[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
gEDA-cvs: gaf.git: branch: master updated (1.5.4-20090830-16-g3edef9f)
The branch, master has been updated
via 3edef9ffb6ebb859213efea337e3bd419b99da8e (commit)
via b7ca06041ea464b0d064bfa965843d2907a83571 (commit)
from 4f40000aff79919a3894de4e2e6e560e224220ce (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
=========
configure.ac | 25 +-
docs/wiki/001geda_debian.html | 58 --
docs/wiki/001geda_documentation.html | 383 ---------
docs/wiki/001geda_gschem_mp.html | 27 -
docs/wiki/001geda_hse_howto.html | 27 -
docs/wiki/001geda_kig_howto.html | 27 -
docs/wiki/001geda_scg.html | 619 --------------
docs/wiki/001geda_suse_10.html | 61 --
docs/wiki/001geda_tasks.html | 27 -
docs/wiki/001geda_todos.html | 27 -
docs/wiki/Makefile.am | 5 +-
docs/wiki/_detail/.gitignore | 3 -
docs/wiki/_detail/001geda_ambiguous1.html | 50 --
docs/wiki/_detail/001geda_ambiguous1_fixed.html | 50 --
docs/wiki/_detail/001geda_design_flow.html | 50 --
docs/wiki/_detail/001geda_faq_attrib.html | 50 --
.../_detail/001geda_gschem_screenshot_001.html | 50 --
docs/wiki/_detail/001geda_gschem_workflow_01.html | 50 --
docs/wiki/_detail/001geda_nets.html | 50 --
docs/wiki/_detail/001geda_status_screenshot.html | 50 --
docs/wiki/_detail/001geda_symbol_7400-1.html | 50 --
.../wiki/_detail/001geda_symbol_7400-1_hidden.html | 50 --
.../_detail/001geda_terminal_screenshot_001.html | 50 --
.../001tragesym_acroread_selectiontable.html | 50 --
docs/wiki/_detail/001tragesym_gschem_finished.html | 50 --
.../_detail/001tragesym_gschem_showhidden.html | 50 --
.../_detail/001tragesym_kpdf_pinconfiguration.html | 50 --
.../_detail/001tragesym_kpdf_pindescription.html | 50 --
docs/wiki/_detail/001tragesym_ooo_attributes.html | 50 --
docs/wiki/_detail/001tragesym_ooo_changedpins.html | 50 --
docs/wiki/_detail/001tragesym_ooo_rearanged.html | 50 --
docs/wiki/_detail/001tragesym_ooo_selection.html | 50 --
.../001tragesym_xemacs_modifiedselection.html | 50 --
.../_detail/001tragesym_xemacs_rawselection.html | 50 --
docs/wiki/_detail/Makefile.am | 11 -
docs/wiki/_detail/devel_tips_dialog_picture.html | 50 --
docs/wiki/_detail/geda_ambiguous1.html | 50 --
docs/wiki/_detail/geda_ambiguous1_fixed.html | 50 --
docs/wiki/_detail/geda_board-1.html | 50 --
docs/wiki/_detail/geda_board-2.html | 50 --
docs/wiki/_detail/geda_board-3.html | 50 --
docs/wiki/_detail/geda_board-4.html | 50 --
docs/wiki/_detail/geda_board-5.html | 50 --
docs/wiki/_detail/geda_board-6.html | 50 --
docs/wiki/_detail/geda_coordinatespace.html | 50 --
docs/wiki/_detail/geda_design_flow.html | 50 --
docs/wiki/_detail/geda_dialogdirective.html | 50 --
docs/wiki/_detail/geda_dialoginclude.html | 50 --
docs/wiki/_detail/geda_dialogmodel.html | 50 --
docs/wiki/_detail/geda_dialogtrans.html | 50 --
docs/wiki/_detail/geda_dialogvac.html | 50 --
docs/wiki/_detail/geda_dialogvdc1.html | 50 --
docs/wiki/_detail/geda_faq_attrib.html | 50 --
docs/wiki/_detail/geda_fileformat_textgraphic.html | 50 --
docs/wiki/_detail/geda_geda_flow.html | 50 --
docs/wiki/_detail/geda_gschem-sym-1.html | 50 --
docs/wiki/_detail/geda_gschem-sym-2.html | 50 --
docs/wiki/_detail/geda_gschem-sym-3.html | 50 --
docs/wiki/_detail/geda_gschem_screenshot_001.html | 50 --
docs/wiki/_detail/geda_gschem_workflow_01.html | 50 --
docs/wiki/_detail/geda_net.html | 50 --
docs/wiki/_detail/geda_nets.html | 50 --
docs/wiki/_detail/geda_one-sch-1.html | 50 --
docs/wiki/_detail/geda_one-sch-2.html | 50 --
docs/wiki/_detail/geda_one-sch-3.html | 50 --
docs/wiki/_detail/geda_pcb-el-1.html | 50 --
docs/wiki/_detail/geda_pcb-el-2.html | 50 --
docs/wiki/_detail/geda_rf_cascade_figure1.html | 50 --
docs/wiki/_detail/geda_rf_cascade_figure2.html | 50 --
docs/wiki/_detail/geda_schematicfinished2.html | 50 --
docs/wiki/_detail/geda_simple1.html | 50 --
docs/wiki/_detail/geda_status_screenshot.html | 50 --
docs/wiki/_detail/geda_suse_electronics_menu.html | 50 --
docs/wiki/_detail/geda_switcap_figure1.html | 50 --
docs/wiki/_detail/geda_switcap_figure2.html | 50 --
docs/wiki/_detail/geda_switcap_figure3.html | 50 --
docs/wiki/_detail/geda_switcap_figure4.html | 50 --
docs/wiki/_detail/geda_symbol_7400-1.html | 50 --
docs/wiki/_detail/geda_symbol_7400-1_hidden.html | 50 --
.../wiki/_detail/geda_terminal_screenshot_001.html | 50 --
docs/wiki/_detail/geda_two-sch-1.html | 50 --
docs/wiki/_detail/geda_two-sch-2.html | 50 --
docs/wiki/_detail/geda_warmup_add_component.html | 50 --
docs/wiki/_detail/geda_warmup_gschem01.html | 50 --
docs/wiki/_detail/geda_warmup_gschem02.html | 50 --
docs/wiki/_detail/geda_warmup_gschem03.html | 50 --
.../_detail/tragesym_acroread_selectiontable.html | 50 --
docs/wiki/_detail/tragesym_gschem_finished.html | 50 --
docs/wiki/_detail/tragesym_gschem_showhidden.html | 50 --
.../_detail/tragesym_kpdf_pinconfiguration.html | 50 --
.../wiki/_detail/tragesym_kpdf_pindescription.html | 50 --
docs/wiki/_detail/tragesym_ooo_attributes.html | 50 --
docs/wiki/_detail/tragesym_ooo_changedpins.html | 50 --
docs/wiki/_detail/tragesym_ooo_rearanged.html | 50 --
docs/wiki/_detail/tragesym_ooo_selection.html | 50 --
.../_detail/tragesym_xemacs_modifiedselection.html | 50 --
.../wiki/_detail/tragesym_xemacs_rawselection.html | 50 --
docs/wiki/_media/.gitignore | 3 -
docs/wiki/_media/Makefile.am | 11 -
docs/wiki/best_practices.html | 32 +-
docs/wiki/design.css | 692 ++++++++++++++++
docs/wiki/docs_20060124_gschem_ug_app_a.html | 27 -
docs/wiki/docs_20060124_gschem_ug_app_b.html | 27 -
docs/wiki/docs_20060124_gschem_ug_app_c.html | 27 -
...m_ug_components_symbols_objects_attributes.html | 27 -
...20060124_gschem_ug_electrical_connectivity.html | 27 -
...cs_20060124_gschem_ug_how_to_ask_questions.html | 27 -
.../docs_20060124_gschem_ug_installing_gschem.html | 27 -
docs/wiki/docs_20060124_gschem_ug_resources.html | 27 -
.../docs_20060124_gschem_ug_the_main_window.html | 27 -
.../docs_20060124_gschem_ug_the_status_window.html | 27 -
docs/wiki/geda-bom_readme.html | 52 ++
...l => geda-circuit_simulation_improvements.html} | 28 +-
.../{geda_covered_mp.html => geda-covered_mp.html} | 26 +-
docs/wiki/{geda_csygas.html => geda-csygas.html} | 38 +-
docs/wiki/{geda_cygwin.html => geda-cygwin.html} | 47 +-
...s.html => geda-data_plotting_improvements.html} | 30 +-
... => geda-data_structure_design_discussion.html} | 30 +-
docs/wiki/geda-debian.fr.html | 46 ++
docs/wiki/geda-debian.html | 52 ++
...=> geda-design_flow_and_hierarchy_roadmap.html} | 30 +-
docs/wiki/geda-design_flow_roadmap.html | 26 +
.../{geda_devel-tips.html => geda-devel-tips.html} | 244 +++----
docs/wiki/geda-devmacosx.html | 160 ++++
docs/wiki/geda-documentation.fr.html | 371 +++++++++
docs/wiki/geda-documentation.html | 391 +++++++++
docs/wiki/geda-eagle_pcb_netlister_readme.html | 43 +
...geda_example_hsm.html => geda-example_hsm.html} | 26 +-
...mple_usbjtag.html => geda-example_usbjtag.html} | 26 +-
docs/wiki/geda-experiences.html | 154 ++++
...a_faq-attribs.html => geda-faq-attribs.fr.html} | 35 +-
...geda_faq-attribs.html => geda-faq-attribs.html} | 141 ++--
...faq-gnetlist.html => geda-faq-gnetlist.fr.html} | 35 +-
...da_faq-gnetlist.html => geda-faq-gnetlist.html} | 37 +-
...faq-gsch2pcb.html => geda-faq-gsch2pcb.fr.html} | 32 +-
...da_faq-gsch2pcb.html => geda-faq-gsch2pcb.html} | 44 +-
...eda_faq-gschem.html => geda-faq-gschem.fr.html} | 102 ++--
.../{geda_faq-gschem.html => geda-faq-gschem.html} | 249 ++++--
docs/wiki/{geda_faq-pcb.html => geda-faq-pcb.html} | 52 +-
...simulation.html => geda-faq-simulation.fr.html} | 30 +-
...aq-simulation.html => geda-faq-simulation.html} | 30 +-
docs/wiki/{001geda_faq.html => geda-faq.fr.html} | 48 +-
docs/wiki/{geda_faq.html => geda-faq.html} | 96 ++--
.../{geda_fbabgapp.html => geda-fbabgapp.html} | 28 +-
docs/wiki/geda-fc1.html | 52 ++
docs/wiki/geda-fc2.html | 52 ++
docs/wiki/geda-fc3.html | 52 ++
docs/wiki/{geda_fc4.html => geda-fc4.html} | 28 +-
...tion.html => geda-fedora_rpm_installation.html} | 32 +-
...format_spec.html => geda-file_format_spec.html} | 377 ++++++++--
docs/wiki/geda-format_translation.html | 391 +++++++++
...attrib_readme.html => geda-gattrib_readme.html} | 26 +-
docs/wiki/geda-gedasuite_installation.html | 142 ++++
.../{geda_gerbv_mp.html => geda-gerbv_mp.html} | 26 +-
..._pnp_readme.html => geda-gerbv_pnp_readme.html} | 26 +-
docs/wiki/{geda_gfdl.html => geda-gfdl.html} | 26 +-
...{geda_glossaire.html => geda-glossaire.fr.html} | 26 +-
.../{geda_glossaire.html => geda-glossary.fr.html} | 26 +-
.../{geda_glossary.html => geda-glossary.html} | 38 +-
...geda_gnetlist_mp.html => geda-gnetlist_mp.html} | 26 +-
...geda_gnetlist_ug.html => geda-gnetlist_ug.html} | 78 +-
docs/wiki/{geda_grcsan.html => geda-grcsan.html} | 36 +-
docs/wiki/geda-grenum_mp.html | 76 ++
...h2pcb_readme.html => geda-gsch2pcb_readme.html} | 26 +-
...b_tutorial.html => geda-gsch2pcb_tutorial.html} | 128 ++--
...ml => geda-gsch2pcb_tutorial_releasenotes.html} | 30 +-
.../wiki/geda-gschem2pcb_readme.html | 37 +-
.../{geda_gschem_mp.html => geda-gschem_mp.html} | 26 +-
...1geda_gschem_ug.html => geda-gschem_ug.fr.html} | 160 ++--
.../{geda_gschem_ug.html => geda-gschem_ug.html} | 505 ++++++------
..._gschem_warmup.html => geda-gschem_warmup.html} | 40 +-
docs/wiki/geda-gsymcheck_mp.html | 87 ++
docs/wiki/geda-gtkwave_lxt2miner_mp.html | 79 ++
docs/wiki/geda-gtkwave_lxt2vcd_mp.html | 60 ++
.../{geda_gtkwave_mp.html => geda-gtkwave_mp.html} | 26 +-
docs/wiki/geda-gtkwave_mvl2lxt_mp.html | 45 +
docs/wiki/geda-gtkwave_mvl2vcd_mp.html | 46 ++
docs/wiki/geda-gtkwave_tex2vcd_mp.html | 45 +
docs/wiki/geda-gtkwave_tla2vcd_mp.html | 63 ++
...2lxt2_mp.html => geda-gtkwave_vcd2lxt2_mp.html} | 26 +-
...cd2lxt_mp.html => geda-gtkwave_vcd2lxt_mp.html} | 26 +-
...cd2vzt_mp.html => geda-gtkwave_vcd2vzt_mp.html} | 26 +-
docs/wiki/geda-gtkwave_vzt2vcd_mp.html | 55 ++
docs/wiki/geda-gtkwave_vztminer_mp.html | 78 ++
...le_scripting.html => geda-guile_scripting.html} | 34 +-
.../{geda_hse_howto.html => geda-hse_howto.html} | 26 +-
.../{geda_icarus_anc.html => geda-icarus_anc.html} | 26 +-
...extensions.html => geda-icarus_extensions.html} | 26 +-
docs/wiki/geda-icarus_glossary.html | 61 ++
...rus_ieee1364.html => geda-icarus_ieee1364.html} | 26 +-
.../{geda_icarus_mp.html => geda-icarus_mp.html} | 26 +-
...carus_opcodes.html => geda-icarus_opcodes.html} | 26 +-
...ick_start.html => geda-icarus_quick_start.html} | 26 +-
..._icarus_readme.html => geda-icarus_readme.html} | 26 +-
..._icarus_vpi_mp.html => geda-icarus_vpi_mp.html} | 26 +-
...in_vvp.html => geda-icarus_vpi_within_vvp.html} | 26 +-
...p_runtime.html => geda-icarus_vvp_runtime.html} | 26 +-
...lation.html => geda-icarus_vvp_simulation.html} | 26 +-
...nx_hints.html => geda-icarus_xilinx_hints.html} | 26 +-
.../{geda_icarus_xnf.html => geda-icarus_xnf.html} | 26 +-
...rus_fpga_lcg.html => geda-igarus_fpga_lcg.html} | 26 +-
...installation.html => geda-installation.fr.html} | 46 +-
...da_installation.html => geda-installation.html} | 58 +-
...ed_plugins.html => geda-installed_plugins.html} | 34 +-
.../{geda_kig_howto.html => geda-kig_howto.html} | 34 +-
..._list.html => geda-master_attributes_list.html} | 60 +-
docs/wiki/geda-mcalc_readme.html | 51 ++
.../{geda_na_howto.html => geda-na_howto.html} | 30 +-
...geda_ngnutmeg_mp.html => geda-ngnutmeg_mp.html} | 26 +-
..._ngsconvert_mp.html => geda-ngsconvert_mp.html} | 26 +-
...nd_gschem.html => geda-ngspice_and_gschem.html} | 50 +-
.../{geda_ngspice_mp.html => geda-ngspice_mp.html} | 26 +-
...geda_olib_readme.html => geda-olib_readme.html} | 26 +-
...rence.html => geda-pcb-quick_reference.fr.html} | 30 +-
...eference.html => geda-pcb-quick_reference.html} | 52 +-
...cb_footprints.html => geda-pcb_footprints.html} | 114 ++-
docs/wiki/geda-pcb_funding_sow-fwdann_ideas.html | 64 ++
docs/wiki/geda-pcb_funding_sow-gui_ideas.html | 35 +
docs/wiki/geda-pcb_funding_sow.html | 844 ++++++++++++++++++++
docs/wiki/geda-pcb_mp.html | 50 ++
...001geda_pcb_tips.html => geda-pcb_tips.fr.html} | 44 +-
.../{geda_pcb_tips.html => geda-pcb_tips.html} | 592 +++++++++-----
docs/wiki/geda-release_engineering.html | 136 ++++
docs/wiki/{geda_scg.html => geda-scg.fr.html} | 37 +-
docs/wiki/{geda_scg.html => geda-scg.html} | 71 +-
docs/wiki/{geda_scm.html => geda-scm.html} | 178 +++--
.../{geda_sdb_howto.html => geda-sdb_howto.html} | 36 +-
.../wiki/geda-sn_readme.html | 37 +-
docs/wiki/geda-spice_improvements.html | 26 +
docs/wiki/{geda_ssan.html => geda-ssan.html} | 40 +-
docs/wiki/geda-start.html | 23 +
...geda_style_guide.html => geda-style_guide.html} | 31 +-
.../{geda_suse_10.html => geda-suse_10.0.html} | 28 +-
docs/wiki/geda-suse_10.1.html | 49 ++
docs/wiki/geda-suse_9.3.html | 65 ++
...lation.html => geda-suse_rpm_installation.html} | 127 ++--
...tax_features.html => geda-syntax_features.html} | 26 +-
...dme.html => geda-systemc_netlister_readme.html} | 28 +-
docs/wiki/{geda_tasks.html => geda-tasks.html} | 51 +-
docs/wiki/geda-todos.html | 402 ++++++++++
docs/wiki/geda-todos_historical.html | 238 ++++++
docs/wiki/geda-tragesym_readme.html | 46 ++
...utorial.html => geda-tragesym_tutorial.fr.html} | 46 +-
...m_tutorial.html => geda-tragesym_tutorial.html} | 46 +-
...istor_guide.html => geda-transistor_guide.html} | 30 +-
docs/wiki/geda-ubuntu.html | 35 +
.../{001geda_usage.html => geda-usage.fr.html} | 36 +-
docs/wiki/{geda_usage.html => geda-usage.html} | 48 +-
...readme.html => geda-vams_netlister_readme.html} | 28 +-
...dme.html => geda-verilog_netlister_readme.html} | 26 +-
docs/wiki/geda-version_control_migration.html | 110 +++
docs/wiki/geda-vhdl_netlister_readme.html | 41 +
docs/wiki/geda-wcalc_mp.html | 70 ++
docs/wiki/geda-wcalc_readme.html | 54 ++
...calc_stdio_mp.html => geda-wcalc_stdio_mp.html} | 26 +-
docs/wiki/geda-wip-clipboard.html | 179 +++++
docs/wiki/geda-xml_file_formats.html | 108 +++
docs/wiki/geda_bill_wilson_s.html | 27 -
docs/wiki/geda_bom_readme.html | 64 --
docs/wiki/geda_covered_rv.html | 27 -
docs/wiki/geda_debian.html | 64 --
docs/wiki/geda_documentation.html | 405 ----------
docs/wiki/geda_eagle_pcb_netlister_readme.html | 55 --
docs/wiki/geda_fc1.html | 64 --
docs/wiki/geda_fc2.html | 64 --
docs/wiki/geda_fc3.html | 64 --
docs/wiki/geda_footprint_creation.html | 27 -
docs/wiki/geda_gedasuite_installation.html | 283 -------
docs/wiki/geda_grenum_mp.html | 88 --
docs/wiki/geda_gschem2pcb_readme.html | 166 ----
docs/wiki/geda_gsymcheck_mp.html | 99 ---
docs/wiki/geda_gtkwave_lxt2miner_mp.html | 91 ---
docs/wiki/geda_gtkwave_lxt2vcd_mp.html | 72 --
docs/wiki/geda_gtkwave_mvl2lxt_mp.html | 57 --
docs/wiki/geda_gtkwave_mvl2vcd_mp.html | 58 --
docs/wiki/geda_gtkwave_tex2vcd_mp.html | 57 --
docs/wiki/geda_gtkwave_tla2vcd_mp.html | 75 --
docs/wiki/geda_gtkwave_vzt2vcd_mp.html | 67 --
docs/wiki/geda_gtkwave_vztminer_mp.html | 90 ---
docs/wiki/geda_icarus_glossary.html | 73 --
docs/wiki/geda_mcalc_readme.html | 63 --
docs/wiki/geda_pcb.html | 27 -
docs/wiki/geda_pcb_mp.html | 62 --
docs/wiki/geda_pcb_ug.html | 27 -
docs/wiki/geda_release_engineering.html | 137 ----
docs/wiki/geda_sn_readme.html | 171 ----
docs/wiki/geda_suse_9.html | 77 --
docs/wiki/geda_todos.html | 194 -----
docs/wiki/geda_tragesym_readme.html | 58 --
docs/wiki/geda_ubuntu.html | 47 --
docs/wiki/geda_vhdl_netlister_readme.html | 53 --
docs/wiki/geda_wcalc_mp.html | 82 --
docs/wiki/geda_wcalc_readme.html | 66 --
docs/wiki/gerbv-projects.html | 39 +-
docs/wiki/glue-projects.html | 48 +-
docs/wiki/gschem-projects.html | 54 +-
docs/wiki/gsoc2007.html | 30 +-
docs/wiki/gsoc2007_projects.html | 28 +-
docs/wiki/gsoc2008.html | 32 +-
docs/wiki/gsoc2008_projects.html | 38 +-
docs/wiki/gsoc2009.html | 134 +++
...oc2008_projects.html => gsoc2009_projects.html} | 72 +-
docs/wiki/gtkwave-projects.html | 38 +
docs/wiki/gwave-projects.html | 57 +-
docs/wiki/{ => images}/.gitignore | 0
docs/wiki/images/Makefile.am | 13 +
docs/wiki/images/bullet.gif | Bin 0 -> 50 bytes
docs/wiki/images/button-cc.gif | Bin 0 -> 1231 bytes
docs/wiki/images/button-css.png | Bin 0 -> 299 bytes
docs/wiki/images/button-donate.gif | Bin 0 -> 200 bytes
docs/wiki/images/button-dw.png | Bin 0 -> 427 bytes
docs/wiki/images/button-php.gif | Bin 0 -> 269 bytes
docs/wiki/images/button-rss.png | Bin 0 -> 280 bytes
docs/wiki/images/button-xhtml.png | Bin 0 -> 321 bytes
docs/wiki/{lib/tpl/geda => }/images/closed.gif | Bin 54 -> 54 bytes
docs/wiki/{lib => }/images/interwiki.png | Bin 1089 -> 1089 bytes
docs/wiki/{ => images/interwiki}/.gitignore | 0
docs/wiki/images/interwiki/Makefile.am | 11 +
docs/wiki/{lib => }/images/interwiki/amazon.de.gif | Bin 882 -> 882 bytes
.../amazon.de.gif => images/interwiki/amazon.gif} | Bin 882 -> 882 bytes
.../interwiki/amazon.uk.gif} | Bin 882 -> 882 bytes
.../dokubug.gif => images/interwiki/bug.gif} | Bin 166 -> 166 bytes
docs/wiki/{lib => }/images/interwiki/coral.gif | Bin 85 -> 85 bytes
docs/wiki/{lib => }/images/interwiki/doku.gif | Bin 257 -> 257 bytes
docs/wiki/{lib => }/images/interwiki/google.gif | Bin 980 -> 980 bytes
docs/wiki/{lib => }/images/interwiki/meatball.gif | Bin 1100 -> 1100 bytes
docs/wiki/{lib => }/images/interwiki/phpfn.gif | Bin 330 -> 330 bytes
docs/wiki/{lib => }/images/interwiki/sb.gif | Bin 886 -> 886 bytes
docs/wiki/{lib => }/images/interwiki/wiki.gif | Bin 909 -> 909 bytes
docs/wiki/{lib => }/images/interwiki/wp.gif | Bin 680 -> 680 bytes
.../interwiki/wp.gif => images/interwiki/wpde.gif} | Bin 680 -> 680 bytes
.../wp.gif => images/interwiki/wpmeta.gif} | Bin 680 -> 680 bytes
docs/wiki/{lib/tpl/geda => }/images/link_icon.gif | Bin 942 -> 942 bytes
docs/wiki/{lib/tpl/geda => }/images/mail_icon.gif | Bin 918 -> 918 bytes
docs/wiki/{lib/tpl/geda => }/images/open.gif | Bin 54 -> 54 bytes
docs/wiki/{ => images/smileys}/.gitignore | 0
docs/wiki/images/smileys/Makefile.am | 11 +
docs/wiki/images/smileys/delete.gif | Bin 0 -> 1421 bytes
docs/wiki/{lib => }/images/smileys/fixme.gif | Bin 1435 -> 1435 bytes
docs/wiki/images/smileys/icon_arrow.gif | Bin 0 -> 170 bytes
docs/wiki/images/smileys/icon_biggrin.gif | Bin 0 -> 172 bytes
docs/wiki/images/smileys/icon_confused.gif | Bin 0 -> 171 bytes
docs/wiki/images/smileys/icon_cool.gif | Bin 0 -> 172 bytes
docs/wiki/images/smileys/icon_cry.gif | Bin 0 -> 498 bytes
docs/wiki/images/smileys/icon_doubt.gif | Bin 0 -> 990 bytes
docs/wiki/images/smileys/icon_doubt2.gif | Bin 0 -> 992 bytes
docs/wiki/images/smileys/icon_eek.gif | Bin 0 -> 170 bytes
docs/wiki/images/smileys/icon_evil.gif | Bin 0 -> 236 bytes
docs/wiki/images/smileys/icon_exclaim.gif | Bin 0 -> 236 bytes
docs/wiki/images/smileys/icon_frown.gif | Bin 0 -> 171 bytes
docs/wiki/images/smileys/icon_fun.gif | Bin 0 -> 590 bytes
docs/wiki/images/smileys/icon_idea.gif | Bin 0 -> 176 bytes
.../smileys/icon_kaddi.gif} | Bin 882 -> 991 bytes
docs/wiki/images/smileys/icon_lol.gif | Bin 0 -> 336 bytes
docs/wiki/images/smileys/icon_mrgreen.gif | Bin 0 -> 349 bytes
docs/wiki/images/smileys/icon_neutral.gif | Bin 0 -> 171 bytes
docs/wiki/images/smileys/icon_question.gif | Bin 0 -> 248 bytes
docs/wiki/images/smileys/icon_razz.gif | Bin 0 -> 176 bytes
docs/wiki/images/smileys/icon_redface.gif | Bin 0 -> 650 bytes
docs/wiki/images/smileys/icon_rolleyes.gif | Bin 0 -> 485 bytes
docs/wiki/images/smileys/icon_sad.gif | Bin 0 -> 171 bytes
docs/wiki/images/smileys/icon_silenced.gif | Bin 0 -> 231 bytes
docs/wiki/{lib => }/images/smileys/icon_smile.gif | Bin 174 -> 174 bytes
docs/wiki/{lib => }/images/smileys/icon_smile2.gif | Bin 174 -> 174 bytes
docs/wiki/images/smileys/icon_surprised.gif | Bin 0 -> 174 bytes
docs/wiki/images/smileys/icon_twisted.gif | Bin 0 -> 238 bytes
docs/wiki/{lib => }/images/smileys/icon_wink.gif | Bin 170 -> 170 bytes
docs/wiki/{lib/tpl/geda => }/images/tocdot2.gif | Bin 810 -> 810 bytes
docs/wiki/{lib/tpl/geda => }/images/windows.gif | Bin 223 -> 223 bytes
docs/wiki/index.html | 142 ++--
docs/wiki/lib/.gitignore | 3 -
docs/wiki/lib/exe/.gitignore | 3 -
docs/wiki/lib/exe/001css | 1 -
docs/wiki/lib/exe/002css | 1 -
docs/wiki/lib/exe/Makefile.am | 11 -
docs/wiki/lib/exe/css | 1 -
docs/wiki/lib/exe/opensearch | 7 -
docs/wiki/lib/images/.gitignore | 3 -
docs/wiki/lib/images/Makefile.am | 13 -
docs/wiki/lib/images/error.png | Bin 706 -> 0 bytes
docs/wiki/lib/images/fileicons/.gitignore | 3 -
docs/wiki/lib/images/fileicons/Makefile.am | 11 -
docs/wiki/lib/images/fileicons/deb.png | Bin 716 -> 0 bytes
docs/wiki/lib/images/fileicons/doc.png | Bin 659 -> 0 bytes
docs/wiki/lib/images/fileicons/file.png | Bin 720 -> 0 bytes
docs/wiki/lib/images/fileicons/gif.png | Bin 1001 -> 0 bytes
docs/wiki/lib/images/fileicons/gz.png | Bin 716 -> 0 bytes
docs/wiki/lib/images/fileicons/jpeg.png | Bin 1001 -> 0 bytes
docs/wiki/lib/images/fileicons/jpg.png | Bin 1001 -> 0 bytes
docs/wiki/lib/images/fileicons/odc.png | Bin 749 -> 0 bytes
docs/wiki/lib/images/fileicons/odf.png | Bin 807 -> 0 bytes
docs/wiki/lib/images/fileicons/odg.png | Bin 788 -> 0 bytes
docs/wiki/lib/images/fileicons/odi.png | Bin 788 -> 0 bytes
docs/wiki/lib/images/fileicons/odp.png | Bin 744 -> 0 bytes
docs/wiki/lib/images/fileicons/ods.png | Bin 749 -> 0 bytes
docs/wiki/lib/images/fileicons/odt.png | Bin 577 -> 0 bytes
docs/wiki/lib/images/fileicons/pdf.png | Bin 663 -> 0 bytes
docs/wiki/lib/images/fileicons/png.png | Bin 1001 -> 0 bytes
docs/wiki/lib/images/fileicons/ppt.png | Bin 762 -> 0 bytes
docs/wiki/lib/images/fileicons/ps.png | Bin 534 -> 0 bytes
docs/wiki/lib/images/fileicons/rar.png | Bin 631 -> 0 bytes
docs/wiki/lib/images/fileicons/rpm.png | Bin 638 -> 0 bytes
docs/wiki/lib/images/fileicons/rtf.png | Bin 474 -> 0 bytes
docs/wiki/lib/images/fileicons/src.png | Bin 542 -> 0 bytes
docs/wiki/lib/images/fileicons/swf.png | Bin 843 -> 0 bytes
docs/wiki/lib/images/fileicons/sxc.png | Bin 749 -> 0 bytes
docs/wiki/lib/images/fileicons/sxd.png | Bin 788 -> 0 bytes
docs/wiki/lib/images/fileicons/sxi.png | Bin 744 -> 0 bytes
docs/wiki/lib/images/fileicons/sxw.png | Bin 577 -> 0 bytes
docs/wiki/lib/images/fileicons/tar.png | Bin 747 -> 0 bytes
docs/wiki/lib/images/fileicons/tgz.png | Bin 716 -> 0 bytes
docs/wiki/lib/images/fileicons/xls.png | Bin 731 -> 0 bytes
docs/wiki/lib/images/fileicons/zip.png | Bin 874 -> 0 bytes
docs/wiki/lib/images/info.png | Bin 783 -> 0 bytes
docs/wiki/lib/images/interwiki/.gitignore | 3 -
docs/wiki/lib/images/interwiki/Makefile.am | 11 -
docs/wiki/lib/images/interwiki/amazon.gif | Bin 882 -> 0 bytes
docs/wiki/lib/images/interwiki/amazon.uk.gif | Bin 882 -> 0 bytes
docs/wiki/lib/images/interwiki/wpde.gif | Bin 680 -> 0 bytes
docs/wiki/lib/images/interwiki/wpmeta.gif | Bin 680 -> 0 bytes
docs/wiki/lib/images/notify.png | Bin 789 -> 0 bytes
docs/wiki/lib/images/smileys/.gitignore | 3 -
docs/wiki/lib/images/smileys/Makefile.am | 11 -
docs/wiki/lib/images/success.png | Bin 816 -> 0 bytes
docs/wiki/lib/plugins/.gitignore | 3 -
docs/wiki/lib/plugins/Makefile.am | 13 -
docs/wiki/lib/plugins/definitionlist/.gitignore | 3 -
docs/wiki/lib/plugins/definitionlist/Makefile.am | 13 -
.../lib/plugins/definitionlist/images/.gitignore | 3 -
.../lib/plugins/definitionlist/images/Makefile.am | 11 -
.../lib/plugins/definitionlist/images/bullet.gif | Bin 45 -> 0 bytes
docs/wiki/lib/plugins/note/.gitignore | 3 -
docs/wiki/lib/plugins/note/images/.gitignore | 3 -
docs/wiki/lib/plugins/note/images/Makefile.am | 11 -
docs/wiki/lib/plugins/note/images/important.png | Bin 2250 -> 0 bytes
docs/wiki/lib/plugins/note/images/note.png | Bin 2520 -> 0 bytes
docs/wiki/lib/plugins/note/images/tip.png | Bin 2909 -> 0 bytes
docs/wiki/lib/plugins/note/images/warning.png | Bin 3249 -> 0 bytes
docs/wiki/lib/tpl/.gitignore | 3 -
docs/wiki/lib/tpl/geda/Makefile.am | 9 -
docs/wiki/lib/tpl/geda/images/Makefile.am | 11 -
docs/wiki/lib/tpl/geda/images/buttonshadow.png | Bin 257 -> 0 bytes
docs/wiki/lib/tpl/geda/images/favicon | Bin 7406 -> 0 bytes
docs/wiki/lib/tpl/geda/images/inputshadow.png | Bin 155 -> 0 bytes
docs/wiki/libgeda3.html | 30 +-
docs/wiki/libgeda3_object_based_design.html | 265 ++++++
docs/wiki/{ => media}/.gitignore | 0
docs/wiki/media/Makefile.am | 8 +
docs/wiki/{ => media/devel_tips}/.gitignore | 0
.../plugins/note => media/devel_tips}/Makefile.am | 6 +-
.../devel_tips/dialog_picture.png} | Bin 27075 -> 27075 bytes
docs/wiki/{ => media/geda}/.gitignore | 0
docs/wiki/media/geda/Makefile.am | 11 +
.../geda/ambiguous1.png} | Bin 6647 -> 6647 bytes
.../geda/ambiguous1_fixed.png} | Bin 5251 -> 5251 bytes
.../geda_board-1.png => media/geda/board-1.png} | Bin 4334 -> 4334 bytes
.../geda_board-2.png => media/geda/board-2.png} | Bin 5507 -> 5507 bytes
.../geda_board-3.png => media/geda/board-3.png} | Bin 8719 -> 8719 bytes
.../geda_board-4.png => media/geda/board-4.png} | Bin 8265 -> 8265 bytes
.../geda_board-5.png => media/geda/board-5.png} | Bin 7029 -> 7029 bytes
.../geda_board-6.png => media/geda/board-6.png} | Bin 7104 -> 7104 bytes
.../geda/coordinatespace.jpg} | Bin 6560 -> 6560 bytes
.../geda/design_flow.jpg} | Bin 3605 -> 3605 bytes
.../geda/dialogdirective.png} | Bin 16106 -> 16106 bytes
.../geda/dialoginclude.png} | Bin 15225 -> 15225 bytes
.../geda/dialogmodel.png} | Bin 17197 -> 17197 bytes
.../geda/dialogtrans.png} | Bin 16070 -> 16070 bytes
.../geda/dialogvac.png} | Bin 17300 -> 17300 bytes
.../geda/dialogvdc1.png} | Bin 16954 -> 16954 bytes
.../geda/faq_attrib.jpg} | Bin 25961 -> 25961 bytes
.../geda/fileformat_textgraphic.jpg} | Bin 9453 -> 9453 bytes
.../geda/geda_flow.png} | Bin 7577 -> 7577 bytes
.../geda/gschem-sym-1.png} | Bin 4216 -> 4216 bytes
.../geda/gschem-sym-2.png} | Bin 3613 -> 3613 bytes
.../geda/gschem-sym-3.png} | Bin 3797 -> 3797 bytes
.../geda/gschem_screenshot_001.jpg} | Bin 36866 -> 36866 bytes
.../geda/gschem_workflow_01.jpg} | Bin 44871 -> 44871 bytes
.../{_media/geda_net.jpg => media/geda/net.jpg} | Bin 68055 -> 68055 bytes
.../{_media/geda_nets.jpg => media/geda/nets.jpg} | Bin 133918 -> 133918 bytes
.../geda/one-sch-1.png} | Bin 5246 -> 5246 bytes
.../geda/one-sch-2.png} | Bin 5412 -> 5412 bytes
.../geda/one-sch-3.png} | Bin 4997 -> 4997 bytes
docs/wiki/media/geda/paper1.gif | Bin 0 -> 9220 bytes
.../media/geda/path_example_and_gate-smaller.png | Bin 0 -> 4458 bytes
docs/wiki/media/geda/path_example_and_gate.png | Bin 0 -> 8244 bytes
.../geda_pcb-el-1.png => media/geda/pcb-el-1.png} | Bin 993 -> 993 bytes
.../geda_pcb-el-2.png => media/geda/pcb-el-2.png} | Bin 1097 -> 1097 bytes
.../geda/rf_cascade_figure1.jpg} | Bin 28453 -> 28453 bytes
.../geda/rf_cascade_figure2.jpg} | Bin 55249 -> 55249 bytes
docs/wiki/media/geda/schematicfinished.png | Bin 0 -> 31197 bytes
.../geda/schematicfinished2.png} | Bin 14232 -> 14232 bytes
.../geda_simple1.png => media/geda/simple1.png} | Bin 7841 -> 7841 bytes
.../geda/status_screenshot.jpg} | Bin 139186 -> 139186 bytes
.../geda/suse_electronics_menu.png} | Bin 54042 -> 54042 bytes
.../geda/switcap_figure1.jpg} | Bin 26659 -> 26659 bytes
.../geda/switcap_figure2.jpg} | Bin 25202 -> 25202 bytes
.../geda/switcap_figure3.jpg} | Bin 32167 -> 32167 bytes
.../geda/switcap_figure4.jpg} | Bin 29211 -> 29211 bytes
.../geda/symbol_7400-1.png} | Bin 5564 -> 5564 bytes
.../geda/symbol_7400-1_hidden.png} | Bin 2845 -> 2845 bytes
.../geda/terminal_screenshot_001.jpg} | Bin 66444 -> 66444 bytes
.../geda/two-sch-1.png} | Bin 4190 -> 4190 bytes
.../geda/two-sch-2.png} | Bin 3932 -> 3932 bytes
.../geda/warmup_add_component.png} | Bin 221 -> 221 bytes
.../geda/warmup_gschem01.png} | Bin 21727 -> 21727 bytes
.../geda/warmup_gschem02.png} | Bin 22213 -> 22213 bytes
.../geda/warmup_gschem03.png} | Bin 22323 -> 22323 bytes
docs/wiki/{ => media/tragesym}/.gitignore | 0
docs/wiki/media/tragesym/Makefile.am | 13 +
.../tragesym/acroread_selectiontable.png} | Bin 20081 -> 20081 bytes
.../tragesym/gschem_finished.png} | Bin 5277 -> 5277 bytes
.../tragesym/gschem_showhidden.png} | Bin 9995 -> 9995 bytes
.../tragesym/kpdf_pinconfiguration.png} | Bin 44021 -> 44021 bytes
.../tragesym/kpdf_pindescription.png} | Bin 32162 -> 32162 bytes
.../tragesym/ooo_attributes.png} | Bin 48240 -> 48240 bytes
.../tragesym/ooo_changedpins.png} | Bin 21007 -> 21007 bytes
.../tragesym/ooo_rearanged.png} | Bin 42428 -> 42428 bytes
.../tragesym/ooo_selection.png} | Bin 9224 -> 9224 bytes
.../tragesym/template.ods} | Bin 18657 -> 18657 bytes
.../tragesym/template.txt} | 0
.../tragesym/template2.ods} | Bin 18834 -> 18834 bytes
.../tragesym/template2.txt.src} | 0
docs/wiki/{ => media/tragesym/tragesym}/.gitignore | 0
.../{lib => media/tragesym/tragesym}/Makefile.am | 6 +-
.../tragesym/tragesym/kpdf_pindescription.png} | Bin 32162 -> 32162 bytes
.../tragesym/xemacs_modifiedselection.png} | Bin 3269 -> 3269 bytes
.../tragesym/xemacs_rawselection.png} | Bin 6395 -> 6395 bytes
docs/wiki/{ => media}/wiki/.gitignore | 0
docs/wiki/{lib/tpl => media/wiki}/Makefile.am | 7 +-
docs/wiki/media/wiki/dokuwiki-128.png | Bin 0 -> 33615 bytes
docs/wiki/pcb-projects.html | 78 +--
docs/wiki/playground-playground.html | 99 +++
...guide.html => playground-transistor_guide.html} | 46 +-
docs/wiki/print.css | 223 ++++++
docs/wiki/start.html | 234 ++++++
docs/wiki/start_es.html | 36 +-
docs/wiki/start_fr.html | 60 +-
docs/wiki/style.css | 44 +
docs/wiki/wiki-dokuwiki.html | 166 ++++
docs/wiki/wiki-syntax.html | 666 +++++++++++++++
gschem/scripts/gschemdoc.sh | 2 +-
541 files changed, 11090 insertions(+), 12801 deletions(-)
delete mode 100644 docs/wiki/001geda_debian.html
delete mode 100644 docs/wiki/001geda_documentation.html
delete mode 100644 docs/wiki/001geda_gschem_mp.html
delete mode 100644 docs/wiki/001geda_hse_howto.html
delete mode 100644 docs/wiki/001geda_kig_howto.html
delete mode 100644 docs/wiki/001geda_scg.html
delete mode 100644 docs/wiki/001geda_suse_10.html
delete mode 100644 docs/wiki/001geda_tasks.html
delete mode 100644 docs/wiki/001geda_todos.html
delete mode 100644 docs/wiki/_detail/.gitignore
delete mode 100644 docs/wiki/_detail/001geda_ambiguous1.html
delete mode 100644 docs/wiki/_detail/001geda_ambiguous1_fixed.html
delete mode 100644 docs/wiki/_detail/001geda_design_flow.html
delete mode 100644 docs/wiki/_detail/001geda_faq_attrib.html
delete mode 100644 docs/wiki/_detail/001geda_gschem_screenshot_001.html
delete mode 100644 docs/wiki/_detail/001geda_gschem_workflow_01.html
delete mode 100644 docs/wiki/_detail/001geda_nets.html
delete mode 100644 docs/wiki/_detail/001geda_status_screenshot.html
delete mode 100644 docs/wiki/_detail/001geda_symbol_7400-1.html
delete mode 100644 docs/wiki/_detail/001geda_symbol_7400-1_hidden.html
delete mode 100644 docs/wiki/_detail/001geda_terminal_screenshot_001.html
delete mode 100644 docs/wiki/_detail/001tragesym_acroread_selectiontable.html
delete mode 100644 docs/wiki/_detail/001tragesym_gschem_finished.html
delete mode 100644 docs/wiki/_detail/001tragesym_gschem_showhidden.html
delete mode 100644 docs/wiki/_detail/001tragesym_kpdf_pinconfiguration.html
delete mode 100644 docs/wiki/_detail/001tragesym_kpdf_pindescription.html
delete mode 100644 docs/wiki/_detail/001tragesym_ooo_attributes.html
delete mode 100644 docs/wiki/_detail/001tragesym_ooo_changedpins.html
delete mode 100644 docs/wiki/_detail/001tragesym_ooo_rearanged.html
delete mode 100644 docs/wiki/_detail/001tragesym_ooo_selection.html
delete mode 100644 docs/wiki/_detail/001tragesym_xemacs_modifiedselection.html
delete mode 100644 docs/wiki/_detail/001tragesym_xemacs_rawselection.html
delete mode 100644 docs/wiki/_detail/Makefile.am
delete mode 100644 docs/wiki/_detail/devel_tips_dialog_picture.html
delete mode 100644 docs/wiki/_detail/geda_ambiguous1.html
delete mode 100644 docs/wiki/_detail/geda_ambiguous1_fixed.html
delete mode 100644 docs/wiki/_detail/geda_board-1.html
delete mode 100644 docs/wiki/_detail/geda_board-2.html
delete mode 100644 docs/wiki/_detail/geda_board-3.html
delete mode 100644 docs/wiki/_detail/geda_board-4.html
delete mode 100644 docs/wiki/_detail/geda_board-5.html
delete mode 100644 docs/wiki/_detail/geda_board-6.html
delete mode 100644 docs/wiki/_detail/geda_coordinatespace.html
delete mode 100644 docs/wiki/_detail/geda_design_flow.html
delete mode 100644 docs/wiki/_detail/geda_dialogdirective.html
delete mode 100644 docs/wiki/_detail/geda_dialoginclude.html
delete mode 100644 docs/wiki/_detail/geda_dialogmodel.html
delete mode 100644 docs/wiki/_detail/geda_dialogtrans.html
delete mode 100644 docs/wiki/_detail/geda_dialogvac.html
delete mode 100644 docs/wiki/_detail/geda_dialogvdc1.html
delete mode 100644 docs/wiki/_detail/geda_faq_attrib.html
delete mode 100644 docs/wiki/_detail/geda_fileformat_textgraphic.html
delete mode 100644 docs/wiki/_detail/geda_geda_flow.html
delete mode 100644 docs/wiki/_detail/geda_gschem-sym-1.html
delete mode 100644 docs/wiki/_detail/geda_gschem-sym-2.html
delete mode 100644 docs/wiki/_detail/geda_gschem-sym-3.html
delete mode 100644 docs/wiki/_detail/geda_gschem_screenshot_001.html
delete mode 100644 docs/wiki/_detail/geda_gschem_workflow_01.html
delete mode 100644 docs/wiki/_detail/geda_net.html
delete mode 100644 docs/wiki/_detail/geda_nets.html
delete mode 100644 docs/wiki/_detail/geda_one-sch-1.html
delete mode 100644 docs/wiki/_detail/geda_one-sch-2.html
delete mode 100644 docs/wiki/_detail/geda_one-sch-3.html
delete mode 100644 docs/wiki/_detail/geda_pcb-el-1.html
delete mode 100644 docs/wiki/_detail/geda_pcb-el-2.html
delete mode 100644 docs/wiki/_detail/geda_rf_cascade_figure1.html
delete mode 100644 docs/wiki/_detail/geda_rf_cascade_figure2.html
delete mode 100644 docs/wiki/_detail/geda_schematicfinished2.html
delete mode 100644 docs/wiki/_detail/geda_simple1.html
delete mode 100644 docs/wiki/_detail/geda_status_screenshot.html
delete mode 100644 docs/wiki/_detail/geda_suse_electronics_menu.html
delete mode 100644 docs/wiki/_detail/geda_switcap_figure1.html
delete mode 100644 docs/wiki/_detail/geda_switcap_figure2.html
delete mode 100644 docs/wiki/_detail/geda_switcap_figure3.html
delete mode 100644 docs/wiki/_detail/geda_switcap_figure4.html
delete mode 100644 docs/wiki/_detail/geda_symbol_7400-1.html
delete mode 100644 docs/wiki/_detail/geda_symbol_7400-1_hidden.html
delete mode 100644 docs/wiki/_detail/geda_terminal_screenshot_001.html
delete mode 100644 docs/wiki/_detail/geda_two-sch-1.html
delete mode 100644 docs/wiki/_detail/geda_two-sch-2.html
delete mode 100644 docs/wiki/_detail/geda_warmup_add_component.html
delete mode 100644 docs/wiki/_detail/geda_warmup_gschem01.html
delete mode 100644 docs/wiki/_detail/geda_warmup_gschem02.html
delete mode 100644 docs/wiki/_detail/geda_warmup_gschem03.html
delete mode 100644 docs/wiki/_detail/tragesym_acroread_selectiontable.html
delete mode 100644 docs/wiki/_detail/tragesym_gschem_finished.html
delete mode 100644 docs/wiki/_detail/tragesym_gschem_showhidden.html
delete mode 100644 docs/wiki/_detail/tragesym_kpdf_pinconfiguration.html
delete mode 100644 docs/wiki/_detail/tragesym_kpdf_pindescription.html
delete mode 100644 docs/wiki/_detail/tragesym_ooo_attributes.html
delete mode 100644 docs/wiki/_detail/tragesym_ooo_changedpins.html
delete mode 100644 docs/wiki/_detail/tragesym_ooo_rearanged.html
delete mode 100644 docs/wiki/_detail/tragesym_ooo_selection.html
delete mode 100644 docs/wiki/_detail/tragesym_xemacs_modifiedselection.html
delete mode 100644 docs/wiki/_detail/tragesym_xemacs_rawselection.html
delete mode 100644 docs/wiki/_media/.gitignore
delete mode 100644 docs/wiki/_media/Makefile.am
create mode 100644 docs/wiki/design.css
delete mode 100644 docs/wiki/docs_20060124_gschem_ug_app_a.html
delete mode 100644 docs/wiki/docs_20060124_gschem_ug_app_b.html
delete mode 100644 docs/wiki/docs_20060124_gschem_ug_app_c.html
delete mode 100644 docs/wiki/docs_20060124_gschem_ug_components_symbols_objects_attributes.html
delete mode 100644 docs/wiki/docs_20060124_gschem_ug_electrical_connectivity.html
delete mode 100644 docs/wiki/docs_20060124_gschem_ug_how_to_ask_questions.html
delete mode 100644 docs/wiki/docs_20060124_gschem_ug_installing_gschem.html
delete mode 100644 docs/wiki/docs_20060124_gschem_ug_resources.html
delete mode 100644 docs/wiki/docs_20060124_gschem_ug_the_main_window.html
delete mode 100644 docs/wiki/docs_20060124_gschem_ug_the_status_window.html
create mode 100644 docs/wiki/geda-bom_readme.html
rename docs/wiki/{geda_circuit_simulation_improvements.html => geda-circuit_simulation_improvements.html} (90%)
rename docs/wiki/{geda_covered_mp.html => geda-covered_mp.html} (86%)
rename docs/wiki/{geda_csygas.html => geda-csygas.html} (97%)
rename docs/wiki/{geda_cygwin.html => geda-cygwin.html} (62%)
rename docs/wiki/{geda_data_plotting_improvements.html => geda-data_plotting_improvements.html} (80%)
rename docs/wiki/{geda_data_structure_design_discussion.html => geda-data_structure_design_discussion.html} (86%)
create mode 100644 docs/wiki/geda-debian.fr.html
create mode 100644 docs/wiki/geda-debian.html
rename docs/wiki/{geda_design_flow_and_hierarchy_roadmap.html => geda-design_flow_and_hierarchy_roadmap.html} (89%)
create mode 100644 docs/wiki/geda-design_flow_roadmap.html
rename docs/wiki/{geda_devel-tips.html => geda-devel-tips.html} (77%)
create mode 100644 docs/wiki/geda-devmacosx.html
create mode 100644 docs/wiki/geda-documentation.fr.html
create mode 100644 docs/wiki/geda-documentation.html
create mode 100644 docs/wiki/geda-eagle_pcb_netlister_readme.html
rename docs/wiki/{geda_example_hsm.html => geda-example_hsm.html} (77%)
rename docs/wiki/{geda_example_usbjtag.html => geda-example_usbjtag.html} (63%)
create mode 100644 docs/wiki/geda-experiences.html
rename docs/wiki/{001geda_faq-attribs.html => geda-faq-attribs.fr.html} (88%)
rename docs/wiki/{geda_faq-attribs.html => geda-faq-attribs.html} (70%)
rename docs/wiki/{001geda_faq-gnetlist.html => geda-faq-gnetlist.fr.html} (73%)
rename docs/wiki/{geda_faq-gnetlist.html => geda-faq-gnetlist.html} (77%)
rename docs/wiki/{001geda_faq-gsch2pcb.html => geda-faq-gsch2pcb.fr.html} (69%)
rename docs/wiki/{geda_faq-gsch2pcb.html => geda-faq-gsch2pcb.html} (64%)
rename docs/wiki/{001geda_faq-gschem.html => geda-faq-gschem.fr.html} (88%)
rename docs/wiki/{geda_faq-gschem.html => geda-faq-gschem.html} (80%)
rename docs/wiki/{geda_faq-pcb.html => geda-faq-pcb.html} (75%)
rename docs/wiki/{001geda_faq-simulation.html => geda-faq-simulation.fr.html} (90%)
rename docs/wiki/{geda_faq-simulation.html => geda-faq-simulation.html} (89%)
rename docs/wiki/{001geda_faq.html => geda-faq.fr.html} (86%)
rename docs/wiki/{geda_faq.html => geda-faq.html} (76%)
rename docs/wiki/{geda_fbabgapp.html => geda-fbabgapp.html} (87%)
create mode 100644 docs/wiki/geda-fc1.html
create mode 100644 docs/wiki/geda-fc2.html
create mode 100644 docs/wiki/geda-fc3.html
rename docs/wiki/{geda_fc4.html => geda-fc4.html} (82%)
rename docs/wiki/{geda_fedora_rpm_installation.html => geda-fedora_rpm_installation.html} (83%)
rename docs/wiki/{geda_file_format_spec.html => geda-file_format_spec.html} (76%)
create mode 100644 docs/wiki/geda-format_translation.html
rename docs/wiki/{geda_gattrib_readme.html => geda-gattrib_readme.html} (80%)
create mode 100644 docs/wiki/geda-gedasuite_installation.html
rename docs/wiki/{geda_gerbv_mp.html => geda-gerbv_mp.html} (88%)
rename docs/wiki/{geda_gerbv_pnp_readme.html => geda-gerbv_pnp_readme.html} (80%)
rename docs/wiki/{geda_gfdl.html => geda-gfdl.html} (94%)
copy docs/wiki/{geda_glossaire.html => geda-glossaire.fr.html} (86%)
rename docs/wiki/{geda_glossaire.html => geda-glossary.fr.html} (86%)
rename docs/wiki/{geda_glossary.html => geda-glossary.html} (73%)
rename docs/wiki/{geda_gnetlist_mp.html => geda-gnetlist_mp.html} (84%)
rename docs/wiki/{geda_gnetlist_ug.html => geda-gnetlist_ug.html} (86%)
rename docs/wiki/{geda_grcsan.html => geda-grcsan.html} (83%)
create mode 100644 docs/wiki/geda-grenum_mp.html
rename docs/wiki/{geda_gsch2pcb_readme.html => geda-gsch2pcb_readme.html} (80%)
rename docs/wiki/{geda_gsch2pcb_tutorial.html => geda-gsch2pcb_tutorial.html} (83%)
rename docs/wiki/{geda_gsch2pcb_tutorial_releasenotes.html => geda-gsch2pcb_tutorial_releasenotes.html} (65%)
copy gnetlist/docs/README.pcb => docs/wiki/geda-gschem2pcb_readme.html (80%)
rename docs/wiki/{geda_gschem_mp.html => geda-gschem_mp.html} (75%)
rename docs/wiki/{001geda_gschem_ug.html => geda-gschem_ug.fr.html} (94%)
rename docs/wiki/{geda_gschem_ug.html => geda-gschem_ug.html} (87%)
rename docs/wiki/{geda_gschem_warmup.html => geda-gschem_warmup.html} (67%)
create mode 100644 docs/wiki/geda-gsymcheck_mp.html
create mode 100644 docs/wiki/geda-gtkwave_lxt2miner_mp.html
create mode 100644 docs/wiki/geda-gtkwave_lxt2vcd_mp.html
rename docs/wiki/{geda_gtkwave_mp.html => geda-gtkwave_mp.html} (74%)
create mode 100644 docs/wiki/geda-gtkwave_mvl2lxt_mp.html
create mode 100644 docs/wiki/geda-gtkwave_mvl2vcd_mp.html
create mode 100644 docs/wiki/geda-gtkwave_tex2vcd_mp.html
create mode 100644 docs/wiki/geda-gtkwave_tla2vcd_mp.html
rename docs/wiki/{geda_gtkwave_vcd2lxt2_mp.html => geda-gtkwave_vcd2lxt2_mp.html} (64%)
rename docs/wiki/{geda_gtkwave_vcd2lxt_mp.html => geda-gtkwave_vcd2lxt_mp.html} (65%)
rename docs/wiki/{geda_gtkwave_vcd2vzt_mp.html => geda-gtkwave_vcd2vzt_mp.html} (68%)
create mode 100644 docs/wiki/geda-gtkwave_vzt2vcd_mp.html
create mode 100644 docs/wiki/geda-gtkwave_vztminer_mp.html
rename docs/wiki/{geda_guile_scripting.html => geda-guile_scripting.html} (78%)
rename docs/wiki/{geda_hse_howto.html => geda-hse_howto.html} (78%)
rename docs/wiki/{geda_icarus_anc.html => geda-icarus_anc.html} (71%)
rename docs/wiki/{geda_icarus_extensions.html => geda-icarus_extensions.html} (71%)
create mode 100644 docs/wiki/geda-icarus_glossary.html
rename docs/wiki/{geda_icarus_ieee1364.html => geda-icarus_ieee1364.html} (94%)
rename docs/wiki/{geda_icarus_mp.html => geda-icarus_mp.html} (92%)
rename docs/wiki/{geda_icarus_opcodes.html => geda-icarus_opcodes.html} (95%)
rename docs/wiki/{geda_icarus_quick_start.html => geda-icarus_quick_start.html} (71%)
rename docs/wiki/{geda_icarus_readme.html => geda-icarus_readme.html} (93%)
rename docs/wiki/{geda_icarus_vpi_mp.html => geda-icarus_vpi_mp.html} (76%)
rename docs/wiki/{geda_icarus_vpi_within_vvp.html => geda-icarus_vpi_within_vvp.html} (84%)
rename docs/wiki/{geda_icarus_vvp_runtime.html => geda-icarus_vvp_runtime.html} (82%)
rename docs/wiki/{geda_icarus_vvp_simulation.html => geda-icarus_vvp_simulation.html} (97%)
rename docs/wiki/{geda_icarus_xilinx_hints.html => geda-icarus_xilinx_hints.html} (75%)
rename docs/wiki/{geda_icarus_xnf.html => geda-icarus_xnf.html} (90%)
rename docs/wiki/{geda_igarus_fpga_lcg.html => geda-igarus_fpga_lcg.html} (85%)
rename docs/wiki/{001geda_installation.html => geda-installation.fr.html} (89%)
rename docs/wiki/{geda_installation.html => geda-installation.html} (55%)
rename docs/wiki/{geda_installed_plugins.html => geda-installed_plugins.html} (61%)
rename docs/wiki/{geda_kig_howto.html => geda-kig_howto.html} (87%)
rename docs/wiki/{geda_master_attributes_list.html => geda-master_attributes_list.html} (87%)
create mode 100644 docs/wiki/geda-mcalc_readme.html
rename docs/wiki/{geda_na_howto.html => geda-na_howto.html} (88%)
rename docs/wiki/{geda_ngnutmeg_mp.html => geda-ngnutmeg_mp.html} (97%)
rename docs/wiki/{geda_ngsconvert_mp.html => geda-ngsconvert_mp.html} (76%)
rename docs/wiki/{geda_ngspice_and_gschem.html => geda-ngspice_and_gschem.html} (68%)
rename docs/wiki/{geda_ngspice_mp.html => geda-ngspice_mp.html} (91%)
rename docs/wiki/{geda_olib_readme.html => geda-olib_readme.html} (79%)
rename docs/wiki/{001geda_pcb-quick_reference.html => geda-pcb-quick_reference.fr.html} (93%)
rename docs/wiki/{geda_pcb-quick_reference.html => geda-pcb-quick_reference.html} (92%)
rename docs/wiki/{geda_pcb_footprints.html => geda-pcb_footprints.html} (51%)
create mode 100644 docs/wiki/geda-pcb_funding_sow-fwdann_ideas.html
create mode 100644 docs/wiki/geda-pcb_funding_sow-gui_ideas.html
create mode 100644 docs/wiki/geda-pcb_funding_sow.html
create mode 100644 docs/wiki/geda-pcb_mp.html
rename docs/wiki/{001geda_pcb_tips.html => geda-pcb_tips.fr.html} (94%)
rename docs/wiki/{geda_pcb_tips.html => geda-pcb_tips.html} (70%)
create mode 100644 docs/wiki/geda-release_engineering.html
copy docs/wiki/{geda_scg.html => geda-scg.fr.html} (94%)
rename docs/wiki/{geda_scg.html => geda-scg.html} (92%)
rename docs/wiki/{geda_scm.html => geda-scm.html} (72%)
rename docs/wiki/{geda_sdb_howto.html => geda-sdb_howto.html} (96%)
copy gnetlist/docs/README.switcap => docs/wiki/geda-sn_readme.html (80%)
create mode 100644 docs/wiki/geda-spice_improvements.html
rename docs/wiki/{geda_ssan.html => geda-ssan.html} (89%)
create mode 100644 docs/wiki/geda-start.html
rename docs/wiki/{geda_style_guide.html => geda-style_guide.html} (88%)
rename docs/wiki/{geda_suse_10.html => geda-suse_10.0.html} (61%)
create mode 100644 docs/wiki/geda-suse_10.1.html
create mode 100644 docs/wiki/geda-suse_9.3.html
rename docs/wiki/{geda_suse_rpm_installation.html => geda-suse_rpm_installation.html} (56%)
rename docs/wiki/{geda_syntax_features.html => geda-syntax_features.html} (76%)
rename docs/wiki/{geda_systemc_netlister_readme.html => geda-systemc_netlister_readme.html} (65%)
rename docs/wiki/{geda_tasks.html => geda-tasks.html} (63%)
create mode 100644 docs/wiki/geda-todos.html
create mode 100644 docs/wiki/geda-todos_historical.html
create mode 100644 docs/wiki/geda-tragesym_readme.html
rename docs/wiki/{001geda_tragesym_tutorial.html => geda-tragesym_tutorial.fr.html} (74%)
rename docs/wiki/{geda_tragesym_tutorial.html => geda-tragesym_tutorial.html} (76%)
copy docs/wiki/{geda_transistor_guide.html => geda-transistor_guide.html} (89%)
create mode 100644 docs/wiki/geda-ubuntu.html
rename docs/wiki/{001geda_usage.html => geda-usage.fr.html} (89%)
rename docs/wiki/{geda_usage.html => geda-usage.html} (89%)
rename docs/wiki/{geda_vams_netlister_readme.html => geda-vams_netlister_readme.html} (94%)
rename docs/wiki/{geda_verilog_netlister_readme.html => geda-verilog_netlister_readme.html} (92%)
create mode 100644 docs/wiki/geda-version_control_migration.html
create mode 100644 docs/wiki/geda-vhdl_netlister_readme.html
create mode 100644 docs/wiki/geda-wcalc_mp.html
create mode 100644 docs/wiki/geda-wcalc_readme.html
rename docs/wiki/{geda_wcalc_stdio_mp.html => geda-wcalc_stdio_mp.html} (61%)
create mode 100644 docs/wiki/geda-wip-clipboard.html
create mode 100644 docs/wiki/geda-xml_file_formats.html
delete mode 100644 docs/wiki/geda_bill_wilson_s.html
delete mode 100644 docs/wiki/geda_bom_readme.html
delete mode 100644 docs/wiki/geda_covered_rv.html
delete mode 100644 docs/wiki/geda_debian.html
delete mode 100644 docs/wiki/geda_documentation.html
delete mode 100644 docs/wiki/geda_eagle_pcb_netlister_readme.html
delete mode 100644 docs/wiki/geda_fc1.html
delete mode 100644 docs/wiki/geda_fc2.html
delete mode 100644 docs/wiki/geda_fc3.html
delete mode 100644 docs/wiki/geda_footprint_creation.html
delete mode 100644 docs/wiki/geda_gedasuite_installation.html
delete mode 100644 docs/wiki/geda_grenum_mp.html
delete mode 100644 docs/wiki/geda_gschem2pcb_readme.html
delete mode 100644 docs/wiki/geda_gsymcheck_mp.html
delete mode 100644 docs/wiki/geda_gtkwave_lxt2miner_mp.html
delete mode 100644 docs/wiki/geda_gtkwave_lxt2vcd_mp.html
delete mode 100644 docs/wiki/geda_gtkwave_mvl2lxt_mp.html
delete mode 100644 docs/wiki/geda_gtkwave_mvl2vcd_mp.html
delete mode 100644 docs/wiki/geda_gtkwave_tex2vcd_mp.html
delete mode 100644 docs/wiki/geda_gtkwave_tla2vcd_mp.html
delete mode 100644 docs/wiki/geda_gtkwave_vzt2vcd_mp.html
delete mode 100644 docs/wiki/geda_gtkwave_vztminer_mp.html
delete mode 100644 docs/wiki/geda_icarus_glossary.html
delete mode 100644 docs/wiki/geda_mcalc_readme.html
delete mode 100644 docs/wiki/geda_pcb.html
delete mode 100644 docs/wiki/geda_pcb_mp.html
delete mode 100644 docs/wiki/geda_pcb_ug.html
delete mode 100644 docs/wiki/geda_release_engineering.html
delete mode 100644 docs/wiki/geda_sn_readme.html
delete mode 100644 docs/wiki/geda_suse_9.html
delete mode 100644 docs/wiki/geda_todos.html
delete mode 100644 docs/wiki/geda_tragesym_readme.html
delete mode 100644 docs/wiki/geda_ubuntu.html
delete mode 100644 docs/wiki/geda_vhdl_netlister_readme.html
delete mode 100644 docs/wiki/geda_wcalc_mp.html
delete mode 100644 docs/wiki/geda_wcalc_readme.html
create mode 100644 docs/wiki/gsoc2009.html
copy docs/wiki/{gsoc2008_projects.html => gsoc2009_projects.html} (57%)
create mode 100644 docs/wiki/gtkwave-projects.html
copy docs/wiki/{ => images}/.gitignore (100%)
create mode 100644 docs/wiki/images/Makefile.am
create mode 100644 docs/wiki/images/bullet.gif
create mode 100644 docs/wiki/images/button-cc.gif
create mode 100644 docs/wiki/images/button-css.png
create mode 100644 docs/wiki/images/button-donate.gif
create mode 100644 docs/wiki/images/button-dw.png
create mode 100644 docs/wiki/images/button-php.gif
create mode 100644 docs/wiki/images/button-rss.png
create mode 100644 docs/wiki/images/button-xhtml.png
rename docs/wiki/{lib/tpl/geda => }/images/closed.gif (100%)
rename docs/wiki/{lib => }/images/interwiki.png (100%)
copy docs/wiki/{ => images/interwiki}/.gitignore (100%)
create mode 100644 docs/wiki/images/interwiki/Makefile.am
copy docs/wiki/{lib => }/images/interwiki/amazon.de.gif (100%)
copy docs/wiki/{lib/images/interwiki/amazon.de.gif => images/interwiki/amazon.gif} (100%)
copy docs/wiki/{lib/images/interwiki/amazon.de.gif => images/interwiki/amazon.uk.gif} (100%)
rename docs/wiki/{lib/images/interwiki/dokubug.gif => images/interwiki/bug.gif} (100%)
rename docs/wiki/{lib => }/images/interwiki/coral.gif (100%)
rename docs/wiki/{lib => }/images/interwiki/doku.gif (100%)
rename docs/wiki/{lib => }/images/interwiki/google.gif (100%)
rename docs/wiki/{lib => }/images/interwiki/meatball.gif (100%)
rename docs/wiki/{lib => }/images/interwiki/phpfn.gif (100%)
rename docs/wiki/{lib => }/images/interwiki/sb.gif (100%)
rename docs/wiki/{lib => }/images/interwiki/wiki.gif (100%)
copy docs/wiki/{lib => }/images/interwiki/wp.gif (100%)
copy docs/wiki/{lib/images/interwiki/wp.gif => images/interwiki/wpde.gif} (100%)
rename docs/wiki/{lib/images/interwiki/wp.gif => images/interwiki/wpmeta.gif} (100%)
rename docs/wiki/{lib/tpl/geda => }/images/link_icon.gif (100%)
rename docs/wiki/{lib/tpl/geda => }/images/mail_icon.gif (100%)
rename docs/wiki/{lib/tpl/geda => }/images/open.gif (100%)
copy docs/wiki/{ => images/smileys}/.gitignore (100%)
create mode 100644 docs/wiki/images/smileys/Makefile.am
create mode 100644 docs/wiki/images/smileys/delete.gif
rename docs/wiki/{lib => }/images/smileys/fixme.gif (100%)
create mode 100644 docs/wiki/images/smileys/icon_arrow.gif
create mode 100644 docs/wiki/images/smileys/icon_biggrin.gif
create mode 100644 docs/wiki/images/smileys/icon_confused.gif
create mode 100644 docs/wiki/images/smileys/icon_cool.gif
create mode 100644 docs/wiki/images/smileys/icon_cry.gif
create mode 100644 docs/wiki/images/smileys/icon_doubt.gif
create mode 100644 docs/wiki/images/smileys/icon_doubt2.gif
create mode 100644 docs/wiki/images/smileys/icon_eek.gif
create mode 100644 docs/wiki/images/smileys/icon_evil.gif
create mode 100644 docs/wiki/images/smileys/icon_exclaim.gif
create mode 100644 docs/wiki/images/smileys/icon_frown.gif
create mode 100644 docs/wiki/images/smileys/icon_fun.gif
create mode 100644 docs/wiki/images/smileys/icon_idea.gif
rename docs/wiki/{lib/images/interwiki/amazon.de.gif => images/smileys/icon_kaddi.gif} (52%)
create mode 100644 docs/wiki/images/smileys/icon_lol.gif
create mode 100644 docs/wiki/images/smileys/icon_mrgreen.gif
create mode 100644 docs/wiki/images/smileys/icon_neutral.gif
create mode 100644 docs/wiki/images/smileys/icon_question.gif
create mode 100644 docs/wiki/images/smileys/icon_razz.gif
create mode 100644 docs/wiki/images/smileys/icon_redface.gif
create mode 100644 docs/wiki/images/smileys/icon_rolleyes.gif
create mode 100644 docs/wiki/images/smileys/icon_sad.gif
create mode 100644 docs/wiki/images/smileys/icon_silenced.gif
rename docs/wiki/{lib => }/images/smileys/icon_smile.gif (100%)
rename docs/wiki/{lib => }/images/smileys/icon_smile2.gif (100%)
create mode 100644 docs/wiki/images/smileys/icon_surprised.gif
create mode 100644 docs/wiki/images/smileys/icon_twisted.gif
rename docs/wiki/{lib => }/images/smileys/icon_wink.gif (100%)
rename docs/wiki/{lib/tpl/geda => }/images/tocdot2.gif (100%)
rename docs/wiki/{lib/tpl/geda => }/images/windows.gif (100%)
delete mode 100644 docs/wiki/lib/.gitignore
delete mode 100644 docs/wiki/lib/exe/.gitignore
delete mode 100644 docs/wiki/lib/exe/001css
delete mode 100644 docs/wiki/lib/exe/002css
delete mode 100644 docs/wiki/lib/exe/Makefile.am
delete mode 100644 docs/wiki/lib/exe/css
delete mode 100644 docs/wiki/lib/exe/opensearch
delete mode 100644 docs/wiki/lib/images/.gitignore
delete mode 100644 docs/wiki/lib/images/Makefile.am
delete mode 100644 docs/wiki/lib/images/error.png
delete mode 100644 docs/wiki/lib/images/fileicons/.gitignore
delete mode 100644 docs/wiki/lib/images/fileicons/Makefile.am
delete mode 100644 docs/wiki/lib/images/fileicons/deb.png
delete mode 100644 docs/wiki/lib/images/fileicons/doc.png
delete mode 100644 docs/wiki/lib/images/fileicons/file.png
delete mode 100644 docs/wiki/lib/images/fileicons/gif.png
delete mode 100644 docs/wiki/lib/images/fileicons/gz.png
delete mode 100644 docs/wiki/lib/images/fileicons/jpeg.png
delete mode 100644 docs/wiki/lib/images/fileicons/jpg.png
delete mode 100644 docs/wiki/lib/images/fileicons/odc.png
delete mode 100644 docs/wiki/lib/images/fileicons/odf.png
delete mode 100644 docs/wiki/lib/images/fileicons/odg.png
delete mode 100644 docs/wiki/lib/images/fileicons/odi.png
delete mode 100644 docs/wiki/lib/images/fileicons/odp.png
delete mode 100644 docs/wiki/lib/images/fileicons/ods.png
delete mode 100644 docs/wiki/lib/images/fileicons/odt.png
delete mode 100644 docs/wiki/lib/images/fileicons/pdf.png
delete mode 100644 docs/wiki/lib/images/fileicons/png.png
delete mode 100644 docs/wiki/lib/images/fileicons/ppt.png
delete mode 100644 docs/wiki/lib/images/fileicons/ps.png
delete mode 100644 docs/wiki/lib/images/fileicons/rar.png
delete mode 100644 docs/wiki/lib/images/fileicons/rpm.png
delete mode 100644 docs/wiki/lib/images/fileicons/rtf.png
delete mode 100644 docs/wiki/lib/images/fileicons/src.png
delete mode 100644 docs/wiki/lib/images/fileicons/swf.png
delete mode 100644 docs/wiki/lib/images/fileicons/sxc.png
delete mode 100644 docs/wiki/lib/images/fileicons/sxd.png
delete mode 100644 docs/wiki/lib/images/fileicons/sxi.png
delete mode 100644 docs/wiki/lib/images/fileicons/sxw.png
delete mode 100644 docs/wiki/lib/images/fileicons/tar.png
delete mode 100644 docs/wiki/lib/images/fileicons/tgz.png
delete mode 100644 docs/wiki/lib/images/fileicons/xls.png
delete mode 100644 docs/wiki/lib/images/fileicons/zip.png
delete mode 100644 docs/wiki/lib/images/info.png
delete mode 100644 docs/wiki/lib/images/interwiki/.gitignore
delete mode 100644 docs/wiki/lib/images/interwiki/Makefile.am
delete mode 100644 docs/wiki/lib/images/interwiki/amazon.gif
delete mode 100644 docs/wiki/lib/images/interwiki/amazon.uk.gif
delete mode 100644 docs/wiki/lib/images/interwiki/wpde.gif
delete mode 100644 docs/wiki/lib/images/interwiki/wpmeta.gif
delete mode 100644 docs/wiki/lib/images/notify.png
delete mode 100644 docs/wiki/lib/images/smileys/.gitignore
delete mode 100644 docs/wiki/lib/images/smileys/Makefile.am
delete mode 100644 docs/wiki/lib/images/success.png
delete mode 100644 docs/wiki/lib/plugins/.gitignore
delete mode 100644 docs/wiki/lib/plugins/Makefile.am
delete mode 100644 docs/wiki/lib/plugins/definitionlist/.gitignore
delete mode 100644 docs/wiki/lib/plugins/definitionlist/Makefile.am
delete mode 100644 docs/wiki/lib/plugins/definitionlist/images/.gitignore
delete mode 100644 docs/wiki/lib/plugins/definitionlist/images/Makefile.am
delete mode 100644 docs/wiki/lib/plugins/definitionlist/images/bullet.gif
delete mode 100644 docs/wiki/lib/plugins/note/.gitignore
delete mode 100644 docs/wiki/lib/plugins/note/images/.gitignore
delete mode 100644 docs/wiki/lib/plugins/note/images/Makefile.am
delete mode 100644 docs/wiki/lib/plugins/note/images/important.png
delete mode 100644 docs/wiki/lib/plugins/note/images/note.png
delete mode 100644 docs/wiki/lib/plugins/note/images/tip.png
delete mode 100644 docs/wiki/lib/plugins/note/images/warning.png
delete mode 100644 docs/wiki/lib/tpl/.gitignore
delete mode 100644 docs/wiki/lib/tpl/geda/Makefile.am
delete mode 100644 docs/wiki/lib/tpl/geda/images/Makefile.am
delete mode 100644 docs/wiki/lib/tpl/geda/images/buttonshadow.png
delete mode 100644 docs/wiki/lib/tpl/geda/images/favicon
delete mode 100644 docs/wiki/lib/tpl/geda/images/inputshadow.png
create mode 100644 docs/wiki/libgeda3_object_based_design.html
copy docs/wiki/{ => media}/.gitignore (100%)
create mode 100644 docs/wiki/media/Makefile.am
copy docs/wiki/{ => media/devel_tips}/.gitignore (100%)
rename docs/wiki/{lib/plugins/note => media/devel_tips}/Makefile.am (55%)
rename docs/wiki/{_media/devel_tips_dialog_picture.png => media/devel_tips/dialog_picture.png} (100%)
copy docs/wiki/{ => media/geda}/.gitignore (100%)
create mode 100644 docs/wiki/media/geda/Makefile.am
rename docs/wiki/{_media/geda_ambiguous1.png => media/geda/ambiguous1.png} (100%)
rename docs/wiki/{_media/geda_ambiguous1_fixed.png => media/geda/ambiguous1_fixed.png} (100%)
rename docs/wiki/{_media/geda_board-1.png => media/geda/board-1.png} (100%)
rename docs/wiki/{_media/geda_board-2.png => media/geda/board-2.png} (100%)
rename docs/wiki/{_media/geda_board-3.png => media/geda/board-3.png} (100%)
rename docs/wiki/{_media/geda_board-4.png => media/geda/board-4.png} (100%)
rename docs/wiki/{_media/geda_board-5.png => media/geda/board-5.png} (100%)
rename docs/wiki/{_media/geda_board-6.png => media/geda/board-6.png} (100%)
rename docs/wiki/{_media/geda_coordinatespace.jpg => media/geda/coordinatespace.jpg} (100%)
rename docs/wiki/{_media/geda_design_flow.jpg => media/geda/design_flow.jpg} (100%)
rename docs/wiki/{_media/geda_dialogdirective.png => media/geda/dialogdirective.png} (100%)
rename docs/wiki/{_media/geda_dialoginclude.png => media/geda/dialoginclude.png} (100%)
rename docs/wiki/{_media/geda_dialogmodel.png => media/geda/dialogmodel.png} (100%)
rename docs/wiki/{_media/geda_dialogtrans.png => media/geda/dialogtrans.png} (100%)
rename docs/wiki/{_media/geda_dialogvac.png => media/geda/dialogvac.png} (100%)
rename docs/wiki/{_media/geda_dialogvdc1.png => media/geda/dialogvdc1.png} (100%)
rename docs/wiki/{_media/geda_faq_attrib.jpg => media/geda/faq_attrib.jpg} (100%)
rename docs/wiki/{_media/geda_fileformat_textgraphic.jpg => media/geda/fileformat_textgraphic.jpg} (100%)
rename docs/wiki/{_media/geda_geda_flow.png => media/geda/geda_flow.png} (100%)
rename docs/wiki/{_media/geda_gschem-sym-1.png => media/geda/gschem-sym-1.png} (100%)
rename docs/wiki/{_media/geda_gschem-sym-2.png => media/geda/gschem-sym-2.png} (100%)
rename docs/wiki/{_media/geda_gschem-sym-3.png => media/geda/gschem-sym-3.png} (100%)
rename docs/wiki/{_media/geda_gschem_screenshot_001.jpg => media/geda/gschem_screenshot_001.jpg} (100%)
rename docs/wiki/{_media/geda_gschem_workflow_01.jpg => media/geda/gschem_workflow_01.jpg} (100%)
rename docs/wiki/{_media/geda_net.jpg => media/geda/net.jpg} (100%)
rename docs/wiki/{_media/geda_nets.jpg => media/geda/nets.jpg} (100%)
rename docs/wiki/{_media/geda_one-sch-1.png => media/geda/one-sch-1.png} (100%)
rename docs/wiki/{_media/geda_one-sch-2.png => media/geda/one-sch-2.png} (100%)
rename docs/wiki/{_media/geda_one-sch-3.png => media/geda/one-sch-3.png} (100%)
create mode 100644 docs/wiki/media/geda/paper1.gif
create mode 100644 docs/wiki/media/geda/path_example_and_gate-smaller.png
create mode 100644 docs/wiki/media/geda/path_example_and_gate.png
rename docs/wiki/{_media/geda_pcb-el-1.png => media/geda/pcb-el-1.png} (100%)
rename docs/wiki/{_media/geda_pcb-el-2.png => media/geda/pcb-el-2.png} (100%)
rename docs/wiki/{_media/geda_rf_cascade_figure1.jpg => media/geda/rf_cascade_figure1.jpg} (100%)
rename docs/wiki/{_media/geda_rf_cascade_figure2.jpg => media/geda/rf_cascade_figure2.jpg} (100%)
create mode 100644 docs/wiki/media/geda/schematicfinished.png
rename docs/wiki/{_media/geda_schematicfinished2.png => media/geda/schematicfinished2.png} (100%)
rename docs/wiki/{_media/geda_simple1.png => media/geda/simple1.png} (100%)
rename docs/wiki/{_media/geda_status_screenshot.jpg => media/geda/status_screenshot.jpg} (100%)
rename docs/wiki/{_media/geda_suse_electronics_menu.png => media/geda/suse_electronics_menu.png} (100%)
rename docs/wiki/{_media/geda_switcap_figure1.jpg => media/geda/switcap_figure1.jpg} (100%)
rename docs/wiki/{_media/geda_switcap_figure2.jpg => media/geda/switcap_figure2.jpg} (100%)
rename docs/wiki/{_media/geda_switcap_figure3.jpg => media/geda/switcap_figure3.jpg} (100%)
rename docs/wiki/{_media/geda_switcap_figure4.jpg => media/geda/switcap_figure4.jpg} (100%)
rename docs/wiki/{_media/geda_symbol_7400-1.png => media/geda/symbol_7400-1.png} (100%)
rename docs/wiki/{_media/geda_symbol_7400-1_hidden.png => media/geda/symbol_7400-1_hidden.png} (100%)
rename docs/wiki/{_media/geda_terminal_screenshot_001.jpg => media/geda/terminal_screenshot_001.jpg} (100%)
rename docs/wiki/{_media/geda_two-sch-1.png => media/geda/two-sch-1.png} (100%)
rename docs/wiki/{_media/geda_two-sch-2.png => media/geda/two-sch-2.png} (100%)
rename docs/wiki/{_media/geda_warmup_add_component.png => media/geda/warmup_add_component.png} (100%)
rename docs/wiki/{_media/geda_warmup_gschem01.png => media/geda/warmup_gschem01.png} (100%)
rename docs/wiki/{_media/geda_warmup_gschem02.png => media/geda/warmup_gschem02.png} (100%)
rename docs/wiki/{_media/geda_warmup_gschem03.png => media/geda/warmup_gschem03.png} (100%)
copy docs/wiki/{ => media/tragesym}/.gitignore (100%)
create mode 100644 docs/wiki/media/tragesym/Makefile.am
rename docs/wiki/{_media/tragesym_acroread_selectiontable.png => media/tragesym/acroread_selectiontable.png} (100%)
rename docs/wiki/{_media/tragesym_gschem_finished.png => media/tragesym/gschem_finished.png} (100%)
rename docs/wiki/{_media/tragesym_gschem_showhidden.png => media/tragesym/gschem_showhidden.png} (100%)
rename docs/wiki/{_media/tragesym_kpdf_pinconfiguration.png => media/tragesym/kpdf_pinconfiguration.png} (100%)
copy docs/wiki/{_media/tragesym_kpdf_pindescription.png => media/tragesym/kpdf_pindescription.png} (100%)
rename docs/wiki/{_media/tragesym_ooo_attributes.png => media/tragesym/ooo_attributes.png} (100%)
rename docs/wiki/{_media/tragesym_ooo_changedpins.png => media/tragesym/ooo_changedpins.png} (100%)
rename docs/wiki/{_media/tragesym_ooo_rearanged.png => media/tragesym/ooo_rearanged.png} (100%)
rename docs/wiki/{_media/tragesym_ooo_selection.png => media/tragesym/ooo_selection.png} (100%)
rename docs/wiki/{_media/001tragesym_template => media/tragesym/template.ods} (100%)
rename docs/wiki/{_media/tragesym_template => media/tragesym/template.txt} (100%)
rename docs/wiki/{_media/tragesym_template2 => media/tragesym/template2.ods} (100%)
rename docs/wiki/{_media/tragesym_template2.txt.txt => media/tragesym/template2.txt.src} (100%)
copy docs/wiki/{ => media/tragesym/tragesym}/.gitignore (100%)
rename docs/wiki/{lib => media/tragesym/tragesym}/Makefile.am (52%)
rename docs/wiki/{_media/tragesym_kpdf_pindescription.png => media/tragesym/tragesym/kpdf_pindescription.png} (100%)
rename docs/wiki/{_media/tragesym_xemacs_modifiedselection.png => media/tragesym/xemacs_modifiedselection.png} (100%)
rename docs/wiki/{_media/tragesym_xemacs_rawselection.png => media/tragesym/xemacs_rawselection.png} (100%)
copy docs/wiki/{ => media}/wiki/.gitignore (100%)
rename docs/wiki/{lib/tpl => media/wiki}/Makefile.am (58%)
create mode 100644 docs/wiki/media/wiki/dokuwiki-128.png
create mode 100644 docs/wiki/playground-playground.html
rename docs/wiki/{geda_transistor_guide.html => playground-transistor_guide.html} (86%)
create mode 100644 docs/wiki/print.css
create mode 100644 docs/wiki/start.html
create mode 100644 docs/wiki/style.css
create mode 100644 docs/wiki/wiki-dokuwiki.html
create mode 100644 docs/wiki/wiki-syntax.html
=================
Commit Messages
=================
commit 3edef9ffb6ebb859213efea337e3bd419b99da8e
Author: Ales Hvezda <ahvezda@xxxxxxxx>
Commit: Ales Hvezda <ahvezda@xxxxxxxx>
Spacing tweak
:100644 100644 c7090c5... 0edb800... M configure.ac
commit b7ca06041ea464b0d064bfa965843d2907a83571
Author: Ales Hvezda <ahvezda@xxxxxxxx>
Commit: Ales Hvezda <ahvezda@xxxxxxxx>
Updated the wiki docs from the online version (in prep for the next release)
(Un)fortunately, the previous mechanism for updating the wiki offline
docs from the online version is completely broken now (due to a segfault
in an external tool), so a new mechanism was used to download the files.
The good news is that the number of files and directories that need to
be downloaded has been reduced considerably. This is the first cut
of the wiki sync.
:100644 100644 7a2cb31... c7090c5... M configure.ac
:100644 000000 d5c32fb... 0000000... D docs/wiki/001geda_debian.html
:100644 000000 ef342a6... 0000000... D docs/wiki/001geda_documentation.html
:100644 000000 041af9a... 0000000... D docs/wiki/001geda_faq-attribs.html
:100644 000000 ee67599... 0000000... D docs/wiki/001geda_faq-gnetlist.html
:100644 000000 36b9b46... 0000000... D docs/wiki/001geda_faq-gsch2pcb.html
:100644 000000 3e61c60... 0000000... D docs/wiki/001geda_faq-gschem.html
:100644 000000 dda1230... 0000000... D docs/wiki/001geda_faq-simulation.html
:100644 000000 8ddc4e9... 0000000... D docs/wiki/001geda_faq.html
:100644 000000 0b269f3... 0000000... D docs/wiki/001geda_gschem_mp.html
:100644 000000 8e04059... 0000000... D docs/wiki/001geda_gschem_ug.html
:100644 000000 3a41a43... 0000000... D docs/wiki/001geda_hse_howto.html
:100644 000000 0cba62e... 0000000... D docs/wiki/001geda_installation.html
:100644 000000 e91358e... 0000000... D docs/wiki/001geda_kig_howto.html
:100644 000000 34666bf... 0000000... D docs/wiki/001geda_pcb-quick_reference.html
:100644 000000 91993bc... 0000000... D docs/wiki/001geda_pcb_tips.html
:100644 000000 15c4ca0... 0000000... D docs/wiki/001geda_scg.html
:100644 000000 14a8ba9... 0000000... D docs/wiki/001geda_suse_10.html
:100644 000000 2625cca... 0000000... D docs/wiki/001geda_tasks.html
:100644 000000 1116eff... 0000000... D docs/wiki/001geda_todos.html
:100644 000000 c879619... 0000000... D docs/wiki/001geda_tragesym_tutorial.html
:100644 000000 51eb5d7... 0000000... D docs/wiki/001geda_usage.html
:100644 100644 fa8d427... 5aff050... M docs/wiki/Makefile.am
:100644 000000 23c1897... 0000000... D docs/wiki/_detail/.gitignore
:100644 000000 5bc85ec... 0000000... D docs/wiki/_detail/001geda_ambiguous1.html
:100644 000000 d2170be... 0000000... D docs/wiki/_detail/001geda_ambiguous1_fixed.html
:100644 000000 8af064f... 0000000... D docs/wiki/_detail/001geda_design_flow.html
:100644 000000 b2bb84d... 0000000... D docs/wiki/_detail/001geda_faq_attrib.html
:100644 000000 d2ab7ab... 0000000... D docs/wiki/_detail/001geda_gschem_screenshot_001.html
:100644 000000 6389a6c... 0000000... D docs/wiki/_detail/001geda_gschem_workflow_01.html
:100644 000000 3e69ad5... 0000000... D docs/wiki/_detail/001geda_nets.html
:100644 000000 7b30d75... 0000000... D docs/wiki/_detail/001geda_status_screenshot.html
:100644 000000 de16766... 0000000... D docs/wiki/_detail/001geda_symbol_7400-1.html
:100644 000000 a583746... 0000000... D docs/wiki/_detail/001geda_symbol_7400-1_hidden.html
:100644 000000 9d8f535... 0000000... D docs/wiki/_detail/001geda_terminal_screenshot_001.html
:100644 000000 7462882... 0000000... D docs/wiki/_detail/001tragesym_acroread_selectiontable.html
:100644 000000 4bbabce... 0000000... D docs/wiki/_detail/001tragesym_gschem_finished.html
:100644 000000 68c8e90... 0000000... D docs/wiki/_detail/001tragesym_gschem_showhidden.html
:100644 000000 bbe89fa... 0000000... D docs/wiki/_detail/001tragesym_kpdf_pinconfiguration.html
:100644 000000 61d6a0d... 0000000... D docs/wiki/_detail/001tragesym_kpdf_pindescription.html
:100644 000000 b254934... 0000000... D docs/wiki/_detail/001tragesym_ooo_attributes.html
:100644 000000 0841d6d... 0000000... D docs/wiki/_detail/001tragesym_ooo_changedpins.html
:100644 000000 9edcc6b... 0000000... D docs/wiki/_detail/001tragesym_ooo_rearanged.html
:100644 000000 d3a7c93... 0000000... D docs/wiki/_detail/001tragesym_ooo_selection.html
:100644 000000 be387b3... 0000000... D docs/wiki/_detail/001tragesym_xemacs_modifiedselection.html
:100644 000000 1c63593... 0000000... D docs/wiki/_detail/001tragesym_xemacs_rawselection.html
:100644 000000 824de2f... 0000000... D docs/wiki/_detail/Makefile.am
:100644 000000 0532548... 0000000... D docs/wiki/_detail/devel_tips_dialog_picture.html
:100644 000000 eb903b0... 0000000... D docs/wiki/_detail/geda_ambiguous1.html
:100644 000000 2fc0b95... 0000000... D docs/wiki/_detail/geda_ambiguous1_fixed.html
:100644 000000 8c44fc6... 0000000... D docs/wiki/_detail/geda_board-1.html
:100644 000000 9f929d7... 0000000... D docs/wiki/_detail/geda_board-2.html
:100644 000000 2f86305... 0000000... D docs/wiki/_detail/geda_board-3.html
:100644 000000 3cacc25... 0000000... D docs/wiki/_detail/geda_board-4.html
:100644 000000 23e0f84... 0000000... D docs/wiki/_detail/geda_board-5.html
:100644 000000 9c7c992... 0000000... D docs/wiki/_detail/geda_board-6.html
:100644 000000 8ea4225... 0000000... D docs/wiki/_detail/geda_coordinatespace.html
:100644 000000 b30f8ab... 0000000... D docs/wiki/_detail/geda_design_flow.html
:100644 000000 8a5b6c5... 0000000... D docs/wiki/_detail/geda_dialogdirective.html
:100644 000000 fbbfc02... 0000000... D docs/wiki/_detail/geda_dialoginclude.html
:100644 000000 2f304d7... 0000000... D docs/wiki/_detail/geda_dialogmodel.html
:100644 000000 f5a1628... 0000000... D docs/wiki/_detail/geda_dialogtrans.html
:100644 000000 05a9504... 0000000... D docs/wiki/_detail/geda_dialogvac.html
:100644 000000 21cbf03... 0000000... D docs/wiki/_detail/geda_dialogvdc1.html
:100644 000000 41aec34... 0000000... D docs/wiki/_detail/geda_faq_attrib.html
:100644 000000 02be3b0... 0000000... D docs/wiki/_detail/geda_fileformat_textgraphic.html
:100644 000000 8120ec0... 0000000... D docs/wiki/_detail/geda_geda_flow.html
:100644 000000 7df612a... 0000000... D docs/wiki/_detail/geda_gschem-sym-1.html
:100644 000000 75e01e9... 0000000... D docs/wiki/_detail/geda_gschem-sym-2.html
:100644 000000 b7cfc7e... 0000000... D docs/wiki/_detail/geda_gschem-sym-3.html
:100644 000000 4f4c0a1... 0000000... D docs/wiki/_detail/geda_gschem_screenshot_001.html
:100644 000000 f8d3ea9... 0000000... D docs/wiki/_detail/geda_gschem_workflow_01.html
:100644 000000 2a532ca... 0000000... D docs/wiki/_detail/geda_net.html
:100644 000000 b14e1b4... 0000000... D docs/wiki/_detail/geda_nets.html
:100644 000000 f655da5... 0000000... D docs/wiki/_detail/geda_one-sch-1.html
:100644 000000 96e3811... 0000000... D docs/wiki/_detail/geda_one-sch-2.html
:100644 000000 6f45c9a... 0000000... D docs/wiki/_detail/geda_one-sch-3.html
:100644 000000 8222165... 0000000... D docs/wiki/_detail/geda_pcb-el-1.html
:100644 000000 1e37697... 0000000... D docs/wiki/_detail/geda_pcb-el-2.html
:100644 000000 dd60b0a... 0000000... D docs/wiki/_detail/geda_rf_cascade_figure1.html
:100644 000000 9f05616... 0000000... D docs/wiki/_detail/geda_rf_cascade_figure2.html
:100644 000000 2c97468... 0000000... D docs/wiki/_detail/geda_schematicfinished2.html
:100644 000000 520bb20... 0000000... D docs/wiki/_detail/geda_simple1.html
:100644 000000 6db4e31... 0000000... D docs/wiki/_detail/geda_status_screenshot.html
:100644 000000 a96f841... 0000000... D docs/wiki/_detail/geda_suse_electronics_menu.html
:100644 000000 a2dc995... 0000000... D docs/wiki/_detail/geda_switcap_figure1.html
:100644 000000 7cdc117... 0000000... D docs/wiki/_detail/geda_switcap_figure2.html
:100644 000000 04fea96... 0000000... D docs/wiki/_detail/geda_switcap_figure3.html
:100644 000000 c1374a9... 0000000... D docs/wiki/_detail/geda_switcap_figure4.html
:100644 000000 f66c673... 0000000... D docs/wiki/_detail/geda_symbol_7400-1.html
:100644 000000 4cf41f3... 0000000... D docs/wiki/_detail/geda_symbol_7400-1_hidden.html
:100644 000000 8ca2588... 0000000... D docs/wiki/_detail/geda_terminal_screenshot_001.html
:100644 000000 373e6e9... 0000000... D docs/wiki/_detail/geda_two-sch-1.html
:100644 000000 fcc5906... 0000000... D docs/wiki/_detail/geda_two-sch-2.html
:100644 000000 8a5fb35... 0000000... D docs/wiki/_detail/geda_warmup_add_component.html
:100644 000000 786c174... 0000000... D docs/wiki/_detail/geda_warmup_gschem01.html
:100644 000000 84ee288... 0000000... D docs/wiki/_detail/geda_warmup_gschem02.html
:100644 000000 df23d82... 0000000... D docs/wiki/_detail/geda_warmup_gschem03.html
:100644 000000 a304002... 0000000... D docs/wiki/_detail/tragesym_acroread_selectiontable.html
:100644 000000 97e7b03... 0000000... D docs/wiki/_detail/tragesym_gschem_finished.html
:100644 000000 cce51a3... 0000000... D docs/wiki/_detail/tragesym_gschem_showhidden.html
:100644 000000 9ae306d... 0000000... D docs/wiki/_detail/tragesym_kpdf_pinconfiguration.html
:100644 000000 2d8cee8... 0000000... D docs/wiki/_detail/tragesym_kpdf_pindescription.html
:100644 000000 d749ea1... 0000000... D docs/wiki/_detail/tragesym_ooo_attributes.html
:100644 000000 2d2f686... 0000000... D docs/wiki/_detail/tragesym_ooo_changedpins.html
:100644 000000 9708593... 0000000... D docs/wiki/_detail/tragesym_ooo_rearanged.html
:100644 000000 9b31f68... 0000000... D docs/wiki/_detail/tragesym_ooo_selection.html
:100644 000000 6a83c75... 0000000... D docs/wiki/_detail/tragesym_xemacs_modifiedselection.html
:100644 000000 f13967f... 0000000... D docs/wiki/_detail/tragesym_xemacs_rawselection.html
:100644 000000 23c1897... 0000000... D docs/wiki/_media/.gitignore
:100644 000000 425e9af... 0000000... D docs/wiki/_media/001tragesym_template
:100644 000000 02832de... 0000000... D docs/wiki/_media/Makefile.am
:100644 000000 3108609... 0000000... D docs/wiki/_media/devel_tips_dialog_picture.png
:100644 000000 29ffddb... 0000000... D docs/wiki/_media/geda_ambiguous1.png
:100644 000000 ae3dc52... 0000000... D docs/wiki/_media/geda_ambiguous1_fixed.png
:100644 000000 6189478... 0000000... D docs/wiki/_media/geda_board-1.png
:100644 000000 62c351c... 0000000... D docs/wiki/_media/geda_board-2.png
:100644 000000 f0406e3... 0000000... D docs/wiki/_media/geda_board-3.png
:100644 000000 ec6eba5... 0000000... D docs/wiki/_media/geda_board-4.png
:100644 000000 57ff80d... 0000000... D docs/wiki/_media/geda_board-5.png
:100644 000000 0e1189a... 0000000... D docs/wiki/_media/geda_board-6.png
:100644 000000 83b57fc... 0000000... D docs/wiki/_media/geda_coordinatespace.jpg
:100644 000000 0d6f152... 0000000... D docs/wiki/_media/geda_design_flow.jpg
:100644 000000 e1f21db... 0000000... D docs/wiki/_media/geda_dialogdirective.png
:100644 000000 5d300bd... 0000000... D docs/wiki/_media/geda_dialoginclude.png
:100644 000000 49e8e42... 0000000... D docs/wiki/_media/geda_dialogmodel.png
:100644 000000 4a7f9a1... 0000000... D docs/wiki/_media/geda_dialogtrans.png
:100644 000000 744893e... 0000000... D docs/wiki/_media/geda_dialogvac.png
:100644 000000 3e16535... 0000000... D docs/wiki/_media/geda_dialogvdc1.png
:100644 000000 cca6286... 0000000... D docs/wiki/_media/geda_faq_attrib.jpg
:100644 000000 1f49c1c... 0000000... D docs/wiki/_media/geda_fileformat_textgraphic.jpg
:100644 000000 79fbf9f... 0000000... D docs/wiki/_media/geda_geda_flow.png
:100644 000000 dfae00a... 0000000... D docs/wiki/_media/geda_gschem-sym-1.png
:100644 000000 dfc7d84... 0000000... D docs/wiki/_media/geda_gschem-sym-2.png
:100644 000000 b76217d... 0000000... D docs/wiki/_media/geda_gschem-sym-3.png
:100644 000000 2e0cf68... 0000000... D docs/wiki/_media/geda_gschem_screenshot_001.jpg
:100644 000000 d1326bc... 0000000... D docs/wiki/_media/geda_gschem_workflow_01.jpg
:100644 000000 3311666... 0000000... D docs/wiki/_media/geda_net.jpg
:100644 000000 264690e... 0000000... D docs/wiki/_media/geda_nets.jpg
:100644 000000 3824b47... 0000000... D docs/wiki/_media/geda_one-sch-1.png
:100644 000000 9028fc2... 0000000... D docs/wiki/_media/geda_one-sch-2.png
:100644 000000 82e65ea... 0000000... D docs/wiki/_media/geda_one-sch-3.png
:100644 000000 84d5bc3... 0000000... D docs/wiki/_media/geda_pcb-el-1.png
:100644 000000 41d7322... 0000000... D docs/wiki/_media/geda_pcb-el-2.png
:100644 000000 2521dfe... 0000000... D docs/wiki/_media/geda_rf_cascade_figure1.jpg
:100644 000000 b271a65... 0000000... D docs/wiki/_media/geda_rf_cascade_figure2.jpg
:100644 000000 6a381b7... 0000000... D docs/wiki/_media/geda_schematicfinished2.png
:100644 000000 a7fce1e... 0000000... D docs/wiki/_media/geda_simple1.png
:100644 000000 394ef3a... 0000000... D docs/wiki/_media/geda_status_screenshot.jpg
:100644 000000 16881ed... 0000000... D docs/wiki/_media/geda_suse_electronics_menu.png
:100644 000000 5313e53... 0000000... D docs/wiki/_media/geda_switcap_figure1.jpg
:100644 000000 b9e0f6a... 0000000... D docs/wiki/_media/geda_switcap_figure2.jpg
:100644 000000 6617c00... 0000000... D docs/wiki/_media/geda_switcap_figure3.jpg
:100644 000000 639985b... 0000000... D docs/wiki/_media/geda_switcap_figure4.jpg
:100644 000000 e817f55... 0000000... D docs/wiki/_media/geda_symbol_7400-1.png
:100644 000000 22807da... 0000000... D docs/wiki/_media/geda_symbol_7400-1_hidden.png
:100644 000000 1b28256... 0000000... D docs/wiki/_media/geda_terminal_screenshot_001.jpg
:100644 000000 74b59c9... 0000000... D docs/wiki/_media/geda_two-sch-1.png
:100644 000000 9448d26... 0000000... D docs/wiki/_media/geda_two-sch-2.png
:100644 000000 cfd5794... 0000000... D docs/wiki/_media/geda_warmup_add_component.png
:100644 000000 1191d90... 0000000... D docs/wiki/_media/geda_warmup_gschem01.png
:100644 000000 af49239... 0000000... D docs/wiki/_media/geda_warmup_gschem02.png
:100644 000000 e9da8d3... 0000000... D docs/wiki/_media/geda_warmup_gschem03.png
:100644 000000 796cd9b... 0000000... D docs/wiki/_media/tragesym_acroread_selectiontable.png
:100644 000000 ccd4d82... 0000000... D docs/wiki/_media/tragesym_gschem_finished.png
:100644 000000 8a2a067... 0000000... D docs/wiki/_media/tragesym_gschem_showhidden.png
:100644 000000 72fc148... 0000000... D docs/wiki/_media/tragesym_kpdf_pinconfiguration.png
:100644 000000 6c5b49e... 0000000... D docs/wiki/_media/tragesym_kpdf_pindescription.png
:100644 000000 3e6fdc8... 0000000... D docs/wiki/_media/tragesym_ooo_attributes.png
:100644 000000 5446849... 0000000... D docs/wiki/_media/tragesym_ooo_changedpins.png
:100644 000000 100395b... 0000000... D docs/wiki/_media/tragesym_ooo_rearanged.png
:100644 000000 41a6a11... 0000000... D docs/wiki/_media/tragesym_ooo_selection.png
:100644 000000 ac3839e... 0000000... D docs/wiki/_media/tragesym_template
:100644 000000 f414b79... 0000000... D docs/wiki/_media/tragesym_template2
:100644 000000 4e507c3... 0000000... D docs/wiki/_media/tragesym_template2.txt.txt
:100644 000000 dd2ce2d... 0000000... D docs/wiki/_media/tragesym_xemacs_modifiedselection.png
:100644 000000 8a86702... 0000000... D docs/wiki/_media/tragesym_xemacs_rawselection.png
:100644 100644 46c5857... 06511f8... M docs/wiki/best_practices.html
:000000 100644 0000000... 86ef2d7... A docs/wiki/design.css
:100644 000000 57d66ef... 0000000... D docs/wiki/docs_20060124_gschem_ug_app_a.html
:100644 000000 681759c... 0000000... D docs/wiki/docs_20060124_gschem_ug_app_b.html
:100644 000000 5292b1a... 0000000... D docs/wiki/docs_20060124_gschem_ug_app_c.html
:100644 000000 8f6b082... 0000000... D docs/wiki/docs_20060124_gschem_ug_components_symbols_objects_attributes.html
:100644 000000 81b7888... 0000000... D docs/wiki/docs_20060124_gschem_ug_electrical_connectivity.html
:100644 000000 356355e... 0000000... D docs/wiki/docs_20060124_gschem_ug_how_to_ask_questions.html
:100644 000000 6129a4c... 0000000... D docs/wiki/docs_20060124_gschem_ug_installing_gschem.html
:100644 000000 83af5d2... 0000000... D docs/wiki/docs_20060124_gschem_ug_resources.html
:100644 000000 4d3825f... 0000000... D docs/wiki/docs_20060124_gschem_ug_the_main_window.html
:100644 000000 dd1d6da... 0000000... D docs/wiki/docs_20060124_gschem_ug_the_status_window.html
:000000 100644 0000000... 3d1659f... A docs/wiki/geda-bom_readme.html
:000000 100644 0000000... f14db5f... A docs/wiki/geda-circuit_simulation_improvements.html
:000000 100644 0000000... c456378... A docs/wiki/geda-covered_mp.html
:000000 100644 0000000... 8433488... A docs/wiki/geda-csygas.html
:000000 100644 0000000... 60d2f33... A docs/wiki/geda-cygwin.html
:000000 100644 0000000... 329b69c... A docs/wiki/geda-data_plotting_improvements.html
:000000 100644 0000000... d639d15... A docs/wiki/geda-data_structure_design_discussion.html
:000000 100644 0000000... 0679bda... A docs/wiki/geda-debian.fr.html
:000000 100644 0000000... 110b34c... A docs/wiki/geda-debian.html
:000000 100644 0000000... 261d0da... A docs/wiki/geda-design_flow_and_hierarchy_roadmap.html
:000000 100644 0000000... 45f3a9a... A docs/wiki/geda-design_flow_roadmap.html
:000000 100644 0000000... 519e21d... A docs/wiki/geda-devel-tips.html
:000000 100644 0000000... e0dc148... A docs/wiki/geda-devmacosx.html
:000000 100644 0000000... cc0b8e6... A docs/wiki/geda-documentation.fr.html
:000000 100644 0000000... 146071f... A docs/wiki/geda-documentation.html
:000000 100644 0000000... 95a3fdc... A docs/wiki/geda-eagle_pcb_netlister_readme.html
:000000 100644 0000000... 9068295... A docs/wiki/geda-example_hsm.html
:000000 100644 0000000... e1ff867... A docs/wiki/geda-example_usbjtag.html
:000000 100644 0000000... 45d8583... A docs/wiki/geda-experiences.html
:000000 100644 0000000... 4df4505... A docs/wiki/geda-faq-attribs.fr.html
:000000 100644 0000000... 2fcd29a... A docs/wiki/geda-faq-attribs.html
:000000 100644 0000000... 260a236... A docs/wiki/geda-faq-gnetlist.fr.html
:000000 100644 0000000... 078f1f7... A docs/wiki/geda-faq-gnetlist.html
:000000 100644 0000000... f78f399... A docs/wiki/geda-faq-gsch2pcb.fr.html
:000000 100644 0000000... 8531b3b... A docs/wiki/geda-faq-gsch2pcb.html
:000000 100644 0000000... 52b341f... A docs/wiki/geda-faq-gschem.fr.html
:000000 100644 0000000... 996d53b... A docs/wiki/geda-faq-gschem.html
:000000 100644 0000000... 5ea33d3... A docs/wiki/geda-faq-pcb.html
:000000 100644 0000000... 843eb8f... A docs/wiki/geda-faq-simulation.fr.html
:000000 100644 0000000... ad780dd... A docs/wiki/geda-faq-simulation.html
:000000 100644 0000000... 8fbfef9... A docs/wiki/geda-faq.fr.html
:000000 100644 0000000... 10d1663... A docs/wiki/geda-faq.html
:000000 100644 0000000... f6a5e7e... A docs/wiki/geda-fbabgapp.html
:000000 100644 0000000... 6890814... A docs/wiki/geda-fc1.html
:000000 100644 0000000... f3893d4... A docs/wiki/geda-fc2.html
:000000 100644 0000000... 0ca4a9e... A docs/wiki/geda-fc3.html
:000000 100644 0000000... a57f8c6... A docs/wiki/geda-fc4.html
:000000 100644 0000000... 406a5b8... A docs/wiki/geda-fedora_rpm_installation.html
:000000 100644 0000000... 779c5cd... A docs/wiki/geda-file_format_spec.html
:000000 100644 0000000... 6c8d8ee... A docs/wiki/geda-format_translation.html
:000000 100644 0000000... f4a7b19... A docs/wiki/geda-gattrib_readme.html
:000000 100644 0000000... c1ad0f4... A docs/wiki/geda-gedasuite_installation.html
:000000 100644 0000000... 4a094e7... A docs/wiki/geda-gerbv_mp.html
:000000 100644 0000000... ee4d44e... A docs/wiki/geda-gerbv_pnp_readme.html
:000000 100644 0000000... 92b2690... A docs/wiki/geda-gfdl.html
:000000 100644 0000000... 28974b3... A docs/wiki/geda-glossaire.fr.html
:000000 100644 0000000... 28974b3... A docs/wiki/geda-glossary.fr.html
:000000 100644 0000000... 04218e3... A docs/wiki/geda-glossary.html
:000000 100644 0000000... 2bcadf5... A docs/wiki/geda-gnetlist_mp.html
:000000 100644 0000000... febcf24... A docs/wiki/geda-gnetlist_ug.html
:000000 100644 0000000... 5be5687... A docs/wiki/geda-grcsan.html
:000000 100644 0000000... 2f63000... A docs/wiki/geda-grenum_mp.html
:000000 100644 0000000... 6d22cf8... A docs/wiki/geda-gsch2pcb_readme.html
:000000 100644 0000000... 5283402... A docs/wiki/geda-gsch2pcb_tutorial.html
:000000 100644 0000000... fc4aa9c... A docs/wiki/geda-gsch2pcb_tutorial_releasenotes.html
:000000 100644 0000000... 8d4f38d... A docs/wiki/geda-gschem2pcb_readme.html
:000000 100644 0000000... 5710d10... A docs/wiki/geda-gschem_mp.html
:000000 100644 0000000... 673f062... A docs/wiki/geda-gschem_ug.fr.html
:000000 100644 0000000... 37fdbeb... A docs/wiki/geda-gschem_ug.html
:000000 100644 0000000... b572695... A docs/wiki/geda-gschem_warmup.html
:000000 100644 0000000... 4324138... A docs/wiki/geda-gsymcheck_mp.html
:000000 100644 0000000... 2015f50... A docs/wiki/geda-gtkwave_lxt2miner_mp.html
:000000 100644 0000000... 0ea03ad... A docs/wiki/geda-gtkwave_lxt2vcd_mp.html
:000000 100644 0000000... 74c42c8... A docs/wiki/geda-gtkwave_mp.html
:000000 100644 0000000... 395911b... A docs/wiki/geda-gtkwave_mvl2lxt_mp.html
:000000 100644 0000000... 9725a35... A docs/wiki/geda-gtkwave_mvl2vcd_mp.html
:000000 100644 0000000... 71825cd... A docs/wiki/geda-gtkwave_tex2vcd_mp.html
:000000 100644 0000000... 806b81c... A docs/wiki/geda-gtkwave_tla2vcd_mp.html
:000000 100644 0000000... 5b11ecf... A docs/wiki/geda-gtkwave_vcd2lxt2_mp.html
:000000 100644 0000000... 2da6354... A docs/wiki/geda-gtkwave_vcd2lxt_mp.html
:000000 100644 0000000... 30df085... A docs/wiki/geda-gtkwave_vcd2vzt_mp.html
:000000 100644 0000000... b5b3636... A docs/wiki/geda-gtkwave_vzt2vcd_mp.html
:000000 100644 0000000... 76771eb... A docs/wiki/geda-gtkwave_vztminer_mp.html
:000000 100644 0000000... 4d97dfd... A docs/wiki/geda-guile_scripting.html
:000000 100644 0000000... d5f8744... A docs/wiki/geda-hse_howto.html
:000000 100644 0000000... 41bb037... A docs/wiki/geda-icarus_anc.html
:000000 100644 0000000... 0004418... A docs/wiki/geda-icarus_extensions.html
:000000 100644 0000000... 53a519e... A docs/wiki/geda-icarus_glossary.html
:000000 100644 0000000... 89361ff... A docs/wiki/geda-icarus_ieee1364.html
:000000 100644 0000000... f98d924... A docs/wiki/geda-icarus_mp.html
:000000 100644 0000000... 961e601... A docs/wiki/geda-icarus_opcodes.html
:000000 100644 0000000... 068bbf3... A docs/wiki/geda-icarus_quick_start.html
:000000 100644 0000000... 2ea4a48... A docs/wiki/geda-icarus_readme.html
:000000 100644 0000000... f3a8a41... A docs/wiki/geda-icarus_vpi_mp.html
:000000 100644 0000000... 104378d... A docs/wiki/geda-icarus_vpi_within_vvp.html
:000000 100644 0000000... 08277ee... A docs/wiki/geda-icarus_vvp_runtime.html
:000000 100644 0000000... 5a0b660... A docs/wiki/geda-icarus_vvp_simulation.html
:000000 100644 0000000... dc8b682... A docs/wiki/geda-icarus_xilinx_hints.html
:000000 100644 0000000... fefadfb... A docs/wiki/geda-icarus_xnf.html
:000000 100644 0000000... 806a427... A docs/wiki/geda-igarus_fpga_lcg.html
:000000 100644 0000000... 9aa6a9e... A docs/wiki/geda-installation.fr.html
:000000 100644 0000000... a035f2d... A docs/wiki/geda-installation.html
:000000 100644 0000000... 39ae539... A docs/wiki/geda-installed_plugins.html
:000000 100644 0000000... b857166... A docs/wiki/geda-kig_howto.html
:000000 100644 0000000... 7287213... A docs/wiki/geda-master_attributes_list.html
:000000 100644 0000000... ba58606... A docs/wiki/geda-mcalc_readme.html
:000000 100644 0000000... 3328309... A docs/wiki/geda-na_howto.html
:000000 100644 0000000... 93cec8c... A docs/wiki/geda-ngnutmeg_mp.html
:000000 100644 0000000... bf4030a... A docs/wiki/geda-ngsconvert_mp.html
:000000 100644 0000000... 7cad960... A docs/wiki/geda-ngspice_and_gschem.html
:000000 100644 0000000... e2a68a9... A docs/wiki/geda-ngspice_mp.html
:000000 100644 0000000... 72f3264... A docs/wiki/geda-olib_readme.html
:000000 100644 0000000... 0bd7a4c... A docs/wiki/geda-pcb-quick_reference.fr.html
:000000 100644 0000000... 45ce5fd... A docs/wiki/geda-pcb-quick_reference.html
:000000 100644 0000000... d2339a6... A docs/wiki/geda-pcb_footprints.html
:000000 100644 0000000... e15c265... A docs/wiki/geda-pcb_funding_sow-fwdann_ideas.html
:000000 100644 0000000... 7fc3e5e... A docs/wiki/geda-pcb_funding_sow-gui_ideas.html
:000000 100644 0000000... 8e933ee... A docs/wiki/geda-pcb_funding_sow.html
:000000 100644 0000000... ed86825... A docs/wiki/geda-pcb_mp.html
:000000 100644 0000000... a1ba425... A docs/wiki/geda-pcb_tips.fr.html
:000000 100644 0000000... 6d473df... A docs/wiki/geda-pcb_tips.html
:000000 100644 0000000... 011a9a4... A docs/wiki/geda-release_engineering.html
:000000 100644 0000000... dae7f3d... A docs/wiki/geda-scg.fr.html
:000000 100644 0000000... 83d058e... A docs/wiki/geda-scg.html
:000000 100644 0000000... 840db3e... A docs/wiki/geda-scm.html
:000000 100644 0000000... 0cf4f90... A docs/wiki/geda-sdb_howto.html
:000000 100644 0000000... 039f97c... A docs/wiki/geda-sn_readme.html
:000000 100644 0000000... 8451e13... A docs/wiki/geda-spice_improvements.html
:000000 100644 0000000... a7e6246... A docs/wiki/geda-ssan.html
:000000 100644 0000000... 483bd45... A docs/wiki/geda-start.html
:000000 100644 0000000... 37b05b7... A docs/wiki/geda-style_guide.html
:000000 100644 0000000... 8559155... A docs/wiki/geda-suse_10.0.html
:000000 100644 0000000... 7605d8a... A docs/wiki/geda-suse_10.1.html
:000000 100644 0000000... c0c8ce8... A docs/wiki/geda-suse_9.3.html
:000000 100644 0000000... 09f0df5... A docs/wiki/geda-suse_rpm_installation.html
:000000 100644 0000000... 8cdb288... A docs/wiki/geda-syntax_features.html
:000000 100644 0000000... a1ed4d4... A docs/wiki/geda-systemc_netlister_readme.html
:000000 100644 0000000... 1bbaec6... A docs/wiki/geda-tasks.html
:000000 100644 0000000... a21fb9e... A docs/wiki/geda-todos.html
:000000 100644 0000000... d759dab... A docs/wiki/geda-todos_historical.html
:000000 100644 0000000... 1d8087c... A docs/wiki/geda-tragesym_readme.html
:000000 100644 0000000... d5dfb24... A docs/wiki/geda-tragesym_tutorial.fr.html
:000000 100644 0000000... c8563b8... A docs/wiki/geda-tragesym_tutorial.html
:000000 100644 0000000... 03e2480... A docs/wiki/geda-transistor_guide.html
:000000 100644 0000000... f2fc7dd... A docs/wiki/geda-ubuntu.html
:000000 100644 0000000... 0a2eead... A docs/wiki/geda-usage.fr.html
:000000 100644 0000000... 1ff47dc... A docs/wiki/geda-usage.html
:000000 100644 0000000... 8505d6c... A docs/wiki/geda-vams_netlister_readme.html
:000000 100644 0000000... b55b04b... A docs/wiki/geda-verilog_netlister_readme.html
:000000 100644 0000000... 2d96277... A docs/wiki/geda-version_control_migration.html
:000000 100644 0000000... 90f1291... A docs/wiki/geda-vhdl_netlister_readme.html
:000000 100644 0000000... 5e24064... A docs/wiki/geda-wcalc_mp.html
:000000 100644 0000000... 548b9f9... A docs/wiki/geda-wcalc_readme.html
:000000 100644 0000000... 43fb47e... A docs/wiki/geda-wcalc_stdio_mp.html
:000000 100644 0000000... 9881d11... A docs/wiki/geda-wip-clipboard.html
:000000 100644 0000000... 3669f04... A docs/wiki/geda-xml_file_formats.html
:100644 000000 d7f8f44... 0000000... D docs/wiki/geda_bill_wilson_s.html
:100644 000000 5e42f23... 0000000... D docs/wiki/geda_bom_readme.html
:100644 000000 7fc3ebf... 0000000... D docs/wiki/geda_circuit_simulation_improvements.html
:100644 000000 524c009... 0000000... D docs/wiki/geda_covered_mp.html
:100644 000000 8968631... 0000000... D docs/wiki/geda_covered_rv.html
:100644 000000 644cf49... 0000000... D docs/wiki/geda_csygas.html
:100644 000000 861c898... 0000000... D docs/wiki/geda_cygwin.html
:100644 000000 b2dfa12... 0000000... D docs/wiki/geda_data_plotting_improvements.html
:100644 000000 00c8abd... 0000000... D docs/wiki/geda_data_structure_design_discussion.html
:100644 000000 2355f06... 0000000... D docs/wiki/geda_debian.html
:100644 000000 f3d53dc... 0000000... D docs/wiki/geda_design_flow_and_hierarchy_roadmap.html
:100644 000000 04b9a0b... 0000000... D docs/wiki/geda_devel-tips.html
:100644 000000 b57af4c... 0000000... D docs/wiki/geda_documentation.html
:100644 000000 fdf9c19... 0000000... D docs/wiki/geda_eagle_pcb_netlister_readme.html
:100644 000000 1fb1dec... 0000000... D docs/wiki/geda_example_hsm.html
:100644 000000 f0a413a... 0000000... D docs/wiki/geda_example_usbjtag.html
:100644 000000 7cf0591... 0000000... D docs/wiki/geda_faq-attribs.html
:100644 000000 21c6240... 0000000... D docs/wiki/geda_faq-gnetlist.html
:100644 000000 6e6b12a... 0000000... D docs/wiki/geda_faq-gsch2pcb.html
:100644 000000 23fe257... 0000000... D docs/wiki/geda_faq-gschem.html
:100644 000000 23a0f43... 0000000... D docs/wiki/geda_faq-pcb.html
:100644 000000 fe4ac48... 0000000... D docs/wiki/geda_faq-simulation.html
:100644 000000 0c4d12c... 0000000... D docs/wiki/geda_faq.html
:100644 000000 a683380... 0000000... D docs/wiki/geda_fbabgapp.html
:100644 000000 c33a924... 0000000... D docs/wiki/geda_fc1.html
:100644 000000 e93dff0... 0000000... D docs/wiki/geda_fc2.html
:100644 000000 436db2d... 0000000... D docs/wiki/geda_fc3.html
:100644 000000 08e58a4... 0000000... D docs/wiki/geda_fc4.html
:100644 000000 e3785e0... 0000000... D docs/wiki/geda_fedora_rpm_installation.html
:100644 000000 61282a3... 0000000... D docs/wiki/geda_file_format_spec.html
:100644 000000 8917a94... 0000000... D docs/wiki/geda_footprint_creation.html
:100644 000000 e81d772... 0000000... D docs/wiki/geda_gattrib_readme.html
:100644 000000 9665e17... 0000000... D docs/wiki/geda_gedasuite_installation.html
:100644 000000 7de8951... 0000000... D docs/wiki/geda_gerbv_mp.html
:100644 000000 8a72f5e... 0000000... D docs/wiki/geda_gerbv_pnp_readme.html
:100644 000000 4deaaa5... 0000000... D docs/wiki/geda_gfdl.html
:100644 000000 35de765... 0000000... D docs/wiki/geda_glossaire.html
:100644 000000 1703a40... 0000000... D docs/wiki/geda_glossary.html
:100644 000000 1214a1a... 0000000... D docs/wiki/geda_gnetlist_mp.html
:100644 000000 8fad7c5... 0000000... D docs/wiki/geda_gnetlist_ug.html
:100644 000000 dabb120... 0000000... D docs/wiki/geda_grcsan.html
:100644 000000 b3330d7... 0000000... D docs/wiki/geda_grenum_mp.html
:100644 000000 0044578... 0000000... D docs/wiki/geda_gsch2pcb_readme.html
:100644 000000 465937b... 0000000... D docs/wiki/geda_gsch2pcb_tutorial.html
:100644 000000 cee89aa... 0000000... D docs/wiki/geda_gsch2pcb_tutorial_releasenotes.html
:100644 000000 5c7d4e2... 0000000... D docs/wiki/geda_gschem2pcb_readme.html
:100644 000000 8677d80... 0000000... D docs/wiki/geda_gschem_mp.html
:100644 000000 27745bb... 0000000... D docs/wiki/geda_gschem_ug.html
:100644 000000 3632169... 0000000... D docs/wiki/geda_gschem_warmup.html
:100644 000000 f25fb18... 0000000... D docs/wiki/geda_gsymcheck_mp.html
:100644 000000 e24dd7a... 0000000... D docs/wiki/geda_gtkwave_lxt2miner_mp.html
:100644 000000 acbe10e... 0000000... D docs/wiki/geda_gtkwave_lxt2vcd_mp.html
:100644 000000 01f8f6b... 0000000... D docs/wiki/geda_gtkwave_mp.html
:100644 000000 96d2a32... 0000000... D docs/wiki/geda_gtkwave_mvl2lxt_mp.html
:100644 000000 195f8bf... 0000000... D docs/wiki/geda_gtkwave_mvl2vcd_mp.html
:100644 000000 6ab0dcd... 0000000... D docs/wiki/geda_gtkwave_tex2vcd_mp.html
:100644 000000 c6aa055... 0000000... D docs/wiki/geda_gtkwave_tla2vcd_mp.html
:100644 000000 6feddeb... 0000000... D docs/wiki/geda_gtkwave_vcd2lxt2_mp.html
:100644 000000 49ea706... 0000000... D docs/wiki/geda_gtkwave_vcd2lxt_mp.html
:100644 000000 612fdaa... 0000000... D docs/wiki/geda_gtkwave_vcd2vzt_mp.html
:100644 000000 55d1b1f... 0000000... D docs/wiki/geda_gtkwave_vzt2vcd_mp.html
:100644 000000 1388a7a... 0000000... D docs/wiki/geda_gtkwave_vztminer_mp.html
:100644 000000 df3e372... 0000000... D docs/wiki/geda_guile_scripting.html
:100644 000000 4138f61... 0000000... D docs/wiki/geda_hse_howto.html
:100644 000000 53db137... 0000000... D docs/wiki/geda_icarus_anc.html
:100644 000000 5add6c6... 0000000... D docs/wiki/geda_icarus_extensions.html
:100644 000000 933afe5... 0000000... D docs/wiki/geda_icarus_glossary.html
:100644 000000 00ddca7... 0000000... D docs/wiki/geda_icarus_ieee1364.html
:100644 000000 f931da4... 0000000... D docs/wiki/geda_icarus_mp.html
:100644 000000 265dabe... 0000000... D docs/wiki/geda_icarus_opcodes.html
:100644 000000 6ee2a88... 0000000... D docs/wiki/geda_icarus_quick_start.html
:100644 000000 5b33825... 0000000... D docs/wiki/geda_icarus_readme.html
:100644 000000 4d09414... 0000000... D docs/wiki/geda_icarus_vpi_mp.html
:100644 000000 7643666... 0000000... D docs/wiki/geda_icarus_vpi_within_vvp.html
:100644 000000 0eee6c8... 0000000... D docs/wiki/geda_icarus_vvp_runtime.html
:100644 000000 11617e8... 0000000... D docs/wiki/geda_icarus_vvp_simulation.html
:100644 000000 d7d0ce5... 0000000... D docs/wiki/geda_icarus_xilinx_hints.html
:100644 000000 6b2ca09... 0000000... D docs/wiki/geda_icarus_xnf.html
:100644 000000 20af6ee... 0000000... D docs/wiki/geda_igarus_fpga_lcg.html
:100644 000000 60533e5... 0000000... D docs/wiki/geda_installation.html
:100644 000000 ae82ef7... 0000000... D docs/wiki/geda_installed_plugins.html
:100644 000000 0d998b2... 0000000... D docs/wiki/geda_kig_howto.html
:100644 000000 02fe8c4... 0000000... D docs/wiki/geda_master_attributes_list.html
:100644 000000 084128f... 0000000... D docs/wiki/geda_mcalc_readme.html
:100644 000000 a59dad5... 0000000... D docs/wiki/geda_na_howto.html
:100644 000000 293f2ba... 0000000... D docs/wiki/geda_ngnutmeg_mp.html
:100644 000000 905a30e... 0000000... D docs/wiki/geda_ngsconvert_mp.html
:100644 000000 70c410b... 0000000... D docs/wiki/geda_ngspice_and_gschem.html
:100644 000000 ab47781... 0000000... D docs/wiki/geda_ngspice_mp.html
:100644 000000 84d72fa... 0000000... D docs/wiki/geda_olib_readme.html
:100644 000000 9759359... 0000000... D docs/wiki/geda_pcb-quick_reference.html
:100644 000000 0131284... 0000000... D docs/wiki/geda_pcb.html
:100644 000000 fde55c8... 0000000... D docs/wiki/geda_pcb_footprints.html
:100644 000000 308d2dd... 0000000... D docs/wiki/geda_pcb_mp.html
:100644 000000 2fe5838... 0000000... D docs/wiki/geda_pcb_tips.html
:100644 000000 4f61c05... 0000000... D docs/wiki/geda_pcb_ug.html
:100644 000000 d4c54b4... 0000000... D docs/wiki/geda_release_engineering.html
:100644 000000 2f471b3... 0000000... D docs/wiki/geda_scg.html
:100644 000000 61792f7... 0000000... D docs/wiki/geda_scm.html
:100644 000000 5f3a06a... 0000000... D docs/wiki/geda_sdb_howto.html
:100644 000000 70f3fef... 0000000... D docs/wiki/geda_sn_readme.html
:100644 000000 9ebdf53... 0000000... D docs/wiki/geda_ssan.html
:100644 000000 3b742a6... 0000000... D docs/wiki/geda_style_guide.html
:100644 000000 ab05eb6... 0000000... D docs/wiki/geda_suse_10.html
:100644 000000 b924f98... 0000000... D docs/wiki/geda_suse_9.html
:100644 000000 132d401... 0000000... D docs/wiki/geda_suse_rpm_installation.html
:100644 000000 e4d5cd8... 0000000... D docs/wiki/geda_syntax_features.html
:100644 000000 98df741... 0000000... D docs/wiki/geda_systemc_netlister_readme.html
:100644 000000 c541e79... 0000000... D docs/wiki/geda_tasks.html
:100644 000000 6b90f45... 0000000... D docs/wiki/geda_todos.html
:100644 000000 0388a1a... 0000000... D docs/wiki/geda_tragesym_readme.html
:100644 000000 e20df8d... 0000000... D docs/wiki/geda_tragesym_tutorial.html
:100644 000000 e2dccd7... 0000000... D docs/wiki/geda_transistor_guide.html
:100644 000000 0663520... 0000000... D docs/wiki/geda_ubuntu.html
:100644 000000 d0f6c7c... 0000000... D docs/wiki/geda_usage.html
:100644 000000 5da308c... 0000000... D docs/wiki/geda_vams_netlister_readme.html
:100644 000000 206114b... 0000000... D docs/wiki/geda_verilog_netlister_readme.html
:100644 000000 eb53fb0... 0000000... D docs/wiki/geda_vhdl_netlister_readme.html
:100644 000000 71232ee... 0000000... D docs/wiki/geda_wcalc_mp.html
:100644 000000 3e195a9... 0000000... D docs/wiki/geda_wcalc_readme.html
:100644 000000 5b94155... 0000000... D docs/wiki/geda_wcalc_stdio_mp.html
:100644 100644 d7183d3... 71c9684... M docs/wiki/gerbv-projects.html
:100644 100644 f02b688... ed144ed... M docs/wiki/glue-projects.html
:100644 100644 84f1e0e... 1e26b36... M docs/wiki/gschem-projects.html
:100644 100644 21474d5... 8ece0bd... M docs/wiki/gsoc2007.html
:100644 100644 61e0f65... c2b847c... M docs/wiki/gsoc2007_projects.html
:100644 100644 94e92d9... 04e07a2... M docs/wiki/gsoc2008.html
:100644 100644 692d895... 22c3f3a... M docs/wiki/gsoc2008_projects.html
:000000 100644 0000000... f9bf230... A docs/wiki/gsoc2009.html
:000000 100644 0000000... e3157dd... A docs/wiki/gsoc2009_projects.html
:000000 100644 0000000... 74ba1d3... A docs/wiki/gtkwave-projects.html
:100644 100644 09217db... 78d0530... M docs/wiki/gwave-projects.html
:000000 100644 0000000... 23c1897... A docs/wiki/images/.gitignore
:000000 100644 0000000... b8db727... A docs/wiki/images/Makefile.am
:000000 100644 0000000... b43de48... A docs/wiki/images/bullet.gif
:000000 100644 0000000... 5861d63... A docs/wiki/images/button-cc.gif
:000000 100644 0000000... 706325e... A docs/wiki/images/button-css.png
:000000 100644 0000000... ec682c6... A docs/wiki/images/button-donate.gif
:000000 100644 0000000... 39d5f56... A docs/wiki/images/button-dw.png
:000000 100644 0000000... 28f329a... A docs/wiki/images/button-php.gif
:000000 100644 0000000... b036f71... A docs/wiki/images/button-rss.png
:000000 100644 0000000... ec68644... A docs/wiki/images/button-xhtml.png
:000000 100644 0000000... 8414d4d... A docs/wiki/images/closed.gif
:000000 100644 0000000... 73d6f8d... A docs/wiki/images/interwiki.png
:000000 100644 0000000... 23c1897... A docs/wiki/images/interwiki/.gitignore
:000000 100644 0000000... a294f2c... A docs/wiki/images/interwiki/Makefile.am
:000000 100644 0000000... f52c1c5... A docs/wiki/images/interwiki/amazon.de.gif
:000000 100644 0000000... f52c1c5... A docs/wiki/images/interwiki/amazon.gif
:000000 100644 0000000... f52c1c5... A docs/wiki/images/interwiki/amazon.uk.gif
:000000 100644 0000000... 3432b8d... A docs/wiki/images/interwiki/bug.gif
:000000 100644 0000000... 0f9f675... A docs/wiki/images/interwiki/coral.gif
:000000 100644 0000000... 7dc4248... A docs/wiki/images/interwiki/doku.gif
:000000 100644 0000000... fb39f61... A docs/wiki/images/interwiki/google.gif
:000000 100644 0000000... 7ac5454... A docs/wiki/images/interwiki/meatball.gif
:000000 100644 0000000... 638d4c4... A docs/wiki/images/interwiki/phpfn.gif
:000000 100644 0000000... e272a29... A docs/wiki/images/interwiki/sb.gif
:000000 100644 0000000... e8dc5d2... A docs/wiki/images/interwiki/wiki.gif
:000000 100644 0000000... ca853b8... A docs/wiki/images/interwiki/wp.gif
:000000 100644 0000000... ca853b8... A docs/wiki/images/interwiki/wpde.gif
:000000 100644 0000000... ca853b8... A docs/wiki/images/interwiki/wpmeta.gif
:000000 100644 0000000... 815ccb1... A docs/wiki/images/link_icon.gif
:000000 100644 0000000... 50a87a9... A docs/wiki/images/mail_icon.gif
:000000 100644 0000000... f5d5c7e... A docs/wiki/images/open.gif
:000000 100644 0000000... 23c1897... A docs/wiki/images/smileys/.gitignore
:000000 100644 0000000... 2e01243... A docs/wiki/images/smileys/Makefile.am
:000000 100644 0000000... d668348... A docs/wiki/images/smileys/delete.gif
:000000 100644 0000000... b66ea99... A docs/wiki/images/smileys/fixme.gif
:000000 100644 0000000... 2880055... A docs/wiki/images/smileys/icon_arrow.gif
:000000 100644 0000000... d352772... A docs/wiki/images/smileys/icon_biggrin.gif
:000000 100644 0000000... 0c49e06... A docs/wiki/images/smileys/icon_confused.gif
:000000 100644 0000000... cead030... A docs/wiki/images/smileys/icon_cool.gif
:000000 100644 0000000... 7d54b1f... A docs/wiki/images/smileys/icon_cry.gif
:000000 100644 0000000... fd7903b... A docs/wiki/images/smileys/icon_doubt.gif
:000000 100644 0000000... eb4b70b... A docs/wiki/images/smileys/icon_doubt2.gif
:000000 100644 0000000... 5d39781... A docs/wiki/images/smileys/icon_eek.gif
:000000 100644 0000000... ab1aa8e... A docs/wiki/images/smileys/icon_evil.gif
:000000 100644 0000000... 6e50e2e... A docs/wiki/images/smileys/icon_exclaim.gif
:000000 100644 0000000... d2ac78c... A docs/wiki/images/smileys/icon_frown.gif
:000000 100644 0000000... a8bb8a3... A docs/wiki/images/smileys/icon_fun.gif
:000000 100644 0000000... a40ae0d... A docs/wiki/images/smileys/icon_idea.gif
:000000 100644 0000000... 1410f7f... A docs/wiki/images/smileys/icon_kaddi.gif
:000000 100644 0000000... 374ba15... A docs/wiki/images/smileys/icon_lol.gif
:000000 100644 0000000... b54cd0f... A docs/wiki/images/smileys/icon_mrgreen.gif
:000000 100644 0000000... 4f31156... A docs/wiki/images/smileys/icon_neutral.gif
:000000 100644 0000000... 9d07226... A docs/wiki/images/smileys/icon_question.gif
:000000 100644 0000000... 29da2a2... A docs/wiki/images/smileys/icon_razz.gif
:000000 100644 0000000... ad76283... A docs/wiki/images/smileys/icon_redface.gif
:000000 100644 0000000... d7f5f2f... A docs/wiki/images/smileys/icon_rolleyes.gif
:000000 100644 0000000... d2ac78c... A docs/wiki/images/smileys/icon_sad.gif
:000000 100644 0000000... 448399b... A docs/wiki/images/smileys/icon_silenced.gif
:000000 100644 0000000... 7b1f6d3... A docs/wiki/images/smileys/icon_smile.gif
:000000 100644 0000000... 769639d... A docs/wiki/images/smileys/icon_smile2.gif
:000000 100644 0000000... cb21424... A docs/wiki/images/smileys/icon_surprised.gif
:000000 100644 0000000... 502fe24... A docs/wiki/images/smileys/icon_twisted.gif
:000000 100644 0000000... d148288... A docs/wiki/images/smileys/icon_wink.gif
:000000 100644 0000000... 3d39c2e... A docs/wiki/images/tocdot2.gif
:000000 100644 0000000... 4f12acc... A docs/wiki/images/windows.gif
:100644 100644 91d4bf3... d876a26... M docs/wiki/index.html
:100644 000000 23c1897... 0000000... D docs/wiki/lib/.gitignore
:100644 000000 928bc60... 0000000... D docs/wiki/lib/Makefile.am
:100644 000000 23c1897... 0000000... D docs/wiki/lib/exe/.gitignore
:100644 000000 a090af9... 0000000... D docs/wiki/lib/exe/001css
:100644 000000 632fd89... 0000000... D docs/wiki/lib/exe/002css
:100644 000000 3155292... 0000000... D docs/wiki/lib/exe/Makefile.am
:100644 000000 6501c40... 0000000... D docs/wiki/lib/exe/css
:100644 000000 698d1c1... 0000000... D docs/wiki/lib/exe/opensearch
:100644 000000 23c1897... 0000000... D docs/wiki/lib/images/.gitignore
:100644 000000 3180c77... 0000000... D docs/wiki/lib/images/Makefile.am
:100644 000000 8a1ba4c... 0000000... D docs/wiki/lib/images/error.png
:100644 000000 23c1897... 0000000... D docs/wiki/lib/images/fileicons/.gitignore
:100644 000000 39d9948... 0000000... D docs/wiki/lib/images/fileicons/Makefile.am
:100644 000000 9229d87... 0000000... D docs/wiki/lib/images/fileicons/deb.png
:100644 000000 932567f... 0000000... D docs/wiki/lib/images/fileicons/doc.png
:100644 000000 817014f... 0000000... D docs/wiki/lib/images/fileicons/file.png
:100644 000000 b4c07a9... 0000000... D docs/wiki/lib/images/fileicons/gif.png
:100644 000000 2426bd1... 0000000... D docs/wiki/lib/images/fileicons/gz.png
:100644 000000 aa4cc23... 0000000... D docs/wiki/lib/images/fileicons/jpeg.png
:100644 000000 1fb6cc1... 0000000... D docs/wiki/lib/images/fileicons/jpg.png
:100644 000000 47f65c8... 0000000... D docs/wiki/lib/images/fileicons/odc.png
:100644 000000 a2fbc51... 0000000... D docs/wiki/lib/images/fileicons/odf.png
:100644 000000 434f182... 0000000... D docs/wiki/lib/images/fileicons/odg.png
:100644 000000 74f6303... 0000000... D docs/wiki/lib/images/fileicons/odi.png
:100644 000000 a5c77f8... 0000000... D docs/wiki/lib/images/fileicons/odp.png
:100644 000000 2ab1273... 0000000... D docs/wiki/lib/images/fileicons/ods.png
:100644 000000 b0c21fc... 0000000... D docs/wiki/lib/images/fileicons/odt.png
:100644 000000 638066d... 0000000... D docs/wiki/lib/images/fileicons/pdf.png
:100644 000000 f0b5b00... 0000000... D docs/wiki/lib/images/fileicons/png.png
:100644 000000 adaefc6... 0000000... D docs/wiki/lib/images/fileicons/ppt.png
:100644 000000 c51c763... 0000000... D docs/wiki/lib/images/fileicons/ps.png
:100644 000000 a6af4d1... 0000000... D docs/wiki/lib/images/fileicons/rar.png
:100644 000000 22212ea... 0000000... D docs/wiki/lib/images/fileicons/rpm.png
:100644 000000 d8bada5... 0000000... D docs/wiki/lib/images/fileicons/rtf.png
:100644 000000 da20009... 0000000... D docs/wiki/lib/images/fileicons/src.png
:100644 000000 0729ed0... 0000000... D docs/wiki/lib/images/fileicons/swf.png
:100644 000000 419c183... 0000000... D docs/wiki/lib/images/fileicons/sxc.png
:100644 000000 5801bb2... 0000000... D docs/wiki/lib/images/fileicons/sxd.png
:100644 000000 2a94290... 0000000... D docs/wiki/lib/images/fileicons/sxi.png
:100644 000000 6da97be... 0000000... D docs/wiki/lib/images/fileicons/sxw.png
:100644 000000 5a2f717... 0000000... D docs/wiki/lib/images/fileicons/tar.png
:100644 000000 141acf5... 0000000... D docs/wiki/lib/images/fileicons/tgz.png
:100644 000000 e8cd58d... 0000000... D docs/wiki/lib/images/fileicons/xls.png
:100644 000000 999ffbe... 0000000... D docs/wiki/lib/images/fileicons/zip.png
:100644 000000 a237c17... 0000000... D docs/wiki/lib/images/info.png
:100644 000000 73d6f8d... 0000000... D docs/wiki/lib/images/interwiki.png
:100644 000000 23c1897... 0000000... D docs/wiki/lib/images/interwiki/.gitignore
:100644 000000 af23805... 0000000... D docs/wiki/lib/images/interwiki/Makefile.am
:100644 000000 f52c1c5... 0000000... D docs/wiki/lib/images/interwiki/amazon.de.gif
:100644 000000 f52c1c5... 0000000... D docs/wiki/lib/images/interwiki/amazon.gif
:100644 000000 f52c1c5... 0000000... D docs/wiki/lib/images/interwiki/amazon.uk.gif
:100644 000000 0f9f675... 0000000... D docs/wiki/lib/images/interwiki/coral.gif
:100644 000000 7dc4248... 0000000... D docs/wiki/lib/images/interwiki/doku.gif
:100644 000000 3432b8d... 0000000... D docs/wiki/lib/images/interwiki/dokubug.gif
:100644 000000 fb39f61... 0000000... D docs/wiki/lib/images/interwiki/google.gif
:100644 000000 7ac5454... 0000000... D docs/wiki/lib/images/interwiki/meatball.gif
:100644 000000 638d4c4... 0000000... D docs/wiki/lib/images/interwiki/phpfn.gif
:100644 000000 e272a29... 0000000... D docs/wiki/lib/images/interwiki/sb.gif
:100644 000000 e8dc5d2... 0000000... D docs/wiki/lib/images/interwiki/wiki.gif
:100644 000000 ca853b8... 0000000... D docs/wiki/lib/images/interwiki/wp.gif
:100644 000000 ca853b8... 0000000... D docs/wiki/lib/images/interwiki/wpde.gif
:100644 000000 ca853b8... 0000000... D docs/wiki/lib/images/interwiki/wpmeta.gif
:100644 000000 6e0015d... 0000000... D docs/wiki/lib/images/notify.png
:100644 000000 23c1897... 0000000... D docs/wiki/lib/images/smileys/.gitignore
:100644 000000 0615d35... 0000000... D docs/wiki/lib/images/smileys/Makefile.am
:100644 000000 b66ea99... 0000000... D docs/wiki/lib/images/smileys/fixme.gif
:100644 000000 7b1f6d3... 0000000... D docs/wiki/lib/images/smileys/icon_smile.gif
:100644 000000 769639d... 0000000... D docs/wiki/lib/images/smileys/icon_smile2.gif
:100644 000000 d148288... 0000000... D docs/wiki/lib/images/smileys/icon_wink.gif
:100644 000000 a5ae9f1... 0000000... D docs/wiki/lib/images/success.png
:100644 000000 23c1897... 0000000... D docs/wiki/lib/plugins/.gitignore
:100644 000000 2abed10... 0000000... D docs/wiki/lib/plugins/Makefile.am
:100644 000000 23c1897... 0000000... D docs/wiki/lib/plugins/definitionlist/.gitignore
:100644 000000 a6bc1c7... 0000000... D docs/wiki/lib/plugins/definitionlist/Makefile.am
:100644 000000 23c1897... 0000000... D docs/wiki/lib/plugins/definitionlist/images/.gitignore
:100644 000000 8cf81aa... 0000000... D docs/wiki/lib/plugins/definitionlist/images/Makefile.am
:100644 000000 ad7b49a... 0000000... D docs/wiki/lib/plugins/definitionlist/images/bullet.gif
:100644 000000 23c1897... 0000000... D docs/wiki/lib/plugins/note/.gitignore
:100644 000000 dca90ce... 0000000... D docs/wiki/lib/plugins/note/Makefile.am
:100644 000000 23c1897... 0000000... D docs/wiki/lib/plugins/note/images/.gitignore
:100644 000000 4c4ac06... 0000000... D docs/wiki/lib/plugins/note/images/Makefile.am
:100644 000000 dc8c8a4... 0000000... D docs/wiki/lib/plugins/note/images/important.png
:100644 000000 df1e0a9... 0000000... D docs/wiki/lib/plugins/note/images/note.png
:100644 000000 2000f20... 0000000... D docs/wiki/lib/plugins/note/images/tip.png
:100644 000000 3c8a37d... 0000000... D docs/wiki/lib/plugins/note/images/warning.png
:100644 000000 23c1897... 0000000... D docs/wiki/lib/tpl/.gitignore
:100644 000000 aa18857... 0000000... D docs/wiki/lib/tpl/Makefile.am
:100644 000000 ba35770... 0000000... D docs/wiki/lib/tpl/geda/Makefile.am
:100644 000000 ce39b5e... 0000000... D docs/wiki/lib/tpl/geda/images/Makefile.am
:100644 000000 f60be30... 0000000... D docs/wiki/lib/tpl/geda/images/buttonshadow.png
:100644 000000 8414d4d... 0000000... D docs/wiki/lib/tpl/geda/images/closed.gif
:100644 000000 8b9616a... 0000000... D docs/wiki/lib/tpl/geda/images/favicon
:100644 000000 d286beb... 0000000... D docs/wiki/lib/tpl/geda/images/inputshadow.png
:100644 000000 815ccb1... 0000000... D docs/wiki/lib/tpl/geda/images/link_icon.gif
:100644 000000 50a87a9... 0000000... D docs/wiki/lib/tpl/geda/images/mail_icon.gif
:100644 000000 f5d5c7e... 0000000... D docs/wiki/lib/tpl/geda/images/open.gif
:100644 000000 3d39c2e... 0000000... D docs/wiki/lib/tpl/geda/images/tocdot2.gif
:100644 000000 4f12acc... 0000000... D docs/wiki/lib/tpl/geda/images/windows.gif
:100644 100644 eea723f... 094f657... M docs/wiki/libgeda3.html
:000000 100644 0000000... 161d4a2... A docs/wiki/libgeda3_object_based_design.html
:000000 100644 0000000... 23c1897... A docs/wiki/media/.gitignore
:000000 100644 0000000... 8ce7d79... A docs/wiki/media/Makefile.am
:000000 100644 0000000... 23c1897... A docs/wiki/media/devel_tips/.gitignore
:000000 100644 0000000... 2161fde... A docs/wiki/media/devel_tips/Makefile.am
:000000 100644 0000000... 3108609... A docs/wiki/media/devel_tips/dialog_picture.png
:000000 100644 0000000... 23c1897... A docs/wiki/media/geda/.gitignore
:000000 100644 0000000... ab3fb70... A docs/wiki/media/geda/Makefile.am
:000000 100644 0000000... 29ffddb... A docs/wiki/media/geda/ambiguous1.png
:000000 100644 0000000... ae3dc52... A docs/wiki/media/geda/ambiguous1_fixed.png
:000000 100644 0000000... 6189478... A docs/wiki/media/geda/board-1.png
:000000 100644 0000000... 62c351c... A docs/wiki/media/geda/board-2.png
:000000 100644 0000000... f0406e3... A docs/wiki/media/geda/board-3.png
:000000 100644 0000000... ec6eba5... A docs/wiki/media/geda/board-4.png
:000000 100644 0000000... 57ff80d... A docs/wiki/media/geda/board-5.png
:000000 100644 0000000... 0e1189a... A docs/wiki/media/geda/board-6.png
:000000 100644 0000000... 83b57fc... A docs/wiki/media/geda/coordinatespace.jpg
:000000 100644 0000000... 0d6f152... A docs/wiki/media/geda/design_flow.jpg
:000000 100644 0000000... e1f21db... A docs/wiki/media/geda/dialogdirective.png
:000000 100644 0000000... 5d300bd... A docs/wiki/media/geda/dialoginclude.png
:000000 100644 0000000... 49e8e42... A docs/wiki/media/geda/dialogmodel.png
:000000 100644 0000000... 4a7f9a1... A docs/wiki/media/geda/dialogtrans.png
:000000 100644 0000000... 744893e... A docs/wiki/media/geda/dialogvac.png
:000000 100644 0000000... 3e16535... A docs/wiki/media/geda/dialogvdc1.png
:000000 100644 0000000... cca6286... A docs/wiki/media/geda/faq_attrib.jpg
:000000 100644 0000000... 1f49c1c... A docs/wiki/media/geda/fileformat_textgraphic.jpg
:000000 100644 0000000... 79fbf9f... A docs/wiki/media/geda/geda_flow.png
:000000 100644 0000000... dfae00a... A docs/wiki/media/geda/gschem-sym-1.png
:000000 100644 0000000... dfc7d84... A docs/wiki/media/geda/gschem-sym-2.png
:000000 100644 0000000... b76217d... A docs/wiki/media/geda/gschem-sym-3.png
:000000 100644 0000000... 2e0cf68... A docs/wiki/media/geda/gschem_screenshot_001.jpg
:000000 100644 0000000... d1326bc... A docs/wiki/media/geda/gschem_workflow_01.jpg
:000000 100644 0000000... 3311666... A docs/wiki/media/geda/net.jpg
:000000 100644 0000000... 264690e... A docs/wiki/media/geda/nets.jpg
:000000 100644 0000000... 3824b47... A docs/wiki/media/geda/one-sch-1.png
:000000 100644 0000000... 9028fc2... A docs/wiki/media/geda/one-sch-2.png
:000000 100644 0000000... 82e65ea... A docs/wiki/media/geda/one-sch-3.png
:000000 100644 0000000... 6920014... A docs/wiki/media/geda/paper1.gif
:000000 100644 0000000... 303863f... A docs/wiki/media/geda/path_example_and_gate-smaller.png
:000000 100644 0000000... 7e46fa9... A docs/wiki/media/geda/path_example_and_gate.png
:000000 100644 0000000... 84d5bc3... A docs/wiki/media/geda/pcb-el-1.png
:000000 100644 0000000... 41d7322... A docs/wiki/media/geda/pcb-el-2.png
:000000 100644 0000000... 2521dfe... A docs/wiki/media/geda/rf_cascade_figure1.jpg
:000000 100644 0000000... b271a65... A docs/wiki/media/geda/rf_cascade_figure2.jpg
:000000 100644 0000000... b3fcf5e... A docs/wiki/media/geda/schematicfinished.png
:000000 100644 0000000... 6a381b7... A docs/wiki/media/geda/schematicfinished2.png
:000000 100644 0000000... a7fce1e... A docs/wiki/media/geda/simple1.png
:000000 100644 0000000... 394ef3a... A docs/wiki/media/geda/status_screenshot.jpg
:000000 100644 0000000... 16881ed... A docs/wiki/media/geda/suse_electronics_menu.png
:000000 100644 0000000... 5313e53... A docs/wiki/media/geda/switcap_figure1.jpg
:000000 100644 0000000... b9e0f6a... A docs/wiki/media/geda/switcap_figure2.jpg
:000000 100644 0000000... 6617c00... A docs/wiki/media/geda/switcap_figure3.jpg
:000000 100644 0000000... 639985b... A docs/wiki/media/geda/switcap_figure4.jpg
:000000 100644 0000000... e817f55... A docs/wiki/media/geda/symbol_7400-1.png
:000000 100644 0000000... 22807da... A docs/wiki/media/geda/symbol_7400-1_hidden.png
:000000 100644 0000000... 1b28256... A docs/wiki/media/geda/terminal_screenshot_001.jpg
:000000 100644 0000000... 74b59c9... A docs/wiki/media/geda/two-sch-1.png
:000000 100644 0000000... 9448d26... A docs/wiki/media/geda/two-sch-2.png
:000000 100644 0000000... cfd5794... A docs/wiki/media/geda/warmup_add_component.png
:000000 100644 0000000... 1191d90... A docs/wiki/media/geda/warmup_gschem01.png
:000000 100644 0000000... af49239... A docs/wiki/media/geda/warmup_gschem02.png
:000000 100644 0000000... e9da8d3... A docs/wiki/media/geda/warmup_gschem03.png
:000000 100644 0000000... 23c1897... A docs/wiki/media/tragesym/.gitignore
:000000 100644 0000000... 857988c... A docs/wiki/media/tragesym/Makefile.am
:000000 100644 0000000... 796cd9b... A docs/wiki/media/tragesym/acroread_selectiontable.png
:000000 100644 0000000... ccd4d82... A docs/wiki/media/tragesym/gschem_finished.png
:000000 100644 0000000... 8a2a067... A docs/wiki/media/tragesym/gschem_showhidden.png
:000000 100644 0000000... 72fc148... A docs/wiki/media/tragesym/kpdf_pinconfiguration.png
:000000 100644 0000000... 6c5b49e... A docs/wiki/media/tragesym/kpdf_pindescription.png
:000000 100644 0000000... 3e6fdc8... A docs/wiki/media/tragesym/ooo_attributes.png
:000000 100644 0000000... 5446849... A docs/wiki/media/tragesym/ooo_changedpins.png
:000000 100644 0000000... 100395b... A docs/wiki/media/tragesym/ooo_rearanged.png
:000000 100644 0000000... 41a6a11... A docs/wiki/media/tragesym/ooo_selection.png
:000000 100644 0000000... 425e9af... A docs/wiki/media/tragesym/template.ods
:000000 100644 0000000... ac3839e... A docs/wiki/media/tragesym/template.txt
:000000 100644 0000000... f414b79... A docs/wiki/media/tragesym/template2.ods
:000000 100644 0000000... 4e507c3... A docs/wiki/media/tragesym/template2.txt.src
:000000 100644 0000000... 23c1897... A docs/wiki/media/tragesym/tragesym/.gitignore
:000000 100644 0000000... f9a94aa... A docs/wiki/media/tragesym/tragesym/Makefile.am
:000000 100644 0000000... 6c5b49e... A docs/wiki/media/tragesym/tragesym/kpdf_pindescription.png
:000000 100644 0000000... dd2ce2d... A docs/wiki/media/tragesym/xemacs_modifiedselection.png
:000000 100644 0000000... 8a86702... A docs/wiki/media/tragesym/xemacs_rawselection.png
:000000 100644 0000000... 23c1897... A docs/wiki/media/wiki/.gitignore
:000000 100644 0000000... 5b6761f... A docs/wiki/media/wiki/Makefile.am
:000000 100644 0000000... b2306ac... A docs/wiki/media/wiki/dokuwiki-128.png
:100644 100644 313e973... f546a40... M docs/wiki/pcb-projects.html
:000000 100644 0000000... 4f6c787... A docs/wiki/playground-playground.html
:000000 100644 0000000... f13fe82... A docs/wiki/playground-transistor_guide.html
:000000 100644 0000000... 77c82a5... A docs/wiki/print.css
:000000 100644 0000000... d876a26... A docs/wiki/start.html
:100644 100644 22ace54... 540ce33... M docs/wiki/start_es.html
:100644 100644 ba5c00a... b629fc9... M docs/wiki/start_fr.html
:000000 100644 0000000... 4e19909... A docs/wiki/style.css
:000000 100644 0000000... aac904c... A docs/wiki/wiki-dokuwiki.html
:000000 100644 0000000... 17b47f2... A docs/wiki/wiki-syntax.html
:100644 100644 8cbfc4b... c24cde8... M gschem/scripts/gschemdoc.sh
=========
Changes
=========
commit 3edef9ffb6ebb859213efea337e3bd419b99da8e
Author: Ales Hvezda <ahvezda@xxxxxxxx>
Commit: Ales Hvezda <ahvezda@xxxxxxxx>
Spacing tweak
diff --git a/configure.ac b/configure.ac
index c7090c5..0edb800 100644
--- a/configure.ac
+++ b/configure.ac
@@ -257,7 +257,7 @@ AC_CONFIG_FILES([Makefile
symbols/Makefile
symbols/documentation/Makefile
- docs/Makefile
+ docs/Makefile
docs/scripts/Makefile
docs/toplevel/Makefile
docs/toplevel/gedadocs.html
commit b7ca06041ea464b0d064bfa965843d2907a83571
Author: Ales Hvezda <ahvezda@xxxxxxxx>
Commit: Ales Hvezda <ahvezda@xxxxxxxx>
Updated the wiki docs from the online version (in prep for the next release)
(Un)fortunately, the previous mechanism for updating the wiki offline
docs from the online version is completely broken now (due to a segfault
in an external tool), so a new mechanism was used to download the files.
The good news is that the number of files and directories that need to
be downloaded has been reduced considerably. This is the first cut
of the wiki sync.
diff --git a/configure.ac b/configure.ac
index 7a2cb31..c7090c5 100644
--- a/configure.ac
+++ b/configure.ac
@@ -257,27 +257,20 @@ AC_CONFIG_FILES([Makefile
symbols/Makefile
symbols/documentation/Makefile
- docs/Makefile
+ docs/Makefile
docs/scripts/Makefile
docs/toplevel/Makefile
docs/toplevel/gedadocs.html
docs/wiki/Makefile
- docs/wiki/_detail/Makefile
- docs/wiki/_media/Makefile
- docs/wiki/lib/Makefile
- docs/wiki/lib/exe/Makefile
- docs/wiki/lib/images/Makefile
- docs/wiki/lib/images/fileicons/Makefile
- docs/wiki/lib/images/interwiki/Makefile
- docs/wiki/lib/images/smileys/Makefile
- docs/wiki/lib/plugins/Makefile
- docs/wiki/lib/plugins/definitionlist/Makefile
- docs/wiki/lib/plugins/definitionlist/images/Makefile
- docs/wiki/lib/plugins/note/Makefile
- docs/wiki/lib/plugins/note/images/Makefile
- docs/wiki/lib/tpl/Makefile
- docs/wiki/lib/tpl/geda/Makefile
- docs/wiki/lib/tpl/geda/images/Makefile
+ docs/wiki/images/smileys/Makefile
+ docs/wiki/images/Makefile
+ docs/wiki/images/interwiki/Makefile
+ docs/wiki/media/geda/Makefile
+ docs/wiki/media/wiki/Makefile
+ docs/wiki/media/tragesym/tragesym/Makefile
+ docs/wiki/media/tragesym/Makefile
+ docs/wiki/media/Makefile
+ docs/wiki/media/devel_tips/Makefile
examples/Makefile
examples/RF_Amp/Makefile
diff --git a/docs/wiki/001geda_debian.html b/docs/wiki/001geda_debian.html
deleted file mode 100644
index d5c32fb..0000000
--- a/docs/wiki/001geda_debian.html
+++ /dev/null
@@ -1,58 +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>geda:debian.fr</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="keywords" content="geda,debian.fr" />
-<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/geda:debian.fr?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:debian.fr"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:debian.fr"; />
-<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">
-
-
-
-<h1><a name="notes_d_installation_debian_de_la_version_20060825" id="notes_d_installation_debian_de_la_version_20060825">Notes d'installation Debian de la version 20060825</a></h1>
-<div class="level1">
-
-<p>
- Voici un rapport dâ??utilisateur qui fournit quelques éléments aux personnes installant avec le CDROM 20060825 sur une Debian. Notez que lâ??utilisateur avec pré-ajouté les paquets -dev sur son système au lieu de laisser lâ??installateur les trouver. Câ??est une manière parfaitement acceptable – et souvent préférable – de traiter les dépendances de gEDA.
-</p>
-<pre class="code">
-Just completed an install on my main desktop box which is Debian
-etch/testing with patches of sid/unstable.
-
-Lib packages I had to add to my system:
- * libreadline5-dev
- * libgd1-xpm-dev
- * libwxgtk2.6-dev
- * libgtk1.2-dev (compile failed because of missing gtk-config.
- Configure did not seem to check for it.)
- * I needed to install guile-1.6-dev rather than libguile-dev.
- Else the installer fails to find scm_make_smob_type.
-
-On my system /usr/lib/libqthreads.so pointed to a non existing
-/usr/lib/libqthreads.so.12.3.1 This may be a bug in Debians packaging
-rules. Thus the installer failed with:
- gcc: /usr/lib/libqthreads.so: No such file or directory make[2]:*** [libgeda.la] Error 1
-I resolved the issue by faking a link:
- sudo ln -s libqthreads.so.12.3.0 libqthreads.so.12.3.1
-</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/001geda_documentation.html b/docs/wiki/001geda_documentation.html
deleted file mode 100644
index ef342a6..0000000
--- a/docs/wiki/001geda_documentation.html
+++ /dev/null
@@ -1,383 +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>geda:documentation.fr</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-06-27T07:42:20-0400" />
-<meta name="keywords" content="geda,documentation.fr" />
-<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/geda:documentation.fr?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:documentation.fr"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:documentation.fr"; />
-<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="#documentation_en_ligne_de_la_suite_d_outils_geda" class="toc">Documentation en ligne de la Suite d'Outils gEDA</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#for_document_authors" class="toc">For document authors</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#gschem_-_saisie_de_schemas" class="toc">gschem - Saisie de Schémas</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#gnetlist_-_netlister" class="toc">gnetlist - Netlister</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#gsymcheck_-_symbol_checker" class="toc">gsymcheck - Symbol Checker</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#utils_-_geda_utilities" class="toc">utils - gEDA Utilities</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#examples" class="toc">Examples</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#attribute_file_format_details" class="toc">Attribute/File Format Details</a></span></div></li>
-</ul>
-</li>
-<li class="level1"><div class="li"><span class="li"><a href="#spice" class="toc">SPICE</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#ngspice" class="toc">ngspice</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#gnucap" class="toc">gnucap</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#gspiceui" class="toc">gSpiceUI</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#pcb" class="toc">PCB</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#gerbv" class="toc">gerbv</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#icarus_verilog" class="toc">Icarus Verilog</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#gtkwave" class="toc">GTKWave</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#wcalc" class="toc">Wcalc</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#mcalc" class="toc">mcalc</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#covered" class="toc">covered</a></span></div></li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="documentation_en_ligne_de_la_suite_d_outils_geda" id="documentation_en_ligne_de_la_suite_d_outils_geda">Documentation en ligne de la Suite d'Outils gEDA</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "Documentation en ligne de la Suite d'Outils gEDA" [1-64] -->
-<h2><a name="for_document_authors" id="for_document_authors">For document authors</a></h2>
-<div class="level2">
-
-<p>
-New features are available for document authors:
-</p>
-<ul>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:syntax_features"; class="wikilink1" title="geda:syntax_features">Syntax features</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:installed_plugins"; class="wikilink1" title="geda:installed_plugins">Installed plugins</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:style_guide"; class="wikilink1" title="geda:style_guide">Style Guide</a> – A work in progress, please contribute</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "For document authors" [65-273] -->
-<h2><a name="gschem_-_saisie_de_schemas" id="gschem_-_saisie_de_schemas">gschem - Saisie de Schémas</a></h2>
-<div class="level2">
-<ul>
-<li class="level1"><div class="li"> <a href="001geda_gschem_ug.html" class="wikilink1" title="geda:gschem_ug.fr">Guide de l'Utilisateur gschem</a> – En cours, vous pouvez participer</div>
-</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>
-<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>
-<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>
-</ul>
-
-</div>
-<!-- SECTION "gschem - Saisie de Schémas" [274-634] -->
-<h2><a name="gnetlist_-_netlister" id="gnetlist_-_netlister">gnetlist - Netlister</a></h2>
-<div class="level2">
-<ul>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:gnetlist_ug"; class="wikilink1" title="geda:gnetlist_ug">gnetlist User's Guide</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:gnetlist_mp"; class="wikilink1" title="geda:gnetlist_mp">gnetlist man-page</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:sdb_howto"; class="wikilink1" title="geda:sdb_howto">Spice netlisting (SDB) HOWTO</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:na_howto"; class="wikilink1" title="geda:na_howto">net= attribute mini-HOWTO</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:ssan"; class="wikilink1" title="geda:ssan">Switcap Symbols and Netlister</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:sn_readme"; class="wikilink1" title="geda:sn_readme">Switcap netlister README</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:fbabgapp"; class="wikilink1" title="geda:fbabgapp">Forward/Backward Annotation Between gEDA and Pads PowerPCB</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:grcsan"; class="wikilink1" title="geda:grcsan">gEDA RF Cascade Symbols and Netlister</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:bom_readme"; class="wikilink1" title="geda:bom_readme">Bill of Material netlister README</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:gschem2pcb_readme"; class="wikilink1" title="geda:gschem2pcb_readme">gschem2pcb README</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:verilog_netlister_readme"; class="wikilink1" title="geda:verilog_netlister_readme">Verilog netlister README</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:vhdl_netlister_readme"; class="wikilink1" title="geda:vhdl_netlister_readme">VHDL netlister README</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:vams_netlister_readme"; class="wikilink1" title="geda:vams_netlister_readme">VAMS netlister README</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:systemc_netlister_readme"; class="wikilink1" title="geda:systemc_netlister_readme">SystemC netlister README</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:eagle_pcb_netlister_readme"; class="wikilink1" title="geda:eagle_pcb_netlister_readme">Eagle PCB netlister README</a></div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "gnetlist - Netlister" [635-1507] -->
-<h2><a name="gsymcheck_-_symbol_checker" id="gsymcheck_-_symbol_checker">gsymcheck - Symbol Checker</a></h2>
-<div class="level2">
-<ul>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:gsymcheck_mp"; class="wikilink1" title="geda:gsymcheck_mp">gsymcheck man-page</a></div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "gsymcheck - Symbol Checker" [1508-1592] -->
-<h2><a name="utils_-_geda_utilities" id="utils_-_geda_utilities">utils - gEDA Utilities</a></h2>
-<div class="level2">
-<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>
-<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>
-<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>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:grenum_mp"; class="wikilink1" title="geda:grenum_mp">grenum man-page</a> – note</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:gattrib_readme"; class="wikilink1" title="geda:gattrib_readme">gattrib README</a> – note</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "utils - gEDA Utilities" [1593-2012] -->
-<h2><a name="examples" id="examples">Examples</a></h2>
-<div class="level2">
-<ul>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:example_hsm"; class="wikilink1" title="geda:example_hsm">Hierarchical SPICE model</a> – note</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:example_usbjtag"; class="wikilink1" title="geda:example_usbjtag">Example USB-based JTAG interface</a> – note</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Examples" [2013-2162] -->
-<h2><a name="attribute_file_format_details" id="attribute_file_format_details">Attribute/File Format Details</a></h2>
-<div class="level2">
-<ul>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:master_attributes_list"; class="wikilink1" title="geda:master_attributes_list">Master Attributes List</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:file_format_spec"; class="wikilink1" title="geda:file_format_spec">sym/sch File Format Specification</a></div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Attribute/File Format Details" [2163-2328] -->
-<h1><a name="spice" id="spice">SPICE</a></h1>
-<div class="level1">
-<ul>
-<li class="level1"><div class="li"> <a href="http://www.geda.seul.org/tools/gnucap/papers/al-davis-dissertation.pdf"; class="urlextern" title="http://www.geda.seul.org/tools/gnucap/papers/al-davis-dissertation.pdf"; rel="nofollow">Implicit Mixed-Mode Simulation of VLSI Circuits</a> by Albert Tatum Davis (1991)<br/>
- Please report if this <acronym title="Uniform Resource Locator">URL</acronym> goes dead.</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://www.brorson.com/gEDA/SPICE/intro.html"; class="urlextern" title="http://www.brorson.com/gEDA/SPICE/intro.html"; rel="nofollow">Circuit Simulation using gEDA and SPICE - HOWTO</a> (<acronym title="HyperText Markup Language">HTML</acronym> version)<br/>
- by Stuart Brorson (20 December 2004).<br/>
- Please report if this <acronym title="Uniform Resource Locator">URL</acronym> is not the latest version.</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://www.brorson.com/gEDA/HOWTO/gEDA_Spice_HOWTO-20050103.pdf"; class="urlextern" title="http://www.brorson.com/gEDA/HOWTO/gEDA_Spice_HOWTO-20050103.pdf"; rel="nofollow">Circuit Simulation using gEDA and SPICE - HOWTO</a> (<acronym title="Portable Document Format">PDF</acronym> version)<br/>
- by Stuart Brorson ( 5 January 2005).</div>
-</li>
-</ul>
-
-<p>
- Testing:
-</p>
-<ul>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:csygas"; class="wikilink1" title="geda:csygas">Circuit Simulation using gEDA and SPICE - HOWTO</a> – Done converting. Please comment on this conversion to a wiki-format.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "SPICE" [2329-3078] -->
-<h1><a name="ngspice" id="ngspice">ngspice</a></h1>
-<div class="level1">
-<ul>
-<li class="level1"><div class="li"> <a href="http://www-ti.informatik.uni-tuebingen.de/~bernauer/lehre/ti-1-0506/spice/ngspice.pdf"; class="urlextern" title="http://www-ti.informatik.uni-tuebingen.de/~bernauer/lehre/ti-1-0506/spice/ngspice.pdf"; rel="nofollow">NGSPICE User Manual</a> – describes ngspice-rework-17, Draft Version 0.2<br/>
- Please report if this <acronym title="Uniform Resource Locator">URL</acronym> is not the appropriated version, or if it goes dead.</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:ngspice_mp"; class="wikilink1" title="geda:ngspice_mp">ngspice man-page</a> – note</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:ngnutmeg_mp"; class="wikilink1" title="geda:ngnutmeg_mp">ngnutmeg man-page</a> – note</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:ngsconvert_mp"; class="wikilink1" title="geda:ngsconvert_mp">ngsconvert man-page</a> – note</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "ngspice" [3079-3501] -->
-<h1><a name="gnucap" id="gnucap">gnucap</a></h1>
-<div class="level1">
-<ul>
-<li class="level1"><div class="li"> <a href="http://www.geda.seul.org/tools/gnucap/gnucap-man.pdf"; class="urlextern" title="http://www.geda.seul.org/tools/gnucap/gnucap-man.pdf"; rel="nofollow">The Gnu Circuit Analysis Package Users manual</a> – January 21,2004 version</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://www.geda.seul.org/tools/gnucap/papers/gnucap-model-compiler.pdf"; class="urlextern" title="http://www.geda.seul.org/tools/gnucap/papers/gnucap-model-compiler.pdf"; rel="nofollow">The Gnucap Model Compiler</a></div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "gnucap" [3502-3762] -->
-<h1><a name="gspiceui" id="gspiceui">gSpiceUI</a></h1>
-<div class="level1">
-<ul>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/shared/gEDA-20060124/Documents/gSpiceUI/gSpiceUI.html"; class="urlextern" title="file:///shared/gEDA-20060124/Documents/gSpiceUI/gSpiceUI.html" rel="nofollow">GNU Spice GUI</a></div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "gSpiceUI" [3763-3870] -->
-<h1><a name="pcb" id="pcb">PCB</a></h1>
-<div class="level1">
-<ul>
-<li class="level1"><div class="li"> <a href="geda_pcb_ug.html" class="wikilink2" title="geda:pcb_ug">Pcb-1.99q</a> – gEDA Suite version 20060123</div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_footprint_creation.html" class="wikilink2" title="geda:footprint_creation">footprint_creation</a> – Stuart Brorsonâ??s document, is this the latest?</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:pcb_mp"; class="wikilink1" title="geda:pcb_mp">PCB man-page</a></div>
-</li>
-<li class="level1"><div class="li"></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://pcb.sourceforge.net/manual.html"; class="urlextern" title="http://pcb.sourceforge.net/manual.html"; rel="nofollow">Recent development shapshot manuals and the current CVS version manual</a></div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "PCB" [3871-4187] -->
-<h1><a name="gerbv" id="gerbv">gerbv</a></h1>
-<div class="level1">
-<ul>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:gerbv_mp"; class="wikilink1" title="geda:gerbv_mp">gerbv man-page</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:gerbv_pnp_readme"; class="wikilink1" title="geda:gerbv_pnp_readme">Searching for Parts and marking them on screen (in gerbv)</a></div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "gerbv" [4188-4333] -->
-<h1><a name="icarus_verilog" id="icarus_verilog">Icarus Verilog</a></h1>
-<div class="level1">
-<ul>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:icarus_quick_start"; class="wikilink1" title="geda:icarus_quick_start">Getting Started with Icarus Verilog</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:icarus_mp"; class="wikilink1" title="geda:icarus_mp">Icarus Verilog compiler man-page</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:icarus_vpi_mp"; class="wikilink1" title="geda:icarus_vpi_mp">Compile front end for VPI modules man-page</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:icarus_vvp_runtime"; class="wikilink1" title="geda:icarus_vvp_runtime">Icarus Verilog vvp runtime engine man-page</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:icarus_readme"; class="wikilink1" title="geda:icarus_readme">The Icarus Verilog Compilation System</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:igarus_fpga_lcg"; class="wikilink1" title="geda:igarus_fpga_lcg">FPGA Loadable Code Generator for Icarus Verilog</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:icarus_xilinx_hints"; class="wikilink1" title="geda:icarus_xilinx_hints">Xilinx Hints</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:icarus_xnf"; class="wikilink1" title="geda:icarus_xnf">Xilinx Netlist Format</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:icarus_ieee1364"; class="wikilink1" title="geda:icarus_ieee1364">Icarus Verilog vs. IEEE1364</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:icarus_anc"; class="wikilink1" title="geda:icarus_anc">Icarus Attribute Naming Conventions</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:icarus_extensions"; class="wikilink1" title="geda:icarus_extensions">Icarus Verilog Extensions</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:icarus_glossary"; class="wikilink1" title="geda:icarus_glossary">Icarus Verilog Glossary</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:icarus_opcodes"; class="wikilink1" title="geda:icarus_opcodes">Executable Instruction Opcodes</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:icarus_vpi_within_vvp"; class="wikilink1" title="geda:icarus_vpi_within_vvp">VPI_within_VVP</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:icarus_vvp_simulation"; class="wikilink1" title="geda:icarus_vvp_simulation">VVP Simulation Engine</a></div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Icarus Verilog" [4334-5259] -->
-<h1><a name="gtkwave" id="gtkwave">GTKWave</a></h1>
-<div class="level1">
-<ul>
-<li class="level1"><div class="li"> <a href="http://home.nc.rr.com/gtkwave/"; class="urlextern" title="http://home.nc.rr.com/gtkwave/"; rel="nofollow">Welcome to GTKWave</a> – Now for version 3.0 (the promoted version 1.3)</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:gtkwave_mp"; class="wikilink1" title="geda:gtkwave_mp">Visualization tool for VCD, LXT, and VZT files (gtkwave)</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:gtkwave_lxt2miner_mp"; class="wikilink1" title="geda:gtkwave_lxt2miner_mp">Data mining of LXT2 files (lxt2miner)</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:gtkwave_lxt2vcd_mp"; class="wikilink1" title="geda:gtkwave_lxt2vcd_mp">Coverts LXT2 files to VCD (lxt2vcd)</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:gtkwave_mvl2lxt_mp"; class="wikilink1" title="geda:gtkwave_mvl2lxt_mp">Coverts MVLSIM AET files to LXT (mvl2lxt)</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:gtkwave_mvl2vcd_mp"; class="wikilink1" title="geda:gtkwave_mvl2vcd_mp">Coverts MVLSIM AET files to VCD (mvl2vcd)</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:gtkwave_tex2vcd_mp"; class="wikilink1" title="geda:gtkwave_tex2vcd_mp">Coverts TEXSIM AET files to VCD (tex2vcd)</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:gtkwave_tla2vcd_mp"; class="wikilink1" title="geda:gtkwave_tla2vcd_mp">Converts TLA to VCD or LST files (tla2vcd)</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:gtkwave_vcd2lxt_mp"; class="wikilink1" title="geda:gtkwave_vcd2lxt_mp">Converts VCD files to interlaced or linear LXT files (vcd2lxt)</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:gtkwave_vcd2lxt2_mp"; class="wikilink1" title="geda:gtkwave_vcd2lxt2_mp">Converts VCD files to LXT2 files (vcd2lxt2)</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:gtkwave_vcd2vzt_mp"; class="wikilink1" title="geda:gtkwave_vcd2vzt_mp">Converts VCD files to VZT files
- (vcd2vzt)</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:gtkwave_vzt2vcd_mp"; class="wikilink1" title="geda:gtkwave_vzt2vcd_mp">Coverts VZT files to VCD (vzt2vcd)</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:gtkwave_vztminer_mp"; class="wikilink1" title="geda:gtkwave_vztminer_mp">Data mining of VZT files (vztminer)</a></div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "GTKWave" [5260-6291] -->
-<h1><a name="wcalc" id="wcalc">Wcalc</a></h1>
-<div class="level1">
-<ul>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:wcalc_readme"; class="wikilink1" title="geda:wcalc_readme">Wcalc README</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:wcalc_mp"; class="wikilink1" title="geda:wcalc_mp">Wcalc man-page</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:wcalc_stdio_mp"; class="wikilink1" title="geda:wcalc_stdio_mp">stdio Wcalc man-page</a></div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Wcalc" [6292-6438] -->
-<h1><a name="mcalc" id="mcalc">mcalc</a></h1>
-<div class="level1">
-<ul>
-<li class="level1"><div class="li"> <a href="http://mcalc.sourceforge.net/"; class="urlextern" title="http://mcalc.sourceforge.net/"; rel="nofollow">Microstrip Analysis/Synthesis Calculator</a> – latest documentation from sourceforge</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:mcalc_readme"; class="wikilink1" title="geda:mcalc_readme">mcalc README</a></div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "mcalc" [6439-6618] -->
-<h1><a name="covered" id="covered">covered</a></h1>
-<div class="level1">
-<ul>
-<li class="level1"><div class="li"> <a href="http://covered.sourceforge.net/user/index.html"; class="urlextern" title="http://covered.sourceforge.net/user/index.html"; rel="nofollow">covered User Manual</a> – link to latest covered documentation on sourceforge</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:covered_rv"; class="wikilink2" title="geda:covered_rv">covered Report Viewer</a> – available in the Help menu of the <acronym title="Graphical User Interface">GUI</acronym> report utility</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:covered_mp"; class="wikilink1" title="geda:covered_mp">covered man-page</a></div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "covered" [6619-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/001geda_faq-attribs.html b/docs/wiki/001geda_faq-attribs.html
deleted file mode 100644
index 041af9a..0000000
--- a/docs/wiki/001geda_faq-attribs.html
+++ /dev/null
@@ -1,251 +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>geda:faq-attribs.fr</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-05-24T22:27:26-0400" />
-<meta name="keywords" content="geda,faq-attribs.fr" />
-<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/geda:faq-attribs.fr?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:faq-attribs.fr"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:faq-attribs.fr"; />
-<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="#generation_de_bom_bill_of_materials" class="toc">Génération de BOM (Bill Of Materials)</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#j_ai_cree_un_nouveau_dessin._comment_je_cree_une_bom" class="toc">J'ai créé un nouveau dessin. Comment je crée une BOM?</a></span></div></li>
-</ul>
-</li>
-<li class="level1"><div class="li"><span class="li"><a href="#drc" class="toc">DRC</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#comment_je_controle_mes_schemas" class="toc">Comment je contrôle mes schémas?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#comment_je_peux_voir_la_sortie_de_drc_a_l_ecran_sans_l_ecrire_dans_un_fichier" class="toc">Comment je peux voir la sortie de DRC à l'écran, sans l'écrire dans un fichier?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#je_veux_desactiver_quelque_uns_des_controles_de_drc_du_schema._comment_faire" class="toc">Je veux désactiver quelque uns des contrôles de DRC du schéma. Comment faire?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#puis-je_inclure_le_controle_de_drc_dans_un_makefile_et_stopper_lorsque_des_erreurs_ou_des_avertissements_sont_trouves" class="toc">Puis-je inclure le contrôle de DRC dans un Makefile et stopper lorsque des erreurs ou des avertissements sont trouvés?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#il_y_a_quelques_avertissements_sur_mon_schema_que_je_connais._puis-je_les_ignorer_dans_la_return_value" class="toc">Il y a quelques avertissements sur mon schéma que je connais. Puis-je les ignorer dans la return value?</a></span></div></li>
-</ul>
-</li>
-<li class="level1"><div class="li"><span class="li"><a href="#gestion_d_attribut" class="toc">Gestion d'attribut</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#au_secours_mon_schema_a_des_centaines_de_composants_et_c_est_penible_d_utiliser_gschem_pour_attacher_tous_mes_attributs" class="toc">Au secours! Mon schéma a des centaines de composants et c'est pénible d'utiliser gschem pour attacher tous mes attributs!</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#comment_savoir_que_nom_d_empreinte_utiliser_pour_le_placement_avec_pcb" class="toc">Comment savoir que nom d'empreinte utiliser pour le placement avec PCB?</a></span></div></li></ul>
-</li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="generation_de_bom_bill_of_materials" id="generation_de_bom_bill_of_materials">Génération de BOM (Bill Of Materials)</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "Génération de BOM (Bill Of Materials)" [1-55] -->
-<h2><a name="j_ai_cree_un_nouveau_dessin._comment_je_cree_une_bom" id="j_ai_cree_un_nouveau_dessin._comment_je_cree_une_bom">J'ai créé un nouveau dessin. Comment je crée une BOM?</a></h2>
-<div class="level2">
-
-<p>
-Il existe plusieurs manières dâ??exporter une BOM depuis votre dessin car il existe des extensions de gEDA. En fait, il existe 5 ou 6 interfaces différentes à gnetlist qui vous permet dâ??exporter une BOM. Câ??est la raison pour laquelle, il est facile pour le débutant dâ??être perturbé sur lâ??approche à utiliser. Une raison, bonne simple et raisonnablemant complète est celle-ci:
-</p>
-<ul>
-<li class="level1"><div class="li"> Créer un fichier appelé «·attribs·» dans votre répertoire de projet. Dans ce fichier, placez chaque attribut dont vous voulez exporter les valeurs sur une ligne séparée. Vous avez un exemple ici:<pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">value
-Mfr
-Mfr_PN
-Vendor
-Vendor_PN</font></pre></div>
-</li>
-<li class="level1"><div class="li"> Netlistez votre schéma en utilisant la commande suivante:<br/>
- <br/>
- <code>gnetlist -v -g bom2 -o MyDesign.bom MyDesign.sch</code> <br/>
- <br/>
- Notez que le drapeau <strong><code>-v</code></strong> fournira une sortie bavarde, vous indiquant ce qui entre dans gnetlist lors de son lancement. Cela peut être utile si vous avez besoin de diagnostiquer un problème avec le netlisting.</div>
-</li>
-<li class="level1"><div class="li"> Avec cette commande, gnetlist sauvegardera une BOM dans le ficheir «·MyDesign.bom·». Les éléments de la BOM seront séparés en utilisant un caractère «·:·» (deux points). Vous pouvez alors lire ce fichier avec un tableur. Assurez-vous dâ??importer la BOM comme un fichier .csv et spécifiez le caractère «·:·» comme séparateur.</div>
-</li>
-</ul>
-
-<p>
- Plusieurs autres méthodes pour créer des BOM existent. Peut-être que dâ??autres geda-users posteront leur méthode favorite ici?!?!?
-</p>
-
-</div>
-<!-- SECTION "J'ai créé un nouveau dessin. Comment je crée une BOM?" [56-1593] -->
-<h1><a name="drc" id="drc">DRC</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "DRC" [1594-1611] -->
-<h2><a name="comment_je_controle_mes_schemas" id="comment_je_controle_mes_schemas">Comment je contrôle mes schémas?</a></h2>
-<div class="level2">
-
-<p>
-Vous pouvez contrôler votre schéma en utilisant le programme de gnetlist drc2. Il vérifiera votre schéma pour les erreurs les plus habituelles, comme la duplication des références, les broches non connectées, les slots inutilisés et bien plus.
-</p>
-
-<p>
-Lancez le programme drc2 avec la commande suivante:
-</p>
-<pre class="code">gnetlist -g drc2 -o MyDesign.drc MyDesign.sch</pre>
-
-<p>
-Avec cette commande, la sortie DRC est écrite dans le ficheir «·MyDesign.drc·». Vous pouvez alors voir ce fichier avec un éditeur de texte et visualiser les avertissements et erreurs de DRC.
-</p>
-
-</div>
-<!-- SECTION "Comment je contrôle mes schémas?" [1612-2221] -->
-<h2><a name="comment_je_peux_voir_la_sortie_de_drc_a_l_ecran_sans_l_ecrire_dans_un_fichier" id="comment_je_peux_voir_la_sortie_de_drc_a_l_ecran_sans_l_ecrire_dans_un_fichier">Comment je peux voir la sortie de DRC à l'écran, sans l'écrire dans un fichier?</a></h2>
-<div class="level2">
-
-<p>
-Lancez drc2 avec la commande suivante:
-</p>
-<pre class="code">gnetlist -g drc2 -o - MyDesign.sch</pre>
-
-<p>
-De cette manière, vous verrez la sortie DRC directement sur votre écran.
-</p>
-
-</div>
-<!-- SECTION "Comment je peux voir la sortie de DRC à l'écran, sans l'écrire dans un fichier?" [2222-2480] -->
-<h2><a name="je_veux_desactiver_quelque_uns_des_controles_de_drc_du_schema._comment_faire" id="je_veux_desactiver_quelque_uns_des_controles_de_drc_du_schema._comment_faire">Je veux désactiver quelque uns des contrôles de DRC du schéma. Comment faire?</a></h2>
-<div class="level2">
-
-<p>
-drc2 est hautement configurable. Vous devez placer quelques commandes spéciales dans un fichier et utiliser lâ??option «·-l·» de gnetlist.
-</p>
-
-<p>
-Les commandes les plus habituelles sont:
-</p>
-<ul>
-<li class="level1"><div class="li"> (define dont-check-non-numbered-parts 1) ;; Disable the non-numbered parts check</div>
-</li>
-<li class="level1"><div class="li"> (define dont-check-duplicated-references 1) ;; Disable the duplicate references check</div>
-</li>
-<li class="level1"><div class="li"> (define dont-check-one-connection-nets 1) ;; Disable the check for nets with only one connection.</div>
-</li>
-<li class="level1"><div class="li"> (define dont-check-pintypes-of-nets 1) ;; Disable the pintype check</div>
-</li>
-<li class="level1"><div class="li"> (define dont-check-not-driven-nets 1) ;; Disable the driven net check</div>
-</li>
-<li class="level1"><div class="li"> (define dont-check-unconnected-pins 1) ;; Disable the unconnected pins check</div>
-</li>
-<li class="level1"><div class="li"> (define dont-check-duplicated-slots 1) ;; Disable the duplicated slots check</div>
-</li>
-<li class="level1"><div class="li"> (define dont-check-unused-slots 1) ;; Disable the unused slots check</div>
-</li>
-<li class="level1"><div class="li"> (define dont-check-slots 1) ;; Disable slot number check</div>
-</li>
-<li class="level1"><div class="li"> (define action-unused-slots #\w) ;; Output an unused slots as a warning</div>
-</li>
-<li class="level1"><div class="li"> (define action-unused-slots #\e) ;; Output an unused slots as an error</div>
-</li>
-<li class="level1"><div class="li"> (define action-unused-slots #\c) ;; An unused slot is OK.</div>
-</li>
-<li class="level1"><div class="li"> (define case_insensitive 1) ;; Do all checks case insensitive</div>
-</li>
-</ul>
-
-<p>
- Il y a dâ??autres commandes avancées pour modifier la matrice DRC et le type de broche qui peut piloter un net. Voyez le fichier «·gnet-drc2.scm·» avec un éditeur de texte. Au début, vous y avez la documentation de disponible.
-</p>
-
-<p>
-Copiez les lignes ci-dessus que vous voulez dans un fichier (par exemple «·drc_rules.txt·»), une par ligne etlancez le contrôleur de drc:
-</p>
-<pre class="code">gnetlist -g drc2 -l drc_rules.txt -o MyDesign.drc MyDesign.sch</pre>
-
-<p>
-Avec cette commande, la sortie de DRC est écrite dans un ficheir «·MyDesign.drc·». Vous pouvez alors visualiser ce fichier avec un éditeur de texte et voir les avertissements et les erreurs de DRC.
-</p>
-
-</div>
-<!-- SECTION "Je veux désactiver quelque uns des contrôles de DRC du schéma. Comment faire?" [2481-4415] -->
-<h2><a name="puis-je_inclure_le_controle_de_drc_dans_un_makefile_et_stopper_lorsque_des_erreurs_ou_des_avertissements_sont_trouves" id="puis-je_inclure_le_controle_de_drc_dans_un_makefile_et_stopper_lorsque_des_erreurs_ou_des_avertissements_sont_trouves">Puis-je inclure le contrôle de DRC dans un Makefile et stopper lorsque des erreurs ou des avertissements sont trouvés?</a></h2>
-<div class="level2">
-
-<p>
-Oui. drc2 renverra une erreur sâ??il y a des erreurs ou des avertissements, donc vous pouvez ajouter ce qui suit dans votre Makefile:
-</p>
-<pre class="code">$(objects).drc : $(objects).sch
- gnetlist -g drc2 $(objects).sch -o $(objects).drc</pre>
-
-<p>
-Si vous devez simuler votre dessin, vous pouvez alors ajouter ce qui suit à votre Makefile:
-</p>
-<pre class="code">$(objects).cir : $(objects).sch $(objects).drc
- grep -v ERROR $(objects).drc >/dev/null 2>&1
- gnetlist -g spice-sdb $(objects).sch -o $(objects).cir</pre>
-
-<p>
-Sinon, utilisez lâ??exemple ci-dessus et adaptez-le à votre propre workflow.
-</p>
-
-</div>
-<!-- SECTION "Puis-je inclure le contrôle de DRC dans un Makefile et stopper lorsque des erreurs ou des avertissements sont trouvés?" [4416-5138] -->
-<h2><a name="il_y_a_quelques_avertissements_sur_mon_schema_que_je_connais._puis-je_les_ignorer_dans_la_return_value" id="il_y_a_quelques_avertissements_sur_mon_schema_que_je_connais._puis-je_les_ignorer_dans_la_return_value">Il y a quelques avertissements sur mon schéma que je connais. Puis-je les ignorer dans la return value?</a></h2>
-<div class="level2">
-
-<p>
-Utilisez lâ??option «·-O ignore-warnings-in-return-value·»:
-</p>
-<pre class="code">gnetlist -g drc2 -o - MyDesign.sch -O ignore-warnings-in-return-value</pre>
-
-<p>
-Faites attention! Vous allez rater tous les avertissements·!
-</p>
-
-</div>
-<!-- SECTION "Il y a quelques avertissements sur mon schéma que je connais. Puis-je les ignorer dans la return value?" [5139-5464] -->
-<h1><a name="gestion_d_attribut" id="gestion_d_attribut">Gestion d'attribut</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "Gestion d'attribut" [5465-5498] -->
-<h2><a name="au_secours_mon_schema_a_des_centaines_de_composants_et_c_est_penible_d_utiliser_gschem_pour_attacher_tous_mes_attributs" id="au_secours_mon_schema_a_des_centaines_de_composants_et_c_est_penible_d_utiliser_gschem_pour_attacher_tous_mes_attributs">Au secours! Mon schéma a des centaines de composants et c'est pénible d'utiliser gschem pour attacher tous mes attributs!</a></h2>
-<div class="level2">
-
-<p>
-Ici, la réponse est lâ??utilitaire de gEDA/gaf, «·gattrib·». Gattrib est un éditeur dâ??attribut pour gEDA. Il lit votre(s) fichier(s) .sch et crée une feuille de calcul montrant tous les composants, nets et broches en ligne, avec les attributs associés listés dans les colonnes. Gattrib vous permet dâ??ajouter, modifier ou effacer les attributs depuis lâ??extérieur de gschem puis de sauvegarder les fichiers .sch. Vous avez une capture dâ??écran:
-</p>
-
-<p>
-<a href="_detail/001geda_faq_attrib.html" class="media" title="geda:faq_attrib.jpg"><img src="http://geda.seul.org/wiki/_media/geda:faq_attrib.jpg?w=&h=&cache=cache"; class="media" title="faq_attrib.jpg" alt="faq_attrib.jpg" /></a>
-</p>
-
-<p>
-Notez que gattrib est la réponse actuelle du Projet gEDA à la question des symboles lourds. Ceci étant, au lieu de mettre tous les attributs (tels que les fichiers de modèle SPICE, les noms dâ??empreintes, les numéros dâ??éléments des fabricants et le reste), vous êtes encouragés à mettre cette information dans votre schéma en utilisant gattrib, où il est visible et facilement manipulable avec gattrib.
-</p>
-
-<p>
-Lors de lâ??utilisation de gattrib, assurez-vous de dâ??abord quitter gschem. Gattrib et gschem sauvegardent tous les deux le travail dans le même fichier, donc vous ne devez avoir quâ??un programme fonctionnant au même moment pour éviter les conflits. Il nâ??y a pas (encore) de mécanisme de vérouillage dans gEDA/gaf, cela reste donc de votre responsabilité.
-</p>
-
-</div>
-<!-- SECTION "Au secours! Mon schéma a des centaines de composants et c'est pénible d'utiliser gschem pour attacher tous mes attributs!" [5499-6887] -->
-<h2><a name="comment_savoir_que_nom_d_empreinte_utiliser_pour_le_placement_avec_pcb" id="comment_savoir_que_nom_d_empreinte_utiliser_pour_le_placement_avec_pcb">Comment savoir que nom d'empreinte utiliser pour le placement avec PCB?</a></h2>
-<div class="level2">
-
-<p>
-La <a href="001geda_pcb_tips.html" class="wikilink1" title="geda:pcb_tips.fr">réponse est ici</a>.
-</p>
-
-</div>
-<!-- SECTION "Comment savoir que nom d'empreinte utiliser pour le placement avec PCB?" [6888-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/001geda_faq-gnetlist.html b/docs/wiki/001geda_faq-gnetlist.html
deleted file mode 100644
index ee67599..0000000
--- a/docs/wiki/001geda_faq-gnetlist.html
+++ /dev/null
@@ -1,117 +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>geda:faq-gnetlist.fr</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-05-24T22:27:26-0400" />
-<meta name="keywords" content="geda,faq-gnetlist.fr" />
-<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/geda:faq-gnetlist.fr?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:faq-gnetlist.fr"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:faq-gnetlist.fr"; />
-<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="#problemes_avec_gnetlist_lors_de_l_installation_execution" class="toc">Problèmes avec gnetlist lors de l'installation/exécution</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#la_bom_de_gnetlist_ne_fonctionne_pas._d_ou_vient_le_probleme" class="toc">la bom de gnetlist ne fonctionne pas. D'où vient le problème?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#quelques_unes_des_commandes_de_gnetlist_debordent_la_pile._comment_je_resoud_ce_probleme" class="toc">Quelques unes des commandes de gnetlist débordent la pile. Comment je résoud ce problème?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#gnetlist_a_cree_une_netlist_qui_duplique_les_broches" class="toc">gnetlist a créé une netlist qui duplique les broches!?</a></span></div></li></ul>
-</li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="problemes_avec_gnetlist_lors_de_l_installation_execution" id="problemes_avec_gnetlist_lors_de_l_installation_execution">Problèmes avec gnetlist lors de l'installation/exécution</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "Problèmes avec gnetlist lors de l'installation/exécution" [1-73] -->
-<h2><a name="la_bom_de_gnetlist_ne_fonctionne_pas._d_ou_vient_le_probleme" id="la_bom_de_gnetlist_ne_fonctionne_pas._d_ou_vient_le_probleme">la bom de gnetlist ne fonctionne pas. D'où vient le problème?</a></h2>
-<div class="level2">
-
-<p>
-Si, lorsque vous lancez gnetlist comme ceci:
-</p>
-<pre class="code">gnetlist -g bom filename.sch</pre>
-
-<p>
-gnetlist vous sort un message dâ??erreur tel que:
-</p>
-<pre class="code">Loading schematic [filename.sch]
-ERROR: In procedure open-file:
-ERROR: No such file or directory: â??attribsâ??</pre>
-
-<p>
-alors vous avez besoin de créer un fichier appelé «·attribs·» dans le répertoire courant qui contient les attributss que vous voulez dans le fichier de bom. Un exemple de ce fichier ressemblerait à : <pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">refdes
-device
-value</font></pre>
-</p>
-
-</div>
-<!-- SECTION "la bom de gnetlist ne fonctionne pas. D'où vient le problème?" [74-654] -->
-<h2><a name="quelques_unes_des_commandes_de_gnetlist_debordent_la_pile._comment_je_resoud_ce_probleme" id="quelques_unes_des_commandes_de_gnetlist_debordent_la_pile._comment_je_resoud_ce_probleme">Quelques unes des commandes de gnetlist débordent la pile. Comment je résoud ce problème?</a></h2>
-<div class="level2">
-
-<p>
-Si vous avez un message tel que:
-</p>
-<pre class="code">ERROR: Stack overflow</pre>
-
-<p>
-lorsque vous faites passer des schémas de grande taille par une des commandes, ajoutez alors ce qui suit à <strong><code>~/.gEDA/gnetlistrc</code></strong> ou un <strong><code>gnetlistrc</code></strong> local (dans le répertoire de travail courant):
-</p>
-<pre class="code">(debug-options (list 'stack 200000))
-(eval-options (list 'stack 200000))</pre>
-
-<p>
-Si cela ne fonctionne pas, éditez alors la commande appropriée (habituellement appelée: gnet-backend_name.scm) et insérez les lignes précédentes en haut de ce fichier. Les commandes gnetlist peuvent être trouvées dans <strong><code>${prefix}/share/gEDA/scheme</code></strong>. Envoyez aussi un courriel à geda-dev rappelant aux développeurs de corriger ceci. Rappelez-vous que vous devez être inscrits sur geda-dev avant dâ??y envoyer des courriels.
-</p>
-
-</div>
-<!-- SECTION "Quelques unes des commandes de gnetlist débordent la pile. Comment je résoud ce problème?" [655-1562] -->
-<h2><a name="gnetlist_a_cree_une_netlist_qui_duplique_les_broches" id="gnetlist_a_cree_une_netlist_qui_duplique_les_broches">gnetlist a créé une netlist qui duplique les broches!?</a></h2>
-<div class="level2">
-
-<p>
-Il y a eu au moins un rapport sur le message suivant venant de PCB après avoir chargé une netlist créée par gnetlist:
-</p>
-<pre class="code">28: Error! Element R117 pin 2 appears multiple times in the netlist file.
-29: Error! Element C167 pin 2 appears multiple times in the netlist file.</pre>
-
-<p>
-Ce qui sâ??est produit est que gnetlist (libgeda en fait) a créé deux nets au lieu dâ??un seul. Ceci se produit lorsque vous dessinez deux nets lâ??un sur lâ??autre avec une broche connectant une intersection de deux nets se chevauchants. Notez que les nets chevauchés ne sont pas connectés ensemble. Un schéma pour la démonstration ressemble à ceci:
-</p>
-
-<p>
-<a href="_detail/001geda_ambiguous1.html" class="media" title="geda:ambiguous1.png"><img src="http://geda.seul.org/wiki/_media/geda:ambiguous1.png?w=&h=&cache=cache"; class="media" alt="" /></a>
-</p>
-
-<p>
-Les développeurs débattent pour savoir si câ??est un bogue ou non de gnetlist mais jusquâ??à maintenant, assurez-vous de vos connexions de nets, spécialement celles qui impliquent des broches connectant des milieu de nets, sont correctement dessinées. Vous avez ici la manière dont la connexion ci-dessus devrait être correctement dessinée pour que netlist fasse son travail proprement:
-</p>
-
-<p>
-<a href="_detail/001geda_ambiguous1_fixed.html" class="media" title="geda:ambiguous1_fixed.png"><img src="http://geda.seul.org/wiki/_media/geda:ambiguous1_fixed.png?w=&h=&cache=cache"; class="media" alt="" /></a>
-</p>
-
-</div>
-<!-- SECTION "gnetlist a créé une netlist qui duplique les broches!?" [1563-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/001geda_faq-gsch2pcb.html b/docs/wiki/001geda_faq-gsch2pcb.html
deleted file mode 100644
index 36b9b46..0000000
--- a/docs/wiki/001geda_faq-gsch2pcb.html
+++ /dev/null
@@ -1,91 +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>geda:faq-gsch2pcb.fr</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-06-27T07:33:33-0400" />
-<meta name="keywords" content="geda,faq-gsch2pcb.fr" />
-<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/geda:faq-gsch2pcb.fr?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:faq-gsch2pcb.fr"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:faq-gsch2pcb.fr"; />
-<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="#gsch2pcb" class="toc">gsch2pcb</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#ou_est_le_tutoriel_gsch2pcb" class="toc">Où est le tutoriel gsch2pcb?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#ou_puis-je_telecharger_gsch2pcb" class="toc">Où puis-je télécharger gsch2pcb?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#gsch2pcb_ne_peut_pas_trouver_quelques_uns_de_mes_empreintes_ou_genere_une_erreur._comment_puis-je_diagnostiquer_mon_probleme" class="toc">gsch2pcb ne peut pas trouver quelques uns de mes empreintes ou génère une erreur. Comment puis-je diagnostiquer mon problème?</a></span></div></li></ul>
-</li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="gsch2pcb" id="gsch2pcb">gsch2pcb</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "gsch2pcb" [1-24] -->
-<h2><a name="ou_est_le_tutoriel_gsch2pcb" id="ou_est_le_tutoriel_gsch2pcb">Où est le tutoriel gsch2pcb?</a></h2>
-<div class="level2">
-
-<p>
- Actuellement, la meilleure information à ce propos est dans le <a href="http://geda.seul.org/wiki/geda:gsch2pcb_tutorial"; class="wikilink1" title="geda:gsch2pcb_tutorial">tutorial</a> de Bill Wilson. <br/>
- <span class="hilited">Cette page grossira plus tard pour contenir les réponses aux <acronym title="Frequently Asked Questions">FAQ</acronym> postées sur la liste des geda-user.</span>
-</p>
-
-<p>
-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>
-<!-- SECTION "Où est le tutoriel gsch2pcb?" [25-436] -->
-<h2><a name="ou_puis-je_telecharger_gsch2pcb" id="ou_puis-je_telecharger_gsch2pcb">Où puis-je télécharger gsch2pcb?</a></h2>
-<div class="level2">
-
-<p>
-gsch2pcb est une part de gEDA/gaf, dans les utils. Il est normalement installé par défaut (parmi les autres) si vous installez gEDA/gaf complètement. Si vous ne lâ??avez pas installé sur votre machine vous pouvez soit télécharger le tarball utils depuis:
-</p>
-<ul>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/download.html"; class="urlextern" title="http://geda.seul.org/download.html"; rel="nofollow">http://geda.seul.org/download.html</a></div>
-</li>
-</ul>
-
-<p>
- ou le prendre directement depuis le <acronym title="Concurrent Versions System">CVS</acronym> sur:
-</p>
-<ul>
-<li class="level1"><div class="li"> <a href="http://cvs.seul.org/viewcvs/viewcvs.cgi/eda/geda/gaf/utils/src/"; class="urlextern" title="http://cvs.seul.org/viewcvs/viewcvs.cgi/eda/geda/gaf/utils/src/"; rel="nofollow">http://cvs.seul.org/viewcvs/viewcvs.cgi/eda/geda/gaf/utils/src/</a></div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Où puis-je télécharger gsch2pcb?" [437-905] -->
-<h2><a name="gsch2pcb_ne_peut_pas_trouver_quelques_uns_de_mes_empreintes_ou_genere_une_erreur._comment_puis-je_diagnostiquer_mon_probleme" id="gsch2pcb_ne_peut_pas_trouver_quelques_uns_de_mes_empreintes_ou_genere_une_erreur._comment_puis-je_diagnostiquer_mon_probleme">gsch2pcb ne peut pas trouver quelques uns de mes empreintes ou génère une erreur. Comment puis-je diagnostiquer mon problème?</a></h2>
-<div class="level2">
-
-<p>
-Tentez de lancer gsch2pcb en mode bavard double: â??gsch2pcb -v -vâ??. Cela produira beaucoup de choses vous indiquant où gsch2pcb cherche lorsquâ??il tente de trouver les empreintes. Il vous indiquera aussi où il trouve les empreintes en cours dâ??utilisation.
-</p>
-
-</div>
-<!-- SECTION "gsch2pcb ne peut pas trouver quelques uns de mes empreintes ou génère une erreur. Comment puis-je diagnostiquer mon problème?" [906-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/001geda_faq-gschem.html b/docs/wiki/001geda_faq-gschem.html
deleted file mode 100644
index 3e61c60..0000000
--- a/docs/wiki/001geda_faq-gschem.html
+++ /dev/null
@@ -1,635 +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>geda:faq-gschem.fr</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-05-24T22:27:26-0400" />
-<meta name="keywords" content="geda,faq-gschem.fr" />
-<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/geda:faq-gschem.fr?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:faq-gschem.fr"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:faq-gschem.fr"; />
-<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="#usage_de_gschem" class="toc">Usage de Gschem</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#comment_je_deplace_un_composant" class="toc">Comment je déplace un composant?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#comment_je_change_la_taille_du_texte_sur_un_symbole" class="toc">Comment je change la taille du texte sur un symbole?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#comment_deverouiller_un_composant" class="toc">Comment dévérouiller un composant</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#comment_refdes_peut-il_etre_automatiquement_numerote_lorsque_je_dessine_un_schema" class="toc">Comment refdes peut-il être automatiquement numéroté lorsque je dessine un schéma?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#qu_est-ce_qu_un_bus_et_comment_l_utiliser" class="toc">Qu'est-ce qu'un bus et comment l'utiliser?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#que_sont_les_liaisons_de_touches_dans_gschem" class="toc">Que sont les Liaisons de Touches dans gschem?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#quelles_sont_les_liaisons_avec_la_souris_dans_gschem" class="toc">Quelles sont les liaisons avec la souris dans gschem?</a></span></div></li>
-</ul>
-</li>
-<li class="level1"><div class="li"><span class="li"><a href="#symboles_gschem" class="toc">Symboles gschem</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#quel_est_l_objet_de_cette_polemique_entre_les_symboles_lourds_et_legers" class="toc">Quel est l'objet de cette polémique entre les symboles lourds et légers?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#j_utilise_un_symbole_exterieur_a_la_bibliotheque._comment_se_fait-il_qu_il_ne_soit_pas_aligne_sur_la_grille" class="toc">J'utilise un symbole extérieur à la bibliothèque. Comment se fait-il qu'il ne soit pas aligné sur la grille?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#existe-t-il_un_symbole_explicitement_non_connecte_que_je_pourrais_devrais_placer_dans_le_schema_pour_empecher_gnetlist_de_penser_que_j_ai_oublie_une_connexion" class="toc">Existe-t-il un symbole explicitement « non connecté » que je pourrais/devrais placer dans le schéma pour empêcher gnetlist de penser que j'ai oublié une connexion?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#comment_placer_un_un_attribut_de_symbole_invisible_dans_un_schema" class="toc">Comment placer un un attribut de symbole invisible dans un schéma?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#que_dois-je_faire_a_propos_des_broches_d_alimentation_sur_mon_symboleles_rendre_visible_explicites_ou_invisibles_implicites" class="toc">Que dois-je faire à propos des broches d'alimentation sur mon symbole: Les rendre visible (explicites) ou invisibles (implicites)?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#existe-t-il_une_specification_ou_un_manuel_pour_creer_les_symboles_gschem_ou_est-il" class="toc">Existe-t-il une spécification ou un manuel pour créer les symboles gschem? Où est-il?</a></span></div></li>
-</ul>
-</li>
-<li class="level1"><div class="li"><span class="li"><a href="#configuration_personnalisation_de_gschem" class="toc">Configuration/personnalisation de gschem</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#comment_changer_la_taille_par_defaut_d_un_texte_flottant" class="toc">Comment changer la taille par défaut d'un texte flottant?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#comment_je_peux_avoir_une_couleur_fond_differente" class="toc">Comment je peux avoir une couleur fond différente?</a></span></div></li>
-</ul>
-</li>
-<li class="level1"><div class="li"><span class="li"><a href="#impression_sortie" class="toc">Impression/Sortie</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#comment_imprimer_les_schemas_depuis_le_ligne_de_commande" class="toc">Comment imprimer les schémas depuis le ligne de commande?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#comment_je_peux_sortie_le_postscript_png_en_couleurs" class="toc">Comment je peux sortie le postscript/PNG en couleurs?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#comment_je_peux_avoir_une_sortie_postscript_png_en_noir_et_blanc" class="toc">Comment je peux avoir une sortie postscript/PNG en noir et blanc?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#comment_j_insere_des_schemas_dans_mon_document_latex" class="toc">Comment j'insère des schémas dans mon document LaTex?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#comment_je_scinde_un_fichier_postscript_en_plusieurs_pages" class="toc">Comment je scinde un fichier postscript en plusieurs pages?</a></span></div></li>
-</ul>
-</li>
-<li class="level1"><div class="li"><span class="li"><a href="#problemes_d_installation_d_execution_de_gschem" class="toc">Problèmes d'installation/d'exécution de gschem</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#gschem_segfaults_lorsque_j_efface_des_composants_sur_fc5_et_sur_d_autres_distributions_linux_existe-t-il_une_amelioration" class="toc">gschem segfaults lorsque j'efface des composants sur FC5 (et sur d'autres distributions Linux)! Existe-t-il une amélioration?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#apres_l_installation_gschem_ne_fonctionne_pas_que_ce_qui_a_pu_aller_mal" class="toc">Après l'installation, gschem ne fonctionne pas!? Que ce qui a pu aller mal?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#ajouter_des_composants_ne_proposent_aucun_symboles_que_puis-je_y_faire" class="toc">"Ajouter des Composants" ne proposent aucun symboles! Que puis-je y faire?</a></span></div></li></ul>
-</li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="usage_de_gschem" id="usage_de_gschem">Usage de Gschem</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "Usage de Gschem" [1-31] -->
-<h2><a name="comment_je_deplace_un_composant" id="comment_je_deplace_un_composant">Comment je déplace un composant?</a></h2>
-<div class="level2">
-
-<p>
-Ce nâ??est plus un problème·; déplacer un composant peut être réalisé en utilisant le bouton gauche de la souris – la méthode haituelle des utilisateurs de Windows. pour les vrsions égales ou plus récentes que 20060824, faites cecido this:
-</p>
-<ol>
-<li class="level1"><div class="li"> Sélectionnez le composant en cliquant dessus avec le bouton gauche de la souris. Le composant sera mis en valeur.</div>
-</li>
-<li class="level1"><div class="li"> Tirez le composant (en utilisant le bouton gauche de la souris) pour le placer où vous le voulez.</div>
-</li>
-</ol>
-
-<p>
- Câ??est probablement ce que vous avez lâ??habitude de faire.
-</p>
-
-<p>
-Pour les personnes avec dâ??anciennes versions de gschem, vous avez ici trois voies pour déplacer facilement les composants avec gschem:
-</p>
-
-<p>
-Un:
-</p>
-<ol>
-<li class="level1"><div class="li"> Attrapez le composants avec le bouton de souris du milieu. Le composant suivra le curseur où vous lâ??emmenez.</div>
-</li>
-<li class="level1"><div class="li"> Pour placer le composant, relachez le bouton du milieu de la souris. Le composant restera où vous lâ??avez placé.</div>
-</li>
-</ol>
-
-<p>
-Deux:
-</p>
-<ol>
-<li class="level1"><div class="li"> Sélectionnez le composant en cliquant dessus avec le bouton gauche de la souris. Le composant sera mis en valeur.</div>
-</li>
-<li class="level1"><div class="li"> Appuyez sur la touche « M » du clavier. Le composant suivra le curseur où vous lâ??emmenez.</div>
-</li>
-<li class="level1"><div class="li"> Pour placer le composant, cliquez le bouton gauche de la souris. Le composant restera où vous lâ??avez placé.</div>
-</li>
-</ol>
-
-<p>
-Trois:
-</p>
-<ol>
-<li class="level1"><div class="li"> Pour placer le composant, cliquez sur le bouton gauche de souris. Le composant restera là où vous lâ??avez placé.</div>
-</li>
-</ol>
-
-</div>
-<!-- SECTION "Comment je déplace un composant?" [32-1447] -->
-<h2><a name="comment_je_change_la_taille_du_texte_sur_un_symbole" id="comment_je_change_la_taille_du_texte_sur_un_symbole">Comment je change la taille du texte sur un symbole?</a></h2>
-<div class="level2">
-<ol>
-<li class="level1"><div class="li"> Sélectionnez le symbole.</div>
-</li>
-<li class="level1"><div class="li"> Clic droit â?? down symbol (ou faites Hierarchy â?? down symbol). Ceci vous mène à lâ??éditeur de symbole.</div>
-</li>
-<li class="level1"><div class="li"> Sélectionnez le pinnumber que vous voulez changer.</div>
-</li>
-<li class="level1"><div class="li"> Faites Edit â?? Edit Text (ou tapez le raccourci clavier « ex »).</div>
-</li>
-<li class="level1"><div class="li"> Changez la taille de police dans la boîte déroulante.</div>
-</li>
-<li class="level1"><div class="li"> Recommencez pour tous les éléments de textes désirés.</div>
-</li>
-<li class="level1"><div class="li"> Fichier â?? sauvegarde</div>
-</li>
-<li class="level1"><div class="li"> Clic droit â?? up (ou Hierarchy â?? Up). Vous êtes maintenant retourné à lâ??éditeur de schéma.</div>
-</li>
-<li class="level1"><div class="li"> Avez le symbole encore sélectionné, faites Edit â?? Update component (ou utilisez le raccourci clavier « ep »). Si cela ne fonctionne pas, effacez simplement le symbole et rechargez-le.</div>
-</li>
-</ol>
-
-<p>
- Plus généralement, vous pouvez utiliser cette procédure pour éditer nâ??importe quoi sur un symbole. (Substituez « Edit Text » pour votre édition souhaitée, bien sûr.)
-</p>
-
-</div>
-<!-- SECTION "Comment je change la taille du texte sur un symbole?" [1448-2405] -->
-<h2><a name="comment_deverouiller_un_composant" id="comment_deverouiller_un_composant">Comment dévérouiller un composant</a></h2>
-<div class="level2">
-
-<p>
-Lorsquâ??un composant est véroullé, il est insélectionnable en utilisant le bouton milieu de la souris mais il est néanmoins sélectionnable en utilisant une sélection de fenêtre. Pour une sélection de fenêtre sur un composant, cliquez et maintenez avec le bouton gauche de souris et tirez pour créer une région rectangulaire contenant le composant devant être dévérouillé. Exécutez la commande <strong><em>Edit</em></strong> <strong>â??</strong> <strong><em>unLock</em></strong> pour dévérouiller le composant.
-</p>
-
-</div>
-<!-- SECTION "Comment dévérouiller un composant" [2406-2932] -->
-<h2><a name="comment_refdes_peut-il_etre_automatiquement_numerote_lorsque_je_dessine_un_schema" id="comment_refdes_peut-il_etre_automatiquement_numerote_lorsque_je_dessine_un_schema">Comment refdes peut-il être automatiquement numéroté lorsque je dessine un schéma?</a></h2>
-<div class="level2">
-
-<p>
-Ã?ditez le fichier system-gschemrc ou placez ce qui suit dans le fichier gschemrc (soit <strong><code>~/.gEDA/gschemrc</code></strong> ou un fichier <strong><code>gschemrc</code></strong> dans le répertoire local dâ??où vous invoquez gschem):
-</p>
-<pre class="code">
-(load (string-append gedadata "/scheme/auto-uref.scm")) ; load the autonumbering script
-(add-hook! add-component-hook auto-uref) ; autonumber when adding a component
-(add-hook! copy-component-hook auto-uref) ; autonumber when copying a component
-</pre>
-
-<p>
-Veuillez substituer $YOUR_INSTALL_PATH par le chemin dâ??installation de geda.
-</p>
-
-</div>
-<!-- SECTION "Comment refdes peut-il être automatiquement numéroté lorsque je dessine un schéma?" [2933-3581] -->
-<h2><a name="qu_est-ce_qu_un_bus_et_comment_l_utiliser" id="qu_est-ce_qu_un_bus_et_comment_l_utiliser">Qu'est-ce qu'un bus et comment l'utiliser?</a></h2>
-<div class="level2">
-
-<p>
- Un bus est purement décoratif. Le netlister lâ??ignore. Lâ??attribut netname= ne fonctionne pas pour connecter les points ensemble â?? câ??est ce que gnetlist lit et transforme dans votre netlist. Il nâ??est pas possible de connecter une ligne discrète ou « accrochée à un bus » car, encore une fois, le bus est plus une entité graphique.
-</p>
-
-<p>
-Quelques utilisateurs ont trouvé utile dâ??organiser leurs réseaux en incorporant un nom de bus dans le nom de net. Par exemple, « net=busA:1 » peut être ajouté à chaque busripper pour aider le tri des nets.
-</p>
-
-</div>
-<!-- SECTION "Qu'est-ce qu'un bus et comment l'utiliser?" [3582-4190] -->
-<h2><a name="que_sont_les_liaisons_de_touches_dans_gschem" id="que_sont_les_liaisons_de_touches_dans_gschem">Que sont les Liaisons de Touches dans gschem?</a></h2>
-<div class="level2">
-
-</div>
-<!-- SECTION "Que sont les Liaisons de Touches dans gschem?" [4191-4249] -->
-<h2><a name="quelles_sont_les_liaisons_avec_la_souris_dans_gschem" id="quelles_sont_les_liaisons_avec_la_souris_dans_gschem">Quelles sont les liaisons avec la souris dans gschem?</a></h2>
-<div class="level2">
-
-<p>
-Par défaut, vous avez:
-</p>
-<ul>
-<li class="level1"><div class="li"> Le bouton gauche de souris est utilisé pour prendre et dessiner</div>
-</li>
-<li class="level1"><div class="li"> Le bouton milieu de souris est soit pour déplacer un objet (maintenez le bouton milieu sur un objet et déplacez la souris), soit pour copier un objet (la touche ALT maintenue lors dâ??une pression sur le bouton milieu sur un objet et déplacez la souris).</div>
-</li>
-<li class="level1"><div class="li"> Le bouton droit de souris est un menu déroulant.</div>
-</li>
-</ul>
-
-<p>
- Vous pouvez changer le bouton milieu en ajoutant ce qui suit à un fichier gschemrc:
-</p>
-<pre class="code">(middle-button "action") ;default binding, move or copy an object</pre>
-
-<p>
-ou:
-</p>
-<pre class="code">(middle-button "stroke") ;draw mouse gestures/strokes (must install libstroke to enable</pre>
-
-<p>
-ou:
-</p>
-<pre class="code">(middle-button "repeat") ;repeat the last command executed</pre>
-
-<p>
-Vous pouvez changer le bouton droit en ajoutant ce qui suit dans un fichier gschemrc:
-</p>
-<pre class="code">(third-button "popup") ;default binding, show a popup menu</pre>
-
-<p>
-ou:
-</p>
-<pre class="code">(third-button "mousepan") ;use the mouse to pan around the schematic</pre>
-
-<p>
-Pour plus informations sur ces options, veuillez aller voir le fichier <strong><code>${install_prefix}/share/gEDA/system-gschemrc</code></strong>.
-</p>
-
-</div>
-<!-- SECTION "Quelles sont les liaisons avec la souris dans gschem?" [4250-5454] -->
-<h1><a name="symboles_gschem" id="symboles_gschem">Symboles gschem</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "Symboles gschem" [5455-5485] -->
-<h2><a name="quel_est_l_objet_de_cette_polemique_entre_les_symboles_lourds_et_legers" id="quel_est_l_objet_de_cette_polemique_entre_les_symboles_lourds_et_legers">Quel est l'objet de cette polémique entre les symboles lourds et légers?</a></h2>
-<div class="level2">
-
-<p>
-Cette nomenclature est apparue dâ??une discussion qui apparaît fréquement sur les listes de diffusion geda-user et geda-dev. Un symbole léger contient peu dâ??attributs intégrés dans le symbole lui-même. Il nécessite que lâ??utilisateur attache presque tous les attributs au niveau du schéma (i.e. en utilisant soit gschem, soit gattrib). Un symbole lourd contient plusieurs attributs (tels quâ??une empreinte de boîtier, des noms de modèle SPICE, etc.) intégrés dans le fichier symbole lui-même. Un symbole lourd nécessite donc des attachements dâ??attributs très légers au niveau du schéma â?? vous nâ??avez quâ??à le placer et câ??est fait.
-</p>
-
-<p>
-Le débat entre les adversaires des symboles lourds et légers est très détaillé et pointu. En caricaturant, les avocats des symboles lourds croient que cela fournit une meilleure intégration entre gschem et PCB avec lâ??importance des attrituts de placement (tels que <a href="http://geda.seul.org/wiki/geda:pcb_tips#i_want_to_use_pcb_to_do_layout._how_do_i_know_what_value_to_use_for_the_footprint_attribute"; class="wikilink1" title="geda:pcb_tips">footprint name</a>) déjà créés dans le symbole. Ceci est considéré comme une bonne chose pour les nouveaux utilisateurs (noobs) qui veulent simplement concevoir une simple carte et nâ??apprécient pas ou nâ??ont que faire des zillions de variations quâ??une simple résistance peut avoir (i.e. empreintes différentes, TCR, précision, composition physique, etc). Les avocats des symboles légers préfère traiter les attributs au niveau du schéma car ils pensent que câ??est plus flexible. Ils font rapidement remarquer que une bibliothèque de symboles lourds sâ??accroîtra rapidement en des milliers de morceaux avec des noms grotesquement longs en tentant de distinguer entre les différentes variations dâ??un composant. Ils soulignent aussi que lâ??utilitaire « gattrib » est lâ??outil préféré pour traiter les attributs au niveau du schéma (i.e. dans le fichier .sch).
-</p>
-
-<p>
-GEDA/gaf, configuré par défaut, utilise des symboles légers, bien quâ??il puisse être configuré pour utiliser des symboles lourds. Pour plus dâ??informations, vous pouvez lire ces dicussions sur la liste de diffusion geda-user:
-</p>
-
-<p>
-<a href="http://archives.seul.org/geda/user/Jun-2005/msg00001.html"; class="urlextern" title="http://archives.seul.org/geda/user/Jun-2005/msg00001.html"; rel="nofollow">http://archives.seul.org/geda/user/Jun-2005/msg00001.html</a> <a href="http://archives.seul.org/geda/dev/Oct-2005/msg00043.html"; class="urlextern" title="http://archives.seul.org/geda/dev/Oct-2005/msg00043.html"; rel="nofollow">http://archives.seul.org/geda/dev/Oct-2005/msg00043.html</a>
-</p>
-
-</div>
-<!-- SECTION "Quel est l'objet de cette polémique entre les symboles lourds et légers?" [5486-7826] -->
-<h2><a name="j_utilise_un_symbole_exterieur_a_la_bibliotheque._comment_se_fait-il_qu_il_ne_soit_pas_aligne_sur_la_grille" id="j_utilise_un_symbole_exterieur_a_la_bibliotheque._comment_se_fait-il_qu_il_ne_soit_pas_aligne_sur_la_grille">J'utilise un symbole extérieur à la bibliothèque. Comment se fait-il qu'il ne soit pas aligné sur la grille?</a></h2>
-<div class="level2">
-
-<p>
-Les symboles dans la bibliothèque, comme ceux disponibles sur le site web <a href="http://www.gedasymbols.org/"; class="urlextern" title="http://www.gedasymbols.org"; rel="nofollow"> gedasymbols </a> sont fournis par des utilisateurs comme vous. Quelques personnes utilisent des initialisations de grille différentes des autres (i.e. 50mil vs. 100mil). Si vous découvrez un symbole qui semble être hors de la grille, tentez de réduire votre espacement de grille, déplacez le symbole de telle manière quâ??il sâ??adapte à « votre » propre grille, puis revenez à votre grille initiale.
-</p>
-
-<p>
-Oui, les docs gEDA suggèrent que vous utilisiez un espacement de grille de 100mil. Mais tout le monde aime faire les choses à sa propre manière et il nâ??existe pas de diktat pour pour imposer les règles sur les symboles rendus disponibles. Vous devez donc être au courant de cette possibilité.
-</p>
-
-</div>
-<!-- SECTION "J'utilise un symbole extérieur à la bibliothèque. Comment se fait-il qu'il ne soit pas aligné sur la grille?" [7827-8765] -->
-<h2><a name="existe-t-il_un_symbole_explicitement_non_connecte_que_je_pourrais_devrais_placer_dans_le_schema_pour_empecher_gnetlist_de_penser_que_j_ai_oublie_une_connexion" id="existe-t-il_un_symbole_explicitement_non_connecte_que_je_pourrais_devrais_placer_dans_le_schema_pour_empecher_gnetlist_de_penser_que_j_ai_oublie_une_connexion">Existe-t-il un symbole explicitement « non connecté » que je pourrais/devrais placer dans le schéma pour empêcher gnetlist de penser que j'ai oublié une connexion?</a></h2>
-<div class="level2">
-
-<p>
-Réponse: misc â?? nc-left, nc-right, nc-top, nc-bottom.
-</p>
-
-<p>
-Attention: occassionnellement, cela peut créer une liaison appelée « no_connect » (ou « NC?? ») qui peut mener à des broches connectées ensembles dans gnetlist â?? ce que vous _ne souhaitez probablement pas_.
-</p>
-
-<p>
-Si vous voulez un symbole graphiquement complet (sans connexions électriques), ajoutez un attribut â??graphical=1â??. Le netlister ignorera entièrement ces symboles.
-</p>
-
-</div>
-<!-- SECTION "Existe-t-il un symbole explicitement « non connecté » que je pourrais/devrais placer dans le schéma pour empêcher gnetlist de penser que j'ai oublié une connexion?" [8766-9388] -->
-<h2><a name="comment_placer_un_un_attribut_de_symbole_invisible_dans_un_schema" id="comment_placer_un_un_attribut_de_symbole_invisible_dans_un_schema">Comment placer un un attribut de symbole invisible dans un schéma?</a></h2>
-<div class="level2">
-
-<p>
-La plupart des symboles dâ??un symbole ne sont pas placés sur le schéma à moins quâ??ils ne soient visibles. Pour afficher les attributs de symboles invisibles, cherchez les mots clés suivants dans le fichier system-gschemrc:
-</p>
-<pre class="code">(attribute-promotion â??enabledâ??);
-(promote-invisible â??disabledâ??) ; â?? This one
-(keep-invisible â??enabledâ??)</pre>
-
-<p>
-Ajoutez à votre fichier gschemrc:
-</p>
-<pre class="code">(promote-invisible â??enabledâ??)</pre>
-
-<p>
-et vous verrez tous les attributs. Le mot « keep-invisible » gardera caché ceux des attributs qui sont cachés dans le fichier symbole.
-</p>
-
-</div>
-<!-- SECTION "Comment placer un un attribut de symbole invisible dans un schéma?" [9389-10049] -->
-<h2><a name="que_dois-je_faire_a_propos_des_broches_d_alimentation_sur_mon_symboleles_rendre_visible_explicites_ou_invisibles_implicites" id="que_dois-je_faire_a_propos_des_broches_d_alimentation_sur_mon_symboleles_rendre_visible_explicites_ou_invisibles_implicites">Que dois-je faire à propos des broches d'alimentation sur mon symbole: Les rendre visible (explicites) ou invisibles (implicites)?</a></h2>
-<div class="level2">
-
-<p>
-Dans le passé, les circuits numériques cachaient souvent leurs broches dâ??alimentation et en utilisant un attribut à lâ??intérieur du symbole. La pensée moderne est que câ??est une mauvaise pratique bien que les guerres de religions font encore occasionnellement rage à propos de ce sujet).
-</p>
-
-<p>
-Cela reste marginalement vrai pour les vieux circuits logiques dâ??avoir toutes des broches dâ??alimentation et de GND, en 5V TTL, cachées. Si vous nâ??avez que du +5V sur votre carte, cacher alors les broches dâ??alimentation +5V peut simplifier quelque peu votre schéma. Néanmoins, peut de concepteur dessinent de tels circuits de nos jours; 5V TTL (et 5V CMOS) sont devenues rapidement des technologies antiques.
-</p>
-
-<p>
-Il a toujours été inacceptable de cacher les broches dâ??alimentation sur les circuits analogiques. Dâ??abord, lâ??analogique a souvent de multiples connexions dâ??alimentation (VCC, VEE) qui ont explicitement besoin dâ??être dessinées. Ensuite, une bonne pratique de conception est de placer des capacités de découplage sur chaquet et toutes les broches dâ??alimentations. Quelques uns placent aussi une inductance en série avec lâ??alimentation. Comme ils doivent être insérés dans le schéma, cela est réalisé plus facilement en les attachant explicitement à une broche dâ??alimentation. Câ??est la raison pour laquelle on ne dedrait jamais utiliser des broches dâ??alimentaion cachées pour les symboles analogiques.
-</p>
-
-<p>
-Les nouveaux circuits logiques utilisent souvent de multiples alimentations pour différentes sections logiques (OVDD, DVDD, etc). Il est aussi habituel dâ??avoir plusieurs familles logiques sur une seule carte (5V, 3.3V, etc.). Câ??est la raison pour laquelle est est mieux de placer et de câbler explicitement les broches dâ??alimentation sur le symbole. Les broches dâ??alimentation cachées sont un réservoir de désastre car vous pouvez facilement mal connecter un composant 5V sur un réseau 3.3V, par exemple.
-</p>
-
-<p>
-Pour paraphraser Nancy Reagan: Dites simplement «·non·» aux broches dâ??alimentation.
-</p>
-
-<p>
-Ceci étant dit, il peut encore être utile de détacher les broches dâ??alimentation de la partie fonctionnelle du du symbole. Pour ce faire, définissez un symbole dâ??alimentation séparé et donnez-lui le même <a href="http://geda.seul.org/wiki/geda:glossary"; class="wikilink1" title="geda:glossary">refdes</a> comme une partie fonctionnelle. Lancer gsch2pcb traitera la séparation correctement comme un seul composant. Comme ni gschem, ni gsch2pcb ne savent explicitement que le composant nâ??est complet quâ??avec les deux symboles définis, vous aurez donc à le contrôler vous-même. Avec cette méthode, vous pouvez dessiner toutes les alimentation dans un coin du schéma où elles nâ??interfèrent pas avec les nets de signaux. Dans plusieurs cas, câ??est plus avantageux avec les circuits analogiques.
-</p>
-
-</div>
-<!-- SECTION "Que dois-je faire à propos des broches d'alimentation sur mon symbole: Les rendre visible (explicites) ou invisibles (implicites)?" [10050-12944] -->
-<h2><a name="existe-t-il_une_specification_ou_un_manuel_pour_creer_les_symboles_gschem_ou_est-il" id="existe-t-il_une_specification_ou_un_manuel_pour_creer_les_symboles_gschem_ou_est-il">Existe-t-il une spécification ou un manuel pour créer les symboles gschem? Où est-il?</a></h2>
-<div class="level2">
-
-<p>
-Oui. Câ??est le <a href="001geda_scg.html" class="wikilink1" title="geda:scg.fr">Guide de Création de Symbole</a>.
-</p>
-
-</div>
-<!-- SECTION "Existe-t-il une spécification ou un manuel pour créer les symboles gschem? Où est-il?" [12945-13107] -->
-<h1><a name="configuration_personnalisation_de_gschem" id="configuration_personnalisation_de_gschem">Configuration/personnalisation de gschem</a></h1>
-<div class="level1">
-
-<p>
-gschem est configurable de plusieurs manières qui peuvent être décrites ici. Jetez un oeil sur «·system-gschemrc·» pour des suggestions sur ce qui peut être fait dâ??autre.
-</p>
-
-</div>
-<!-- SECTION "Configuration/personnalisation de gschem" [13108-13342] -->
-<h2><a name="comment_changer_la_taille_par_defaut_d_un_texte_flottant" id="comment_changer_la_taille_par_defaut_d_un_texte_flottant">Comment changer la taille par défaut d'un texte flottant?</a></h2>
-<div class="level2">
-
-<p>
-Placez
-</p>
-<pre class="code">(text-size 10)</pre>
-
-<p>
- dans votre gschemrc et replacez «·10·» avec votre taille favorite.
-</p>
-
-</div>
-<!-- SECTION "Comment changer la taille par défaut d'un texte flottant?" [13343-13521] -->
-<h2><a name="comment_je_peux_avoir_une_couleur_fond_differente" id="comment_je_peux_avoir_une_couleur_fond_differente">Comment je peux avoir une couleur fond différente?</a></h2>
-<div class="level2">
-
-<p>
- �ditez le fichier system-gschemrc et au début du fichier, vous trouvezrez des lignes comme:
-</p>
-<pre class="code">;
-; Start of color section
-;
-; Load up a color scheme has a light (almost white) background
-; Comment out the first line and comment in the second line for a
-; dark (black) background. The dark background is the original look.
-;
-(load (string-append gedadatarc "/gschem-darkbg")) ; dark background
-;(load (string-append gedadatarc "/gschem-lightbg")) ; light background</pre>
-
-<p>
-Commentez la ligne <strong><code>darkbg</code></strong> (avec un ;) et décommentez la ligne <strong><code>lightbg</code></strong>. Cela vous donnera une couleur de fond blanche au lieu de noir. Il ajuste aussi toutes les autres couleurs pour être compatibles avec un fond lumineux.
-</p>
-
-<p>
-Si vous voulez plus de contrôle sur les couleurs, veuillez éditer <strong><code>${prefix}/share/gEDA/gschem-darkbg</code></strong> ou <strong><code>${prefix}/share/gEDA/gschem-lightbg</code></strong> ou créez votre propre fichier et chargez-le dans le fichier <strong><code>system-gschemrc</code></strong>.
-</p>
-
-<p>
-Un fond noir est préféré par plusieurs utilisateurs.
-</p>
-
-</div>
-<!-- SECTION "Comment je peux avoir une couleur fond différente?" [13522-14611] -->
-<h1><a name="impression_sortie" id="impression_sortie">Impression/Sortie</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "Impression/Sortie" [14612-14644] -->
-<h2><a name="comment_imprimer_les_schemas_depuis_le_ligne_de_commande" id="comment_imprimer_les_schemas_depuis_le_ligne_de_commande">Comment imprimer les schémas depuis le ligne de commande?</a></h2>
-<div class="level2">
-
-<p>
- Lancez le script <strong><code>gschem-print.scm</code></strong> créera le fichier Postscript qui est spécifié par la ligne de commande.
-</p>
-
-<p>
-La ligne de commande ci-dessous crée un fichier Postscript depuis le fichier schéma (replacez MY_SCH avec le nom de votre schéma et GEDA_SCHEME_DIR avec le nom de votre répertoire où les fichiers schémas gEDA sont installés):
-</p>
-<pre class="code">gschem -p -oMY_SCH.ps -sGEDA_SCHEME_DIR/gschem-print.scm MY_SCH.sch</pre>
-
-<p>
-Le script BASH ci-dessous, que jâ??ai nommé <strong><code>gschem-print</code></strong>, crée un fichier Postscript pour chaque fichier schéma spécifié sur la ligne de commande et place chaque fichier généré sur lâ??imprimante par défaut:
-</p>
-<pre class="code">#!/bin/bash
-
-# gschem options
-# -oPS_FILENAME output to Postscript file PS_FILENAME
-# -sSCRIPT_FILENAME run script SCRIPT_FILENAME
-# -p autoplace windows
-
-for name in $*
-do
-base=â??${name%.*}â??
-gschem -p -o$base.ps -sGEDA_SCHEME_DIR/gschem-print.scm $base.sch
-lpr -P$PRINTER $base.ps
-done</pre>
-
-</div>
-<!-- SECTION "Comment imprimer les schémas depuis le ligne de commande?" [14645-15674] -->
-<h2><a name="comment_je_peux_sortie_le_postscript_png_en_couleurs" id="comment_je_peux_sortie_le_postscript_png_en_couleurs">Comment je peux sortie le postscript/PNG en couleurs?</a></h2>
-<div class="level2">
-
-<p>
-�ditez le fichier <strong><code>system-gschemrc</code></strong> ou placez ce qui suit dans un fichier <strong><code>gschemrc</code></strong> (soit <strong><code>~/.gEDA/gschemrc</code></strong> ou un fichier <strong><code>gschemrc</code></strong> dans le répertoire local depuis où vous invoquez gschem):
-</p>
-<pre class="code">(output-color "enabled") ; for color postscript output
-(image-color "enabled") ; for color PNG output (enabled by default)</pre>
-
-<p>
-Pour contrôler la couleur de fond du fichier PS, changez la ligne suivante soit avec gschem-darkbg (pour la couleur de fond par défaut en noir) ou gschem-lightbg (pour une couleur de fond alternative):
-</p>
-<pre class="code">(output-color-background 16 "black" "null" "0 0 0" 0 0 0)</pre>
-
-<p>
-Les â??0 0 0â?? sont les composantes RGB (entre 0..1) pour la couleur de fond de la sortie du PS.
-</p>
-
-<p>
-Pour contrôler le fond de la sortie <acronym title="Portable Network Graphics">PNG</acronym>, changez la ligne suivante soit en gschem-darkbg (pour la couleur de fond par défaut en noir) ou gschem-lightbg (pour une couleur de fond alternative):
-</p>
-<pre class="code">(background-color 0 "grey94" "null" "1 1 1" 255 255 255)</pre>
-
-<p>
-Les 255 255 255 sont les composantes RGB pour la couleur de fond de lâ??image <acronym title="Portable Network Graphics">PNG</acronym>.
-</p>
-
-</div>
-<!-- SECTION "Comment je peux sortie le postscript/PNG en couleurs?" [15675-16830] -->
-<h2><a name="comment_je_peux_avoir_une_sortie_postscript_png_en_noir_et_blanc" id="comment_je_peux_avoir_une_sortie_postscript_png_en_noir_et_blanc">Comment je peux avoir une sortie postscript/PNG en noir et blanc?</a></h2>
-<div class="level2">
-
-<p>
-Pour les sorties PS en noir et blanc, placez ce qui suit dans un fichier gschemrc:
-</p>
-<pre class="code">(output-color "disabled") ; for monochrome postscript output</pre>
-
-<p>
-Pour les images <acronym title="Portable Network Graphics">PNG</acronym> en noir et blanc, placez ce qui suit dans un fichier gschemrc:
-</p>
-<pre class="code">(image-color "disabled") ; for monochromoe PNG output</pre>
-
-</div>
-<!-- SECTION "Comment je peux avoir une sortie postscript/PNG en noir et blanc?" [16831-17228] -->
-<h2><a name="comment_j_insere_des_schemas_dans_mon_document_latex" id="comment_j_insere_des_schemas_dans_mon_document_latex">Comment j'insère des schémas dans mon document LaTex?</a></h2>
-<div class="level2">
-<ol>
-<li class="level1"><div class="li"> Sortez le schéma dans un fichier. Cela sera un postscript générique (*.ps).</div>
-</li>
-<li class="level1"><div class="li"> Convertissez le fichier postscript en epsi avec lâ??outil ps2epsi. Câ??est un script de la suite ghostscript.</div>
-</li>
-<li class="level1"><div class="li"> Incluez usepackage{graphicx} dans le préambulz de votre document latex. Utilisez la commande includegraphics pour placer votre schéma.</div>
-</li>
-</ol>
-
-<p>
- Un exemple simple:
-</p>
-<pre class="code">\documentclass{article}
-\usepackage{graphicx}
-\begin{document}
- \begin{image}
- \includegraphics[width=100mm]{ModulPID.epsi}
- \end{image}
-\end{document}</pre>
-
-</div>
-<!-- SECTION "Comment j'insère des schémas dans mon document LaTex?" [17229-17819] -->
-<h2><a name="comment_je_scinde_un_fichier_postscript_en_plusieurs_pages" id="comment_je_scinde_un_fichier_postscript_en_plusieurs_pages">Comment je scinde un fichier postscript en plusieurs pages?</a></h2>
-<div class="level2">
-
-<p>
-gschem ne fournit pas cette fonctionnalité en interne; il existe néanmoins un programme appelé «·poster·» qui le réalise exactement. Il peut être téléchargé depuis soit <a href="http://www.gnu.org/directory/poster.html"; class="urlextern" title="http://www.gnu.org/directory/poster.html"; rel="nofollow">ici</a> (GNU), soit <a href="http://printing.kde.org/downloads/"; class="urlextern" title="http://printing.kde.org/downloads/"; rel="nofollow">ici</a> (KDE Print).
-</p>
-
-</div>
-<!-- SECTION "Comment je scinde un fichier postscript en plusieurs pages?" [17820-18190] -->
-<h1><a name="problemes_d_installation_d_execution_de_gschem" id="problemes_d_installation_d_execution_de_gschem">Problèmes d'installation/d'exécution de gschem</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "Problèmes d'installation/d'exécution de gschem" [18191-18254] -->
-<h2><a name="gschem_segfaults_lorsque_j_efface_des_composants_sur_fc5_et_sur_d_autres_distributions_linux_existe-t-il_une_amelioration" id="gschem_segfaults_lorsque_j_efface_des_composants_sur_fc5_et_sur_d_autres_distributions_linux_existe-t-il_une_amelioration">gschem segfaults lorsque j'efface des composants sur FC5 (et sur d'autres distributions Linux)! Existe-t-il une amélioration?</a></h2>
-<div class="level2">
-
-<p>
-Ce bogue semble être apparu pour les utilisateurs de la Fedora Core 5 (et dâ??autres distributions linux qui utilisent glib 2.10.x). Le bogue a été réglé par les développeurs et il apparaîtra dans la prochaine version de gEDA/gaf.
-</p>
-
-<p>
-A moyen terme, vous pouvez contourner ce bogue en plaçant la variable dâ??environnement G_SLICE à «·always-malloc·». Spécifiquement, avant de lancer gschem, faites ceci:
-</p>
-
-<p>
-bash:
-</p>
-<pre class="code">export G_SLICE=always-malloc</pre>
-
-<p>
-csh:
-</p>
-<pre class="code">setenv G_SLICE always-malloc</pre>
-
-</div>
-<!-- SECTION "gschem segfaults lorsque j'efface des composants sur FC5 (et sur d'autres distributions Linux)! Existe-t-il une amélioration?" [18255-18905] -->
-<h2><a name="apres_l_installation_gschem_ne_fonctionne_pas_que_ce_qui_a_pu_aller_mal" id="apres_l_installation_gschem_ne_fonctionne_pas_que_ce_qui_a_pu_aller_mal">Après l'installation, gschem ne fonctionne pas!? Que ce qui a pu aller mal?</a></h2>
-<div class="level2">
-
-<p>
- Si vous lancez gschem et que vous avez une fenêtre sans barre de menu, sans couleurs et le programme sâ??arrête lorsque vous appuyez sur une touche avec le message suivant:
-</p>
-<pre class="code">ERROR: Unbound variable: current-keymap</pre>
-
-<p>
-Ou vous avez une erreur tel que ceci:
-</p>
-<pre class="code">Gtk-CRITICAL : file gtkpixmap.c: line 97 (gtk_pixmap_new): assertion `val != NULLâ?? failed.
-Gtk-CRITICAL : file gtkpixmap.c: line 97 (gtk_pixmap_new): assertion `val != NULLâ?? failed.
-Tried to get an invalid color: 0
-Tried to get an invalid color: 7
-Tried to get an invalid color: 0
-Tried to get an invalid color: 7</pre>
-
-<p>
-alors gschem ne trouve pas de fichier rc. Il y a deux ficheirs rc nécessaires. Le premier est <strong><code>system-gschemrc</code></strong> et le second <strong><code>system-commonrc</code></strong>.
-</p>
-<ul>
-<li class="level1"><div class="li"> Le fichier rc system-gschemrc doit être installé lorsque vous installez gschem et réside typiquement dans <strong><code>${prefix}/share/gEDA/system-gschemrc</code></strong>. <strong><code>${prefix}</code></strong> est lâ??endroit où vous avez installé gschem (habituellement <strong><code>/usr</code></strong> ou <strong><code>/usr/local</code></strong> ou <strong><code>$HOME/geda</code></strong>). Ce fichier peut aussi être installé dans /etc/gEDA (câ??est le cas des paquets .debs).</div>
-</li>
-<li class="level1"><div class="li"> Le fichier rc system-commonrc devrait être installé lorsque vous installez la bibliothèque de symboles pour gEDA/gaf. Il réside dans <strong><code>${prefix}/share/gEDA/system-commonrc</code></strong>. Ce fichier peut aussi être installé dans <strong><code>/etc/gEDA</code></strong> (câ??est le cas des paquets .debs). Ce fichier nâ??est pas chargé directement par gschem. Il est chargé par un â??(load …)â?? dans le ficheir rc system-gschemrc.</div>
-</li>
-</ul>
-
-<p>
- Assurez-vous que ces fichiers soient installés. Le fichier gschem.log (qui est créé à chaque fois que vous lancez gschem) contient des informations de déboguage intéressantes qui doivent aider dans la recherche de ce qui ne va pas. Contrôlez ce fichier pour voir où gschem cherche les fichiers rc.
-</p>
-
-<p>
-Aussi, quelques anciennes versions de gEDA/gaf ont quelques bogues lorsque les fichiers rc files sont installés dans dâ??autres endroits (autres que <strong><code>${prefix}/share/gEDA</code></strong>), veuillez donc le mettre à jour vers une version plus récente.
-</p>
-
-</div>
-<!-- SECTION "Après l'installation, gschem ne fonctionne pas!? Que ce qui a pu aller mal?" [18906-21095] -->
-<h2><a name="ajouter_des_composants_ne_proposent_aucun_symboles_que_puis-je_y_faire" id="ajouter_des_composants_ne_proposent_aucun_symboles_que_puis-je_y_faire">"Ajouter des Composants" ne proposent aucun symboles! Que puis-je y faire?</a></h2>
-<div class="level2">
-
-<p>
- Assurez-vous quâ??au moins un de vos fichiers de config contient un chemin valide vers une bibliothèque de symbole. Au démarrage, gschem contrôle les fichiers de de config suivants (sur un système Debian):
-</p>
-<ol>
-<li class="level1"><div class="li"> fichier gafrc système: <code>/etc/gEDA/system-gafrc</code></div>
-</li>
-<li class="level1"><div class="li"> fichier gafrc utilisateur: <code>~/.gEDA/gafrc</code></div>
-</li>
-<li class="level1"><div class="li"> fichier gafrc local: <code>$PWD/gafrc</code></div>
-</li>
-<li class="level1"><div class="li"> fichier gschemrc système: <code>/etc/gEDA/system-gschemrc</code></div>
-</li>
-<li class="level1"><div class="li"> fichier gschemrc utilisateur: <code>~/.gEDA/gschemrc</code></div>
-</li>
-<li class="level1"><div class="li"> fichier gschemrc local: <code>$PWD/gschemrc]</code></div>
-</li>
-</ol>
-
-<p>
-Tous ces fichies de config peuvent ou non ajouter des chemins à la liste de recherche des bibliothèques. Si un fichier de config contient la commande
-</p>
-<pre class="code">(reset-component-library)</pre>
-
-<p>
- Le chemin de recherche des bibliothèques sera vidé. Lâ??ordre est évidemment important, comme cette commande effacera tout chemin précédemment ajoûté.
-</p>
-
-</div>
-<!-- SECTION "Ajouter des Composants ne proposent aucun symboles! Que puis-je y faire?" [21096-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/001geda_faq-simulation.html b/docs/wiki/001geda_faq-simulation.html
deleted file mode 100644
index dda1230..0000000
--- a/docs/wiki/001geda_faq-simulation.html
+++ /dev/null
@@ -1,173 +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>geda:faq-simulation.fr</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-05-24T22:27:26-0400" />
-<meta name="keywords" content="geda,faq-simulation.fr" />
-<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/geda:faq-simulation.fr?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:faq-simulation.fr"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:faq-simulation.fr"; />
-<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="#simulation" class="toc">Simulation</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#je_veux_simuler_mon_circuit_analogique._quelles_sont_mes_options" class="toc">Je veux simuler mon circuit analogique. Quelles sont mes options?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#qu_en_est-il_de_tclspice_qu_est_ce_que_c_est_dois-je_l_utiliser" class="toc">Qu'en est-il de tclspice? Qu'est ce que c'est? Dois-je l'utiliser?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#n_existe-t-il_une_belle_interface_graphique_capture_de_schema_de_telle_maniere_que_je_n_ai_juste_qu_a_placer_des_composants_et_presser_un_bouton_simulation" class="toc">N'existe-t-il une belle interface graphique (capture de schéma) de telle manière que je n'ai juste qu'à placer des composants et presser un bouton «·simulation·»?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#comment_puis-je_creer_mes_schemas_pour_faciliter_les_simulations_analogiques" class="toc">Comment puis-je créer mes schémas pour faciliter les simulations analogiques?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#quelles_sont_les_commandes_gnetlist_pour_spice_sont_a_utiliser_ici_il_y_en_a_beaucoup" class="toc">Quelles sont les commandes gnetlist pour SPICE sont à utiliser ici? Il y en a beaucoup. . . .</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#comment_faire_si_on_veut_utiliser_gnucap_puis-je_utiliser_spice-sdb_pour_creer_mes_netlists_gnucap" class="toc">Comment faire si on veut utiliser gnucap, puis-je utiliser spice-sdb pour créer mes netlists gnucap?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#pourquoi_ne_puis-je_reutiliser_mon_schema_de_simulation_pour_le_placement_sur_carte" class="toc">Pourquoi ne puis-je réutiliser mon schéma de simulation pour le placement sur carte?</a></span></div></li></ul>
-</li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="simulation" id="simulation">Simulation</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "Simulation" [1-25] -->
-<h2><a name="je_veux_simuler_mon_circuit_analogique._quelles_sont_mes_options" id="je_veux_simuler_mon_circuit_analogique._quelles_sont_mes_options">Je veux simuler mon circuit analogique. Quelles sont mes options?</a></h2>
-<div class="level2">
-
-<p>
-Parmi les applications de la Suite gEDA, il y a deux simulateurs de circuits analogiques: ngspice et gnucap. Plus (un peu) en détail:
-</p>
-<ul>
-<li class="level1"><div class="li"> <a href="http://ngspice.sourceforge.net/"; class="urlextern" title="http://ngspice.sourceforge.net/"; rel="nofollow">Ngspice</a> est un portage/nettoyage du SPICE 3f5 classique sur la plate-forme GNU/Linux. Il est pleinement fonctionnel, inclut des extensions XSpice (tels que des constructions SPICE 2 POLY) et une structure CIDER.</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://www.gnucap.org/"; class="urlextern" title="http://www.gnucap.org/"; rel="nofollow">Gnucap</a> est un nouveau simulateur de circuit écrit depuis zéro. Il offre la possibilité dâ??effectuer des simulations basées sur les événements â?? de même quâ??en temps â??. Câ??est le travail de Al Davis, Professor of Electrical Engineering à lâ??Université Kettering. Si vous voulez le télécharger, assurez-vous de prendre la dernière version, disponible avec les liens des «·developement releases·» sur le site gnucap.</div>
-</li>
-</ul>
-
-<p>
- Les deux sont des programmes CLI (command line interface·; «·interface à ligne de commande·»), signifiant que vous intérragissez avec le simulateur en saisissant les commandes sur la ligne de commande. Cela signifie aussi que vous avez besoin dâ??apprendre le jeu de commandes spécifique au simulateur.
-</p>
-
-<p>
-Si vous préférez une interface graphique, la nouvelle application GSpiceUI de gEDA fournit une jolie interface utilisateur graphique pour piloter les programmes de simulation. Néanmoins, GSpiceUI nâ??est pas un simulateur sortie-schema-vers-simulation complet comme LTSpice ou PSpice. Il fournit, à la place, un menu dâ??interface graphique qui vous vous aide à porter des commandes dont vous avez besoin pour effectuer vos simulations ngspice/gnucap.
-</p>
-
-</div>
-<!-- SECTION "Je veux simuler mon circuit analogique. Quelles sont mes options?" [26-1717] -->
-<h2><a name="qu_en_est-il_de_tclspice_qu_est_ce_que_c_est_dois-je_l_utiliser" id="qu_en_est-il_de_tclspice_qu_est_ce_que_c_est_dois-je_l_utiliser">Qu'en est-il de tclspice? Qu'est ce que c'est? Dois-je l'utiliser?</a></h2>
-<div class="level2">
-
-<p>
-<a href="http://tclspice.sourceforge.net/"; class="urlextern" title="http://tclspice.sourceforge.net/"; rel="nofollow">Tclspice</a> est un fork du développement de ngspice. Il a débuté en 2002. En principe, tclspice exportera le jeu de commande SPICE vers un <acronym title="Application Programming Interface">API</acronym> TCL, vous permettant dâ??embarquer des analyses SPICE en un programme TCL. Cette vision est certainement très attirante car TCL est un langage à scripts très puissant â?? bien plus puissant que les constructions de scripts disponibles dans SPICE lui-même. En utilisant TCL, il est possible dâ??imaginer lâ??écriture dâ??optimisateurs de circuits complexes, ajoutant des éléments de comportement à la simulation et finalement en gagnant le contrôle de la sortie graphique de SPICE.
-</p>
-
-<p>
-Au fur et à mesure, le but a été partiellement atteint â?? avec tclspice, vous pouvez donc faire quelque chose comme ceci:
-</p>
-<pre class="code">#! tclsh
-package require spice
-spice::codemodel /usr/local/src/tclspice-0.2.12/src/xspice/icm/spice2poly.cm
-
-spice::source netlistname.cir
-spice::tran 0.1ns 40ns
-spice::run
-spice::plot Vout
-puts "All done now!"</pre>
-
-<p>
-Malheureusement, tclspice manque de fonctionnalités importantes, comme vous fournir un code de retour qui vous indique à quel stade réel est votre simulation ou si elle est en erreur. Aussi, les fonctionnalités graphiques semblent de jamais fonctionner (au moins pour moi … et les développeurs admettent que la partie graphique a des problèmes). Convertir des variables TCL vers et depuis des vecteurs SPICE semble ne jamais fonctionner â?? encore une fois, au moins pour moi. Finalement, ngspice (au moins) beaucoup de fuites de mémoire, rendant les simulations longues difficiles. Câ??est la raison pour laquelle, tclspice nâ??a pas encore réalisé les promesses qui ont été originellement été faites: une manière pratique, par scripts pour piloter les simulations SPICE.
-</p>
-
-<p>
-Les développements sur tclspice ont effectivement cessé en 2004. Peu être quâ??un jour, quelquâ??un le redémarrera. Pendant ce temps, la branche de développement <a href="http://ngspice.sourceforge.net/"; class="urlextern" title="http://ngspice.sourceforge.net/"; rel="nofollow">ngspice</a> a récupéré quelques fonctionnalités tclspice si vous les voulez (elles nécessitent des options de configuration séparées) et le code est plus récent.
-</p>
-
-</div>
-<!-- SECTION "Qu'en est-il de tclspice? Qu'est ce que c'est? Dois-je l'utiliser?" [1718-3965] -->
-<h2><a name="n_existe-t-il_une_belle_interface_graphique_capture_de_schema_de_telle_maniere_que_je_n_ai_juste_qu_a_placer_des_composants_et_presser_un_bouton_simulation" id="n_existe-t-il_une_belle_interface_graphique_capture_de_schema_de_telle_maniere_que_je_n_ai_juste_qu_a_placer_des_composants_et_presser_un_bouton_simulation">N'existe-t-il une belle interface graphique (capture de schéma) de telle manière que je n'ai juste qu'à placer des composants et presser un bouton «·simulation·»?</a></h2>
-<div class="level2">
-
-<p>
-Non. Le miux que vous puissiez faire est dâ??utiliser GSpiceUI.
-</p>
-
-</div>
-<!-- SECTION "N'existe-t-il une belle interface graphique (capture de schéma) de telle manière que je n'ai juste qu'à placer des composants et presser un bouton «·simulation·»?" [3966-4210] -->
-<h2><a name="comment_puis-je_creer_mes_schemas_pour_faciliter_les_simulations_analogiques" id="comment_puis-je_creer_mes_schemas_pour_faciliter_les_simulations_analogiques">Comment puis-je créer mes schémas pour faciliter les simulations analogiques?</a></h2>
-<div class="level2">
-
-<p>
-Le chemin habituel pour la conception est «·gschem·» â?? «·gnetlist -g spice-sdb·» â?? [«·ngspice·» | «·gnucap·»]. Vous avez besoin dâ??attacher des attributs aux composants dans votre schéma pour fournir les attributs nécessaires à SPICE/Gnucap. Vous pouvez aussi attacher des attributs en utilisant gattrib.
-</p>
-
-<p>
-Le <a href="http://geda.seul.org/wiki/geda:csygas"; class="wikilink1" title="geda:csygas">Circuit Simulation using gEDA and SPICE - HOWTO</a> décrit tout ceci en détail.
-</p>
-
-<p>
- Quelques <a href="http://www.brorson.com/gEDA/SPICE/"; class="urlextern" title="http://www.brorson.com/gEDA/SPICE/"; rel="nofollow">ressources SPICE</a> vous aideront pour comprendre comment utiliser spice-sdb.
-</p>
-
-</div>
-<!-- SECTION "Comment puis-je créer mes schémas pour faciliter les simulations analogiques?" [4211-4853] -->
-<h2><a name="quelles_sont_les_commandes_gnetlist_pour_spice_sont_a_utiliser_ici_il_y_en_a_beaucoup" id="quelles_sont_les_commandes_gnetlist_pour_spice_sont_a_utiliser_ici_il_y_en_a_beaucoup">Quelles sont les commandes gnetlist pour SPICE sont à utiliser ici? Il y en a beaucoup. . . .</a></h2>
-<div class="level2">
-
-<p>
-Utilisez spice-sdb. Il est le plus riche en fonctionnalités. Les autres ne sont présent que pour des raisons historiques. Notez que spice-sdb est une extension dâ??une des autres commandes SPICE, vous ne perdez rien en utilisant spice-sdb.
-</p>
-
-</div>
-<!-- SECTION "Quelles sont les commandes gnetlist pour SPICE sont à utiliser ici? Il y en a beaucoup. . . ." [4854-5201] -->
-<h2><a name="comment_faire_si_on_veut_utiliser_gnucap_puis-je_utiliser_spice-sdb_pour_creer_mes_netlists_gnucap" id="comment_faire_si_on_veut_utiliser_gnucap_puis-je_utiliser_spice-sdb_pour_creer_mes_netlists_gnucap">Comment faire si on veut utiliser gnucap, puis-je utiliser spice-sdb pour créer mes netlists gnucap?</a></h2>
-<div class="level2">
-
-<p>
-Oui. Vous pouvez aussi dessiner votre schéma en utilisant les directives gnucap disponibles dans le répertoire de symbole «·spice·».
-</p>
-
-</div>
-<!-- SECTION "Comment faire si on veut utiliser gnucap, puis-je utiliser spice-sdb pour créer mes netlists gnucap?" [5202-5455] -->
-<h2><a name="pourquoi_ne_puis-je_reutiliser_mon_schema_de_simulation_pour_le_placement_sur_carte" id="pourquoi_ne_puis-je_reutiliser_mon_schema_de_simulation_pour_le_placement_sur_carte">Pourquoi ne puis-je réutiliser mon schéma de simulation pour le placement sur carte?</a></h2>
-<div class="level2">
-
-<p>
-Les nouveau veulent habituellement créer un schéma unique pour la simulation/validation et le placement sur carte. Cette vision semble tout dâ??abord attirante car votre carte aura dâ??abord été testée et validée avant de la créer en FR-4. Néanmoins, le diable est dans les détails·; utiliser un seul schéma pour la simulation et le placement ne fonctionne habituellement pas pour els raisons suivantes:
-</p>
-<ul>
-<li class="level1"><div class="li"> Les composants nécessaires pour la simulation et le placement sont normalement très différents. par exemple, la simulation nécessite souvent un schéma comportant un lot dâ??éléments liés à SPICE comme mes sources de tension, les sources dépendantes, les directives SPICE et ainsi de suite. Dâ??un autre côté, le placement nécessite des composant impossible à modéliser comme des connecteurs, des composants logiques et même des éléments comme des régulateurs de tension qui peuvent ne pas avoir de modèles SPICE de disponibles mais qui vont poluer votre netlist SPICE, rendant le netlister et le simulateur malheureux.</div>
-</li>
-<li class="level1"><div class="li"> Quelques composants électroniques réels nâ??ont pas de modèles SPICE. Il existe beaucoup de composants qui nâ??en possèdent pas comme les potentiomètres, les transformateurs, les thermistances, les filtres EMI, les portes logiques, les quartz, les tubes à vide et ainsi de suite. Câ??est la raison pour laquelle si votre schéma utilise un de ces composants, vous devez avoir un élément utilisant un circuit équivalent pour faire la simulation. Cela rend très difficile la réutilisation du schéma de simulation pour le placement.</div>
-</li>
-<li class="level1"><div class="li"> Habituellement, vous avez seulement besoin de simuler un sous-ensemble de votre schéma. Par exemple, vous pouvez vouloir simuler le comportement dâ??un filtre ou dâ??un circuit oscillant mais sans vous préoccuper de (ou vous ne pouvez pas simuler) votre alimentation, la partie logique ou tout autre partie de votre schéma. Si vous insister pour créer un modèle SPICE pour ces sous-sections de circuit, vous pourriez avoir beaucoup de problèmes â?? et faire beaucoup de travail inutile â?? de manière à trouver ou créer des modèles SPICE pour des zones de votre circuit qui ne sont pas importantes.</div>
-</li>
-</ul>
-
-<p>
- Câ??est la raison pour laquelle, je (SDB) recommande normalement de ne pas trop tenter dâ??utiliser le même schéma pour la simulation et pour le placement. Si vous pouvez le faire, câ??est bien! Mais, habituellement, vous ne le pouvez pas.
-</p>
-
-<p>
-Personellement, je ne crée des modèles SPICE que pour les sections analogiques critiques de mon circuit. Un projet plus grand devrait donc avoir plusieurs schémas de simulation validant les sous-circuits analogiques. En plus des schémas de simulation, jâ??ai un schéma principal qui est utilisé pour le placement.
-</p>
-
-</div>
-<!-- SECTION "Pourquoi ne puis-je réutiliser mon schéma de simulation pour le placement sur carte?" [5456-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/001geda_faq.html b/docs/wiki/001geda_faq.html
deleted file mode 100644
index 8ddc4e9..0000000
--- a/docs/wiki/001geda_faq.html
+++ /dev/null
@@ -1,329 +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>geda:faq.fr</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-06-27T07:37:40-0400" />
-<meta name="keywords" content="geda,faq.fr" />
-<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/geda:faq.fr?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:faq.fr"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:faq.fr"; />
-<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="#faq_geda" class="toc">FAQ gEDA</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#qu_est_ce_que_le_projet_geda" class="toc">Qu'est ce que le projet gEDA?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#qu_est_ce_que_geda_gaf_et_quelle_est_sa_relation_avec_geda" class="toc">qu'est ce que gEDA/gaf et quelle est sa relation avec gEDA?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#qu_est_ce_que_la_suite_geda" class="toc">Qu'est ce que la suite gEDA?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#pourquoi_qu_est_ce_qui_rend_geda_si_different_des_autres_outils_d_eda" class="toc">Pourquoi? Qu'est ce qui rend gEDA si différent des autres outils d'EDA ?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#pourquoi_la_suite_geda_ressemble-t-elle_a_une_collection_de_programmes_epars_et_pas_une_seule_application_integree" class="toc">Pourquoi la Suite gEDA ressemble-t-elle à une collection de programmes épars et pas une seule application intégrée?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#qu_est_ce_qui_est_mieux_une_suite_i.e._confederee_de_programmes_ou_une_application_integree" class="toc">Qu'est ce qui est mieux, une suite (i.e. confédérée) de programmes ou une application intégrée?</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#pour_la_suite_l_association" class="toc">Pour la Suite (l'association):</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#contre_la_suite_l_association" class="toc">Contre la Suite (l'association):</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#pour_les_applications_monolithiques" class="toc">Pour les applications monolithiques:</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#contre_les_applications_monolithiques" class="toc">Contre les applications monolithiques:</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#quelle_est_la_licence_utilisee_par_geda" class="toc">Quelle est la licence utilisée par gEDA?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#ou_puis-je_avoir_plus_d_informations_a_propos_de_geda_et_sur_son_telechargement" class="toc">Où puis-je avoir plus d'informations à propos de gEDA et sur son téléchargement?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#ok_comment_je_comence_a_utiliser_geda" class="toc">OK, comment je comence à utiliser gEDA?</a></span></div></li></ul>
-</li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="faq_geda" id="faq_geda">FAQ gEDA</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "FAQ gEDA" [1-24] -->
-<h2><a name="qu_est_ce_que_le_projet_geda" id="qu_est_ce_que_le_projet_geda">Qu'est ce que le projet gEDA?</a></h2>
-<div class="level2">
-
-<p>
-Le projet gEDA travaille à produire une suite <acronym title="GNU General Public License">GPL</acronym> complète dâ??outils EDA (<em class="u">E</em>lectronic <em class="u">D</em>esign <em class="u">A</em>utomation). Ces outils sont utilisés pour la conception de circuits électriques, la saisie de schémas, la simulation, le prototypage et la production. Le projet gEDA offre actuellement une suite mature dâ??applications de logiciels libres pour la conception électronique, incluant le la saisie de schémas, la gestion dâ??attributs, la génération de bill of materials (BOM), le netlisting dans plus de 20 formats de netlist, la simulation analogique et numérique et le placement sur circuit imprimé « printed circuit board (PCB) ».
-</p>
-
-<p>
-Ales Hvezda est à lâ??origine du projet gEDA. Le projet gEDA a quelque peu grossi, depuis le printemps 1998. Ces outils ne sont plus lâ??oeuvre dâ??une seule personne. De nombreuses personnes sâ??y sont impliquées. Quelques personnes contribuent aux outils originaux, alors que les autres développent leurs propres outils. Câ??est la raison pour laquelle gEDA ne se réfère plus aux outils originels (ils ont maintenant leurs propres vies) mais à tous les projets qui sont libres et qui sont associés quelque part dans ces pages web ou les listes de diffusion geda-dev/geda-user. En association avec gEDA, les auteurs de logiciels libres ne laissent pas le contrôle sur leurs outils mais ils sont aidés par la communauté pour maintenir la qualité et la liberté des outils EDA.
-</p>
-
-<p>
-gEDA peut être prononcé « gee-daahhh » (rhymes with cheetah) ou â??g-dahhh (short g).
-</p>
-
-</div>
-<!-- SECTION "Qu'est ce que le projet gEDA?" [25-1585] -->
-<h2><a name="qu_est_ce_que_geda_gaf_et_quelle_est_sa_relation_avec_geda" id="qu_est_ce_que_geda_gaf_et_quelle_est_sa_relation_avec_geda">qu'est ce que gEDA/gaf et quelle est sa relation avec gEDA?</a></h2>
-<div class="level2">
-
-<p>
-gaf signifie « <em class="u">g</em>schem <em class="u">a</em>nd <em class="u">f</em>riends » (gschem et ses amis). Câ??est un sous-jeu de la suite dâ??outils complète groupée sous le nom de gEDA. gEDA/gaf est une collection dâ??outils qui inclut actuellement:
-</p>
-<ul>
-<li class="level1"><div class="li"> gschem: un programme de capture de schémas</div>
-</li>
-<li class="level1"><div class="li"> gnetlist: un programme de génération de netlist</div>
-</li>
-<li class="level1"><div class="li"> gsymcheck: un vérificateur de syntaxe pour les symboles de schémas</div>
-</li>
-<li class="level1"><div class="li"> gattrib: une feuille de calcul qui manipule les propriétés des symboles dâ??un schéma</div>
-</li>
-<li class="level1"><div class="li"> libgeda: les bibliothèques pour gnetlist de gschem et gsymcheck</div>
-</li>
-<li class="level1"><div class="li"> gsch2pcb: Annotation directe depuis votre schéma vers le circuit en utilisant <a href="http://geda.seul.org/wiki/geda:pcb"; class="wikilink2" title="geda:pcb">PCB</a>.</div>
-</li>
-<li class="level1"><div class="li"> quelques utilitaires mineurs</div>
-</li>
-</ul>
-
-<p>
- Les outils gEDA/gaf partagent un format de fichier commun (.sch) et partagent aussi une bibliothèque commune (libgeda.so). Les sources de la distribution gEDA/gaf peuvent être trouvées sur ce site web (geda.seul.org).
-</p>
-
-<p>
-Bien que gaf se réfère surtout à gEDA, le nom gEDA ne sâ??applique pas obligatoirement à gaf â?? les outils rassemblés sous la bannière de « gEDA » comprennent beaucoup dâ??autres programmes. En fait, gEDA fait référence à <strong>tout</strong> outil dâ??EDA sous <acronym title="GNU General Public License">GPL</acronym> qui décide de sâ??associer avec le site web/liste de diffusion. Des exemples importants dâ??outils gEDA incluent le programme de création de circuit imprimé <a href="http://geda.seul.org/wiki/geda:pcb"; class="wikilink2" title="geda:pcb">PCB</a>, le compilateur Verilog <a href="http://www.icarus.com/eda/verilog/"; class="urlextern" title="http://www.icarus.com/eda/verilog/"; rel="nofollow">Icarus Verilog</a>, le simulateur de circuits analogiques <a href="http://www.gnucap.org/"; class="urlextern" title="http://www.gnucap.org/"; rel="nofollow">gnucap</a> et le simulateur open-source SPICE <a href="http://www.ngspice.org/"; class="urlextern" title="http://www.ngspice.org/"; rel="nofollow">ngspice</a>. Il existe plusieurs autres programmes gEDA.
-</p>
-
-<p>
-Pour des raisons historiques, sur <a href="http://freshmeat.net/"; class="urlextern" title="http://freshmeat.net/"; rel="nofollow">freshmeat</a>, gaf est connu comme le paquet â??gEDAâ??.
-</p>
-
-</div>
-<!-- SECTION "qu'est ce que gEDA/gaf et quelle est sa relation avec gEDA?" [1586-3369] -->
-<h2><a name="qu_est_ce_que_la_suite_geda" id="qu_est_ce_que_la_suite_geda">Qu'est ce que la suite gEDA?</a></h2>
-<div class="level2">
-
-<p>
-La suite gEDA est une image CDROM (.iso) crée par Stuart Brorson pour faciliter lâ??installation des divers outils qui forment, sont associés oiu fonctionnent totalement avec le projet gEDA. Lâ??objectif est que les outils rassemblés sur la suite gEDA en CDROM constitue un environnement de conception cohérent, complet, open-source en un seul téléchargement. La suite gEDA sur CDROM inclut actuellement:
-</p>
-<ul>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/tools/"; class="urlextern" title="http://geda.seul.org/tools/"; rel="nofollow">gEDA/gaf</a> â?? saisie de schématic et netlisting</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/tools/ngspice"; class="urlextern" title="http://geda.seul.org/tools/ngspice"; rel="nofollow">ngspice</a> â?? simulation SPICE</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/tools/gnucap"; class="urlextern" title="http://geda.seul.org/tools/gnucap"; rel="nofollow">gnucap</a> â?? simulation analogique</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/tools/gspiceui"; class="urlextern" title="http://geda.seul.org/tools/gspiceui"; rel="nofollow">gspiceui</a> â?? <acronym title="Graphical User Interface">GUI</acronym> front end for ngspice/gnucap</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/tools/pcb"; class="urlextern" title="http://geda.seul.org/tools/pcb"; rel="nofollow">pcb</a> â?? placement avec PCB</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/tools/gerbv"; class="urlextern" title="http://geda.seul.org/tools/gerbv"; rel="nofollow">gerbv</a> â?? visualisation Gerber</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/tools/icarus"; class="urlextern" title="http://geda.seul.org/tools/icarus"; rel="nofollow">Icarus Verilog</a> â?? simulateur Verilog</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/tools/gtkwave"; class="urlextern" title="http://geda.seul.org/tools/gtkwave"; rel="nofollow">GTKWave</a> â?? visualisation de forme dâ??onde numérique</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://wcalc.sourceforge.net/"; class="urlextern" title="http://wcalc.sourceforge.net/"; rel="nofollow">wcalc</a> â?? analyse de ligne de transmission et structure électromagnetique</div>
-</li>
-</ul>
-
-<p>
- Au centre de la suite gEDA en CDROM est la facilité dâ??utiliser lâ??installateur qui automatise la construction et lâ??installation des divers paquets depuis les sources - facilitant lâ??installation la suite complète pour les novices. La suite gEDA en CDROM est disponible sur la page de <a href="http://geda.seul.org/download.html"; class="urlextern" title="http://geda.seul.org/download.html"; rel="nofollow">téléchargement</a>. <strong>Note: Lâ??installateur ne fonctionne quâ??avec Linux!</strong>
-</p>
-
-</div>
-<!-- SECTION "Qu'est ce que la suite gEDA?" [3370-4962] -->
-<h2><a name="pourquoi_qu_est_ce_qui_rend_geda_si_different_des_autres_outils_d_eda" id="pourquoi_qu_est_ce_qui_rend_geda_si_different_des_autres_outils_d_eda">Pourquoi? Qu'est ce qui rend gEDA si différent des autres outils d'EDA ?</a></h2>
-<div class="level2">
-
-<p>
-Les outils de la suite gEDA et leurs associés ont les caractéristiques suivantes:
-</p>
-<ul>
-<li class="level1"><div class="li"> Gratuit.</div>
-</li>
-<li class="level1"><div class="li"> Tous les formats de fichiers et tous les codes sources sont disponibles en licence <acronym title="GNU General Public License">GPL</acronym>. Cette licence vous garantit des droits spécifiques aux auteurs et aux utilisateurs de logiciels <acronym title="GNU General Public License">GPL</acronym>.</div>
-</li>
-<li class="level1"><div class="li"> Lâ??indépendence vis à vis de toute entreprise. Tous les outils gEDA sont fournis avec les sources complètes. Vous pouvez les changer, les améliorer, les porter (sur dâ??autres systèmes) et même les distribuer (si vous respectez les termes de la <acronym title="GNU General Public License">GPL</acronym>).</div>
-</li>
-<li class="level1"><div class="li"> Aucun mécanisme nâ??est utilisé pour restreindre lâ??utilisation de ces outils (comme lâ??utilisation de numéros de série du disque dur ou des adresses ethernet pour forcer le logiciel à ne fonctionner que sur un machine).</div>
-</li>
-<li class="level1"><div class="li"> Aucunes limitations arbitraires, imposées par les marketing ou les ingénieurs. Les versions gratuites des outils commerciaux incluent des limitations capricieuses (i.e. une taille de carte limité, lâ??impossibilité dâ??imprimer, lâ??impossibilité dâ??exporter des netlists, etc.) qui verrouille le programme et force les utilisateurs sérieux à acheter les outils complets. Par contraste, les outils gEDA sont pleinement fonctionnels et nâ??imposent aucune limitation arbitraire sur la conception pour vous soutirer de lâ??argent.</div>
-</li>
-<li class="level1"><div class="li"> Garanties de protection de conception. Comme le logiciel fonctionnera pour toujours (pour les raisons citées ci-dessus), les fichiers de conception de gEDA sera toujours visualisable/éditable (avec les bonnes versions du logiciel).</div>
-</li>
-<li class="level1"><div class="li"> Flux de conception ouverts. Cela signifie que les outils correspondent les uns avec les autres par des moyens connus et documentés (fichiers / <acronym title="Application Programming Interface">API</acronym>). Il est facile de remplacer un outil ou de lâ??améliorer avec quelque chose dâ??autre si vous le désirez.</div>
-</li>
-<li class="level1"><div class="li"> Stabilité - Les bogues qui plantent sont étudiés immediatement et réparés dès que possible.</div>
-</li>
-<li class="level1"><div class="li"> Minimise les fonctionnalités gourmandes et inutiles.</div>
-</li>
-<li class="level1"><div class="li"> Fonctionne sur autant de plates-formes que possible. Pour gEDA/gaf: GNU/Linux et dâ??autres systèmes Unix.</div>
-</li>
-<li class="level1"><div class="li"> Dévelopé dâ??une manière ouverte (pas de secrets).</div>
-</li>
-<li class="level1"><div class="li"> Les programmes sont documentées.</div>
-</li>
-</ul>
-
-<p>
- gEDA nâ??aura peut être pas les dernières fonctionnalités les plus pointues que lâ??on pourrait trouver dans dâ??autres paquets et peut, quelques fois, être vu comme à la traîne de la technique EDA mais les outils sont devenus utiles à beaucoup de personnes à cause des raisons mentionnées ci-dessus.
-</p>
-
-</div>
-<!-- SECTION "Pourquoi? Qu'est ce qui rend gEDA si différent des autres outils d'EDA ?" [4963-7518] -->
-<h2><a name="pourquoi_la_suite_geda_ressemble-t-elle_a_une_collection_de_programmes_epars_et_pas_une_seule_application_integree" id="pourquoi_la_suite_geda_ressemble-t-elle_a_une_collection_de_programmes_epars_et_pas_une_seule_application_integree">Pourquoi la Suite gEDA ressemble-t-elle à une collection de programmes épars et pas une seule application intégrée?</a></h2>
-<div class="level2">
-
-<p>
-La Suite gEDA est un rassemblement de programmes independants. Cela sâ??est produit pour des raisons historiques: Ales Hvezda a débuté le programme gEDA plus ou moins seul. La vision originelle était de produire une suite intégrée complète pour créer des circuits imprimés de telle manière que les passionnés de robots puissent concevoir leurs propres cartes. Néanmoins, au fur et à mesure de la progression du projet gEDA, lâ??ampleur de la tâche est devenu claire - et le codage des nombreuses applications proposées nâ??avait pas encore commencé!
-</p>
-
-<p>
-Pendant ce temps, dâ??autres développeurs de logiciels -avec leurs propres applications écrites indépendament - ont trouvé que la vision du projet permettait de les compléter. Les auteurs de ces applications se sont joints à Ales et ont fait contribuer leur programme au projet gEDA. Parmi des projets, on trouve « pcb », un programme de création de circuits imprimés vieux de 10 ans (à ce moment). Avec cette contribution de « pcb », lâ??outil originel pour circuits imprimés de gEDA, « gpcb » a été abandonné. Au même moment, dâ??autres développeurs ont ajouté des simulateurs analogiques et numériques, des visualiseurs de formes de signal, ainsi de suite.
-</p>
-
-<p>
-Câ??est de cette manière que sâ??est agglomérée la suite gEDA. Ce nâ??est pas un code partagé ou une interface utilisateur commune qui distingue la suite gEDA. Câ??est plutôt la vision partagée dâ??un environnement EDA open-source qui maintient la cohérence du projet. Aujourdâ??hui, la Suite gEDA est un ensemble de différents programmes réalisés par plusieurs auteurs. Les applications tentent de fonctionner ensemble et réussissent généralement. Mais les démarrages séparés de chaque programme de la suite sont encore observables. Néanmoins, avec un peu de travail, les divers composants de la Suite sont intéropérables et plusieurs personnes ont achevé des circuits imprimés assez compliqués en utilisant la Suite gEDA.
-</p>
-
-</div>
-<!-- SECTION "Pourquoi la Suite gEDA ressemble-t-elle à une collection de programmes épars et pas une seule application intégrée?" [7519-9623] -->
-<h2><a name="qu_est_ce_qui_est_mieux_une_suite_i.e._confederee_de_programmes_ou_une_application_integree" id="qu_est_ce_qui_est_mieux_une_suite_i.e._confederee_de_programmes_ou_une_application_integree">Qu'est ce qui est mieux, une suite (i.e. confédérée) de programmes ou une application intégrée?</a></h2>
-<div class="level2">
-
-<p>
-Câ??est plus une question de religion. Je vais résumer quelques pour et contre (tel que je les vois) de chaque approche ici.
-</p>
-
-</div>
-<!-- SECTION "Qu'est ce qui est mieux, une suite (i.e. confédérée) de programmes ou une application intégrée?" [9624-9861] -->
-<h3><a name="pour_la_suite_l_association" id="pour_la_suite_l_association">Pour la Suite (l'association):</a></h3>
-<div class="level3">
-<ul>
-<li class="level1"><div class="li"> Vous pouvez utiliser les « meilleures des espèces » dâ??applications pour chaque partie de la conception. Ceci étant, vous pouvez utiliser le flux standard de gEDA gschem â??gsch2pcb â??pcb pour créer un circuit imprimé. Néanmoins, si vous pensez que lâ??application open-source « PCB » craint, vous pouvez utiliser le flux gschem â??gnetlist â??Protel (par exemple). Rappelez-vous que gnetlist peut sortir plus de vingt différents formats de netlist! De plus, si vous nâ??aimez pas un des composants du flux, vous pouvez écrire un autre outil qui le remplacera. Maintenant, il est vrai, quâ??en ce moment, en général, quâ??il nâ??existe quâ??une seule application pour effectuer une tâche particulière. Cette situation devrait néanmoins changer avec le temps â?? comme en témoigne la nouvelle branche du projet « pcb », le netlister supplémentaire <a href="http://www.viasic.com/opensource/"; class="urlextern" title="http://www.viasic.com/opensource/"; rel="nofollow">gnetman</a>, de même que le projet <a href="http://web.comhem.se/~u31829222/"; class="urlextern" title="http://web.comhem.se/~u31829222/"; rel="nofollow">HEC</a>. En règle générale, lâ??approche de la suite offre la plus grande liberté à lâ??utilisateur.</div>
-</li>
-<li class="level1"><div class="li"> Le flux de la conception possède quelques points dâ??arrêts naturels. Cela se produit lorsquâ??un des outils achève son travail et lâ??écrit dans un dans un fichier (i.e. gschem écrit un fichier .sch ou gnetlist écrit une netlist SPICE). A ce point, vous pouvez facilement casser le flux et écrire des scripts qui traite totalement et/ou partiellement les données de lâ??étude. Pour les grands développements, câ??est un avantage réel dâ??avoir une approche de « suite de conception ». Cet avantage peut peut ne parler quâ??aux « utilisateurs intensifs » mais notez son importance: toutes les suites dâ??EDA de rang professionnel (Synopsys, Xilinx) travaillent de la même manière.</div>
-</li>
-<li class="level1"><div class="li"> Lâ??utilisation dâ??une suite dâ??applications peut être automatisé en utilisant un Makefile ou même un script <acronym title="Practical Extraction and Report Language">Perl</acronym>. Les concepteur dâ??ASIC le font en permanence avec leurs outils de schémas et de synthèse. Quelques utilisateurs gEDA ont publiquement annoncé (sur la liste de diffusion) quâ??ils le faisaient aussi et soulignent que câ??est une fonctionnalité importante de la suite gEDA.</div>
-</li>
-<li class="level1"><div class="li"> Extensibilité: une application monolithique est presque toujours développée un seul développeur qui a une vision unique de son programme. Ce développeur peut assurer un standard de style et dâ??interface utilisateur pour tous ses outils. Le problème avec ceci est quâ??un développeur seul ne peut écrire - même sâ??il est particulièrement doué - quâ??un (ou quelques) partie dâ??une application EDA. Câ??est la raison pour laquelle toute application EDA monolithique, open-source, sera toujours limitée dans son champ et ses fonctionnalités par les aptitudes dâ??un développeur seul. (Jâ??aimerais que lâ??on me prouve que jâ??ai tord sur ce point. Les contres-exemples sont les bienvenus mais aucun nâ??a attiré mon attention lors de lâ??écriture de cette partie.) Dâ??un autre côté, une assemblée de développeurs travaillant indépendamment sur leurs propres applications - tout en contribuant à lâ??oeuvre dans son ensemble â?? peuvent donc créer un environnement EDA très grand et très capable.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Pour la Suite (l'association):" [9862-13042] -->
-<h3><a name="contre_la_suite_l_association" id="contre_la_suite_l_association">Contre la Suite (l'association):</a></h3>
-<div class="level3">
-<ul>
-<li class="level1"><div class="li"> Câ??est plus difficile pour les nouveaux car ils ne connaissent pas le flux dâ??avance. Ceci étant, ils ont réellement besoin de <acronym title="Read The Fine Manual">RTFM</acronym> pour savoir quel est lâ??outil quâ??ils devront faire ensuite fonctionner. Une bonne documentation aide (câ??est la raison pour laquelle vous lisez ceci) mais elle reste toujours un second choix après le développement dâ??une interface intuitive.</div>
-</li>
-<li class="level1"><div class="li"> Les différents programmes peuvent avoir diverses conventions dâ??interfaces utilisateur (i.e. lâ??organisation du menu est différente, la fonctionnalité des touches ou de la souris sont différents). Ceci peut être désagréable pour ceux qui ne sont pas familiers avec les programmes.</div>
-</li>
-<li class="level1"><div class="li"> Comme aucune supposition nâ??est faite dans le flux de la conception, les symboles <a href="http://geda.seul.org/wiki/geda:faq-gschem#what_s_this_business_about_heavy_vs._light_symbols"; class="wikilink1" title="geda:faq-gschem">légers</a> de schémas sont nécessaires. Cela impose à lâ??utilisateur de passer plus de temps à ajouter, par exemple, des attributs dâ??empreintes de composants à son schéma. De plus, lâ??utilisateur doit passer réellement plus de temps à trouver quelle empreinte utiliser. Néanmoins, une bonne suite (comme la suite gEDA) offrira de multiples méthodes pour effectuer cette tâche (i.e. gattrib, des scripts <acronym title="Practical Extraction and Report Language">Perl</acronym> pour faciliter les empreintes, etc.).</div>
-</li>
-<li class="level1"><div class="li"> Quelques développeurs sont plus énergiques que dâ??autres ou ont plus de temps libre. Câ??est la raison pour laquelle quelques programmes de la suite seront plus développés (et moins bogués) que dâ??autres. Malheureusement, un seul programme bogué dans une suite peut entacher la perception dâ??un nouvel utilisateur sur la suite complète.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Contre la Suite (l'association):" [13043-14705] -->
-<h3><a name="pour_les_applications_monolithiques" id="pour_les_applications_monolithiques">Pour les applications monolithiques:</a></h3>
-<div class="level3">
-<ul>
-<li class="level1"><div class="li"> Un environnement unique, unifié est plus facile à apréhender pour les utilisateurs. Les conventions dâ??interfaces utilisateur peuvent être harmonisées. Lâ??outil peut être suffisamment intuitif de telle manière quâ??il puisse être utilisé sans <acronym title="Read The Fine Manual">RTFM</acronym>.</div>
-</li>
-<li class="level1"><div class="li"> Les symboles de schémas peuvent être complets, avec moins de travail nécessaire pour lâ??attachement des attributs à chaque symbole dans un schéma.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Pour les applications monolithiques:" [14706-15166] -->
-<h3><a name="contre_les_applications_monolithiques" id="contre_les_applications_monolithiques">Contre les applications monolithiques:</a></h3>
-<div class="level3">
-<ul>
-<li class="level1"><div class="li"> Elles ne sont pas ajustables indéfiniment. Un développeur ne peut pas tout faire, quelque soit sa force. Câ??est la raison pour laquelle une application monolithique nâ??aura jamais la puissance dâ??une suite développée par une confédération de programmeurs.</div>
-</li>
-<li class="level1"><div class="li"> Manque de choix. Si le développeur nâ??aime pas votre manière de faire les choses, vous nâ??auvez aucun autre choix. Même si vous soumettez des patches pour permettre pour pouvoir travailler à votre manière, il est possible que le développeur principal ignore ou rejette vos modifications. Ce nâ??est probablement pas grave pour les nouveaux mais çà lâ??est pour les « utilisateurs intensifs ».</div>
-</li>
-<li class="level1"><div class="li"> Risque. Si le développeur de lâ??application abandonne, le code est abandoné et les utilisateurs en patissent. Câ??est ce qui sâ??est produit avec le programme <a href="http://sourceforge.net/projects/xtrkcad"; class="urlextern" title="http://sourceforge.net/projects/xtrkcad"; rel="nofollow">XTrkCAD</a>, un programme de CAO pour concevoir des voies ferrées. Lâ??auteur du programme a cessé de le développer mais lâ??a heureusement placé sur Sourceforge pour lâ??empêcher de disparaître. Malheureusement, sans lâ??implication du développeur originel, le code a stagné. Les patches des contributeurs sont allés dans /dev/null. Une coalition dâ??utilisateurs/développeurs ont fini par créer un <a href="http://xtrkcad-fork.sourceforge.net/"; class="urlextern" title="http://xtrkcad-fork.sourceforge.net/"; rel="nofollow">fork</a> du code pour permettre un développement ultérieur. Néanmoins, le travail sur le code forké a été parcimonieux et sporadique. (Jâ??espère que cela changera un jour.) pendant ce temps, pour lâ??utilisateur normal, lâ??abandon du développeur a représenté une catastrophe.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Contre les applications monolithiques:" [15167-16800] -->
-<h2><a name="quelle_est_la_licence_utilisee_par_geda" id="quelle_est_la_licence_utilisee_par_geda">Quelle est la licence utilisée par gEDA?</a></h2>
-<div class="level2">
-
-<p>
-Tous les outils et fichiers associés de gEDA sont sous GNU General Public License version 2 (<acronym title="GNU General Public License">GPL</acronym>), de la Free Software Foundation
-</p>
-
-<p>
-La licence:
-</p>
-
-<p>
-Lorsque nous parlons de logiciels libre, nous nous référons à la liberté, pas au prix. Nos « General Public Licenses » sont conçues pour sâ??assurer que vous avez la liberté de distribuer des copies des logiciels libres (et de faire payer pour ce service si vous le souhaitez), que vous recevez le code source ou que vous puissiez lâ??obtenir si vous le souhaitez, que vous pouvez modifier le logiciel ou en utiliser des morceaux dans de nouveaux programmes libres; et que vous sachiez comment le faire.
-</p>
-
-<p>
-Ce nâ??est jamais assez répété: « gEDA est un logiciel <acronym title="GNU General Public License">GPL</acronym> ». Câ??est la raison pour laquelle rien de propriétaire ne peut être distribué avec gEDA, tel que les bibliothèques de composants depuis les produits dâ??EDA propriétaires. Le programme de conversion pour les bibliothèques propriétaires sera disponible mais les fichiers de conversion qui font partie du produit propriétaire ne doivent jamais être mis dans gEDA. Les fichiers contribués doivent pouvoir être <acronym title="GNU General Public License">GPL</acronym> (ou être placé sous une autre licence libre). Veuillez garder ceci en mémoire si vous souhaitez y contribuer.
-</p>
-
-<p>
-Bien que lâ??ojectif de gEDA soit les logiciels <acronym title="GNU General Public License">GPL</acronym>, les logiciels avec dâ??autres licences sont plus que les bienvenus, tant quâ??ils restent compatibles avec la <acronym title="GNU General Public License">GPL</acronym>.
-</p>
-
-</div>
-<!-- SECTION "Quelle est la licence utilisée par gEDA?" [16801-18266] -->
-<h2><a name="ou_puis-je_avoir_plus_d_informations_a_propos_de_geda_et_sur_son_telechargement" id="ou_puis-je_avoir_plus_d_informations_a_propos_de_geda_et_sur_son_telechargement">Où puis-je avoir plus d'informations à propos de gEDA et sur son téléchargement?</a></h2>
-<div class="level2">
-
-<p>
-Le site officiel est <a href="http://geda.seul.org/"; class="urlextern" title="http://geda.seul.org/"; rel="nofollow">gEDA Project</a>, hébergé par le <a href="http://www.seul.org/"; class="urlextern" title="http://www.seul.org/"; rel="nofollow">projet SEUL</a>. Le miroir européen est sur <a href="http://ftp.sunet.se/geda/"; class="urlextern" title="http://ftp.sunet.se/geda/"; rel="nofollow">miroir du projet Européen de gEDA</a> hébergé par le réseau des universités suédoises.
-</p>
-
-<p>
-Il existe plusieurs listes de diffusion. Veuillez aller voir la <a href="http://geda.seul.org/mailinglist"; class="urlextern" title="http://geda.seul.org/mailinglist"; rel="nofollow">page d'info</a> sur les listes de diffusion pour savoir comment souscrire et poster.
-</p>
-
-<p>
-Vous pouvez télécharger tous les logiciels, incluant la suite gEDA sur CDROM depuis la page <a href="http://geda.seul.org/download.html"; class="urlextern" title="http://geda.seul.org/download.html"; rel="nofollow">download</a>.
-</p>
-
-<p>
-Vous pouvez trouver le dernier jeu de documentation sur la page de sommaire <a href="http://geda.seul.org/docs/"; class="urlextern" title="http://geda.seul.org/docs/"; rel="nofollow">documentation</a>.
-</p>
-
-<p>
-Venez à la réunion des « Free EDA Users Group » (Freedog) de Cambridge, MA. La réunion est à 7H le premier mercredi de chaque mois au <a href="http://www.starbucks.com/retail/locator/MapResults.aspx?a=1&StoreKey=93728&IC_O=42.3599350625432%3a-71.1021394862385%3a32%3a02139+(postal+code)%2c+Massachusetts%2c+United+States&GAD1_O=&GAD2_O=&GAD3_O=02139+(postal+code)%2c+Massachusetts%2c+United+States&GAD4_O=&radius=5&countryID=244&dataSource=MapPoint.NA" class="urlextern" title="http://www.starbucks.com/retail/locator/MapResults.aspx?a=1&StoreKey=93728&IC_O=42.3599350625432%3a-71.1021394862385%3a32%3a02139+(postal+code)%2c+Massachusetts%2c+United+States&GAD1_O=&GAD2_O=&GAD3_O=02139+(postal+code)%2c+Massachusetts%2c+United+States&GAD4_O=&radius=5&countryID=244&dataSource=MapPoint.NA" rel="nofollow">Kendal Square Starbucks</a>.
-</p>
-
-</div>
-<!-- SECTION "Où puis-je avoir plus d'informations à propos de gEDA et sur son téléchargement?" [18267-19556] -->
-<h2><a name="ok_comment_je_comence_a_utiliser_geda" id="ok_comment_je_comence_a_utiliser_geda">OK, comment je comence à utiliser gEDA?</a></h2>
-<div class="level2">
-
-<p>
-La chose la plus importante à faire est de lire et de comprendre lâ??excellent tutoriel de Bill Wilson <a href="http://geda.seul.org/wiki/geda:gsch2pcb_tutorial"; class="wikilink1" title="geda:gsch2pcb_tutorial">gschem -> gsch2pcb -> PCB</a>. Cela vous permettra de débuter.
-</p>
-
-<p>
-Assurez-vous aussi de visionner les autres <a href="http://geda.seul.org/docs"; class="urlextern" title="http://geda.seul.org/docs"; rel="nofollow">documentations gEDA</a>. Un guide dâ??installation est contenu dans ce Wiki, ainsi que des informations générales sur lâ??utilisation de ces outils. Prenez un peu de temps à naviguer, télécharger la Suite gEDA Suite et essayez-le par vous même!
-</p>
-
-</div>
-<!-- SECTION "OK, comment je comence à utiliser gEDA?" [19557-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/001geda_gschem_mp.html b/docs/wiki/001geda_gschem_mp.html
deleted file mode 100644
index 0b269f3..0000000
--- a/docs/wiki/001geda_gschem_mp.html
+++ /dev/null
@@ -1,27 +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>geda:gschem_mp.fr</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="noindex,follow" />
-<meta name="date" content="1969-12-31T19:00:00-0500" />
-<meta name="keywords" content="geda,gschem_mp.fr" />
-<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/geda:gschem_mp.fr?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gschem_mp.fr"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gschem_mp.fr"; />
-<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>
-</body>
-</html>
diff --git a/docs/wiki/001geda_gschem_ug.html b/docs/wiki/001geda_gschem_ug.html
deleted file mode 100644
index 8e04059..0000000
--- a/docs/wiki/001geda_gschem_ug.html
+++ /dev/null
@@ -1,3559 +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>geda:gschem_ug.fr</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-06-27T07:44:10-0400" />
-<meta name="keywords" content="geda,gschem_ug.fr" />
-<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/geda:gschem_ug.fr?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gschem_ug.fr"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gschem_ug.fr"; />
-<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="#guide_de_l_utilisateur_gschem_geda" class="toc">Guide de l'utilisateur gschem gEDA</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#about_this_document" class="toc">About this document ...</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#introduction" class="toc">Introduction</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#overview" class="toc">Overview</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#resources" class="toc">Resources</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#how_to_ask_questions" class="toc">How To Ask Questions</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#installing_gschem" class="toc">Installing gschem</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#latest_stable" class="toc">Latest Stable</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#geda_tools_suite_cd-rom" class="toc">"gEDA Tools Suite" CD-ROM</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#debian_distributions" class="toc">Debian distributions</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#red_hat_distributions" class="toc">Red Hat distributions</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#mac_osx_distributions" class="toc">Mac OSX distributions</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#cvs_unstable_testing" class="toc">CVS Unstable/Testing</a></span></div></li>
-</ul>
-</li>
-<li class="level1"><div class="li"><span class="li"><a href="#configuring_gschem" class="toc">Configuring gschem</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#gschemrc" class="toc">gschemrc</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#gafrc" class="toc">gafrc</a></span></div></li>
-</ul>
-</li>
-<li class="level1"><div class="li"><span class="li"><a href="#lancer_gschem" class="toc">Lancer gschem</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#confirming_gschem_is_installed" class="toc">Confirming gschem is installed</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#the_shell_prompt" class="toc">The Shell Prompt</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#backups" class="toc">Backups</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#classic_linux_backups" class="toc">Classic Linux backups</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#incremental_backups" class="toc">Incremental backups</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#relevant_configuration_settings" class="toc">Relevant configuration settings</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#on-line_documentation" class="toc">On-line documentation</a></span></div></li>
-</ul>
-</li>
-<li class="level1"><div class="li"><span class="li"><a href="#electrical_connectivity" class="toc">Electrical Connectivity</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#components_symbols_objects_attributes" class="toc">Components & Symbols & Objects & Attributes</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#components" class="toc">Components</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#symbols" class="toc">Symbols</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#objects" class="toc">Objects</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#attributes" class="toc">Attributes</a></span></div></li>
-</ul>
-</li>
-<li class="level1"><div class="li"><span class="li"><a href="#the_main_window" class="toc">The Main Window</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#the_status_window" class="toc">The Status Window</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#the_schematic_file" class="toc">The Schematic File</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#the_symbol_file" class="toc">The Symbol File</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#symbol_libraries" class="toc">Symbol Libraries</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#the_log_file" class="toc">The Log File</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#grips" class="toc">Grips</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#menu_operations" class="toc">Menu Operations</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#file" class="toc">File</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#new_window_fw" class="toc">New Window (fw)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#new_page_fn" class="toc">New Page (fn)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#open_page..._fo" class="toc">Open Page... (fo)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#close_page_pc" class="toc">Close Page (pc)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#revert_page_pr" class="toc">Revert Page (pr)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#save_page_fs" class="toc">Save Page (fs)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#save_page_as..._fa" class="toc">Save Page As... (fa)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#save_all_fl_fl" class="toc">Save All (fl) (fl)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#print..._fp" class="toc">Print... (fp)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#write_png..._fi" class="toc">Write PNG... (fi)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#execute_script..._ft" class="toc">Execute Script... (ft)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#close_window_fc" class="toc">Close Window (fc)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#quit_alt-q" class="toc">Quit (Alt-q)</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#edit" class="toc">Edit</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#undo_shift-u" class="toc">Undo (shift-u)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#redo_shift-r" class="toc">Redo (shift-r)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#select_mode_s" class="toc">Select Mode (s)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#edit..._ee" class="toc">Edit... (ee)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#edit_text..._ex" class="toc">Edit Text... (ex)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#copy_mode_ec" class="toc">Copy Mode (ec)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#move_mode_em" class="toc">Move Mode (em)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#delete_delete-key" class="toc">Delete (Delete-key)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#rotate_90_mode_er" class="toc">Rotate 90 Mode (er)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#mirror_mode_ei" class="toc">Mirror Mode (ei)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#slot..._e_shift-s" class="toc">Slot... (e shift-s)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#color..._eo" class="toc">Color... (eo)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#lock_el_unlock_e_shift-l" class="toc">Lock (el) / Unlock (e shift-l)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#line_width_type..._ew" class="toc">Line Width & Type... (ew)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#fill_type..._ef" class="toc">Fill Type... (ef)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#symbol_translate..._et" class="toc">Symbol Translate... (et)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#embed_component_picture_eb" class="toc">Embed Component/Picture (eb)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#unembed_component_picture_eu" class="toc">Unembed Component/Picture (eu)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#update_component_ep" class="toc">Update Component (ep)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#show_hide_inv_text_en" class="toc">Show/Hide Inv Text (en)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#make_inv_text_vis_ev" class="toc">Make Inv Text Vis (ev)</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#buffer" class="toc">Buffer</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#copy_into_1_2_3_4_5_yc" class="toc">Copy into 1/2/3/4/5 (yc)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#cut_into_1_2_3_4_5_yu" class="toc">Cut into 1/2/3/4/5 (yu)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#paste_from_1_2_3_4_5_yp" class="toc">Paste from 1/2/3/4/5 (yp)</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#view" class="toc">View</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#redraw_vr" class="toc">Redraw (vr)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#pan_x" class="toc">Pan (x)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#zoom_box_w" class="toc">Zoom Box (w)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#zoom_extents_ve" class="toc">Zoom Extents (ve)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#zoom_in_z" class="toc">Zoom In (z)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#zoom_out_z" class="toc">Zoom Out (Z)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#zoom_full_vf" class="toc">Zoom Full (vf)</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#page" class="toc">Page</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#manager..._pm" class="toc">Manager... (pm)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#next" class="toc">Next (>)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#previous" class="toc">Previous (<)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#new_pe" class="toc">New (pe)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#revert_pr" class="toc">Revert (pr)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#close_pc" class="toc">Close (pc)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#discard_pd" class="toc">Discard (pd)</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#add" class="toc">Add</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#component..._i" class="toc">Component... (i)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#net_n" class="toc">Net (n)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#bus_u" class="toc">Bus (u)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#attribute..._aa" class="toc">Attribute... (aa)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#text..._at" class="toc">Text... (at)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#line_l" class="toc">Line (l)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#box_b" class="toc">Box (b)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#circle_ai" class="toc">Circle (ai)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#arc_ar" class="toc">Arc (ar)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#pin_ap" class="toc">Pin (ap)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#picture..._ag" class="toc">Picture... (ag)</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#hierarchy" class="toc">Hierarchy</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#down_schematic_hd" class="toc">Down Schematic (Hd)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#down_symbol_hs" class="toc">Down Symbol (Hs)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#up_hu" class="toc">Up (Hu)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#documentation_ho" class="toc">Documentation (Ho)</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#attributes1" class="toc">Attributes</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#attach_ta" class="toc">Attach (ta)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#detach_td" class="toc">Detach (td)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#show_value_tv" class="toc">Show Value (tv)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#show_name_tn" class="toc">Show Name (tn)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#show_both_tb" class="toc">Show Both (tb)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#toggle_visibility_tt" class="toc">Toggle Visibility (tt)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#find_specific_text..._t_shift-f" class="toc">Find Specific Text... (t shift-f)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#hide_specific_text..._th" class="toc">Hide Specific Text... (th)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#show_specific_text..._t_shift-h" class="toc">Show Specific Text... (t shift-h)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#autonumber_text..._tu" class="toc">Autonumber Text... (tu)</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#options" class="toc">Options</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#text_size..._ot" class="toc">Text Size... (ot)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#toggle_grid_on_off_og" class="toc">Toggle Grid On/Off (og)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#toggle_snap_on_off_os" class="toc">Toggle Snap On/Off (os)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#snap_grid_spacing..._os" class="toc">Snap Grid Spacing... (oS)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#toggle_outline_box_oa" class="toc">Toggle Outline/Box (oa)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#toggle_net_rubberband_or" class="toc">Toggle Net/Rubberband (or)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#show_log_window_ol" class="toc">Show Log Window (ol)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#show_coord_window..._oc" class="toc">Show Coord Window... (oc)</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#help" class="toc">Help</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#about..._ha" class="toc">About... (ha)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#manual..._hm" class="toc">Manual... (hm)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#hotkeys..._hh" class="toc">Hotkeys... (hh)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#component..._ho" class="toc">Component... (Ho)</a></span></div></li>
-</ul>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"><span class="li"><a href="#appendix_a_--_heavy_vs_light_symbol_libraries" class="toc">Appendix A -- Heavy vs Light Symbol Libraries</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#appendix_b_--_printing_schematics_and_symbols" class="toc">Appendix B -- Printing Schematics and Symbols</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#appendix_c_--_writing_guile_scripts" class="toc">Appendix C -- Writing guile Scripts</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#appendix_d_--_i_want_to_build_a_printed_circuit_board" class="toc">Appendix D -- I Want To Build A Printed Circuit Board</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#appendix_e_--_i_want_to_simulate_my_design" class="toc">Appendix E -- I Want To Simulate My Design</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#appendix_f_--_change_gschemdoc_user-defined_preferences" class="toc">Appendix F -- Change gschemdoc User-Defined Preferences</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#appendix_g_--_breaking_a_large_symbol_into_smaller_symbols" class="toc">Appendix G -- Breaking a Large Symbol Into Smaller Symbols</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#appendix_h_--_definition_of_terms" class="toc">Appendix H -- Definition of Terms</a></span></div></li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="guide_de_l_utilisateur_gschem_geda" id="guide_de_l_utilisateur_gschem_geda">Guide de l'utilisateur gschem gEDA</a></h1>
-<div class="level1">
-
-<p>
-by: Ales Hvezda / September 21st, 2003
-</p>
-
-<p>
-The latest version of this document may be found at: <a href="http://geda.seul.org/wiki/geda:gschem_ug"; class="urlextern" title="http://geda.seul.org/wiki/geda:gschem_ug"; rel="nofollow">http://geda.seul.org/wiki/geda:gschem_ug</a>
-</p>
-
-<p>
-This document is released under the <a href="http://geda.seul.org/wiki/geda:gfdl"; class="wikilink1" title="geda:gfdl">GNU Free Documentation License (GFDL)</a>.
-</p>
-
-<p>
- Please report any errors/inconsistencies in this document by commenting in the Discussion area at the bottom of the associated page.
-</p>
-
-</div>
-<!-- SECTION "Guide de l'utilisateur gschem gEDA" [1-409] -->
-<h1><a name="about_this_document" id="about_this_document">About this document ...</a></h1>
-<div class="level1">
-
-<p>
-gEDA gschem Users Guide
-</p>
-
-<p>
-This document was generated using the LaTeX2HTML translator Version 2002-2-1 (1.70)
-</p>
-
-<p>
-Copyright © 1993, 1994, 1995, 1996, Nikos Drakos, Computer Based Learning Unit, University of Leeds. Copyright © 1997, 1998, 1999, Ross Moore, Mathematics Department, Macquarie University, Sydney.
-</p>
-
-<p>
-The command line arguments were: latex2html -local_icons gschem
-</p>
-
-<p>
-The translation was initiated by Ales Hvezda on 2005-08-20
-</p>
-
-</div>
-<!-- SECTION "About this document ..." [410-882] -->
-<h1><a name="introduction" id="introduction">Introduction</a></h1>
-<div class="level1">
-
-<p>
-This document describes the installation, configuration, and operation of the <strong>gschem</strong> application.<br/>
- This document does not describe the process of generating schematics. For this, refer to the various tutorials on using the gEDA Tool Suite:
-</p>
-<ul>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:gschem_warmup"; class="wikilink1" title="geda:gschem_warmup">Bill Wilson's gschem warmup</a></div>
-</li>
-<li class="level1"><div class="li"> Bill Wilsonâ??s <a href="http://geda.seul.org/wiki/geda:gsch2pcb_tutorial"; class="wikilink1" title="geda:gsch2pcb_tutorial">gschem and pcb tutorial</a></div>
-</li>
-<li class="level1"><div class="li"> â??Optical Proximity Sensor for Robots (Part 1), Simple PCB Design with the gEDA Suiteâ??, by Stuart Brorson (March 2006 Circuit Cellar article)</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://www-mdp.eng.cam.ac.uk/urop05/files/gedalib/starting_gEDA.pdf"; class="urlextern" title="http://www-mdp.eng.cam.ac.uk/urop05/files/gedalib/starting_gEDA.pdf"; rel="nofollow">Starting with gEDA at the Cambridge University Engineering Department</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://www.brorson.com/gEDA/SPICE/t1.html"; class="urlextern" title="http://www.brorson.com/gEDA/SPICE/t1.html"; rel="nofollow">"Circuit simulation using gEDA and SPICE -- HOWTO" by Stuart Brorson</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://www.circuitcellar.com/magazine/176toc.htm"; class="urlextern" title="http://www.circuitcellar.com/magazine/176toc.htm"; rel="nofollow">"gEDA Design Suite for Linux" by Stuart Brorson, Ales Hvezda, & Dan McMahill (03 Mar 2005 Circuite Cellar article)</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://www.linuxjournal.com/article/8438"; class="urlextern" title="http://www.linuxjournal.com/article/8438"; rel="nofollow">"Circuit Design on Your Linux Box Using gEDA" by Stuart Brorson (29 November 2005 Linux Journal article)</a></div>
-</li>
-<li class="level1"><div class="li"> Optical Proximity Sensor for Robots (Part 1): Simple PCB Design with the gEDA Suite, by Stuart Brorson, Circuit Cellar magazine, March 2006 (Issue 188), p. 48</div>
-</li>
-<li class="level1"><div class="li"> And, of course, <a href="http://www.google.com/search?hl=en&lr=&q=gEDA+%22schematic+capture%22+tutorial&btnG=Search"; class="urlextern" title="http://www.google.com/search?hl=en&lr=&q=gEDA+%22schematic+capture%22+tutorial&btnG=Search"; rel="nofollow">Google is your friend</a>.</div>
-</li>
-</ul>
-
-<p>
- Ce document suppose que vous comprenez les bases de la capture de schéma. Par exemple: vous comprenez ce quâ??un composant représente et que les liaisons et les bus interconnectent ces composants pour former un schéma, etc… For a basic understanding of the various work-flows available in the gEDA Tool Suite, please read the above tutorials. For more detailed understanding of specific tool issues, please refer to <a href="http://geda.seul.org/wiki/docs:20060124:gschem_ug:how_to_ask_questions"; class="wikilink2" title="docs:20060124:gschem_ug:how_to_ask_questions">How To Ask Questions</a> and to the <a href="http://geda.seul.org/wiki/docs:20060124:gschem_ug:resources"; class="wikilink2" title="docs:20060124:gschem_ug:resources">Resources</a>.
-</p>
-
-</div>
-<!-- SECTION "Introduction" [883-2837] -->
-<h1><a name="overview" id="overview">Overview</a></h1>
-<div class="level1">
-
-<p>
-<strong>gschem</strong> is the schematic capture program in the gEDA Tool Suite. Its purpose is to facilitate the graphical input of:
-</p>
-<ul>
-<li class="level1"><div class="li"> circuit schematics</div>
-</li>
-<li class="level1"><div class="li"> component symbols</div>
-</li>
-<li class="level1"><div class="li"> block diagrams</div>
-</li>
-</ul>
-
-<p>
- Once <strong>gschem</strong> has been used to enter the symbols/schematics for your design, several gEDA Tool Suite â??utilityâ?? programs are used to extract information for other purposes:
-</p>
-<ul>
-<li class="level1"><div class="li"> <strong>gattrib</strong> – <strong>gattrib</strong> is a gEDA Tool Suite productivity aid. <strong>gattrib</strong> reads a [hierarchical set of] gschem schematic files and creates a spreadsheet showing all components in rows, with the associated component attributes listed in the columns. It allows the user to add, modify, or delete component attributes outside of <strong>gschem</strong>, and then save the .sch files.</div>
-</li>
-<li class="level1"><div class="li"> <strong>gnetlist</strong> – A tool that converts a [hierarchical set of] schematic files into an equivalent netlist (a textual representation of a schematic) in various formats. Various gnetlist back-ends are used to create:</div>
-<ul>
-<li class="level2"><div class="li"> Bill of Materials (BOM) files.</div>
-</li>
-<li class="level2"><div class="li"> Design Rule Checks (DRCs).</div>
-</li>
-<li class="level2"><div class="li"> Netlist files for use as input to various printed circuit board layout programs (e.g., Allegro, PADS, <strong>pcb</strong> (part of the gEDA Tool Suite), Protell, Tango, RACAL-REDAC, etc.).</div>
-</li>
-<li class="level2"><div class="li"> Files for input to SPICE simulation programs.</div>
-</li>
-<li class="level2"><div class="li"> VHDL code.</div>
-</li>
-<li class="level2"><div class="li"> Verilog code.</div>
-</li>
-<li class="level2"><div class="li"> etc.</div>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"> <strong>grenum</strong> – <strong>grenum</strong> is a gEDA Tool Suite productivity aid that will renumber the reference designators (i.e., refdes) in a [hierarchical set of] schematic files.</div>
-</li>
-<li class="level1"><div class="li"> <strong>gsch2pcb</strong> – The prefered method to create a netlist for the <strong>pcb</strong> printed circuit board layout tool (part of the gEDA Tool Suite).</div>
-</li>
-<li class="level1"><div class="li"> <strong>gspiceui</strong> – GNU Spice <acronym title="Graphical User Interface">GUI</acronym> (i.e., <strong>gspiceui</strong>) provides a <acronym title="Graphical User Interface">GUI</acronym> for freely available Spice electronic cicuit simulation engines (e.g., <strong>gnucap</strong> and <strong>ngspice</strong>). It uses <strong>gnetlist</strong> (to convert schematic files to net list files) and <strong>gwave</strong> (to display simulation results). gSchem is the preferred schematic capture tool.</div>
-</li>
-<li class="level1"><div class="li"> <strong>gsymcheck</strong> – A checker for symbols created with gEDA Tool Suite (e.g., <strong>gschem</strong>, <strong>tragesym</strong>, etc.).</div>
-</li>
-<li class="level1"><div class="li"> <strong>pcb</strong> – A tool for the layout of printed circuit boards.</div>
-</li>
-<li class="level1"><div class="li"> <strong>refdes_renum</strong> – Reads a [hierarchical set of] <strong>gschem</strong> schematic files and renumbers all reference designators. The reference designators are numbered starting with 1 and the old schematic file is replaced by the modified schematic file.</div>
-</li>
-<li class="level1"><div class="li"> <strong>tragesym</strong> – A python script that creates geda symbols from structured textfiles. The symbols usually need to be â??cleaned upâ?? in gschem.</div>
-</li>
-</ul>
-<table class="inline">
- <tr>
- <td> <a href="_detail/001geda_gschem_workflow_01.html" class="media" title="geda:gschem_workflow_01.jpg"><img src="http://geda.seul.org/wiki/_media/geda:gschem_workflow_01.jpg?w=&h=&cache=cache"; class="media" title="gschem_workflow_01.jpg" alt="gschem_workflow_01.jpg" /></a> </td>
- </tr>
-</table>
-
-</div>
-<!-- SECTION "Overview" [2838-5418] -->
-<h1><a name="resources" id="resources">Resources</a></h1>
-<div class="level1">
-
-<p>
-The following on-line resources are useful for designers using <strong>gschem</strong>:
-</p>
-<ul>
-<li class="level1"><div class="li"> <a href="http://www.geda.seul.org/docs/current/tutorials/gsch2pcb/gschem-warmup.html"; class="urlextern" title="http://www.geda.seul.org/docs/current/tutorials/gsch2pcb/gschem-warmup.html"; rel="nofollow">Bill Wilson's gschem warmup tutorial</a> – If you are new to the gEDA tools, read this before you read Billâ??s â??Bill Wilsonâ??s gsch2pcb tutorialâ??.</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:gsch2pcb_tutorial"; class="wikilink1" title="geda:gsch2pcb_tutorial">Bill Wilson's gschem and pcb tutorial</a> – If you are new to the gEDA tools, this tutorial will bring you up to speed quickly.</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://www.circuitcellar.com/"; class="urlextern" title="http://www.circuitcellar.com/"; rel="nofollow">Circuit Cellar Magazine</a> – Practical, hands-on applications and solutions for embedded designers:</div>
-<ul>
-<li class="level2"><div class="li"> gEDA Design Suite for Linux, by Stuart Brorson, Ales Hvezda, & Dan McMahill, Circuit Cellar magazine, March 2005 (Issue 176), p. 12</div>
-</li>
-<li class="level2"><div class="li"> Optical Proximity Sensor for Robots (Part 1): Simple PCB Design with the gEDA Suite, by Stuart Brorson, Circuit Cellar magazine, March 2006 (Issue 188), p. 48</div>
-</li>
-<li class="level2"><div class="li"> Optical Proximity Sensor for Robots (Part 2): Open-Source PCB Layout Editor, by Stuart Borson, Circuit Cellar magazine, April 2006 (Issue 189), p. 40</div>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"> <a href="http://www.geda.seul.org/index.html"; class="urlextern" title="http://www.geda.seul.org/index.html"; rel="nofollow">gEDA Project home page</a> – The homepage for the gEDA Tools Suite. A rather mature site, includes (but not limited to):</div>
-<ul>
-<li class="level2"><div class="li"> <a href="http://www.geda.seul.org/news/index.html"; class="urlextern" title="http://www.geda.seul.org/news/index.html"; rel="nofollow">News</a> – from 2002</div>
-</li>
-<li class="level2"><div class="li"> <a href="http://www.geda.seul.org/screenshots/index.html"; class="urlextern" title="http://www.geda.seul.org/screenshots/index.html"; rel="nofollow">Screenshots</a> – <strong>gschem</strong> in action</div>
-</li>
-<li class="level2"><div class="li"> <a href="http://www.geda.seul.org/tools/index.html"; class="urlextern" title="http://www.geda.seul.org/tools/index.html"; rel="nofollow">Tools</a> – links to project homepages</div>
-</li>
-<li class="level2"><div class="li"> <a href="http://www.geda.seul.org/download.html"; class="urlextern" title="http://www.geda.seul.org/download.html"; rel="nofollow">Download</a> – <acronym title="International Organization for Standardization">ISO</acronym> images, binaries, and sources</div>
-</li>
-<li class="level2"><div class="li"> <a href="http://www.geda.seul.org/mailinglist/index.html"; class="urlextern" title="http://www.geda.seul.org/mailinglist/index.html"; rel="nofollow">Lists</a> – e-mail list subscription and archives</div>
-</li>
-<li class="level2"><div class="li"> <a href="http://www.geda.seul.org/docs/index.html"; class="urlextern" title="http://www.geda.seul.org/docs/index.html"; rel="nofollow">Docs</a> – current gEDA/gaf documentation (not gEDA Tools Suite documentation), wiki, slide presentations</div>
-</li>
-<li class="level2"><div class="li"> <a href="http://www.geda.seul.org/developer.html"; class="urlextern" title="http://www.geda.seul.org/developer.html"; rel="nofollow">Devel</a> – nonymous <acronym title="Concurrent Versions System">CVS</acronym> access</div>
-</li>
-<li class="level2"><div class="li"> <a href="http://www.geda.seul.org/search.html"; class="urlextern" title="http://www.geda.seul.org/search.html"; rel="nofollow">Search</a> – by Google</div>
-</li>
-<li class="level2"><div class="li"> <a href="http://www.geda.seul.org/links.html"; class="urlextern" title="http://www.geda.seul.org/links.html"; rel="nofollow">Links</a> – links associated with gEDA, projects developed using gEDA Tools Suite, gEDA-related press</div>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"> <a href="http://sourceforge.net/tracker/?group_id=161080&atid=818426"; class="urlextern" title="http://sourceforge.net/tracker/?group_id=161080&atid=818426"; rel="nofollow">gEDA Bug Tracker</a> – On SourceForge</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/dokuwiki/doku.php?id=geda"; class="urlextern" title="http://geda.seul.org/dokuwiki/doku.php?id=geda"; rel="nofollow">gEDA Project's Wiki</a> – All things related to the gEDA Tools Suite.</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://www.gedasymbols.org/"; class="urlextern" title="http://www.gedasymbols.org"; rel="nofollow">gedasymbols.org</a> – On-line repository of user-developed symbols for <strong>gschem</strong>, SPICE models, and footprints for <strong>pcb</strong>.</div>
-</li>
-<li class="level1"><div class="li"> John C. Lucianiâ??s proposed <a href="http://www.luciani.org/geda/pcb/footprint-name-spec.pdf"; class="urlextern" title="http://www.luciani.org/geda/pcb/footprint-name-spec.pdf"; rel="nofollow">Land Pattern Naming Convention</a> – Footprint naming conventions document, used by him, and often used by those submitting to the <a href="http://www.gedasymbols.org/"; class="urlextern" title="http://www.gedasymbols.org"; rel="nofollow">gedasymbols.org</a> symbols/footprint repository.</div>
-</li>
-<li class="level1"><div class="li"> John C. Lucianiâ??s <a href="http://geda.seul.org/shared/HomePages/dhart/index.html"; class="urlextern" title="file:///shared/HomePages/dhart/index.html" rel="nofollow">PCB Footprints Library</a> – A rather inclusive collection of non-<acronym title="GNU General Public License">GPL</acronym> licensed footprints and the scripts used to create them.</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://www.opencollector.org/"; class="urlextern" title="http://www.opencollector.org/"; rel="nofollow">OpenCollector</a> carries listings and news for free EDA software and circuit designs. Open Collector supports gEDA.</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://alternatezone.com/electronics/files/PCBDesignTutorialRevA.pdf"; class="urlextern" title="http://alternatezone.com/electronics/files/PCBDesignTutorialRevA.pdf"; rel="nofollow">PCB Design Tutorial; RevA</a> – Document describing the process of taking a schematic to a pcb. Excellent for the beginner.</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://pcblibraries.com/"; class="urlextern" title="http://pcblibraries.com/"; rel="nofollow">PCB Libraries website</a> – Advocates of the IPC standard Land Pattern (a.k.a., footprint) Naming Conventions and Land Pattern Calculators. A useful site if you have the money to subscribe to the services.</div>
-<ul>
-<li class="level2"><div class="li"> The free (windows-based) <a href="http://landpatterns.ipc.org/default.asp"; class="urlextern" title="http://landpatterns.ipc.org/default.asp"; rel="nofollow">IPC-7351 Land Pattern Viewer</a> is a very useful tool for viewing the latest IPC footprints.</div>
-</li>
-<li class="level2"><div class="li"> <a href="http://www.pcblibraries.com/resources/LibDoc.asp"; class="urlextern" title="http://www.pcblibraries.com/resources/LibDoc.asp"; rel="nofollow">CAD Data Files to be used with PCB Libraries' IPC-7351A LP Programs</a> – please note the license restrictions.</div>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"> <a href="http://www-mdp.eng.cam.ac.uk/urop05/files/gedalib/starting_gEDA.pdf"; class="urlextern" title="http://www-mdp.eng.cam.ac.uk/urop05/files/gedalib/starting_gEDA.pdf"; rel="nofollow">Starting with gEDA at the Cambridge University Engineering Department</a> – The Cambridge University Engineering Departmentâ??s tutorial for using gEDA.</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://www.brorson.com/gEDA/"; class="urlextern" title="http://www.brorson.com/gEDA/"; rel="nofollow">Stuart Brorson's gEDA tools and tips</a> – gEDA related tools and information.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Resources" [5419-9678] -->
-<h1><a name="how_to_ask_questions" id="how_to_ask_questions">How To Ask Questions</a></h1>
-<div class="level1">
-
-<p>
-<strong>gschem</strong> is an OpenSource, community driven, development. As such, the emphasis has been on developing the gEDA Tools Suite, not on developing commercial-level documentation and support. Much of the burden on learning how to use the gEDA Tools Suite applications is placed on the user, who must understand the basics of electronics, Electronics Design Automation (EDA), and the terminology used in schematic capture, circuit simulation, and printed circuit board design.<br/>
- As a typical OpenSource development, the gEDA Tools Suite development community provides timely and insightful response to user inquiries, but please perform the following steps before bothering the developers (they need to focus on making gEDA Tools Suite applications better, and you can actually learn to answer your own questions and become independent of the developers):
-</p>
-<ol>
-<li class="level1"><div class="li"> Read Rick Moenâ??s <a href="http://www.catb.org/~esr/faqs/smart-questions.html"; class="urlextern" title="http://www.catb.org/~esr/faqs/smart-questions.html"; rel="nofollow">How To Ask Questions The Smart Way</a>, about how to ask for help. This is a must read for everybody.</div>
-</li>
-<li class="level1"><div class="li"> Read this document. I know, itâ??s a lot to expect engineers to actually read a userâ??s guide. The latest version of this document is maintained on the gEDA web-site at <span class="hilited">TBD</span>. The information should be here. If it isnâ??t, comment to the fact in one of the on-line documentâ??s â??Discussionâ?? areas (at the bottom of each wiki-page). Helpful comments are clear, to the point, and may even contain the wording that should be inserted into the document.</div>
-</li>
-<li class="level1"><div class="li"> Read the <a href="http://geda.seul.org/dokuwiki/doku.php?id=geda:faq-gschem"; class="urlextern" title="http://geda.seul.org/dokuwiki/doku.php?id=geda:faq-gschem"; rel="nofollow">gschem Frequently Asked Questions (FAQ)</a> wiki-page. This on-line document is updated often to reflect user and developer experiences with <strong>gschem</strong>.</div>
-</li>
-<li class="level1"><div class="li"> Read the <a href="http://www.geda.seul.org/docs/current/index.html"; class="urlextern" title="http://www.geda.seul.org/docs/current/index.html"; rel="nofollow">gEDA/gaf Documentation</a>. This information was installed on your computer if the gEDA Tools Suite was installed from the gEDA Tools Suite CD-ROM.</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://www.google.com/"; class="urlextern" title="http://www.google.com"; rel="nofollow">Google</a> is your friend. People that have asked questions that obviously didnâ??t do any simple Google search will not be treated well when asking for help. This is particularly true if your problem is not unique to the gEDA Tools Suite applications.</div>
-</li>
-<li class="level1"><div class="li"> Ask for a pointer to the right direction. It is considered good â??net etiquetteâ?? to ask for a pointer to information, so that you can learn where such information can be found, rather than have someone search the information for you.</div>
-</li>
-<li class="level1"><div class="li"> If you are software literate, look at the source code to see what it is doing.</div>
-</li>
-<li class="level1"><div class="li"> Subscribe to the gEDA e-mail lists (i.e., you can only post to the e-mail lists if you are a subscriber). Then:</div>
-<ol>
-<li class="level2"><div class="li"> Start reading recent messages in the <a href="http://archives.seul.org/geda/user/"; class="urlextern" title="http://archives.seul.org/geda/user/"; rel="nofollow">geda-user e-mail list archives</a>. Get a feel for the listâ??s ettiquite so that you learn how to properly ask questions.</div>
-</li>
-<li class="level2"><div class="li"> Search the archives for issues similar to yours. You may find the question has been asked of the developers and users before, and answered.</div>
-</li>
-<li class="level2"><div class="li"> In the event that you can find no information concerning your problem, submit a concise description of the problem and a request for the type of help you are requesting.</div>
-</li>
-</ol>
-</li>
-</ol>
-
-</div>
-<!-- SECTION "How To Ask Questions" [9679-12860] -->
-<h1><a name="installing_gschem" id="installing_gschem">Installing gschem</a></h1>
-<div class="level1">
-
-<p>
-As a mature OpenSource project, the gEDA Tools Suite and its components have been installed on many Linux distributions. The following are by no means the only methods of installing the gEDA Tools Suite and/or its components.
-</p>
-
-</div>
-<!-- SECTION "Installing gschem" [12861-13119] -->
-<h2><a name="latest_stable" id="latest_stable">Latest Stable</a></h2>
-<div class="level2">
-
-<p>
-<strong>gschem</strong> is a component of the gEDA/gaf set of tools which tend to integrate together in the development and maintenance of schematics and symbols. The term â??gafâ?? stands for â??<em class="u">g</em>EDA <em class="u">a</em>nd <em class="u">f</em>riendsâ??). The gEDA/gaf applications are actually rather stable, and receive significant testing prior to release.<br/>
- There are multiple methods of installing <strong>gschem</strong>. The appropriate method depends on your distribution. See the following for some examples.
-</p>
-
-</div>
-<!-- SECTION "Latest Stable" [13120-13604] -->
-<h3><a name="geda_tools_suite_cd-rom" id="geda_tools_suite_cd-rom">"gEDA Tools Suite" CD-ROM</a></h3>
-<div class="level3">
-
-<p>
-The recommended method is installation from the â??gEDA Tools Suiteâ?? CD-ROM, gratefully prepared by Stuart Brorson. The latest version of this CD-ROM is available on-line for free download as an <acronym title="International Organization for Standardization">ISO</acronym> image from the <a href="http://www.geda.seul.org/download.html"; class="urlextern" title="http://www.geda.seul.org/download.html"; rel="nofollow">gEDA Downloads</a> web-page. Simply burn this <acronym title="International Organization for Standardization">ISO</acronym> image to a CD-ROM using your favorite CD burning software (e.g., K3b, …). Insert the CD-ROM, and if your computer supports autodetection of the CD-ROM, the built-in installation wizzard will launch. This wizzard will first check if your computer has some required software (informing you if you donâ??t and optionally installing these if you want), then build all of the â??gEDA Tool Suiteâ?? applications (including <strong>gschem</strong>) from source. The whole process can take 2 hours on a slower computer.
-</p>
-
-<p>
-If the installation wizzard did not launch, enter as follows to install the gEDA Tool Suite for access by all users on this computer (i.e., when prompted for the installation directory, enter something like: â??/usr/local/gEDA-20060124â??): <pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0"><strong>sudo sh /media/cdrecorder/installer –log –verbose</strong></font></pre>
-</p>
-
-<p>
-The above command requires superuser permissions configured for the user invoking the command. If you do not have the proper permissions to execute this command, ask your administrator to install the gEDA Tool Suite for you.
-</p>
-
-<p>
-If the installation wizzard did not launch, enter as follows to install the gEDA Tool Suite for access by just the user doing the installation(i.e., when prompted for the installation directory, accept the default "/home/{login id}/geda-installâ??): <pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0"><strong>sh /media/cdrecorder/installer –log –verbose</strong></font></pre>
-</p>
-
-</div>
-<!-- SECTION "gEDA Tools Suite CD-ROM" [13605-15291] -->
-<h3><a name="debian_distributions" id="debian_distributions">Debian distributions</a></h3>
-<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.
-</p>
-
-</div>
-<!-- SECTION "Debian distributions" [15292-15640] -->
-<h3><a name="red_hat_distributions" id="red_hat_distributions">Red Hat distributions</a></h3>
-<div class="level3">
-
-<p>
-For Red Hat distributions (and possibly others) you may wish to download the latest RPM binaries]] prepared by Wojciech Kazubski.
-</p>
-
-</div>
-<!-- SECTION "Red Hat distributions" [15641-15803] -->
-<h3><a name="mac_osx_distributions" id="mac_osx_distributions">Mac OSX distributions</a></h3>
-<div class="level3">
-
-<p>
-For Mac OSX 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 Fink binaries</a> prepared by Charles Lepple.
-</p>
-
-</div>
-<!-- SECTION "Mac OSX distributions" [15804-15983] -->
-<h2><a name="cvs_unstable_testing" id="cvs_unstable_testing">CVS Unstable/Testing</a></h2>
-<div class="level2">
-
-<p>
-For those already familiar with the gEDA/gaf applications on the â??gEDA Tools Suiteâ?? CD-ROM, access to the <acronym title="Concurrent Versions System">CVS</acronym> repository is available. This is the latest developer source-code version of the application.<br/>
- Installation from <acronym title="Concurrent Versions System">CVS</acronym> is appropriate for those:
-</p>
-<ul>
-<li class="level1"><div class="li"> Seeking a solution to a specific problem that was submitted to the development team, to test the â??fixâ?? so that the developers can be informed that the â??fixâ?? works.</div>
-</li>
-<li class="level1"><div class="li"> With significant working knowledge of the â??gEDA Tools Suiteâ?? and industry expertise, wishing to test the latest version of the application(s) prior to the next release. This usually requires access to several existing designs known to work in the current stable release of the â??gEDA Tools Suiteâ?? <acronym title="International Organization for Standardization">ISO</acronym> image, so that comparisons can be made and issues brought to the attention of the developer/user community (via the e-mail lists).</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "CVS Unstable/Testing" [15984-16874] -->
-<h1><a name="configuring_gschem" id="configuring_gschem">Configuring gschem</a></h1>
-<div class="level1">
-
-<p>
-Assume that you have installed the gEDA Tools Suite from CD-ROM (the most common installation method), and that you are ready to configure <strong>gschem</strong> to your personal likes. When installing, you were prompted for the path where the gEDA executables would be placed. The default was the <strong>/home/{login id}/geda-install</strong> directory, where {login id} is the username you logged into your account with, but you may have changed this to another directory on the computer. This directory is referred to below as the <strong>{binary-install-path}</strong> because this is where the gEDA binary executables are placed. If you forgot where the binaries were installed, simply issue the following command to find where <strong>gschem</strong> is installed (in this case the {binary-install-path} is <strong>/usr/local/gEDA-20060124</strong>): <pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">% which gschem
-/usr/local/gEDA-20060124/bin/gschem
-%</font></pre>
-</p>
-
-<p>
-The gEDA Tools Suite applications follow normal Unix/Linux conventions for placement of configuration files; there are usually system-wide, user-wide, and project-specific configuration settings. The system-wide settings are placed in a sub-directory of the {binary-install-path}. The user-wide settings are placed in the userâ??s home directory, also known as the login directory (referred to in Unix/Linux parlance as the <strong>$HOME</strong> directory). The project-specific settings are placed in a project-specific directory.<br/>
-
-</p>
-
-<p>
-Now that we know the above, we can configure <strong>gschem</strong>.<br/>
- <strong>gschem</strong> is highly configurable. All configuration is handled through the following resource files (written using the GNU Guile programming language, an interpreter for Scheme, a version of Lisp):
-</p>
-<ul>
-<li class="level1"><div class="li"> <strong>system-gschemrc</strong>: The system-wide initialization file for <strong>gschem</strong>. Installed in the {binary-install-path}/share/gEDA/system-gschemrc file, it is required for <strong>gschem</strong> to run. Users should not modify this file, but should override the settings in this file by creating their own $HOME/gschemrc file and/or â??pwdâ??/gschemrc file and putting the new settings in those files. The {binary-install-path} directory is where your gEDA/gaf executables were installed, including <strong>gschem</strong>. Depends on your install method. Refer to <a href="http://geda.seul.org/wiki/docs:20060124:gschem_ug:installing_gschem"; class="wikilink2" title="docs:20060124:gschem_ug:installing_gschem">Installing gschem</a> for more details.</div>
-</li>
-<li class="level1"><div class="li"> <strong>$HOME/gschemrc</strong>: The per-user initialization file for <strong>gschem</strong>. Created by the user in the userâ??s home directory. Settings placed in this file will override settings in the system-gschemrc file. Users should put settings in this file they want to apply to all of their sessions, such as (to change the default black background color scheme to a light background color scheme):</div>
-</li>
-</ul>
-
-<p>
-<pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">; Load up a color scheme
-(load (string-append gedadatarc "/gschem-lightbg")) ; light background</font></pre>
-</p>
-<ul>
-<li class="level1"><div class="li"> <strong>â??pwdâ??/gschemrc</strong>: The per-project initialization file for <strong>gschem</strong>. Created by the user in the userâ??s project directory. Settings placed in this file will override settings in both the system-gschemrc file and the $HOME/gschemrc file. Users should put settings in this file they want to apply to this particular project, such as (to autonumber reference designators when components are placed on the schematic):</div>
-</li>
-</ul>
-
-<p>
-<pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">; Comment in this scheme code if you want automatic numbering when
-; placing new component and copying components
-;
-(load (string-append gedadata "/scheme/auto-uref.scm"))
-(add-hook! add-component-hook auto-uref)</font></pre>
-</p>
-<ul>
-<li class="level1"><div class="li"> <strong>system-gafrc</strong>: The system-wide initialization file for gEDA/gaf applications (includes <strong>gschem</strong>, <strong>gnetlist</strong>). Installed in the {binary-install-path}/share/gEDA/system-gafrc file, it is required for <strong>gschem</strong> to run. Users should not modify this file, but should override the settings in this file by creating their own $HOME/gafrc file and/or â??pwdâ??/gafrc file and putting the new settings in those files. The {binary-install-path} directory is where your gEDA/gaf executables were installed, including <strong>gschem</strong>. Depends on your install method. Refer to <a href="http://geda.seul.org/wiki/docs:20060124:gschem_ug:installing_gschem"; class="wikilink2" title="docs:20060124:gschem_ug:installing_gschem">Installing gschem</a> for more details.</div>
-</li>
-<li class="level1"><div class="li"> <strong>$HOME/gafrc</strong>: The per-user initialization file for gEDA/gaf applications. Created by the user in the userâ??s home directory. Settings placed in this file will override settings in the system-gafrc file. Users should put settings in this file they want to apply to all of their sessions. </div>
-</li>
-<li class="level1"><div class="li"> <strong>â??pwdâ??/gafrc</strong>: The per-project initialization file for the gEDA/gaf applications. Created by the user in the userâ??s project directory. Settings placed in this file will override settings in both the system-gafrc file and the $HOME/gafrc file. Users should put settings in this file they want to apply to this particular project. Settings such as the <strong>component-library</strong> or <strong>source-library</strong> keywords go into this file.</div>
-</li>
-<li class="level1"><div class="li"> <strong>gschem-gtkrc</strong>: Installed in the {binary-install-path}/share/gEDA/gschem-gtkrc file. Used to define the font for all gtk+ widgets in <strong>gschem</strong>.</div>
-</li>
-</ul>
-
-<p>
- A few comments about changing the files:
-</p>
-<ul>
-<li class="level1"><div class="li"> Donâ??t break any guile syntax rules. Doing so will cause the scheme interpreter (guile) to stop interpreting.</div>
-</li>
-<li class="level1"><div class="li"> To add a setting to the $HOME/gschemrc file (or to the â??pwdâ??/gschemrc file), copy the settingâ??s text from the {binary-install-directory}/share/gEDA/system-gschemrc file to the $HOME/gschemrc file (or the â??pwdâ??/gschemrc file) and make the setting change there.</div>
-</li>
-<li class="level1"><div class="li"> To add a setting to the $HOME/gafrc file (or the â??pwdâ??/gafrc file), copy the relevant settingâ??s text from the {binary-install-directory}/share/gEDA/system-gafrc file to the $HOME/gafrc file (or the â??pwdâ??/gafrc file) and make the setting change there.</div>
-</li>
-<li class="level1"><div class="li"> Keywords/defaults always override what came before, with the exception of cumulative keywords (like component-library).</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Configuring gschem" [16875-22595] -->
-<h2><a name="gschemrc" id="gschemrc">gschemrc</a></h2>
-<div class="level2">
-
-<p>
-The {binary-install-path}/share/gEDA/system-gschemrc file is well commented. Read this file for more details on the settings available.<br/>
- Some of the settings appropriate for override (by placing in either the userâ??s $HOME/gschemrc file or the projectâ??s â??pwdâ??/gschemrc file) are:
-</p>
-
-</div>
-<!-- SECTION "gschemrc" [22596-22897] -->
-<h2><a name="gafrc" id="gafrc">gafrc</a></h2>
-<div class="level2">
-
-<p>
-The {binary-install-path}/share/gEDA/system-gafrc file is well commented. Read this file for more details on the settings available.<br/>
- Some of the settings appropriate for override (by placing in either the userâ??s $HOME/gafrc file or the projectâ??s â??pwdâ??/gafrc file) are:
-</p>
-
-</div>
-<!-- SECTION "gafrc" [22898-23187] -->
-<h1><a name="lancer_gschem" id="lancer_gschem">Lancer gschem</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "Lancer gschem" [23188-23216] -->
-<h2><a name="confirming_gschem_is_installed" id="confirming_gschem_is_installed">Confirming gschem is installed</a></h2>
-<div class="level2">
-
-<p>
-You should determine if <strong>gschem</strong> has been correctly installed on your Linux computer.<br/>
- Log into your Linux account, and launch your favorite interactive shell. The different Linux distributions will usually offer more than one interactive shell such as xterm, gnome-term, konsole, etc.<br/>
- You will see a shell prompt, which will depend on your Linux distribution and on your selection of interactive shell. It is common practice in Linux documentation to refer to the userâ??s interactive login shell prompt as â??<strong>%</strong>â??, and to refer to the superuserâ??s (i.e., user â??rootâ??) interactive login shell prompt as â??<strong>#</strong>â??.<br/>
- At the shell prompt, enter the following commands to determine if <strong>gschem</strong> is installed:
-</p>
-
-<p>
-<pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">% <strong>echo $PATH</strong>
-<strong>/usr/local/gEDA-20060124/bin</strong>:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/home/<strong>gEDA</strong>/bin
-% <strong>which gschem</strong>
-/usr/local/gEDA-20060124/bin/gschem
-% <strong>ldd /usr/local/gEDA-20060124/bin/gschem</strong>
- linux-gate.so.1 => (0x00345000)
- libgeda.so.25 => /usr/local/gEDA-20060124/lib/libgeda.so.25 (0x00d7d000)
- libguile.so.12 => /usr/lib/libguile.so.12 (0x00588000)
- libguile-ltdl.so.1 => /usr/lib/libguile-ltdl.so.1 (0x00b62000)
- libqthreads.so.12 => /usr/lib/libqthreads.so.12 (0x009f7000)
- libpthread.so.0 => /lib/libpthread.so.0 (0x006d4000)
- libcrypt.so.1 => /lib/libcrypt.so.1 (0x03266000)
- libgdk-x11-2.0.so.0 => /usr/lib/libgdk-x11-2.0.so.0 (0x00c10000)
- libgdk_pixbuf-2.0.so.0 => /usr/lib/libgdk_pixbuf-2.0.so.0 (0x006ac000)
- libm.so.6 => /lib/libm.so.6 (0x008df000)
- libpangoxft-1.0.so.0 => /usr/lib/libpangoxft-1.0.so.0 (0x003e7000)
- libpangox-1.0.so.0 => /usr/lib/libpangox-1.0.so.0 (0x00a57000)
- libpango-1.0.so.0 => /usr/lib/libpango-1.0.so.0 (0x00bd8000)
- libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0x00a01000)
- libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0x009fb000)
- libdl.so.2 => /lib/libdl.so.2 (0x00906000)
- libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x0448e000)
- libgtk-x11-2.0.so.0 => /usr/lib/libgtk-x11-2.0.so.0 (0x06a81000)
- libatk-1.0.so.0 => /usr/lib/libatk-1.0.so.0 (0x00c96000)
- libSM.so.6 => /usr/X11R6/lib/libSM.so.6 (0x00d4f000)
- libICE.so.6 => /usr/X11R6/lib/libICE.so.6 (0x00d33000)
- libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00921000)
- libc.so.6 => /lib/libc.so.6 (0x007b4000)
- /lib/ld-linux.so.2 (0x00796000)
- libXrandr.so.2 => /usr/X11R6/lib/libXrandr.so.2 (0x00bac000)
- libXi.so.6 => /usr/X11R6/lib/libXi.so.6 (0x00cca000)
- libXinerama.so.1 => /usr/X11R6/lib/libXinerama.so.1 (0x00bb2000)
- libXft.so.2 => /usr/X11R6/lib/libXft.so.2 (0x00ad1000)
- libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x00af8000)
- libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0x00111000)
- libXfixes.so.3 => /usr/X11R6/lib/libXfixes.so.3 (0x00d0d000)
- libXcursor.so.1 => /usr/X11R6/lib/libXcursor.so.1 (0x00bcc000)
- libXrender.so.1 => /usr/X11R6/lib/libXrender.so.1 (0x00ba2000)
- libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x00a82000)
- libpangoft2-1.0.so.0 => /usr/lib/libpangoft2-1.0.so.0 (0x05362000)
- libexpat.so.0 => /usr/lib/libexpat.so.0 (0x0068b000)
- libz.so.1 => /usr/lib/libz.so.1 (0x0090c000)</font></pre>
-</p>
-
-<p>
-The <strong>echo $PATH</strong> command displays the userâ??s current setting for the <strong>PATH</strong> environment variable. In the above example for a Fedora Core 4 installation, user <strong>gEDA</strong> executed the command and determined that the <strong>PATH</strong> included the /usr/local/gEDA-20060124/bin directory (this will differ depending on where you put the gEDA Tools Suite executables). If you installed from the gEDA Tools Suite CD-ROM (the most common method of installing the gEDA tools), as the last step of the installation wizzard you were prompted to:
-</p>
-<ol>
-<li class="level1"><div class="li"> Set your $PATH environment variable to {the directory in which the install wizzard installed gEDAâ??s executables}</div>
-</li>
-<li class="level1"><div class="li"> Set your $LD_LIBRARY_PATH environment variable to {the directory in which the install wizzard installed gEDAâ??s libraries}</div>
-</li>
-</ol>
-
-<p>
- The <strong>which</strong> command displays the full path of a commandâ??s executable, searching for the command on the userâ??s list of directories, as defined in the <strong>PATH</strong> environment variable. In this case, it will return the full path to the <strong>gschem</strong> executable if it is on the userâ??s <strong>PATH</strong>. If this command does not return the full path to the <strong>gschem</strong> executable, make sure your <strong>PATH</strong> environment variable has been properly set.
-</p>
-
-<p>
-The <strong>ldd</strong> command displays shared libraries required by a program. All of the requested libraries must be found for <strong>gschem</strong> to run. Donâ??t be intimidated by the long list of libraries, this is common for mature Linux applications. If we had not received this output (or something very similar), we would have to check on our setting for the <strong>LD_LIBRARY_PATH</strong> environment variable.
-</p>
-
-<p>
-And of course, there is always attempting to just run <strong>gschem</strong> as follows: <pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">% <strong>gschem -h</strong>
-Usage: gschem [OPTIONS] schematic_filename1 ... schematic_filenameN
- -q Quiet mode
- -v Verbose mode on
- -r filename Rc filename
- -s filename Script (guile) filename
- -o filename Output filename (for printing)
- -p Automatically place the window
- -t Print stroke information
- -h Help; this message</font></pre>
-</p>
-
-<p>
-where we displayed the <strong>gschem</strong> help.
-</p>
-
-<p>
-If these commands do not return the expected results, then most likely the gEDA tools are not installed properly. Please see the appropriate INSTALL docs (which came with the gEDA distribution) for more info on installing the gEDA tools. If you installed from the gEDA Tools Suite CD-ROM, read the INSTALL document on the CD-ROM first.<br/>
-
-</p>
-
-</div>
-<!-- SECTION "Confirming gschem is installed" [23217-28922] -->
-<h2><a name="the_shell_prompt" id="the_shell_prompt">The Shell Prompt</a></h2>
-<div class="level2">
-<table class="inline">
- <tr>
- <td> <a href="_detail/001geda_terminal_screenshot_001.html" class="media" title="geda:terminal_screenshot_001.jpg"><img src="http://geda.seul.org/wiki/_media/geda:terminal_screenshot_001.jpg?w=&h=&cache=cache"; class="media" title="terminal_screenshot_001.jpg" alt="terminal_screenshot_001.jpg" /></a> </td>
- </tr>
- <tr>
- <td> Figure 1 – gnome-terminal </td>
- </tr>
-</table>
-
-<p>
- You launch <strong>gschem</strong> from your favorite shell prompt (in this case, gnome-terminal on Fedora Core 4).<br/>
- There are several command-line switches:
-</p>
-<ul>
-<li class="level1"><div class="li"> <strong>-q</strong> – Quiet mode<br/>
- Turns on â??quiet modeâ??. Output (i.e., stdout and stderr) is not generated to the shell. Useful if calling <strong>gschem</strong> from a script (e.g., bash, sh, csh, etc.) to perform batch operations such as printing a large number of schematics or symbols.</div>
-</li>
-<li class="level1"><div class="li"> <strong>-v</strong> – Verbose mode ON<br/>
- Generate verbose information. Not used very much in <strong>gschem</strong>.</div>
-</li>
-<li class="level1"><div class="li"> <strong>-r filename</strong> – Process additional configuration settings from <strong>filename</strong><br/>
- <strong>filename</strong> is a file containing settings of the form found in either system-gschemrc or system-gafrc<br/>
- In addition to the following files, <strong>gschem</strong> will process <strong>filename</strong> for additional configuration settings:<br/>
- * {binary-install-path}/share/gEDA/system-gschemrc<br/>
- * $HOME/gschemrc<br/>
- * â??pwdâ??/gschemrc<br/>
- * {binary-install-path}/share/gEDA/system-gafrc<br/>
- * $HOME/gafrc<br/>
- * â??pwdâ??/gafrc</div>
-</li>
-<li class="level1"><div class="li"> <strong>-s filename</strong> – Process <strong>filename</strong> as a guile script<br/>
- The name of a script file (written in guile) for <strong>gschem</strong> to process.<br/>
- Refer to <a href="http://geda.seul.org/wiki/docs:20060124:gschem_ug:app_b"; class="wikilink2" title="docs:20060124:gschem_ug:app_b">Appendix B -- Printing Schematics and Symbols</a> and <a href="http://geda.seul.org/wiki/docs:20060124:gschem_ug:app_c"; class="wikilink2" title="docs:20060124:gschem_ug:app_c">Appendix C -- Writing guile Scripts</a> for more details.<br/>
- For example, in your $HOME/geda-sources/gedagaf/{gEDA Tools Suite version}/scripts/ directory is the <strong>print.scm</strong> file, a template script file directing <strong>gschem</strong> to generate a PostScript file of a schematic appropriate for printing. This <strong>print.scm</strong> file works as is, but you may want to customize it for your own needs. To print the schematic_1.sch schematic to the schematic_1.ps PostScript file from within a bash script, you would enter: <code>gschem -q -p -o schematic_1.ps -s print.scm schematic_1.sch</code><br/>
- Then, simply use your favorite printing solution to print the file, such as: <code>lp schematic_1.ps</code><br/>
- to a PostScript printer.</div>
-</li>
-<li class="level1"><div class="li"> <strong>-o filename</strong> – Output <strong>filename</strong> (e.g., for printing)<br/>
- Specify the output filename. For example, as used to specify the Postscript filename in the example above.</div>
-</li>
-<li class="level1"><div class="li"> <strong>-p</strong> – Automatically place the window<br/>
- Donâ??t wait for the windowmanager to place the window.<br/>
- When a new window is opened, some window managers display the bounding box of the window and wait for the user to place the window manually. The "-pâ?? option avoids that, letting the window manager decide where to put the new window.</div>
-</li>
-<li class="level1"><div class="li"> <strong>-t</strong> – Print stroke information<br/>
- </div>
-</li>
-<li class="level1"><div class="li"> <strong>-h</strong> – Help<br/>
- Generate a short usage printout.</div>
-</li>
-</ul>
-
-<p>
- Running <strong>gschem</strong> is straightforward once you have installed it on your GNU/Linux system.<br/>
- Although <strong>gschem</strong> is a <acronym title="Graphical User Interface">GUI</acronym> application, <strong>gschem</strong> is meant to be launched from the command-line, as it takes command-line arguements (see Figure 1 above).<br/>
- To open an empty schematic, run: <code><strong>% gschem</strong></code><br/>
-
-</p>
-
-<p>
-To open a specific schematic, run: <code><strong>% gschem schematic_name.sch</strong></code><br/>
-
-</p>
-
-<p>
-To open a list of schematics, run: <code><strong>% gschem schematic_1.sch schematic_2.sch, schematic_3.sch …</strong></code><br/>
- or use wildcards to specify multiple filenames: <code><strong>% gschem schematic_*.sch</strong></code>
-</p>
-
-<p>
-As operations are performed in the <strong>gschem</strong> <a href="http://geda.seul.org/wiki/docs:20060124:gschem_ug:the_main_window"; class="wikilink2" title="docs:20060124:gschem_ug:the_main_window">Main Window</a> the <strong>gschem</strong> <a href="http://geda.seul.org/wiki/docs:20060124:gschem_ug:the_status_window"; class="wikilink2" title="docs:20060124:gschem_ug:the_status_window">Status Window</a> continues to output information, and the shell promptâ??s window continues to output information, consisting of:
-</p>
-<ul>
-<li class="level1"><div class="li"> …</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "The Shell Prompt" [28923-32457] -->
-<h2><a name="backups" id="backups">Backups</a></h2>
-<div class="level2">
-
-<p>
-There are two basic mechanisms in <strong>gschem</strong> for backing up schematics and symbols, classic Linux backups and incremental backups.
-</p>
-
-</div>
-<!-- SECTION "Backups" [32458-32609] -->
-<h3><a name="classic_linux_backups" id="classic_linux_backups">Classic Linux backups</a></h3>
-<div class="level3">
-
-<p>
-While creating and/or editing schematic file(s) or symbol file(s), snapshots are triggered by the <strong>autosave</strong> interval setting in the {binary-install-path}/share/gEDA/system-gschemrc file (see <a href="#relevant_configuration_settings" title="geda:gschem_ug.fr ↵" class="wikilink1">Relevant configuration settings</a> below). If the file has not been manually saved, and the interval expires (current default 2 minutes), the snapshot is saved the next time a change is made in the <strong>gschem</strong> main window (to either a schematic or to a symbol). The interval timer starts again as soon as the snapshot file(s) have been written, and once the timer expires the next change to the main window will trigger the snapshot to be written.<br/>
- This snapshot includes all work up to, but not including, the last operation performed in the <strong>gschem</strong> main window. This is to allow for easier recovery from a crash that may have been caused by the last operation.<br/>
- When <strong>gschem</strong> exits normally, the snapshot file(s) are deleted. So, if <strong>gschem</strong> were to crash, or not terminate normally for some reason (e.g., power failure, soda → keyboard, etc.), the shapshot file(s) would be found the next time <strong>gschem</strong> opened the file(s). <strong>gschem</strong> will display the following warning message when it finds a snapshot file associated with the schematic file(s) or symbol file(s) it opens: <pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">WARNING: Found and autosave backup file:
- {full path to autosave file}
-
-The backup copy is newer than the schematic, so it seems you
-should load it instead of the original fil.
-Gschem usually makes backup copies automatically, and this
-situation happens when it crashed or it was forced to exit
-abruptely.
-
-If you load the original file, the backup file will be overwritten in
-the next autosave timeout and it will be lost.
-
-Do you want to load the backup file?</font></pre>
-</p>
-
-<p>
-The snapshots are saved to a file whose filename is constructed from the original filename (schematic or symbol) as follows:
-</p>
-<ul>
-<li class="level1"><div class="li"> add a "#" to the beginning of the original filename</div>
-</li>
-<li class="level1"><div class="li"> add a "#" to the end</div>
-</li>
-</ul>
-
-<p>
- so that:
-</p>
-<ul>
-<li class="level1"><div class="li"> â??schematic_1.schâ?? becomes "#schematic_1.sch#"</div>
-</li>
-<li class="level1"><div class="li"> â??symbol.symâ?? becomes "#symbol.sym#"</div>
-</li>
-</ul>
-
-<p>
- And yes, the "#" at the front and back of the filename are part of the filename.<br/>
-
-</p>
-
-<p>
-When the user does finally manually save the file, the original file (i.e., the file that was opened) is renamed to "{filename~}" and the latest snapshot file (i.e., "#{filename}#") gets copied as "{filename}". Note that this new "{filename}" file may not contain the latest information as displayed on the <strong>gschem</strong> main window, as the <strong>autosave</strong> interval timer may not have expired since the last change to the schematic/symbol.<br/>
- When the user finally decides to close <strong>gschem</strong>, the latest snapshot file (i.e., "#{filename}#") is saved to the original file (i.e., "{filename}".<br/>
- When you exit <strong>gschem</strong> and are prompted to save any unsaved schematic file(s) or symbol file(s), this constitutes a manual save.
-</p>
-
-</div>
-<!-- SECTION "Classic Linux backups" [32610-35516] -->
-<h3><a name="incremental_backups" id="incremental_backups">Incremental backups</a></h3>
-<div class="level3">
-
-</div>
-<!-- SECTION "Incremental backups" [35517-35550] -->
-<h3><a name="relevant_configuration_settings" id="relevant_configuration_settings">Relevant configuration settings</a></h3>
-<div class="level3">
-
-<p>
-There are the following configuration settings in the {binary-install-path}/share/gEDA/system-gschemrc file that effect backups:
-</p>
-<ul>
-<li class="level1"><div class="li"> <strong>undo-control</strong> : Controls if the undo feature is enabled or not.</div>
-</li>
-<li class="level1"><div class="li"> <strong>undo-levels</strong> : Determines the number of levels of undo. Basically this number decides how many backup schematics are saved.</div>
-</li>
-<li class="level1"><div class="li"> <strong>undo-type</strong> : Controls which kind of undo is used, disk or memory. The default is to use the disk as the storage medium (i.e., after every action the undo information is stored to a new file on disk). The disk mechanism is nice because you get that many backups of the schematic, written to disk as backups, so you should never lose a schematic due to a crash.</div>
-</li>
-<li class="level1"><div class="li"> <strong>autosave</strong> : Controls if a backup copy is made every â??intervalâ?? seconds. Note that a backup copy is only made when you make some change to the schematic, and there were more than â??intervalâ?? seconds from the last autosave. Autosaving will not be allowed if the â??intervalâ?? setting is set to zero.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Relevant configuration settings" [35551-36592] -->
-<h2><a name="on-line_documentation" id="on-line_documentation">On-line documentation</a></h2>
-<div class="level2">
-
-<p>
-For a listing of the various command line flags run â??<strong>gschem -h</strong>â??: <pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">% <strong>gschem -h</strong>
-Usage: gschem [OPTIONS] schematic_filename1 ... schematic_filenameN
- -q Quiet mode
- -v Verbose mode on
- -r filename Rc filename
- -s filename Script (guile) filename
- -o filename Output filename (for printing)
- -p Automatically place the window
- -t Print stroke information
- -h Help; this message</font></pre>
-</p>
-
-<p>
-For a detailed explanation of the command line flags look at the <strong>gschem</strong> man page: <pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">% <strong>man gschem</strong>
-gschem(1) 20031231 gschem(1)
-
-
-
-NAME
- gschem - gEDA/gaf Schematic Capture
-
-SYNOPSIS
- gschem [-q] [-v] [-t] [-r rcfilename] [-s scriptfilename] [-o output-
- filename] [-p] [schematic1 ... schematicN]
-
-DESCRIPTION
- gschem is the schematic capture program which is part gEDA (GPL Elec-
- tronic Design Automation) toolset. This program is used to draw elec-
- tronic schematics. Schematics consist of standard symbols (which are
- either part of a standard library or created by the user) which repre-
- sent the various gates and components. These components are then
- interconnected by nets (wires). Schematics may be printed to a
- PostScript file for printing or further conversion to other output for-
- mats.
-
- gschem is also the symbol creation editor. All the standard methods of
- creating schematics are used in the creation of symbols. There are a
- few special rules when creating symbols, so please refer to the (non-
- existant as of now) symbol creation document.
-
- Please read the official documentation (very minimal at this point) on
- how to use gschem, since this man page just describes the command line
- arguments and a few examples on how to run gschem.
-
-
-OPTIONS
- gschem accepts the following options:
-
- -q Quiet mode on. This mode turns off all warnings/notes/mes-
- sages. (optional)
-
- -v Verbose mode on. This mode gives as much feedback to the user
- as possible. (optional)
-
- -t Print out more information when using mouse strokes. With this
- command line flag and the middle button configured for mouse
- strokes, gschem will output the stroke sequence numbers as the
- user executes strokes. These numbers can be used to define new
- strokes in the system-gschemrc file.
-
- -r filename
- Specify a rc filename. Normally gschem searches for the sys-
- tem-gschemrc, then ~/.gEDA/gschemrc, and finally for a gschemrc
- in the current directory. This options allows the user to
- specify an additional rc file which is read after all the other
- rc files are read. (optional)
-
- -s filename
- Specify a guile script to be executed at startup. (optional)
-
- -o filename
- Specify a filename for postscript output. This command line
- argument is useful when running gschem from a shell script and
- with a guile script. The filename can be changed through the
- print dialog box.
-
- -p Automatically place the window, especially useful if running
- gschem from the command line and generating output.
-
- schematic1 [... schematicN]
- Schematic file to be loaded. Specifing a schematic file is
- optional. If multiple schematic files are specified they are
- read in sequentially and put on seperate pages. It is impor-
- tant that the schematic(s) follow all the options (ie last).
-
-
-EXAMPLES
- These examples assume that you have a schematic called stack_1.sch in
- the current directory
-
- To run gschem and then interact with the program:
-
- ./gschem
-
- To run gschem in interactive mode but load a sample schematic:
-
- ./gschem adders_1.sch
-
- To run gschem and load up all schematics in the current subdirectory:
-
- ./gschem *.sch
-
-
-ENVIRONMENT
- No environment variables are used.
-
-
-AUTHOR
- Ales Hvezda and many others
-
-
-SEE ALSO
- gnetlist(1), gsymcheck(1)
-
-COPYRIGHT
- Copyright © 1999-2004 Ales Hvezda
-
- This document can be freely redistributed according to the terms of the
- GNU General Public License version 2.0
-
-
-
-
-Version December 31st, 2003 gschem(1)</font></pre>
-</p>
-
-</div>
-<!-- SECTION "On-line documentation" [36593-41062] -->
-<h1><a name="electrical_connectivity" id="electrical_connectivity">Electrical Connectivity</a></h1>
-<div class="level1">
-
-<p>
-As you draw schematics you need be aware of what is considered to be electrically connected by the gEDA programs.<br/>
- Nets which are visually connected to other nets are electrically connected. This connection may be endpoint to endpoint or endpoint to midpoint. When a single endpoint to endpoint (net or pin endpoint) connection is drawn, the visual dangling net cue disappears. When an endpoint ends in the middle of another net (or multiple endpoints coming together at a single point) then a circular filled connectivity cue is drawn. You cannot connect a net to the middle of a pin. Nets can only be connected to the endpoints of pins. You cannot connect to a net if that net is not orthogonal (horizontal or vertical). The visual cues are the primary way of telling if nets/pins are connected.<br/>
- Bus are similar to nets with the exception that you cannot connect a net to the endpoint of a bus (only to the middle). If you do try to connect a net to the end of a bus you will see a big red X at the invalid endpoint connection. Buses are still very new so there are still many quirks.<br/>
- You can label nets by using the <code>label=</code> attribute. Do not attach more than one <code>label=</code> to a net. You only need to attach the <code>label=</code> attribute to one net segment. Different nets (i.e. multiple net segments which arenâ??t connected together) which have the same attribute <code>label=</code> attached to them are also considered electrically connected. You will not get any indication of this connection by <strong>gschem</strong>, but the netlister (<strong>gnetlist</strong>) considers nets with the same <code>label=</code> attribute electrically connected. The naming convention for buses has not been formalized yet.
-</p>
-
-</div>
-<!-- SECTION "Electrical Connectivity" [41063-42779] -->
-<h1><a name="components_symbols_objects_attributes" id="components_symbols_objects_attributes">Components & Symbols & Objects & Attributes</a></h1>
-<div class="level1">
-
-<p>
-There is a hierarchical association between components, symbols, objects, and attributes.
-</p>
-
-</div>
-<!-- SECTION "Components & Symbols & Objects & Attributes" [42780-42928] -->
-<h2><a name="components" id="components">Components</a></h2>
-<div class="level2">
-
-<p>
-A component is the instantiation of a specific symbol, as placed on the schematic. When discussing a schematic you refer to <em class="u">components</em> on the schematic, not <em class="u">symbols</em> on the schematic. Think of symbols as being <em class="u">conceptual</em>, and components as being <em class="u">concrete</em>.<br/>
- The component consists of a graphic representation and the attributes describing the componentâ??s features.<br/>
- The component inherits all of the attributes defined in the symbol. Certain attributes in the symbol:
-</p>
-<ul>
-<li class="level1"><div class="li"> those explicitly defined as visible unattached attributes (see <a href="#attributes" title="geda:gschem_ug.fr ↵" class="wikilink1">Attributes</a>)</div>
-</li>
-<li class="level1"><div class="li"> specific attributes such as <code>symversion</code> and <code>refdes</code></div>
-</li>
-</ul>
-
-<p>
- are promoted to the component level for manipulation by the circuit designer. These attributes may optionally be exposed (made viewable) with the componentâ??s graphic, and their values may be changed.<br/>
- Any attribute not defined in the symbol may be defined in the component. For example, if the symbol does not define the <code>comment</code> attribute, this attribute may be added to the component, perhaps to add a comment for the Bill of Material or Assembly Instructions.<br/>
- Unfortunately, it is difficult to determine a componentâ??s attributes from <strong>gschem</strong> while entering the schematic. You have to place a symbol on the schematic, select the resulting component, and select <strong>Hierarchy | Down Symbol</strong> from the pull-down menus. Then, you have to unhide all attributes with <strong>Edit | Make Inv Text Vis</strong> from the pull-down menus. Then you have to expand your view of the symbol with <strong>View | Extents</strong>. Then, you have to go back to the schematic by selecting <strong>Hierarchy | Up</strong> from the pull-down menus. Then, you have to select <strong>Edit | Edit…</strong> to bring up the â??Edit Attributesâ?? dialog box to determine if any attributes have been added at the component level.
-</p>
-
-</div>
-<!-- SECTION "Components" [42929-44743] -->
-<h2><a name="symbols" id="symbols">Symbols</a></h2>
-<div class="level2">
-
-<p>
-Symbols are just a collection of objects and attributes.<br/>
- The objects have positional significance in the symbol, and define the graphic that is viewed.<br/>
- Attributes may be attached to objects, or they may be attached to the symbol itself (termed as â??unattachedâ?? attributes, because they are not attached to an object).
-</p>
-
-</div>
-<!-- SECTION "Symbols" [44744-45085] -->
-<h2><a name="objects" id="objects">Objects</a></h2>
-<div class="level2">
-
-<p>
-The following are objects:
-</p>
-<ul>
-<li class="level1"><div class="li"> Line</div>
-</li>
-<li class="level1"><div class="li"> Box</div>
-</li>
-<li class="level1"><div class="li"> Circle</div>
-</li>
-<li class="level1"><div class="li"> Arc</div>
-</li>
-<li class="level1"><div class="li"> Pin</div>
-</li>
-<li class="level1"><div class="li"> Picture</div>
-</li>
-<li class="level1"><div class="li"> Text</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Objects" [45086-45198] -->
-<h2><a name="attributes" id="attributes">Attributes</a></h2>
-<div class="level2">
-
-<p>
-An attribute is text which is in the form <code>name=value</code> (there are no spaces to the left or right of the name,value pair). An attribute can be either attached to an object or unattached. Attributes are used extensively in the gEDA project to convey information (e.g., device name, pin numbers, hidden nets, and unit reference numbers). Check <a href="http://www.geda.seul.org/docs/current/attributes/index.html"; class="urlextern" title="http://www.geda.seul.org/docs/current/attributes/index.html"; rel="nofollow">gEDA/gaf Master Attribute Document</a> for a complete list of attributes.<br/>
- There are three kinds of attributes:</p>
-<dl>
-<dt><span class='term'> Attached attributes</span></dt>
-<dd>These are attributes which take on the standard form and are attached to some object (pin, net, component, or box etc…) to associate a value with the attribute. For example: a pin number associated with a pin. <span class="hilited">These attributes are usually yellow in color.</span></dd>
-<dt><span class='term'> Unattached attributes</span></dt>
-<dd>These are attributes which take on the standard form, but are not attached to any object and usually convey some information which is global in nature. For example: a <code>device=</code> attribute (which lives inside symbols) and specifies what device the entire symbol represents. These attributes are also known as floating or toplevel attributes.</dd>
-<dt><span class='term'> Promoted attributes</span></dt>
-<dd>These are unattached attributes in the symbolâ??s definition that get turned into attached attributes in the componentâ??s definition when the symbol is instantiated as a component when placed in the schematic. If you place an unattached visible attribute inside a symbol and then instantiate that symbol, then that unattached attribute gets â??promotedâ??; that is, it becomes an attached attribute. This mechanism of attribute reattachement (from within a symbol) is known as attribute promotion.</dd>
-</dl>
-<p>There are some gotchas about attribute promotion:
-</p>
-<ul>
-<li class="level1"><div class="li"> Promotion <strong>only</strong> happens when the symbol is first placed. That means that if you place a symbol (e.g., sym1) and then change it on disk (by adding or removing new unattached attributes), existing sym1â??s will not reflect these new unattached attributes (i.e., they wonâ??t get promoted) in any schematic.</div>
-</li>
-<li class="level1"><div class="li"> The <code>device=</code> attribute is not promoted.</div>
-</li>
-<li class="level1"><div class="li"> Invisible attributes are not promoted by default. If you add an unattached attribute (e.g., numslots=#) and make it invisible, it will not be promoted.</div>
-</li>
-</ul>
-
-<p>
- Now, in order to make everybody happy, this attribute promotion behavior is configurable.<br/>
- The system-gschemrc file defines: <pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">(attribute-promotion "enabled")</font></pre>
-</p>
-
-<p>
-which enables attribute promotion.<br/>
- If you override the system-gschemrcâ??s default promote-invisible setting by adding: <pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">(promote-invisible "enabled")</font></pre>
-</p>
-
-<p>
-to either your userâ??s ~/gschemrc or local â??pwdâ??/gschemrc file, invisible unattached attributes will also be promoted <span class="hilited">(and in memory removed)</span>.
-</p>
-
-<p>
-However, if you do this, component slotting will break because <strong>gschem</strong> expects certain unattached attributes inside the symbol <span class="hilited">(in memory even though they are invisible)</span>.<br/>
- So you can add: <pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">(keep-invisible "enabled")</font></pre>
-</p>
-
-<p>
-to either your userâ??s ~/gschemrc or local â??pwdâ??/gschemrc file. This is enabled by default, but has no effect unless promote-invisible is enabled.
-</p>
-
-<p>
-So, to summarize, attribute promotion takes unattached attributes inside symbols and attaches them to the outside of a placed symbol. Three *rc keywords control this behavior: attribute-promotion, promote-invisible, and keep-invisible.
-</p>
-
-</div>
-<!-- SECTION "Attributes" [45199-48585] -->
-<h1><a name="the_main_window" id="the_main_window">The Main Window</a></h1>
-<div class="level1">
-<table class="inline">
- <tr>
- <td> <a href="_detail/001geda_gschem_screenshot_001.html" class="media" title="geda:gschem_screenshot_001.jpg"><img src="http://geda.seul.org/wiki/_media/geda:gschem_screenshot_001.jpg?w=&h=&cache=cache"; class="media" title="gschem_screenshot_001.jpg" alt="gschem_screenshot_001.jpg" /></a> </td>
- </tr>
-</table>
-
-<p>
- There are several ways to interact with <strong>gschem</strong>. <strong>gschem</strong> requires a keyboard and mouse. There are three ways to initiate an operation or command:
-</p>
-<ul>
-<li class="level1"><div class="li"> Using the mouse to select the operation off a menu</div>
-</li>
-<li class="level1"><div class="li"> Typing the keyboard shortcut(s).</div>
-</li>
-<li class="level1"><div class="li"> Draw the appropriate stroke (if stroke support is enabled)</div>
-</li>
-</ul>
-
-<p>
- To make usage matters more confusing, selecting an operation off of the menus behaves slightly differently than typing the keyboard shortcut. Most of the operations operate on the currently selected object(s), hence you need to select the object first before manipulating them. The menu selected operations usually require some more input (usually a mouse click) after they are picked off of the menu. The keyboard shortcut operations take that required input as the current mouse position. This saves an extra click since you can position the mouse at the right place, type in the shortcut(s), and the command then executes. Note, you can change this so that both menu and shortcut behavior is exactly the same. See the section on the resource file for more info on how to configure this.<br/>
- Most of the interaction with <strong>gschem</strong> is fairly mode oriented (similar to the great text editor vi). If you select operations off of the menu, then you are placed into the corresponding mode (like copy or move mode). You must then select an anchor point (or whatever the appropriate point is) to continue the operation. Most of the commands off of the menu expect the objects to be already selected. Some of the modes persist after being execute while other immediately return you into select mode (the default mode).<br/>
- The shortcuts are also mode like in nature. Most of the default shortcuts are for the various commands are not single keystrokes. There are a few which are single keystrokes (like zoom in: `zâ?? or pan: `xâ??), but most are typically two keystrokes long. As examples, to execute File/Save you would type `fâ?? and `sâ?? (without the quotes) or Add/Line is `aâ?? and `lâ??. You can get a listing of the shortcuts by picking Help/Hotkeys. You can also see the hotkey assignments in the pulldown menus as well. The shortcuts are defined in the resource files (<strong>system-gschemrc</strong>, <strong>/.gEDA/gschemrc</strong>, or <strong>`pwd`/gschemrc</strong>). See the section on the resource file for more info.<br/>
- The mouse button actions in <strong>gschem</strong> are mostly configurable. The first mouse button is always used to select objects or pick points. This button is not configurable. The second mouse button is either a copy/move action (when held down over an object), a repeat last command or used to draw a stroke to execute a command. The third mouse button is either a mouse pan (when held down as the mouse is moved) or a popup menu. The behavior of the second and third mouse buttons is controlled through the resource file (see the section below for more info).
-</p>
-
-</div>
-<!-- SECTION "The Main Window" [48586-51499] -->
-<h1><a name="the_status_window" id="the_status_window">The Status Window</a></h1>
-<div class="level1">
-<table class="inline">
- <tr>
- <td> <a href="_detail/001geda_status_screenshot.html" class="media" title="geda:status_screenshot.jpg"><img src="http://geda.seul.org/wiki/_media/geda:status_screenshot.jpg?w=&h=&cache=cache"; class="media" title=":geda:status_screenshot.jpg" alt=":geda:status_screenshot.jpg" /></a> </td>
- </tr>
-</table>
-
-<p>
- Add some details about what gets displayed in the status window.
-</p>
-
-</div>
-<!-- SECTION "The Status Window" [51500-51662] -->
-<h1><a name="the_schematic_file" id="the_schematic_file">The Schematic File</a></h1>
-<div class="level1">
-
-<p>
-Schematic files. These files contain components, nets, text, and sometimes primitive objects (like lines, circles, box etc…) Schematics do not contain pins. Schematic filenames should follow this convention: name_#.sch where:
-</p>
-<ul>
-<li class="level1"><div class="li"> name is a text string which describes what this schematic contains.</div>
-</li>
-<li class="level1"><div class="li"> _# is an underscore and a number (like _1, _2, _7, _13, etc…) This number is used to sequence schematic pages in a multiple page schematic.</div>
-</li>
-<li class="level1"><div class="li"> .sch is the schematic extension/suffix. It is important the schematic pages have this extension.</div>
-</li>
-</ul>
-
-<p>
- Schematic files are pure <acronym title="American Standard Code for Information Interchange">ASCII</acronym> and will always be pure <acronym title="American Standard Code for Information Interchange">ASCII</acronym>. gEDA does not support any binary file formats. The file format for schematics is described in the gEDA file formats document.
-</p>
-
-</div>
-<!-- SECTION "The Schematic File" [51663-52432] -->
-<h1><a name="the_symbol_file" id="the_symbol_file">The Symbol File</a></h1>
-<div class="level1">
-
-<p>
-Symbol files. The schematic and symbol file formats are identical. <strong>gschem</strong> (or a text editor) is used to create symbol files as well as schematics. Symbol files contain lines, circles, boxes, arcs, pins, text, and attributes.<br/>
- The naming convention for symbol files is: name-#.sym where:
-</p>
-<ul>
-<li class="level1"><div class="li"> name is a text string which describes what the symbol represents.</div>
-</li>
-<li class="level1"><div class="li"> -# is a dash and a number (like -1, -2 etc…) The number is used to allow for a symbols to have the same name yet different contents. There might be multiple representations for resistors so these symbols should be called: resistor-1.sym, resistor-2.sym, and resistor-3.sym.</div>
-</li>
-<li class="level1"><div class="li"> .sym is the symbol extension/suffix. It is important the symbols have this extension.</div>
-</li>
-</ul>
-
-<p>
- The way of specifying hierarchy is by using the source= attribute. Please see the master attribute document for info on this mechanism.<br/>
- The hierarchy mechanism is still in heavy flux, so there might be some more changes.
-</p>
-
-</div>
-<!-- SECTION "The Symbol File" [52433-53419] -->
-<h1><a name="symbol_libraries" id="symbol_libraries">Symbol Libraries</a></h1>
-<div class="level1">
-
-<p>
-Components are searched for by specifying (component-library "…â??) inside one of the *rc files. See below for more info.
-</p>
-
-</div>
-<!-- SECTION "Symbol Libraries" [53420-53573] -->
-<h1><a name="the_log_file" id="the_log_file">The Log File</a></h1>
-<div class="level1">
-
-<p>
-Log file. This file contains informative, error, warnings etc… messages when <strong>gschem</strong> was run. This file is created in the working directory that <strong>gschem</strong> was started in. This allows the user to preserve log files between independent projects.
-</p>
-
-</div>
-<!-- SECTION "The Log File" [53574-53851] -->
-<h1><a name="grips" id="grips">Grips</a></h1>
-<div class="level1">
-
-<p>
-Grips are a mechanism used in <strong>gschem</strong> to provide an easy way of modifying objects inside schematics. When you select an object, little squares are placed in strategic locations (line end points or circle radius point or corners of a box) which allow you to change the object quickly. Grip support currently exists for lines, nets, pins, buses, circles, and boxes. Arcs do not yet have grips, but will eventually have them.
-</p>
-
-<p>
-Using grips is easy:
-</p>
-<ul>
-<li class="level1"><div class="li"> Select the object you want to change. The grips (the little boxes) will appear.</div>
-</li>
-<li class="level1"><div class="li"> Click and hold the first mouse button inside the box.</div>
-</li>
-<li class="level1"><div class="li"> Move the mouse around till you have the object where you want it</div>
-</li>
-<li class="level1"><div class="li"> Release the mouse button.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Grips" [53852-54561] -->
-<h1><a name="menu_operations" id="menu_operations">Menu Operations</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "Menu Operations" [54562-54591] -->
-<h2><a name="file" id="file">File</a></h2>
-<div class="level2">
-
-<p>
-The <strong>gschem</strong> application is primarily used for the creation of schematic files (i.e., filename.sch) and symbol files (filename.sym).<br/>
- The following operations are related to the manipulation of these files.<br/>
- Note that <strong>gschem</strong> automatically maintains backups of open schematic/symbol files, in the /tmp directory, for the purpose of Undo/Redo. <strong>gschem</strong> cleans up these files when it exits gracefully. If <strong>gschem</strong> does not exit gracefully, the next time you launch <strong>gschem</strong> you will be prompted with a dialog similar to: <pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">WARNING: Found an autosave backup file:
- {filename}
-
- The backup copy is newer than the schematic, so it seems you
- load it instead of the original file.
- gschem usually makes backup copies automatically, and this
- situation happens when it crashed or it was forced to exit
- abruptly.
-
- If you load the original file, the backup file will be overwritten in
- the next autosave timeout and it will be lost.
-
- Do you want to load the backup file?</font></pre>
-</p>
-
-<p>
-The following are available from the <strong>gschem</strong> main windowâ??s menu-bar when you expand <strong>File</strong>:
-</p>
-
-</div>
-<!-- SECTION "File" [54592-55745] -->
-<h3><a name="new_window_fw" id="new_window_fw">New Window (fw)</a></h3>
-<div class="level3">
-
-<p>
-<strong>File | New Window</strong> Ouvre une nouvelle fenêtre. Chaque fenêtre est totalement séparée des autres fenêtres.
-</p>
-
-</div>
-<!-- SECTION "New Window (fw)" [55746-55886] -->
-<h3><a name="new_page_fn" id="new_page_fn">New Page (fn)</a></h3>
-<div class="level3">
-
-<p>
-<strong>File | New Page</strong> Ouvre une nouvelle page en plus de toute page ouverte existante. Cette page sera habituellement appelée «·untitled_N.sch·» où N est un nombre incrémenté.
-</p>
-
-</div>
-<!-- SECTION "New Page (fn)" [55887-56093] -->
-<h3><a name="open_page..._fo" id="open_page..._fo">Open Page... (fo)</a></h3>
-<div class="level3">
-
-<p>
-<strong>File | Open Page…</strong> Ouvre une page depuis le disque.<br/>
- The â??Open…â?? dialog box pops up providing:
-</p>
-<ul>
-<li class="level1"><div class="li"> Directory navigation aids</div>
-</li>
-<li class="level1"><div class="li"> Filters for restricting the displayed files:</div>
-<ul>
-<li class="level2"><div class="li"> Schematics</div>
-</li>
-<li class="level2"><div class="li"> Symbols</div>
-</li>
-<li class="level2"><div class="li"> Schematics and Symbols</div>
-</li>
-<li class="level2"><div class="li"> All files</div>
-</li>
-</ul>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Open Page... (fo)" [56094-56380] -->
-<h3><a name="close_page_pc" id="close_page_pc">Close Page (pc)</a></h3>
-<div class="level3">
-
-<p>
-<strong>File | Close Page</strong> Fermer la page actuellement affichée. Il vous sera demandé de faire une sauvegarde si vous avez fait des modifications sur la page.
-</p>
-
-</div>
-<!-- SECTION "Close Page (pc)" [56381-56563] -->
-<h3><a name="revert_page_pr" id="revert_page_pr">Revert Page (pr)</a></h3>
-<div class="level3">
-
-<p>
-<strong>File | Revert Page</strong> Ferme et réouvre la page actuellement affichée. Il ne vous sera pas demandé de sauvegarder la page courante et effacera toutes les changements que vous avez fait en réouvrant le schéma sauvegardé dans le disque. A utiliser avec précaution.
-</p>
-
-</div>
-<!-- SECTION "Revert Page (pr)" [56564-56861] -->
-<h3><a name="save_page_fs" id="save_page_fs">Save Page (fs)</a></h3>
-<div class="level3">
-
-<p>
-<strong>File | Save Page</strong> Sauve la page courante. The current filename is displayed in the <strong>gschem</strong> status-bar.<br/>
- Si la page est appelée untitled_N.sch (o N est un entier) alors une boîte de dialogue avec Save As… apparaîtra demandant un nouveau nom de fichier.<br/>
- If the pageâ??s filename is NOT â??untitled_N.schâ?? (where N is a integer), then the Save As… dialog box will NOT be displayed, and:
-</p>
-<ul>
-<li class="level1"><div class="li"> the backup file will be created for the previous version, named {filename}~ That is, the "~" (tilde character) is appended to the filename. Any previous backup file is lost.</div>
-</li>
-<li class="level1"><div class="li"> the file will be saved to the current filename.<br/>
-</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Save Page (fs)" [56862-57515] -->
-<h3><a name="save_page_as..._fa" id="save_page_as..._fa">Save Page As... (fa)</a></h3>
-<div class="level3">
-
-<p>
-<strong>File | Save Page As…</strong> Ouvre la boîte de dialogue Save As.<br/>
- If the current filename is â??untitled_N.schâ??, the Save As… dialog box prompts for a new filename.<br/>
- If the current filename is NOT â??untitled_N.schâ??, the Save As… dialog box prompts for a new filename, filling in the current filename as a default.<br/>
- In either case the filename may be changed, and a new file created when the Save As button is clicked.
-</p>
-
-</div>
-<!-- SECTION "Save Page As... (fa)" [57516-57968] -->
-<h3><a name="save_all_fl_fl" id="save_all_fl_fl">Save All (fl) (fl)</a></h3>
-<div class="level3">
-
-<p>
-<strong>File | Save All</strong> Sauvegarde inconditionnelle de tous les schémas chargés dans la mémoire.
-</p>
-
-</div>
-<!-- SECTION "Save All (fl) (fl)" [57969-58094] -->
-<h3><a name="print..._fp" id="print..._fp">Print... (fp)</a></h3>
-<div class="level3">
-
-<p>
-<strong>File | Print…</strong> Affiche la boîte de dialogue Print.<br/>
- The following may be selected:
-</p>
-<ul>
-<li class="level1"><div class="li"> Filename (if <strong>gschem</strong> has multiple pages loaded, this filename defaults to the page currently displayed).</div>
-</li>
-<li class="level1"><div class="li"> Paper size (that is loaded into your printer).</div>
-</li>
-<li class="level1"><div class="li"> The print type:</div>
-<ul>
-<li class="level2"><div class="li"> Extents with margins – the current page, with margins where the printer doesnâ??t output.</div>
-</li>
-<li class="level2"><div class="li"> Extents no margins – the current page, but without margins where the printer doesnâ??t output. The printer output may be scaled larger than when using â??Entents with marginsâ??, but at the loss along the borders of the schematic.</div>
-</li>
-<li class="level2"><div class="li"> Current window – Scaled to fit the page size, but not optimally.</div>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"> Orientation:</div>
-<ul>
-<li class="level2"><div class="li"> Landscape</div>
-</li>
-<li class="level2"><div class="li"> Portrait</div>
-</li>
-</ul>
-</li>
-</ul>
-
-<p>
- Pressing Print will generate a PostScript file with the filname format of the form {filename}.ps (e.g., printing schematic file First_1.sch would generate First_1.ps).<br/>
- Printing the PostScript file to your printer is distribution dependent:</p>
-<dl>
-<dt><span class='term'> Fedora Core (from the command-line):</span></dt>
-<dd><code>lp First_1.ps</code></dd>
-</dl>
-
-
-</div>
-<!-- SECTION "Print... (fp)" [58095-59143] -->
-<h3><a name="write_png..._fi" id="write_png..._fi">Write PNG... (fi)</a></h3>
-<div class="level3">
-
-<p>
-<strong>File | Write <acronym title="Portable Network Graphics">PNG</acronym>…</strong> Affiche la boîte de dialogue Write <acronym title="Portable Network Graphics">PNG</acronym>. Note you must have libgdgeda installed (and any required dependencies) if you want to output images.<br/>
- The dialog box allows you to select:
-</p>
-<ul>
-<li class="level1"><div class="li"> Width x Height:</div>
-<ul>
-<li class="level2"><div class="li"> 320 x 240</div>
-</li>
-<li class="level2"><div class="li"> 640 x 480</div>
-</li>
-<li class="level2"><div class="li"> 800 x 600</div>
-</li>
-<li class="level2"><div class="li"> 1024 x 768</div>
-</li>
-<li class="level2"><div class="li"> 1280 x 960</div>
-</li>
-<li class="level2"><div class="li"> 1600 x 1200</div>
-</li>
-<li class="level2"><div class="li"> 3200 x 2400</div>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"> Filename (if <strong>gschem</strong> has multiple pages loaded, the currently displayed pageâ??s filname is given)</div>
-</li>
-</ul>
-
-<p>
- When the OK button is clicked, a <acronym title="Portable Network Graphics">PNG</acronym> graphic file with a filename of the form {filename}.png is created (e.g., writing a <acronym title="Portable Network Graphics">PNG</acronym> for schematic file First_1.sch will generate a First_1.png file).<br/>
- This file may be used any way a <acronym title="Portable Network Graphics">PNG</acronym> file is used (e.g., web-page, document insertion, image manipulation with the GIMP, etc.).
-</p>
-
-</div>
-<!-- SECTION "Write PNG... (fi)" [59144-59940] -->
-<h3><a name="execute_script..._ft" id="execute_script..._ft">Execute Script... (ft)</a></h3>
-<div class="level3">
-
-<p>
-<strong>File | Execute Script…</strong> …..TBD
-</p>
-
-</div>
-<!-- SECTION "Execute Script... (ft)" [59941-60012] -->
-<h3><a name="close_window_fc" id="close_window_fc">Close Window (fc)</a></h3>
-<div class="level3">
-
-<p>
-<strong>File | Close Window</strong> Ferme la fenêtre actuelle. Sâ??il y a des schémas modifiés, une boîte de dialogue â??There are unsaved schematicsâ?? apparaîtra. Cliquer sur OK fera perdre tous les schémas non sauvegardés.
-</p>
-
-</div>
-<!-- SECTION "Close Window (fc)" [60013-60263] -->
-<h3><a name="quit_alt-q" id="quit_alt-q">Quit (Alt-q)</a></h3>
-<div class="level3">
-
-<p>
-<strong>File | Quit</strong> closes all opened windows and exits <strong>gschem</strong>. A â??There are unsaved schematicsâ?? dialog box will appear for each window that has unsaved schematics.
-</p>
-
-</div>
-<!-- SECTION "Quit (Alt-q)" [60264-60456] -->
-<h2><a name="edit" id="edit">Edit</a></h2>
-<div class="level2">
-
-<p>
-The following are available from the <strong>gschem</strong> main windowâ??s menu-bar when you expand <strong>Edit</strong>:
-</p>
-
-</div>
-<!-- SECTION "Edit" [60457-60573] -->
-<h3><a name="undo_shift-u" id="undo_shift-u">Undo (shift-u)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Edit | Undo</strong> does exactly that, it undos the last action which changed the schematic.<br/>
- The depth of undo (how many undo steps can be performed) is set in the system-gschemrc file. The default is 10. Simply override this setting by placing the following lines in either your ~/.gEDA/gschemrc file or your local gschemrc file: <pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">; undo-levels number
-;
-; Determines the number of levels of undo. Basically this number decides
-; how many backup schematics are saved on disk.
-;
-(undo-levels 10)</font></pre>
-</p>
-
-<p>
-After every action (including zooming and panning) the schematic is saved to disk (in /tmp). The undo-levels setting determines how many of these temporary files are maintained in the /tmp directory. <strong>gschem</strong> does clean-up after itself when you exit.<br/>
- Should <strong>gschem</strong> crash, the saved files remain in /tmp for disaster recovery. You will be prompted the next time the schematic is opened to recover from the backup.<br/>
-
-</p>
-
-</div>
-<!-- SECTION "Undo (shift-u)" [60574-61532] -->
-<h3><a name="redo_shift-r" id="redo_shift-r">Redo (shift-r)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Edit | Redo</strong> only applies after you have done an <strong>Edit | Undo</strong>. You can undo something and then immediately redo it. However if you do anything in between you will lose the undo info. You can undo and redo to your hearts desire up and down till you reach the max undo levels.<br/>
-
-</p>
-
-</div>
-<!-- SECTION "Redo (shift-r)" [61533-61841] -->
-<h3><a name="select_mode_s" id="select_mode_s">Select Mode (s)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Edit | Select Mode</strong> is the initial mode in which <strong>gschem</strong> starts.<br/>
- When in <strong>Select Mode</strong>, an unlocked object (i.e., component, line, box, circle, …) may be selected by placing the mouse pointer within the outline of the object and single-clicking, or by dragging a box (i.e., holding down the first mouse-button) around the object. Selecting an already selected object will leave the object selected (i.e., you can not unselect an object by single-clicking it). Multiple unlocked objects may be selected by dragging a box around the objects.<br/>
- A locked object may be selected by dragging a box around the object.<br/>
- To de-select all objects, single-click anywhere on the schematic where there is no object.<br/>
- A visible attribute for an unlocked component may be selected by placing the mouse pointer over the componentâ??s visible attribute and single-clicking. Placing the mouse pointer over the unlocked componentâ??s visible attribute and double-clicking will open the edit dialog box appropriate for the attribute.<br/>
- Objects will change color when selected.<br/>
- You stay in <strong>Select Mode</strong> until you select one of the other Modes (e.g., Line, Copy, Move, etc.).<br/>
- Your current Mode is displayed on the status-bar, in the lower-right corner of the <strong>gschem</strong> window.<br/>
- If multiple objects overlap, single-clicking where they overlap will cycle through the objects.<br/>
- If you hold down the SHIFT key and single-click, you can select and deselect multiple objects. Doing this with multiple overlapping objects will cause the selection to cycle among the possible object selections.<br/>
- If you hold down the CONTROL key and single-click, you will toggle the object in and out of the current selection list.<br/>
- If you hold down the SHIFT key while drawing a selection box you will add to the currently selected objects. Objects cannot be removed using the selection box and holding down the SHIFT key.<br/>
- If you hold down the CONTROL key while drawing a selection box then you will toggle any encompassed objects. If an object was selected then it will be unselected and vice versa.<br/>
- If you pick a component, its visible and invisible attributes are selected as well. If you just want to select the object, you must deselect the attributes.<br/>
- The selection mechanisms are not obvious and do require some practice. There are some quirks so please report them as you come across them.
-</p>
-
-</div>
-<!-- SECTION "Select Mode (s)" [61842-64249] -->
-<h3><a name="edit..._ee" id="edit..._ee">Edit... (ee)</a></h3>
-<div class="level3">
-
-<p>
-First, select the object to be edited (i.e., in <strong>Select Mode</strong>).<br/>
- If the object is a component, <strong>Edit | Edit…</strong> then pops up a dialog box that allows you to edit the componentâ??s attributes:
-</p>
-<ul>
-<li class="level1"><div class="li"> Existing attributes (e.g., refdes) are displayed.</div>
-</li>
-<li class="level1"><div class="li"> A drop-down list of pre-defined attributes permits selection, and a edit-box provides association of a value to the attribute.</div>
-</li>
-<li class="level1"><div class="li"> The attributeâ?? name and/or value may be made visible or invisible,</div>
-</li>
-</ul>
-
-<p>
- If the ojbect is a text string, <strong>Edit…</strong> then pops up a dialog box that allows you to modify the text stringâ??s attributes:
-</p>
-<ul>
-<li class="level1"><div class="li"> The text string may be modified. Multiple lines of text may be entered by inserting carriage-returns.</div>
-</li>
-<li class="level1"><div class="li"> The text color may be modified.</div>
-</li>
-<li class="level1"><div class="li"> The text size may be modified.</div>
-</li>
-<li class="level1"><div class="li"> The text alignment:</div>
-<ul>
-<li class="level2"><div class="li"> Lower/middle/upper left</div>
-</li>
-<li class="level2"><div class="li"> Lower/middle/upper middle</div>
-</li>
-<li class="level2"><div class="li"> Lower/middle/upper right</div>
-</li>
-</ul>
-</li>
-</ul>
-
-<p>
- Apply the changes by pressing OK.
-</p>
-
-<p>
-<strong>Notes:</strong><br/>
- If you need to change the attributes to more than just a few components, consider saving your schematics, closing <strong>gschem</strong>, and using the <strong>gattrib</strong> application, the <strong>grenum</strong> application, or the <strong>refdes_renum</strong> application to make the changes.
-</p>
-
-</div>
-<!-- SECTION "Edit... (ee)" [64250-65444] -->
-<h3><a name="edit_text..._ex" id="edit_text..._ex">Edit Text... (ex)</a></h3>
-<div class="level3">
-
-<p>
-First, select the text object to be edited (i.e., in <strong>Select Mode</strong>).<br/>
- <strong>Edit | Edit Text…</strong> allows you to edit just text.<br/>
- <strong>Edit | Edit Text…</strong> then pops up a dialog box that allows you to modify the text stringâ??s attributes:
-</p>
-<ul>
-<li class="level1"><div class="li"> The text string may be modified. Multiple lines of text may be entered by inserting carriage-returns.</div>
-</li>
-<li class="level1"><div class="li"> The text color may be modified.</div>
-</li>
-<li class="level1"><div class="li"> The text size may be modified.</div>
-</li>
-<li class="level1"><div class="li"> The text alignment:</div>
-<ul>
-<li class="level2"><div class="li"> Lower/middle/upper left</div>
-</li>
-<li class="level2"><div class="li"> Lower/middle/upper middle</div>
-</li>
-<li class="level2"><div class="li"> Lower/middle/upper right</div>
-</li>
-</ul>
-</li>
-</ul>
-
-<p>
- Apply the changes by pressing OK.
-</p>
-
-<p>
-<strong>Notes:</strong><br/>
- If you need to change the attributes to more than just a few text strings, consider saving your schematics, closing <strong>gschem</strong>, and using the <strong>gattrib</strong> application, the <strong>grenum</strong> application, or the <strong>refdes_renum</strong> application to make the changes.
-</p>
-
-</div>
-<!-- SECTION "Edit Text... (ex)" [65445-66303] -->
-<h3><a name="copy_mode_ec" id="copy_mode_ec">Copy Mode (ec)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Edit | Copy Mode</strong> allows you to copy (i.e., duplicate) the currently selected objects.<br/>
- To copy the object(s):
-</p>
-<ul>
-<li class="level1"><div class="li"> Select the objects to be copied (i.e., in <strong>Select Mode</strong>)</div>
-</li>
-<li class="level1"><div class="li"> Select <strong>Edit | Copy Mode</strong></div>
-</li>
-<li class="level1"><div class="li"> Observe the status-bar now indicates <strong>Copy Mode</strong></div>
-</li>
-<li class="level1"><div class="li"> Click on the selected component(s) to establish an origin of reference</div>
-</li>
-<li class="level1"><div class="li"> Observe a shadow/outline appears for the selected components that moves with the mouse</div>
-</li>
-<li class="level1"><div class="li"> Place the components where you want them</div>
-</li>
-<li class="level1"><div class="li"> Click to anchor the copied components in place.</div>
-</li>
-</ul>
-
-<p>
- After finishing the copy, you automatically return to <strong>Select Mode</strong>.<br/>
- Holding down the CONTROL key as you move the outline around will constrain the movement to be either horizontal or vertical.<br/>
- To copy objects using the shortcut keys is almost the same as above except that the origin point is selected automatically for you once you hit the copy mode shortcut.<br/>
-
-</p>
-
-</div>
-<!-- SECTION "Copy Mode (ec)" [66304-67228] -->
-<h3><a name="move_mode_em" id="move_mode_em">Move Mode (em)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Edit | Move Mode</strong> allows you to move the currently selected objects.<br/>
- To move the object(s):
-</p>
-<ul>
-<li class="level1"><div class="li"> Select the objects to be moved (i.e., in <strong>Select Mode</strong>)</div>
-</li>
-<li class="level1"><div class="li"> Select <strong>Edit | Move Mode</strong></div>
-</li>
-<li class="level1"><div class="li"> Observe the status-bar now indicates <strong>Move Mode</strong></div>
-</li>
-<li class="level1"><div class="li"> Click on the selected component(s) to establish an origin of reference</div>
-</li>
-<li class="level1"><div class="li"> Observe a shadow/outline appears for the selected components that moves with the mouse</div>
-</li>
-<li class="level1"><div class="li"> Place the components where you want them</div>
-</li>
-<li class="level1"><div class="li"> Click to anchor the moved components in place.</div>
-</li>
-</ul>
-
-<p>
- After finishing the move, you automatically return to <strong>Select Mode</strong>.<br/>
- Holding down the CONTROL key as you move the outline around will constrain the movement to be either horizontal or vertical.<br/>
- To move objects using the shortcut keys is almost the same as above except that the origin point is selected automatically for you once you hit the copy mode shortcut.<br/>
-
-</p>
-
-<p>
-Since version 20060906, there is another way to move object(s):<br/>
-
-</p>
-<ul>
-<li class="level1"><div class="li"> Select the objects to be moved (i.e., in <strong>Select Mode</strong>).<br/>
-</div>
-</li>
-<li class="level1"><div class="li"> Put the mouse pointer on one of the selected objects, then drag the objects and drop them where you want them.<br/>
-</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Move Mode (em)" [67229-68382] -->
-<h3><a name="delete_delete-key" id="delete_delete-key">Delete (Delete-key)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Edit | Delete</strong> allows you to remove objects off of the page.<br/>
- To delete objects:
-</p>
-<ul>
-<li class="level1"><div class="li"> Select the desired object(s) (i.e., in <strong>Select Mode</strong>)</div>
-</li>
-<li class="level1"><div class="li"> Select <strong>Edit | Delete</strong></div>
-</li>
-</ul>
-
-<p>
- The object(s) will be deleted immediately. If you inadvertantly delete a component, you can use Undo to recover.
-</p>
-
-</div>
-<!-- SECTION "Delete (Delete-key)" [68383-68701] -->
-<h3><a name="rotate_90_mode_er" id="rotate_90_mode_er">Rotate 90 Mode (er)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Edit | Rotate 90 Mode</strong> allows you to rotate objects 90 degrees around a pivot/center point.<br/>
- To rotate objects:
-</p>
-<ul>
-<li class="level1"><div class="li"> Select the desired object(s) (i.e., in <strong>Select Mode</strong>)</div>
-</li>
-<li class="level1"><div class="li"> Select <strong>Edit | Rotate 90 Mode</strong></div>
-</li>
-<li class="level1"><div class="li"> Click on the pivot (or center) point of the rotate</div>
-</li>
-</ul>
-
-<p>
- The object(s) will be rotated 90º counter-clockwise immediately. If you inadvertantly rotate a component, you can use Undo to recover.<br/>
- Rotating objects using the shortcut keys is similar to above except that the center point is the last mouse position at which you typed the shortcut.<br/>
-
-</p>
-
-</div>
-<!-- SECTION "Rotate 90 Mode (er)" [68702-69291] -->
-<h3><a name="mirror_mode_ei" id="mirror_mode_ei">Mirror Mode (ei)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Edit | Mirror Mode</strong> allows you to mirror objects horizontally around a pivot point.<br/>
- To mirror objects:
-</p>
-<ul>
-<li class="level1"><div class="li"> Select the desired object(s) (i.e., in <strong>Select Mode</strong>)</div>
-</li>
-<li class="level1"><div class="li"> Select <strong>Edit | Mirror Mode</strong></div>
-</li>
-<li class="level1"><div class="li"> Click on the pivot (or center) point of the mirror</div>
-</li>
-</ul>
-
-<p>
- Mirroring objects using the shortcut keys is similar to above except that the pivot point is the last mouse position at which you typed the shortcut.<br/>
- Objects are mirrored horizontally about the pivot point. If you want to get a vertical mirror then rotate and mirror the object(s) till you get the desired position.<br/>
- Mirroring of embedded components is not supported.
-</p>
-
-</div>
-<!-- SECTION "Mirror Mode (ei)" [69292-69948] -->
-<h3><a name="slot..._e_shift-s" id="slot..._e_shift-s">Slot... (e shift-s)</a></h3>
-<div class="level3">
-
-<p>
-Some physical packages (e.g., the classic 7400 Quad NAND gate) contain more than one logical component (e.g., one of the NAND gates). In <strong>gchem</strong> terminology, each of these logical components is termed a â??slotâ?? (e.g., there would be 4 slots in the 7400 Quad NAND gate). Each slot is associated with specific pins on the physical package.<br/>
- <strong>Edit | Slot…</strong> allows you to change the slot number of a multiple-slot package. The package must support slotting. Refer to the <a href="http://www.geda.seul.org/docs/current/symbols/index.html"; class="urlextern" title="http://www.geda.seul.org/docs/current/symbols/index.html"; rel="nofollow">gEDA/gaf Symbol Creation Document</a> for more details.<br/>
- To change the slot number (i.e., select which package pins are associated with a logical component):
-</p>
-<ul>
-<li class="level1"><div class="li"> Select the desired logical component (i.e., in <strong>Select Mode</strong>)</div>
-</li>
-<li class="level1"><div class="li"> Select <strong>Edit | Slot…</strong></div>
-</li>
-<li class="level1"><div class="li"> Change the â??slot=nâ?? value in the â??Edit slot numberâ?? dialog box</div>
-</li>
-<li class="level1"><div class="li"> Press OK</div>
-</li>
-</ul>
-
-<p>
- Note that selecting the slot on a package often effects the layout of the printed circuit board, as the slot may be on the wrong side of the package for effecient routing of nets. Donâ??t worry, you can always come back and change the slot selection once you start laying out your board and know which slots route best.
-</p>
-
-</div>
-<!-- SECTION "Slot... (e shift-s)" [69949-71165] -->
-<h3><a name="color..._eo" id="color..._eo">Color... (eo)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Edit | Color…</strong> allows you to change the color of any selected object (with the exception of components).<br/>
- To change the color of the currently selected objects:
-</p>
-<ul>
-<li class="level1"><div class="li"> Select the desired object(s) (i.e., in <strong>Select Mode</strong>)</div>
-</li>
-<li class="level1"><div class="li"> Select <strong>Edit | Color…</strong></div>
-</li>
-<li class="level1"><div class="li"> The â??Edit | Color Editâ?? dialog box, with a drop down list for colors, will appear:</div>
-<ul>
-<li class="level2"><div class="li"> 1 | pin | black</div>
-</li>
-<li class="level2"><div class="li"> 2 | net endpoint | red</div>
-</li>
-<li class="level2"><div class="li"> 3 | graphic | green4</div>
-</li>
-<li class="level2"><div class="li"> 4 | net | blue2</div>
-</li>
-<li class="level2"><div class="li"> 5 | attribute | black</div>
-</li>
-<li class="level2"><div class="li"> 6 | logic bubble | DarkCyan</div>
-</li>
-<li class="level2"><div class="li"> 8 | detached attribute | red</div>
-</li>
-<li class="level2"><div class="li"> 9 | text | green4</div>
-</li>
-<li class="level2"><div class="li"> 10 | bus | green2</div>
-</li>
-<li class="level2"><div class="li"> 11 | select | firebrick</div>
-</li>
-<li class="level2"><div class="li"> 12 | bounding box | orange</div>
-</li>
-<li class="level2"><div class="li"> 13 | zoom box | DarkCyan</div>
-</li>
-<li class="level2"><div class="li"> 14 | stroke | grey90</div>
-</li>
-<li class="level2"><div class="li"> 15 | lock | grey40</div>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"> Pick the new color</div>
-</li>
-<li class="level1"><div class="li"> Press Apply</div>
-</li>
-</ul>
-
-<p>
- The color change will take effect once you press Apply.<br/>
- You can leave this dialog box up and select other objects and change their color by pressing Apply.
-</p>
-
-</div>
-<!-- SECTION "Color... (eo)" [71166-72124] -->
-<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">
-
-<p>
-<strong>Edit | Lock</strong> and <strong>Edit | Unlock</strong> allow you to lock/unlock components in a schematic. A locked component cannot be selected by a single click. To select locked component(s), drag a box around the component(s).<br/>
- Locking a component is useful for components such as title blocks, which should not be selectable because there are other objects inside its boundaries. If the titleblock was not locked, and you missed selecting a component by clicking it with the mouse, you would end up selecting the titleblock instead.<br/>
- Locking a component is also useful just to prevent it from being inadvertantly selected.<br/>
- To lock/unlock components:
-</p>
-<ul>
-<li class="level1"><div class="li"> Select the desired object(s) (i.e., in <strong>Select Mode</strong>)</div>
-</li>
-<li class="level1"><div class="li"> Select <strong>Edit | Lock</strong> or <strong>Edit | Unlock</strong></div>
-</li>
-</ul>
-
-<p>
- The locked/unlocked state of components is preserved when <strong>gschem</strong> exits, so components which were locked remain locked the next time the schematic is opened.<br/>
- You can lock and unlock regular objects (e.g., lines, pins, boxes…). This is nice when you are drawing something and an object is in the way. Just lock it, and you will not have to think about it when you click to select other objects. Locking an object is not preserved in the file format, so once you quit <strong>gschem</strong> any locked objects will be unlocked the next time the schematic is opened.<br/>
- Note that if a component is locked, you can not single-click to select a visible attribute, or double-click to select and edit a visible component. First unlock such locked components.
-</p>
-
-</div>
-<!-- SECTION "Lock (el) / Unlock (e shift-l)" [72125-73663] -->
-<h3><a name="line_width_type..._ew" id="line_width_type..._ew">Line Width & Type... (ew)</a></h3>
-<div class="level3">
-
-<p>
-The <strong>Edit | Line Width & Type…</strong> dialog box lets you control the width and type of lines, boxes, circles, and arcs on the schematic/symbol.<br/>
- To change the <strong>Line Width & Type…</strong>:
-</p>
-<ul>
-<li class="level1"><div class="li"> Select the desired object(s) (i.e., in <strong>Select Mode</strong>)</div>
-</li>
-<li class="level1"><div class="li"> Select <strong>Edit | Line Width & Type…</strong></div>
-</li>
-<li class="level1"><div class="li"> The â??Edit Line Width * Typeâ?? dialog box displays</div>
-</li>
-<li class="level1"><div class="li"> Change the following as suites the object:</div>
-<ul>
-<li class="level2"><div class="li"> Line Width</div>
-</li>
-<li class="level2"><div class="li"> Line Type</div>
-</li>
-<li class="level2"><div class="li"> Line Dash Length</div>
-</li>
-<li class="level2"><div class="li"> Line Dash Space</div>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"> Press OK to apply the changes</div>
-</li>
-</ul>
-
-<p>
- Note that if the line width doesnâ??t seem to change, just pick a larger value.
-</p>
-
-</div>
-<!-- SECTION "Line Width & Type... (ew)" [73664-74279] -->
-<h3><a name="fill_type..._ef" id="fill_type..._ef">Fill Type... (ef)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Edit | Fill Type…</strong> is used to fill boxes and circles.<br/>
- To fill a box or circle:
-</p>
-<ul>
-<li class="level1"><div class="li"> Select the box or circle.</div>
-</li>
-<li class="level1"><div class="li"> Select <strong>Edit | Fill Type…</strong>. The â??Edit FIll Typeâ?? dialog box is displayed.</div>
-</li>
-<li class="level1"><div class="li"> Enter:</div>
-<ul>
-<li class="level2"><div class="li"> Fill Type</div>
-</li>
-<li class="level2"><div class="li"> Line Width</div>
-</li>
-<li class="level2"><div class="li"> Angle 1</div>
-</li>
-<li class="level2"><div class="li"> Pitch 1</div>
-</li>
-<li class="level2"><div class="li"> Angle 2</div>
-</li>
-<li class="level2"><div class="li"> Pitch 2</div>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"> Press OK.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Fill Type... (ef)" [74280-74620] -->
-<h3><a name="symbol_translate..._et" id="symbol_translate..._et">Symbol Translate... (et)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Edit | Symbol Translate…</strong> is used when creating a symbol, to translate the symbol to an origin for subsequent placement. The symbol may take an optional offset (in mils), as appropriate to the symbol.<br/>
- To translate the symbol:
-</p>
-<ul>
-<li class="level1"><div class="li"> Open a file for the symbol</div>
-</li>
-<li class="level1"><div class="li"> Set the grid snap spacing to 100 mils (<strong>Options</strong> | <strong>Snap Grid Spacing…</strong>).</div>
-</li>
-<li class="level1"><div class="li"> Toggle the grid ON (<strong>Options</strong> | <strong>Toggle Grid On/Off</strong>)</div>
-</li>
-<li class="level1"><div class="li"> Toggle the grid snap ON (<strong>Options</strong> | <strong>Toggle Snap On/Off</strong>)</div>
-</li>
-<li class="level1"><div class="li"> Zoom as appropriate for the symbolâ??s dimensions</div>
-</li>
-<li class="level1"><div class="li"> Draw the symbol, according to the recommendations in the <a href="http://www.geda.seul.org/docs/current/symbols/index.html"; class="urlextern" title="http://www.geda.seul.org/docs/current/symbols/index.html"; rel="nofollow">gEDA/gaf Symbol Creation Document</a></div>
-</li>
-<li class="level1"><div class="li"> Select <strong>Edit | Symbol Translate…</strong></div>
-</li>
-<li class="level1"><div class="li"> The â??Translateâ?? dialog box is displayed.</div>
-</li>
-<li class="level1"><div class="li"> Enter 0 to translate to the origin, or enter a value (in mils), positive or negative, to offset the symbol from the origin.</div>
-</li>
-<li class="level1"><div class="li"> Press OK to apply</div>
-</li>
-<li class="level1"><div class="li"> Save the symbol to the file</div>
-</li>
-</ul>
-
-<p>
- If you enter a 0, then all the objects will be translated to the origin.<br/>
- If you enter a non-zero offset, this will be applied equally in both the X and the Y directions.<br/>
-
-</p>
-
-</div>
-<!-- SECTION "Symbol Translate... (et)" [74621-75785] -->
-<h3><a name="embed_component_picture_eb" id="embed_component_picture_eb">Embed Component/Picture (eb)</a></h3>
-<div class="level3">
-
-<p>
-<strong>gschem</strong> supports the concept of embedded components and graphics, where all the information necessary to display a component/graphic is placed in the schematic file. <strong>Edit | Embed Component/Picture</strong> causes schematic files to be significantly larger, but it makes it easy to share schematics with other people or archive schematics. You should only embed components when absolutely necessary.<br/>
- To <strong>Embed Component/Picture</strong>:
-</p>
-<ul>
-<li class="level1"><div class="li"> Select the component/picture (in <strong>Select Mode</strong>)</div>
-</li>
-<li class="level1"><div class="li"> Select <strong>Edit | Embed Component/Picture</strong></div>
-</li>
-</ul>
-
-<p>
- Save the schematic. The schematic file will now contain the text strings for the embedded component or embedded graphic.<br/>
- The <strong>Add Component…</strong> dialog box allows you to optionally embed the component.<br/>
- The <strong>Add Picture…</strong> dialog box does NOT allow you to optionally embed the component.<br/>
- You can only embed and unembed components. Also, you cannot embed and then mirror a component (this is a limitation of <strong>gschem</strong> and will eventually be fixed).
-</p>
-
-</div>
-<!-- SECTION "Embed Component/Picture (eb)" [75786-76815] -->
-<h3><a name="unembed_component_picture_eu" id="unembed_component_picture_eu">Unembed Component/Picture (eu)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Edit | Unembed Component/Picture</strong> will move the componentâ??s or graphicâ??s information from the schematic fileâ??s contents and output it to the original fileâ??s path/filename (i.e., the schematic file includes the path/filename information). To <strong>Unembed Component/Picture</strong>:
-</p>
-<ul>
-<li class="level1"><div class="li"> Select the component/picture (in <strong>Select Mode</strong>)</div>
-</li>
-<li class="level1"><div class="li"> Select <strong>Edit | Unembed Component/Picture</strong></div>
-</li>
-</ul>
-
-<p>
- Save the schematic. The schematic file will now NOT contain the text strings for the embedded component or embedded graphic.<br/>
- You can only embed and unembed components.
-</p>
-
-</div>
-<!-- SECTION "Unembed Component/Picture (eu)" [76816-77405] -->
-<h3><a name="update_component_ep" id="update_component_ep">Update Component (ep)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Edit | Update Component</strong> updates a componentâ??s definition.<br/>
- A symbol can be modified from within <strong>gschem</strong> using the following sequence:
-</p>
-<ul>
-<li class="level1"><div class="li"> Select the component for which the symbol should be changed.</div>
-</li>
-<li class="level1"><div class="li"> Select <strong>Hierarchy | Down Symbol</strong>. This takes you to the symbol editor</div>
-</li>
-<li class="level1"><div class="li"> Modify the symbol. This includes modifying the symbolâ??s graphic objects, adding/changing/deleting attributes, and moving objects with respect to the origin</div>
-</li>
-<li class="level1"><div class="li"> Donâ??t forget to <strong>Edit | Symbol Translate</strong></div>
-</li>
-<li class="level1"><div class="li"> Select <strong>File | Save Page</strong> to save the symbol to itâ??s file</div>
-</li>
-<li class="level1"><div class="li"> Select <strong>Hierarchy | Up Symbol</strong>. This returns you to the schematic editor</div>
-</li>
-<li class="level1"><div class="li"> With the component still selected, select <strong>Edit | Update Component</strong> to update the componetâ??s description from the modified symbolâ??s definition</div>
-</li>
-<li class="level1"><div class="li"> Select each component on the schematic(s) made from this symbol, and select <strong>Edit | Update Component</strong></div>
-</li>
-</ul>
-
-<p>
- New components placed on the schematic from this updated symbol will use the new symbol definition.<br/>
- Components placed on the schematic from this symbol will be updated the next time this schematic is opened.<br/>
- The symbolâ??s <code>symversion</code> attribute will automatically be incremented for non-trivial changes when the symbol is saved. When a schematic is opened by <strong>gschem</strong>, all symbols used by the schematic are read from their libraries. The <code>symversion</code> attribute of the symbol read from the library is compared to the <code>symversion</code> attribute of the components in the schematic. If the <code>symversion</code> attributes are different, the <code>symversion</code> attribute is exposed on the schematic for those symbols effected. Note that:
-</p>
-<ul>
-<li class="level1"><div class="li"> This is a â??hintâ?? to the designer to check the symbol.</div>
-</li>
-<li class="level1"><div class="li"> You need to actually open a schematic file with <strong>gschem</strong> for the components to be updated.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Update Component (ep)" [77406-79215] -->
-<h3><a name="show_hide_inv_text_en" id="show_hide_inv_text_en">Show/Hide Inv Text (en)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Edit | Show/Hide Inv Text</strong> is most appropriate when creating or editing symbols, to view or hide the text for all of the symbolâ??s invisible attributes.<br/>
- <a href="#make_inv_text_vis" title="geda:gschem_ug.fr ↵" class="wikilink1">Make Inv Text Vis</a> is most appropriate when adding symbols to schematics, to view the text for the symbolâ??s modifiable invisible attributes.<br/>
- <strong>Edit | Show/Hide Inv Text</strong> toggles between making all invisible text visible and hiding all invisible text. When selected, all objects in the symbol are effected.<br/>
- Visible text always remains visible.<br/>
- A symbol has the following <em class="u">potential</em> attributes :
-</p>
-<ul>
-<li class="level1"><div class="li"> netname</div>
-</li>
-<li class="level1"><div class="li"> refdes</div>
-</li>
-<li class="level1"><div class="li"> slot</div>
-</li>
-<li class="level1"><div class="li"> value</div>
-</li>
-<li class="level1"><div class="li"> net</div>
-</li>
-<li class="level1"><div class="li"> device</div>
-</li>
-<li class="level1"><div class="li"> pinnumber</div>
-</li>
-<li class="level1"><div class="li"> pinseq</div>
-</li>
-<li class="level1"><div class="li"> pintype</div>
-</li>
-<li class="level1"><div class="li"> pinlabel</div>
-</li>
-<li class="level1"><div class="li"> source</div>
-</li>
-<li class="level1"><div class="li"> numslots</div>
-</li>
-<li class="level1"><div class="li"> slotdef</div>
-</li>
-<li class="level1"><div class="li"> graphical</div>
-</li>
-<li class="level1"><div class="li"> footprint</div>
-</li>
-<li class="level1"><div class="li"> description</div>
-</li>
-<li class="level1"><div class="li"> documentation</div>
-</li>
-<li class="level1"><div class="li"> symversion</div>
-</li>
-<li class="level1"><div class="li"> comment</div>
-</li>
-<li class="level1"><div class="li"> file</div>
-</li>
-<li class="level1"><div class="li"> model-name</div>
-</li>
-</ul>
-
-<p>
- Not all attributes need to be used to define a symbol (see the discussion of <a href="http://geda.seul.org/wiki/docs:20060124:gschem_ug:app_a"; class="wikilink2" title="docs:20060124:gschem_ug:app_a">Appendix A -- Heavy vs Light Symbol Libraries</a>). The <strong>gschem</strong> default is to define symbols as â??lightâ??, indicating that the symbol includes as few attributes as necessary to describe the symbol. â??lightâ?? symbols depend on the designer attaching additional descriptive attributes to the symbol when the symbol is placed on the schematic. For example: a â??lightâ?? symbol for a resistor might include just the graphic for a resistor, its pin attributes, and the â??refdesâ?? attribute. This describes a resistor. It would be the designerâ??s responsibility, after the resistor has been placed on the schematic, to add the â??valueâ?? and â??footprintâ?? attributes appropriate for the specific resistor in the circuit. A â??heavyâ?? symbol includes more descriptive attributes. Using â??lightâ?? vs. â??heavyâ?? symbols is up to the designer.<br/>
- A symbolâ??s attributes may be flagged as either visible or invisible. Attributes are flagged as invisible to reduce the clutter around a symbol on the schematic.<br/>
- When creating or editing the symbol, and changing a visible attribute to an invisible attribute, the attribute can not be viewed during further editing of the symbol. It becomes difficult to place attribute text. To view both the visible and invisible text, select <strong>Edit | Show/Hide Inv Text</strong>.<br/>
- When a symbol is instantiated on a schematic as a component, only the symbolâ??s visible attributes are promoted to the component. For example: if a resistorâ??s symbol defines â??refdesâ?? as the only visible attribute defined in the symbol, the only attribute that the component contains is the â??refdesâ?? attribute). Those attributes not included in the symbol definition may be added at the schematic level, component-by-component.<br/>
- This operation is useful when drawing/debugging symbols.<br/>
- When hidden text is visible, â??Show Hiddenâ?? will appear on the status-bar in the lower right.
-</p>
-
-</div>
-<!-- SECTION "Show/Hide Inv Text (en)" [79216-82043] -->
-<h3><a name="make_inv_text_vis_ev" id="make_inv_text_vis_ev">Make Inv Text Vis (ev)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Edit | Make Inv Text Vis</strong> is a quick method of making all of a componentâ??s invisible attributes visible. The same effect can be accomplished by double-clicking on the component and marking all of the entries in the Attributes listbox as â??Vis?" (i.e., visible).<br/>
- To <strong>Make Inv Text Vis</strong> for a component:
-</p>
-<ul>
-<li class="level1"><div class="li"> Select the component(s) in <strong>Select Mode</strong></div>
-</li>
-<li class="level1"><div class="li"> Select <strong>Edit | Make Inv Text Vis</strong></div>
-</li>
-</ul>
-
-<p>
- The attributes that had been hidden are displayed.<br/>
- To hide the attributes again, you need to double-click the component to bring up itâ??s â??Edit Attributesâ?? dialog box, and explicitly place a check for each attribute you want hidden.
-</p>
-
-</div>
-<!-- SECTION "Make Inv Text Vis (ev)" [82044-82707] -->
-<h2><a name="buffer" id="buffer">Buffer</a></h2>
-<div class="level2">
-
-<p>
-<strong>gschem</strong> supports 5 copy/cut/paste buffers which are visible across all opened pages and windows.
-</p>
-
-</div>
-<!-- SECTION "Buffer" [82708-82827] -->
-<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">
-
-<p>
-To copy something into a buffer:
-</p>
-<ol>
-<li class="level1"><div class="li"> Select the objects you want to copy.</div>
-</li>
-<li class="level1"><div class="li"> Select Buffer/Copy/Copy into buffer #.</div>
-</li>
-</ol>
-
-</div>
-<!-- SECTION "Copy into 1/2/3/4/5 (yc)" [82828-82980] -->
-<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">
-
-<p>
-Cut is like copy in that it removes the objects from the schematic
-</p>
-
-</div>
-<!-- SECTION "Cut into 1/2/3/4/5 (yu)" [82981-83082] -->
-<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">
-
-<p>
-To paste a buffer into the current schematic:
-</p>
-<ol>
-<li class="level1"><div class="li"> Fill the buffer using the above Copy or Cut.</div>
-</li>
-<li class="level1"><div class="li"> Go to the new schematic page/window.</div>
-</li>
-<li class="level1"><div class="li"> Select Buffer/Paste/Paste from buffer #.</div>
-</li>
-<li class="level1"><div class="li"> Click the first mouse button to pick an anchor point.</div>
-</li>
-<li class="level1"><div class="li"> Move the mouse to the final spot.</div>
-</li>
-<li class="level1"><div class="li"> Click the first mouse button again.</div>
-</li>
-</ol>
-
-</div>
-<!-- SECTION "Paste from 1/2/3/4/5 (yp)" [83083-83436] -->
-<h2><a name="view" id="view">View</a></h2>
-<div class="level2">
-
-</div>
-<!-- SECTION "View" [83437-83454] -->
-<h3><a name="redraw_vr" id="redraw_vr">Redraw (vr)</a></h3>
-<div class="level3">
-
-<p>
-<strong>View | Redraw</strong> re-paints the current window.<br/>
- This is useful when you have mouse/component/line/text etc… droppings left over from a previous action. It is also useful when you want to update all visual connectivity cues.
-</p>
-
-</div>
-<!-- SECTION "Redraw (vr)" [83455-83705] -->
-<h3><a name="pan_x" id="pan_x">Pan (x)</a></h3>
-<div class="level3">
-
-<p>
-<strong>View | Pan</strong> lets you change the focus of the display.<br/>
- To pan the display:
-</p>
-<ul>
-<li class="level1"><div class="li"> Select <strong>View | Pan</strong></div>
-</li>
-<li class="level1"><div class="li"> Click the first mouse button at the new center of the display.</div>
-</li>
-</ul>
-
-<p>
- To pan the display using the shortcut is much simpler, simply place the mouse pointer where you want the display centered and type â??xâ??. The display will jump to the mouseâ??s location.<br/>
- Pan behavior is configurable. The system-gschemrc file defines: <pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">(third-button "popup")</font></pre>
-</p>
-
-<p>
-If you override the system-gschemrcâ??s default, of popping up a menu when the third mouse button is clicked, by adding: <pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">(third-button "mousepan")</font></pre>
-</p>
-
-<p>
-to either your userâ??s ~/gschemrc file or local â??pwdâ??/gschemrc file, the third mouse button (i.e., the right mouse button on scroll-wheel mice) will allow you to pan the schematic by holding down the third mouse button and dragging.<br/>
- The system-gschemrc file also defines: <pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">(fast-mousepan "enabled")</font></pre>
-</p>
-
-<p>
-If you override the system-gschemrcâ??s default by adding: <pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">(fast-mousepan "disabled")</font></pre>
-</p>
-
-<p>
-to either your userâ??s ~/gschemrc file or local â??pwdâ??/gschemrc file, text will be displayed properly when the third mouse button is held down while dragging. The <code>(third-button â??mousepanâ??)</code> setting must also be applied for this to work. Disabling <code>fast-mousepan</code> adversely effects rendering speed while panning on large â??complicatedâ?? schematics.<br/>
- The system-gschemrc file also defines: <pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">(zoom-with-pan "enabled")</font></pre>
-</p>
-
-<p>
-If you override the system-gschemrcâ??s default by adding: <pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">(zoom-with-pan "disabled")</font></pre>
-</p>
-
-<p>
-to either your userâ??s ~/gschemrc file or local â??pwdâ??/gschemrc file, whenever you zoom in/out, the zoom will NOT center on the mouse pointer, effectively removing the pan feature of the zoom in/out operations.
-</p>
-
-</div>
-<!-- SECTION "Pan (x)" [83706-85502] -->
-<h3><a name="zoom_box_w" id="zoom_box_w">Zoom Box (w)</a></h3>
-<div class="level3">
-
-<p>
-<strong>View | Zoom Box</strong> allows you to draw a box around a part of the <strong>gschem</strong> window and zoom in.<br/>
- To use <strong>View | Zoom Box</strong>:
-</p>
-<ul>
-<li class="level1"><div class="li"> Select <strong>View | Zoom Box</strong></div>
-</li>
-<li class="level1"><div class="li"> Position the mouse pointer at one corner of the box you want to draw</div>
-</li>
-<li class="level1"><div class="li"> Click and hold down the first mouse button</div>
-</li>
-<li class="level1"><div class="li"> Drag the mouse, drawing the zoom box around the area to which you want to zoom</div>
-</li>
-<li class="level1"><div class="li"> Release the mouse button and the display will zoom</div>
-</li>
-</ul>
-
-<p>
- To use <strong>View | Zoom Box</strong> by typing the equivalent shortcut (i.e., â??<strong>w</strong>â??) is more convenient. Simply position the mouse pointer at one corner of the zoom box, then type â??<strong>w</strong>â??. The zoom box will start immediately using the current mouse location as the first corner of the box.<br/>
- <strong>View | Zoom Box</strong> will attempt to zoom to the requested area, but some boxes are not legal and <strong>gschem</strong> will do itâ??s best to zoom the requested area.
-</p>
-
-</div>
-<!-- SECTION "Zoom Box (w)" [85503-86383] -->
-<h3><a name="zoom_extents_ve" id="zoom_extents_ve">Zoom Extents (ve)</a></h3>
-<div class="level3">
-
-<p>
-<strong>View | Extents</strong> will zoom the display to fit all of the placed objects into the current window.<br/>
- To view all of the current windowâ??s objects:
-</p>
-<ul>
-<li class="level1"><div class="li"> Select <strong>View | Extents</strong></div>
-</li>
-</ul>
-
-<p>
- Typing the <strong>View | Extents</strong> shortcut (i.e., â??<strong>ve</strong>â??) is particularly convenient for those that have learned to navigate the schematics using the shortcuts.<br/>
-
-</p>
-
-</div>
-<!-- SECTION "Zoom Extents (ve)" [86384-86750] -->
-<h3><a name="zoom_in_z" id="zoom_in_z">Zoom In (z)</a></h3>
-<div class="level3">
-
-<p>
-<strong>View | Zoom In</strong> zooms the display in. The current center of the window is the center of the new window. This command zooms in by a factor.<br/>
- To zoom in:
-</p>
-<ul>
-<li class="level1"><div class="li"> Select <strong>View | Zoom In</strong></div>
-</li>
-</ul>
-
-<p>
- The (zoom-with-pan â??enabledâ??) configuration setting in the gschemrc files effects the operation of the zoom in shortcut (i.e., â??<strong>z</strong>â??). The default system-gschemrc setting for: <pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">(zoom-with-pan "enabled")</font></pre>
-</p>
-
-<p>
-enables zooming in, using the mouse pointerâ??s location as the new center of the window. If this changed to: <pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">(zoom-with-pan "disabled")</font></pre>
-</p>
-
-<p>
-in either your userâ??s ~/gschemrc file or local â??pwdâ??/gschemrc file, whenever you zoom in, the zoom will NOT center on the mouse pointer but will center on the current center of the window, effectively removing the pan feature of the zoom in operation.<br/>
- To zoom in using the shortcut:
-</p>
-<ul>
-<li class="level1"><div class="li"> If the default (zoom-with-pan â??enabledâ??) is configured in one of the gschemrc files, position the mouse pointer in the window where you want the new center</div>
-</li>
-<li class="level1"><div class="li"> Type â??<strong>z</strong>â??</div>
-</li>
-</ul>
-
-<p>
- Typing â??<strong>z</strong>â?? is particularly convenient for those that have learned to navigate the schematics using the shortcuts.
-</p>
-
-</div>
-<!-- SECTION "Zoom In (z)" [86751-87912] -->
-<h3><a name="zoom_out_z" id="zoom_out_z">Zoom Out (Z)</a></h3>
-<div class="level3">
-
-<p>
-<strong>View | Zoom Out</strong> zooms the display out. The current center of the window is the center of the new window. This command zooms out by a factor.<br/>
- To zoom out:
-</p>
-<ul>
-<li class="level1"><div class="li"> Select <strong>View | Zoom Out</strong></div>
-</li>
-</ul>
-
-<p>
- The (zoom-with-pan â??enabledâ??) configuration setting in the gschemrc files effects the operation of the zoom out shortcut (i.e., â??<strong>z</strong>â??). The default system-gschemrc setting for: <pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">(zoom-with-pan "enabled")</font></pre>
-</p>
-
-<p>
-enables zooming out, using the mouse pointerâ??s location as the new center of the window. If this changed to: <pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">(zoom-with-pan "disabled")</font></pre>
-</p>
-
-<p>
-in either your userâ??s ~/gschemrc file or local â??pwdâ??/gschemrc file, whenever you zoom out, the zoom will NOT center on the mouse pointer but will center on the current center of the window, effectively removing the pan feature of the zoom out operation.<br/>
- To zoom out using the shortcut:
-</p>
-<ul>
-<li class="level1"><div class="li"> If the default (zoom-with-pan â??enabledâ??) is configured in one of the gschemrc files, position the mouse pointer in the window where you want the new center</div>
-</li>
-<li class="level1"><div class="li"> Type â??<strong>Z</strong>â?? (i.e., shift-z)</div>
-</li>
-</ul>
-
-<p>
- Typing â??<strong>Z</strong>â?? is particularly convenient for those that have learned to navigate the schematics using the shortcuts.
-</p>
-
-</div>
-<!-- SECTION "Zoom Out (Z)" [87913-89101] -->
-<h3><a name="zoom_full_vf" id="zoom_full_vf">Zoom Full (vf)</a></h3>
-<div class="level3">
-
-<p>
-<strong>View | Zoom Full</strong> will zoom the display to the maximum possible displayable view.<br/>
-
-</p>
-
-<p>
-To view the maximum displayable area:
-</p>
-<ul>
-<li class="level1"><div class="li"> Select <strong>View | Zoom Full</strong></div>
-</li>
-</ul>
-
-<p>
- The window contents will immediately change to show the maximum possible displayable view.<br/>
-
-</p>
-
-<p>
-To view the maximum displayable area using the keyboard shortcut (i.e., â??<strong>vf</strong>â??):
-</p>
-<ul>
-<li class="level1"><div class="li"> Type â??<strong>vf</strong>â??</div>
-</li>
-</ul>
-
-<p>
- The window contents will immediately change to show the maximum possible displayable view.<br/>
-
-</p>
-
-<p>
-<strong>View | Zoom Full</strong> is useful if you like to put your working notes outside the titleblock for you schematic, for example. Just remember, these notes would now be considered part of the windows extents, so if you were to <strong>View | Extents</strong>, the display would show the titleblock and your working notes.
-</p>
-
-</div>
-<!-- SECTION "Zoom Full (vf)" [89102-89880] -->
-<h2><a name="page" id="page">Page</a></h2>
-<div class="level2">
-
-</div>
-<!-- SECTION "Page" [89881-89899] -->
-<h3><a name="manager..._pm" id="manager..._pm">Manager... (pm)</a></h3>
-<div class="level3">
-
-</div>
-<!-- SECTION "Manager... (pm)" [89900-89927] -->
-<h3><a name="next" id="next">Next (>)</a></h3>
-<div class="level3">
-
-</div>
-<!-- SECTION "Next (>)" [89928-89948] -->
-<h3><a name="previous" id="previous">Previous (<)</a></h3>
-<div class="level3">
-
-</div>
-<!-- SECTION "Previous (<)" [89949-89973] -->
-<h3><a name="new_pe" id="new_pe">New (pe)</a></h3>
-<div class="level3">
-
-</div>
-<!-- SECTION "New (pe)" [89974-89994] -->
-<h3><a name="revert_pr" id="revert_pr">Revert (pr)</a></h3>
-<div class="level3">
-
-</div>
-<!-- SECTION "Revert (pr)" [89995-90018] -->
-<h3><a name="close_pc" id="close_pc">Close (pc)</a></h3>
-<div class="level3">
-
-</div>
-<!-- SECTION "Close (pc)" [90019-90041] -->
-<h3><a name="discard_pd" id="discard_pd">Discard (pd)</a></h3>
-<div class="level3">
-
-</div>
-<!-- SECTION "Discard (pd)" [90042-90066] -->
-<h2><a name="add" id="add">Add</a></h2>
-<div class="level2">
-
-</div>
-<!-- SECTION "Add" [90067-90083] -->
-<h3><a name="component..._i" id="component..._i">Component... (i)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Add | Component…</strong> Ouvre une boîte de dialogue qui vous
-</p>
-<pre class="code">permet de placer les composants depuis les bibliothèques de composants.\\</pre>
-
-<p>
-Pour placer un composant:
-</p>
-<ul>
-<li class="level1"><div class="li"> Select <strong>Add |Component…</strong></div>
-</li>
-<li class="level1"><div class="li"> Select a component Library from the left list-box</div>
-</li>
-<li class="level1"><div class="li"> Sélectionnez un Composant dans la liste de droite</div>
-</li>
-<li class="level1"><div class="li"> Confirm the symbol is correct by reviewing the image in the Preview window</div>
-</li>
-<li class="level1"><div class="li"> Move the mouse into the main drawing window (you should see an outline follow the mouse pointer).</div>
-</li>
-<li class="level1"><div class="li"> Press the first mouse button to anchor the component</div>
-</li>
-<li class="level1"><div class="li"> Position the mouse pointer, and keep pressing the first mouse button to anchor additional instances of the component</div>
-</li>
-<li class="level1"><div class="li"> When finished anchoring components, press the last mouse button or the ESC key</div>
-</li>
-</ul>
-
-<p>
- Si un nom de composant est déjà sélectionné, taper Appliquer et déplacer la souris dans la fenêtre principale vous permettra placer à nouveau ce composant.<br/>
- Vous pouvez effectuer une rotation avant le placement du composant en cliquant sur le bouton du milieu. Pour chaque clic de bouton, le composant effectuera une rotation de 90 degrésdans le sens inverse des aiguilles.<br/>
- Care has been taken to give components descriptive names in the libraries, though it is sometimes difficult to determine what the component really represents from its name.<br/>
- For example: in the analog library there are four capacitor entries:
-</p>
-<ul>
-<li class="level1"><div class="li"> capacitor-1.sym</div>
-</li>
-<li class="level1"><div class="li"> capacitor-2.sym</div>
-</li>
-<li class="level1"><div class="li"> capacitor-3.sym</div>
-</li>
-<li class="level1"><div class="li"> capacitor-4.sym</div>
-</li>
-</ul>
-
-<p>
- It helps to preview the symbol in the â??Select Componentâ?? dialog box before selecting and placing the symbol.
-</p>
-
-</div>
-<!-- SECTION "Component... (i)" [90084-91682] -->
-<h3><a name="net_n" id="net_n">Net (n)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Net</strong> Dessine un nouveau segment de liaison.<br/>
- A net is typically a contiguous set of line segments between two pins, though it is possible to draw nets between a pin and a point on another net, or between two nets.<br/>
- For example, the following diagram shows 3 net segments:
-</p>
-<ul>
-<li class="level1"><div class="li"> Between R1 and R2</div>
-</li>
-<li class="level1"><div class="li"> Between R3 and R4</div>
-</li>
-<li class="level1"><div class="li"> Between the two nets</div>
-</li>
-</ul>
-<table class="inline">
- <tr>
- <td> <a href="_detail/001geda_nets.html" class="media" title="geda:nets.jpg"><img src="http://geda.seul.org/wiki/_media/geda:nets.jpg?w=&h=&cache=cache"; class="media" title="nets.jpg" alt="nets.jpg" /></a> </td>
- </tr>
-</table>
-
-<p>
- Note the small red segment at the end of the resistorâ??s pins. All pins in <strong>gschem</strong> have this red segment. This is the connectivity cue for the pin. It is sometimes difficult to â??grabâ?? this attachment point when drawing nets, you may need to zoom in on the pin. To zoom in, press the â??zâ?? key. To zoom out, press the â??Zâ?? (i.e., shift-z) key.<br/>
- To begin drawing a net using the menu:
-</p>
-<ul>
-<li class="level1"><div class="li"> Select <strong>Add | Net</strong></div>
-</li>
-<li class="level1"><div class="li"> Zoom in on the component where the net is to start, so that you can easily grab the pinâ??s attachment point</div>
-</li>
-<li class="level1"><div class="li"> Position the mouse pointer over the pinâ??s connectivity cue</div>
-</li>
-<li class="level1"><div class="li"> Press the first mouse button to start the net</div>
-</li>
-</ul>
-
-<p>
- To begin drawing the net using the shortcut:
-</p>
-<ul>
-<li class="level1"><div class="li"> Zoom in on the component where the net is to start, so that you can easily grab the pinâ??s attachment point</div>
-</li>
-<li class="level1"><div class="li"> Position the mouse pointer over the pinâ??s connectivity cue</div>
-</li>
-<li class="level1"><div class="li"> Press the â??nâ?? key</div>
-</li>
-</ul>
-
-<p>
- To continue drawing the net segment(s):
-</p>
-<ul>
-<li class="level1"><div class="li"> Drag the mouse pointer in the direction of the end-point</div>
-</li>
-<li class="level1"><div class="li"> For any necessary 90º turns, single-click the mouse, and continue dragging the mouse pointer toward the end-point</div>
-</li>
-<li class="level1"><div class="li"> For any necessary non-orthogonal net segments (e.g., 45º angle), hold down the CONTROL button, single-click the mouse, and continue dragging the mouse pointer to the end-point</div>
-</li>
-<li class="level1"><div class="li"> When you reach the end-point, press the first mouse button to end the net segment</div>
-</li>
-<li class="level1"><div class="li"> Another net segment will start at the last end-point</div>
-<ul>
-<li class="level2"><div class="li"> If this second pin is to be connected to a third pin, continue as above</div>
-</li>
-<li class="level2"><div class="li"> If this is the end of the connections, press the last mouse button (or ESC) to end the net</div>
-</li>
-</ul>
-</li>
-</ul>
-
-<p>
- Appuyez sur le dernier bouton de souris ou sur ESC pour effacer toute liaison en cours.<br/>
- If the net is cancelled you are automatically placed in <strong>Select Mode</strong>. You must pick <strong>Add | Net</strong> again or type the shortcut to add more nets.<br/>
- You cannot connect a net segment to the middle of a non-orthogonal net.<br/>
- The boxes at the end of the nets are connectivity cues. Red boxes signify a dangling net (not connected to anything).<br/>
- Filled circles are midpoint connections/junctions. These cues are drawn automatically and are an indicator of electrical connectivity.<br/>
- See <a href="http://geda.seul.org/wiki/docs:20060124:gschem_ug:electrical_connectivity"; class="wikilink2" title="docs:20060124:gschem_ug:electrical_connectivity">Electrical Connectivity</a> for more information.
-</p>
-
-</div>
-<!-- SECTION "Net (n)" [91683-94314] -->
-<h3><a name="bus_u" id="bus_u">Bus (u)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Add | Bus</strong> est basiquement la même chose que <strong>Add | Net</strong>, except that it draws buses.<br/>
- Buses are very new and there are many aspects which are not defined yet, so keep that in mind as you uses buses. More to be added here eventually.
-</p>
-
-</div>
-<!-- SECTION "Bus (u)" [94315-94574] -->
-<h3><a name="attribute..._aa" id="attribute..._aa">Attribute... (aa)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Add | Attribute…</strong> is appropriate when creating or editing symbols, to add a new attribute.<br/>
- <strong>Add | Attribute…</strong> brings up the â??Single Attribute Editorâ?? dialog box. This dialog box is ONLY used to add attributes. It does not display or manipulate already placed attributes.<br/>
- Un attribut nâ??est rien de plus quâ??un objet texte qui est de la forme name=value (Il ne peut y avoir dâ??espace à gauche et à droite de la paire name,value). Il peut soit être attaché à un objet ou détaché.<br/>
- Pour attacher un attribut détaché (e.g., â??commentâ??, â??documentationâ??, etc.) au symbole:
-</p>
-<ul>
-<li class="level1"><div class="li"> Select <strong>Add | Attribute…</strong></div>
-</li>
-<li class="level1"><div class="li"> Select an attribute name off of the pulldown list, or type the attribute name into the name entry</div>
-</li>
-<li class="level1"><div class="li"> Saisissez la valeur pour lâ??attribut</div>
-</li>
-<li class="level1"><div class="li"> Pick any of the attribute options</div>
-</li>
-<li class="level1"><div class="li"> Cliquez sur OK et lâ??attribut sera placé.</div>
-</li>
-</ul>
-
-<p>
- Si vous voulez attacher un attribut à un objet, sélectionnez dâ??abord lâ??objet souhaité et pressez ensuite <strong>Add | Attribute…</strong> depuis le menu déroulant. Si vous cliquez sur un objet qui possède des attributs attachés, ils doivent être aussi sélectionnés.<br/>
- Si vous sélectionnez <strong>Add | Attribute…</strong> en dehors des menus déroulants alors vous nâ??avez pas beaucoup de contrôle sur le placement de lâ??attribut (il prend place soit en bas à gauche de lâ??extension de lâ??objet soit à lâ??origine de tout objet sélectionné). Si vous exécutez néanmoins Add/Attribute (i.e., â??aaâ??) en utilisant la touche de raccourci alors la position courante de la souris est utilisé comme point dâ??encrage pour lâ??objet attribut.<br/>
- Vous ne pouvez pas placer un attribut incomplet (un attribut sans nom et sans valeur).<br/>
- Please see <a href="http://geda.seul.org/wiki/docs:20060124:gschem_ug:components_symbols_objects_attributes"; class="wikilink2" title="docs:20060124:gschem_ug:components_symbols_objects_attributes">Components/Symbols/Objects/Attributes</a> for more info on how to use attributes.
-</p>
-
-</div>
-<!-- SECTION "Attribute... (aa)" [94575-96381] -->
-<h3><a name="text..._at" id="text..._at">Text... (at)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Add | Text…</strong> displays the â??Text Entry…â?? dialog box. To place text:
-</p>
-<ul>
-<li class="level1"><div class="li"> Select <strong>Options | Text Size…</strong> and select the size for the text</div>
-</li>
-<li class="level1"><div class="li"> Select <strong>Add | Text…</strong></div>
-</li>
-<li class="level1"><div class="li"> Type the text in the entry field (multiple lines may be entered by pressing Enter)</div>
-</li>
-<li class="level1"><div class="li"> Press Apply or type Enter</div>
-</li>
-<li class="level1"><div class="li"> Déplacez la souris dans la fenêtre principale (un soulignement de texte devrait apparaître et suivre </div>
-</li>
-</ul>
-
-<p>
-la souris)
-</p>
-<ul>
-<li class="level1"><div class="li"> Pressez le premier bouton de souris pour ancrer le texte</div>
-</li>
-<li class="level1"><div class="li"> Close the â??Text Entry…â?? dialog box</div>
-</li>
-</ul>
-
-<p>
- Si vous laissez la boîte de dialogue dâ??ajout de texte (<strong>Add | Text…</strong>) ouverte, vous pouvez replacer le même objet texte encore et encore en cliquant simplement sur apply (ou en pressant enter) et en déplaçant la souris dans la fenêtre principale.<br/>
- The following settings in the system-gschemrc file, the userâ??s ~/gschemrc file, or the local â??pwdâ??/gschemrc file control how text is displayed:</p>
-<dl>
-<dt><span class='term'> text-origin-marker</span></dt>
-<dd>Controls if the text origin markers are displayed.</dd>
-<dt><span class='term'> text-size</span></dt>
-<dd>Sets the default text size.</dd>
-<dt><span class='term'> text-caps-style</span></dt>
-<dd>Sets the default caps style used for the display of text</dd>
-<dt><span class='term'> output-text</span></dt>
-<dd>Controls how text is rendered to postscript</dd>
-</dl>
-<p>Le texte placé débutera automatiquement avec une majuscule. Veuillez voir la section Fichiers Ressource ci-dessous sur comment contrôler ce comportement.<br/>
- Pour effacer un emplacement de texte, pressez le dernier bouton de souris ou sur la touche ESC.<br/>
- Si vous créez du texte dans la forme name=value alors vous êtes en cours de création dâ??attributs. gEDA permet aux attributs généraux de flotter librement (ou détachés). Câ??est une bonne idée de changer la couleur de ces attributs flottants à la couleur des attributs courants (qui est aussi appelée couleur dâ??attribut attaché) pour indiquer que le lâ??objet texte est un attribut.<br/>
- Vous pouvez faire pivoter le texte avant de le placer en cliquant sur le bouton milieu. Pour chaque clic de bouton, le texte fera une rotation de 90 degrés.<br/>
-
-</p>
-
-</div>
-<!-- SECTION "Text... (at)" [96382-98392] -->
-<h3><a name="line_l" id="line_l">Line (l)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Add | Line</strong> draws a single line segment.<br/>
- To draw a line:
-</p>
-<ul>
-<li class="level1"><div class="li"> If you want to snap the line to the grid, set the grid spacing by selecting <strong>Options | Snap Grid Spacing…</strong> and entering the grid spacing, and then selecting <strong>Options | Toggle Snap On/Off</strong> until you donâ??t see â??Snap Offâ?? on the status-bar</div>
-</li>
-<li class="level1"><div class="li"> Select <strong>Add | Line</strong></div>
-</li>
-<li class="level1"><div class="li"> If you want to constrain the line to 90º movements, hold the CONTROL key down while moving the mouse</div>
-</li>
-<li class="level1"><div class="li"> Position the mouse pointer to the start-point</div>
-</li>
-<li class="level1"><div class="li"> Press the first mouse button</div>
-</li>
-<li class="level1"><div class="li"> Move the mouse in the intended direction</div>
-</li>
-<li class="level1"><div class="li"> When positioned at the end-point, press the first mouse button</div>
-</li>
-<li class="level1"><div class="li"> Continue placing lines, until you either press the second mouse button or type the Escape key</div>
-</li>
-</ul>
-
-<p>
- <strong>Add | Line</strong> dessine une ligne de la même manière quâ??en dessinant les réseaux avec les exceptions suivantes:
-</p>
-<ul>
-<li class="level1"><div class="li"> Une ligne nâ??a pas de signification électrique</div>
-</li>
-<li class="level1"><div class="li"> Seule un segment de ligne est dessiné</div>
-</li>
-<li class="level1"><div class="li"> Vous gardez les lignes dessinées tant que vous êtes dans le mode de dessin de lignes (<strong>Line Mode</strong>).</div>
-</li>
-</ul>
-
-<p>
- Pour effacer une ligne directe en cours, pressez le dernier bouton de souris ou la touche ESC.
-</p>
-
-</div>
-<!-- SECTION "Line (l)" [98393-99561] -->
-<h3><a name="box_b" id="box_b">Box (b)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Add | Box</strong> draws a box. To draw a box:
-</p>
-<ul>
-<li class="level1"><div class="li"> If you want to snap the box to the grid, set the grid spacing by selecting <strong>Options | Snap Grid Spacing…</strong> and entering the grid spacing, and then selecting <strong>Options | Toggle Snap On/Off</strong> until you donâ??t see â??Snap Offâ?? on the status-bar</div>
-</li>
-<li class="level1"><div class="li"> Select <strong>Add | Box</strong></div>
-</li>
-<li class="level1"><div class="li"> Position the mouse pointer to the start-point</div>
-</li>
-<li class="level1"><div class="li"> Press the first mouse button</div>
-</li>
-<li class="level1"><div class="li"> Move the mouse in the intended direction</div>
-</li>
-<li class="level1"><div class="li"> When positioned at the end-point, press the first mouse button again</div>
-</li>
-<li class="level1"><div class="li"> Continue placing boxes, until you either press the second mouse button or type the ESC key</div>
-</li>
-</ul>
-
-<p>
- To cancel a box in progress, press the last mouse button or type the ESC key.<br/>
- A box has no electrical significance.
-</p>
-
-</div>
-<!-- SECTION "Box (b)" [99562-100314] -->
-<h3><a name="circle_ai" id="circle_ai">Circle (ai)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Add | Circle</strong> creates a circle.<br/>
- To draw a circle:
-</p>
-<ul>
-<li class="level1"><div class="li"> If you want to snap the box to the grid, set the grid spacing by selecting <strong>Options | Snap Grid Spacing…</strong> and entering the grid spacing, and then selecting <strong>Options | Toggle Snap On/Off</strong> until you donâ??t see â??Snap Offâ?? on the status-bar</div>
-</li>
-<li class="level1"><div class="li"> Select <strong>Add | Circle</strong></div>
-</li>
-<li class="level1"><div class="li"> Placez le centre du cercle </div>
-</li>
-<li class="level1"><div class="li"> Pressez le premier bouton</div>
-</li>
-<li class="level1"><div class="li"> Déplacez la souris pour voir un surlignement du cercle</div>
-</li>
-<li class="level1"><div class="li"> Pressez le premier bouton de souris pour terminer le cercle</div>
-</li>
-<li class="level1"><div class="li"> Continue placing circles, until you either press the second mouse button or type the ESC key</div>
-</li>
-</ul>
-
-<p>
- Pour dessiner un cercle (en utilisant le raccourci clavier), identique à au-dessus excepté que ce centre du cercle est pris sur la dernière position de souris lorsque vous saisissez le raccourci.<br/>
- Pour effacer un dessin de cercle en cours, pressez sur le dernier bouton de souris ou sur la touche ESC.<br/>
-
-</p>
-
-</div>
-<!-- SECTION "Circle (ai)" [100315-101265] -->
-<h3><a name="arc_ar" id="arc_ar">Arc (ar)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Add | Arc</strong> draws an arc. Pour dessiner un arc:
-</p>
-<ul>
-<li class="level1"><div class="li"> If you want to snap the box to the grid, set the grid spacing by selecting <strong>Options | Snap Grid Spacing…</strong> and entering the grid spacing, and then selecting <strong>Options | Toggle Snap On/Off</strong> until you donâ??t see â??Snap Offâ?? on the status-bar</div>
-</li>
-<li class="level1"><div class="li"> Select <strong>Add | Arc</strong></div>
-</li>
-<li class="level1"><div class="li"> Place the mouse pointer at the center-point for the arc</div>
-</li>
-<li class="level1"><div class="li"> Press the first mouse button</div>
-</li>
-<li class="level1"><div class="li"> Move the mouse to the right, to define the radius of the arc</div>
-</li>
-<li class="level1"><div class="li"> Press the first mouse button again</div>
-</li>
-<li class="level1"><div class="li"> Enter the Start Angle (in degrees) – 0º is the â??xâ?? axis</div>
-</li>
-<li class="level1"><div class="li"> Enter the Degrees of Sweep (for counter-clockwise sweep)</div>
-</li>
-<li class="level1"><div class="li"> Press OK</div>
-</li>
-<li class="level1"><div class="li"> Continue placing arcs, until you either press the second mouse button or type the ESC key</div>
-</li>
-</ul>
-
-<p>
- Lâ??angle de démarrage peut être positif ou négatif. Les degrés sont spécifiés en utilisant le système des coordonnées Cartésiennes standard. Les degrés de sweep peuvent être positifs ou négatifs.<br/>
- Pour effacer un arc en cours de dessin (lorsquâ??il y a le rayon) pressez le dernier bouton de souris ou la touche ESC ou pressez le bouton Cancel dans la boîte de dialogue arc.
-</p>
-
-</div>
-<!-- SECTION "Arc (ar)" [101266-102426] -->
-<h3><a name="pin_ap" id="pin_ap">Pin (ap)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Add | Pin</strong> adds a pin.<br/>
- Though you can <strong>Add | Pin</strong> while entering a schematic, it only makes sense to create pins while creating or editing symbol files.<br/>
- To draw a pin:
-</p>
-<ul>
-<li class="level1"><div class="li"> Set the grid spacing by selecting <strong>Options | Snap Grid Spacing…</strong> and entering the grid spacing, and then selecting <strong>Options | Toggle Snap On/Off</strong> until you donâ??t see â??Snap Offâ?? on the status-bar. The <a href="http://www.geda.seul.org/docs/current/symbols/symbols.pdf"; class="urlextern" title="http://www.geda.seul.org/docs/current/symbols/symbols.pdf"; rel="nofollow">gEDA/gaf Symbol Creation Document</a> specifies grid settings for pin placement in gEDA/gaf compliant symbols files.</div>
-</li>
-<li class="level1"><div class="li"> Select <strong>Add | Pin</strong></div>
-</li>
-<li class="level1"><div class="li"> Pins are constrained to 90º movements</div>
-</li>
-<li class="level1"><div class="li"> Position the mouse pointer to the start-point</div>
-</li>
-<li class="level1"><div class="li"> Press the first mouse button</div>
-</li>
-<li class="level1"><div class="li"> Move the mouse in the intended direction. The <a href="http://www.geda.seul.org/docs/current/symbols/symbols.pdf"; class="urlextern" title="http://www.geda.seul.org/docs/current/symbols/symbols.pdf"; rel="nofollow">gEDA/gaf Symbol Creation Document</a> specifies the length of pins in gEDA/gaf compliant symbol files.</div>
-</li>
-<li class="level1"><div class="li"> When positioned at the end-point, press the first mouse button</div>
-</li>
-<li class="level1"><div class="li"> Continue placing pins, until you either press the second mouse button or type the Escape key</div>
-</li>
-</ul>
-
-<p>
- To cancel a pin in progress, press the last mouse button or the ESC key.
-</p>
-
-</div>
-<!-- SECTION "Pin (ap)" [102427-103614] -->
-<h3><a name="picture..._ag" id="picture..._ag">Picture... (ag)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Add | Picture</strong> places a graphic in the schematic. To draw a picture:
-</p>
-<ul>
-<li class="level1"><div class="li"> If you want to snap the picture to the grid, set the grid spacing by selecting <strong>Options | Snap Grid Spacing…</strong> and entering the grid spacing, and then selecting <strong>Options | Toggle Snap On/Off</strong> until you donâ??t see â??Snap Offâ?? on the status-bar</div>
-</li>
-<li class="level1"><div class="li"> Select <strong>Add | Picture</strong></div>
-</li>
-<li class="level1"><div class="li"> Select the graphic file from the â??Please select a picture fileâ?? dialog box</div>
-</li>
-<li class="level1"><div class="li"> Press OK</div>
-</li>
-<li class="level1"><div class="li"> Position the mouse pointer to the start-point</div>
-</li>
-<li class="level1"><div class="li"> Press the first mouse button</div>
-</li>
-<li class="level1"><div class="li"> Move the mouse in the intended direction. The outline of the picture will appear, retaining the aspect ratio of the original picture.</div>
-</li>
-<li class="level1"><div class="li"> When positioned at the end-point, press the first mouse button again.</div>
-</li>
-<li class="level1"><div class="li"> Continue placing pictures, until you either press the second mouse button or type the ESC key</div>
-</li>
-</ul>
-
-<p>
- To cancel a picture in progress, press the last mouse button or type the ESC key.<br/>
- A picture has no electrical significance.
-</p>
-
-</div>
-<!-- SECTION "Picture... (ag)" [103615-104610] -->
-<h2><a name="hierarchy" id="hierarchy">Hierarchy</a></h2>
-<div class="level2">
-
-</div>
-<!-- SECTION "Hierarchy" [104611-104633] -->
-<h3><a name="down_schematic_hd" id="down_schematic_hd">Down Schematic (Hd)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Hierarchy | Down Schematic</strong> shifts the focus from the current schematic to a sub-schematic.<br/>
- Descend dans un symbole, en ouvrant tous les schémas sous-jacents. Cela ouvrira typiquement un schéma sous-jacent du composant sélectionné sâ??il existe dans le chemin de recherche de la bibliothèque source. Voyez la section des Fichiers Ressource sur la manière de définir ce chemin.<br/>
- Il y a actuellement deux manières de spécifier quâ??un symbole possède un schéma sous-jacent ou des schémas:
-</p>
-<ol>
-<li class="level1"><div class="li"> Le schéma sous-jacent doit avoir le même nom que le symbole mais avec une extension .sch et doit suivre la convention de nommage de suffixe _#. Voyez la section Fichiers au-dessus à propos de cette convention.</div>
-</li>
-<li class="level1"><div class="li"> Attacher un attribut au symbole appelé source=filename.sch filename.sch nâ??est pas un chemin vers le symbole mais plutôt un nom de base (le dernier fichier dans le spécificateur de chemin) du chemin de symbole. Le schéma sous-jacent sera encore recherché dans le chemin de bibliothèque source. Vous pouvez spécifier des attributs source= multiples. Les schémas sous-jacents seront ouverts dans lâ??ordre de découverte de lâ??attribut source= .</div>
-</li>
-</ol>
-
-<p>
- Sâ??il a des schémas sous-jacents multiples, ils seront chargés. Le mouvement entre les pages de schéma est limité (au niveau du même jeu des schémas sous-jacent) à moins que le mot-clé rc enforce-hierarchy ne soit modifié pour permettre un mode de libre circulation transversal. Veuillez voir la section des Fichiers de Ressource pour plus dâ??informations.<br/>
- Il est aussi recommandé que vous mainteniez des noms uniques pour les divers niveaux (lorsque vous utilisez lâ??attribut source<img src="lib/images/smileys/icon_smile2.gif" class="middle" alt="=)" /> pour éviter des possibles confusions. Les mécanismes hiérarchiques sont assez nouveaux et vous pouvez craindre quelques anomalies (et veuillez les rapporter sâ??il vous plaît).
-</p>
-
-</div>
-<!-- SECTION "Down Schematic (Hd)" [104634-106510] -->
-<h3><a name="down_symbol_hs" id="down_symbol_hs">Down Symbol (Hs)</a></h3>
-<div class="level3">
-
-<p>
-Cette option ouvrira le symbole du composant sélectionné.<br/>
- Une fois que le symbole est ouvert, lâ??utilisateur peut lâ??éditer et le sauvegarder.<br/>
- A ce moment, le schéma principal ne verra pas les changements du symbole à moins que le schéma principal ne soit rechargé ou que File/Revert ne soit exécuté. Cela sera modifié un jour.
-</p>
-
-</div>
-<!-- SECTION "Down Symbol (Hs)" [106511-106879] -->
-<h3><a name="up_hu" id="up_hu">Up (Hu)</a></h3>
-<div class="level3">
-
-<p>
-Cette option permettra de remonter dans la hiérarchie (sâ??il y a des pages au-dessus de la page actuellement affichée).
-</p>
-
-</div>
-<!-- SECTION "Up (Hu)" [106880-107020] -->
-<h3><a name="documentation_ho" id="documentation_ho">Documentation (Ho)</a></h3>
-<div class="level3">
-
-<p>
-Open any documentation available for the selected symbol/component.<br/>
- The job is handed over to â??gschemdocâ??, which makes a best-effort attempt of finding relevant documentation.<br/>
- The documention would normally be in <acronym title="Portable Document Format">PDF</acronym>, <acronym title="HyperText Markup Language">HTML</acronym>, text or image format, but gschemdoc tries to be as transparent as possible on this account.<br/>
- First and foremost, the attribute â??documentation=" is assumed to point to the documentation. This attribute should either be the filename (basename) of the document, or it should be a complete <acronym title="Uniform Resource Locator">URL</acronym>.<br/>
- If it is a filename, and the file is found locally (in /usr/share/gEDA/documentation or otherwise), the relevant viewer will be initiated. Otherwise, a Google search for the document will be initiated.<br/>
- If there is no documentation attribute, the attributes â??deviceâ?? and possibly â??valueâ?? will be consulted in much the same way as for â??documentationâ??. File searches will be made in forms of filenames like â??device-value.pdfâ?? and â??device.pdfâ??.<br/>
- Failing that, the file name for the symbol itself will be used as basis for the search.
-</p>
-
-</div>
-<!-- SECTION "Documentation (Ho)" [107021-108105] -->
-<h2><a name="attributes1" id="attributes1">Attributes</a></h2>
-<div class="level2">
-
-</div>
-<!-- SECTION "Attributes" [108106-108129] -->
-<h3><a name="attach_ta" id="attach_ta">Attach (ta)</a></h3>
-<div class="level3">
-
-<p>
-The Attach command allows you to take a text item (in the proper form; <code>name=value</code>) and attach it to another object.<br/>
- To use Attributes/Attach:
-</p>
-<ol>
-<li class="level1"><div class="li"> Select the object which will receive the attributes</div>
-</li>
-<li class="level1"><div class="li"> Select the text object(s) which will be attached to the above object</div>
-</li>
-<li class="level1"><div class="li"> Pick or type the shortcut for Attributes/Attach</div>
-</li>
-</ol>
-
-<p>
- The order of the sequence of selecting the object and then the text items is important; <strong>gschem</strong> will not allow you to select the text items first and then the object. After going through the above sequence the text item will turn yellow (or the current attached attribute color) signifying that the text item is an attached attribute.<br/>
- You cannot attach a single attribute to several different objects. You cannot attach non-text items as attributes.
-</p>
-
-</div>
-<!-- SECTION "Attach (ta)" [108130-108937] -->
-<h3><a name="detach_td" id="detach_td">Detach (td)</a></h3>
-<div class="level3">
-
-<p>
-Detach allows you to deassociate attributes from objects.<br/>
- To deselect an object of all attributes:
-</p>
-<ol>
-<li class="level1"><div class="li"> Select the object of interest</div>
-</li>
-<li class="level1"><div class="li"> Pick or type the shortcut for Attributes/Detach</div>
-</li>
-</ol>
-
-<p>
- All the attached attributes (even if they are not selected) will be detached from the object. This behavior is probably broken and will eventually be fixed (so that only selected attributes are detached).<br/>
- When you detach attributes then they turn red (or the current detached attribute color). This color changes allows you to spot text which was an attribute and is now dangling (unattached).
-</p>
-
-</div>
-<!-- SECTION "Detach (td)" [108938-109544] -->
-<h3><a name="show_value_tv" id="show_value_tv">Show Value (tv)</a></h3>
-<div class="level3">
-
-<p>
-These operations allow you to control which part of the attribute string is visible. Usually you are just interested in seeing the <code>value</code> of the attribute, but there are circumstances where seeing the <code>name</code> and <code>value</code> (or maybe just the <code>name</code>) would be useful.<br/>
- To use the options:
-</p>
-<ol>
-<li class="level1"><div class="li"> Select the attribute(s) of interest</div>
-</li>
-<li class="level1"><div class="li"> Pick or type the shortcut for Attributes/Show *</div>
-</li>
-</ol>
-
-<p>
- The text item(s) should immediately change.<br/>
- These operations only work on text items which are in the form <code>name=value</code>
-</p>
-
-</div>
-<!-- SECTION "Show Value (tv)" [109545-110083] -->
-<h3><a name="show_name_tn" id="show_name_tn">Show Name (tn)</a></h3>
-<div class="level3">
-
-<p>
-These operations allow you to control which part of the attribute string is visible. Usually you are just interested in seeing the <code>value</code> of the attribute, but there are circumstances where seeing the <code>name</code> and <code>value</code> (or maybe just the <code>name</code>) would be useful.<br/>
- To use the options:
-</p>
-<ol>
-<li class="level1"><div class="li"> Select the attribute(s) of interest</div>
-</li>
-<li class="level1"><div class="li"> Pick or type the shortcut for Attributes/Show *</div>
-</li>
-</ol>
-
-<p>
- The text item(s) should immediately change.<br/>
- These operations only work on text items which are in the form <code>name=value</code>
-</p>
-
-</div>
-<!-- SECTION "Show Name (tn)" [110084-110621] -->
-<h3><a name="show_both_tb" id="show_both_tb">Show Both (tb)</a></h3>
-<div class="level3">
-
-<p>
-These operations allow you to control which part of the attribute string is visible. Usually you are just interested in seeing the <code>value</code> of the attribute, but there are circumstances where seeing the <code>name</code> and <code>value</code> (or maybe just the <code>name</code>) would be useful.<br/>
- To use the options:
-</p>
-<ol>
-<li class="level1"><div class="li"> Select the attribute(s) of interest</div>
-</li>
-<li class="level1"><div class="li"> Pick or type the shortcut for Attributes/Show *</div>
-</li>
-</ol>
-
-<p>
- The text item(s) should immediately change.<br/>
- These operations only work on text items which are in the form <code>name=value</code>
-</p>
-
-</div>
-<!-- SECTION "Show Both (tb)" [110622-111159] -->
-<h3><a name="toggle_visibility_tt" id="toggle_visibility_tt">Toggle Visibility (tt)</a></h3>
-<div class="level3">
-
-<p>
-This operation allows you to toggle the visibility of attributes.<br/>
- To use this option:
-</p>
-<ol>
-<li class="level1"><div class="li"> Select the text item(s) of interest</div>
-</li>
-<li class="level1"><div class="li"> Pick or type the shortcut for Attributes/Toggle Vis</div>
-</li>
-</ol>
-
-<p>
- The text item(s) should change their visibility immediately.<br/>
- If you make an attached attribute invisible, then you can simply select the parent object and select Toggle Vis and the attribute will be come visible (likewise any visible attributes attached to that object will become invisible).<br/>
- If you make a free floating (unattached) attribute invisible, then the only way to make it visible (and all other invisible attributes) is to use the Edit/Show Hidden Text option.
-</p>
-
-</div>
-<!-- SECTION "Toggle Visibility (tt)" [111160-111855] -->
-<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">
-
-</div>
-<!-- SECTION "Find Specific Text... (t shift-f)" [111856-111900] -->
-<h3><a name="hide_specific_text..._th" id="hide_specific_text..._th">Hide Specific Text... (th)</a></h3>
-<div class="level3">
-
-</div>
-<!-- SECTION "Hide Specific Text... (th)" [111901-111938] -->
-<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">
-
-</div>
-<!-- SECTION "Show Specific Text... (t shift-h)" [111939-111982] -->
-<h3><a name="autonumber_text..._tu" id="autonumber_text..._tu">Autonumber Text... (tu)</a></h3>
-<div class="level3">
-
-</div>
-<!-- SECTION "Autonumber Text... (tu)" [111983-112017] -->
-<h2><a name="options" id="options">Options</a></h2>
-<div class="level2">
-
-</div>
-<!-- SECTION "Options" [112018-112038] -->
-<h3><a name="text_size..._ot" id="text_size..._ot">Text Size... (ot)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Options | Text Size…</strong> pops up a dialog box which allows you to specify the text size of all text (including attributes placed with the Add/Attribute… dialog box).<br/>
- The text size is in points (1/72â??). The default text size is 10 point text. The smallest text size is 2 points.
-</p>
-
-</div>
-<!-- SECTION "Text Size... (ot)" [112039-112351] -->
-<h3><a name="toggle_grid_on_off_og" id="toggle_grid_on_off_og">Toggle Grid On/Off (og)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Options | Toggle Grid On/Off</strong> toggles the visible grid.
-</p>
-
-</div>
-<!-- SECTION "Toggle Grid On/Off (og)" [112352-112445] -->
-<h3><a name="toggle_snap_on_off_os" id="toggle_snap_on_off_os">Toggle Snap On/Off (os)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Options | Toggle Snap On/Off</strong> toggles the snap. Be very careful using this. Connections between pins and nets (and nets to nets) depends on being exactly connected. Turning of the grid will almost guarantee that nets/pins do not connect.<br/>
- Before you translate a symbol using Edit/Symbol Translate, make sure the snap is on.<br/>
- When snap mode is off, the text â??Snap Offâ?? will appear in the lower, righthand corner.
-</p>
-
-</div>
-<!-- SECTION "Toggle Snap On/Off (os)" [112446-112897] -->
-<h3><a name="snap_grid_spacing..._os" id="snap_grid_spacing..._os">Snap Grid Spacing... (oS)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Options | Snap Grid Spacing…</strong> brings up a dialog box which allows you to change the snap grid spacing (not the grid spacing). The units for this spacing are mils.<br/>
- Before you translate a symbol using Edit/Symbol Translate, make sure this spacing is set to 100.
-</p>
-
-</div>
-<!-- SECTION "Snap Grid Spacing... (oS)" [112898-113201] -->
-<h3><a name="toggle_outline_box_oa" id="toggle_outline_box_oa">Toggle Outline/Box (oa)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Options | Toggle Outline/Box</strong> toggles between drawing the outline of the current selection or just drawing a box when doing moves/copies/component and text places. The outline mode looks better, but tends to be significantly slower than using the box (bounding box) mode.
-</p>
-
-</div>
-<!-- SECTION "Toggle Outline/Box (oa)" [113202-113511] -->
-<h3><a name="toggle_net_rubberband_or" id="toggle_net_rubberband_or">Toggle Net/Rubberband (or)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Options | Toggle Net/Rubberband</strong> …..????
-</p>
-
-</div>
-<!-- SECTION "Toggle Net/Rubberband (or)" [113512-113595] -->
-<h3><a name="show_log_window_ol" id="show_log_window_ol">Show Log Window (ol)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Options | Show Log Window</strong> displays the log window if it has been closed or disabled from being displayed when you start up <strong>gschem</strong>.
-</p>
-
-</div>
-<!-- SECTION "Show Log Window (ol)" [113596-113766] -->
-<h3><a name="show_coord_window..._oc" id="show_coord_window..._oc">Show Coord Window... (oc)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Options | Show Coord Window…</strong> displays a pop-up window that displays the coordinates of the mouse pointer on the schematic. Useful for accurately placing objects.
-</p>
-
-</div>
-<!-- SECTION "Show Coord Window... (oc)" [113767-113971] -->
-<h2><a name="help" id="help">Help</a></h2>
-<div class="level2">
-
-</div>
-<!-- SECTION "Help" [113972-113989] -->
-<h3><a name="about..._ha" id="about..._ha">About... (ha)</a></h3>
-<div class="level3">
-
-<p>
-Every <acronym title="Graphical User Interface">GUI</acronym> application needs an <strong>Help | About…</strong> feature, to display:
-</p>
-<ul>
-<li class="level1"><div class="li"> The applicationâ??s name.</div>
-</li>
-<li class="level1"><div class="li"> The version of the software.</div>
-</li>
-<li class="level1"><div class="li"> The authorâ??s name(s) and how to contact.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "About... (ha)" [113990-114192] -->
-<h3><a name="manual..._hm" id="manual..._hm">Manual... (hm)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Help | Manual…</strong> brings up the â??gEDA/gaf Documentionâ?? web-page installed on this computer. Very useful for accessing the various documentation available for the gEDA/gaf applications.
-</p>
-
-</div>
-<!-- SECTION "Manual... (hm)" [114193-114406] -->
-<h3><a name="hotkeys..._hh" id="hotkeys..._hh">Hotkeys... (hh)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Help | Hotkeys…</strong> lists the current hotkeys (a.k.a., shortcuts, a.k.a., keyboard accellerators).
-</p>
-
-</div>
-<!-- SECTION "Hotkeys... (hh)" [114407-114534] -->
-<h3><a name="component..._ho" id="component..._ho">Component... (Ho)</a></h3>
-<div class="level3">
-
-<p>
-If you select a component on the schematic, and select <strong>Help | Component…</strong>, <strong>gschem</strong> uses the gschemdoc script to do its best job finding some documentation appropriate for the component:
-</p>
-<ul>
-<li class="level1"><div class="li"> If the componentâ??s symbol included the <code>documentation=documentation_locator</code> attribute, this <acronym title="Uniform Resource Identifier">URI</acronym> is used to retreive the documentation. If the full <acronym title="Uniform Resource Identifier">URI</acronym> is given, the <acronym title="Uniform Resource Identifier">URI</acronym> on the internet is retrieved. If the <acronym title="Uniform Resource Identifier">URI</acronym> is not fully qualified, it is considered to be local to this computer, and is searched for and displayed.</div>
-</li>
-<li class="level1"><div class="li"> If the componentâ??s symbol does not include the <code>documentation=documentation_locator</code> attribute, a Google search is performed for <acronym title="Portable Document Format">PDF</acronym> documents, based on the <code>device=</code> attribute, the <code>value=</code> attribute, and the symbol basename.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Component... (Ho)" [114535-115317] -->
-<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">
-
-<p>
-A short discussion of Light Symbol Libraries as the default for <strong>gschem</strong>, and the option to build your own Heavy Symbol Libraries.
-</p>
-
-</div>
-<!-- SECTION "Appendix A -- Heavy vs Light Symbol Libraries" [115318-115511] -->
-<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">
-
-<p>
-To be supplied…
-</p>
-
-</div>
-<!-- SECTION "Appendix B -- Printing Schematics and Symbols" [115512-115590] -->
-<h1><a name="appendix_c_--_writing_guile_scripts" id="appendix_c_--_writing_guile_scripts">Appendix C -- Writing guile Scripts</a></h1>
-<div class="level1">
-
-<p>
-To be supplied…
-</p>
-
-</div>
-<!-- SECTION "Appendix C -- Writing guile Scripts" [115591-115659] -->
-<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">
-
-<p>
-<strong>gschem</strong> is used for two primary design workflows:
-</p>
-<ul>
-<li class="level1"><div class="li"> Circuit design intended for production of Printed Circuit Boards (PCBs).</div>
-</li>
-<li class="level1"><div class="li"> Circuit design intended for simulation.</div>
-</li>
-</ul>
-
-<p>
- The following guidelines will assist you in developing quality designs intended for use by applications that support the creation of Printed Circuit Boards:
-</p>
-<ul>
-<li class="level1"><div class="li"> <span class="hilited">To be supplied…</span></div>
-</li>
-</ul>
-
-<p>
- The following on-line tutorials are an excellent method for the beginner to learn the gEDA Tools Suite design workflow resulting in a PCB:
-</p>
-<ul>
-<li class="level1"><div class="li"> <a href="http://www.geda.seul.org/docs/current/tutorials/gsch2pcb/gschem-warmup.html"; class="urlextern" title="http://www.geda.seul.org/docs/current/tutorials/gsch2pcb/gschem-warmup.html"; rel="nofollow">Bill Wilson's gschem warmup</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://www.geda.seul.org/docs/current/tutorials/gsch2pcb/tutorial.html"; class="urlextern" title="http://www.geda.seul.org/docs/current/tutorials/gsch2pcb/tutorial.html"; rel="nofollow">Bill Wilson's gsch2pcb tutorial</a></div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Appendix D -- I Want To Build A Printed Circuit Board" [115660-116449] -->
-<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">
-
-<p>
-<strong>gschem</strong> is used for two primary design workflows:
-</p>
-<ul>
-<li class="level1"><div class="li"> Circuit design intended for production of Printed Circuit Boards.</div>
-</li>
-<li class="level1"><div class="li"> Circuit design intended for simulation.</div>
-</li>
-</ul>
-
-<p>
- The following guidelines will assist you in developing quality designs intended for simulation:
-</p>
-<ul>
-<li class="level1"><div class="li"> Discuss attributes appropriate for a SPICE model, and how these differ from attributes appropriate for a PCB.</div>
-</li>
-<li class="level1"><div class="li"> <span class="hilited">To be supplied…</span></div>
-</li>
-</ul>
-
-<p>
- The following on-line tutorials are an excellent method for the beginner to learn the gEDA Tools Suite design workflow resulting in a SPICE simulation:
-</p>
-<ul>
-<li class="level1"><div class="li"> <a href="http://www.brorson.com/gEDA/SPICE/t1.html"; class="urlextern" title="http://www.brorson.com/gEDA/SPICE/t1.html"; rel="nofollow">"Circuit simulation using gEDA and SPICE -- HOWTO" by Stuart Brorson</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://www-mdp.eng.cam.ac.uk/urop05/files/gedalib/starting_gEDA.pdf"; class="urlextern" title="http://www-mdp.eng.cam.ac.uk/urop05/files/gedalib/starting_gEDA.pdf"; rel="nofollow">Starting with gEDA at the Cambridge University Engineering Department</a></div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Appendix E -- I Want To Simulate My Design" [116450-117329] -->
-<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">
-
-<p>
-As installed, the <strong>gschemdoc</strong> utility script is used by <strong>gschem</strong> to:
-</p>
-<ul>
-<li class="level1"><div class="li"> Display the â??gEDA/gaf Documentationâ?? (i.e., <strong>Help | Manual…</strong>)</div>
-</li>
-<li class="level1"><div class="li"> Display component documentation (i.e., <strong>Help | Component…</strong>)</div>
-</li>
-</ul>
-
-<p>
- The list of application launchers that <strong>gschemdoc</strong> uses are defined in the {binary-install-path}/bin/gschemdoc file: <pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">#
-# these may be changed to suit local preferences
-#
-CANDIDATE_BROWSER="galeon mozilla phoenix netscape netscape-navigator opera firefox konqueror"
-CANDIDATE_PDFREADER="xpdf acroread ggv gv"
-CANDIDATE_LOCATE="slocate locate"</font></pre>
-</p>
-
-<p>
-To select a different application launcher, simply edit the {binary-install-path}/bin/gschemdoc file, find the above lines, and move your favorite application to the beginning of the list. For example, to use <strong>firefox</strong> as your preferred browser, move it to the beginning of the <strong>CANDIDATE_BROWSER=</strong> list, to use <strong>acroread</strong> (Adobeâ??s Acrobat Reader) as your preferred <acronym title="Portable Document Format">PDF</acronym> reader, move it to the beginning of the <strong>CANDIDATE_PDFREADER=</strong> list, and to use <strong>locate</strong> as your preferred filesystem search utility, move it to the beginning of the <strong>CANDIDATE_LOCATE=</strong> list.
-</p>
-
-</div>
-<!-- SECTION "Appendix F -- Change gschemdoc User-Defined Preferences" [117330-118546] -->
-<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">
-
-<p>
-To be supplied…
-</p>
-
-</div>
-<!-- SECTION "Appendix G -- Breaking a Large Symbol Into Smaller Symbols" [118547-118638] -->
-<h1><a name="appendix_h_--_definition_of_terms" id="appendix_h_--_definition_of_terms">Appendix H -- Definition of Terms</a></h1>
-<div class="level1">
-
-<p>
-Some terms used in the art of schematic capture:</p>
-<dl>
-<dt><span class='term'> <strong>attribute</strong></span></dt>
-<dd>A text item which is in the form <code>name=value</code>. It can be either unattached or attached.</dd>
-<dt><span class='term'> <strong>buffer</strong></span></dt>
-<dd>…</dd>
-<dt><span class='term'> <strong>component</strong></span></dt>
-<dd>Also know as <strong>part</strong>. The equivalent of an [electronics] device, as one may place on a printed circuit board. Components are instances of a <strong>symbol</strong> placed on a schematic.</dd>
-<dt><span class='term'> <strong>device</strong></span></dt>
-<dd>Also known as â??packageâ??. The equivalent of an [electronics] device, as one may place on a printed circuit board.</dd>
-<dt><span class='term'> <strong>dialog box</strong></span></dt>
-<dd>…</dd>
-<dt><span class='term'> <strong>embedded component</strong></span></dt>
-<dd>A component whose definition is saved as part of the schematicâ??s file.</dd>
-<dt><span class='term'> <strong>footprint</strong></span></dt>
-<dd>Also known as a <strong>land pattern</strong>. The surface space occupied by a <strong>component</strong>/<strong>package</strong>/<strong>part</strong>.</dd>
-<dt><span class='term'> <strong>gEDA/gaf</strong></span></dt>
-<dd><strong>gschem</strong> is a component of the gEDA/gaf set of tools, which tend to integrate together in the development and maintenance of schematics and symbols. The term â??gafâ?? stands for â??<em class="u">g</em>EDA <em class="u">a</em>nd <em class="u">f</em>riendsâ??).</dd>
-<dt><span class='term'> <strong>grip</strong></span></dt>
-<dd>…</dd>
-<dt><span class='term'> <strong>guile</strong></span></dt>
-<dd><a href="http://www.gnu.org/software/guile/"; class="urlextern" title="http://www.gnu.org/software/guile/"; rel="nofollow">GNU Guile</a> is an interpreter for Scheme, a version of Lisp.</dd>
-<dt><span class='term'> <strong>HDL</strong></span></dt>
-<dd>Hardware Description Language (e.g., VHDL, Verilog, etc.). Used to simulate or document a device.</dd>
-<dt><span class='term'> <strong>hierarchical</strong></span></dt>
-<dd>The concept that designs can contain nested levels of schematics, so that all the circuit doesnâ??t need to be placed on a single sheet.</dd>
-<dt><span class='term'> <strong>land pattern</strong></span></dt>
-<dd>Also known as a <strong>footprint</strong>. The surface space occupied by a structure or device.</dd>
-<dt><span class='term'> <strong>library</strong></span></dt>
-<dd>A collection of symbols.</dd>
-<dt><span class='term'> <strong>line</strong></span></dt>
-<dd>A straight drawing element, connecting two points. On the schematic it has no electrical significance. In a symbol, a line is part of the symbolâ??s graphic elements.</dd>
-<dt><span class='term'> <strong>model</strong></span></dt>
-<dd>A description of how a device behaves. Most often this is a SPICE model. The model is defined in <strong>gschem</strong>, but used in subsequent applications such as <strong>ngspice</strong>, <strong>gnucap</strong>, etc.</dd>
-<dt><span class='term'> <strong>net</strong></span></dt>
-<dd>A net connects two or more pins on a schematic, and is made up of segments. The netâ??s equivalent is a â??wireâ?? or â??traceâ?? on the printed circuit board.</dd>
-<dt><span class='term'> <strong>object</strong></span></dt>
-<dd>A line, circle, pin, net, box, bus, text/attribute, or picture.</dd>
-<dt><span class='term'> <strong>package</strong></span></dt>
-<dd>Also known as <strong>device</strong>. The equivalent of an [electronics] device, as one may place on a printed circuit board.</dd>
-<dt><span class='term'> <strong>page</strong></span></dt>
-<dd>Also known as a schematicâ??s <strong>sheet</strong>.</dd>
-<dt><span class='term'> <strong>part</strong></span></dt>
-<dd> Also know as <strong>component</strong>. The equivalent of an [electronics] device, as one may place on a printed circuit board.</dd>
-<dt><span class='term'> <strong>project</strong></span></dt>
-<dd>A collection of schematics, custom symbols, models, documentation, etc.</dd>
-<dt><span class='term'> <strong>segment</strong></span></dt>
-<dd>Part of a net. A segment has two end-points, or â??gripsâ??.</dd>
-<dt><span class='term'> <strong>schematic</strong></span></dt>
-<dd>A <strong>page</strong>/<strong>sheet</strong> with electronics symbols, text, and drawing elements (i.e., lines, circles, boxes, etc.) representing a diagram of an electrical or mechanical system.</dd>
-<dt><span class='term'> <strong>series</strong></span></dt>
-<dd>A collection of schematics which share a common basename (e.g., schematic_1.sch, schematic_2.sch, schematic_3.sch, etc.). The series basename ties schematics together.</dd>
-<dt><span class='term'> <strong>slotted device</strong></span></dt>
-<dd>Also known as a <strong>slotted package</strong>. A physical [electronics] device consisting of multiple identical components (e.g., the 7400 quad NAND device consists of 4 identical NAND gates).</dd>
-<dt><span class='term'> <strong>source</strong></span></dt>
-<dd>A schematic, HDL code, or model which implements, describes, or documents some aspect of the project.</dd>
-<dt><span class='term'> <strong>symbol</strong></span></dt>
-<dd>A collection of <strong>objects</strong>. The objects may have <strong>attributes</strong> attatched (i.e., associated) with them. There may also be <strong>attributes</strong> attached (i.e., associated) to the <strong>symbol</strong> itself (i.e., not specifically associated with an object).</dd>
-<dt><span class='term'> <strong>sheet</strong></span></dt>
-<dd>Also known as a schematicâ??s <strong>page</strong>.</dd>
-<dt><span class='term'> <strong>trace</strong></span></dt>
-<dd>The equivalent of a wire on a printed circuit board.</dd>
-<dt><span class='term'> <strong>window</strong></span></dt>
-<dd>…</dd>
-<dt><span class='term'> <strong>workflow</strong></span></dt>
-<dd>The process of designing. Usually includes continuous review and re-design, until it works. In the gEDA Tools Suite design workflow, multiple applications are used. One application typically is followed by another. The flow of data collected and how this data effects the design is considered the workflow.</dd>
-</dl>
-<p>~~DISCUSSION~~
-</p>
-
-</div>
-<!-- SECTION "Appendix H -- Definition of Terms" [118639-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/001geda_hse_howto.html b/docs/wiki/001geda_hse_howto.html
deleted file mode 100644
index 3a41a43..0000000
--- a/docs/wiki/001geda_hse_howto.html
+++ /dev/null
@@ -1,27 +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>geda:hse_howto.fr</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="noindex,follow" />
-<meta name="date" content="1969-12-31T19:00:00-0500" />
-<meta name="keywords" content="geda,hse_howto.fr" />
-<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/geda:hse_howto.fr?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:hse_howto.fr"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:hse_howto.fr"; />
-<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>
-</body>
-</html>
diff --git a/docs/wiki/001geda_installation.html b/docs/wiki/001geda_installation.html
deleted file mode 100644
index 0cba62e..0000000
--- a/docs/wiki/001geda_installation.html
+++ /dev/null
@@ -1,281 +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>geda:installation.fr</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="keywords" content="geda,installation.fr" />
-<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/geda:installation.fr?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:installation.fr"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:installation.fr"; />
-<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="#aide_a_l_installation" class="toc">Aide à l'installation</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#comment_installer_la_suite_geda" class="toc">Comment installer la Suite gEDA?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#comment_desinstaller_la_suite_geda" class="toc">Comment désinstaller la Suite gEDA?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#pourquoi_voudrais-je_desinstaller_la_suite_geda" class="toc">Pourquoi voudrais-je désinstaller la Suite gEDA?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#aaaaargh_j_ai_mis_un_cd_dans_le_lecteur_je_l_ai_monte_mais_rien_ne_se_produit" class="toc">Aaaaargh! J'ai mis un CD dans le lecteur, je l'ai monté mais rien ne se produit!</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#aidez-moi_je_tente_une_installation_en_utilisant_le_cd_rom_mais_le_magicien_d_installation_m_indique_une_erreur" class="toc">Aidez-moi! Je tente une installation en utilisant le CD ROM mais le magicien d'installation m'indique une erreur!</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#waaaaa_l_installation_s_est_terminee_mais_j_ai_un_segfault_ou_autre_probleme_lorsque_je_lance_gschem_ou_gattrib_ou_gnetlist_ou" class="toc">Waaaaa! L'installation s'est terminée mais j'ai un segfault (ou autre problème) lorsque je lance gschem (ou gattrib ou gnetlist, ou. . . )!</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#fedora_core_4_install_notes" class="toc">Fedora Core 4 install notes</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#fedora_core_3_install_notes" class="toc">Fedora Core 3 install notes</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#fedora_core_2_install_notes" class="toc">Fedora Core 2 install notes</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#fedora_core_1_install_notes" class="toc">Fedora Core 1 install notes</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#suse_9.3_install_notes" class="toc">Suse 9.3 install notes</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#suse_10.0_install_notes" class="toc">Suse 10.0 install notes</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#suse_10.1_install_notes" class="toc">Suse 10.1 install notes</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#notes_d_installation_debian" class="toc">Notes d'installation Debian</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#windows_install_notes" class="toc">Windows install notes</a></span></div></li></ul>
-</li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="aide_a_l_installation" id="aide_a_l_installation">Aide à l'installation</a></h1>
-<div class="level1">
-
-<p>
-Cette section fournit quelques informations utiles aux personnes qui veulent installer gEDA sur leur ordinateur.
-</p>
-
-</div>
-<!-- SECTION "Aide à l'installation" [1-151] -->
-<h2><a name="comment_installer_la_suite_geda" id="comment_installer_la_suite_geda">Comment installer la Suite gEDA?</a></h2>
-<div class="level2">
-
-<p>
-La manière la plus facile dâ??installer la Suite gEDA est de graver le CDROM et de lâ??utiliser. Les instructions sont dans le README disponible sur la <a href="http://geda.seul.org/download.html"; class="urlextern" title="http://geda.seul.org/download.html"; rel="nofollow">page des téléchargements</a>. <strong><em>Notez que lâ??installateur du CD ROM suppose que vous êtes sur le bureau Gnome! La même chose est vraie pour les outils gEDA: Ils utilisent le jeu de widgets GTK qui soutend Gnome. Si vous êtes sous KDE, vous avez au moins besoin des bibliothèques Gnome dâ??installées sur votre machine avant de tenter de lancer lâ??installateur.</em></strong>
-</p>
-
-<p>
-Le CD de la Suite gEDA contient les tarballs de plus dâ??une douzaine dâ??applications populaires de gEDA. Il incorpore aussi un «·magicien·» graphique qui contrôle la configuration de votre système, vous pose quelques questions et surveille la compilation et lâ??installation des différentes applications gEDA. Le magicien dâ??installation automatise le processus normal â??./configure && make && make installâ?? utilisé pour construire les logiciels GNU depuis les sources. Câ??est la raison pour laquelle il est plus ou moins indépendant de la plate-forme (tant que vous faites tourner Linux).
-</p>
-
-<p>
-Dans lâ??éventualité où le magicien dâ??installation ne peut pas installer la Suite gEDA automatiquement, vous pouvez encore extraire les tarballs de source du CD et de les construire manuellement. Les instructions sont disponibles sur la page de téléchargement, de même que le fichier INSTALL sur le CD.
-</p>
-
-<p>
-De la même manière, des personnes ont créé des RPM RedHat, des Debs Debian et des paquets Mac OSX Fink si vous préférez les installer de cette manière. Ces distributions binaires sont disponibles sur la <a href="http://geda.seul.org/download.html"; class="urlextern" title="http://geda.seul.org/download.html"; rel="nofollow">page de téléchargement</a>. Finalement, les tarballs de sources pour tous les programmes sont aussi disponiblessur la <a href="http://geda.seul.org/download.html"; class="urlextern" title="http://geda.seul.org/download.html"; rel="nofollow">page de téléchargements</a>.
-</p>
-
-<p>
-Au fait, câ??est toujours une bonne idée dâ??installer gEDA dans son propre répertoire. De cette manière, lorsque vous voulez mettre à jour le paquet, vous avez juste besoin dâ??effacer le répertoire et ré-installer. (Ce conseil est vrai pour toute grande suite dâ??applications dâ??unix.) Vous en avez plus ci-dessous.
-</p>
-
-<p>
-Finalement, si ces instructions ne sont pas suffisantes, David Hart a placé un <a href="http://www.offramp.com/Lab-Install/doku.php?id=fc4#create_user_geda_account_and_install_geda_tool_suite"; class="urlextern" title="http://www.offramp.com/Lab-Install/doku.php?id=fc4#create_user_geda_account_and_install_geda_tool_suite"; rel="nofollow">guide for configuring and installing gEDA</a> utile et détaillé (pour Fedora Core 4 mais qui aidera probablement aussi avec les autres distros), de même quâ??un <a href="http://www.offramp.com/Lab-Install/doku.php?id=fc4#geda_tutorial"; class="urlextern" title="http://www.offramp.com/Lab-Install/doku.php?id=fc4#geda_tutorial"; rel="nofollow">tutoriel gEDA</a> pour les nouveaux utilisateurs.
-</p>
-
-</div>
-<!-- SECTION "Comment installer la Suite gEDA?" [152-2869] -->
-<h2><a name="comment_desinstaller_la_suite_geda" id="comment_desinstaller_la_suite_geda">Comment désinstaller la Suite gEDA?</a></h2>
-<div class="level2">
-
-<p>
-Au moment de lâ??écriture de cet article, il nâ??existe pas de méthode pour désinstaller la Suite gEDA. Contrairement à certain systèmes dâ??exploitation commerciaux, Linux (et unix) nâ??ont pas été conçus dans lâ??idée de faciliter la gestion des paquets facilement et nous souffrons de cet héritage.
-</p>
-
-<p>
-Câ??est la raison pour laquelle nous recommandons dâ??installer la Suite gEDA dans son propre répertoire. Par exemple, lâ??installateur CD placera les exécutables de la Suite dans <strong><code>${HOME}/geda-install</code></strong> par défaut. Alors, si vous avez besoin de désinstaller la Suite gEDA, vous pouvez juste effacer le répertoire complet.
-</p>
-
-<p>
-<span class="hilited">(Dâ??autres méthodes avancées pour installer/désinstaller les paquets sur Linux/unix existe aussi. Quelquâ??un pourrait-il écrire quelque chose sur le sujet?)</span>
-</p>
-
-</div>
-<!-- SECTION "Comment désinstaller la Suite gEDA?" [2870-3713] -->
-<h2><a name="pourquoi_voudrais-je_desinstaller_la_suite_geda" id="pourquoi_voudrais-je_desinstaller_la_suite_geda">Pourquoi voudrais-je désinstaller la Suite gEDA?</a></h2>
-<div class="level2">
-
-<p>
-Différentes applications appartenant à gEDA/gaf utilisent la même bibliothèque partagée, libgeda.so. Les éléments dans la bibliothèque changent dâ??une version gEDA à lâ??autre. Câ??est la raison pour laquelle les applications ne peuvent pas être liées à libgeda.so si leur code de version est différent.
-</p>
-
-<p>
-Si vous avez besoin de mettre à jour une application de gEDA/gaf, vous devrez dâ??abord désinstaller votre ancienne version puis intaller un tout nouveau jeu dâ??applications, incluant la bibliothèque et tous les composants de gEDA/gaf.
-</p>
-
-<p>
-Alternativement, vous pouvez installer le nouveau gEDA/gaf dans un nouveau répertoire et éditer alors vos variables dâ??environnement <strong><code>${PATH}</code></strong>, <strong><code>${PKG_CONFIG_PATH}</code></strong> puis <strong><code>${LD_LIBRARY_PATH}</code></strong> pour enlever lâ??ancien répertoire et pointer vers le nouveau. Assurez-vous de le faire <strong>avant</strong> de tenter une nouvelle installation de gEDA/gaf.
-</p>
-
-</div>
-<!-- SECTION "Pourquoi voudrais-je désinstaller la Suite gEDA?" [3714-4683] -->
-<h2><a name="aaaaargh_j_ai_mis_un_cd_dans_le_lecteur_je_l_ai_monte_mais_rien_ne_se_produit" id="aaaaargh_j_ai_mis_un_cd_dans_le_lecteur_je_l_ai_monte_mais_rien_ne_se_produit">Aaaaargh! J'ai mis un CD dans le lecteur, je l'ai monté mais rien ne se produit!</a></h2>
-<div class="level2">
-
-<p>
- Dâ??une manière surprenante, il y a encore des personnes qui copient simplement le fichier installateur .iso en utilisant «·cp·» vers un CD vierge et tentent ensuite de lâ??utiliser tel quel. Cela ne marche pas. Vous avez besoin de «·graver·» un CD avec un .iso dâ??une manière qui écrit le système de fichier complet directement sur le CDROM. La commande linux/unix pour ce faire est habituellement «·cdrecord·» ou, peut être, une interface graphique dérivée de cet utilitaire. Il ne suffit pas de juste «·cp·» le fichier .iso sur le CD vierge!
-</p>
-
-<p>
-De nombreuses distributions Linux récentes ne lanceront pas automatiquement les exécutables sur un média installé. Câ??est une précaution de sécurité. Pour passer outre, vous avez besoin de monter un CD qui donne les permissions de lancer un exécutable. Par exemple, avec Gentoo et Debian, vous devez monter le CD ROM de cette manière:
-</p>
-<pre class="code">mount -o exec -t iso9660 /dev/cdrom /mnt/cdrom</pre>
-
-<p>
-Le drapeau précis ou le point de montage adéquat de votre distribution peut être un peu différent·; lisez le manuel pour mount («·man mount·») si vous avez des questions sur la manière de le faire.
-</p>
-
-<p>
-Après avoir monté le CD avec des permissions dâ??exécution, vous pouvez alors lancer lâ??installateur depuis la ligne de commande comme ceci·:
-</p>
-<pre class="code">/mnt/cdrom/installer</pre>
-
-<p>
-Ã? ce point, lâ??interface graphique du magicien dâ??installation devrait apparaître et vous pouvez entrer dans lâ??installation. Si vous ne pouvez pas installer, veuillez tenter un «·ls·» sur le CD pour vérifier sâ??il est lisible. Câ??est à dire en faitant:
-</p>
-<pre class="code">ls -l /mnt/cdrom/</pre>
-
-<p>
-Et assurez-vous dâ??avoir une liste de répertoires plutôt dâ??un message dâ??erreur (ou rien du tout).
-</p>
-
-</div>
-<!-- SECTION "Aaaaargh! J'ai mis un CD dans le lecteur, je l'ai monté mais rien ne se produit!" [4684-6523] -->
-<h2><a name="aidez-moi_je_tente_une_installation_en_utilisant_le_cd_rom_mais_le_magicien_d_installation_m_indique_une_erreur" id="aidez-moi_je_tente_une_installation_en_utilisant_le_cd_rom_mais_le_magicien_d_installation_m_indique_une_erreur">Aidez-moi! Je tente une installation en utilisant le CD ROM mais le magicien d'installation m'indique une erreur!</a></h2>
-<div class="level2">
-
-<p>
- Dâ??abord, gardez en mémoire que lâ??installateur du CD ROM ne fonctionne quâ??avec Linux. Lâ??installateur du CD ROM ne fonctionnera pas sur Sun, BSD ou Mac OSX et il ne fonctionnera certainement pas avec Windows.
-</p>
-
-<p>
-Comme règle général, si vous avez des problèmes en installant gEDA depuis le CD, vous avez ici des éléments que vous pouvez tenter:
-</p>
-<ol>
-<li class="level1"><div class="li"> Si vous lancez lâ??installateur avec le drapeau <strong><code>â??log</code></strong>, il placera un fichier appelé Install.log dans votre répertoire local (depuis où vous avez lancé votre installateur). Ce fichier est un journal de toutes les commandes émises et toutes les réponses générées pendant le processus dâ??installation. Il vous permet de sauvegarder les données affichées dans la fenêtre journal lors de lâ??installation. Lancer lâ??installateur avec <strong><code>â??log</code></strong> est une bonne idée si vous avez des problèmes·; vous pouvez envoyer votre fichier Install.log à un expert qui pourra diagnostiquer votre problème. Vous en saurez plus après.</div>
-</li>
-<li class="level1"><div class="li"> Après avoir eu un problème, la première chose à faire est de regarder le wiki de gEDA. Il est plus que probable que quelquâ??un a déjà eu votre problème et lâ??a rapporté et quâ??une solution a été trouvée et postée. Des distributions Linux différentes ont eu des problèmes différents dans le passé. En focntion de votre distribution, consultez les sections dâ??aide ci-dessous.</div>
-</li>
-<li class="level1"><div class="li"> Si aucune mention de votre problème spécifique nâ??a été posté sur le Wiki, tentez une recherche sur Google. LEs trucs et astuces de GEDA sont dans différents endroits sur la toile et Google peut les trouver pour vous. De même, la liste des geda-user est indexée continuellement par Google. Comme les gens postent fréquement des bogues et des correctifs, Google vous aidera à trouver ces rapports.</div>
-</li>
-<li class="level1"><div class="li"> Ensuite, tentez de poster une question sur la liste des geda-user. Notez que vous devez dâ??abord vous enregistrer. Dâ??autre peuvent avoir déjà développé une solution à votre problème. Quelques uns des experts hantent cette liste et peut offrir quelques sugestions dâ??aide.</div>
-</li>
-</ol>
-
-</div>
-<!-- SECTION "Aidez-moi! Je tente une installation en utilisant le CD ROM mais le magicien d'installation m'indique une erreur!" [6524-8722] -->
-<h2><a name="waaaaa_l_installation_s_est_terminee_mais_j_ai_un_segfault_ou_autre_probleme_lorsque_je_lance_gschem_ou_gattrib_ou_gnetlist_ou" id="waaaaa_l_installation_s_est_terminee_mais_j_ai_un_segfault_ou_autre_probleme_lorsque_je_lance_gschem_ou_gattrib_ou_gnetlist_ou">Waaaaa! L'installation s'est terminée mais j'ai un segfault (ou autre problème) lorsque je lance gschem (ou gattrib ou gnetlist, ou. . . )!</a></h2>
-<div class="level2">
-
-<p>
-Après que vous ayiez installé la Suite gEDA depuis le CD ROM, assurez-vous dâ??avoir fait ce qui suit:
-</p>
-<ol>
-<li class="level1"><div class="li"> Mettez votre <strong><code>${PATH}</code></strong> pour quâ??il pointe vers lâ??endroit où vos nouveau exécutables gEDA sont placés (par exemple, <strong><code>/home/your-name/geda-install/bin</code></strong>). Assurez-vous que vous enlevez les pointeurs vers la anciennes versions de gEDA, sâ??ils existent. Vous ne devez pas seulement mettre le <strong><code>${PATH}</code></strong> dans votre shell courant mais vous devriez alors mettre à jour vos scripts de config (i.e. .bashrc ou .cshrc)</div>
-</li>
-<li class="level1"><div class="li"> Tapez «·rehash·» pour mettre à jour votre chemin de recherche des exécutables.</div>
-</li>
-<li class="level1"><div class="li"> Changez votre <strong><code>${LD_LIBRARY_PATH}</code></strong> pour quâ??il pointe sur lâ??endroitoù sont vos nouveaux exécutables gEDA (par exemple, <strong><code>/home/your-name/geda-install/lib</code></strong>). Assurez-vous dâ??enlever les pointeurs des anciennes versions de gEDA, si elles existent. Vous ne devez pas seulement mettre le <strong><code>${LD_LIBRARY_PATH}</code></strong> dans votre shell courant mais vous devriez alors mettre à jour vos scripts de config (i.e. .bashrc ou .cshrc)</div>
-</li>
-<li class="level1"><div class="li"> LAncez «·su -c ldconfig·» pour indiquer au noyau où trouver votre nouvelle libgeda.so.</div>
-</li>
-</ol>
-
-</div>
-<!-- SECTION "Waaaaa! L'installation s'est terminée mais j'ai un segfault (ou autre problème) lorsque je lance gschem (ou gattrib ou gnetlist, ou. . . )!" [8723-10033] -->
-<h2><a name="fedora_core_4_install_notes" id="fedora_core_4_install_notes">Fedora Core 4 install notes</a></h2>
-<div class="level2">
-
-<p>
-<a href="geda_fc4.html" class="wikilink1" title="geda:fc4">FC4 notes available here</a>
-</p>
-
-</div>
-<!-- SECTION "Fedora Core 4 install notes" [10034-10112] -->
-<h2><a name="fedora_core_3_install_notes" id="fedora_core_3_install_notes">Fedora Core 3 install notes</a></h2>
-<div class="level2">
-
-<p>
-<a href="geda_fc3.html" class="wikilink1" title="geda:fc3">FC3 notes available here</a>
-</p>
-
-</div>
-<!-- SECTION "Fedora Core 3 install notes" [10113-10191] -->
-<h2><a name="fedora_core_2_install_notes" id="fedora_core_2_install_notes">Fedora Core 2 install notes</a></h2>
-<div class="level2">
-
-<p>
-<a href="geda_fc2.html" class="wikilink1" title="geda:fc2">FC2 notes available here</a>
-</p>
-
-</div>
-<!-- SECTION "Fedora Core 2 install notes" [10192-10270] -->
-<h2><a name="fedora_core_1_install_notes" id="fedora_core_1_install_notes">Fedora Core 1 install notes</a></h2>
-<div class="level2">
-
-<p>
-<a href="geda_fc1.html" class="wikilink1" title="geda:fc1">FC1 notes available here</a>
-</p>
-
-</div>
-<!-- SECTION "Fedora Core 1 install notes" [10271-10349] -->
-<h2><a name="suse_9.3_install_notes" id="suse_9.3_install_notes">Suse 9.3 install notes</a></h2>
-<div class="level2">
-
-<p>
-<a href="geda_suse_9.html" class="wikilink1" title="geda:suse_9.3">SuSE 9.3 notes available here</a>
-</p>
-
-</div>
-<!-- SECTION "Suse 9.3 install notes" [10350-10433] -->
-<h2><a name="suse_10.0_install_notes" id="suse_10.0_install_notes">Suse 10.0 install notes</a></h2>
-<div class="level2">
-
-<p>
-<a href="geda_suse_10.html" class="wikilink1" title="geda:suse_10.0">SuSE 10.0 notes available here</a>
-</p>
-
-</div>
-<!-- SECTION "Suse 10.0 install notes" [10434-10520] -->
-<h2><a name="suse_10.1_install_notes" id="suse_10.1_install_notes">Suse 10.1 install notes</a></h2>
-<div class="level2">
-
-<p>
-<a href="001geda_suse_10.html" class="wikilink1" title="geda:suse_10.1">SuSE 10.1 notes available here</a>
-</p>
-
-</div>
-<!-- SECTION "Suse 10.1 install notes" [10521-10607] -->
-<h2><a name="notes_d_installation_debian" id="notes_d_installation_debian">Notes d'installation Debian</a></h2>
-<div class="level2">
-
-<p>
-Les <a href="001geda_debian.html" class="wikilink1" title="geda:debian.fr">notes d'installation Debian sont disponibles ici</a>
-</p>
-
-</div>
-<!-- SECTION "Notes d'installation Debian" [10608-10720] -->
-<h2><a name="windows_install_notes" id="windows_install_notes">Windows install notes</a></h2>
-<div class="level2">
-
-<p>
-<a href="geda_cygwin.html" class="wikilink1" title="geda:cygwin">Cygwin notes available here</a>
-</p>
-
-</div>
-<!-- SECTION "Windows install notes" [10721-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/001geda_kig_howto.html b/docs/wiki/001geda_kig_howto.html
deleted file mode 100644
index e91358e..0000000
--- a/docs/wiki/001geda_kig_howto.html
+++ /dev/null
@@ -1,27 +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>geda:kig_howto.fr</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="noindex,follow" />
-<meta name="date" content="1969-12-31T19:00:00-0500" />
-<meta name="keywords" content="geda,kig_howto.fr" />
-<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/geda:kig_howto.fr?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:kig_howto.fr"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:kig_howto.fr"; />
-<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>
-</body>
-</html>
diff --git a/docs/wiki/001geda_pcb-quick_reference.html b/docs/wiki/001geda_pcb-quick_reference.html
deleted file mode 100644
index 34666bf..0000000
--- a/docs/wiki/001geda_pcb-quick_reference.html
+++ /dev/null
@@ -1,459 +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>geda:pcb-quick_reference.fr</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="keywords" content="geda,pcb-quick_reference.fr" />
-<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/geda:pcb-quick_reference.fr?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:pcb-quick_reference.fr"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:pcb-quick_reference.fr"; />
-<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="#pcbreference_rapide" class="toc">PCB: Référence Rapide</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#disposition_des_touches" class="toc">Disposition des Touches</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#table_des_touches_pcb" class="toc">Table des Touches PCB</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#touches_de_visualisation" class="toc">Touches de Visualisation</a></span></div></li>
-</ul>
-</li>
-<li class="level1"><div class="li"><span class="li"><a href="#reference_d_empreintes" class="toc">Référence d'Empreintes</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#syntaxe_generale" class="toc">Syntaxe Générale</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#elements" class="toc">�léments</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#pastilles" class="toc">Pastilles</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#broches" class="toc">Broches</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#exemples" class="toc">Exemples</a></span></div></li></ul>
-</li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="pcbreference_rapide" id="pcbreference_rapide">PCB: Référence Rapide</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "PCB: Référence Rapide" [1-39] -->
-<h2><a name="disposition_des_touches" id="disposition_des_touches">Disposition des Touches</a></h2>
-<div class="level2">
-
-</div>
-<!-- SECTION "Disposition des Touches" [40-76] -->
-<h3><a name="table_des_touches_pcb" id="table_des_touches_pcb">Table des Touches PCB</a></h3>
-<div class="level3">
-<table class="inline">
- <tr>
- <th class="centeralign"> TOUCHE </th><th class="leftalign"> MNEMONIQUE </th><th class="centeralign"> DESCRIPTION </th>
- </tr>
- <tr>
- <td class="centeralign"> esc </td><td class="leftalign"> panner </td><td> enter panning mode </td>
- </tr>
- <tr>
- <td class="centeralign"> insert </td><td class="leftalign"> insert point </td><td> enter insert point mode. Click and drag on track to insert a point </td>
- </tr>
- <tr>
- <td class="centeralign"> space </td><td class="leftalign"> select </td><td class="leftalign"> entrez en mode select </td>
- </tr>
- <tr>
- <td class="centeralign"> tab </td><td class="leftalign"> flip view </td><td class="leftalign"> view: flip board </td>
- </tr>
- <tr>
- <td class="centeralign"> shift-del </td><td class="leftalign"> del-cu </td><td class="leftalign"> deletes electrically connected copper (including power and signal planes) </td>
- </tr>
- <tr>
- <td class="centeralign"> \ </td><td class="leftalign"> thin-draw </td><td class="leftalign"> toggles thin draw mode </td>
- </tr>
- <tr>
- <td class="centeralign"> shift-alt-a </td><td class="leftalign"> unselect </td><td class="leftalign"> clear selection </td>
- </tr>
- <tr>
- <td class="centeralign"> b </td><td class="leftalign"> to other side </td><td class="leftalign"> flip object to the other side of the board </td>
- </tr>
- <tr>
- <td class="centeralign"> shift-b </td><td class="leftalign"> flip view </td><td class="leftalign"> view: flip board </td>
- </tr>
- <tr>
- <td class="centeralign"> c </td><td class="leftalign"> center </td><td class="leftalign"> view: center display at cursor position </td>
- </tr>
- <tr>
- <td class="centeralign"> ctrl-c </td><td> copy to buffer</td><td class="leftalign"> copie la sélection vers le tampon et désélectionne </td>
- </tr>
- <tr>
- <td class="centeralign"> d </td><td class="leftalign"> display name </td><td class="leftalign"> affiche le nom de la broche ou pastille </td>
- </tr>
- <tr>
- <td class="centeralign"> shift-d </td><td class="leftalign"> pinout dialog </td><td class="leftalign"> open pinout window for element under mouse cursor </td>
- </tr>
- <tr>
- <td class="centeralign"> e </td><td> eliminate rats</td><td class="leftalign"> efface tous les rats </td>
- </tr>
- <tr>
- <td class="centeralign"> shift-e </td><td class="leftalign"> eliminate some rats </td><td class="leftalign"> efface tous les rats sélectionnés </td>
- </tr>
- <tr>
- <td class="centeralign"> f </td><td class="leftalign"> find </td><td class="leftalign"> highlight connections to object under mouse cursor </td>
- </tr>
- <tr>
- <td class="centeralign"> shift-f </td><td class="leftalign"> un-find </td><td class="leftalign"> un-highlight found connections </td>
- </tr>
- <tr>
- <td class="centeralign"> g </td><td class="leftalign"> increase grid </td><td class="leftalign"> increment grid by configured grid increment </td>
- </tr>
- <tr>
- <td class="centeralign"> shift-g </td><td class="leftalign"> decrease grid </td><td class="leftalign"> decrement grid by configured grid increment </td>
- </tr>
- <tr>
- <td class="centeralign"> h </td><td class="leftalign"> hide </td><td class="leftalign"> toggle the visiblity of the refdes or value attached to the current component </td>
- </tr>
- <tr>
- <td class="centeralign"> ctrl-h </td><td class="leftalign"> holeplate </td><td class="leftalign"> toggle plating of a via. Used to produce non metalized mounting holes </td>
- </tr>
- <tr>
- <td class="centeralign"> k </td><td class="leftalign"> klearance </td><td class="leftalign"> increment clearance (soldermask to copper edge) </td>
- </tr>
- <tr>
- <td class="centeralign"> shift-k </td><td class="leftalign"> klear (-) </td><td class="leftalign"> decrement clearance (soldermask to copper edge (NOTE: can go negative!)) </td>
- </tr>
- <tr>
- <td class="centeralign"> l </td><td class="leftalign"> increase line </td><td class="leftalign"> increment width of the line tool, adds to the settings of the current line style </td>
- </tr>
- <tr>
- <td class="centeralign"> shift-l </td><td class="leftalign"> decrease line </td><td> reduce the current linewidth </td>
- </tr>
- <tr>
- <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>
- </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>
- </tr>
- <tr>
- <td class="centeralign"> n </td><td class="leftalign"> name </td><td> show object refdes / pin number at mouse pointer </td>
- </tr>
- <tr>
- <td class="centeralign"> shift-n </td><td class="leftalign"> next </td><td> Select the shortest unselected rat on the board </td>
- </tr>
- <tr>
- <td class="centeralign"> o </td><td class="leftalign"> optimize rats </td><td> optimize and redraw all rats </td>
- </tr>
- <tr>
- <td class="centeralign"> shift-o </td><td class="leftalign"> optimize some rats </td><td> optimize and redraw selected nets only </td>
- </tr>
- <tr>
- <td class="centeralign"> shift-p </td><td class="leftalign"> polygon close </td><td class="leftalign"> connect the first point of a polygon with the last </td>
- </tr>
- <tr>
- <td class="centeralign"> q </td><td class="leftalign"> square toggle </td><td class="leftalign"> toggle square/round corners on pads </td>
- </tr>
- <tr>
- <td class="centeralign"> ctrl-r </td><td class="leftalign"> report </td><td class="leftalign"> show object report </td>
- </tr>
- <tr>
- <td class="centeralign"> s </td><td class="leftalign"> size </td><td class="leftalign"> augmente la taille </td>
- </tr>
- <tr>
- <td class="centeralign"> shift-s </td><td class="leftalign"> size (-) </td><td class="leftalign"> diminue la taille </td>
- </tr>
- <tr>
- <td class="centeralign"> alt-s </td><td class="leftalign"> sizehole </td><td class="leftalign"> augmente la taille du trou </td>
- </tr>
- <tr>
- <td class="centeralign"> alt-shift-s </td><td class="leftalign"> sizehole (-) </td><td class="leftalign"> diminue la taille du trou </td>
- </tr>
- <tr>
- <td class="centeralign"> ctrl-s </td><td class="leftalign"> sizehole </td><td class="leftalign"> augmente la taille du trou </td>
- </tr>
- <tr>
- <td class="centeralign"> ctrl-shift-s </td><td class="leftalign"> sizehole (-) </td><td class="leftalign"> diminue la taille du trou </td>
- </tr>
- <tr>
- <td class="centeralign"> v </td><td class="leftalign"> view extents </td><td class="leftalign"> vue globale de la zone de travail </td>
- </tr>
- <tr>
- <td class="centeralign"> z </td><td class="leftalign"> zoom </td><td class="leftalign"> voir: agrandir </td>
- </tr>
- <tr>
- <td class="centeralign"> shift-z </td><td class="leftalign"> un-zoom </td><td class="leftalign"> voir: réduire </td>
- </tr>
- <tr>
- <td class="centeralign"> F1 </td><td class="leftalign"> via </td><td> entrer lâ??outil de via </td>
- </tr>
- <tr>
- <td class="centeralign"> F2 </td><td class="leftalign"> line </td><td class="leftalign"> entrer lâ??outil de ligne </td>
- </tr>
- <tr>
- <td class="centeralign"> F3 </td><td class="leftalign"> arc </td><td> entrer lâ??outil dâ??arc </td>
- </tr>
- <tr>
- <td class="centeralign"> F4 </td><td class="leftalign"> text </td><td> entrer lâ??outil de texte </td>
- </tr>
- <tr>
- <td class="centeralign"> F5 </td><td class="leftalign"> rectangle </td><td class="leftalign"> entrer lâ??outil de rectangle </td>
- </tr>
- <tr>
- <td class="centeralign"> F6 </td><td class="leftalign"> polygon </td><td class="leftalign"> entrer lâ??outil de polygone </td>
- </tr>
- <tr>
- <td class="centeralign"> F7 </td><td class="leftalign"> buffer </td><td> entrer lâ??outil de mode tampon </td>
- </tr>
- <tr>
- <td class="centeralign"> F8 </td><td class="leftalign"> delete </td><td class="leftalign"> entrer lâ??outil de mode supression </td>
- </tr>
- <tr>
- <td class="centeralign"> F9 </td><td class="leftalign"> rotate </td><td class="leftalign"> entrer lâ??outil de mode de rotation </td>
- </tr>
- <tr>
- <td class="centeralign"> F10 </td><td class="leftalign"> file menu </td><td class="leftalign"> menu fichier </td>
- </tr>
- <tr>
- <td class="centeralign"> F11 </td><td class="leftalign"> select </td><td class="leftalign"> entrer dans le mode sélection (comme [space]) </td>
- </tr>
- <tr>
- <td class="centeralign"> F12 </td><td class="leftalign"> lock </td><td> entrer dans le mode lock </td>
- </tr>
-</table>
-
-</div>
-<!-- SECTION "Table des Touches PCB" [77-3777] -->
-<h2><a name="touches_de_visualisation" id="touches_de_visualisation">Touches de Visualisation</a></h2>
-<div class="level2">
-<table class="inline">
- <tr>
- <th class="centeralign"> TOUCHE </th><th class="centeralign"> MNEMONIC </th><th class="centeralign"> DESCRIPTION </th>
- </tr>
- <tr>
- <td class="centeralign"> esc </td><td class="centeralign"> panner </td><td class="rightalign"> </td>
- </tr>
- <tr>
- <td class="centeralign"> v </td><td class="centeralign"> view extents </td><td>vue globale de la zone de travail</td>
- </tr>
- <tr>
- <td class="centeralign"> c </td><td class="centeralign"> center </td><td>centre la vue sur le curseur</td>
- </tr>
- <tr>
- <td class="centeralign"> z </td><td class="centeralign"> zoom </td><td>agrandissement</td>
- </tr>
- <tr>
- <td class="centeralign"> shift-z </td><td class="centeralign"> un-zoom </td><td class="rightalign"> </td>
- </tr>
- <tr>
- <td class="centeralign"> \ </td><td class="centeralign"> thin-draw on/off </td><td>toggles thin draw mode</td>
- </tr>
- <tr>
- <td class="centeralign"> tab </td><td class="centeralign"> flip view </td><td>retournement carte</td>
- </tr>
- <tr>
- <td class="centeralign"> shift-b </td><td class="centeralign"> flip view </td><td>retournement carte</td>
- </tr>
-</table>
-
-</div>
-<!-- SECTION "Touches de Visualisation" [3778-4194] -->
-<h1><a name="reference_d_empreintes" id="reference_d_empreintes">Référence d'Empreintes</a></h1>
-<div class="level1">
-
-<p>
- Le document maître pour la création dâ??empreintes est le <a href="http://pcb.sourceforge.net/index.html#dir"; class="urlextern" title="http://pcb.sourceforge.net/index.html#dir"; rel="nofollow">PCB Manual</a>. Il y a aussi le <a href="http://www.brorson.com/gEDA/land_patterns_20050129.pdf"; class="urlextern" title="http://www.brorson.com/gEDA/land_patterns_20050129.pdf"; rel="nofollow">Footprint Creation for the Open-Source Layout Program PCB</a> de Stuart Brorson.
-</p>
-
-</div>
-<!-- SECTION "Référence d'Empreintes" [4195-4503] -->
-<h2><a name="syntaxe_generale" id="syntaxe_generale">Syntaxe Générale</a></h2>
-<div class="level2">
-
-<p>
- Un fichier dâ??empreinte pcb peut contenir une des commandes suivantes:
-</p>
-<ul>
-<li class="level1"><div class="li"> <strong><code>Element [element_flags, description, pcb-name, value, mark_x, mark_y, text_x, text_y, text_direction, text_scale, text_flags]</code></strong></div>
-</li>
-<li class="level1"><div class="li"> <strong><code>Pad [x1 y1 x2 y2 thickness clearance mask name pad_number flags]</code></strong></div>
-</li>
-<li class="level1"><div class="li"> <strong><code>Pin [x y thickness clearance mask drillholedia name number flags]</code></strong></div>
-</li>
-<li class="level1"><div class="li"> <strong><code>ElementArc [x y r1 r2 startangle sweepangle thickness]</code></strong></div>
-</li>
-<li class="level1"><div class="li"> <strong><code>ElementLine [x1 y1 x2 y2 thickness] â??> thickness != 1000 = 10 mils almost for all footprints</code></strong></div>
-</li>
-<li class="level1"><div class="li"> Les lignes de commentaires débutent avec le signe â??<strong><code>#</code></strong>â??</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Syntaxe Générale" [4504-5144] -->
-<h2><a name="elements" id="elements">�léments</a></h2>
-<div class="level2">
-
-<p>
-<strong><code>Element [element_flags, description, pcb-name, value, mark_x, mark_y, text_x, text_y, text_direction, text_scale, text_flags]</code></strong>
-</p>
-<table class="inline">
- <tr>
- <th class="centeralign"> item </th><th class="centeralign"> allowed value </th><th class="centeralign"> explanation </th><th class="centeralign"> comment </th>
- </tr>
- <tr>
- <td class="centeralign"> element_flags </td><td class="centeralign"> unsigned hex value </td><td class="rightalign"> </td><td class="rightalign"> </td>
- </tr>
- <tr>
- <td class="centeralign"> description </td><td class="centeralign"> string </td><td class="centeralign"> text descriptif de lâ??empreinte </td><td class="leftalign">écrit par lâ??auteur de lâ??empreinte </td>
- </tr>
- <tr>
- <td class="centeralign"> pcb name </td><td class="centeralign"> string </td><td class="centeralign"> refdes utilisé pour ce pcb particulier </td><td class="leftalign">xxx </td>
- </tr>
- <tr>
- <td class="centeralign"> value </td><td class="centeralign"> string </td><td class="centeralign"> valeur du composant sur ce pcb particulier </td><td class="leftalign">xxx </td>
- </tr>
- <tr>
- <td class="centeralign"> mark_x </td><td class="centeralign"> 1/100th mils </td><td class="rightalign"> </td><td class="rightalign"> </td>
- </tr>
- <tr>
- <td class="centeralign"> mark_y </td><td class="centeralign"> 1/100th mils </td><td class="rightalign"> </td><td class="rightalign"> </td>
- </tr>
- <tr>
- <td class="centeralign"> text_x </td><td class="centeralign"> 1/100th mils </td><td class="rightalign"> </td><td class="rightalign"> </td>
- </tr>
- <tr>
- <td class="centeralign"> text_y </td><td class="centeralign"> 1/100th mils </td><td class="rightalign"> </td><td class="rightalign"> </td>
- </tr>
- <tr>
- <td class="centeralign"> text direction </td><td class="centeralign"> decimal integer </td><td class="centeralign"> 0=horiz; 1=ccw90; 2=180; 3=cw90 </td><td class="rightalign"> </td>
- </tr>
- <tr>
- <td class="centeralign"> text_scale </td><td class="centeralign"> decimal integer </td><td class="rightalign"> </td><td class="leftalign">usu. set 100 </td>
- </tr>
- <tr>
- <td class="centeralign"> text_flags </td><td class="centeralign"> unsigned hex </td><td class="rightalign"> </td><td class="rightalign"> </td>
- </tr>
-</table>
-
-</div>
-<!-- SECTION "�léments" [5145-5981] -->
-<h2><a name="pastilles" id="pastilles">Pastilles</a></h2>
-<div class="level2">
-
-<p>
-<strong><code>Pad[x1 y1 x2 y2 thickness clearance mask name pad_number flags]</code></strong>
-</p>
-<table class="inline">
- <tr>
- <th class="centeralign"> Item </th><th class="centeralign"> Allowed Value </th><th class="centeralign"> Explanation </th><th class="centeralign"> Comment </th>
- </tr>
- <tr>
- <td class="centeralign"> x1 </td><td class="centeralign"> 1/100th mils </td><td class="centeralign"> x(1st point) </td><td class="rightalign"> </td>
- </tr>
- <tr>
- <td class="centeralign"> y1 </td><td class="centeralign"> 1/100th mils </td><td class="centeralign"> y(1st point) </td><td class="rightalign"> </td>
- </tr>
- <tr>
- <td class="centeralign"> x2 </td><td class="centeralign"> 1/100th mils </td><td class="centeralign"> x(2nd point) </td><td class="rightalign"> </td>
- </tr>
- <tr>
- <td class="centeralign"> y2 </td><td class="centeralign"> 1/100th mils </td><td class="centeralign"> y(2nd point) </td><td class="rightalign"> </td>
- </tr>
- <tr>
- <td class="centeralign"> thickness </td><td class="centeralign"> 1/100 mils </td><td class="centeralign"> épaisseur de métal entourant le segment de ligne </td><td class="leftalign">voir le .pdf de Brorson </td>
- </tr>
- <tr>
- <td class="centeralign"> clearance </td><td class="centeralign"> 1/100 mils </td><td class="centeralign"> distance vis à vis des autres zones de cuivre sur toutes les couches </td><td class="leftalign">actually 1/2 of this number is used! </td>
- </tr>
- <tr>
- <td class="centeralign"> mask </td><td class="centeralign"> 1/100th mils </td><td class="centeralign"> width of mask relief </td><td class="leftalign">actual width of the mask centered on pad copper </td>
- </tr>
- <tr>
- <td class="centeralign"> name </td><td class="centeralign"> string </td><td class="centeralign"> name of pad (arb. string) </td><td class="leftalign">e.g. â??pad_1â?? or â??positiveâ?? or any other string </td>
- </tr>
- <tr>
- <td class="centeralign"> pad_number </td><td class="centeralign"> string </td><td class="centeralign"> pad # </td><td class="leftalign">used for nets. it MUST be consistent with the definitions on the netlist. </td>
- </tr>
- <tr>
- <td class="centeralign"> flags </td><td class="centeralign"> hex value </td><td class="centeralign"> xxx </td><td class="rightalign"> </td>
- </tr>
-</table>
-
-</div>
-<!-- SECTION "Pastilles" [5982-6937] -->
-<h2><a name="broches" id="broches">Broches</a></h2>
-<div class="level2">
-
-<p>
-<strong><code>Pin[x y thickness clearance mask drillholedia name number flags]</code></strong>
-</p>
-<table class="inline">
- <tr>
- <th class="centeralign"> Item </th><th class="leftalign"> Allowed Value </th><th class="centeralign"> Explanation </th><th class="centeralign"> Comment </th>
- </tr>
- <tr>
- <td class="centeralign"> x </td><td class="centeralign"> 1/100th mils </td><td class="centeralign"> pin x coord. </td><td class="rightalign"> </td>
- </tr>
- <tr>
- <td class="centeralign"> y </td><td class="centeralign"> 1/100th mils </td><td class="centeralign"> pin y coord. </td><td class="rightalign"> </td>
- </tr>
- <tr>
- <td class="centeralign"> thickness </td><td class="centeralign"> 1/100th mils </td><td class="centeralign"> copper diameter </td><td class="rightalign"> </td>
- </tr>
- <tr>
- <td class="centeralign"> clearance </td><td class="centeralign"> 1/100th mils </td><td class="centeralign"> 2*(cu to cu clearance) </td><td class="leftalign">if you want a 10 mil clearance, put 2000 (20 mils) here </td>
- </tr>
- <tr>
- <td class="centeralign"> mask </td><td class="centeralign"> 1/100th mils </td><td class="centeralign"> diameter of mask aperture </td><td class="leftalign">actual dia. of hole in mask </td>
- </tr>
- <tr>
- <td class="centeralign"> drillholedia </td><td class="centeralign"> 1/100th mils </td><td class="centeralign"> dia. of hole </td><td class="rightalign"> </td>
- </tr>
- <tr>
- <td class="centeralign"> name </td><td class="centeralign"> string </td><td class="centeralign"> arb. pin name </td><td class="rightalign"> </td>
- </tr>
- <tr>
- <td class="centeralign"> number </td><td class="centeralign"> decimal integer </td><td class="centeralign"> pin number used by nets/rats </td><td class="rightalign"> </td>
- </tr>
- <tr>
- <td class="centeralign"> flags </td><td class="centeralign"> hex </td><td class="centeralign"> xxx </td><td class="rightalign"> </td>
- </tr>
-</table>
-
-</div>
-<!-- SECTION "Broches" [6938-7639] -->
-<h2><a name="exemples" id="exemples">Exemples</a></h2>
-<div class="level2">
-<ul>
-<li class="level1"><div class="li"> <strong><code>Pad[-24606 14760 -19538 14760 1181 2000 3181 â??â?? â??16â?? â??squareâ??]</code></strong></div>
-</li>
-<li class="level1"><div class="li"> <strong><code>Pad[-14760 19538 -14760 24606 1181 2000 3181 â??â?? â??17â?? â??square,edge2â??]</code></strong></div>
-</li>
-<li class="level1"><div class="li"> <strong><code>Pin[0 0 12000 2000 12500 6400 â??â?? â??1â?? 0Ã?00000001]</code></strong></div>
-</li>
-<li class="level1"><div class="li"> <strong><code>ElementArc [0 0 6800 6800 0 360 1000]</code></strong></div>
-</li>
-<li class="level1"><div class="li"> <strong><code>ElementLine [-26696 -26696 26696 -26696 1000]</code></strong></div>
-</li>
-<li class="level1"><div class="li"> <strong><code># notes within PCB Footprints go after the pound sign</code></strong></div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Exemples" [7640-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/001geda_pcb_tips.html b/docs/wiki/001geda_pcb_tips.html
deleted file mode 100644
index 91993bc..0000000
--- a/docs/wiki/001geda_pcb_tips.html
+++ /dev/null
@@ -1,962 +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>geda:pcb_tips.fr</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-05-24T22:27:26-0400" />
-<meta name="keywords" content="geda,pcb_tips.fr" />
-<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/geda:pcb_tips.fr?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:pcb_tips.fr"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:pcb_tips.fr"; />
-<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="#outils_pcb" class="toc">Outils PCB</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#ou_puis-je_lire_les_bases_sur_l_utilisation_de_pcb" class="toc">Où puis-je lire les bases sur l'utilisation de pcb?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#j_ai_trouve_un_bogue_que_puis-je_y_faire" class="toc">J'ai trouvé un bogue·! Que puis-je y faire·?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#comment_configurer_les_regles_du_fabricant_a_utiliser_i.e._diametres_de_percage_specification_des_largeurs_espacements_des_pistes" class="toc">Comment configurer les règles du fabricant à utiliser (i.e. diamètres de perçage, spécification des largeurs/espacements des pistes)?</a></span></div></li>
-</ul>
-</li>
-<li class="level1"><div class="li"><span class="li"><a href="#a_propos_des_empreintes" class="toc">Ã? propos des empreintes</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#comment_fonctionne_le_systeme_d_empreintes_de_pcb" class="toc">Comment fonctionne le système d'empreintes de PCB?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#ou_puis-je_obtenir_des_empreintes_pre-dessinees_pour_pcb" class="toc">Où puis-je obtenir des empreintes pré-dessinées pour PCB?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#je_veux_utiliser_pcb_pour_faire_le_placement._comment_connaitre_la_valeur_a_utiliser_pour_l_attribut_d_empreinte" class="toc">Je veux utiliser PCB pour faire le placement. Comment connaitre la valeur à utiliser pour l'attribut d'empreinte?</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#newlib" class="toc">Newlib</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#bibliotheque_m4" class="toc">Bibliothèque M4</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#quelle_est_la_maniere_recommandee_pour_traiter_les_differentes_empreintes_pour_le_meme_type_de_composant" class="toc">Quelle est la manière recommandée pour traiter les différentes empreintes pour le même type de composant?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#comment_je_dessine_une_nouvelle_une_empreinte" class="toc">Comment je dessine une nouvelle une empreinte?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#comment_j_edite_change_une_empreinte_existante" class="toc">Comment j'édite/change une empreinte existante?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#comment_j_ajoute_une_bibliotheque_d_empreintes_a_pcb" class="toc">Comment j'ajoute une bibliothèque d'empreintes à PCB?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#pcb_ne_trouve_par_mes_empreintes._pourquoi" class="toc">PCB ne trouve par mes empreintes. Pourquoi?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#maintenant_que_j_ai_toutes_ces_empreintes_ou_dois-je_les_placer" class="toc">Maintenant que j'ai toutes ces empreintes, où dois-je les placer?</a></span></div></li>
-</ul>
-</li>
-<li class="level1"><div class="li"><span class="li"><a href="#placement_de_composants" class="toc">Placement de composants</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#comment_je_pivote_une_selection_i.e._pour_plus_d_un_element" class="toc">Comment je pivote une sélection (i.e. pour plus d'un élément)?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#comment_je_change_la_taille_de_l_objet_graphique_comme_du_texte_des_lignes_de_masque_texte_etc" class="toc">Comment je change la taille de l'objet graphique (comme du texte, des lignes de masque texte, etc)?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#comment_placer_les_composants_sur_les_deux_faces_de_pcb" class="toc">Comment placer les composants sur les deux faces de PCB?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#comment_je_place_l_origine_dans_pcb" class="toc">Comment je place l'origine dans pcb?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#comment_je_mesure_les_distances_et_les_dimensions_des_composants" class="toc">Comment je mesure les distances et les dimensions des composants?</a></span></div></li>
-</ul>
-</li>
-<li class="level1"><div class="li"><span class="li"><a href="#routage" class="toc">Routage</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#comment_router_une_connexion_depuis_le_cote_soudure_vers_le_cote_composant_et_inversement" class="toc">Comment router une connexion depuis le côté soudure vers le côté composant et inversement?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#comment_je_change_le_style_de_routage" class="toc">Comment je change le style de routage?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#j_ai_merde_comment_je_reviens_en_arriere" class="toc">J'ai merdé! Comment je reviens en arrière?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#comment_je_deplace_un_jeu_de_piste_d_une_couche_a_l_autre" class="toc">Comment je déplace un jeu de piste d'une couche à l'autre?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#comment_je_change_les_soldermask_clearance_autour_d_un_trou_via" class="toc">Comment je change les soldermask clearance autour d'un trou/via?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#comment_changer_la_taille_des_pistes" class="toc">Comment changer la taille des pistes?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#comment_je_pilote_un_via_pour_connecter_une_piste_a_un_plan_de_masse_sur_une_couche_differente" class="toc">Comment je pilote un via pour connecter une piste à un plan de masse sur une couche différente?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#je_veux_dessiner_une_piste_entre_deux_segments_sur_le_meme_net_mais_pcb_ne_me_laisse_pas_faire_pourquoi" class="toc">Je veux dessiner une piste entre deux segments sur le même net mais PCB ne me laisse pas faire! Pourquoi?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#pcb_semble_manger_mes_noms_de_composants_et_se_plaint_qu_il_ne_peut_pas_trouver_des_nets_adaptes_aux_broches_de_quoi_cela_vient" class="toc">PCB semble manger mes noms de composants et se plaint qu'il ne peut pas trouver des nets adaptés aux broches! De quoi cela vient?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#comment_je_peux_configurer_la_couleur_et_l_epaisseur_des_rats_nests" class="toc">Comment je peux configurer la couleur et l'épaisseur des rats nests?</a></span></div></li>
-</ul>
-</li>
-<li class="level1"><div class="li"><span class="li"><a href="#au_dela_des_pistes_et_des_empreintes" class="toc">Au delà des pistes et des empreintes</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#comment_je_trace_un_dessin_une_impression_ou_un_autre_pcb" class="toc">Comment je trace un dessin, une impression ou un autre PCB?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#je_ne_peux_pas_copier_des_pastilles_dans_un_circuit._comment_je_fais" class="toc">Je ne peux pas copier des pastilles dans un circuit. Comment je fais?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#comment_je_remplis_les_zones_avec_cuivre" class="toc">Comment je remplis les zones avec cuivre?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#les_polygones_mettent_mes_pistes_a_la_masse_que_puis-je_y_faire" class="toc">Les polygones mettent mes pistes à la masse! Que puis-je y faire?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#comment_je_change_le_polygon_clearance" class="toc">Comment je change le polygon clearance?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#comment_je_cache_les_polygones_lorsque_j_edite_le_placement" class="toc">Comment je cache les polygones lorsque j'édite le placement?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#comment_editer_les_polygones" class="toc">Comment éditer les polygones?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#comment_je_place_des_vias_qui_connectent_un_polygone_pour_une_dissipation_thermique_complete_ou_pour_une_integrite_de_protection_complete" class="toc">Comment je place des vias qui connectent un polygone pour une dissipation thermique complète ou pour une intégrité de protection complète?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#les_polygones_peuvent-ils_etre_un-masques_un_polygone_peut-il_etre_de_cuivre_sans_masque_de_soudure" class="toc">Les polygones peuvent-ils être un-masqués? (Un polygone peut-il être de cuivre sans masque de soudure?)</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#comment_je_place_des_trous_de_montage_mounting_hole" class="toc">Comment je place des trous de montage (mounting hole)?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#pourquoi_est-il_possible_de_realiser_des_ponts_thermiques_pour_les_broches_mais_pas_pour_une_pastille" class="toc">Pourquoi est-il possible de réaliser des ponts thermiques pour les broches mais pas pour une pastille?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#pcb_peut-il_etre_utilise_pour_realiser_des_cartes_a_simple_couche" class="toc">PCB peut-il être utilisé pour réaliser des cartes à simple couche?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#quelles_ressources_existent_pour_traiter_les_fichiers_pcb_en_utilisant_les_scripts" class="toc">Quelles ressources existent pour traiter les fichiers PCB en utilisant les scripts?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#comment_j_importe_des_graphiques_vectoriels_externe" class="toc">Comment j'importe des graphiques vectoriels externe?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#comment_j_attache_un_nom_a_mon_circuit" class="toc">Comment j'attache un nom à mon circuit?</a></span></div></li>
-</ul>
-</li>
-<li class="level1"><div class="li"><span class="li"><a href="#autorouteur" class="toc">Autorouteur</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#comment_je_force_l_autorouteur_a_ne_placer_des_pistes_que_sur_une_couche_particuliere" class="toc">Comment je force l'autorouteur à ne placer des pistes que sur une couche particulière?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#commennt_forcer_l_autorouteur_a_router_seulement_dans_les_limites_des_contours_du_pcb" class="toc">Commennt forcer l'autorouteur à router seulement dans les limites des contours du pcb?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#comment_je_route_les_plans_d_alimentation_et_de_masse_avec_l_autorouteur" class="toc">Comment je route les plans d'alimentation et de masse avec l'autorouteur?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#le_circuit_produit_par_l_autorouteur_est_inefficace" class="toc">Le circuit produit par l'autorouteur est inefficace!</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#le_circuit_produit_par_l_autorouteur_est_moche" class="toc">Le circuit produit par l'autorouteur est moche!</a></span></div></li>
-</ul>
-</li>
-<li class="level1"><div class="li"><span class="li"><a href="#generation_gerber_et_production_de_fichiers_i_o" class="toc">Génération Gerber et production de fichiers I/O</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#comment_je_realise_des_contours_de_carte_pour_proposer_mes_gerbers_vers_le_fabricant_de_carte" class="toc">Comment je réalise des contours de carte pour proposer mes gerbers vers le fabricant de carte?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#j_ai_fini_mon_placement._comment_je_le_controle" class="toc">J'ai fini mon placement. Comment je le contrôle?</a></span></div></li>
-</ul>
-</li>
-<li class="level1"><div class="li"><span class="li"><a href="#vous_n_avez_pas_repondu_a_mes_questions._ou_puis-je_trouver_d_autres_informations_sur_pcb" class="toc">Vous n'avez pas répondu à mes questions. Où puis-je trouver d'autres informations sur PCB?</a></span></div></li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="outils_pcb" id="outils_pcb">Outils PCB</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "Outils PCB" [1-26] -->
-<h2><a name="ou_puis-je_lire_les_bases_sur_l_utilisation_de_pcb" id="ou_puis-je_lire_les_bases_sur_l_utilisation_de_pcb">Où puis-je lire les bases sur l'utilisation de pcb?</a></h2>
-<div class="level2">
-
-<p>
-Le <a href="http://pcb.sourceforge.net/manual.html"; class="urlextern" title="http://pcb.sourceforge.net/manual.html"; rel="nofollow">manuel de pcb</a> contient une description concise de lâ??interface utilisateur dans la section «·Getting Started·» (<a href="http://pcb.sourceforge.net/pcb-20060822/pcb.html#Getting%20Started"; class="urlextern" title="http://pcb.sourceforge.net/pcb-20060822/pcb.html#Getting%20Started"; rel="nofollow">version 20060822</a>)
-</p>
-
-</div>
-<!-- SECTION "Où puis-je lire les bases sur l'utilisation de pcb?" [27-342] -->
-<h2><a name="j_ai_trouve_un_bogue_que_puis-je_y_faire" id="j_ai_trouve_un_bogue_que_puis-je_y_faire">J'ai trouvé un bogue·! Que puis-je y faire·?</a></h2>
-<div class="level2">
-<ol>
-<li class="level1"><div class="li"> Débutez en lisant <a href="http://pcb.sourceforge.net/bugs.html"; class="urlextern" title="http://pcb.sourceforge.net/bugs.html"; rel="nofollow">the pcb bug reporting page</a>.</div>
-</li>
-<li class="level1"><div class="li"> Contrôlez, de quoi avons-nous besoin pour reproduire le bogue.</div>
-</li>
-<li class="level1"><div class="li"> Demandez sur la liste de <a href="http://www.geda.seul.org/mailinglist/index.html"; class="urlextern" title="http://www.geda.seul.org/mailinglist/index.html"; rel="nofollow">diffusion de geda-user</a> sâ??il est en cours de correction ou sâ??il a été réglé avec la version la plus à jour de pcb. Notez que vous devez être inscrits sur la liste de diffusion de geda-user avant de pouvoir poster.</div>
-</li>
-<li class="level1"><div class="li"> Vérifiez si le problème est déjà répertorié dans le <a href="http://sourceforge.net/tracker/?group_id=73743&atid=538811"; class="urlextern" title="http://sourceforge.net/tracker/?group_id=73743&atid=538811"; rel="nofollow">bug tracking system de pcb</a>. Si ce nâ??est pas le cas; émettez un rapport de bogue. Assurez-vous de donner toutes les informations nécessaires pour reproduire le bogue et ajoutez la version de pcb qui contient le bogue.</div>
-</li>
-<li class="level1"><div class="li"> Finallement, avec tous les projets open source ouverts, vous pourriez muscler vos muscles de programmation et tenter de régler le bogue par vous même. Veuillez envoyer un correctif sur les changements que vous avez effectués sur le <a href="http://sourceforge.net/tracker/?group_id=73743&atid=538811"; class="urlextern" title="http://sourceforge.net/tracker/?group_id=73743&atid=538811"; rel="nofollow">BTS de pcb</a>. Le correctif sera accepté avec reconnaissance pour améliorer la prochaine version de pcb.</div>
-</li>
-</ol>
-
-</div>
-<!-- SECTION "J'ai trouvé un bogue·! Que puis-je y faire·?" [343-1613] -->
-<h2><a name="comment_configurer_les_regles_du_fabricant_a_utiliser_i.e._diametres_de_percage_specification_des_largeurs_espacements_des_pistes" id="comment_configurer_les_regles_du_fabricant_a_utiliser_i.e._diametres_de_percage_specification_des_largeurs_espacements_des_pistes">Comment configurer les règles du fabricant à utiliser (i.e. diamètres de perçage, spécification des largeurs/espacements des pistes)?</a></h2>
-<div class="level2">
-
-<p>
-Ce sujet est couvert dans la documentation disponible sur <a href="http://pcb.sourceforge.net/pcb-20060422/pcb.html#Vendor%20drill%20mapping"; class="urlextern" title="http://pcb.sourceforge.net/pcb-20060422/pcb.html#Vendor%20drill%20mapping"; rel="nofollow">le site PCBe</a>.
-</p>
-
-</div>
-<!-- SECTION "Comment configurer les règles du fabricant à utiliser (i.e. diamètres de perçage, spécification des largeurs/espacements des pistes)?" [1614-1915] -->
-<h1><a name="a_propos_des_empreintes" id="a_propos_des_empreintes">Ã? propos des empreintes</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "Ã? propos des empreintes" [1916-1955] -->
-<h2><a name="comment_fonctionne_le_systeme_d_empreintes_de_pcb" id="comment_fonctionne_le_systeme_d_empreintes_de_pcb">Comment fonctionne le système d'empreintes de PCB?</a></h2>
-<div class="level2">
-
-<p>
-PCB supporte deux mécanismes de bibliothèque entièrement séparés:
-</p>
-<ol>
-<li class="level1"><div class="li"> Le premier est appelé «·oldlib·», «·pcblib·» ou «·bibliothèque M4·». Ce système est historique·; il dépend du langage macro M4 pour générer des empreintes à la volée. La bibliothèque M4 est assez grande et a quelques bogues. Néanmoins, elle est très maniable et est distribuée avec PCB. Un fonctionnalité puissante de la bibliothèque m4 est quâ??une famille complète dâ??empreintes peut être définie rapidement avec une macro de base appropriée.</div>
-</li>
-<li class="level1"><div class="li"> La seconde bibliothèque dâ??empreintes pour PCB est appelée «·newlib·». Les empreintes de newlib sont définies en utilisant des fichiers de texte <acronym title="American Standard Code for Information Interchange">ASCII</acronym> qui appelent des primitives graphiques réalisant une empreinte complète. Les empreintes newlib peuvent aussi être créées graphiquement en utilisant PCB ou par toute autre méthode qui peut produire un fichier texte (éditeur de texte, script awk/perl/ruby, etc.). </div>
-</li>
-</ol>
-
-<p>
- Câ??est pourquoi, pendant le placement, vous pouvez utiliser des empreintes qui sont distribuées avec PCB, vous pouvez trouver des empreintes par une recherche web ou vous pouvez vous créer la votre et la placer dans un répertoire dédié. Le <a href="http://pcb.sourceforge.net/manual.html"; class="urlextern" title="http://pcb.sourceforge.net/manual.html"; rel="nofollow">manuel pcb</a> est complet et mise à jour pour le format de fichier élément. Un tutoriel assez incomplet mais utile est disponible sur le web comme: <a href="http://www.brorson.com/gEDA/"; class="urlextern" title="http://www.brorson.com/gEDA/"; rel="nofollow">http://www.brorson.com/gEDA/</a> (recherche des termes «·newlib·»).
-</p>
-
-</div>
-<!-- SECTION "Comment fonctionne le système d'empreintes de PCB?" [1956-3509] -->
-<h2><a name="ou_puis-je_obtenir_des_empreintes_pre-dessinees_pour_pcb" id="ou_puis-je_obtenir_des_empreintes_pre-dessinees_pour_pcb">Où puis-je obtenir des empreintes pré-dessinées pour PCB?</a></h2>
-<div class="level2">
-
-<p>
-Actuellement, le meilleur endroit pour avoir de empreintes (en plus de la distribution PCB) est le <a href="http://www.gedasymbols.org/"; class="urlextern" title="http://www.gedasymbols.org"; rel="nofollow">site web des symboles gEDA</a>. Le <a href="http://www.luciani.org/geda/pcb/pcb-footprint-list.html"; class="urlextern" title="http://www.luciani.org/geda/pcb/pcb-footprint-list.html"; rel="nofollow">site web de John Luciani</a> possède une grand nombre dâ??empreintes et dâ??outils. De même, Darrell Harmon fournit un chouette script de génération dâ??empreintes <a href="http://www.dlharmon.com/geda/footgen.html"; class="urlextern" title="http://www.dlharmon.com/geda/footgen.html"; rel="nofollow">sur son site web</a>. Votre contribution au projet est la bienvenue, ainsi que le partage des empreintes. Finallement, vous pouvez demander sur la liste geda-user car quelquâ??un pourrait avoir pitié et vous envoyer un symbole. Notez que vous devez souscrire à la liste de diffusion geda-user avant de pouvoir poster.
-</p>
-
-</div>
-<!-- SECTION "Où puis-je obtenir des empreintes pré-dessinées pour PCB?" [3510-4322] -->
-<h2><a name="je_veux_utiliser_pcb_pour_faire_le_placement._comment_connaitre_la_valeur_a_utiliser_pour_l_attribut_d_empreinte" id="je_veux_utiliser_pcb_pour_faire_le_placement._comment_connaitre_la_valeur_a_utiliser_pour_l_attribut_d_empreinte">Je veux utiliser PCB pour faire le placement. Comment connaitre la valeur à utiliser pour l'attribut d'empreinte?</a></h2>
-<div class="level2">
-
-<p>
-Cette question est une des plus habituelle parmi les nouveaux utilisateurs de gEDA. De fait, aider les nouveaux à déterminer les noms dâ??empreintes appropriés est au coeur dâ??un débat en cours sur les <a href="http://geda.seul.org/wiki/geda:faq-gschem.fr#quel_est_l_objet_de_cette_polemique_entre_les_symboles_lourds_et_legers"; class="wikilink1" title="geda:faq-gschem.fr">symboles légers vs. lourds</a>. Dans la distribution courante gEDA/gaf, les symboles sont légers, vous devez attacher lâ??attribut footprint au niveau du schéma (i.e. en utilisant soit gschem, soit gattrib). Le nom des empreintes à utiliser dépend de si vous utilisez la bibliothèque newlib ou M4 (pcblib).
-</p>
-
-</div>
-<!-- SECTION "Je veux utiliser PCB pour faire le placement. Comment connaitre la valeur à utiliser pour l'attribut d'empreinte?" [4323-5057] -->
-<h3><a name="newlib" id="newlib">Newlib</a></h3>
-<div class="level3">
-
-<p>
-Newlib stocke une empreinte par fichier et les noms utilisés par newlib sont des noms de fichier des fichiers dâ??empreinte.
-</p>
-
-<p>
-Il y a plusieurs manières de trouver les noms dâ??empreintes newlib à utiliser·:
-</p>
-<ul>
-<li class="level1"><div class="li"> Vous pouvez naviguer dans les empreintes disponibles enlançant pcb et en ouvrant la fenêtre de bibliothèque dâ??empreintes (disponibles depuis la barre de menu par «·Window â?? library·»). Clickez sur le groupe de bibliothèques «·newlib·» et sélectionnez une sous-bibliothèque pour chercher ses symboles. Le nom de chaque empreinte apparaît dans la fenêtre «·Elements·» sur le côté droit du navigateur de bibliothèque. Utilisez le nom exactement tel quâ??il apparaît dans le navigateur pour lâ??attribut dâ??empreinte dans gschem ou gattrib.</div>
-</li>
-<li class="level1"><div class="li"> Les empreintes newlib distribuées avec PCB sont stockées dans les répertoires sous <strong><code>${PREFIX}/share/pcb/newlib</code></strong>. (<strong><code>${PREFIX}</code></strong> est le répertoire dâ??installation spécifié lors de la configuration/compilation de PCB.) Le nom à coller avec lâ??attribut «·footprint·» est le nom de fichier de lâ??empreinte que vous souhaitez utiliser.<br/>
- Par exemple, sur ma machine, jâ??ai installé gEDA avec le préfix <strong><code>/usr/local/geda/</code></strong>. Le boîtier 0805 (pour les résistances ou capas SMT) est dans un fichier avec un chemin absolu<br/>
- <strong><code>/usr/local/geda/share/pcb/newlib/generic_SMD_packages/0805_reflow_solder</code></strong> <br/>
- Donc, pour utiliser cette empreinte avec un composant, je met son attribut «·footprint·» à <strong><code>0805_reflow_solder</code></strong> en utilisant gschem ou gattrib.<br/>
- Notez que si le symbole newlib que vous voulez utiliser est dans un répertoire non-standard, gsch2pcb aura besoin que vous lui spécifiez un chemin vers ce répertoire, siot dans votre fichier project.rc (si vous en utilisez un) ou en utilisant le drapeau <strong><code>â??elements-dir</code></strong> (depuis la ligne de commande).</div>
-</li>
-<li class="level1"><div class="li"> Finalement, comme chaque nouveau schéma vous imposera de dessiner au moins une ou deux nouvelles empreintes, il serait bien dâ??avoir un répertoire dâ??«·empreintes·» local. Comme précédement, le nom dâ??empreinte à utiliser est le nom de fichier que vous assignez à chacune de vos nouvelles empreintes. Encore une fois, nâ??oubliez pas dâ??ajouter une ligne à votre fichier project.rc indiquant à gsch2pcb où trouver vos empreintes locales. Alternativement, vous pouvez lancer gsch2pcb avec le drapeau <strong><code>â??elements-dir</code></strong> pour pointer vers votre répertoire dâ??empreintes local.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Newlib" [5058-7532] -->
-<h3><a name="bibliotheque_m4" id="bibliotheque_m4">Bibliothèque M4</a></h3>
-<div class="level3">
-
-<p>
-La bibliothèque M4 stocke les empreintes comme des macros M4·; Il y a habituellement plusieurs (beaucoup) dâ??empreintes contenues dans chaque fichier dâ??empreinte. Les différentes empreintes dans un simple fichier sont généralement des variations dâ??un même motif (e.g. DIP-8, DIP-14, DIP-16, etc.). La manière la plus facile de trouver le nom dâ??attribut correct est de naviguer dans la bibliothèque «·pcblib·» par la fenêtre de bibliothèque de PCB. Les attributs dâ??empreinte sont données entre crochets dans la description. Vous pouvez aussi voir la liste des empreintes de pcblib sur la <a href="http://www.gedasymbols.org/footprints/"; class="urlextern" title="http://www.gedasymbols.org/footprints/"; rel="nofollow">page web des symboles gEDA</a>.
-</p>
-
-<p>
-Les bibliothèques m4 suivantes ont reçu plus dâ??attention et dâ??amélioration que les autres·:
-</p>
-<ul>
-<li class="level1"><div class="li"> ~amp pour les connecteurs Amp</div>
-</li>
-<li class="level1"><div class="li"> ~amphenol pour les connecteurs Amphenol</div>
-</li>
-<li class="level1"><div class="li"> ~geda pour plusieurs éléments utilisés dans les circuits basiques utilisés par gEDA (résistances, capacités, etc).</div>
-</li>
-<li class="level1"><div class="li"> ~bourns pour les produits comme des potentiomètres de Bourns</div>
-</li>
-<li class="level1"><div class="li"> ~cts pour les produits comme les réseaux de résistances de CTS</div>
-</li>
-<li class="level1"><div class="li"> ~johnstech pour les sockets Johnstech</div>
-</li>
-<li class="level1"><div class="li"> ~minicircuits pour les empreintes spécifiques Minicircuits</div>
-</li>
-<li class="level1"><div class="li"> ~panasonic pour quelques empreintes spécifiques Panasonic</div>
-</li>
-</ul>
-
-<p>
- Finalement, pour les bibliothèques newlib et M4, il est extrêmement important que vous vérifiez que les noms dâ??empreintes utilisées épelent *exactement* celui de lâ??empreinte que vous voulez placer dans PCB. Câ??es la raison pour laquelle il est critique dâ??inspecter lâ??empreinte avant de lâ??utiliser. Vous pouvez vérifier lâ??empreinte que vous voulez utiliser en cliquant dessus dans la «·bibliothèque dâ??empreinte·» puis le placer dans une zone vide de la zone de dessin de PCB. Inspectez manuellement lâ??empreinte pour vous assurer que le nombre correct de broches/pastilles, que les dimensions sont correctes, etc.
-</p>
-
-<p>
-Aussi, une fois que vous avez généré les fichiers Gerber, assurez-vous dâ??avoir <span class="curid"><a href="http://geda.seul.org/wiki/geda:pcb_tips.fr#j_ai_fini_mon_placement._comment_je_le_controle"; class="wikilink1" title="geda:pcb_tips.fr">inspecté toutes les empreintes instantiées dans vos Gerbers</a></span> en utilisant gerbv (ou un visualiseur Gerber équivalent) avant que vous nâ??envoyiez votre circuit à la fabrication.
-</p>
-
-</div>
-<!-- SECTION "Bibliothèque M4" [7533-9792] -->
-<h2><a name="quelle_est_la_maniere_recommandee_pour_traiter_les_differentes_empreintes_pour_le_meme_type_de_composant" id="quelle_est_la_maniere_recommandee_pour_traiter_les_differentes_empreintes_pour_le_meme_type_de_composant">Quelle est la manière recommandée pour traiter les différentes empreintes pour le même type de composant?</a></h2>
-<div class="level2">
-
-<p>
-Par exemple, un ampli op peut être DIP8 ou SO8. Une résistance peut être 0603, 0805, 1208 ou passante. Comment je sais quel boîtier et empreinte utiliser et comment je gère les choix?
-</p>
-
-<p>
-Dâ??abord, lâ??empreinte que vous devez utiliser est votre décision, pas celui de votre outil conception. Câ??est à vous de choisir votre boîtier préféré puis attacher lâ??attribut dâ??empreinte correct dans le composant du schéma. Une fois que vous avez choisi le boîtier (et lâ??empreinte), vous voudrez utiliser soit <span class="curid"><a href="http://geda.seul.org/wiki/geda:pcb_tips.fr#ou_puis-je_obtenir_des_empreintes_pre-dessinees_pour_pcb"; class="wikilink1" title="geda:pcb_tips.fr">trouver une empreinte appropriée</a></span> ou en <span class="curid"><a href="http://geda.seul.org/wiki/geda:pcb_tips.fr#comment_je_dessine_une_nouvelle_une_empreinte"; class="wikilink1" title="geda:pcb_tips.fr">dessiner une vous même</a></span> et la sauvegarder dans un répertoire local.
-</p>
-
-<p>
-Pour la gestion des choix dâ??empreintes (et donc le grand nombre dâ??attributs de composants que vous êtes susceptibles dâ??avoir): Utilisez <a href="http://geda.seul.org/wiki/geda:faq-attribs.fr#au_secours_mon_schema_a_des_centaines_de_composants_et_c_est_penible_d_utiliser_gschem_pour_attacher_tous_mes_attributs"; class="wikilink1" title="geda:faq-attribs.fr">gattrib</a>. Câ??est fait pour.
-</p>
-
-</div>
-<!-- SECTION "Quelle est la manière recommandée pour traiter les différentes empreintes pour le même type de composant?" [9793-10988] -->
-<h2><a name="comment_je_dessine_une_nouvelle_une_empreinte" id="comment_je_dessine_une_nouvelle_une_empreinte">Comment je dessine une nouvelle une empreinte?</a></h2>
-<div class="level2">
-
-<p>
-Tout le monde le fait à sa manière. Quelques personnes dessinent les empreintes en utilisant seulement PCB. Quelques personnes dessinent dâ??abord une empreinte préliminaire dans PCB et puis la terminent ensuite à la main et lâ??éditant (e.g. en utilisant emacs). Quelques personnes écrivent des scripts <acronym title="Practical Extraction and Report Language">Perl</acronym> pour générer automatiquement des empreintes.
-</p>
-
-<p>
-Karel Kulhavy préfère dessiner lâ??empreinte entièrement en utilisant PCB, qui peut être la manière la moins dangereuse à utiliser pour les nouveaux. Il maintient un <a href="http://ronja.twibright.com/guidelines/footprints.php"; class="urlextern" title="http://ronja.twibright.com/guidelines/footprints.php"; rel="nofollow">HOWTO de procédure de création d'empreintes</a> sur son site web Ronja.
-</p>
-
-<p>
-Si vous voulez éditer le fichier empreinte à la main, le <a href="http://www.brorson.com/gEDA/land_patterns_20050129.pdf"; class="urlextern" title="http://www.brorson.com/gEDA/land_patterns_20050129.pdf"; rel="nofollow">manuel sur la création d'empreintes</a> par Stephen Meier et Stuart Brorson fournissent les détails de la syntaxe. Le document donne aussi des conseils sur la manière de faire des conceptions élégantes qui sâ??appliquent aussi à lâ??interface graphique de la création dâ??empreintes.
-</p>
-
-</div>
-<!-- SECTION "Comment je dessine une nouvelle une empreinte?" [10989-12104] -->
-<h2><a name="comment_j_edite_change_une_empreinte_existante" id="comment_j_edite_change_une_empreinte_existante">Comment j'édite/change une empreinte existante?</a></h2>
-<div class="level2">
-
-<p>
-Vous pouvez convertir une empreinte de circuit, éditer les éléments et les reconvertir en empreinte. DAns la liste suivante, les éléments en polices mono space sont des actions depuis le menu buffer.
-</p>
-<ol>
-<li class="level1"><div class="li"> Selectionner lâ??élément</div>
-</li>
-<li class="level1"><div class="li"> Copier la sélection vers le tampon</div>
-</li>
-<li class="level1"><div class="li"> <code>Séparez le tampon en morceaux</code></div>
-</li>
-<li class="level1"><div class="li"> <code>Copiez le tampon dans le placement</code></div>
-</li>
-<li class="level1"><div class="li"> Effectuez les changement souhaités</div>
-</li>
-<li class="level1"><div class="li"> Sélectionnez tous les objets qui appartiennent aux empreintes</div>
-</li>
-<li class="level1"><div class="li"> <code>Copiez la sélection dans le tampon</code></div>
-</li>
-<li class="level1"><div class="li"> <code>Convertissez le tampon en élément</code></div>
-</li>
-<li class="level1"><div class="li"> <code>Copiez le tampon dans le placement</code></div>
-</li>
-<li class="level1"><div class="li"> Placez la souris sur les pastilles qui ont été arrondis pendant lâ??étape 4 et pressez q. Cela arrondit les bords des pastilles.</div>
-</li>
-<li class="level1"><div class="li"> Allez sur chaque pastille, pressez n et donnez un nom à la pastille</div>
-</li>
-<li class="level1"><div class="li"> Sélectionnez tout puis <code>copy selection to buffer</code></div>
-</li>
-<li class="level1"><div class="li"> <code>Save buffer as elements to file</code>. Le fichier empreinte sera créé à lâ??endroit dâ??où pcb a été appelé.</div>
-</li>
-</ol>
-
-<p>
-Alternativement, vous pouvez utiliser votre éditeur de texte favori et éditez le code source de lâ??empreinte.
-</p>
-
-</div>
-<!-- SECTION "Comment j'édite/change une empreinte existante?" [12105-13249] -->
-<h2><a name="comment_j_ajoute_une_bibliotheque_d_empreintes_a_pcb" id="comment_j_ajoute_une_bibliotheque_d_empreintes_a_pcb">Comment j'ajoute une bibliothèque d'empreintes à PCB?</a></h2>
-<div class="level2">
-
-<p>
-Lâ??ajoût dâ??une bibliothèque dâ??empreintes peut être réalisée depuis lâ??interface graphique:<br/>
- <strong><em>File</em></strong> â??> <strong><em>Preferences</em></strong> â??> <strong><em>Library</em></strong> â??> <strong>FOOTPRINTDIRECTORY</strong><br/>
- Alternativement, vous pouvez éditer le fichier <code>$HOME/.pcb/preferences</code>. Cherchez la ligne qui débute par «·library-newlib·». Nâ??oubliez pas dâ??inclure le nouveau répertorie dans votre fichier de ressource gsch2pcb (si vous utilisez gsch2pcb, bien sûr).
-</p>
-
-</div>
-<!-- SECTION "Comment j'ajoute une bibliothèque d'empreintes à PCB?" [13250-13768] -->
-<h2><a name="pcb_ne_trouve_par_mes_empreintes._pourquoi" id="pcb_ne_trouve_par_mes_empreintes._pourquoi">PCB ne trouve par mes empreintes. Pourquoi?</a></h2>
-<div class="level2">
-
-<p>
-Le chemin des empreintes utilisé par PCB est défini en utilisant la variable <strong><code>Pcb.elementPath</code></strong> dans le fichier des applications par défaut appelé <strong><code>PCB</code></strong>. Le chemin pour le fichier <strong><code>PCB</code></strong> est configuré en utilisant la variable dâ??environnement <strong><code>XAPPLRESDIR</code></strong> qui est typiquement fait avec un script nommé <strong><code>pcb</code></strong>.
-</p>
-
-</div>
-<!-- SECTION "PCB ne trouve par mes empreintes. Pourquoi?" [13769-14168] -->
-<h2><a name="maintenant_que_j_ai_toutes_ces_empreintes_ou_dois-je_les_placer" id="maintenant_que_j_ai_toutes_ces_empreintes_ou_dois-je_les_placer">Maintenant que j'ai toutes ces empreintes, où dois-je les placer?</a></h2>
-<div class="level2">
-
-<p>
-Je préfère placer toutes les empreintes «·prêtes pour la production·» dans un seul répertoire qui nâ??est pas dans lâ??arbre dâ??installation de gEDA/PCB. Lorsquâ??une nouvelle version de gEDA/PCB sort, je ne fais aucun changement aux fichier de projet ou aux bibliothèques. Sâ??il y a des empreintes newlib dans la bibliothèque PCB que je veux utiliser, je les copie dans le répertoire dâ??empreintes «·prêtes pour la production·».
-</p>
-
-<p>
-Plutôt que changer les fichiers de configuration permettant à gsch2pcb de trouver les empreintes, jâ??ai créé un script appelé <strong><code>sch2pcb</code></strong> qui contient le chemin des empreitnes. Tous les utilisateurs utilisent le même script et accèdent aux même empreintes de production.
-</p>
-
-<p>
-Pour utiliser le script <strong><code>sch2pcb</code></strong> qui est listé ci-dessus, remplacez la chaîne <strong><code>FOOTPRINT_DIR</code></strong> avec votre répertoire dâ??empreintes:
-</p>
-<pre class="code">
-#!/bin/bash
-gsch2pcb --elements-dir FOOTPRINT_DIR $@
-</pre>
-
-<p>
-Ou une autre version utilisateur:
-</p>
-<pre class="code">
-#!/bin/bash
-#this script was written by John Luciani
-gsch2pcb --elements-dir /home/user/pcb/footprints/user --use-files $@
-</pre>
-
-</div>
-<!-- SECTION "Maintenant que j'ai toutes ces empreintes, où dois-je les placer?" [14169-15356] -->
-<h1><a name="placement_de_composants" id="placement_de_composants">Placement de composants</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "Placement de composants" [15357-15395] -->
-<h2><a name="comment_je_pivote_une_selection_i.e._pour_plus_d_un_element" id="comment_je_pivote_une_selection_i.e._pour_plus_d_un_element">Comment je pivote une sélection (i.e. pour plus d'un élément)?</a></h2>
-<div class="level2">
-<ol>
-<li class="level1"><div class="li"> Sélectionnez les éléments</div>
-</li>
-<li class="level1"><div class="li"> Buffer â?? Coupez la sélection vers le tampon</div>
-</li>
-<li class="level1"><div class="li"> Buffer â?? Pivotez le tampon de 90 deg CCW (ou CW)</div>
-</li>
-<li class="level1"><div class="li"> Clickez partout sur la carte et la sélection est à nouveau collée sur le circuit.</div>
-</li>
-</ol>
-
-</div>
-<!-- SECTION "Comment je pivote une sélection (i.e. pour plus d'un élément)?" [15396-15702] -->
-<h2><a name="comment_je_change_la_taille_de_l_objet_graphique_comme_du_texte_des_lignes_de_masque_texte_etc" id="comment_je_change_la_taille_de_l_objet_graphique_comme_du_texte_des_lignes_de_masque_texte_etc">Comment je change la taille de l'objet graphique (comme du texte, des lignes de masque texte, etc)?</a></h2>
-<div class="level2">
-<ul>
-<li class="level1"><div class="li"> La souris sur lâ??objet et frappez [<strong><code>s</code></strong>]. Cela augmentera la taille de lâ??objet sur lequel est la souris.</div>
-</li>
-<li class="level1"><div class="li"> La souris sur lâ??objet et grappez [<strong><code><shift>-S</code></strong>]. Cela diminuera la taille de lâ??objet sur lequel est la souris.</div>
-</li>
-</ul>
-
-<p>
- Vous pouvez modifier la valeur dâ??augmentation/diminution en utilisant le menu <strong><em>file</em></strong> â?? <strong><em>preferences</em></strong> â?? <strong><em>increments</em></strong>.
-</p>
-
-</div>
-<!-- SECTION "Comment je change la taille de l'objet graphique (comme du texte, des lignes de masque texte, etc)?" [15703-16188] -->
-<h2><a name="comment_placer_les_composants_sur_les_deux_faces_de_pcb" id="comment_placer_les_composants_sur_les_deux_faces_de_pcb">Comment placer les composants sur les deux faces de PCB?</a></h2>
-<div class="level2">
-
-<p>
-Il y a deux manières de le faire:
-</p>
-<ul>
-<li class="level1"><div class="li"> Presser la touche de tabulation alternera le côté actif entre le côté composants et et soudure. Lorsque vous placez des composants, il iront sur le côté actif.</div>
-</li>
-<li class="level1"><div class="li"> Si vous visualisez un côté de la carte, placez y un composant et (avec le pointeur dessus), pressez la touche [<strong><code>b</code></strong>] (ce qui signifie, envoyer le composant de lâ??autre côté), le composant va vers lâ??autre côté de la carte.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Comment placer les composants sur les deux faces de PCB?" [16189-16699] -->
-<h2><a name="comment_je_place_l_origine_dans_pcb" id="comment_je_place_l_origine_dans_pcb">Comment je place l'origine dans pcb?</a></h2>
-<div class="level2">
-
-<p>
-Lâ??origine absolue est toujours dans le coin haut gauche de la zone accessible. Ceci ne peut être configuré ailleurs. Néanmoins, les coordonnées des objets peuvent aussi être donnés en relation de la grile courante. Dans la version GTK2 de pcb, les coordonnées sont montrées dans le coin haut droit de la fenêtre principale. La bonne valeur est la position absolue, alors que la valeur de gauche reflète la position relative dâ??un marqueur arbitraire. Ce marqueur est configuré à la position courante de la souris par la séquence de touche [<strong><code>ctrl-m</code></strong>]. Vous pouvez vouloir configurer le marqueur sur un point de grille ou de broche spécifique.
-</p>
-
-</div>
-<!-- SECTION "Comment je place l'origine dans pcb?" [16700-17410] -->
-<h2><a name="comment_je_mesure_les_distances_et_les_dimensions_des_composants" id="comment_je_mesure_les_distances_et_les_dimensions_des_composants">Comment je mesure les distances et les dimensions des composants?</a></h2>
-<div class="level2">
-
-<p>
-Utilisez [<strong><code>ctrl-m</code></strong>] pour configurer lâ??origine et lisez la distance de ce point par rapport au pointeur de souris sur le bord haut gauche de la fenêtre de pcb. Quelques objets comme les vias et les pistes donnent des informations utiles dans les rapports dâ??objets. Accédez au rapport de lâ??objet sous le pointeur de souris avec [<strong><code>ctrl-r</code></strong>].
-</p>
-
-</div>
-<!-- SECTION "Comment je mesure les distances et les dimensions des composants?" [17411-17841] -->
-<h1><a name="routage" id="routage">Routage</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "Routage" [17842-17863] -->
-<h2><a name="comment_router_une_connexion_depuis_le_cote_soudure_vers_le_cote_composant_et_inversement" id="comment_router_une_connexion_depuis_le_cote_soudure_vers_le_cote_composant_et_inversement">Comment router une connexion depuis le côté soudure vers le côté composant et inversement?</a></h2>
-<div class="level2">
-
-<p>
-Lors de lâ??utilistion de lâ??outil line tool, utilisez les touches de chiffres en haut du clavier pour changer de couche. Un via sera placé automatiquement à la fin du dernier segment complet.
-</p>
-
-</div>
-<!-- SECTION "Comment router une connexion depuis le côté soudure vers le côté composant et inversement?" [17864-18163] -->
-<h2><a name="comment_je_change_le_style_de_routage" id="comment_je_change_le_style_de_routage">Comment je change le style de routage?</a></h2>
-<div class="level2">
-
-<p>
-Il existe un jeu de tailles de routage prédéfinies. Le jeu porte des noms suggestifs (Signal, Power, Fat et Skinny). Touchez le bouton «·Route Style·» pour configurer les tailles du jeu courant à vos besoins. Lâ??outil line connaît différents modes pour traiter les connexions transversales. La status line sur le bas de la page indique quel mode est en cours:
-</p>
-<ol>
-<li class="level1"><div class="li"> 45° plus vertical/horizontal (status line: â??\_â??)</div>
-</li>
-<li class="level1"><div class="li"> vertical plus 45° (status line: â??_/â??)</div>
-</li>
-<li class="level1"><div class="li"> either vertical or 45° (status line: â??45â??)</div>
-</li>
-<li class="level1"><div class="li"> arbitrary angle (status line: â??allâ??)</div>
-</li>
-</ol>
-
-<p>
-La manière dâ??accéder à ces modes diffère en fonction des version de lâ??interface. La version GTK courante (v20060288) a par défaut â??_/â?? mais peut être modifiée temporairement en â??\_â?? avec la touche shift. Vous pouvez passer au mode 45° avec la touche slash â??/â??. Pour les angles arbitraires, pressez la touche point «·.·» ou choisissez «·enable all line directions·» dans le setting menu.
-</p>
-
-</div>
-<!-- SECTION "Comment je change le style de routage?" [18164-19200] -->
-<h2><a name="j_ai_merde_comment_je_reviens_en_arriere" id="j_ai_merde_comment_je_reviens_en_arriere">J'ai merdé! Comment je reviens en arrière?</a></h2>
-<div class="level2">
-
-<p>
-La touche universelle undo [<strong><code>U</code></strong>] fonctionne même en pleine action de placement de piste. IIl enlèvera le dernier segment mais gardera lâ??outil line attaché à la souris. Vous pouvez donc immediatement aller sur le routage et trouver un meilleur placement.
-</p>
-
-</div>
-<!-- SECTION "J'ai merdé! Comment je reviens en arrière?" [19201-19522] -->
-<h2><a name="comment_je_deplace_un_jeu_de_piste_d_une_couche_a_l_autre" id="comment_je_deplace_un_jeu_de_piste_d_une_couche_a_l_autre">Comment je déplace un jeu de piste d'une couche à l'autre?</a></h2>
-<div class="level2">
-<ol>
-<li class="level1"><div class="li"> Sélectionnez les pistes. Câ??est plus facile à faire sur vous fermez dâ??abord tout le reste sur cette couche (i.e. silk, broches, autres couches, etc).</div>
-</li>
-<li class="level1"><div class="li"> Configurez la nouvelle couche de réception. Oui, la nouvelle couche doit être affichée·; ce qui nâ??est pas un problème si vous avez déjà sélectionné les pistes à déplacer.</div>
-</li>
-<li class="level1"><div class="li"> Pressez [<strong><code>shift-M</code></strong>] pour déplacer toutes les pistes sélectionnées vers la couche courante.</div>
-</li>
-</ol>
-
-</div>
-<!-- SECTION "Comment je déplace un jeu de piste d'une couche à l'autre?" [19523-20041] -->
-<h2><a name="comment_je_change_les_soldermask_clearance_autour_d_un_trou_via" id="comment_je_change_les_soldermask_clearance_autour_d_un_trou_via">Comment je change les soldermask clearance autour d'un trou/via?</a></h2>
-<div class="level2">
-
-<p>
-Vous pouvez augmenter la soldermask clearance depuis tout trou/via en positionnant le curseur sur lâ??objet et tapez la touche [<strong><code>k</code></strong>]. Vous pouvez diminuer la clearance en utilisant la touche [<strong><code><shift>-K</code></strong>].
-</p>
-
-</div>
-<!-- SECTION "Comment je change les soldermask clearance autour d'un trou/via?" [20042-20335] -->
-<h2><a name="comment_changer_la_taille_des_pistes" id="comment_changer_la_taille_des_pistes">Comment changer la taille des pistes?</a></h2>
-<div class="level2">
-
-<p>
-Il existe plusieurs manières de changer la taille de piste déjà placées:
-</p>
-<ol>
-<li class="level1"><div class="li"> Utilisez [<strong><code>s</code></strong>] et [<strong><code>shift-s</code></strong>] pour augmenter ou diminuer la taille de la piste sous le curseur de la souris.</div>
-</li>
-<li class="level1"><div class="li"> choisissez <strong><code>Select/Change_size_of_selected_objects/Decrement_lines_by_4mil</code></strong> depuis le menu <strong><code>Select</code></strong>. La valeur de changement peut être configurée dans <strong><code>File/Preferences/Sizes</code></strong>. Cela nâ??agit que sur les pistes. Donc la sélection peut contenir des composants, des textes, vias et ainsi de suite.</div>
-</li>
-<li class="level1"><div class="li"> Sélectionnez les pistes devant être changées et tapez <strong><code>:ChangeSize(SelectedLines,+4,mils)</code></strong>. La virgule vous offre la ligne de commande et <strong><code>ChangeSize()</code></strong> est la version commandée de lâ??action précédemment décrite. Remplacez â??<strong><code>+4</code></strong>â?? par la valeur à laquelle vous voulez augmenter la taille de la piste. Utilisez le signe moins pour diminuer la taille de la piste. Si vous omettez le signe, la commande configure la taille de la piste à la valeur donnée.</div>
-</li>
-</ol>
-
-</div>
-<!-- SECTION "Comment changer la taille des pistes?" [20336-21393] -->
-<h2><a name="comment_je_pilote_un_via_pour_connecter_une_piste_a_un_plan_de_masse_sur_une_couche_differente" id="comment_je_pilote_un_via_pour_connecter_une_piste_a_un_plan_de_masse_sur_une_couche_differente">Comment je pilote un via pour connecter une piste à un plan de masse sur une couche différente?</a></h2>
-<div class="level2">
-<ol>
-<li class="level1"><div class="li"> Configurez la couche de plan de masse comme la couche active.</div>
-</li>
-<li class="level1"><div class="li"> Sélectionnez lâ??outil «·via·».</div>
-</li>
-<li class="level1"><div class="li"> Placez le via où vous voulez quâ??il aille (clic gauche pour le placer).</div>
-</li>
-<li class="level1"><div class="li"> Sélectionnez maintenant lâ??outil «·thermal·».</div>
-</li>
-<li class="level1"><div class="li"> Clic gauche sur le via que vous venez juste de placer.</div>
-</li>
-<li class="level1"><div class="li"> Changer maintenant la couche active en celle de la couche de routage souhaitée.</div>
-</li>
-<li class="level1"><div class="li"> Sélectionnez lâ??outil «·line·».</div>
-</li>
-<li class="level1"><div class="li"> Routez la piste sur la couche active vers ou depuis le via comme dâ??habitude.</div>
-</li>
-</ol>
-
-</div>
-<!-- SECTION "Comment je pilote un via pour connecter une piste à un plan de masse sur une couche différente?" [21394-22004] -->
-<h2><a name="je_veux_dessiner_une_piste_entre_deux_segments_sur_le_meme_net_mais_pcb_ne_me_laisse_pas_faire_pourquoi" id="je_veux_dessiner_une_piste_entre_deux_segments_sur_le_meme_net_mais_pcb_ne_me_laisse_pas_faire_pourquoi">Je veux dessiner une piste entre deux segments sur le même net mais PCB ne me laisse pas faire! Pourquoi?</a></h2>
-<div class="level2">
-
-<p>
-Vous pouvez dessiner des pistes avec auto-DRC Ã on. Pour connecter les deux segments, vous avez ici quelques suggestions:
-</p>
-<ul>
-<li class="level1"><div class="li"> DRC enforcement utilise le ratsnest pour déterminer où les pistes sont permises. Donc, vous devez avoir des ratsnest dessinés de manière à réaliser des connexions dans le mode auto-DRC. Sinon, vous ne serez pas authorisés) à connecter (ou approcher) toute zone de cuivre qui nâ??est pas connectée à notre net. (Si la visibilité du rat vous embête, vous pouvez cacher les couches de rat â?? mais les rats doivent exister).</div>
-</li>
-<li class="level1"><div class="li"> Vous devrez aussi rafraîchir les rats régulièrement lors du dessin. Tapez [<strong><code>o</code></strong>] pour redessiner/re-optimiser les rats. Assurez-vous quâ??un rat connecte visiblement deux pièces de métal que vous souhaitez réunir.</div>
-</li>
-<li class="level1"><div class="li"> Il est aussi possible que vous expérimentiez cette situation lors du dessin de pistes entre les broches dâ??un connecteur. Dans ce cas, il est possible que la largeur de piste viole les règles de clearance du champ de broche. Tentez de diminuer la clearance broche-vers-métal ou utilisez une épaisseur de piste plus étroite.</div>
-</li>
-<li class="level1"><div class="li"> Quelques fois, ce comportement de blocage du routage peut provenir dâ??une erreur dans votre netlist. Ne terminez pas les refdes avec des minuscules - elles sont réservées pour els portes à lâ??intérieur des composants. Finissez avec un majuscule ou un chiffre·; les minuscules sont simplement ignorées.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Je veux dessiner une piste entre deux segments sur le même net mais PCB ne me laisse pas faire! Pourquoi?" [22005-23552] -->
-<h2><a name="pcb_semble_manger_mes_noms_de_composants_et_se_plaint_qu_il_ne_peut_pas_trouver_des_nets_adaptes_aux_broches_de_quoi_cela_vient" id="pcb_semble_manger_mes_noms_de_composants_et_se_plaint_qu_il_ne_peut_pas_trouver_des_nets_adaptes_aux_broches_de_quoi_cela_vient">PCB semble manger mes noms de composants et se plaint qu'il ne peut pas trouver des nets adaptés aux broches! De quoi cela vient?</a></h2>
-<div class="level2">
-
-<p>
-Plus raisonnablement, vous les nommez de telle manière que pcb croie quâ??ils ne forment quâ??un élément. Les minuscules à la fin dâ??un refdes sont ignorés. Donc, les composants U2foo et U2bar ressemblent tous les deux à U2 pour pcb. Lors de la construction des rat nests, pcb cherchera des nets pour U2 qui, bien sûr, nâ??existe pas. Les minuscules sont destinées pour différentier les slots dâ??un multi-composant. E.g., les quatres symboles opamp dâ??un amplificateur opérationnel quadruple.<br/>
- Ligne de fin: Nâ??utilisez pas les minuscules à la fin dâ??un refdes, à moins que vous ne sachiez ce que vous faites.
-</p>
-
-</div>
-<!-- SECTION "PCB semble manger mes noms de composants et se plaint qu'il ne peut pas trouver des nets adaptés aux broches! De quoi cela vient?" [23553-24310] -->
-<h2><a name="comment_je_peux_configurer_la_couleur_et_l_epaisseur_des_rats_nests" id="comment_je_peux_configurer_la_couleur_et_l_epaisseur_des_rats_nests">Comment je peux configurer la couleur et l'épaisseur des rats nests?</a></h2>
-<div class="level2">
-
-<p>
-Vous pouvez configurer la couleur des rats dans <code>File - Preference - Colors - Main colors</code>
-</p>
-
-<p>
-Il nâ??existe actuellement pas dâ??interface graphique pour changer les épaisseurs de rat mais vous pouvez éditer votre fichier <code>$HOME/.pcb/preference</code> manuellement. Fermez toutes les instances de pcb et cherchez la ligne qui débute avec <code>rat-thickness</code>.
-</p>
-
-</div>
-<!-- SECTION "Comment je peux configurer la couleur et l'épaisseur des rats nests?" [24311-24748] -->
-<h1><a name="au_dela_des_pistes_et_des_empreintes" id="au_dela_des_pistes_et_des_empreintes">Au delà des pistes et des empreintes</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "Au delà des pistes et des empreintes" [24749-24801] -->
-<h2><a name="comment_je_trace_un_dessin_une_impression_ou_un_autre_pcb" id="comment_je_trace_un_dessin_une_impression_ou_un_autre_pcb">Comment je trace un dessin, une impression ou un autre PCB?</a></h2>
-<div class="level2">
-
-<p>
-Voyez la page <a href="http://www.delorie.com/pcb/bg-image.html"; class="urlextern" title="http://www.delorie.com/pcb/bg-image.html"; rel="nofollow">http://www.delorie.com/pcb/bg-image.html</a> sur le site web PCB HID de DJ Delorie.
-</p>
-
-<p>
-Câ??est un bonne manière pour tracer des images à la main ou un autre PCB, disons un de ceux que vous en avez un au format propriétaire, que vous voudriez «·déverrouiller·» maintenant. De plus, vous pouvez utiliser des images comme outils pour faire des révisions de cartes ou des reconceptions.
-</p>
-
-<p>
-Si vous nâ??aimez pas utiliser PCB confiné à la zone de la carte, i.e. si vous voulez des marges autour de la carte, alors ajoutez-les dans GIMP. Jâ??aime faire des marges de 1.00000 autour de la carte. Lorsque vous configurez votre taille de PCB, vous voudrez ajouter votre zone de marge. CTRL-M vous aidera à vérifier la taille. Aussi, le temps de corriger les distorsions de votre scanner ou depuis votre dessin est à faire avant de le charger, dans GIMP ou un des équivalent.
-</p>
-
-</div>
-<!-- SECTION "Comment je trace un dessin, une impression ou un autre PCB?" [24802-25761] -->
-<h2><a name="je_ne_peux_pas_copier_des_pastilles_dans_un_circuit._comment_je_fais" id="je_ne_peux_pas_copier_des_pastilles_dans_un_circuit._comment_je_fais">Je ne peux pas copier des pastilles dans un circuit. Comment je fais?</a></h2>
-<div class="level2">
-
-<p>
-<strong>Question:</strong> Je veux copier une section de mon placement en un autre endroit.
-</p>
-
-<p>
-Je peux sélectionner une zone existante. Tout semble virer au au bleu.
-</p>
-
-<p>
-â??Bufferâ??–>â??Copy Selection To Bufferâ?? semble réussir (pas de complaintes).
-</p>
-
-<p>
-Lorsque je veux copier la zone copiée… et tout ce que jâ??arrive à bouger sont un couple de pistes et quelques vias. Les pastilles qu jâ??ai créé avec difficulté ne sont pas copiées. Pourquoi!?!?!?
-</p>
-
-<p>
-<strong>Réponse:</strong> Si la couche du dessus (silk layer) est désactivée, vous ne pouvez copier les éléments par le tampon copier. Bizarre, mais câ??est comme cela que cela fonctionne. Donc, validez la couche du dessus avant de copier une section de placement.
-</p>
-
-</div>
-<!-- SECTION "Je ne peux pas copier des pastilles dans un circuit. Comment je fais?" [25762-26535] -->
-<h2><a name="comment_je_remplis_les_zones_avec_cuivre" id="comment_je_remplis_les_zones_avec_cuivre">Comment je remplis les zones avec cuivre?</a></h2>
-<div class="level2">
-
-<p>
-Utilisez les plans rectangle et polygone. Ces objets éviteront toujours les vias, pastilles et broches. Les pistes sont aussi évitées, si elles ont le drapeau clear polygons de configuré. (menu: Settings/Enable_new_lines_clear_polygons)
-</p>
-
-</div>
-<!-- SECTION "Comment je remplis les zones avec cuivre?" [26536-26831] -->
-<h2><a name="les_polygones_mettent_mes_pistes_a_la_masse_que_puis-je_y_faire" id="les_polygones_mettent_mes_pistes_a_la_masse_que_puis-je_y_faire">Les polygones mettent mes pistes à la masse! Que puis-je y faire?</a></h2>
-<div class="level2">
-
-<p>
-Vous nâ??avez pas contrôlé le «·Enable_new_lines_clear_polygons·» dans le menu settings lorsque vous avez placé les pistes. Entrez «·changejoin(selection)·» dans la fenêtre de commande pour basculer ce drapeau pour toutes les pistes qui sont actuellement sélectionnées. Le raccourci clavier pour cette action est [<strong><code>shift-j</code></strong>].
-</p>
-
-</div>
-<!-- SECTION "Les polygones mettent mes pistes à la masse! Que puis-je y faire?" [26832-27255] -->
-<h2><a name="comment_je_change_le_polygon_clearance" id="comment_je_change_le_polygon_clearance">Comment je change le polygon clearance?</a></h2>
-<div class="level2">
-
-<p>
-Pressez [<strong><code>k</code></strong>] pour augmenter la clearence de lâ??objet sous le curseur. Utilisez [<strong><code>ctrl-k</code></strong>] pour augmenter la clearence des objets sélectionnés. Ajoutez le modificateur [<strong><code>shift</code></strong>] pour diminuer la clearence. Pour changer une piste complète, pressez [<strong><code>f</code></strong>] pour trouver tous les segments qui sont connectés à lâ??objet sous le curseur et appliquez lâ??action «·select(connection)·».
-</p>
-
-<p>
-La valeur de lâ??incrément peut être configurée dans le dialogue File/Preference/Increments.
-</p>
-
-</div>
-<!-- SECTION "Comment je change le polygon clearance?" [27256-27810] -->
-<h2><a name="comment_je_cache_les_polygones_lorsque_j_edite_le_placement" id="comment_je_cache_les_polygones_lorsque_j_edite_le_placement">Comment je cache les polygones lorsque j'édite le placement?</a></h2>
-<div class="level2">
-
-<p>
-Placez les polygones (et les rectangles) sur une couce séparée. Utilisez la préférence pour vous assurer que cette couche nâ??est pas dans le même groupe que les pistes. Désactivez la piste en clickant sur le bouton de couche correspondant dans la fenêtre principale. Après que vous ayiez terminé avec les changements, utilisez le dialogue preference pour permettre à la couche des polygones de joindre la couche des pistes.
-</p>
-
-</div>
-<!-- SECTION "Comment je cache les polygones lorsque j'édite le placement?" [27811-28318] -->
-<h2><a name="comment_editer_les_polygones" id="comment_editer_les_polygones">Comment éditer les polygones?</a></h2>
-<div class="level2">
-
-<p>
-Il y a quatre manières de base pour éditer les contours des polygones. Vous pouvez déplacer et effacer les verticales et vous pouvez insérer les verticales en utilisant deux techniques. Les polygones peuvent être éditées de manière équivalente dans le mode «·thin line draw·» (settings â??> enable thin line draw) ou dans le mode normal. Déplacer un sommet est facilement accompli en utilisant un-selecting your polygon puis en cliquant et tirant ce sommet dans le nouvel emplacement. Pour effacer un sommet, un coin de votre polygone, placez votre pointeur sur le point et tapez «·delete·» avec le clavier. Pour insérer un sommet, vous devez utiliser lâ??outil insert (â??insertâ?? keystroke). Démarrez en cliquant sur le bord que vous voulez séparer avec un nouveau point. Cliquez et tirez le nouveau point dans le polygone. Une variation de cette technique est 1) cliquer pour sélectionner, suivi par 2) cliquer pour placer le nouveau sommet.
-</p>
-
-<p>
-(NOTE: Insérer des points dans un polygone ne fonctionnera généralement QUE avec «·all direction lines·» de validé («·settings â??> enable all direction lines·»). Câ??est parce PCB possède un système de contrainte de 45/90 degrés puissante. Si vous tentez dâ??insérer des nouveaux sommets, dans un polygone, qui ne tombent pas sur des lignes à contraintes de 45 et 90 degrés, PCB ne permet pas cette action!)
-</p>
-
-</div>
-<!-- SECTION "Comment éditer les polygones?" [28319-29752] -->
-<h2><a name="comment_je_place_des_vias_qui_connectent_un_polygone_pour_une_dissipation_thermique_complete_ou_pour_une_integrite_de_protection_complete" id="comment_je_place_des_vias_qui_connectent_un_polygone_pour_une_dissipation_thermique_complete_ou_pour_une_integrite_de_protection_complete">Comment je place des vias qui connectent un polygone pour une dissipation thermique complète ou pour une intégrité de protection complète?</a></h2>
-<div class="level2">
-
-<p>
-Il est souvent utile dâ??avoir des vias connectés complètement à un polygone (une zone de cuivre) pour les transferts de chaleur â?? le problème apparent est que les polygones de PCB ont un seul drapeau «·clear pins/vias·» pour le polygone complet (basculé avec la touche [<strong><code>s</code></strong>]). Notre objectif est de seulement connecter quelques uns des broches/vias au polygone mais pour mieux les connecter que ne le font un des connexions thermiques. Vous avez ici quelques manières de le faire·:
-</p>
-
-<p>
-Une manière est de faire un objet qui est presque comme une connexion thermique en ce sens quelle est entre le via et le polygone â?? la différence est que vous créez réellement un anneau pour remplir complètement lâ??espace entre le trou et le polygone (qui, à cause de sa clearance validée, nâ??est pas connecté à la broche). Cet anneau est un arc à quatre segments. Vous pouvez copier ces quatre objets dans le tampon pour créer un «·zero-clearance thermal tool·». Le contre-coup de cette astuce est que lorsque vous changez la taille de via, vous aurez aussi à modifier la taille de ces éléments de remplissage.
-</p>
-
-<p>
-Les arcs vous permettront dâ??utiliser cette astuce de remplissage dans les zones étroites en ne plaçant que deux des quatre arcs.
-</p>
-
-<p>
-Une autre astuce est de réaliser une ligne sans longueur. Prenez un seul segment de ligne et déplacez le point de fin au point de début. Vous avez maintenant une «·ligne à un seul point·» (un cercle) avec le diamètre égal à lâ??épaisseur de la ligne. Faites autant de couches (touche [<strong><code>m</code></strong>]) que vous jugez nécessaire. Placez cet objet centré sur votre via pour le connecter à un polygone.
-</p>
-
-<p>
-Les utilisateurs intensifs peuvent vouloir garder une petite bibliothèque personnalisée des ces éléments en les sauvegardant comme des éléments. Il est aussi pratique de placer des «·éléments·» dans un de vos tampons PCB de telle manière quâ??ils soient à portée de main.
-</p>
-
-<p>
-Vous pouvez aussi ajouter un autre polygone par dessus le polygone sur lequel vous connecter vos vias. Vous devez désactiver le drapeau «·clear pins/vias·» et les vias seront connectés au polygon le plus grand en dessous.
-</p>
-
-</div>
-<!-- SECTION "Comment je place des vias qui connectent un polygone pour une dissipation thermique complète ou pour une intégrité de protection complète?" [29753-32096] -->
-<h2><a name="les_polygones_peuvent-ils_etre_un-masques_un_polygone_peut-il_etre_de_cuivre_sans_masque_de_soudure" id="les_polygones_peuvent-ils_etre_un-masques_un_polygone_peut-il_etre_de_cuivre_sans_masque_de_soudure">Les polygones peuvent-ils être un-masqués? (Un polygone peut-il être de cuivre sans masque de soudure?)</a></h2>
-<div class="level2">
-
-<p>
-Ce nâ??est actuellement pas possible dans PCB. La manière habituelle (par exemple si vous voulez quâ??une zone nue sâ??attache à une zone de dissipation ou un shielding) est de réaliser un élément qui est une pastille simple. Cette pastille doit être aussi petite que possible (0 x 0) mais avec une grand clearance. Câ??est la clearance du masque de soudure de cet élément que vous allez utiliser pour dé-masquer le polygone. PCB limite en interne la taille de la pastille à 250 mils. Pour les zones plus grandes, vous aurez besoin dâ??utiliser plusieurs pastilles.
-</p>
-
-</div>
-<!-- SECTION "Les polygones peuvent-ils être un-masqués? (Un polygone peut-il être de cuivre sans masque de soudure?)" [32097-32782] -->
-<h2><a name="comment_je_place_des_trous_de_montage_mounting_hole" id="comment_je_place_des_trous_de_montage_mounting_hole">Comment je place des trous de montage (mounting hole)?</a></h2>
-<div class="level2">
-
-<p>
-Utilisez une empreinte pour les pour trou de montage ou placez un via.
-</p>
-
-<p>
-Si la pastille entourant le trou de montage doit être conneté électriquement, alors vous devez montrer la connexion dans votre schéma. Ajoutez un symbole pour le pour le trou de montage et changez son attribut dâ??empreinte.
-</p>
-
-<p>
-Ma préférence est de créer des empreintes PCB pour les divers types dâ??éléments à monter. Jâ??ai une variété de silkscreens pour diverses combinaisons de de matériel (hex nut, hex nut with washer, etc.). Le silkscreen fournit une référence de placement pendant le placement avec PCB.
-</p>
-
-<p>
-Pour les exemples dâ??empreintes, voyez <a href="http://www.luciani.org/geda/pcb/pcb-footprint-list.html#Hardware"; class="urlextern" title="http://www.luciani.org/geda/pcb/pcb-footprint-list.html#Hardware"; rel="nofollow">http://www.luciani.org/geda/pcb/pcb-footprint-list.html#Hardware</a>.
-</p>
-
-</div>
-<!-- SECTION "Comment je place des trous de montage (mounting hole)?" [32783-33551] -->
-<h2><a name="pourquoi_est-il_possible_de_realiser_des_ponts_thermiques_pour_les_broches_mais_pas_pour_une_pastille" id="pourquoi_est-il_possible_de_realiser_des_ponts_thermiques_pour_les_broches_mais_pas_pour_une_pastille">Pourquoi est-il possible de réaliser des ponts thermiques pour les broches mais pas pour une pastille?</a></h2>
-<div class="level2">
-
-<p>
-La raison est que les broches ont habituellement suffisamment dâ??espace avec le plan les entourant qui reste intact sur toutes les faces et ce nâ??est pas le cas des pastilles qui sont habituellement trop serrées. Ã? cause de ceci, vous devez dessiner manuellement les «·doigts·» de liaison thermique pour connecter la pastille au plan de masse. Assurez-vous que vous avez configuré la connexion de telles nouvelles lignes aux plans lorsque vous les dessinez. Si vous avez besoin de faire plusieurs de ces ponts thermiques, passez un peu de temps à faire le premier de la manière dont vous souhaitez puis copiez les doigts dans le tampon et collez-le si vous voulez les autres.
-</p>
-
-</div>
-<!-- SECTION "Pourquoi est-il possible de réaliser des ponts thermiques pour les broches mais pas pour une pastille?" [33552-34351] -->
-<h2><a name="pcb_peut-il_etre_utilise_pour_realiser_des_cartes_a_simple_couche" id="pcb_peut-il_etre_utilise_pour_realiser_des_cartes_a_simple_couche">PCB peut-il être utilisé pour réaliser des cartes à simple couche?</a></h2>
-<div class="level2">
-
-<p>
-Oui. Tracez vos gerbers et et enlevez toutes les couches qui ne sont pas nécessaires. Vous pouvez juste dessiner le placement comme vous le souhaitez (style libre). Si vous voulez vérifier la connectivité, vous avez deux choix:
-</p>
-<ol>
-<li class="level1"><div class="li"> Supposer que votre cuivre est sur le côté oppposé, utilisez le côté supérieur du placement pour y placer les pistes où seront les jumpers. Câ??est probablement le plus facile. Puis, traitez le côté opposé et placez les jumpers où vous avez le côté supérieur du cuivre.</div>
-</li>
-<li class="level1"><div class="li"> Créez un symbole «·jumper·» dans le schéma et placez-le dans les endroits où vous avez besoin dâ??un jumper. Cela peut être pénible mais vous pouvez forcer les dimensions des jumpers de cette manière si vous en avez besoin.</div>
-</li>
-</ol>
-
-<p>
- Si vous tentez dâ??utliser lâ??autorouter, désactivez toutes les couches arrière lorsque vous routez et il collera à cette couche.
-</p>
-
-</div>
-<!-- SECTION "PCB peut-il être utilisé pour réaliser des cartes à simple couche?" [34352-35318] -->
-<h2><a name="quelles_ressources_existent_pour_traiter_les_fichiers_pcb_en_utilisant_les_scripts" id="quelles_ressources_existent_pour_traiter_les_fichiers_pcb_en_utilisant_les_scripts">Quelles ressources existent pour traiter les fichiers PCB en utilisant les scripts?</a></h2>
-<div class="level2">
-
-<p>
-Une des plus grande fonctionnalité de PCB est quâ??il utilise un format de fichier <acronym title="American Standard Code for Information Interchange">ASCII</acronym> facilement compréhensible. Câ??est la raison pour laquelle de nombreues personnes utilisent les scripts (habituellement <acronym title="Practical Extraction and Report Language">Perl</acronym>) pour traiter leurs cartes de différentes manières. Vous pouvez utiliser ces scripts soit comme ils sont, soit en les modifiant pour les adapter à nos propres buts. Vous avez ici quelques liens vers les scripts disponibles:
-</p>
-<ol>
-<li class="level1"><div class="li"> John Luciani possède une large éventail de <a href="http://www.luciani.org/geda/pcb/pcb-perl-library.html"; class="urlextern" title="http://www.luciani.org/geda/pcb/pcb-perl-library.html"; rel="nofollow">scripts</a> disponible sur <a href="http://www.luciani.org/"; class="urlextern" title="http://www.luciani.org"; rel="nofollow"> son site web</a>. Dans cette collection, des scripts sont inclus pour générer des empreintes, de même que </div>
-</li>
-<li class="level1"><div class="li"> David Rowe possède des scripts pour mettre à jour des éléments de même quâ??ajouter/suprimer des fichiers PCB les uns des autres sur <a href="http://www.rowetel.com/perl4pcb.html"; class="urlextern" title="http://www.rowetel.com/perl4pcb.html"; rel="nofollow">son site web</a>.</div>
-</li>
-<li class="level1"><div class="li"> Stuart Brorson a écrit un script simple qui génère des empreintes pour deux ponts thermiques passifs en SMD. Un tarball gzippé est disponible <a href="http://www.brorson.com/gEDA/Smtgen.pl.gz"; class="urlextern" title="http://www.brorson.com/gEDA/Smtgen.pl.gz"; rel="nofollow"> ici </a>.</div>
-</li>
-</ol>
-
-</div>
-<!-- SECTION "Quelles ressources existent pour traiter les fichiers PCB en utilisant les scripts?" [35319-36519] -->
-<h2><a name="comment_j_importe_des_graphiques_vectoriels_externe" id="comment_j_importe_des_graphiques_vectoriels_externe">Comment j'importe des graphiques vectoriels externe?</a></h2>
-<div class="level2">
-
-<p>
-Il existe un utilitaire open source provenant dâ??une tierce personne appelé <a href="http://www.pstoedit.net/"; class="urlextern" title="http://www.pstoedit.net/"; rel="nofollow">pstoedit</a> qui convertit des données postscript au format pcb. Il est inclus dans la plupart des distributions majeures de Linux. Vous pouvez utiliser votre graphique vectoriel préféré pour produire un logo ou toute autre type de marque amusante. Exportez-le comme eps si vous pouvez et assurez-vous que votre logo correspond à la à la boîte de remplissage (contrôlez-le avec un visualiseur postscript tel que ggv). Sâ??il nâ??y a pas dâ??export dâ??eps de disponible, vous pouvez produire du postscript en lâ??imprimant dans un fichier. Dans ce cas, vous pouvez ajouter une boîte de remplissage avec <a href="http://www.cs.wisc.edu/~ghost/doc/gnu/6.53/Ps2epsi.htm"; class="urlextern" title="http://www.cs.wisc.edu/~ghost/doc/gnu/6.53/Ps2epsi.htm"; rel="nofollow">ps2epsi</a>. Appelez pstoedit avec lâ??option «·<code>-f pcb</code>·» pour produire un fichier pcb valide qui contient les graphiques comme piste sur une couche 1. Chargez ce fichier dans pcb. Les graphiques seront alors quelque part dans le bord bas gauche de la visualisation. Vous avoir à zommer pour lâ??avoir sur lâ??écran.
-</p>
-
-<p>
-Lâ??import de graphiques vectoriels externes est utile si un si une forme irrégulière de pcb est nécessaire. Utilisez le tampon couper pour copier la forme de votre circuit réel.
-</p>
-
-</div>
-<!-- SECTION "Comment j'importe des graphiques vectoriels externe?" [36520-37846] -->
-<h2><a name="comment_j_attache_un_nom_a_mon_circuit" id="comment_j_attache_un_nom_a_mon_circuit">Comment j'attache un nom à mon circuit?</a></h2>
-<div class="level2">
-
-<p>
-Vous pouvez configurer le nom du pcb courant avec <code>Menu Edit - Edit name of - layout</code>. Cela configure lâ??attribut de titre sur le circuit. Cet attribut est utilisé pour els actions dâ??export. Il nâ??interfère pas avec le nom de fichier.
-</p>
-
-</div>
-<!-- SECTION "Comment j'attache un nom à mon circuit?" [37847-38140] -->
-<h1><a name="autorouteur" id="autorouteur">Autorouteur</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "Autorouteur" [38141-38166] -->
-<h2><a name="comment_je_force_l_autorouteur_a_ne_placer_des_pistes_que_sur_une_couche_particuliere" id="comment_je_force_l_autorouteur_a_ne_placer_des_pistes_que_sur_une_couche_particuliere">Comment je force l'autorouteur à ne placer des pistes que sur une couche particulière?</a></h2>
-<div class="level2">
-
-<p>
-Désactivez juste les couches dont vous ne voulez pas (habituellement vertes et bleues) en cliquant sur le nom de la couche puis pressez autoroute.
-</p>
-
-</div>
-<!-- SECTION "Comment je force l'autorouteur à ne placer des pistes que sur une couche particulière?" [38167-38416] -->
-<h2><a name="commennt_forcer_l_autorouteur_a_router_seulement_dans_les_limites_des_contours_du_pcb" id="commennt_forcer_l_autorouteur_a_router_seulement_dans_les_limites_des_contours_du_pcb">Commennt forcer l'autorouteur à router seulement dans les limites des contours du pcb?</a></h2>
-<div class="level2">
-
-<p>
-Vous pouvez faire fonctionner lâ??autorouteur seulement dans une zone donnée en dessinant un polygone de cuivre se conformant à votre emboîtement de circuit et placez-le dans chaque couche que vous tentez dâ??autorouter. Vous pouvez aussi utiliser cette astuce pour ne seulement autorouter quâ??une petite zone. Bien sûr, si vous avez un net qui touche accidentellement le polygone, toutes les routes seront court-circuitées à ce net.
-</p>
-
-</div>
-<!-- SECTION "Commennt forcer l'autorouteur à router seulement dans les limites des contours du pcb?" [38417-38952] -->
-<h2><a name="comment_je_route_les_plans_d_alimentation_et_de_masse_avec_l_autorouteur" id="comment_je_route_les_plans_d_alimentation_et_de_masse_avec_l_autorouteur">Comment je route les plans d'alimentation et de masse avec l'autorouteur?</a></h2>
-<div class="level2">
-
-<p>
-Connectez les polygones qui deviendront vos plans dâ??alimantation (et de masse) Ã un net et lâ??autorouteur sâ??occupera du reste. Vous pouvez avoir besoin de quelques astuces de clearances de polygone pour avoir le routage de lâ??alimentation _et_ le routage dans les limites de la carte.
-</p>
-
-</div>
-<!-- SECTION "Comment je route les plans d'alimentation et de masse avec l'autorouteur?" [38953-39323] -->
-<h2><a name="le_circuit_produit_par_l_autorouteur_est_inefficace" id="le_circuit_produit_par_l_autorouteur_est_inefficace">Le circuit produit par l'autorouteur est inefficace!</a></h2>
-<div class="level2">
-
-<p>
-Ce une limitation technologique de lâ??autorouteur actuel. Il est sans grille et utilise seulement les rectangles géométriques.
-</p>
-
-</div>
-<!-- SECTION "Le circuit produit par l'autorouteur est inefficace!" [39324-39517] -->
-<h2><a name="le_circuit_produit_par_l_autorouteur_est_moche" id="le_circuit_produit_par_l_autorouteur_est_moche">Le circuit produit par l'autorouteur est moche!</a></h2>
-<div class="level2">
-
-<p>
-Vous êtes plus que bienvenu pour contribuer à un autorouteur topologique.
-</p>
-
-</div>
-<!-- SECTION "Le circuit produit par l'autorouteur est moche!" [39518-39654] -->
-<h1><a name="generation_gerber_et_production_de_fichiers_i_o" id="generation_gerber_et_production_de_fichiers_i_o">Génération Gerber et production de fichiers I/O</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "Génération Gerber et production de fichiers I/O" [39655-39719] -->
-<h2><a name="comment_je_realise_des_contours_de_carte_pour_proposer_mes_gerbers_vers_le_fabricant_de_carte" id="comment_je_realise_des_contours_de_carte_pour_proposer_mes_gerbers_vers_le_fabricant_de_carte">Comment je réalise des contours de carte pour proposer mes gerbers vers le fabricant de carte?</a></h2>
-<div class="level2">
-
-<p>
-Vous pouvez ajouter une couche de contour pour vos projets pcb. PCB interprète toute couche appelée «·outline·» (edit â??> edit name of â??> active layer) comme étant le bord absolu du pcb. PCB imprime des fichiers gerber qui représente rigidement ceci.
-</p>
-
-<p>
-Vous pouvez entrer voter couche de contour par lâ??interface graphique de PCB. Vous dessinez simplement les lignes de contour de la carte. Vous pouvez générer des cartes de toute forme de cette manière.
-</p>
-
-<p>
-Il est aussi possible dâ??éditer le format de fichier natif .pcb de votre circuit. Jâ??utilise habituellement la Couche 8 pour les contours:
-</p>
-<pre class="code">Layer(8 "outline")
-(
- Line[x1 y1 x2 y2 1000 2000 0x00000000]
- Line[x2 y2 x3 y3 1000 2000 0x00000000]
- Line[x3 y3 x4 y4 1000 2000 0x00000000]
- Line[x4 y4 x1 y1 1000 2000 0x00000000]
- Line[<more points go here for non-square boards> 1000 2000 0x00000000]
-)</pre>
-
-</div>
-<!-- SECTION "Comment je réalise des contours de carte pour proposer mes gerbers vers le fabricant de carte?" [39720-40703] -->
-<h2><a name="j_ai_fini_mon_placement._comment_je_le_controle" id="j_ai_fini_mon_placement._comment_je_le_controle">J'ai fini mon placement. Comment je le contrôle?</a></h2>
-<div class="level2">
-<ul>
-<li class="level1"><div class="li"> Lancez un contrôle des règles de dessin soit par lâ??interface de commande (â??DRC()") ou depuis le menu (Connects - Design Rule Checker). Vous pouvez configurer les règles avec la section des tailles dans le dialogue preference. Les résultats du contrôle sont montrés dans la fenêtre de journal (log). </div>
-</li>
-</ul>
-
-<p>
-avant de lancer le contrôleur de DRC, il est essentiel de contrôler vos fichiers Gerber. La Suite gEDA inclut le programme «·gerbv·» pour cette tâche. Vous avez ici quelques éléments à contrôler/vérifier:
-</p>
-<ul>
-<li class="level1"><div class="li"> Contrôlez que toutes les largeurs de pistes ont la taille correcte. Assurez-vous aussi que les largeurs de pistes et les séparations métal-métal sont au-dessus du minimum spécifié par votre fabricant de PCB.</div>
-</li>
-<li class="level1"><div class="li"> Contrôlez que tous les diamètres de trous sont à la bonne taille.</div>
-</li>
-<li class="level1"><div class="li"> Contrôlez que les anneaux de métal autour des trous/vias sont suffisamment larges. Lâ??anneau annulaire est la distance entre les bords du trou et le diamètre extérieur de la métallisation. Lâ??anneau annulaire doit être suffisamment large pour permettre la zone de perçage + connexion entre couches + autres anomalies de fabrication. Cette information devrait être disponible chez votre fabricant de PCB·; ils publient normalement les tailles minimum dâ??anneau annulaire dans leurs documents de règles de fabrication.</div>
-</li>
-<li class="level1"><div class="li"> Contrôlez que vos antipads (clearance autour des trous/vias) soient suffisamment larges. Cette information doit être disponible chez votre fabricant de PCB·; demandez-leur leurs documents de règles de fabrication.</div>
-</li>
-<li class="level1"><div class="li"> Vérifiez quâ??aucun soldermask ou silkscreen ne se superpose avec une pastille de cuivre ou un trou passant.</div>
-</li>
-<li class="level1"><div class="li"> Sur les couches de plan, vérifiez quâ??au moins quelques vias sâ??y connectent (oui, jâ??ai vu une carte ou le plan de masse complet était flottant â?? il nâ??avait pas été réalisé avec pcb, soit dit en passant)</div>
-</li>
-<li class="level1"><div class="li"> Sur les couches de plan, vérifiez quâ??au moins quelques vias _nâ??y sont pas_ connecté.</div>
-</li>
-<li class="level1"><div class="li"> Effectuez une contrôle visuel dâ??anomalie sur toutes les couches. Rien de détaillé, jetez juste une regard approximatif sur la manière dont cela evrait être.</div>
-</li>
-<li class="level1"><div class="li"> Toutes les couches sont-elles négatives/positives telles quâ??elles devraient lâ??être? Notez que certains fabricants veulent seulement des couches positives. PCB en créera automatiquement des Gerbers négatives sur les couches de plans sans pistes. Si vous voulez une couche avec tous les plans en sortie comme couche positive, dessinez une piste simple quelque part dans une zone inutilisée du plan. Cela obligera PCB à faire de cette couche une couche positive.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "J'ai fini mon placement. Comment je le contrôle?" [40704-43388] -->
-<h1><a name="vous_n_avez_pas_repondu_a_mes_questions._ou_puis-je_trouver_d_autres_informations_sur_pcb" id="vous_n_avez_pas_repondu_a_mes_questions._ou_puis-je_trouver_d_autres_informations_sur_pcb">Vous n'avez pas répondu à mes questions. Où puis-je trouver d'autres informations sur PCB?</a></h1>
-<div class="level1">
-
-<p>
-<a href="http://www.luciani.org/geda/pcb/faq-pcb-footprint.html"; class="urlextern" title="http://www.luciani.org/geda/pcb/faq-pcb-footprint.html"; rel="nofollow">http://www.luciani.org/geda/pcb/faq-pcb-footprint.html</a><br/>
- <a href="http://pcb.sourceforge.net/faq.html"; class="urlextern" title="http://pcb.sourceforge.net/faq.html"; rel="nofollow">http://pcb.sourceforge.net/faq.html</a><br/>
- <a href="http://pcb.sourceforge.net/pcb-20060822/pcb.html#Top"; class="urlextern" title="http://pcb.sourceforge.net/pcb-20060822/pcb.html#Top"; rel="nofollow">http://pcb.sourceforge.net/pcb-20060822/pcb.html#Top</a>
-</p>
-
-<p>
-Vous pouvez avoir des réponses plus rapides avec la liste des geda-user. Si vous nâ??avez trouvé une réponse à votre question à propos de PCB sur cette page ou dans les autres documentations, postez alors sur la liste! Notez que vous devez y souscrire avant de pouvoir y écrire. Les listes de gEDA et leurs archives sont sur: <a href="http://geda.seul.org/mailinglist/index.html"; class="urlextern" title="http://geda.seul.org/mailinglist/index.html"; rel="nofollow">http://geda.seul.org/mailinglist/index.html</a>
-</p>
-
-</div>
-<!-- SECTION "Vous n'avez pas répondu à mes questions. Où puis-je trouver d'autres informations sur PCB?" [43389-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/001geda_scg.html b/docs/wiki/001geda_scg.html
deleted file mode 100644
index 15c4ca0..0000000
--- a/docs/wiki/001geda_scg.html
+++ /dev/null
@@ -1,619 +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>geda:scg.fr</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-05-24T22:27:26-0400" />
-<meta name="keywords" content="geda,scg.fr" />
-<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/geda:scg.fr?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:scg.fr"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:scg.fr"; />
-<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="#geda_gaf_symbol_creation_document" class="toc">gEDA/gaf Symbol Creation Document</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#overview" class="toc">Overview</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#component_symbol_creation" class="toc">Component symbol creation</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#requirements" class="toc">Requirements</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#style" class="toc">Style</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#text" class="toc">Text</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#attributes" class="toc">Attributes</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#graphics" class="toc">Graphics</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#pins" class="toc">Pins</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#electrical" class="toc">Electrical</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#footprint_naming_conventions" class="toc">Footprint naming conventions</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#notes" class="toc">Notes</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#integrated_circuit_packages" class="toc">Integrated circuit packages</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#integrated_circuit_smt_packages" class="toc">Integrated circuit SMT packages</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#basic_semiconductors" class="toc">Basic semiconductors</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#basic_smt_semiconductors" class="toc">Basic SMT semiconductors</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#passive_components" class="toc">Passive components</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#passive_smt_components" class="toc">Passive SMT components</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#hints_and_tips" class="toc">Hints and Tips</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#example" class="toc">Example</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#document_revision_history" class="toc">Document Revision History</a></span></div></li></ul>
-</li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="geda_gaf_symbol_creation_document" id="geda_gaf_symbol_creation_document">gEDA/gaf Symbol Creation Document</a></h1>
-<div class="level1">
-
-<p>
-by: Ales V. Hvezda / July 6th, 2004
-</p>
-
-<p>
-The latest version of this document may be found at: <a href="http://geda.seul.org/wiki/geda:scg"; class="urlextern" title="http://geda.seul.org/wiki/geda:scg"; rel="nofollow">http://geda.seul.org/wiki/geda:scg</a>
-</p>
-
-<p>
-This document is released under the <a href="http://geda.seul.org/wiki/geda:gfdl"; class="wikilink1" title="geda:gfdl">GNU Free Documentation License (GFDL)</a>.
-</p>
-
-</div>
-<!-- SECTION "gEDA/gaf Symbol Creation Document" [1-264] -->
-<h2><a name="overview" id="overview">Overview</a></h2>
-<div class="level2">
-
-<p>
-This document describes the creation of component symbols, including style conventions, and hints/tips and things to look out for when drawing symbols for the gEDA/gaf system.
-</p>
-
-</div>
-<!-- SECTION "Overview" [265-462] -->
-<h2><a name="component_symbol_creation" id="component_symbol_creation">Component symbol creation</a></h2>
-<div class="level2">
-
-<p>
-Component symbols (from here on known as â??symbolsâ??) are drawn using gschem just like drawing a schematic sheet. Here are the steps in a symbol in the gEDA/gaf system:<br/>
- 1. Run gschem and find a blank page or run: gschem filename-1.sym<br/>
- 2. Draw the symbol (see the style guide below for some conventions).<br/>
- 3. Translate the symbol to the origin using Edit/Symbol Translate…<br/>
-
-</p>
-<ul>
-<li class="level1"><div class="li"> Zoom in at least one step.</div>
-</li>
-<li class="level1"><div class="li"> Make sure the snap is ON (this is critical).</div>
-</li>
-<li class="level1"><div class="li"> Make sure grid snap size is set to 100 (this is critical).</div>
-</li>
-<li class="level1"><div class="li"> Select â??Symbol Translate…â?? or the press equivalent hotkey.</div>
-</li>
-<li class="level1"><div class="li"> Enter 0 into the entry field and press OK.<br/>
-</div>
-</li>
-</ul>
-
-<p>
-Translating the symbol to the origin is a required step. To translate a symbol elsewhere, enter a offset (in mils) which is a even multiple of 100. Make sure all pins are snapped to a 100 mil grid point.
-</p>
-
-<p>
-4. Save the symbol using Save or SaveAs… Here are some symbol naming conventions:<br/>
-
-</p>
-<ul>
-<li class="level1"><div class="li"> Symbols are named: symbolname-#.sym</div>
-</li>
-<li class="level1"><div class="li"> Symbols end with a .sym extension.</div>
-</li>
-<li class="level1"><div class="li"> Symbols have a -# where # is a number. Typically # is 1 but if there are multiple symbols for a device then this number simply increments.</div>
-</li>
-<li class="level1"><div class="li"> Symbol names are typically lowercase but letters which are part of a part number are uppercase.</div>
-</li>
-<li class="level1"><div class="li"> The above case rule can be broken if the filename looks incorrect or wrong.</div>
-</li>
-</ul>
-
-<p>
- 5. Place the symbol in one of the directories specified by the componentlibrary keyword in the system-gafrc file. Once this is done, the symbol should be visible immediately and can be selected and placed with the â??Add/Select Component…â?? menu item.
-</p>
-
-</div>
-<!-- SECTION "Component symbol creation" [463-2082] -->
-<h2><a name="requirements" id="requirements">Requirements</a></h2>
-<div class="level2">
-
-<p>
-This section describes the various requirements which must be met in order to create a valid symbol which will display and netlist in the gEDA/gaf system. Most of the requirements center around having certain attributes attached or inside the symbol.<br/>
- Running gsymcheck will check that all of these requirements are met. gsymcheck will output fatal errors which are quite serious and must be corrected. gsymcheck will also output warnings on things which should be fixed but are not fatal.<br/>
- For more information on the attributes presented here, please see the Master Attribute Document.
-</p>
-<ul>
-<li class="level1"><div class="li"> device=DEVICENAME should be placed somewhere in the symbol and made invisible. device= is the device name and is required. Typically the devicename is in all caps (capital letters). This attribute should not be used as a label. Use a separate text object for the label. If the object is a graphic then device= should be set to none (device=none). It is no longer required to attach this attribute anything; just having it exist as device=DEVICENAME is good enough.</div>
-</li>
-<li class="level1"><div class="li"> graphical=1 should exist somewhere in a symbol which is purely graphical (such as a title block or decon symbol). Symbols which have this attribute have no electrical or circuit significance. Donâ??t forget to set device=none.</div>
-</li>
-<li class="level1"><div class="li"> description=text should exist somewhere in the symbol. This attribute provides an one line description of the symbol.</div>
-</li>
-<li class="level1"><div class="li"> All pins should have a pair of attributes attached to them: pinseq=# and pinnumber=#. The first attribute, pinseq=# is just a sequence number and increments sequentially starting at 1. The second attribute pinnumber=# is the number of the pin. When a symbol is netlisted, the pin numbers are output in order of pin sequence. The pin number can be alphanumeric (i.e. like E or C).</div>
-</li>
-<li class="level1"><div class="li"> All pins should also have pinlabel=value attached to them. This attribute is the name or label of the pin (vs the pin number). This attribute is also used when a symbol is used in a hierarchical schematic. Please make this attribute green (instead of the default attribute yellow).</div>
-</li>
-<li class="level1"><div class="li"> All pins should also have pintype=value attached to them. This attribute describes the kind of a pin. Possible values are: in, out, io, oc, oe, pas, tp, tri, clk, pwr. Please see the Master Attribute Document for more info.</div>
-</li>
-<li class="level1"><div class="li"> If a component has multiple slots in a package (such as a 7400 (NAND) which has 4 NANDs per package) then you need a numslots=# attribute. The # is the number of slots the device has. numslots= should be exist somewhere in the symbol and made invisible. Additional slot related required attributes are described below.</div>
-</li>
-<li class="level1"><div class="li"> If a component has multiple slots in a physical package then you also need to include a slotdef=#:#,#,#… for every slot. The first # corresponds to the slot number. If a device has 4 slots then there should be slotdef=1:…, slotdef=2:…, slotdef=3:…, and slotdef=4:…, attributes existing somewhere in the symbol and made invisible. The subsequent # have a one-to-one correspondence to pinseq=# attributes and specify what corresponding pinnumber=# should be when that slot is set. See The attached 7400-1.sym as an example of how this should all work.</div>
-</li>
-<li class="level1"><div class="li"> It is recommended that all symbols which have slots have a slot=1 attribute inside the symbol.</div>
-</li>
-<li class="level1"><div class="li"> footprint=PACKAGENAME should exist somewhere in the symbol which might be used with the PCB netlister. PACKAGENAME is the PCB footprint or package type like DIP14 or DIP40. Please see the Footprint naming conventions chapter for further detail. See also the PCB documentation and gnetlist/docs/README.pcb for more info on this attribute.</div>
-</li>
-<li class="level1"><div class="li"> You should put a refdes=U? attribute inside the symbol. Make only the value visible and it will be promoted (attached to the outside of the symbol (so it can be edited) when the symbol is placed in a schematic.</div>
-</li>
-<li class="level1"><div class="li"> The label= attribute should not be attached anywhere in the symbol. It is obsolete.</div>
-</li>
-<li class="level1"><div class="li"> The name= attribute should not be attached anywhere in the symbol.</div>
-</li>
-<li class="level1"><div class="li"> The netname= attribute should not be attached anywhere in the symbol. It is only used in schematics.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Requirements" [2083-6223] -->
-<h2><a name="style" id="style">Style</a></h2>
-<div class="level2">
-
-<p>
-This section describes the style in which is used in the standard gEDA/gaf symbol library.
-</p>
-
-</div>
-<!-- SECTION "Style" [6224-6333] -->
-<h3><a name="text" id="text">Text</a></h3>
-<div class="level3">
-<ul>
-<li class="level1"><div class="li"> All Text labels should all be 10 pt in size.</div>
-</li>
-<li class="level1"><div class="li"> Text (labels not attributes) should be color number 9 (text | green).</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Text" [6334-6472] -->
-<h3><a name="attributes" id="attributes">Attributes</a></h3>
-<div class="level3">
-<ul>
-<li class="level1"><div class="li"> Pin numbers (which are attributes) should all be 8 pt in size.</div>
-</li>
-<li class="level1"><div class="li"> Attached attributes should be yellow. The color is set automatically to yellow if the text item is attached.</div>
-</li>
-<li class="level1"><div class="li"> The only exception to this is pinlabel= attributes, those should be color number 9 (text | green). If every text item within a symbol is yellow, the symbol looks too yellow.</div>
-</li>
-<li class="level1"><div class="li"> Attributes can be attached to some part of the symbol. Toplevel attributes (like the device= or net= attributes) used to be required to be attached to something to be attributes, but now they just have to exist in the symbol file as name=value.</div>
-</li>
-<li class="level1"><div class="li"> Expanding a bit on the last sentence, as long as the text item has the format name=value, it is considered an attribute. Attributes inside a symbol do not have to be attached to anything. In order to see hidden attributes in gschem select Edit/Show/Hide Inv Text.</div>
-</li>
-<li class="level1"><div class="li"> There is a symbol content versioning system in libgeda which is based on the symversion= attribute. Please see the Master Attribute Document for more information on using this versioning scheme.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Attributes" [6473-7569] -->
-<h3><a name="graphics" id="graphics">Graphics</a></h3>
-<div class="level3">
-<ul>
-<li class="level1"><div class="li"> Lines, boxes, arcs, and any other graphics should be color number 3 (graphic | green).</div>
-</li>
-<li class="level1"><div class="li"> Polarity bubbles should be color number 6 (logic bubble | cyan)</div>
-</li>
-<li class="level1"><div class="li"> If you are unsure on how to make a new symbol look or how big to make a new symbol, look at the existing symbols to get a feel for the appropriate appearance and size.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Graphics" [7570-7920] -->
-<h3><a name="pins" id="pins">Pins</a></h3>
-<div class="level3">
-<ul>
-<li class="level1"><div class="li"> Pins should all be 300 mils (3 grid spaces) long.</div>
-</li>
-<li class="level1"><div class="li"> For pins which are next to a logic bubble, make the pins 200 mils (2 grid spaces) long and then make the logic bubble 100 mils in diameter. In order to draw a 100 mil diameter circle, you will need to change the snap spacing to 50.</div>
-</li>
-<li class="level1"><div class="li"> A pin has two ends: one end has a red endpoint and one end that does not. The red endpoint is where nets can be connected. You can either rotate the pin so that this active end is in the right place or manually edit the symbol file changing the â??whichendâ?? parameter on the pin object. See the File Format document for more info.</div>
-</li>
-<li class="level1"><div class="li"> Be that all endpoints of pins which are meant to be connected to are on the 100 mil grid. The endpoint which is not active can be off the grid if necessary.</div>
-</li>
-<li class="level1"><div class="li"> Pins should be color number 1 (pins | white).</div>
-</li>
-<li class="level1"><div class="li"> Leave 400 mils (4 grid spaces) between (vertically) pins, unless you are drawing a special symbol, then just try to make it look good.</div>
-</li>
-<li class="level1"><div class="li"> Pin number attributes should be 50 mils above (or below; which ever makes the most sense) the pin which they are attached to.</div>
-</li>
-<li class="level1"><div class="li"> Input pins belong on the left and output pins belong on the right of the symbol.</div>
-</li>
-<li class="level1"><div class="li"> Please do not mix inputs and outputs on the same side of the symbol, unless absolutely necessary.</div>
-</li>
-<li class="level1"><div class="li"> You can have pins on the top or bottom of a symbol.</div>
-</li>
-<li class="level1"><div class="li"> The order for rows of pins (buses) should be LSB (least significant bit) to MSB (most significant bit). When drawing pins which are part of a bus, make sure the LSB of the bus is at the top (or for pins on top/bottom of a symbol, left of the rest of the other pins). Look at 74/74181-1.sym for a correct example of this order (A0 on top through A3 and B0 on top through B3). Violating this rule will make connecting buses much more diffcult.</div>
-</li>
-<li class="level1"><div class="li"> When placing pins on logic gates, be sure to place the smallest pin numbers toward the top (or left) and then increment going down (or across).</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Pins" [7921-9876] -->
-<h3><a name="electrical" id="electrical">Electrical</a></h3>
-<div class="level3">
-<ul>
-<li class="level1"><div class="li"> Do not draw power and ground pins. That information will be conveyed using attributes (see the netattrib document).</div>
-</li>
-<li class="level1"><div class="li"> The above rule can be broken if necessary, but keep in mind most of the standard library does not have power pins showing.</div>
-</li>
-<li class="level1"><div class="li"> Keep in mind, symbols are supposed to be symbolic, they do not represent the physical package that the device comes in.</div>
-</li>
-<li class="level1"><div class="li"> There is some disagreement on above, so this is okay too: Arrange the pins on a symbol logically so that they promote an uncluttered schematic. Note that this is frequently not the same pin arrangement as the physical device.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Electrical" [9877-10499] -->
-<h2><a name="footprint_naming_conventions" id="footprint_naming_conventions">Footprint naming conventions</a></h2>
-<div class="level2">
-
-<p>
-This section describes the conventions for naming of footprints used in gEDA/gaf.<br/>
- The purpose of the naming convention is to establish a standard to maintain the same naming convention through the different phases of the CAD chain. This helps in ensuring that the collaborative effort of gEDA/gaf is not lost.
-</p>
-
-</div>
-<!-- SECTION "Footprint naming conventions" [10500-10853] -->
-<h3><a name="notes" id="notes">Notes</a></h3>
-<div class="level3">
-<ul>
-<li class="level1"><div class="li"> Unless otherwise noted, numerical pin names will be used, starting from 1.</div>
-</li>
-<li class="level1"><div class="li"> n is for the pin count.</div>
-</li>
-<li class="level1"><div class="li"> m is for the pin spacing in mils.</div>
-</li>
-<li class="level1"><div class="li"> x is for the x dimension of the package (excluding pins). In particular this is used for the QFP package family.</div>
-</li>
-<li class="level1"><div class="li"> SMT means surface mount, other components are through-hole.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Notes" [10854-11196] -->
-<h3><a name="integrated_circuit_packages" id="integrated_circuit_packages">Integrated circuit packages</a></h3>
-<div class="level3">
-<ul>
-<li class="level1"><div class="li"> Dual in line packages with up to 22 100 mil spaced pins and 300 mil row spacing are called DIPn.</div>
-</li>
-<li class="level1"><div class="li"> Dual in line packages with 24 or more 100 mil spaced pins and 300 mil row spacing are called DIPnN.</div>
-</li>
-<li class="level1"><div class="li"> Dual in line packages with 100 mil spaced pins and 400 mil row spacing are called DIPnH.</div>
-</li>
-<li class="level1"><div class="li"> Dual in line packages with 24 or more 100 mil spaced pins and 600 mil row spacing are called DIPn.</div>
-</li>
-<li class="level1"><div class="li"> Shrink dual in line packages with up to 24 70 mil spaced pins and 300 mil row spacing are called SDIPn.</div>
-</li>
-<li class="level1"><div class="li"> Shrink dual in line packages with more than 24 70 mil spaced pins and 400 mil row spacing are called SDIPn.</div>
-</li>
-<li class="level1"><div class="li"> Single in line packages with 100 mil spaced pins are called SIPnN. See also JUMPER, below.</div>
-</li>
-<li class="level1"><div class="li"> Zig-zag in-line package are called ZIPn.</div>
-</li>
-<li class="level1"><div class="li"> Plastic leadless chip carrier with pin socket are called PLCCnX.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Integrated circuit packages" [11197-12065] -->
-<h3><a name="integrated_circuit_smt_packages" id="integrated_circuit_smt_packages">Integrated circuit SMT packages</a></h3>
-<div class="level3">
-<ul>
-<li class="level1"><div class="li"> Small outline SMT packages with up to 16 50 mil spaced pins and 150 mil total width are called SOn.</div>
-</li>
-<li class="level1"><div class="li"> Small outline SMT packages with more than 16 50 mil spaced pins and 150 mil total width are called SOnN.</div>
-</li>
-<li class="level1"><div class="li"> Small outline SMT packages with 50 mil spaced pins and 200 mil total width are called SOnM.</div>
-</li>
-<li class="level1"><div class="li"> Small outline SMT packages with up to 20 50 mil spaced pins and 300 mil total width are called SOnW.</div>
-</li>
-<li class="level1"><div class="li"> Small outline SMT packages with more than 20 50 mil spaced pins and 300 mil total width are called SOn.</div>
-</li>
-<li class="level1"><div class="li"> Small outline SMT packages with 44 or more 50 mil spaced pins and 525 mil total width are called SOn.</div>
-</li>
-<li class="level1"><div class="li"> Metric shrink small outline SMT packages with 0.65 mm spaced pins and 323 mil total width are called MSSOPn. NOTE: To be confirmed.</div>
-</li>
-<li class="level1"><div class="li"> Metric shrink small outline SMT packages with up to 44 0.65 mm spaced pins and 420 mil total width are called MSSOPnW.</div>
-</li>
-<li class="level1"><div class="li"> Metric shrink small outline SMT packages with over 44 0.65 mm spaced pins and 545 mil total width are called MSSOPnW.</div>
-</li>
-<li class="level1"><div class="li"> Shrink small outline SMT packages with 25 mil spaced pins and 420 mil total width are called SSOPnW.</div>
-</li>
-<li class="level1"><div class="li"> Quarter size small outline SMT packages with 25 mil spaced pins and 244 mil total width are called SSOPn.</div>
-</li>
-<li class="level1"><div class="li"> Thin small outline SMT packages with 21.65 mil spaced pins and 535 mil total width are called TSOPn.</div>
-</li>
-<li class="level1"><div class="li"> Thin small outline SMT packages with 20 mil spaced pins and 795 mil total width are called TSOPnA.</div>
-</li>
-<li class="level1"><div class="li"> Thin small outline SMT packages with 20 mil spaced pins and 559 mil total width are called TSOPnB.</div>
-</li>
-<li class="level1"><div class="li"> Thin shrink small outline SMT packages with up to 28 26 mil spaced pins and 260 mil total width are called TSSOPn.</div>
-</li>
-<li class="level1"><div class="li"> Thin shrink small outline SMT packages with over 28 20 mil spaced pins and 319 mil total width are called TSSOPn.</div>
-</li>
-<li class="level1"><div class="li"> Ultra Super Mini SMT packages with up to 16 0.5 mm spaced pins are called USn.</div>
-</li>
-<li class="level1"><div class="li"> Plastic leadless chip carrier SMT are called PLCCn.</div>
-</li>
-<li class="level1"><div class="li"> Square quad-side at pack SMT are called QFPn x.</div>
-</li>
-<li class="level1"><div class="li"> Rectangular quad-side at pack SMT are called QFPn R.</div>
-</li>
-<li class="level1"><div class="li"> Square low profile quad-side at pack SMT are called LQFPn x.</div>
-</li>
-<li class="level1"><div class="li"> Square thin quad-side at pack SMT are called TQFPn x.</div>
-</li>
-<li class="level1"><div class="li"> Square Quad-side at no-lead SMT without exposed paddle (back side contact) are called QFNn x. Pin count is n and package size is x mm.</div>
-</li>
-<li class="level1"><div class="li"> Square Quad-side at no-lead SMT with exposed paddle (back side contact) are called QFNn x EP. Pin count is n and package size is x mm.</div>
-</li>
-<li class="level1"><div class="li"> Thin profile square Quad-side at no-lead SMT without exposed paddle (back side contact) are called TQFNn x. Pin count is n and package size is x mm.</div>
-</li>
-<li class="level1"><div class="li"> Thin profile square Quad-side at no-lead SMT with exposed paddle (back side contact) are called TQFNn x EP. Pin count is n and package size is x mm.</div>
-</li>
-<li class="level1"><div class="li"> Dual in line style crystal oscillators are OSC8 and OSC14.</div>
-</li>
-<li class="level1"><div class="li"> 5 pin SOT SMT packages are SOT25 and SOT325.</div>
-</li>
-<li class="level1"><div class="li"> 6 pin SOT SMT packages are SOT26 and SOT326.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Integrated circuit SMT packages" [12066-14996] -->
-<h3><a name="basic_semiconductors" id="basic_semiconductors">Basic semiconductors</a></h3>
-<div class="level3">
-<ul>
-<li class="level1"><div class="li"> Axial diodes are called ALFm. Pin 1 is the cathode.</div>
-</li>
-<li class="level1"><div class="li"> Conventional through hole LED is LED3 and LED5 for 3 and 5 mm respectively. Pin 1 is plus. NOTE: Should probably be changed to be in line with diode convention.</div>
-</li>
-<li class="level1"><div class="li"> TO transistors are TO5, TO92, TO126, TO220 etc. Suxes may apply, e.g. TO126W is for wide, TO126S is for standing, TO126SW is for standing, wide.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Basic semiconductors" [14997-15399] -->
-<h3><a name="basic_smt_semiconductors" id="basic_smt_semiconductors">Basic SMT semiconductors</a></h3>
-<div class="level3">
-<ul>
-<li class="level1"><div class="li"> SOD diode SMT packages use their standard package name, e.g. SOD80, SOD87, SOD106A, SOD110. There are also SOD123, SOD323 with narrow pads.</div>
-</li>
-<li class="level1"><div class="li"> SOT transistor SMT packages use their standard package name, e.g. SOT23, SOT323. There is also an SC90.</div>
-</li>
-<li class="level1"><div class="li"> SOT transistor SMT packages with numbering as for diodes (pin 1 is cathode, pin 2 anode) are SOT23D, SOT323D.</div>
-</li>
-<li class="level1"><div class="li"> 4 pin SOT SMT packages are SOT89, SOT143, SOT223.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Basic SMT semiconductors" [15400-15855] -->
-<h3><a name="passive_components" id="passive_components">Passive components</a></h3>
-<div class="level3">
-<ul>
-<li class="level1"><div class="li"> Axial non-polar components (typically resistor, capacitor) are called ACYm.</div>
-</li>
-<li class="level1"><div class="li"> Bottom lead (radial) non-polar circular component (typically capacitor) is RCYm.</div>
-</li>
-<li class="level1"><div class="li"> Bottom lead non-polar rectangular component (typically capacitor) is BREm.</div>
-</li>
-<li class="level1"><div class="li"> A standard crystal is HC49, or other HC designations as required.</div>
-</li>
-<li class="level1"><div class="li"> Single row 100 mil pin spacing jumpers are JUMPERn. The main difference compared to single in line package is the hole size.</div>
-</li>
-<li class="level1"><div class="li"> Dual row 100 mil spacing headers with DIP pin numbering are HEADERn 1. Note that n is an even number.</div>
-</li>
-<li class="level1"><div class="li"> Dual row 100 mil spacing headers with ribbon cable numbering are HEADERn 2. Note that n is an even number.</div>
-</li>
-<li class="level1"><div class="li"> Angled full header connectors with latches are DIN41651 n.</div>
-</li>
-<li class="level1"><div class="li"> Standing full header connectors with latches are DIN41651 nS.</div>
-</li>
-<li class="level1"><div class="li"> DSUB connectors female are DBnF.</div>
-</li>
-<li class="level1"><div class="li"> DSUB connectors male are DBnM.</div>
-</li>
-<li class="level1"><div class="li"> Female DIN card-to-card connectors are DIN41612CnF. Add S suffix for standing.</div>
-</li>
-<li class="level1"><div class="li"> Male DIN card-to-card connectors are DIN41612CnM. Add S suffix for standing.</div>
-</li>
-<li class="level1"><div class="li"> AMP modular RJ connectors with screen are RJ11, RJ12 and RJ45.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Passive components" [15856-16977] -->
-<h3><a name="passive_smt_components" id="passive_smt_components">Passive SMT components</a></h3>
-<div class="level3">
-<ul>
-<li class="level1"><div class="li"> Standard SMT resistors, inductors, capacitors etc are 0201, 0402, 0603, 0805, 1206, 1210, 1806, 1812, 1825, 2020, 2706.</div>
-</li>
-<li class="level1"><div class="li"> Tantalum SMT capacitors are EIA3216, EIA3528, EIA6032, and EIA7343. Pin 1 is plus.</div>
-</li>
-<li class="level1"><div class="li"> SMT electrolytics are designated by can diameter in 1/10 mm: SME33, SME43, SME53, SME66, SME84, SME104.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Passive SMT components" [16978-17330] -->
-<h2><a name="hints_and_tips" id="hints_and_tips">Hints and Tips</a></h2>
-<div class="level2">
-
-<p>
-This section describes some hints and tips which will make your symbol creation experience easier.<br/>
-
-</p>
-<ul>
-<li class="level1"><div class="li"> Avoid drawing things off of the grid. If you do, you cannot move the object(s) using the move command (if the grid is on) since the object will be snapped to the grid. [This was an old bug, which I think has been fixed, but avoid doing this anyway]. Use the symbol translate command instead (or move the object with grid snap off)</div>
-</li>
-<li class="level1"><div class="li"> If you need a finer grid then use Options/Snap Grid Spacing… to set a finer grid snap spacing. Just remember to set this back to 100 once you are ready to translate the symbol to the origin.</div>
-</li>
-<li class="level1"><div class="li"> If you want to translate a symbol from the origin to elsewhere, then use the â??Symbol translateâ?? command and enter a non zero number. Make sure this number is a multiple of 100 (ie 1000, or 1100).</div>
-</li>
-<li class="level1"><div class="li"> Pins MUST be snapped on the 100 spaced grid (at least the end which will have nets connected to it).</div>
-</li>
-<li class="level1"><div class="li"> Pins MUST be snapped on the 100 spaced grid (at least the end which will have nets connected to it). Yes this is line a duplicate. I canâ??t stress this point enough.</div>
-</li>
-<li class="level1"><div class="li"> Remember that pins are special objects; if you want to add a pin, make sure it is a pin and not a line or net. Use the Add/Pin command to place a pin.</div>
-</li>
-<li class="level1"><div class="li"> Donâ??t include nets or buses inside symbols. That is not supported and doesnâ??t make much sense anyway.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Hints and Tips" [17331-18726] -->
-<h2><a name="example" id="example">Example</a></h2>
-<div class="level2">
-
-<p>
-This section provides a simple example which tries to follow all of the above rules. This symbol is of a 7400 (NAND gate).<br/>
-
-</p>
-
-<p>
-<pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">v 20031231 1
-L 300 200 300 800 3 0 0 0 -1 -1
-T 300 0 9 8 1 0 0 0 1
-7400
-L 300 800 700 800 3 0 0 0 -1 -1
-T 500 900 5 10 0 0 0 0 1
-device=7400
-T 500 1100 5 10 0 0 0 0 1
-slot=1
-T 500 1300 5 10 0 0 0 0 1
-numslots=4
-T 500 1500 5 10 0 0 0 0 1
-slotdef=1:1,2,3
-T 500 1700 5 10 0 0 0 0 1
-slotdef=2:4,5,6
-T 500 1900 5 10 0 0 0 0 1
-slotdef=3:9,10,8
-T 500 2100 5 10 0 0 0 0 1
-slotdef=4:12,13,11
-L 300 200 700 200 3 0 0 0 -1 -1
-A 700 500 300 270 180 3 0 0 0 -1 -1
-V 1050 500 50 6 0 0 0 -1 -1 0 -1 -1 -1 -1 -1
-P 1100 500 1300 500 1 0 1
-{
-T 1100 550 5 8 1 1 0 0 1
-pinnumber=3
-T 1100 450 5 8 0 1 0 2 1
-pinseq=3
-T 950 500 9 8 0 1 0 6 1
-pinlabel=Y
-T 950 500 5 8 0 1 0 8 1
-pintype=out
-}
-P 300 300 0 300 1 0 1
-{
-T 200 350 5 8 1 1 0 6 1
-pinnumber=2
-T 200 250 5 8 0 1 0 8 1
-pinseq=2
-T 350 300 9 8 0 1 0 0 1
-pinlabel=B
-T 350 300 5 8 0 1 0 2 1
-pintype=in
-}
-P 300 700 0 700 1 0 1
-{
-T 200 750 5 8 1 1 0 6 1
-pinnumber=1
-T 200 650 5 8 0 1 0 8 1
-pinseq=1
-T 350 700 9 8 0 1 0 0 1
-pinlabel=A
-T 350 700 5 8 0 1 0 2 1
-pintype=in
-}
-T 300 900 8 10 1 1 0 0 1
-refdes=U?
-T 500 2250 5 10 0 0 0 0 1
-footprint=DIP14
-T 500 2450 5 10 0 0 0 0 1
-description=4 NAND gates with 2 inputs
-T 500 2850 5 10 0 0 0 0 1
-net=Vcc:14
-T 500 3050 5 10 0 0 0 0 1
-net=GND:7
-T 500 2650 5 10 0 0 0 0 1
-documentation=http://www-s.ti.com/sc/ds/sn74hc00.pdf
-</font></pre>
-</p>
-
-<p>
-This example produces the following (using gschem):
-</p>
-
-<p>
-<a href="_detail/001geda_symbol_7400-1_hidden.html" class="media" title="geda:symbol_7400-1_hidden.png"><img src="http://geda.seul.org/wiki/_media/geda:symbol_7400-1_hidden.png?w=&h=&cache=cache"; class="media" title=":geda:symbol_7400-1_hidden.png" alt=":geda:symbol_7400-1_hidden.png" /></a>
-</p>
-
-<p>
-This is the same symbol with all the hidden text visible (via Edit/Show/Hide Inv Text):
-</p>
-
-<p>
-<a href="_detail/001geda_symbol_7400-1.html" class="media" title="geda:symbol_7400-1.png"><img src="http://geda.seul.org/wiki/_media/geda:symbol_7400-1.png?w=&h=&cache=cache"; class="media" title=":geda:symbol_7400-1.png" alt=":geda:symbol_7400-1.png" /></a>
-</p>
-
-</div>
-<!-- SECTION "Example" [18727-20443] -->
-<h2><a name="document_revision_history" id="document_revision_history">Document Revision History</a></h2>
-<div class="level2">
-<table class="inline">
- <tr>
- <td> September 14th, 2002</td><td>Created symbol.tex from symbols.html </td>
- </tr>
- <tr>
- <td> October 31st, 2002</td><td>Fixed bad example symbol </td>
- </tr>
- <tr>
- <td> February 11th, 2003</td><td>Footprint naming conventions added </td>
- </tr>
- <tr>
- <td> September 27th, 2003</td><td>Applied Dan McMahillâ??s QFP and QFN patch </td>
- </tr>
- <tr>
- <td> July 6th, 2004</td><td>Added a bunch more details/hints to the pin section </td>
- </tr>
-</table>
-
-</div>
-<!-- SECTION "Document Revision History" [20444-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/001geda_suse_10.html b/docs/wiki/001geda_suse_10.html
deleted file mode 100644
index 14a8ba9..0000000
--- a/docs/wiki/001geda_suse_10.html
+++ /dev/null
@@ -1,61 +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>geda:suse_10.1</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="keywords" content="geda,suse_10.1" />
-<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/geda:suse_10.1?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:suse_10.1"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:suse_10.1"; />
-<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">
-
-
-
-<h1><a name="suse_10.1_install_notes" id="suse_10.1_install_notes">Suse 10.1 install notes</a></h1>
-<div class="level1">
-
-<p>
-These notes pertain to the latest gEDA CD install (20060825).
-</p>
-
-</div>
-<!-- SECTION "Suse 10.1 install notes" [1-101] -->
-<h2><a name="prerequisites" id="prerequisites">Prerequisites:</a></h2>
-<div class="level2">
-
-<p>
-If you are installing gEDA onto a pre-existing SuSE system, make sure your system runs the Gnome desktop, or at least has the Gnome libraries installed. If you have a KDE desktop system, unpredictable things may happen with the installer.
-</p>
-
-<p>
-When installing SuSE-10.1, click on the â??changeâ?? button when YaST shows you your configuration. Select â??softwareâ?? â?? â??detailsâ??. Then add the following packages to your installation list:
-</p>
-<ul>
-<li class="level1"><div class="li"> C/C++ tools</div>
-</li>
-<li class="level1"><div class="li"> Gnome development</div>
-</li>
-</ul>
-
-<p>
- Once these packages are installed, the installer should run to completion. You <strong>will</strong> need to let the installer become root to install gd-devel as well as WxGTK. If you donâ??t want to do this, then install gd-devel and WxGTK manually before running the installer.
-</p>
-
-</div>
-<!-- SECTION "Prerequisites:" [102-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/001geda_tasks.html b/docs/wiki/001geda_tasks.html
deleted file mode 100644
index 2625cca..0000000
--- a/docs/wiki/001geda_tasks.html
+++ /dev/null
@@ -1,27 +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>geda:tasks.fr</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="noindex,follow" />
-<meta name="date" content="1969-12-31T19:00:00-0500" />
-<meta name="keywords" content="geda,tasks.fr" />
-<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/geda:tasks.fr?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:tasks.fr"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:tasks.fr"; />
-<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>
-</body>
-</html>
diff --git a/docs/wiki/001geda_todos.html b/docs/wiki/001geda_todos.html
deleted file mode 100644
index 1116eff..0000000
--- a/docs/wiki/001geda_todos.html
+++ /dev/null
@@ -1,27 +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>geda:todos.fr</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="noindex,follow" />
-<meta name="date" content="1969-12-31T19:00:00-0500" />
-<meta name="keywords" content="geda,todos.fr" />
-<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/geda:todos.fr?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:todos.fr"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:todos.fr"; />
-<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>
-</body>
-</html>
diff --git a/docs/wiki/001geda_tragesym_tutorial.html b/docs/wiki/001geda_tragesym_tutorial.html
deleted file mode 100644
index c879619..0000000
--- a/docs/wiki/001geda_tragesym_tutorial.html
+++ /dev/null
@@ -1,270 +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>geda:tragesym_tutorial.fr</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="keywords" content="geda,tragesym_tutorial.fr" />
-<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/geda:tragesym_tutorial.fr?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:tragesym_tutorial.fr"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:tragesym_tutorial.fr"; />
-<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="#creer_des_symboles_gschem_rapidement_et_facilement_en_utilisant_tragesym_et_un_tableur" class="toc">Créer des symboles gschem rapidement et facilement en utilisant tragesym et un tableur</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#etapes_necessaires" class="toc">�tapes nécessaires</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#etape_1ouvrir_un_fichier_de_formulaire_tragesym" class="toc">Ã?tape 1: Ouvrir un fichier de formulaire tragesym</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#etape_2telecharger_le_fichier_technique_du_composant_et_trouver_la_liste_des_broches" class="toc">�tape 2: Télécharger le fichier technique du composant et trouver la liste des broches</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#etape_3copier_la_liste_des_broches_dans_un_editeur_et_la_preparer" class="toc">�tape 3: Copier la liste des broches dans un éditeur et la préparer</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#etape_4inserer_toutes_les_donnees_manquantes_dans_la_feuille_de_calcul" class="toc">�tape 4: Insérer toutes les données manquantes dans la feuille de calcul</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#etape_5exporter_la_feuille_de_calcul_dans_un_fichier_texte_avec_separation_par_tabulation" class="toc">�tape 5: Exporter la feuille de calcul dans un fichier texte avec séparation par tabulation</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#etape_6lancer_tragesym_et_creer_le_symbole" class="toc">�tape 6: Lancer tragesym et créer le symbole</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#etape_7controler_le_resultat_avec_gschem_et_peaufiner_le_symbole" class="toc">�tape 7: Contrôler le résultat avec gschem et peaufiner le symbole</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#conclusion" class="toc">Conclusion</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#credits" class="toc">Crédits</a></span></div></li></ul>
-</li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="creer_des_symboles_gschem_rapidement_et_facilement_en_utilisant_tragesym_et_un_tableur" id="creer_des_symboles_gschem_rapidement_et_facilement_en_utilisant_tragesym_et_un_tableur">Créer des symboles gschem rapidement et facilement en utilisant tragesym et un tableur</a></h1>
-<div class="level1">
-
-<p>
- La création de symboles pour le dessin de schémas peut prendre beaucoup de temps, générer beaucoup dâ??erreurs et de frustrations. Heureusement, gschem utilise un format de fichier texte ouvert qui est très facile à utiliser avec des scripts. Ce tutoriel succint décrit comment utiliser tragesym, un outil extérieur, pour créer des symboles très rapidement (probablement plus rapidement quâ??avec tout paquet commercial).
-</p>
-
-</div>
-<!-- SECTION "Créer des symboles gschem rapidement et facilement en utilisant tragesym et un tableur" [1-532] -->
-<h2><a name="etapes_necessaires" id="etapes_necessaires">�tapes nécessaires</a></h2>
-<div class="level2">
-<ul>
-<li class="level1"><div class="li"> Ã?tape 1: Ouvrir un fichier de formulaire tragesym</div>
-</li>
-<li class="level1"><div class="li"> �tape 2: Télécharger le fichier technique du composant et trouver la liste des broches</div>
-</li>
-<li class="level1"><div class="li"> �tape 3: Copier la liste des broches dans un éditeur et la préparer</div>
-</li>
-<li class="level1"><div class="li"> �tape 4: Insérer toutes les données manquantes dans la feuille de calcul</div>
-</li>
-<li class="level1"><div class="li"> �tape 5: Exporter la feuille de calcul dans un fichier texte avec séparation par tabulation</div>
-</li>
-<li class="level1"><div class="li"> �tape 6: Lancer tragesym et créer le symbole</div>
-</li>
-<li class="level1"><div class="li"> �tape 7: Contrôler le résultat avec gschem et peaufiner le symbole</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "�tapes nécessaires" [533-1094] -->
-<h2><a name="etape_1ouvrir_un_fichier_de_formulaire_tragesym" id="etape_1ouvrir_un_fichier_de_formulaire_tragesym">Ã?tape 1: Ouvrir un fichier de formulaire tragesym</a></h2>
-<div class="level2">
-
-<p>
- 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>
-<!-- SECTION "Ã?tape 1: Ouvrir un fichier de formulaire tragesym" [1095-1958] -->
-<h2><a name="etape_2telecharger_le_fichier_technique_du_composant_et_trouver_la_liste_des_broches" id="etape_2telecharger_le_fichier_technique_du_composant_et_trouver_la_liste_des_broches">�tape 2: Télécharger le fichier technique du composant et trouver la liste des broches</a></h2>
-<div class="level2">
-
-<p>
- Pour cet exemple, nous allons créer un symbole avec les ports IO du PCA9555 16-bit IIC IO de Philips Semiconductor. La description du produit et la fiche technique sont disponibles sur Philips : [<a href="http://www-us.semiconductors.philips.com/cgi-bin/pldb/pip/pca9555.html"; class="urlextern" title="http://www-us.semiconductors.philips.com/cgi-bin/pldb/pip/pca9555.html"; rel="nofollow">http://www-us.semiconductors.philips.com/cgi-bin/pldb/pip/pca9555.html</a>]. Téléchargez la fiche technique et ouvrez-la avec un visualiseur pdf qui permet la copie du texte à lâ??extérieur du <acronym title="Portable Document Format">PDF</acronym>, tel que xpdf (téléchargeable sur [<a href="http://www.foolabs.com/xpdf/home.html"; class="urlextern" title="http://www.foolabs.com/xpdf/home.html"; rel="nofollow">http://www.foolabs.com/xpdf/home.html</a>]). Passez les pages jusquâ??à ce que vous ayez trouvé le brochage ou le composant·:
-</p>
-
-<p>
-<a href="_detail/001tragesym_kpdf_pinconfiguration.html" class="media" title="tragesym:kpdf_pinconfiguration.png"><img src="http://geda.seul.org/wiki/_media/tragesym:kpdf_pinconfiguration.png?w=&h=&cache=cache"; class="media" alt="" /></a> <a href="_detail/001tragesym_acroread_selectiontable.html" class="media" title="tragesym:acroread_selectiontable.png"><img src="http://geda.seul.org/wiki/_media/tragesym:acroread_selectiontable.png?w=&h=&cache=cache"; class="media" alt="" /></a>
-</p>
-
-<p>
-Dans la feuille de calcul, la liste des broches peut être seulement présente dans le dessin du boîtier. Sâ??il existe une belle table, comme dans la second image, dâ??un autre fichie technique, utilisez-la.
-</p>
-
-</div>
-<!-- SECTION "�tape 2: Télécharger le fichier technique du composant et trouver la liste des broches" [1959-2906] -->
-<h2><a name="etape_3copier_la_liste_des_broches_dans_un_editeur_et_la_preparer" id="etape_3copier_la_liste_des_broches_dans_un_editeur_et_la_preparer">�tape 3: Copier la liste des broches dans un éditeur et la préparer</a></h2>
-<div class="level2">
-
-<p>
- Sélectionnez la liste des broches et copiez-la dans un éditeur de texte. Câ??est une étape intermédiaire nécessaire car votre tableur a besoin de champs séparateurs spéciaux, comme les virgules ou les tabulations. Vous pouvez avoir à enlever les séparateurs en double ou de les remplacer avec des tabulations.
-</p>
-
-<p>
-<strong>Note:</strong> Le comportement lors de la sélection de kpdf est différent de celui de acroread. kpdf semble vous donner une copie qui ressemble plus à une présentation graphique, alors que acroread fournit une sortie qui est plus «·orientée fichier·». Si vous devez créer beaucoup de symboles, testez les deux et comparez les résultats (NdT: xpdf semble fonctionner très bien au 04/12/2006 et reste très léger).
-</p>
-
-<p>
-<a href="_detail/001tragesym_xemacs_rawselection.html" class="media" title="tragesym:xemacs_rawselection.png"><img src="http://geda.seul.org/wiki/_media/tragesym:xemacs_rawselection.png?w=&h=&cache=cache"; class="media" alt="" /></a> <a href="_detail/001tragesym_xemacs_modifiedselection.html" class="media" title="tragesym:xemacs_modifiedselection.png"><img src="http://geda.seul.org/wiki/_media/tragesym:xemacs_modifiedselection.png?w=&h=&cache=cache"; class="media" alt="" /></a> <a href="_detail/001tragesym_ooo_selection.html" class="media" title="tragesym:ooo_selection.png"><img src="http://geda.seul.org/wiki/_media/tragesym:ooo_selection.png?w=&h=&cache=cache"; class="media" alt="" /></a>
-</p>
-
-<p>
-Lâ??image ci-dessus illustre les étapes·:
-</p>
-<ul>
-<li class="level1"><div class="li"> insérez la sélection depuis votre visualiseur pdf vers un éditeur de texte</div>
-</li>
-<li class="level1"><div class="li"> modifiez la liste des broches pour rendre votre tableur heureux </div>
-<ul>
-<li class="level2"><div class="li"> coupez la liste de 24 à 13 avec la sélection rectangulaire</div>
-</li>
-<li class="level2"><div class="li"> insérez la sélection rectangulaire sous les broches 1 à 12</div>
-</li>
-<li class="level2"><div class="li"> triez les lignes (xemacs peut le faire <img src="http://geda.seul.org/wiki/lib/images/smileys/icon_wink.gif"; class="middle" alt=";-)" />)</div>
-</li>
-<li class="level2"><div class="li"> enlevez ou réparez les lignes avec les numéros 2,3,… Ils ne sont pas sur la même ligne. Vous pouvez facilement recréer les numéros de broche plus tard</div>
-</li>
-<li class="level2"><div class="li"> remplacez les espaces avec des tabulations (pas réellement nécessaire en utilisant OpenOffice)</div>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"> copiez les données modifiées dans le formulaire feuille de calcul quelque part en dessous</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "�tape 3: Copier la liste des broches dans un éditeur et la préparer" [2907-4587] -->
-<h2><a name="etape_4inserer_toutes_les_donnees_manquantes_dans_la_feuille_de_calcul" id="etape_4inserer_toutes_les_donnees_manquantes_dans_la_feuille_de_calcul">�tape 4: Insérer toutes les données manquantes dans la feuille de calcul</a></h2>
-<div class="level2">
-
-<p>
- Déplacez maintenant les étiquettes et les numéros de broches dans leurs colonnes respectives. Vous pouvez aussi utiliser la fonctionnalité dâ??autoremplissage de votre tableur pour créer les numéros de broche.
-</p>
-
-<p>
-<a href="_detail/001tragesym_ooo_rearanged.html" class="media" title="tragesym:ooo_rearanged.png"><img src="http://geda.seul.org/wiki/_media/tragesym:ooo_rearanged.png?w=&h=&cache=cache"; class="media" alt="" /></a>
-</p>
-
-<p>
-Remplissez les colonens de type, de style et de position aux valeurs les plus habituelles. Vous pouvez à nouveau utiliser la fonctionnalité dâ??autoremplissage Maintenant vous allez changer quelques unes de ces valeurs. Jetez un coup dâ??oeil sur le tableau descriptif de la fiche technique:
-</p>
-
-<p>
-<a href="_detail/001tragesym_kpdf_pindescription.html" class="media" title="tragesym:kpdf_pindescription.png"><img src="http://geda.seul.org/wiki/_media/tragesym:kpdf_pindescription.png?w=&h=&cache=cache"; class="media" alt="" /></a>
-</p>
-
-<p>
-Selon ce tableau, nous changeons les éléments suivants (voir le résultat ci-dessus):
-</p>
-<ul>
-<li class="level1"><div class="li"> La broche 1 est une sortie, nous voudrions avoir un rond dâ??inversion (NdT: trad à revoir) et une barre de négation</div>
-</li>
-<li class="level1"><div class="li"> A1 à A3 sont des entrées, nous changeons le type et les déplaçons sur le côté gauche</div>
-</li>
-<li class="level1"><div class="li"> mettez le type de SCL en entrée et déplacez aussi SCL et SDA sur le côté gauche </div>
-</li>
-<li class="level1"><div class="li"> changez le type des broches dâ??alimentations VSS et VDD et ajoutez des noms de net. Nous utilisons les habituels GND et Vcc.</div>
-</li>
-</ul>
-
-<p>
- <strong>Note:</strong> Si une de vos étiquettes contient un backslash «·\·», vous devez le remplacer par sa séquence dâ??échapement «·\\·».
-</p>
-
-<p>
-<a href="_detail/001tragesym_ooo_changedpins.html" class="media" title="tragesym:ooo_changedpins.png"><img src="http://geda.seul.org/wiki/_media/tragesym:ooo_changedpins.png?w=&h=&cache=cache"; class="media" alt="" /></a>
-</p>
-
-<p>
-Avant de configurer les attributs et les options aux valeurs appropriées.
-</p>
-
-<p>
-<a href="_detail/001tragesym_ooo_attributes.html" class="media" title="tragesym:ooo_attributes.png"><img src="http://geda.seul.org/wiki/_media/tragesym:ooo_attributes.png?w=&h=&cache=cache"; class="media" alt="" /></a>
-</p>
-
-</div>
-<!-- SECTION "�tape 4: Insérer toutes les données manquantes dans la feuille de calcul" [4588-6061] -->
-<h2><a name="etape_5exporter_la_feuille_de_calcul_dans_un_fichier_texte_avec_separation_par_tabulation" id="etape_5exporter_la_feuille_de_calcul_dans_un_fichier_texte_avec_separation_par_tabulation">�tape 5: Exporter la feuille de calcul dans un fichier texte avec séparation par tabulation</a></h2>
-<div class="level2">
-
-<p>
- Vous pouvez soit utiliser le fonction export de votre tableur pour créer un fichier texte délimité par des tabulations ou simplement sélectionner le tableau et copier son contenu dans votre éditeur de texte et sauvegarder le fichier.
-</p>
-
-</div>
-<!-- SECTION "�tape 5: Exporter la feuille de calcul dans un fichier texte avec séparation par tabulation" [6062-6409] -->
-<h2><a name="etape_6lancer_tragesym_et_creer_le_symbole" id="etape_6lancer_tragesym_et_creer_le_symbole">�tape 6: Lancer tragesym et créer le symbole</a></h2>
-<div class="level2">
-
-<p>
- Utilisez un shell et exécutez tragesym:
-</p>
-
-<p>
-<code>werner@werner-amd64:~/Desktop/tragesym_tutorial> tragesym pca555.src pca555.sch</code>
-</p>
-
-<p>
-Si tragesym indique quâ??il y a une erreur, faites quelques changements dans la feuille de calcul et exportez à nouveau le fichier ou éditez simplement le fichier exporté.
-</p>
-
-</div>
-<!-- SECTION "�tape 6: Lancer tragesym et créer le symbole" [6410-6771] -->
-<h2><a name="etape_7controler_le_resultat_avec_gschem_et_peaufiner_le_symbole" id="etape_7controler_le_resultat_avec_gschem_et_peaufiner_le_symbole">�tape 7: Contrôler le résultat avec gschem et peaufiner le symbole</a></h2>
-<div class="level2">
-
-<p>
- Ouvrez maintenant le symbole généré avec et contrôlez le résultat
-</p>
-
-<p>
-<code>werner@werner-amd64:~/Desktop/tragesym_tutorial> gschem pca555.sch</code>
-</p>
-
-<p>
-En validant le texte caché («·en·», Edit→Show/Hide Inv Text), vous pouvez voir le symbole généré en entier. Il nâ??est pas réellement nécessaire de changer quoi que ce soit mais cela peut améliorer lâ??aspect du symbole si vous réarrangez un peu les broches.
-</p>
-
-<p>
-<a href="_detail/001tragesym_gschem_showhidden.html" class="media" title="tragesym:gschem_showhidden.png"><img src="http://geda.seul.org/wiki/_media/tragesym:gschem_showhidden.png?w=&h=&cache=cache"; class="media" alt="" /></a> <a href="_detail/001tragesym_gschem_finished.html" class="media" title="tragesym:gschem_finished.png"><img src="http://geda.seul.org/wiki/_media/tragesym:gschem_finished.png?w=&h=&cache=cache"; class="media" alt="" /></a>
-</p>
-
-<p>
-Nous avons maintenant un symbole complet. Vous pouvez le copier dans votre bibliothèque locale de symboles, e.g. /usr/local/share/gEDA/sym/local/ et lâ??utiliser.
-</p>
-
-</div>
-<!-- SECTION "�tape 7: Contrôler le résultat avec gschem et peaufiner le symbole" [6772-7503] -->
-<h2><a name="conclusion" id="conclusion">Conclusion</a></h2>
-<div class="level2">
-
-<p>
- Câ??était un exemple simple avec peu de broches mais cela est dâ??autant plus rentable lorsque vous en avez beaucoup (ie, bga-272, tfqp-100, etc.).
-</p>
-
-</div>
-<!-- SECTION "Conclusion" [7504-7673] -->
-<h2><a name="credits" id="credits">Crédits</a></h2>
-<div class="level2">
-
-<p>
- De grands remerciements à <Russ.Dill(AT)asu.edu>, qui a écrti la première version de ce tutoriel. Vous pouvez trouver ce tutoriel sur <a href="http://www.geda.seul.org/docs/current/tutorials/tragesym/tragesym.html"; class="urlextern" title="http://www.geda.seul.org/docs/current/tutorials/tragesym/tragesym.html"; rel="nofollow">http://www.geda.seul.org/docs/current/tutorials/tragesym/tragesym.html</a> (version anglaise)
-</p>
-
-<p>
-NdT·: si vous voulez la version française: <a href="http://www.iznogood-factory.org/pub/gEDA/symboles.html"; class="urlextern" title="http://www.iznogood-factory.org/pub/gEDA/symboles.html"; rel="nofollow">http://www.iznogood-factory.org/pub/gEDA/symboles.html</a>
-</p>
-
-</div>
-<!-- SECTION "Crédits" [7674-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/001geda_usage.html b/docs/wiki/001geda_usage.html
deleted file mode 100644
index 51eb5d7..0000000
--- a/docs/wiki/001geda_usage.html
+++ /dev/null
@@ -1,246 +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>geda:usage.fr</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-06-27T07:34:07-0400" />
-<meta name="keywords" content="geda,usage.fr" />
-<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/geda:usage.fr?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:usage.fr"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:usage.fr"; />
-<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="#quelle_est_la_meilleure_maniere_d_apprendre_a_utiliser_geda" class="toc">Quelle est la meilleure manière d'apprendre à utiliser gEDA?</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#a_quoi_ressemble_de_le_flux_de_conception_de_geda" class="toc">Ã? quoi ressemble de le flux de conception de gEDA?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#quelles_sont_les_limitations_pour_les_outils_geda" class="toc">Quelles sont les limitations pour les outils gEDA?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#quels_fichiers_de_configuration_locaux_sont_utilises_pour_un_projet" class="toc">Quels fichiers de configuration locaux sont utilisés pour un projet?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#quels_sont_les_noms_et_les_emplacements_des_fichiers_rc_utilises_avec_les_applications_geda_gaf" class="toc">Quels sont les noms et les emplacements des fichiers RC utilisés avec les applications gEDA/gaf?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#qu_en_est-il_du_gestionnaire_de_projet" class="toc">Qu'en est-il du gestionnaire de projet?</a></span></div></li></ul>
-</li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="quelle_est_la_meilleure_maniere_d_apprendre_a_utiliser_geda" id="quelle_est_la_meilleure_maniere_d_apprendre_a_utiliser_geda">Quelle est la meilleure manière d'apprendre à utiliser gEDA?</a></h1>
-<div class="level1">
-
-<p>
-La première chose à faire est de lire et comprendre lâ??excellent <a href="http://geda.seul.org/wiki/geda:gsch2pcb_tutorial"; class="wikilink1" title="geda:gsch2pcb_tutorial">gschem -> gsch2pcb -> PCB</a> tutoriel de Bill Wilson. Cela devrait vous permettre de débuter.
-</p>
-
-<p>
-Allez aussi voir les autres <a href="http://geda.seul.org/docs"; class="urlextern" title="http://geda.seul.org/docs"; rel="nofollow">documentations gEDA</a> disponible sur ce site.
-</p>
-
-<p>
-Néanmoins, peut être que la meilleure voie pour apprendre la suite gEDA est de le télécharger et de lâ??essayer vous-même! Si vous consultez le <a href="http://geda.seul.org/docs/current/tutorials/gsch2pcb/tutorial.html"; class="urlextern" title="http://geda.seul.org/docs/current/tutorials/gsch2pcb/tutorial.html"; rel="nofollow">tutoriel</a> de Bill Wilson en essayant la Suite pour vous-même, vous deviendrez un expert en peu de temps!
-</p>
-
-</div>
-<!-- SECTION "Quelle est la meilleure manière d'apprendre à utiliser gEDA?" [1-690] -->
-<h2><a name="a_quoi_ressemble_de_le_flux_de_conception_de_geda" id="a_quoi_ressemble_de_le_flux_de_conception_de_geda">Ã? quoi ressemble de le flux de conception de gEDA?</a></h2>
-<div class="level2">
-
-<p>
-Vous avez ici un schéma de synthèse pour un flux de création de PCB en utilisant la Suite gEDA:
-</p>
-
-<p>
-<a href="_detail/001geda_design_flow.html" class="media" title="geda:design_flow.jpg"><img src="http://geda.seul.org/wiki/_media/geda:design_flow.jpg?w=&h=&cache=cache"; class="media" title="design_flow.jpg" alt="design_flow.jpg" /></a>
-</p>
-
-<p>
-Mis en mots, le flux de conception pour un PCB simple se fait de la manière suivante:
-</p>
-<ol>
-<li class="level1"><div class="li"> Créez vos schémas en utilisant « gschem ».</div>
-</li>
-<li class="level1"><div class="li"> Contrôlez vos schémas avec le vérificateur de DRC. Vous pouvez apprendre à le maîtriser <a href="http://geda.seul.org/wiki/geda:faq-attribs#how_do_i_check_my_schematics"; class="wikilink1" title="geda:faq-attribs">ici</a>.</div>
-</li>
-<li class="level1"><div class="li"> Assigner des références à vos composants en utilisant « grenum » ou « refdes_renum » (ou simplement les attacher depuis « gschem »).</div>
-</li>
-<li class="level1"><div class="li"> Assignez dâ??autres attributs de composants (tels que des empreintes) en utilisant « gattrib » (ou attachez les simplement manuellement en utilisant « gschem »).</div>
-</li>
-<li class="level1"><div class="li"> Créez un fichier préliminaire de synthèse et faites une netlist en utilisant « gsch2pcb ».</div>
-</li>
-<li class="level1"><div class="li"> Disposez les composants et routez les connexions de votre carte en utilisant « pcb ».</div>
-</li>
-<li class="level1"><div class="li"> Sortez les Gerbers depuis « pcb » en utilisant « File â??Print layout » et sélectionnez « Gerber/RS274X » comme type de fichier de sortie.</div>
-</li>
-</ol>
-
-<p>
- Si vous faites des changements ou des ajouts à votre schéma ou des attributs, mettez votre fichier PCB comme ceci:
-</p>
-<ol>
-<li class="level1"><div class="li"> �ditez votre schéma et/ou les attributs (« gschem » ou « gattrib »).</div>
-</li>
-<li class="level1"><div class="li"> Contrôlez votre schéma avec le contrôleur de DRC. Vous pouvez apprendre à le maîtriser <a href="http://geda.seul.org/wiki/geda:faq-attribs#how_do_i_check_my_schematics"; class="wikilink1" title="geda:faq-attribs">ici</a>.</div>
-</li>
-<li class="level1"><div class="li"> Annotez directement vos changements en utilisant « gsch2pcb ».</div>
-</li>
-<li class="level1"><div class="li"> Depuis « pcb », mettez à jour vos composants en utilisant « File â??Load layout data to paste buffer » puis cliquez sur la zone de dessin pour placer les composants.</div>
-</li>
-<li class="level1"><div class="li"> Depuis « pcb », mettez à jour votre netlist en utilisant « File â??Load netlist file ».</div>
-</li>
-</ol>
-
-<p>
- Habituellement, les utilisateurs invoquent les outils individuels depuis la ligne de commande. Un gestionnaire de projet (« geda ») existe mais a besoin dâ??être amélioré.
-</p>
-
-</div>
-<!-- SECTION "Ã? quoi ressemble de le flux de conception de gEDA?" [691-2693] -->
-<h2><a name="quelles_sont_les_limitations_pour_les_outils_geda" id="quelles_sont_les_limitations_pour_les_outils_geda">Quelles sont les limitations pour les outils gEDA?</a></h2>
-<div class="level2">
-
-<p>
-La chose la plus importante à garder en mémoire à propos des limitations de gEDA est ceci: GEDA est un projet de logiciel open-source. Il possède quelques limitations mais contrairement à celles des logiciels commerciaux, ses limitations ne sont pas artificielles, arbitraires ou pilotées par le marketing. Ceci étant, gEDA nâ??est ni un nagware, ni un crippleware, ni un demoware, ni une « version étudiante limitée ». Toutes les limitations des outils gEDA existent car les programmeurs nâ??ont pas encore implementé ces fonctionnalités particulières. Comme le code est ouvert à tous pour la modification, tout le monde est le bienvenu sâ??il veut implémenter de nouvelles fonctionnalités ou supprimer des limitations puis de soumettre leurs patches au projet. Si vous êtes un hacker et que vous êtes intéressés pour une contribution au projet gEDA, veuillez considérer effacer une des limitations listée ci-dessous! Vous vous ferez un tas dâ??amis et gagnerez une notoriété internationale!
-</p>
-<ul>
-<li class="level1"><div class="li"> Le support hiérarchique de bus: Le support pour les bus hiérarchiques nâ??existe pas encore.</div>
-</li>
-<li class="level1"><div class="li"> Les attributs de nets et de broches dans gattrib: Lâ??attachement des attributs de routage pour les nets et les broches dans gattrib reste à faire. (Les attributs de net sont utiles pour les schémas à haute vitesse. Par exemple, il est souvent important que toutes les pistes dâ??un bus aient la même longueur électrique. Malheureusement, il nâ??est pas certain que PCB supprte actuellement ces attributs de routage.)</div>
-</li>
-<li class="level1"><div class="li"> La rétro-annotation depuis PCB vers gschem. Le support pour la permutation de broche et les modifications du fichier de conception de pcb avec les rétro-annotations induites vers gschem reste à faire.</div>
-</li>
-<li class="level1"><div class="li"> Le gestionnaire de projet « geda » est obsolète et nécessite une mise à jour.</div>
-</li>
-<li class="level1"><div class="li"> Le nombre de couches dans PCB: Actuellement, le nombre de couche de PCB est limité à 8 (ce qui est plus que adéquat pour les projets de petite et moyenne taille). Les développeurs de PCB travaillent sur lâ??augmentation du nombre de couches vers un nombre indéfini mais ce nâ??est pas encore fait. Contactez-les directement si vous êtes intéressés par ce projet.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Quelles sont les limitations pour les outils gEDA?" [2694-4952] -->
-<h2><a name="quels_fichiers_de_configuration_locaux_sont_utilises_pour_un_projet" id="quels_fichiers_de_configuration_locaux_sont_utilises_pour_un_projet">Quels fichiers de configuration locaux sont utilisés pour un projet?</a></h2>
-<div class="level2">
-
-<p>
-Une conception typique de PCB nécessite les fichiers de config suivants dans votre répertoire local:
-</p>
-<ul>
-<li class="level1"><div class="li"> gafrc: il contient les infos de configuration pour les programmes gEDA/gaf (i.e. gschem, gattrib, gnetlist, etc.). Il doit contenir des pointeurs de votre répertoire de symbole local (si vous en avez).</div>
-</li>
-<li class="level1"><div class="li"> attribs: si vous utilisez « gnetlist -g bom2 » pour créer un projet BOM (« Bill Of Material »: liste des éléments) puis vous avez besoin de ce fichier de manière à spéficier quels attributs sont écrits dans la BOM.</div>
-</li>
-<li class="level1"><div class="li"> projectrc: lorsque vous faites un pcb, « gsch2pcb projectrc » est une manière pratique de spécifier les chemins aux répertoires locaux dâ??empreintes, de même que les autres informations de configuration pour « gsch2pcb ». Notez que ce ficheir peut avoir tout nom que vous lui choisissez; jâ??aime utiliser projectrc comme son nom est suggestif de sa fonction.</div>
-</li>
-</ul>
-
-<p>
- Des informations plus détaillées à propos de chaque fichier de configuration est fourni dans la <a href="http://geda.seul.org/docs/index.html"; class="urlextern" title="http://geda.seul.org/docs/index.html"; rel="nofollow">documentation</a> pour chaque élément.
-</p>
-
-</div>
-<!-- SECTION "Quels fichiers de configuration locaux sont utilisés pour un projet?" [4953-6122] -->
-<h2><a name="quels_sont_les_noms_et_les_emplacements_des_fichiers_rc_utilises_avec_les_applications_geda_gaf" id="quels_sont_les_noms_et_les_emplacements_des_fichiers_rc_utilises_avec_les_applications_geda_gaf">Quels sont les noms et les emplacements des fichiers RC utilisés avec les applications gEDA/gaf?</a></h2>
-<div class="level2">
-
-<p>
-Les diverses applications gEDA/gaf (gschem, gattrib, gnetlist, etc.) utilisent un jeu de fichiers RC pour initialiser différentes options configurables dans les outils eux-mêmes. Ces fichiers RC sont lus par chaque application lors de leur démarrage. Philosophiquement, il existe trois endroits où une application gEDA/gaf va chercher des fichiers RC:
-</p>
-<ul>
-<li class="level1"><div class="li"> Dans le répertoire dâ??installation du système: <strong><code>${prefix}/share/gEDA/</code></strong>. Cet endroit contient les fichiers RC globaux du système et à tous les utilisateurs. Ces fichiers RC doivent être trouvés et chargés avec succès pour que les applications gEDA fonctionnent correctement. <strong><code>${prefix}</code></strong> est initialisé avec le chemin où gEDA/gaf est installé.</div>
-</li>
-<li class="level1"><div class="li"> Dans le répertoire utilisateur: <strong><code>$HOME/.gEDA/</code></strong>. Cet endroit garde les fichiers RC qui sâ??appliquent à tous les projets dâ??utilisateurs. <strong><code>.gEDA</code></strong> est un répertoire. Ces fichiers sont optionels. Ne faites pas que placer une copie du system-gschemrc (ou un autre) dans ce répertoire; ceci ne fonctionnera pas correctement. La bonne chose à faire est de dépasser les choses spécifiques que vous voulez changer.</div>
-</li>
-<li class="level1"><div class="li"> Dans le répertoire local du projet. Cet endroit contient les fichiers RC qui sâ??appliquent au projet local (placé dans ce même répertoire). Ces fichiers RC fournissent des dépassements spécifiques, tels que des bibliothèques de composants ou de sources. Ce fichier est aussi optionel. Ne faites pas que placer une copie de system-gschemrc (ou un autre) dans ce répertoire; il ne fonctionnera pas correctement.</div>
-</li>
-</ul>
-
-<p>
- Le système de fichier RC a évolué au fil du temps. Originellement, chaque application gEDA/gaf a utilisé ses propres fichiers RC (par exemple, gschem utilise gschemrc, gnetlist utilise gnetlistrc et ainsi de suite). Nénmoins, avec lâ??augmentation du nombre des applications gEDA/gaf, il est devenu clair que les fichiers RC individuels contenaient un lot dâ??informations redondantes et que les nouveaux utilisateurs étaient perturbés par les différents fichiers RC. Câ??est la raison pour laquelle les différents fichiers RC ont été compactés en un seul fichier, appelé « gafrc ». Néanmoins, comme gschem a besoin de tous les types de personalisations spéciaux, nous avons décidé de garder le gschemrc système en plus de tous les fichiers gafrc. Aussi, de manière à préserver une compatibilité arrière, lâ??ancien fichier RC système est encore maintenu dans le répertoire système. En conséquence, le fichier de configuration RC actuel ressemble à ceci:
-</p>
-<ul>
-<li class="level1"><div class="li"> Dans le répertoire dâ??installation du système:</div>
-<ul>
-<li class="level2"><div class="li"> <strong><code>system-gafrc</code></strong> â?? Il contient la plupart des initialisations globales de gaf.</div>
-</li>
-<li class="level2"><div class="li"> <strong><code>system-gattribrc</code></strong></div>
-</li>
-<li class="level2"><div class="li"> <strong><code>system-gnetlistrc</code></strong></div>
-</li>
-<li class="level2"><div class="li"> <strong><code>system-gschemrc</code></strong> â?? Il contient de nombreuses configurations spécifiques à gschem</div>
-</li>
-<li class="level2"><div class="li"> <strong><code>system-gschlasrc</code></strong></div>
-</li>
-<li class="level2"><div class="li"> <strong><code>system-gsymcheckrc</code></strong></div>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"> Dans le répertoire <strong><code>${HOME}</code></strong> de lâ??utilisateur:</div>
-<ul>
-<li class="level2"><div class="li"> <strong><code>.gEDA/gafrc</code></strong></div>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"> Dans le répertoire local du projet:</div>
-<ul>
-<li class="level2"><div class="li"> <strong><code>gafrc</code></strong> â?? Il devrait contenir les dépassements locaux, tels que les pointeurs vers les symboles localement définis.</div>
-</li>
-</ul>
-</li>
-</ul>
-
-<p>
- Les définitions de couleurs gschem-darkbg ou gschem-lightbg sont aussi chargées par le system-gschemrc.
-</p>
-
-<p>
-Finalement, notez que les applications gEDA/gaf recherchent jusquâ??à six fichiers de configuration au démarrage:
-</p>
-<ol>
-<li class="level1"><div class="li"> <strong><code>system-gafrc</code></strong></div>
-</li>
-<li class="level1"><div class="li"> <strong><code>system-gschemrc</code></strong> (ou un autre)</div>
-</li>
-<li class="level1"><div class="li"> <strong><code>${HOME}/.geda/gafrc</code></strong></div>
-</li>
-<li class="level1"><div class="li"> <strong><code>${HOME}/.geda/gschemrc</code></strong> (ou un autre)</div>
-</li>
-<li class="level1"><div class="li"> <strong><code>./gafrc</code></strong></div>
-</li>
-<li class="level1"><div class="li"> <strong><code>./gschemrc</code></strong> (ou un autre)</div>
-</li>
-</ol>
-
-<p>
- Si vous obtenez un avertissement comme quoi votre application ne peut pas trouver lâ??un ou lâ??autre de ces fichiers, ne vous inquiétez pas. La plupart dâ??entre eux sont optionels. Les seuls fichiers nécessaires sont les fichiers RC systèmes.
-</p>
-
-</div>
-<!-- SECTION "Quels sont les noms et les emplacements des fichiers RC utilisés avec les applications gEDA/gaf?" [6123-10078] -->
-<h2><a name="qu_en_est-il_du_gestionnaire_de_projet" id="qu_en_est-il_du_gestionnaire_de_projet">Qu'en est-il du gestionnaire de projet?</a></h2>
-<div class="level2">
-
-<p>
-Les composants individuels dans la suite de conception de gEDA ne forment pas un projet de bout en bout. A la place, ils traitent leurs propres fichiers (i.e. « gschem » â?? .sch, « pcb » â?? .pcb). Néanmoins, il existe un gestionnaire de projet appelé « geda », que vous pouvez invoquer depuis le ligne de commande. Son but est de vous faciliter la gestion de votre idée comme un tout depuis le concept, en passant par la saisie de schéma, lâ??attachement dâ??attributs, le placement, la génération de BOM, ainsi de suite.
-</p>
-
-<p>
-Malheureusement, le développement de « geda » nâ??a pas suivi le reste de gEDA/gaf. En particulier, « geda » nâ??utilise pas les derniers outils ou méthodes pour réaliser les tâches individuelles. Câ??est la raison pour laquelle nous recommandons aux utilisateurs dâ??utiliser les outils individuels (i.e. gschem, gattrib, gnetlist, gsch2pcb, etc) depuis la ligne de commande. Câ??est pourquoi, si vous êtes un hacker à la recherche dâ??un petit projet à adopter, améliorer « geda » serait une belle introduction à la Suite gEDA et vous vous feriez un tas dâ??amis en le faisant!
-</p>
-
-</div>
-<!-- SECTION "Qu'en est-il du gestionnaire de projet?" [10079-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/Makefile.am b/docs/wiki/Makefile.am
index fa8d427..5aff050 100644
--- a/docs/wiki/Makefile.am
+++ b/docs/wiki/Makefile.am
@@ -1,11 +1,10 @@
-
docname=wiki
docsdir = $(docdir)/$(docname)/
-SUBDIRS = _media _detail lib
+SUBDIRS = images media
-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 geda_gschem_mp.html gerbv-projects.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_release_engineering.html geda_guile_scripting.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_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 gsoc2007.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 gsoc2008.html 001geda_installation.html geda_gtkwave_vcd2lxt_mp.html start_fr.html gsoc2007_projects.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 glue-projects.html geda_debian.html geda_gtkwave_mvl2vcd_mp.html geda_installed_plugins.html geda_example_hsm.html geda_gtkwave_vzt2vcd_mp.html gsoc2008_projects.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_ngspice_and_gschem.html geda_vhdl_netlister_readme.html docs_20060124_gschem_ug_resources.html gwave-projects.html geda_faq-gsch2pcb.html geda_glossary.html geda_gsch2pcb_readme.html best_practices.html geda_fedora_rpm_installation.html geda_covered_mp.html geda_master_attributes_list.html geda_icarus_vvp_simulation.html pcb-projects.html 001geda_todos.html geda_todos.html docs_20060124_gschem_ug_the_main_window.html geda_ssan.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 gschem-projects.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
+docs_DATA = geda-gtkwave_tex2vcd_mp.html geda-na_howto.html geda-wip-clipboard.html geda-icarus_vpi_mp.html geda-debian.html geda-grcsan.html geda-devmacosx.html geda-mcalc_readme.html geda-format_translation.html geda-scg.html gerbv-projects.html geda-csygas.html geda-todos_historical.html geda-icarus_extensions.html libgeda3_object_based_design.html playground-transistor_guide.html geda-igarus_fpga_lcg.html geda-icarus_xnf.html playground-playground.html geda-icarus_vvp_runtime.html geda-gschem_ug.fr.html geda-faq-attribs.fr.html geda-wcalc_readme.html geda-gsch2pcb_tutorial.html geda-gtkwave_vcd2lxt2_mp.html geda-pcb_funding_sow.html geda-bom_readme.html geda-design_flow_roadmap.html geda-gerbv_pnp_readme.html geda-faq-attribs.html geda-fbabgapp.html geda-faq-simulation.fr.html geda-gtkwave_vztminer_mp.html geda-documentation.html geda-scm.html geda-icarus_ieee1364.html geda-pcb-quick_reference.html geda-pcb-quick_reference.fr.html index.html geda-sn_readme.html geda-faq-gnetlist.html geda-documentation.fr.html geda-eagle_pcb_netlister_readme.html geda-faq.fr.html geda-tragesym_tutorial.fr.html geda-faq-gnetlist.fr.html geda-example_usbjtag.html geda-suse_10.1.html start_es.html geda-todos.html geda-icarus_opcodes.html geda-gschem_warmup.html geda-suse_rpm_installation.html geda-pcb_tips.fr.html geda-gtkwave_mvl2lxt_mp.html style.css geda-cygwin.html gsoc2007.html geda-gfdl.html geda-gtkwave_vcd2lxt_mp.html geda-start.html geda-pcb_funding_sow-gui_ideas.html geda-ngspice_mp.html geda-ssan.html geda-faq.html geda-faq-gsch2pcb.fr.html geda-gattrib_readme.html geda-gschem2pcb_readme.html geda-xml_file_formats.html geda-example_hsm.html geda-ngsconvert_mp.html gsoc2008.html geda-glossary.fr.html geda-grenum_mp.html geda-tragesym_readme.html geda-icarus_readme.html geda-icarus_anc.html geda-gtkwave_mp.html start.html geda-ngspice_and_gschem.html start_fr.html geda-file_format_spec.html geda-data_structure_design_discussion.html geda-installation.html geda-wcalc_stdio_mp.html geda-gschem_mp.html geda-pcb_mp.html gsoc2007_projects.html gsoc2009_projects.html geda-hse_howto.html geda-icarus_quick_start.html geda-style_guide.html geda-circuit_simulation_improvements.html geda-pcb_footprints.html geda-ubuntu.html geda-fedora_rpm_installation.html glue-projects.html geda-spice_improvements.html print.css geda-gtkwave_mvl2vcd_mp.html geda-glossary.html geda-data_plotting_improvements.html geda-wcalc_mp.html geda-gnetlist_ug.html gsoc2008_projects.html geda-usage.fr.html geda-gtkwave_lxt2miner_mp.html geda-faq-simulation.html geda-suse_10.0.html gwave-projects.html geda-gsch2pcb_tutorial_releasenotes.html geda-usage.html best_practices.html geda-installed_plugins.html geda-glossaire.fr.html pcb-projects.html geda-covered_mp.html geda-icarus_glossary.html geda-pcb_tips.html geda-debian.fr.html geda-gsymcheck_mp.html gschem-projects.html geda-syntax_features.html libgeda3.html design.css geda-fc3.html geda-ngnutmeg_mp.html gtkwave-projects.html geda-gtkwave_lxt2vcd_mp.html geda-gnetlist_mp.html geda-gtkwave_vzt2vcd_mp.html geda-devel-tips.html geda-gtkwave_tla2vcd_mp.html geda-guile_scripting.html geda-olib_readme.html geda-gerbv_mp.html geda-master_attributes_list.html geda-kig_howto.html geda-version_control_migration.html geda-fc1.html geda-gsch2pcb_readme.html geda-design_flow_and_hierarchy_roadmap.html geda-faq-gschem.fr.html geda-gschem_ug.html geda-fc2.html geda-icarus_xilinx_hints.html geda-transistor_guide.html geda-verilog_netlister_readme.html geda-icarus_vpi_within_vvp.html wiki-syntax.html geda-scg.fr.html geda-faq-gsch2pcb.html wiki-dokuwiki.html geda-tragesym_tutorial.html geda-gedasuite_installation.html geda-faq-gschem.html geda-release_engineering.html geda-experiences.html geda-fc4.html gsoc2009.html geda-systemc_netlister_readme.html geda-pcb_funding_sow-fwdann_ideas.html geda-faq-pcb.html geda-installation.fr.html geda-icarus_vvp_simulation.html geda-vhdl_netlister_readme.html geda-gtkwave_vcd2vzt_mp.html geda-tasks.html geda-suse_9.3.html geda-sdb_howto.html geda-vams_netlister_readme.html geda-icarus_mp.html
EXTRA_DIST = $(docs_DATA)
diff --git a/docs/wiki/_detail/.gitignore b/docs/wiki/_detail/.gitignore
deleted file mode 100644
index 23c1897..0000000
--- a/docs/wiki/_detail/.gitignore
+++ /dev/null
@@ -1,3 +0,0 @@
-Makefile
-Makefile.in
-*~
diff --git a/docs/wiki/_detail/001geda_ambiguous1.html b/docs/wiki/_detail/001geda_ambiguous1.html
deleted file mode 100644
index 5bc85ec..0000000
--- a/docs/wiki/_detail/001geda_ambiguous1.html
+++ /dev/null
@@ -1,50 +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>
- geda:ambiguous1.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:faq-gnetlist.fr?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:faq-gnetlist.fr"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:faq-gnetlist.fr"; />
-<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" />
-
- <link rel="shortcut icon" href="http://geda.seul.org/wiki/lib/tpl/geda/images/favicon.ico"; />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:ambiguous1.png</h1>
-
- <div class="img_big">
- <a href="http://geda.seul.org/wiki/_media/geda:ambiguous1.png?cache=cache";><img src="http://geda.seul.org/wiki/_media/geda:ambiguous1.png?cache=cache&w=707&h=492"; width="707" height="492" class="img_detail" alt="ambiguous1.png" title="ambiguous1.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:faq-gnetlist.fr"; class="wikilink1" title="geda:faq-gnetlist.fr">faq-gnetlist.fr</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>ambiguous1.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>6KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/001geda_ambiguous1_fixed.html b/docs/wiki/_detail/001geda_ambiguous1_fixed.html
deleted file mode 100644
index d2170be..0000000
--- a/docs/wiki/_detail/001geda_ambiguous1_fixed.html
+++ /dev/null
@@ -1,50 +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>
- geda:ambiguous1_fixed.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:faq-gnetlist.fr?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:faq-gnetlist.fr"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:faq-gnetlist.fr"; />
-<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" />
-
- <link rel="shortcut icon" href="http://geda.seul.org/wiki/lib/tpl/geda/images/favicon.ico"; />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:ambiguous1_fixed.png</h1>
-
- <div class="img_big">
- <a href="http://geda.seul.org/wiki/_media/geda:ambiguous1_fixed.png?cache=cache";><img src="http://geda.seul.org/wiki/_media/geda:ambiguous1_fixed.png?cache=cache&w=754&h=506"; width="754" height="506" class="img_detail" alt="ambiguous1_fixed.png" title="ambiguous1_fixed.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:faq-gnetlist.fr"; class="wikilink1" title="geda:faq-gnetlist.fr">faq-gnetlist.fr</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>ambiguous1_fixed.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>5KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/001geda_design_flow.html b/docs/wiki/_detail/001geda_design_flow.html
deleted file mode 100644
index 8af064f..0000000
--- a/docs/wiki/_detail/001geda_design_flow.html
+++ /dev/null
@@ -1,50 +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>
- geda:design_flow.jpg [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:usage.fr?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:usage.fr"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:usage.fr"; />
-<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" />
-
- <link rel="shortcut icon" href="http://geda.seul.org/wiki/lib/tpl/geda/images/favicon.ico"; />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:design_flow.jpg</h1>
-
- <div class="img_big">
- <a href="http://geda.seul.org/wiki/_media/geda:design_flow.jpg?cache=cache";><img src="http://geda.seul.org/wiki/_media/geda:design_flow.jpg?cache=cache&w=398&h=414"; width="398" height="414" class="img_detail" alt="design_flow.jpg" title="design_flow.jpg" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:usage.fr"; class="wikilink1" title="geda:usage.fr">usage.fr</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>design_flow.jpg</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>4KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/001geda_faq_attrib.html b/docs/wiki/_detail/001geda_faq_attrib.html
deleted file mode 100644
index b2bb84d..0000000
--- a/docs/wiki/_detail/001geda_faq_attrib.html
+++ /dev/null
@@ -1,50 +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>
- geda:faq_attrib.jpg [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:faq-attribs.fr?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:faq-attribs.fr"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:faq-attribs.fr"; />
-<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" />
-
- <link rel="shortcut icon" href="http://geda.seul.org/wiki/lib/tpl/geda/images/favicon.ico"; />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:faq_attrib.jpg</h1>
-
- <div class="img_big">
- <a href="http://geda.seul.org/wiki/_media/geda:faq_attrib.jpg?cache=cache";><img src="http://geda.seul.org/wiki/_media/geda:faq_attrib.jpg?cache=cache&w=756&h=623"; width="756" height="623" class="img_detail" alt="faq_attrib.jpg" title="faq_attrib.jpg" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:faq-attribs.fr"; class="wikilink1" title="geda:faq-attribs.fr">faq-attribs.fr</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>faq_attrib.jpg</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>25KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/001geda_gschem_screenshot_001.html b/docs/wiki/_detail/001geda_gschem_screenshot_001.html
deleted file mode 100644
index d2ab7ab..0000000
--- a/docs/wiki/_detail/001geda_gschem_screenshot_001.html
+++ /dev/null
@@ -1,50 +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>
- geda:gschem_screenshot_001.jpg [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:gschem_ug.fr?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gschem_ug.fr"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gschem_ug.fr"; />
-<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" />
-
- <link rel="shortcut icon" href="http://geda.seul.org/wiki/lib/tpl/geda/images/favicon.ico"; />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:gschem_screenshot_001.jpg</h1>
-
- <div class="img_big">
- <a href="http://geda.seul.org/wiki/_media/geda:gschem_screenshot_001.jpg?cache=cache";><img src="http://geda.seul.org/wiki/_media/geda:gschem_screenshot_001.jpg?cache=cache&w=695&h=598"; width="695" height="598" class="img_detail" alt="gschem_screenshot_001.jpg" title="gschem_screenshot_001.jpg" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:gschem_ug.fr"; class="wikilink1" title="geda:gschem_ug.fr">gschem_ug.fr</a></span></p>
-
- <dl class="img_tags">
- <dt>Date:</dt><dd>2007/05/24 22:27</dd><dt>Filename:</dt><dd>gschem_screenshot_001.jpg</dd><dt>Format:</dt><dd>JPEG</dd><dt>Size:</dt><dd>36KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/001geda_gschem_workflow_01.html b/docs/wiki/_detail/001geda_gschem_workflow_01.html
deleted file mode 100644
index 6389a6c..0000000
--- a/docs/wiki/_detail/001geda_gschem_workflow_01.html
+++ /dev/null
@@ -1,50 +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>
- geda:gschem_workflow_01.jpg [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:gschem_ug.fr?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gschem_ug.fr"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gschem_ug.fr"; />
-<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" />
-
- <link rel="shortcut icon" href="http://geda.seul.org/wiki/lib/tpl/geda/images/favicon.ico"; />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:gschem_workflow_01.jpg</h1>
-
- <div class="img_big">
- <a href="http://geda.seul.org/wiki/_media/geda:gschem_workflow_01.jpg?cache=cache";><img src="http://geda.seul.org/wiki/_media/geda:gschem_workflow_01.jpg?cache=cache&w=532&h=389"; width="532" height="389" class="img_detail" alt="gschem_workflow_01.jpg" title="gschem_workflow_01.jpg" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:gschem_ug.fr"; class="wikilink1" title="geda:gschem_ug.fr">gschem_ug.fr</a></span></p>
-
- <dl class="img_tags">
- <dt>Date:</dt><dd>2007/05/24 22:27</dd><dt>Filename:</dt><dd>gschem_workflow_01.jpg</dd><dt>Format:</dt><dd>JPEG</dd><dt>Size:</dt><dd>44KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/001geda_nets.html b/docs/wiki/_detail/001geda_nets.html
deleted file mode 100644
index 3e69ad5..0000000
--- a/docs/wiki/_detail/001geda_nets.html
+++ /dev/null
@@ -1,50 +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>
- geda:nets.jpg [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:gschem_ug.fr?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gschem_ug.fr"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gschem_ug.fr"; />
-<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" />
-
- <link rel="shortcut icon" href="http://geda.seul.org/wiki/lib/tpl/geda/images/favicon.ico"; />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:nets.jpg</h1>
-
- <div class="img_big">
- <a href="http://geda.seul.org/wiki/_media/geda:nets.jpg?cache=cache";><img src="http://geda.seul.org/wiki/_media/geda:nets.jpg?cache=cache&w=596&h=643"; width="596" height="643" class="img_detail" alt="nets.jpg" title="nets.jpg" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:gschem_ug.fr"; class="wikilink1" title="geda:gschem_ug.fr">gschem_ug.fr</a></span></p>
-
- <dl class="img_tags">
- <dt>Date:</dt><dd>2007/05/24 22:27</dd><dt>Filename:</dt><dd>nets.jpg</dd><dt>Format:</dt><dd>JPEG</dd><dt>Size:</dt><dd>131KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/001geda_status_screenshot.html b/docs/wiki/_detail/001geda_status_screenshot.html
deleted file mode 100644
index 7b30d75..0000000
--- a/docs/wiki/_detail/001geda_status_screenshot.html
+++ /dev/null
@@ -1,50 +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>
- geda:status_screenshot.jpg [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:gschem_ug.fr?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gschem_ug.fr"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gschem_ug.fr"; />
-<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" />
-
- <link rel="shortcut icon" href="http://geda.seul.org/wiki/lib/tpl/geda/images/favicon.ico"; />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:status_screenshot.jpg</h1>
-
- <div class="img_big">
- <a href="http://geda.seul.org/wiki/_media/geda:status_screenshot.jpg?cache=cache";><img src="http://geda.seul.org/wiki/_media/geda:status_screenshot.jpg?cache=cache&w=612&h=367"; width="612" height="367" class="img_detail" alt="status_screenshot.jpg" title="status_screenshot.jpg" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:gschem_ug.fr"; class="wikilink1" title="geda:gschem_ug.fr">gschem_ug.fr</a></span></p>
-
- <dl class="img_tags">
- <dt>Date:</dt><dd>2007/05/24 22:27</dd><dt>Filename:</dt><dd>status_screenshot.jpg</dd><dt>Format:</dt><dd>JPEG</dd><dt>Size:</dt><dd>136KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/001geda_symbol_7400-1.html b/docs/wiki/_detail/001geda_symbol_7400-1.html
deleted file mode 100644
index de16766..0000000
--- a/docs/wiki/_detail/001geda_symbol_7400-1.html
+++ /dev/null
@@ -1,50 +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>
- geda:symbol_7400-1.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:scg.fr?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:scg.fr"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:scg.fr"; />
-<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" />
-
- <link rel="shortcut icon" href="http://geda.seul.org/wiki/lib/tpl/geda/images/favicon.ico"; />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:symbol_7400-1.png</h1>
-
- <div class="img_big">
- <a href="http://geda.seul.org/wiki/_media/geda:symbol_7400-1.png?cache=cache";><img src="http://geda.seul.org/wiki/_media/geda:symbol_7400-1.png?cache=cache&w=443&h=274"; width="443" height="274" class="img_detail" alt="symbol_7400-1.png" title="symbol_7400-1.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:scg.fr"; class="wikilink1" title="geda:scg.fr">scg.fr</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>symbol_7400-1.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>5KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/001geda_symbol_7400-1_hidden.html b/docs/wiki/_detail/001geda_symbol_7400-1_hidden.html
deleted file mode 100644
index a583746..0000000
--- a/docs/wiki/_detail/001geda_symbol_7400-1_hidden.html
+++ /dev/null
@@ -1,50 +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>
- geda:symbol_7400-1_hidden.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:scg.fr?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:scg.fr"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:scg.fr"; />
-<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" />
-
- <link rel="shortcut icon" href="http://geda.seul.org/wiki/lib/tpl/geda/images/favicon.ico"; />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:symbol_7400-1_hidden.png</h1>
-
- <div class="img_big">
- <a href="http://geda.seul.org/wiki/_media/geda:symbol_7400-1_hidden.png?cache=cache";><img src="http://geda.seul.org/wiki/_media/geda:symbol_7400-1_hidden.png?cache=cache&w=383&h=305"; width="383" height="305" class="img_detail" alt="symbol_7400-1_hidden.png" title="symbol_7400-1_hidden.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:scg.fr"; class="wikilink1" title="geda:scg.fr">scg.fr</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>symbol_7400-1_hidden.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>3KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/001geda_terminal_screenshot_001.html b/docs/wiki/_detail/001geda_terminal_screenshot_001.html
deleted file mode 100644
index 9d8f535..0000000
--- a/docs/wiki/_detail/001geda_terminal_screenshot_001.html
+++ /dev/null
@@ -1,50 +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>
- geda:terminal_screenshot_001.jpg [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:gschem_ug.fr?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gschem_ug.fr"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gschem_ug.fr"; />
-<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" />
-
- <link rel="shortcut icon" href="http://geda.seul.org/wiki/lib/tpl/geda/images/favicon.ico"; />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:terminal_screenshot_001.jpg</h1>
-
- <div class="img_big">
- <a href="http://geda.seul.org/wiki/_media/geda:terminal_screenshot_001.jpg?cache=cache";><img src="http://geda.seul.org/wiki/_media/geda:terminal_screenshot_001.jpg?cache=cache&w=589&h=417"; width="589" height="417" class="img_detail" alt="terminal_screenshot_001.jpg" title="terminal_screenshot_001.jpg" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:gschem_ug.fr"; class="wikilink1" title="geda:gschem_ug.fr">gschem_ug.fr</a></span></p>
-
- <dl class="img_tags">
- <dt>Date:</dt><dd>2007/05/24 22:27</dd><dt>Filename:</dt><dd>terminal_screenshot_001.jpg</dd><dt>Format:</dt><dd>JPEG</dd><dt>Size:</dt><dd>65KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/001tragesym_acroread_selectiontable.html b/docs/wiki/_detail/001tragesym_acroread_selectiontable.html
deleted file mode 100644
index 7462882..0000000
--- a/docs/wiki/_detail/001tragesym_acroread_selectiontable.html
+++ /dev/null
@@ -1,50 +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>
- tragesym:acroread_selectiontable.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:tragesym_tutorial.fr?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:tragesym_tutorial.fr"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:tragesym_tutorial.fr"; />
-<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" />
-
- <link rel="shortcut icon" href="http://geda.seul.org/wiki/lib/tpl/geda/images/favicon.ico"; />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>tragesym:acroread_selectiontable.png</h1>
-
- <div class="img_big">
- <a href="http://geda.seul.org/wiki/_media/tragesym:acroread_selectiontable.png?cache=cache";><img src="http://geda.seul.org/wiki/_media/tragesym:acroread_selectiontable.png?cache=cache&w=375&h=371"; width="375" height="371" class="img_detail" alt="acroread_selectiontable.png" title="acroread_selectiontable.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:tragesym_tutorial.fr"; class="wikilink1" title="geda:tragesym_tutorial.fr">tragesym_tutorial.fr</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>acroread_selectiontable.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>20KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/001tragesym_gschem_finished.html b/docs/wiki/_detail/001tragesym_gschem_finished.html
deleted file mode 100644
index 4bbabce..0000000
--- a/docs/wiki/_detail/001tragesym_gschem_finished.html
+++ /dev/null
@@ -1,50 +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>
- tragesym:gschem_finished.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:tragesym_tutorial.fr?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:tragesym_tutorial.fr"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:tragesym_tutorial.fr"; />
-<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" />
-
- <link rel="shortcut icon" href="http://geda.seul.org/wiki/lib/tpl/geda/images/favicon.ico"; />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>tragesym:gschem_finished.png</h1>
-
- <div class="img_big">
- <a href="http://geda.seul.org/wiki/_media/tragesym:gschem_finished.png?cache=cache";><img src="http://geda.seul.org/wiki/_media/tragesym:gschem_finished.png?cache=cache&w=180&h=700"; width="180" height="700" class="img_detail" alt="gschem_finished.png" title="gschem_finished.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:tragesym_tutorial.fr"; class="wikilink1" title="geda:tragesym_tutorial.fr">tragesym_tutorial.fr</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>gschem_finished.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>5KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/001tragesym_gschem_showhidden.html b/docs/wiki/_detail/001tragesym_gschem_showhidden.html
deleted file mode 100644
index 68c8e90..0000000
--- a/docs/wiki/_detail/001tragesym_gschem_showhidden.html
+++ /dev/null
@@ -1,50 +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>
- tragesym:gschem_showhidden.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:tragesym_tutorial.fr?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:tragesym_tutorial.fr"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:tragesym_tutorial.fr"; />
-<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" />
-
- <link rel="shortcut icon" href="http://geda.seul.org/wiki/lib/tpl/geda/images/favicon.ico"; />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>tragesym:gschem_showhidden.png</h1>
-
- <div class="img_big">
- <a href="http://geda.seul.org/wiki/_media/tragesym:gschem_showhidden.png?cache=cache";><img src="http://geda.seul.org/wiki/_media/tragesym:gschem_showhidden.png?cache=cache&w=232&h=700"; width="232" height="700" class="img_detail" alt="gschem_showhidden.png" title="gschem_showhidden.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:tragesym_tutorial.fr"; class="wikilink1" title="geda:tragesym_tutorial.fr">tragesym_tutorial.fr</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>gschem_showhidden.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>10KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/001tragesym_kpdf_pinconfiguration.html b/docs/wiki/_detail/001tragesym_kpdf_pinconfiguration.html
deleted file mode 100644
index bbe89fa..0000000
--- a/docs/wiki/_detail/001tragesym_kpdf_pinconfiguration.html
+++ /dev/null
@@ -1,50 +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>
- tragesym:kpdf_pinconfiguration.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:tragesym_tutorial.fr?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:tragesym_tutorial.fr"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:tragesym_tutorial.fr"; />
-<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" />
-
- <link rel="shortcut icon" href="http://geda.seul.org/wiki/lib/tpl/geda/images/favicon.ico"; />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>tragesym:kpdf_pinconfiguration.png</h1>
-
- <div class="img_big">
- <a href="http://geda.seul.org/wiki/_media/tragesym:kpdf_pinconfiguration.png?cache=cache";><img src="http://geda.seul.org/wiki/_media/tragesym:kpdf_pinconfiguration.png?cache=cache&w=504&h=371"; width="504" height="371" class="img_detail" alt="kpdf_pinconfiguration.png" title="kpdf_pinconfiguration.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:tragesym_tutorial.fr"; class="wikilink1" title="geda:tragesym_tutorial.fr">tragesym_tutorial.fr</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>kpdf_pinconfiguration.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>43KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/001tragesym_kpdf_pindescription.html b/docs/wiki/_detail/001tragesym_kpdf_pindescription.html
deleted file mode 100644
index 61d6a0d..0000000
--- a/docs/wiki/_detail/001tragesym_kpdf_pindescription.html
+++ /dev/null
@@ -1,50 +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>
- tragesym:kpdf_pindescription.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:tragesym_tutorial.fr?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:tragesym_tutorial.fr"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:tragesym_tutorial.fr"; />
-<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" />
-
- <link rel="shortcut icon" href="http://geda.seul.org/wiki/lib/tpl/geda/images/favicon.ico"; />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>tragesym:kpdf_pindescription.png</h1>
-
- <div class="img_big">
- <a href="http://geda.seul.org/wiki/_media/tragesym:kpdf_pindescription.png?cache=cache";><img src="http://geda.seul.org/wiki/_media/tragesym:kpdf_pindescription.png?cache=cache&w=670&h=235"; width="670" height="235" class="img_detail" alt="kpdf_pindescription.png" title="kpdf_pindescription.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:tragesym_tutorial.fr"; class="wikilink1" title="geda:tragesym_tutorial.fr">tragesym_tutorial.fr</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>kpdf_pindescription.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>31KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/001tragesym_ooo_attributes.html b/docs/wiki/_detail/001tragesym_ooo_attributes.html
deleted file mode 100644
index b254934..0000000
--- a/docs/wiki/_detail/001tragesym_ooo_attributes.html
+++ /dev/null
@@ -1,50 +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>
- tragesym:ooo_attributes.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:tragesym_tutorial.fr?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:tragesym_tutorial.fr"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:tragesym_tutorial.fr"; />
-<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" />
-
- <link rel="shortcut icon" href="http://geda.seul.org/wiki/lib/tpl/geda/images/favicon.ico"; />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>tragesym:ooo_attributes.png</h1>
-
- <div class="img_big">
- <a href="http://geda.seul.org/wiki/_media/tragesym:ooo_attributes.png?cache=cache";><img src="http://geda.seul.org/wiki/_media/tragesym:ooo_attributes.png?cache=cache&w=723&h=398"; width="723" height="398" class="img_detail" alt="ooo_attributes.png" title="ooo_attributes.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:tragesym_tutorial.fr"; class="wikilink1" title="geda:tragesym_tutorial.fr">tragesym_tutorial.fr</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>ooo_attributes.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>47KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/001tragesym_ooo_changedpins.html b/docs/wiki/_detail/001tragesym_ooo_changedpins.html
deleted file mode 100644
index 0841d6d..0000000
--- a/docs/wiki/_detail/001tragesym_ooo_changedpins.html
+++ /dev/null
@@ -1,50 +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>
- tragesym:ooo_changedpins.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:tragesym_tutorial.fr?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:tragesym_tutorial.fr"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:tragesym_tutorial.fr"; />
-<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" />
-
- <link rel="shortcut icon" href="http://geda.seul.org/wiki/lib/tpl/geda/images/favicon.ico"; />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>tragesym:ooo_changedpins.png</h1>
-
- <div class="img_big">
- <a href="http://geda.seul.org/wiki/_media/tragesym:ooo_changedpins.png?cache=cache";><img src="http://geda.seul.org/wiki/_media/tragesym:ooo_changedpins.png?cache=cache&w=575&h=336"; width="575" height="336" class="img_detail" alt="ooo_changedpins.png" title="ooo_changedpins.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:tragesym_tutorial.fr"; class="wikilink1" title="geda:tragesym_tutorial.fr">tragesym_tutorial.fr</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>ooo_changedpins.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>21KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/001tragesym_ooo_rearanged.html b/docs/wiki/_detail/001tragesym_ooo_rearanged.html
deleted file mode 100644
index 9edcc6b..0000000
--- a/docs/wiki/_detail/001tragesym_ooo_rearanged.html
+++ /dev/null
@@ -1,50 +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>
- tragesym:ooo_rearanged.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:tragesym_tutorial.fr?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:tragesym_tutorial.fr"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:tragesym_tutorial.fr"; />
-<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" />
-
- <link rel="shortcut icon" href="http://geda.seul.org/wiki/lib/tpl/geda/images/favicon.ico"; />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>tragesym:ooo_rearanged.png</h1>
-
- <div class="img_big">
- <a href="http://geda.seul.org/wiki/_media/tragesym:ooo_rearanged.png?cache=cache";><img src="http://geda.seul.org/wiki/_media/tragesym:ooo_rearanged.png?cache=cache&w=584&h=553"; width="584" height="553" class="img_detail" alt="ooo_rearanged.png" title="ooo_rearanged.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:tragesym_tutorial.fr"; class="wikilink1" title="geda:tragesym_tutorial.fr">tragesym_tutorial.fr</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>ooo_rearanged.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>41KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/001tragesym_ooo_selection.html b/docs/wiki/_detail/001tragesym_ooo_selection.html
deleted file mode 100644
index d3a7c93..0000000
--- a/docs/wiki/_detail/001tragesym_ooo_selection.html
+++ /dev/null
@@ -1,50 +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>
- tragesym:ooo_selection.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:tragesym_tutorial.fr?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:tragesym_tutorial.fr"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:tragesym_tutorial.fr"; />
-<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" />
-
- <link rel="shortcut icon" href="http://geda.seul.org/wiki/lib/tpl/geda/images/favicon.ico"; />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>tragesym:ooo_selection.png</h1>
-
- <div class="img_big">
- <a href="http://geda.seul.org/wiki/_media/tragesym:ooo_selection.png?cache=cache";><img src="http://geda.seul.org/wiki/_media/tragesym:ooo_selection.png?cache=cache&w=335&h=383"; width="335" height="383" class="img_detail" alt="ooo_selection.png" title="ooo_selection.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:tragesym_tutorial.fr"; class="wikilink1" title="geda:tragesym_tutorial.fr">tragesym_tutorial.fr</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>ooo_selection.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>9KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/001tragesym_xemacs_modifiedselection.html b/docs/wiki/_detail/001tragesym_xemacs_modifiedselection.html
deleted file mode 100644
index be387b3..0000000
--- a/docs/wiki/_detail/001tragesym_xemacs_modifiedselection.html
+++ /dev/null
@@ -1,50 +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>
- tragesym:xemacs_modifiedselection.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:tragesym_tutorial.fr?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:tragesym_tutorial.fr"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:tragesym_tutorial.fr"; />
-<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" />
-
- <link rel="shortcut icon" href="http://geda.seul.org/wiki/lib/tpl/geda/images/favicon.ico"; />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>tragesym:xemacs_modifiedselection.png</h1>
-
- <div class="img_big">
- <a href="http://geda.seul.org/wiki/_media/tragesym:xemacs_modifiedselection.png?cache=cache";><img src="http://geda.seul.org/wiki/_media/tragesym:xemacs_modifiedselection.png?cache=cache&w=163&h=383"; width="163" height="383" class="img_detail" alt="xemacs_modifiedselection.png" title="xemacs_modifiedselection.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:tragesym_tutorial.fr"; class="wikilink1" title="geda:tragesym_tutorial.fr">tragesym_tutorial.fr</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>xemacs_modifiedselection.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>3KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/001tragesym_xemacs_rawselection.html b/docs/wiki/_detail/001tragesym_xemacs_rawselection.html
deleted file mode 100644
index 1c63593..0000000
--- a/docs/wiki/_detail/001tragesym_xemacs_rawselection.html
+++ /dev/null
@@ -1,50 +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>
- tragesym:xemacs_rawselection.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:tragesym_tutorial.fr?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:tragesym_tutorial.fr"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:tragesym_tutorial.fr"; />
-<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" />
-
- <link rel="shortcut icon" href="http://geda.seul.org/wiki/lib/tpl/geda/images/favicon.ico"; />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>tragesym:xemacs_rawselection.png</h1>
-
- <div class="img_big">
- <a href="http://geda.seul.org/wiki/_media/tragesym:xemacs_rawselection.png?cache=cache";><img src="http://geda.seul.org/wiki/_media/tragesym:xemacs_rawselection.png?cache=cache&w=168&h=384"; width="168" height="384" class="img_detail" alt="xemacs_rawselection.png" title="xemacs_rawselection.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:tragesym_tutorial.fr"; class="wikilink1" title="geda:tragesym_tutorial.fr">tragesym_tutorial.fr</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>xemacs_rawselection.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>6KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/Makefile.am b/docs/wiki/_detail/Makefile.am
deleted file mode 100644
index 824de2f..0000000
--- a/docs/wiki/_detail/Makefile.am
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-docname=wiki
-docsdir = $(docdir)/$(docname)/_detail
-
-docs_DATA = geda_net.html geda_faq_attrib.html geda_board-4.html 001tragesym_xemacs_modifiedselection.html geda_warmup_gschem03.html geda_gschem_screenshot_001.html geda_pcb-el-1.html tragesym_gschem_finished.html geda_rf_cascade_figure1.html geda_geda_flow.html 001tragesym_acroread_selectiontable.html geda_board-2.html geda_dialogmodel.html geda_dialogtrans.html geda_one-sch-3.html 001geda_terminal_screenshot_001.html 001tragesym_gschem_finished.html 001tragesym_xemacs_rawselection.html tragesym_ooo_rearanged.html tragesym_gschem_showhidden.html 001tragesym_kpdf_pinconfiguration.html tragesym_acroread_selectiontable.html geda_design_flow.html geda_switcap_figure1.html geda_schematicfinished2.html geda_two-sch-1.html geda_two-sch-2.html geda_dialogvac.html geda_status_screenshot.html 001geda_gschem_screenshot_001.html geda_symbol_7400-1.html geda_board-3.html geda_gschem-sym-1.html geda_switcap_figure4.html 001geda_ambiguous1.html geda_board-6.html geda_dialogdirective.html 001geda_gschem_workflow_01.html 001geda_ambiguous1_fixed.html geda_warmup_gschem02.html 001geda_symbol_7400-1.html geda_board-1.html geda_gschem-sym-3.html geda_switcap_figure3.html geda_one-sch-1.html geda_pcb-el-2.html 001tragesym_ooo_selection.html geda_nets.html geda_coordinatespace.html 001tragesym_ooo_rearanged.html geda_warmup_add_component.html geda_dialogvdc1.html geda_ambiguous1.html geda_dialoginclude.html 001geda_status_screenshot.html geda_ambiguous1_fixed.html tragesym_ooo_attributes.html tragesym_kpdf_pinconfiguration.html geda_one-sch-2.html geda_terminal_screenshot_001.html 001tragesym_ooo_changedpins.html geda_simple1.html geda_rf_cascade_figure2.html 001tragesym_kpdf_pindescription.html geda_gschem-sym-2.html geda_switcap_figure2.html geda_suse_electronics_menu.html 001geda_faq_attrib.html tragesym_xemacs_rawselection.html devel_tips_dialog_picture.html geda_warmup_gschem01.html tragesym_xemacs_modifiedselection.html geda_board-5.html geda_fileformat_textgraphic.html 001geda_design_flow.html geda_symbol_7400-1_hidden.html tragesym_ooo_changedpins.html 001geda_nets.html geda_gschem_workflow_01.html 001geda_symbol_7400-1_hidden.html 001tragesym_ooo_attributes.html 001tragesym_gschem_showhidden.html tragesym_kpdf_pindescription.html tragesym_ooo_selection.html
-
-EXTRA_DIST = $(docs_DATA)
-
-MAINTAINERCLEANFILES = *.log core FILE *~ Makefile.in
-
diff --git a/docs/wiki/_detail/devel_tips_dialog_picture.html b/docs/wiki/_detail/devel_tips_dialog_picture.html
deleted file mode 100644
index 0532548..0000000
--- a/docs/wiki/_detail/devel_tips_dialog_picture.html
+++ /dev/null
@@ -1,50 +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>
- devel_tips:dialog_picture.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:devel-tips?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:devel-tips"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:devel-tips"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>devel_tips:dialog_picture.png</h1>
-
- <div class="img_big">
- <a href="../_media/devel_tips_dialog_picture.png"><img src="../_media/devel_tips_dialog_picture.png" width="600" height="380" class="img_detail" alt="dialog_picture.png" title="dialog_picture.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:devel-tips"; class="wikilink1" title="geda:devel-tips">devel-tips</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>dialog_picture.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>26KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/geda_ambiguous1.html b/docs/wiki/_detail/geda_ambiguous1.html
deleted file mode 100644
index eb903b0..0000000
--- a/docs/wiki/_detail/geda_ambiguous1.html
+++ /dev/null
@@ -1,50 +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>
- geda:ambiguous1.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:faq-gnetlist?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:faq-gnetlist"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:faq-gnetlist"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:ambiguous1.png</h1>
-
- <div class="img_big">
- <a href="../_media/geda_ambiguous1.png"><img src="../_media/geda_ambiguous1.png" width="707" height="492" class="img_detail" alt="ambiguous1.png" title="ambiguous1.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:faq-gnetlist"; class="wikilink1" title="geda:faq-gnetlist">faq-gnetlist</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>ambiguous1.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>6KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/geda_ambiguous1_fixed.html b/docs/wiki/_detail/geda_ambiguous1_fixed.html
deleted file mode 100644
index 2fc0b95..0000000
--- a/docs/wiki/_detail/geda_ambiguous1_fixed.html
+++ /dev/null
@@ -1,50 +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>
- geda:ambiguous1_fixed.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:faq-gnetlist?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:faq-gnetlist"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:faq-gnetlist"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:ambiguous1_fixed.png</h1>
-
- <div class="img_big">
- <a href="../_media/geda_ambiguous1_fixed.png"><img src="../_media/geda_ambiguous1_fixed.png" width="754" height="506" class="img_detail" alt="ambiguous1_fixed.png" title="ambiguous1_fixed.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:faq-gnetlist"; class="wikilink1" title="geda:faq-gnetlist">faq-gnetlist</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>ambiguous1_fixed.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>5KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/geda_board-1.html b/docs/wiki/_detail/geda_board-1.html
deleted file mode 100644
index 8c44fc6..0000000
--- a/docs/wiki/_detail/geda_board-1.html
+++ /dev/null
@@ -1,50 +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>
- geda:board-1.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:gsch2pcb_tutorial?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gsch2pcb_tutorial"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gsch2pcb_tutorial"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:board-1.png</h1>
-
- <div class="img_big">
- <a href="../_media/geda_board-1.png"><img src="../_media/geda_board-1.png" width="167" height="265" class="img_detail" alt="board-1.png" title="board-1.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:gsch2pcb_tutorial"; class="wikilink1" title="geda:gsch2pcb_tutorial">gsch2pcb_tutorial</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>board-1.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>4KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/geda_board-2.html b/docs/wiki/_detail/geda_board-2.html
deleted file mode 100644
index 9f929d7..0000000
--- a/docs/wiki/_detail/geda_board-2.html
+++ /dev/null
@@ -1,50 +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>
- geda:board-2.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:gsch2pcb_tutorial?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gsch2pcb_tutorial"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gsch2pcb_tutorial"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:board-2.png</h1>
-
- <div class="img_big">
- <a href="../_media/geda_board-2.png"><img src="../_media/geda_board-2.png" width="182" height="324" class="img_detail" alt="board-2.png" title="board-2.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:gsch2pcb_tutorial"; class="wikilink1" title="geda:gsch2pcb_tutorial">gsch2pcb_tutorial</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>board-2.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>5KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/geda_board-3.html b/docs/wiki/_detail/geda_board-3.html
deleted file mode 100644
index 2f86305..0000000
--- a/docs/wiki/_detail/geda_board-3.html
+++ /dev/null
@@ -1,50 +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>
- geda:board-3.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:gsch2pcb_tutorial?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gsch2pcb_tutorial"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gsch2pcb_tutorial"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:board-3.png</h1>
-
- <div class="img_big">
- <a href="../_media/geda_board-3.png"><img src="../_media/geda_board-3.png" width="191" height="324" class="img_detail" alt="board-3.png" title="board-3.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:gsch2pcb_tutorial"; class="wikilink1" title="geda:gsch2pcb_tutorial">gsch2pcb_tutorial</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>board-3.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>9KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/geda_board-4.html b/docs/wiki/_detail/geda_board-4.html
deleted file mode 100644
index 3cacc25..0000000
--- a/docs/wiki/_detail/geda_board-4.html
+++ /dev/null
@@ -1,50 +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>
- geda:board-4.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:gsch2pcb_tutorial?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gsch2pcb_tutorial"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gsch2pcb_tutorial"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:board-4.png</h1>
-
- <div class="img_big">
- <a href="../_media/geda_board-4.png"><img src="../_media/geda_board-4.png" width="206" height="299" class="img_detail" alt="board-4.png" title="board-4.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:gsch2pcb_tutorial"; class="wikilink1" title="geda:gsch2pcb_tutorial">gsch2pcb_tutorial</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>board-4.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>8KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/geda_board-5.html b/docs/wiki/_detail/geda_board-5.html
deleted file mode 100644
index 23e0f84..0000000
--- a/docs/wiki/_detail/geda_board-5.html
+++ /dev/null
@@ -1,50 +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>
- geda:board-5.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:gsch2pcb_tutorial?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gsch2pcb_tutorial"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gsch2pcb_tutorial"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:board-5.png</h1>
-
- <div class="img_big">
- <a href="../_media/geda_board-5.png"><img src="../_media/geda_board-5.png" width="233" height="263" class="img_detail" alt="board-5.png" title="board-5.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:gsch2pcb_tutorial"; class="wikilink1" title="geda:gsch2pcb_tutorial">gsch2pcb_tutorial</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>board-5.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>7KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/geda_board-6.html b/docs/wiki/_detail/geda_board-6.html
deleted file mode 100644
index 9c7c992..0000000
--- a/docs/wiki/_detail/geda_board-6.html
+++ /dev/null
@@ -1,50 +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>
- geda:board-6.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:gsch2pcb_tutorial?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gsch2pcb_tutorial"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gsch2pcb_tutorial"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:board-6.png</h1>
-
- <div class="img_big">
- <a href="../_media/geda_board-6.png"><img src="../_media/geda_board-6.png" width="227" height="278" class="img_detail" alt="board-6.png" title="board-6.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:gsch2pcb_tutorial"; class="wikilink1" title="geda:gsch2pcb_tutorial">gsch2pcb_tutorial</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>board-6.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>7KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/geda_coordinatespace.html b/docs/wiki/_detail/geda_coordinatespace.html
deleted file mode 100644
index 8ea4225..0000000
--- a/docs/wiki/_detail/geda_coordinatespace.html
+++ /dev/null
@@ -1,50 +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>
- geda:coordinatespace.jpg [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:file_format_spec?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:file_format_spec"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:file_format_spec"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:coordinatespace.jpg</h1>
-
- <div class="img_big">
- <a href="../_media/geda_coordinatespace.jpg"><img src="../_media/geda_coordinatespace.jpg" width="470" height="358" class="img_detail" alt="coordinatespace.jpg" title="coordinatespace.jpg" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:file_format_spec"; class="wikilink1" title="geda:file_format_spec">file_format_spec</a></span></p>
-
- <dl class="img_tags">
- <dt>Date:</dt><dd>2007/05/24 22:27</dd><dt>Filename:</dt><dd>coordinatespace.jpg</dd><dt>Format:</dt><dd>JPEG</dd><dt>Size:</dt><dd>6KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/geda_design_flow.html b/docs/wiki/_detail/geda_design_flow.html
deleted file mode 100644
index b30f8ab..0000000
--- a/docs/wiki/_detail/geda_design_flow.html
+++ /dev/null
@@ -1,50 +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>
- geda:design_flow.jpg [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:usage?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:usage"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:usage"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:design_flow.jpg</h1>
-
- <div class="img_big">
- <a href="../_media/geda_design_flow.jpg"><img src="../_media/geda_design_flow.jpg" width="398" height="414" class="img_detail" alt="design_flow.jpg" title="design_flow.jpg" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:usage"; class="wikilink1" title="geda:usage">usage</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>design_flow.jpg</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>4KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/geda_dialogdirective.html b/docs/wiki/_detail/geda_dialogdirective.html
deleted file mode 100644
index 8a5b6c5..0000000
--- a/docs/wiki/_detail/geda_dialogdirective.html
+++ /dev/null
@@ -1,50 +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>
- geda:dialogdirective.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:ngspice_and_gschem?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:ngspice_and_gschem"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:ngspice_and_gschem"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:dialogdirective.png</h1>
-
- <div class="img_big">
- <a href="../_media/geda_dialogdirective.png"><img src="../_media/geda_dialogdirective.png" width="622" height="332" class="img_detail" alt="dialogdirective.png" title="dialogdirective.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:ngspice_and_gschem"; class="wikilink1" title="geda:ngspice_and_gschem">ngspice_and_gschem</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>dialogdirective.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>16KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/geda_dialoginclude.html b/docs/wiki/_detail/geda_dialoginclude.html
deleted file mode 100644
index fbbfc02..0000000
--- a/docs/wiki/_detail/geda_dialoginclude.html
+++ /dev/null
@@ -1,50 +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>
- geda:dialoginclude.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:ngspice_and_gschem?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:ngspice_and_gschem"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:ngspice_and_gschem"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:dialoginclude.png</h1>
-
- <div class="img_big">
- <a href="../_media/geda_dialoginclude.png"><img src="../_media/geda_dialoginclude.png" width="622" height="332" class="img_detail" alt="dialoginclude.png" title="dialoginclude.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:ngspice_and_gschem"; class="wikilink1" title="geda:ngspice_and_gschem">ngspice_and_gschem</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>dialoginclude.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>15KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/geda_dialogmodel.html b/docs/wiki/_detail/geda_dialogmodel.html
deleted file mode 100644
index 2f304d7..0000000
--- a/docs/wiki/_detail/geda_dialogmodel.html
+++ /dev/null
@@ -1,50 +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>
- geda:dialogmodel.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:ngspice_and_gschem?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:ngspice_and_gschem"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:ngspice_and_gschem"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:dialogmodel.png</h1>
-
- <div class="img_big">
- <a href="../_media/geda_dialogmodel.png"><img src="../_media/geda_dialogmodel.png" width="622" height="332" class="img_detail" alt="dialogmodel.png" title="dialogmodel.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:ngspice_and_gschem"; class="wikilink1" title="geda:ngspice_and_gschem">ngspice_and_gschem</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>dialogmodel.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>17KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/geda_dialogtrans.html b/docs/wiki/_detail/geda_dialogtrans.html
deleted file mode 100644
index f5a1628..0000000
--- a/docs/wiki/_detail/geda_dialogtrans.html
+++ /dev/null
@@ -1,50 +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>
- geda:dialogtrans.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:ngspice_and_gschem?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:ngspice_and_gschem"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:ngspice_and_gschem"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:dialogtrans.png</h1>
-
- <div class="img_big">
- <a href="../_media/geda_dialogtrans.png"><img src="../_media/geda_dialogtrans.png" width="622" height="332" class="img_detail" alt="dialogtrans.png" title="dialogtrans.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:ngspice_and_gschem"; class="wikilink1" title="geda:ngspice_and_gschem">ngspice_and_gschem</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>dialogtrans.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>16KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/geda_dialogvac.html b/docs/wiki/_detail/geda_dialogvac.html
deleted file mode 100644
index 05a9504..0000000
--- a/docs/wiki/_detail/geda_dialogvac.html
+++ /dev/null
@@ -1,50 +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>
- geda:dialogvac.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:ngspice_and_gschem?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:ngspice_and_gschem"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:ngspice_and_gschem"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:dialogvac.png</h1>
-
- <div class="img_big">
- <a href="../_media/geda_dialogvac.png"><img src="../_media/geda_dialogvac.png" width="622" height="332" class="img_detail" alt="dialogvac.png" title="dialogvac.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:ngspice_and_gschem"; class="wikilink1" title="geda:ngspice_and_gschem">ngspice_and_gschem</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>dialogvac.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>17KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/geda_dialogvdc1.html b/docs/wiki/_detail/geda_dialogvdc1.html
deleted file mode 100644
index 21cbf03..0000000
--- a/docs/wiki/_detail/geda_dialogvdc1.html
+++ /dev/null
@@ -1,50 +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>
- geda:dialogvdc1.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:ngspice_and_gschem?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:ngspice_and_gschem"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:ngspice_and_gschem"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:dialogvdc1.png</h1>
-
- <div class="img_big">
- <a href="../_media/geda_dialogvdc1.png"><img src="../_media/geda_dialogvdc1.png" width="622" height="332" class="img_detail" alt="dialogvdc1.png" title="dialogvdc1.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:ngspice_and_gschem"; class="wikilink1" title="geda:ngspice_and_gschem">ngspice_and_gschem</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>dialogvdc1.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>17KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/geda_faq_attrib.html b/docs/wiki/_detail/geda_faq_attrib.html
deleted file mode 100644
index 41aec34..0000000
--- a/docs/wiki/_detail/geda_faq_attrib.html
+++ /dev/null
@@ -1,50 +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>
- geda:faq_attrib.jpg [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:faq-attribs?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:faq-attribs"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:faq-attribs"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:faq_attrib.jpg</h1>
-
- <div class="img_big">
- <a href="../_media/geda_faq_attrib.jpg"><img src="../_media/geda_faq_attrib.jpg" width="756" height="623" class="img_detail" alt="faq_attrib.jpg" title="faq_attrib.jpg" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:faq-attribs"; class="wikilink1" title="geda:faq-attribs">faq-attribs</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>faq_attrib.jpg</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>25KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/geda_fileformat_textgraphic.html b/docs/wiki/_detail/geda_fileformat_textgraphic.html
deleted file mode 100644
index 02be3b0..0000000
--- a/docs/wiki/_detail/geda_fileformat_textgraphic.html
+++ /dev/null
@@ -1,50 +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>
- geda:fileformat_textgraphic.jpg [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:file_format_spec?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:file_format_spec"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:file_format_spec"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:fileformat_textgraphic.jpg</h1>
-
- <div class="img_big">
- <a href="../_media/geda_fileformat_textgraphic.jpg"><img src="../_media/geda_fileformat_textgraphic.jpg" width="432" height="200" class="img_detail" alt="fileformat_textgraphic.jpg" title="fileformat_textgraphic.jpg" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:file_format_spec"; class="wikilink1" title="geda:file_format_spec">file_format_spec</a></span></p>
-
- <dl class="img_tags">
- <dt>Date:</dt><dd>2007/05/24 22:27</dd><dt>Filename:</dt><dd>fileformat_textgraphic.jpg</dd><dt>Format:</dt><dd>JPEG</dd><dt>Size:</dt><dd>9KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/geda_geda_flow.html b/docs/wiki/_detail/geda_geda_flow.html
deleted file mode 100644
index 8120ec0..0000000
--- a/docs/wiki/_detail/geda_geda_flow.html
+++ /dev/null
@@ -1,50 +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>
- geda:geda_flow.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:csygas?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:csygas"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:csygas"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:geda_flow.png</h1>
-
- <div class="img_big">
- <a href="../_media/geda_geda_flow.png"><img src="../_media/geda_geda_flow.png" width="730" height="554" class="img_detail" alt="geda_flow.png" title="geda_flow.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:csygas"; class="wikilink1" title="geda:csygas">csygas</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>geda_flow.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>7KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/geda_gschem-sym-1.html b/docs/wiki/_detail/geda_gschem-sym-1.html
deleted file mode 100644
index 7df612a..0000000
--- a/docs/wiki/_detail/geda_gschem-sym-1.html
+++ /dev/null
@@ -1,50 +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>
- geda:gschem-sym-1.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:gsch2pcb_tutorial?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gsch2pcb_tutorial"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gsch2pcb_tutorial"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:gschem-sym-1.png</h1>
-
- <div class="img_big">
- <a href="../_media/geda_gschem-sym-1.png"><img src="../_media/geda_gschem-sym-1.png" width="178" height="200" class="img_detail" alt="gschem-sym-1.png" title="gschem-sym-1.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:gsch2pcb_tutorial"; class="wikilink1" title="geda:gsch2pcb_tutorial">gsch2pcb_tutorial</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>gschem-sym-1.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>4KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/geda_gschem-sym-2.html b/docs/wiki/_detail/geda_gschem-sym-2.html
deleted file mode 100644
index 75e01e9..0000000
--- a/docs/wiki/_detail/geda_gschem-sym-2.html
+++ /dev/null
@@ -1,50 +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>
- geda:gschem-sym-2.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:gsch2pcb_tutorial?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gsch2pcb_tutorial"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gsch2pcb_tutorial"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:gschem-sym-2.png</h1>
-
- <div class="img_big">
- <a href="../_media/geda_gschem-sym-2.png"><img src="../_media/geda_gschem-sym-2.png" width="182" height="197" class="img_detail" alt="gschem-sym-2.png" title="gschem-sym-2.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:gsch2pcb_tutorial"; class="wikilink1" title="geda:gsch2pcb_tutorial">gsch2pcb_tutorial</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>gschem-sym-2.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>4KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/geda_gschem-sym-3.html b/docs/wiki/_detail/geda_gschem-sym-3.html
deleted file mode 100644
index b7cfc7e..0000000
--- a/docs/wiki/_detail/geda_gschem-sym-3.html
+++ /dev/null
@@ -1,50 +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>
- geda:gschem-sym-3.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:gsch2pcb_tutorial?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gsch2pcb_tutorial"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gsch2pcb_tutorial"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:gschem-sym-3.png</h1>
-
- <div class="img_big">
- <a href="../_media/geda_gschem-sym-3.png"><img src="../_media/geda_gschem-sym-3.png" width="142" height="227" class="img_detail" alt="gschem-sym-3.png" title="gschem-sym-3.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:gsch2pcb_tutorial"; class="wikilink1" title="geda:gsch2pcb_tutorial">gsch2pcb_tutorial</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>gschem-sym-3.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>4KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/geda_gschem_screenshot_001.html b/docs/wiki/_detail/geda_gschem_screenshot_001.html
deleted file mode 100644
index 4f4c0a1..0000000
--- a/docs/wiki/_detail/geda_gschem_screenshot_001.html
+++ /dev/null
@@ -1,50 +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>
- geda:gschem_screenshot_001.jpg [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:gschem_ug?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gschem_ug"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gschem_ug"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:gschem_screenshot_001.jpg</h1>
-
- <div class="img_big">
- <a href="../_media/geda_gschem_screenshot_.jpg"><img src="../_media/geda_gschem_screenshot_001.jpg" width="695" height="598" class="img_detail" alt="gschem_screenshot_001.jpg" title="gschem_screenshot_001.jpg" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:gschem_ug"; class="wikilink1" title="geda:gschem_ug">gschem_ug</a></span></p>
-
- <dl class="img_tags">
- <dt>Date:</dt><dd>2007/05/24 22:27</dd><dt>Filename:</dt><dd>gschem_screenshot_001.jpg</dd><dt>Format:</dt><dd>JPEG</dd><dt>Size:</dt><dd>36KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/geda_gschem_workflow_01.html b/docs/wiki/_detail/geda_gschem_workflow_01.html
deleted file mode 100644
index f8d3ea9..0000000
--- a/docs/wiki/_detail/geda_gschem_workflow_01.html
+++ /dev/null
@@ -1,50 +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>
- geda:gschem_workflow_01.jpg [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:gschem_ug?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gschem_ug"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gschem_ug"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:gschem_workflow_01.jpg</h1>
-
- <div class="img_big">
- <a href="../_media/geda_gschem_workflow_01.jpg"><img src="../_media/geda_gschem_workflow_01.jpg" width="532" height="389" class="img_detail" alt="gschem_workflow_01.jpg" title="gschem_workflow_01.jpg" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:gschem_ug"; class="wikilink1" title="geda:gschem_ug">gschem_ug</a></span></p>
-
- <dl class="img_tags">
- <dt>Date:</dt><dd>2007/05/24 22:27</dd><dt>Filename:</dt><dd>gschem_workflow_01.jpg</dd><dt>Format:</dt><dd>JPEG</dd><dt>Size:</dt><dd>44KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/geda_net.html b/docs/wiki/_detail/geda_net.html
deleted file mode 100644
index 2a532ca..0000000
--- a/docs/wiki/_detail/geda_net.html
+++ /dev/null
@@ -1,50 +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>
- geda:net.jpg [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:na_howto?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:na_howto"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:na_howto"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:net.jpg</h1>
-
- <div class="img_big">
- <a href="../_media/geda_net.jpg"><img src="../_media/geda_net.jpg" width="861" height="657" class="img_detail" alt="net.jpg" title="net.jpg" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:na_howto"; class="wikilink1" title="geda:na_howto">na_howto</a></span></p>
-
- <dl class="img_tags">
- <dt>Date:</dt><dd>2007/05/24 22:27</dd><dt>Filename:</dt><dd>net.jpg</dd><dt>Format:</dt><dd>JPEG</dd><dt>Size:</dt><dd>66KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/geda_nets.html b/docs/wiki/_detail/geda_nets.html
deleted file mode 100644
index b14e1b4..0000000
--- a/docs/wiki/_detail/geda_nets.html
+++ /dev/null
@@ -1,50 +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>
- geda:nets.jpg [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:gschem_ug?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gschem_ug"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gschem_ug"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:nets.jpg</h1>
-
- <div class="img_big">
- <a href="../_media/geda_nets.jpg"><img src="../_media/geda_nets.jpg" width="596" height="643" class="img_detail" alt="nets.jpg" title="nets.jpg" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:gschem_ug"; class="wikilink1" title="geda:gschem_ug">gschem_ug</a></span></p>
-
- <dl class="img_tags">
- <dt>Date:</dt><dd>2007/05/24 22:27</dd><dt>Filename:</dt><dd>nets.jpg</dd><dt>Format:</dt><dd>JPEG</dd><dt>Size:</dt><dd>131KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/geda_one-sch-1.html b/docs/wiki/_detail/geda_one-sch-1.html
deleted file mode 100644
index f655da5..0000000
--- a/docs/wiki/_detail/geda_one-sch-1.html
+++ /dev/null
@@ -1,50 +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>
- geda:one-sch-1.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:gsch2pcb_tutorial?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gsch2pcb_tutorial"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gsch2pcb_tutorial"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:one-sch-1.png</h1>
-
- <div class="img_big">
- <a href="../_media/geda_one-sch-1.png"><img src="../_media/geda_one-sch-1.png" width="276" height="323" class="img_detail" alt="one-sch-1.png" title="one-sch-1.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:gsch2pcb_tutorial"; class="wikilink1" title="geda:gsch2pcb_tutorial">gsch2pcb_tutorial</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>one-sch-1.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>5KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/geda_one-sch-2.html b/docs/wiki/_detail/geda_one-sch-2.html
deleted file mode 100644
index 96e3811..0000000
--- a/docs/wiki/_detail/geda_one-sch-2.html
+++ /dev/null
@@ -1,50 +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>
- geda:one-sch-2.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:gsch2pcb_tutorial?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gsch2pcb_tutorial"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gsch2pcb_tutorial"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:one-sch-2.png</h1>
-
- <div class="img_big">
- <a href="../_media/geda_one-sch-2.png"><img src="../_media/geda_one-sch-2.png" width="252" height="328" class="img_detail" alt="one-sch-2.png" title="one-sch-2.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:gsch2pcb_tutorial"; class="wikilink1" title="geda:gsch2pcb_tutorial">gsch2pcb_tutorial</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>one-sch-2.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>5KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/geda_one-sch-3.html b/docs/wiki/_detail/geda_one-sch-3.html
deleted file mode 100644
index 6f45c9a..0000000
--- a/docs/wiki/_detail/geda_one-sch-3.html
+++ /dev/null
@@ -1,50 +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>
- geda:one-sch-3.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:gsch2pcb_tutorial?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gsch2pcb_tutorial"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gsch2pcb_tutorial"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:one-sch-3.png</h1>
-
- <div class="img_big">
- <a href="../_media/geda_one-sch-3.png"><img src="../_media/geda_one-sch-3.png" width="268" height="331" class="img_detail" alt="one-sch-3.png" title="one-sch-3.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:gsch2pcb_tutorial"; class="wikilink1" title="geda:gsch2pcb_tutorial">gsch2pcb_tutorial</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>one-sch-3.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>5KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/geda_pcb-el-1.html b/docs/wiki/_detail/geda_pcb-el-1.html
deleted file mode 100644
index 8222165..0000000
--- a/docs/wiki/_detail/geda_pcb-el-1.html
+++ /dev/null
@@ -1,50 +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>
- geda:pcb-el-1.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:gsch2pcb_tutorial?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gsch2pcb_tutorial"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gsch2pcb_tutorial"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:pcb-el-1.png</h1>
-
- <div class="img_big">
- <a href="../_media/geda_pcb-el-1.png"><img src="../_media/geda_pcb-el-1.png" width="179" height="130" class="img_detail" alt="pcb-el-1.png" title="pcb-el-1.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:gsch2pcb_tutorial"; class="wikilink1" title="geda:gsch2pcb_tutorial">gsch2pcb_tutorial</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>pcb-el-1.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>993B</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/geda_pcb-el-2.html b/docs/wiki/_detail/geda_pcb-el-2.html
deleted file mode 100644
index 1e37697..0000000
--- a/docs/wiki/_detail/geda_pcb-el-2.html
+++ /dev/null
@@ -1,50 +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>
- geda:pcb-el-2.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:gsch2pcb_tutorial?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gsch2pcb_tutorial"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gsch2pcb_tutorial"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:pcb-el-2.png</h1>
-
- <div class="img_big">
- <a href="../_media/geda_pcb-el-2.png"><img src="../_media/geda_pcb-el-2.png" width="147" height="136" class="img_detail" alt="pcb-el-2.png" title="pcb-el-2.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:gsch2pcb_tutorial"; class="wikilink1" title="geda:gsch2pcb_tutorial">gsch2pcb_tutorial</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>pcb-el-2.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>1KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/geda_rf_cascade_figure1.html b/docs/wiki/_detail/geda_rf_cascade_figure1.html
deleted file mode 100644
index dd60b0a..0000000
--- a/docs/wiki/_detail/geda_rf_cascade_figure1.html
+++ /dev/null
@@ -1,50 +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>
- geda:rf_cascade_figure1.jpg [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:grcsan?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:grcsan"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:grcsan"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:rf_cascade_figure1.jpg</h1>
-
- <div class="img_big">
- <a href="../_media/geda_rf_cascade_figure1.jpg"><img src="../_media/geda_rf_cascade_figure1.jpg" width="694" height="328" class="img_detail" alt="rf_cascade_figure1.jpg" title="rf_cascade_figure1.jpg" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:grcsan"; class="wikilink1" title="geda:grcsan">grcsan</a></span></p>
-
- <dl class="img_tags">
- <dt>Date:</dt><dd>2007/05/24 22:27</dd><dt>Filename:</dt><dd>rf_cascade_figure1.jpg</dd><dt>Format:</dt><dd>JPEG</dd><dt>Size:</dt><dd>28KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/geda_rf_cascade_figure2.html b/docs/wiki/_detail/geda_rf_cascade_figure2.html
deleted file mode 100644
index 9f05616..0000000
--- a/docs/wiki/_detail/geda_rf_cascade_figure2.html
+++ /dev/null
@@ -1,50 +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>
- geda:rf_cascade_figure2.jpg [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:grcsan?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:grcsan"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:grcsan"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:rf_cascade_figure2.jpg</h1>
-
- <div class="img_big">
- <a href="../_media/geda_rf_cascade_figure2.jpg"><img src="../_media/geda_rf_cascade_figure2.jpg" width="682" height="570" class="img_detail" alt="rf_cascade_figure2.jpg" title="rf_cascade_figure2.jpg" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:grcsan"; class="wikilink1" title="geda:grcsan">grcsan</a></span></p>
-
- <dl class="img_tags">
- <dt>Date:</dt><dd>2007/05/24 22:27</dd><dt>Filename:</dt><dd>rf_cascade_figure2.jpg</dd><dt>Format:</dt><dd>JPEG</dd><dt>Size:</dt><dd>54KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/geda_schematicfinished2.html b/docs/wiki/_detail/geda_schematicfinished2.html
deleted file mode 100644
index 2c97468..0000000
--- a/docs/wiki/_detail/geda_schematicfinished2.html
+++ /dev/null
@@ -1,50 +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>
- geda:schematicfinished2.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:ngspice_and_gschem?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:ngspice_and_gschem"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:ngspice_and_gschem"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:schematicfinished2.png</h1>
-
- <div class="img_big">
- <a href="../_media/geda_schematicfinished2.png"><img src="../_media/geda_schematicfinished2.png" width="885" height="543" class="img_detail" alt="schematicfinished2.png" title="schematicfinished2.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:ngspice_and_gschem"; class="wikilink1" title="geda:ngspice_and_gschem">ngspice_and_gschem</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>schematicfinished2.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>14KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/geda_simple1.html b/docs/wiki/_detail/geda_simple1.html
deleted file mode 100644
index 520bb20..0000000
--- a/docs/wiki/_detail/geda_simple1.html
+++ /dev/null
@@ -1,50 +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>
- geda:simple1.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:ngspice_and_gschem?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:ngspice_and_gschem"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:ngspice_and_gschem"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:simple1.png</h1>
-
- <div class="img_big">
- <a href="../_media/geda_simple1.png"><img src="../_media/geda_simple1.png" width="828" height="558" class="img_detail" alt="simple1.png" title="simple1.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:ngspice_and_gschem"; class="wikilink1" title="geda:ngspice_and_gschem">ngspice_and_gschem</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>simple1.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>8KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/geda_status_screenshot.html b/docs/wiki/_detail/geda_status_screenshot.html
deleted file mode 100644
index 6db4e31..0000000
--- a/docs/wiki/_detail/geda_status_screenshot.html
+++ /dev/null
@@ -1,50 +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>
- geda:status_screenshot.jpg [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:gschem_ug?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gschem_ug"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gschem_ug"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:status_screenshot.jpg</h1>
-
- <div class="img_big">
- <a href="../_media/geda_status_screenshot.jpg"><img src="../_media/geda_status_screenshot.jpg" width="612" height="367" class="img_detail" alt="status_screenshot.jpg" title="status_screenshot.jpg" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:gschem_ug"; class="wikilink1" title="geda:gschem_ug">gschem_ug</a></span></p>
-
- <dl class="img_tags">
- <dt>Date:</dt><dd>2007/05/24 22:27</dd><dt>Filename:</dt><dd>status_screenshot.jpg</dd><dt>Format:</dt><dd>JPEG</dd><dt>Size:</dt><dd>136KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/geda_suse_electronics_menu.html b/docs/wiki/_detail/geda_suse_electronics_menu.html
deleted file mode 100644
index a96f841..0000000
--- a/docs/wiki/_detail/geda_suse_electronics_menu.html
+++ /dev/null
@@ -1,50 +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>
- geda:suse_electronics_menu.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:suse_rpm_installation?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:suse_rpm_installation"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:suse_rpm_installation"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:suse_electronics_menu.png</h1>
-
- <div class="img_big">
- <a href="../_media/geda_suse_electronics_menu.png"><img src="../_media/geda_suse_electronics_menu.png" width="636" height="384" class="img_detail" alt="suse_electronics_menu.png" title="suse_electronics_menu.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:suse_rpm_installation"; class="wikilink1" title="geda:suse_rpm_installation">suse_rpm_installation</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>suse_electronics_menu.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>53KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/geda_switcap_figure1.html b/docs/wiki/_detail/geda_switcap_figure1.html
deleted file mode 100644
index a2dc995..0000000
--- a/docs/wiki/_detail/geda_switcap_figure1.html
+++ /dev/null
@@ -1,50 +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>
- geda:switcap_figure1.jpg [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:ssan?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:ssan"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:ssan"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:switcap_figure1.jpg</h1>
-
- <div class="img_big">
- <a href="../_media/geda_switcap_figure1.jpg"><img src="../_media/geda_switcap_figure1.jpg" width="633" height="561" class="img_detail" alt="switcap_figure1.jpg" title="switcap_figure1.jpg" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:ssan"; class="wikilink1" title="geda:ssan">ssan</a></span></p>
-
- <dl class="img_tags">
- <dt>Date:</dt><dd>2007/05/24 22:27</dd><dt>Filename:</dt><dd>switcap_figure1.jpg</dd><dt>Format:</dt><dd>JPEG</dd><dt>Size:</dt><dd>26KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/geda_switcap_figure2.html b/docs/wiki/_detail/geda_switcap_figure2.html
deleted file mode 100644
index 7cdc117..0000000
--- a/docs/wiki/_detail/geda_switcap_figure2.html
+++ /dev/null
@@ -1,50 +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>
- geda:switcap_figure2.jpg [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:ssan?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:ssan"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:ssan"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:switcap_figure2.jpg</h1>
-
- <div class="img_big">
- <a href="../_media/geda_switcap_figure2.jpg"><img src="../_media/geda_switcap_figure2.jpg" width="631" height="559" class="img_detail" alt="switcap_figure2.jpg" title="switcap_figure2.jpg" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:ssan"; class="wikilink1" title="geda:ssan">ssan</a></span></p>
-
- <dl class="img_tags">
- <dt>Date:</dt><dd>2007/05/24 22:27</dd><dt>Filename:</dt><dd>switcap_figure2.jpg</dd><dt>Format:</dt><dd>JPEG</dd><dt>Size:</dt><dd>25KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/geda_switcap_figure3.html b/docs/wiki/_detail/geda_switcap_figure3.html
deleted file mode 100644
index 04fea96..0000000
--- a/docs/wiki/_detail/geda_switcap_figure3.html
+++ /dev/null
@@ -1,50 +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>
- geda:switcap_figure3.jpg [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:ssan?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:ssan"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:ssan"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:switcap_figure3.jpg</h1>
-
- <div class="img_big">
- <a href="../_media/geda_switcap_figure3.jpg"><img src="../_media/geda_switcap_figure3.jpg" width="632" height="562" class="img_detail" alt="switcap_figure3.jpg" title="switcap_figure3.jpg" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:ssan"; class="wikilink1" title="geda:ssan">ssan</a></span></p>
-
- <dl class="img_tags">
- <dt>Date:</dt><dd>2007/05/24 22:27</dd><dt>Filename:</dt><dd>switcap_figure3.jpg</dd><dt>Format:</dt><dd>JPEG</dd><dt>Size:</dt><dd>31KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/geda_switcap_figure4.html b/docs/wiki/_detail/geda_switcap_figure4.html
deleted file mode 100644
index c1374a9..0000000
--- a/docs/wiki/_detail/geda_switcap_figure4.html
+++ /dev/null
@@ -1,50 +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>
- geda:switcap_figure4.jpg [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:ssan?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:ssan"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:ssan"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:switcap_figure4.jpg</h1>
-
- <div class="img_big">
- <a href="../_media/geda_switcap_figure4.jpg"><img src="../_media/geda_switcap_figure4.jpg" width="691" height="366" class="img_detail" alt="switcap_figure4.jpg" title="switcap_figure4.jpg" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:ssan"; class="wikilink1" title="geda:ssan">ssan</a></span></p>
-
- <dl class="img_tags">
- <dt>Date:</dt><dd>2007/05/24 22:27</dd><dt>Filename:</dt><dd>switcap_figure4.jpg</dd><dt>Format:</dt><dd>JPEG</dd><dt>Size:</dt><dd>29KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/geda_symbol_7400-1.html b/docs/wiki/_detail/geda_symbol_7400-1.html
deleted file mode 100644
index f66c673..0000000
--- a/docs/wiki/_detail/geda_symbol_7400-1.html
+++ /dev/null
@@ -1,50 +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>
- geda:symbol_7400-1.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:scg?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:scg"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:scg"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:symbol_7400-1.png</h1>
-
- <div class="img_big">
- <a href="../_media/geda_symbol_7400-1.png"><img src="../_media/geda_symbol_7400-1.png" width="443" height="274" class="img_detail" alt="symbol_7400-1.png" title="symbol_7400-1.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:scg"; class="wikilink1" title="geda:scg">scg</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>symbol_7400-1.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>5KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/geda_symbol_7400-1_hidden.html b/docs/wiki/_detail/geda_symbol_7400-1_hidden.html
deleted file mode 100644
index 4cf41f3..0000000
--- a/docs/wiki/_detail/geda_symbol_7400-1_hidden.html
+++ /dev/null
@@ -1,50 +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>
- geda:symbol_7400-1_hidden.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:scg?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:scg"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:scg"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:symbol_7400-1_hidden.png</h1>
-
- <div class="img_big">
- <a href="../_media/geda_symbol_7400-1_hidden.png"><img src="../_media/geda_symbol_7400-1_hidden.png" width="383" height="305" class="img_detail" alt="symbol_7400-1_hidden.png" title="symbol_7400-1_hidden.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:scg"; class="wikilink1" title="geda:scg">scg</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>symbol_7400-1_hidden.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>3KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/geda_terminal_screenshot_001.html b/docs/wiki/_detail/geda_terminal_screenshot_001.html
deleted file mode 100644
index 8ca2588..0000000
--- a/docs/wiki/_detail/geda_terminal_screenshot_001.html
+++ /dev/null
@@ -1,50 +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>
- geda:terminal_screenshot_001.jpg [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:gschem_ug?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gschem_ug"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gschem_ug"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:terminal_screenshot_001.jpg</h1>
-
- <div class="img_big">
- <a href="../_media/geda_terminal_screenshot_.jpg"><img src="../_media/geda_terminal_screenshot_001.jpg" width="589" height="417" class="img_detail" alt="terminal_screenshot_001.jpg" title="terminal_screenshot_001.jpg" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:gschem_ug"; class="wikilink1" title="geda:gschem_ug">gschem_ug</a></span></p>
-
- <dl class="img_tags">
- <dt>Date:</dt><dd>2007/05/24 22:27</dd><dt>Filename:</dt><dd>terminal_screenshot_001.jpg</dd><dt>Format:</dt><dd>JPEG</dd><dt>Size:</dt><dd>65KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/geda_two-sch-1.html b/docs/wiki/_detail/geda_two-sch-1.html
deleted file mode 100644
index 373e6e9..0000000
--- a/docs/wiki/_detail/geda_two-sch-1.html
+++ /dev/null
@@ -1,50 +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>
- geda:two-sch-1.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:gsch2pcb_tutorial?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gsch2pcb_tutorial"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gsch2pcb_tutorial"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:two-sch-1.png</h1>
-
- <div class="img_big">
- <a href="../_media/geda_two-sch-1.png"><img src="../_media/geda_two-sch-1.png" width="280" height="293" class="img_detail" alt="two-sch-1.png" title="two-sch-1.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:gsch2pcb_tutorial"; class="wikilink1" title="geda:gsch2pcb_tutorial">gsch2pcb_tutorial</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>two-sch-1.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>4KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/geda_two-sch-2.html b/docs/wiki/_detail/geda_two-sch-2.html
deleted file mode 100644
index fcc5906..0000000
--- a/docs/wiki/_detail/geda_two-sch-2.html
+++ /dev/null
@@ -1,50 +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>
- geda:two-sch-2.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:gsch2pcb_tutorial?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gsch2pcb_tutorial"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gsch2pcb_tutorial"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:two-sch-2.png</h1>
-
- <div class="img_big">
- <a href="../_media/geda_two-sch-2.png"><img src="../_media/geda_two-sch-2.png" width="237" height="288" class="img_detail" alt="two-sch-2.png" title="two-sch-2.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:gsch2pcb_tutorial"; class="wikilink1" title="geda:gsch2pcb_tutorial">gsch2pcb_tutorial</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>two-sch-2.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>4KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/geda_warmup_add_component.html b/docs/wiki/_detail/geda_warmup_add_component.html
deleted file mode 100644
index 8a5fb35..0000000
--- a/docs/wiki/_detail/geda_warmup_add_component.html
+++ /dev/null
@@ -1,50 +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>
- geda:warmup_add_component.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:gschem_warmup?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gschem_warmup"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gschem_warmup"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:warmup_add_component.png</h1>
-
- <div class="img_big">
- <a href="../_media/geda_warmup_add_component.png"><img src="../_media/geda_warmup_add_component.png" width="23" height="14" class="img_detail" alt="warmup_add_component.png" title="warmup_add_component.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:gschem_warmup"; class="wikilink1" title="geda:gschem_warmup">gschem_warmup</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>warmup_add_component.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>221B</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/geda_warmup_gschem01.html b/docs/wiki/_detail/geda_warmup_gschem01.html
deleted file mode 100644
index 786c174..0000000
--- a/docs/wiki/_detail/geda_warmup_gschem01.html
+++ /dev/null
@@ -1,50 +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>
- geda:warmup_gschem01.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:gschem_warmup?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gschem_warmup"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gschem_warmup"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:warmup_gschem01.png</h1>
-
- <div class="img_big">
- <a href="../_media/geda_warmup_gschem01.png"><img src="../_media/geda_warmup_gschem01.png" width="810" height="591" class="img_detail" alt="warmup_gschem01.png" title="warmup_gschem01.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:gschem_warmup"; class="wikilink1" title="geda:gschem_warmup">gschem_warmup</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>warmup_gschem01.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>21KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/geda_warmup_gschem02.html b/docs/wiki/_detail/geda_warmup_gschem02.html
deleted file mode 100644
index 84ee288..0000000
--- a/docs/wiki/_detail/geda_warmup_gschem02.html
+++ /dev/null
@@ -1,50 +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>
- geda:warmup_gschem02.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:gschem_warmup?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gschem_warmup"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gschem_warmup"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:warmup_gschem02.png</h1>
-
- <div class="img_big">
- <a href="../_media/geda_warmup_gschem02.png"><img src="../_media/geda_warmup_gschem02.png" width="810" height="591" class="img_detail" alt="warmup_gschem02.png" title="warmup_gschem02.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:gschem_warmup"; class="wikilink1" title="geda:gschem_warmup">gschem_warmup</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>warmup_gschem02.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>22KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/geda_warmup_gschem03.html b/docs/wiki/_detail/geda_warmup_gschem03.html
deleted file mode 100644
index df23d82..0000000
--- a/docs/wiki/_detail/geda_warmup_gschem03.html
+++ /dev/null
@@ -1,50 +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>
- geda:warmup_gschem03.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:gschem_warmup?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gschem_warmup"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gschem_warmup"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>geda:warmup_gschem03.png</h1>
-
- <div class="img_big">
- <a href="../_media/geda_warmup_gschem03.png"><img src="../_media/geda_warmup_gschem03.png" width="810" height="591" class="img_detail" alt="warmup_gschem03.png" title="warmup_gschem03.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:gschem_warmup"; class="wikilink1" title="geda:gschem_warmup">gschem_warmup</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>warmup_gschem03.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>22KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/tragesym_acroread_selectiontable.html b/docs/wiki/_detail/tragesym_acroread_selectiontable.html
deleted file mode 100644
index a304002..0000000
--- a/docs/wiki/_detail/tragesym_acroread_selectiontable.html
+++ /dev/null
@@ -1,50 +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>
- tragesym:acroread_selectiontable.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:tragesym_tutorial?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:tragesym_tutorial"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:tragesym_tutorial"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>tragesym:acroread_selectiontable.png</h1>
-
- <div class="img_big">
- <a href="../_media/tragesym_acroread_selectiontable.png"><img src="../_media/tragesym_acroread_selectiontable.png" width="375" height="371" class="img_detail" alt="acroread_selectiontable.png" title="acroread_selectiontable.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:tragesym_tutorial"; class="wikilink1" title="geda:tragesym_tutorial">tragesym_tutorial</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>acroread_selectiontable.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>20KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/tragesym_gschem_finished.html b/docs/wiki/_detail/tragesym_gschem_finished.html
deleted file mode 100644
index 97e7b03..0000000
--- a/docs/wiki/_detail/tragesym_gschem_finished.html
+++ /dev/null
@@ -1,50 +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>
- tragesym:gschem_finished.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:tragesym_tutorial?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:tragesym_tutorial"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:tragesym_tutorial"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>tragesym:gschem_finished.png</h1>
-
- <div class="img_big">
- <a href="../_media/tragesym_gschem_finished.png"><img src="../_media/tragesym_gschem_finished.png" width="180" height="700" class="img_detail" alt="gschem_finished.png" title="gschem_finished.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:tragesym_tutorial"; class="wikilink1" title="geda:tragesym_tutorial">tragesym_tutorial</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>gschem_finished.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>5KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/tragesym_gschem_showhidden.html b/docs/wiki/_detail/tragesym_gschem_showhidden.html
deleted file mode 100644
index cce51a3..0000000
--- a/docs/wiki/_detail/tragesym_gschem_showhidden.html
+++ /dev/null
@@ -1,50 +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>
- tragesym:gschem_showhidden.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:tragesym_tutorial?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:tragesym_tutorial"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:tragesym_tutorial"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>tragesym:gschem_showhidden.png</h1>
-
- <div class="img_big">
- <a href="../_media/tragesym_gschem_showhidden.png"><img src="../_media/tragesym_gschem_showhidden.png" width="232" height="700" class="img_detail" alt="gschem_showhidden.png" title="gschem_showhidden.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:tragesym_tutorial"; class="wikilink1" title="geda:tragesym_tutorial">tragesym_tutorial</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>gschem_showhidden.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>10KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/tragesym_kpdf_pinconfiguration.html b/docs/wiki/_detail/tragesym_kpdf_pinconfiguration.html
deleted file mode 100644
index 9ae306d..0000000
--- a/docs/wiki/_detail/tragesym_kpdf_pinconfiguration.html
+++ /dev/null
@@ -1,50 +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>
- tragesym:kpdf_pinconfiguration.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:tragesym_tutorial?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:tragesym_tutorial"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:tragesym_tutorial"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>tragesym:kpdf_pinconfiguration.png</h1>
-
- <div class="img_big">
- <a href="../_media/tragesym_kpdf_pinconfiguration.png"><img src="../_media/tragesym_kpdf_pinconfiguration.png" width="504" height="371" class="img_detail" alt="kpdf_pinconfiguration.png" title="kpdf_pinconfiguration.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:tragesym_tutorial"; class="wikilink1" title="geda:tragesym_tutorial">tragesym_tutorial</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>kpdf_pinconfiguration.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>43KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/tragesym_kpdf_pindescription.html b/docs/wiki/_detail/tragesym_kpdf_pindescription.html
deleted file mode 100644
index 2d8cee8..0000000
--- a/docs/wiki/_detail/tragesym_kpdf_pindescription.html
+++ /dev/null
@@ -1,50 +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>
- tragesym:kpdf_pindescription.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:tragesym_tutorial?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:tragesym_tutorial"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:tragesym_tutorial"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>tragesym:kpdf_pindescription.png</h1>
-
- <div class="img_big">
- <a href="../_media/tragesym_kpdf_pindescription.png"><img src="../_media/tragesym_kpdf_pindescription.png" width="670" height="235" class="img_detail" alt="kpdf_pindescription.png" title="kpdf_pindescription.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:tragesym_tutorial"; class="wikilink1" title="geda:tragesym_tutorial">tragesym_tutorial</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>kpdf_pindescription.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>31KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/tragesym_ooo_attributes.html b/docs/wiki/_detail/tragesym_ooo_attributes.html
deleted file mode 100644
index d749ea1..0000000
--- a/docs/wiki/_detail/tragesym_ooo_attributes.html
+++ /dev/null
@@ -1,50 +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>
- tragesym:ooo_attributes.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:tragesym_tutorial?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:tragesym_tutorial"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:tragesym_tutorial"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>tragesym:ooo_attributes.png</h1>
-
- <div class="img_big">
- <a href="../_media/tragesym_ooo_attributes.png"><img src="../_media/tragesym_ooo_attributes.png" width="723" height="398" class="img_detail" alt="ooo_attributes.png" title="ooo_attributes.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:tragesym_tutorial"; class="wikilink1" title="geda:tragesym_tutorial">tragesym_tutorial</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>ooo_attributes.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>47KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/tragesym_ooo_changedpins.html b/docs/wiki/_detail/tragesym_ooo_changedpins.html
deleted file mode 100644
index 2d2f686..0000000
--- a/docs/wiki/_detail/tragesym_ooo_changedpins.html
+++ /dev/null
@@ -1,50 +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>
- tragesym:ooo_changedpins.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:tragesym_tutorial?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:tragesym_tutorial"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:tragesym_tutorial"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>tragesym:ooo_changedpins.png</h1>
-
- <div class="img_big">
- <a href="../_media/tragesym_ooo_changedpins.png"><img src="../_media/tragesym_ooo_changedpins.png" width="575" height="336" class="img_detail" alt="ooo_changedpins.png" title="ooo_changedpins.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:tragesym_tutorial"; class="wikilink1" title="geda:tragesym_tutorial">tragesym_tutorial</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>ooo_changedpins.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>21KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/tragesym_ooo_rearanged.html b/docs/wiki/_detail/tragesym_ooo_rearanged.html
deleted file mode 100644
index 9708593..0000000
--- a/docs/wiki/_detail/tragesym_ooo_rearanged.html
+++ /dev/null
@@ -1,50 +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>
- tragesym:ooo_rearanged.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:tragesym_tutorial?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:tragesym_tutorial"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:tragesym_tutorial"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>tragesym:ooo_rearanged.png</h1>
-
- <div class="img_big">
- <a href="../_media/tragesym_ooo_rearanged.png"><img src="../_media/tragesym_ooo_rearanged.png" width="584" height="553" class="img_detail" alt="ooo_rearanged.png" title="ooo_rearanged.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:tragesym_tutorial"; class="wikilink1" title="geda:tragesym_tutorial">tragesym_tutorial</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>ooo_rearanged.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>41KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/tragesym_ooo_selection.html b/docs/wiki/_detail/tragesym_ooo_selection.html
deleted file mode 100644
index 9b31f68..0000000
--- a/docs/wiki/_detail/tragesym_ooo_selection.html
+++ /dev/null
@@ -1,50 +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>
- tragesym:ooo_selection.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:tragesym_tutorial?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:tragesym_tutorial"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:tragesym_tutorial"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>tragesym:ooo_selection.png</h1>
-
- <div class="img_big">
- <a href="../_media/tragesym_ooo_selection.png"><img src="../_media/tragesym_ooo_selection.png" width="335" height="383" class="img_detail" alt="ooo_selection.png" title="ooo_selection.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:tragesym_tutorial"; class="wikilink1" title="geda:tragesym_tutorial">tragesym_tutorial</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>ooo_selection.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>9KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/tragesym_xemacs_modifiedselection.html b/docs/wiki/_detail/tragesym_xemacs_modifiedselection.html
deleted file mode 100644
index 6a83c75..0000000
--- a/docs/wiki/_detail/tragesym_xemacs_modifiedselection.html
+++ /dev/null
@@ -1,50 +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>
- tragesym:xemacs_modifiedselection.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:tragesym_tutorial?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:tragesym_tutorial"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:tragesym_tutorial"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>tragesym:xemacs_modifiedselection.png</h1>
-
- <div class="img_big">
- <a href="../_media/tragesym_xemacs_modifiedselection.png"><img src="../_media/tragesym_xemacs_modifiedselection.png" width="163" height="383" class="img_detail" alt="xemacs_modifiedselection.png" title="xemacs_modifiedselection.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:tragesym_tutorial"; class="wikilink1" title="geda:tragesym_tutorial">tragesym_tutorial</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>xemacs_modifiedselection.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>3KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_detail/tragesym_xemacs_rawselection.html b/docs/wiki/_detail/tragesym_xemacs_rawselection.html
deleted file mode 100644
index f13967f..0000000
--- a/docs/wiki/_detail/tragesym_xemacs_rawselection.html
+++ /dev/null
@@ -1,50 +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>
- tragesym:xemacs_rawselection.png [geda Wiki]
- </title>
-
- <meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/geda:tragesym_tutorial?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:tragesym_tutorial"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:tragesym_tutorial"; />
-<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" />
-
- <link rel="shortcut icon" href="../lib/tpl/geda/images/favicon" />
-</head>
-
-<body>
-<div class="dokuwiki">
-
- <div class="page">
-
- <h1>tragesym:xemacs_rawselection.png</h1>
-
- <div class="img_big">
- <a href="../_media/tragesym_xemacs_rawselection.png"><img src="../_media/tragesym_xemacs_rawselection.png" width="168" height="384" class="img_detail" alt="xemacs_rawselection.png" title="xemacs_rawselection.png" /></a> </div>
-
- <div class="img_detail">
- <p class="img_caption">
- </p>
-
- <p>← Back to <span class="curid"><a href="http://geda.seul.org/wiki/geda:tragesym_tutorial"; class="wikilink1" title="geda:tragesym_tutorial">tragesym_tutorial</a></span></p>
-
- <dl class="img_tags">
- <dt>Filename:</dt><dd>xemacs_rawselection.png</dd><dt>Format:</dt><dd>PNG</dd><dt>Size:</dt><dd>6KB</dd> </dl>
- </div>
-
- </div>
-</div>
-</body>
-</html>
-
diff --git a/docs/wiki/_media/.gitignore b/docs/wiki/_media/.gitignore
deleted file mode 100644
index 23c1897..0000000
--- a/docs/wiki/_media/.gitignore
+++ /dev/null
@@ -1,3 +0,0 @@
-Makefile
-Makefile.in
-*~
diff --git a/docs/wiki/_media/001tragesym_template b/docs/wiki/_media/001tragesym_template
deleted file mode 100644
index 425e9af..0000000
Binary files a/docs/wiki/_media/001tragesym_template and /dev/null differ
diff --git a/docs/wiki/_media/Makefile.am b/docs/wiki/_media/Makefile.am
deleted file mode 100644
index 02832de..0000000
--- a/docs/wiki/_media/Makefile.am
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-docname=wiki
-docsdir = $(docdir)/$(docname)/_media
-
-docs_DATA = geda_dialogtrans.png geda_one-sch-2.png geda_fileformat_textgraphic.jpg geda_switcap_figure2.jpg geda_board-2.png geda_pcb-el-2.png 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_suse_electronics_menu.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_dialogdirective.png geda_dialogmodel.png geda_geda_flow.png geda_symbol_7400-1.png devel_tips_dialog_picture.png geda_board-4.png geda_schematicfinished2.png tragesym_acroread_selectiontable.png geda_coordinatespace.jpg tragesym_xemacs_modifiedselection.png geda_warmup_gschem02.png geda_warmup_gschem03.png geda_dialogvac.png geda_dialoginclude.png geda_simple1.png tragesym_template geda_symbol_7400-1_hidden.png geda_rf_cascade_figure1.jpg geda_dialogvdc1.png tragesym_gschem_finished.png tragesym_kpdf_pindescription.png geda_board-1.png
-
-EXTRA_DIST = $(docs_DATA)
-
-MAINTAINERCLEANFILES = *.log core FILE *~ Makefile.in
-
diff --git a/docs/wiki/_media/devel_tips_dialog_picture.png b/docs/wiki/_media/devel_tips_dialog_picture.png
deleted file mode 100644
index 3108609..0000000
Binary files a/docs/wiki/_media/devel_tips_dialog_picture.png and /dev/null differ
diff --git a/docs/wiki/_media/geda_ambiguous1.png b/docs/wiki/_media/geda_ambiguous1.png
deleted file mode 100644
index 29ffddb..0000000
Binary files a/docs/wiki/_media/geda_ambiguous1.png and /dev/null differ
diff --git a/docs/wiki/_media/geda_ambiguous1_fixed.png b/docs/wiki/_media/geda_ambiguous1_fixed.png
deleted file mode 100644
index ae3dc52..0000000
Binary files a/docs/wiki/_media/geda_ambiguous1_fixed.png and /dev/null differ
diff --git a/docs/wiki/_media/geda_board-1.png b/docs/wiki/_media/geda_board-1.png
deleted file mode 100644
index 6189478..0000000
Binary files a/docs/wiki/_media/geda_board-1.png and /dev/null differ
diff --git a/docs/wiki/_media/geda_board-2.png b/docs/wiki/_media/geda_board-2.png
deleted file mode 100644
index 62c351c..0000000
Binary files a/docs/wiki/_media/geda_board-2.png and /dev/null differ
diff --git a/docs/wiki/_media/geda_board-3.png b/docs/wiki/_media/geda_board-3.png
deleted file mode 100644
index f0406e3..0000000
Binary files a/docs/wiki/_media/geda_board-3.png and /dev/null differ
diff --git a/docs/wiki/_media/geda_board-4.png b/docs/wiki/_media/geda_board-4.png
deleted file mode 100644
index ec6eba5..0000000
Binary files a/docs/wiki/_media/geda_board-4.png and /dev/null differ
diff --git a/docs/wiki/_media/geda_board-5.png b/docs/wiki/_media/geda_board-5.png
deleted file mode 100644
index 57ff80d..0000000
Binary files a/docs/wiki/_media/geda_board-5.png and /dev/null differ
diff --git a/docs/wiki/_media/geda_board-6.png b/docs/wiki/_media/geda_board-6.png
deleted file mode 100644
index 0e1189a..0000000
Binary files a/docs/wiki/_media/geda_board-6.png and /dev/null differ
diff --git a/docs/wiki/_media/geda_coordinatespace.jpg b/docs/wiki/_media/geda_coordinatespace.jpg
deleted file mode 100644
index 83b57fc..0000000
Binary files a/docs/wiki/_media/geda_coordinatespace.jpg and /dev/null differ
diff --git a/docs/wiki/_media/geda_design_flow.jpg b/docs/wiki/_media/geda_design_flow.jpg
deleted file mode 100644
index 0d6f152..0000000
Binary files a/docs/wiki/_media/geda_design_flow.jpg and /dev/null differ
diff --git a/docs/wiki/_media/geda_dialogdirective.png b/docs/wiki/_media/geda_dialogdirective.png
deleted file mode 100644
index e1f21db..0000000
Binary files a/docs/wiki/_media/geda_dialogdirective.png and /dev/null differ
diff --git a/docs/wiki/_media/geda_dialoginclude.png b/docs/wiki/_media/geda_dialoginclude.png
deleted file mode 100644
index 5d300bd..0000000
Binary files a/docs/wiki/_media/geda_dialoginclude.png and /dev/null differ
diff --git a/docs/wiki/_media/geda_dialogmodel.png b/docs/wiki/_media/geda_dialogmodel.png
deleted file mode 100644
index 49e8e42..0000000
Binary files a/docs/wiki/_media/geda_dialogmodel.png and /dev/null differ
diff --git a/docs/wiki/_media/geda_dialogtrans.png b/docs/wiki/_media/geda_dialogtrans.png
deleted file mode 100644
index 4a7f9a1..0000000
Binary files a/docs/wiki/_media/geda_dialogtrans.png and /dev/null differ
diff --git a/docs/wiki/_media/geda_dialogvac.png b/docs/wiki/_media/geda_dialogvac.png
deleted file mode 100644
index 744893e..0000000
Binary files a/docs/wiki/_media/geda_dialogvac.png and /dev/null differ
diff --git a/docs/wiki/_media/geda_dialogvdc1.png b/docs/wiki/_media/geda_dialogvdc1.png
deleted file mode 100644
index 3e16535..0000000
Binary files a/docs/wiki/_media/geda_dialogvdc1.png and /dev/null differ
diff --git a/docs/wiki/_media/geda_faq_attrib.jpg b/docs/wiki/_media/geda_faq_attrib.jpg
deleted file mode 100644
index cca6286..0000000
Binary files a/docs/wiki/_media/geda_faq_attrib.jpg and /dev/null differ
diff --git a/docs/wiki/_media/geda_fileformat_textgraphic.jpg b/docs/wiki/_media/geda_fileformat_textgraphic.jpg
deleted file mode 100644
index 1f49c1c..0000000
Binary files a/docs/wiki/_media/geda_fileformat_textgraphic.jpg and /dev/null differ
diff --git a/docs/wiki/_media/geda_geda_flow.png b/docs/wiki/_media/geda_geda_flow.png
deleted file mode 100644
index 79fbf9f..0000000
Binary files a/docs/wiki/_media/geda_geda_flow.png and /dev/null differ
diff --git a/docs/wiki/_media/geda_gschem-sym-1.png b/docs/wiki/_media/geda_gschem-sym-1.png
deleted file mode 100644
index dfae00a..0000000
Binary files a/docs/wiki/_media/geda_gschem-sym-1.png and /dev/null differ
diff --git a/docs/wiki/_media/geda_gschem-sym-2.png b/docs/wiki/_media/geda_gschem-sym-2.png
deleted file mode 100644
index dfc7d84..0000000
Binary files a/docs/wiki/_media/geda_gschem-sym-2.png and /dev/null differ
diff --git a/docs/wiki/_media/geda_gschem-sym-3.png b/docs/wiki/_media/geda_gschem-sym-3.png
deleted file mode 100644
index b76217d..0000000
Binary files a/docs/wiki/_media/geda_gschem-sym-3.png and /dev/null differ
diff --git a/docs/wiki/_media/geda_gschem_screenshot_001.jpg b/docs/wiki/_media/geda_gschem_screenshot_001.jpg
deleted file mode 100644
index 2e0cf68..0000000
Binary files a/docs/wiki/_media/geda_gschem_screenshot_001.jpg and /dev/null differ
diff --git a/docs/wiki/_media/geda_gschem_workflow_01.jpg b/docs/wiki/_media/geda_gschem_workflow_01.jpg
deleted file mode 100644
index d1326bc..0000000
Binary files a/docs/wiki/_media/geda_gschem_workflow_01.jpg and /dev/null differ
diff --git a/docs/wiki/_media/geda_net.jpg b/docs/wiki/_media/geda_net.jpg
deleted file mode 100644
index 3311666..0000000
Binary files a/docs/wiki/_media/geda_net.jpg and /dev/null differ
diff --git a/docs/wiki/_media/geda_nets.jpg b/docs/wiki/_media/geda_nets.jpg
deleted file mode 100644
index 264690e..0000000
Binary files a/docs/wiki/_media/geda_nets.jpg and /dev/null differ
diff --git a/docs/wiki/_media/geda_one-sch-1.png b/docs/wiki/_media/geda_one-sch-1.png
deleted file mode 100644
index 3824b47..0000000
Binary files a/docs/wiki/_media/geda_one-sch-1.png and /dev/null differ
diff --git a/docs/wiki/_media/geda_one-sch-2.png b/docs/wiki/_media/geda_one-sch-2.png
deleted file mode 100644
index 9028fc2..0000000
Binary files a/docs/wiki/_media/geda_one-sch-2.png and /dev/null differ
diff --git a/docs/wiki/_media/geda_one-sch-3.png b/docs/wiki/_media/geda_one-sch-3.png
deleted file mode 100644
index 82e65ea..0000000
Binary files a/docs/wiki/_media/geda_one-sch-3.png and /dev/null differ
diff --git a/docs/wiki/_media/geda_pcb-el-1.png b/docs/wiki/_media/geda_pcb-el-1.png
deleted file mode 100644
index 84d5bc3..0000000
Binary files a/docs/wiki/_media/geda_pcb-el-1.png and /dev/null differ
diff --git a/docs/wiki/_media/geda_pcb-el-2.png b/docs/wiki/_media/geda_pcb-el-2.png
deleted file mode 100644
index 41d7322..0000000
Binary files a/docs/wiki/_media/geda_pcb-el-2.png and /dev/null differ
diff --git a/docs/wiki/_media/geda_rf_cascade_figure1.jpg b/docs/wiki/_media/geda_rf_cascade_figure1.jpg
deleted file mode 100644
index 2521dfe..0000000
Binary files a/docs/wiki/_media/geda_rf_cascade_figure1.jpg and /dev/null differ
diff --git a/docs/wiki/_media/geda_rf_cascade_figure2.jpg b/docs/wiki/_media/geda_rf_cascade_figure2.jpg
deleted file mode 100644
index b271a65..0000000
Binary files a/docs/wiki/_media/geda_rf_cascade_figure2.jpg and /dev/null differ
diff --git a/docs/wiki/_media/geda_schematicfinished2.png b/docs/wiki/_media/geda_schematicfinished2.png
deleted file mode 100644
index 6a381b7..0000000
Binary files a/docs/wiki/_media/geda_schematicfinished2.png and /dev/null differ
diff --git a/docs/wiki/_media/geda_simple1.png b/docs/wiki/_media/geda_simple1.png
deleted file mode 100644
index a7fce1e..0000000
Binary files a/docs/wiki/_media/geda_simple1.png and /dev/null differ
diff --git a/docs/wiki/_media/geda_status_screenshot.jpg b/docs/wiki/_media/geda_status_screenshot.jpg
deleted file mode 100644
index 394ef3a..0000000
Binary files a/docs/wiki/_media/geda_status_screenshot.jpg and /dev/null differ
diff --git a/docs/wiki/_media/geda_suse_electronics_menu.png b/docs/wiki/_media/geda_suse_electronics_menu.png
deleted file mode 100644
index 16881ed..0000000
Binary files a/docs/wiki/_media/geda_suse_electronics_menu.png and /dev/null differ
diff --git a/docs/wiki/_media/geda_switcap_figure1.jpg b/docs/wiki/_media/geda_switcap_figure1.jpg
deleted file mode 100644
index 5313e53..0000000
Binary files a/docs/wiki/_media/geda_switcap_figure1.jpg and /dev/null differ
diff --git a/docs/wiki/_media/geda_switcap_figure2.jpg b/docs/wiki/_media/geda_switcap_figure2.jpg
deleted file mode 100644
index b9e0f6a..0000000
Binary files a/docs/wiki/_media/geda_switcap_figure2.jpg and /dev/null differ
diff --git a/docs/wiki/_media/geda_switcap_figure3.jpg b/docs/wiki/_media/geda_switcap_figure3.jpg
deleted file mode 100644
index 6617c00..0000000
Binary files a/docs/wiki/_media/geda_switcap_figure3.jpg and /dev/null differ
diff --git a/docs/wiki/_media/geda_switcap_figure4.jpg b/docs/wiki/_media/geda_switcap_figure4.jpg
deleted file mode 100644
index 639985b..0000000
Binary files a/docs/wiki/_media/geda_switcap_figure4.jpg and /dev/null differ
diff --git a/docs/wiki/_media/geda_symbol_7400-1.png b/docs/wiki/_media/geda_symbol_7400-1.png
deleted file mode 100644
index e817f55..0000000
Binary files a/docs/wiki/_media/geda_symbol_7400-1.png and /dev/null differ
diff --git a/docs/wiki/_media/geda_symbol_7400-1_hidden.png b/docs/wiki/_media/geda_symbol_7400-1_hidden.png
deleted file mode 100644
index 22807da..0000000
Binary files a/docs/wiki/_media/geda_symbol_7400-1_hidden.png and /dev/null differ
diff --git a/docs/wiki/_media/geda_terminal_screenshot_001.jpg b/docs/wiki/_media/geda_terminal_screenshot_001.jpg
deleted file mode 100644
index 1b28256..0000000
Binary files a/docs/wiki/_media/geda_terminal_screenshot_001.jpg and /dev/null differ
diff --git a/docs/wiki/_media/geda_two-sch-1.png b/docs/wiki/_media/geda_two-sch-1.png
deleted file mode 100644
index 74b59c9..0000000
Binary files a/docs/wiki/_media/geda_two-sch-1.png and /dev/null differ
diff --git a/docs/wiki/_media/geda_two-sch-2.png b/docs/wiki/_media/geda_two-sch-2.png
deleted file mode 100644
index 9448d26..0000000
Binary files a/docs/wiki/_media/geda_two-sch-2.png and /dev/null differ
diff --git a/docs/wiki/_media/geda_warmup_add_component.png b/docs/wiki/_media/geda_warmup_add_component.png
deleted file mode 100644
index cfd5794..0000000
Binary files a/docs/wiki/_media/geda_warmup_add_component.png and /dev/null differ
diff --git a/docs/wiki/_media/geda_warmup_gschem01.png b/docs/wiki/_media/geda_warmup_gschem01.png
deleted file mode 100644
index 1191d90..0000000
Binary files a/docs/wiki/_media/geda_warmup_gschem01.png and /dev/null differ
diff --git a/docs/wiki/_media/geda_warmup_gschem02.png b/docs/wiki/_media/geda_warmup_gschem02.png
deleted file mode 100644
index af49239..0000000
Binary files a/docs/wiki/_media/geda_warmup_gschem02.png and /dev/null differ
diff --git a/docs/wiki/_media/geda_warmup_gschem03.png b/docs/wiki/_media/geda_warmup_gschem03.png
deleted file mode 100644
index e9da8d3..0000000
Binary files a/docs/wiki/_media/geda_warmup_gschem03.png and /dev/null differ
diff --git a/docs/wiki/_media/tragesym_acroread_selectiontable.png b/docs/wiki/_media/tragesym_acroread_selectiontable.png
deleted file mode 100644
index 796cd9b..0000000
Binary files a/docs/wiki/_media/tragesym_acroread_selectiontable.png and /dev/null differ
diff --git a/docs/wiki/_media/tragesym_gschem_finished.png b/docs/wiki/_media/tragesym_gschem_finished.png
deleted file mode 100644
index ccd4d82..0000000
Binary files a/docs/wiki/_media/tragesym_gschem_finished.png and /dev/null differ
diff --git a/docs/wiki/_media/tragesym_gschem_showhidden.png b/docs/wiki/_media/tragesym_gschem_showhidden.png
deleted file mode 100644
index 8a2a067..0000000
Binary files a/docs/wiki/_media/tragesym_gschem_showhidden.png and /dev/null differ
diff --git a/docs/wiki/_media/tragesym_kpdf_pinconfiguration.png b/docs/wiki/_media/tragesym_kpdf_pinconfiguration.png
deleted file mode 100644
index 72fc148..0000000
Binary files a/docs/wiki/_media/tragesym_kpdf_pinconfiguration.png and /dev/null differ
diff --git a/docs/wiki/_media/tragesym_kpdf_pindescription.png b/docs/wiki/_media/tragesym_kpdf_pindescription.png
deleted file mode 100644
index 6c5b49e..0000000
Binary files a/docs/wiki/_media/tragesym_kpdf_pindescription.png and /dev/null differ
diff --git a/docs/wiki/_media/tragesym_ooo_attributes.png b/docs/wiki/_media/tragesym_ooo_attributes.png
deleted file mode 100644
index 3e6fdc8..0000000
Binary files a/docs/wiki/_media/tragesym_ooo_attributes.png and /dev/null differ
diff --git a/docs/wiki/_media/tragesym_ooo_changedpins.png b/docs/wiki/_media/tragesym_ooo_changedpins.png
deleted file mode 100644
index 5446849..0000000
Binary files a/docs/wiki/_media/tragesym_ooo_changedpins.png and /dev/null differ
diff --git a/docs/wiki/_media/tragesym_ooo_rearanged.png b/docs/wiki/_media/tragesym_ooo_rearanged.png
deleted file mode 100644
index 100395b..0000000
Binary files a/docs/wiki/_media/tragesym_ooo_rearanged.png and /dev/null differ
diff --git a/docs/wiki/_media/tragesym_ooo_selection.png b/docs/wiki/_media/tragesym_ooo_selection.png
deleted file mode 100644
index 41a6a11..0000000
Binary files a/docs/wiki/_media/tragesym_ooo_selection.png and /dev/null differ
diff --git a/docs/wiki/_media/tragesym_template b/docs/wiki/_media/tragesym_template
deleted file mode 100644
index ac3839e..0000000
--- a/docs/wiki/_media/tragesym_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/tragesym_template2 b/docs/wiki/_media/tragesym_template2
deleted file mode 100644
index f414b79..0000000
Binary files a/docs/wiki/_media/tragesym_template2 and /dev/null differ
diff --git a/docs/wiki/_media/tragesym_template2.txt.txt b/docs/wiki/_media/tragesym_template2.txt.txt
deleted file mode 100644
index 4e507c3..0000000
--- a/docs/wiki/_media/tragesym_template2.txt.txt
+++ /dev/null
@@ -1,59 +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
-# 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
-#-----------------------------------------------------
diff --git a/docs/wiki/_media/tragesym_xemacs_modifiedselection.png b/docs/wiki/_media/tragesym_xemacs_modifiedselection.png
deleted file mode 100644
index dd2ce2d..0000000
Binary files a/docs/wiki/_media/tragesym_xemacs_modifiedselection.png and /dev/null differ
diff --git a/docs/wiki/_media/tragesym_xemacs_rawselection.png b/docs/wiki/_media/tragesym_xemacs_rawselection.png
deleted file mode 100644
index 8a86702..0000000
Binary files a/docs/wiki/_media/tragesym_xemacs_rawselection.png and /dev/null differ
diff --git a/docs/wiki/best_practices.html b/docs/wiki/best_practices.html
index 46c5857..06511f8 100644
--- a/docs/wiki/best_practices.html
+++ b/docs/wiki/best_practices.html
@@ -1,27 +1,16 @@
<!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">
+<html>
<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
- <title>best_practices</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2008-03-02T09:06:28-0500" />
-<meta name="keywords" content="best_practices" />
-<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/best_practices?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/best_practices"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/best_practices"; />
-<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">
+
@@ -29,10 +18,12 @@
<div class="level3">
<p>
- 2008 is the second year in which the gEDA Project has participated in Googleâ??s Summer of Code program. Through our experience, we have learned a couple of things about running a successful program. Here are the things we ask of our students to help make the GSoC experience a success for everybody.
+ 2009 is the third year in which the gEDA Project has participated in Googleâ??s Summer of Code program. Through our experience, we have learned a couple of things about running a successful program. Here are the things we ask of our students to help make the GSoC experience a success for everybody.
</p>
<ul>
-<li class="level1"><div class="li"> Do not hesitate to get involved with the gEDA Project <strong>before</strong> the summer begins. We are more interested in having new developers join (and stay with) our community than we are in simply giving away easy summer jobs. Therefore, get involved now! Join our <a href="http://geda.seul.org/mailinglist/index.html"; class="urlextern" title="http://geda.seul.org/mailinglist/index.html"; rel="nofollow"> mailing lists</a>, check the code out of git, and fiddle around with it. We will rate your application more highly if you are already a participant, and not just a new face when GSoC application time rolls around.</div>
+<li class="level1"><div class="li"> Please get involved with the gEDA Project <strong>before</strong> the summer begins. We are more interested in having new developers join (and stay with) our community than we are in simply giving away easy summer jobs. Therefore, get involved <strong>now!</strong> Join our <a href="http://geda.seul.org/mailinglist/index.html"; class="urlextern" title="http://geda.seul.org/mailinglist/index.html"; rel="nofollow"> mailing lists</a>, check the code out of git, and fiddle around with it. We will rate your application more highly if you are already a participant, and not just a new face when GSoC application time rolls around.</div>
+</li>
+<li class="level1"><div class="li"> Participating in Google Summer of Code is meant to be a <strong>full time job</strong>. We expect that you will work on your project 8 hours/day from Monday to Friday. Summer of Code is not meant to be a side job. Please do not try to work on both Summer of Code and a different job during the summer – you will tire yourself out, your work quality will suffer, and you wonâ??t enjoy the experience at all.</div>
</li>
<li class="level1"><div class="li"> Students and mentors should use the <a href="http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev"; class="urlextern" title="http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev"; rel="nofollow">geda-dev mailing list</a> for (almost) all communication about their GSoC project. There are several reasons for this: </div>
<ul>
@@ -59,6 +50,5 @@
</p>
</div>
-</div>
</body>
</html>
diff --git a/docs/wiki/design.css b/docs/wiki/design.css
new file mode 100644
index 0000000..86ef2d7
--- /dev/null
+++ b/docs/wiki/design.css
@@ -0,0 +1,692 @@
+/**
+ * Design elements for default Template
+ *
+ * @author Andreas Gohr <andi@xxxxxxxxxxxxxx>
+ * @author Anika Henke <henke@xxxxxxxxxxxx>
+ */
+
+/* -------------- general elements --------------- */
+
+body {
+ font: 100% "Lucida Grande", Verdana, Lucida, Helvetica, Arial, sans-serif;
+ background-color: #f8f8f8;
+ color: Black;
+ margin: 0;
+ padding: 0;
+ margin-left: 1em;
+ margin-right: 1em;
+}
+
+/* the document */
+div.page {
+ margin-top: 4px;
+ margin-left: 1em;
+ margin-right: 2em;
+ text-align: justify;
+}
+
+table {
+ font-size: 100%;
+ padding:0;
+ margin:0;
+}
+
+tr,td,th {padding:0; margin:0;}
+
+img {border:0}
+
+p {padding:0; margin: 0 0 1.0em 0;}
+
+hr {
+ border: 0px;
+ border-top: 1px solid #8cacbb;
+ text-align:center;
+ height: 0px;
+}
+
+div.nothing {
+ text-align:center;
+ margin: 2em;
+}
+
+/* ---------------- forms ------------------------ */
+
+form {
+ border: none;
+ margin: 0;
+ display: inline;
+}
+
+label {
+ display: block;
+ text-align: right;
+ font-weight: bold;
+}
+
+label.simple {
+ text-align: left;
+ font-weight: normal;
+}
+
+label input.edit {
+ width: 50%;
+}
+
+fieldset {
+ width: 300px;
+ text-align: center;
+ border: 1px solid #8cacbb;
+ padding: 0.5em;
+}
+
+textarea.edit {
+ font-family:monospace;
+ border: 1px solid #8cacbb;
+ color: Black;
+ background-color: white;
+ font-size:14px;
+ padding: 3px;
+ width:100%;
+}
+
+input.edit,select.edit {
+ font-size: 100%;
+ border: 1px solid #8cacbb;
+ height: 18px !important;
+ max-height: 22px !important;
+ min-height: 22px !important;
+ color: Black;
+ background-color: white;
+ vertical-align: middle;
+ padding: 1px;
+ display: inline;
+}
+
+input.missing {
+ font-size: 100%;
+ border: 1px solid #8cacbb;
+ height: 18px !important;
+ max-height: 22px !important;
+ min-height: 22px !important;
+ color: Black;
+ background-color: #ffcccc;
+ vertical-align: middle;
+ padding: 1px;
+ display: inline;
+}
+
+/* --------- buttons ------------------- */
+
+
+input.button {
+ border: 1px solid #8cacbb;
+ color: Black;
+ background-color: white;
+ vertical-align: middle;
+ text-decoration:none;
+ font-size: 100%;
+ cursor: pointer;
+ height: 22px !important;
+ max-height: 22px !important;
+ min-height: 22px !important;
+ margin: 1px;
+ display: inline;
+}
+
+div.secedit input.button {
+ border: 1px solid #8cacbb;
+ color: Black;
+ background-color: white;
+ vertical-align: middle;
+ text-decoration:none;
+ margin: 0px;
+ padding: 0px;
+ font-size: 10px;
+ cursor: pointer;
+ height: 15px !important;
+ max-height: 15px !important;
+ min-height: 15px !important;
+ float:right;
+ display: inline;
+}
+
+/* ----------- page navigator ------------- */
+
+div.pagenav {
+ margin-top:1em;
+}
+
+div.pagenav-prev {
+ text-align:right;
+ float:left;
+ width:50%
+}
+
+div.pagenav-prev input.button {
+ margin-right:5px;
+}
+
+div.pagenav-next {
+ text-align:left;
+ float:right;
+ width:50%
+}
+
+div.pagenav-next input.button {
+ margin-left:5px;
+}
+
+/* --------------- Links ------------------ */
+
+a {
+ color:#000000;
+ text-decoration:none;
+}
+a:hover {
+ color:#000000;
+ text-decoration:none;
+}
+
+/* external link */
+a.urlextern{
+ background: transparent url(images/link_icon.gif) 0px 1px no-repeat;
+ padding: 1px 0px 1px 16px;
+ color:#0000BB;
+ text-decoration:none;
+}
+a.urlextern:visited {
+ color:Purple;
+}
+a.urlextern:hover {
+ text-decoration:underline;
+}
+
+/* windows share */
+a.windows{
+ background: transparent url(images/windows.gif) 0px 1px no-repeat;
+ padding: 1px 0px 1px 16px;
+ color:#436976;
+ text-decoration:none;
+}
+a.windows:visited {
+ color:Purple;
+}
+a.windows:hover {
+ text-decoration:underline;
+}
+
+/* interwiki link */
+a.interwiki{
+ background: transparent url(images/interwiki.png) 0px 1px no-repeat;
+ padding-left: 16px;
+ color:#436976;
+ text-decoration:none;
+}
+a.interwiki:visited {
+ color:Purple;
+}
+a.interwiki:hover {
+ text-decoration:underline;
+}
+
+/* link to some embedded media */
+a.media {
+ color:#436976;
+ text-decoration:none;
+}
+a.media:hover {
+ color:#436976;
+ text-decoration:underline
+}
+
+/* email link */
+a.mail {
+ background: transparent url(images/mail_icon.gif) 0px 1px no-repeat;
+ padding: 1px 0px 1px 16px;
+ color:#436976;
+ text-decoration:none;
+}
+a.mail:hover {
+ text-decoration:underline;
+}
+
+/* existing wikipage */
+a.wikilink1:link { color:#0000BB; text-decoration:none }
+a.wikilink1:visited { color:Purple; text-decoration:none }
+a.wikilink1:hover { color:#0000BB; text-decoration:underline }
+
+/* not existing wikipage */
+a.wikilink2:link { color:#FF3300; text-decoration:none }
+a.wikilink2:visited { color:#FF3300; text-decoration:none }
+a.wikilink2:hover { color:#FF3300; text-decoration:underline }
+
+
+/* ------------- Page elements ----------------- */
+
+div.preview{
+ background:#f7f9fa;
+ margin-left:2em;
+ padding: 4px;
+ border: 1px dashed #000000;
+}
+
+div.breadcrumbs{
+ background-color: #f5f5f5;
+ font-size:80%;
+ color: #666666;
+ padding-left: 4px;
+}
+
+span.user{
+ color: #cccccc;
+ font-size: 90%;
+}
+
+/* embedded images */
+img.media {
+ margin: 3px;
+}
+
+img.medialeft {
+ border: 0;
+ float: left;
+ margin: 0 1.5em 0 0;
+}
+
+img.mediaright {
+ border: 0;
+ float: right;
+ margin: 0 0 0 1.5em;
+}
+
+img.mediacenter {
+ border: 0;
+ display: block;
+ margin-left: auto;
+ margin-right: auto;
+}
+
+acronym {
+ cursor: help;
+ border-bottom: 1px dotted #000;
+}
+
+/* general headline setup */
+h1, h2, h3, h4, h5 {
+ color: Black;
+ background-color: transparent;
+ font-family: "Lucida Grande", Verdana, Lucida, Helvetica, Arial, sans-serif;
+ font-size: 100%;
+ font-weight: normal;
+ margin-left: 0;
+ margin-right: 0;
+ margin-top: 0;
+ margin-bottom: 1em;
+ padding-left: 0;
+ padding-right: 0;
+ padding-top: 0.5em;
+ padding-bottom: 0;
+ border-bottom: 1px solid #8cacbb;
+ clear: left;
+}
+
+/* special headlines */
+h1 {font-size: 160%; margin-left: 0px; font-weight: bold;}
+h2 {font-size: 150%; margin-left: 20px;}
+h3 {font-size: 140%; margin-left: 40px; border-bottom: none; font-weight: bold;}
+h4 {font-size: 120%; margin-left: 60px; border-bottom: none; font-weight: bold;}
+h5 {font-size: 100%; margin-left: 80px; border-bottom: none; font-weight: bold;}
+
+/* indent different sections */
+div.level1 {margin-left: 3px;}
+div.level2 {margin-left: 23px;}
+div.level3 {margin-left: 43px;}
+div.level4 {margin-left: 63px;}
+div.level5 {margin-left: 83px;}
+
+/* unordered lists */
+ul {
+ line-height: 1.5em;
+ list-style-type: square;
+ margin: 0 0 0.5em 1.5em;
+ padding: 0;
+ list-style-image: url(images/bullet.gif);
+}
+
+/* ordered lists */
+ol {
+ line-height: 1.5em;
+ margin: 0 0 0.5em 1.5em;
+ padding: 0;
+ color: #638c9c;
+ font-weight: bold;
+ list-style-image: none;
+}
+
+/* the list items overriding the ol definition */
+.li {
+ color: #000000;
+ font-weight: normal;
+}
+
+ol {list-style-type: decimal}
+ol ol {list-style-type: upper-roman}
+ol ol ol {list-style-type: lower-alpha}
+ol ol ol ol {list-style-type: lower-greek}
+
+li.open {
+ list-style-image: url(images/open.gif);
+}
+
+li.closed {
+ list-style-image: url(images/closed.gif);
+}
+
+blockquote {
+ border-left: 2px solid #8cacbb;
+ padding-left: 3px;
+ margin-left: 0;
+}
+
+/* code blocks by indention */
+pre.pre {
+ font-size: 120%;
+ padding: 0.5em;
+ border: 1px dashed #8cacbb;
+ color: Black;
+ background-color: #f7f9fa;
+ overflow: auto;
+}
+
+/* code blocks by code tag */
+pre.code {
+ font-size: 120%;
+ padding: 0.5em;
+ border: 1px dashed #8cacbb;
+ color: Black;
+ background-color: #f7f9fa;
+ overflow: auto;
+}
+
+/* inline code words */
+code {
+ font-size: 120%;
+}
+
+/* code blocks by file tag */
+pre.file {
+ font-size: 120%;
+ padding: 0.5em;
+ border: 1px dashed #8cacbb;
+ color: Black;
+ background-color: #dee7ec;
+ overflow: auto;
+}
+
+/* inline tables */
+table.inline {
+ background-color: #ffffff;
+ border-spacing: 0px;
+ border-collapse: collapse;
+}
+
+table.inline th {
+ padding: 3px;
+ border: 1px solid #8cacbb;
+ background-color: #dee7ec;
+}
+
+table.inline td {
+ padding: 3px;
+ border: 1px solid #8cacbb;
+}
+
+.leftalign{
+ text-align: left;
+}
+
+.centeralign{
+ text-align: center;
+}
+
+.rightalign{
+ text-align: right;
+}
+
+/* ---------- table of contents ------------------- */
+
+div.toc {
+ margin-left: 2em;
+ margin-top: 1.2em;
+ margin-bottom: 0;
+ float:right;
+ width: 200px;
+ font-size: 80%;
+ clear:both;
+ border: 1px solid #8cacbb;
+ background-color: #ffffff;
+}
+
+div.tocheader {
+ padding: 3px;
+ border: 1px solid #8cacbb;
+ background-color: #dee7ec;
+ text-align: left;
+ font-weight:bold;
+ margin-bottom: 2px;
+}
+
+div.toctoggle {
+ float:right;
+ margin-top:0.3em;
+ margin-right:3px;
+}
+
+div.toctoggle img {
+ width:0.8em;
+ height:0.8em;
+}
+
+#tocinside {
+ border: 1px solid #8cacbb;
+ background-color: #ffffff;
+ text-align: left;
+ padding-top: 0.5em;
+ padding-bottom: 0.7em;
+}
+
+ul.toc {
+ list-style-type: none;
+ list-style-image: none;
+ line-height: 1.2em;
+ margin: 0;
+ padding: 0;
+ padding-left: 1em;
+}
+
+ul.toc li {
+ background: transparent url(images/tocdot2.gif) 0 0.6em no-repeat;
+ padding-left:0.4em;
+}
+
+ul.toc li.clear {
+ background-image: none;
+ padding-left:0.4em;
+}
+
+a.toc {
+ color: #0000BB;
+ text-decoration:none;
+}
+
+a.toc:hover {
+ color: #000000;
+ text-decoration:underline;
+}
+
+/* ---------------------------- Diff rendering --------------------------*/
+table.diff { background:white; }
+td.diff-blockheader {font-weight:bold}
+td.diff-header {
+ border-bottom: 1px solid #8cacbb;
+ font-size:120%;
+}
+td.diff-addedline {
+ background:#ddffdd;
+ font-family: monospace;
+ font-size: 100%;
+}
+td.diff-deletedline {
+ background:#ffffbb;
+ font-family: monospace;
+ font-size: 100%;
+}
+td.diff-context {
+ background:#f7f9fa;
+ font-family: monospace;
+ font-size: 100%;
+}
+span.diffchange { color: red; }
+
+/* --------------------- footnotes -------------------------------- */
+
+div.footnotes{
+ clear:both;
+ border-top: 1px solid #8cacbb;
+ padding-left: 1em;
+ margin-top: 1em;
+}
+
+div.fn{
+ font-size:90%;
+}
+
+a.fn_top{
+ vertical-align:super;
+ font-size:80%;
+}
+
+a.fn_bot{
+ vertical-align:super;
+ font-size:80%;
+ font-weight:bold;
+}
+
+
+/* --------------- search result formating --------------- */
+.search_result{
+ margin-bottom: 6px;
+ padding-left: 30px;
+ padding-right: 10px;
+}
+
+.search_snippet{
+ color: #999999;
+ font-size: 12px;
+ margin-left: 20px;
+}
+
+.search_sep{
+ color: #000000;
+}
+
+.search_hit{
+ color: #000000;
+ background: #FFFF99;
+}
+
+div.search_quickresult{
+ margin-bottom: 15px;
+ padding-bottom: 5px;
+ border-bottom: 1px dashed #8cacbb;
+ margin-left: 30px;
+ padding-right: 10px;
+}
+
+div.search_quickhits {
+ margin-left: 1em;
+ float:left;
+ background: transparent url(images/bullet.gif) 0px 1px no-repeat;
+ padding: 1px 0px 1px 8px;
+ width: 30%;
+}
+
+/* ------------------ Additional ---------------------- */
+.footerinc a img {
+ opacity: 0.5;
+}
+
+.footerinc a:hover img {
+ opacity: 1;
+}
+
+/* ---- Admin --- */
+
+div.acladmin label {
+ text-align: left;
+ font-weight: normal;
+ display: inline;
+}
+
+div.acladmin table{
+ margin-left: 10%;
+ width: 80%;
+}
+
+/* ---------- AJAX quicksearch ----------- */
+
+div.ajax_qsearch {
+ position:absolute;
+ right:225px;;
+ text-align:left;
+ width: 200px;
+ background-color: #ff9;
+ opacity: 0.9;
+ display:none;
+}
+
+/* ---------- Spellchecking ------------- */
+
+a.spell_error {
+ color: #ff0000;
+ text-decoration: underline;
+}
+
+div#spell_suggest {
+ position: absolute;
+ left: 0;
+ top: 0;
+ display: none;
+ background-color: #fff;
+ padding: 2px;
+ border: 1px solid #000;
+ font-size:80%;
+ z-index: 2;
+}
+
+div#spell_result {
+ display:none;
+ font-family:monospace;
+ border: 1px solid #8cacbb;
+ color: Black;
+ font-size:14px;
+ padding: 3px;
+ background-color: #f7f9fa;
+ overflow: auto;
+ z-index: 1;
+
+ white-space: pre-wrap; /* css-3 */
+ white-space: -moz-pre-wrap; /* Mozilla, since 1999 */
+ white-space: -pre-wrap; /* Opera 4-6 */
+ white-space: -o-pre-wrap; /* Opera 7 */
+ word-wrap: break-word; /* Internet Explorer 5.5+ */
+}
+
+span.spell_noerr {
+ color: #009933;
+}
+
+span.spell_wait {
+ color: #0066cc;
+}
+
diff --git a/docs/wiki/docs_20060124_gschem_ug_app_a.html b/docs/wiki/docs_20060124_gschem_ug_app_a.html
deleted file mode 100644
index 57d66ef..0000000
--- a/docs/wiki/docs_20060124_gschem_ug_app_a.html
+++ /dev/null
@@ -1,27 +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>docs:20060124:gschem_ug:app_a</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="noindex,follow" />
-<meta name="date" content="1969-12-31T19:00:00-0500" />
-<meta name="keywords" content="docs,20060124,gschem_ug,app_a" />
-<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/docs:20060124:gschem_ug:app_a?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=docs:20060124:gschem_ug"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/docs:20060124:gschem_ug:app_a"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/docs:20060124:gschem_ug:app_a"; />
-<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>
-</body>
-</html>
diff --git a/docs/wiki/docs_20060124_gschem_ug_app_b.html b/docs/wiki/docs_20060124_gschem_ug_app_b.html
deleted file mode 100644
index 681759c..0000000
--- a/docs/wiki/docs_20060124_gschem_ug_app_b.html
+++ /dev/null
@@ -1,27 +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>docs:20060124:gschem_ug:app_b</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="noindex,follow" />
-<meta name="date" content="1969-12-31T19:00:00-0500" />
-<meta name="keywords" content="docs,20060124,gschem_ug,app_b" />
-<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/docs:20060124:gschem_ug:app_b?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=docs:20060124:gschem_ug"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/docs:20060124:gschem_ug:app_b"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/docs:20060124:gschem_ug:app_b"; />
-<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>
-</body>
-</html>
diff --git a/docs/wiki/docs_20060124_gschem_ug_app_c.html b/docs/wiki/docs_20060124_gschem_ug_app_c.html
deleted file mode 100644
index 5292b1a..0000000
--- a/docs/wiki/docs_20060124_gschem_ug_app_c.html
+++ /dev/null
@@ -1,27 +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>docs:20060124:gschem_ug:app_c</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="noindex,follow" />
-<meta name="date" content="1969-12-31T19:00:00-0500" />
-<meta name="keywords" content="docs,20060124,gschem_ug,app_c" />
-<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/docs:20060124:gschem_ug:app_c?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=docs:20060124:gschem_ug"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/docs:20060124:gschem_ug:app_c"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/docs:20060124:gschem_ug:app_c"; />
-<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>
-</body>
-</html>
diff --git a/docs/wiki/docs_20060124_gschem_ug_components_symbols_objects_attributes.html b/docs/wiki/docs_20060124_gschem_ug_components_symbols_objects_attributes.html
deleted file mode 100644
index 8f6b082..0000000
--- a/docs/wiki/docs_20060124_gschem_ug_components_symbols_objects_attributes.html
+++ /dev/null
@@ -1,27 +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>docs:20060124:gschem_ug:components_symbols_objects_attributes</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="noindex,follow" />
-<meta name="date" content="1969-12-31T19:00:00-0500" />
-<meta name="keywords" content="docs,20060124,gschem_ug,components_symbols_objects_attributes" />
-<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/docs:20060124:gschem_ug:components_symbols_objects_attributes?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=docs:20060124:gschem_ug"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/docs:20060124:gschem_ug:components_symbols_objects_attributes"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/docs:20060124:gschem_ug:components_symbols_objects_attributes"; />
-<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>
-</body>
-</html>
diff --git a/docs/wiki/docs_20060124_gschem_ug_electrical_connectivity.html b/docs/wiki/docs_20060124_gschem_ug_electrical_connectivity.html
deleted file mode 100644
index 81b7888..0000000
--- a/docs/wiki/docs_20060124_gschem_ug_electrical_connectivity.html
+++ /dev/null
@@ -1,27 +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>docs:20060124:gschem_ug:electrical_connectivity</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="noindex,follow" />
-<meta name="date" content="1969-12-31T19:00:00-0500" />
-<meta name="keywords" content="docs,20060124,gschem_ug,electrical_connectivity" />
-<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/docs:20060124:gschem_ug:electrical_connectivity?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=docs:20060124:gschem_ug"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/docs:20060124:gschem_ug:electrical_connectivity"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/docs:20060124:gschem_ug:electrical_connectivity"; />
-<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>
-</body>
-</html>
diff --git a/docs/wiki/docs_20060124_gschem_ug_how_to_ask_questions.html b/docs/wiki/docs_20060124_gschem_ug_how_to_ask_questions.html
deleted file mode 100644
index 356355e..0000000
--- a/docs/wiki/docs_20060124_gschem_ug_how_to_ask_questions.html
+++ /dev/null
@@ -1,27 +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>docs:20060124:gschem_ug:how_to_ask_questions</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="noindex,follow" />
-<meta name="date" content="1969-12-31T19:00:00-0500" />
-<meta name="keywords" content="docs,20060124,gschem_ug,how_to_ask_questions" />
-<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/docs:20060124:gschem_ug:how_to_ask_questions?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=docs:20060124:gschem_ug"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/docs:20060124:gschem_ug:how_to_ask_questions"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/docs:20060124:gschem_ug:how_to_ask_questions"; />
-<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>
-</body>
-</html>
diff --git a/docs/wiki/docs_20060124_gschem_ug_installing_gschem.html b/docs/wiki/docs_20060124_gschem_ug_installing_gschem.html
deleted file mode 100644
index 6129a4c..0000000
--- a/docs/wiki/docs_20060124_gschem_ug_installing_gschem.html
+++ /dev/null
@@ -1,27 +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>docs:20060124:gschem_ug:installing_gschem</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="noindex,follow" />
-<meta name="date" content="1969-12-31T19:00:00-0500" />
-<meta name="keywords" content="docs,20060124,gschem_ug,installing_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/"; />
-<link rel="contents" href="http://geda.seul.org/wiki/docs:20060124:gschem_ug:installing_gschem?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=docs:20060124:gschem_ug"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/docs:20060124:gschem_ug:installing_gschem"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/docs:20060124:gschem_ug:installing_gschem"; />
-<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>
-</body>
-</html>
diff --git a/docs/wiki/docs_20060124_gschem_ug_resources.html b/docs/wiki/docs_20060124_gschem_ug_resources.html
deleted file mode 100644
index 83af5d2..0000000
--- a/docs/wiki/docs_20060124_gschem_ug_resources.html
+++ /dev/null
@@ -1,27 +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>docs:20060124:gschem_ug:resources</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="noindex,follow" />
-<meta name="date" content="1969-12-31T19:00:00-0500" />
-<meta name="keywords" content="docs,20060124,gschem_ug,resources" />
-<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/docs:20060124:gschem_ug:resources?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=docs:20060124:gschem_ug"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/docs:20060124:gschem_ug:resources"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/docs:20060124:gschem_ug:resources"; />
-<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>
-</body>
-</html>
diff --git a/docs/wiki/docs_20060124_gschem_ug_the_main_window.html b/docs/wiki/docs_20060124_gschem_ug_the_main_window.html
deleted file mode 100644
index 4d3825f..0000000
--- a/docs/wiki/docs_20060124_gschem_ug_the_main_window.html
+++ /dev/null
@@ -1,27 +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>docs:20060124:gschem_ug:the_main_window</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="noindex,follow" />
-<meta name="date" content="1969-12-31T19:00:00-0500" />
-<meta name="keywords" content="docs,20060124,gschem_ug,the_main_window" />
-<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/docs:20060124:gschem_ug:the_main_window?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=docs:20060124:gschem_ug"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/docs:20060124:gschem_ug:the_main_window"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/docs:20060124:gschem_ug:the_main_window"; />
-<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>
-</body>
-</html>
diff --git a/docs/wiki/docs_20060124_gschem_ug_the_status_window.html b/docs/wiki/docs_20060124_gschem_ug_the_status_window.html
deleted file mode 100644
index dd1d6da..0000000
--- a/docs/wiki/docs_20060124_gschem_ug_the_status_window.html
+++ /dev/null
@@ -1,27 +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>docs:20060124:gschem_ug:the_status_window</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="noindex,follow" />
-<meta name="date" content="1969-12-31T19:00:00-0500" />
-<meta name="keywords" content="docs,20060124,gschem_ug,the_status_window" />
-<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/docs:20060124:gschem_ug:the_status_window?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=docs:20060124:gschem_ug"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/docs:20060124:gschem_ug:the_status_window"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/docs:20060124:gschem_ug:the_status_window"; />
-<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>
-</body>
-</html>
diff --git a/docs/wiki/geda-bom_readme.html b/docs/wiki/geda-bom_readme.html
new file mode 100644
index 0000000..3d1659f
--- /dev/null
+++ b/docs/wiki/geda-bom_readme.html
@@ -0,0 +1,52 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="bill_of_material_netlister_readme" id="bill_of_material_netlister_readme">Bill of Material netlister README</a></h1>
+<div class="level1">
+<pre class="code">README for
+BOM - Bill Of Materials generater for gnetlist.
+
+--------------------------------------------------------------------------
+
+I (Matt) put together a quick bill of materials generator for gnetlist.
+It takes a configuration file which tells it what attributes you want
+netlisted (i.e. vendor, part number).
+
+This is a sample config file:
+
+device
+label
+name
+
+Just call it with
+ gnetlist -g bom -o test.bom test.sch
+
+The config file must be called "attribs" and be in the pwd, because
+there is no way to pass arguments to the netlister (at least that I
+could find).
+
+Eventually I'd like to integrate this with some sort of a database for
+production purposes. Let me know if you are interested in helping or
+have any ideas.
+
+Matt
+matt@xxxxxxxxx
+
+</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-circuit_simulation_improvements.html b/docs/wiki/geda-circuit_simulation_improvements.html
new file mode 100644
index 0000000..f14db5f
--- /dev/null
+++ b/docs/wiki/geda-circuit_simulation_improvements.html
@@ -0,0 +1,382 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#circuit_simulation_improvements_in_gschem" class="toc">Circuit simulation improvements in gschem</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#rationale" class="toc">Rationale</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#draft" class="toc">Draft</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#the_probes" class="toc">The probes</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#voltage_and_current_sources" class="toc">Voltage and current sources</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#the_simulations" class="toc">The simulations</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#creating_a_simulation_dialog_inside_gschem" class="toc">Creating a simulation dialog inside gschem</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#the_option_dialog" class="toc">The option dialog</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#invoking_the_simulation" class="toc">Invoking the simulation</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#appendix" class="toc">Appendix</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#a_current_probe_symbol_draft" class="toc">A current probe symbol (draft)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#a_voltage_probe_symbol_draft" class="toc">A voltage probe symbol (draft)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#another_current_probe_symbol_used_by_kurt_peters" class="toc">Another current probe symbol used by Kurt Peters</a></span></div></li></ul>
+</li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="circuit_simulation_improvements_in_gschem" id="circuit_simulation_improvements_in_gschem">Circuit simulation improvements in gschem</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "Circuit simulation improvements in gschem" [1-58] -->
+<h2><a name="rationale" id="rationale">Rationale</a></h2>
+<div class="level2">
+
+<p>
+Using gschem as a circuit simulation (ngspice or gnucap) frontend is not easy for novice users. A new user would like to do the following things inside gschem:
+</p>
+<ul>
+<li class="level1"><div class="li"> specify what kinds of simulations should be run</div>
+</li>
+<li class="level1"><div class="li"> specify which voltages and currents should be plotted</div>
+</li>
+<li class="level1"><div class="li"> start the simulation</div>
+</li>
+</ul>
+
+<p>
+ The simulation runs and the postprocessing may be in an external programm that is triggered by IPC.
+</p>
+
+<p>
+There are some graphical frontends around but they canâ??t solve all of the above problems
+</p>
+<ul>
+<li class="level1"><div class="li"> <a href="http://www.geda.seul.org/tools/gspiceui/index.html"; class="urlextern" title="http://www.geda.seul.org/tools/gspiceui/index.html"; rel="nofollow">gspiceui</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="http://www.comefly.us/"; class="urlextern" title="http://www.comefly.us/"; rel="nofollow">kjwaves</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="http://easy-spice.sourceforge.net/"; class="urlextern" title="http://easy-spice.sourceforge.net/"; rel="nofollow">easyspice</a></div>
+</li>
+</ul>
+
+<p>
+ All frontends have the problem that you can not point to the net youâ??d like to see. You need to know the netname of the node.
+</p>
+
+</div>
+<!-- SECTION "Rationale" [59-862] -->
+<h2><a name="draft" id="draft">Draft</a></h2>
+<div class="level2">
+
+<p>
+Letâ??s assume we only want to make tiny changes to gschem and libgeda so that we can at least set some probes and ran a simulation.
+</p>
+
+</div>
+<!-- SECTION "Draft" [863-1012] -->
+<h3><a name="the_probes" id="the_probes">The probes</a></h3>
+<div class="level3">
+
+<p>
+<strong>Current probes</strong> can be ordinary dc voltage sources with 0V. The easy way to insert that probe would be a symbol with two pins like an normal ampere meter. If weâ??d like to set a current probe to an end of a pin we need a netlister that detects that current probe and replaces it with our â??ampere meterâ??. If we use a voltage source as an ampere meter the netlister does not need to know the netnames inside the schematic. All 0V voltage sources with a special device name are current probes.
+</p>
+
+<p>
+<strong>Voltage probes</strong> may be current sources with 0A. The second pin of the current source is tied to GND with a net attribute. Thus again the netlister does not need to know the netnames as it can use that net that is connected with that special current sources. Like above a voltage source could be a special (graphical) symbol that is detected by a netlister.
+</p>
+
+</div>
+<!-- SECTION "The probes" [1013-1888] -->
+<h3><a name="voltage_and_current_sources" id="voltage_and_current_sources">Voltage and current sources</a></h3>
+<div class="level3">
+
+<p>
+Specifying the parameters of sources is not that easy. Currently they are stored inside the â??valueâ?? attribute of the symbol. eg. â??value=pulse 0 1 10n 10n 100n 1u 2uâ??. These settings needs to match the spice attributes â??pulse(V1 V2 TD TR TF PW PER)".
+</p>
+
+<p>
+A dialog would be nice that prompts the user for the named attributes and not only for the value string.
+</p>
+
+<p>
+A modified edit attribute (ee) command could take care of voltage and current source devices and trigger a different property dialog for that sources. Currently the multiattrib edit dialog is triggered.
+</p>
+
+</div>
+<!-- SECTION "Voltage and current sources" [1889-2487] -->
+<h3><a name="the_simulations" id="the_simulations">The simulations</a></h3>
+<div class="level3">
+
+<p>
+How can we store a simulation inside gschem.
+</p>
+
+<p>
+To store one simulation we can use a symbol with the devicename â??SIMULATIONâ??. All options that define one simulation are stored as attributes attached to that object.
+</p>
+<ul>
+<li class="level1"><div class="li"> kind of simulation (dc, ac, tran, …)</div>
+</li>
+<li class="level1"><div class="li"> simulator options</div>
+</li>
+<li class="level1"><div class="li"> the simulator? (can we run the same circuit with too simulators in one step?)</div>
+</li>
+<li class="level1"><div class="li"> simulation parameters (global parameters, temperature, …)</div>
+</li>
+</ul>
+<pre class="code">
+v 20061020 1
+C 41500 49200 1 0 0 spice-directive-1.sym
+{
+device=spice_simulation_block
+refdes=A1
+simulation_name=random name
+simulation_active=1
+simulation_type=DC 0V 1V 0.1V
+parametric_simulation1=V1 lin 0 5 0.1
+parametric_simulation2=R1.value lin 10k 100k 10k
+option_TNOM=100 Deg
+option_ABSTOL=1e-3
+global_param1=???
+global_param2=???
+}
+</pre>
+
+<p>
+There may be many simulation objects inside a single schematic.
+</p>
+
+<p>
+To store additional libraries we can either use an include card or using a â??LIBRARYâ?? symbol that contains all libraries either as:
+</p>
+<ul>
+<li class="level1"><div class="li"> a multiline attribute</div>
+</li>
+<li class="level1"><div class="li"> multiple attached library attributes to the LIBRARY symbol</div>
+</li>
+</ul>
+
+<p>
+ There should be a distinction between global, user and local libs. global and user libs may be specified by a gafrc or a new spicerc configuration file.
+</p>
+
+</div>
+<!-- SECTION "The simulations" [2488-3735] -->
+<h3><a name="creating_a_simulation_dialog_inside_gschem" id="creating_a_simulation_dialog_inside_gschem">Creating a simulation dialog inside gschem</a></h3>
+<div class="level3">
+
+<p>
+ Lets assume anything we need to add simulation support to gschem is a single dialog.
+</p>
+<ul>
+<li class="level1"><div class="li"> It would have a list of simulations (listview with enable/disable buttons and simulation names)</div>
+</li>
+<li class="level1"><div class="li"> It would have some icons to add the probes. </div>
+</li>
+<li class="level1"><div class="li"> It may have buttons for the most common symbols: resistor, capacitor, inductor, diode, … [R,C,L,D,M,E,F,G,H..]</div>
+</li>
+<li class="level1"><div class="li"> It would have some dialog elements to do the spice settings</div>
+</li>
+<li class="level1"><div class="li"> It would have a simulate and a close button</div>
+</li>
+<li class="level1"><div class="li"> Some additional buttons like: Copy simulation, Remove simulation, general options…</div>
+</li>
+</ul>
+
+<p>
+ When creating that dialog all simulation objects are collected into the simulation list (listview with enable/disable checkbutton)
+</p>
+
+<p>
+When changing the settings the attributes of the assosiated simulation object are changed.
+</p>
+
+</div>
+<!-- SECTION "Creating a simulation dialog inside gschem" [3736-4567] -->
+<h3><a name="the_option_dialog" id="the_option_dialog">The option dialog</a></h3>
+<div class="level3">
+
+<p>
+What kind of options do we need for that dialog? And Why?
+</p>
+
+<p>
+The probes that we have placed can be used to tell the simulator the variables that we like to save or tell the plotting application which plots weâ??d like to see. This is something completely different, we need an option for that:
+</p>
+<ul>
+<li class="level1"><div class="li"> plot all marks and only save the corresponding node voltages</div>
+</li>
+<li class="level1"><div class="li"> plot all marks but save all node voltages and currents (through voltage sources)</div>
+</li>
+<li class="level1"><div class="li"> only save voltage nodes of the current schematic level or store subcircuit node voltages, too.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "The option dialog" [4568-5135] -->
+<h3><a name="invoking_the_simulation" id="invoking_the_simulation">Invoking the simulation</a></h3>
+<div class="level3">
+
+<p>
+The simulation button of the dialog should lead to the following actions:
+</p>
+<ul>
+<li class="level1"><div class="li"> save the schematic (ask the user or use a temporary file?)</div>
+</li>
+<li class="level1"><div class="li"> create a netlist using gnetlist</div>
+</li>
+<li class="level1"><div class="li"> create simulation files and include the netlist (can this be done with gnetlist too?)</div>
+</li>
+<li class="level1"><div class="li"> execute the simulation startup script (guile, sh, …)</div>
+</li>
+</ul>
+
+<p>
+ That startup script may even call a scheduler that can take lots of large simulations.
+</p>
+
+</div>
+<!-- SECTION "Invoking the simulation" [5136-5581] -->
+<h2><a name="appendix" id="appendix">Appendix</a></h2>
+<div class="level2">
+
+</div>
+<!-- SECTION "Appendix" [5582-5602] -->
+<h3><a name="a_current_probe_symbol_draft" id="a_current_probe_symbol_draft">A current probe symbol (draft)</a></h3>
+<div class="level3">
+<pre class="code">
+v 20061020 1
+P 0 0 200 200 1 0 0
+{
+T 100 0 5 10 0 1 0 0 1
+pintype=pas
+T 0 100 5 10 0 1 0 0 1
+pinseq=1
+T 0 100 5 10 0 1 0 0 1
+pinnumber=1
+T 0 100 5 10 0 1 0 0 1
+pinlabel=1
+}
+V 300 300 150 3 10 0 0 -1 -1 0 -1 -1 -1 -1 -1
+L 300 200 240 360 3 10 0 0 -1 -1
+L 300 200 360 360 3 10 0 0 -1 -1
+T 0 500 9 10 0 0 0 0 1
+device=VOLTAGE_PROBE
+T 200 50 9 6 1 1 0 0 1
+refdes=I_VP?
+T 0 700 9 10 0 0 0 0 1
+net=GND:2
+T 0 900 9 10 0 0 0 0 1
+value=DC 0A
+</pre>
+
+</div>
+<!-- SECTION "A current probe symbol (draft)" [5603-6092] -->
+<h3><a name="a_voltage_probe_symbol_draft" id="a_voltage_probe_symbol_draft">A voltage probe symbol (draft)</a></h3>
+<div class="level3">
+<pre class="code">
+v 20061020 1
+P 0 200 150 200 1 0 0
+{
+T -150 50 5 10 0 1 0 0 1
+pintype=pas
+T 50 250 5 10 0 1 0 0 1
+pinseq=1
+T 50 250 5 10 0 1 0 0 1
+pinnumber=1
+T 50 250 5 10 0 1 0 0 1
+pinlabel=1
+}
+V 300 200 150 3 10 0 0 -1 -1 0 -1 -1 -1 -1 -1
+L 300 300 380 140 3 10 0 0 -1 -1
+L 300 300 220 140 3 10 0 0 -1 -1
+T 0 500 9 10 0 0 0 0 1
+device=CURRENT_PROBE
+T 200 370 9 6 1 1 0 0 1
+refdes=V_IP?
+P 600 200 450 200 1 0 0
+{
+T 500 50 5 10 0 1 0 0 1
+pintype=pas
+T 500 250 5 10 0 1 0 0 1
+pinseq=2
+T 500 250 5 10 0 1 0 0 1
+pinnumber=2
+T 500 250 5 10 0 1 0 0 1
+pinlabel=2
+}
+L 240 180 360 180 3 10 0 0 -1 -1
+T 0 700 9 10 0 0 0 0 1
+value=DC 0V
+</pre>
+
+</div>
+<!-- SECTION "A voltage probe symbol (draft)" [6093-6761] -->
+<h3><a name="another_current_probe_symbol_used_by_kurt_peters" id="another_current_probe_symbol_used_by_kurt_peters">Another current probe symbol used by Kurt Peters</a></h3>
+<div class="level3">
+<pre class="code">
+v 20061020 1
+T 700 650 8 10 1 1 0 0 1
+refdes=VAM?
+T 700 850 5 10 1 1 0 0 1
+device=Ammeter
+T 700 1050 5 10 0 0 0 0 1
+footprint=none
+T 700 1250 5 10 0 0 0 0 1
+numslots=0
+T 700 1450 5 10 0 0 0 0 1
+description=ammeter for spice
+P 300 1200 300 900 1 0 0
+{
+T 350 1000 5 8 1 1 0 0 1
+pinnumber=1
+T 350 1000 5 8 0 1 0 2 1
+pinseq=1
+T 400 850 9 8 1 1 0 5 1
+pinlabel=+
+T 300 700 5 8 0 1 0 5 1
+pintype=pwr
+}
+P 300 0 300 300 1 0 0
+{
+T 350 100 5 8 1 1 0 0 1
+pinnumber=2
+T 350 100 5 8 0 1 0 2 1
+pinseq=2
+T 300 500 5 8 0 1 0 3 1
+pintype=pwr
+T 300 300 5 10 1 1 0 0 1
+pinlabel=-
+}
+L 300 400 400 500 3 0 0 0 -1 -1
+L 200 500 300 400 3 0 0 0 -1 -1
+T 700 450 5 10 0 1 0 0 1
+value=DC 0V
+L 300 400 300 800 3 0 0 0 -1 -1
+L 100 800 500 400 3 0 0 0 -1 -1
+B 0 300 600 600 3 0 0 0 -1 -1 0 -1 -1 -1 -1 -1
+L 200 800 100 800 3 0 0 0 -1 -1
+L 100 700 100 800 3 0 0 0 -1 -1
+</pre>
+
+</div>
+<!-- SECTION "Another current probe symbol used by Kurt Peters" [6762-] --></body>
+</html>
diff --git a/docs/wiki/geda-covered_mp.html b/docs/wiki/geda-covered_mp.html
new file mode 100644
index 0000000..c456378
--- /dev/null
+++ b/docs/wiki/geda-covered_mp.html
@@ -0,0 +1,232 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="covered_man-page" id="covered_man-page">covered man-page</a></h1>
+<div class="level1">
+<pre class="code">Covered(1) Code Analysis Covered(1)
+
+
+
+NAME
+ Covered - Verilog Code Coverage Analyzer
+
+SYNTAX
+ covered [<options>] score [<options>]
+ covered [<options>] merge [<options>] <existing_database>
+ <database_to_merge>
+ covered [<options>] report [<options>] <database_file>
+
+DESCRIPTION
+ Covered is a Verilog code coverage analysis tool that can be useful for
+ determining how well a diagnostic test suite is covering the design
+ under test. Covered reads in the Verilog design files and a VCD or LXT
+ formatted dumpfile from a diagnostic run and generates a database file
+ called a Coverage Description Database (CDD) file, using the score com-
+ mand. This file can be merged with other CDD files from the same
+ design to create accummulated coverage, using the merge command. Once
+ a CDD file is created, the user can use Covered to generate various
+ human-readable coverage reports in an ASCII format or use Covered�s GUI
+ to interactively look at coverage results, using the report command.
+ Additionally, as part of Covered�s score command, race condition possi-
+ bilities are found in the design files and can be either ignored,
+ flagged as warnings or flagged as errors. By specifying race condi-
+ tions as errors, Covered can also be used as a race condition checker.
+
+GLOBAL OPTIONS
+ These options are placed immediately after the keyword covered in the
+ command-line. They can be used for any command (with the exception of
+ -v and -h) and have the same effect in each case.
+
+ -D Debug. Display information helpful for debugging tool problems.
+ Note: This option is now only available when covered is built
+ with the --enable-debug configuration option.
+
+ -h Help. Display this usage information.
+
+ -Q Quiet mode. Causes all output to be suppressed.
+
+ -v Version. Display current Covered version.
+
+COMMANDS
+ score Parses Verilog files and VCD/LXT dumpfiles to create database
+ file used for merging and reporting.
+
+ merge Merges two database files into one.
+
+ report Generates human-readable coverage reports from database file or
+ starts the coverage report GUI.
+
+SCORE COMMAND
+ The following options are valid for the score command:
+
+ -D define_name
+ Defines the specified name to 1.
+
+ -D define_name=value
+ Defines the specified name to the specified value.
+
+ -e block_name
+ Name of module, task, function or named begin/end block to not
+ score. Causes all subblocks in the Verilog tree under this
+ block to also not be scored.
+
+ -ea Excludes all always blocks from being considered for coverage.
+
+ -ec Excludes all continuous assignments from being considered for
+ coverage.
+
+ -ei Excludes all initial blocks from being considered for coverage.
+
+ -F module_name=(in_expr,)out_expr
+ Indicates to the parser where to find the FSM located in module
+ module_name which has an input state expression called in_expr
+ and output state expression called out_expr. If in_expr is not
+ specified, out_expr is used as both the input and output state
+ expression.
+
+ -f filename
+ Name of file containing additional arguments to parse.
+
+ -h Displays this help information.
+
+ -I directory
+ Directory to find included Verilog files.
+
+ -i instance_name
+ Verilog hierarchical reference to the module that is at the top
+ of the tree to be scored. This option is necessary if module to
+ verify coverage is not the top-level module in the design. If
+ not specified, -t value is used.
+
+ -lxt filename
+ Name of LXT/LXT2 dumpfile to score design with. If this or the
+ -vcd option is not used, Covered will only create an initial CDD
+ file from the design and will not attempt to score the design.
+
+ -o database
+ Name of database to write coverage information to. If not spec-
+ ified, the output database filename will be "cov.cdd".
+
+ -p filename
+ Overrides default filename used to store intermediate preproces-
+ sor output.
+
+ -P parameter_scope=value
+ Performs a defparam on the specified parameter with value.
+
+ -r(S|W|E)
+ Specifies action to take when race condition checking finds
+ problems in design (-rS = Silent, -rW = Warning, -rE = Error).
+
+ -S Outputs simulation statistics after simulation has completed.
+ This information is currently only useful for the developers of
+ Covered.
+
+ -t top-level module
+ Specifies the module name of the top-most module that will be
+ measured. Note that this module does not need to be the
+ top-most module in the simulator. This field is required for
+ all calls to the score command.
+
+ -ts number
+ When scoring occurs, this option allows the user to see how far
+ the simulator has progressed by outputting the current timestep
+ to standard output. The value of number specifies how many
+ timesteps are allowed to be simulated before outputting the cur-
+ rent timestep (results in less calls to output stream).
+
+ -T min|typ|max
+ Specifies which value to use when encountering a delay expres-
+ sion in the form: min:typ:max. If this option is not speci-
+ fied, �typ� select is used by default.
+
+ -v filename
+ Name of specific Verilog file to score.
+
+ -vcd filename
+ Name of VCD dumpfile to score design with. If this or the -lxt
+ option is not used, Covered will only create an initial CDD file
+ from the design and will not attempt to score the design.
+
+ -y directory
+ Directory to find unspecified Verilog files.
+
+ +libext+.extension(+.extension)*+
+ Extensions of Verilog files to allow in scoring.
+
+MERGE COMMAND
+ The following options are valid for the merge command:
+
+ -h Displays this help information.
+
+ -o filename
+ File to output new database to. If this argument is not speci-
+ fied, the existing_database is used as the output database name.
+
+REPORT COMMAND
+ The following options are valid with the report command:
+
+ -c If -v is specified, displays covered line, toggle and combina-
+ tional cases. Default is to display uncovered information.
+
+ -d (s|d|v)
+ Level of detail to provide in coverage report information (s =
+ summary, d = detailed, v = verbose). Default is summary.
+
+ -h Displays this help information.
+
+ -i Provides coverage information for instances instead of module.
+
+ -m [l][t][c][f][r]
+ Type(s) of metrics to report. Default is ltcf.
+
+ -o filename
+ File to output report information to. Default is standard out-
+ put.
+
+ -v Deprecated. Replaced by �-d d� or �-d v�.
+
+ -view Starts the GUI interface for interactive coverage reporting.
+
+ -w (number)
+ Specifies the maximum line width (in characters) that can be
+ used to output Verilog information. If this option is not spec-
+ ified, all Verilog code in the report will retain the same for-
+ matting as was specified in the original Verilog code. If this
+ option is specified, Verilog code will be formatted to use as
+ much of the current line as possible, wrapping text when the
+ line reaches the maximum line width. The default maximum line
+ width is 115 characters (this value is used if no number is
+ specified with the -w option). If a number is specified with
+ the -w option, this value is used for the maximum line width.
+
+AUTHORS
+ Trevor Williams <trevorw@xxxxxxxxxxx>
+
+ Arpan Sen <arpan_sen@xxxxxxxxx>
+
+SEE ALSO
+ For more information on how to use the Covered code coverage tool,
+ please consult the on-line User�s Guide at http://covered.source-
+ forge.net/user/index.html.
+
+
+
+Trevor Williams covered-20060218 Covered(1)</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-csygas.html b/docs/wiki/geda-csygas.html
new file mode 100644
index 0000000..8433488
--- /dev/null
+++ b/docs/wiki/geda-csygas.html
@@ -0,0 +1,1395 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#circuit_simulation_using_geda_and_spice_-_howto" class="toc">Circuit Simulation using gEDA and SPICE - HOWTO</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#introduction" class="toc">Introduction</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#target_audience_for_this_howto" class="toc">Target audience for this HOWTO</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#acknowledgements" class="toc">Acknowledgements</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#the_big_picturethe_design_flow_in_geda" class="toc">The big picture: the design flow in gEDA</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#overview_of_spice_usage_with_geda" class="toc">Overview of SPICE usage with gEDA</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#detailed_design_simulation_flow_summary" class="toc">Detailed design/simulation flow summary</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#preliminary_workpreparing_your_symbols_and_spice_files" class="toc">Preliminary work: preparing your symbols and SPICE files</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#configuring_your_symbols" class="toc">Configuring your symbols</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#configuring_your_spice_files" class="toc">Configuring your SPICE files</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#creating_your_circuitschematic_capture" class="toc">Creating your circuit: schematic capture</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#gschem_attributes_for_spice_netlisting" class="toc">Gschem attributes for spice netlisting</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#component_attributes_and_meanings" class="toc">Component attributes and meanings</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#refdes_conventions" class="toc">refdes conventions</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#passives" class="toc">Passives</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#passives_with_additional_attributes" class="toc">Passives with additional attributes</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#passives_for_semiconductor_design" class="toc">Passives for semiconductor design</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#transistors_and_diodes" class="toc">Transistors and diodes</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#actives_--_integrated_circuits" class="toc">Actives -- integrated circuits</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#independent_sources" class="toc">Independent sources</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#dependent_sources" class="toc">Dependent sources</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#spice_components" class="toc">SPICE components</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#handling_hierarchical_models" class="toc">Handling hierarchical models</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#spice_netlist_generation" class="toc">SPICE netlist generation</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#using_gnetlist" class="toc">Using gnetlist</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#creating_the_netlist_using_gnetlist_and_spice-sdb" class="toc">Creating the netlist using gnetlist and spice-sdb</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#common_netlisting_problems" class="toc">Common netlisting problems</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#spice_simulation" class="toc">SPICE simulation</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#ltspice" class="toc">LTSpice</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#ngspice" class="toc">Ngspice</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#tclspice" class="toc">Tclspice</a></span></div></li>
+</ul>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"><span class="li"><a href="#appendix_a" class="toc">Appendix A</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#appendix_b" class="toc">Appendix B</a></span></div></li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="circuit_simulation_using_geda_and_spice_-_howto" id="circuit_simulation_using_geda_and_spice_-_howto">Circuit Simulation using gEDA and SPICE - HOWTO</a></h1>
+<div class="level1">
+
+<p>
+Stuart Brorson<br/>
+ Electroniscript, inc.<br/>
+ sdb@xxxxxxxxxxxxxxxxxxx<br/>
+ <br/>
+ 5th January 2006
+</p>
+
+<p>
+<strong>abstract</strong><br/>
+ Linux will become an increasingly popular engineering platform in the future. Professional-quality CAD applications for circuit design are becoming available from programmers within the free-software community. For electronics, the gEDA suite is the preferred tool set for circuit design. Analog circuit simulation using SPICE is also now available on Linux. This HOWTO describes the design flow employed to perform SPICE simulations using gEDA tools on Linux.
+</p>
+
+<p>
+Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 2 or any later version published by the Free Software Foundation with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. You may obtain a copy of the GNU Free Documentation License from the Free Software Foundation by visiting their Web site (<a href="http://www.fsf.org/"; class="urlextern" title="http://www.fsf.org/"; rel="nofollow">http://www.fsf.org/</a>) by writing to: Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. <a href="#fn__1" name="fnt__1" id="fnt__1" class="fn_top">1)</a>.
+</p>
+
+</div>
+<!-- SECTION "Circuit Simulation using gEDA and SPICE - HOWTO" [1-1357] -->
+<h2><a name="introduction" id="introduction">Introduction</a></h2>
+<div class="level2">
+
+<p>
+Modern engineering is a computer-intensive discipline. Like professionals in other engineering disciplines, electrical engineers and electronics designers are heavy users of all kinds of CAD software, including software for circuit design and simulation, as well as PCB and chip production. Electrical engineers have a special name for the CAD software they use: EDA, which stands for â??Electronic Design Automationâ??. Under this rubric fall many different kinds of CAD software. For example, during the front-end stages of a design, an electrical engineer will use a program called a â??schematic captureâ?? package to enter his design into the computer. A schematic capture program is basically a specialized drawing program incorporating symbols used in creating a circuit design. After drawing his schematic, the electrical engineer may choose to simulate the behavior of his circuit in order to verify that his design will work as desired. The most popular program for this purpose is SPICE (Simulation Program with Integrated Circuit Emphasis), which was developed at Berkeley starting in the 1970s, and is widely available in multiple forms today. SPICE is now considered a fundamental engineering tool, and is an essential part of the repertoire of most practicing engineers.
+</p>
+
+<p>
+The <a href="http://www.geda.seul.org/"; class="urlextern" title="http://www.geda.seul.org/"; rel="nofollow">gEDA project</a> is an open-source effort to create a <acronym title="GNU General Public License">GPL</acronym>â??ed EDA suite running on Linux. GEDA has developed to the point where the power and quality of the tools is quite high; using the gEDA suite, you can now create complex SPICE netlists (files) incorporating vendor model files. You can then use various simulators running on Linux to perform SPICE simulations of your netlists. The purpose of this document is to explain how to use the gEDA tools (typically running on GNU/Linux) to perform SPICE simulations. In particular, this HOWTO documents the usage of <strong>spice-sdb</strong>, which is an advanced backend for the gEDA netlister (<strong>gnetlist</strong>) used to create SPICE netlists. <strong>spice-sdb</strong> is bundled with the gEDA tool suite; if you have installed gEDA, you are ready to create SPICE netlists. This HOWTO also provides advice about using ngspice/tclspice and/or LTSpice to simulate a circuit netlisted with <strong>spice-sdb</strong>.
+</p>
+
+</div>
+<!-- SECTION "Introduction" [1358-3623] -->
+<h3><a name="target_audience_for_this_howto" id="target_audience_for_this_howto">Target audience for this HOWTO</a></h3>
+<div class="level3">
+
+<p>
+This HOWTO is not a tutorial about circuit design or SPICE simulation. Rather, it is designed to help the practicing engineer begin using gEDA to perform SPICE simulations on the Linux platform. Therefore, I assume that you are already familiar with electronic design, the mechanics of schematic capture using EDA tools, and SPICE simulation in general. I also assume that you are reasonably familiar with the GNU/Linux operating system and its development environment. Finally, I assume that you have already installed gEDA, and know how to use it. If you need to come up to speed on any of these subjects, further information is available at the following websites:
+</p>
+<ul>
+<li class="level1"><div class="li"> The gEDA project: <a href="http://www.geda.seul.org"; class="urlextern" title="http://www.geda.seul.org"; rel="nofollow">http://www.geda.seul.org</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-faq-simulation.html" class="wikilink1" title="geda-faq-simulation.html">faq-simulation</a></div>
+</li>
+<li class="level1"><div class="li"> SPICE3 syntax and commands: <a href="http://newton.ex.ac.uk/teaching/CDHW/Electronics2/userguide/"; class="urlextern" title="http://newton.ex.ac.uk/teaching/CDHW/Electronics2/userguide/"; rel="nofollow">http://newton.ex.ac.uk/teaching/CDHW/Electronics2/userguide/</a></div>
+</li>
+<li class="level1"><div class="li"> Ngspice: <a href="http://ngspice.sourceforge.net/"; class="urlextern" title="http://ngspice.sourceforge.net/"; rel="nofollow">http://ngspice.sourceforge.net/</a></div>
+</li>
+<li class="level1"><div class="li"> Tclspice: <a href="http://tclspice.sourceforge.net/"; class="urlextern" title="http://tclspice.sourceforge.net/"; rel="nofollow">http://tclspice.sourceforge.net/</a></div>
+</li>
+<li class="level1"><div class="li"> LTSpice: <a href="http://www.linear.com/software/"; class="urlextern" title="http://www.linear.com/software/"; rel="nofollow">http://www.linear.com/software/</a></div>
+</li>
+<li class="level1"><div class="li"> Spice on Linux resources: <a href="http://www.brorson.com/gEDA/SPICE/"; class="urlextern" title="http://www.brorson.com/gEDA/SPICE/"; rel="nofollow">http://www.brorson.com/gEDA/SPICE/</a></div>
+</li>
+<li class="level1"><div class="li"> Free Dog – The Free EDA Users Group: <a href="http://www.freeedaug.org/"; class="urlextern" title="http://www.freeedaug.org/"; rel="nofollow">http://www.freeedaug.org/</a></div>
+</li>
+<li class="level1"><div class="li"> Starting with gEDA – slightly out of date, but a great resource <a href="http://www-mdp.eng.cam.ac.uk/CD/engapps/geda/starting_gEDA_long.pdf"; class="urlextern" title="http://www-mdp.eng.cam.ac.uk/CD/engapps/geda/starting_gEDA_long.pdf"; rel="nofollow">http://www-mdp.eng.cam.ac.uk/CD/engapps/geda/starting_gEDA_long.pdf</a></div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Target audience for this HOWTO" [3624-4971] -->
+<h3><a name="acknowledgements" id="acknowledgements">Acknowledgements</a></h3>
+<div class="level3">
+
+<p>
+This document does not live in isolation. Several active members of the free EDA community were instrumental in helping me to creat this HOWTO. First and foremost, Paolo Nenzi, the author of ngspice, took my original HOWTO and turned it into a Lyx document which I could then make a DocBook. Thanks, Paolo, for helping with this HOWTO, and more importantly, thanks for all the great work on ngspice! Also at the top of the list stands Ales Hvezda, who is the driving force behind the gEDA project. Without Ales, none of this would have been possible; his contribution of <strong>gschem</strong> is invaluable. Thanks, Ales, for creating gEDA and distributing it worldwide under the <acronym title="GNU General Public License">GPL</acronym> – youâ??ve started a revolution! Stefan Jones deserves a deep thank-you for his work on tclspice, and his graceous support and integration efforts when I submitted patches to the tclspice project. I should also thank W. Kazubski and S. Gieltjes – they wrote the original SPICE netlisters upon which I based gnet-spice-sdb.scm. I also want to thank Ken Healy for contributing the netlist sorting patch, and Peter Kaiser for pushing me to include some features useful for chip simulation. Peter also deserves thanks for writing some of the device-oriented sections of this document. Finally, I should acknolwedge the contributions and suggestions I receive from readers of the geda-user e-mail list. The beauty of free software is that it encourages collaboration, which means that the end product is greater than what one individual could acheive alone.
+</p>
+
+</div>
+<!-- SECTION "Acknowledgements" [4972-6526] -->
+<h3><a name="the_big_picturethe_design_flow_in_geda" id="the_big_picturethe_design_flow_in_geda">The big picture: the design flow in gEDA</a></h3>
+<div class="level3">
+
+<p>
+In EDA, the concept of â??design flowâ?? is important. GEDA is a suite of tools used to do electronic design – it is not a single application. â??Design flowâ?? refers to the order in which you use the tools to acheive your goal. Depending upon whether you are doing analog or digital design, designing boards or chips, the type of files required by the manufacturer of your boards, and a number of other factors, you will use different tools from the gEDA suite to acheive your goal.
+</p>
+
+<p>
+A flow diagram of the gEDA design flow is shown in the figure below. The diagram shows a simple flow suitable for designing, simulating, and laying out PC boards. As can be seen, the simulation activitiy (blue blocks) is a loop. That is, you create your design and simulate it repeatedly until it behaves according to your desired specifications. <a href="media/geda/geda_flow.png" class="media" target="_blank" title="geda:geda_flow.png"><img src="media/geda/geda_flow.png" class="mediacenter" alt="" /></a> The design flow used in gEDA. Shown under â??simulationâ?? are several different types of simulator available. In this HOWTO, we are interested only in the SPICE variants (e.g. ngspice, tclspice).
+</p>
+
+</div>
+<!-- SECTION "The big picture: the design flow in gEDA" [6527-7623] -->
+<h3><a name="overview_of_spice_usage_with_geda" id="overview_of_spice_usage_with_geda">Overview of SPICE usage with gEDA</a></h3>
+<div class="level3">
+
+<p>
+Conceptually, SPICE simulation in gEDA proceeds via the following steps:
+</p>
+<ol>
+<li class="level1"><div class="li"> Creation and gathering of schematic symbols and SPICE model files. Often, the SPICE model files are obtained from your component vendor. You can generally find most models by checking the component vendorâ??s website.</div>
+</li>
+<li class="level1"><div class="li"> Schematic capture using symbols and SPICE models created in step 1.</div>
+</li>
+<li class="level1"><div class="li"> Netlist generation from the schematic created in step 2.</div>
+</li>
+<li class="level1"><div class="li"> SPICE simulation of the circuit described by the netlist created in step 3.</div>
+</li>
+</ol>
+
+<p>
+ These steps are illustrated by the blue boxes in the flow diagram above.
+</p>
+
+<p>
+To create a SPICE netlist, the netlister (<strong>gnetlist</strong>) iterates through the entire schematic and looks at several parts of each componentâ??s symbol in order to create a blob of SPICE code. In general, each component can generate one or more lines of SPICE code. Component information needed by the netlister is held in two places:
+</p>
+<ol>
+<li class="level1"><div class="li"> The symbol itself, in the attribute, which is attached when the symbol is created, and is typically accessed through the symbol editor.</div>
+</li>
+<li class="level1"><div class="li"> In attributes manually attached to the component during schematic capture using <strong>gschem</strong>.</div>
+</li>
+</ol>
+
+<p>
+ Since there are two places the netlister looks for information, <strong><em>you must make sure that the required information is available in both places</em></strong>.
+</p>
+
+</div>
+<!-- SECTION "Overview of SPICE usage with gEDA" [7624-8967] -->
+<h3><a name="detailed_design_simulation_flow_summary" id="detailed_design_simulation_flow_summary">Detailed design/simulation flow summary</a></h3>
+<div class="level3">
+
+<p>
+The detailed steps required to design and simulate a circuit using gEDA look like this:
+</p>
+<ol>
+<li class="level1"><div class="li"> Schematic symbol creation with correct <strong><code>device</code></strong> attribute. (Usually, the symbols have already been created with the correct <strong><code>device</code></strong> attribute, but if you are having problems, it doesnâ??t hurt to check them.)</div>
+</li>
+<li class="level1"><div class="li"> Schematic capture using <strong>gschem</strong>.</div>
+</li>
+<li class="level1"><div class="li"> Assignment of SPICE attributes (<strong><code>value</code></strong>, <strong><code>model</code></strong>, <strong><code>file</code></strong>, <strong><code>type</code></strong>, , etc.) to components using <strong>gschem</strong> or <strong>gattrib</strong>.</div>
+</li>
+<li class="level1"><div class="li"> Assignment of <strong><code>refdes</code></strong> using e.g. <strong>refdes_renum</strong>.</div>
+</li>
+<li class="level1"><div class="li"> Creation of netlist using: <strong><code>gnetlist -g spice-sdb</code></strong></div>
+</li>
+<li class="level1"><div class="li"> Check netlist for correctness (manually open and inspect netlist).</div>
+</li>
+<li class="level1"><div class="li"> Run spice using a simulator such as <strong>LTSpice</strong>, <strong>ngspice</strong>, or <strong>tclspice</strong>.</div>
+</li>
+<li class="level1"><div class="li"> Plot/analyze results (often plotting/analysis tools are incorporated in the simulator).</div>
+</li>
+<li class="level1"><div class="li"> If you are not happy with your circuitâ??s performance as revealed by simulation, go back to step 2, fix it using <strong>gschem</strong> and iterate.</div>
+</li>
+</ol>
+
+<p>
+ The purpose of this HOWTO is to provide the detailed understanding necessary to successfully navigate this process.
+</p>
+
+</div>
+<!-- SECTION "Detailed design/simulation flow summary" [8968-10147] -->
+<h2><a name="preliminary_workpreparing_your_symbols_and_spice_files" id="preliminary_workpreparing_your_symbols_and_spice_files">Preliminary work: preparing your symbols and SPICE files</a></h2>
+<div class="level2">
+
+<p>
+When you create schematic symbols for inclusion into your schematic, you must make sure that certain built-in attributes are correctly configured. The steps outlined below are done by editing the symbol itself using the symbol editor in <strong>gschem</strong>, or by editing the symbol file itself using a text editor.
+</p>
+
+</div>
+<!-- SECTION "Preliminary work: preparing your symbols and SPICE files" [10148-10526] -->
+<h3><a name="configuring_your_symbols" id="configuring_your_symbols">Configuring your symbols</a></h3>
+<div class="level3">
+
+</div>
+
+<h4><a name="identifying_the_component_to_the_netlister" id="identifying_the_component_to_the_netlister">Identifying the component to the netlister</a></h4>
+<div class="level4">
+
+<p>
+The SPICE netlister can recognize any particular symbol in two ways:
+</p>
+<ol>
+<li class="level1"><div class="li"> The symbolâ??s <strong><code>device</code></strong> attribute, and</div>
+</li>
+<li class="level1"><div class="li"> The symbolâ??s <strong><code>refdes</code></strong>.</div>
+</li>
+</ol>
+
+<p>
+ Both of these attributes are attached to the symbol when the symbol is created.
+</p>
+
+<p>
+Each symbol has a <strong><code>device</code></strong> attribute attached to it. The <strong><code>device</code></strong> attribute is the first thing the netlister examines when processing the symbol. There are a number of devices which are native to the netlister, meaning that the netlister knows exactly how to deal with these types of devices. Native device types include <strong>RESISTOR</strong>, <strong>CAPACITOR</strong>, <strong>NPN_TRANSISTOR</strong>, etc. The entire list of native devices is present in <a href="#appendix_a" title=":geda:csygas.txt ↵" class="wikilink1">Appendix A</a> - Native components and their attributes.
+</p>
+
+<p>
+The <strong><code>device</code></strong> attribute is hidden during normal use of <strong>gschem</strong>. Most often, the symbolâ??s creator has already given the symbol the correct <strong><code>device</code></strong> attribute. However, because the <strong><code>device</code></strong> attribute is hidden from the ordinary user, it can sometimes cause problems with SPICE netlist creation when it is set to an unexpected value. To view the <strong><code>device</code></strong> attribute, go into the symbol editor (select the symbol to edit, and do <strong><em>Hierarchy</em></strong> → <strong><em>down symbol</em></strong>, and turn on invisible attributes (<strong><em>Edit</em></strong> → <strong><em>show/hide inv text</em></strong>). If the <strong><code>device</code></strong> attribute is incorrect, you may change it by editing the symbol itself using a text editor.
+</p>
+
+<p>
+If a symbol is not native (i.e. the netlister doesnâ??t recognize it as a built-in type), the netlister relies upon the first letter of the <strong><code>refdes</code></strong> to determine how to process the symbol. The <strong><code>refdes</code></strong> prefix is also built into the symbol when it is created. Example <strong><code>refdes</code></strong> prefixes are <strong>R</strong> for resistors, <strong>C</strong> for capacitors, <strong>Q</strong> for transistors, etc. <strong><code>refdes</code></strong> prefixes correct for SPICE are listed in <a href="#appendix_a" title=":geda:csygas.txt ↵" class="wikilink1">Appendix A</a> - Native components and their attributes. Note that relying upon the <strong><code>refdes</code></strong> to identify the component for SPICE is not foolproof – for example, the netlister cannot distinguish between NPN and PNP transistors based upon the <strong><code>refdes</code></strong>. Therefore, it is always best to use a native <strong><code>device</code></strong> in your symbols.
+</p>
+
+</div>
+
+<h4><a name="setting_the_pin_order" id="setting_the_pin_order">Setting the pin order</a></h4>
+<div class="level4">
+
+<p>
+The netlister emits component pins in the order set by the <strong><code>pinseq</code></strong> attribute. Note that this is not the same as the physical pin location. To set the <strong><code>pinseq</code></strong> attribute, first determine the pin ordering you want. SPICE uses a specific pin order for many components, including diodes and transistors. For example, a bipolar transistorâ??s pins listed in CBE order. Another example: if your symbol is meant to represent an IC modeled with a vendorâ??s <strong><code>.subckt</code></strong>, the order of the connections to the subcircuit is set by the <strong><code>.subckt</code></strong> line in the file.
+</p>
+
+<p>
+Once you know the order in which to emit the pins, simply set the <strong><code>pinseq</code></strong> attribute with the correct order for the part. This will ensure that the partâ??s pins are emitted in the correct order.
+</p>
+
+</div>
+<!-- SECTION "Configuring your symbols" [10527-13603] -->
+<h3><a name="configuring_your_spice_files" id="configuring_your_spice_files">Configuring your SPICE files</a></h3>
+<div class="level3">
+
+<p>
+Files holding complicated SPICE models or other SPICE code may be incorporated into the final SPICE netlist by including appropriate symbols into the schematic. SPICE model files are usually obtained from component vendors. Dealing with these files is straightforward. However, some issues should be kept in mind when preparing models for use during schematic capture:
+</p>
+<ul>
+<li class="level1"><div class="li"> It is usually prudent to place these files into a dedicated directory distinct from the symbol directories.</div>
+</li>
+<li class="level1"><div class="li"> <em>Make sure that the SPICE files pin assignments correctly correspond to the pins as defined in the componentâ??s symbol!</em> This is hard to over-emphasize. The order in which pins are listed in a .subckt file do not necessarily correspond to the physical pin ordering of the part. As described above, pins are emitted from the netlister in the order given by the <strong><code>pinseq</code></strong> attribute.</div>
+</li>
+<li class="level1"><div class="li"> <em>Make sure that the last character in a SPICE model file is a carriage return.</em> If no carriage return exists, then the next component listed in the netlist may be placed on the same line as the last line of the SPICE model file.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Configuring your SPICE files" [13604-14750] -->
+<h2><a name="creating_your_circuitschematic_capture" id="creating_your_circuitschematic_capture">Creating your circuit: schematic capture</a></h2>
+<div class="level2">
+
+<p>
+Schematic capture is the process by which one uses a special-purpose drawing program to draw a schematic diagram of the circuit under design. In the gEDA environment, the schematic capture program is called <strong>gschem</strong>. I assume you already know how to use <strong>gschem</strong>. If not, consult the documentation available at the gEDA website: <a href="http://www.geda.seul.org/"; class="urlextern" title="http://www.geda.seul.org/"; rel="nofollow">http://www.geda.seul.org/</a>. For the purposes of creating SPICE netlists, you must use <strong>gschem</strong> to attach attributes to components, and possibly also incorporate other SPICE directives into your netlist. After you are done with schematic capture, you create the SPICE netlist by running gEDAâ??s netlister <strong>gnetlist</strong> on your design.
+</p>
+
+</div>
+<!-- SECTION "Creating your circuit: schematic capture" [14751-15474] -->
+<h3><a name="gschem_attributes_for_spice_netlisting" id="gschem_attributes_for_spice_netlisting">Gschem attributes for spice netlisting</a></h3>
+<div class="level3">
+
+<p>
+There are several ways that spice attributes may be associated with a component using <strong>gschem</strong>. The way you choose to do this depends upon many factors, including the type of component, and the size and format of the SPICE model.
+</p>
+
+</div>
+<!-- SECTION "Gschem attributes for spice netlisting" [15475-15756] -->
+<h3><a name="component_attributes_and_meanings" id="component_attributes_and_meanings">Component attributes and meanings</a></h3>
+<div class="level3">
+
+<p>
+The following attributes are meaningful for SPICE netlisting, and may be attached from within <strong>gschem</strong>:
+</p>
+<ul>
+<li class="level1"><div class="li"> <strong><code>refdes</code></strong>: The reference designator of the component. Valid values depend upon the component type and are given in <a href="#appendix_a" title=":geda:csygas.txt ↵" class="wikilink1">Appendix A</a> - Native components and their attributes.</div>
+</li>
+<li class="level1"><div class="li"> <strong><code>value</code></strong>: For passives, this is the component value. For actives, this is the type (model no.) of the component (e.g. 2N3904, uA741). When a model for an active is instantiated separately from the component itself, the <strong><code>value</code></strong> attribute holds the name of the spice model.</div>
+</li>
+<li class="level1"><div class="li"> <strong><code>model</code></strong>: This holds a one line spice model for the component.</div>
+</li>
+<li class="level1"><div class="li"> <strong><code>file</code></strong>: This holds the name of a file. Typically, this is a file holding e.g. a SPICE .MODEL, .SUBCKT, or other SPICE code.</div>
+</li>
+<li class="level1"><div class="li"> <strong><code>model-name</code></strong>: This holds the name of the spice model referred to in a .MODEL or .SUBCKT statement. <strong><code>model-name</code></strong> is mainly used to identify the spice model name in the symbol <strong><code>spice-model-1.sym</code></strong>. Active components should call out this name in the <strong><code>device</code></strong> attribute to associate the component with its particular spice model or subcircuit.</div>
+</li>
+<li class="level1"><div class="li"> <strong><code>type</code></strong>: This specifies the type of component and is used by spice when interpreting the model parameters. Valid values depend upon the device being modeled.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Component attributes and meanings" [15757-17116] -->
+<h3><a name="refdes_conventions" id="refdes_conventions">refdes conventions</a></h3>
+<div class="level3">
+
+<p>
+As a prerequisite to handling SPICE-related attributes, the SPICE netlister requires that all components must have a <strong><code>refdes</code></strong> attached to them. The <strong><code>refdes</code></strong> may be attached either by hand (which is laborious), or using the program <strong>refdes_renum</strong> included in the gEDA distribution.
+</p>
+
+<p>
+Note that the first letter of the <strong><code>refdes</code></strong> must correspond to the appropriate letter for spice simulation. The <strong><code>refdes</code></strong> convention is given in the appendix.
+</p>
+
+</div>
+<!-- SECTION "refdes conventions" [17117-17611] -->
+<h3><a name="passives" id="passives">Passives</a></h3>
+<div class="level3">
+
+</div>
+
+<h4><a name="basic_passives" id="basic_passives">Basic passives</a></h4>
+<div class="level4">
+
+<p>
+The most basic components which one encounters in SPICE are passive components like resistors and capacitors which have numeric values, but no other modeling attributes. In this case the following attributes must be filled in:
+</p>
+<ul>
+<li class="level1"><div class="li"> <strong><code>refdes</code></strong>: The correct <strong><code>refdes</code></strong> for the component.</div>
+</li>
+<li class="level1"><div class="li"> <strong><code>value</code></strong>: For passives, this is the numeric value of the component (e.g. 100pF). For actives, this attribute may be filled in, but if no model attribute is available elsewhere in the schematic, the value is not used (in SPICE netlisting, anyway).</div>
+</li>
+<li class="level1"><div class="li"> If only a <strong><code>refdes</code></strong> and <strong><code>value</code></strong> attribute are encountered, the netlister will write a single line into the output file.</div>
+</li>
+</ul>
+
+</div>
+
+<h4><a name="example_resistor" id="example_resistor">Example resistor:</a></h4>
+<div class="level4">
+<ul>
+<li class="level1"><div class="li"> <strong><code>refdes</code></strong> = R2</div>
+</li>
+<li class="level1"><div class="li"> <strong><code>value</code></strong> = 220</div>
+</li>
+</ul>
+
+<p>
+ SPICE line generated: <strong><code>R2 0 4 220</code></strong>
+</p>
+
+<p>
+(note that â??0â?? and â??4â?? correspond to the net nodes connected to the component, and are generated automatically by <strong>gnetlist</strong>.)
+</p>
+
+</div>
+
+<h4><a name="example_capacitor" id="example_capacitor">Example capacitor:</a></h4>
+<div class="level4">
+<ul>
+<li class="level1"><div class="li"> <strong><code>refdes</code></strong> = C22</div>
+</li>
+<li class="level1"><div class="li"> <strong><code>value</code></strong> = 1UF</div>
+</li>
+</ul>
+
+<p>
+ SPICE line generated: <strong><code>C22 4 23 1UF</code></strong>
+</p>
+
+</div>
+<!-- SECTION "Passives" [17612-18707] -->
+<h3><a name="passives_with_additional_attributes" id="passives_with_additional_attributes">Passives with additional attributes</a></h3>
+<div class="level3">
+
+<p>
+Oftentimes, passive components have additional attributes attached to them for spice simulation. Examples of such attributes are temperature coefficients (for resistors) and initial conditions (for reactive components). These additional components may be incorporated into the SPICE file by simply attaching them to the componentâ??s <strong><code>model</code></strong> attribute. Specifically, the required attributes are:
+</p>
+<ul>
+<li class="level1"><div class="li"> <strong><code>refdes</code></strong>: Correct component <strong><code>refdes</code></strong>.</div>
+</li>
+<li class="level1"><div class="li"> <strong><code>value</code></strong>: Numerical component <strong><code>value</code></strong>, as always.</div>
+</li>
+<li class="level1"><div class="li"> <strong><code>model</code></strong>: One line string holding additional parameters, formatted as a valid SPICE string.</div>
+</li>
+</ul>
+
+<p>
+ This string is placed after the component value in the line generated by gnetlist. Therefore, it is important to format the string placed in the <strong><code>model</code></strong> line to be valid SPICE code. Otherwise, you will risk causing the SPICE simulator to barf.
+</p>
+
+</div>
+
+<h4><a name="example_resistor1" id="example_resistor1">Example resistor:</a></h4>
+<div class="level4">
+<ul>
+<li class="level1"><div class="li"> <strong><code>refdes</code></strong> = R5</div>
+</li>
+<li class="level1"><div class="li"> <strong><code>value</code></strong> = 1MEG</div>
+</li>
+<li class="level1"><div class="li"> <strong><code>model</code></strong> = TC=0.001,0.015</div>
+</li>
+</ul>
+
+<p>
+ SPICE line generated: <strong><code>R2 0 4 220 TC=0.001,0.015</code></strong>
+</p>
+
+</div>
+<!-- SECTION "Passives with additional attributes" [18708-19793] -->
+<h3><a name="passives_for_semiconductor_design" id="passives_for_semiconductor_design">Passives for semiconductor design</a></h3>
+<div class="level3">
+
+<p>
+The values for resistors and capacitors are often given as dimensions in an ASIC design. SPICE takes from the technology library the typical value per square and calculates the actual value in Ohm or Farad by itself. Therefor the following attributes are required:
+</p>
+<ul>
+<li class="level1"><div class="li"> <strong><code>refdes</code></strong>: The correct refdes for the component.</div>
+</li>
+<li class="level1"><div class="li"> <strong><code>model-name</code></strong>: corresponds to the model in the technology library.</div>
+</li>
+<li class="level1"><div class="li"> <strong><code>w</code></strong>, <strong><code>l</code></strong>: dimensions of the device.</div>
+</li>
+</ul>
+
+<p>
+ The technology library must be included with an <strong><code>.include</code></strong> line in the SPICE input file.
+</p>
+
+</div>
+
+<h4><a name="example_semiconductor_resistor" id="example_semiconductor_resistor">Example semiconductor resistor:</a></h4>
+<div class="level4">
+<ul>
+<li class="level1"><div class="li"> <strong><code>refdes</code></strong> = R6</div>
+</li>
+<li class="level1"><div class="li"> <strong><code>model-name</code></strong> = rpoly</div>
+</li>
+<li class="level1"><div class="li"> <strong><code>w</code></strong> = 3u</div>
+</li>
+<li class="level1"><div class="li"> <strong><code>l</code></strong> = 100u</div>
+</li>
+</ul>
+
+<p>
+ SPICE line generated: <strong><code>R6 0 5 rpoly w=3u l=100u</code></strong>
+</p>
+
+</div>
+
+<h4><a name="example_semiconductor_resistor_model" id="example_semiconductor_resistor_model">Example semiconductor resistor model:</a></h4>
+<div class="level4">
+<ul>
+<li class="level1"><div class="li"> model rpoly R rsh=300</div>
+</li>
+</ul>
+
+<p>
+ This should be part of the technology library from your ASIC vendor.
+</p>
+
+</div>
+<!-- SECTION "Passives for semiconductor design" [19794-20720] -->
+<h3><a name="transistors_and_diodes" id="transistors_and_diodes">Transistors and diodes</a></h3>
+<div class="level3">
+
+<p>
+Transistors and diodes are generally accompanied by a device-specific model. Each model attempts to capture the detailed nonlinear dynamics of its particular device; otherwise, SPICE simulation is pointless. The SPICE model may be either a short, one-line string of parameters, or a multi-line set of SPICE parameters. A typical one-line parameter string is a short list of parameters describing a small-signal diode. Typical multi-line models come from component vendors, who often provide models for their components in a text file. Since there are two broad formats of SPICE information, there are two approaches to incorporating these parameters into the schematic:
+</p>
+
+</div>
+
+<h4><a name="one_line_string_of_spice_parameters" id="one_line_string_of_spice_parameters">One line string of SPICE parameters</a></h4>
+<div class="level4">
+
+<p>
+To incorporate a one line string of SPICE parameters into the netlist, the following attributes must be attached to the component:
+</p>
+<ul>
+<li class="level1"><div class="li"> <strong><code>refdes</code></strong>: Correct component <strong><code>refdes</code></strong>.</div>
+</li>
+<li class="level1"><div class="li"> <strong><code>value</code></strong>: The model number or part number of the component.</div>
+</li>
+<li class="level1"><div class="li"> <strong><code>model-name</code></strong>: The name you wish to give the SPICE model. This is usually the model number or part number of the component. If you have already attached a <strong><code>value</code></strong> attribute to the component, this parameter is optional.</div>
+</li>
+<li class="level1"><div class="li"> <strong><code>model</code></strong>: One line string holding additional parameters. Do not place the model parameters in parentheses – <strong>gnetlist</strong> will do this for you.</div>
+</li>
+</ul>
+
+</div>
+
+<h4><a name="example_diode" id="example_diode">Example diode:</a></h4>
+<div class="level4">
+<ul>
+<li class="level1"><div class="li"> <strong><code>refdes</code></strong> = D5</div>
+</li>
+<li class="level1"><div class="li"> <strong><code>model-name</code></strong> = 1N1004</div>
+</li>
+<li class="level1"><div class="li"> <strong><code>model</code></strong> = IS=0.5UA RS=6 BV=5.20</div>
+</li>
+</ul>
+
+<p>
+ SPICE lines generated: <strong><code>D5 2 6 1N1004 MODEL 1N1004 D (IS=0.5UA RS=6 BV=5.20)</code></strong>
+</p>
+
+</div>
+
+<h4><a name="spice_model_file" id="spice_model_file">SPICE model file</a></h4>
+<div class="level4">
+
+<p>
+To incorporate a file-full of SPICE parameters into the netlist, the following attributes must be attached to the component:
+</p>
+<ul>
+<li class="level1"><div class="li"> <strong><code>refdes</code></strong>: Correct component <strong><code>refdes</code></strong>.</div>
+</li>
+<li class="level1"><div class="li"> <strong><code>value</code></strong>: The model number or part number of the component.</div>
+</li>
+<li class="level1"><div class="li"> <strong><code>model-name</code></strong>: the name you wish to give the SPICE model. This is usually the model number or part number of the component. If you have already attached a <strong><code>value</code></strong> attribute to the component, this parameter is optional.</div>
+</li>
+<li class="level1"><div class="li"> <strong><code>file</code></strong>: The file name of the SPICE model which you wish to incorporate into the netlist. This file name may specify either a relative or an absolute path, but it is probably better to use an absolute path to avoid problems if you ever move your schematic directory.</div>
+</li>
+</ul>
+
+<p>
+ Note that you need to make sure that the model name held in your SPICE model file is the same as the <strong><code>value</code></strong> or <strong><code>model-name</code></strong> attributes you attached to the component. It is also a good idea to verify that the pin assignments in the model file correspond to the pin assignments made by the component symbol.
+</p>
+
+</div>
+<!-- SECTION "Transistors and diodes" [20721-23421] -->
+<h3><a name="actives_--_integrated_circuits" id="actives_--_integrated_circuits">Actives -- integrated circuits</a></h3>
+<div class="level3">
+
+<p>
+Integrated circuits are incorporated into the netlist similarly to transistors and diodes. As such, you may incorporate the spice information either as a one-line parameter string, or as a model file.
+</p>
+
+</div>
+
+<h4><a name="one_line_string_of_spice_parameters1" id="one_line_string_of_spice_parameters1">One line string of SPICE parameters</a></h4>
+<div class="level4">
+
+<p>
+To incorporate a one line string of SPICE parameters into the netlist, the following attributes must be attached to the component:
+</p>
+<ul>
+<li class="level1"><div class="li"> <strong><code>refdes</code></strong>: Correct component <strong><code>refdes</code></strong>.</div>
+</li>
+<li class="level1"><div class="li"> <strong><code>value</code></strong>: The model number or part number of the component.</div>
+</li>
+<li class="level1"><div class="li"> <strong><code>model-name</code></strong>: the name you wish to give the SPICE model. This is usually the model number or part number of the component. If you have already attached a <strong><code>value</code></strong> attribute to the component, this parameter is optional.</div>
+</li>
+<li class="level1"><div class="li"> <strong><code>model</code></strong>: One line string holding additional parameters. Do not place the model parameters in parentheses – <strong>gnetlist</strong> will do this for you.</div>
+</li>
+</ul>
+
+</div>
+
+<h4><a name="spice_.model_or_.subckt_file" id="spice_.model_or_.subckt_file">SPICE .MODEL or .SUBCKT file</a></h4>
+<div class="level4">
+
+<p>
+To incorporate a file-full of SPICE parameters into the netlist, the following attributes must be attached to the component:
+</p>
+<ul>
+<li class="level1"><div class="li"> <strong><code>refdes</code></strong>: Correct component <strong><code>refdes</code></strong>. <em>Note that if the file holds a .MODEL, the</em> <strong><code>refdes</code></strong> <em>should start with U; if the file holds a .SUBCKT, the refdes should start with X.</em> The netlister checks for the file type and tries to â??do the right thingâ??, but problems can arise if you donâ??t follow this rule.</div>
+</li>
+<li class="level1"><div class="li"> <strong><code>value</code></strong>: The model number or part number of the component.</div>
+</li>
+<li class="level1"><div class="li"> <strong><code>model-name</code></strong>: The name you wish to give the SPICE model. This is usually the model number or part number of the component. If you have already attached a <strong><code>value</code></strong> attribute to the component, this parameter is optional.</div>
+</li>
+<li class="level1"><div class="li"> <strong><code>file</code></strong>: The name of the file holding the SPICE .MODEL or .SUBCKT which you wish to incorporate into the netlist. This file name may specify either a relative or an absolute path, but it is probably better to use an absolute path to avoid problems if you ever move your schematic directory.</div>
+</li>
+</ul>
+
+<p>
+ Note that you need to make sure that the model name held in your SPICE model file is the same as the <strong><code>value</code></strong> or <strong><code>model-name</code></strong> attributes you attached to the component. It is also a good idea to verify that the pin assignments in the model file correspond to the pin assignments made by the component symbol.
+</p>
+
+</div>
+<!-- SECTION "Actives -- integrated circuits" [23422-25765] -->
+<h3><a name="independent_sources" id="independent_sources">Independent sources</a></h3>
+<div class="level3">
+
+<p>
+There are two independent sources: voltage sources and current sources. For incorporation into a SPICE netlist, they both work the same way. To incorporate an independent source into your SPICE netlist, do the following:
+</p>
+<ol>
+<li class="level1"><div class="li"> Place the independent source on your schematic. (Do <strong><em>Add</em></strong> → <strong><em>Component</em></strong> → <strong><em>spice</em></strong> → <strong><independent source name>.sym</strong>)</div>
+</li>
+<li class="level1"><div class="li"> Double click on the block and add/edit the following attributes:</div>
+<ul>
+<li class="level2"><div class="li"> <strong><code>refdes</code></strong>: V? or I?</div>
+</li>
+<li class="level2"><div class="li"> <strong><code>value</code></strong>: A one line string in SPICE format describing the source.</div>
+</li>
+</ul>
+</li>
+</ol>
+
+</div>
+<!-- SECTION "Independent sources" [25766-26339] -->
+<h3><a name="dependent_sources" id="dependent_sources">Dependent sources</a></h3>
+<div class="level3">
+
+<p>
+There are four dependent sources:
+</p>
+
+<p>
+This section remains TBD.
+</p>
+
+</div>
+<!-- SECTION "Dependent sources" [26340-26429] -->
+<h3><a name="spice_components" id="spice_components">SPICE components</a></h3>
+<div class="level3">
+
+</div>
+
+<h4><a name="spice_model_block" id="spice_model_block">Spice model block</a></h4>
+<div class="level4">
+
+<p>
+In certain situations, you may wish to embed a spice model block directly into your schematic. This is done when you have several devices with a â??valueâ?? attribute calling out for a spice model. Depending upon whether the spice block is one line or multi-line, you may embed the code in one of two ways:
+</p>
+
+</div>
+
+<h4><a name="one_line_spice_model" id="one_line_spice_model">One line SPICE model:</a></h4>
+<div class="level4">
+<ol>
+<li class="level1"><div class="li"> Place a spice model block on your schematic. (Do <strong><em>Add</em></strong> → <strong><em>Component</em></strong> → <strong><em>spice</em></strong> → <strong>spice-model-1.sym</strong>)</div>
+</li>
+<li class="level1"><div class="li"> Double click on the block and add/edit the following attributes:</div>
+<ul>
+<li class="level2"><div class="li"> <strong><code>refdes</code></strong>: A?</div>
+</li>
+<li class="level2"><div class="li"> <strong><code>model</code></strong>: model name (i.e. the model name used in the components being modeled)</div>
+</li>
+<li class="level2"><div class="li"> <strong><code>type</code></strong>: One of the valid spice component types defined in the spice <acronym title="specification">spec</acronym>.</div>
+</li>
+<li class="level2"><div class="li"> <strong><code>value</code></strong>: The corresponding one-line spice model</div>
+</li>
+</ul>
+</li>
+</ol>
+
+</div>
+
+<h4><a name="multi-line_spice_model" id="multi-line_spice_model">Multi-line SPICE model:</a></h4>
+<div class="level4">
+<ol>
+<li class="level1"><div class="li"> Place a spice model block on your schematic.(Do <strong><em>Add</em></strong> → <strong><em>Component</em></strong> → <strong><em>spice</em></strong> → <strong>spice-model-1.sym</strong>)</div>
+</li>
+<li class="level1"><div class="li"> Double click on the block and add/edit the following attributes:</div>
+<ul>
+<li class="level2"><div class="li"> <strong><code>refdes</code></strong>: A?</div>
+</li>
+<li class="level2"><div class="li"> <strong><code>model</code></strong>: model name</div>
+</li>
+<li class="level2"><div class="li"> <strong><code>file</code></strong>: Name of file holding SPICE model code (i.e. .MODEL or .SUBCKT).</div>
+</li>
+</ul>
+</li>
+</ol>
+
+</div>
+
+<h4><a name="include_block" id="include_block">Include block</a></h4>
+<div class="level4">
+
+<p>
+The include block places a .INCLUDE directive into your netlist.
+</p>
+<ol>
+<li class="level1"><div class="li"> Place a spice model block on your schematic. (Do <strong><em>Add</em></strong> → <strong><em>Component</em></strong> → <strong><em>spice</em></strong> → <strong>spice-include-1.sym</strong>)</div>
+</li>
+<li class="level1"><div class="li"> Double click on the block and add/edit the following attributes:</div>
+<ul>
+<li class="level2"><div class="li"> <strong><code>refdes</code></strong>: A?</div>
+</li>
+<li class="level2"><div class="li"> <strong><code>file</code></strong>: Name of file to include.</div>
+</li>
+</ul>
+</li>
+</ol>
+
+</div>
+
+<h4><a name="spice_directive_block" id="spice_directive_block">SPICE directive block</a></h4>
+<div class="level4">
+
+<p>
+Placing a SPICE directive block into your schematic creates an arbitrary block of SPICE code in the netlist. The directive may be either statements held in a file, or a one-line string held in the <strong><code>model</code></strong> attribute. The netlister will simply dump the contents of the string or the file into your netlist verbatim. Examples of situations where this is useful include:
+</p>
+<ul>
+<li class="level1"><div class="li"> .TEMP statement</div>
+</li>
+<li class="level1"><div class="li"> .IC statement</div>
+</li>
+<li class="level1"><div class="li"> Other SPICE statements for which <strong>gschem</strong> has no symbol.</div>
+</li>
+</ul>
+
+<p>
+ To place a SPICE directive on your schematic, do:
+</p>
+<ol>
+<li class="level1"><div class="li"> Place a SPICE directive block on your schematic. (Do <strong><em>Add</em></strong> → <strong><em>Component</em></strong> → <strong><em>spice</em></strong> → <strong>spice-directive-1.sym</strong>)</div>
+</li>
+<li class="level1"><div class="li"> Double click on the block and add/edit the following attributes:</div>
+<ul>
+<li class="level2"><div class="li"> <strong><code>refdes</code></strong>: A?</div>
+</li>
+<li class="level2"><div class="li"> <strong><code>file</code></strong>: Name of file to include.</div>
+</li>
+</ul>
+</li>
+</ol>
+
+</div>
+<!-- SECTION "SPICE components" [26430-28839] -->
+<h3><a name="handling_hierarchical_models" id="handling_hierarchical_models">Handling hierarchical models</a></h3>
+<div class="level3">
+
+<p>
+In SPICE modeling, there are often situations where you wish to create a schematic representation of some particular component as a .SUBCKT, and then embed that componentâ??s model in a higher level schematic. A common example might be as follows: You are doing a microwave simulation, and want to use a capacitor model which includes parasitic inductances and resistances, as well as the capacitance. Capacitor manufacturers often supply a printed schematic showing a circuit topology incorporating parasitics, and specify values for the parasitics. You would like to draw the capacitor model using gschem, netlist it to create a .SUBCKT, and then use the .SUBCKT to model capacitors in a higher lever schematic.
+</p>
+
+<p>
+Since this kind of task is very common in SPICE simulation, <strong>gnet-spice-sdb</strong> now supports it (starting with rev 20030331). To create a lower level .SUBCKT and use it in a higher level schematic, do the following:
+</p>
+<ol>
+<li class="level1"><div class="li"> Draw the schematic of the lower level component (e.g. the capacitor + parasitics) using <strong>gschem</strong>.</div>
+</li>
+<li class="level1"><div class="li"> On the lower level schematic, place a <strong><code>spice-subcircuit-LL</code></strong> block (<strong>spice-subcircuit-LL-1.sym</strong>). This alerts the netlister that the schematic is a Lower Level .SUBCKT. Attach the following attributes to the symbol:<br/>
+ <br/>
+ * <strong><code>model-name</code></strong> = cap_with_parasitics<br/>
+ <br/>
+ (Of course, â??cap_with_parasiticsâ?? is the example we use here. Use your own model name in your schematic.) Upon netlisting, this schematic symbol will cause the netlist to insert ".SUBCKT cap_with_parasiticsâ?? into the first line of the netlist file.</div>
+</li>
+<li class="level1"><div class="li"> On the lower level schematic, attach a <strong><code>spice-subcircuit-IO</code></strong> symbol (<strong>spice-subcircuit-IO-1.sym</strong>) to each IO net (i.e. connection to the upper level). Number the refdeses of the IO symbols in the same order as you would like the IO nets to be listed in the .SUBCKT line in the output file. (i.e. P1 = first, P2 = second, etc.)</div>
+</li>
+<li class="level1"><div class="li"> When you are done with the lower level schematic, netlist it in the usual way. For example, if your schematic is called <strong><code>cap_with_parasitics.sch</code></strong>, netlist it by saying: <br/>
+ <br/>
+ <strong><code>gnetlist -g spice-sdb -o cap_with_parasitics.cir cap_with_parasitics.sch</code></strong><br/>
+ <br/>
+ This will dump the SPICE netlist into the file called â??<strong>cap_with_parasitics.cir</strong>â??. Visually inspect the .cir file to make sure that netlisting worked correctly.</div>
+</li>
+<li class="level1"><div class="li"> Next, create a symbol for the upper level schematic which will point to the .SUBCKT. Note that the symbol must have a starting with the letter â??Xâ??. To ensure that this happens, do the following:</div>
+<ul>
+<li class="level2"><div class="li"> Use <strong>gschem</strong> to draw the symbol. I usually draw a box around a model symbol to distinguish it from a normal component. Make any other annotations desired.</div>
+</li>
+<li class="level2"><div class="li"> In the symbol, make sure that the pins are ordered identically to the order in which you have placed the pins in the .SUBCKT. This is done by editing the symbol with a text editor and setting the <strong><code>pinseq</code></strong> attribute. The netlister will output the pins in the order determined by the <strong><code>pinseq</code></strong> attribute.</div>
+</li>
+<li class="level2"><div class="li"> Using a text editor, give the symbol a <strong><code>device</code></strong> attribute like â??capacitor-modelâ??. Do <strong>not</strong> assign the symbol one of the native device types listed in the appendix! The goal is to create a symbol whose <strong><code>refdes</code></strong> starts with â??Xâ??, and if the <strong><code>device</code></strong> is a recognized type, this will not happen.</div>
+</li>
+<li class="level2"><div class="li"> Using a text editor, give the symbol the <strong><code>refdefs</code></strong> attribute â??X?"</div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> Create the upper level schematic. Place your newly created symbol on the schematic as many times as required and wire up the schematic in the usual way.</div>
+</li>
+<li class="level1"><div class="li"> To point your symbol to the lower level .SUBCKT, double click on the symbol and set the following attributes:<br/>
+ <br/>
+ * <strong><code>file</code></strong> = cap_with_parasitics.cir<br/>
+ * <strong><code>model-name</code></strong> = cap_with_parasitics<br/>
+ <br/>
+ as well as any other attributes required (e.g. <strong><code>refdes</code></strong>).</div>
+</li>
+<li class="level1"><div class="li"> Now netlist your upper level schematic the usual way. The contents of each .SUBCKT file is dumped into the main netlist. Inspect your netlist visually using a text editor to ensure that it is correct. It is a good idea to pay particular attention to the following:</div>
+<ul>
+<li class="level2"><div class="li"> Verify that the ordering of the nets connecting the upper level netlist to the lower level .SUBCKT is correct.</div>
+</li>
+<li class="level2"><div class="li"> Make sure that the upper level model-name and the lower level model name (on the .SUBCKT declaration line) are the same.</div>
+</li>
+</ul>
+</li>
+</ol>
+
+<p>
+ Once the netlist is created, you may simulate your design using any SPICE simulator desired. Some simulators running on Linux are covered below.
+</p>
+
+</div>
+<!-- SECTION "Handling hierarchical models" [28840-33380] -->
+<h2><a name="spice_netlist_generation" id="spice_netlist_generation">SPICE netlist generation</a></h2>
+<div class="level2">
+
+</div>
+<!-- SECTION "SPICE netlist generation" [33381-33417] -->
+<h3><a name="using_gnetlist" id="using_gnetlist">Using gnetlist</a></h3>
+<div class="level3">
+
+<p>
+Once the schematic is captured, a SPICE netlist can be generated running gEDAâ??s command-line program <strong>gnetlist</strong> on the schematic files. <strong>gnetlist</strong> is architected in two sections: a front-end processor written in C which reads in the .sch file and creates from it an internal, generic representation of your design, and a back-end netlister written in SCHEME. Using this architecture, <strong>gnetlist</strong> is highly customizable; different SCHEME backends are used to write out different netlist formats. The beauty of this scheme (pun intended) is that gEDA users can easily write their own netlisters to suit their own applications. The back-end Scheme file which implements advanced SPICE netlisting is called <strong><code>gnet-spice-sdb.scm</code></strong>, and it lives in the <strong><code>${PREFIX}/geda/share/gEDA/scheme</code></strong> directory.
+</p>
+
+<p>
+<strong>gnetlist</strong> with <strong>spice-sdb</strong> is invoked from the command line in the following way: <strong><code>gnetlist [OPTIONS] -g spice-sdb filename1 … filenameN</code></strong>. The following command-line options are available with spice-sdb:
+</p>
+<pre class="code">-i Interactive scheme mode
+-I Put .INCLUDE <filename> in output file instead of model file's contents
+-q Quiet mode
+-l filename Load scheme file before loading backend
+-m filename Load scheme file after loading backend, but still before executing procedure
+-g proc Scheme procedure to execute (i.e. spice-sdb)
+-o filename Output netlist filename
+-c string Execute string as a scheme script
+-v Verbose mode on
+-s Sort output netlist (for Gnucap)</pre>
+
+</div>
+<!-- SECTION "Using gnetlist" [33418-34978] -->
+<h3><a name="creating_the_netlist_using_gnetlist_and_spice-sdb" id="creating_the_netlist_using_gnetlist_and_spice-sdb">Creating the netlist using gnetlist and spice-sdb</a></h3>
+<div class="level3">
+
+<p>
+Creating a netlist from a schematic is easy. To generate a SPICE netlist, just do the following:
+</p>
+<ul>
+<li class="level1"><div class="li"> Save your schematic to <<strong><code>filename.sch</code></strong>></div>
+</li>
+<li class="level1"><div class="li"> Create the SPICE netlist by doing â??<strong><code>gnetlist -g spice-sdb <filename.sch></code></strong>â??. The output is a netlist held in the file <strong><code>output.net</code></strong>. Alternatively, if you wish to give your output file a different name, set the output name using the <strong>-o</strong> switch. For example:<br/>
+ <br/>
+ <strong><code>gnetlist -g spice-sdb -o amplifier.cir amplifier.sch</code></strong><br/>
+ <br/>
+ takes the design schematic called â??<strong><code>amplifier.sch</code></strong>â?? and outputs a SPICE netlist named â??<strong><code>amplifier.cir</code></strong>â??.</div>
+</li>
+<li class="level1"><div class="li"> Inspect your SPICE netlist using a text editor. Verify that there are no missing attributes or other netlist problems.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Creating the netlist using gnetlist and spice-sdb" [34979-35772] -->
+<h3><a name="common_netlisting_problems" id="common_netlisting_problems">Common netlisting problems</a></h3>
+<div class="level3">
+
+<p>
+The following list attempts to catalog common problems with the netlist and the associated fixes:
+</p>
+<ul>
+<li class="level1"><div class="li"> ERROR_INVALID_<acronym title="Personal Identification Number">PIN</acronym>:<br/>
+ This can happen if the symbolâ??s <strong><code>pinseq</code></strong> attributes donâ??t start at 1, or have gaps in the numbering. This must be fixed by editing the symbol itself in a text editor.</div>
+</li>
+<li class="level1"><div class="li"> ERROR: In procedure caddr:<br/>
+ This error is quite common. It usually occurs when you forget to add a mandatory attribute. To rectify the problem, try running gnetlist in verbose mode (<strong><code>gnetlist -v -g spice-sdb <filename.sch></code></strong>). The netlister will stop processing and bomb out at the part with the missing attribute. Having therefore identified the offending part, you can re-open the schematic in gnetlist and fix the attributes.</div>
+</li>
+</ul>
+
+<p>
+ Finally, remember that it is important to manually inspect your SPICE netlist prior to using it in simulation. Please keep in mind that the netlister is still â??betaâ?? quality, and some problems may still exist in netlist generation.
+</p>
+
+</div>
+<!-- SECTION "Common netlisting problems" [35773-36778] -->
+<h2><a name="spice_simulation" id="spice_simulation">SPICE simulation</a></h2>
+<div class="level2">
+
+<p>
+There are several options for doing SPICE simulations under GNU/Linux; I will highlight three:
+</p>
+<ul>
+<li class="level1"><div class="li"> <strong>LTSpice</strong>, which is a freeware SPICE simulator originally released by Linear Technologies as a component selection/design tool running under Windows. Because its SPICE engine is very fast and powerful, it has become a popular SPICE simulator amongst hobbyists and design engineers who prefer to use free tools. Originally written for Windows, LTSpice has been tweaked to run under GNU/Linux using wine; I recommend using it if you need a robust, professional-quality SPICE simulator.</div>
+</li>
+<li class="level1"><div class="li"> <strong>Ngspice</strong>, which is the â??officialâ?? SPICE simulator of the gEDA suite. Ngspice is a revival of the SPICE 3 code for Linux. It provides a simulation engine, a command-line driven front-end, and the capability to plot simulation results graphically under the X Windows System. Ngspice is Linux-native and open-source. It is the SPICE of choice for those who want to do SPICE simulations easily on Linux, or want to hack and improve SPICEâ??s internals.</div>
+</li>
+<li class="level1"><div class="li"> <strong>Tclspice</strong>, is a fork off the ngspice development path. Tclspice is a superset of ngspice which (in theory) exports the SPICE command set to a TCL <acronym title="Application Programming Interface">API</acronym>, allowing you to embed SPICE analyses into a TCL program. This is useful for automating a design optimization, amongst other things. Tclspice is the simulator to use if you are interested in advanced, scripted design.</div>
+</li>
+</ul>
+
+<p>
+ There is also a <acronym title="GNU General Public License">GPL</acronym>â??ed simulator called <strong>gnucap</strong>, which is based upon (or is the descendant of) Alâ??s Circuit Simulator (<strong><code>ACS</code></strong>). I havenâ??t used it very much; information about gnucap is therefore TBD.
+</p>
+
+</div>
+<!-- SECTION "SPICE simulation" [36779-38431] -->
+<h3><a name="ltspice" id="ltspice">LTSpice</a></h3>
+<div class="level3">
+
+<p>
+LTSpice was written by Mike Englehardt and others at Linear Technologies, and is given away by LinearTech as a design aid for engineers wishing to simulate the performance of LinearTechâ??s switch mode power supply controllers. The package incorporates a schematic capture front end, fast and powerful SPICE engine, and the capability for plotting the results of many different types of SPICE analysis. Personally, I think the schematic capture front-end is hard to use and clunky; <strong>gschem</strong> knocks its socks off for ease of use and features. However, the SPICE engine and analysis stuff in LTSpice is simply great.
+</p>
+
+<p>
+LTSpice was originally developed to run under Windows, but Mike has tweaked it so that it runs fairly well on GNU/Linux under wine. (Only the help menu system is broken – the rest of the package runs well). Another good feature of LTSpice is that it is well supported – Mike reads the newsgroup <strong><code>sci.electronics.cad</code></strong> regularly and is generally happy to help people who experience problems with it. Therefore, despite its Windoze heritage, I recommend LTSpice as a powerful, professional-quality simulation and analysis back end for gEDA.
+</p>
+
+</div>
+
+<h4><a name="installation_and_configuration_of_ltspice" id="installation_and_configuration_of_ltspice">Installation and configuration of LTSpice</a></h4>
+<div class="level4">
+
+<p>
+To install and configure LTSpice, do the following:
+</p>
+<ol>
+<li class="level1"><div class="li"> Download and install wine. I have had success using Wine-20030219. Later versions probably also work.</div>
+</li>
+<li class="level1"><div class="li"> Download LTSpice. It is available under <a href="http://www.linear.com/software"; class="urlextern" title="http://www.linear.com/software"; rel="nofollow">http://www.linear.com/software</a> under the name SwitcherCAD-III.</div>
+</li>
+<li class="level1"><div class="li"> Run the LTSpice installer under wine.</div>
+</li>
+</ol>
+
+</div>
+
+<h4><a name="running_ltspice_with_geda_designs" id="running_ltspice_with_geda_designs">Running LTSpice with gEDA designs</a></h4>
+<div class="level4">
+
+<p>
+LTSpice can read a file holding a gEDA SPICE netlist. I have had success doing LTSpice simulations in the following way:
+</p>
+<ol>
+<li class="level1"><div class="li"> First of all, make sure that you are logged in as a normal user – Wine doesnâ??t like to run when invoked by root.</div>
+</li>
+<li class="level1"><div class="li"> Create a file in your project directory called â??Simulation.cmdâ??. In this file place your spice analysis commands (e.g. .OP, .AC, .DC, etc.)</div>
+</li>
+<li class="level1"><div class="li"> Place a SPICE include block into your schematic. For the file attribute, type in â??Simulation.cmdâ??.</div>
+</li>
+<li class="level1"><div class="li"> Netlist your design.</div>
+</li>
+<li class="level1"><div class="li"> Create a link from your netlist <strong><code>output.net</code></strong> and a netlist in the directory in which SwCADIII lives. Make the netlist suffix <strong><code>.cir</code></strong>. For example:<br/>
+ <br/>
+ ln -s ${DESIGN_HOME}/output.net ${WINE_HOME}/.wine/fake_windows/Program Files/LTC/SwCADIII/MyDesign.cir<br/>
+ <br/>
+</div>
+</li>
+<li class="level1"><div class="li"> Run LTSpice: cd into the directory where SwCADIII lives and say â??<strong><code>wine scad3.exe</code></strong>â??</div>
+</li>
+<li class="level1"><div class="li"> From the SwCADIII <acronym title="Graphical User Interface">GUI</acronym>, do: <strong><em>File</em></strong> → <strong><em>Open</em></strong> → <strong><em>(files of type netlist [.cir])</em></strong>, and select your file.</div>
+</li>
+<li class="level1"><div class="li"> Run the simulator by clicking on the run button, or doing: <strong><em>Simulate</em></strong> → <strong><em>Run</em></strong>.</div>
+</li>
+<li class="level1"><div class="li"> Select the variables to graph, and then click OK. SwCADIII does the rest of the work.</div>
+</li>
+</ol>
+
+<p>
+ Naturally, it is very important to play around with LTSpice to understand how to use it effectively, but the above description should suffice to get you started.
+</p>
+
+</div>
+<!-- SECTION "LTSpice" [38432-41371] -->
+<h3><a name="ngspice" id="ngspice">Ngspice</a></h3>
+<div class="level3">
+
+<p>
+Ngspice was started at the University of Rome â??La Sapienzaâ?? by Paolo Nenzi as an attempt to create a <acronym title="GNU General Public License">GPL</acronym>â??ed version of the standard Berkeley SPICE version 3 by re-writing the entire SPICE package. Plans were also laid to create better, more robust computational algorithms for the simulation engine. More information is available at the ngspice website: <a href="http://ngspice.sourceforge.net/"; class="urlextern" title="http://ngspice.sourceforge.net/"; rel="nofollow">http://ngspice.sourceforge.net/</a>. In light of his lofty plans, what Paolo did, however, was a little different: He took the SPICE 3 code which had been floating around the internet for many years, refactored it, and hacked the build system so that it would compile using the normal GNU make procedure. This was a major achievement for which Paolo deserves great praise. Unfortunately, from the look of the webpage, development on <strong>ngspice</strong> seems to have ceased at the end of 2001. Indeed, development did slow down considerably after 2001, but recently Paolo has been working on <strong>ngspice</strong> again. He released the latest version, <strong>ngspice-rework-15</strong>, in February 2004. This version is available only on the Sourceforge download page; Paolo hasnâ??t updated the rest of the projectâ??s website.
+</p>
+
+</div>
+
+<h4><a name="installation_and_configuration_of_ngspice" id="installation_and_configuration_of_ngspice">Installation and configuration of ngspice</a></h4>
+<div class="level4">
+
+<p>
+I generally find it best to download, configure, and compile the source of <strong>ngspice</strong> instead of trying to install a binary package. Thatâ??s the approach I outline here.
+</p>
+
+</div>
+
+<h4><a name="downloading_the_source_code" id="downloading_the_source_code">Downloading the source code</a></h4>
+<div class="level4">
+
+<p>
+Get the latest distribution from: <a href="http://sourceforge.net/projetcs/ngspice"; class="urlextern" title="http://sourceforge.net/projetcs/ngspice"; rel="nofollow">http://sourceforge.net/projetcs/ngspice</a>. Make sure that you get the latest version for best performance and the most features. As of May 2004, the latest release is <strong>ngspice-rework-15</strong>. Install the source in the place you typically put your sources. I like to keep my gEDA sources in a separate directory, for example <strong><code>/usr/local/geda/sources/ngspice</code></strong>. You might adopt a similar system.
+</p>
+
+</div>
+
+<h4><a name="extracting_the_source_code" id="extracting_the_source_code">Extracting the source code</a></h4>
+<div class="level4">
+
+<p>
+The source code you downloaded is distributed in a â??tarballâ??, a compressed archive. You have to extract archived files by doing:
+</p>
+<pre class="code">user@host:~$ cd <directory where you want to extract the source>
+user@host:~sources$ tar -xvzf </path/to/package.tar.gz>
+user@host:~sources$ cd <extracted dir></pre>
+
+<p>
+At this point you are in the top level directory of ngspice. Read the usual files, like <strong><code>README</code></strong>, and <strong><code>INSTALL</code></strong>, to learn about the simulator and the installation process. Reading <strong><code>NOTES</code></strong> file is also a good idea; it holds information valuable if you want to hack or debug features present in ngspice.
+</p>
+
+</div>
+
+<h4><a name="configuration_and_compilation_of_ngspice" id="configuration_and_compilation_of_ngspice">Configuration and compilation of ngspice.</a></h4>
+<div class="level4">
+
+<p>
+Ngspice uses the typical â??<strong><code>configure && make && make install</code></strong>â?? sequence used by other GNU software. There are numerous configure time options available for ngspice. A complete listing with attendant documentation is TBD; the best way to see them all is to look at <strong><code>configure.ac</code></strong> itself. Many of the configure time options pertain to debugging the simulator, or are to enable experimental analyses. For newbies, three configure time options are worth mentioning:
+</p>
+<ul>
+<li class="level1"><div class="li"> <strong><code>–enable-xspice</code></strong>: This flag compiles in support for XSpice extensions. These extensions allow you to define devices whose behavior is given by arbitrary â??code modelsâ??. Arguably, the most important code model is <strong><code>spice2poly</code></strong>, which is a model which translates SPICE2 style POLY constructs into an XSpice model usable by SPICE 3.</div>
+</li>
+<li class="level1"><div class="li"> <strong><code>–with-readline</code></strong>: This flag compiles GNU readline support into <strong>ngspice</strong>, which means that you can use emacs-style key commands, as well as the arrow keys to move around in the command line interface (CLI). Without this feature, the command line interface can be hostile, meaning that if you make a mistake in typing a long command, you have no choice but to type it all over again. Paolo discourages use of the readline feature because it mixes <acronym title="GNU General Public License">GPL</acronym> code (readline) with BSD code (<strong>ngspice</strong>), but he left the option open to other to decide for themselves how pure they wanted to be.</div>
+</li>
+<li class="level1"><div class="li"> <strong><code>–prefix</code></strong>: This flag point to the base directory where you want your binaries to be installed.</div>
+</li>
+</ul>
+
+<p>
+ Before you run configure, you should check the options you want to include, a brief description is given in appendix TBD. Once ready type:
+</p>
+<pre class="code">user@host:~sources/<tld>$./configure --enable-xspice --with-readline --prefix=/usr/local/geda <other configure options></pre>
+
+<p>
+Of course, â??<strong><code>–prefix=</code></strong>â?? should point to the place where you put <strong>your</strong> gEDA stuff. After issuing the command, your simulator is configured and ready to be compiled. Compilation is straightforward:
+</p>
+<pre class="code">user@host:~sources/<tld>$ make && make install</pre>
+
+<p>
+As always, you will probably need to be root in order to install the packages in a public directory, in such case you should do:
+</p>
+<pre class="code">user@host:~sources/<tld>$ make
+user@host:~sources/<tld>$ su -c make install</pre>
+
+</div>
+
+<h4><a name="testing_the_installation" id="testing_the_installation">Testing the installation</a></h4>
+<div class="level4">
+
+<p>
+At this point, you should be able to use ngspice. You can test your installation by trying one of the test circuits held in the tests directory. I recommend running the TransImpedanceAmp test, since it tests the SPICE2 POLY functionality.
+</p>
+
+</div>
+
+<h4><a name="using_ngspice" id="using_ngspice">Using ngspice</a></h4>
+<div class="level4">
+
+<p>
+Running ngspice is very simple. Just issue the command:
+</p>
+<pre class="code">user@host:~$ ngspice filename.net</pre>
+
+<p>
+at the unix command prompt, and ngspice will load the SPICE netlist called <strong><code>filename.net</code></strong> into its workspace, and leave you at an ngspice command prompt. You can run the simulator by saying â??runâ??. Your results will be stored in SPICE vectors for later printing or plotting. The command set available to you is documented at: <a href="http://newton.ex.ac.uk/teaching/CDHW/Electronics2/userguide/sec5.html#5"; class="urlextern" title="http://newton.ex.ac.uk/teaching/CDHW/Electronics2/userguide/sec5.html#5"; rel="nofollow">http://newton.ex.ac.uk/teaching/CDHW/Electronics2/userguide/sec5.html#5</a>
+</p>
+
+<p>
+To make use of the SPICE2 POLY codemodel, you need to load it into <strong>ngspice</strong> <strong><em class="u">before</em></strong> you load your netlist. (If you load it after loading your netlist, POLYs in your netlist are not translated, and therefore wonâ??t be simulated correctly.) To load the codemodel, just say:
+</p>
+<pre class="code">codemodel /usr/local/geda/lib/spice/spice2poly.cm</pre>
+
+<p>
+(or wherever you put your codemodels) at the ngspice prompt. Note that you must provide the <strong>absolute path</strong> to the location of the codemodel; ngspice isnâ??t smart enough to look for it in any default locations. (Also note that you should specify the location where <strong><code>spice2poly.cm</code></strong> lives on your machine; the path above is for mine).
+</p>
+
+<p>
+A better way to read in the <strong><code>spice2poly</code></strong> codemodel is to include it in the ngspice initialization file, <strong><code>spinit</code></strong>. The initialization file lives in the directory <strong><code>/usr/local/geda/share/ng-spice-rework/scripts</code></strong> (or where ever you placed your gEDA installation). Other ngspice customizations may also be placed into the <strong><code>spinit</code></strong> file.
+</p>
+
+</div>
+<!-- SECTION "Ngspice" [41372-48076] -->
+<h3><a name="tclspice" id="tclspice">Tclspice</a></h3>
+<div class="level3">
+
+<p>
+While the main branch of ngspice development hibernated in 2002, some friendly people at MultiGig Ltd. (<a href="http://www.multigig.com/"; class="urlextern" title="http://www.multigig.com/"; rel="nofollow">http://www.multigig.com/</a>) were busy developing a branch of ngspice which they called <strong>tclspice</strong>. Tclspice is a superset of ngspice in which much of the SPICE command set is exported as an <acronym title="Application Programming Interface">API</acronym> to TCL. The purpose of this is to facilitate scripting of SPICE analyses. This is a very powerful tool: With tclspice you can write a TCL script which runs a loop, tweaks component values, runs an analysis, and then evaluates the circuit performance with the tweaked components before looping again. Obviously, this ability can be used to perform automated, multi-dimensional circuit optimization. When complete, tclspice might possibly become a â??killer-appâ?? for open-source EDA.
+</p>
+
+</div>
+
+<h4><a name="downloading_installing_and_building_tclspice" id="downloading_installing_and_building_tclspice">Downloading, installing, and building tclspice</a></h4>
+<div class="level4">
+
+<p>
+Tclspiceâ??s project homepage is at: <a href="http://tclspice.sourceforge.net/"; class="urlextern" title="http://tclspice.sourceforge.net/"; rel="nofollow">http://tclspice.sourceforge.net/</a>. The tclspice source lives at <a href="http://sourceforge.net/projects/tclspice"; class="urlextern" title="http://sourceforge.net/projects/tclspice"; rel="nofollow">http://sourceforge.net/projects/tclspice</a>. Download and installation of tclspice follow the same steps as those detailed for ngspice above. Since tclspice is a superset of ngspice, you can install ngspice alone from the tclspice sources if desired. To build the entire package requires a couple of extra steps. Here, I present a series of steps which will build both ngspice (the stand-alone, CLI driven program) and the TCL <acronym title="Application Programming Interface">API</acronym> from the tclspice source.
+</p>
+
+<p>
+Before building tclspice, you need to have the following packages already installed:
+</p>
+<ul>
+<li class="level1"><div class="li"> TclX (tclx8.3.5 works for me.)</div>
+</li>
+<li class="level1"><div class="li"> tclreadline (tclreadline-2.1.0 works for me.)</div>
+</li>
+<li class="level1"><div class="li"> BLT for TCL (blt2.4z works for me.)</div>
+</li>
+<li class="level1"><div class="li"> TCL/Tk (8.4.3. works for me)</div>
+</li>
+</ul>
+
+<p>
+ If you donâ??t have these packages already on your Linux box, you need to get and build them. Note that building TclX requires having the sources for TCL and Tk, so you will also need to get those sources if you donâ??t have them installed already. I am running successfully with TCL/Tk 8.4.3, although 8.3.X versions are also supposed to work. Also, if you want to run spice in the background you need to recompile TCL and Tk to enable thread support if they havenâ??t got it enabled already (redhat packages havenâ??t).
+</p>
+
+<p>
+Assuming you have downloaded and installed the additional packages mentioned above, the following steps will build both ngspice and the TCL <acronym title="Application Programming Interface">API</acronym> on your machine:
+</p>
+<pre class="code">user@host:~sources/<tld>$ ./configure --enable-xspice --with-readline --prefix=/usr/local/geda
+user@host:~sources/<tld>$ make && make install (this makes and installs regular old ngspice)
+user@host:~sources/<tld>$ ./configure --enable-xspice --prefix=/usr/local/geda --enable-tcl --enable-experimental --disable-shared
+user@host:~sources/<tld>$ make tcl && make install-tcl</pre>
+
+<p>
+As always, you will probably need to be root in order to install the packages in a public directory, in such case you should do:
+</p>
+<pre class="code">user@host:~sources/<tld>$ su -c make install
+user@host:~sources/<tld>$ su -c make install-tcl</pre>
+
+<p>
+to install your packages. Now you will be ready to write TCL scripts which incorporate SPICE commands. Information about using tclspice is given below. Finally, if you are interested in hacking tclspice (or even if you are not), itâ??s a good idea to read the <strong><code>NOTES</code></strong> file living in the top source directory for a couple of useful pointers.
+</p>
+
+</div>
+
+<h4><a name="use_of_tclspice" id="use_of_tclspice">Use of tclspice</a></h4>
+<div class="level4">
+
+<p>
+Tclspice is designed to export SPICE commands to TCL programs. To use tclspice, you just need to say â??<strong><code>package require spice</code></strong>â?? at the beginning of your TCL program. Thereafter, to invoke a SPICE command, you just call it in the spice namespace. For example, the following TCL program will read in a SPICE netlist, command a transient analysis, run the simulation, and then plot the voltage observed over time on net Vout:
+</p>
+<pre class="code">#! tclsh
+package require spice
+spice::codemodel /usr/local/src/tclspice-0.2.12/src/xspice/icm/spice2poly.cm
+spice::source netlistname.cir
+spice::tran 0.1ns 40ns
+spice::run
+spice::plot Vout
+puts "All done now!"</pre>
+
+<p>
+Note that since tclspice doesnâ??t read the ngspice initialization file <strong><code>spinit</code></strong>, you will need to put any initialization commands directly into the TCL program. For example, in the above example we read the spice2poly codemodel directly into the workspace. Many other commands are also available; the entire tclspice commandset is documented at: <a href="http://tclspice.sourceforge.net/docs/tclspice_com.html"; class="urlextern" title="http://tclspice.sourceforge.net/docs/tclspice_com.html"; rel="nofollow">http://tclspice.sourceforge.net/docs/tclspice_com.html</a>
+</p>
+
+</div>
+
+<h4><a name="tclspice_problems" id="tclspice_problems">Tclspice problems</a></h4>
+<div class="level4">
+
+<p>
+A major problem with tclspice (which was inherited from ngspice) is that it leaks memory. Therefore, the time over which you may run a simulation is limited. This means that if you want to do an optimization by looping through a circuit many, many times, you may run out of memory before your program has completed its optimization. This is a known issue with tclspice, and efforts are underway to plug the leaks.
+</p>
+
+<p>
+Meanwhile, there are some workarounds which can be used on moderate-sized designs to facilitate long optimization runs. One method I have employed is to have the optimizer write its current state into a file after every circuit analysis, and read its starting state from the same file. The optimizer also stores the current list of best components in another file, and reads this file at the start of every run. Then, I have a TCL program called <strong><code>TaskMgr.tcl</code></strong> which runs in a loop; at each iteration of the loop it forks a child process to run the optimizer. Meanwhile, the parent process waits for 5 minutes (a heuristically determined time), and then issues a â??KILLâ?? signal to the child before looping and starting the optimizer again. This way, the optimizer never runs long enough to consume all the memory in my machine. The <strong><code>TaskMgr.tcl</code></strong> program is shown here:
+</p>
+<pre class="code">#! tclsh
+package require Tclx
+while {1} {
+ set PID [fork]
+ if {$PID} {
+ # Parent
+ after 300000
+ puts "About to kill child PID = $PID . . . ."
+ kill $PID
+ wait $PID
+ } else {
+ # Child
+ source Optimize.tcl
+ # If we ever get through this, we can print out the following:
+ error "We are done now!!!!!!"
+ }
+}</pre>
+
+<p>
+Note that <strong><code>TaskMgr.tcl</code></strong> needs the TclX package you already installed to run tclspice. Also, you may want to change the wait time to a different value depending upon the memory and speed of your machine. Finally, the parent has to wait on $PID because that causes the child processâ??s corpse to be taken off the Linux kernelâ??s task list when it dies. Otherwise, you will end up with a lot of zombie processes lurking around your machine as the optimizer runs – a long optimization could turn your system into â??the night of the living deadâ??!
+</p>
+
+<p>
+This method of waiting a specific amount of time for the child process is preferable if a single analysis run takes a relatively short time compared to the time required to eat all memory in the machine. If the analysis time is comparable to the time taken to eat all memory in the machine, a better approach is to have the parent keep track of the analysis state, kick off a single analysis run, and then have the run terminate after every iteration. Whether this is preferable depends upon the size and complexity of your design; you may want to experiment with your analysis to see just how long it takes and how much memory it consumes. I have found that a design comprised of six op amps (with corresponding vendor models) and 50 or so passives will run in under 10 seconds on a PIII 333MHz with 128MB RAM. Therefore, your design must be very big before a single analysis will eat a significant amount of RAM.
+</p>
+
+</div>
+<!-- SECTION "Tclspice" [48077-55608] -->
+<h1><a name="appendix_a" id="appendix_a">Appendix A</a></h1>
+<div class="level1">
+
+<p>
+<strong>Native components and their attributes</strong>
+</p>
+
+<p>
+Presented in table 1 are the devices and associated attributes used with spice-sdb. Bold faced attributes are required, normal typeface attributes are optional. Note that the <strong><code>device</code></strong> attribute is invisible, and is normally attached to the symbol when it is created. The other attributes are attached to the symbol during schematic capture using <strong>gschem</strong>.
+</p>
+
+<p>
+When dealing with simple actives (diodes, transistors) having SPICE models held in files, you only need to set the <strong><code>model-name</code></strong> and <strong><code>file</code></strong> attributes; you donâ??t need to set the <strong><code>model</code></strong> attribute. However, if your simple active has a one-line SPICE model which you wish to enter directly into the schematic, then set the <strong><code>model</code></strong> and <strong><code>model-name</code></strong> attribures; you donâ??t need to set the <strong><code>file</code></strong> attribute.
+</p>
+<table class="inline">
+ <tr>
+ <th>device</th><th>refdes</th><th>value</th><th>model</th><th>file</th><th>model-name</th><th>type</th><th>comment</th>
+ </tr>
+ <tr>
+ <td>RESISTOR</td><td class="centeralign"> R? </td><td class="centeralign"> (4) </td><td class="centeralign"> (2) </td><td class="centeralign"> - </td><td class="centeralign"> Name of model </td><td class="centeralign"> - </td><td class="centeralign"> (11) </td>
+ </tr>
+ <tr>
+ <td>CAPACITOR</td><td class="centeralign"> C? </td><td class="centeralign"> (4) </td><td class="centeralign"> (3) </td><td class="centeralign"> - </td><td class="centeralign"> Name of model </td><td class="centeralign"> - </td><td class="centeralign"> (11) </td>
+ </tr>
+ <tr>
+ <td>POLARIZED_CAPACITOR</td><td class="centeralign"> C? </td><td class="centeralign"> (4) </td><td class="centeralign"> (3) </td><td class="centeralign"> - </td><td class="centeralign"> Name of model </td><td class="centeralign"> - </td><td class="centeralign"> (11) </td>
+ </tr>
+ <tr>
+ <td>INDUCTOR</td><td class="centeralign"> L? </td><td class="centeralign"> (4) </td><td class="centeralign"> (3) </td><td class="centeralign"> - </td><td class="centeralign"> Name of model </td><td class="centeralign"> - </td><td class="centeralign"> (11) </td>
+ </tr>
+ <tr>
+ <td>SPICE-ccvs</td><td class="centeralign"> H? </td><td class="centeralign"> (5) </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td>SPICE-cccs</td><td class="centeralign"> F? </td><td class="centeralign"> (5) </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td>SPICE-vscs</td><td class="centeralign"> E? </td><td class="centeralign"> (5) </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td>SPICE-vccs</td><td class="centeralign"> G? </td><td class="centeralign"> (5) </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td>SPICE-nullor</td><td class="centeralign"> E? </td><td class="centeralign"> (5) </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td>DIODE</td><td class="centeralign"> D? </td><td class="centeralign"> Part number </td><td class="centeralign"> One line SPICE model </td><td class="centeralign"> Model file name </td><td class="centeralign"> Name of model </td><td class="centeralign"> - </td><td class="centeralign"> (12) </td>
+ </tr>
+ <tr>
+ <td>PMOS_TRANSISTOR</td><td class="centeralign"> M? </td><td class="centeralign"> Part number </td><td class="centeralign"> One line SPICE model </td><td class="centeralign"> Model file name </td><td class="centeralign"> Name of model </td><td class="centeralign"> - </td><td class="centeralign"> (12) </td>
+ </tr>
+ <tr>
+ <td>NMOS_TRANSISTOR</td><td class="centeralign"> M? </td><td class="centeralign"> Part number </td><td class="centeralign"> One line SPICE model </td><td class="centeralign"> Model file name </td><td class="centeralign"> Name of model </td><td class="centeralign"> - </td><td class="centeralign"> (12) </td>
+ </tr>
+ <tr>
+ <td>PNP_TRANSISTOR</td><td class="centeralign"> Q? </td><td class="centeralign"> Part number </td><td class="centeralign"> One line SPICE model </td><td class="centeralign"> Model file name </td><td class="centeralign"> Name of model </td><td class="centeralign"> - </td><td class="centeralign"> (12) </td>
+ </tr>
+ <tr>
+ <td>NPN_TRANSISTOR</td><td class="centeralign"> Q? </td><td class="centeralign"> Part number </td><td class="centeralign"> One line SPICE model </td><td class="centeralign"> Model file name </td><td class="centeralign"> Name of model </td><td class="centeralign"> - </td><td class="centeralign"> (12) </td>
+ </tr>
+ <tr>
+ <td>PFET_TRANSISTOR</td><td class="centeralign"> J? </td><td class="centeralign"> Part number </td><td class="centeralign"> One line SPICE model </td><td class="centeralign"> Model file name </td><td class="centeralign"> Name of model </td><td class="centeralign"> - </td><td class="centeralign"> (12) </td>
+ </tr>
+ <tr>
+ <td>NFET_TRANSISTOR</td><td class="centeralign"> J? </td><td class="centeralign"> Part number </td><td class="centeralign"> One line SPICE model </td><td class="centeralign"> Model file name </td><td class="centeralign"> Name of model </td><td class="centeralign"> - </td><td class="centeralign"> (12) </td>
+ </tr>
+ <tr>
+ <td>MESFET_TRANSISTOR</td><td class="centeralign"> B? </td><td class="centeralign"> Part number </td><td class="centeralign"> One line SPICE model </td><td class="centeralign"> Model file name </td><td class="centeralign"> Name of model </td><td class="centeralign"> - </td><td class="centeralign"> (12) </td>
+ </tr>
+ <tr>
+ <td>IC</td><td class="centeralign"> U? </td><td class="centeralign"> Part number </td><td class="rightalign"> </td><td class="centeralign"> .model file name </td><td class="centeralign"> Name of model </td><td class="centeralign"> - </td><td class="centeralign"> For IC with .model file </td>
+ </tr>
+ <tr>
+ <td>IC</td><td class="centeralign"> X? </td><td class="centeralign"> Part number </td><td class="rightalign"> </td><td class="centeralign"> .subckt file name </td><td class="centeralign"> Name of .subckt </td><td class="centeralign"> - </td><td class="centeralign"> For IC with .subckt file </td>
+ </tr>
+ <tr>
+ <td>model</td><td class="centeralign"> A? </td><td class="centeralign"> - </td><td class="centeralign"> One line SPICE model </td><td class="centeralign"> .model file name </td><td class="centeralign"> (9) </td><td class="centeralign"> (10) </td><td class="centeralign"> (12) </td>
+ </tr>
+ <tr>
+ <td>include</td><td class="centeralign"> A? </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="centeralign"> .include file name </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="centeralign"> (13) </td>
+ </tr>
+ <tr>
+ <td>options</td><td class="centeralign"> A? </td><td class="centeralign"> (8) </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="centeralign"> (13) </td>
+ </tr>
+ <tr>
+ <td>directive</td><td class="centeralign"> A? </td><td class="centeralign"> (1) </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="centeralign"> (12) </td>
+ </tr>
+ <tr>
+ <td>VOLTAGE_SOURCE</td><td class="centeralign"> V? </td><td class="centeralign"> (6) </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="centeralign"> Independent voltage source </td>
+ </tr>
+ <tr>
+ <td>CURRENT_SOURCE</td><td class="centeralign"> I? </td><td class="centeralign"> (7) </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="centeralign"> Independent current source </td>
+ </tr>
+</table>
+
+<p>
+ (1) One line string holding SPICE statements for inclusion in netlist<br/>
+ (2) One line of SPICE model parameters (e.g. TC, etc.)<br/>
+ (3) One line of SPICE model parameters (e.g. IC, POLY, etc.)<br/>
+ (4) Component numeric value<br/>
+ (5) String describing source behavior<br/>
+ (6) One line string holding voltage source behavior<br/>
+ (7) One line string holding current source behavior<br/>
+ (8) line of options to include<br/>
+ (9) Name of model pointed to by other components<br/>
+ (10) Corresponding SPICE model type (valid types given below)<br/>
+ (11) Model parameters are placed inside parentheses after component value<br/>
+ (12) For modeling, one must include either model or file<br/>
+ (13) Places .include directive in SPICE netlist<br/>
+
+</p>
+
+<p>
+â??Native to the netlisterâ?? means that there is a corresponding blob of scheme code which knows exactly how to handle these components and is guaranteed (almost) to generate correct spice code. Symbols having â??deviceâ?? attributes not on the above list are handled using the scheme function â??spice-sdb:write-default-componentâ??, which looks at the refdes of the component to make a decision about how to treat the component. In general, this function will â??do the right thingâ?? when generating spice code, but it is not guaranteed. In particular, this function cannot distinguish between N and P type transistors, and will generate an <unknown> type for the .MODEL string in the netlist. This will probably cause your SPICE simulator to barf. Therefore, it is best to make sure that all devices used have the proper â??deviceâ?? attribute.
+</p>
+
+</div>
+<!-- SECTION "Appendix A" [55609-60280] -->
+<h1><a name="appendix_b" id="appendix_b">Appendix B</a></h1>
+<div class="level1">
+
+<p>
+<strong>Valid â??typeâ?? values.</strong>
+</p>
+
+<p>
+The â??typeâ?? attribute is a flag signaling the spice engine the component type, and prepares it to accept model parameters specific to that component type. The following values are valid SPICE â??typeâ??s:
+</p>
+<table class="inline">
+ <tr>
+ <th class="centeralign"> Component </th><th class="centeralign"> â??typeâ?? </th><th class="centeralign"> Comment </th>
+ </tr>
+ <tr>
+ <td class="centeralign"> RESISTOR </td><td class="centeralign"> RES </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> CAPACITOR </td><td class="centeralign"> CAP </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> POLARIZED_CAPACITOR </td><td class="centeralign"> CAP </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> INDUCTOR </td><td class="centeralign"> IND </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> DIODE </td><td class="centeralign"> D </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> PMOS_TRANSISTOR </td><td class="centeralign"> PMOS </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> NMOS_TRANSISTOR </td><td class="centeralign"> NMOS </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> PNP_TRANSISTOR </td><td class="centeralign"> PNP </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> NPN_TRANSISTOR </td><td class="centeralign"> NPN </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> PFET_TRANSISTOR </td><td class="centeralign"> PJF </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> NFET_TRANSISTOR </td><td class="centeralign"> NJF </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> MESFET_TRANSISTOR </td><td class="centeralign"> - </td><td class="rightalign"> </td>
+ </tr>
+</table>
+
+<p>
+ Table 2: Valid â??typeâ?? attributes for components.
+</p>
+
+</div>
+<!-- SECTION "Appendix B" [60281-] --><div class="footnotes">
+<div class="fn"><a href="#fnt__1" id="fn__1" name="fn__1" class="fn_bot">1)</a>
+This HOWTO is released under the GNU Free Documentation License thanks to the generosity of Electroniscript, inc. The most recent copy can always be found at <a href="http://www.brorson.com/gEDA/HOWTO/"; class="urlextern" title="http://www.brorson.com/gEDA/HOWTO/"; rel="nofollow">http://www.brorson.com/gEDA/HOWTO/</a></div>
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-cygwin.html b/docs/wiki/geda-cygwin.html
new file mode 100644
index 0000000..60d2f33
--- /dev/null
+++ b/docs/wiki/geda-cygwin.html
@@ -0,0 +1,129 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="installing_geda_gaf_on_windows_-_the_cygwin_way" id="installing_geda_gaf_on_windows_-_the_cygwin_way">Installing gEDA/gaf on Windows - the Cygwin way</a></h1>
+<div class="level1">
+
+<p>
+ This guide describes one way to build gEDA/gaf (gschem and friends) on the Windows operating system. It uses Cygwin as the layer between Windows and the *nix world (ie gcc, make, bash etc…).
+</p>
+
+</div>
+<!-- SECTION "Installing gEDA/gaf on Windows - the Cygwin way" [1-258] -->
+<h2><a name="instructions" id="instructions">Instructions</a></h2>
+<div class="level2">
+
+<p>
+ <strong>1. Download and run setup.exe from cygwin website:</strong> <a href="http://www.cygwin.com"; class="urlextern" title="http://www.cygwin.com"; rel="nofollow">http://www.cygwin.com</a>.
+</p>
+
+<p>
+In the package selection dialog, select the following packages:
+</p>
+
+<p>
+(Hint: press the â??viewâ?? button once to arrange the list in alphabetical order)
+</p>
+<pre class="code">atk-devel
+crypt
+file
+gcc
+gtk2-x11-devel
+guile-devel
+libgmp-devel
+libtool1.5
+make
+pango-devel
+patchutils
+pcre-devel
+pcre-doc
+pkg-config
+xorg-x11-devel
+xorg-x11-fscl
+xterm</pre>
+
+<p>
+ <strong>2. Append these lines to your .bash_profile:</strong>
+</p>
+<pre class="code">export LD_LIBRARY_PATH=$HOME/geda/lib:$LD_LIBRARY_PATH
+export PATH=$HOME/geda/bin:$PATH
+export PKG_CONFIG_PATH=$HOME/geda/lib/pkgconfig:$PKG_CONFIG_PATH</pre>
+
+<p>
+ Update your environment:
+</p>
+<pre class="code">$ source .bash_profile</pre>
+
+<p>
+ <strong>3. Go to the <a href="http://www.geda.seul.org/sources.html"; class="urlextern" title="http://www.geda.seul.org/sources.html"; rel="nofollow">gEDA sources download page</a>.</strong>
+</p>
+
+<p>
+From the gEDA/gaf group, download <strong>only</strong> the packages which have a date as its version. The necessary dependencies were already installed in step 1. However, if you havenâ??t installed or built the libstroke package, be sure to add
+</p>
+<pre class="code">
+--disable-stroke
+</pre>
+
+<p>
+ to the opts= line. Add the following options to the opts= line in the Makefile
+</p>
+<pre class="code">
+--disable-update-mime-database --disable-update-desktop-database --disable-nls
+</pre>
+
+<p>
+<strong>4. Go to the download directory and type:</strong>
+</p>
+<pre class="code">$ make open
+$ make install
+( ...patience... )</pre>
+
+<p>
+ <strong>5. Now, to properly view the documentation from the help menu of gschem:</strong>
+</p>
+
+<p>
+Locate the executables of your browser and <acronym title="Portable Document Format">PDF</acronym> reader and create links from /usr/bin. Examples:
+</p>
+<pre class="code">$ ln -s "c:\Program Files\Internet Explorer\iexplore.exe" /usr/bin/iexplore
+$ ln -s "c:\Program Files\Firefox\firefox.exe" /usr/bin/firefox
+$ ln -s "c:\Program Files\Adobe\Acrobat 7.0\Reader\AcroRd32.exe" /usr/bin/acroread</pre>
+
+<p>
+ Try:
+</p>
+<pre class="code">$ iexplore
+( Microsoft Internet Explorer appears )
+$ firefox
+( Firefox appears - if installed )
+$ acroread
+( Adobe Acrobat Reader appears )
+$ gschemdoc -m
+( gEDA documentation appears )</pre>
+
+<p>
+ <strong>6. Finally, start the X server:</strong>
+</p>
+<pre class="code">$ startx</pre>
+
+<p>
+ Have fun!
+</p>
+
+</div>
+<!-- SECTION "Instructions" [259-] --></body>
+</html>
diff --git a/docs/wiki/geda-data_plotting_improvements.html b/docs/wiki/geda-data_plotting_improvements.html
new file mode 100644
index 0000000..329b69c
--- /dev/null
+++ b/docs/wiki/geda-data_plotting_improvements.html
@@ -0,0 +1,136 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#simulation_data_plotting" class="toc">Simulation Data Plotting</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#rationale" class="toc">Rationale</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#draft1extend_gtkwaves" class="toc">Draft1: Extend gtkwaves</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#draft2improve_gwave" class="toc">Draft2: improve gwave</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#draft3search_for_existing_data_exploring_programs" class="toc">Draft3: Search for existing data exploring programs</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#draft4a_new_plotting_application" class="toc">Draft4: A new plotting application</a></span></div></li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="simulation_data_plotting" id="simulation_data_plotting">Simulation Data Plotting</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "Simulation Data Plotting" [1-41] -->
+<h2><a name="rationale" id="rationale">Rationale</a></h2>
+<div class="level2">
+
+<p>
+This article discusses on how data plotting can be improved. There are various programs out there, each has itâ??s own pros and cons:
+</p>
+<ul>
+<li class="level1"><div class="li"> <a href="http://home.nc.rr.com/gtkwave/"; class="urlextern" title="http://home.nc.rr.com/gtkwave/"; rel="nofollow"> gtkwave</a>: a great viewer for digital simulation data</div>
+</li>
+<li class="level1"><div class="li"> <a href="http://www.telltronics.org/software/gwave/"; class="urlextern" title="http://www.telltronics.org/software/gwave/"; rel="nofollow"> gwave</a>: analog waveform viewer</div>
+</li>
+<li class="level1"><div class="li"> <a href="http://sourceforge.net/projects/kjwaves"; class="urlextern" title="http://sourceforge.net/projects/kjwaves"; rel="nofollow"> KJWaves</a>: simulation frontend with plotting window</div>
+</li>
+<li class="level1"><div class="li"> buildin plotting functions in ngspice</div>
+</li>
+<li class="level1"><div class="li"> gnuplot / octave / scipy / … or similar programs as postprocessing script languages</div>
+</li>
+<li class="level1"><div class="li"> …</div>
+</li>
+</ul>
+
+<p>
+ There have been various suggestions on the mailing lists about the feature a plotting program could have:
+</p>
+<ul>
+<li class="level1"><div class="li"> postprocessing: integrate, add, diff, fft, …</div>
+</li>
+<li class="level1"><div class="li"> view, examine: cursors, multiple windows, …</div>
+</li>
+<li class="level1"><div class="li"> data import, file format: circuit simulation data (gnucap, spice, …) <a href="http://www.hdfgroup.org/HDF5/"; class="urlextern" title="http://www.hdfgroup.org/HDF5/"; rel="nofollow"> hdf5 </a>, measured data from oscilloscopes, spectrum analysers, …</div>
+</li>
+<li class="level1"><div class="li"> data export, file format: hdf5, pictures (png, ps, …), ascii</div>
+</li>
+<li class="level1"><div class="li"> communication backends: dbus, …</div>
+</li>
+<li class="level1"><div class="li"> extension/scripting language</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Rationale" [42-1133] -->
+<h2><a name="draft1extend_gtkwaves" id="draft1extend_gtkwaves">Draft1: Extend gtkwaves</a></h2>
+<div class="level2">
+<ul>
+<li class="level1"><div class="li"> write some import functions for analog data</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Draft1: Extend gtkwaves" [1134-1219] -->
+<h2><a name="draft2improve_gwave" id="draft2improve_gwave">Draft2: improve gwave</a></h2>
+<div class="level2">
+
+<p>
+ gwave requires an old <a href="http://www.gnu.org/software/guile-gtk/"; class="urlextern" title="http://www.gnu.org/software/guile-gtk/"; rel="nofollow"> guile-gtk</a> for GTK1.2.
+</p>
+<ul>
+<li class="level1"><div class="li"> port gwave to guile-gtk2.0 for GTK2.x</div>
+</li>
+<li class="level1"><div class="li"> remove the guile-gtk requirement. Maybe create a native gtk2 application with libglade?</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Draft2: improve gwave" [1220-1479] -->
+<h2><a name="draft3search_for_existing_data_exploring_programs" id="draft3search_for_existing_data_exploring_programs">Draft3: Search for existing data exploring programs</a></h2>
+<div class="level2">
+
+<p>
+ Are there any programs out there that can show and postprocess simulation data? If yes, how can they be extended to work as a waveform viewer for the simulators (gnucap, ngspice)
+</p>
+
+</div>
+<!-- SECTION "Draft3: Search for existing data exploring programs" [1480-1724] -->
+<h2><a name="draft4a_new_plotting_application" id="draft4a_new_plotting_application">Draft4: A new plotting application</a></h2>
+<div class="level2">
+
+<p>
+ Some vague notes on how a new plotting application could be written. This notes currently relate on python as programming language.
+</p>
+<ul>
+<li class="level1"><div class="li"> the <acronym title="Graphical User Interface">GUI</acronym> could be created with <a href="http://www.jamesh.id.au/software/libglade/"; class="urlextern" title="http://www.jamesh.id.au/software/libglade/"; rel="nofollow">libglade</a></div>
+</li>
+<li class="level1"><div class="li"> the data storage format could be <a href="http://www.hdfgroup.org/HDF5/"; class="urlextern" title="http://www.hdfgroup.org/HDF5/"; rel="nofollow"> hdf5 </a>, maybe together with <a href="http://www.pytables.org/moin"; class="urlextern" title="http://www.pytables.org/moin"; rel="nofollow">pytables</a></div>
+</li>
+<li class="level1"><div class="li"> the plotting engine could be <a href="http://matplotlib.sourceforge.net/"; class="urlextern" title="http://matplotlib.sourceforge.net/"; rel="nofollow"> matplotlib</a> (png, ps export included)</div>
+</li>
+<li class="level1"><div class="li"> postprocessing could be done with <a href="http://www.scipy.org"; class="urlextern" title="http://www.scipy.org"; rel="nofollow"> scipy</a></div>
+</li>
+<li class="level1"><div class="li"> the scripting language is python. Thus import filter to hdf5 can easily be written. Even an integrated python shell would be possible. Seen on <a href="http://code.enthought.com/mayavi2-screenshot.shtml"; class="urlextern" title="http://code.enthought.com/mayavi2-screenshot.shtml"; rel="nofollow"> MayaVi 2</a></div>
+</li>
+</ul>
+
+<p>
+ Disadvantage: This configuration has a huge rucksack of additional required packages.
+</p>
+
+</div>
+<!-- SECTION "Draft4: A new plotting application" [1725-] --></body>
+</html>
diff --git a/docs/wiki/geda-data_structure_design_discussion.html b/docs/wiki/geda-data_structure_design_discussion.html
new file mode 100644
index 0000000..d639d15
--- /dev/null
+++ b/docs/wiki/geda-data_structure_design_discussion.html
@@ -0,0 +1,226 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#data_structure_design_discussion" class="toc">Data structure design discussion</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#concept_diagram" class="toc">Concept diagram</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#concepts_behind_the_structures" class="toc">Concepts behind the structures</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#design" class="toc">Design</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#circuit" class="toc">Circuit</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#mport" class="toc">MPort</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#instance" class="toc">Instance</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#attrib" class="toc">Attrib</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#netlist" class="toc">Netlist</a></span></div></li>
+<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="#page" class="toc">Page</a></span></div></li>
+</ul>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"><span class="li"><a href="#brainstorms" class="toc">Brainstorms</a></span></div></li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="data_structure_design_discussion" id="data_structure_design_discussion">Data structure design discussion</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "Data structure design discussion" [1-48] -->
+<h1><a name="concept_diagram" id="concept_diagram">Concept diagram</a></h1>
+<div class="level1">
+
+<p>
+ (Inspired by gnetman, by Bill Cox)
+</p>
+
+<p>
+<a href="./lib/exe/fetch.php?cache=cache&media=http%3A%2F%2Fwww2.eng.cam.ac.uk%2F%7Epcjc2%2Fgeda%2Fdatastructures.png" class="media" title="http://www2.eng.cam.ac.uk/~pcjc2/geda/datastructures.png";><img src="media/http///www2.eng.cam.ac.uk/~pcjc2/geda/datastructures.png" class="media" alt="" /></a>
+</p>
+
+</div>
+<!-- SECTION "Concept diagram" [49-178] -->
+<h2><a name="concepts_behind_the_structures" id="concepts_behind_the_structures">Concepts behind the structures</a></h2>
+<div class="level2">
+
+</div>
+<!-- SECTION "Concepts behind the structures" [179-222] -->
+<h3><a name="design" id="design">Design</a></h3>
+<div class="level3">
+
+<p>
+ This is might not exist as a â??fileâ??, as such, but exists as a data structure entity to be the owner of the circuits required in a particular design. The â??root circuitâ?? is the uppermost level of hierarchy.
+</p>
+
+</div>
+<!-- SECTION "Design" [223-446] -->
+<h3><a name="circuit" id="circuit">Circuit</a></h3>
+<div class="level3">
+
+<p>
+ A <strong>circuit</strong> entity is the key concept in this model. It defines an electrical block by a its external connections (<strong>MPort</strong>s). A schematic is one way of representing a circuit, hence a circuit object may own or more <strong>page</strong> of schematics.
+</p>
+
+<p>
+We may also define a <strong>symbolic</strong> (graphic) representation of a circuit - this is like a schematic <strong>page</strong>, however its representation should fit within a single sheet. The minimum a symbolic representation must contain is the <strong>pins</strong> which connect it to higher levels of circuit hierarchy.
+</p>
+
+</div>
+<!-- SECTION "Circuit" [447-1004] -->
+<h3><a name="mport" id="mport">MPort</a></h3>
+<div class="level3">
+
+<p>
+ If it is to be useful as a re-usable block, a sub-<strong>circuit</strong> must expose electrical connectivity for a parent <strong>circuit</strong> to connect with. Each such connection is represented by an <strong>Mport</strong> (Master port). This term (re-used from gnetman) represents the fact that once a circuit is instantiated, we need to differentiate between the connections of each specific instance. This is done with instance specific <strong>Port</strong> structures. The <strong>port</strong>s point back at the <strong>Mport</strong>s (master ports) of the circuit representation.
+</p>
+
+</div>
+<!-- SECTION "MPort" [1005-1541] -->
+<h3><a name="instance" id="instance">Instance</a></h3>
+<div class="level3">
+
+<p>
+ A <strong>circuit</strong> represents a re-usable electrical entity which we may replicate at various points in our design hierarchy. This is done by instantiating the sub-<strong>circuit </strong> in a higher level of hierarchy. Each instance is associated with an <strong>Instance</strong> structure, which is a placeholder for instance specific attributes such as the sub-circuitâ??s hierarchical refdes.
+</p>
+
+</div>
+<!-- SECTION "Instance" [1542-1929] -->
+<h3><a name="attrib" id="attrib">Attrib</a></h3>
+<div class="level3">
+
+<p>
+ An <strong>Attrib</strong> defines meta-data attached which might be attached to a <strong>circuit</strong>, a <strong>circuit</strong>â??s <strong>Mport</strong>, a specific <strong>circuit</strong> <strong>instance</strong>, or a <strong>Net</strong>.
+</p>
+
+<p>
+In a break from gEDAâ??s current <strong>attrib</strong> model, it makes sense to associate the meta-data directly with the particular entity it pertains to, rather than the graphic representation. This is because some forms of sub-<strong>circuit</strong> entity may be defined without a schematic, and could still require this meta-data. It will be possible to reference any <strong>attrib</strong> within the realm of a <strong>circuit</strong> for display on its schematic <strong>page</strong>(s) where that is desired.
+</p>
+
+</div>
+<!-- SECTION "Attrib" [1930-2569] -->
+<h3><a name="netlist" id="netlist">Netlist</a></h3>
+<div class="level3">
+
+<p>
+ A <strong>Netlist</strong> defines the electrical connectivity of a <strong>circuit</strong>. It owns a number of <strong>Net</strong>s, which individually represent a single connection between <strong>Mport</strong>s belonging to this <strong>circuit</strong>, and <strong>ports</strong> of instantiated sub-<strong>circuits</strong>.
+</p>
+
+<p>
+Initially, it is likely there will only be one netlist for a <strong>circuit</strong> - the one constructed from processing the electrically relevant objects on <strong>page</strong>(s) of the <strong>circuit</strong>â??s schematic.
+</p>
+
+<p>
+Future developments may see multiple netlists for a circuit, possibly some generated / written in an HDL language, and critically, re-exported from a layout package (e.g. PCB). It will be possible to identify and flag up differences in connectivity throughout a design flow, be that from HDL to schematic, or schematic to layout.
+</p>
+
+<p>
+This has real applications in back-annotation and in design verification.
+</p>
+
+</div>
+<!-- SECTION "Netlist" [2570-3435] -->
+<h3><a name="net" id="net">Net</a></h3>
+<div class="level3">
+
+<p>
+ A <strong>net</strong> associates with structures forming a given electrical connection within this <strong>circuit</strong>.
+</p>
+
+<p>
+As we also have a graphical representation of the wires (<strong>ConnSegment</strong>s) which make up this connection, each <strong>Net</strong> can be associated with multiple <strong>ConnSegment</strong>s. The association to <strong>Pins</strong> representing <strong>Mport</strong>s of this <strong>circuit</strong> and to the <strong>Pins</strong> of any instantiated sub-<strong>circuits</strong> is made via a <strong>net</strong>â??s association to the appropriate <strong>Mport</strong> and <strong>port</strong> structures.
+</p>
+
+</div>
+<!-- SECTION "Net" [3436-3940] -->
+<h3><a name="page" id="page">Page</a></h3>
+<div class="level3">
+
+<p>
+ A <strong>page</strong> is a canvas for placing graphical objects representing a circuit. A <strong>page</strong> can be used to draw an electrically meaningful schematic, or it can be used to draw a symbolic representation of the circuit entity.
+</p>
+
+<p>
+Whilst most objects on a <strong>page</strong> are graphic primitives, there are some which have a relation to the <strong>circuit</strong>â??s electrical specification.
+</p>
+<ul>
+<li class="level1"><div class="li"> <strong>ConnSegments</strong> (or <strong>net</strong>s) represent connected electrical signals within the circuit represented.</div>
+<ul>
+<li class="level2"><div class="li"> A connectivity representation (<strong>netlist</strong>) can be built by considering the end-point positioning of these objects.</div>
+</li>
+<li class="level2"><div class="li"> <strong>ConnSegment</strong> is intended to be a generalisation of <strong>net</strong>s and <strong>bus</strong>es for the purpose of this diagram.</div>
+</li>
+</ul>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> <strong>Pins</strong> represent a connection outside this circuit.</div>
+<ul>
+<li class="level2"><div class="li"> When constructing a netlist, coincidence of a <strong>ConnSegment</strong> end on these implies an electrical connection to that external port.</div>
+</li>
+<li class="level2"><div class="li"> Each <strong>pin</strong> (or group of pins?) represent an external electrical connection with this <strong>circuit</strong>.</div>
+</li>
+<li class="level2"><div class="li"> There is a necessary link between a <strong>pin</strong> and the circuitâ??s <strong>Mport</strong> which it represents.</div>
+</li>
+</ul>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> <strong>complex</strong> objects represent instantiating a sub-<strong>circuit</strong>, and will be linked to a specific <strong>instance</strong> structure.</div>
+<ul>
+<li class="level2"><div class="li"> Graphically, this means a <strong>symbolic</strong> representation of the instantiated circuit will be placed on the page.</div>
+</li>
+<li class="level2"><div class="li"> Nets ending co-incident with the <strong>pins</strong> of that embedded symbol represent electrical connectivity with the instantiated sub-<strong>circuit</strong> entity.</div>
+</li>
+</ul>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Page" [3941-5460] -->
+<h1><a name="brainstorms" id="brainstorms">Brainstorms</a></h1>
+<div class="level1">
+
+<p>
+ (from conversation on MSN/<acronym title="Internet Relay Chat">IRC</acronym> on 10th April 2007 – Peter Brett / Peter Clifton)
+</p>
+<ul>
+<li class="level1"><div class="li"> In order to do back annotation, need to be able to change the board part references for anywhere in the schematic. It then makes sense to dissociate the concepts of <strong>InstanceID</strong> and <strong>Board Reference</strong>, and use an <strong>override table</strong> that can override an attribute at any given path within the current <strong>circuit</strong> based on a path composed of <strong>InstanceID</strong>s. <strong>InstanceID</strong>s would be special-cased throughout libgeda as a means for uniquely identifying circuits and instances. An entry in the override table might have the form "/id1/id2/id3:refdes:U3â??</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> It might be useful to allow nets to have attributes, for instance to specify minimum copper width and spacing for a net, independently from the attributes of net segments.</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> The schematic editor needs to have sidebars for browsing hierarchy and inspecting attributes. This needs to include a way of seeing where the attributes have been inherited from.</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> We need to do lazy netlisting, on a circuit-by-circuit basis – the netlists should only be combined into a flat netlist when required by a tool (and even then, most tools can potentially make good use of hierarchy information).</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> In order to make finding objects by hierarchical path fast (e.g. to implement override tables discussed above) there needs to be a fast way of generating unique identifiers for objects (e.g. 32-bit ints) that can then be used as keys in hashtables.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Brainstorms" [5461-] --></body>
+</html>
diff --git a/docs/wiki/geda-debian.fr.html b/docs/wiki/geda-debian.fr.html
new file mode 100644
index 0000000..0679bda
--- /dev/null
+++ b/docs/wiki/geda-debian.fr.html
@@ -0,0 +1,46 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="notes_d_installation_debian_de_la_version_20060825" id="notes_d_installation_debian_de_la_version_20060825">Notes d'installation Debian de la version 20060825</a></h1>
+<div class="level1">
+
+<p>
+ Voici un rapport dâ??utilisateur qui fournit quelques éléments aux personnes installant avec le CDROM 20060825 sur une Debian. Notez que lâ??utilisateur avec pré-ajouté les paquets -dev sur son système au lieu de laisser lâ??installateur les trouver. Câ??est une manière parfaitement acceptable – et souvent préférable – de traiter les dépendances de gEDA.
+</p>
+<pre class="code">
+Just completed an install on my main desktop box which is Debian
+etch/testing with patches of sid/unstable.
+
+Lib packages I had to add to my system:
+ * libreadline5-dev
+ * libgd1-xpm-dev
+ * libwxgtk2.6-dev
+ * libgtk1.2-dev (compile failed because of missing gtk-config.
+ Configure did not seem to check for it.)
+ * I needed to install guile-1.6-dev rather than libguile-dev.
+ Else the installer fails to find scm_make_smob_type.
+
+On my system /usr/lib/libqthreads.so pointed to a non existing
+/usr/lib/libqthreads.so.12.3.1 This may be a bug in Debians packaging
+rules. Thus the installer failed with:
+ gcc: /usr/lib/libqthreads.so: No such file or directory make[2]:*** [libgeda.la] Error 1
+I resolved the issue by faking a link:
+ sudo ln -s libqthreads.so.12.3.0 libqthreads.so.12.3.1
+</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-debian.html b/docs/wiki/geda-debian.html
new file mode 100644
index 0000000..110b34c
--- /dev/null
+++ b/docs/wiki/geda-debian.html
@@ -0,0 +1,52 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="installer_20070221_on_debian_testing" id="installer_20070221_on_debian_testing">Installer 20070221 on Debian/testing</a></h1>
+<div class="level1">
+
+<p>
+The iso image contains binary packages to all the open source development utilities needed to build the geda suite. Nevertheless, it is advisable to stick with the native debian versions to avoid an inconsistent mix of packages. In april 2007 an install of the geda/gaf iso image 20070221 the following additional packages were necessary on a fresh debian/lenny box:
+</p>
+<ul>
+<li class="level1"><div class="li"> pkg-config</div>
+</li>
+<li class="level1"><div class="li"> libreadline5-dev</div>
+</li>
+<li class="level1"><div class="li"> libgd2</div>
+</li>
+<li class="level1"><div class="li"> libgd2-dev</div>
+</li>
+<li class="level1"><div class="li"> guile1.6-dev</div>
+</li>
+<li class="level1"><div class="li"> libwxgtk2.6-dev</div>
+</li>
+<li class="level1"><div class="li"> libgtk2.0-dev</div>
+</li>
+<li class="level1"><div class="li"> flex</div>
+</li>
+<li class="level1"><div class="li"> bison</div>
+</li>
+<li class="level1"><div class="li"> g++</div>
+</li>
+</ul>
+
+<p>
+The debian package manager will expand this list significantly as required by the debian database of dependencies.
+</p>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-design_flow_and_hierarchy_roadmap.html b/docs/wiki/geda-design_flow_and_hierarchy_roadmap.html
new file mode 100644
index 0000000..261d0da
--- /dev/null
+++ b/docs/wiki/geda-design_flow_and_hierarchy_roadmap.html
@@ -0,0 +1,259 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#required_for_production_circuits" class="toc">Required for production circuits</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#intermediate_translation_file_format_vhdl_edif" class="toc">intermediate translation file format VHDL? EDIF?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#hierarchical_buses" class="toc">Hierarchical Buses</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#ipc_improvements" class="toc">IPC Improvements</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#robust_function" class="toc">Robust Function</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#other_improvements" class="toc">Other Improvements</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#too_detailed" class="toc">Too Detailed</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#implementation" class="toc">Implementation</a></span></div></li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="required_for_production_circuits" id="required_for_production_circuits">Required for production circuits</a></h1>
+<div class="level1">
+<ul>
+<li class="level1"><div class="li"> hierarchy in schematic and netlist and pcb – modules that can be reused, arrayed.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Required for production circuits" [1-135] -->
+<h2><a name="intermediate_translation_file_format_vhdl_edif" id="intermediate_translation_file_format_vhdl_edif">intermediate translation file format VHDL? EDIF?</a></h2>
+<div class="level2">
+
+</div>
+
+<h4><a name="schematic_layout_logic_sim_analog_sim_etc" id="schematic_layout_logic_sim_analog_sim_etc">Schematic, Layout, logic sim, analog sim, etc</a></h4>
+<div class="level4">
+
+<p>
+ In an *AMS language, nets have types. Itâ??s not just â??wireâ??. The schematic needs to be extended so that pins on symbols can have types. It is not prohibited to mix types. Verilog has something called a â??connectmoduleâ?? to define how to resolve mixed types. <strong>gschem attributes need to have types.</strong> [Al Davis]
+</p>
+
+<p>
+ I certainly agree that the (gnetlist-ed.) Verilog output is not â??losslessâ?? – itâ??s only an interchange format for the interconnect…[Mike Jarabek]
+</p>
+
+<p>
+ Heâ??s not actually proposing to use VHDL (as modeling language-ed.) but to steal some <strong>syntax from VHDL</strong> and interpret it as he sees fit for the task. In particular, heâ??s only interested in the <strong>entity-architecture separation</strong>[Steve Williams]
+</p>
+
+<p>
+More useful, (than creating intermediate file formats-ed.) is to <strong>refactor libgeda and define an <acronym title="Application Programming Interface">API</acronym></strong> which can be exposed via C, scheme, DBus, and other scripting languages directly modifying the underlying design. [Peter Clifton]
+</p>
+
+<p>
+ Any extraction should preserve hierarchy, in hopes that the target tool also benefits from it. Translation must be 100%, lossless, from netlist to PCB refdes, and from PCB refdes used to create a module or back annotate a schematic. [Al Davis] [paraphrased heavily by JGriessen – correct?]
+</p>
+
+<p>
+ The <strong>file format should be designed as a language</strong> meaningful and expressive of IC, programmable logic, and printed circuits. File formats that are data structure dumps cause big problems. We need an interchange file format..[Al Davis]
+</p>
+
+<p>
+ If EDIF has layout objects or schematic objects built-in, that is actually a weakness. Just like SPICE having resistors and transistors built-in has become a weakness.[Al Davis]
+</p>
+
+<p>
+ <strong>EDIFâ??s not mainstream.</strong> VHDL and Verilog are mainstream. That is one reason for my preference. Itâ??s not all technical[Al Davis]
+</p>
+
+<p>
+ <strong>PCB behavior with a hierarchic netlist</strong> Right click on a symbol, select â??go insideâ??, and another drawing opens up showing whatâ??s inside. gschem also should act this way. [Al Davis] Display in place whatâ??s inside, <strong>turn on/off the visibility</strong> or â??editabilityâ?? of any subcells. [Igor] <strong>Ability to visually toggle</strong> [Dan McMahill] <strong>â??blocksâ?? should be translucent.</strong> (To show in place)ed. even when youâ??re not editing it. [DJ Delorie] Yep. [John Griessen] Dive into a block so you can edit it. When done, <strong>close and updated in place</strong>. [DJ Delorie]
+</p>
+
+<p>
+<strong>how to handle re-use blocks?</strong> [Stuart Brorson] That is, if I have a sub-schematic which I instantiate four times, how should it be refdesed in the netlist?
+</p>
+
+</div>
+<!-- SECTION "intermediate translation file format VHDL? EDIF?" [136-2788] -->
+<h2><a name="hierarchical_buses" id="hierarchical_buses">Hierarchical Buses</a></h2>
+<div class="level2">
+
+</div>
+<!-- SECTION "Hierarchical Buses" [2789-2821] -->
+<h2><a name="ipc_improvements" id="ipc_improvements">IPC Improvements</a></h2>
+<div class="level2">
+
+<p>
+ (InterProcess Communication -ed.) between gschem and PCB using DBus will benefit from netlisting changes (certainly cross probing and back annotation).[Peter Clifton]
+</p>
+
+<p>
+ Peter Brett and I put together a graphical frontend to gsch2pcb which uses gsch2pcbâ??s output to feed changes into a live PCB layout. [Peter Clifton]
+</p>
+
+<p>
+ For <strong>cross-probing</strong> / interactive simulation / back annotation, we require libgeda to <strong>give gschem, gattrib etc.. the circuit representation</strong> underlying your schematic drawing.[Peter Clifton]
+</p>
+
+</div>
+<!-- SECTION "IPC Improvements" [2822-3368] -->
+<h2><a name="robust_function" id="robust_function">Robust Function</a></h2>
+<div class="level2">
+
+<p>
+ libgeda could/should evolve - as a backend to different tools. Since the PCB file-format is PCBâ??s, and may change, it is wiser to use a defined <acronym title="Application Programming Interface">API</acronym> to PCB to make PCB write the file. This entails adding to PCBâ??s action interface as necessary, and making gsch2pcb output a script of actions rather than a â??PCBâ?? file. [Peter Clifton]
+</p>
+
+<p>
+ Iâ??m hoping to separate much of the <acronym title="Graphical User Interface">GUI</acronym> structure and cram that back in the applications it belongs in, re-structuring libgeda to be design data-oriented.[Peter Clifton]
+</p>
+
+<p>
+<strong>function library with bindings to users language of choice</strong> a proper, â??officialâ?? <acronym title="Practical Extraction and Report Language">Perl</acronym>-callable library to parse a layout file, a footprint file, or a schematic file, and load the data into an in-memory data structure. Such a library to read and write these file formats would dramatically reduce the activation energy hump to write a rich set of tools for all of us. [CP Tarun]
+</p>
+
+<p>
+ It would not fall out of sync with the changing file-formats, because you wouldnâ??t write yet another implementation of the parser, data-structures etc, nor would you copy-paste code. You would have one library which is used by all tools (probably in C as this is what the suite mostly uses), then you would provide language bindings so people can write the useful utilities they want. If this means having to split code out of existing tools and into a library, that is the way forward in terms of code reuse. [Peter Clifton]
+</p>
+
+<p>
+ I completely agree. [Dan McMahill]
+</p>
+
+<p>
+ Also consider libgpmi which currently supports 8 languages, will support guile [Igor]
+</p>
+
+</div>
+<!-- SECTION "Robust Function" [3369-4944] -->
+<h2><a name="other_improvements" id="other_improvements">Other Improvements</a></h2>
+<div class="level2">
+
+<p>
+It is very useful I think to let DRC run to completion and <strong>have a DRC layer</strong> (or perhaps 1 DRC layer per copper layer as you suggest) that identifies exactly the <strong>offending feature</strong>.[Dan McMahill]
+</p>
+
+<p>
+<strong>layout and save a hierarchy module</strong> [Steve Meier]
+</p>
+
+<p>
+ have a block (in PCB)ed. that is a modular entity. Normally, you canâ??t do anything but move it around as a whole. A special action â??opensâ?? this block (and hides everything else) so you can edit it. When youâ??re done, itâ??s closed again - and any copies of the block are automatically updated in place. [DJ Delorie]
+</p>
+
+<p>
+<strong>be able in the netlist to tell pcb which slots are swapable</strong>, which i/o pins are swapable and which pin pairs can function as differential pairs (these last two have to be able to be limited to specific banks) such that pcb could correctly change the net list itself. Then I would like PCB to be able to tell me what pins and in what order the pins were swapped so that this could be imported back into the original design.[Steve Meier]
+</p>
+
+<p>
+ <strong>gschem attribute editable as symbols placed</strong>, (such as description of the layout footprint attribute) [CP Tarun]
+</p>
+
+<p>
+<strong> recesses in boards, (holes in PCB layers)</strong>[Steve Meier] Required for straight leads out side of packages and flex circuits.
+</p>
+
+<p>
+ Yeah, youâ??d need the â??layer typesâ?? patch to really manage that, as youâ??d be able to tag multiple pcb layers as â??outlineâ?? layers[DJ Delorie]
+</p>
+
+<p>
+<strong> PCB should be able to do hidden vias</strong>, buried vias and micro vias. [Steve Meier]
+</p>
+
+<p>
+ Answered by non-copper layers, multi-pin projects in SoC list [DJ Delorie]
+</p>
+
+<p>
+ Use padstack to build elements with copper and non-copper layers independent.[Levente]
+</p>
+
+<p>
+ <strong>a PCB interface for presenting dynamic dialog boxes</strong> for importers [Igor] I think this is part of having easy scripting of userâ??s choice, so an important design flow consideration[John Griessen]
+</p>
+
+</div>
+<!-- SECTION "Other Improvements" [4945-6847] -->
+<h2><a name="too_detailed" id="too_detailed">Too Detailed</a></h2>
+<div class="level2">
+
+<p>
+<strong>change only the top of hierarchy string</strong> of a layout module to netlist correctly.[Steve Meier]
+</p>
+
+<p>
+<strong>Separate the hierarchy</strong> from the rest of the refdes. [Steve Meier]
+</p>
+
+<p>
+ PCB doesnâ??t care what the refdes is, a heirarchical one is just as valid [DJ Delorie]
+</p>
+
+<p>
+<strong>In gschem, visually browse the symbol library</strong>.[CP Tarun]
+</p>
+
+<p>
+ Can be putoff and done as a <acronym title="Graphical User Interface">GUI</acronym> plugin script – a detail of easy scripting wants [JGriessen]
+</p>
+
+<p>
+<strong>In gschem, more control over printed or exporting</strong>, as in CAM files a la Eagle.[CP Tarun]
+</p>
+
+<p>
+ Can be putoff and done as a <acronym title="Graphical User Interface">GUI</acronym> plugin script – a detail of easy scripting wants [JGriessen]
+</p>
+
+</div>
+<!-- SECTION "Too Detailed" [6848-7493] -->
+<h2><a name="implementation" id="implementation">Implementation</a></h2>
+<div class="level2">
+
+<p>
+ <strong>What kind of data structures are desirable?</strong> How would they look? [Stuart Brorson] <strong>Once a datastructure is decided upon, then what does the file format look like?</strong> Preserving the current close mapping of files to data structures is a desirable goal. The data structures defining hierarchy dictate what the file format should look like. [Stuart Brorson]
+</p>
+
+<p>
+ Right now, the main data structure for a schematic is a linear linked list of graphical objects (for each schematic page). Some list items point to others (i.e. to support component attributes). How would that change to support hierarchy? [Stuart Brorson]
+</p>
+
+<p>
+ PCB has a second format it uses called a â??resource fileâ??. Itâ??s a semi-lisp-ish format that allows for arbitrarily nested data. It could be used to hold pretty much anything, but it isnâ??t â??designed for the dataâ??.[DJ Delorie]
+</p>
+
+<p>
+<strong>How should gschem behave once hierarchy is architected in?</strong> Right now you attach a source= attribute to a symbol. Then you do â??schematic downâ?? on that symbol to dive into the sub-schematic. Is that OK? Or whatâ??s a better scheme?
+</p>
+
+<p>
+<strong>Some work has already been done using gnetman by Bill Cox,</strong> but it has never been part of the distribution gnetlist. Dan McMahill wrote: â??a reason to use the gnetman database as opposed to one designed by one of usâ?? is that without availing Bill Coxâ??s substantial tested work, we may â??find that the underlying database structure and methods for accessing it still arenâ??t complete enough, fast enough, or scalable enough."
+</p>
+
+<p>
+<strong>Some work has already been done by Steve Meier</strong> to enable practical work on FPGAs.
+</p>
+
+<p>
+<strong>Some design work has been done by Peter Brett and Peter Clifton,</strong> producing a concept diagram of a sub-circuit oriented data-structure based on gnetmanâ??s structure diagram for netlisting. See <a href="geda-data_structure_design_discussion.html" class="wikilink1" title="geda-data_structure_design_discussion.html">data structure design discussion</a>
+</p>
+
+</div>
+<!-- SECTION "Implementation" [7494-] --></body>
+</html>
diff --git a/docs/wiki/geda-design_flow_roadmap.html b/docs/wiki/geda-design_flow_roadmap.html
new file mode 100644
index 0000000..45f3a9a
--- /dev/null
+++ b/docs/wiki/geda-design_flow_roadmap.html
@@ -0,0 +1,26 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h2><a name="page_moved" id="page_moved">Page moved</a></h2>
+<div class="level2">
+
+<p>
+ This page has moved to <a href="geda-design_flow_and_hierarchy_roadmap.html" class="wikilink1" title="geda-design_flow_and_hierarchy_roadmap.html">design_flow_and_hierarchy_roadmap</a>.
+</p>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-devel-tips.html b/docs/wiki/geda-devel-tips.html
new file mode 100644
index 0000000..519e21d
--- /dev/null
+++ b/docs/wiki/geda-devel-tips.html
@@ -0,0 +1,717 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#geda_developer_tips_tricks_and_hints" class="toc">gEDA Developer Tips, tricks and hints</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#data_structure_of_a_schematic" class="toc">Data Structure of a Schematic</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#doxygen_comments_and_styles" class="toc">Doxygen Comments and styles</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#documenting_files" class="toc">Documenting Files</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#documenting_variables_defines_typedefs" class="toc">Documenting Variables/Defines/Typedefs</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#documenting_functions" class="toc">Documenting Functions</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#structure_documentation" class="toc">Structure Documentation</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#bug_todo_commands" class="toc">Bug/Todo Commands</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#dialogsdesign_and_behaviour" class="toc">Dialogs: Design and Behaviour</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#dialog_design" class="toc">Dialog Design</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#modal_or_nonmodal_dialogs" class="toc">Modal or Nonmodal dialogs</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#where_to_place_the_dialog" class="toc">Where to place the dialog</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#placing_dialogs_in_front_of_their_parent_window" class="toc">Placing dialogs in front of their parent window</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#button_order_in_dialogs" class="toc">Button order in dialogs</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#dialog_design_of_the_current_dialogs" class="toc">Dialog design of the current dialogs</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#source_template_for_simple_dialogs" class="toc">Source template for simple dialogs</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#current_dialog_issues_in_gschem" class="toc">Current Dialog Issues in Gschem</a></span></div></li></ul>
+</li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="geda_developer_tips_tricks_and_hints" id="geda_developer_tips_tricks_and_hints">gEDA Developer Tips, tricks and hints</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "gEDA Developer Tips, tricks and hints" [1-54] -->
+<h2><a name="data_structure_of_a_schematic" id="data_structure_of_a_schematic">Data Structure of a Schematic</a></h2>
+<div class="level2">
+
+<p>
+Internally, a schematic in gaf is implemented by number of doubly linked lists. The central type linked in the lists is OBJECT. It can represent a symbol, a line of text, a drawing primitive, a net, or an attribute.
+</p>
+
+<p>
+An overview of the data structure of a schematic can be retrieved <a href="http://www.brorson.com/gEDA/gEDA_Structures_20050108.pdf"; class="urlextern" title="http://www.brorson.com/gEDA/gEDA_Structures_20050108.pdf"; rel="nofollow">here</a>. The sketch was drawn in 2005 by Stuart Brorson.
+</p>
+
+</div>
+<!-- SECTION "Data Structure of a Schematic" [55-503] -->
+<h2><a name="doxygen_comments_and_styles" id="doxygen_comments_and_styles">Doxygen Comments and styles</a></h2>
+<div class="level2">
+
+<p>
+ <strong>Doxygen</strong> is a tool which extracts <acronym title="Application Programming Interface">API</acronym> documentation from comments in the source code. Markup can be placed in the comments, which is then extracted and rendered to <acronym title="HyperText Markup Language">HTML</acronym> or LaTeX by Doxygen. This allows e.g. one function to link to another related function, and permits arguments and return values to have documentation associated with them.
+</p>
+
+<p>
+Some sections of the gaf source have already been doxyfied. Currently, this includes libgeda and gattrib. The Makefile in the doc dir of these tools contains a target â??doxygenâ??. Alternatively, you can browse the output of doxygen online <a href="http://www.xs4all.nl/~ljh4timm/gaf/dox.html"; class="urlextern" title="http://www.xs4all.nl/~ljh4timm/gaf/dox.html"; rel="nofollow">on this site</a>, made available by Bert Timmerman.
+</p>
+
+<p>
+If you want to see Doxygenâ??s ideas on how to format documentation see the <a href="http://www.stack.nl/~dimitri/doxygen/docblocks.html"; class="urlextern" title="http://www.stack.nl/~dimitri/doxygen/docblocks.html"; rel="nofollow">Doxygen website</a>. The individual commands are documented <a href="http://www.stack.nl/~dimitri/doxygen/commands.html"; class="urlextern" title="http://www.stack.nl/~dimitri/doxygen/commands.html"; rel="nofollow">here</a>. There is also a very handy Doxygen <a href="http://www.digilife.be/quickreferences/QRC/Doxygen%20Quick%20Reference.pdf"; class="urlextern" title="http://www.digilife.be/quickreferences/QRC/Doxygen%20Quick%20Reference.pdf"; rel="nofollow">quick reference card</a>.
+</p>
+
+<p>
+The following sections provide an introduction on how gschem and libgeda are customarily documented. Note that the QT style of <strong>/*! comment goes here */</strong> for a Doxygen-enabled comment is preferred.
+</p>
+
+</div>
+<!-- SECTION "Doxygen Comments and styles" [504-1809] -->
+<h3><a name="documenting_files" id="documenting_files">Documenting Files</a></h3>
+<div class="level3">
+
+<p>
+ When starting a new file, you obviously need to have the normal GNU license text. After the GNU License you should include a file comment describing what the file is for and any other descriptions that apply to the whole file.
+</p>
+<pre class="code">/*! \file <filename.ext>
+ \brief Put a brief summary of what this file is for...
+ \par Description
+ A lengthier description of what the file is for (this is optional).
+ */</pre>
+
+</div>
+<!-- SECTION "Documenting Files" [1810-2259] -->
+<h3><a name="documenting_variables_defines_typedefs" id="documenting_variables_defines_typedefs">Documenting Variables/Defines/Typedefs</a></h3>
+<div class="level3">
+
+<p>
+ Global variables in a file can be documented using the <strong>\var</strong> command or by just writing a comment with a <strong>\brief</strong> command right before the definition.
+</p>
+<pre class="code">/*! \brief fill style of objects like cirle, rect, path */
+typedef enum {FILLING_HOLLOW, FILLING_FILL, FILLING_MESH, FILLING_HATCH, FILLING_VOID} OBJECT_FILLING;</pre>
+
+</div>
+<!-- SECTION "Documenting Variables/Defines/Typedefs" [2260-2633] -->
+<h3><a name="documenting_functions" id="documenting_functions">Documenting Functions</a></h3>
+<div class="level3">
+
+<p>
+ Functions can be documented in the same way as Variables, etc… Just use a comment block above the function it is documenting and use a <strong>\brief</strong> command to start it.
+</p>
+
+<p>
+Usually an additional <strong>Function Description</strong> paragraph is used for the lengthy description of the functionâ??s purpose. Also <strong>\param</strong> commands are used with the [in] or [out] attributes to document if the parameter will be modified by the function.
+</p>
+<pre class="code">/*! \brief "Save" a file into a string buffer
+ * \par Function Description
+ * This function saves a whole schematic into a buffer in libgeda
+ * format. The buffer should be freed when no longer needed.
+ *
+ * \param [in] toplevel The current TOPLEVEL.
+ * \param [in] object_list The head of a GList of OBJECTs to save.
+ * \return a buffer containing schematic data or NULL on failure.
+ */</pre>
+
+</div>
+<!-- SECTION "Documenting Functions" [2634-3504] -->
+<h3><a name="structure_documentation" id="structure_documentation">Structure Documentation</a></h3>
+<div class="level3">
+
+<p>
+ Structures are documented the same as in the previous sections. Note that comments on the structure members can be documented inline or using the same <strong>\brief</strong> syntax as variables. Inline documentation requires the special comment starting with <strong>/*!<</strong> at the end of the line it applies to.
+</p>
+<pre class="code">/*! \brief Structure for connections between OBJECTs
+ *
+ * The st_conn structure contains a single connection
+ * to another object.
+ * The connection system in s_conn.c uses this struct
+ */
+struct st_conn {
+ OBJECT *other_object; /*!< The "other" object connected to this one */
+ /*! \brief type of connection. Always in reference to how the "other"
+ object is connected to the current one */
+ int type;
+ int x; /*!< x coord of the connection position */
+ int y; /*!< y coord of the connection position */
+ int whichone; /*!< which endpoint of the current object caused this connection */
+ int other_whichone; /*!< which endpoint of the "other" object caused this connection */
+};</pre>
+
+</div>
+<!-- SECTION "Structure Documentation" [3505-4565] -->
+<h3><a name="bug_todo_commands" id="bug_todo_commands">Bug/Todo Commands</a></h3>
+<div class="level3">
+
+<p>
+ <strong>\bug</strong> and <strong>\todo</strong> are useful for notating where there are defects or missing features in the code. These commands can be used anywhere within the Doxygen comments, and generate entries on special pages in the documentation so that they can easily be referred to.
+</p>
+
+</div>
+<!-- SECTION "Bug/Todo Commands" [4566-4863] -->
+<h2><a name="dialogsdesign_and_behaviour" id="dialogsdesign_and_behaviour">Dialogs: Design and Behaviour</a></h2>
+<div class="level2">
+
+</div>
+<!-- SECTION "Dialogs: Design and Behaviour" [4864-4907] -->
+<h3><a name="dialog_design" id="dialog_design">Dialog Design</a></h3>
+<div class="level3">
+
+<p>
+Thereâ??s a nice document from the gnome guys called <a href="http://developer.gnome.org/projects/gup/hig/2.0/"; class="urlextern" title="http://developer.gnome.org/projects/gup/hig/2.0/"; rel="nofollow"> Gnome HIG</a>. There are several suggestions on how to design dialogs and how they should behave.
+</p>
+
+<p>
+<strong> The dialog design is mostly a matter of taste:</strong>
+</p>
+<ul>
+<li class="level1"><div class="li"> alignment of elements. See <a href="http://developer.gnome.org/projects/gup/hig/2.0/design-window.html"; class="urlextern" title="http://developer.gnome.org/projects/gup/hig/2.0/design-window.html"; rel="nofollow"> Window Layout</a></div>
+</li>
+<li class="level1"><div class="li"> right alignment of dialog buttons</div>
+</li>
+<li class="level1"><div class="li"> some spacing around the dialog (but how much?)</div>
+</li>
+<li class="level1"><div class="li"> some spacing between the elements (vertical and horizontal)</div>
+</li>
+<li class="level1"><div class="li"> option groups with frames or indentation?</div>
+</li>
+<li class="level1"><div class="li"> frame labels or bold headlines?</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Dialog Design" [4908-5538] -->
+<h3><a name="modal_or_nonmodal_dialogs" id="modal_or_nonmodal_dialogs">Modal or Nonmodal dialogs</a></h3>
+<div class="level3">
+
+<p>
+A modal dialog is required whenever the main application provides data for the dialog.
+</p>
+<pre class="code">Example:
+ The dialog is called with a selection list and the dialog only should operate on this selection.</pre>
+
+<p>
+ A modal dialog is OK too, if the dialog is only called very seldom. The file open dialog could be nonmodal because it does not require any input from the application.
+</p>
+
+<p>
+A modal dialog is not OK if there is a lot of user interaction with the dialog. The component selection is a good example.
+</p>
+
+</div>
+<!-- SECTION "Modal or Nonmodal dialogs" [5539-6069] -->
+<h3><a name="where_to_place_the_dialog" id="where_to_place_the_dialog">Where to place the dialog</a></h3>
+<div class="level3">
+
+<p>
+A dialog can be put on different places in on the screen. A list of possible places can be found in the <a href="http://developer.gnome.org/doc/API/2.0/gtk/gtk-Standard-Enumerations.html#GtkWindowPosition"; class="urlextern" title="http://developer.gnome.org/doc/API/2.0/gtk/gtk-Standard-Enumerations.html#GtkWindowPosition"; rel="nofollow"> GtkReference</a>
+</p>
+
+<p>
+The current dialogs are placed either on the mouse position (GTK_WIN_POS_MOUSE) or at no preset position (GTK_WIN_POS_NONE). The Gnome HID does not say anything about that topic.
+</p>
+
+<p>
+The default setting is GTK_WIN_POS_NONE for GtkWindow see <a href="http://developer.gnome.org/doc/API/2.0/gtk/GtkWindow.html#GtkWindow--window-position"; class="urlextern" title="http://developer.gnome.org/doc/API/2.0/gtk/GtkWindow.html#GtkWindow--window-position"; rel="nofollow"> GtkWindow</a>. The default for GtkDialog is GTK_WIN_POS_CENTER_ON_PARENT (<a href="http://cvs.gnome.org/viewcvs/gtk%2B/gtk/gtkdialog.c"; class="urlextern" title="http://cvs.gnome.org/viewcvs/gtk%2B/gtk/gtkdialog.c"; rel="nofollow"> taken from the GtkDialog source</a>).
+</p>
+
+</div>
+<!-- SECTION "Where to place the dialog" [6070-6814] -->
+<h3><a name="placing_dialogs_in_front_of_their_parent_window" id="placing_dialogs_in_front_of_their_parent_window">Placing dialogs in front of their parent window</a></h3>
+<div class="level3">
+
+<p>
+Most of the dialogs are placed in front of their parent window using the transient_for property (see. <a href="http://developer.gnome.org/doc/API/2.0/gtk/GtkWindow.html#gtk-window-set-transient-for"; class="urlextern" title="http://developer.gnome.org/doc/API/2.0/gtk/GtkWindow.html#gtk-window-set-transient-for"; rel="nofollow"> GtkReference</a>). This property should be set for all modal dialogs.
+</p>
+
+<p>
+For nonmodal dialogs the setting of transient_for property is not obvious. While in gschem for example the coord dialog should stay above the parent window, the log window does not need to stay in front of it.
+</p>
+
+<p>
+<strong>Note:</strong> There is an older mechanism that keeps the the dialogs in front of gschem. If the <em>raise-dialog-boxes-on-expose</em> variable is set to <em>enable</em> in one of gschemâ??s configuration files, it may cause problems with some window managers. If dialogs are flickering at 100% CPU load, then disable that setting.
+</p>
+<pre class="code lisp"><span class="co1">; raise-dialog-boxes-on-expose string</span>
+<span class="co1">;</span>
+<span class="co1">; Controls if dialog boxes are raised whenever an expose event happens</span>
+<span class="co1">; Default is enabled</span>
+<span class="co1">;</span>
+<span class="co1">;(raise-dialog-boxes-on-expose "enabled")</span>
+<span class="br0">(</span>raise-dialog-boxes-on-expose <span class="st0">"disabled"</span><span class="br0">)</span></pre>
+</div>
+<!-- SECTION "Placing dialogs in front of their parent window" [6815-7900] -->
+<h3><a name="button_order_in_dialogs" id="button_order_in_dialogs">Button order in dialogs</a></h3>
+<div class="level3">
+
+<p>
+ Button order at the bottom of the dialog depends on which operating system the user is using. GTK handles this automatically (require version > 2.6.0) , but requires the developers set the alternative button order. For more information, check the GTK documentation <a href="http://developer.gnome.org/doc/API/2.0/gtk/GtkSettings.html"; class="urlextern" title="http://developer.gnome.org/doc/API/2.0/gtk/GtkSettings.html"; rel="nofollow">here</a>.
+</p>
+
+<p>
+The alternative button order is set with just one call to a GTK function:
+</p>
+<pre class="code C"><span class="co2">#if GTK_CHECK_VERSION (2,6,0)</span>
+ <span class="coMULTI">/* Set the alternative button order (ok, cancel, help) for other systems */</span>
+ gtk_dialog_set_alternative_button_order<span class="br0">(</span>GTK_DIALOG<span class="br0">(</span>dialog<span class="br0">)</span>,
+ GTK_RESPONSE_OK,
+ GTK_RESPONSE_NO,
+ GTK_RESPONSE_CANCEL,
+ GTK_RESPONSE_HELP,
+ <span class="nu0">-1</span><span class="br0">)</span>;
+<span class="co2">#endif</span></pre>
+<p>
+This should be done for every new dialog created, before running it.
+</p>
+
+</div>
+<!-- SECTION "Button order in dialogs" [7901-8724] -->
+<h3><a name="dialog_design_of_the_current_dialogs" id="dialog_design_of_the_current_dialogs">Dialog design of the current dialogs</a></h3>
+<div class="level3">
+
+<p>
+<a href="media/devel_tips/dialog_picture.png" class="media" target="_blank" title="devel_tips:dialog_picture.png"><img src="media/devel_tips/dialog_picture.png" class="media" alt="" /></a>
+</p>
+<ul>
+<li class="level1"><div class="li"> There is some space around the whole dialog (<em>DIALOG_BORDER_SPACING</em>). </div>
+</li>
+<li class="level1"><div class="li"> Some indentation to show the topic group (<em>DIALOG_INDENTATION</em>) below itâ??s bold headline.</div>
+</li>
+<li class="level1"><div class="li"> The vertikal and the horizontal separation is done with <em>DIALOG_H_SPACING</em> and <em>DIALOG_V_SPACING</em>.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Dialog design of the current dialogs" [8725-9089] -->
+<h3><a name="source_template_for_simple_dialogs" id="source_template_for_simple_dialogs">Source template for simple dialogs</a></h3>
+<div class="level3">
+
+<p>
+This template is not intented to compile, but you can easily copy the code block that you need.
+</p>
+<pre class="code c"><span class="kw4">void</span> dialog <span class="br0">(</span>TOPLEVEL *w_current<span class="br0">)</span>
+<span class="br0">{</span>
+ GtkWidget *vbox, *label, *alignment, *table;
+ GtkWidget *dialog;
+
+ <span class="coMULTI">/* only create the dialog if it is not there yet. This usually is a
+ widget pointer in the w_current structure:
+ dialog = w_current->tewindow */</span>
+ <span class="kw1">if</span> <span class="br0">(</span>!dialog<span class="br0">)</span> <span class="br0">{</span>
+ dialog = gtk_dialog_new_with_buttons<span class="br0">(</span>_<span class="br0">(</span><span class="st0">"Dialog title"</span><span class="br0">)</span>,
+ <span class="coMULTI">/* the parent window or NULL */</span>
+ GTK_WINDOW<span class="br0">(</span>w_current->main_window<span class="br0">)</span>,
+ <span class="coMULTI">/* dialog properties */</span>
+ GTK_DIALOG_MODAL, <span class="coMULTI">/* 0 for nonmodal dialogs */</span>
+ <span class="coMULTI">/* dialog buttons and response signals */</span>
+ GTK_STOCK_CANCEL,
+ GTK_RESPONSE_REJECT,
+ GTK_STOCK_OK,
+ GTK_RESPONSE_ACCEPT,
+ <span class="kw2">NULL</span><span class="br0">)</span>;
+
+<span class="co2">#if GTK_CHECK_VERSION (2,6,0)</span>
+ <span class="coMULTI">/* Set the alternative button order (ok, cancel, help) for other systems */</span>
+ gtk_dialog_set_alternative_button_order<span class="br0">(</span>GTK_DIALOG<span class="br0">(</span>dialog<span class="br0">)</span>,
+ GTK_RESPONSE_OK,
+ GTK_RESPONSE_NO,
+ GTK_RESPONSE_CANCEL,
+ GTK_RESPONSE_HELP,
+ <span class="nu0">-1</span><span class="br0">)</span>;
+<span class="co2">#endif</span>
+
+ <span class="coMULTI">/* set default response signal. This is usually triggered by the
+ "Return" key */</span>
+ gtk_dialog_set_default_response<span class="br0">(</span>GTK_DIALOG<span class="br0">(</span>dialog<span class="br0">)</span>,
+ GTK_RESPONSE_ACCEPT<span class="br0">)</span>;
+
+ <span class="coMULTI">/* set the function for handling the button responses and dialog close
+ for nonmodal dialogs you can use dialog_run() too.*/</span>
+ gtk_signal_connect<span class="br0">(</span>GTK_OBJECT<span class="br0">(</span>dialog<span class="br0">)</span>, <span class="st0">"response"</span>,
+ GTK_SIGNAL_FUNC<span class="br0">(</span>dialog_response<span class="br0">)</span>, w_current<span class="br0">)</span>;
+
+ <span class="coMULTI">/* where to place the dialog: GTK_WIN_POS_MOUSE or GTK_WIN_POS_NONE */</span>
+ gtk_window_position<span class="br0">(</span>GTK_WINDOW <span class="br0">(</span>dialog<span class="br0">)</span>, GTK_WIN_POS_MOUSE<span class="br0">)</span>;
+
+ <span class="coMULTI">/* set the border spacing and the vbox spacing of the dialog */</span>
+ vbox = GTK_DIALOG<span class="br0">(</span>dialog<span class="br0">)</span>->vbox;
+ gtk_container_set_border_width<span class="br0">(</span>GTK_CONTAINER<span class="br0">(</span>dialog<span class="br0">)</span>,DIALOG_BORDER_SPACING<span class="br0">)</span>;
+ gtk_box_set_spacing<span class="br0">(</span>GTK_BOX<span class="br0">(</span>vbox<span class="br0">)</span>, DIALOG_V_SPACING<span class="br0">)</span>;
+
+ <span class="coMULTI">/* create a label (with markup) and pack it into the dialog box */</span>
+ label = gtk_label_new<span class="br0">(</span>_<span class="br0">(</span><span class="st0">"<b>Section label</b>"</span><span class="br0">)</span><span class="br0">)</span>;
+ gtk_label_set_use_markup<span class="br0">(</span>GTK_LABEL<span class="br0">(</span>label<span class="br0">)</span>, <span class="kw2">TRUE</span><span class="br0">)</span>;
+ gtk_misc_set_alignment<span class="br0">(</span>GTK_MISC<span class="br0">(</span>label<span class="br0">)</span>,<span class="nu0">0</span>,<span class="nu0">0</span><span class="br0">)</span>;
+ gtk_box_pack_start<span class="br0">(</span>GTK_BOX<span class="br0">(</span>vbox<span class="br0">)</span>, label, <span class="kw2">FALSE</span>, <span class="kw2">FALSE</span>, <span class="nu0">0</span><span class="br0">)</span>;
+
+ <span class="coMULTI">/* create a alignment container with the DIALOG_INDENTATION on the left */</span>
+ alignment = gtk_alignment_new<span class="br0">(</span><span class="nu0">0</span>,<span class="nu0">0</span>,<span class="nu0">1</span>,<span class="nu0">1</span><span class="br0">)</span>;
+ gtk_alignment_set_padding<span class="br0">(</span>GTK_ALIGNMENT<span class="br0">(</span>alignment<span class="br0">)</span>, <span class="nu0">0</span>, <span class="nu0">0</span>,
+ DIALOG_INDENTATION, <span class="nu0">0</span><span class="br0">)</span>;
+ gtk_box_pack_start<span class="br0">(</span>GTK_BOX<span class="br0">(</span>vbox<span class="br0">)</span>, alignment, <span class="kw2">FALSE</span>, <span class="kw2">FALSE</span>, <span class="nu0">0</span><span class="br0">)</span>;
+
+ <span class="coMULTI">/* a table can store several entries. It is stored in the aligment container.
+ Note: the vertical and horizontal cell spacings */</span>
+ table = gtk_table_new <span class="br0">(</span><span class="nu0">3</span>, <span class="nu0">2</span>, <span class="kw2">FALSE</span><span class="br0">)</span>;
+ gtk_table_set_row_spacings<span class="br0">(</span>GTK_TABLE<span class="br0">(</span>table<span class="br0">)</span>, DIALOG_V_SPACING<span class="br0">)</span>;
+ gtk_table_set_col_spacings<span class="br0">(</span>GTK_TABLE<span class="br0">(</span>table<span class="br0">)</span>, DIALOG_H_SPACING<span class="br0">)</span>;
+ gtk_container_add<span class="br0">(</span>GTK_CONTAINER<span class="br0">(</span>alignment<span class="br0">)</span>, table<span class="br0">)</span>;
+
+ <span class="coMULTI">/* a simple text label in one table cell with left alignment.
+ Note: the GTK_FILL in the third line is required */</span>
+ label = gtk_label_new<span class="br0">(</span>_<span class="br0">(</span><span class="st0">"Text:"</span><span class="br0">)</span><span class="br0">)</span>;
+ gtk_misc_set_alignment<span class="br0">(</span>GTK_MISC<span class="br0">(</span>label<span class="br0">)</span>,<span class="nu0">0</span>,<span class="nu0">0</span><span class="br0">)</span>;
+ gtk_table_attach<span class="br0">(</span>GTK_TABLE<span class="br0">(</span>table<span class="br0">)</span>, label, <span class="nu0">0</span>,<span class="nu0">1</span>,<span class="nu0">0</span>,<span class="nu0">1</span>, GTK_FILL,<span class="nu0">0</span>,<span class="nu0">0</span>,<span class="nu0">0</span><span class="br0">)</span>;
+
+ <span class="coMULTI">/* a simple text entry completes the option row */</span>
+ textentry = gtk_entry_new_with_max_length <span class="br0">(</span><span class="nu0">10</span><span class="br0">)</span>;
+ gtk_table_attach_defaults<span class="br0">(</span>GTK_TABLE<span class="br0">(</span>table<span class="br0">)</span>, textentry, <span class="nu0">1</span>,<span class="nu0">2</span>,<span class="nu0">0</span>,<span class="nu0">1</span><span class="br0">)</span>;
+ gtk_entry_set_activates_default<span class="br0">(</span>GTK_ENTRY<span class="br0">(</span>textentry<span class="br0">)</span>, <span class="kw2">TRUE</span><span class="br0">)</span>;
+
+ <span class="coMULTI">/* ..... more table rows with options, or new sections */</span>
+
+ <span class="coMULTI">/* create references to all widgets that you need later */</span>
+ GLADE_HOOKUP_OBJECT<span class="br0">(</span>dialog, sizeentry,<span class="st0">"textentry"</span><span class="br0">)</span>;
+
+ <span class="coMULTI">/* show all widgets recursivly */</span>
+ gtk_widget_show_all<span class="br0">(</span>dialog<span class="br0">)</span>;
+ <span class="br0">}</span>
+
+ <span class="kw1">else</span> <span class="br0">{</span>
+ <span class="coMULTI">/* Dialog is already there. Present it to the user.
+ This is only required if you have a nonmodal dialog */</span>
+ gtk_window_present<span class="br0">(</span>GTK_WINDOW<span class="br0">(</span>dialog<span class="br0">)</span><span class="br0">)</span>;
+ <span class="br0">}</span>
+
+ <span class="coMULTI">/* always set the current values to the dialog
+ If you're placing that part at the end of the dialog function you can
+ easily create dialogs that can be called, even if they are already open */</span>
+ textentry = g_object_get_data<span class="br0">(</span>G_OBJECT<span class="br0">(</span>dialog<span class="br0">)</span>, <span class="st0">"textentry"</span><span class="br0">)</span>;
+ gtk_entry_set_text<span class="br0">(</span>GTK_ENTRY<span class="br0">(</span>textentry<span class="br0">)</span>, <span class="kw4">string</span><span class="br0">)</span>;
+ <span class="coMULTI">/* select the text region that the user usually likes to overwrite */</span>
+ gtk_entry_select_region<span class="br0">(</span>GTK_ENTRY<span class="br0">(</span>textentry<span class="br0">)</span>, <span class="nu0">0</span>, strlen<span class="br0">(</span><span class="kw4">string</span><span class="br0">)</span><span class="br0">)</span>;
+<span class="br0">}</span></pre>
+<p>
+The response function for such a dialog may look like this:
+</p>
+<pre class="code c"><span class="kw4">void</span> dialog_response<span class="br0">(</span>GtkWidget *widget, gint response, TOPLEVEL *w_current<span class="br0">)</span>
+<span class="br0">{</span>
+ <span class="kw1">switch</span> <span class="br0">(</span>response<span class="br0">)</span> <span class="br0">{</span>
+ <span class="kw1">case</span> GTK_RESPONSE_ACCEPT:
+ <span class="coMULTI">/* apply the dialog settings:
+ just insert your code here if it is short
+ call an extra apply function if the required code is long */</span>
+ <span class="kw2">break</span>;
+ <span class="kw1">case</span> GTK_RESPONSE_REJECT:
+ <span class="kw1">case</span> GTK_RESPONSE_DELETE_EVENT:
+ <span class="coMULTI">/* for modal dialogs just do nothing,
+ for nonmodal dialogs, destroy the dialog and clean up */</span>
+ <span class="kw2">break</span>;
+ <span class="kw1">default</span>:
+ <span class="coMULTI">/* catch wrong signals signals (paranoid error checking ;-)) */</span>
+ <a href="http://www.opengroup.org/onlinepubs/009695399/functions/printf.html";><span class="kw3">printf</span></a><span class="br0">(</span><span class="st0">"dialog_response(): strange signal %d<span class="es0">\n</span>"</span>, response<span class="br0">)</span>;
+ <span class="br0">}</span>
+
+ <span class="coMULTI">/* for nonmodal dialogs just do nothing,
+ for modal dialogs, always destroy the dialog and clean up */</span>
+<span class="br0">}</span></pre>
+</div>
+<!-- SECTION "Source template for simple dialogs" [9090-14225] -->
+<h3><a name="current_dialog_issues_in_gschem" id="current_dialog_issues_in_gschem">Current Dialog Issues in Gschem</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> every dialog has itâ??s own design</div>
+</li>
+<li class="level1"><div class="li"> dialog placement: mouse position or no predefined position?</div>
+</li>
+<li class="level1"><div class="li"> dialogs do not remember their last size, position and contents.</div>
+</li>
+<li class="level1"><div class="li"> missing keyboard shortcuts</div>
+</li>
+</ul>
+
+<p>
+ <strong>Hereâ??s a list of things that could be improved:</strong>
+</p>
+
+</div>
+
+<h5><a name="print_dialog" id="print_dialog">Print Dialog</a></h5>
+<div class="level5">
+<ul>
+<li class="level1"><div class="li"> change design?</div>
+</li>
+</ul>
+
+</div>
+
+<h5><a name="write_image" id="write_image">Write Image</a></h5>
+<div class="level5">
+<ul>
+<li class="level1"><div class="li"> In the fileselect dialog the default filename is missing if the file does not exist</div>
+</li>
+<li class="level1"><div class="li"> Return key does not work in the filename entry</div>
+</li>
+</ul>
+
+</div>
+
+<h5><a name="execute_script" id="execute_script">Execute Script</a></h5>
+<div class="level5">
+<ul>
+<li class="level1"><div class="li"> </div>
+</li>
+</ul>
+
+</div>
+
+<h5><a name="edit_text" id="edit_text">Edit Text</a></h5>
+<div class="level5">
+<ul>
+<li class="level1"><div class="li"> some missing keyboard shortcuts</div>
+</li>
+<li class="level1"><div class="li"> add *unmodified* tags if there are multiple selections</div>
+</li>
+<li class="level1"><div class="li"> maybe add some color pixbufs for the color</div>
+</li>
+<li class="level1"><div class="li"> maybe replace the text alignment with nine ratio buttons, toggle buttons with icons or …</div>
+</li>
+</ul>
+
+</div>
+
+<h5><a name="color_dialog" id="color_dialog">Color Dialog</a></h5>
+<div class="level5">
+<ul>
+<li class="level1"><div class="li"> maybe add some color pixbufs for the color</div>
+</li>
+</ul>
+
+</div>
+
+<h5><a name="line_width_and_type" id="line_width_and_type">Line Width and Type</a></h5>
+<div class="level5">
+<ul>
+<li class="level1"><div class="li"> keyboard shortcuts missing</div>
+</li>
+<li class="level1"><div class="li"> icons for the line type</div>
+</li>
+</ul>
+
+</div>
+
+<h5><a name="fill_type" id="fill_type">Fill Type</a></h5>
+<div class="level5">
+<ul>
+<li class="level1"><div class="li"> keyboard shortcuts missing</div>
+</li>
+<li class="level1"><div class="li"> icons in the fill type</div>
+</li>
+</ul>
+
+</div>
+
+<h5><a name="translate_symbol" id="translate_symbol">Translate Symbol</a></h5>
+<div class="level5">
+<ul>
+<li class="level1"><div class="li"> </div>
+</li>
+</ul>
+
+</div>
+
+<h5><a name="page_manager" id="page_manager">Page Manager</a></h5>
+<div class="level5">
+<ul>
+<li class="level1"><div class="li"> wrong button order? Depends on whether you think the refresh button is the main action button or just an extra button.</div>
+</li>
+<li class="level1"><div class="li"> Maybe the â??Returnâ?? key should trigger Refresh</div>
+</li>
+</ul>
+
+</div>
+
+<h5><a name="component_selector" id="component_selector">Component Selector</a></h5>
+<div class="level5">
+<ul>
+<li class="level1"><div class="li"> strange edit widget when typing and the tree is selected (Itâ??s a search helper widget, disable it?!)</div>
+</li>
+</ul>
+
+</div>
+
+<h5><a name="single_attribut_editor" id="single_attribut_editor">Single Attribut Editor</a></h5>
+<div class="level5">
+<ul>
+<li class="level1"><div class="li"> when multiple elements are selected and you call edit (ee) there are a few problems:</div>
+<ul>
+<li class="level3"><div class="li"> if the first object is text, then this dialog is opened (but with the wrong list parameter</div>
+</li>
+<li class="level3"><div class="li"> if the first object is complex then the multiple attribute editor is called</div>
+</li>
+</ul>
+</li>
+</ul>
+
+</div>
+
+<h5><a name="multi_attribute_editor" id="multi_attribute_editor">Multi Attribute Editor</a></h5>
+<div class="level5">
+<ul>
+<li class="level1"><div class="li"> </div>
+</li>
+</ul>
+
+</div>
+
+<h5><a name="add_text" id="add_text">Add Text</a></h5>
+<div class="level5">
+<ul>
+<li class="level1"><div class="li"> </div>
+</li>
+</ul>
+
+</div>
+
+<h5><a name="arc_params" id="arc_params">Arc Params</a></h5>
+<div class="level5">
+<ul>
+<li class="level1"><div class="li"> add the diameter to the dialog, but select the start angle entry (increment = grid)</div>
+</li>
+<li class="level1"><div class="li"> let â??eeâ?? call that dialog if only a single arc is selected</div>
+</li>
+<li class="level1"><div class="li"> maybe add a section label</div>
+</li>
+</ul>
+
+</div>
+
+<h5><a name="insert_picture" id="insert_picture">Insert Picture</a></h5>
+<div class="level5">
+<ul>
+<li class="level1"><div class="li"> </div>
+</li>
+</ul>
+
+</div>
+
+<h5><a name="picture_replace" id="picture_replace">Picture Replace</a></h5>
+<div class="level5">
+<ul>
+<li class="level1"><div class="li"> the new picture uses the aspect ratio of the old picture</div>
+</li>
+<li class="level1"><div class="li"> the dialog has lots in common with the Insert Picture dialog. They could use some code together</div>
+</li>
+</ul>
+
+</div>
+
+<h5><a name="find_text" id="find_text">Find Text</a></h5>
+<div class="level5">
+<ul>
+<li class="level1"><div class="li"> manipulates the mouse pointer (maybe the zooming code is the culprit). Just press â??Returnâ?? to trigger a FindNext</div>
+</li>
+<li class="level1"><div class="li"> if you select hierarchy and the found text is in a different schematic, then the filename in the title is not updated</div>
+</li>
+<li class="level1"><div class="li"> maybe add an option: â??Select all matching text objectsâ??, disable hierarchy for that feature!</div>
+</li>
+<li class="level1"><div class="li"> <img src="images/smileys/fixme.gif" align="middle" alt="FIXME" /> gschem hangs if you use that dialog with hierarchical schematics that have dependancy loops (e.g. the autonumber test schematics)</div>
+</li>
+<li class="level1"><div class="li"> add an option â??search for visible text onlyâ??</div>
+</li>
+<li class="level1"><div class="li"> maybe use regular expressions instead of the substring for the searchtext</div>
+</li>
+</ul>
+
+</div>
+
+<h5><a name="hide_text" id="hide_text">Hide Text</a></h5>
+<div class="level5">
+<ul>
+<li class="level1"><div class="li"> use regular expressions instead of starting substring</div>
+</li>
+</ul>
+
+</div>
+
+<h5><a name="show_text" id="show_text">Show Text</a></h5>
+<div class="level5">
+<ul>
+<li class="level1"><div class="li"> use regular expressions instead of starting substring</div>
+</li>
+<li class="level1"><div class="li"> Maybe merge that dialog together with the â??Hide Textâ?? dialog</div>
+</li>
+</ul>
+
+</div>
+
+<h5><a name="autonumber_text" id="autonumber_text">Autonumber Text</a></h5>
+<div class="level5">
+<ul>
+<li class="level1"><div class="li"> Maybe disable the skip option if the renumber scope is â??selectionâ??. The other skip options (Page and Hierarchy) are really stupid.</div>
+</li>
+</ul>
+
+</div>
+
+<h5><a name="text_size" id="text_size">Text Size</a></h5>
+<div class="level5">
+<ul>
+<li class="level1"><div class="li"> </div>
+</li>
+</ul>
+
+</div>
+
+<h5><a name="snap_grid_spacing" id="snap_grid_spacing">Snap Grid Spacing</a></h5>
+<div class="level5">
+<ul>
+<li class="level1"><div class="li"> </div>
+</li>
+</ul>
+
+</div>
+
+<h5><a name="coord_dialog" id="coord_dialog">Coord Dialog</a></h5>
+<div class="level5">
+<ul>
+<li class="level1"><div class="li"> maybe move the world coordinates to the main window status bar</div>
+</li>
+</ul>
+
+</div>
+
+<h5><a name="about_dialog" id="about_dialog">About Dialog</a></h5>
+<div class="level5">
+<ul>
+<li class="level1"><div class="li"> </div>
+</li>
+</ul>
+
+</div>
+
+<h5><a name="hotkeys" id="hotkeys">Hotkeys</a></h5>
+<div class="level5">
+<ul>
+<li class="level1"><div class="li"> </div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Current Dialog Issues in Gschem" [14226-] --></body>
+</html>
diff --git a/docs/wiki/geda-devmacosx.html b/docs/wiki/geda-devmacosx.html
new file mode 100644
index 0000000..e0dc148
--- /dev/null
+++ b/docs/wiki/geda-devmacosx.html
@@ -0,0 +1,160 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#geda_on_the_mac" class="toc">gEDA On The Mac</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#geda_via_fink" class="toc">gEDA via Fink</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#geda_via_macports" class="toc">gEDA via macports</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#building_the_project" class="toc">Building The Project</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#working_with_python" class="toc">Working With Python</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#current_mac_issues" class="toc">Current Mac Issues</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#geda_via_virtualbox" class="toc">gEDA via VirtualBox</a></span></div></li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h2><a name="geda_on_the_mac" id="geda_on_the_mac">gEDA On The Mac</a></h2>
+<div class="level2">
+
+<p>
+ There are a number of options with running gEDA on the mac. You can install via the fink or macports package management or build from the source or some combination of the two. Both fink and macports will install software in a directory off the root or â??sandboxâ?? (fink /sw and macports /opt) so they donâ??t co-mingle software with your native mac software. You can read more about the pros and cons of each online.
+</p>
+
+<p>
+I have both fink and macports package managers installed and have been using macports lately. I added some code to my .bash_profile that lets me choose what package manager I want to use on shell startup by setting my path variable. Iâ??ve pasted it below.
+</p>
+
+<p>
+Personally, I use macports to install dependencies and build and install geda from the source. This makes it easy for me to grab the latest code from the git repository.
+</p>
+<pre class="code">
+PS3="Which port?:"
+echo "Choose from the list below."
+select NAME in macports fink mac
+do
+ break
+done
+echo "Setting path to prefer $NAME."
+case $NAME in
+macports) export PATH=/opt/local/bin:${PATH} PS1="opt-\A-[\w]\$" ;;
+fink) test -r /sw/bin/init.sh && . /sw/bin/init.sh PS1="sw-\A-[\w\\$" ;;
+*) PS1="osx-\A-[\w]\$" ;;
+esac
+
+echo "Path set to " $PATH
+</pre>
+
+</div>
+<!-- SECTION "gEDA On The Mac" [1-1251] -->
+<h2><a name="geda_via_fink" id="geda_via_fink">gEDA via Fink</a></h2>
+<div class="level2">
+
+<p>
+You can link to instructions on installing gEDA via fink from the gEDA <a href="http://www.geda.seul.org/download.html"; class="urlextern" title="http://www.geda.seul.org/download.html"; rel="nofollow">download page</a> or go directly to <a href="http://www.ghz.cc/charles/fink/"; class="urlextern" title="http://www.ghz.cc/charles/fink/"; rel="nofollow">http://www.ghz.cc/charles/fink/</a>. Using fink, gEDA can be installed from binaries or compiled from a recent development snapshot, if the fink unstable branch is enabled. (Please see the Fink documentation on how to enable the unstable branch.)
+</p>
+
+<p>
+Once Fink is installed, gEDA (and other programs) can be installed from the command line or through a graphical tool called <a href="http://finkcommander.sourceforge.net/"; class="urlextern" title="http://finkcommander.sourceforge.net/"; rel="nofollow">fink commander</a>. From the command line, the principal gEDA suite programs can be installed with the command:
+</p>
+<pre class="code">fink install geda-bundle</pre>
+
+</div>
+<!-- SECTION "gEDA via Fink" [1252-1994] -->
+<h2><a name="geda_via_macports" id="geda_via_macports">gEDA via macports</a></h2>
+<div class="level2">
+
+<p>
+I am in the process of putting together a macports release of gEDA. You can download macports from <a href="http://www.macports.org/"; class="urlextern" title="http://www.macports.org/"; rel="nofollow">http://www.macports.org/</a>. I use macports with the <acronym title="Graphical User Interface">GUI</acronym> Porticus. You can download that from here <a href="http://porticus.alittledrop.com/"; class="urlextern" title="http://porticus.alittledrop.com/"; rel="nofollow">http://porticus.alittledrop.com/</a>.
+</p>
+
+<p>
+Until the macports release is ready, you can use Porticus (or macports command line) to install these dependent projects, then download and compile the source from the gEDA download page.
+</p>
+<ul>
+<li class="level1"><div class="li"> gettext</div>
+</li>
+<li class="level1"><div class="li"> guile</div>
+</li>
+<li class="level1"><div class="li"> gtk2</div>
+</li>
+<li class="level1"><div class="li"> groff</div>
+</li>
+<li class="level1"><div class="li"> intltool</div>
+</li>
+</ul>
+
+<p>
+ Iâ??ve also installed python25 and python_select. python_select letâ??s you choose what version of python your mac will run as the default python.
+</p>
+
+</div>
+<!-- SECTION "gEDA via macports" [1995-2654] -->
+<h2><a name="building_the_project" id="building_the_project">Building The Project</a></h2>
+<div class="level2">
+
+<p>
+ Once you have the dependencies installed (either via fink or macports) just follow the instructions in the developer section for building and installing. I had no issues (there was an issue with strnlen function being used in gschem, which isnâ??t part of the standard gcc libraries, but once that was fixed I was able to build and run with no problems). I have also setup an XCode project to debug gEDA code in. I will post that up to the site as soon as itâ??s ready.
+</p>
+
+</div>
+<!-- SECTION "Building The Project" [2655-3158] -->
+<h2><a name="working_with_python" id="working_with_python">Working With Python</a></h2>
+<div class="level2">
+
+<p>
+Currently I am working with myEclipse and the PyDev python plugin. You can download Eclipse <a href="http://www.eclipse.org/"; class="urlextern" title="http://www.eclipse.org/"; rel="nofollow">http://www.eclipse.org/</a> or myEclipse <a href="http://www.eclipse.org/"; class="urlextern" title="http://www.eclipse.org/"; rel="nofollow">http://www.eclipse.org/</a> which is Eclipse bundled with plugins and currently costs $31.75 per year for a subscription. You can download PyDev here <a href="http://pydev.sourceforge.net/"; class="urlextern" title="http://pydev.sourceforge.net/"; rel="nofollow">http://pydev.sourceforge.net/</a>. It seems to have an annoying popup unless you buy a license, but other than that it seems to work well in Eclipse for working with python code.
+</p>
+
+</div>
+<!-- SECTION "Working With Python" [3159-3657] -->
+<h2><a name="current_mac_issues" id="current_mac_issues">Current Mac Issues</a></h2>
+<div class="level2">
+<ul>
+<li class="level1"><div class="li"> gEDA Manager does not currently run because it needs pyinotify which is based on Linux kernel infrastructure. If anyone knows a way to get gEDA Manager running on mac that is appreciated. Otherwise I plan on looking at a cross platform way to modify gEDA Manager.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Current Mac Issues" [3658-3962] -->
+<h2><a name="geda_via_virtualbox" id="geda_via_virtualbox">gEDA via VirtualBox</a></h2>
+<div class="level2">
+
+<p>
+An alternative method to run gEDA programs on the Mac is to install them under Linux in an virtualization environment. <a href="http://www.virtualbox.org/"; class="urlextern" title="http://www.virtualbox.org/"; rel="nofollow">VirtualBox</a> is a professional-grade x86 virtualization program that is available under the <acronym title="GNU General Public License">GPL</acronym>. After installing this program, you can download and install a linux distribution within that environment. This method has the advantage of using precompiled linux-oriented binaries, and installatoin - even accounting for for downloading and installing the guest <acronym title="Operating System">OS</acronym> - can be <em>very fast</em> compared to compiling and building the gEDA suite in Fink.
+</p>
+
+<p>
+The gEDA suite programs have been tested and appear to work properly under Ubuntu running within VirtualBox on the Mac. After downloading and installing VirtualBox, download <a href="http://www.ubuntu.com/getubuntu"; class="urlextern" title="http://www.ubuntu.com/getubuntu"; rel="nofollow">Ubuntu</a> and launch its installer, following the VirtualBox instructions. Once Ubuntu is installed, you can install gEDA following (simplified, standard) procedures for installing gEDA under linux. From the command line,
+</p>
+<pre class="code">sudo apt-get install geda</pre>
+
+<p>
+ This installs gschem , gnetlist, & gattrib. Then, to install additional applications:
+</p>
+<pre class="code">sudo apt-get install geda-utlils
+sudo apt-get install pcb-gtk
+sudo apt-get install gerbv
+sudo apt-get install geda-xgsch2pcb</pre>
+
+</div>
+<!-- SECTION "gEDA via VirtualBox" [3963-] --></body>
+</html>
diff --git a/docs/wiki/geda-documentation.fr.html b/docs/wiki/geda-documentation.fr.html
new file mode 100644
index 0000000..cc0b8e6
--- /dev/null
+++ b/docs/wiki/geda-documentation.fr.html
@@ -0,0 +1,371 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#documentation_en_ligne_de_la_suite_d_outils_geda" class="toc">Documentation en ligne de la Suite d'Outils gEDA</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#for_document_authors" class="toc">For document authors</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#gschem_-_saisie_de_schemas" class="toc">gschem - Saisie de Schémas</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#gnetlist_-_netlister" class="toc">gnetlist - Netlister</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#gsymcheck_-_symbol_checker" class="toc">gsymcheck - Symbol Checker</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#utils_-_geda_utilities" class="toc">utils - gEDA Utilities</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#examples" class="toc">Examples</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#attribute_file_format_details" class="toc">Attribute/File Format Details</a></span></div></li>
+</ul>
+</li>
+<li class="level1"><div class="li"><span class="li"><a href="#spice" class="toc">SPICE</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#ngspice" class="toc">ngspice</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#gnucap" class="toc">gnucap</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#gspiceui" class="toc">gSpiceUI</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#pcb" class="toc">PCB</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#gerbv" class="toc">gerbv</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#icarus_verilog" class="toc">Icarus Verilog</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#gtkwave" class="toc">GTKWave</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#wcalc" class="toc">Wcalc</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#mcalc" class="toc">mcalc</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#covered" class="toc">covered</a></span></div></li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="documentation_en_ligne_de_la_suite_d_outils_geda" id="documentation_en_ligne_de_la_suite_d_outils_geda">Documentation en ligne de la Suite d'Outils gEDA</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "Documentation en ligne de la Suite d'Outils gEDA" [1-64] -->
+<h2><a name="for_document_authors" id="for_document_authors">For document authors</a></h2>
+<div class="level2">
+
+<p>
+New features are available for document authors:
+</p>
+<ul>
+<li class="level1"><div class="li"> <a href="geda-syntax_features.html" class="wikilink1" title="geda-syntax_features.html">Syntax features</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-installed_plugins.html" class="wikilink1" title="geda-installed_plugins.html">Installed plugins</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-style_guide.html" class="wikilink1" title="geda-style_guide.html">Style Guide</a> – A work in progress, please contribute</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "For document authors" [65-273] -->
+<h2><a name="gschem_-_saisie_de_schemas" id="gschem_-_saisie_de_schemas">gschem - Saisie de Schémas</a></h2>
+<div class="level2">
+<ul>
+<li class="level1"><div class="li"> <a href="geda-gschem_ug.fr.html" class="wikilink1" title="geda-gschem_ug.fr.html">Guide de l'Utilisateur gschem</a> – En cours, vous pouvez participer</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-gschem_mp.fr.html" class="wikilink2" title="geda-gschem_mp.fr.html">page de manuel gschem</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-scg.fr.html" class="wikilink1" title="geda-scg.fr.html">Guide de la Création de Symbole</a> (à traduire)</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-hse_howto.fr.html" class="wikilink2" title="geda-hse_howto.fr.html">Hooks/Scheme Extension HOWTO</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-kig_howto.fr.html" class="wikilink2" title="geda-kig_howto.fr.html">HOWTO du Keymapping dans gschem</a></div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "gschem - Saisie de Schémas" [274-634] -->
+<h2><a name="gnetlist_-_netlister" id="gnetlist_-_netlister">gnetlist - Netlister</a></h2>
+<div class="level2">
+<ul>
+<li class="level1"><div class="li"> <a href="geda-gnetlist_ug.html" class="wikilink1" title="geda-gnetlist_ug.html">gnetlist User's Guide</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-gnetlist_mp.html" class="wikilink1" title="geda-gnetlist_mp.html">gnetlist man-page</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-sdb_howto.html" class="wikilink1" title="geda-sdb_howto.html">Spice netlisting (SDB) HOWTO</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-na_howto.html" class="wikilink1" title="geda-na_howto.html">net= attribute mini-HOWTO</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-ssan.html" class="wikilink1" title="geda-ssan.html">Switcap Symbols and Netlister</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-sn_readme.html" class="wikilink1" title="geda-sn_readme.html">Switcap netlister README</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-fbabgapp.html" class="wikilink1" title="geda-fbabgapp.html">Forward/Backward Annotation Between gEDA and Pads PowerPCB</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-grcsan.html" class="wikilink1" title="geda-grcsan.html">gEDA RF Cascade Symbols and Netlister</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-bom_readme.html" class="wikilink1" title="geda-bom_readme.html">Bill of Material netlister README</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-gschem2pcb_readme.html" class="wikilink1" title="geda-gschem2pcb_readme.html">gschem2pcb README</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-verilog_netlister_readme.html" class="wikilink1" title="geda-verilog_netlister_readme.html">Verilog netlister README</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-vhdl_netlister_readme.html" class="wikilink1" title="geda-vhdl_netlister_readme.html">VHDL netlister README</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-vams_netlister_readme.html" class="wikilink1" title="geda-vams_netlister_readme.html">VAMS netlister README</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-systemc_netlister_readme.html" class="wikilink1" title="geda-systemc_netlister_readme.html">SystemC netlister README</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-eagle_pcb_netlister_readme.html" class="wikilink1" title="geda-eagle_pcb_netlister_readme.html">Eagle PCB netlister README</a></div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "gnetlist - Netlister" [635-1507] -->
+<h2><a name="gsymcheck_-_symbol_checker" id="gsymcheck_-_symbol_checker">gsymcheck - Symbol Checker</a></h2>
+<div class="level2">
+<ul>
+<li class="level1"><div class="li"> <a href="geda-gsymcheck_mp.html" class="wikilink1" title="geda-gsymcheck_mp.html">gsymcheck man-page</a></div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "gsymcheck - Symbol Checker" [1508-1592] -->
+<h2><a name="utils_-_geda_utilities" id="utils_-_geda_utilities">utils - gEDA Utilities</a></h2>
+<div class="level2">
+<ul>
+<li class="level1"><div class="li"> <a href="geda-gsch2pcb_readme.html" class="wikilink1" title="geda-gsch2pcb_readme.html">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.html">gschem and pcb tutorial</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-tragesym_readme.html" class="wikilink1" title="geda-tragesym_readme.html">tragesym (symbol generator) README</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-tragesym_tutorial.fr.html" class="wikilink1" title="geda-tragesym_tutorial.fr.html">Tutoriel tragesym.fr</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-olib_readme.html" class="wikilink1" title="geda-olib_readme.html">olib (OrCAD (TM) converter) README</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-grenum_mp.html" class="wikilink1" title="geda-grenum_mp.html">grenum man-page</a> – note</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-gattrib_readme.html" class="wikilink1" title="geda-gattrib_readme.html">gattrib README</a> – note</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "utils - gEDA Utilities" [1593-2012] -->
+<h2><a name="examples" id="examples">Examples</a></h2>
+<div class="level2">
+<ul>
+<li class="level1"><div class="li"> <a href="geda-example_hsm.html" class="wikilink1" title="geda-example_hsm.html">Hierarchical SPICE model</a> – note</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-example_usbjtag.html" class="wikilink1" title="geda-example_usbjtag.html">Example USB-based JTAG interface</a> – note</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Examples" [2013-2162] -->
+<h2><a name="attribute_file_format_details" id="attribute_file_format_details">Attribute/File Format Details</a></h2>
+<div class="level2">
+<ul>
+<li class="level1"><div class="li"> <a href="geda-master_attributes_list.html" class="wikilink1" title="geda-master_attributes_list.html">Master Attributes List</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-file_format_spec.html" class="wikilink1" title="geda-file_format_spec.html">sym/sch File Format Specification</a></div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Attribute/File Format Details" [2163-2328] -->
+<h1><a name="spice" id="spice">SPICE</a></h1>
+<div class="level1">
+<ul>
+<li class="level1"><div class="li"> <a href="http://www.geda.seul.org/tools/gnucap/papers/al-davis-dissertation.pdf"; class="urlextern" title="http://www.geda.seul.org/tools/gnucap/papers/al-davis-dissertation.pdf"; rel="nofollow">Implicit Mixed-Mode Simulation of VLSI Circuits</a> by Albert Tatum Davis (1991)<br/>
+ Please report if this <acronym title="Uniform Resource Locator">URL</acronym> goes dead.</div>
+</li>
+<li class="level1"><div class="li"> <a href="http://www.brorson.com/gEDA/SPICE/intro.html"; class="urlextern" title="http://www.brorson.com/gEDA/SPICE/intro.html"; rel="nofollow">Circuit Simulation using gEDA and SPICE - HOWTO</a> (<acronym title="HyperText Markup Language">HTML</acronym> version)<br/>
+ by Stuart Brorson (20 December 2004).<br/>
+ Please report if this <acronym title="Uniform Resource Locator">URL</acronym> is not the latest version.</div>
+</li>
+<li class="level1"><div class="li"> <a href="http://www.brorson.com/gEDA/HOWTO/gEDA_Spice_HOWTO-20050103.pdf"; class="urlextern" title="http://www.brorson.com/gEDA/HOWTO/gEDA_Spice_HOWTO-20050103.pdf"; rel="nofollow">Circuit Simulation using gEDA and SPICE - HOWTO</a> (<acronym title="Portable Document Format">PDF</acronym> version)<br/>
+ by Stuart Brorson ( 5 January 2005).</div>
+</li>
+</ul>
+
+<p>
+ Testing:
+</p>
+<ul>
+<li class="level1"><div class="li"> <a href="geda-csygas.html" class="wikilink1" title="geda-csygas.html">Circuit Simulation using gEDA and SPICE - HOWTO</a> – Done converting. Please comment on this conversion to a wiki-format.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "SPICE" [2329-3078] -->
+<h1><a name="ngspice" id="ngspice">ngspice</a></h1>
+<div class="level1">
+<ul>
+<li class="level1"><div class="li"> <a href="http://www-ti.informatik.uni-tuebingen.de/~bernauer/lehre/ti-1-0506/spice/ngspice.pdf"; class="urlextern" title="http://www-ti.informatik.uni-tuebingen.de/~bernauer/lehre/ti-1-0506/spice/ngspice.pdf"; rel="nofollow">NGSPICE User Manual</a> – describes ngspice-rework-17, Draft Version 0.2<br/>
+ Please report if this <acronym title="Uniform Resource Locator">URL</acronym> is not the appropriated version, or if it goes dead.</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-ngspice_mp.html" class="wikilink1" title="geda-ngspice_mp.html">ngspice man-page</a> – note</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-ngnutmeg_mp.html" class="wikilink1" title="geda-ngnutmeg_mp.html">ngnutmeg man-page</a> – note</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-ngsconvert_mp.html" class="wikilink1" title="geda-ngsconvert_mp.html">ngsconvert man-page</a> – note</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "ngspice" [3079-3501] -->
+<h1><a name="gnucap" id="gnucap">gnucap</a></h1>
+<div class="level1">
+<ul>
+<li class="level1"><div class="li"> <a href="http://www.geda.seul.org/tools/gnucap/gnucap-man.pdf"; class="urlextern" title="http://www.geda.seul.org/tools/gnucap/gnucap-man.pdf"; rel="nofollow">The Gnu Circuit Analysis Package Users manual</a> – January 21,2004 version</div>
+</li>
+<li class="level1"><div class="li"> <a href="http://www.geda.seul.org/tools/gnucap/papers/gnucap-model-compiler.pdf"; class="urlextern" title="http://www.geda.seul.org/tools/gnucap/papers/gnucap-model-compiler.pdf"; rel="nofollow">The Gnucap Model Compiler</a></div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "gnucap" [3502-3762] -->
+<h1><a name="gspiceui" id="gspiceui">gSpiceUI</a></h1>
+<div class="level1">
+<ul>
+<li class="level1"><div class="li"> <a href="file:///shared/gEDA-20060124/Documents/gSpiceUI/gSpiceUI.html" class="urlextern" title="file:///shared/gEDA-20060124/Documents/gSpiceUI/gSpiceUI.html" rel="nofollow">GNU Spice GUI</a></div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "gSpiceUI" [3763-3870] -->
+<h1><a name="pcb" id="pcb">PCB</a></h1>
+<div class="level1">
+<ul>
+<li class="level1"><div class="li"> <a href="geda-pcb_ug.html" class="wikilink2" title="geda-pcb_ug.html">Pcb-1.99q</a> – gEDA Suite version 20060123</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-footprint_creation.html" class="wikilink2" title="geda-footprint_creation.html">footprint_creation</a> – Stuart Brorsonâ??s document, is this the latest?</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-pcb_mp.html" class="wikilink1" title="geda-pcb_mp.html">PCB man-page</a></div>
+</li>
+<li class="level1"><div class="li"></div>
+</li>
+<li class="level1"><div class="li"> <a href="http://pcb.sourceforge.net/manual.html"; class="urlextern" title="http://pcb.sourceforge.net/manual.html"; rel="nofollow">Recent development shapshot manuals and the current CVS version manual</a></div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "PCB" [3871-4187] -->
+<h1><a name="gerbv" id="gerbv">gerbv</a></h1>
+<div class="level1">
+<ul>
+<li class="level1"><div class="li"> <a href="geda-gerbv_mp.html" class="wikilink1" title="geda-gerbv_mp.html">gerbv man-page</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-gerbv_pnp_readme.html" class="wikilink1" title="geda-gerbv_pnp_readme.html">Searching for Parts and marking them on screen (in gerbv)</a></div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "gerbv" [4188-4333] -->
+<h1><a name="icarus_verilog" id="icarus_verilog">Icarus Verilog</a></h1>
+<div class="level1">
+<ul>
+<li class="level1"><div class="li"> <a href="geda-icarus_quick_start.html" class="wikilink1" title="geda-icarus_quick_start.html">Getting Started with Icarus Verilog</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-icarus_mp.html" class="wikilink1" title="geda-icarus_mp.html">Icarus Verilog compiler man-page</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-icarus_vpi_mp.html" class="wikilink1" title="geda-icarus_vpi_mp.html">Compile front end for VPI modules man-page</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-icarus_vvp_runtime.html" class="wikilink1" title="geda-icarus_vvp_runtime.html">Icarus Verilog vvp runtime engine man-page</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-icarus_readme.html" class="wikilink1" title="geda-icarus_readme.html">The Icarus Verilog Compilation System</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-igarus_fpga_lcg.html" class="wikilink1" title="geda-igarus_fpga_lcg.html">FPGA Loadable Code Generator for Icarus Verilog</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-icarus_xilinx_hints.html" class="wikilink1" title="geda-icarus_xilinx_hints.html">Xilinx Hints</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-icarus_xnf.html" class="wikilink1" title="geda-icarus_xnf.html">Xilinx Netlist Format</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-icarus_ieee1364.html" class="wikilink1" title="geda-icarus_ieee1364.html">Icarus Verilog vs. IEEE1364</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-icarus_anc.html" class="wikilink1" title="geda-icarus_anc.html">Icarus Attribute Naming Conventions</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-icarus_extensions.html" class="wikilink1" title="geda-icarus_extensions.html">Icarus Verilog Extensions</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-icarus_glossary.html" class="wikilink1" title="geda-icarus_glossary.html">Icarus Verilog Glossary</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-icarus_opcodes.html" class="wikilink1" title="geda-icarus_opcodes.html">Executable Instruction Opcodes</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-icarus_vpi_within_vvp.html" class="wikilink1" title="geda-icarus_vpi_within_vvp.html">VPI_within_VVP</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-icarus_vvp_simulation.html" class="wikilink1" title="geda-icarus_vvp_simulation.html">VVP Simulation Engine</a></div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Icarus Verilog" [4334-5259] -->
+<h1><a name="gtkwave" id="gtkwave">GTKWave</a></h1>
+<div class="level1">
+<ul>
+<li class="level1"><div class="li"> <a href="http://home.nc.rr.com/gtkwave/"; class="urlextern" title="http://home.nc.rr.com/gtkwave/"; rel="nofollow">Welcome to GTKWave</a> – Now for version 3.0 (the promoted version 1.3)</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-gtkwave_mp.html" class="wikilink1" title="geda-gtkwave_mp.html">Visualization tool for VCD, LXT, and VZT files (gtkwave)</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-gtkwave_lxt2miner_mp.html" class="wikilink1" title="geda-gtkwave_lxt2miner_mp.html">Data mining of LXT2 files (lxt2miner)</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-gtkwave_lxt2vcd_mp.html" class="wikilink1" title="geda-gtkwave_lxt2vcd_mp.html">Coverts LXT2 files to VCD (lxt2vcd)</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-gtkwave_mvl2lxt_mp.html" class="wikilink1" title="geda-gtkwave_mvl2lxt_mp.html">Coverts MVLSIM AET files to LXT (mvl2lxt)</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-gtkwave_mvl2vcd_mp.html" class="wikilink1" title="geda-gtkwave_mvl2vcd_mp.html">Coverts MVLSIM AET files to VCD (mvl2vcd)</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-gtkwave_tex2vcd_mp.html" class="wikilink1" title="geda-gtkwave_tex2vcd_mp.html">Coverts TEXSIM AET files to VCD (tex2vcd)</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-gtkwave_tla2vcd_mp.html" class="wikilink1" title="geda-gtkwave_tla2vcd_mp.html">Converts TLA to VCD or LST files (tla2vcd)</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-gtkwave_vcd2lxt_mp.html" class="wikilink1" title="geda-gtkwave_vcd2lxt_mp.html">Converts VCD files to interlaced or linear LXT files (vcd2lxt)</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-gtkwave_vcd2lxt2_mp.html" class="wikilink1" title="geda-gtkwave_vcd2lxt2_mp.html">Converts VCD files to LXT2 files (vcd2lxt2)</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-gtkwave_vcd2vzt_mp.html" class="wikilink1" title="geda-gtkwave_vcd2vzt_mp.html">Converts VCD files to VZT files
+ (vcd2vzt)</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-gtkwave_vzt2vcd_mp.html" class="wikilink1" title="geda-gtkwave_vzt2vcd_mp.html">Coverts VZT files to VCD (vzt2vcd)</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-gtkwave_vztminer_mp.html" class="wikilink1" title="geda-gtkwave_vztminer_mp.html">Data mining of VZT files (vztminer)</a></div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "GTKWave" [5260-6291] -->
+<h1><a name="wcalc" id="wcalc">Wcalc</a></h1>
+<div class="level1">
+<ul>
+<li class="level1"><div class="li"> <a href="geda-wcalc_readme.html" class="wikilink1" title="geda-wcalc_readme.html">Wcalc README</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-wcalc_mp.html" class="wikilink1" title="geda-wcalc_mp.html">Wcalc man-page</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-wcalc_stdio_mp.html" class="wikilink1" title="geda-wcalc_stdio_mp.html">stdio Wcalc man-page</a></div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Wcalc" [6292-6438] -->
+<h1><a name="mcalc" id="mcalc">mcalc</a></h1>
+<div class="level1">
+<ul>
+<li class="level1"><div class="li"> <a href="http://mcalc.sourceforge.net/"; class="urlextern" title="http://mcalc.sourceforge.net/"; rel="nofollow">Microstrip Analysis/Synthesis Calculator</a> – latest documentation from sourceforge</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-mcalc_readme.html" class="wikilink1" title="geda-mcalc_readme.html">mcalc README</a></div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "mcalc" [6439-6618] -->
+<h1><a name="covered" id="covered">covered</a></h1>
+<div class="level1">
+<ul>
+<li class="level1"><div class="li"> <a href="http://covered.sourceforge.net/user/index.html"; class="urlextern" title="http://covered.sourceforge.net/user/index.html"; rel="nofollow">covered User Manual</a> – link to latest covered documentation on sourceforge</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-covered_rv.html" class="wikilink2" title="geda-covered_rv.html">covered Report Viewer</a> – available in the Help menu of the <acronym title="Graphical User Interface">GUI</acronym> report utility</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-covered_mp.html" class="wikilink1" title="geda-covered_mp.html">covered man-page</a></div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "covered" [6619-] --></body>
+</html>
diff --git a/docs/wiki/geda-documentation.html b/docs/wiki/geda-documentation.html
new file mode 100644
index 0000000..146071f
--- /dev/null
+++ b/docs/wiki/geda-documentation.html
@@ -0,0 +1,391 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#geda_tool_suite_on-line_documentation" class="toc">gEDA Tool Suite on-line documentation</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#tutorials" class="toc">Tutorials</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#gschem_-_schematic_capture" class="toc">gschem - Schematic Capture</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#gnetlist_-_netlister" class="toc">gnetlist - Netlister</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#gsymcheck_-_symbol_checker" class="toc">gsymcheck - Symbol Checker</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#utils_-_geda_utilities" class="toc">utils - gEDA Utilities</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#examples" class="toc">Examples</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#attribute_file_format_details" class="toc">Attribute/File Format Details</a></span></div></li>
+</ul>
+</li>
+<li class="level1"><div class="li"><span class="li"><a href="#spice" class="toc">SPICE</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#ngspice" class="toc">ngspice</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#gnucap" class="toc">gnucap</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#gspiceui" class="toc">gSpiceUI</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#pcb" class="toc">PCB</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#gerbv" class="toc">gerbv</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#icarus_verilog" class="toc">Icarus Verilog</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#gtkwave" class="toc">GTKWave</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#wcalc" class="toc">Wcalc</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#mcalc" class="toc">mcalc</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#covered" class="toc">covered</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#for_document_authors" class="toc">For document authors</a></span></div></li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="geda_tool_suite_on-line_documentation" id="geda_tool_suite_on-line_documentation">gEDA Tool Suite on-line documentation</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "gEDA Tool Suite on-line documentation" [1-55] -->
+<h2><a name="tutorials" id="tutorials">Tutorials</a></h2>
+<div class="level2">
+<ul>
+<li class="level1"><div class="li"> <a href="geda-gsch2pcb_tutorial.html" class="wikilink1" title="geda-gsch2pcb_tutorial.html">gschem to pcb tutorial</a>, by Bill Wilson.</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-gschem_warmup.html" class="wikilink1" title="geda-gschem_warmup.html">gschem warmup</a>, by Bill Willson.</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-transistor_guide.html" class="wikilink1" title="geda-transistor_guide.html">gschem Symbol and PCB Element Transistor Guide</a>, by Bill Willson.</div>
+</li>
+<li class="level1"><div class="li"> <a href="http://www.delorie.com/pcb/docs/gs/gs.html"; class="urlextern" title="http://www.delorie.com/pcb/docs/gs/gs.html"; rel="nofollow">PCB tutorial</a>, by DJ Delorie. </div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-ngspice_and_gschem.html" class="wikilink1" title="geda-ngspice_and_gschem.html">ngspice and gschem</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-tragesym_tutorial.html" class="wikilink1" title="geda-tragesym_tutorial.html">tragesym tutorial</a> on how to create symbols with the tragesym script.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Tutorials" [56-511] -->
+<h2><a name="gschem_-_schematic_capture" id="gschem_-_schematic_capture">gschem - Schematic Capture</a></h2>
+<div class="level2">
+<ul>
+<li class="level1"><div class="li"> <a href="geda-gschem_ug.html" class="wikilink1" title="geda-gschem_ug.html">gschem User's Guide</a> – also in transition, please comment</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-gschem_mp.html" class="wikilink1" title="geda-gschem_mp.html">gschem man-page</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-scg.html" class="wikilink1" title="geda-scg.html">Symbol Creation Guide</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-hse_howto.html" class="wikilink1" title="geda-hse_howto.html">Hooks/Scheme Extension HOWTO</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-kig_howto.html" class="wikilink1" title="geda-kig_howto.html">Keymapping in gschem HOWTO</a></div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "gschem - Schematic Capture" [512-812] -->
+<h2><a name="gnetlist_-_netlister" id="gnetlist_-_netlister">gnetlist - Netlister</a></h2>
+<div class="level2">
+<ul>
+<li class="level1"><div class="li"> <a href="geda-gnetlist_ug.html" class="wikilink1" title="geda-gnetlist_ug.html">gnetlist User's Guide</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-gnetlist_mp.html" class="wikilink1" title="geda-gnetlist_mp.html">gnetlist man-page</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-sdb_howto.html" class="wikilink1" title="geda-sdb_howto.html">Spice netlisting (SDB) HOWTO</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-na_howto.html" class="wikilink1" title="geda-na_howto.html">net= attribute mini-HOWTO</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-ssan.html" class="wikilink1" title="geda-ssan.html">Switcap Symbols and Netlister</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-sn_readme.html" class="wikilink1" title="geda-sn_readme.html">Switcap netlister README</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-fbabgapp.html" class="wikilink1" title="geda-fbabgapp.html">Forward/Backward Annotation Between gEDA and Pads PowerPCB</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-grcsan.html" class="wikilink1" title="geda-grcsan.html">gEDA RF Cascade Symbols and Netlister</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-bom_readme.html" class="wikilink1" title="geda-bom_readme.html">Bill of Material netlister README</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-gschem2pcb_readme.html" class="wikilink1" title="geda-gschem2pcb_readme.html">gschem2pcb README</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-verilog_netlister_readme.html" class="wikilink1" title="geda-verilog_netlister_readme.html">Verilog netlister README</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-vhdl_netlister_readme.html" class="wikilink1" title="geda-vhdl_netlister_readme.html">VHDL netlister README</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-vams_netlister_readme.html" class="wikilink1" title="geda-vams_netlister_readme.html">VAMS netlister README</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-systemc_netlister_readme.html" class="wikilink1" title="geda-systemc_netlister_readme.html">SystemC netlister README</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-eagle_pcb_netlister_readme.html" class="wikilink1" title="geda-eagle_pcb_netlister_readme.html">Eagle PCB netlister README</a></div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "gnetlist - Netlister" [813-1685] -->
+<h2><a name="gsymcheck_-_symbol_checker" id="gsymcheck_-_symbol_checker">gsymcheck - Symbol Checker</a></h2>
+<div class="level2">
+<ul>
+<li class="level1"><div class="li"> <a href="geda-gsymcheck_mp.html" class="wikilink1" title="geda-gsymcheck_mp.html">gsymcheck man-page</a></div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "gsymcheck - Symbol Checker" [1686-1771] -->
+<h2><a name="utils_-_geda_utilities" id="utils_-_geda_utilities">utils - gEDA Utilities</a></h2>
+<div class="level2">
+<ul>
+<li class="level1"><div class="li"> <a href="geda-gsch2pcb_readme.html" class="wikilink1" title="geda-gsch2pcb_readme.html">gsch2pcb (gschem to PCB) README</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-gsch2pcb_tutorial.html" class="wikilink1" title="geda-gsch2pcb_tutorial.html">gsch2pcb tutorial</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-tragesym_readme.html" class="wikilink1" title="geda-tragesym_readme.html">tragesym (symbol generator) README</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-tragesym_tutorial.html" class="wikilink1" title="geda-tragesym_tutorial.html">tragesym Tutorial</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-olib_readme.html" class="wikilink1" title="geda-olib_readme.html">olib (OrCAD (TM) converter) README</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-grenum_mp.html" class="wikilink1" title="geda-grenum_mp.html">grenum man-page</a> – note</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-gattrib_readme.html" class="wikilink1" title="geda-gattrib_readme.html">gattrib README</a> – note</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "utils - gEDA Utilities" [1772-2188] -->
+<h2><a name="examples" id="examples">Examples</a></h2>
+<div class="level2">
+<ul>
+<li class="level1"><div class="li"> <a href="geda-example_hsm.html" class="wikilink1" title="geda-example_hsm.html">Hierarchical SPICE model</a> – note</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-example_usbjtag.html" class="wikilink1" title="geda-example_usbjtag.html">Example USB-based JTAG interface</a> – note</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Examples" [2189-2338] -->
+<h2><a name="attribute_file_format_details" id="attribute_file_format_details">Attribute/File Format Details</a></h2>
+<div class="level2">
+<ul>
+<li class="level1"><div class="li"> <a href="geda-master_attributes_list.html" class="wikilink1" title="geda-master_attributes_list.html">Master Attributes List</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-file_format_spec.html" class="wikilink1" title="geda-file_format_spec.html">sym/sch File Format Specification</a></div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Attribute/File Format Details" [2339-2504] -->
+<h1><a name="spice" id="spice">SPICE</a></h1>
+<div class="level1">
+<ul>
+<li class="level1"><div class="li"> <a href="http://www.gnucap.org/papers/al-davis-dissertation.pdf"; class="urlextern" title="http://www.gnucap.org/papers/al-davis-dissertation.pdf"; rel="nofollow">Implicit Mixed-Mode Simulation of VLSI Circuits</a> by Albert Tatum Davis (1991)<br/>
+ Please report if this <acronym title="Uniform Resource Locator">URL</acronym> goes dead.</div>
+</li>
+<li class="level1"><div class="li"> <a href="http://www.brorson.com/gEDA/SPICE/intro.html"; class="urlextern" title="http://www.brorson.com/gEDA/SPICE/intro.html"; rel="nofollow">Circuit Simulation using gEDA and SPICE - HOWTO</a> (<acronym title="HyperText Markup Language">HTML</acronym> version)<br/>
+ by Stuart Brorson (20 December 2004).<br/>
+ Please report if this <acronym title="Uniform Resource Locator">URL</acronym> is not the latest version.</div>
+</li>
+<li class="level1"><div class="li"> <a href="http://www.brorson.com/gEDA/HOWTO/gEDA_Spice_HOWTO-20050103.pdf"; class="urlextern" title="http://www.brorson.com/gEDA/HOWTO/gEDA_Spice_HOWTO-20050103.pdf"; rel="nofollow">Circuit Simulation using gEDA and SPICE - HOWTO</a> (<acronym title="Portable Document Format">PDF</acronym> version)<br/>
+ by Stuart Brorson ( 5 January 2005).</div>
+</li>
+</ul>
+
+<p>
+ Testing:
+</p>
+<ul>
+<li class="level1"><div class="li"> <a href="geda-csygas.html" class="wikilink1" title="geda-csygas.html">Circuit Simulation using gEDA and SPICE - HOWTO</a> – Done converting. Please comment on this conversion to a wiki-format.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "SPICE" [2505-3238] -->
+<h1><a name="ngspice" id="ngspice">ngspice</a></h1>
+<div class="level1">
+<ul>
+<li class="level1"><div class="li"> <a href="http://www-ti.informatik.uni-tuebingen.de/~bernauer/lehre/ti-1-0506/spice/ngspice.pdf"; class="urlextern" title="http://www-ti.informatik.uni-tuebingen.de/~bernauer/lehre/ti-1-0506/spice/ngspice.pdf"; rel="nofollow">NGSPICE User Manual</a> – describes ngspice-rework-17, Draft Version 0.2<br/>
+ Please report if this <acronym title="Uniform Resource Locator">URL</acronym> is not the appropriated version, or if it goes dead.</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-ngspice_mp.html" class="wikilink1" title="geda-ngspice_mp.html">ngspice man-page</a> – note</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-ngnutmeg_mp.html" class="wikilink1" title="geda-ngnutmeg_mp.html">ngnutmeg man-page</a> – note</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-ngsconvert_mp.html" class="wikilink1" title="geda-ngsconvert_mp.html">ngsconvert man-page</a> – note</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "ngspice" [3239-3661] -->
+<h1><a name="gnucap" id="gnucap">gnucap</a></h1>
+<div class="level1">
+<ul>
+<li class="level1"><div class="li"> <a href="http://www.gnucap.org/gnucap-man.pdf"; class="urlextern" title="http://www.gnucap.org/gnucap-man.pdf"; rel="nofollow">The Gnu Circuit Analysis Package Users manual</a> – January 21,2004 version</div>
+</li>
+<li class="level1"><div class="li"> <a href="http://www.gnucap.org/papers/gnucap-model-compiler.pdf"; class="urlextern" title="http://www.gnucap.org/papers/gnucap-model-compiler.pdf"; rel="nofollow">The Gnucap Model Compiler</a></div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "gnucap" [3662-3890] -->
+<h1><a name="gspiceui" id="gspiceui">gSpiceUI</a></h1>
+<div class="level1">
+<ul>
+<li class="level1"><div class="li"> Please look inside the gSpiceUI tarball for documentation</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "gSpiceUI" [3891-3976] -->
+<h1><a name="pcb" id="pcb">PCB</a></h1>
+<div class="level1">
+<ul>
+<li class="level1"><div class="li"> The pcb <acronym title="Frequently Asked Questions">FAQ</acronym>: <a href="geda-faq-pcb.html" class="wikilink1" title="geda-faq-pcb.html">faq-pcb</a></div>
+</li>
+<li class="level1"><div class="li"> The official <a href="http://pcb.gpleda.org/manual.html"; class="urlextern" title="http://pcb.gpleda.org/manual.html"; rel="nofollow">manual of pcb</a></div>
+</li>
+<li class="level1"><div class="li"> A very detailed <a href="http://www.brorson.com/gEDA/land_patterns_20070818.pdf"; class="urlextern" title="http://www.brorson.com/gEDA/land_patterns_20070818.pdf"; rel="nofollow">manual on footprint creation</a> by Stephen Meier and Stuart Brorson. It also covers most of the syntax of the *.pcb format. The document refers to the 2007 version of pcb.</div>
+</li>
+<li class="level1"><div class="li"> The <a href="geda-pcb_mp.html" class="wikilink1" title="geda-pcb_mp.html">man-page of pcb</a></div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "PCB" [3977-4381] -->
+<h1><a name="gerbv" id="gerbv">gerbv</a></h1>
+<div class="level1">
+<ul>
+<li class="level1"><div class="li"> <a href="geda-gerbv_mp.html" class="wikilink1" title="geda-gerbv_mp.html">gerbv man-page</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-gerbv_pnp_readme.html" class="wikilink1" title="geda-gerbv_pnp_readme.html">Searching for Parts and marking them on screen (in gerbv)</a></div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "gerbv" [4382-4527] -->
+<h1><a name="icarus_verilog" id="icarus_verilog">Icarus Verilog</a></h1>
+<div class="level1">
+<ul>
+<li class="level1"><div class="li"> <a href="geda-icarus_quick_start.html" class="wikilink1" title="geda-icarus_quick_start.html">Getting Started with Icarus Verilog</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="http://www.rowetel.com/blog/?p=13"; class="urlextern" title="http://www.rowetel.com/blog/?p=13"; rel="nofollow">Icarus Verilog Mini How To</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-icarus_mp.html" class="wikilink1" title="geda-icarus_mp.html">Icarus Verilog compiler man-page</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-icarus_vpi_mp.html" class="wikilink1" title="geda-icarus_vpi_mp.html">Compile front end for VPI modules man-page</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-icarus_vvp_runtime.html" class="wikilink1" title="geda-icarus_vvp_runtime.html">Icarus Verilog vvp runtime engine man-page</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-icarus_readme.html" class="wikilink1" title="geda-icarus_readme.html">The Icarus Verilog Compilation System</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-igarus_fpga_lcg.html" class="wikilink1" title="geda-igarus_fpga_lcg.html">FPGA Loadable Code Generator for Icarus Verilog</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-icarus_xilinx_hints.html" class="wikilink1" title="geda-icarus_xilinx_hints.html">Xilinx Hints</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-icarus_xnf.html" class="wikilink1" title="geda-icarus_xnf.html">Xilinx Netlist Format</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-icarus_ieee1364.html" class="wikilink1" title="geda-icarus_ieee1364.html">Icarus Verilog vs. IEEE1364</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-icarus_anc.html" class="wikilink1" title="geda-icarus_anc.html">Icarus Attribute Naming Conventions</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-icarus_extensions.html" class="wikilink1" title="geda-icarus_extensions.html">Icarus Verilog Extensions</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-icarus_glossary.html" class="wikilink1" title="geda-icarus_glossary.html">Icarus Verilog Glossary</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-icarus_opcodes.html" class="wikilink1" title="geda-icarus_opcodes.html">Executable Instruction Opcodes</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-icarus_vpi_within_vvp.html" class="wikilink1" title="geda-icarus_vpi_within_vvp.html">VPI_within_VVP</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-icarus_vvp_simulation.html" class="wikilink1" title="geda-icarus_vvp_simulation.html">VVP Simulation Engine</a></div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Icarus Verilog" [4528-5522] -->
+<h1><a name="gtkwave" id="gtkwave">GTKWave</a></h1>
+<div class="level1">
+<ul>
+<li class="level1"><div class="li"> <a href="http://home.nc.rr.com/gtkwave/"; class="urlextern" title="http://home.nc.rr.com/gtkwave/"; rel="nofollow">Welcome to GTKWave</a> – Now for version 3.0 (the promoted version 1.3)</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-gtkwave_mp.html" class="wikilink1" title="geda-gtkwave_mp.html">Visualization tool for VCD, LXT, and VZT files (gtkwave)</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-gtkwave_lxt2miner_mp.html" class="wikilink1" title="geda-gtkwave_lxt2miner_mp.html">Data mining of LXT2 files (lxt2miner)</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-gtkwave_lxt2vcd_mp.html" class="wikilink1" title="geda-gtkwave_lxt2vcd_mp.html">Coverts LXT2 files to VCD (lxt2vcd)</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-gtkwave_mvl2lxt_mp.html" class="wikilink1" title="geda-gtkwave_mvl2lxt_mp.html">Coverts MVLSIM AET files to LXT (mvl2lxt)</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-gtkwave_mvl2vcd_mp.html" class="wikilink1" title="geda-gtkwave_mvl2vcd_mp.html">Coverts MVLSIM AET files to VCD (mvl2vcd)</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-gtkwave_tex2vcd_mp.html" class="wikilink1" title="geda-gtkwave_tex2vcd_mp.html">Coverts TEXSIM AET files to VCD (tex2vcd)</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-gtkwave_tla2vcd_mp.html" class="wikilink1" title="geda-gtkwave_tla2vcd_mp.html">Converts TLA to VCD or LST files (tla2vcd)</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-gtkwave_vcd2lxt_mp.html" class="wikilink1" title="geda-gtkwave_vcd2lxt_mp.html">Converts VCD files to interlaced or linear LXT files (vcd2lxt)</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-gtkwave_vcd2lxt2_mp.html" class="wikilink1" title="geda-gtkwave_vcd2lxt2_mp.html">Converts VCD files to LXT2 files (vcd2lxt2)</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-gtkwave_vcd2vzt_mp.html" class="wikilink1" title="geda-gtkwave_vcd2vzt_mp.html">Converts VCD files to VZT files
+ (vcd2vzt)</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-gtkwave_vzt2vcd_mp.html" class="wikilink1" title="geda-gtkwave_vzt2vcd_mp.html">Coverts VZT files to VCD (vzt2vcd)</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-gtkwave_vztminer_mp.html" class="wikilink1" title="geda-gtkwave_vztminer_mp.html">Data mining of VZT files (vztminer)</a></div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "GTKWave" [5523-6554] -->
+<h1><a name="wcalc" id="wcalc">Wcalc</a></h1>
+<div class="level1">
+<ul>
+<li class="level1"><div class="li"> <a href="geda-wcalc_readme.html" class="wikilink1" title="geda-wcalc_readme.html">Wcalc README</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-wcalc_mp.html" class="wikilink1" title="geda-wcalc_mp.html">Wcalc man-page</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-wcalc_stdio_mp.html" class="wikilink1" title="geda-wcalc_stdio_mp.html">stdio Wcalc man-page</a></div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Wcalc" [6555-6701] -->
+<h1><a name="mcalc" id="mcalc">mcalc</a></h1>
+<div class="level1">
+<ul>
+<li class="level1"><div class="li"> <a href="http://mcalc.sourceforge.net/"; class="urlextern" title="http://mcalc.sourceforge.net/"; rel="nofollow">Microstrip Analysis/Synthesis Calculator</a> – latest documentation from sourceforge</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-mcalc_readme.html" class="wikilink1" title="geda-mcalc_readme.html">mcalc README</a></div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "mcalc" [6702-6881] -->
+<h1><a name="covered" id="covered">covered</a></h1>
+<div class="level1">
+<ul>
+<li class="level1"><div class="li"> <a href="http://covered.sourceforge.net/user/index.html"; class="urlextern" title="http://covered.sourceforge.net/user/index.html"; rel="nofollow">covered User Manual</a> – link to latest covered documentation on sourceforge</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-covered_rv.html" class="wikilink2" title="geda-covered_rv.html">covered Report Viewer</a> – available in the Help menu of the <acronym title="Graphical User Interface">GUI</acronym> report utility</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-covered_mp.html" class="wikilink1" title="geda-covered_mp.html">covered man-page</a></div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "covered" [6882-7179] -->
+<h1><a name="for_document_authors" id="for_document_authors">For document authors</a></h1>
+<div class="level1">
+
+<p>
+New features are available for document authors:
+</p>
+<ul>
+<li class="level1"><div class="li"> <a href="geda-syntax_features.html" class="wikilink1" title="geda-syntax_features.html">Syntax features</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-installed_plugins.html" class="wikilink1" title="geda-installed_plugins.html">Installed plugins</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-style_guide.html" class="wikilink1" title="geda-style_guide.html">Style Guide</a> – A work in progress, please contribute</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "For document authors" [7180-] --></body>
+</html>
diff --git a/docs/wiki/geda-eagle_pcb_netlister_readme.html b/docs/wiki/geda-eagle_pcb_netlister_readme.html
new file mode 100644
index 0000000..95a3fdc
--- /dev/null
+++ b/docs/wiki/geda-eagle_pcb_netlister_readme.html
@@ -0,0 +1,43 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="eagle_pcb_netlister_readme" id="eagle_pcb_netlister_readme">Eagle PCB netlister README</a></h1>
+<div class="level1">
+<pre class="code">Basic information about the Eagle PCB backend and sch2eaglepos.sh
+
+gnet-eagle.scm
+
+The script uses the component's package, footprint, value, and (if no
+value) device attributes, as well as the netlist, to generate an Eagle
+script that will add and connect all components. It also introduces a
+"lib" attribute, which specifies the Eagle library where the footprint
+can be found...if a "lib" attribute is not set for a component, then
+the library defaults to "smd-ipc" (the default Eagle surface mount library).
+
+sch2eaglepos.sh
+
+I am also including a simple shell script that I wrote which has saved
+me hours by extracting the relative locations of the parts from a
+gschem schematic, and generating an Eagle script to place the
+components in the same relative locations on the layout. By default
+all packages are piled on top of each other, and with a large design
+it takes a long time to sort out which cap bypasses which IC, etc.
+
+</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-example_hsm.html b/docs/wiki/geda-example_hsm.html
new file mode 100644
index 0000000..9068295
--- /dev/null
+++ b/docs/wiki/geda-example_hsm.html
@@ -0,0 +1,135 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="hierarchical_spice_model" id="hierarchical_spice_model">Hierarchical SPICE model</a></h1>
+<div class="level1">
+
+<p>
+If you installed the gEDA Tool Suite from the distribution CD-ROM, then you should have this example of a hierarchical analog RF SPICE model in the:<br/>
+ <strong><code>{source_install_path}geda-sources/gedagaf/geda-examples-20060123/RF_Amp</code></strong> <br/>
+ directory.
+</p>
+<pre class="code">This README created 3.31.2003
+
+--------------------- Contents of directories -----------------------
+
+This directory holds the schematics and associated materials for a
+SPICE model of Agilent's MSA-2643 bipolar amp. The model was obtained
+from Agilent's datasheet 5980-2396E. The directory structure is as
+follows:
+
+RF_Amp (base directory)
+
+MSA-2643.sch -- schematic of stuff inside device package (as shown in
+p. 7 of datasheet. Note that I have not included the transmission
+lines in this schematic because no value of Z was included in the data
+sheet. (Yes, it's probably 50 ohms, but including them was a
+sideshow compared to my main intent: build a hierarchical model of an
+RF circuit.)
+MSA-2643.cir -- netlisted circuit ready for SPICE simulation.
+
+Q1.sch -- schematic model of Q1 MSA-26 transistor shown on p. 8 of datasheet.
+Q1.cir -- netlisted circuit holding .SUBCKT model of Q1.
+
+Q2.sch -- schematic model of Q2 MSA-26 transistor shown on p. 8 of datasheet.
+Q2.cir -- netlisted circuit holding .SUBCKT model of Q2.
+
+README -- this file.
+
+Simulation.cmd -- a file holding SPICE analysis commands which is read
+at simulation time by the SPICE simulator.
+
+5980-2396E.pdf -- Agilent datasheet about the MSA-2643.
+
+
+./model/
+
+BJTM1_Q1.mod -- text-based SPICE model of BJT1 used in Q1 .SUBCKT
+DiodeM1_Q1.mod -- text-based SPICE model of diode M1 used in Q1 .SUBCKT
+DiodeM2_Q1.mod -- SPICE model of diode M2 used in Q1 .SUBCKT
+DiodeM3_Q1.mod -- SPICE model of diode M3 used in Q1 .SUBCKT
+(similar files for Q2 models. . . .)
+These models were obtained from parameters give in p. 8 of the datasheet.
+
+./sym/
+
+BJT_Model.sym
+spice-subcircuit-IO-1.sym
+spice-subcircuit-LL-1.sym
+Q_Model.sym -- symbol pointing to lower level models placed on upper
+level schematic.
+
+------------ Usage of hierarchical spice models ---------------------
+This project exemplifies construction of a hierarchical SPICE
+simulation using gEDA. The project is built in the following way:
+
+1. Use a text editor to create .mod files containing SPICE models of
+the transistors and diodes on p. 8 of the datasheet.
+
+2. Create Q1 and Q2 transistor model schematics using gschem. Place
+the .SUBCKT SPICE block on the schematic to alert the netlister that
+the schematic is a lower level .SUBCKT for incorporation into other
+schematics. Place spice-IO pads on the schematic to instantiate the
+IOs. Make sure to number the spice-IO pads in the same order as you
+wish them to appear in the .SUBCKT line in the .cir.
+
+3. Generate the .SUBCKT netlist by saying:
+
+gnetlist -g spice-sdb -o Q1.cir Q1.sch
+gnetlist -g spice-sdb -o Q2.cir Q2.sch
+
+4. Create a symbol for Q1.cir and Q2.cir which will be dropped onto
+the higher lever schematic. Name the symbol Q_Model.sym. Set the
+symbol "DEVICE" attribute = NPN_TRANSISTOR_subcircuit. This causes
+the netlister to use "write-default-component" to write out the SPICE
+line for the component. Make sure that the "REFDES" attribute is X?
+and not Q? -- this enables the .SUBCKT file to be attached to the
+device.
+
+5. Create the higher layer schematic MSA-2643.sch. Place
+two copies of Q_Model.sym onto the schematic, corresponding to Q1 and
+Q2. Make Q1 point to its model by setting the following attributes:
+
+model-name: Q1_MSA26F
+file: Q1.cir
+
+Do the same for Q2.
+
+6. Create the rest of the higher layer schematic the usual way. Make
+sure to place a spice-include block on the schematic and point it to
+"Simulation.cmd". Place any analysis commands (e.g. .DC, .AC, .TRAN,
+etc.) into the file "Simulation.cmd".
+
+7. Netlist the higher layer design:
+
+gnetlist -g spice-sdb -o MSA-2643.cir MSA-2643.sch
+
+8. The circuit may be simulated by any desired SPICE simulation
+and analysis package, e.g. LTSpice.
+
+-------------------- Contact ----------------------------
+Documentation and other materials relevant to SPICE simulation under
+gEDA lives at http://www.brorson.com/gEDA/SPICE
+
+For inquiries or bug reports, please contact me:
+
+Stuart Brorson
+mailto:sdb@xxxxxxxxxx
+</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-example_usbjtag.html b/docs/wiki/geda-example_usbjtag.html
new file mode 100644
index 0000000..e1ff867
--- /dev/null
+++ b/docs/wiki/geda-example_usbjtag.html
@@ -0,0 +1,76 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="example_usb-based_jtag_interface" id="example_usb-based_jtag_interface">Example USB-based JTAG interface</a></h1>
+<div class="level1">
+
+<p>
+If you installed the gEDA Tool Suite from the distribution CD-ROM, then you should have this example of a USB-based JTAG interface in the:<br/>
+ <strong><code>{source-code_installation_path}geda-sources/gedagaf/geda-examples-20060123/gTAG</code></strong> <br/>
+ directory.
+</p>
+<pre class="code"> gTAG - USB to JTAG interface
+ ============================
+
+This is the README file for the schematic of gTAG.
+
+Short description
+-----------------
+gTAG is an interface to connect your USB port of computer to talk
+to your circuits which talks JTAG.
+
+Copyright
+---------
+These schematics is (C) by Stefan Petersen (spe@xxxxxxxxxxxxxx) and
+released under GPL (see the attached file COPYING). GPL is mainly
+written for software, ie intellectual property in electronic form.
+By making this schematic an intellectual property in electronic
+form gTAG schematics can be covered by GPL.
+
+How?
+----
+These schematics are made with gschem and netlists are then generated
+with gnetlist. Both gschem and gnetlist are part of gEDA
+(http://www.geda.seul.org/).
+
+Files
+-----
+The distribution of the schematics of gTAG should consist of:
+* README - this file.
+* COPYING - GPL copyright notice.
+* crdist.sh - shell script used to generate the tar.gz.
+* ChangeLog - tries to scribble down what has changed between versions.
+* Four component symbols:
+ - 7414-1.sym - Original 7414 from gschem without power attributes.
+ - max882.sym - 5-to-3.3 V converter.
+ - cy7c64603-52nc.sym - USB microcontroller from Cypress.
+ - sn75240pw.sym - Surge supressor for USB
+ - copyleft.sym - Symbol with GPL text for all schematics.
+* Five schematics with four symbols:
+ - gTAG.sch.sch - Toplevel schematic for gTAG
+ - gTAG-jtagio.[sym/sch]
+ - gTAG-ucont.[sym/sch]
+ - gTAG-consio.[sym/sch]
+ - gTAG-psu.[sym/sch]
+* gEDA rc-files for this project:
+ - commonrc - contains common declarations for both gschem and gnetlist
+ - gnetlistrc - gnetlist specific and and calls commonrc
+ - gschemrc - gschem specific and and calls commonrc
+</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-experiences.html b/docs/wiki/geda-experiences.html
new file mode 100644
index 0000000..45d8583
--- /dev/null
+++ b/docs/wiki/geda-experiences.html
@@ -0,0 +1,154 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="this_page_should_include_user_experiences_with_the_geda_suite" id="this_page_should_include_user_experiences_with_the_geda_suite">This page should include user experiences with the gEDA suite.</a></h1>
+<div class="level1">
+
+<p>
+Hello!
+</p>
+
+<p>
+My name is Paul Csanyi. I am a technics teacher in an elementary school.
+</p>
+
+<p>
+I use mainly Debian GNU/Linux operating system. I have installed the gEDA suite on my system.
+</p>
+
+<p>
+I am a newbe to the electronics and to the gEDA tools, but the electronics is so interesting theme to me so I decide to study gEDA tools and use it for making some simple projects. With these simple projects I intend to teach my pupils to fundamentals of electronics.
+</p>
+
+<p>
+I tried first the gEDA <acronym title="Graphical User Interface">GUI</acronym>, but then I red that it is better to use gEDA from the command line, so I did so.
+</p>
+
+<p>
+I have tried several times gEDA tools to make some simple projects. Up to the present I learn how to use gschem tool very easily. I made schematics easily.
+</p>
+
+<p>
+But then I need a symbol that I canâ??t find in gschem library, so I decide to make it. I follow the tutorial <a href="http://geda.seul.org/wiki/geda:tragesym_tutorial"; class="urlextern" title="http://geda.seul.org/wiki/geda:tragesym_tutorial"; rel="nofollow">http://geda.seul.org/wiki/geda:tragesym_tutorial</a> and ask some questions on the mailing list geda-user <a href="http://www.seul.org/cgi-bin/mailman/listinfo/geda-user"; class="urlextern" title="http://www.seul.org/cgi-bin/mailman/listinfo/geda-user"; rel="nofollow">http://www.seul.org/cgi-bin/mailman/listinfo/geda-user</a>.
+</p>
+
+<p>
+Here in this Wiki I want to share some of mine experiences with the gEDA suite. I want to share some addons to the tragesym tutorial.
+</p>
+
+<p>
+If these thoughts are specific for the Debian system, like the place of the tragesym_template.gz file, then I shall write a note of this.
+</p>
+
+<p>
+I made a symbol for the 36-pin Centronics connector.
+</p>
+
+<p>
+From the â??Tragesym tutorialâ??:
+</p>
+
+<p>
+<strong>Step1: Open a tragesym template file</strong>
+</p>
+<ul>
+<li class="level1"><div class="li"> open xterm window: eg.: urxvt</div>
+</li>
+<li class="level1"><div class="li"> cp /usr/share/doc/geda-doc/wiki/_media/tragesym_template.gz ~/gEDA/gaf/ <br/>
+</div>
+</li>
+</ul>
+
+<p>
+<em class="u">Note: This is Debian specific.</em>
+</p>
+<ul>
+<li class="level1"><div class="li"> cd gEDA/gaf/</div>
+</li>
+<li class="level1"><div class="li"> gzip -d tragesym_template.gz</div>
+</li>
+<li class="level1"><div class="li"> Open in OpenOffice the tragesym_template file. I get OpenOffice Calc with opened file. â??Set the type, style and position column to the most common value." I have saved this <strong>tragesym_template</strong> file for the future use.</div>
+</li>
+</ul>
+
+<p>
+ <strong>Step2: Download the part data sheet and find the pin list</strong>
+</p>
+
+<p>
+<strong>Step3: Copy the pin list into an editor and prepare it</strong>
+</p>
+<ul>
+<li class="level1"><div class="li">I have tried Midnight Commander as editor, but XEmacs is much better for this. I make Tabs between columns. From XEmacs I copy the lines into OpenOffice Calc.</div>
+</li>
+</ul>
+
+<p>
+ <strong>Step4: Insert all missing data into the spreadsheet</strong>
+</p>
+<ul>
+<li class="level1"><div class="li">In OpenOffice Calc I inserted all missing data. The label of the Pin 36 is â??IN SELâ?? and have a negation overbar, so I write in the approppriate column: \_IN\ SEL\_ Note that here is a space between â??INâ?? and â??SELâ??. Maybe it is trivial, but if one have a space in the label this works.</div>
+</li>
+</ul>
+
+<p>
+ <strong>Step5: Export the spreadsheet into a tab seperated text file</strong>
+</p>
+<ul>
+<li class="level1"><div class="li">In OpenOffice I did File / Save As / Filename: tragesym_template-for_36-pin_centronics_connector / Filetype: Structural text (CSV) (.csv) / Filter setup: on / Save / Text boundary: empty</div>
+</li>
+</ul>
+
+<p>
+ <strong>Step6: execute tragesym and create the symbol</strong>
+</p>
+<ul>
+<li class="level1"><div class="li">tragesym tragesym_template-for_36-pin_centronics_connector 36-pin-centronics.sch</div>
+</li>
+</ul>
+
+<p>
+ <strong>Step7: check the result with gschem and do some artwork</strong>
+</p>
+<ul>
+<li class="level1"><div class="li">â??Now we have a complete symbol."</div>
+</li>
+<li class="level1"><div class="li">â??You can copy the symbol to your local symbol library e.g. /usr/local/share/gEDA/sym/local/ and use it." <br/>
+</div>
+</li>
+</ul>
+
+<p>
+cp 36-pin_centronics.sch /home/username/gEDA/gaf/gschem-sym/connectors/36-pin_centronics.sym
+</p>
+
+<p>
+This symbol can be viewed here: <br/>
+ <a href="http://www.mediamax.com/paul_csanyi/Hosted/gschem_schems/36-pin-centronics.sym"; class="urlextern" title="http://www.mediamax.com/paul_csanyi/Hosted/gschem_schems/36-pin-centronics.sym"; rel="nofollow">http://www.mediamax.com/paul_csanyi/Hosted/gschem_schems/36-pin-centronics.sym</a>
+</p>
+
+<p>
+In this symbol I put the footprint: â??SUBD_FEMALE_LAY 25â?? but this is not the approppriate footprint for the 36-pin Centronics connector. I tried to find footprint for the 36-pin Centronics connector here: <a href="http://www.gedasymbols.org/"; class="urlextern" title="http://www.gedasymbols.org/"; rel="nofollow">http://www.gedasymbols.org/</a>, but with no success.
+</p>
+
+<p>
+I think I gone to make one 36-pin Centronics footprint soon, using â??PCB Footprint Guideâ?? here:<br/>
+ <a href="http://geda.seul.org/wiki/geda:pcb_footprints"; class="urlextern" title="http://geda.seul.org/wiki/geda:pcb_footprints"; rel="nofollow">http://geda.seul.org/wiki/geda:pcb_footprints</a>. <img src="images/smileys/icon_smile.gif" align="middle" alt=":-)" />
+</p>
+
+</div>
+<!-- SECTION "This page should include user experiences with the gEDA suite." [24-] --></body>
+</html>
diff --git a/docs/wiki/geda-faq-attribs.fr.html b/docs/wiki/geda-faq-attribs.fr.html
new file mode 100644
index 0000000..4df4505
--- /dev/null
+++ b/docs/wiki/geda-faq-attribs.fr.html
@@ -0,0 +1,240 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#generation_de_bom_bill_of_materials" class="toc">Génération de BOM (Bill Of Materials)</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#j_ai_cree_un_nouveau_dessin._comment_je_cree_une_bom" class="toc">J'ai créé un nouveau dessin. Comment je crée une BOM?</a></span></div></li>
+</ul>
+</li>
+<li class="level1"><div class="li"><span class="li"><a href="#drc" class="toc">DRC</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#comment_je_controle_mes_schemas" class="toc">Comment je contrôle mes schémas?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#comment_je_peux_voir_la_sortie_de_drc_a_l_ecran_sans_l_ecrire_dans_un_fichier" class="toc">Comment je peux voir la sortie de DRC à l'écran, sans l'écrire dans un fichier?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#je_veux_desactiver_quelque_uns_des_controles_de_drc_du_schema._comment_faire" class="toc">Je veux désactiver quelque uns des contrôles de DRC du schéma. Comment faire?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#puis-je_inclure_le_controle_de_drc_dans_un_makefile_et_stopper_lorsque_des_erreurs_ou_des_avertissements_sont_trouves" class="toc">Puis-je inclure le contrôle de DRC dans un Makefile et stopper lorsque des erreurs ou des avertissements sont trouvés?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#il_y_a_quelques_avertissements_sur_mon_schema_que_je_connais._puis-je_les_ignorer_dans_la_return_value" class="toc">Il y a quelques avertissements sur mon schéma que je connais. Puis-je les ignorer dans la return value?</a></span></div></li>
+</ul>
+</li>
+<li class="level1"><div class="li"><span class="li"><a href="#gestion_d_attribut" class="toc">Gestion d'attribut</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#au_secours_mon_schema_a_des_centaines_de_composants_et_c_est_penible_d_utiliser_gschem_pour_attacher_tous_mes_attributs" class="toc">Au secours! Mon schéma a des centaines de composants et c'est pénible d'utiliser gschem pour attacher tous mes attributs!</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#comment_savoir_que_nom_d_empreinte_utiliser_pour_le_placement_avec_pcb" class="toc">Comment savoir que nom d'empreinte utiliser pour le placement avec PCB?</a></span></div></li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="generation_de_bom_bill_of_materials" id="generation_de_bom_bill_of_materials">Génération de BOM (Bill Of Materials)</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "Génération de BOM (Bill Of Materials)" [1-55] -->
+<h2><a name="j_ai_cree_un_nouveau_dessin._comment_je_cree_une_bom" id="j_ai_cree_un_nouveau_dessin._comment_je_cree_une_bom">J'ai créé un nouveau dessin. Comment je crée une BOM?</a></h2>
+<div class="level2">
+
+<p>
+Il existe plusieurs manières dâ??exporter une BOM depuis votre dessin car il existe des extensions de gEDA. En fait, il existe 5 ou 6 interfaces différentes à gnetlist qui vous permet dâ??exporter une BOM. Câ??est la raison pour laquelle, il est facile pour le débutant dâ??être perturbé sur lâ??approche à utiliser. Une raison, bonne simple et raisonnablemant complète est celle-ci:
+</p>
+<ul>
+<li class="level1"><div class="li"> Créer un fichier appelé «·attribs·» dans votre répertoire de projet. Dans ce fichier, placez chaque attribut dont vous voulez exporter les valeurs sur une ligne séparée. Vous avez un exemple ici:<pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">value
+Mfr
+Mfr_PN
+Vendor
+Vendor_PN</font></pre></div>
+</li>
+<li class="level1"><div class="li"> Netlistez votre schéma en utilisant la commande suivante:<br/>
+ <br/>
+ <code>gnetlist -v -g bom2 -o MyDesign.bom MyDesign.sch</code> <br/>
+ <br/>
+ Notez que le drapeau <strong><code>-v</code></strong> fournira une sortie bavarde, vous indiquant ce qui entre dans gnetlist lors de son lancement. Cela peut être utile si vous avez besoin de diagnostiquer un problème avec le netlisting.</div>
+</li>
+<li class="level1"><div class="li"> Avec cette commande, gnetlist sauvegardera une BOM dans le ficheir «·MyDesign.bom·». Les éléments de la BOM seront séparés en utilisant un caractère «·:·» (deux points). Vous pouvez alors lire ce fichier avec un tableur. Assurez-vous dâ??importer la BOM comme un fichier .csv et spécifiez le caractère «·:·» comme séparateur.</div>
+</li>
+</ul>
+
+<p>
+ Plusieurs autres méthodes pour créer des BOM existent. Peut-être que dâ??autres geda-users posteront leur méthode favorite ici?!?!?
+</p>
+
+</div>
+<!-- SECTION "J'ai créé un nouveau dessin. Comment je crée une BOM?" [56-1593] -->
+<h1><a name="drc" id="drc">DRC</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "DRC" [1594-1611] -->
+<h2><a name="comment_je_controle_mes_schemas" id="comment_je_controle_mes_schemas">Comment je contrôle mes schémas?</a></h2>
+<div class="level2">
+
+<p>
+Vous pouvez contrôler votre schéma en utilisant le programme de gnetlist drc2. Il vérifiera votre schéma pour les erreurs les plus habituelles, comme la duplication des références, les broches non connectées, les slots inutilisés et bien plus.
+</p>
+
+<p>
+Lancez le programme drc2 avec la commande suivante:
+</p>
+<pre class="code">gnetlist -g drc2 -o MyDesign.drc MyDesign.sch</pre>
+
+<p>
+Avec cette commande, la sortie DRC est écrite dans le ficheir «·MyDesign.drc·». Vous pouvez alors voir ce fichier avec un éditeur de texte et visualiser les avertissements et erreurs de DRC.
+</p>
+
+</div>
+<!-- SECTION "Comment je contrôle mes schémas?" [1612-2221] -->
+<h2><a name="comment_je_peux_voir_la_sortie_de_drc_a_l_ecran_sans_l_ecrire_dans_un_fichier" id="comment_je_peux_voir_la_sortie_de_drc_a_l_ecran_sans_l_ecrire_dans_un_fichier">Comment je peux voir la sortie de DRC à l'écran, sans l'écrire dans un fichier?</a></h2>
+<div class="level2">
+
+<p>
+Lancez drc2 avec la commande suivante:
+</p>
+<pre class="code">gnetlist -g drc2 -o - MyDesign.sch</pre>
+
+<p>
+De cette manière, vous verrez la sortie DRC directement sur votre écran.
+</p>
+
+</div>
+<!-- SECTION "Comment je peux voir la sortie de DRC à l'écran, sans l'écrire dans un fichier?" [2222-2480] -->
+<h2><a name="je_veux_desactiver_quelque_uns_des_controles_de_drc_du_schema._comment_faire" id="je_veux_desactiver_quelque_uns_des_controles_de_drc_du_schema._comment_faire">Je veux désactiver quelque uns des contrôles de DRC du schéma. Comment faire?</a></h2>
+<div class="level2">
+
+<p>
+drc2 est hautement configurable. Vous devez placer quelques commandes spéciales dans un fichier et utiliser lâ??option «·-l·» de gnetlist.
+</p>
+
+<p>
+Les commandes les plus habituelles sont:
+</p>
+<ul>
+<li class="level1"><div class="li"> (define dont-check-non-numbered-parts 1) ;; Disable the non-numbered parts check</div>
+</li>
+<li class="level1"><div class="li"> (define dont-check-duplicated-references 1) ;; Disable the duplicate references check</div>
+</li>
+<li class="level1"><div class="li"> (define dont-check-one-connection-nets 1) ;; Disable the check for nets with only one connection.</div>
+</li>
+<li class="level1"><div class="li"> (define dont-check-pintypes-of-nets 1) ;; Disable the pintype check</div>
+</li>
+<li class="level1"><div class="li"> (define dont-check-not-driven-nets 1) ;; Disable the driven net check</div>
+</li>
+<li class="level1"><div class="li"> (define dont-check-unconnected-pins 1) ;; Disable the unconnected pins check</div>
+</li>
+<li class="level1"><div class="li"> (define dont-check-duplicated-slots 1) ;; Disable the duplicated slots check</div>
+</li>
+<li class="level1"><div class="li"> (define dont-check-unused-slots 1) ;; Disable the unused slots check</div>
+</li>
+<li class="level1"><div class="li"> (define dont-check-slots 1) ;; Disable slot number check</div>
+</li>
+<li class="level1"><div class="li"> (define action-unused-slots #\w) ;; Output an unused slots as a warning</div>
+</li>
+<li class="level1"><div class="li"> (define action-unused-slots #\e) ;; Output an unused slots as an error</div>
+</li>
+<li class="level1"><div class="li"> (define action-unused-slots #\c) ;; An unused slot is OK.</div>
+</li>
+<li class="level1"><div class="li"> (define case_insensitive 1) ;; Do all checks case insensitive</div>
+</li>
+</ul>
+
+<p>
+ Il y a dâ??autres commandes avancées pour modifier la matrice DRC et le type de broche qui peut piloter un net. Voyez le fichier «·gnet-drc2.scm·» avec un éditeur de texte. Au début, vous y avez la documentation de disponible.
+</p>
+
+<p>
+Copiez les lignes ci-dessus que vous voulez dans un fichier (par exemple «·drc_rules.txt·»), une par ligne etlancez le contrôleur de drc:
+</p>
+<pre class="code">gnetlist -g drc2 -l drc_rules.txt -o MyDesign.drc MyDesign.sch</pre>
+
+<p>
+Avec cette commande, la sortie de DRC est écrite dans un ficheir «·MyDesign.drc·». Vous pouvez alors visualiser ce fichier avec un éditeur de texte et voir les avertissements et les erreurs de DRC.
+</p>
+
+</div>
+<!-- SECTION "Je veux désactiver quelque uns des contrôles de DRC du schéma. Comment faire?" [2481-4415] -->
+<h2><a name="puis-je_inclure_le_controle_de_drc_dans_un_makefile_et_stopper_lorsque_des_erreurs_ou_des_avertissements_sont_trouves" id="puis-je_inclure_le_controle_de_drc_dans_un_makefile_et_stopper_lorsque_des_erreurs_ou_des_avertissements_sont_trouves">Puis-je inclure le contrôle de DRC dans un Makefile et stopper lorsque des erreurs ou des avertissements sont trouvés?</a></h2>
+<div class="level2">
+
+<p>
+Oui. drc2 renverra une erreur sâ??il y a des erreurs ou des avertissements, donc vous pouvez ajouter ce qui suit dans votre Makefile:
+</p>
+<pre class="code">$(objects).drc : $(objects).sch
+ gnetlist -g drc2 $(objects).sch -o $(objects).drc</pre>
+
+<p>
+Si vous devez simuler votre dessin, vous pouvez alors ajouter ce qui suit à votre Makefile:
+</p>
+<pre class="code">$(objects).cir : $(objects).sch $(objects).drc
+ grep -v ERROR $(objects).drc >/dev/null 2>&1
+ gnetlist -g spice-sdb $(objects).sch -o $(objects).cir</pre>
+
+<p>
+Sinon, utilisez lâ??exemple ci-dessus et adaptez-le à votre propre workflow.
+</p>
+
+</div>
+<!-- SECTION "Puis-je inclure le contrôle de DRC dans un Makefile et stopper lorsque des erreurs ou des avertissements sont trouvés?" [4416-5138] -->
+<h2><a name="il_y_a_quelques_avertissements_sur_mon_schema_que_je_connais._puis-je_les_ignorer_dans_la_return_value" id="il_y_a_quelques_avertissements_sur_mon_schema_que_je_connais._puis-je_les_ignorer_dans_la_return_value">Il y a quelques avertissements sur mon schéma que je connais. Puis-je les ignorer dans la return value?</a></h2>
+<div class="level2">
+
+<p>
+Utilisez lâ??option «·-O ignore-warnings-in-return-value·»:
+</p>
+<pre class="code">gnetlist -g drc2 -o - MyDesign.sch -O ignore-warnings-in-return-value</pre>
+
+<p>
+Faites attention! Vous allez rater tous les avertissements·!
+</p>
+
+</div>
+<!-- SECTION "Il y a quelques avertissements sur mon schéma que je connais. Puis-je les ignorer dans la return value?" [5139-5464] -->
+<h1><a name="gestion_d_attribut" id="gestion_d_attribut">Gestion d'attribut</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "Gestion d'attribut" [5465-5498] -->
+<h2><a name="au_secours_mon_schema_a_des_centaines_de_composants_et_c_est_penible_d_utiliser_gschem_pour_attacher_tous_mes_attributs" id="au_secours_mon_schema_a_des_centaines_de_composants_et_c_est_penible_d_utiliser_gschem_pour_attacher_tous_mes_attributs">Au secours! Mon schéma a des centaines de composants et c'est pénible d'utiliser gschem pour attacher tous mes attributs!</a></h2>
+<div class="level2">
+
+<p>
+Ici, la réponse est lâ??utilitaire de gEDA/gaf, «·gattrib·». Gattrib est un éditeur dâ??attribut pour gEDA. Il lit votre(s) fichier(s) .sch et crée une feuille de calcul montrant tous les composants, nets et broches en ligne, avec les attributs associés listés dans les colonnes. Gattrib vous permet dâ??ajouter, modifier ou effacer les attributs depuis lâ??extérieur de gschem puis de sauvegarder les fichiers .sch. Vous avez une capture dâ??écran:
+</p>
+
+<p>
+<a href="media/geda/faq_attrib.jpg" class="media" target="_blank" title="geda:faq_attrib.jpg"><img src="media/geda/faq_attrib.jpg" class="media" alt="" /></a>
+</p>
+
+<p>
+Notez que gattrib est la réponse actuelle du Projet gEDA à la question des symboles lourds. Ceci étant, au lieu de mettre tous les attributs (tels que les fichiers de modèle SPICE, les noms dâ??empreintes, les numéros dâ??éléments des fabricants et le reste), vous êtes encouragés à mettre cette information dans votre schéma en utilisant gattrib, où il est visible et facilement manipulable avec gattrib.
+</p>
+
+<p>
+Lors de lâ??utilisation de gattrib, assurez-vous de dâ??abord quitter gschem. Gattrib et gschem sauvegardent tous les deux le travail dans le même fichier, donc vous ne devez avoir quâ??un programme fonctionnant au même moment pour éviter les conflits. Il nâ??y a pas (encore) de mécanisme de vérouillage dans gEDA/gaf, cela reste donc de votre responsabilité.
+</p>
+
+</div>
+<!-- SECTION "Au secours! Mon schéma a des centaines de composants et c'est pénible d'utiliser gschem pour attacher tous mes attributs!" [5499-6887] -->
+<h2><a name="comment_savoir_que_nom_d_empreinte_utiliser_pour_le_placement_avec_pcb" id="comment_savoir_que_nom_d_empreinte_utiliser_pour_le_placement_avec_pcb">Comment savoir que nom d'empreinte utiliser pour le placement avec PCB?</a></h2>
+<div class="level2">
+
+<p>
+La <a href="geda-pcb_tips.fr.html#je_veux_utiliser_pcb_pour_faire_le_placement._comment_connaitre_la_valeur_a_utiliser_pour_l_attribut_d_empreinte" class="wikilink1" title="geda-pcb_tips.fr.html">réponse est ici</a>.
+</p>
+
+</div>
+<!-- SECTION "Comment savoir que nom d'empreinte utiliser pour le placement avec PCB?" [6888-] --></body>
+</html>
diff --git a/docs/wiki/geda-faq-attribs.html b/docs/wiki/geda-faq-attribs.html
new file mode 100644
index 0000000..2fcd29a
--- /dev/null
+++ b/docs/wiki/geda-faq-attribs.html
@@ -0,0 +1,284 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#bom_generation" class="toc">BOM generation</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_create_a_bill_of_materials_bom" class="toc">How do I create a bill of materials (BOM)?</a></span></div></li>
+</ul>
+</li>
+<li class="level1"><div class="li"><span class="li"><a href="#design_rule_check_drc" class="toc">Design Rule Check (DRC)</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_check_my_schematics" class="toc">How do I check my schematics?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_see_the_drc_output_in_the_screen_without_writing_to_a_file" class="toc">How do I see the DRC output in the screen, without writing to a file?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#i_want_to_disable_some_of_the_schematic_drc_checks._how_can_i_do_it" class="toc">I want to disable some of the schematic DRC checks. How can I do it?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#can_i_include_the_drc_checking_into_a_makefile_and_stop_when_errors_or_warnings_are_found" class="toc">Can I include the DRC checking into a Makefile and stop when errors or warnings are found?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#there_are_some_warnings_in_my_design_i_m_aware_of._can_i_ignore_the_warnings_in_the_return_value" class="toc">There are some warnings in my design I'm aware of. Can I ignore the warnings in the return value?</a></span></div></li>
+</ul>
+</li>
+<li class="level1"><div class="li"><span class="li"><a href="#attribute_management" class="toc">Attribute management</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#help_my_design_has_hundreds_of_components_and_it_s_a_pain_to_use_gschem_to_attach_all_my_attributes" class="toc">Help! My design has hundreds of components, and it's a pain to use gschem to attach all my attributes!</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_know_what_footprint_name_to_use_for_layout_using_pcb" class="toc">How do I know what footprint name to use for layout using PCB?</a></span></div></li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="bom_generation" id="bom_generation">BOM generation</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "BOM generation" [1-32] -->
+<h2><a name="how_do_i_create_a_bill_of_materials_bom" id="how_do_i_create_a_bill_of_materials_bom">How do I create a bill of materials (BOM)?</a></h2>
+<div class="level2">
+
+<p>
+There are five different backends for <a href="http://geda.seul.org/tools/gnetlist/index.html"; class="urlextern" title="http://geda.seul.org/tools/gnetlist/index.html"; rel="nofollow">gnetlist</a> which enable you to export a BOM. Call them with -g and be sure to give the output file name with the -o option:
+</p>
+<pre class="code">
+ gnetlist -g partslist3 -o output.bom schematic.sch
+</pre>
+
+<p>
+gnetlist descends into sub sheets and list the contents of these schematics along with the parts from the top document.
+</p>
+
+<p>
+The backends bom and bom2 require read access to a local file called attribs. This file should contain the name of the attributes to be listed each in a seperate line. E.g:
+</p>
+<pre class="code">
+value
+footprint
+description
+</pre>
+
+<p>
+Each of the backends lists and sorts the parts in different ways in an ascii file. Choose the one you like best:
+</p>
+
+</div>
+
+<h4><a name="bom" id="bom">bom</a></h4>
+<div class="level4">
+
+<p>
+The bom backend needs to read an attribs file (see above). The list produced by "-g bomâ?? will contain as many lines as there are components. Columns are seperated by tab characters. Lines are not sorted.
+</p>
+
+</div>
+
+<h4><a name="bom2" id="bom2">bom2</a></h4>
+<div class="level4">
+
+<p>
+The bom2 backend also needs to read an attribs file. With "-g bom2â?? the refdeses of all components with the same value will be collected into a single line. Columns are seperated by colons. Different items in the same column are seperated by a komma character.
+</p>
+
+</div>
+
+<h4><a name="partslist1" id="partslist1">partslist1</a></h4>
+<div class="level4">
+
+<p>
+A list produced by the partlist1 backend gives a line for each and every component. Lines are sorted alphabetically by refdes. Columns are â??refdesâ??, â??deviceâ??, â??valueâ??, â??footprintâ?? and â??quantityâ??. Since every line contains just one part, the quantity is always â??1â??.
+</p>
+
+</div>
+
+<h4><a name="partslist2" id="partslist2">partslist2</a></h4>
+<div class="level4">
+
+<p>
+This backend produces output similar to partslist1. Lines are sorted by the value of the device attribute.
+</p>
+
+</div>
+
+<h4><a name="partslist3" id="partslist3">partslist3</a></h4>
+<div class="level4">
+
+<p>
+The backend partslist3 assembles all parts with the same value in a single line, very much like bom2. Lines are sorted by the value of the device attribute. The fourth column reports the number of parts in a line. Columns are seperated by the tab character, items by space.
+</p>
+
+</div>
+<!-- SECTION "How do I create a bill of materials (BOM)?" [33-2022] -->
+<h1><a name="design_rule_check_drc" id="design_rule_check_drc">Design Rule Check (DRC)</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "Design Rule Check (DRC)" [2023-2060] -->
+<h2><a name="how_do_i_check_my_schematics" id="how_do_i_check_my_schematics">How do I check my schematics?</a></h2>
+<div class="level2">
+
+<p>
+You can check your schematics using the drc2 gnetlistâ??s backend. It will check your schematics for some common errors, like duplicate references, unconnected pins, unused slots and more.
+</p>
+
+<p>
+Run the drc2 backend with the following command:
+</p>
+<pre class="code">gnetlist -g drc2 -o MyDesign.drc MyDesign.sch</pre>
+
+<p>
+With this command, the DRC output is written into the file â??MyDesign.drcâ??. You can then view this file with a text editor and see the DRC warnings and errors.
+</p>
+
+</div>
+<!-- SECTION "How do I check my schematics?" [2061-2565] -->
+<h2><a name="how_do_i_see_the_drc_output_in_the_screen_without_writing_to_a_file" id="how_do_i_see_the_drc_output_in_the_screen_without_writing_to_a_file">How do I see the DRC output in the screen, without writing to a file?</a></h2>
+<div class="level2">
+
+<p>
+Run the drc2 backend with the following command:
+</p>
+<pre class="code">gnetlist -g drc2 -o - MyDesign.sch</pre>
+
+<p>
+This way, you will see the DRC output directly in your screen.
+</p>
+
+</div>
+<!-- SECTION "How do I see the DRC output in the screen, without writing to a file?" [2566-2809] -->
+<h2><a name="i_want_to_disable_some_of_the_schematic_drc_checks._how_can_i_do_it" id="i_want_to_disable_some_of_the_schematic_drc_checks._how_can_i_do_it">I want to disable some of the schematic DRC checks. How can I do it?</a></h2>
+<div class="level2">
+
+<p>
+The drc2 backend is highly configurable. You have to put some special commands into a file and use the â??-lâ?? option of gnetlist with it.
+</p>
+
+<p>
+The most common commands are:
+</p>
+<ul>
+<li class="level1"><div class="li"> (define dont-check-non-numbered-parts 1) ;; Disable the non-numbered parts check</div>
+</li>
+<li class="level1"><div class="li"> (define dont-check-duplicated-references 1) ;; Disable the duplicate references check</div>
+</li>
+<li class="level1"><div class="li"> (define dont-check-one-connection-nets 1) ;; Disable the check for nets with only one connection.</div>
+</li>
+<li class="level1"><div class="li"> (define dont-check-pintypes-of-nets 1) ;; Disable the pintype check</div>
+</li>
+<li class="level1"><div class="li"> (define dont-check-not-driven-nets 1) ;; Disable the driven net check</div>
+</li>
+<li class="level1"><div class="li"> (define dont-check-unconnected-pins 1) ;; Disable the unconnected pins check</div>
+</li>
+<li class="level1"><div class="li"> (define dont-check-duplicated-slots 1) ;; Disable the duplicated slots check</div>
+</li>
+<li class="level1"><div class="li"> (define dont-check-unused-slots 1) ;; Disable the unused slots check</div>
+</li>
+<li class="level1"><div class="li"> (define dont-check-slots 1) ;; Disable slot number check</div>
+</li>
+<li class="level1"><div class="li"> (define action-unused-slots #\w) ;; Output an unused slots as a warning</div>
+</li>
+<li class="level1"><div class="li"> (define action-unused-slots #\e) ;; Output an unused slots as an error</div>
+</li>
+<li class="level1"><div class="li"> (define action-unused-slots #\c) ;; An unused slot is OK.</div>
+</li>
+<li class="level1"><div class="li"> (define case_insensitive 1) ;; Do all checks case insensitive</div>
+</li>
+</ul>
+
+<p>
+ There are some other advanced commands, to modify the DRC matrix and the pintype which can drive a net. See the backend file â??gnet-drc2.scmâ?? with a text editor. At the beginning there is the available documentation.
+</p>
+
+<p>
+Copy the above lines you want into a file (for example â??drc_rules.txtâ??), one per line, and run the drc checker:
+</p>
+<pre class="code">gnetlist -g drc2 -l drc_rules.txt -o MyDesign.drc MyDesign.sch</pre>
+
+<p>
+With this command, the DRC output is written into the file â??MyDesign.drcâ??. You can then view this file with a text editor and see the DRC warnings and errors.
+</p>
+
+</div>
+<!-- SECTION "I want to disable some of the schematic DRC checks. How can I do it?" [2810-4638] -->
+<h2><a name="can_i_include_the_drc_checking_into_a_makefile_and_stop_when_errors_or_warnings_are_found" id="can_i_include_the_drc_checking_into_a_makefile_and_stop_when_errors_or_warnings_are_found">Can I include the DRC checking into a Makefile and stop when errors or warnings are found?</a></h2>
+<div class="level2">
+
+<p>
+Yes. The drc2 backend will return an error if there are errors or warnings, so you can add the following to your Makefile:
+</p>
+<pre class="code">$(objects).drc : $(objects).sch
+ gnetlist -g drc2 $(objects).sch -o $(objects).drc</pre>
+
+<p>
+If you are going to simulate your design, then you can add the following to your Makefile:
+</p>
+<pre class="code">$(objects).cir : $(objects).sch $(objects).drc
+ grep -v ERROR $(objects).drc >/dev/null 2>&1
+ gnetlist -g spice-sdb $(objects).sch -o $(objects).cir</pre>
+
+<p>
+If not, please use the above example and adapt it to your own workflow.
+</p>
+
+</div>
+<!-- SECTION "Can I include the DRC checking into a Makefile and stop when errors or warnings are found?" [4639-5316] -->
+<h2><a name="there_are_some_warnings_in_my_design_i_m_aware_of._can_i_ignore_the_warnings_in_the_return_value" id="there_are_some_warnings_in_my_design_i_m_aware_of._can_i_ignore_the_warnings_in_the_return_value">There are some warnings in my design I'm aware of. Can I ignore the warnings in the return value?</a></h2>
+<div class="level2">
+
+<p>
+Use the â??-O ignore-warnings-in-return-valueâ?? option:
+</p>
+<pre class="code">gnetlist -g drc2 -o - MyDesign.sch -O ignore-warnings-in-return-value</pre>
+
+<p>
+Do this with caution! You will be missing all the warnings!
+</p>
+
+</div>
+<!-- SECTION "There are some warnings in my design I'm aware of. Can I ignore the warnings in the return value?" [5317-5628] -->
+<h1><a name="attribute_management" id="attribute_management">Attribute management</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "Attribute management" [5629-5664] -->
+<h2><a name="help_my_design_has_hundreds_of_components_and_it_s_a_pain_to_use_gschem_to_attach_all_my_attributes" id="help_my_design_has_hundreds_of_components_and_it_s_a_pain_to_use_gschem_to_attach_all_my_attributes">Help! My design has hundreds of components, and it's a pain to use gschem to attach all my attributes!</a></h2>
+<div class="level2">
+
+<p>
+The answer here is the gEDA/gaf utility â??gattribâ??. Gattrib is an attribute editor for gEDA. It reads your .sch file(s) and creates a spreadsheet showing all components, nets, and pins in rows, with the associated attributes listed in the columns. Gattrib allows you to add, modify, or delete attributes outside of gschem, and then save the .sch files back out. Hereâ??s a screenshot:
+</p>
+
+<p>
+<a href="media/geda/faq_attrib.jpg" class="media" target="_blank" title="geda:faq_attrib.jpg"><img src="media/geda/faq_attrib.jpg" class="media" alt="" /></a>
+</p>
+
+<p>
+Note that gattrib is the gEDA Projectâ??s current answer to the question of heavy symbols. That is, rather than putting all attributes (such as SPICE model files, footprint names, manufacturer part nos and the like), you are encouraged to put this information into your schematic using gattrib, where it is visible and easily manipulable with gattrib.
+</p>
+
+<p>
+When using gattrib, make sure you exit gschem first. Gattrib and gschem both save your work into the same file, so you should have only one program running at a time to avoid conflicts. There is no lockfile mechanism in gEDA/gaf (yet), so itâ??s your responsibility to avoid conflicts.
+</p>
+
+</div>
+<!-- SECTION "Help! My design has hundreds of components, and it's a pain to use gschem to attach all my attributes!" [5665-6834] -->
+<h2><a name="how_do_i_know_what_footprint_name_to_use_for_layout_using_pcb" id="how_do_i_know_what_footprint_name_to_use_for_layout_using_pcb">How do I know what footprint name to use for layout using PCB?</a></h2>
+<div class="level2">
+
+<p>
+<a href="geda-pcb_tips.html#i_want_to_use_pcb_to_do_layout._how_do_i_know_what_value_to_use_for_the_footprint_attribute" class="wikilink1" title="geda-pcb_tips.html">Answered here</a>.
+</p>
+
+</div>
+<!-- SECTION "How do I know what footprint name to use for layout using PCB?" [6835-] --></body>
+</html>
diff --git a/docs/wiki/geda-faq-gnetlist.fr.html b/docs/wiki/geda-faq-gnetlist.fr.html
new file mode 100644
index 0000000..260a236
--- /dev/null
+++ b/docs/wiki/geda-faq-gnetlist.fr.html
@@ -0,0 +1,106 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#problemes_avec_gnetlist_lors_de_l_installation_execution" class="toc">Problèmes avec gnetlist lors de l'installation/exécution</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#la_bom_de_gnetlist_ne_fonctionne_pas._d_ou_vient_le_probleme" class="toc">la bom de gnetlist ne fonctionne pas. D'où vient le problème?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#quelques_unes_des_commandes_de_gnetlist_debordent_la_pile._comment_je_resoud_ce_probleme" class="toc">Quelques unes des commandes de gnetlist débordent la pile. Comment je résoud ce problème?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#gnetlist_a_cree_une_netlist_qui_duplique_les_broches" class="toc">gnetlist a créé une netlist qui duplique les broches!?</a></span></div></li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="problemes_avec_gnetlist_lors_de_l_installation_execution" id="problemes_avec_gnetlist_lors_de_l_installation_execution">Problèmes avec gnetlist lors de l'installation/exécution</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "Problèmes avec gnetlist lors de l'installation/exécution" [1-73] -->
+<h2><a name="la_bom_de_gnetlist_ne_fonctionne_pas._d_ou_vient_le_probleme" id="la_bom_de_gnetlist_ne_fonctionne_pas._d_ou_vient_le_probleme">la bom de gnetlist ne fonctionne pas. D'où vient le problème?</a></h2>
+<div class="level2">
+
+<p>
+Si, lorsque vous lancez gnetlist comme ceci:
+</p>
+<pre class="code">gnetlist -g bom filename.sch</pre>
+
+<p>
+gnetlist vous sort un message dâ??erreur tel que:
+</p>
+<pre class="code">Loading schematic [filename.sch]
+ERROR: In procedure open-file:
+ERROR: No such file or directory: â??attribsâ??</pre>
+
+<p>
+alors vous avez besoin de créer un fichier appelé «·attribs·» dans le répertoire courant qui contient les attributss que vous voulez dans le fichier de bom. Un exemple de ce fichier ressemblerait à : <pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">refdes
+device
+value</font></pre>
+</p>
+
+</div>
+<!-- SECTION "la bom de gnetlist ne fonctionne pas. D'où vient le problème?" [74-654] -->
+<h2><a name="quelques_unes_des_commandes_de_gnetlist_debordent_la_pile._comment_je_resoud_ce_probleme" id="quelques_unes_des_commandes_de_gnetlist_debordent_la_pile._comment_je_resoud_ce_probleme">Quelques unes des commandes de gnetlist débordent la pile. Comment je résoud ce problème?</a></h2>
+<div class="level2">
+
+<p>
+Si vous avez un message tel que:
+</p>
+<pre class="code">ERROR: Stack overflow</pre>
+
+<p>
+lorsque vous faites passer des schémas de grande taille par une des commandes, ajoutez alors ce qui suit à <strong><code>~/.gEDA/gnetlistrc</code></strong> ou un <strong><code>gnetlistrc</code></strong> local (dans le répertoire de travail courant):
+</p>
+<pre class="code">(debug-options (list 'stack 200000))
+(eval-options (list 'stack 200000))</pre>
+
+<p>
+Si cela ne fonctionne pas, éditez alors la commande appropriée (habituellement appelée: gnet-backend_name.scm) et insérez les lignes précédentes en haut de ce fichier. Les commandes gnetlist peuvent être trouvées dans <strong><code>${prefix}/share/gEDA/scheme</code></strong>. Envoyez aussi un courriel à geda-dev rappelant aux développeurs de corriger ceci. Rappelez-vous que vous devez être inscrits sur geda-dev avant dâ??y envoyer des courriels.
+</p>
+
+</div>
+<!-- SECTION "Quelques unes des commandes de gnetlist débordent la pile. Comment je résoud ce problème?" [655-1562] -->
+<h2><a name="gnetlist_a_cree_une_netlist_qui_duplique_les_broches" id="gnetlist_a_cree_une_netlist_qui_duplique_les_broches">gnetlist a créé une netlist qui duplique les broches!?</a></h2>
+<div class="level2">
+
+<p>
+Il y a eu au moins un rapport sur le message suivant venant de PCB après avoir chargé une netlist créée par gnetlist:
+</p>
+<pre class="code">28: Error! Element R117 pin 2 appears multiple times in the netlist file.
+29: Error! Element C167 pin 2 appears multiple times in the netlist file.</pre>
+
+<p>
+Ce qui sâ??est produit est que gnetlist (libgeda en fait) a créé deux nets au lieu dâ??un seul. Ceci se produit lorsque vous dessinez deux nets lâ??un sur lâ??autre avec une broche connectant une intersection de deux nets se chevauchants. Notez que les nets chevauchés ne sont pas connectés ensemble. Un schéma pour la démonstration ressemble à ceci:
+</p>
+
+<p>
+<a href="media/geda/ambiguous1.png" class="media" target="_blank" title="geda:ambiguous1.png"><img src="media/geda/ambiguous1.png" class="media" alt="" /></a>
+</p>
+
+<p>
+Les développeurs débattent pour savoir si câ??est un bogue ou non de gnetlist mais jusquâ??à maintenant, assurez-vous de vos connexions de nets, spécialement celles qui impliquent des broches connectant des milieu de nets, sont correctement dessinées. Vous avez ici la manière dont la connexion ci-dessus devrait être correctement dessinée pour que netlist fasse son travail proprement:
+</p>
+
+<p>
+<a href="media/geda/ambiguous1_fixed.png" class="media" target="_blank" title="geda:ambiguous1_fixed.png"><img src="media/geda/ambiguous1_fixed.png" class="media" alt="" /></a>
+</p>
+
+</div>
+<!-- SECTION "gnetlist a créé une netlist qui duplique les broches!?" [1563-] --></body>
+</html>
diff --git a/docs/wiki/geda-faq-gnetlist.html b/docs/wiki/geda-faq-gnetlist.html
new file mode 100644
index 0000000..078f1f7
--- /dev/null
+++ b/docs/wiki/geda-faq-gnetlist.html
@@ -0,0 +1,144 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#gnetlist_build_run-time_problems" class="toc">Gnetlist build/run-time problems</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#i_get_a_parenthesis_mismatch_error_when_running_gnetlist._what_s_up" class="toc">I get a "parenthesis mismatch" error when running gnetlist. What's up?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#the_gnetlist_bom_backend_does_not_work._what_is_wrong" class="toc">The gnetlist bom backend does not work. What is wrong?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#some_gnetlist_backends_overflow_the_stack._how_do_i_solve_this" class="toc">Some gnetlist backends overflow the stack. How do I solve this?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#gnetlist_has_created_a_netlist_with_duplicate_pins" class="toc">gnetlist has created a netlist with duplicate pins!?</a></span></div></li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="gnetlist_build_run-time_problems" id="gnetlist_build_run-time_problems">Gnetlist build/run-time problems</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "Gnetlist build/run-time problems" [1-48] -->
+<h2><a name="i_get_a_parenthesis_mismatch_error_when_running_gnetlist._what_s_up" id="i_get_a_parenthesis_mismatch_error_when_running_gnetlist._what_s_up">I get a "parenthesis mismatch" error when running gnetlist. What's up?</a></h2>
+<div class="level2">
+
+<p>
+ Starting with Fedorea Core 6 and SuSE 10.2, many users have reported an error which looks like this:
+</p>
+<pre class="code">
+$gnetlist -g spice-sdb -o TwoStageAmp.cir TwoStageAmp.sch
+Command line passed = gnetlist -g spice-sdb -o TwoStageAmp.cir TwoStageAmp.sch
+gEDA/gnetlist version 20061020
+gEDA/gnetlist comes with ABSOLUTELY NO WARRANTY; see COPYING for more details.
+This is free software, and you are welcome to redistribute it under certain
+conditions; please see the COPYING file for more details.
+
+Remember to check that your schematic has no errors using the drc2 backend.
+You can do it running 'gnetlist -g drc2 your_schematic.sch -o drc_output.txt'
+and seeing the contents of the file drc_output.txt.
+
+Loading schematic [/home/nano/TwoStageAmp/TwoStageAmp.sch]
+Probably parenthesis mismatch in /usr/share/gEDA/scheme/gnet-spice-sdb.scm
+Most recently read form: (#@begin #<unspecified>)
+ERROR: Unbound variable: spice-sdb
+</pre>
+
+<p>
+Several gnetlist backends evince this problem, including spice-sdb and drc2.
+</p>
+
+<p>
+This is a bug in guile-1.8.X. The gEDA developers are working on a fix. Meanwhile, try to backrev your version of guile to 1.6.7, which is known to work flawlessly with gEDA.
+</p>
+
+</div>
+<!-- SECTION "I get a parenthesis mismatch error when running gnetlist. What's up?" [49-1315] -->
+<h2><a name="the_gnetlist_bom_backend_does_not_work._what_is_wrong" id="the_gnetlist_bom_backend_does_not_work._what_is_wrong">The gnetlist bom backend does not work. What is wrong?</a></h2>
+<div class="level2">
+
+<p>
+If when running gnetlist like this:
+</p>
+<pre class="code">gnetlist -g bom filename.sch</pre>
+
+<p>
+and gnetlist outputs an error message like:
+</p>
+<pre class="code">Loading schematic [filename.sch]
+ERROR: In procedure open-file:
+ERROR: No such file or directory: â??attribsâ??</pre>
+
+<p>
+then you need to create a file called â??attribsâ?? in the current directory which contains the attributes which you want inside the bom file. An example of this file would be: <pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">device
+value</font></pre>
+</p>
+
+<p>
+For information about BOM generation see the <a href="geda-faq-attribs.html#bom_generation" class="wikilink1" title="geda-faq-attribs.html">FAQ-attribs</a>.
+</p>
+
+</div>
+<!-- SECTION "The gnetlist bom backend does not work. What is wrong?" [1316-1932] -->
+<h2><a name="some_gnetlist_backends_overflow_the_stack._how_do_i_solve_this" id="some_gnetlist_backends_overflow_the_stack._how_do_i_solve_this">Some gnetlist backends overflow the stack. How do I solve this?</a></h2>
+<div class="level2">
+
+<p>
+If you get an error message like:
+</p>
+<pre class="code">ERROR: Stack overflow</pre>
+
+<p>
+when running certain larger sized schematics through some of the backends, then add the following to a <strong><code>~/.gEDA/gnetlistrc</code></strong> or a local <strong><code>gnetlistrc</code></strong> (in the current working directory):
+</p>
+<pre class="code">(debug-options (list 'stack 200000))
+(eval-options (list 'stack 200000))</pre>
+
+<p>
+If this does not work, then edit the appropriate backend (usually named: gnet-backend_name.scm) and put the above lines at the top of this file. The gnetlist backends can be found in <strong><code>${prefix}/share/gEDA/scheme</code></strong>. Also send an e-mail to geda-dev reminding the developers to fix this. Remember, you must subscribe to geda-dev before you post to the geda-dev e-mail list.
+</p>
+
+</div>
+<!-- SECTION "Some gnetlist backends overflow the stack. How do I solve this?" [1933-2738] -->
+<h2><a name="gnetlist_has_created_a_netlist_with_duplicate_pins" id="gnetlist_has_created_a_netlist_with_duplicate_pins">gnetlist has created a netlist with duplicate pins!?</a></h2>
+<div class="level2">
+
+<p>
+There has been at least one report of the following message coming from PCB after loading up a netlist created by gnetlist:
+</p>
+<pre class="code">28: Error! Element R117 pin 2 appears multiple times in the netlist file.
+29: Error! Element C167 pin 2 appears multiple times in the netlist file.</pre>
+
+<p>
+What has happened is gnetlist (really libgeda) created two nets instead of one. This happens when you draw two nets that cross each other and a pin connecting to the intersection of the two crossing nets. Note the cross nets are not connected together. A schematic which demonstrates this looks like this:
+</p>
+
+<p>
+<a href="media/geda/ambiguous1.png" class="media" target="_blank" title="geda:ambiguous1.png"><img src="media/geda/ambiguous1.png" class="media" alt="" /></a>
+</p>
+
+<p>
+The developers are debating whether or not this is a bug in gnetlist, but for now make sure your net connections, especially those that involve pins connecting to the middle of other nets, are explicitly drawn. Here is how the above connection should be drawn to netlist properly:
+</p>
+
+<p>
+<a href="media/geda/ambiguous1_fixed.png" class="media" target="_blank" title="geda:ambiguous1_fixed.png"><img src="media/geda/ambiguous1_fixed.png" class="media" alt="" /></a>
+</p>
+
+</div>
+<!-- SECTION "gnetlist has created a netlist with duplicate pins!?" [2739-] --></body>
+</html>
diff --git a/docs/wiki/geda-faq-gsch2pcb.fr.html b/docs/wiki/geda-faq-gsch2pcb.fr.html
new file mode 100644
index 0000000..f78f399
--- /dev/null
+++ b/docs/wiki/geda-faq-gsch2pcb.fr.html
@@ -0,0 +1,79 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#gsch2pcb" class="toc">gsch2pcb</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#ou_est_le_tutoriel_gsch2pcb" class="toc">Où est le tutoriel gsch2pcb?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#ou_puis-je_telecharger_gsch2pcb" class="toc">Où puis-je télécharger gsch2pcb?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#gsch2pcb_ne_peut_pas_trouver_quelques_uns_de_mes_empreintes_ou_genere_une_erreur._comment_puis-je_diagnostiquer_mon_probleme" class="toc">gsch2pcb ne peut pas trouver quelques uns de mes empreintes ou génère une erreur. Comment puis-je diagnostiquer mon problème?</a></span></div></li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="gsch2pcb" id="gsch2pcb">gsch2pcb</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "gsch2pcb" [1-24] -->
+<h2><a name="ou_est_le_tutoriel_gsch2pcb" id="ou_est_le_tutoriel_gsch2pcb">Où est le tutoriel gsch2pcb?</a></h2>
+<div class="level2">
+
+<p>
+ Actuellement, la meilleure information à ce propos est dans le <a href="geda-gsch2pcb_tutorial.html" class="wikilink1" title="geda-gsch2pcb_tutorial.html">tutorial</a> de Bill Wilson. <br/>
+ <span class="hilited">Cette page grossira plus tard pour contenir les réponses aux <acronym title="Frequently Asked Questions">FAQ</acronym> postées sur la liste des geda-user.</span>
+</p>
+
+<p>
+Câ??est un script de gestion pour gsch2pcb appelé sch2pcb. Vous pouvez y trouver des informations dans la section <a href="geda-pcb_tips.fr.html" class="wikilink1" title="geda-pcb_tips.fr.html">pcb_tips.fr</a> de ce wiki.
+</p>
+
+</div>
+<!-- SECTION "Où est le tutoriel gsch2pcb?" [25-436] -->
+<h2><a name="ou_puis-je_telecharger_gsch2pcb" id="ou_puis-je_telecharger_gsch2pcb">Où puis-je télécharger gsch2pcb?</a></h2>
+<div class="level2">
+
+<p>
+gsch2pcb est une part de gEDA/gaf, dans les utils. Il est normalement installé par défaut (parmi les autres) si vous installez gEDA/gaf complètement. Si vous ne lâ??avez pas installé sur votre machine vous pouvez soit télécharger le tarball utils depuis:
+</p>
+<ul>
+<li class="level1"><div class="li"> <a href="http://geda.seul.org/download.html"; class="urlextern" title="http://geda.seul.org/download.html"; rel="nofollow">http://geda.seul.org/download.html</a></div>
+</li>
+</ul>
+
+<p>
+ ou le prendre directement depuis le <acronym title="Concurrent Versions System">CVS</acronym> sur:
+</p>
+<ul>
+<li class="level1"><div class="li"> <a href="http://cvs.seul.org/viewcvs/viewcvs.cgi/eda/geda/gaf/utils/src/"; class="urlextern" title="http://cvs.seul.org/viewcvs/viewcvs.cgi/eda/geda/gaf/utils/src/"; rel="nofollow">http://cvs.seul.org/viewcvs/viewcvs.cgi/eda/geda/gaf/utils/src/</a></div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Où puis-je télécharger gsch2pcb?" [437-905] -->
+<h2><a name="gsch2pcb_ne_peut_pas_trouver_quelques_uns_de_mes_empreintes_ou_genere_une_erreur._comment_puis-je_diagnostiquer_mon_probleme" id="gsch2pcb_ne_peut_pas_trouver_quelques_uns_de_mes_empreintes_ou_genere_une_erreur._comment_puis-je_diagnostiquer_mon_probleme">gsch2pcb ne peut pas trouver quelques uns de mes empreintes ou génère une erreur. Comment puis-je diagnostiquer mon problème?</a></h2>
+<div class="level2">
+
+<p>
+Tentez de lancer gsch2pcb en mode bavard double: â??gsch2pcb -v -vâ??. Cela produira beaucoup de choses vous indiquant où gsch2pcb cherche lorsquâ??il tente de trouver les empreintes. Il vous indiquera aussi où il trouve les empreintes en cours dâ??utilisation.
+</p>
+
+</div>
+<!-- SECTION "gsch2pcb ne peut pas trouver quelques uns de mes empreintes ou génère une erreur. Comment puis-je diagnostiquer mon problème?" [906-] --></body>
+</html>
diff --git a/docs/wiki/geda-faq-gsch2pcb.html b/docs/wiki/geda-faq-gsch2pcb.html
new file mode 100644
index 0000000..8531b3b
--- /dev/null
+++ b/docs/wiki/geda-faq-gsch2pcb.html
@@ -0,0 +1,105 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#gsch2pcb" class="toc">gsch2pcb</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#where_is_the_gsch2pcb_tutorial" class="toc">Where is the gsch2pcb tutorial?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#where_can_i_download_gsch2pcb" class="toc">Where can I download gsch2pcb?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#gsch2pcb_can_t_find_some_of_my_footprints_or_errors_out._what_can_i_do_to_diagnose_my_problem" class="toc">gsch2pcb can't find some of my footprints, or errors out. What can I do to diagnose my problem?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#i_don_t_like_the_default_layer_stack_of_gschem2pcb._how_can_i_change_this" class="toc">I don't like the default layer stack of gschem2pcb. How can I change this?</a></span></div></li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="gsch2pcb" id="gsch2pcb">gsch2pcb</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "gsch2pcb" [1-24] -->
+<h2><a name="where_is_the_gsch2pcb_tutorial" id="where_is_the_gsch2pcb_tutorial">Where is the gsch2pcb tutorial?</a></h2>
+<div class="level2">
+
+<p>
+Currently, the best information about how to get started with gsch2pcb is contained in Bill Wilsonâ??s outstanding <a href="geda-gsch2pcb_tutorial.html" class="wikilink1" title="geda-gsch2pcb_tutorial.html">tutorial</a>.
+</p>
+
+<p>
+There is a wrapper script for gsch2pcb called sch2pcb. Read about it in the <a href="geda-pcb_tips.html" class="wikilink1" title="geda-pcb_tips.html">pcb_tips</a> section of this wiki.
+</p>
+
+</div>
+<!-- SECTION "Where is the gsch2pcb tutorial?" [25-336] -->
+<h2><a name="where_can_i_download_gsch2pcb" id="where_can_i_download_gsch2pcb">Where can I download gsch2pcb?</a></h2>
+<div class="level2">
+
+<p>
+gsch2pcb is part of gEDA/gaf, in the utils. It is normally installed by default (along with everything else) if you install the entirety of gEDA/gaf. If you donâ??t have it installed on your machine for some reason you can either download the utils tarball from:
+</p>
+<ul>
+<li class="level1"><div class="li"> <a href="http://geda.seul.org/download.html"; class="urlextern" title="http://geda.seul.org/download.html"; rel="nofollow">http://geda.seul.org/download.html</a></div>
+</li>
+</ul>
+
+<p>
+ or grab it directly from git at:
+</p>
+<ul>
+<li class="level1"><div class="li"> <a href="http://git.gpleda.org/?p=gaf.git;a=tree;f=utils/src;h=abf7590274f82f17c67bb1eecdc0d1da5029718a;hb=HEAD"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=tree;f=utils/src;h=abf7590274f82f17c67bb1eecdc0d1da5029718a;hb=HEAD"; rel="nofollow">http://git.gpleda.org/?p=gaf.git;a=tree;f=utils/src;h=abf7590274f82f17c67bb1eecdc0d1da5029718a;hb=HEAD</a></div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Where can I download gsch2pcb?" [337-831] -->
+<h2><a name="gsch2pcb_can_t_find_some_of_my_footprints_or_errors_out._what_can_i_do_to_diagnose_my_problem" id="gsch2pcb_can_t_find_some_of_my_footprints_or_errors_out._what_can_i_do_to_diagnose_my_problem">gsch2pcb can't find some of my footprints, or errors out. What can I do to diagnose my problem?</a></h2>
+<div class="level2">
+
+<p>
+Try running gsch2pcb in double verbose mode: â??gsch2pcb -v -vâ??. This will produce lots of spew telling you where gsch2pcb is looking while it tries to find footprints. It will also tell you where it does find the footprints it uses.
+</p>
+
+</div>
+<!-- SECTION "gsch2pcb can't find some of my footprints, or errors out. What can I do to diagnose my problem?" [832-1177] -->
+<h2><a name="i_don_t_like_the_default_layer_stack_of_gschem2pcb._how_can_i_change_this" id="i_don_t_like_the_default_layer_stack_of_gschem2pcb._how_can_i_change_this">I don't like the default layer stack of gschem2pcb. How can I change this?</a></h2>
+<div class="level2">
+
+<p>
+Edit $INSTALLDIR/share/gEDA/scheme/gnet-gsch2pcb.scm to reflect your preferred layer stack. In particular you may have to modify the line that defines the layer groups:
+</p>
+<pre class="code"> (display "Groups(\"1,2,3,s:4,5,6,c:7:8\")\n" port) </pre>
+
+<p>
+ and the layer stack itself:
+</p>
+<pre class="code">(lambda (port)
+ (display "Layer(1 \"bottom\")\n(\n)\n" port)
+ (display "Layer(2 \"bott.-poly.\")\n(\n)\n" port)
+ ...
+ (display "Layer(8 \"lineout\")\n(\n)" port)
+ (display "Layer(9 \"ignored\")\n(\n)\n" port)
+ (display "Layer(10 \"ignored\")\n(\n)" port)
+ (newline port)))</pre>
+
+<p>
+ Note, the last two layers will map to silk on both sides of the board. So you will have to define two more layers than you want for your copper layout.
+</p>
+
+</div>
+<!-- SECTION "I don't like the default layer stack of gschem2pcb. How can I change this?" [1178-] --></body>
+</html>
diff --git a/docs/wiki/geda-faq-gschem.fr.html b/docs/wiki/geda-faq-gschem.fr.html
new file mode 100644
index 0000000..52b341f
--- /dev/null
+++ b/docs/wiki/geda-faq-gschem.fr.html
@@ -0,0 +1,631 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#usage_de_gschem" class="toc">Usage de Gschem</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#comment_je_deplace_un_composant" class="toc">Comment je déplace un composant?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#comment_je_change_la_taille_du_texte_sur_un_symbole" class="toc">Comment je change la taille du texte sur un symbole?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#comment_deverouiller_un_composant" class="toc">Comment dévérouiller un composant</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#comment_refdes_peut-il_etre_automatiquement_numerote_lorsque_je_dessine_un_schema" class="toc">Comment refdes peut-il être automatiquement numéroté lorsque je dessine un schéma?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#qu_est-ce_qu_un_bus_et_comment_l_utiliser" class="toc">Qu'est-ce qu'un bus et comment l'utiliser?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#que_sont_les_liaisons_de_touches_dans_gschem" class="toc">Que sont les Liaisons de Touches dans gschem?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#quelles_sont_les_liaisons_avec_la_souris_dans_gschem" class="toc">Quelles sont les liaisons avec la souris dans gschem?</a></span></div></li>
+</ul>
+</li>
+<li class="level1"><div class="li"><span class="li"><a href="#symboles_gschem" class="toc">Symboles gschem</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#quel_est_l_objet_de_cette_polemique_entre_les_symboles_lourds_et_legers" class="toc">Quel est l'objet de cette polémique entre les symboles lourds et légers?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#j_utilise_un_symbole_exterieur_a_la_bibliotheque._comment_se_fait-il_qu_il_ne_soit_pas_aligne_sur_la_grille" class="toc">J'utilise un symbole extérieur à la bibliothèque. Comment se fait-il qu'il ne soit pas aligné sur la grille?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#existe-t-il_un_symbole_explicitement_non_connecte_que_je_pourrais_devrais_placer_dans_le_schema_pour_empecher_gnetlist_de_penser_que_j_ai_oublie_une_connexion" class="toc">Existe-t-il un symbole explicitement « non connecté » que je pourrais/devrais placer dans le schéma pour empêcher gnetlist de penser que j'ai oublié une connexion?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#comment_placer_un_un_attribut_de_symbole_invisible_dans_un_schema" class="toc">Comment placer un un attribut de symbole invisible dans un schéma?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#que_dois-je_faire_a_propos_des_broches_d_alimentation_sur_mon_symboleles_rendre_visible_explicites_ou_invisibles_implicites" class="toc">Que dois-je faire à propos des broches d'alimentation sur mon symbole: Les rendre visible (explicites) ou invisibles (implicites)?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#existe-t-il_une_specification_ou_un_manuel_pour_creer_les_symboles_gschem_ou_est-il" class="toc">Existe-t-il une spécification ou un manuel pour créer les symboles gschem? Où est-il?</a></span></div></li>
+</ul>
+</li>
+<li class="level1"><div class="li"><span class="li"><a href="#configuration_personnalisation_de_gschem" class="toc">Configuration/personnalisation de gschem</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#comment_changer_la_taille_par_defaut_d_un_texte_flottant" class="toc">Comment changer la taille par défaut d'un texte flottant?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#comment_je_peux_avoir_une_couleur_fond_differente" class="toc">Comment je peux avoir une couleur fond différente?</a></span></div></li>
+</ul>
+</li>
+<li class="level1"><div class="li"><span class="li"><a href="#impression_sortie" class="toc">Impression/Sortie</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#comment_imprimer_les_schemas_depuis_le_ligne_de_commande" class="toc">Comment imprimer les schémas depuis le ligne de commande?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#comment_je_peux_sortie_le_postscript_png_en_couleurs" class="toc">Comment je peux sortie le postscript/PNG en couleurs?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#comment_je_peux_avoir_une_sortie_postscript_png_en_noir_et_blanc" class="toc">Comment je peux avoir une sortie postscript/PNG en noir et blanc?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#comment_j_insere_des_schemas_dans_mon_document_latex" class="toc">Comment j'insère des schémas dans mon document LaTex?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#comment_je_scinde_un_fichier_postscript_en_plusieurs_pages" class="toc">Comment je scinde un fichier postscript en plusieurs pages?</a></span></div></li>
+</ul>
+</li>
+<li class="level1"><div class="li"><span class="li"><a href="#problemes_d_installation_d_execution_de_gschem" class="toc">Problèmes d'installation/d'exécution de gschem</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#gschem_segfaults_lorsque_j_efface_des_composants_sur_fc5_et_sur_d_autres_distributions_linux_existe-t-il_une_amelioration" class="toc">gschem segfaults lorsque j'efface des composants sur FC5 (et sur d'autres distributions Linux)! Existe-t-il une amélioration?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#apres_l_installation_gschem_ne_fonctionne_pas_que_ce_qui_a_pu_aller_mal" class="toc">Après l'installation, gschem ne fonctionne pas!? Que ce qui a pu aller mal?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#ajouter_des_composants_ne_proposent_aucun_symboles_que_puis-je_y_faire" class="toc">"Ajouter des Composants" ne proposent aucun symboles! Que puis-je y faire?</a></span></div></li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="usage_de_gschem" id="usage_de_gschem">Usage de Gschem</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "Usage de Gschem" [1-33] -->
+<h2><a name="comment_je_deplace_un_composant" id="comment_je_deplace_un_composant">Comment je déplace un composant?</a></h2>
+<div class="level2">
+
+<p>
+Ce nâ??est plus un problème·; déplacer un composant peut être réalisé en utilisant le bouton gauche de la souris – la méthode haituelle des utilisateurs de Windows. Pour les versions égales ou plus récentes que 20060824, faites ceci:
+</p>
+<ol>
+<li class="level1"><div class="li"> Sélectionnez le composant en cliquant dessus avec le bouton gauche de la souris. Le composant sera mis en valeur.</div>
+</li>
+<li class="level1"><div class="li"> Tirez le composant (en utilisant le bouton gauche de la souris) pour le placer où vous le voulez.</div>
+</li>
+</ol>
+
+<p>
+ Câ??est probablement ce que vous avez lâ??habitude de faire.
+</p>
+
+<p>
+Pour les personnes avec dâ??anciennes versions de gschem, vous avez ici trois voies pour déplacer facilement les composants avec gschem:
+</p>
+
+<p>
+Un:
+</p>
+<ol>
+<li class="level1"><div class="li"> Attrapez le composants avec le bouton de souris du milieu. Le composant suivra le curseur où vous lâ??emmenez.</div>
+</li>
+<li class="level1"><div class="li"> Pour placer le composant, relachez le bouton du milieu de la souris. Le composant restera où vous lâ??avez placé.</div>
+</li>
+</ol>
+
+<p>
+Deux:
+</p>
+<ol>
+<li class="level1"><div class="li"> Sélectionnez le composant en cliquant dessus avec le bouton gauche de la souris. Le composant sera mis en valeur.</div>
+</li>
+<li class="level1"><div class="li"> Appuyez sur la touche « M » du clavier. Le composant suivra le curseur où vous lâ??emmenez.</div>
+</li>
+<li class="level1"><div class="li"> Pour placer le composant, cliquez le bouton gauche de la souris. Le composant restera où vous lâ??avez placé.</div>
+</li>
+</ol>
+
+<p>
+Trois:
+</p>
+<ol>
+<li class="level1"><div class="li"> Pour placer le composant, cliquez sur le bouton gauche de souris. Le composant restera là où vous lâ??avez placé.</div>
+</li>
+</ol>
+
+</div>
+<!-- SECTION "Comment je déplace un composant?" [34-1443] -->
+<h2><a name="comment_je_change_la_taille_du_texte_sur_un_symbole" id="comment_je_change_la_taille_du_texte_sur_un_symbole">Comment je change la taille du texte sur un symbole?</a></h2>
+<div class="level2">
+<ol>
+<li class="level1"><div class="li"> Sélectionnez le symbole.</div>
+</li>
+<li class="level1"><div class="li"> Clic droit â?? down symbol (ou faites Hierarchy â?? down symbol). Ceci vous mène à lâ??éditeur de symbole.</div>
+</li>
+<li class="level1"><div class="li"> Sélectionnez le pinnumber que vous voulez changer.</div>
+</li>
+<li class="level1"><div class="li"> Faites Edit â?? Edit Text (ou tapez le raccourci clavier « ex »).</div>
+</li>
+<li class="level1"><div class="li"> Changez la taille de police dans la boîte déroulante.</div>
+</li>
+<li class="level1"><div class="li"> Recommencez pour tous les éléments de textes désirés.</div>
+</li>
+<li class="level1"><div class="li"> Fichier â?? sauvegarde</div>
+</li>
+<li class="level1"><div class="li"> Clic droit â?? up (ou Hierarchy â?? Up). Vous êtes maintenant retourné à lâ??éditeur de schéma.</div>
+</li>
+<li class="level1"><div class="li"> Avez le symbole encore sélectionné, faites Edit â?? Update component (ou utilisez le raccourci clavier « ep »). Si cela ne fonctionne pas, effacez simplement le symbole et rechargez-le.</div>
+</li>
+</ol>
+
+<p>
+ Plus généralement, vous pouvez utiliser cette procédure pour éditer nâ??importe quoi sur un symbole. (Substituez « Edit Text » pour votre édition souhaitée, bien sûr.)
+</p>
+
+</div>
+<!-- SECTION "Comment je change la taille du texte sur un symbole?" [1444-2401] -->
+<h2><a name="comment_deverouiller_un_composant" id="comment_deverouiller_un_composant">Comment dévérouiller un composant</a></h2>
+<div class="level2">
+
+<p>
+Lorsquâ??un composant est véroullé, il est insélectionnable en utilisant le bouton milieu de la souris mais il est néanmoins sélectionnable en utilisant une sélection de fenêtre. Pour une sélection de fenêtre sur un composant, cliquez et maintenez avec le bouton gauche de souris et tirez pour créer une région rectangulaire contenant le composant devant être dévérouillé. Exécutez la commande <strong><em>Edit</em></strong> <strong>â??</strong> <strong><em>unLock</em></strong> pour dévérouiller le composant.
+</p>
+
+</div>
+<!-- SECTION "Comment dévérouiller un composant" [2402-2929] -->
+<h2><a name="comment_refdes_peut-il_etre_automatiquement_numerote_lorsque_je_dessine_un_schema" id="comment_refdes_peut-il_etre_automatiquement_numerote_lorsque_je_dessine_un_schema">Comment refdes peut-il être automatiquement numéroté lorsque je dessine un schéma?</a></h2>
+<div class="level2">
+
+<p>
+Ã?ditez le fichier system-gschemrc ou placez ce qui suit dans le fichier gschemrc (soit <strong><code>~/.gEDA/gschemrc</code></strong> ou un fichier <strong><code>gschemrc</code></strong> dans le répertoire local dâ??où vous invoquez gschem):
+</p>
+<pre class="code">
+;(load (string-append gedadata "/scheme/auto-uref.scm")) ; load the autonumbering script ; ancienne syntaxe
+(load-from-path "auto-uref.scm") ; nouvelle syntaxe
+(add-hook! add-component-hook auto-uref) ; autonumber when adding a component
+(add-hook! copy-component-hook auto-uref) ; autonumber when copying a component
+</pre>
+
+<p>
+Veuillez substituer $YOUR_INSTALL_PATH par le chemin dâ??installation de geda.
+</p>
+
+</div>
+<!-- SECTION "Comment refdes peut-il être automatiquement numéroté lorsque je dessine un schéma?" [2930-3664] -->
+<h2><a name="qu_est-ce_qu_un_bus_et_comment_l_utiliser" id="qu_est-ce_qu_un_bus_et_comment_l_utiliser">Qu'est-ce qu'un bus et comment l'utiliser?</a></h2>
+<div class="level2">
+
+<p>
+ Un bus est purement décoratif. Le netlister lâ??ignore. Lâ??attribut netname= ne fonctionne pas pour connecter les points ensemble â?? câ??est ce que gnetlist lit et transforme dans votre netlist. Il nâ??est pas possible de connecter une ligne discrète ou « accrochée à un bus » car, encore une fois, le bus est plus une entité graphique.
+</p>
+
+<p>
+Quelques utilisateurs ont trouvé utile dâ??organiser leurs réseaux en incorporant un nom de bus dans le nom de net. Par exemple, « net=busA:1 » peut être ajouté à chaque busripper pour aider le tri des nets.
+</p>
+
+</div>
+<!-- SECTION "Qu'est-ce qu'un bus et comment l'utiliser?" [3665-4273] -->
+<h2><a name="que_sont_les_liaisons_de_touches_dans_gschem" id="que_sont_les_liaisons_de_touches_dans_gschem">Que sont les Liaisons de Touches dans gschem?</a></h2>
+<div class="level2">
+
+</div>
+<!-- SECTION "Que sont les Liaisons de Touches dans gschem?" [4274-4332] -->
+<h2><a name="quelles_sont_les_liaisons_avec_la_souris_dans_gschem" id="quelles_sont_les_liaisons_avec_la_souris_dans_gschem">Quelles sont les liaisons avec la souris dans gschem?</a></h2>
+<div class="level2">
+
+<p>
+Par défaut, vous avez:
+</p>
+<ul>
+<li class="level1"><div class="li"> Le bouton gauche de souris est utilisé pour prendre et dessiner</div>
+</li>
+<li class="level1"><div class="li"> Le bouton milieu de souris est soit pour déplacer un objet (maintenez le bouton milieu sur un objet et déplacez la souris), soit pour copier un objet (la touche ALT maintenue lors dâ??une pression sur le bouton milieu sur un objet et déplacez la souris).</div>
+</li>
+<li class="level1"><div class="li"> Le bouton droit de souris est un menu déroulant.</div>
+</li>
+</ul>
+
+<p>
+ Vous pouvez changer le bouton milieu en ajoutant ce qui suit à un fichier gschemrc:
+</p>
+<pre class="code">(middle-button "action") ;default binding, move or copy an object</pre>
+
+<p>
+ou:
+</p>
+<pre class="code">(middle-button "stroke") ;draw mouse gestures/strokes (must install libstroke to enable</pre>
+
+<p>
+ou:
+</p>
+<pre class="code">(middle-button "repeat") ;repeat the last command executed</pre>
+
+<p>
+Vous pouvez changer le bouton droit en ajoutant ce qui suit dans un fichier gschemrc:
+</p>
+<pre class="code">(third-button "popup") ;default binding, show a popup menu</pre>
+
+<p>
+ou:
+</p>
+<pre class="code">(third-button "mousepan") ;use the mouse to pan around the schematic</pre>
+
+<p>
+Pour plus informations sur ces options, veuillez aller voir le fichier <strong><code>${install_prefix}/share/gEDA/system-gschemrc</code></strong>.
+</p>
+
+</div>
+<!-- SECTION "Quelles sont les liaisons avec la souris dans gschem?" [4333-5537] -->
+<h1><a name="symboles_gschem" id="symboles_gschem">Symboles gschem</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "Symboles gschem" [5538-5568] -->
+<h2><a name="quel_est_l_objet_de_cette_polemique_entre_les_symboles_lourds_et_legers" id="quel_est_l_objet_de_cette_polemique_entre_les_symboles_lourds_et_legers">Quel est l'objet de cette polémique entre les symboles lourds et légers?</a></h2>
+<div class="level2">
+
+<p>
+Cette nomenclature est apparue dâ??une discussion qui apparaît fréquement sur les listes de diffusion geda-user et geda-dev. Un symbole léger contient peu dâ??attributs intégrés dans le symbole lui-même. Il nécessite que lâ??utilisateur attache presque tous les attributs au niveau du schéma (i.e. en utilisant soit gschem, soit gattrib). Un symbole lourd contient plusieurs attributs (tels quâ??une empreinte de boîtier, des noms de modèle SPICE, etc.) intégrés dans le fichier symbole lui-même. Un symbole lourd nécessite donc des attachements dâ??attributs très légers au niveau du schéma â?? vous nâ??avez quâ??à le placer et câ??est fait.
+</p>
+
+<p>
+Le débat entre les adversaires des symboles lourds et légers est très détaillé et pointu. En caricaturant, les avocats des symboles lourds croient que cela fournit une meilleure intégration entre gschem et PCB avec lâ??importance des attrituts de placement (tels que <a href="geda-pcb_tips.html#i_want_to_use_pcb_to_do_layout._how_do_i_know_what_value_to_use_for_the_footprint_attribute" class="wikilink1" title="geda-pcb_tips.html">footprint name</a>) déjà créés dans le symbole. Ceci est considéré comme une bonne chose pour les nouveaux utilisateurs (noobs) qui veulent simplement concevoir une simple carte et nâ??apprécient pas ou nâ??ont que faire des zillions de variations quâ??une simple résistance peut avoir (i.e. empreintes différentes, TCR, précision, composition physique, etc). Les avocats des symboles légers préfère traiter les attributs au niveau du schéma car ils pensent que câ??est plus flexible. Ils font rapidement remarquer que une bibliothèque de symboles lourds sâ??accroîtra rapidement en des milliers de morceaux avec des noms grotesquement longs en tentant de distinguer entre les différentes variations dâ??un composant. Ils soulignent aussi que lâ??utilitaire « gattrib » est lâ??outil préféré pour traiter les attributs au niveau du schéma (i.e. dans le fichier .sch).
+</p>
+
+<p>
+GEDA/gaf, configuré par défaut, utilise des symboles légers, bien quâ??il puisse être configuré pour utiliser des symboles lourds. Pour plus dâ??informations, vous pouvez lire ces dicussions sur la liste de diffusion geda-user:
+</p>
+
+<p>
+<a href="http://archives.seul.org/geda/user/Jun-2005/msg00001.html"; class="urlextern" title="http://archives.seul.org/geda/user/Jun-2005/msg00001.html"; rel="nofollow">http://archives.seul.org/geda/user/Jun-2005/msg00001.html</a> <a href="http://archives.seul.org/geda/dev/Oct-2005/msg00043.html"; class="urlextern" title="http://archives.seul.org/geda/dev/Oct-2005/msg00043.html"; rel="nofollow">http://archives.seul.org/geda/dev/Oct-2005/msg00043.html</a>
+</p>
+
+</div>
+<!-- SECTION "Quel est l'objet de cette polémique entre les symboles lourds et légers?" [5569-7909] -->
+<h2><a name="j_utilise_un_symbole_exterieur_a_la_bibliotheque._comment_se_fait-il_qu_il_ne_soit_pas_aligne_sur_la_grille" id="j_utilise_un_symbole_exterieur_a_la_bibliotheque._comment_se_fait-il_qu_il_ne_soit_pas_aligne_sur_la_grille">J'utilise un symbole extérieur à la bibliothèque. Comment se fait-il qu'il ne soit pas aligné sur la grille?</a></h2>
+<div class="level2">
+
+<p>
+Les symboles dans la bibliothèque, comme ceux disponibles sur le site web <a href="http://www.gedasymbols.org"; class="urlextern" title="http://www.gedasymbols.org"; rel="nofollow"> gedasymbols </a> sont fournis par des utilisateurs comme vous. Quelques personnes utilisent des initialisations de grille différentes des autres (i.e. 50mil vs. 100mil). Si vous découvrez un symbole qui semble être hors de la grille, tentez de réduire votre espacement de grille, déplacez le symbole de telle manière quâ??il sâ??adapte à « votre » propre grille, puis revenez à votre grille initiale.
+</p>
+
+<p>
+Oui, les docs gEDA suggèrent que vous utilisiez un espacement de grille de 100mil. Mais tout le monde aime faire les choses à sa propre manière et il nâ??existe pas de diktat pour pour imposer les règles sur les symboles rendus disponibles. Vous devez donc être au courant de cette possibilité.
+</p>
+
+</div>
+<!-- SECTION "J'utilise un symbole extérieur à la bibliothèque. Comment se fait-il qu'il ne soit pas aligné sur la grille?" [7910-8848] -->
+<h2><a name="existe-t-il_un_symbole_explicitement_non_connecte_que_je_pourrais_devrais_placer_dans_le_schema_pour_empecher_gnetlist_de_penser_que_j_ai_oublie_une_connexion" id="existe-t-il_un_symbole_explicitement_non_connecte_que_je_pourrais_devrais_placer_dans_le_schema_pour_empecher_gnetlist_de_penser_que_j_ai_oublie_une_connexion">Existe-t-il un symbole explicitement « non connecté » que je pourrais/devrais placer dans le schéma pour empêcher gnetlist de penser que j'ai oublié une connexion?</a></h2>
+<div class="level2">
+
+<p>
+Réponse: misc â?? nc-left, nc-right, nc-top, nc-bottom.
+</p>
+
+<p>
+Attention: occassionnellement, cela peut créer une liaison appelée « no_connect » (ou « NC?? ») qui peut mener à des broches connectées ensembles dans gnetlist â?? ce que vous _ne souhaitez probablement pas_.
+</p>
+
+<p>
+Si vous voulez un symbole graphiquement complet (sans connexions électriques), ajoutez un attribut â??graphical=1â??. Le netlister ignorera entièrement ces symboles.
+</p>
+
+</div>
+<!-- SECTION "Existe-t-il un symbole explicitement « non connecté » que je pourrais/devrais placer dans le schéma pour empêcher gnetlist de penser que j'ai oublié une connexion?" [8849-9471] -->
+<h2><a name="comment_placer_un_un_attribut_de_symbole_invisible_dans_un_schema" id="comment_placer_un_un_attribut_de_symbole_invisible_dans_un_schema">Comment placer un un attribut de symbole invisible dans un schéma?</a></h2>
+<div class="level2">
+
+<p>
+La plupart des symboles dâ??un symbole ne sont pas placés sur le schéma à moins quâ??ils ne soient visibles. Pour afficher les attributs de symboles invisibles, cherchez les mots clés suivants dans le fichier system-gschemrc:
+</p>
+<pre class="code">(attribute-promotion â??enabledâ??);
+(promote-invisible â??disabledâ??) ; â?? This one
+(keep-invisible â??enabledâ??)</pre>
+
+<p>
+Ajoutez à votre fichier gschemrc:
+</p>
+<pre class="code">(promote-invisible â??enabledâ??)</pre>
+
+<p>
+et vous verrez tous les attributs. Le mot « keep-invisible » gardera caché ceux des attributs qui sont cachés dans le fichier symbole.
+</p>
+
+</div>
+<!-- SECTION "Comment placer un un attribut de symbole invisible dans un schéma?" [9472-10132] -->
+<h2><a name="que_dois-je_faire_a_propos_des_broches_d_alimentation_sur_mon_symboleles_rendre_visible_explicites_ou_invisibles_implicites" id="que_dois-je_faire_a_propos_des_broches_d_alimentation_sur_mon_symboleles_rendre_visible_explicites_ou_invisibles_implicites">Que dois-je faire à propos des broches d'alimentation sur mon symbole: Les rendre visible (explicites) ou invisibles (implicites)?</a></h2>
+<div class="level2">
+
+<p>
+Dans le passé, les circuits numériques cachaient souvent leurs broches dâ??alimentation et en utilisant un attribut à lâ??intérieur du symbole. La pensée moderne est que câ??est une mauvaise pratique bien que les guerres de religions font encore occasionnellement rage à propos de ce sujet).
+</p>
+
+<p>
+Cela reste marginalement vrai pour les vieux circuits logiques dâ??avoir toutes des broches dâ??alimentation et de GND, en 5V TTL, cachées. Si vous nâ??avez que du +5V sur votre carte, cacher alors les broches dâ??alimentation +5V peut simplifier quelque peu votre schéma. Néanmoins, peut de concepteur dessinent de tels circuits de nos jours; 5V TTL (et 5V CMOS) sont devenues rapidement des technologies antiques.
+</p>
+
+<p>
+Il a toujours été inacceptable de cacher les broches dâ??alimentation sur les circuits analogiques. Dâ??abord, lâ??analogique a souvent de multiples connexions dâ??alimentation (VCC, VEE) qui ont explicitement besoin dâ??être dessinées. Ensuite, une bonne pratique de conception est de placer des capacités de découplage sur chaquet et toutes les broches dâ??alimentations. Quelques uns placent aussi une inductance en série avec lâ??alimentation. Comme ils doivent être insérés dans le schéma, cela est réalisé plus facilement en les attachant explicitement à une broche dâ??alimentation. Câ??est la raison pour laquelle on ne dedrait jamais utiliser des broches dâ??alimentaion cachées pour les symboles analogiques.
+</p>
+
+<p>
+Les nouveaux circuits logiques utilisent souvent de multiples alimentations pour différentes sections logiques (OVDD, DVDD, etc). Il est aussi habituel dâ??avoir plusieurs familles logiques sur une seule carte (5V, 3.3V, etc.). Câ??est la raison pour laquelle est est mieux de placer et de câbler explicitement les broches dâ??alimentation sur le symbole. Les broches dâ??alimentation cachées sont un réservoir de désastre car vous pouvez facilement mal connecter un composant 5V sur un réseau 3.3V, par exemple.
+</p>
+
+<p>
+Pour paraphraser Nancy Reagan: Dites simplement «·non·» aux broches dâ??alimentation.
+</p>
+
+<p>
+Ceci étant dit, il peut encore être utile de détacher les broches dâ??alimentation de la partie fonctionnelle du du symbole. Pour ce faire, définissez un symbole dâ??alimentation séparé et donnez-lui le même <a href="geda-glossary.html" class="wikilink1" title="geda-glossary.html">refdes</a> comme une partie fonctionnelle. Lancer gsch2pcb traitera la séparation correctement comme un seul composant. Comme ni gschem, ni gsch2pcb ne savent explicitement que le composant nâ??est complet quâ??avec les deux symboles définis, vous aurez donc à le contrôler vous-même. Avec cette méthode, vous pouvez dessiner toutes les alimentation dans un coin du schéma où elles nâ??interfèrent pas avec les nets de signaux. Dans plusieurs cas, câ??est plus avantageux avec les circuits analogiques.
+</p>
+
+</div>
+<!-- SECTION "Que dois-je faire à propos des broches d'alimentation sur mon symbole: Les rendre visible (explicites) ou invisibles (implicites)?" [10133-13027] -->
+<h2><a name="existe-t-il_une_specification_ou_un_manuel_pour_creer_les_symboles_gschem_ou_est-il" id="existe-t-il_une_specification_ou_un_manuel_pour_creer_les_symboles_gschem_ou_est-il">Existe-t-il une spécification ou un manuel pour créer les symboles gschem? Où est-il?</a></h2>
+<div class="level2">
+
+<p>
+Oui. Câ??est le <a href="geda-scg.fr.html" class="wikilink1" title="geda-scg.fr.html">Guide de Création de Symbole</a>.
+</p>
+
+</div>
+<!-- SECTION "Existe-t-il une spécification ou un manuel pour créer les symboles gschem? Où est-il?" [13028-13190] -->
+<h1><a name="configuration_personnalisation_de_gschem" id="configuration_personnalisation_de_gschem">Configuration/personnalisation de gschem</a></h1>
+<div class="level1">
+
+<p>
+gschem est configurable de plusieurs manières qui peuvent être décrites ici. Jetez un oeil sur «·system-gschemrc·» pour des suggestions sur ce qui peut être fait dâ??autre.
+</p>
+
+</div>
+<!-- SECTION "Configuration/personnalisation de gschem" [13191-13425] -->
+<h2><a name="comment_changer_la_taille_par_defaut_d_un_texte_flottant" id="comment_changer_la_taille_par_defaut_d_un_texte_flottant">Comment changer la taille par défaut d'un texte flottant?</a></h2>
+<div class="level2">
+
+<p>
+Placez
+</p>
+<pre class="code">(text-size 10)</pre>
+
+<p>
+ dans votre gschemrc et replacez «·10·» avec votre taille favorite.
+</p>
+
+</div>
+<!-- SECTION "Comment changer la taille par défaut d'un texte flottant?" [13426-13605] -->
+<h2><a name="comment_je_peux_avoir_une_couleur_fond_differente" id="comment_je_peux_avoir_une_couleur_fond_differente">Comment je peux avoir une couleur fond différente?</a></h2>
+<div class="level2">
+
+<p>
+ �ditez le fichier system-gschemrc et au début du fichier, vous trouvezrez des lignes comme:
+</p>
+<pre class="code">;
+; Start of color section
+;
+; Load up a color scheme has a light (almost white) background
+; Comment out the first line and comment in the second line for a
+; dark (black) background. The dark background is the original look.
+;
+(load (string-append gedadatarc "/gschem-darkbg")) ; dark background
+;(load (string-append gedadatarc "/gschem-lightbg")) ; light background</pre>
+
+<p>
+Commentez la ligne <strong><code>darkbg</code></strong> (avec un ;) et décommentez la ligne <strong><code>lightbg</code></strong>. Cela vous donnera une couleur de fond blanche au lieu de noir. Il ajuste aussi toutes les autres couleurs pour être compatibles avec un fond lumineux.
+</p>
+
+<p>
+Si vous voulez plus de contrôle sur les couleurs, veuillez éditer <strong><code>${prefix}/share/gEDA/gschem-darkbg</code></strong> ou <strong><code>${prefix}/share/gEDA/gschem-lightbg</code></strong> ou créez votre propre fichier et chargez-le dans le fichier <strong><code>system-gschemrc</code></strong>.
+</p>
+
+<p>
+Un fond noir est préféré par plusieurs utilisateurs.
+</p>
+
+<p>
+Avec les versions récentes de gscgem, vous pouvez aussi placer ceci dans gschemrc:
+</p>
+<pre class="code">(load-from-path "../gschem-lightbg")</pre>
+
+</div>
+<!-- SECTION "Comment je peux avoir une couleur fond différente?" [13606-14819] -->
+<h1><a name="impression_sortie" id="impression_sortie">Impression/Sortie</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "Impression/Sortie" [14820-14853] -->
+<h2><a name="comment_imprimer_les_schemas_depuis_le_ligne_de_commande" id="comment_imprimer_les_schemas_depuis_le_ligne_de_commande">Comment imprimer les schémas depuis le ligne de commande?</a></h2>
+<div class="level2">
+<pre class="code">Notez que le script gschem-print.scm s'appelle désormais print.scm .
+Dans Gentoo en particulier, il est placé en /usr/share/gEDA/scheme/print.scm .</pre>
+
+<p>
+ Lancez le script <strong><code>gschem-print.scm</code></strong> créera le fichier Postscript qui est spécifié par la ligne de commande.
+</p>
+
+<p>
+La ligne de commande ci-dessous crée un fichier Postscript depuis le fichier schéma (replacez MY_SCH avec le nom de votre schéma et GEDA_SCHEME_DIR avec le nom de votre répertoire où les fichiers schémas gEDA sont installés):
+</p>
+<pre class="code">gschem -p -oMY_SCH.ps -sGEDA_SCHEME_DIR/gschem-print.scm MY_SCH.sch</pre>
+
+<p>
+Le script BASH ci-dessous, que jâ??ai nommé <strong><code>gschem-print</code></strong>, crée un fichier Postscript pour chaque fichier schéma spécifié sur la ligne de commande et place chaque fichier généré sur lâ??imprimante par défaut:
+</p>
+<pre class="code">#!/bin/bash
+
+# gschem options
+# -oPS_FILENAME output to Postscript file PS_FILENAME
+# -sSCRIPT_FILENAME run script SCRIPT_FILENAME
+# -p autoplace windows
+
+for name in $*
+do
+base=â??${name%.*}â??
+gschem -p -o$base.ps -sGEDA_SCHEME_DIR/gschem-print.scm $base.sch
+lpr -P$PRINTER $base.ps
+done</pre>
+
+</div>
+<!-- SECTION "Comment imprimer les schémas depuis le ligne de commande?" [14854-16038] -->
+<h2><a name="comment_je_peux_sortie_le_postscript_png_en_couleurs" id="comment_je_peux_sortie_le_postscript_png_en_couleurs">Comment je peux sortie le postscript/PNG en couleurs?</a></h2>
+<div class="level2">
+
+<p>
+�ditez le fichier <strong><code>system-gschemrc</code></strong> ou placez ce qui suit dans un fichier <strong><code>gschemrc</code></strong> (soit <strong><code>~/.gEDA/gschemrc</code></strong> ou un fichier <strong><code>gschemrc</code></strong> dans le répertoire local depuis où vous invoquez gschem):
+</p>
+<pre class="code">(output-color "enabled") ; for color postscript output
+(image-color "enabled") ; for color PNG output (enabled by default)</pre>
+
+<p>
+Pour contrôler la couleur de fond du fichier PS, changez la ligne suivante soit avec gschem-darkbg (pour la couleur de fond par défaut en noir) ou gschem-lightbg (pour une couleur de fond alternative):
+</p>
+<pre class="code">(output-color-background 16 "black" "null" "0 0 0" 0 0 0)</pre>
+
+<p>
+Les â??0 0 0â?? sont les composantes RGB (entre 0..1) pour la couleur de fond de la sortie du PS.
+</p>
+
+<p>
+Pour contrôler le fond de la sortie <acronym title="Portable Network Graphics">PNG</acronym>, changez la ligne suivante soit en gschem-darkbg (pour la couleur de fond par défaut en noir) ou gschem-lightbg (pour une couleur de fond alternative):
+</p>
+<pre class="code">(background-color 0 "grey94" "null" "1 1 1" 255 255 255)</pre>
+
+<p>
+Les 255 255 255 sont les composantes RGB pour la couleur de fond de lâ??image <acronym title="Portable Network Graphics">PNG</acronym>.
+</p>
+
+</div>
+<!-- SECTION "Comment je peux sortie le postscript/PNG en couleurs?" [16039-17194] -->
+<h2><a name="comment_je_peux_avoir_une_sortie_postscript_png_en_noir_et_blanc" id="comment_je_peux_avoir_une_sortie_postscript_png_en_noir_et_blanc">Comment je peux avoir une sortie postscript/PNG en noir et blanc?</a></h2>
+<div class="level2">
+
+<p>
+Pour les sorties PS en noir et blanc, placez ce qui suit dans un fichier gschemrc:
+</p>
+<pre class="code">(output-color "disabled") ; for monochrome postscript output</pre>
+
+<p>
+Pour les images <acronym title="Portable Network Graphics">PNG</acronym> en noir et blanc, placez ce qui suit dans un fichier gschemrc:
+</p>
+<pre class="code">(image-color "disabled") ; for monochromoe PNG output</pre>
+
+</div>
+<!-- SECTION "Comment je peux avoir une sortie postscript/PNG en noir et blanc?" [17195-17592] -->
+<h2><a name="comment_j_insere_des_schemas_dans_mon_document_latex" id="comment_j_insere_des_schemas_dans_mon_document_latex">Comment j'insère des schémas dans mon document LaTex?</a></h2>
+<div class="level2">
+<ol>
+<li class="level1"><div class="li"> Sortez le schéma dans un fichier. Cela sera un postscript générique (*.ps).</div>
+</li>
+<li class="level1"><div class="li"> Convertissez le fichier postscript en epsi avec lâ??outil ps2epsi. Câ??est un script de la suite ghostscript.</div>
+</li>
+<li class="level1"><div class="li"> Incluez usepackage{graphicx} dans le préambulz de votre document latex. Utilisez la commande includegraphics pour placer votre schéma.</div>
+</li>
+</ol>
+
+<p>
+ Un exemple simple:
+</p>
+<pre class="code">\documentclass{article}
+\usepackage{graphicx}
+\begin{document}
+ \begin{image}
+ \includegraphics[width=100mm]{ModulPID.epsi}
+ \end{image}
+\end{document}</pre>
+
+</div>
+<!-- SECTION "Comment j'insère des schémas dans mon document LaTex?" [17593-18183] -->
+<h2><a name="comment_je_scinde_un_fichier_postscript_en_plusieurs_pages" id="comment_je_scinde_un_fichier_postscript_en_plusieurs_pages">Comment je scinde un fichier postscript en plusieurs pages?</a></h2>
+<div class="level2">
+
+<p>
+gschem ne fournit pas cette fonctionnalité en interne; il existe néanmoins un programme appelé «·poster·» qui le réalise exactement. Il peut être téléchargé depuis soit <a href="http://www.gnu.org/directory/poster.html"; class="urlextern" title="http://www.gnu.org/directory/poster.html"; rel="nofollow">ici</a> (GNU), soit <a href="http://printing.kde.org/downloads/"; class="urlextern" title="http://printing.kde.org/downloads/"; rel="nofollow">ici</a> (KDE Print).
+</p>
+
+</div>
+<!-- SECTION "Comment je scinde un fichier postscript en plusieurs pages?" [18184-18554] -->
+<h1><a name="problemes_d_installation_d_execution_de_gschem" id="problemes_d_installation_d_execution_de_gschem">Problèmes d'installation/d'exécution de gschem</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "Problèmes d'installation/d'exécution de gschem" [18555-18618] -->
+<h2><a name="gschem_segfaults_lorsque_j_efface_des_composants_sur_fc5_et_sur_d_autres_distributions_linux_existe-t-il_une_amelioration" id="gschem_segfaults_lorsque_j_efface_des_composants_sur_fc5_et_sur_d_autres_distributions_linux_existe-t-il_une_amelioration">gschem segfaults lorsque j'efface des composants sur FC5 (et sur d'autres distributions Linux)! Existe-t-il une amélioration?</a></h2>
+<div class="level2">
+
+<p>
+Ce bogue semble être apparu pour les utilisateurs de la Fedora Core 5 (et dâ??autres distributions linux qui utilisent glib 2.10.x). Le bogue a été réglé par les développeurs et il apparaîtra dans la prochaine version de gEDA/gaf.
+</p>
+
+<p>
+A moyen terme, vous pouvez contourner ce bogue en plaçant la variable dâ??environnement G_SLICE à «·always-malloc·». Spécifiquement, avant de lancer gschem, faites ceci:
+</p>
+
+<p>
+bash:
+</p>
+<pre class="code">export G_SLICE=always-malloc</pre>
+
+<p>
+csh:
+</p>
+<pre class="code">setenv G_SLICE always-malloc</pre>
+
+</div>
+<!-- SECTION "gschem segfaults lorsque j'efface des composants sur FC5 (et sur d'autres distributions Linux)! Existe-t-il une amélioration?" [18619-19269] -->
+<h2><a name="apres_l_installation_gschem_ne_fonctionne_pas_que_ce_qui_a_pu_aller_mal" id="apres_l_installation_gschem_ne_fonctionne_pas_que_ce_qui_a_pu_aller_mal">Après l'installation, gschem ne fonctionne pas!? Que ce qui a pu aller mal?</a></h2>
+<div class="level2">
+
+<p>
+ Si vous lancez gschem et que vous avez une fenêtre sans barre de menu, sans couleurs et le programme sâ??arrête lorsque vous appuyez sur une touche avec le message suivant:
+</p>
+<pre class="code">ERROR: Unbound variable: current-keymap</pre>
+
+<p>
+Ou vous avez une erreur tel que ceci:
+</p>
+<pre class="code">Gtk-CRITICAL : file gtkpixmap.c: line 97 (gtk_pixmap_new): assertion `val != NULLâ?? failed.
+Gtk-CRITICAL : file gtkpixmap.c: line 97 (gtk_pixmap_new): assertion `val != NULLâ?? failed.
+Tried to get an invalid color: 0
+Tried to get an invalid color: 7
+Tried to get an invalid color: 0
+Tried to get an invalid color: 7</pre>
+
+<p>
+alors gschem ne trouve pas de fichier rc. Il y a deux ficheirs rc nécessaires. Le premier est <strong><code>system-gschemrc</code></strong> et le second <strong><code>system-commonrc</code></strong>.
+</p>
+<ul>
+<li class="level1"><div class="li"> Le fichier rc system-gschemrc doit être installé lorsque vous installez gschem et réside typiquement dans <strong><code>${prefix}/share/gEDA/system-gschemrc</code></strong>. <strong><code>${prefix}</code></strong> est lâ??endroit où vous avez installé gschem (habituellement <strong><code>/usr</code></strong> ou <strong><code>/usr/local</code></strong> ou <strong><code>$HOME/geda</code></strong>). Ce fichier peut aussi être installé dans /etc/gEDA (câ??est le cas des paquets .debs).</div>
+</li>
+<li class="level1"><div class="li"> Le fichier rc system-commonrc devrait être installé lorsque vous installez la bibliothèque de symboles pour gEDA/gaf. Il réside dans <strong><code>${prefix}/share/gEDA/system-commonrc</code></strong>. Ce fichier peut aussi être installé dans <strong><code>/etc/gEDA</code></strong> (câ??est le cas des paquets .debs). Ce fichier nâ??est pas chargé directement par gschem. Il est chargé par un â??(load …)â?? dans le ficheir rc system-gschemrc.</div>
+</li>
+</ul>
+
+<p>
+ Assurez-vous que ces fichiers soient installés. Le fichier gschem.log (qui est créé à chaque fois que vous lancez gschem) contient des informations de déboguage intéressantes qui doivent aider dans la recherche de ce qui ne va pas. Contrôlez ce fichier pour voir où gschem cherche les fichiers rc.
+</p>
+
+<p>
+Aussi, quelques anciennes versions de gEDA/gaf ont quelques bogues lorsque les fichiers rc files sont installés dans dâ??autres endroits (autres que <strong><code>${prefix}/share/gEDA</code></strong>), veuillez donc le mettre à jour vers une version plus récente.
+</p>
+
+</div>
+<!-- SECTION "Après l'installation, gschem ne fonctionne pas!? Que ce qui a pu aller mal?" [19270-21459] -->
+<h2><a name="ajouter_des_composants_ne_proposent_aucun_symboles_que_puis-je_y_faire" id="ajouter_des_composants_ne_proposent_aucun_symboles_que_puis-je_y_faire">"Ajouter des Composants" ne proposent aucun symboles! Que puis-je y faire?</a></h2>
+<div class="level2">
+
+<p>
+ Assurez-vous quâ??au moins un de vos fichiers de config contient un chemin valide vers une bibliothèque de symbole. Au démarrage, gschem contrôle les fichiers de de config suivants (sur un système Debian):
+</p>
+<ol>
+<li class="level1"><div class="li"> fichier gafrc système: <code>/etc/gEDA/system-gafrc</code></div>
+</li>
+<li class="level1"><div class="li"> fichier gafrc utilisateur: <code>~/.gEDA/gafrc</code></div>
+</li>
+<li class="level1"><div class="li"> fichier gafrc local: <code>$PWD/gafrc</code></div>
+</li>
+<li class="level1"><div class="li"> fichier gschemrc système: <code>/etc/gEDA/system-gschemrc</code></div>
+</li>
+<li class="level1"><div class="li"> fichier gschemrc utilisateur: <code>~/.gEDA/gschemrc</code></div>
+</li>
+<li class="level1"><div class="li"> fichier gschemrc local: <code>$PWD/gschemrc]</code></div>
+</li>
+</ol>
+
+<p>
+Tous ces fichies de config peuvent ou non ajouter des chemins à la liste de recherche des bibliothèques. Si un fichier de config contient la commande
+</p>
+<pre class="code">(reset-component-library)</pre>
+
+<p>
+ Le chemin de recherche des bibliothèques sera vidé. Lâ??ordre est évidemment important, comme cette commande effacera tout chemin précédemment ajoûté.
+</p>
+
+</div>
+<!-- SECTION "Ajouter des Composants ne proposent aucun symboles! Que puis-je y faire?" [21460-] --></body>
+</html>
diff --git a/docs/wiki/geda-faq-gschem.html b/docs/wiki/geda-faq-gschem.html
new file mode 100644
index 0000000..996d53b
--- /dev/null
+++ b/docs/wiki/geda-faq-gschem.html
@@ -0,0 +1,1031 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#general" class="toc">General</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#i_found_a_bug_what_can_i_do_about_it" class="toc">I found a bug! What can I do about it?</a></span></div></li>
+</ul>
+</li>
+<li class="level1"><div class="li"><span class="li"><a href="#gschem_usage" class="toc">Gschem usage</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#there_is_no_symbol_in_the_chooser_dialog" class="toc">There is no symbol in the chooser dialog!</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_move_a_component" class="toc">How do I move a component?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_move_components_without_dragging_a_tail_of_connectet_nets" class="toc">How do I move components without dragging a tail of connectet nets?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_change_the_size_of_the_text_on_a_symbol" class="toc">How do I change the size of the text on a symbol?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#is_it_possible_to_overline_text_in_gschem" class="toc">Is it possible to overline text in gschem?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_unlock_a_locked_component" class="toc">How do I unlock a locked component</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_can_i_get_refdes_automatically_numbered_when_i_draw_a_schematic" class="toc">How can I get refdes automatically numbered when I draw a schematic?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#what_is_a_bus_and_how_do_i_use_it" class="toc">What is a Bus and how do I use it?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_can_i_change_key_bindings_in_gschem" class="toc">How can I change Key Bindings in gschem?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#what_are_the_mouse_bindings_in_gschem" class="toc">What are the mouse bindings in gschem?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#can_gschem_do_hierarchical_designs_with_sub_sheets" class="toc">Can gschem do hierarchical designs with sub sheets?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#can_gschem_do_a_hierarchy_where_the_top-level_symbol_points_to_a_multi-page_schematic" class="toc">Can gschem do a hierarchy where the top-level symbol points to a multi-page schematic?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#can_the_hierarchy_be_setup_in_multiple_directories" class="toc">Can the hierarchy be setup in multiple directories?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_declare_a_global_net" class="toc">How do I declare a global net</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_can_options_and_libraries_be_specific_on_subsheet_level" class="toc">How can options and libraries be specific on subsheet level?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#are_there_limitations_to_hierarchy_design" class="toc">Are there limitations to hierarchy design?</a></span></div></li>
+</ul>
+</li>
+<li class="level1"><div class="li"><span class="li"><a href="#gschem_symbols" class="toc">gschem symbols</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#where_do_i_find_symbols_beyond_the_default_library" class="toc">Where do I find symbols beyond the default library?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#what_s_this_business_about_heavy_vs._light_symbols" class="toc">What's this business about heavy vs. light symbols?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#i_am_using_a_symbol_out_of_the_library._how_come_it_s_not_aligned_to_the_grid" class="toc">I am using a symbol out of the library. How come it's not aligned to the grid?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#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" class="toc">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></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_promote_an_invisible_symbol_attribute_into_the_schematic" class="toc">How do I promote an invisible symbol attribute into the schematic?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#what_should_i_do_about_power_pins_on_my_symbolsmake_them_visible_explicit_or_invisible_implicit" class="toc">What should I do about power pins on my symbols: Make them visible (explicit) or invisible (implicit)?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#is_there_a_specification_or_manual_for_creating_gschem_symbols_where_is_it" class="toc">Is there a specification or manual for creating gschem symbols? Where is it?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#is_there_a_symbol_wizard_in_gschem" class="toc">Is there a symbol wizard in gschem?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#can_my_local_library_cover_frequently_needed_sub_circuits" class="toc">Can my local library cover frequently needed sub circuits?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#where_can_i_find_information_on_gschems_file_format" class="toc">Where can I find information on gschems file format?</a></span></div></li>
+</ul>
+</li>
+<li class="level1"><div class="li"><span class="li"><a href="#gschem_configuration_customization" class="toc">Gschem configuration/customization</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_configure_my_local_gafrc_to_find_my_local_symbol_directory" class="toc">How do I configure my local gafrc to find my local symbol directory?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#can_gafrc_use_a_variable_to_set_the_root_of_my_library" class="toc">Can gafrc use a variable to set the root of my library?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#the_library_window_is_cluttered_with_default_symbols._can_i_restrict_to_my_local_lib" class="toc">The library window is cluttered with default symbols. Can I restrict to my local lib?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_can_i_change_the_default_size_of_floating_text" class="toc">How can I change the default size of floating text?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_can_i_have_a_different_background_color_other_than_black" class="toc">How can I have a different background color other than black?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#each_time_i_start_gschem_the_log_message_window_is_shown._can_i_disable_it" class="toc">Each time I start gschem, the log message window is shown. Can I disable it?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#can_i_get_a_customized_title_block_with_new_schematics" class="toc">Can I get a customized title block with new schematics?</a></span></div></li>
+</ul>
+</li>
+<li class="level1"><div class="li"><span class="li"><a href="#printing_output" class="toc">Printing/Output</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_print_schematics_from_the_command_line" class="toc">How do I print schematics from the command line?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_can_i_get_color_postscript_png_output" class="toc">How can I get color postscript/PNG output?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_can_i_get_black_and_white_postscript_png_output" class="toc">How can I get black and white postscript/PNG output?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_can_i_produce_pdf_output" class="toc">How can I produce PDF output?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_can_i_insert_schematics_into_my_latex_document" class="toc">How can I insert schematics into my LaTex document?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_can_i_split_postscript_output_over_multiple_pages" class="toc">How can I split Postscript output over multiple pages?</a></span></div></li>
+</ul>
+</li>
+<li class="level1"><div class="li"><span class="li"><a href="#gschem_installation_run-time_problems" class="toc">Gschem installation/run-time problems</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#gschem_segfaults_when_i_delete_components_on_fc5_and_other_linux_distributions_is_there_a_work-around" class="toc">Gschem segfaults when I delete components on FC5 (and other Linux distributions)! Is there a work-around?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#after_installation_gschem_does_not_work_what_could_be_wrong" class="toc">After installation gschem does not work!? What could be wrong?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#add_components_offers_no_symbols_what_can_i_do_about_it" class="toc">"Add Components" offers no symbols! What can I do about it?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#i_m_using_gschem_gaf_through_a_ssh_connection_and_i_get_an_error_likexlibextension_render_missing_on_display_localhost10.0" class="toc">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></span></div></li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="general" id="general">General</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "General" [1-24] -->
+<h2><a name="i_found_a_bug_what_can_i_do_about_it" id="i_found_a_bug_what_can_i_do_about_it">I found a bug! What can I do about it?</a></h2>
+<div class="level2">
+<ol>
+<li class="level1"><div class="li"> See if you can reproduce the bug.</div>
+</li>
+<li class="level1"><div class="li"> Ask on the <a href="http://www.geda.seul.org/mailinglist/index.html"; class="urlextern" title="http://www.geda.seul.org/mailinglist/index.html"; rel="nofollow">geda-user mailing</a> list if there is a work around, or has been dealt with in the bleeding edge version of gEDA/gaf. Note, that you must subscribe to the geda-user e-mail list before you can post to this list.</div>
+</li>
+<li class="level1"><div class="li"> See whether the issue is already in the <a href="http://sourceforge.net/tracker/?group_id=161080&atid=818426"; class="urlextern" title="http://sourceforge.net/tracker/?group_id=161080&atid=818426"; rel="nofollow">bug tracking system of geda/gaf</a>. If not, file a bug report. Make sure to give all information necessary to reproduce the bug and add the version of gEDA/gaf that contains the bug.</div>
+</li>
+<li class="level1"><div class="li"> Finally, as with all open source projects, you may flex your programming muscles and try to fix the bug yourself. Please file a patch of the changes you had to make to the BTS of geda/gaf. The patch will be gladly accepted to improve the next release of gEDA/gaf.</div>
+</li>
+</ol>
+
+</div>
+<!-- SECTION "I found a bug! What can I do about it?" [25-946] -->
+<h1><a name="gschem_usage" id="gschem_usage">Gschem usage</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "Gschem usage" [947-975] -->
+<h2><a name="there_is_no_symbol_in_the_chooser_dialog" id="there_is_no_symbol_in_the_chooser_dialog">There is no symbol in the chooser dialog!</a></h2>
+<div class="level2">
+
+<p>
+The chooser dialog presents a list of captions of the library sections. Click on the right-pointing triangle to the left of caption. This will expand the list. Scroll down to the symbol you want to add to the schematics.
+</p>
+
+</div>
+<!-- SECTION "There is no symbol in the chooser dialog!" [976-1252] -->
+<h2><a name="how_do_i_move_a_component" id="how_do_i_move_a_component">How do I move a component?</a></h2>
+<div class="level2">
+
+<p>
+ 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>
+</li>
+<li class="level1"><div class="li"> Drag the component (using the left mouse button) to the place you want it.</div>
+</li>
+</ol>
+
+<p>
+ This is probably what you are already used to doing.
+</p>
+
+<p>
+For folks with older versions of gschem, here are three ways to move components within gschem:
+</p>
+
+<p>
+One:
+</p>
+<ol>
+<li class="level1"><div class="li"> Grab the component with the middle mouse button. The component will follow the cursor around as you move it.</div>
+</li>
+<li class="level1"><div class="li"> To place the component, release the middle mouse button. The component will stay where you placed it.</div>
+</li>
+</ol>
+
+<p>
+ Two:
+</p>
+<ol>
+<li class="level1"><div class="li"> Select the component by clicking it with the left mouse button. The component will highlight.</div>
+</li>
+<li class="level1"><div class="li"> Hit the â??Mâ?? key on the keyboard. The component will now follow the cursor around as you move it.</div>
+</li>
+<li class="level1"><div class="li"> To place the component, click the left mouse button. The component will stay where you placed it.</div>
+</li>
+</ol>
+
+<p>
+ Three:
+</p>
+<ol>
+<li class="level1"><div class="li"> Select the component by clicking it with the left mouse button. The component will highlight.</div>
+</li>
+<li class="level1"><div class="li"> Click the right mouse button. A pop-up menu will appear.</div>
+</li>
+<li class="level1"><div class="li"> With the left mouse button, click on the â??moveâ?? option in the pop-up menu.</div>
+</li>
+<li class="level1"><div class="li"> Click on the component with the left mouse button. The component will now follow the cursor around as you move it.</div>
+</li>
+<li class="level1"><div class="li"> To place the component, click the left mouse button. The component will stay where you placed it.</div>
+</li>
+</ol>
+
+</div>
+<!-- SECTION "How do I move a component?" [1253-2687] -->
+<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">
+
+<p>
+Type [or] to toggle this behaviour. That is, the â??oâ?? key followed by the â??râ?? key. The status window will report if the toggle command was performed. The command can also be accessed via the Options menu.
+</p>
+
+</div>
+<!-- SECTION "How do I move components without dragging a tail of connectet nets?" [2688-2973] -->
+<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>
+<li class="level1"><div class="li"> Select the symbol.</div>
+</li>
+<li class="level1"><div class="li"> Right click â?? down symbol (or do Hierarchy â?? down symbol). This takes you to the symbol editor.</div>
+</li>
+<li class="level1"><div class="li"> Select the pinnumber you want to change.</div>
+</li>
+<li class="level1"><div class="li"> Do Edit â?? Edit Text (or type keyboard shortcut â??exâ??).</div>
+</li>
+<li class="level1"><div class="li"> Change the font size in the pop-up box.</div>
+</li>
+<li class="level1"><div class="li"> Repeat for all desired text elements.</div>
+</li>
+<li class="level1"><div class="li"> File â?? save</div>
+</li>
+<li class="level1"><div class="li"> Right click â?? up (or Hierarchy â?? Up). Now you are back in the schematic editor.</div>
+</li>
+<li class="level1"><div class="li"> With the symbol still selected do Edit â?? Update component (or use the keyboard shortcut â??epâ??). If this doesnâ??t work, just delete the symbol and reload it.</div>
+</li>
+</ol>
+
+<p>
+ More generally, you can use this procedure to edit anything on a symbol. (Substitute â??Edit Textâ?? for your desired edit, of course.)
+</p>
+
+</div>
+<!-- SECTION "How do I change the size of the text on a symbol?" [2974-3765] -->
+<h2><a name="is_it_possible_to_overline_text_in_gschem" id="is_it_possible_to_overline_text_in_gschem">Is it possible to overline text in gschem?</a></h2>
+<div class="level2">
+
+<p>
+Yes, overbars are possible. A backslash followed by an an underscore will start an overlined section of text. A second backslash-underscore combo will return to normal text. Example: Double click on an attribute ansd type â??\_this\_â??
+</p>
+
+<p>
+Note, on transfer to pcb, there will be no overline on the layout.The backslash is ignored, which leaves an underscore at the edges of the overlined text.
+</p>
+
+</div>
+<!-- SECTION "Is it possible to overline text in gschem?" [3766-4210] -->
+<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">
+
+<p>
+When a component is locked it cannot be selected with the middle mouse button; however it is selectable using a window select. To window select a component, click and hold the left mouse button and drag the mouse to create a rectangular region containing the component to be unlocked. Execute the command <strong><em>Edit</em></strong> <strong>â??</strong> <strong><em>unLock</em></strong> to unlock the component.
+</p>
+
+</div>
+<!-- SECTION "How do I unlock a locked component" [4211-4625] -->
+<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">
+
+<p>
+Edit the system-gschemrc file or place the following into a gschemrc file (either <strong><code>~/.gEDA/gschemrc</code></strong> or a <strong><code>gschemrc</code></strong> file in the local directory where you invoke gschem):
+</p>
+<pre class="code">
+(load (string-append gedadata "/scheme/auto-uref.scm")) ; load the autonumbering script
+(add-hook! add-component-hook auto-uref) ; autonumber when adding a component
+(add-hook! copy-component-hook auto-uref) ; autonumber when copying a component
+</pre>
+
+<p>
+<strong>Note:</strong> Starting with version 1.2 of gschem the name of the path variable has changed:
+</p>
+<pre class="code">
+(load (string-append geda-data-path "/scheme/auto-uref.scm")) ; load the autonumbering script
+(add-hook! add-component-hook auto-uref) ; autonumber when adding a component
+(add-hook! copy-component-hook auto-uref) ; autonumber when copying a component
+</pre>
+
+</div>
+<!-- SECTION "How can I get refdes automatically numbered when I draw a schematic?" [4626-5530] -->
+<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">
+
+<p>
+ A â??busâ?? is purely decoration. The netlister ignores it. The netname= attribute does actual work of connecting points together–this is what gnetlist reads and transforms into your netlist. It is not possible to connect to a discrete line or â??bitâ?? on a bus because, again, the bus is merely a graphical entity.
+</p>
+
+<p>
+Some users have found it helpful to organize their nets by incorporating a bus name into the net name. For example â??net=busA:1â?? may be added to each busripper to aid in sorting out the nets.
+</p>
+
+</div>
+<!-- SECTION "What is a Bus and how do I use it?" [5531-6086] -->
+<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">
+
+<p>
+Key accels are determined by configuration files read on start-up. The default key bindings are set in the file system-gschemrc. If you want to change them, it is recommended to copy and modify the corresponding keymap section to a local config file ($HOME/.gEDA/gschemrc, or $PWD/gschemrc). The modified section will override the the definitions given in system-gschemrc.
+</p>
+
+</div>
+<!-- SECTION "How can I change Key Bindings in gschem?" [6087-6513] -->
+<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">
+
+<p>
+By default you get:
+</p>
+<ul>
+<li class="level1"><div class="li"> Left mouse button is used for picking and drawing.</div>
+</li>
+<li class="level1"><div class="li"> Middle mouse button is either move object (just hold down the middle button over an object and move the mouse) or copy object (ALT key held down while holding down the middle button over object and move the mouse).</div>
+</li>
+<li class="level1"><div class="li"> Right mouse button is a popup menu.</div>
+</li>
+</ul>
+
+<p>
+ You can change the middle button by adding the following to a gschemrc file:
+</p>
+<pre class="code">(middle-button "action") ;default binding, move or copy an object</pre>
+
+<p>
+or:
+</p>
+<pre class="code">(middle-button "stroke") ;draw mouse gestures/strokes (must install libstroke to enable</pre>
+
+<p>
+or:
+</p>
+<pre class="code">(middle-button "repeat") ;repeat the last command executed</pre>
+
+<p>
+You can change the right button by adding the following to a gschemrc file:
+</p>
+<pre class="code">(third-button "popup") ;default binding, show a popup menu</pre>
+
+<p>
+or:
+</p>
+<pre class="code">(third-button "mousepan") ;use the mouse to pan around the schematic</pre>
+
+<p>
+For more information on these options, please see the <code>${install_prefix}/share/gEDA/system-gschemrc</code> file.
+</p>
+
+</div>
+<!-- SECTION "What are the mouse bindings in gschem?" [6514-7597] -->
+<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">
+
+<p>
+Yes. Sub sheets are represented by special symbols on the top level schematic. You can find an example for a hierarchical design in the doc section of gschem (<code>geda-doc/examples/gTAG/gTAG.sch</code>). Currently, there is no way to automatically build a sub sheet symbol from an actual sub sheet. The sub sheet symbol has to be drawn manually. Any patches or external scripts that get the job done would be greatly appreciated.
+</p>
+
+<p>
+A <code>source=</code> attribute attached to the sub sheet symbol gives the path to the sub sheet file. The pins of the symbol correspond to ports from top sheet to sub sheet. These ports should correspond to a refdes of a port symbol on the sub sheet. The port symbols in the default library of geda are <code>in-1.sym</code> and <code>out-1.sym</code>. Use the hierarchy menu to navigate within the hierarchy of sub sheets. Alternatively, you can navigate with the page manager.
+</p>
+
+<p>
+To convert a hierarchy to a netlist just call gsch2pcb on the top level schematic. By default, net names and refdesâ??s of components are strictly local to the subsheet. They get the sub sheet symbol refdes as a prefix when inserted into the net list. You can even use multiple instances of a sub sheet symbol without undue short cuts. Whether or not net names and refdesâ??s are mangled and thus local to the sub sheet can be configured in the config file gnetlistrc. Copy the corresponding lines from <code>system-gnetlistrc</code> to <code>gnetlistrc</code> in the current working directory or to <code>$HOME/.gEDA/gnetlistrc</code>. A convenient configuration is to make nets delivered by power symbols global while ordinary nets remain local to the sub sheet. This can be achieved with â??hierarchy-netattrib-mangleâ?? enabled.
+</p>
+
+</div>
+<!-- SECTION "Can gschem do hierarchical designs with sub sheets?" [7598-9340] -->
+<h2><a name="can_gschem_do_a_hierarchy_where_the_top-level_symbol_points_to_a_multi-page_schematic" id="can_gschem_do_a_hierarchy_where_the_top-level_symbol_points_to_a_multi-page_schematic">Can gschem do a hierarchy where the top-level symbol points to a multi-page schematic?</a></h2>
+<div class="level2">
+
+<p>
+Yes. Just attach the <code>source=</code> attribute multiple times with different values. Drill down into the schematic from the symbol, then use [page-up] / [page-down] to navigate through the pages on that level.
+</p>
+
+</div>
+<!-- SECTION "Can gschem do a hierarchy where the top-level symbol points to a multi-page schematic?" [9341-9648] -->
+<h2><a name="can_the_hierarchy_be_setup_in_multiple_directories" id="can_the_hierarchy_be_setup_in_multiple_directories">Can the hierarchy be setup in multiple directories?</a></h2>
+<div class="level2">
+
+<p>
+Yes. Make sure, the <code>(source-library "…â??)</code> and <code>(component-library "…â??)</code> declarations in your gafrc file list the appropriate paths.
+</p>
+
+</div>
+<!-- SECTION "Can the hierarchy be setup in multiple directories?" [9649-9854] -->
+<h2><a name="how_do_i_declare_a_global_net" id="how_do_i_declare_a_global_net">How do I declare a global net</a></h2>
+<div class="level2">
+
+<p>
+All netnames are global with regard to the current sheet. Whether or not netnames are global in a hierarchical stack of schematics, depends on the settings in gnetlistrc. This file can reside in $HOME/.gEDA or locally next to the schematics. Defaults are set in system-gschemrc. Copy the respective lines to your local gnetlistrc, if you want a different behavior.
+</p>
+
+<p>
+There is no way to make individual netnames global. However, you can differentiate between netnames granted to nets the netname attribute and netnames defined by the net attribute. This aims at power symbols, which set their net with the net attribute. That way, you donâ??t need to hand the power nets in the sub sheet symbols.
+</p>
+
+</div>
+<!-- SECTION "How do I declare a global net" [9855-10590] -->
+<h2><a name="how_can_options_and_libraries_be_specific_on_subsheet_level" id="how_can_options_and_libraries_be_specific_on_subsheet_level">How can options and libraries be specific on subsheet level?</a></h2>
+<div class="level2">
+
+<p>
+When opening schematics, libgeda changes directory. So it should load any gafrc in the sub-dirs too, as and when the schematics are processed.
+</p>
+
+</div>
+<!-- SECTION "How can options and libraries be specific on subsheet level?" [10591-10807] -->
+<h2><a name="are_there_limitations_to_hierarchy_design" id="are_there_limitations_to_hierarchy_design">Are there limitations to hierarchy design?</a></h2>
+<div class="level2">
+
+<p>
+Although support for subsheets covers many aspects of hierachical design, there are some limitations:
+</p>
+<ul>
+<li class="level1"><div class="li"> Buses cannot connect into subsheets. </div>
+</li>
+<li class="level1"><div class="li"> There is no <acronym title="Graphical User Interface">GUI</acronym> way to start subsheets. You need to manually create a seperate symbol for each subsheet. </div>
+</li>
+</ul>
+
+<p>
+Feel free to fix these issues. Contributions are welcome.
+</p>
+
+</div>
+<!-- SECTION "Are there limitations to hierarchy design?" [10808-11177] -->
+<h1><a name="gschem_symbols" id="gschem_symbols">gschem symbols</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "gschem symbols" [11178-11209] -->
+<h2><a name="where_do_i_find_symbols_beyond_the_default_library" id="where_do_i_find_symbols_beyond_the_default_library">Where do I find symbols beyond the default library?</a></h2>
+<div class="level2">
+
+<p>
+There is a website <a href="http://www.gedasymbols.org/"; class="urlextern" title="http://www.gedasymbols.org/"; rel="nofollow">gedasymbols.org</a> dedicated to user contributed resources for gEDA. You can search the site, preview symbols and download them individually. If you have configured your gafrc files accordingly you can put the symbols right next to the schematics file of your project. You might want to build a local library of symbols, so all projects can access the new symbols. See <a href="geda-faq-gschem.html#can_gafrc_use_a_variable_to_set_the_root_of_my_library" class="wikilink1" title="geda-faq-gschem.html">below</a> for the details.
+</p>
+
+<p>
+You can even download all user contributed content from gedasymbols. See the instructions on how to <a href="http://www.gedasymbols.org/cvs.html"; class="urlextern" title="http://www.gedasymbols.org/cvs.html"; rel="nofollow">access gedasymbols using CVS</a>.
+</p>
+
+</div>
+<!-- SECTION "Where do I find symbols beyond the default library?" [11210-11956] -->
+<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">
+
+<p>
+This nomenclature arose from a discussion which frequently appears on the geda-user and geda-dev mailing lists. A light symbol is one which contains very few built-in attributes in the symbol itself. It requires that the user attach almost all attributes at the schematic level (e.g. using either gschem or gattrib). A heavy symbol is one which contains many attributes (such as package footprints, SPICE model names, etc.) built into the symbol file itself. A heavy symbol therefore requires very little attribute attachment at the schematic level â?? you just place it and youâ??re done.
+</p>
+
+<p>
+The debate between proponents of heavy and light symbols is very detailed and involved. Briefly, proponents of heavy symbols believe that they provide better integration between gschem and PCB since the important layout attributes (such as <a href="geda-pcb_tips.html#i_want_to_use_pcb_to_do_layout._how_do_i_know_what_value_to_use_for_the_footprint_attribute" class="wikilink1" title="geda-pcb_tips.html">footprint name</a>) are already built into the symbol. This is considered a good thing for new users (noobs) who just want to design a simple board and donâ??t appreciate or donâ??t care about the zillions of variations that even a simple resistor might have (e.g. different footprint, TCR, precision, material composition, etc). Proponents of light symbols prefer to deal with attributes at the schematic level because they believe it to be more flexible. They are quick to point out that a library of heavy symbols will quickly grow into the thousands of parts with grotesquely long names trying to distinguish between the different variations of the part. They also point out that the utility â??gattribâ?? is the preferred tool for dealing with attributes at the schematic level (i.e. in the .sch file).
+</p>
+
+<p>
+GEDA/gaf, as default configured, uses light symbols, although it can be configured to use heavy symbols. For further information, you may read these dicussions from the geda-user mailing list:
+</p>
+
+<p>
+<a href="http://archives.seul.org/geda/user/Jun-2005/msg00001.html"; class="urlextern" title="http://archives.seul.org/geda/user/Jun-2005/msg00001.html"; rel="nofollow">http://archives.seul.org/geda/user/Jun-2005/msg00001.html</a>
+</p>
+
+<p>
+<a href="http://archives.seul.org/geda/dev/Oct-2005/msg00043.html"; class="urlextern" title="http://archives.seul.org/geda/dev/Oct-2005/msg00043.html"; rel="nofollow">http://archives.seul.org/geda/dev/Oct-2005/msg00043.html</a>
+</p>
+
+<p>
+<a href="http://archives.seul.org/geda/user/Dec-2007/msg00146.html"; class="urlextern" title="http://archives.seul.org/geda/user/Dec-2007/msg00146.html"; rel="nofollow">http://archives.seul.org/geda/user/Dec-2007/msg00146.html</a>
+</p>
+
+</div>
+<!-- SECTION "What's this business about heavy vs. light symbols?" [11957-14148] -->
+<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">
+
+<p>
+The symbols in the symbol library, like those available at the <a href="http://www.gedasymbols.org"; class="urlextern" title="http://www.gedasymbols.org"; rel="nofollow"> gedasymbols</a> website are contributed by users just like you. Some people use different grid settings than other people (e.g. 50mil vs. 100mil). If you discover a symbol which seems to be off the grid, try reducing your grid spacing, move the symbol so that it sits on <strong>your</strong> grid, then revert to your preferred grid settings.
+</p>
+
+<p>
+Yes, the gEDA docs suggest that you use a 100mil grid spacing. But everybody likes to do things their own way, and there is no overall symbol dictator to enforce the rules on contributed symbols. Therefore, you just need to be aware of this possibility.
+</p>
+
+</div>
+<!-- SECTION "I am using a symbol out of the library. How come it's not aligned to the grid?" [14149-14922] -->
+<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">
+
+<p>
+Answer: misc â?? nc-left, nc-right, nc-top, nc-bottom.
+</p>
+
+<p>
+Caution: occassionally this may create a net called â??no_connectâ?? (or â??NC??") which may lead to no-connect pins being connected together in gnetlist â?? which you probably _donâ??t_ want to happen.
+</p>
+
+<p>
+If you want an entire symbol to be graphical (no elec. connections) , add a â??graphical=1â?? attribute. The netlister will ignore these symbols entirely.
+</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?" [14923-15493] -->
+<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">
+
+<p>
+Most attributes living in the symbol do not get promoted to the schematic unless they are visible. To promote invisible symbol attributes, look for the following keywords in the system-gafrc file:
+</p>
+<pre class="code">(attribute-promotion "enabled");
+(promote-invisible "disabled") ; â?? This one
+(keep-invisible "enabled")</pre>
+
+<p>
+Add to your gafrc file:
+</p>
+<pre class="code">(promote-invisible "enabled")</pre>
+
+<p>
+and you will get all the attributes promoted. The â??keep-invisibleâ?? keyword will keep hidden those attributes that are hidden in the symbol file.
+</p>
+
+</div>
+<!-- SECTION "How do I promote an invisible symbol attribute into the schematic?" [15494-16107] -->
+<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">
+
+<p>
+In the past, digital logic circuits often hid the power pin, and attached power nets using an attribute inside the symbol. Modern thought is that this is a bad practice (although religious wars still occasionally rage about this topic).
+</p>
+
+<p>
+Itâ??s marginally OK for an old logic circuit which is all 5V TTL to have hidden power and GND pins. If you only have +5V on your board, then hiding the power pin can simplify your schematic somewhat. However, few designers design such circuits nowadays; 5V TTL (and 5V CMOS) are rapidly becoming antique technologies.
+</p>
+
+<p>
+Itâ??s always been unacceptable to hide the power pins on analog chips. First, analog often has multiple power connections (VCC, VEE) which need to be explicitly drawn out. Second, good design practice is to place decoupling caps on each and every power pin. Sometimes one places an inductor in series with power also. Since these should be drawn into the schematic, it is best done by attaching them to an explicit power pin. Therefore, one should never use hidden power pins for analog symbols.
+</p>
+
+<p>
+New logic circuits often use multiple supplies for different chip sections (OVDD, DVDD, etc). It is also typical to have several logic families on a single board (5V, 3.3V etc.). Therefore, itâ??s best to explicitly place and wire the power pins on the symbol. Hidden power pins are a recipe for disaster since you can all too easily misconnect a 5V part to a 3.3V power net, for example.
+</p>
+
+<p>
+To paraphrase Nancy Reagan: Just say â??noâ?? to hidden power pins.
+</p>
+
+<p>
+That said, it may still be useful to detach the power pins from the functional part of the symbol. To do so, define a seperate power symbol and give it the same <a href="geda-glossary.html" class="wikilink1" title="geda-glossary.html">refdes</a> as the functional part. A run of gsch2pcb will treat the siblings properly as one single component. As neither gschem nor gsch2pcb explicitely know that the component is only complete with both symbols defined, you have to check yourself. With this workaround, you can draw all power related circuitry in one corner of the schematic where it does not interfere with the signal nets. In many cases this is advantageous with analog circuits.
+</p>
+
+</div>
+<!-- SECTION "What should I do about power pins on my symbols: Make them visible (explicit) or invisible (implicit)?" [16108-18365] -->
+<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">
+
+<p>
+Yes. It is the <a href="geda-scg.html" class="wikilink1" title="geda-scg.html">Symbol Creation Guide</a>.
+</p>
+
+</div>
+<!-- SECTION "Is there a specification or manual for creating gschem symbols? Where is it?" [18366-18507] -->
+<h2><a name="is_there_a_symbol_wizard_in_gschem" id="is_there_a_symbol_wizard_in_gschem">Is there a symbol wizard in gschem?</a></h2>
+<div class="level2">
+
+<p>
+There is no wizard included in the gschem-<acronym title="Graphical User Interface">GUI</acronym>. But there are scripts which automatically create symbols from parameters given in a config file. One of these scripts is <a href="geda-tragesym_readme.html" class="wikilink1" title="geda-tragesym_readme.html">tragesym</a>. It is part of the default installation of geda. A short <a href="geda-tragesym_tutorial.html" class="wikilink1" title="geda-tragesym_tutorial.html">tutorial</a> will get you started with this tool.
+</p>
+
+<p>
+One of the major contributors to the project wrote his own symbol creation script: <a href="http://www.gedasymbols.org/user/dj_delorie/tools/djboxsym.html"; class="urlextern" title="http://www.gedasymbols.org/user/dj_delorie/tools/djboxsym.html"; rel="nofollow">djboxsym</a>
+</p>
+
+</div>
+<!-- SECTION "Is there a symbol wizard in gschem?" [18508-19041] -->
+<h2><a name="can_my_local_library_cover_frequently_needed_sub_circuits" id="can_my_local_library_cover_frequently_needed_sub_circuits">Can my local library cover frequently needed sub circuits?</a></h2>
+<div class="level2">
+
+<p>
+Yes, symbols can contain symbols and nets.
+</p>
+<ol>
+<li class="level1"><div class="li"> Copy the subcircuit to a fresh sheet. (unlock and remove the default title block as you wonâ??t need it)</div>
+</li>
+<li class="level1"><div class="li"> The values of refdes attributes should end with "?", to allow to auto number them later. </div>
+</li>
+<li class="level1"><div class="li"> Move the sub circuit to the lower left of the available space. (You can use symbol-translate from the edit menu)</div>
+</li>
+<li class="level1"><div class="li"> Save the sub circuit as a *.sym file in your local library. </div>
+</li>
+<li class="level1"><div class="li"> Choose â??Include component as individual objectsâ?? when selecting this complex symbol for your actual schematic. The whole sub circuit will be pasted to your sheet. Be sure to switch back to the default mode for inclusion of ordinary symbols. </div>
+</li>
+</ol>
+
+</div>
+<!-- SECTION "Can my local library cover frequently needed sub circuits?" [19042-19787] -->
+<h2><a name="where_can_i_find_information_on_gschems_file_format" id="where_can_i_find_information_on_gschems_file_format">Where can I find information on gschems file format?</a></h2>
+<div class="level2">
+
+<p>
+Unlike many other EDA software, the format of gschem is strictly human readable <acronym title="American Standard Code for Information Interchange">ASCII</acronym>. This is deliberate, to facilate scripting. It also allows for quick fixes with the text editor. The format of gschem files ist described <a href="geda-file_format_spec.html" class="wikilink1" title="geda-file_format_spec.html">here</a>.
+</p>
+
+</div>
+<!-- SECTION "Where can I find information on gschems file format?" [19788-20104] -->
+<h1><a name="gschem_configuration_customization" id="gschem_configuration_customization">Gschem configuration/customization</a></h1>
+<div class="level1">
+
+<p>
+Gschem is configurable in more ways than can be describe here. Look at â??system-gschemrcâ?? for suggestions what else can be done.
+</p>
+
+</div>
+<!-- SECTION "Gschem configuration/customization" [20105-20283] -->
+<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>
+<li class="level1"><div class="li"> Create a project directory, for example ${HOME}/myproj.</div>
+</li>
+<li class="level1"><div class="li"> Place the symbols you want to use into ${HOME}/myproj/symbols.</div>
+</li>
+<li class="level1"><div class="li"> Create a gafrc file in ${HOME}/myproj.</div>
+</li>
+<li class="level1"><div class="li"> In gafrc, put this line: <pre class="code"> (component-library "./symbols") </pre>
+</div>
+</li>
+<li class="level1"><div class="li"> Run gschem from your project directory ${HOME}/myproj. That is, do this to run gschem:<pre class="code">cd ${HOME}/myproj
+gschem myschematic.sch</pre>
+</div>
+</li>
+</ol>
+
+<p>
+ Points to remember:
+</p>
+<ul>
+<li class="level1"><div class="li"> The guile stuff which processes your RC file doesnâ??t understand or expand shell wildcards like "~" or ${HOME}. It does understand "." as the current working directory, and it does understand absolute file paths. If you want to do something tricky, you can try to use Scheme functions to get directory information.</div>
+</li>
+<li class="level1"><div class="li"> Make sure gafrc lives in your main project directory. </div>
+</li>
+<li class="level1"><div class="li"> Run all gEDA programs from your main project directory. </div>
+</li>
+<li class="level1"><div class="li"> Run the programs from the command line in a terminal shell – donâ??t use any whizzy, shiny desktop icons to run gschem (if you have them) since you wonâ??t know what directory gschem is starting in, and gschem might not find gafrc.</div>
+</li>
+<li class="level1"><div class="li"> The key is: start gschem in the same directory as where your gafrc lives.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "How do I configure my local gafrc to find my local symbol directory?" [20284-21538] -->
+<h2><a name="can_gafrc_use_a_variable_to_set_the_root_of_my_library" id="can_gafrc_use_a_variable_to_set_the_root_of_my_library">Can gafrc use a variable to set the root of my library?</a></h2>
+<div class="level2">
+
+<p>
+Currently (v1.3.1) gschem does not descend into subdirectories of the symbol library. You have to give individually each and every directory of your local lib in your gafrc file. However, you donâ??t have to repeat the absolute base path over and over. You can use the function â??build-pathâ?? to concatenate the path on the fly:
+</p>
+<pre class="code">(define gedasymbols "/path/to/local/library")
+(component-library (build-path gedasymbols "analog"))
+(component-library (build-path gedasymbols "block"))
+(component-library (build-path gedasymbols "connector"))</pre>
+
+</div>
+<!-- SECTION "Can gafrc use a variable to set the root of my library?" [21539-22155] -->
+<h2><a name="the_library_window_is_cluttered_with_default_symbols._can_i_restrict_to_my_local_lib" id="the_library_window_is_cluttered_with_default_symbols._can_i_restrict_to_my_local_lib">The library window is cluttered with default symbols. Can I restrict to my local lib?</a></h2>
+<div class="level2">
+
+<p>
+Put a localized version of the following lines in a gafrc.
+</p>
+<pre class="code">
+; empty the library path and populate it with local paths
+(reset-component-library)
+(component-library "/foo/localgedalib1")
+(component-library "/bar/foo/localgedalib2")
+</pre>
+
+<p>
+ You have to add each and every dir of your local library. Subdirs are not automatically reckognized by gschem and gsch2pcb. Its a good idea to place this gafrc in your projects dir. That way, if you start gschem from some other place, you still get the system symbols shown. This also allows to configure special symbol libs for specific projects.
+</p>
+
+</div>
+<!-- SECTION "The library window is cluttered with default symbols. Can I restrict to my local lib?" [22156-22847] -->
+<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">
+
+<p>
+Put
+</p>
+<pre class="code">(text-size 10)</pre>
+
+<p>
+ into your gschemrc and replace â??10â?? with your favorite size.
+</p>
+
+</div>
+<!-- SECTION "How can I change the default size of floating text?" [22848-23006] -->
+<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">
+
+<p>
+Edit the system-gschemrc file and near the top you will find lines like:
+</p>
+<pre class="code">;
+; Start of color section
+;
+; Load up a color scheme has a light (almost white) background
+; Comment out the first line and comment in the second line for a
+; dark (black) background. The dark background is the original look.
+;
+(load (string-append gedadatarc "/gschem-darkbg")) ; dark background
+;(load (string-append gedadatarc "/gschem-lightbg")) ; light background</pre>
+
+<p>
+Comment out the <strong><code>darkbg</code></strong> line (with a ;) and comment in the <strong><code>lightbg</code></strong> line. This will give you a light background instead of a black background. It also adjust all the other colors to be compatible with a light background.
+</p>
+
+<p>
+Note, starting with version 1.2 of gschem the syntax of this line changed to
+</p>
+<pre class="code">(load (build-path geda-rc-path "gschem-lightbg")) ; light background</pre>
+
+<p>
+ If you want more control over the colors, please edit <strong><code>${prefix}/share/gEDA/gschem-darkbg</code></strong> or <strong><code>${prefix}/share/gEDA/gschem-lightbg</code></strong> or create your own file and load it in the <strong><code>system-gschemrc</code></strong> file.
+</p>
+
+<p>
+A dark background is preferred by many users.
+</p>
+
+</div>
+<!-- SECTION "How can I have a different background color other than black?" [23007-24205] -->
+<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">
+
+<p>
+In the system-gschemrc file, you will find the following section:
+</p>
+<pre class="code">
+; log-window string
+;
+; Controls if the log message window is mapped when gschem is started up
+; Possible options:
+; startup - opened up when gschem starts
+; later - NOT opened up when gschem starts
+; (can be opened by Options/Show Log Window)
+;
+(log-window "startup")
+;(log-window "later")</pre>
+
+<p>
+Comment out the <strong><code>startup</code></strong> line (with a ;) and comment in the <strong><code>later</code></strong> line, or add the following line to your gschemrc file:
+</p>
+<pre class="code">(log-window "later")</pre>
+
+</div>
+<!-- SECTION "Each time I start gschem, the log message window is shown. Can I disable it?" [24206-24868] -->
+<h2><a name="can_i_get_a_customized_title_block_with_new_schematics" id="can_i_get_a_customized_title_block_with_new_schematics">Can I get a customized title block with new schematics?</a></h2>
+<div class="level2">
+
+<p>
+Put the following line into your gschemrc file:
+</p>
+<pre class="code">(define default-titleblock "title-A3.sym")</pre>
+
+<p>
+ Replace â??title-A3.symâ?? with the file name of your favorite title block symbol.
+</p>
+
+</div>
+<!-- SECTION "Can I get a customized title block with new schematics?" [24869-25121] -->
+<h1><a name="printing_output" id="printing_output">Printing/Output</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "Printing/Output" [25122-25152] -->
+<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">
+
+<p>
+Running the script <strong><code>print.scm</code></strong> will create the Postscript file that is specified on the command line.
+</p>
+
+<p>
+The command line below creates a Postscript file from a schematic file (replace MY_SCH with the name of your schematic and GEDA_SCHEME_DIR with the name of the directory where your gEDA scheme files are installed):
+</p>
+<pre class="code">gschem -p -oMY_SCH.ps -sGEDA_SCHEME_DIR/print.scm MY_SCH.sch</pre>
+
+<p>
+The <code>bash</code> script below, which I name <strong><code>gschem-print</code></strong>, creates a Postscript file for each schematic file that is specified on the command line and then outputs each Postscript file to the default printer:
+</p>
+<pre class="code">#!/bin/bash
+
+# gschem options
+# -oPS_FILENAME output to Postscript file PS_FILENAME
+# -sSCRIPT_FILENAME run script SCRIPT_FILENAME
+# -p autoplace windows
+
+for name in $*
+do
+ base="${name%.*}"
+ gschem -p -o$base.ps -sGEDA_SCHEME_DIR/print.scm $base.sch
+ lpr -P$PRINTER $base.ps
+done</pre>
+
+<p>
+The default printing size is used when printing from the command line. To set the default printing size to A4 add
+</p>
+<pre class="code">(paper-size 11.69 8.27) ; A4</pre>
+
+<p>
+ to your <code>gschemrc</code> in <code>$(HOME)/.gEDA</code> (or in the local directory <code>gschemrc</code>). The full list of paper-size options can be found in <code>system-gschemrc</code>.
+</p>
+
+</div>
+<!-- SECTION "How do I print schematics from the command line?" [25153-26443] -->
+<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">
+
+<p>
+Edit the <strong><code>system-gschemrc</code></strong> file or place the following into a <strong><code>gschemrc</code></strong> file (either <strong><code>~/.gEDA/gschemrc</code></strong> or a <strong><code>gschemrc</code></strong> file in the local directory where you invoke gschem):
+</p>
+<pre class="code">(output-color "enabled") ; for color postscript output
+(image-color "enabled") ; for color PNG output (enabled by default)</pre>
+
+<p>
+To control the background of the PS output, change the following line in either gschem-darkbg (for the default black colored background) or gschem-lightbg (for the alternative light colored background):
+</p>
+<pre class="code">(output-color-background 16 "black" "null" "0 0 0" 0 0 0)</pre>
+
+<p>
+The â??0 0 0â?? is the RGB components (between 0..1) for the background color of the PS output.
+</p>
+
+<p>
+To control the background of the <acronym title="Portable Network Graphics">PNG</acronym> output, change the following line in either gschem-darkbg (for the default black colored background) or gschem-lightbg (for the alternative light colored background):
+</p>
+<pre class="code">(background-color 0 "grey94" "null" "1 1 1" 255 255 255)</pre>
+
+<p>
+The 255 255 255 are the RGB components for the background color of the <acronym title="Portable Network Graphics">PNG</acronym> image.
+</p>
+
+</div>
+<!-- SECTION "How can I get color postscript/PNG output?" [26444-27576] -->
+<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">
+
+<p>
+For black and white PS output, place the following into a gschemrc file:
+</p>
+<pre class="code">(output-color "disabled") ; for monochrome postscript output</pre>
+
+<p>
+For black and white <acronym title="Portable Network Graphics">PNG</acronym> images, place the following into a gschemrc file:
+</p>
+<pre class="code">(image-color "disabled") ; for monochromoe PNG output</pre>
+
+</div>
+<!-- SECTION "How can I get black and white postscript/PNG output?" [27577-27942] -->
+<h2><a name="how_can_i_produce_pdf_output" id="how_can_i_produce_pdf_output">How can I produce PDF output?</a></h2>
+<div class="level2">
+
+<p>
+There are different ways to produce <acronym title="Portable Document Format">PDF</acronym> in gschem:
+</p>
+<ol>
+<li class="level1"><div class="li"> Print to file as Postscript and externally convert to <acronym title="Portable Document Format">PDF</acronym>. The utility ps2pdf needs the option -sPAPERSIZE=a4</div>
+</li>
+<li class="level1"><div class="li"> Use a <acronym title="Portable Document Format">PDF</acronym>-Printer installed on the system.</div>
+</li>
+</ol>
+
+<p>
+ The second option is more convenient, but needs a little more administration.
+</p>
+
+<p>
+In a gnome environment a prerequisite to make this work is the package cups-pdf. A <acronym title="Portable Document Format">PDF</acronym> printer called â??CUPS-<acronym title="Portable Document Format">PDF</acronym>-Printerâ?? should be configured as a â??Local Printerâ?? via the usual CUPS interface. Choose Manufacturer â??Genericâ??, model â??CUPS-<acronym title="Portable Document Format">PDF</acronym>-Printerâ??. Add this line to the local gschemrc to make the lp print command default in gschem:
+</p>
+<pre class="code">(print-command "lp -d CUPS-PDF-Printer")</pre>
+
+<p>
+ The resulting <acronym title="Portable Document Format">PDF</acronym> will go to $HOME/<acronym title="Portable Document Format">PDF</acronym> by default.
+</p>
+
+<p>
+In a KDE environment the print command is â??kprinterâ?? with the output option set to <acronym title="Portable Document Format">PDF</acronym> is the way to go. So you need to add this line to the local gschemrc:
+</p>
+<pre class="code">(print-command "kprinter")</pre>
+
+</div>
+<!-- SECTION "How can I produce PDF output?" [27943-28915] -->
+<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>
+<li class="level1"><div class="li"> Print the schematic to a file. This will be generic postscript (*.ps).</div>
+</li>
+<li class="level1"><div class="li"> Convert the postscript file to epsi with the tool ps2epsi. This is a script from the ghostscript suite.</div>
+</li>
+<li class="level1"><div class="li"> Include usepackage{graphicx} to the preamble of your latex document. Use the command <strong>includegraphics</strong> to place your schematic.</div>
+</li>
+</ol>
+
+<p>
+ A simple example:
+</p>
+<pre class="code">\documentclass{article}
+\usepackage{graphicx}
+\begin{document}
+ \begin{image}
+ \includegraphics[width=100mm]{ModulPID.epsi}
+ \end{image}
+\end{document}</pre>
+
+</div>
+<!-- SECTION "How can I insert schematics into my LaTex document?" [28916-29484] -->
+<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">
+
+<p>
+gschem does not provide this functionality internally, however there is a program called â??posterâ?? which does exactly this. It can be downloaded from either <a href="http://www.gnu.org/directory/poster.html"; class="urlextern" title="http://www.gnu.org/directory/poster.html"; rel="nofollow">here</a> (GNU) or <a href="http://printing.kde.org/downloads/"; class="urlextern" title="http://printing.kde.org/downloads/"; rel="nofollow">here</a> (KDE Print).
+</p>
+
+</div>
+<!-- SECTION "How can I split Postscript output over multiple pages?" [29485-29828] -->
+<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" [29829-29881] -->
+<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">
+
+<p>
+This bug emerged in mid 2006 for users of Fedora Core 5 (and other linux distributions that use glib 2.10.x). The bug has been fixed by the developers; the latest versions of gEDA/gaf (i.e. Oct 2006 and beyond) shouldnâ??t have this problem.
+</p>
+
+<p>
+If you happen to have an older version of gEDA/gaf, you can work around this bug by setting the environment variable G_SLICE to â??always-mallocâ??. Specifically, before you run gschem, do this:
+</p>
+
+<p>
+bash:
+</p>
+<pre class="code">export G_SLICE=always-malloc</pre>
+
+<p>
+csh:
+</p>
+<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?" [29882-30536] -->
+<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">
+
+<p>
+If you run gschem and you get a window without a menu bar, no colors, and the program terminates when you press a key with the following message:
+</p>
+<pre class="code">ERROR: Unbound variable: current-keymap</pre>
+
+<p>
+Or you get errors like this:
+</p>
+<pre class="code">Gtk-CRITICAL : file gtkpixmap.c: line 97 (gtk_pixmap_new): assertion `val != NULLâ?? failed.
+Gtk-CRITICAL : file gtkpixmap.c: line 97 (gtk_pixmap_new): assertion `val != NULLâ?? failed.
+Tried to get an invalid color: 0
+Tried to get an invalid color: 7
+Tried to get an invalid color: 0
+Tried to get an invalid color: 7</pre>
+
+<p>
+then gschem is not finding an rc file. There are two required rc files. The first is <strong><code>system-gschemrc</code></strong> and the second is <strong><code>system-commonrc</code></strong>.
+</p>
+<ul>
+<li class="level1"><div class="li"> The system-gschemrc rc file should be installed when you install gschem and typically resides in <strong><code>${prefix}/share/gEDA/system-gschemrc</code></strong>. <strong><code>${prefix}</code></strong> is where you installed gschem (usually <strong><code>/usr</code></strong> or <strong><code>/usr/local</code></strong> or <strong><code>$HOME/geda</code></strong>). This file can also be installed in /etc/gEDA (the .debs packages do this).</div>
+</li>
+<li class="level1"><div class="li"> The system-commonrc rc file should be installed when you install the symbol library for gEDA/gaf. It resides in <strong><code>${prefix}/share/gEDA/system-commonrc</code></strong>. This file can also be installed in <strong><code>/etc/gEDA</code></strong> (the .debs packages do this). This file is not loaded directly by gschem. It is loaded by a â??(load …)â?? in the system-gschemrc rc file.</div>
+</li>
+</ul>
+
+<p>
+ Make sure these file are installed. The gschem.log file (which is created everytime you run gschem) holds valuable debugging information which should help in determining what is wrong. Check this file for where gschem is looking for the rc files.
+</p>
+
+<p>
+Also, some older releases of gEDA/gaf had some bugs when the rc files were installed in other locations (other that <strong><code>${prefix}/share/gEDA</code></strong>), so please upgrade to a more current release.
+</p>
+
+</div>
+<!-- SECTION "After installation gschem does not work!? What could be wrong?" [30537-32461] -->
+<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">
+
+<p>
+Make sure that at least one of your config files contains a valid path to a symbol library. At startup, gschem checks for the following config files (on a Debian system):
+</p>
+<ol>
+<li class="level1"><div class="li"> distributed system-wide gafrc file: <code>/etc/gEDA/system-gafrc</code> (will be overwritten on update)</div>
+</li>
+<li class="level1"><div class="li"> local system-wide gafrc file <code>/usr/share/gEDA/gafrc.d/gafrc</code> (with geda versions after summer 2009)</div>
+</li>
+<li class="level1"><div class="li"> user gafrc file: <code>~/.gEDA/gafrc</code></div>
+</li>
+<li class="level1"><div class="li"> local gafrc file: <code>$PWD/gafrc</code></div>
+</li>
+<li class="level1"><div class="li"> system gschemrc file: <code>/etc/gEDA/system-gschemrc</code></div>
+</li>
+<li class="level1"><div class="li"> user gschemrc file: <code>~/.gEDA/gschemrc</code></div>
+</li>
+<li class="level1"><div class="li"> local gschemrc file: <code>$PWD/gschemrc</code></div>
+</li>
+</ol>
+
+<p>
+All of these config files may or may not append paths to the library search list. If a config file contains the command
+</p>
+<pre class="code">(reset-component-library)</pre>
+
+<p>
+ the library search path will be emptied. Order is obviously important, as this command will erase any previously appended paths.
+</p>
+
+</div>
+<!-- SECTION "Add Components offers no symbols! What can I do about it?" [32462-33420] -->
+<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">
+
+<p>
+ If you are getting into the remote machine by doing:
+</p>
+<pre class="code">$ ssh -X your_username@your_remote_machine</pre>
+
+<p>
+and afterwards you get the Xlib RENDER message, then try using:
+</p>
+<pre class="code">$ ssh -Y your_username@your_remote_machine</pre>
+
+<p>
+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.'" [33421-] --></body>
+</html>
diff --git a/docs/wiki/geda-faq-pcb.html b/docs/wiki/geda-faq-pcb.html
new file mode 100644
index 0000000..5ea33d3
--- /dev/null
+++ b/docs/wiki/geda-faq-pcb.html
@@ -0,0 +1,150 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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>
+<li class="level3"><div class="li"><span class="li"><a href="#is_there_any_relation_between_the_geda_pcb_and_the_opencircuitdesign_pcb" class="toc">Is there any relation between the gEDA PCB and the opencircuitdesign PCB?</a></span></div></li></ul>
+</li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h2><a name="pcb_faq" id="pcb_faq">pcb FAQ</a></h2>
+<div class="level2">
+
+</div>
+<!-- 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>
+<!-- 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="geda-installation.html" class="wikilink1" title="geda-installation.html">installation</a>.
+</p>
+
+</div>
+<!-- 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 …
+</p>
+
+</div>
+<!-- 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.
+</p>
+
+</div>
+<!-- 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. 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#how_do_i_make_a_board_outline_to_go_with_my_gerbers_to_the_board_maker" class="wikilink1" title="geda-pcb_tips.html">this note</a> in the more comprehensive <a href="geda-pcb_tips.html" class="wikilink1" title="geda-pcb_tips.html">pcb_tips</a>
+</p>
+
+</div>
+<!-- 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
+</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>
+</li>
+<li class="level1"><div class="li"> <a href="http://en.wikibooks.org/wiki/Practical_Electronics/PCB_Layout"; class="urlextern" title="http://en.wikibooks.org/wiki/Practical_Electronics/PCB_Layout"; rel="nofollow">http://en.wikibooks.org/wiki/Practical_Electronics/PCB_Layout</a></div>
+</li>
+</ul>
+
+</div>
+<!-- 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="geda-faq-gsch2pcb.html" class="wikilink1" title="geda-faq-gsch2pcb.html">faq-gsch2pcb</a>. Then you might go through the tutorial <a href="geda-gsch2pcb_tutorial.html" class="wikilink1" title="geda-gsch2pcb_tutorial.html">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.html">pcb_tips</a>, and the <a href="geda-pcb-quick_reference.html" class="wikilink1" title="geda-pcb-quick_reference.html">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">
+
+<p>
+See <a href="geda-pcb_footprints.html" class="wikilink1" title="geda-pcb_footprints.html">pcb_footprints</a>.
+</p>
+
+<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>.
+</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>
+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 "I had a hard time to find info on pcb due its ambigous name. Why don't you rename the app?" [1618-1954] -->
+<h3><a name="is_there_any_relation_between_the_geda_pcb_and_the_opencircuitdesign_pcb" id="is_there_any_relation_between_the_geda_pcb_and_the_opencircuitdesign_pcb">Is there any relation between the gEDA PCB and the opencircuitdesign PCB?</a></h3>
+<div class="level3">
+
+<p>
+ <a href="geda-faq-pcb.html" class="wikilink1" title="geda-faq-pcb.html"> gEDA PCB</a> and <a href="http://opencircuitdesign.com/pcb/"; class="urlextern" title="http://opencircuitdesign.com/pcb/"; rel="nofollow"> opencircuitdesign PCB</a> ?
+</p>
+
+</div>
+<!-- SECTION "Is there any relation between the gEDA PCB and the opencircuitdesign PCB?" [1955-] --></body>
+</html>
diff --git a/docs/wiki/geda-faq-simulation.fr.html b/docs/wiki/geda-faq-simulation.fr.html
new file mode 100644
index 0000000..843eb8f
--- /dev/null
+++ b/docs/wiki/geda-faq-simulation.fr.html
@@ -0,0 +1,161 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#simulation" class="toc">Simulation</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#je_veux_simuler_mon_circuit_analogique._quelles_sont_mes_options" class="toc">Je veux simuler mon circuit analogique. Quelles sont mes options?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#qu_en_est-il_de_tclspice_qu_est_ce_que_c_est_dois-je_l_utiliser" class="toc">Qu'en est-il de tclspice? Qu'est ce que c'est? Dois-je l'utiliser?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#n_existe-t-il_une_belle_interface_graphique_capture_de_schema_de_telle_maniere_que_je_n_ai_juste_qu_a_placer_des_composants_et_presser_un_bouton_simulation" class="toc">N'existe-t-il une belle interface graphique (capture de schéma) de telle manière que je n'ai juste qu'à placer des composants et presser un bouton «·simulation·»?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#comment_puis-je_creer_mes_schemas_pour_faciliter_les_simulations_analogiques" class="toc">Comment puis-je créer mes schémas pour faciliter les simulations analogiques?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#quelles_sont_les_commandes_gnetlist_pour_spice_sont_a_utiliser_ici_il_y_en_a_beaucoup" class="toc">Quelles sont les commandes gnetlist pour SPICE sont à utiliser ici? Il y en a beaucoup. . . .</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#comment_faire_si_on_veut_utiliser_gnucap_puis-je_utiliser_spice-sdb_pour_creer_mes_netlists_gnucap" class="toc">Comment faire si on veut utiliser gnucap, puis-je utiliser spice-sdb pour créer mes netlists gnucap?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#pourquoi_ne_puis-je_reutiliser_mon_schema_de_simulation_pour_le_placement_sur_carte" class="toc">Pourquoi ne puis-je réutiliser mon schéma de simulation pour le placement sur carte?</a></span></div></li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="simulation" id="simulation">Simulation</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "Simulation" [1-25] -->
+<h2><a name="je_veux_simuler_mon_circuit_analogique._quelles_sont_mes_options" id="je_veux_simuler_mon_circuit_analogique._quelles_sont_mes_options">Je veux simuler mon circuit analogique. Quelles sont mes options?</a></h2>
+<div class="level2">
+
+<p>
+Parmi les applications de la Suite gEDA, il y a deux simulateurs de circuits analogiques: ngspice et gnucap. Plus (un peu) en détail:
+</p>
+<ul>
+<li class="level1"><div class="li"> <a href="http://ngspice.sourceforge.net/"; class="urlextern" title="http://ngspice.sourceforge.net/"; rel="nofollow">Ngspice</a> est un portage/nettoyage du SPICE 3f5 classique sur la plate-forme GNU/Linux. Il est pleinement fonctionnel, inclut des extensions XSpice (tels que des constructions SPICE 2 POLY) et une structure CIDER.</div>
+</li>
+<li class="level1"><div class="li"> <a href="http://www.gnucap.org/"; class="urlextern" title="http://www.gnucap.org/"; rel="nofollow">Gnucap</a> est un nouveau simulateur de circuit écrit depuis zéro. Il offre la possibilité dâ??effectuer des simulations basées sur les événements â?? de même quâ??en temps â??. Câ??est le travail de Al Davis, Professor of Electrical Engineering à lâ??Université Kettering. Si vous voulez le télécharger, assurez-vous de prendre la dernière version, disponible avec les liens des «·developement releases·» sur le site gnucap.</div>
+</li>
+</ul>
+
+<p>
+ Les deux sont des programmes CLI (command line interface·; «·interface à ligne de commande·»), signifiant que vous intérragissez avec le simulateur en saisissant les commandes sur la ligne de commande. Cela signifie aussi que vous avez besoin dâ??apprendre le jeu de commandes spécifique au simulateur.
+</p>
+
+<p>
+Si vous préférez une interface graphique, la nouvelle application GSpiceUI de gEDA fournit une jolie interface utilisateur graphique pour piloter les programmes de simulation. Néanmoins, GSpiceUI nâ??est pas un simulateur sortie-schema-vers-simulation complet comme LTSpice ou PSpice. Il fournit, à la place, un menu dâ??interface graphique qui vous vous aide à porter des commandes dont vous avez besoin pour effectuer vos simulations ngspice/gnucap.
+</p>
+
+</div>
+<!-- SECTION "Je veux simuler mon circuit analogique. Quelles sont mes options?" [26-1717] -->
+<h2><a name="qu_en_est-il_de_tclspice_qu_est_ce_que_c_est_dois-je_l_utiliser" id="qu_en_est-il_de_tclspice_qu_est_ce_que_c_est_dois-je_l_utiliser">Qu'en est-il de tclspice? Qu'est ce que c'est? Dois-je l'utiliser?</a></h2>
+<div class="level2">
+
+<p>
+<a href="http://tclspice.sourceforge.net/"; class="urlextern" title="http://tclspice.sourceforge.net/"; rel="nofollow">Tclspice</a> est un fork du développement de ngspice. Il a débuté en 2002. En principe, tclspice exportera le jeu de commande SPICE vers un <acronym title="Application Programming Interface">API</acronym> TCL, vous permettant dâ??embarquer des analyses SPICE en un programme TCL. Cette vision est certainement très attirante car TCL est un langage à scripts très puissant â?? bien plus puissant que les constructions de scripts disponibles dans SPICE lui-même. En utilisant TCL, il est possible dâ??imaginer lâ??écriture dâ??optimisateurs de circuits complexes, ajoutant des éléments de comportement à la simulation et finalement en gagnant le contrôle de la sortie graphique de SPICE.
+</p>
+
+<p>
+Au fur et à mesure, le but a été partiellement atteint â?? avec tclspice, vous pouvez donc faire quelque chose comme ceci:
+</p>
+<pre class="code">#! tclsh
+package require spice
+spice::codemodel /usr/local/src/tclspice-0.2.12/src/xspice/icm/spice2poly.cm
+
+spice::source netlistname.cir
+spice::tran 0.1ns 40ns
+spice::run
+spice::plot Vout
+puts "All done now!"</pre>
+
+<p>
+Malheureusement, tclspice manque de fonctionnalités importantes, comme vous fournir un code de retour qui vous indique à quel stade réel est votre simulation ou si elle est en erreur. Aussi, les fonctionnalités graphiques semblent de jamais fonctionner (au moins pour moi … et les développeurs admettent que la partie graphique a des problèmes). Convertir des variables TCL vers et depuis des vecteurs SPICE semble ne jamais fonctionner â?? encore une fois, au moins pour moi. Finalement, ngspice (au moins) beaucoup de fuites de mémoire, rendant les simulations longues difficiles. Câ??est la raison pour laquelle, tclspice nâ??a pas encore réalisé les promesses qui ont été originellement été faites: une manière pratique, par scripts pour piloter les simulations SPICE.
+</p>
+
+<p>
+Les développements sur tclspice ont effectivement cessé en 2004. Peu être quâ??un jour, quelquâ??un le redémarrera. Pendant ce temps, la branche de développement <a href="http://ngspice.sourceforge.net/"; class="urlextern" title="http://ngspice.sourceforge.net/"; rel="nofollow">ngspice</a> a récupéré quelques fonctionnalités tclspice si vous les voulez (elles nécessitent des options de configuration séparées) et le code est plus récent.
+</p>
+
+</div>
+<!-- SECTION "Qu'en est-il de tclspice? Qu'est ce que c'est? Dois-je l'utiliser?" [1718-3965] -->
+<h2><a name="n_existe-t-il_une_belle_interface_graphique_capture_de_schema_de_telle_maniere_que_je_n_ai_juste_qu_a_placer_des_composants_et_presser_un_bouton_simulation" id="n_existe-t-il_une_belle_interface_graphique_capture_de_schema_de_telle_maniere_que_je_n_ai_juste_qu_a_placer_des_composants_et_presser_un_bouton_simulation">N'existe-t-il une belle interface graphique (capture de schéma) de telle manière que je n'ai juste qu'à placer des composants et presser un bouton «·simulation·»?</a></h2>
+<div class="level2">
+
+<p>
+Non. Le miux que vous puissiez faire est dâ??utiliser GSpiceUI.
+</p>
+
+</div>
+<!-- SECTION "N'existe-t-il une belle interface graphique (capture de schéma) de telle manière que je n'ai juste qu'à placer des composants et presser un bouton «·simulation·»?" [3966-4210] -->
+<h2><a name="comment_puis-je_creer_mes_schemas_pour_faciliter_les_simulations_analogiques" id="comment_puis-je_creer_mes_schemas_pour_faciliter_les_simulations_analogiques">Comment puis-je créer mes schémas pour faciliter les simulations analogiques?</a></h2>
+<div class="level2">
+
+<p>
+Le chemin habituel pour la conception est «·gschem·» â?? «·gnetlist -g spice-sdb·» â?? [«·ngspice·» | «·gnucap·»]. Vous avez besoin dâ??attacher des attributs aux composants dans votre schéma pour fournir les attributs nécessaires à SPICE/Gnucap. Vous pouvez aussi attacher des attributs en utilisant gattrib.
+</p>
+
+<p>
+Le <a href="geda-csygas.html" class="wikilink1" title="geda-csygas.html">Circuit Simulation using gEDA and SPICE - HOWTO</a> décrit tout ceci en détail.
+</p>
+
+<p>
+ Quelques <a href="http://www.brorson.com/gEDA/SPICE/"; class="urlextern" title="http://www.brorson.com/gEDA/SPICE/"; rel="nofollow">ressources SPICE</a> vous aideront pour comprendre comment utiliser spice-sdb.
+</p>
+
+</div>
+<!-- SECTION "Comment puis-je créer mes schémas pour faciliter les simulations analogiques?" [4211-4853] -->
+<h2><a name="quelles_sont_les_commandes_gnetlist_pour_spice_sont_a_utiliser_ici_il_y_en_a_beaucoup" id="quelles_sont_les_commandes_gnetlist_pour_spice_sont_a_utiliser_ici_il_y_en_a_beaucoup">Quelles sont les commandes gnetlist pour SPICE sont à utiliser ici? Il y en a beaucoup. . . .</a></h2>
+<div class="level2">
+
+<p>
+Utilisez spice-sdb. Il est le plus riche en fonctionnalités. Les autres ne sont présent que pour des raisons historiques. Notez que spice-sdb est une extension dâ??une des autres commandes SPICE, vous ne perdez rien en utilisant spice-sdb.
+</p>
+
+</div>
+<!-- SECTION "Quelles sont les commandes gnetlist pour SPICE sont à utiliser ici? Il y en a beaucoup. . . ." [4854-5201] -->
+<h2><a name="comment_faire_si_on_veut_utiliser_gnucap_puis-je_utiliser_spice-sdb_pour_creer_mes_netlists_gnucap" id="comment_faire_si_on_veut_utiliser_gnucap_puis-je_utiliser_spice-sdb_pour_creer_mes_netlists_gnucap">Comment faire si on veut utiliser gnucap, puis-je utiliser spice-sdb pour créer mes netlists gnucap?</a></h2>
+<div class="level2">
+
+<p>
+Oui. Vous pouvez aussi dessiner votre schéma en utilisant les directives gnucap disponibles dans le répertoire de symbole «·spice·».
+</p>
+
+</div>
+<!-- SECTION "Comment faire si on veut utiliser gnucap, puis-je utiliser spice-sdb pour créer mes netlists gnucap?" [5202-5455] -->
+<h2><a name="pourquoi_ne_puis-je_reutiliser_mon_schema_de_simulation_pour_le_placement_sur_carte" id="pourquoi_ne_puis-je_reutiliser_mon_schema_de_simulation_pour_le_placement_sur_carte">Pourquoi ne puis-je réutiliser mon schéma de simulation pour le placement sur carte?</a></h2>
+<div class="level2">
+
+<p>
+Les nouveau veulent habituellement créer un schéma unique pour la simulation/validation et le placement sur carte. Cette vision semble tout dâ??abord attirante car votre carte aura dâ??abord été testée et validée avant de la créer en FR-4. Néanmoins, le diable est dans les détails·; utiliser un seul schéma pour la simulation et le placement ne fonctionne habituellement pas pour els raisons suivantes:
+</p>
+<ul>
+<li class="level1"><div class="li"> Les composants nécessaires pour la simulation et le placement sont normalement très différents. par exemple, la simulation nécessite souvent un schéma comportant un lot dâ??éléments liés à SPICE comme mes sources de tension, les sources dépendantes, les directives SPICE et ainsi de suite. Dâ??un autre côté, le placement nécessite des composant impossible à modéliser comme des connecteurs, des composants logiques et même des éléments comme des régulateurs de tension qui peuvent ne pas avoir de modèles SPICE de disponibles mais qui vont poluer votre netlist SPICE, rendant le netlister et le simulateur malheureux.</div>
+</li>
+<li class="level1"><div class="li"> Quelques composants électroniques réels nâ??ont pas de modèles SPICE. Il existe beaucoup de composants qui nâ??en possèdent pas comme les potentiomètres, les transformateurs, les thermistances, les filtres EMI, les portes logiques, les quartz, les tubes à vide et ainsi de suite. Câ??est la raison pour laquelle si votre schéma utilise un de ces composants, vous devez avoir un élément utilisant un circuit équivalent pour faire la simulation. Cela rend très difficile la réutilisation du schéma de simulation pour le placement.</div>
+</li>
+<li class="level1"><div class="li"> Habituellement, vous avez seulement besoin de simuler un sous-ensemble de votre schéma. Par exemple, vous pouvez vouloir simuler le comportement dâ??un filtre ou dâ??un circuit oscillant mais sans vous préoccuper de (ou vous ne pouvez pas simuler) votre alimentation, la partie logique ou tout autre partie de votre schéma. Si vous insister pour créer un modèle SPICE pour ces sous-sections de circuit, vous pourriez avoir beaucoup de problèmes â?? et faire beaucoup de travail inutile â?? de manière à trouver ou créer des modèles SPICE pour des zones de votre circuit qui ne sont pas importantes.</div>
+</li>
+</ul>
+
+<p>
+ Câ??est la raison pour laquelle, je (SDB) recommande normalement de ne pas trop tenter dâ??utiliser le même schéma pour la simulation et pour le placement. Si vous pouvez le faire, câ??est bien! Mais, habituellement, vous ne le pouvez pas.
+</p>
+
+<p>
+Personellement, je ne crée des modèles SPICE que pour les sections analogiques critiques de mon circuit. Un projet plus grand devrait donc avoir plusieurs schémas de simulation validant les sous-circuits analogiques. En plus des schémas de simulation, jâ??ai un schéma principal qui est utilisé pour le placement.
+</p>
+
+</div>
+<!-- SECTION "Pourquoi ne puis-je réutiliser mon schéma de simulation pour le placement sur carte?" [5456-] --></body>
+</html>
diff --git a/docs/wiki/geda-faq-simulation.html b/docs/wiki/geda-faq-simulation.html
new file mode 100644
index 0000000..ad780dd
--- /dev/null
+++ b/docs/wiki/geda-faq-simulation.html
@@ -0,0 +1,165 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#simulation" class="toc">Simulation</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#i_want_to_simulate_my_analog_circuit_design._what_are_my_options" class="toc">I want to simulate my analog circuit design. What are my options?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#what_about_tclspice_what_is_it_should_i_use_it" class="toc">What about tclspice? What is it? Should I use it?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#isn_t_there_a_nice_graphical_schematic_capture_front_end_so_i_can_just_place_components_and_press_a_simulate_button" class="toc">Isn't there a nice graphical (schematic capture) front end so I can just place components and press a "simulate" button?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_create_my_schematic_to_facilitate_analog_simulation" class="toc">How do I create my schematic to facilitate analog simulation?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#which_spice_netlister_backend_to_gnetlist_should_i_use_there_are_several_of_them" class="toc">Which spice netlister backend to gnetlist should I use? There are several of them. . . .</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_about_if_i_want_to_use_gnucap_can_i_use_spice-sdb_to_create_my_gnucap_netlists" class="toc">How about if I want to use gnucap, can I use spice-sdb to create my gnucap netlists?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#why_not_reuse_my_simulation_schematic_for_layout" class="toc">Why not reuse my simulation schematic for layout?</a></span></div></li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="simulation" id="simulation">Simulation</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "Simulation" [1-26] -->
+<h2><a name="i_want_to_simulate_my_analog_circuit_design._what_are_my_options" id="i_want_to_simulate_my_analog_circuit_design._what_are_my_options">I want to simulate my analog circuit design. What are my options?</a></h2>
+<div class="level2">
+
+<p>
+Within the cannonical gEDA Suite apps there are two analog circuit simulators: ngspice and gnucap. In (slightly) more detail:
+</p>
+<ul>
+<li class="level1"><div class="li"> <a href="http://ngspice.sourceforge.net/"; class="urlextern" title="http://ngspice.sourceforge.net/"; rel="nofollow">Ngspice</a> is a port/clean-up of classical SPICE 3f5 to the GNU/Linux platform. It is fully functional, includes the XSpice extensions (such as SPICE 2 POLY constructs), and the CIDER framework.</div>
+</li>
+<li class="level1"><div class="li"> <a href="http://www.gnucap.org/"; class="urlextern" title="http://www.gnucap.org/"; rel="nofollow">Gnucap</a> is a new circuit simulator written from the ground up. It offers the ability to perform event-driven â?? as well as continuous time â?? simulations. It is the work of Al Davis. If you wish to download it, make sure you grab the latest version, available through the â??developement releasesâ?? link on the gnucap website.</div>
+</li>
+</ul>
+
+<p>
+ Both are CLI (command line interface) programs, meaning that you intereact with the simulator by typing commands at a command line. It also means that you need to learn the simulator-specific command set.
+</p>
+
+<p>
+If you prefer a graphical interface, the new gEDA app GSpiceUI provides a nice <acronym title="Graphical User Interface">GUI</acronym> front-end to drive the simulation programs. However, GSpiceUI is not a complete schematic-to-simulation-output simulator like LTSpice or PSpice. Rather, it just provides a <acronym title="Graphical User Interface">GUI</acronym> menu which helps you navigate the commands you need to perform your ngspice/gnucap simulation.
+</p>
+
+</div>
+<!-- SECTION "I want to simulate my analog circuit design. What are my options?" [27-1384] -->
+<h2><a name="what_about_tclspice_what_is_it_should_i_use_it" id="what_about_tclspice_what_is_it_should_i_use_it">What about tclspice? What is it? Should I use it?</a></h2>
+<div class="level2">
+
+<p>
+<a href="http://tclspice.sourceforge.net/"; class="urlextern" title="http://tclspice.sourceforge.net/"; rel="nofollow">Tclspice</a> was a fork off the ngspice development path. It was begun in the 2002 timeframe. In principle, tclspice would export the SPICE command set to a TCL <acronym title="Application Programming Interface">API</acronym>, allowing you to embed SPICE analyses into a TCL program. This vision is certainly very attractive since TCL is a powerful scripting language â?? much more powerful than the scripting constructs available from within SPICE itself. Using TCL, one could imagine writing complex circuit optimizers, adding behavioral elements to a simulation, and finally gaining control over SPICEâ??s graphical output.
+</p>
+
+<p>
+As it turns out, this goal was partially met â?? with tclspice you can indeed do something like this:
+</p>
+<pre class="code">#! tclsh
+package require spice
+spice::codemodel /usr/local/src/tclspice-0.2.12/src/xspice/icm/spice2poly.cm
+
+spice::source netlistname.cir
+spice::tran 0.1ns 40ns
+spice::run
+spice::plot Vout
+puts "All done now!"</pre>
+
+<p>
+Unfortunately, tclspice lacks certain important features, like providing you a return code which tells you whether your simulation actually worked or errored out instead. Also, the graphics functionality never seemed to work (at least for me … and the developers admit that the graphics stink). Converting TCL variables to and from SPICE vectors never seemed to work â?? again at least for me. Finally, ngspice (at least) has a lot of memory leaks, making long simulation runs difficult. Therefore, tclspice doesnâ??t meet the promise it originally held out: a convenient, scriptable way to drive SPICE simulations.
+</p>
+
+<p>
+Developement on tclspice effectively stopped in 2004. Perhaps some day somebody will pick it up again. In the meantime, the main <a href="http://ngspice.sourceforge.net/"; class="urlextern" title="http://ngspice.sourceforge.net/"; rel="nofollow">ngspice</a> development branch has picked up the tclspice features if you want them (they require separate configuration options), and the code is fresher.
+</p>
+
+</div>
+<!-- SECTION "What about tclspice? What is it? Should I use it?" [1385-3314] -->
+<h2><a name="isn_t_there_a_nice_graphical_schematic_capture_front_end_so_i_can_just_place_components_and_press_a_simulate_button" id="isn_t_there_a_nice_graphical_schematic_capture_front_end_so_i_can_just_place_components_and_press_a_simulate_button">Isn't there a nice graphical (schematic capture) front end so I can just place components and press a "simulate" button?</a></h2>
+<div class="level2">
+
+<p>
+No. The best you can do is use <a href="http://www.geda.seul.org/tools/gspiceui/index.html"; class="urlextern" title="http://www.geda.seul.org/tools/gspiceui/index.html"; rel="nofollow">GSpiceUI</a>.
+</p>
+
+</div>
+<!-- SECTION "Isn't there a nice graphical (schematic capture) front end so I can just place components and press a simulate button?" [3315-3544] -->
+<h2><a name="how_do_i_create_my_schematic_to_facilitate_analog_simulation" id="how_do_i_create_my_schematic_to_facilitate_analog_simulation">How do I create my schematic to facilitate analog simulation?</a></h2>
+<div class="level2">
+
+<p>
+The usual design path is â??gschemâ?? â?? â??gnetlist -g spice-sdbâ?? â?? [â??ngspiceâ?? | â??gnucapâ??]. You need to attach attributes to the components in your schematic to provide attributes needed by SPICE/Gnucap. You can also attach attributes using gattrib.
+</p>
+
+<p>
+The <a href="geda-csygas.html" class="wikilink1" title="geda-csygas.html">Circuit Simulation using gEDA and SPICE - HOWTO</a> describes all this in great detail.
+</p>
+
+<p>
+ Some <a href="http://www.brorson.com/gEDA/SPICE/"; class="urlextern" title="http://www.brorson.com/gEDA/SPICE/"; rel="nofollow">SPICE resources</a> will help you understand how to use spice-sdb.
+</p>
+
+</div>
+<!-- SECTION "How do I create my schematic to facilitate analog simulation?" [3545-4097] -->
+<h2><a name="which_spice_netlister_backend_to_gnetlist_should_i_use_there_are_several_of_them" id="which_spice_netlister_backend_to_gnetlist_should_i_use_there_are_several_of_them">Which spice netlister backend to gnetlist should I use? There are several of them. . . .</a></h2>
+<div class="level2">
+
+<p>
+Use spice-sdb. It is by far the most advanced and feature rich. The others are there only for reasons of history. Note that spice-sdb is an extension of one of the other SPICE backends, so you arenâ??t missing anything by using spice-sdb.
+</p>
+
+</div>
+<!-- SECTION "Which spice netlister backend to gnetlist should I use? There are several of them. . . ." [4098-4438] -->
+<h2><a name="how_about_if_i_want_to_use_gnucap_can_i_use_spice-sdb_to_create_my_gnucap_netlists" id="how_about_if_i_want_to_use_gnucap_can_i_use_spice-sdb_to_create_my_gnucap_netlists">How about if I want to use gnucap, can I use spice-sdb to create my gnucap netlists?</a></h2>
+<div class="level2">
+
+<p>
+Yes. Also, you can draw your schematic using gnucap directives available in the â??spiceâ?? symbol directory.
+</p>
+
+<p>
+It is better to just draw the circuit, without directives, and run the simulator interactively.
+</p>
+
+</div>
+<!-- SECTION "How about if I want to use gnucap, can I use spice-sdb to create my gnucap netlists?" [4439-4743] -->
+<h2><a name="why_not_reuse_my_simulation_schematic_for_layout" id="why_not_reuse_my_simulation_schematic_for_layout">Why not reuse my simulation schematic for layout?</a></h2>
+<div class="level2">
+
+<p>
+Newbies commonly want to create a single schematic for both design simulation/validation as well as layout. This vision seems very attractive at first, since your layout will have been tested & validated before committing it to FR-4. However, the devil is in the details; using a single schematic for simulation and layout usually doesnâ??t work for the following reasons:
+</p>
+<ul>
+<li class="level1"><div class="li"> Components required for simulation and layout are normally very different. For example, simulation often requires a schematic holding a bunch of SPICE-related devices such as voltage sources, dependent sources, SPICE directives, and so on. On the other hand, layout requires non-SPICEable components such as connectors, logic devices, and even things like voltage regulators which might have no SPICE models available, but will pollute your SPICE netlist, possibly making the netlister and the simulator unhappy.</div>
+</li>
+<li class="level1"><div class="li"> Some real electronic components donâ??t have built-in SPICE models. There are plenty of components which donâ??t have native SPICE models like potentiometers, transformers, thermistors, EMI filters, logic gates, crystals, vacuum tubes, and on and on. Therefore, if your design uses any of these components, you must mock up the device using an equivalent circuit for simulation. This makes it very difficult to reuse the simulation schematic for layout.</div>
+</li>
+<li class="level1"><div class="li"> Usually, you only really need to simulate a subset of your design. For example, you might want to simulate the behavior of a filter or oscillator circuit, but donâ??t care about (or canâ??t simulate) your power supply, glue logic, or other part of your design. If you insist upon creating a SPICE model for these circuit subsections, you might need to jump through a lot of hoops â?? and do a lot of unnecessary hard work â?? in order to find or create SPICE models for parts of your design which arenâ??t important.</div>
+</li>
+</ul>
+
+<p>
+ Therefore, I (SDB) normally recommend that you shouldnâ??t try too hard to use the same schematic for simulation and for layout. If you can do it, great! But usually you canâ??t.
+</p>
+
+<p>
+Personally, I tend to create SPICE models of only the critical analog sections of my design. A larger project might therefore have a couple of simulation schematics validating a couple of analog subcircuits. Besides the simulation schematics, Iâ??ll have a main schematic which is used for layout.
+</p>
+
+</div>
+<!-- SECTION "Why not reuse my simulation schematic for layout?" [4744-] --></body>
+</html>
diff --git a/docs/wiki/geda-faq.fr.html b/docs/wiki/geda-faq.fr.html
new file mode 100644
index 0000000..8fbfef9
--- /dev/null
+++ b/docs/wiki/geda-faq.fr.html
@@ -0,0 +1,317 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#faq_geda" class="toc">FAQ gEDA</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#qu_est_ce_que_le_projet_geda" class="toc">Qu'est ce que le projet gEDA?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#qu_est_ce_que_geda_gaf_et_quelle_est_sa_relation_avec_geda" class="toc">qu'est ce que gEDA/gaf et quelle est sa relation avec gEDA?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#qu_est_ce_que_la_suite_geda" class="toc">Qu'est ce que la suite gEDA?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#pourquoi_qu_est_ce_qui_rend_geda_si_different_des_autres_outils_d_eda" class="toc">Pourquoi? Qu'est ce qui rend gEDA si différent des autres outils d'EDA ?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#pourquoi_la_suite_geda_ressemble-t-elle_a_une_collection_de_programmes_epars_et_pas_une_seule_application_integree" class="toc">Pourquoi la Suite gEDA ressemble-t-elle à une collection de programmes épars et pas une seule application intégrée?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#qu_est_ce_qui_est_mieux_une_suite_i.e._confederee_de_programmes_ou_une_application_integree" class="toc">Qu'est ce qui est mieux, une suite (i.e. confédérée) de programmes ou une application intégrée?</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#pour_la_suite_l_association" class="toc">Pour la Suite (l'association):</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#contre_la_suite_l_association" class="toc">Contre la Suite (l'association):</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#pour_les_applications_monolithiques" class="toc">Pour les applications monolithiques:</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#contre_les_applications_monolithiques" class="toc">Contre les applications monolithiques:</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#quelle_est_la_licence_utilisee_par_geda" class="toc">Quelle est la licence utilisée par gEDA?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#ou_puis-je_avoir_plus_d_informations_a_propos_de_geda_et_sur_son_telechargement" class="toc">Où puis-je avoir plus d'informations à propos de gEDA et sur son téléchargement?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#ok_comment_je_comence_a_utiliser_geda" class="toc">OK, comment je comence à utiliser gEDA?</a></span></div></li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="faq_geda" id="faq_geda">FAQ gEDA</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "FAQ gEDA" [1-24] -->
+<h2><a name="qu_est_ce_que_le_projet_geda" id="qu_est_ce_que_le_projet_geda">Qu'est ce que le projet gEDA?</a></h2>
+<div class="level2">
+
+<p>
+Le projet gEDA travaille à produire une suite <acronym title="GNU General Public License">GPL</acronym> complète dâ??outils EDA (<em class="u">E</em>lectronic <em class="u">D</em>esign <em class="u">A</em>utomation). Ces outils sont utilisés pour la conception de circuits électriques, la saisie de schémas, la simulation, le prototypage et la production. Le projet gEDA offre actuellement une suite mature dâ??applications de logiciels libres pour la conception électronique, incluant le la saisie de schémas, la gestion dâ??attributs, la génération de bill of materials (BOM), le netlisting dans plus de 20 formats de netlist, la simulation analogique et numérique et le placement sur circuit imprimé « printed circuit board (PCB) ».
+</p>
+
+<p>
+Ales Hvezda est à lâ??origine du projet gEDA. Le projet gEDA a quelque peu grossi, depuis le printemps 1998. Ces outils ne sont plus lâ??oeuvre dâ??une seule personne. De nombreuses personnes sâ??y sont impliquées. Quelques personnes contribuent aux outils originaux, alors que les autres développent leurs propres outils. Câ??est la raison pour laquelle gEDA ne se réfère plus aux outils originels (ils ont maintenant leurs propres vies) mais à tous les projets qui sont libres et qui sont associés quelque part dans ces pages web ou les listes de diffusion geda-dev/geda-user. En association avec gEDA, les auteurs de logiciels libres ne laissent pas le contrôle sur leurs outils mais ils sont aidés par la communauté pour maintenir la qualité et la liberté des outils EDA.
+</p>
+
+<p>
+gEDA peut être prononcé « gee-daahhh » (rhymes with cheetah) ou â??g-dahhh (short g).
+</p>
+
+</div>
+<!-- SECTION "Qu'est ce que le projet gEDA?" [25-1585] -->
+<h2><a name="qu_est_ce_que_geda_gaf_et_quelle_est_sa_relation_avec_geda" id="qu_est_ce_que_geda_gaf_et_quelle_est_sa_relation_avec_geda">qu'est ce que gEDA/gaf et quelle est sa relation avec gEDA?</a></h2>
+<div class="level2">
+
+<p>
+gaf signifie « <em class="u">g</em>schem <em class="u">a</em>nd <em class="u">f</em>riends » (gschem et ses amis). Câ??est un sous-jeu de la suite dâ??outils complète groupée sous le nom de gEDA. gEDA/gaf est une collection dâ??outils qui inclut actuellement:
+</p>
+<ul>
+<li class="level1"><div class="li"> gschem: un programme de capture de schémas</div>
+</li>
+<li class="level1"><div class="li"> gnetlist: un programme de génération de netlist</div>
+</li>
+<li class="level1"><div class="li"> gsymcheck: un vérificateur de syntaxe pour les symboles de schémas</div>
+</li>
+<li class="level1"><div class="li"> gattrib: une feuille de calcul qui manipule les propriétés des symboles dâ??un schéma</div>
+</li>
+<li class="level1"><div class="li"> libgeda: les bibliothèques pour gnetlist de gschem et gsymcheck</div>
+</li>
+<li class="level1"><div class="li"> gsch2pcb: Annotation directe depuis votre schéma vers le circuit en utilisant <a href="geda-pcb.html" class="wikilink2" title="geda-pcb.html">PCB</a>.</div>
+</li>
+<li class="level1"><div class="li"> quelques utilitaires mineurs</div>
+</li>
+</ul>
+
+<p>
+ Les outils gEDA/gaf partagent un format de fichier commun (.sch) et partagent aussi une bibliothèque commune (libgeda.so). Les sources de la distribution gEDA/gaf peuvent être trouvées sur ce site web (geda.seul.org).
+</p>
+
+<p>
+Bien que gaf se réfère surtout à gEDA, le nom gEDA ne sâ??applique pas obligatoirement à gaf â?? les outils rassemblés sous la bannière de « gEDA » comprennent beaucoup dâ??autres programmes. En fait, gEDA fait référence à <strong>tout</strong> outil dâ??EDA sous <acronym title="GNU General Public License">GPL</acronym> qui décide de sâ??associer avec le site web/liste de diffusion. Des exemples importants dâ??outils gEDA incluent le programme de création de circuit imprimé <a href="geda-pcb.html" class="wikilink2" title="geda-pcb.html">PCB</a>, le compilateur Verilog <a href="http://www.icarus.com/eda/verilog/"; class="urlextern" title="http://www.icarus.com/eda/verilog/"; rel="nofollow">Icarus Verilog</a>, le simulateur de circuits analogiques <a href="http://www.gnucap.org/"; class="urlextern" title="http://www.gnucap.org/"; rel="nofollow">gnucap</a> et le simulateur open-source SPICE <a href="http://www.ngspice.org/"; class="urlextern" title="http://www.ngspice.org/"; rel="nofollow">ngspice</a>. Il existe plusieurs autres programmes gEDA.
+</p>
+
+<p>
+Pour des raisons historiques, sur <a href="http://freshmeat.net/"; class="urlextern" title="http://freshmeat.net/"; rel="nofollow">freshmeat</a>, gaf est connu comme le paquet â??gEDAâ??.
+</p>
+
+</div>
+<!-- SECTION "qu'est ce que gEDA/gaf et quelle est sa relation avec gEDA?" [1586-3369] -->
+<h2><a name="qu_est_ce_que_la_suite_geda" id="qu_est_ce_que_la_suite_geda">Qu'est ce que la suite gEDA?</a></h2>
+<div class="level2">
+
+<p>
+La suite gEDA est une image CDROM (.iso) crée par Stuart Brorson pour faciliter lâ??installation des divers outils qui forment, sont associés oiu fonctionnent totalement avec le projet gEDA. Lâ??objectif est que les outils rassemblés sur la suite gEDA en CDROM constitue un environnement de conception cohérent, complet, open-source en un seul téléchargement. La suite gEDA sur CDROM inclut actuellement:
+</p>
+<ul>
+<li class="level1"><div class="li"> <a href="http://geda.seul.org/tools/"; class="urlextern" title="http://geda.seul.org/tools/"; rel="nofollow">gEDA/gaf</a> â?? saisie de schématic et netlisting</div>
+</li>
+<li class="level1"><div class="li"> <a href="http://geda.seul.org/tools/ngspice"; class="urlextern" title="http://geda.seul.org/tools/ngspice"; rel="nofollow">ngspice</a> â?? simulation SPICE</div>
+</li>
+<li class="level1"><div class="li"> <a href="http://geda.seul.org/tools/gnucap"; class="urlextern" title="http://geda.seul.org/tools/gnucap"; rel="nofollow">gnucap</a> â?? simulation analogique</div>
+</li>
+<li class="level1"><div class="li"> <a href="http://geda.seul.org/tools/gspiceui"; class="urlextern" title="http://geda.seul.org/tools/gspiceui"; rel="nofollow">gspiceui</a> â?? <acronym title="Graphical User Interface">GUI</acronym> front end for ngspice/gnucap</div>
+</li>
+<li class="level1"><div class="li"> <a href="http://geda.seul.org/tools/pcb"; class="urlextern" title="http://geda.seul.org/tools/pcb"; rel="nofollow">pcb</a> â?? placement avec PCB</div>
+</li>
+<li class="level1"><div class="li"> <a href="http://geda.seul.org/tools/gerbv"; class="urlextern" title="http://geda.seul.org/tools/gerbv"; rel="nofollow">gerbv</a> â?? visualisation Gerber</div>
+</li>
+<li class="level1"><div class="li"> <a href="http://geda.seul.org/tools/icarus"; class="urlextern" title="http://geda.seul.org/tools/icarus"; rel="nofollow">Icarus Verilog</a> â?? simulateur Verilog</div>
+</li>
+<li class="level1"><div class="li"> <a href="http://geda.seul.org/tools/gtkwave"; class="urlextern" title="http://geda.seul.org/tools/gtkwave"; rel="nofollow">GTKWave</a> â?? visualisation de forme dâ??onde numérique</div>
+</li>
+<li class="level1"><div class="li"> <a href="http://wcalc.sourceforge.net/"; class="urlextern" title="http://wcalc.sourceforge.net/"; rel="nofollow">wcalc</a> â?? analyse de ligne de transmission et structure électromagnetique</div>
+</li>
+</ul>
+
+<p>
+ Au centre de la suite gEDA en CDROM est la facilité dâ??utiliser lâ??installateur qui automatise la construction et lâ??installation des divers paquets depuis les sources - facilitant lâ??installation la suite complète pour les novices. La suite gEDA en CDROM est disponible sur la page de <a href="http://geda.seul.org/download.html"; class="urlextern" title="http://geda.seul.org/download.html"; rel="nofollow">téléchargement</a>. <strong>Note: Lâ??installateur ne fonctionne quâ??avec Linux!</strong>
+</p>
+
+</div>
+<!-- SECTION "Qu'est ce que la suite gEDA?" [3370-4962] -->
+<h2><a name="pourquoi_qu_est_ce_qui_rend_geda_si_different_des_autres_outils_d_eda" id="pourquoi_qu_est_ce_qui_rend_geda_si_different_des_autres_outils_d_eda">Pourquoi? Qu'est ce qui rend gEDA si différent des autres outils d'EDA ?</a></h2>
+<div class="level2">
+
+<p>
+Les outils de la suite gEDA et leurs associés ont les caractéristiques suivantes:
+</p>
+<ul>
+<li class="level1"><div class="li"> Gratuit.</div>
+</li>
+<li class="level1"><div class="li"> Tous les formats de fichiers et tous les codes sources sont disponibles en licence <acronym title="GNU General Public License">GPL</acronym>. Cette licence vous garantit des droits spécifiques aux auteurs et aux utilisateurs de logiciels <acronym title="GNU General Public License">GPL</acronym>.</div>
+</li>
+<li class="level1"><div class="li"> Lâ??indépendence vis à vis de toute entreprise. Tous les outils gEDA sont fournis avec les sources complètes. Vous pouvez les changer, les améliorer, les porter (sur dâ??autres systèmes) et même les distribuer (si vous respectez les termes de la <acronym title="GNU General Public License">GPL</acronym>).</div>
+</li>
+<li class="level1"><div class="li"> Aucun mécanisme nâ??est utilisé pour restreindre lâ??utilisation de ces outils (comme lâ??utilisation de numéros de série du disque dur ou des adresses ethernet pour forcer le logiciel à ne fonctionner que sur un machine).</div>
+</li>
+<li class="level1"><div class="li"> Aucunes limitations arbitraires, imposées par les marketing ou les ingénieurs. Les versions gratuites des outils commerciaux incluent des limitations capricieuses (i.e. une taille de carte limité, lâ??impossibilité dâ??imprimer, lâ??impossibilité dâ??exporter des netlists, etc.) qui verrouille le programme et force les utilisateurs sérieux à acheter les outils complets. Par contraste, les outils gEDA sont pleinement fonctionnels et nâ??imposent aucune limitation arbitraire sur la conception pour vous soutirer de lâ??argent.</div>
+</li>
+<li class="level1"><div class="li"> Garanties de protection de conception. Comme le logiciel fonctionnera pour toujours (pour les raisons citées ci-dessus), les fichiers de conception de gEDA sera toujours visualisable/éditable (avec les bonnes versions du logiciel).</div>
+</li>
+<li class="level1"><div class="li"> Flux de conception ouverts. Cela signifie que les outils correspondent les uns avec les autres par des moyens connus et documentés (fichiers / <acronym title="Application Programming Interface">API</acronym>). Il est facile de remplacer un outil ou de lâ??améliorer avec quelque chose dâ??autre si vous le désirez.</div>
+</li>
+<li class="level1"><div class="li"> Stabilité - Les bogues qui plantent sont étudiés immediatement et réparés dès que possible.</div>
+</li>
+<li class="level1"><div class="li"> Minimise les fonctionnalités gourmandes et inutiles.</div>
+</li>
+<li class="level1"><div class="li"> Fonctionne sur autant de plates-formes que possible. Pour gEDA/gaf: GNU/Linux et dâ??autres systèmes Unix.</div>
+</li>
+<li class="level1"><div class="li"> Dévelopé dâ??une manière ouverte (pas de secrets).</div>
+</li>
+<li class="level1"><div class="li"> Les programmes sont documentées.</div>
+</li>
+</ul>
+
+<p>
+ gEDA nâ??aura peut être pas les dernières fonctionnalités les plus pointues que lâ??on pourrait trouver dans dâ??autres paquets et peut, quelques fois, être vu comme à la traîne de la technique EDA mais les outils sont devenus utiles à beaucoup de personnes à cause des raisons mentionnées ci-dessus.
+</p>
+
+</div>
+<!-- SECTION "Pourquoi? Qu'est ce qui rend gEDA si différent des autres outils d'EDA ?" [4963-7518] -->
+<h2><a name="pourquoi_la_suite_geda_ressemble-t-elle_a_une_collection_de_programmes_epars_et_pas_une_seule_application_integree" id="pourquoi_la_suite_geda_ressemble-t-elle_a_une_collection_de_programmes_epars_et_pas_une_seule_application_integree">Pourquoi la Suite gEDA ressemble-t-elle à une collection de programmes épars et pas une seule application intégrée?</a></h2>
+<div class="level2">
+
+<p>
+La Suite gEDA est un rassemblement de programmes independants. Cela sâ??est produit pour des raisons historiques: Ales Hvezda a débuté le programme gEDA plus ou moins seul. La vision originelle était de produire une suite intégrée complète pour créer des circuits imprimés de telle manière que les passionnés de robots puissent concevoir leurs propres cartes. Néanmoins, au fur et à mesure de la progression du projet gEDA, lâ??ampleur de la tâche est devenu claire - et le codage des nombreuses applications proposées nâ??avait pas encore commencé!
+</p>
+
+<p>
+Pendant ce temps, dâ??autres développeurs de logiciels -avec leurs propres applications écrites indépendament - ont trouvé que la vision du projet permettait de les compléter. Les auteurs de ces applications se sont joints à Ales et ont fait contribuer leur programme au projet gEDA. Parmi des projets, on trouve « pcb », un programme de création de circuits imprimés vieux de 10 ans (à ce moment). Avec cette contribution de « pcb », lâ??outil originel pour circuits imprimés de gEDA, « gpcb » a été abandonné. Au même moment, dâ??autres développeurs ont ajouté des simulateurs analogiques et numériques, des visualiseurs de formes de signal, ainsi de suite.
+</p>
+
+<p>
+Câ??est de cette manière que sâ??est agglomérée la suite gEDA. Ce nâ??est pas un code partagé ou une interface utilisateur commune qui distingue la suite gEDA. Câ??est plutôt la vision partagée dâ??un environnement EDA open-source qui maintient la cohérence du projet. Aujourdâ??hui, la Suite gEDA est un ensemble de différents programmes réalisés par plusieurs auteurs. Les applications tentent de fonctionner ensemble et réussissent généralement. Mais les démarrages séparés de chaque programme de la suite sont encore observables. Néanmoins, avec un peu de travail, les divers composants de la Suite sont intéropérables et plusieurs personnes ont achevé des circuits imprimés assez compliqués en utilisant la Suite gEDA.
+</p>
+
+</div>
+<!-- SECTION "Pourquoi la Suite gEDA ressemble-t-elle à une collection de programmes épars et pas une seule application intégrée?" [7519-9623] -->
+<h2><a name="qu_est_ce_qui_est_mieux_une_suite_i.e._confederee_de_programmes_ou_une_application_integree" id="qu_est_ce_qui_est_mieux_une_suite_i.e._confederee_de_programmes_ou_une_application_integree">Qu'est ce qui est mieux, une suite (i.e. confédérée) de programmes ou une application intégrée?</a></h2>
+<div class="level2">
+
+<p>
+Câ??est plus une question de religion. Je vais résumer quelques pour et contre (tel que je les vois) de chaque approche ici.
+</p>
+
+</div>
+<!-- SECTION "Qu'est ce qui est mieux, une suite (i.e. confédérée) de programmes ou une application intégrée?" [9624-9861] -->
+<h3><a name="pour_la_suite_l_association" id="pour_la_suite_l_association">Pour la Suite (l'association):</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> Vous pouvez utiliser les « meilleures des espèces » dâ??applications pour chaque partie de la conception. Ceci étant, vous pouvez utiliser le flux standard de gEDA gschem â??gsch2pcb â??pcb pour créer un circuit imprimé. Néanmoins, si vous pensez que lâ??application open-source « PCB » craint, vous pouvez utiliser le flux gschem â??gnetlist â??Protel (par exemple). Rappelez-vous que gnetlist peut sortir plus de vingt différents formats de netlist! De plus, si vous nâ??aimez pas un des composants du flux, vous pouvez écrire un autre outil qui le remplacera. Maintenant, il est vrai, quâ??en ce moment, en général, quâ??il nâ??existe quâ??une seule application pour effectuer une tâche particulière. Cette situation devrait néanmoins changer avec le temps â?? comme en témoigne la nouvelle branche du projet « pcb », le netlister supplémentaire <a href="http://www.viasic.com/opensource/"; class="urlextern" title="http://www.viasic.com/opensource/"; rel="nofollow">gnetman</a>, de même que le projet <a href="http://web.comhem.se/~u31829222/"; class="urlextern" title="http://web.comhem.se/~u31829222/"; rel="nofollow">HEC</a>. En règle générale, lâ??approche de la suite offre la plus grande liberté à lâ??utilisateur.</div>
+</li>
+<li class="level1"><div class="li"> Le flux de la conception possède quelques points dâ??arrêts naturels. Cela se produit lorsquâ??un des outils achève son travail et lâ??écrit dans un dans un fichier (i.e. gschem écrit un fichier .sch ou gnetlist écrit une netlist SPICE). A ce point, vous pouvez facilement casser le flux et écrire des scripts qui traite totalement et/ou partiellement les données de lâ??étude. Pour les grands développements, câ??est un avantage réel dâ??avoir une approche de « suite de conception ». Cet avantage peut peut ne parler quâ??aux « utilisateurs intensifs » mais notez son importance: toutes les suites dâ??EDA de rang professionnel (Synopsys, Xilinx) travaillent de la même manière.</div>
+</li>
+<li class="level1"><div class="li"> Lâ??utilisation dâ??une suite dâ??applications peut être automatisé en utilisant un Makefile ou même un script <acronym title="Practical Extraction and Report Language">Perl</acronym>. Les concepteur dâ??ASIC le font en permanence avec leurs outils de schémas et de synthèse. Quelques utilisateurs gEDA ont publiquement annoncé (sur la liste de diffusion) quâ??ils le faisaient aussi et soulignent que câ??est une fonctionnalité importante de la suite gEDA.</div>
+</li>
+<li class="level1"><div class="li"> Extensibilité: une application monolithique est presque toujours développée un seul développeur qui a une vision unique de son programme. Ce développeur peut assurer un standard de style et dâ??interface utilisateur pour tous ses outils. Le problème avec ceci est quâ??un développeur seul ne peut écrire - même sâ??il est particulièrement doué - quâ??un (ou quelques) partie dâ??une application EDA. Câ??est la raison pour laquelle toute application EDA monolithique, open-source, sera toujours limitée dans son champ et ses fonctionnalités par les aptitudes dâ??un développeur seul. (Jâ??aimerais que lâ??on me prouve que jâ??ai tord sur ce point. Les contres-exemples sont les bienvenus mais aucun nâ??a attiré mon attention lors de lâ??écriture de cette partie.) Dâ??un autre côté, une assemblée de développeurs travaillant indépendamment sur leurs propres applications - tout en contribuant à lâ??oeuvre dans son ensemble â?? peuvent donc créer un environnement EDA très grand et très capable.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Pour la Suite (l'association):" [9862-13042] -->
+<h3><a name="contre_la_suite_l_association" id="contre_la_suite_l_association">Contre la Suite (l'association):</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> Câ??est plus difficile pour les nouveaux car ils ne connaissent pas le flux dâ??avance. Ceci étant, ils ont réellement besoin de <acronym title="Read The Fine Manual">RTFM</acronym> pour savoir quel est lâ??outil quâ??ils devront faire ensuite fonctionner. Une bonne documentation aide (câ??est la raison pour laquelle vous lisez ceci) mais elle reste toujours un second choix après le développement dâ??une interface intuitive.</div>
+</li>
+<li class="level1"><div class="li"> Les différents programmes peuvent avoir diverses conventions dâ??interfaces utilisateur (i.e. lâ??organisation du menu est différente, la fonctionnalité des touches ou de la souris sont différents). Ceci peut être désagréable pour ceux qui ne sont pas familiers avec les programmes.</div>
+</li>
+<li class="level1"><div class="li"> Comme aucune supposition nâ??est faite dans le flux de la conception, les symboles <a href="geda-faq-gschem.html#what_s_this_business_about_heavy_vs._light_symbols" class="wikilink1" title="geda-faq-gschem.html">légers</a> de schémas sont nécessaires. Cela impose à lâ??utilisateur de passer plus de temps à ajouter, par exemple, des attributs dâ??empreintes de composants à son schéma. De plus, lâ??utilisateur doit passer réellement plus de temps à trouver quelle empreinte utiliser. Néanmoins, une bonne suite (comme la suite gEDA) offrira de multiples méthodes pour effectuer cette tâche (i.e. gattrib, des scripts <acronym title="Practical Extraction and Report Language">Perl</acronym> pour faciliter les empreintes, etc.).</div>
+</li>
+<li class="level1"><div class="li"> Quelques développeurs sont plus énergiques que dâ??autres ou ont plus de temps libre. Câ??est la raison pour laquelle quelques programmes de la suite seront plus développés (et moins bogués) que dâ??autres. Malheureusement, un seul programme bogué dans une suite peut entacher la perception dâ??un nouvel utilisateur sur la suite complète.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Contre la Suite (l'association):" [13043-14705] -->
+<h3><a name="pour_les_applications_monolithiques" id="pour_les_applications_monolithiques">Pour les applications monolithiques:</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> Un environnement unique, unifié est plus facile à apréhender pour les utilisateurs. Les conventions dâ??interfaces utilisateur peuvent être harmonisées. Lâ??outil peut être suffisamment intuitif de telle manière quâ??il puisse être utilisé sans <acronym title="Read The Fine Manual">RTFM</acronym>.</div>
+</li>
+<li class="level1"><div class="li"> Les symboles de schémas peuvent être complets, avec moins de travail nécessaire pour lâ??attachement des attributs à chaque symbole dans un schéma.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Pour les applications monolithiques:" [14706-15166] -->
+<h3><a name="contre_les_applications_monolithiques" id="contre_les_applications_monolithiques">Contre les applications monolithiques:</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> Elles ne sont pas ajustables indéfiniment. Un développeur ne peut pas tout faire, quelque soit sa force. Câ??est la raison pour laquelle une application monolithique nâ??aura jamais la puissance dâ??une suite développée par une confédération de programmeurs.</div>
+</li>
+<li class="level1"><div class="li"> Manque de choix. Si le développeur nâ??aime pas votre manière de faire les choses, vous nâ??auvez aucun autre choix. Même si vous soumettez des patches pour permettre pour pouvoir travailler à votre manière, il est possible que le développeur principal ignore ou rejette vos modifications. Ce nâ??est probablement pas grave pour les nouveaux mais çà lâ??est pour les « utilisateurs intensifs ».</div>
+</li>
+<li class="level1"><div class="li"> Risque. Si le développeur de lâ??application abandonne, le code est abandoné et les utilisateurs en patissent. Câ??est ce qui sâ??est produit avec le programme <a href="http://sourceforge.net/projects/xtrkcad"; class="urlextern" title="http://sourceforge.net/projects/xtrkcad"; rel="nofollow">XTrkCAD</a>, un programme de CAO pour concevoir des voies ferrées. Lâ??auteur du programme a cessé de le développer mais lâ??a heureusement placé sur Sourceforge pour lâ??empêcher de disparaître. Malheureusement, sans lâ??implication du développeur originel, le code a stagné. Les patches des contributeurs sont allés dans /dev/null. Une coalition dâ??utilisateurs/développeurs ont fini par créer un <a href="http://xtrkcad-fork.sourceforge.net/"; class="urlextern" title="http://xtrkcad-fork.sourceforge.net/"; rel="nofollow">fork</a> du code pour permettre un développement ultérieur. Néanmoins, le travail sur le code forké a été parcimonieux et sporadique. (Jâ??espère que cela changera un jour.) pendant ce temps, pour lâ??utilisateur normal, lâ??abandon du développeur a représenté une catastrophe.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Contre les applications monolithiques:" [15167-16800] -->
+<h2><a name="quelle_est_la_licence_utilisee_par_geda" id="quelle_est_la_licence_utilisee_par_geda">Quelle est la licence utilisée par gEDA?</a></h2>
+<div class="level2">
+
+<p>
+Tous les outils et fichiers associés de gEDA sont sous GNU General Public License version 2 (<acronym title="GNU General Public License">GPL</acronym>), de la Free Software Foundation
+</p>
+
+<p>
+La licence:
+</p>
+
+<p>
+Lorsque nous parlons de logiciels libre, nous nous référons à la liberté, pas au prix. Nos « General Public Licenses » sont conçues pour sâ??assurer que vous avez la liberté de distribuer des copies des logiciels libres (et de faire payer pour ce service si vous le souhaitez), que vous recevez le code source ou que vous puissiez lâ??obtenir si vous le souhaitez, que vous pouvez modifier le logiciel ou en utiliser des morceaux dans de nouveaux programmes libres; et que vous sachiez comment le faire.
+</p>
+
+<p>
+Ce nâ??est jamais assez répété: « gEDA est un logiciel <acronym title="GNU General Public License">GPL</acronym> ». Câ??est la raison pour laquelle rien de propriétaire ne peut être distribué avec gEDA, tel que les bibliothèques de composants depuis les produits dâ??EDA propriétaires. Le programme de conversion pour les bibliothèques propriétaires sera disponible mais les fichiers de conversion qui font partie du produit propriétaire ne doivent jamais être mis dans gEDA. Les fichiers contribués doivent pouvoir être <acronym title="GNU General Public License">GPL</acronym> (ou être placé sous une autre licence libre). Veuillez garder ceci en mémoire si vous souhaitez y contribuer.
+</p>
+
+<p>
+Bien que lâ??ojectif de gEDA soit les logiciels <acronym title="GNU General Public License">GPL</acronym>, les logiciels avec dâ??autres licences sont plus que les bienvenus, tant quâ??ils restent compatibles avec la <acronym title="GNU General Public License">GPL</acronym>.
+</p>
+
+</div>
+<!-- SECTION "Quelle est la licence utilisée par gEDA?" [16801-18267] -->
+<h2><a name="ou_puis-je_avoir_plus_d_informations_a_propos_de_geda_et_sur_son_telechargement" id="ou_puis-je_avoir_plus_d_informations_a_propos_de_geda_et_sur_son_telechargement">Où puis-je avoir plus d'informations à propos de gEDA et sur son téléchargement?</a></h2>
+<div class="level2">
+
+<p>
+Le site officiel est <a href="http://www.gpleda.org/"; class="urlextern" title="http://www.gpleda.org/"; rel="nofollow">gEDA Project</a>, hébergé par le <a href="http://www.seul.org/"; class="urlextern" title="http://www.seul.org/"; rel="nofollow">projet SEUL</a>. Le miroir européen est sur <a href="http://ftp.sunet.se/geda/"; class="urlextern" title="http://ftp.sunet.se/geda/"; rel="nofollow">miroir du projet Européen de gEDA</a> hébergé par le réseau des universités suédoises.
+</p>
+
+<p>
+Il existe plusieurs listes de diffusion. Veuillez aller voir la <a href="http://www.gpleda.org/mailinglists/index.html"; class="urlextern" title="http://www.gpleda.org/mailinglists/index.html"; rel="nofollow">page d'info</a> sur les listes de diffusion pour savoir comment souscrire et poster.
+</p>
+
+<p>
+Vous pouvez télécharger tous les logiciels, incluant la suite gEDA sur CDROM depuis la page <a href="http://geda.seul.org/download.html"; class="urlextern" title="http://geda.seul.org/download.html"; rel="nofollow">download</a>.
+</p>
+
+<p>
+Vous pouvez trouver le dernier jeu de documentation sur la page de sommaire <a href="http://geda.seul.org/wiki/"; class="urlextern" title="http://geda.seul.org/wiki/"; rel="nofollow">documentation</a>.
+</p>
+
+<p>
+Venez à la réunion des « Free EDA Users Group » (Freedog) de Cambridge, MA. La réunion est à 7H le premier mercredi de chaque mois au <a href="http://www.starbucks.com/retail/locator/MapResults.aspx?a=1&StoreKey=93728&IC_O=42.3599350625432%3a-71.1021394862385%3a32%3a02139+(postal+code)%2c+Massachusetts%2c+United+States&GAD1_O=&GAD2_O=&GAD3_O=02139+(postal+code)%2c+Massachusetts%2c+United+States&GAD4_O=&radius=5&countryID=244&dataSource=MapPoint.NA" class="urlextern" title="http://www.starbucks.com/retail/locator/MapResults.aspx?a=1&StoreKey=93728&IC_O=42.3599350625432%3a-71.1021394862385%3a32%3a02139+(postal+code)%2c+Massachusetts%2c+United+States&GAD1_O=&GAD2_O=&GAD3_O=02139+(postal+code)%2c+Massachusetts%2c+United+States&GAD4_O=&radius=5&countryID=244&dataSource=MapPoint.NA" rel="nofollow">Kendal Square Starbucks</a>.
+</p>
+
+</div>
+<!-- SECTION "Où puis-je avoir plus d'informations à propos de gEDA et sur son téléchargement?" [18268-19571] -->
+<h2><a name="ok_comment_je_comence_a_utiliser_geda" id="ok_comment_je_comence_a_utiliser_geda">OK, comment je comence à utiliser gEDA?</a></h2>
+<div class="level2">
+
+<p>
+La chose la plus importante à faire est de lire et de comprendre lâ??excellent tutoriel de Bill Wilson <a href="geda-gsch2pcb_tutorial.html" class="wikilink1" title="geda-gsch2pcb_tutorial.html">gschem -> gsch2pcb -> PCB</a>. Cela vous permettra de débuter.
+</p>
+
+<p>
+Assurez-vous aussi de visionner les autres <a href="http://geda.seul.org/docs"; class="urlextern" title="http://geda.seul.org/docs"; rel="nofollow">documentations gEDA</a>. Un guide dâ??installation est contenu dans ce Wiki, ainsi que des informations générales sur lâ??utilisation de ces outils. Prenez un peu de temps à naviguer, télécharger la Suite gEDA Suite et essayez-le par vous même!
+</p>
+
+</div>
+<!-- SECTION "OK, comment je comence à utiliser gEDA?" [19572-] --></body>
+</html>
diff --git a/docs/wiki/geda-faq.html b/docs/wiki/geda-faq.html
new file mode 100644
index 0000000..10d1663
--- /dev/null
+++ b/docs/wiki/geda-faq.html
@@ -0,0 +1,353 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#geda_faq" class="toc">gEDA FAQ</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#what_is_the_geda_project" class="toc">What is the gEDA project?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#what_is_geda_gaf_and_how_does_it_relate_to_geda" class="toc">What is gEDA/gaf and how does it relate to gEDA?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#what_is_the_geda_suite" class="toc">What is the gEDA suite?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#why_what_makes_geda_so_different_from_other_eda_tools" class="toc">Why? What makes gEDA so different from other EDA tools?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#why_does_the_geda_suite_seem_like_a_collection_of_random_programs_and_not_a_single_integrated_application" class="toc">Why does the gEDA Suite seem like a collection of random programs, and not a single integrated application?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#so_which_is_better_a_suite_i.e._confederacy_of_programs_or_an_integrated_application" class="toc">So which is better, a suite (i.e. confederacy) of programs or an integrated application?</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#suite_confederacy_pros" class="toc">Suite (confederacy) pros:</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#suite_confederacy_cons" class="toc">Suite (confederacy) cons:</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#monolithic_application_pros" class="toc">Monolithic application pros:</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#monolithic_application_cons" class="toc">Monolithic application cons:</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#tool_xxx_is_missing_critical_feature_yyy_what_can_i_do" class="toc">Tool XXX is missing critical feature YYY! What can I do?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#what_license_does_geda_use" class="toc">What license does gEDA use?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#where_can_i_get_more_information_about_and_download_geda" class="toc">Where can I get more information about and download gEDA?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#okay_how_do_i_start_using_geda" class="toc">Okay, how do I start using gEDA?</a></span></div></li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="geda_faq" id="geda_faq">gEDA FAQ</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "gEDA FAQ" [1-25] -->
+<h2><a name="what_is_the_geda_project" id="what_is_the_geda_project">What is the gEDA project?</a></h2>
+<div class="level2">
+
+<p>
+The gEDA project has produced and continues working on a full <acronym title="GNU General Public License">GPL</acronym>â??d suite and toolkit of Electronic Design Automation tools. These tools are used for electrical circuit design, schematic capture, simulation, prototyping, and production. Currently, the gEDA project offers a mature suite of free software applications for electronics design, including schematic capture, attribute management, bill of materials (BOM) generation, netlisting into over 20 netlist formats, analog and digital simulation, and printed circuit board (PCB) layout.
+</p>
+
+<p>
+The gEDA project was launched by Ales Hvezda in Spring 1998 in order to advance the state of free hardware and open source hardware. Over the past ten years, the gEDA software and the community have grown considerably. A few people are contributing to the original tools, while others are doing their own development on their own tools. â??gEDAâ?? does not refer solely to the original tools anymore (those tools now stand on their own), but instead to all the projects which are free and are somehow associated with this webpage or the geda-dev/geda-user mailing lists. By associating with gEDA, free software authors do not give up any control over their tools, but they gain a community which cares about quality and free (as in freedom) EDA tools.
+</p>
+
+<p>
+gEDA can be pronounced â??gee-daahhhâ?? (rhymes with cheetah) or â??g-dahhh (short g).
+</p>
+
+</div>
+<!-- SECTION "What is the gEDA project?" [26-1445] -->
+<h2><a name="what_is_geda_gaf_and_how_does_it_relate_to_geda" id="what_is_geda_gaf_and_how_does_it_relate_to_geda">What is gEDA/gaf and how does it relate to gEDA?</a></h2>
+<div class="level2">
+
+<p>
+<strong>gaf</strong> stands for â??<em class="u">g</em>schem <em class="u">a</em>nd <em class="u">f</em>riendsâ??. It is a subset of the entire tool suite grouped together under the gEDA name. gEDA/gaf is a collection of tools which currently includes:
+</p>
+<ul>
+<li class="level1"><div class="li"> gschem: A schematic capture program</div>
+</li>
+<li class="level1"><div class="li"> gnetlist: A netlist generation program</div>
+</li>
+<li class="level1"><div class="li"> gsymcheck: A syntax checker for schematic symbols</div>
+</li>
+<li class="level1"><div class="li"> gattrib: A spreadsheet programm that manipulates the properties of symbols of a schematic</div>
+</li>
+<li class="level1"><div class="li"> libgeda: Libraries for gschem gnetlist and gsymcheck</div>
+</li>
+<li class="level1"><div class="li"> gsch2pcb: A tool to forward annotation from your schematic to layout using <a href="geda-pcb.html" class="wikilink2" title="geda-pcb.html">PCB</a></div>
+</li>
+<li class="level1"><div class="li"> some minor utilities</div>
+</li>
+</ul>
+
+<p>
+ The gEDA/gaf tools share a common file format (.sch) and also share a common link library (libgeda.so). The gEDA/gaf source distribution can be found on this website (geda.seul.org).
+</p>
+
+<p>
+Even though gaf is very much a part of gEDA, the gEDA name does not necessarily only apply to gaf â?? tools gathered under the â??gEDAâ?? moniker include many other programs. Indeed, gEDA refers to <strong>any</strong> <acronym title="GNU General Public License">GPL</acronym>â??d EDA tool which decides to associate itself with the gEDA website/mailing list. Important examples of gEDA tools include the layout program <a href="geda-pcb.html" class="wikilink2" title="geda-pcb.html">PCB</a>, the Verilog compiler <a href="http://www.icarus.com/eda/verilog/"; class="urlextern" title="http://www.icarus.com/eda/verilog/"; rel="nofollow">Icarus Verilog</a>, the analog circuit simulator <a href="http://www.gnucap.org/"; class="urlextern" title="http://www.gnucap.org/"; rel="nofollow">gnucap</a>, and the open-source SPICE simulator <a href="http://www.ngspice.org/"; class="urlextern" title="http://www.ngspice.org/"; rel="nofollow">ngspice</a>. Many other gEDA programs also exist.
+</p>
+
+<p>
+For historical reasons, on <a href="http://freshmeat.net/"; class="urlextern" title="http://freshmeat.net/"; rel="nofollow">freshmeat</a> gaf is known as the package â??gEDAâ??.
+</p>
+
+</div>
+<!-- SECTION "What is gEDA/gaf and how does it relate to gEDA?" [1446-3012] -->
+<h2><a name="what_is_the_geda_suite" id="what_is_the_geda_suite">What is the gEDA suite?</a></h2>
+<div class="level2">
+
+<p>
+The gEDA suite is the collection of all the various tools that are part of, associated with, or just plain work with the gEDA projectâ??s software. Currently the gEDA suite includes:
+</p>
+<ul>
+<li class="level1"><div class="li"> <a href="http://geda.seul.org/tools/"; class="urlextern" title="http://geda.seul.org/tools/"; rel="nofollow">gEDA/gaf</a> â?? schematic capture and netlisting</div>
+</li>
+<li class="level1"><div class="li"> <a href="http://geda.seul.org/tools/ngspice"; class="urlextern" title="http://geda.seul.org/tools/ngspice"; rel="nofollow">ngspice</a> â?? SPICE simulation</div>
+</li>
+<li class="level1"><div class="li"> <a href="http://geda.seul.org/tools/gnucap"; class="urlextern" title="http://geda.seul.org/tools/gnucap"; rel="nofollow">gnucap</a> â?? analog simulation</div>
+</li>
+<li class="level1"><div class="li"> <a href="http://geda.seul.org/tools/gspiceui"; class="urlextern" title="http://geda.seul.org/tools/gspiceui"; rel="nofollow">gspiceui</a> â?? <acronym title="Graphical User Interface">GUI</acronym> front end for ngspice/gnucap</div>
+</li>
+<li class="level1"><div class="li"> <a href="http://geda.seul.org/tools/pcb"; class="urlextern" title="http://geda.seul.org/tools/pcb"; rel="nofollow">pcb</a> â?? PCB layout</div>
+</li>
+<li class="level1"><div class="li"> <a href="http://geda.seul.org/tools/gerbv"; class="urlextern" title="http://geda.seul.org/tools/gerbv"; rel="nofollow">gerbv</a> â?? Gerber viewer</div>
+</li>
+<li class="level1"><div class="li"> <a href="http://geda.seul.org/tools/icarus"; class="urlextern" title="http://geda.seul.org/tools/icarus"; rel="nofollow">Icarus Verilog</a> â?? Verilog simulator</div>
+</li>
+<li class="level1"><div class="li"> <a href="http://geda.seul.org/tools/gtkwave"; class="urlextern" title="http://geda.seul.org/tools/gtkwave"; rel="nofollow">GTKWave</a> â?? Digital waveform viewer</div>
+</li>
+<li class="level1"><div class="li"> <a href="http://wcalc.sourceforge.net/"; class="urlextern" title="http://wcalc.sourceforge.net/"; rel="nofollow">wcalc</a> â?? Transmission line and electromagnetic structure analysis</div>
+</li>
+</ul>
+
+<p>
+ One way of downloading and install most of the above tool is to use the â??gEDA Suite Binaryâ?? installer. The gEDA suite Binary installer is available from the <a href="http://geda.seul.org/download.html"; class="urlextern" title="http://geda.seul.org/download.html"; rel="nofollow">download</a> page. <strong>Note: The installer works only with i386 GNU/Linux!</strong>
+</p>
+
+</div>
+<!-- SECTION "What is the gEDA suite?" [3013-4204] -->
+<h2><a name="why_what_makes_geda_so_different_from_other_eda_tools" id="why_what_makes_geda_so_different_from_other_eda_tools">Why? What makes gEDA so different from other EDA tools?</a></h2>
+<div class="level2">
+
+<p>
+Tools in the gEDA suite and associated tools have the following characteristics:
+</p>
+<ul>
+<li class="level1"><div class="li"> Free in the monetary sense (no cost).</div>
+</li>
+<li class="level1"><div class="li"> All the file formats and source code are available via the <acronym title="GNU General Public License">GPL</acronym> license. This license grants specific rights to the authors and users of <acronym title="GNU General Public License">GPL</acronym>â??d software.</div>
+</li>
+<li class="level1"><div class="li"> Independence from any one vendor. All gEDA tools come with full source. You may freely redistribute, change, improve and port the tools. You may also distribute your changes, if you follow the terms of the <acronym title="GNU General Public License">GPL</acronym>.</div>
+</li>
+<li class="level1"><div class="li"> No mechanism is used to restrict the use of the tools (like making use of hard disk serial numbers or ethernet addresses to force the software to only run on one machine).</div>
+</li>
+<li class="level1"><div class="li"> No arbitrary, marketeering-driven limitations. Free versions of commercial tools usually include capricious limitations (i.e. limited design size, inability to print, inability to export netlists, etc.) which cripple the program, and force the serious user to buy the real tool. In contrast, the gEDA tools are fully-featured, and do not arbitrarily impose limits on design as a way of extracting money from you.</div>
+</li>
+<li class="level1"><div class="li"> Legacy design protection. Since the software will always be available, and can always be updated to work with updated operating systems or libraries, gEDA tool design files will always be viewable and editable.</div>
+</li>
+<li class="level1"><div class="li"> Open design flow. This means that the tools talk to each other via known and documented means (files / APIs). It is easy to replace a tool or augment the tools with something else if you so desire. The gEDA suite is an EDA toolkit. The individual pieces are loosely coupled and allow for end users to customize or replaces parts of the design flow.</div>
+</li>
+<li class="level1"><div class="li"> Stability - Bugs which cause crashes are investigated immediately and fixed as soon as possible.</div>
+</li>
+<li class="level1"><div class="li"> Minimize bloat and unnecessary features.</div>
+</li>
+<li class="level1"><div class="li"> Run on as many platforms as possible. For gEDA/gaf: GNU/Linux, various other Unix systems.</div>
+</li>
+<li class="level1"><div class="li"> Developed in an open (no secrets) fashion.</div>
+</li>
+<li class="level1"><div class="li"> Strive to be documented.</div>
+</li>
+</ul>
+
+<p>
+ gEDA may not have all the latest cutting edge features found in other packages and may be viewed sometimes as being on the trailing edge of EDA technology, but the tools are becoming useful to a lot of people for the above mentioned reasons.
+</p>
+
+</div>
+<!-- SECTION "Why? What makes gEDA so different from other EDA tools?" [4205-6491] -->
+<h2><a name="why_does_the_geda_suite_seem_like_a_collection_of_random_programs_and_not_a_single_integrated_application" id="why_does_the_geda_suite_seem_like_a_collection_of_random_programs_and_not_a_single_integrated_application">Why does the gEDA Suite seem like a collection of random programs, and not a single integrated application?</a></h2>
+<div class="level2">
+
+<p>
+The gEDA suite is indeed a confederacy of somewhat independent programs. This happened for reasons of history: Ales Hvezda started the gEDA project more or less on his own. The original vision was to produce an end-to-end software suite for creating PC boards so that robotics hobbiests could design their own boards. However, as the gEDA project progressed the large magnitude of this task became clear â?? and coding many of the proposed apps had not even begun!
+</p>
+
+<p>
+Meanwhile, other software developers â?? with their own independently written applications â?? found the gEDA project vision compelling. The authors of those applications joined Ales and contributed their programs to the gEDA project. Amongst the contributed projects was â??pcbâ??, a ten year old (at that time) PCB layout program. With the contribution of â??pcbâ??, gEDAâ??s originally planned layout tool â??gpcbâ?? was scuttled. At the same time, other developers contributed analog and digital simulators, waveform viewers, and so on.
+</p>
+
+<p>
+In this way the gEDA suite came together. It is not shared code, or a common user interface which distinguishes the gEDA suite. Rather, the shared vision of an open-source EDA environment is the thread which holds the project together. Today, the gEDA Suite is a collection of many different programs contributed by many different authors. The apps strive to work together, and usually succeed. But the separate beginnings of each program in the suite are still observable. Nonetheless, with a little work the various components of the suite are interoperable, and many people have completed quite complex board designs using the gEDA suite.
+</p>
+
+<p>
+In the end, the best way to think about the gEDA suite is as an EDA toolkit. This toolkit approach gives the end user considerable control. End users can modify or completely replaces parts of the design flow to suit their own requirements.
+</p>
+
+</div>
+<!-- SECTION "Why does the gEDA Suite seem like a collection of random programs, and not a single integrated application?" [6492-8506] -->
+<h2><a name="so_which_is_better_a_suite_i.e._confederacy_of_programs_or_an_integrated_application" id="so_which_is_better_a_suite_i.e._confederacy_of_programs_or_an_integrated_application">So which is better, a suite (i.e. confederacy) of programs or an integrated application?</a></h2>
+<div class="level2">
+
+<p>
+This is ultimately a matter of religion. Iâ??ll summarize some of the pros and cons (as I see them) of each approach here.
+</p>
+
+</div>
+<!-- SECTION "So which is better, a suite (i.e. confederacy) of programs or an integrated application?" [8507-8731] -->
+<h3><a name="suite_confederacy_pros" id="suite_confederacy_pros">Suite (confederacy) pros:</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> You can use â??best of breedâ?? applications for each part of the design flow. That is, you can use the standard gEDA flow gschem â?? gsch2pcb â?? pcb to create a PC Board. However, if you think that the open-source application â??pcbâ?? stinks, you can use the flow gschem â?? gnetlist â?? Protel (for example). Recall that gnetlist can output more than twenty different netlist formats! Moreover, if you donâ??t like one component of the flow, you can write another tool to replace it. Now at this time it is true that only a single application generally exists to perform a particular task. However, this situation will likely change with time â?? witness the forking of the â??pcbâ?? project, the contributed netlister <a href="http://www.viasic.com/opensource/"; class="urlextern" title="http://www.viasic.com/opensource/"; rel="nofollow">gnetman</a>, as well as the <a href="http://web.comhem.se/~u31829222/"; class="urlextern" title="http://web.comhem.se/~u31829222/"; rel="nofollow">HEC</a> project. As a general rule, the suite approach offers the greatest freedom to the user.</div>
+</li>
+<li class="level1"><div class="li"> The design flow has a lot of natural breakpoints. These occur where one design tool completes its job and writes out a file (i.e. gschem writes out a .sch file, or gnetlist writes out a SPICE netlist). At this point, you can easily break into the flow and write scripts which process and/or munge the design data. For big, advanced designs, this is a real advantage to the â??design suiteâ?? approach. This advantage may appeal only to the â??power userâ??, but note its importance: professional-grade EDA suites (Synopsys, Xilinx) also work the same way.</div>
+</li>
+<li class="level1"><div class="li"> Usage of an applications suite can be automated using a Makefile, or even a <acronym title="Practical Extraction and Report Language">Perl</acronym> script. ASIC designers do this all the time with their design and synthesis tools. Some gEDA users have stated on the e-mail list that they do this too, and point to it as an important feature of the gEDA suite.</div>
+</li>
+<li class="level1"><div class="li"> Scalability: A monolithic application is almost always developed by a lone developer who has a single-minded vision for his program. This developer can enforce stylistic and UI standards throughout all his tools. The problem with this is that a single developer â?? even one who is uniquely gifted â?? can only write one or two parts of an EDA application. Therefore, any open-source, monolithic EDA app will likely always be limited in scope and features by the abilities of a single developer. (I would love to be proven wrong on this point. I welcome counter-examples, but none have come to my attention as of this writing.) On the other hand, a confederacy of developers working independently on their own apps â?? but meanwhile contributing to a greater whole â?? can create a very large and capable EDA environment indeed.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Suite (confederacy) pros:" [8732-11376] -->
+<h3><a name="suite_confederacy_cons" id="suite_confederacy_cons">Suite (confederacy) cons:</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> More confusing to new users, since they donâ??t know the flow right off the bat. That is, they actually need to <acronym title="Read The Fine Manual">RTFM</acronym> to know what tool to run next. Good documentation helps (thatâ??s why youâ??re reading this), but documentation is always second choice behind developing an intuitive application interface.</div>
+</li>
+<li class="level1"><div class="li"> Different programs have different UI conventions (i.e. menu organization is different, keyboard or mouse bindings are different). This can be uncomfortable to those who arenâ??t familiar with the programs.</div>
+</li>
+<li class="level1"><div class="li"> Since no assumptions are made about the design flow, schematic symbols are necessarily <a href="geda-faq-gschem.html#what_s_this_business_about_heavy_vs._light_symbols" class="wikilink1" title="geda-faq-gschem.html">light</a>. This forces the user to spend more time attaching e.g. footprint attributes to his design. Moreover, the user must spend more time actually researching which footprints to use. However, a good suite (like the gEDA suite) will offer multiple methods to perform this task (e.g. gattrib, <acronym title="Practical Extraction and Report Language">Perl</acronym> scripts to populate footprints, etc.).</div>
+</li>
+<li class="level1"><div class="li"> Some developers are more energetic than others, or have more free time. Therefore, some programs in a suite will be more developed (and less buggy) than others. Unfortunately, a single buggy program in a suite can unfairly taint a new userâ??s perception of the entire suite.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Suite (confederacy) cons:" [11377-12712] -->
+<h3><a name="monolithic_application_pros" id="monolithic_application_pros">Monolithic application pros:</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> A single, unified design environment is easier for new users to grasp. UI conventions may be harmonized. The tool might be intuitive enough that it can be driven without needing to <acronym title="Read The Fine Manual">RTFM</acronym>.</div>
+</li>
+<li class="level1"><div class="li"> Schematic capture symbols can be heavy, so less work is required in attaching attributes to each symbol in a schematic.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Monolithic application pros:" [12713-13067] -->
+<h3><a name="monolithic_application_cons" id="monolithic_application_cons">Monolithic application cons:</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> Not infinitely scalable. One developer canâ??t do everything, no matter how smart. Therefore, a monolithic app will never approach the size or power of a suite developed by a confederacy of programmers.</div>
+</li>
+<li class="level1"><div class="li"> Lack of choice. If the developer doesnâ??t like your way of doing things, you have no choice. Even if you submit patches to enable your way of performing a task, there is a chance the main developer will ignore or reject your patches. This is probably not an issue for newbies, but for â??power usersâ?? it represents a problem.</div>
+</li>
+<li class="level1"><div class="li"> Risk. If the developer quits, the code becomes abandoned, and the users suffer. This effectively happened to the program <a href="http://sourceforge.net/projects/xtrkcad"; class="urlextern" title="http://sourceforge.net/projects/xtrkcad"; rel="nofollow">XTrkCAD</a>, a CAD program for designing model railroads. The author of this program quit developing it, but thankfully placed his stuff on Sourceforge so that the program wouldnâ??t simply disappear. Unfortunately, without the original developerâ??s involvement, the code languished. Patches contributed to the project went to /dev/null. Eventually, a coalition of concerned user/developers created a <a href="http://xtrkcad-fork.sourceforge.net/"; class="urlextern" title="http://xtrkcad-fork.sourceforge.net/"; rel="nofollow">fork</a> of the code to enable further development. However, work on the forked code has been piecemeal and sporadic. (Hopefully, this will change someday.) Meanwhile, for the ordinary user, the fact that the original developer quit represents a catastrophe.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Monolithic application cons:" [13068-14511] -->
+<h2><a name="tool_xxx_is_missing_critical_feature_yyy_what_can_i_do" id="tool_xxx_is_missing_critical_feature_yyy_what_can_i_do">Tool XXX is missing critical feature YYY! What can I do?</a></h2>
+<div class="level2">
+
+<p>
+Newbies sometimes show up on the gEDA mailing lists and flame the project for missing features, perceived bugs, and supppoesd UI quirks. The gEDA developers are very interested in receiving constructive feedback and criticism, so we do welcome feature requests and bug reports. But please keep in mind that the developers are full-time professional EEs or software engineers, and work on gEDA as an unpaid, fun hobby. Unconstructive or ill-informed flames are not the way to get new features implemented.
+</p>
+
+<p>
+If you need a new feature implemented in one of the gEDA tools, here are your options:
+</p>
+<ul>
+<li class="level1"><div class="li"> Write it yourself. The code is open and available for everybody to see, understand, and modify. If you have implemented a new feature, please <a href="http://sourceforge.net/tracker/?atid=818428&group_id=161080&func=browse"; class="urlextern" title="http://sourceforge.net/tracker/?atid=818428&group_id=161080&func=browse"; rel="nofollow">submit your patches</a> to the project; chances are good that they will be incorporated into the main development branch.</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> Ask politely on the gEDA e-mail lists. If your feature request is simple, or of interest to one of the developers, itâ??s possible that somebody will implement your feature. If itâ??s more complicated, itâ??s likely that the feature is already under discussion amongst the developers, but nobody has enough spare time to implement it. (You can also submit feature requests via the <a href="http://sourceforge.net/tracker/?atid=818429&group_id=161080&func=browse"; class="urlextern" title="http://sourceforge.net/tracker/?atid=818429&group_id=161080&func=browse"; rel="nofollow">SourceForge feature requests tracker.</a>) Please donâ??t rant or flame on the e-mail lists, since you will likely be flamed right back and you wonâ??t get your feature either. Why waste your time?</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> If the above possibilities donâ??t work for you, hire an open-source developer to write the feature for you! Itâ??s amazing how often this possibility is ignored. People willing to pay $25,000 – $100,000 for commercial EDA tools will balk at paying a teen-age programming whiz $10/hr to re-create the same features in the gEDA Suite. Why? If youâ??re an educator, consider hiring some students for a UROP project to work on gEDA. If you run a business, hire a teenager or somebody fresh out of school! And if you want seasoned help, you can (soon) turn to some of the main gEDA developers who do consulting.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Tool XXX is missing critical feature YYY! What can I do?" [14512-16777] -->
+<h2><a name="what_license_does_geda_use" id="what_license_does_geda_use">What license does gEDA use?</a></h2>
+<div class="level2">
+
+<p>
+All of the tools and associated files in gEDA will be released under the GNU General Public License version 2 (<acronym title="GNU General Public License">GPL</acronym>), from the Free Software Foundation.
+</p>
+
+<p>
+From the license:
+</p>
+
+<p>
+â??When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things."
+</p>
+
+<p>
+This cannot be stressed enough: <strong>gEDA is GPLed software</strong>. Therefore nothing proprietary can be distributed with gEDA like part libraries from proprietary EDA products. Conversion programs for proprietary libraries will be available, but any converted files which are part of a proprietary product must never find their way into gEDA. Contributed files must be GPLable (or be placed under another free license). Please keep this in mind if you wish to contribute something.
+</p>
+
+<p>
+Even though the focus of gEDA is GPLed software, other software licenses are more than welcome to be mixed with the existing software, as long as they are compatible with the <acronym title="GNU General Public License">GPL</acronym>.
+</p>
+
+</div>
+<!-- SECTION "What license does gEDA use?" [16778-18060] -->
+<h2><a name="where_can_i_get_more_information_about_and_download_geda" id="where_can_i_get_more_information_about_and_download_geda">Where can I get more information about and download gEDA?</a></h2>
+<div class="level2">
+
+<p>
+The official website is <a href="http://geda.seul.org/"; class="urlextern" title="http://geda.seul.org/"; rel="nofollow">gEDA Project</a> hosted by the <a href="http://www.seul.org/"; class="urlextern" title="http://www.seul.org/"; rel="nofollow">SEUL Project</a>. The European mirror is at <a href="http://ftp.sunet.se/geda/"; class="urlextern" title="http://ftp.sunet.se/geda/"; rel="nofollow">European gEDA Project mirror</a> hosted by Swedish University Network - Sweden, Northern Europe.
+</p>
+
+<p>
+There are several mailing lists. Please look at the mailing list <a href="http://geda.seul.org/mailinglist"; class="urlextern" title="http://geda.seul.org/mailinglist"; rel="nofollow">info page</a> for how to subscribe and post.
+</p>
+
+<p>
+You can download all the software, including the gEDA Suite Binary installer, from the <a href="http://geda.seul.org/download.html"; class="urlextern" title="http://geda.seul.org/download.html"; rel="nofollow">download</a> page.
+</p>
+
+<p>
+You can find the latest set of documentation on the top-level <a href="http://geda.seul.org/docs/"; class="urlextern" title="http://geda.seul.org/docs/"; rel="nofollow">documentation</a> page.
+</p>
+
+<p>
+Come to the Free EDA Users Group (Freedog) meeting. These meetings are an informal way to meet some of the gEDA developers and users. The meetings are held in the metro Boston, MA (USA) area. Sometimes they are held at one of the developerâ??s homes, while other times they are held at a local cafe. Meeting times vary, so send an e-mail to the geda-user mailing list for more information.
+</p>
+
+</div>
+<!-- SECTION "Where can I get more information about and download gEDA?" [18061-19190] -->
+<h2><a name="okay_how_do_i_start_using_geda" id="okay_how_do_i_start_using_geda">Okay, how do I start using gEDA?</a></h2>
+<div class="level2">
+
+<p>
+The most important thing to do is to read and understand one or both of the tutorials available online:
+</p>
+<ul>
+<li class="level1"><div class="li"> Bill Wilsonâ??s excellent <a href="geda-gsch2pcb_tutorial.html" class="wikilink1" title="geda-gsch2pcb_tutorial.html">gschem -> gsch2pcb -> PCB</a> tutorial.</div>
+</li>
+<li class="level1"><div class="li"> DJ Delorieâ??s <a href="http://www.delorie.com/pcb/docs/gs/gs.html"; class="urlextern" title="http://www.delorie.com/pcb/docs/gs/gs.html"; rel="nofollow">tutorial on pcb</a> also covers basic usage of gschem.</div>
+</li>
+</ul>
+
+<p>
+ Also be sure to check out the other <a href="geda-documentation.html" class="wikilink1" title="geda-documentation.html">gEDA documentation</a>. An installation guide is contained in this Wiki, as is some general information about how to use the tools. Spend some time browsing, download the gEDA Suite, and try it out for yourself!
+</p>
+
+</div>
+<!-- SECTION "Okay, how do I start using gEDA?" [19191-] --></body>
+</html>
diff --git a/docs/wiki/geda-fbabgapp.html b/docs/wiki/geda-fbabgapp.html
new file mode 100644
index 0000000..f6a5e7e
--- /dev/null
+++ b/docs/wiki/geda-fbabgapp.html
@@ -0,0 +1,211 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#forward_backward_annotation_between_geda_gaf_and_pads_powerpcb" class="toc">Forward/Backward Annotation Between gEDA/gaf and PADS PowerPCB</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#forward_annotation_of_geda_schematic_changes_to_pads_powerpcb_layout" class="toc">Forward Annotation of gEDA Schematic Changes to PADS PowerPCB Layout</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#overview" class="toc">Overview</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#detailed_forward_annotation_procedure" class="toc">Detailed Forward Annotation Procedure</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#back_annotation_of_pads_powerpcb_layout_changes_to_geda_schematic" class="toc">Back Annotation of PADS PowerPCB Layout Changes to gEDA Schematic</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#detailed_backannotation_procedure" class="toc">Detailed Backannotation Procedure</a></span></div></li></ul>
+</li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="forward_backward_annotation_between_geda_gaf_and_pads_powerpcb" id="forward_backward_annotation_between_geda_gaf_and_pads_powerpcb">Forward/Backward Annotation Between gEDA/gaf and PADS PowerPCB</a></h1>
+<div class="level1">
+
+<p>
+by: Dan McMahill
+</p>
+
+<p>
+This document is released under <a href="http://www.gnu.org/copyleft/fdl.html"; class="urlextern" title="http://www.gnu.org/copyleft/fdl.html"; rel="nofollow">GFDL</a>
+</p>
+
+<p>
+March 6th, 2003
+</p>
+
+</div>
+<!-- SECTION "Forward/Backward Annotation Between gEDA/gaf and PADS PowerPCB" [1-191] -->
+<h2><a name="forward_annotation_of_geda_schematic_changes_to_pads_powerpcb_layout" id="forward_annotation_of_geda_schematic_changes_to_pads_powerpcb_layout">Forward Annotation of gEDA Schematic Changes to PADS PowerPCB Layout</a></h2>
+<div class="level2">
+
+</div>
+<!-- SECTION "Forward Annotation of gEDA Schematic Changes to PADS PowerPCB Layout" [192-272] -->
+<h2><a name="overview" id="overview">Overview</a></h2>
+<div class="level2">
+
+<p>
+Forward annotation is the process of updating a layout to reflect changes made in the schematic. This process is used when, for example, a new component is added to a schematic and needs to be included in the layout. This section describes how to forward annotate changes in a gEDA schematic to a PADS PowerPCB layout.<br/>
+ PADS implements forward annotation through the use of an ECO (Engineering Change Order) file. The ECO file describes the differences between a current design and the desired design. PADS generates the ECO file by performing a netlist comparison between a new netlist file and the netlist contained in the current layout.
+</p>
+
+</div>
+<!-- SECTION "Overview" [273-936] -->
+<h2><a name="detailed_forward_annotation_procedure" id="detailed_forward_annotation_procedure">Detailed Forward Annotation Procedure</a></h2>
+<div class="level2">
+
+<p>
+This procedure assumes you have a board layout open in PADS and that you have made your schematic changes in gschem. For the purposes of illustration, assume your schematic is split into two pages in the files pg1.sch and pg2.sch.
+</p>
+<ul>
+<li class="level1"><div class="li"> Create an updated PADS netlist by running:<br/>
+ <strong><code>gnetlist -g pads -o mynet.asc pg1.sch pg2.sch</code></strong><br/>
+ This will create the netlist file <strong><code>mynet.asc</code></strong>.</div>
+</li>
+<li class="level1"><div class="li"> Make a backup copy of your PADS layout in case things fail in a destructive way.</div>
+</li>
+<li class="level1"><div class="li"> From within PADS, choose the â??Tools → Compare Netlistâ?? menu item and choose the following options in the form:</div>
+</li>
+</ul>
+<table class="inline">
+ <tr>
+ <td>original design to compare</td><td>use current PCB design</td>
+ </tr>
+ <tr>
+ <td>new design with changes</td><td>mynet.asc</td>
+ </tr>
+ <tr>
+ <td>â??</td><td>generate differences report</td>
+ </tr>
+ <tr>
+ <td>â??</td><td>generate eco file</td>
+ </tr>
+ <tr>
+
+ </tr>
+ <tr>
+ <td colspan="2">comparison options</td>
+ </tr>
+ <tr>
+ <td>â??</td><td>compare only ECO registered parts</td>
+ </tr>
+ <tr>
+ <td colspan="2"> </td>
+ </tr>
+ <tr>
+ <td colspan="2">attribute comparison level</td>
+ </tr>
+ <tr>
+ <td>â??</td><td>ignore all attributes</td>
+ </tr>
+</table>
+
+<p>
+ Click the OK button to create the ECO file.
+</p>
+<ul>
+<li class="level1"><div class="li"> Examine the ECO file to make sure it looks ok (the ECO file is a text file which can be viewed with any text editor).</div>
+</li>
+<li class="level1"><div class="li"> From within PADS, choose the â??File → Import…â?? menu item. Locate and choose the ECO file created previously.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Detailed Forward Annotation Procedure" [937-2135] -->
+<h2><a name="back_annotation_of_pads_powerpcb_layout_changes_to_geda_schematic" id="back_annotation_of_pads_powerpcb_layout_changes_to_geda_schematic">Back Annotation of PADS PowerPCB Layout Changes to gEDA Schematic</a></h2>
+<div class="level2">
+
+<p>
+Backannotation is the process of updating schematics to reflect changes made in the layout. This process is used, for example, when the reference designators have been renumbered on the layout, when pins have been swapped (e.g., on an AND gate), or slots have been swapped (e.g., on a multi-gate package). This section describes how to backannotate changes in a PADS PowerPCB layout to a gEDA schematic. The PADS PowerPCB tool supports three types of schematic backannotation:
+</p>
+<ol>
+<li class="level1"><div class="li"> Reference designator changes. This is often times used at the end of a layout to give components which are geographically close a set of reference designators which are numerically close.</div>
+</li>
+<li class="level1"><div class="li"> Slot swapping. This is commonly found in digital designs where there may be multiple identical gates in a single package. For example, you may wish to swap which slot is used in a hex inverter.</div>
+</li>
+<li class="level1"><div class="li"> Pin swapping. During layout, the designer may wish to swap equivalent pins on a chip. For example, the two inputs on a NAND gate.</div>
+</li>
+</ol>
+
+<p>
+ Currently only reference designator changes are automatically processed by the PADS to gschem backannotation tool. The slot and pin swapping changes are provided in a report which the schematic designer must use to manually correct the schematic.
+</p>
+
+</div>
+<!-- SECTION "Back Annotation of PADS PowerPCB Layout Changes to gEDA Schematic" [2136-3463] -->
+<h3><a name="detailed_backannotation_procedure" id="detailed_backannotation_procedure">Detailed Backannotation Procedure</a></h3>
+<div class="level3">
+
+<p>
+This procedure assumes you have a board layout open in PADS. For the purposes of illustration, assume your schematic is split into two pages in the files pg1.sch and pg2.sch.
+</p>
+<ul>
+<li class="level1"><div class="li"> Create an up to date PADS netlist by running:<br/>
+ <strong><code>gnetlist -g pads -o mynet.asc pg1.sch pg2.sch</code></strong><br/>
+ This will create the netlist file <strong><code>mynet.asc</code></strong>.</div>
+</li>
+<li class="level1"><div class="li"> From within PADS, choose the â??Tools → Compare Netlistâ?? menu item and choose the following options in the form:</div>
+</li>
+</ul>
+<table class="inline">
+ <tr>
+ <td>original design to compare</td><td>mynet.asc</td>
+ </tr>
+ <tr>
+ <td>new design with changes</td><td>use current PCB design</td>
+ </tr>
+ <tr>
+ <td>â??</td><td>generate differences report</td>
+ </tr>
+ <tr>
+ <td>â??</td><td>generate eco file</td>
+ </tr>
+ <tr>
+ <td colspan="2"> </td>
+ </tr>
+ <tr>
+ <td colspan="2">comparison options</td>
+ </tr>
+ <tr>
+ <td>â??</td><td>compare only ECO registered parts</td>
+ </tr>
+ <tr>
+ <td colspan="2"> </td>
+ </tr>
+ <tr>
+ <td colspan="2">attribute comparison level</td>
+ </tr>
+ <tr>
+ <td>â??</td><td>ignore all attributes</td>
+ </tr>
+</table>
+
+<p>
+ Click the OK button to create the ECO file.
+</p>
+<ul>
+<li class="level1"><div class="li"> Examine the ECO file to make sure it looks ok (the ECO file is a text file which can be viewed with any text editor).</div>
+</li>
+<li class="level1"><div class="li"> Make a backup copy of your gEDA schematic files in case things fail in a destructive way.</div>
+</li>
+<li class="level1"><div class="li"> Run:<br/>
+ <strong><code>pads_backannotate file.eco pg1.sch pg2.sch | tee backanno.log</code></strong><br/>
+ where <strong><code>file.eco</code></strong> is the name of the ECO file created previously and <strong><code>pg1.sch</code></strong> and <strong><code>pg2.sch</code></strong> are all of your schematic pages. This will apply the reference designator change portion of the ECO file and also generate a list of pin and slot swapping which must be performed by hand. The file <strong><code>backanno.log</code></strong> will contain a log of the session that can be refered to when performing the pin and slot swapping.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Detailed Backannotation Procedure" [3464-] --></body>
+</html>
diff --git a/docs/wiki/geda-fc1.html b/docs/wiki/geda-fc1.html
new file mode 100644
index 0000000..6890814
--- /dev/null
+++ b/docs/wiki/geda-fc1.html
@@ -0,0 +1,52 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#installer_2005080x_on_fedora_core_1_install_notes" class="toc">Installer 2005080X on Fedora Core 1 install notes</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#prerequisites" class="toc">Prerequisites:</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#problems" class="toc">Problems:</a></span></div></li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="installer_2005080x_on_fedora_core_1_install_notes" id="installer_2005080x_on_fedora_core_1_install_notes">Installer 2005080X on Fedora Core 1 install notes</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "Installer 2005080X on Fedora Core 1 install notes" [1-64] -->
+<h2><a name="prerequisites" id="prerequisites">Prerequisites:</a></h2>
+<div class="level2">
+
+<p>
+When you install FC1, make sure you install the â??workstationâ?? version, and not the â??desktopâ?? version. (You are presented with this choice when you first install the distribution off of the distribution media.) The â??workstationâ?? version includes important header files and other tools which are necessary to build many components of the gEDA Suite using the installer.
+</p>
+
+</div>
+<!-- SECTION "Prerequisites:" [65-472] -->
+<h2><a name="problems" id="problems">Problems:</a></h2>
+<div class="level2">
+
+<p>
+The installer has been thoroughly tested on this platform. No problems are known, and none have been reported.
+</p>
+
+</div>
+<!-- SECTION "Problems:" [473-] --></body>
+</html>
diff --git a/docs/wiki/geda-fc2.html b/docs/wiki/geda-fc2.html
new file mode 100644
index 0000000..f3893d4
--- /dev/null
+++ b/docs/wiki/geda-fc2.html
@@ -0,0 +1,52 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#installer_2005080x_on_fedora_core_2_install_notes" class="toc">Installer 2005080X on Fedora Core 2 install notes</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#prerequisites" class="toc">Prerequisites:</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#problems" class="toc">Problems:</a></span></div></li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="installer_2005080x_on_fedora_core_2_install_notes" id="installer_2005080x_on_fedora_core_2_install_notes">Installer 2005080X on Fedora Core 2 install notes</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "Installer 2005080X on Fedora Core 2 install notes" [1-64] -->
+<h2><a name="prerequisites" id="prerequisites">Prerequisites:</a></h2>
+<div class="level2">
+
+<p>
+When you install FC2, make sure you install the â??workstationâ?? version, and not the â??desktopâ?? version. (You are presented with this choice when you first install the distribution off of the distribution media.) The â??workstationâ?? version includes important header files and other tools which are necessary to build many components of the gEDA Suite using the installer.
+</p>
+
+</div>
+<!-- SECTION "Prerequisites:" [65-472] -->
+<h2><a name="problems" id="problems">Problems:</a></h2>
+<div class="level2">
+
+<p>
+The installer has been thoroughly tested on this platform. No problems are known, and none have been reported.
+</p>
+
+</div>
+<!-- SECTION "Problems:" [473-] --></body>
+</html>
diff --git a/docs/wiki/geda-fc3.html b/docs/wiki/geda-fc3.html
new file mode 100644
index 0000000..0ca4a9e
--- /dev/null
+++ b/docs/wiki/geda-fc3.html
@@ -0,0 +1,52 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#installer_2005080x_on_fedora_core_3_install_notes" class="toc">Installer 2005080X on Fedora Core 3 install notes</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#prerequisites" class="toc">Prerequisites:</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#problems" class="toc">Problems:</a></span></div></li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="installer_2005080x_on_fedora_core_3_install_notes" id="installer_2005080x_on_fedora_core_3_install_notes">Installer 2005080X on Fedora Core 3 install notes</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "Installer 2005080X on Fedora Core 3 install notes" [1-64] -->
+<h2><a name="prerequisites" id="prerequisites">Prerequisites:</a></h2>
+<div class="level2">
+
+<p>
+When you install FC3, make sure you install the â??workstationâ?? version, and not the â??desktopâ?? version. (You are presented with this choice when you first install the distribution off of the distribution media.) The â??workstationâ?? version includes important header files and other tools which are necessary to build many components of the gEDA Suite using the installer.
+</p>
+
+</div>
+<!-- SECTION "Prerequisites:" [65-472] -->
+<h2><a name="problems" id="problems">Problems:</a></h2>
+<div class="level2">
+
+<p>
+No problems are known, and none have been reported.
+</p>
+
+</div>
+<!-- SECTION "Problems:" [473-] --></body>
+</html>
diff --git a/docs/wiki/geda-fc4.html b/docs/wiki/geda-fc4.html
new file mode 100644
index 0000000..a57f8c6
--- /dev/null
+++ b/docs/wiki/geda-fc4.html
@@ -0,0 +1,144 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#installer_20060825_on_fedora_core_4_install_notes" class="toc">Installer 20060825 on Fedora Core 4 install notes</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#installer_2005080x_on_fedora_core_4_install_notes" class="toc">Installer 2005080X on Fedora Core 4 install notes</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#prerequisites" class="toc">Prerequisites:</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#problems" class="toc">Problems:</a></span></div></li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="installer_20060825_on_fedora_core_4_install_notes" id="installer_20060825_on_fedora_core_4_install_notes">Installer 20060825 on Fedora Core 4 install notes</a></h1>
+<div class="level1">
+
+<p>
+The latest CD installer will work fine on Fedora Core 4. All gEDA Suite programs now compile happily with gcc-4.X. When you build your FC4 system, make sure you select â??devlopement worstationâ?? as your system type, and include as many -devel packages into the build as you can. The following packages are particularly important:
+</p>
+<ul>
+<li class="level1"><div class="li"> gtk-devel</div>
+</li>
+<li class="level1"><div class="li"> gnome-devel</div>
+</li>
+<li class="level1"><div class="li"> guile-devel</div>
+</li>
+<li class="level1"><div class="li"> tcl-devel</div>
+</li>
+<li class="level1"><div class="li"> tk-devel</div>
+</li>
+</ul>
+
+<p>
+If you are missing most of these -devel packages, the installer will do the right thing, but itâ??s better to pre-install them so the installer doesnâ??t have to become root to do it.
+</p>
+
+</div>
+<!-- SECTION "Installer 20060825 on Fedora Core 4 install notes" [1-650] -->
+<h1><a name="installer_2005080x_on_fedora_core_4_install_notes" id="installer_2005080x_on_fedora_core_4_install_notes">Installer 2005080X on Fedora Core 4 install notes</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "Installer 2005080X on Fedora Core 4 install notes" [651-714] -->
+<h2><a name="prerequisites" id="prerequisites">Prerequisites:</a></h2>
+<div class="level2">
+
+<p>
+When you install FC4, make sure you install the â??workstationâ?? version, and not the â??desktopâ?? version. (You are presented with this choice when you first install the distribution off of the distribution media.) The â??workstationâ?? version includes important header files and other tools which are necessary to build many components of the gEDA Suite using the installer.
+</p>
+
+<p>
+Also, the following additional RPMs are required:
+</p>
+<ul>
+<li class="level1"><div class="li"> guile-1.6.7-devel</div>
+</li>
+<li class="level1"><div class="li"> gettext-XX-devel.</div>
+</li>
+<li class="level1"><div class="li"> compat-gcc-3.2.3-47.fc4.i386.rpm</div>
+</li>
+<li class="level1"><div class="li"> compat-gcc-32-c++-3.2.3-47.fc4.i386.rpm</div>
+</li>
+<li class="level1"><div class="li"> compat-libstdc++-33-0:3.2.3-47.fc4.i386.rpm (installed automatically when g++ is installed by rpm)</div>
+</li>
+</ul>
+
+<p>
+ These RPMs are not automatically installed by RedHatâ??s installer; you need to install them manually. The devel packages live on the 4th FC4 disk. The gcc compatability compiler lives on the 3rd FC4 disk. Install all these packages before trying to build the gEDA Suite.
+</p>
+
+<p>
+Before installing the gEDA Suite on an FC4 system, you should set the CC environment variable to point to gcc32. This is explained further in the â??Problemsâ?? section below.
+</p>
+
+</div>
+<!-- SECTION "Prerequisites:" [715-1851] -->
+<h2><a name="problems" id="problems">Problems:</a></h2>
+<div class="level2">
+
+<p>
+The 200508XX installer will fail on FC4 systems. There seem to be several independent problems:
+</p>
+<ol>
+<li class="level1"><div class="li"> The installer doesnâ??t find guile, even though it comes pre-installed on the platform.<br/>
+ The problem here is that the installer tries to find guile by issuing the â??guile-configâ?? command. This command lives in the guile-devel RPM which is not installed by default (see above). To fix the problem, install the guile-devel RPM which lives on the FC4 install CD no. 4.</div>
+</li>
+<li class="level1"><div class="li"> The installer doesnâ??t find gettext, even though it comes pre-installed on the platform. Gettext is used by gschem, so this error is raised during the configure stage for gschem.<br/>
+ Again, the gettext header files live in the gettext-devel RPM which is not installed by default (see above). To fix this problem, install the gettext-devel RPM which lives on the FC4 install CD no. 4.</div>
+</li>
+<li class="level1"><div class="li"> Many different applications (e.g. GTKWave, GSpiceUI, Icarus Verilog) fail during compilation. The error message typically says something about a problem involving a â??typeâ??.</div>
+</li>
+</ol>
+
+<p>
+ This problem obtains because FC4 incorporates the new gcc-4.0 compiler. Gcc-4.0 incorporates much stricter type checking than the older gcc versions. This has caused many open-source applications to fail to compile.
+</p>
+
+<p>
+Fortunately, RedHat still provides the older version of gcc on the FC4 disks. This version of gcc is called â??gcc32â??. It is not installed as part of the normal installation, so you must install it yourself. The RPM lives on the FC4 install media, disk 3, and is called â??compat-gcc-32-3.2.3-47.fc4.i386.rpmâ??. Allow rpm to install any dependencies it finds.
+</p>
+
+<p>
+A similar situation holds for the C++ compiler g++. You need to install the older version too; get it on the FC4 disk 4. It is called â??compat-gcc-32-c++-3.2.3-47.fc4.i386.rpmâ??. Also install any dependencies found by rpm when you install these pacakges.
+</p>
+
+<p>
+Once they are installed, set the gcc environment variables as follows:
+</p>
+
+<p>
+for bash:
+</p>
+<pre class="code">export CC=gcc32
+export CXX=g++32</pre>
+
+<p>
+for csh:
+</p>
+<pre class="code">setenv CC gcc32
+setenv CXX g++32</pre>
+
+<p>
+and then run the installer. Make sure you run the installer from the same window as where you set the CC environment variable!
+</p>
+
+</div>
+<!-- SECTION "Problems:" [1852-] --></body>
+</html>
diff --git a/docs/wiki/geda-fedora_rpm_installation.html b/docs/wiki/geda-fedora_rpm_installation.html
new file mode 100644
index 0000000..406a5b8
--- /dev/null
+++ b/docs/wiki/geda-fedora_rpm_installation.html
@@ -0,0 +1,305 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#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="#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="#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>
+</div>
+
+
+
+<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" [1-54] -->
+<h2><a name="geda_gaf_for_fedora" id="geda_gaf_for_fedora">gEDA/gaf for fedora</a></h2>
+<div class="level2">
+
+<p>
+ 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>
+ 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 "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\* 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>
+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 "The easiest way" [871-1851] -->
+<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 "Compile it yourself" [1852-2506] -->
+<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>
+
+<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="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 "Rebuild your own rpms" [2507-] --></body>
+</html>
diff --git a/docs/wiki/geda-file_format_spec.html b/docs/wiki/geda-file_format_spec.html
new file mode 100644
index 0000000..779c5cd
--- /dev/null
+++ b/docs/wiki/geda-file_format_spec.html
@@ -0,0 +1,1563 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#geda_gaf_file_format_document" class="toc">gEDA/gaf File Format Document</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#overview" class="toc">Overview</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#coordinate_space" class="toc">Coordinate Space</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#filenames" class="toc">Filenames</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#object_types" class="toc">Object types</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#version" class="toc">version</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#line" class="toc">line</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#picture" class="toc">picture</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#box" class="toc">box</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#circle" class="toc">circle</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#arc" class="toc">arc</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#text" class="toc">text</a></span></div></li>
+<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="#bus" class="toc">bus</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#pin" class="toc">pin</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#component" class="toc">component</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#path" class="toc">path</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#font" class="toc">font</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#colors" class="toc">Colors</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#attributes" class="toc">Attributes</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#embedded_components" class="toc">Embedded Components</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#path_data" class="toc">Path data</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#document_revision_history" class="toc">Document Revision History</a></span></div></li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="geda_gaf_file_format_document" id="geda_gaf_file_format_document">gEDA/gaf File Format Document</a></h1>
+<div class="level1">
+
+<p>
+by: Ales V. Hvezda, ahvezda@xxxxxxxxxxxxx
+</p>
+
+<p>
+This document is released under <a href="http://www.gnu.org/copyleft/fdl.html"; class="urlextern" title="http://www.gnu.org/copyleft/fdl.html"; rel="nofollow">GFDL</a>
+</p>
+
+<p>
+December 31st, 2003
+</p>
+
+</div>
+<!-- SECTION "gEDA/gaf File Format Document" [1-187] -->
+<h2><a name="overview" id="overview">Overview</a></h2>
+<div class="level2">
+
+<p>
+This file is the official documentation for the file formats in gEDA/gaf (gschem And Friends). The primary file format used in gEDA/gaf is the schematic/symbol format. Files which end with .sch or .sym are schematics or symbol files. Until there is another file type in gEDA/gaf, then this document will only cover the symbol/schematic file format.<br/>
+ This file format document is current as of gEDA/gaf version 20040111. This document covers file format version 1 and 2.<br/>
+ Note, this file format and any other file formats associated with gEDA are placed under the General Public License (<acronym title="GNU General Public License">GPL</acronym>) version 2.0. The gEDA/gaf symbol and schematic file format is Copyright (C) 1998-2004 Ales Hvezda.
+</p>
+
+</div>
+<!-- SECTION "Overview" [188-902] -->
+<h2><a name="coordinate_space" id="coordinate_space">Coordinate Space</a></h2>
+<div class="level2">
+
+<p>
+All coordinates are in mils (1/1000 or an inch). This is an arbitrary decision. Remember in there is no concept of physical lengths/dimensions in schematics and symbols (for schematic capture only).<br/>
+
+</p>
+<ul>
+<li class="level1"><div class="li"> Origin is in lower left hand corner.</div>
+</li>
+<li class="level1"><div class="li"> The size of the coordinate space is unlimited, but it is recommended that all objects stay within (120.0, 90.0) (x, y inches).</div>
+</li>
+<li class="level1"><div class="li"> It is generally advisable to have positive x and y coordinates, however, negative coordinates work too, but not recommended.</div>
+</li>
+</ul>
+
+<p>
+ The following figure shows how the coordinate space is setup:
+</p>
+<table class="inline">
+ <tr>
+ <td><a href="media/geda/coordinatespace.jpg" class="media" target="_blank" title="geda:coordinatespace.jpg"><img src="media/geda/coordinatespace.jpg" class="mediaright" title=":geda:coordinatespace.jpg " alt=":geda:coordinatespace.jpg " /></a></td>
+ </tr>
+</table>
+
+<p>
+ X axis increases going to the right. Y axis increase going up. Coordinate system is landscape and corresponds to a sheet of paper turned on its side.
+</p>
+
+</div>
+<!-- SECTION "Coordinate Space" [903-1709] -->
+<h2><a name="filenames" id="filenames">Filenames</a></h2>
+<div class="level2">
+
+<p>
+Symbols end in .sym. The only symbol filename convention that is used in gEDA/gaf is that if there are multiple instances of a symbol with the same name (like a 7400), then a -1, -2, -3, … -N suffix is added to the end of the filename. Example: 7400-1.sym, 7400-2.sym, 7400-3.sym…<br/>
+ Schematics end in .sch. There used to be a schematic filename convention (adding a -1 .. -N to the end of the basename), but this convention is now obsolete. Schematic filenames can be anything that makes sense to the creator.
+</p>
+
+</div>
+<!-- SECTION "Filenames" [1710-2246] -->
+<h2><a name="object_types" id="object_types">Object types</a></h2>
+<div class="level2">
+
+<p>
+A schematic/symbol file for gEDA/gaf consists of:
+</p>
+<ul>
+<li class="level1"><div class="li"> A version (v) as the first item in the file. This is required.</div>
+</li>
+<li class="level1"><div class="li"> Any number of objects and the correct data. Objects are specified by an â??object typeâ??</div>
+</li>
+<li class="level1"><div class="li"> Most objects are a single line, however text objects are two lines long.</div>
+</li>
+<li class="level1"><div class="li"> No blank lines at the end of the file (these are ignored by the tools)</div>
+</li>
+<li class="level1"><div class="li"> For all enumerated types in the gEDA/gaf file formats, the field takes on the numeric value.</div>
+</li>
+</ul>
+
+<p>
+ The â??object typeâ?? id is a single letter and this id must start in the first column. The object type id is case sensitive.<br/>
+ The schematic and symbol files share the same file layout. A symbol is nothing more than a collection of primitive objects (lines, boxes, circles, arcs, text, and pins). A schematic is a collection of symbols (components), nets, and buses.<br/>
+ The following sections describe the specifics of each recognized object type. Each section has the name of the object, which file type (sch/sym) the object can appear in, the format of the data, a description of each individual field, details and caveats of the fields, and finally an example with description.<br/>
+ For information on the color index (which is used in practically all objects), see the Color section.
+</p>
+
+</div>
+<!-- SECTION "Object types" [2247-3517] -->
+<h3><a name="version" id="version">version</a></h3>
+<div class="level3">
+
+<p>
+Valid in: Schematic and Symbol files<br/>
+ <strong><code>type version fileformat_version</code></strong>
+</p>
+<table class="inline">
+ <tr>
+ <th>Field</th><th>Type/unit</th><th>Description</th>
+ </tr>
+ <tr>
+ <td>type</td><td>char</td><td>v</td>
+ </tr>
+ <tr>
+ <td>version</td><td>int</td><td>version of gEDA/gaf that wrote this file</td>
+ </tr>
+ <tr>
+ <td>fileformat_version</td><td>int</td><td>gEDA/gaf file format version number</td>
+ </tr>
+</table>
+<ul>
+<li class="level1"><div class="li"> The type is a lower case â??vâ?? (as in Victor).</div>
+</li>
+<li class="level1"><div class="li"> This object must be in every file used or created by the gEDA/gaf tools.</div>
+</li>
+<li class="level1"><div class="li"> The format of the first version field is YYYYMMDD.</div>
+</li>
+<li class="level1"><div class="li"> The version number is not an arbitrary timestamp. Do not make up a version number and expect the tools to behave properly.</div>
+</li>
+<li class="level1"><div class="li"> The â??version of gEDA/gaf that wrote this fileâ?? was used in all versions of gEDA/gaf up to 20030921 as the file formats version. This field should no longer be used to determine the file format. It is used for information purposes only now.</div>
+</li>
+<li class="level1"><div class="li"> Starting at and after gEDA/gaf version 20031004, the fileformat version field is used to determine the file format version. All file format code should key off of this field.</div>
+</li>
+<li class="level1"><div class="li"> fileformat version increases when the file format changes.</div>
+</li>
+<li class="level1"><div class="li"> The starting point for fileformat version was 1. The current fileformat is 2.</div>
+</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"> 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, 20070818, 20071229, 20080110</div>
+</li>
+<li class="level1"><div class="li"> Stable versions include: 20070526, 20070626, 20070902, 20071231, 20080127</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>
+<li class="level1"><div class="li"> Keep in mind that each of the above listed versions might have had file format variations. This document only covers the last versionâ??s file format.</div>
+</li>
+</ul>
+
+<p>
+ Example:<br/>
+
+</p>
+<pre class="code">v 20040111 1</pre>
+
+</div>
+<!-- SECTION "version" [3518-5475] -->
+<h3><a name="line" id="line">line</a></h3>
+<div class="level3">
+
+<p>
+Valid in: Schematic and Symbol files<br/>
+ <strong><code>type x1 y1 x2 y2 color width capstyle dashstyle dashlength dashspace</code></strong>
+</p>
+<table class="inline">
+ <tr>
+ <th>Field</th><th>Type/unit</th><th>Description</th>
+ </tr>
+ <tr>
+ <td>type</td><td>char</td><td>L</td>
+ </tr>
+ <tr>
+ <td>x1</td><td>int/mils</td><td>First X coordinate</td>
+ </tr>
+ <tr>
+ <td>y1</td><td>int/mils</td><td>First Y coordinate</td>
+ </tr>
+ <tr>
+ <td>x2</td><td>int/mils</td><td>Second X coordinate</td>
+ </tr>
+ <tr>
+ <td>y2</td><td>int/mils</td><td>Second Y coordinate</td>
+ </tr>
+ <tr>
+ <td>color</td><td>int</td><td>Color index</td>
+ </tr>
+ <tr>
+ <td>width</td><td>int/mils</td><td>Width of line</td>
+ </tr>
+ <tr>
+ <td>capstyle</td><td>int</td><td>Line cap style</td>
+ </tr>
+ <tr>
+ <td>dashstyle</td><td>int</td><td>Type of dash style</td>
+ </tr>
+ <tr>
+ <td>dashlength</td><td>int</td><td>Length of dash</td>
+ </tr>
+ <tr>
+ <td>dashspace</td><td>int</td><td>Space inbetween dashes</td>
+ </tr>
+</table>
+<ul>
+<li class="level1"><div class="li"> The capstyle is an enumerated type:</div>
+<ul>
+<li class="level2"><div class="li"> END NONE = 0</div>
+</li>
+<li class="level2"><div class="li"> END SQUARE = 1</div>
+</li>
+<li class="level2"><div class="li"> END ROUND = 2</div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> The dashstyle is an enumerated type:</div>
+<ul>
+<li class="level2"><div class="li"> TYPE SOLID = 0</div>
+</li>
+<li class="level2"><div class="li"> TYPE DOTTED = 1</div>
+</li>
+<li class="level2"><div class="li"> TYPE DASHED = 2</div>
+</li>
+<li class="level2"><div class="li"> TYPE CENTER = 3</div>
+</li>
+<li class="level2"><div class="li"> TYPE PHANTOM = 4</div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> The dashlength parameter is not used for TYPE SOLID and TYPE DOTTED. This parameter should take on a value of -1 in these cases.</div>
+</li>
+<li class="level1"><div class="li"> The dashspace paramater is not used for TYPE SOLID. This parameter should take on a value of -1 in these case.</div>
+</li>
+</ul>
+
+<p>
+ Example:<br/>
+
+</p>
+<pre class="code">L 23000 69000 28000 69000 3 40 0 1 -1 75</pre>
+
+<p>
+A line segment from (23000, 69000) to (28000, 69000) with color index 3, 40 mils thick, no cap, dotted line style, and with a spacing of 75 mils in between each dot.
+</p>
+
+</div>
+<!-- SECTION "line" [5476-6710] -->
+<h3><a name="picture" id="picture">picture</a></h3>
+<div class="level3">
+
+<p>
+Valid in: Schematic and Symbol files<br/>
+ <strong><code>type x1 y1 width height angle ratio mirrored embedded<br/>
+
+filename<br/>
+
+[encoded picture data<br/>
+
+encoded picture end]</code></strong>
+</p>
+<table class="inline">
+ <tr>
+ <th>Field</th><th>Type/unit</th><th>Description</th>
+ </tr>
+ <tr>
+ <td>type</td><td>char</td><td>G</td>
+ </tr>
+ <tr>
+ <td>x</td><td>int/mils</td><td>Lower left X coordinate</td>
+ </tr>
+ <tr>
+ <td>y</td><td>int/mils</td><td>Lower left Y coordinate</td>
+ </tr>
+ <tr>
+ <td>width</td><td>int/mils</td><td>Width of the picture</td>
+ </tr>
+ <tr>
+ <td>height</td><td>int/mils</td><td>Height of the picture</td>
+ </tr>
+ <tr>
+ <td>angle</td><td>int/degrees</td><td>Angle of the picture</td>
+ </tr>
+ <tr>
+ <td>mirrored</td><td>char</td><td>Mirrored or normal picture</td>
+ </tr>
+ <tr>
+ <td>embedded</td><td>char</td><td>Embedded or link to the picture file</td>
+ </tr>
+ <tr>
+ <td>filename</td><td>string</td><td>path and filename of a not embedded picture</td>
+ </tr>
+ <tr>
+ <td>encoded picture data</td><td>string</td><td>Serialized picture encoded using base64</td>
+ </tr>
+ <tr>
+ <td>encoded picture end</td><td>string</td><td>A line containing only a dot character</td>
+ </tr>
+</table>
+<ul>
+<li class="level1"><div class="li"> This object is a picture object. The first line contains all the picture parameters, and the second line is the path and filename of the picture. The filename is not used if the picture is embedded.</div>
+</li>
+<li class="level1"><div class="li"> The angle of the picture can only take on one of the following values: 0, 90, 180, 270.</div>
+</li>
+<li class="level1"><div class="li"> The mirrored field is an enumerated type:</div>
+<ul>
+<li class="level2"><div class="li"> NOT MIRRORED = 0</div>
+</li>
+<li class="level2"><div class="li"> MIRRORED = 1</div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> The embedded field is an enumerated type:</div>
+<ul>
+<li class="level2"><div class="li"> NOT EMBEDDED = 0</div>
+</li>
+<li class="level2"><div class="li"> EMBEDDED = 1 (not yet supported)</div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> The encoded picture and encoded picture end fields are only in the file if the picture is embedded in the schematic:</div>
+<ul>
+<li class="level2"><div class="li"> encoded picture data: This is a multiple line field. The picture is serialized and then encoded using base64. This way the encoded data uses only printable characters. This field is the result of these two operations.</div>
+</li>
+<li class="level2"><div class="li"> encoded picture end : A line containing only a single dot '.' character marks the end of the encoded picture data.</div>
+</li>
+</ul>
+</li>
+</ul>
+
+<p>
+ Example:<br/>
+
+</p>
+<pre class="code">G 16900 35800 1400 2175 0 6.435331e-01 0 0
+../bitmaps/logo.jpg</pre>
+
+<p>
+A picture object with the lower left corner at (16900, 35800). The width of the image is 1400 mils, and its height is 2175 mils (i.e.: the ratio is 0.6353). The picture rotation is 0 degrees and the picture is not mirrored, neither embedded.<br/>
+ The picture path and filename is showed in the second line.<br/>
+ Example:<br/>
+
+</p>
+<pre class="code">G 16900 35800 1400 2175 0 6.435331e-01 0 1
+../bitmaps/logo.jpg
+AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
+BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB
+.</pre>
+
+<p>
+A picture object with the lower left corner at (16900, 35800). The width of the image is 1400 mils, and its height is 2175 mils (i.e.: the ratio is 0.6353).<br/>
+ The picture rotation is 0 degrees, it is not mirrored, and it is embedded.<br/>
+ The picture path and filename is showed in the second line. Since this is an embedded picture, the filename and path are not used.<br/>
+ The encoded picture data is only an example (it is not real data). The last line containing a single dot '.' character marks the end of the encoded picture data.
+</p>
+
+</div>
+<!-- SECTION "picture" [6711-9504] -->
+<h3><a name="box" id="box">box</a></h3>
+<div class="level3">
+
+<p>
+Valid in: Schematic and Symbol files<br/>
+ <strong><code>type x y width height color width capstyle dashtype dashlength dashspace
+filltype fillwidth angle1 pitch1 angle2 pitch2</code></strong>
+</p>
+<table class="inline">
+ <tr>
+ <th>Field</th><th>Type/unit</th><th>Description</th>
+ </tr>
+ <tr>
+ <td>type</td><td>char</td><td>B</td>
+ </tr>
+ <tr>
+ <td>x</td><td>int/mils</td><td>Lower left hand X coordinate</td>
+ </tr>
+ <tr>
+ <td>y</td><td>int/mils</td><td>Lower left hand Y coordinate</td>
+ </tr>
+ <tr>
+ <td>width</td><td>int/mils</td><td>Width of the box (x direction)</td>
+ </tr>
+ <tr>
+ <td>height</td><td>int/mils</td><td>Height of the box (y direction)</td>
+ </tr>
+ <tr>
+ <td>color</td><td>int</td><td>Color index</td>
+ </tr>
+ <tr>
+ <td>width</td><td>int/mils</td><td>Width of lines</td>
+ </tr>
+ <tr>
+ <td>capstyle</td><td>int/mils</td><td>Line cap style</td>
+ </tr>
+ <tr>
+ <td>dashstyle</td><td>int</td><td>Type of dash style</td>
+ </tr>
+ <tr>
+ <td>dashlength</td><td>int/mils</td><td>Length of dash</td>
+ </tr>
+ <tr>
+ <td>dashspace</td><td>int/mils</td><td>Space inbetween dashes</td>
+ </tr>
+ <tr>
+ <td>filltype</td><td>int</td><td>Type of fill</td>
+ </tr>
+ <tr>
+ <td>fillwidth</td><td>int/mils</td><td>Width of the fill lines</td>
+ </tr>
+ <tr>
+ <td>angle1</td><td>int/degrees</td><td>First angle of fill</td>
+ </tr>
+ <tr>
+ <td>pitch1</td><td>int/mils</td><td>First pitch/spacing of fill</td>
+ </tr>
+ <tr>
+ <td>angle2</td><td>int/degrees</td><td>Second angle of fill</td>
+ </tr>
+ <tr>
+ <td>pitch2</td><td>int/mils</td><td>Second pitch/spacing of fill</td>
+ </tr>
+</table>
+<ul>
+<li class="level1"><div class="li"> The capstyle is an enumerated type:</div>
+<ul>
+<li class="level2"><div class="li"> END NONE = 0</div>
+</li>
+<li class="level2"><div class="li"> END SQUARE = 1</div>
+</li>
+<li class="level2"><div class="li"> END ROUND = 2</div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> The dashstyle is an enumerated type:</div>
+<ul>
+<li class="level2"><div class="li"> TYPE SOLID = 0</div>
+</li>
+<li class="level2"><div class="li"> TYPE DOTTED = 1</div>
+</li>
+<li class="level2"><div class="li"> TYPE DASHED = 2</div>
+</li>
+<li class="level2"><div class="li"> TYPE CENTER = 3</div>
+</li>
+<li class="level2"><div class="li"> TYPE PHANTOM = 4</div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> The dashlength parameter is not used for TYPE SOLID and TYPE DOTTED. This parameter should take on a value of -1 in these cases.</div>
+</li>
+<li class="level1"><div class="li"> The dashspace paramater is not used for TYPE SOLID. This parameter should take on a value of -1 in these case.</div>
+</li>
+<li class="level1"><div class="li"> The filltype parameter is an enumerated type:</div>
+<ul>
+<li class="level2"><div class="li"> FILLING HOLLOW = 0</div>
+</li>
+<li class="level2"><div class="li"> FILLING FILL = 1</div>
+</li>
+<li class="level2"><div class="li"> FILLING MESH = 2</div>
+</li>
+<li class="level2"><div class="li"> FILLING HATCH = 3</div>
+</li>
+<li class="level2"><div class="li"> FILLING VOID = 4 unused</div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> If the filltype is 0 (FILLING HOLLOW), then all the fill parameters should take on a value of -1.</div>
+</li>
+<li class="level1"><div class="li"> The fill type FILLING FILL is a solid color fill.</div>
+</li>
+<li class="level1"><div class="li"> The two pairs of pitch and spacing control the fill or hatch if the fill type is FILLING MESH.</div>
+</li>
+<li class="level1"><div class="li"> Only the first pair of pitch and spacing are used if the fill type is FILLING HATCH.</div>
+</li>
+</ul>
+
+<p>
+ Example:<br/>
+
+</p>
+<pre class="code">B 33000 67300 2000 2000 3 60 0 2 75 50 0 -1 -1 -1 -1 -1</pre>
+
+<p>
+A box with the lower left hand corner at (33000, 67300) and a width and height of (2000, 2000), color index 3, line width of 60 mils, no cap, dashed line type, dash length of 75 mils, dash spacing of 50 mils, no fill, rest parameters unset.
+</p>
+
+</div>
+<!-- SECTION "box" [9505-11711] -->
+<h3><a name="circle" id="circle">circle</a></h3>
+<div class="level3">
+
+<p>
+Valid in: Schematic and Symbol files<br/>
+ <strong><code>type x y radius color width capstyle dashtype dashlength dashspace
+filltype fillwidth angle1 pitch1 angle2 pitch2</code></strong>
+</p>
+<table class="inline">
+ <tr>
+ <th>Field</th><th>Type/unit</th><th>Description</th>
+ </tr>
+ <tr>
+ <td>type</td><td>char</td><td>V</td>
+ </tr>
+ <tr>
+ <td>x</td><td>int/mils</td><td>Center X coordinate</td>
+ </tr>
+ <tr>
+ <td>y</td><td>int/mils</td><td>Center Y coordinate</td>
+ </tr>
+ <tr>
+ <td>radius</td><td>int/mils</td><td>Radius of the circle</td>
+ </tr>
+ <tr>
+ <td>color</td><td>int</td><td>Color index</td>
+ </tr>
+ <tr>
+ <td>width</td><td>int/mils</td><td>Width of circle line</td>
+ </tr>
+ <tr>
+ <td>capstyle</td><td>int/mils</td><td>0 unused</td>
+ </tr>
+ <tr>
+ <td>dashstyle</td><td>int</td><td>Type of dash style</td>
+ </tr>
+ <tr>
+ <td>dashlength</td><td>int/mils</td><td>Length of dash</td>
+ </tr>
+ <tr>
+ <td>dashspace</td><td>int/mils</td><td>Space inbetween dashes</td>
+ </tr>
+ <tr>
+ <td>filltype</td><td>int</td><td>Type of fill</td>
+ </tr>
+ <tr>
+ <td>fillwidth</td><td>int/mils</td><td>Width of the fill lines</td>
+ </tr>
+ <tr>
+ <td>angle1</td><td>int/degrees</td><td>First angle of fill</td>
+ </tr>
+ <tr>
+ <td>pitch1</td><td>int/mils</td><td>First pitch/spacing of fill</td>
+ </tr>
+ <tr>
+ <td>angle2</td><td>int/degrees</td><td>Second angle of fill</td>
+ </tr>
+ <tr>
+ <td>pitch2</td><td>int/mils</td><td>Second pitch/spacing of fill</td>
+ </tr>
+</table>
+<ul>
+<li class="level1"><div class="li"> The dashstyle is an enumerated type:</div>
+<ul>
+<li class="level2"><div class="li"> TYPE SOLID = 0</div>
+</li>
+<li class="level2"><div class="li"> TYPE DOTTED = 1</div>
+</li>
+<li class="level2"><div class="li"> TYPE DASHED = 2</div>
+</li>
+<li class="level2"><div class="li"> TYPE CENTER = 3</div>
+</li>
+<li class="level2"><div class="li"> TYPE PHANTOM = 4</div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> The dashlength parameter is not used for TYPE SOLID and TYPE DOTTED. This parameter should take on a value of -1 in these cases.</div>
+</li>
+<li class="level1"><div class="li"> The dashspace paramater is not used for TYPE SOLID. This parameter should take on a value of -1 in these case.</div>
+</li>
+<li class="level1"><div class="li"> The filltype parameter is an enumerated type:</div>
+<ul>
+<li class="level2"><div class="li"> FILLING HOLLOW = 0</div>
+</li>
+<li class="level2"><div class="li"> FILLING FILL = 1</div>
+</li>
+<li class="level2"><div class="li"> FILLING MESH = 2</div>
+</li>
+<li class="level2"><div class="li"> FILLING HATCH = 3</div>
+</li>
+<li class="level2"><div class="li"> FILLING VOID = 4 unused</div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> If the filltype is 0 (FILLING HOLLOW), then all the fill parameters should take on a value of -1.</div>
+</li>
+<li class="level1"><div class="li"> The fill type FILLING FILL is a solid color fill.</div>
+</li>
+<li class="level1"><div class="li"> The two pairs of pitch and spacing control the fill or hatch if the fill type is FILLING MESH.</div>
+</li>
+<li class="level1"><div class="li"> Only the first pair of pitch and spacing are used if the fill type is FILLING HATCH.</div>
+</li>
+</ul>
+
+<p>
+ Example:<br/>
+
+</p>
+<pre class="code">V 38000 67000 900 3 0 0 2 75 50 2 10 20 30 90 50</pre>
+
+<p>
+A circle with the center at (38000, 67000) and a radius of 900 mils, color index 3, line width of 0 mils (smallest size), no cap, dashed line type, dash length of 75 mils, dash spacing of 50 mils, mesh fill, 10 mils thick mesh lines, first mesh line: 20 degrees, with a spacing of 30 mils, second mesh line: 90 degrees, with a spacing of 50 mils.
+</p>
+
+</div>
+<!-- SECTION "circle" [11712-13837] -->
+<h3><a name="arc" id="arc">arc</a></h3>
+<div class="level3">
+
+<p>
+Valid in: Schematic and Symbol files<br/>
+ <strong><code>type x y radius startangle sweepangle color width capstyle dashtype
+dashlength dashspace</code></strong>
+</p>
+<table class="inline">
+ <tr>
+ <th>Field</th><th>Type/unit</th><th>Description</th>
+ </tr>
+ <tr>
+ <td>type</td><td>char</td><td>A</td>
+ </tr>
+ <tr>
+ <td>x</td><td>int/mils</td><td>Center X coordinate</td>
+ </tr>
+ <tr>
+ <td>y</td><td>int/mils</td><td>Center Y coordinate</td>
+ </tr>
+ <tr>
+ <td>radius</td><td>int/mils</td><td>Radius of the arc</td>
+ </tr>
+ <tr>
+ <td>startangle</td><td>int/degrees</td><td>Starting angle of the arc</td>
+ </tr>
+ <tr>
+ <td>sweepangle</td><td>int/degrees</td><td>Amount the arc sweeps</td>
+ </tr>
+ <tr>
+ <td>color</td><td>int</td><td>Color index</td>
+ </tr>
+ <tr>
+ <td>width</td><td>int/mils</td><td>Width of circle line</td>
+ </tr>
+ <tr>
+ <td>capstyle</td><td>int</td><td>Cap style</td>
+ </tr>
+ <tr>
+ <td>dashstyle</td><td>int</td><td>Type of dash style</td>
+ </tr>
+ <tr>
+ <td>dashlength</td><td>int/mils</td><td>Length of dash</td>
+ </tr>
+ <tr>
+ <td>dashspace</td><td>int/mils</td><td>Space inbetween dashes</td>
+ </tr>
+</table>
+<ul>
+<li class="level1"><div class="li"> The startangle can be negative, but not recommended.</div>
+</li>
+<li class="level1"><div class="li"> The sweepangle can be negative, but not recommended.</div>
+</li>
+<li class="level1"><div class="li"> The capstyle is an enumerated type:</div>
+<ul>
+<li class="level2"><div class="li"> END NONE = 0</div>
+</li>
+<li class="level2"><div class="li"> END SQUARE = 1</div>
+</li>
+<li class="level2"><div class="li"> END ROUND = 2</div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> The dashstyle is an enumerated type:</div>
+<ul>
+<li class="level2"><div class="li"> TYPE SOLID = 0</div>
+</li>
+<li class="level2"><div class="li"> TYPE DOTTED = 1</div>
+</li>
+<li class="level2"><div class="li"> TYPE DASHED = 2</div>
+</li>
+<li class="level2"><div class="li"> TYPE CENTER = 3</div>
+</li>
+<li class="level2"><div class="li"> TYPE PHANTOM = 4</div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> The dashlength parameter is not used for TYPE SOLID and TYPE DOTTED. This parameter should take on a value of -1 in these cases.</div>
+</li>
+<li class="level1"><div class="li"> The dashspace paramater is not used for TYPE SOLID. This parameter should take on a value of -1 in these case.</div>
+</li>
+</ul>
+
+<p>
+ Example:<br/>
+
+</p>
+<pre class="code">A 30600 75000 2000 0 45 3 0 0 3 75 50</pre>
+
+<p>
+ An arc with the center at (30600, 75000) and a radius of 2000 mils, a starting angle of 0, sweeping 45 degrees, color index 3, line width of 0 mils (smallest size), no cap, center line type, dash length of 75 mils, dash spacing of 50 mils.
+</p>
+
+</div>
+<!-- SECTION "arc" [13838-15354] -->
+<h3><a name="text" id="text">text</a></h3>
+<div class="level3">
+
+<p>
+Valid in: Schematic and Symbol files<br/>
+ <strong><code>type x y color size visibility show_name_value angle alignment num_lines<br/>
+
+string line 1<br/>
+
+string line 2<br/>
+
+string line 3<br/>
+
+…<br/>
+
+string line N</code></strong>
+</p>
+<table class="inline">
+ <tr>
+ <th>Field</th><th>Type/unit</th><th>Description</th>
+ </tr>
+ <tr>
+ <td>type</td><td>char</td><td>T</td>
+ </tr>
+ <tr>
+ <td>x</td><td>int/mils</td><td>First X coordinate</td>
+ </tr>
+ <tr>
+ <td>y</td><td>int/mils</td><td>First Y coordinate</td>
+ </tr>
+ <tr>
+ <td>color</td><td>int</td><td>Color index</td>
+ </tr>
+ <tr>
+ <td>size</td><td>int/points</td><td>Size of text</td>
+ </tr>
+ <tr>
+ <td>visibility</td><td>int</td><td>Visibility of text</td>
+ </tr>
+ <tr>
+ <td>show_name_value</td><td>int</td><td>Attribute visibility control</td>
+ </tr>
+ <tr>
+ <td>angle</td><td>int/degrees</td><td>Angle of the text</td>
+ </tr>
+ <tr>
+ <td>alignment</td><td>int</td><td>Alignment/origin of the text</td>
+ </tr>
+ <tr>
+ <td>num_lines</td><td>int</td><td>Number of lines of text (1 based)</td>
+ </tr>
+ <tr>
+ <td>string line 1 … N</td><td>string</td><td>The text strings, on a seperate line</td>
+ </tr>
+</table>
+<ul>
+<li class="level1"><div class="li"> This object is a multi line object. The first line contains all the text parameters and the subsequent lines are the text strings.</div>
+</li>
+<li class="level1"><div class="li"> There must be exactly num lines of text following the T … string.</div>
+</li>
+<li class="level1"><div class="li"> The maximum length of any single text string is 1024, however there is no limit to the number of text string lines.</div>
+</li>
+<li class="level1"><div class="li"> The minimum size is 2 points (1/72 of an inch).</div>
+</li>
+<li class="level1"><div class="li"> There is no maximum size.</div>
+</li>
+<li class="level1"><div class="li"> The coordinate pair is the origin of the text item.</div>
+</li>
+<li class="level1"><div class="li"> The visibility field is an enumerated type:</div>
+<ul>
+<li class="level2"><div class="li"> INVISIBLE = 0</div>
+</li>
+<li class="level2"><div class="li"> VISIBLE = 1</div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> The show_name_value is an enumerated type:</div>
+<ul>
+<li class="level2"><div class="li"> SHOW NAME VALUE = 0 (show both name and value of an attribute)</div>
+</li>
+<li class="level2"><div class="li"> SHOW VALUE = 1 (show only the value of an attribute)</div>
+</li>
+<li class="level2"><div class="li"> SHOW NAME = 2 (show only the name of an attribute)</div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> The show_name_value field is only valid if the string is an attribute (string has to be in the form: name=value to be considered an attribute).</div>
+</li>
+<li class="level1"><div class="li"> The angle of the text can only take on one of the following values: 0, 90, 180, 270. A value of 270 will always generate upright text.</div>
+</li>
+<li class="level1"><div class="li"> The alignment/origin field controls the relative location of the origin.</div>
+</li>
+<li class="level1"><div class="li"> The alignment field can take a value from 0 to 8. <br/>
+ The following diagram shows what the values for the alignment field mean:</div>
+</li>
+</ul>
+
+<p>
+ <a href="media/geda/fileformat_textgraphic.jpg" class="media" target="_blank" title="geda:fileformat_textgraphic.jpg"><img src="media/geda/fileformat_textgraphic.jpg" class="media" alt="" /></a>
+</p>
+<ul>
+<li class="level1"><div class="li"> The num_lines field always starts at 1.<br/>
+ The num_lines field was added starting with file format version 1. Past versions (0 or earlier) only supported single line text objects.</div>
+</li>
+<li class="level1"><div class="li"> The text strings of the string line(s) can have overbars if the text is embedded in two overbar markers <strong>â??\_â??</strong>. A single backslash needs to be written as <strong>â??\\â??</strong>.</div>
+</li>
+</ul>
+
+<p>
+Example1:<br/>
+
+</p>
+<pre class="code">T 16900 35800 3 10 1 0 0 0 1
+Text string!</pre>
+
+<p>
+A text object with the origin at (16900, 35800), color index 3, 10 points in size, visible, attribute ags not valid (not an attribute), origin at lower left, not rotated, string: Text string!
+</p>
+
+<p>
+Example2:<br/>
+
+</p>
+<pre class="code">T 16900 35800 3 10 1 0 0 0 5
+Text string line 1
+Text string line 2
+Text string line 3
+Text string line 4
+Text string line 5</pre>
+
+<p>
+This is a similar text object as the above example, however here there are five lines of text.
+</p>
+
+<p>
+Example3:<br/>
+
+</p>
+<pre class="code">T 10000 20000 3 10 1 1 8 90 1
+pinlabel=R/\_W\_</pre>
+
+<p>
+A text object with the origin at (10000, 20000), color index 3, 10 points in size, visible, only the value of the attribute is visible, text origin at upper right, the text is rotated by 90 degree, the string: â??R/Wâ?? has an overbar over the â??Wâ??.
+</p>
+
+</div>
+<!-- SECTION "text" [15355-18509] -->
+<h3><a name="net" id="net">net</a></h3>
+<div class="level3">
+
+<p>
+Valid in: Schematic files ONLY<br/>
+ <strong><code>type x1 y1 x2 y2 color</code></strong>
+</p>
+<table class="inline">
+ <tr>
+ <th>Field</th><th>Type/unit</th><th>Description</th>
+ </tr>
+ <tr>
+ <td>type</td><td>char</td><td>N</td>
+ </tr>
+ <tr>
+ <td>x1</td><td>int/mils</td><td>First X coordinate</td>
+ </tr>
+ <tr>
+ <td>y1</td><td>int/mils</td><td>First Y coordinate</td>
+ </tr>
+ <tr>
+ <td>x2</td><td>int/mils</td><td>Second X coordinate</td>
+ </tr>
+ <tr>
+ <td>y2</td><td>int/mils</td><td>Second Y coordinate</td>
+ </tr>
+ <tr>
+ <td>color</td><td>int</td><td>Color index</td>
+ </tr>
+</table>
+<ul>
+<li class="level1"><div class="li"> Nets can only appear in schematic files.</div>
+</li>
+<li class="level1"><div class="li"> You cannot have a zero length net (the tools will throw them away).</div>
+</li>
+</ul>
+
+<p>
+ Example:<br/>
+
+</p>
+<pre class="code">N 12700 29400 32900 29400 4</pre>
+
+<p>
+A net segment from (12700, 29400) to (32900, 29400) with color index 4.
+</p>
+
+</div>
+<!-- SECTION "net" [18510-19035] -->
+<h3><a name="bus" id="bus">bus</a></h3>
+<div class="level3">
+
+<p>
+Valid in: Schematic files ONLY<br/>
+ <strong><code>type x1 y1 x2 y2 color ripperdir</code></strong>
+</p>
+<table class="inline">
+ <tr>
+ <th>Field</th><th>Type/unit</th><th>Description</th>
+ </tr>
+ <tr>
+ <td>type</td><td>char</td><td>U</td>
+ </tr>
+ <tr>
+ <td>x1</td><td>int/mils</td><td>First X coordinate</td>
+ </tr>
+ <tr>
+ <td>y1</td><td>int/mils</td><td>First Y coordinate</td>
+ </tr>
+ <tr>
+ <td>x2</td><td>int/mils</td><td>Second X coordinate</td>
+ </tr>
+ <tr>
+ <td>y2</td><td>int/mils</td><td>Second Y coordinate</td>
+ </tr>
+ <tr>
+ <td>color</td><td>int</td><td>Color index</td>
+ </tr>
+ <tr>
+ <td>ripperdir</td><td>int</td><td>Direction of bus rippers</td>
+ </tr>
+</table>
+<ul>
+<li class="level1"><div class="li"> The ripperdir field for an brand new bus is 0.</div>
+</li>
+<li class="level1"><div class="li"> The ripperdir field takes on a value of 1 or -1 when a net is connected to the bus for the first time. This value indicates the direction of the ripper symbol. The ripper direction is set to the same value for the entire life of the bus object.</div>
+</li>
+<li class="level1"><div class="li"> Buses can only appear in schematic files.</div>
+</li>
+<li class="level1"><div class="li"> You cannot have a zero length bus (the tools will throw them away).</div>
+</li>
+</ul>
+
+<p>
+ Example:<br/>
+
+</p>
+<pre class="code">U 27300 37400 27300 35300 3 0</pre>
+
+<p>
+A bus segment from (27300, 37400) to (27300, 35300) with color index 3 and no nets have been connected to this bus segment.
+</p>
+
+</div>
+<!-- SECTION "bus" [19036-19967] -->
+<h3><a name="pin" id="pin">pin</a></h3>
+<div class="level3">
+
+<p>
+Valid in: Symbol files ONLY<br/>
+ <strong><code>type x1 y1 x2 y2 color pintype whichend</code></strong>
+</p>
+<table class="inline">
+ <tr>
+ <th>Field</th><th>Type/unit</th><th>Description</th>
+ </tr>
+ <tr>
+ <td>type</td><td>char</td><td>P</td>
+ </tr>
+ <tr>
+ <td>x1</td><td>int/mils</td><td>First X coordinate</td>
+ </tr>
+ <tr>
+ <td>y1</td><td>int/mils</td><td>First Y coordinate</td>
+ </tr>
+ <tr>
+ <td>x2</td><td>int/mils</td><td>Second X coordinate</td>
+ </tr>
+ <tr>
+ <td>y2</td><td>int/mils</td><td>Second Y coordinate</td>
+ </tr>
+ <tr>
+ <td>color</td><td>int</td><td>Color index</td>
+ </tr>
+ <tr>
+ <td>pintype</td><td>int</td><td>Type of pin</td>
+ </tr>
+ <tr>
+ <td>whichend</td><td>int</td><td>Specifies the active end</td>
+ </tr>
+</table>
+<ul>
+<li class="level1"><div class="li"> The pintype is an enumerated type:</div>
+<ul>
+<li class="level2"><div class="li"> NORMAL <acronym title="Personal Identification Number">PIN</acronym> = 0</div>
+</li>
+<li class="level2"><div class="li"> BUS <acronym title="Personal Identification Number">PIN</acronym> = 1 unused</div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> The whichend specifies which end point of the pin is the active connection port. Only this end point can have other pins or nets connected to it.</div>
+</li>
+<li class="level1"><div class="li"> To make the first end point active, whichend should be 0, else to specify the other end, whichend should be 1.</div>
+</li>
+<li class="level1"><div class="li"> Pins can only appear in symbol files.</div>
+</li>
+<li class="level1"><div class="li"> You cannot have a zero length pen (the tools will throw them away).</div>
+</li>
+</ul>
+
+<p>
+ Example:<br/>
+
+</p>
+<pre class="code">P 0 200 200 200 1 0 0</pre>
+
+<p>
+A pin from (0, 200) to (200, 200) with color index 1, a regular pin, and the first point being the active connection end.
+</p>
+
+</div>
+<!-- SECTION "pin" [19968-20964] -->
+<h3><a name="component" id="component">component</a></h3>
+<div class="level3">
+
+<p>
+Valid in: Schematic files ONLY<br/>
+ <strong><code>type x y selectable angle mirror basename</code></strong>
+</p>
+<table class="inline">
+ <tr>
+ <th>Field</th><th>Type/unit</th><th>Description</th>
+ </tr>
+ <tr>
+ <td>type</td><td>char</td><td>C</td>
+ </tr>
+ <tr>
+ <td>x</td><td>int/mils</td><td>Origin X coordinate</td>
+ </tr>
+ <tr>
+ <td>y</td><td>int/mils</td><td>Origin Y coordinate</td>
+ </tr>
+ <tr>
+ <td>selectable</td><td>int</td><td>Selectable flag</td>
+ </tr>
+ <tr>
+ <td>angle</td><td>int/degrees</td><td>Angle of the component</td>
+ </tr>
+ <tr>
+ <td>mirror</td><td>int</td><td>Mirror around Y axis</td>
+ </tr>
+ <tr>
+ <td>basename</td><td>string</td><td>The filename of the component</td>
+ </tr>
+</table>
+
+<p>
+ The selectable field is either 1 for selectable or 0 if not selectable.
+</p>
+<ul>
+<li class="level1"><div class="li"> The angle field can only take on the following values: 0, 90, 180, 270.</div>
+</li>
+<li class="level1"><div class="li"> The angle field can only be positive.</div>
+</li>
+<li class="level1"><div class="li"> The mirror flag is 0 if the component is not mirrored (around the Y axis).</div>
+</li>
+<li class="level1"><div class="li"> The mirror flag is 1 if the component is mirrored (around the Y axis).</div>
+</li>
+<li class="level1"><div class="li"> The just basename is the filename of the component. This filename is not the full path.</div>
+</li>
+</ul>
+
+<p>
+ Example:<br/>
+
+</p>
+<pre class="code">C 18600 19900 1 0 0 7400-1.sym</pre>
+
+<p>
+A component whoâ??s origin is at (18600,19900), is selectable, not rotated, not mirrored, and the basename of the component is 7400-1.sym.
+</p>
+
+</div>
+<!-- SECTION "component" [20965-21969] -->
+<h3><a name="path" id="path">path</a></h3>
+<div class="level3">
+
+<p>
+Valid in: Schematic and Symbol files<br/>
+ Valid since: Fileformat version 2 (release 1.5.1)<br/>
+ <strong><code>type color width capstyle dashstyle dashlength dashspace filltype fillwidth angle1 pitch1 angle2 pitch2 numlines<br/>
+
+path data line 1<br/>
+
+path data line 2<br/>
+
+path data line 3<br/>
+
+…<br/>
+
+path data line N</code></strong>
+</p>
+<table class="inline">
+ <tr>
+ <th>Field</th><th>Type/unit</th><th>Description</th>
+ </tr>
+ <tr>
+ <td>type</td><td>char</td><td>H</td>
+ </tr>
+ <tr>
+ <td>color</td><td>int</td><td>Color index</td>
+ </tr>
+ <tr>
+ <td>width</td><td>int/mils</td><td>Width of line</td>
+ </tr>
+ <tr>
+ <td>capstyle</td><td>int</td><td>Line cap style</td>
+ </tr>
+ <tr>
+ <td>dashstyle</td><td>int</td><td>Type of dash style</td>
+ </tr>
+ <tr>
+ <td>dashlength</td><td>int</td><td>Length of dash</td>
+ </tr>
+ <tr>
+ <td>dashspace</td><td>int</td><td>Space inbetween dashes</td>
+ </tr>
+ <tr>
+ <td>filltype</td><td>int</td><td>Type of fill</td>
+ </tr>
+ <tr>
+ <td>fillwidth</td><td>int/mils</td><td>Width of the fill lines</td>
+ </tr>
+ <tr>
+ <td>angle1</td><td>int/degrees</td><td>First angle of fill</td>
+ </tr>
+ <tr>
+ <td>pitch1</td><td>int/mils</td><td>First pitch/spacing of fill</td>
+ </tr>
+ <tr>
+ <td>angle2</td><td>int/degrees</td><td>Second angle of fill</td>
+ </tr>
+ <tr>
+ <td>pitch2</td><td>int/mils</td><td>Second pitch/spacing of fill</td>
+ </tr>
+ <tr>
+ <td>num_lines</td><td>int</td><td>Number of lines of path data (1 based)</td>
+ </tr>
+ <tr>
+ <td>path data line 1 … N</td><td>path data</td><td>The path data, on seperate lines</td>
+ </tr>
+</table>
+<ul>
+<li class="level1"><div class="li"> The capstyle is an enumerated type:</div>
+<ul>
+<li class="level2"><div class="li"> END NONE = 0</div>
+</li>
+<li class="level2"><div class="li"> END SQUARE = 1</div>
+</li>
+<li class="level2"><div class="li"> END ROUND = 2</div>
+</li>
+</ul>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> The dashstyle is an enumerated type:</div>
+<ul>
+<li class="level2"><div class="li"> TYPE SOLID = 0</div>
+</li>
+<li class="level2"><div class="li"> TYPE DOTTED = 1</div>
+</li>
+<li class="level2"><div class="li"> TYPE DASHED = 2</div>
+</li>
+<li class="level2"><div class="li"> TYPE CENTER = 3</div>
+</li>
+<li class="level2"><div class="li"> TYPE PHANTOM = 4</div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> The dashlength parameter is not used for TYPE SOLID and TYPE DOTTED. This parameter should take on a value of -1 in these cases.</div>
+</li>
+<li class="level1"><div class="li"> The dashspace paramater is not used for TYPE SOLID. This parameter should take on a value of -1 in these case.</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> The filltype parameter is an enumerated type:</div>
+<ul>
+<li class="level2"><div class="li"> FILLING HOLLOW = 0</div>
+</li>
+<li class="level2"><div class="li"> FILLING FILL = 1</div>
+</li>
+<li class="level2"><div class="li"> FILLING MESH = 2</div>
+</li>
+<li class="level2"><div class="li"> FILLING HATCH = 3</div>
+</li>
+<li class="level2"><div class="li"> FILLING VOID = 4 unused</div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> If the filltype is 0 (FILLING HOLLOW), then all the fill parameters should take on a value of -1.</div>
+</li>
+<li class="level1"><div class="li"> The fill type FILLING FILL is a solid color fill.</div>
+</li>
+<li class="level1"><div class="li"> The two pairs of pitch and spacing control the fill or hatch if the fill type is FILLING MESH.</div>
+</li>
+<li class="level1"><div class="li"> Only the first pair of pitch and spacing are used if the fill type is FILLING HATCH.</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> The format of path data is deliberately similar to that of <a href="http://www.w3.org/TR/SVG/paths.html"; class="urlextern" title="http://www.w3.org/TR/SVG/paths.html"; rel="nofollow">paths in the W3C SVG standard</a>.</div>
+</li>
+<li class="level1"><div class="li"> The subset of the <acronym title="Scalable Vector Graphics">SVG</acronym> path syntax emitted by gEDA is documented below.</div>
+</li>
+<li class="level1"><div class="li"> As an implementation detail; libgeda takes code from librsvg, an <acronym title="Scalable Vector Graphics">SVG</acronym> parsing library. As a result, the majority of <acronym title="Scalable Vector Graphics">SVG</acronym> path syntax is read correctly, however this is always normalised to absolute move, line, bezier curve and close-path commands internally (and is saved as such).</div>
+</li>
+<li class="level1"><div class="li"> Coordintes along the path are specified in the standard gschem coordinate space.</div>
+</li>
+</ul>
+
+<p>
+ Example:
+</p>
+<pre class="code">H 3 10 0 0 -1 -1 0 -1 -1 -1 -1 -1 5
+M 410,240
+L 501,200
+L 455,295
+L 435,265
+z</pre>
+
+<p>
+A path starting at (410,240) with lines drawn from there, and joining points (501,200), (455,295), (435,265), closing back to its origin. It has color index 3, is 10 mils thick, no cap, solid style. There are 5 lines of path data.
+</p>
+
+</div>
+<!-- SECTION "path" [21970-24820] -->
+<h3><a name="font" id="font">font</a></h3>
+<div class="level3">
+
+<p>
+Valid in: Special font files ONLY<br/>
+ <strong><code>type character width flag</code></strong>
+</p>
+<table class="inline">
+ <tr>
+ <th>Field</th><th>Type/unit</th><th>Description</th>
+ </tr>
+ <tr>
+ <td>type</td><td>char</td><td>F</td>
+ </tr>
+ <tr>
+ <td>character</td><td>char</td><td>The character being defined</td>
+ </tr>
+ <tr>
+ <td>width</td><td>int/mils</td><td>Width of the character (mils)</td>
+ </tr>
+ <tr>
+ <td>flag</td><td>int</td><td>Special space flag</td>
+ </tr>
+</table>
+<ul>
+<li class="level1"><div class="li"> This is a special tag and should ONLY show up in font definition files.</div>
+</li>
+<li class="level1"><div class="li"> If the font character being defined is the space character (32) then flag should be 1, otherwise 0.</div>
+</li>
+</ul>
+
+<p>
+ Example:<br/>
+
+</p>
+<pre class="code">F 11 1</pre>
+
+<p>
+The above font definition is for the space character.
+</p>
+
+</div>
+<!-- SECTION "font" [24821-25342] -->
+<h2><a name="colors" id="colors">Colors</a></h2>
+<div class="level2">
+
+<p>
+In the gEDA/gaf schematic and symbol file format colors are specified via an integer index. The relationship between integer and color is based on object type. Each object type typically has one or more colors. Here is a table of color index to object type:
+</p>
+<table class="inline">
+ <tr>
+ <th>Index</th><th>Object type</th>
+ </tr>
+ <tr>
+ <td>0</td><td>BACKGROUND_COLOR</td>
+ </tr>
+ <tr>
+ <td>1</td><td><acronym title="Personal Identification Number">PIN</acronym>_COLOR</td>
+ </tr>
+ <tr>
+ <td>2</td><td>NET_ENDPOINT_COLOR</td>
+ </tr>
+ <tr>
+ <td>3</td><td>GRAPHIC_COLOR</td>
+ </tr>
+ <tr>
+ <td>4</td><td>NET_COLOR</td>
+ </tr>
+ <tr>
+ <td>5</td><td>ATTRIBUTE_COLOR</td>
+ </tr>
+ <tr>
+ <td>6</td><td>LOGIC_BUBBLE_COLOR</td>
+ </tr>
+ <tr>
+ <td>7</td><td>DOTS_GRID_COLOR</td>
+ </tr>
+ <tr>
+ <td>8</td><td>DETACHED_ATTRIBUTE_COLOR</td>
+ </tr>
+ <tr>
+ <td>9</td><td>TEXT_COLOR</td>
+ </tr>
+ <tr>
+ <td>10</td><td>BUS_COLOR</td>
+ </tr>
+ <tr>
+ <td>11</td><td>SELECT_COLOR</td>
+ </tr>
+ <tr>
+ <td>12</td><td>BOUNDINGBOX_COLOR</td>
+ </tr>
+ <tr>
+ <td>13</td><td>ZOOM_BOX_COLOR</td>
+ </tr>
+ <tr>
+ <td>14</td><td>STROKE_COLOR</td>
+ </tr>
+ <tr>
+ <td>15</td><td>LOCK_COLOR</td>
+ </tr>
+ <tr>
+ <td>16</td><td>OUTPUT_BACKGROUND_COLOR</td>
+ </tr>
+ <tr>
+ <td>17</td><td>FREESTYLE1_COLOR</td>
+ </tr>
+ <tr>
+ <td>18</td><td>FREESTYLE2_COLOR</td>
+ </tr>
+ <tr>
+ <td>19</td><td>FREESTYLE3_COLOR</td>
+ </tr>
+ <tr>
+ <td>20</td><td>FREESTYLE4_COLOR</td>
+ </tr>
+ <tr>
+ <td>21</td><td>JUNCTION_COLOR</td>
+ </tr>
+ <tr>
+ <td>22</td><td>MESH_GRID_MAJOR_COLOR</td>
+ </tr>
+ <tr>
+ <td>23</td><td>MESH_GRID_MINOR_COLOR</td>
+ </tr>
+</table>
+
+<p>
+ The actual color associated with the color index is defined on a per tool bases. Objects are typically assigned their corresponding color index, but it is permissible (sometimes) to assign other color index values to different object types.
+</p>
+
+</div>
+<!-- SECTION "Colors" [25343-26381] -->
+<h2><a name="attributes" id="attributes">Attributes</a></h2>
+<div class="level2">
+
+<p>
+Attributes are enclosed in braces {} and can only be text. Attributes are text items which take on the form name=value. If it doesnâ??t have name=value, itâ??s not an attribute. Attributes are attached to the previous object. Hereâ??s an example:
+</p>
+<pre class="code">P 988 500 1300 500 1
+{
+T 1000 570 5 8 1 1 0
+pinseq=3
+T 1000 550 5 8 1 1 0
+pinnumber=3
+}</pre>
+
+<p>
+The object is a pin which has an attribute pinnumber=3 and pinseq=3 (name=value). You can have multiple text objects (both the T … and text string are required) in between the braces {}. As of 20021103, you can only attached text items as attributes. Attaching other object types as attributes is unsupported.<br/>
+ You can also have â??toplevelâ?? attributes. These attributes are not attached to any object, but instead are just text objects that take on the form name=value.<br/>
+ These attributes are useful when you need to convey some info about a schematic page or symbol and need the netlister to have access to this info.
+</p>
+
+</div>
+<!-- SECTION "Attributes" [26382-27369] -->
+<h2><a name="embedded_components" id="embedded_components">Embedded Components</a></h2>
+<div class="level2">
+
+<p>
+Embedded components are components which have all of their definition stored within the schematic file. When a users place a component onto a schematic page, they have the option of making the component embedded. Other than storing all the symbol information inside of the schematic, an embedded component is just any other component. Embedded components are defined as:
+</p>
+<pre class="code">C 18600 21500 1 0 0 EMBEDDED555-1.sym
+[
+...
+... Embedded primitive objects
+...
+]</pre>
+
+<p>
+In the example above, <strong>555-1.sym</strong> is the component. The EMBEDDED tag and the [ ] are the distinguishing characteristics of embedded components. <strong>componentname.sym</strong> must exist in one of the specified component-libraries if you want to unembed the component.
+</p>
+
+</div>
+<!-- SECTION "Embedded Components" [27370-28134] -->
+<h2><a name="path_data" id="path_data">Path data</a></h2>
+<div class="level2">
+
+<p>
+The gEDA/gaf path data format has been deliberately specified to match a subset of <a href="http://www.w3.org/TR/SVG/paths.html"; class="urlextern" title="http://www.w3.org/TR/SVG/paths.html"; rel="nofollow">that in the W3C SVG standard.</a>.
+</p>
+<ul>
+<li class="level1"><div class="li"> As an implementation detail; libgeda takes code from librsvg, an <acronym title="Scalable Vector Graphics">SVG</acronym> parsing library. As a result, the majority of <acronym title="Scalable Vector Graphics">SVG</acronym> path syntax is read correctly, however this is always normalised to absolute move, line, bezier curve and close-path commands internally (and is saved as such).</div>
+</li>
+<li class="level1"><div class="li"> Coordintes along the path are specified in the standard gschem coordinate space.</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> Those path commands which gEDA emits, and will gaurantee to parse, are listed in the table below:<br/>
+</div>
+</li>
+</ul>
+
+<p>
+(Text taken from the above <acronym title="Scalable Vector Graphics">SVG</acronym> specification).
+</p>
+<ul>
+<li class="level1"><div class="li"> In the table below, the following notation is used:</div>
+<ul>
+<li class="level2"><div class="li"> (): grouping of parameters</div>
+</li>
+<li class="level2"><div class="li"> +: 1 or more of the given parameter(s) is required</div>
+</li>
+</ul>
+</li>
+</ul>
+<table class="inline">
+ <tr>
+ <th>Command</th><th>Name</th><th>Parameters</th><th>Description</th>
+ </tr>
+ <tr>
+ <td>M (absolute)</td><td>moveto</td><td>(x,y)+</td><td>Start a new sub-path at the given (x,y) coordinate. M (uppercase) indicates that absolute coordinates will follow; m (lowercase) indicates that relative coordinates will follow. If a relative moveto (m) appears as the first element of the path, then it is treated as a pair of absolute coordinates. If a moveto is followed by multiple pairs of coordinates, the subsequent pairs are treated as implicit lineto commands.</td>
+ </tr>
+ <tr>
+ <td>L (absolute)</td><td>lineto</td><td>(x,y)+</td><td>Draw a line from the current point to the given (x,y) coordinate which becomes the new current point. L (uppercase) indicates that absolute coordinates will follow; l (lowercase) indicates that relative coordinates will follow. A number of coordinates pairs may be specified to draw a polyline. At the end of the command, the new current point is set to the final set of coordinates provided.</td>
+ </tr>
+ <tr>
+ <td>C (absolute)</td><td>curveto</td><td>(x1,y1 x2,y2 x,y)+</td><td>Draws a cubic Bézier curve from the current point to (x,y) using (x1,y1) as the control point at the beginning of the curve and (x2,y2) as the control point at the end of the curve. C (uppercase) indicates that absolute coordinates will follow; c (lowercase) indicates that relative coordinates will follow. Multiple sets of coordinates may be specified to draw a polybézier. At the end of the command, the new current point becomes the final (x,y) coordinate pair used in the polybézier.</td>
+ </tr>
+ <tr>
+ <td>Z or z</td><td>closepath</td><td>(none)</td><td>Close the current subpath by drawing a straight line from the current point to current subpathâ??s initial point.</td>
+ </tr>
+</table>
+<ul>
+<li class="level1"><div class="li"> gEDAâ??s output currently emits only the absolute coordinate versions of the above commands.</div>
+</li>
+<li class="level1"><div class="li"> gEDAâ??s output currently emits the commands, M, L, C before every set of coordinates, even where they could be omited according to the <acronym title="Scalable Vector Graphics">SVG</acronym> specification.</div>
+</li>
+<li class="level1"><div class="li"> gEDAâ??s output places commas between x,y coordinates. These may be replaced with whitespace according to the <acronym title="Scalable Vector Graphics">SVG</acronym> specification.</div>
+</li>
+<li class="level1"><div class="li"> gEDAâ??s does not currently support more than one sub-path.</div>
+</li>
+<li class="level1"><div class="li"> gEDA currently emits one path data line per command + coordinate set.</div>
+</li>
+</ul>
+
+<p>
+ As example, lets draw the outline of an AND gate. The path data is:
+</p>
+<pre class="code">M 100,100 L 500,100 C 700,100 800,275 800,400
+C 800,525 700,700 500,700 L 100,700 z</pre>
+
+<p>
+And a complete schematic:
+</p>
+<pre class="code">v 20080706 1
+H 3 0 0 0 -1 -1 0 2 20 100 -1 -1 6
+M 100,100
+L 500,100
+C 700,100 800,275 800,400
+C 800,525 700,700 500,700
+L 100,700
+z</pre>
+
+<p>
+The resulting path (with control points drawn on to illustrate their positions) is shown here:
+</p>
+
+<p>
+<a href="media/geda/path_example_and_gate-smaller.png" class="media" target="_blank" title="geda:path_example_and_gate-smaller.png"><img src="media/geda/path_example_and_gate-smaller.png" class="media" title="" alt="" /></a>
+</p>
+
+</div>
+<!-- SECTION "Path data" [28135-31563] -->
+<h2><a name="document_revision_history" id="document_revision_history">Document Revision History</a></h2>
+<div class="level2">
+<table class="inline">
+ <tr>
+ <td>November 30th, 2002</td><td>Created fleformats.tex from fleformats.html.</td>
+ </tr>
+ <tr>
+ <td>December 1st, 2002</td><td>Continued work on this document.</td>
+ </tr>
+ <tr>
+ <td>October 4th, 2003</td><td>Added new file format version flag info.</td>
+ </tr>
+ <tr>
+ <td>October 19th, 2003</td><td>Added num lines text field.</td>
+ </tr>
+ <tr>
+ <td>November 2nd, 2008</td><td>Added path object, bumping file format version to 2</td>
+ </tr>
+</table>
+
+</div>
+<!-- SECTION "Document Revision History" [31564-] --></body>
+</html>
diff --git a/docs/wiki/geda-format_translation.html b/docs/wiki/geda-format_translation.html
new file mode 100644
index 0000000..6c8d8ee
--- /dev/null
+++ b/docs/wiki/geda-format_translation.html
@@ -0,0 +1,391 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#file_format_translation" class="toc">File format translation</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#scope" class="toc">Scope</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#tool_types_needing_support" class="toc">Tool types needing support</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#geda_tools" class="toc">gEDA tools</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#other_free_tools_that_should_be_well_supported" class="toc">Other free tools that should be well supported</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#non-free_import_and_export" class="toc">Non-free import and export</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#geda_missing_functionality" class="toc">gEDA missing functionality</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#explicitly_not_supported" class="toc">Explicitly not supported</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#concepts" class="toc">Concepts</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#some_possible_formats" class="toc">Some possible formats</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#representation_of_physical_placement" class="toc">Representation of physical placement</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#applications" class="toc">Applications</a></span></div></li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="file_format_translation" id="file_format_translation">File format translation</a></h1>
+<div class="level1">
+
+<p>
+ We need a universal translator system that can translate in all directions between gEDA tools, possible future gEDA tools, and outside tools that are likely to be used with gEDA tools.
+</p>
+
+</div>
+<!-- SECTION "File format translation" [1-225] -->
+<h2><a name="scope" id="scope">Scope</a></h2>
+<div class="level2">
+
+<p>
+ Of course, everything to everything is not reasonable. So, set a limit of gEDA tools, possible future gEDA tools, and outside tools that are likely to be used with gEDA tools. Of course, tool formats where translation doesnâ??t make sense donâ??t need to be supported.
+</p>
+
+<p>
+The idea is to have an intermediate format. First translate to the intermediate format, then translate out. The intermediate format should be sufficiently expressive that there can be a lossless round trip from any gEDA tool format to the intermediate format and back.
+</p>
+
+<p>
+Lossless means that the resultant file is equivalent in how it works. It is not necessary to preserve formatting and other things that donâ??t matter.
+</p>
+
+<p>
+All of the formats needing translation presently consist of lists of objects, with some kind of encapsulation. Each object has connections and attributes.
+</p>
+
+<p>
+This suggests the possible of a standard netlist format as the intermediate format.
+</p>
+
+<p>
+Further discussion related only to formats that fit this model.
+</p>
+
+<p>
+If possible, the format chosen should have a history of use for at least part of this, and have a published specification that is externally controlled and freely available.
+</p>
+
+<p>
+There needs to be a way to merge changes from any target/source without messing up other parts.
+</p>
+
+</div>
+<!-- SECTION "Scope" [226-1514] -->
+<h3><a name="tool_types_needing_support" id="tool_types_needing_support">Tool types needing support</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> schematic</div>
+</li>
+<li class="level1"><div class="li"> layout</div>
+</li>
+<li class="level1"><div class="li"> simulation</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Tool types needing support" [1515-1592] -->
+<h3><a name="geda_tools" id="geda_tools">gEDA tools</a></h3>
+<div class="level3">
+
+<p>
+Lossless round trip is required, so archival storage can use the intermediate format.
+</p>
+<ul>
+<li class="level1"><div class="li"> gschem</div>
+</li>
+<li class="level1"><div class="li"> pcb</div>
+</li>
+<li class="level1"><div class="li"> gnucap</div>
+</li>
+<li class="level1"><div class="li"> Icarus Verilog</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "gEDA tools" [1593-1749] -->
+<h3><a name="other_free_tools_that_should_be_well_supported" id="other_free_tools_that_should_be_well_supported">Other free tools that should be well supported</a></h3>
+<div class="level3">
+
+<p>
+These tools are free, too. The standard needs to support them on an equal basis with gEDA.
+</p>
+<ul>
+<li class="level1"><div class="li"> NGspice</div>
+</li>
+<li class="level1"><div class="li"> Qucs</div>
+</li>
+<li class="level1"><div class="li"> Kicad</div>
+</li>
+<li class="level1"><div class="li"> Magic</div>
+</li>
+<li class="level1"><div class="li"> Electric</div>
+</li>
+<li class="level1"><div class="li"> Xcircuit</div>
+</li>
+<li class="level1"><div class="li"> Fritzing</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Other free tools that should be well supported" [1750-1980] -->
+<h3><a name="non-free_import_and_export" id="non-free_import_and_export">Non-free import and export</a></h3>
+<div class="level3">
+
+<p>
+Support for these will allow gEDA tools to play nice with the commercial world. Basic functionality is needed, but it doesnâ??t need to be lossless. Lossless should be possible, but it is not a high priority to actually implement it.
+</p>
+<ul>
+<li class="level1"><div class="li"> Eagle</div>
+</li>
+<li class="level1"><div class="li"> Orcad</div>
+</li>
+<li class="level1"><div class="li"> LTspice</div>
+</li>
+<li class="level1"><div class="li"> Pads</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Non-free import and export" [1981-2293] -->
+<h3><a name="geda_missing_functionality" id="geda_missing_functionality">gEDA missing functionality</a></h3>
+<div class="level3">
+
+<p>
+Hopefully having a translator system will provide a seed so these can be done.
+</p>
+<ul>
+<li class="level1"><div class="li"> Back annotation from layout or simulation to schematic</div>
+</li>
+<li class="level1"><div class="li"> Static timing analysis</div>
+</li>
+<li class="level1"><div class="li"> Post-layout signal integrity simulation.</div>
+</li>
+<li class="level1"><div class="li"> Layout - schematic comparison</div>
+</li>
+<li class="level1"><div class="li"> Use of the same schematic for the whole project.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "gEDA missing functionality" [2294-2628] -->
+<h3><a name="explicitly_not_supported" id="explicitly_not_supported">Explicitly not supported</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> Plotting</div>
+</li>
+<li class="level1"><div class="li"> Commands</div>
+</li>
+<li class="level1"><div class="li"> Behavioral modeling</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Explicitly not supported" [2629-2714] -->
+<h2><a name="concepts" id="concepts">Concepts</a></h2>
+<div class="level2">
+
+<p>
+ All of these consist of lists of objects, with connections and attributes.
+</p>
+
+<p>
+It is tradition that a netlist is used for interchange, but the traditional approach only goes one way, because information is lost in the translation.
+</p>
+
+<p>
+The format must convey the meaning, not necessarily in the same way as the toolâ??s native format or internal storage.
+</p>
+
+<p>
+It is not necessary to translate parts that are usually in libraries, and are tool specific, such as models, symbols, or footprints.
+</p>
+
+<p>
+All contenders for possible formats must support a loss round-trip to any other.
+</p>
+
+</div>
+<!-- SECTION "Concepts" [2715-3299] -->
+<h3><a name="some_possible_formats" id="some_possible_formats">Some possible formats</a></h3>
+<div class="level3">
+
+</div>
+
+<h4><a name="spice" id="spice">Spice</a></h4>
+<div class="level4">
+
+<p>
+ A popular netlist format. It has a history of use for interchange, but not yet for physical placement. Problems: irregular syntax, not sufficiently expressive. These problems have been a major hassle for years for developers. It is well accepted, but not by people who know it well.
+</p>
+
+</div>
+
+<h4><a name="verilog" id="verilog">Verilog</a></h4>
+<div class="level4">
+
+<p>
+ The structural subset is a good netlist format. It is regular, sufficiently expressive, and has a published standard. It has a history of use for interchange, but not yet for physical placement.
+</p>
+
+</div>
+
+<h4><a name="vhdl" id="vhdl">VHDL</a></h4>
+<div class="level4">
+
+<p>
+ The structural subset is a good netlist format. It is regular, sufficiently expressive, and has a published standard. It has a history of use for interchange, but not yet for physical placement.
+</p>
+
+</div>
+
+<h4><a name="spectre" id="spectre">Spectre</a></h4>
+<div class="level4">
+
+<p>
+ The structural subset is a good netlist format. It is regular, sufficiently expressive, but belongs to one company (Cadence), so rule it out. It has a history of use for simulation only.
+</p>
+
+</div>
+
+<h4><a name="xml" id="xml">XML</a></h4>
+<div class="level4">
+
+<p>
+ <acronym title="Extensible Markup Language">XML</acronym> is not really a format but a syntax. A good format can easily be made based on <acronym title="Extensible Markup Language">XML</acronym>, but has no history of use in a similar context. The syntax is well documented but there is no outside documentation of application in any related use.
+</p>
+
+</div>
+<!-- SECTION "Some possible formats" [3300-4524] -->
+<h3><a name="representation_of_physical_placement" id="representation_of_physical_placement">Representation of physical placement</a></h3>
+<div class="level3">
+
+<p>
+ This part is the only part where there is not a strong history of use for VHDL and Verilog.
+</p>
+
+<p>
+Ideas:
+</p>
+<ul>
+<li class="level1"><div class="li"> Nets are also objects with connections and attributes. Nets have meaning in all contexts.</div>
+</li>
+<li class="level1"><div class="li"> A place on a schematic can be considered to be an object, with connections and attributes.</div>
+</li>
+<li class="level1"><div class="li"> Pads, connectors, thermals, vias .. are also objects, with connections and attributes.</div>
+</li>
+<li class="level1"><div class="li"> Use `define (assuming Verilog format) to set aside sections that have meaning in one context but not another.</div>
+</li>
+<li class="level1"><div class="li"> This is a high level description. Take a high level view across all. Itâ??s not lines, boxes, and circles.</div>
+</li>
+<li class="level1"><div class="li"> If you must, lines, boxes, and circles can be objects too, but not translatable because they have no meaning in other contexts.</div>
+</li>
+<li class="level1"><div class="li"> Attributes that have no meaning are silently ignored. Attributes that have meaning in one context but not in another context are ignored where they have no meaning.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Representation of physical placement" [4525-5482] -->
+<h2><a name="applications" id="applications">Applications</a></h2>
+<div class="level2">
+
+<p>
+ Choosing the Verilog format as one possibility.
+</p>
+
+<p>
+The unit of encapsulation is the â??moduleâ??:
+</p>
+<pre class="code">module my-module(connections);
+// contents
+endmodule</pre>
+
+<p>
+ Each object in the list has a consistent syntax:
+</p>
+<pre class="code">type #(attributes) name (connections);</pre>
+
+<p>
+ Example:
+</p>
+<pre class="code">resistor #(.r(1k)) r123 (a, b);
+resistor #(.r(1k)) r234 (.p(b), .n(c));</pre>
+
+<p>
+ â??râ?? is the name of an attribute. â??1kâ?? is the value (a string).
+</p>
+
+<p>
+In the first example, connections are determined by order. In the second, they are mapped by name. Node â??bâ?? connects to pin â??pâ?? and node â??câ?? connects to pin â??nâ??.
+</p>
+
+<p>
+A â??netâ?? is also an object.
+</p>
+
+<p>
+In the above example, both connect to node b directly. In a schematic representation the connection would not be direct, but through a â??netâ??
+</p>
+<pre class="code">resistor #(.r(1k)) r123 (.p(a1), .n(b1));
+resistor #(.r(1k)) r125 (.p(b2), .n(c2));
+net b (.1(b1), .2(b2));</pre>
+
+<p>
+ The name of the net is â??bâ??. It has no attributes.
+</p>
+
+<p>
+For schematic, you can now place the nodes:
+</p>
+<pre class="code">place #(.x(1222), .y(3438)) place11333 (b1);
+place #(.x(4334), .y(8433)) place34894 (b2);
+place #(.x(9393), .y(4232)) place49334 (a1);
+place #(.x(2932), .y(2384)) place34983 (c2);</pre>
+
+<p>
+ Portions that apply in only certain contexts can be selectively included with â??ifdef:
+</p>
+<pre class="code">module my_circuit;
+ `ifdef SCHEMATIC
+ place ...
+ place ...
+ `endif
+ res ...
+ res ...
+ net ...
+endmodule</pre>
+
+<p>
+ Complex nets can be encapsulated:
+</p>
+<pre class="code">module net23842 (1,2,3);
+ net n23482 (1,2);
+ net n84333 (2,3);
+ `ifdef SCHEMATIC
+ place ...
+ place ...
+ place ...
+ `endif
+endmodule</pre>
+<pre class="code">module net9393 (1,2);
+ net #(.color(blue), .thickness(thin)) n38423 (1,2);
+endmodule</pre>
+
+</div>
+<!-- SECTION "Applications" [5483-] --></body>
+</html>
diff --git a/docs/wiki/geda-gattrib_readme.html b/docs/wiki/geda-gattrib_readme.html
new file mode 100644
index 0000000..f4a7b19
--- /dev/null
+++ b/docs/wiki/geda-gattrib_readme.html
@@ -0,0 +1,152 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="gattrib_readme" id="gattrib_readme">gattrib README</a></h1>
+<div class="level1">
+<pre class="code">******************************************************************
+************* DANGER!! Read the entirety of this **************
+************ README before you try runing gattrib! *************
+******************************************************************
+
+
+INTRODUCTION
+
+Gattrib is gEDA's attribute editor. It reads a set of gschem .sch
+files (schematic files), and creates a spreadsheet showing all
+components in rows, with the associated component attributes listed in
+the columns. It allows the user to add, modify, or delete component
+attributes outside of gschem, and then save the .sch files back
+out. When it is completed, it will allow the user to edit attributes
+attached to components, nets, and pins. (Currently, only component
+attribute editing is implemented; pin attributes are displayed only,
+and net attributes are TBD.)
+
+Gattrib is useful in situations where you need to view, add, modify,
+or delete a number of attributes all at once. It saves you the pain
+of clicking on each component and repeatedly using gschem's attribute
+editor to modify component attributes. For example, if you create a
+large design with generic components, and then later want to attach
+"footprint" attributes to your components, it is a real hassle to do
+so using gschem. In this situation, you can run gattrib on your
+design files to attach the "footprint" attributes all at once using an
+easy-to-use spreadsheet.
+
+WARNING NOTE: Gattrib is currently PRE-ALPHA SOFTWARE!
+It has been tested on several designs, but is not garuanteed to work.
+It may even trash your design! Therefore, if you wish to try gattrib
+out, please create a backup copy of your design before you run it!
+
+------------------------------------------------------------------
+USAGE
+
+You can invoke gattrib on your design from the command line in the
+following way:
+
+gattrib my_design_*.sch
+
+(This assumes you have a multi-page design with file names
+"my_design_1.sch", "my_design_2.sch", etc.) Gattrib will then read in
+your design, and present you with a spreadsheet showing all components
+and associated attributes.
+
+You can also just run gattrib, and specify the input files using the
+file->open dialog box.
+
+To edit your attributes, just edit the cells in the spreadsheet.
+
+To save your design, just select "save" from the command menu. Note
+that no checks are currently done when you select save. Be careful!
+
+To quit, just select "quit" from the command menu. Note that
+currently no checks thet you have saved your design are done when you
+quit.
+
+If you want to add an entirely new attribute to your design (i.e. one
+which doesn't exist on any component), you must first attach at least
+one instance of that attribute to a component using gschem. Then you
+can use gattrib to attach the attribute to the remaining components.
+(The reason for this is that gattrib creates its spreadsheet columns
+based upon all attributes it finds when reading in the design.
+Therefore, to create a column for a new attribute, you need to make
+sure that that new attribute pre-exists in the design.) In the future,
+you will be able to add new attribute columns directly from gattrib,
+but this feature is currently unimplemented.
+
+------------------------------------------------------------------
+FEATURES
+
+The following features are currently implemented:
+
+* .sch file read in from command line.
+* .sch file read in from menu.
+* .sch file save out from menu.
+* Component attribute editing (of course).
+* Pin attribute viewing.
+* Quit from menu.
+
+The following features are currently unimplemented, but will be
+incorporated at some future date:
+
+* Throw up "Are you sure" dialog boxes upon selecting "save" and
+ "quit" from menu.
+* Alphabetic sort of rows. (Should happen automatically upon read-in
+ of design.)
+* Editing of net attributes (important for setting routing
+ attributes).
+* Adding/deleting attribute columns (to add/delete entire sets of
+ attributes from a design.)
+* Search/replace of individual attributes.
+* Search for component refdeses & netnames.
+* Set/view component & net visibility (through options pull-down
+ menu). Currently, visibility is "invisible", and both name & value
+ are displayed (if you turn on the visibility).
+
+Note that if you select unimplemented features from the menu, nothing
+will happen.
+
+------------------------------------------------------------------
+INSTALLATION
+
+To install gattrib, place the tarball in the directory where your gEDA
+sources live. Then do:
+
+tar -zxvf geda-gattrib-20040806.tar.gz
+cd geda-gattrib-20040806
+./configure --prefix=/path/to/your/geda/stuff
+make
+make install
+
+Note that you may need to set some environment variables first. If
+your compilation barfs, try setting these (for csh):
+
+setenv LD_LIBRARY_PATH /usr/local/geda/lib:$LD_LIBRARY_PATH
+setenv PATH /usr/local/geda/bin:$PATH
+setenv PKG_CONFIG_PATH /usr/local/geda/lib/pkgconfig:$PKG_CONFIG_PATH
+
+------------------------------------------------------------------
+CREDITS/CONTACT:
+
+Gattrib was cobbled together by Stuart Brorson starting in December
+2003 from parts culled from GtkSheet (GTK+Extra) and gEDA. Please
+mail bug reports to: sdb@xxxxxxxxxx
+
+
+
+</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-gedasuite_installation.html b/docs/wiki/geda-gedasuite_installation.html
new file mode 100644
index 0000000..c1ad0f4
--- /dev/null
+++ b/docs/wiki/geda-gedasuite_installation.html
@@ -0,0 +1,142 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#how_do_i_install_the_geda_suite" class="toc">How do I install the gEDA Suite?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#fedora_core_4_install_notes" class="toc">Fedora Core 4 install notes</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#fedora_core_3_install_notes" class="toc">Fedora Core 3 install notes</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#fedora_core_2_install_notes" class="toc">Fedora Core 2 install notes</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#fedora_core_1_install_notes" class="toc">Fedora Core 1 install notes</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#suse_9.3_install_notes" class="toc">Suse 9.3 install notes</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#suse_10.0_install_notes" class="toc">Suse 10.0 install notes</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#suse_10.1_install_notes" class="toc">Suse 10.1 install notes</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#debian_install_notes" class="toc">Debian install notes</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#ubuntu_install_notes" class="toc">Ubuntu install notes</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#windows_install_notes" class="toc">Windows install notes</a></span></div></li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h2><a name="how_do_i_install_the_geda_suite" id="how_do_i_install_the_geda_suite">How do I install the gEDA Suite?</a></h2>
+<div class="level2">
+
+<p>
+The easiest way to install the gEDA Suite is to grab the gEDA Binary Suite installer and use it. The instructions are contained in the README available on the <a href="http://geda.seul.org/download.html"; class="urlextern" title="http://geda.seul.org/download.html"; rel="nofollow">downloads page</a>.
+</p>
+
+<p>
+Also, people have created RedHat RPMs, Debian Debs, and Mac OSX Fink packages if you prefer to install that way. These binary distributions are available on the <a href="http://geda.seul.org/download.html"; class="urlextern" title="http://geda.seul.org/download.html"; rel="nofollow">downloads page</a>. Finally, source tarballs for all programs are also available on the <a href="http://geda.seul.org/download.html"; class="urlextern" title="http://geda.seul.org/download.html"; rel="nofollow">downloads page</a>.
+</p>
+
+</div>
+<!-- SECTION "How do I install the gEDA Suite?" [1-601] -->
+<h2><a name="fedora_core_4_install_notes" id="fedora_core_4_install_notes">Fedora Core 4 install notes</a></h2>
+<div class="level2">
+
+<p>
+<a href="geda-fc4.html" class="wikilink1" title="geda-fc4.html">FC4 notes available here</a>
+</p>
+
+</div>
+<!-- SECTION "Fedora Core 4 install notes" [602-680] -->
+<h2><a name="fedora_core_3_install_notes" id="fedora_core_3_install_notes">Fedora Core 3 install notes</a></h2>
+<div class="level2">
+
+<p>
+<a href="geda-fc3.html" class="wikilink1" title="geda-fc3.html">FC3 notes available here</a>
+</p>
+
+</div>
+<!-- SECTION "Fedora Core 3 install notes" [681-759] -->
+<h2><a name="fedora_core_2_install_notes" id="fedora_core_2_install_notes">Fedora Core 2 install notes</a></h2>
+<div class="level2">
+
+<p>
+<a href="geda-fc2.html" class="wikilink1" title="geda-fc2.html">FC2 notes available here</a>
+</p>
+
+</div>
+<!-- SECTION "Fedora Core 2 install notes" [760-838] -->
+<h2><a name="fedora_core_1_install_notes" id="fedora_core_1_install_notes">Fedora Core 1 install notes</a></h2>
+<div class="level2">
+
+<p>
+<a href="geda-fc1.html" class="wikilink1" title="geda-fc1.html">FC1 notes available here</a>
+</p>
+
+</div>
+<!-- SECTION "Fedora Core 1 install notes" [839-917] -->
+<h2><a name="suse_9.3_install_notes" id="suse_9.3_install_notes">Suse 9.3 install notes</a></h2>
+<div class="level2">
+
+<p>
+<a href="geda-suse_9.3.html" class="wikilink1" title="geda-suse_9.3.html">SuSE 9.3 notes available here</a>
+</p>
+
+</div>
+<!-- SECTION "Suse 9.3 install notes" [918-1001] -->
+<h2><a name="suse_10.0_install_notes" id="suse_10.0_install_notes">Suse 10.0 install notes</a></h2>
+<div class="level2">
+
+<p>
+<a href="geda-suse_10.0.html" class="wikilink1" title="geda-suse_10.0.html">SuSE 10.0 notes available here</a>
+</p>
+
+</div>
+<!-- SECTION "Suse 10.0 install notes" [1002-1088] -->
+<h2><a name="suse_10.1_install_notes" id="suse_10.1_install_notes">Suse 10.1 install notes</a></h2>
+<div class="level2">
+
+<p>
+<a href="geda-suse_10.1.html" class="wikilink1" title="geda-suse_10.1.html">SuSE 10.1 notes available here</a>
+</p>
+
+</div>
+<!-- SECTION "Suse 10.1 install notes" [1089-1175] -->
+<h2><a name="debian_install_notes" id="debian_install_notes">Debian install notes</a></h2>
+<div class="level2">
+
+<p>
+<a href="geda-debian.html" class="wikilink1" title="geda-debian.html">Debian notes available here</a>
+</p>
+
+</div>
+<!-- SECTION "Debian install notes" [1176-1253] -->
+<h2><a name="ubuntu_install_notes" id="ubuntu_install_notes">Ubuntu install notes</a></h2>
+<div class="level2">
+
+<p>
+<a href="geda-ubuntu.html" class="wikilink1" title="geda-ubuntu.html">Ubuntu notes available here</a>
+</p>
+
+</div>
+<!-- SECTION "Ubuntu install notes" [1254-1332] -->
+<h2><a name="windows_install_notes" id="windows_install_notes">Windows install notes</a></h2>
+<div class="level2">
+
+<p>
+<a href="geda-cygwin.html" class="wikilink1" title="geda-cygwin.html">Cygwin notes available here</a>
+</p>
+
+</div>
+<!-- SECTION "Windows install notes" [1333-] --></body>
+</html>
diff --git a/docs/wiki/geda-gerbv_mp.html b/docs/wiki/geda-gerbv_mp.html
new file mode 100644
index 0000000..4a094e7
--- /dev/null
+++ b/docs/wiki/geda-gerbv_mp.html
@@ -0,0 +1,258 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="gerbv_man-page" id="gerbv_man-page">gerbv man-page</a></h1>
+<div class="level1">
+<pre class="code">gerbv(1) cvs-20051023 gerbv(1)
+
+
+
+NAME
+ gerbv - Gerber Viewer
+
+SYNOPSIS
+ gerbv [OPTIONS] [gerberfile[s]]
+
+DESCRIPTION
+ gerbv is a viewer for Gerber files. Gerber files is generated from dif-
+ ferent PCB CAD programs and are sent to subcontractors to actually make
+ the PCB. gerbv also supports Excellon/NC drill files.
+
+
+OPTIONS
+ Warning! On some platforms, which hasn�t long option available, only
+ short options are available.
+
+
+ gerbv Options
+ -V|--version Prints the version number of gerbv and exits.
+
+ -h|--help
+ Prints a brief usage guide.
+
+ -l <filename>|--log=<filename>
+ All error messages etc are stored in a file with filename <file-
+ name>.
+
+ -t <filename>|--tools=<filename>
+ Read Excellon tools from the file <filename>.
+
+ --geometry=<width>x<height>[<+->x-position[<+->y-position]]
+ Sets the the size of the window. X-position and y-position are
+ currently ignored by gerbv.
+
+ -p <project filename>|--project=<project filename>
+ Load a stored project. Please note that the project file must be
+ stored in the same directory as the gerber files.
+
+
+ GTK Options
+ --gtk-module=MODULE Load an additional GTK module
+
+ --g-fatal-warnings
+ Make all warnings fatal
+
+ --gtk-debug=FLAGS
+ GTK debugging flags to set
+
+ --gtk-no-debug=FLAGS
+ GTK debugging flags to unset
+
+ --gdk-debug=FLAGS
+ GDK debugging flags to set
+
+ --gdk-no-debug=FLAGS
+ GDK debugging flags to unset
+
+ --display=DISPLAY
+ X display to use
+
+ --sync Make X call synchronous
+
+ --no-xshm
+ Don�t use X shared memory extension
+
+ --name=NAME
+ Program name as used by the window manager
+
+ --class=CLASS
+ Program class as used by the window manager
+
+
+GENERAL
+ When you start gerbv you can give the files to be loaded on the command
+ line, either as each file separated with a space or by using wildcards.
+
+ The user interface is graphical. Simply press left mouse button and the
+ image will pan as you move the mouse. To manipulate a layer, right-
+ click on one of the rightmost buttons. That will bring up a pop-up menu
+ where you can select what you want to do with that layer (load file,
+ change color, etc).
+
+ If you hold the mouse button over one the rightmost button a tooltips
+ will show you the name of the file loaded on that layer.
+
+ Default of concurrently loaded files are 20 layers. You can change this
+ during configure with:
+
+ ./configure with-maxfiles=<number>
+
+
+ACTIVATION AND DEACTIVATION OF LAYERS
+ You can load several files at one time. You can then turn displaying of
+ the layers on and off by clicking on one of the rightmost buttons.
+
+ You can also control this from the keyboard. Press Alt, enter the num-
+ ber on the layer you want activate/deactivate on the numerical keypad
+ and then release the Alt key.
+
+
+ZOOMING
+ Zooming can be handled by either menu choices, keypressing, middle
+ mouse button or scroll wheel. If you press Alt+I you will zoom in and
+ if you press Alt+O you will zoom out.If you press middle mouse button
+ you will zoom out, and if you press Shift and middle mouse button you
+ will zoom in. Scroll wheel works if you enabled that in your X server
+ and mapped it to button 4 and 5. You can also zoom in by pressing z and
+ zoom out by pressing shift+z (ie Z). You can make the image fit by
+ pressing f (there is also a menu alternativ for this).
+
+ You can also do zooming by outline. Press right mouse button, draw,
+ release. The dashed line shows how the zooming will be dependent on
+ the resolution of the window. The non-dashed outline will show what you
+ actually selected. If you change your mind when started to mark out-
+ line, you can always abort by pressing escape. By holding down the
+ shift key when you press the right mouse button, you will select an
+ area where the point you started at will be the center of your selec-
+ tion.
+
+
+MEASUREMENTS
+ You can do measurement on the image displayed. By pressing shift, the
+ cursor changes to a plus. By using left mouse button you can draw the
+ lines that you want to measure. The result of the last measurement is
+ also displayed on the statusbar. All measurements are in the drawing
+ until you either zoom, pan or press the escape key.
+
+ The statusbar shows the current mouse position on the layer in the same
+ coordinates as in the file. Ie if you have (0,0) in the middle of the
+ image in the gerber files, the statusbar will show (0,0) at the same
+ place.
+
+
+SUPERIMPOSING
+ When you load several Gerber files, you can display them "on top of
+ each other", ie superimposing. The general way to display them are that
+ upper layers cover the layers beneath, which is called copy (GTK+
+ terms).
+
+ The other ways selectable are and, or, xor and invert. They map
+ directly to corresponding functions in GTK. In GTK they are described
+ as: "For colored images, only GDK_COPY, GDK_XOR and GDK_INVERT are gen-
+ erally useful. For bitmaps, GDK_AND and GDK_OR are also useful."
+
+
+PROJECTS
+ gerbv can also handle projects. A project consist of bunch of loaded
+ layers with their resp. color and the background color. The easiest way
+ to create a project is to load all files you want into the layer you
+ want, set all the colors etc and do a "Save Project As...".
+
+ You load a project either from the menu bar or by using the commandline
+ switches -p or --project.
+
+ Currently there is a limit in that the project file must be in the same
+ directory as the gerber files to be loaded.
+
+
+SCHEME
+ The project files are simple Scheme programs that is interpreted by a
+ built in Scheme interpreter. The Scheme interpreter is TinyScheme and
+ needs a Scheme program called init.scm to initialize itself. The search
+ path for init.scm is (in the following order)
+ /usr/local/gEDA-20060124/share/gerbv/scheme/share/gerbv/scheme/, the
+ directory with the executable gerbv, the directory gerbv was invoked
+ from and finally according to the environment variable
+ GERBV_SCHEMEINIT.
+
+
+TOOLS FILE
+ Not every Excellon drill file is self-sufficient. Some CADs produce
+ .drd files where tools are only referenced, but never defined (such as
+ what diameter of the tool is.) Eagle CAD is one of such CADs, and there
+ are more since many board houses require Tools files.
+
+ A Tools file is a plain text file which you create in an editor. Each
+ line of the file describes one tool (the name and the diameter, in
+ inches):
+
+ T01 0.024
+ T02 0.040
+ ...
+
+ These are the same tools (T01 etc.) that are used in the Drill file. A
+ standard practice with Eagle is to create an empty Tools file, run the
+ CAM processor, and the error report tells you which tools you "forgot".
+ Then you put these tools into the file and rerun the CAM processor.
+
+ You load a tool file by using the commandline switches -t or --tools.
+ The file can have any name you wish, but Eagle expects the file type to
+ be ".drl", so it makes sense to keep it this way. Some board houses are
+ still using CAM software from DOS era, so you may want to excercise
+ caution before going beyond the 8.3 naming convention.
+
+ When gerbv reads the Tools file it also checks that there are no dupli-
+ cate definitions of tools. This does happen from time to time as you
+ edit the file by hand, especially if you, during design, add or remove
+ parts from the board and then have to add new tools into the Tools
+ file. The duplicate tools are a very serious error which will stop
+ (HOLD) your board until you fix the Tools file and maybe the Excellon
+ file. gerbv will detect duplicate tools if they are present, and will
+ exit immediately to indicate such a fatal error in a very obvious way.
+ A message will also be printed to standard error.
+
+ If your Excellon file does not contain tool definitions then gerbv will
+ preconfigure the tools by deriving the diameter of the drill bit from
+ the tool number. This is probably not what you want, and you will see
+ warnings printed on the console.
+
+
+ENVIRONMENT
+ GERBV_SCHEMEINIT
+ Defines where the init.scm file is stored. Used by scheme inter-
+ preter, which is used by the project reader.
+
+
+AUTHOR
+ Stefan Petersen (spetm at users.sourceforge.net): Overall hacker and project leader
+ Andreas Andersson (e92_aan at e.kth.se): Drill file support and general hacking
+ Anders Eriksson (aenfaldor at users.sourceforge.net) : X and GTK+ ideas and hacking
+
+
+COPYRIGHT
+ Copyright �© 2001-2004 Stefan Petersen
+
+ This document can be freely redistributed according to the terms of the
+ GNU General Public License version 2.0
+
+
+
+Version Feb 8th, 2004 gerbv(1)
+</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-gerbv_pnp_readme.html b/docs/wiki/geda-gerbv_pnp_readme.html
new file mode 100644
index 0000000..ee4d44e
--- /dev/null
+++ b/docs/wiki/geda-gerbv_pnp_readme.html
@@ -0,0 +1,133 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="searching_for_parts_and_marking_them_on_screen_in_gerbv" id="searching_for_parts_and_marking_them_on_screen_in_gerbv">Searching for Parts and marking them on screen (in gerbv)</a></h1>
+<div class="level1">
+<pre class="code">Searching for Parts and marking them on screen (in gerbv)
+
+THIS FUNCTIONALITY IS ONLY AVAILABLE WHEN COMPILING GERBV AGAINST GTK2!
+
+Please direct any comments, suggestions etc. to Juergen <juergenhaas@xxxxxxx>
+=============================================================================
+*** Support for Pick and Place files: ***
+*** csv-style files with/without quotes ***
+*** the following delimiters are supported ';' ':' '|' ',' ***
+----------------------------------------------------------------------------
+
+
+----------------------------------------------------------------------------
+A pick and place file has 11 columns (the first two lines a file in gerbv/examplei
+are shown here) and looks like this:
+
+Designator:Footprint:Mid X:Mid Y:Ref X:Ref Y:Pad X:Pad Y:Layer:Rotation:Comment
+
+R29:0805_REFL:25.4mm:72.644mm:25.4mm:72.644mm:25.4mm:71.6788mm:T:90.00:1K/1%
+----------------------------------------------------------------------------
+
+Some instructions for the first time user:
+
+after loading a PNP file a new dialog will come up offering various option of
+selecting and graphically marking electronic parts.
+
+Three modes of selecting items do exist:
+1)enter any search phrase and hit enter
+ (See also paragraph "SCROLLING" further down)
+ -Generally under linux regexp expressions are used such as ".*" i.e. '*'
+ -All matches will be marked in the list AND on the screen
+ -if you press ESC or press <ENTER> on an empty line it will deselect all
+ items
+ -if you had a selection already and you would like to add single items
+ one by one, just hold down CTRL key while you left-click on the desired
+ fields
+
+2)just simply use left click combined with Shift and/or CTRL for manual
+ mouse driven selections
+ Pressing right button of mouse will not only select but also draw item on
+ selected layer
+
+3)if you have pressed <ENTER> on an empty phrase you first of all will deselect
+ anything which was selected and you can then enter the so-called "assembly
+ mode" by left clicking on an item and afterwards pressing space as often as
+ desired, while the select parts dialog is active. The selection will move
+ down the list one by one displaying the selected part in the window
+ automatically (with the corresponding layer being active).
+
+ Alternatively 1:
+ If you had more than one item selected and you did not clear the selections list
+ by <ENTER> on an empty phrase, only the first item will be taken into account
+ and all others will be deselected.
+
+ Alternatively 2:
+ You can of course also select an item by clicking on it, pressing space will
+ then proceed as described
+
+ This mode also features arrows Up/Down selection, where arrow Up will reverse
+ the action of arrow Down/Spacebar. Furthermore, holding SHIFT while pressing
+ arrow Up/Down will increase the selection in either direction
+-------------------------
+More Features:
+
+4)Inversion of selection:
+ pressing this button at any given time inverts the selection concerning the
+ whole list and upon clicking Mark button this new selection will be drawn
+ onto screen.
+
+
+5)Top/bottom selection
+ General: press mark to mark selections on screen, after choosing to select
+ top or bottom parts.
+
+ a)in existing selection will only remove non wanted items
+ (e.g. all bottom parts if you press "top parts") from selection
+
+ b)if there is no selection, all top or all bottoms parts are selected
+
+
+6)Choose available layers for marking selected parts from drop-down list
+ HINT: if pick and place file is loaded last, already occupied layers
+ will not be in the drop-down list
+
+-------------------------------------------------------------------
+Hint 1:
+right click functionality to know Part description.
+After you have graphically marked a number of parts (say all resistors) you can
+right click onto a part which is selected in the scroll-down list of available
+parts in the search dialog.
+Its designator, comment and footprint are then shown in the statusbar and in the log window.
+This comes in handy if there are many parts you want to look at, but e.g. you already
+know a fault has occurred only on one side of the board.
+
+-------------------------------------------------------------------
+Hint 2:
+SCROLLING (in the dialog window)
+ Scrolling generally only occurs, if search for comments is not activated AND
+ also whenever enter is hit the list will bescrolled to the first hit,
+ regardless of the search mode.
+ The use of BackSpace is supported.
+ If you decide to select an entry from the list of completions offered, then the
+ scrolling will only occur once you press enter.
+
+Example:
+ imagine you are looking for an element labelled EU3:
+ If you hit the first key (E) to enter a search phrase in the entry field, the
+ list will be scrolled to the first element matching this key (E), also entering
+ a subsequent key (U) will then further refine that and scroll to the first
+ element with EU etc.
+====================================================================</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-gfdl.html b/docs/wiki/geda-gfdl.html
new file mode 100644
index 0000000..92b2690
--- /dev/null
+++ b/docs/wiki/geda-gfdl.html
@@ -0,0 +1,420 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="gnu_free_documentation_license" id="gnu_free_documentation_license">GNU Free Documentation License</a></h1>
+<div class="level1">
+<pre class="code"> GNU Free Documentation License
+ Version 1.2, November 2002
+
+
+ Copyright (C) 2000,2001,2002 Free Software Foundation, Inc.
+ 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+
+0. PREAMBLE
+
+The purpose of this License is to make a manual, textbook, or other
+functional and useful document "free" in the sense of freedom: to
+assure everyone the effective freedom to copy and redistribute it,
+with or without modifying it, either commercially or noncommercially.
+Secondarily, this License preserves for the author and publisher a way
+to get credit for their work, while not being considered responsible
+for modifications made by others.
+
+This License is a kind of "copyleft", which means that derivative
+works of the document must themselves be free in the same sense. It
+complements the GNU General Public License, which is a copyleft
+license designed for free software.
+
+We have designed this License in order to use it for manuals for free
+software, because free software needs free documentation: a free
+program should come with manuals providing the same freedoms that the
+software does. But this License is not limited to software manuals;
+it can be used for any textual work, regardless of subject matter or
+whether it is published as a printed book. We recommend this License
+principally for works whose purpose is instruction or reference.
+
+
+1. APPLICABILITY AND DEFINITIONS
+
+This License applies to any manual or other work, in any medium, that
+contains a notice placed by the copyright holder saying it can be
+distributed under the terms of this License. Such a notice grants a
+world-wide, royalty-free license, unlimited in duration, to use that
+work under the conditions stated herein. The "Document", below,
+refers to any such manual or work. Any member of the public is a
+licensee, and is addressed as "you". You accept the license if you
+copy, modify or distribute the work in a way requiring permission
+under copyright law.
+
+A "Modified Version" of the Document means any work containing the
+Document or a portion of it, either copied verbatim, or with
+modifications and/or translated into another language.
+
+A "Secondary Section" is a named appendix or a front-matter section of
+the Document that deals exclusively with the relationship of the
+publishers or authors of the Document to the Document's overall subject
+(or to related matters) and contains nothing that could fall directly
+within that overall subject. (Thus, if the Document is in part a
+textbook of mathematics, a Secondary Section may not explain any
+mathematics.) The relationship could be a matter of historical
+connection with the subject or with related matters, or of legal,
+commercial, philosophical, ethical or political position regarding
+them.
+
+The "Invariant Sections" are certain Secondary Sections whose titles
+are designated, as being those of Invariant Sections, in the notice
+that says that the Document is released under this License. If a
+section does not fit the above definition of Secondary then it is not
+allowed to be designated as Invariant. The Document may contain zero
+Invariant Sections. If the Document does not identify any Invariant
+Sections then there are none.
+
+The "Cover Texts" are certain short passages of text that are listed,
+as Front-Cover Texts or Back-Cover Texts, in the notice that says that
+the Document is released under this License. A Front-Cover Text may
+be at most 5 words, and a Back-Cover Text may be at most 25 words.
+
+A "Transparent" copy of the Document means a machine-readable copy,
+represented in a format whose specification is available to the
+general public, that is suitable for revising the document
+straightforwardly with generic text editors or (for images composed of
+pixels) generic paint programs or (for drawings) some widely available
+drawing editor, and that is suitable for input to text formatters or
+for automatic translation to a variety of formats suitable for input
+to text formatters. A copy made in an otherwise Transparent file
+format whose markup, or absence of markup, has been arranged to thwart
+or discourage subsequent modification by readers is not Transparent.
+An image format is not Transparent if used for any substantial amount
+of text. A copy that is not "Transparent" is called "Opaque".
+
+Examples of suitable formats for Transparent copies include plain
+ASCII without markup, Texinfo input format, LaTeX input format, SGML
+or XML using a publicly available DTD, and standard-conforming simple
+HTML, PostScript or PDF designed for human modification. Examples of
+transparent image formats include PNG, XCF and JPG. Opaque formats
+include proprietary formats that can be read and edited only by
+proprietary word processors, SGML or XML for which the DTD and/or
+processing tools are not generally available, and the
+machine-generated HTML, PostScript or PDF produced by some word
+processors for output purposes only.
+
+The "Title Page" means, for a printed book, the title page itself,
+plus such following pages as are needed to hold, legibly, the material
+this License requires to appear in the title page. For works in
+formats which do not have any title page as such, "Title Page" means
+the text near the most prominent appearance of the work's title,
+preceding the beginning of the body of the text.
+
+A section "Entitled XYZ" means a named subunit of the Document whose
+title either is precisely XYZ or contains XYZ in parentheses following
+text that translates XYZ in another language. (Here XYZ stands for a
+specific section name mentioned below, such as "Acknowledgements",
+"Dedications", "Endorsements", or "History".) To "Preserve the Title"
+of such a section when you modify the Document means that it remains a
+section "Entitled XYZ" according to this definition.
+
+The Document may include Warranty Disclaimers next to the notice which
+states that this License applies to the Document. These Warranty
+Disclaimers are considered to be included by reference in this
+License, but only as regards disclaiming warranties: any other
+implication that these Warranty Disclaimers may have is void and has
+no effect on the meaning of this License.
+
+
+2. VERBATIM COPYING
+
+You may copy and distribute the Document in any medium, either
+commercially or noncommercially, provided that this License, the
+copyright notices, and the license notice saying this License applies
+to the Document are reproduced in all copies, and that you add no other
+conditions whatsoever to those of this License. You may not use
+technical measures to obstruct or control the reading or further
+copying of the copies you make or distribute. However, you may accept
+compensation in exchange for copies. If you distribute a large enough
+number of copies you must also follow the conditions in section 3.
+
+You may also lend copies, under the same conditions stated above, and
+you may publicly display copies.
+
+
+3. COPYING IN QUANTITY
+
+If you publish printed copies (or copies in media that commonly have
+printed covers) of the Document, numbering more than 100, and the
+Document's license notice requires Cover Texts, you must enclose the
+copies in covers that carry, clearly and legibly, all these Cover
+Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on
+the back cover. Both covers must also clearly and legibly identify
+you as the publisher of these copies. The front cover must present
+the full title with all words of the title equally prominent and
+visible. You may add other material on the covers in addition.
+Copying with changes limited to the covers, as long as they preserve
+the title of the Document and satisfy these conditions, can be treated
+as verbatim copying in other respects.
+
+If the required texts for either cover are too voluminous to fit
+legibly, you should put the first ones listed (as many as fit
+reasonably) on the actual cover, and continue the rest onto adjacent
+pages.
+
+If you publish or distribute Opaque copies of the Document numbering
+more than 100, you must either include a machine-readable Transparent
+copy along with each Opaque copy, or state in or with each Opaque copy
+a computer-network location from which the general network-using
+public has access to download using public-standard network protocols
+a complete Transparent copy of the Document, free of added material.
+If you use the latter option, you must take reasonably prudent steps,
+when you begin distribution of Opaque copies in quantity, to ensure
+that this Transparent copy will remain thus accessible at the stated
+location until at least one year after the last time you distribute an
+Opaque copy (directly or through your agents or retailers) of that
+edition to the public.
+
+It is requested, but not required, that you contact the authors of the
+Document well before redistributing any large number of copies, to give
+them a chance to provide you with an updated version of the Document.
+
+
+4. MODIFICATIONS
+
+You may copy and distribute a Modified Version of the Document under
+the conditions of sections 2 and 3 above, provided that you release
+the Modified Version under precisely this License, with the Modified
+Version filling the role of the Document, thus licensing distribution
+and modification of the Modified Version to whoever possesses a copy
+of it. In addition, you must do these things in the Modified Version:
+
+A. Use in the Title Page (and on the covers, if any) a title distinct
+ from that of the Document, and from those of previous versions
+ (which should, if there were any, be listed in the History section
+ of the Document). You may use the same title as a previous version
+ if the original publisher of that version gives permission.
+B. List on the Title Page, as authors, one or more persons or entities
+ responsible for authorship of the modifications in the Modified
+ Version, together with at least five of the principal authors of the
+ Document (all of its principal authors, if it has fewer than five),
+ unless they release you from this requirement.
+C. State on the Title page the name of the publisher of the
+ Modified Version, as the publisher.
+D. Preserve all the copyright notices of the Document.
+E. Add an appropriate copyright notice for your modifications
+ adjacent to the other copyright notices.
+F. Include, immediately after the copyright notices, a license notice
+ giving the public permission to use the Modified Version under the
+ terms of this License, in the form shown in the Addendum below.
+G. Preserve in that license notice the full lists of Invariant Sections
+ and required Cover Texts given in the Document's license notice.
+H. Include an unaltered copy of this License.
+I. Preserve the section Entitled "History", Preserve its Title, and add
+ to it an item stating at least the title, year, new authors, and
+ publisher of the Modified Version as given on the Title Page. If
+ there is no section Entitled "History" in the Document, create one
+ stating the title, year, authors, and publisher of the Document as
+ given on its Title Page, then add an item describing the Modified
+ Version as stated in the previous sentence.
+J. Preserve the network location, if any, given in the Document for
+ public access to a Transparent copy of the Document, and likewise
+ the network locations given in the Document for previous versions
+ it was based on. These may be placed in the "History" section.
+ You may omit a network location for a work that was published at
+ least four years before the Document itself, or if the original
+ publisher of the version it refers to gives permission.
+K. For any section Entitled "Acknowledgements" or "Dedications",
+ Preserve the Title of the section, and preserve in the section all
+ the substance and tone of each of the contributor acknowledgements
+ and/or dedications given therein.
+L. Preserve all the Invariant Sections of the Document,
+ unaltered in their text and in their titles. Section numbers
+ or the equivalent are not considered part of the section titles.
+M. Delete any section Entitled "Endorsements". Such a section
+ may not be included in the Modified Version.
+N. Do not retitle any existing section to be Entitled "Endorsements"
+ or to conflict in title with any Invariant Section.
+O. Preserve any Warranty Disclaimers.
+
+If the Modified Version includes new front-matter sections or
+appendices that qualify as Secondary Sections and contain no material
+copied from the Document, you may at your option designate some or all
+of these sections as invariant. To do this, add their titles to the
+list of Invariant Sections in the Modified Version's license notice.
+These titles must be distinct from any other section titles.
+
+You may add a section Entitled "Endorsements", provided it contains
+nothing but endorsements of your Modified Version by various
+parties--for example, statements of peer review or that the text has
+been approved by an organization as the authoritative definition of a
+standard.
+
+You may add a passage of up to five words as a Front-Cover Text, and a
+passage of up to 25 words as a Back-Cover Text, to the end of the list
+of Cover Texts in the Modified Version. Only one passage of
+Front-Cover Text and one of Back-Cover Text may be added by (or
+through arrangements made by) any one entity. If the Document already
+includes a cover text for the same cover, previously added by you or
+by arrangement made by the same entity you are acting on behalf of,
+you may not add another; but you may replace the old one, on explicit
+permission from the previous publisher that added the old one.
+
+The author(s) and publisher(s) of the Document do not by this License
+give permission to use their names for publicity for or to assert or
+imply endorsement of any Modified Version.
+
+
+5. COMBINING DOCUMENTS
+
+You may combine the Document with other documents released under this
+License, under the terms defined in section 4 above for modified
+versions, provided that you include in the combination all of the
+Invariant Sections of all of the original documents, unmodified, and
+list them all as Invariant Sections of your combined work in its
+license notice, and that you preserve all their Warranty Disclaimers.
+
+The combined work need only contain one copy of this License, and
+multiple identical Invariant Sections may be replaced with a single
+copy. If there are multiple Invariant Sections with the same name but
+different contents, make the title of each such section unique by
+adding at the end of it, in parentheses, the name of the original
+author or publisher of that section if known, or else a unique number.
+Make the same adjustment to the section titles in the list of
+Invariant Sections in the license notice of the combined work.
+
+In the combination, you must combine any sections Entitled "History"
+in the various original documents, forming one section Entitled
+"History"; likewise combine any sections Entitled "Acknowledgements",
+and any sections Entitled "Dedications". You must delete all sections
+Entitled "Endorsements".
+
+
+6. COLLECTIONS OF DOCUMENTS
+
+You may make a collection consisting of the Document and other documents
+released under this License, and replace the individual copies of this
+License in the various documents with a single copy that is included in
+the collection, provided that you follow the rules of this License for
+verbatim copying of each of the documents in all other respects.
+
+You may extract a single document from such a collection, and distribute
+it individually under this License, provided you insert a copy of this
+License into the extracted document, and follow this License in all
+other respects regarding verbatim copying of that document.
+
+
+7. AGGREGATION WITH INDEPENDENT WORKS
+
+A compilation of the Document or its derivatives with other separate
+and independent documents or works, in or on a volume of a storage or
+distribution medium, is called an "aggregate" if the copyright
+resulting from the compilation is not used to limit the legal rights
+of the compilation's users beyond what the individual works permit.
+When the Document is included in an aggregate, this License does not
+apply to the other works in the aggregate which are not themselves
+derivative works of the Document.
+
+If the Cover Text requirement of section 3 is applicable to these
+copies of the Document, then if the Document is less than one half of
+the entire aggregate, the Document's Cover Texts may be placed on
+covers that bracket the Document within the aggregate, or the
+electronic equivalent of covers if the Document is in electronic form.
+Otherwise they must appear on printed covers that bracket the whole
+aggregate.
+
+
+8. TRANSLATION
+
+Translation is considered a kind of modification, so you may
+distribute translations of the Document under the terms of section 4.
+Replacing Invariant Sections with translations requires special
+permission from their copyright holders, but you may include
+translations of some or all Invariant Sections in addition to the
+original versions of these Invariant Sections. You may include a
+translation of this License, and all the license notices in the
+Document, and any Warranty Disclaimers, provided that you also include
+the original English version of this License and the original versions
+of those notices and disclaimers. In case of a disagreement between
+the translation and the original version of this License or a notice
+or disclaimer, the original version will prevail.
+
+If a section in the Document is Entitled "Acknowledgements",
+"Dedications", or "History", the requirement (section 4) to Preserve
+its Title (section 1) will typically require changing the actual
+title.
+
+
+9. TERMINATION
+
+You may not copy, modify, sublicense, or distribute the Document except
+as expressly provided for under this License. Any other attempt to
+copy, modify, sublicense or distribute the Document is void, and will
+automatically terminate your rights under this License. However,
+parties who have received copies, or rights, from you under this
+License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+
+10. FUTURE REVISIONS OF THIS LICENSE
+
+The Free Software Foundation may publish new, revised versions
+of the GNU Free Documentation License from time to time. Such new
+versions will be similar in spirit to the present version, but may
+differ in detail to address new problems or concerns. See
+http://www.gnu.org/copyleft/.
+
+Each version of the License is given a distinguishing version number.
+If the Document specifies that a particular numbered version of this
+License "or any later version" applies to it, you have the option of
+following the terms and conditions either of that specified version or
+of any later version that has been published (not as a draft) by the
+Free Software Foundation. If the Document does not specify a version
+number of this License, you may choose any version ever published (not
+as a draft) by the Free Software Foundation.
+
+
+ADDENDUM: How to use this License for your documents
+
+To use this License in a document you have written, include a copy of
+the License in the document and put the following copyright and
+license notices just after the title page:
+
+ Copyright (c) YEAR YOUR NAME.
+ Permission is granted to copy, distribute and/or modify this document
+ under the terms of the GNU Free Documentation License, Version 1.2
+ or any later version published by the Free Software Foundation;
+ with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
+ A copy of the license is included in the section entitled "GNU
+ Free Documentation License".
+
+If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts,
+replace the "with...Texts." line with this:
+
+ with the Invariant Sections being LIST THEIR TITLES, with the
+ Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.
+
+If you have Invariant Sections without Cover Texts, or some other
+combination of the three, merge those two alternatives to suit the
+situation.
+
+If your document contains nontrivial examples of program code, we
+recommend releasing these examples in parallel under your choice of
+free software license, such as the GNU General Public License,
+to permit their use in free software.
+</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-glossaire.fr.html b/docs/wiki/geda-glossaire.fr.html
new file mode 100644
index 0000000..28974b3
--- /dev/null
+++ b/docs/wiki/geda-glossaire.fr.html
@@ -0,0 +1,64 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="glossaire_des_termes_de_geda_et_des_eda" id="glossaire_des_termes_de_geda_et_des_eda">Glossaire des termes de gEDA (et des EDA)</a></h1>
+<div class="level1">
+
+<p>
+ La conception en électronique implique beaucoup de termes spécifiques. Quelques termes ont une signification qui ne ressemble que vaguement à leur utilisation dans la vie de tous les jours. Ce glossaire est destiné à devenir un dictionaire de termes spécifiques à la suite gEDA, de même que monde plus grand des CAO pour lâ??électronique. Malheureusement, il nâ??existe pas de méthode universelle de nommage des concepts dans le champ de la conception électronique. Le glossaire donnera des éléments sur la manière dont les choses sont appelées dans les autres suites de conception.
+</p>
+
+<p>
+<span class="hilited">(Aux auteurs du Wiki:Veuillez insérer les nouveaux termes dans lâ??ordre de lâ??alphabet)</span>
+</p>
+<ul>
+<li class="level1"><div class="li"> <strong>anneau annulaire (annular ring)</strong>: Lâ??anneau annulaire, quelque fois aussi appelé <strong>annulus</strong>, est un diamètre de cuivre qui doit être placé autour des trous métallisés comme les pastilles et les vias. La taille minimum de lâ??anneau annulaire est spécifié par les fabricants de pcb. Une spécification habituelle est de 16 mil plus large que le trou.</div>
+</li>
+<li class="level1"><div class="li"> <strong>empreinte (footprint)</strong>: Le dessin de métal et de silkscreen qui définit où vous placez un composant sur un circuit. Les empreintes sont disposées par lâ??utilisateur sur le circuit imprimé lors de la phase de « placement » (en utilisant i.e. lâ??outil open-source PCB). Une empreinte est aussi quelque fois appelée un « decal » (PADS) ou un « land-pattern ».</div>
+</li>
+<li class="level1"><div class="li"> <strong>flux de conception (design flow)</strong>: Lâ??ordre des étapes dans lequel vous faites progresser votre étude depuis le concept initial, par la saisie de schéma, lâ??ajout dâ??attribut, le netlisting et le circuit imprimé. On utilisera typiquement plusieurs outils pour accomplir différentes tâches pendant la réalisation. La Suite gEDA utilise des programmes entièrement séparés pour les différents étapes du cheminement; chaque outil de la suite lit le fichier de sortie produit par lâ??outil précédent et écrit un fichier pouvant être lu par lâ??outil suivant dans la chaîne. Le flux de conception de gEDA pour réaliser un PCB est illustré <a href="http://geda.seul.org/dokuwiki/doku.php?id=geda:usage#what_does_the_design_flow_in_geda_look_like"; class="urlextern" title="http://geda.seul.org/dokuwiki/doku.php?id=geda:usage#what_does_the_design_flow_in_geda_look_like"; rel="nofollow">ici</a>. Notez que le flux du cheminement pour des tâches différentes peut varier. Par exemple, si votre but est de simuler votre circuit, vous utiliserez un flux différent de celui montré dans le lien ci-dessus. Finalement, les autres outils de conception de PCB â?? habituellement plus simples â?? utilisent une approche monolithique dans laquelle un seul programme (albeit avec différents modes dâ??édition) est utilisé pour réaliser le montage complet. Déterminer la meilleure approche est plus une affaire de croyance personnelle.</div>
+</li>
+<li class="level1"><div class="li"> <strong>net</strong>: Un net est la représentation dâ??un fil ou dâ??une connexion électrique dans un schéma. Câ??est, basiquement, une ligne connectant deux broches de symbole. Le terme « net » est aussi quelque fois utilisé pour parler dâ??une connexion électrique (via une fil ou une piste de PCB) dans un circuit réel. Quelques outils de saisie de schéma appellent un net un « fil ».</div>
+</li>
+<li class="level1"><div class="li"> <strong>netlist</strong>: Une netlist est une représentation en fichier texte de votre circuit qui souligne les connexions entre les différents éléments du circuit, peut être indépendants des boîtiers physiques constituants les composants réels du circuit.</div>
+</li>
+<li class="level1"><div class="li"> <strong>pad</strong>: Une pastille est une zone de cuivre sur lequel un SMD sera soudé. Bien que les pastilles soient habituellement carrées, elles peuvent aussi être rondes.</div>
+</li>
+<li class="level1"><div class="li"> <strong>pin</strong>: Une patte/broche est un trou dans un circuit imprimé qui permet de connecter un composant câblé. Dans plusieurs cas, le trou est rempli de cuivre par le fabricant.</div>
+</li>
+<li class="level1"><div class="li"> <strong>pcb</strong>: Dans le contexte de gEDA, cet acronyme a deux significations distinctes:</div>
+<ol>
+<li class="level2"><div class="li"> Un abbréviation de « printed circuit board ». Câ??est la partie qui est utilisée pour connecter les composants électroniques. Elle est aussi quelque fois appelée une « carte de câblage imprimée » (PWB), bien que cette utilisation ait été abandonné.</div>
+</li>
+<li class="level2"><div class="li"> Un puissant outil open-source, utilisé pour concevoir la disposition dâ??un circuit imprimé. La sortie des outils de gaf peut être utilisée comme entrée à pcb. (<a href="http://pcb.sourceforge.net/index.html"; class="urlextern" title="http://pcb.sourceforge.net/index.html"; rel="nofollow">page d'accueil de pcb</a>)</div>
+</li>
+</ol>
+</li>
+<li class="level1"><div class="li"> <strong>rats nest</strong>: Les lignes dessinées sur la zone de travail du circuit, qui relient les pastilles devant encore être connectées avec des pistes. Contrairement aux pistes réelles, les rats nest sont des lignes droites. Si plusieurs pastilles sont impliquées dans un net, pcb tente de dessiner les rats nests avec les longueurs les plus courtes possibles.</div>
+</li>
+<li class="level1"><div class="li"> <strong>refdes</strong>: Raccourci pour « reference designator » (numéro de référence). Le numéro de référence (ou nom) dâ??un composant. Les outils gEDA se réfèrent aux refdes pour organiser les composants en internes. Câ??est la raison pour laquelle, pour une création réussie de circuit imprimé, chaque composant doit être lié avec un refdes. Habituellement, le refdes consiste quelques majuscules et un chiffre. Exemples: R1, R2, U115, CONN3. (Protel: « Designator »)</div>
+</li>
+<li class="level1"><div class="li"> <strong>slot</strong>: Quelques composants contiennent de multiples parties identiques à lâ??intérieur dâ??un boîtier. Les IO (Input/output, entrées/sorties) pour chaque partie sont disposées pour différents jeux de broches sur le boîtier. Un exemple classique est la quadruple porte NAND TTL 7400. Gschem (comme dâ??autres paquets de saisie de schéma) traite ce type de composant en vous permettant de dessiner quatre symboles NAND séparés et de sélectionner ensuite quel « slot » devrait avoir chaque symbole en attachant un attribut de slot au symbole. Dans lâ??exemple du quadruple NAND 7400, vous sélectionneriez « <code>slot=1</code> » pour la première apparition du symbole, slot=2 pour la seconde et ainsi de suite. Notez que dans gschem, vous nâ??avez besoin dâ??attacher les liaisons dâ??alimentation à un composant en slot quâ??une seule fois. (Les autres programme de saisie de schéma comme Orcad vous demandent dâ??attacher les liaisons communes â?? comme lâ??alimentation â?? sur chaque instantiation du symbole en slot.)</div>
+</li>
+<li class="level1"><div class="li"> <strong>symbole</strong>: Un symbole est la représentation dâ??un composant particulier dans votre schéma. Les exemples classiques sont les lignes en zig-zag pour les résistances (dans lâ??utilisation US néanmoins) ou un triangle pour un ampli opérationnel. En utilisant un programme de saisie de schémas (i.e. gschem), vous placez les symboles sur votre carte et alors les câbler pour créer une représentation de votre circuit.</div>
+</li>
+<li class="level1"><div class="li"> <strong>via</strong>: Un via est un trou métallisé qui qui est destiné à connecter électriquement des différentes couches du circuit imprimé. Habituellement, les vias sont aussi petits que possible pour sauvegarder de la place sur le le pcb.</div>
+</li>
+</ul>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-glossary.fr.html b/docs/wiki/geda-glossary.fr.html
new file mode 100644
index 0000000..28974b3
--- /dev/null
+++ b/docs/wiki/geda-glossary.fr.html
@@ -0,0 +1,64 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="glossaire_des_termes_de_geda_et_des_eda" id="glossaire_des_termes_de_geda_et_des_eda">Glossaire des termes de gEDA (et des EDA)</a></h1>
+<div class="level1">
+
+<p>
+ La conception en électronique implique beaucoup de termes spécifiques. Quelques termes ont une signification qui ne ressemble que vaguement à leur utilisation dans la vie de tous les jours. Ce glossaire est destiné à devenir un dictionaire de termes spécifiques à la suite gEDA, de même que monde plus grand des CAO pour lâ??électronique. Malheureusement, il nâ??existe pas de méthode universelle de nommage des concepts dans le champ de la conception électronique. Le glossaire donnera des éléments sur la manière dont les choses sont appelées dans les autres suites de conception.
+</p>
+
+<p>
+<span class="hilited">(Aux auteurs du Wiki:Veuillez insérer les nouveaux termes dans lâ??ordre de lâ??alphabet)</span>
+</p>
+<ul>
+<li class="level1"><div class="li"> <strong>anneau annulaire (annular ring)</strong>: Lâ??anneau annulaire, quelque fois aussi appelé <strong>annulus</strong>, est un diamètre de cuivre qui doit être placé autour des trous métallisés comme les pastilles et les vias. La taille minimum de lâ??anneau annulaire est spécifié par les fabricants de pcb. Une spécification habituelle est de 16 mil plus large que le trou.</div>
+</li>
+<li class="level1"><div class="li"> <strong>empreinte (footprint)</strong>: Le dessin de métal et de silkscreen qui définit où vous placez un composant sur un circuit. Les empreintes sont disposées par lâ??utilisateur sur le circuit imprimé lors de la phase de « placement » (en utilisant i.e. lâ??outil open-source PCB). Une empreinte est aussi quelque fois appelée un « decal » (PADS) ou un « land-pattern ».</div>
+</li>
+<li class="level1"><div class="li"> <strong>flux de conception (design flow)</strong>: Lâ??ordre des étapes dans lequel vous faites progresser votre étude depuis le concept initial, par la saisie de schéma, lâ??ajout dâ??attribut, le netlisting et le circuit imprimé. On utilisera typiquement plusieurs outils pour accomplir différentes tâches pendant la réalisation. La Suite gEDA utilise des programmes entièrement séparés pour les différents étapes du cheminement; chaque outil de la suite lit le fichier de sortie produit par lâ??outil précédent et écrit un fichier pouvant être lu par lâ??outil suivant dans la chaîne. Le flux de conception de gEDA pour réaliser un PCB est illustré <a href="http://geda.seul.org/dokuwiki/doku.php?id=geda:usage#what_does_the_design_flow_in_geda_look_like"; class="urlextern" title="http://geda.seul.org/dokuwiki/doku.php?id=geda:usage#what_does_the_design_flow_in_geda_look_like"; rel="nofollow">ici</a>. Notez que le flux du cheminement pour des tâches différentes peut varier. Par exemple, si votre but est de simuler votre circuit, vous utiliserez un flux différent de celui montré dans le lien ci-dessus. Finalement, les autres outils de conception de PCB â?? habituellement plus simples â?? utilisent une approche monolithique dans laquelle un seul programme (albeit avec différents modes dâ??édition) est utilisé pour réaliser le montage complet. Déterminer la meilleure approche est plus une affaire de croyance personnelle.</div>
+</li>
+<li class="level1"><div class="li"> <strong>net</strong>: Un net est la représentation dâ??un fil ou dâ??une connexion électrique dans un schéma. Câ??est, basiquement, une ligne connectant deux broches de symbole. Le terme « net » est aussi quelque fois utilisé pour parler dâ??une connexion électrique (via une fil ou une piste de PCB) dans un circuit réel. Quelques outils de saisie de schéma appellent un net un « fil ».</div>
+</li>
+<li class="level1"><div class="li"> <strong>netlist</strong>: Une netlist est une représentation en fichier texte de votre circuit qui souligne les connexions entre les différents éléments du circuit, peut être indépendants des boîtiers physiques constituants les composants réels du circuit.</div>
+</li>
+<li class="level1"><div class="li"> <strong>pad</strong>: Une pastille est une zone de cuivre sur lequel un SMD sera soudé. Bien que les pastilles soient habituellement carrées, elles peuvent aussi être rondes.</div>
+</li>
+<li class="level1"><div class="li"> <strong>pin</strong>: Une patte/broche est un trou dans un circuit imprimé qui permet de connecter un composant câblé. Dans plusieurs cas, le trou est rempli de cuivre par le fabricant.</div>
+</li>
+<li class="level1"><div class="li"> <strong>pcb</strong>: Dans le contexte de gEDA, cet acronyme a deux significations distinctes:</div>
+<ol>
+<li class="level2"><div class="li"> Un abbréviation de « printed circuit board ». Câ??est la partie qui est utilisée pour connecter les composants électroniques. Elle est aussi quelque fois appelée une « carte de câblage imprimée » (PWB), bien que cette utilisation ait été abandonné.</div>
+</li>
+<li class="level2"><div class="li"> Un puissant outil open-source, utilisé pour concevoir la disposition dâ??un circuit imprimé. La sortie des outils de gaf peut être utilisée comme entrée à pcb. (<a href="http://pcb.sourceforge.net/index.html"; class="urlextern" title="http://pcb.sourceforge.net/index.html"; rel="nofollow">page d'accueil de pcb</a>)</div>
+</li>
+</ol>
+</li>
+<li class="level1"><div class="li"> <strong>rats nest</strong>: Les lignes dessinées sur la zone de travail du circuit, qui relient les pastilles devant encore être connectées avec des pistes. Contrairement aux pistes réelles, les rats nest sont des lignes droites. Si plusieurs pastilles sont impliquées dans un net, pcb tente de dessiner les rats nests avec les longueurs les plus courtes possibles.</div>
+</li>
+<li class="level1"><div class="li"> <strong>refdes</strong>: Raccourci pour « reference designator » (numéro de référence). Le numéro de référence (ou nom) dâ??un composant. Les outils gEDA se réfèrent aux refdes pour organiser les composants en internes. Câ??est la raison pour laquelle, pour une création réussie de circuit imprimé, chaque composant doit être lié avec un refdes. Habituellement, le refdes consiste quelques majuscules et un chiffre. Exemples: R1, R2, U115, CONN3. (Protel: « Designator »)</div>
+</li>
+<li class="level1"><div class="li"> <strong>slot</strong>: Quelques composants contiennent de multiples parties identiques à lâ??intérieur dâ??un boîtier. Les IO (Input/output, entrées/sorties) pour chaque partie sont disposées pour différents jeux de broches sur le boîtier. Un exemple classique est la quadruple porte NAND TTL 7400. Gschem (comme dâ??autres paquets de saisie de schéma) traite ce type de composant en vous permettant de dessiner quatre symboles NAND séparés et de sélectionner ensuite quel « slot » devrait avoir chaque symbole en attachant un attribut de slot au symbole. Dans lâ??exemple du quadruple NAND 7400, vous sélectionneriez « <code>slot=1</code> » pour la première apparition du symbole, slot=2 pour la seconde et ainsi de suite. Notez que dans gschem, vous nâ??avez besoin dâ??attacher les liaisons dâ??alimentation à un composant en slot quâ??une seule fois. (Les autres programme de saisie de schéma comme Orcad vous demandent dâ??attacher les liaisons communes â?? comme lâ??alimentation â?? sur chaque instantiation du symbole en slot.)</div>
+</li>
+<li class="level1"><div class="li"> <strong>symbole</strong>: Un symbole est la représentation dâ??un composant particulier dans votre schéma. Les exemples classiques sont les lignes en zig-zag pour les résistances (dans lâ??utilisation US néanmoins) ou un triangle pour un ampli opérationnel. En utilisant un programme de saisie de schémas (i.e. gschem), vous placez les symboles sur votre carte et alors les câbler pour créer une représentation de votre circuit.</div>
+</li>
+<li class="level1"><div class="li"> <strong>via</strong>: Un via est un trou métallisé qui qui est destiné à connecter électriquement des différentes couches du circuit imprimé. Habituellement, les vias sont aussi petits que possible pour sauvegarder de la place sur le le pcb.</div>
+</li>
+</ul>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-glossary.html b/docs/wiki/geda-glossary.html
new file mode 100644
index 0000000..04218e3
--- /dev/null
+++ b/docs/wiki/geda-glossary.html
@@ -0,0 +1,78 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="glossary_of_geda_and_eda_terms" id="glossary_of_geda_and_eda_terms">Glossary of gEDA (and EDA) terms</a></h1>
+<div class="level1">
+
+<p>
+ The design of electronics involves a host of specific terms. Some words have a meaning that only vaguely resembles the use in everyday life. This glossary aims to be a dictionary of terms specific to the gEDA suite, as well as to the larger world of CAD for electronics. Unfortunately, there is no universal naming scheme for concepts in the area of electronic design. The glossary will give hints on how things are called in other design suites.
+</p>
+
+<p>
+<span class="hilited">(Wiki-authors: Please insert new terms according to the alphabet)</span>
+</p>
+<ul>
+<li class="level1"><div class="li"> <strong>annular ring</strong>: The annular ring, sometimes also called <strong>annulus</strong>, is a diameter of copper that needs to be placed arround metalized holes like pads and vias. The minimum size of the annular ring is specified by the pcb-fab. A common requirements is 16 mil larger than the hole.</div>
+</li>
+<li class="level1"><div class="li"> <strong>dead copper</strong>: A part of the copper layer which is not connected to any net defined in the netlist. By definition, this may be any object pcb defines. However, the term commonly refers to unconnected snippets of a polygon which is divided by a track. </div>
+</li>
+<li class="level1"><div class="li"> <strong>design flow</strong>: The order or stages through which you take your design as you progress from initial concept, through schematic capture, attribute attachment, netlisting, and layout. The gEDA Suite uses entirely separate programs for different stages of the flow; each tool in the suite reads the output file produced by the previous tool, and writes a file to be read by the next tool in the flow. The gEDA design flow for designing a PCB is illustrated <a href="http://geda.seul.org/wiki/geda:usage#what_does_the_design_flow_in_geda_look_like"; class="urlextern" title="http://geda.seul.org/wiki/geda:usage#what_does_the_design_flow_in_geda_look_like"; rel="nofollow">here</a>. Note that the design flow for different tasks might look different. For example, if your goal is to simulate your circuit, you will use a different flow than that shown in the link above.</div>
+</li>
+<li class="level1"><div class="li"> <strong>footprint</strong>: The pattern of metal and silkscreen which defines where you place a component on a PCB. Footprints are the placed by the user onto the PC board during the â??placementâ?? phase of PCB layout (using e.g. the open-source tool PCB). A footprint is also sometimes called called a â??decalâ?? (PADS), or a â??land-patternâ??.</div>
+</li>
+<li class="level1"><div class="li"> <strong>GTK-HID</strong>: The GTK version of the pcb user interface. â??HIDâ?? is an acronym for â??human interface deviceâ??. As the name sugests, GTK-HID uses the GTK+ widgetset and tries to comply with GTK usability standards.This is the default <acronym title="Graphical User Interface">GUI</acronym> of pcb. Menu and keyboard configuration is read from gpcb-menu.res. (See Lesstif-HID for an alternative)</div>
+</li>
+<li class="level1"><div class="li"> <strong>Lesstif-HID</strong>: The Lesstif version of the pcb user interface. It uses the Lesstif widgetset, which is the open source version of Motif. Menu and keyboard configuration read from <code>pcb-menu.res</code> try to comply with Lesstif usability standards. If you want to give this interface a try, you have to give the option <code>–with-gui=lesstif</code> at compile time.</div>
+</li>
+<li class="level1"><div class="li"> <strong>net</strong>: A net is the representation of a wire, or electrical connection in your schematic diagram. It is basically a line connecting two symbol pins. The term â??netâ?? is also sometimes used loosely to talk about an electrical connection (via a wire or PCB trace) in a real circuit. Some schematic capture tools call a net a â??wireâ??.</div>
+</li>
+<li class="level1"><div class="li"> <strong>netlist</strong>: A netlist is an text file representation of your circuit which emphasizes the connections between the different circuit elements, perhaps independently of the physical packages constituting the actual components in the circuit.</div>
+</li>
+<li class="level1"><div class="li"> <strong>pad</strong>: A pad is the patch of copper to which a SMD-component is to be soldered. Although pads are usually square, they can also be rounded.</div>
+</li>
+<li class="level1"><div class="li"> <strong>pin</strong>: A pin is a hole in the printed circuit that allows to connect a wired component. In many cases the hole is clad with copper by the pcb-fab. Also called a â??thru-holeâ??.</div>
+</li>
+<li class="level1"><div class="li"> <strong>pcb</strong>: In the context of gEDA this acronym has two distict meanings:</div>
+<ol>
+<li class="level2"><div class="li"> An abbreviation of â??printed circuit boardâ??. This is the actual hardware that is used to connect electronic components. It is also sometimes called a â??printed wiring boardâ?? (PWB), although this usage may be dying out.</div>
+</li>
+<li class="level2"><div class="li"> A powerful, open-source tool used to design the layout of a printed circuit board. The output of the gaf tools can be used as an input to pcb.(<a href="http://pcb.sourceforge.net/index.html"; class="urlextern" title="http://pcb.sourceforge.net/index.html"; rel="nofollow">homepage of pcb</a>)</div>
+</li>
+</ol>
+</li>
+<li class="level1"><div class="li"> <strong>rats nest</strong>: The lines drawn on the pcb working area that hint which pads still need to be connected with tracks. Unlike the actual tracks the rats nest are straight lines. If multiple pads are involved in a net, pcb tries to draw rats nests with the shortest possible length.</div>
+</li>
+<li class="level1"><div class="li"> <strong>refdes</strong>: Short for â??reference designatorâ??. The unique designator (or name) of a component. The gEDA tools rely on the refdefs to organize the components internally. Therefore, for successful creation of a printed circuit board every component has to be linked with a refdes. Usually, the refdes consists of a few upper case letters and a digit. Examples: R1, R2, U115, CONN3. (Protel: â??Designatorâ??)(<a href="http://en.wikipedia.org/wiki/reference_designator"; class="urlextern" title="http://en.wikipedia.org/wiki/reference_designator"; rel="nofollow"> Wikipedia: reference designator</a>)</div>
+</li>
+<li class="level1"><div class="li"> <strong>silkscreen</strong>: This is the layer that defines the text and graphics printed on the pcb board. It usually contains the name of the board, outlines of the components and possibly their values or refdes. The origin of the name is the silk traditionally used during the print process. </div>
+</li>
+<li class="level1"><div class="li"> <strong>slot</strong>: Some components contain multiple, identical devices inside a single package. The IOs for each component are mapped to different pin sets on the package. A classic example is the TTL 7400 quad nand gate. Gschem (like other schematic capture packages) handles this type of component by allowing you to draw four separate nand gate symbols, and then selecting which <strong>slot</strong> each symbol should have by attaching a slot attribute to the symbol. In the example of the 7400 quad nand, you would select <strong><code>slot=1</code></strong> for the first appearance of the symbol, slot=2 for the second appearance, and so on. Note that in gschem you need to attach power nets to a slotted component only <strong>once</strong>. (Other schematic capture programs like Orcad require you to attach common nets â?? like power nets â?? on each instantiation of the slotted symbol.)</div>
+</li>
+<li class="level1"><div class="li"> <strong>solder layer</strong>: This is the side of the board where traditional, thru hole components are soldered. (Protel: â??Bottom Layerâ??)</div>
+</li>
+<li class="level1"><div class="li"> <strong>symbol</strong>: A symbol is the representation of a particular component in your schematic diagram. The classic examples are squiggley lines for resistors (in US usage anyway), or a triangle for an op-amp. Using a schematic capture program (e.g. gschem) you place symbols on your board, and then wire them up to create a representation of your circuit.</div>
+</li>
+<li class="level1"><div class="li"> <strong>component layer</strong>: This is the side of the board where traditional, thru hole components sit, Usually the top side of the board. (Protel: â??Top Layerâ??)</div>
+</li>
+<li class="level1"><div class="li"> <strong>thermal</strong>, short for <a href="http://en.wikipedia.org/wiki/Thermal_relief_pad"; class="urlextern" title="http://en.wikipedia.org/wiki/Thermal_relief_pad"; rel="nofollow"> thermal relief pad</a>: A thermal is a way to connect a via with a copper plane through narrow bridges. The aim is to connect electrically, but provide enough thermal resistance to allow for convenient soldering. There is a special mode in pcb to convert the annular ring of vias into thermals. (However, vias never need thermals, since they are never soldered – only thru-holes need vias).</div>
+</li>
+<li class="level1"><div class="li"> <strong>via</strong>: A via is a metalized hole that is meant to electrically connect different layers of the pcb. Usually, vias are as small as possible to save valuable real estate on the pcb. A via is made the same way as a thru-hole, but since no pin will be pushed through, itâ??s OK for the metal to completely fill the hole (â??filledâ??) and for the solder mask to completely cover the hole (â??tentedâ??).</div>
+</li>
+</ul>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-gnetlist_mp.html b/docs/wiki/geda-gnetlist_mp.html
new file mode 100644
index 0000000..2bcadf5
--- /dev/null
+++ b/docs/wiki/geda-gnetlist_mp.html
@@ -0,0 +1,230 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="gnetlist_man-page" id="gnetlist_man-page">gnetlist man-page</a></h1>
+<div class="level1">
+<pre class="code">gnetlist(1) 20031231 gnetlist(1)
+
+
+
+NAME
+ gnetlist - gEDA/gaf Netlist extraction/generation
+
+SYNOPSIS
+ gnetlist [-i] [-I] [-q] [-s] [-v] [-l schem_file] [-m schem_file ] [-g
+ guile_procedure] [-c scheme_string ] [-o output_filename] schematic1
+ [... schematicN]
+
+DESCRIPTION
+ gnetlist is the netlist extraction/generation program which is part
+ gEDA (GPL Electronic Design Automation) toolset. This program takes a
+ schematic for its input and outputs a netlist.
+
+ gnetlist depends heavily on guile (a scheme based scripting language).
+ It uses guile to define the output format. Basically gnetlist reads a
+ schematic, creates an internal representation of the various connec-
+ tions, and then a guile script extracts the connections into some
+ netlist format.
+
+ gnetlist is very much so a work in progress. Currently it supports the
+ following backends:
+
+ 1) Allegro netlist format (-g allegro)
+
+ 2) BAE netlist format (-g bae)
+
+ 3) BOM / BOM2 - Bill of Materials (-g bom and -g bom2)
+
+ 4) Partslist 1,2,3 - More Bill of Materials (-g partslist[1-3])
+
+ 5) DRC - Start of a design rule checker (-g drc)
+
+ 6) DRC2 - A second design rule checker (-g drc2)
+
+ 7) gEDA - native format, mainly used for testing (-g geda)
+
+ 8) Gossip netlist format (-g gossip)
+
+ 9) PADS netlist format (-g pads)
+
+ 10) PCB / PCBboard (-g PCB and -g PCBboard)
+
+ 11) gsch2pcb backend (-g gsch2pcb)
+
+ 12) ProtelII netlist format (-g protelII)
+
+ 13) Spice compatible netlist format (-g spice)
+
+ 14) Enhanced spice compatible netlist format (-g spice-sdb)
+
+ 15) Switcap netlist format (-g switcap)
+
+ 16) Tango netlist format (-g tango)
+
+ 17) Verilog code (-g verilog)
+
+ 18) VHDL code (-g vhdl)
+
+ 19) VIPEC netlist format (-g vipec)
+
+ 20) Bartels Autoengineer netlist format (-g bae)
+
+ 21) GOSSIP system simulation system netlist format (-g gossip)
+
+ 22) MAXASCII netlist format (-g maxascii)
+
+ 23) VHDL-AMS netlist format (-g vams)
+
+ 24) Futurenet2 netlist format (-g futurenet2 )
+
+ 25) SWITCAP switched capacitor simulator netlist format (-g
+ switcap )
+
+ 26) RF Cascade netlist format (-g cascade )
+
+ 27) RACAL-REDAC netlist format (-g redac )
+
+ 28) PCB actions file for forward annotating pin/pad names from
+ schematic to layout (-g pcbpins)
+
+
+ For more info on these formats please look at the README.*
+
+ Please read the official (non-existant) documentation on how to use
+ gnetlist, since this man page just describes the command line arguments
+ and a few examples on how to run gnetlist.
+
+
+OPTIONS
+ gnelist accepts the following options:
+
+ -q Quiet mode on. This mode turns off all warnings/notes/mes-
+ sages. (optional)
+
+ -v Verbose mode on. This mode gives as much feedback to the user
+ as possible. (optional)
+
+ -g guile_procedure
+ Specify the guile procedure which is executed to create the
+ netlist.
+
+ -o output_filename
+ Specify the filename which will contain the netlist generated
+ by gnetlist. If this option is not specified the default file-
+ name is "output.net".
+
+ -l scheme_file
+ Specify a filename which contains scheme code to be loaded and
+ execute before any backend is loaded or any guile procedure
+ (using -g flag) is executed. This flag can be specified multi-
+ ple times and can be used to pass information to backends.
+
+ -m scheme_file
+ Specify a filename which contains scheme code to be loaded and
+ execute after the backend is loaded but still before any guile
+ procedure (using -g flag) is executed. This flag can be speci-
+ fied multiple times and can be used to pass information to
+ backends. This flag, for example, allows the user to override
+ variables inside of the backends (such as paths).
+
+ -c string
+ Pass the specified string to the guile interpreter. This
+ allows you to execute arbitrary guile scripts from the command
+ line. Be sure to surround the string with either single or
+ double quotes to satisfy your shell. The string is execute
+ before any init or netlist backend scheme code is loaded or
+ executed.
+
+ -I Put .INCLUDE <filename> in output file instead of model fileâ??s
+ contents.
+
+ -i Interactive mode. After the schematic is read in and parsed
+ then go into interactive mode. Interactive mode allows the
+ user to execute guile procedures directly.
+
+ -s Sort output netlist (for Gnucap)
+
+ schematic1 [... schematicN]
+ At least one schematic file must be specified. If multiple
+ schematics are specified then they are sequentially read in and
+ parsed with the assumption that they are all part of the same
+ design. It is important that the schematic(s) follow all the
+ options (ie last).
+
+
+EXAMPLES
+ These examples assume that you have a stack_1.sch in the current direc-
+ tory.
+
+ gnetlist requires that at least one schematic to be specified on the
+ command line:
+
+ ./gnetlist stack_1.sch
+
+ This is not very useful since it does not direct gnetlist to do
+ anything.
+
+ Specify a guile procedure name to get gnetlist to output a netlist:
+
+ ./gnetlist -g geda stack_1.sch
+
+ The netlist output will be written to a file called "output.net"
+ in the current working directory.
+
+ You can specify the output filename by using the -o flag:
+
+ ./gnetlist -g geda stack_1.sch -o stack.netlist
+
+ The spice backend is run against the schematic(s) if you specify
+ -g spice and the tango backend is run if you specify -g tango.
+
+ To interact with the guile interpreter:
+
+ ./gnetlist -i stack_1.sch
+
+ You will get a prompt where you can execute guile procedures.
+
+ To get a more verbose feedback as to what gnetlist is doing run
+ with the -v flag:
+
+ ./gnetlist -v -g geda stack_1.sch
+
+
+ENVIRONMENT
+ No environment variables are used.
+
+
+AUTHOR
+ Ales Hvezda and many others
+
+
+SEE ALSO
+ gschem(1), gsymcheck(1)
+
+COPYRIGHT
+ Copyright © 1999-2004 Ales Hvezda
+
+ This document can be freely redistributed according to the terms of the
+ GNU General Public License version 2.0
+
+
+
+
+Version December 31st, 2003 gnetlist(1)</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-gnetlist_ug.html b/docs/wiki/geda-gnetlist_ug.html
new file mode 100644
index 0000000..febcf24
--- /dev/null
+++ b/docs/wiki/geda-gnetlist_ug.html
@@ -0,0 +1,419 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#geda_gnetlist_users_guide" class="toc">gEDA gnetlist Users Guide</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#introduction" class="toc">Introduction</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#overview" class="toc">Overview</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#installation" class="toc">Installation</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#running_gnetlist" class="toc">Running gnetlist</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#schematic_symbol_requirements" class="toc">Schematic / symbol requirements</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#symbol_requirements" class="toc">Symbol requirements</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#schematic_requirements" class="toc">Schematic requirements</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#random_notes" class="toc">Random notes</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#hierarchy_support" class="toc">Hierarchy Support</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#specific_backend_info" class="toc">Specific backend info</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#scheme_backend_api" class="toc">Scheme backend API</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#overview1" class="toc">Overview</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#entry_point" class="toc">Entry Point</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#initialization_of_the_backend" class="toc">Initialization of the Backend</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#net_name_and_reference_designator_aliasing" class="toc">Net Name and Reference Designator Aliasing</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#debugging_hints" class="toc">Debugging Hints</a></span></div></li></ul>
+</li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="geda_gnetlist_users_guide" id="geda_gnetlist_users_guide">gEDA gnetlist Users Guide</a></h1>
+<div class="level1">
+
+<p>
+by: Ales Hvezda
+</p>
+
+<p>
+This document is released under <a href="http://www.gnu.org/copyleft/fdl.html"; class="urlextern" title="http://www.gnu.org/copyleft/fdl.html"; rel="nofollow">GFDL</a>
+</p>
+
+<p>
+September 21st, 2003
+</p>
+
+</div>
+<!-- SECTION "gEDA gnetlist Users Guide" [1-158] -->
+<h2><a name="introduction" id="introduction">Introduction</a></h2>
+<div class="level2">
+
+<p>
+This document describes how to use <strong>gnetlist</strong>. This document and <strong>gnetlist</strong> in general are pretty ALPHA, so keep that in mind as you use it to generate netlists. As all engineers know, it is very important that you do not blindly trust tools, assuming that they will always create correct output. <strong>gnetlist</strong> is certainly no exception to this rule. It is very important that you verify *every* netlists you create. As with most programs (including all the programs in gEDA), <strong>gnetlist</strong> comes with NO WARRANTY. Blah, I hate having to say that, but Iâ??m hoping that this warning will keep the user from assuming that <strong>gnetlist</strong> generates perfect netlists. Though if you find a bug, please let <strong>ahvezda@xxxxxxxxxxxxx</strong> know.<br/>
+ This document is very rough, so please e-mail all corrections to <strong>ahvezda@xxxxxxxxxxxxx</strong> or file a bug report on the gEDA homepage at <a href="http://www.gpleda.org"; class="urlextern" title="http://www.gpleda.org"; rel="nofollow">http://www.gpleda.org</a>. Thanks!
+</p>
+
+</div>
+<!-- SECTION "Introduction" [159-1084] -->
+<h2><a name="overview" id="overview">Overview</a></h2>
+<div class="level2">
+
+<p>
+<strong>gnetlist</strong> is the gEDA netlister. It takes as input schematic files and produces a netlist. A netlist is a textual representation of a schematic. This textual representation has all of the connections between devices completely resolved. This means that all the connections associated with a net are grouped together. The netlister also handles hierarchies of schematics.<br/>
+ <strong>gnetlist</strong> has a very flexible architecture. The main program, which is written in C, reads in a schematic (using routines from libgeda) and creates an internal representation of the schematic data. This internal representation is then manipulated by a backend which is responsible for writing the various netlist formats. The backend for each netlist format is written in scheme (specifically Guile). This architecture not only allows for an infinite number of netlist formats, but also allows the netlister to generate other reports (like bill of material lists).<br/>
+ As of 20001006 <strong>gnetlist</strong> has scheme backends to support the following netlist formats:
+</p>
+<ol>
+<li class="level1"><div class="li"> PCB & PCBboard - UNIX PCB netlist format.</div>
+</li>
+<li class="level1"><div class="li"> Allegro netlist format</div>
+</li>
+<li class="level1"><div class="li"> BAE netlist format</div>
+</li>
+<li class="level1"><div class="li"> BOM & BOM2 - Bill of Material generators</div>
+</li>
+<li class="level1"><div class="li"> DRC - Start of a design rule checker</div>
+</li>
+<li class="level1"><div class="li"> gEDA - the native format of gEDA, mainly used for testing</div>
+</li>
+<li class="level1"><div class="li"> Gossip netlist format</div>
+</li>
+<li class="level1"><div class="li"> PADS netlist format</div>
+</li>
+<li class="level1"><div class="li"> ProtelII netlist format</div>
+</li>
+<li class="level1"><div class="li"> Spice compatible netlist format</div>
+</li>
+<li class="level1"><div class="li"> Tango netlist format</div>
+</li>
+<li class="level1"><div class="li"> Verilog code</div>
+</li>
+<li class="level1"><div class="li"> VHDL code</div>
+</li>
+<li class="level1"><div class="li"> VIPEC netlist format</div>
+</li>
+<li class="level1"><div class="li"> VAMS - VHDL-AMS netlist format</div>
+</li>
+</ol>
+
+<p>
+ This list is constantly growing. Several lacking features (as of 20001006) are: no support for buses, error detection and reporting is fairly limited, and … (many more).
+</p>
+
+</div>
+<!-- SECTION "Overview" [1085-2789] -->
+<h2><a name="installation" id="installation">Installation</a></h2>
+<div class="level2">
+
+<p>
+Hopefully by now you have already installed <strong>gnetlist</strong> on your machine. This document does not cover installation. You can verify the installation by running:
+</p>
+<pre class="code">libgeda-config --version
+gesym-config --version
+which gnetlist
+ldd `which gnetlist`</pre>
+
+<p>
+The first two should return the version of the installed tools (libgeda and the symbol library) and the next command should return the path to the <strong>gnetlist</strong> binary. The final command (only on Unix-like operating systems which include the ldd utility for listing dynamic dependencies of executable files or shared objects) will return which libraries are linked to <strong>gnetlist</strong>; all of the request libraries must be found for <strong>gnetlist</strong> to run. If these commands do not return the expected results, then most likely the gEDA tools are not installed properly. Please see the appropriate INSTALL docs (which came with the distribution) for more info on installing the gEDA tools.
+</p>
+
+</div>
+<!-- SECTION "Installation" [2790-3757] -->
+<h2><a name="running_gnetlist" id="running_gnetlist">Running gnetlist</a></h2>
+<div class="level2">
+
+<p>
+It is very easy to run <strong>gnetlist</strong>. <strong>gnetlist</strong> is a pure command line interface so there is no pesky <acronym title="Graphical User Interface">GUI</acronym> to get in the way <img src="images/smileys/icon_smile.gif" align="middle" alt=":-)" /> For a list of command line arguments please run <code>gnetlist -h</code>.<br/>
+ You need to specify the following two parameters to run <strong>gnetlist</strong>:
+</p>
+<ul>
+<li class="level1"><div class="li"> <strong>-g guile_procedure</strong> (this specifies which backend to run against the schematics)</div>
+</li>
+<li class="level1"><div class="li"> <strong>filename.sch</strong> (this specifies the schematic files)</div>
+</li>
+</ul>
+
+<p>
+ You can specify multiple schematics on the command line. The default filename for the generated netlist goes into â??<strong>output.net</strong>â?? You can change this default location by using the <strong>-o filename</strong> option.<br/>
+ A few examples on running <strong>gnetlist</strong>:
+</p>
+<pre class="code">gnetlist -g geda -o stack.net stack_1.sch</pre>
+
+<p>
+(output netlist (in <strong>stack.net</strong>) for <strong>stack_1.sch</strong> using the gEDA native format)
+</p>
+
+<p>
+There are also a few debugging flags. The first one is the <strong>-v</strong> flag which enables verbose mode. Verbose mode outputs a whole bunch of information on what <strong>gnetlist</strong> is doing as well a dump of the internal representation. The <strong>-i</strong> flag which puts <strong>gnetlist</strong> into a interactive mode is very useful in debugging scheme backends and typically is not used by the end user.<br/>
+ For a detailed list of command line arguments please see the <strong>gnetlist</strong> man page.
+</p>
+
+</div>
+<!-- SECTION "Running gnetlist" [3758-5053] -->
+<h2><a name="schematic_symbol_requirements" id="schematic_symbol_requirements">Schematic / symbol requirements</a></h2>
+<div class="level2">
+
+<p>
+This section describes what schematics/symbols need to have to be usable with <strong>gnetlist</strong>. In order for <strong>gnetlist</strong> to work correctly, both the schematics and supporting symbols must be correct. Basically these requirements consist of attribute specification. Attributes are used through out the gEDA system to represent information. Attributes are the only way of adding information to components, nets, pins, etc… For more detailed information about the attributes mentioned in this document, please see the <a href="geda-master_attributes_list.html" class="wikilink1" title="geda-master_attributes_list.html">Master Attributes List</a> document.
+</p>
+
+</div>
+<!-- SECTION "Schematic / symbol requirements" [5054-5677] -->
+<h3><a name="symbol_requirements" id="symbol_requirements">Symbol requirements</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> All symbols must have a <code>device=</code> attribute.</div>
+</li>
+<li class="level1"><div class="li"> All pins must have the <code>pin#=#</code> attribute. This attribute will eventually change form, but for now it is required as <code>pin#=#</code>.</div>
+</li>
+<li class="level1"><div class="li"> All pins should also have a <code>pinlabel=</code> attribute.</div>
+</li>
+<li class="level1"><div class="li"> For symbols which are slotted you also need the <code>slot=</code> attribute, for each slot a <code>slot#=#</code> attribute, and the <code>numslots=#</code> attribute. Slotting will also change in the near future, but for now it should be specified as above.</div>
+</li>
+<li class="level1"><div class="li"> For any power/gnd/arbitrary you need to put <code>net=</code> attributes inside the symbol. See the netattrib.txt document for more info.</div>
+</li>
+<li class="level1"><div class="li"> You can supply default values for various parameters (this is dependent on which backend you use) by taking advantage of the attribute â??promotionâ?? mechanism. See below for more info as well as the gschem documentation.</div>
+</li>
+<li class="level1"><div class="li"> For symbols which you want the netlister to completely ignore use the <code>graphical=1</code> attribute.</div>
+</li>
+<li class="level1"><div class="li"> For more tips on symbols, please see the <a href="geda-scg.html" class="wikilink1" title="geda-scg.html">Symbol Creation Guide</a>.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Symbol requirements" [5678-6726] -->
+<h3><a name="schematic_requirements" id="schematic_requirements">Schematic requirements</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> Most importantly, every component you want to show up in a netlist must have a <code>refdes=</code> attribute. This is <strong>VERY</strong> important. <strong>gnetlist</strong> should warn you if you have a component which doesnâ??t have a <code>refdes=</code>, but there have been bugs which do not cause this warning.</div>
+</li>
+<li class="level1"><div class="li"> You can label all nets using the <code>label=</code> attribute. You only need to attach this label to one net segment (of an electrically connected net) for all the net segments to inherit the label.</div>
+</li>
+<li class="level1"><div class="li"> You can have multiple schematics in a design (which is actually a confusing term since it means many different things to people). To use multiple schematics to create a single netlist, just specify them on the <strong>gnetlist</strong> command line.</div>
+</li>
+<li class="level1"><div class="li"> If you name nets the same, then these nets will be electrically connected. Same net names spawn all the specified schematics.</div>
+</li>
+<li class="level1"><div class="li"> There are quite a few issues that deal with hierarchy please see the hierarchy section below.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Schematic requirements" [6727-7703] -->
+<h3><a name="random_notes" id="random_notes">Random notes</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> Attributes which are not attached to anything and are inside a symbol are â??promotedâ?? to the outside of the symbol when the symbol is placed inside a schematic (in gschem). These promoted attributes are always looked at/for first before going into the symbol. So, in other words, if there is an attribute with the same name is inside a symbol and attached to the outside of the instantiated component, then the outside attribute takes precedence.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Random notes" [7704-8177] -->
+<h2><a name="hierarchy_support" id="hierarchy_support">Hierarchy Support</a></h2>
+<div class="level2">
+
+<p>
+TBA
+</p>
+
+</div>
+<!-- SECTION "Hierarchy Support" [8178-8212] -->
+<h2><a name="specific_backend_info" id="specific_backend_info">Specific backend info</a></h2>
+<div class="level2">
+
+<p>
+TBA
+</p>
+
+</div>
+<!-- SECTION "Specific backend info" [8213-8251] -->
+<h2><a name="scheme_backend_api" id="scheme_backend_api">Scheme backend API</a></h2>
+<div class="level2">
+
+<p>
+Please note that this section is still under construction. The information here should be correct, but it is not complete.
+</p>
+
+</div>
+<!-- SECTION "Scheme backend API" [8252-8406] -->
+<h3><a name="overview1" id="overview1">Overview</a></h3>
+<div class="level3">
+
+<p>
+<strong>gnetlist</strong> operates by loading the schematic database from the .sch files, building an internal representation and then calling a function specific to the desired output netlist type which performs the actual netlisting. Each <strong>gnetlist</strong> backend is contained in a file called gnet-<backend>.scm. Where <backend> is the name of the particular backend. For example, gnet-switcap.scm contains the code used by â??gnetlist -g switcapâ?? and gnet-drc.scm contains the code used by â??gnetlist -g drcâ??. The backends are written in the Scheme programming language. The particular implementation of scheme is guile which stands for GNUâ??s Ubiquitous Intelligent Language for Extensions. More information about guile may be found at <a href="http://www.gnu.org/software/guile/guile.html"; class="urlextern" title="http://www.gnu.org/software/guile/guile.html"; rel="nofollow">http://www.gnu.org/software/guile/guile.html</a>.
+</p>
+
+</div>
+<!-- SECTION "Overview" [8407-9196] -->
+<h3><a name="entry_point" id="entry_point">Entry Point</a></h3>
+<div class="level3">
+
+<p>
+Each netlist backend is required to provide a function whose name matches the netlist type. For example, the switcap backend contained in gnet-switcap.scm must provide a function called â??switcapâ??. That is the function which <strong>gnetlist</strong> will call to initiate the netlisting. The entry point function is given a single argument which is the filename for the output netlist. Typically the first thing a netlister does is to open the output file for writing.<br/>
+ The following excerpt from the switcap backend shows the start of the entry point function and shows the output file being opened. At the end of the function, the output file is closed.
+</p>
+<pre class="code">;; ---------------------------------------
+;; Switcap netlist generation -- top level
+;; ---------------------------------------
+(define switcap
+ (lambda (output-filename)
+ (let ((port (open-output-file output-filename)))
+
+;; rest of netlisting goes here
+
+;; close the output file and return
+ (close-output-port port))))</pre>
+
+</div>
+<!-- SECTION "Entry Point" [9197-10206] -->
+<h3><a name="initialization_of_the_backend" id="initialization_of_the_backend">Initialization of the Backend</a></h3>
+<div class="level3">
+
+<p>
+After opening the output netlist, any specific initializations which must be done for the particular netlist are done. In the switcap example, we must initialize a net name and reference designator (refdes) aliasing database. This is because switcap has more restrictive requirements on its net names than gschem does. In addition, the reference designators in a switcap netlist have special requirements. To deal with this situation, <strong>gnetlist</strong> provides some general purpose functions which rename nets and reference designators to comply with the target netlist requirements. More details on this later. For now, just note that the switcap backend uses the following code:
+</p>
+<pre class="code">;; initialize the net-name aliasing
+(gnetlist:build-net-aliases switcap:map-net-names
+ all-unique-nets)
+
+;; initialize the refdes aliasing
+(gnetlist:build-refdes-aliases switcap:map-refdes
+ packages)</pre>
+
+<p>
+The other initialization which is typically done, although not required by all netlist types, is to output some sort of header. This header may be explicitly contained in the entry point function or it may be contained in its own function for code clarity. In the switcap backend, the call is:
+</p>
+<pre class="code">(switcap:write-top-header port)</pre>
+
+<p>
+Note that the convention is for any backend specific functions to have their names prefixed by the backend name. For example all switcap specific functions begin with â??switcap:". Functions which are available to all backends and provided by <strong>gnetlist</strong> are prefixed by â??gnetlist:".<br/>
+ The definition of â??switcap:write-top-headerâ?? is
+</p>
+<pre class="code">;;
+;; Switcap netlist header
+;;
+(define switcap:write-top-header
+ (lambda (port)
+ (display
+ "/* Switcap netlist produced by gnetlist (part of gEDA) */\n"
+ port)
+ (display
+ "/* See http://www.geda.seul.org for more information. */\n"
+ port)
+ (display
+ "/* Switcap backend written by Dan McMahill */\n"
+ port)
+ (display "\n\n" port)
+ )
+ )</pre>
+
+<p>
+The entry point function continues by calling functions for each section in the output netlist. The variable â??packagesâ?? is predefined by <strong>gnetlist</strong> to be a list of all components in the design and â??all-unique-netsâ?? is a list of all the nets in the design. The various functions used by the backend for each section in the netlist will use these variables. For example, the main part of the switcap netlist which contains the components and their connectivity is written to the output file with
+</p>
+<pre class="code">(switcap:write-netlist port packages)</pre>
+
+</div>
+<!-- SECTION "Initialization of the Backend" [10207-12775] -->
+<h3><a name="net_name_and_reference_designator_aliasing" id="net_name_and_reference_designator_aliasing">Net Name and Reference Designator Aliasing</a></h3>
+<div class="level3">
+
+<p>
+It is common for a target netlist type to have a more restrictive requirement for the net names than gschem does. For example, there may be restrictions on length, allowed characters, or case. To address this issue, <strong>gnetlist</strong> provides a net name aliasing feature. To use this feature, the function â??gnetlist:build-netaliasesâ?? is called as part of the initialization section of the entry point function.<br/>
+ For example in the switcap backend,
+</p>
+<pre class="code">;; initialize the net-name aliasing
+(gnetlist:build-net-aliases switcap:map-net-names
+ all-unique-nets)</pre>
+
+<p>
+The function â??switcap:map-net-namesâ?? is a backend specific (switcap in this case) function which accepts a gschem net name as an argument and returns a modified net name which meets the requirements for the output netlist format. In the case of switcap, the requirement is ground must be called â??0â??, nets may have no more than 7 characters, and the netlist is not case sensitive.
+</p>
+<pre class="code">;; This procedure takes a net name as determined by
+;; gnetlist and modifies it to be a valid SWITCAP net name.
+;;
+(define switcap:map-net-names
+ (lambda (net-name)
+ (let ((rx (make-regexp "^unnamed_net"))
+ (net-alias net-name)
+ )
+ ;; XXX we should use a dynamic regexp based on the
+ ;; current value for the unnamed net base string.
+
+ (cond
+ ;; Change "GND" to "0"
+ ((string=? net-name "GND") (set! net-alias "0"))
+ ;; remove the 'unnamed_net' part
+ ((regexp-exec rx net-name)
+ (set! net-alias (substring net-name 11)))
+ (else net-name)
+ )
+
+ ;; Truncate to 7 characters
+ (if (> (string-length net-alias) 7)
+ (set! net-alias (substring net-alias 0 7))
+ )
+
+ ;; Convert to all upper case
+ (string-upcase net-alias)
+
+ )
+ )
+)</pre>
+
+<p>
+The function â??gnetlist:build-net-aliasesâ?? creates a database which later on lets you look up the output net name from the gschem net name or the gschem net name from the output net name. In addition it does the very important task of ensuring that no shorts are created by modifying the net names. As an example suppose you had a net called â??MyNetâ?? and another called â??mynetâ?? in the schematic. Those are unique but after converting both to upper case they become a single net. â??gnetlist:build-net-aliasesâ?? will detect this condition and issue an error and stop netlisting.<br/>
+ Now that the database has been initialized, the netlister simply uses
+</p>
+<pre class="code">(gnetlist:alias-net somenet)</pre>
+
+<p>
+to retrive the netlist net name from the gschem net name.<br/>
+ A similar set of functions are provided for reference designator aliasing.
+</p>
+
+</div>
+<!-- SECTION "Net Name and Reference Designator Aliasing" [12776-15447] -->
+<h3><a name="debugging_hints" id="debugging_hints">Debugging Hints</a></h3>
+<div class="level3">
+
+<p>
+A useful debugging tool is to run <strong>gnetlist</strong> in interactive mode. This is done by using the "-iâ?? option to <strong>gnetlist</strong>. This will give you a shell where you may enter scheme commands. This provides a simple way to examine various variables and try out various functions.<br/>
+ An example of running <strong>gnetlist</strong> in interactive mode is shown below.
+</p>
+<pre class="code">% gnetlist -i ../../gnetlist/examples/switcap/*.sch
+gEDA/gnetlist version 20041228
+gEDA/gnetlist comes with ABSOLUTELY NO WARRANTY; see COPYING for more details.
+This is free software, and you are welcome to redistribute it under certain
+conditions; please see the COPYING file for more details.
+
+Loading schematic [../../gnetlist/examples/switcap/analysis.sch]
+Loading schematic [../../gnetlist/examples/switcap/ckt.sch]
+Loading schematic [../../gnetlist/examples/switcap/clocks.sch]
+gnetlist> all-unique-nets
+ ("unnamed_net6" "unnamed_net5" "unnamed_net4" "OUT" "unnamed_net3"
+ "unnamed_net2" "unnamed_net1" "GND")
+ gnetlist> packages
+ ("TIMING" "CLK1" "S7" "S8" "S6" "S5" "C3" "S4" "C2" "C1" "E1" "S3"
+ "S1" "V1" "S2" "OPTIONS" "TITLE" "ANA1")
+ gnetlist> (quit)
+ %</pre>
+
+</div>
+<!-- SECTION "Debugging Hints" [15448-] --></body>
+</html>
diff --git a/docs/wiki/geda-grcsan.html b/docs/wiki/geda-grcsan.html
new file mode 100644
index 0000000..5be5687
--- /dev/null
+++ b/docs/wiki/geda-grcsan.html
@@ -0,0 +1,293 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#geda_gaf_rf_cascade_symbols_and_netlister" class="toc">gEDA/gaf RF Cascade Symbols and Netlister</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#overview" class="toc">Overview</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#requirements" class="toc">Requirements</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#creating_schematics" class="toc">Creating Schematics</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#extracting_the_cascade_input_file" class="toc">Extracting the Cascade Input File</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#running_cascade" class="toc">Running Cascade</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#appendix_a_--_symbols_in_the_library" class="toc">Appendix A -- Symbols in the Library</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#sources_cascade-source" class="toc">Sources (cascade-source)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#defaults_cascade-default" class="toc">Defaults (cascade-default)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#elements" class="toc">Elements</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#example" class="toc">Example</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#example_schematics" class="toc">Example Schematics</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#netlist_the_design" class="toc">Netlist the Design</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#run_the_analysis" class="toc">Run the Analysis</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#document_revision_history" class="toc">Document Revision History</a></span></div></li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="geda_gaf_rf_cascade_symbols_and_netlister" id="geda_gaf_rf_cascade_symbols_and_netlister">gEDA/gaf RF Cascade Symbols and Netlister</a></h1>
+<div class="level1">
+
+<p>
+by: Dan McMahill
+</p>
+
+<p>
+This document is released under <a href="http://www.gnu.org/copyleft/fdl.html"; class="urlextern" title="http://www.gnu.org/copyleft/fdl.html"; rel="nofollow">GFDL</a>
+</p>
+
+<p>
+December 3rd, 2003
+</p>
+
+</div>
+<!-- SECTION "gEDA/gaf RF Cascade Symbols and Netlister" [1-173] -->
+<h2><a name="overview" id="overview">Overview</a></h2>
+<div class="level2">
+
+<p>
+This document describes the symbol library and gnetlist backend which support driving RF Cascade (<a href="http://rfcascade.sourceforge.net"; class="urlextern" title="http://rfcascade.sourceforge.net"; rel="nofollow">http://rfcascade.sourceforge.net</a>) simulations from the gEDA/gaf system. Cascade is a noise figure and distortion analysis tool geared towards radio receiver design.<br/>
+ The basic steps involved with using gEDA as the frontend for Cascade simulations are:
+</p>
+<ol>
+<li class="level1"><div class="li"> Create schematics of the circuit.</div>
+</li>
+<li class="level1"><div class="li"> Extract the netlist.</div>
+</li>
+<li class="level1"><div class="li"> Run Cascade.</div>
+</li>
+</ol>
+
+</div>
+<!-- SECTION "Overview" [174-630] -->
+<h2><a name="requirements" id="requirements">Requirements</a></h2>
+<div class="level2">
+
+<p>
+You will need the following programs to be installed:
+</p>
+<ul>
+<li class="level1"><div class="li"> A recent version of gEDA/gaf. To see if your version is recent enough, see if the directory <strong><code>$prefix/share/gEDA/sym/cascade</code></strong> exists. <strong><code>$prefix</code></strong> is the installation prefix for gEDA on your system.</div>
+</li>
+<li class="level1"><div class="li"> RF Cascade. The executable is usually called cascade. If you do not have Cascade available on your system, you will need to get a copy from <a href="http://rfcascade.sourceforge.net"; class="urlextern" title="http://rfcascade.sourceforge.net"; rel="nofollow">http://rfcascade.sourceforge.net</a>.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Requirements" [631-1103] -->
+<h2><a name="creating_schematics" id="creating_schematics">Creating Schematics</a></h2>
+<div class="level2">
+
+<p>
+When creating a block diagram in the gschem schematic editor, use only the symbols from the cascade library. Every block diagram must have a \cascadesourceâ?? element. In addition, the block diagram must be a simple cascade. No parallel paths or branches are allowed.<br/>
+ All instances must have a unique reference designator. For a receiver block diagram, this is often times best achieved by manually entering them. The only restriction on reference designator names is that they contain no spaces. A descriptive name such as \RF Filterâ?? or \First Mixerâ?? is useful as it will show up in the cascade output report.
+</p>
+
+</div>
+<!-- SECTION "Creating Schematics" [1104-1748] -->
+<h2><a name="extracting_the_cascade_input_file" id="extracting_the_cascade_input_file">Extracting the Cascade Input File</a></h2>
+<div class="level2">
+
+<p>
+To extract the Cascade input file, run:
+</p>
+<pre class="code">gnetlist -g cascade -o test.cas file1.sch [file2.sch ...]</pre>
+
+<p>
+For the example file contained in this archive, you can run:
+</p>
+<pre class="code">gnetlist -g cascade -o example.cas example.sch</pre>
+
+<p>
+The netlist will be left in <strong><code>example.cas</code></strong>.
+</p>
+
+</div>
+<!-- SECTION "Extracting the Cascade Input File" [1749-2078] -->
+<h2><a name="running_cascade" id="running_cascade">Running Cascade</a></h2>
+<div class="level2">
+
+<p>
+Cascade is exceptionally simple to run. Just run:
+</p>
+<pre class="code">cascade example.cas > example.out</pre>
+
+<p>
+to run the analysis on the system contained in the file <strong><code>example.cas</code></strong> and write the results to the file <strong><code>example.out</code></strong>. Refer to the Cascade documentation for complete details.
+</p>
+
+</div>
+<!-- SECTION "Running Cascade" [2079-2393] -->
+<h2><a name="appendix_a_--_symbols_in_the_library" id="appendix_a_--_symbols_in_the_library">Appendix A -- Symbols in the Library</a></h2>
+<div class="level2">
+
+<p>
+Please note that all instances must have the <strong><code>refdes=</code></strong> attribute set.
+</p>
+
+</div>
+<!-- SECTION "Appendix A -- Symbols in the Library" [2394-2519] -->
+<h3><a name="sources_cascade-source" id="sources_cascade-source">Sources (cascade-source)</a></h3>
+<div class="level3">
+
+<p>
+Source. Attributes:
+</p>
+<ul>
+<li class="level1"><div class="li"> C=Carrier level in dBm. Optional.</div>
+</li>
+<li class="level1"><div class="li"> CN0=Carrier to Noise Spectral Density Ratio in dBm/Hz. Optional.</div>
+</li>
+<li class="level1"><div class="li"> CN=Carrier to Noise Ratio in dB. Optional.</div>
+</li>
+<li class="level1"><div class="li"> BW=Signal Bandwidth in Hz. Optional, but requred if CN= is used.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Sources (cascade-source)" [2520-2798] -->
+<h3><a name="defaults_cascade-default" id="defaults_cascade-default">Defaults (cascade-default)</a></h3>
+<div class="level3">
+
+<p>
+This symbol sets the default impedance levels as well as the correlation coeffcient used for third order distortion calculations. There are two versions of this symbol. One is used to set the defaults at the beginnng of the definition. The other can be placed in series with the cascade to change the defaults part way through. This is useful if you wish to change impedance levels in the middle of the receiver chain. Attributes:
+</p>
+<ul>
+<li class="level1"><div class="li"> RIN=Default block input resistance in Ohms. Optional.</div>
+</li>
+<li class="level1"><div class="li"> ROUT=Default block output resistance in Ohms. Optional.</div>
+</li>
+<li class="level1"><div class="li"> RHO=Default third order distortion correlation coeffcient. Optional.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Defaults (cascade-default)" [2799-3458] -->
+<h3><a name="elements" id="elements">Elements</a></h3>
+<div class="level3">
+
+<p>
+Cascade characterizes each block in a system by its gain and optionally noise figure and third order intercept point. As such, there is no distinction between various elements such as amplifiers, filters, and mixers. The gEDA/gaf RF Cascade symbol library contains different symbols for clarity in the diagram only. The currently available element symbols are: Attributes:
+</p>
+<table class="inline">
+ <tr>
+ <td>cascade-amp</td><td>Amplifier</td>
+ </tr>
+ <tr>
+ <td>cascade-filter</td><td>Filter</td>
+ </tr>
+ <tr>
+ <td>cascade-mixer</td><td>Mixer</td>
+ </tr>
+ <tr>
+ <td>cascade-transformer</td><td>Transformer</td>
+ </tr>
+ <tr>
+ <td colspan="2"> </td>
+ </tr>
+ <tr>
+ <td colspan="2"> Table 1: Element Types </td>
+ </tr>
+</table>
+<ul>
+<li class="level1"><div class="li"> Gain is specified by one of the following:</div>
+<ul>
+<li class="level2"><div class="li"> <strong>G</strong>=Power gain in dB.</div>
+</li>
+<li class="level2"><div class="li"> <strong>GP</strong>=Power gain in dB.</div>
+</li>
+<li class="level2"><div class="li"> <strong>GV</strong>=Voltage gain in dB.</div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> <strong>NF</strong>=Noise Figure in dB. Optional.</div>
+</li>
+<li class="level1"><div class="li"> <strong>IIP3</strong>=Input Third Order Intercept Point in dBm. Optional.</div>
+</li>
+<li class="level1"><div class="li"> <strong>RIN</strong>=Block input resistance in Ohms. Optional.</div>
+</li>
+<li class="level1"><div class="li"> <strong>ROUT</strong>=Block output resistance in Ohms. Optional.</div>
+</li>
+<li class="level1"><div class="li"> <strong>RHO</strong>=Third order distortion correlation coeffcient. Optional.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Elements" [3459-4416] -->
+<h2><a name="example" id="example">Example</a></h2>
+<div class="level2">
+
+<p>
+This appendix provides a simple example of the entire process of generating a schematic, producing a Cascade input file, running an analysis and looking at the result.
+</p>
+
+</div>
+<!-- SECTION "Example" [4417-4605] -->
+<h3><a name="example_schematics" id="example_schematics">Example Schematics</a></h3>
+<div class="level3">
+
+<p>
+Figure 1 shows the schematic of a simple receiver signal chain.<br/>
+ Figure 2 shows the contents of the example.cas file.
+</p>
+<table class="inline">
+ <tr>
+ <td> <a href="media/geda/rf_cascade_figure1.jpg" class="media" target="_blank" title="geda:rf_cascade_figure1.jpg"><img src="media/geda/rf_cascade_figure1.jpg" class="media" alt="" /></a> </td>
+ </tr>
+ <tr>
+ <td> <a href="media/geda/rf_cascade_figure2.jpg" class="media" target="_blank" title="geda:rf_cascade_figure2.jpg"><img src="media/geda/rf_cascade_figure2.jpg" class="media" alt="" /></a> </td>
+ </tr>
+</table>
+
+</div>
+<!-- SECTION "Example Schematics" [4606-4829] -->
+<h3><a name="netlist_the_design" id="netlist_the_design">Netlist the Design</a></h3>
+<div class="level3">
+
+<p>
+To netlist the design, run:
+</p>
+<pre class="code">gnetlist -g cascade example.cas example.sch</pre>
+
+</div>
+<!-- SECTION "Netlist the Design" [4830-4944] -->
+<h3><a name="run_the_analysis" id="run_the_analysis">Run the Analysis</a></h3>
+<div class="level3">
+
+<p>
+Run the analysis with:
+</p>
+<pre class="code">cascade example.cas</pre>
+
+</div>
+<!-- SECTION "Run the Analysis" [4945-5028] -->
+<h2><a name="document_revision_history" id="document_revision_history">Document Revision History</a></h2>
+<div class="level2">
+<table class="inline">
+ <tr>
+ <td>December 3rd, 2003</td><td>Created cascade.tex</td>
+ </tr>
+</table>
+
+</div>
+<!-- SECTION "Document Revision History" [5029-] --></body>
+</html>
diff --git a/docs/wiki/geda-grenum_mp.html b/docs/wiki/geda-grenum_mp.html
new file mode 100644
index 0000000..2f63000
--- /dev/null
+++ b/docs/wiki/geda-grenum_mp.html
@@ -0,0 +1,76 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="grenum_man-page" id="grenum_man-page">grenum man-page</a></h1>
+<div class="level1">
+<pre class="code">grenum(1) grenum(1)
+
+
+
+NAME
+ grenum - An advanced refdes renumber utility
+
+
+SYNOPSIS
+ grenum [-v|--version -h|--help -p|--pagejump] infile1.sch infile2.sch
+ ...
+
+
+
+DESCRIPTION
+ The grenum program will renumber the refdes definitions read from
+ infile.
+
+
+OPTIONS
+ -p, --pagejump
+ This will switch on the page jump mode. It means that refdes�s
+ from each inputfile gets renumbered from 100,200... etc.
+
+ -v, --version
+ prints version information
+
+ -h, --help
+ prints help message
+
+
+RETURN VALUE
+ grenum will return 0 if all files processed successfully, -1 if there
+ was no input file specified, -2 if I/O files can�t be opened/written,
+ -3 if there is parse error in input file, -4 if there is not enough
+ memory to store refdes prefixes.
+
+BUGS
+ If you find one, please report it to:
+
+
+AUTHOR
+ Levente Kovacs
+
+ Levente.Kovacs@xxxxxxxxxxxx
+
+
+SEE ALSO
+ gschem(1)
+
+
+
+ grenum(1)
+</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-gsch2pcb_readme.html b/docs/wiki/geda-gsch2pcb_readme.html
new file mode 100644
index 0000000..6d22cf8
--- /dev/null
+++ b/docs/wiki/geda-gsch2pcb_readme.html
@@ -0,0 +1,131 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="gsch2pcb_gschem_to_pcb_readme" id="gsch2pcb_gschem_to_pcb_readme">gsch2pcb (gschem to PCB) README</a></h1>
+<div class="level1">
+<pre class="code">gsch2pcb
+--------
+gsch2pcb is a program that interfaces a set of schematics generated with
+with the gEDA gschem to PCB layout files.
+
+gsch2pcb is conceptually similar to the gschem2pcb shell script, but
+additionally handles multiple schematics, handles file element footprints,
+and removes pc board elements corresponding to components deleted from the
+schematics. It also forward annotates component value changes.
+
+Using gsch2pcb allows you to drive all design changes from the gschem
+schematics without the headache of manually keeping PCB elements and
+element values in sync.
+
+It requires that the gnet-gsch2pcb.scm file be install into the gEDA
+scheme directory. On Debian this is /usr/share/gEDA/scheme, but see
+the INSTALL file.
+
+Typical usage
+-------------
+1) Create your custom PCB elements and save each one into its own file.
+ Some compatibility tips if you will be inserting elements into a
+ layout manually as well as with gsch2pcb:
+ * Make the initial "Description" field of these elements the same
+ as the file name because gsch2pcb depends on this name (which is
+ the gschem footprint
+ value) to know when footprints/elements are changed.
+ * Make the initial layout-name field (displayed when the "name on PCB"
+ menu entry is selected) empty (ie "") so that gsch2pcb
+ will not delete your element when you want it to be in the layout
+ even though it is not in the schematic. You can later edit the
+ layout-name to be some refdes value, but I'm not sure it makes sense
+ to name a PCB element that is not referenced in the schematic.
+
+ Note: since once a layout element is named PCB won't let you reset it
+ to an empty name, a sort of kludge is that setting the first character
+ of the layout-name to a non-alphanumeric will protect the element from
+ being deleted by gsch2pcb.
+
+ These file elements should be placed in a directory heirarchy that
+ gsch2pcb will search. The default directories /usr/local/pcb_lib and
+ ./packages are searched in addition to any directories you specify with
+ --elements-dir dirname arguments to gsch2pcb.
+
+2) Create your schematic with gschem. Make sure each component has a
+ unique refdes attribute and a footprint attribute that matches either
+ a PCB m4 element or one of your custom file element names. Beware of
+ file element names that collide with PCB m4 macro names (or specify the
+ use-files option).
+ Make a project file if you wish.
+
+3) Run "gsch2pcb foo.sch" or "gsch2pcb myproject" if you've created the
+ myproject file. If you didn't specify an output name, this will generate
+ a foo.pcb and a foo.net file.
+ If you get errors about footprints not found, you need to create PCB
+ elements for them and repeat this step until you get no errors.
+ Or, just run gsch2pcb again and it will shift unfound elements to
+ foo.new.pcb and you can proceed using PCB on foo.pcb if you wish to
+ fix the errors from inside of PCB.
+
+4) Run "pcb foo.pcb". All the elements will be stacked on top of each other,
+ so move them to desired locations. Load the netlist file foo.net and
+ proceed with using PCB.
+
+5) Modify foo.sch and again run "gsch2pcb foo.sch".
+ * If components were added, PCB elements for them will be placed in the
+ file foo.new.pcb. If components were deleted, the elements for them
+ will be removed from foo.pcb and the original foo.pcb will be renamed
+ to a foo.pcb.bak sequence.
+ * If elements can't be found for new schematic footprints, then the
+ unfound elements will be indicated with PKG_ lines in foo.new.pcb
+ unless you run "gsch2pcb --remove-unfound foo.sch" which will omit
+ the PKG_ lines so you can go ahead and load foo.new.pcb into PCB.
+ * Note that If you have added elements to the .pcb layout which
+ will not exist on the schematics (mounting holes, etc), make sure
+ there is no "name on PCB" (the gschem refdes) for them or else gsch2pcb
+ will delete them when they don't match a schematic refdes and footprint.
+ You could use the --preserve option to prevent deleting any elements at
+ all, but this is really not the best way to use gsch2pcb.
+
+6) Run "pcb foo.pcb" and clean up any dangling traces left over from removed
+ elements. Load any new elements in foo.new.pcb with the "Load layout
+ data to paste-buffer" function. Load the new netlist foo.net.
+
+
+Caveats
+-------
+* gsch2pcb uses a gnetlist backend gnet-gsch2pcb.scm, so be sure when you
+ install gsch2pcb that the gnet-gsch2pcb.scm file gets installed into the
+ right place. Look at the INSTALL file in the tarball.
+
+* WARNING: if you wish to start processing with gsch2pcb any existing PCB
+ files that have m4 elements and were originally generated with gschem2pcb,
+ then be sure to run first with at least gsch2pcb 0.4:
+
+ gsch2pcb --fix-elements
+
+ on the PCB file schematics or else gsch2pcb will want to delete the
+ m4 elements.
+
+* footprint information is saved into PCB element's Description fields,
+ so it's probably not a good idea to change element Description values
+ in your layout while using gsch2pcb unless it is a protected element
+ that has an empty layout-name.
+
+
+
+Bill Wilson billw@xxxxxx
+</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-gsch2pcb_tutorial.html b/docs/wiki/geda-gsch2pcb_tutorial.html
new file mode 100644
index 0000000..5283402
--- /dev/null
+++ b/docs/wiki/geda-gsch2pcb_tutorial.html
@@ -0,0 +1,878 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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_-_gsch2pcb_-_pcb" class="toc">gschem -> gsch2pcb -> PCB</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#terminology" class="toc">Terminology</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#setup" class="toc">Setup</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#simple_example" class="toc">Simple Example</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#create_schematicone.sch" class="toc">Create schematic: one.sch</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#edit_the_attributes_of_the_components_on_the_schematic" class="toc">Edit the attributes of the components on the schematic.</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#create_schematictwo.sch" class="toc">Create schematic: two.sch</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#generate_pcb_files_from_schematics" class="toc">Generate PCB Files from Schematics</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#layout_pcb_files" class="toc">Layout PCB Files</a></span></div></li>
+</ul>
+</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="#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>
+</div>
+</div>
+
+
+
+<h1><a name="gschem_-_gsch2pcb_-_pcb" id="gschem_-_gsch2pcb_-_pcb">gschem -> gsch2pcb -> PCB</a></h1>
+<div class="level1">
+
+<p>
+This is a tutorial on the process of using gsch2pcb as an interface between gschem and PCB. It assumes the gEDA, PCB and gsch2pcb packages are already installed and ready to use. Starting with gEDA 20030901, gsch2pcb is packaged with gEDA and doesnâ??t need to be separately installed. This tutorial is functional and intended to generate results as quickly as possible. It is not a complete reference on gschem or PCB, but it does show with a simple example design all the steps one might need to take.
+</p>
+
+<p>
+The goal is to use gsch2pcb as the bridge between gschem and PCB so that the schematics can always be in sync with the PCB layout because all element additions or deletions in the layout will automatically be driven by changes in the schematics. Back annotation from PCB to gschem is currently not possible.
+</p>
+
+<p>
+See the <a href="geda-gsch2pcb_tutorial_releasenotes.html" class="wikilink1" title="geda-gsch2pcb_tutorial_releasenotes.html">release notes</a> for the history of this tutorial.
+</p>
+
+</div>
+<!-- SECTION "gschem -> gsch2pcb -> PCB" [1-947] -->
+<h2><a name="terminology" id="terminology">Terminology</a></h2>
+<div class="level2">
+
+<p>
+With gschem, you add symbols representing electronic components to a schematic. A symbol is a group of pins, attributes, and lines showing an iconic representation of an electronic component. Pins in symbols are connected to other pins by drawing a net connection between them. Attributes are just named tags attached to symbols to convey some bit of information. For using the schematic with PCB, there are three of these attributes which are relevant and must be specified. Each added symbol should have a <strong>footprint, value,</strong> and <strong>refdes</strong> attribute.
+</p>
+
+<p>
+The schematic <strong>footprint</strong> attribute value of a symbol is the name of the PCB element to be placed on the layout for that instance of the symbol. A PCB element is a group of pins, pads, and silk layer outlines physically corresponding to electronic components. It is probably a source of confusion for newcomers to PCB that elements are of two different types. There are the original m4 macro generated PCB elements and since PCB version 1.7 there are also the newlib style file elements. A file element is a single fixed element in a single file. However, many m4 macro element definitions may exist in a single m4 element file. The macros can be given arguments to provide programmable elements of variable number of pins or spacings. Using these two types will be covered in this tutorial and I will be referring to these distinct element types as <strong>m4 elements</strong> and <strong>file elements</strong>. When you run PCB, the gschem <strong>footprint</strong> attribute value will appear as the displayed element name when you select <strong>Description</strong> from the <strong>Screen→Displayed Element Name</strong> menu because gsch2pcb uses this field to keep track of which <strong>footprint</strong> corresponds to a particular PCB element.
+</p>
+
+<p>
+The gschem <strong>refdes</strong> attribute value is the reference designator on the schematic such as Q1, U1, R1, etc. When you run PCB, this refdes will appear as the displayed element name when you select <strong>Reference Designator</strong> from the <strong>Screen→Displayed Element Name</strong> menu.
+</p>
+
+<p>
+The gschem <strong>value</strong> attribute value is the particular component value such as BC546, 7400, 1K, etc. When you run PCB, this <strong>value</strong> will appear as the displayed element name when you select <strong>Value</strong> from the <strong>Screen→Displayed Element Name</strong> menu.
+</p>
+
+</div>
+<!-- SECTION "Terminology" [948-3251] -->
+<h2><a name="setup" id="setup">Setup</a></h2>
+<div class="level2">
+
+<p>
+You should have a directory structure in mind for organizing your design projects. The install of gEDA and PCB gives you a set of default gschem symbols and default PCB elements, but you can also provide for creating your own custom libraries of gschem symbols and PCB elements.
+</p>
+<ul>
+<li class="level1"><div class="li"> Somewhere, probably under your home directory, create a directory structure for your projects. Use directory names you like, but this tutorial will reference the directory name structure I use:</div>
+</li>
+</ul>
+<pre class="code">gaf/
+gaf/gschem-sym/ Where I put the custom gschem symbols I create.
+gaf/gschem-sym/transistors/ You can organize your custom symbols into subdirectories.
+gaf/pcb-elements/ Where I put the custom PCB file elements I create.
+These can also be organized into subdirectories.
+gaf/myproject1/ And finally, separate directories for each
+gaf/myproject2/ design project.
+...</pre>
+
+<p>
+ With this organization, any custom gschem symbols and PCB elements you make can be common to all of your projects and this is good enough to get you started. However, Iâ??ll mention other possibilities which will be revealed below: There can be project specific PCB <strong>file element</strong> subdirectories or <strong>m4 element</strong> files. Or, CAD administrators can set up site wide custom PCB <strong>file element</strong> directories and <strong>m4 element</strong> files.
+</p>
+<ul>
+<li class="level1"><div class="li"> <strong>gEDA setup (for new versions released >= 2005): </strong> the gschem, gnetlist, and other programs you may use such as gattrib, etc, all need to be able to find any custom symbols you will make, so you need to make your custom gschem symbol directories known to these programs in a gEDA gafrc file by adding <strong>component-library</strong> lines to either a user <strong>${HOME}/gafrc</strong> file or a project specific <strong>gafrc</strong> file in the project directory. There is also a system wide <strong>${GEDADATA}/system-gafrc</strong> file administrators can set up. The <strong>HOME</strong> and <strong>GEDADATA</strong> environment variables must be respectively set for those <strong>gafrc</strong> files to be found. For our directory structure setup above, we could add these lines to <strong>${HOME}/gafrc</strong> (plus lines for each additional <strong>gschem-sym </strong> subdirectory you want):</div>
+</li>
+</ul>
+<pre class="code">(component-library "${HOME}/gaf/gschem-sym")
+(component-library "${HOME}/gaf/gschem-sym/transistors")</pre>
+
+<p>
+or, in each project directory there could be a <strong>gafrc</strong> file with the lines:
+</p>
+<pre class="code">(component-library "../gaf/gschem-sym")
+(component-library "../gaf/gschem-sym/transistors")</pre>
+<ul>
+<li class="level1"><div class="li"> <strong>gEDA setup (for old versions released >= 2004): </strong> The <strong>gafrc</strong> file is not supported. Well, the feature was actually introduced mid 2004, but to get the full functionality described here (relative paths) you really need a 2005 gEDA. Anyway, when using an older gEDA it is necessary to duplicate the <strong>component-library</strong> setup lines in multiple rc files that apply to the various gEDA programs: </div>
+<ul>
+<li class="level2"><div class="li"> <strong>gschem program setup: </strong> create the file <strong>~/.gEDA/gschemrc</strong> with this content:</div>
+</li>
+</ul>
+</li>
+</ul>
+<pre class="code">(component-library "${HOME}/gaf/gschem-sym")
+(component-library "${HOME}/gaf/gschem-sym/transistors")</pre>
+<ul>
+<li class="level1"><div class="li"> <strong>gnetlist program setup: </strong> gnetlist will also need to find these symbols so duplicate those lines into <strong>~/.gEDA/gnetlistrc</strong>.</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> If you want a more detailed customization of gschem and gnetlist, you can override other initializations that are setup in the global rc files. In Debian, look at rc files in <strong>/etc/gEDA/</strong> for settings you can make. For example, I like the light gschem background, so I also put in my <strong>~/.gEDA/gschemrc</strong> the line:</div>
+</li>
+</ul>
+<pre class="code">(load (build-path geda-rc-path "gschem-colormap-lightbg")) ; light background</pre>
+<ul>
+<li class="level1"><div class="li"> <strong>PCB setup: </strong> A PCB distribution usually is set up so that PCB will automatically look in a <strong>packages</strong> subdirectory of the working directory. So, to make PCB find all the custom elements I put in <strong>gaf/pcb-elements</strong> I make a link in each of my project directories. Note that this link is actually not required when using gsch2pcb because, as described below, you may alternatively specify the <strong>pcb-elements</strong> directory in a <strong>project</strong> file. But if you do want to make the link, in directory <strong>gaf/myproject1</strong> enter the command:</div>
+</li>
+</ul>
+<pre class="code">ln -s ../pcb-elements packages</pre>
+<ul>
+<li class="level1"><div class="li"> <strong> gsch2pcb setup: </strong> In each of your project directories, create a gsch2pcb project file which can be named anything that does not end in <em>.sch</em>. A poject file will be created in the example below.</div>
+</li>
+</ul>
+
+<p>
+ This is all the setup you need beyond the initial install of the gschem, gsch2pcb, and PCB packages.
+</p>
+
+</div>
+<!-- SECTION "Setup" [3252-7825] -->
+<h2><a name="simple_example" id="simple_example">Simple Example</a></h2>
+<div class="level2">
+
+<p>
+Letâ??s generate a trivial design from schematics to PCB layout almost as quickly as possible and then we can use it as a base for doing some more advanced stuff. Iâ??ll complicate it just a bit by making it a two schematic design.
+</p>
+
+<p>
+ Assuming you setup the directory structure described above, go to the <strong>gaf/myproject1</strong> directory and create a file named <strong>project</strong> with this content:
+</p>
+<pre class="code">schematics one.sch two.sch
+output-name board
+</pre>
+
+</div>
+<!-- SECTION "Simple Example" [7826-8301] -->
+<h3><a name="create_schematicone.sch" id="create_schematicone.sch">Create schematic: one.sch</a></h3>
+<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.html">gschem warmup</a>.
+</p>
+
+<p>
+<a href="media/geda/one-sch-1.png" class="media" target="_blank" title="geda:one-sch-1.png"><img src="media/geda/one-sch-1.png" class="medialeft" title="one.sch" alt="one.sch" /></a> Run <strong>gschem one.sch</strong> and create this schematic (the second opamp is redundant, but this is just a tutorial):
+</p>
+<ul>
+<li class="level1"><div class="li"> Open the select components dialog (type <strong>i</strong>)</div>
+</li>
+<li class="level1"><div class="li"> Make sure, the drop down menu at the bottom of the dialog is set to â??Default behavior - reference componentâ??.</div>
+</li>
+<li class="level1"><div class="li"> Add the components:</div>
+<ul>
+<li class="level2"><div class="li"> From the <strong>Basic devices</strong> library three <strong>resistor-1.sym</strong> and two <strong>dual-opamp-1.sym</strong>.</div>
+</li>
+<li class="level2"><div class="li"> From the <strong>Input/output</strong> library one <strong>output-2.sym</strong>.</div>
+</li>
+<li class="level2"><div class="li"> From the <strong>Power rails</strong> library one <strong>gnd-1.sym</strong>, two <strong>vcc-1.sym</strong> and two <strong>vee-1.sym</strong></div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> Move components with the middle mouse button and rotate selected components by hitting keys <strong>er</strong> until everything is placed nicely. Rotate the bottom opamp and mirror it with the <strong>ei</strong> keys.</div>
+</li>
+<li class="level1"><div class="li"> Use the <strong>n</strong> key and the mouse to draw net connections.</div>
+</li>
+</ul>
+
+<p>
+ The large frame of the titleblock is a component too. It has been locked for convienience to prevent the mouse from catching it all the time. To unlock it, select it by dragging with left mouse button held down and press [e - shift-L]. You can find title blocks with different sizes in the <strong>Titleblocks</strong> library. Remember, to lock the new title block with [el] while the title block is selected.
+</p>
+
+</div>
+<!-- SECTION "Create schematic: one.sch" [8302-9703] -->
+<h3><a name="edit_the_attributes_of_the_components_on_the_schematic" id="edit_the_attributes_of_the_components_on_the_schematic">Edit the attributes of the components on the schematic.</a></h3>
+<div class="level3">
+
+<p>
+<a href="media/geda/one-sch-2.png" class="media" target="_blank" title="geda:one-sch-2.png"><img src="media/geda/one-sch-2.png" class="mediaright" title="one.sch" alt="one.sch" /></a> For each component, select it and bring up its attributes window by hitting keys <strong>ee</strong>. Do not edit the <strong>refdes</strong> attribute here, but do make these edits:
+</p>
+<ul>
+<li class="level1"><div class="li"> For resistors and the opamps, add visible <strong>value</strong> attributes and assign appropriate values to them (10K, TL072). Move these newly visible attributes to nice locations with the middle mouse button. Zoom in and repeat clicking the middle mouse button if it is difficult to select them.</div>
+</li>
+<li class="level1"><div class="li"> For the resistors, add a <strong>footprint</strong> attribute and give it the value <strong>R025</strong> which is the PCB <em>m4 element</em> for a 1/4 watt resistor. Make this attribute invisible.</div>
+</li>
+<li class="level1"><div class="li"> For the opamps, edit the already existing <strong>footprint</strong> attribute to be <strong>DIL 8 300</strong>. Yes, include those spaces because <strong>DIL</strong> is a <strong>m4 element</strong> that takes two args. Weâ??re telling it to make a dual in line package with 8 pins in a 300 mil package. Edit the <strong>slot</strong> attribute of the second opamp to be <strong>2</strong>. Its I/O pin numbers should change from (1,2,3) to (5,6,7).</div>
+</li>
+<li class="level1"><div class="li"> For the output module port, edit its <strong>net</strong> attribute to be <strong>vmixer:1</strong> and make it invisible. Edit its <strong>value</strong> attribute to be <strong>Vmixer</strong>.</div>
+</li>
+</ul>
+
+<p>
+ It may have occurred to you that this editing will be painful for a schematic with a large number of components that donâ??t have reasonable initial attribute values. At least for the footprints, there are a couple of things that could help. You can create your own library symbols having an initial <strong>footprint</strong> (and even <strong>value</strong>) attribute default that covers most of your uses. Or, when you add your first component, edit it to have a good footprint default and then copy it (select it and hit the <strong>ec</strong> keys) for all remaining components instead of adding them from the library.<br/>
+
+</p>
+
+<p>
+Anyway, weâ??re done for now with <strong>one.sch</strong>, so save it with the menu <strong>File→Save Page</strong> and quit gschem.
+</p>
+
+</div>
+<!-- SECTION "Edit the attributes of the components on the schematic." [9704-11653] -->
+<h3><a name="create_schematictwo.sch" id="create_schematictwo.sch">Create schematic: two.sch</a></h3>
+<div class="level3">
+
+<p>
+This will be really trivial and stupid since weâ??re doing it only to demonstrate multiple schematic capability. <a href="media/geda/two-sch-1.png" class="media" target="_blank" title="geda:two-sch-1.png"><img src="media/geda/two-sch-1.png" class="medialeft" title="two.sch" alt="two.sch" /></a> Run <strong>gschem two.sch:</strong>
+</p>
+<ul>
+<li class="level1"><div class="li"> Add component <strong>title-B.sym</strong> as you did in one.sch.</div>
+</li>
+<li class="level1"><div class="li"> Add components:</div>
+<ul>
+<li class="level2"><div class="li"> From the <strong>Iput/Output</strong> library one <strong>input-2.sym</strong>.</div>
+</li>
+<li class="level2"><div class="li"> From the <strong>Basic Devices</strong> library one <strong>resistor-1.sym</strong>.</div>
+</li>
+<li class="level2"><div class="li"> From the <strong>Transistors</strong> library one <strong>2N3904-1.sym</strong>.</div>
+</li>
+<li class="level2"><div class="li"> From the <strong>Power rails</strong> library one <strong>gnd-1.sym</strong>, one <strong>vcc-1.sym</strong> and one <strong>vee-1.sym</strong>.</div>
+</li>
+<li class="level2"><div class="li"> From the <strong>Connectors</strong> library one <strong>BNC-1.sym</strong>.</div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> Move components and draw nets as before.</div>
+</li>
+<li class="level1"><div class="li"> Edit component attributes:</div>
+<ul>
+<li class="level2"><div class="li"> Input module port: edit <strong>net</strong> attribute to be invisible and have value <strong>vmixer:1</strong> so this net will be connected to the <strong>vmixer</strong> in one.sch. Make the <strong>value</strong> attribute be <strong>Vmixer</strong>.</div>
+</li>
+<li class="level2"><div class="li"> Resistor: give it invisible <strong>footprint</strong> attribute <strong>R025</strong> and a visible <strong>value</strong> attribute 10K.</div>
+</li>
+<li class="level2"><div class="li"> Transistor: add <strong>value</strong> attribute <strong>2N3904</strong> and invisible <strong>footprint</strong> attribute <strong>TO92</strong>.</div>
+</li>
+<li class="level2"><div class="li"> BNC connector: add invisible <strong>footprint</strong> attribute <strong>CONNECTOR 2 1</strong>. which is a <strong>m4 element</strong> that takes arguments and weâ??re telling it to make a connector with 2 rows and 1 column. We put a BNC connector on the schematic, but Iâ??m pretending weâ??ll just jumper wires from this pc board header to a panel mounted connector.</div>
+</li>
+</ul>
+</li>
+</ul>
+
+<p>
+ Unfortunately, the 2N3904 symbol we added has the text â??2N3904â?? as an integral part of its symbol. So when we add the <strong>value</strong> attribute (which we want so the PCB layout will show appropriate values), there are two â??2N3904â?? designations visible on our schematic unless we would make the <strong>value</strong> attribute invisible. This is not good and for this example we have to live with it, but note that in most cases itâ??s not a good idea to hardwire information into symbols like this. Also the default <strong>device</strong> attribute is wrong and should be <strong>NPN_TRANSISTOR</strong> but it wonâ??t affect this tutorial. This is just to inform you that currently there are some symbols in gschem that carry over outdated attribute usage from older versions of gschem. If you get into running spice on schematics, then your symbols will need to have proper <strong>device</strong> attributes.
+</p>
+
+<p>
+Now we are done with the schematics except for assigning <strong>refdes</strong> attributes and we can use the command <strong>refdes_renum</strong> to do this for both schematics at once. So, save <strong>two.sch</strong>, quit gschem and run:
+</p>
+<pre class="code">$ refdes_renum --pgskip one.sch two.sch
+</pre>
+
+<p>
+ Run gschem on the schematics again to see how the components have been given a <strong>refdes</strong> attribute. The <em>–pgksip</em> option makes numbering begin at 101 for one.sch and at 201 for two.sch. But you should know that running <strong>refdes_renum</strong> is really only useful for an initial numbering. If you later edit your schematics and add or delete components, there is no guarantee when rerunning <strong>refdes_renum</strong> that components will keep an existing <strong>refdes</strong> value. If in the meantime youâ??ve generated a pc board using gsch2pcb, this reference designator number mixup will put your schematics out of sync with your PCB layout. So, after you initially run <strong>refdes_renum</strong> and start a PCB layout, to be safe you will need to manually add (unique) <strong>refdes</strong> attributes for any schematic components you might add. Also note that <strong>refdes_renum</strong> may number your resistors differently than it did for my examples here depending on the order in which resistors were added. Keep that in mind when comparing your eventual PCB layout to what you see in the images below.
+</p>
+
+</div>
+<!-- SECTION "Create schematic: two.sch" [11654-15281] -->
+<h3><a name="generate_pcb_files_from_schematics" id="generate_pcb_files_from_schematics">Generate PCB Files from Schematics</a></h3>
+<div class="level3">
+
+<p>
+We have to fix one thing in <strong>one.sch</strong> before we can proceed. Run <strong>gschem one.sch</strong> and notice that <strong>refdes_renum</strong> has given our opamps <strong>refdes</strong> values of <strong>U101</strong> and <strong>U102</strong> and did not know we really want to be using two opamps out of a single TL072 package. Thatâ??s why we edited the <strong>slot</strong> attribute of the second opamp. We have to go back and fix this by editing the <strong>refdes</strong> attribute of the second opamp to be <strong>U101</strong> so both opamps will have the same <strong>refdes</strong> and there will be only one TL072 package on our pc board.
+</p>
+
+<p>
+ Now, since we have already set up a gsch2pcb <strong>project</strong> file, all we need to do to create an initial set of PCB files is to run gsch2pcb:
+</p>
+<pre class="code">~/gaf/myproject1$ gsch2pcb project
+0 file elements and 7 m4 elements added to board.pcb.
+</pre>
+
+<p>
+ Since the project file specifed <strong>board</strong> as the output-name, the PCB files created are named <strong>board.pcb</strong> and <strong>board.net</strong>.
+</p>
+
+<p>
+NB: more recent advice is to create an empty board using pcb first; then every use of gsch2pcb will generate changes to that layout as described below (Modifying Schematics). The reason for this is that gsch2pcbâ??s default settings are quite different than pcbâ??s these days, and the consensus is that pcbâ??s defaults are better for most uses. One caveat with this is that if you use pcb2panel to combine multiple layouts into a single panelized layout, you will get unusable results if the boards were created with a mix of gsch2pcb and [recent] pcb defaults without editing the layer stacks, which may require further work. (mjm, Aug 2008)
+</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="geda-gsch2pcb_tutorial.html#custom_m4_elements_requires_gsch2pcb_1.0" class="wikilink1" title="geda-gsch2pcb_tutorial.html"> Custom M4 Elements </a> section.
+</p>
+
+</div>
+<!-- SECTION "Generate PCB Files from Schematics" [15282-17519] -->
+<h3><a name="layout_pcb_files" id="layout_pcb_files">Layout PCB Files</a></h3>
+<div class="level3">
+
+</div>
+
+<h4><a name="set_the_defaults" id="set_the_defaults">Set the defaults</a></h4>
+<div class="level4">
+
+<p>
+<a href="media/geda/board-1.png" class="media" target="_blank" title="geda:board-1.png"><img src="media/geda/board-1.png" class="medialeft" title="pcb, step 1" alt="pcb, step 1" /></a>Run <strong>pcb board.pcb</strong>. Youâ??ll see grouped into a big pile the PCB elements for all the schematic component footprints. This is ok, we will clean up this mess later.
+</p>
+
+<p>
+When you run PCB on a <strong>.pcb</strong> file for the first time, you should set up various initial values. I usually set a 25 mil grid spacing with <strong>Screen→Grid Setting→25 mil</strong> for the bulk of my layout work and then change grid spacing to smaller values as needed for tight layout situations. Note that if you have enabled millimeter units with <strong>Screen→Enable millimeter grid units</strong> you will see a set of millimeter size options to select from instead of mils in the <strong>Screen→Grid Setting</strong> menu. You may change between millimeter and mil grid units at any time when doing a layout.
+</p>
+
+<p>
+You should also set the default line and via sizes you want for the Signal, Power, Fat, and Skinny drawing route styles. Simply select one of these four route styles at the lower left of the PCB window and then press the <strong>Route Style</strong> button to edit the sizes. You can set your board size now or wait until later while working on the layout. To change the board size, bring up the <strong>File→Preferences</strong> window and select the <strong>Sizes</strong> page. Other design rule checking and increment sizes can also be edited in the Preferences window. You should review PCB documentation for definitions of these items. And you may find it useful to select <strong>Screen→Enable visible grid</strong>.
+</p>
+
+</div>
+
+<h4><a name="disperse_the_components" id="disperse_the_components">Disperse the Components</a></h4>
+<div class="level4">
+
+<p>
+<a href="media/geda/board-2.png" class="media" target="_blank" title="geda:board-2.png"><img src="media/geda/board-2.png" class="mediaright" title="step 2" alt="step 2" /></a> Use the middle mouse button to grab and move elements one at a time until you have separated all the elements.
+</p>
+
+<p>
+Or, you can let PCB spread out the elements with <strong>Select→Disperse all elements</strong> before you fine tune the positions with the middle mouse button.
+</p>
+
+</div>
+
+<h4><a name="load_the_netlist" id="load_the_netlist">Load the Netlist</a></h4>
+<div class="level4">
+
+<p>
+<a href="media/geda/board-3.png" class="media" target="_blank" title="geda:board-3.png"><img src="media/geda/board-3.png" class="medialeft" title="Step 3" alt="Step 3" /></a>
+</p>
+<ul>
+<li class="level1"><div class="li"> Go to <strong>File→load netlist file</strong> and select <strong>board.net</strong> </div>
+</li>
+<li class="level1"><div class="li"> Do <strong>Connects→optimize rats-nest</strong>. Now, the pins and pads of components should be connected with straight lines according to the schematic. These are â??ratsâ??.</div>
+</li>
+</ul>
+
+<p>
+ To minimize confusion, PCB tries to draw the rats of complex connections such that the sum of all rats is as short as possible. Try to drag an element to the other side of the working area. The rats will follow like a rubber band, but the end of the rats will not jump to a different node, although the resulting length might be shorter. The action <strong>optimize rats-nest</strong> rats will make the rats jump to this â??betterâ?? geometry. This action can be applied conviniently anytime with a troke of the the key <strong>o</strong>.
+</p>
+
+</div>
+
+<h4><a name="place_the_components" id="place_the_components">Place the Components</a></h4>
+<div class="level4">
+
+<p>
+<a href="media/geda/board-4.png" class="media" target="_blank" title="geda:board-4.png"><img src="media/geda/board-4.png" class="mediaright" title="Step 4" alt="Step 4" /></a>You will have to replace the rats with traces that can be etched in copper. After â??Disperse all elementsâ?? the rats are usually in a random mess with lots of crossings. You should move and rotate the components around and try to disentangle the rats as much as possible. The key to a well routed pcb is proper placement of the components. Although PCB tries to clean up the rats lines while you move the components around, it is good practice to occasionly initiate rats optimization with the <strong>o</strong>-key.
+</p>
+
+<p>
+ Select the <strong>ROT</strong> tool (<strong>F-9</strong>) to move elements with the middle mouse button and rotate them with the left mouse button. The right mouse button will move the viewport to the canvas when zoomed in. Zoom in and out with the mouse wheel or alternatively with <strong>z</strong> and <strong>Shift z</strong>. Hit the <strong>f</strong> key while the mouse hovers over a pin to highlight the particular that touches this pin to help visualize the routes. Use <strong>Shift f</strong> to unhighlight. You can undo changes anytime with the <strong>u</strong> key.
+</p>
+
+<p>
+Note: you can use the PCB auto placement feature instead of manually placing (or dispersing with the <strong>Select→Disperse …</strong> commands) the components as described above. To do this, you would load the netlist, select the components you want to be autoplaced (if this is the first PCB run, just <b>Select→Select all objects</b>) then do <strong>Select→Auto place selected elements</strong>. Then you can again manually tune the PCB generated placements. The auto place function should place elements more intelligently than the disperse function, but it is also much slower as layouts get larger.
+</p>
+
+</div>
+
+<h4><a name="replace_rats_nests_with_routes" id="replace_rats_nests_with_routes">Replace rats nests with routes</a></h4>
+<div class="level4">
+
+<p>
+<a href="media/geda/board-5.png" class="media" target="_blank" title="geda:board-5.png"><img src="media/geda/board-5.png" class="medialeft" title="Step 5" alt="Step 5" /></a> At this point you can start routing traces between pins connected by rats nest lines. On the left PCB toolbar, select the <strong>LINE</strong> tool, select the layer you want to draw on (solder, component, etc), and start drawing lines by selecting endpoints with the left mouse button. Again, it can help to use the <strong>f</strong> key to highlight routes that need to be connected. If you want to stop the current trace so you can start drawing a new trace somewhere else, finish the current trace with a middle mouse click. Or you can play with auto routing here.
+</p>
+
+<p>
+A very useful operation with the <strong>SEL</strong> tool is to select multiple objects and then cut or copy them to a buffer with the menu <strong>Buffer→Cut selection to buffer</strong> (or copy). You can immediately paste the buffer contents or abort the current paste by selecting another tool. The buffer contents can be pasted any time later with <strong>Buffer→Paste buffer to layout</strong>. With this you can move layout areas around or step and repeat common trace patterns. To select multiple objects with the <strong>SEL</strong> tool, click and drag to select rectangular regions, and SHIFT click to toggle additional selections to the currently selected set.
+</p>
+
+<p>
+When youâ??ve finished routing the traces (PCB will congratulate you if all traces are routed when you optimze the rats nest) the board can look something like this. For this view Iâ??ve selected <strong>Screen→Displayed element name→Value</strong>.
+</p>
+
+<p>
+You will want more information on using PCB and there is a set of html docs in the PCB source tarball. I donâ??t know of a link to put here, but you can get the latest tarball from the <a href="http://sourceforge.net/projects/pcb/"; class="urlextern" title="http://sourceforge.net/projects/pcb/"; rel="nofollow">PCB development </a> site. Or the docs may be installed somewhere on your system. The Debian package has them installed in <strong>/usr/share/doc/pcb/html/</strong>. PCB also has some convenient â??liveâ?? documentation that can help you become familiar with keyboard shortcuts or keyboard commands. Bring up the keyboard shortcuts window with the menu <strong>Window→Key Reference</strong> and youâ??ll probably find just reading through the shortcuts available will teach you a lot about what you can do with PCB. If you have selected in the <strong>File→Preferences</strong> window the <em>Use separate window for command entry</em> option, then when you bring up the Command window with <strong>Window→Command Entry</strong> (or the ':' key), you will see a <strong>Command Reference</strong> expander arrow. Click on the arrow and a command reference will be shown which lists some commands you can type in that may not be available from the menus or a keyboard shortcut.
+</p>
+
+<p>
+ For example, say you have in the <strong>Preferences→Increments</strong> page configured a size increment of 5 mils. With this you can select some lines and then increase their width by 5 mils by selecting from the menu <strong>Select→Change size of selected objects→Increment lines by 5 mils.</strong> However, suppose you want to be changing widths by random values and itâ??s inconvenient to be changing the Preferences each time. For this, you can select some lines, bring up the command window (hit â??<strong>:</strong>â??) and type in the command:
+</p>
+<pre class="code"> changesize(selectedlines, +3, mils)
+</pre>
+
+<p>
+ and the selected lines will increase by 3 mils. This command is now in a history list which you can recall and quickly edit in the command window to change sizes by other values.
+</p>
+
+</div>
+
+<h4><a name="looking_at_the_other_side_of_the_board" id="looking_at_the_other_side_of_the_board">Looking at the other side of the board</a></h4>
+<div class="level4">
+
+<p>
+In some layouts it is important to put components on either side of the board, although not for the preceeding example. In such a case the â??tabâ?? key can be used to flip the board over and view it from the back while the â??bâ?? key can be used to put a selected component on the other side of the board. On dual sided boards it is also important to note what side a particular layer of traces is on. This can be seen, and set, in the File→Preferences→Layers→Groups dialog. Layers on the â??componentâ?? side will be on the top of the board and layers on the â??solderâ?? side will be on the bottom. In this dialog you should make sure that all layers which are to be fabricated in the same step (i.e. etched with photo-lithography) are grouped together.
+</p>
+
+</div>
+<!-- SECTION "Layout PCB Files" [17520-25954] -->
+<h2><a name="modifying_schematics" id="modifying_schematics">Modifying Schematics</a></h2>
+<div class="level2">
+
+<p>
+The process of transfering schematic modifications to your PCB layout is made very simple by using gsch2pcb. After the first <strong>board.pcb</strong> was created when you initially ran gsch2pcb, each time you run gschem on your schematics and make changes, run <strong>gsch2pcb project</strong>. Then run <strong>pcb board.pcb</strong> and do whatever is necessary based on the work gsch2pcb has done. Each time gsch2pcb is run, this will happen:
+</p>
+<ul>
+<li class="level1"><div class="li"> gsch2pcb always generates a new <strong>board.net</strong>. If the net was changed, load the new netlist file when you run pcb. *</div>
+</li>
+</ul>
+
+<p>
+ If you added components (with a footprint attribute) to a schematic gsch2pcb will generate a <strong>board.new.pcb</strong> containing all the new PCB elements corresponding to the footprints. You then run <strong>pcb board.pcb</strong> and load the <strong>board.new.pcb</strong> with new elements into the existing layout with <strong>File→load layout data to paste-buffer</strong>. Place the new elements, load the new netlist, and route new traces.<br/>
+
+</p>
+<ul>
+<li class="level1"><div class="li"> If you deleted components from a schematic, gsch2pcb will delete the corresponding PCB elements from <strong>board.pcb</strong>. You only need to run <strong>pcb board.pcb</strong> and clean up dangling traces from around the deleted elements.</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> If you change an existing componentâ??s <strong>footprint</strong>, gsch2pcb will delete the corresponding old element from <strong>board.pcb</strong> and add the new element to <strong>board.new.pcb</strong>.</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> If you changed schematic component <strong>value</strong> attributes, the value changes will be forward annotated to <strong>board.pcb</strong> in place.</div>
+</li>
+</ul>
+
+<p>
+So by using gsch2pcb, all PCB element changes are driven by the schematics and you should never need to manually add or delete elements for schematic components.
+</p>
+
+<p>
+ However, you will need to manually add PCB elements that are not part of the schematics such as pc board mounting holes. For these manually added PCB elements, make sure you never give them a <strong>name on PCB</strong> name because that is reserved for schematic component <strong>refdes</strong> attributes and gsch2pcb will want to delete elements which have a non-empty <strong>name on PCB</strong> and donâ??t match any schematic component <strong>refdes</strong>.
+</p>
+
+<p>
+ Now, so far weâ??ve only used <strong>m4 elements</strong> in our layout so letâ??s modify a schematic to use a <strong>file element</strong>. But first, it would help to know about the default elements PCB provides. Depending on the location of your PCB install there will be a directory <strong>/usr/local/share/pcb/newlib, /usr/share/pcb/newlib</strong>, or possibly something else (depending on the <em>prefix</em> specified when PCB was installed). PCB versions before 20031113 used <strong>pcb_lib</strong> instead of <strong>newlib</strong> in the locations <strong>/usr/local/pcb_lib, </strong> or <strong>/usr/lib/pcb_lib,</strong>. Once you find your <strong>newlib</strong> directory, look at the file names in each subdirectory. Each file name is a name which may be used as a <strong>footprint</strong> attribute for a schematic component. For example, there is the file <strong>xxx/newlib/2_pin_thru-hole_packages/0.125W_Carbon_Resistor</strong> so if we wanted 1/8 watt resistors on our layout, we could use <strong>0.125W_Carbon_Resistor</strong> as the resistor <strong>footprint</strong> attribute instead of <strong>R025</strong>. Try changing, say resistor R101 to use <strong>0.125W_Carbon_Resistor</strong> in <strong>one.sch</strong> and then run <strong>gsch2pcb project</strong>. If gsch2pcb does not find this element, then you need to add your <strong>newlib</strong> directory to your <strong>project</strong> file with a line like:
+</p>
+<pre class="code">elements-dir /usr/lib/newlib
+</pre>
+
+<p>
+ If gsch2pcb does find it, you will get:
+</p>
+<pre class="code">~/gaf/myproject1$ gsch2pcb project
+board.pcb is backed up as board.pcb.bak1.
+1 elements deleted from board.pcb.
+1 file elements and 0 m4 elements added to board.new.pcb.
+</pre>
+
+<p>
+ Now you need to run <strong>pcb board.pcb</strong>. You will see that the element for resistor R101 is gone and that you will get the new element by loading <strong>board.new.pcb</strong> with <strong>File→load layout data to paste-buffer</strong>.
+</p>
+
+</div>
+<!-- SECTION "Modifying Schematics" [25955-29760] -->
+<h2><a name="custom_gschem_symbols" id="custom_gschem_symbols">Custom gschem Symbols</a></h2>
+<div class="level2">
+
+<p>
+A common way to generate a custom symbol is to start with an existing symbol and modify it. One thing I donâ??t like about the <strong>dual-opamp-1.sym</strong> we used is that the power pins are repeated on each symbol. While some will prefer this, I think it makes a page full of opamps look a little cluttered and it presents a good opportunity to learn about <strong>net</strong> attributes in this tutorial. Itâ??s possible with gschem for symbols to have <strong>net</strong> attributes which can assign pins to a particular net. Instead of hooking up each opamp pin 8 to Vcc and pin 4 to to Vee on the schematic, we can have that happen automatically and eliminate the pins on the schematic. To do this, just copy the original symbol to our custom gschem symbol directory, giving it a new name, and edit it. Do the steps described below. (Your gEDA symbol install directory may be something different like <strong>/usr/local/share/gEDA/sym/</strong>):
+</p>
+
+</div>
+
+<h5><a name="make_attributes_visible" id="make_attributes_visible">Make Attributes Visible</a></h5>
+<div class="level5">
+
+<p>
+<a href="media/geda/gschem-sym-1.png" class="media" target="_blank" title="geda:gschem-sym-1.png"><img src="media/geda/gschem-sym-1.png" class="medialeft" title="Step 1" alt="Step 1" /></a>
+</p>
+<pre class="code">cd /usr/share/gEDA/sym/analog/
+cp dual-opamp-1.sym ~/gaf/gschem-sym/opamp-dual.sym
+cd ~/gaf/gschem-sym
+gschem opamp-dual.sym
+</pre>
+<ul>
+<li class="level1"><div class="li"> Hit keys <strong>en</strong> to make attributes visible.</div>
+</li>
+<li class="level1"><div class="li"> Hit keys <strong>ve</strong> to view extents.</div>
+</li>
+<li class="level1"><div class="li"> Left mouse click on pin 8 to select it.</div>
+</li>
+</ul>
+
+</div>
+
+<h5><a name="remove_the_visible_supply_pins" id="remove_the_visible_supply_pins">Remove the Visible Supply Pins</a></h5>
+<div class="level5">
+
+<p>
+<a href="media/geda/gschem-sym-2.png" class="media" target="_blank" title="geda:gschem-sym-2.png"><img src="media/geda/gschem-sym-2.png" class="medialeft" title="Step 2" alt="Step 2" /></a> * Hit <strong>Delete</strong> key to delete pin 8.
+</p>
+<ul>
+<li class="level1"><div class="li"> Similarly select and delete pin 4.</div>
+</li>
+<li class="level1"><div class="li"> Double click to select and edit the <strong>slotdef</strong> lines. Edit them by removing the pins 4 and 8.</div>
+</li>
+</ul>
+
+</div>
+
+<h5><a name="add_global_nets_to_in_numbers" id="add_global_nets_to_in_numbers">Add global Nets to in Numbers</a></h5>
+<div class="level5">
+
+<p>
+<a href="media/geda/gschem-sym-3.png" class="media" target="_blank" title="geda:gschem-sym-3.png"><img src="media/geda/gschem-sym-3.png" class="medialeft" title="Step 3" alt="Step 3" /></a>From the menu <strong>Add→Attribute</strong>
+</p>
+<ul>
+<li class="level1"><div class="li"> Add a <strong>net</strong> attribute with value <strong>Vcc:8</strong> Select <strong>Show Name &amp; Value</strong> and make it invisible.</div>
+</li>
+<li class="level1"><div class="li"> Add a <strong>net</strong> attribute with value <strong>Vee:4</strong> Make it <strong>Show Name &amp; Value</strong> and invisible.</div>
+</li>
+<li class="level1"><div class="li"> Make the <strong>device</strong> attribute be just <strong>OPAMP</strong>.</div>
+</li>
+</ul>
+
+<p>
+ Clean up by moving these new attributes as shown.
+</p>
+
+<p>
+Change the footprint default if you wish. When all the edits are done, itâ??s very important when editing symbols to do a <strong>Edit→Symbol Translate</strong> to zero before saving. Do that and then save the symbol with <strong>File→Save Page</strong> I made the <strong>footprint</strong> default be <strong>DIP8</strong> because I have that as a custom element.
+</p>
+
+</div>
+
+<h5><a name="run_gschem_with_the_new_symbol" id="run_gschem_with_the_new_symbol">Run gschem with the New Symbol</a></h5>
+<div class="level5">
+
+<p>
+<a href="media/geda/one-sch-3.png" class="media" target="_blank" title="geda:one-sch-3.png"><img src="media/geda/one-sch-3.png" class="medialeft" title="one.sch" alt="one.sch" /></a> Run <strong>gschem one.sch</strong>. Select and delete with the <strong>Delete</strong> key both opamps. Also delete the <strong>Vcc</strong> and <strong>Vee</strong> symbols that were connected to them. Bring up the Add Components window and from the <strong>gschem-sym</strong> library which should now have your new custom symbol, place two of the <strong>opamp-dual.sym</strong> Move them to the right place on the schematic and donâ??t forget to mirror and rotate the bottom opamp as before. Edit the attributes of each opamp giving them the same attributes they had, that is make the <strong>footprint</strong> be <strong>DIL 8 300</strong>, add a <strong>value</strong> attribute of <strong>TL072</strong>, and make the <strong>refdes</strong> of both opamps be <strong>U101</strong>. Make the <strong>slot</strong> of the second opamp be <strong>2</strong>. If you donâ??t make the attributes the same as they were before, gsch2pcb will think it is a different component and delete the existing <strong>DIL</strong> package from the layout. If you did everything right, running gsch2pcb should give:
+</p>
+<pre class="code">~/gaf/myproject1$ gsch2pcb project
+Found a cpinlist head with a netname! [Vcc]
+Found a cpinlist head with a netname! [Vee]
+Found a cpinlist head with a netname! [Vcc]
+Found a cpinlist head with a netname! [Vee]
+Found a cpinlist head with a netname! [Vcc]
+Found a cpinlist head with a netname! [Vee]
+Found a cpinlist head with a netname! [Vcc]
+Found a cpinlist head with a netname! [Vee]
+No elements to add so not creating board.new.pcb
+</pre>
+
+<p>
+ Where the gEDA gnetlist program seems a bit â??excitedâ?? about finding the new Vcc and Vee <strong>net</strong> attributes we just added, and a new netlist was generated. Now I think the schematic looks cleaner. And if you run <strong>pcb board.pcb</strong> and load the new netlist and then optimize the rats nest, PCB should tell you the board is complete which means connecting the opamp power pins via the <strong>net</strong> attribute has worked.
+</p>
+
+<p>
+For complete details on making symbols, read through the <a href="geda-scg.html" class="wikilink1" title="geda-scg.html">Symbol Creation Document</a> on the <a href="geda-documentation.html" class="wikilink1" title="geda-documentation.html">gEDA Documentation</a> page.
+</p>
+
+</div>
+<!-- SECTION "Custom gschem Symbols" [29761-34014] -->
+<h2><a name="custom_file_elements" id="custom_file_elements">Custom file elements</a></h2>
+<div class="level2">
+
+<p>
+You can create custom <strong>file elements</strong> in the middle of running PCB on any layout or you can run PCB just for making the element. As a demonstration, lets make a custom element for a 1N4004 diode. There are axial packages provided by PCB, but we want to be sure the drill size will be right for this 1 amp diode with slightly fatter leads. It needs about a 42 mil (#58) drill.
+</p>
+
+<p>
+ Run <strong>pcb</strong> and the first thing to do is select the <strong>Signal</strong> routing style and edit its sizes (press the <strong>Route Style</strong> button) Set the <strong>Via hole</strong> size to 42 and the <strong>via size</strong> to 70 or larger as you like. Select <strong>Screen→Grid setting→25 mil</strong> and <strong>Screen→Enable visible grid</strong>. Zoom in a couple of steps, then make the element: <a href="media/geda/pcb-el-1.png" class="media" target="_blank" title="geda:pcb-el-1.png"><img src="media/geda/pcb-el-1.png" class="medialeft" title="Step 1" alt="Step 1" /></a>
+</p>
+<ul>
+<li class="level1"><div class="li"> Select the <strong>VIA</strong> tool and place two vias 400 milsapart.</div>
+</li>
+<li class="level1"><div class="li"> With the mouse on the left via, hit the <strong>n</strong> key and give the via the name <strong>1</strong>. Give the right via the name <strong>2</strong></div>
+</li>
+<li class="level1"><div class="li"> Pin 1 will be the cathode and this must agree with the pin numbers in your diode gschem symbol.</div>
+</li>
+</ul>
+
+<p>
+ <a href="media/geda/pcb-el-2.png" class="media" target="_blank" title="geda:pcb-el-2.png"><img src="media/geda/pcb-el-2.png" class="mediaright" title="Step 2" alt="Step 2" /></a>
+</p>
+<ul>
+<li class="level1"><div class="li"> Select the <strong>Silk</strong> layer and the <strong>LINE</strong> tool.</div>
+</li>
+<li class="level1"><div class="li"> Draw the component outline as shown with line width set to 10 mils and the grid setting set to 10 mils.</div>
+</li>
+<li class="level1"><div class="li"> Draw the left fat cathode indicator with three lines after setting the line width to 20 mils.</div>
+</li>
+<li class="level1"><div class="li"> Donâ??t let silk layer lines overlap solder pads. </div>
+</li>
+</ul>
+
+<p>
+Select the vias and the outline just drawn using the <strong>SEL</strong> tool and finish making the element:
+</p>
+<ul>
+<li class="level1"><div class="li"> <strong>Buffer→Cut selection to buffer</strong> and move the cursor to the center of the left via and click.</div>
+</li>
+<li class="level1"><div class="li"> <strong>Buffer→Convert buffer to element</strong></div>
+</li>
+<li class="level1"><div class="li"> <strong>Buffer→Save buffer elements to file</strong> and navigate to <strong>~/gaf/pcb-elements</strong> and save the element as <strong>D400-1A</strong> since itâ??s a package for a 1A diode with 400 mil spaced pins. Or give it any descriptive name you like.</div>
+</li>
+</ul>
+
+<p>
+ <strong>Note:</strong> if you save the element with a name which is the same as a <strong>m4 element</strong>, gsch2pcb will preferentially use the m4 element unless you give gsch2pcb the –use-files (or -f) option. You may put <strong>use-files</strong> in a project file if you want to always give priority to using <strong>file elements</strong>. The m4 element names appear to use upper case, so you could also avoid the problem by using lower case in your file element names. Also, the only way I know to make the pin 1 of the symbol square is to edit the D400-1A file manually and change the square flag in the Pin â??1â?? line. For example, change the line:
+</p>
+<pre class="code"> Pin(0 0 70 20 70 42 "" "1" 0x00000001)
+to:
+Pin(0 0 70 20 70 42 "" "1" 0x00000101)
+</pre>
+
+<p>
+ You can now use <strong>D400-1A</strong> in a gschem schematic symbol <strong>footprint</strong> attribute and gsch2pcb will find it provided you have made the <strong>packages</strong> link described in the <strong>Setup</strong> section. If you have not made that link, you can still tell gsch2pcb about the elements directory with a line in a project file:
+</p>
+<pre class="code">elements-dir ~/gaf/pcb-elements
+</pre>
+
+<p>
+ Possibly youâ??ve noticed, but there are some things not right about the <strong>myproject1</strong> example. For one thing, silk layer lines are overlapping solder pads on some of the elements, and for another, the transistor is backwards on the layout! You otherwise shouldnâ??t have a problem like this when working with gschem and PCB, but transistor pin numbering can be confusing. If you will be using transistors in your designs, hereâ??s a description of my approach to making sure my gschem transistor symbol pin numbering is coordinated with PCB element pin numbers: <a href="geda-transistor_guide.html" class="wikilink1" title="geda-transistor_guide.html">transistor guide.</a>
+</p>
+
+<p>
+ From the transistor guide, you can see that the problem here is that the <strong>TO92</strong> element has its pins numbered in the less common (3,2,1) configuration while the <strong>2N3904-1.sym</strong> is like a npn-ebc symbol which needs a (1,2,3) numbering. You can see the 2N3904 pin numbers in gschem by hitting the <strong>en</strong> keys (and donâ??t be confused by the <strong>pinseq</strong> attribute that nearly covers up the <strong>pinnumber</strong>). And in PCB, you can see the <strong>TO92</strong> pin numbers by hitting the <strong>d</strong> key with the mouse over the element. To be sure you are seeing pin numbers and not pin names, select <strong>Screen→pinout shows number</strong>.
+</p>
+
+<p>
+ I have libraries with transistor symbols and elements that you might find useful, so as a convenience you can get your custom libraries initially populated by installing my <a href="http://www.geda.seul.org/docs/current/tutorials/gsch2pcb/gsch2pcb-libs-20040110.tar.gz"; class="urlextern" title="http://www.geda.seul.org/docs/current/tutorials/gsch2pcb/gsch2pcb-libs-20040110.tar.gz"; rel="nofollow"> gschem/PCB libraries </a>. Untar them under ~/gaf to mirror the setup of our example and there will also be a <strong>~/gaf/pcb-elements.Readme</strong> which documents the PCB elements. <i>Note: as of 1/10/2004 Iâ??ve corrected the tarball pcb elements to not overlap solder pads with silk layer lines.</i> If you untar them somewhere else, you will need to make sure that gschem knows about them with gschemrc/gnetlistrc <strong>component-library</strong> lines and that gsch2pcb can find them with <strong>elements-dir</strong> lines in a project file.
+</p>
+
+<p>
+ If you install them, you can fix Q201 in <strong>two.sch</strong> by changing its footprint to <strong>TO-92</strong> which is my custom element with (1,2,3) pin numbering. Then run <strong>gsch2pcb project</strong> and then <strong>pcb board.pcb</strong> and load the new element for the transistor. In the next images, <strong>two.sch</strong> is showing the <strong>footprint</strong> attribute visible to emphasize it, and it also shows a new symbol for the 2N3904 which I created from my custom <strong>npn-ebc.sym</strong> as described in my transistor guide. In the updated board.pcb layout, if you compare the outline appearance of the transistor to the original layout you see that the orientation is now correct and that silk layer lines donâ??t overlap the solder pads. I also changed the <strong>footprint</strong> attribute for resistors R102 and R103 in <strong>one.sch</strong> to my custom 1/8 watt <strong>R0w8</strong> and 1/4 watt <strong>R0w4</strong> elements to illustrate the differences in style you can have with custom elements. You can also see the R101 style after its footprint was changed to <strong>0.125W_Carbon_Resistor</strong> as suggested above. As you evaluate the differences in these styles, Iâ??ll mention that for my custom elements I wanted to maximize room to display value and refdes text (the 0.125W… element body could be a little larger) and I wanted the solder pad diameter a little larger so it will be more forgiving of board fabrication technique. Also, the resistor pin spacing for my <strong>R0w4</strong> is slightly less than in <strong>R025</strong> to improve component density.
+</p>
+
+<p>
+<a href="media/geda/two-sch-2.png" class="media" target="_blank" title="geda:two-sch-2.png"><img src="media/geda/two-sch-2.png" class="medialeft" title="two.sch" alt="two.sch" /></a> <a href="media/geda/board-6.png" class="media" target="_blank" title="geda:board-6.png"><img src="media/geda/board-6.png" class="mediaright" title="pcb" alt="pcb" /></a>
+</p>
+
+</div>
+<!-- SECTION "Custom file elements" [34015-40476] -->
+<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>
+First, some words about how to find out about the default <strong>m4 elements</strong> available in PCB. I think there is some documention forthcoming in the PCB project, but at this point I donâ??t know of anything to refer you to and you canâ??t just look at filenames as you can for the <strong>file elements</strong>. Not only that, but many of these elements require arguments and you need to determine what they are. So for now all I can say is that the best way to find out whatâ??s available is to read the m4 element files and for this you need to know where the PCB m4 files install location is. As of PCB 20031113 this install directory will most likely be <strong>/usr/share/pcb/m4</strong> or <strong>/usr/local/share/pcb/m4</strong>, while on earlier PCB versions it could be <strong>/usr/X11R6/lib/X11/pcb/m4</strong> (run <em>gsch2pcb –help</em> or <em>gsch2pcb -v project</em> to see which of these directories gsch2pcb is using). But if your install is somewhere else you will have to track it down. By the way, if the m4 directory <em>is</em> somewhere different from the above three, then gsch2pcb wonâ??t be finding your <strong>m4 elements</strong> in the above examples and you will need to add the correct m4 directory to your <strong>project</strong> file with a line like:
+</p>
+<pre class="code">m4-pcbdir /path/to/pcb/m4
+</pre>
+
+<p>
+ Just read the <strong>.inc</strong> files in the m4 install directory. For example, in the <strong>misc.inc</strong> file you will find the <strong>R025</strong> element weâ??ve used and it starts out with:
+</p>
+<pre class="code"># -------------------------------------------------------------------
+# the definition of a resistor (0.25W) package
+# $1: canonical name
+# $2: name on PCB
+# $3: value
+define(`PKG_R025',
+`Element(0x00 "$1" "$2" "$3" 120 30 0 100 0x00)
+(
+...
+</pre>
+
+<p>
+ The information you can extract from this is that a m4 <strong>PKG_</strong> macro named <strong>R025</strong> is being defined and it takes 3 arguments. Now, all PCB <strong>m4 element</strong> macros take at least three arguments and these are automatically filled in by gsch2pcb with the gschem attributes <strong>footprint</strong> for <strong>canonical name</strong>, <strong>refdes</strong> for <strong>name on PCB</strong>, and <strong>value</strong> for <strong>value</strong>. The â??canonical nameâ?? used in these m4 files is just an older way of referring to the current PCB usage of <strong>description</strong> as mentioned above in the <strong>Terminology</strong> section. Since these args are automatically filled in, you donâ??t need to specify any additional args to <strong>R025</strong> when you use it as a gschem <strong>footprint</strong>. But now look at the very next m4 element define in <strong>misc.inc</strong>:
+</p>
+<pre class="code"># -------------------------------------------------------------------
+# the definition of a SIL package without a common pin
+# $1: canonical name
+# $2: name on PCB
+# $3: value
+# $4: number of pins
+define(`PKG_SIL',
+`define(`MAXY', `eval(`$4' * 100 -50)')
+Element(0x00 "$1" "$2" "$3" 160 10 3 100 0x00)
+(
+...
+</pre>
+
+<p>
+ From this you can determine there is a <strong>SIL</strong> package you can use as a <strong>footprint</strong>. It has 4 arguments, but only the first three are handled automatically so there is one argument you must give when using it. You get a flash of insight and realize this is a â??Single In Lineâ?? package! So, instead of the <strong>CONNECTOR 2 1</strong> element specifying 1 column we used in our example above, you might think we could have used <strong>SIL 2</strong>. But you would be wrong! Because if you read the macro body you will see that if the argument is <strong>2</strong> the second forloop canâ??t handle it. In fact, it will only work for arguments >= 4. If you ever run gsch2pcb and it appears stuck in an infinite loop, a m4 macro argument problem is likely the cause. As you look through <strong>misc.inc</strong> hereâ??s a summary of what you will find as possible elements you can use:
+</p>
+<pre class="code">Package Args you need to supply
+SD 1 number of pins of a ZIP package
+MULTIWATT15 0
+R025 0
+SIL 1 number of pins (we know now must be >= 4)
+CSIL 1 number of pins
+QFP132 0
+LED 1 diameter of LED
+DIODE_LAY 1 pin separation
+AXIAL_LAY 1 pin separation
+CRYSTAL 1 package width
+OSC 0
+ISA8 0
+OVEN_OSC 0
+RADIAL_CAN 1
+SMD_BASE 2 length and width of surface mount device
+SMD_CHIP 1 package length
+</pre>
+
+<p>
+ And so on for the other <strong>.inc</strong> files…
+</p>
+
+<p>
+ The reality is that the m4 setup is less user friendly (you canâ??t create the elements graphically) and more complicated (you need to understand m4 macros) than the simple <strong>file element</strong> approach. So for most of your custom elements I suggest you are better off staying with <strong>file elements</strong>. However, with the m4 macro method a single element definition that takes arguments gives you a programmable element which can be very useful for large pin count packages. It is particularly nice for IC packages with variable widths and number of pins, so a good example of using a custom <strong>m4 element</strong> would be to copy and modify to our taste the existing m4 macro for IC packages (the <strong>DIL</strong> macro) into a m4 file gsch2pcb will search. The destination m4 file can be any of these:
+</p>
+<ul>
+<li class="level1"><div class="li"> <strong>pcb.inc</strong> in our <strong>myproject1</strong> directory and the custom element will be local to this project.</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> <strong>~/.pcb/pcb.inc</strong> and the element will be known to all of our projects.</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> <strong>/path/to/anyfile</strong> if this path is made known to gsch2pcb by adding a line to a project file like:<pre class="code">m4-file /path/to/anyfile
+ </pre>
+
+<p>
+ Depending on whether you want the file known only to this project, to all of your projects, or to all projects of all users, this line may be added to any of the project files:
+</p>
+<pre class="code">~/gaf/myproject1/project
+~/.gsch2pcb
+/usr/local/etc/gsch2pcb
+/etc/gsch2pcb
+ </pre>
+</div>
+</li>
+</ul>
+
+<p>
+For this tutorial, Iâ??ll use the first <strong>pcb.inc</strong> way, so copy over the existing macro file:
+</p>
+<pre class="code">cd /usr/local/share/pcb/m4 (or /usr/share/pcb/m4 or /usr/X11R6/lib/X11/pcb/m4)
+cp dil.inc ~/gaf/myproject1/pcb.inc
+cd ~/gaf/myproject1
+</pre>
+
+<p>
+ Now, edit the <strong>pcb.inc</strong> file you just copied and cut everything out except for the PKG_DIL macro. Change the name of the package to something like PKG_DILFAT because the change weâ??ll make will be to make larger diameter pins. Actually, we could leave the name alone and our new definition would override the old one, but for now letâ??s go with the new name. Change the pin diameter from <strong>60</strong> to <strong>70</strong> on the <strong><acronym title="Personal Identification Number">PIN</acronym></strong> lines. When done, this should be the entire contents of the new <strong>pcb.inc</strong> file:
+</p>
+<pre class="code"># -------------------------------------------------------------------
+# the definition of a dual-inline package N and similar types
+# $1: canonical name
+# $2: name on PCB
+# $3: value
+# $4: number of pins
+# $5: package size (300, 600, 900 + 100 for socket space)
+#
+define(`PKG_DILFAT',
+`define(`MAXY', `eval(`$4' / 2 * 100)')
+define(`MAXX', `eval(`$5' + 100)')
+define(`CENTERX', `eval(MAXX / 2)')
+Element(0x00 "$1" "$2" "$3" eval(CENTERX + 20) 100 3 100 0x00)
+(
+forloop(`i', 1, eval($4 / 2),
+`PIN(50, eval(i * 100 -50), 70, 28, i)
+')
+forloop(`i', 1, eval($4 / 2),
+`PIN(eval(MAXX -50), eval(MAXY - i * 100 +50), 70, 28, eval(i + $4/2))
+')
+ElementLine(0 0 0 MAXY 10)
+ElementLine(0 MAXY MAXX MAXY 10)
+ElementLine(MAXX MAXY MAXX 0 10)
+ElementLine(0 0 eval(CENTERX - 50) 0 10)
+ElementLine(eval(CENTERX + 50) 0 MAXX 0 10)
+ElementArc(CENTERX 0 50 50 0 180 10)
+Mark(50 50)
+)')
+</pre>
+
+<p>
+ Run <strong>gschem one.sch</strong> and edit the <strong>footprint</strong> attribute of the opamps to be <strong>DILFAT 8 300</strong>. Then run <strong>gsch2pcb project</strong> and gsch2pcb will remove the <strong>DIL</strong> element from <strong>board.pcb</strong> and add into <strong>board.new.pcb</strong> a new <strong>DILFAT</strong> element from your custom m4 file <strong>pcb.inc</strong>. Run <strong>pcb board.pcb</strong> and load the <strong>board.new.pcb</strong> into your layout. Move the new element with its fatter pins to the location left vacant by the removal of the old element.
+</p>
+
+</div>
+<!-- SECTION "Custom m4 elements (Requires gsch2pcb >= 1.0)" [40477-48164] -->
+<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">
+
+<p>
+The above examples are oriented towards a single user with projects and custom gschem and PCB libraries under his home directory. Hereâ??s a way to set up for multiple users who need to share resources:
+</p>
+<ul>
+<li class="level1"><div class="li"> Put site wide custom PCB <strong>file elements</strong> under, for example, <strong>/usr/local/share/pcb/pcb-elements</strong>. Make this directory searched by gsch2pcb for all users by putting a line into <strong>/etc/gsch2pcb</strong> or <strong>/usr/local/etc/gsch2pcb</strong>:<pre class="code">elements-dir /usr/local/share/pcb/pcb-elements
+ </pre>
+
+<p>
+ If there are any site wide custom PCB <strong>m4 element</strong> files, for example, <strong>/usr/local/share/pcb/pcb.inc</strong>, add another line into <strong>/etc/gsch2pcb</strong> or <strong>/usr/local/etc/gsch2pcb</strong>:
+</p>
+<pre class="code">m4-file /usr/local/share/pcb/pcb.inc
+ </pre>
+</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> If the default PCB m4 install is not <strong>/usr/local/share/pcb/m4, /usr/share/pcb/m4,</strong> or <strong>/usr/X11R6/lib/X11/pcb/m4</strong>, then make the install location known to all users of gsch2pcb by putting into <strong>/etc/gsch2pcb</strong> or <strong>/usr/local/etc/gsch2pcb</strong> the line:<pre class="code">m4-pcbdir /path/to/pcb/m4
+ </pre>
+
+<p>
+ If the m4 program is gm4 instead of m4, add to the gsch2pcb file:
+</p>
+<pre class="code">m4-command gm4
+ </pre>
+</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> If there are site wide custom gschem symbols under some directory, you will have to edit the system gschemrc and gnetlistrc files and add <strong>component-library</strong> lines for them.</div>
+</li>
+</ul>
+
+<p>
+With the above, users will have access to site wide libraries and only need to put in a design <strong>project</strong> file lines for <strong>schematics</strong> and <strong>output-name</strong>. But they also are free to have their own additional user and/or project specific symbol and element libraries.
+</p>
+
+</div>
+<!-- SECTION "Multi-user Setup (requires gsch2pcb >= 1.0)" [48165-49802] -->
+<h2><a name="pc_board_fabrication" id="pc_board_fabrication">PC Board Fabrication</a></h2>
+<div class="level2">
+
+<p>
+The tutorial should cover pcb fabrication too.
+</p>
+
+</div>
+
+<h5><a name="photo-lithography" id="photo-lithography">Photo-lithography</a></h5>
+<div class="level5">
+
+<p>
+ Use File→Export layout→ps to make a postscript file suitable for printing on a transparency. Note the presence of the â??mirrorâ?? and â??ps-invertâ?? options which you may need depending on your process.
+</p>
+
+<p>
+Open the ps file and print only the pages that you will actually need for fabrication. There are a large number of pages here, many of which you may not need.
+</p>
+
+<p>
+If you find that your pads and traces donâ??t print on the same page, or are placed on the wrong side you need to check the settings under File→Preferences→Layers to group the layers appropriately and place them on the correct side.
+</p>
+
+</div>
+
+<h5><a name="machining" id="machining">Machining</a></h5>
+<div class="level5">
+
+<p>
+ <a href="http://www.lpkf.com"; class="urlextern" title="http://www.lpkf.com"; rel="nofollow">LPKF</a> (and probably other companies) have a pcb plotting machines that accept gerber files. These files can be produced by choosing File→Export Layout→gerber which produces a large number of files. The files can be viewed using <a href="http://geda.seul.org/tools/gerbv/index.html"; class="urlextern" title="http://geda.seul.org/tools/gerbv/index.html"; rel="nofollow">gerbv</a> and the visualization saved. Once you are satisfied with the output gerber files just hand them off to whomever controls the pcb plotting machine and wait for the boards to be completed!
+</p>
+
+</div>
+<!-- SECTION "PC Board Fabrication" [49803-] --></body>
+</html>
diff --git a/docs/wiki/geda-gsch2pcb_tutorial_releasenotes.html b/docs/wiki/geda-gsch2pcb_tutorial_releasenotes.html
new file mode 100644
index 0000000..fc4aa9c
--- /dev/null
+++ b/docs/wiki/geda-gsch2pcb_tutorial_releasenotes.html
@@ -0,0 +1,70 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="release_notes_for_gsch2pcb_tutorial" id="release_notes_for_gsch2pcb_tutorial">Release Notes for gsch2pcb Tutorial</a></h1>
+<div class="level1">
+
+<p>
+These are the relase notes to the <a href="geda-gsch2pcb_tutorial.html" class="wikilink1" title="geda-gsch2pcb_tutorial.html">gsch2pcb tutorial</a>.
+</p>
+<ul>
+<li class="level1"><div class="li"> Starting with the PCB-20050609 snapshot, PCB has a new Gtk user interface which replaces the old Xaw interface and this tutorial will describe using the Gtk interface. If you are using the Xaw PCB, you can look at this <a href="http://www.geda.seul.org/docs/current/tutorials/gsch2pcb/tutorial-old.html"; class="urlextern" title="http://www.geda.seul.org/docs/current/tutorials/gsch2pcb/tutorial-old.html"; rel="nofollow"> older version of this tutorial,</a> which is also not up to date with info on the gEDA gafrc files.</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> If you have a gschem version less than 20030525 these tutorial examples may not work as expected.</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> If you have gEDA version 20030901 installed such that you are using its included gsch2pcb 0.9 and you are getting an error:<pre class="code">ERROR: Unbound variable: open-output-pipe</pre>
+
+<p>
+ then the problem is syntax in <em>gnet-gsch2pcb.scm</em> that worked in guile 1.4 but does not work in guile 1.6. Youâ??ll need to upgrade to using at least gsch2pcb 1.0.1 to solve this problem.
+</p>
+</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> As of about 1/9/2004 <acronym title="Concurrent Versions System">CVS</acronym> PCB versions changed to using a hi resolution output file format which will require using at least gsch2pcb-1.4.</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> <strong> Mini Changelog</strong></div>
+<ul>
+<li class="level2"><div class="li"> 5/16/2007 Imported into wiki. Weâ??ll see if itâ??s worth keeping this Changelog up to date after this.</div>
+</li>
+<li class="level2"><div class="li"> 6/23/2005 Added gafrc file info to setup section. Updated the tutorial to use the Gtk PCB.</div>
+</li>
+<li class="level2"><div class="li"> 1/10/2004 Corrected my sloppy PCB file elements which had silkscreen lines overlapping solder pads.</div>
+</li>
+<li class="level2"><div class="li"> 12/23/2003 Added comments about new <acronym title="Concurrent Versions System">CVS</acronym> PCB versions which have the m4 and newlib directories default installed under /usr/share or /usr/local/share.</div>
+</li>
+</ul>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Release Notes for gsch2pcb Tutorial" [1-1644] -->
+<h2><a name="source_of_the_original_document" id="source_of_the_original_document">Source of the original document</a></h2>
+<div class="level2">
+
+<p>
+The tutorial was originally prepared by Bill Wilson (bill–at–gkrellm.net). <a href="http://members.dslextreme.com/users/billw/gsch2pcb/gsch2pcb.html"; class="urlextern" title="http://members.dslextreme.com/users/billw/gsch2pcb/gsch2pcb.html"; rel="nofollow">gsch2pcb Home</a>
+</p>
+
+</div>
+<!-- SECTION "Source of the original document" [1645-] --></body>
+</html>
diff --git a/docs/wiki/geda-gschem2pcb_readme.html b/docs/wiki/geda-gschem2pcb_readme.html
new file mode 100644
index 0000000..8d4f38d
--- /dev/null
+++ b/docs/wiki/geda-gschem2pcb_readme.html
@@ -0,0 +1,154 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="gschem2pcb_readme" id="gschem2pcb_readme">gschem2pcb README</a></h1>
+<div class="level1">
+<pre class="code">------------------------------------------------------------------
+JM Routoure. routoure@xxxxxxxxxxxxxx
+17/01/2000
+
+I would like to thank Stefan Petersen for debuging the scheme program.
+
+-------------------------------------------------------------------
+
+
+This document describes how to install (section I) and use (section II) the
+gschem2pcb package. Section III describes some of the footprints
+available in pcb
+
+The purpose of this package is to interface gschem with pcb. It uses a scheme
+program and a script.
+
+
+Section I : Installation.
+
+1. Untar the gschem2pcb.tar. You must obtain 3 files gschem2pcb.sh,
+GNET-PCBboard.scm and the README file.
+
+2. Move gschem2pcb.sh in a directory which is in your PATH (/usr/local/bin for
+instance ). Be sure that gschem2pcb.sh can be executed (chmod 755 gschem2pcb.sh)
+
+3. Move GNET-PCBboard.scm in the share directory of your gEDA distribution.
+Normally, it should be /usr/local/share/gEDA/scheme.
+
+4. Modify the common.m4 file of the pcb program (should be found in
+/usr/X11R6/lib/X11/pcb/m4/) like this : the include keywords at the end of the
+file must be replace by
+
+include(/usr/X11R6/lib/X11/pcb/m4/connector.inc)
+include(/usr/X11R6/lib/X11/pcb/m4/dil.inc)
+include(/usr/X11R6/lib/X11/pcb/m4/misc.inc)
+include(/usr/X11R6/lib/X11/pcb/m4/plcc.inc)
+include(/usr/X11R6/lib/X11/pcb/m4/to.inc)
+include(/usr/X11R6/lib/X11/pcb/m4/qfp.inc)
+
+5. Edit the ~/.gEDA/gschemrc file and be sure that the following line exists :
+(attribute-name "footprint")
+
+
+6. Be sure that grep, sed and gawk are installed. That's all..
+
+
+Section II : using gschem2pcb.
+
+1. With gschem, create a schematic. All the device you want to have in pcb must
+have a Uref attribute. The footprint that you want to use in pcb are indicated
+by the footprint attribute (see section III for the description of the footprint
+in pcb)
+
+Be careful that the attributes Uref, name, value and device must not contain
+space char.
+--------------------------------------------------------
+
+2. Save your work (ultralownoise.sch for instance -ambitious design!) and type in a shell
+
+ gschem2pcb.sh ultralownoise.sch.
+
+note : the gschem file must end by .sch
+
+Error messages will appear if some space characters are found in the
+attributes Uref, name, value and device and if the name of the footprint was not
+found. Warning, pcb files are created even if errors occur!
+
+- if ultralownoise.pcb does not exist, it will be created. A netlist file
+ultralownoise.net will also be created. In pcb, load the pcb (load layout). All
+the footprints will appears at the top-left corner of the windows. Load the
+netlist (load netlist file) and type the key "w". Place the footprints and type
+"o" to optimize the rastnet. See the pcb documentation for details.
+
+- if ultralownoise.pcb exists, a ultralownoise.new.pcb file should be
+created. It should contain only the new device that have been added in the
+schematic since the last save of the ultralownoise.pcb file. Use "load layout
+data to paste buffer" to include the new footprints in the pcb file. The nestlist
+file is also updated so read it again.
+
+
+Section III. Description of the name of the footprint in pcb.
+pcb uses macro to define the footprints. For DIL packages, for instance, 2
+arguments are used to indicate the number of pins and the width in mil of the
+footprint. In gschem the footprint attribute of a 300 mil width and 8 pins DIL
+is:
+DIL 8 300.
+Warning, for that attribute, you have to included the space char!
+
+In the following. I describe the footprint attribute that are to be used in
+gschem for the footprint avalaible in pcb. N stands
+for the number of pins, W the width in mil, L the length in mil and D the
+diameter in mil
+CONNECTOR ROWS COLS # single connector
+DIN41_651LAY N # DIN 41.651 laying
+DIN41_651STAND N # DIN 41.651 standing
+SUBD_LAY_BASE N # SUB-D connector laying
+SUBD_MALE_LAY_BASE N # SUB-D connector male laying
+SUBD_FEMALE_LAY_BASE N # SUB-D connector female laying
+DIL N W # dual-inline standard
+D N # dual inline with W=244
+DW N # dual inline with W=419
+SD N # SD (ZIP)
+MULTIWATT15 # 15 pins multiwatt footprint
+R025 # standard 1/4W resistor !now attributes
+SIL N # SIL
+CSIL # SIL package with a common pin
+QFP132 # QFP132 flat pack
+LED D # standing LED
+DIODE_LAY L # laying diode
+AXIAL_LAY L # standard axial footprint
+CRYSTAL W # crystal package
+OSC # a can oscillator
+ISA8 # 8 bit ISA Slot card
+OVEN_OSC # ovenized-oscillator package
+RADIAL_CAN W # a radial capcitor package
+PLCC N # pllc
+PLCC N add # pllc with additionnal border add
+QFP N add # qfp with additionnal border add
+No additional parameters for the to footprints
+TO3_90
+TO3_45
+TO5
+TO92
+TO126
+TO126LAY-WIDE
+TO126STAND-WIDE
+TO220
+TO220LAY-WIDE
+TO220STAND
+TO220STAND-WIDE
+
+</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-gschem_mp.html b/docs/wiki/geda-gschem_mp.html
new file mode 100644
index 0000000..5710d10
--- /dev/null
+++ b/docs/wiki/geda-gschem_mp.html
@@ -0,0 +1,132 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="gschem_man-page" id="gschem_man-page">gschem man-page</a></h1>
+<div class="level1">
+<pre class="code">gschem(1) 20031231 gschem(1)
+
+
+
+NAME
+ gschem - gEDA/gaf Schematic Capture
+
+SYNOPSIS
+ gschem [-q] [-v] [-t] [-r rcfilename] [-s scriptfilename] [-o output-
+ filename] [-p] [schematic1 ... schematicN]
+
+DESCRIPTION
+ gschem is the schematic capture program which is part gEDA (GPL Elec-
+ tronic Design Automation) toolset. This program is used to draw elec-
+ tronic schematics. Schematics consist of standard symbols (which are
+ either part of a standard library or created by the user) which repre-
+ sent the various gates and components. These components are then
+ interconnected by nets (wires). Schematics may be printed to a
+ PostScript file for printing or further conversion to other output for-
+ mats.
+
+ gschem is also the symbol creation editor. All the standard methods of
+ creating schematics are used in the creation of symbols. There are a
+ few special rules when creating symbols, so please refer to the (non-
+ existant as of now) symbol creation document.
+
+ Please read the official documentation (very minimal at this point) on
+ how to use gschem, since this man page just describes the command line
+ arguments and a few examples on how to run gschem.
+
+
+OPTIONS
+ gschem accepts the following options:
+
+ -q Quiet mode on. This mode turns off all warnings/notes/mes-
+ sages. (optional)
+
+ -v Verbose mode on. This mode gives as much feedback to the user
+ as possible. (optional)
+
+ -t Print out more information when using mouse strokes. With this
+ command line flag and the middle button configured for mouse
+ strokes, gschem will output the stroke sequence numbers as the
+ user executes strokes. These numbers can be used to define new
+ strokes in the system-gschemrc file.
+
+ -r filename
+ Specify a rc filename. Normally gschem searches for the sys-
+ tem-gschemrc, then ~/.gEDA/gschemrc, and finally for a gschemrc
+ in the current directory. This options allows the user to
+ specify an additional rc file which is read after all the other
+ rc files are read. (optional)
+
+ -s filename
+ Specify a guile script to be executed at startup. (optional)
+
+ -o filename
+ Specify a filename for postscript output. This command line
+ argument is useful when running gschem from a shell script and
+ with a guile script. The filename can be changed through the
+ print dialog box.
+
+ -p Automatically place the window, especially useful if running
+ gschem from the command line and generating output.
+
+ schematic1 [... schematicN]
+ Schematic file to be loaded. Specifing a schematic file is
+ optional. If multiple schematic files are specified they are
+ read in sequentially and put on seperate pages. It is impor-
+ tant that the schematic(s) follow all the options (ie last).
+
+
+EXAMPLES
+ These examples assume that you have a schematic called stack_1.sch in
+ the current directory
+
+ To run gschem and then interact with the program:
+
+ ./gschem
+
+ To run gschem in interactive mode but load a sample schematic:
+
+ ./gschem adders_1.sch
+
+ To run gschem and load up all schematics in the current subdirectory:
+
+ ./gschem *.sch
+
+
+ENVIRONMENT
+ No environment variables are used.
+
+
+AUTHOR
+ Ales Hvezda and many others
+
+
+SEE ALSO
+ gnetlist(1), gsymcheck(1)
+
+COPYRIGHT
+ Copyright © 1999-2004 Ales Hvezda
+
+ This document can be freely redistributed according to the terms of the
+ GNU General Public License version 2.0
+
+
+
+
+Version December 31st, 2003 gschem(1)</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-gschem_ug.fr.html b/docs/wiki/geda-gschem_ug.fr.html
new file mode 100644
index 0000000..673f062
--- /dev/null
+++ b/docs/wiki/geda-gschem_ug.fr.html
@@ -0,0 +1,3573 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#guide_de_l_utilisateur_gschem_geda" class="toc">Guide de l'utilisateur gschem gEDA</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#about_this_document" class="toc">About this document ...</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#introduction" class="toc">Introduction</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#overview" class="toc">Overview</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#resources" class="toc">Resources</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#how_to_ask_questions" class="toc">How To Ask Questions</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#installing_gschem" class="toc">Installing gschem</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#latest_stable" class="toc">Latest Stable</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#geda_tools_suite_cd-rom" class="toc">"gEDA Tools Suite" CD-ROM</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#debian_distributions" class="toc">Debian distributions</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#red_hat_distributions" class="toc">Red Hat distributions</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#mac_osx_distributions" class="toc">Mac OSX distributions</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#cvs_unstable_testing" class="toc">CVS Unstable/Testing</a></span></div></li>
+</ul>
+</li>
+<li class="level1"><div class="li"><span class="li"><a href="#configuring_gschem" class="toc">Configuring gschem</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#gschemrc" class="toc">gschemrc</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#gafrc" class="toc">gafrc</a></span></div></li>
+</ul>
+</li>
+<li class="level1"><div class="li"><span class="li"><a href="#lancer_gschem" class="toc">Lancer gschem</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#confirming_gschem_is_installed" class="toc">Confirming gschem is installed</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#the_shell_prompt" class="toc">The Shell Prompt</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#backups" class="toc">Backups</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#classic_linux_backups" class="toc">Classic Linux backups</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#incremental_backups" class="toc">Incremental backups</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#relevant_configuration_settings" class="toc">Relevant configuration settings</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#on-line_documentation" class="toc">On-line documentation</a></span></div></li>
+</ul>
+</li>
+<li class="level1"><div class="li"><span class="li"><a href="#electrical_connectivity" class="toc">Electrical Connectivity</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#components_symbols_objects_attributes" class="toc">Components & Symbols & Objects & Attributes</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#components" class="toc">Components</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#symbols" class="toc">Symbols</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#objects" class="toc">Objects</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#attributes" class="toc">Attributes</a></span></div></li>
+</ul>
+</li>
+<li class="level1"><div class="li"><span class="li"><a href="#the_main_window" class="toc">The Main Window</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#the_status_window" class="toc">The Status Window</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#the_schematic_file" class="toc">The Schematic File</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#the_symbol_file" class="toc">The Symbol File</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#symbol_libraries" class="toc">Symbol Libraries</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#the_log_file" class="toc">The Log File</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#grips" class="toc">Grips</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#menu_operations" class="toc">Menu Operations</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#file" class="toc">File</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#new_window_fw" class="toc">New Window (fw)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#new_page_fn" class="toc">New Page (fn)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#open_page..._fo" class="toc">Open Page... (fo)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#close_page_pc" class="toc">Close Page (pc)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#revert_page_pr" class="toc">Revert Page (pr)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#save_page_fs" class="toc">Save Page (fs)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#save_page_as..._fa" class="toc">Save Page As... (fa)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#save_all_fl_fl" class="toc">Save All (fl) (fl)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#print..._fp" class="toc">Print... (fp)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#write_png..._fi" class="toc">Write PNG... (fi)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#execute_script..._ft" class="toc">Execute Script... (ft)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#close_window_fc" class="toc">Close Window (fc)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#quit_alt-q" class="toc">Quit (Alt-q)</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#edit" class="toc">Edit</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#undo_shift-u" class="toc">Undo (shift-u)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#redo_shift-r" class="toc">Redo (shift-r)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#select_mode_s" class="toc">Select Mode (s)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#edit..._ee" class="toc">Edit... (ee)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#edit_text..._ex" class="toc">Edit Text... (ex)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#copy_mode_ec" class="toc">Copy Mode (ec)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#move_mode_em" class="toc">Move Mode (em)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#delete_delete-key" class="toc">Delete (Delete-key)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#rotate_90_mode_er" class="toc">Rotate 90 Mode (er)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#mirror_mode_ei" class="toc">Mirror Mode (ei)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#slot..._e_shift-s" class="toc">Slot... (e shift-s)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#color..._eo" class="toc">Color... (eo)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#lock_el_unlock_e_shift-l" class="toc">Lock (el) / Unlock (e shift-l)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#line_width_type..._ew" class="toc">Line Width & Type... (ew)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#fill_type..._ef" class="toc">Fill Type... (ef)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#symbol_translate..._et" class="toc">Symbol Translate... (et)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#embed_component_picture_eb" class="toc">Embed Component/Picture (eb)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#unembed_component_picture_eu" class="toc">Unembed Component/Picture (eu)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#update_component_ep" class="toc">Update Component (ep)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#show_hide_inv_text_en" class="toc">Show/Hide Inv Text (en)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#make_inv_text_vis_ev" class="toc">Make Inv Text Vis (ev)</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#buffer" class="toc">Buffer</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#copy_into_1_2_3_4_5_yc" class="toc">Copy into 1/2/3/4/5 (yc)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#cut_into_1_2_3_4_5_yu" class="toc">Cut into 1/2/3/4/5 (yu)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#paste_from_1_2_3_4_5_yp" class="toc">Paste from 1/2/3/4/5 (yp)</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#view" class="toc">View</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#redraw_vr" class="toc">Redraw (vr)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#pan_x" class="toc">Pan (x)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#zoom_box_w" class="toc">Zoom Box (w)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#zoom_extents_ve" class="toc">Zoom Extents (ve)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#zoom_in_z" class="toc">Zoom In (z)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#zoom_out_z" class="toc">Zoom Out (Z)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#zoom_full_vf" class="toc">Zoom Full (vf)</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#page" class="toc">Page</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#manager..._pm" class="toc">Manager... (pm)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#next" class="toc">Next (>)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#previous" class="toc">Previous (<)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#new_pe" class="toc">New (pe)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#revert_pr" class="toc">Revert (pr)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#close_pc" class="toc">Close (pc)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#discard_pd" class="toc">Discard (pd)</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#add" class="toc">Add</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#component..._i" class="toc">Component... (i)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#net_n" class="toc">Net (n)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#bus_u" class="toc">Bus (u)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#attribute..._aa" class="toc">Attribute... (aa)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#text..._at" class="toc">Text... (at)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#line_l" class="toc">Line (l)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#box_b" class="toc">Box (b)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#circle_ai" class="toc">Circle (ai)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#arc_ar" class="toc">Arc (ar)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#pin_ap" class="toc">Pin (ap)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#picture..._ag" class="toc">Picture... (ag)</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#hierarchy" class="toc">Hierarchy</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#down_schematic_hd" class="toc">Down Schematic (Hd)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#down_symbol_hs" class="toc">Down Symbol (Hs)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#up_hu" class="toc">Up (Hu)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#documentation_ho" class="toc">Documentation (Ho)</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#attributes1" class="toc">Attributes</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#attach_ta" class="toc">Attach (ta)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#detach_td" class="toc">Detach (td)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#show_value_tv" class="toc">Show Value (tv)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#show_name_tn" class="toc">Show Name (tn)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#show_both_tb" class="toc">Show Both (tb)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#toggle_visibility_tt" class="toc">Toggle Visibility (tt)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#find_specific_text..._t_shift-f" class="toc">Find Specific Text... (t shift-f)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#hide_specific_text..._th" class="toc">Hide Specific Text... (th)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#show_specific_text..._t_shift-h" class="toc">Show Specific Text... (t shift-h)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#autonumber_text..._tu" class="toc">Autonumber Text... (tu)</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#options" class="toc">Options</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#text_size..._ot" class="toc">Text Size... (ot)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#toggle_grid_on_off_og" class="toc">Toggle Grid On/Off (og)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#toggle_snap_on_off_os" class="toc">Toggle Snap On/Off (os)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#snap_grid_spacing..._os" class="toc">Snap Grid Spacing... (oS)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#toggle_outline_box_oa" class="toc">Toggle Outline/Box (oa)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#toggle_net_rubberband_or" class="toc">Toggle Net/Rubberband (or)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#show_log_window_ol" class="toc">Show Log Window (ol)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#show_coord_window..._oc" class="toc">Show Coord Window... (oc)</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#help" class="toc">Help</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#about..._ha" class="toc">About... (ha)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#manual..._hm" class="toc">Manual... (hm)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#hotkeys..._hh" class="toc">Hotkeys... (hh)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#component..._ho" class="toc">Component... (Ho)</a></span></div></li>
+</ul>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"><span class="li"><a href="#appendix_a_--_heavy_vs_light_symbol_libraries" class="toc">Appendix A -- Heavy vs Light Symbol Libraries</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#appendix_b_--_printing_schematics_and_symbols" class="toc">Appendix B -- Printing Schematics and Symbols</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#appendix_c_--_writing_guile_scripts" class="toc">Appendix C -- Writing guile Scripts</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#appendix_d_--_i_want_to_build_a_printed_circuit_board" class="toc">Appendix D -- I Want To Build A Printed Circuit Board</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#appendix_e_--_i_want_to_simulate_my_design" class="toc">Appendix E -- I Want To Simulate My Design</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#appendix_f_--_change_gschemdoc_user-defined_preferences" class="toc">Appendix F -- Change gschemdoc User-Defined Preferences</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#appendix_g_--_breaking_a_large_symbol_into_smaller_symbols" class="toc">Appendix G -- Breaking a Large Symbol Into Smaller Symbols</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#appendix_h_--_definition_of_terms" class="toc">Appendix H -- Definition of Terms</a></span></div></li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="guide_de_l_utilisateur_gschem_geda" id="guide_de_l_utilisateur_gschem_geda">Guide de l'utilisateur gschem gEDA</a></h1>
+<div class="level1">
+
+<p>
+by: Ales Hvezda / September 21st, 2003
+</p>
+
+<p>
+The latest version of this document may be found at: <a href="http://geda.seul.org/wiki/geda:gschem_ug"; class="urlextern" title="http://geda.seul.org/wiki/geda:gschem_ug"; rel="nofollow">http://geda.seul.org/wiki/geda:gschem_ug</a>
+</p>
+
+<p>
+This document is released under the <a href="geda-gfdl.html" class="wikilink1" title="geda-gfdl.html">GNU Free Documentation License (GFDL)</a>.
+</p>
+
+<p>
+ Please report any errors/inconsistencies in this document by commenting in the Discussion area at the bottom of the associated page.
+</p>
+
+</div>
+<!-- SECTION "Guide de l'utilisateur gschem gEDA" [1-409] -->
+<h1><a name="about_this_document" id="about_this_document">About this document ...</a></h1>
+<div class="level1">
+
+<p>
+gEDA gschem Users Guide
+</p>
+
+<p>
+This document was generated using the LaTeX2HTML translator Version 2002-2-1 (1.70)
+</p>
+
+<p>
+Copyright © 1993, 1994, 1995, 1996, Nikos Drakos, Computer Based Learning Unit, University of Leeds. Copyright © 1997, 1998, 1999, Ross Moore, Mathematics Department, Macquarie University, Sydney.
+</p>
+
+<p>
+The command line arguments were: latex2html -local_icons gschem
+</p>
+
+<p>
+The translation was initiated by Ales Hvezda on 2005-08-20
+</p>
+
+</div>
+<!-- SECTION "About this document ..." [410-882] -->
+<h1><a name="introduction" id="introduction">Introduction</a></h1>
+<div class="level1">
+
+<p>
+This document describes the installation, configuration, and operation of the <strong>gschem</strong> application.<br/>
+ This document does not describe the process of generating schematics. For this, refer to the various tutorials on using the gEDA Tool Suite:
+</p>
+<ul>
+<li class="level1"><div class="li"> <a href="geda-gschem_warmup.html" class="wikilink1" title="geda-gschem_warmup.html">Bill Wilson's gschem warmup</a></div>
+</li>
+<li class="level1"><div class="li"> Bill Wilsonâ??s <a href="geda-gsch2pcb_tutorial.html" class="wikilink1" title="geda-gsch2pcb_tutorial.html">gschem and pcb tutorial</a></div>
+</li>
+<li class="level1"><div class="li"> â??Optical Proximity Sensor for Robots (Part 1), Simple PCB Design with the gEDA Suiteâ??, by Stuart Brorson (March 2006 Circuit Cellar article)</div>
+</li>
+<li class="level1"><div class="li"> <a href="http://www-mdp.eng.cam.ac.uk/urop05/files/gedalib/starting_gEDA.pdf"; class="urlextern" title="http://www-mdp.eng.cam.ac.uk/urop05/files/gedalib/starting_gEDA.pdf"; rel="nofollow">Starting with gEDA at the Cambridge University Engineering Department</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="http://www.brorson.com/gEDA/SPICE/t1.html"; class="urlextern" title="http://www.brorson.com/gEDA/SPICE/t1.html"; rel="nofollow">"Circuit simulation using gEDA and SPICE -- HOWTO" by Stuart Brorson</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="http://www.circuitcellar.com/magazine/176toc.htm"; class="urlextern" title="http://www.circuitcellar.com/magazine/176toc.htm"; rel="nofollow">"gEDA Design Suite for Linux" by Stuart Brorson, Ales Hvezda, & Dan McMahill (03 Mar 2005 Circuite Cellar article)</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="http://www.linuxjournal.com/article/8438"; class="urlextern" title="http://www.linuxjournal.com/article/8438"; rel="nofollow">"Circuit Design on Your Linux Box Using gEDA" by Stuart Brorson (29 November 2005 Linux Journal article)</a></div>
+</li>
+<li class="level1"><div class="li"> Optical Proximity Sensor for Robots (Part 1): Simple PCB Design with the gEDA Suite, by Stuart Brorson, Circuit Cellar magazine, March 2006 (Issue 188), p. 48</div>
+</li>
+<li class="level1"><div class="li"> And, of course, <a href="http://www.google.com/search?hl=en&lr=&q=gEDA+%22schematic+capture%22+tutorial&btnG=Search"; class="urlextern" title="http://www.google.com/search?hl=en&lr=&q=gEDA+%22schematic+capture%22+tutorial&btnG=Search"; rel="nofollow">Google is your friend</a>.</div>
+</li>
+</ul>
+
+<p>
+ Ce document suppose que vous comprenez les bases de la capture de schéma. Par exemple: vous comprenez ce quâ??un composant représente et que les liaisons et les bus interconnectent ces composants pour former un schéma, etc… For a basic understanding of the various work-flows available in the gEDA Tool Suite, please read the above tutorials. For more detailed understanding of specific tool issues, please refer to <a href="docs-20060124-gschem_ug-how_to_ask_questions.html" class="wikilink2" title="docs-20060124-gschem_ug-how_to_ask_questions.html">How To Ask Questions</a> and to the <a href="docs-20060124-gschem_ug-resources.html" class="wikilink2" title="docs-20060124-gschem_ug-resources.html">Resources</a>.
+</p>
+
+</div>
+<!-- SECTION "Introduction" [883-2837] -->
+<h1><a name="overview" id="overview">Overview</a></h1>
+<div class="level1">
+
+<p>
+<strong>gschem</strong> is the schematic capture program in the gEDA Tool Suite. Its purpose is to facilitate the graphical input of:
+</p>
+<ul>
+<li class="level1"><div class="li"> circuit schematics</div>
+</li>
+<li class="level1"><div class="li"> component symbols</div>
+</li>
+<li class="level1"><div class="li"> block diagrams</div>
+</li>
+</ul>
+
+<p>
+ Once <strong>gschem</strong> has been used to enter the symbols/schematics for your design, several gEDA Tool Suite â??utilityâ?? programs are used to extract information for other purposes:
+</p>
+<ul>
+<li class="level1"><div class="li"> <strong>gattrib</strong> – <strong>gattrib</strong> is a gEDA Tool Suite productivity aid. <strong>gattrib</strong> reads a [hierarchical set of] gschem schematic files and creates a spreadsheet showing all components in rows, with the associated component attributes listed in the columns. It allows the user to add, modify, or delete component attributes outside of <strong>gschem</strong>, and then save the .sch files.</div>
+</li>
+<li class="level1"><div class="li"> <strong>gnetlist</strong> – A tool that converts a [hierarchical set of] schematic files into an equivalent netlist (a textual representation of a schematic) in various formats. Various gnetlist back-ends are used to create:</div>
+<ul>
+<li class="level2"><div class="li"> Bill of Materials (BOM) files.</div>
+</li>
+<li class="level2"><div class="li"> Design Rule Checks (DRCs).</div>
+</li>
+<li class="level2"><div class="li"> Netlist files for use as input to various printed circuit board layout programs (e.g., Allegro, PADS, <strong>pcb</strong> (part of the gEDA Tool Suite), Protell, Tango, RACAL-REDAC, etc.).</div>
+</li>
+<li class="level2"><div class="li"> Files for input to SPICE simulation programs.</div>
+</li>
+<li class="level2"><div class="li"> VHDL code.</div>
+</li>
+<li class="level2"><div class="li"> Verilog code.</div>
+</li>
+<li class="level2"><div class="li"> etc.</div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> <strong>grenum</strong> – <strong>grenum</strong> is a gEDA Tool Suite productivity aid that will renumber the reference designators (i.e., refdes) in a [hierarchical set of] schematic files.</div>
+</li>
+<li class="level1"><div class="li"> <strong>gsch2pcb</strong> – The prefered method to create a netlist for the <strong>pcb</strong> printed circuit board layout tool (part of the gEDA Tool Suite).</div>
+</li>
+<li class="level1"><div class="li"> <strong>gspiceui</strong> – GNU Spice <acronym title="Graphical User Interface">GUI</acronym> (i.e., <strong>gspiceui</strong>) provides a <acronym title="Graphical User Interface">GUI</acronym> for freely available Spice electronic cicuit simulation engines (e.g., <strong>gnucap</strong> and <strong>ngspice</strong>). It uses <strong>gnetlist</strong> (to convert schematic files to net list files) and <strong>gwave</strong> (to display simulation results). gSchem is the preferred schematic capture tool.</div>
+</li>
+<li class="level1"><div class="li"> <strong>gsymcheck</strong> – A checker for symbols created with gEDA Tool Suite (e.g., <strong>gschem</strong>, <strong>tragesym</strong>, etc.).</div>
+</li>
+<li class="level1"><div class="li"> <strong>pcb</strong> – A tool for the layout of printed circuit boards.</div>
+</li>
+<li class="level1"><div class="li"> <strong>refdes_renum</strong> – Reads a [hierarchical set of] <strong>gschem</strong> schematic files and renumbers all reference designators. The reference designators are numbered starting with 1 and the old schematic file is replaced by the modified schematic file.</div>
+</li>
+<li class="level1"><div class="li"> <strong>tragesym</strong> – A python script that creates geda symbols from structured textfiles. The symbols usually need to be â??cleaned upâ?? in gschem.</div>
+</li>
+</ul>
+<table class="inline">
+ <tr>
+ <td> <a href="media/geda/gschem_workflow_01.jpg" class="media" target="_blank" title="geda:gschem_workflow_01.jpg"><img src="media/geda/gschem_workflow_01.jpg" class="media" alt="" /></a> </td>
+ </tr>
+</table>
+
+</div>
+<!-- SECTION "Overview" [2838-5418] -->
+<h1><a name="resources" id="resources">Resources</a></h1>
+<div class="level1">
+
+<p>
+The following on-line resources are useful for designers using <strong>gschem</strong>:
+</p>
+<ul>
+<li class="level1"><div class="li"> <a href="http://www.geda.seul.org/docs/current/tutorials/gsch2pcb/gschem-warmup.html"; class="urlextern" title="http://www.geda.seul.org/docs/current/tutorials/gsch2pcb/gschem-warmup.html"; rel="nofollow">Bill Wilson's gschem warmup tutorial</a> – If you are new to the gEDA tools, read this before you read Billâ??s â??Bill Wilsonâ??s gsch2pcb tutorialâ??.</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-gsch2pcb_tutorial.html" class="wikilink1" title="geda-gsch2pcb_tutorial.html">Bill Wilson's gschem and pcb tutorial</a> – If you are new to the gEDA tools, this tutorial will bring you up to speed quickly.</div>
+</li>
+<li class="level1"><div class="li"> <a href="http://www.circuitcellar.com/"; class="urlextern" title="http://www.circuitcellar.com/"; rel="nofollow">Circuit Cellar Magazine</a> – Practical, hands-on applications and solutions for embedded designers:</div>
+<ul>
+<li class="level2"><div class="li"> gEDA Design Suite for Linux, by Stuart Brorson, Ales Hvezda, & Dan McMahill, Circuit Cellar magazine, March 2005 (Issue 176), p. 12</div>
+</li>
+<li class="level2"><div class="li"> Optical Proximity Sensor for Robots (Part 1): Simple PCB Design with the gEDA Suite, by Stuart Brorson, Circuit Cellar magazine, March 2006 (Issue 188), p. 48</div>
+</li>
+<li class="level2"><div class="li"> Optical Proximity Sensor for Robots (Part 2): Open-Source PCB Layout Editor, by Stuart Borson, Circuit Cellar magazine, April 2006 (Issue 189), p. 40</div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> <a href="http://www.geda.seul.org/index.html"; class="urlextern" title="http://www.geda.seul.org/index.html"; rel="nofollow">gEDA Project home page</a> – The homepage for the gEDA Tools Suite. A rather mature site, includes (but not limited to):</div>
+<ul>
+<li class="level2"><div class="li"> <a href="http://www.geda.seul.org/news/index.html"; class="urlextern" title="http://www.geda.seul.org/news/index.html"; rel="nofollow">News</a> – from 2002</div>
+</li>
+<li class="level2"><div class="li"> <a href="http://www.geda.seul.org/screenshots/index.html"; class="urlextern" title="http://www.geda.seul.org/screenshots/index.html"; rel="nofollow">Screenshots</a> – <strong>gschem</strong> in action</div>
+</li>
+<li class="level2"><div class="li"> <a href="http://www.geda.seul.org/tools/index.html"; class="urlextern" title="http://www.geda.seul.org/tools/index.html"; rel="nofollow">Tools</a> – links to project homepages</div>
+</li>
+<li class="level2"><div class="li"> <a href="http://www.geda.seul.org/download.html"; class="urlextern" title="http://www.geda.seul.org/download.html"; rel="nofollow">Download</a> – <acronym title="International Organization for Standardization">ISO</acronym> images, binaries, and sources</div>
+</li>
+<li class="level2"><div class="li"> <a href="http://www.geda.seul.org/mailinglist/index.html"; class="urlextern" title="http://www.geda.seul.org/mailinglist/index.html"; rel="nofollow">Lists</a> – e-mail list subscription and archives</div>
+</li>
+<li class="level2"><div class="li"> <a href="http://www.geda.seul.org/docs/index.html"; class="urlextern" title="http://www.geda.seul.org/docs/index.html"; rel="nofollow">Docs</a> – current gEDA/gaf documentation (not gEDA Tools Suite documentation), wiki, slide presentations</div>
+</li>
+<li class="level2"><div class="li"> <a href="http://www.geda.seul.org/developer.html"; class="urlextern" title="http://www.geda.seul.org/developer.html"; rel="nofollow">Devel</a> – nonymous <acronym title="Concurrent Versions System">CVS</acronym> access</div>
+</li>
+<li class="level2"><div class="li"> <a href="http://www.geda.seul.org/search.html"; class="urlextern" title="http://www.geda.seul.org/search.html"; rel="nofollow">Search</a> – by Google</div>
+</li>
+<li class="level2"><div class="li"> <a href="http://www.geda.seul.org/links.html"; class="urlextern" title="http://www.geda.seul.org/links.html"; rel="nofollow">Links</a> – links associated with gEDA, projects developed using gEDA Tools Suite, gEDA-related press</div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> <a href="http://sourceforge.net/tracker/?group_id=161080&atid=818426"; class="urlextern" title="http://sourceforge.net/tracker/?group_id=161080&atid=818426"; rel="nofollow">gEDA Bug Tracker</a> – On SourceForge</div>
+</li>
+<li class="level1"><div class="li"> <a href="http://geda.seul.org/dokuwiki/doku.php?id=geda"; class="urlextern" title="http://geda.seul.org/dokuwiki/doku.php?id=geda"; rel="nofollow">gEDA Project's Wiki</a> – All things related to the gEDA Tools Suite.</div>
+</li>
+<li class="level1"><div class="li"> <a href="http://www.gedasymbols.org"; class="urlextern" title="http://www.gedasymbols.org"; rel="nofollow">gedasymbols.org</a> – On-line repository of user-developed symbols for <strong>gschem</strong>, SPICE models, and footprints for <strong>pcb</strong>.</div>
+</li>
+<li class="level1"><div class="li"> John C. Lucianiâ??s proposed <a href="http://www.luciani.org/geda/pcb/footprint-name-spec.pdf"; class="urlextern" title="http://www.luciani.org/geda/pcb/footprint-name-spec.pdf"; rel="nofollow">Land Pattern Naming Convention</a> – Footprint naming conventions document, used by him, and often used by those submitting to the <a href="http://www.gedasymbols.org"; class="urlextern" title="http://www.gedasymbols.org"; rel="nofollow">gedasymbols.org</a> symbols/footprint repository.</div>
+</li>
+<li class="level1"><div class="li"> John C. Lucianiâ??s <a href="file:///shared/HomePages/dhart/index.html" class="urlextern" title="file:///shared/HomePages/dhart/index.html" rel="nofollow">PCB Footprints Library</a> – A rather inclusive collection of non-<acronym title="GNU General Public License">GPL</acronym> licensed footprints and the scripts used to create them.</div>
+</li>
+<li class="level1"><div class="li"> <a href="http://www.opencollector.org/"; class="urlextern" title="http://www.opencollector.org/"; rel="nofollow">OpenCollector</a> carries listings and news for free EDA software and circuit designs. Open Collector supports gEDA.</div>
+</li>
+<li class="level1"><div class="li"> <a href="http://alternatezone.com/electronics/files/PCBDesignTutorialRevA.pdf"; class="urlextern" title="http://alternatezone.com/electronics/files/PCBDesignTutorialRevA.pdf"; rel="nofollow">PCB Design Tutorial; RevA</a> – Document describing the process of taking a schematic to a pcb. Excellent for the beginner.</div>
+</li>
+<li class="level1"><div class="li"> <a href="http://pcblibraries.com/"; class="urlextern" title="http://pcblibraries.com/"; rel="nofollow">PCB Libraries website</a> – Advocates of the IPC standard Land Pattern (a.k.a., footprint) Naming Conventions and Land Pattern Calculators. A useful site if you have the money to subscribe to the services.</div>
+<ul>
+<li class="level2"><div class="li"> The free (windows-based) <a href="http://landpatterns.ipc.org/default.asp"; class="urlextern" title="http://landpatterns.ipc.org/default.asp"; rel="nofollow">IPC-7351 Land Pattern Viewer</a> is a very useful tool for viewing the latest IPC footprints.</div>
+</li>
+<li class="level2"><div class="li"> <a href="http://www.pcblibraries.com/resources/LibDoc.asp"; class="urlextern" title="http://www.pcblibraries.com/resources/LibDoc.asp"; rel="nofollow">CAD Data Files to be used with PCB Libraries' IPC-7351A LP Programs</a> – please note the license restrictions.</div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> <a href="http://www-mdp.eng.cam.ac.uk/urop05/files/gedalib/starting_gEDA.pdf"; class="urlextern" title="http://www-mdp.eng.cam.ac.uk/urop05/files/gedalib/starting_gEDA.pdf"; rel="nofollow">Starting with gEDA at the Cambridge University Engineering Department</a> – The Cambridge University Engineering Departmentâ??s tutorial for using gEDA.</div>
+</li>
+<li class="level1"><div class="li"> <a href="http://www.brorson.com/gEDA/"; class="urlextern" title="http://www.brorson.com/gEDA/"; rel="nofollow">Stuart Brorson's gEDA tools and tips</a> – gEDA related tools and information.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Resources" [5419-9678] -->
+<h1><a name="how_to_ask_questions" id="how_to_ask_questions">How To Ask Questions</a></h1>
+<div class="level1">
+
+<p>
+<strong>gschem</strong> is an OpenSource, community driven, development. As such, the emphasis has been on developing the gEDA Tools Suite, not on developing commercial-level documentation and support. Much of the burden on learning how to use the gEDA Tools Suite applications is placed on the user, who must understand the basics of electronics, Electronics Design Automation (EDA), and the terminology used in schematic capture, circuit simulation, and printed circuit board design.<br/>
+ As a typical OpenSource development, the gEDA Tools Suite development community provides timely and insightful response to user inquiries, but please perform the following steps before bothering the developers (they need to focus on making gEDA Tools Suite applications better, and you can actually learn to answer your own questions and become independent of the developers):
+</p>
+<ol>
+<li class="level1"><div class="li"> Read Rick Moenâ??s <a href="http://www.catb.org/~esr/faqs/smart-questions.html"; class="urlextern" title="http://www.catb.org/~esr/faqs/smart-questions.html"; rel="nofollow">How To Ask Questions The Smart Way</a>, about how to ask for help. This is a must read for everybody.</div>
+</li>
+<li class="level1"><div class="li"> Read this document. I know, itâ??s a lot to expect engineers to actually read a userâ??s guide. The latest version of this document is maintained on the gEDA web-site at <span class="hilited">TBD</span>. The information should be here. If it isnâ??t, comment to the fact in one of the on-line documentâ??s â??Discussionâ?? areas (at the bottom of each wiki-page). Helpful comments are clear, to the point, and may even contain the wording that should be inserted into the document.</div>
+</li>
+<li class="level1"><div class="li"> Read the <a href="http://geda.seul.org/dokuwiki/doku.php?id=geda:faq-gschem"; class="urlextern" title="http://geda.seul.org/dokuwiki/doku.php?id=geda:faq-gschem"; rel="nofollow">gschem Frequently Asked Questions (FAQ)</a> wiki-page. This on-line document is updated often to reflect user and developer experiences with <strong>gschem</strong>.</div>
+</li>
+<li class="level1"><div class="li"> Read the <a href="http://www.geda.seul.org/docs/current/index.html"; class="urlextern" title="http://www.geda.seul.org/docs/current/index.html"; rel="nofollow">gEDA/gaf Documentation</a>. This information was installed on your computer if the gEDA Tools Suite was installed from the gEDA Tools Suite CD-ROM.</div>
+</li>
+<li class="level1"><div class="li"> <a href="http://www.google.com"; class="urlextern" title="http://www.google.com"; rel="nofollow">Google</a> is your friend. People that have asked questions that obviously didnâ??t do any simple Google search will not be treated well when asking for help. This is particularly true if your problem is not unique to the gEDA Tools Suite applications.</div>
+</li>
+<li class="level1"><div class="li"> Ask for a pointer to the right direction. It is considered good â??net etiquetteâ?? to ask for a pointer to information, so that you can learn where such information can be found, rather than have someone search the information for you.</div>
+</li>
+<li class="level1"><div class="li"> If you are software literate, look at the source code to see what it is doing.</div>
+</li>
+<li class="level1"><div class="li"> Subscribe to the gEDA e-mail lists (i.e., you can only post to the e-mail lists if you are a subscriber). Then:</div>
+<ol>
+<li class="level2"><div class="li"> Start reading recent messages in the <a href="http://archives.seul.org/geda/user/"; class="urlextern" title="http://archives.seul.org/geda/user/"; rel="nofollow">geda-user e-mail list archives</a>. Get a feel for the listâ??s ettiquite so that you learn how to properly ask questions.</div>
+</li>
+<li class="level2"><div class="li"> Search the archives for issues similar to yours. You may find the question has been asked of the developers and users before, and answered.</div>
+</li>
+<li class="level2"><div class="li"> In the event that you can find no information concerning your problem, submit a concise description of the problem and a request for the type of help you are requesting.</div>
+</li>
+</ol>
+</li>
+</ol>
+
+</div>
+<!-- SECTION "How To Ask Questions" [9679-12860] -->
+<h1><a name="installing_gschem" id="installing_gschem">Installing gschem</a></h1>
+<div class="level1">
+
+<p>
+As a mature OpenSource project, the gEDA Tools Suite and its components have been installed on many Linux distributions. The following are by no means the only methods of installing the gEDA Tools Suite and/or its components.
+</p>
+
+</div>
+<!-- SECTION "Installing gschem" [12861-13119] -->
+<h2><a name="latest_stable" id="latest_stable">Latest Stable</a></h2>
+<div class="level2">
+
+<p>
+<strong>gschem</strong> is a component of the gEDA/gaf set of tools which tend to integrate together in the development and maintenance of schematics and symbols. The term â??gafâ?? stands for â??<em class="u">g</em>EDA <em class="u">a</em>nd <em class="u">f</em>riendsâ??). The gEDA/gaf applications are actually rather stable, and receive significant testing prior to release.<br/>
+ There are multiple methods of installing <strong>gschem</strong>. The appropriate method depends on your distribution. See the following for some examples.
+</p>
+
+</div>
+<!-- SECTION "Latest Stable" [13120-13604] -->
+<h3><a name="geda_tools_suite_cd-rom" id="geda_tools_suite_cd-rom">"gEDA Tools Suite" CD-ROM</a></h3>
+<div class="level3">
+
+<p>
+The recommended method is installation from the â??gEDA Tools Suiteâ?? CD-ROM, gratefully prepared by Stuart Brorson. The latest version of this CD-ROM is available on-line for free download as an <acronym title="International Organization for Standardization">ISO</acronym> image from the <a href="http://www.geda.seul.org/download.html"; class="urlextern" title="http://www.geda.seul.org/download.html"; rel="nofollow">gEDA Downloads</a> web-page. Simply burn this <acronym title="International Organization for Standardization">ISO</acronym> image to a CD-ROM using your favorite CD burning software (e.g., K3b, …). Insert the CD-ROM, and if your computer supports autodetection of the CD-ROM, the built-in installation wizzard will launch. This wizzard will first check if your computer has some required software (informing you if you donâ??t and optionally installing these if you want), then build all of the â??gEDA Tool Suiteâ?? applications (including <strong>gschem</strong>) from source. The whole process can take 2 hours on a slower computer.
+</p>
+
+<p>
+If the installation wizzard did not launch, enter as follows to install the gEDA Tool Suite for access by all users on this computer (i.e., when prompted for the installation directory, enter something like: â??/usr/local/gEDA-20060124â??): <pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0"><strong>sudo sh /media/cdrecorder/installer –log –verbose</strong></font></pre>
+</p>
+
+<p>
+The above command requires superuser permissions configured for the user invoking the command. If you do not have the proper permissions to execute this command, ask your administrator to install the gEDA Tool Suite for you.
+</p>
+
+<p>
+If the installation wizzard did not launch, enter as follows to install the gEDA Tool Suite for access by just the user doing the installation(i.e., when prompted for the installation directory, accept the default "/home/{login id}/geda-installâ??): <pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0"><strong>sh /media/cdrecorder/installer –log –verbose</strong></font></pre>
+</p>
+
+</div>
+<!-- SECTION "gEDA Tools Suite CD-ROM" [13605-15291] -->
+<h3><a name="debian_distributions" id="debian_distributions">Debian distributions</a></h3>
+<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.
+</p>
+
+</div>
+<!-- SECTION "Debian distributions" [15292-15640] -->
+<h3><a name="red_hat_distributions" id="red_hat_distributions">Red Hat distributions</a></h3>
+<div class="level3">
+
+<p>
+For Red Hat distributions (and possibly others) you may wish to download the latest RPM binaries]] prepared by Wojciech Kazubski.
+</p>
+
+</div>
+<!-- SECTION "Red Hat distributions" [15641-15803] -->
+<h3><a name="mac_osx_distributions" id="mac_osx_distributions">Mac OSX distributions</a></h3>
+<div class="level3">
+
+<p>
+For Mac OSX 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 Fink binaries</a> prepared by Charles Lepple.
+</p>
+
+</div>
+<!-- SECTION "Mac OSX distributions" [15804-15983] -->
+<h2><a name="cvs_unstable_testing" id="cvs_unstable_testing">CVS Unstable/Testing</a></h2>
+<div class="level2">
+
+<p>
+For those already familiar with the gEDA/gaf applications on the â??gEDA Tools Suiteâ?? CD-ROM, access to the <acronym title="Concurrent Versions System">CVS</acronym> repository is available. This is the latest developer source-code version of the application.<br/>
+ Installation from <acronym title="Concurrent Versions System">CVS</acronym> is appropriate for those:
+</p>
+<ul>
+<li class="level1"><div class="li"> Seeking a solution to a specific problem that was submitted to the development team, to test the â??fixâ?? so that the developers can be informed that the â??fixâ?? works.</div>
+</li>
+<li class="level1"><div class="li"> With significant working knowledge of the â??gEDA Tools Suiteâ?? and industry expertise, wishing to test the latest version of the application(s) prior to the next release. This usually requires access to several existing designs known to work in the current stable release of the â??gEDA Tools Suiteâ?? <acronym title="International Organization for Standardization">ISO</acronym> image, so that comparisons can be made and issues brought to the attention of the developer/user community (via the e-mail lists).</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "CVS Unstable/Testing" [15984-16874] -->
+<h1><a name="configuring_gschem" id="configuring_gschem">Configuring gschem</a></h1>
+<div class="level1">
+
+<p>
+Assume that you have installed the gEDA Tools Suite from CD-ROM (the most common installation method), and that you are ready to configure <strong>gschem</strong> to your personal likes. When installing, you were prompted for the path where the gEDA executables would be placed. The default was the <strong>/home/{login id}/geda-install</strong> directory, where {login id} is the username you logged into your account with, but you may have changed this to another directory on the computer. This directory is referred to below as the <strong>{binary-install-path}</strong> because this is where the gEDA binary executables are placed. If you forgot where the binaries were installed, simply issue the following command to find where <strong>gschem</strong> is installed (in this case the {binary-install-path} is <strong>/usr/local/gEDA-20060124</strong>): <pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">% which gschem
+/usr/local/gEDA-20060124/bin/gschem
+%</font></pre>
+</p>
+
+<p>
+The gEDA Tools Suite applications follow normal Unix/Linux conventions for placement of configuration files; there are usually system-wide, user-wide, and project-specific configuration settings. The system-wide settings are placed in a sub-directory of the {binary-install-path}. The user-wide settings are placed in the userâ??s home directory, also known as the login directory (referred to in Unix/Linux parlance as the <strong>$HOME</strong> directory). The project-specific settings are placed in a project-specific directory.<br/>
+
+</p>
+
+<p>
+Now that we know the above, we can configure <strong>gschem</strong>.<br/>
+ <strong>gschem</strong> is highly configurable. All configuration is handled through the following resource files (written using the GNU Guile programming language, an interpreter for Scheme, a version of Lisp):
+</p>
+<ul>
+<li class="level1"><div class="li"> <strong>system-gschemrc</strong>: The system-wide initialization file for <strong>gschem</strong>. Installed in the {binary-install-path}/share/gEDA/system-gschemrc file, it is required for <strong>gschem</strong> to run. Users should not modify this file, but should override the settings in this file by creating their own $HOME/gschemrc file and/or â??pwdâ??/gschemrc file and putting the new settings in those files. The {binary-install-path} directory is where your gEDA/gaf executables were installed, including <strong>gschem</strong>. Depends on your install method. Refer to <a href="docs-20060124-gschem_ug-installing_gschem.html" class="wikilink2" title="docs-20060124-gschem_ug-installing_gschem.html">Installing gschem</a> for more details.</div>
+</li>
+<li class="level1"><div class="li"> <strong>$HOME/gschemrc</strong>: The per-user initialization file for <strong>gschem</strong>. Created by the user in the userâ??s home directory. Settings placed in this file will override settings in the system-gschemrc file. Users should put settings in this file they want to apply to all of their sessions, such as (to change the default black background color scheme to a light background color scheme):</div>
+</li>
+</ul>
+
+<p>
+<pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">; Load up a color scheme
+(load (string-append gedadatarc "/gschem-lightbg")) ; light background</font></pre>
+</p>
+<ul>
+<li class="level1"><div class="li"> <strong>â??pwdâ??/gschemrc</strong>: The per-project initialization file for <strong>gschem</strong>. Created by the user in the userâ??s project directory. Settings placed in this file will override settings in both the system-gschemrc file and the $HOME/gschemrc file. Users should put settings in this file they want to apply to this particular project, such as (to autonumber reference designators when components are placed on the schematic):</div>
+</li>
+</ul>
+
+<p>
+<pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">; Comment in this scheme code if you want automatic numbering when
+; placing new component and copying components
+;
+(load (string-append gedadata "/scheme/auto-uref.scm"))
+(add-hook! add-component-hook auto-uref)</font></pre>
+</p>
+<ul>
+<li class="level1"><div class="li"> <strong>system-gafrc</strong>: The system-wide initialization file for gEDA/gaf applications (includes <strong>gschem</strong>, <strong>gnetlist</strong>). Installed in the {binary-install-path}/share/gEDA/system-gafrc file, it is required for <strong>gschem</strong> to run. Users should not modify this file, but should override the settings in this file by creating their own $HOME/gafrc file and/or â??pwdâ??/gafrc file and putting the new settings in those files. The {binary-install-path} directory is where your gEDA/gaf executables were installed, including <strong>gschem</strong>. Depends on your install method. Refer to <a href="docs-20060124-gschem_ug-installing_gschem.html" class="wikilink2" title="docs-20060124-gschem_ug-installing_gschem.html">Installing gschem</a> for more details.</div>
+</li>
+<li class="level1"><div class="li"> <strong>$HOME/gafrc</strong>: The per-user initialization file for gEDA/gaf applications. Created by the user in the userâ??s home directory. Settings placed in this file will override settings in the system-gafrc file. Users should put settings in this file they want to apply to all of their sessions. </div>
+</li>
+<li class="level1"><div class="li"> <strong>â??pwdâ??/gafrc</strong>: The per-project initialization file for the gEDA/gaf applications. Created by the user in the userâ??s project directory. Settings placed in this file will override settings in both the system-gafrc file and the $HOME/gafrc file. Users should put settings in this file they want to apply to this particular project. Settings such as the <strong>component-library</strong> or <strong>source-library</strong> keywords go into this file.</div>
+</li>
+<li class="level1"><div class="li"> <strong>gschem-gtkrc</strong>: Installed in the {binary-install-path}/share/gEDA/gschem-gtkrc file. Used to define the font for all gtk+ widgets in <strong>gschem</strong>.</div>
+</li>
+</ul>
+
+<p>
+ A few comments about changing the files:
+</p>
+<ul>
+<li class="level1"><div class="li"> Donâ??t break any guile syntax rules. Doing so will cause the scheme interpreter (guile) to stop interpreting.</div>
+</li>
+<li class="level1"><div class="li"> To add a setting to the $HOME/gschemrc file (or to the â??pwdâ??/gschemrc file), copy the settingâ??s text from the {binary-install-directory}/share/gEDA/system-gschemrc file to the $HOME/gschemrc file (or the â??pwdâ??/gschemrc file) and make the setting change there.</div>
+</li>
+<li class="level1"><div class="li"> To add a setting to the $HOME/gafrc file (or the â??pwdâ??/gafrc file), copy the relevant settingâ??s text from the {binary-install-directory}/share/gEDA/system-gafrc file to the $HOME/gafrc file (or the â??pwdâ??/gafrc file) and make the setting change there.</div>
+</li>
+<li class="level1"><div class="li"> Keywords/defaults always override what came before, with the exception of cumulative keywords (like component-library).</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Configuring gschem" [16875-22595] -->
+<h2><a name="gschemrc" id="gschemrc">gschemrc</a></h2>
+<div class="level2">
+
+<p>
+The {binary-install-path}/share/gEDA/system-gschemrc file is well commented. Read this file for more details on the settings available.<br/>
+ Some of the settings appropriate for override (by placing in either the userâ??s $HOME/gschemrc file or the projectâ??s â??pwdâ??/gschemrc file) are:
+</p>
+
+</div>
+<!-- SECTION "gschemrc" [22596-22897] -->
+<h2><a name="gafrc" id="gafrc">gafrc</a></h2>
+<div class="level2">
+
+<p>
+The {binary-install-path}/share/gEDA/system-gafrc file is well commented. Read this file for more details on the settings available.<br/>
+ Some of the settings appropriate for override (by placing in either the userâ??s $HOME/gafrc file or the projectâ??s â??pwdâ??/gafrc file) are:
+</p>
+
+</div>
+<!-- SECTION "gafrc" [22898-23187] -->
+<h1><a name="lancer_gschem" id="lancer_gschem">Lancer gschem</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "Lancer gschem" [23188-23216] -->
+<h2><a name="confirming_gschem_is_installed" id="confirming_gschem_is_installed">Confirming gschem is installed</a></h2>
+<div class="level2">
+
+<p>
+You should determine if <strong>gschem</strong> has been correctly installed on your Linux computer.<br/>
+ Log into your Linux account, and launch your favorite interactive shell. The different Linux distributions will usually offer more than one interactive shell such as xterm, gnome-term, konsole, etc.<br/>
+ You will see a shell prompt, which will depend on your Linux distribution and on your selection of interactive shell. It is common practice in Linux documentation to refer to the userâ??s interactive login shell prompt as â??<strong>%</strong>â??, and to refer to the superuserâ??s (i.e., user â??rootâ??) interactive login shell prompt as â??<strong>#</strong>â??.<br/>
+ At the shell prompt, enter the following commands to determine if <strong>gschem</strong> is installed:
+</p>
+
+<p>
+<pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">% <strong>echo $PATH</strong>
+<strong>/usr/local/gEDA-20060124/bin</strong>:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/home/<strong>gEDA</strong>/bin
+% <strong>which gschem</strong>
+/usr/local/gEDA-20060124/bin/gschem
+% <strong>ldd /usr/local/gEDA-20060124/bin/gschem</strong>
+ linux-gate.so.1 => (0x00345000)
+ libgeda.so.25 => /usr/local/gEDA-20060124/lib/libgeda.so.25 (0x00d7d000)
+ libguile.so.12 => /usr/lib/libguile.so.12 (0x00588000)
+ libguile-ltdl.so.1 => /usr/lib/libguile-ltdl.so.1 (0x00b62000)
+ libqthreads.so.12 => /usr/lib/libqthreads.so.12 (0x009f7000)
+ libpthread.so.0 => /lib/libpthread.so.0 (0x006d4000)
+ libcrypt.so.1 => /lib/libcrypt.so.1 (0x03266000)
+ libgdk-x11-2.0.so.0 => /usr/lib/libgdk-x11-2.0.so.0 (0x00c10000)
+ libgdk_pixbuf-2.0.so.0 => /usr/lib/libgdk_pixbuf-2.0.so.0 (0x006ac000)
+ libm.so.6 => /lib/libm.so.6 (0x008df000)
+ libpangoxft-1.0.so.0 => /usr/lib/libpangoxft-1.0.so.0 (0x003e7000)
+ libpangox-1.0.so.0 => /usr/lib/libpangox-1.0.so.0 (0x00a57000)
+ libpango-1.0.so.0 => /usr/lib/libpango-1.0.so.0 (0x00bd8000)
+ libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0x00a01000)
+ libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0x009fb000)
+ libdl.so.2 => /lib/libdl.so.2 (0x00906000)
+ libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x0448e000)
+ libgtk-x11-2.0.so.0 => /usr/lib/libgtk-x11-2.0.so.0 (0x06a81000)
+ libatk-1.0.so.0 => /usr/lib/libatk-1.0.so.0 (0x00c96000)
+ libSM.so.6 => /usr/X11R6/lib/libSM.so.6 (0x00d4f000)
+ libICE.so.6 => /usr/X11R6/lib/libICE.so.6 (0x00d33000)
+ libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00921000)
+ libc.so.6 => /lib/libc.so.6 (0x007b4000)
+ /lib/ld-linux.so.2 (0x00796000)
+ libXrandr.so.2 => /usr/X11R6/lib/libXrandr.so.2 (0x00bac000)
+ libXi.so.6 => /usr/X11R6/lib/libXi.so.6 (0x00cca000)
+ libXinerama.so.1 => /usr/X11R6/lib/libXinerama.so.1 (0x00bb2000)
+ libXft.so.2 => /usr/X11R6/lib/libXft.so.2 (0x00ad1000)
+ libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x00af8000)
+ libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0x00111000)
+ libXfixes.so.3 => /usr/X11R6/lib/libXfixes.so.3 (0x00d0d000)
+ libXcursor.so.1 => /usr/X11R6/lib/libXcursor.so.1 (0x00bcc000)
+ libXrender.so.1 => /usr/X11R6/lib/libXrender.so.1 (0x00ba2000)
+ libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x00a82000)
+ libpangoft2-1.0.so.0 => /usr/lib/libpangoft2-1.0.so.0 (0x05362000)
+ libexpat.so.0 => /usr/lib/libexpat.so.0 (0x0068b000)
+ libz.so.1 => /usr/lib/libz.so.1 (0x0090c000)</font></pre>
+</p>
+
+<p>
+The <strong>echo $PATH</strong> command displays the userâ??s current setting for the <strong>PATH</strong> environment variable. In the above example for a Fedora Core 4 installation, user <strong>gEDA</strong> executed the command and determined that the <strong>PATH</strong> included the /usr/local/gEDA-20060124/bin directory (this will differ depending on where you put the gEDA Tools Suite executables). If you installed from the gEDA Tools Suite CD-ROM (the most common method of installing the gEDA tools), as the last step of the installation wizzard you were prompted to:
+</p>
+<ol>
+<li class="level1"><div class="li"> Set your $PATH environment variable to {the directory in which the install wizzard installed gEDAâ??s executables}</div>
+</li>
+<li class="level1"><div class="li"> Set your $LD_LIBRARY_PATH environment variable to {the directory in which the install wizzard installed gEDAâ??s libraries}</div>
+</li>
+</ol>
+
+<p>
+ The <strong>which</strong> command displays the full path of a commandâ??s executable, searching for the command on the userâ??s list of directories, as defined in the <strong>PATH</strong> environment variable. In this case, it will return the full path to the <strong>gschem</strong> executable if it is on the userâ??s <strong>PATH</strong>. If this command does not return the full path to the <strong>gschem</strong> executable, make sure your <strong>PATH</strong> environment variable has been properly set.
+</p>
+
+<p>
+The <strong>ldd</strong> command displays shared libraries required by a program. All of the requested libraries must be found for <strong>gschem</strong> to run. Donâ??t be intimidated by the long list of libraries, this is common for mature Linux applications. If we had not received this output (or something very similar), we would have to check on our setting for the <strong>LD_LIBRARY_PATH</strong> environment variable.
+</p>
+
+<p>
+And of course, there is always attempting to just run <strong>gschem</strong> as follows: <pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">% <strong>gschem -h</strong>
+Usage: gschem [OPTIONS] schematic_filename1 ... schematic_filenameN
+ -q Quiet mode
+ -v Verbose mode on
+ -r filename Rc filename
+ -s filename Script (guile) filename
+ -o filename Output filename (for printing)
+ -p Automatically place the window
+ -t Print stroke information
+ -h Help; this message</font></pre>
+</p>
+
+<p>
+where we displayed the <strong>gschem</strong> help.
+</p>
+
+<p>
+If these commands do not return the expected results, then most likely the gEDA tools are not installed properly. Please see the appropriate INSTALL docs (which came with the gEDA distribution) for more info on installing the gEDA tools. If you installed from the gEDA Tools Suite CD-ROM, read the INSTALL document on the CD-ROM first.<br/>
+
+</p>
+
+</div>
+<!-- SECTION "Confirming gschem is installed" [23217-28922] -->
+<h2><a name="the_shell_prompt" id="the_shell_prompt">The Shell Prompt</a></h2>
+<div class="level2">
+<table class="inline">
+ <tr>
+ <td> <a href="media/geda/terminal_screenshot_001.jpg" class="media" target="_blank" title="geda:terminal_screenshot_001.jpg"><img src="media/geda/terminal_screenshot_001.jpg" class="media" alt="" /></a> </td>
+ </tr>
+ <tr>
+ <td> Figure 1 – gnome-terminal </td>
+ </tr>
+</table>
+
+<p>
+ You launch <strong>gschem</strong> from your favorite shell prompt (in this case, gnome-terminal on Fedora Core 4).<br/>
+ There are several command-line switches:
+</p>
+<ul>
+<li class="level1"><div class="li"> <strong>-q</strong> – Quiet mode<br/>
+ Turns on â??quiet modeâ??. Output (i.e., stdout and stderr) is not generated to the shell. Useful if calling <strong>gschem</strong> from a script (e.g., bash, sh, csh, etc.) to perform batch operations such as printing a large number of schematics or symbols.</div>
+</li>
+<li class="level1"><div class="li"> <strong>-v</strong> – Verbose mode ON<br/>
+ Generate verbose information. Not used very much in <strong>gschem</strong>.</div>
+</li>
+<li class="level1"><div class="li"> <strong>-r filename</strong> – Process additional configuration settings from <strong>filename</strong><br/>
+ <strong>filename</strong> is a file containing settings of the form found in either system-gschemrc or system-gafrc<br/>
+ In addition to the following files, <strong>gschem</strong> will process <strong>filename</strong> for additional configuration settings:<br/>
+ * {binary-install-path}/share/gEDA/system-gschemrc<br/>
+ * $HOME/gschemrc<br/>
+ * â??pwdâ??/gschemrc<br/>
+ * {binary-install-path}/share/gEDA/system-gafrc<br/>
+ * $HOME/gafrc<br/>
+ * â??pwdâ??/gafrc</div>
+</li>
+<li class="level1"><div class="li"> <strong>-s filename</strong> – Process <strong>filename</strong> as a guile script<br/>
+ The name of a script file (written in guile) for <strong>gschem</strong> to process.<br/>
+ Refer to <a href="docs-20060124-gschem_ug-app_b.html" class="wikilink2" title="docs-20060124-gschem_ug-app_b.html">Appendix B -- Printing Schematics and Symbols</a> and <a href="docs-20060124-gschem_ug-app_c.html" class="wikilink2" title="docs-20060124-gschem_ug-app_c.html">Appendix C -- Writing guile Scripts</a> for more details.<br/>
+ For example, in your $HOME/geda-sources/gedagaf/{gEDA Tools Suite version}/scripts/ directory is the <strong>print.scm</strong> file, a template script file directing <strong>gschem</strong> to generate a PostScript file of a schematic appropriate for printing. This <strong>print.scm</strong> file works as is, but you may want to customize it for your own needs. To print the schematic_1.sch schematic to the schematic_1.ps PostScript file from within a bash script, you would enter: <code>gschem -q -p -o schematic_1.ps -s print.scm schematic_1.sch</code><br/>
+ Then, simply use your favorite printing solution to print the file, such as: <code>lp schematic_1.ps</code><br/>
+ to a PostScript printer.</div>
+</li>
+<li class="level1"><div class="li"> <strong>-o filename</strong> – Output <strong>filename</strong> (e.g., for printing)<br/>
+ Specify the output filename. For example, as used to specify the Postscript filename in the example above.</div>
+</li>
+<li class="level1"><div class="li"> <strong>-p</strong> – Automatically place the window<br/>
+ Donâ??t wait for the windowmanager to place the window.<br/>
+ When a new window is opened, some window managers display the bounding box of the window and wait for the user to place the window manually. The "-pâ?? option avoids that, letting the window manager decide where to put the new window.</div>
+</li>
+<li class="level1"><div class="li"> <strong>-t</strong> – Print stroke information<br/>
+ </div>
+</li>
+<li class="level1"><div class="li"> <strong>-h</strong> – Help<br/>
+ Generate a short usage printout.</div>
+</li>
+</ul>
+
+<p>
+ Running <strong>gschem</strong> is straightforward once you have installed it on your GNU/Linux system.<br/>
+ Although <strong>gschem</strong> is a <acronym title="Graphical User Interface">GUI</acronym> application, <strong>gschem</strong> is meant to be launched from the command-line, as it takes command-line arguements (see Figure 1 above).<br/>
+ To open an empty schematic, run: <code><strong>% gschem</strong></code><br/>
+
+</p>
+
+<p>
+To open a specific schematic, run: <code><strong>% gschem schematic_name.sch</strong></code><br/>
+
+</p>
+
+<p>
+To open a list of schematics, run: <code><strong>% gschem schematic_1.sch schematic_2.sch, schematic_3.sch …</strong></code><br/>
+ or use wildcards to specify multiple filenames: <code><strong>% gschem schematic_*.sch</strong></code>
+</p>
+
+<p>
+As operations are performed in the <strong>gschem</strong> <a href="docs-20060124-gschem_ug-the_main_window.html" class="wikilink2" title="docs-20060124-gschem_ug-the_main_window.html">Main Window</a> the <strong>gschem</strong> <a href="docs-20060124-gschem_ug-the_status_window.html" class="wikilink2" title="docs-20060124-gschem_ug-the_status_window.html">Status Window</a> continues to output information, and the shell promptâ??s window continues to output information, consisting of:
+</p>
+<ul>
+<li class="level1"><div class="li"> …</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "The Shell Prompt" [28923-32457] -->
+<h2><a name="backups" id="backups">Backups</a></h2>
+<div class="level2">
+
+<p>
+There are two basic mechanisms in <strong>gschem</strong> for backing up schematics and symbols, classic Linux backups and incremental backups.
+</p>
+
+</div>
+<!-- SECTION "Backups" [32458-32609] -->
+<h3><a name="classic_linux_backups" id="classic_linux_backups">Classic Linux backups</a></h3>
+<div class="level3">
+
+<p>
+While creating and/or editing schematic file(s) or symbol file(s), snapshots are triggered by the <strong>autosave</strong> interval setting in the {binary-install-path}/share/gEDA/system-gschemrc file (see <a href="#relevant_configuration_settings" title=":geda:gschem_ug.fr.txt ↵" class="wikilink1">Relevant configuration settings</a> below). If the file has not been manually saved, and the interval expires (current default 2 minutes), the snapshot is saved the next time a change is made in the <strong>gschem</strong> main window (to either a schematic or to a symbol). The interval timer starts again as soon as the snapshot file(s) have been written, and once the timer expires the next change to the main window will trigger the snapshot to be written.<br/>
+ This snapshot includes all work up to, but not including, the last operation performed in the <strong>gschem</strong> main window. This is to allow for easier recovery from a crash that may have been caused by the last operation.<br/>
+ When <strong>gschem</strong> exits normally, the snapshot file(s) are deleted. So, if <strong>gschem</strong> were to crash, or not terminate normally for some reason (e.g., power failure, soda → keyboard, etc.), the shapshot file(s) would be found the next time <strong>gschem</strong> opened the file(s). <strong>gschem</strong> will display the following warning message when it finds a snapshot file associated with the schematic file(s) or symbol file(s) it opens: <pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">WARNING: Found and autosave backup file:
+ {full path to autosave file}
+
+The backup copy is newer than the schematic, so it seems you
+should load it instead of the original fil.
+Gschem usually makes backup copies automatically, and this
+situation happens when it crashed or it was forced to exit
+abruptely.
+
+If you load the original file, the backup file will be overwritten in
+the next autosave timeout and it will be lost.
+
+Do you want to load the backup file?</font></pre>
+</p>
+
+<p>
+The snapshots are saved to a file whose filename is constructed from the original filename (schematic or symbol) as follows:
+</p>
+<ul>
+<li class="level1"><div class="li"> add a "#" to the beginning of the original filename</div>
+</li>
+<li class="level1"><div class="li"> add a "#" to the end</div>
+</li>
+</ul>
+
+<p>
+ so that:
+</p>
+<ul>
+<li class="level1"><div class="li"> â??schematic_1.schâ?? becomes "#schematic_1.sch#"</div>
+</li>
+<li class="level1"><div class="li"> â??symbol.symâ?? becomes "#symbol.sym#"</div>
+</li>
+</ul>
+
+<p>
+ And yes, the "#" at the front and back of the filename are part of the filename.<br/>
+
+</p>
+
+<p>
+When the user does finally manually save the file, the original file (i.e., the file that was opened) is renamed to "{filename~}" and the latest snapshot file (i.e., "#{filename}#") gets copied as "{filename}". Note that this new "{filename}" file may not contain the latest information as displayed on the <strong>gschem</strong> main window, as the <strong>autosave</strong> interval timer may not have expired since the last change to the schematic/symbol.<br/>
+ When the user finally decides to close <strong>gschem</strong>, the latest snapshot file (i.e., "#{filename}#") is saved to the original file (i.e., "{filename}".<br/>
+ When you exit <strong>gschem</strong> and are prompted to save any unsaved schematic file(s) or symbol file(s), this constitutes a manual save.
+</p>
+
+</div>
+<!-- SECTION "Classic Linux backups" [32610-35516] -->
+<h3><a name="incremental_backups" id="incremental_backups">Incremental backups</a></h3>
+<div class="level3">
+
+</div>
+<!-- SECTION "Incremental backups" [35517-35550] -->
+<h3><a name="relevant_configuration_settings" id="relevant_configuration_settings">Relevant configuration settings</a></h3>
+<div class="level3">
+
+<p>
+There are the following configuration settings in the {binary-install-path}/share/gEDA/system-gschemrc file that effect backups:
+</p>
+<ul>
+<li class="level1"><div class="li"> <strong>undo-control</strong> : Controls if the undo feature is enabled or not.</div>
+</li>
+<li class="level1"><div class="li"> <strong>undo-levels</strong> : Determines the number of levels of undo. Basically this number decides how many backup schematics are saved.</div>
+</li>
+<li class="level1"><div class="li"> <strong>undo-type</strong> : Controls which kind of undo is used, disk or memory. The default is to use the disk as the storage medium (i.e., after every action the undo information is stored to a new file on disk). The disk mechanism is nice because you get that many backups of the schematic, written to disk as backups, so you should never lose a schematic due to a crash.</div>
+</li>
+<li class="level1"><div class="li"> <strong>autosave</strong> : Controls if a backup copy is made every â??intervalâ?? seconds. Note that a backup copy is only made when you make some change to the schematic, and there were more than â??intervalâ?? seconds from the last autosave. Autosaving will not be allowed if the â??intervalâ?? setting is set to zero.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Relevant configuration settings" [35551-36592] -->
+<h2><a name="on-line_documentation" id="on-line_documentation">On-line documentation</a></h2>
+<div class="level2">
+
+<p>
+For a listing of the various command line flags run â??<strong>gschem -h</strong>â??: <pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">% <strong>gschem -h</strong>
+Usage: gschem [OPTIONS] schematic_filename1 ... schematic_filenameN
+ -q Quiet mode
+ -v Verbose mode on
+ -r filename Rc filename
+ -s filename Script (guile) filename
+ -o filename Output filename (for printing)
+ -p Automatically place the window
+ -t Print stroke information
+ -h Help; this message</font></pre>
+</p>
+
+<p>
+For a detailed explanation of the command line flags look at the <strong>gschem</strong> man page: <pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">% <strong>man gschem</strong>
+gschem(1) 20031231 gschem(1)
+
+
+
+NAME
+ gschem - gEDA/gaf Schematic Capture
+
+SYNOPSIS
+ gschem [-q] [-v] [-t] [-r rcfilename] [-s scriptfilename] [-o output-
+ filename] [-p] [schematic1 ... schematicN]
+
+DESCRIPTION
+ gschem is the schematic capture program which is part gEDA (GPL Elec-
+ tronic Design Automation) toolset. This program is used to draw elec-
+ tronic schematics. Schematics consist of standard symbols (which are
+ either part of a standard library or created by the user) which repre-
+ sent the various gates and components. These components are then
+ interconnected by nets (wires). Schematics may be printed to a
+ PostScript file for printing or further conversion to other output for-
+ mats.
+
+ gschem is also the symbol creation editor. All the standard methods of
+ creating schematics are used in the creation of symbols. There are a
+ few special rules when creating symbols, so please refer to the (non-
+ existant as of now) symbol creation document.
+
+ Please read the official documentation (very minimal at this point) on
+ how to use gschem, since this man page just describes the command line
+ arguments and a few examples on how to run gschem.
+
+
+OPTIONS
+ gschem accepts the following options:
+
+ -q Quiet mode on. This mode turns off all warnings/notes/mes-
+ sages. (optional)
+
+ -v Verbose mode on. This mode gives as much feedback to the user
+ as possible. (optional)
+
+ -t Print out more information when using mouse strokes. With this
+ command line flag and the middle button configured for mouse
+ strokes, gschem will output the stroke sequence numbers as the
+ user executes strokes. These numbers can be used to define new
+ strokes in the system-gschemrc file.
+
+ -r filename
+ Specify a rc filename. Normally gschem searches for the sys-
+ tem-gschemrc, then ~/.gEDA/gschemrc, and finally for a gschemrc
+ in the current directory. This options allows the user to
+ specify an additional rc file which is read after all the other
+ rc files are read. (optional)
+
+ -s filename
+ Specify a guile script to be executed at startup. (optional)
+
+ -o filename
+ Specify a filename for postscript output. This command line
+ argument is useful when running gschem from a shell script and
+ with a guile script. The filename can be changed through the
+ print dialog box.
+
+ -p Automatically place the window, especially useful if running
+ gschem from the command line and generating output.
+
+ schematic1 [... schematicN]
+ Schematic file to be loaded. Specifing a schematic file is
+ optional. If multiple schematic files are specified they are
+ read in sequentially and put on seperate pages. It is impor-
+ tant that the schematic(s) follow all the options (ie last).
+
+
+EXAMPLES
+ These examples assume that you have a schematic called stack_1.sch in
+ the current directory
+
+ To run gschem and then interact with the program:
+
+ ./gschem
+
+ To run gschem in interactive mode but load a sample schematic:
+
+ ./gschem adders_1.sch
+
+ To run gschem and load up all schematics in the current subdirectory:
+
+ ./gschem *.sch
+
+
+ENVIRONMENT
+ No environment variables are used.
+
+
+AUTHOR
+ Ales Hvezda and many others
+
+
+SEE ALSO
+ gnetlist(1), gsymcheck(1)
+
+COPYRIGHT
+ Copyright © 1999-2004 Ales Hvezda
+
+ This document can be freely redistributed according to the terms of the
+ GNU General Public License version 2.0
+
+
+
+
+Version December 31st, 2003 gschem(1)</font></pre>
+</p>
+
+</div>
+<!-- SECTION "On-line documentation" [36593-41062] -->
+<h1><a name="electrical_connectivity" id="electrical_connectivity">Electrical Connectivity</a></h1>
+<div class="level1">
+
+<p>
+As you draw schematics you need be aware of what is considered to be electrically connected by the gEDA programs.<br/>
+ Nets which are visually connected to other nets are electrically connected. This connection may be endpoint to endpoint or endpoint to midpoint. When a single endpoint to endpoint (net or pin endpoint) connection is drawn, the visual dangling net cue disappears. When an endpoint ends in the middle of another net (or multiple endpoints coming together at a single point) then a circular filled connectivity cue is drawn. You cannot connect a net to the middle of a pin. Nets can only be connected to the endpoints of pins. You cannot connect to a net if that net is not orthogonal (horizontal or vertical). The visual cues are the primary way of telling if nets/pins are connected.<br/>
+ Bus are similar to nets with the exception that you cannot connect a net to the endpoint of a bus (only to the middle). If you do try to connect a net to the end of a bus you will see a big red X at the invalid endpoint connection. Buses are still very new so there are still many quirks.<br/>
+ You can label nets by using the <code>label=</code> attribute. Do not attach more than one <code>label=</code> to a net. You only need to attach the <code>label=</code> attribute to one net segment. Different nets (i.e. multiple net segments which arenâ??t connected together) which have the same attribute <code>label=</code> attached to them are also considered electrically connected. You will not get any indication of this connection by <strong>gschem</strong>, but the netlister (<strong>gnetlist</strong>) considers nets with the same <code>label=</code> attribute electrically connected. The naming convention for buses has not been formalized yet.
+</p>
+
+</div>
+<!-- SECTION "Electrical Connectivity" [41063-42779] -->
+<h1><a name="components_symbols_objects_attributes" id="components_symbols_objects_attributes">Components & Symbols & Objects & Attributes</a></h1>
+<div class="level1">
+
+<p>
+There is a hierarchical association between components, symbols, objects, and attributes.
+</p>
+
+</div>
+<!-- SECTION "Components & Symbols & Objects & Attributes" [42780-42928] -->
+<h2><a name="components" id="components">Components</a></h2>
+<div class="level2">
+
+<p>
+A component is the instantiation of a specific symbol, as placed on the schematic. When discussing a schematic you refer to <em class="u">components</em> on the schematic, not <em class="u">symbols</em> on the schematic. Think of symbols as being <em class="u">conceptual</em>, and components as being <em class="u">concrete</em>.<br/>
+ The component consists of a graphic representation and the attributes describing the componentâ??s features.<br/>
+ The component inherits all of the attributes defined in the symbol. Certain attributes in the symbol:
+</p>
+<ul>
+<li class="level1"><div class="li"> those explicitly defined as visible unattached attributes (see <a href="#attributes" title=":geda:gschem_ug.fr.txt ↵" class="wikilink1">Attributes</a>)</div>
+</li>
+<li class="level1"><div class="li"> specific attributes such as <code>symversion</code> and <code>refdes</code></div>
+</li>
+</ul>
+
+<p>
+ are promoted to the component level for manipulation by the circuit designer. These attributes may optionally be exposed (made viewable) with the componentâ??s graphic, and their values may be changed.<br/>
+ Any attribute not defined in the symbol may be defined in the component. For example, if the symbol does not define the <code>comment</code> attribute, this attribute may be added to the component, perhaps to add a comment for the Bill of Material or Assembly Instructions.<br/>
+ Unfortunately, it is difficult to determine a componentâ??s attributes from <strong>gschem</strong> while entering the schematic. You have to place a symbol on the schematic, select the resulting component, and select <strong>Hierarchy | Down Symbol</strong> from the pull-down menus. Then, you have to unhide all attributes with <strong>Edit | Make Inv Text Vis</strong> from the pull-down menus. Then you have to expand your view of the symbol with <strong>View | Extents</strong>. Then, you have to go back to the schematic by selecting <strong>Hierarchy | Up</strong> from the pull-down menus. Then, you have to select <strong>Edit | Edit…</strong> to bring up the â??Edit Attributesâ?? dialog box to determine if any attributes have been added at the component level.
+</p>
+
+</div>
+<!-- SECTION "Components" [42929-44743] -->
+<h2><a name="symbols" id="symbols">Symbols</a></h2>
+<div class="level2">
+
+<p>
+Symbols are just a collection of objects and attributes.<br/>
+ The objects have positional significance in the symbol, and define the graphic that is viewed.<br/>
+ Attributes may be attached to objects, or they may be attached to the symbol itself (termed as â??unattachedâ?? attributes, because they are not attached to an object).
+</p>
+
+</div>
+<!-- SECTION "Symbols" [44744-45085] -->
+<h2><a name="objects" id="objects">Objects</a></h2>
+<div class="level2">
+
+<p>
+The following are objects:
+</p>
+<ul>
+<li class="level1"><div class="li"> Line</div>
+</li>
+<li class="level1"><div class="li"> Box</div>
+</li>
+<li class="level1"><div class="li"> Circle</div>
+</li>
+<li class="level1"><div class="li"> Arc</div>
+</li>
+<li class="level1"><div class="li"> Pin</div>
+</li>
+<li class="level1"><div class="li"> Picture</div>
+</li>
+<li class="level1"><div class="li"> Text</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Objects" [45086-45198] -->
+<h2><a name="attributes" id="attributes">Attributes</a></h2>
+<div class="level2">
+
+<p>
+An attribute is text which is in the form <code>name=value</code> (there are no spaces to the left or right of the name,value pair). An attribute can be either attached to an object or unattached. Attributes are used extensively in the gEDA project to convey information (e.g., device name, pin numbers, hidden nets, and unit reference numbers). Check <a href="http://www.geda.seul.org/docs/current/attributes/index.html"; class="urlextern" title="http://www.geda.seul.org/docs/current/attributes/index.html"; rel="nofollow">gEDA/gaf Master Attribute Document</a> for a complete list of attributes.<br/>
+ There are three kinds of attributes:</p>
+<dl>
+<dt><span class='term'> Attached attributes</span></dt>
+<dd>These are attributes which take on the standard form and are attached to some object (pin, net, component, or box etc…) to associate a value with the attribute. For example: a pin number associated with a pin. <span class="hilited">These attributes are usually yellow in color.</span></dd>
+<dt><span class='term'> Unattached attributes</span></dt>
+<dd>These are attributes which take on the standard form, but are not attached to any object and usually convey some information which is global in nature. For example: a <code>device=</code> attribute (which lives inside symbols) and specifies what device the entire symbol represents. These attributes are also known as floating or toplevel attributes.</dd>
+<dt><span class='term'> Promoted attributes</span></dt>
+<dd>These are unattached attributes in the symbolâ??s definition that get turned into attached attributes in the componentâ??s definition when the symbol is instantiated as a component when placed in the schematic. If you place an unattached visible attribute inside a symbol and then instantiate that symbol, then that unattached attribute gets â??promotedâ??; that is, it becomes an attached attribute. This mechanism of attribute reattachement (from within a symbol) is known as attribute promotion.</dd>
+</dl>
+<p>There are some gotchas about attribute promotion:
+</p>
+<ul>
+<li class="level1"><div class="li"> Promotion <strong>only</strong> happens when the symbol is first placed. That means that if you place a symbol (e.g., sym1) and then change it on disk (by adding or removing new unattached attributes), existing sym1â??s will not reflect these new unattached attributes (i.e., they wonâ??t get promoted) in any schematic.</div>
+</li>
+<li class="level1"><div class="li"> The <code>device=</code> attribute is not promoted.</div>
+</li>
+<li class="level1"><div class="li"> Invisible attributes are not promoted by default. If you add an unattached attribute (e.g., numslots=#) and make it invisible, it will not be promoted.</div>
+</li>
+</ul>
+
+<p>
+ Now, in order to make everybody happy, this attribute promotion behavior is configurable.<br/>
+ The system-gschemrc file defines: <pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">(attribute-promotion "enabled")</font></pre>
+</p>
+
+<p>
+which enables attribute promotion.<br/>
+ If you override the system-gschemrcâ??s default promote-invisible setting by adding: <pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">(promote-invisible "enabled")</font></pre>
+</p>
+
+<p>
+to either your userâ??s ~/gschemrc or local â??pwdâ??/gschemrc file, invisible unattached attributes will also be promoted <span class="hilited">(and in memory removed)</span>.
+</p>
+
+<p>
+However, if you do this, component slotting will break because <strong>gschem</strong> expects certain unattached attributes inside the symbol <span class="hilited">(in memory even though they are invisible)</span>.<br/>
+ So you can add: <pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">(keep-invisible "enabled")</font></pre>
+</p>
+
+<p>
+to either your userâ??s ~/gschemrc or local â??pwdâ??/gschemrc file. This is enabled by default, but has no effect unless promote-invisible is enabled.
+</p>
+
+<p>
+So, to summarize, attribute promotion takes unattached attributes inside symbols and attaches them to the outside of a placed symbol. Three *rc keywords control this behavior: attribute-promotion, promote-invisible, and keep-invisible.
+</p>
+
+</div>
+<!-- SECTION "Attributes" [45199-48585] -->
+<h1><a name="the_main_window" id="the_main_window">The Main Window</a></h1>
+<div class="level1">
+<table class="inline">
+ <tr>
+ <td> <a href="media/geda/gschem_screenshot_001.jpg" class="media" target="_blank" title="geda:gschem_screenshot_001.jpg"><img src="media/geda/gschem_screenshot_001.jpg" class="media" alt="" /></a> </td>
+ </tr>
+</table>
+
+<p>
+ There are several ways to interact with <strong>gschem</strong>. <strong>gschem</strong> requires a keyboard and mouse. There are three ways to initiate an operation or command:
+</p>
+<ul>
+<li class="level1"><div class="li"> Using the mouse to select the operation off a menu</div>
+</li>
+<li class="level1"><div class="li"> Typing the keyboard shortcut(s).</div>
+</li>
+<li class="level1"><div class="li"> Draw the appropriate stroke (if stroke support is enabled)</div>
+</li>
+</ul>
+
+<p>
+ To make usage matters more confusing, selecting an operation off of the menus behaves slightly differently than typing the keyboard shortcut. Most of the operations operate on the currently selected object(s), hence you need to select the object first before manipulating them. The menu selected operations usually require some more input (usually a mouse click) after they are picked off of the menu. The keyboard shortcut operations take that required input as the current mouse position. This saves an extra click since you can position the mouse at the right place, type in the shortcut(s), and the command then executes. Note, you can change this so that both menu and shortcut behavior is exactly the same. See the section on the resource file for more info on how to configure this.<br/>
+ Most of the interaction with <strong>gschem</strong> is fairly mode oriented (similar to the great text editor vi). If you select operations off of the menu, then you are placed into the corresponding mode (like copy or move mode). You must then select an anchor point (or whatever the appropriate point is) to continue the operation. Most of the commands off of the menu expect the objects to be already selected. Some of the modes persist after being execute while other immediately return you into select mode (the default mode).<br/>
+ The shortcuts are also mode like in nature. Most of the default shortcuts are for the various commands are not single keystrokes. There are a few which are single keystrokes (like zoom in: `zâ?? or pan: `xâ??), but most are typically two keystrokes long. As examples, to execute File/Save you would type `fâ?? and `sâ?? (without the quotes) or Add/Line is `aâ?? and `lâ??. You can get a listing of the shortcuts by picking Help/Hotkeys. You can also see the hotkey assignments in the pulldown menus as well. The shortcuts are defined in the resource files (<strong>system-gschemrc</strong>, <strong>/.gEDA/gschemrc</strong>, or <strong>`pwd`/gschemrc</strong>). See the section on the resource file for more info.<br/>
+ The mouse button actions in <strong>gschem</strong> are mostly configurable. The first mouse button is always used to select objects or pick points. This button is not configurable. The second mouse button is either a copy/move action (when held down over an object), a repeat last command or used to draw a stroke to execute a command. The third mouse button is either a mouse pan (when held down as the mouse is moved) or a popup menu. The behavior of the second and third mouse buttons is controlled through the resource file (see the section below for more info).
+</p>
+
+</div>
+<!-- SECTION "The Main Window" [48586-51499] -->
+<h1><a name="the_status_window" id="the_status_window">The Status Window</a></h1>
+<div class="level1">
+<table class="inline">
+ <tr>
+ <td> <a href="media/geda/status_screenshot.jpg" class="media" target="_blank" title="geda:status_screenshot.jpg"><img src="media/geda/status_screenshot.jpg" class="media" title=":geda:status_screenshot.jpg" alt=":geda:status_screenshot.jpg" /></a> </td>
+ </tr>
+</table>
+
+<p>
+ Add some details about what gets displayed in the status window.
+</p>
+
+</div>
+<!-- SECTION "The Status Window" [51500-51662] -->
+<h1><a name="the_schematic_file" id="the_schematic_file">The Schematic File</a></h1>
+<div class="level1">
+
+<p>
+Schematic files. These files contain components, nets, text, and sometimes primitive objects (like lines, circles, box etc…) Schematics do not contain pins. Schematic filenames should follow this convention: name_#.sch where:
+</p>
+<ul>
+<li class="level1"><div class="li"> name is a text string which describes what this schematic contains.</div>
+</li>
+<li class="level1"><div class="li"> _# is an underscore and a number (like _1, _2, _7, _13, etc…) This number is used to sequence schematic pages in a multiple page schematic.</div>
+</li>
+<li class="level1"><div class="li"> .sch is the schematic extension/suffix. It is important the schematic pages have this extension.</div>
+</li>
+</ul>
+
+<p>
+ Schematic files are pure <acronym title="American Standard Code for Information Interchange">ASCII</acronym> and will always be pure <acronym title="American Standard Code for Information Interchange">ASCII</acronym>. gEDA does not support any binary file formats. The file format for schematics is described in the gEDA file formats document.
+</p>
+
+</div>
+<!-- SECTION "The Schematic File" [51663-52432] -->
+<h1><a name="the_symbol_file" id="the_symbol_file">The Symbol File</a></h1>
+<div class="level1">
+
+<p>
+Symbol files. The schematic and symbol file formats are identical. <strong>gschem</strong> (or a text editor) is used to create symbol files as well as schematics. Symbol files contain lines, circles, boxes, arcs, pins, text, and attributes.<br/>
+ The naming convention for symbol files is: name-#.sym where:
+</p>
+<ul>
+<li class="level1"><div class="li"> name is a text string which describes what the symbol represents.</div>
+</li>
+<li class="level1"><div class="li"> -# is a dash and a number (like -1, -2 etc…) The number is used to allow for a symbols to have the same name yet different contents. There might be multiple representations for resistors so these symbols should be called: resistor-1.sym, resistor-2.sym, and resistor-3.sym.</div>
+</li>
+<li class="level1"><div class="li"> .sym is the symbol extension/suffix. It is important the symbols have this extension.</div>
+</li>
+</ul>
+
+<p>
+ The way of specifying hierarchy is by using the source= attribute. Please see the master attribute document for info on this mechanism.<br/>
+ The hierarchy mechanism is still in heavy flux, so there might be some more changes.
+</p>
+
+</div>
+<!-- SECTION "The Symbol File" [52433-53419] -->
+<h1><a name="symbol_libraries" id="symbol_libraries">Symbol Libraries</a></h1>
+<div class="level1">
+
+<p>
+Components are searched for by specifying (component-library "…â??) inside one of the *rc files. See below for more info.
+</p>
+
+</div>
+<!-- SECTION "Symbol Libraries" [53420-53573] -->
+<h1><a name="the_log_file" id="the_log_file">The Log File</a></h1>
+<div class="level1">
+
+<p>
+Log file. This file contains informative, error, warnings etc… messages when <strong>gschem</strong> was run. This file is created in the working directory that <strong>gschem</strong> was started in. This allows the user to preserve log files between independent projects.
+</p>
+
+</div>
+<!-- SECTION "The Log File" [53574-53851] -->
+<h1><a name="grips" id="grips">Grips</a></h1>
+<div class="level1">
+
+<p>
+Grips are a mechanism used in <strong>gschem</strong> to provide an easy way of modifying objects inside schematics. When you select an object, little squares are placed in strategic locations (line end points or circle radius point or corners of a box) which allow you to change the object quickly. Grip support currently exists for lines, nets, pins, buses, circles, and boxes. Arcs do not yet have grips, but will eventually have them.
+</p>
+
+<p>
+Using grips is easy:
+</p>
+<ul>
+<li class="level1"><div class="li"> Select the object you want to change. The grips (the little boxes) will appear.</div>
+</li>
+<li class="level1"><div class="li"> Click and hold the first mouse button inside the box.</div>
+</li>
+<li class="level1"><div class="li"> Move the mouse around till you have the object where you want it</div>
+</li>
+<li class="level1"><div class="li"> Release the mouse button.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Grips" [53852-54561] -->
+<h1><a name="menu_operations" id="menu_operations">Menu Operations</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "Menu Operations" [54562-54591] -->
+<h2><a name="file" id="file">File</a></h2>
+<div class="level2">
+
+<p>
+The <strong>gschem</strong> application is primarily used for the creation of schematic files (i.e., filename.sch) and symbol files (filename.sym).<br/>
+ The following operations are related to the manipulation of these files.<br/>
+ Note that <strong>gschem</strong> automatically maintains backups of open schematic/symbol files, in the /tmp directory, for the purpose of Undo/Redo. <strong>gschem</strong> cleans up these files when it exits gracefully. If <strong>gschem</strong> does not exit gracefully, the next time you launch <strong>gschem</strong> you will be prompted with a dialog similar to: <pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">WARNING: Found an autosave backup file:
+ {filename}
+
+ The backup copy is newer than the schematic, so it seems you
+ load it instead of the original file.
+ gschem usually makes backup copies automatically, and this
+ situation happens when it crashed or it was forced to exit
+ abruptly.
+
+ If you load the original file, the backup file will be overwritten in
+ the next autosave timeout and it will be lost.
+
+ Do you want to load the backup file?</font></pre>
+</p>
+
+<p>
+The following are available from the <strong>gschem</strong> main windowâ??s menu-bar when you expand <strong>File</strong>:
+</p>
+
+</div>
+<!-- SECTION "File" [54592-55745] -->
+<h3><a name="new_window_fw" id="new_window_fw">New Window (fw)</a></h3>
+<div class="level3">
+
+<p>
+<strong>File | New Window</strong> Ouvre une nouvelle fenêtre. Chaque fenêtre est totalement séparée des autres fenêtres.
+</p>
+
+</div>
+<!-- SECTION "New Window (fw)" [55746-55886] -->
+<h3><a name="new_page_fn" id="new_page_fn">New Page (fn)</a></h3>
+<div class="level3">
+
+<p>
+<strong>File | New Page</strong> Ouvre une nouvelle page en plus de toute page ouverte existante. Cette page sera habituellement appelée «·untitled_N.sch·» où N est un nombre incrémenté.
+</p>
+
+</div>
+<!-- SECTION "New Page (fn)" [55887-56093] -->
+<h3><a name="open_page..._fo" id="open_page..._fo">Open Page... (fo)</a></h3>
+<div class="level3">
+
+<p>
+<strong>File | Open Page…</strong> Ouvre une page depuis le disque.<br/>
+ The â??Open…â?? dialog box pops up providing:
+</p>
+<ul>
+<li class="level1"><div class="li"> Directory navigation aids</div>
+</li>
+<li class="level1"><div class="li"> Filters for restricting the displayed files:</div>
+<ul>
+<li class="level2"><div class="li"> Schematics</div>
+</li>
+<li class="level2"><div class="li"> Symbols</div>
+</li>
+<li class="level2"><div class="li"> Schematics and Symbols</div>
+</li>
+<li class="level2"><div class="li"> All files</div>
+</li>
+</ul>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Open Page... (fo)" [56094-56380] -->
+<h3><a name="close_page_pc" id="close_page_pc">Close Page (pc)</a></h3>
+<div class="level3">
+
+<p>
+<strong>File | Close Page</strong> Fermer la page actuellement affichée. Il vous sera demandé de faire une sauvegarde si vous avez fait des modifications sur la page.
+</p>
+
+</div>
+<!-- SECTION "Close Page (pc)" [56381-56563] -->
+<h3><a name="revert_page_pr" id="revert_page_pr">Revert Page (pr)</a></h3>
+<div class="level3">
+
+<p>
+<strong>File | Revert Page</strong> Ferme et réouvre la page actuellement affichée. Il ne vous sera pas demandé de sauvegarder la page courante et effacera toutes les changements que vous avez fait en réouvrant le schéma sauvegardé dans le disque. A utiliser avec précaution.
+</p>
+
+</div>
+<!-- SECTION "Revert Page (pr)" [56564-56861] -->
+<h3><a name="save_page_fs" id="save_page_fs">Save Page (fs)</a></h3>
+<div class="level3">
+
+<p>
+<strong>File | Save Page</strong> Sauve la page courante. The current filename is displayed in the <strong>gschem</strong> status-bar.<br/>
+ Si la page est appelée untitled_N.sch (o N est un entier) alors une boîte de dialogue avec Save As… apparaîtra demandant un nouveau nom de fichier.<br/>
+ If the pageâ??s filename is NOT â??untitled_N.schâ?? (where N is a integer), then the Save As… dialog box will NOT be displayed, and:
+</p>
+<ul>
+<li class="level1"><div class="li"> the backup file will be created for the previous version, named {filename}~ That is, the "~" (tilde character) is appended to the filename. Any previous backup file is lost.</div>
+</li>
+<li class="level1"><div class="li"> the file will be saved to the current filename.<br/>
+</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Save Page (fs)" [56862-57515] -->
+<h3><a name="save_page_as..._fa" id="save_page_as..._fa">Save Page As... (fa)</a></h3>
+<div class="level3">
+
+<p>
+<strong>File | Save Page As…</strong> Ouvre la boîte de dialogue Save As.<br/>
+ If the current filename is â??untitled_N.schâ??, the Save As… dialog box prompts for a new filename.<br/>
+ If the current filename is NOT â??untitled_N.schâ??, the Save As… dialog box prompts for a new filename, filling in the current filename as a default.<br/>
+ In either case the filename may be changed, and a new file created when the Save As button is clicked.
+</p>
+
+</div>
+<!-- SECTION "Save Page As... (fa)" [57516-57968] -->
+<h3><a name="save_all_fl_fl" id="save_all_fl_fl">Save All (fl) (fl)</a></h3>
+<div class="level3">
+
+<p>
+<strong>File | Save All</strong> Sauvegarde inconditionnelle de tous les schémas chargés dans la mémoire.
+</p>
+
+</div>
+<!-- SECTION "Save All (fl) (fl)" [57969-58094] -->
+<h3><a name="print..._fp" id="print..._fp">Print... (fp)</a></h3>
+<div class="level3">
+
+<p>
+<strong>File | Print…</strong> Affiche la boîte de dialogue Print.<br/>
+ The following may be selected:
+</p>
+<ul>
+<li class="level1"><div class="li"> Filename (if <strong>gschem</strong> has multiple pages loaded, this filename defaults to the page currently displayed).</div>
+</li>
+<li class="level1"><div class="li"> Paper size (that is loaded into your printer).</div>
+</li>
+<li class="level1"><div class="li"> The print type:</div>
+<ul>
+<li class="level2"><div class="li"> Extents with margins – the current page, with margins where the printer doesnâ??t output.</div>
+</li>
+<li class="level2"><div class="li"> Extents no margins – the current page, but without margins where the printer doesnâ??t output. The printer output may be scaled larger than when using â??Entents with marginsâ??, but at the loss along the borders of the schematic.</div>
+</li>
+<li class="level2"><div class="li"> Current window – Scaled to fit the page size, but not optimally.</div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> Orientation:</div>
+<ul>
+<li class="level2"><div class="li"> Landscape</div>
+</li>
+<li class="level2"><div class="li"> Portrait</div>
+</li>
+</ul>
+</li>
+</ul>
+
+<p>
+ Pressing Print will generate a PostScript file with the filname format of the form {filename}.ps (e.g., printing schematic file First_1.sch would generate First_1.ps).<br/>
+ Printing the PostScript file to your printer is distribution dependent:</p>
+<dl>
+<dt><span class='term'> Fedora Core (from the command-line):</span></dt>
+<dd><code>lp First_1.ps</code></dd>
+</dl>
+
+
+</div>
+<!-- SECTION "Print... (fp)" [58095-59143] -->
+<h3><a name="write_png..._fi" id="write_png..._fi">Write PNG... (fi)</a></h3>
+<div class="level3">
+
+<p>
+<strong>File | Write <acronym title="Portable Network Graphics">PNG</acronym>…</strong> Affiche la boîte de dialogue Write <acronym title="Portable Network Graphics">PNG</acronym>. Note you must have libgdgeda installed (and any required dependencies) if you want to output images.<br/>
+ The dialog box allows you to select:
+</p>
+<ul>
+<li class="level1"><div class="li"> Width x Height:</div>
+<ul>
+<li class="level2"><div class="li"> 320 x 240</div>
+</li>
+<li class="level2"><div class="li"> 640 x 480</div>
+</li>
+<li class="level2"><div class="li"> 800 x 600</div>
+</li>
+<li class="level2"><div class="li"> 1024 x 768</div>
+</li>
+<li class="level2"><div class="li"> 1280 x 960</div>
+</li>
+<li class="level2"><div class="li"> 1600 x 1200</div>
+</li>
+<li class="level2"><div class="li"> 3200 x 2400</div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> Filename (if <strong>gschem</strong> has multiple pages loaded, the currently displayed pageâ??s filname is given)</div>
+</li>
+</ul>
+
+<p>
+ When the OK button is clicked, a <acronym title="Portable Network Graphics">PNG</acronym> graphic file with a filename of the form {filename}.png is created (e.g., writing a <acronym title="Portable Network Graphics">PNG</acronym> for schematic file First_1.sch will generate a First_1.png file).<br/>
+ This file may be used any way a <acronym title="Portable Network Graphics">PNG</acronym> file is used (e.g., web-page, document insertion, image manipulation with the GIMP, etc.).
+</p>
+
+</div>
+<!-- SECTION "Write PNG... (fi)" [59144-59940] -->
+<h3><a name="execute_script..._ft" id="execute_script..._ft">Execute Script... (ft)</a></h3>
+<div class="level3">
+
+<p>
+<strong>File | Execute Script…</strong> …..TBD
+</p>
+
+</div>
+<!-- SECTION "Execute Script... (ft)" [59941-60012] -->
+<h3><a name="close_window_fc" id="close_window_fc">Close Window (fc)</a></h3>
+<div class="level3">
+
+<p>
+<strong>File | Close Window</strong> Ferme la fenêtre actuelle. Sâ??il y a des schémas modifiés, une boîte de dialogue â??There are unsaved schematicsâ?? apparaîtra. Cliquer sur OK fera perdre tous les schémas non sauvegardés.
+</p>
+
+</div>
+<!-- SECTION "Close Window (fc)" [60013-60263] -->
+<h3><a name="quit_alt-q" id="quit_alt-q">Quit (Alt-q)</a></h3>
+<div class="level3">
+
+<p>
+<strong>File | Quit</strong> closes all opened windows and exits <strong>gschem</strong>. A â??There are unsaved schematicsâ?? dialog box will appear for each window that has unsaved schematics.
+</p>
+
+</div>
+<!-- SECTION "Quit (Alt-q)" [60264-60456] -->
+<h2><a name="edit" id="edit">Edit</a></h2>
+<div class="level2">
+
+<p>
+The following are available from the <strong>gschem</strong> main windowâ??s menu-bar when you expand <strong>Edit</strong>:
+</p>
+
+</div>
+<!-- SECTION "Edit" [60457-60573] -->
+<h3><a name="undo_shift-u" id="undo_shift-u">Undo (shift-u)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Edit | Undo</strong> does exactly that, it undos the last action which changed the schematic.<br/>
+ The depth of undo (how many undo steps can be performed) is set in the system-gschemrc file. The default is 10. Simply override this setting by placing the following lines in either your ~/.gEDA/gschemrc file or your local gschemrc file: <pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">; undo-levels number
+;
+; Determines the number of levels of undo. Basically this number decides
+; how many backup schematics are saved on disk.
+;
+(undo-levels 10)</font></pre>
+</p>
+
+<p>
+After every action (including zooming and panning) the schematic is saved to disk (in /tmp). The undo-levels setting determines how many of these temporary files are maintained in the /tmp directory. <strong>gschem</strong> does clean-up after itself when you exit.<br/>
+ Should <strong>gschem</strong> crash, the saved files remain in /tmp for disaster recovery. You will be prompted the next time the schematic is opened to recover from the backup.<br/>
+
+</p>
+
+</div>
+<!-- SECTION "Undo (shift-u)" [60574-61532] -->
+<h3><a name="redo_shift-r" id="redo_shift-r">Redo (shift-r)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Edit | Redo</strong> only applies after you have done an <strong>Edit | Undo</strong>. You can undo something and then immediately redo it. However if you do anything in between you will lose the undo info. You can undo and redo to your hearts desire up and down till you reach the max undo levels.<br/>
+
+</p>
+
+</div>
+<!-- SECTION "Redo (shift-r)" [61533-61841] -->
+<h3><a name="select_mode_s" id="select_mode_s">Select Mode (s)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Edit | Select Mode</strong> is the initial mode in which <strong>gschem</strong> starts.<br/>
+ When in <strong>Select Mode</strong>, an unlocked object (i.e., component, line, box, circle, …) may be selected by placing the mouse pointer within the outline of the object and single-clicking, or by dragging a box (i.e., holding down the first mouse-button) around the object. Selecting an already selected object will leave the object selected (i.e., you can not unselect an object by single-clicking it). Multiple unlocked objects may be selected by dragging a box around the objects.<br/>
+ A locked object may be selected by dragging a box around the object.<br/>
+ To de-select all objects, single-click anywhere on the schematic where there is no object.<br/>
+ A visible attribute for an unlocked component may be selected by placing the mouse pointer over the componentâ??s visible attribute and single-clicking. Placing the mouse pointer over the unlocked componentâ??s visible attribute and double-clicking will open the edit dialog box appropriate for the attribute.<br/>
+ Objects will change color when selected.<br/>
+ You stay in <strong>Select Mode</strong> until you select one of the other Modes (e.g., Line, Copy, Move, etc.).<br/>
+ Your current Mode is displayed on the status-bar, in the lower-right corner of the <strong>gschem</strong> window.<br/>
+ If multiple objects overlap, single-clicking where they overlap will cycle through the objects.<br/>
+ If you hold down the SHIFT key and single-click, you can select and deselect multiple objects. Doing this with multiple overlapping objects will cause the selection to cycle among the possible object selections.<br/>
+ If you hold down the CONTROL key and single-click, you will toggle the object in and out of the current selection list.<br/>
+ If you hold down the SHIFT key while drawing a selection box you will add to the currently selected objects. Objects cannot be removed using the selection box and holding down the SHIFT key.<br/>
+ If you hold down the CONTROL key while drawing a selection box then you will toggle any encompassed objects. If an object was selected then it will be unselected and vice versa.<br/>
+ If you pick a component, its visible and invisible attributes are selected as well. If you just want to select the object, you must deselect the attributes.<br/>
+ The selection mechanisms are not obvious and do require some practice. There are some quirks so please report them as you come across them.
+</p>
+
+</div>
+<!-- SECTION "Select Mode (s)" [61842-64249] -->
+<h3><a name="edit..._ee" id="edit..._ee">Edit... (ee)</a></h3>
+<div class="level3">
+
+<p>
+First, select the object to be edited (i.e., in <strong>Select Mode</strong>).<br/>
+ If the object is a component, <strong>Edit | Edit…</strong> then pops up a dialog box that allows you to edit the componentâ??s attributes:
+</p>
+<ul>
+<li class="level1"><div class="li"> Existing attributes (e.g., refdes) are displayed.</div>
+</li>
+<li class="level1"><div class="li"> A drop-down list of pre-defined attributes permits selection, and a edit-box provides association of a value to the attribute.</div>
+</li>
+<li class="level1"><div class="li"> The attributeâ?? name and/or value may be made visible or invisible,</div>
+</li>
+</ul>
+
+<p>
+ If the ojbect is a text string, <strong>Edit…</strong> then pops up a dialog box that allows you to modify the text stringâ??s attributes:
+</p>
+<ul>
+<li class="level1"><div class="li"> The text string may be modified. Multiple lines of text may be entered by inserting carriage-returns.</div>
+</li>
+<li class="level1"><div class="li"> The text color may be modified.</div>
+</li>
+<li class="level1"><div class="li"> The text size may be modified.</div>
+</li>
+<li class="level1"><div class="li"> The text alignment:</div>
+<ul>
+<li class="level2"><div class="li"> Lower/middle/upper left</div>
+</li>
+<li class="level2"><div class="li"> Lower/middle/upper middle</div>
+</li>
+<li class="level2"><div class="li"> Lower/middle/upper right</div>
+</li>
+</ul>
+</li>
+</ul>
+
+<p>
+ Apply the changes by pressing OK.
+</p>
+
+<p>
+<strong>Notes:</strong><br/>
+ If you need to change the attributes to more than just a few components, consider saving your schematics, closing <strong>gschem</strong>, and using the <strong>gattrib</strong> application, the <strong>grenum</strong> application, or the <strong>refdes_renum</strong> application to make the changes.
+</p>
+
+</div>
+<!-- SECTION "Edit... (ee)" [64250-65444] -->
+<h3><a name="edit_text..._ex" id="edit_text..._ex">Edit Text... (ex)</a></h3>
+<div class="level3">
+
+<p>
+First, select the text object to be edited (i.e., in <strong>Select Mode</strong>).<br/>
+ <strong>Edit | Edit Text…</strong> allows you to edit just text.<br/>
+ <strong>Edit | Edit Text…</strong> then pops up a dialog box that allows you to modify the text stringâ??s attributes:
+</p>
+<ul>
+<li class="level1"><div class="li"> The text string may be modified. Multiple lines of text may be entered by inserting carriage-returns.</div>
+</li>
+<li class="level1"><div class="li"> The text color may be modified.</div>
+</li>
+<li class="level1"><div class="li"> The text size may be modified.</div>
+</li>
+<li class="level1"><div class="li"> The text alignment:</div>
+<ul>
+<li class="level2"><div class="li"> Lower/middle/upper left</div>
+</li>
+<li class="level2"><div class="li"> Lower/middle/upper middle</div>
+</li>
+<li class="level2"><div class="li"> Lower/middle/upper right</div>
+</li>
+</ul>
+</li>
+</ul>
+
+<p>
+ Apply the changes by pressing OK.
+</p>
+
+<p>
+<strong>Notes:</strong><br/>
+ If you need to change the attributes to more than just a few text strings, consider saving your schematics, closing <strong>gschem</strong>, and using the <strong>gattrib</strong> application, the <strong>grenum</strong> application, or the <strong>refdes_renum</strong> application to make the changes.
+</p>
+
+</div>
+<!-- SECTION "Edit Text... (ex)" [65445-66303] -->
+<h3><a name="copy_mode_ec" id="copy_mode_ec">Copy Mode (ec)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Edit | Copy Mode</strong> allows you to copy (i.e., duplicate) the currently selected objects.<br/>
+ To copy the object(s):
+</p>
+<ul>
+<li class="level1"><div class="li"> Select the objects to be copied (i.e., in <strong>Select Mode</strong>)</div>
+</li>
+<li class="level1"><div class="li"> Select <strong>Edit | Copy Mode</strong></div>
+</li>
+<li class="level1"><div class="li"> Observe the status-bar now indicates <strong>Copy Mode</strong></div>
+</li>
+<li class="level1"><div class="li"> Click on the selected component(s) to establish an origin of reference</div>
+</li>
+<li class="level1"><div class="li"> Observe a shadow/outline appears for the selected components that moves with the mouse</div>
+</li>
+<li class="level1"><div class="li"> Place the components where you want them</div>
+</li>
+<li class="level1"><div class="li"> Click to anchor the copied components in place.</div>
+</li>
+</ul>
+
+<p>
+ After finishing the copy, you automatically return to <strong>Select Mode</strong>.<br/>
+ Holding down the CONTROL key as you move the outline around will constrain the movement to be either horizontal or vertical.<br/>
+ To copy objects using the shortcut keys is almost the same as above except that the origin point is selected automatically for you once you hit the copy mode shortcut.<br/>
+
+</p>
+
+</div>
+<!-- SECTION "Copy Mode (ec)" [66304-67228] -->
+<h3><a name="move_mode_em" id="move_mode_em">Move Mode (em)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Edit | Move Mode</strong> allows you to move the currently selected objects.<br/>
+ To move the object(s):
+</p>
+<ul>
+<li class="level1"><div class="li"> Select the objects to be moved (i.e., in <strong>Select Mode</strong>)</div>
+</li>
+<li class="level1"><div class="li"> Select <strong>Edit | Move Mode</strong></div>
+</li>
+<li class="level1"><div class="li"> Observe the status-bar now indicates <strong>Move Mode</strong></div>
+</li>
+<li class="level1"><div class="li"> Click on the selected component(s) to establish an origin of reference</div>
+</li>
+<li class="level1"><div class="li"> Observe a shadow/outline appears for the selected components that moves with the mouse</div>
+</li>
+<li class="level1"><div class="li"> Place the components where you want them</div>
+</li>
+<li class="level1"><div class="li"> Click to anchor the moved components in place.</div>
+</li>
+</ul>
+
+<p>
+ After finishing the move, you automatically return to <strong>Select Mode</strong>.<br/>
+ Holding down the CONTROL key as you move the outline around will constrain the movement to be either horizontal or vertical.<br/>
+ To move objects using the shortcut keys is almost the same as above except that the origin point is selected automatically for you once you hit the copy mode shortcut.<br/>
+
+</p>
+
+<p>
+Since version 20060906, there is another way to move object(s):<br/>
+
+</p>
+<ul>
+<li class="level1"><div class="li"> Select the objects to be moved (i.e., in <strong>Select Mode</strong>).<br/>
+</div>
+</li>
+<li class="level1"><div class="li"> Put the mouse pointer on one of the selected objects, then drag the objects and drop them where you want them.<br/>
+</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Move Mode (em)" [67229-68382] -->
+<h3><a name="delete_delete-key" id="delete_delete-key">Delete (Delete-key)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Edit | Delete</strong> allows you to remove objects off of the page.<br/>
+ To delete objects:
+</p>
+<ul>
+<li class="level1"><div class="li"> Select the desired object(s) (i.e., in <strong>Select Mode</strong>)</div>
+</li>
+<li class="level1"><div class="li"> Select <strong>Edit | Delete</strong></div>
+</li>
+</ul>
+
+<p>
+ The object(s) will be deleted immediately. If you inadvertantly delete a component, you can use Undo to recover.
+</p>
+
+</div>
+<!-- SECTION "Delete (Delete-key)" [68383-68701] -->
+<h3><a name="rotate_90_mode_er" id="rotate_90_mode_er">Rotate 90 Mode (er)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Edit | Rotate 90 Mode</strong> allows you to rotate objects 90 degrees around a pivot/center point.<br/>
+ To rotate objects:
+</p>
+<ul>
+<li class="level1"><div class="li"> Select the desired object(s) (i.e., in <strong>Select Mode</strong>)</div>
+</li>
+<li class="level1"><div class="li"> Select <strong>Edit | Rotate 90 Mode</strong></div>
+</li>
+<li class="level1"><div class="li"> Click on the pivot (or center) point of the rotate</div>
+</li>
+</ul>
+
+<p>
+ The object(s) will be rotated 90º counter-clockwise immediately. If you inadvertantly rotate a component, you can use Undo to recover.<br/>
+ Rotating objects using the shortcut keys is similar to above except that the center point is the last mouse position at which you typed the shortcut.<br/>
+
+</p>
+
+</div>
+<!-- SECTION "Rotate 90 Mode (er)" [68702-69291] -->
+<h3><a name="mirror_mode_ei" id="mirror_mode_ei">Mirror Mode (ei)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Edit | Mirror Mode</strong> allows you to mirror objects horizontally around a pivot point.<br/>
+ To mirror objects:
+</p>
+<ul>
+<li class="level1"><div class="li"> Select the desired object(s) (i.e., in <strong>Select Mode</strong>)</div>
+</li>
+<li class="level1"><div class="li"> Select <strong>Edit | Mirror Mode</strong></div>
+</li>
+<li class="level1"><div class="li"> Click on the pivot (or center) point of the mirror</div>
+</li>
+</ul>
+
+<p>
+ Mirroring objects using the shortcut keys is similar to above except that the pivot point is the last mouse position at which you typed the shortcut.<br/>
+ Objects are mirrored horizontally about the pivot point. If you want to get a vertical mirror then rotate and mirror the object(s) till you get the desired position.<br/>
+ Mirroring of embedded components is not supported.
+</p>
+
+</div>
+<!-- SECTION "Mirror Mode (ei)" [69292-69948] -->
+<h3><a name="slot..._e_shift-s" id="slot..._e_shift-s">Slot... (e shift-s)</a></h3>
+<div class="level3">
+
+<p>
+Some physical packages (e.g., the classic 7400 Quad NAND gate) contain more than one logical component (e.g., one of the NAND gates). In <strong>gchem</strong> terminology, each of these logical components is termed a â??slotâ?? (e.g., there would be 4 slots in the 7400 Quad NAND gate). Each slot is associated with specific pins on the physical package.<br/>
+ <strong>Edit | Slot…</strong> allows you to change the slot number of a multiple-slot package. The package must support slotting. Refer to the <a href="http://www.geda.seul.org/docs/current/symbols/index.html"; class="urlextern" title="http://www.geda.seul.org/docs/current/symbols/index.html"; rel="nofollow">gEDA/gaf Symbol Creation Document</a> for more details.<br/>
+ To change the slot number (i.e., select which package pins are associated with a logical component):
+</p>
+<ul>
+<li class="level1"><div class="li"> Select the desired logical component (i.e., in <strong>Select Mode</strong>)</div>
+</li>
+<li class="level1"><div class="li"> Select <strong>Edit | Slot…</strong></div>
+</li>
+<li class="level1"><div class="li"> Change the â??slot=nâ?? value in the â??Edit slot numberâ?? dialog box</div>
+</li>
+<li class="level1"><div class="li"> Press OK</div>
+</li>
+</ul>
+
+<p>
+ Note that selecting the slot on a package often effects the layout of the printed circuit board, as the slot may be on the wrong side of the package for effecient routing of nets. Donâ??t worry, you can always come back and change the slot selection once you start laying out your board and know which slots route best.
+</p>
+
+</div>
+<!-- SECTION "Slot... (e shift-s)" [69949-71165] -->
+<h3><a name="color..._eo" id="color..._eo">Color... (eo)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Edit | Color…</strong> allows you to change the color of any selected object (with the exception of components).<br/>
+ To change the color of the currently selected objects:
+</p>
+<ul>
+<li class="level1"><div class="li"> Select the desired object(s) (i.e., in <strong>Select Mode</strong>)</div>
+</li>
+<li class="level1"><div class="li"> Select <strong>Edit | Color…</strong></div>
+</li>
+<li class="level1"><div class="li"> The â??Edit | Color Editâ?? dialog box, with a drop down list for colors, will appear:</div>
+<ul>
+<li class="level2"><div class="li"> 1 | pin | black</div>
+</li>
+<li class="level2"><div class="li"> 2 | net endpoint | red</div>
+</li>
+<li class="level2"><div class="li"> 3 | graphic | green4</div>
+</li>
+<li class="level2"><div class="li"> 4 | net | blue2</div>
+</li>
+<li class="level2"><div class="li"> 5 | attribute | black</div>
+</li>
+<li class="level2"><div class="li"> 6 | logic bubble | DarkCyan</div>
+</li>
+<li class="level2"><div class="li"> 8 | detached attribute | red</div>
+</li>
+<li class="level2"><div class="li"> 9 | text | green4</div>
+</li>
+<li class="level2"><div class="li"> 10 | bus | green2</div>
+</li>
+<li class="level2"><div class="li"> 11 | select | firebrick</div>
+</li>
+<li class="level2"><div class="li"> 12 | bounding box | orange</div>
+</li>
+<li class="level2"><div class="li"> 13 | zoom box | DarkCyan</div>
+</li>
+<li class="level2"><div class="li"> 14 | stroke | grey90</div>
+</li>
+<li class="level2"><div class="li"> 15 | lock | grey40</div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> Pick the new color</div>
+</li>
+<li class="level1"><div class="li"> Press Apply</div>
+</li>
+</ul>
+
+<p>
+ The color change will take effect once you press Apply.<br/>
+ You can leave this dialog box up and select other objects and change their color by pressing Apply.
+</p>
+
+</div>
+<!-- SECTION "Color... (eo)" [71166-72124] -->
+<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">
+
+<p>
+<strong>Edit | Lock</strong> and <strong>Edit | Unlock</strong> allow you to lock/unlock components in a schematic. A locked component cannot be selected by a single click. To select locked component(s), drag a box around the component(s).<br/>
+ Locking a component is useful for components such as title blocks, which should not be selectable because there are other objects inside its boundaries. If the titleblock was not locked, and you missed selecting a component by clicking it with the mouse, you would end up selecting the titleblock instead.<br/>
+ Locking a component is also useful just to prevent it from being inadvertantly selected.<br/>
+ To lock/unlock components:
+</p>
+<ul>
+<li class="level1"><div class="li"> Select the desired object(s) (i.e., in <strong>Select Mode</strong>)</div>
+</li>
+<li class="level1"><div class="li"> Select <strong>Edit | Lock</strong> or <strong>Edit | Unlock</strong></div>
+</li>
+</ul>
+
+<p>
+ The locked/unlocked state of components is preserved when <strong>gschem</strong> exits, so components which were locked remain locked the next time the schematic is opened.<br/>
+ You can lock and unlock regular objects (e.g., lines, pins, boxes…). This is nice when you are drawing something and an object is in the way. Just lock it, and you will not have to think about it when you click to select other objects. Locking an object is not preserved in the file format, so once you quit <strong>gschem</strong> any locked objects will be unlocked the next time the schematic is opened.<br/>
+ Note that if a component is locked, you can not single-click to select a visible attribute, or double-click to select and edit a visible component. First unlock such locked components.
+</p>
+
+</div>
+<!-- SECTION "Lock (el) / Unlock (e shift-l)" [72125-73663] -->
+<h3><a name="line_width_type..._ew" id="line_width_type..._ew">Line Width & Type... (ew)</a></h3>
+<div class="level3">
+
+<p>
+The <strong>Edit | Line Width & Type…</strong> dialog box lets you control the width and type of lines, boxes, circles, and arcs on the schematic/symbol.<br/>
+ To change the <strong>Line Width & Type…</strong>:
+</p>
+<ul>
+<li class="level1"><div class="li"> Select the desired object(s) (i.e., in <strong>Select Mode</strong>)</div>
+</li>
+<li class="level1"><div class="li"> Select <strong>Edit | Line Width & Type…</strong></div>
+</li>
+<li class="level1"><div class="li"> The â??Edit Line Width * Typeâ?? dialog box displays</div>
+</li>
+<li class="level1"><div class="li"> Change the following as suites the object:</div>
+<ul>
+<li class="level2"><div class="li"> Line Width</div>
+</li>
+<li class="level2"><div class="li"> Line Type</div>
+</li>
+<li class="level2"><div class="li"> Line Dash Length</div>
+</li>
+<li class="level2"><div class="li"> Line Dash Space</div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> Press OK to apply the changes</div>
+</li>
+</ul>
+
+<p>
+ Note that if the line width doesnâ??t seem to change, just pick a larger value.
+</p>
+
+</div>
+<!-- SECTION "Line Width & Type... (ew)" [73664-74279] -->
+<h3><a name="fill_type..._ef" id="fill_type..._ef">Fill Type... (ef)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Edit | Fill Type…</strong> is used to fill boxes and circles.<br/>
+ To fill a box or circle:
+</p>
+<ul>
+<li class="level1"><div class="li"> Select the box or circle.</div>
+</li>
+<li class="level1"><div class="li"> Select <strong>Edit | Fill Type…</strong>. The â??Edit FIll Typeâ?? dialog box is displayed.</div>
+</li>
+<li class="level1"><div class="li"> Enter:</div>
+<ul>
+<li class="level2"><div class="li"> Fill Type</div>
+</li>
+<li class="level2"><div class="li"> Line Width</div>
+</li>
+<li class="level2"><div class="li"> Angle 1</div>
+</li>
+<li class="level2"><div class="li"> Pitch 1</div>
+</li>
+<li class="level2"><div class="li"> Angle 2</div>
+</li>
+<li class="level2"><div class="li"> Pitch 2</div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> Press OK.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Fill Type... (ef)" [74280-74620] -->
+<h3><a name="symbol_translate..._et" id="symbol_translate..._et">Symbol Translate... (et)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Edit | Symbol Translate…</strong> is used when creating a symbol, to translate the symbol to an origin for subsequent placement. The symbol may take an optional offset (in mils), as appropriate to the symbol.<br/>
+ To translate the symbol:
+</p>
+<ul>
+<li class="level1"><div class="li"> Open a file for the symbol</div>
+</li>
+<li class="level1"><div class="li"> Set the grid snap spacing to 100 mils (<strong>Options</strong> | <strong>Snap Grid Spacing…</strong>).</div>
+</li>
+<li class="level1"><div class="li"> Toggle the grid ON (<strong>Options</strong> | <strong>Toggle Grid On/Off</strong>)</div>
+</li>
+<li class="level1"><div class="li"> Toggle the grid snap ON (<strong>Options</strong> | <strong>Toggle Snap On/Off</strong>)</div>
+</li>
+<li class="level1"><div class="li"> Zoom as appropriate for the symbolâ??s dimensions</div>
+</li>
+<li class="level1"><div class="li"> Draw the symbol, according to the recommendations in the <a href="http://www.geda.seul.org/docs/current/symbols/index.html"; class="urlextern" title="http://www.geda.seul.org/docs/current/symbols/index.html"; rel="nofollow">gEDA/gaf Symbol Creation Document</a></div>
+</li>
+<li class="level1"><div class="li"> Select <strong>Edit | Symbol Translate…</strong></div>
+</li>
+<li class="level1"><div class="li"> The â??Translateâ?? dialog box is displayed.</div>
+</li>
+<li class="level1"><div class="li"> Enter 0 to translate to the origin, or enter a value (in mils), positive or negative, to offset the symbol from the origin.</div>
+</li>
+<li class="level1"><div class="li"> Press OK to apply</div>
+</li>
+<li class="level1"><div class="li"> Save the symbol to the file</div>
+</li>
+</ul>
+
+<p>
+ If you enter a 0, then all the objects will be translated to the origin.<br/>
+ If you enter a non-zero offset, this will be applied equally in both the X and the Y directions.<br/>
+
+</p>
+
+</div>
+<!-- SECTION "Symbol Translate... (et)" [74621-75785] -->
+<h3><a name="embed_component_picture_eb" id="embed_component_picture_eb">Embed Component/Picture (eb)</a></h3>
+<div class="level3">
+
+<p>
+<strong>gschem</strong> supports the concept of embedded components and graphics, where all the information necessary to display a component/graphic is placed in the schematic file. <strong>Edit | Embed Component/Picture</strong> causes schematic files to be significantly larger, but it makes it easy to share schematics with other people or archive schematics. You should only embed components when absolutely necessary.<br/>
+ To <strong>Embed Component/Picture</strong>:
+</p>
+<ul>
+<li class="level1"><div class="li"> Select the component/picture (in <strong>Select Mode</strong>)</div>
+</li>
+<li class="level1"><div class="li"> Select <strong>Edit | Embed Component/Picture</strong></div>
+</li>
+</ul>
+
+<p>
+ Save the schematic. The schematic file will now contain the text strings for the embedded component or embedded graphic.<br/>
+ The <strong>Add Component…</strong> dialog box allows you to optionally embed the component.<br/>
+ The <strong>Add Picture…</strong> dialog box does NOT allow you to optionally embed the component.<br/>
+ You can only embed and unembed components. Also, you cannot embed and then mirror a component (this is a limitation of <strong>gschem</strong> and will eventually be fixed).
+</p>
+
+</div>
+<!-- SECTION "Embed Component/Picture (eb)" [75786-76815] -->
+<h3><a name="unembed_component_picture_eu" id="unembed_component_picture_eu">Unembed Component/Picture (eu)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Edit | Unembed Component/Picture</strong> will move the componentâ??s or graphicâ??s information from the schematic fileâ??s contents and output it to the original fileâ??s path/filename (i.e., the schematic file includes the path/filename information). To <strong>Unembed Component/Picture</strong>:
+</p>
+<ul>
+<li class="level1"><div class="li"> Select the component/picture (in <strong>Select Mode</strong>)</div>
+</li>
+<li class="level1"><div class="li"> Select <strong>Edit | Unembed Component/Picture</strong></div>
+</li>
+</ul>
+
+<p>
+ Save the schematic. The schematic file will now NOT contain the text strings for the embedded component or embedded graphic.<br/>
+ You can only embed and unembed components.
+</p>
+
+</div>
+<!-- SECTION "Unembed Component/Picture (eu)" [76816-77405] -->
+<h3><a name="update_component_ep" id="update_component_ep">Update Component (ep)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Edit | Update Component</strong> updates a componentâ??s definition.<br/>
+ A symbol can be modified from within <strong>gschem</strong> using the following sequence:
+</p>
+<ul>
+<li class="level1"><div class="li"> Select the component for which the symbol should be changed.</div>
+</li>
+<li class="level1"><div class="li"> Select <strong>Hierarchy | Down Symbol</strong>. This takes you to the symbol editor</div>
+</li>
+<li class="level1"><div class="li"> Modify the symbol. This includes modifying the symbolâ??s graphic objects, adding/changing/deleting attributes, and moving objects with respect to the origin</div>
+</li>
+<li class="level1"><div class="li"> Donâ??t forget to <strong>Edit | Symbol Translate</strong></div>
+</li>
+<li class="level1"><div class="li"> Select <strong>File | Save Page</strong> to save the symbol to itâ??s file</div>
+</li>
+<li class="level1"><div class="li"> Select <strong>Hierarchy | Up Symbol</strong>. This returns you to the schematic editor</div>
+</li>
+<li class="level1"><div class="li"> With the component still selected, select <strong>Edit | Update Component</strong> to update the componetâ??s description from the modified symbolâ??s definition</div>
+</li>
+<li class="level1"><div class="li"> Select each component on the schematic(s) made from this symbol, and select <strong>Edit | Update Component</strong></div>
+</li>
+</ul>
+
+<p>
+ New components placed on the schematic from this updated symbol will use the new symbol definition.<br/>
+ Components placed on the schematic from this symbol will be updated the next time this schematic is opened.<br/>
+ The symbolâ??s <code>symversion</code> attribute will automatically be incremented for non-trivial changes when the symbol is saved. When a schematic is opened by <strong>gschem</strong>, all symbols used by the schematic are read from their libraries. The <code>symversion</code> attribute of the symbol read from the library is compared to the <code>symversion</code> attribute of the components in the schematic. If the <code>symversion</code> attributes are different, the <code>symversion</code> attribute is exposed on the schematic for those symbols effected. Note that:
+</p>
+<ul>
+<li class="level1"><div class="li"> This is a â??hintâ?? to the designer to check the symbol.</div>
+</li>
+<li class="level1"><div class="li"> You need to actually open a schematic file with <strong>gschem</strong> for the components to be updated.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Update Component (ep)" [77406-79215] -->
+<h3><a name="show_hide_inv_text_en" id="show_hide_inv_text_en">Show/Hide Inv Text (en)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Edit | Show/Hide Inv Text</strong> is most appropriate when creating or editing symbols, to view or hide the text for all of the symbolâ??s invisible attributes.<br/>
+ <a href="#make_inv_text_vis" title=":geda:gschem_ug.fr.txt ↵" class="wikilink1">Make Inv Text Vis</a> is most appropriate when adding symbols to schematics, to view the text for the symbolâ??s modifiable invisible attributes.<br/>
+ <strong>Edit | Show/Hide Inv Text</strong> toggles between making all invisible text visible and hiding all invisible text. When selected, all objects in the symbol are effected.<br/>
+ Visible text always remains visible.<br/>
+ A symbol has the following <em class="u">potential</em> attributes :
+</p>
+<ul>
+<li class="level1"><div class="li"> netname</div>
+</li>
+<li class="level1"><div class="li"> refdes</div>
+</li>
+<li class="level1"><div class="li"> slot</div>
+</li>
+<li class="level1"><div class="li"> value</div>
+</li>
+<li class="level1"><div class="li"> net</div>
+</li>
+<li class="level1"><div class="li"> device</div>
+</li>
+<li class="level1"><div class="li"> pinnumber</div>
+</li>
+<li class="level1"><div class="li"> pinseq</div>
+</li>
+<li class="level1"><div class="li"> pintype</div>
+</li>
+<li class="level1"><div class="li"> pinlabel</div>
+</li>
+<li class="level1"><div class="li"> source</div>
+</li>
+<li class="level1"><div class="li"> numslots</div>
+</li>
+<li class="level1"><div class="li"> slotdef</div>
+</li>
+<li class="level1"><div class="li"> graphical</div>
+</li>
+<li class="level1"><div class="li"> footprint</div>
+</li>
+<li class="level1"><div class="li"> description</div>
+</li>
+<li class="level1"><div class="li"> documentation</div>
+</li>
+<li class="level1"><div class="li"> symversion</div>
+</li>
+<li class="level1"><div class="li"> comment</div>
+</li>
+<li class="level1"><div class="li"> file</div>
+</li>
+<li class="level1"><div class="li"> model-name</div>
+</li>
+</ul>
+
+<p>
+ Not all attributes need to be used to define a symbol (see the discussion of <a href="docs-20060124-gschem_ug-app_a.html" class="wikilink2" title="docs-20060124-gschem_ug-app_a.html">Appendix A -- Heavy vs Light Symbol Libraries</a>). The <strong>gschem</strong> default is to define symbols as â??lightâ??, indicating that the symbol includes as few attributes as necessary to describe the symbol. â??lightâ?? symbols depend on the designer attaching additional descriptive attributes to the symbol when the symbol is placed on the schematic. For example: a â??lightâ?? symbol for a resistor might include just the graphic for a resistor, its pin attributes, and the â??refdesâ?? attribute. This describes a resistor. It would be the designerâ??s responsibility, after the resistor has been placed on the schematic, to add the â??valueâ?? and â??footprintâ?? attributes appropriate for the specific resistor in the circuit. A â??heavyâ?? symbol includes more descriptive attributes. Using â??lightâ?? vs. â??heavyâ?? symbols is up to the designer.<br/>
+ A symbolâ??s attributes may be flagged as either visible or invisible. Attributes are flagged as invisible to reduce the clutter around a symbol on the schematic.<br/>
+ When creating or editing the symbol, and changing a visible attribute to an invisible attribute, the attribute can not be viewed during further editing of the symbol. It becomes difficult to place attribute text. To view both the visible and invisible text, select <strong>Edit | Show/Hide Inv Text</strong>.<br/>
+ When a symbol is instantiated on a schematic as a component, only the symbolâ??s visible attributes are promoted to the component. For example: if a resistorâ??s symbol defines â??refdesâ?? as the only visible attribute defined in the symbol, the only attribute that the component contains is the â??refdesâ?? attribute). Those attributes not included in the symbol definition may be added at the schematic level, component-by-component.<br/>
+ This operation is useful when drawing/debugging symbols.<br/>
+ When hidden text is visible, â??Show Hiddenâ?? will appear on the status-bar in the lower right.
+</p>
+
+</div>
+<!-- SECTION "Show/Hide Inv Text (en)" [79216-82043] -->
+<h3><a name="make_inv_text_vis_ev" id="make_inv_text_vis_ev">Make Inv Text Vis (ev)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Edit | Make Inv Text Vis</strong> is a quick method of making all of a componentâ??s invisible attributes visible. The same effect can be accomplished by double-clicking on the component and marking all of the entries in the Attributes listbox as â??Vis?" (i.e., visible).<br/>
+ To <strong>Make Inv Text Vis</strong> for a component:
+</p>
+<ul>
+<li class="level1"><div class="li"> Select the component(s) in <strong>Select Mode</strong></div>
+</li>
+<li class="level1"><div class="li"> Select <strong>Edit | Make Inv Text Vis</strong></div>
+</li>
+</ul>
+
+<p>
+ The attributes that had been hidden are displayed.<br/>
+ To hide the attributes again, you need to double-click the component to bring up itâ??s â??Edit Attributesâ?? dialog box, and explicitly place a check for each attribute you want hidden.
+</p>
+
+</div>
+<!-- SECTION "Make Inv Text Vis (ev)" [82044-82707] -->
+<h2><a name="buffer" id="buffer">Buffer</a></h2>
+<div class="level2">
+
+<p>
+<strong>gschem</strong> supports 5 copy/cut/paste buffers which are visible across all opened pages and windows.
+</p>
+
+</div>
+<!-- SECTION "Buffer" [82708-82827] -->
+<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">
+
+<p>
+To copy something into a buffer:
+</p>
+<ol>
+<li class="level1"><div class="li"> Select the objects you want to copy.</div>
+</li>
+<li class="level1"><div class="li"> Select Buffer/Copy/Copy into buffer #.</div>
+</li>
+</ol>
+
+</div>
+<!-- SECTION "Copy into 1/2/3/4/5 (yc)" [82828-82980] -->
+<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">
+
+<p>
+Cut is like copy in that it removes the objects from the schematic
+</p>
+
+</div>
+<!-- SECTION "Cut into 1/2/3/4/5 (yu)" [82981-83082] -->
+<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">
+
+<p>
+To paste a buffer into the current schematic:
+</p>
+<ol>
+<li class="level1"><div class="li"> Fill the buffer using the above Copy or Cut.</div>
+</li>
+<li class="level1"><div class="li"> Go to the new schematic page/window.</div>
+</li>
+<li class="level1"><div class="li"> Select Buffer/Paste/Paste from buffer #.</div>
+</li>
+<li class="level1"><div class="li"> Click the first mouse button to pick an anchor point.</div>
+</li>
+<li class="level1"><div class="li"> Move the mouse to the final spot.</div>
+</li>
+<li class="level1"><div class="li"> Click the first mouse button again.</div>
+</li>
+</ol>
+
+</div>
+<!-- SECTION "Paste from 1/2/3/4/5 (yp)" [83083-83436] -->
+<h2><a name="view" id="view">View</a></h2>
+<div class="level2">
+
+</div>
+<!-- SECTION "View" [83437-83454] -->
+<h3><a name="redraw_vr" id="redraw_vr">Redraw (vr)</a></h3>
+<div class="level3">
+
+<p>
+<strong>View | Redraw</strong> re-paints the current window.<br/>
+ This is useful when you have mouse/component/line/text etc… droppings left over from a previous action. It is also useful when you want to update all visual connectivity cues.
+</p>
+
+</div>
+<!-- SECTION "Redraw (vr)" [83455-83705] -->
+<h3><a name="pan_x" id="pan_x">Pan (x)</a></h3>
+<div class="level3">
+
+<p>
+<strong>View | Pan</strong> lets you change the focus of the display.<br/>
+ To pan the display:
+</p>
+<ul>
+<li class="level1"><div class="li"> Select <strong>View | Pan</strong></div>
+</li>
+<li class="level1"><div class="li"> Click the first mouse button at the new center of the display.</div>
+</li>
+</ul>
+
+<p>
+ To pan the display using the shortcut is much simpler, simply place the mouse pointer where you want the display centered and type â??xâ??. The display will jump to the mouseâ??s location.<br/>
+ Pan behavior is configurable. The system-gschemrc file defines: <pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">(third-button "popup")</font></pre>
+</p>
+
+<p>
+If you override the system-gschemrcâ??s default, of popping up a menu when the third mouse button is clicked, by adding: <pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">(third-button "mousepan")</font></pre>
+</p>
+
+<p>
+to either your userâ??s ~/gschemrc file or local â??pwdâ??/gschemrc file, the third mouse button (i.e., the right mouse button on scroll-wheel mice) will allow you to pan the schematic by holding down the third mouse button and dragging.<br/>
+ The system-gschemrc file also defines: <pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">(fast-mousepan "enabled")</font></pre>
+</p>
+
+<p>
+If you override the system-gschemrcâ??s default by adding: <pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">(fast-mousepan "disabled")</font></pre>
+</p>
+
+<p>
+to either your userâ??s ~/gschemrc file or local â??pwdâ??/gschemrc file, text will be displayed properly when the third mouse button is held down while dragging. The <code>(third-button â??mousepanâ??)</code> setting must also be applied for this to work. Disabling <code>fast-mousepan</code> adversely effects rendering speed while panning on large â??complicatedâ?? schematics.<br/>
+ The system-gschemrc file also defines: <pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">(zoom-with-pan "enabled")</font></pre>
+</p>
+
+<p>
+If you override the system-gschemrcâ??s default by adding: <pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">(zoom-with-pan "disabled")</font></pre>
+</p>
+
+<p>
+to either your userâ??s ~/gschemrc file or local â??pwdâ??/gschemrc file, whenever you zoom in/out, the zoom will NOT center on the mouse pointer, effectively removing the pan feature of the zoom in/out operations.
+</p>
+
+</div>
+<!-- SECTION "Pan (x)" [83706-85502] -->
+<h3><a name="zoom_box_w" id="zoom_box_w">Zoom Box (w)</a></h3>
+<div class="level3">
+
+<p>
+<strong>View | Zoom Box</strong> allows you to draw a box around a part of the <strong>gschem</strong> window and zoom in.<br/>
+ To use <strong>View | Zoom Box</strong>:
+</p>
+<ul>
+<li class="level1"><div class="li"> Select <strong>View | Zoom Box</strong></div>
+</li>
+<li class="level1"><div class="li"> Position the mouse pointer at one corner of the box you want to draw</div>
+</li>
+<li class="level1"><div class="li"> Click and hold down the first mouse button</div>
+</li>
+<li class="level1"><div class="li"> Drag the mouse, drawing the zoom box around the area to which you want to zoom</div>
+</li>
+<li class="level1"><div class="li"> Release the mouse button and the display will zoom</div>
+</li>
+</ul>
+
+<p>
+ To use <strong>View | Zoom Box</strong> by typing the equivalent shortcut (i.e., â??<strong>w</strong>â??) is more convenient. Simply position the mouse pointer at one corner of the zoom box, then type â??<strong>w</strong>â??. The zoom box will start immediately using the current mouse location as the first corner of the box.<br/>
+ <strong>View | Zoom Box</strong> will attempt to zoom to the requested area, but some boxes are not legal and <strong>gschem</strong> will do itâ??s best to zoom the requested area.
+</p>
+
+</div>
+<!-- SECTION "Zoom Box (w)" [85503-86383] -->
+<h3><a name="zoom_extents_ve" id="zoom_extents_ve">Zoom Extents (ve)</a></h3>
+<div class="level3">
+
+<p>
+<strong>View | Extents</strong> will zoom the display to fit all of the placed objects into the current window.<br/>
+ To view all of the current windowâ??s objects:
+</p>
+<ul>
+<li class="level1"><div class="li"> Select <strong>View | Extents</strong></div>
+</li>
+</ul>
+
+<p>
+ Typing the <strong>View | Extents</strong> shortcut (i.e., â??<strong>ve</strong>â??) is particularly convenient for those that have learned to navigate the schematics using the shortcuts.<br/>
+
+</p>
+
+</div>
+<!-- SECTION "Zoom Extents (ve)" [86384-86750] -->
+<h3><a name="zoom_in_z" id="zoom_in_z">Zoom In (z)</a></h3>
+<div class="level3">
+
+<p>
+<strong>View | Zoom In</strong> zooms the display in. The current center of the window is the center of the new window. This command zooms in by a factor.<br/>
+ To zoom in:
+</p>
+<ul>
+<li class="level1"><div class="li"> Select <strong>View | Zoom In</strong></div>
+</li>
+</ul>
+
+<p>
+ The (zoom-with-pan â??enabledâ??) configuration setting in the gschemrc files effects the operation of the zoom in shortcut (i.e., â??<strong>z</strong>â??). The default system-gschemrc setting for: <pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">(zoom-with-pan "enabled")</font></pre>
+</p>
+
+<p>
+enables zooming in, using the mouse pointerâ??s location as the new center of the window. If this changed to: <pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">(zoom-with-pan "disabled")</font></pre>
+</p>
+
+<p>
+in either your userâ??s ~/gschemrc file or local â??pwdâ??/gschemrc file, whenever you zoom in, the zoom will NOT center on the mouse pointer but will center on the current center of the window, effectively removing the pan feature of the zoom in operation.<br/>
+ To zoom in using the shortcut:
+</p>
+<ul>
+<li class="level1"><div class="li"> If the default (zoom-with-pan â??enabledâ??) is configured in one of the gschemrc files, position the mouse pointer in the window where you want the new center</div>
+</li>
+<li class="level1"><div class="li"> Type â??<strong>z</strong>â??</div>
+</li>
+</ul>
+
+<p>
+ Typing â??<strong>z</strong>â?? is particularly convenient for those that have learned to navigate the schematics using the shortcuts.
+</p>
+
+</div>
+<!-- SECTION "Zoom In (z)" [86751-87912] -->
+<h3><a name="zoom_out_z" id="zoom_out_z">Zoom Out (Z)</a></h3>
+<div class="level3">
+
+<p>
+<strong>View | Zoom Out</strong> zooms the display out. The current center of the window is the center of the new window. This command zooms out by a factor.<br/>
+ To zoom out:
+</p>
+<ul>
+<li class="level1"><div class="li"> Select <strong>View | Zoom Out</strong></div>
+</li>
+</ul>
+
+<p>
+ The (zoom-with-pan â??enabledâ??) configuration setting in the gschemrc files effects the operation of the zoom out shortcut (i.e., â??<strong>z</strong>â??). The default system-gschemrc setting for: <pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">(zoom-with-pan "enabled")</font></pre>
+</p>
+
+<p>
+enables zooming out, using the mouse pointerâ??s location as the new center of the window. If this changed to: <pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">(zoom-with-pan "disabled")</font></pre>
+</p>
+
+<p>
+in either your userâ??s ~/gschemrc file or local â??pwdâ??/gschemrc file, whenever you zoom out, the zoom will NOT center on the mouse pointer but will center on the current center of the window, effectively removing the pan feature of the zoom out operation.<br/>
+ To zoom out using the shortcut:
+</p>
+<ul>
+<li class="level1"><div class="li"> If the default (zoom-with-pan â??enabledâ??) is configured in one of the gschemrc files, position the mouse pointer in the window where you want the new center</div>
+</li>
+<li class="level1"><div class="li"> Type â??<strong>Z</strong>â?? (i.e., shift-z)</div>
+</li>
+</ul>
+
+<p>
+ Typing â??<strong>Z</strong>â?? is particularly convenient for those that have learned to navigate the schematics using the shortcuts.
+</p>
+
+</div>
+<!-- SECTION "Zoom Out (Z)" [87913-89101] -->
+<h3><a name="zoom_full_vf" id="zoom_full_vf">Zoom Full (vf)</a></h3>
+<div class="level3">
+
+<p>
+<strong>View | Zoom Full</strong> will zoom the display to the maximum possible displayable view.<br/>
+
+</p>
+
+<p>
+To view the maximum displayable area:
+</p>
+<ul>
+<li class="level1"><div class="li"> Select <strong>View | Zoom Full</strong></div>
+</li>
+</ul>
+
+<p>
+ The window contents will immediately change to show the maximum possible displayable view.<br/>
+
+</p>
+
+<p>
+To view the maximum displayable area using the keyboard shortcut (i.e., â??<strong>vf</strong>â??):
+</p>
+<ul>
+<li class="level1"><div class="li"> Type â??<strong>vf</strong>â??</div>
+</li>
+</ul>
+
+<p>
+ The window contents will immediately change to show the maximum possible displayable view.<br/>
+
+</p>
+
+<p>
+<strong>View | Zoom Full</strong> is useful if you like to put your working notes outside the titleblock for you schematic, for example. Just remember, these notes would now be considered part of the windows extents, so if you were to <strong>View | Extents</strong>, the display would show the titleblock and your working notes.
+</p>
+
+</div>
+<!-- SECTION "Zoom Full (vf)" [89102-89880] -->
+<h2><a name="page" id="page">Page</a></h2>
+<div class="level2">
+
+</div>
+<!-- SECTION "Page" [89881-89899] -->
+<h3><a name="manager..._pm" id="manager..._pm">Manager... (pm)</a></h3>
+<div class="level3">
+
+</div>
+<!-- SECTION "Manager... (pm)" [89900-89927] -->
+<h3><a name="next" id="next">Next (>)</a></h3>
+<div class="level3">
+
+</div>
+<!-- SECTION "Next (>)" [89928-89948] -->
+<h3><a name="previous" id="previous">Previous (<)</a></h3>
+<div class="level3">
+
+</div>
+<!-- SECTION "Previous (<)" [89949-89973] -->
+<h3><a name="new_pe" id="new_pe">New (pe)</a></h3>
+<div class="level3">
+
+</div>
+<!-- SECTION "New (pe)" [89974-89994] -->
+<h3><a name="revert_pr" id="revert_pr">Revert (pr)</a></h3>
+<div class="level3">
+
+</div>
+<!-- SECTION "Revert (pr)" [89995-90018] -->
+<h3><a name="close_pc" id="close_pc">Close (pc)</a></h3>
+<div class="level3">
+
+</div>
+<!-- SECTION "Close (pc)" [90019-90041] -->
+<h3><a name="discard_pd" id="discard_pd">Discard (pd)</a></h3>
+<div class="level3">
+
+</div>
+<!-- SECTION "Discard (pd)" [90042-90066] -->
+<h2><a name="add" id="add">Add</a></h2>
+<div class="level2">
+
+</div>
+<!-- SECTION "Add" [90067-90083] -->
+<h3><a name="component..._i" id="component..._i">Component... (i)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Add | Component…</strong> Ouvre une boîte de dialogue qui vous
+</p>
+<pre class="code">permet de placer les composants depuis les bibliothèques de composants.\\</pre>
+
+<p>
+Pour placer un composant:
+</p>
+<ul>
+<li class="level1"><div class="li"> Select <strong>Add |Component…</strong></div>
+</li>
+<li class="level1"><div class="li"> Select a component Library from the left list-box</div>
+</li>
+<li class="level1"><div class="li"> Sélectionnez un Composant dans la liste de droite</div>
+</li>
+<li class="level1"><div class="li"> Confirm the symbol is correct by reviewing the image in the Preview window</div>
+</li>
+<li class="level1"><div class="li"> Move the mouse into the main drawing window (you should see an outline follow the mouse pointer).</div>
+</li>
+<li class="level1"><div class="li"> Press the first mouse button to anchor the component</div>
+</li>
+<li class="level1"><div class="li"> Position the mouse pointer, and keep pressing the first mouse button to anchor additional instances of the component</div>
+</li>
+<li class="level1"><div class="li"> When finished anchoring components, press the last mouse button or the ESC key</div>
+</li>
+</ul>
+
+<p>
+ Si un nom de composant est déjà sélectionné, taper Appliquer et déplacer la souris dans la fenêtre principale vous permettra placer à nouveau ce composant.<br/>
+ Vous pouvez effectuer une rotation avant le placement du composant en cliquant sur le bouton du milieu. Pour chaque clic de bouton, le composant effectuera une rotation de 90 degrésdans le sens inverse des aiguilles.<br/>
+ Care has been taken to give components descriptive names in the libraries, though it is sometimes difficult to determine what the component really represents from its name.<br/>
+ For example: in the analog library there are four capacitor entries:
+</p>
+<ul>
+<li class="level1"><div class="li"> capacitor-1.sym</div>
+</li>
+<li class="level1"><div class="li"> capacitor-2.sym</div>
+</li>
+<li class="level1"><div class="li"> capacitor-3.sym</div>
+</li>
+<li class="level1"><div class="li"> capacitor-4.sym</div>
+</li>
+</ul>
+
+<p>
+ It helps to preview the symbol in the â??Select Componentâ?? dialog box before selecting and placing the symbol.
+</p>
+
+</div>
+<!-- SECTION "Component... (i)" [90084-91682] -->
+<h3><a name="net_n" id="net_n">Net (n)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Net</strong> Dessine un nouveau segment de liaison.<br/>
+ A net is typically a contiguous set of line segments between two pins, though it is possible to draw nets between a pin and a point on another net, or between two nets.<br/>
+ For example, the following diagram shows 3 net segments:
+</p>
+<ul>
+<li class="level1"><div class="li"> Between R1 and R2</div>
+</li>
+<li class="level1"><div class="li"> Between R3 and R4</div>
+</li>
+<li class="level1"><div class="li"> Between the two nets</div>
+</li>
+</ul>
+<table class="inline">
+ <tr>
+ <td> <a href="media/geda/nets.jpg" class="media" target="_blank" title="geda:nets.jpg"><img src="media/geda/nets.jpg" class="media" alt="" /></a> </td>
+ </tr>
+</table>
+
+<p>
+ Note the small red segment at the end of the resistorâ??s pins. All pins in <strong>gschem</strong> have this red segment. This is the connectivity cue for the pin. It is sometimes difficult to â??grabâ?? this attachment point when drawing nets, you may need to zoom in on the pin. To zoom in, press the â??zâ?? key. To zoom out, press the â??Zâ?? (i.e., shift-z) key.<br/>
+ To begin drawing a net using the menu:
+</p>
+<ul>
+<li class="level1"><div class="li"> Select <strong>Add | Net</strong></div>
+</li>
+<li class="level1"><div class="li"> Zoom in on the component where the net is to start, so that you can easily grab the pinâ??s attachment point</div>
+</li>
+<li class="level1"><div class="li"> Position the mouse pointer over the pinâ??s connectivity cue</div>
+</li>
+<li class="level1"><div class="li"> Press the first mouse button to start the net</div>
+</li>
+</ul>
+
+<p>
+ To begin drawing the net using the shortcut:
+</p>
+<ul>
+<li class="level1"><div class="li"> Zoom in on the component where the net is to start, so that you can easily grab the pinâ??s attachment point</div>
+</li>
+<li class="level1"><div class="li"> Position the mouse pointer over the pinâ??s connectivity cue</div>
+</li>
+<li class="level1"><div class="li"> Press the â??nâ?? key</div>
+</li>
+</ul>
+
+<p>
+ To continue drawing the net segment(s):
+</p>
+<ul>
+<li class="level1"><div class="li"> Drag the mouse pointer in the direction of the end-point</div>
+</li>
+<li class="level1"><div class="li"> For any necessary 90º turns, single-click the mouse, and continue dragging the mouse pointer toward the end-point</div>
+</li>
+<li class="level1"><div class="li"> For any necessary non-orthogonal net segments (e.g., 45º angle), hold down the CONTROL button, single-click the mouse, and continue dragging the mouse pointer to the end-point</div>
+</li>
+<li class="level1"><div class="li"> When you reach the end-point, press the first mouse button to end the net segment</div>
+</li>
+<li class="level1"><div class="li"> Another net segment will start at the last end-point</div>
+<ul>
+<li class="level2"><div class="li"> If this second pin is to be connected to a third pin, continue as above</div>
+</li>
+<li class="level2"><div class="li"> If this is the end of the connections, press the last mouse button (or ESC) to end the net</div>
+</li>
+</ul>
+</li>
+</ul>
+
+<p>
+ Appuyez sur le dernier bouton de souris ou sur ESC pour effacer toute liaison en cours.<br/>
+ If the net is cancelled you are automatically placed in <strong>Select Mode</strong>. You must pick <strong>Add | Net</strong> again or type the shortcut to add more nets.<br/>
+ You cannot connect a net segment to the middle of a non-orthogonal net.<br/>
+ The boxes at the end of the nets are connectivity cues. Red boxes signify a dangling net (not connected to anything).<br/>
+ Filled circles are midpoint connections/junctions. These cues are drawn automatically and are an indicator of electrical connectivity.<br/>
+ See <a href="docs-20060124-gschem_ug-electrical_connectivity.html" class="wikilink2" title="docs-20060124-gschem_ug-electrical_connectivity.html">Electrical Connectivity</a> for more information.
+</p>
+
+</div>
+<!-- SECTION "Net (n)" [91683-94314] -->
+<h3><a name="bus_u" id="bus_u">Bus (u)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Add | Bus</strong> est basiquement la même chose que <strong>Add | Net</strong>, except that it draws buses.<br/>
+ Buses are very new and there are many aspects which are not defined yet, so keep that in mind as you uses buses. More to be added here eventually.
+</p>
+
+</div>
+<!-- SECTION "Bus (u)" [94315-94574] -->
+<h3><a name="attribute..._aa" id="attribute..._aa">Attribute... (aa)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Add | Attribute…</strong> is appropriate when creating or editing symbols, to add a new attribute.<br/>
+ <strong>Add | Attribute…</strong> brings up the â??Single Attribute Editorâ?? dialog box. This dialog box is ONLY used to add attributes. It does not display or manipulate already placed attributes.<br/>
+ Un attribut nâ??est rien de plus quâ??un objet texte qui est de la forme name=value (Il ne peut y avoir dâ??espace à gauche et à droite de la paire name,value). Il peut soit être attaché à un objet ou détaché.<br/>
+ Pour attacher un attribut détaché (e.g., â??commentâ??, â??documentationâ??, etc.) au symbole:
+</p>
+<ul>
+<li class="level1"><div class="li"> Select <strong>Add | Attribute…</strong></div>
+</li>
+<li class="level1"><div class="li"> Select an attribute name off of the pulldown list, or type the attribute name into the name entry</div>
+</li>
+<li class="level1"><div class="li"> Saisissez la valeur pour lâ??attribut</div>
+</li>
+<li class="level1"><div class="li"> Pick any of the attribute options</div>
+</li>
+<li class="level1"><div class="li"> Cliquez sur OK et lâ??attribut sera placé.</div>
+</li>
+</ul>
+
+<p>
+ Si vous voulez attacher un attribut à un objet, sélectionnez dâ??abord lâ??objet souhaité et pressez ensuite <strong>Add | Attribute…</strong> depuis le menu déroulant. Si vous cliquez sur un objet qui possède des attributs attachés, ils doivent être aussi sélectionnés.<br/>
+ Si vous sélectionnez <strong>Add | Attribute…</strong> en dehors des menus déroulants alors vous nâ??avez pas beaucoup de contrôle sur le placement de lâ??attribut (il prend place soit en bas à gauche de lâ??extension de lâ??objet soit à lâ??origine de tout objet sélectionné). Si vous exécutez néanmoins Add/Attribute (i.e., â??aaâ??) en utilisant la touche de raccourci alors la position courante de la souris est utilisé comme point dâ??encrage pour lâ??objet attribut.<br/>
+ Vous ne pouvez pas placer un attribut incomplet (un attribut sans nom et sans valeur).<br/>
+ Please see <a href="docs-20060124-gschem_ug-components_symbols_objects_attributes.html" class="wikilink2" title="docs-20060124-gschem_ug-components_symbols_objects_attributes.html">Components/Symbols/Objects/Attributes</a> for more info on how to use attributes.
+</p>
+
+</div>
+<!-- SECTION "Attribute... (aa)" [94575-96381] -->
+<h3><a name="text..._at" id="text..._at">Text... (at)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Add | Text…</strong> displays the â??Text Entry…â?? dialog box. To place text:
+</p>
+<ul>
+<li class="level1"><div class="li"> Select <strong>Options | Text Size…</strong> and select the size for the text</div>
+</li>
+<li class="level1"><div class="li"> Select <strong>Add | Text…</strong></div>
+</li>
+<li class="level1"><div class="li"> Type the text in the entry field (multiple lines may be entered by pressing Enter)</div>
+</li>
+<li class="level1"><div class="li"> Press Apply or type Enter</div>
+</li>
+<li class="level1"><div class="li"> Déplacez la souris dans la fenêtre principale (un soulignement de texte devrait apparaître et suivre </div>
+</li>
+</ul>
+
+<p>
+la souris)
+</p>
+<ul>
+<li class="level1"><div class="li"> Pressez le premier bouton de souris pour ancrer le texte</div>
+</li>
+<li class="level1"><div class="li"> Close the â??Text Entry…â?? dialog box</div>
+</li>
+</ul>
+
+<p>
+ Si vous laissez la boîte de dialogue dâ??ajout de texte (<strong>Add | Text…</strong>) ouverte, vous pouvez replacer le même objet texte encore et encore en cliquant simplement sur apply (ou en pressant enter) et en déplaçant la souris dans la fenêtre principale.<br/>
+ The following settings in the system-gschemrc file, the userâ??s ~/gschemrc file, or the local â??pwdâ??/gschemrc file control how text is displayed:</p>
+<dl>
+<dt><span class='term'> text-origin-marker</span></dt>
+<dd>Controls if the text origin markers are displayed.</dd>
+<dt><span class='term'> text-size</span></dt>
+<dd>Sets the default text size.</dd>
+<dt><span class='term'> text-caps-style</span></dt>
+<dd>Sets the default caps style used for the display of text</dd>
+<dt><span class='term'> output-text</span></dt>
+<dd>Controls how text is rendered to postscript</dd>
+</dl>
+<p>Le texte placé débutera automatiquement avec une majuscule. Veuillez voir la section Fichiers Ressource ci-dessous sur comment contrôler ce comportement.<br/>
+ Pour effacer un emplacement de texte, pressez le dernier bouton de souris ou sur la touche ESC.<br/>
+ Si vous créez du texte dans la forme name=value alors vous êtes en cours de création dâ??attributs. gEDA permet aux attributs généraux de flotter librement (ou détachés). Câ??est une bonne idée de changer la couleur de ces attributs flottants à la couleur des attributs courants (qui est aussi appelée couleur dâ??attribut attaché) pour indiquer que le lâ??objet texte est un attribut.<br/>
+ Vous pouvez faire pivoter le texte avant de le placer en cliquant sur le bouton milieu. Pour chaque clic de bouton, le texte fera une rotation de 90 degrés.<br/>
+
+</p>
+
+</div>
+<!-- SECTION "Text... (at)" [96382-98392] -->
+<h3><a name="line_l" id="line_l">Line (l)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Add | Line</strong> draws a single line segment.<br/>
+ To draw a line:
+</p>
+<ul>
+<li class="level1"><div class="li"> If you want to snap the line to the grid, set the grid spacing by selecting <strong>Options | Snap Grid Spacing…</strong> and entering the grid spacing, and then selecting <strong>Options | Toggle Snap On/Off</strong> until you donâ??t see â??Snap Offâ?? on the status-bar</div>
+</li>
+<li class="level1"><div class="li"> Select <strong>Add | Line</strong></div>
+</li>
+<li class="level1"><div class="li"> If you want to constrain the line to 90º movements, hold the CONTROL key down while moving the mouse</div>
+</li>
+<li class="level1"><div class="li"> Position the mouse pointer to the start-point</div>
+</li>
+<li class="level1"><div class="li"> Press the first mouse button</div>
+</li>
+<li class="level1"><div class="li"> Move the mouse in the intended direction</div>
+</li>
+<li class="level1"><div class="li"> When positioned at the end-point, press the first mouse button</div>
+</li>
+<li class="level1"><div class="li"> Continue placing lines, until you either press the second mouse button or type the Escape key</div>
+</li>
+</ul>
+
+<p>
+ <strong>Add | Line</strong> dessine une ligne de la même manière quâ??en dessinant les réseaux avec les exceptions suivantes:
+</p>
+<ul>
+<li class="level1"><div class="li"> Une ligne nâ??a pas de signification électrique</div>
+</li>
+<li class="level1"><div class="li"> Seule un segment de ligne est dessiné</div>
+</li>
+<li class="level1"><div class="li"> Vous gardez les lignes dessinées tant que vous êtes dans le mode de dessin de lignes (<strong>Line Mode</strong>).</div>
+</li>
+</ul>
+
+<p>
+ Pour effacer une ligne directe en cours, pressez le dernier bouton de souris ou la touche ESC.
+</p>
+
+</div>
+<!-- SECTION "Line (l)" [98393-99561] -->
+<h3><a name="box_b" id="box_b">Box (b)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Add | Box</strong> draws a box. To draw a box:
+</p>
+<ul>
+<li class="level1"><div class="li"> If you want to snap the box to the grid, set the grid spacing by selecting <strong>Options | Snap Grid Spacing…</strong> and entering the grid spacing, and then selecting <strong>Options | Toggle Snap On/Off</strong> until you donâ??t see â??Snap Offâ?? on the status-bar</div>
+</li>
+<li class="level1"><div class="li"> Select <strong>Add | Box</strong></div>
+</li>
+<li class="level1"><div class="li"> Position the mouse pointer to the start-point</div>
+</li>
+<li class="level1"><div class="li"> Press the first mouse button</div>
+</li>
+<li class="level1"><div class="li"> Move the mouse in the intended direction</div>
+</li>
+<li class="level1"><div class="li"> When positioned at the end-point, press the first mouse button again</div>
+</li>
+<li class="level1"><div class="li"> Continue placing boxes, until you either press the second mouse button or type the ESC key</div>
+</li>
+</ul>
+
+<p>
+ To cancel a box in progress, press the last mouse button or type the ESC key.<br/>
+ A box has no electrical significance.
+</p>
+
+</div>
+<!-- SECTION "Box (b)" [99562-100314] -->
+<h3><a name="circle_ai" id="circle_ai">Circle (ai)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Add | Circle</strong> creates a circle.<br/>
+ To draw a circle:
+</p>
+<ul>
+<li class="level1"><div class="li"> If you want to snap the box to the grid, set the grid spacing by selecting <strong>Options | Snap Grid Spacing…</strong> and entering the grid spacing, and then selecting <strong>Options | Toggle Snap On/Off</strong> until you donâ??t see â??Snap Offâ?? on the status-bar</div>
+</li>
+<li class="level1"><div class="li"> Select <strong>Add | Circle</strong></div>
+</li>
+<li class="level1"><div class="li"> Placez le centre du cercle </div>
+</li>
+<li class="level1"><div class="li"> Pressez le premier bouton</div>
+</li>
+<li class="level1"><div class="li"> Déplacez la souris pour voir un surlignement du cercle</div>
+</li>
+<li class="level1"><div class="li"> Pressez le premier bouton de souris pour terminer le cercle</div>
+</li>
+<li class="level1"><div class="li"> Continue placing circles, until you either press the second mouse button or type the ESC key</div>
+</li>
+</ul>
+
+<p>
+ Pour dessiner un cercle (en utilisant le raccourci clavier), identique à au-dessus excepté que ce centre du cercle est pris sur la dernière position de souris lorsque vous saisissez le raccourci.<br/>
+ Pour effacer un dessin de cercle en cours, pressez sur le dernier bouton de souris ou sur la touche ESC.<br/>
+
+</p>
+
+</div>
+<!-- SECTION "Circle (ai)" [100315-101265] -->
+<h3><a name="arc_ar" id="arc_ar">Arc (ar)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Add | Arc</strong> draws an arc. Pour dessiner un arc:
+</p>
+<ul>
+<li class="level1"><div class="li"> If you want to snap the box to the grid, set the grid spacing by selecting <strong>Options | Snap Grid Spacing…</strong> and entering the grid spacing, and then selecting <strong>Options | Toggle Snap On/Off</strong> until you donâ??t see â??Snap Offâ?? on the status-bar</div>
+</li>
+<li class="level1"><div class="li"> Select <strong>Add | Arc</strong></div>
+</li>
+<li class="level1"><div class="li"> Place the mouse pointer at the center-point for the arc</div>
+</li>
+<li class="level1"><div class="li"> Press the first mouse button</div>
+</li>
+<li class="level1"><div class="li"> Move the mouse to the right, to define the radius of the arc</div>
+</li>
+<li class="level1"><div class="li"> Press the first mouse button again</div>
+</li>
+<li class="level1"><div class="li"> Enter the Start Angle (in degrees) – 0º is the â??xâ?? axis</div>
+</li>
+<li class="level1"><div class="li"> Enter the Degrees of Sweep (for counter-clockwise sweep)</div>
+</li>
+<li class="level1"><div class="li"> Press OK</div>
+</li>
+<li class="level1"><div class="li"> Continue placing arcs, until you either press the second mouse button or type the ESC key</div>
+</li>
+</ul>
+
+<p>
+ Lâ??angle de démarrage peut être positif ou négatif. Les degrés sont spécifiés en utilisant le système des coordonnées Cartésiennes standard. Les degrés de sweep peuvent être positifs ou négatifs.<br/>
+ Pour effacer un arc en cours de dessin (lorsquâ??il y a le rayon) pressez le dernier bouton de souris ou la touche ESC ou pressez le bouton Cancel dans la boîte de dialogue arc.
+</p>
+
+</div>
+<!-- SECTION "Arc (ar)" [101266-102426] -->
+<h3><a name="pin_ap" id="pin_ap">Pin (ap)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Add | Pin</strong> adds a pin.<br/>
+ Though you can <strong>Add | Pin</strong> while entering a schematic, it only makes sense to create pins while creating or editing symbol files.<br/>
+ To draw a pin:
+</p>
+<ul>
+<li class="level1"><div class="li"> Set the grid spacing by selecting <strong>Options | Snap Grid Spacing…</strong> and entering the grid spacing, and then selecting <strong>Options | Toggle Snap On/Off</strong> until you donâ??t see â??Snap Offâ?? on the status-bar. The <a href="http://www.geda.seul.org/docs/current/symbols/symbols.pdf"; class="urlextern" title="http://www.geda.seul.org/docs/current/symbols/symbols.pdf"; rel="nofollow">gEDA/gaf Symbol Creation Document</a> specifies grid settings for pin placement in gEDA/gaf compliant symbols files.</div>
+</li>
+<li class="level1"><div class="li"> Select <strong>Add | Pin</strong></div>
+</li>
+<li class="level1"><div class="li"> Pins are constrained to 90º movements</div>
+</li>
+<li class="level1"><div class="li"> Position the mouse pointer to the start-point</div>
+</li>
+<li class="level1"><div class="li"> Press the first mouse button</div>
+</li>
+<li class="level1"><div class="li"> Move the mouse in the intended direction. The <a href="http://www.geda.seul.org/docs/current/symbols/symbols.pdf"; class="urlextern" title="http://www.geda.seul.org/docs/current/symbols/symbols.pdf"; rel="nofollow">gEDA/gaf Symbol Creation Document</a> specifies the length of pins in gEDA/gaf compliant symbol files.</div>
+</li>
+<li class="level1"><div class="li"> When positioned at the end-point, press the first mouse button</div>
+</li>
+<li class="level1"><div class="li"> Continue placing pins, until you either press the second mouse button or type the Escape key</div>
+</li>
+</ul>
+
+<p>
+ To cancel a pin in progress, press the last mouse button or the ESC key.
+</p>
+
+</div>
+<!-- SECTION "Pin (ap)" [102427-103614] -->
+<h3><a name="picture..._ag" id="picture..._ag">Picture... (ag)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Add | Picture</strong> places a graphic in the schematic. To draw a picture:
+</p>
+<ul>
+<li class="level1"><div class="li"> If you want to snap the picture to the grid, set the grid spacing by selecting <strong>Options | Snap Grid Spacing…</strong> and entering the grid spacing, and then selecting <strong>Options | Toggle Snap On/Off</strong> until you donâ??t see â??Snap Offâ?? on the status-bar</div>
+</li>
+<li class="level1"><div class="li"> Select <strong>Add | Picture</strong></div>
+</li>
+<li class="level1"><div class="li"> Select the graphic file from the â??Please select a picture fileâ?? dialog box</div>
+</li>
+<li class="level1"><div class="li"> Press OK</div>
+</li>
+<li class="level1"><div class="li"> Position the mouse pointer to the start-point</div>
+</li>
+<li class="level1"><div class="li"> Press the first mouse button</div>
+</li>
+<li class="level1"><div class="li"> Move the mouse in the intended direction. The outline of the picture will appear, retaining the aspect ratio of the original picture.</div>
+</li>
+<li class="level1"><div class="li"> When positioned at the end-point, press the first mouse button again.</div>
+</li>
+<li class="level1"><div class="li"> Continue placing pictures, until you either press the second mouse button or type the ESC key</div>
+</li>
+</ul>
+
+<p>
+ To cancel a picture in progress, press the last mouse button or type the ESC key.<br/>
+ A picture has no electrical significance.
+</p>
+
+</div>
+<!-- SECTION "Picture... (ag)" [103615-104610] -->
+<h2><a name="hierarchy" id="hierarchy">Hierarchy</a></h2>
+<div class="level2">
+
+</div>
+<!-- SECTION "Hierarchy" [104611-104633] -->
+<h3><a name="down_schematic_hd" id="down_schematic_hd">Down Schematic (Hd)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Hierarchy | Down Schematic</strong> shifts the focus from the current schematic to a sub-schematic.<br/>
+ Descend dans un symbole, en ouvrant tous les schémas sous-jacents. Cela ouvrira typiquement un schéma sous-jacent du composant sélectionné sâ??il existe dans le chemin de recherche de la bibliothèque source. Voyez la section des Fichiers Ressource sur la manière de définir ce chemin.<br/>
+ Il y a actuellement deux manières de spécifier quâ??un symbole possède un schéma sous-jacent ou des schémas:
+</p>
+<ol>
+<li class="level1"><div class="li"> Le schéma sous-jacent doit avoir le même nom que le symbole mais avec une extension .sch et doit suivre la convention de nommage de suffixe _#. Voyez la section Fichiers au-dessus à propos de cette convention.</div>
+</li>
+<li class="level1"><div class="li"> Attacher un attribut au symbole appelé source=filename.sch filename.sch nâ??est pas un chemin vers le symbole mais plutôt un nom de base (le dernier fichier dans le spécificateur de chemin) du chemin de symbole. Le schéma sous-jacent sera encore recherché dans le chemin de bibliothèque source. Vous pouvez spécifier des attributs source= multiples. Les schémas sous-jacents seront ouverts dans lâ??ordre de découverte de lâ??attribut source= .</div>
+</li>
+</ol>
+
+<p>
+ Sâ??il a des schémas sous-jacents multiples, ils seront chargés. Le mouvement entre les pages de schéma est limité (au niveau du même jeu des schémas sous-jacent) à moins que le mot-clé rc enforce-hierarchy ne soit modifié pour permettre un mode de libre circulation transversal. Veuillez voir la section des Fichiers de Ressource pour plus dâ??informations.<br/>
+ Il est aussi recommandé que vous mainteniez des noms uniques pour les divers niveaux (lorsque vous utilisez lâ??attribut source<img src="images/smileys/icon_smile2.gif" align="middle" alt="=)" /> pour éviter des possibles confusions. Les mécanismes hiérarchiques sont assez nouveaux et vous pouvez craindre quelques anomalies (et veuillez les rapporter sâ??il vous plaît).
+</p>
+
+</div>
+<!-- SECTION "Down Schematic (Hd)" [104634-106510] -->
+<h3><a name="down_symbol_hs" id="down_symbol_hs">Down Symbol (Hs)</a></h3>
+<div class="level3">
+
+<p>
+Cette option ouvrira le symbole du composant sélectionné.<br/>
+ Une fois que le symbole est ouvert, lâ??utilisateur peut lâ??éditer et le sauvegarder.<br/>
+ A ce moment, le schéma principal ne verra pas les changements du symbole à moins que le schéma principal ne soit rechargé ou que File/Revert ne soit exécuté. Cela sera modifié un jour.
+</p>
+
+</div>
+<!-- SECTION "Down Symbol (Hs)" [106511-106879] -->
+<h3><a name="up_hu" id="up_hu">Up (Hu)</a></h3>
+<div class="level3">
+
+<p>
+Cette option permettra de remonter dans la hiérarchie (sâ??il y a des pages au-dessus de la page actuellement affichée).
+</p>
+
+</div>
+<!-- SECTION "Up (Hu)" [106880-107020] -->
+<h3><a name="documentation_ho" id="documentation_ho">Documentation (Ho)</a></h3>
+<div class="level3">
+
+<p>
+Open any documentation available for the selected symbol/component.<br/>
+ The job is handed over to â??gschemdocâ??, which makes a best-effort attempt of finding relevant documentation.<br/>
+ The documention would normally be in <acronym title="Portable Document Format">PDF</acronym>, <acronym title="HyperText Markup Language">HTML</acronym>, text or image format, but gschemdoc tries to be as transparent as possible on this account.<br/>
+ First and foremost, the attribute â??documentation=" is assumed to point to the documentation. This attribute should either be the filename (basename) of the document, or it should be a complete <acronym title="Uniform Resource Locator">URL</acronym>.<br/>
+ If it is a filename, and the file is found locally (in /usr/share/gEDA/documentation or otherwise), the relevant viewer will be initiated. Otherwise, a Google search for the document will be initiated.<br/>
+ If there is no documentation attribute, the attributes â??deviceâ?? and possibly â??valueâ?? will be consulted in much the same way as for â??documentationâ??. File searches will be made in forms of filenames like â??device-value.pdfâ?? and â??device.pdfâ??.<br/>
+ Failing that, the file name for the symbol itself will be used as basis for the search.
+</p>
+
+</div>
+<!-- SECTION "Documentation (Ho)" [107021-108105] -->
+<h2><a name="attributes1" id="attributes1">Attributes</a></h2>
+<div class="level2">
+
+</div>
+<!-- SECTION "Attributes" [108106-108129] -->
+<h3><a name="attach_ta" id="attach_ta">Attach (ta)</a></h3>
+<div class="level3">
+
+<p>
+The Attach command allows you to take a text item (in the proper form; <code>name=value</code>) and attach it to another object.<br/>
+ To use Attributes/Attach:
+</p>
+<ol>
+<li class="level1"><div class="li"> Select the object which will receive the attributes</div>
+</li>
+<li class="level1"><div class="li"> Select the text object(s) which will be attached to the above object</div>
+</li>
+<li class="level1"><div class="li"> Pick or type the shortcut for Attributes/Attach</div>
+</li>
+</ol>
+
+<p>
+ The order of the sequence of selecting the object and then the text items is important; <strong>gschem</strong> will not allow you to select the text items first and then the object. After going through the above sequence the text item will turn yellow (or the current attached attribute color) signifying that the text item is an attached attribute.<br/>
+ You cannot attach a single attribute to several different objects. You cannot attach non-text items as attributes.
+</p>
+
+</div>
+<!-- SECTION "Attach (ta)" [108130-108937] -->
+<h3><a name="detach_td" id="detach_td">Detach (td)</a></h3>
+<div class="level3">
+
+<p>
+Detach allows you to deassociate attributes from objects.<br/>
+ To deselect an object of all attributes:
+</p>
+<ol>
+<li class="level1"><div class="li"> Select the object of interest</div>
+</li>
+<li class="level1"><div class="li"> Pick or type the shortcut for Attributes/Detach</div>
+</li>
+</ol>
+
+<p>
+ All the attached attributes (even if they are not selected) will be detached from the object. This behavior is probably broken and will eventually be fixed (so that only selected attributes are detached).<br/>
+ When you detach attributes then they turn red (or the current detached attribute color). This color changes allows you to spot text which was an attribute and is now dangling (unattached).
+</p>
+
+</div>
+<!-- SECTION "Detach (td)" [108938-109544] -->
+<h3><a name="show_value_tv" id="show_value_tv">Show Value (tv)</a></h3>
+<div class="level3">
+
+<p>
+These operations allow you to control which part of the attribute string is visible. Usually you are just interested in seeing the <code>value</code> of the attribute, but there are circumstances where seeing the <code>name</code> and <code>value</code> (or maybe just the <code>name</code>) would be useful.<br/>
+ To use the options:
+</p>
+<ol>
+<li class="level1"><div class="li"> Select the attribute(s) of interest</div>
+</li>
+<li class="level1"><div class="li"> Pick or type the shortcut for Attributes/Show *</div>
+</li>
+</ol>
+
+<p>
+ The text item(s) should immediately change.<br/>
+ These operations only work on text items which are in the form <code>name=value</code>
+</p>
+
+</div>
+<!-- SECTION "Show Value (tv)" [109545-110083] -->
+<h3><a name="show_name_tn" id="show_name_tn">Show Name (tn)</a></h3>
+<div class="level3">
+
+<p>
+These operations allow you to control which part of the attribute string is visible. Usually you are just interested in seeing the <code>value</code> of the attribute, but there are circumstances where seeing the <code>name</code> and <code>value</code> (or maybe just the <code>name</code>) would be useful.<br/>
+ To use the options:
+</p>
+<ol>
+<li class="level1"><div class="li"> Select the attribute(s) of interest</div>
+</li>
+<li class="level1"><div class="li"> Pick or type the shortcut for Attributes/Show *</div>
+</li>
+</ol>
+
+<p>
+ The text item(s) should immediately change.<br/>
+ These operations only work on text items which are in the form <code>name=value</code>
+</p>
+
+</div>
+<!-- SECTION "Show Name (tn)" [110084-110621] -->
+<h3><a name="show_both_tb" id="show_both_tb">Show Both (tb)</a></h3>
+<div class="level3">
+
+<p>
+These operations allow you to control which part of the attribute string is visible. Usually you are just interested in seeing the <code>value</code> of the attribute, but there are circumstances where seeing the <code>name</code> and <code>value</code> (or maybe just the <code>name</code>) would be useful.<br/>
+ To use the options:
+</p>
+<ol>
+<li class="level1"><div class="li"> Select the attribute(s) of interest</div>
+</li>
+<li class="level1"><div class="li"> Pick or type the shortcut for Attributes/Show *</div>
+</li>
+</ol>
+
+<p>
+ The text item(s) should immediately change.<br/>
+ These operations only work on text items which are in the form <code>name=value</code>
+</p>
+
+</div>
+<!-- SECTION "Show Both (tb)" [110622-111159] -->
+<h3><a name="toggle_visibility_tt" id="toggle_visibility_tt">Toggle Visibility (tt)</a></h3>
+<div class="level3">
+
+<p>
+This operation allows you to toggle the visibility of attributes.<br/>
+ To use this option:
+</p>
+<ol>
+<li class="level1"><div class="li"> Select the text item(s) of interest</div>
+</li>
+<li class="level1"><div class="li"> Pick or type the shortcut for Attributes/Toggle Vis</div>
+</li>
+</ol>
+
+<p>
+ The text item(s) should change their visibility immediately.<br/>
+ If you make an attached attribute invisible, then you can simply select the parent object and select Toggle Vis and the attribute will be come visible (likewise any visible attributes attached to that object will become invisible).<br/>
+ If you make a free floating (unattached) attribute invisible, then the only way to make it visible (and all other invisible attributes) is to use the Edit/Show Hidden Text option.
+</p>
+
+</div>
+<!-- SECTION "Toggle Visibility (tt)" [111160-111855] -->
+<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">
+
+</div>
+<!-- SECTION "Find Specific Text... (t shift-f)" [111856-111900] -->
+<h3><a name="hide_specific_text..._th" id="hide_specific_text..._th">Hide Specific Text... (th)</a></h3>
+<div class="level3">
+
+</div>
+<!-- SECTION "Hide Specific Text... (th)" [111901-111938] -->
+<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">
+
+</div>
+<!-- SECTION "Show Specific Text... (t shift-h)" [111939-111982] -->
+<h3><a name="autonumber_text..._tu" id="autonumber_text..._tu">Autonumber Text... (tu)</a></h3>
+<div class="level3">
+
+</div>
+<!-- SECTION "Autonumber Text... (tu)" [111983-112017] -->
+<h2><a name="options" id="options">Options</a></h2>
+<div class="level2">
+
+</div>
+<!-- SECTION "Options" [112018-112038] -->
+<h3><a name="text_size..._ot" id="text_size..._ot">Text Size... (ot)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Options | Text Size…</strong> pops up a dialog box which allows you to specify the text size of all text (including attributes placed with the Add/Attribute… dialog box).<br/>
+ The text size is in points (1/72â??). The default text size is 10 point text. The smallest text size is 2 points.
+</p>
+
+</div>
+<!-- SECTION "Text Size... (ot)" [112039-112351] -->
+<h3><a name="toggle_grid_on_off_og" id="toggle_grid_on_off_og">Toggle Grid On/Off (og)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Options | Toggle Grid On/Off</strong> toggles the visible grid.
+</p>
+
+</div>
+<!-- SECTION "Toggle Grid On/Off (og)" [112352-112445] -->
+<h3><a name="toggle_snap_on_off_os" id="toggle_snap_on_off_os">Toggle Snap On/Off (os)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Options | Toggle Snap On/Off</strong> toggles the snap. Be very careful using this. Connections between pins and nets (and nets to nets) depends on being exactly connected. Turning of the grid will almost guarantee that nets/pins do not connect.<br/>
+ Before you translate a symbol using Edit/Symbol Translate, make sure the snap is on.<br/>
+ When snap mode is off, the text â??Snap Offâ?? will appear in the lower, righthand corner.
+</p>
+
+</div>
+<!-- SECTION "Toggle Snap On/Off (os)" [112446-112897] -->
+<h3><a name="snap_grid_spacing..._os" id="snap_grid_spacing..._os">Snap Grid Spacing... (oS)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Options | Snap Grid Spacing…</strong> brings up a dialog box which allows you to change the snap grid spacing (not the grid spacing). The units for this spacing are mils.<br/>
+ Before you translate a symbol using Edit/Symbol Translate, make sure this spacing is set to 100.
+</p>
+
+</div>
+<!-- SECTION "Snap Grid Spacing... (oS)" [112898-113201] -->
+<h3><a name="toggle_outline_box_oa" id="toggle_outline_box_oa">Toggle Outline/Box (oa)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Options | Toggle Outline/Box</strong> toggles between drawing the outline of the current selection or just drawing a box when doing moves/copies/component and text places. The outline mode looks better, but tends to be significantly slower than using the box (bounding box) mode.
+</p>
+
+</div>
+<!-- SECTION "Toggle Outline/Box (oa)" [113202-113511] -->
+<h3><a name="toggle_net_rubberband_or" id="toggle_net_rubberband_or">Toggle Net/Rubberband (or)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Options | Toggle Net/Rubberband</strong> …..????
+</p>
+
+</div>
+<!-- SECTION "Toggle Net/Rubberband (or)" [113512-113595] -->
+<h3><a name="show_log_window_ol" id="show_log_window_ol">Show Log Window (ol)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Options | Show Log Window</strong> displays the log window if it has been closed or disabled from being displayed when you start up <strong>gschem</strong>.
+</p>
+
+</div>
+<!-- SECTION "Show Log Window (ol)" [113596-113766] -->
+<h3><a name="show_coord_window..._oc" id="show_coord_window..._oc">Show Coord Window... (oc)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Options | Show Coord Window…</strong> displays a pop-up window that displays the coordinates of the mouse pointer on the schematic. Useful for accurately placing objects.
+</p>
+
+</div>
+<!-- SECTION "Show Coord Window... (oc)" [113767-113971] -->
+<h2><a name="help" id="help">Help</a></h2>
+<div class="level2">
+
+</div>
+<!-- SECTION "Help" [113972-113989] -->
+<h3><a name="about..._ha" id="about..._ha">About... (ha)</a></h3>
+<div class="level3">
+
+<p>
+Every <acronym title="Graphical User Interface">GUI</acronym> application needs an <strong>Help | About…</strong> feature, to display:
+</p>
+<ul>
+<li class="level1"><div class="li"> The applicationâ??s name.</div>
+</li>
+<li class="level1"><div class="li"> The version of the software.</div>
+</li>
+<li class="level1"><div class="li"> The authorâ??s name(s) and how to contact.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "About... (ha)" [113990-114192] -->
+<h3><a name="manual..._hm" id="manual..._hm">Manual... (hm)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Help | Manual…</strong> brings up the â??gEDA/gaf Documentionâ?? web-page installed on this computer. Very useful for accessing the various documentation available for the gEDA/gaf applications.
+</p>
+
+</div>
+<!-- SECTION "Manual... (hm)" [114193-114406] -->
+<h3><a name="hotkeys..._hh" id="hotkeys..._hh">Hotkeys... (hh)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Help | Hotkeys…</strong> lists the current hotkeys (a.k.a., shortcuts, a.k.a., keyboard accellerators).
+</p>
+
+</div>
+<!-- SECTION "Hotkeys... (hh)" [114407-114534] -->
+<h3><a name="component..._ho" id="component..._ho">Component... (Ho)</a></h3>
+<div class="level3">
+
+<p>
+If you select a component on the schematic, and select <strong>Help | Component…</strong>, <strong>gschem</strong> uses the gschemdoc script to do its best job finding some documentation appropriate for the component:
+</p>
+<ul>
+<li class="level1"><div class="li"> If the componentâ??s symbol included the <code>documentation=documentation_locator</code> attribute, this <acronym title="Uniform Resource Identifier">URI</acronym> is used to retreive the documentation. If the full <acronym title="Uniform Resource Identifier">URI</acronym> is given, the <acronym title="Uniform Resource Identifier">URI</acronym> on the internet is retrieved. If the <acronym title="Uniform Resource Identifier">URI</acronym> is not fully qualified, it is considered to be local to this computer, and is searched for and displayed.</div>
+</li>
+<li class="level1"><div class="li"> If the componentâ??s symbol does not include the <code>documentation=documentation_locator</code> attribute, a Google search is performed for <acronym title="Portable Document Format">PDF</acronym> documents, based on the <code>device=</code> attribute, the <code>value=</code> attribute, and the symbol basename.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Component... (Ho)" [114535-115317] -->
+<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">
+
+<p>
+A short discussion of Light Symbol Libraries as the default for <strong>gschem</strong>, and the option to build your own Heavy Symbol Libraries.
+</p>
+
+</div>
+<!-- SECTION "Appendix A -- Heavy vs Light Symbol Libraries" [115318-115511] -->
+<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">
+
+<p>
+To be supplied…
+</p>
+
+</div>
+<!-- SECTION "Appendix B -- Printing Schematics and Symbols" [115512-115590] -->
+<h1><a name="appendix_c_--_writing_guile_scripts" id="appendix_c_--_writing_guile_scripts">Appendix C -- Writing guile Scripts</a></h1>
+<div class="level1">
+
+<p>
+To be supplied…
+</p>
+
+</div>
+<!-- SECTION "Appendix C -- Writing guile Scripts" [115591-115659] -->
+<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">
+
+<p>
+<strong>gschem</strong> is used for two primary design workflows:
+</p>
+<ul>
+<li class="level1"><div class="li"> Circuit design intended for production of Printed Circuit Boards (PCBs).</div>
+</li>
+<li class="level1"><div class="li"> Circuit design intended for simulation.</div>
+</li>
+</ul>
+
+<p>
+ The following guidelines will assist you in developing quality designs intended for use by applications that support the creation of Printed Circuit Boards:
+</p>
+<ul>
+<li class="level1"><div class="li"> <span class="hilited">To be supplied…</span></div>
+</li>
+</ul>
+
+<p>
+ The following on-line tutorials are an excellent method for the beginner to learn the gEDA Tools Suite design workflow resulting in a PCB:
+</p>
+<ul>
+<li class="level1"><div class="li"> <a href="http://www.geda.seul.org/docs/current/tutorials/gsch2pcb/gschem-warmup.html"; class="urlextern" title="http://www.geda.seul.org/docs/current/tutorials/gsch2pcb/gschem-warmup.html"; rel="nofollow">Bill Wilson's gschem warmup</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="http://www.geda.seul.org/docs/current/tutorials/gsch2pcb/tutorial.html"; class="urlextern" title="http://www.geda.seul.org/docs/current/tutorials/gsch2pcb/tutorial.html"; rel="nofollow">Bill Wilson's gsch2pcb tutorial</a></div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Appendix D -- I Want To Build A Printed Circuit Board" [115660-116449] -->
+<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">
+
+<p>
+<strong>gschem</strong> is used for two primary design workflows:
+</p>
+<ul>
+<li class="level1"><div class="li"> Circuit design intended for production of Printed Circuit Boards.</div>
+</li>
+<li class="level1"><div class="li"> Circuit design intended for simulation.</div>
+</li>
+</ul>
+
+<p>
+ The following guidelines will assist you in developing quality designs intended for simulation:
+</p>
+<ul>
+<li class="level1"><div class="li"> Discuss attributes appropriate for a SPICE model, and how these differ from attributes appropriate for a PCB.</div>
+</li>
+<li class="level1"><div class="li"> <span class="hilited">To be supplied…</span></div>
+</li>
+</ul>
+
+<p>
+ The following on-line tutorials are an excellent method for the beginner to learn the gEDA Tools Suite design workflow resulting in a SPICE simulation:
+</p>
+<ul>
+<li class="level1"><div class="li"> <a href="http://www.brorson.com/gEDA/SPICE/t1.html"; class="urlextern" title="http://www.brorson.com/gEDA/SPICE/t1.html"; rel="nofollow">"Circuit simulation using gEDA and SPICE -- HOWTO" by Stuart Brorson</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="http://www-mdp.eng.cam.ac.uk/urop05/files/gedalib/starting_gEDA.pdf"; class="urlextern" title="http://www-mdp.eng.cam.ac.uk/urop05/files/gedalib/starting_gEDA.pdf"; rel="nofollow">Starting with gEDA at the Cambridge University Engineering Department</a></div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Appendix E -- I Want To Simulate My Design" [116450-117329] -->
+<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">
+
+<p>
+As installed, the <strong>gschemdoc</strong> utility script is used by <strong>gschem</strong> to:
+</p>
+<ul>
+<li class="level1"><div class="li"> Display the â??gEDA/gaf Documentationâ?? (i.e., <strong>Help | Manual…</strong>)</div>
+</li>
+<li class="level1"><div class="li"> Display component documentation (i.e., <strong>Help | Component…</strong>)</div>
+</li>
+</ul>
+
+<p>
+ The list of application launchers that <strong>gschemdoc</strong> uses are defined in the {binary-install-path}/bin/gschemdoc file: <pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">#
+# these may be changed to suit local preferences
+#
+CANDIDATE_BROWSER="galeon mozilla phoenix netscape netscape-navigator opera firefox konqueror"
+CANDIDATE_PDFREADER="xpdf acroread ggv gv"
+CANDIDATE_LOCATE="slocate locate"</font></pre>
+</p>
+
+<p>
+To select a different application launcher, simply edit the {binary-install-path}/bin/gschemdoc file, find the above lines, and move your favorite application to the beginning of the list. For example, to use <strong>firefox</strong> as your preferred browser, move it to the beginning of the <strong>CANDIDATE_BROWSER=</strong> list, to use <strong>acroread</strong> (Adobeâ??s Acrobat Reader) as your preferred <acronym title="Portable Document Format">PDF</acronym> reader, move it to the beginning of the <strong>CANDIDATE_PDFREADER=</strong> list, and to use <strong>locate</strong> as your preferred filesystem search utility, move it to the beginning of the <strong>CANDIDATE_LOCATE=</strong> list.
+</p>
+
+</div>
+<!-- SECTION "Appendix F -- Change gschemdoc User-Defined Preferences" [117330-118546] -->
+<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">
+
+<p>
+To be supplied…
+</p>
+
+</div>
+<!-- SECTION "Appendix G -- Breaking a Large Symbol Into Smaller Symbols" [118547-118638] -->
+<h1><a name="appendix_h_--_definition_of_terms" id="appendix_h_--_definition_of_terms">Appendix H -- Definition of Terms</a></h1>
+<div class="level1">
+
+<p>
+Some terms used in the art of schematic capture:</p>
+<dl>
+<dt><span class='term'> <strong>attribute</strong></span></dt>
+<dd>A text item which is in the form <code>name=value</code>. It can be either unattached or attached.</dd>
+<dt><span class='term'> <strong>buffer</strong></span></dt>
+<dd>…</dd>
+<dt><span class='term'> <strong>component</strong></span></dt>
+<dd>Also know as <strong>part</strong>. The equivalent of an [electronics] device, as one may place on a printed circuit board. Components are instances of a <strong>symbol</strong> placed on a schematic.</dd>
+<dt><span class='term'> <strong>device</strong></span></dt>
+<dd>Also known as â??packageâ??. The equivalent of an [electronics] device, as one may place on a printed circuit board.</dd>
+<dt><span class='term'> <strong>dialog box</strong></span></dt>
+<dd>…</dd>
+<dt><span class='term'> <strong>embedded component</strong></span></dt>
+<dd>A component whose definition is saved as part of the schematicâ??s file.</dd>
+<dt><span class='term'> <strong>footprint</strong></span></dt>
+<dd>Also known as a <strong>land pattern</strong>. The surface space occupied by a <strong>component</strong>/<strong>package</strong>/<strong>part</strong>.</dd>
+<dt><span class='term'> <strong>gEDA/gaf</strong></span></dt>
+<dd><strong>gschem</strong> is a component of the gEDA/gaf set of tools, which tend to integrate together in the development and maintenance of schematics and symbols. The term â??gafâ?? stands for â??<em class="u">g</em>EDA <em class="u">a</em>nd <em class="u">f</em>riendsâ??).</dd>
+<dt><span class='term'> <strong>grip</strong></span></dt>
+<dd>…</dd>
+<dt><span class='term'> <strong>guile</strong></span></dt>
+<dd><a href="http://www.gnu.org/software/guile/"; class="urlextern" title="http://www.gnu.org/software/guile/"; rel="nofollow">GNU Guile</a> is an interpreter for Scheme, a version of Lisp.</dd>
+<dt><span class='term'> <strong>HDL</strong></span></dt>
+<dd>Hardware Description Language (e.g., VHDL, Verilog, etc.). Used to simulate or document a device.</dd>
+<dt><span class='term'> <strong>hierarchical</strong></span></dt>
+<dd>The concept that designs can contain nested levels of schematics, so that all the circuit doesnâ??t need to be placed on a single sheet.</dd>
+<dt><span class='term'> <strong>land pattern</strong></span></dt>
+<dd>Also known as a <strong>footprint</strong>. The surface space occupied by a structure or device.</dd>
+<dt><span class='term'> <strong>library</strong></span></dt>
+<dd>A collection of symbols.</dd>
+<dt><span class='term'> <strong>line</strong></span></dt>
+<dd>A straight drawing element, connecting two points. On the schematic it has no electrical significance. In a symbol, a line is part of the symbolâ??s graphic elements.</dd>
+<dt><span class='term'> <strong>model</strong></span></dt>
+<dd>A description of how a device behaves. Most often this is a SPICE model. The model is defined in <strong>gschem</strong>, but used in subsequent applications such as <strong>ngspice</strong>, <strong>gnucap</strong>, etc.</dd>
+<dt><span class='term'> <strong>net</strong></span></dt>
+<dd>A net connects two or more pins on a schematic, and is made up of segments. The netâ??s equivalent is a â??wireâ?? or â??traceâ?? on the printed circuit board.</dd>
+<dt><span class='term'> <strong>object</strong></span></dt>
+<dd>A line, circle, pin, net, box, bus, text/attribute, or picture.</dd>
+<dt><span class='term'> <strong>package</strong></span></dt>
+<dd>Also known as <strong>device</strong>. The equivalent of an [electronics] device, as one may place on a printed circuit board.</dd>
+<dt><span class='term'> <strong>page</strong></span></dt>
+<dd>Also known as a schematicâ??s <strong>sheet</strong>.</dd>
+<dt><span class='term'> <strong>part</strong></span></dt>
+<dd> Also know as <strong>component</strong>. The equivalent of an [electronics] device, as one may place on a printed circuit board.</dd>
+<dt><span class='term'> <strong>project</strong></span></dt>
+<dd>A collection of schematics, custom symbols, models, documentation, etc.</dd>
+<dt><span class='term'> <strong>segment</strong></span></dt>
+<dd>Part of a net. A segment has two end-points, or â??gripsâ??.</dd>
+<dt><span class='term'> <strong>schematic</strong></span></dt>
+<dd>A <strong>page</strong>/<strong>sheet</strong> with electronics symbols, text, and drawing elements (i.e., lines, circles, boxes, etc.) representing a diagram of an electrical or mechanical system.</dd>
+<dt><span class='term'> <strong>series</strong></span></dt>
+<dd>A collection of schematics which share a common basename (e.g., schematic_1.sch, schematic_2.sch, schematic_3.sch, etc.). The series basename ties schematics together.</dd>
+<dt><span class='term'> <strong>slotted device</strong></span></dt>
+<dd>Also known as a <strong>slotted package</strong>. A physical [electronics] device consisting of multiple identical components (e.g., the 7400 quad NAND device consists of 4 identical NAND gates).</dd>
+<dt><span class='term'> <strong>source</strong></span></dt>
+<dd>A schematic, HDL code, or model which implements, describes, or documents some aspect of the project.</dd>
+<dt><span class='term'> <strong>symbol</strong></span></dt>
+<dd>A collection of <strong>objects</strong>. The objects may have <strong>attributes</strong> attatched (i.e., associated) with them. There may also be <strong>attributes</strong> attached (i.e., associated) to the <strong>symbol</strong> itself (i.e., not specifically associated with an object).</dd>
+<dt><span class='term'> <strong>sheet</strong></span></dt>
+<dd>Also known as a schematicâ??s <strong>page</strong>.</dd>
+<dt><span class='term'> <strong>trace</strong></span></dt>
+<dd>The equivalent of a wire on a printed circuit board.</dd>
+<dt><span class='term'> <strong>window</strong></span></dt>
+<dd>…</dd>
+<dt><span class='term'> <strong>workflow</strong></span></dt>
+<dd>The process of designing. Usually includes continuous review and re-design, until it works. In the gEDA Tools Suite design workflow, multiple applications are used. One application typically is followed by another. The flow of data collected and how this data effects the design is considered the workflow.</dd>
+</dl>
+<p>~~DISCUSSION~~
+</p>
+
+</div>
+<!-- SECTION "Appendix H -- Definition of Terms" [118639-] --></body>
+</html>
diff --git a/docs/wiki/geda-gschem_ug.html b/docs/wiki/geda-gschem_ug.html
new file mode 100644
index 0000000..37fdbeb
--- /dev/null
+++ b/docs/wiki/geda-gschem_ug.html
@@ -0,0 +1,3669 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#geda_gschem_user_guide" class="toc">gEDA gschem User Guide</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#about_this_document" class="toc">About this document ...</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#introduction" class="toc">Introduction</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#overview" class="toc">Overview</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#resources" class="toc">Resources</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#how_to_ask_questions" class="toc">How To Ask Questions</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#installing_gschem" class="toc">Installing gschem</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#latest_stable" class="toc">Latest Stable</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#geda_binary_suite" class="toc">gEDA Binary Suite</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#debian_based_distributions" class="toc">Debian based distributions</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#fedora_and_redhat_distributions" class="toc">Fedora and RedHat distributions</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#suse_and_opensuse_distributions" class="toc">SuSE and OpenSuSE distributions</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#mac_osx_distributions" class="toc">Mac OSX distributions</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#developer_unstable_testing" class="toc">Developer Unstable/Testing</a></span></div></li>
+</ul>
+</li>
+<li class="level1"><div class="li"><span class="li"><a href="#configuring_gschem" class="toc">Configuring gschem</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#gschemrc" class="toc">gschemrc</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#gafrc" class="toc">gafrc</a></span></div></li>
+</ul>
+</li>
+<li class="level1"><div class="li"><span class="li"><a href="#running_gschem" class="toc">Running gschem</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#confirming_gschem_is_installed" class="toc">Confirming gschem is installed</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#the_shell_prompt" class="toc">The Shell Prompt</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#backups" class="toc">Backups</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#classic_linux_backups" class="toc">Classic Linux backups</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#incremental_backups" class="toc">Incremental backups</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#relevant_configuration_settings" class="toc">Relevant configuration settings</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#on-line_documentation" class="toc">On-line documentation</a></span></div></li>
+</ul>
+</li>
+<li class="level1"><div class="li"><span class="li"><a href="#electrical_connectivity" class="toc">Electrical Connectivity</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#components_symbols_objects_attributes" class="toc">Components & Symbols & Objects & Attributes</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#components" class="toc">Components</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#symbols" class="toc">Symbols</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#objects" class="toc">Objects</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#attributes" class="toc">Attributes</a></span></div></li>
+</ul>
+</li>
+<li class="level1"><div class="li"><span class="li"><a href="#the_main_window" class="toc">The Main Window</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#the_status_window" class="toc">The Status Window</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#the_schematic_file" class="toc">The Schematic File</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#the_symbol_file" class="toc">The Symbol File</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#symbol_libraries" class="toc">Symbol Libraries</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#the_log_file" class="toc">The Log File</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#grips" class="toc">Grips</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#menu_operations" class="toc">Menu Operations</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#file" class="toc">File</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#new_window_fw" class="toc">New Window (fw)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#new_page_fn" class="toc">New Page (fn)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#open_page..._fo" class="toc">Open Page... (fo)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#close_page_pc" class="toc">Close Page (pc)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#revert_page_pr" class="toc">Revert Page (pr)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#save_page_fs" class="toc">Save Page (fs)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#save_page_as..._fa" class="toc">Save Page As... (fa)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#save_all_fl_fl" class="toc">Save All (fl) (fl)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#print..._fp" class="toc">Print... (fp)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#write_png..._fi" class="toc">Write PNG... (fi)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#execute_script..._ft" class="toc">Execute Script... (ft)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#close_window_fc" class="toc">Close Window (fc)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#quit_alt-q" class="toc">Quit (Alt-q)</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#edit" class="toc">Edit</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#undo_shift-u" class="toc">Undo (shift-u)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#redo_shift-r" class="toc">Redo (shift-r)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#select_mode_s" class="toc">Select Mode (s)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#edit..._ee" class="toc">Edit... (ee)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#edit_text..._ex" class="toc">Edit Text... (ex)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#copy_mode_ec" class="toc">Copy Mode (ec)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#move_mode_em" class="toc">Move Mode (em)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#delete_delete-key" class="toc">Delete (Delete-key)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#rotate_90_mode_er" class="toc">Rotate 90 Mode (er)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#mirror_mode_ei" class="toc">Mirror Mode (ei)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#slot..._e_shift-s" class="toc">Slot... (e shift-s)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#color..._eo" class="toc">Color... (eo)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#lock_el_unlock_e_shift-l" class="toc">Lock (el) / Unlock (e shift-l)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#line_width_type..._ew" class="toc">Line Width & Type... (ew)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#fill_type..._ef" class="toc">Fill Type... (ef)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#symbol_translate..._et" class="toc">Symbol Translate... (et)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#embed_component_picture_eb" class="toc">Embed Component/Picture (eb)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#unembed_component_picture_eu" class="toc">Unembed Component/Picture (eu)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#update_component_ep" class="toc">Update Component (ep)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#show_hide_inv_text_en" class="toc">Show/Hide Inv Text (en)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#make_inv_text_vis_ev" class="toc">Make Inv Text Vis (ev)</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#buffer" class="toc">Buffer</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#copy_into_1_2_3_4_5_yc" class="toc">Copy into 1/2/3/4/5 (yc)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#cut_into_1_2_3_4_5_yu" class="toc">Cut into 1/2/3/4/5 (yu)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#paste_from_1_2_3_4_5_yp" class="toc">Paste from 1/2/3/4/5 (yp)</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#view" class="toc">View</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#redraw_vr" class="toc">Redraw (vr)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#pan_x" class="toc">Pan (x)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#zoom_box_w" class="toc">Zoom Box (w)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#zoom_extents_ve" class="toc">Zoom Extents (ve)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#zoom_in_z" class="toc">Zoom In (z)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#zoom_out_z" class="toc">Zoom Out (Z)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#zoom_full_vf" class="toc">Zoom Full (vf)</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#page" class="toc">Page</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#manager..._pm" class="toc">Manager... (pm)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#next" class="toc">Next (>)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#previous" class="toc">Previous (<)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#new_pe" class="toc">New (pe)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#revert_pr" class="toc">Revert (pr)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#close_pc" class="toc">Close (pc)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#discard_pd" class="toc">Discard (pd)</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#add" class="toc">Add</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#component..._i" class="toc">Component... (i)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#net_n" class="toc">Net (n)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#bus_u" class="toc">Bus (u)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#attribute..._aa" class="toc">Attribute... (aa)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#text..._at" class="toc">Text... (at)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#line_l" class="toc">Line (l)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#box_b" class="toc">Box (b)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#circle_ai" class="toc">Circle (ai)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#arc_ar" class="toc">Arc (ar)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#pin_ap" class="toc">Pin (ap)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#picture..._ag" class="toc">Picture... (ag)</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#hierarchy" class="toc">Hierarchy</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#down_schematic_hd" class="toc">Down Schematic (Hd)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#down_symbol_hs" class="toc">Down Symbol (Hs)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#up_hu" class="toc">Up (Hu)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#documentation_ho" class="toc">Documentation (Ho)</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#attributes1" class="toc">Attributes</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#attach_ta" class="toc">Attach (ta)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#detach_td" class="toc">Detach (td)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#show_value_tv" class="toc">Show Value (tv)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#show_name_tn" class="toc">Show Name (tn)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#show_both_tb" class="toc">Show Both (tb)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#toggle_visibility_tt" class="toc">Toggle Visibility (tt)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#find_specific_text..._t_shift-f" class="toc">Find Specific Text... (t shift-f)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#hide_specific_text..._th" class="toc">Hide Specific Text... (th)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#show_specific_text..._t_shift-h" class="toc">Show Specific Text... (t shift-h)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#autonumber_text..._tu" class="toc">Autonumber Text... (tu)</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#options" class="toc">Options</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#text_size..._ot" class="toc">Text Size... (ot)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#toggle_grid_on_off_og" class="toc">Toggle Grid On/Off (og)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#toggle_snap_on_off_os" class="toc">Toggle Snap On/Off (os)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#snap_grid_spacing..._os" class="toc">Snap Grid Spacing... (oS)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#toggle_outline_box_oa" class="toc">Toggle Outline/Box (oa)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#toggle_net_rubberband_or" class="toc">Toggle Net/Rubberband (or)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#show_log_window_ol" class="toc">Show Log Window (ol)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#show_coord_window..._oc" class="toc">Show Coord Window... (oc)</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#help" class="toc">Help</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#about..._ha" class="toc">About... (ha)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#manual..._hm" class="toc">Manual... (hm)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#hotkeys..._hh" class="toc">Hotkeys... (hh)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#component..._ho" class="toc">Component... (Ho)</a></span></div></li>
+</ul>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"><span class="li"><a href="#appendix_a_--_heavy_vs_light_symbol_libraries" class="toc">Appendix A -- Heavy vs Light Symbol Libraries</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#appendix_b_--_printing_schematics_and_symbols" class="toc">Appendix B -- Printing Schematics and Symbols</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#appendix_c_--_writing_guile_scripts" class="toc">Appendix C -- Writing guile Scripts</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#appendix_d_--_i_want_to_build_a_printed_circuit_board" class="toc">Appendix D -- I Want To Build A Printed Circuit Board</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#appendix_e_--_i_want_to_simulate_my_design" class="toc">Appendix E -- I Want To Simulate My Design</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#appendix_f_--_change_gschemdoc_user-defined_preferences" class="toc">Appendix F -- Change gschemdoc User-Defined Preferences</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#appendix_g_--_breaking_a_large_symbol_into_smaller_symbols" class="toc">Appendix G -- Breaking a Large Symbol Into Smaller Symbols</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#appendix_h_--_definition_of_terms" class="toc">Appendix H -- Definition of Terms</a></span></div></li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="geda_gschem_user_guide" id="geda_gschem_user_guide">gEDA gschem User Guide</a></h1>
+<div class="level1">
+
+<p>
+by: Ales Hvezda / September 21st, 2003
+</p>
+
+<p>
+The latest version of this document may be found at: <a href="http://geda.seul.org/wiki/geda:gschem_ug"; class="urlextern" title="http://geda.seul.org/wiki/geda:gschem_ug"; rel="nofollow">http://geda.seul.org/wiki/geda:gschem_ug</a>
+</p>
+
+<p>
+This document is released under the <a href="geda-gfdl.html" class="wikilink1" title="geda-gfdl.html">GNU Free Documentation License (GFDL)</a>.
+</p>
+
+<p>
+ Please report any errors/inconsistencies in this document by commenting in the Discussion area at the bottom of the associated page.
+</p>
+
+</div>
+<!-- SECTION "gEDA gschem User Guide" [1-397] -->
+<h1><a name="about_this_document" id="about_this_document">About this document ...</a></h1>
+<div class="level1">
+
+<p>
+gEDA gschem Users Guide
+</p>
+
+<p>
+This document was generated using the LaTeX2HTML translator Version 2002-2-1 (1.70)
+</p>
+
+<p>
+Copyright © 1993, 1994, 1995, 1996, Nikos Drakos, Computer Based Learning Unit, University of Leeds. Copyright © 1997, 1998, 1999, Ross Moore, Mathematics Department, Macquarie University, Sydney.
+</p>
+
+<p>
+The command line arguments were: latex2html -local_icons gschem
+</p>
+
+<p>
+The translation was initiated by Ales Hvezda on 2005-08-20
+</p>
+
+</div>
+<!-- SECTION "About this document ..." [398-873] -->
+<h1><a name="introduction" id="introduction">Introduction</a></h1>
+<div class="level1">
+
+<p>
+This document describes the installation, configuration, and operation of the <strong>gschem</strong> application.<br/>
+ This document does not describe the process of generating schematics. For this, refer to the various tutorials on using the gEDA Tool Suite:
+</p>
+<ul>
+<li class="level1"><div class="li"> <a href="geda-gschem_warmup.html" class="wikilink1" title="geda-gschem_warmup.html">Bill Wilson's gschem warmup</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-gsch2pcb_tutorial.html" class="wikilink1" title="geda-gsch2pcb_tutorial.html">Bill Wilson's gsch2pcb tutorial</a></div>
+</li>
+<li class="level1"><div class="li"> â??Optical Proximity Sensor for Robots (Part 1), Simple PCB Design with the gEDA Suiteâ??, by Stuart Brorson (March 2006 Circuit Cellar article)</div>
+</li>
+<li class="level1"><div class="li"> <a href="http://www-mdp.eng.cam.ac.uk/urop05/files/gedalib/starting_gEDA.pdf"; class="urlextern" title="http://www-mdp.eng.cam.ac.uk/urop05/files/gedalib/starting_gEDA.pdf"; rel="nofollow">Starting with gEDA at the Cambridge University Engineering Department</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="http://www.brorson.com/gEDA/SPICE/t1.html"; class="urlextern" title="http://www.brorson.com/gEDA/SPICE/t1.html"; rel="nofollow">"Circuit simulation using gEDA and SPICE -- HOWTO" by Stuart Brorson</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="http://www.circuitcellar.com/magazine/176toc.htm"; class="urlextern" title="http://www.circuitcellar.com/magazine/176toc.htm"; rel="nofollow">"gEDA Design Suite for Linux" by Stuart Brorson, Ales Hvezda, & Dan McMahill (03 Mar 2005 Circuit Cellar article)</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="http://www.linuxjournal.com/article/8438"; class="urlextern" title="http://www.linuxjournal.com/article/8438"; rel="nofollow">"Circuit Design on Your Linux Box Using gEDA" by Stuart Brorson (29 November 2005 Linux Journal article)</a></div>
+</li>
+<li class="level1"><div class="li"> Optical Proximity Sensor for Robots (Part 1): Simple PCB Design with the gEDA Suite, by Stuart Brorson, Circuit Cellar magazine, March 2006 (Issue 188), p. 48</div>
+</li>
+<li class="level1"><div class="li"> And, of course, <a href="http://www.google.com/search?hl=en&lr=&q=gEDA+%22schematic+capture%22+tutorial&btnG=Search"; class="urlextern" title="http://www.google.com/search?hl=en&lr=&q=gEDA+%22schematic+capture%22+tutorial&btnG=Search"; rel="nofollow">Google is your friend</a>.</div>
+</li>
+</ul>
+
+<p>
+ This document assumes you understand basic schematic capture concepts. For example: that a component represents something and that nets and buses interconnect these components to form a schematic, etc… For a basic understanding of the various work-flows available in the gEDA Tool Suite, please read the above tutorials. For more detailed understanding of specific tool issues, please refer to <a href="geda-gschem_ug.html#how_to_ask_questions" class="wikilink1" title="geda-gschem_ug.html">How To Ask Questions</a> and to the <a href="geda-gschem_ug.html#resources" class="wikilink1" title="geda-gschem_ug.html">Resources</a>.
+</p>
+
+</div>
+<!-- SECTION "Introduction" [874-2809] -->
+<h1><a name="overview" id="overview">Overview</a></h1>
+<div class="level1">
+
+<p>
+<strong>gschem</strong> is the schematic capture program in the gEDA Tool Suite. Its purpose is to facilitate the graphical input of:
+</p>
+<ul>
+<li class="level1"><div class="li"> circuit schematics</div>
+</li>
+<li class="level1"><div class="li"> component symbols</div>
+</li>
+<li class="level1"><div class="li"> block diagrams</div>
+</li>
+</ul>
+
+<p>
+ Once <strong>gschem</strong> has been used to enter the symbols/schematics for your design, several gEDA Tool Suite â??utilityâ?? programs are used to extract information for other purposes:
+</p>
+<ul>
+<li class="level1"><div class="li"> <strong>gattrib</strong> – <strong>gattrib</strong> is a gEDA Tool Suite productivity aid. <strong>gattrib</strong> reads a [hierarchical set of] gschem schematic files and creates a spreadsheet showing all components in rows, with the associated component attributes listed in the columns. It allows the user to add, modify, or delete component attributes outside of <strong>gschem</strong>, and then save the .sch files.</div>
+</li>
+<li class="level1"><div class="li"> <strong>gnetlist</strong> – A tool that converts a [hierarchical set of] schematic files into an equivalent netlist (a textual representation of a schematic) in various formats. Various gnetlist back-ends are used to create:</div>
+<ul>
+<li class="level2"><div class="li"> Bill of Materials (BOM) files.</div>
+</li>
+<li class="level2"><div class="li"> Design Rule Checks (DRCs).</div>
+</li>
+<li class="level2"><div class="li"> Netlist files for use as input to various printed circuit board layout programs (e.g., Allegro, PADS, <strong>pcb</strong> (part of the gEDA Tool Suite), Protell, Tango, RACAL-REDAC, etc.).</div>
+</li>
+<li class="level2"><div class="li"> Files for input to SPICE simulation programs.</div>
+</li>
+<li class="level2"><div class="li"> VHDL code.</div>
+</li>
+<li class="level2"><div class="li"> Verilog code.</div>
+</li>
+<li class="level2"><div class="li"> etc.</div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> <strong>grenum</strong> – <strong>grenum</strong> is a gEDA Tool Suite productivity aid that will renumber the reference designators (i.e., refdes) in a [hierarchical set of] schematic files.</div>
+</li>
+<li class="level1"><div class="li"> <strong>gsch2pcb</strong> – The prefered method to create a netlist for the <strong>pcb</strong> printed circuit board layout tool (part of the gEDA Tool Suite).</div>
+</li>
+<li class="level1"><div class="li"> <strong>gspiceui</strong> – GNU Spice <acronym title="Graphical User Interface">GUI</acronym> (i.e., <strong>gspiceui</strong>) provides a <acronym title="Graphical User Interface">GUI</acronym> for freely available Spice electronic cicuit simulation engines (e.g., <strong>gnucap</strong> and <strong>ngspice</strong>). It uses <strong>gnetlist</strong> (to convert schematic files to net list files) and <strong>gwave</strong> (to display simulation results). gSchem is the preferred schematic capture tool.</div>
+</li>
+<li class="level1"><div class="li"> <strong>gsymcheck</strong> – A checker for symbols created with gEDA Tool Suite (e.g., <strong>gschem</strong>, <strong>tragesym</strong>, etc.).</div>
+</li>
+<li class="level1"><div class="li"> <strong>pcb</strong> – A tool for the layout of printed circuit boards.</div>
+</li>
+<li class="level1"><div class="li"> <strong>refdes_renum</strong> – Reads a [hierarchical set of] <strong>gschem</strong> schematic files and renumbers all reference designators. The reference designators are numbered starting with 1 and the old schematic file is replaced by the modified schematic file.</div>
+</li>
+<li class="level1"><div class="li"> <strong>tragesym</strong> – A python script that creates geda symbols from structured textfiles. The symbols usually need to be â??cleaned upâ?? in gschem.</div>
+</li>
+</ul>
+<table class="inline">
+ <tr>
+ <td> <a href="media/geda/gschem_workflow_01.jpg" class="media" target="_blank" title="geda:gschem_workflow_01.jpg"><img src="media/geda/gschem_workflow_01.jpg" class="media" alt="" /></a> </td>
+ </tr>
+</table>
+
+</div>
+<!-- SECTION "Overview" [2810-5392] -->
+<h1><a name="resources" id="resources">Resources</a></h1>
+<div class="level1">
+
+<p>
+The following on-line resources are useful for designers using <strong>gschem</strong>:
+</p>
+<ul>
+<li class="level1"><div class="li"> <a href="geda-gschem_warmup.html" class="wikilink1" title="geda-gschem_warmup.html">Bill Wilson's gschem warmup tutorial</a> – If you are new to the gEDA tools, read this before you read Billâ??s â??Bill Wilsonâ??s gsch2pcb tutorialâ??.</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-gsch2pcb_tutorial.html" class="wikilink1" title="geda-gsch2pcb_tutorial.html">Bill Wilson's gsch2pcb tutorial</a> – If you are new to the gEDA tools, this tutorial will bring you up to speed quickly.</div>
+</li>
+<li class="level1"><div class="li"> <a href="http://www.circuitcellar.com/"; class="urlextern" title="http://www.circuitcellar.com/"; rel="nofollow">Circuit Cellar Magazine</a> – Practical, hands-on applications and solutions for embedded designers:</div>
+<ul>
+<li class="level2"><div class="li"> gEDA Design Suite for Linux, by Stuart Brorson, Ales Hvezda, & Dan McMahill, Circuit Cellar magazine, March 2005 (Issue 176), p. 12</div>
+</li>
+<li class="level2"><div class="li"> Optical Proximity Sensor for Robots (Part 1): Simple PCB Design with the gEDA Suite, by Stuart Brorson, Circuit Cellar magazine, March 2006 (Issue 188), p. 48</div>
+</li>
+<li class="level2"><div class="li"> Optical Proximity Sensor for Robots (Part 2): Open-Source PCB Layout Editor, by Stuart Borson, Circuit Cellar magazine, April 2006 (Issue 189), p. 40</div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> <a href="http://www.gpleda.org/index.html"; class="urlextern" title="http://www.gpleda.org/index.html"; rel="nofollow">gEDA Project home page</a> – The homepage for the gEDA Tools Suite. </div>
+</li>
+<li class="level1"><div class="li"> <a href="http://sourceforge.net/tracker/?group_id=161080&atid=818426"; class="urlextern" title="http://sourceforge.net/tracker/?group_id=161080&atid=818426"; rel="nofollow">gEDA Bug Tracker</a> – On SourceForge</div>
+</li>
+<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki"; class="urlextern" title="http://geda.seul.org/wiki"; rel="nofollow">gEDA Project's Wiki</a> – All things related to the gEDA Tools Suite.</div>
+</li>
+<li class="level1"><div class="li"> <a href="http://www.gedasymbols.org"; class="urlextern" title="http://www.gedasymbols.org"; rel="nofollow">gedasymbols.org</a> – On-line repository of user-developed symbols for <strong>gschem</strong>, SPICE models, and footprints for <strong>pcb</strong>.</div>
+</li>
+<li class="level1"><div class="li"> John C. Lucianiâ??s proposed <a href="http://www.luciani.org/geda/pcb/footprint-name-spec.pdf"; class="urlextern" title="http://www.luciani.org/geda/pcb/footprint-name-spec.pdf"; rel="nofollow">Land Pattern Naming Convention</a> – Footprint naming conventions document, used by him, and often used by those submitting to the <a href="http://www.gedasymbols.org"; class="urlextern" title="http://www.gedasymbols.org"; rel="nofollow">gedasymbols.org</a> symbols/footprint repository.</div>
+</li>
+<li class="level1"><div class="li"> John C. Lucianiâ??s <a href="file:///shared/HomePages/dhart/index.html" class="urlextern" title="file:///shared/HomePages/dhart/index.html" rel="nofollow">PCB Footprints Library</a> – A rather inclusive collection of non-<acronym title="GNU General Public License">GPL</acronym> licensed footprints and the scripts used to create them.</div>
+</li>
+<li class="level1"><div class="li"> <a href="http://www.opencollector.org/"; class="urlextern" title="http://www.opencollector.org/"; rel="nofollow">OpenCollector</a> carries listings and news for free EDA software and circuit designs. Open Collector supports gEDA.</div>
+</li>
+<li class="level1"><div class="li"> <a href="http://alternatezone.com/electronics/files/PCBDesignTutorialRevA.pdf"; class="urlextern" title="http://alternatezone.com/electronics/files/PCBDesignTutorialRevA.pdf"; rel="nofollow">PCB Design Tutorial; RevA</a> – Document describing the process of taking a schematic to a pcb. Excellent for the beginner.</div>
+</li>
+<li class="level1"><div class="li"> <a href="http://pcblibraries.com/"; class="urlextern" title="http://pcblibraries.com/"; rel="nofollow">PCB Libraries website</a> – Advocates of the IPC standard Land Pattern (a.k.a., footprint) Naming Conventions and Land Pattern Calculators. A useful site if you have the money to subscribe to the services.</div>
+<ul>
+<li class="level2"><div class="li"> The free (windows-based) <a href="http://landpatterns.ipc.org/default.asp"; class="urlextern" title="http://landpatterns.ipc.org/default.asp"; rel="nofollow">IPC-7351 Land Pattern Viewer</a> is a very useful tool for viewing the latest IPC footprints.</div>
+</li>
+<li class="level2"><div class="li"> <a href="http://www.pcblibraries.com/resources/LibDoc.asp"; class="urlextern" title="http://www.pcblibraries.com/resources/LibDoc.asp"; rel="nofollow">CAD Data Files to be used with PCB Libraries' IPC-7351A LP Programs</a> – please note the license restrictions.</div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> <a href="http://www-mdp.eng.cam.ac.uk/urop05/files/gedalib/starting_gEDA.pdf"; class="urlextern" title="http://www-mdp.eng.cam.ac.uk/urop05/files/gedalib/starting_gEDA.pdf"; rel="nofollow">Starting with gEDA at the Cambridge University Engineering Department</a> – The Cambridge University Engineering Departmentâ??s tutorial for using gEDA.</div>
+</li>
+<li class="level1"><div class="li"> <a href="http://www.brorson.com/gEDA/"; class="urlextern" title="http://www.brorson.com/gEDA/"; rel="nofollow">Stuart Brorson's gEDA tools and tips</a> – gEDA related tools and information.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Resources" [5393-8619] -->
+<h1><a name="how_to_ask_questions" id="how_to_ask_questions">How To Ask Questions</a></h1>
+<div class="level1">
+
+<p>
+<strong>gschem</strong> is an OpenSource, community driven, development. As such, the emphasis has been on developing the gEDA Tools Suite, not on developing commercial-level documentation and support. Much of the burden on learning how to use the gEDA Tools Suite applications is placed on the user, who must understand the basics of electronics, Electronics Design Automation (EDA), and the terminology used in schematic capture, circuit simulation, and printed circuit board design.<br/>
+ As a typical OpenSource development, the gEDA Tools Suite development community provides timely and insightful response to user inquiries, but please perform the following steps before bothering the developers (they need to focus on making gEDA Tools Suite applications better, and you can actually learn to answer your own questions and become independent of the developers):
+</p>
+<ol>
+<li class="level1"><div class="li"> Read Rick Moenâ??s <a href="http://www.catb.org/~esr/faqs/smart-questions.html"; class="urlextern" title="http://www.catb.org/~esr/faqs/smart-questions.html"; rel="nofollow">How To Ask Questions The Smart Way</a>, about how to ask for help. This is a must read for everybody.</div>
+</li>
+<li class="level1"><div class="li"> Read this document. I know, itâ??s a lot to expect engineers to actually read a userâ??s guide. The latest version of this document is maintained on the gEDA web-site at <a href="http://geda.seul.org/wiki/geda:gschem_ug"; class="urlextern" title="http://geda.seul.org/wiki/geda:gschem_ug"; rel="nofollow">gschem User Guide</a>. The information should be here. If it isnâ??t, comment to the fact in one of the on-line documentâ??s â??Discussionâ?? areas (at the bottom of each wiki-page). Helpful comments are clear, to the point, and may even contain the wording that should be inserted into the document.</div>
+</li>
+<li class="level1"><div class="li"> Read the <a href="geda-faq-gschem.html" class="wikilink1" title="geda-faq-gschem.html">gschem Frequently Asked Questions (FAQ)</a> wiki-page. This on-line document is updated often to reflect user and developer experiences with <strong>gschem</strong>.</div>
+</li>
+<li class="level1"><div class="li"> Read the <a href="geda-documentation.html" class="wikilink1" title="geda-documentation.html">gEDA/gaf Documentation</a>. This information was installed on your computer if the gEDA Tools Suite was installed from the gEDA Binary Suite installer.</div>
+</li>
+<li class="level1"><div class="li"> <a href="http://www.google.com"; class="urlextern" title="http://www.google.com"; rel="nofollow">Google</a> is your friend. People that have asked questions that obviously didnâ??t do any simple Google search will not be treated well when asking for help. This is particularly true if your problem is not unique to the gEDA Tools Suite applications.</div>
+</li>
+<li class="level1"><div class="li"> Ask for a pointer to the right direction. It is considered good â??net etiquetteâ?? to ask for a pointer to information, so that you can learn where such information can be found, rather than have someone search the information for you.</div>
+</li>
+<li class="level1"><div class="li"> If you are software literate, look at the source code to see what it is doing.</div>
+</li>
+<li class="level1"><div class="li"> Subscribe to the gEDA e-mail lists (i.e., you can only post to the e-mail lists if you are a subscriber). Then:</div>
+<ol>
+<li class="level2"><div class="li"> Start reading recent messages in the <a href="http://archives.seul.org/geda/user/"; class="urlextern" title="http://archives.seul.org/geda/user/"; rel="nofollow">geda-user e-mail list archives</a>. Get a feel for the listâ??s ettiquite so that you learn how to properly ask questions.</div>
+</li>
+<li class="level2"><div class="li"> Search the archives for issues similar to yours. You may find the question has been asked of the developers and users before, and answered.</div>
+</li>
+<li class="level2"><div class="li"> In the event that you can find no information concerning your problem, submit a concise description of the problem and a request for the type of help you are requesting.</div>
+</li>
+</ol>
+</li>
+</ol>
+
+</div>
+<!-- SECTION "How To Ask Questions" [8620-11789] -->
+<h1><a name="installing_gschem" id="installing_gschem">Installing gschem</a></h1>
+<div class="level1">
+
+<p>
+As a mature OpenSource project, the gEDA Tools Suite and its components have been installed on many Linux distributions. The following are by no means the only methods of installing the gEDA Tools Suite and/or its components.
+</p>
+
+</div>
+<!-- SECTION "Installing gschem" [11790-12048] -->
+<h2><a name="latest_stable" id="latest_stable">Latest Stable</a></h2>
+<div class="level2">
+
+<p>
+<strong>gschem</strong> is a component of the gEDA/gaf set of tools which tend to integrate together in the development and maintenance of schematics and symbols. The term â??gafâ?? stands for â??<em class="u">g</em>EDA <em class="u">a</em>nd <em class="u">f</em>riendsâ??). The gEDA/gaf applications are actually rather stable, and receive significant testing prior to release.<br/>
+ There are multiple methods of installing <strong>gschem</strong>. The appropriate method depends on your distribution. See the following for some examples.
+</p>
+
+</div>
+<!-- SECTION "Latest Stable" [12049-12535] -->
+<h3><a name="geda_binary_suite" id="geda_binary_suite">gEDA Binary Suite</a></h3>
+<div class="level3">
+
+<p>
+If you do not have gEDA packages available for your GNU/Linux distribution, you can install most of the tools using the gEDA Binary Suite Installer.
+</p>
+
+<p>
+The latest version of this binary suite is available as a tarball from the <a href="http://www.gpleda.org/download.html"; class="urlextern" title="http://www.gpleda.org/download.html"; rel="nofollow">gEDA Downloads</a> web-page.
+</p>
+
+<p>
+Please read the <a href="http://geda.seul.org/dist/suite/v0.0.2/README"; class="urlextern" title="http://geda.seul.org/dist/suite/v0.0.2/README"; rel="nofollow">README</a> for more information on how to install the gEDA Binary Suite.
+</p>
+
+</div>
+<!-- SECTION "gEDA Binary Suite" [12536-12991] -->
+<h3><a name="debian_based_distributions" id="debian_based_distributions">Debian based distributions</a></h3>
+<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 binary packages provide a hassle free way to install the core of geda.
+</p>
+
+</div>
+<!-- SECTION "Debian based distributions" [12992-13252] -->
+<h3><a name="fedora_and_redhat_distributions" id="fedora_and_redhat_distributions">Fedora and RedHat distributions</a></h3>
+<div class="level3">
+
+<p>
+For RedHat distributions you may wish to download the <a href="http://www.sp5pbe.waw.pl/~sp5smk/software.html"; class="urlextern" title="http://www.sp5pbe.waw.pl/~sp5smk/software.html"; rel="nofollow"> RPM binaries</a> prepared by Wojciech Kazubski.
+</p>
+
+<p>
+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 information, read the <a href="geda-fedora_rpm_installation.html" class="wikilink1" title="geda-fedora_rpm_installation.html"> fedora rpm installation notes</a>.
+</p>
+
+</div>
+<!-- SECTION "Fedora and RedHat distributions" [13253-13658] -->
+<h3><a name="suse_and_opensuse_distributions" id="suse_and_opensuse_distributions">SuSE and OpenSuSE distributions</a></h3>
+<div class="level3">
+
+<p>
+For SuSE and OpenSuSE distributions there are rpm packages for several gEDA related programms. Theyâ??ve been prepared by Werner Hoch using the OpenSuSE Build Service.
+</p>
+
+<p>
+You can install the rpm packages with YaST, yum or any other installation tool. The packages are located at <a href="ftp://ftp-1.gwdg.de/pub/opensuse/repositories/science/"; class="urlextern" title="ftp://ftp-1.gwdg.de/pub/opensuse/repositories/science/"; rel="nofollow">ftp://ftp-1.gwdg.de/pub/opensuse/repositories/science/</a>.
+</p>
+
+<p>
+For more informations read the <a href="geda-suse_rpm_installation.html" class="wikilink1" title="geda-suse_rpm_installation.html"> SuSE rpm installation notes</a>.
+</p>
+
+</div>
+<!-- SECTION "SuSE and OpenSuSE distributions" [13659-14130] -->
+<h3><a name="mac_osx_distributions" id="mac_osx_distributions">Mac OSX distributions</a></h3>
+<div class="level3">
+
+<p>
+For Mac OSX 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 Fink binaries</a> prepared by Charles Lepple.
+</p>
+
+</div>
+<!-- SECTION "Mac OSX distributions" [14131-14311] -->
+<h2><a name="developer_unstable_testing" id="developer_unstable_testing">Developer Unstable/Testing</a></h2>
+<div class="level2">
+
+<p>
+For those already familiar with the gEDA/gaf applications, access to the development repository is available. This is the latest developer source-code version of the application.<br/>
+ Installation from development repository (git based) is appropriate for those:
+</p>
+<ul>
+<li class="level1"><div class="li"> Seeking a solution to a specific problem that was submitted to the development team, to test the â??fixâ?? so that the developers can be informed that the â??fixâ?? works.</div>
+</li>
+<li class="level1"><div class="li"> With significant working knowledge of the â??gEDA Suiteâ?? and industry expertise, wishing to test the latest version of the application(s) prior to the next release. This usually requires access to several existing designs known to work in the current stable release of the â??gEDA Suiteâ??, so that comparisons can be made and issues brought to the attention of the developer/user community (via the e-mail lists).</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Developer Unstable/Testing" [14312-15197] -->
+<h1><a name="configuring_gschem" id="configuring_gschem">Configuring gschem</a></h1>
+<div class="level1">
+
+<p>
+Assume that you have installed the gEDA Binary Suite (the most common installation method), and that you are ready to configure <strong>gschem</strong> to your personal likes. When installing, you were prompted for the path where the gEDA executables would be placed. The default was the <strong>/home/{login id}/geda-install</strong> directory, where {login id} is the username you logged into your account with, but you may have changed this to another directory on the computer. This directory is referred to below as the <strong>{binary-install-path}</strong> because this is where the gEDA binary executables are placed. If you forgot where the binaries were installed, simply issue the following command to find where <strong>gschem</strong> is installed (in this case the {binary-install-path} is <strong>/usr/local/gEDA-20060124</strong>): <pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">% which gschem
+/usr/local/gEDA-20060124/bin/gschem
+%</font></pre>
+</p>
+
+<p>
+The gEDA Tools Suite applications follow normal Unix/Linux conventions for placement of configuration files; there are usually system-wide, user-wide, and project-specific configuration settings. The system-wide settings are placed in a sub-directory of the {binary-install-path}. The user-wide settings are placed in the userâ??s home directory, also known as the login directory (referred to in Unix/Linux parlance as the <strong>$HOME</strong> directory). The project-specific settings are placed in a project-specific directory.<br/>
+
+</p>
+
+<p>
+Now that we know the above, we can configure <strong>gschem</strong>.<br/>
+ <strong>gschem</strong> is highly configurable. All configuration is handled through the following resource files (written using the GNU Guile programming language, an interpreter for Scheme, a version of Lisp):
+</p>
+<ul>
+<li class="level1"><div class="li"> <strong>system-gschemrc</strong>: The system-wide initialization file for <strong>gschem</strong>. Installed in the {binary-install-path}/share/gEDA/system-gschemrc file, it is required for <strong>gschem</strong> to run. Users should not modify this file, but should override the settings in this file by creating their own $HOME/.gEDA/gschemrc file and/or â??pwdâ??/gschemrc file and putting the new settings in those files. The {binary-install-path} directory is where your gEDA/gaf executables were installed, including <strong>gschem</strong>. Depends on your install method. Refer to <a href="docs-20060124-gschem_ug-installing_gschem.html" class="wikilink2" title="docs-20060124-gschem_ug-installing_gschem.html">Installing gschem</a> for more details.</div>
+</li>
+<li class="level1"><div class="li"> <strong>$HOME/.gEDA/gschemrc</strong>: The per-user initialization file for <strong>gschem</strong>. Created by the user under the userâ??s home directory. Settings placed in this file will override settings in the system-gschemrc file. Users should put settings in this file they want to apply to all of their sessions, such as (to change the default black background color scheme to a light background color scheme):</div>
+</li>
+</ul>
+
+<p>
+<pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">; Load up a color scheme
+(load (build-path geda-rc-path "gschem-lightbg")) ; light background</font></pre>
+</p>
+<ul>
+<li class="level1"><div class="li"> <strong>â??pwdâ??/gschemrc</strong>: The per-project initialization file for <strong>gschem</strong>. Created by the user in the userâ??s project directory. Settings placed in this file will override settings in both the system-gschemrc file and the $HOME/.gEDA/gschemrc file. Users should put settings in this file they want to apply to this particular project, such as (to autonumber reference designators when components are placed on the schematic):</div>
+</li>
+</ul>
+
+<p>
+<pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">; Comment in this scheme code if you want automatic numbering when
+; placing new component and copying components
+;
+(load (string-append gedadata "/scheme/auto-uref.scm"))
+(add-hook! add-component-hook auto-uref)</font></pre>
+</p>
+<ul>
+<li class="level1"><div class="li"> <strong>system-gafrc</strong>: The system-wide initialization file for gEDA/gaf applications (includes <strong>gschem</strong>, <strong>gnetlist</strong>). Installed in the {binary-install-path}/share/gEDA/system-gafrc file, it is required for <strong>gschem</strong> to run. Users should not modify this file, but should override the settings in this file by creating their own $HOME/.gEDA/gafrc file and/or â??pwdâ??/gafrc file and putting the new settings in those files. The {binary-install-path} directory is where your gEDA/gaf executables were installed, including <strong>gschem</strong>. Depends on your install method. Refer to <a href="docs-20060124-gschem_ug-installing_gschem.html" class="wikilink2" title="docs-20060124-gschem_ug-installing_gschem.html">Installing gschem</a> for more details.</div>
+</li>
+<li class="level1"><div class="li"> <strong>$HOME/.gEDA/gafrc</strong>: The per-user initialization file for gEDA/gaf applications. Created by the user under the userâ??s home directory. Settings placed in this file will override settings in the system-gafrc file. Users should put settings in this file they want to apply to all of their sessions. </div>
+</li>
+<li class="level1"><div class="li"> <strong>â??pwdâ??/gafrc</strong>: The per-project initialization file for the gEDA/gaf applications. Created by the user in the userâ??s project directory. Settings placed in this file will override settings in both the system-gafrc file and the $HOME/.gEDA/gafrc file. Users should put settings in this file they want to apply to this particular project. Settings such as the <strong>component-library</strong> or <strong>source-library</strong> keywords go into this file.</div>
+</li>
+<li class="level1"><div class="li"> <strong>gschem-gtkrc</strong>: Installed in the {binary-install-path}/share/gEDA/gschem-gtkrc file. Used to define the font for all gtk+ widgets in <strong>gschem</strong>.</div>
+</li>
+</ul>
+
+<p>
+ A few comments about changing the files:
+</p>
+<ul>
+<li class="level1"><div class="li"> Donâ??t break any guile syntax rules. Doing so will cause the scheme interpreter (guile) to stop interpreting.</div>
+</li>
+<li class="level1"><div class="li"> To add a setting to the $HOME/.gEDA/gschemrc file (or to the â??pwdâ??/gschemrc file), copy the settingâ??s text from the {binary-install-directory}/share/gEDA/system-gschemrc file to the $HOME/.gEDA/gschemrc file (or the â??pwdâ??/gschemrc file) and make the setting change there.</div>
+</li>
+<li class="level1"><div class="li"> To add a setting to the $HOME/.gEDA/gafrc file (or the â??pwdâ??/gafrc file), copy the relevant settingâ??s text from the {binary-install-directory}/share/gEDA/system-gafrc file to the $HOME/.gEDA/gafrc file (or the â??pwdâ??/gafrc file) and make the setting change there.</div>
+</li>
+<li class="level1"><div class="li"> Keywords/defaults always override what came before, with the exception of cumulative keywords (like component-library).</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Configuring gschem" [15198-20971] -->
+<h2><a name="gschemrc" id="gschemrc">gschemrc</a></h2>
+<div class="level2">
+
+<p>
+The {binary-install-path}/share/gEDA/system-gschemrc file is well commented. Read this file for more details on the settings available.<br/>
+ Some of the settings appropriate for override (by placing in either the userâ??s $HOME/gschemrc file or the projectâ??s â??pwdâ??/gschemrc file) are:
+</p>
+
+</div>
+<!-- SECTION "gschemrc" [20972-21273] -->
+<h2><a name="gafrc" id="gafrc">gafrc</a></h2>
+<div class="level2">
+
+<p>
+The {binary-install-path}/share/gEDA/system-gafrc file is well commented. Read this file for more details on the settings available.<br/>
+ Some of the settings appropriate for override (by placing in either the userâ??s $HOME/gafrc file or the projectâ??s â??pwdâ??/gafrc file) are:
+</p>
+
+</div>
+<!-- SECTION "gafrc" [21274-21563] -->
+<h1><a name="running_gschem" id="running_gschem">Running gschem</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "Running gschem" [21564-21595] -->
+<h2><a name="confirming_gschem_is_installed" id="confirming_gschem_is_installed">Confirming gschem is installed</a></h2>
+<div class="level2">
+
+<p>
+You should determine if <strong>gschem</strong> has been correctly installed on your Linux computer.<br/>
+ Log into your Linux account, and launch your favorite interactive shell. The different Linux distributions will usually offer more than one interactive shell such as xterm, gnome-term, konsole, etc.<br/>
+ You will see a shell prompt, which will depend on your Linux distribution and on your selection of interactive shell. It is common practice in Linux documentation to refer to the userâ??s interactive login shell prompt as â??<strong>%</strong>â??, and to refer to the superuserâ??s (i.e., user â??rootâ??) interactive login shell prompt as â??<strong>#</strong>â??.<br/>
+ At the shell prompt, enter the following commands to determine if <strong>gschem</strong> is installed:
+</p>
+
+<p>
+<pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">% <strong>echo $PATH</strong>
+<strong>/usr/local/gEDA-20060124/bin</strong>:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/home/<strong>gEDA</strong>/bin
+% <strong>which gschem</strong>
+/usr/local/gEDA-20060124/bin/gschem
+% <strong>ldd /usr/local/gEDA-20060124/bin/gschem</strong>
+ linux-gate.so.1 => (0x00345000)
+ libgeda.so.25 => /usr/local/gEDA-20060124/lib/libgeda.so.25 (0x00d7d000)
+ libguile.so.12 => /usr/lib/libguile.so.12 (0x00588000)
+ libguile-ltdl.so.1 => /usr/lib/libguile-ltdl.so.1 (0x00b62000)
+ libqthreads.so.12 => /usr/lib/libqthreads.so.12 (0x009f7000)
+ libpthread.so.0 => /lib/libpthread.so.0 (0x006d4000)
+ libcrypt.so.1 => /lib/libcrypt.so.1 (0x03266000)
+ libgdk-x11-2.0.so.0 => /usr/lib/libgdk-x11-2.0.so.0 (0x00c10000)
+ libgdk_pixbuf-2.0.so.0 => /usr/lib/libgdk_pixbuf-2.0.so.0 (0x006ac000)
+ libm.so.6 => /lib/libm.so.6 (0x008df000)
+ libpangoxft-1.0.so.0 => /usr/lib/libpangoxft-1.0.so.0 (0x003e7000)
+ libpangox-1.0.so.0 => /usr/lib/libpangox-1.0.so.0 (0x00a57000)
+ libpango-1.0.so.0 => /usr/lib/libpango-1.0.so.0 (0x00bd8000)
+ libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0x00a01000)
+ libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0x009fb000)
+ libdl.so.2 => /lib/libdl.so.2 (0x00906000)
+ libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x0448e000)
+ libgtk-x11-2.0.so.0 => /usr/lib/libgtk-x11-2.0.so.0 (0x06a81000)
+ libatk-1.0.so.0 => /usr/lib/libatk-1.0.so.0 (0x00c96000)
+ libSM.so.6 => /usr/X11R6/lib/libSM.so.6 (0x00d4f000)
+ libICE.so.6 => /usr/X11R6/lib/libICE.so.6 (0x00d33000)
+ libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00921000)
+ libc.so.6 => /lib/libc.so.6 (0x007b4000)
+ /lib/ld-linux.so.2 (0x00796000)
+ libXrandr.so.2 => /usr/X11R6/lib/libXrandr.so.2 (0x00bac000)
+ libXi.so.6 => /usr/X11R6/lib/libXi.so.6 (0x00cca000)
+ libXinerama.so.1 => /usr/X11R6/lib/libXinerama.so.1 (0x00bb2000)
+ libXft.so.2 => /usr/X11R6/lib/libXft.so.2 (0x00ad1000)
+ libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x00af8000)
+ libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0x00111000)
+ libXfixes.so.3 => /usr/X11R6/lib/libXfixes.so.3 (0x00d0d000)
+ libXcursor.so.1 => /usr/X11R6/lib/libXcursor.so.1 (0x00bcc000)
+ libXrender.so.1 => /usr/X11R6/lib/libXrender.so.1 (0x00ba2000)
+ libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x00a82000)
+ libpangoft2-1.0.so.0 => /usr/lib/libpangoft2-1.0.so.0 (0x05362000)
+ libexpat.so.0 => /usr/lib/libexpat.so.0 (0x0068b000)
+ libz.so.1 => /usr/lib/libz.so.1 (0x0090c000)</font></pre>
+</p>
+
+<p>
+The <strong>echo $PATH</strong> command displays the userâ??s current setting for the <strong>PATH</strong> environment variable. In the above example for a Fedora Core 4 installation, user <strong>gEDA</strong> executed the command and determined that the <strong>PATH</strong> included the /usr/local/gEDA-20060124/bin directory (this will differ depending on where you put the gEDA Tools Suite executables).
+</p>
+<ol>
+<li class="level1"><div class="li"> Set your $PATH environment variable to {the directory where you installed the gEDA executables}</div>
+</li>
+<li class="level1"><div class="li"> Set your $LD_LIBRARY_PATH environment variable to {the directory in where you installed the gEDA libraries}</div>
+</li>
+</ol>
+
+<p>
+ The <strong>which</strong> command displays the full path of a commandâ??s executable, searching for the command on the userâ??s list of directories, as defined in the <strong>PATH</strong> environment variable. In this case, it will return the full path to the <strong>gschem</strong> executable if it is on the userâ??s <strong>PATH</strong>. If this command does not return the full path to the <strong>gschem</strong> executable, make sure your <strong>PATH</strong> environment variable has been properly set.
+</p>
+
+<p>
+The <strong>ldd</strong> command displays shared libraries required by a program. All of the requested libraries must be found for <strong>gschem</strong> to run. Donâ??t be intimidated by the long list of libraries, this is common for mature Linux applications. If we had not received this output (or something very similar), we would have to check on our setting for the <strong>LD_LIBRARY_PATH</strong> environment variable.
+</p>
+
+<p>
+And of course, there is always attempting to just run <strong>gschem</strong> as follows: <pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">% <strong>gschem -h</strong>
+Usage: gschem [OPTIONS] schematic_filename1 ... schematic_filenameN
+ -q Quiet mode
+ -v Verbose mode on
+ -r filename Rc filename
+ -s filename Script (guile) filename
+ -o filename Output filename (for printing)
+ -p Automatically place the window
+ -t Print stroke information
+ -h Help; this message</font></pre>
+</p>
+
+<p>
+where we displayed the <strong>gschem</strong> help.
+</p>
+
+<p>
+If these commands do not return the expected results, then most likely the gEDA tools are not installed properly. Please see the appropriate INSTALL docs (which came with the gEDA distribution) for more info on installing the gEDA tools. <br/>
+
+</p>
+
+</div>
+<!-- SECTION "Confirming gschem is installed" [21596-27003] -->
+<h2><a name="the_shell_prompt" id="the_shell_prompt">The Shell Prompt</a></h2>
+<div class="level2">
+<table class="inline">
+ <tr>
+ <td> <a href="media/geda/terminal_screenshot_001.jpg" class="media" target="_blank" title="geda:terminal_screenshot_001.jpg"><img src="media/geda/terminal_screenshot_001.jpg" class="media" alt="" /></a> </td>
+ </tr>
+ <tr>
+ <td> Figure 1 – gnome-terminal </td>
+ </tr>
+</table>
+
+<p>
+ You launch <strong>gschem</strong> from your favorite shell prompt (in this case, gnome-terminal on Fedora Core 4).<br/>
+ There are several command-line switches:
+</p>
+<ul>
+<li class="level1"><div class="li"> <strong>-q</strong> – Quiet mode<br/>
+ Turns on â??quiet modeâ??. Output (i.e., stdout and stderr) is not generated to the shell. Useful if calling <strong>gschem</strong> from a script (e.g., bash, sh, csh, etc.) to perform batch operations such as printing a large number of schematics or symbols.</div>
+</li>
+<li class="level1"><div class="li"> <strong>-v</strong> – Verbose mode ON<br/>
+ Generate verbose information. Not used very much in <strong>gschem</strong>.</div>
+</li>
+<li class="level1"><div class="li"> <strong>-r filename</strong> – Process additional configuration settings from <strong>filename</strong><br/>
+ <strong>filename</strong> is a file containing settings of the form found in either system-gschemrc or system-gafrc<br/>
+ In addition to the following files, <strong>gschem</strong> will process <strong>filename</strong> for additional configuration settings:<br/>
+ * {binary-install-path}/share/gEDA/system-gschemrc<br/>
+ * $HOME/gschemrc<br/>
+ * â??pwdâ??/gschemrc<br/>
+ * {binary-install-path}/share/gEDA/system-gafrc<br/>
+ * $HOME/gafrc<br/>
+ * â??pwdâ??/gafrc</div>
+</li>
+<li class="level1"><div class="li"> <strong>-s filename</strong> – Process <strong>filename</strong> as a guile script<br/>
+ The name of a script file (written in guile) for <strong>gschem</strong> to process.<br/>
+ Refer to <a href="docs-20060124-gschem_ug-app_b.html" class="wikilink2" title="docs-20060124-gschem_ug-app_b.html">Appendix B -- Printing Schematics and Symbols</a> and <a href="docs-20060124-gschem_ug-app_c.html" class="wikilink2" title="docs-20060124-gschem_ug-app_c.html">Appendix C -- Writing guile Scripts</a> for more details.<br/>
+ For example, in your $HOME/geda-sources/gedagaf/{gEDA Tools Suite version}/scripts/ directory is the <strong>print.scm</strong> file, a template script file directing <strong>gschem</strong> to generate a PostScript file of a schematic appropriate for printing. This <strong>print.scm</strong> file works as is, but you may want to customize it for your own needs. To print the schematic_1.sch schematic to the schematic_1.ps PostScript file from within a bash script, you would enter: <code>gschem -q -p -o schematic_1.ps -s print.scm schematic_1.sch</code><br/>
+ Then, simply use your favorite printing solution to print the file, such as: <code>lp schematic_1.ps</code><br/>
+ to a PostScript printer.</div>
+</li>
+<li class="level1"><div class="li"> <strong>-o filename</strong> – Output <strong>filename</strong> (e.g., for printing)<br/>
+ Specify the output filename. For example, as used to specify the Postscript filename in the example above.</div>
+</li>
+<li class="level1"><div class="li"> <strong>-p</strong> – Automatically place the window<br/>
+ Donâ??t wait for the windowmanager to place the window.<br/>
+ When a new window is opened, some window managers display the bounding box of the window and wait for the user to place the window manually. The "-pâ?? option avoids that, letting the window manager decide where to put the new window.</div>
+</li>
+<li class="level1"><div class="li"> <strong>-t</strong> – Print stroke information<br/>
+ </div>
+</li>
+<li class="level1"><div class="li"> <strong>-h</strong> – Help<br/>
+ Generate a short usage printout.</div>
+</li>
+</ul>
+
+<p>
+ Running <strong>gschem</strong> is straightforward once you have installed it on your GNU/Linux system.<br/>
+ Although <strong>gschem</strong> is a <acronym title="Graphical User Interface">GUI</acronym> application, <strong>gschem</strong> is meant to be launched from the command-line, as it takes command-line arguements (see Figure 1 above).<br/>
+ To open an empty schematic, run: <code><strong>% gschem</strong></code><br/>
+
+</p>
+
+<p>
+To open a specific schematic, run: <code><strong>% gschem schematic_name.sch</strong></code><br/>
+
+</p>
+
+<p>
+To open a list of schematics, run: <code><strong>% gschem schematic_1.sch schematic_2.sch, schematic_3.sch …</strong></code><br/>
+ or use wildcards to specify multiple filenames: <code><strong>% gschem schematic_*.sch</strong></code>
+</p>
+
+<p>
+As operations are performed in the <strong>gschem</strong> <a href="docs-20060124-gschem_ug-the_main_window.html" class="wikilink2" title="docs-20060124-gschem_ug-the_main_window.html">Main Window</a> the <strong>gschem</strong> <a href="docs-20060124-gschem_ug-the_status_window.html" class="wikilink2" title="docs-20060124-gschem_ug-the_status_window.html">Status Window</a> continues to output information, and the shell promptâ??s window continues to output information, consisting of:
+</p>
+<ul>
+<li class="level1"><div class="li"> …</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "The Shell Prompt" [27004-30538] -->
+<h2><a name="backups" id="backups">Backups</a></h2>
+<div class="level2">
+
+<p>
+There are two basic mechanisms in <strong>gschem</strong> for backing up schematics and symbols, classic Linux backups and incremental backups.
+</p>
+
+</div>
+<!-- SECTION "Backups" [30539-30690] -->
+<h3><a name="classic_linux_backups" id="classic_linux_backups">Classic Linux backups</a></h3>
+<div class="level3">
+
+<p>
+While creating and/or editing schematic file(s) or symbol file(s), snapshots are triggered by the <strong>autosave</strong> interval setting in the {binary-install-path}/share/gEDA/system-gschemrc file (see <a href="#relevant_configuration_settings" title=":geda:gschem_ug.txt ↵" class="wikilink1">Relevant configuration settings</a> below). If the file has not been manually saved, and the interval expires (current default 2 minutes), the snapshot is saved the next time a change is made in the <strong>gschem</strong> main window (to either a schematic or to a symbol). The interval timer starts again as soon as the snapshot file(s) have been written, and once the timer expires the next change to the main window will trigger the snapshot to be written.<br/>
+ This snapshot includes all work up to, but not including, the last operation performed in the <strong>gschem</strong> main window. This is to allow for easier recovery from a crash that may have been caused by the last operation.<br/>
+ When <strong>gschem</strong> exits normally, the snapshot file(s) are deleted. So, if <strong>gschem</strong> were to crash, or not terminate normally for some reason (e.g., power failure, soda → keyboard, etc.), the shapshot file(s) would be found the next time <strong>gschem</strong> opened the file(s). <strong>gschem</strong> will display the following warning message when it finds a snapshot file associated with the schematic file(s) or symbol file(s) it opens: <pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">WARNING: Found and autosave backup file:
+ {full path to autosave file}
+
+The backup copy is newer than the schematic, so it seems you
+should load it instead of the original fil.
+Gschem usually makes backup copies automatically, and this
+situation happens when it crashed or it was forced to exit
+abruptely.
+
+If you load the original file, the backup file will be overwritten in
+the next autosave timeout and it will be lost.
+
+Do you want to load the backup file?</font></pre>
+</p>
+
+<p>
+The snapshots are saved to a file whose filename is constructed from the original filename (schematic or symbol) as follows:
+</p>
+<ul>
+<li class="level1"><div class="li"> add a "#" to the beginning of the original filename</div>
+</li>
+<li class="level1"><div class="li"> add a "#" to the end</div>
+</li>
+</ul>
+
+<p>
+ so that:
+</p>
+<ul>
+<li class="level1"><div class="li"> â??schematic_1.schâ?? becomes "#schematic_1.sch#"</div>
+</li>
+<li class="level1"><div class="li"> â??symbol.symâ?? becomes "#symbol.sym#"</div>
+</li>
+</ul>
+
+<p>
+ And yes, the "#" at the front and back of the filename are part of the filename.<br/>
+
+</p>
+
+<p>
+When the user does finally manually save the file, the original file (i.e., the file that was opened) is renamed to "{filename~}" and the latest snapshot file (i.e., "#{filename}#") gets copied as "{filename}". Note that this new "{filename}" file may not contain the latest information as displayed on the <strong>gschem</strong> main window, as the <strong>autosave</strong> interval timer may not have expired since the last change to the schematic/symbol.<br/>
+ When the user finally decides to close <strong>gschem</strong>, the latest snapshot file (i.e., "#{filename}#") is saved to the original file (i.e., "{filename}".<br/>
+ When you exit <strong>gschem</strong> and are prompted to save any unsaved schematic file(s) or symbol file(s), this constitutes a manual save.
+</p>
+
+</div>
+<!-- SECTION "Classic Linux backups" [30691-33597] -->
+<h3><a name="incremental_backups" id="incremental_backups">Incremental backups</a></h3>
+<div class="level3">
+
+</div>
+<!-- SECTION "Incremental backups" [33598-33631] -->
+<h3><a name="relevant_configuration_settings" id="relevant_configuration_settings">Relevant configuration settings</a></h3>
+<div class="level3">
+
+<p>
+There are the following configuration settings in the {binary-install-path}/share/gEDA/system-gschemrc file that effect backups:
+</p>
+<ul>
+<li class="level1"><div class="li"> <strong>undo-control</strong> : Controls if the undo feature is enabled or not.</div>
+</li>
+<li class="level1"><div class="li"> <strong>undo-levels</strong> : Determines the number of levels of undo. Basically this number decides how many backup schematics are saved.</div>
+</li>
+<li class="level1"><div class="li"> <strong>undo-type</strong> : Controls which kind of undo is used, disk or memory. The default is to use the disk as the storage medium (i.e., after every action the undo information is stored to a new file on disk). The disk mechanism is nice because you get that many backups of the schematic, written to disk as backups, so you should never lose a schematic due to a crash.</div>
+</li>
+<li class="level1"><div class="li"> <strong>autosave</strong> : Controls if a backup copy is made every â??intervalâ?? seconds. Note that a backup copy is only made when you make some change to the schematic, and there were more than â??intervalâ?? seconds from the last autosave. Autosaving will not be allowed if the â??intervalâ?? setting is set to zero.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Relevant configuration settings" [33632-34673] -->
+<h2><a name="on-line_documentation" id="on-line_documentation">On-line documentation</a></h2>
+<div class="level2">
+
+<p>
+For a listing of the various command line flags run â??<strong>gschem -h</strong>â??: <pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">% <strong>gschem -h</strong>
+Usage: gschem [OPTIONS] schematic_filename1 ... schematic_filenameN
+ -q Quiet mode
+ -v Verbose mode on
+ -r filename Rc filename
+ -s filename Script (guile) filename
+ -o filename Output filename (for printing)
+ -p Automatically place the window
+ -t Print stroke information
+ -h Help; this message</font></pre>
+</p>
+
+<p>
+For a detailed explanation of the command line flags look at the <strong>gschem</strong> man page: <pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">% <strong>man gschem</strong>
+gschem(1) 20031231 gschem(1)
+
+
+
+NAME
+ gschem - gEDA/gaf Schematic Capture
+
+SYNOPSIS
+ gschem [-q] [-v] [-t] [-r rcfilename] [-s scriptfilename] [-o output-
+ filename] [-p] [schematic1 ... schematicN]
+
+DESCRIPTION
+ gschem is the schematic capture program which is part gEDA (GPL Elec-
+ tronic Design Automation) toolset. This program is used to draw elec-
+ tronic schematics. Schematics consist of standard symbols (which are
+ either part of a standard library or created by the user) which repre-
+ sent the various gates and components. These components are then
+ interconnected by nets (wires). Schematics may be printed to a
+ PostScript file for printing or further conversion to other output for-
+ mats.
+
+ gschem is also the symbol creation editor. All the standard methods of
+ creating schematics are used in the creation of symbols. There are a
+ few special rules when creating symbols, so please refer to the (non-
+ existant as of now) symbol creation document.
+
+ Please read the official documentation (very minimal at this point) on
+ how to use gschem, since this man page just describes the command line
+ arguments and a few examples on how to run gschem.
+
+
+OPTIONS
+ gschem accepts the following options:
+
+ -q Quiet mode on. This mode turns off all warnings/notes/mes-
+ sages. (optional)
+
+ -v Verbose mode on. This mode gives as much feedback to the user
+ as possible. (optional)
+
+ -t Print out more information when using mouse strokes. With this
+ command line flag and the middle button configured for mouse
+ strokes, gschem will output the stroke sequence numbers as the
+ user executes strokes. These numbers can be used to define new
+ strokes in the system-gschemrc file.
+
+ -r filename
+ Specify a rc filename. Normally gschem searches for the sys-
+ tem-gschemrc, then ~/.gEDA/gschemrc, and finally for a gschemrc
+ in the current directory. This options allows the user to
+ specify an additional rc file which is read after all the other
+ rc files are read. (optional)
+
+ -s filename
+ Specify a guile script to be executed at startup. (optional)
+
+ -o filename
+ Specify a filename for postscript output. This command line
+ argument is useful when running gschem from a shell script and
+ with a guile script. The filename can be changed through the
+ print dialog box.
+
+ -p Automatically place the window, especially useful if running
+ gschem from the command line and generating output.
+
+ schematic1 [... schematicN]
+ Schematic file to be loaded. Specifing a schematic file is
+ optional. If multiple schematic files are specified they are
+ read in sequentially and put on seperate pages. It is impor-
+ tant that the schematic(s) follow all the options (ie last).
+
+
+EXAMPLES
+ These examples assume that you have a schematic called stack_1.sch in
+ the current directory
+
+ To run gschem and then interact with the program:
+
+ ./gschem
+
+ To run gschem in interactive mode but load a sample schematic:
+
+ ./gschem adders_1.sch
+
+ To run gschem and load up all schematics in the current subdirectory:
+
+ ./gschem *.sch
+
+
+ENVIRONMENT
+ No environment variables are used.
+
+
+AUTHOR
+ Ales Hvezda and many others
+
+
+SEE ALSO
+ gnetlist(1), gsymcheck(1)
+
+COPYRIGHT
+ Copyright © 1999-2004 Ales Hvezda
+
+ This document can be freely redistributed according to the terms of the
+ GNU General Public License version 2.0
+
+
+
+
+Version December 31st, 2003 gschem(1)</font></pre>
+</p>
+
+</div>
+<!-- SECTION "On-line documentation" [34674-39143] -->
+<h1><a name="electrical_connectivity" id="electrical_connectivity">Electrical Connectivity</a></h1>
+<div class="level1">
+
+<p>
+As you draw schematics you need be aware of what is considered to be electrically connected by the gEDA programs.<br/>
+ Nets which are visually connected to other nets are electrically connected. This connection may be endpoint to endpoint or endpoint to midpoint. When a single endpoint to endpoint (net or pin endpoint) connection is drawn, the visual dangling net cue disappears. When an endpoint ends in the middle of another net (or multiple endpoints coming together at a single point) then a circular filled connectivity cue is drawn. You cannot connect a net to the middle of a pin. Nets can only be connected to the endpoints of pins. You cannot connect to a net if that net is not orthogonal (horizontal or vertical). The visual cues are the primary way of telling if nets/pins are connected.<br/>
+ Bus are similar to nets with the exception that you cannot connect a net to the endpoint of a bus (only to the middle). If you do try to connect a net to the end of a bus you will see a big red X at the invalid endpoint connection. Buses are still very new so there are still many quirks.<br/>
+ You can label nets by using the <code>label=</code> attribute. Do not attach more than one <code>label=</code> to a net. You only need to attach the <code>label=</code> attribute to one net segment. Different nets (i.e. multiple net segments which arenâ??t connected together) which have the same attribute <code>label=</code> attached to them are also considered electrically connected. You will not get any indication of this connection by <strong>gschem</strong>, but the netlister (<strong>gnetlist</strong>) considers nets with the same <code>label=</code> attribute electrically connected. The naming convention for buses has not been formalized yet.
+</p>
+
+</div>
+<!-- SECTION "Electrical Connectivity" [39144-40860] -->
+<h1><a name="components_symbols_objects_attributes" id="components_symbols_objects_attributes">Components & Symbols & Objects & Attributes</a></h1>
+<div class="level1">
+
+<p>
+There is a hierarchical association between components, symbols, objects, and attributes.
+</p>
+
+</div>
+<!-- SECTION "Components & Symbols & Objects & Attributes" [40861-41009] -->
+<h2><a name="components" id="components">Components</a></h2>
+<div class="level2">
+
+<p>
+A component is the instantiation of a specific symbol, as placed on the schematic. When discussing a schematic you refer to <em class="u">components</em> on the schematic, not <em class="u">symbols</em> on the schematic. Think of symbols as being <em class="u">conceptual</em>, and components as being <em class="u">concrete</em>.<br/>
+ The component consists of a graphic representation and the attributes describing the componentâ??s features.<br/>
+ The component inherits all of the attributes defined in the symbol. Certain attributes in the symbol:
+</p>
+<ul>
+<li class="level1"><div class="li"> those explicitly defined as visible unattached attributes (see <a href="#attributes" title=":geda:gschem_ug.txt ↵" class="wikilink1">Attributes</a>)</div>
+</li>
+<li class="level1"><div class="li"> specific attributes such as <code>symversion</code> and <code>refdes</code></div>
+</li>
+</ul>
+
+<p>
+ are promoted to the component level for manipulation by the circuit designer. These attributes may optionally be exposed (made viewable) with the componentâ??s graphic, and their values may be changed.<br/>
+ Any attribute not defined in the symbol may be defined in the component. For example, if the symbol does not define the <code>comment</code> attribute, this attribute may be added to the component, perhaps to add a comment for the Bill of Material or Assembly Instructions.<br/>
+ Unfortunately, it is difficult to determine a componentâ??s attributes from <strong>gschem</strong> while entering the schematic. You have to place a symbol on the schematic, select the resulting component, and select <strong>Hierarchy | Down Symbol</strong> from the pull-down menus. Then, you have to unhide all attributes with <strong>Edit | Make Inv Text Vis</strong> from the pull-down menus. Then you have to expand your view of the symbol with <strong>View | Extents</strong>. Then, you have to go back to the schematic by selecting <strong>Hierarchy | Up</strong> from the pull-down menus. Then, you have to select <strong>Edit | Edit…</strong> to bring up the â??Edit Attributesâ?? dialog box to determine if any attributes have been added at the component level.
+</p>
+
+</div>
+<!-- SECTION "Components" [41010-42824] -->
+<h2><a name="symbols" id="symbols">Symbols</a></h2>
+<div class="level2">
+
+<p>
+Symbols are just a collection of objects and attributes.<br/>
+ The objects have positional significance in the symbol, and define the graphic that is viewed.<br/>
+ Attributes may be attached to objects, or they may be attached to the symbol itself (termed as â??unattachedâ?? attributes, because they are not attached to an object).
+</p>
+
+</div>
+<!-- SECTION "Symbols" [42825-43166] -->
+<h2><a name="objects" id="objects">Objects</a></h2>
+<div class="level2">
+
+<p>
+The following are objects:
+</p>
+<ul>
+<li class="level1"><div class="li"> Line</div>
+</li>
+<li class="level1"><div class="li"> Box</div>
+</li>
+<li class="level1"><div class="li"> Circle</div>
+</li>
+<li class="level1"><div class="li"> Arc</div>
+</li>
+<li class="level1"><div class="li"> Pin</div>
+</li>
+<li class="level1"><div class="li"> Picture</div>
+</li>
+<li class="level1"><div class="li"> Text</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Objects" [43167-43280] -->
+<h2><a name="attributes" id="attributes">Attributes</a></h2>
+<div class="level2">
+
+<p>
+An attribute is text which is in the form <code>name=value</code> (there are no spaces to the left or right of the name,value pair). An attribute can be either attached to an object or unattached. Attributes are used extensively in the gEDA project to convey information (e.g., device name, pin numbers, hidden nets, and unit reference numbers). Check <a href="geda-master_attributes_list.html" class="wikilink1" title="geda-master_attributes_list.html">gEDA/gaf Master Attribute Document</a> for a complete list of attributes.<br/>
+ There are three kinds of attributes:
+</p>
+<ul>
+<li class="level1"><div class="li"> <strong>Attached attributes:</strong> These are attributes which take on the standard form and are attached to some object (pin, net, component, or box etc…) to associate a value with the attribute. For example: a pin number associated with a pin. <span class="hilited">These attributes are usually yellow in color.</span></div>
+</li>
+<li class="level1"><div class="li"> <strong>Unattached attributes:</strong> These are attributes which take on the standard form, but are not attached to any object and usually convey some information which is global in nature. For example: a <code>device=</code> attribute (which lives inside symbols) and specifies what device the entire symbol represents. These attributes are also known as floating or toplevel attributes.</div>
+</li>
+<li class="level1"><div class="li"> <strong>Promoted attributes:</strong> These are unattached attributes in the symbolâ??s definition that get turned into attached attributes in the componentâ??s definition when the symbol is instantiated as a component when placed in the schematic. If you place an unattached visible attribute inside a symbol and then instantiate that symbol, then that unattached attribute gets â??promotedâ??; that is, it becomes an attached attribute. This mechanism of attribute reattachement (from within a symbol) is known as attribute promotion.</div>
+</li>
+</ul>
+
+<p>
+ There are some gotchas about attribute promotion:
+</p>
+<ul>
+<li class="level1"><div class="li"> Promotion <strong>only</strong> happens when the symbol is first placed. That means that if you place a symbol (e.g., sym1) and then change it on disk (by adding or removing new unattached attributes), existing sym1â??s will not reflect these new unattached attributes (i.e., they wonâ??t get promoted) in any schematic.</div>
+</li>
+<li class="level1"><div class="li"> The <code>device=</code> attribute is not promoted.</div>
+</li>
+<li class="level1"><div class="li"> Invisible attributes are not promoted by default. If you add an unattached attribute (e.g., numslots=#) and make it invisible, it will not be promoted.</div>
+</li>
+</ul>
+
+<p>
+ Now, in order to make everybody happy, this attribute promotion behavior is configurable.<br/>
+ The system-gschemrc file defines:
+</p>
+<pre class="code lisp"><span class="br0">(</span>attribute-promotion <span class="st0">"enabled"</span><span class="br0">)</span></pre>
+<p>
+which enables attribute promotion.<br/>
+ If you override the system-gschemrcâ??s default promote-invisible setting by adding:
+</p>
+<pre class="code lisp"><span class="br0">(</span>promote-invisible <span class="st0">"enabled"</span><span class="br0">)</span></pre>
+<p>
+to either your userâ??s ~/gschemrc or local â??pwdâ??/gschemrc file, invisible unattached attributes will also be promoted <span class="hilited">(and in memory removed)</span>.
+</p>
+
+<p>
+However, if you do this, component slotting will break because <strong>gschem</strong> expects certain unattached attributes inside the symbol <span class="hilited">(in memory even though they are invisible)</span>.<br/>
+ So you can add:
+</p>
+<pre class="code lisp"><span class="br0">(</span>keep-invisible <span class="st0">"enabled"</span><span class="br0">)</span></pre>
+<p>
+to either your userâ??s ~/gschemrc or local â??pwdâ??/gschemrc file. This is enabled by default, but has no effect unless promote-invisible is enabled.
+</p>
+
+<p>
+So, to summarize, attribute promotion takes unattached attributes inside symbols and attaches them to the outside of a placed symbol. Three *rc keywords control this behavior: attribute-promotion, promote-invisible, and keep-invisible.
+</p>
+
+</div>
+<!-- SECTION "Attributes" [43281-46653] -->
+<h1><a name="the_main_window" id="the_main_window">The Main Window</a></h1>
+<div class="level1">
+<table class="inline">
+ <tr>
+ <td> <a href="media/geda/gschem_screenshot_001.jpg" class="media" target="_blank" title="geda:gschem_screenshot_001.jpg"><img src="media/geda/gschem_screenshot_001.jpg" class="media" alt="" /></a> </td>
+ </tr>
+</table>
+
+<p>
+ There are several ways to interact with <strong>gschem</strong>. <strong>gschem</strong> requires a keyboard and mouse. There are three ways to initiate an operation or command:
+</p>
+<ul>
+<li class="level1"><div class="li"> Using the mouse to select the operation off a menu</div>
+</li>
+<li class="level1"><div class="li"> Typing the keyboard shortcut(s).</div>
+</li>
+<li class="level1"><div class="li"> Draw the appropriate stroke (if stroke support is enabled)</div>
+</li>
+</ul>
+
+<p>
+ To make usage matters more confusing, selecting an operation off of the menus behaves slightly differently than typing the keyboard shortcut. Most of the operations operate on the currently selected object(s), hence you need to select the object first before manipulating them. The menu selected operations usually require some more input (usually a mouse click) after they are picked off of the menu. The keyboard shortcut operations take that required input as the current mouse position. This saves an extra click since you can position the mouse at the right place, type in the shortcut(s), and the command then executes. Note, you can change this so that both menu and shortcut behavior is exactly the same. See the section on the resource file for more info on how to configure this.<br/>
+ Most of the interaction with <strong>gschem</strong> is fairly mode oriented (similar to the great text editor vi). If you select operations off of the menu, then you are placed into the corresponding mode (like copy or move mode). You must then select an anchor point (or whatever the appropriate point is) to continue the operation. Most of the commands off of the menu expect the objects to be already selected. Some of the modes persist after being execute while other immediately return you into select mode (the default mode).<br/>
+ The shortcuts are also mode like in nature. Most of the default shortcuts are for the various commands are not single keystrokes. There are a few which are single keystrokes (like zoom in: `zâ?? or pan: `xâ??), but most are typically two keystrokes long. As examples, to execute File/Save you would type `fâ?? and `sâ?? (without the quotes) or Add/Line is `aâ?? and `lâ??. You can get a listing of the shortcuts by picking Help/Hotkeys. You can also see the hotkey assignments in the pulldown menus as well. The shortcuts are defined in the resource files (<strong>system-gschemrc</strong>, <strong>/.gEDA/gschemrc</strong>, or <strong>`pwd`/gschemrc</strong>). See the section on the resource file for more info.<br/>
+ The mouse button actions in <strong>gschem</strong> are mostly configurable. The first mouse button is always used to select objects or pick points. This button is not configurable. The second mouse button is either a copy/move action (when held down over an object), a repeat last command or used to draw a stroke to execute a command. The third mouse button is either a mouse pan (when held down as the mouse is moved) or a popup menu. The behavior of the second and third mouse buttons is controlled through the resource file (see the section below for more info).
+</p>
+
+</div>
+<!-- SECTION "The Main Window" [46654-49567] -->
+<h1><a name="the_status_window" id="the_status_window">The Status Window</a></h1>
+<div class="level1">
+<table class="inline">
+ <tr>
+ <td> <a href="media/geda/status_screenshot.jpg" class="media" target="_blank" title="geda:status_screenshot.jpg"><img src="media/geda/status_screenshot.jpg" class="media" title=":geda:status_screenshot.jpg" alt=":geda:status_screenshot.jpg" /></a> </td>
+ </tr>
+</table>
+
+<p>
+ Add some details about what gets displayed in the status window.
+</p>
+
+</div>
+<!-- SECTION "The Status Window" [49568-49730] -->
+<h1><a name="the_schematic_file" id="the_schematic_file">The Schematic File</a></h1>
+<div class="level1">
+
+<p>
+Schematic files. These files contain components, nets, text, and sometimes primitive objects (like lines, circles, box etc…) Schematics do not contain pins. Schematic filenames should follow this convention: name_#.sch where:
+</p>
+<ul>
+<li class="level1"><div class="li"> name is a text string which describes what this schematic contains.</div>
+</li>
+<li class="level1"><div class="li"> _# is an underscore and a number (like _1, _2, _7, _13, etc…) This number is used to sequence schematic pages in a multiple page schematic.</div>
+</li>
+<li class="level1"><div class="li"> .sch is the schematic extension/suffix. It is important the schematic pages have this extension.</div>
+</li>
+</ul>
+
+<p>
+ Schematic files are pure <acronym title="American Standard Code for Information Interchange">ASCII</acronym> and will always be pure <acronym title="American Standard Code for Information Interchange">ASCII</acronym>. gEDA does not support any binary file formats. The file format for schematics is described in the gEDA file formats document.
+</p>
+
+</div>
+<!-- SECTION "The Schematic File" [49731-50500] -->
+<h1><a name="the_symbol_file" id="the_symbol_file">The Symbol File</a></h1>
+<div class="level1">
+
+<p>
+Symbol files. The schematic and symbol file formats are identical. <strong>gschem</strong> (or a text editor) is used to create symbol files as well as schematics. Symbol files contain lines, circles, boxes, arcs, pins, text, and attributes.<br/>
+ The naming convention for symbol files is: name-#.sym where:
+</p>
+<ul>
+<li class="level1"><div class="li"> name is a text string which describes what the symbol represents.</div>
+</li>
+<li class="level1"><div class="li"> -# is a dash and a number (like -1, -2 etc…) The number is used to allow for a symbols to have the same name yet different contents. There might be multiple representations for resistors so these symbols should be called: resistor-1.sym, resistor-2.sym, and resistor-3.sym.</div>
+</li>
+<li class="level1"><div class="li"> .sym is the symbol extension/suffix. It is important the symbols have this extension.</div>
+</li>
+</ul>
+
+<p>
+ The way of specifying hierarchy is by using the source= attribute. Please see the master attribute document for info on this mechanism.<br/>
+ The hierarchy mechanism is still in heavy flux, so there might be some more changes.
+</p>
+
+</div>
+<!-- SECTION "The Symbol File" [50501-51487] -->
+<h1><a name="symbol_libraries" id="symbol_libraries">Symbol Libraries</a></h1>
+<div class="level1">
+
+<p>
+Components are searched for by specifying (component-library "…â??) inside one of the *rc files. See below for more info.
+</p>
+
+</div>
+<!-- SECTION "Symbol Libraries" [51488-51641] -->
+<h1><a name="the_log_file" id="the_log_file">The Log File</a></h1>
+<div class="level1">
+
+<p>
+Log file. This file contains informative, error, warnings etc… messages when <strong>gschem</strong> was run. This file is created in the working directory that <strong>gschem</strong> was started in. This allows the user to preserve log files between independent projects.
+</p>
+
+</div>
+<!-- SECTION "The Log File" [51642-51919] -->
+<h1><a name="grips" id="grips">Grips</a></h1>
+<div class="level1">
+
+<p>
+Grips are a mechanism used in <strong>gschem</strong> to provide an easy way of modifying objects inside schematics. When you select an object, little squares are placed in strategic locations (line end points or circle radius point or corners of a box) which allow you to change the object quickly. Grip support currently exists for lines, nets, pins, buses, circles, and boxes. Arcs do not yet have grips, but will eventually have them.
+</p>
+
+<p>
+Using grips is easy:
+</p>
+<ul>
+<li class="level1"><div class="li"> Select the object you want to change. The grips (the little boxes) will appear.</div>
+</li>
+<li class="level1"><div class="li"> Click and hold the first mouse button inside the box.</div>
+</li>
+<li class="level1"><div class="li"> Move the mouse around till you have the object where you want it</div>
+</li>
+<li class="level1"><div class="li"> Release the mouse button.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Grips" [51920-52629] -->
+<h1><a name="menu_operations" id="menu_operations">Menu Operations</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "Menu Operations" [52630-52659] -->
+<h2><a name="file" id="file">File</a></h2>
+<div class="level2">
+
+<p>
+The <strong>gschem</strong> application is primarily used for the creation of schematic files (i.e., filename.sch) and symbol files (filename.sym).<br/>
+ The following operations are related to the manipulation of these files.<br/>
+ Note that <strong>gschem</strong> automatically maintains backups of open schematic/symbol files, in the /tmp directory, for the purpose of Undo/Redo. <strong>gschem</strong> cleans up these files when it exits gracefully. If <strong>gschem</strong> does not exit gracefully, the next time you launch <strong>gschem</strong> you will be prompted with a dialog similar to: <pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">WARNING: Found an autosave backup file:
+ {filename}
+
+ The backup copy is newer than the schematic, so it seems you
+ load it instead of the original file.
+ gschem usually makes backup copies automatically, and this
+ situation happens when it crashed or it was forced to exit
+ abruptly.
+
+ If you load the original file, the backup file will be overwritten in
+ the next autosave timeout and it will be lost.
+
+ Do you want to load the backup file?</font></pre>
+</p>
+
+<p>
+The following are available from the <strong>gschem</strong> main windowâ??s menu-bar when you expand <strong>File</strong>:
+</p>
+
+</div>
+<!-- SECTION "File" [52660-53813] -->
+<h3><a name="new_window_fw" id="new_window_fw">New Window (fw)</a></h3>
+<div class="level3">
+
+<p>
+<strong>File | New Window</strong> opens a new window, in addition to any already open windows. Each window is totally separate from the other windows.
+</p>
+
+</div>
+<!-- SECTION "New Window (fw)" [53814-53979] -->
+<h3><a name="new_page_fn" id="new_page_fn">New Page (fn)</a></h3>
+<div class="level3">
+
+<p>
+<strong>File | New Page</strong> opens a new page, in addition to any existing open pages. Usually this page will be named â??untitled_N.schâ??, where N is an incrementing number.
+</p>
+
+</div>
+<!-- SECTION "New Page (fn)" [53980-54167] -->
+<h3><a name="open_page..._fo" id="open_page..._fo">Open Page... (fo)</a></h3>
+<div class="level3">
+
+<p>
+<strong>File | Open Page…</strong> opens an existing page from disk.<br/>
+ The â??Open…â?? dialog box pops up providing:
+</p>
+<ul>
+<li class="level1"><div class="li"> Directory navigation aids</div>
+</li>
+<li class="level1"><div class="li"> Filters for restricting the displayed files:</div>
+<ul>
+<li class="level2"><div class="li"> Schematics</div>
+</li>
+<li class="level2"><div class="li"> Symbols</div>
+</li>
+<li class="level2"><div class="li"> Schematics and Symbols</div>
+</li>
+<li class="level2"><div class="li"> All files</div>
+</li>
+</ul>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Open Page... (fo)" [54168-54455] -->
+<h3><a name="close_page_pc" id="close_page_pc">Close Page (pc)</a></h3>
+<div class="level3">
+
+<p>
+<strong>File | Close Page</strong> closes the currently displayed page. This will prompt you to save if you have modified the page.
+</p>
+
+</div>
+<!-- SECTION "Close Page (pc)" [54456-54601] -->
+<h3><a name="revert_page_pr" id="revert_page_pr">Revert Page (pr)</a></h3>
+<div class="level3">
+
+<p>
+<strong>File | Revert Page</strong> closes and reopens the currently displayed page. This will not prompt you to save the current page, but will quickly discard any changes you have made and reopen the saved schematic from disk. Use with caution.
+</p>
+
+</div>
+<!-- SECTION "Revert Page (pr)" [54602-54863] -->
+<h3><a name="save_page_fs" id="save_page_fs">Save Page (fs)</a></h3>
+<div class="level3">
+
+<p>
+<strong>File | Save Page</strong> saves the current page. The current filename is displayed in the <strong>gschem</strong> status-bar.<br/>
+ If the pageâ??s filename is â??untitled_N.schâ?? (where N is a integer), then the Save As… dialog box will be displayed, prompting for a new filename.<br/>
+ If the pageâ??s filename is NOT â??untitled_N.schâ?? (where N is a integer), then the Save As… dialog box will NOT be displayed, and:
+</p>
+<ul>
+<li class="level1"><div class="li"> the backup file will be created for the previous version, named {filename}~ That is, the "~" (tilde character) is appended to the filename. Any previous backup file is lost.</div>
+</li>
+<li class="level1"><div class="li"> the file will be saved to the current filename.<br/>
+</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Save Page (fs)" [54864-55511] -->
+<h3><a name="save_page_as..._fa" id="save_page_as..._fa">Save Page As... (fa)</a></h3>
+<div class="level3">
+
+<p>
+<strong>File | Save Page As…</strong> opens the Save As.. dialog box.<br/>
+ If the current filename is â??untitled_N.schâ??, the Save As… dialog box prompts for a new filename.<br/>
+ If the current filename is NOT â??untitled_N.schâ??, the Save As… dialog box prompts for a new filename, filling in the current filename as a default.<br/>
+ In either case the filename may be changed, and a new file created when the Save As button is clicked.
+</p>
+
+</div>
+<!-- SECTION "Save Page As... (fa)" [55512-55959] -->
+<h3><a name="save_all_fl_fl" id="save_all_fl_fl">Save All (fl) (fl)</a></h3>
+<div class="level3">
+
+<p>
+<strong>File | Save All</strong> unconditionally saves all schematics loaded in memory.
+</p>
+
+</div>
+<!-- SECTION "Save All (fl) (fl)" [55960-56064] -->
+<h3><a name="print..._fp" id="print..._fp">Print... (fp)</a></h3>
+<div class="level3">
+
+<p>
+<strong>File | Print…</strong> brings up the Print… dialog box.<br/>
+ The following may be selected:
+</p>
+<ul>
+<li class="level1"><div class="li"> Filename (if <strong>gschem</strong> has multiple pages loaded, this filename defaults to the page currently displayed).</div>
+</li>
+<li class="level1"><div class="li"> Paper size (that is loaded into your printer).</div>
+</li>
+<li class="level1"><div class="li"> The print type:</div>
+<ul>
+<li class="level2"><div class="li"> Extents with margins – the current page, with margins where the printer doesnâ??t output.</div>
+</li>
+<li class="level2"><div class="li"> Extents no margins – the current page, but without margins where the printer doesnâ??t output. The printer output may be scaled larger than when using â??Entents with marginsâ??, but at the loss along the borders of the schematic.</div>
+</li>
+<li class="level2"><div class="li"> Current window – Scaled to fit the page size, but not optimally.</div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> Orientation:</div>
+<ul>
+<li class="level2"><div class="li"> Landscape</div>
+</li>
+<li class="level2"><div class="li"> Portrait</div>
+</li>
+</ul>
+</li>
+</ul>
+
+<p>
+ Pressing Print will generate a PostScript file with the filname format of the form {filename}.ps (e.g., printing schematic file First_1.sch would generate First_1.ps).<br/>
+ Printing the PostScript file to your printer is distribution dependent:</p>
+<dl>
+<dt><span class='term'> Fedora Core (from the command-line):</span></dt>
+<dd><code>lp First_1.ps</code></dd>
+</dl>
+
+
+</div>
+<!-- SECTION "Print... (fp)" [56065-57111] -->
+<h3><a name="write_png..._fi" id="write_png..._fi">Write PNG... (fi)</a></h3>
+<div class="level3">
+
+<p>
+<strong>File | Write <acronym title="Portable Network Graphics">PNG</acronym>…</strong> brings up the Write <acronym title="Portable Network Graphics">PNG</acronym>… dialog box. Note you must have libgdgeda installed (and any required dependencies) if you want to output images.<br/>
+ The dialog box allows you to select:
+</p>
+<ul>
+<li class="level1"><div class="li"> Width x Height:</div>
+<ul>
+<li class="level2"><div class="li"> 320 x 240</div>
+</li>
+<li class="level2"><div class="li"> 640 x 480</div>
+</li>
+<li class="level2"><div class="li"> 800 x 600</div>
+</li>
+<li class="level2"><div class="li"> 1024 x 768</div>
+</li>
+<li class="level2"><div class="li"> 1280 x 960</div>
+</li>
+<li class="level2"><div class="li"> 1600 x 1200</div>
+</li>
+<li class="level2"><div class="li"> 3200 x 2400</div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> Filename (if <strong>gschem</strong> has multiple pages loaded, the currently displayed pageâ??s filname is given)</div>
+</li>
+</ul>
+
+<p>
+ When the OK button is clicked, a <acronym title="Portable Network Graphics">PNG</acronym> graphic file with a filename of the form {filename}.png is created (e.g., writing a <acronym title="Portable Network Graphics">PNG</acronym> for schematic file First_1.sch will generate a First_1.png file).<br/>
+ This file may be used any way a <acronym title="Portable Network Graphics">PNG</acronym> file is used (e.g., web-page, document insertion, image manipulation with the GIMP, etc.).
+</p>
+
+</div>
+<!-- SECTION "Write PNG... (fi)" [57112-57906] -->
+<h3><a name="execute_script..._ft" id="execute_script..._ft">Execute Script... (ft)</a></h3>
+<div class="level3">
+
+<p>
+<strong>File | Execute Script…</strong> …..TBD
+</p>
+
+</div>
+<!-- SECTION "Execute Script... (ft)" [57907-57978] -->
+<h3><a name="close_window_fc" id="close_window_fc">Close Window (fc)</a></h3>
+<div class="level3">
+
+<p>
+<strong>File | Close Window</strong> closes the current window. If there are any modified schematics, the â??There are unsaved schematicsâ?? dialog box will appear. Clicking OK will cause all unsaved schematics to be lost.
+</p>
+
+</div>
+<!-- SECTION "Close Window (fc)" [57979-58217] -->
+<h3><a name="quit_alt-q" id="quit_alt-q">Quit (Alt-q)</a></h3>
+<div class="level3">
+
+<p>
+<strong>File | Quit</strong> closes all opened windows and exits <strong>gschem</strong>. A â??There are unsaved schematicsâ?? dialog box will appear for each window that has unsaved schematics.
+</p>
+
+</div>
+<!-- SECTION "Quit (Alt-q)" [58218-58410] -->
+<h2><a name="edit" id="edit">Edit</a></h2>
+<div class="level2">
+
+<p>
+The following are available from the <strong>gschem</strong> main windowâ??s menu-bar when you expand <strong>Edit</strong>:
+</p>
+
+</div>
+<!-- SECTION "Edit" [58411-58527] -->
+<h3><a name="undo_shift-u" id="undo_shift-u">Undo (shift-u)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Edit | Undo</strong> does exactly that, it undos the last action which changed the schematic.<br/>
+ The depth of undo (how many undo steps can be performed) is set in the system-gschemrc file. The default is 10. Simply override this setting by placing the following lines in either your ~/.gEDA/gschemrc file or your local gschemrc file: <pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">; undo-levels number
+;
+; Determines the number of levels of undo. Basically this number decides
+; how many backup schematics are saved on disk.
+;
+(undo-levels 10)</font></pre>
+</p>
+
+<p>
+After every action (including zooming and panning) the schematic is saved to disk (in /tmp). The undo-levels setting determines how many of these temporary files are maintained in the /tmp directory. <strong>gschem</strong> does clean-up after itself when you exit.<br/>
+ Should <strong>gschem</strong> crash, the saved files remain in /tmp for disaster recovery. You will be prompted the next time the schematic is opened to recover from the backup.<br/>
+
+</p>
+
+</div>
+<!-- SECTION "Undo (shift-u)" [58528-59486] -->
+<h3><a name="redo_shift-r" id="redo_shift-r">Redo (shift-r)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Edit | Redo</strong> only applies after you have done an <strong>Edit | Undo</strong>. You can undo something and then immediately redo it. However if you do anything in between you will lose the undo info. You can undo and redo to your hearts desire up and down till you reach the max undo levels.<br/>
+
+</p>
+
+</div>
+<!-- SECTION "Redo (shift-r)" [59487-59795] -->
+<h3><a name="select_mode_s" id="select_mode_s">Select Mode (s)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Edit | Select Mode</strong> is the initial mode in which <strong>gschem</strong> starts.<br/>
+ When in <strong>Select Mode</strong>, an unlocked object (i.e., component, line, box, circle, …) may be selected by placing the mouse pointer within the outline of the object and single-clicking, or by dragging a box (i.e., holding down the first mouse-button) around the object. Selecting an already selected object will leave the object selected (i.e., you can not unselect an object by single-clicking it). Multiple unlocked objects may be selected by dragging a box around the objects.<br/>
+ A locked object may be selected by dragging a box around the object.<br/>
+ To de-select all objects, single-click anywhere on the schematic where there is no object.<br/>
+ A visible attribute for an unlocked component may be selected by placing the mouse pointer over the componentâ??s visible attribute and single-clicking. Placing the mouse pointer over the unlocked componentâ??s visible attribute and double-clicking will open the edit dialog box appropriate for the attribute.<br/>
+ Objects will change color when selected.<br/>
+ You stay in <strong>Select Mode</strong> until you select one of the other Modes (e.g., Line, Copy, Move, etc.).<br/>
+ Your current Mode is displayed on the status-bar, in the lower-right corner of the <strong>gschem</strong> window.<br/>
+ If multiple objects overlap, single-clicking where they overlap will cycle through the objects.<br/>
+ If you hold down the SHIFT key and single-click, you can select and deselect multiple objects. Doing this with multiple overlapping objects will cause the selection to cycle among the possible object selections.<br/>
+ If you hold down the CONTROL key and single-click, you will toggle the object in and out of the current selection list.<br/>
+ If you hold down the SHIFT key while drawing a selection box you will add to the currently selected objects. Objects cannot be removed using the selection box and holding down the SHIFT key.<br/>
+ If you hold down the CONTROL key while drawing a selection box then you will toggle any encompassed objects. If an object was selected then it will be unselected and vice versa.<br/>
+ If you pick a component, its visible and invisible attributes are selected as well. If you just want to select the object, you must deselect the attributes.<br/>
+ The selection mechanisms are not obvious and do require some practice. There are some quirks so please report them as you come across them.
+</p>
+
+</div>
+<!-- SECTION "Select Mode (s)" [59796-62203] -->
+<h3><a name="edit..._ee" id="edit..._ee">Edit... (ee)</a></h3>
+<div class="level3">
+
+<p>
+First, select the object to be edited (i.e., in <strong>Select Mode</strong>).<br/>
+ If the object is a component, <strong>Edit | Edit…</strong> then pops up a dialog box that allows you to edit the componentâ??s attributes:
+</p>
+<ul>
+<li class="level1"><div class="li"> Existing attributes (e.g., refdes) are displayed.</div>
+</li>
+<li class="level1"><div class="li"> A drop-down list of pre-defined attributes permits selection, and a edit-box provides association of a value to the attribute.</div>
+</li>
+<li class="level1"><div class="li"> The attributeâ?? name and/or value may be made visible or invisible,</div>
+</li>
+</ul>
+
+<p>
+ If the ojbect is a text string, <strong>Edit…</strong> then pops up a dialog box that allows you to modify the text stringâ??s attributes:
+</p>
+<ul>
+<li class="level1"><div class="li"> The text string may be modified. Multiple lines of text may be entered by inserting carriage-returns.</div>
+</li>
+<li class="level1"><div class="li"> The text color may be modified.</div>
+</li>
+<li class="level1"><div class="li"> The text size may be modified.</div>
+</li>
+<li class="level1"><div class="li"> The text alignment:</div>
+<ul>
+<li class="level2"><div class="li"> Lower/middle/upper left</div>
+</li>
+<li class="level2"><div class="li"> Lower/middle/upper middle</div>
+</li>
+<li class="level2"><div class="li"> Lower/middle/upper right</div>
+</li>
+</ul>
+</li>
+</ul>
+
+<p>
+ Apply the changes by pressing OK.
+</p>
+
+<p>
+<strong>Notes:</strong><br/>
+ If you need to change the attributes to more than just a few components, consider saving your schematics, closing <strong>gschem</strong>, and using the <strong>gattrib</strong> application, the <strong>grenum</strong> application, or the <strong>refdes_renum</strong> application to make the changes.
+</p>
+
+</div>
+<!-- SECTION "Edit... (ee)" [62204-63398] -->
+<h3><a name="edit_text..._ex" id="edit_text..._ex">Edit Text... (ex)</a></h3>
+<div class="level3">
+
+<p>
+First, select the text object to be edited (i.e., in <strong>Select Mode</strong>).<br/>
+ <strong>Edit | Edit Text…</strong> allows you to edit just text.<br/>
+ <strong>Edit | Edit Text…</strong> then pops up a dialog box that allows you to modify the text stringâ??s attributes:
+</p>
+<ul>
+<li class="level1"><div class="li"> The text string may be modified. Multiple lines of text may be entered by inserting carriage-returns.</div>
+</li>
+<li class="level1"><div class="li"> The text color may be modified.</div>
+</li>
+<li class="level1"><div class="li"> The text size may be modified.</div>
+</li>
+<li class="level1"><div class="li"> The text alignment:</div>
+<ul>
+<li class="level2"><div class="li"> Lower/middle/upper left</div>
+</li>
+<li class="level2"><div class="li"> Lower/middle/upper middle</div>
+</li>
+<li class="level2"><div class="li"> Lower/middle/upper right</div>
+</li>
+</ul>
+</li>
+</ul>
+
+<p>
+ Apply the changes by pressing OK.
+</p>
+
+<p>
+<strong>Notes:</strong><br/>
+ If you need to change the attributes to more than just a few text strings, consider saving your schematics, closing <strong>gschem</strong>, and using the <strong>gattrib</strong> application, the <strong>grenum</strong> application, or the <strong>refdes_renum</strong> application to make the changes.
+</p>
+
+</div>
+<!-- SECTION "Edit Text... (ex)" [63399-64257] -->
+<h3><a name="copy_mode_ec" id="copy_mode_ec">Copy Mode (ec)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Edit | Copy Mode</strong> allows you to copy (i.e., duplicate) the currently selected objects.<br/>
+ To copy the object(s):
+</p>
+<ul>
+<li class="level1"><div class="li"> Select the objects to be copied (i.e., in <strong>Select Mode</strong>)</div>
+</li>
+<li class="level1"><div class="li"> Select <strong>Edit | Copy Mode</strong></div>
+</li>
+<li class="level1"><div class="li"> Observe the status-bar now indicates <strong>Copy Mode</strong></div>
+</li>
+<li class="level1"><div class="li"> Click on the selected component(s) to establish an origin of reference</div>
+</li>
+<li class="level1"><div class="li"> Observe a shadow/outline appears for the selected components that moves with the mouse</div>
+</li>
+<li class="level1"><div class="li"> Place the components where you want them</div>
+</li>
+<li class="level1"><div class="li"> Click to anchor the copied components in place.</div>
+</li>
+</ul>
+
+<p>
+ After finishing the copy, you automatically return to <strong>Select Mode</strong>.<br/>
+ Holding down the CONTROL key as you move the outline around will constrain the movement to be either horizontal or vertical.<br/>
+ To copy objects using the shortcut keys is almost the same as above except that the origin point is selected automatically for you once you hit the copy mode shortcut.<br/>
+
+</p>
+
+</div>
+<!-- SECTION "Copy Mode (ec)" [64258-65182] -->
+<h3><a name="move_mode_em" id="move_mode_em">Move Mode (em)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Edit | Move Mode</strong> allows you to move the currently selected objects.<br/>
+ To move the object(s):
+</p>
+<ul>
+<li class="level1"><div class="li"> Select the objects to be moved (i.e., in <strong>Select Mode</strong>)</div>
+</li>
+<li class="level1"><div class="li"> Select <strong>Edit | Move Mode</strong></div>
+</li>
+<li class="level1"><div class="li"> Observe the status-bar now indicates <strong>Move Mode</strong></div>
+</li>
+<li class="level1"><div class="li"> Click on the selected component(s) to establish an origin of reference</div>
+</li>
+<li class="level1"><div class="li"> Observe a shadow/outline appears for the selected components that moves with the mouse</div>
+</li>
+<li class="level1"><div class="li"> Place the components where you want them</div>
+</li>
+<li class="level1"><div class="li"> Click to anchor the moved components in place.</div>
+</li>
+</ul>
+
+<p>
+ After finishing the move, you automatically return to <strong>Select Mode</strong>.<br/>
+ Holding down the CONTROL key as you move the outline around will constrain the movement to be either horizontal or vertical.<br/>
+ To move objects using the shortcut keys is almost the same as above except that the origin point is selected automatically for you once you hit the copy mode shortcut.<br/>
+
+</p>
+
+<p>
+Since version 20060906, there is another way to move object(s):<br/>
+
+</p>
+<ul>
+<li class="level1"><div class="li"> Select the objects to be moved (i.e., in <strong>Select Mode</strong>).<br/>
+</div>
+</li>
+<li class="level1"><div class="li"> Put the mouse pointer on one of the selected objects, then drag the objects and drop them where you want them.<br/>
+</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Move Mode (em)" [65183-66336] -->
+<h3><a name="delete_delete-key" id="delete_delete-key">Delete (Delete-key)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Edit | Delete</strong> allows you to remove objects off of the page.<br/>
+ To delete objects:
+</p>
+<ul>
+<li class="level1"><div class="li"> Select the desired object(s) (i.e., in <strong>Select Mode</strong>)</div>
+</li>
+<li class="level1"><div class="li"> Select <strong>Edit | Delete</strong></div>
+</li>
+</ul>
+
+<p>
+ The object(s) will be deleted immediately. If you inadvertantly delete a component, you can use Undo to recover.
+</p>
+
+</div>
+<!-- SECTION "Delete (Delete-key)" [66337-66655] -->
+<h3><a name="rotate_90_mode_er" id="rotate_90_mode_er">Rotate 90 Mode (er)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Edit | Rotate 90 Mode</strong> allows you to rotate objects 90 degrees around a pivot/center point.<br/>
+ To rotate objects:
+</p>
+<ul>
+<li class="level1"><div class="li"> Select the desired object(s) (i.e., in <strong>Select Mode</strong>)</div>
+</li>
+<li class="level1"><div class="li"> Select <strong>Edit | Rotate 90 Mode</strong></div>
+</li>
+<li class="level1"><div class="li"> Click on the pivot (or center) point of the rotate</div>
+</li>
+</ul>
+
+<p>
+ The object(s) will be rotated 90º counter-clockwise immediately. If you inadvertantly rotate a component, you can use Undo to recover.<br/>
+ Rotating objects using the shortcut keys is similar to above except that the center point is the last mouse position at which you typed the shortcut.<br/>
+
+</p>
+
+</div>
+<!-- SECTION "Rotate 90 Mode (er)" [66656-67245] -->
+<h3><a name="mirror_mode_ei" id="mirror_mode_ei">Mirror Mode (ei)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Edit | Mirror Mode</strong> allows you to mirror objects horizontally around a pivot point.<br/>
+ To mirror objects:
+</p>
+<ul>
+<li class="level1"><div class="li"> Select the desired object(s) (i.e., in <strong>Select Mode</strong>)</div>
+</li>
+<li class="level1"><div class="li"> Select <strong>Edit | Mirror Mode</strong></div>
+</li>
+<li class="level1"><div class="li"> Click on the pivot (or center) point of the mirror</div>
+</li>
+</ul>
+
+<p>
+ Mirroring objects using the shortcut keys is similar to above except that the pivot point is the last mouse position at which you typed the shortcut.<br/>
+ Objects are mirrored horizontally about the pivot point. If you want to get a vertical mirror then rotate and mirror the object(s) till you get the desired position.<br/>
+ Mirroring of embedded components is not supported.
+</p>
+
+</div>
+<!-- SECTION "Mirror Mode (ei)" [67246-67902] -->
+<h3><a name="slot..._e_shift-s" id="slot..._e_shift-s">Slot... (e shift-s)</a></h3>
+<div class="level3">
+
+<p>
+Some physical packages (e.g., the classic 7400 Quad NAND gate) contain more than one logical component (e.g., one of the NAND gates). In <strong>gchem</strong> terminology, each of these logical components is termed a â??slotâ?? (e.g., there would be 4 slots in the 7400 Quad NAND gate). Each slot is associated with specific pins on the physical package.<br/>
+ <strong>Edit | Slot…</strong> allows you to change the slot number of a multiple-slot package. The package must support slotting. Refer to the <a href="http://www.geda.seul.org/docs/current/symbols/index.html"; class="urlextern" title="http://www.geda.seul.org/docs/current/symbols/index.html"; rel="nofollow">gEDA/gaf Symbol Creation Document</a> for more details.<br/>
+ To change the slot number (i.e., select which package pins are associated with a logical component):
+</p>
+<ul>
+<li class="level1"><div class="li"> Select the desired logical component (i.e., in <strong>Select Mode</strong>)</div>
+</li>
+<li class="level1"><div class="li"> Select <strong>Edit | Slot…</strong></div>
+</li>
+<li class="level1"><div class="li"> Change the â??slot=nâ?? value in the â??Edit slot numberâ?? dialog box</div>
+</li>
+<li class="level1"><div class="li"> Press OK</div>
+</li>
+</ul>
+
+<p>
+ Note that selecting the slot on a package often effects the layout of the printed circuit board, as the slot may be on the wrong side of the package for effecient routing of nets. Donâ??t worry, you can always come back and change the slot selection once you start laying out your board and know which slots route best.
+</p>
+
+</div>
+<!-- SECTION "Slot... (e shift-s)" [67903-69119] -->
+<h3><a name="color..._eo" id="color..._eo">Color... (eo)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Edit | Color…</strong> allows you to change the color of any selected object (with the exception of components).<br/>
+ To change the color of the currently selected objects:
+</p>
+<ul>
+<li class="level1"><div class="li"> Select the desired object(s) (i.e., in <strong>Select Mode</strong>)</div>
+</li>
+<li class="level1"><div class="li"> Select <strong>Edit | Color…</strong></div>
+</li>
+<li class="level1"><div class="li"> The â??Edit | Color Editâ?? dialog box, with a drop down list for colors, will appear:</div>
+<ul>
+<li class="level2"><div class="li"> 1 | pin | black</div>
+</li>
+<li class="level2"><div class="li"> 2 | net endpoint | red</div>
+</li>
+<li class="level2"><div class="li"> 3 | graphic | green4</div>
+</li>
+<li class="level2"><div class="li"> 4 | net | blue2</div>
+</li>
+<li class="level2"><div class="li"> 5 | attribute | black</div>
+</li>
+<li class="level2"><div class="li"> 6 | logic bubble | DarkCyan</div>
+</li>
+<li class="level2"><div class="li"> 8 | detached attribute | red</div>
+</li>
+<li class="level2"><div class="li"> 9 | text | green4</div>
+</li>
+<li class="level2"><div class="li"> 10 | bus | green2</div>
+</li>
+<li class="level2"><div class="li"> 11 | select | firebrick</div>
+</li>
+<li class="level2"><div class="li"> 12 | bounding box | orange</div>
+</li>
+<li class="level2"><div class="li"> 13 | zoom box | DarkCyan</div>
+</li>
+<li class="level2"><div class="li"> 14 | stroke | grey90</div>
+</li>
+<li class="level2"><div class="li"> 15 | lock | grey40</div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> Pick the new color</div>
+</li>
+<li class="level1"><div class="li"> Press Apply</div>
+</li>
+</ul>
+
+<p>
+ The color change will take effect once you press Apply.<br/>
+ You can leave this dialog box up and select other objects and change their color by pressing Apply.
+</p>
+
+</div>
+<!-- SECTION "Color... (eo)" [69120-70078] -->
+<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">
+
+<p>
+<strong>Edit | Lock</strong> and <strong>Edit | Unlock</strong> allow you to lock/unlock components in a schematic. A locked component cannot be selected by a single click. To select locked component(s), drag a box around the component(s).<br/>
+ Locking a component is useful for components such as title blocks, which should not be selectable because there are other objects inside its boundaries. If the titleblock was not locked, and you missed selecting a component by clicking it with the mouse, you would end up selecting the titleblock instead.<br/>
+ Locking a component is also useful just to prevent it from being inadvertantly selected.<br/>
+ To lock/unlock components:
+</p>
+<ul>
+<li class="level1"><div class="li"> Select the desired object(s) (i.e., in <strong>Select Mode</strong>)</div>
+</li>
+<li class="level1"><div class="li"> Select <strong>Edit | Lock</strong> or <strong>Edit | Unlock</strong></div>
+</li>
+</ul>
+
+<p>
+ The locked/unlocked state of components is preserved when <strong>gschem</strong> exits, so components which were locked remain locked the next time the schematic is opened.<br/>
+ You can lock and unlock regular objects (e.g., lines, pins, boxes…). This is nice when you are drawing something and an object is in the way. Just lock it, and you will not have to think about it when you click to select other objects. Locking an object is not preserved in the file format, so once you quit <strong>gschem</strong> any locked objects will be unlocked the next time the schematic is opened.<br/>
+ Note that if a component is locked, you can not single-click to select a visible attribute, or double-click to select and edit a visible component. First unlock such locked components.
+</p>
+
+</div>
+<!-- SECTION "Lock (el) / Unlock (e shift-l)" [70079-71617] -->
+<h3><a name="line_width_type..._ew" id="line_width_type..._ew">Line Width & Type... (ew)</a></h3>
+<div class="level3">
+
+<p>
+The <strong>Edit | Line Width & Type…</strong> dialog box lets you control the width and type of lines, boxes, circles, and arcs on the schematic/symbol.<br/>
+ To change the <strong>Line Width & Type…</strong>:
+</p>
+<ul>
+<li class="level1"><div class="li"> Select the desired object(s) (i.e., in <strong>Select Mode</strong>)</div>
+</li>
+<li class="level1"><div class="li"> Select <strong>Edit | Line Width & Type…</strong></div>
+</li>
+<li class="level1"><div class="li"> The â??Edit Line Width * Typeâ?? dialog box displays</div>
+</li>
+<li class="level1"><div class="li"> Change the following as suites the object:</div>
+<ul>
+<li class="level2"><div class="li"> Line Width</div>
+</li>
+<li class="level2"><div class="li"> Line Type</div>
+</li>
+<li class="level2"><div class="li"> Line Dash Length</div>
+</li>
+<li class="level2"><div class="li"> Line Dash Space</div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> Press OK to apply the changes</div>
+</li>
+</ul>
+
+<p>
+ Note that if the line width doesnâ??t seem to change, just pick a larger value.
+</p>
+
+</div>
+<!-- SECTION "Line Width & Type... (ew)" [71618-72233] -->
+<h3><a name="fill_type..._ef" id="fill_type..._ef">Fill Type... (ef)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Edit | Fill Type…</strong> is used to fill boxes and circles.<br/>
+ To fill a box or circle:
+</p>
+<ul>
+<li class="level1"><div class="li"> Select the box or circle.</div>
+</li>
+<li class="level1"><div class="li"> Select <strong>Edit | Fill Type…</strong>. The â??Edit FIll Typeâ?? dialog box is displayed.</div>
+</li>
+<li class="level1"><div class="li"> Enter:</div>
+<ul>
+<li class="level2"><div class="li"> Fill Type</div>
+</li>
+<li class="level2"><div class="li"> Line Width</div>
+</li>
+<li class="level2"><div class="li"> Angle 1</div>
+</li>
+<li class="level2"><div class="li"> Pitch 1</div>
+</li>
+<li class="level2"><div class="li"> Angle 2</div>
+</li>
+<li class="level2"><div class="li"> Pitch 2</div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> Press OK.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Fill Type... (ef)" [72234-72574] -->
+<h3><a name="symbol_translate..._et" id="symbol_translate..._et">Symbol Translate... (et)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Edit | Symbol Translate…</strong> is used when creating a symbol, to translate the symbol to an origin for subsequent placement. The symbol may take an optional offset (in mils), as appropriate to the symbol.<br/>
+ To translate the symbol:
+</p>
+<ul>
+<li class="level1"><div class="li"> Open a file for the symbol</div>
+</li>
+<li class="level1"><div class="li"> Set the grid snap spacing to 100 mils (<strong>Options</strong> | <strong>Snap Grid Spacing…</strong>).</div>
+</li>
+<li class="level1"><div class="li"> Toggle the grid ON (<strong>Options</strong> | <strong>Toggle Grid On/Off</strong>)</div>
+</li>
+<li class="level1"><div class="li"> Toggle the grid snap ON (<strong>Options</strong> | <strong>Toggle Snap On/Off</strong>)</div>
+</li>
+<li class="level1"><div class="li"> Zoom as appropriate for the symbolâ??s dimensions</div>
+</li>
+<li class="level1"><div class="li"> Draw the symbol, according to the recommendations in the <a href="http://www.geda.seul.org/docs/current/symbols/index.html"; class="urlextern" title="http://www.geda.seul.org/docs/current/symbols/index.html"; rel="nofollow">gEDA/gaf Symbol Creation Document</a></div>
+</li>
+<li class="level1"><div class="li"> Select <strong>Edit | Symbol Translate…</strong></div>
+</li>
+<li class="level1"><div class="li"> The â??Translateâ?? dialog box is displayed.</div>
+</li>
+<li class="level1"><div class="li"> Enter 0 to translate to the origin, or enter a value (in mils), positive or negative, to offset the symbol from the origin.</div>
+</li>
+<li class="level1"><div class="li"> Press OK to apply</div>
+</li>
+<li class="level1"><div class="li"> Save the symbol to the file</div>
+</li>
+</ul>
+
+<p>
+ If you enter a 0, then all the objects will be translated to the origin.<br/>
+ If you enter a non-zero offset, this will be applied equally in both the X and the Y directions.<br/>
+
+</p>
+
+</div>
+<!-- SECTION "Symbol Translate... (et)" [72575-73739] -->
+<h3><a name="embed_component_picture_eb" id="embed_component_picture_eb">Embed Component/Picture (eb)</a></h3>
+<div class="level3">
+
+<p>
+<strong>gschem</strong> supports the concept of embedded components and graphics, where all the information necessary to display a component/graphic is placed in the schematic file. <strong>Edit | Embed Component/Picture</strong> causes schematic files to be significantly larger, but it makes it easy to share schematics with other people or archive schematics. You should only embed components when absolutely necessary.<br/>
+ To <strong>Embed Component/Picture</strong>:
+</p>
+<ul>
+<li class="level1"><div class="li"> Select the component/picture (in <strong>Select Mode</strong>)</div>
+</li>
+<li class="level1"><div class="li"> Select <strong>Edit | Embed Component/Picture</strong></div>
+</li>
+</ul>
+
+<p>
+ Save the schematic. The schematic file will now contain the text strings for the embedded component or embedded graphic.<br/>
+ The <strong>Add Component…</strong> dialog box allows you to optionally embed the component.<br/>
+ The <strong>Add Picture…</strong> dialog box does NOT allow you to optionally embed the component.<br/>
+ You can only embed and unembed components. Also, you cannot embed and then mirror a component (this is a limitation of <strong>gschem</strong> and will eventually be fixed).
+</p>
+
+</div>
+<!-- SECTION "Embed Component/Picture (eb)" [73740-74769] -->
+<h3><a name="unembed_component_picture_eu" id="unembed_component_picture_eu">Unembed Component/Picture (eu)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Edit | Unembed Component/Picture</strong> will move the componentâ??s or graphicâ??s information from the schematic fileâ??s contents and output it to the original fileâ??s path/filename (i.e., the schematic file includes the path/filename information). To <strong>Unembed Component/Picture</strong>:
+</p>
+<ul>
+<li class="level1"><div class="li"> Select the component/picture (in <strong>Select Mode</strong>)</div>
+</li>
+<li class="level1"><div class="li"> Select <strong>Edit | Unembed Component/Picture</strong></div>
+</li>
+</ul>
+
+<p>
+ Save the schematic. The schematic file will now NOT contain the text strings for the embedded component or embedded graphic.<br/>
+ You can only embed and unembed components.
+</p>
+
+</div>
+<!-- SECTION "Unembed Component/Picture (eu)" [74770-75359] -->
+<h3><a name="update_component_ep" id="update_component_ep">Update Component (ep)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Edit | Update Component</strong> updates a componentâ??s definition.<br/>
+ A symbol can be modified from within <strong>gschem</strong> using the following sequence:
+</p>
+<ul>
+<li class="level1"><div class="li"> Select the component for which the symbol should be changed.</div>
+</li>
+<li class="level1"><div class="li"> Select <strong>Hierarchy | Down Symbol</strong>. This takes you to the symbol editor</div>
+</li>
+<li class="level1"><div class="li"> Modify the symbol. This includes modifying the symbolâ??s graphic objects, adding/changing/deleting attributes, and moving objects with respect to the origin</div>
+</li>
+<li class="level1"><div class="li"> Donâ??t forget to <strong>Edit | Symbol Translate</strong></div>
+</li>
+<li class="level1"><div class="li"> Select <strong>File | Save Page</strong> to save the symbol to itâ??s file</div>
+</li>
+<li class="level1"><div class="li"> Select <strong>Hierarchy | Up Symbol</strong>. This returns you to the schematic editor</div>
+</li>
+<li class="level1"><div class="li"> With the component still selected, select <strong>Edit | Update Component</strong> to update the componetâ??s description from the modified symbolâ??s definition</div>
+</li>
+<li class="level1"><div class="li"> Select each component on the schematic(s) made from this symbol, and select <strong>Edit | Update Component</strong></div>
+</li>
+</ul>
+
+<p>
+ New components placed on the schematic from this updated symbol will use the new symbol definition.<br/>
+ Components placed on the schematic from this symbol will be updated the next time this schematic is opened.<br/>
+ The symbolâ??s <code>symversion</code> attribute will automatically be incremented for non-trivial changes when the symbol is saved. When a schematic is opened by <strong>gschem</strong>, all symbols used by the schematic are read from their libraries. The <code>symversion</code> attribute of the symbol read from the library is compared to the <code>symversion</code> attribute of the components in the schematic. If the <code>symversion</code> attributes are different, the <code>symversion</code> attribute is exposed on the schematic for those symbols effected. Note that:
+</p>
+<ul>
+<li class="level1"><div class="li"> This is a â??hintâ?? to the designer to check the symbol.</div>
+</li>
+<li class="level1"><div class="li"> You need to actually open a schematic file with <strong>gschem</strong> for the components to be updated.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Update Component (ep)" [75360-77169] -->
+<h3><a name="show_hide_inv_text_en" id="show_hide_inv_text_en">Show/Hide Inv Text (en)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Edit | Show/Hide Inv Text</strong> is most appropriate when creating or editing symbols, to view or hide the text for all of the symbolâ??s invisible attributes.<br/>
+ <a href="#make_inv_text_vis" title=":geda:gschem_ug.txt ↵" class="wikilink1">Make Inv Text Vis</a> is most appropriate when adding symbols to schematics, to view the text for the symbolâ??s modifiable invisible attributes.<br/>
+ <strong>Edit | Show/Hide Inv Text</strong> toggles between making all invisible text visible and hiding all invisible text. When selected, all objects in the symbol are effected.<br/>
+ Visible text always remains visible.<br/>
+ A symbol has the following <em class="u">potential</em> attributes :
+</p>
+<ul>
+<li class="level1"><div class="li"> netname</div>
+</li>
+<li class="level1"><div class="li"> refdes</div>
+</li>
+<li class="level1"><div class="li"> slot</div>
+</li>
+<li class="level1"><div class="li"> value</div>
+</li>
+<li class="level1"><div class="li"> net</div>
+</li>
+<li class="level1"><div class="li"> device</div>
+</li>
+<li class="level1"><div class="li"> pinnumber</div>
+</li>
+<li class="level1"><div class="li"> pinseq</div>
+</li>
+<li class="level1"><div class="li"> pintype</div>
+</li>
+<li class="level1"><div class="li"> pinlabel</div>
+</li>
+<li class="level1"><div class="li"> source</div>
+</li>
+<li class="level1"><div class="li"> numslots</div>
+</li>
+<li class="level1"><div class="li"> slotdef</div>
+</li>
+<li class="level1"><div class="li"> graphical</div>
+</li>
+<li class="level1"><div class="li"> footprint</div>
+</li>
+<li class="level1"><div class="li"> description</div>
+</li>
+<li class="level1"><div class="li"> documentation</div>
+</li>
+<li class="level1"><div class="li"> symversion</div>
+</li>
+<li class="level1"><div class="li"> comment</div>
+</li>
+<li class="level1"><div class="li"> file</div>
+</li>
+<li class="level1"><div class="li"> model-name</div>
+</li>
+</ul>
+
+<p>
+ Not all attributes need to be used to define a symbol (see the discussion of <a href="docs-20060124-gschem_ug-app_a.html" class="wikilink2" title="docs-20060124-gschem_ug-app_a.html">Appendix A -- Heavy vs Light Symbol Libraries</a>). The <strong>gschem</strong> default is to define symbols as â??lightâ??, indicating that the symbol includes as few attributes as necessary to describe the symbol. â??lightâ?? symbols depend on the designer attaching additional descriptive attributes to the symbol when the symbol is placed on the schematic. For example: a â??lightâ?? symbol for a resistor might include just the graphic for a resistor, its pin attributes, and the â??refdesâ?? attribute. This describes a resistor. It would be the designerâ??s responsibility, after the resistor has been placed on the schematic, to add the â??valueâ?? and â??footprintâ?? attributes appropriate for the specific resistor in the circuit. A â??heavyâ?? symbol includes more descriptive attributes. Using â??lightâ?? vs. â??heavyâ?? symbols is up to the designer.<br/>
+ A symbolâ??s attributes may be flagged as either visible or invisible. Attributes are flagged as invisible to reduce the clutter around a symbol on the schematic.<br/>
+ When creating or editing the symbol, and changing a visible attribute to an invisible attribute, the attribute can not be viewed during further editing of the symbol. It becomes difficult to place attribute text. To view both the visible and invisible text, select <strong>Edit | Show/Hide Inv Text</strong>.<br/>
+ When a symbol is instantiated on a schematic as a component, only the symbolâ??s visible attributes are promoted to the component. For example: if a resistorâ??s symbol defines â??refdesâ?? as the only visible attribute defined in the symbol, the only attribute that the component contains is the â??refdesâ?? attribute). Those attributes not included in the symbol definition may be added at the schematic level, component-by-component.<br/>
+ This operation is useful when drawing/debugging symbols.<br/>
+ When hidden text is visible, â??Show Hiddenâ?? will appear on the status-bar in the lower right.
+</p>
+
+</div>
+<!-- SECTION "Show/Hide Inv Text (en)" [77170-79997] -->
+<h3><a name="make_inv_text_vis_ev" id="make_inv_text_vis_ev">Make Inv Text Vis (ev)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Edit | Make Inv Text Vis</strong> is a quick method of making all of a componentâ??s invisible attributes visible. The same effect can be accomplished by double-clicking on the component and marking all of the entries in the Attributes listbox as â??Vis?" (i.e., visible).<br/>
+ To <strong>Make Inv Text Vis</strong> for a component:
+</p>
+<ul>
+<li class="level1"><div class="li"> Select the component(s) in <strong>Select Mode</strong></div>
+</li>
+<li class="level1"><div class="li"> Select <strong>Edit | Make Inv Text Vis</strong></div>
+</li>
+</ul>
+
+<p>
+ The attributes that had been hidden are displayed.<br/>
+ To hide the attributes again, you need to double-click the component to bring up itâ??s â??Edit Attributesâ?? dialog box, and explicitly place a check for each attribute you want hidden.
+</p>
+
+</div>
+<!-- SECTION "Make Inv Text Vis (ev)" [79998-80661] -->
+<h2><a name="buffer" id="buffer">Buffer</a></h2>
+<div class="level2">
+
+<p>
+<strong>gschem</strong> supports 5 copy/cut/paste buffers which are visible across all opened pages and windows.
+</p>
+
+</div>
+<!-- SECTION "Buffer" [80662-80781] -->
+<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">
+
+<p>
+To copy something into a buffer:
+</p>
+<ol>
+<li class="level1"><div class="li"> Select the objects you want to copy.</div>
+</li>
+<li class="level1"><div class="li"> Select Buffer/Copy/Copy into buffer #.</div>
+</li>
+</ol>
+
+</div>
+<!-- SECTION "Copy into 1/2/3/4/5 (yc)" [80782-80934] -->
+<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">
+
+<p>
+Cut is like copy in that it removes the objects from the schematic
+</p>
+
+</div>
+<!-- SECTION "Cut into 1/2/3/4/5 (yu)" [80935-81036] -->
+<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">
+
+<p>
+To paste a buffer into the current schematic:
+</p>
+<ol>
+<li class="level1"><div class="li"> Fill the buffer using the above Copy or Cut.</div>
+</li>
+<li class="level1"><div class="li"> Go to the new schematic page/window.</div>
+</li>
+<li class="level1"><div class="li"> Select Buffer/Paste/Paste from buffer #.</div>
+</li>
+<li class="level1"><div class="li"> Click the first mouse button to pick an anchor point.</div>
+</li>
+<li class="level1"><div class="li"> Move the mouse to the final spot.</div>
+</li>
+<li class="level1"><div class="li"> Click the first mouse button again.</div>
+</li>
+</ol>
+
+</div>
+<!-- SECTION "Paste from 1/2/3/4/5 (yp)" [81037-81390] -->
+<h2><a name="view" id="view">View</a></h2>
+<div class="level2">
+
+</div>
+<!-- SECTION "View" [81391-81408] -->
+<h3><a name="redraw_vr" id="redraw_vr">Redraw (vr)</a></h3>
+<div class="level3">
+
+<p>
+<strong>View | Redraw</strong> re-paints the current window.<br/>
+ This is useful when you have mouse/component/line/text etc… droppings left over from a previous action. It is also useful when you want to update all visual connectivity cues.
+</p>
+
+</div>
+<!-- SECTION "Redraw (vr)" [81409-81659] -->
+<h3><a name="pan_x" id="pan_x">Pan (x)</a></h3>
+<div class="level3">
+
+<p>
+<strong>View | Pan</strong> lets you change the focus of the display.<br/>
+ To pan the display:
+</p>
+<ul>
+<li class="level1"><div class="li"> Select <strong>View | Pan</strong></div>
+</li>
+<li class="level1"><div class="li"> Click the first mouse button at the new center of the display.</div>
+</li>
+</ul>
+
+<p>
+ To pan the display using the shortcut is much simpler, simply place the mouse pointer where you want the display centered and type â??xâ??. The display will jump to the mouseâ??s location.<br/>
+ Pan behavior is configurable. The system-gschemrc file defines: <pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">(third-button "popup")</font></pre>
+</p>
+
+<p>
+If you override the system-gschemrcâ??s default, of popping up a menu when the third mouse button is clicked, by adding: <pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">(third-button "mousepan")</font></pre>
+</p>
+
+<p>
+to either your userâ??s ~/gschemrc file or local â??pwdâ??/gschemrc file, the third mouse button (i.e., the right mouse button on scroll-wheel mice) will allow you to pan the schematic by holding down the third mouse button and dragging.<br/>
+ The system-gschemrc file also defines: <pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">(fast-mousepan "enabled")</font></pre>
+</p>
+
+<p>
+If you override the system-gschemrcâ??s default by adding: <pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">(fast-mousepan "disabled")</font></pre>
+</p>
+
+<p>
+to either your userâ??s ~/gschemrc file or local â??pwdâ??/gschemrc file, text will be displayed properly when the third mouse button is held down while dragging. The <code>(third-button â??mousepanâ??)</code> setting must also be applied for this to work. Disabling <code>fast-mousepan</code> adversely effects rendering speed while panning on large â??complicatedâ?? schematics.<br/>
+ The system-gschemrc file also defines: <pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">(zoom-with-pan "enabled")</font></pre>
+</p>
+
+<p>
+If you override the system-gschemrcâ??s default by adding: <pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">(zoom-with-pan "disabled")</font></pre>
+</p>
+
+<p>
+to either your userâ??s ~/gschemrc file or local â??pwdâ??/gschemrc file, whenever you zoom in/out, the zoom will NOT center on the mouse pointer, effectively removing the pan feature of the zoom in/out operations.
+</p>
+
+</div>
+<!-- SECTION "Pan (x)" [81660-83456] -->
+<h3><a name="zoom_box_w" id="zoom_box_w">Zoom Box (w)</a></h3>
+<div class="level3">
+
+<p>
+<strong>View | Zoom Box</strong> allows you to draw a box around a part of the <strong>gschem</strong> window and zoom in.<br/>
+ To use <strong>View | Zoom Box</strong>:
+</p>
+<ul>
+<li class="level1"><div class="li"> Select <strong>View | Zoom Box</strong></div>
+</li>
+<li class="level1"><div class="li"> Position the mouse pointer at one corner of the box you want to draw</div>
+</li>
+<li class="level1"><div class="li"> Click and hold down the first mouse button</div>
+</li>
+<li class="level1"><div class="li"> Drag the mouse, drawing the zoom box around the area to which you want to zoom</div>
+</li>
+<li class="level1"><div class="li"> Release the mouse button and the display will zoom</div>
+</li>
+</ul>
+
+<p>
+ To use <strong>View | Zoom Box</strong> by typing the equivalent shortcut (i.e., â??<strong>w</strong>â??) is more convenient. Simply position the mouse pointer at one corner of the zoom box, then type â??<strong>w</strong>â??. The zoom box will start immediately using the current mouse location as the first corner of the box.<br/>
+ <strong>View | Zoom Box</strong> will attempt to zoom to the requested area, but some boxes are not legal and <strong>gschem</strong> will do itâ??s best to zoom the requested area.
+</p>
+
+</div>
+<!-- SECTION "Zoom Box (w)" [83457-84337] -->
+<h3><a name="zoom_extents_ve" id="zoom_extents_ve">Zoom Extents (ve)</a></h3>
+<div class="level3">
+
+<p>
+<strong>View | Extents</strong> will zoom the display to fit all of the placed objects into the current window.<br/>
+ To view all of the current windowâ??s objects:
+</p>
+<ul>
+<li class="level1"><div class="li"> Select <strong>View | Extents</strong></div>
+</li>
+</ul>
+
+<p>
+ Typing the <strong>View | Extents</strong> shortcut (i.e., â??<strong>ve</strong>â??) is particularly convenient for those that have learned to navigate the schematics using the shortcuts.<br/>
+
+</p>
+
+</div>
+<!-- SECTION "Zoom Extents (ve)" [84338-84704] -->
+<h3><a name="zoom_in_z" id="zoom_in_z">Zoom In (z)</a></h3>
+<div class="level3">
+
+<p>
+<strong>View | Zoom In</strong> zooms the display in. The current center of the window is the center of the new window. This command zooms in by a factor.<br/>
+ To zoom in:
+</p>
+<ul>
+<li class="level1"><div class="li"> Select <strong>View | Zoom In</strong></div>
+</li>
+</ul>
+
+<p>
+ The (zoom-with-pan â??enabledâ??) configuration setting in the gschemrc files effects the operation of the zoom in shortcut (i.e., â??<strong>z</strong>â??). The default system-gschemrc setting for: <pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">(zoom-with-pan "enabled")</font></pre>
+</p>
+
+<p>
+enables zooming in, using the mouse pointerâ??s location as the new center of the window. If this changed to: <pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">(zoom-with-pan "disabled")</font></pre>
+</p>
+
+<p>
+in either your userâ??s ~/gschemrc file or local â??pwdâ??/gschemrc file, whenever you zoom in, the zoom will NOT center on the mouse pointer but will center on the current center of the window, effectively removing the pan feature of the zoom in operation.<br/>
+ To zoom in using the shortcut:
+</p>
+<ul>
+<li class="level1"><div class="li"> If the default (zoom-with-pan â??enabledâ??) is configured in one of the gschemrc files, position the mouse pointer in the window where you want the new center</div>
+</li>
+<li class="level1"><div class="li"> Type â??<strong>z</strong>â??</div>
+</li>
+</ul>
+
+<p>
+ Typing â??<strong>z</strong>â?? is particularly convenient for those that have learned to navigate the schematics using the shortcuts.
+</p>
+
+</div>
+<!-- SECTION "Zoom In (z)" [84705-85866] -->
+<h3><a name="zoom_out_z" id="zoom_out_z">Zoom Out (Z)</a></h3>
+<div class="level3">
+
+<p>
+<strong>View | Zoom Out</strong> zooms the display out. The current center of the window is the center of the new window. This command zooms out by a factor.<br/>
+ To zoom out:
+</p>
+<ul>
+<li class="level1"><div class="li"> Select <strong>View | Zoom Out</strong></div>
+</li>
+</ul>
+
+<p>
+ The (zoom-with-pan â??enabledâ??) configuration setting in the gschemrc files effects the operation of the zoom out shortcut (i.e., â??<strong>z</strong>â??). The default system-gschemrc setting for: <pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">(zoom-with-pan "enabled")</font></pre>
+</p>
+
+<p>
+enables zooming out, using the mouse pointerâ??s location as the new center of the window. If this changed to: <pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">(zoom-with-pan "disabled")</font></pre>
+</p>
+
+<p>
+in either your userâ??s ~/gschemrc file or local â??pwdâ??/gschemrc file, whenever you zoom out, the zoom will NOT center on the mouse pointer but will center on the current center of the window, effectively removing the pan feature of the zoom out operation.<br/>
+ To zoom out using the shortcut:
+</p>
+<ul>
+<li class="level1"><div class="li"> If the default (zoom-with-pan â??enabledâ??) is configured in one of the gschemrc files, position the mouse pointer in the window where you want the new center</div>
+</li>
+<li class="level1"><div class="li"> Type â??<strong>Z</strong>â?? (i.e., shift-z)</div>
+</li>
+</ul>
+
+<p>
+ Typing â??<strong>Z</strong>â?? is particularly convenient for those that have learned to navigate the schematics using the shortcuts.
+</p>
+
+</div>
+<!-- SECTION "Zoom Out (Z)" [85867-87055] -->
+<h3><a name="zoom_full_vf" id="zoom_full_vf">Zoom Full (vf)</a></h3>
+<div class="level3">
+
+<p>
+<strong>View | Zoom Full</strong> will zoom the display to the maximum possible displayable view.<br/>
+
+</p>
+
+<p>
+To view the maximum displayable area:
+</p>
+<ul>
+<li class="level1"><div class="li"> Select <strong>View | Zoom Full</strong></div>
+</li>
+</ul>
+
+<p>
+ The window contents will immediately change to show the maximum possible displayable view.<br/>
+
+</p>
+
+<p>
+To view the maximum displayable area using the keyboard shortcut (i.e., â??<strong>vf</strong>â??):
+</p>
+<ul>
+<li class="level1"><div class="li"> Type â??<strong>vf</strong>â??</div>
+</li>
+</ul>
+
+<p>
+ The window contents will immediately change to show the maximum possible displayable view.<br/>
+
+</p>
+
+<p>
+<strong>View | Zoom Full</strong> is useful if you like to put your working notes outside the titleblock for you schematic, for example. Just remember, these notes would now be considered part of the windows extents, so if you were to <strong>View | Extents</strong>, the display would show the titleblock and your working notes.
+</p>
+
+</div>
+<!-- SECTION "Zoom Full (vf)" [87056-87834] -->
+<h2><a name="page" id="page">Page</a></h2>
+<div class="level2">
+
+</div>
+<!-- SECTION "Page" [87835-87853] -->
+<h3><a name="manager..._pm" id="manager..._pm">Manager... (pm)</a></h3>
+<div class="level3">
+
+</div>
+<!-- SECTION "Manager... (pm)" [87854-87881] -->
+<h3><a name="next" id="next">Next (>)</a></h3>
+<div class="level3">
+
+</div>
+<!-- SECTION "Next (>)" [87882-87902] -->
+<h3><a name="previous" id="previous">Previous (<)</a></h3>
+<div class="level3">
+
+</div>
+<!-- SECTION "Previous (<)" [87903-87927] -->
+<h3><a name="new_pe" id="new_pe">New (pe)</a></h3>
+<div class="level3">
+
+</div>
+<!-- SECTION "New (pe)" [87928-87948] -->
+<h3><a name="revert_pr" id="revert_pr">Revert (pr)</a></h3>
+<div class="level3">
+
+</div>
+<!-- SECTION "Revert (pr)" [87949-87972] -->
+<h3><a name="close_pc" id="close_pc">Close (pc)</a></h3>
+<div class="level3">
+
+</div>
+<!-- SECTION "Close (pc)" [87973-87995] -->
+<h3><a name="discard_pd" id="discard_pd">Discard (pd)</a></h3>
+<div class="level3">
+
+</div>
+<!-- SECTION "Discard (pd)" [87996-88020] -->
+<h2><a name="add" id="add">Add</a></h2>
+<div class="level2">
+
+</div>
+<!-- SECTION "Add" [88021-88037] -->
+<h3><a name="component..._i" id="component..._i">Component... (i)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Add | Component…</strong> opens a dialog box which lets you place components from the component libraries.<br/>
+ To place a component:
+</p>
+<ul>
+<li class="level1"><div class="li"> Select <strong>Add |Component…</strong></div>
+</li>
+<li class="level1"><div class="li"> Select a component Library from the left list-box</div>
+</li>
+<li class="level1"><div class="li"> Select a component from the right list-box</div>
+</li>
+<li class="level1"><div class="li"> Confirm the symbol is correct by reviewing the image in the Preview window</div>
+</li>
+<li class="level1"><div class="li"> Move the mouse into the main drawing window (you should see an outline follow the mouse pointer).</div>
+</li>
+<li class="level1"><div class="li"> Press the first mouse button to anchor the component</div>
+</li>
+<li class="level1"><div class="li"> Position the mouse pointer, and keep pressing the first mouse button to anchor additional instances of the component</div>
+</li>
+<li class="level1"><div class="li"> When finished anchoring components, press the last mouse button or the ESC key</div>
+</li>
+</ul>
+
+<p>
+ If a component name is already selected, hitting apply and moving the mouse into the main window will allow you to place that component again.<br/>
+ You can rotate the component before you place it by clicking the middle button. For every button click, the component will be rotate counter-clockwise 90 degrees.<br/>
+ Care has been taken to give components descriptive names in the libraries, though it is sometimes difficult to determine what the component really represents from its name.<br/>
+ For example: in the analog library there are four capacitor entries:
+</p>
+<ul>
+<li class="level1"><div class="li"> capacitor-1.sym</div>
+</li>
+<li class="level1"><div class="li"> capacitor-2.sym</div>
+</li>
+<li class="level1"><div class="li"> capacitor-3.sym</div>
+</li>
+<li class="level1"><div class="li"> capacitor-4.sym</div>
+</li>
+</ul>
+
+<p>
+ It helps to preview the symbol in the â??Select Componentâ?? dialog box before selecting and placing the symbol.
+</p>
+
+</div>
+<!-- SECTION "Component... (i)" [88038-89514] -->
+<h3><a name="net_n" id="net_n">Net (n)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Net</strong> draws a net segment.<br/>
+ A net is typically a contiguous set of line segments between two pins, though it is possible to draw nets between a pin and a point on another net, or between two nets.<br/>
+ For example, the following diagram shows 3 net segments:
+</p>
+<ul>
+<li class="level1"><div class="li"> Between R1 and R2</div>
+</li>
+<li class="level1"><div class="li"> Between R3 and R4</div>
+</li>
+<li class="level1"><div class="li"> Between the two nets</div>
+</li>
+</ul>
+<table class="inline">
+ <tr>
+ <td> <a href="media/geda/nets.jpg" class="media" target="_blank" title="geda:nets.jpg"><img src="media/geda/nets.jpg" class="media" alt="" /></a> </td>
+ </tr>
+</table>
+
+<p>
+ Note the small red segment at the end of the resistorâ??s pins. All pins in <strong>gschem</strong> have this red segment. This is the connectivity cue for the pin. It is sometimes difficult to â??grabâ?? this attachment point when drawing nets, you may need to zoom in on the pin. To zoom in, press the â??zâ?? key. To zoom out, press the â??Zâ?? (i.e., shift-z) key.<br/>
+ To begin drawing a net using the menu:
+</p>
+<ul>
+<li class="level1"><div class="li"> Select <strong>Add | Net</strong></div>
+</li>
+<li class="level1"><div class="li"> Zoom in on the component where the net is to start, so that you can easily grab the pinâ??s attachment point</div>
+</li>
+<li class="level1"><div class="li"> Position the mouse pointer over the pinâ??s connectivity cue</div>
+</li>
+<li class="level1"><div class="li"> Press the first mouse button to start the net</div>
+</li>
+</ul>
+
+<p>
+ To begin drawing the net using the shortcut:
+</p>
+<ul>
+<li class="level1"><div class="li"> Zoom in on the component where the net is to start, so that you can easily grab the pinâ??s attachment point</div>
+</li>
+<li class="level1"><div class="li"> Position the mouse pointer over the pinâ??s connectivity cue</div>
+</li>
+<li class="level1"><div class="li"> Press the â??nâ?? key</div>
+</li>
+</ul>
+
+<p>
+ To continue drawing the net segment(s):
+</p>
+<ul>
+<li class="level1"><div class="li"> Drag the mouse pointer in the direction of the end-point</div>
+</li>
+<li class="level1"><div class="li"> For any necessary 90º turns, single-click the mouse, and continue dragging the mouse pointer toward the end-point</div>
+</li>
+<li class="level1"><div class="li"> For any necessary non-orthogonal net segments (e.g., 45º angle), hold down the CONTROL button, single-click the mouse, and continue dragging the mouse pointer to the end-point</div>
+</li>
+<li class="level1"><div class="li"> When you reach the end-point, press the first mouse button to end the net segment</div>
+</li>
+<li class="level1"><div class="li"> Another net segment will start at the last end-point</div>
+<ul>
+<li class="level2"><div class="li"> If this second pin is to be connected to a third pin, continue as above</div>
+</li>
+<li class="level2"><div class="li"> If this is the end of the connections, press the last mouse button (or ESC) to end the net</div>
+</li>
+</ul>
+</li>
+</ul>
+
+<p>
+ Press the last mouse button or ESC to cancel any net in progress.<br/>
+ If the net is cancelled you are automatically placed in <strong>Select Mode</strong>. You must pick <strong>Add | Net</strong> again or type the shortcut to add more nets.<br/>
+ You cannot connect a net segment to the middle of a non-orthogonal net.<br/>
+ The boxes at the end of the nets are connectivity cues. Red boxes signify a dangling net (not connected to anything).<br/>
+ Filled circles are midpoint connections/junctions. These cues are drawn automatically and are an indicator of electrical connectivity.<br/>
+ See <a href="docs-20060124-gschem_ug-electrical_connectivity.html" class="wikilink2" title="docs-20060124-gschem_ug-electrical_connectivity.html">Electrical Connectivity</a> for more information.
+</p>
+
+</div>
+<!-- SECTION "Net (n)" [89515-92106] -->
+<h3><a name="bus_u" id="bus_u">Bus (u)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Add | Bus</strong> is basically the same as <strong>Add | Net</strong>, except that it draws buses.<br/>
+ Buses are very new and there are many aspects which are not defined yet, so keep that in mind as you uses buses. More to be added here eventually.
+</p>
+
+</div>
+<!-- SECTION "Bus (u)" [92107-92356] -->
+<h3><a name="attribute..._aa" id="attribute..._aa">Attribute... (aa)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Add | Attribute…</strong> is appropriate when creating or editing symbols, to add a new attribute.<br/>
+ <strong>Add | Attribute…</strong> brings up the â??Single Attribute Editorâ?? dialog box. This dialog box is ONLY used to add attributes. It does not display or manipulate already placed attributes.<br/>
+ An attribute is nothing more than a text item which is in the form <code>name=value</code> (there cannot be any spaces to the left or right of the name,value pair). It can be either attached to an object, or unattached.<br/>
+ To add an unattached attribute (e.g., â??commentâ??, â??documentationâ??, etc.) to the symbol:
+</p>
+<ul>
+<li class="level1"><div class="li"> Select <strong>Add | Attribute…</strong></div>
+</li>
+<li class="level1"><div class="li"> Select an attribute name off of the pulldown list, or type the attribute name into the name entry</div>
+</li>
+<li class="level1"><div class="li"> Type in a value for the attribute</div>
+</li>
+<li class="level1"><div class="li"> Pick any of the attribute options</div>
+</li>
+<li class="level1"><div class="li"> Click OK, and the attribute will be placed.</div>
+</li>
+</ul>
+
+<p>
+ If you want to attach an attribute to an object, then select the desired object first and then <strong>Add | Attribute…</strong> from the pull-down menu. If you click on an object which has attached attributes, the attached attributes should be selected as well.<br/>
+ If you select <strong>Add | Attribute…</strong> off of the pull down menus then you do not have much control as to where the attribute gets placed (it gets places either at the lower left hand corner of the object extents or at the origin of any selected object). However, if you use the hot key (i.e., â??aaâ??) then the current mouse position is used as the anchor point for the attribute item.<br/>
+ You cannot place an incomplete attribute (an attribute without a name and value).<br/>
+ Please see <a href="docs-20060124-gschem_ug-components_symbols_objects_attributes.html" class="wikilink2" title="docs-20060124-gschem_ug-components_symbols_objects_attributes.html">Components/Symbols/Objects/Attributes</a> for more info on how to use attributes.
+</p>
+
+</div>
+<!-- SECTION "Attribute... (aa)" [92357-94069] -->
+<h3><a name="text..._at" id="text..._at">Text... (at)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Add | Text…</strong> displays the â??Text Entry…â?? dialog box. To place text:
+</p>
+<ul>
+<li class="level1"><div class="li"> Select <strong>Options | Text Size…</strong> and select the size for the text</div>
+</li>
+<li class="level1"><div class="li"> Select <strong>Add | Text…</strong></div>
+</li>
+<li class="level1"><div class="li"> Type the text in the entry field (multiple lines may be entered by pressing Enter)</div>
+</li>
+<li class="level1"><div class="li"> Press Apply or type Enter</div>
+</li>
+<li class="level1"><div class="li"> Move the mouse into the main window (an outline of the text should appear and follow the mouse)</div>
+</li>
+<li class="level1"><div class="li"> Press the first mouse button to anchor the text</div>
+</li>
+<li class="level1"><div class="li"> Close the â??Text Entry…â?? dialog box</div>
+</li>
+</ul>
+
+<p>
+ If you leave the <strong>Add | Text…</strong> dialog box open you can place the same text item again and again by just clicking Apply (or pressing Enter) and moving the mouse into the main window.<br/>
+ The following settings in the system-gschemrc file, the userâ??s ~/gschemrc file, or the local â??pwdâ??/gschemrc file control how text is displayed:
+</p>
+<pre class="code lisp"><span class="co1">; text-origin-marker : Controls if the text origin markers are displayed.</span>
+<span class="co1">; text-size : Sets the default text size.</span>
+<span class="co1">; text-caps-style : Sets the default caps style used for the display of text</span>
+<span class="co1">; output-text : Controls how text is rendered to postscript</span></pre>
+<p>
+Text which is placed will be automatically capitalized. Please see the Resource file section below on how to control this behavior.<br/>
+ To cancel a text place press the last mouse button or the ESC key.<br/>
+ If you create text in the form name=value, then you are creating attributes. gEDA allows for general attributes to be free floating (or unattached). It is a good idea to change the color of these floating attributes to the current attribute color (which is also called the attached attribute color) to signify that this text item is an attribute.<br/>
+ You can rotate the text before you place it by clicking the middle button. For every button click, the text will be rotate 90 degrees.<br/>
+
+</p>
+
+</div>
+<!-- SECTION "Text... (at)" [94070-95873] -->
+<h3><a name="line_l" id="line_l">Line (l)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Add | Line</strong> draws a single line segment.<br/>
+ To draw a line:
+</p>
+<ul>
+<li class="level1"><div class="li"> If you want to snap the line to the grid, set the grid spacing by selecting <strong>Options | Snap Grid Spacing…</strong> and entering the grid spacing, and then selecting <strong>Options | Toggle Snap On/Off</strong> until you donâ??t see â??Snap Offâ?? on the status-bar</div>
+</li>
+<li class="level1"><div class="li"> Select <strong>Add | Line</strong></div>
+</li>
+<li class="level1"><div class="li"> If you want to constrain the line to 90º movements, hold the CONTROL key down while moving the mouse</div>
+</li>
+<li class="level1"><div class="li"> Position the mouse pointer to the start-point</div>
+</li>
+<li class="level1"><div class="li"> Press the first mouse button</div>
+</li>
+<li class="level1"><div class="li"> Move the mouse in the intended direction</div>
+</li>
+<li class="level1"><div class="li"> When positioned at the end-point, press the first mouse button</div>
+</li>
+<li class="level1"><div class="li"> Continue placing lines, until you either press the second mouse button or type the Escape key</div>
+</li>
+</ul>
+
+<p>
+ <strong>Add | Line</strong> draws a line in the same fashion as drawing nets with the following exceptions:
+</p>
+<ul>
+<li class="level1"><div class="li"> A line has no electrical significance</div>
+</li>
+<li class="level1"><div class="li"> Only a single line segment can be drawn</div>
+</li>
+<li class="level1"><div class="li"> You keep drawing lines as long as you are in line <strong>Line Mode</strong>.</div>
+</li>
+</ul>
+
+<p>
+ To cancel a line in progress, press the last mouse button or type the ESC key.
+</p>
+
+</div>
+<!-- SECTION "Line (l)" [95874-96960] -->
+<h3><a name="box_b" id="box_b">Box (b)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Add | Box</strong> draws a box. To draw a box:
+</p>
+<ul>
+<li class="level1"><div class="li"> If you want to snap the box to the grid, set the grid spacing by selecting <strong>Options | Snap Grid Spacing…</strong> and entering the grid spacing, and then selecting <strong>Options | Toggle Snap On/Off</strong> until you donâ??t see â??Snap Offâ?? on the status-bar</div>
+</li>
+<li class="level1"><div class="li"> Select <strong>Add | Box</strong></div>
+</li>
+<li class="level1"><div class="li"> Position the mouse pointer to the start-point</div>
+</li>
+<li class="level1"><div class="li"> Press the first mouse button</div>
+</li>
+<li class="level1"><div class="li"> Move the mouse in the intended direction</div>
+</li>
+<li class="level1"><div class="li"> When positioned at the end-point, press the first mouse button again</div>
+</li>
+<li class="level1"><div class="li"> Continue placing boxes, until you either press the second mouse button or type the ESC key</div>
+</li>
+</ul>
+
+<p>
+ To cancel a box in progress, press the last mouse button or type the ESC key.<br/>
+ A box has no electrical significance.
+</p>
+
+</div>
+<!-- SECTION "Box (b)" [96961-97713] -->
+<h3><a name="circle_ai" id="circle_ai">Circle (ai)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Add | Circle</strong> creates a circle.<br/>
+ To draw a circle:
+</p>
+<ul>
+<li class="level1"><div class="li"> If you want to snap the box to the grid, set the grid spacing by selecting <strong>Options | Snap Grid Spacing…</strong> and entering the grid spacing, and then selecting <strong>Options | Toggle Snap On/Off</strong> until you donâ??t see â??Snap Offâ?? on the status-bar</div>
+</li>
+<li class="level1"><div class="li"> Select <strong>Add | Circle</strong></div>
+</li>
+<li class="level1"><div class="li"> Place the mouse pointer at the center of the circle</div>
+</li>
+<li class="level1"><div class="li"> Press the first button</div>
+</li>
+<li class="level1"><div class="li"> Move the mouse to see an outline of the circle</div>
+</li>
+<li class="level1"><div class="li"> Press the first mouse button to finish the circle</div>
+</li>
+<li class="level1"><div class="li"> Continue placing circles, until you either press the second mouse button or type the ESC key</div>
+</li>
+</ul>
+
+<p>
+ To draw a circle (typing the shortcut), same as above except that you position the mouse pointer to the center-point of the circle before you type the shortcut.<br/>
+ To cancel a circle in progress, press the last mouse button or the ESC key.<br/>
+
+</p>
+
+</div>
+<!-- SECTION "Circle (ai)" [97714-98598] -->
+<h3><a name="arc_ar" id="arc_ar">Arc (ar)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Add | Arc</strong> draws an arc. To draw an arc:
+</p>
+<ul>
+<li class="level1"><div class="li"> If you want to snap the box to the grid, set the grid spacing by selecting <strong>Options | Snap Grid Spacing…</strong> and entering the grid spacing, and then selecting <strong>Options | Toggle Snap On/Off</strong> until you donâ??t see â??Snap Offâ?? on the status-bar</div>
+</li>
+<li class="level1"><div class="li"> Select <strong>Add | Arc</strong></div>
+</li>
+<li class="level1"><div class="li"> Place the mouse pointer at the center-point for the arc</div>
+</li>
+<li class="level1"><div class="li"> Press the first mouse button</div>
+</li>
+<li class="level1"><div class="li"> Move the mouse to the right, to define the radius of the arc</div>
+</li>
+<li class="level1"><div class="li"> Press the first mouse button again</div>
+</li>
+<li class="level1"><div class="li"> Enter the Start Angle (in degrees) – 0º is the â??xâ?? axis</div>
+</li>
+<li class="level1"><div class="li"> Enter the Degrees of Sweep (for counter-clockwise sweep)</div>
+</li>
+<li class="level1"><div class="li"> Press OK</div>
+</li>
+<li class="level1"><div class="li"> Continue placing arcs, until you either press the second mouse button or type the ESC key</div>
+</li>
+</ul>
+
+<p>
+ The Start Angle can be positive or negative. The degrees are specified using the standard Cartesian coordinate system. The degrees of sweep can be positive or negative.<br/>
+ To cancel an arc in progress (while rubberband the radius), press the last mouse button or the ESC key or press the Cancel button in the arc dialog box.
+</p>
+
+</div>
+<!-- SECTION "Arc (ar)" [98599-99691] -->
+<h3><a name="pin_ap" id="pin_ap">Pin (ap)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Add | Pin</strong> adds a pin.<br/>
+ Though you can <strong>Add | Pin</strong> while entering a schematic, it only makes sense to create pins while creating or editing symbol files.<br/>
+ To draw a pin:
+</p>
+<ul>
+<li class="level1"><div class="li"> Set the grid spacing by selecting <strong>Options | Snap Grid Spacing…</strong> and entering the grid spacing, and then selecting <strong>Options | Toggle Snap On/Off</strong> until you donâ??t see â??Snap Offâ?? on the status-bar. The <a href="http://www.geda.seul.org/docs/current/symbols/symbols.pdf"; class="urlextern" title="http://www.geda.seul.org/docs/current/symbols/symbols.pdf"; rel="nofollow">gEDA/gaf Symbol Creation Document</a> specifies grid settings for pin placement in gEDA/gaf compliant symbols files.</div>
+</li>
+<li class="level1"><div class="li"> Select <strong>Add | Pin</strong></div>
+</li>
+<li class="level1"><div class="li"> Pins are constrained to 90º movements</div>
+</li>
+<li class="level1"><div class="li"> Position the mouse pointer to the start-point</div>
+</li>
+<li class="level1"><div class="li"> Press the first mouse button</div>
+</li>
+<li class="level1"><div class="li"> Move the mouse in the intended direction. The <a href="http://www.geda.seul.org/docs/current/symbols/symbols.pdf"; class="urlextern" title="http://www.geda.seul.org/docs/current/symbols/symbols.pdf"; rel="nofollow">gEDA/gaf Symbol Creation Document</a> specifies the length of pins in gEDA/gaf compliant symbol files.</div>
+</li>
+<li class="level1"><div class="li"> When positioned at the end-point, press the first mouse button</div>
+</li>
+<li class="level1"><div class="li"> Continue placing pins, until you either press the second mouse button or type the Escape key</div>
+</li>
+</ul>
+
+<p>
+ To cancel a pin in progress, press the last mouse button or the ESC key.
+</p>
+
+</div>
+<!-- SECTION "Pin (ap)" [99692-100879] -->
+<h3><a name="picture..._ag" id="picture..._ag">Picture... (ag)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Add | Picture</strong> places a graphic in the schematic. To draw a picture:
+</p>
+<ul>
+<li class="level1"><div class="li"> If you want to snap the picture to the grid, set the grid spacing by selecting <strong>Options | Snap Grid Spacing…</strong> and entering the grid spacing, and then selecting <strong>Options | Toggle Snap On/Off</strong> until you donâ??t see â??Snap Offâ?? on the status-bar</div>
+</li>
+<li class="level1"><div class="li"> Select <strong>Add | Picture</strong></div>
+</li>
+<li class="level1"><div class="li"> Select the graphic file from the â??Please select a picture fileâ?? dialog box</div>
+</li>
+<li class="level1"><div class="li"> Press OK</div>
+</li>
+<li class="level1"><div class="li"> Position the mouse pointer to the start-point</div>
+</li>
+<li class="level1"><div class="li"> Press the first mouse button</div>
+</li>
+<li class="level1"><div class="li"> Move the mouse in the intended direction. The outline of the picture will appear, retaining the aspect ratio of the original picture.</div>
+</li>
+<li class="level1"><div class="li"> When positioned at the end-point, press the first mouse button again.</div>
+</li>
+<li class="level1"><div class="li"> Continue placing pictures, until you either press the second mouse button or type the ESC key</div>
+</li>
+</ul>
+
+<p>
+ To cancel a picture in progress, press the last mouse button or type the ESC key.<br/>
+ A picture has no electrical significance.
+</p>
+
+</div>
+<!-- SECTION "Picture... (ag)" [100880-101875] -->
+<h2><a name="hierarchy" id="hierarchy">Hierarchy</a></h2>
+<div class="level2">
+
+</div>
+<!-- SECTION "Hierarchy" [101876-101898] -->
+<h3><a name="down_schematic_hd" id="down_schematic_hd">Down Schematic (Hd)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Hierarchy | Down Schematic</strong> shifts the focus from the current schematic to a sub-schematic.<br/>
+ Go down into a symbol, opening up any underlying schematics. Basically this will open up an underlying schematic of the selected component if it exists in the source library search path. See the Resource File section on how to define this path.<br/>
+ There are currently two ways of specifying that a symbol has an underlying schematic or schematics:
+</p>
+<ol>
+<li class="level1"><div class="li"> The underlying schematic must have the same name as the symbol but have a .sch extension and must follow the _# suffix naming convention. See the Files section below on this convention.</div>
+</li>
+<li class="level1"><div class="li"> Attach an attribute to the symbol called source=filename.sch filename.sch is not a path to the symbol, but rather the basename (last file in the path specifier) of the symbol path. The underlying schematic will still be searched in the source-library path. You can specify multiple source= attributes. The underlying schematics will be opened in the order that the source= attribute is found.</div>
+</li>
+</ol>
+
+<p>
+ If there multiple underlying schematics, they will be loaded. Movement between the schematic pages is restricted (to the same level of the same set of underlying schematics) unless the rc keyword enforce-hierarchy is modified to allow for a freer hierarchy traversal mode. See the Resource File section for more info.<br/>
+ It is also recommend that you maintain unique names for the various levels (when using the source= attribute) to avoid possible confusion. The hierarchy mechanisms are fairly new so expect some odd behavior (and please report it)
+</p>
+
+</div>
+<!-- SECTION "Down Schematic (Hd)" [101899-103511] -->
+<h3><a name="down_symbol_hs" id="down_symbol_hs">Down Symbol (Hs)</a></h3>
+<div class="level3">
+
+<p>
+This option will open up the symbol of the selected component.<br/>
+ Once the symbol is open, the user can edit it and save it.<br/>
+ At this time, the toplevel schematic will not see the symbol change unless the toplevel schematic is reloaded or File/Revert is executed. This will be fixed eventually.
+</p>
+
+</div>
+<!-- SECTION "Down Symbol (Hs)" [103512-103834] -->
+<h3><a name="up_hu" id="up_hu">Up (Hu)</a></h3>
+<div class="level3">
+
+<p>
+This option will move up the hierarchy (if there are pages above the currently displayed page).
+</p>
+
+</div>
+<!-- SECTION "Up (Hu)" [103835-103949] -->
+<h3><a name="documentation_ho" id="documentation_ho">Documentation (Ho)</a></h3>
+<div class="level3">
+
+<p>
+Open any documentation available for the selected symbol/component.<br/>
+ The job is handed over to â??gschemdocâ??, which makes a best-effort attempt of finding relevant documentation.<br/>
+ The documention would normally be in <acronym title="Portable Document Format">PDF</acronym>, <acronym title="HyperText Markup Language">HTML</acronym>, text or image format, but gschemdoc tries to be as transparent as possible on this account.<br/>
+ First and foremost, the attribute â??documentation=" is assumed to point to the documentation. This attribute should either be the filename (basename) of the document, or it should be a complete <acronym title="Uniform Resource Locator">URL</acronym>.<br/>
+ If it is a filename, and the file is found locally (in /usr/share/gEDA/documentation or otherwise), the relevant viewer will be initiated. Otherwise, a Google search for the document will be initiated.<br/>
+ If there is no documentation attribute, the attributes â??deviceâ?? and possibly â??valueâ?? will be consulted in much the same way as for â??documentationâ??. File searches will be made in forms of filenames like â??device-value.pdfâ?? and â??device.pdfâ??.<br/>
+ Failing that, the file name for the symbol itself will be used as basis for the search.
+</p>
+
+</div>
+<!-- SECTION "Documentation (Ho)" [103950-105034] -->
+<h2><a name="attributes1" id="attributes1">Attributes</a></h2>
+<div class="level2">
+
+</div>
+<!-- SECTION "Attributes" [105035-105058] -->
+<h3><a name="attach_ta" id="attach_ta">Attach (ta)</a></h3>
+<div class="level3">
+
+<p>
+The Attach command allows you to take a text item (in the proper form; <code>name=value</code>) and attach it to another object.<br/>
+ To use Attributes/Attach:
+</p>
+<ol>
+<li class="level1"><div class="li"> Select the object which will receive the attributes</div>
+</li>
+<li class="level1"><div class="li"> Select the text object(s) which will be attached to the above object</div>
+</li>
+<li class="level1"><div class="li"> Pick or type the shortcut for Attributes/Attach</div>
+</li>
+</ol>
+
+<p>
+ The order of the sequence of selecting the object and then the text items is important; <strong>gschem</strong> will not allow you to select the text items first and then the object. After going through the above sequence the text item will turn yellow (or the current attached attribute color) signifying that the text item is an attached attribute.<br/>
+ You cannot attach a single attribute to several different objects. You cannot attach non-text items as attributes.
+</p>
+
+</div>
+<!-- SECTION "Attach (ta)" [105059-105866] -->
+<h3><a name="detach_td" id="detach_td">Detach (td)</a></h3>
+<div class="level3">
+
+<p>
+Detach allows you to deassociate attributes from objects.<br/>
+ To deselect an object of all attributes:
+</p>
+<ol>
+<li class="level1"><div class="li"> Select the object of interest</div>
+</li>
+<li class="level1"><div class="li"> Pick or type the shortcut for Attributes/Detach</div>
+</li>
+</ol>
+
+<p>
+ All the attached attributes (even if they are not selected) will be detached from the object. This behavior is probably broken and will eventually be fixed (so that only selected attributes are detached).<br/>
+ When you detach attributes then they turn red (or the current detached attribute color). This color changes allows you to spot text which was an attribute and is now dangling (unattached).
+</p>
+
+</div>
+<!-- SECTION "Detach (td)" [105867-106473] -->
+<h3><a name="show_value_tv" id="show_value_tv">Show Value (tv)</a></h3>
+<div class="level3">
+
+<p>
+These operations allow you to control which part of the attribute string is visible. Usually you are just interested in seeing the <code>value</code> of the attribute, but there are circumstances where seeing the <code>name</code> and <code>value</code> (or maybe just the <code>name</code>) would be useful.<br/>
+ To use the options:
+</p>
+<ol>
+<li class="level1"><div class="li"> Select the attribute(s) of interest</div>
+</li>
+<li class="level1"><div class="li"> Pick or type the shortcut for Attributes/Show *</div>
+</li>
+</ol>
+
+<p>
+ The text item(s) should immediately change.<br/>
+ These operations only work on text items which are in the form <code>name=value</code>
+</p>
+
+</div>
+<!-- SECTION "Show Value (tv)" [106474-107012] -->
+<h3><a name="show_name_tn" id="show_name_tn">Show Name (tn)</a></h3>
+<div class="level3">
+
+<p>
+These operations allow you to control which part of the attribute string is visible. Usually you are just interested in seeing the <code>value</code> of the attribute, but there are circumstances where seeing the <code>name</code> and <code>value</code> (or maybe just the <code>name</code>) would be useful.<br/>
+ To use the options:
+</p>
+<ol>
+<li class="level1"><div class="li"> Select the attribute(s) of interest</div>
+</li>
+<li class="level1"><div class="li"> Pick or type the shortcut for Attributes/Show *</div>
+</li>
+</ol>
+
+<p>
+ The text item(s) should immediately change.<br/>
+ These operations only work on text items which are in the form <code>name=value</code>
+</p>
+
+</div>
+<!-- SECTION "Show Name (tn)" [107013-107550] -->
+<h3><a name="show_both_tb" id="show_both_tb">Show Both (tb)</a></h3>
+<div class="level3">
+
+<p>
+These operations allow you to control which part of the attribute string is visible. Usually you are just interested in seeing the <code>value</code> of the attribute, but there are circumstances where seeing the <code>name</code> and <code>value</code> (or maybe just the <code>name</code>) would be useful.<br/>
+ To use the options:
+</p>
+<ol>
+<li class="level1"><div class="li"> Select the attribute(s) of interest</div>
+</li>
+<li class="level1"><div class="li"> Pick or type the shortcut for Attributes/Show *</div>
+</li>
+</ol>
+
+<p>
+ The text item(s) should immediately change.<br/>
+ These operations only work on text items which are in the form <code>name=value</code>
+</p>
+
+</div>
+<!-- SECTION "Show Both (tb)" [107551-108088] -->
+<h3><a name="toggle_visibility_tt" id="toggle_visibility_tt">Toggle Visibility (tt)</a></h3>
+<div class="level3">
+
+<p>
+This operation allows you to toggle the visibility of attributes.<br/>
+ To use this option:
+</p>
+<ol>
+<li class="level1"><div class="li"> Select the text item(s) of interest</div>
+</li>
+<li class="level1"><div class="li"> Pick or type the shortcut for Attributes/Toggle Vis</div>
+</li>
+</ol>
+
+<p>
+ The text item(s) should change their visibility immediately.<br/>
+ If you make an attached attribute invisible, then you can simply select the parent object and select Toggle Vis and the attribute will be come visible (likewise any visible attributes attached to that object will become invisible).<br/>
+ If you make a free floating (unattached) attribute invisible, then the only way to make it visible (and all other invisible attributes) is to use the Edit/Show Hidden Text option.
+</p>
+
+</div>
+<!-- SECTION "Toggle Visibility (tt)" [108089-108784] -->
+<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">
+
+<p>
+ This operation allows you to find a text element in a schematic.
+</p>
+
+<p>
+To use this operation:
+</p>
+<ol>
+<li class="level1"><div class="li"> open the dialog and enter the substring you want to search for</div>
+</li>
+<li class="level1"><div class="li"> select whether you only want to search in the current page or in the whole hierarchy of a multipage schematic</div>
+</li>
+<li class="level1"><div class="li"> press the find button</div>
+</li>
+</ol>
+
+<p>
+ If the text is found in the schematic, gschem will zoom and pan to that element. Pressing the find button again will find the next matching text element. If no more text is found the dialog closes.
+</p>
+
+<p>
+<strong>Note:</strong> gschem will find hidden text elements, too. If you donâ??t see the found element, try to show the hidden text.
+</p>
+
+</div>
+<!-- SECTION "Find Specific Text... (t shift-f)" [108785-109445] -->
+<h3><a name="hide_specific_text..._th" id="hide_specific_text..._th">Hide Specific Text... (th)</a></h3>
+<div class="level3">
+
+<p>
+ This operation allows you to hide text elements.
+</p>
+
+<p>
+To use this operation:
+</p>
+<ol>
+<li class="level1"><div class="li"> open the dialog and enter your text string</div>
+</li>
+<li class="level1"><div class="li"> press the apply button</div>
+</li>
+</ol>
+
+<p>
+ gschem will hide all text elements that start with the given search string.
+</p>
+
+<p>
+This operation is useful if you like to hide pintype and pinseq attributes when creating symbols.
+</p>
+
+</div>
+<!-- SECTION "Hide Specific Text... (th)" [109446-109807] -->
+<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">
+
+<p>
+ This operation allows you to show hidden text elements.
+</p>
+
+<p>
+To use this operation:
+</p>
+<ol>
+<li class="level1"><div class="li"> open the dialog and enter your text string</div>
+</li>
+<li class="level1"><div class="li"> press the apply button</div>
+</li>
+</ol>
+
+<p>
+ gschem will unhide all hidden text elements that starts with the given search string.
+</p>
+
+<p>
+This operation is useful if you like to see only one specific attribute in the whole schematic (the footprint attribute for example). Use this operation together with the <em>Hide Specific Text</em> operation.
+</p>
+
+</div>
+<!-- SECTION "Show Specific Text... (t shift-h)" [109808-110299] -->
+<h3><a name="autonumber_text..._tu" id="autonumber_text..._tu">Autonumber Text... (tu)</a></h3>
+<div class="level3">
+
+<p>
+ This operation allows you to renumber text elements in your schematics and symbols.
+</p>
+
+<p>
+You can use it to:
+</p>
+<ul>
+<li class="level1"><div class="li"> renumber pinseq and pinnumber attributes when creating symbols</div>
+</li>
+<li class="level1"><div class="li"> renumber components in a schematic (the refdes attribute)</div>
+</li>
+<li class="level1"><div class="li"> renumber netnames to create address and data busses</div>
+</li>
+</ul>
+
+<p>
+ To use that operation:
+</p>
+<ol>
+<li class="level1"><div class="li"> select or enter the text elements you like to renumber in the <em>search for</em> entry. searchtext with a "?" at the end will match trailing "?" and trailing numbers in the text elements you are searching for. searchtext with a â??*â?? at the end will match the given searchtext, followed by arbitrary text and followed by a trailing "?" or trailing numbers.</div>
+</li>
+<li class="level1"><div class="li"> the <em>autonumber text in</em> option specifies where to search for the given searchstring.</div>
+</li>
+<li class="level1"><div class="li"> the <em>skip numbers found in</em> option specifies in which region you donâ??t want have duplicate numbers. <strong>Example:</strong> If you renumber your components you usually want uniq numbers on a page or even uniq number in the whole hierarchy of a multipage schematic. If you renumber netnames of a bus you usually want to apply the new numbers only to selected net elements. Thus you can have multiple equal netnames on a schematic sheet.</div>
+</li>
+<li class="level1"><div class="li"> the <em>overwrite existing numbers</em> option specifies whether you only want to number unnumbered elements or if you like to renumber elements too.</div>
+</li>
+<li class="level1"><div class="li"> The <em>starting number</em> entry allows you to specify the start number you like. It is common to number each schematic sheet starting with numbers like 100, 200 and so on. For bus netnames you may need numbers starting at 8, 16.</div>
+</li>
+<li class="level1"><div class="li"> The <em>sort order</em> tells in which direction you like to number your elements. For components you usually use the <em>diagonal</em>, the <em>top to bottom</em> or the <em>left to right</em> option. For bus netnames you may need <em>right to left</em> and <em>bottom to top</em> numbering. The <em>file order</em> means that the found text elements are not sorted before renumbering them. The fileorder is usually the order you have placed the objects to your sheet.</div>
+</li>
+<li class="level1"><div class="li"> the <em>remove numbers</em> options is a special option. It removes all numbers from the text elements you have selected in the <em>Scope</em> section of the dialog.</div>
+</li>
+<li class="level1"><div class="li"> the <em>automatic slotting</em> option is the second special option. When renumbering components it will add the slot attribute to slotted components like logik gates.</div>
+</li>
+</ol>
+
+<p>
+ Pressing the apply button will start the autonumbering action.
+</p>
+
+</div>
+<!-- SECTION "Autonumber Text... (tu)" [110300-112737] -->
+<h2><a name="options" id="options">Options</a></h2>
+<div class="level2">
+
+</div>
+<!-- SECTION "Options" [112738-112758] -->
+<h3><a name="text_size..._ot" id="text_size..._ot">Text Size... (ot)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Options | Text Size…</strong> pops up a dialog box which allows you to specify the text size of all text (including attributes placed with the Add/Attribute… dialog box).<br/>
+ The text size is in points (1/72â??). The default text size is 10 point text. The smallest text size is 2 points.
+</p>
+
+</div>
+<!-- SECTION "Text Size... (ot)" [112759-113071] -->
+<h3><a name="toggle_grid_on_off_og" id="toggle_grid_on_off_og">Toggle Grid On/Off (og)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Options | Toggle Grid On/Off</strong> toggles the visible grid.
+</p>
+
+</div>
+<!-- SECTION "Toggle Grid On/Off (og)" [113072-113165] -->
+<h3><a name="toggle_snap_on_off_os" id="toggle_snap_on_off_os">Toggle Snap On/Off (os)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Options | Toggle Snap On/Off</strong> toggles the snap. Be very careful using this. Connections between pins and nets (and nets to nets) depends on being exactly connected. Turning of the grid will almost guarantee that nets/pins do not connect.<br/>
+ Before you translate a symbol using Edit/Symbol Translate, make sure the snap is on.<br/>
+ When snap mode is off, the text â??Snap Offâ?? will appear in the lower, righthand corner.
+</p>
+
+</div>
+<!-- SECTION "Toggle Snap On/Off (os)" [113166-113617] -->
+<h3><a name="snap_grid_spacing..._os" id="snap_grid_spacing..._os">Snap Grid Spacing... (oS)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Options | Snap Grid Spacing…</strong> brings up a dialog box which allows you to change the snap grid spacing (not the grid spacing). The units for this spacing are mils.<br/>
+ Before you translate a symbol using Edit/Symbol Translate, make sure this spacing is set to 100.
+</p>
+
+</div>
+<!-- SECTION "Snap Grid Spacing... (oS)" [113618-113921] -->
+<h3><a name="toggle_outline_box_oa" id="toggle_outline_box_oa">Toggle Outline/Box (oa)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Options | Toggle Outline/Box</strong> toggles between drawing the outline of the current selection or just drawing a box when doing moves/copies/component and text places. The outline mode looks better, but tends to be significantly slower than using the box (bounding box) mode.
+</p>
+
+</div>
+<!-- SECTION "Toggle Outline/Box (oa)" [113922-114231] -->
+<h3><a name="toggle_net_rubberband_or" id="toggle_net_rubberband_or">Toggle Net/Rubberband (or)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Options | Toggle Net/Rubberband</strong> …..????
+</p>
+
+</div>
+<!-- SECTION "Toggle Net/Rubberband (or)" [114232-114315] -->
+<h3><a name="show_log_window_ol" id="show_log_window_ol">Show Log Window (ol)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Options | Show Log Window</strong> displays the log window if it has been closed or disabled from being displayed when you start up <strong>gschem</strong>.
+</p>
+
+</div>
+<!-- SECTION "Show Log Window (ol)" [114316-114486] -->
+<h3><a name="show_coord_window..._oc" id="show_coord_window..._oc">Show Coord Window... (oc)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Options | Show Coord Window…</strong> displays a pop-up window that displays the coordinates of the mouse pointer on the schematic. Useful for accurately placing objects.
+</p>
+
+</div>
+<!-- SECTION "Show Coord Window... (oc)" [114487-114691] -->
+<h2><a name="help" id="help">Help</a></h2>
+<div class="level2">
+
+</div>
+<!-- SECTION "Help" [114692-114709] -->
+<h3><a name="about..._ha" id="about..._ha">About... (ha)</a></h3>
+<div class="level3">
+
+<p>
+Every <acronym title="Graphical User Interface">GUI</acronym> application needs an <strong>Help | About…</strong> feature, to display:
+</p>
+<ul>
+<li class="level1"><div class="li"> The applicationâ??s name.</div>
+</li>
+<li class="level1"><div class="li"> The version of the software.</div>
+</li>
+<li class="level1"><div class="li"> The authorâ??s name(s) and how to contact.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "About... (ha)" [114710-114912] -->
+<h3><a name="manual..._hm" id="manual..._hm">Manual... (hm)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Help | Manual…</strong> brings up the â??gEDA/gaf Documentionâ?? web-page installed on this computer. Very useful for accessing the various documentation available for the gEDA/gaf applications.
+</p>
+
+</div>
+<!-- SECTION "Manual... (hm)" [114913-115126] -->
+<h3><a name="hotkeys..._hh" id="hotkeys..._hh">Hotkeys... (hh)</a></h3>
+<div class="level3">
+
+<p>
+<strong>Help | Hotkeys…</strong> lists the current hotkeys (a.k.a., shortcuts, a.k.a., keyboard accellerators).
+</p>
+
+</div>
+<!-- SECTION "Hotkeys... (hh)" [115127-115254] -->
+<h3><a name="component..._ho" id="component..._ho">Component... (Ho)</a></h3>
+<div class="level3">
+
+<p>
+If you select a component on the schematic, and select <strong>Help | Component…</strong>, <strong>gschem</strong> uses the gschemdoc script to do its best job finding some documentation appropriate for the component:
+</p>
+<ul>
+<li class="level1"><div class="li"> If the componentâ??s symbol included the <code>documentation=documentation_locator</code> attribute, this <acronym title="Uniform Resource Identifier">URI</acronym> is used to retreive the documentation. If the full <acronym title="Uniform Resource Identifier">URI</acronym> is given, the <acronym title="Uniform Resource Identifier">URI</acronym> on the internet is retrieved. If the <acronym title="Uniform Resource Identifier">URI</acronym> is not fully qualified, it is considered to be local to this computer, and is searched for and displayed.</div>
+</li>
+<li class="level1"><div class="li"> If the componentâ??s symbol does not include the <code>documentation=documentation_locator</code> attribute, a Google search is performed for <acronym title="Portable Document Format">PDF</acronym> documents, based on the <code>device=</code> attribute, the <code>value=</code> attribute, and the symbol basename.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Component... (Ho)" [115255-116037] -->
+<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">
+
+<p>
+A short discussion of Light Symbol Libraries as the default for <strong>gschem</strong>, and the option to build your own Heavy Symbol Libraries.
+</p>
+
+</div>
+<!-- SECTION "Appendix A -- Heavy vs Light Symbol Libraries" [116038-116231] -->
+<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">
+
+<p>
+To be supplied…
+</p>
+
+</div>
+<!-- SECTION "Appendix B -- Printing Schematics and Symbols" [116232-116310] -->
+<h1><a name="appendix_c_--_writing_guile_scripts" id="appendix_c_--_writing_guile_scripts">Appendix C -- Writing guile Scripts</a></h1>
+<div class="level1">
+
+<p>
+To be supplied…
+</p>
+
+</div>
+<!-- SECTION "Appendix C -- Writing guile Scripts" [116311-116379] -->
+<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">
+
+<p>
+<strong>gschem</strong> is used for two primary design workflows:
+</p>
+<ul>
+<li class="level1"><div class="li"> Circuit design intended for production of Printed Circuit Boards (PCBs).</div>
+</li>
+<li class="level1"><div class="li"> Circuit design intended for simulation.</div>
+</li>
+</ul>
+
+<p>
+ The following guidelines will assist you in developing quality designs intended for use by applications that support the creation of Printed Circuit Boards:
+</p>
+<ul>
+<li class="level1"><div class="li"> <span class="hilited">To be supplied…</span></div>
+</li>
+</ul>
+
+<p>
+ The following on-line tutorials are an excellent method for the beginner to learn the gEDA Tools Suite design workflow resulting in a PCB:
+</p>
+<ul>
+<li class="level1"><div class="li"> <a href="http://www.geda.seul.org/docs/current/tutorials/gsch2pcb/gschem-warmup.html"; class="urlextern" title="http://www.geda.seul.org/docs/current/tutorials/gsch2pcb/gschem-warmup.html"; rel="nofollow">Bill Wilson's gschem warmup</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="http://www.geda.seul.org/docs/current/tutorials/gsch2pcb/tutorial.html"; class="urlextern" title="http://www.geda.seul.org/docs/current/tutorials/gsch2pcb/tutorial.html"; rel="nofollow">Bill Wilson's gsch2pcb tutorial</a></div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Appendix D -- I Want To Build A Printed Circuit Board" [116380-117169] -->
+<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">
+
+<p>
+<strong>gschem</strong> is used for two primary design workflows:
+</p>
+<ul>
+<li class="level1"><div class="li"> Circuit design intended for production of Printed Circuit Boards.</div>
+</li>
+<li class="level1"><div class="li"> Circuit design intended for simulation.</div>
+</li>
+</ul>
+
+<p>
+ The following guidelines will assist you in developing quality designs intended for simulation:
+</p>
+<ul>
+<li class="level1"><div class="li"> Discuss attributes appropriate for a SPICE model, and how these differ from attributes appropriate for a PCB.</div>
+</li>
+<li class="level1"><div class="li"> <span class="hilited">To be supplied…</span></div>
+</li>
+</ul>
+
+<p>
+ The following on-line tutorials are an excellent method for the beginner to learn the gEDA Tools Suite design workflow resulting in a SPICE simulation:
+</p>
+<ul>
+<li class="level1"><div class="li"> <a href="http://www.brorson.com/gEDA/SPICE/t1.html"; class="urlextern" title="http://www.brorson.com/gEDA/SPICE/t1.html"; rel="nofollow">"Circuit simulation using gEDA and SPICE -- HOWTO" by Stuart Brorson</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="http://www-mdp.eng.cam.ac.uk/urop05/files/gedalib/starting_gEDA.pdf"; class="urlextern" title="http://www-mdp.eng.cam.ac.uk/urop05/files/gedalib/starting_gEDA.pdf"; rel="nofollow">Starting with gEDA at the Cambridge University Engineering Department</a></div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Appendix E -- I Want To Simulate My Design" [117170-118049] -->
+<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">
+
+<p>
+As installed, the <strong>gschemdoc</strong> utility script is used by <strong>gschem</strong> to:
+</p>
+<ul>
+<li class="level1"><div class="li"> Display the â??gEDA/gaf Documentationâ?? (i.e., <strong>Help | Manual…</strong>)</div>
+</li>
+<li class="level1"><div class="li"> Display component documentation (i.e., <strong>Help | Component…</strong>)</div>
+</li>
+</ul>
+
+<p>
+ The list of application launchers that <strong>gschemdoc</strong> uses are defined in the {binary-install-path}/bin/gschemdoc file: <pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">#
+# these may be changed to suit local preferences
+#
+CANDIDATE_BROWSER="galeon mozilla phoenix netscape netscape-navigator opera firefox konqueror"
+CANDIDATE_PDFREADER="xpdf acroread ggv gv"
+CANDIDATE_LOCATE="slocate locate"</font></pre>
+</p>
+
+<p>
+To select a different application launcher, simply edit the {binary-install-path}/bin/gschemdoc file, find the above lines, and move your favorite application to the beginning of the list. For example, to use <strong>firefox</strong> as your preferred browser, move it to the beginning of the <strong>CANDIDATE_BROWSER=</strong> list, to use <strong>acroread</strong> (Adobeâ??s Acrobat Reader) as your preferred <acronym title="Portable Document Format">PDF</acronym> reader, move it to the beginning of the <strong>CANDIDATE_PDFREADER=</strong> list, and to use <strong>locate</strong> as your preferred filesystem search utility, move it to the beginning of the <strong>CANDIDATE_LOCATE=</strong> list.
+</p>
+
+</div>
+<!-- SECTION "Appendix F -- Change gschemdoc User-Defined Preferences" [118050-119266] -->
+<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">
+
+<p>
+To be supplied…
+</p>
+
+</div>
+<!-- SECTION "Appendix G -- Breaking a Large Symbol Into Smaller Symbols" [119267-119358] -->
+<h1><a name="appendix_h_--_definition_of_terms" id="appendix_h_--_definition_of_terms">Appendix H -- Definition of Terms</a></h1>
+<div class="level1">
+
+<p>
+Some terms used in the art of schematic capture:</p>
+<dl>
+<dt><span class='term'> <strong>attribute</strong></span></dt>
+<dd>A text item which is in the form <code>name=value</code>. It can be either unattached or attached.</dd>
+<dt><span class='term'> <strong>buffer</strong></span></dt>
+<dd>…</dd>
+<dt><span class='term'> <strong>component</strong></span></dt>
+<dd>Also know as <strong>part</strong>. The equivalent of an [electronics] device, as one may place on a printed circuit board. Components are instances of a <strong>symbol</strong> placed on a schematic.</dd>
+<dt><span class='term'> <strong>device</strong></span></dt>
+<dd>Also known as â??packageâ??. The equivalent of an [electronics] device, as one may place on a printed circuit board.</dd>
+<dt><span class='term'> <strong>dialog box</strong></span></dt>
+<dd>…</dd>
+<dt><span class='term'> <strong>embedded component</strong></span></dt>
+<dd>A component whose definition is saved as part of the schematicâ??s file.</dd>
+<dt><span class='term'> <strong>footprint</strong></span></dt>
+<dd>Also known as a <strong>land pattern</strong>. The surface space occupied by a <strong>component</strong>/<strong>package</strong>/<strong>part</strong>.</dd>
+<dt><span class='term'> <strong>gEDA/gaf</strong></span></dt>
+<dd><strong>gschem</strong> is a component of the gEDA/gaf set of tools, which tend to integrate together in the development and maintenance of schematics and symbols. The term â??gafâ?? stands for â??<em class="u">g</em>EDA <em class="u">a</em>nd <em class="u">f</em>riendsâ??).</dd>
+<dt><span class='term'> <strong>grip</strong></span></dt>
+<dd>…</dd>
+<dt><span class='term'> <strong>guile</strong></span></dt>
+<dd><a href="http://www.gnu.org/software/guile/"; class="urlextern" title="http://www.gnu.org/software/guile/"; rel="nofollow">GNU Guile</a> is an interpreter for Scheme, a version of Lisp.</dd>
+<dt><span class='term'> <strong>HDL</strong></span></dt>
+<dd>Hardware Description Language (e.g., VHDL, Verilog, etc.). Used to simulate or document a device.</dd>
+<dt><span class='term'> <strong>hierarchical</strong></span></dt>
+<dd>The concept that designs can contain nested levels of schematics, so that all the circuit doesnâ??t need to be placed on a single sheet.</dd>
+<dt><span class='term'> <strong>land pattern</strong></span></dt>
+<dd>Also known as a <strong>footprint</strong>. The surface space occupied by a structure or device.</dd>
+<dt><span class='term'> <strong>library</strong></span></dt>
+<dd>A collection of symbols.</dd>
+<dt><span class='term'> <strong>line</strong></span></dt>
+<dd>A straight drawing element, connecting two points. On the schematic it has no electrical significance. In a symbol, a line is part of the symbolâ??s graphic elements.</dd>
+<dt><span class='term'> <strong>model</strong></span></dt>
+<dd>A description of how a device behaves. Most often this is a SPICE model. The model is defined in <strong>gschem</strong>, but used in subsequent applications such as <strong>ngspice</strong>, <strong>gnucap</strong>, etc.</dd>
+<dt><span class='term'> <strong>net</strong></span></dt>
+<dd>A net connects two or more pins on a schematic, and is made up of segments. The netâ??s equivalent is a â??wireâ?? or â??traceâ?? on the printed circuit board.</dd>
+<dt><span class='term'> <strong>object</strong></span></dt>
+<dd>A line, circle, pin, net, box, bus, text/attribute, or picture.</dd>
+<dt><span class='term'> <strong>package</strong></span></dt>
+<dd>Also known as <strong>device</strong>. The equivalent of an [electronics] device, as one may place on a printed circuit board.</dd>
+<dt><span class='term'> <strong>page</strong></span></dt>
+<dd>Also known as a schematicâ??s <strong>sheet</strong>.</dd>
+<dt><span class='term'> <strong>part</strong></span></dt>
+<dd> Also know as <strong>component</strong>. The equivalent of an [electronics] device, as one may place on a printed circuit board.</dd>
+<dt><span class='term'> <strong>project</strong></span></dt>
+<dd>A collection of schematics, custom symbols, models, documentation, etc.</dd>
+<dt><span class='term'> <strong>segment</strong></span></dt>
+<dd>Part of a net. A segment has two end-points, or â??gripsâ??.</dd>
+<dt><span class='term'> <strong>schematic</strong></span></dt>
+<dd>A <strong>page</strong>/<strong>sheet</strong> with electronics symbols, text, and drawing elements (i.e., lines, circles, boxes, etc.) representing a diagram of an electrical or mechanical system.</dd>
+<dt><span class='term'> <strong>series</strong></span></dt>
+<dd>A collection of schematics which share a common basename (e.g., schematic_1.sch, schematic_2.sch, schematic_3.sch, etc.). The series basename ties schematics together.</dd>
+<dt><span class='term'> <strong>slotted device</strong></span></dt>
+<dd>Also known as a <strong>slotted package</strong>. A physical [electronics] device consisting of multiple identical components (e.g., the 7400 quad NAND device consists of 4 identical NAND gates).</dd>
+<dt><span class='term'> <strong>source</strong></span></dt>
+<dd>A schematic, HDL code, or model which implements, describes, or documents some aspect of the project.</dd>
+<dt><span class='term'> <strong>symbol</strong></span></dt>
+<dd>A collection of <strong>objects</strong>. The objects may have <strong>attributes</strong> attatched (i.e., associated) with them. There may also be <strong>attributes</strong> attached (i.e., associated) to the <strong>symbol</strong> itself (i.e., not specifically associated with an object).</dd>
+<dt><span class='term'> <strong>sheet</strong></span></dt>
+<dd>Also known as a schematicâ??s <strong>page</strong>.</dd>
+<dt><span class='term'> <strong>trace</strong></span></dt>
+<dd>The equivalent of a wire on a printed circuit board.</dd>
+<dt><span class='term'> <strong>window</strong></span></dt>
+<dd>…</dd>
+<dt><span class='term'> <strong>workflow</strong></span></dt>
+<dd>The process of designing. Usually includes continuous review and re-design, until it works. In the gEDA Tools Suite design workflow, multiple applications are used. One application typically is followed by another. The flow of data collected and how this data effects the design is considered the workflow.</dd>
+</dl>
+<p>~~DISCUSSION~~
+</p>
+
+</div>
+<!-- SECTION "Appendix H -- Definition of Terms" [119359-] --></body>
+</html>
diff --git a/docs/wiki/geda-gschem_warmup.html b/docs/wiki/geda-gschem_warmup.html
new file mode 100644
index 0000000..b572695
--- /dev/null
+++ b/docs/wiki/geda-gschem_warmup.html
@@ -0,0 +1,99 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="gschem_warmup_for_beginners" id="gschem_warmup_for_beginners">gschem Warmup for Beginners</a></h1>
+<div class="level1">
+
+<p>
+ You need to become familiar with doing a few things in <em><strong>gschem</strong></em>, so just run <em><strong>gschem</strong></em> and start playing around:
+</p>
+
+<p>
+You get an initial blank page with menus and a toolbar at the top. As you select operations from the menus, notice that there are usually keyboard shortcuts which can alternatively be used to access the menu functions.
+</p>
+
+<p>
+When drawing a schematic, Itâ??s a good idea to always start by setting some schematic boundaries to draw within, so we will do this by adding a title-block. I find that using a B sized title-block lets my schematics print at a nice size on letter sized paper:
+</p>
+<ul>
+<li class="level1"><div class="li"> Bring up the <strong>Select Component</strong> window by selecting from the menu <strong>Add→Component</strong> or hit keyboard shortcut <strong>i</strong>. Or you could click the add component icon on the toobar (<a href="media/geda/warmup_add_component.png" class="media" target="_blank" title="geda:warmup_add_component.png"><img src="media/geda/warmup_add_component.png" class="media" alt="" /></a>).</div>
+</li>
+<li class="level1"><div class="li"> In the <strong>Libraries</strong> list, select <strong>title-block</strong>.</div>
+</li>
+<li class="level1"><div class="li"> Under the <strong>Components list</strong>, select <strong>title-B.sym</strong>.</div>
+</li>
+<li class="level1"><div class="li"> Move the mouse onto the <em><strong>gschem</strong></em> drawing area and place the title-block symbol by clicking the left mouse button. Then click the right mouse button to abort adding more title-block symbols.</div>
+</li>
+</ul>
+
+<p>
+ <a href="media/geda/warmup_gschem01.png" class="media" target="_blank" title="geda:warmup_gschem01.png"><img src="media/geda/warmup_gschem01.png" class="media" alt="" /></a>
+</p>
+<ul>
+<li class="level1"><div class="li"> With the mouse in the <em><strong>gschem</strong></em> drawing area, hit the keys <strong>ve</strong> (or select from menu <strong>View→Zoom Extents</strong>) to zoom the view to the title-block symbol extents.</div>
+</li>
+<li class="level1"><div class="li"> Back in the select components window, (bring it up again if you closed it), select the <strong>analog</strong> library and then select the component <strong>resistor-1.sym</strong> and place a couple of resistors on the schematic with the left mouse button. Notice that as you place each one it is an orange color and that indicates it is selected.</div>
+</li>
+<li class="level1"><div class="li"> Zoom in (keyboard shortcut <strong>z</strong>) and zoom out (keyboard shortcut <strong>SHIFT z</strong>) in the area where you placed the resistors. If you get lost, zoom back to extents with <strong>ve</strong>. Notice that as you zoom in or out the viewable area centers around the mouse cursor.</div>
+</li>
+<li class="level1"><div class="li"> Alternate left clicking on both resistors to select them, but notice that if you donâ??t hit the resistor just right, the title-block is selected instead. We really donâ??t want to ever select the title-block again, so we can lock it to prevent its irritating selection: click so the title-block IS selected, then select <strong>Edit→Lock</strong>. Now itâ??s easier to select the resistors as we like.</div>
+</li>
+<li class="level1"><div class="li"> Move the resistors around with the middle mouse button.</div>
+</li>
+<li class="level1"><div class="li"> Select a resistor and then rotate with the <strong>er</strong> keys or the <strong>Edit→Rotate 90 Mode</strong>.</div>
+</li>
+<li class="level1"><div class="li"> Move the resistors relatively close together and then zoom in on them.</div>
+</li>
+<li class="level1"><div class="li"> Place the mouse on one of the resistor pins and hit the <strong>n</strong> key to start adding a net. Move the mouse to a pin on the other resistor and left click to attach the net to the pin. Right click to abort adding this net but notice that if you left click again you will start adding another net.</div>
+</li>
+</ul>
+
+<p>
+ <a href="media/geda/warmup_gschem02.png" class="media" target="_blank" title="geda:warmup_gschem02.png"><img src="media/geda/warmup_gschem02.png" class="media" alt="" /></a>
+</p>
+<ul>
+<li class="level1"><div class="li"> Look at the toolbar and see that your mode has switched to adding nets. Before you can change resistor selections again, you will have to re-enter select mode with the <strong>s</strong> key or by clicking the select toolbar icon or by using the menu <strong>Edit→Select Mode</strong>. But if you try to move a resistor with the middle mouse button, you can do it and you will automatically re-enter select mode. You will have to play with doing things to get used to the <em><strong>gschem</strong></em> modes.</div>
+</li>
+<li class="level1"><div class="li"> If when you added the net between the resistors you get something that looks like this:</div>
+</li>
+</ul>
+
+<p>
+ <a href="media/geda/warmup_gschem03.png" class="media" target="_blank" title="geda:warmup_gschem03.png"><img src="media/geda/warmup_gschem03.png" class="media" alt="" /></a>
+</p>
+
+<p>
+it means you missed the pin on the right resistor. Look closely and youâ??ll see the tip of the pin is red and you must start and stop nets with the mouse on this red spot to make a connection to the pin.
+</p>
+<ul>
+<li class="level1"><div class="li"> Select the net between the resistors and delete it with the <strong>Delete</strong> key.</div>
+</li>
+<li class="level1"><div class="li"> Select a resistor and hit the <strong>ee</strong> keys. This will pop up the attribute editing window for the resistor. Here you can change existing attribute values or add new attributes with values to the resistor. Practice well with adding attributes and changing attribute values because you will need to be very familiar with managing attributes when using <em><strong>gschem</strong></em>.</div>
+</li>
+</ul>
+
+<p>
+ Now go back to <a href="geda-gsch2pcb_tutorial.html" class="wikilink1" title="geda-gsch2pcb_tutorial.html">the tutorial</a> and try working through the simple example there. If you encounter steps that arenâ??t clear, look through the <em><strong>gschem</strong></em> user documentation and attributes documentation on the <a href="geda-gschem_ug.html" class="wikilink1" title="geda-gschem_ug.html">gschem Documentation</a> page.
+</p>
+<hr />
+
+<p>
+tutorial by Bill Wilson (bill–at–gkrellm.net)
+</p>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-gsymcheck_mp.html b/docs/wiki/geda-gsymcheck_mp.html
new file mode 100644
index 0000000..4324138
--- /dev/null
+++ b/docs/wiki/geda-gsymcheck_mp.html
@@ -0,0 +1,87 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="gsymcheck_man-page" id="gsymcheck_man-page">gsymcheck man-page</a></h1>
+<div class="level1">
+<pre class="code">gsymcheck(1) 20031231 gsymcheck(1)
+
+
+
+NAME
+ gsymcheck - gEDA/gaf Symbol Checker
+
+SYNOPSIS
+ gnetlist [-h] [-v] [-q] symbol1 [... symbolN]
+
+DESCRIPTION
+ gsymcheck is a symbol checker for gEDA. Eventually there will be a
+ list of checks performed on the symbols listed here.
+
+
+OPTIONS
+ gsymcheck accepts the following options:
+
+ -q Quiet mode on. This mode turns off all warnings/notes/mes-
+ sages. (optional)
+
+ -v Verbose mode 1. This mode will show all error messages
+ (optional)
+
+ -vv Verbose mode 2. This mode will show all error and warning mes-
+ sages (optional)
+
+ -vvv Verbose mode 2. This mode will show all error, warning, and
+ info messages (optional)
+
+ -h Usage summary / gsymcheck help
+
+ symbol1 [... symbolN]
+ At least one symbol file must be specified. If multiple sym-
+ bols are specified then they are sequentially read in and
+ checked. It is important that the schematic(s) follow all the
+ options (ie last).
+
+
+EXAMPLES
+ Examples to be listed here eventually
+
+
+ENVIRONMENT
+ No environment variables are used.
+
+
+AUTHOR
+ Ales Hvezda and many others
+
+
+SEE ALSO
+ gschem(1), gnetlist(1)
+
+COPYRIGHT
+ Copyright © 1999-2004 Ales Hvezda
+
+ This document can be freely redistributed according to the terms of the
+ GNU General Public License version 2.0
+
+
+
+
+Version December 31st, 2003 gsymcheck(1)
+</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-gtkwave_lxt2miner_mp.html b/docs/wiki/geda-gtkwave_lxt2miner_mp.html
new file mode 100644
index 0000000..2015f50
--- /dev/null
+++ b/docs/wiki/geda-gtkwave_lxt2miner_mp.html
@@ -0,0 +1,79 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="data_mining_of_lxt2_files_lxt2miner" id="data_mining_of_lxt2_files_lxt2miner">Data mining of LXT2 files (lxt2miner)</a></h1>
+<div class="level1">
+<pre class="code">LXT2MINER(1) Dumpfile Data Mining LXT2MINER(1)
+
+
+
+NAME
+ lxt2miner - Data mining of LXT2 files
+
+SYNTAX
+ lxt2miner [option]... [LXT2FILE]
+
+DESCRIPTION
+ Mines LXT2 files for specific data values and generates gtkwave save
+ files to stdout for future reload.
+
+OPTIONS
+ -d,--dumpfile <filename>
+ Specify LXT2 input dumpfile.
+
+ -m,--match <filename>
+ Specifies "bitwise" match data (binary, real, string)
+
+ -x,--hex <value>
+ Specifies hexadecimal match data that will automatically be con-
+ verted to binary for searches
+
+ -n,--namesonly
+ Indicates that only facnames should be printed in a gtkwave
+ savefile compatible format. By doing this, the file can be used
+ to specify which traces are to be imported into gtkwave.
+
+ -h,--help
+ Show help screen.
+
+EXAMPLES
+ lxt2miner dumpfile.lxt2 --match 20470000 -n
+
+ This attempts to match the hex value 20470000 across all facilities and
+ when the value is encountered, the facname only is printed to stdout in
+ order to generate a gtkwave compatible save file.
+
+LIMITATIONS
+ lxt2miner only prints the first time a value is encountered for a spe-
+ cific net. This is done in order to cut down on the size of output
+ files and to aid in following data such as addresses through a simula-
+ tion model.
+
+
+AUTHORS
+ Anthony Bybell <bybell@xxxxxxxxx>
+
+SEE ALSO
+ vztminer(1) vzt2vcd(1) lxt2vcd(1) vcd2lxt2(1) gtkwave(1)
+
+
+
+Anthony Bybell 1.3.64 LXT2MINER(1)
+</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-gtkwave_lxt2vcd_mp.html b/docs/wiki/geda-gtkwave_lxt2vcd_mp.html
new file mode 100644
index 0000000..0ea03ad
--- /dev/null
+++ b/docs/wiki/geda-gtkwave_lxt2vcd_mp.html
@@ -0,0 +1,60 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="coverts_lxt2_files_to_vcd_lxt2vcd" id="coverts_lxt2_files_to_vcd_lxt2vcd">Coverts LXT2 files to VCD (lxt2vcd)</a></h1>
+<div class="level1">
+<pre class="code">LXT2VCD(1) Filetype Conversion LXT2VCD(1)
+
+
+
+NAME
+ lxt2vcd - Coverts LXT2 files to VCD
+
+SYNTAX
+ lxt2vcd <filename>
+
+DESCRIPTION
+ Converts LXT2 files to VCD files on stdout. Note that "regular" LXT2
+ files will convert to VCD files with monotonically increasing time val-
+ ues. LXT2 files which are dumped with the "partial" option (to speed
+ up access in wave viewers) will dump with monotonically increasing time
+ values per 2k block of nets. This may be fixed in later versions of
+ lxt2vcd.
+
+EXAMPLES
+ To run this program the standard way type:
+
+ lxt2vcd filename.lxt
+ The VCD conversion is emitted to stdout.
+
+LIMITATIONS
+ lxt2vcd does not re-create glitches as these are coalesced together
+ into one value change during the writing of the LXT2 file.
+
+
+AUTHORS
+ Anthony Bybell <bybell@xxxxxxxxx>
+
+SEE ALSO
+ vcd2lxt2(1) vcd2lxt(1) gtkwave(1)
+
+
+
+Anthony Bybell 1.3.34 LXT2VCD(1)</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-gtkwave_mp.html b/docs/wiki/geda-gtkwave_mp.html
new file mode 100644
index 0000000..74c42c8
--- /dev/null
+++ b/docs/wiki/geda-gtkwave_mp.html
@@ -0,0 +1,123 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="visualization_tool_for_vcd_lxt_and_vzt_files_gtkwave" id="visualization_tool_for_vcd_lxt_and_vzt_files_gtkwave">Visualization tool for VCD, LXT, and VZT files (gtkwave)</a></h1>
+<div class="level1">
+<pre class="code">GTKWAVE(1) Simulation Wave Viewer GTKWAVE(1)
+
+
+
+NAME
+ gtkwave - Visualization tool for VCD, LXT, and VZT files
+
+SYNTAX
+ gtkwave [option]... [DUMPFILE] [SAVEFILE] [RCFILE]
+
+
+DESCRIPTION
+ Visualization tool for VCD, LXT, LXT2, and VZT. VCD is an industry
+ standard simulation dump format. LXT, LXT2, and VZT have been designed
+ specifically for use with gtkwave. Native dumpers exist in Icarus Ver-
+ ilog for the LXT formats so conversion with vcd2lxt(1) or vcd2lxt2(1)
+ is not necessary to take direct advantage of LXT with that simulator.
+ AET2 files can also be processed provided that libae2rw is available
+ but this is only of interest to people who use IBM EDA toolsets.
+
+OPTIONS
+ -n,--nocli <directory name>
+ Use file requester for dumpfile name
+
+ -f,--dump <filename>
+ Specify dumpfile name.
+
+ -r,--rcfile <filename>
+ Specify override .gtkwaverc filename.
+
+ -i,--indirect <filename>
+ Specify indirect facs file name. The file contains a series of
+ regular expressions used to limit what signals can be browsed.
+ Signal names which match any of the regular expressions will be
+ viewable. Typically, indirect files are used to reduce memory
+ requirements for extremely large models containing millions of
+ facilities or to strip out top-level hierarchy clutter from
+ BugSpray models. This feature is only available with the AET2
+ loader.
+
+ -l,--logfile <filename>
+ Specify simulation logfile name. Multiple logfiles may be spec-
+ ified by preceeding each with the command flag. By selecting
+ the numbers in the text widget, the marker will immediately zoom
+ to the specific time value.
+
+ -d,--defaultskip
+ If there is not a .gtkwaverc file in the home directory or cur-
+ rent directory and it is not explicitly specified on the command
+ line, when this option is enabled, do not use an implicit con-
+ figuration file and instead default to the old "whitescreen"
+ behavior.
+
+ -s,--start <time>
+ Specify start time for LXT2/VZT block skip.
+
+ -e,--end <time>
+ Specify end time for LXT2/VZT block skip.
+
+ -c,--cpu <numcpus>
+ Specify number of CPUs available for parallelizable ops (e.g.,
+ block prefetching on VZT reads).
+
+ -v,--vcd
+ Use stdin as a VCD dumpfile.
+
+ -V,--version
+ Display version banner then exit.
+
+ -h,--help
+ Display help then exit.
+
+ -x,--exit
+ Exit after loading trace (for loader benchmarking).
+
+FILES
+ ~/.gtkwaverc
+
+
+EXAMPLES
+ To run this program the standard way type:
+ gtkwave dumpfile.vcd
+
+ Alternatively you can run it with a save file as:
+ gtkwave dumpfile.vcd dumpfile.sav
+
+ Command line options are not necessary for representing the dumpfile,
+ savefile, and rcfile names. They are merely provided to allow specify-
+ ing them out of order. Note that on non-glibc systems, the long com-
+ mand line options will not be available and that the short ones will
+ have to be used instead.
+
+AUTHORS
+ Anthony Bybell <bybell@xxxxxxxxx>
+
+SEE ALSO
+ lxt2vcd(1) vcd2lxt(1) vcd2lxt2(1) vzt2vcd(1) vcd2vzt(1)
+
+
+
+Anthony Bybell 1.3.70 GTKWAVE(1)</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-gtkwave_mvl2lxt_mp.html b/docs/wiki/geda-gtkwave_mvl2lxt_mp.html
new file mode 100644
index 0000000..395911b
--- /dev/null
+++ b/docs/wiki/geda-gtkwave_mvl2lxt_mp.html
@@ -0,0 +1,45 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="coverts_mvlsim_aet_files_to_lxt_mvl2lxt" id="coverts_mvlsim_aet_files_to_lxt_mvl2lxt">Coverts MVLSIM AET files to LXT (mvl2lxt)</a></h1>
+<div class="level1">
+<pre class="code">MVL2LXT(1) Filetype Conversion MVL2LXT(1)
+
+
+
+NAME
+ mvl2lxt - Coverts MVLSIM AET files to LXT
+
+SYNTAX
+ mvl2lxt <filename.aet> <filename.lxt>
+
+DESCRIPTION
+ Converts AET files to LXT. This is experimental as it is not a com-
+ plete implementation and is not intended for general use.
+
+AUTHORS
+ Anthony Bybell <bybell@xxxxxxxxx>
+
+SEE ALSO
+ tex2vcd(1) mvl2vcd(1) lxt2vcd(1) vcd2lxt2(1) vcd2lxt(1) gtkwave(1)
+
+
+
+Anthony Bybell 1.3.34 MVL2LXT(1)</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-gtkwave_mvl2vcd_mp.html b/docs/wiki/geda-gtkwave_mvl2vcd_mp.html
new file mode 100644
index 0000000..9725a35
--- /dev/null
+++ b/docs/wiki/geda-gtkwave_mvl2vcd_mp.html
@@ -0,0 +1,46 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="coverts_mvlsim_aet_files_to_vcd_mvl2vcd" id="coverts_mvlsim_aet_files_to_vcd_mvl2vcd">Coverts MVLSIM AET files to VCD (mvl2vcd)</a></h1>
+<div class="level1">
+<pre class="code">MVL2VCD(1) Filetype Conversion MVL2VCD(1)
+
+
+
+NAME
+ mvl2vcd - Coverts MVLSIM AET files to VCD
+
+SYNTAX
+ mvl2vcd <filename.aet>
+
+DESCRIPTION
+ Converts AET files to VCD on stdout. This is experimental as it is not
+ a complete implementation and is not intended for general use.
+
+AUTHORS
+ Anthony Bybell <bybell@xxxxxxxxx>
+
+SEE ALSO
+ tex2vcd(1) mvl2lxt(1) lxt2vcd(1) vcd2lxt2(1) vcd2lxt(1) gtkwave(1)
+
+
+
+Anthony Bybell 1.3.34 MVL2VCD(1)
+</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-gtkwave_tex2vcd_mp.html b/docs/wiki/geda-gtkwave_tex2vcd_mp.html
new file mode 100644
index 0000000..71825cd
--- /dev/null
+++ b/docs/wiki/geda-gtkwave_tex2vcd_mp.html
@@ -0,0 +1,45 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="coverts_texsim_aet_files_to_vcd_tex2vcd" id="coverts_texsim_aet_files_to_vcd_tex2vcd">Coverts TEXSIM AET files to VCD (tex2vcd)</a></h1>
+<div class="level1">
+<pre class="code">TEX2VCD(1) Filetype Conversion TEX2VCD(1)
+
+
+
+NAME
+ tex2vcd - Coverts TEXSIM AET files to VCD
+
+SYNTAX
+ mvl2vcd <filename.aet>
+
+DESCRIPTION
+ Converts AET files to VCD on stdout. This is experimental as it is not
+ a complete implementation and is not intended for general use.
+
+AUTHORS
+ Anthony Bybell <bybell@xxxxxxxxx>
+
+SEE ALSO
+ mvl2vcd(1) mvl2lxt(1) lxt2vcd(1) vcd2lxt2(1) vcd2lxt(1) gtkwave(1)
+
+
+
+Anthony Bybell 1.3.34 TEX2VCD(1)</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-gtkwave_tla2vcd_mp.html b/docs/wiki/geda-gtkwave_tla2vcd_mp.html
new file mode 100644
index 0000000..806b81c
--- /dev/null
+++ b/docs/wiki/geda-gtkwave_tla2vcd_mp.html
@@ -0,0 +1,63 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="converts_tla_to_vcd_or_lst_files_tla2vcd" id="converts_tla_to_vcd_or_lst_files_tla2vcd">Converts TLA to VCD or LST files (tla2vcd)</a></h1>
+<div class="level1">
+<pre class="code">TLA2VCD(1) Tektronix File Format Conversion TLA2VCD(1)
+
+
+
+NAME
+ tla2vcd - Converts TLA to VCD or LST files
+
+SYNTAX
+ tla2vcd [option]... TLAFILE [[TLAFILE]...]
+
+
+DESCRIPTION
+ Converts TLA files from Tektronix logic analyzers to VCD or LST files.
+ Conversion to VCD allows viewing in tools such as gtkwave(1).
+
+OPTIONS
+ -t Generate text LST file instead of VCD file
+
+ -l List the available channels/groups and exit
+
+ -s <signal_list>
+ Select signals from regular expression list
+
+ -a All channels
+
+ -m Append MagniVu info (only in listing mode)
+
+ -z Compress output
+
+ -v Verbose
+
+
+AUTHORS
+ Emil
+
+SEE ALSO
+ lxt2vcd(1) vzt2vcd(1) gtkwave(1)
+
+
+
+Emil 1.0 TLA2VCD(1)</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-gtkwave_vcd2lxt2_mp.html b/docs/wiki/geda-gtkwave_vcd2lxt2_mp.html
new file mode 100644
index 0000000..5b11ecf
--- /dev/null
+++ b/docs/wiki/geda-gtkwave_vcd2lxt2_mp.html
@@ -0,0 +1,96 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="converts_vcd_files_to_lxt2_files_vcd2lxt2" id="converts_vcd_files_to_lxt2_files_vcd2lxt2">Converts VCD files to LXT2 files (vcd2lxt2)</a></h1>
+<div class="level1">
+<pre class="code">VCD2LXT2(1) Filetype Conversion VCD2LXT2(1)
+
+
+
+NAME
+ vcd2lxt2 - Converts VCD files to LXT2 files
+
+SYNTAX
+ vcd2lxt2 [option]... [VCDFILE] [LXTFILE]
+
+DESCRIPTION
+ Converts VCD files to LXT2 files.
+
+OPTIONS
+ -v,--vcdname <filename>
+ Specify VCD input filename.
+
+ -l,--lxtname <filename>
+ Specify LXT2 output filename.
+
+ -d,--depth <value>
+ Specify 0..9 gzip compression depth, default is 4.
+
+ -m,--maxgranule <value>
+ Specify number of granules per section, default is 8. One gran-
+ ule is equal to 32 timsteps.
+
+ -b,--break <value>
+ Specify break size (default = 0 = off). When the break size is
+ exceeded, the LXT2 dumper will dump all state information at the
+ next convenient granule plus dictionary boundary.
+
+ -p,--partialmode <mode>
+ Specify partial zip mode 0 = monolithic, 1 = separation. Using
+ a value of 1 expands LXT2 filesize but provides fast access for
+ very large traces. Note that the default mode is neither mono-
+ lithic nor separation: partial zip is disabled.
+
+ -c,--checkpoint <mode>
+ Specify checkpoint mode. 0 is on which is default, and 1 is
+ off. This is disabled when the break size is active.
+
+ -h,--help
+ Show help screen.
+
+
+
+ EXAMPLES
+
+ Note that you should specify dumpfile.vcd directly or use "-" for
+ stdin.
+
+ vcd2lxt dumpfile.vcd dumpfile.lxt --depth 9 --break 1073741824
+ This sets the compression level to 9 and sets the break size to
+ 1GB.
+
+ vcd2lxt dumpfile.vcd dumpfile.lxt --depth 9 --maxgranule 256
+ Allows more granules per section which allows for greater com-
+ pression.
+
+LIMITATIONS
+ vcd2lxt2 does not store glitches as these are coalesced together into
+ one value change during the writing of the LXT2 file.
+
+
+AUTHORS
+ Anthony Bybell <bybell@xxxxxxxxx>
+
+SEE ALSO
+ lxt2vcd(1) vcd2lxt2(1) gtkwave(1)
+
+
+
+Anthony Bybell 1.3.42 VCD2LXT2(1)</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-gtkwave_vcd2lxt_mp.html b/docs/wiki/geda-gtkwave_vcd2lxt_mp.html
new file mode 100644
index 0000000..2da6354
--- /dev/null
+++ b/docs/wiki/geda-gtkwave_vcd2lxt_mp.html
@@ -0,0 +1,83 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="converts_vcd_files_to_interlaced_or_linear_lxt_files_vcd2lxt" id="converts_vcd_files_to_interlaced_or_linear_lxt_files_vcd2lxt">Converts VCD files to interlaced or linear LXT files (vcd2lxt)</a></h1>
+<div class="level1">
+<pre class="code">VCD2LXT(1) Filetype Conversion VCD2LXT(1)
+
+
+
+NAME
+ vcd2lxt - Converts VCD files to interlaced or linear LXT files
+
+SYNTAX
+ vcd2lxt [VCDFILE] [LXTFILE] [option]...
+
+DESCRIPTION
+ Converts VCD files to interlaced or linear LXT files. Noncompressed
+ interlaced files will provide the fastest access, linear files will
+ provide the slowest yet have the greatest compression ratios.
+
+OPTIONS
+ -stats Prints out statistics on all nets in VCD file in addition to
+ performing the conversion.
+
+ -clockpack
+ Apply two-way subtraction algorithm in order to identify nets
+ whose value changes by a constant XOR or whose value
+ increases/decreases by a constant amount per constant unit of
+ time. This option can reduce dumpfile size dramatically as
+ value changes can be represented by an equation rather than
+ explicitly as a triple of time, net, and value.
+
+ -chgpack
+ Emit data to file after being filtered through zlib (gzip).
+
+ -linear
+ Write out LXT in "linear" format with no backpointers. These
+ are re-generated during initialization in gtkwave. Addition-
+ ally, use libbz2 (bzip2) as the compression filter.
+
+ -dictpack <size>
+ Store value changes greater than or equal to size bits as an
+ index into a dictionary. Experimentation shows that a value of
+ 18 is optimal for most cases.
+
+EXAMPLES
+ Note that you should specify dumpfile.vcd directly or use "-" for
+ stdin.
+
+ vcd2lxt dumpfile.vcd dumpfile.lxt -clockpack -chgpack -dictpack 18
+ This turns on clock packing, zlib compression, and enables the
+ dictionary encoding. Note that using no options writes out a
+ normal LXT file.
+
+ vcd2lxt dumpfile.vcd dumpfile.lxt -clockpack -linear -dictpack 18
+ Uses linear mode for even smaller files.
+
+AUTHORS
+ Anthony Bybell <bybell@xxxxxxxxx>
+
+SEE ALSO
+ lxt2vcd(1) vcd2lxt2(1) gtkwave(1)
+
+
+
+Anthony Bybell 1.3.34 VCD2LXT(1)</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-gtkwave_vcd2vzt_mp.html b/docs/wiki/geda-gtkwave_vcd2vzt_mp.html
new file mode 100644
index 0000000..30df085
--- /dev/null
+++ b/docs/wiki/geda-gtkwave_vcd2vzt_mp.html
@@ -0,0 +1,105 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="converts_vcd_files_to_vzt_files_vcd2vzt" id="converts_vcd_files_to_vzt_files_vcd2vzt">Converts VCD files to VZT files (vcd2vzt)</a></h1>
+<div class="level1">
+<pre class="code">VCD2VZT(1) Filetype Conversion VCD2VZT(1)
+
+
+
+NAME
+ vcd2vzt - Converts VCD files to VZT files
+
+SYNTAX
+ vcd2vzt [option]... [VCDFILE] [VZTFILE]
+
+DESCRIPTION
+ Converts VCD files to VZT files.
+
+OPTIONS
+ -v,--vcdname <filename>
+ Specify VCD input filename.
+
+ -l,--vztname <filename>
+ Specify VZT output filename.
+
+ -d,--depth <value>
+ Specify 0..9 gzip compression depth, default is 4.
+
+ -m,--maxgranule <value>
+ Specify number of granules per section, default is 8. One gran-
+ ule is equal to 32 timesteps.
+
+ -b,--break <value>
+ Specify break size (default = 0 = off). When the break size is
+ exceeded, the VZT dumper will dump all state information at the
+ next convenient granule plus dictionary boundary.
+
+ -z,--ziptype <value>
+ Specify zip type (default = 0 gzip, 1 = bzip2). This allows you
+ to override the default compression algorithm to use a more
+ effective one at the expense of greater runtime. Note that
+ bzip2 does not decompress as fast as gzip so the viewer will be
+ about two times slower when decompressing blocks.
+
+ -t,--twostate
+ Forces MVL2 twostate mode (default is MVL4). When enabled, the
+ trace will only store 0/1 values for binary facilities. This is
+ useful for functional simulation and will speed up dumping as
+ well as make traces somewhat smaller.
+
+ -r, --rle
+ Uses an bitwise RLE compression on the value table. Default is
+ off. When enabled, this causes the trace data table to be
+ stored using an alternate representation which can improve com-
+ pression in many cases.
+
+ -h,--help
+ Show help screen.
+
+
+
+ EXAMPLES
+
+ Note that you should specify dumpfile.vcd directly or use "-" for
+ stdin.
+
+ vcd2vzt dumpfile.vcd dumpfile.lxt --depth 9 --break 1073741824
+ This sets the compression level to 9 and sets the break size to
+ 1GB.
+
+ vcd2vzt dumpfile.vcd dumpfile.lxt --depth 9 --maxgranule 512
+ Allows more granules per section which allows for greater com-
+ pression at the expense of memory usage.
+
+LIMITATIONS
+ vcd2vzt does not store glitches as these are coalesced together into
+ one value change during the writing of the VZT file.
+
+
+AUTHORS
+ Anthony Bybell <bybell@xxxxxxxxx>
+
+SEE ALSO
+ vzt2vcd(1) lxt2vcd(1) vcd2lxt2(1) gtkwave(1)
+
+
+
+Anthony Bybell 1.3.48 VCD2VZT(1)</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-gtkwave_vzt2vcd_mp.html b/docs/wiki/geda-gtkwave_vzt2vcd_mp.html
new file mode 100644
index 0000000..b5b3636
--- /dev/null
+++ b/docs/wiki/geda-gtkwave_vzt2vcd_mp.html
@@ -0,0 +1,55 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="coverts_vzt_files_to_vcd_vzt2vcd" id="coverts_vzt_files_to_vcd_vzt2vcd">Coverts VZT files to VCD (vzt2vcd)</a></h1>
+<div class="level1">
+<pre class="code">VZT2VCD(1) Filetype Conversion VZT2VCD(1)
+
+
+
+NAME
+ vzt2vcd - Coverts VZT files to VCD
+
+SYNTAX
+ vzt2vcd <filename>
+
+DESCRIPTION
+ Converts VZT files to VCD files on stdout.
+
+EXAMPLES
+ To run this program the standard way type:
+
+ vzt2vcd filename.vzt
+ The VCD conversion is emitted to stdout.
+
+LIMITATIONS
+ vzt2vcd does not re-create glitches as these are coalesced together
+ into one value change during the writing of the VZT file.
+
+
+AUTHORS
+ Anthony Bybell <bybell@xxxxxxxxx>
+
+SEE ALSO
+ vcd2lxt2(1) vcd2lxt(1) lxt2vcd(1) gtkwave(1)
+
+
+
+Anthony Bybell 1.3.44 VZT2VCD(1)</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-gtkwave_vztminer_mp.html b/docs/wiki/geda-gtkwave_vztminer_mp.html
new file mode 100644
index 0000000..76771eb
--- /dev/null
+++ b/docs/wiki/geda-gtkwave_vztminer_mp.html
@@ -0,0 +1,78 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="data_mining_of_vzt_files_vztminer" id="data_mining_of_vzt_files_vztminer">Data mining of VZT files (vztminer)</a></h1>
+<div class="level1">
+<pre class="code">VZTMINER(1) Dumpfile Data Mining VZTMINER(1)
+
+
+
+NAME
+ vztminer - Data mining of VZT files
+
+SYNTAX
+ vztminer [option]... [VZTFILE]
+
+DESCRIPTION
+ Mines VZT files for specific data values and generates gtkwave save
+ files to stdout for future reload.
+
+OPTIONS
+ -d,--dumpfile <filename>
+ Specify VZT input dumpfile.
+
+ -m,--match <filename>
+ Specifies "bitwise" match data (binary, real, string)
+
+ -x,--hex <value>
+ Specifies hexadecimal match data that will automatically be con-
+ verted to binary for searches
+
+ -n,--namesonly
+ Indicates that only facnames should be printed in a gtkwave
+ savefile compatible format. By doing this, the file can be used
+ to specify which traces are to be imported into gtkwave.
+
+ -h,--help
+ Show help screen.
+
+EXAMPLES
+ vztminer dumpfile.vzt --match 20470000 -n
+
+ This attempts to match the hex value 20470000 across all facilities and
+ when the value is encountered, the facname only is printed to stdout in
+ order to generate a gtkwave compatible save file.
+
+LIMITATIONS
+ vztminer only prints the first time a value is encountered for a spe-
+ cific net. This is done in order to cut down on the size of output
+ files and to aid in following data such as addresses through a simula-
+ tion model.
+
+
+AUTHORS
+ Anthony Bybell <bybell@xxxxxxxxx>
+
+SEE ALSO
+ lxt2miner(1) vzt2vcd(1) lxt2vcd(1) vcd2lxt2(1) gtkwave(1)
+
+
+
+Anthony Bybell 1.3.64 VZTMINER(1)</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-guile_scripting.html b/docs/wiki/geda-guile_scripting.html
new file mode 100644
index 0000000..4d97dfd
--- /dev/null
+++ b/docs/wiki/geda-guile_scripting.html
@@ -0,0 +1,222 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#guile_scripting_reference" class="toc">Guile scripting reference</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#libgeda_c_library" class="toc">libgeda C library</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#libgeda_geda.scm" class="toc">libgeda geda.scm</a></span></div></li></ul>
+</li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h2><a name="guile_scripting_reference" id="guile_scripting_reference">Guile scripting reference</a></h2>
+<div class="level2">
+
+</div>
+<!-- SECTION "Guile scripting reference" [1-40] -->
+<h3><a name="libgeda_c_library" id="libgeda_c_library">libgeda C library</a></h3>
+<div class="level3">
+
+<p>
+ libgeda defines a number of low-level functions in C for configuring its behaviour and manipulating features such as the component and subcircuit libraries.
+</p>
+
+</div>
+
+<h4><a name="types" id="types">Types</a></h4>
+<div class="level4">
+<ul>
+<li class="level1"><div class="li"> attribute</div>
+</li>
+<li class="level1"><div class="li"> object</div>
+</li>
+<li class="level1"><div class="li"> page</div>
+</li>
+</ul>
+
+</div>
+
+<h4><a name="variables" id="variables">Variables</a></h4>
+<div class="level4">
+
+<p>
+ Basic configuration (defined by libgeda, read-only)
+</p>
+<ul>
+<li class="level1"><div class="li"> path-sep</div>
+</li>
+<li class="level1"><div class="li"> geda-rc-path</div>
+</li>
+<li class="level1"><div class="li"> geda-data-path</div>
+</li>
+</ul>
+
+<p>
+ Object type identifiers (defined by libgeda, read-only)
+</p>
+<ul>
+<li class="level1"><div class="li"> OBJ_LINE</div>
+</li>
+<li class="level1"><div class="li"> OBJ_BOX</div>
+</li>
+<li class="level1"><div class="li"> OBJ_PICTURE</div>
+</li>
+<li class="level1"><div class="li"> OBJ_CIRCLE</div>
+</li>
+<li class="level1"><div class="li"> OBJ_NET</div>
+</li>
+<li class="level1"><div class="li"> OBJ_BUS</div>
+</li>
+<li class="level1"><div class="li"> OBJ_COMPLEX</div>
+</li>
+<li class="level1"><div class="li"> OBJ_TEXT</div>
+</li>
+<li class="level1"><div class="li"> OBJ_<acronym title="Personal Identification Number">PIN</acronym></div>
+</li>
+<li class="level1"><div class="li"> OBJ_ARC</div>
+</li>
+<li class="level1"><div class="li"> OBJ_ROUTE</div>
+</li>
+<li class="level1"><div class="li"> OBJ_THRU_HOLE</div>
+</li>
+<li class="level1"><div class="li"> OBJ_PLACEHOLDER</div>
+</li>
+</ul>
+
+</div>
+
+<h4><a name="functions" id="functions">Functions</a></h4>
+<div class="level4">
+
+<p>
+ Component library:
+</p>
+<ul>
+<li class="level1"><div class="li"> component-library</div>
+</li>
+<li class="level1"><div class="li"> component-library-command</div>
+</li>
+<li class="level1"><div class="li"> component-library-funcs</div>
+</li>
+<li class="level1"><div class="li"> component-library-search</div>
+</li>
+<li class="level1"><div class="li"> reset-component-library</div>
+</li>
+</ul>
+
+<p>
+ Subcircuit library:
+</p>
+<ul>
+<li class="level1"><div class="li"> source-library</div>
+</li>
+<li class="level1"><div class="li"> source-library-search</div>
+</li>
+<li class="level1"><div class="li"> reset-source-library</div>
+</li>
+</ul>
+
+<p>
+ Libgeda behaviour configuration (write-only):
+</p>
+<ul>
+<li class="level1"><div class="li"> always-promote-attributes</div>
+</li>
+<li class="level1"><div class="li"> attribute-promotion</div>
+</li>
+<li class="level1"><div class="li"> bitmap-directory</div>
+</li>
+<li class="level1"><div class="li"> bus-ripper-symname</div>
+</li>
+<li class="level1"><div class="li"> font-directory</div>
+</li>
+<li class="level1"><div class="li"> keep-invisible</div>
+</li>
+<li class="level1"><div class="li"> map-font-character-to-file</div>
+</li>
+<li class="level1"><div class="li"> postscript-prolog</div>
+</li>
+<li class="level1"><div class="li"> promote-invisible</div>
+</li>
+<li class="level1"><div class="li"> scheme-directory</div>
+</li>
+<li class="level1"><div class="li"> untitled-name</div>
+</li>
+<li class="level1"><div class="li"> world-size</div>
+</li>
+</ul>
+
+<p>
+ Smob type manipulators:
+</p>
+<ul>
+<li class="level1"><div class="li"> get-attribute-name-value</div>
+</li>
+<li class="level1"><div class="li"> get-attribute-bounds</div>
+</li>
+<li class="level1"><div class="li"> get-attribute-angle</div>
+</li>
+<li class="level1"><div class="li"> calcule-new-attrib-bounds</div>
+</li>
+<li class="level1"><div class="li"> get-object-attributes</div>
+</li>
+<li class="level1"><div class="li"> get-attrib-value-by-attrib-name</div>
+</li>
+<li class="level1"><div class="li"> get-object-type</div>
+</li>
+<li class="level1"><div class="li"> get-line-width</div>
+</li>
+<li class="level1"><div class="li"> get-page-filename</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "libgeda C library" [41-1481] -->
+<h3><a name="libgeda_geda.scm" id="libgeda_geda.scm">libgeda geda.scm</a></h3>
+<div class="level3">
+
+<p>
+ geda.scm, installed with libgeda, provides several useful functions for doing simple manipulation of paths and files, as well as loading rc files from gafrc.d directories.
+</p>
+
+</div>
+
+<h4><a name="functions1" id="functions1">Functions</a></h4>
+<div class="level4">
+<ul>
+<li class="level1"><div class="li"> build-path</div>
+</li>
+<li class="level1"><div class="li"> regular-file?</div>
+</li>
+<li class="level1"><div class="li"> directory?</div>
+</li>
+<li class="level1"><div class="li"> has-suffix?</div>
+</li>
+<li class="level1"><div class="li"> load-scheme-dir</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "libgeda geda.scm" [1482-] --></body>
+</html>
diff --git a/docs/wiki/geda-hse_howto.html b/docs/wiki/geda-hse_howto.html
new file mode 100644
index 0000000..d5f8744
--- /dev/null
+++ b/docs/wiki/geda-hse_howto.html
@@ -0,0 +1,137 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="hooks_scheme_extension_howto" id="hooks_scheme_extension_howto">Hooks/Scheme Extension HOWTO</a></h1>
+<div class="level1">
+<pre class="code">gEDA - GPL Electronic Design Automation
+
+HOOKS AND SCHEME EXTENSION IN GSCHEM
+====================================
+
+Copyright (C) 2000 Stefan Petersen
+
+This program is free software; you can redistribute it and/or modify
+it under the terms of the GNU General Public License as published by
+the Free Software Foundation; either version 2 of the License, or
+(at your option) any later version.
+
+This program is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+GNU General Public License for more details.
+
+You should have received a copy of the GNU General Public License
+along with this program; if not, write to the Free Software
+Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
+
+
+Introduction
+------------
+gschem has a scheme interpreter (called Guile) built in. Though not
+complete, there are extensions to this interpreter to get access to
+different parts of the schematic.
+
+There are a couple of other scheme extensions available that will not be
+described here. They belong mainly to rc-files (resource files in
+gEDA programs are really scheme scripts) and to the keymapping system
+(described in separate keymapping documentation).
+
+The rest I will try to describe here.
+
+
+Scheme functions
+----------------
+There are two function available for handling attributes in the schematic.
+
+* get-attribute-name-value
+Inparameter : an attribute
+Outparameter : a pair with the name of the attribute as string in the
+ car element and the value of the attribute in the cdr
+ element.
+Description : Simply an accessor to the information hidden in the type
+ attribute. The functionality of this is placed in libgeda
+ since the C-type ATTRIBUTE is defined there.
+
+* set-attribute-value!
+Inparameter : an attribute and a string.
+Outparameter : undefined.
+Description : Sets a new value to an attribute. The attribute must
+ be defined, the function can't create a new attribute.
+ Defined both in gschem and libgeda, mainly because
+ where different variables and information are available.
+
+
+Hooks
+-----
+Hooks are a way to define functions that will be called during different
+part of a programs execution. In gschem there are (currently) three
+different hooks available:
+* add-component-hook
+* copy-component-hook
+* move-component-hook
+
+As their name indicate, they are called at different occasions. When
+you add a component add-component-hook is called, etc.
+
+To add a function to be called you simply use the Guile funtion add-hook!.
+An example; to run the function auto-uref when you add a component you
+simply add the following line, preferrably in ${HOME}/.gEDA/gschemrc:
+(add-hook! add-component-hook auto-uref)
+
+The function to be called from a hook (for example auto-uref above) has
+to accept one parameter, a list of attributes.
+
+A small example that prints all attributes on a component to be placed:
+
+(define (print-all-attributes attribute-list)
+ (foreach (lambda (attribute) (display attribute)) attribute-list))
+
+
+How to use this
+---------------
+The most complete example utilizing all of the above functions are in fact
+the auto-uref scheme script that currently is part of the gschem distribution.
+You can find it <where gschem is installed>/share/gEDA/scheme/auto-uref.scm.
+Uninstalled it's available at gschem/scheme/auto-uref.scm
+
+All components have a reference designator that must be unique so
+gnetlist can handle it properly. By automatically assigning a number
+to each instance of a component when you place and copy it, you can
+simplify the naming operation.
+
+All components has, per default, an uref attribute, for example uref=R?.
+The letter varies with component type. The auto-uref script enumerates
+uref based on what prefix the component has and assigns a number.
+
+For example, the first component you place has per default uref=U? gets
+the attribute uref=U1. Next component with uref=U? gets uref=U2 and so on.
+
+To be able to use the auto-uref script you simply add two lines in
+${HOME}/.gEDA/gschemrc. They are:
+(load "<where gschem is installed>/share/gEDA/scheme/auto-uref.scm")
+(add-hook! add-component-hook auto-uref)
+
+If you want auto enumeration to work when you copy the component too, you
+simply add the following line:
+(add-hook! copy-component-hook auto-uref)
+
+Good luck!
+
+</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-icarus_anc.html b/docs/wiki/geda-icarus_anc.html
new file mode 100644
index 0000000..41bb037
--- /dev/null
+++ b/docs/wiki/geda-icarus_anc.html
@@ -0,0 +1,106 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="icarus_attribute_naming_conventions" id="icarus_attribute_naming_conventions">Icarus Attribute Naming Conventions</a></h1>
+<div class="level1">
+<pre class="code">ATTRIBUTE NAMING CONVENTIONS
+
+Attributes that are specific to Icarus Verilog, and are intended to be
+of use to programmers, start with the prefix "ivl_".
+
+Attributes with the "_ivl_" prefix are set aside for internal
+use. They may be generated internally by the compiler. They need not
+be documented here.
+
+ATTRIBUTES TO CONTROL SYNTHESIS
+
+The following is a summary of Verilog attributes that Icarus Verilog
+understands within Verilog source files to control synthesis
+behavior. This section documents generic synthesis attributes. For
+target specific attributes, see target specific documentation.
+
+These attributes only effect the behavior of the synthesizer. For
+example, the ivl_combinational will not generate an error message
+if the Verilog is being compiled for simulation. (It may generate a
+warning.)
+
+
+* Attributes for "always" and "initial" statements
+
+(* ivl_combinational *)
+
+ This attribute tells the compiler that the statement models
+ combinational logic. If the compiler finds that it cannot make
+ combinational logic out of a marked always statement, it will
+ report an error.
+
+ This attribute can be used to prevent accidentally inferring
+ latches or flip-flops where the user intended combinational
+ logic.
+
+(* ivl_synthesis_on *)
+
+ This attribute tells the compiler that the marked always statement
+ is synthesizable. The compiler will attempt to synthesize the
+ code in the marked "always" statement. If it cannot in any way
+ synthesize it, then it will report an error.
+
+(* ivl_synthesis_off *)
+
+ If this value is attached to an "always" statement, then the
+ compiler will *not* synthesize the "always" statement. This can be
+ used, for example, to mark embedded test bench code.
+
+
+* Attributes for modules
+
+(* ivl_synthesis_cell *)
+
+ If this value is attached to a module during synthesis, that
+ module will be considered a target architecture primitive, and
+ its interior will not be synthesized further. The module can
+ therefore hold a model for simulation purposes.
+
+
+* Attributes for signals (wire/reg/integer/tri/etc.)
+
+(* PAD = "<pad assignment list>" *)
+
+ If this attribute is attached to a signal that happens to be a
+ root module port, then targets that support it will use the string
+ value as a list of pin assignments for the port/signal. The format
+ is a comma separated list of location tokens, with the format of
+ the token itself defined by the back-end tools in use.
+
+* Other Attributes
+
+[ none defined yet ]
+
+
+MISC
+
+(* _ivl_schedule_push *)
+
+ If this attribute is attached to a thread object (always or
+ initial statement) then the vvp code generator will generate code
+ that causes the scheduler to push this thread at compile time. The
+ compiler may internally add this attribute to always statements if
+ it detects that it is combinational. This helps resolve time-0
+ races.</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-icarus_extensions.html b/docs/wiki/geda-icarus_extensions.html
new file mode 100644
index 0000000..0004418
--- /dev/null
+++ b/docs/wiki/geda-icarus_extensions.html
@@ -0,0 +1,105 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="icarus_verilog_extensions" id="icarus_verilog_extensions">Icarus Verilog Extensions</a></h1>
+<div class="level1">
+<pre class="code">Icarus Verilog Extensions
+
+Icarus Verilog supports certain extensions to the baseline IEEE1364
+standard. Some of these are picked from extended variants of the
+language, such as SystemVerilog, and some are expressions of internal
+behavior of Icarus Verilog, made available as a tool debugging aid.
+
+* Builtin System Functions
+
+** Extended Verilog Data Types
+
+This feature is turned off if the generation flag "-g" is set to other
+then the default "2x". For example, "iverilog -g2x" enables extended
+data types, and "iverilog -g2" disables them.
+
+Icarus Verilog adds support for extended data types. This extended
+type syntax is based on a proposal by Cadence Design Systems,
+originally as an update to the IEEE1364. That original proposal has
+apparently been absorbed by the IEEE1800 SystemVerilog
+standard. Icarus Verilog currently only takes the new primitive types
+from the proposal.
+
+Extended data types separates the concept of net/variable from the
+data type. Both nets and variables can declared with any data
+type. The primitive types available are:
+
+ logic - The familiar 0, 1, x and z, optionally with strength.
+ bool - Limited to only 0 and 1
+ real - 64bit real values
+
+Nets with logic type may have multiple drivers with strength, and the
+value is resolved the usual way. Only logic values may be driven to
+logic nets, so bool values driven onto logic nets are implicitly
+converted to logic.
+
+Nets with any other type may not have multiple drivers. The compiler
+should detect the multiple drivers and report an error.
+
+- Declarations
+
+The declaration of a net is extended to include the type of the wire,
+with the syntax:
+
+ wire <type> <wire-assignment-list>... ;
+
+The <type>, if omitted, is taken to be logic. The "wire" can be any of
+the net keywords. Wires can be logic, bool, real, or vectors of logic
+or bool. Some valid examples:
+
+ wire real foo = 1.0;
+ tri logic bus[31:0];
+ wire bool addr[23:0];
+ ... and so on.
+
+The declarations of variables is similar. The "reg" keyword is used to
+specify that this is a variable. Variables can have the same data
+types as nets.
+
+- Ports
+
+Module and task ports in standard verilog are restricted to logic
+types. This extension removes that restriction, allowing any type to
+pass through the port consistent with the continuous assignment
+connectivity that is implied by the type.
+
+- Expressions
+
+Expressions in the face of real values is covered by the baseline
+Verilog standard.
+
+The bool type supports the same operators as the logic type, with the
+obvious differences imposed by the limited domain.
+
+Comparison operators (not case compare) return logic if either of
+their operands is logic. If both are bool or real (including mix of
+bool and real) then the result is bool. This is because comparison of
+bools and reals always return exactly true or false.
+
+Case comparison returns bool. This differs from baseline Verilog,
+which strictly speaking returns a logic, but only 0 or 1 values.
+
+All the arithmetic operators return bool if both of their operands are
+bool or real. Otherwise, they return logic.</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-icarus_glossary.html b/docs/wiki/geda-icarus_glossary.html
new file mode 100644
index 0000000..53a519e
--- /dev/null
+++ b/docs/wiki/geda-icarus_glossary.html
@@ -0,0 +1,61 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="icarus_verilog_glossary" id="icarus_verilog_glossary">Icarus Verilog Glossary</a></h1>
+<div class="level1">
+<pre class="code">Throughout Icarus Verilog descriptions and source code, I use a
+variety of terms and acronyms that might be specific to Icarus
+Verilog, have an Icarus Verilog specific meaning, or just aren't
+widely known. So here I define these terms.
+
+
+LRM - Language Reference Manual
+ This is a generic acronym, but in the Verilog world we sometimes
+ mean *the* language reference manual, the IEEE1364 standard.
+
+
+PLI - Programming Language Interface
+ This is a C API into Verilog simulators that is defined by the
+ IEEE1364. There are two major interfaces, sometimes called PLI 1
+ and PLI 2. PLI 2 is also often called VPI.
+
+
+UDP - User Defined Primitive
+ These are objects that Verilog programmers define with the
+ "primitive" keyword. They are truth-table based devices. The
+ syntax for defining them is described in the LRM.
+
+
+VPI -
+ This is the C API that is defined by the Verilog standard, and
+ that Icarus Verilog partially implements. See also PLI.
+
+
+VVM - Verilog Virtual Machine
+ This is the Icarus Verilog runtime that works with the code
+ generator that generates C++.
+
+
+VVP - Verilog Virtual Processor
+ This is the Icarus Verilog runtime that reads in custom code in a
+ form that I call "VVP Assembly". See the vvp/ directory for
+ documentation on that.
+
+</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-icarus_ieee1364.html b/docs/wiki/geda-icarus_ieee1364.html
new file mode 100644
index 0000000..89361ff
--- /dev/null
+++ b/docs/wiki/geda-icarus_ieee1364.html
@@ -0,0 +1,574 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="icarus_verilog_vs._ieee1364" id="icarus_verilog_vs._ieee1364">Icarus Verilog vs. IEEE1364</a></h1>
+<div class="level1">
+<pre class="code"> Icarus Verilog vs. IEEE1364
+ Copyright 2000 Stephen Williams
+
+The IEEE1364 standard is the bible that defines the correctness of the
+Icarus Verilog implementation and behavior of the compiled
+program. The IEEE1364.1 is also referenced for matters of
+synthesis. So the ultimate definition of right and wrong comes from
+those documents.
+
+That does not mean that a Verilog implementation is fully
+constrained. The standard document allows for implementation specific
+behavior that, when properly accounted for, does not effect the
+intended semantics of the specified language. It is therefore possible
+and common to write programs that produce different results when run
+by different Verilog implementations.
+
+
+STANDARDIZATION ISSUES
+
+These are some issues where the IEEE1364 left unclear, unspecified or
+simply wrong. I'll try to be precise as I can, and reference the
+standard as needed. I've made implementation decisions for Icarus
+Verilog, and I will make clear what those decisions are and how they
+affect the language.
+
+* OBJECTS CAN BE DECLARED ANYWHERE IN THE MODULE
+
+Consider this module:
+
+ module sample1;
+ initial foo = 1;
+ reg foo;
+ wire tmp = bar;
+ initial #1 $display("foo = %b, bar = %b", foo, tmp);
+ endmodule
+
+Notice that the ``reg foo;'' declaration is placed after the first
+initial statement. It turns out that this is a perfectly legal module
+according to the -1995 and -2000 versions of the standard. The
+statement ``reg foo;'' is a module_item_declaration which is in turn a
+module_item. The BNF in the appendix of IEEE1364-1995 treats all
+module_item statements equally, so no order is imposed.
+
+Furthermore, there is no text (that I can find) elsewhere in the
+standard that imposes any ordering restriction. The sorts of
+restrictions I would look for are "module_item_declarations must
+appear before all other module_items" or "variables must be declared
+textually before they are referenced." Such statements simply do not
+exist. (Personally, I think it is fine that they don't.)
+
+The closest is the rules for implicit declarations of variables that
+are otherwise undeclared. In the above example, ``bar'' is implicitly
+declared and is therefore a wire. However, although ``initial foo = 1;''
+is written before foo is declared, foo *is* declared within the
+module, and declared legally by the BNF of the standard.
+
+Here is another example:
+
+ module sample2;
+ initial x.foo = 1;
+ test x;
+ initial #1 $display("foo = %b", x.foo);
+ endmodule
+
+ module test;
+ reg foo;
+ endmodule;
+
+From this example one can clearly see that foo is once again declared
+after its use in behavioral code. One also sees a forward reference of
+an entire module. Once again, the standard places no restriction on
+the order of module declarations in a source file, so this program is,
+according to the standard, perfectly well formed.
+
+Icarus Verilog interprets both of these examples according to "The
+Standard As I Understand It." However, commercial tools in general
+break down with these programs. In particular, the first example
+may generate different errors depending on the tool. The most common
+error is to claim that ``foo'' is declared twice, once (implicitly) as
+a wire and once as a reg.
+
+So the question now becomes, "Is the standard broken, or are the tools
+limited?" Coverage of the standard seems to vary widely from tool to
+tool so it is not clear that the standard really is at fault. It is
+clear, however, that somebody goofed somewhere.
+
+My personal opinion is that there is no logical need to require that
+all module_item_declarations precede any other module items. I
+personally would oppose such a restriction. It may make sense to
+require that declarations of variables within a module be preceded by
+their use, although even that is not necessary for the implementation
+of efficient compilers.
+
+However, the existence hierarchical naming syntax as demonstrated in
+sample2 can have implications that affect any declaration order
+rules. When reaching into a module with a hierarchical name, the
+module being referenced is already completely declared (or not
+declared at all, as in sample2) so module_item order is completely
+irrelevant. But a "declare before use" rule would infect module
+ordering, by requiring that modules that are used be first defined.
+
+
+* TASK AND FUNCTION PARAMETERS CANNOT HAVE EXPLICIT TYPES
+
+Consider a function negate that wants to take a signed integer value
+and return its negative:
+
+ function integer negate;
+ input [15:0] val;
+ negate = -val;
+ endfunction
+
+This is not quite right, because the input is implicitly a reg type,
+which is unsigned. The result, then, will always be a negative value,
+even if a negative val is passed in.
+
+It is possible to fix up this specific example to work properly with
+the bit pattern of a 16bit number, but that is not the point. What's
+needed is clarification on whether an input can be declared in the
+port declaration as well as in the contained block declaration.
+
+As I understand the situation, this should be allowed:
+
+ function integer negate;
+ input [15:0] val;
+ reg signed [15:0] val;
+ negate = -val;
+ endfunction
+
+In the -1995 standard, the variable is already implicitly a reg if
+declared within a function or task. However, in the -2000 standard
+there is now (as in this example) a reason why one might want to
+actually declare the type explicitly.
+
+I think that a port *cannot* be declared as an integer or time type
+(though the result can) because the range of the port declaration must
+match the range of the integer/time declaration, but the range of
+integers is unspecified. This, by the way, also applies to module
+ports.
+
+With the above in mind, I have decided to *allow* function and task
+ports to be declared with types, as long as the types are variable
+types, such as reg or integer. Without this, there would be no
+portable way to pass integers into functions/tasks. The standard does
+not say it is allowed, but it doesn't *disallow* it, and other
+commercial tools seem to work similarly.
+
+
+* ROUNDING OF TIME
+
+When the `timescale directive is present, the compiler is supposed to
+round fractional times (after scaling) to the nearest integer. The
+confusing bit here is that it is apparently conventional that if the
+`timescale directive is *not* present, times are rounded towards zero
+always.
+
+
+* VALUE OF X IN PRIMITIVE OUTPUTS
+
+The IEEE1364-1995 standard clearly states in Table 8-1 that the x
+symbols is allowed in input columns, but is not allowed in
+outputs. Furthermore, none of the examples have an x in the output of
+a primitive. Table 8-1 in the IEEE1364-2000 also says the same thing.
+
+However, the BNF clearly states that 0, 1, x and X are valid
+output_symbol characters. The standard is self contradictory. So I
+take it that x is allowed, as that is what Verilog-XL does.
+
+
+* REPEAT LOOPS vs. REPEAT EVENT CONTROL
+
+There seems to be ambiguity in how code like this should be parsed:
+
+ repeat (5) @(posedge clk) <statement>;
+
+There are two valid interpretations of this code, from the
+IEEE1364-1995 standard. One looks like this:
+
+ procedural_timing_control_statement ::=
+ delay_or_event_control statement_or_null
+
+ delay_or_event_control ::=
+ event_control
+ | repeat ( expression ) event_control
+
+If this interpretation is used, then the statement <statement> should
+be executed after the 5th posedge of clk. However, there is also this
+interpretation:
+
+ loop_statement ::=
+ repeat ( expression ) statement
+
+If *this* interpretation is used, then <statement> should be executed
+5 times on the posedge of clk. The way the -1995 standard is written,
+these are both equally valid interpretations of the example, yet they
+produce very different results. The standard offers no guidance on how
+to resolve this conflict, and the IEEE1364-2000 DRAFT does not improve
+the situation.
+
+Practice suggests that a repeat followed by an event control should be
+interpreted as a loop head, and this is what Icarus Verilog does, as
+well as all the other major Verilog tools, but the standard does not
+say this.
+
+* UNSIZED NUMERIC CONSTANTS ARE NOT LIMITED TO 32 BITS
+
+The Verilog standard allows Verilog implementations to limit the size
+of unsized constants to a bit width of at least 32. That means that a
+constant 17179869183 (36'h3_ffff_ffff) may overflow some compilers. In
+fact, it is common to limit these values to 32bits. However, a
+compiler may just as easily choose another width limit, for example
+64bits. That value is equally good.
+
+However, it is not *required* that an implementation truncate at 32
+bits, and in fact Icarus Verilog does not truncate at all. It will
+make the unsized constant as big as it needs to be to hold the value
+accurately. This is especially useful in situations like this;
+
+ reg [width-1:0] foo = 17179869183;
+
+The programmer wants the constant to take on the width of the reg,
+which in this example is parameterized. Since constant sizes cannot be
+parameterized, the programmer ideally gives an unsized constant, which
+the compiler then expands/contracts to match the l-value.
+
+Also, by choosing to not ever truncate, Icarus Verilog can handle code
+written for a 64bit compiler as easily as for a 32bit compiler. In
+particular, any constants that the user does not expect to be
+arbitrarily truncated by his compiler will also not be truncated by
+Icarus Verilog, no matter what that other compiler chooses as a
+truncation point.
+
+
+* UNSIZED EXPRESSIONS AS PARAMETERS TO CONCATENATION {}
+
+The Verilog standard clearly states in 4.1.14:
+
+ "Unsized constant numbers shall not be allowed in
+ concatenations. This is because the size of each
+ operand in the concatenation is needed to calculate
+ the complete size of the concatenation."
+
+So for example the expression {1'b0, 16} is clearly illegal. It
+also stands to reason that {1'b0, 15+1} is illegal, for exactly the
+same justification. What is the size of the expression (15+1)?
+Furthermore, it is reasonable to expect that (16) and (15+1) are
+exactly the same so far as the compiler is concerned.
+
+Unfortunately, Cadence seems to feel otherwise. In particular, it has
+been reported that although {1'b0, 16} causes an error, {1'b0, 15+1}
+is accepted. Further testing shows that any expression other then a
+simple unsized constant is accepted there, even if all the operands of
+all the operators that make up the expression are unsized integers.
+
+This is a semantic problem. Icarus Verilog doesn't limit the size of
+integer constants. This is valid as stated in 2.5.1 Note 3:
+
+ "The number of bits that make up an unsized number
+ (which is a simple decimal number or a number without
+ the size specification) shall be *at*least* 32."
+ [emphasis added]
+
+Icarus Verilog will hold any integer constant, so the size will be as
+large as it needs to be, whether that is 64bits, 128bits, or
+more. With this in mind, what is the value of these expressions?
+
+ {'h1_00_00_00_00}
+ {'h1 << 32}
+ {'h0_00_00_00_01 << 32}
+ {'h5_00_00_00_00 + 1}
+
+These examples show that the standard is justified in requiring that
+the operands of concatenation have size. The dispute is what it takes
+to cause an expression to have a size, and what that size is.
+Verilog-XL claims that (16) does not have a size, but (15+1) does. The
+size of the expression (15+1) is the size of the adder that is
+created, but how wide is the adder when adding unsized constants?
+
+One might note that the quote from section 4.1.14 says "Unsized
+*constant*numbers* shall not be allowed." It does not say "Unsized
+expressions...", so arguably accepting (15+1) or even (16+0) as an
+operand to a concatenation is not a violation of the letter of the
+law. However, the very next sentence of the quote expresses the
+intent, and accepting (15+1) as having a more defined size then (16)
+seems to be a violation of that intent.
+
+Whatever a compiler decides the size is, the user has no way to
+predict it, and the compiler should not have the right to treat (15+1)
+any differently then (16). Therefore, Icarus Verilog takes the
+position that such expressions are *unsized* and are not allowed as
+operands to concatenations. Icarus Verilog will in general assume that
+operations on unsized numbers produce unsized results. There are
+exceptions when the operator itself does define a size, such as the
+comparison operators or the reduction operators. Icarus Verilog will
+generate appropriate error messages.
+
+
+* MODULE INSTANCE WITH WRONG SIZE PORT LIST
+
+A module declaration like this declares a module that takes three ports:
+
+ module three (a, b, c);
+ input a, b, c;
+ reg x;
+ endmodule
+
+This is fine and obvious. It is also clear from the standard that
+these are legal instantiations of this module:
+
+ three u1 (x,y,z);
+ three u2 ( ,y, );
+ three u3 ( , , );
+ three u4 (.b(y));
+
+In some of the above examples, there are unconnected ports. In the
+case of u4, the pass by name connects only port b, and leaves a and c
+unconnected. u2 and u4 are the same thing, in fact, but using
+positional or by-name syntax. The next example is a little less
+obvious:
+
+ three u4 ();
+
+The trick here is that strictly speaking, the parser cannot tell
+whether this is a list of no pass by name ports (that is, all
+unconnected) or an empty positional list. If this were an empty
+positional list, then the wrong number of ports is given, but if it is
+an empty by-name list, it is an obviously valid instantiation. So it
+is fine to accept this case as valid.
+
+These are more doubtful:
+
+ three u5(x,y);
+ three u6(,);
+
+These are definitely positional port lists, and they are definitely
+the wrong length. In this case, the standard is not explicit about
+what to do about positional port lists in module instantiations,
+except that the first is connected to the first, second to second,
+etc. It does not say that the list must be the right length, but every
+example of unconnected ports used by-name syntax, and every example of
+ordered list has the right size list.
+
+Icarus Verilog takes the (very weak) hint that ordered lists should be
+the right length, and will therefore flag instances u5 and u6 as
+errors. The IEEE1364 standard should be more specific one way or the
+other.
+
+* UNKNOWN VALUES IN L-VALUE BIT SELECTS
+
+Consider this example:
+
+ reg [7:0] vec;
+ wire [4:0] idx = <expr>;
+ [...]
+ vec[idx] = 1;
+
+So long as the value of idx is a valid bit select address, the
+behavior of this assignment is obvious. However, there is no explicit
+word in the standard as to what happens if the value is out of
+range. The standard clearly states the value of an expression when the
+bit-select or part select is out of range (the value is x) but does
+not address the behavior when the expression is an l-value.
+
+Icarus Verilog will take the position that bit select expressions in
+the l-value will select oblivion if it is out of range. That is, if
+idx has a value that is not a valid bit select of vec, then the
+assignment will have no effect.
+
+
+* SCHEDULING VALUES IN LOGIC
+
+The interaction between blocking assignments in procedural code and
+logic gates in gate-level code and expressions is poorly defined in
+Verilog. Consider this example:
+
+ reg a;
+ reg b;
+ wire q = a & b;
+
+ initial begin
+ a = 1;
+ b = 0;
+ #1 b = 1;
+ if (q !== 0) begin
+ $display("FAILED -- q changed too soon? %b", q);
+ $finish;
+ end
+ end
+
+This is a confusing situation. It is clear from the Verilog standard
+that an assignment to a variable using a blocking assign causes the
+l-value to receive the value before the assignment completes. This
+means that a subsequent read of the assigned variable *must* read back
+what was blocking-assigned.
+
+However, in the example above, the "wire q = a & b" expresses some
+gate logic between a/b and q. The standard does not say whether a read
+out of logic should read the value computed from previous assigns to
+the input from the same thread. Specifically, when "a" and "b" are
+assigned by blocking assignments, will a read of "q" get the computed
+value or the existing value?
+
+In fact, existing commercial tools do it both ways. Some tools print
+the FAILED message in the above example, and some do not. Icarus
+Verilog does not print the FAILED message in the above example,
+because the gate value change is *scheduled* when inputs are assigned,
+but not propagated until the thread gives up the processor.
+
+Icarus Verilog chooses this behavior in order to filter out zero-width
+pulses as early as possible. The implication of this is that a read of
+the output of combinational logic will most likely *not* reflect the
+changes in inputs until the thread that changed the inputs yields
+execution.
+
+
+* BIT AND PART SELECTS OF PARAMETERS
+
+Bit and part selects are supposed to only be supported on vector nets
+and variables (wires, regs, etc.) However, it is common for Verilog
+compilers to also support bit and part select on parameters. Icarus
+Verilog also chooses to support bit and part selects on parameter
+names, but we need to define what that means.
+
+A bit or a part select on a parameter expression returns an unsigned
+value with a defined size. The parameter value is considered be a
+constant vector of bits foo[X:0]. That is, zero based. The bit and
+part selects operate from that assumption.
+
+Verilog 2001 adds syntax to allow the user to explicitly declare the
+parameter range (i.e. parameter [5:0] foo = 9;) so Icarus Verilog will
+(or should) use the explicitly declared vector dimensions to interpret
+bit and part selects.
+
+
+* EDGES OF VECTORS
+
+Consider this example:
+
+ reg [ 5:0] clock;
+ always @(posedge clock) [do stuff]
+
+The IEEE1364 standard clearly states that the @(posedge clock) looks
+only at the bit clock[0] (the least significant bit) to search for
+edges. It has been pointed out by some that Verilog XL instead
+implements it as "@(posedge |clock)": it looks for a rise in the
+reduction or of the vector. Cadence Design Systems technical support
+has been rumored to claim that the IEEE1364 specification is wrong,
+but NC-Verilog behaves according to the specification, and thus
+different from XL.
+
+Icarus Verilog, therefore, takes the position that the specification
+is clear and correct, and it behaves as does NC-Verilog in this
+matter.
+
+
+* REAL VARIABLES IN $dumpoff DEAD-ZONES
+
+The IEEE1364 standard clearly states that in VCD files, the $dumpoff
+section checkpoints all the dumped variables as X values. For reg and
+wire bits/vectors, this obviously means 'bx values. Icarus Verilog
+does this, for example:
+
+ $dumpoff
+ x!
+ x"
+ $end
+
+Real variables can also be included in VCD dumps, but it is not at
+all obvious what is supposed to be dumped into the $dumpoff-$end
+section of the VCD file. Verilog-XL dumps "r0 !" to set the real
+variables to the dead-zone value of 0.0, whereas other tools, such as
+ModelTech, ignore real variables in this section.
+
+For example (from XL):
+
+ $dumpoff
+ r0 !
+ r0 "
+ $end
+
+Icarus Verilog dumps NaN values for real variables in the
+$dumpoff-$end section of the VCD file. The NaN value is the IEEE754
+equivalent of an unknown value, and so better reflects the unknown
+(during the dead zone) status of the variable, like this:
+
+ $dumpoff
+ rNaN !
+ rNaN "
+ $end
+
+It turns out that NaN is conventionally accepted by scanf functions,
+and viewers that support real variables support NaN values. So while
+the IEEE1364 doesn't require this behavior, and given the variety that
+already seems to exist amongst VCD viewers in the wild, this behavior
+seems to be acceptable according to the standard, is a better mirror
+of 4-value behavior in the dead zone, and appears more user friendly
+when viewed by reasonable viewers.
+
+
+$Id: ieee1364-notes.txt,v 1.17 2003/07/15 03:49:22 steve Exp $
+$Log: ieee1364-notes.txt,v $
+Revision 1.17 2003/07/15 03:49:22 steve
+ Spelling fixes.
+
+Revision 1.16 2003/04/14 03:40:21 steve
+ Make some effort to preserve bits while
+ operating on constant values.
+
+Revision 1.15 2003/02/16 23:39:08 steve
+ NaN in dead zones of VCD dumps.
+
+Revision 1.14 2003/02/06 17:51:36 steve
+ Edge of vectors notes.
+
+Revision 1.13 2002/08/20 04:11:53 steve
+ Support parameters with defined ranges.
+
+Revision 1.12 2002/06/11 03:34:33 steve
+ Spelling patch (Larry Doolittle)
+
+Revision 1.11 2002/04/27 02:38:04 steve
+ Support selecting bits from parameters.
+
+Revision 1.10 2002/03/31 01:54:13 steve
+ Notes about scheduling
+
+Revision 1.9 2002/01/26 02:08:07 steve
+ Handle x in l-value of set/x
+
+Revision 1.8 2001/08/01 05:17:31 steve
+ Accept empty port lists to module instantiation.
+
+Revision 1.7 2001/02/17 05:27:31 steve
+ I allow function ports to have types.
+
+Revision 1.6 2001/02/12 16:48:04 steve
+ Rant about bit widths.
+
+Revision 1.5 2001/01/02 17:28:08 steve
+ Resolve repeat ambiguity in favor of loop.
+
+Revision 1.4 2001/01/01 19:12:35 steve
+ repeat loops ambiguity.
+
+Revision 1.3 2000/12/15 00:21:46 steve
+ rounding of time and x in primitives.
+
+Revision 1.2 2000/11/19 22:03:04 steve
+ Integer parameter comments.
+
+Revision 1.1 2000/07/23 18:06:31 steve
+ Document ieee1364 issues.</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-icarus_mp.html b/docs/wiki/geda-icarus_mp.html
new file mode 100644
index 0000000..f98d924
--- /dev/null
+++ b/docs/wiki/geda-icarus_mp.html
@@ -0,0 +1,377 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="icarus_verilog_compiler_man-page" id="icarus_verilog_compiler_man-page">Icarus Verilog compiler man-page</a></h1>
+<div class="level1">
+<pre class="code">iverilog(1) $Date: 2005/06/28 04:25:55 $ iverilog(1)
+
+
+
+NAME
+ iverilog - Icarus Verilog compiler
+
+
+SYNOPSIS
+ iverilog [-ESVv] [-Bpath] [-ccmdfile] [-g1|-g2|-g2x] [-Dmacro[=defn]]
+ [-pflag=value] [-Iincludedir] [-mmodule] [-Mfile] [-Nfile] [-ooutput-
+ filename] [-stopmodule] [-ttype] [-Tmin/typ/max] [-Wclass] [-ypath]
+ sourcefile
+
+
+DESCRIPTION
+ iverilog is a compiler that translates Verilog source code into exe-
+ cutable programs for simulation, or other netlist formats for further
+ processing. The currently supported targets are vvp for simulation, and
+ xnf and fpga for synthesis. Other target types are added as code gener-
+ ators are implemented.
+
+
+OPTIONS
+ iverilog accepts the following options:
+
+ -Bbase The iverilog program uses external programs and configuration
+ files to preprocess and compile the Verilog source. Normally,
+ the path used to locate these tools is built into the iverilog
+ program. However, the -B switch allows the user to select a
+ different set of programs. The path given is used to locate
+ ivlpp, ivl, code generators and the VPI modules.
+
+ -cfile This flag specifies an input file that contains a list of Ver-
+ ilog source files. This is similar to the command file of other
+ Verilog simulators, in that it is a file that contains the file
+ names instead of taking them on the command line. See Command
+ Files below.
+
+ -Dmacro Defines macro macro with the string ââ?¬Ë?1ââ?¬â?¢ as its definition. This
+ form is normally only used to trigger ifdef conditionals in the
+ Verilog source.
+
+ -Dmacro=defn
+ Defines macro macro as defn.
+
+ -E Preprocess the Verilog source, but do not compile it. The out-
+ put file is the Verilog input, but with file inclusions and
+ macro references expanded and removed. This is useful, for
+ example, to preprocess Verilog source for use by other compil-
+ ers.
+
+ -g1|-g2|-g2x
+ Select the Verilog language generation to support in the com-
+ piler. This selects between IEEE1364-1995(1), IEEE1364-2001(2),
+ or Verilog with extension(2x). Normally, Icarus Verilog
+ defaults to the latest known generation of the language. This
+ flag is most useful to restrict the language to a set supported
+ by tools of specific generations, for compatibility with other
+ tools.
+
+ -Iincludedir
+ Append directory includedir to list of directories searched for
+ Verilog include files. The -I switch may be used many times to
+ specify several directories to search, the directories are
+ searched in the order they appear on the command line.
+
+ -Mpath Write into the file specified by path a list of files that con-
+ tribute to the compilation of the design. This includes files
+ that are included by include directives and files that are
+ automatically loaded by library support. The output is one file
+ name per line, with no leading or trailing space.
+
+ -mmodule
+ Add this module to the list of VPI modules to be loaded by the
+ simulation. Many modules can be specified, and all will be
+ loaded, in the order specified. The system module is implicit
+ and always included.
+
+ -Npath This is used for debugging the compiler proper. Dump the final
+ netlist form of the design to the specified file. It otherwise
+ does not affect operation of the compiler. The dump happens
+ after the design is elaborated and optimized.
+
+ -o filename
+ Place output in the file filename. If no output file name is
+ specified, iverilog uses the default name a.out.
+
+ -pflag=value
+ Assign a value to a target specific flag. The -p switch may be
+ used as often as necessary to specify all the desired flags.
+ The flags that are used depend on the target that is selected,
+ and are described in target specific documentation. Flags that
+ are not used are ignored.
+
+ -S Synthesize. Normally, if the target can accept behavioral
+ descriptions the compiler will leave processes in behavioral
+ form. The -S switch causes the compiler to perform synthesis
+ even if it is not necessary for the target. If the target type
+ is a netlist format, the -S switch is unnecessary and has no
+ effect.
+
+ -s topmodule
+ Specify the top level module to elaborate. Icarus Verilog will
+ by default choose modules that are not instantiated in any
+ other modules, but sometimes that is not sufficient, or instan-
+ tiates too many modules. If the user specifies one or more root
+ modules with -s flags, then they will be used as root modules
+ instead.
+
+ -Tmin|typ|max
+ Use this switch to select min, typ or max times from
+ min:typ:max expressions. Normally, the compiler will simply use
+ the typ value from these expressions (with a warning) but this
+ switch will tell the compiler explicitly which value to use.
+ This will suppress the warning that the compiler is making a
+ choice.
+
+ -ttarget
+ Use this switch to specify the target output format. See the
+ TARGETS section below for a list of valid output formats.
+
+ -v Turn on verbose messages. This will print the command lines
+ that are executed to perform the actual compilation, along with
+ version information from the various components, as well as the
+ version of the product as a whole. You will notice that the
+ command lines include a reference to a key temporary file that
+ passes information to the compiler proper. To keep that file
+ from being deleted at the end of the process, provide a file
+ name of your own in the environment variable IVERILOG_ICONFIG.
+
+ -V Print the version of the compiler, and exit.
+
+ -Wclass Turn on different classes of warnings. See the WARNING TYPES
+ section below for descriptions of the different warning groups.
+ If multiple -W switches are used, the warning set is the union
+ of all the requested classes.
+
+ -ylibdir
+ Append the directory to the library module search path. When
+ the compiler finds an undefined module, it looks in these
+ directories for files with the right name.
+
+
+MODULE LIBRARIES
+ The Icarus Verilog compiler supports module libraries as directories
+ that contain Verilog source files. During elaboration, the compiler
+ notices the instantiation of undefined module types. If the user speci-
+ fies library search directories, the compiler will search the directory
+ for files with the name of the missing module type. If it finds such a
+ file, it loads it as a Verilog source file, they tries again to elabo-
+ rate the module.
+
+ Library module files should contain only a single module, but this is
+ not a requirement. Library modules may reference other modules in the
+ library or in the main design.
+
+
+TARGETS
+ The Icarus Verilog compiler supports a variety of targets, for differ-
+ ent purposes, and the -t switch is used to select the desired target.
+
+
+ null The null target causes no code to be generated. It is useful
+ for checking the syntax of the Verilog source.
+
+ vvp This is the default. The vvp target generates code for the vvp
+ runtime. The output is a complete program that simulates the
+ design but must be run by the vvp command.
+
+ xnf This is the Xilinx Netlist Format used by many tools for plac-
+ ing devices in FPGAs or other programmable devices. This target
+ is obsolete, use the fpga target instead.
+
+ fpga This is a synthesis target that supports a variety of fpga
+ devices, mostly by EDIF format output. The Icarus Verilog fpga
+ code generator can generate complete designs or EDIF macros
+ that can in turn be imported into larger designs by other
+ tools. The fpga target implies the synthesis -S flag.
+
+
+WARNING TYPES
+ These are the types of warnings that can be selected by the -W switch.
+ All the warning types (other then all) can also be prefixed with no- to
+ turn off that warning. This is most useful after a -Wall argument to
+ suppress isolated warning types.
+
+
+ all This enables all supported warning categories.
+
+
+ implicit
+ This enables warnings for creation of implicit declarations.
+ For example, if a scalar wire X is used but not declared in the
+ Verilog source, this will print a warning at its first use.
+
+
+ portbind
+ This enables warnings for ports of module instantiations that
+ are not connected but probably should be. Dangling input ports,
+ for example, will generate a warning.
+
+
+ timescale
+ This enables warnings for inconsistent use of the timescale
+ directive. It detects if some modules have no timescale, or if
+ modules inherit timescale from another file. Both probably mean
+ that timescales are inconsistent, and simulation timing can be
+ confusing and dependent on compilation order.
+
+
+SYSTEM FUNCTION TABLE FILES
+ If the source file name as a .sft suffix, then it is taken to be a sys-
+ tem function table file. A System function table file is used to
+ describe to the compiler the return types for system functions. This is
+ necessary because the compiler needs this information to elaborate
+ expressions that contain these system functions, but cannot run the
+ sizetf functions since it has no run-time.
+
+ The format of the table is ASCII, one function per line. Empty lines
+ are ignored, and lines that start with the �#� character are comment
+ lines. Each non-comment line starts with the function name, then the
+ vpi type (i.e. vpiSysFuncReal). The following types are supported:
+
+
+ vpiSysFuncReal
+ The function returns a real/realtime value.
+
+
+ vpiSysFuncInt
+ The function returns an integer.
+
+
+ vpiSysFuncSized <wid> <signed|unsigned>
+ The function returns a vector with the given width, and is
+ signed or unsigned according to the flag.
+
+
+COMMAND FILES
+ The command file allows the user to place source file names and certain
+ command line switches into a text file instead of on a long command
+ line. Command files can include C or C++ style comments, as well as #
+ comments, if the # starts the line.
+
+
+ file name
+ A simple file name or file path is taken to be the name of a
+ Verilog source file. The path starts with the first non-white-
+ space character. Variables are substitued in file names.
+
+
+ -y libdir
+ A -y token prefixes a library directory in the command file,
+ exactly like it does on the command line. The parameter to the
+ -y flag may be on the same line or the next non-comment line.
+
+ Variables in the libdir are substituted.
+
+
+ +incdir+includedir
+ The +incdir+ token in command files gives directories to search
+ for include files in much the same way that -I flags work on
+ the command line. The difference is that multiple +includedir
+ directories are valid parameters to a single +incdir+ token,
+ although you may also have multiple +incdir+ lines.
+
+ Variables in the includedir are substituted.
+
+
+ +libext+ext
+ The +libext token in command files fives file extensions to try
+ when looking for a library file. This is useful in conjunction
+ with -y flags to list suffixes to try in each directory before
+ moving on to the next library directory.
+
+
+ +libdir+dir
+ This is another way to specify library directories. See the -y
+ flag.
+
+
+ +libdir-nocase+dir
+ This is like the +libdir statement, but file names inside the
+ directories declared here are case insensitive. The missing
+ module name in a lookup need not match the file name case, as
+ long as the letters are correct. For example, "foo" matches
+ "Foo.v" but not "bar.v".
+
+
+ +define+NAME=value
+ The +define+ token is the same as the -D option on the command
+ line. The value part of the token is optional.
+
+
+ +toupper-filename
+ This token causes file names after this in the command file to
+ be translated to uppercase. This helps with situations where a
+ directory has passed through a DOS machine, and in the process
+ the file names become munged.
+
+
+ +tolower-filename
+ This is similar to the +toupper-filename hack described above.
+
+
+VARIABLES IN COMMAND FILES
+ In certain cases, iverilog supports variables in command files. These
+ are strings of the form "$(varname)", where varname is the name of the
+ environment variable to read. The entire string is replaced with the
+ contents of that variable. Variables are only substitued in contexts
+ that explicitly support them, including file and directory strings.
+
+ Variable values come from the operating system environment, and not
+ from preprocessor defines elsewhere in the file or the command line.
+
+
+EXAMPLES
+ These examples assume that you have a Verilog source file called
+ hello.v in the current directory
+
+ To compile hello.v to an executable file called a.out:
+
+ iverilog hello.v
+
+ To compile hello.v to an executable file called hello:
+
+ iverilog -o hello hello.v
+
+ To compile and run explicitly using the vvp runtime:
+
+ iverilog -ohello.vvp -tvvp hello.v
+
+ To compile hello.v to a file in XNF-format called hello.xnf
+
+ iverilog -txnf -ohello.xnf hello.v
+
+
+
+AUTHOR
+ Steve Williams (steve@xxxxxxxxxx)
+
+
+SEE ALSO
+ vvp(1), <http://www.icarus.com/eda/verilog/>
+
+
+COPYRIGHT
+ Copyright �© 2002 Stephen Williams
+
+ This document can be freely redistributed according to the terms of the
+ GNU General Public License version 2.0
+
+
+
+Version $Date: 2005/06/28 04:25:55 $ iverilog(1)</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-icarus_opcodes.html b/docs/wiki/geda-icarus_opcodes.html
new file mode 100644
index 0000000..961e601
--- /dev/null
+++ b/docs/wiki/geda-icarus_opcodes.html
@@ -0,0 +1,700 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="executable_instruction_opcodes" id="executable_instruction_opcodes">Executable Instruction Opcodes</a></h1>
+<div class="level1">
+<pre class="code">/*
+ * Copyright (c) 2001-2003 Stephen Williams (steve@xxxxxxxxxx)
+ *
+ * $Id: opcodes.txt,v 1.69 2005/11/26 17:16:05 steve Exp $
+ */
+
+
+
+EXECUTABLE INSTRUCTION OPCODES
+
+Instruction opcodes all start with a % character and have 0 or more
+operands. In no case are there more then 3 operands. This chapter
+describes the specific behavior of each opcode, in enough detail
+(I hope) that its complete effect can be predicted.
+
+General principles of Arithmetic:
+
+The binary arithmetic instruction in general take three parameters,
+the left operand, the right operand, and the base. The left operand is
+replaced with the result, which is the same width as the left and
+right operands.
+
+
+* %add <bit-l>, <bit-r>, <wid>
+
+This instruction adds the right vector into the left vector, the
+vectors having the width <wid>. If any of the bits of either vector
+are x or z, the result is x. Otherwise, the result is the arithmetic
+sum.
+
+See also the %sub instruction.
+
+
+* %add/wr <bit-l>, <bit-r>
+
+This is the real valued version of the %add instruction. The arguments
+are word indices of the operands. The right operand is added into the
+left operand.
+
+See also the %sub/wr instruction.
+
+
+* %addi <bit-l>, <imm>, <wid>
+
+This instruction adds the immediate value (no x or z bits) into the
+left vector. The imm value is limited to 16 significant bits, but it
+is zero extended to match any width.
+
+* %and <bit-l>, <bit-r>, <wid>
+
+Perform the bitwise AND of the two vectors, and store the result in
+the left vector. Each bit is calculated independent of other bits. AND
+means the following:
+
+ 0 and ? --> 0
+ ? and 0 --> 0
+ 1 and 1 --> 1
+ otherwise x
+
+* %assign/m <memory-label>, <delay>, <bit> (OBSOLETE)
+
+This instruction does a non-blocking assignment to a bit in a memory
+from the specified thread register <bit>. The memory bit is addressed
+by index register 3. Bit address zero is the LSB of the first memory
+word.
+
+* %assign/mv <memory-label>, <delay>, <bit>
+
+the %assign/mv instruction assigns a vector value to a word in the
+labeled memory. The <delay> is the delay in simulation time to the
+assignment (0 for non-blocking assignment) and the <bit> is the base
+of the vector to write.
+
+The width of the word is retrieved from index register 0.
+
+The address of the word in the memory is from index register 3. The
+address is canonical form.
+
+* %assign/v0 <var-label>, <delay>, <bit>
+* %assign/v0/d <var-label>, <delayx>, <bit>
+
+The %assign/v0 instruction is a vector version of non-blocking
+assignment. The <delay> is the number of clock ticks in the future
+where the assignment should be schedule, and the <bit> is the base of
+the vector to be assigned to the destination. The vector width is in
+index register 0.
+
+The %assign/v0/d variation puts the delay instead into an integer
+register that is given by the <delayx> value. This should not be 0, of
+course, because integer 0 is taken with the vector width.
+
+The <var-label> references a .var object that can receive non-blocking
+assignments. For blocking assignments, see %set/v.
+
+* %assign/v0x1 <var-label>, <delay>, <bit>
+
+This is similar to the %assign/v0 instruction, but adds the index-1
+index register with the canonical index of the destination where the
+vector is to be written. This allows for part writes into the vector.
+
+* %assign/wr <vpi-label>, <delay>, <index>
+
+This instruction causes a non-blocking assign of the indexed value to
+the real object addressed by the <vpi-label> label.
+
+* %assign/x0 <var-label>, <delay>, <bit> (OBSOLETE -- See %assign/v0x)
+
+This does a non-blocking assignment to a functor, similar to the
+%assign instruction. The <var-label> identifies the base functor of
+the affected variable, and the <delay> gives the delay when the
+assignment takes place. The delay may be 0. The actual functor used is
+calculated by using <var-label> as a base, and indexing with the
+index[0] index register. This supports indexed assignment.
+
+The <bit> is the address of the thread register that contains the bit
+value to assign.
+
+
+* %blend <bit-l>, <bit-r>, <wid>
+
+This instruction blends the bits of a vector into the destination in a
+manner like the expression (x ? <a> : <b>). The truth table is:
+
+ 1 1 --> 1
+ 0 0 --> 0
+ z z --> z
+ x x --> x
+ .... --> x
+
+In other words, if the bits are identical, then take that
+value. Otherwise, the value is x.
+
+* %breakpoint
+
+This instruction unconditionally breaks the simulator into the
+interactive debugger. The idea is to stop the simulator here and give
+the user a chance to display the state of the simulation using
+debugger commands.
+
+This may not work on all platforms. If run-time debugging is compiled
+out, then this function is a no-op.
+
+* %cassign/v <var-label>, <bit>, <wid>
+
+Perform a continuous assign of a constant value to the target
+variable. This is similar to %set, but it uses the cassign port
+(port-1) of the signal functor instead of the normal assign, so the
+signal responds differently. See "VARIABLE STATEMENTS" in the
+README.txt file.
+
+
+* %cmp/u <bit-l>, <bit-r>, <wid>
+* %cmp/s <bit-l>, <bit-r>, <wid>
+
+These instructions perform a generic comparison of two vectors of equal
+size. The <bit-l> and <bit-r> numbers address the least-significant
+bit of each vector, and <wid> is the width. If either operand is 0,
+1, 2 or 3 then it is taken to be a constant replicated to the selected
+width.
+
+The results of the comparison go into bits 4, 5, 6 and 7:
+
+ 4: eq (equal)
+ 5: lt (less than)
+ 6: eeq (case equal)
+
+The eeq bit is set to 1 if all the bits in the vectors are exactly the
+same, or 0 otherwise. The eq bit is true if the values are logically
+the same. That is, x and z are considered equal. In other words the eq
+bit is the same as ``=='' and the eeq bit ``===''.
+
+The lt bit is 1 if the left vector is less then the right vector, or 0
+if greater then or equal to the right vector. It is the equivalent of
+the Verilog < operator. Combinations of these three bits can be used
+to implement all the Verilog comparison operators.
+
+The %cmp/u and %cmp/s differ only in the handling of the lt bit. The
+%cmp/u does an unsigned compare, whereas the %cmp/s does a signed
+compare. In either case, if either operand contains x or z, then lt
+bit gets the x value.
+
+
+* %cmp/wr <bit-l>, <bit-r>
+
+[compare real values.]
+
+* %cmp/ws <bit-l>, <bit-r>
+* %cmp/wu <bit-l>, <bit-r>
+
+[compare signed/unsigned integer words.]
+
+* %cmp/z <bit-l>, <bit-r>, <wid>
+* %cmp/x <bit-l>, <bit-r>, <wid>
+
+These instructions are for implementing the casez and casex
+comparisons. These work similar to the %cmp/u instructions, except
+only an eq bit is calculated. These comparisons both treat z values in
+the left or right operand as don't care positions. The %cmp/x
+instruction will also treat x values in either operand as don't care.
+
+Only bit 4 is set by these instructions.
+
+
+* %cvt/ir <bit-l>, <bit-r>
+* %cvt/ri <bit-l>, <bit-r>
+* %cvt/vr <bit-l>, <bit-r>, <wid>
+
+Copy a word from r to l, converting it from real to integer (ir) or
+integer to real (ri) in the process. The source and destination may
+be the same word address, leading to a convert in place.
+
+The %cvt/vr opcode converts a real word <bit-r> to a thread vector
+starting at <bit-l> and with the width <wid>. Non-integer precision is
+lost in the conversion.
+
+* %deassign <var-label>
+
+Deactivate and disconnect a procedural continuous assignment to a
+variable. The <var-label> identifies the affected variable.
+
+* %delay <delay>
+
+This opcode pauses the thread, and causes it to be rescheduled for a
+time in the future. The <amount> is the number of the ticks in the
+future to reschedule, and is >= 0. If the %delay is zero, then the
+thread yields the processor for another thread, but will be resumed in
+the current time step.
+
+* %delayx <idx>
+
+This is similar to the %delay opcode, except that the parameter
+selects an index register, which contains the actual delay. This
+supports run-time calculated delays.
+
+* %disable <scope-label>
+
+This instruction terminates threads that are part of a specific
+scope. The label identifies the scope in question, and the threads are
+the threads that are currently within that scope.
+
+
+* %div <bit-l>, <bit-r>, <wid>
+* %div/s <bit-l>, <bit-r>, <wid>
+
+This instruction arithmetically divides the <bit-l> vector by the
+<bit-r> vector, and leaves the result in the <bit-l> vector. IF any of
+the bits in either vector are x or z, the entire result is x.
+
+The %div/s instruction is the same as %div, but does signed division.
+
+
+* %div/wr <bit-l>, <bit-r>
+
+This opcode divides the left operand by the right operand. If the
+right operand is 0, then the result is NaN.
+
+
+* %force/v <label>, <bit>, <wid>
+
+Force a constant value to the target variable. This is similar to %set
+and %cassign/v, but it uses the force port (port-2) of the signal
+functor instead of the normal assign port (port-0), so the signal
+responds differently. See "VARIABLE STATEMENTS" and "NET STATEMENTS"
+in the README.txt file.
+
+* %force/x0 <label>, <bit>, <wid>
+
+Force a constant value to part target variable. This is similar to
+%set/x instruction, but it uses the force port (port-2) of the signal
+functor instead of the normal assign port (port-0), so the signal
+responds differently. See "VARIABLE STATEMENTS" and "NET STATEMENTS"
+in the README.txt file.
+
+* %fork <code-label>, <scope-label>
+
+This instruction is similar to %jmp, except that it creates a new
+thread to start executing at the specified address. The new thread is
+created and pushed onto the child stack. It is also marked runnable,
+but is not necessarily started until the current thread yields.
+
+The %fork instruction has no effect other then to push a child thread.
+
+See also %join.
+
+
+* %inv <bit>, <wid>
+
+Perform a bitwise invert of the vector starting at <bit>. The result
+replaces the input. Invert means the following, independently for each
+bit:
+
+ 0 --> 1
+ 1 --> 0
+ x --> x
+ z --> x
+
+
+* %ix/get <idx>, <bit>, <wid>
+
+This instruction loads a thread vector starting at <bit>, size <wid>,
+into the index register <idx>. The <bit> is the lsb of the value in
+thread bit space, and <wid> is the width of the vector.
+
+The function converts the 4-value bits into a binary number, without
+sign extension. If any of the bits of the vector is x or z, then the
+index register gets the value 0.
+
+The function also writes into bit 4 a 1 if any of the bits of the
+input vector are x or z. This is a flag that the 0 value written into
+the index register is really the result of calculating from unknown
+bits.
+
+ 4: unknown value
+ 5: (reserved)
+ 6: (reserved)
+
+
+* %ix/load <idx>, <value>
+
+This instruction loads an immediate value into the addressed index
+register. The index register holds numeric values, so the <value> is a
+number. The idx value selects the index register, and may be 0, 1, 2
+or 3. This is different from %ix/get, which loads the index register
+from a value in the thread bit vector.
+
+
+* %ix/add <idx>, <value>
+* %ix/sub <idx>, <value>
+* %ix/mul <idx>, <value>
+
+This instruction adds, subtracts, or multiplies an immediate value to
+the addressed index register. The index register holds numeric values,
+so the <value> is a number. The <idx> value selects the index register,
+and may be 0, 1, 2 or 3.
+
+
+* %jmp <code-label>
+
+The %jmp instruction performs an unconditional branch to a given
+location. The parameter is the label of the destination instruction.
+
+* %jmp/[01xz] <code-label>, <bit>
+
+This is a conditional version of the %jmp instruction. In this case,
+a single bit (addressed by <bit>) is tested. If it is one of the
+values in the part after the /, the jump is taken. For example:
+
+ %jmp/xz T_label, 8;
+
+will jump to T_label if bit 8 is x or z.
+
+* %join
+
+This is the partner to %fork. This instruction causes the thread to
+wait for the top thread in the child stack to terminate, then
+continues. It has no effect in the current thread other then to wait
+until the top child is cleared.
+
+It is an error to execute %join if there are no children in the child
+stack. Every %join in the thread must have a matching %fork that
+spawned off a child thread.
+
+If the matching child instruction is still running, a %join suspends
+the calling thread until the child ends. If the child is already
+ended, then the %join does not block or yield the thread.
+
+* %load/m <bit>, <memory-label> (OBSOLETE)
+
+This instruction loads a value from a memory bit into the specified
+thread register bit. The memory bit is addressed by index register 3.
+Bit address zero is the LSB of the first memory word. This
+instruction loads only a single bit.
+
+* %load/mv <bit>, <memory-label>, <wid>
+
+this instruction loads a word from the specified memory. The word
+address is in index register 3. The width should match the width of
+the memory word.
+
+* %load/nx <bit>, <vpi-label>, <idx>
+
+This instruction load a value from a .net object bit. Since .net
+objects don't really exist (they are only named indirection into the
+netlist) this instruction indexes into the .net list of bits.
+
+* %load/v <bit>, <functor-label>, <wid>
+
+This instruction loads a vector value from the given functor node into
+the specified thread register bit. The functor-label can refer to a
+.net, a .var or a .functor with a vector output. The entire vector,
+from the least significant up to <wid> bits, is loaded starting at
+thread bit <bit>. It is an error for the width to not match the vector
+width at the functor.
+
+* %load/wr <bit>, <vpi-label>
+
+This instruction reads a real value from the vpi-like object to a word
+register.
+
+* %load/x <bit>, <functor-label>, <idx>
+* %load/x.p <bit>, <functor-label>, <idx>
+
+This is an indexed load. It uses the contents of the specified index
+register to select a bit from a vector functor at <functor-label>. The
+bit is pulled from the indexed bit of the addressed functor and loaded
+into the destination thread bit. If the indexed value is beyond the
+width of the vector, then the result is X.
+
+The %load/x.p is the same, but when the operation is done, it
+increments the specified index register. This provides a basic
+auto-increment feature.
+
+* %loadi/wr <bit>, <mant>, <exp>
+
+This opcode loads an immediate value, floating point, into the word
+register selected by <bit>. The mantissa is an unsigned integer value,
+up to 32 bits, that multiplied by 2**(<exp>-0x1000) to make a real
+value. The sign bit is OR-ed into the <exp> value at bit 0x2000, and
+is removed from the <exp> before calculating the real value.
+
+
+* %mod <bit-l>, <bit-r>, <wid>
+* %mod/s <bit-l>, <bit-r>, <wid>
+
+This instruction calculates the modulus %r of the left operand, and
+replaces the left operand with the result. The <wid> gives the width
+of the left and the right vectors, and the left vector is completely
+replaced with the result.
+
+The /s form does signed %.
+
+* %mov <dst>, <src>, <wid>
+
+This instruction copies a vector from one place in register space to
+another. The destination and source vectors are assumed to be the same
+width and non-overlapping. The <dst> may not be 0-3, but if the <src>
+is one of the 4 constant bits, the effect is to replicate the value
+into the destination vector. This is useful for filling a vector.
+
+
+* %mul <bit-l>, <bit-r>, <wid>
+
+This instruction multiplies the left vector by the right vector, the
+vectors having the width <wid>. If any of the bits of either vector
+are x or z, the result is x. Otherwise, the result is the arithmetic
+product.
+
+
+* %mul/wr <bit-l>, <bit-r>
+
+This opcode multiplies two real words together. The result replaces
+the left operand.
+
+
+* %muli <bit-l>, <imm>, <wid>
+
+This instruction is the same as %mul, but the second operand is an
+immediate value that is padded to the width of the result.
+
+
+* %nand <dst>, <src>, <wid>
+
+Perform the bitwise NAND of the two vectors, and store the result in
+the left vector. Each bit is calculated independent of other bits. NAND
+means the following:
+
+ 0 and ? --> 1
+ ? and 0 --> 1
+ 1 and 1 --> 0
+ otherwise x
+
+
+* %nor <dst>, <src>, <wid>
+
+Perform the bitwise nor of the vectors. Each bit in the <dst> is
+combined with the corresponding bit in the source, according to the
+truth table:
+
+ 1 nor ? --> 0
+ ? nor 1 --> 0
+ 0 nor 0 --> 1
+ otherwise x
+
+
+* %nor/r <dst>, <src>, <wid>
+
+The %nor/r instruction is a reduction nor. That is, the <src> is a
+vector with width, but the result is a single bit. The <src> vector is
+not affected by the operation unless the <dst> bit is within the
+vector. The result is calculated before the <dst> bit is written, so
+it is valid to place the <dst> within the <src>.
+
+The actual operation performed is the inverted or of all the bits in
+the vector.
+
+
+* %or <dst>, <src>, <wid>
+
+Perform the bitwise or of the vectors. Each bit in the <dst> is
+combined with the corresponding bit in the source, according to the
+truth table:
+
+ 1 or ? --> 1
+ ? or 1 --> 1
+ 0 or 0 --> 0
+ otherwise x
+
+
+* %or/r <dst>, <src>, <wid>
+
+This is a reduction version of the %or opcode. The <src> is a vector,
+and the <dst> is a writable scalar. The <dst> gets the value of the
+or of all the bits of the src vector.
+
+
+* %release/net <functor-label>
+* %release/reg <functor-label>
+
+Release the force on the signal that is represented by the functor
+<functor-label>. The force was previously activated with a %force/v
+statement. If no force was active on this functor the statement does
+nothing. The %release/net sends to the labeled functor the release
+command with net semantics: the unforced value is propagated to the
+output of the signal after the release is complete. The %release/reg
+sends the release command with reg semantics: the signal holds its
+forced value until another value propagates through.
+
+* %set/v <var-label>, <bit>, <wid>
+
+This sets a vector to a variable, and is used to implement blocking
+assignments. The <var-label> identifies the variable to receive the
+new value. Once the set completes, the value is immediately available
+to be read out of the variable. The <bit> is the address of the thread
+register that contains the LSB of the vector, and the <wid> is the
+size of the vector. The width must exactly match the width of the
+signal.
+
+* %set/mv <memory-label>, <bit>, <wid>
+
+This sets a thread vector to a memory word. The <memory-label>
+addresses a memory device, and the <bit>,<wid> describe a vector to be
+written. Index register 3 contains the address of the word within the
+memory. The address (in canonical form) is precalculated and loaded
+into index register 3.
+
+
+* %set/wr <vpi-label>, <bit>
+
+This instruction writes a real word to the specified VPI-like object.
+
+* %set/x0 <var-label>, <bit>, <wid>
+
+This sets the part of a signal vector, the address calculated by
+using the index register 0 to index the base within the vector of
+<var-label>. The destination must be a signal of some sort. Otherwise,
+the instruction will fail.
+
+The addressing is canonical (0-based) so the compiler must figure out
+non-zero offsets, if any. The width is the width of the part being
+written. The other bits of the vector are not touched.
+
+The index may be signed, and if less then 0, the beginning bits are
+not assigned. Also, if the bits go beyond the end of the signal, those
+bits are not written anywhere.
+
+
+* %shiftl/i0 <bit>, <wid>
+
+This instruction shifts the vector left (towards more significant
+bits) by the amount in index register 0. The <bit> is the address of
+the lsb of the vector, and <wid> the width of the vector. The shift is
+done in place. Zero values are shifted in.
+
+* %shiftr/i0 <bit>, <wid>
+* %shiftr/s/i0 <bit>, <wid>
+
+This instruction shifts the vector right (towards the less significant
+bits) by the amount in the index register 0. The <bit> is the address
+of the lsb of the vector, and <wid> is the width of the vector. The
+shift is done in place.
+
+%shiftr/i0 is an unsigned down shift, so zeros are shifted into the
+top bits. %shiftr/s/i0 is a signed shift, so the value is sign-extended.
+
+* %sub <bit-l>, <bit-r>, <wid>
+
+This instruction arithmetically subtracts the right vector out of the
+left vector. It accomplishes this by adding to the left vector 1 plus
+the 1s complement of the right vector. The carry value is dropped, and
+the result, placed in <bit-l>, is the subtraction of <bit-r> from the
+input <bit-l>. Both vectors have the same width. If any bits in either
+operand are x, then the entire result is x.
+
+See also the %add instruction.
+
+* %subi <bit-l>, <imm>, <wid>
+
+This instruction arithmetically subtracts the immediate value from the
+left vector. The <imm> value is a 16bit unsigned value zero-extended to
+the <wid> of the left vector. The result replaces the left vector.
+
+See also the %addi instruction.
+
+
+* %sub/wr <bit-l>, <bit-r>
+
+This instruction operates on real values in word registers. The right
+indexed value is subtracted from the left indexed value, and the
+result placed in the left index.
+
+
+* %vpi_call <name> [, ...]
+
+This instruction makes a call to a system task that was declared using
+VPI. The operands are compiled down to a vpiHandle for the call. The
+instruction contains only the vpiHandle for the call. See the vpi.txt
+file for more on system task/function calls.
+
+
+* %vpi_func <name>, <dst>, <wid> [, ...]
+
+This instruction is similar to %vpi_call, except that it is for
+calling system functions. The difference here is the <dst> and <wid>
+parameters that specify where the return value is to go. The normal
+means that the VPI code uses to write the return value causes those
+bits to go here.
+
+
+* %wait <functor-label>
+
+When a thread executes this instruction, it places itself in the
+sensitive list for the addressed functor. The functor holds all the
+threads that await the functor. When the defined sort of event occurs
+on the functor, a thread schedule event is created for all the threads
+in its list and the list is cleared.
+
+* %xnor <dst>, <src>, <wid>
+
+This does a bitwise exclusive nor (~^) of the <src> and <dst> vector,
+and leaves the result in the <dst> vector. xnor is this:
+
+ 0 xnor 0 --> 1
+ 0 xnor 1 --> 0
+ 1 xnor 0 --> 0
+ 1 xnor 1 --> 1
+ otherwise x
+
+
+* %xor <dst>, <src>, <wid>
+
+This does a bitwise exclusive or (^) of the <src> and <dst> vector,
+and leaves the result in the <dst> vector. xor is this:
+
+ 0 xnor 0 --> 0
+ 0 xnor 1 --> 1
+ 1 xnor 0 --> 1
+ 1 xnor 1 --> 0
+ otherwise x
+
+
+/*
+ * Copyright (c) 2001-2003 Stephen Williams (steve@xxxxxxxxxx)
+ *
+ * This source code is free software; you can redistribute it
+ * and/or modify it in source code form under the terms of the GNU
+ * General Public License as published by the Free Software
+ * Foundation; either version 2 of the License, or (at your option)
+ * any later version.
+ *
+ * This program is distributed in the hope that it will be useful,
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ * GNU General Public License for more details.
+ *
+ * You should have received a copy of the GNU General Public License
+ * along with this program; if not, write to the Free Software
+ * Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA
+ */</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-icarus_quick_start.html b/docs/wiki/geda-icarus_quick_start.html
new file mode 100644
index 0000000..068bbf3
--- /dev/null
+++ b/docs/wiki/geda-icarus_quick_start.html
@@ -0,0 +1,104 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="getting_started_with_icarus_verilog" id="getting_started_with_icarus_verilog">Getting Started with Icarus Verilog</a></h1>
+<div class="level1">
+<pre class="code">* Getting Started with Icarus Verilog
+
+Icarus Verilog is a Verilog compiler. It is suitable for use as a
+simulator, and, to some degree, synthesizer. Icarus Verilog runs under
+Linux and a variety of UNIX systems, as well as Windows as a command
+line tool, so the instructions are generally applicable to all
+environments. Note that this is only a quick start. For more detailed
+documentation, see the manual page for the iverilog command.
+
+
+* Hello, World!
+
+The first thing you want to do as a user is learn how to compile and
+execute even the most trivial design. For the purposes of simulation,
+we use as our example *the* most trivial simulation:
+
+ module main;
+
+ initial
+ begin
+ $display("Hello, World");
+ $finish ;
+ end
+
+ endmodule
+
+By a text editor (or copy hello.vl from the Icarus Verilog examples
+directory) arrange for this program to be in a text file, "hello.vl".
+Next, compile this program with a command like this:
+
+ % iverilog -o hello hello.vl
+
+The results of this compile are placed into the file "hello", as the
+"-o" flag tells the compiler where to place the compiled result. Next,
+execute the compiled program like so:
+
+ % vvp hello
+ Hello, World
+
+And there it is, the program has been executed. So what happened? The
+first step, the "iverilog" command, read and interpreted the source
+file, then generated a compiled result. The compiled form may be
+selected by command line switches, but the default form is the VVP
+format, which is actually run by the "vvp" command.
+
+The "iverilog" and "vvp" commands are the only commands that users
+use to invoke Icarus Verilog. What the compiler actually does is
+controlled by command line switches. In our little example, we asked
+the compiler to compile the source program to the default vvp form,
+which is in turn executed by the vvp program.
+
+
+* Windows Install
+
+The easiest way to install under Windows is to get a precompiled
+installer for the version you wish to install. Icarus Verilog is
+distributed for Windows users as a self-installing .exe. Just execute
+the installer and follow the instructions. During the install, take
+note of the directory where the program is installed: for example,
+C:\iverilog is a good place to install.
+
+Once the binary is installed, you need to add the bin directory to
+your execution path. The executables you need are in C:\iverilog\bin,
+where the "C:\iverilog" part is actually the root of where you
+installed the package. The programs are in the bin subdirectory. Put
+this directory in your PATH environment variable, and the above
+commands become accessible to you at the command line prompt, or even
+in batch files.
+
+
+* Linux Install
+
+Under Linux, the install is even easier. For RedHat and Mandrake based
+systems, there is the appropriate RPM file. Just install the package
+with the "rpm -U <file>" command. Debian users should get Icarus
+Verilog packages from the main Debian software site.
+
+
+* Install From Source
+
+In this case, see README.txt and other documentation that comes with
+the source.</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-icarus_readme.html b/docs/wiki/geda-icarus_readme.html
new file mode 100644
index 0000000..2ea4a48
--- /dev/null
+++ b/docs/wiki/geda-icarus_readme.html
@@ -0,0 +1,517 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="the_icarus_verilog_compilation_system" id="the_icarus_verilog_compilation_system">The Icarus Verilog Compilation System</a></h1>
+<div class="level1">
+<pre class="code"> THE ICARUS VERILOG COMPILATION SYSTEM
+ Copyright 2000-2004 Stephen Williams
+
+
+1.0 What is ICARUS Verilog?
+
+Icarus Verilog is intended to compile ALL of the Verilog HDL as
+described in the IEEE-1364 standard. Of course, it's not quite there
+yet. It does currently handle a mix of structural and behavioral
+constructs. For a view of the current state of Icarus Verilog, see its
+home page at <http://www.icarus.com/eda/verilog>.
+
+Icarus Verilog is not aimed at being a simulator in the traditional
+sense, but a compiler that generates code employed by back-end
+tools. These back-end tools currently include a simulator engine
+called VVP, an XNF (Xilinx Netlist Format) generator and an EDIF FPGA
+netlist generator. In the future, backends are expected for EDIF/LPM,
+structural Verilog, VHDL, etc.
+
+ For instructions on how to run Icarus Verilog,
+ see the ``iverilog'' man page.
+
+
+2.0 Building/Installing Icarus Verilog From Source
+
+If you are starting from source, the build process is designed to be
+as simple as practical. Someone basically familiar with the target
+system and C/C++ compilation should be able to build the source
+distribution with little effort. Some actual programming skills are
+not required, but helpful in case of problems.
+
+If you are building for Windows, see the mingw.txt file.
+
+2.1 Compile Time Prerequisites
+
+You need the following software to compile Icarus Verilog from source
+on a UNIX-like system:
+
+ - GNU Make
+ The Makefiles use some GNU extensions, so a basic POSIX
+ make will not work. Linux systems typically come with a
+ satisfactory make. BSD based systems (i.e., NetBSD, FreeBSD)
+ typically have GNU make as the gmake program.
+
+ - ISO C++ Compiler
+ The ivl and ivlpp programs are written in C++ and make use
+ of templates and some of the standard C++ library. egcs and
+ recent gcc compilers with the associated libstdc++ are known
+ to work. MSVC++ 5 and 6 are known to definitely *not* work.
+
+ - bison and flex
+
+ - gperf 2.7
+ The lexical analyzer doesn't recognize keywords directly,
+ but instead matches symbols and looks them up in a hash
+ table in order to get the proper lexical code. The gperf
+ program generates the lookup table.
+
+ A version problem with this program is the most common cause
+ of difficulty. See the Icarus Verilog FAQ.
+
+ - readline 4.2
+ On Linux systems, this usually means the readline-devel
+ rpm. In any case, it is the development headers of readline
+ that are needed.
+
+ - termcap
+ The readline library in turn uses termcap.
+
+If you are building from CVS, you will also need software to generate
+the configure scripts.
+
+ - autoconf 2.53
+ This generates configure scripts from configure.in. The 2.53
+ or later versions are known to work, autoconf 2.13 is
+ reported to *not* work.
+
+2.2 Compilation
+
+Unpack the tar-ball and cd into the verilog-######### directory
+(presumably that is how you got to this README) and compile the source
+with the commands:
+
+ ./configure
+ make
+
+Normally, this command automatically figures out everything it needs
+to know. It generally works pretty well. There are a few flags to the
+configure script that modify its behavior:
+
+ --without-ipal
+ This turns off support for Icarus PAL, whether ipal
+ libraries are installed or not.
+
+ --prefix=<root>
+ The default is /usr/local, which causes the tool suite to
+ be compiled for install in /usr/local/bin,
+ /usr/local/share/ivl, etc.
+
+ I recommend that if you are configuring for precompiled
+ binaries, use --prefix=/usr. On Solaris systems, it is
+ common to use --prefix=/opt. You can configure for a non-root
+ install with --prefix=$HOME.
+
+ --enable-vvp32 (experimental)
+ If compiling on AMD64 systems, this enables the
+ compilation of 32bit compatible vvp (vvp32) and the vpi
+ modules that match.
+
+2.2.1 Special AMD64 Instructions
+
+(The Icarus Verilog RPM for x86_64 is build using these instructions.)
+
+If you are building for Linux/AMD64 (a.k.a x86_64) then to get the
+most out of your install, first make sure you have both 64bit and
+32bit development libraries installed. Then configure with this
+somewhat more complicated command:
+
+ ./configure libdir64='$(prefix)/lib64' vpidir1=vpi64 vpidir2=. --enable-vvp32
+
+This reflects the convention on AMD64 systems that 64bit libraries go
+into lib64 directories. The "--enable-vvp32" also turns on 32bit
+compatibility files. A 32bit version of vvp (vvp32) will be created,
+as well as 32bit versions of the development libraries and bundled VPI
+libraries.
+
+2.3 (Optional) Testing
+
+To run a simple test before installation, execute
+
+ make check
+
+The commands printed by this run might help you in running Icarus
+Verilog on your own Verilog sources before the package is installed
+by root.
+
+2.4 Installation
+
+Now install the files in an appropriate place. (The makefiles by
+default install in /usr/local unless you specify a different prefix
+with the --prefix=<path> flag to the configure command.) You may need
+to do this as root to gain access to installation directories.
+
+ make install
+
+2.5 Uninstallation
+
+The generated Makefiles also include the uninstall target. This should
+remove all the files that ``make install'' creates.
+
+3.0 How Icarus Verilog Works
+
+This tool includes a parser which reads in Verilog (plus extensions)
+and generates an internal netlist. The netlist is passed to various
+processing steps that transform the design to more optimal/practical
+forms, then is passed to a code generator for final output. The
+processing steps and the code generator are selected by command line
+switches.
+
+3.1 Preprocessing
+
+There is a separate program, ivlpp, that does the preprocessing. This
+program implements the `include and `define directives producing
+output that is equivalent but without the directives. The output is a
+single file with line number directives, so that the actual compiler
+only sees a single input file. See ivlpp/ivlpp.txt for details.
+
+3.2 Parse
+
+The Verilog compiler starts by parsing the Verilog source file. The
+output of the parse is a list of Module objects in "pform". The pform
+(see pform.h) is mostly a direct reflection of the compilation
+step. There may be dangling references, and it is not yet clear which
+module is the root.
+
+One can see a human readable version of the final pform by using the
+``-P <path>'' flag to the compiler. This will cause iverilog to dump
+the pform into the file named <path>.
+
+3.3 Elaboration
+
+This phase takes the pform and generates a netlist. The driver selects
+(by user request or lucky guess) the root module to elaborate,
+resolves references and expands the instantiations to form the design
+netlist. (See netlist.txt.) Final semantic checks are performed during
+elaboration, and some simple optimizations are performed. The netlist
+includes all the behavioral descriptions, as well as gates and wires.
+
+The elaborate() function performs the elaboration.
+
+One can see a human readable version of the final, elaborated and
+optimized netlist by using the ``-N <path>'' flag to the compiler. If
+elaboration succeeds, the final netlist (i.e., after optimizations but
+before code generation) will be dumped into the file named <path>.
+
+Elaboration is actually performed in two steps: scopes and parameters
+first, followed by the structural and behavioral elaboration.
+
+3.3.1 Scope Elaboration
+
+This pass scans through the pform looking for scopes and parameters. A
+tree of NetScope objects is built up and placed in the Design object,
+with the root module represented by the root NetScope object. The
+elab_scope.cc and elab_pexpr.cc files contain most of the code for
+handling this phase.
+
+The tail of the elaborate_scope behavior (after the pform is
+traversed) includes a scan of the NetScope tree to locate defparam
+assignments that were collected during scope elaboration. This is when
+the defparam overrides are applied to the parameters.
+
+3.3.2 Netlist Elaboration
+
+After the scopes and parameters are generated and the NetScope tree
+fully formed, the elaboration runs through the pform again, this time
+generating the structural and behavioral netlist. Parameters are
+elaborated and evaluated by now so all the constants of code
+generation are now known locally, so the netlist can be generated by
+simply passing through the pform.
+
+3.4 Optimization
+
+This is actually a collection of processing steps that perform
+optimizations that do not depend on the target technology. Examples of
+some useful transformations are
+
+ - eliminate null effect circuitry
+ - combinational reduction
+ - constant propagation
+
+The actual functions performed are specified on the ivl command line by
+the -F flags (see below).
+
+3.5 Code Generation
+
+This step takes the design netlist and uses it to drive the code
+generator (see target.h). This may require transforming the
+design to suit the technology.
+
+The emit() method of the Design class performs this step. It runs
+through the design elements, calling target functions as need arises
+to generate actual output.
+
+The user selects the target code generator with the -t flag on the
+command line.
+
+3.6 ATTRIBUTES
+
+ NOTE: The $attribute syntax will soon be deprecated in favor of the
+ Verilog-2001 attribute syntax, which is cleaner and standardized.
+
+The parser accepts, as an extension to Verilog, the $attribute module
+item. The syntax of the $attribute item is:
+
+ $attribute (<identifier>, <key>, <value>);
+
+The $attribute keyword looks like a system task invocation. The
+difference here is that the parameters are more restricted then those
+of a system task. The <identifier> must be an identifier. This will be
+the item to get an attribute. The <key> and <value> are strings, not
+expressions, that give the key and the value of the attribute to be
+attached to the identified object.
+
+Attributes are [<key> <value>] pairs and are used to communicate with
+the various processing steps. See the documentation for the processing
+step for a list of the pertinent attributes.
+
+Attributes can also be applied to gate types. When this is done, the
+attribute is given to every instantiation of the primitive. The syntax
+for the attribute statement is the same, except that the <identifier>
+names a primitive earlier in the compilation unit and the statement is
+placed in global scope, instead of within a module. The semicolon is
+not part of a type attribute.
+
+Note that attributes are also occasionally used for communication
+between processing steps. Processing steps that are aware of others
+may place attributes on netlist objects to communicate information to
+later steps.
+
+Icarus Verilog also accepts the Verilog 2001 syntax for
+attributes. They have the same general meaning as with the $attribute
+syntax, but they are attached to objects by position instead of by
+name. Also, the key is a Verilog identifier instead of a string.
+
+4.0 Running iverilog
+
+The preferred way to invoke the compiler is with the iverilog(1)
+command. This program invokes the preprocessor (ivlpp) and the
+compiler (ivl) with the proper command line options to get the job
+done in a friendly way. See the iverilog(1) man page for usage details.
+
+
+4.1 EXAMPLES
+
+Example: Compiling "hello.vl"
+
+------------------------ hello.vl ----------------------------
+module main();
+
+initial
+ begin
+ $display("Hi there");
+ $finish ;
+ end
+
+endmodule
+
+--------------------------------------------------------------
+
+Ensure that "iverilog" is on your search path, and the vpi library
+is available.
+
+To compile the program:
+
+ iverilog hello.vl
+
+(The above presumes that /usr/local/include and /usr/local/lib are
+part of the compiler search path, which is usually the case for gcc.)
+
+To run the program:
+
+ ./a.out
+
+You can use the "-o" switch to name the output command to be generated
+by the compiler. See the iverilog(1) man page.
+
+5.0 Unsupported Constructs
+
+Icarus Verilog is in development - as such it still only supports a
+(growing) subset of Verilog. Below is a description of some of the
+currently unsupported Verilog features. This list is not exhaustive,
+and does not account for errors in the compiler. See the Icarus
+Verilog web page for the current state of support for Verilog, and in
+particular, browse the bug report database for reported unsupported
+constructs.
+
+ - System functions are supported, but the return value is a little
+ tricky. See SYSTEM FUNCTION TABLE FILES in the iverilog man page.
+
+ - Specify blocks are parsed but ignored in general.
+
+ - trireg is not supported. tri0 and tri1 are supported.
+
+ - tran primitives, i.e. tran, tranif1, tranif0, rtran, rtranif1
+ and rtranif0 are not supported.
+
+ - Net delays, of the form "wire #N foo;" do not work. Delays in
+ every other context do work properly, including the V2001 form
+ "wire #5 foo = bar;"
+
+ - Event controls inside non-blocking assignments are not supported.
+ i.e.: a <= @(posedge clk) b;
+
+ - Macro arguments are not supported. `define macros are supported,
+ but they cannot take arguments.
+
+5.1 Nonstandard Constructs or Behaviors
+
+Icarus Verilog includes some features that are not part of the
+IEEE1364 standard, but have well defined meaning, and also sometimes
+gives nonstandard (but extended) meanings to some features of the
+language that are defined. See the "extensions.txt" documentation for
+more details.
+
+ $is_signed(<expr>)
+ This system function returns 1 if the expression contained is
+ signed, or 0 otherwise. This is mostly of use for compiler
+ regression tests.
+
+ $sizeof(<expr>)
+ $bits(<expr>)
+ The $bits system function returns the size in bits of the
+ expression that is its argument. The result of this
+ function is undefined if the argument doesn't have a
+ self-determined size.
+
+ The $sizeof function is deprecated in favor of $bits, which is
+ the same thing, but included in the SystemVerilog definition.
+
+ $simtime
+ The $simtime system function returns as a 64bit value the
+ simulation time, unscaled by the time units of local
+ scope. This is different from the $time and $stime functions
+ which return the scaled times. This function is added for
+ regression testing of the compiler and run time, but can be
+ used by applications who really want the simulation time.
+
+ Note that the simulation time can be confusing if there are
+ lots of different `timescales within a design. It is not in
+ general possible to predict what the simulation precision will
+ turn out to be.
+
+ $mti_random()
+ $mti_dist_uniform
+ These functions are similar to the IEEE1364 standard $random
+ functions, but they use the Mersenne Twister (MT19937)
+ algorithm. This is considered an excellent random number
+ generator, but does not generate the same sequence as the
+ standardized $random.
+
+ Builtin system functions
+
+ Certain of the system functions have well defined meanings, so
+ can theoretically be evaluated at compile time, instead of
+ using runtime VPI code. Doing so means that VPI cannot
+ override the definitions of functions handled in this
+ manner. On the other hand, this makes them synthesizable, and
+ also allows for more aggressive constant propagation. The
+ functions handled in this manner are:
+
+ $bits
+ $signed
+ $sizeof
+ $unsigned
+
+ Implementations of these system functions in VPI modules will
+ be ignored.
+
+ Preprocessing Library Modules
+
+ Icarus Verilog does preprocess modules that are loaded from
+ libraries via the -y mechanism. However, the only macros
+ defined during compilation of that file are those that it
+ defines itself (or includes) or that are defined on the
+ command line or command file.
+
+ Specifically, macros defined in the non-library source files
+ are not remembered when the library module is loaded. This is
+ intentional. If it were otherwise, then compilation results
+ might vary depending on the order that libraries are loaded,
+ and that is too unpredictable.
+
+ It is said that some commercial compilers do allow macro
+ definitions to span library modules. That's just plain weird.
+
+ Width in %t Time Formats
+
+ Standard Verilog does not allow width fields in the %t formats
+ of display strings. For example, this is illegal:
+
+ $display("Time is %0t", %time);
+
+ Standard Verilog instead relies on the $timeformat to
+ completely specify the format.
+
+ Icarus Verilog allows the programmer to specify the field
+ width. The "%t" format in Icarus Verilog works exactly as it
+ does in standard Verilog. However, if the programmer chooses
+ to specify a minimum width (i.e., "%5t"), then for that display
+ Icarus Verilog will override the $timeformat minimum width and
+ use the explicit minimum width.
+
+ vpiScope iterator on vpiScope objects.
+
+ In the VPI, the normal way to iterate over vpiScope objects
+ contained within a vpiScope object, is the vpiInternalScope
+ iterator. Icarus Verilog adds support for the vpiScope
+ iterator of a vpiScope object, that iterates over *everything*
+ the is contained in the current scope. This is useful in cases
+ where one wants to iterate over all the objects in a scope
+ without iterating over all the contained types explicitly.
+
+ time 0 race resolution.
+
+ Combinational logic is routinely modeled using always
+ blocks. However, this can lead to race conditions if the
+ inputs to the combinational block are initialized in initial
+ statements. Icarus Verilog slightly modifies time 0 scheduling
+ by arranging for always statements with ANYEDGE sensitivity
+ lists to be scheduled before any other threads. This causes
+ combinational always blocks to be triggered when the values in
+ the sensitivity list are initialized by initial threads.
+
+ Nets with Types
+
+ Icarus Verilog support an extension syntax that allows nets
+ and regs to be explicitly typed. The currently supported types
+ are logic, bool and real. This implies that "logic" and "bool"
+ are new keywords. Typical syntax is:
+
+ wire real foo = 1.0;
+ reg logic bar, bat;
+
+ ... and so forth. The syntax can be turned off by using the
+ -g2 flag to iverilog, and turned on explicitly with the -g2x
+ flag to iverilog.
+
+6.0 CREDITS
+
+Except where otherwise noted, Icarus Verilog, ivl and ivlpp are
+Copyright Stephen Williams. The proper notices are in the head of each
+file. However, I have early on received aid in the form of fixes,
+Verilog guidance, and especially testing from many people. Testers in
+particular include a larger community of people interested in a GPL
+Verilog for Linux.</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-icarus_vpi_mp.html b/docs/wiki/geda-icarus_vpi_mp.html
new file mode 100644
index 0000000..f3a8a41
--- /dev/null
+++ b/docs/wiki/geda-icarus_vpi_mp.html
@@ -0,0 +1,143 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="compile_front_end_for_vpi_modules_man-page" id="compile_front_end_for_vpi_modules_man-page">Compile front end for VPI modules man-page</a></h1>
+<div class="level1">
+<pre class="code">iverilog-vpi(1) $Date: 2004/10/04 01:10:53 $ iverilog-vpi(1)
+
+
+
+NAME
+ iverilog-vpi - Compile front end for VPI modules
+
+
+SYNOPSIS
+ iverilog-vpi [--name=name] sourcefile...
+
+
+DESCRIPTION
+ iverilog-vpi is a tool to simplify the compilation of VPI modules for
+ use with Icarus Verilog. It takes on the command line a list of C or
+ C++ source files, and generates as output a linked VPI module. See the
+ vvp(1) man page for a description of how the linked module is loaded by
+ a simulation.
+
+ The output is named after the first source file. For example, if the
+ first source file is named foo.c, the output becomes foo.vpi.
+
+
+OPTIONS
+ iverilog-vpi accepts the following options:
+
+ -llibrary
+ Include the named library in the link of the VPI module. This
+ allows VPI modules to further reference external libraries.
+
+
+ --name=name
+ Normally, the output VPI module will be named after the first
+ source file passed to the command. This flag sets the name
+ (without the .vpi suffix) of the output vpi module.
+
+
+ --install-dir
+ This flag causes the program to print the install directory for
+ VPI modules, then exit. It is a convenience for makefiles or
+ automated plug-in installers.
+
+
+PC-ONLY OPTIONS
+ The PC port of iverilog-vpi includes two special flags needed to sup-
+ port the more intractable development environment. These flags help the
+ program locate parts that it needs.
+
+
+ -mingw=path
+ Tell the program the root of the Mingw compiler tool suite. The
+ vvp runtime is compiled with this compiler, and this is the
+ compiler that iverilog-vpi expects to use to compile your
+ source code. This is normally not needed, and if you do use it,
+ it is only needed once. The compiler will save the path in the
+ registry for use later.
+
+
+ -ivl=path
+ Set for the use during compilation the root if the Icarus Ver-
+ ilog install. This is the place where you installed Icarus Ver-
+ ilog when you ran the installer. This flag is also only needed
+ once, and the path is stored in the registry for future use.
+
+
+UNIX-ONLY OPTIONS
+ The UNIX version of iverilog-vpi includes additional flags to let Make-
+ file gurus peek at the configuration of the iverilog installation.
+ This way, Makefiles can be written that handle complex VPI builds
+ natively, and without hard-coding values that depend on the system and
+ installation. If used at all, these options must be used one at a
+ time, and without any other options or directives.
+
+
+ --cflags
+ Print the compiler flags (CFLAGS or CXXFLAGS) needed to compile
+ source code destined for a VPI module.
+
+
+ --ldflags
+ Print the linker flags (LDFLAGS) needed to link a VPI module.
+
+
+ --ldlibs
+ Print the libraries (LDLIBS) needed to link a VPI module.
+
+
+ -m32 On 64bit systems that support it (and support vvp32) this flag
+ requests a 32bit vpi binary instead of the default 64bit
+ binary.
+
+
+ Example GNU makefile that takes advantage of these flags:
+
+ CFLAGS = -Wall -O $(CFLAGS_$@)
+ VPI_CFLAGS := $(shell iverilog-vpi --cflags)
+ CFLAGS_messagev.o = $(VPI_CFLAGS)
+ CFLAGS_fifo.o = $(VPI_CFLAGS)
+ messagev.o fifo.o: transport.h
+ messagev.vpi: messagev.o fifo.o
+ iverilog-vpi $^
+
+
+AUTHOR
+ Steve Williams (steve@xxxxxxxxxx)
+
+
+SEE ALSO
+ iverilog(1), vvp(1), <http://www.icarus.com/eda/verilog/>,
+ <http://www.mingw.org>,
+
+
+COPYRIGHT
+ Copyright �© 2002 Stephen Williams
+
+ This document can be freely redistributed according to the terms of the
+ GNU General Public License version 2.0
+
+
+
+Version $Date: 2004/10/04 01:10:53 $ iverilog-vpi(1)</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-icarus_vpi_within_vvp.html b/docs/wiki/geda-icarus_vpi_within_vvp.html
new file mode 100644
index 0000000..104378d
--- /dev/null
+++ b/docs/wiki/geda-icarus_vpi_within_vvp.html
@@ -0,0 +1,188 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="vpi_within_vvp" id="vpi_within_vvp">VPI_within_VVP</a></h1>
+<div class="level1">
+<pre class="code">/*
+ * Copyright (c) 2001 Stephen Williams (steve@xxxxxxxxxx)
+ *
+ * $Id: vpi.txt,v 1.7 2003/02/09 23:33:26 steve Exp $
+ */
+
+
+VPI WITHIN VVP
+
+System tasks and functions in Verilog are implemented in Icarus
+Verilog by C routines written with VPI. This implies that the vvp
+engine must provide at least a subset of the Verilog VPI
+interface. The minimalist concepts of vvp, however, make the method
+less then obvious.
+
+Within a Verilog design, there is a more or less fixed web of
+vpiHandles that is the design database as is available to VPI
+functions. The Verilog standard defines quite a lot of types, but the
+vvp only implements the ones it needs. The VPI web is added into the
+design using special pseudo-ops that create the needed objects.
+
+
+LOADING VPI MODULES
+
+The vvp runtime loads VPI modules at runtime before the parser reads
+in the source files. This gives the modules a chance to register tasks
+and functions before the source is compiled. This allows the compiler
+to resolve references to system tasks and system functions to a
+vpiHandle at compile time. References to missing tasks/function can
+thus be caught before the simulation is run.
+
+ NOTE: This also, miraculously, allows for some minimal support of
+ the compiletf call. From the perspective of VPI code, compilation
+ of the VVP source is not unlike compilation of the original
+ Verilog.
+
+The handle that the vvp threads have to the VPI are the vpiHandles of
+the system tasks and functions. The %vpi_call instruction, once compiled,
+carries the vpiHandle of the system task.
+
+
+SYSTEM TASK CALLS
+
+A system task call invokes a VPI routine, and makes available to that
+routine the arguments to the system task. The called routine gets
+access to the system task call by calling back the VPI requesting the
+handle. It uses the handle, in turn, to get hold of the operands for
+the task.
+
+All that vvp needs to know about a system task call is the handle of
+the system task definitions (created by the vpi_register_systf
+function) and the arguments of the actual call. The arguments are
+tricky because the list has no bound, even though each particular call
+in the Verilog source has a specific set of parameters.
+
+Since each call takes a fixed number of parameters, the input source
+can include in the statement the list of arguments. The argument list
+will not fit in a single generated instruction, but a vpiHandle that
+refers to a vpiSysTfCall does. Therefore, the compiler can take the
+long argument list and form a vpiSysTaskCall object. The generated
+instruction then only needs to be a %vpi_call with the single parameter
+that is the vpiHandle for the call.
+
+
+SYSTEM FUNCTION CALLS
+
+System function calls are similar to system tasks. The only
+differences are that all the arguments are input only, and there is a
+single magic output that is the return value. The same %vpi_call can
+even be used to call a function.
+
+System functions, like system tasks, can only be called from thread
+code. However, they can appear in expressions, even when that
+expression is entirely structural. The desired effect is achieved by
+writing a wrapper thread that calls the function when inputs change,
+and that writes the output into the containing expression.
+
+
+SYSTEM TASK/FUNCTION ARGUMENTS
+
+The arguments to each system task or call are not stored in the
+instruction op-code, but in the vpiSysTfCall object that the compiler
+creates and that the %vpi_call instruction ultimately refers to. All
+the arguments must be some sort of object that can be represented by a
+vpiHandle at compile time.
+
+Arguments are handled at compile time by the parser, which uses the
+argument_list rule to build a list of vpiHandle objects. Each argument
+in the argument_list invokes whatever function is appropriate for the
+token in order to make a vpiHandle object for the argument_list. When
+all this is done, an array of vpiHandles is passed to code to create a
+vpiSysTfCall object that has all that is needed to make the call.
+
+
+SCOPES
+
+VPI can access scopes as objects of type vpiScope. Scopes have names
+and can also contain other sub-scopes, all of which the VPI function
+can access by the vpiInternalScope reference. Therefore, the run-time
+needs to form a tree of scopes into which other scoped VPI objects are
+placed.
+
+A scope is created with a .scope directive, like so:
+
+ <label> .scope "name" [, <parent>];
+ .timescale <units>;
+
+The scope takes a string name as the first parameter. If there is an
+additional parameter, it is a label of the directive for the parent
+scope. Scopes that have no parent are root scopes. It is an error to
+declare a scope with the same name more then once in a parent scope.
+
+The name string given when creating the scope is the basename for the
+scope. The vvp automatically constructs full names from the scope
+hierarchy, and runtime VPI code can access that full name with the
+vpiFullname reference.
+
+The .timescale directive changes the scope units from the simulation
+precision to the specified precision. The .timescale directive affects
+the current scope.
+
+Objects that place themselves in a scope place themselves in the
+current scope. The current scope is the one that was last mentioned by
+a .scope directive. If the wrong scope is current, the label on a
+scope directive can be used to resume a scope. The syntax works like
+this:
+
+ .scope <symbol>;
+
+In this case, the <symbol> is the label of a previous scope directive,
+and is used to identify the scope to be resumed. A scope resume
+directive cannot have a label.
+
+
+VARIABLES
+
+Reg vectors (scalars are vectors of length 1) are created by .var
+statements in the source. The .var statement includes the declared
+name of the variable, and the indices of the MSB and LSB of the
+vector. The vpiHandle is then created with this information, and the
+vpi_ipoint_t pointer to the LSB functor of the variable. VPI programs
+access the vector through the vpiHandle and related functions. The VPI
+code gets access to the declared indices.
+
+The VPI interface to variable (vpiReg objects) uses the MSB and LSB
+values that the user defined to describe the dimensions of the
+object.
+
+/*
+ * Copyright (c) 2001 Stephen Williams (steve@xxxxxxxxxx)
+ *
+ * This source code is free software; you can redistribute it
+ * and/or modify it in source code form under the terms of the GNU
+ * General Public License as published by the Free Software
+ * Foundation; either version 2 of the License, or (at your option)
+ * any later version.
+ *
+ * This program is distributed in the hope that it will be useful,
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ * GNU General Public License for more details.
+ *
+ * You should have received a copy of the GNU General Public License
+ * along with this program; if not, write to the Free Software
+ * Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA
+ */</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-icarus_vvp_runtime.html b/docs/wiki/geda-icarus_vvp_runtime.html
new file mode 100644
index 0000000..08277ee
--- /dev/null
+++ b/docs/wiki/geda-icarus_vvp_runtime.html
@@ -0,0 +1,167 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="icarus_verilog_vvp_runtime_engine_man-page" id="icarus_verilog_vvp_runtime_engine_man-page">Icarus Verilog vvp runtime engine man-page</a></h1>
+<div class="level1">
+<pre class="code">vvp(1) $Date: 2005/01/29 06:28:19 $ vvp(1)
+
+
+
+NAME
+ vvp - Icarus Verilog vvp runtime engine
+
+
+SYNOPSIS
+ vvp [-sv] [-Mpath] [-mmodule] [-llogfile] inputfile [extended-args...]
+
+
+DESCRIPTION
+ vvp is the run time engine that executes the default compiled form gen-
+ erated by Icarus Verilog. The output from the iverilog command is not
+ by itself executable on any platform. Instead, the vvp program is
+ invoked to execute the generated output file.
+
+
+OPTIONS
+ vvp accepts the following options:
+
+ -llogfile
+ This flag specifies a logfile where all MCI <stdlog> output
+ goes. Specify logfile as �-� to send log output to <stderr>.
+ $display and friends send their output both to <stdout> and
+ <stdlog>.
+
+ -Mpath This flag adds a directory to the path list used to locate VPI
+ modules. The default path includes only the install directory
+ for the system.vpi module, but this flag can add other directo-
+ ries. Multiple paths are allowed, and modules will be searched
+ in order.
+
+ -mmodule
+ Tell the vvp run time to load the named module before executing
+ the simulation. The system.vpi module is loaded by default, but
+ additional modules, including modules that you compiled
+ locally, can be specified with this flag. Any number of modules
+ can be loaded, and they will be linked in the order they are
+ listed on the command line.
+
+ Normally, you only need to specify the name of the module,
+ without any directory path or .vpi suffix and the search path
+ is scanned to find the module. However, if the name includes at
+ least one directory character, then the search path is not
+ scanned and the name is assumed to be a complete file name.
+
+ -s Stop. This will cause the simulation to stop in the beginning,
+ before any events are scheduled. This allows the interactive
+ user to get hold of the simulation just before it starts.
+
+ -v Turn on verbose messages. This will cause information about run
+ time progress to be printed to standard out.
+
+
+EXTENDED ARGUMENTS
+ The vvp options described above must come before the design file name.
+ After the design file name, however, there may be any number of unspec-
+ ified arguments. These arguments are not interpreted by vvp but are
+ instead passed on to the executed design, and are available via the
+ $test$plusargs and $value$plusargs system functions.
+
+ Arguments that do not start with the plus(+) character are not avail-
+ able to the $plusargs system tasks, but can still be accessed via PLI
+ code via the vpi_get_vlog_info function. This means that vpi modules
+ may use arguments that do not start with + and be assured that they do
+ not interfere with user defined plus-args.
+
+ There are a few extended arguments that are interpreted by the standard
+ system.vpi module, which implements the standard system tasks and so is
+ always included. These arguments are described here.
+
+ -vcd|-vcd-none
+ This extended argument sets the wave dump format to VCD. This
+ is the default in the absence of any IVERILOG_DUMPER environ-
+ ment variable. The VCD dump files are large and ponderous, but
+ are also maximally compatible with third party tools that read
+ waveform dumps.
+
+ The -vcd-none variant actually suppresses all waveform output. This can
+ make long simulations run faster.
+
+
+ -lxt|-lxt-speed|-lxt-space|-lxt-none
+ These extended arguments set the wave dump format to lxt, pos-
+ sibly with format optimizations. The -lxt-space flag sets the
+ output format to lxt with full compression enabled. The result-
+ ing files are quite small. The -lxt-speed chooses the lxt com-
+ pression mode that leads to the best execution time and the
+ fastest read time, at the expense of some file size.
+
+ The -lxt-none variant actually suppresses all waveform output. This can
+ make long simulations run faster.
+
+
+ -lxt2 The LXT2 format is slower then LXT (faster then VCD) but takes
+ less space, and is written out incrementally. Thus, you can
+ view lxt2 files while a simulation is still running (or paused)
+ or if your simulation crashes or is killed, you still have a
+ useful dump.
+
+
+ENVIRONMENT
+ The vvp command also accepts some environment variables that control
+ its behavior. These can be used to make semi-permanent changes.
+
+
+ IVERILOG_DUMPER=lxt|lxt2|vcd|none
+ This selects the output format for the waveform output. Nor-
+ mally, waveforms are dumped in vcd format, but this variable
+ can be used to select lxt format, which is far more compact,
+ though limited to gtkwave or compatible viewers. It can also be
+ used to suppress VCD output, a time-saver for regression tests.
+
+
+INTERACTIVE MODE
+ The simulation engine supports an interactive mode. The user may inter-
+ rupt the simulation (typically by typing Ctrl-C) to get to the interac-
+ tive prompt. From that prompt, the help command prints a brief summary
+ of the available commands.
+
+ The interactive mode may also be entered by a call to the $stop system
+ task from within the simulation, or by a call to the vpi_control VPI
+ function with the vpiStop control argument. These means of entering
+ interactive mode are equivalent.
+
+
+AUTHOR
+ Steve Williams (steve@xxxxxxxxxx)
+
+
+SEE ALSO
+ iverilog(1), iverilog-vpi(1), <http://www.icarus.com/eda/verilog/>
+
+
+COPYRIGHT
+ Copyright �© 2001-2003 Stephen Williams
+
+ This document can be freely redistributed according to the terms of the
+ GNU General Public License version 2.0
+
+
+
+Version $Date: 2005/01/29 06:28:19 $ vvp(1)</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-icarus_vvp_simulation.html b/docs/wiki/geda-icarus_vvp_simulation.html
new file mode 100644
index 0000000..5a0b660
--- /dev/null
+++ b/docs/wiki/geda-icarus_vvp_simulation.html
@@ -0,0 +1,1014 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="vvp_simulation_engine" id="vvp_simulation_engine">VVP Simulation Engine</a></h1>
+<div class="level1">
+<pre class="code">/*
+ * Copyright (c) 2001 Stephen Williams (steve@xxxxxxxxxx)
+ *
+ * $Id: README.txt,v 1.74 2005/11/25 17:55:26 steve Exp $
+ */
+
+VVP SIMULATION ENGINE
+
+The VVP simulator takes as input source code not unlike assembly
+language for a conventional processor. It is intended to be machine
+generated code emitted by other tools, including the Icarus Verilog
+compiler, so the syntax, though readable, is not necessarily
+convenient for humans.
+
+
+GENERAL FORMAT
+
+The source file is a collection of statements. Each statement may have
+a label, an opcode, and operands that depend on the opcode. For some
+opcodes, the label is optional (or meaningless) and for others it is
+required.
+
+Every statement is terminated by a semicolon. The semicolon is also
+the start of a comment line, so you can put comment text after the
+semicolon that terminates a statement. Like so:
+
+ Label .functor and, 0x5a, x, y ; This is a comment.
+
+The semicolon is required, whether the comment is there or not.
+
+Statements may span multiple lines, as long as there is no text (other
+then the first character of a label) in the first column of the
+continuation line.
+
+HEADER SYNTAX
+
+Before any other non-commentary code starts, the source may contain
+some header statements. These are used for passing parameters or
+global details from the compiler to the vvp run-time. In all cases,
+the header statement starts with a left-justified keyword.
+
+* :module "name" ;
+
+This header statement names a vpi module that vvp should load before
+the rest of the program is compiled. The compiler looks in the
+standard VPI_MODULE_PATH for files named "name.vpi", and tries to
+dynamic load them.
+
+* :vpi_time_precision [+|-]<value>;
+
+This header statement specifies the time precision of a single tick of
+the simulation clock. This is mostly used for display (and VPI)
+purposes, because the engine itself does not care about units. The
+compiler scales time values ahead of time.
+
+The value is the size of a simulation tick in seconds, and is
+expressed as a power of 10. For example, +0 is 1 second, and -9 is 1
+nanosecond. If the record is left out, then the precision is taken to
+be +0.
+
+LABELS AND SYMBOLS
+
+Labels and symbols consist of the characters:
+
+ a-z
+ A-Z
+ 0-9
+ .$_<>
+
+Labels and symbols may not start with a digit or a '.', so that they
+are easily distinguished from keywords and numbers. A Label is a
+symbol that starts a statement. If a label is present in a statement,
+it must start in the first text column. This is how the lexical
+analyzer distinguishes a label from a symbol. If a symbol is present
+in a statement, it is in the operand. Opcodes of statements must be a
+keyword.
+
+Symbols are references to labels. It is not necessary for a label to
+be declared before its use in a symbol, but it must be declared
+eventually. When symbols refer to functors, the symbol represents the
+vvp_ipoint_t pointer to the output. (Inputs cannot, and need not, be
+references symbolically.)
+
+If the functor is part of a vector, then the symbol is the
+vvp_ipoint_t for the first functor. The [] operator can then be used
+to reference a functor other then the first in the vector.
+
+There are some special symbols that in certain contexts have special
+meanings. As inputs to functors, the symbols "C<0>", "C<1>", "C<x>"
+and "C<z>" represent a constant driver of the given value.
+
+
+SCOPE STATEMENTS:
+
+
+PARAMETER STATEMENTS:
+
+Parameters are named constants within a scope. These parameters have a
+type and value, and also a label so that they can be referenced as VPI
+objects.
+
+The syntax of a parameter is:
+
+ <label> .param <name>, <type>, <value>;
+
+The <name> is a string that names the parameter. The name is placed in
+the current scope as a vpiParameter object. The <type> is one of the
+following:
+
+ real -- The parameter has a real value
+ string -- The parameter has a string value
+ [<msb>,<lsb>,<s>]
+ -- The parameter is a vector, with specified
+ indices. The <s> is s or u for signed or
+ unsigned.
+
+The value, then, is appropriate for the data type. For example:
+
+ P_123 .param "hello", string, "Hello, World.";
+
+
+FUNCTOR STATEMENTS:
+
+A functor statement is a statement that uses the ``.functor''
+opcode. Functors are the basic structural units of a simulation, and
+include a type (in the form of a truth table) and up to four inputs. A
+label is required for functors.
+
+The general syntax of a functor is:
+
+ <label> .functor <type> [ (<delay>) ], symbol_list ;
+
+The symbol list is 4 names of labels of other functors. These connect
+inputs of the functor of the statement to the output of other
+functors. If the input is unconnected, use a C<?> symbol instead. The
+type selects the truth lookup table to use for the functor
+implementation. Most of the core gate types have built in tables.
+
+The initial values of all the inputs and the output is x. Any other
+value is passed around as run-time behavior. If the inputs have C<?>
+symbols, then the inputs are initialized to the specified bit value,
+and if this causes the output to be something other then x, a
+propagation event is created to be executed at the start of run time.
+
+The strengths of inputs are ignored by functors, and the output has
+fixed drive0 and drive1 strengths. So strength information is
+typically lost as it passes through functors.
+
+Almost all of the structural aspects of a simulation can be
+represented by functors, which perform the very basic task of
+combining up to four inputs down to one output.
+
+- MUXZ
+
+ Q | A B S n/a
+ --+-------------
+ A | * * 0
+ B | * * 1
+
+
+DFF STATEMENTS:
+
+The Verilog language itself does not have a DFF primitive, but post
+synthesis readily creates DFF devices that are best simulated with a
+common device. Thus, there is the DFF statement to create DFF devices:
+
+ <label> .dff <d>, <clk>, <ce>, <async-input>;
+
+The generated functor is generally synchronous on the <clk> rising
+edge of <clk>, with the <ce> enable active high. The <clk> and <ce>
+are single bit vectors (or scalars) on ports 1 and 2. Port-0 is any
+type of datum at all. The device will transfer the input to the output
+when it is loaded by a clock. The <async-input> is a special
+asynchronous input that is immediately stored and transferred to the
+output when data arrives here. This is useful for implementing
+asynchronous set/clear functions.
+
+UDP STATEMENTS:
+
+A UDP statement either defines a User Defined Primitive, or
+instantiates a previously defined UDP by creating a UDP functor. A
+UDP functor has as many inputs as the UDP definition requires.
+
+UDPs come in sequential and combinatorial flavors. Sequential UDPs
+carry an output state and can respond to edges at the inputs. The
+output of combinatorial UDPs is a function of its current inputs
+only.
+
+The function of a UDP is defined via a table. The rows of the table
+are strings which describe input states or edges, and the new output
+state. Combinatorial UDPs require one character for each input, and
+one character at the end for the output state. Sequential UDPs need
+an additional char for the current state, which is the first char of
+the row.
+
+Any input transition or the new state must match at most one row (or
+all matches must provide the same output state). If no row matches,
+the output becomes 1'bx.
+
+The output state can be specified as "0", "1", or "x". Sequential
+UDPs may also have "-": no change.
+
+An input or current output state can be
+
+ "1": 1
+ "0": 0
+ "x": x
+ "b": 1, 0
+ "h": 1, x
+ "l": 0, x
+ "?": 1, 0, x
+
+For Sequential UDPs, at most one input state specification may be
+replaced by an edge specification. Valid edges are:
+
+ "*": (??) "_": (?0) "+": (?1) "%": (?x)
+ "P": (0?) "r": (01) "Q": (0x)
+ "N": (1?) "f": (10) "M": (1x)
+ "B": (x?) "F": (x0) "R": (x1)
+
+ "n": (1?) | (?0)
+ "p": (0?) | (?1)
+
+A combinatorial UDP is defined like this:
+
+ <type> .udp/comb "<name>", <number>, "<row0>", "<row1>", ... ;
+
+<type> is a label that identifies the UDP. <number> is the number of
+inputs. "<name>" is there for public identification. Sequential UDPs
+need an additional initialization value:
+
+ <type> .udp/sequ "<name>", <number>, <init>, "<row0>", "<row1>", ... ;
+
+<init> is the initial value for all instances of the UDP. We do not
+provide initial values for individual instances. <init> must be a
+number 0, 1, or 2 (for 1'bx).
+
+A UDP functor instance is created so:
+
+ <label> .udp <type>, <symbol_list> ;
+
+Where <label> identifies the functor, <type> is the label of a UDP
+defined earlier, and <symbol_list> is a list of symbols, one for each
+input of the UDP.
+
+
+VARIABLE STATEMENTS:
+
+A variable is a bit vector that can be written by behavioral code (so
+has no structural input) and propagates its output to a functor. The
+general syntax of a variable is:
+
+ <label> .var "name", <msb>, <lsb>;
+ <label> .var/s "name", <msb>, <lsb>;
+ <label> .var/real "name", <msb>, <lsb>;
+
+The "name" is the declared base name of the original variable, for the
+sake of VPI code that might access it. The variable is placed in the
+current scope. The variable also has a width, defined by the indices
+for the most significant and lest significant bits. If the indices are
+equal (normally 0) the vector has width of one. If the width is greater
+then one, a contiguous array of functors is created and the value of
+the label is the address of the least significant bit.
+
+A variable does not take inputs, since its value is set behaviorally
+by assignment events. It does have output, though, and its output is
+propagated into the net of functors in the usual way.
+
+A variable gets its value by assignments from procedural code: %set
+and %assign. These instructions write values to the port-0 input. From
+there, the value is held.
+
+Behavioral code can also invoke %cassign/v statements that work like
+%set/v, but instead write to port-1 of the variable node. Writes to
+port-1 of a variable activate continuous assign mode, where the values
+written to port-0 are ignored. The continuous assign mode remains
+active until a long(1) is written to port-3 (a command port).
+
+Behavioral code may also invoke %force/v statements that write to port-2
+to invoke force mode. This overrides continuous assign mode until a
+long(2) is written to port-3 to disable force mode.
+
+NET STATEMENTS:
+
+A net is similar to a variable, except that a thread cannot write to
+it (unless it uses a force) and it is given a different VPI type
+code. The syntax of a .net statement is also similar to but not
+exactly the same as the .var statement:
+
+ <label> .net "name", <msb>, <lsb>, <symbol>;
+ <label> .net/s "name", <msb>, <lsb>, <symbol>;
+ <label> .net8 "name", <msb>, <lsb>, <symbol>;
+ <label> .net8/s "name", <msb>, <lsb>, <symbol>;
+ <label> .net/real "name", <msb>, <lsb>, <symbol>;
+ <label> .alias "name", <msb>, <lsb>, <symbol>;
+
+
+Like a .var statement, the .net statement creates a VPI object with
+the basename and dimensions given as parameters. The symbol is a
+functor that feeds into the vector of the net, and the vpiHandle
+holds references to that functor.
+
+The input of a .net is replicated to its output. In this sense, it
+acts like a diode. The purpose of this node is to hold various VPI
+and event trappings. The .net and .net8 nodes are vector types. They
+both may represent wires, but the .net8 nodes preserve strength values
+that arrive through them, while .net nodes reduce strength values to
+4-value logic. The .net8 nodes should only be used when strength
+information really is possible.
+
+The <label> is required and is used to locate the net object that is
+represents. This label does not map to a functor, so only references
+that know they want to access .nets are able to locate the symbol. In
+particular, this includes behavioral %load and %wait instructions. The
+references to net and reg objects are done through the .net label
+instead of a general functor symbol. The instruction stores the
+functor pointer, though.
+
+The .alias statements do not create new nodes, but instead create net
+names that are aliases of an existing node. This handles special cases
+where a net has different names, possibly in different scopes.
+
+MEMORY STATEMENTS:
+
+Memories are arrays of words, each word a vvp_vector4_t vector of the
+same width. The memory is canonically addressed as a 1-dimensional
+array of words, although indices are stored with the memory for
+calculating a canonical address from a multi-dimensional address.
+
+Three types of memory statement perform (1) creation of a memory, (2)
+connecting a read port to an existing memory, and (3) initializing the
+memory's contents.
+
+ <label> .mem "name", <msb>,<lsb>, <last>,<first> ... ;
+
+The pair of numbers <msb>,<lsb> defines the word width. The pair
+<last>,<first> defines the address range. Multiple address ranges are
+allowed for multidimensional indexing. This statement creates the
+memory array and makes it available to procedural code.
+
+Procedural access to the memory references the memory as single array
+of words, with the base address==0, and the last address the size (in
+words) of the memory -1. It is up to the compiler to convert Verilog
+index sets to a canonical address. The multi-dimensional index set is
+available for VPI use.
+
+Structural read access is implemented in terms of address and data
+ports. The addresses applied to the address port are expected to be
+in canonical form.
+
+A read port is a functor that takes a single input, the read address,
+and outputs the word value at the given (canonical) address.
+
+ <label> .mem/port <memid>, <address> ;
+
+<label> identifies the vector of output functors, to allow connections
+to the data output. <memid> is the label of the memory.
+
+Any address input change, or any change in the addressed memory
+contents, is immediately propagated to the port output.
+
+A write port is a superset of a read port. It is a 4-input functor
+that accepts the word address, an event input, a write enable input,
+and the data input.
+
+ <label> .mem/port <memid>, <address>, <event>, <we>, <data> ;
+
+<event> is an event functor that triggers a write, if the <we> input
+is true. <data> is the input that connect to the data input
+port. For asynchronous transparent write operation, connect
+<event> to C4<z>, the RAM will transparently follow any changes on
+address and data lines, while <we> is true.
+
+There is no Verilog construct that calls for a structural write port
+to a memory, but synthesis may ask for lpm_ram_d[pq] objects.
+
+To initialize a memory, use:
+
+ .mem/init <memid> <start>, val , val ... ;
+
+<memid> is the label of the memory, and the <start> is the start
+address (canonical) of the first word to be initialized. The start
+address allows multiple statements be used to initialize words of a
+memory.
+
+The values are one per word.
+
+Procedural access to the memory employs an index register to address a
+bit location in the memory, via the commands:
+
+ %load/m <bit>, <memid> ;
+ %set/m <memid>, <bit> ;
+ %assign/m <memid>, <delay>, <bit> ;
+
+The memory bit is addressed by index register 3. The value of
+register 3 is the index in the memory's bit space, where each data
+word occupies a multiple of four bits.
+
+
+EVENT STATEMENTS
+
+Threads need to interact with the functors of a netlist synchronously,
+as well as asynchronously. There are cases where the web of functors
+needs to wake up a waiting thread. The web of functors signals threads
+through .event objects, that are declared like so:
+
+ <label> .event <type>, <symbols_list>;
+ <label> .event "name";
+
+
+This event statement declares an object that a %wait instruction
+can take as an operand. When a thread executes a %wait, it puts
+itself in the notification list of the event and suspends. The
+<symbols_list> is a set of inputs that can trigger the event.
+
+The <type> describes the conditions needed to trigger the event. It
+may be posedge, negedge or edge. If the type is instead a "name"
+string, then this is a named event which receives events by the %set
+instruction instead of from the output of a functor.
+
+If the event has inputs (a requirement unless it is a named event)
+then it has up to 4 symbols that address functors. The event then
+detects the appropriate edge on any of the inputs and signals when the
+event is true. Normally (in Verilog) a posedge or negedge event only
+watches a single bit, so the generated code would only include a
+single symbol for the addressed bit. However, if there are several
+events of the same edge in an event OR expression, the compiler may
+combine up to 4 into a single event.
+
+If many more events need to be combined together (for example due to
+an event or expression in the Verilog) then this form can be used:
+
+ <label> .event/or <symbols_list>;
+
+In this case, the symbols list all the events that are to be combined
+to trigger this event. Only one of the input events needs to trigger
+to make this one go.
+
+
+RESOLVER STATEMENTS:
+
+Resolver statements are strength-aware functors with 4 inputs, but
+their job typically is to calculate a resolved output using strength
+resolution. The type of the functor is used to select a specific
+resolution function.
+
+ <label> .resolv tri, <symbols_list>;
+ <label> .resolv tri0, <symbols_list>;
+ <label> .resolv tri1, <symbols_list>;
+
+The output from the resolver is vvp_vector8_t value. That is, the
+result is a vector with strength included.
+
+
+PART SELECT STATEMENTS:
+
+Part select statements are functors with three inputs. They take in at
+port-0 a vector, and output a selected (likely smaller) part of that
+vector. The other inputs specify what those parts are, as a canonical
+bit number, and a width. Normally, those bits are constant values.
+
+ <label> .part <symbol>, <base>, <wid>;
+ <label> .part/pv <symbol>, <base>, <wid>, <vector_wid>;
+ <label> .part/v <symbol>, <symbol>, <wid>;
+
+The input is typically a .reg or .net, but can be any vector node in
+the netlist.
+
+The .part/pv variation is the inverse of the .part version, in that
+the output is actually written to a *part* of the output. The node
+uses special part-select-write functions to propagate a part of a
+network. The <vector_wid> is the total width of the destination net
+that part is written to. Destination nodes use this value to check
+further output widths.
+
+The .part/v variation takes a vector (or long) input on port-1 as the
+base of the part select. Thus, the part select can move around.
+
+PART CONCATENATION STATEMENTS:
+
+The opposite of the part select statement is the part concatenation
+statement. The .concat statement is a functor node that takes at input
+vector values and produces a single vector output that is the
+concatenation of all the inputs.
+
+ <label> .concat [W X Y Z], <symbols_list> ;
+
+The "[" and "]" tokens surround a set of 4 numbers that are the
+expected widths of all the inputs. These widths are needed to figure
+the positions of the input vectors in the generated output, and are
+listed in order LSB to MSB. The inputs themselves are also listed LSB
+to MSB, with the LSB vector input coming through port-0 of the real
+functor.
+
+The initial output value is (W+X+Y+Z) bits of 'bx. As input values are
+propagated, the bits are placed in the correct place in the output
+vector value, and a new output value is propagated.
+
+
+REPEAT VECTOR STATEMENTS:
+
+The repeat vector statement is similar to the concatenation statement,
+expect that the input is repeated a constant number of times. The
+format of the repeat vector statement is:
+
+ <label> .repeat <wid>, <rept count>, <symbol> ;
+
+In this statement, the <wid> is a decimal number that is the width of
+the *output* vector. The <rept count> is the number of time the input
+vector value is repeated to make the output width. The input width is
+implicit from these numbers. The <symbol> is then the input source.
+
+REDUCTION LOGIC
+
+The reduction logic statements take in a single vector, and propagate
+a single bit.
+
+ <label> .reduce/and <symbol> ;
+ <label> .reduce/or <symbol> ;
+ <label> .reduce/xor <symbol> ;
+ <label> .reduce/nand <symbol> ;
+ <label> .reduce/nor <symbol> ;
+ <label> .reduce/xnor <symbol> ;
+
+the device has a single input, which is a vector of any width. The
+device performs the logic on all the bits of the vector (a la Verilog)
+and produces and propagates a single bit width vector.
+
+EXPANSION LOGIC
+
+Sign extension nodes are the opposite of reduction logic, in that they
+take a narrow vector, or single bit, and pad it out to a wider
+vector.
+
+ <label> .expand/s <wid>, <symbol> ;
+
+The .expand/s node takes an input symbol and sign-extends it to the
+given width.
+
+FORCE STATEMENTS (old method - remove me):
+
+A force statement creates functors that represent a Verilog force
+statement.
+
+ <label> .force <signal>, <symbol_list>;
+
+The symbol <signal> represents the signal which is to be forced. The
+<symbol_list> specifies the bits of the expression that is to be
+forced on the <signal>. The <label> identifies the force functors.
+There will be as many force functors as there are symbols in the
+<symbol_list>.
+
+To activate and deactivate a force on a single bit, use:
+
+ %force <label>, <width>;
+ %release <signal>;
+
+<label>/<width> is the label/width of a vector of force functors.
+<signal> is the label of the functor that drives the signal that is
+being forced.
+
+FORCE STATEMENTS (new method - implement me):
+
+A %force instruction, as described in the .var section, forces a
+constant value onto a .var or .net, and the matching %release releases
+that value. However, there are times when the value of a functor
+(i.e. another .net) needs to be forced onto a .var or .net. For this
+task, the %force/link instruction exists:
+
+ %force/link <dst>, <src> ;
+ %release/link <dst> ;
+
+This causes the output of the node <src> to be linked to the force
+input of the <dst> .var/.net node. When linked, the output functor
+will automatically drive values to the force port of the destination
+node. The matching %release/link instruction removes the link (a
+%release is still needed) to the destination. The %release/link
+releases the last %force/link, no matter where the link is from. A new
+%force/link will remove a previous link.
+
+The instructions:
+
+ %cassign/link <dst>, <src> ;
+ %deassign/link <dst> ;
+
+are the same concept, but for the continuous assign port.
+
+STRUCTURAL ARITHMETIC STATEMENTS:
+
+The various Verilog arithmetic operators (+-*/%) are available to
+structural contexts as two-input functors that take in vectors. All of
+these operators take two inputs and generate a fixed width output. The
+input vectors will be padded if needed to get the desired output width.
+
+ <label> .arith/sub <wid>, <A>, <B>;
+ <label> .arith/sum <wid>, <A>, <B>;
+ <label> .arith/mult <wid>, <A>, <B>;
+ <label> .arith/div <wid>, <A>, <B>;
+ <label> .arith/mod <wid>, <A>, <B>;
+
+In all cases, there are no width limits, so long as the width is
+fixed.
+
+NOTE: The .arith/mult inputs are not necessarily the width of the
+output. I have not decided how to handle this.
+
+These devices support .s and .r suffixes. The .s means the node is a
+signed vector device, the .r a real valued device.
+
+STRUCTURAL COMPARE STATEMENTS:
+
+The arithmetic statements handle various arithmetic operators that
+have wide outputs, but the comparators have single bit output, so they
+are implemented a bit differently. The syntax, however, is very
+similar:
+
+ <label> .cmp/eeq <wid>, <A>, <B>;
+ <label> .cmp/nee <wid>, <A>, <B>;
+ <label> .cmp/eq <wid>, <A>, <B>;
+ <label> .cmp/ne <wid>, <A>, <B>;
+ <label> .cmp/ge <wid>, <A>, <B>;
+ <label> .cmp/gt <wid>, <A>, <B>;
+ <label> .cmp/ge.s <wid>, <A>, <B>;
+ <label> .cmp/gt.s <wid>, <A>, <B>;
+
+Whereas the arithmetic statements generate an output the width of
+<wid>, the comparisons produce a single bit vector result. The plain
+versions do unsigned comparison, but the ".s" versions to signed
+comparisons. (Equality doesn't need to care about sign.)
+
+
+STRUCTURAL SHIFTER STATEMENTS:
+
+Variable shifts in structural context are implemented with .shift
+statements:
+
+ <label> .shift/l <wid>, <data symbol>, <shift symbol>;
+ <label> .shift/r <wid>, <data symbol>, <shift symbol>;
+
+The shifter has a width that defines the vector width of the output, a
+<data symbol> that is the input data to be shifted and a <shift-symbol>
+that is the amount to shift. The vectors that come from port 0 are the
+data to be shifted and must have exactly the width of the output. The
+input to port 1 is the amount to shift.
+
+
+STRUCTURAL FUNCTION CALLS:
+
+The .ufunc statement defines a call to a user defined function.
+
+ <label> .ufunc <flabel>, <wid>, <isymbols> ( <psymbols> ) <rsymbol> ;
+
+The <flabel> is the code label for the first instruction of the
+function implementation. This is code that the simulator will branch
+to.
+
+The <wid> is the width of the output vector in bits.
+
+The <isymbols> is a list of net symbols for each of the inputs to the
+function. These are points in the net, and the ufunc device watches
+these nets for input changes.
+
+The <psymbols> list is exactly the same size as the <isymbols>
+list. The <psymbols> are variables that represent the input ports for
+the function. The ufunc performs an assignment to these variables
+before calling the function.
+
+Finally, the <rsymbol> is the variable within the function where the
+result will be found when the function code ends. This value is picked
+up and propagated to the output of the functor.
+
+THREAD STATEMENTS:
+
+Thread statements create the initial threads for a simulation. These
+represent the initial and always blocks, and possibly other causes to
+create threads at startup.
+
+ .thread <symbol> [, <flag>]
+
+This statement creates a thread with a starting address at the
+instruction given by <symbol>. When the simulation starts, a thread is
+created for the .thread statement, and it starts at the <symbol>
+addressed instruction.
+
+The <flag> modifies the creation/execution behavior of the
+thread. Supported flags are:
+
+ $push -- Cause the thread to be pushed in the scheduler. This
+ only effects startup (time 0) by arranging for pushed
+ threads to be started before non-pushed threads. This
+ is useful for resolving time-0 races.
+
+* Threads in general
+
+Thread statements create the initial threads of a design. These
+include the ``initial'' and ``always'' statements of the original
+Verilog, and possibly some other synthetic threads for various
+purposes. It is also possible to create transient threads from
+behavioral code. These are needed to support such constructs as
+fork/join, named blocks and task activation.
+
+A transient thread is created with a %fork instruction. When a
+transient thread is created this way, the operand to the %fork gives
+the starting address, and the new thread is said to be a child of the
+forking thread. The children of a thread are pushed onto a stack of
+children. A thread can have only one direct child.
+
+A transient thread is reaped with a %join instruction. %join waits for
+the top thread in the stack of children to complete, then
+continues. It is an error to %join when there are no children.
+
+As you can see, the transient thread in VVP is a cross between a
+conventional thread and a function call. In fact, there is no %call
+instruction in vvp, the job is accomplished with %fork/%join in the
+caller and %end in the callee. The %fork, then is simply a
+generalization of a function call, where the caller does not
+necessarily wait for the callee.
+
+For all the behavior of threads and thread parentage to work
+correctly, all %fork statements must have a corresponding %join in the
+parent, and %end in the child. Without this proper matching, the
+hierarchical relationships can get confused. The behavior of erroneous
+code is undefined.
+
+* Thread Context
+
+The context of a thread is all the local data that only that thread
+can address. The local data is broken into two addresses spaces: bit
+memory and word memory.
+
+The bit memory is a region of 4-value bits (0,1,x,z) that can be
+addressed in strips of arbitrary length. For example, an 8-bit value
+can be in locations 8 through and including 15. The bits at address 0,
+1, 2 and 3 are special constant values. Reads from those locations
+make vectors of 0, 1, x or z values, so these can be used to
+manufacture complex values elsewhere.
+
+The word memory is a region of tagged words. The value in each word
+may be native long or real. These words have a distinct address space
+from the bits.
+
+* Threads and scopes
+
+The Verilog ``disable'' statement deserves some special mention
+because of how it interacts with threads. In particular, threads
+throughout the design can affect (end) other threads in the design
+using the disable statement.
+
+In Verilog, the operand to the disable statement is the name of a
+scope. The behavior of the disable is to cause all threads executing
+in the scope to end. Termination of a thread includes all the children
+of the thread. In vvp, all threads are in a scope, so this is how the
+disable gains access to the desired thread.
+
+It is obvious how initial/always thread join a scope. They become part
+of the scope simply by being declared after a .scope declaration. (See
+vvp.txt for .scope declarations.) The .thread statement placed in the
+assembly source after a .scope statement causes the thread to join the
+named scope.
+
+Transient threads join a scope that is the operand to the %fork
+instruction. The scope is referenced by name, and the thread created
+by the fork atomically joins that scope. Once the transient thread
+joins the scope, it stays there until it ends. Threads never change
+scopes, not even transient threads.
+
+TRUTH TABLES
+
+The logic that a functor represents is expressed as a truth table. The
+functor has four inputs and one output. Each input and output has one
+of four possible values (0, 1, x and z) so two bits are needed to
+represent them. So the input of the functor is 8 bits, and the output
+2 bits. A complete lookup table for generating the 2-bit output from
+an 8-bit input is 512 bits. That can be packed into 64 bytes. This is
+small enough that the table should take less space then the code to
+implement the logic.
+
+To implement the truth table, we need to assign 2-bit encodings for
+the 4-value signals. I choose, pseudo-randomly, the following
+encoding:
+
+ 1'b0 : 00
+ 1'b1 : 01
+ 1'bx : 10
+ 1'bz : 11
+
+The table is an array of 64 bytes, each byte holding 4 2-bit
+outputs. Construct a 6-bit byte address with inputs 1, 2 and 3 like
+so:
+ 332211
+
+The input 0 2-bits can then be used to select which of the 4 2-bit
+pairs in the 8-bit byte are the output:
+
+ MSB -> zzxx1100 <- LSB
+
+A complete truth table, then is described as 64 8-bit bytes.
+
+The vvp engine includes truth tables for the primitive gate types, so
+none needs to be given by the programmer. It is sufficient to name the
+type to get that truth table.
+
+
+EXECUTABLE INSTRUCTIONS
+
+Threads run executable code, much like a processor executes machine
+code. VVP has a variety of opcodes for executable instructions. All of
+those instructions start with '%' and go into a single address
+space. Labels attached to executable instructions get assigned the
+address of the instruction, and can be the target of %jmp instructions
+and starting points for threads.
+
+The opcodes.txt file has a more detailed description of all the
+various instructions.
+
+
+THE RELATIONSHIP BETWEEN FUNCTORS, THREADS AND EVENTS
+
+Given the above summary of the major components of vvp, some
+description of their relationship is warranted. Functors provide a
+structural description of the design (so far as it can be described
+structurally) and these functors run independently of the threads. In
+particular, when an input to a functor is set, it calculates a new
+output value; and if that output is different from the existing
+output, a propagation event is created. Functor output is calculated
+by truth table lookup, without the aid of threads.
+
+Propagation events are one of three kinds of events in vvp. They are
+scheduled to execute at some time, and they simply point to the functor
+that is to have its output propagated. When the event expires, the
+output of the referenced functor is propagated to all the inputs that
+it is connected to, and those functors in turn create new events if
+needed.
+
+Assignment events (the second of three types of events) are created
+by non-blocking assignments in behavioral code. When the ``<='' is
+executed (a %assign in vvp) an assign event is created, which includes
+the vvp_ipoint_t pointer to the functor input to receive the value,
+as well as the value. These are distinct from propagation events because:
+
+ a) There is no functor that has as its output the value to be
+ assigned (this is how values get into the functor net in
+ the first place), and
+
+ b) This allows for behavioral code to create waveforms of
+ arbitrary length that feed into a variable. Verilog allows
+ this of non-blocking assignments, but not of gate outputs.
+
+The last type of event is the thread schedule event. This event simply
+points to a thread to be executed. Threads are made up of a virtual
+processor with a program counter and some private storage. Threads
+can execute %assign instructions to create assignment events, and can
+execute %set instructions to do blocking assignments. Threads can also
+use %load to read the output of functors.
+
+The core event scheduler takes these three kinds of events and calls
+the right kind of code to cause things to happen in the design. If the
+event is a propagate or assignment event, the network of functors is
+tickled; if the event is a thread schedule, then a thread is run. The
+implementation of the event queue is not important, but currently is
+implemented as a ``skip list''. That is, it is a sorted singly linked
+list with skip pointers that skip over delta-time events.
+
+The functor net and the threads are distinct. They communicate through
+thread instructions %set, %assign, %waitfor and %load. So far as a thread
+is concerned, the functor net is a blob of structure that it pokes and
+prods via certain functor access instructions.
+
+
+VVP COMPILATION AND EXECUTION
+
+The vvp program operates in a few steps:
+
+ 1) Initialization
+ Data structures are cleared to empty, and tables are
+ readied for compilation.
+
+ 2) Compilation
+ The input file is read and compiled. Symbol tables are
+ build up as needed, objects are allocated and linked
+ together.
+
+ 3) Cleanup
+ Symbol tables and other resources used only for
+ compilation are released to reduce the memory
+ footprint.
+
+ 4) Simulation
+ Event simulation is run.
+
+
+The initialization step is performed by the compile_init() function in
+compile.cc. This function in turn calls all the *_init() functions in
+other parts of the source that need initialization for compile. All
+the various sub-init functions are called <foo>_init().
+
+Compilation is controlled by the parser, it parse.y. As the parser
+reads and parses input, the compilation proceeds in the rules by
+calling various compile_* functions. All these functions live in the
+compile.cc file. Compilation calls other sections of the code as
+needed.
+
+When the parser completes compilation, compile_cleanup() is called to
+finish the compilation process. Unresolved references are completed,
+then all the symbol tables and other compile-time-only resources are
+released. Once compile_cleanup() returns, there is no more use for the
+parser for the function in compile.cc.
+
+After cleanup, the simulation is started. This is done by executing
+the schedule_simulate() function. This does any final setup and starts
+the simulation running and the event queue running.
+
+
+HOW TO GET FROM THERE TO HERE
+
+The vvp simulation engine is designed to be able to take as input a
+compiled form of Verilog. That implies that there is a compiler that
+compiles Verilog into a form that the vvp engine can read.
+
+
+* Boolean logic gates
+
+Gates like AND, OR and NAND are implemented simply and obviously by
+functor statements. Any logic up to 4 inputs can be implemented with a
+single functor. For example:
+
+ and gate (out, i1, i2, i3);
+
+becomes:
+
+ gate .functor and, i1, i2, i3;
+
+Notice the first parameter of the .functor is the type. The type
+includes a truth table that describes the output with a given
+input. If the gate is wider then four inputs, then cascade
+functors. For example:
+
+ and gate (out, i1, i2, i3, i4, i5, i6, i7, i8);
+
+becomes:
+
+ gate.0 .functor and, i1, i2, i3, i4;
+ gate.1 .functor and, i5, i6, i7, i8;
+ gate .functor and, gate.0, gate.1;
+
+
+* reg and other variables
+
+Reg and integer are cases of what Verilog calls ``variables.''
+Variables are, simply put, things that behavioral code can assign
+to. These are not the same as ``nets,'' which include wires and the
+like.
+
+Each bit of a variable is created by a ``.var'' statement. For example:
+
+ reg a;
+
+becomes:
+
+ a .var "a", 0, 0;
+
+
+* named events
+
+Events in general are implemented as functors, but named events in
+particular have no inputs and only the event output. The way to
+generate code for these is like so:
+
+ a .event "name";
+
+This creates a functor and makes it into a mode-2 functor. Then the
+trigger statement, "-> a", cause a ``%set a, 0;'' statement be
+generated. This is sufficient to trigger the event.
+
+/*
+ * Copyright (c) 2001 Stephen Williams (steve@xxxxxxxxxx)
+ *
+ * This source code is free software; you can redistribute it
+ * and/or modify it in source code form under the terms of the GNU
+ * General Public License as published by the Free Software
+ * Foundation; either version 2 of the License, or (at your option)
+ * any later version.
+ *
+ * This program is distributed in the hope that it will be useful,
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ * GNU General Public License for more details.
+ *
+ * You should have received a copy of the GNU General Public License
+ * along with this program; if not, write to the Free Software
+ * Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA
+ */</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-icarus_xilinx_hints.html b/docs/wiki/geda-icarus_xilinx_hints.html
new file mode 100644
index 0000000..dc8b682
--- /dev/null
+++ b/docs/wiki/geda-icarus_xilinx_hints.html
@@ -0,0 +1,118 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="xilinx_hints" id="xilinx_hints">Xilinx Hints</a></h1>
+<div class="level1">
+<pre class="code">For those of you who wish to use Icarus Verilog, in combination with
+the Xilinx back end (Foundation or Alliance), it can be done. I have
+run some admittedly simple (2300 equivalent gates) designs through this
+setup, targeting a Spartan XCS10.
+
+Verilog:
+
+ Older versions of Icarus Verilog (like 19990814) couldn't synthesize
+ logic buried in procedural (flip-flop) assignment. Newer versions
+ (like 20000120) don't have this limitation.
+
+ Procedural assignments have to be given one at a time, to be
+ "found" by xnfsyn. Say
+ always @ (posedge Clk) Y = newY;
+ always @ (posedge Clk) Z = newZ;
+ rather than
+ always @ (posedge Clk) begin
+ Y = newY;
+ Z = newZ;
+ end
+
+ Steve's xnf.txt covers most buffer and pin constructs, but I had reason
+ to use a global clock net not connected to an input pin. The standard
+ Verilog for a buffer, combined with a declaration to turn that into a
+ BUFG, is:
+ buf BUFG( your_output_here, your_input_here );
+ $attribute(BUFG,"XNF-LCA","BUFG:O,I")
+
+ I use post-processing on my .xnf files to add "FAST" attributes to
+ output pins.
+
+Running ivl:
+
+ The -F switches are important. The following order seems to robustly
+ generate valid XNF files, and is used by "verilog -X":
+ -Fsynth -Fnodangle -Fxnfio
+
+Generating .pcf files:
+
+ The ngdbuild step seems to lose pin placement information that ivl
+ puts in the XNF file. Use xnf2pcf to extract this information to
+ a .pcf file, which the Xilinx place-and-route software _will_ pay
+ attention to. Steve says he now makes that information available
+ in an NCF file, with -fncf=<path>, but I haven't tested that.
+
+Running the Xilinx back end:
+
+ You can presumably use the GUI, but that doesn't fit in Makefiles :-).
+ Here is the command sequence in pseudo-shell-script:
+ ngdbuild -p $part $1.xnf $1.ngd
+ map -p $part -o map.ncd $1.ngd
+ xnf2pcf <$1.xnf >$1.pcf # see above
+ par -w -ol 2 -d 0 map.ncd $1.ncd $1.pcf
+ bitgen_flags = -g ConfigRate:SLOW -g TdoPin:PULLNONE -g DonePin:PULLUP \
+ -g CRC:enable -g StartUpClk:CCLK -g SyncToDone:no \
+ -g DoneActive:C1 -g OutputsActive:C3 -g GSRInactive:C4 \
+ -g ReadClk:CCLK -g ReadCapture:enable -g ReadAbort:disable
+ bitgen $1.ncd -l -w $bitgen_flags
+
+ The Xilinx software has diarrhea of the temp files (14, not including
+ .xnf, .pcf, .ngd, .ncd, and .bit), so this sequence is best done in a
+ dedicated directory. Note in particular that map.ncd is a generic name.
+
+ I had reason to run this remotely (and transparently within a Makefile)
+ via ssh. I use the gmake rule
+%.bit : %.xnf
+ ssh -x -a -o 'BatchMode yes' ${ALLIANCE_HOST} \
+ remote_alliance ${REMOTE_DIR} $(basename $@) 2>&1 < $<
+ scp ${ALLIANCE_HOST}:${REMOTE_DIR}/$@ .
+ and the remote_alliance script (on ${ALLIANCE_HOST})
+/bin/csh
+cd $1
+cat >! $2.xnf
+xnf2pcf <$2.xnf >! $2.pcf
+./backend $2
+
+ There is now a "Xilinx on Linux HOWTO" at
+ http://www.polybus.com/xilinx_on_linux.html
+ I haven't tried this yet, it looks interesting.
+
+Downloading:
+
+ I use the XESS (http://www.xess.com/) XSP-10 development board, which
+ uses the PC parallel (printer) port for downloading and interaction
+ with the host. They made an old version of their download program
+ public domain, posted it at
+ http://www.xess.com/FPGA/xstools.zip ,
+ and now there is a Linux port at
+ ftp://ftp.microux.com/pub/pilotscope/xstools.tar.gz .
+
+The above hints are based on my experience with Foundation 1.5 on NT
+(gack) and Alliance 2.1i on Solaris. Your mileage may vary. Good luck!
+
+ - Larry Doolittle <LRDoolittle@xxxxxxx> August 19, 1999
+ updated February 1, 2000
+</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-icarus_xnf.html b/docs/wiki/geda-icarus_xnf.html
new file mode 100644
index 0000000..fefadfb
--- /dev/null
+++ b/docs/wiki/geda-icarus_xnf.html
@@ -0,0 +1,318 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="xilinx_netlist_format" id="xilinx_netlist_format">Xilinx Netlist Format</a></h1>
+<div class="level1">
+<pre class="code">WHAT IS XNF
+
+XNF is the Xilinx Netlist Format. This is somewhat specific to the
+Xilinx tool chain, but it is sufficiently ubiquitous that it's still
+worth it. This format can be fed to place and route tools and
+simulators. Since some third party simulators accept XNF, the format
+may be useful even independent of Xilinx parts.
+
+Icarus Verilog supports XNF as specified by the Xilinx Netlist Format
+Specification, Version 6.1.
+
+GENERATE XNF OUTPUT -- THE SHORT STORY
+
+The easiest way to compile for XNF output is with the "verilog"
+command (man verilog) and the -X switch:
+
+ % iverilog -fpart=4010e -fncf=prog.ncf -txnf prog.v
+
+This generates from the prog.v Verilog source file the prog.xnf output
+and the prog.ncf netlist constraints file. The verilog program
+arranges to call the preprocessor and the ivl compiler with all the
+correct switches for generating XNF.
+
+GENERATING XNF MACROS
+
+Icarus Verilog can be used to generate XNF implementations of devices
+that are written in Verilog and used by schematic editors such as
+OrCAD. The trick here is that the code generator automatically notices
+ports to the root module and generates the PIN= attributes needed so
+that external tools can link to the generated XNF.
+
+Icarus Verilog chooses a name for the pin. The name it chooses is the
+port name of the module. If the port is a vector, a pin is generated
+for all the bits of the vector with the bit number appended. For
+example:
+
+ module foo(in);
+ input [3:0] in;
+
+causes the single bit ports ``in0'' through ``in3'' be
+generated. Internally, the XNF file uses the bussed names instead of
+the pin name.
+
+The implication of this is that there is a chance of name collision
+with the generated XNF macro if the port names are chosen badly. It is
+best to not end a port name with decimal digits, as that can cause
+trouble at link time. Also, XNF is not case sensitive and that should
+be accounted for as well.
+
+XNF PADS IN VERILOG SOURCE
+
+You can assign wires to pads using the Icarus Verilog $attribute
+extension. Attach to a scalar signal (wire or register) the PAD
+attribute with the value that specifies the direction and pin
+number. For example:
+
+ wire foo, bar, bid;
+ $attribute(foo, "PAD", "i1"); // Input pad on pin 1
+ $attribute(bar, "PAD", "o2"); // Output pad on pin 2
+ $attribute(bid, "PAD", "b3"); // Bi-directional pad on pin 3
+
+The XNFIO function uses these attributes to locate signals that are
+connected to pads, and generates XNF I/O block devices to connect to
+the pad to do the FPGA pin buffering that is needed. So the Verilog
+programmer need not in general specify the IBUF/OBUF buffers.
+
+If the programmer does connect buffers to pads, the compiler will
+notice them and convert them to I/OBUFs automatically. For example:
+
+ buf b1 (sig, foo);
+
+connects to pad foo, so will be converted into an XNF IBUF
+device. Also:
+
+ bufif1 bt (bar, value, en);
+
+connects to pad bar so will automatically be converted into an OBUFT
+device. Icarus Verilog understands OBUF, IBUF and OBUFT (with optionally
+inverted enable) devices and will convert Verilog devices from the
+source, or generate missing devices.
+
+In addition, the Verilog programmer may explicitly declare a device as
+an I/OBUF by attaching an attribute to the device, like so:
+
+ buf b1 (sig, foo);
+ $attribute(b1, "XNF-LCA", "OBUF:O,I");
+
+This latter feature is not entirely recommended as it expects that the
+programmer really knows how the pins of the XNF device are to be
+connected. It also bypasses the efforts of the compiler, so is not
+checked for correctness.
+
+XNF STORAGE ELEMENTS
+
+Storage elements in XNF include flip-flops, latches and CLB
+rams. These devices are generated from the LPM equivalents that the
+-Fsynth functor synthesizes from behavioral descriptions.
+
+Flip-flops, or more specifically DFF devices, are generated to
+implement behavioral code like this:
+
+ reg Q;
+ always @(posedge clk) Q <= <expr>;
+
+The edge can be positive or negative, and the expression can be any
+synthesizable expression. Furthermore, the register "Q" can have
+width, which will cause the appropriate number of flip-flops to be
+created. A clock enable expression can also be added like so:
+
+ reg Q;
+ always @(posedge clk) if (<ce>) Q <= <expr>;
+
+The <ce> expression can be any synthesizable expression.
+
+With or without the CE, the generated DFF devices are written into the
+XNF output one bit at a time, with the clock input inverted if necessary.
+
+Xilinx parts also support CLB circuitry as synchronous RAMS. These
+devices are created from Verilog memories if the properties are
+right. The behavioral description that the -Fsynth functor matches to
+get a synchronous RAM looks very similar to that for a DFF:
+
+ reg [15:0] M;
+ always @(posedge clk) if (<we>) M[<addr>] <= <expr>;
+
+Note that in this case the l-value of the assignment is an addressed
+memory. This statement models writes into the memory. Reads from the
+device can be modeled with ordinary structural code, i.e.:
+
+ assign foo <= M[<addr>];
+
+For the memory to be synthesizable in the XNF target, the address
+lines for writes and reads must be connected. This corresponds to the
+limitations of the real hardware.
+
+OTHER XNF SPECIAL DEVICES
+
+There are certain special devices in XNF that Verilog does not
+naturally represent, although there are similar more generic Verilog
+devices. The most obvious and useful example is the clock driver,
+otherwise known as the global buffer BUFG. As with pads, Icarus
+Verilog uses the $attribute extension to allow you to specify special
+devices.
+
+The $attribute statement can be applied to devices much the same way
+one applies them to wires. For example, to turn a buffer into a clock
+buffer:
+
+ wire iclk, clk;
+ buf BUFG (clk, iclk);
+ $attribute(iclk, "PAD", "i1");
+ $attribute(BUFG, "XNF-LCA", "BUFG:O,I");
+
+The above statements cause the buffer BUFG to be emitted in the XNF
+output as a BUFG device with the first signal called "O" and the
+second called "I". The rest of this example connects the input of the
+BUFG to a signal from the input pin #1 and connects the output to the
+internal wire "clk". Incidentally, this example will cause an IBUF to
+be generated to connect the iclk signal to input pin #1.
+
+SUMMARY OF IVL SUPPORT FOR XNF
+
+Icarus Verilog has a code generator and synthesis functions that
+support generation of XNF netlists. The XNF modules also allow the
+programmer to use $attributes to control certain aspects of code
+generation.
+
+XNF code generation is enabled with the ``-t xnf'' flag on the command
+line. The code generator needs to know the type of part to generate
+code for, so the ``-fpart=<type>'' flag is also needed. For example,
+to generate code for the 4010E the command line might start out as:
+
+ ivl -txnf -fpart=4010e -Fsynth -Fnodangle -Fxnfio [...]
+
+Icarus Verilog includes the functions ``synth'' and ``xnfio'' to
+perform transformations and optimizations on the design before code is
+generated. The ``synth'' function matches certain behavioral constructs
+to structural components, and the xnfio function generates pads and
+fills the IOBs.
+
+SUPPORTED FLAGS
+
+ -fpart=<part>
+ Specify the type of part to target. This string is written
+ literally into the PART, record of the XNF, and may also be
+ used to control synthesis and placement.
+
+ -fncf=<path>
+ Cause the code generator to write into <path> the netlist
+ constraints needed for controlling placement and timing. This
+ switch is required if pin assignments are assigned in the
+ Verilog source.
+
+THE SYNTH FUNCTION
+
+This function does synthesis transformations on the entered design,
+making it possible to generate XNF netlist components from certain
+behavioral constructs. This is needed in Verilog for example to model
+some of the synchronous components of the XNF library.
+
+It is a bit much to expect a Verilog compiler in general to generate
+components from arbitrary behavioral descriptions, so the synth
+function works by matching statements that have some documented
+structure, and substituting them for the equivalent XNF component. A
+fully synthesize-able design, then, is one where the behavioral
+statements can all be matched and substituted by the synth function.
+
+THE XNFIO FUNCTION
+
+The "xnfio" function transforms the netlist where the IOBs are
+concerned. The signals with PAD attributes are checked, and
+surrounding circuitry generated to conform to the logic available in
+the IOB.
+
+If the pad is an OPAD, the function will look for an existing buf or
+not gate connected to the PAD signal. If the gate is appropriately
+connected, the buf or not gate will be turned into an OBUF. This pulls
+the buf or inverter into the IOB, freeing a CLB and providing the
+required pin circuitry.
+
+If the pad is an IPAD, the function will look for a buf, and convert
+that to an IBUF. Since Xilinx IOBs cannot invert the output from an
+IBUF, NOT gates cannot be absorbed as in the OPAD case.
+
+
+/*
+ * Copyright (c) 1998-1999 Stephen Williams (steve@xxxxxxxxxx)
+ *
+ * This source code is free software; you can redistribute it
+ * and/or modify it in source code form under the terms of the GNU
+ * General Public License as published by the Free Software
+ * Foundation; either version 2 of the License, or (at your option)
+ * any later version.
+ *
+ * This program is distributed in the hope that it will be useful,
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ * GNU General Public License for more details.
+ *
+ * You should have received a copy of the GNU General Public License
+ * along with this program; if not, write to the Free Software
+ * Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA
+ */
+
+
+ $Log: xnf.txt,v $
+ Revision 1.16 2003/07/15 03:49:22 steve
+ Spelling fixes.
+
+ Revision 1.15 2003/01/30 16:23:08 steve
+ Spelling fixes.
+
+ Revision 1.14 2000/08/01 21:32:40 steve
+ Use the iverilog command in documentation.
+
+ Revision 1.13 2000/08/01 02:48:42 steve
+ Support <= in synthesis of DFF and ram devices.
+
+ Revision 1.12 2000/07/25 22:49:32 steve
+ memory is not a data type in verilog.
+
+ Revision 1.11 2000/04/23 23:03:13 steve
+ automatically generate macro interface code.
+
+ Revision 1.10 1999/12/05 19:30:43 steve
+ Generate XNF RAMS from synthesized memories.
+
+ Revision 1.9 1999/11/18 03:52:20 steve
+ Turn NetTmp objects into normal local NetNet objects,
+ and add the nodangle functor to clean up the local
+ symbols generated by elaboration and other steps.
+
+ Revision 1.8 1999/11/06 04:51:42 steve
+ Support writing some XNF things into an NCF file.
+
+ Revision 1.7 1999/11/03 05:18:18 steve
+ XNF synthesis now uses the synth functor.
+
+ Revision 1.6 1999/11/02 01:43:55 steve
+ Fix iobuf and iobufif handling.
+
+ Revision 1.5 1999/10/09 17:52:27 steve
+ support XNF OBUFT devices.
+
+ Revision 1.4 1999/08/14 22:48:21 steve
+ Mention the sigfold function.
+
+ Revision 1.3 1999/07/22 02:05:20 steve
+ is_constant method for PEConcat.
+
+ Revision 1.2 1999/07/18 21:17:51 steve
+ Add support for CE input to XNF DFF, and do
+ complete cleanup of replaced design nodes.
+
+ Revision 1.1 1999/05/01 02:57:11 steve
+ XNF target documentation.</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-igarus_fpga_lcg.html b/docs/wiki/geda-igarus_fpga_lcg.html
new file mode 100644
index 0000000..806a427
--- /dev/null
+++ b/docs/wiki/geda-igarus_fpga_lcg.html
@@ -0,0 +1,249 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="fpga_loadable_code_generator_for_icarus_verilog" id="fpga_loadable_code_generator_for_icarus_verilog">FPGA Loadable Code Generator for Icarus Verilog</a></h1>
+<div class="level1">
+<pre class="code">FPGA LOADABLE CODE GENERATOR FOR Icarus Verilog
+
+ Copyright 2001 Stephen Williams
+ $Id: fpga.txt,v 1.12 2005/09/19 21:45:36 steve Exp $
+
+The FPGA code generator supports a variety of FPGA devices, writing
+XNF or EDIF depending on the target. You can select the architecture
+of the device, and the detailed part name. The architecture is used to
+select library primitives, and the detailed part name is written into
+the generated file for the use of downstream tools.
+
+INVOKING THE FPGA TARGET
+
+The code generator is invoked with the -tfpga flag to iverilog. It
+understands the part= and the arch= parameters, which can be set with
+the -p flag of iverilog:
+
+ iverilog -parch=virtex -ppart=v50-pq240-6 -tfpga foo.vl
+
+This example selects the Virtex architecture, and give the detailed
+part number as v50-pq240-6. The output is written into a.out unless a
+different output file is specified with the -o flag.
+
+The following is a list of architecture types that this code generator
+supports.
+
+* arch=lpm
+
+This is a device independent format, where the gates are device types
+as defined by the LPM 2 1 0 specification. Some backend tools may take
+this format, or users may write interface libraries to connect these
+netlists to the device in question.
+
+* arch=generic-edif (obsolete)
+
+This is generic EDIF code. It doesn't necessarily work because the
+external library is not available to the code generator. But, what it
+does is generate generic style gates that a portability library can
+map to target gates if desired.
+
+* arch=generic-xnf (obsolete)
+
+If this is selected, then the output is formatted as an XNF file,
+suitable for most any type of device. The devices that it emits
+are generic devices from the unified library. Some devices are macros,
+you may need to further resolve the generated XNF to get working
+code for your part.
+
+* arch=virtex
+
+If this is selected, then the output is formatted as an EDIF 200 file,
+suitable for Virtex class devices. This is supposed to know that you
+are targeting a Virtex part, so can generate primitives instead of
+using external macros. It includes the VIRTEX internal library, and
+should work properly for any Virtex part.
+
+* arch=virtex2
+
+If this is selected, then the output is EDIF 2 0 0 suitable for
+Virtex-II and Virtex-II Pro devices. It uses the VIRTEX2 library, but
+is very similar to the Virtex target.
+
+XNF ROOT PORTS
+
+ NOTE: As parts are moved over to EDIF format, XNF support will be
+ phased out. Current Xilinx implementation tools will accept EDIF
+ format files even for the older parts, and non-Xilinx implementation
+ tools accept nothing else.
+
+When the output format is XNF, the code generator will generate "SIG"
+records for the signals that are ports of the root module. The name is
+declared as an external pin that this macro makes available.
+
+The name given to the macro pin is generated from the base name of the
+signal. If the signal is one bit wide, then the pin name is exactly
+the module port name. If the port is a vector, then the pin number is
+given as a vector. For example, the module:
+
+ module main(out, in);
+ output out;
+ input [2:0] in;
+ [...]
+ endmodule
+
+leads to these SIG, records:
+
+ SIG, main/out, PIN=out
+ SIG, main/in<2>, PIN=in2
+ SIG, main/in<1>, PIN=in1
+ SIG, main/in<0>, PIN=in0
+
+
+EDIF ROOT PORTS
+
+The EDIF format is more explicit about the interface into an EDIF
+file. The code generator uses that control to generate an explicit
+interface definition into the design. (This is *not* the same as the
+PADS of a part.) The generated EDIF interface section contains port
+definitions, including the proper direction marks.
+
+With the (rename ...) s-exp in EDIF, it is possible to assign
+arbitrary text to port names. The EDIF code generator therefore does
+not resort to the mangling that is needed for the XNF target. The base
+name of the signal that is an input or output is used as the name of
+the port, complete with the proper case.
+
+However, since the ports are single bit ports, the name of vectors
+includes the string "[0]" where the number is the bit number. For
+example, the module:
+
+
+ module main(out, in);
+ output out;
+ input [2:0] in;
+ [...]
+ endmodule
+
+creates these ports:
+
+ out OUTPUT
+ in[0] INPUT
+ in[1] INPUT
+ in[2] INPUT
+
+Target tools, including Xilinx Foundation tools, understand the []
+characters in the name and recollect the signals into a proper bus
+when presenting the vector to the user.
+
+
+PADS AND PIN ASSIGNMENT
+
+The ports of a root module may be assigned to specific pins, or to a
+generic pad. If a signal (that is a port) has a PAD attribute, then
+the value of that attribute is a list of locations, one for each bit
+of the signal, that specifies the pin for each bit of the signal. For
+example:
+
+ module main( (* PAD = "P10" *) output out,
+ (* PAD = "P20,P21,P22" *) input [2:0] in);
+
+ [...]
+
+ endmodule
+
+In this example, port ``out'' is assigned to pin 10, and port ``in''
+is assigned to pins 20-22. If the architecture supports it, a pin
+number of 0 means let the back end tools choose a pin. The format of
+the pin number depends on the architecture family being targeted, so
+for example Xilinx family devices take the name that is associated
+with the "LOC" attribute.
+
+NOTE: If a module port is assigned to a pin (and therefore attached to
+a PAD) then it is *not* connected to a port of the EDIF file. This is
+because the PAD (and possibly IBUF or OBUF) would become an extra
+driver to the port. An error.
+
+
+SPECIAL DEVICES
+
+The code generator supports the "cellref" attribute attached to logic
+devices to cause specific device types be generated, instead of the
+usual device that the code generator might generate. For example, to
+get a clock buffer out of a Verilog buf:
+
+ buf my_gbuf(out, in);
+ $attribute(my_buf, "cellref", "GBUF:O,I");
+
+The "cellref" attribute tells the code generator to use the given
+cell. The syntax of the value is:
+
+ <cell type>:<pin name>,...
+
+The cell type is the name of the library part to use. The pin names
+are the names of the type in the library, in the order that the logic
+device pins are connected.
+
+
+COMPILING WITH XILINX FOUNDATION
+
+Compile a single-file design with command line tools like so:
+
+ % iverilog -parch=virtex -o foo.edf foo.vl
+ % edif2ngd foo.edf foo.ngo
+ % ngdbuild -p v50-pq240 foo.ngo foo.ngd
+ % map -o map.ncd foo.ngd
+ % par -w map.ncd foo.ncd
+
+---
+$Log: fpga.txt,v $
+Revision 1.12 2005/09/19 21:45:36 steve
+ Spelling patches from Larry.
+
+Revision 1.11 2003/08/07 05:17:34 steve
+ Add arch=lpm to the documentation.
+
+Revision 1.10 2003/07/04 03:57:19 steve
+ Allow attributes on Verilog 2001 port declarations.
+
+Revision 1.9 2003/07/04 01:08:03 steve
+ PAD attribute can be used to assign pins.
+
+Revision 1.8 2003/07/02 00:26:49 steve
+ Fix spelling of part= flag.
+
+Revision 1.7 2003/03/24 02:28:38 steve
+ Document the virtex2 architecture.
+
+Revision 1.6 2003/03/24 00:47:54 steve
+ Add new virtex2 architecture family, and
+ also the new edif.h EDIF management functions.
+
+Revision 1.5 2002/04/30 04:26:42 steve
+ Spelling errors.
+
+Revision 1.4 2001/09/16 22:26:47 steve
+ Support the cellref attribute.
+
+Revision 1.3 2001/09/16 01:48:16 steve
+ Suppor the PAD attribute on signals.
+
+Revision 1.2 2001/09/06 04:28:40 steve
+ Separate the virtex and generic-edif code generators.
+
+Revision 1.1 2001/09/02 23:58:49 steve
+ Add documentation for the code generator.
+
+</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-installation.fr.html b/docs/wiki/geda-installation.fr.html
new file mode 100644
index 0000000..9aa6a9e
--- /dev/null
+++ b/docs/wiki/geda-installation.fr.html
@@ -0,0 +1,269 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#aide_a_l_installation" class="toc">Aide à l'installation</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#comment_installer_la_suite_geda" class="toc">Comment installer la Suite gEDA?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#comment_desinstaller_la_suite_geda" class="toc">Comment désinstaller la Suite gEDA?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#pourquoi_voudrais-je_desinstaller_la_suite_geda" class="toc">Pourquoi voudrais-je désinstaller la Suite gEDA?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#aaaaargh_j_ai_mis_un_cd_dans_le_lecteur_je_l_ai_monte_mais_rien_ne_se_produit" class="toc">Aaaaargh! J'ai mis un CD dans le lecteur, je l'ai monté mais rien ne se produit!</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#aidez-moi_je_tente_une_installation_en_utilisant_le_cd_rom_mais_le_magicien_d_installation_m_indique_une_erreur" class="toc">Aidez-moi! Je tente une installation en utilisant le CD ROM mais le magicien d'installation m'indique une erreur!</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#waaaaa_l_installation_s_est_terminee_mais_j_ai_un_segfault_ou_autre_probleme_lorsque_je_lance_gschem_ou_gattrib_ou_gnetlist_ou" class="toc">Waaaaa! L'installation s'est terminée mais j'ai un segfault (ou autre problème) lorsque je lance gschem (ou gattrib ou gnetlist, ou. . . )!</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#fedora_core_4_install_notes" class="toc">Fedora Core 4 install notes</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#fedora_core_3_install_notes" class="toc">Fedora Core 3 install notes</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#fedora_core_2_install_notes" class="toc">Fedora Core 2 install notes</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#fedora_core_1_install_notes" class="toc">Fedora Core 1 install notes</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#suse_9.3_install_notes" class="toc">Suse 9.3 install notes</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#suse_10.0_install_notes" class="toc">Suse 10.0 install notes</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#suse_10.1_install_notes" class="toc">Suse 10.1 install notes</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#notes_d_installation_debian" class="toc">Notes d'installation Debian</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#windows_install_notes" class="toc">Windows install notes</a></span></div></li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="aide_a_l_installation" id="aide_a_l_installation">Aide à l'installation</a></h1>
+<div class="level1">
+
+<p>
+Cette section fournit quelques informations utiles aux personnes qui veulent installer gEDA sur leur ordinateur.
+</p>
+
+</div>
+<!-- SECTION "Aide à l'installation" [1-151] -->
+<h2><a name="comment_installer_la_suite_geda" id="comment_installer_la_suite_geda">Comment installer la Suite gEDA?</a></h2>
+<div class="level2">
+
+<p>
+La manière la plus facile dâ??installer la Suite gEDA est de graver le CDROM et de lâ??utiliser. Les instructions sont dans le README disponible sur la <a href="http://geda.seul.org/download.html"; class="urlextern" title="http://geda.seul.org/download.html"; rel="nofollow">page des téléchargements</a>. <strong><em>Notez que lâ??installateur du CD ROM suppose que vous êtes sur le bureau Gnome! La même chose est vraie pour les outils gEDA: Ils utilisent le jeu de widgets GTK qui soutend Gnome. Si vous êtes sous KDE, vous avez au moins besoin des bibliothèques Gnome dâ??installées sur votre machine avant de tenter de lancer lâ??installateur.</em></strong>
+</p>
+
+<p>
+Le CD de la Suite gEDA contient les tarballs de plus dâ??une douzaine dâ??applications populaires de gEDA. Il incorpore aussi un «·magicien·» graphique qui contrôle la configuration de votre système, vous pose quelques questions et surveille la compilation et lâ??installation des différentes applications gEDA. Le magicien dâ??installation automatise le processus normal â??./configure && make && make installâ?? utilisé pour construire les logiciels GNU depuis les sources. Câ??est la raison pour laquelle il est plus ou moins indépendant de la plate-forme (tant que vous faites tourner Linux).
+</p>
+
+<p>
+Dans lâ??éventualité où le magicien dâ??installation ne peut pas installer la Suite gEDA automatiquement, vous pouvez encore extraire les tarballs de source du CD et de les construire manuellement. Les instructions sont disponibles sur la page de téléchargement, de même que le fichier INSTALL sur le CD.
+</p>
+
+<p>
+De la même manière, des personnes ont créé des RPM RedHat, des Debs Debian et des paquets Mac OSX Fink si vous préférez les installer de cette manière. Ces distributions binaires sont disponibles sur la <a href="http://geda.seul.org/download.html"; class="urlextern" title="http://geda.seul.org/download.html"; rel="nofollow">page de téléchargement</a>. Finalement, les tarballs de sources pour tous les programmes sont aussi disponiblessur la <a href="http://geda.seul.org/download.html"; class="urlextern" title="http://geda.seul.org/download.html"; rel="nofollow">page de téléchargements</a>.
+</p>
+
+<p>
+Au fait, câ??est toujours une bonne idée dâ??installer gEDA dans son propre répertoire. De cette manière, lorsque vous voulez mettre à jour le paquet, vous avez juste besoin dâ??effacer le répertoire et ré-installer. (Ce conseil est vrai pour toute grande suite dâ??applications dâ??unix.) Vous en avez plus ci-dessous.
+</p>
+
+<p>
+Finalement, si ces instructions ne sont pas suffisantes, David Hart a placé un <a href="http://www.offramp.com/Lab-Install/doku.php?id=fc4#create_user_geda_account_and_install_geda_tool_suite"; class="urlextern" title="http://www.offramp.com/Lab-Install/doku.php?id=fc4#create_user_geda_account_and_install_geda_tool_suite"; rel="nofollow">guide for configuring and installing gEDA</a> utile et détaillé (pour Fedora Core 4 mais qui aidera probablement aussi avec les autres distros), de même quâ??un <a href="http://www.offramp.com/Lab-Install/doku.php?id=fc4#geda_tutorial"; class="urlextern" title="http://www.offramp.com/Lab-Install/doku.php?id=fc4#geda_tutorial"; rel="nofollow">tutoriel gEDA</a> pour les nouveaux utilisateurs.
+</p>
+
+</div>
+<!-- SECTION "Comment installer la Suite gEDA?" [152-2869] -->
+<h2><a name="comment_desinstaller_la_suite_geda" id="comment_desinstaller_la_suite_geda">Comment désinstaller la Suite gEDA?</a></h2>
+<div class="level2">
+
+<p>
+Au moment de lâ??écriture de cet article, il nâ??existe pas de méthode pour désinstaller la Suite gEDA. Contrairement à certain systèmes dâ??exploitation commerciaux, Linux (et unix) nâ??ont pas été conçus dans lâ??idée de faciliter la gestion des paquets facilement et nous souffrons de cet héritage.
+</p>
+
+<p>
+Câ??est la raison pour laquelle nous recommandons dâ??installer la Suite gEDA dans son propre répertoire. Par exemple, lâ??installateur CD placera les exécutables de la Suite dans <strong><code>${HOME}/geda-install</code></strong> par défaut. Alors, si vous avez besoin de désinstaller la Suite gEDA, vous pouvez juste effacer le répertoire complet.
+</p>
+
+<p>
+<span class="hilited">(Dâ??autres méthodes avancées pour installer/désinstaller les paquets sur Linux/unix existe aussi. Quelquâ??un pourrait-il écrire quelque chose sur le sujet?)</span>
+</p>
+
+</div>
+<!-- SECTION "Comment désinstaller la Suite gEDA?" [2870-3713] -->
+<h2><a name="pourquoi_voudrais-je_desinstaller_la_suite_geda" id="pourquoi_voudrais-je_desinstaller_la_suite_geda">Pourquoi voudrais-je désinstaller la Suite gEDA?</a></h2>
+<div class="level2">
+
+<p>
+Différentes applications appartenant à gEDA/gaf utilisent la même bibliothèque partagée, libgeda.so. Les éléments dans la bibliothèque changent dâ??une version gEDA à lâ??autre. Câ??est la raison pour laquelle les applications ne peuvent pas être liées à libgeda.so si leur code de version est différent.
+</p>
+
+<p>
+Si vous avez besoin de mettre à jour une application de gEDA/gaf, vous devrez dâ??abord désinstaller votre ancienne version puis intaller un tout nouveau jeu dâ??applications, incluant la bibliothèque et tous les composants de gEDA/gaf.
+</p>
+
+<p>
+Alternativement, vous pouvez installer le nouveau gEDA/gaf dans un nouveau répertoire et éditer alors vos variables dâ??environnement <strong><code>${PATH}</code></strong>, <strong><code>${PKG_CONFIG_PATH}</code></strong> puis <strong><code>${LD_LIBRARY_PATH}</code></strong> pour enlever lâ??ancien répertoire et pointer vers le nouveau. Assurez-vous de le faire <strong>avant</strong> de tenter une nouvelle installation de gEDA/gaf.
+</p>
+
+</div>
+<!-- SECTION "Pourquoi voudrais-je désinstaller la Suite gEDA?" [3714-4683] -->
+<h2><a name="aaaaargh_j_ai_mis_un_cd_dans_le_lecteur_je_l_ai_monte_mais_rien_ne_se_produit" id="aaaaargh_j_ai_mis_un_cd_dans_le_lecteur_je_l_ai_monte_mais_rien_ne_se_produit">Aaaaargh! J'ai mis un CD dans le lecteur, je l'ai monté mais rien ne se produit!</a></h2>
+<div class="level2">
+
+<p>
+ Dâ??une manière surprenante, il y a encore des personnes qui copient simplement le fichier installateur .iso en utilisant «·cp·» vers un CD vierge et tentent ensuite de lâ??utiliser tel quel. Cela ne marche pas. Vous avez besoin de «·graver·» un CD avec un .iso dâ??une manière qui écrit le système de fichier complet directement sur le CDROM. La commande linux/unix pour ce faire est habituellement «·cdrecord·» ou, peut être, une interface graphique dérivée de cet utilitaire. Il ne suffit pas de juste «·cp·» le fichier .iso sur le CD vierge!
+</p>
+
+<p>
+De nombreuses distributions Linux récentes ne lanceront pas automatiquement les exécutables sur un média installé. Câ??est une précaution de sécurité. Pour passer outre, vous avez besoin de monter un CD qui donne les permissions de lancer un exécutable. Par exemple, avec Gentoo et Debian, vous devez monter le CD ROM de cette manière:
+</p>
+<pre class="code">mount -o exec -t iso9660 /dev/cdrom /mnt/cdrom</pre>
+
+<p>
+Le drapeau précis ou le point de montage adéquat de votre distribution peut être un peu différent·; lisez le manuel pour mount («·man mount·») si vous avez des questions sur la manière de le faire.
+</p>
+
+<p>
+Après avoir monté le CD avec des permissions dâ??exécution, vous pouvez alors lancer lâ??installateur depuis la ligne de commande comme ceci·:
+</p>
+<pre class="code">/mnt/cdrom/installer</pre>
+
+<p>
+Ã? ce point, lâ??interface graphique du magicien dâ??installation devrait apparaître et vous pouvez entrer dans lâ??installation. Si vous ne pouvez pas installer, veuillez tenter un «·ls·» sur le CD pour vérifier sâ??il est lisible. Câ??est à dire en faitant:
+</p>
+<pre class="code">ls -l /mnt/cdrom/</pre>
+
+<p>
+Et assurez-vous dâ??avoir une liste de répertoires plutôt dâ??un message dâ??erreur (ou rien du tout).
+</p>
+
+</div>
+<!-- SECTION "Aaaaargh! J'ai mis un CD dans le lecteur, je l'ai monté mais rien ne se produit!" [4684-6523] -->
+<h2><a name="aidez-moi_je_tente_une_installation_en_utilisant_le_cd_rom_mais_le_magicien_d_installation_m_indique_une_erreur" id="aidez-moi_je_tente_une_installation_en_utilisant_le_cd_rom_mais_le_magicien_d_installation_m_indique_une_erreur">Aidez-moi! Je tente une installation en utilisant le CD ROM mais le magicien d'installation m'indique une erreur!</a></h2>
+<div class="level2">
+
+<p>
+ Dâ??abord, gardez en mémoire que lâ??installateur du CD ROM ne fonctionne quâ??avec Linux. Lâ??installateur du CD ROM ne fonctionnera pas sur Sun, BSD ou Mac OSX et il ne fonctionnera certainement pas avec Windows.
+</p>
+
+<p>
+Comme règle général, si vous avez des problèmes en installant gEDA depuis le CD, vous avez ici des éléments que vous pouvez tenter:
+</p>
+<ol>
+<li class="level1"><div class="li"> Si vous lancez lâ??installateur avec le drapeau <strong><code>â??log</code></strong>, il placera un fichier appelé Install.log dans votre répertoire local (depuis où vous avez lancé votre installateur). Ce fichier est un journal de toutes les commandes émises et toutes les réponses générées pendant le processus dâ??installation. Il vous permet de sauvegarder les données affichées dans la fenêtre journal lors de lâ??installation. Lancer lâ??installateur avec <strong><code>â??log</code></strong> est une bonne idée si vous avez des problèmes·; vous pouvez envoyer votre fichier Install.log à un expert qui pourra diagnostiquer votre problème. Vous en saurez plus après.</div>
+</li>
+<li class="level1"><div class="li"> Après avoir eu un problème, la première chose à faire est de regarder le wiki de gEDA. Il est plus que probable que quelquâ??un a déjà eu votre problème et lâ??a rapporté et quâ??une solution a été trouvée et postée. Des distributions Linux différentes ont eu des problèmes différents dans le passé. En focntion de votre distribution, consultez les sections dâ??aide ci-dessous.</div>
+</li>
+<li class="level1"><div class="li"> Si aucune mention de votre problème spécifique nâ??a été posté sur le Wiki, tentez une recherche sur Google. LEs trucs et astuces de GEDA sont dans différents endroits sur la toile et Google peut les trouver pour vous. De même, la liste des geda-user est indexée continuellement par Google. Comme les gens postent fréquement des bogues et des correctifs, Google vous aidera à trouver ces rapports.</div>
+</li>
+<li class="level1"><div class="li"> Ensuite, tentez de poster une question sur la liste des geda-user. Notez que vous devez dâ??abord vous enregistrer. Dâ??autre peuvent avoir déjà développé une solution à votre problème. Quelques uns des experts hantent cette liste et peut offrir quelques sugestions dâ??aide.</div>
+</li>
+</ol>
+
+</div>
+<!-- SECTION "Aidez-moi! Je tente une installation en utilisant le CD ROM mais le magicien d'installation m'indique une erreur!" [6524-8722] -->
+<h2><a name="waaaaa_l_installation_s_est_terminee_mais_j_ai_un_segfault_ou_autre_probleme_lorsque_je_lance_gschem_ou_gattrib_ou_gnetlist_ou" id="waaaaa_l_installation_s_est_terminee_mais_j_ai_un_segfault_ou_autre_probleme_lorsque_je_lance_gschem_ou_gattrib_ou_gnetlist_ou">Waaaaa! L'installation s'est terminée mais j'ai un segfault (ou autre problème) lorsque je lance gschem (ou gattrib ou gnetlist, ou. . . )!</a></h2>
+<div class="level2">
+
+<p>
+Après que vous ayiez installé la Suite gEDA depuis le CD ROM, assurez-vous dâ??avoir fait ce qui suit:
+</p>
+<ol>
+<li class="level1"><div class="li"> Mettez votre <strong><code>${PATH}</code></strong> pour quâ??il pointe vers lâ??endroit où vos nouveau exécutables gEDA sont placés (par exemple, <strong><code>/home/your-name/geda-install/bin</code></strong>). Assurez-vous que vous enlevez les pointeurs vers la anciennes versions de gEDA, sâ??ils existent. Vous ne devez pas seulement mettre le <strong><code>${PATH}</code></strong> dans votre shell courant mais vous devriez alors mettre à jour vos scripts de config (i.e. .bashrc ou .cshrc)</div>
+</li>
+<li class="level1"><div class="li"> Tapez «·rehash·» pour mettre à jour votre chemin de recherche des exécutables.</div>
+</li>
+<li class="level1"><div class="li"> Changez votre <strong><code>${LD_LIBRARY_PATH}</code></strong> pour quâ??il pointe sur lâ??endroitoù sont vos nouveaux exécutables gEDA (par exemple, <strong><code>/home/your-name/geda-install/lib</code></strong>). Assurez-vous dâ??enlever les pointeurs des anciennes versions de gEDA, si elles existent. Vous ne devez pas seulement mettre le <strong><code>${LD_LIBRARY_PATH}</code></strong> dans votre shell courant mais vous devriez alors mettre à jour vos scripts de config (i.e. .bashrc ou .cshrc)</div>
+</li>
+<li class="level1"><div class="li"> LAncez «·su -c ldconfig·» pour indiquer au noyau où trouver votre nouvelle libgeda.so.</div>
+</li>
+</ol>
+
+</div>
+<!-- SECTION "Waaaaa! L'installation s'est terminée mais j'ai un segfault (ou autre problème) lorsque je lance gschem (ou gattrib ou gnetlist, ou. . . )!" [8723-10033] -->
+<h2><a name="fedora_core_4_install_notes" id="fedora_core_4_install_notes">Fedora Core 4 install notes</a></h2>
+<div class="level2">
+
+<p>
+<a href="geda-fc4.html" class="wikilink1" title="geda-fc4.html">FC4 notes available here</a>
+</p>
+
+</div>
+<!-- SECTION "Fedora Core 4 install notes" [10034-10112] -->
+<h2><a name="fedora_core_3_install_notes" id="fedora_core_3_install_notes">Fedora Core 3 install notes</a></h2>
+<div class="level2">
+
+<p>
+<a href="geda-fc3.html" class="wikilink1" title="geda-fc3.html">FC3 notes available here</a>
+</p>
+
+</div>
+<!-- SECTION "Fedora Core 3 install notes" [10113-10191] -->
+<h2><a name="fedora_core_2_install_notes" id="fedora_core_2_install_notes">Fedora Core 2 install notes</a></h2>
+<div class="level2">
+
+<p>
+<a href="geda-fc2.html" class="wikilink1" title="geda-fc2.html">FC2 notes available here</a>
+</p>
+
+</div>
+<!-- SECTION "Fedora Core 2 install notes" [10192-10270] -->
+<h2><a name="fedora_core_1_install_notes" id="fedora_core_1_install_notes">Fedora Core 1 install notes</a></h2>
+<div class="level2">
+
+<p>
+<a href="geda-fc1.html" class="wikilink1" title="geda-fc1.html">FC1 notes available here</a>
+</p>
+
+</div>
+<!-- SECTION "Fedora Core 1 install notes" [10271-10349] -->
+<h2><a name="suse_9.3_install_notes" id="suse_9.3_install_notes">Suse 9.3 install notes</a></h2>
+<div class="level2">
+
+<p>
+<a href="geda-suse_9.3.html" class="wikilink1" title="geda-suse_9.3.html">SuSE 9.3 notes available here</a>
+</p>
+
+</div>
+<!-- SECTION "Suse 9.3 install notes" [10350-10433] -->
+<h2><a name="suse_10.0_install_notes" id="suse_10.0_install_notes">Suse 10.0 install notes</a></h2>
+<div class="level2">
+
+<p>
+<a href="geda-suse_10.0.html" class="wikilink1" title="geda-suse_10.0.html">SuSE 10.0 notes available here</a>
+</p>
+
+</div>
+<!-- SECTION "Suse 10.0 install notes" [10434-10520] -->
+<h2><a name="suse_10.1_install_notes" id="suse_10.1_install_notes">Suse 10.1 install notes</a></h2>
+<div class="level2">
+
+<p>
+<a href="geda-suse_10.1.html" class="wikilink1" title="geda-suse_10.1.html">SuSE 10.1 notes available here</a>
+</p>
+
+</div>
+<!-- SECTION "Suse 10.1 install notes" [10521-10607] -->
+<h2><a name="notes_d_installation_debian" id="notes_d_installation_debian">Notes d'installation Debian</a></h2>
+<div class="level2">
+
+<p>
+Les <a href="geda-debian.fr.html" class="wikilink1" title="geda-debian.fr.html">notes d'installation Debian sont disponibles ici</a>
+</p>
+
+</div>
+<!-- SECTION "Notes d'installation Debian" [10608-10720] -->
+<h2><a name="windows_install_notes" id="windows_install_notes">Windows install notes</a></h2>
+<div class="level2">
+
+<p>
+<a href="geda-cygwin.html" class="wikilink1" title="geda-cygwin.html">Cygwin notes available here</a>
+</p>
+
+</div>
+<!-- SECTION "Windows install notes" [10721-] --></body>
+</html>
diff --git a/docs/wiki/geda-installation.html b/docs/wiki/geda-installation.html
new file mode 100644
index 0000000..a035f2d
--- /dev/null
+++ b/docs/wiki/geda-installation.html
@@ -0,0 +1,150 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#installation_help" class="toc">Installation help</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#debian_distributions" class="toc">Debian distributions</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#fedora_and_redhat_distributions" class="toc">Fedora and RedHat distributions</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#suse_and_opensuse_distributions" class="toc">SuSE and OpenSuSE distributions</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#mac_osx_distributions" class="toc">Mac OSX distributions</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#windows_distributions" class="toc">Windows distributions</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#geda_binary_suite_installer" class="toc">"gEDA Binary Suite" Installer</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#cvs_gitunstable_testing" class="toc">CVS / git: Unstable/Testing</a></span></div></li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="installation_help" id="installation_help">Installation help</a></h1>
+<div class="level1">
+
+<p>
+This section provides some information useful to people who want to install gEDA onto their computers.
+</p>
+
+</div>
+<!-- SECTION "Installation help" [1-136] -->
+<h2><a name="debian_distributions" id="debian_distributions">Debian distributions</a></h2>
+<div class="level2">
+
+<p>
+The repository of the Debian distribution contains <a href="http://packages.debian.org/cgi-bin/search_packages.pl?keywords=geda&searchon=names&subword=1&version=all&release=all"; class="urlextern" title="http://packages.debian.org/cgi-bin/search_packages.pl?keywords=geda&searchon=names&subword=1&version=all&release=all"; rel="nofollow">binary packages</a> of the core geda/gaf tools including <a href="http://packages.debian.org/cgi-bin/search_packages.pl?keywords=gschem&searchon=names&subword=1&version=all&release=all"; class="urlextern" title="http://packages.debian.org/cgi-bin/search_packages.pl?keywords=gschem&searchon=names&subword=1&version=all&release=all"; rel="nofollow">gschem</a>, <a href="http://packages.debian.org/cgi-bin/search_packages.pl?keywords=pcb&searchon=names&subword=1&version=all&release=all"; class="urlextern" title="http://packages.debian.org/cgi-bin/search_packages.pl?keywords=pcb&searchon=names&subword=1&version=all&release=all"; rel="nofollow">pcb</a>, <a href="http://packages.debian.org/cgi-bin/search_packages.pl?keywords=gnucap&searchon=names&subword=1&version=all&release=all"; class="urlextern" title="http://packages.debian.org/cgi-bin/search_packages.pl?keywords=gnucap&searchon=names&subword=1&version=all&release=all"; rel="nofollow">gnucap</a> and <a href="http://packages.debian.org/cgi-bin/search_packages.pl?keywords=gerbv&searchon=names&subword=1&version=all&release=all"; class="urlextern" title="http://packages.debian.org/cgi-bin/search_packages.pl?keywords=gerbv&searchon=names&subword=1&version=all&release=all"; rel="nofollow">gerbv</a>. Due to license specifics some tools like ngspice cannot be distributed by Debian. However, the geda suite iso image will work nicely on Debian, if you have have prepared your box by installing some development packages. For more detailed information, see the <a href="geda-debian.html" class="wikilink1" title="geda-debian.html">debian installation notes</a>.
+</p>
+
+</div>
+<!-- SECTION "Debian distributions" [137-1217] -->
+<h2><a name="fedora_and_redhat_distributions" id="fedora_and_redhat_distributions">Fedora and RedHat distributions</a></h2>
+<div class="level2">
+
+<p>
+For RedHat distributions you may wish to download the <a href="http://www.sp5pbe.waw.pl/~sp5smk/software.html"; class="urlextern" title="http://www.sp5pbe.waw.pl/~sp5smk/software.html"; rel="nofollow"> RPM binaries</a> prepared by Wojciech Kazubski.
+</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>.
+</p>
+
+<p>
+For more informations read the <a href="geda-fedora_rpm_installation.html" class="wikilink1" title="geda-fedora_rpm_installation.html"> fedora rpm installation notes</a>.
+</p>
+
+</div>
+<!-- SECTION "Fedora and RedHat distributions" [1218-1660] -->
+<h2><a name="suse_and_opensuse_distributions" id="suse_and_opensuse_distributions">SuSE and OpenSuSE distributions</a></h2>
+<div class="level2">
+
+<p>
+For SuSE and OpenSuSE distributions there are rpm packages for several gEDA related programms. Theyâ??ve been prepared by Werner Hoch using the OpenSuSE Build Service.
+</p>
+
+<p>
+You can install the rpm packages with YaST, yum or any other installation tool. The packages are located in a yum repository at <a href="http://download.opensuse.org/repositories/science/"; class="urlextern" title="http://download.opensuse.org/repositories/science/"; rel="nofollow">OpenSuSE</a> or <a href="ftp://ftp-1.gwdg.de/pub/opensuse/repositories/science/"; class="urlextern" title="ftp://ftp-1.gwdg.de/pub/opensuse/repositories/science/"; rel="nofollow">OpenSuSE mirror</a>.
+</p>
+
+<p>
+For more informations read the <a href="geda-suse_rpm_installation.html" class="wikilink1" title="geda-suse_rpm_installation.html"> SuSE rpm installation notes</a>.
+</p>
+
+</div>
+<!-- SECTION "SuSE and OpenSuSE distributions" [1661-2241] -->
+<h2><a name="mac_osx_distributions" id="mac_osx_distributions">Mac OSX distributions</a></h2>
+<div class="level2">
+
+<p>
+For Mac OSX 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 Fink binaries</a> prepared by Charles Lepple. See also <a href="geda-devmacosx.html" class="wikilink1" title="geda-devmacosx.html">notes on using gEDA on Mac</a>.
+</p>
+
+</div>
+<!-- SECTION "Mac OSX distributions" [2242-2480] -->
+<h2><a name="windows_distributions" id="windows_distributions">Windows distributions</a></h2>
+<div class="level2">
+
+<p>
+MinGW hooks are built into many of the gEDA applications. Therefore, knowledgeable individuals have been able to build, install, and run many of the tools on Windows systems. Also, the tools do run on Windows under the <a href="http://www.cygwin.com/"; class="urlextern" title="http://www.cygwin.com/"; rel="nofollow">Cygwin</a> environment. However, binary executables for most of the gEDA Suite are not currently distributed by the gEDA Project. If you are a developer and wish to provide ongoing support for Windows, please contact the project via the geda-user e-mailing list.
+</p>
+
+<p>
+Please see the <a href="geda-cygwin.html" class="wikilink1" title="geda-cygwin.html">cygwin</a> page on this wiki for more information on building gEDA using cygwin.
+</p>
+
+</div>
+<!-- SECTION "Windows distributions" [2481-3128] -->
+<h2><a name="geda_binary_suite_installer" id="geda_binary_suite_installer">"gEDA Binary Suite" Installer</a></h2>
+<div class="level2">
+
+<p>
+If there are no current packages for your distribution available, the recommended method is installation from the â??gEDA Binary Suiteâ?? installer. The latest version of this installer is available on-line at <a href="http://www.geda.seul.org/download.html"; class="urlextern" title="http://www.geda.seul.org/download.html"; rel="nofollow">gEDA Downloads</a> web-page.
+</p>
+
+</div>
+<!-- SECTION "gEDA Binary Suite Installer" [3129-3449] -->
+<h2><a name="cvs_gitunstable_testing" id="cvs_gitunstable_testing">CVS / git: Unstable/Testing</a></h2>
+<div class="level2">
+
+<p>
+For those already familiar with the gEDA/gaf applications and those who need the latest stuff, access to source-code repository is available (this has changed from <acronym title="Concurrent Versions System">CVS</acronym> to a <a href="http://git.or.cz/"; class="urlextern" title="http://git.or.cz/"; rel="nofollow">git</a> repository). This is the latest developer source-code version of the application.<br/>
+ Installation from the Unstable/Testing repository is appropriate for those:
+</p>
+<ul>
+<li class="level1"><div class="li"> Seeking a solution to a specific problem that was submitted to the development team, e.g., to test the â??fixâ?? so that the developers can be informed that the â??fixâ?? works.</div>
+</li>
+<li class="level1"><div class="li"> With significant working knowledge of the gEDA Tools and quite some knowledge in using and installing from git.</div>
+</li>
+</ul>
+
+<p>
+ This usually requires access to several existing designs known to work in the current stable release of the gEDA Tools, so that comparisons can be made and issues brought to the attention of the developer/user community (via the e-mail lists or the bug tracker). You must build and install the packages in the following order:
+</p>
+<pre class="code"> 1. libgeda
+ 2. symbols
+ 3. gschem
+ 4. gnetlist
+ 5. gsymcheck
+ 6. gattrib
+ 7. utils
+ 8. docs
+ 9. examples</pre>
+
+<p>
+ The repository can be found <a href="http://geda.seul.org/developer.html"; class="urlextern" title="http://geda.seul.org/developer.html"; rel="nofollow">here</a>.
+</p>
+
+</div>
+<!-- SECTION "CVS / git: Unstable/Testing" [3450-] --></body>
+</html>
diff --git a/docs/wiki/geda-installed_plugins.html b/docs/wiki/geda-installed_plugins.html
new file mode 100644
index 0000000..39ae539
--- /dev/null
+++ b/docs/wiki/geda-installed_plugins.html
@@ -0,0 +1,97 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#installed_plugins" class="toc">Installed plugins</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#hilited" class="toc">hilited</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#xterm" class="toc">xterm</a></span></div></li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="installed_plugins" id="installed_plugins">Installed plugins</a></h1>
+<div class="level1">
+
+<p>
+The following plugins have been installed, to give the gEDA Project Wiki additional functionality.
+</p>
+
+</div>
+<!-- SECTION "Installed plugins" [1-132] -->
+<h2><a name="hilited" id="hilited">hilited</a></h2>
+<div class="level2">
+
+<p>
+The â??hilitedâ?? plugin acts as a yellow highlighter. Surround the text you want to highlight with double-exclamation marks.
+</p>
+
+<p>
+Example:<br/>
+
+</p>
+<pre class="code">Sample text !!highlighted!! in a paragraph.</pre>
+
+<p>
+becomes:<br/>
+ Sample text <span class="hilited">highlighted</span> in a paragraph.
+</p>
+
+</div>
+<!-- SECTION "hilited" [133-400] -->
+<h2><a name="xterm" id="xterm">xterm</a></h2>
+<div class="level2">
+
+<p>
+The â??xtermâ?? plugin allows you to embed preformatted text.<br/>
+ The <code><</code>xterm<code>><</code>/xterm<code>></code> tags surround the text you wish to embed.<br/>
+ The <code><</code>xterm<code>><</code>/xterm<code>></code> tags differ from the built-in <code><</code>code<code>><</code>/code<code>></code> tags as follows:
+</p>
+<ul>
+<li class="level1"><div class="li"> The text is indented.</div>
+</li>
+<li class="level1"><div class="li"> You can emphasize parts of the text.</div>
+</li>
+<li class="level1"><div class="li"> The text will have a lightgreen background, so it will stand out on the wiki-page.</div>
+</li>
+</ul>
+
+<p>
+ Example:<br/>
+ The following is indented from the current sectionâ??s left margin: <pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">embedded <strong>preformatted</strong> words</font></pre>
+</p>
+
+<p>
+The following shows how the preformatted text will follow the <acronym title="Extensible HyperText Markup Language">XHTML</acronym> indent levels:
+</p>
+<ul>
+<li class="level1"><div class="li"> Test line 1.</div>
+</li>
+<li class="level1"><div class="li"> Test line 2.<br/>
+ <pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">Indented test line 3.</font></pre></div>
+</li>
+<li class="level1"><div class="li"> Test line 4.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "xterm" [401-] --></body>
+</html>
diff --git a/docs/wiki/geda-kig_howto.html b/docs/wiki/geda-kig_howto.html
new file mode 100644
index 0000000..b857166
--- /dev/null
+++ b/docs/wiki/geda-kig_howto.html
@@ -0,0 +1,320 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#how_to_setup_keymapping_in_gschem" class="toc">How To Setup Keymapping In gschem</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#about_this_document" class="toc">About this document</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#functionality" class="toc">Functionality</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#keymaps" class="toc">Keymaps</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#an_example_on_keymaps" class="toc">An example on keymaps</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#description_of_keys" class="toc">Description of keys</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#actions" class="toc">Actions</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#function_calls" class="toc">Function calls</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#another_keymap" class="toc">Another keymap</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#where_are_the_key_mappings_stored" class="toc">Where are the key mappings stored</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#appendix_a_--_dictionary" class="toc">Appendix A -- Dictionary</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#appendix_b_--_built-in_actions_in_gschem" class="toc">Appendix B -- Built-in actions in gschem</a></span></div></li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="how_to_setup_keymapping_in_gschem" id="how_to_setup_keymapping_in_gschem">How To Setup Keymapping In gschem</a></h1>
+<div class="level1">
+
+<p>
+by: Stefan Petersen, spe@xxxxxxxxxxxxx This document is released under <a href="http://www.fsf.org/copyleft/gpl.html"; class="urlextern" title="http://www.fsf.org/copyleft/gpl.html"; rel="nofollow">GPL</a>
+</p>
+
+<p>
+1999-07-24
+</p>
+
+</div>
+<!-- SECTION "How To Setup Keymapping In gschem" [1-177] -->
+<h2><a name="about_this_document" id="about_this_document">About this document</a></h2>
+<div class="level2">
+
+<p>
+The purpose of this document is to try to explain how key mapping works in gEDA/gschem schematic entry program. It uses the langauge Scheme a lot, which is a Lisp-dialect and is used in gschem as a scripting language. If youâ??re not familiar with this language, please see the dictionary (see appendix A, page X, for a short description of common data structures used in Scheme.
+</p>
+
+</div>
+<!-- SECTION "About this document" [178-588] -->
+<h2><a name="functionality" id="functionality">Functionality</a></h2>
+<div class="level2">
+
+<p>
+When you press a button in gschem, a Scheme function is called. This function (press-key) accepts one argument, the name of the pressed key. Then there are Scheme routines to evaluate which key you pressed and call the appropriate action.<br/>
+ Since the evaluation routines are written in Scheme itâ??s simple to change the behaviour of what happens when you presses a key. You can implement macros or do several things at each key press. For example, the â??repeat-last-keyâ?? command is implemented completly in Scheme.
+</p>
+
+</div>
+<!-- SECTION "Functionality" [589-1128] -->
+<h2><a name="keymaps" id="keymaps">Keymaps</a></h2>
+<div class="level2">
+
+<p>
+The current implementation is built-up around â??keymapsâ??. A keymap is a list with pairs. Each pairs first element (the car-element) is which key to react on, and the second element (cdr) is a â??what-to-do-nextâ??. This can either be an action, a function to call or another keymap.
+</p>
+
+</div>
+<!-- SECTION "Keymaps" [1129-1427] -->
+<h3><a name="an_example_on_keymaps" id="an_example_on_keymaps">An example on keymaps</a></h3>
+<div class="level3">
+
+<p>
+Two simple examples of keymaps are seen in Figure 1 and Figure 2.
+</p>
+<pre class="code">(define global-keymap
+ '(("Escape" . cancel)
+ ("a" . add-keymap)))</pre>
+
+<p>
+Figure 1: First example of an simple keymap
+</p>
+
+<p>
+In figure 1 is the keymap called global-keymap. This keymap is the first keymap used. If you for example press the â??aâ??-key, global-keymap tells us that next key pressed will be interpreted by add-keymap (see figure 2).
+</p>
+<pre class="code">(define add-keymap
+ '(("c" . add-component)
+ ("a" . add-attribute)
+ ("n" . add-net-hotkey)))</pre>
+
+<p>
+Figure 2: Second example of an simple keymap
+</p>
+
+<p>
+If you, after you pressed â??aâ??, press a â??câ?? the built-in action add-component comes to live. This is exactly what had happend if you had selected Add, Component…in the menubar.<br/>
+ When an action has been performed the current keymap is reset back to global-keymap.<br/>
+ Available built-in actions are listed in appendix B.
+</p>
+
+</div>
+<!-- SECTION "An example on keymaps" [1428-2357] -->
+<h3><a name="description_of_keys" id="description_of_keys">Description of keys</a></h3>
+<div class="level3">
+
+<p>
+The key are described as:
+</p>
+<table class="inline">
+ <tr>
+ <td> For a </td><td> â??aâ?? </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> For Shift-A </td><td> â??Shift Aâ?? </td>
+ </tr>
+ <tr>
+ <td> For Control-a </td><td> â??Control aâ?? </td>
+ </tr>
+ <tr>
+ <td> For Alt-a </td><td> â??Alt aâ?? </td>
+ </tr>
+</table>
+
+<p>
+ There are a few simple rules to follow when keys for a new keymap is defined:
+</p>
+<ul>
+<li class="level1"><div class="li"> Everything is case sensitive</div>
+</li>
+<li class="level1"><div class="li"> At this point in time you can only have one modifier (shift, control, alt) at a time.</div>
+</li>
+<li class="level1"><div class="li"> Keys must be unique in each keymap, especially the global one</div>
+</li>
+<li class="level1"><div class="li"> Strings (without any modifers) are the same strings specified for the keys in the file /usr/lib/X11/XKeysymDB (at least on a linux box) </div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Description of keys" [2358-2925] -->
+<h3><a name="actions" id="actions">Actions</a></h3>
+<div class="level3">
+
+<p>
+The built-in actions that can be called are listed in Appendix B.<br/>
+ Sometimes you may notice that there are similar actions, like edit-rotate-90 and edit-rotate-90-hotkey. They do the same thing, just that the -hotkey actions is run immediately, while the other wait for you to select something.
+</p>
+
+</div>
+<!-- SECTION "Actions" [2926-3240] -->
+<h3><a name="function_calls" id="function_calls">Function calls</a></h3>
+<div class="level3">
+
+<p>
+If the cdr-element is an ordinary Scheme function that function is called. The function canâ??t receive any arguments.<br/>
+ This can be used if you want to do complex tasks, like several actions in a row or do some calculation. You can do rather advanced actions since the Guile dialect of Scheme used in gschem is extended from plain Scheme. For further information on Guile, please see the Guile documentation.
+</p>
+
+</div>
+<!-- SECTION "Function calls" [3241-3674] -->
+<h3><a name="another_keymap" id="another_keymap">Another keymap</a></h3>
+<div class="level3">
+
+<p>
+If the cdr-element is another keymap then that command is a multi-key command, ie you need to press at least two keys to cause an action. The first key is desribed in the first keymap, which points to the next keymap. The second keymap describes what should happen when the second key is pressed.
+</p>
+
+</div>
+<!-- SECTION "Another keymap" [3675-3997] -->
+<h2><a name="where_are_the_key_mappings_stored" id="where_are_the_key_mappings_stored">Where are the key mappings stored</a></h2>
+<div class="level2">
+
+<p>
+The keymap is stored in the startup file for gschem, namely <code><startpath, typically /usr/local>/share/gEDA/system-gschemrc</code>.<br/>
+ You can then redefine or add keymaps as you like (I think) in your local setup file for gschem, ~/.gEDA/gschemrc
+</p>
+
+<p>
+The Scheme functions used to resolve keypresses to actions are stored at <code><startpath, typically /usr/local>/share/gEDA/scheme/gschem.scm</code>. This is configurable in the gschemrc files.
+</p>
+
+</div>
+<!-- SECTION "Where are the key mappings stored" [3998-4471] -->
+<h3><a name="appendix_a_--_dictionary" id="appendix_a_--_dictionary">Appendix A -- Dictionary</a></h3>
+<div class="level3">
+<table class="inline">
+ <tr>
+ <td> <strong>function</strong> </td><td>A subprogram in Scheme, C or other programming languages. </td>
+ </tr>
+ <tr>
+ <td><strong>action</strong> </td><td>What gschem (in this case) does when you press a key or a set of keys. </td>
+ </tr>
+ <tr>
+ <td><strong>list</strong> </td><td>A data structure very common in Lisp-looking languages like Scheme. Simply put, a long list of values. </td>
+ </tr>
+ <tr>
+ <td><strong>pair</strong> </td><td>(also dotted pair) A datstructure also very common in Lisp-looking languages. </td>
+ </tr>
+ <tr>
+ <td><strong>car element</strong> </td><td>First element in a pair. Since lists are decendents from pairs, car is also the first element in a list. </td>
+ </tr>
+ <tr>
+ <td><strong>cdr element</strong> </td><td>(pronounced cudr) The second element in a pair. In the list case it denotes the rest of list. </td>
+ </tr>
+</table>
+
+</div>
+<!-- SECTION "Appendix A -- Dictionary" [4472-5116] -->
+<h2><a name="appendix_b_--_built-in_actions_in_gschem" id="appendix_b_--_built-in_actions_in_gschem">Appendix B -- Built-in actions in gschem</a></h2>
+<div class="level2">
+
+<p>
+Run: <pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">grep gh_register_procedure_0_0 gschem/src/g_register.c</font></pre>
+</p>
+
+<p>
+and do some work in emacsen.
+</p>
+
+<p>
+<pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">file-new-window
+file-new
+file-open
+file-script
+file-save
+file-save-as
+file-save-all
+file-print
+file-image
+file-close-window
+file-quit
+edit-select
+edit-copy
+edit-copy-hotkey
+edit-move
+edit-move-hotkey
+edit-delete
+edit-rotate-90
+edit-rotate-90-hotkey
+edit-mirror
+edit-mirror-hotkey
+edit-slot
+edit-color
+edit-edit
+edit-lock
+edit-unlock
+edit-translate
+edit-embed
+edit-unembed
+edit-hidden
+view-redraw
+view-zoom-full
+view-zoom-limits
+view-zoom-in
+view-zoom-out
+view-zoom-box
+view-zoom-box-hotkey
+view-pan
+view-pan-hotkey
+view-update-nets
+page-manager
+page-next
+page-prev
+page-new
+page-close
+page-discard
+page-print
+add-component
+add-attribute
+add-net
+add-net-hotkey
+add-text
+add-line
+add-line-hotkey
+add-box
+add-box-hotkey
+add-circle
+add-circle-hotkey
+add-arc
+add-arc-hotkey
+add-pin
+add-pin-hotkey
+hierarchy-open-symbol
+attributes-attach
+attributes-detach
+attributes-show-name
+attributes-show-value
+attributes-show-both
+attributes-visibility-toggle
+options-text-size
+options-snap-size
+options-action-feedback
+options-grid
+options-snap
+options-show-log-window
+options-show-coord-window
+misc-misc
+cancel</font></pre>
+</p>
+
+</div>
+<!-- SECTION "Appendix B -- Built-in actions in gschem" [5117-] --></body>
+</html>
diff --git a/docs/wiki/geda-master_attributes_list.html b/docs/wiki/geda-master_attributes_list.html
new file mode 100644
index 0000000..7287213
--- /dev/null
+++ b/docs/wiki/geda-master_attributes_list.html
@@ -0,0 +1,583 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#geda_gaf_master_attribute_document" class="toc">gEDA/gaf Master Attribute Document</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#overview" class="toc">Overview</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#what_are_attributes" class="toc">What are Attributes?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#symbol_only_attributes" class="toc">Symbol only Attributes</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#device" class="toc">device</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#graphical" class="toc">graphical</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#description" class="toc">description</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#author" class="toc">author</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#comment" class="toc">comment</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#pinseq" class="toc">pinseq</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#pinnumber" class="toc">pinnumber</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#pintype" class="toc">pintype</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#pinlabel" class="toc">pinlabel</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#numslots" class="toc">numslots</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#slotdef" class="toc">slotdef</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#footprint" class="toc">footprint</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#documentation" class="toc">documentation</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#schematic_only_attributes" class="toc">Schematic only Attributes</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#netname" class="toc">netname</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#source" class="toc">source</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#symbol_and_schematic_attributes" class="toc">Symbol and Schematic Attributes</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#refdes" class="toc">refdes</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#slot" class="toc">slot</a></span></div></li>
+<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>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#uref" class="toc">uref</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#name" class="toc">name</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#label" class="toc">label</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#pin" class="toc">pin#</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#slot1" class="toc">slot#</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#type" class="toc">type</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#email" class="toc">email</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#document_revision_history" class="toc">Document Revision History</a></span></div></li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="geda_gaf_master_attribute_document" id="geda_gaf_master_attribute_document">gEDA/gaf Master Attribute Document</a></h1>
+<div class="level1">
+
+<p>
+by: Ales Hvezda, ahvezda@xxxxxxxxxxxxx
+</p>
+
+<p>
+This document is released under <a href="http://www.gnu.org/copyleft/fdl.html"; class="urlextern" title="http://www.gnu.org/copyleft/fdl.html"; rel="nofollow">GFDL</a>
+</p>
+
+<p>
+July 10th, 2007
+</p>
+
+</div>
+<!-- SECTION "gEDA/gaf Master Attribute Document" [1-185] -->
+<h2><a name="overview" id="overview">Overview</a></h2>
+<div class="level2">
+
+<p>
+This document describes all the attributes used in in gEDA/gaf (<acronym title="GNU General Public License">GPL</acronym>â??d Electronic Design Automation / Gschem And Friends). This document is broken down into several section: this overview, symbol only attributes, schematic only attributes, attributes which can appear in both symbols and schematics, and attributes which are obsolete or deprecated.<br/>
+ In this document, attribute names are in <strong>bold</strong> and examples are in the <code>typewriter</code> font.
+</p>
+
+</div>
+<!-- SECTION "Overview" [186-652] -->
+<h2><a name="what_are_attributes" id="what_are_attributes">What are Attributes?</a></h2>
+<div class="level2">
+
+<p>
+Attributes in the gEDA/gaf system are nothing more than text items which take on the form: <strong>name</strong>=value. Name can be anything just as long as it doesnâ??t contain a equals sign. Value can also be anything just as long as it is something (vs nothing). <strong>name</strong>= (without a value part) is not a valid attribute. Also, there cannot be any spaces immediately before or after the equals sign.<br/>
+ Attributes can be attached to some part of the symbol. If the attribute conveys information specific to an object, then the attribute should be attached directly to the object, otherwise the attribute should be free standing or floating. Free standing attributes just exist in the symbol file as text items which take on the form <strong>name</strong>=value.
+</p>
+
+</div>
+<!-- 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" [1424-1459] -->
+<h3><a name="device" id="device">device</a></h3>
+<div class="level3">
+
+<p>
+<strong>device</strong>= is the device name of the symbol and is required by gnetlist.<br/>
+ <strong>device</strong>= should be placed somewhere in the symbol and made invisible. This is a free standing or floating attribute. If the object is a graphic then <strong>device</strong>= should be set to none (<strong>device</strong>=none) and attach a <a href="#graphical" title=":geda:master_attributes_list.txt ↵" class="wikilink1">graphical</a>= attribute. Do not confuse this attribute with just having a text label which the device name. Do not put spaces into the device name; there are some programs which dislike spaces in the device specifier. Generally the device name is in all caps.<br/>
+ Examples: <code>device=7400 device=CONNECTOR 10 device=NPN TRANSISTOR</code>
+</p>
+
+</div>
+<!-- SECTION "device" [1460-2103] -->
+<h3><a name="graphical" id="graphical">graphical</a></h3>
+<div class="level3">
+
+<p>
+Symbols which have no electrical or circuit significance need a <strong>graphical</strong>=1 attribute. Symbols like titleboxes are purely graphical symbols. Any symbol which has <strong>graphical</strong>=1 is ignored by gnetlist.<br/>
+ <strong>graphical</strong>=1 should exist somewhere in the symbol and made invisible. This is a free standing or floating attribute. Donâ??t forget to set <a href="#device" title=":geda:master_attributes_list.txt ↵" class="wikilink1">device</a>=none.<br/>
+ Example: <code>graphical=1</code>
+</p>
+
+</div>
+<!-- SECTION "graphical" [2104-2518] -->
+<h3><a name="description" id="description">description</a></h3>
+<div class="level3">
+
+<p>
+The <strong>description</strong> attribute provides a simple one line description of what the symbol is supposed to represent.<br/>
+ Example: <code>description=4 NAND gates with 2 inputs</code>
+</p>
+
+</div>
+<!-- SECTION "description" [2519-2709] -->
+<h3><a name="author" id="author">author</a></h3>
+<div class="level3">
+
+<p>
+The <strong>author</strong> attribute identifies the name of the author of this symbol and their e-mail address. This attribute is optional, but it is nice to know who created which symbols. It also serves the purpose of known who to contact if there are questions about the intent(s) of the symbol. This attribute is free form and it can also include peopleâ??s names who modified the symbol as well as multiple e-mail addresses. It is probably also a good idea to obfuscate the e-mail address so it is not harvested for spam purposes.<br/>
+ Example: <code>author=Ales Hvezda ahvezdaATgeda.seul.org</code>
+</p>
+
+</div>
+<!-- SECTION "author" [2710-3306] -->
+<h3><a name="comment" id="comment">comment</a></h3>
+<div class="level3">
+
+<p>
+The <code>comment</code> attribute can contain anything. This attribute can convey any additional information which might not fit into any other attribute. There can be multiple instances of this attribute.<br/>
+ Example: <code>comment=This is a comment inside a symbol</code>
+</p>
+
+</div>
+<!-- SECTION "comment" [3307-3580] -->
+<h3><a name="pinseq" id="pinseq">pinseq</a></h3>
+<div class="level3">
+
+<p>
+This attribute is used to give each pin an unique number or sequence. All pins must have a <strong>pinseq</strong>=# attribute attached to the pin object. This attribute should be hidden. This attribute is used extensively by gschem and gnetlist.<br/>
+ In some backends (especially the SPICE backend), gnetlist will output pins in the order of increasing pin sequence. The sequence numbers start at 1 and should increase without skipping any numbers. This attribute is not the pin number (i.e. device pin numbers, like GND is 7 on TTL). For pin numbers see the <a href="#pinnumber" title=":geda:master_attributes_list.txt ↵" class="wikilink1">pinnumber</a> attribute.<br/>
+ Examples: <code>pinseq=1 pinseq=2 pinseq=3</code><br/>
+
+</p>
+
+<p>
+This attribute replaces the obsolete <strong>pin#</strong>=# attribute.
+</p>
+
+</div>
+<!-- SECTION "pinseq" [3581-4273] -->
+<h3><a name="pinnumber" id="pinnumber">pinnumber</a></h3>
+<div class="level3">
+
+<p>
+This attribute is the pin number (i.e. like GND is 7 on 74 TTL). All pins must have a <strong>pinnumber</strong>=# attribute attached to the pin object.<br/>
+ You can have numbers or letters for the value. This attribute should be visible with the value only visible. You also need a <a href="#pinseq" title=":geda:master_attributes_list.txt ↵" class="wikilink1">pinseq</a> attribute.<br/>
+ Examples: <code>pinnumber=1 pinnumber=13 pinnumber=A0</code><br/>
+
+</p>
+
+<p>
+This attribute replaces the obsolete pin#=# attribute.
+</p>
+
+</div>
+<!-- SECTION "pinnumber" [4274-4696] -->
+<h3><a name="pintype" id="pintype">pintype</a></h3>
+<div class="level3">
+
+<p>
+Each pin must have a <strong>pintype</strong>=value attribute attached to it and should be make hidden. Table 1 shows valid values for this attribute.<br/>
+ This attribute is not used extensively in the symbol library, but it will be used for DRC and netlisting.<br/>
+ Examples: <code>pintype=clk pintype=in pintype=pas</code><br/>
+
+</p>
+<table class="inline">
+ <tr>
+ <td>in</td><td>Input</td>
+ </tr>
+ <tr>
+ <td>out</td><td>Output</td>
+ </tr>
+ <tr>
+ <td>io</td><td>Input/Output</td>
+ </tr>
+ <tr>
+ <td>oc</td><td>Open collector</td>
+ </tr>
+ <tr>
+ <td>oe</td><td>Open emitter</td>
+ </tr>
+ <tr>
+ <td>pas</td><td>Passive</td>
+ </tr>
+ <tr>
+ <td>tp</td><td>Totem pole</td>
+ </tr>
+ <tr>
+ <td>tri</td><td>Tristate (high impedance)</td>
+ </tr>
+ <tr>
+ <td>clk</td><td>Clock</td>
+ </tr>
+ <tr>
+ <td>pwr</td><td>Power/Ground</td>
+ </tr>
+ <tr>
+ <td colspan="2">Table 1: pintype values</td>
+ </tr>
+</table>
+
+</div>
+<!-- SECTION "pintype" [4697-5215] -->
+<h3><a name="pinlabel" id="pinlabel">pinlabel</a></h3>
+<div class="level3">
+
+<p>
+This attribute labels a pin object. This attribute is primarily used by gnetlist to support hierarchical designs.<br/>
+ This attribute must be attached to the pin and be left visible. Please make this attribute green (instead of the default attribute yellow).<br/>
+ Examples: <code>pinlabel=A0 pinlabel=DATA1 pinlabel=CLK</code><br/>
+
+</p>
+
+</div>
+<!-- SECTION "pinlabel" [5216-5549] -->
+<h3><a name="numslots" id="numslots">numslots</a></h3>
+<div class="level3">
+
+<p>
+If a component has multiple slots in a physical package (such as a 7400 (NAND) which has 4 NANDs per package) then you need a <strong>numslots</strong>=# attribute. The # is the number of slots that are in a physical device. <strong>numslots</strong>=# should exist somewhere in the symbol and be made invisible. This is a free standing or floating attribute. If the symbol does not need slotting, then put <strong>numslots</strong>=0 into the symbol file.<br/>
+ Example: <code>numslots=4</code>
+</p>
+
+</div>
+<!-- SECTION "numslots" [5550-6013] -->
+<h3><a name="slotdef" id="slotdef">slotdef</a></h3>
+<div class="level3">
+
+<p>
+If a component has multiple slots in a physical package then you must attach a <strong>slotdef</strong>=slotnumber:#,#,#… for every device inside the physical package.<br/>
+ The slotnumber corresponds to the slot number. The colon after the slot number is required. For example, if a device has 4 slots then there would be <strong>slotdef</strong>=1:…, <strong>slotdef</strong>=2:…, <strong>slotdef</strong>=3:…, and slotdef=4:… attributes somewhere in the symbol and be made invisible. This is a free standing or floating attribute.<br/>
+ The #â??s have a one-to-one correspondence to the <strong>pinseq</strong> attributes and specify which <strong>pinnumber</strong>=# is used during display (gschem) or netlisting (gnetlist).<br/>
+ It is recommended that all symbols which have slots have a <a href="#slot" title=":geda:master_attributes_list.txt ↵" class="wikilink1">slot</a>=1 attribute attached in the same fashion as the <a href="#device" title=":geda:master_attributes_list.txt ↵" class="wikilink1">device</a>= attribute.<br/>
+ See 7400-1.sym as a concrete example.<br/>
+ Examples: <code>slotdef=1:1,2,3 slotdef=2:4,5,6 slotdef=3:7,8,9</code><br/>
+ This attribute replaces the obsolete <strong>slot</strong>#=# attribute.
+</p>
+
+</div>
+<!-- SECTION "slotdef" [6014-6994] -->
+<h3><a name="footprint" id="footprint">footprint</a></h3>
+<div class="level3">
+
+<p>
+<strong>footprint</strong>=package name should exist somewhere in the symbol and be made invisible. This attribute is used by gnetlist and primarily for the PCB package.<br/>
+ Attach this attribute just like the <a href="#device" title=":geda:master_attributes_list.txt ↵" class="wikilink1">device</a>= attribute. This is a free standing or floating attribute.<br/>
+ package name is the pcb footprint or package type like DIP14 or DIP40. Although this attribute in principle is pcb package dependent, gEDA/gaf conventions exist to make this attribute as portable as possible, allowing for easy collaboration and sharing between users. See the <a href="geda-scg.html#footprint_naming_conventions" class="wikilink1" title="geda-scg.html">Footprint naming conventions in the Symbol Creation Guide</a>.<br/>
+ If the symbol does not have a footprint, then the value of <strong>footprint</strong>= should be set to none. If the footprint must be overridden in a schematic, then the value of <strong>footprint</strong>= should be set to none. If the footprint is not known, then the value of footprint= should be set to unknown.
+</p>
+
+</div>
+<!-- SECTION "footprint" [6995-7953] -->
+<h3><a name="documentation" id="documentation">documentation</a></h3>
+<div class="level3">
+
+<p>
+<strong>documentation</strong>=documentation_locator may exist somewhere in the symbol and be made invisible. This attribute is used by gschemdoc to find relevant documentation for the symbol, or rather, the device or component associated with the symbol.<br/>
+ Attach this attribute just like the <a href="#device" title=":geda:master_attributes_list.txt ↵" class="wikilink1">device</a>= attribute. This is a freestanding or floating attribute.<br/>
+ documentation_locator is either the base filename of the documentation, or it is the complete Internet <acronym title="Uniform Resource Locator">URL</acronym> (Uniform Resource Locator). If it is the filename, an attempt will be made to search for it in the local gEDA share directory named <strong>documentation</strong>.<br/>
+ Filename example: <code>documentation=sn74ls00.pdf</code><br/>
+ <acronym title="Uniform Resource Locator">URL</acronym> example: <code>documentation=<a href="http://www-s.ti.com/sc/ds/sn74ls00.pdf"; class="urlextern" title="http://www-s.ti.com/sc/ds/sn74ls00.pdf"; rel="nofollow">http://www-s.ti.com/sc/ds/sn74ls00.pdf</a></code>
+</p>
+
+</div>
+<!-- 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" [8713-8750] -->
+<h3><a name="netname" id="netname">netname</a></h3>
+<div class="level3">
+
+<p>
+This attribute should be attached to a net object to give it a name. Multiple net names for connected net segments is discouraged. All nets which have the same value are considered electrically connected. This attribute is not valid inside symbols (as you cannot have nets inside of symbols).<br/>
+ Examples: <code>netname=DATA0 H netname=CLK L</code><br/>
+
+</p>
+
+</div>
+<!-- SECTION "netname" [8751-9110] -->
+<h3><a name="source" id="source">source</a></h3>
+<div class="level3">
+
+<p>
+The source= attribute is used to specify that a symbol has underlying schematics. This attribute is attached directly to a component.<br/>
+ This attribute should only be attached to instantiated components in schematics. Attach the attribute to a component and specify the filename (not the path) of the underlying schematic (like block.sch) for the value. The specified schematic must be in a source-library path. This attribute can be attached multiple times with difierent values which basically means that there are multiple underlying schematics.<br/>
+ Examples: <code>source=underlying.sch source=memory.sch</code>
+</p>
+
+</div>
+<!-- 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" [9733-9777] -->
+<h3><a name="refdes" id="refdes">refdes</a></h3>
+<div class="level3">
+
+<p>
+This attribute is used to specify the reference designator to a particular instantiated component. It must be on ALL components which have some sort of electrical significance. This attribute can also be on the inside of a symbol (it will be promoted, i.e. attached to the outside of the symbol, if it is visible) to provide a default refdes value (such as U?). Usually this attribute is composed by a prefix (â??Uâ?? for example) and a number (different for each component).<br/>
+ Examples: <code>refdes=U1 refdes=R10 refdes=CONN1</code><br/>
+ There is a convention of the reference designator used for each kind of component. Here are some of them (substitute a cardinal value for <n>):
+</p>
+<table class="inline">
+ <tr>
+ <th> Prefix </th><th> Component type</th>
+ </tr>
+ <tr>
+ <td class="leftalign"> R<n> </td><td>Resistor</td>
+ </tr>
+ <tr>
+ <td class="leftalign"> RN<n> </td><td>Resistor Network</td>
+ </tr>
+ <tr>
+ <td class="leftalign"> FB<n> </td><td>Ferrite Bead</td>
+ </tr>
+ <tr>
+ <td class="leftalign"> L<n> </td><td>Inductor</td>
+ </tr>
+ <tr>
+ <td class="leftalign"> C<n> </td><td>Capacitor</td>
+ </tr>
+ <tr>
+ <td class="leftalign"> B<n> </td><td>Battery </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> F<n> </td><td class="leftalign">Fuse </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> J<n> </td><td>Connector</td>
+ </tr>
+ <tr>
+ <td class="leftalign"> P<n> </td><td>Connector (usually plugs that mate with J<n>)</td>
+ </tr>
+ <tr>
+ <td class="leftalign"> K<n> </td><td>Relay</td>
+ </tr>
+ <tr>
+ <td class="leftalign"> S<n> </td><td>Switch</td>
+ </tr>
+ <tr>
+ <td class="leftalign"> T<n> </td><td>Transformer</td>
+ </tr>
+ <tr>
+ <td class="leftalign"> TP<n> </td><td>Testpoint</td>
+ </tr>
+ <tr>
+ <td class="leftalign"> M<n> </td><td>Motor</td>
+ </tr>
+ <tr>
+ <td class="leftalign"> D<n> </td><td>Diode</td>
+ </tr>
+ <tr>
+ <td class="leftalign"> Q<n> </td><td>Transistor</td>
+ </tr>
+ <tr>
+ <td class="leftalign"> U<n> </td><td>IC</td>
+ </tr>
+ <tr>
+ <td class="leftalign"> X<n> </td><td>Crystal</td>
+ </tr>
+</table>
+
+</div>
+<!-- SECTION "refdes" [9778-10889] -->
+<h3><a name="slot" id="slot">slot</a></h3>
+<div class="level3">
+
+<p>
+This attribute is used to specify a slot for a slotted component. It should be attached to an instantiated component. This attribute can also be on the inside of a symbol (it will be promoted, i.e. attached to the outside of the symbol, if it is visible) to provide a default slot.
+</p>
+
+</div>
+<!-- SECTION "slot" [10890-11187] -->
+<h3><a name="net" id="net">net</a></h3>
+<div class="level3">
+
+<p>
+The <strong>net</strong>= attribute is used to create power/ground and arbitrary nets. Please see the <a href="geda-na_howto.html" class="wikilink1" title="geda-na_howto.html">net= attribute mini-HOWTO</a> for more info. When this attribute is inside a symbol, it is used to create nets. When this attribute is attached to an instantiated component (in a schematic), then the <strong>net</strong>= can also be used to create new nets and can used to override existing nets.
+</p>
+
+</div>
+<!-- SECTION "net" [11188-11591] -->
+<h3><a name="value" id="value">value</a></h3>
+<div class="level3">
+
+<p>
+Used mainly in the spice backend netlister to specify the value of the various elements. No translation is done on this, and it is placed as is into the netlist.<br/>
+ Examples: <code>value=1K value=10V</code><br/>
+
+</p>
+
+</div>
+<!-- SECTION "value" [11592-11807] -->
+<h3><a name="symversion" id="symversion">symversion</a></h3>
+<div class="level3">
+
+<p>
+The <strong>symversion</strong>= attribute is used to version the contents of symbols. Normally this attribute is not present, but once a symbol has been accepted into the main gEDA symbol library and there are changes to it, this attribute must be placed into the symbol file and properly incremented. The value of this attribute takes the following form:<br/>
+ <strong>major.minor</strong>
+</p>
+
+<p>
+where major and minor are just plain integers (separated by a period). The major number is incremented when a symbol has some sort of a change which will break or might break an existing schematic. The minor number is only incremented when a cosmetic or very minor change is made to the symbol. The major and minor numbers are not coupled in any way, however, when making major version changes, the minor version number can be reset to zero.<br/>
+ If this attribute is inside of a symbol and that symbol is placed onto a schematic, then the <strong>symversion</strong>= attribute will be automatically promoted and attached to the outside of the symbol. During the load of the symbol from disk, the value of the <strong>symversion</strong>= inside the symbol file (if any) and the <strong>symversion</strong>= attached to the symbol (if any) are compared. If the values are the same then the placed symbol matches the disk symbol file, however if the values do not match, then libgeda will output a warning/error message (based on whether it is a major or minor version change).<br/>
+ New symbols should not receive this attribute at all. Only when the symbol is change should this attribute be placed into the symbol file and maintained. Users should not attach this attribute manually to instantiated symbols. This attribute should normally be made invisible when placed inside of a symbol file. This attribute is always promoted when it is found inside of a symbol (during component placement).<br/>
+ Examples: <code>symversion=1.1</code><br/>
+
+</p>
+
+</div>
+<!-- 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="images/smileys/fixme.gif" align="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" [14458-14489] -->
+<h3><a name="uref" id="uref">uref</a></h3>
+<div class="level3">
+
+<p>
+The uref= attribute is obsolete and cannot not be used. It was used to provide the same information as <a href="#refdes" title=":geda:master_attributes_list.txt ↵" class="wikilink1">refdes</a>.
+</p>
+
+</div>
+<!-- SECTION "uref" [14490-14621] -->
+<h3><a name="name" id="name">name</a></h3>
+<div class="level3">
+
+<p>
+The <strong>name</strong>= attribute should not be attached or appear in any symbol. It is considered ambiguous. <strong>name</strong>= was never used by gEDA/gaf.
+</p>
+
+</div>
+<!-- SECTION "name" [14622-14775] -->
+<h3><a name="label" id="label">label</a></h3>
+<div class="level3">
+
+<p>
+The <strong>label</strong>= attribute is obsolete and cannot be used. It was used to give nets names/labels and to label pins. The replacement attributes for this are <a href="#netname" title=":geda:master_attributes_list.txt ↵" class="wikilink1">netname</a> and <a href="#pinlabel" title=":geda:master_attributes_list.txt ↵" class="wikilink1">pinlabel</a> respectively.
+</p>
+
+</div>
+<!-- SECTION "label" [14776-14991] -->
+<h3><a name="pin" id="pin">pin#</a></h3>
+<div class="level3">
+
+<p>
+The <strong>pin#</strong>=# attribute is obsolete and cannot be used. It was used to provide sequence and number information to pins. The replacement attributes for this are <a href="#pinseq" title=":geda:master_attributes_list.txt ↵" class="wikilink1">pinseq</a> and <a href="#pinnumber" title=":geda:master_attributes_list.txt ↵" class="wikilink1">pinnumber</a>.
+</p>
+
+</div>
+<!-- SECTION "pin#" [14992-15200] -->
+<h3><a name="slot1" id="slot1">slot#</a></h3>
+<div class="level3">
+
+<p>
+The <strong>slot#</strong>=# attribute is obsolete and cannot be used. It was used to provide slotting information to components. The replacement attribute for this is <a href="#slotdef" title=":geda:master_attributes_list.txt ↵" class="wikilink1">slotdef</a>.
+</p>
+
+</div>
+<!-- SECTION "slot#" [15201-15386] -->
+<h3><a name="type" id="type">type</a></h3>
+<div class="level3">
+
+<p>
+The <strong>type</strong>= attribute is obsolete and cannot be used. It was used to provide type information on pins. The replacement attribute for this is <a href="#pintype" title=":geda:master_attributes_list.txt ↵" class="wikilink1">pintype</a>.
+</p>
+
+</div>
+<!-- SECTION "type" [15387-15559] -->
+<h3><a name="email" id="email">email</a></h3>
+<div class="level3">
+
+<p>
+The information in this attribute has been merged with <a href="#author" title=":geda:master_attributes_list.txt ↵" class="wikilink1">author</a>.
+</p>
+
+</div>
+<!-- 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">
+ <tr>
+ <td>July 14th, 2002</td><td>Created attributes.tex from attributes.txt.</td>
+ </tr>
+ <tr>
+ <td>July 14th, 2002</td><td>Updated doc to be in sync with post-20020527.</td>
+ </tr>
+ <tr>
+ <td>August 25th, 2002</td><td>Added obsolete type= attribute.</td>
+ </tr>
+ <tr>
+ <td>September 14, 2002</td><td>Added description= attribute. Minor xes</td>
+ </tr>
+ <tr>
+ <td>October 7, 2002</td><td>Added doc= attribute; Egil Kvaleberg.</td>
+ </tr>
+ <tr>
+ <td>February 11, 2003</td><td>Added reference to footprint conventions.</td>
+ </tr>
+ <tr>
+ <td>February 23, 2003</td><td>Added author=, email=, and comment= attributes.</td>
+ </tr>
+ <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" [15645-] --></body>
+</html>
diff --git a/docs/wiki/geda-mcalc_readme.html b/docs/wiki/geda-mcalc_readme.html
new file mode 100644
index 0000000..ba58606
--- /dev/null
+++ b/docs/wiki/geda-mcalc_readme.html
@@ -0,0 +1,51 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="mcalc_readme" id="mcalc_readme">mcalc README</a></h1>
+<div class="level1">
+<pre class="code">$Id: README,v 1.1 2001/08/16 11:19:01 dan Exp $
+
+WHAT IS IT?
+------------
+
+mstrip is a JavaScript based microstrip analysis/synthesis calculator.
+It is designed to be easy to use and fairly accurate. The accuracy is
+generally within a percent or so for the characteristic impedance which
+greatly exceeds the simplified formulations found in most text books.
+
+
+HOW DO I INSTALL IT?
+--------------------
+
+To install this package, simply copy all the files in the archive to the
+installation directory.
+
+To use this pacakge, just point your JavaScript capable web broswer at
+the file 'index.html'.
+
+
+CAN I COPY IT?
+--------------
+Please refer to the file 'copying.html' for copyright information.
+
+
+IS THERE A HISTORY FILE?
+------------------------
+Please refer to the file 'verinfo.html' for version history.</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-na_howto.html b/docs/wiki/geda-na_howto.html
new file mode 100644
index 0000000..3328309
--- /dev/null
+++ b/docs/wiki/geda-na_howto.html
@@ -0,0 +1,237 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#net_attribute_mini-howto" class="toc">net= attribute mini-HOWTO</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#what_is_the_net_attribute_used_for" class="toc">What is the net= attribute used for?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#what_is_the_format_of_the_net_attribute" class="toc">What is the format of the net= attribute?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_do_you_actually_use_the_net_attribute" class="toc">How do you actually use the net= attribute?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#caveats_bugs" class="toc">Caveats / Bugs</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#example" class="toc">Example</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#final_notes" class="toc">Final notes</a></span></div></li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="net_attribute_mini-howto" id="net_attribute_mini-howto">net= attribute mini-HOWTO</a></h1>
+<div class="level1">
+
+<p>
+by: Ales Hvezda
+</p>
+
+<p>
+This document is released under <a href="http://www.gnu.org/copyleft/fdl.html"; class="urlextern" title="http://www.gnu.org/copyleft/fdl.html"; rel="nofollow">GFDL</a>
+</p>
+
+<p>
+October 2nd, 2003
+</p>
+
+<p>
+The information in this document is current as of 19991011.
+</p>
+
+</div>
+<!-- SECTION "net= attribute mini-HOWTO" [1-216] -->
+<h2><a name="what_is_the_net_attribute_used_for" id="what_is_the_net_attribute_used_for">What is the net= attribute used for?</a></h2>
+<div class="level2">
+
+<p>
+The <strong><code>net=</code></strong> attribute is used to specify power, ground, and/or arbitrary nets in the gEDA system.<br/>
+ The <strong><code>net=</code></strong> attribute is used instead some of the other systems of specifying power/ground (such as having power/ground pins on symbols or power boxes). Some devices have lots of power/ground pins and having all of these pins on the symbol would increase its size and make it unmanageable. The <strong><code>net=</code></strong> attribute is the power/ground specification of choice in the gEDA system because of its simplicity and versatility. Now having said all this, you can have power/ground pins on a symbol, but gnetlist will probably not recognize these nets connected to these pins as separate power/ground nets. Please keep this in mind as you draw symbols.
+</p>
+
+</div>
+<!-- SECTION "What is the net= attribute used for?" [217-1022] -->
+<h2><a name="what_is_the_format_of_the_net_attribute" id="what_is_the_format_of_the_net_attribute">What is the format of the net= attribute?</a></h2>
+<div class="level2">
+
+<p>
+Attributes in gEDA are simple text items which are in the form <code>name=value</code>. All proper attributes follow this form. Attribute names are always lower case, but the value can be upper or lower case. gnetlist and friends are case sensitive. Typically net/signal names by default are upper case.<br/>
+ Attribute can be attached to an object or in certain cases (like the <strong><code>net=</code></strong> attribute) can be free oating (not attached to anything). The free floating attributes are also called toplevel attributes.<br/>
+ The <strong><code>net=</code></strong> attribute is a text item which takes on the following form:
+</p>
+<pre class="code">net=signalname:pinname,pinname,pinname,...</pre>
+
+<p>
+where:
+</p>
+<table class="inline">
+ <tr>
+ <td> <strong><code>net=</code></strong> </td><td> The attribute name (always the same, lowercase) </td>
+ </tr>
+ <tr>
+ <td> signalname </td><td> The signal or net being defines (like +5V, GND, etc…) </td>
+ </tr>
+ <tr>
+ <td> pinname </td><td> The pin name (or number) which is assigned to this signal/net (or pin names/numbers) </td>
+ </tr>
+</table>
+
+<p>
+ The signalname cannot contain the ":" character (since it is a delimiter). The pinname is the pin name (A1, P2, D1, etc…) or pin number (1, 2, 5, 13, etc…). The pinname cannot contain the "," character (since it is also a delimiter). pinnames are typically the same sort of numbers/names like the <code>pin#=#</code> attribute (if you are familiar with that attribute).<br/>
+ You can only have ONE signalname per <strong><code>net=</code></strong> attribute, but you can have as many pinnames/numbers as you want.
+</p>
+
+</div>
+<!-- SECTION "What is the format of the net= attribute?" [1023-2446] -->
+<h2><a name="how_do_you_actually_use_the_net_attribute" id="how_do_you_actually_use_the_net_attribute">How do you actually use the net= attribute?</a></h2>
+<div class="level2">
+
+<p>
+You can place the <strong><code>net=</code></strong> attribute in several places. Hereâ??s the list so far:
+</p>
+<ul>
+<li class="level1"><div class="li"> Inside a symbol either as an attached attribute or an unattached attribute (toplevel attribute). Example which creates power/gnd nets: <strong><code>net=GND:7</code></strong> or <strong><code>net=+5V:14</code></strong></div>
+</li>
+<li class="level1"><div class="li"> Outside a symbol (which is instantiated on a schematic) attached as an attribute to override an existing <strong><code>net=</code></strong> created net/signal. Suppose a symbol has a <strong><code>net=GND:7</code></strong> inside it already; attaching this to the symbol: <strong><code>net=AGND:7</code></strong> overrides the GND net (on pin 7) calling it AGND and connects/associates it to pin 7.</div>
+</li>
+<li class="level1"><div class="li"> Outside or inside a symbol to connect a net to a visible pin automatically. This is still untested and still might have some undesirable (negative) side effects. Use with caution.</div>
+</li>
+<li class="level1"><div class="li"> Attached to one of those special power/gnd symbol (like vcc/gnd/vdd) and you can change what that symbol represents. You could change the ground symbol to create a net called DIGITAL GND without editing the symbol (<strong><code>net=DIGITAL_GND:1</code></strong>).<br/>
+ In the current symbol (19991011) library there are symbols named <strong>vdd-1.sym</strong>, <strong>vcc-1.sym</strong>, <strong>vee-1.sym</strong>, etc… which do not have a <strong><code>net=</code></strong> attribute inside, so you must attach the <strong><code>net=</code></strong> attribute yourself (in the schematic).<br/>
+ There also symbols named 5V-minus-1.sym, 12V-plus-1.sym, 9V-plus-1.sym, etc… which have the appropriate <strong><code>net=</code></strong> attribute in them already (can be overridden though). You can use these symbol as examples of how to use the <strong><code>net=</code></strong> attribute.<br/>
+</div>
+</li>
+</ul>
+
+<p>
+You can have as many <strong><code>net=</code></strong> attributes as you want. Just remember that <strong><code>net=</code></strong> attributes attached to the outside of a symbol override any equivalent internal (inside the symbol) <strong><code>net=</code></strong> attributes. If you run into a case where this doesnâ??t work, please let <strong>ahvezdaATgeda.seul.org</strong>. In fact, send any bug reports to that individual.
+</p>
+
+</div>
+<!-- SECTION "How do you actually use the net= attribute?" [2447-4387] -->
+<h2><a name="caveats_bugs" id="caveats_bugs">Caveats / Bugs</a></h2>
+<div class="level2">
+
+<p>
+The <strong><code>net=</code></strong> attribute/mechanism is fairly new, so there are bound to be bugs (many bugs). Here are some of the identified issues:
+</p>
+<ul>
+<li class="level1"><div class="li"> As of 19991011 almost all of the symbols in the standard library do not have the <strong><code>net=</code></strong> attribute or any other power/ground specifiers. Hopefully this will be updated sometime (any volunteers?).</div>
+</li>
+<li class="level1"><div class="li"> Attach a special power symbol (vcc/gnd) to a already named net will alias (rename) that net to the signalname specified in the <strong><code>net=</code></strong> attribute (in/attached to the vcc/gnd symbol). You can override this (so the reverse is true) by playing with the â??net-naming-priorityâ??. Be careful with this. There might be other â??aliasingâ?? issues which have not been identified yet.</div>
+</li>
+<li class="level1"><div class="li"> Creating a <strong><code>net=</code></strong> attribute which associates a signal name with a pin which is already visible on the symbol, is probably a bad idea. This does work, but all the ramifications have not been explored yet.</div>
+</li>
+<li class="level1"><div class="li"> It is probably a bad idea to have the same <strong><code>net=</code></strong> attribute attached several times. Ales has not formalized what happens in this case. Just remember that the <strong><code>net=</code></strong> attribute on the outside of a symbol should override the internal one.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Caveats / Bugs" [4388-5599] -->
+<h2><a name="example" id="example">Example</a></h2>
+<div class="level2">
+
+<p>
+Hereâ??s a schematic which uses standard symbols (note: the 7400 does not have the <strong><code>net=</code></strong> attribute inside yet). This schematic consists of a 7400 with the <strong><code>net=</code></strong> attributes attached for power and ground, One of the input pins grounded using a gnd symbol and the other at a logic one using the vcc symbol (with an attached <strong><code>net=</code></strong> attribute). One of the input net is named, but as you will see, the netname is replaced by the <strong><code>net=</code></strong> signal name (see above for more info on this). The output is pulled up with a pull up resistor which has power specified using the +5V symbol.<br/>
+
+</p>
+<table class="inline">
+ <tr>
+ <td> <a href="media/geda/net.jpg" class="media" target="_blank" title="geda:net.jpg"><img src="media/geda/net.jpg" class="media" alt="" /></a> </td>
+ </tr>
+</table>
+<pre class="code">v 19991011
+C 38700 58100 1 0 0 7400-1.sym
+{
+T 39000 59000 5 10 1 1 0
+uref=U100
+T 38900 59500 5 10 1 1 0
+net=GND:7
+T 38900 59300 5 10 1 1 0
+net=+5V:14
+}
+N 38700 58800 37400 58800 4
+{
+T 37600 58900 5 10 1 1 0
+netname=NETLABEL
+}
+N 37400 58800 37400 59200 4
+N 38700 58400 37400 58400 4
+N 37400 58000 37400 58400 4
+C 37300 57700 1 0 0 gnd-1.sym
+C 37200 59200 1 0 0 vcc-1.sym
+{
+T 36800 59200 5 10 1 1 0
+net=+5V:1
+}
+N 40000 58600 41600 58600 4
+{
+T 41200 58700 5 10 1 1 0
+netname=OUTPUT
+}
+C 40700 58800 1 90 0 resistor-1.sym
+{
+T 40800 59200 5 10 1 1 0
+uref=R1
+}
+N 40600 58800 40600 58600 4
+N 40600 59900 40600 59700 4
+C 40400 59900 1 0 0 5V-plus-1.sym</pre>
+
+<p>
+<strong>gnetlist</strong> (using the geda netlist format) run using this sample schematic outputs this:
+</p>
+<pre class="code">START header
+
+gEDA's netlist format
+Created specifically for testing of gnetlist
+
+END header
+
+START components
+
+R1 device=RESISTOR
+U100 device=7400
+
+END components
+
+START renamed-nets
+
+NETLABEL -> +5V
+
+END renamed-nets
+
+START nets
+
++5V : R1 2, U100 14, U100 1
+GND : U100 7, U100 2
+OUTPUT : R1 1, U100 3
+
+END nets</pre>
+
+<p>
+Notice how NETLABEL was renamed (aliased to the +5V net).
+</p>
+
+</div>
+<!-- SECTION "Example" [5600-7377] -->
+<h2><a name="final_notes" id="final_notes">Final notes</a></h2>
+<div class="level2">
+
+<p>
+Send all bugs to <strong>ahvezdaATgeda.seul.org</strong> or <strong>geda-devATgeda.seul.org</strong> (mailing list, please subscribe first). [Iâ??m sure thereâ??s more to say here]
+</p>
+
+</div>
+<!-- SECTION "Final notes" [7378-] --></body>
+</html>
diff --git a/docs/wiki/geda-ngnutmeg_mp.html b/docs/wiki/geda-ngnutmeg_mp.html
new file mode 100644
index 0000000..93cec8c
--- /dev/null
+++ b/docs/wiki/geda-ngnutmeg_mp.html
@@ -0,0 +1,912 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="ngnutmeg_man-page" id="ngnutmeg_man-page">ngnutmeg man-page</a></h1>
+<div class="level1">
+<pre class="code">NUTMEG(1) NUTMEG(1)
+
+
+
+NAME
+ nutmeg - spice post-processor
+
+SYNOPSIS
+ nutmeg [ - ] [ -n ] [ -t term ] [ datafile ... ]
+
+DESCRIPTION
+ Nutmeg is a post processor for SPICE - it takes the raw output file
+ created by spice -r and plots the data on a graphics terminal or a
+ workstation display. Note that the raw output file is different from
+ the data that SPICE writes to the standard output.
+
+ Arguments are:
+
+ - Don�t try to load the default data file ("rawspice") if no other
+ files are given.
+
+ -n (or --no-spiceinit)
+ Don�t try to source the file ".spiceinit" upon startup. Normally
+ nutmeg tries to find the file in the current directory, and if
+ it is not found then in the user�s home directory.
+
+ -t term (or --term=term)
+ The program is being run on a terminal with mfb name term.
+
+ -h (or --help)
+ Display a verbose help on the arguments available to the pro-
+ gram.
+
+ -v (or --version)
+ Display a version number and copyright information of the pro-
+ gram.
+
+ Further arguments are taken to be data files in binary or ascii format
+ (see sconvert(1)) which are loaded into nutmeg. If the file is in
+ binary format, it may be only partially completed (useful for examining
+ SPICE ouput before the simulation is finished). One file may contain
+ any number of data sets from different analyses.
+
+ Nutmeg data is in the form of vectors: time, voltage, etc. Each vector
+ has a type, and vectors can be operated on and combined algebraicly in
+ ways consistent with their types. Vectors are normally created when a
+ data file is read in (see the load command below), and when the initial
+ datafile is loaded. They can also be created with the let command.
+
+ An expression is an algebraic formula involving vectors and scalars (a
+ scalar is a vector of length 1), and the following operations:
+
+ +, -, *, %, /, ^, and ,.
+
+ % is the modulo operator, and the comma operator has two meanings: if
+ it is present in the argument list of a user-definable function, it
+ serves to seperate the arguments. Otherwise, the term x , y is synony-
+ mous with x + j(y).
+
+ Also available are the logical operations & (and), | (or), ! (not), and
+ the relational operations <, >, >=, <=, =, and <> (not equal). If used
+ in an algebraic expression they work like they would in C, producing
+ values of 0 or 1. The relational operators have the following syn-
+ onyms: "gt" is >, "lt" is <, "ge" is >=, "le" is <=, "ne" is <>, "eq"
+ is =, "and" is &, "or" is |, and "not" is !. These are useful when <
+ and > might be confused with IO redirection (which is almost always).
+
+ The following functions are available:
+
+ mag(vector) - The magnitude of vector.
+
+ ph(vector) - The phase of vector.
+
+ j(vector) - i (sqrt(-1)) times vector.
+
+ real(vector) - The real component of vector.
+
+ imag(vector) - The imaginary part of vector.
+
+ db(vector) - 20 * log10(mag(vector)).
+
+ log(vector) - The logarithm (base 10) of the vector.
+
+ ln(vector) - The natural logarithm (base e) of vector.
+
+ exp(vector) - e to the vector power.
+
+ abs(vector) - The absolute value of vector.
+
+ sqrt(vector) - The square root of vector.
+
+ sin(vector) - The sin of vector.
+
+ cos(vector) - The cosine of vector.
+
+ tan(vector) - The tangent of vector.
+
+ atan(vector) - The inverse tangent of vector.
+
+ norm(vector) - The vector normalized to 1 (i.e, the largest mag-
+ nitude of any component will be 1).
+
+ rnd(vector) - A vector with each component a random integer
+ between 0 and the absolute value of the vectors�s corresponding
+ component.
+
+ mean(vector) - The result is a scalar (a length 1 vector) that
+ is the mean of the elements of vector.
+
+ vector(number) - The result is a vector of length number, with
+ elements 0, 1, ... number - 1. If number is a vector then just
+ the first element is taken, and if it isn�t an integer then the
+ floor of the magnitude is used.
+
+ length(vector) - The length of vector.
+
+ interpolate(plot.vector) - The result of interpolating the named
+ vector onto the scale of the current plot. This function uses
+ the variable polydegree to determine the degree of interpola-
+ tion.
+
+ A vector may be either the name of a vector already defined, a float-
+ ing- point number (a scalar), or a list like [elt1 elt2 ... eltn],
+ which is a vector of length n. A number may be written in any format
+ acceptable to SPICE, such as 14.6MEG or -1.231E-4. Note that you can
+ either use scientific notation or one of the abbreviations like MEG or
+ G, but not both. As with SPICE, a number may have trailing alphabetic
+ characters after it.
+
+ The notation expr [lower upper], where lower and upper are numbers,
+ denotes the range of elements from expr between lower and upper. The
+ notation expr [num] denotes the num�th element of expr. If upper is
+ lower than lower, the order of the elements in the vector is reversed.
+ In all other cases, [ and ] serve to surround literal vectors as
+ described above. (You may have to use a lot of parentheses to make
+ sure that you get what you want. For instance, you have to type print
+ (foo) ([1 2]) to print the two vectors. Otherwise it will be inter-
+ preted as a function call or a vector with an index.) Note that the
+ expression foo[10 20][5] will not yield the 15th element of foo, but
+ rather the 5th. In general only the last index suffix on an expression
+ will take effect.
+
+ To reference vectors in a plot that is not the current plot (see the
+ setplot command, below), the notation plotname.vecname can be used.
+
+ Either a plotname or a vector name may be the wildcard all. If the
+ plotname is all, matching vectors from all plots are specified, and if
+ the vector name is all, all vectors in the specified plots are refer-
+ enced. Note that you may not use binary operations on expressions
+ involving wildcards - it is not obvious what all + all should denote,
+ for instance.
+
+ Thus some (contrived) examples of expressions are:
+
+ cos(TIME) + db(v(3))
+
+ sin(cos(log([1 2 3 4 5 6 7 8 9 10])))
+
+ TIME * rnd(v(9)) - 15 * cos(vin#branch) ^ [7.9e5 8]
+
+ not ((ac3.FREQ[32] & tran1.TIME[10]) gt 3)
+
+ Nutmeg commands are as follows:
+
+ plot exprs [ylimit ylo yhi] [xlimit xlo xhi] [xindices xilo xihi]
+ [xcompress comp] [xdelta xdel] [ydelta ydel] [xlog] [ylog] [vs xname]
+ [xlabel word] [ylabel word] [title word] [samep]
+ Plot the given exprs on the screen (if you are on a graphics
+ terminal). The xlimit and ylimit arguments determine the high
+ and low x- and y-limits of the axes, respectively. The xindices
+ arguments determine what range of points are to be plotted -
+ everything between the xilo�th point and the xihi�th point is
+ plotted. The xcompress argument specifies that only one out of
+ every comp points should be plotted. If an xdelta or a ydelta
+ parameter is present, it specifies the spacing between grid
+ lines on the X- and Y-axis. These parameter names may be abbre-
+ viated to xl, yl, xind, xcomp, xdel, and ydel respectively. The
+ xname argument is an expression to use as the scale on the x-
+ axis. If xlog or ylog are present, the X or Y scale respec-
+ tively will be logarithmic. The xlabel and ylabel arguments
+ cause the specified labels to be used for the X and Y axes,
+ respectively. If samep is given, the values of the other param-
+ eters (other than xname) from the previous plot, hardcopy, or
+ asciiplot command will be used unless re-defined on the command
+ line. Finally, the title argument will be used in the place of
+ the plot name at the bottom of the graph.
+
+ hardcopy file plotargs
+ Just like plot, except creates a file called file containing the
+ plot. The file is an image in plot(5) format, and can be
+ printed by either the plot(1) program or lpr with the -g flag.
+
+ asciiplot plotargs
+ Produce a line printer plot of the vectors. The plot is sent to
+ the standard output, so you can put it into a file with asci-
+ iplot args ... > file. The set options width, height, and
+ nobreak determine the width and height of the plot, and whether
+ there are page breaks, respectively. Note that you will have
+ problems if you try to asciiplot something with an X-scale that
+ isn�t monotonic (i.e, something like sin(TIME) ), because asci-
+ iplot uses a simple-minded sort of linear interpolation.
+
+ define function(arg1, arg2, ...) expression
+ Define the user-definable function with the name function and
+ arguments arg1, arg2, ... to be expression, which may involve
+ the arguments. When the function is later used, the arguments it
+ is given are substituted for the formal arguments when it is
+ parsed. If expression is not present, any definition for func-
+ tion is printed, and if there are no arguments to define then
+ all currently active definitions are printed. Note that you may
+ have different functions defined with the same name but differ-
+ ent arities. Some useful definitions are:
+
+ define max(x,y) (x > y) * x + (x <= y) * y
+ define min(x,y) (x < y) * x + (x >= y) * y
+
+ undefine function ...
+ Definitions for the named user-defined functions are deleted.
+
+ let name = expr
+ Creates a new vector called name with the value specified by
+ expr, an expression as described above. If expr is [] (a zero-
+ length vector) then the vector becomes undefined. If there are
+ no arguments, let is the same as display.
+
+ print [col] [line] expr ...
+ Prints the vector described by the expression expr. If the col
+ argument is present, print the vectors named side by side. If
+ line is given, the vectors are printed horizontally. col is the
+ default, unless all the vectors named have a length of one, in
+ which case line is the default. The options width, length, and
+ nobreak are effective for this command (see asciiplot). If the
+ expression is all, all of the vectors available are printed.
+ Thus print col all > file will print everything in the file in
+ SPICE2 format. The scale vector (time, frequency) will always
+ be in the first column unless the variable noprintscale is true.
+
+ load [filename] ...
+ Loads the raw data in either binary or ascii format from the
+ files named. The default filename is rawspice, or the argument
+ to the -r flag if there was one.
+
+ source filename
+ Reads commands from the file filename. Lines beginning with the
+ character * are considered comments and ignored.
+
+ help [all] [command ...]
+ Prints help. If the argument all is given, a short description
+ of everything you could possibly type is printed. If commands
+ are given, descriptions of those commands are printed. Other-
+ wise help for only a few major commands is printed.
+
+ display [varname ...]
+ Prints a summary of currently defined vectors, or of the names
+ specified. The vectors are sorted by name unless the variable
+ nosort is set. The information given is the name of the vector,
+ the length, the type of the vector, and whether it is real or
+ complex data. Additionally, one vector will be labeled [scale].
+ When a command such as plot is given without a vs argument, this
+ scale is used for the X-axis. It is always the first vector in a
+ rawfile, or the first vector defined in a new plot. If you unde-
+ fine the scale (i.e, let TIME = []), a random remaining vector
+ will become the scale.
+
+ setplot [plotname]
+ Set the current plot to the plot with the given name, or if no
+ name is given, prompt the user with a menu. (Note that the
+ plots are named as they are loaded, with names like tran1 or
+ op2. These names are shown by the setplot and display commands
+ and are used by diff, below.) If the "New plot" item is
+ selected, the current plot will become one with no vectors
+ defined. Note that here the word "plot" refers to a group of
+ vectors that are the result of one SPICE run. When more than
+ one file is loaded in, or more than one plot is present in one
+ file, nutmeg keeps them seperate and only shows you the vectors
+ in the current plot.
+
+ settype type vector ...
+ Change the type of the named vectors to type. Type names can be
+ found in the manual page for sconvert.
+
+ diff plot1 plot2 [vec ...]
+ Compare all the vectors in the specified plots, or only the
+ named vectors if any are given. There are different vectors in
+ the two plots, or any values in the vectors differ significantly
+ the difference is reported. The variables abstol, reltol, and
+ vntol are used to determine what "significantly" means (see the
+ SPICE3 User�s Manual).
+
+ quit Quit nutmeg.
+
+ bug Send a bug report. (If you have defined BUGADDR, the mail will
+ go there.)
+
+ write [file] [exprs]
+ Writes out the expr�s to file. First vectors are grouped
+ together by plots, and written out as such. (I.e, if the
+ expression list contained three vectors from one plot and two
+ from another, then two plots will be written, one with three
+ vectors and one with two.) Additionally, if the scale for a
+ vector isn�t present, it is automatically written out as well.
+ The default format is ascii, but this can be changed with the
+ set filetype command. The default filename is rawspice, or the
+ argument to the -r flag on the command line, if there was one,
+ and the default expression list is all.
+
+ shell [args ...]
+ Fork a shell, or execute the arguments as a command to the
+ shell.
+
+ alias [word] [text ...]
+ Causes word to be aliased to text. History substitutions may be
+ used, as in C-shell aliases.
+
+ unalias [word ...]
+ Removes any aliases present for the words.
+
+ history [number]
+ Print out the history, or the last number commands typed at the
+ keyboard. Note: in version 3a7 and earlier, all commands
+ (including ones read from files) were saved.
+
+ set [word] [word = value] ...
+ Set the value of word to be value, if it is present. You can
+ set any word to be any value, numeric or string. If no value is
+ given then the value is the boolean �true�. The value of word
+ may be inserted into a command by writing $word. If a variable
+ is set to a list of values that are enclosed in parentheses
+ (which must be seperated from their values by white space), the
+ value of the variable is the list. The variables meaningful to
+ nutmeg (of which there are too many) are:
+
+ abstol
+ The absolute tolerance used by the diff command.
+
+ appendwrite
+ Append to the file when a write command is issued, if
+ one already exists.
+
+ colorN
+ These variables determine the colors used, if X is
+ being run on a color display. N may be between 0 and
+ 15. Color 0 is the background, color 1 is the grid and
+ text color, and colors 2 through 15 are used in order
+ for vectors plotted. The value of the color variables
+ should be names of colors, which may be found in the
+ file /usr/lib/rgb.txt.
+
+ combplot
+ Plot vectors by drawing a vertical line from each point
+ to the X-axis, as opposed to joining the points. Note
+ that this option is subsumed in the plottype option,
+ below.
+
+ cpdebug
+ Print cshpar debugging information. (Must be complied
+ with the -DCPDEBUG flag.)
+
+ debug
+ If set then a lot of debugging information is printed.
+ (Must be compiled with the -DFTEDEBUG flag.)
+
+ device
+ The name (/dev/tty??) of the graphics device. If this
+ variable isn�t set then the user�s terminal is used. To
+ do plotting on another monitor you will probably have
+ to set both the device and term variables. (If device
+ is set to the name of a file, nutmeg will dump the
+ graphics control codes into this file -- this is useful
+ for saving plots.)
+
+ echo
+ Print out each command before it is executed.
+
+ filetype
+ This can be either ascii or binary, and determines what
+ the format of rawfiles will be. The default is ascii.
+
+ fourgridsize
+ How many points to use for interpolating into when
+ doing fourier analysis.
+
+ gridsize
+ If this variable is set to an integer, this number will
+ be used as the number of equally spaced points to use
+ for the Y-axis when plotting. Otherwise the current
+ scale will be used (which may not have equally spaced
+ points). If the current scale isn�t strictly mono-
+ tonic, then this option will have no effect.
+
+ hcopydev
+ If this is set, when the hardcopy command is run the
+ resulting file is automatically printed on the printer
+ named hcopydev with the command lpr -Phcopydev -g file.
+
+ hcopydevtype
+ This variable specifies the type of the printer output
+ to use in the hardcopy command. If hcopydevtype is not
+ set, plot (5) format is assumed. The standard distri-
+ bution currently recognizes postscript as an alterna-
+ tive output format. When used in conjunction with
+ hcopydev, hcopydevtype should specify a format sup-
+ ported by the printer.
+
+ height
+ The length of the page for asciiplot and print col.
+
+ history
+ The number of events to save in the history list.
+
+ nfreqs
+ The number of frequencies to compute in the fourier
+ command. (Defaults to 10.)
+
+ nobreak
+ Don�t have asciiplot and print col break between pages.
+
+ noasciiplotvalue
+ Don�t print the first vector plotted to the left when
+ doing an asciiplot.
+
+ noclobber
+ Don�t overwrite existing files when doing IO redirec-
+ tion.
+
+ noglob
+ Donââ?¬â?¢t expand the global characters ââ?¬Ë?*ââ?¬â?¢, ââ?¬Ë??ââ?¬â?¢, ââ?¬Ë?[ââ?¬â?¢, and
+ ââ?¬Ë?]ââ?¬â?¢. This is the default.
+
+ nogrid
+ Don�t plot a grid when graphing curves (but do label
+ the axes).
+
+ nomoremode
+ If nomoremode is not set, whenever a large amount of
+ data is being printed to the screen (e.g, the print or
+ asciiplot commands), the output will be stopped every
+ screenful and will continue when a carriage return is
+ typed. If nomoremode is set then data will scroll off
+ the screen without hesitation.
+
+ nonomatch
+ If noglob is unset and a global expression cannot be
+ matched, use the global characters literally instead of
+ complaining.
+
+ nosort
+ Don�t have display sort the variable names.
+
+ noprintscale
+ Don�t print the scale in the leftmost column when a
+ print col command is given.
+
+ numdgt
+ The number of digits to print when printing tables of
+ data (fourier, print col). The default precision is 6
+ digits. On the VAX, approximately 16 decimal digits
+ are available using double precision, so numdgt should
+ not be more than 16. If the number is negative, one
+ fewer digit is printed to ensure constant widths in
+ tables.
+
+ plottype
+ This should be one of normal, comb, or point:chars.
+ normal, the default, causes points to be plotted as
+ parts of connected lines. comb causes a comb plot to
+ be done (see the description of the combplot variable
+ above). point causes each point to be plotted seper-
+ ately - the chars are a list of characters that will be
+ used for each vector plotted. If they are omitted then
+ a default set is used.
+
+ polydegree
+ The degree of the polynomial that the plot command
+ should fit to the data. If polydegree is N, then nutmeg
+ will fit a degree N polynomial to every set of N points
+ and draw 10 intermediate points in between each end-
+ point. If the points aren�t monotonic, then it will try
+ rotating the curve and reducing the degree until a fit
+ is achieved.
+
+ polysteps
+ The number of points to interpolate between every pair
+ of points available when doing curve fitting. The
+ default is 10. (This should really be done automati-
+ cally.)
+
+ program
+ The name of the current program (argv[0]).
+
+ prompt
+ The prompt, with the character ââ?¬Ë?!ââ?¬â?¢ replaced by the cur-
+ rent event number.
+
+ rawfile
+ The default name for rawfiles created.
+
+ reltol
+ The relative tolerance used by the diff command.
+
+ rhost
+ The machine to use for remote SPICE-3 runs, instead of
+ the default one. (See the description of the rspice
+ command, below.)
+
+ rprogram
+ The name of the remote program to use in the rspice
+ command.
+
+ slowplot
+ Stop between each graph plotted and wait for the user
+ to type return before continuing.
+
+ sourcepath
+ A list of the directories to search when a source com-
+ mand is given. The default is the current directory
+ and the standard spice library (/usr/local/lib/spice,
+ or whatever LIBPATH is #defined to in the source.
+
+ spicepath
+ The program to use for the aspice command. The default
+ is /cad/bin/spice.
+
+ term
+ The mfb name of the current terminal.
+
+ units
+ If this is degrees, then all the trig functions will
+ use degrees instead of radians.
+
+ unixcom
+ If a command isn�t defined, try to execute it as a UNIX
+ command. Setting this option has the effect of giving
+ a rehash command, below. This is useful for people who
+ want to use nutmeg as a login shell.
+
+ verbose
+ Be verbose. This is midway between echo and debug /
+ cpdebug.
+
+ vntol
+ The absolute voltage tolerance used by the diff com-
+ mand.
+
+ width
+ The width of the page for asciiplot and print col.
+
+ xbrushheight
+ The height of the brush to use if X is being run.
+
+ xbrushwidth
+ The width of the brush to use if X is being run.
+
+ xfont
+ The name of the X font to use when plotting data and
+ entering labels. The plot may not look entirely great
+ if this is a variable-width font.
+
+
+ unset [word] ...
+ Unset the variables word.
+
+ shift [varname] [number]
+ If varname is the name of a list variable, it is shifted to the
+ left by number elements. (I.e, the number leftmost elements are
+ removed.) The default varname is argv, and the default number
+ is 1.
+
+ rusage [resource ...]
+ Print resource usage statistics. If any resources are given,
+ just print the usage of that resource. Currently valid
+ resources are:
+
+ elapsed
+ The amount of time elapsed since the last rusage elaped
+ call.
+
+ faults
+ Number of page faults and context switches (BSD only).
+
+ space
+ Data space used.
+
+ time
+ CPU time used so far.
+
+ everything
+ All of the above.
+
+ cd [directory] Change the current working directory to directory, or
+ to the user�s home directory if none is given.
+
+ aspice [output-file]
+ Start a SPICE-3 run, and when it is finished load the
+ data. The raw data is kept in a temporary file. If out-
+ put-file is specified then the diagnostic output is
+ directed into that file, otherwise it is thrown away.
+
+ jobs Report on the asynchronous SPICE-3 jobs currently run-
+ ning. Nutmeg checks to see if the jobs are finished
+ every time you execute a command. If it is done then
+ the data is loaded and becomes available.
+
+ rspice [input file]
+ Runs a SPICE-3 remotely taking the input file as a
+ SPICE-3 input deck, or the current circuit if no argu-
+ ment is given. Nutmeg waits for the job to complete,
+ and passes output from the remote job to the user�s
+ standard output. When the job is finished the data is
+ loaded in as with aspice. If the variable rhost is set,
+ nutmeg will connect to this host instead of the default
+ remote SPICE-3 server machine. Note that this command
+ will only work if your system administrator is running
+ a SPICE-3 daemon on the remote host. If the variable
+ rprogram is set, then rspice will use this as the path-
+ name to the program to run.
+
+ echo [stuff...] Echos the arguments.
+
+ fourier fundamental_frequency [value ...]
+ Does a fourier analysis of each of the given values,
+ using the first 10 multiples of the fundamental fre-
+ quency (or the first nfreqs, if that variable is set -
+ see below). The output is like that of the .four card.
+ The values may be any valid expression. The values are
+ interpolated onto a fixed-space grid with the number of
+ points given by the fourgridsize variable, or 200 if it
+ is not set. The interpolation will be of degree poly-
+ degree if that variable is set, or 1. If polydegree is
+ 0, then no interpolation will be done. This is likely
+ to give erroneous results if the time scale is not
+ monotonic, though.
+
+ version [version id]
+ Print out the version of nutmeg that is running. If
+ there are arguments, it checks to make sure that the
+ arguments match the current version of SPICE. (This is
+ mainly used as a Command: line in rawfiles.)
+
+ rehash Recalculate the internal hash tables used when looking
+ up UNIX commands, and make all UNIX commands in the
+ user�s PATH available for command completion. This is
+ useless unless you have set unixcom first (see above).
+
+ The following control structures are available:
+
+ while condition
+ statement
+ ...
+ end
+
+ While condition, an arbitrary algebraic expression, is true, execute
+ the statements.
+
+ repeat [number]
+ statement
+ ...
+ end
+
+ Execute the statements number times, or forever if no argument is
+ given.
+
+ dowhile condition
+ statement
+ ...
+ end
+
+ The same as while, except that the condition is tested after the
+ statements are executed.
+
+ foreach var value ...
+ statement
+ ...
+ end
+
+ The statements are executed once for each of the values, each time with
+ the variable var set to the current one. (var can be accessed by the
+ $var notation - see below).
+
+ if condition
+ statement
+ ...
+ else
+ statement
+ ...
+ end
+
+ If the condition is non-zero then the first set of statements are exe-
+ cuted, otherwise the second set. The else and the second set of state-
+ ments may be omitted.
+
+ label word
+
+ If a statement of the form goto word is encountered, control is trans-
+ fered to this point, otherwise this is a no-op.
+
+ goto word
+
+ If a statement of the form label word is present in the block or an
+ enclosing block, control is transfered there. Note that if the label
+ is at the top level, it must be before the goto statement (i.e, a for-
+ ward goto may occur only within a block).
+
+ continue
+
+ If there is a while, dowhile, or foreach block enclosing this state-
+ ment, control passes to the test, or in the case of foreach, the next
+ value is taken. Otherwise an error results.
+
+ break
+
+ If there is a while, dowhile, or foreach block enclosing this state-
+ ment, control passes out of the block. Otherwise an error results.
+
+ Of course, control structures may be nested. When a block is entered
+ and the input is the terminal, the prompt becomes a number of >�s
+ equalling the number of blocks the user has entered. The current con-
+ trol structures may be examined with the debugging command cdump.
+
+ If a word is typed as a command, and there is no built-in command with
+ that name, the directories in the sourcepath list are searched in order
+ for the file. If it is found, it is read in as a command file (as if
+ it were sourced). Before it is read, however, the variables argc and
+ argv are set to the number of words following the filename on the com-
+ mand line, and a list of those words respectively. After the file is
+ finished, these variables are unset. Note that if a command file calls
+ another, it must save its argv and argc since they will get altered.
+ Also, command files may not be re-entrant since there are no local
+ variables. (Of course, the procedures may explicitly manipulate a
+ stack...) This way one can write scripts analogous to shell scripts
+ for nutmeg and . Note that for the script to work with , it must begin
+ with a blank line (or whatever you like, since it will be thrown away)
+ and then a line with .control on it. This is an unfortunate result of
+ the source command being used for both circuit input and command file
+ execution. Note also that this allows the user to merely type the name
+ of a circuit file as a command, and it will be automatically run.
+
+ There are various command scripts installed in
+ /usr/local/lib/spice/scripts (or whatever the path is on your machine),
+ and the default sourcepath includes this directory, so you can use
+ these command files (almost) like builtin commands.
+
+ Nutmeg will use either X or MFB, depending on whether it finds the
+ variable DISPLAY in the environment. If you are using X on a worksta-
+ tion, it should already be present, but if you want to display graphics
+ on a different machine than the one you are running nutmeg on, DISPLAY
+ should be of the form machine:0.
+
+ If X is being used, the cursor may be positioned at any point on the
+ screen when the window is up and characters typed at the keyboard will
+ be added to the window at that point. The window may then be sent to a
+ printer using the xpr(1) program.
+
+ There are a number of pre-defined constants in nutmeg. They are:
+ pi pi
+ e The base of natural logarithms
+ c The speed of light
+ i The square root of -1
+ kelvin Absolute 0 in Centigrade
+ echarge The charge on an electron
+ boltz Boltzman�s constant
+ planck Planck�s constant (h)
+
+
+ These are all in MKS units. If you have another variable with a name
+ that conflicts with one of these then it takes precedence.
+
+ Nutmeg occasionally checks to see if it is getting close to running out
+ of space, and warns the user if this is the case. (This is more likely
+ to be useful with the SPICE front end.)
+
+ C-shell type quoting with "" and ��, and backquote substitution may be
+ used. Within single quotes, no further substitution (like history sub-
+ stitution) is done, and within double quotes, the words are kept
+ together but further substitution is done. Any text between backquotes
+ is replaced by the result of executing the text as a command to the
+ shell.
+
+ Tenex-style (�set filec� in the 4.3 C-shell) command, filename, and
+ keyword completion is possible: If EOF (control-D) is typed after the
+ first character on the line, a list of the commands or possible argu-
+ ments is printed. (If it is alone on the line it will exit nutmeg.) If
+ escape is typed, then nutmeg will try to complete what the user has
+ already typed. To get a list of all commands, the user should type
+ <space> ^D.
+
+ The values of variables may be used in commands by writing $varname
+ where the value of the variable is to appear. The special variables $$
+ and $< refer to the process ID of the program and a line of input which
+ is read from the terminal when the variable is evaluated, respectively.
+ If a variable has a name of the form $&word, then word is considered a
+ vector (see above), and its value is taken to be the value of the vari-
+ able. If $foo is a valid variable, and is of type list, then the
+ expression $foo[low-high] represents a range of elements. Either the
+ upper index or the lower may be left out, and the reverse of a list may
+ be obtained with $foo[len-0]. Also, the notation $?foo evaluates to 1
+ if the variable foo is defined, 0 otherwise, and $#foo evaluates to the
+ number of elements in foo if it is a list, 1 if it is a number or
+ string, and 0 if it is a boolean variable.
+
+ History substitutions, similar to C-shell history substitutions, are
+ also available - see the C-shell manual page for all of the details.
+
+ The characters ~, {, and } have the same effects as they do in the C-
+ Shell, i.e., home directory and alternative expansion. It is possible
+ to use the wildcard characters *, ?, [, and ] also, but only if you
+ unset noglob first. This makes them rather useless for typing algebraic
+ expressions, so you should set noglob again after you are done with
+ wildcard expansion. Note that the pattern [^abc] will match all charac-
+ ters except a, b, and c.
+
+ IO redirection is available - the symbols >, >>, >&, >>&, and < have
+ the same effects as in the C-shell.
+
+ You may type multiple commands on one line, seperated by semicolons.
+
+ If you want to use a different mfbcap file than the default (usually
+ ~cad/lib/mfbcap), you have to set the environment variable MFBCAP
+ before you start nutmeg. The -m option and the mfbcap variable no
+ longer work.
+
+VMS NOTES
+ Nutmeg can be run under VAX/VMS. Some features like command, etc com-
+ pletion, expansion of *, ?, and [], backquote substitution, the shell
+ command, and so forth do not work. (In fact command completion only
+ works on 4.2 or 4.3 BSD.)
+
+ Nutmeg will look for start-up commands in the file spice.rc in the cur-
+ rent directory.
+
+ The standard suffix for rawspice files in VMS is ".raw".
+
+ You will have to respond to the -more- prompt during plot with a car-
+ riage return instead of any key as you can do on UNIX.
+
+SEE ALSO
+ sconvert(1), spice(1), mfb(3), writedata(3)
+
+AUTHOR
+ Wayne Christopher (faustus@xxxxxxxxxxxxxxxx)
+
+BUGS
+ The label entry facilities are very primitive - after all, nutmeg isn�t
+ a graphics editor (yet). You must be careful to type very slowly when
+ entering labels -- nutmeg checks the X event queue once every second,
+ and can get very confused if characters arrive faster than that.
+
+ If you redefine colors after creating a plot window with X, and then
+ cause the window to be redrawn, it will not to the right thing.
+
+ When defining aliases like
+
+ alias pdb plot db( �!:1� - �!:2� )
+
+ you must be careful to quote the argument list substitutions in this
+ manner. If you quote the whole argument it might not work properly.
+
+ In a user-defined function, the arguments cannot be part of a name that
+ uses the plot.vec syntax. I.e,
+
+ define poke(duck) cos(tran1.duck)
+
+ won�t do the right thing.
+
+ If you type plot all all, or otherwise use a wildcard reference for one
+ plot twice in a command, bad things will happen.
+
+ The asciiplot command doesn�t deal with log scales or the delta key-
+ words.
+
+ There are probably some features that nutmeg doesn�t have yet.
+
+CAVEATS
+ Often the names of terminals recognised by MFB are different from those
+ in /etc/termcap. Thus you may have to reset your terminal type with the
+ command
+
+ set term = termname
+
+ where termname is the name in the mfbcap file.
+
+ The hardcopy command is useless on VMS and other systems without the
+ plot command, unless the user has a program that understands plot(5)
+ format.
+
+
+
+
+4th Berkeley Distribution 27 April 1987 NUTMEG(1)
+</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-ngsconvert_mp.html b/docs/wiki/geda-ngsconvert_mp.html
new file mode 100644
index 0000000..bf4030a
--- /dev/null
+++ b/docs/wiki/geda-ngsconvert_mp.html
@@ -0,0 +1,139 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="ngsconvert_man-page" id="ngsconvert_man-page">ngsconvert man-page</a></h1>
+<div class="level1">
+<pre class="code">SCONVERT(1) SCONVERT(1)
+
+
+
+NAME
+ sconvert - convert spice formats
+
+SYNOPSIS
+ sconvert fromtype fromfile totype tofile
+ sconvert fromtype totype
+ sconvert
+
+DESCRIPTION
+ Sconvert translates spice output files among three formats: the old
+ binary format, a new binary format, and a new ascii format. The for-
+ mats are specified by the fromtype and totype arguments: ââ?¬Ë?oââ?¬â?¢ for the
+ old format, ââ?¬Ë?bââ?¬â?¢ for the new binary format, and ââ?¬Ë?aââ?¬â?¢ for the new ascii
+ format. Fromtype specifies the format to be read, and totype specifies
+ the format to be written. If fromfile and tofile are given, then they
+ are used as the input and output, otherwise standard input and output
+ are used. (Note that this second option is only available on UNIX sys-
+ tems - on VMS and other systems you must supply the filenames.) If no
+ arguments are given, the parameters are prompted for.
+
+ Binary format is the preferred format for general use, as it is the
+ most economical in terms of space and speed of access, and ascii is
+ provided to make it easy to modify data files and transfer them between
+ machines with different floating-point formats. The old format is pro-
+ vided only for backward compatibility. The three formats are as fol-
+ lows:
+
+ Old:
+
+ What Size in Bytes
+
+ title 80
+ date 8
+ time 8
+ numoutputs 2
+ the integer 4 2
+ variable names --
+ char[numoutputs][8] numoutputs * 8
+ types of output numoutputs * 2
+ node index numoutputs * 2
+ plot title numoutputs * 24
+ the actual data numpoints * numoutputs * 8
+
+ Ascii:
+
+ Title: Title Card String
+ Date: Date
+ [ Plotname: Plot Name
+ Flags: complex or real
+ No. Variables: numoutputs
+ No. Points: numpoints
+ Command: nutmeg command
+ Variables: 0 varname1 typename1
+ 1 varname2 typename2
+ etc...
+ Values:
+ 0 n n n n ...
+ 1 n n n n ...
+ And so forth...
+ ] repeated one or more times
+
+
+ If one of the flags is complex, the points look like r,i where r and i
+ are floating point (in %e format). Otherwise they are in %e format.
+ Only one of real and complex should appear.
+
+ The lines are guaranteed to be less than 80 columns wide (unless the
+ plot title or variable names are very long), so this format is safe
+ to mail between systems like CMS.
+
+ Any number of Command: lines may appear between the No. Points:
+ and the Variables: lines, and whenever the plot is loaded into
+ nutmeg they will be executed.
+
+ Binary:
+
+ Title Card (a NULL terminated string)
+ Date, Time (a NULL terminated string)
+ [
+ Plot title (a NULL terminated string)
+ Number of variables (an int)
+ Number of data points (an int)
+ flags (a short)
+ variable header struct (repeated numoutputs times)
+ variable name (a NULL terminated string)
+ variable type (an int)
+ set of outputs (repeated numpoints times)
+ ] repeated one or more times.
+
+
+ A set of outputs is a vector of doubles of length numoutputs, or
+ a vector of real-imaginary pairs of doubles if the data is complex.
+
+SEE ALSO
+ nutmeg(1), spice(1), writedata(3)
+
+AUTHOR
+ Wayne Christopher (faustus@xxxxxxxxxxxxxxxx)
+
+BUGS
+ If variable names and the title and plotname strings have trailing
+ blanks in them they will be stripped off when the file is read, if it
+ is in ascii format.
+
+ If a plot title begins with "Title:" nutmeg will be fooled into think-
+ ing that this is an ascii format file. Sconvert always requires the
+ type to be specified, however.
+
+
+
+
+4th Berkeley Distribution 20 March 1986 SCONVERT(1)
+</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-ngspice_and_gschem.html b/docs/wiki/geda-ngspice_and_gschem.html
new file mode 100644
index 0000000..7cad960
--- /dev/null
+++ b/docs/wiki/geda-ngspice_and_gschem.html
@@ -0,0 +1,180 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#overview" class="toc">Overview</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#setup" class="toc">Setup</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#adding_some_spice_stuff" class="toc">Adding some SPICE stuff</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#simulation" class="toc">Simulation</a></span></div></li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="overview" id="overview">Overview</a></h1>
+<div class="level1">
+
+<p>
+ It is possible to use gschem to make circuit diagrams which can then be simulated with ngspice. The advantage is that you can iteratively design and simulate before you commit to fabrication. The purpose of this tutorial is not to teach the details of SPICE but rather to work a very simple example so that the required steps are made clear. More detailed documents on both Spice and gEDA can be found at:
+</p>
+<ul>
+<li class="level1"><div class="li"> <a href="http://ngspice.sourceforge.net/index.html"; class="urlextern" title="http://ngspice.sourceforge.net/index.html"; rel="nofollow">ngspice</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-csygas.html" class="wikilink1" title="geda-csygas.html">geda and Spice</a></div>
+</li>
+</ul>
+
+<p>
+ There is a <acronym title="Frequently Asked Questions">FAQ</acronym> in the wiki that may be of help: <a href="geda-faq-simulation.html" class="wikilink1" title="geda-faq-simulation.html">faq-simulation</a>
+</p>
+
+<p>
+ This tutorial is based on the example â??TwoStageAmp.schâ?? in the examples which ship in gEDAâ??s documentation and constructs the first half of that example step by step.
+</p>
+
+</div>
+<!-- SECTION "Overview" [1-772] -->
+<h1><a name="setup" id="setup">Setup</a></h1>
+<div class="level1">
+
+<p>
+ It is assumed that you are able to construct schematics with gschem. If you are unsure how to do this please visit <a href="geda-gsch2pcb_tutorial.html" class="wikilink1" title="geda-gsch2pcb_tutorial.html">gsch2pcb_tutorial</a>. So letâ??s start by making a project directory â??simpleSPICEâ?? and creating a schematic file named â??simplespice.schâ?? in that directory.
+</p>
+
+<p>
+Use gschem to build up a schematic that looks like:
+</p>
+
+<p>
+<a href="media/geda/simple1.png" class="media" target="_blank" title="geda:simple1.png"><img src="media/geda/simple1.png" class="media" alt="" /></a>
+</p>
+
+<p>
+Note that three named nets have been created, â??Vinâ??, â??Voutâ??, and â??Vbaseâ??. Although this is not necessary, it is an easy way to keep track of important points in the circuit. Naming nets is done by editing either by right-clicking or by hitting â??eeâ?? while a net is selected; then just add the attribute â??netnameâ?? and give it an appropriate name. Although we now have a circuit to simulate, we need to add some SPICE specific information before we can get any results.
+</p>
+
+</div>
+<!-- SECTION "Setup" [773-1612] -->
+<h1><a name="adding_some_spice_stuff" id="adding_some_spice_stuff">Adding some SPICE stuff</a></h1>
+<div class="level1">
+
+<p>
+ There are four things that we will need to add to the schematic to make it suitable for simulation. We must include an input signal, describe the properties of the transistor, explicitly define Vcc, and add some lines to the SPICE file. When all these things are done the schematic will look like:
+</p>
+
+<p>
+<a href="media/geda/schematicfinished2.png" class="media" target="_blank" title="geda:schematicfinished2.png"><img src="media/geda/schematicfinished2.png" class="media" title="" alt="" /></a>
+</p>
+
+<p>
+The input signal is added by choosing â??SPICE simulation elements→vac-1.symâ?? from the components menu and, after placing the device, editing its properties to read:
+</p>
+
+<p>
+<a href="media/geda/dialogvac.png" class="media" target="_blank" title="geda:dialogvac.png"><img src="media/geda/dialogvac.png" class="media" title="" alt="" /></a>
+</p>
+
+<p>
+Notice that the â??valueâ?? is a string that will be read by SPICE. You learn about SPICE syntax in the links given above.
+</p>
+
+<p>
+Vcc is set in basically the same way except we choose â??SPICE simulation elements→vdc-1.symâ?? from the components menu. Its properties should be edited to read:
+</p>
+
+<p>
+<a href="media/geda/dialogvdc1.png" class="media" target="_blank" title="geda:dialogvdc1.png"><img src="media/geda/dialogvdc1.png" class="media" title="" alt="" /></a>
+</p>
+
+<p>
+The transistor setup is a bit more complicated. We must first have access to a SPICE model for the transistor of interest. This can usually be found from the transistor datasheet or downloaded from a manufacturer website. For this example we will consider the ubiquitous 2N3904. Which has the following model:
+</p>
+<pre class="code">.model 2N3904 NPN(Is=6.734f Xti=3 Eg=1.11 Vaf=74.03 Bf=416.4 Ne=1.259
++ Ise=6.734f Ikf=66.78m Xtb=1.5 Br=.7371 Nc=2 Isc=0 Ikr=0 Rc=1
++ Cjc=3.638p Mjc=.3085 Vjc=.75 Fc=.5 Cje=4.493p Mje=.2593 Vje=.75
++ Tr=239.5n Tf=301.2p Itf=.4 Vtf=4 Xtf=2 Rb=10)
+* Fairchild pid=23 case=TO92
+* 88-09-08 bam creation </pre>
+
+<p>
+Make a sub-folder named â??modelsâ?? in our project folder â??simpleSPICEâ?? and make a file named â??2N3904.modâ?? in that folder and fill it with the model text given above. Make sure that there is a newline at the end of the file, this is important so that when the final SPICE file is created everything will be on its own line. Okay, now that we have a model for the transistor we have to apply it. Edit the transistor properties to read:
+</p>
+
+<p>
+<a href="media/geda/dialogtrans.png" class="media" target="_blank" title="geda:dialogtrans.png"><img src="media/geda/dialogtrans.png" class="media" title="" alt="" /></a>
+</p>
+
+<p>
+Now we also need to inform gschem of the model file we created. This is done by adding a â??spice-model-1.symâ?? symbol to the schematic. Edit its properties to read:
+</p>
+
+<p>
+<a href="media/geda/dialogmodel.png" class="media" target="_blank" title="geda:dialogmodel.png"><img src="media/geda/dialogmodel.png" class="media" title="" alt="" /></a>
+</p>
+
+<p>
+Okay, there are two more symbols to add. The first is â??spice-include-1.symâ?? which will include a text file which describes the SPICE simulation you may want to run and the other is â??spice-directive-1.symâ?? which allows additional lines to be added to the SPICE file. The properties of these symbols can be set as:
+</p>
+
+<p>
+<a href="media/geda/dialoginclude.png" class="media" target="_blank" title="geda:dialoginclude.png"><img src="media/geda/dialoginclude.png" class="media" alt="" /></a>
+</p>
+
+<p>
+<a href="media/geda/dialogdirective.png" class="media" target="_blank" title="geda:dialogdirective.png"><img src="media/geda/dialogdirective.png" class="media" alt="" /></a>
+</p>
+
+<p>
+Congratulations! We now have a schematic that is ready for simulation.
+</p>
+
+</div>
+<!-- SECTION "Adding some SPICE stuff" [1613-4297] -->
+<h1><a name="simulation" id="simulation">Simulation</a></h1>
+<div class="level1">
+
+<p>
+ Although the schematic is in place, we still need to write out what the simulation will do. This information will be written in the './Simulation.cmdâ?? that was referenced in the include symbol added in the last section. For now, create a file './Simulation.cmdâ?? and make it read:
+</p>
+<pre class="code">.OP
+.AC DEC 20 1Hz 100MegHz
+* .DC VINPUT 0 5 .01
+* .DC VINPUT 1 2 .01
+.plot ac v(Vout) v(Vin)
+.print ac v(Vout) v(Vin)</pre>
+
+<p>
+Which does one AC analysis while two lines for DC analysis are commented out. Then both Vout and Vin are plotted as well as having their numerical values printed. As mentioned previously, SPICE can be learned from the links given above.
+</p>
+
+<p>
+Now that we have described the simulation we want done, open a terminal, move to the â??simpleSPICEâ?? directory and type the command:
+</p>
+<pre class="code">gnetlist -g spice-sdb -o spice.net simplespice.sch</pre>
+
+<p>
+ to produce the SPICE file â??spice.netâ??. Now the simulation can be run in batch mode by typing:
+</p>
+<pre class="code">ngspice -b spice.net > result.txt</pre>
+
+<p>
+ which will spew a great deal of text to â??result.txtâ??. The file should include the numerical output we requested as well as a crude ascii plot of the results. Note that the 10mV input signal has been amplified to about -280mV over a wide frequency range. If you want to veiw graphical plots ngspice can be operated in interactive mode by removing the -b option. The ngspice website describes this in more detail. In any event, we now have the simulation results in a nice text format suitable for reading with a script, perhaps something written in python or octave, for further graphing or analysis.
+</p>
+
+</div>
+<!-- SECTION "Simulation" [4298-] --></body>
+</html>
diff --git a/docs/wiki/geda-ngspice_mp.html b/docs/wiki/geda-ngspice_mp.html
new file mode 100644
index 0000000..e2a68a9
--- /dev/null
+++ b/docs/wiki/geda-ngspice_mp.html
@@ -0,0 +1,339 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="ngspice_man-page" id="ngspice_man-page">ngspice man-page</a></h1>
+<div class="level1">
+<pre class="code">SPICE(1) SPICE(1)
+
+
+
+NAME
+ spice - circuit simulator
+
+SYNOPSIS
+ spice [ -n ] [ -t term ] [ -r rawfile] [ -b ] [ -i ] [ input file ... ]
+
+DESCRIPTION
+ This manual page describes the commands available for interactive use
+ of SPICE3. For details of circuit descriptions and the process of simu-
+ lating a circuit, see the SPICE3 User�s Manual. The commands available
+ are a superset of those available for nutmeg - only the additional com-
+ mands available in SPICE3 are described here. You should be familiar
+ with the manual page for nutmeg(1) before reading this manual page.
+
+ Arguments are:
+
+ -n (or --no-spiceinit)
+ Don�t try to source the file ".spiceinit" upon startup. Normally
+ SPICE3 tries to find the file in the current directory, and if
+ it is not found then in the user�s home directory.
+
+ -q (or --completion)
+ Enable command completion.
+
+ -t term (or --term=term)
+ The program is being run on a terminal with mfb name term.
+
+ -b (or --batch)
+ Run in batch mode. SPICE3 will read the standard input or the
+ specified input file and do the simulation. Note that if the
+ standard input is not a terminal, SPICE3 will default to batch
+ mode, unless the -i flag is given.
+
+ -s (or --server)
+ Run in server mode. This is like batch mode, except that a tem-
+ porary rawfile is used and then written to the standard output,
+ preceded by a line with a single "@", after the simulation is
+ done. This mode is used by the spice daemon.
+
+ -i (or --interactive)
+ Run in interactive mode. This is useful if the standard input is
+ not a terminal but interactive mode is desired. Command comple-
+ tion is not available unless the standard input is a terminal,
+ however.
+
+ -r rawfile (or --rawfile=file)
+ Use rawfile as the default file into which the results of the
+ simulation are saved.
+
+ -c circuitfile (or --circuitfile=circuitfile)
+ Use circuitfile as the default input deck.
+
+ -h (or --help)
+ Display a verbose help on the arguments available to the pro-
+ gram.
+
+ -v (or --version)
+ Display a version number and copyright information of the pro-
+ gram.
+
+ Further arguments are taken to be SPICE3 input decks, which are read
+ and saved. (If batch mode is requested then they are run immediately.)
+
+ SPICE3 will accept any SPICE2 input decks, and output ascii plots,
+ fourier analyses, and node printouts as specified in .plot, .four, and
+ .print cards. If a out parameter is given on a .width card, the effect
+ is the same as set width = .... Since SPICE3 ascii plots do not use
+ multiple ranges, however, if vectors together on a .plot card have dif-
+ ferent ranges they will not provide as much information as they would
+ in SPICE2. The output of SPICE3 is also much less verbose than SPICE2,
+ in that the only data printed is that requested by the above cards.
+
+ Vector names are the same as in nutmeg, with this addition: a name such
+ as @name[param], where name is either the name of a device instance or
+ model, denotes the value of the param parameter of the device or model.
+ See the SPICE3 User�s Manual for details of what parameters are avail-
+ able. The value is a vector of length 1. This function is also avail-
+ able with the show command, and is available with variables for conve-
+ nience for command scripts.
+
+ SPICE3 commands are as follows (these are only those commands not also
+ available in nutmeg - consult the nutmeg manual page for more com-
+ mands):
+
+ setcirc [circuit name]
+ Change the current circuit. The current circuit is the one that
+ is used for the simulation commands below. When a circuit is
+ loaded with the source command (see below) it becomes the cur-
+ rent circuit.
+
+ op [.op card args]
+ Do an operating point analysis.
+
+ tran [.tran card args]
+ Do a transient analysis.
+
+ ac [.ac card args]
+ Do an ac analysis.
+
+ dc [.dc card args]
+ Do a dc transfer curve analysis.
+
+ listing [logical] [physical] [deck] [expand]
+ Print a listing of the current circuit. If the logical argument
+ is given, the listing is with all continuation lines collapsed
+ into one line, and if the physical argument is given the lines
+ are printed out as they were found in the file. The default is
+ logical. A deck listing is just like the physical listing,
+ except without the line numbers it recreates the input file ver-
+ batim (except that it does not preserve case). If the word
+ expand is present, the circuit will be printed with all subcir-
+ cuits expanded.
+
+ edit [file]
+ Print the current SPICE3 deck into a file, call up the editor on
+ that file and allow the user to modify it, and then read it back
+ in, replacing the origonal deck. If a filename is given, then
+ edit that file and load it, making the circuit the current one.
+
+ resume Resume a simulation after a stop.
+
+ show Show a device parameter.
+
+ alter Alter a device parameter.
+
+ state Print the state of the circuit. (This command is largely unim-
+ plemented.)
+
+ save [all] [output ...] or .save [all] [output ...]
+ Save a set of outputs, discarding the rest. If a node has been
+ mentioned in a save command, it will appear in the working plot
+ after a run has completed, or in the rawfile if spice is run in
+ batch mode. If a node is traced or plotted (see below) it will
+ also be saved. For backward compatibility, if there are no save
+ commands given, all outputs are saved.
+
+ stop [ after n] [ when something cond something ] ...
+ Set a breakpoint. The argument after n means stop after n itera-
+ tion number n, and the argument when something cond something
+ means stop when the first something is in the given relation
+ with the second something, the possible relations being eq or =
+ (equal to), ne or <> (not equal to), gt or > (greater than), lt
+ or < (less than), ge or >= (greater than or equal to), and le or
+ <= (less than or equal to). IO redirection is disabled for the
+ stop command, since the relational operations conflict with it
+ (it doesn�t produce any output anyway). The somethings above
+ may be node names in the running circuit, or real values. If
+ more than one condition is given, e.g. stop after 4 when v(1) >
+ 4 when v(2) < 2, the conjunction of the conditions is implied.
+
+ trace [ node ...]
+ Trace nodes. Every iteration the value of the node is printed to
+ the standard output.
+
+ iplot [ node ...]
+ Incrementally plot the values of the nodes while SPICE3 runs.
+
+ step [number]
+ Iterate number times, or once, and then stop.
+
+ status Display all of the traces and breakpoints currently in effect.
+
+ delete [debug number ...]
+ Delete the specified breakpoints and traces. The debug numbers
+ are those shown by the status command. (Unless you do status >
+ file, in which case the debug numbers aren�t printed.)
+
+ reset Throw out any intermediate data in the circuit (e.g, after a
+ breakpoint or after one or more analyses have been done
+ already), and re-parse the deck. The circuit can then be re-run.
+ (Note: this command used to be end in SPICE 3a5 and earlier ver-
+ sions -- end is now used for control structures.) The run com-
+ mand will take care of this automatically, so this command
+ should not be necessary...
+
+ run [rawfile]
+ Run the simulation as specified in the input file. If there were
+ any of the control cards .ac, .op, .tran, or .dc, they are exe-
+ cuted. The output is put in rawfile if it was given, in addition
+ to being available interactively.
+
+ source file
+ Read the SPICE3 input file file. Nutmeg and SPICE3 commands may
+ be included in the file, and must be enclosed between the lines
+ .control and .endc. These commands are executed immediately
+ after the circuit is loaded, so a control line of ac ... will
+ work the same as the corresponding .ac card. The first line in
+ any input file is considered a title line and not parsed but
+ kept as the name of the circuit. The exception to this rule is
+ the file .spiceinit. Thus, a SPICE3 command script must begin
+ with a blank line and then with a .control line. Also, any line
+ beginning with the characters *# is considered a control line.
+ This makes it possible to imbed commands in SPICE3 input files
+ that will be ignored by earlier versions of SPICE. Note: in
+ spice3a7 and before, the .control and .endc lines were not
+ needed, and any line beginning with the name of a front-end com-
+ mand would be executed.
+
+ linearize vec ...
+ Create a new plot with all of the vectors in the current plot,
+ or only those mentioned if arguments are given. The new vectors
+ will be interpolated onto a linear time scale, which is deter-
+ mined by the values of tstep, tstart, and tstop in the currently
+ active transient analysis. The currently loaded deck must
+ include a transient analysis (a tran command may be run interac-
+ tively before the last reset, alternately), and the current plot
+ must be from this transient analysis. This command is needed
+ because SPICE3 doesn�t output the results from a transient anal-
+ ysis in the same manner that SPICE2 did.
+
+ There are several set variables that SPICE3 uses but nutmeg does not.
+ They are:
+
+ editor
+ The editor to use for the edit command.
+
+ modelcard
+ The name of the model card (normally .model).
+
+ noaskquit
+ Do not check to make sure that there are no circuits
+ suspended and no plots unsaved. Normally SPICE3 will
+ warn the user when he tries to quit if this is the
+ case.
+
+ nobjthack
+ Assume that BJT�s have 4 nodes.
+
+ noparse
+ Don�t attempt to parse decks when they are read in
+ (useful for debugging). Of course, they cannot be run
+ if they are not parsed.
+
+ nosubckt
+ Don�t expand subcircuits.
+
+ renumber
+ Renumber input lines when a deck has .include�s.
+
+ subend
+ The card to end subcircuits (normally .ends).
+
+ subinvoke
+ The prefix to invoke subcircuits (normally x).
+
+ substart
+ The card to begin subcircuits (normally .subckt).
+
+ There are a number of rusage parameters available, in addition to the
+ ones available in nutmeg:
+
+
+
+ If there are subcircuits in the input file, SPICE3 expands instances of
+ them. A subcircuit is delimited by the cards .subckt and .ends, or
+ whatever the value of the variables substart and subend is, respec-
+ tively. An instance of a subcircuit is created by specifying a device
+ with type �x� - the device line is written
+
+ xname node1 node2 ... subcktname
+
+ where the nodes are the node names that replace the formal parameters
+ on the .subckt line. All nodes that are not formal parameters are
+ prepended with the name given to the instance and a �:�, as are the
+ names of the devices in the subcircuit. If there are several nested
+ subcircuits, node and device names look like subckt1:subckt2:...:name.
+ If the variable subinvoke is set, then it is used as the prefix that
+ specifies instances of subcircuits, instead of �x�.
+
+VMS NOTES
+ The standard suffix for rawspice files in VMS is ".raw".
+
+ You may have to redefine the value EDITOR if you wish to use the edit
+ command, since the default for VMS is "vi".
+
+SEE ALSO
+ nutmeg(1), sconvert(1), spice(1), mfb(3), writedata(3) SPICE3 User�s
+ Guide
+
+AUTHORS
+ SPICE3: Tom Quarles (quarles@xxxxxxxxxxxxxxxx)
+ nutmeg / User interface: Wayne Christopher (faustus@xxxxxxxxxxxxxxxx)
+
+BUGS
+ SPICE3 will recognise all the notations used in SPICE2 .plot cards, and
+ will translate vp(1) into ph(v(1)), and so forth. However, if there are
+ spaces in these names it won�t work. Hence v(1, 2) and (-.5, .5) aren�t
+ recognised.
+
+ BJT�s can have either 3 or 4 nodes, which makes it difficult for the
+ subcircuit expansion routines to decide what to rename. If the fourth
+ parameter has been declared as a model name, then it is assumed that
+ there are 3 nodes, otherwise it is considered a node. To disable this
+ kludge, you can set the variable "nobjthack", which will force BJT�s to
+ have 4 nodes (for the purposes of subcircuit expansion, at least).
+
+ The @name[param] notation might not work with trace, iplot, etc. yet.
+
+ The first line of a command file (except for the .spiceinit file)
+ should be a comment. Otherwise SPICE may create an empty circuit
+ structure.
+
+CAVEATS
+ SPICE3 files specified on the command line are read in before the .spi-
+ ceinit file is read. Thus if you define aliases there that you call in
+ a SPICE3 source file mentioned on the command line, they won�t be
+ recognised.
+
+
+
+
+4th Berkeley Distribution 20 March 1986 SPICE(1)
+</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-olib_readme.html b/docs/wiki/geda-olib_readme.html
new file mode 100644
index 0000000..72f3264
--- /dev/null
+++ b/docs/wiki/geda-olib_readme.html
@@ -0,0 +1,123 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="olib_orcad_tm_converter_readme" id="olib_orcad_tm_converter_readme">olib (OrCAD (TM) converter) README</a></h1>
+<div class="level1">
+<pre class="code">###############################################################
+README and release notes for olib2geda - 1 settembre 2002
+OrCAD (TM) lib ASCII dump to gEDA .sym converter
+###############################################################
+
+
+What it olib2geda?
+It's a simple automated converter from OrCAD v4 (in SDT version 1.10) parts
+library (in ASCII dump format, through "decomp" utility) to gEDA component
+definition in .sym format file.
+It allow an initial dumb conversion file to file, with one lib converted in
+multiple .sym file, one per component in library.
+The converted component file needs little editing to become usable, but in some
+case needs no editing at all.
+
+
+What olib do.
+* Convert box shaped component in OrCAD (TM) lib in .sym file in gEDA format
+* Place pin, pin name, pin type, pin number
+* Place logic bubble when needed (DOT attribute in OrCAD (TM), for logic nega-
+ tion)
+* Place clock arrow when needed (CLK attribute)
+* Place reference, from REFERENCE statement in OrCAD (TM)
+* Place Part name as label and device name as attribute
+* Parse and draw non-box component, with LINE, ARC, CIRCLE and TEXT
+* Add power pin as invisible net=name:pin attribute when detected (in OrCAD (TM)
+ invisible pin has tipically T0 and B0 coords)
+* Through command line switch, hides pin name in VECTOR drawed symbols, allowing
+ better appearance
+* Write both new (20020825) and old (20020209) file format for .sym files
+ through a switch on the command line
+
+
+What olib do not.
+* Do not parse and store alternate component drawing (statement CONVERT in
+ OrCAD (TM))
+* Do not handle drawing part using VECTOR list from another part (statement
+ VECTOR 'partname' in OrCAD (TM))
+* Do not handle FILL statement in VECTOR statement (incompatible with gEDA, but
+ for what i know is used only for "better" part drawing)
+* Do not handle multiple part in one package (slots in gEDA)
+
+
+Bugs.
+More and more. But for the use that I do bugs aren't so critical.
+If you find a bug or want improvements to the program, feel free to contact me
+at the e-mail address at the end of this text.
+
+
+How to obtain last version.
+Open the URL:
+http://digilander.libero.it/tailchaser
+in section "Linux" you can see the main page of olib.
+
+
+Compile and install.
+[[ Ales here, I have incorperated olib into the ./configure build mechanism,
+ so these instructions only apply if you build from Mario's distribution ]]
+
+To compile program go in directory 'src' of the unpacked tarball, and type
+'make'. This produces the binary executable, named 'olib'.
+Compilation process uses the flex scanner generator to generate the file
+'olib.c' from the 'olib.lex', and link the library math to the code. The binary
+included in the distribution is compiled on a P266-MMX with RedHat 7.2, with gcc
+version 2.96 and flex 2.5.4, but the program don't require any special feature
+or critical function, as far as I know. At the end of compilation phase, you can
+see two warnings:
+* warning, -s option given but default rule can be matched
+* warning: `yyunput' defined but not used
+this is normal, don't affect program functionality, and you can safely ignore
+it.
+Installation is not needed for normal operations, but if you want you can copy
+only the executable (olib) on a directory in the PATH.
+
+
+Use of olib.
+To convert library, first convert it to ASCII dump with 'decomp' utility
+included in the OrCAD (TM) distribution. After that invoke the lib converter:
+olib path/to/file/file_ascii prefix where 'prefix' is used to generate file name
+of every symbol, like:
+prefix-partname-1.sym
+During the process, you can see a lot of ugly text scrolling in the terminal,
+that show the progress of the conversion. If you want to read this text, you can
+redirect the stderr output to a file:
+olib path/to/file/file_ascii prefix 2> logfile.txt
+where '2>' instruct the shell to redirect stderr output to logfile.txt.
+The converter write one file per part, in the current directory. At the end of
+the execution you can see a lot of file in the directory, extracted from OrCAD
+library.
+In the (not so improbable) case of incomplete conversion of a part (i.e. because
+of unsupported VECTOR 'partname' statement), the file of the incomplete part
+will be named 'prefix-partname-1.sym.part', stand for partial conversion.
+If the conversion process stops with the message: "flex scanner jammed", the
+converter has encountered an unknown statement, an incompatible version of
+library, or a bug. If you can, please report the complete log and the library
+dump, to allow corrections or improvements.
+
+
+Mario Pascucci
+<m.pas@xxxxxxxxx>
+</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-pcb-quick_reference.fr.html b/docs/wiki/geda-pcb-quick_reference.fr.html
new file mode 100644
index 0000000..0bd7a4c
--- /dev/null
+++ b/docs/wiki/geda-pcb-quick_reference.fr.html
@@ -0,0 +1,447 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#pcbreference_rapide" class="toc">PCB: Référence Rapide</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#disposition_des_touches" class="toc">Disposition des Touches</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#table_des_touches_pcb" class="toc">Table des Touches PCB</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#touches_de_visualisation" class="toc">Touches de Visualisation</a></span></div></li>
+</ul>
+</li>
+<li class="level1"><div class="li"><span class="li"><a href="#reference_d_empreintes" class="toc">Référence d'Empreintes</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#syntaxe_generale" class="toc">Syntaxe Générale</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#elements" class="toc">�léments</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#pastilles" class="toc">Pastilles</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#broches" class="toc">Broches</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#exemples" class="toc">Exemples</a></span></div></li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="pcbreference_rapide" id="pcbreference_rapide">PCB: Référence Rapide</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "PCB: Référence Rapide" [1-39] -->
+<h2><a name="disposition_des_touches" id="disposition_des_touches">Disposition des Touches</a></h2>
+<div class="level2">
+
+</div>
+<!-- SECTION "Disposition des Touches" [40-76] -->
+<h3><a name="table_des_touches_pcb" id="table_des_touches_pcb">Table des Touches PCB</a></h3>
+<div class="level3">
+<table class="inline">
+ <tr>
+ <th class="centeralign"> TOUCHE </th><th class="leftalign"> MNEMONIQUE </th><th class="centeralign"> DESCRIPTION </th>
+ </tr>
+ <tr>
+ <td class="centeralign"> esc </td><td class="leftalign"> panner </td><td> enter panning mode </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> insert </td><td class="leftalign"> insert point </td><td> enter insert point mode. Click and drag on track to insert a point </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> space </td><td class="leftalign"> select </td><td class="leftalign"> entrez en mode select </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> tab </td><td class="leftalign"> flip view </td><td class="leftalign"> view: flip board </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> shift-del </td><td class="leftalign"> del-cu </td><td class="leftalign"> deletes electrically connected copper (including power and signal planes) </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> \ </td><td class="leftalign"> thin-draw </td><td class="leftalign"> toggles thin draw mode </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> shift-alt-a </td><td class="leftalign"> unselect </td><td class="leftalign"> clear selection </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> b </td><td class="leftalign"> to other side </td><td class="leftalign"> flip object to the other side of the board </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> shift-b </td><td class="leftalign"> flip view </td><td class="leftalign"> view: flip board </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> c </td><td class="leftalign"> center </td><td class="leftalign"> view: center display at cursor position </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> ctrl-c </td><td> copy to buffer</td><td class="leftalign"> copie la sélection vers le tampon et désélectionne </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> d </td><td class="leftalign"> display name </td><td class="leftalign"> affiche le nom de la broche ou pastille </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> shift-d </td><td class="leftalign"> pinout dialog </td><td class="leftalign"> open pinout window for element under mouse cursor </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> e </td><td> eliminate rats</td><td class="leftalign"> efface tous les rats </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> shift-e </td><td class="leftalign"> eliminate some rats </td><td class="leftalign"> efface tous les rats sélectionnés </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> f </td><td class="leftalign"> find </td><td class="leftalign"> highlight connections to object under mouse cursor </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> shift-f </td><td class="leftalign"> un-find </td><td class="leftalign"> un-highlight found connections </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> g </td><td class="leftalign"> increase grid </td><td class="leftalign"> increment grid by configured grid increment </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> shift-g </td><td class="leftalign"> decrease grid </td><td class="leftalign"> decrement grid by configured grid increment </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> h </td><td class="leftalign"> hide </td><td class="leftalign"> toggle the visiblity of the refdes or value attached to the current component </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> ctrl-h </td><td class="leftalign"> holeplate </td><td class="leftalign"> toggle plating of a via. Used to produce non metalized mounting holes </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> k </td><td class="leftalign"> klearance </td><td class="leftalign"> increment clearance (soldermask to copper edge) </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> shift-k </td><td class="leftalign"> klear (-) </td><td class="leftalign"> decrement clearance (soldermask to copper edge (NOTE: can go negative!)) </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> l </td><td class="leftalign"> increase line </td><td class="leftalign"> increment width of the line tool, adds to the settings of the current line style </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> shift-l </td><td class="leftalign"> decrease line </td><td> reduce the current linewidth </td>
+ </tr>
+ <tr>
+ <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="geda-pcb_tips.html#how_do_i_move_one_set_of_layer_tracks_to_another_layer" class="wikilink1" title="geda-pcb_tips.html">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>
+ </tr>
+ <tr>
+ <td class="centeralign"> n </td><td class="leftalign"> name </td><td> show object refdes / pin number at mouse pointer </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> shift-n </td><td class="leftalign"> next </td><td> Select the shortest unselected rat on the board </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> o </td><td class="leftalign"> optimize rats </td><td> optimize and redraw all rats </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> shift-o </td><td class="leftalign"> optimize some rats </td><td> optimize and redraw selected nets only </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> shift-p </td><td class="leftalign"> polygon close </td><td class="leftalign"> connect the first point of a polygon with the last </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> q </td><td class="leftalign"> square toggle </td><td class="leftalign"> toggle square/round corners on pads </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> ctrl-r </td><td class="leftalign"> report </td><td class="leftalign"> show object report </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> s </td><td class="leftalign"> size </td><td class="leftalign"> augmente la taille </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> shift-s </td><td class="leftalign"> size (-) </td><td class="leftalign"> diminue la taille </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> alt-s </td><td class="leftalign"> sizehole </td><td class="leftalign"> augmente la taille du trou </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> alt-shift-s </td><td class="leftalign"> sizehole (-) </td><td class="leftalign"> diminue la taille du trou </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> ctrl-s </td><td class="leftalign"> sizehole </td><td class="leftalign"> augmente la taille du trou </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> ctrl-shift-s </td><td class="leftalign"> sizehole (-) </td><td class="leftalign"> diminue la taille du trou </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> v </td><td class="leftalign"> view extents </td><td class="leftalign"> vue globale de la zone de travail </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> z </td><td class="leftalign"> zoom </td><td class="leftalign"> voir: agrandir </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> shift-z </td><td class="leftalign"> un-zoom </td><td class="leftalign"> voir: réduire </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> F1 </td><td class="leftalign"> via </td><td> entrer lâ??outil de via </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> F2 </td><td class="leftalign"> line </td><td class="leftalign"> entrer lâ??outil de ligne </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> F3 </td><td class="leftalign"> arc </td><td> entrer lâ??outil dâ??arc </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> F4 </td><td class="leftalign"> text </td><td> entrer lâ??outil de texte </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> F5 </td><td class="leftalign"> rectangle </td><td class="leftalign"> entrer lâ??outil de rectangle </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> F6 </td><td class="leftalign"> polygon </td><td class="leftalign"> entrer lâ??outil de polygone </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> F7 </td><td class="leftalign"> buffer </td><td> entrer lâ??outil de mode tampon </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> F8 </td><td class="leftalign"> delete </td><td class="leftalign"> entrer lâ??outil de mode supression </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> F9 </td><td class="leftalign"> rotate </td><td class="leftalign"> entrer lâ??outil de mode de rotation </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> F10 </td><td class="leftalign"> file menu </td><td class="leftalign"> menu fichier </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> F11 </td><td class="leftalign"> select </td><td class="leftalign"> entrer dans le mode sélection (comme [space]) </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> F12 </td><td class="leftalign"> lock </td><td> entrer dans le mode lock </td>
+ </tr>
+</table>
+
+</div>
+<!-- SECTION "Table des Touches PCB" [77-3777] -->
+<h2><a name="touches_de_visualisation" id="touches_de_visualisation">Touches de Visualisation</a></h2>
+<div class="level2">
+<table class="inline">
+ <tr>
+ <th class="centeralign"> TOUCHE </th><th class="centeralign"> MNEMONIC </th><th class="centeralign"> DESCRIPTION </th>
+ </tr>
+ <tr>
+ <td class="centeralign"> esc </td><td class="centeralign"> panner </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> v </td><td class="centeralign"> view extents </td><td>vue globale de la zone de travail</td>
+ </tr>
+ <tr>
+ <td class="centeralign"> c </td><td class="centeralign"> center </td><td>centre la vue sur le curseur</td>
+ </tr>
+ <tr>
+ <td class="centeralign"> z </td><td class="centeralign"> zoom </td><td>agrandissement</td>
+ </tr>
+ <tr>
+ <td class="centeralign"> shift-z </td><td class="centeralign"> un-zoom </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> \ </td><td class="centeralign"> thin-draw on/off </td><td>toggles thin draw mode</td>
+ </tr>
+ <tr>
+ <td class="centeralign"> tab </td><td class="centeralign"> flip view </td><td>retournement carte</td>
+ </tr>
+ <tr>
+ <td class="centeralign"> shift-b </td><td class="centeralign"> flip view </td><td>retournement carte</td>
+ </tr>
+</table>
+
+</div>
+<!-- SECTION "Touches de Visualisation" [3778-4194] -->
+<h1><a name="reference_d_empreintes" id="reference_d_empreintes">Référence d'Empreintes</a></h1>
+<div class="level1">
+
+<p>
+ Le document maître pour la création dâ??empreintes est le <a href="http://pcb.sourceforge.net/index.html#dir"; class="urlextern" title="http://pcb.sourceforge.net/index.html#dir"; rel="nofollow">PCB Manual</a>. Il y a aussi le <a href="http://www.brorson.com/gEDA/land_patterns_20050129.pdf"; class="urlextern" title="http://www.brorson.com/gEDA/land_patterns_20050129.pdf"; rel="nofollow">Footprint Creation for the Open-Source Layout Program PCB</a> de Stuart Brorson.
+</p>
+
+</div>
+<!-- SECTION "Référence d'Empreintes" [4195-4503] -->
+<h2><a name="syntaxe_generale" id="syntaxe_generale">Syntaxe Générale</a></h2>
+<div class="level2">
+
+<p>
+ Un fichier dâ??empreinte pcb peut contenir une des commandes suivantes:
+</p>
+<ul>
+<li class="level1"><div class="li"> <strong><code>Element [element_flags, description, pcb-name, value, mark_x, mark_y, text_x, text_y, text_direction, text_scale, text_flags]</code></strong></div>
+</li>
+<li class="level1"><div class="li"> <strong><code>Pad [x1 y1 x2 y2 thickness clearance mask name pad_number flags]</code></strong></div>
+</li>
+<li class="level1"><div class="li"> <strong><code>Pin [x y thickness clearance mask drillholedia name number flags]</code></strong></div>
+</li>
+<li class="level1"><div class="li"> <strong><code>ElementArc [x y r1 r2 startangle sweepangle thickness]</code></strong></div>
+</li>
+<li class="level1"><div class="li"> <strong><code>ElementLine [x1 y1 x2 y2 thickness] â??> thickness != 1000 = 10 mils almost for all footprints</code></strong></div>
+</li>
+<li class="level1"><div class="li"> Les lignes de commentaires débutent avec le signe â??<strong><code>#</code></strong>â??</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Syntaxe Générale" [4504-5144] -->
+<h2><a name="elements" id="elements">�léments</a></h2>
+<div class="level2">
+
+<p>
+<strong><code>Element [element_flags, description, pcb-name, value, mark_x, mark_y, text_x, text_y, text_direction, text_scale, text_flags]</code></strong>
+</p>
+<table class="inline">
+ <tr>
+ <th class="centeralign"> item </th><th class="centeralign"> allowed value </th><th class="centeralign"> explanation </th><th class="centeralign"> comment </th>
+ </tr>
+ <tr>
+ <td class="centeralign"> element_flags </td><td class="centeralign"> unsigned hex value </td><td class="rightalign"> </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> description </td><td class="centeralign"> string </td><td class="centeralign"> text descriptif de lâ??empreinte </td><td class="leftalign">écrit par lâ??auteur de lâ??empreinte </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> pcb name </td><td class="centeralign"> string </td><td class="centeralign"> refdes utilisé pour ce pcb particulier </td><td class="leftalign">xxx </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> value </td><td class="centeralign"> string </td><td class="centeralign"> valeur du composant sur ce pcb particulier </td><td class="leftalign">xxx </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> mark_x </td><td class="centeralign"> 1/100th mils </td><td class="rightalign"> </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> mark_y </td><td class="centeralign"> 1/100th mils </td><td class="rightalign"> </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> text_x </td><td class="centeralign"> 1/100th mils </td><td class="rightalign"> </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> text_y </td><td class="centeralign"> 1/100th mils </td><td class="rightalign"> </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> text direction </td><td class="centeralign"> decimal integer </td><td class="centeralign"> 0=horiz; 1=ccw90; 2=180; 3=cw90 </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> text_scale </td><td class="centeralign"> decimal integer </td><td class="rightalign"> </td><td class="leftalign">usu. set 100 </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> text_flags </td><td class="centeralign"> unsigned hex </td><td class="rightalign"> </td><td class="rightalign"> </td>
+ </tr>
+</table>
+
+</div>
+<!-- SECTION "�léments" [5145-5981] -->
+<h2><a name="pastilles" id="pastilles">Pastilles</a></h2>
+<div class="level2">
+
+<p>
+<strong><code>Pad[x1 y1 x2 y2 thickness clearance mask name pad_number flags]</code></strong>
+</p>
+<table class="inline">
+ <tr>
+ <th class="centeralign"> Item </th><th class="centeralign"> Allowed Value </th><th class="centeralign"> Explanation </th><th class="centeralign"> Comment </th>
+ </tr>
+ <tr>
+ <td class="centeralign"> x1 </td><td class="centeralign"> 1/100th mils </td><td class="centeralign"> x(1st point) </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> y1 </td><td class="centeralign"> 1/100th mils </td><td class="centeralign"> y(1st point) </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> x2 </td><td class="centeralign"> 1/100th mils </td><td class="centeralign"> x(2nd point) </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> y2 </td><td class="centeralign"> 1/100th mils </td><td class="centeralign"> y(2nd point) </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> thickness </td><td class="centeralign"> 1/100 mils </td><td class="centeralign"> épaisseur de métal entourant le segment de ligne </td><td class="leftalign">voir le .pdf de Brorson </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> clearance </td><td class="centeralign"> 1/100 mils </td><td class="centeralign"> distance vis à vis des autres zones de cuivre sur toutes les couches </td><td class="leftalign">actually 1/2 of this number is used! </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> mask </td><td class="centeralign"> 1/100th mils </td><td class="centeralign"> width of mask relief </td><td class="leftalign">actual width of the mask centered on pad copper </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> name </td><td class="centeralign"> string </td><td class="centeralign"> name of pad (arb. string) </td><td class="leftalign">e.g. â??pad_1â?? or â??positiveâ?? or any other string </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> pad_number </td><td class="centeralign"> string </td><td class="centeralign"> pad # </td><td class="leftalign">used for nets. it MUST be consistent with the definitions on the netlist. </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> flags </td><td class="centeralign"> hex value </td><td class="centeralign"> xxx </td><td class="rightalign"> </td>
+ </tr>
+</table>
+
+</div>
+<!-- SECTION "Pastilles" [5982-6937] -->
+<h2><a name="broches" id="broches">Broches</a></h2>
+<div class="level2">
+
+<p>
+<strong><code>Pin[x y thickness clearance mask drillholedia name number flags]</code></strong>
+</p>
+<table class="inline">
+ <tr>
+ <th class="centeralign"> Item </th><th class="leftalign"> Allowed Value </th><th class="centeralign"> Explanation </th><th class="centeralign"> Comment </th>
+ </tr>
+ <tr>
+ <td class="centeralign"> x </td><td class="centeralign"> 1/100th mils </td><td class="centeralign"> pin x coord. </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> y </td><td class="centeralign"> 1/100th mils </td><td class="centeralign"> pin y coord. </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> thickness </td><td class="centeralign"> 1/100th mils </td><td class="centeralign"> copper diameter </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> clearance </td><td class="centeralign"> 1/100th mils </td><td class="centeralign"> 2*(cu to cu clearance) </td><td class="leftalign">if you want a 10 mil clearance, put 2000 (20 mils) here </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> mask </td><td class="centeralign"> 1/100th mils </td><td class="centeralign"> diameter of mask aperture </td><td class="leftalign">actual dia. of hole in mask </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> drillholedia </td><td class="centeralign"> 1/100th mils </td><td class="centeralign"> dia. of hole </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> name </td><td class="centeralign"> string </td><td class="centeralign"> arb. pin name </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> number </td><td class="centeralign"> decimal integer </td><td class="centeralign"> pin number used by nets/rats </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> flags </td><td class="centeralign"> hex </td><td class="centeralign"> xxx </td><td class="rightalign"> </td>
+ </tr>
+</table>
+
+</div>
+<!-- SECTION "Broches" [6938-7639] -->
+<h2><a name="exemples" id="exemples">Exemples</a></h2>
+<div class="level2">
+<ul>
+<li class="level1"><div class="li"> <strong><code>Pad[-24606 14760 -19538 14760 1181 2000 3181 â??â?? â??16â?? â??squareâ??]</code></strong></div>
+</li>
+<li class="level1"><div class="li"> <strong><code>Pad[-14760 19538 -14760 24606 1181 2000 3181 â??â?? â??17â?? â??square,edge2â??]</code></strong></div>
+</li>
+<li class="level1"><div class="li"> <strong><code>Pin[0 0 12000 2000 12500 6400 â??â?? â??1â?? 0Ã?00000001]</code></strong></div>
+</li>
+<li class="level1"><div class="li"> <strong><code>ElementArc [0 0 6800 6800 0 360 1000]</code></strong></div>
+</li>
+<li class="level1"><div class="li"> <strong><code>ElementLine [-26696 -26696 26696 -26696 1000]</code></strong></div>
+</li>
+<li class="level1"><div class="li"> <strong><code># notes within PCB Footprints go after the pound sign</code></strong></div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Exemples" [7640-] --></body>
+</html>
diff --git a/docs/wiki/geda-pcb-quick_reference.html b/docs/wiki/geda-pcb-quick_reference.html
new file mode 100644
index 0000000..45ce5fd
--- /dev/null
+++ b/docs/wiki/geda-pcb-quick_reference.html
@@ -0,0 +1,453 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#pcbquick_reference" class="toc">PCB: Quick Reference</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#key_mapping" class="toc">Key Mapping</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#pcb_keystrokes" class="toc">PCB Keystrokes</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#viewport_keystrokes" class="toc">Viewport Keystrokes</a></span></div></li>
+</ul>
+</li>
+<li class="level1"><div class="li"><span class="li"><a href="#footprint_reference" class="toc">Footprint Reference</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#general_syntax" class="toc">General syntax</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#elements" class="toc">Elements</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#pads" class="toc">Pads</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#pins" class="toc">Pins</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#examples" class="toc">Examples</a></span></div></li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="pcbquick_reference" id="pcbquick_reference">PCB: Quick Reference</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "PCB: Quick Reference" [1-35] -->
+<h2><a name="key_mapping" id="key_mapping">Key Mapping</a></h2>
+<div class="level2">
+
+</div>
+<!-- SECTION "Key Mapping" [36-62] -->
+<h3><a name="pcb_keystrokes" id="pcb_keystrokes">PCB Keystrokes</a></h3>
+<div class="level3">
+<table class="inline">
+ <tr>
+ <th class="centeralign"> KEY </th><th class="leftalign"> MNEMONIC </th><th class="centeralign"> DESCRIPTION </th>
+ </tr>
+ <tr>
+ <td class="centeralign"> esc </td><td class="leftalign"> panner </td><td> enter panning mode </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> insert </td><td class="leftalign"> insert point </td><td> enter insert point mode. Click and drag on track to insert a point </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> space </td><td class="leftalign"> select </td><td class="leftalign"> enter select mode </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> tab </td><td class="leftalign"> flip view </td><td class="leftalign"> view: flip board </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> shift-del </td><td class="leftalign"> del-cu </td><td class="leftalign"> deletes connected copper (rats are considered a connection) </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> \ </td><td class="leftalign"> thin-draw </td><td class="leftalign"> toggles thin draw mode </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> shift-alt-a </td><td class="leftalign"> unselect </td><td class="leftalign"> clear selection </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> b </td><td class="leftalign"> to other side </td><td class="leftalign"> flip object to the other side of the board </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> shift-b </td><td class="leftalign"> flip view </td><td class="leftalign"> view: flip board </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> c </td><td class="leftalign"> center </td><td class="leftalign"> view: center display at cursor position </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> ctrl-c </td><td> copy to buffer</td><td class="leftalign"> copy selection to buffer and unselect </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> d </td><td class="leftalign"> display name </td><td class="leftalign"> display pin or pad name </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> shift-d </td><td class="leftalign"> pinout dialog </td><td class="leftalign"> open pinout window for element under mouse cursor </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> e </td><td> eliminate rats</td><td class="leftalign"> delete all rats </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> shift-e </td><td class="leftalign"> eliminate some rats </td><td class="leftalign"> delete selected rats </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> f </td><td class="leftalign"> find </td><td class="leftalign"> highlight connections to object under mouse cursor </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> shift-f </td><td class="leftalign"> un-find </td><td class="leftalign"> un-highlight found connections </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> g </td><td class="leftalign"> increase grid </td><td class="leftalign"> increment grid by configured grid increment </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> shift-g </td><td class="leftalign"> decrease grid </td><td class="leftalign"> decrement grid by configured grid increment </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> h </td><td class="leftalign"> hide </td><td class="leftalign"> toggle the visiblity of the refdes or value attached to the current component </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> ctrl-h </td><td class="leftalign"> holeplate </td><td class="leftalign"> toggle plating of a via. Used to produce non metalized mounting holes </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> j </td><td class="leftalign"> lineclear </td><td class="leftalign"> toggles line clears polygon </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> k </td><td class="leftalign"> klearance </td><td class="leftalign"> increment clearance (soldermask to copper edge) </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> shift-k </td><td class="leftalign"> klear (-) </td><td class="leftalign"> decrement clearance (soldermask to copper edge (NOTE: can go negative!)) </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> l </td><td class="leftalign"> increase line </td><td class="leftalign"> increment width of the line tool, adds to the settings of the current line style </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> shift-l </td><td class="leftalign"> decrease line </td><td> reduce the current linewidth </td>
+ </tr>
+ <tr>
+ <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="geda-pcb_tips.html#how_do_i_move_one_set_of_layer_tracks_to_another_layer" class="wikilink1" title="geda-pcb_tips.html">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>
+ </tr>
+ <tr>
+ <td class="centeralign"> n </td><td class="leftalign"> name </td><td> show object refdes / pin number at mouse pointer </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> shift-n </td><td class="leftalign"> next </td><td> Select the shortest unselected rat on the board </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> o </td><td class="leftalign"> optimize rats </td><td> optimize and redraw all rats </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> shift-o </td><td class="leftalign"> optimize some rats </td><td> optimize and redraw selected nets only </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> shift-p </td><td class="leftalign"> polygon close </td><td class="leftalign"> connect the first point of a polygon with the last </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> q </td><td class="leftalign"> square toggle </td><td class="leftalign"> toggle square/round corners on pads </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> ctrl-r </td><td class="leftalign"> report </td><td class="leftalign"> show object report </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> s </td><td class="leftalign"> solid-poly </td><td> toggles polygon-clear of lines and pins (compare: thermal) </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> s </td><td class="leftalign"> size </td><td class="leftalign"> increment size </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> shift-s </td><td class="leftalign"> size (-) </td><td class="leftalign"> decrement size </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> alt-s </td><td class="leftalign"> sizehole </td><td class="leftalign"> increase the hole size </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> alt-shift-s </td><td class="leftalign"> sizehole (-) </td><td class="leftalign"> decrease the hole size </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> ctrl-s </td><td class="leftalign"> sizehole </td><td class="leftalign"> increase the hole size </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> ctrl-shift-s </td><td class="leftalign"> sizehole (-) </td><td class="leftalign"> decrease the hole size </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> v </td><td class="leftalign"> view extents </td><td class="leftalign"> global view of working area </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> z </td><td class="leftalign"> zoom </td><td class="leftalign"> view: zoom in </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> shift-z </td><td class="leftalign"> un-zoom </td><td class="leftalign"> view: zoom out </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> F1 </td><td class="leftalign"> via </td><td> enter via tool </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> F2 </td><td class="leftalign"> line </td><td class="leftalign"> enter line tool </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> F3 </td><td class="leftalign"> arc </td><td> enter arc tool </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> F4 </td><td class="leftalign"> text </td><td> enter text tool </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> F5 </td><td class="leftalign"> rectangle </td><td> enter rectangle tool</td>
+ </tr>
+ <tr>
+ <td class="centeralign"> F6 </td><td class="leftalign"> polygon </td><td> enter polygon tool </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> F7 </td><td class="leftalign"> buffer </td><td> enter buffer mode </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> F8 </td><td class="leftalign"> delete </td><td> enter remove mode </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> F9 </td><td class="leftalign"> rotate </td><td class="leftalign"> enter rotate mode </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> F10 </td><td class="leftalign"> file menu </td><td> file menu </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> F11 </td><td class="leftalign"> select </td><td class="leftalign"> enter select mode (same as [space]) </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> F12 </td><td class="leftalign"> lock </td><td> enter lock mode </td>
+ </tr>
+</table>
+
+</div>
+<!-- SECTION "PCB Keystrokes" [63-3697] -->
+<h2><a name="viewport_keystrokes" id="viewport_keystrokes">Viewport Keystrokes</a></h2>
+<div class="level2">
+<table class="inline">
+ <tr>
+ <th class="centeralign"> KEY </th><th class="centeralign"> MNEMONIC </th><th class="centeralign"> DESCRIPTION </th>
+ </tr>
+ <tr>
+ <td class="centeralign"> esc </td><td class="centeralign"> panner </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> v </td><td class="centeralign"> view extents </td><td>global view of working area</td>
+ </tr>
+ <tr>
+ <td class="centeralign"> c </td><td class="centeralign"> center </td><td>centers view on cursor</td>
+ </tr>
+ <tr>
+ <td class="centeralign"> z </td><td class="centeralign"> zoom </td><td>zoom in</td>
+ </tr>
+ <tr>
+ <td class="centeralign"> shift-z </td><td class="centeralign"> un-zoom </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> \ </td><td class="centeralign"> thin-draw on/off </td><td>toggles thin draw mode</td>
+ </tr>
+ <tr>
+ <td class="centeralign"> tab </td><td class="centeralign"> flip view </td><td>flip board</td>
+ </tr>
+ <tr>
+ <td class="centeralign"> shift-b </td><td class="centeralign"> flip view </td><td>flip board</td>
+ </tr>
+</table>
+
+</div>
+<!-- SECTION "Viewport Keystrokes" [3698-4071] -->
+<h1><a name="footprint_reference" id="footprint_reference">Footprint Reference</a></h1>
+<div class="level1">
+
+<p>
+The Master document for footprint creation is the <a href="http://pcb.sourceforge.net/index.html#dir"; class="urlextern" title="http://pcb.sourceforge.net/index.html#dir"; rel="nofollow">PCB Manual</a>. There is also Stuart Brorsonâ??s <a href="http://www.brorson.com/gEDA/land_patterns_20050129.pdf"; class="urlextern" title="http://www.brorson.com/gEDA/land_patterns_20050129.pdf"; rel="nofollow">Footprint Creation for the Open-Source Layout Program PCB</a>.
+</p>
+
+</div>
+<!-- SECTION "Footprint Reference" [4072-4365] -->
+<h2><a name="general_syntax" id="general_syntax">General syntax</a></h2>
+<div class="level2">
+
+<p>
+A pcb footprint file may contain any of the following commands:
+</p>
+<ul>
+<li class="level1"><div class="li"> <strong><code>Element [element_flags, description, pcb-name, value, mark_x, mark_y, text_x, text_y, text_direction, text_scale, text_flags]</code></strong></div>
+</li>
+<li class="level1"><div class="li"> <strong><code>Pad [x1 y1 x2 y2 thickness clearance mask name pad_number flags]</code></strong></div>
+</li>
+<li class="level1"><div class="li"> <strong><code>Pin [x y thickness clearance mask drillholedia name number flags]</code></strong></div>
+</li>
+<li class="level1"><div class="li"> <strong><code>ElementArc [x y r1 r2 startangle sweepangle thickness]</code></strong></div>
+</li>
+<li class="level1"><div class="li"> <strong><code>ElementLine [x1 y1 x2 y2 thickness] â??> thickness != 1000 = 10 mils almost for all footprints</code></strong></div>
+</li>
+<li class="level1"><div class="li"> Comment lines start with the â??<strong><code>#</code></strong>â??-sign</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "General syntax" [4366-4978] -->
+<h2><a name="elements" id="elements">Elements</a></h2>
+<div class="level2">
+
+<p>
+<strong><code>Element [element_flags, description, pcb-name, value, mark_x, mark_y, text_x, text_y, text_direction, text_scale, text_flags]</code></strong>
+</p>
+<table class="inline">
+ <tr>
+ <th class="centeralign"> item </th><th class="centeralign"> allowed value </th><th class="centeralign"> explanation </th><th class="centeralign"> comment </th>
+ </tr>
+ <tr>
+ <td class="centeralign"> element_flags </td><td class="centeralign"> unsigned hex value </td><td class="rightalign"> </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> description </td><td class="centeralign"> string </td><td class="centeralign"> text description of footprint </td><td class="leftalign">written by footprint author </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> pcb name </td><td class="centeralign"> string </td><td class="centeralign"> refdes used on this particular pcb </td><td class="leftalign">xxx </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> value </td><td class="centeralign"> string </td><td class="centeralign"> value of component on this particular pcb layout </td><td class="leftalign">xxx </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> mark_x </td><td class="centeralign"> 1/100th mils </td><td class="rightalign"> </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> mark_y </td><td class="centeralign"> 1/100th mils </td><td class="rightalign"> </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> text_x </td><td class="centeralign"> 1/100th mils </td><td class="rightalign"> </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> text_y </td><td class="centeralign"> 1/100th mils </td><td class="rightalign"> </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> text direction </td><td class="centeralign"> decimal integer </td><td class="centeralign"> 0=horiz; 1=ccw90; 2=180; 3=cw90 </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> text_scale </td><td class="centeralign"> decimal integer </td><td class="rightalign"> </td><td class="leftalign">usu. set 100 </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> text_flags </td><td class="centeralign"> unsigned hex </td><td class="rightalign"> </td><td class="rightalign"> </td>
+ </tr>
+</table>
+
+</div>
+<!-- SECTION "Elements" [4979-5806] -->
+<h2><a name="pads" id="pads">Pads</a></h2>
+<div class="level2">
+
+<p>
+<strong><code>Pad[x1 y1 x2 y2 thickness clearance mask name pad_number flags]</code></strong>
+</p>
+<table class="inline">
+ <tr>
+ <th class="centeralign"> Item </th><th class="centeralign"> Allowed Value </th><th class="centeralign"> Explanation </th><th class="centeralign"> Comment </th>
+ </tr>
+ <tr>
+ <td class="centeralign"> x1 </td><td class="centeralign"> 1/100th mils </td><td class="centeralign"> x(1st point) </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> y1 </td><td class="centeralign"> 1/100th mils </td><td class="centeralign"> y(1st point) </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> x2 </td><td class="centeralign"> 1/100th mils </td><td class="centeralign"> x(2nd point) </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> y2 </td><td class="centeralign"> 1/100th mils </td><td class="centeralign"> y(2nd point) </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> thickness </td><td class="centeralign"> 1/100 mils </td><td class="centeralign"> width of metal surrounding line segment </td><td class="leftalign">see Brorson .pdf </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> clearance </td><td class="centeralign"> 1/100 mils </td><td class="centeralign"> distance to any other copper on any layer </td><td class="leftalign">actually 1/2 of this number is used! </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> mask </td><td class="centeralign"> 1/100th mils </td><td class="centeralign"> width of mask relief </td><td class="leftalign">actual width of the mask centered on pad copper </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> name </td><td class="centeralign"> string </td><td class="centeralign"> name of pad (arb. string) </td><td class="leftalign">e.g. â??pad_1â?? or â??positiveâ?? or any other string </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> pad_number </td><td class="centeralign"> string </td><td class="centeralign"> pad # </td><td class="leftalign">used for nets. it MUST be consistent with the definitions on the netlist. </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> flags </td><td class="centeralign"> hex value </td><td class="centeralign"> xxx </td><td class="rightalign"> </td>
+ </tr>
+</table>
+
+</div>
+<!-- SECTION "Pads" [5807-6711] -->
+<h2><a name="pins" id="pins">Pins</a></h2>
+<div class="level2">
+
+<p>
+<strong><code>Pin[x y thickness clearance mask drillholedia name number flags]</code></strong>
+</p>
+<table class="inline">
+ <tr>
+ <th class="centeralign"> Item </th><th class="leftalign"> Allowed Value </th><th class="centeralign"> Explanation </th><th class="centeralign"> Comment </th>
+ </tr>
+ <tr>
+ <td class="centeralign"> x </td><td class="centeralign"> 1/100th mils </td><td class="centeralign"> pin x coord. </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> y </td><td class="centeralign"> 1/100th mils </td><td class="centeralign"> pin y coord. </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> thickness </td><td class="centeralign"> 1/100th mils </td><td class="centeralign"> copper diameter </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> clearance </td><td class="centeralign"> 1/100th mils </td><td class="centeralign"> 2*(cu to cu clearance) </td><td class="leftalign">if you want a 10 mil clearance, put 2000 (20 mils) here </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> mask </td><td class="centeralign"> 1/100th mils </td><td class="centeralign"> diameter of mask aperture </td><td class="leftalign">actual dia. of hole in mask </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> drillholedia </td><td class="centeralign"> 1/100th mils </td><td class="centeralign"> dia. of hole </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> name </td><td class="centeralign"> string </td><td class="centeralign"> arb. pin name </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> number </td><td class="centeralign"> decimal integer </td><td class="centeralign"> pin number used by nets/rats </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="centeralign"> flags </td><td class="centeralign"> hex </td><td class="centeralign"> xxx </td><td class="rightalign"> </td>
+ </tr>
+</table>
+
+</div>
+<!-- SECTION "Pins" [6712-7410] -->
+<h2><a name="examples" id="examples">Examples</a></h2>
+<div class="level2">
+<ul>
+<li class="level1"><div class="li"> <strong><code>Pad[-24606 14760 -19538 14760 1181 2000 3181 â??â?? â??16â?? â??squareâ??]</code></strong></div>
+</li>
+<li class="level1"><div class="li"> <strong><code>Pad[-14760 19538 -14760 24606 1181 2000 3181 â??â?? â??17â?? â??square,edge2â??]</code></strong></div>
+</li>
+<li class="level1"><div class="li"> <strong><code>Pin[0 0 12000 2000 12500 6400 â??â?? â??1â?? 0Ã?00000001]</code></strong></div>
+</li>
+<li class="level1"><div class="li"> <strong><code>ElementArc [0 0 6800 6800 0 360 1000]</code></strong></div>
+</li>
+<li class="level1"><div class="li"> <strong><code>ElementLine [-26696 -26696 26696 -26696 1000]</code></strong></div>
+</li>
+<li class="level1"><div class="li"> <strong><code># notes within PCB Footprints go after the pound sign</code></strong></div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Examples" [7411-] --></body>
+</html>
diff --git a/docs/wiki/geda-pcb_footprints.html b/docs/wiki/geda-pcb_footprints.html
new file mode 100644
index 0000000..d2339a6
--- /dev/null
+++ b/docs/wiki/geda-pcb_footprints.html
@@ -0,0 +1,164 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#pcb_footprint_guide" class="toc">PCB Footprint Guide</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#using_pcb_footprints" class="toc">Using PCB Footprints</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#creating_pcb_footprints" class="toc">Creating PCB Footprints</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#footprint_basics" class="toc">Footprint basics</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#pcb_footprint_faq" class="toc">PCB Footprint FAQ</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#sharing_pcb_footprints" class="toc">Sharing PCB Footprints</a></span></div></li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="pcb_footprint_guide" id="pcb_footprint_guide">PCB Footprint Guide</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "PCB Footprint Guide" [3-37] -->
+<h2><a name="using_pcb_footprints" id="using_pcb_footprints">Using PCB Footprints</a></h2>
+<div class="level2">
+
+</div>
+<!-- SECTION "Using PCB Footprints" [38-71] -->
+<h2><a name="creating_pcb_footprints" id="creating_pcb_footprints">Creating PCB Footprints</a></h2>
+<div class="level2">
+
+<p>
+<strong>This page is redundant!!! see <a href="geda-pcb_tips.html" class="wikilink1" title="geda-pcb_tips.html">pcb_tips</a>. Furthermore, there is no better way to understand the inner workings of footprints than the pdf <em>Footprint Creation for the Open-Source Layout Program â??PCBâ??</em></strong><a href="http://brorson.com/gEDA/land_patterns_20070818.pdf"; class="urlextern" title="http://brorson.com/gEDA/land_patterns_20070818.pdf"; rel="nofollow">http://brorson.com/gEDA/land_patterns_20070818.pdf</a>
+</p>
+
+</div>
+<!-- SECTION "Creating PCB Footprints" [72-375] -->
+<h3><a name="footprint_basics" id="footprint_basics">Footprint basics</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> There are two types of footprints: M4 and NEWLIB.</div>
+</li>
+<li class="level1"><div class="li"> The best tools for creating footprints are PCB (wysiwyg), TEXT EDITOR (fast, accurate), SCRIPTING (powerful).</div>
+</li>
+<li class="level1"><div class="li"> For drawing footprints in PCB, refer to:</div>
+</li>
+<li class="level1"><div class="li"> For writing footprints in text, refer to: " <em>Footprint Creation for the Open-Source Layout Program â??PCBâ??</em> written and maintained by Stuart Brorson</div>
+</li>
+<li class="level1"><div class="li"> For Scripting footprints:</div>
+</li>
+<li class="level1"><div class="li"> Other things you may find helpful: calculator, paper+pencil, datasheets, calipers, spreadsheet.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Footprint basics" [376-906] -->
+<h3><a name="pcb_footprint_faq" id="pcb_footprint_faq">PCB Footprint FAQ</a></h3>
+<div class="level3">
+
+</div>
+
+<h4><a name="what_is_the_footprint_naming_convention" id="what_is_the_footprint_naming_convention">What is the Footprint naming Convention ?</a></h4>
+<div class="level4">
+
+</div>
+
+<h4><a name="can_i_have_two_pads_pins_with_the_same_pin-number" id="can_i_have_two_pads_pins_with_the_same_pin-number">Can I have two pads/pins with the same pin-number?</a></h4>
+<div class="level4">
+
+<p>
+â??Yes, totally. This is how you create oval shaped copper around pins, or funny shaped pads (e.g. square at one end and round at the other) by overlapping two or more pads."
+</p>
+
+</div>
+
+<h4><a name="how_do_i_make_an_oval_shaped_pad_around_a_footprint_pin" id="how_do_i_make_an_oval_shaped_pad_around_a_footprint_pin">How do I make an oval shaped pad around a footprint pin?</a></h4>
+<div class="level4">
+
+<p>
+Simply add a pad on top of your pin and give them the same pin-number. If the soldermask is kept off both pins, and they overlap, they should appear as one pin on your board.
+</p>
+
+</div>
+
+<h4><a name="how_do_i_make_a_2-sided_pad" id="how_do_i_make_a_2-sided_pad">How do I make a 2-sided pad?</a></h4>
+<div class="level4">
+
+<p>
+â??Odd as it sounds, this can be necessary for some edge connectors. … but how do you do it???"
+</p>
+
+</div>
+
+<h4><a name="edge_connectors" id="edge_connectors">Edge Connectors</a></h4>
+<div class="level4">
+
+</div>
+
+<h4><a name="what_are_some_references_for_making_surface_mount_pads_and_footprints" id="what_are_some_references_for_making_surface_mount_pads_and_footprints">What are some references for making surface mount pads and footprints?</a></h4>
+<div class="level4">
+<ul>
+<li class="level1"><div class="li"> <a href="http://www.nxp.com/package"; class="urlextern" title="http://www.nxp.com/package"; rel="nofollow">http://www.nxp.com/package</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="http://focus.ti.com/general/docs/packaging.jsp"; class="urlextern" title="http://focus.ti.com/general/docs/packaging.jsp"; rel="nofollow">http://focus.ti.com/general/docs/packaging.jsp</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="http://www.maxim-ic.com/design/packaging/"; class="urlextern" title="http://www.maxim-ic.com/design/packaging/"; rel="nofollow">http://www.maxim-ic.com/design/packaging/</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="http://www.national.com/packaging/folders/pkg_index.html"; class="urlextern" title="http://www.national.com/packaging/folders/pkg_index.html"; rel="nofollow">http://www.national.com/packaging/folders/pkg_index.html</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="http://www.irf.com/package/"; class="urlextern" title="http://www.irf.com/package/"; rel="nofollow">http://www.irf.com/package/</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="http://www.onsemi.com/PowerSolutions/supportTechDoc.do?id=1165"; class="urlextern" title="http://www.onsemi.com/PowerSolutions/supportTechDoc.do?id=1165"; rel="nofollow">http://www.onsemi.com/PowerSolutions/supportTechDoc.do?id=1165</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="http://www.analog.com/Analog_Root/Packages/Packages_Home/"; class="urlextern" title="http://www.analog.com/Analog_Root/Packages/Packages_Home/"; rel="nofollow">http://www.analog.com/Analog_Root/Packages/Packages_Home/</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="http://www.linear.com/designtools/PkgInfo.jsp"; class="urlextern" title="http://www.linear.com/designtools/PkgInfo.jsp"; rel="nofollow">http://www.linear.com/designtools/PkgInfo.jsp</a></div>
+</li>
+</ul>
+
+<p>
+ <a href="geda-pcb_tips.html" class="wikilink1" title="geda-pcb_tips.html">pcb_tips</a> covers a lot of Footprint material. This page and that page need to be reconciled!
+</p>
+
+</div>
+<!-- SECTION "PCB Footprint FAQ" [907-2204] -->
+<h2><a name="sharing_pcb_footprints" id="sharing_pcb_footprints">Sharing PCB Footprints</a></h2>
+<div class="level2">
+
+</div>
+
+<h5><a name="popular_sources_of_footprints" id="popular_sources_of_footprints">Popular Sources of Footprints</a></h5>
+<div class="level5">
+
+<p>
+ * The place to share symbols and footprints is <a href="http://www.gedasymbols.org"; class="urlextern" title="http://www.gedasymbols.org"; rel="nofollow"> gedasymbols.org</a>
+</p>
+
+<p>
+* You can find many PCB footprints at <a href="http://www.luciani.org/geda/pcb/pcb-footprint-list.html"; class="urlextern" title="http://www.luciani.org/geda/pcb/pcb-footprint-list.html"; rel="nofollow">John Luciani's footprint page</a>
+</p>
+
+<p>
+* You can share <a href="http://opencircuits.com/PCB_Footprints"; class="urlextern" title="http://opencircuits.com/PCB_Footprints"; rel="nofollow"> gEDA footprints at Open Circuits</a>.
+</p>
+
+</div>
+<!-- SECTION "Sharing PCB Footprints" [2205-] --></body>
+</html>
diff --git a/docs/wiki/geda-pcb_funding_sow-fwdann_ideas.html b/docs/wiki/geda-pcb_funding_sow-fwdann_ideas.html
new file mode 100644
index 0000000..e15c265
--- /dev/null
+++ b/docs/wiki/geda-pcb_funding_sow-fwdann_ideas.html
@@ -0,0 +1,64 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+<a href=.>start</a> => <a href=geda-pcb_funding_sow.html>pcb_funding_sow</a></br>
+
+
+
+<h1><a name="pcb_sowforward_annotationideas_commentary_and_examples_from_users" id="pcb_sowforward_annotationideas_commentary_and_examples_from_users">PCB SoW: Forward Annotation: Ideas, commentary, and examples from users</a></h1>
+<div class="level1">
+
+<p>
+ <em>Anyone with any ideas or commentary about how this task should be completed may add
+them here. Ideas about the details behind the implementation, too. Please refrain from deleting or significantly changing the meaning of someone elseâ??s entry.</em>
+</p>
+
+</div>
+<!-- SECTION "PCB SoW: Forward Annotation: Ideas, commentary, and examples from users" [1-337] -->
+<h2><a name="dj_s_implementation_ideas" id="dj_s_implementation_ideas">DJ's Implementation Ideas</a></h2>
+<div class="level2">
+
+<p>
+This is what Iâ??m thinking for the forward annotation (gsch2pcb) design:
+</p>
+
+<p>
+The PCB has a list of schematics that it gets info from. Do we need path support, or is full-paths (or relative to the pcb) ok? Wildcards? Anyway, the list of schematics is stored in the .pcb file somehow. The <acronym title="Graphical User Interface">GUI</acronym> needs a way to manage these, too.
+</p>
+
+<p>
+When the user asks, PCB uses the list of schematics to run a gnetlist command with my new backend, passing the list of schematics. The gnetlist spits out a list of actions, which pcb runs. These actions update the netlist, add any missing elements, and remove any appropriate elements. Elements which need new footprints are updated (magically! in place! we hope ;).
+</p>
+
+<p>
+Also, some additional attributes will be propogated to elements, like vendor, vendor_part_number, etc.
+</p>
+
+<p>
+If the import is part of a â??new boardâ?? step, we place the parts and disperse them, optimize the rats nest, etc. No problem there.
+</p>
+
+<p>
+What do we do with new elements if itâ??s just an update? Eventually, Iâ??d like to have some separate container for â??unplaced elementsâ?? but I mean, what do we do for now? Iâ??m wondering if disperse or autoplace is smart enough to do something useful if we place the parts and select them, on a partially laid out board.
+</p>
+
+<p>
+I think this is enough information in the .pcb file that we can get rid of gsch2pcb and the â??projectâ?? file it uses.
+</p>
+
+<p>
+It does mean that the pcb cares which schematics go with it, but the schematics donâ??t care which pcb they go with. Schematics can be reused/shared, boards generally canâ??t.
+</p>
+
+</div>
+<!-- SECTION "DJ's Implementation Ideas" [338-] --></body>
+</html>
diff --git a/docs/wiki/geda-pcb_funding_sow-gui_ideas.html b/docs/wiki/geda-pcb_funding_sow-gui_ideas.html
new file mode 100644
index 0000000..7fc3e5e
--- /dev/null
+++ b/docs/wiki/geda-pcb_funding_sow-gui_ideas.html
@@ -0,0 +1,35 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+<a href=.>start</a> => <a href=geda-pcb_funding_sow.html>pcb_funding_sow</a></br>
+
+
+
+<h1><a name="pcb_sowgui_enhancementideas_commentary_and_examples_from_users" id="pcb_sowgui_enhancementideas_commentary_and_examples_from_users">PCB SoW: GUI Enhancement: Ideas, commentary, and examples from users</a></h1>
+<div class="level1">
+
+<p>
+ <em>Anyone with any ideas or commentary about how this task should be completed may add
+them here. Ideas about the details behind the implementation, too. Please refrain from deleting or significantly changing the meaning of someone elseâ??s entry.</em>
+</p>
+
+<p>
+Currently, we either enable or disable categories of objects (like vias). Perhaps an intermediate setting that either outlines it or draws is translucently, so that things below it can be selected while still being able to see and interact with the above things? Example: with rubberband set, youâ??d still want to be able to snap to the line endings beneath it, yet move the via along with the lines.
+</p>
+
+<p>
+When you hover over a track, the netname should be displayed in the status line.
+</p>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-pcb_funding_sow.html b/docs/wiki/geda-pcb_funding_sow.html
new file mode 100644
index 0000000..8e933ee
--- /dev/null
+++ b/docs/wiki/geda-pcb_funding_sow.html
@@ -0,0 +1,844 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#background_and_motivation" class="toc">Background and motivation</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#statement_of_work" class="toc">Statement of work</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#general_guidelines" class="toc">General guidelines</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#forward_annotation_upgrade" class="toc">Forward annotation upgrade</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#gui_modernization" class="toc">GUI modernization</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#footprint_editor_implementation" class="toc">Footprint editor implementation</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#upgrade_of_layer_and_design_objects" class="toc">Upgrade of layer and design objects</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#design_rule_checking_upgrade" class="toc">Design Rule Checking Upgrade</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#project_milestones_duration_and_budget_estimates" class="toc">Project milestones, duration, and budget estimates</a></span></div></li></ul>
+</li></ul>
+</li></ul>
+</div>
+</div>
+
+<p>
+<strong>Statement of work: Improving PCBâ??s usability within the gEDA Suite framework</strong>
+</p>
+
+
+
+<h2><a name="background_and_motivation" id="background_and_motivation">Background and motivation</a></h2>
+<div class="level2">
+
+<p>
+The open-source layout tool <a href="http://pcb.sourceforge.net/"; class="urlextern" title="http://pcb.sourceforge.net/"; rel="nofollow">PCB</a> has been a member of the gEDA Project for many years. It is an essential part of the end-to-end design flow offered by the gEDA tool set. That is, although gschem/gnetlist can (in principle) support many back-end PCB layout tools, the most advanced forward annotation tools have been developed for PCB, and the vast majority (if not all) of the gEDA Projectâ??s user base uses PCB as their layout tool. PCB is a core part of the gEDA Projectâ??s software offerings.
+</p>
+
+<p>
+For a variety of reasons, many electronics designers find PCBâ??s user interface difficult to master. Many tasks are best performed using PCBâ??s internal command line (instead of menus or buttons), dropping to the unix shell, or even hand-editing design files using scripts or emacs. Some specific shortcomings of PCB have been widely noted on the geda-* e-mail lists, along with reasonable solutions. A list of the biggest issues includes:
+</p>
+<ul>
+<li class="level1"><div class="li"> <strong>Forward annotation:</strong> Difficulty forward annotating designs from gschem/gnetlist. A separate command-line tool is used to carry the design from gschem to PCB. This tool can produce design files out of synch with PCB. Also, many electronics designers are unfamiliar with using the unix command line.</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> <strong><acronym title="Graphical User Interface">GUI</acronym>:</strong> PCBâ??s <acronym title="Graphical User Interface">GUI</acronym> shows its age. It has the following infelicitous properties:</div>
+<ul>
+<li class="level2"><div class="li"> It uses a mixture of noun/verb and verb/noun actions. (Modern <acronym title="Graphical User Interface">GUI</acronym> programs are noun/verb only.)</div>
+</li>
+<li class="level2"><div class="li"> Incomplete menu/button coverage of possible editing actions. For example, arbitrary rotation and component refdes renumbering are available only through the pop-up command entry window.</div>
+</li>
+<li class="level2"><div class="li"> There is a lack of <acronym title="Graphical User Interface">GUI</acronym> controls for exact, CAD-like editing. Examples for these desirable actions: Give the position of an object by typing its coordinates. Rotate an object by a given angle. Move objects by an exact amount. Do a multi copy of objects.</div>
+</li>
+<li class="level2"><div class="li"> Unlike many other graphical GUIs a dialog to edit properties of an object is missing in pcb. Properties to be edited might be layer, thickness, connected flag, polygon clearance, the net it belongs to, position, orientation, etc.</div>
+</li>
+<li class="level2"><div class="li"> Underlying the user interface, there is strong belief amongst PCBâ??s developers that the supporting datastructures and methods are inadequate, and require upgrade as part of any <acronym title="Graphical User Interface">GUI</acronym> upgrade.</div>
+</li>
+</ul>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> <strong>Footprint creation/editing:</strong> Creating/editing footprints using PCB is difficult. Most power users have created perl scripts to automate this process, but new users tend to be flummoxed by this approach.</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> <strong>Layers and design objects:</strong> Although PCB can handle any arbitrary number of metal layers, it does not fully support other design layers as independent objects. For example, it lacks full support for common layout layers like: keepout, DRC, outline, etc. Also, the concept of padstacks is missing from PCB. Finally, PCB does not provide the full DRC functionality expected of a modern layout program.</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> <strong>DRC:</strong> The existing mechanism to find DRCs is clumsy. Also, a separate DRC layer which may be turned on or off (typical of modern layout programs) is missing.</div>
+</li>
+</ul>
+
+<p>
+ We envision that addressing the above problems will provide a significant, powerful benefit to PCBâ??s usability within the larger framework of the gEDA toolkit. Addressing the usability issues will bring the following specific benefits to the gEDA Project:
+</p>
+<ul>
+<li class="level1"><div class="li"> <strong>Adoption:</strong> Making PCB easier to use will lead to greater uptake of the entire gEDA electronic design toolkit by practicing engineers, including those working in commercial organizations.</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> <strong>Contribution:</strong> More users implies more contributors. In the context of the gEDA Project, this means not only software developers, but also people who will contribute schematic symbols, PCB footprints, utility scripts, and other collateral necessary to a thriving design environment. (A strong focal point for contributors is – and will remain – the <a href="http://www.gedasymbols.org"; class="urlextern" title="http://www.gedasymbols.org"; rel="nofollow">www.gedasymbols.org</a> website.)</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> <strong>Support:</strong> Engineers using the gEDA tools in a company context might be positioned to help organize funding for ongoing development of the gEDA Suite, thereby closing the circle from developers to users back to developers. This would go a long way towards raising the gEDA Project above its current â??advanced hobby hackerâ?? status, a beneficial result for the entire gEDA ecosystem.</div>
+</li>
+</ul>
+
+<p>
+ Therefore, the purpose of this document is to specify modifications to PCB which we hope will bring about a renaissance in the gEDA Project itself by making the critical tool PCB more accessible to the ordinary electronics engineer.
+</p>
+
+</div>
+<!-- SECTION "Background and motivation" [86-4750] -->
+<h2><a name="statement_of_work" id="statement_of_work">Statement of work</a></h2>
+<div class="level2">
+
+<p>
+This section provides descriptions of what work is desired in each area of PCBâ??s functionality. This is not a full specification; it is assumed that the person chosen to perform this work is familiar enough with the concepts associated with PCB design and the internals of PCB that this statement of work provides sufficient guidance about what to do.
+</p>
+<hr />
+
+</div>
+<!-- SECTION "Statement of work" [4751-5140] -->
+<h3><a name="general_guidelines" id="general_guidelines">General guidelines</a></h3>
+<div class="level3">
+
+</div>
+
+<h4><a name="gtk_hid" id="gtk_hid">GTK HID</a></h4>
+<div class="level4">
+
+<p>
+PCB supports several HIDs. The HID is the interface layer which the user interacts with. The two major HIDs provided for interactive use are based upon 1) the GTK <acronym title="Graphical User Interface">GUI</acronym> widget set, and 2) The X/Motif <acronym title="Graphical User Interface">GUI</acronym> widget set. <strong>The work called out for this project shall be targeted at the GTK HID.</strong> The reason for this is simple: The rest of gEDA uses GTK. A primary goal the renovation work in PCB is to more tightly bind PCB into the entire gEDA workflow. More to the point: the gEDA tool chain should present a more uniform interface to the user. Users expect to see the same â??look and feelâ?? in all the tools they use. However, any changes made as part of this work shall not break any feature present in any other HID, including the Motif HID.
+</p>
+
+</div>
+
+<h4><a name="code_clarity" id="code_clarity">Code clarity</a></h4>
+<div class="level4">
+
+<p>
+Many other changes are desirable in PCB. However, they are outside the scope of this work. The idea behind the changes specified here is that they create a launching point for other developers to come in afterward and continue improving PCB. Therefore, <strong>the developer must strive to make his code clear and well commented.</strong> Do not use hard to understand code tricks, obfuscating macros, or other devices which will hamper any follow-on work by other developers.
+</p>
+
+</div>
+
+<h4><a name="doxygen" id="doxygen">Doxygen</a></h4>
+<div class="level4">
+
+<p>
+The developer should place Doxygen comments into the header of any new function he writes. Fully doxygenating PCB is outside the scope of this project, but <strong>the developer should at least use doxygen for the changes he makes.</strong>
+</p>
+
+</div>
+
+<h4><a name="platforms" id="platforms">Platforms</a></h4>
+<div class="level4">
+
+<p>
+The upgrades to PCB must work on the usual platforms supported by the gEDA Project. Specifically:
+</p>
+<ul>
+<li class="level1"><div class="li"> Linux, BSD, Sun.</div>
+</li>
+<li class="level1"><div class="li"> GTK version 2.8 or later (consistent with gschem 1.5 head).</div>
+</li>
+</ul>
+
+<p>
+Hooks for support on Windows systems are outside the scope of this project. However, any Windows features present currently in PCB should not break as a result of these changes.
+</p>
+
+</div>
+
+<h4><a name="backwards_compatibility" id="backwards_compatibility">Backwards compatibility</a></h4>
+<div class="level4">
+
+<p>
+<strong>Any changes made to PCB should not break the ability of PCB to import existing
+.pcb files.</strong> It <strong>is</strong> allowed to break import of .new.pcb files (i.e. the output of gsch2pcb).
+</p>
+<hr />
+
+</div>
+<!-- SECTION "General guidelines" [5141-7262] -->
+<h3><a name="forward_annotation_upgrade" id="forward_annotation_upgrade">Forward annotation upgrade</a></h3>
+<div class="level3">
+
+<p>
+ <a href="geda-pcb_funding_sow-fwdann_ideas.html" class="wikilink1" title="geda-pcb_funding_sow-fwdann_ideas.html">Ideas, commentary, and examples from users</a>
+</p>
+
+</div>
+
+<h4><a name="feature_description" id="feature_description">Feature description</a></h4>
+<div class="level4">
+
+<p>
+The goal of forward annotation is to read the design information output from e.g. a netlister, and use it to import all information required into PCB, ready for use in creating or modifying a layout. Reading the following information is a required part of creating a PCB layout:
+</p>
+<ul>
+<li class="level1"><div class="li"> Footprints with associated refdeses and their associated layers (if assigned).</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> Graphical elements (pads, tracks, polygons, holes, etc) (usually imported from a previous design iteration).</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> Electronic connectivity (netlist).</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> Any global design information such as routing constraints. (Currently unsupported by PCB).</div>
+</li>
+</ul>
+
+<p>
+ The scheme currently used by PCB is to read a file – already in PCB format – containing the actual footprints embedded within it. The netlist is read in using a separate step.
+</p>
+
+<p>
+The new scheme would read a file containing a list of actions. Each line in the file would correspond to a separate action. The file would be generated by a forward annotation tool (e.g. gsch2pcb). The actions would correspond to the atomic actions performed by PCB itself when it finds a footprint by searching its footprint library.
+</p>
+
+<p>
+For example, one line in the forward annotation file might say â??(load-element-data SOT-23 U6)â??. This would make PCB look for an SOT-23 package in its footprint library (using PCBâ??s $FOOTPRINT_PATH), place it in a waiting position on the PCB, and give it the refdes â??U6â??. Another action might say â??(add-line <layer> <X1> <Y1> <X2> <Y2> <width> <flags>)â??, which would add a straight line segment onto layer <layer> from position (X1, Y1) to position (X2, Y2) having width <width> and flags <flags>. (The flags would specify things like whether the line ends are round or square, along with the other properties of a line.)
+</p>
+
+<p>
+Besides importing footprint and graphical information, the new PCB forward annotation facility should import the netlist at the same time as the rest of the layout information. (This is currently a separate step, which is inconsistent with the goal of ease-of-use.)
+</p>
+
+<p>
+Note that the above descriptions of the actions are meant to provide examples of how PCB should be modified. The details of each action are to be determined by the developer and the architecture of PCB itself.
+</p>
+
+</div>
+
+<h4><a name="use_cases" id="use_cases">Use cases</a></h4>
+<div class="level4">
+
+<p>
+Once the forward annotation changes are complete, the following use cases should apply:
+</p>
+
+<p>
+<strong>New PCB</strong>
+</p>
+<ol>
+<li class="level1"><div class="li"> The user creates his design using gschem. </div>
+</li>
+<li class="level1"><div class="li"> He creates a forward annotation file by running the .sch files through gsch2pcb, which creates a single .pfa (PCB forward annotation) file.</div>
+</li>
+<li class="level1"><div class="li"> The user starts PCB.</div>
+</li>
+<li class="level1"><div class="li"> He clicks â??File → new PCBâ??. A window pops up, providing a place to enter the new boardâ??s layer count and size. The window may also provide a way to specify common board templates (PC-104, 3U Eurocard, etc.)</div>
+</li>
+<li class="level1"><div class="li"> The new board is shown in PCBâ??s main window as a white area on a darker background (as currently implemented).</div>
+</li>
+<li class="level1"><div class="li"> The user clicks â??File → Import forward annotation fileâ??.</div>
+</li>
+<li class="level1"><div class="li"> A file selection window pops up. The user clicks on his .pfa file and clicks OK.</div>
+</li>
+<li class="level1"><div class="li"> PCB reads each action in the forward annotation file, and does the corresponding thing. </div>
+</li>
+<li class="level1"><div class="li"> The PCB netlist is also imported during this activity. No separate netlist readin step is required.</div>
+</li>
+<li class="level1"><div class="li"> At the end of the fileâ??s read-in, the footprints should be present on the board (*not* in the paste buffer), ready to be disbursed and placed.</div>
+</li>
+</ol>
+
+<p>
+ <strong>Existing PCB</strong>
+</p>
+<ol>
+<li class="level1"><div class="li"> The user has a pre-existing .pcb file for the design under consideration. He makes changes to his design using e.g. gschem or gattrib. </div>
+</li>
+<li class="level1"><div class="li"> The creates a forward annotation file by running the .sch files through gsch2pcb, which creates a single .pfa (PCB forward annotation) file. </div>
+</li>
+<li class="level1"><div class="li"> The user starts PCB (or re-activates an existing PCB session running in its window).</div>
+</li>
+<li class="level1"><div class="li"> The user clicks â??File → Import forward annotation fileâ??.</div>
+</li>
+<li class="level1"><div class="li"> A file selection window pops up. The user clicks on his .pfa file and clicks OK.</div>
+</li>
+<li class="level1"><div class="li"> PCB reads each action in the forward annotation file, and does the corresponding thing. Using the refdes, the importer looks to see if the component in the forward annotation file is already placed in PCB, and if so, it ignores the action. </div>
+</li>
+<li class="level1"><div class="li"> The netlist is also read in and updated at this stage. No separate netlist readin step is required.</div>
+</li>
+<li class="level1"><div class="li"> Once this action is complete, the user is ready to continue editing his board. </div>
+</li>
+</ol>
+
+</div>
+
+<h4><a name="other_ideas" id="other_ideas">Other Ideas</a></h4>
+<div class="level4">
+<ul>
+<li class="level1"><div class="li"> Besides a menu option, there should be a toolbar button to sync changes</div>
+</li>
+<li class="level1"><div class="li"> Alternately, a thread running a file change monitor can spot the new annotation file when it appears</div>
+</li>
+<li class="level1"><div class="li"> Finally, the project manager (gsch2pcb / xgsch2pcb / geda_manager) can invoke readin of a forward annotation file via IPC</div>
+</li>
+</ul>
+
+</div>
+
+<h4><a name="work_required" id="work_required">Work required</a></h4>
+<div class="level4">
+
+<p>
+Some of the support for forward annotation already exists. Specifically, many actions are already supported. Therefore, this project involves:
+</p>
+<ol>
+<li class="level1"><div class="li"> Creating the missing actions required for full forward annotation.</div>
+</li>
+<li class="level1"><div class="li"> Creating a method for reading in an action script.</div>
+</li>
+<li class="level1"><div class="li"> Integrating the new script-based forward annotation into PCBâ??s <acronym title="Graphical User Interface">GUI</acronym>.</div>
+</li>
+<li class="level1"><div class="li"> Testing and bug cleanup.</div>
+</li>
+</ol>
+<hr />
+
+</div>
+<!-- SECTION "Forward annotation upgrade" [7263-12536] -->
+<h3><a name="gui_modernization" id="gui_modernization">GUI modernization</a></h3>
+<div class="level3">
+
+<p>
+ <a href="geda-pcb_funding_sow-gui_ideas.html" class="wikilink1" title="geda-pcb_funding_sow-gui_ideas.html">Ideas, commentary, and examples from users</a>
+</p>
+
+<p>
+The basic goal is to make the upgraded PCB behave exactly as an inexperienced user might expect, based upon his familiarity with modern <acronym title="Graphical User Interface">GUI</acronym>-based tools like OpenOffice. This means:
+</p>
+<ul>
+<li class="level1"><div class="li"> PCB should support all the â??normalâ?? keystrokes which have become defacto standards for <acronym title="Graphical User Interface">GUI</acronym> programs. Examples include <ctrl>-c for copy, <ctrl>-x for delete, etc. PCB may continue to support the old key strokes to maintain backward compatibility for those who are already experienced with the program, but in the event that one of PCBâ??s current keystrokes conflicts with the â??defacto standardâ??, the defacto standard shall be implemented.</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> PCB should support all actions using â??noun/verbâ?? syntax. Details of this upgrade are presented in the â??actionsâ?? section below.</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> PCB should support normal selection modes (i.e. ways to select an object for editing or modification). Details of this upgrade are presented in the â??selection methodsâ?? section below.</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> PCBâ??s internals should be upgraded to easily support enhanced menus and button bars. This means upgraded callbacks and possibly also a resource file which specifies things like menu layout, menu options available, and keybindings.</div>
+</li>
+</ul>
+
+<p>
+ If the descriptions in this specification are ambiguous or unclear, use the behaviors implemented in gschem as the preferred example.
+</p>
+
+</div>
+
+<h4><a name="actions" id="actions">Actions</a></h4>
+<div class="level4">
+
+<p>
+The following actions should be modified to support a â??noun/verbâ?? actions, if they do not support it already. Where possible, support for the current â??verb/nounâ?? actions should not be dropped to maintain compatibility for users who have learned the old actions. However, if there is a conflict between the new noun/verb and the old verb/noun actions, the new noun/verb actions take presidence.
+</p>
+<ul>
+<li class="level1"><div class="li"> <strong>select/delete</strong> Using any of: menu item, <ctrl>-x. Delete should move the deleted object(s) from the layout into the copy buffer, so the user may place them elsewhere with a subsequent action. (NOTE: The copy buffer should probably be implemented separately from the existing â??element bufferâ??.)</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> <strong>select/remove</strong> Using any of menu item, <del>, character d. Remove should permanently remove the selected item.</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> <strong>select/move</strong> Using: left mouse button down and drag. Also: Select, then use arrow keys to move the selected objects some small quantum of motion (perhaps the grid spacing) in the direction specified by the arrow. </div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> <strong>select/copy</strong> Using any of: menu item, copy button, character c. <ctrl>-c. This should copy the selected items into the copy buffer so the user may place them elsewhere in a subsequent action. (NOTE: The copy buffer should probably be implemented separately from the existing â??element bufferâ??.)</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> <strong>paste</strong> Using any of: menu item, paste button, <ctrl>-v. This will bring the contents of the copy buffer into action at the cursor. When the user clicks on the design, then the elements will be placed on the layout where the user clicks. Refer to the behavior of gschem to see exactly how this should work.</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> <strong>select/move selection to current layer</strong> Using menu item, </div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> <strong>select/move object to opposite layer</strong> Using menu item, <shift>-c.</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> <strong>select/report object properties</strong> Using menu item or <ctrl>-r.</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> <strong>select/edit object properties</strong> Using menu item or double click on single object. This is a new action.<br/>
+ If the selected object is a graphical primitive (line, arc, etc), PCB will open up a window displaying the object properties in an editable window, allowing for the user to modify the objectâ??s properties. For example double clicking on a Cu track should open up the edit window, showing the trackâ??s width, current layer, end type (round vs. square), and its beginning and end coordinates.<br/>
+ If the selected object is a footprint, PCB will open up a window allowing the user to select a different footprint name. Some type of footprint browsing window with previewing should be presented to the user for this. The footprints should be found by looking through PCBâ??s footprint search path. Recommendation: steal the symbol browser window from gschem for this task. (Question: how to back annotate this info into the .sch files?)<br/>
+ If the selected object is text, then PCB should open up the text edit dialog box, allow the user to edit his text, click OK, and the text on the layout should be updated.</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> <strong>Select/rotate</strong> Using menu item or <ctrl>-r. This is a new window (the action already exists). This will open a window asking the user to type in a rotation angle. The user will type in the angle (in degrees), click OK, and the selected item will be rotated. Ideally, the rotation would apply globally to a selected set of items; it is up to the developer to determine if this is feasible. If not, then rotate should apply to only one item.</div>
+</li>
+</ul>
+
+</div>
+
+<h4><a name="selection_modes" id="selection_modes">Selection modes</a></h4>
+<div class="level4">
+
+<p>
+The following selection modes must be supported:
+</p>
+<ul>
+<li class="level1"><div class="li"> mouse click on single object.</div>
+</li>
+<li class="level1"><div class="li"> <ctrl>-click on multiple objects. (Example: <ctrl>-click this 1, <ctrl>-click this 2, <ctrl>-click this 3, etc.)</div>
+</li>
+<li class="level1"><div class="li"> Click and drag to select objects within a rectangular area.</div>
+</li>
+<li class="level1"><div class="li"> <esc> clears all selections</div>
+</li>
+<li class="level1"><div class="li"> <ctrl>-a selects all objects in the design.</div>
+</li>
+<li class="level1"><div class="li"> <ctrl>-A selects all connected objects. (Question: What is this selection mode useful for?)</div>
+</li>
+</ul>
+
+</div>
+
+<h4><a name="work_required1" id="work_required1">Work required</a></h4>
+<div class="level4">
+
+<p>
+This project involves:
+</p>
+<ol>
+<li class="level1"><div class="li"> Refactoring and upgrade of program internals to support noun/verb actions. </div>
+</li>
+<li class="level1"><div class="li"> Create new windows (e.g. object editor, move, rotate, etc.). </div>
+</li>
+<li class="level1"><div class="li"> Refactoring and upgrade of program internals to support selection modes.</div>
+</li>
+<li class="level1"><div class="li"> Implementation of <acronym title="Graphical User Interface">GUI</acronym> resource file which is read in upon program start to configure user interface.</div>
+</li>
+<li class="level1"><div class="li"> <acronym title="Graphical User Interface">GUI</acronym> upgrade. Specifically, hook up the callbacks to the menu items and buttons defined in the <acronym title="Graphical User Interface">GUI</acronym> resource file.</div>
+</li>
+<li class="level1"><div class="li"> Testing and bug cleanup.</div>
+</li>
+</ol>
+<hr />
+
+</div>
+<!-- SECTION "GUI modernization" [12537-18472] -->
+<h3><a name="footprint_editor_implementation" id="footprint_editor_implementation">Footprint editor implementation</a></h3>
+<div class="level3">
+
+<p>
+Incorporating a good footprint editor into PCB is a common request from users. It is important for PCB to clearly distinguish between editing a footprint and editing an entire PCB design. Here are two possible methods to accomplish this:
+</p>
+<ol>
+<li class="level1"><div class="li"> Although it is not optimal, the symbol editing mode present in gschem provides a reference for how this might be implemented. Specifically, editing a footprint may be implemented as a â??modeâ??, in which the user drills down into the footprint, and is placed into a special mode of the standard PCB editing window which is reserved for editing footprints. </div>
+</li>
+<li class="level1"><div class="li"> Another way to implement a footprint editor is to have a pop-up window with its own drawing pane along with editing widgets specialized for creating and modifying footprints.</div>
+</li>
+</ol>
+
+<p>
+Optionally, features involving editing footprints via the buffer will be removed. Alternately, retain the option allowing the user to draw in the main window, select, then invoke some menu option to convert the selection to a footprint. This option may exist <strong>alongside</strong> the new footprint editor.
+</p>
+
+</div>
+
+<h4><a name="invocation" id="invocation">Invocation</a></h4>
+<div class="level4">
+
+<p>
+There are two ways to invoke the footprint editor:
+</p>
+<ol>
+<li class="level1"><div class="li"> Create a new footprint. In this case the user will have no object selected on the PCB drawing window. He will then choose an option from the menu, like â??tools → down footprintâ??. This will place the user into the footprint editor, and the drawing area will be empty</div>
+</li>
+<li class="level1"><div class="li"> Edit an existing footprint. In this case, the user will select a footprint present on the board by clicking on it. Then he will select an option from the menu, like â??tools → down footprintâ??. This will place the user into the footprint editor, and the drawing area will hold a copy of the selected footprint, ready for editing.</div>
+</li>
+</ol>
+
+<p>
+ As a third possibility, the user should be able to do â??tools → create new footprintâ??, go into the editor, and then do â??file → openâ?? and select a footprint from the library to edit.
+</p>
+
+<p>
+As a fourth possibility, allow a mode similar to gschem, where a library browser is used to select and place primitive objects. That would save the user from needing to know where the library files are hidden.
+</p>
+
+</div>
+
+<h4><a name="editing" id="editing">Editing</a></h4>
+<div class="level4">
+
+<p>
+The footprint editor should be a graphical drawing environment similar to that presented by PCB for layout editing.
+</p>
+<ul>
+<li class="level1"><div class="li"> Buttons and menus. The footprint editor should have all the same menus and buttons as are available from the PCB editor. Those menu items and buttons which are not useful for footprint editing should be greyed out.</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> Look and feel. Once the user is placed in the footprint editor, the PCB window should change in some way to reflect that the user is in a different mode. For example, the title bar must say â??footprint modeâ??. Also, the drawing field background color might be changed a little bit to emphasize the change in mode.</div>
+</li>
+</ul>
+
+<p>
+ The design choice of which environment is better is left to the developer to decide based upon factors including input from the community, ease of implementation, etc.
+</p>
+
+</div>
+
+<h4><a name="saving" id="saving">Saving</a></h4>
+<div class="level4">
+
+<p>
+Once the user has edited his footprint, he will want to save it out. This is a problematic action, since itâ??s not a good idea to allow the user to overwrite a footprint living in the footprint libraries. Moreover, the user may not have write access to the library directories.
+</p>
+
+<p>
+Therefore, when the user is done editing his footprint, there should be only one save action available under the file menu: â??file → save footprint asâ??. This will call up the file save dialog, which will default to sticking the footprint in the current working directory (or the last directory he saved a footprint into during this session). The user will then be required to browse to his preferred save directory, and save the footprint there.
+</p>
+
+</div>
+
+<h4><a name="leaving" id="leaving">Leaving</a></h4>
+<div class="level4">
+
+<p>
+Once the footprint editing session is done, the user may leave the editor and return to his main PCB editing session. This may be accomplished using a menu item like â??tools → up to layoutâ??. If any unsaved changes remain in the footprint, then the user should be prompted to either save or discard his changes before leaving the footprint editor.
+</p>
+
+</div>
+
+<h4><a name="updating_a_footprint_placed_on_the_board" id="updating_a_footprint_placed_on_the_board">Updating a footprint placed on the board</a></h4>
+<div class="level4">
+
+<p>
+After editing a footprint and saving it out, the user will often want to update a footprint already present on the PCB. Here is the preferred method (use case) to do this:
+</p>
+<ol>
+<li class="level1"><div class="li"> User selects footprint to update.</div>
+</li>
+<li class="level1"><div class="li"> From menu, user selects â??tools → update footprintâ??. A keystroke to start this action may also be provided.</div>
+</li>
+<li class="level1"><div class="li"> A pop-up window opens, giving the user the footprint browser (as described above). The window will have has default footprint the name of the currently selected footprint. </div>
+</li>
+<li class="level1"><div class="li"> The user will either accept the default footprint presented, or he may search for a different footprint. When he is done, he will click OK.</div>
+</li>
+<li class="level1"><div class="li"> PCB will load the specified footprint from its library. Note: For this to work after editing a footprint, the user must place his local directory first on the footprint search path.</div>
+</li>
+<li class="level1"><div class="li"> PCB will then replace the old footprint on the board with the one pulled from the library. The old footprint (currently written into the .pcb file) will go away, and the new one will take its place.</div>
+</li>
+</ol>
+
+</div>
+
+<h4><a name="work_required2" id="work_required2">Work required</a></h4>
+<div class="level4">
+
+<p>
+This project involves:
+</p>
+<ol>
+<li class="level1"><div class="li"> Create internal structures and methods needed to support a separate footprint editor.</div>
+</li>
+<li class="level1"><div class="li"> Create footprint editing window (if the separate window approach is adopted).</div>
+</li>
+<li class="level1"><div class="li"> Integrate access to footprint editor into main PCB <acronym title="Graphical User Interface">GUI</acronym>.</div>
+</li>
+<li class="level1"><div class="li"> Testing and bug cleanup.</div>
+</li>
+</ol>
+<hr />
+
+</div>
+<!-- SECTION "Footprint editor implementation" [18473-24061] -->
+<h3><a name="upgrade_of_layer_and_design_objects" id="upgrade_of_layer_and_design_objects">Upgrade of layer and design objects</a></h3>
+<div class="level3">
+
+</div>
+
+<h4><a name="feature_description1" id="feature_description1">Feature Description</a></h4>
+<div class="level4">
+
+<p>
+Currently, PCBâ??s internal data structures only â??knowâ?? about metal and silk layers. Other layers commonly used in PCB design are either missing (e.g. DRC layer, outline layer), or are simply derived from the metal layer (solder mask). This task involves implementing full support for layers of arbitrary type and layer count. Also, support for other design objects is part of this upgrade. Specific features required are:
+</p>
+<ul>
+<li class="level1"><div class="li"> Upgrade of existing datastructures to support layers of arbitrary type including: DRC, mechanical outline, annotation, solder mask, paste mask, plated through-hole, unplated through-hole, metal, silk. The upgrade must also provide support for an arbitrary number of layers. Also, allowing for per-layer clearance settings is an important feature for inclusion here.</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> Implement window widget allowing for easy selection/configuration of layer stack-up. Parameters to configure include: layer count, layer type, layer polarity, layer visibility, layer color. The window will also allow the user to re-order the layers (from front to back), and to add or subtract an arbitrary number of layers. The layer window presented in â??gerbvâ?? is a reasonable example of what this window should support.</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> Implement a new datastructure representing a pad stack.</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> Implement a window widget allowing for easy editing of the pad stackâ??s properties, including: metal annulus outer diameter (per layer), solder mask diameter (per layer), paste mask diameter (per layer), clearance width (per layer), hole diameter.</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> Consider how the data-structures could allow support for blind or burried vias in the future.</div>
+</li>
+</ul>
+
+</div>
+
+<h4><a name="work_required3" id="work_required3">Work required</a></h4>
+<div class="level4">
+
+<p>
+This project involves:
+</p>
+<ol>
+<li class="level1"><div class="li"> Upgrade internal structures and methods to enable full layer support.</div>
+</li>
+<li class="level1"><div class="li"> Create layer configuration window.</div>
+</li>
+<li class="level1"><div class="li"> Create internal datastructures and methods to support padstacks.</div>
+</li>
+<li class="level1"><div class="li"> Create padstack configuration window.</div>
+</li>
+<li class="level1"><div class="li"> Testing and bug cleanup.</div>
+</li>
+</ol>
+<hr />
+
+</div>
+<!-- SECTION "Upgrade of layer and design objects" [24062-26087] -->
+<h3><a name="design_rule_checking_upgrade" id="design_rule_checking_upgrade">Design Rule Checking Upgrade</a></h3>
+<div class="level3">
+
+</div>
+
+<h4><a name="feature_description2" id="feature_description2">Feature Description</a></h4>
+<div class="level4">
+
+<p>
+The goal of design rule checking (DRC) is to insure that a printed circuit board layout conforms to a set of design rules. Design rules will consist of specifications like minimum copper line width, minimum copper spacing, etc. Generating a manufacturable PCB layout without DRC is tedious at best
+</p>
+
+<p>
+The current PCB DRC steps through design rule violations one by one using a dialog box that reports the error, the coordinate position of the error and places the cursor at the error. Bouncing back and forth between the layout and the dialog box is time consuming. Knowing all of the errors prior to starting error correction is usually more productive.
+</p>
+
+<p>
+A preferred method of reporting DRC violations would be to graphically indicate all errors on the layout. With this method all errors are quickly visible. DJ has suggested a layer for displaying DRC errors. The user should be able to turn the layer visibility on and off.
+</p>
+
+<p>
+A useful option for DRC would be to have it run periodically. A proactive DRC should help novices avoid creating multiple similar errors. Threaded operation, or a DRC which works in packets of time where the mainloop hits idle would be possibilities here. Both have their merits and draw-backs. If the operation is slow, weâ??ll need some way to queue the work such that updates to the board in the mean time queue updates for new DRC checking.
+</p>
+
+<p>
+Similarly, weâ??d need to ensure that removing or changing objects on the board doesnâ??t crash the DRC code - if it is running in a thread.
+</p>
+
+</div>
+
+<h4><a name="use_cases1" id="use_cases1">Use Cases</a></h4>
+<div class="level4">
+
+<p>
+<strong>Manual DRC</strong>
+</p>
+<ol>
+<li class="level1"><div class="li"> The user runs DRC using either a hot-key or menu item. An unobtrusive DRC status indicator is displayed. Perhaps the phrase â??DRC Checkâ?? in yellow text in the top bar.</div>
+</li>
+<li class="level1"><div class="li"> DRC violation marks are displayed on the DRC layer or on the PCB the layout.</div>
+</li>
+<li class="level1"><div class="li"> An unobtrusive DRC status indicator is displayed. Perhaps the phrases â??DRC PASSâ?? in green text and â??DRC FAILâ?? in red text in the top bar.</div>
+</li>
+<li class="level1"><div class="li"> If there are DRC failures the user can step to the next error manually or by using a hot-key. After changes are made the DRC can be run manually to verify the fix.</div>
+</li>
+</ol>
+
+<p>
+ <strong>Automatic DRC</strong>
+</p>
+<ol>
+<li class="level1"><div class="li"> Using a menu item the user can set the appropriate time interval for running DRC. A default value is used if a new value is not set.</div>
+</li>
+<li class="level1"><div class="li"> The user enables automatic DRC mode.</div>
+</li>
+<li class="level1"><div class="li"> After the DRC idle period has elapsed DRC runs. An unobtrusive DRC status indicator is displayed. Perhaps the phrase â??DRC Checkâ?? in yellow text in the top bar.</div>
+</li>
+<li class="level1"><div class="li"> DRC violation marks are displayed on the DRC layer or on the PCB layout.</div>
+</li>
+<li class="level1"><div class="li"> An unobtrusive DRC status indicator is displayed. Perhaps the phrase â??DRC PASSâ?? in green text and â??DRC FAILâ?? in red text in the top bar.</div>
+</li>
+<li class="level1"><div class="li"> If there are DRC failures the user can step to the next error manually or by using a hot-key. After changes are made the DRC can be run manually to verify the fix.</div>
+</li>
+</ol>
+
+</div>
+
+<h4><a name="work_required4" id="work_required4">Work required</a></h4>
+<div class="level4">
+
+<p>
+This project involves:
+</p>
+<ol>
+<li class="level1"><div class="li"> Implementation of DRC layer (part of work called out in â??DRC Upgradeâ?? section).</div>
+</li>
+<li class="level1"><div class="li"> Upgrade existing DRC checker with new DRC layer.</div>
+</li>
+<li class="level1"><div class="li"> Update <acronym title="Graphical User Interface">GUI</acronym> to use upgraded DRC checker.</div>
+</li>
+<li class="level1"><div class="li"> Testing and bug cleanup.</div>
+</li>
+</ol>
+<hr />
+
+</div>
+<!-- SECTION "Design Rule Checking Upgrade" [26088-29273] -->
+<h3><a name="project_milestones_duration_and_budget_estimates" id="project_milestones_duration_and_budget_estimates">Project milestones, duration, and budget estimates</a></h3>
+<div class="level3">
+
+<p>
+Although they are intertwined, the major focus areas are scoped independently here. Ordinarily, a project manager would put a Gantt chart here, but that level of detail is probably too fine for the purposes of an open source project. Therefore, I simply call out an estimated time required for each subtask. The project duration times are SWAGs based upon my limited experience in estimating software projects. They are based upon 8 hour work days (i.e. this work is performed as a full-time job) at a nominal billing rate of $50/hour. <strong>It is up to the developer to
+validate these estimations and negotiate his own billing rate before he agrees to perform this work.</strong>
+</p>
+
+</div>
+
+<h4><a name="forward_annotation_upgrade1" id="forward_annotation_upgrade1">Forward annotation upgrade</a></h4>
+<div class="level4">
+<ol>
+<li class="level1"><div class="li"> Determine which actions remain to be scripted so that forward annotation of any board is possible using an action list. (2 days).</div>
+</li>
+<li class="level1"><div class="li"> Define syntax for remaining actions, and document full syntax (2 days). This document will be used to update gsch2pcb (outside the scope of this project).</div>
+</li>
+<li class="level1"><div class="li"> Write sample action scripts for testing purposes (1 day).</div>
+</li>
+<li class="level1"><div class="li"> Creating the missing actions required for full forward annotation (3 days).</div>
+</li>
+<li class="level1"><div class="li"> Creating a method for reading in an action script (2 days)</div>
+</li>
+<li class="level1"><div class="li"> Integrating the new script-based forward annotation into PCBâ??s <acronym title="Graphical User Interface">GUI</acronym> (1 day)</div>
+</li>
+<li class="level1"><div class="li"> Testing and bug cleanup (5 days).</div>
+</li>
+</ol>
+
+<p>
+Total duration: 16 days = 128 hours. Cost: $6400
+</p>
+
+</div>
+
+<h4><a name="gui_modernization1" id="gui_modernization1">GUI modernization</a></h4>
+<div class="level4">
+<ol>
+<li class="level1"><div class="li"> Refactoring and upgrade of program internals to support noun/verb actions (5 days)</div>
+</li>
+<li class="level1"><div class="li"> Create new windows (e.g. object editor, move, rotate, etc.) (5 days). </div>
+</li>
+<li class="level1"><div class="li"> Refactoring and upgrade of program internals to support selection modes (5 days).</div>
+</li>
+<li class="level1"><div class="li"> Implementation of <acronym title="Graphical User Interface">GUI</acronym> resource file which is read in upon program start to configure user interface (3 days).</div>
+</li>
+<li class="level1"><div class="li"> <acronym title="Graphical User Interface">GUI</acronym> upgrade. Specifically, hook up the callbacks to the menu items and buttons defined in the <acronym title="Graphical User Interface">GUI</acronym> resource file (3 days).</div>
+</li>
+<li class="level1"><div class="li"> Testing and bug cleanup (5 days).</div>
+</li>
+</ol>
+
+<p>
+Total duration: 26 days = 208 hours Cost: $10400
+</p>
+
+</div>
+
+<h4><a name="footprint_editor_implementation1" id="footprint_editor_implementation1">Footprint editor implementation</a></h4>
+<div class="level4">
+<ol>
+<li class="level1"><div class="li"> Create internal structures and methods needed to support a separate footprint editor (4 days).</div>
+</li>
+<li class="level1"><div class="li"> Create footprint editing window (if the separate window approach is adopted) (3 days).</div>
+</li>
+<li class="level1"><div class="li"> Integrate access to footprint editor into main PCB <acronym title="Graphical User Interface">GUI</acronym> (2 days).</div>
+</li>
+<li class="level1"><div class="li"> Testing and bug cleanup (5 days).</div>
+</li>
+</ol>
+
+<p>
+Total duration: 14 days = 112 hours. Cost: $5600
+</p>
+
+</div>
+
+<h4><a name="layer_design_object_upgrade" id="layer_design_object_upgrade">Layer/design object upgrade</a></h4>
+<div class="level4">
+<ol>
+<li class="level1"><div class="li"> Upgrade internal structures and methods to enable full layer support (5 days).</div>
+</li>
+<li class="level1"><div class="li"> Create layer configuration window (3 days).</div>
+</li>
+<li class="level1"><div class="li"> Create internal datastructures and methods to support padstacks (4 days).</div>
+</li>
+<li class="level1"><div class="li"> Create padstack configuration window (3 days).</div>
+</li>
+<li class="level1"><div class="li"> Testing and bug cleanup (5 days).</div>
+</li>
+</ol>
+
+<p>
+Total duration: 20 days = 160 hours. Cost: $8000
+</p>
+
+</div>
+
+<h4><a name="design_rule_checking_upgrade1" id="design_rule_checking_upgrade1">Design Rule Checking Upgrade</a></h4>
+<div class="level4">
+<ol>
+<li class="level1"><div class="li"> Implementation of DRC layer (part of work called out in â??DRC Upgradeâ?? section) (0 days, assuming layer upgrade is complete).</div>
+</li>
+<li class="level1"><div class="li"> Upgrade existing DRC checker with new DRC layer (3 days).</div>
+</li>
+<li class="level1"><div class="li"> Update <acronym title="Graphical User Interface">GUI</acronym> to use upgraded DRC checker (2 days).</div>
+</li>
+<li class="level1"><div class="li"> Testing and bug cleanup (5 days).</div>
+</li>
+</ol>
+
+<p>
+Total duration: 10 days = 80 hours. Cost: $4000
+</p>
+
+</div>
+<!-- SECTION "Project milestones, duration, and budget estimates" [29274-] --></body>
+</html>
diff --git a/docs/wiki/geda-pcb_mp.html b/docs/wiki/geda-pcb_mp.html
new file mode 100644
index 0000000..ed86825
--- /dev/null
+++ b/docs/wiki/geda-pcb_mp.html
@@ -0,0 +1,50 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="pcb_man-page" id="pcb_man-page">PCB man-page</a></h1>
+<div class="level1">
+<pre class="code">PCB(1) PCB(1)
+
+
+
+NAME
+ pcb - Printed circuit board layout tool
+
+
+SYNOPSIS
+ pcb [options] [pcb file]
+
+
+DESCRIPTION
+ The pcb program is a tool for the layout of printed circuit boards.
+ The complete manual for pcb is provided in a GNU texinfo format as well
+ as HTML and PDF. The texinfo version of the manual is typically viewed
+ with the info program or alternatively with emacs or a graphical info
+ viewer such as tkinfo /usr/local/share/pcb/pcb.html and
+ /usr/local/share/pcb/pcb.pdf. The prefix "/usr/local" may vary at your
+ site.
+
+
+
+
+
+
+
+ PCB(1)</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-pcb_tips.fr.html b/docs/wiki/geda-pcb_tips.fr.html
new file mode 100644
index 0000000..a1ba425
--- /dev/null
+++ b/docs/wiki/geda-pcb_tips.fr.html
@@ -0,0 +1,950 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#outils_pcb" class="toc">Outils PCB</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#ou_puis-je_lire_les_bases_sur_l_utilisation_de_pcb" class="toc">Où puis-je lire les bases sur l'utilisation de pcb?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#j_ai_trouve_un_bogue_que_puis-je_y_faire" class="toc">J'ai trouvé un bogue·! Que puis-je y faire·?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#comment_configurer_les_regles_du_fabricant_a_utiliser_i.e._diametres_de_percage_specification_des_largeurs_espacements_des_pistes" class="toc">Comment configurer les règles du fabricant à utiliser (i.e. diamètres de perçage, spécification des largeurs/espacements des pistes)?</a></span></div></li>
+</ul>
+</li>
+<li class="level1"><div class="li"><span class="li"><a href="#a_propos_des_empreintes" class="toc">Ã? propos des empreintes</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#comment_fonctionne_le_systeme_d_empreintes_de_pcb" class="toc">Comment fonctionne le système d'empreintes de PCB?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#ou_puis-je_obtenir_des_empreintes_pre-dessinees_pour_pcb" class="toc">Où puis-je obtenir des empreintes pré-dessinées pour PCB?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#je_veux_utiliser_pcb_pour_faire_le_placement._comment_connaitre_la_valeur_a_utiliser_pour_l_attribut_d_empreinte" class="toc">Je veux utiliser PCB pour faire le placement. Comment connaitre la valeur à utiliser pour l'attribut d'empreinte?</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#newlib" class="toc">Newlib</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#bibliotheque_m4" class="toc">Bibliothèque M4</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#quelle_est_la_maniere_recommandee_pour_traiter_les_differentes_empreintes_pour_le_meme_type_de_composant" class="toc">Quelle est la manière recommandée pour traiter les différentes empreintes pour le même type de composant?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#comment_je_dessine_une_nouvelle_une_empreinte" class="toc">Comment je dessine une nouvelle une empreinte?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#comment_j_edite_change_une_empreinte_existante" class="toc">Comment j'édite/change une empreinte existante?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#comment_j_ajoute_une_bibliotheque_d_empreintes_a_pcb" class="toc">Comment j'ajoute une bibliothèque d'empreintes à PCB?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#pcb_ne_trouve_par_mes_empreintes._pourquoi" class="toc">PCB ne trouve par mes empreintes. Pourquoi?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#maintenant_que_j_ai_toutes_ces_empreintes_ou_dois-je_les_placer" class="toc">Maintenant que j'ai toutes ces empreintes, où dois-je les placer?</a></span></div></li>
+</ul>
+</li>
+<li class="level1"><div class="li"><span class="li"><a href="#placement_de_composants" class="toc">Placement de composants</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#comment_je_pivote_une_selection_i.e._pour_plus_d_un_element" class="toc">Comment je pivote une sélection (i.e. pour plus d'un élément)?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#comment_je_change_la_taille_de_l_objet_graphique_comme_du_texte_des_lignes_de_masque_texte_etc" class="toc">Comment je change la taille de l'objet graphique (comme du texte, des lignes de masque texte, etc)?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#comment_placer_les_composants_sur_les_deux_faces_de_pcb" class="toc">Comment placer les composants sur les deux faces de PCB?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#comment_je_place_l_origine_dans_pcb" class="toc">Comment je place l'origine dans pcb?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#comment_je_mesure_les_distances_et_les_dimensions_des_composants" class="toc">Comment je mesure les distances et les dimensions des composants?</a></span></div></li>
+</ul>
+</li>
+<li class="level1"><div class="li"><span class="li"><a href="#routage" class="toc">Routage</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#comment_router_une_connexion_depuis_le_cote_soudure_vers_le_cote_composant_et_inversement" class="toc">Comment router une connexion depuis le côté soudure vers le côté composant et inversement?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#comment_je_change_le_style_de_routage" class="toc">Comment je change le style de routage?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#j_ai_merde_comment_je_reviens_en_arriere" class="toc">J'ai merdé! Comment je reviens en arrière?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#comment_je_deplace_un_jeu_de_piste_d_une_couche_a_l_autre" class="toc">Comment je déplace un jeu de piste d'une couche à l'autre?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#comment_je_change_les_soldermask_clearance_autour_d_un_trou_via" class="toc">Comment je change les soldermask clearance autour d'un trou/via?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#comment_changer_la_taille_des_pistes" class="toc">Comment changer la taille des pistes?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#comment_je_pilote_un_via_pour_connecter_une_piste_a_un_plan_de_masse_sur_une_couche_differente" class="toc">Comment je pilote un via pour connecter une piste à un plan de masse sur une couche différente?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#je_veux_dessiner_une_piste_entre_deux_segments_sur_le_meme_net_mais_pcb_ne_me_laisse_pas_faire_pourquoi" class="toc">Je veux dessiner une piste entre deux segments sur le même net mais PCB ne me laisse pas faire! Pourquoi?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#pcb_semble_manger_mes_noms_de_composants_et_se_plaint_qu_il_ne_peut_pas_trouver_des_nets_adaptes_aux_broches_de_quoi_cela_vient" class="toc">PCB semble manger mes noms de composants et se plaint qu'il ne peut pas trouver des nets adaptés aux broches! De quoi cela vient?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#comment_je_peux_configurer_la_couleur_et_l_epaisseur_des_rats_nests" class="toc">Comment je peux configurer la couleur et l'épaisseur des rats nests?</a></span></div></li>
+</ul>
+</li>
+<li class="level1"><div class="li"><span class="li"><a href="#au_dela_des_pistes_et_des_empreintes" class="toc">Au delà des pistes et des empreintes</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#comment_je_trace_un_dessin_une_impression_ou_un_autre_pcb" class="toc">Comment je trace un dessin, une impression ou un autre PCB?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#je_ne_peux_pas_copier_des_pastilles_dans_un_circuit._comment_je_fais" class="toc">Je ne peux pas copier des pastilles dans un circuit. Comment je fais?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#comment_je_remplis_les_zones_avec_cuivre" class="toc">Comment je remplis les zones avec cuivre?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#les_polygones_mettent_mes_pistes_a_la_masse_que_puis-je_y_faire" class="toc">Les polygones mettent mes pistes à la masse! Que puis-je y faire?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#comment_je_change_le_polygon_clearance" class="toc">Comment je change le polygon clearance?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#comment_je_cache_les_polygones_lorsque_j_edite_le_placement" class="toc">Comment je cache les polygones lorsque j'édite le placement?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#comment_editer_les_polygones" class="toc">Comment éditer les polygones?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#comment_je_place_des_vias_qui_connectent_un_polygone_pour_une_dissipation_thermique_complete_ou_pour_une_integrite_de_protection_complete" class="toc">Comment je place des vias qui connectent un polygone pour une dissipation thermique complète ou pour une intégrité de protection complète?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#les_polygones_peuvent-ils_etre_un-masques_un_polygone_peut-il_etre_de_cuivre_sans_masque_de_soudure" class="toc">Les polygones peuvent-ils être un-masqués? (Un polygone peut-il être de cuivre sans masque de soudure?)</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#comment_je_place_des_trous_de_montage_mounting_hole" class="toc">Comment je place des trous de montage (mounting hole)?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#pourquoi_est-il_possible_de_realiser_des_ponts_thermiques_pour_les_broches_mais_pas_pour_une_pastille" class="toc">Pourquoi est-il possible de réaliser des ponts thermiques pour les broches mais pas pour une pastille?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#pcb_peut-il_etre_utilise_pour_realiser_des_cartes_a_simple_couche" class="toc">PCB peut-il être utilisé pour réaliser des cartes à simple couche?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#quelles_ressources_existent_pour_traiter_les_fichiers_pcb_en_utilisant_les_scripts" class="toc">Quelles ressources existent pour traiter les fichiers PCB en utilisant les scripts?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#comment_j_importe_des_graphiques_vectoriels_externe" class="toc">Comment j'importe des graphiques vectoriels externe?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#comment_j_attache_un_nom_a_mon_circuit" class="toc">Comment j'attache un nom à mon circuit?</a></span></div></li>
+</ul>
+</li>
+<li class="level1"><div class="li"><span class="li"><a href="#autorouteur" class="toc">Autorouteur</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#comment_je_force_l_autorouteur_a_ne_placer_des_pistes_que_sur_une_couche_particuliere" class="toc">Comment je force l'autorouteur à ne placer des pistes que sur une couche particulière?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#commennt_forcer_l_autorouteur_a_router_seulement_dans_les_limites_des_contours_du_pcb" class="toc">Commennt forcer l'autorouteur à router seulement dans les limites des contours du pcb?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#comment_je_route_les_plans_d_alimentation_et_de_masse_avec_l_autorouteur" class="toc">Comment je route les plans d'alimentation et de masse avec l'autorouteur?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#le_circuit_produit_par_l_autorouteur_est_inefficace" class="toc">Le circuit produit par l'autorouteur est inefficace!</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#le_circuit_produit_par_l_autorouteur_est_moche" class="toc">Le circuit produit par l'autorouteur est moche!</a></span></div></li>
+</ul>
+</li>
+<li class="level1"><div class="li"><span class="li"><a href="#generation_gerber_et_production_de_fichiers_i_o" class="toc">Génération Gerber et production de fichiers I/O</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#comment_je_realise_des_contours_de_carte_pour_proposer_mes_gerbers_vers_le_fabricant_de_carte" class="toc">Comment je réalise des contours de carte pour proposer mes gerbers vers le fabricant de carte?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#j_ai_fini_mon_placement._comment_je_le_controle" class="toc">J'ai fini mon placement. Comment je le contrôle?</a></span></div></li>
+</ul>
+</li>
+<li class="level1"><div class="li"><span class="li"><a href="#vous_n_avez_pas_repondu_a_mes_questions._ou_puis-je_trouver_d_autres_informations_sur_pcb" class="toc">Vous n'avez pas répondu à mes questions. Où puis-je trouver d'autres informations sur PCB?</a></span></div></li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="outils_pcb" id="outils_pcb">Outils PCB</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "Outils PCB" [1-26] -->
+<h2><a name="ou_puis-je_lire_les_bases_sur_l_utilisation_de_pcb" id="ou_puis-je_lire_les_bases_sur_l_utilisation_de_pcb">Où puis-je lire les bases sur l'utilisation de pcb?</a></h2>
+<div class="level2">
+
+<p>
+Le <a href="http://pcb.sourceforge.net/manual.html"; class="urlextern" title="http://pcb.sourceforge.net/manual.html"; rel="nofollow">manuel de pcb</a> contient une description concise de lâ??interface utilisateur dans la section «·Getting Started·» (<a href="http://pcb.sourceforge.net/pcb-20060822/pcb.html#Getting%20Started"; class="urlextern" title="http://pcb.sourceforge.net/pcb-20060822/pcb.html#Getting%20Started"; rel="nofollow">version 20060822</a>)
+</p>
+
+</div>
+<!-- SECTION "Où puis-je lire les bases sur l'utilisation de pcb?" [27-342] -->
+<h2><a name="j_ai_trouve_un_bogue_que_puis-je_y_faire" id="j_ai_trouve_un_bogue_que_puis-je_y_faire">J'ai trouvé un bogue·! Que puis-je y faire·?</a></h2>
+<div class="level2">
+<ol>
+<li class="level1"><div class="li"> Débutez en lisant <a href="http://pcb.sourceforge.net/bugs.html"; class="urlextern" title="http://pcb.sourceforge.net/bugs.html"; rel="nofollow">the pcb bug reporting page</a>.</div>
+</li>
+<li class="level1"><div class="li"> Contrôlez, de quoi avons-nous besoin pour reproduire le bogue.</div>
+</li>
+<li class="level1"><div class="li"> Demandez sur la liste de <a href="http://www.geda.seul.org/mailinglist/index.html"; class="urlextern" title="http://www.geda.seul.org/mailinglist/index.html"; rel="nofollow">diffusion de geda-user</a> sâ??il est en cours de correction ou sâ??il a été réglé avec la version la plus à jour de pcb. Notez que vous devez être inscrits sur la liste de diffusion de geda-user avant de pouvoir poster.</div>
+</li>
+<li class="level1"><div class="li"> Vérifiez si le problème est déjà répertorié dans le <a href="http://sourceforge.net/tracker/?group_id=73743&atid=538811"; class="urlextern" title="http://sourceforge.net/tracker/?group_id=73743&atid=538811"; rel="nofollow">bug tracking system de pcb</a>. Si ce nâ??est pas le cas; émettez un rapport de bogue. Assurez-vous de donner toutes les informations nécessaires pour reproduire le bogue et ajoutez la version de pcb qui contient le bogue.</div>
+</li>
+<li class="level1"><div class="li"> Finallement, avec tous les projets open source ouverts, vous pourriez muscler vos muscles de programmation et tenter de régler le bogue par vous même. Veuillez envoyer un correctif sur les changements que vous avez effectués sur le <a href="http://sourceforge.net/tracker/?group_id=73743&atid=538811"; class="urlextern" title="http://sourceforge.net/tracker/?group_id=73743&atid=538811"; rel="nofollow">BTS de pcb</a>. Le correctif sera accepté avec reconnaissance pour améliorer la prochaine version de pcb.</div>
+</li>
+</ol>
+
+</div>
+<!-- SECTION "J'ai trouvé un bogue·! Que puis-je y faire·?" [343-1613] -->
+<h2><a name="comment_configurer_les_regles_du_fabricant_a_utiliser_i.e._diametres_de_percage_specification_des_largeurs_espacements_des_pistes" id="comment_configurer_les_regles_du_fabricant_a_utiliser_i.e._diametres_de_percage_specification_des_largeurs_espacements_des_pistes">Comment configurer les règles du fabricant à utiliser (i.e. diamètres de perçage, spécification des largeurs/espacements des pistes)?</a></h2>
+<div class="level2">
+
+<p>
+Ce sujet est couvert dans la documentation disponible sur <a href="http://pcb.sourceforge.net/pcb-20060422/pcb.html#Vendor%20drill%20mapping"; class="urlextern" title="http://pcb.sourceforge.net/pcb-20060422/pcb.html#Vendor%20drill%20mapping"; rel="nofollow">le site PCBe</a>.
+</p>
+
+</div>
+<!-- SECTION "Comment configurer les règles du fabricant à utiliser (i.e. diamètres de perçage, spécification des largeurs/espacements des pistes)?" [1614-1915] -->
+<h1><a name="a_propos_des_empreintes" id="a_propos_des_empreintes">Ã? propos des empreintes</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "Ã? propos des empreintes" [1916-1955] -->
+<h2><a name="comment_fonctionne_le_systeme_d_empreintes_de_pcb" id="comment_fonctionne_le_systeme_d_empreintes_de_pcb">Comment fonctionne le système d'empreintes de PCB?</a></h2>
+<div class="level2">
+
+<p>
+PCB supporte deux mécanismes de bibliothèque entièrement séparés:
+</p>
+<ol>
+<li class="level1"><div class="li"> Le premier est appelé «·oldlib·», «·pcblib·» ou «·bibliothèque M4·». Ce système est historique·; il dépend du langage macro M4 pour générer des empreintes à la volée. La bibliothèque M4 est assez grande et a quelques bogues. Néanmoins, elle est très maniable et est distribuée avec PCB. Un fonctionnalité puissante de la bibliothèque m4 est quâ??une famille complète dâ??empreintes peut être définie rapidement avec une macro de base appropriée.</div>
+</li>
+<li class="level1"><div class="li"> La seconde bibliothèque dâ??empreintes pour PCB est appelée «·newlib·». Les empreintes de newlib sont définies en utilisant des fichiers de texte <acronym title="American Standard Code for Information Interchange">ASCII</acronym> qui appelent des primitives graphiques réalisant une empreinte complète. Les empreintes newlib peuvent aussi être créées graphiquement en utilisant PCB ou par toute autre méthode qui peut produire un fichier texte (éditeur de texte, script awk/perl/ruby, etc.). </div>
+</li>
+</ol>
+
+<p>
+ Câ??est pourquoi, pendant le placement, vous pouvez utiliser des empreintes qui sont distribuées avec PCB, vous pouvez trouver des empreintes par une recherche web ou vous pouvez vous créer la votre et la placer dans un répertoire dédié. Le <a href="http://pcb.sourceforge.net/manual.html"; class="urlextern" title="http://pcb.sourceforge.net/manual.html"; rel="nofollow">manuel pcb</a> est complet et mise à jour pour le format de fichier élément. Un tutoriel assez incomplet mais utile est disponible sur le web comme: <a href="http://www.brorson.com/gEDA/"; class="urlextern" title="http://www.brorson.com/gEDA/"; rel="nofollow">http://www.brorson.com/gEDA/</a> (recherche des termes «·newlib·»).
+</p>
+
+</div>
+<!-- SECTION "Comment fonctionne le système d'empreintes de PCB?" [1956-3509] -->
+<h2><a name="ou_puis-je_obtenir_des_empreintes_pre-dessinees_pour_pcb" id="ou_puis-je_obtenir_des_empreintes_pre-dessinees_pour_pcb">Où puis-je obtenir des empreintes pré-dessinées pour PCB?</a></h2>
+<div class="level2">
+
+<p>
+Actuellement, le meilleur endroit pour avoir de empreintes (en plus de la distribution PCB) est le <a href="http://www.gedasymbols.org"; class="urlextern" title="http://www.gedasymbols.org"; rel="nofollow">site web des symboles gEDA</a>. Le <a href="http://www.luciani.org/geda/pcb/pcb-footprint-list.html"; class="urlextern" title="http://www.luciani.org/geda/pcb/pcb-footprint-list.html"; rel="nofollow">site web de John Luciani</a> possède une grand nombre dâ??empreintes et dâ??outils. De même, Darrell Harmon fournit un chouette script de génération dâ??empreintes <a href="http://www.dlharmon.com/geda/footgen.html"; class="urlextern" title="http://www.dlharmon.com/geda/footgen.html"; rel="nofollow">sur son site web</a>. Votre contribution au projet est la bienvenue, ainsi que le partage des empreintes. Finallement, vous pouvez demander sur la liste geda-user car quelquâ??un pourrait avoir pitié et vous envoyer un symbole. Notez que vous devez souscrire à la liste de diffusion geda-user avant de pouvoir poster.
+</p>
+
+</div>
+<!-- SECTION "Où puis-je obtenir des empreintes pré-dessinées pour PCB?" [3510-4322] -->
+<h2><a name="je_veux_utiliser_pcb_pour_faire_le_placement._comment_connaitre_la_valeur_a_utiliser_pour_l_attribut_d_empreinte" id="je_veux_utiliser_pcb_pour_faire_le_placement._comment_connaitre_la_valeur_a_utiliser_pour_l_attribut_d_empreinte">Je veux utiliser PCB pour faire le placement. Comment connaitre la valeur à utiliser pour l'attribut d'empreinte?</a></h2>
+<div class="level2">
+
+<p>
+Cette question est une des plus habituelle parmi les nouveaux utilisateurs de gEDA. De fait, aider les nouveaux à déterminer les noms dâ??empreintes appropriés est au coeur dâ??un débat en cours sur les <a href="geda-faq-gschem.fr.html#quel_est_l_objet_de_cette_polemique_entre_les_symboles_lourds_et_legers" class="wikilink1" title="geda-faq-gschem.fr.html">symboles légers vs. lourds</a>. Dans la distribution courante gEDA/gaf, les symboles sont légers, vous devez attacher lâ??attribut footprint au niveau du schéma (i.e. en utilisant soit gschem, soit gattrib). Le nom des empreintes à utiliser dépend de si vous utilisez la bibliothèque newlib ou M4 (pcblib).
+</p>
+
+</div>
+<!-- SECTION "Je veux utiliser PCB pour faire le placement. Comment connaitre la valeur à utiliser pour l'attribut d'empreinte?" [4323-5057] -->
+<h3><a name="newlib" id="newlib">Newlib</a></h3>
+<div class="level3">
+
+<p>
+Newlib stocke une empreinte par fichier et les noms utilisés par newlib sont des noms de fichier des fichiers dâ??empreinte.
+</p>
+
+<p>
+Il y a plusieurs manières de trouver les noms dâ??empreintes newlib à utiliser·:
+</p>
+<ul>
+<li class="level1"><div class="li"> Vous pouvez naviguer dans les empreintes disponibles enlançant pcb et en ouvrant la fenêtre de bibliothèque dâ??empreintes (disponibles depuis la barre de menu par «·Window â?? library·»). Clickez sur le groupe de bibliothèques «·newlib·» et sélectionnez une sous-bibliothèque pour chercher ses symboles. Le nom de chaque empreinte apparaît dans la fenêtre «·Elements·» sur le côté droit du navigateur de bibliothèque. Utilisez le nom exactement tel quâ??il apparaît dans le navigateur pour lâ??attribut dâ??empreinte dans gschem ou gattrib.</div>
+</li>
+<li class="level1"><div class="li"> Les empreintes newlib distribuées avec PCB sont stockées dans les répertoires sous <strong><code>${PREFIX}/share/pcb/newlib</code></strong>. (<strong><code>${PREFIX}</code></strong> est le répertoire dâ??installation spécifié lors de la configuration/compilation de PCB.) Le nom à coller avec lâ??attribut «·footprint·» est le nom de fichier de lâ??empreinte que vous souhaitez utiliser.<br/>
+ Par exemple, sur ma machine, jâ??ai installé gEDA avec le préfix <strong><code>/usr/local/geda/</code></strong>. Le boîtier 0805 (pour les résistances ou capas SMT) est dans un fichier avec un chemin absolu<br/>
+ <strong><code>/usr/local/geda/share/pcb/newlib/generic_SMD_packages/0805_reflow_solder</code></strong> <br/>
+ Donc, pour utiliser cette empreinte avec un composant, je met son attribut «·footprint·» à <strong><code>0805_reflow_solder</code></strong> en utilisant gschem ou gattrib.<br/>
+ Notez que si le symbole newlib que vous voulez utiliser est dans un répertoire non-standard, gsch2pcb aura besoin que vous lui spécifiez un chemin vers ce répertoire, siot dans votre fichier project.rc (si vous en utilisez un) ou en utilisant le drapeau <strong><code>â??elements-dir</code></strong> (depuis la ligne de commande).</div>
+</li>
+<li class="level1"><div class="li"> Finalement, comme chaque nouveau schéma vous imposera de dessiner au moins une ou deux nouvelles empreintes, il serait bien dâ??avoir un répertoire dâ??«·empreintes·» local. Comme précédement, le nom dâ??empreinte à utiliser est le nom de fichier que vous assignez à chacune de vos nouvelles empreintes. Encore une fois, nâ??oubliez pas dâ??ajouter une ligne à votre fichier project.rc indiquant à gsch2pcb où trouver vos empreintes locales. Alternativement, vous pouvez lancer gsch2pcb avec le drapeau <strong><code>â??elements-dir</code></strong> pour pointer vers votre répertoire dâ??empreintes local.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Newlib" [5058-7532] -->
+<h3><a name="bibliotheque_m4" id="bibliotheque_m4">Bibliothèque M4</a></h3>
+<div class="level3">
+
+<p>
+La bibliothèque M4 stocke les empreintes comme des macros M4·; Il y a habituellement plusieurs (beaucoup) dâ??empreintes contenues dans chaque fichier dâ??empreinte. Les différentes empreintes dans un simple fichier sont généralement des variations dâ??un même motif (e.g. DIP-8, DIP-14, DIP-16, etc.). La manière la plus facile de trouver le nom dâ??attribut correct est de naviguer dans la bibliothèque «·pcblib·» par la fenêtre de bibliothèque de PCB. Les attributs dâ??empreinte sont données entre crochets dans la description. Vous pouvez aussi voir la liste des empreintes de pcblib sur la <a href="http://www.gedasymbols.org/footprints/"; class="urlextern" title="http://www.gedasymbols.org/footprints/"; rel="nofollow">page web des symboles gEDA</a>.
+</p>
+
+<p>
+Les bibliothèques m4 suivantes ont reçu plus dâ??attention et dâ??amélioration que les autres·:
+</p>
+<ul>
+<li class="level1"><div class="li"> ~amp pour les connecteurs Amp</div>
+</li>
+<li class="level1"><div class="li"> ~amphenol pour les connecteurs Amphenol</div>
+</li>
+<li class="level1"><div class="li"> ~geda pour plusieurs éléments utilisés dans les circuits basiques utilisés par gEDA (résistances, capacités, etc).</div>
+</li>
+<li class="level1"><div class="li"> ~bourns pour les produits comme des potentiomètres de Bourns</div>
+</li>
+<li class="level1"><div class="li"> ~cts pour les produits comme les réseaux de résistances de CTS</div>
+</li>
+<li class="level1"><div class="li"> ~johnstech pour les sockets Johnstech</div>
+</li>
+<li class="level1"><div class="li"> ~minicircuits pour les empreintes spécifiques Minicircuits</div>
+</li>
+<li class="level1"><div class="li"> ~panasonic pour quelques empreintes spécifiques Panasonic</div>
+</li>
+</ul>
+
+<p>
+ Finalement, pour les bibliothèques newlib et M4, il est extrêmement important que vous vérifiez que les noms dâ??empreintes utilisées épelent *exactement* celui de lâ??empreinte que vous voulez placer dans PCB. Câ??es la raison pour laquelle il est critique dâ??inspecter lâ??empreinte avant de lâ??utiliser. Vous pouvez vérifier lâ??empreinte que vous voulez utiliser en cliquant dessus dans la «·bibliothèque dâ??empreinte·» puis le placer dans une zone vide de la zone de dessin de PCB. Inspectez manuellement lâ??empreinte pour vous assurer que le nombre correct de broches/pastilles, que les dimensions sont correctes, etc.
+</p>
+
+<p>
+Aussi, une fois que vous avez généré les fichiers Gerber, assurez-vous dâ??avoir <a href="geda-pcb_tips.fr.html#j_ai_fini_mon_placement._comment_je_le_controle" class="wikilink1" title="geda-pcb_tips.fr.html">inspecté toutes les empreintes instantiées dans vos Gerbers</a> en utilisant gerbv (ou un visualiseur Gerber équivalent) avant que vous nâ??envoyiez votre circuit à la fabrication.
+</p>
+
+</div>
+<!-- SECTION "Bibliothèque M4" [7533-9792] -->
+<h2><a name="quelle_est_la_maniere_recommandee_pour_traiter_les_differentes_empreintes_pour_le_meme_type_de_composant" id="quelle_est_la_maniere_recommandee_pour_traiter_les_differentes_empreintes_pour_le_meme_type_de_composant">Quelle est la manière recommandée pour traiter les différentes empreintes pour le même type de composant?</a></h2>
+<div class="level2">
+
+<p>
+Par exemple, un ampli op peut être DIP8 ou SO8. Une résistance peut être 0603, 0805, 1208 ou passante. Comment je sais quel boîtier et empreinte utiliser et comment je gère les choix?
+</p>
+
+<p>
+Dâ??abord, lâ??empreinte que vous devez utiliser est votre décision, pas celui de votre outil conception. Câ??est à vous de choisir votre boîtier préféré puis attacher lâ??attribut dâ??empreinte correct dans le composant du schéma. Une fois que vous avez choisi le boîtier (et lâ??empreinte), vous voudrez utiliser soit <a href="geda-pcb_tips.fr.html#ou_puis-je_obtenir_des_empreintes_pre-dessinees_pour_pcb" class="wikilink1" title="geda-pcb_tips.fr.html">trouver une empreinte appropriée</a> ou en <a href="geda-pcb_tips.fr.html#comment_je_dessine_une_nouvelle_une_empreinte" class="wikilink1" title="geda-pcb_tips.fr.html">dessiner une vous même</a> et la sauvegarder dans un répertoire local.
+</p>
+
+<p>
+Pour la gestion des choix dâ??empreintes (et donc le grand nombre dâ??attributs de composants que vous êtes susceptibles dâ??avoir): Utilisez <a href="geda-faq-attribs.fr.html#au_secours_mon_schema_a_des_centaines_de_composants_et_c_est_penible_d_utiliser_gschem_pour_attacher_tous_mes_attributs" class="wikilink1" title="geda-faq-attribs.fr.html">gattrib</a>. Câ??est fait pour.
+</p>
+
+</div>
+<!-- SECTION "Quelle est la manière recommandée pour traiter les différentes empreintes pour le même type de composant?" [9793-10988] -->
+<h2><a name="comment_je_dessine_une_nouvelle_une_empreinte" id="comment_je_dessine_une_nouvelle_une_empreinte">Comment je dessine une nouvelle une empreinte?</a></h2>
+<div class="level2">
+
+<p>
+Tout le monde le fait à sa manière. Quelques personnes dessinent les empreintes en utilisant seulement PCB. Quelques personnes dessinent dâ??abord une empreinte préliminaire dans PCB et puis la terminent ensuite à la main et lâ??éditant (e.g. en utilisant emacs). Quelques personnes écrivent des scripts <acronym title="Practical Extraction and Report Language">Perl</acronym> pour générer automatiquement des empreintes.
+</p>
+
+<p>
+Karel Kulhavy préfère dessiner lâ??empreinte entièrement en utilisant PCB, qui peut être la manière la moins dangereuse à utiliser pour les nouveaux. Il maintient un <a href="http://ronja.twibright.com/guidelines/footprints.php"; class="urlextern" title="http://ronja.twibright.com/guidelines/footprints.php"; rel="nofollow">HOWTO de procédure de création d'empreintes</a> sur son site web Ronja.
+</p>
+
+<p>
+Si vous voulez éditer le fichier empreinte à la main, le <a href="http://www.brorson.com/gEDA/land_patterns_20050129.pdf"; class="urlextern" title="http://www.brorson.com/gEDA/land_patterns_20050129.pdf"; rel="nofollow">manuel sur la création d'empreintes</a> par Stephen Meier et Stuart Brorson fournissent les détails de la syntaxe. Le document donne aussi des conseils sur la manière de faire des conceptions élégantes qui sâ??appliquent aussi à lâ??interface graphique de la création dâ??empreintes.
+</p>
+
+</div>
+<!-- SECTION "Comment je dessine une nouvelle une empreinte?" [10989-12104] -->
+<h2><a name="comment_j_edite_change_une_empreinte_existante" id="comment_j_edite_change_une_empreinte_existante">Comment j'édite/change une empreinte existante?</a></h2>
+<div class="level2">
+
+<p>
+Vous pouvez convertir une empreinte de circuit, éditer les éléments et les reconvertir en empreinte. DAns la liste suivante, les éléments en polices mono space sont des actions depuis le menu buffer.
+</p>
+<ol>
+<li class="level1"><div class="li"> Selectionner lâ??élément</div>
+</li>
+<li class="level1"><div class="li"> Copier la sélection vers le tampon</div>
+</li>
+<li class="level1"><div class="li"> <code>Séparez le tampon en morceaux</code></div>
+</li>
+<li class="level1"><div class="li"> <code>Copiez le tampon dans le placement</code></div>
+</li>
+<li class="level1"><div class="li"> Effectuez les changement souhaités</div>
+</li>
+<li class="level1"><div class="li"> Sélectionnez tous les objets qui appartiennent aux empreintes</div>
+</li>
+<li class="level1"><div class="li"> <code>Copiez la sélection dans le tampon</code></div>
+</li>
+<li class="level1"><div class="li"> <code>Convertissez le tampon en élément</code></div>
+</li>
+<li class="level1"><div class="li"> <code>Copiez le tampon dans le placement</code></div>
+</li>
+<li class="level1"><div class="li"> Placez la souris sur les pastilles qui ont été arrondis pendant lâ??étape 4 et pressez q. Cela arrondit les bords des pastilles.</div>
+</li>
+<li class="level1"><div class="li"> Allez sur chaque pastille, pressez n et donnez un nom à la pastille</div>
+</li>
+<li class="level1"><div class="li"> Sélectionnez tout puis <code>copy selection to buffer</code></div>
+</li>
+<li class="level1"><div class="li"> <code>Save buffer as elements to file</code>. Le fichier empreinte sera créé à lâ??endroit dâ??où pcb a été appelé.</div>
+</li>
+</ol>
+
+<p>
+Alternativement, vous pouvez utiliser votre éditeur de texte favori et éditez le code source de lâ??empreinte.
+</p>
+
+</div>
+<!-- SECTION "Comment j'édite/change une empreinte existante?" [12105-13249] -->
+<h2><a name="comment_j_ajoute_une_bibliotheque_d_empreintes_a_pcb" id="comment_j_ajoute_une_bibliotheque_d_empreintes_a_pcb">Comment j'ajoute une bibliothèque d'empreintes à PCB?</a></h2>
+<div class="level2">
+
+<p>
+Lâ??ajoût dâ??une bibliothèque dâ??empreintes peut être réalisée depuis lâ??interface graphique:<br/>
+ <strong><em>File</em></strong> â??> <strong><em>Preferences</em></strong> â??> <strong><em>Library</em></strong> â??> <strong>FOOTPRINTDIRECTORY</strong><br/>
+ Alternativement, vous pouvez éditer le fichier <code>$HOME/.pcb/preferences</code>. Cherchez la ligne qui débute par «·library-newlib·». Nâ??oubliez pas dâ??inclure le nouveau répertorie dans votre fichier de ressource gsch2pcb (si vous utilisez gsch2pcb, bien sûr).
+</p>
+
+</div>
+<!-- SECTION "Comment j'ajoute une bibliothèque d'empreintes à PCB?" [13250-13768] -->
+<h2><a name="pcb_ne_trouve_par_mes_empreintes._pourquoi" id="pcb_ne_trouve_par_mes_empreintes._pourquoi">PCB ne trouve par mes empreintes. Pourquoi?</a></h2>
+<div class="level2">
+
+<p>
+Le chemin des empreintes utilisé par PCB est défini en utilisant la variable <strong><code>Pcb.elementPath</code></strong> dans le fichier des applications par défaut appelé <strong><code>PCB</code></strong>. Le chemin pour le fichier <strong><code>PCB</code></strong> est configuré en utilisant la variable dâ??environnement <strong><code>XAPPLRESDIR</code></strong> qui est typiquement fait avec un script nommé <strong><code>pcb</code></strong>.
+</p>
+
+</div>
+<!-- SECTION "PCB ne trouve par mes empreintes. Pourquoi?" [13769-14168] -->
+<h2><a name="maintenant_que_j_ai_toutes_ces_empreintes_ou_dois-je_les_placer" id="maintenant_que_j_ai_toutes_ces_empreintes_ou_dois-je_les_placer">Maintenant que j'ai toutes ces empreintes, où dois-je les placer?</a></h2>
+<div class="level2">
+
+<p>
+Je préfère placer toutes les empreintes «·prêtes pour la production·» dans un seul répertoire qui nâ??est pas dans lâ??arbre dâ??installation de gEDA/PCB. Lorsquâ??une nouvelle version de gEDA/PCB sort, je ne fais aucun changement aux fichier de projet ou aux bibliothèques. Sâ??il y a des empreintes newlib dans la bibliothèque PCB que je veux utiliser, je les copie dans le répertoire dâ??empreintes «·prêtes pour la production·».
+</p>
+
+<p>
+Plutôt que changer les fichiers de configuration permettant à gsch2pcb de trouver les empreintes, jâ??ai créé un script appelé <strong><code>sch2pcb</code></strong> qui contient le chemin des empreitnes. Tous les utilisateurs utilisent le même script et accèdent aux même empreintes de production.
+</p>
+
+<p>
+Pour utiliser le script <strong><code>sch2pcb</code></strong> qui est listé ci-dessus, remplacez la chaîne <strong><code>FOOTPRINT_DIR</code></strong> avec votre répertoire dâ??empreintes:
+</p>
+<pre class="code">
+#!/bin/bash
+gsch2pcb --elements-dir FOOTPRINT_DIR $@
+</pre>
+
+<p>
+Ou une autre version utilisateur:
+</p>
+<pre class="code">
+#!/bin/bash
+#this script was written by John Luciani
+gsch2pcb --elements-dir /home/user/pcb/footprints/user --use-files $@
+</pre>
+
+</div>
+<!-- SECTION "Maintenant que j'ai toutes ces empreintes, où dois-je les placer?" [14169-15356] -->
+<h1><a name="placement_de_composants" id="placement_de_composants">Placement de composants</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "Placement de composants" [15357-15395] -->
+<h2><a name="comment_je_pivote_une_selection_i.e._pour_plus_d_un_element" id="comment_je_pivote_une_selection_i.e._pour_plus_d_un_element">Comment je pivote une sélection (i.e. pour plus d'un élément)?</a></h2>
+<div class="level2">
+<ol>
+<li class="level1"><div class="li"> Sélectionnez les éléments</div>
+</li>
+<li class="level1"><div class="li"> Buffer â?? Coupez la sélection vers le tampon</div>
+</li>
+<li class="level1"><div class="li"> Buffer â?? Pivotez le tampon de 90 deg CCW (ou CW)</div>
+</li>
+<li class="level1"><div class="li"> Clickez partout sur la carte et la sélection est à nouveau collée sur le circuit.</div>
+</li>
+</ol>
+
+</div>
+<!-- SECTION "Comment je pivote une sélection (i.e. pour plus d'un élément)?" [15396-15702] -->
+<h2><a name="comment_je_change_la_taille_de_l_objet_graphique_comme_du_texte_des_lignes_de_masque_texte_etc" id="comment_je_change_la_taille_de_l_objet_graphique_comme_du_texte_des_lignes_de_masque_texte_etc">Comment je change la taille de l'objet graphique (comme du texte, des lignes de masque texte, etc)?</a></h2>
+<div class="level2">
+<ul>
+<li class="level1"><div class="li"> La souris sur lâ??objet et frappez [<strong><code>s</code></strong>]. Cela augmentera la taille de lâ??objet sur lequel est la souris.</div>
+</li>
+<li class="level1"><div class="li"> La souris sur lâ??objet et grappez [<strong><code><shift>-S</code></strong>]. Cela diminuera la taille de lâ??objet sur lequel est la souris.</div>
+</li>
+</ul>
+
+<p>
+ Vous pouvez modifier la valeur dâ??augmentation/diminution en utilisant le menu <strong><em>file</em></strong> â?? <strong><em>preferences</em></strong> â?? <strong><em>increments</em></strong>.
+</p>
+
+</div>
+<!-- SECTION "Comment je change la taille de l'objet graphique (comme du texte, des lignes de masque texte, etc)?" [15703-16188] -->
+<h2><a name="comment_placer_les_composants_sur_les_deux_faces_de_pcb" id="comment_placer_les_composants_sur_les_deux_faces_de_pcb">Comment placer les composants sur les deux faces de PCB?</a></h2>
+<div class="level2">
+
+<p>
+Il y a deux manières de le faire:
+</p>
+<ul>
+<li class="level1"><div class="li"> Presser la touche de tabulation alternera le côté actif entre le côté composants et et soudure. Lorsque vous placez des composants, il iront sur le côté actif.</div>
+</li>
+<li class="level1"><div class="li"> Si vous visualisez un côté de la carte, placez y un composant et (avec le pointeur dessus), pressez la touche [<strong><code>b</code></strong>] (ce qui signifie, envoyer le composant de lâ??autre côté), le composant va vers lâ??autre côté de la carte.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Comment placer les composants sur les deux faces de PCB?" [16189-16699] -->
+<h2><a name="comment_je_place_l_origine_dans_pcb" id="comment_je_place_l_origine_dans_pcb">Comment je place l'origine dans pcb?</a></h2>
+<div class="level2">
+
+<p>
+Lâ??origine absolue est toujours dans le coin haut gauche de la zone accessible. Ceci ne peut être configuré ailleurs. Néanmoins, les coordonnées des objets peuvent aussi être donnés en relation de la grile courante. Dans la version GTK2 de pcb, les coordonnées sont montrées dans le coin haut droit de la fenêtre principale. La bonne valeur est la position absolue, alors que la valeur de gauche reflète la position relative dâ??un marqueur arbitraire. Ce marqueur est configuré à la position courante de la souris par la séquence de touche [<strong><code>ctrl-m</code></strong>]. Vous pouvez vouloir configurer le marqueur sur un point de grille ou de broche spécifique.
+</p>
+
+</div>
+<!-- SECTION "Comment je place l'origine dans pcb?" [16700-17410] -->
+<h2><a name="comment_je_mesure_les_distances_et_les_dimensions_des_composants" id="comment_je_mesure_les_distances_et_les_dimensions_des_composants">Comment je mesure les distances et les dimensions des composants?</a></h2>
+<div class="level2">
+
+<p>
+Utilisez [<strong><code>ctrl-m</code></strong>] pour configurer lâ??origine et lisez la distance de ce point par rapport au pointeur de souris sur le bord haut gauche de la fenêtre de pcb. Quelques objets comme les vias et les pistes donnent des informations utiles dans les rapports dâ??objets. Accédez au rapport de lâ??objet sous le pointeur de souris avec [<strong><code>ctrl-r</code></strong>].
+</p>
+
+</div>
+<!-- SECTION "Comment je mesure les distances et les dimensions des composants?" [17411-17841] -->
+<h1><a name="routage" id="routage">Routage</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "Routage" [17842-17863] -->
+<h2><a name="comment_router_une_connexion_depuis_le_cote_soudure_vers_le_cote_composant_et_inversement" id="comment_router_une_connexion_depuis_le_cote_soudure_vers_le_cote_composant_et_inversement">Comment router une connexion depuis le côté soudure vers le côté composant et inversement?</a></h2>
+<div class="level2">
+
+<p>
+Lors de lâ??utilistion de lâ??outil line tool, utilisez les touches de chiffres en haut du clavier pour changer de couche. Un via sera placé automatiquement à la fin du dernier segment complet.
+</p>
+
+</div>
+<!-- SECTION "Comment router une connexion depuis le côté soudure vers le côté composant et inversement?" [17864-18163] -->
+<h2><a name="comment_je_change_le_style_de_routage" id="comment_je_change_le_style_de_routage">Comment je change le style de routage?</a></h2>
+<div class="level2">
+
+<p>
+Il existe un jeu de tailles de routage prédéfinies. Le jeu porte des noms suggestifs (Signal, Power, Fat et Skinny). Touchez le bouton «·Route Style·» pour configurer les tailles du jeu courant à vos besoins. Lâ??outil line connaît différents modes pour traiter les connexions transversales. La status line sur le bas de la page indique quel mode est en cours:
+</p>
+<ol>
+<li class="level1"><div class="li"> 45° plus vertical/horizontal (status line: â??\_â??)</div>
+</li>
+<li class="level1"><div class="li"> vertical plus 45° (status line: â??_/â??)</div>
+</li>
+<li class="level1"><div class="li"> either vertical or 45° (status line: â??45â??)</div>
+</li>
+<li class="level1"><div class="li"> arbitrary angle (status line: â??allâ??)</div>
+</li>
+</ol>
+
+<p>
+La manière dâ??accéder à ces modes diffère en fonction des version de lâ??interface. La version GTK courante (v20060288) a par défaut â??_/â?? mais peut être modifiée temporairement en â??\_â?? avec la touche shift. Vous pouvez passer au mode 45° avec la touche slash â??/â??. Pour les angles arbitraires, pressez la touche point «·.·» ou choisissez «·enable all line directions·» dans le setting menu.
+</p>
+
+</div>
+<!-- SECTION "Comment je change le style de routage?" [18164-19200] -->
+<h2><a name="j_ai_merde_comment_je_reviens_en_arriere" id="j_ai_merde_comment_je_reviens_en_arriere">J'ai merdé! Comment je reviens en arrière?</a></h2>
+<div class="level2">
+
+<p>
+La touche universelle undo [<strong><code>U</code></strong>] fonctionne même en pleine action de placement de piste. IIl enlèvera le dernier segment mais gardera lâ??outil line attaché à la souris. Vous pouvez donc immediatement aller sur le routage et trouver un meilleur placement.
+</p>
+
+</div>
+<!-- SECTION "J'ai merdé! Comment je reviens en arrière?" [19201-19522] -->
+<h2><a name="comment_je_deplace_un_jeu_de_piste_d_une_couche_a_l_autre" id="comment_je_deplace_un_jeu_de_piste_d_une_couche_a_l_autre">Comment je déplace un jeu de piste d'une couche à l'autre?</a></h2>
+<div class="level2">
+<ol>
+<li class="level1"><div class="li"> Sélectionnez les pistes. Câ??est plus facile à faire sur vous fermez dâ??abord tout le reste sur cette couche (i.e. silk, broches, autres couches, etc).</div>
+</li>
+<li class="level1"><div class="li"> Configurez la nouvelle couche de réception. Oui, la nouvelle couche doit être affichée·; ce qui nâ??est pas un problème si vous avez déjà sélectionné les pistes à déplacer.</div>
+</li>
+<li class="level1"><div class="li"> Pressez [<strong><code>shift-M</code></strong>] pour déplacer toutes les pistes sélectionnées vers la couche courante.</div>
+</li>
+</ol>
+
+</div>
+<!-- SECTION "Comment je déplace un jeu de piste d'une couche à l'autre?" [19523-20041] -->
+<h2><a name="comment_je_change_les_soldermask_clearance_autour_d_un_trou_via" id="comment_je_change_les_soldermask_clearance_autour_d_un_trou_via">Comment je change les soldermask clearance autour d'un trou/via?</a></h2>
+<div class="level2">
+
+<p>
+Vous pouvez augmenter la soldermask clearance depuis tout trou/via en positionnant le curseur sur lâ??objet et tapez la touche [<strong><code>k</code></strong>]. Vous pouvez diminuer la clearance en utilisant la touche [<strong><code><shift>-K</code></strong>].
+</p>
+
+</div>
+<!-- SECTION "Comment je change les soldermask clearance autour d'un trou/via?" [20042-20335] -->
+<h2><a name="comment_changer_la_taille_des_pistes" id="comment_changer_la_taille_des_pistes">Comment changer la taille des pistes?</a></h2>
+<div class="level2">
+
+<p>
+Il existe plusieurs manières de changer la taille de piste déjà placées:
+</p>
+<ol>
+<li class="level1"><div class="li"> Utilisez [<strong><code>s</code></strong>] et [<strong><code>shift-s</code></strong>] pour augmenter ou diminuer la taille de la piste sous le curseur de la souris.</div>
+</li>
+<li class="level1"><div class="li"> choisissez <strong><code>Select/Change_size_of_selected_objects/Decrement_lines_by_4mil</code></strong> depuis le menu <strong><code>Select</code></strong>. La valeur de changement peut être configurée dans <strong><code>File/Preferences/Sizes</code></strong>. Cela nâ??agit que sur les pistes. Donc la sélection peut contenir des composants, des textes, vias et ainsi de suite.</div>
+</li>
+<li class="level1"><div class="li"> Sélectionnez les pistes devant être changées et tapez <strong><code>:ChangeSize(SelectedLines,+4,mils)</code></strong>. La virgule vous offre la ligne de commande et <strong><code>ChangeSize()</code></strong> est la version commandée de lâ??action précédemment décrite. Remplacez â??<strong><code>+4</code></strong>â?? par la valeur à laquelle vous voulez augmenter la taille de la piste. Utilisez le signe moins pour diminuer la taille de la piste. Si vous omettez le signe, la commande configure la taille de la piste à la valeur donnée.</div>
+</li>
+</ol>
+
+</div>
+<!-- SECTION "Comment changer la taille des pistes?" [20336-21393] -->
+<h2><a name="comment_je_pilote_un_via_pour_connecter_une_piste_a_un_plan_de_masse_sur_une_couche_differente" id="comment_je_pilote_un_via_pour_connecter_une_piste_a_un_plan_de_masse_sur_une_couche_differente">Comment je pilote un via pour connecter une piste à un plan de masse sur une couche différente?</a></h2>
+<div class="level2">
+<ol>
+<li class="level1"><div class="li"> Configurez la couche de plan de masse comme la couche active.</div>
+</li>
+<li class="level1"><div class="li"> Sélectionnez lâ??outil «·via·».</div>
+</li>
+<li class="level1"><div class="li"> Placez le via où vous voulez quâ??il aille (clic gauche pour le placer).</div>
+</li>
+<li class="level1"><div class="li"> Sélectionnez maintenant lâ??outil «·thermal·».</div>
+</li>
+<li class="level1"><div class="li"> Clic gauche sur le via que vous venez juste de placer.</div>
+</li>
+<li class="level1"><div class="li"> Changer maintenant la couche active en celle de la couche de routage souhaitée.</div>
+</li>
+<li class="level1"><div class="li"> Sélectionnez lâ??outil «·line·».</div>
+</li>
+<li class="level1"><div class="li"> Routez la piste sur la couche active vers ou depuis le via comme dâ??habitude.</div>
+</li>
+</ol>
+
+</div>
+<!-- SECTION "Comment je pilote un via pour connecter une piste à un plan de masse sur une couche différente?" [21394-22004] -->
+<h2><a name="je_veux_dessiner_une_piste_entre_deux_segments_sur_le_meme_net_mais_pcb_ne_me_laisse_pas_faire_pourquoi" id="je_veux_dessiner_une_piste_entre_deux_segments_sur_le_meme_net_mais_pcb_ne_me_laisse_pas_faire_pourquoi">Je veux dessiner une piste entre deux segments sur le même net mais PCB ne me laisse pas faire! Pourquoi?</a></h2>
+<div class="level2">
+
+<p>
+Vous pouvez dessiner des pistes avec auto-DRC Ã on. Pour connecter les deux segments, vous avez ici quelques suggestions:
+</p>
+<ul>
+<li class="level1"><div class="li"> DRC enforcement utilise le ratsnest pour déterminer où les pistes sont permises. Donc, vous devez avoir des ratsnest dessinés de manière à réaliser des connexions dans le mode auto-DRC. Sinon, vous ne serez pas authorisés) à connecter (ou approcher) toute zone de cuivre qui nâ??est pas connectée à notre net. (Si la visibilité du rat vous embête, vous pouvez cacher les couches de rat â?? mais les rats doivent exister).</div>
+</li>
+<li class="level1"><div class="li"> Vous devrez aussi rafraîchir les rats régulièrement lors du dessin. Tapez [<strong><code>o</code></strong>] pour redessiner/re-optimiser les rats. Assurez-vous quâ??un rat connecte visiblement deux pièces de métal que vous souhaitez réunir.</div>
+</li>
+<li class="level1"><div class="li"> Il est aussi possible que vous expérimentiez cette situation lors du dessin de pistes entre les broches dâ??un connecteur. Dans ce cas, il est possible que la largeur de piste viole les règles de clearance du champ de broche. Tentez de diminuer la clearance broche-vers-métal ou utilisez une épaisseur de piste plus étroite.</div>
+</li>
+<li class="level1"><div class="li"> Quelques fois, ce comportement de blocage du routage peut provenir dâ??une erreur dans votre netlist. Ne terminez pas les refdes avec des minuscules - elles sont réservées pour els portes à lâ??intérieur des composants. Finissez avec un majuscule ou un chiffre·; les minuscules sont simplement ignorées.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Je veux dessiner une piste entre deux segments sur le même net mais PCB ne me laisse pas faire! Pourquoi?" [22005-23552] -->
+<h2><a name="pcb_semble_manger_mes_noms_de_composants_et_se_plaint_qu_il_ne_peut_pas_trouver_des_nets_adaptes_aux_broches_de_quoi_cela_vient" id="pcb_semble_manger_mes_noms_de_composants_et_se_plaint_qu_il_ne_peut_pas_trouver_des_nets_adaptes_aux_broches_de_quoi_cela_vient">PCB semble manger mes noms de composants et se plaint qu'il ne peut pas trouver des nets adaptés aux broches! De quoi cela vient?</a></h2>
+<div class="level2">
+
+<p>
+Plus raisonnablement, vous les nommez de telle manière que pcb croie quâ??ils ne forment quâ??un élément. Les minuscules à la fin dâ??un refdes sont ignorés. Donc, les composants U2foo et U2bar ressemblent tous les deux à U2 pour pcb. Lors de la construction des rat nests, pcb cherchera des nets pour U2 qui, bien sûr, nâ??existe pas. Les minuscules sont destinées pour différentier les slots dâ??un multi-composant. E.g., les quatres symboles opamp dâ??un amplificateur opérationnel quadruple.<br/>
+ Ligne de fin: Nâ??utilisez pas les minuscules à la fin dâ??un refdes, à moins que vous ne sachiez ce que vous faites.
+</p>
+
+</div>
+<!-- SECTION "PCB semble manger mes noms de composants et se plaint qu'il ne peut pas trouver des nets adaptés aux broches! De quoi cela vient?" [23553-24310] -->
+<h2><a name="comment_je_peux_configurer_la_couleur_et_l_epaisseur_des_rats_nests" id="comment_je_peux_configurer_la_couleur_et_l_epaisseur_des_rats_nests">Comment je peux configurer la couleur et l'épaisseur des rats nests?</a></h2>
+<div class="level2">
+
+<p>
+Vous pouvez configurer la couleur des rats dans <code>File - Preference - Colors - Main colors</code>
+</p>
+
+<p>
+Il nâ??existe actuellement pas dâ??interface graphique pour changer les épaisseurs de rat mais vous pouvez éditer votre fichier <code>$HOME/.pcb/preference</code> manuellement. Fermez toutes les instances de pcb et cherchez la ligne qui débute avec <code>rat-thickness</code>.
+</p>
+
+</div>
+<!-- SECTION "Comment je peux configurer la couleur et l'épaisseur des rats nests?" [24311-24748] -->
+<h1><a name="au_dela_des_pistes_et_des_empreintes" id="au_dela_des_pistes_et_des_empreintes">Au delà des pistes et des empreintes</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "Au delà des pistes et des empreintes" [24749-24801] -->
+<h2><a name="comment_je_trace_un_dessin_une_impression_ou_un_autre_pcb" id="comment_je_trace_un_dessin_une_impression_ou_un_autre_pcb">Comment je trace un dessin, une impression ou un autre PCB?</a></h2>
+<div class="level2">
+
+<p>
+Voyez la page <a href="http://www.delorie.com/pcb/bg-image.html"; class="urlextern" title="http://www.delorie.com/pcb/bg-image.html"; rel="nofollow">http://www.delorie.com/pcb/bg-image.html</a> sur le site web PCB HID de DJ Delorie.
+</p>
+
+<p>
+Câ??est un bonne manière pour tracer des images à la main ou un autre PCB, disons un de ceux que vous en avez un au format propriétaire, que vous voudriez «·déverrouiller·» maintenant. De plus, vous pouvez utiliser des images comme outils pour faire des révisions de cartes ou des reconceptions.
+</p>
+
+<p>
+Si vous nâ??aimez pas utiliser PCB confiné à la zone de la carte, i.e. si vous voulez des marges autour de la carte, alors ajoutez-les dans GIMP. Jâ??aime faire des marges de 1.00000 autour de la carte. Lorsque vous configurez votre taille de PCB, vous voudrez ajouter votre zone de marge. CTRL-M vous aidera à vérifier la taille. Aussi, le temps de corriger les distorsions de votre scanner ou depuis votre dessin est à faire avant de le charger, dans GIMP ou un des équivalent.
+</p>
+
+</div>
+<!-- SECTION "Comment je trace un dessin, une impression ou un autre PCB?" [24802-25761] -->
+<h2><a name="je_ne_peux_pas_copier_des_pastilles_dans_un_circuit._comment_je_fais" id="je_ne_peux_pas_copier_des_pastilles_dans_un_circuit._comment_je_fais">Je ne peux pas copier des pastilles dans un circuit. Comment je fais?</a></h2>
+<div class="level2">
+
+<p>
+<strong>Question:</strong> Je veux copier une section de mon placement en un autre endroit.
+</p>
+
+<p>
+Je peux sélectionner une zone existante. Tout semble virer au au bleu.
+</p>
+
+<p>
+â??Bufferâ??–>â??Copy Selection To Bufferâ?? semble réussir (pas de complaintes).
+</p>
+
+<p>
+Lorsque je veux copier la zone copiée… et tout ce que jâ??arrive à bouger sont un couple de pistes et quelques vias. Les pastilles qu jâ??ai créé avec difficulté ne sont pas copiées. Pourquoi!?!?!?
+</p>
+
+<p>
+<strong>Réponse:</strong> Si la couche du dessus (silk layer) est désactivée, vous ne pouvez copier les éléments par le tampon copier. Bizarre, mais câ??est comme cela que cela fonctionne. Donc, validez la couche du dessus avant de copier une section de placement.
+</p>
+
+</div>
+<!-- SECTION "Je ne peux pas copier des pastilles dans un circuit. Comment je fais?" [25762-26535] -->
+<h2><a name="comment_je_remplis_les_zones_avec_cuivre" id="comment_je_remplis_les_zones_avec_cuivre">Comment je remplis les zones avec cuivre?</a></h2>
+<div class="level2">
+
+<p>
+Utilisez les plans rectangle et polygone. Ces objets éviteront toujours les vias, pastilles et broches. Les pistes sont aussi évitées, si elles ont le drapeau clear polygons de configuré. (menu: Settings/Enable_new_lines_clear_polygons)
+</p>
+
+</div>
+<!-- SECTION "Comment je remplis les zones avec cuivre?" [26536-26831] -->
+<h2><a name="les_polygones_mettent_mes_pistes_a_la_masse_que_puis-je_y_faire" id="les_polygones_mettent_mes_pistes_a_la_masse_que_puis-je_y_faire">Les polygones mettent mes pistes à la masse! Que puis-je y faire?</a></h2>
+<div class="level2">
+
+<p>
+Vous nâ??avez pas contrôlé le «·Enable_new_lines_clear_polygons·» dans le menu settings lorsque vous avez placé les pistes. Entrez «·changejoin(selection)·» dans la fenêtre de commande pour basculer ce drapeau pour toutes les pistes qui sont actuellement sélectionnées. Le raccourci clavier pour cette action est [<strong><code>shift-j</code></strong>].
+</p>
+
+</div>
+<!-- SECTION "Les polygones mettent mes pistes à la masse! Que puis-je y faire?" [26832-27255] -->
+<h2><a name="comment_je_change_le_polygon_clearance" id="comment_je_change_le_polygon_clearance">Comment je change le polygon clearance?</a></h2>
+<div class="level2">
+
+<p>
+Pressez [<strong><code>k</code></strong>] pour augmenter la clearence de lâ??objet sous le curseur. Utilisez [<strong><code>ctrl-k</code></strong>] pour augmenter la clearence des objets sélectionnés. Ajoutez le modificateur [<strong><code>shift</code></strong>] pour diminuer la clearence. Pour changer une piste complète, pressez [<strong><code>f</code></strong>] pour trouver tous les segments qui sont connectés à lâ??objet sous le curseur et appliquez lâ??action «·select(connection)·».
+</p>
+
+<p>
+La valeur de lâ??incrément peut être configurée dans le dialogue File/Preference/Increments.
+</p>
+
+</div>
+<!-- SECTION "Comment je change le polygon clearance?" [27256-27810] -->
+<h2><a name="comment_je_cache_les_polygones_lorsque_j_edite_le_placement" id="comment_je_cache_les_polygones_lorsque_j_edite_le_placement">Comment je cache les polygones lorsque j'édite le placement?</a></h2>
+<div class="level2">
+
+<p>
+Placez les polygones (et les rectangles) sur une couce séparée. Utilisez la préférence pour vous assurer que cette couche nâ??est pas dans le même groupe que les pistes. Désactivez la piste en clickant sur le bouton de couche correspondant dans la fenêtre principale. Après que vous ayiez terminé avec les changements, utilisez le dialogue preference pour permettre à la couche des polygones de joindre la couche des pistes.
+</p>
+
+</div>
+<!-- SECTION "Comment je cache les polygones lorsque j'édite le placement?" [27811-28318] -->
+<h2><a name="comment_editer_les_polygones" id="comment_editer_les_polygones">Comment éditer les polygones?</a></h2>
+<div class="level2">
+
+<p>
+Il y a quatre manières de base pour éditer les contours des polygones. Vous pouvez déplacer et effacer les verticales et vous pouvez insérer les verticales en utilisant deux techniques. Les polygones peuvent être éditées de manière équivalente dans le mode «·thin line draw·» (settings â??> enable thin line draw) ou dans le mode normal. Déplacer un sommet est facilement accompli en utilisant un-selecting your polygon puis en cliquant et tirant ce sommet dans le nouvel emplacement. Pour effacer un sommet, un coin de votre polygone, placez votre pointeur sur le point et tapez «·delete·» avec le clavier. Pour insérer un sommet, vous devez utiliser lâ??outil insert (â??insertâ?? keystroke). Démarrez en cliquant sur le bord que vous voulez séparer avec un nouveau point. Cliquez et tirez le nouveau point dans le polygone. Une variation de cette technique est 1) cliquer pour sélectionner, suivi par 2) cliquer pour placer le nouveau sommet.
+</p>
+
+<p>
+(NOTE: Insérer des points dans un polygone ne fonctionnera généralement QUE avec «·all direction lines·» de validé («·settings â??> enable all direction lines·»). Câ??est parce PCB possède un système de contrainte de 45/90 degrés puissante. Si vous tentez dâ??insérer des nouveaux sommets, dans un polygone, qui ne tombent pas sur des lignes à contraintes de 45 et 90 degrés, PCB ne permet pas cette action!)
+</p>
+
+</div>
+<!-- SECTION "Comment éditer les polygones?" [28319-29752] -->
+<h2><a name="comment_je_place_des_vias_qui_connectent_un_polygone_pour_une_dissipation_thermique_complete_ou_pour_une_integrite_de_protection_complete" id="comment_je_place_des_vias_qui_connectent_un_polygone_pour_une_dissipation_thermique_complete_ou_pour_une_integrite_de_protection_complete">Comment je place des vias qui connectent un polygone pour une dissipation thermique complète ou pour une intégrité de protection complète?</a></h2>
+<div class="level2">
+
+<p>
+Il est souvent utile dâ??avoir des vias connectés complètement à un polygone (une zone de cuivre) pour les transferts de chaleur â?? le problème apparent est que les polygones de PCB ont un seul drapeau «·clear pins/vias·» pour le polygone complet (basculé avec la touche [<strong><code>s</code></strong>]). Notre objectif est de seulement connecter quelques uns des broches/vias au polygone mais pour mieux les connecter que ne le font un des connexions thermiques. Vous avez ici quelques manières de le faire·:
+</p>
+
+<p>
+Une manière est de faire un objet qui est presque comme une connexion thermique en ce sens quelle est entre le via et le polygone â?? la différence est que vous créez réellement un anneau pour remplir complètement lâ??espace entre le trou et le polygone (qui, à cause de sa clearance validée, nâ??est pas connecté à la broche). Cet anneau est un arc à quatre segments. Vous pouvez copier ces quatre objets dans le tampon pour créer un «·zero-clearance thermal tool·». Le contre-coup de cette astuce est que lorsque vous changez la taille de via, vous aurez aussi à modifier la taille de ces éléments de remplissage.
+</p>
+
+<p>
+Les arcs vous permettront dâ??utiliser cette astuce de remplissage dans les zones étroites en ne plaçant que deux des quatre arcs.
+</p>
+
+<p>
+Une autre astuce est de réaliser une ligne sans longueur. Prenez un seul segment de ligne et déplacez le point de fin au point de début. Vous avez maintenant une «·ligne à un seul point·» (un cercle) avec le diamètre égal à lâ??épaisseur de la ligne. Faites autant de couches (touche [<strong><code>m</code></strong>]) que vous jugez nécessaire. Placez cet objet centré sur votre via pour le connecter à un polygone.
+</p>
+
+<p>
+Les utilisateurs intensifs peuvent vouloir garder une petite bibliothèque personnalisée des ces éléments en les sauvegardant comme des éléments. Il est aussi pratique de placer des «·éléments·» dans un de vos tampons PCB de telle manière quâ??ils soient à portée de main.
+</p>
+
+<p>
+Vous pouvez aussi ajouter un autre polygone par dessus le polygone sur lequel vous connecter vos vias. Vous devez désactiver le drapeau «·clear pins/vias·» et les vias seront connectés au polygon le plus grand en dessous.
+</p>
+
+</div>
+<!-- SECTION "Comment je place des vias qui connectent un polygone pour une dissipation thermique complète ou pour une intégrité de protection complète?" [29753-32096] -->
+<h2><a name="les_polygones_peuvent-ils_etre_un-masques_un_polygone_peut-il_etre_de_cuivre_sans_masque_de_soudure" id="les_polygones_peuvent-ils_etre_un-masques_un_polygone_peut-il_etre_de_cuivre_sans_masque_de_soudure">Les polygones peuvent-ils être un-masqués? (Un polygone peut-il être de cuivre sans masque de soudure?)</a></h2>
+<div class="level2">
+
+<p>
+Ce nâ??est actuellement pas possible dans PCB. La manière habituelle (par exemple si vous voulez quâ??une zone nue sâ??attache à une zone de dissipation ou un shielding) est de réaliser un élément qui est une pastille simple. Cette pastille doit être aussi petite que possible (0 x 0) mais avec une grand clearance. Câ??est la clearance du masque de soudure de cet élément que vous allez utiliser pour dé-masquer le polygone. PCB limite en interne la taille de la pastille à 250 mils. Pour les zones plus grandes, vous aurez besoin dâ??utiliser plusieurs pastilles.
+</p>
+
+</div>
+<!-- SECTION "Les polygones peuvent-ils être un-masqués? (Un polygone peut-il être de cuivre sans masque de soudure?)" [32097-32782] -->
+<h2><a name="comment_je_place_des_trous_de_montage_mounting_hole" id="comment_je_place_des_trous_de_montage_mounting_hole">Comment je place des trous de montage (mounting hole)?</a></h2>
+<div class="level2">
+
+<p>
+Utilisez une empreinte pour les pour trou de montage ou placez un via.
+</p>
+
+<p>
+Si la pastille entourant le trou de montage doit être conneté électriquement, alors vous devez montrer la connexion dans votre schéma. Ajoutez un symbole pour le pour le trou de montage et changez son attribut dâ??empreinte.
+</p>
+
+<p>
+Ma préférence est de créer des empreintes PCB pour les divers types dâ??éléments à monter. Jâ??ai une variété de silkscreens pour diverses combinaisons de de matériel (hex nut, hex nut with washer, etc.). Le silkscreen fournit une référence de placement pendant le placement avec PCB.
+</p>
+
+<p>
+Pour les exemples dâ??empreintes, voyez <a href="http://www.luciani.org/geda/pcb/pcb-footprint-list.html#Hardware"; class="urlextern" title="http://www.luciani.org/geda/pcb/pcb-footprint-list.html#Hardware"; rel="nofollow">http://www.luciani.org/geda/pcb/pcb-footprint-list.html#Hardware</a>.
+</p>
+
+</div>
+<!-- SECTION "Comment je place des trous de montage (mounting hole)?" [32783-33551] -->
+<h2><a name="pourquoi_est-il_possible_de_realiser_des_ponts_thermiques_pour_les_broches_mais_pas_pour_une_pastille" id="pourquoi_est-il_possible_de_realiser_des_ponts_thermiques_pour_les_broches_mais_pas_pour_une_pastille">Pourquoi est-il possible de réaliser des ponts thermiques pour les broches mais pas pour une pastille?</a></h2>
+<div class="level2">
+
+<p>
+La raison est que les broches ont habituellement suffisamment dâ??espace avec le plan les entourant qui reste intact sur toutes les faces et ce nâ??est pas le cas des pastilles qui sont habituellement trop serrées. Ã? cause de ceci, vous devez dessiner manuellement les «·doigts·» de liaison thermique pour connecter la pastille au plan de masse. Assurez-vous que vous avez configuré la connexion de telles nouvelles lignes aux plans lorsque vous les dessinez. Si vous avez besoin de faire plusieurs de ces ponts thermiques, passez un peu de temps à faire le premier de la manière dont vous souhaitez puis copiez les doigts dans le tampon et collez-le si vous voulez les autres.
+</p>
+
+</div>
+<!-- SECTION "Pourquoi est-il possible de réaliser des ponts thermiques pour les broches mais pas pour une pastille?" [33552-34351] -->
+<h2><a name="pcb_peut-il_etre_utilise_pour_realiser_des_cartes_a_simple_couche" id="pcb_peut-il_etre_utilise_pour_realiser_des_cartes_a_simple_couche">PCB peut-il être utilisé pour réaliser des cartes à simple couche?</a></h2>
+<div class="level2">
+
+<p>
+Oui. Tracez vos gerbers et et enlevez toutes les couches qui ne sont pas nécessaires. Vous pouvez juste dessiner le placement comme vous le souhaitez (style libre). Si vous voulez vérifier la connectivité, vous avez deux choix:
+</p>
+<ol>
+<li class="level1"><div class="li"> Supposer que votre cuivre est sur le côté oppposé, utilisez le côté supérieur du placement pour y placer les pistes où seront les jumpers. Câ??est probablement le plus facile. Puis, traitez le côté opposé et placez les jumpers où vous avez le côté supérieur du cuivre.</div>
+</li>
+<li class="level1"><div class="li"> Créez un symbole «·jumper·» dans le schéma et placez-le dans les endroits où vous avez besoin dâ??un jumper. Cela peut être pénible mais vous pouvez forcer les dimensions des jumpers de cette manière si vous en avez besoin.</div>
+</li>
+</ol>
+
+<p>
+ Si vous tentez dâ??utliser lâ??autorouter, désactivez toutes les couches arrière lorsque vous routez et il collera à cette couche.
+</p>
+
+</div>
+<!-- SECTION "PCB peut-il être utilisé pour réaliser des cartes à simple couche?" [34352-35318] -->
+<h2><a name="quelles_ressources_existent_pour_traiter_les_fichiers_pcb_en_utilisant_les_scripts" id="quelles_ressources_existent_pour_traiter_les_fichiers_pcb_en_utilisant_les_scripts">Quelles ressources existent pour traiter les fichiers PCB en utilisant les scripts?</a></h2>
+<div class="level2">
+
+<p>
+Une des plus grande fonctionnalité de PCB est quâ??il utilise un format de fichier <acronym title="American Standard Code for Information Interchange">ASCII</acronym> facilement compréhensible. Câ??est la raison pour laquelle de nombreues personnes utilisent les scripts (habituellement <acronym title="Practical Extraction and Report Language">Perl</acronym>) pour traiter leurs cartes de différentes manières. Vous pouvez utiliser ces scripts soit comme ils sont, soit en les modifiant pour les adapter à nos propres buts. Vous avez ici quelques liens vers les scripts disponibles:
+</p>
+<ol>
+<li class="level1"><div class="li"> John Luciani possède une large éventail de <a href="http://www.luciani.org/geda/pcb/pcb-perl-library.html"; class="urlextern" title="http://www.luciani.org/geda/pcb/pcb-perl-library.html"; rel="nofollow">scripts</a> disponible sur <a href="http://www.luciani.org"; class="urlextern" title="http://www.luciani.org"; rel="nofollow"> son site web</a>. Dans cette collection, des scripts sont inclus pour générer des empreintes, de même que </div>
+</li>
+<li class="level1"><div class="li"> David Rowe possède des scripts pour mettre à jour des éléments de même quâ??ajouter/suprimer des fichiers PCB les uns des autres sur <a href="http://www.rowetel.com/perl4pcb.html"; class="urlextern" title="http://www.rowetel.com/perl4pcb.html"; rel="nofollow">son site web</a>.</div>
+</li>
+<li class="level1"><div class="li"> Stuart Brorson a écrit un script simple qui génère des empreintes pour deux ponts thermiques passifs en SMD. Un tarball gzippé est disponible <a href="http://www.brorson.com/gEDA/Smtgen.pl.gz"; class="urlextern" title="http://www.brorson.com/gEDA/Smtgen.pl.gz"; rel="nofollow"> ici </a>.</div>
+</li>
+</ol>
+
+</div>
+<!-- SECTION "Quelles ressources existent pour traiter les fichiers PCB en utilisant les scripts?" [35319-36519] -->
+<h2><a name="comment_j_importe_des_graphiques_vectoriels_externe" id="comment_j_importe_des_graphiques_vectoriels_externe">Comment j'importe des graphiques vectoriels externe?</a></h2>
+<div class="level2">
+
+<p>
+Il existe un utilitaire open source provenant dâ??une tierce personne appelé <a href="http://www.pstoedit.net/"; class="urlextern" title="http://www.pstoedit.net/"; rel="nofollow">pstoedit</a> qui convertit des données postscript au format pcb. Il est inclus dans la plupart des distributions majeures de Linux. Vous pouvez utiliser votre graphique vectoriel préféré pour produire un logo ou toute autre type de marque amusante. Exportez-le comme eps si vous pouvez et assurez-vous que votre logo correspond à la à la boîte de remplissage (contrôlez-le avec un visualiseur postscript tel que ggv). Sâ??il nâ??y a pas dâ??export dâ??eps de disponible, vous pouvez produire du postscript en lâ??imprimant dans un fichier. Dans ce cas, vous pouvez ajouter une boîte de remplissage avec <a href="http://www.cs.wisc.edu/~ghost/doc/gnu/6.53/Ps2epsi.htm"; class="urlextern" title="http://www.cs.wisc.edu/~ghost/doc/gnu/6.53/Ps2epsi.htm"; rel="nofollow">ps2epsi</a>. Appelez pstoedit avec lâ??option «·<code>-f pcb</code>·» pour produire un fichier pcb valide qui contient les graphiques comme piste sur une couche 1. Chargez ce fichier dans pcb. Les graphiques seront alors quelque part dans le bord bas gauche de la visualisation. Vous avoir à zommer pour lâ??avoir sur lâ??écran.
+</p>
+
+<p>
+Lâ??import de graphiques vectoriels externes est utile si un si une forme irrégulière de pcb est nécessaire. Utilisez le tampon couper pour copier la forme de votre circuit réel.
+</p>
+
+</div>
+<!-- SECTION "Comment j'importe des graphiques vectoriels externe?" [36520-37846] -->
+<h2><a name="comment_j_attache_un_nom_a_mon_circuit" id="comment_j_attache_un_nom_a_mon_circuit">Comment j'attache un nom à mon circuit?</a></h2>
+<div class="level2">
+
+<p>
+Vous pouvez configurer le nom du pcb courant avec <code>Menu Edit - Edit name of - layout</code>. Cela configure lâ??attribut de titre sur le circuit. Cet attribut est utilisé pour els actions dâ??export. Il nâ??interfère pas avec le nom de fichier.
+</p>
+
+</div>
+<!-- SECTION "Comment j'attache un nom à mon circuit?" [37847-38140] -->
+<h1><a name="autorouteur" id="autorouteur">Autorouteur</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "Autorouteur" [38141-38166] -->
+<h2><a name="comment_je_force_l_autorouteur_a_ne_placer_des_pistes_que_sur_une_couche_particuliere" id="comment_je_force_l_autorouteur_a_ne_placer_des_pistes_que_sur_une_couche_particuliere">Comment je force l'autorouteur à ne placer des pistes que sur une couche particulière?</a></h2>
+<div class="level2">
+
+<p>
+Désactivez juste les couches dont vous ne voulez pas (habituellement vertes et bleues) en cliquant sur le nom de la couche puis pressez autoroute.
+</p>
+
+</div>
+<!-- SECTION "Comment je force l'autorouteur à ne placer des pistes que sur une couche particulière?" [38167-38416] -->
+<h2><a name="commennt_forcer_l_autorouteur_a_router_seulement_dans_les_limites_des_contours_du_pcb" id="commennt_forcer_l_autorouteur_a_router_seulement_dans_les_limites_des_contours_du_pcb">Commennt forcer l'autorouteur à router seulement dans les limites des contours du pcb?</a></h2>
+<div class="level2">
+
+<p>
+Vous pouvez faire fonctionner lâ??autorouteur seulement dans une zone donnée en dessinant un polygone de cuivre se conformant à votre emboîtement de circuit et placez-le dans chaque couche que vous tentez dâ??autorouter. Vous pouvez aussi utiliser cette astuce pour ne seulement autorouter quâ??une petite zone. Bien sûr, si vous avez un net qui touche accidentellement le polygone, toutes les routes seront court-circuitées à ce net.
+</p>
+
+</div>
+<!-- SECTION "Commennt forcer l'autorouteur à router seulement dans les limites des contours du pcb?" [38417-38952] -->
+<h2><a name="comment_je_route_les_plans_d_alimentation_et_de_masse_avec_l_autorouteur" id="comment_je_route_les_plans_d_alimentation_et_de_masse_avec_l_autorouteur">Comment je route les plans d'alimentation et de masse avec l'autorouteur?</a></h2>
+<div class="level2">
+
+<p>
+Connectez les polygones qui deviendront vos plans dâ??alimantation (et de masse) Ã un net et lâ??autorouteur sâ??occupera du reste. Vous pouvez avoir besoin de quelques astuces de clearances de polygone pour avoir le routage de lâ??alimentation _et_ le routage dans les limites de la carte.
+</p>
+
+</div>
+<!-- SECTION "Comment je route les plans d'alimentation et de masse avec l'autorouteur?" [38953-39323] -->
+<h2><a name="le_circuit_produit_par_l_autorouteur_est_inefficace" id="le_circuit_produit_par_l_autorouteur_est_inefficace">Le circuit produit par l'autorouteur est inefficace!</a></h2>
+<div class="level2">
+
+<p>
+Ce une limitation technologique de lâ??autorouteur actuel. Il est sans grille et utilise seulement les rectangles géométriques.
+</p>
+
+</div>
+<!-- SECTION "Le circuit produit par l'autorouteur est inefficace!" [39324-39517] -->
+<h2><a name="le_circuit_produit_par_l_autorouteur_est_moche" id="le_circuit_produit_par_l_autorouteur_est_moche">Le circuit produit par l'autorouteur est moche!</a></h2>
+<div class="level2">
+
+<p>
+Vous êtes plus que bienvenu pour contribuer à un autorouteur topologique.
+</p>
+
+</div>
+<!-- SECTION "Le circuit produit par l'autorouteur est moche!" [39518-39654] -->
+<h1><a name="generation_gerber_et_production_de_fichiers_i_o" id="generation_gerber_et_production_de_fichiers_i_o">Génération Gerber et production de fichiers I/O</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "Génération Gerber et production de fichiers I/O" [39655-39719] -->
+<h2><a name="comment_je_realise_des_contours_de_carte_pour_proposer_mes_gerbers_vers_le_fabricant_de_carte" id="comment_je_realise_des_contours_de_carte_pour_proposer_mes_gerbers_vers_le_fabricant_de_carte">Comment je réalise des contours de carte pour proposer mes gerbers vers le fabricant de carte?</a></h2>
+<div class="level2">
+
+<p>
+Vous pouvez ajouter une couche de contour pour vos projets pcb. PCB interprète toute couche appelée «·outline·» (edit â??> edit name of â??> active layer) comme étant le bord absolu du pcb. PCB imprime des fichiers gerber qui représente rigidement ceci.
+</p>
+
+<p>
+Vous pouvez entrer voter couche de contour par lâ??interface graphique de PCB. Vous dessinez simplement les lignes de contour de la carte. Vous pouvez générer des cartes de toute forme de cette manière.
+</p>
+
+<p>
+Il est aussi possible dâ??éditer le format de fichier natif .pcb de votre circuit. Jâ??utilise habituellement la Couche 8 pour les contours:
+</p>
+<pre class="code">Layer(8 "outline")
+(
+ Line[x1 y1 x2 y2 1000 2000 0x00000000]
+ Line[x2 y2 x3 y3 1000 2000 0x00000000]
+ Line[x3 y3 x4 y4 1000 2000 0x00000000]
+ Line[x4 y4 x1 y1 1000 2000 0x00000000]
+ Line[<more points go here for non-square boards> 1000 2000 0x00000000]
+)</pre>
+
+</div>
+<!-- SECTION "Comment je réalise des contours de carte pour proposer mes gerbers vers le fabricant de carte?" [39720-40703] -->
+<h2><a name="j_ai_fini_mon_placement._comment_je_le_controle" id="j_ai_fini_mon_placement._comment_je_le_controle">J'ai fini mon placement. Comment je le contrôle?</a></h2>
+<div class="level2">
+<ul>
+<li class="level1"><div class="li"> Lancez un contrôle des règles de dessin soit par lâ??interface de commande (â??DRC()") ou depuis le menu (Connects - Design Rule Checker). Vous pouvez configurer les règles avec la section des tailles dans le dialogue preference. Les résultats du contrôle sont montrés dans la fenêtre de journal (log). </div>
+</li>
+</ul>
+
+<p>
+avant de lancer le contrôleur de DRC, il est essentiel de contrôler vos fichiers Gerber. La Suite gEDA inclut le programme «·gerbv·» pour cette tâche. Vous avez ici quelques éléments à contrôler/vérifier:
+</p>
+<ul>
+<li class="level1"><div class="li"> Contrôlez que toutes les largeurs de pistes ont la taille correcte. Assurez-vous aussi que les largeurs de pistes et les séparations métal-métal sont au-dessus du minimum spécifié par votre fabricant de PCB.</div>
+</li>
+<li class="level1"><div class="li"> Contrôlez que tous les diamètres de trous sont à la bonne taille.</div>
+</li>
+<li class="level1"><div class="li"> Contrôlez que les anneaux de métal autour des trous/vias sont suffisamment larges. Lâ??anneau annulaire est la distance entre les bords du trou et le diamètre extérieur de la métallisation. Lâ??anneau annulaire doit être suffisamment large pour permettre la zone de perçage + connexion entre couches + autres anomalies de fabrication. Cette information devrait être disponible chez votre fabricant de PCB·; ils publient normalement les tailles minimum dâ??anneau annulaire dans leurs documents de règles de fabrication.</div>
+</li>
+<li class="level1"><div class="li"> Contrôlez que vos antipads (clearance autour des trous/vias) soient suffisamment larges. Cette information doit être disponible chez votre fabricant de PCB·; demandez-leur leurs documents de règles de fabrication.</div>
+</li>
+<li class="level1"><div class="li"> Vérifiez quâ??aucun soldermask ou silkscreen ne se superpose avec une pastille de cuivre ou un trou passant.</div>
+</li>
+<li class="level1"><div class="li"> Sur les couches de plan, vérifiez quâ??au moins quelques vias sâ??y connectent (oui, jâ??ai vu une carte ou le plan de masse complet était flottant â?? il nâ??avait pas été réalisé avec pcb, soit dit en passant)</div>
+</li>
+<li class="level1"><div class="li"> Sur les couches de plan, vérifiez quâ??au moins quelques vias _nâ??y sont pas_ connecté.</div>
+</li>
+<li class="level1"><div class="li"> Effectuez une contrôle visuel dâ??anomalie sur toutes les couches. Rien de détaillé, jetez juste une regard approximatif sur la manière dont cela evrait être.</div>
+</li>
+<li class="level1"><div class="li"> Toutes les couches sont-elles négatives/positives telles quâ??elles devraient lâ??être? Notez que certains fabricants veulent seulement des couches positives. PCB en créera automatiquement des Gerbers négatives sur les couches de plans sans pistes. Si vous voulez une couche avec tous les plans en sortie comme couche positive, dessinez une piste simple quelque part dans une zone inutilisée du plan. Cela obligera PCB à faire de cette couche une couche positive.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "J'ai fini mon placement. Comment je le contrôle?" [40704-43388] -->
+<h1><a name="vous_n_avez_pas_repondu_a_mes_questions._ou_puis-je_trouver_d_autres_informations_sur_pcb" id="vous_n_avez_pas_repondu_a_mes_questions._ou_puis-je_trouver_d_autres_informations_sur_pcb">Vous n'avez pas répondu à mes questions. Où puis-je trouver d'autres informations sur PCB?</a></h1>
+<div class="level1">
+
+<p>
+<a href="http://www.luciani.org/geda/pcb/faq-pcb-footprint.html"; class="urlextern" title="http://www.luciani.org/geda/pcb/faq-pcb-footprint.html"; rel="nofollow">http://www.luciani.org/geda/pcb/faq-pcb-footprint.html</a><br/>
+ <a href="http://pcb.sourceforge.net/faq.html"; class="urlextern" title="http://pcb.sourceforge.net/faq.html"; rel="nofollow">http://pcb.sourceforge.net/faq.html</a><br/>
+ <a href="http://pcb.sourceforge.net/pcb-20060822/pcb.html#Top"; class="urlextern" title="http://pcb.sourceforge.net/pcb-20060822/pcb.html#Top"; rel="nofollow">http://pcb.sourceforge.net/pcb-20060822/pcb.html#Top</a>
+</p>
+
+<p>
+Vous pouvez avoir des réponses plus rapides avec la liste des geda-user. Si vous nâ??avez trouvé une réponse à votre question à propos de PCB sur cette page ou dans les autres documentations, postez alors sur la liste! Notez que vous devez y souscrire avant de pouvoir y écrire. Les listes de gEDA et leurs archives sont sur: <a href="http://geda.seul.org/mailinglist/index.html"; class="urlextern" title="http://geda.seul.org/mailinglist/index.html"; rel="nofollow">http://geda.seul.org/mailinglist/index.html</a>
+</p>
+
+</div>
+<!-- SECTION "Vous n'avez pas répondu à mes questions. Où puis-je trouver d'autres informations sur PCB?" [43389-] --></body>
+</html>
diff --git a/docs/wiki/geda-pcb_tips.html b/docs/wiki/geda-pcb_tips.html
new file mode 100644
index 0000000..6d473df
--- /dev/null
+++ b/docs/wiki/geda-pcb_tips.html
@@ -0,0 +1,1524 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#about_pcb_layout_and_routing" class="toc">About PCB layout and routing</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#what_s_a_footprint_what_s_a_via_what_s_a_track" class="toc">What's a footprint? What's a via? What's a track?</a></span></div></li>
+</ul>
+</li>
+<li class="level1"><div class="li"><span class="li"><a href="#pcb_tools" class="toc">PCB Tools</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#where_can_i_read_about_the_basics_of_using_pcb" class="toc">Where can I read about the basics of using pcb?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#i_found_a_bug_what_can_i_do_about_it" class="toc">I found a bug! What can I do about it?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_can_i_set_the_manufacturing_rules_to_use_i.e._drill_diameters_trace_width_space_specs" class="toc">How can I set the manufacturing rules to use (i.e. drill diameters, trace width/space specs)?</a></span></div></li>
+</ul>
+</li>
+<li class="level1"><div class="li"><span class="li"><a href="#non-obvious_aspects_of_the_gui" class="toc">Non-obvious aspects of the GUI</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#auto-pan_bugs_me._what_can_i_do_about_it" class="toc">Auto-pan bugs me. What can I do about it?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#the_delete_key_sometimes_refuses_to_delete" class="toc">The delete key sometimes refuses to delete</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#i_try_to_move_an_object_but_pcb_won_t_let_me_what_can_i_do_about_it" class="toc">I try to move an object, but pcb won't let me! What can I do about it?</a></span></div></li>
+</ul>
+</li>
+<li class="level1"><div class="li"><span class="li"><a href="#footprint_issues" class="toc">Footprint issues</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#how_do_pcb_s_footprints_work" class="toc">How do PCB's footprints work?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#where_can_i_get_pre-drawn_footprints_for_pcb" class="toc">Where can I get pre-drawn footprints for PCB?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#i_want_to_use_pcb_to_do_layout._how_do_i_know_what_value_to_use_for_the_footprint_attribute" class="toc">I want to use PCB to do layout. How do I know what value to use for the footprint attribute?</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#newlib" class="toc">Newlib</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#m4_library" class="toc">M4 library</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#what_is_the_recommended_way_to_deal_with_different_footprints_for_the_same_sort_of_device" class="toc">What is the recommended way to deal with different footprints for the same sort of device?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_draw_a_new_footprint" class="toc">How do I draw a new footprint?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_edit_change_an_existing_footprint" class="toc">How do I edit/change an existing footprint?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#what_is_the_proper_way_to_make_a_double-sided_footprint" class="toc">What is the proper way to make a double-sided footprint?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_add_a_footprint_library_to_pcb" class="toc">How do I add a footprint library to PCB?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_update_a_footprint_in_my_layout" class="toc">How do I update a footprint in my layout?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#pcb_is_not_finding_my_footprints._why" class="toc">PCB is not finding my footprints. Why?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#now_that_i_have_all_of_these_footprints_where_do_i_put_them" class="toc">Now that I have all of these footprints where do I put them?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#what_s_this_business_about_flashed_pads" class="toc">What's this business about flashed pads?</a></span></div></li>
+</ul>
+</li>
+<li class="level1"><div class="li"><span class="li"><a href="#component_placement" class="toc">Component placement</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_rotate_a_selection_i.e._of_more_than_one_item" class="toc">How do I rotate a selection (i.e. of more than one item)?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_rotate_objects_by_an_arbitrary_angle" class="toc">How do I rotate objects by an arbitrary angle?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_move_objects_by_an_arbitrary_distance" class="toc">How do I move objects by an arbitrary distance?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_move_objects_to_an_absolute_location" class="toc">How do I move objects to an absolute location?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_change_the_size_of_a_graphical_object_such_as_text_silkscreen_lines_etc" class="toc">How do I change the size of a graphical object (such as text, silkscreen lines, etc)?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_put_components_on_both_faces_in_pcb" class="toc">How do I put components on both faces in PCB?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#i_cant_t_move_the_components_on_the_other_side_of_the_board" class="toc">I cant't move the components on the other side of the board!</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_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>
+<li class="level2"><div class="li"><span class="li"><a href="#i_want_to_draw_a_track_between_two_segments_on_the_same_net_but_pcb_won_t_let_me_why" class="toc">I want to draw a track between two segments on the same net, but PCB won't let me! Why?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#pcb_seems_to_munge_my_components_names_and_complains_that_it_can_t_find_proper_nets_for_the_pins_how_come" class="toc">PCB seems to munge my components names and complains that it can't find proper nets for the pins! How come?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_can_i_set_color_and_thickness_of_the_rats_nests" class="toc">How can I set color and thickness of the rats nests?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#where_is_that_last_remaining_rat" class="toc">Where is that last remaining rat?</a></span></div></li>
+</ul>
+</li>
+<li class="level1"><div class="li"><span class="li"><a href="#beyond_tracks_and_footprints" class="toc">Beyond tracks and footprints</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_trace_a_drawing_a_print_or_another_pcb" class="toc">How do I trace a drawing, a print, or another PCB?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#i_can_t_copy_component_pads_in_a_layout._what_gives" class="toc">I can't copy component pads in a layout. What gives?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_fill_areas_with_copper" class="toc">How do I fill areas with copper?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_can_i_assign_my_polygon_to_a_net" class="toc">How can I assign my polygon to a net?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_can_i_connect_tracks_pads_or_vias_to_my_polygon" class="toc">How can I connect tracks, pads, or vias to my polygon?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#the_polygons_are_shorting_my_tracks_what_can_i_do_about_it" class="toc">The polygons are shorting my tracks! What can I do about it?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_change_polygon_clearance" class="toc">How do I change polygon clearance?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_hide_the_polygons_while_i_edit_the_layout" class="toc">How do I hide the polygons while I edit the layout?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#polygons_are_making_the_gui_sluggish._what_i_can_do_about_it" class="toc">Polygons are making the GUI sluggish. What I can do about it?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#after_i_defined_those_ground_planes_pcb_takes_ages_to_load._how_come" class="toc">After I defined those ground planes, pcb takes ages to load. How come?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_edit_polygons" class="toc">How do I edit polygons?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_place_vias_that_connect_to_a_polygon_for_full_thermal_dissipation_or_full_shielding_integrity" class="toc">How do I place vias that connect to a polygon for full thermal dissipation or full shielding integrity?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#can_polygons_be_un-masked_can_a_polygon_be_made_bare-copper_with_no_solder_mask" class="toc">Can polygons be un-masked? (Can a polygon be made bare-copper with no solder mask?)</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_place_mounting_holes" class="toc">How do I place mounting holes?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#why_is_it_possible_to_make_a_thermal_for_pin_but_not_for_a_pad" class="toc">Why is it possible to make a thermal for pin, but not for a pad?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#can_pcb_be_used_to_make_single_layer_boards" class="toc">Can PCB be used to make single layer boards?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#what_resources_exist_to_process_pcb_files_using_scripts" class="toc">What resources exist to process PCB files using scripts?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_import_external_vector_graphics" class="toc">How do I import external vector graphics?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#is_there_a_way_to_import_a_dxf_drawing_from_mechanical_cad_applications" class="toc">Is there a way to import a DXF drawing from mechanical CAD applications?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#what_is_the_best_way_to_do_weird_footprints" class="toc">What is the best way to do weird footprints?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_attach_a_name_to_my_layout" class="toc">How Do I attach a name to my layout?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#is_there_a_way_to_do_multiple_instances_of_a_subcircuits" class="toc">Is there a way to do multiple instances of a subcircuits?</a></span></div></li>
+</ul>
+</li>
+<li class="level1"><div class="li"><span class="li"><a href="#auto_router" class="toc">Auto Router</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_make_the_most_of_the_auto_router" class="toc">How do I make the most of the auto router?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_force_the_autorouter_to_only_put_traces_on_a_particular_layer" class="toc">How do I force the autorouter to only put traces on a particular layer?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_make_autorouter_leave_particular_nets_alone" class="toc">How do I make autorouter leave particular nets alone?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_force_the_autorouter_to_route_only_within_my_pcb_outline" class="toc">How do I force the autorouter to route only within my pcb outline?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_route_power_and_ground_planes_with_the_autorouter" class="toc">How do I route power and ground planes with the autorouter?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#the_layout_produced_by_the_autorouter_is_inefficient" class="toc">The layout produced by the autorouter is inefficient!</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#the_layout_produced_by_the_autorouter_is_ugly" class="toc">The layout produced by the autorouter is ugly!</a></span></div></li>
+</ul>
+</li>
+<li class="level1"><div class="li"><span class="li"><a href="#gerber_files_prints_and_other_i_o_issues" class="toc">Gerber files, prints and other I/O issues</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#is_is_possible_to_produce_output_without_gui_intervention" class="toc">Is is possible to produce output without GUI intervention?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_make_a_board_outline_to_go_with_my_gerbers_to_the_board_maker" class="toc">How do I make a board outline to go with my gerbers to the board maker?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#yes_i_tried_that_but_the_gerber_exporter_didn_t_give_me_an_outline_file._why" class="toc">Yes, I tried that, but the gerber exporter didn't give me an outline file. Why?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_make_sure_that_the_design_contains_only_certain_hole_sizes" class="toc">How do I make sure, that the design contains only certain hole sizes?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#i_m_done_with_my_layout._how_should_i_check_my_design" class="toc">I'm done with my layout. How should I check my design?</a></span></div></li>
+</ul>
+</li>
+<li class="level1"><div class="li"><span class="li"><a href="#exporting_other_formatsraster_and_ps_files" class="toc">Exporting Other Formats: Raster and PS Files</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#what_is_xy-max_in_the_png_export_dialog_box" class="toc">What is xy-max in the PNG export dialog box?</a></span></div></li>
+</ul>
+</li>
+<li class="level1"><div class="li"><span class="li"><a href="#customization" class="toc">Customization</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#i_don_t_like_that_old-style_black_background._how_can_i_get_a_light_canvas" class="toc">I don't like that old-style black background. How can I get a light canvas?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_set_the_default_values_of_the_postscript_dialog" class="toc">How do I set the default values of the postscript dialog?</a></span></div></li>
+</ul>
+</li>
+<li class="level1"><div class="li"><span class="li"><a href="#you_didn_t_answer_my_question._what_other_resources_exist_for_pcb_information" class="toc">You didn't answer my question. What other resources exist for PCB information?</a></span></div></li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="about_pcb_layout_and_routing" id="about_pcb_layout_and_routing">About PCB layout and routing</a></h1>
+<div class="level1">
+
+<p>
+This section answers general questions about PCB technology. If youâ??re just beginning to learn about electronics, you might benefit from some of the answers given here.
+</p>
+
+</div>
+<!-- SECTION "About PCB layout and routing" [1-214] -->
+<h2><a name="what_s_a_footprint_what_s_a_via_what_s_a_track" id="what_s_a_footprint_what_s_a_via_what_s_a_track">What's a footprint? What's a via? What's a track?</a></h2>
+<div class="level2">
+
+<p>
+You can find a glossary of terms <a href="http://geda.seul.org/wiki/geda:glossary"; class="urlextern" title="http://geda.seul.org/wiki/geda:glossary"; rel="nofollow">here</a>.
+</p>
+
+</div>
+<!-- SECTION "What's a footprint? What's a via? What's a track?" [215-360] -->
+<h1><a name="pcb_tools" id="pcb_tools">PCB Tools</a></h1>
+<div class="level1">
+
+<p>
+This section provides answers about the open-source layout tool â??PCBâ?? itself.
+</p>
+
+</div>
+<!-- SECTION "PCB Tools" [361-463] -->
+<h2><a name="where_can_i_read_about_the_basics_of_using_pcb" id="where_can_i_read_about_the_basics_of_using_pcb">Where can I read about the basics of using pcb?</a></h2>
+<div class="level2">
+
+<p>
+The <a href="http://pcb.sourceforge.net/manual.html"; class="urlextern" title="http://pcb.sourceforge.net/manual.html"; rel="nofollow">pcb manual</a> contains a concise description of the user interface in the section â??Getting Startedâ??(<a href="http://pcb.sourceforge.net/pcb-20060822/pcb.html#Getting%20Started"; class="urlextern" title="http://pcb.sourceforge.net/pcb-20060822/pcb.html#Getting%20Started"; rel="nofollow">version 20060822</a>)
+</p>
+
+</div>
+<!-- SECTION "Where can I read about the basics of using pcb?" [464-761] -->
+<h2><a name="i_found_a_bug_what_can_i_do_about_it" id="i_found_a_bug_what_can_i_do_about_it">I found a bug! What can I do about it?</a></h2>
+<div class="level2">
+<ol>
+<li class="level1"><div class="li"> Start by reading <a href="http://pcb.sourceforge.net/bugs.html"; class="urlextern" title="http://pcb.sourceforge.net/bugs.html"; rel="nofollow">the pcb bug reporting page</a>.</div>
+</li>
+<li class="level1"><div class="li"> Check, what it needs to reproduce the bug.</div>
+</li>
+<li class="level1"><div class="li"> Ask on the <a href="http://www.geda.seul.org/mailinglist/index.html"; class="urlextern" title="http://www.geda.seul.org/mailinglist/index.html"; rel="nofollow">geda-user mailing</a> list if there is a work around, or has been dealt with in the bleading edge version of pcb. Note that you must subscribe to the geda-user e-mail list before you can post to this list.</div>
+</li>
+<li class="level1"><div class="li"> Check, wether the issue is already in the <a href="http://sourceforge.net/tracker/?group_id=73743&atid=538811"; class="urlextern" title="http://sourceforge.net/tracker/?group_id=73743&atid=538811"; rel="nofollow">bug tracking system of pcb</a>. If not, file a bug report. Make sure to give every information necessary to reproduce the bug and add the version of pcb that contains the bug.</div>
+</li>
+<li class="level1"><div class="li"> Finally, as with all open source projects, you may flex your programming muscles and try to squish the bug yourself. Please file a patch of the changes you had to make to the <a href="http://sourceforge.net/tracker/?group_id=73743&atid=538811"; class="urlextern" title="http://sourceforge.net/tracker/?group_id=73743&atid=538811"; rel="nofollow">BTS of pcb</a>. The patch will be gladly accepted to improve the next release of pcb.</div>
+</li>
+</ol>
+
+</div>
+<!-- SECTION "I found a bug! What can I do about it?" [762-1824] -->
+<h2><a name="how_can_i_set_the_manufacturing_rules_to_use_i.e._drill_diameters_trace_width_space_specs" id="how_can_i_set_the_manufacturing_rules_to_use_i.e._drill_diameters_trace_width_space_specs">How can I set the manufacturing rules to use (i.e. drill diameters, trace width/space specs)?</a></h2>
+<div class="level2">
+
+<p>
+This topic is covered <a href="http://pcb.sourceforge.net/pcb-20060422/pcb.html#Vendor%20drill%20mapping"; class="urlextern" title="http://pcb.sourceforge.net/pcb-20060422/pcb.html#Vendor%20drill%20mapping"; rel="nofollow">in the documentation available at the PCB website</a>.
+</p>
+
+</div>
+<!-- SECTION "How can I set the manufacturing rules to use (i.e. drill diameters, trace width/space specs)?" [1825-2082] -->
+<h1><a name="non-obvious_aspects_of_the_gui" id="non-obvious_aspects_of_the_gui">Non-obvious aspects of the GUI</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "Non-obvious aspects of the GUI" [2083-2128] -->
+<h2><a name="auto-pan_bugs_me._what_can_i_do_about_it" id="auto-pan_bugs_me._what_can_i_do_about_it">Auto-pan bugs me. What can I do about it?</a></h2>
+<div class="level2">
+<ul>
+<li class="level1"><div class="li"> You can tell, whether the screen will auto-pan by looking for little squares at the end of the cross hair cursor.</div>
+</li>
+<li class="level1"><div class="li"> Auto-pan can be toggled during move with a right mouse button click.</div>
+</li>
+<li class="level1"><div class="li"> Auto-pan speed can be set in <code>$HOME/.pcb/preferences</code> </div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Auto-pan bugs me. What can I do about it?" [2129-2436] -->
+<h2><a name="the_delete_key_sometimes_refuses_to_delete" id="the_delete_key_sometimes_refuses_to_delete">The delete key sometimes refuses to delete</a></h2>
+<div class="level2">
+
+<p>
+Probably you try to delete a selected object. In pcb the delete button does not act on the selection, but on the object currently under the mouse. Consequently nothing will be deleted if an object is selected and the mouse hovers at some other place. Bottom line: Just position the mouse over an object and press the delete button. No need to select the object.
+</p>
+
+<p>
+However, the Select menu contains an action that lets you delete the current selection. Currently, there is no accel key attached to this action.
+</p>
+
+<p>
+Note, for versions younger than summer 2007 this issue is resolved. The delete key acts on selected objects too.
+</p>
+
+</div>
+<!-- SECTION "The delete key sometimes refuses to delete" [2437-3115] -->
+<h2><a name="i_try_to_move_an_object_but_pcb_won_t_let_me_what_can_i_do_about_it" id="i_try_to_move_an_object_but_pcb_won_t_let_me_what_can_i_do_about_it">I try to move an object, but pcb won't let me! What can I do about it?</a></h2>
+<div class="level2">
+
+<p>
+Most probably the object is locked. To see, wether it indeeed is, select-all-connected-objects from the select menu. Locked objects wonâ??t highlight. Use the lock tool to unlock the object in question. Note, that the lock tool always toggles the lock state of the object you click at. Afterwards an n object report pops up that contains the lock state in the last line.
+</p>
+
+<p>
+If you want to remove all locks, you may consider to remove all occurences of the string <em>lock</em> in the *.pcb file with your favorite ascii editor.
+</p>
+
+</div>
+<!-- SECTION "I try to move an object, but pcb won't let me! What can I do about it?" [3116-3721] -->
+<h1><a name="footprint_issues" id="footprint_issues">Footprint issues</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "Footprint issues" [3722-3753] -->
+<h2><a name="how_do_pcb_s_footprints_work" id="how_do_pcb_s_footprints_work">How do PCB's footprints work?</a></h2>
+<div class="level2">
+
+<p>
+PCB supports two entirely separate footprint library mechanisms:
+</p>
+<ol>
+<li class="level1"><div class="li"> The first is referred to as the â??oldlibâ??, â??pcblibâ??, or the â??M4 libraryâ??. This system uses the macro language M4 to generate footprints on the fly. The M4 library is fairly large. A powerful feature of the m4 library is that an entire family of footprints can quickly be defined by defining an appropriate base macro. Several standard families of footprints exist in pcblib. Starting with the pcb-20070208 snapshot, the entire m4 library is available as â??newlibâ?? footprints (see the following paragraph) under the name â??pcblib-newlibâ??.</div>
+</li>
+<li class="level1"><div class="li"> The second footprint library for PCB is called the â??newlibâ??. Newlib footprints are defined using <acronym title="American Standard Code for Information Interchange">ASCII</acronym> text files which call out each graphical primitive which makes up an entire footprint. Newlib footprints can either be created graphically using PCB or via any other method which can produce a text file (text editor, awk/perl/ruby script, etc.). The use of a scripting or programming language is especially powerful because you can generate large footprints or families of footprints.</div>
+</li>
+</ol>
+
+<p>
+ Therefore, during layout, you can use footprints which are distributed with PCB, you can find footprints via a web search, or you can create your own, and put them in a dedicated directory. The <a href="http://pcb.sourceforge.net/manual.html"; class="urlextern" title="http://pcb.sourceforge.net/manual.html"; rel="nofollow">pcb manual</a> has complete and up to date documentation for the element file format. <a href="http://gedasymbols.org"; class="urlextern" title="http://gedasymbols.org"; rel="nofollow">Gedasymbols.org</a> has a number of user contributed footprints. A somewhat incomplete but useful tutorial is available on the web at: <a href="http://www.brorson.com/gEDA/"; class="urlextern" title="http://www.brorson.com/gEDA/"; rel="nofollow">http://www.brorson.com/gEDA/</a> (search for the term â??newlibâ??).
+</p>
+
+</div>
+<!-- SECTION "How do PCB's footprints work?" [3754-5458] -->
+<h2><a name="where_can_i_get_pre-drawn_footprints_for_pcb" id="where_can_i_get_pre-drawn_footprints_for_pcb">Where can I get pre-drawn footprints for PCB?</a></h2>
+<div class="level2">
+
+<p>
+Currently, the best place to get footprints (besides in the PCB distribution) is the <a href="http://www.gedasymbols.org"; class="urlextern" title="http://www.gedasymbols.org"; rel="nofollow">gEDA Symbols website</a>. <a href="http://www.luciani.org/geda/pcb/pcb-footprint-list.html"; class="urlextern" title="http://www.luciani.org/geda/pcb/pcb-footprint-list.html"; rel="nofollow">John Luciani's website</a> has a large number of footprints and tools. Also, Darrell Harmon provides a nice footprint generating script <a href="http://www.dlharmon.com/geda/footgen.html"; class="urlextern" title="http://www.dlharmon.com/geda/footgen.html"; rel="nofollow">on his website</a>. You are welcome to contribute to the project and share your footprints. Finally, you can ask on the geda-user list, and somebody might take pity on you and send you a symbol. Note that you must subscribe to the geda-user e-mail list before you can post an e-mail to the geda-user list.
+</p>
+
+</div>
+<!-- SECTION "Where can I get pre-drawn footprints for PCB?" [5459-6197] -->
+<h2><a name="i_want_to_use_pcb_to_do_layout._how_do_i_know_what_value_to_use_for_the_footprint_attribute" id="i_want_to_use_pcb_to_do_layout._how_do_i_know_what_value_to_use_for_the_footprint_attribute">I want to use PCB to do layout. How do I know what value to use for the footprint attribute?</a></h2>
+<div class="level2">
+
+<p>
+This question is a common one amongst new gEDA users. Indeed, helping newbies determine the appropriate footprint names lies at the core of the ongoing <a href="geda-faq-gschem.html#what_s_this_business_about_heavy_vs._light_symbols" class="wikilink1" title="geda-faq-gschem.html">light vs. heavy symbol</a> debate. In the current, light symbol gEDA/gaf distribution, you need to attach the footprint attribute at the schematic level (i.e. using either gschem or gattrib). The name of the footprint to use depends upon whether you are using the newlib or the M4 library (pcblib).
+</p>
+
+</div>
+<!-- SECTION "I want to use PCB to do layout. How do I know what value to use for the footprint attribute?" [6198-6821] -->
+<h3><a name="newlib" id="newlib">Newlib</a></h3>
+<div class="level3">
+
+<p>
+The newlib stores one footprint per file, and the footprint names used by the newlib are the file names of the footprint files.
+</p>
+
+<p>
+There are several ways to determine the newlib footprint names to use:
+</p>
+<ul>
+<li class="level1"><div class="li"> You can browse the available footprints by running pcb and opening the footprint library window (available from the menu bar via â??Window â?? libraryâ??). Click on the â??newlibâ?? library group, and then select a sublibrary to browse its symbols. The name of each footprint appears in the â??Elementsâ?? window on the right hand side of the footprint library browser. Use the name exactly as it appears in the browser for the footprint attribute in gschem or gattrib.</div>
+</li>
+<li class="level1"><div class="li"> The newlib footprints distributed with PCB are stored in the directories under <strong><code>${PREFIX}/share/pcb/newlib</code></strong>. (<strong><code>${PREFIX}</code></strong> is the install directory you specified when configuring/building PCB.) The name to stick in the â??footprintâ?? attribute is the filename of the footprint you wish to use.<br/>
+ For example, on my machine I installed gEDA with the prefix <strong><code>/usr/local/geda/</code></strong>. The 0805 package (for SMT resistors or caps) lives in a file with absolute path<br/>
+ <strong><code>/usr/local/geda/share/pcb/newlib/generic_SMD_packages/0805_reflow_solder</code></strong> <br/>
+ Therefore, to use this footprint on a component I set its â??footprintâ?? attribute to <strong><code>0805_reflow_solder</code></strong> using gschem or gattrib.<br/>
+ Note that if the newlib symbol you want to use lives in a non-standard directory, gsch2pcb needs you to specify a path to that directory, either within your project.rc file (if you use one) or using the <strong><code>â??elements-dir</code></strong> flag (from the command line).</div>
+</li>
+<li class="level1"><div class="li"> Finally, since each new design typically requires you to draw at least a couple of new footprints, itâ??s likely you will have a local â??footprintsâ?? directory. As previously, the footprint name to use is the filename you assign to each of your new footprints. Again, donâ??t forget to add a line to your project.rc file telling gsch2pcb where to find your local footprints. Alternately, you can run gsch2pcb with the <strong><code>â??elements-dir</code></strong> flag set to point to your local footprint directory.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Newlib" [6822-8976] -->
+<h3><a name="m4_library" id="m4_library">M4 library</a></h3>
+<div class="level3">
+
+<p>
+The M4 library stores the footprints as M4 macros; there are usually several (many) footprints contained in each footprint file. The different footprints in a single file are generally variations on a single pattern (e.g. DIP-8, DIP-14, DIP-16, etc.) The easiest way to find the correct footprint attribute name is by browsing through the â??pcblibâ?? library in the PCB library window. The footprint attribute is given in square brackets in the description. Also you can view the list of footprints from pcblib at the <a href="http://www.gedasymbols.org/footprints/"; class="urlextern" title="http://www.gedasymbols.org/footprints/"; rel="nofollow">gEDA Symbols webpage</a>.
+</p>
+
+<p>
+The following m4 libraries have received more attention and improvements than the others:
+</p>
+<ul>
+<li class="level1"><div class="li"> ~amp for Amp connectors</div>
+</li>
+<li class="level1"><div class="li"> ~amphenol for Amphenol connectors</div>
+</li>
+<li class="level1"><div class="li"> ~geda for many diverse parts used in basic design using gEDA (resistors, caps, etc).</div>
+</li>
+<li class="level1"><div class="li"> ~bourns for products like trim pots from Bourns</div>
+</li>
+<li class="level1"><div class="li"> ~cts for products like resistor packs from CTS</div>
+</li>
+<li class="level1"><div class="li"> ~johnstech for Johnstech sockets</div>
+</li>
+<li class="level1"><div class="li"> ~minicircuits for Minicircuits specific footprints</div>
+</li>
+<li class="level1"><div class="li"> ~panasonic for some Panasonic specific footprints</div>
+</li>
+</ul>
+
+<p>
+ Finally, for both the newlib and the M4 lib, it is extremely important that you verify that the footprint name you use instantiates *exactly* the footprint you want when you place it in PCB. Therefore, it is critical to inspect the footprint before you use it. You can verify the footprint you want to use by clicking on it in the â??footprint libraryâ?? window, and then placing it onto an empty spot in PCBâ??s drawing area. Manually inspect the footprint to ensure that it has the correct number of pins/pads, correct dimensions, etc.
+</p>
+
+<p>
+Also, once you generate Gerber files, make sure you <a href="geda-pcb_tips.html#i_m_done_with_my_layout._how_should_i_check_my_design" class="wikilink1" title="geda-pcb_tips.html">inspect all footprints instantiated in your Gerbers</a> using gerbv (or an equivalent Gerber viewer) before you send your design out for fabrication.
+</p>
+
+</div>
+<!-- SECTION "M4 library" [8977-10886] -->
+<h2><a name="what_is_the_recommended_way_to_deal_with_different_footprints_for_the_same_sort_of_device" id="what_is_the_recommended_way_to_deal_with_different_footprints_for_the_same_sort_of_device">What is the recommended way to deal with different footprints for the same sort of device?</a></h2>
+<div class="level2">
+
+<p>
+For example, an opamp may be DIP8 or SO8. A resistor may be 0603, 0805, 1208, or through-hole. How do I know what package and footprint to use, and how do I manage the choices?
+</p>
+
+<p>
+First off, the footprint you should use is a decision for you to make, not your CAD tool. It is up to you to choose your preferred package type/footprint, and then attach the correct footprint attribute to the component in the schematic. Once you have choosen which package (and footprint) you wish to use, then either <a href="geda-pcb_tips.html#where_can_i_get_pre-drawn_footprints_for_pcb" class="wikilink1" title="geda-pcb_tips.html">find an appropriate footprint</a>, or <a href="geda-pcb_tips.html#how_do_i_draw_a_new_footprint" class="wikilink1" title="geda-pcb_tips.html">draw one yourself</a> and save it in a local directory.
+</p>
+
+<p>
+As far as managing the footprint choices (and indeed the large number of component attributes you are likely to have): Use <a href="geda-faq-attribs.html#help_my_design_has_hundreds_of_components_and_it_s_a_pain_to_use_gschem_to_attach_all_my_attributes" class="wikilink1" title="geda-faq-attribs.html">gattrib</a>. Thatâ??s what itâ??s for.
+</p>
+
+</div>
+<!-- SECTION "What is the recommended way to deal with different footprints for the same sort of device?" [10887-11968] -->
+<h2><a name="how_do_i_draw_a_new_footprint" id="how_do_i_draw_a_new_footprint">How do I draw a new footprint?</a></h2>
+<div class="level2">
+
+<p>
+Everybody does this a little differently. Some people draw the footprint entirely using PCB. Some people first draw a preliminary footprint in PCB, and then finish it off by hand editing it (e.g. using emacs). Some people write <acronym title="Practical Extraction and Report Language">Perl</acronym> or Python scripts to autogenerate footprints.
+</p>
+<ul>
+<li class="level1"><div class="li"> use a text editor. See <a href="http://www.brorson.com/gEDA/land_patterns_20070818.pdf"; class="urlextern" title="http://www.brorson.com/gEDA/land_patterns_20070818.pdf"; rel="nofollow"> the manual on footprint creation</a> by Stuart Brorson for the details.</div>
+</li>
+<li class="level1"><div class="li"> draw the part in PCB and save as a footprint. See the <a href="http://ronja.twibright.com/guidelines/footprints.php"; class="urlextern" title="http://ronja.twibright.com/guidelines/footprints.php"; rel="nofollow">howto by Karel Kulhavy</a></div>
+</li>
+<li class="level1"><div class="li"> or use a <a href="http://dlharmon.com/geda/footgen.html"; class="urlextern" title="http://dlharmon.com/geda/footgen.html"; rel="nofollow"> python script</a> by Darrel Harmon for â??two padâ??, â??SOxxâ??, â??tabbedâ?? and QFPâ?? style</div>
+</li>
+<li class="level1"><div class="li"> or use a <a href="http://www.brorson.com/gEDA"; class="urlextern" title="http://www.brorson.com/gEDA"; rel="nofollow"> perl script</a> by Stuart Brorson for two pad SMT components</div>
+</li>
+<li class="level1"><div class="li"> or use a <a href="http://www.luciani.org/geda/pcb/pcb-perl-library.html"; class="urlextern" title="http://www.luciani.org/geda/pcb/pcb-perl-library.html"; rel="nofollow">perl script</a> from John Luciani – can be adapted to DIL, SOxx-Style, QFP, or even circular arrangement of pads. </div>
+</li>
+<li class="level1"><div class="li"> or use the web based application <a href="http://www.gedasymbols.org/user/dj_delorie/tools/dilpad.html"; class="urlextern" title="http://www.gedasymbols.org/user/dj_delorie/tools/dilpad.html"; rel="nofollow">dilpad</a> written by DJ Delorie for â??SOxxâ?? style footprints.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "How do I draw a new footprint?" [11969-13166] -->
+<h2><a name="how_do_i_edit_change_an_existing_footprint" id="how_do_i_edit_change_an_existing_footprint">How do I edit/change an existing footprint?</a></h2>
+<div class="level2">
+
+<p>
+You can convert a footprint into a ordinary layout, edit the parts and convert them back to footprint. In the following list the parts in mono space font are actions from the buffer menu.
+</p>
+<ol>
+<li class="level1"><div class="li"> Select element</div>
+</li>
+<li class="level1"><div class="li"> Copy selection to buffer</div>
+</li>
+<li class="level1"><div class="li"> <code>Break buffer into pieces</code></div>
+</li>
+<li class="level1"><div class="li"> <code>Paste buffer to layout</code></div>
+</li>
+<li class="level1"><div class="li"> Do the desired changes</div>
+</li>
+<li class="level1"><div class="li"> Select all objects that belong to the footprint</div>
+</li>
+<li class="level1"><div class="li"> <code>Copy selection to buffer</code></div>
+</li>
+<li class="level1"><div class="li"> <code>Convert buffer to element</code></div>
+</li>
+<li class="level1"><div class="li"> <code>Paste buffer to layout</code></div>
+</li>
+<li class="level1"><div class="li"> Place the mouse over the pads that got rounded during step 4 and press q. This squares off the rounded pad edges.</div>
+</li>
+<li class="level1"><div class="li"> Go over every pad, press n and give a name to the pad</div>
+</li>
+<li class="level1"><div class="li"> Select everything and <code>copy selection to buffer</code></div>
+</li>
+<li class="level1"><div class="li"> <code>Save buffer as elements to file</code>. The footprint file will created at the path where pcb was called.</div>
+</li>
+</ol>
+
+<p>
+Alternatively, you can use your favorite text editor and edit the source code of the footprint.
+</p>
+
+</div>
+<!-- SECTION "How do I edit/change an existing footprint?" [13167-14134] -->
+<h2><a name="what_is_the_proper_way_to_make_a_double-sided_footprint" id="what_is_the_proper_way_to_make_a_double-sided_footprint">What is the proper way to make a double-sided footprint?</a></h2>
+<div class="level2">
+
+<p>
+You can use the â??onsolderâ?? flag to place pads on the opposite side of the board. You would have something like this for a connector on both sides of the board:
+</p>
+
+<p>
+<code>Pad[-40000 -7000 -40000 7000 2700 2400 3000 â??B1â?? â??B1â?? â??squareâ??]</code><br/>
+ <code>Pad[-40000 -7000 -40000 3000 2700 2400 3000 â??A1â?? â??A1â?? â??square,onsolderâ??]</code>
+</p>
+
+<p>
+If you draw the footprint with pcb-<acronym title="Graphical User Interface">GUI</acronym> and do convert-buffer-to-element, the lines on the second layer become pads with the onsolder flag. Yes, it is the second layer, regardless its name.
+</p>
+
+</div>
+<!-- SECTION "What is the proper way to make a double-sided footprint?" [14135-14704] -->
+<h2><a name="how_do_i_add_a_footprint_library_to_pcb" id="how_do_i_add_a_footprint_library_to_pcb">How do I add a footprint library to PCB?</a></h2>
+<div class="level2">
+
+<p>
+Adding footprint libraries can be done from the <acronym title="Graphical User Interface">GUI</acronym>:<br/>
+ <strong><em>File</em></strong> â??> <strong><em>Preferences</em></strong> â??> <strong><em>Library</em></strong> â??> <strong>FOOTPRINTDIRECTORY</strong><br/>
+ Alternatively you can edit the file <code>$HOME/.pcb/preferences</code>. Make sure, no instance of pcb is currently running. Look for the line that starts with â??library-newlibâ??. Donâ??t forget to include the new directory into either your gsch2pcbrc, or your local gafrc file (if you are using gsch2pcb, that is).
+</p>
+
+</div>
+<!-- SECTION "How do I add a footprint library to PCB?" [14705-15210] -->
+<h2><a name="how_do_i_update_a_footprint_in_my_layout" id="how_do_i_update_a_footprint_in_my_layout">How do I update a footprint in my layout?</a></h2>
+<div class="level2">
+
+<p>
+There is no way to automatically replace all instances of a footprint with the new version, yet. But there is a special mode of the buffer-paste tool, that will reduce the amount of clicks for manual replacement.<br/>
+ Use the Window→Library dialog box to manually choose the new footprint. The tool becomes the buffer-paste tool, with the new footprint preloaded. Rotate it if needed with Buffer→Rotate Buffer. Position the new footprint over the old one, and shift-left-mouse-click to replace the old footprint with the new one. Watch out for being 180 degrees off, use â??oâ?? to check the rats nest after each placement, and undo if it appears you placed it backwards.
+</p>
+
+</div>
+<!-- SECTION "How do I update a footprint in my layout?" [15211-15933] -->
+<h2><a name="pcb_is_not_finding_my_footprints._why" id="pcb_is_not_finding_my_footprints._why">PCB is not finding my footprints. Why?</a></h2>
+<div class="level2">
+
+<p>
+The footprint path that PCB uses is defined using the <strong><code>Pcb.elementPath</code></strong> variable in the app-defaults file named <strong><code>PCB</code></strong>. The path for the <strong><code>PCB</code></strong> file is set using the <strong><code>XAPPLRESDIR</code></strong> environment variable which is typically set from within the wrapper script named <strong><code>pcb</code></strong>.
+</p>
+
+</div>
+<!-- SECTION "PCB is not finding my footprints. Why?" [15934-16282] -->
+<h2><a name="now_that_i_have_all_of_these_footprints_where_do_i_put_them" id="now_that_i_have_all_of_these_footprints_where_do_i_put_them">Now that I have all of these footprints where do I put them?</a></h2>
+<div class="level2">
+
+<p>
+I prefer to place all â??production-readyâ?? footprints in a single directory that is not in the gEDA/PCB install tree. When a new version of gEDA/PCB comes out I do not make any changes to project files or libraries. If there are newlib footprints in the PCB library that I want to use I copy them to the â??production-readyâ?? footprint directory.
+</p>
+
+<p>
+Rather than change configuration files to get gsch2pcb to find the footprints I create a wrapper script called <strong><code>sch2pcb</code></strong> that contains the footprint path. All users use the same script and access the same production footprints.
+</p>
+
+<p>
+To use the <strong><code>sch2pcb</code></strong> script that is listed below replace the string <strong><code>FOOTPRINT_DIR</code></strong> with your footprint directory:
+</p>
+<pre class="code">
+#!/bin/bash
+gsch2pcb --elements-dir FOOTPRINT_DIR $@
+</pre>
+
+<p>
+Or another userâ??s version:
+</p>
+<pre class="code">
+#!/bin/bash
+#this script was written by John Luciani
+gsch2pcb --elements-dir /home/user/pcb/footprints/user --use-files $@
+</pre>
+
+<p>
+Alternatively you can make use of a project file which gsch2pcb reads for its options. For example the file <code>myproject</code> could look like this:
+</p>
+<pre class="code">
+schematics myschematic.sch myschematic2.sch
+elements-dir /myfootprintdir
+output-name mypcb
+skip-m4
+</pre>
+
+<p>
+The example file searches through <code>myfootprintdir</code> for footprints used in <code>myschematic.sch</code> and <code>myschematic2.sch</code> and creates <code>mypcb.pcb</code> skipping m4 style footprints. gsch2pcb is then called with the project file as an option.
+</p>
+<pre class="code">
+gsch2pcb myproject
+</pre>
+
+</div>
+<!-- SECTION "Now that I have all of these footprints where do I put them?" [16283-17830] -->
+<h2><a name="what_s_this_business_about_flashed_pads" id="what_s_this_business_about_flashed_pads">What's this business about flashed pads?</a></h2>
+<div class="level2">
+
+<p>
+Pads may be â??flashedâ?? as opposed to â??drawnâ??. In the old days, the photo plotters had a big wheel with holes called apertures cut in it. The machine would turn the wheel to pick the correct aperture, position the film at the right place relative to the aperture and turn on a light that would shine through the aperture and expose the photo sensitive film behind. A â??flashedâ?? pad means that the pad shape and size exactly matched one of the apertures and to make a pad, youâ??d position the aperture over the pad location and flash the light (like a camera flash). A â??drawnâ?? pad by contrast is one where youâ??d use a small aperture, position it, turn on the light and then draw back and forth until you drew your pad shape. Think of this like taking a marker and coloring in a pad.
+</p>
+
+<p>
+Since these aperture wheels were physical things that had to be made, companies would typically have a set aperture list that theyâ??d use for everything so they wouldnâ??t have to buy a new aperture wheel every time they ordered boards. This is why the older RS274-D (â??gerberâ??) files did not include the aperture list but instead there would be a single aperture file that got used over and over.
+</p>
+
+<p>
+Now the plotters I believe are all laser plotters and the concept of flashed vs drawn doesnâ??t have much bearing on exactly what happens mechanically during photo plotting. Also, there is no problem with changing aperture lists all the time. This is part of why the newer RS274-X format with embedded aperture definitions exists. Still, youâ??ll see in RS274-X files that some pads are in fact specified as flashed vs drawn.
+</p>
+
+</div>
+<!-- SECTION "What's this business about flashed pads?" [17831-19490] -->
+<h1><a name="component_placement" id="component_placement">Component placement</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "Component placement" [19491-19525] -->
+<h2><a name="how_do_i_rotate_a_selection_i.e._of_more_than_one_item" id="how_do_i_rotate_a_selection_i.e._of_more_than_one_item">How do I rotate a selection (i.e. of more than one item)?</a></h2>
+<div class="level2">
+<ol>
+<li class="level1"><div class="li"> Select the items</div>
+</li>
+<li class="level1"><div class="li"> Buffer â?? Cut selection to buffer</div>
+</li>
+<li class="level1"><div class="li"> Buffer â?? Rotate buffer 90 deg CCW (or CW)</div>
+</li>
+<li class="level1"><div class="li"> Click anywhere on the board and the selection is pasted on the design again.</div>
+</li>
+</ol>
+
+<p>
+ Note: Square pads may not clear polygons correctly. Rectangular pads are ok, though. This is a known issue caused by the difficulty to know the reference direction of a square pad.
+</p>
+
+</div>
+<!-- SECTION "How do I rotate a selection (i.e. of more than one item)?" [19526-19969] -->
+<h2><a name="how_do_i_rotate_objects_by_an_arbitrary_angle" id="how_do_i_rotate_objects_by_an_arbitrary_angle">How do I rotate objects by an arbitrary angle?</a></h2>
+<div class="level2">
+<ol>
+<li class="level1"><div class="li"> Cut the object into the paste buffer.</div>
+</li>
+<li class="level1"><div class="li"> Type ":FreeRotateBuffer(45)". The colon will open the command line. Replace â??45â?? with the angle you want to rotate by.</div>
+</li>
+<li class="level1"><div class="li"> Paste the object back to your board.</div>
+</li>
+</ol>
+
+<p>
+ Note: For internal reasons, FreeRotateBuffer does not work with exact squares. As workaround use two or more polygons that add to give a square.
+</p>
+
+</div>
+<!-- SECTION "How do I rotate objects by an arbitrary angle?" [19970-20382] -->
+<h2><a name="how_do_i_move_objects_by_an_arbitrary_distance" id="how_do_i_move_objects_by_an_arbitrary_distance">How do I move objects by an arbitrary distance?</a></h2>
+<div class="level2">
+<ol>
+<li class="level1"><div class="li"> Let the mouse hover over the object to be moved.</div>
+</li>
+<li class="level1"><div class="li"> Type ":MoveObject(x,y,unit)". The colon will open the command line. Replace â??xâ?? and â??yâ?? with the desired coordinates and â??unitâ?? with either â??mmâ??, or â??milâ??.</div>
+</li>
+<li class="level1"><div class="li"> Type [return].</div>
+</li>
+</ol>
+
+<p>
+If both coordinates are prefixed with a "+", or "-" the move is relative to the current position. Else the object is moved to absolute coordinates.
+</p>
+
+</div>
+<!-- SECTION "How do I move objects by an arbitrary distance?" [20383-20824] -->
+<h2><a name="how_do_i_move_objects_to_an_absolute_location" id="how_do_i_move_objects_to_an_absolute_location">How do I move objects to an absolute location?</a></h2>
+<div class="level2">
+
+<p>
+Use the command â??MoveObject()" as described above.
+</p>
+
+</div>
+<!-- SECTION "How do I move objects to an absolute location?" [20825-20935] -->
+<h2><a name="how_do_i_change_the_size_of_a_graphical_object_such_as_text_silkscreen_lines_etc" id="how_do_i_change_the_size_of_a_graphical_object_such_as_text_silkscreen_lines_etc">How do I change the size of a graphical object (such as text, silkscreen lines, etc)?</a></h2>
+<div class="level2">
+<ul>
+<li class="level1"><div class="li"> Mouse over the object and hit [<strong><code>s</code></strong>]. This will increase the size of the object you are mousing over.</div>
+</li>
+<li class="level1"><div class="li"> Mouse over the object and hit [<strong><code><shift>-S</code></strong>]. This will decrease the size of the object you are mousing over.</div>
+</li>
+</ul>
+
+<p>
+ You can alter the increase/decrease quantum using the <strong><em>file</em></strong> â?? <strong><em>preferences</em></strong> â?? <strong><em>increments</em></strong> menu.
+</p>
+
+</div>
+<!-- SECTION "How do I change the size of a graphical object (such as text, silkscreen lines, etc)?" [20936-21387] -->
+<h2><a name="how_do_i_put_components_on_both_faces_in_pcb" id="how_do_i_put_components_on_both_faces_in_pcb">How do I put components on both faces in PCB?</a></h2>
+<div class="level2">
+
+<p>
+There are two ways to do it:
+</p>
+<ul>
+<li class="level1"><div class="li"> Pressing the tab key will alternate the active side between the component and solder sides. When you place components, they will go on the active side.</div>
+</li>
+<li class="level1"><div class="li"> If you are viewing one side of the board, place a component there and (with the cursor over it) press the [<strong><code>b</code></strong>] key (wich means, send the component to the Back side) the component go to the other side of the board.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "How do I put components on both faces in PCB?" [21388-21856] -->
+<h2><a name="i_cant_t_move_the_components_on_the_other_side_of_the_board" id="i_cant_t_move_the_components_on_the_other_side_of_the_board">I cant't move the components on the other side of the board!</a></h2>
+<div class="level2">
+
+<p>
+The mouse is only sensitive to components on the active side of the board. This prevents ampbiguities with components placed on both, top and bottom. By default, top side is active and the bottom side is the â??far sideâ?? whose components are ignored by the mouse. You can swap the roles of the sides to make components on the far side accessible. The key-accels [tab], [shift-tab], [ctrl-tab] and <a href="ctrl-shift-tab_will_do_the_trick._these_accels_combine_the_swap_with_different_vertical_and_horizontal_flips._specifically-tab_-swap_sides_and_mirror_along_horizontal_axis._this_is_like_flipping_a_real_board_upside-down._shift-tab_-swap_sides_and_mirror_along_vertical_axis._this_mimics_flipping_a_real_board_like_a_page_in_a_book._ctrl-tab_-swap_sides_and_mirror_along_both_axis._that_is_do_an_inversion._this_cannot_be_done_with_a_real_board_..._ctrl-shift-tab_-no_mirroring_just_swap_front_side_and_far_side._this_is_like_an_x-ray_view._how_do_i_know_which_side_a_component_sits_on_if_the_component_is_on_the_currrently_far_side_of_the_layout_its_silk_layer_is_drawn_in_grey._if_unsure_deactivate_the_far_side_with_the_far_side_button_at_the_bottom_of_the_layer_button_row._this_should_remove_the_silk_of_all_far_side_components_from_the_view._how_do_i_define_a_silkscreen_layer_for_the_other_side_of_the_board_although_only_one_silk_layer_button_is_visible_in_the_gui_silkscreen_for_both_sides_is_automatically_configured._in_default_view_the_silk_layer_button_refers_to_silkscreen_on_the_component_side_of_the_board._to_place_text_or_lines_on_solder_silk_you_have_to_flip_the_board_with_the_tab_key_or_shift-tab_if_you_prefer_a_left-right_flip_._this_is_like_physically_turning_the_board_to_the_other_side._it_turns_the_solder_layer_on_top_and_component_layer_on_bottom._objects_on_component_silk_layer_will_be_greyed_out._if_you_draw_to_silk_lines_will_always_go_to_the_current_top_silk_layer_which_is_solder_now._the_same_happens_to_components_and_their_silk_screen._flip_the_board_again_to_return_to_default_view._why_text_i_add_to_the_solder_side_not_reversed_add_it_while_the_board_is_flipped_tab_._just_selecting_the_solder_side_is_insufficient._new_text_always_reads_correctly_from_the_side_you_re_looking_at._is_it_possible_to_use_an_arbitrary_grid_spacing_yes._you_can_use_the_command_nowiki_setvalue_grid_value_unit_nowiki_._to_do_this-type_-setvalue_grid_x_unit_._the_colon_will_open_the_command_line._replace_x_with_the_desired_grid_spacing_and_unit_with_either_mm_or_mil_._-_type_return_._how_do_i_set_the_origin_in_pcb_the_absolute_origin_is_always_in_the_upper_left_corner_of_the_accessible_area._this_cannot_be_set_to_some_other_place._however_coordinates_of_objects_can_also_be_given_relative_to_the_current_grid._in_the_gtk2_version_of_pcb_coordinates_are_shown_in_the_upper_right_corner_of_the_main_window._the_right_pair_is_the_absolute_position_while_the_left_pair_reflects_the_position_relative_to_an_arbitrary_marker._this_marker_is_set_to_the_current_position_of_the_mouse_by_the_key_sequence_ctrl-m_._you_may_want_to_set_the_marker_to_a_grid_point_or_a_specific_pin._how_do_i_measure_distances_and_dimensions_of_components_use_ctrl-m_to_set_the_origin_and_read_the_distance_of_the_mouse_pointer_relative_to_this_point_on_the_upper_left_of_the_pcb_window._some_objects_like_vias_and_tracks_yield_usefull_information_in_object_reports._access_the_report_of_the_object_currently_under_the_mouse_pointer_with_ctrl-r_._how_do_i_hide_rats_of_specific_nets_in_the_netlist_window_doubleclick_on_the_specific_rat_name_then_press_o_on_your_board_window._your_rats_are_hidden_for_that_net._in_the_netlist_window_an_asterisk_appears_in_from_of_the_rat_name._to_reverse-follow_the_same_procedure._routing_how_do_i_route_a_connection_from_solder_to_component_side_and_back_while_using_the_line_tool_use_the_number_keys_on_top_of_the_keyboard_to_switch_layers._a_via_will_be_placed_automatically_at_the_endpoint_of_the_last_complete_segment._how_do_i_change_the_routing_style_there_is_a_set_of_predefined_sizes_for_routing._the_sets_bear_suggestive_names_signal_power_fat_and_skinny_._hit_the_button_route_style_to_configure_the_sizes_of_the_current_set_to_your_needs._you_can_set_the_names_and_the_default_values_of_these_parameter_sets_in_a_config_file_.pcb_settings_for_the_glossary.html" class="wikilink2" title="ctrl-shift-tab_will_do_the_trick._these_accels_combine_the_swap_with_different_vertical_and_horizontal_flips._specifically-tab_-swap_sides_and_mirror_along_horizontal_axis._this_is_like_flipping_a_real_board_upside-down._shift-tab_-swap_sides_and_mirror_along_vertical_axis._this_mimics_flipping_a_real_board_like_a_page_in_a_book._ctrl-tab_-swap_sides_and_mirror_along_both_axis._that_is_do_an_inversion._this_cannot_be_done_with_a_real_board_..._ctrl-shift-tab_-no_mirroring_just_swap_front_side_and_far_side._this_is_like_an_x-ray_view._how_do_i_know_which_side_a_component_sits_on_if_the_component_is_on_the_currrently_far_side_of_the_layout_its_silk_layer_is_drawn_in_grey._if_unsure_deactivate_the_far_side_with_the_far_side_button_at_the_bottom_of_the_layer_button_row._this_should_remove_the_silk_of_all_far_side_components_from_the_view._how_do_i_define_a_silkscreen_layer_for_the_other_side_of_the_board_although_only_one_silk_layer_button_is_visible_in_the_gui_silkscreen_for_both_sides_is_automatically_configured._in_default_view_the_silk_layer_button_refers_to_silkscreen_on_the_component_side_of_the_board._to_place_text_or_lines_on_solder_silk_you_have_to_flip_the_board_with_the_tab_key_or_shift-tab_if_you_prefer_a_left-right_flip_._this_is_like_physically_turning_the_board_to_the_other_side._it_turns_the_solder_layer_on_top_and_component_layer_on_bottom._objects_on_component_silk_layer_will_be_greyed_out._if_you_draw_to_silk_lines_will_always_go_to_the_current_top_silk_layer_which_is_solder_now._the_same_happens_to_components_and_their_silk_screen._flip_the_board_again_to_return_to_default_view._why_text_i_add_to_the_solder_side_not_reversed_add_it_while_the_board_is_flipped_tab_._just_selecting_the_solder_side_is_insufficient._new_text_always_reads_correctly_from_the_side_you_re_looking_at._is_it_possible_to_use_an_arbitrary_grid_spacing_yes._you_can_use_the_command_nowiki_setvalue_grid_value_unit_nowiki_._to_do_this-type_-setvalue_grid_x_unit_._the_colon_will_open_the_command_line._replace_x_with_the_desired_grid_spacing_and_unit_with_either_mm_or_mil_._-_type_return_._how_do_i_set_the_origin_in_pcb_the_absolute_origin_is_always_in_the_upper_left_corner_of_the_accessible_area._this_cannot_be_set_to_some_other_place._however_coordinates_of_objects_can_also_be_given_relative_to_the_current_grid._in_the_gtk2_version_of_pcb_coordinates_are_shown_in_the_upper_right_corner_of_the_main_window._the_right_pair_is_the_absolute_position_while_the_left_pair_reflects_the_position_relative_to_an_arbitrary_marker._this_marker_is_set_to_the_current_position_of_the_mouse_by_the_key_sequence_ctrl-m_._you_may_want_to_set_the_marker_to_a_grid_point_or_a_specific_pin._how_do_i_measure_distances_and_dimensions_of_components_use_ctrl-m_to_set_the_origin_and_read_the_distance_of_the_mouse_pointer_relative_to_this_point_on_the_upper_left_of_the_pcb_window._some_objects_like_vias_and_tracks_yield_usefull_information_in_object_reports._access_the_report_of_the_object_currently_under_the_mouse_pointer_with_ctrl-r_._how_do_i_hide_rats_of_specific_nets_in_the_netlist_window_doubleclick_on_the_specific_rat_name_then_press_o_on_your_board_window._your_rats_are_hidden_for_that_net._in_the_netlist_window_an_asterisk_appears_in_from_of_the_rat_name._to_reverse-follow_the_same_procedure._routing_how_do_i_route_a_connection_from_solder_to_component_side_and_back_while_using_the_line_tool_use_the_number_keys_on_top_of_the_keyboard_to_switch_layers._a_via_will_be_placed_automatically_at_the_endpoint_of_the_last_complete_segment._how_do_i_change_the_routing_style_there_is_a_set_of_predefined_sizes_for_routing._the_sets_bear_suggestive_names_signal_power_fat_and_skinny_._hit_the_button_route_style_to_configure_the_sizes_of_the_current_set_to_your_needs._you_can_set_the_names_and_the_default_values_of_these_parameter_sets_in_a_config_file_.pcb_settings_for_the_glossary.html">GTK-HID</a>, or ~/.Xdefaults for the <a href="geda-glossary.html" class="wikilink1" title="geda-glossary.html">Lesstif-HID</a>). Example for such a setting:
+</p>
+<pre class="code">
+route-styles = Signal,1000,3600,2000,1000:Power,2500,6000,3500,1000:Fat,4000,6000,3500,1000:Skinny,600,2402,1181,600
+</pre>
+
+<p>
+ Be sure, to remove any route-style line in ~/.pcb/preferences . Else, the line in settings will be ignored.
+</p>
+
+<p>
+The line tool knows about different modes to deal with transversal connections. The status line on the bottom of the page tells, which mode is in effect:
+</p>
+<ol>
+<li class="level1"><div class="li"> 45° plus vertical/horizontal (status line: â??\_â??)</div>
+</li>
+<li class="level1"><div class="li"> vertical plus 45° (status line: â??_/â??)</div>
+</li>
+<li class="level1"><div class="li"> either vertical or 45° (status line: â??45â??)</div>
+</li>
+<li class="level1"><div class="li"> arbitrary angle (status line: â??allâ??)</div>
+</li>
+</ol>
+
+<p>
+The way to access these modes differs among the <acronym title="Graphical User Interface">GUI</acronym> versions. The current GTK snapshot (v20060288) defaults to â??_/â?? but can be temporarily turned to â??\_â?? with the shift key. You can switch to 45° mode with the slash key â??/â??. For arbitrary angles, press the period key â??.â??, or choose â??enable all line directionsâ?? in the setting menu.
+</p>
+
+</div>
+<!-- SECTION "I cant't move the components on the other side of the board!" [21857-27529] -->
+<h2><a name="i_got_stuck_how_do_i_go_back" id="i_got_stuck_how_do_i_go_back">I got stuck! How do I go back?</a></h2>
+<div class="level2">
+
+<p>
+The universal undo key [<strong><code>U</code></strong>] works even while in the middle of track layout actions. It will remove the last segment but keep the line tool attached to the mouse. So you can immediately go on routing and find a better way.
+</p>
+
+</div>
+<!-- SECTION "I got stuck! How do I go back?" [27530-27802] -->
+<h2><a name="how_do_i_move_one_set_of_layer_tracks_to_a_different_layer" id="how_do_i_move_one_set_of_layer_tracks_to_a_different_layer">How do I move one set of layer tracks to a different layer?</a></h2>
+<div class="level2">
+<ol>
+<li class="level1"><div class="li"> Select the tracks. Itâ??s easiest to do this if you shut off everything but that layer first (i.e. silk, pins, other layers, etc).</div>
+</li>
+<li class="level1"><div class="li"> Now set the current layer to be the new layer. Yes, the layer might get displayed; not a problem as youâ??ve already selected the tracks you want.</div>
+</li>
+<li class="level1"><div class="li"> Press [<strong><code>shift-M</code></strong>] to move all the selected tracks to the current layer.</div>
+</li>
+</ol>
+
+</div>
+<!-- SECTION "How do I move one set of layer tracks to a different layer?" [27803-28243] -->
+<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>
+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" [28244-30019] -->
+<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/pad?" [30020-30546] -->
+<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">
+
+<p>
+There are a number of ways to change the size of already laid down tracks:
+</p>
+<ol>
+<li class="level1"><div class="li"> Use [<strong><code>s</code></strong>] and [<strong><code>shift-s</code></strong>] to increase and decrease the size of the track currenty under the mouse cursor.</div>
+</li>
+<li class="level1"><div class="li"> choose <strong><code>Select/Change_size_of_selected_objects/Decrement_lines_by_4mil</code></strong> from the <strong><code>Select</code></strong> menu. The actual amount of change can be set in <strong><code>File/Preferences/Sizes</code></strong>. This only acts on the tracks. So the selection may contain components, text, vias and the like.</div>
+</li>
+<li class="level1"><div class="li"> Select the tracks to be changed and type <strong><code>:ChangeSize(SelectedLines,+4,mils)</code></strong>. The colon gets you to the command line and <strong><code>ChangeSize()</code></strong> is the command version of the previously described action. Replace â??<strong><code>+4</code></strong>â?? by the amount you want to increase the track size. Use the minus sign to decrease the tracksize. If you omit the sign the command sets the track size to the value given.</div>
+</li>
+</ol>
+
+</div>
+<!-- SECTION "How do I change the size of my tracks?" [30547-31484] -->
+<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>
+<li class="level1"><div class="li"> Set the GND plane layer as the active layer.</div>
+</li>
+<li class="level1"><div class="li"> Select the â??viaâ?? tool.</div>
+</li>
+<li class="level1"><div class="li"> Place the via where you want it to live (left click to place).</div>
+</li>
+<li class="level1"><div class="li"> Now select the â??thermalâ?? tool.</div>
+</li>
+<li class="level1"><div class="li"> Left click on the via you just placed.</div>
+</li>
+<li class="level1"><div class="li"> Now change the active layer to your desired routing layer.</div>
+</li>
+<li class="level1"><div class="li"> Select the â??lineâ?? tool.</div>
+</li>
+<li class="level1"><div class="li"> Route the track on the active layer to or from the via as usual.</div>
+</li>
+</ol>
+
+</div>
+<!-- SECTION "How do I drive a via to connect a track to a ground plane on a different layer?" [31485-31970] -->
+<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">
+
+<p>
+A â??thermal viaâ?? is not a via with a thermal relief. Rather, itâ??s a via with no thermal relief punched into polygons on both sides of the board. These vias get filled with solder to help create a large thermal mass to be used as a heat sink. For more info, see Freescale App-Note AN4005.
+</p>
+
+<p>
+Here are some suggestions:
+</p>
+<ul>
+<li class="level1"><div class="li"> Draw a rectangle to comfortably surround the vias. Then, mouse over the rectangle and hit â??sâ??. This will flood the thermal reliefs on the vias. If you want to ever de-solder the part from the back, make sure the pad on the opposite side has the solder resist cleared.</div>
+</li>
+<li class="level1"><div class="li"> Just put a normal thermal relief on the via and then shift click on it to cycle through to the one with no relief. </div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "What is the easiest way to create a thermal via?" [31971-32748] -->
+<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">
+
+<p>
+You are likely drawing tracks with auto-DRC on. To connect the two segments, here are some suggestions:
+</p>
+<ul>
+<li class="level1"><div class="li"> DRC enforcement uses the ratsnest to determine where a track is allowed to go. Thus, you must have the ratsnest drawn in order to make connections in auto-DRC mode. Otherwise you will not be allowed to connect (or approach) any copper that is not already connected to your net. (If the rat visibility bothers you, you can hide the rats layer â?? but the rats must exist).</div>
+</li>
+<li class="level1"><div class="li"> You should also refresh the rats regularly when drawing. Hit [<strong><code>o</code></strong>] to redraw/re-optimize the rats. Make sure a rat is visibly connecting the two pieces of metal you want to connect.</div>
+</li>
+<li class="level1"><div class="li"> It is also possible that you will experience this situation when drawing tracks between pins in a connector. In this case, it is possible that your track width violates the clearance requirements of the pin field. Try decreasing the pin-to-metal clearance, or use a narrower track width.</div>
+</li>
+<li class="level1"><div class="li"> Sometimes this route-blocking behaviour can come about from an error in your netlist. Donâ??t end refdesâ??s with lower case letters - theyâ??re reserved for gates within devices. End with upper case or a digit; the lowercase letters are simply ignored.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "I want to draw a track between two segments on the same net, but PCB won't let me! Why?" [32749-34067] -->
+<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">
+
+<p>
+Most likely you named them such that pcb believes they are one part. Lower case letters at the end of a refdes are ignored. Thus, the components U2foo and U2bar both look like U2 to pcb. When building the rat nests pcb is will look for nets to U2 that, of course donâ??t exist. Lower case letters are meant to differentiate slots of a multi-component. E.g. the four opamp symbols of a quad operational amplifier.<br/>
+ Bottom line: Donâ??t use lower case letters at the end of a refdes, unless you know what you are doing.
+</p>
+
+</div>
+<!-- SECTION "PCB seems to munge my components names and complains that it can't find proper nets for the pins! How come?" [34068-34706] -->
+<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">
+
+<p>
+You can set the color of the rats in <code>File - Preference - Colors - Main colors</code>
+</p>
+
+<p>
+There is currently no <acronym title="Graphical User Interface">GUI</acronym> way to set the rat width, but you can edit your <code>$HOME/.pcb/preference</code> file manually. Close all instances of pcb and look for the line that starts with <code>rat-thickness</code>.
+</p>
+
+<p>
+Values 0..19 are fixed width in screen pixels. Anything larger means PCB units (i.e. 100 means â??1 milâ??). On zoom, PCB unit rats will scale accordingly.
+</p>
+
+</div>
+<!-- SECTION "How can I set color and thickness of the rats nests?" [34707-35211] -->
+<h2><a name="where_is_that_last_remaining_rat" id="where_is_that_last_remaining_rat">Where is that last remaining rat?</a></h2>
+<div class="level2">
+
+<p>
+Sometimes remaining rats are hard to see, because they have zero length. This will be the case if a via is missing for some reason. You can make them pop into your eye by setting the rat thickness to some big value e.g. 3000 mil. Rat thickness is set in <code>$HOME/.pcb/preference</code>.
+</p>
+
+</div>
+<!-- SECTION "Where is that last remaining rat?" [35212-35539] -->
+<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" [35540-35582] -->
+<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">
+
+<p>
+See the page <a href="http://www.delorie.com/pcb/bg-image.html"; class="urlextern" title="http://www.delorie.com/pcb/bg-image.html"; rel="nofollow">http://www.delorie.com/pcb/bg-image.html</a> at DJ Delorieâ??s PCB HID website.
+</p>
+
+<p>
+This is a great way to trace hand-drawn artwork or another PCB, say one you made in software with a proprietary format, which youâ??d now like to â??unlockâ??. Furthermore, you can use the background image as tool for making board revisions or redesigns.
+</p>
+
+<p>
+If you donâ??t like to use PCB confined to the area of the board, i.e. if you want margins around your board, then add them in the GIMP. I like to make a 1.00000 inch margin around the board. When you set your PCB size in PCB, youâ??ll want to add the margin area. CTRL-M will help you verify the scaling. Also, the time to correct distortions from your scanner, or from your drawing is before you load it, in the GIMP or the like.
+</p>
+
+</div>
+<!-- SECTION "How do I trace a drawing, a print, or another PCB?" [35583-36423] -->
+<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">
+
+<p>
+<strong>Question:</strong> I want to copy a section of my existing layout to another spot.
+</p>
+
+<p>
+I can select the existing area. Everything turns pretty blue.
+</p>
+
+<p>
+â??Bufferâ??–>â??Copy Selection To Bufferâ?? seems to succeed (no complaints).
+</p>
+
+<p>
+Then I go to paste the copied area… and all that moves are a couple of traces and some vias. The pads Iâ??ve painstakingly created arenâ??t copied. What gives!?!?!?
+</p>
+
+<p>
+<strong>Answer:</strong> If the silk layer is off, you canâ??t copy elements through the paste buffer. Weird, but thatâ??s how it works. Therefore, turn on the silk layer before trying to copy a section of a layout.
+</p>
+
+</div>
+<!-- SECTION "I can't copy component pads in a layout. What gives?" [36424-37078] -->
+<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">
+
+<p>
+Use rectangles and polygon planes. These items will always avoid vias, pads and pins. Tracks are also avoided, if they have the clear polygons flag set. (menu: Settings/Enable_new_lines_clear_polygons). Since version 20070208 of pcb the resulting polygon will be one contiguous piece. Isolated snippets are removed.
+</p>
+
+</div>
+<!-- SECTION "How do I fill areas with copper?" [37079-37442] -->
+<h2><a name="how_can_i_assign_my_polygon_to_a_net" id="how_can_i_assign_my_polygon_to_a_net">How can I assign my polygon to a net?</a></h2>
+<div class="level2">
+
+<p>
+Polygons are not â??assignedâ?? to nets, theyâ??re connected to them. Pads are the only carriers of netnames in pcb. This means, you need to design some copper to connect the polygon with a pad. The net of the pad automatically transfers to the polygon.
+</p>
+
+</div>
+<!-- SECTION "How can I assign my polygon to a net?" [37443-37745] -->
+<h2><a name="how_can_i_connect_tracks_pads_or_vias_to_my_polygon" id="how_can_i_connect_tracks_pads_or_vias_to_my_polygon">How can I connect tracks, pads, or vias to my polygon?</a></h2>
+<div class="level2">
+
+<p>
+There are different ways to adequately connect different types of objects to a polygon:
+</p>
+<ul>
+<li class="level1"><div class="li"> tracks: Set the join flag of the track. You can do this with the [<strong><code>j</code></strong>] key, while the mouse hovers above the track. Alternatively you can select the lines and apply the command â??SetFlag(selected,join)". For new lines, you can uncheck the new-lines-clear-polygons in the settings menu. The polygon will immediately flow into the track.</div>
+</li>
+<li class="level1"><div class="li"> pads: Currently, there is no way to directly connect a polygon to a pad. Draw a track without the join flag from the pad to the polygon. (see above) </div>
+</li>
+<li class="level1"><div class="li"> pins and vias: Choose the thermal tool (â??THRMâ??). Select the layer the polygon sits on. Shift-Click on the via to circle through the available styles of the connection. </div>
+</li>
+<li class="level1"><div class="li"> polygons: Just define them geometrically overlapping.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "How can I connect tracks, pads, or vias to my polygon?" [37746-38632] -->
+<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">
+
+<p>
+You didnâ??t have â??Enable_new_lines_clear_polygonsâ?? checked in the settings menu when you layed down the tracks. Enter â??changejoin(selected)â?? in the command window to toggle this flag for all tracks that are currently selected. The keyboard shortcut to this action is [<strong><code>shift-j</code></strong>]. If you want to set or clear the join flag rather than toggle it, you can use the commands â??SetFlag(selected, join)â?? and â??ClrFlag(selected, join)". See the SetFlag description in the <a href="http://pcb.sourceforge.net/manual.html"; class="urlextern" title="http://pcb.sourceforge.net/manual.html"; rel="nofollow">pcb manual</a> for more details on these commands.
+</p>
+
+</div>
+<!-- SECTION "The polygons are shorting my tracks! What can I do about it?" [38633-39282] -->
+<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">
+
+<p>
+Press [<strong><code>k</code></strong>] to increase the clearence of the object under the cursor. Use [<strong><code>ctrl-k</code></strong>] to increase the clearence of selected objects. Add the [<strong><code>shift</code></strong>] modifier to decrease the clearence. To change a whole track press [<strong><code>f</code></strong>] to find all segments that are connected to the object under the cursor and apply the action â??select(connection)â??.
+</p>
+
+<p>
+The amount of the increment can be configured in the dialog File/Preference/Increments.
+</p>
+
+</div>
+<!-- SECTION "How do I change polygon clearance?" [39283-39783] -->
+<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">
+
+<p>
+Put the polygons (and rectangles) on a separate layer. Use the preference to make sure, this layer is not in the same group as the tracks. Disable the layer by a click on the corresponding layer button in the main window. After you are finished with the changes, use the preference dialog to let the polygon layer join the layer of the tracks. You will have to save and reload the layout to trigger recalculation of polygons so they are adapted to your edits. Alternatively a restart will recaalculate the polygons too.
+</p>
+
+</div>
+<!-- SECTION "How do I hide the polygons while I edit the layout?" [39784-40369] -->
+<h2><a name="polygons_are_making_the_gui_sluggish._what_i_can_do_about_it" id="polygons_are_making_the_gui_sluggish._what_i_can_do_about_it">Polygons are making the GUI sluggish. What I can do about it?</a></h2>
+<div class="level2">
+
+<p>
+Parts of the polygon that are not connected to some net are automatically eliminated. This effectively removes <a href="geda-glossary.html" class="wikilink1" title="geda-glossary.html">dead copper</a>. While this is desirable for the actual board, it requires calculation of quite extensive algorithms. So it is not necessarily a bug, but a price to be paid for a powerful feature. Still, there is a couple of things you can do to improve the situation:
+</p>
+<ul>
+<li class="level1"><div class="li"> Temporarily hide the polygons. (see above)</div>
+</li>
+<li class="level1"><div class="li"> Choose â??thin draw polyâ?? from the settings menu to display only the outlines of the polygons and disable dead copper removal. In recent versions of gschem, i.e. later than september 2007, you can select through the polygons. </div>
+</li>
+<li class="level1"><div class="li"> Make sure, you donâ??t have redundant polygons defined, which multiply overlay the same area. These polygons wonâ??t display becaus they shade each other. But they demand calculation resources. The best way to check for redundant polygons is to edit the source of your layout with an ascii editor. </div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Polygons are making the GUI sluggish. What I can do about it?" [40370-41413] -->
+<h2><a name="after_i_defined_those_ground_planes_pcb_takes_ages_to_load._how_come" id="after_i_defined_those_ground_planes_pcb_takes_ages_to_load._how_come">After I defined those ground planes, pcb takes ages to load. How come?</a></h2>
+<div class="level2">
+
+<p>
+Polygon calculation is potentially an expensive operation in terms of processor cyles. Unless your layout is pretty complex, you most likely have redundant polygons defined. Look into the source of your layout to find and delete unnecessary polygons. If this does not apply, see above for possible measures to ameliorate the situation.
+</p>
+
+</div>
+<!-- SECTION "After I defined those ground planes, pcb takes ages to load. How come?" [41414-41834] -->
+<h2><a name="how_do_i_edit_polygons" id="how_do_i_edit_polygons">How do I edit polygons?</a></h2>
+<div class="level2">
+
+<p>
+There are four basic ways to edit polygon outlines. You can move and delete vertices and you can insert vertices using two techniques. Polygons can be edited equally well in â??thin line drawâ?? mode (settings â??> enable thin line draw) or in normal mode. Moving a vertex is easily accomplished by un-selecting your polygon and then clicking and dragging that vertex to a new location. To delete a vertex, a corner in your polygon, put your crosshairs over the point and hit â??deleteâ?? on the keyboard. To insert a vertex, youâ??ll use the insert tool (â??insertâ?? keystroke). Start by clicking the edge you want to split with a new point. Click and drag a new point into the polygon. A variation on this technique is 1) click to select, followed by 2) click to place new vertex.
+</p>
+
+<p>
+(NOTE: Inserting points into polygon will generally work ONLY with â??all direction linesâ?? enabled (â??settings â??> enable all direction linesâ??). This is because PCB has a powerful 45/90 degree constraints system. If you try to insert new vertices into a polygon that donâ??t fall onto lines of proper 45 and 90 degree constraints, PCB disallows the action!)
+</p>
+
+</div>
+<!-- SECTION "How do I edit polygons?" [41835-43020] -->
+<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">
+
+<p>
+Often itâ??s useful to have vias connect completely to a polygon (a field of copper) for heat transferâ?? the apparent problem is that PCB polygons have only a single â??clear pins/viasâ?? flag for the entire polygon (toggled by the [<strong><code>s</code></strong>] key). Our goal is to only connect some of the pins/vias to the polygon, but to connect them better than a thermal does. Here are a few ways to do this:
+</p>
+
+<p>
+One way, youâ??ll make an object thatâ??s almost just like a thermal in that it goes between your via and the polygonâ??the difference is that youâ??ll actually create an annulus to completely fill the space between the hole and polygon (which because itâ??s clearance is turned on, is not connected to the pin). This annulus is four arc segments. You can copy these four items to the buffer to create a â??zero-clearance thermal toolâ??. The drawback of this trick is that when you change via size, youâ??ll also have to modify the size of these filler parts.
+</p>
+
+<p>
+The arcs allow you to use this fill trick in tight places by only placing, say two of the four arcs.
+</p>
+
+<p>
+Another trick is to make a zero-length line. Take a single line segment and move the end-point on top of the start-point. Now you have a â??single point lineâ?? (a circle) with the diameter equal to the line thickness. Move to different layers ([<strong><code>m</code></strong>] key) as you see fit. Place this object centered on your via to connect it to a polygon.
+</p>
+
+<p>
+Power-users may want to keep a small custom library of these parts by saving them as elements. Itâ??s also handy to put these â??partsâ?? in one of your PCB buffers so theyâ??re at your fingertips.
+</p>
+
+<p>
+You can also add another polygon on-top of the polygon to which you want to connect you vias. Youâ??ll un-set the â??clear pins/viasâ?? flag and the vias will be connected to the larger polygon underneath.
+</p>
+
+</div>
+<!-- SECTION "How do I place vias that connect to a polygon for full thermal dissipation or full shielding integrity?" [43021-44942] -->
+<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">
+
+<p>
+Currently, there is no way to directly make polgons clear solder mask. The usual workaround is to work with pads.
+</p>
+<ol>
+<li class="level1"><div class="li"> Draw a track in the middle of the desired no solder mask area. Every track will become a pad.</div>
+</li>
+<li class="level1"><div class="li"> Select the tracks</div>
+</li>
+<li class="level1"><div class="li"> Do convert-selection-to-element from the select menu</div>
+</li>
+<li class="level1"><div class="li"> Activate the solder mask layer. The solder mask should keep clear of the tracks</div>
+</li>
+<li class="level1"><div class="li"> Increase the clearance of the pads to match the desired bare copper area. To do this, press [k] while the mouse cursor hovers above the pads.</div>
+</li>
+<li class="level1"><div class="li"> Optionally press q to set the square flag of the pads.</div>
+</li>
+</ol>
+
+<p>
+While the pad witdth is limited to 250 mil, clearance can be arbitrary.
+</p>
+
+</div>
+<!-- SECTION "Can polygons be un-masked? (Can a polygon be made bare-copper with no solder mask?)" [44943-45692] -->
+<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">
+
+<p>
+Use a footprint for the mounting hole or place a via.
+</p>
+
+<p>
+If the pads surrounding the mounting hole need to be electrically connected then you should show the connection in your schematic. Add a symbol for the mounting hole and change its footprint attribute.
+</p>
+
+<p>
+My preference is to create PCB footprints for the various types of mounting hardware. I have a variety of silkscreens for various hardware combinations (hex nut, hex nut with washer, etc.) The silkscreen provides a convenient placement reference during PCB layout.
+</p>
+
+<p>
+For footprint examples see <a href="http://www.luciani.org/geda/pcb/pcb-footprint-list.html#Hardware"; class="urlextern" title="http://www.luciani.org/geda/pcb/pcb-footprint-list.html#Hardware"; rel="nofollow">http://www.luciani.org/geda/pcb/pcb-footprint-list.html#Hardware</a>.
+</p>
+
+</div>
+<!-- SECTION "How do I place mounting holes?" [45693-46357] -->
+<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">
+
+<p>
+The reason is that pins usually have sufficient spacing that the plane surrounding them remains intact on all sides and pads usually are so tightly spaced that they do not. Because of this you must manually draw the thermal â??fingersâ?? to connect the pad to the ground plane. Be sure that you have the settings such that new lines connect to planes when you draw them. If you need to make several such thermals, spend a little time making the first one just the way you want then copy the fingers to the buffer and paste it where you want the others.
+</p>
+
+</div>
+<!-- SECTION "Why is it possible to make a thermal for pin, but not for a pad?" [46358-46989] -->
+<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">
+
+<p>
+Itâ??s all just names when youâ??re doing single sided. Thereâ??s no such thing as a single sided board in pcb - just a double sided board with nothing on one side.
+</p>
+
+<p>
+Design for two-sided, but with all the traces on the solder side. If you use the autorouter, turn off all but the bottom layer. This will make the autorouter stick to that layer. If you need wire jumpers, you have two options to let pcb know there is a valid connection: You can draw tracks on top layer similar to a two layer layout. Alternatively you can Create a â??jumperâ?? symbol in the schematic and put that in places where you need a jumper. This is likely to be a major pain, but you can enforce dimensions of the jumpers this way if you care.
+</p>
+
+<p>
+Single sided boards do not have plated holes, so pad diameter for pins must be greater, usually two to three times the drill size. Some footprints in the default library have very small pads which will be too weak if used for single sided board. Tweak them to your needs and place them in a local library.
+</p>
+
+<p>
+When you dump your gerbers, delete the component side one and rename the plated-holes one to unplated-holes. Voila! A single sided board.
+</p>
+
+</div>
+<!-- SECTION "Can PCB be used to make single layer boards?" [46990-48215] -->
+<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">
+
+<p>
+One of PCBâ??s great features is that it uses an easily understood <acronym title="American Standard Code for Information Interchange">ASCII</acronym> file format. Therefore, many people use scripts (commonly <acronym title="Practical Extraction and Report Language">Perl</acronym>) to process their boards in various ways. You can use these scripts either as they are, or modify them to suit your own goals. Here are some links to available scripts:
+</p>
+<ol>
+<li class="level1"><div class="li"> John Luciani has a large number of <a href="http://www.luciani.org/geda/pcb/pcb-perl-library.html"; class="urlextern" title="http://www.luciani.org/geda/pcb/pcb-perl-library.html"; rel="nofollow">scripts</a> available on <a href="http://www.luciani.org"; class="urlextern" title="http://www.luciani.org"; rel="nofollow"> his website</a>. Included in his collection are scripts for generating footprints, as well as </div>
+</li>
+<li class="level1"><div class="li"> David Rowe has scripts for updating elements as well as adding/subtracting PCB files from each other on <a href="http://www.rowetel.com/perl4pcb.html"; class="urlextern" title="http://www.rowetel.com/perl4pcb.html"; rel="nofollow">his website.</a></div>
+</li>
+<li class="level1"><div class="li"> Stuart Brorson wrote a simple script which generates footprints for two terminal SMT passives. A gzipped tarball is available <a href="http://www.brorson.com/gEDA/Smtgen.pl.gz"; class="urlextern" title="http://www.brorson.com/gEDA/Smtgen.pl.gz"; rel="nofollow"> here </a>.</div>
+</li>
+<li class="level1"><div class="li"> The website <a href="http://www.gedasymbols.org/"; class="urlextern" title="http://www.gedasymbols.org/"; rel="nofollow"> gedasymbols.org</a> has gathered a collection of footprints, symbols, scripts, and other materials from many different gEDA contributors. The website is organized by contributor, so if you take the time to browse around there, you may find exactly what you are looking for!</div>
+</li>
+</ol>
+
+</div>
+<!-- SECTION "What resources exist to process PCB files using scripts?" [48216-49501] -->
+<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">
+
+<p>
+There is a third party open source utility called <a href="http://www.pstoedit.net/"; class="urlextern" title="http://www.pstoedit.net/"; rel="nofollow">pstoedit</a> that converts postscript data to pcb format. It is included in most major linux distributions. You can use your favorite vector graphics utility to produce a logo or any kind of fancy layout. Export as eps if you can and make sure that your logo fits into the bounding box (check with a postscript viewer such as ggv). If there is no eps export available, you can produce postscript by printing to a file. In this case you may add a bounding box with <a href="http://www.cs.wisc.edu/~ghost/doc/gnu/6.53/Ps2epsi.htm"; class="urlextern" title="http://www.cs.wisc.edu/~ghost/doc/gnu/6.53/Ps2epsi.htm"; rel="nofollow">ps2epsi</a>. Call pstoedit with the option "<code>-f pcb</code>â?? to produce a valid pcb file that contains the graphics as tracks on layer 1. Load this file to pcb. The graphics will sit somewhere on the lower left of the view port. You may have to zoom out to get it on the screen.
+</p>
+
+<p>
+Import of external vector graphics is usefull if an irregular shape of the pcb is required. Use the cut buffer to copy the shape to your actual design.
+</p>
+
+</div>
+<!-- SECTION "How do I import external vector graphics?" [49502-50581] -->
+<h2><a name="is_there_a_way_to_import_a_dxf_drawing_from_mechanical_cad_applications" id="is_there_a_way_to_import_a_dxf_drawing_from_mechanical_cad_applications">Is there a way to import a DXF drawing from mechanical CAD applications?</a></h2>
+<div class="level2">
+
+<p>
+There is no import filter to directly load a DXF file to pcb. However, the open source application <a href="http://www.qcad.org"; class="urlextern" title="http://www.qcad.org"; rel="nofollow">qcad</a> can open DXF files and export them as postscript. The tool pstoedit can turn this postscript file into a format readable by pcb (see above).
+</p>
+
+</div>
+<!-- SECTION "Is there a way to import a DXF drawing from mechanical CAD applications?" [50582-50936] -->
+<h2><a name="what_is_the_best_way_to_do_weird_footprints" id="what_is_the_best_way_to_do_weird_footprints">What is the best way to do weird footprints?</a></h2>
+<div class="level2">
+
+<p>
+Sometimes footprints call for shapes that are difficult to achieve with the restricted graphics <acronym title="Graphical User Interface">GUI</acronym> of pcb. It may be easier to start with a the vector drawing application inkscape and convert to pcb. In inkscape:
+</p>
+<ul>
+<li class="level1"><div class="li"> draw the weird shape with lines. Lines donâ??t have to be straight.</div>
+</li>
+<li class="level1"><div class="li"> save as eps (uncheck â??make bounding box around pageâ??)</div>
+</li>
+</ul>
+
+<p>
+ Convert to pcb format:
+</p>
+<ul>
+<li class="level1"><div class="li"> pstoedit -f pcb > footprint.pcb</div>
+</li>
+</ul>
+
+<p>
+ In pcb do:
+</p>
+<ul>
+<li class="level1"><div class="li"> File - load-layout-data-to-buffer</div>
+</li>
+<li class="level1"><div class="li"> edit to your needs (lines only, no polygons)</div>
+</li>
+<li class="level1"><div class="li"> select the bunch of lines</div>
+</li>
+<li class="level1"><div class="li"> copy to buffer ( ctrl-c )</div>
+</li>
+<li class="level1"><div class="li"> Buffer - convert-buffer-to-element</div>
+</li>
+<li class="level1"><div class="li"> Buffer - save-buffer-elements-to-file</div>
+</li>
+</ul>
+
+<p>
+ In a text editor:
+</p>
+<ul>
+<li class="level1"><div class="li"> add the same pin number to all the lines with search and replace</div>
+</li>
+<li class="level1"><div class="li"> save as *.fp at a place where pcb is looking for footprint libraries</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "What is the best way to do weird footprints?" [50937-51798] -->
+<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">
+
+<p>
+You can set the name of the current pcb with <code>Menu Edit - Edit name of - layout</code>. This sets the title attribute of the layout. This attribute is used for the export actions. It does not interfere with the file name.
+</p>
+
+</div>
+<!-- SECTION "How Do I attach a name to my layout?" [51799-52071] -->
+<h2><a name="is_there_a_way_to_do_multiple_instances_of_a_subcircuits" id="is_there_a_way_to_do_multiple_instances_of_a_subcircuits">Is there a way to do multiple instances of a subcircuits?</a></h2>
+<div class="level2">
+
+<p>
+The <acronym title="Graphical User Interface">GUI</acronym> provides no way to do similar subcircuits automatically. You can copy groups of tracks and vias. However, you have to place the footprints manually. Deactivate â??Auto-enforce-DRC-Clearranceâ?? in the edit menu during placement. Else pcb wonâ??t let you connect the footprints with the copied tracks and vias.
+</p>
+
+<p>
+John Luciani wrote a pair of perl scripts that can do better than that. The script sch-matrix places multiple copies of a basic block on the sheet. It increments the numbers and positions of the symbols as needed. The layout script pcb-matrix arranges multiple copies of a sample layout in a matrix way. The result is a matching pair of schematic and layout with a subcircuit repeated multiple times. See <a href="http://www.luciani.org/geda/util/matrix/index.html"; class="urlextern" title="http://www.luciani.org/geda/util/matrix/index.html"; rel="nofollow">Johns website</a> for the details and a download of the scripts.
+</p>
+
+<p>
+The pair of scripts was written a few years ago and is not used regularily. They may need to be updated when used with recent versions of pcb. Contribution of bug reports and/or patches are welcome.
+</p>
+
+</div>
+<!-- SECTION "Is there a way to do multiple instances of a subcircuits?" [52072-53179] -->
+<h1><a name="auto_router" id="auto_router">Auto Router</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "Auto Router" [53180-53209] -->
+<h2><a name="how_do_i_make_the_most_of_the_auto_router" id="how_do_i_make_the_most_of_the_auto_router">How do I make the most of the auto router?</a></h2>
+<div class="level2">
+<ol>
+<li class="level1"><div class="li"> Turn off visibility of any layers you donâ??t want the router using.</div>
+</li>
+<li class="level1"><div class="li"> Turn of via visibility if you donâ??t want it to introduce any new vias.</div>
+</li>
+<li class="level1"><div class="li"> Use only plain rectangles for power/ground planes that you want the router to use. (Use the rectangle tool rather than the polygon tool!)</div>
+</li>
+<li class="level1"><div class="li"> Make at least one connection from any plane you want the router to use to the net you want it to connect to.</div>
+</li>
+<li class="level1"><div class="li"> Draw continuous lines on all routing layers to outline keep-out zones.</div>
+</li>
+<li class="level1"><div class="li"> Use routing styles in the netlist to have per-net routing styles.</div>
+</li>
+<li class="level1"><div class="li"> Set the current routing style for any nets not having a defined route style in the netlist.</div>
+</li>
+<li class="level1"><div class="li"> Disable any nets that you donâ??t want the autorouter to route – double-click them in the netlist window to add/remove the â??*â??.</div>
+</li>
+<li class="level1"><div class="li"> Create a fresh ratâ??s nest. (press the [o]-key)</div>
+</li>
+<li class="level1"><div class="li"> Select â??show autorouter trialsâ?? in the settings menu if you want to watch whatâ??s happening.</div>
+</li>
+<li class="level1"><div class="li"> Choose â??autoroute all ratsâ?? in the connection menu.</div>
+</li>
+</ol>
+
+<p>
+ Note on disabled nets: If you will be manually routing these later not using planes, it is usually better to let the autorouter route them then rip them up yourself afterwards. If you plan to use a ground/power plane manually, consider making it from one or more pure rectangles and letting the autorouter have a go at it.
+</p>
+
+<p>
+If you really want to muck with the router because you have a special design, e.g. all through-hole components you can mess with layer directional costs by editing the autoroute.c source file and changing the directional costs in lines 929-940. and try again. Even more mucking about with costs is possible in lines 4540-4569, but itâ??s probably not such a good idea unless you really just want to experiment.
+</p>
+
+</div>
+<!-- SECTION "How do I make the most of the auto router?" [53210-54977] -->
+<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">
+
+<p>
+Just unselect the layers you donâ??t want (usually green and blue) by clicking on the name of the layer. then press autoroute.
+</p>
+
+</div>
+<!-- SECTION "How do I force the autorouter to only put traces on a particular layer?" [54978-55189] -->
+<h2><a name="how_do_i_make_autorouter_leave_particular_nets_alone" id="how_do_i_make_autorouter_leave_particular_nets_alone">How do I make autorouter leave particular nets alone?</a></h2>
+<div class="level2">
+
+<p>
+Open up the netlist window. It has options for including or excluding nets from the ratlist. If you use the GTK-HID double-click a route to disable it. Make sure, only the nets you want are enabled. Optimize the rats with key [o]. Do â??autoroute all ratsâ??.
+</p>
+
+</div>
+<!-- SECTION "How do I make autorouter leave particular nets alone?" [55190-55514] -->
+<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">
+
+<p>
+You can have the autorouter work only within a given area by drawing a copper polygon conforming to your boardâ??s boundary and placing it in each layer youâ??re trying to autoroute. You can also use this trick to autoroute only with small areas. Of course, if you accidentally have a net touching the polygon, all routes will get shorted to that net.
+</p>
+
+</div>
+<!-- SECTION "How do I force the autorouter to route only within my pcb outline?" [55515-55946] -->
+<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">
+
+<p>
+Connect the polygon that will become your power planes to a net and the autorouter will figure it all out. You may need some trick polygon clearances to get power routing _and_ routing within a board outline.
+</p>
+
+</div>
+<!-- SECTION "How do I route power and ground planes with the autorouter?" [55947-56228] -->
+<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">
+
+<p>
+This is a technological limitation of the current auto router. It is gridless and uses geometric rectangles only.
+</p>
+
+</div>
+<!-- SECTION "The layout produced by the autorouter is inefficient!" [56229-56409] -->
+<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">
+
+<p>
+Have you tried the various clean-up tools under connects–>optimize routed tracks?
+</p>
+
+</div>
+<!-- SECTION "The layout produced by the autorouter is ugly!" [56410-56553] -->
+<h1><a name="gerber_files_prints_and_other_i_o_issues" id="gerber_files_prints_and_other_i_o_issues">Gerber files, prints and other I/O issues</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "Gerber files, prints and other I/O issues" [56554-56610] -->
+<h2><a name="is_is_possible_to_produce_output_without_gui_intervention" id="is_is_possible_to_produce_output_without_gui_intervention">Is is possible to produce output without GUI intervention?</a></h2>
+<div class="level2">
+
+<p>
+Yes, you can tell pcb on the command line to do an export. All the parameters set in the print dialog can be used in the command line too. Some simple examples:
+</p>
+
+<p>
+Gerber files:
+</p>
+<pre class="code">
+pcb -x gerber --gerberfile BOARD BOARD.pcb
+</pre>
+
+<p>
+Postscript formated print:
+</p>
+<pre class="code">
+pcb -x ps --psfile BOARD.ps BOARD.pcb
+</pre>
+
+<p>
+<acronym title="Portable Network Graphics">PNG</acronym> format:
+</p>
+<pre class="code">
+pcb -x png --dpi 300 --only-visible --outfile BOARD.png BOARD.pcb
+</pre>
+
+<p>
+Different output procedures allow for different options. See the output of <code>pcb --help</code> for details.
+</p>
+
+</div>
+<!-- SECTION "Is is possible to produce output without GUI intervention?" [56611-57212] -->
+<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">
+
+<p>
+You can add an outline layer to your pcb projects. PCB interprets any layer called â??outlineâ?? (edit â??> edit name of â??> active layer) as though it is the absolute edge of the pcb. PCB prints gerber files that rigidly represent this.
+</p>
+
+<p>
+You can enter your outline layer thru PCBâ??s <acronym title="Graphical User Interface">GUI</acronym>. You just draw the lines of the board outline. You can generate boards of any shape this way.
+</p>
+
+<p>
+Itâ??s also possible to edit the native .pcb file format of your layout. I usually use Layer 8 for outlines:
+</p>
+<pre class="code">Layer(8 "outline")
+(
+ Line[x1 y1 x2 y2 1000 2000 0x00000000]
+ Line[x2 y2 x3 y3 1000 2000 0x00000000]
+ Line[x3 y3 x4 y4 1000 2000 0x00000000]
+ Line[x4 y4 x1 y1 1000 2000 0x00000000]
+ Line[<more points go here for non-square boards> 1000 2000 0x00000000]
+)</pre>
+
+</div>
+<!-- SECTION "How do I make a board outline to go with my gerbers to the board maker?" [57213-58061] -->
+<h2><a name="yes_i_tried_that_but_the_gerber_exporter_didn_t_give_me_an_outline_file._why" id="yes_i_tried_that_but_the_gerber_exporter_didn_t_give_me_an_outline_file._why">Yes, I tried that, but the gerber exporter didn't give me an outline file. Why?</a></h2>
+<div class="level2">
+
+<p>
+By default, gsch2pcb creates layer groups in a way which prevents your outline layer from being treated properly. So you should remove all the unnecessary layers (i.e, all but your copper layers and silkscreen), then add an outline layer (named <code>outline</code>), on which you define your outline. The gerber exporter should then give you the outline gerber file.
+</p>
+
+</div>
+<!-- SECTION "Yes, I tried that, but the gerber exporter didn't give me an outline file. Why?" [58062-58514] -->
+<h2><a name="how_do_i_make_sure_that_the_design_contains_only_certain_hole_sizes" id="how_do_i_make_sure_that_the_design_contains_only_certain_hole_sizes">How do I make sure, that the design contains only certain hole sizes?</a></h2>
+<div class="level2">
+
+<p>
+Some fabs provide lists of standard drill sizes and charge extra if the design contains additional sizes. You can put this list in a â??vendor resource fileâ??. This file may also exceptions and specify if the nearest diameter should be chosen, or rounded up to the next size in the list. See <a href="http://pcb.gpleda.org/pcb-cvs/pcb.html#Vendor-drill-mapping"; class="urlextern" title="http://pcb.gpleda.org/pcb-cvs/pcb.html#Vendor-drill-mapping"; rel="nofollow">the section Vendor-drill-mapping</a> in the pcb manual for the syntax of this file.
+</p>
+
+<p>
+Load the file to pcb with Load-Vendor-Resource-File from the main menu. Alternatively, you can use with the command :LoadVendor(drillfile). Substitute â??drillfileâ?? with the name of your file.
+</p>
+
+<p>
+On load, pcb will substitute drill sizes so that the layout conforms to the list. If you want to apply an already loaded vendor resource file again, you can do Apply-vendor-drill-mapping from the connects menu.
+</p>
+
+</div>
+<!-- SECTION "How do I make sure, that the design contains only certain hole sizes?" [58515-59486] -->
+<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>
+<li class="level1"><div class="li"> Run a check of design rules either through the command interface (â??DRC()") or from the menu (Connects - Design Rule Checker). You can set the rules in the sizes section of the preference dialog. Results of the check are shown in the log window. </div>
+</li>
+</ul>
+
+<p>
+Besides running the DRC checker, it is essential to check your Gerber files. The gEDA Suite includes the program â??gerbvâ?? for this task. Here are some things to check/verify:
+</p>
+<ul>
+<li class="level1"><div class="li"> Check that all trace widths are the correct size. Also make sure your trace widths and metal-metal separations are above the minimum specified by your PCB vendor.</div>
+</li>
+<li class="level1"><div class="li"> Check that all hole diameters are called out at the correct size.</div>
+</li>
+<li class="level1"><div class="li"> Check that metal annular rings around holes/vias are large enough. The annular ring is the distance between the holeâ??s edge and the outer diameter of the metallization. The annular ring must be large enough to accomodate drill location + layer registration + other manufacturing inaccuracy. This information should be available from your PCB fabrication house; they normally publish the minimum annular ring requirements in their manufacturing rules document.</div>
+</li>
+<li class="level1"><div class="li"> Check that your antipads (clearance around holes/vias) are large enough. This information should be available from your PCB fabrication house; ask them for their manufacturing rules document.</div>
+</li>
+<li class="level1"><div class="li"> Verify that no soldermask or silkscreen overlays a copper pad or through-hole.</div>
+</li>
+<li class="level1"><div class="li"> On plane layers, verify that at least some vias connect to it (yes, I have seen a board where the entire ground plane was floating â?? not done in pcb btw)</div>
+</li>
+<li class="level1"><div class="li"> On plane layers, verify that at least some vias _donâ??t_ connect to it.</div>
+</li>
+<li class="level1"><div class="li"> Do a visual sanity check of all layers. Nothing detailed, just does it look approximately like you think it should.</div>
+</li>
+<li class="level1"><div class="li"> Are all layers negative/positive as they should be? Note that some fab houses want positive layers only. PCB will automatically create negative Gerbers on outer layer planes with no tracks. If you want an all-plane layer to be output as a positive layer, draw a single track somewhere in an unused part of the plane. This will trigger PCB to render that layer as a positive layer.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "I'm done with my layout. How should I check my design?" [59487-61706] -->
+<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" [61707-61766] -->
+<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">
+
+<p>
+It limits the size of the image to NxN pixels, but maintains the aspect ratio. For example, if you set it to 400, a 6000×8000 mil board would yield a 300×400 image, but a 6000×4500 board yeilds a 400×300 image.
+</p>
+
+</div>
+<!-- SECTION "What is xy-max in the PNG export dialog box?" [61767-62037] -->
+<h1><a name="customization" id="customization">Customization</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "Customization" [62038-62066] -->
+<h2><a name="i_don_t_like_that_old-style_black_background._how_can_i_get_a_light_canvas" id="i_don_t_like_that_old-style_black_background._how_can_i_get_a_light_canvas">I don't like that old-style black background. How can I get a light canvas?</a></h2>
+<div class="level2">
+
+<p>
+In <a href="geda-glossary.html" class="wikilink1" title="geda-glossary.html">GTK-HID</a> there is a preference dialog in the file menu. The Colors tab presents a convinient way to set all the colros pcb uses via the standard GTK color chooser. The colors are saved to $HOME/.pcb/preferences on shut down of the application. With <a href="geda-glossary.html" class="wikilink1" title="geda-glossary.html">Lesstif-HID</a> there is no preference dialog. Colors can be set in <code>$HOME/.pcb/settings</code>
+</p>
+
+</div>
+<!-- SECTION "I don't like that old-style black background. How can I get a light canvas?" [62067-62521] -->
+<h2><a name="how_do_i_set_the_default_values_of_the_postscript_dialog" id="how_do_i_set_the_default_values_of_the_postscript_dialog">How do I set the default values of the postscript dialog?</a></h2>
+<div class="level2">
+
+<p>
+You can set the default options of the postscript printing dialog as command line parameters when invoking pcb. Type <code>pcb –help</code> for a list of available options. These options can also be set in a file <code>$HOME/.pcb/settings</code>. A settings file for a4 paper, no alignment marks, multi page output would contain:
+</p>
+<pre class="code">media = A4
+align-marks = 0
+multi-file = 1</pre>
+
+</div>
+<!-- SECTION "How do I set the default values of the postscript dialog?" [62522-62960] -->
+<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">
+
+<p>
+<a href="http://www.luciani.org/geda/pcb/faq-pcb-footprint.html"; class="urlextern" title="http://www.luciani.org/geda/pcb/faq-pcb-footprint.html"; rel="nofollow">http://www.luciani.org/geda/pcb/faq-pcb-footprint.html</a><br/>
+ <a href="http://pcb.sourceforge.net/faq.html"; class="urlextern" title="http://pcb.sourceforge.net/faq.html"; rel="nofollow">http://pcb.sourceforge.net/faq.html</a><br/>
+ <a href="http://pcb.sourceforge.net/pcb-20060822/pcb.html#Top"; class="urlextern" title="http://pcb.sourceforge.net/pcb-20060822/pcb.html#Top"; rel="nofollow">http://pcb.sourceforge.net/pcb-20060822/pcb.html#Top</a>
+</p>
+
+<p>
+You can get fast responses from the geda-user email list. If you havenâ??t found an answer to your question about PCB on this page, or in the other documentation, then post to the list! Note that you must subscribe to the geda-user e-mail list before you can post to the list. The gEDA e-mail lists, and their archives, are at: <a href="http://geda.seul.org/mailinglist/index.html"; class="urlextern" title="http://geda.seul.org/mailinglist/index.html"; rel="nofollow">http://geda.seul.org/mailinglist/index.html</a>
+</p>
+
+</div>
+<!-- SECTION "You didn't answer my question. What other resources exist for PCB information?" [62961-] --></body>
+</html>
diff --git a/docs/wiki/geda-release_engineering.html b/docs/wiki/geda-release_engineering.html
new file mode 100644
index 0000000..011a9a4
--- /dev/null
+++ b/docs/wiki/geda-release_engineering.html
@@ -0,0 +1,136 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="geda_s_release_engineering" id="geda_s_release_engineering">gEDA's Release Engineering</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "gEDA's Release Engineering" [1-44] -->
+<h2><a name="geda_gaf_release_creation_checklist" id="geda_gaf_release_creation_checklist">gEDA/gaf Release Creation Checklist</a></h2>
+<div class="level2">
+
+<p>
+ Here is a list of steps that are taken every time when creating a new gEDA/gaf release:
+</p>
+<ul>
+<li class="level1"><div class="li"> Update the toplevel NEWS file with a summary of all the changes in the new release. The NEWS file forms the basis for the release notes.</div>
+</li>
+<li class="level1"><div class="li"> Manually run all tests. gnetlist has a nice set of regression tests in gnetlist/tests. gsymcheck also has a nice set of regression tests in gsymcheck/tests. Open up all schematics in gschem/examples and gschem/tests. You can do this by running the following in the toplevel directory:</div>
+</li>
+</ul>
+<pre class="code">
+ make check
+</pre>
+<ul>
+<li class="level1"><div class="li"> Run make update-po in all po directories. Commit these changes before continuing.</div>
+</li>
+<li class="level1"><div class="li"> In the toplevel configure.ac file update the package version in the AC_INIT macro, the date in the AX_GIT_VERSION macro, and update libgedaâ??s shared library version (libgedaâ??s so version should follow what is described in <a href="http://sourceware.org/autobook/autobook/autobook_91.html"; class="urlextern" title="http://sourceware.org/autobook/autobook/autobook_91.html"; rel="nofollow"> Autobook's library versioning</a> chapter).</div>
+</li>
+<li class="level1"><div class="li"> Update all the versions and dates in the man pages (gschem.1, gnetlist.1, gsymcheck.1)</div>
+</li>
+<li class="level1"><div class="li"> Update the wiki documentation (this is far far far too manual)</div>
+</li>
+</ul>
+<pre class="code">
+ cd docs
+ mkdir wip
+ cd wip
+ ../scripts/wikifetch.sh
+ rm -f *.txt
+ mv geda.seul.org/wiki/* .
+ rmdir geda.seul.org/wiki
+ rmdir geda.seul.org
+ ../scripts/postproc.sh
+ find . -name *.orig -exec rm -f {} \; -print
+ cd ..
+ scripts/copygitignores.sh
+ cd wip
+ ../scripts/populatemkfiles.sh
+ vi `find . -name Makefile.am` (Make sure all files have correct install path)
+ cd ..
+ diff -r -q wiki wip | grep -v Only | sed "s/Files /tkdiff /" | sed "s/ and//" | sed "s/differ//" > diffs
+ sh diffs (and examine all changes; you need to have tkdiff installer or use just plain diff above)
+ mv wiki wiki.original
+ mv wip wiki
+ git status
+ git add <any new files>
+ git commit -a
+</pre>
+<ul>
+<li class="level1"><div class="li"> Commit all of the above changes (preferably in between each step)</div>
+</li>
+<li class="level1"><div class="li"> To build the distribution tarball (and verify all tests on the contained files) run: </div>
+</li>
+</ul>
+<pre class="code">
+ make distcheck
+</pre>
+
+<p>
+and make sure it completes without any errors. After this is complete you will find the distribution tarball in the toplevel directory (named gEDA-gaf-VERSION.tar.gz).
+</p>
+<ul>
+<li class="level1"><div class="li"> Copy the distribution tarball some place else along with the toplevel README (which should be renamed to gEDA-gaf-VERSION-README.txt).</div>
+</li>
+<li class="level1"><div class="li"> Create a file the md5sum for the toplevel tarball. </div>
+</li>
+</ul>
+<pre class="code">
+ md5sum -b gEDA-gaf-1.5.3.tar.gz > gEDA-gaf-1.5.3.md5sum
+</pre>
+<ul>
+<li class="level1"><div class="li"> Untar the tarballs and compare what is inside to what is in the repository. You should only find additional dist files inside the tarballs and no missing required files.</div>
+</li>
+<li class="level1"><div class="li"> Build and test the distribution tarball one last time.</div>
+</li>
+<li class="level1"><div class="li"> Make sure everything is committed and pushed and then put down the correctly formatted tag:</div>
+</li>
+</ul>
+<pre class="code">
+ git tag -a 1.5.3-20090829
+</pre>
+<ul>
+<li class="level1"><div class="li"> Push all the commits to the main repository. If you are on a branch the command should be: </div>
+</li>
+</ul>
+<pre class="code">
+ git push origin remote_branch_name
+</pre>
+<ul>
+<li class="level1"><div class="li"> Push the tag to the main repository:</div>
+</li>
+</ul>
+<pre class="code">
+ git push --tags
+</pre>
+<ul>
+<li class="level1"><div class="li"> Upload distribution tarball, README, and md5sum file to the correct place</div>
+</li>
+<li class="level1"><div class="li"> Write release announcement and send to mailing lists</div>
+</li>
+<li class="level1"><div class="li"> Write up release notes and send pointer to mailing lists (named: gEDA-gaf-VERSION-releasenotes.html)</div>
+</li>
+<li class="level1"><div class="li"> Update news update the sources download pages on the website with links to the new version</div>
+</li>
+<li class="level1"><div class="li"> Update the geda:todos page moving the release into the historical todos page.</div>
+</li>
+<li class="level1"><div class="li"> Done!</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "gEDA/gaf Release Creation Checklist" [45-] --></body>
+</html>
diff --git a/docs/wiki/geda-scg.fr.html b/docs/wiki/geda-scg.fr.html
new file mode 100644
index 0000000..dae7f3d
--- /dev/null
+++ b/docs/wiki/geda-scg.fr.html
@@ -0,0 +1,608 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#geda_gaf_symbol_creation_document" class="toc">gEDA/gaf Symbol Creation Document</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#overview" class="toc">Overview</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#component_symbol_creation" class="toc">Component symbol creation</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#requirements" class="toc">Requirements</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#style" class="toc">Style</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#text" class="toc">Text</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#attributes" class="toc">Attributes</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#graphics" class="toc">Graphics</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#pins" class="toc">Pins</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#electrical" class="toc">Electrical</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#footprint_naming_conventions" class="toc">Footprint naming conventions</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#notes" class="toc">Notes</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#integrated_circuit_packages" class="toc">Integrated circuit packages</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#integrated_circuit_smt_packages" class="toc">Integrated circuit SMT packages</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#basic_semiconductors" class="toc">Basic semiconductors</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#basic_smt_semiconductors" class="toc">Basic SMT semiconductors</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#passive_components" class="toc">Passive components</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#passive_smt_components" class="toc">Passive SMT components</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#hints_and_tips" class="toc">Hints and Tips</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#example" class="toc">Example</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#document_revision_history" class="toc">Document Revision History</a></span></div></li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="geda_gaf_symbol_creation_document" id="geda_gaf_symbol_creation_document">gEDA/gaf Symbol Creation Document</a></h1>
+<div class="level1">
+
+<p>
+by: Ales V. Hvezda / July 6th, 2004
+</p>
+
+<p>
+The latest version of this document may be found at: <a href="http://geda.seul.org/wiki/geda:scg"; class="urlextern" title="http://geda.seul.org/wiki/geda:scg"; rel="nofollow">http://geda.seul.org/wiki/geda:scg</a>
+</p>
+
+<p>
+This document is released under the <a href="geda-gfdl.html" class="wikilink1" title="geda-gfdl.html">GNU Free Documentation License (GFDL)</a>.
+</p>
+
+</div>
+<!-- SECTION "gEDA/gaf Symbol Creation Document" [1-264] -->
+<h2><a name="overview" id="overview">Overview</a></h2>
+<div class="level2">
+
+<p>
+This document describes the creation of component symbols, including style conventions, and hints/tips and things to look out for when drawing symbols for the gEDA/gaf system.
+</p>
+
+</div>
+<!-- SECTION "Overview" [265-462] -->
+<h2><a name="component_symbol_creation" id="component_symbol_creation">Component symbol creation</a></h2>
+<div class="level2">
+
+<p>
+Component symbols (from here on known as â??symbolsâ??) are drawn using gschem just like drawing a schematic sheet. Here are the steps in a symbol in the gEDA/gaf system:<br/>
+ 1. Run gschem and find a blank page or run: gschem filename-1.sym<br/>
+ 2. Draw the symbol (see the style guide below for some conventions).<br/>
+ 3. Translate the symbol to the origin using Edit/Symbol Translate…<br/>
+
+</p>
+<ul>
+<li class="level1"><div class="li"> Zoom in at least one step.</div>
+</li>
+<li class="level1"><div class="li"> Make sure the snap is ON (this is critical).</div>
+</li>
+<li class="level1"><div class="li"> Make sure grid snap size is set to 100 (this is critical).</div>
+</li>
+<li class="level1"><div class="li"> Select â??Symbol Translate…â?? or the press equivalent hotkey.</div>
+</li>
+<li class="level1"><div class="li"> Enter 0 into the entry field and press OK.<br/>
+</div>
+</li>
+</ul>
+
+<p>
+Translating the symbol to the origin is a required step. To translate a symbol elsewhere, enter a offset (in mils) which is a even multiple of 100. Make sure all pins are snapped to a 100 mil grid point.
+</p>
+
+<p>
+4. Save the symbol using Save or SaveAs… Here are some symbol naming conventions:<br/>
+
+</p>
+<ul>
+<li class="level1"><div class="li"> Symbols are named: symbolname-#.sym</div>
+</li>
+<li class="level1"><div class="li"> Symbols end with a .sym extension.</div>
+</li>
+<li class="level1"><div class="li"> Symbols have a -# where # is a number. Typically # is 1 but if there are multiple symbols for a device then this number simply increments.</div>
+</li>
+<li class="level1"><div class="li"> Symbol names are typically lowercase but letters which are part of a part number are uppercase.</div>
+</li>
+<li class="level1"><div class="li"> The above case rule can be broken if the filename looks incorrect or wrong.</div>
+</li>
+</ul>
+
+<p>
+ 5. Place the symbol in one of the directories specified by the componentlibrary keyword in the system-gafrc file. Once this is done, the symbol should be visible immediately and can be selected and placed with the â??Add/Select Component…â?? menu item.
+</p>
+
+</div>
+<!-- SECTION "Component symbol creation" [463-2082] -->
+<h2><a name="requirements" id="requirements">Requirements</a></h2>
+<div class="level2">
+
+<p>
+This section describes the various requirements which must be met in order to create a valid symbol which will display and netlist in the gEDA/gaf system. Most of the requirements center around having certain attributes attached or inside the symbol.<br/>
+ Running gsymcheck will check that all of these requirements are met. gsymcheck will output fatal errors which are quite serious and must be corrected. gsymcheck will also output warnings on things which should be fixed but are not fatal.<br/>
+ For more information on the attributes presented here, please see the Master Attribute Document.
+</p>
+<ul>
+<li class="level1"><div class="li"> device=DEVICENAME should be placed somewhere in the symbol and made invisible. device= is the device name and is required. Typically the devicename is in all caps (capital letters). This attribute should not be used as a label. Use a separate text object for the label. If the object is a graphic then device= should be set to none (device=none). It is no longer required to attach this attribute anything; just having it exist as device=DEVICENAME is good enough.</div>
+</li>
+<li class="level1"><div class="li"> graphical=1 should exist somewhere in a symbol which is purely graphical (such as a title block or decon symbol). Symbols which have this attribute have no electrical or circuit significance. Donâ??t forget to set device=none.</div>
+</li>
+<li class="level1"><div class="li"> description=text should exist somewhere in the symbol. This attribute provides an one line description of the symbol.</div>
+</li>
+<li class="level1"><div class="li"> All pins should have a pair of attributes attached to them: pinseq=# and pinnumber=#. The first attribute, pinseq=# is just a sequence number and increments sequentially starting at 1. The second attribute pinnumber=# is the number of the pin. When a symbol is netlisted, the pin numbers are output in order of pin sequence. The pin number can be alphanumeric (i.e. like E or C).</div>
+</li>
+<li class="level1"><div class="li"> All pins should also have pinlabel=value attached to them. This attribute is the name or label of the pin (vs the pin number). This attribute is also used when a symbol is used in a hierarchical schematic. Please make this attribute green (instead of the default attribute yellow).</div>
+</li>
+<li class="level1"><div class="li"> All pins should also have pintype=value attached to them. This attribute describes the kind of a pin. Possible values are: in, out, io, oc, oe, pas, tp, tri, clk, pwr. Please see the Master Attribute Document for more info.</div>
+</li>
+<li class="level1"><div class="li"> If a component has multiple slots in a package (such as a 7400 (NAND) which has 4 NANDs per package) then you need a numslots=# attribute. The # is the number of slots the device has. numslots= should be exist somewhere in the symbol and made invisible. Additional slot related required attributes are described below.</div>
+</li>
+<li class="level1"><div class="li"> If a component has multiple slots in a physical package then you also need to include a slotdef=#:#,#,#… for every slot. The first # corresponds to the slot number. If a device has 4 slots then there should be slotdef=1:…, slotdef=2:…, slotdef=3:…, and slotdef=4:…, attributes existing somewhere in the symbol and made invisible. The subsequent # have a one-to-one correspondence to pinseq=# attributes and specify what corresponding pinnumber=# should be when that slot is set. See The attached 7400-1.sym as an example of how this should all work.</div>
+</li>
+<li class="level1"><div class="li"> It is recommended that all symbols which have slots have a slot=1 attribute inside the symbol.</div>
+</li>
+<li class="level1"><div class="li"> footprint=PACKAGENAME should exist somewhere in the symbol which might be used with the PCB netlister. PACKAGENAME is the PCB footprint or package type like DIP14 or DIP40. Please see the Footprint naming conventions chapter for further detail. See also the PCB documentation and gnetlist/docs/README.pcb for more info on this attribute.</div>
+</li>
+<li class="level1"><div class="li"> You should put a refdes=U? attribute inside the symbol. Make only the value visible and it will be promoted (attached to the outside of the symbol (so it can be edited) when the symbol is placed in a schematic.</div>
+</li>
+<li class="level1"><div class="li"> The label= attribute should not be attached anywhere in the symbol. It is obsolete.</div>
+</li>
+<li class="level1"><div class="li"> The name= attribute should not be attached anywhere in the symbol.</div>
+</li>
+<li class="level1"><div class="li"> The netname= attribute should not be attached anywhere in the symbol. It is only used in schematics.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Requirements" [2083-6223] -->
+<h2><a name="style" id="style">Style</a></h2>
+<div class="level2">
+
+<p>
+This section describes the style in which is used in the standard gEDA/gaf symbol library.
+</p>
+
+</div>
+<!-- SECTION "Style" [6224-6333] -->
+<h3><a name="text" id="text">Text</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> All Text labels should all be 10 pt in size.</div>
+</li>
+<li class="level1"><div class="li"> Text (labels not attributes) should be color number 9 (text | green).</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Text" [6334-6472] -->
+<h3><a name="attributes" id="attributes">Attributes</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> Pin numbers (which are attributes) should all be 8 pt in size.</div>
+</li>
+<li class="level1"><div class="li"> Attached attributes should be yellow. The color is set automatically to yellow if the text item is attached.</div>
+</li>
+<li class="level1"><div class="li"> The only exception to this is pinlabel= attributes, those should be color number 9 (text | green). If every text item within a symbol is yellow, the symbol looks too yellow.</div>
+</li>
+<li class="level1"><div class="li"> Attributes can be attached to some part of the symbol. Toplevel attributes (like the device= or net= attributes) used to be required to be attached to something to be attributes, but now they just have to exist in the symbol file as name=value.</div>
+</li>
+<li class="level1"><div class="li"> Expanding a bit on the last sentence, as long as the text item has the format name=value, it is considered an attribute. Attributes inside a symbol do not have to be attached to anything. In order to see hidden attributes in gschem select Edit/Show/Hide Inv Text.</div>
+</li>
+<li class="level1"><div class="li"> There is a symbol content versioning system in libgeda which is based on the symversion= attribute. Please see the Master Attribute Document for more information on using this versioning scheme.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Attributes" [6473-7569] -->
+<h3><a name="graphics" id="graphics">Graphics</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> Lines, boxes, arcs, and any other graphics should be color number 3 (graphic | green).</div>
+</li>
+<li class="level1"><div class="li"> Polarity bubbles should be color number 6 (logic bubble | cyan)</div>
+</li>
+<li class="level1"><div class="li"> If you are unsure on how to make a new symbol look or how big to make a new symbol, look at the existing symbols to get a feel for the appropriate appearance and size.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Graphics" [7570-7920] -->
+<h3><a name="pins" id="pins">Pins</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> Pins should all be 300 mils (3 grid spaces) long.</div>
+</li>
+<li class="level1"><div class="li"> For pins which are next to a logic bubble, make the pins 200 mils (2 grid spaces) long and then make the logic bubble 100 mils in diameter. In order to draw a 100 mil diameter circle, you will need to change the snap spacing to 50.</div>
+</li>
+<li class="level1"><div class="li"> A pin has two ends: one end has a red endpoint and one end that does not. The red endpoint is where nets can be connected. You can either rotate the pin so that this active end is in the right place or manually edit the symbol file changing the â??whichendâ?? parameter on the pin object. See the File Format document for more info.</div>
+</li>
+<li class="level1"><div class="li"> Be that all endpoints of pins which are meant to be connected to are on the 100 mil grid. The endpoint which is not active can be off the grid if necessary.</div>
+</li>
+<li class="level1"><div class="li"> Pins should be color number 1 (pins | white).</div>
+</li>
+<li class="level1"><div class="li"> Leave 400 mils (4 grid spaces) between (vertically) pins, unless you are drawing a special symbol, then just try to make it look good.</div>
+</li>
+<li class="level1"><div class="li"> Pin number attributes should be 50 mils above (or below; which ever makes the most sense) the pin which they are attached to.</div>
+</li>
+<li class="level1"><div class="li"> Input pins belong on the left and output pins belong on the right of the symbol.</div>
+</li>
+<li class="level1"><div class="li"> Please do not mix inputs and outputs on the same side of the symbol, unless absolutely necessary.</div>
+</li>
+<li class="level1"><div class="li"> You can have pins on the top or bottom of a symbol.</div>
+</li>
+<li class="level1"><div class="li"> The order for rows of pins (buses) should be LSB (least significant bit) to MSB (most significant bit). When drawing pins which are part of a bus, make sure the LSB of the bus is at the top (or for pins on top/bottom of a symbol, left of the rest of the other pins). Look at 74/74181-1.sym for a correct example of this order (A0 on top through A3 and B0 on top through B3). Violating this rule will make connecting buses much more diffcult.</div>
+</li>
+<li class="level1"><div class="li"> When placing pins on logic gates, be sure to place the smallest pin numbers toward the top (or left) and then increment going down (or across).</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Pins" [7921-9876] -->
+<h3><a name="electrical" id="electrical">Electrical</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> Do not draw power and ground pins. That information will be conveyed using attributes (see the netattrib document).</div>
+</li>
+<li class="level1"><div class="li"> The above rule can be broken if necessary, but keep in mind most of the standard library does not have power pins showing.</div>
+</li>
+<li class="level1"><div class="li"> Keep in mind, symbols are supposed to be symbolic, they do not represent the physical package that the device comes in.</div>
+</li>
+<li class="level1"><div class="li"> There is some disagreement on above, so this is okay too: Arrange the pins on a symbol logically so that they promote an uncluttered schematic. Note that this is frequently not the same pin arrangement as the physical device.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Electrical" [9877-10499] -->
+<h2><a name="footprint_naming_conventions" id="footprint_naming_conventions">Footprint naming conventions</a></h2>
+<div class="level2">
+
+<p>
+This section describes the conventions for naming of footprints used in gEDA/gaf.<br/>
+ The purpose of the naming convention is to establish a standard to maintain the same naming convention through the different phases of the CAD chain. This helps in ensuring that the collaborative effort of gEDA/gaf is not lost.
+</p>
+
+</div>
+<!-- SECTION "Footprint naming conventions" [10500-10853] -->
+<h3><a name="notes" id="notes">Notes</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> Unless otherwise noted, numerical pin names will be used, starting from 1.</div>
+</li>
+<li class="level1"><div class="li"> n is for the pin count.</div>
+</li>
+<li class="level1"><div class="li"> m is for the pin spacing in mils.</div>
+</li>
+<li class="level1"><div class="li"> x is for the x dimension of the package (excluding pins). In particular this is used for the QFP package family.</div>
+</li>
+<li class="level1"><div class="li"> SMT means surface mount, other components are through-hole.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Notes" [10854-11196] -->
+<h3><a name="integrated_circuit_packages" id="integrated_circuit_packages">Integrated circuit packages</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> Dual in line packages with up to 22 100 mil spaced pins and 300 mil row spacing are called DIPn.</div>
+</li>
+<li class="level1"><div class="li"> Dual in line packages with 24 or more 100 mil spaced pins and 300 mil row spacing are called DIPnN.</div>
+</li>
+<li class="level1"><div class="li"> Dual in line packages with 100 mil spaced pins and 400 mil row spacing are called DIPnH.</div>
+</li>
+<li class="level1"><div class="li"> Dual in line packages with 24 or more 100 mil spaced pins and 600 mil row spacing are called DIPn.</div>
+</li>
+<li class="level1"><div class="li"> Shrink dual in line packages with up to 24 70 mil spaced pins and 300 mil row spacing are called SDIPn.</div>
+</li>
+<li class="level1"><div class="li"> Shrink dual in line packages with more than 24 70 mil spaced pins and 400 mil row spacing are called SDIPn.</div>
+</li>
+<li class="level1"><div class="li"> Single in line packages with 100 mil spaced pins are called SIPnN. See also JUMPER, below.</div>
+</li>
+<li class="level1"><div class="li"> Zig-zag in-line package are called ZIPn.</div>
+</li>
+<li class="level1"><div class="li"> Plastic leadless chip carrier with pin socket are called PLCCnX.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Integrated circuit packages" [11197-12065] -->
+<h3><a name="integrated_circuit_smt_packages" id="integrated_circuit_smt_packages">Integrated circuit SMT packages</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> Small outline SMT packages with up to 16 50 mil spaced pins and 150 mil total width are called SOn.</div>
+</li>
+<li class="level1"><div class="li"> Small outline SMT packages with more than 16 50 mil spaced pins and 150 mil total width are called SOnN.</div>
+</li>
+<li class="level1"><div class="li"> Small outline SMT packages with 50 mil spaced pins and 200 mil total width are called SOnM.</div>
+</li>
+<li class="level1"><div class="li"> Small outline SMT packages with up to 20 50 mil spaced pins and 300 mil total width are called SOnW.</div>
+</li>
+<li class="level1"><div class="li"> Small outline SMT packages with more than 20 50 mil spaced pins and 300 mil total width are called SOn.</div>
+</li>
+<li class="level1"><div class="li"> Small outline SMT packages with 44 or more 50 mil spaced pins and 525 mil total width are called SOn.</div>
+</li>
+<li class="level1"><div class="li"> Metric shrink small outline SMT packages with 0.65 mm spaced pins and 323 mil total width are called MSSOPn. NOTE: To be confirmed.</div>
+</li>
+<li class="level1"><div class="li"> Metric shrink small outline SMT packages with up to 44 0.65 mm spaced pins and 420 mil total width are called MSSOPnW.</div>
+</li>
+<li class="level1"><div class="li"> Metric shrink small outline SMT packages with over 44 0.65 mm spaced pins and 545 mil total width are called MSSOPnW.</div>
+</li>
+<li class="level1"><div class="li"> Shrink small outline SMT packages with 25 mil spaced pins and 420 mil total width are called SSOPnW.</div>
+</li>
+<li class="level1"><div class="li"> Quarter size small outline SMT packages with 25 mil spaced pins and 244 mil total width are called SSOPn.</div>
+</li>
+<li class="level1"><div class="li"> Thin small outline SMT packages with 21.65 mil spaced pins and 535 mil total width are called TSOPn.</div>
+</li>
+<li class="level1"><div class="li"> Thin small outline SMT packages with 20 mil spaced pins and 795 mil total width are called TSOPnA.</div>
+</li>
+<li class="level1"><div class="li"> Thin small outline SMT packages with 20 mil spaced pins and 559 mil total width are called TSOPnB.</div>
+</li>
+<li class="level1"><div class="li"> Thin shrink small outline SMT packages with up to 28 26 mil spaced pins and 260 mil total width are called TSSOPn.</div>
+</li>
+<li class="level1"><div class="li"> Thin shrink small outline SMT packages with over 28 20 mil spaced pins and 319 mil total width are called TSSOPn.</div>
+</li>
+<li class="level1"><div class="li"> Ultra Super Mini SMT packages with up to 16 0.5 mm spaced pins are called USn.</div>
+</li>
+<li class="level1"><div class="li"> Plastic leadless chip carrier SMT are called PLCCn.</div>
+</li>
+<li class="level1"><div class="li"> Square quad-side at pack SMT are called QFPn x.</div>
+</li>
+<li class="level1"><div class="li"> Rectangular quad-side at pack SMT are called QFPn R.</div>
+</li>
+<li class="level1"><div class="li"> Square low profile quad-side at pack SMT are called LQFPn x.</div>
+</li>
+<li class="level1"><div class="li"> Square thin quad-side at pack SMT are called TQFPn x.</div>
+</li>
+<li class="level1"><div class="li"> Square Quad-side at no-lead SMT without exposed paddle (back side contact) are called QFNn x. Pin count is n and package size is x mm.</div>
+</li>
+<li class="level1"><div class="li"> Square Quad-side at no-lead SMT with exposed paddle (back side contact) are called QFNn x EP. Pin count is n and package size is x mm.</div>
+</li>
+<li class="level1"><div class="li"> Thin profile square Quad-side at no-lead SMT without exposed paddle (back side contact) are called TQFNn x. Pin count is n and package size is x mm.</div>
+</li>
+<li class="level1"><div class="li"> Thin profile square Quad-side at no-lead SMT with exposed paddle (back side contact) are called TQFNn x EP. Pin count is n and package size is x mm.</div>
+</li>
+<li class="level1"><div class="li"> Dual in line style crystal oscillators are OSC8 and OSC14.</div>
+</li>
+<li class="level1"><div class="li"> 5 pin SOT SMT packages are SOT25 and SOT325.</div>
+</li>
+<li class="level1"><div class="li"> 6 pin SOT SMT packages are SOT26 and SOT326.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Integrated circuit SMT packages" [12066-14996] -->
+<h3><a name="basic_semiconductors" id="basic_semiconductors">Basic semiconductors</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> Axial diodes are called ALFm. Pin 1 is the cathode.</div>
+</li>
+<li class="level1"><div class="li"> Conventional through hole LED is LED3 and LED5 for 3 and 5 mm respectively. Pin 1 is plus. NOTE: Should probably be changed to be in line with diode convention.</div>
+</li>
+<li class="level1"><div class="li"> TO transistors are TO5, TO92, TO126, TO220 etc. Suxes may apply, e.g. TO126W is for wide, TO126S is for standing, TO126SW is for standing, wide.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Basic semiconductors" [14997-15399] -->
+<h3><a name="basic_smt_semiconductors" id="basic_smt_semiconductors">Basic SMT semiconductors</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> SOD diode SMT packages use their standard package name, e.g. SOD80, SOD87, SOD106A, SOD110. There are also SOD123, SOD323 with narrow pads.</div>
+</li>
+<li class="level1"><div class="li"> SOT transistor SMT packages use their standard package name, e.g. SOT23, SOT323. There is also an SC90.</div>
+</li>
+<li class="level1"><div class="li"> SOT transistor SMT packages with numbering as for diodes (pin 1 is cathode, pin 2 anode) are SOT23D, SOT323D.</div>
+</li>
+<li class="level1"><div class="li"> 4 pin SOT SMT packages are SOT89, SOT143, SOT223.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Basic SMT semiconductors" [15400-15855] -->
+<h3><a name="passive_components" id="passive_components">Passive components</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> Axial non-polar components (typically resistor, capacitor) are called ACYm.</div>
+</li>
+<li class="level1"><div class="li"> Bottom lead (radial) non-polar circular component (typically capacitor) is RCYm.</div>
+</li>
+<li class="level1"><div class="li"> Bottom lead non-polar rectangular component (typically capacitor) is BREm.</div>
+</li>
+<li class="level1"><div class="li"> A standard crystal is HC49, or other HC designations as required.</div>
+</li>
+<li class="level1"><div class="li"> Single row 100 mil pin spacing jumpers are JUMPERn. The main difference compared to single in line package is the hole size.</div>
+</li>
+<li class="level1"><div class="li"> Dual row 100 mil spacing headers with DIP pin numbering are HEADERn 1. Note that n is an even number.</div>
+</li>
+<li class="level1"><div class="li"> Dual row 100 mil spacing headers with ribbon cable numbering are HEADERn 2. Note that n is an even number.</div>
+</li>
+<li class="level1"><div class="li"> Angled full header connectors with latches are DIN41651 n.</div>
+</li>
+<li class="level1"><div class="li"> Standing full header connectors with latches are DIN41651 nS.</div>
+</li>
+<li class="level1"><div class="li"> DSUB connectors female are DBnF.</div>
+</li>
+<li class="level1"><div class="li"> DSUB connectors male are DBnM.</div>
+</li>
+<li class="level1"><div class="li"> Female DIN card-to-card connectors are DIN41612CnF. Add S suffix for standing.</div>
+</li>
+<li class="level1"><div class="li"> Male DIN card-to-card connectors are DIN41612CnM. Add S suffix for standing.</div>
+</li>
+<li class="level1"><div class="li"> AMP modular RJ connectors with screen are RJ11, RJ12 and RJ45.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Passive components" [15856-16977] -->
+<h3><a name="passive_smt_components" id="passive_smt_components">Passive SMT components</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> Standard SMT resistors, inductors, capacitors etc are 0201, 0402, 0603, 0805, 1206, 1210, 1806, 1812, 1825, 2020, 2706.</div>
+</li>
+<li class="level1"><div class="li"> Tantalum SMT capacitors are EIA3216, EIA3528, EIA6032, and EIA7343. Pin 1 is plus.</div>
+</li>
+<li class="level1"><div class="li"> SMT electrolytics are designated by can diameter in 1/10 mm: SME33, SME43, SME53, SME66, SME84, SME104.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Passive SMT components" [16978-17330] -->
+<h2><a name="hints_and_tips" id="hints_and_tips">Hints and Tips</a></h2>
+<div class="level2">
+
+<p>
+This section describes some hints and tips which will make your symbol creation experience easier.<br/>
+
+</p>
+<ul>
+<li class="level1"><div class="li"> Avoid drawing things off of the grid. If you do, you cannot move the object(s) using the move command (if the grid is on) since the object will be snapped to the grid. [This was an old bug, which I think has been fixed, but avoid doing this anyway]. Use the symbol translate command instead (or move the object with grid snap off)</div>
+</li>
+<li class="level1"><div class="li"> If you need a finer grid then use Options/Snap Grid Spacing… to set a finer grid snap spacing. Just remember to set this back to 100 once you are ready to translate the symbol to the origin.</div>
+</li>
+<li class="level1"><div class="li"> If you want to translate a symbol from the origin to elsewhere, then use the â??Symbol translateâ?? command and enter a non zero number. Make sure this number is a multiple of 100 (ie 1000, or 1100).</div>
+</li>
+<li class="level1"><div class="li"> Pins MUST be snapped on the 100 spaced grid (at least the end which will have nets connected to it).</div>
+</li>
+<li class="level1"><div class="li"> Pins MUST be snapped on the 100 spaced grid (at least the end which will have nets connected to it). Yes this is line a duplicate. I canâ??t stress this point enough.</div>
+</li>
+<li class="level1"><div class="li"> Remember that pins are special objects; if you want to add a pin, make sure it is a pin and not a line or net. Use the Add/Pin command to place a pin.</div>
+</li>
+<li class="level1"><div class="li"> Donâ??t include nets or buses inside symbols. That is not supported and doesnâ??t make much sense anyway.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Hints and Tips" [17331-18726] -->
+<h2><a name="example" id="example">Example</a></h2>
+<div class="level2">
+
+<p>
+This section provides a simple example which tries to follow all of the above rules. This symbol is of a 7400 (NAND gate).<br/>
+
+</p>
+
+<p>
+<pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">v 20031231 1
+L 300 200 300 800 3 0 0 0 -1 -1
+T 300 0 9 8 1 0 0 0 1
+7400
+L 300 800 700 800 3 0 0 0 -1 -1
+T 500 900 5 10 0 0 0 0 1
+device=7400
+T 500 1100 5 10 0 0 0 0 1
+slot=1
+T 500 1300 5 10 0 0 0 0 1
+numslots=4
+T 500 1500 5 10 0 0 0 0 1
+slotdef=1:1,2,3
+T 500 1700 5 10 0 0 0 0 1
+slotdef=2:4,5,6
+T 500 1900 5 10 0 0 0 0 1
+slotdef=3:9,10,8
+T 500 2100 5 10 0 0 0 0 1
+slotdef=4:12,13,11
+L 300 200 700 200 3 0 0 0 -1 -1
+A 700 500 300 270 180 3 0 0 0 -1 -1
+V 1050 500 50 6 0 0 0 -1 -1 0 -1 -1 -1 -1 -1
+P 1100 500 1300 500 1 0 1
+{
+T 1100 550 5 8 1 1 0 0 1
+pinnumber=3
+T 1100 450 5 8 0 1 0 2 1
+pinseq=3
+T 950 500 9 8 0 1 0 6 1
+pinlabel=Y
+T 950 500 5 8 0 1 0 8 1
+pintype=out
+}
+P 300 300 0 300 1 0 1
+{
+T 200 350 5 8 1 1 0 6 1
+pinnumber=2
+T 200 250 5 8 0 1 0 8 1
+pinseq=2
+T 350 300 9 8 0 1 0 0 1
+pinlabel=B
+T 350 300 5 8 0 1 0 2 1
+pintype=in
+}
+P 300 700 0 700 1 0 1
+{
+T 200 750 5 8 1 1 0 6 1
+pinnumber=1
+T 200 650 5 8 0 1 0 8 1
+pinseq=1
+T 350 700 9 8 0 1 0 0 1
+pinlabel=A
+T 350 700 5 8 0 1 0 2 1
+pintype=in
+}
+T 300 900 8 10 1 1 0 0 1
+refdes=U?
+T 500 2250 5 10 0 0 0 0 1
+footprint=DIP14
+T 500 2450 5 10 0 0 0 0 1
+description=4 NAND gates with 2 inputs
+T 500 2850 5 10 0 0 0 0 1
+net=Vcc:14
+T 500 3050 5 10 0 0 0 0 1
+net=GND:7
+T 500 2650 5 10 0 0 0 0 1
+documentation=http://www-s.ti.com/sc/ds/sn74hc00.pdf
+</font></pre>
+</p>
+
+<p>
+This example produces the following (using gschem):
+</p>
+
+<p>
+<a href="media/geda/symbol_7400-1_hidden.png" class="media" target="_blank" title="geda:symbol_7400-1_hidden.png"><img src="media/geda/symbol_7400-1_hidden.png" class="media" title=":geda:symbol_7400-1_hidden.png" alt=":geda:symbol_7400-1_hidden.png" /></a>
+</p>
+
+<p>
+This is the same symbol with all the hidden text visible (via Edit/Show/Hide Inv Text):
+</p>
+
+<p>
+<a href="media/geda/symbol_7400-1.png" class="media" target="_blank" title="geda:symbol_7400-1.png"><img src="media/geda/symbol_7400-1.png" class="media" title=":geda:symbol_7400-1.png" alt=":geda:symbol_7400-1.png" /></a>
+</p>
+
+</div>
+<!-- SECTION "Example" [18727-20443] -->
+<h2><a name="document_revision_history" id="document_revision_history">Document Revision History</a></h2>
+<div class="level2">
+<table class="inline">
+ <tr>
+ <td> September 14th, 2002</td><td>Created symbol.tex from symbols.html </td>
+ </tr>
+ <tr>
+ <td> October 31st, 2002</td><td>Fixed bad example symbol </td>
+ </tr>
+ <tr>
+ <td> February 11th, 2003</td><td>Footprint naming conventions added </td>
+ </tr>
+ <tr>
+ <td> September 27th, 2003</td><td>Applied Dan McMahillâ??s QFP and QFN patch </td>
+ </tr>
+ <tr>
+ <td> July 6th, 2004</td><td>Added a bunch more details/hints to the pin section </td>
+ </tr>
+</table>
+
+</div>
+<!-- SECTION "Document Revision History" [20444-] --></body>
+</html>
diff --git a/docs/wiki/geda-scg.html b/docs/wiki/geda-scg.html
new file mode 100644
index 0000000..83d058e
--- /dev/null
+++ b/docs/wiki/geda-scg.html
@@ -0,0 +1,610 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#geda_gaf_symbol_creation_document" class="toc">gEDA/gaf Symbol Creation Document</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#overview" class="toc">Overview</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#component_symbol_creation" class="toc">Component symbol creation</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#requirements" class="toc">Requirements</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#style" class="toc">Style</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#text" class="toc">Text</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#attributes" class="toc">Attributes</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#graphics" class="toc">Graphics</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#pins" class="toc">Pins</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#electrical" class="toc">Electrical</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#footprint_naming_conventions" class="toc">Footprint naming conventions</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#notes" class="toc">Notes</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#integrated_circuit_packages" class="toc">Integrated circuit packages</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#integrated_circuit_smt_packages" class="toc">Integrated circuit SMT packages</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#basic_semiconductors" class="toc">Basic semiconductors</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#basic_smt_semiconductors" class="toc">Basic SMT semiconductors</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#passive_components" class="toc">Passive components</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#passive_smt_components" class="toc">Passive SMT components</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#hints_and_tips" class="toc">Hints and Tips</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#example" class="toc">Example</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#document_revision_history" class="toc">Document Revision History</a></span></div></li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="geda_gaf_symbol_creation_document" id="geda_gaf_symbol_creation_document">gEDA/gaf Symbol Creation Document</a></h1>
+<div class="level1">
+
+<p>
+by: Ales V. Hvezda / July 6th, 2004
+</p>
+
+<p>
+The latest version of this document may be found at: <a href="http://geda.seul.org/wiki/geda:scg"; class="urlextern" title="http://geda.seul.org/wiki/geda:scg"; rel="nofollow">http://geda.seul.org/wiki/geda:scg</a>
+</p>
+
+<p>
+This document is released under the <a href="geda-gfdl.html" class="wikilink1" title="geda-gfdl.html">GNU Free Documentation License (GFDL)</a>.
+</p>
+
+</div>
+<!-- SECTION "gEDA/gaf Symbol Creation Document" [1-264] -->
+<h2><a name="overview" id="overview">Overview</a></h2>
+<div class="level2">
+
+<p>
+This document describes the creation of component symbols, including style conventions, and hints/tips and things to look out for when drawing symbols for the gEDA/gaf system.
+</p>
+
+</div>
+<!-- SECTION "Overview" [265-462] -->
+<h2><a name="component_symbol_creation" id="component_symbol_creation">Component symbol creation</a></h2>
+<div class="level2">
+
+<p>
+Component symbols (from here on known as â??symbolsâ??) are drawn using gschem just like drawing a schematic sheet. Here are the steps in a symbol in the gEDA/gaf system:<br/>
+ 1. Run gschem and find a blank page or run: gschem filename-1.sym<br/>
+ 2. Draw the symbol (see the style guide below for some conventions).<br/>
+ 3. Translate the symbol to the origin using Edit/Symbol Translate…<br/>
+
+</p>
+<ul>
+<li class="level1"><div class="li"> Zoom in at least one step.</div>
+</li>
+<li class="level1"><div class="li"> Make sure the snap is ON (this is critical).</div>
+</li>
+<li class="level1"><div class="li"> Make sure grid snap size is set to 100 (this is critical).</div>
+</li>
+<li class="level1"><div class="li"> Select â??Symbol Translate…â?? or the press equivalent hotkey.</div>
+</li>
+<li class="level1"><div class="li"> Enter 0 into the entry field and press OK.<br/>
+</div>
+</li>
+</ul>
+
+<p>
+Translating the symbol to the origin is a required step. To translate a symbol elsewhere, enter a offset (in mils) which is a even multiple of 100. Make sure all pins are snapped to a 100 mil grid point.
+</p>
+
+<p>
+4. Save the symbol using Save or SaveAs… Here are some symbol naming conventions:<br/>
+
+</p>
+<ul>
+<li class="level1"><div class="li"> Symbols are named: symbolname-#.sym</div>
+</li>
+<li class="level1"><div class="li"> Symbols end with a .sym extension.</div>
+</li>
+<li class="level1"><div class="li"> Symbols have a -# where # is a number. Typically # is 1 but if there are multiple symbols for a device then this number simply increments.</div>
+</li>
+<li class="level1"><div class="li"> Symbol names are typically lowercase but letters which are part of a part number are uppercase.</div>
+</li>
+<li class="level1"><div class="li"> The above case rule can be broken if the filename looks incorrect or wrong.</div>
+</li>
+</ul>
+
+<p>
+ 5. Place the symbol in one of the directories specified by the componentlibrary keyword in the system-gafrc file. Once this is done, the symbol should be visible immediately and can be selected and placed with the â??Add/Select Component…â?? menu item.
+</p>
+
+</div>
+<!-- SECTION "Component symbol creation" [463-2082] -->
+<h2><a name="requirements" id="requirements">Requirements</a></h2>
+<div class="level2">
+
+<p>
+This section describes the various requirements which must be met in order to create a valid symbol which will display and netlist in the gEDA/gaf system. Most of the requirements center around having certain attributes attached or inside the symbol.<br/>
+ Running gsymcheck will check that all of these requirements are met. gsymcheck will output fatal errors which are quite serious and must be corrected. gsymcheck will also output warnings on things which should be fixed but are not fatal.<br/>
+ For more information on the attributes presented here, please see the Master Attribute Document.
+</p>
+<ul>
+<li class="level1"><div class="li"> device=DEVICENAME should be placed somewhere in the symbol and made invisible. device= is the device name and is required. Typically the devicename is in all caps (capital letters). This attribute should not be used as a label. Use a separate text object for the label. If the object is a graphic then device= should be set to none (device=none). It is no longer required to attach this attribute anything; just having it exist as device=DEVICENAME is good enough.</div>
+</li>
+<li class="level1"><div class="li"> graphical=1 should exist somewhere in a symbol which is purely graphical (such as a title block or decon symbol). Symbols which have this attribute have no electrical or circuit significance. Donâ??t forget to set device=none.</div>
+</li>
+<li class="level1"><div class="li"> description=text should exist somewhere in the symbol. This attribute provides an one line description of the symbol.</div>
+</li>
+<li class="level1"><div class="li"> All pins should have a pair of attributes attached to them: pinseq=# and pinnumber=#. The first attribute, pinseq=# is just a sequence number and increments sequentially starting at 1. The second attribute pinnumber=# is the number of the pin. When a symbol is netlisted, the pin numbers are output in order of pin sequence. The pin number can be alphanumeric (i.e. like E or C).</div>
+</li>
+<li class="level1"><div class="li"> All pins should also have pinlabel=value attached to them. This attribute is the name or label of the pin (vs the pin number). This attribute is also used when a symbol is used in a hierarchical schematic. Please make this attribute green (instead of the default attribute yellow).</div>
+</li>
+<li class="level1"><div class="li"> All pins should also have pintype=value attached to them. This attribute describes the kind of a pin. Possible values are: in, out, io, oc, oe, pas, tp, tri, clk, pwr. Please see the Master Attribute Document for more info.</div>
+</li>
+<li class="level1"><div class="li"> If a component has multiple slots in a package (such as a 7400 (NAND) which has 4 NANDs per package) then you need a numslots=# attribute. The # is the number of slots the device has. numslots= should be exist somewhere in the symbol and made invisible. Additional slot related required attributes are described below.</div>
+</li>
+<li class="level1"><div class="li"> If a component has multiple slots in a physical package then you also need to include a slotdef=#:#,#,#… for every slot. The first # corresponds to the slot number. If a device has 4 slots then there should be slotdef=1:…, slotdef=2:…, slotdef=3:…, and slotdef=4:…, attributes existing somewhere in the symbol and made invisible. The subsequent # have a one-to-one correspondence to pinseq=# attributes and specify what corresponding pinnumber=# should be when that slot is set. See The attached 7400-1.sym as an example of how this should all work.</div>
+</li>
+<li class="level1"><div class="li"> It is recommended that all symbols which have slots have a slot=1 attribute inside the symbol.</div>
+</li>
+<li class="level1"><div class="li"> footprint=PACKAGENAME should exist somewhere in the symbol which might be used with the PCB netlister. PACKAGENAME is the PCB footprint or package type like DIP14 or DIP40. Please see the Footprint naming conventions chapter for further detail. See also the PCB documentation and gnetlist/docs/README.pcb for more info on this attribute.</div>
+</li>
+<li class="level1"><div class="li"> You should put a refdes=U? attribute inside the symbol. Make only the value visible and it will be promoted (attached to the outside of the symbol (so it can be edited) when the symbol is placed in a schematic.</div>
+</li>
+<li class="level1"><div class="li"> The label= attribute should not be attached anywhere in the symbol. It is obsolete.</div>
+</li>
+<li class="level1"><div class="li"> The name= attribute should not be attached anywhere in the symbol.</div>
+</li>
+<li class="level1"><div class="li"> The netname= attribute should not be attached anywhere in the symbol. It is only used in schematics.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Requirements" [2083-6223] -->
+<h2><a name="style" id="style">Style</a></h2>
+<div class="level2">
+
+<p>
+This section describes the style in which is used in the standard gEDA/gaf symbol library.
+</p>
+
+</div>
+<!-- SECTION "Style" [6224-6334] -->
+<h3><a name="text" id="text">Text</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> All Text labels should all be 10 pt in size.</div>
+</li>
+<li class="level1"><div class="li"> Text (labels not attributes) should be color number 9 (text | green).</div>
+</li>
+<li class="level1"><div class="li"> Use the special overbar encoding (e.g. â??pinlabel=\_Reset\_â??) to express inverse logic levels</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Text" [6335-6570] -->
+<h3><a name="attributes" id="attributes">Attributes</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> Pin numbers (which are attributes) should all be 8 pt in size.</div>
+</li>
+<li class="level1"><div class="li"> Attached attributes should be yellow. The color is set automatically to yellow if the text item is attached.</div>
+</li>
+<li class="level1"><div class="li"> The only exception to this is pinlabel= attributes, those should be color number 9 (text | green). If every text item within a symbol is yellow, the symbol looks too yellow.</div>
+</li>
+<li class="level1"><div class="li"> Attributes can be attached to some part of the symbol. Toplevel attributes (like the device= or net= attributes) used to be required to be attached to something to be attributes, but now they just have to exist in the symbol file as name=value.</div>
+</li>
+<li class="level1"><div class="li"> Expanding a bit on the last sentence, as long as the text item has the format name=value, it is considered an attribute. Attributes inside a symbol do not have to be attached to anything. In order to see hidden attributes in gschem select Edit/Show/Hide Inv Text.</div>
+</li>
+<li class="level1"><div class="li"> There is a symbol content versioning system in libgeda which is based on the symversion= attribute. Please see the Master Attribute Document for more information on using this versioning scheme.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Attributes" [6571-7667] -->
+<h3><a name="graphics" id="graphics">Graphics</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> Lines, boxes, arcs, and any other graphics should be color number 3 (graphic | green).</div>
+</li>
+<li class="level1"><div class="li"> Polarity bubbles should be color number 6 (logic bubble | cyan)</div>
+</li>
+<li class="level1"><div class="li"> If you are unsure on how to make a new symbol look or how big to make a new symbol, look at the existing symbols to get a feel for the appropriate appearance and size.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Graphics" [7668-8018] -->
+<h3><a name="pins" id="pins">Pins</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> Pins should all be 300 mils (3 grid spaces) long.</div>
+</li>
+<li class="level1"><div class="li"> For pins which are next to a logic bubble, make the pins 200 mils (2 grid spaces) long and then make the logic bubble 100 mils in diameter. In order to draw a 100 mil diameter circle, you will need to change the snap spacing to 50.</div>
+</li>
+<li class="level1"><div class="li"> A pin has two ends: one end has a red endpoint and one end that does not. The red endpoint is where nets can be connected. You can either rotate the pin so that this active end is in the right place or manually edit the symbol file changing the â??whichendâ?? parameter on the pin object. See the File Format document for more info.</div>
+</li>
+<li class="level1"><div class="li"> Be that all endpoints of pins which are meant to be connected to are on the 100 mil grid. The endpoint which is not active can be off the grid if necessary.</div>
+</li>
+<li class="level1"><div class="li"> Pins should be color number 1 (pins | white).</div>
+</li>
+<li class="level1"><div class="li"> Leave 400 mils (4 grid spaces) between (vertically) pins, unless you are drawing a special symbol, then just try to make it look good.</div>
+</li>
+<li class="level1"><div class="li"> Pin number attributes should be 50 mils above (or below; which ever makes the most sense) the pin which they are attached to.</div>
+</li>
+<li class="level1"><div class="li"> Input pins belong on the left and output pins belong on the right of the symbol.</div>
+</li>
+<li class="level1"><div class="li"> Please do not mix inputs and outputs on the same side of the symbol, unless absolutely necessary.</div>
+</li>
+<li class="level1"><div class="li"> You can have pins on the top or bottom of a symbol.</div>
+</li>
+<li class="level1"><div class="li"> The order for rows of pins (buses) should be LSB (least significant bit) to MSB (most significant bit). When drawing pins which are part of a bus, make sure the LSB of the bus is at the top (or for pins on top/bottom of a symbol, left of the rest of the other pins). Look at 74/74181-1.sym for a correct example of this order (A0 on top through A3 and B0 on top through B3). Violating this rule will make connecting buses much more diffcult.</div>
+</li>
+<li class="level1"><div class="li"> When placing pins on logic gates, be sure to place the smallest pin numbers toward the top (or left) and then increment going down (or across).</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Pins" [8019-9974] -->
+<h3><a name="electrical" id="electrical">Electrical</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> Do not draw power and ground pins. That information will be conveyed using attributes (see the netattrib document).</div>
+</li>
+<li class="level1"><div class="li"> The above rule can be broken if necessary, but keep in mind most of the standard library does not have power pins showing.</div>
+</li>
+<li class="level1"><div class="li"> Keep in mind, symbols are supposed to be symbolic, they do not represent the physical package that the device comes in.</div>
+</li>
+<li class="level1"><div class="li"> There is some disagreement on above, so this is okay too: Arrange the pins on a symbol logically so that they promote an uncluttered schematic. Note that this is frequently not the same pin arrangement as the physical device.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Electrical" [9975-10597] -->
+<h2><a name="footprint_naming_conventions" id="footprint_naming_conventions">Footprint naming conventions</a></h2>
+<div class="level2">
+
+<p>
+This section describes the conventions for naming of footprints used in gEDA/gaf.<br/>
+ The purpose of the naming convention is to establish a standard to maintain the same naming convention through the different phases of the CAD chain. This helps in ensuring that the collaborative effort of gEDA/gaf is not lost.
+</p>
+
+</div>
+<!-- SECTION "Footprint naming conventions" [10598-10951] -->
+<h3><a name="notes" id="notes">Notes</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> Unless otherwise noted, numerical pin names will be used, starting from 1.</div>
+</li>
+<li class="level1"><div class="li"> n is for the pin count.</div>
+</li>
+<li class="level1"><div class="li"> m is for the pin spacing in mils.</div>
+</li>
+<li class="level1"><div class="li"> x is for the x dimension of the package (excluding pins). In particular this is used for the QFP package family.</div>
+</li>
+<li class="level1"><div class="li"> SMT means surface mount, other components are through-hole.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Notes" [10952-11294] -->
+<h3><a name="integrated_circuit_packages" id="integrated_circuit_packages">Integrated circuit packages</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> Dual in line packages with up to 22 100 mil spaced pins and 300 mil row spacing are called DIPn.</div>
+</li>
+<li class="level1"><div class="li"> Dual in line packages with 24 or more 100 mil spaced pins and 300 mil row spacing are called DIPnN.</div>
+</li>
+<li class="level1"><div class="li"> Dual in line packages with 100 mil spaced pins and 400 mil row spacing are called DIPnH.</div>
+</li>
+<li class="level1"><div class="li"> Dual in line packages with 24 or more 100 mil spaced pins and 600 mil row spacing are called DIPn.</div>
+</li>
+<li class="level1"><div class="li"> Shrink dual in line packages with up to 24 70 mil spaced pins and 300 mil row spacing are called SDIPn.</div>
+</li>
+<li class="level1"><div class="li"> Shrink dual in line packages with more than 24 70 mil spaced pins and 400 mil row spacing are called SDIPn.</div>
+</li>
+<li class="level1"><div class="li"> Single in line packages with 100 mil spaced pins are called SIPnN. See also JUMPER, below.</div>
+</li>
+<li class="level1"><div class="li"> Zig-zag in-line package are called ZIPn.</div>
+</li>
+<li class="level1"><div class="li"> Plastic leadless chip carrier with pin socket are called PLCCnX.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Integrated circuit packages" [11295-12163] -->
+<h3><a name="integrated_circuit_smt_packages" id="integrated_circuit_smt_packages">Integrated circuit SMT packages</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> Small outline SMT packages with up to 16 50 mil spaced pins and 150 mil total width are called SOn.</div>
+</li>
+<li class="level1"><div class="li"> Small outline SMT packages with more than 16 50 mil spaced pins and 150 mil total width are called SOnN.</div>
+</li>
+<li class="level1"><div class="li"> Small outline SMT packages with 50 mil spaced pins and 200 mil total width are called SOnM.</div>
+</li>
+<li class="level1"><div class="li"> Small outline SMT packages with up to 20 50 mil spaced pins and 300 mil total width are called SOnW.</div>
+</li>
+<li class="level1"><div class="li"> Small outline SMT packages with more than 20 50 mil spaced pins and 300 mil total width are called SOn.</div>
+</li>
+<li class="level1"><div class="li"> Small outline SMT packages with 44 or more 50 mil spaced pins and 525 mil total width are called SOn.</div>
+</li>
+<li class="level1"><div class="li"> Metric shrink small outline SMT packages with 0.65 mm spaced pins and 323 mil total width are called MSSOPn. NOTE: To be confirmed.</div>
+</li>
+<li class="level1"><div class="li"> Metric shrink small outline SMT packages with up to 44 0.65 mm spaced pins and 420 mil total width are called MSSOPnW.</div>
+</li>
+<li class="level1"><div class="li"> Metric shrink small outline SMT packages with over 44 0.65 mm spaced pins and 545 mil total width are called MSSOPnW.</div>
+</li>
+<li class="level1"><div class="li"> Shrink small outline SMT packages with 25 mil spaced pins and 420 mil total width are called SSOPnW.</div>
+</li>
+<li class="level1"><div class="li"> Quarter size small outline SMT packages with 25 mil spaced pins and 244 mil total width are called SSOPn.</div>
+</li>
+<li class="level1"><div class="li"> Thin small outline SMT packages with 21.65 mil spaced pins and 535 mil total width are called TSOPn.</div>
+</li>
+<li class="level1"><div class="li"> Thin small outline SMT packages with 20 mil spaced pins and 795 mil total width are called TSOPnA.</div>
+</li>
+<li class="level1"><div class="li"> Thin small outline SMT packages with 20 mil spaced pins and 559 mil total width are called TSOPnB.</div>
+</li>
+<li class="level1"><div class="li"> Thin shrink small outline SMT packages with up to 28 26 mil spaced pins and 260 mil total width are called TSSOPn.</div>
+</li>
+<li class="level1"><div class="li"> Thin shrink small outline SMT packages with over 28 20 mil spaced pins and 319 mil total width are called TSSOPn.</div>
+</li>
+<li class="level1"><div class="li"> Ultra Super Mini SMT packages with up to 16 0.5 mm spaced pins are called USn.</div>
+</li>
+<li class="level1"><div class="li"> Plastic leadless chip carrier SMT are called PLCCn.</div>
+</li>
+<li class="level1"><div class="li"> Square quad-side at pack SMT are called QFPn x.</div>
+</li>
+<li class="level1"><div class="li"> Rectangular quad-side at pack SMT are called QFPn R.</div>
+</li>
+<li class="level1"><div class="li"> Square low profile quad-side at pack SMT are called LQFPn x.</div>
+</li>
+<li class="level1"><div class="li"> Square thin quad-side at pack SMT are called TQFPn x.</div>
+</li>
+<li class="level1"><div class="li"> Square Quad-side at no-lead SMT without exposed paddle (back side contact) are called QFNn x. Pin count is n and package size is x mm.</div>
+</li>
+<li class="level1"><div class="li"> Square Quad-side at no-lead SMT with exposed paddle (back side contact) are called QFNn x EP. Pin count is n and package size is x mm.</div>
+</li>
+<li class="level1"><div class="li"> Thin profile square Quad-side at no-lead SMT without exposed paddle (back side contact) are called TQFNn x. Pin count is n and package size is x mm.</div>
+</li>
+<li class="level1"><div class="li"> Thin profile square Quad-side at no-lead SMT with exposed paddle (back side contact) are called TQFNn x EP. Pin count is n and package size is x mm.</div>
+</li>
+<li class="level1"><div class="li"> Dual in line style crystal oscillators are OSC8 and OSC14.</div>
+</li>
+<li class="level1"><div class="li"> 5 pin SOT SMT packages are SOT25 and SOT325.</div>
+</li>
+<li class="level1"><div class="li"> 6 pin SOT SMT packages are SOT26 and SOT326.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Integrated circuit SMT packages" [12164-15094] -->
+<h3><a name="basic_semiconductors" id="basic_semiconductors">Basic semiconductors</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> Axial diodes are called ALFm. Pin 1 is the cathode.</div>
+</li>
+<li class="level1"><div class="li"> Conventional through hole LED is LED3 and LED5 for 3 and 5 mm respectively. Pin 1 is plus. NOTE: Should probably be changed to be in line with diode convention.</div>
+</li>
+<li class="level1"><div class="li"> TO transistors are TO5, TO92, TO126, TO220 etc. Suxes may apply, e.g. TO126W is for wide, TO126S is for standing, TO126SW is for standing, wide.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Basic semiconductors" [15095-15497] -->
+<h3><a name="basic_smt_semiconductors" id="basic_smt_semiconductors">Basic SMT semiconductors</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> SOD diode SMT packages use their standard package name, e.g. SOD80, SOD87, SOD106A, SOD110. There are also SOD123, SOD323 with narrow pads.</div>
+</li>
+<li class="level1"><div class="li"> SOT transistor SMT packages use their standard package name, e.g. SOT23, SOT323. There is also an SC90.</div>
+</li>
+<li class="level1"><div class="li"> SOT transistor SMT packages with numbering as for diodes (pin 1 is cathode, pin 2 anode) are SOT23D, SOT323D.</div>
+</li>
+<li class="level1"><div class="li"> 4 pin SOT SMT packages are SOT89, SOT143, SOT223.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Basic SMT semiconductors" [15498-15953] -->
+<h3><a name="passive_components" id="passive_components">Passive components</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> Axial non-polar components (typically resistor, capacitor) are called ACYm.</div>
+</li>
+<li class="level1"><div class="li"> Bottom lead (radial) non-polar circular component (typically capacitor) is RCYm.</div>
+</li>
+<li class="level1"><div class="li"> Bottom lead non-polar rectangular component (typically capacitor) is BREm.</div>
+</li>
+<li class="level1"><div class="li"> A standard crystal is HC49, or other HC designations as required.</div>
+</li>
+<li class="level1"><div class="li"> Single row 100 mil pin spacing jumpers are JUMPERn. The main difference compared to single in line package is the hole size.</div>
+</li>
+<li class="level1"><div class="li"> Dual row 100 mil spacing headers with DIP pin numbering are HEADERn 1. Note that n is an even number.</div>
+</li>
+<li class="level1"><div class="li"> Dual row 100 mil spacing headers with ribbon cable numbering are HEADERn 2. Note that n is an even number.</div>
+</li>
+<li class="level1"><div class="li"> Angled full header connectors with latches are DIN41651 n.</div>
+</li>
+<li class="level1"><div class="li"> Standing full header connectors with latches are DIN41651 nS.</div>
+</li>
+<li class="level1"><div class="li"> DSUB connectors female are DBnF.</div>
+</li>
+<li class="level1"><div class="li"> DSUB connectors male are DBnM.</div>
+</li>
+<li class="level1"><div class="li"> Female DIN card-to-card connectors are DIN41612CnF. Add S suffix for standing.</div>
+</li>
+<li class="level1"><div class="li"> Male DIN card-to-card connectors are DIN41612CnM. Add S suffix for standing.</div>
+</li>
+<li class="level1"><div class="li"> AMP modular RJ connectors with screen are RJ11, RJ12 and RJ45.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Passive components" [15954-17075] -->
+<h3><a name="passive_smt_components" id="passive_smt_components">Passive SMT components</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> Standard SMT resistors, inductors, capacitors etc are 0201, 0402, 0603, 0805, 1206, 1210, 1806, 1812, 1825, 2020, 2706.</div>
+</li>
+<li class="level1"><div class="li"> Tantalum SMT capacitors are EIA3216, EIA3528, EIA6032, and EIA7343. Pin 1 is plus.</div>
+</li>
+<li class="level1"><div class="li"> SMT electrolytics are designated by can diameter in 1/10 mm: SME33, SME43, SME53, SME66, SME84, SME104.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Passive SMT components" [17076-17428] -->
+<h2><a name="hints_and_tips" id="hints_and_tips">Hints and Tips</a></h2>
+<div class="level2">
+
+<p>
+This section describes some hints and tips which will make your symbol creation experience easier.<br/>
+
+</p>
+<ul>
+<li class="level1"><div class="li"> Avoid drawing things off of the grid. If you do, you cannot move the object(s) using the move command (if the grid is on) since the object will be snapped to the grid. [This was an old bug, which I think has been fixed, but avoid doing this anyway]. Use the symbol translate command instead (or move the object with grid snap off)</div>
+</li>
+<li class="level1"><div class="li"> If you need a finer grid then use Options/Snap Grid Spacing… to set a finer grid snap spacing. Just remember to set this back to 100 once you are ready to translate the symbol to the origin.</div>
+</li>
+<li class="level1"><div class="li"> If you want to translate a symbol from the origin to elsewhere, then use the â??Symbol translateâ?? command and enter a non zero number. Make sure this number is a multiple of 100 (ie 1000, or 1100).</div>
+</li>
+<li class="level1"><div class="li"> Pins MUST be snapped on the 100 spaced grid (at least the end which will have nets connected to it).</div>
+</li>
+<li class="level1"><div class="li"> Pins MUST be snapped on the 100 spaced grid (at least the end which will have nets connected to it). Yes this is line a duplicate. I canâ??t stress this point enough.</div>
+</li>
+<li class="level1"><div class="li"> Remember that pins are special objects; if you want to add a pin, make sure it is a pin and not a line or net. Use the Add/Pin command to place a pin.</div>
+</li>
+<li class="level1"><div class="li"> Donâ??t include nets or buses inside symbols. That is not supported and doesnâ??t make much sense anyway.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Hints and Tips" [17429-18824] -->
+<h2><a name="example" id="example">Example</a></h2>
+<div class="level2">
+
+<p>
+This section provides a simple example which tries to follow all of the above rules. This symbol is of a 7400 (NAND gate).<br/>
+
+</p>
+
+<p>
+<pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">v 20031231 1
+L 300 200 300 800 3 0 0 0 -1 -1
+T 300 0 9 8 1 0 0 0 1
+7400
+L 300 800 700 800 3 0 0 0 -1 -1
+T 500 900 5 10 0 0 0 0 1
+device=7400
+T 500 1100 5 10 0 0 0 0 1
+slot=1
+T 500 1300 5 10 0 0 0 0 1
+numslots=4
+T 500 1500 5 10 0 0 0 0 1
+slotdef=1:1,2,3
+T 500 1700 5 10 0 0 0 0 1
+slotdef=2:4,5,6
+T 500 1900 5 10 0 0 0 0 1
+slotdef=3:9,10,8
+T 500 2100 5 10 0 0 0 0 1
+slotdef=4:12,13,11
+L 300 200 700 200 3 0 0 0 -1 -1
+A 700 500 300 270 180 3 0 0 0 -1 -1
+V 1050 500 50 6 0 0 0 -1 -1 0 -1 -1 -1 -1 -1
+P 1100 500 1300 500 1 0 1
+{
+T 1100 550 5 8 1 1 0 0 1
+pinnumber=3
+T 1100 450 5 8 0 1 0 2 1
+pinseq=3
+T 950 500 9 8 0 1 0 6 1
+pinlabel=Y
+T 950 500 5 8 0 1 0 8 1
+pintype=out
+}
+P 300 300 0 300 1 0 1
+{
+T 200 350 5 8 1 1 0 6 1
+pinnumber=2
+T 200 250 5 8 0 1 0 8 1
+pinseq=2
+T 350 300 9 8 0 1 0 0 1
+pinlabel=B
+T 350 300 5 8 0 1 0 2 1
+pintype=in
+}
+P 300 700 0 700 1 0 1
+{
+T 200 750 5 8 1 1 0 6 1
+pinnumber=1
+T 200 650 5 8 0 1 0 8 1
+pinseq=1
+T 350 700 9 8 0 1 0 0 1
+pinlabel=A
+T 350 700 5 8 0 1 0 2 1
+pintype=in
+}
+T 300 900 8 10 1 1 0 0 1
+refdes=U?
+T 500 2250 5 10 0 0 0 0 1
+footprint=DIP14
+T 500 2450 5 10 0 0 0 0 1
+description=4 NAND gates with 2 inputs
+T 500 2850 5 10 0 0 0 0 1
+net=Vcc:14
+T 500 3050 5 10 0 0 0 0 1
+net=GND:7
+T 500 2650 5 10 0 0 0 0 1
+documentation=http://www-s.ti.com/sc/ds/sn74hc00.pdf
+</font></pre>
+</p>
+
+<p>
+This example produces the following (using gschem):
+</p>
+
+<p>
+<a href="media/geda/symbol_7400-1_hidden.png" class="media" target="_blank" title="geda:symbol_7400-1_hidden.png"><img src="media/geda/symbol_7400-1_hidden.png" class="media" title=":geda:symbol_7400-1_hidden.png" alt=":geda:symbol_7400-1_hidden.png" /></a>
+</p>
+
+<p>
+This is the same symbol with all the hidden text visible (via Edit/Show/Hide Inv Text):
+</p>
+
+<p>
+<a href="media/geda/symbol_7400-1.png" class="media" target="_blank" title="geda:symbol_7400-1.png"><img src="media/geda/symbol_7400-1.png" class="media" title=":geda:symbol_7400-1.png" alt=":geda:symbol_7400-1.png" /></a>
+</p>
+
+</div>
+<!-- SECTION "Example" [18825-20541] -->
+<h2><a name="document_revision_history" id="document_revision_history">Document Revision History</a></h2>
+<div class="level2">
+<table class="inline">
+ <tr>
+ <td> September 14th, 2002</td><td>Created symbol.tex from symbols.html </td>
+ </tr>
+ <tr>
+ <td> October 31st, 2002</td><td>Fixed bad example symbol </td>
+ </tr>
+ <tr>
+ <td> February 11th, 2003</td><td>Footprint naming conventions added </td>
+ </tr>
+ <tr>
+ <td> September 27th, 2003</td><td>Applied Dan McMahillâ??s QFP and QFN patch </td>
+ </tr>
+ <tr>
+ <td> July 6th, 2004</td><td>Added a bunch more details/hints to the pin section </td>
+ </tr>
+</table>
+
+</div>
+<!-- SECTION "Document Revision History" [20542-] --></body>
+</html>
diff --git a/docs/wiki/geda-scm.html b/docs/wiki/geda-scm.html
new file mode 100644
index 0000000..840db3e
--- /dev/null
+++ b/docs/wiki/geda-scm.html
@@ -0,0 +1,525 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#geda_gaf_s_source_control_management" class="toc">gEDA/gaf's Source Control Management</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#installing_git_related_tools" class="toc">Installing git & related tools</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#learning_to_use_git" class="toc">Learning to use git</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#accessing_the_repository_anonymously" class="toc">Accessing the repository anonymously</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#accessing_the_repository_with_write_permission" class="toc">Accessing the repository with write permission</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#accessing_the_repository_using_anonymous_cvs" class="toc">Accessing the repository using anonymous CVS</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#making_and_committing_changes" class="toc">Making and committing changes</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#setting_up_user_information" class="toc">Setting up user information</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#committing_patches_from_other_contributors" class="toc">Committing patches from other contributors</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#writing_good_commit_message" class="toc">Writing good commit message</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#push_is_destructive" class="toc">Push is Destructive</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_do_i" class="toc">How Do I ... ?</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#get_a_copy_of_geda_gaf_git_repository" class="toc">... get a copy of gEDA/gaf git repository?</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#keep_my_local_copy_current" class="toc">... keep my local copy current?</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#commit_my_changes_to_the_local_git_repository" class="toc">... commit my changes to the local git repository?</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#undo_any_uncommitted_local_changes" class="toc">... undo any uncommitted local changes?</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#fix_change_my_last_commit" class="toc">... fix/change my last commit?</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#track_a_branch" class="toc">... track a branch?</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#create_a_branch_starting_at_a_tag" class="toc">... create a branch (starting at a tag)?</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#fetch_a_development_branch_from_other_people" class="toc">... fetch a development branch from other people?</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#format_a_patch_to_send_to_the_developers" class="toc">... format a patch to send to the developers?</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#recover_from_a_really_messed_up_local_repository" class="toc">... recover from a really messed up local repository?</a></span></div></li></ul>
+</li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="geda_gaf_s_source_control_management" id="geda_gaf_s_source_control_management">gEDA/gaf's Source Control Management</a></h1>
+<div class="level1">
+
+<p>
+ gEDA uses <strong>git</strong> for source code management. git is a distributed version control system, where every user has his or her own full copy of the revision history.
+</p>
+<ul>
+<li class="level1"><div class="li"> <a href="http://git.or.cz/"; class="urlextern" title="http://git.or.cz/"; rel="nofollow">Official git website</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="http://www.kernel.org/pub/software/scm/git/docs/"; class="urlextern" title="http://www.kernel.org/pub/software/scm/git/docs/"; rel="nofollow">git documentation online</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="http://en.wikipedia.org/wiki/Git_(software)" class="urlextern" title="http://en.wikipedia.org/wiki/Git_(software)" rel="nofollow">git Wikipedia page</a></div>
+</li>
+</ul>
+
+<p>
+ The web interface to the gEDA git repository is at <a href="http://git.gpleda.org/"; class="urlextern" title="http://git.gpleda.org/"; rel="nofollow">http://git.gpleda.org/</a>.
+</p>
+
+</div>
+<!-- SECTION "gEDA/gaf's Source Control Management" [1-494] -->
+<h2><a name="installing_git_related_tools" id="installing_git_related_tools">Installing git & related tools</a></h2>
+<div class="level2">
+
+<p>
+ The core git tools are of course required for using the repository, and the documentation is always useful. However, other tools are often helpful for working with git:
+</p>
+<ul>
+<li class="level1"><div class="li"> <a href="http://www.kernel.org/pub/software/scm/git/docs/gitk.html"; class="urlextern" title="http://www.kernel.org/pub/software/scm/git/docs/gitk.html"; rel="nofollow">gitk</a>, a visual history repository browser</div>
+</li>
+<li class="level1"><div class="li"> <a href="http://www.procode.org/stgit/"; class="urlextern" title="http://www.procode.org/stgit/"; rel="nofollow">Stacked Git</a>, for working with patchsets</div>
+</li>
+</ul>
+
+<p>
+ Make sure that you install at least version 1.5.x of git if you are planning on pushing changes to the central git repository.
+</p>
+
+<p>
+Debian-based
+</p>
+<pre class="code">apt-get install git-core git-doc gitk stgit</pre>
+
+<p>
+ you may also want:
+</p>
+<pre class="code">apt-get install git-email git-completion</pre>
+
+<p>
+ Note, as of 2007/06/25, Debian stable (etch) and Debian testing (lenny) have git version 1.4.x. Debian unstable (sid) has 1.5.2.2.
+</p>
+
+<p>
+ Fedora Linux
+</p>
+<pre class="code">yum install git stgit </pre>
+
+</div>
+<!-- SECTION "Installing git & related tools" [495-1330] -->
+<h2><a name="learning_to_use_git" id="learning_to_use_git">Learning to use git</a></h2>
+<div class="level2">
+
+<p>
+ The toplevel documentation for git can be found at:
+</p>
+
+<p>
+<a href="http://www.kernel.org/pub/software/scm/git/docs/"; class="urlextern" title="http://www.kernel.org/pub/software/scm/git/docs/"; rel="nofollow">Official git docs</a>
+</p>
+
+<p>
+The userâ??s manual for git can be found at:
+</p>
+
+<p>
+<a href="http://www.kernel.org/pub/software/scm/git/docs/user-manual.html"; class="urlextern" title="http://www.kernel.org/pub/software/scm/git/docs/user-manual.html"; rel="nofollow">git user manual</a>
+</p>
+
+<p>
+A current tutorial can be found at:
+</p>
+
+<p>
+<a href="http://www.kernel.org/pub/software/scm/git/docs/gitcore-tutorial.html"; class="urlextern" title="http://www.kernel.org/pub/software/scm/git/docs/gitcore-tutorial.html"; rel="nofollow">git core tutorial</a>
+</p>
+
+<p>
+Other nice tutorials/webpages:
+</p>
+
+<p>
+<a href="http://wiki.sourcemage.org/Git_Guide"; class="urlextern" title="http://wiki.sourcemage.org/Git_Guide"; rel="nofollow">Git Guide</a><br/>
+ <a href="http://git.or.cz/course/index.html"; class="urlextern" title="http://git.or.cz/course/index.html"; rel="nofollow">git Crash Courses</a><br/>
+
+</p>
+
+<p>
+Keep in mind that some of these tutorials are a little dated and may not cover current git syntax.
+</p>
+
+</div>
+<!-- SECTION "Learning to use git" [1331-2001] -->
+<h2><a name="accessing_the_repository_anonymously" id="accessing_the_repository_anonymously">Accessing the repository anonymously</a></h2>
+<div class="level2">
+
+<p>
+ To clone the gaf.git repository (or any repository hosted at <a href="http://git.gpleda.org"; class="urlextern" title="http://git.gpleda.org"; rel="nofollow">git.gpleda.org</a>) using anonymous git access:
+</p>
+<pre class="code">git clone git://git.gpleda.org/gaf.git</pre>
+
+<p>
+ or
+</p>
+<pre class="code">git clone git://git.gpleda.org/pcb.git</pre>
+
+<p>
+ For different repositories hosted at git.gpleda.org, just substitute the last part of the above <acronym title="Uniform Resource Locator">URL</acronym>.
+</p>
+
+</div>
+<!-- SECTION "Accessing the repository anonymously" [2002-2374] -->
+<h2><a name="accessing_the_repository_with_write_permission" id="accessing_the_repository_with_write_permission">Accessing the repository with write permission</a></h2>
+<div class="level2">
+
+<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>
+
+<p>
+or
+</p>
+<pre class="code">git clone ssh://<username>@git.gpleda.org/home/git/pcb.git</pre>
+
+<p>
+ If you have ssh access you will also need to edit your ~/.ssh/config file (create it if it doesnâ??t exist) and put the following text into it:
+</p>
+<pre class="code">Host git.gpleda.org
+Port 5022</pre>
+
+</div>
+<!-- SECTION "Accessing the repository with write permission" [2375-2891] -->
+<h2><a name="accessing_the_repository_using_anonymous_cvs" id="accessing_the_repository_using_anonymous_cvs">Accessing the repository using anonymous CVS</a></h2>
+<div class="level2">
+
+<p>
+ Finally, it is possible to access the repository using <acronym title="Concurrent Versions System">CVS</acronym>, as there is a git-cvsserver running. This is read-only access.
+</p>
+<pre class="code"> export CVSROOT=:pserver:anonymous@xxxxxxxxxxxxxx/home/git/gaf.git
+ cvs co master </pre>
+
+<p>
+ You can only checkout exported heads (for example: master).
+</p>
+
+</div>
+<!-- SECTION "Accessing the repository using anonymous CVS" [2892-3226] -->
+<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" [3227-3271] -->
+<h3><a name="setting_up_user_information" id="setting_up_user_information">Setting up user information</a></h3>
+<div class="level3">
+
+<p>
+ You should make sure that your username & e-mail address are set in your git configuration file.
+</p>
+<pre class="code">$ git config --global user.name "Your Name Comes Here"
+$ git config --global user.email you@xxxxxxxxxxxxxxxxxxxxxx</pre>
+
+</div>
+<!-- SECTION "Setting up user information" [3272-3530] -->
+<h3><a name="committing_patches_from_other_contributors" id="committing_patches_from_other_contributors">Committing patches from other contributors</a></h3>
+<div class="level3">
+
+<p>
+ If you apply a patch from someone else (e.g. from a SourceForge patch record) there are a few things to consider. Git stores two different names and e-mail addresses for a given commit: the â??authorâ?? of the patch, and the â??committerâ?? of the patch, so these details must be set correctly when making the commit.
+</p>
+
+<p>
+First of all, check a few things:
+</p>
+<ul>
+<li class="level1"><div class="li"> You have the latest version of the patch.</div>
+</li>
+<li class="level1"><div class="li"> The author of the patch is happy for it to be committed (and wasnâ??t still working on it)</div>
+</li>
+<li class="level1"><div class="li"> That the youâ??re happy with the patch, and taking responsibility for committing those changes.</div>
+</li>
+</ul>
+
+<p>
+ For simplicity, start from an unmodified up-to date tree (git status shows no changes).
+</p>
+
+<p>
+Apply the patch as usual (as an example):
+</p>
+<pre class="code">$ patch -p1 < example_changes.patch</pre>
+
+<p>
+ You can also use the git apply command:
+</p>
+<pre class="code">$ git apply example_changes.patch</pre>
+
+<p>
+ If the patch needs any minor editing before it is committed (eg. white-space changes), please inform the author this was done. They may have other work based on their patch and will want to know if there were changes to the applied version.
+</p>
+
+<p>
+Note: <em>This is easy to miss accidentally if your editor introduces tabs. Please avoid letting it do so!</em>
+</p>
+
+<p>
+For every file changed, added or removed, you need to inform git before it will commit the changes. To see the modified files, run:
+</p>
+<pre class="code">$ git status</pre>
+
+<p>
+ For speed, the command:
+</p>
+<pre class="code">$ git add -u</pre>
+
+<p>
+ will update all files which git tracks, including any files which were deleted.
+</p>
+
+<p>
+For adding any new files the patch introduced, use the command
+</p>
+<pre class="code">$ git add new_file.c</pre>
+
+<p>
+ Note: git add also takes wild-cards.
+</p>
+
+<p>
+Commit the patch, making sure that the Authorâ??s name and e-mail address are specified:
+</p>
+<pre class="code">$ git commit --author "Author's Name Comes Here <author@xxxxxxxxxxx>"</pre>
+
+<p>
+ As an alternative, you can set the GIT_AUTHOR_NAME and GIT_AUTHOR_EMAIL environment variables before issuing the normal commit command
+</p>
+
+</div>
+<!-- SECTION "Committing patches from other contributors" [3531-5461] -->
+<h3><a name="writing_good_commit_message" id="writing_good_commit_message">Writing good commit message</a></h3>
+<div class="level3">
+
+<p>
+The commit message format is as follows: a *strictly* one-line summary of the patch, followed by a blank line, followed by a long description. If you can fit the whole description of the patch on one line, thatâ??s fine; donâ??t bother with the long description.
+</p>
+
+<p>
+The one-line summary is used for generating e-mail subject lines, and for the gitk & gitweb log displays. Having a good one-line summary is really useful, because it means those tools can be used to quickly find a commit of interest.
+</p>
+
+<p>
+<strong>Do not</strong> put a list of files changed into commit messages. This information can be trivially obtained using the git tools.
+</p>
+
+<p>
+Example:
+</p>
+<pre class="code">
+Added new GedaList class derived from GObject
+
+This abstracts a GList with API for write access. Its main use is in list
+change notification, as it emits a "changed" g_signal when modified.
+Read only access to the underlying GList is provided by an accessor,
+currenly implemented as a macro.
+</pre>
+
+</div>
+<!-- SECTION "Writing good commit message" [5462-6443] -->
+<h3><a name="push_is_destructive" id="push_is_destructive">Push is Destructive</a></h3>
+<div class="level3">
+
+<p>
+ <strong>Warning: pushing changes to the remote repository is destructive</strong>
+</p>
+
+<p>
+Unlike <acronym title="Concurrent Versions System">CVS</acronym>, it is not the committing of changes which changes the master repository, but pushing changes using git-push. You should always double- (or triple-) check that the commits you are about to push are actually meant for the main repository.
+</p>
+
+</div>
+<!-- SECTION "Push is Destructive" [6444-6797] -->
+<h2><a name="how_do_i" id="how_do_i">How Do I ... ?</a></h2>
+<div class="level2">
+
+<p>
+ For a more information please checkout the <a href="http://wiki.sourcemage.org/Git_Guide"; class="urlextern" title="http://wiki.sourcemage.org/Git_Guide"; rel="nofollow">Git Guide</a>.
+</p>
+
+</div>
+<!-- SECTION "How Do I ... ?" [6798-6921] -->
+<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">
+
+<p>
+ For anonymous read-only access:
+</p>
+<pre class="code">$ git clone git://git.gpleda.org/gaf</pre>
+
+<p>
+ For developers with read/write access:
+</p>
+<pre class="code">$ git clone git://git.gpleda.org/home/git/gaf.git</pre>
+
+</div>
+<!-- SECTION "... get a copy of gEDA/gaf git repository?" [6922-7141] -->
+<h3><a name="keep_my_local_copy_current" id="keep_my_local_copy_current">... keep my local copy current?</a></h3>
+<div class="level3">
+
+<p>
+ For those who are are not merging changes back into the central git repository you can run:
+</p>
+<pre class="code">$ git pull</pre>
+
+<p>
+ However, for those of you who are going to be pushing your changes back into the central git repository, using git pull will clutter up the history with merge messages (â??Merge branch â??masterâ??â??). To avoid this you should run:
+</p>
+<pre class="code">$ git fetch
+$ git rebase origin</pre>
+
+</div>
+<!-- SECTION "... keep my local copy current?" [7142-7556] -->
+<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>
+
+<p>
+ This command will find all changed files that git knows about (added with git-add) and prompt you for a commit message. Be sure to follow the above commit message convention if you plan on pushing your changes to the central repository.
+</p>
+
+<p>
+If you want to commit files in the current directory or want to explicitly commit only certain files, do not specify the -a flag and/or specify the individual filenames on the command line like:
+</p>
+<pre class="code">$ git commit filename1 filename2</pre>
+
+</div>
+<!-- SECTION "... commit my changes to the local git repository?" [7557-8112] -->
+<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>
+
+<p>
+ Note this will discard any changes to any files that are being tracked by git.
+</p>
+
+<p>
+If you want to just discard edits in a single file, just run:
+</p>
+<pre class="code">$ git checkout path/to/file/to/discard</pre>
+
+<p>
+ If you want to discard all edits from the current directory and downward recursively, just run:
+</p>
+<pre class="code">$ git checkout .</pre>
+
+</div>
+<!-- SECTION "... undo any uncommitted local changes?" [8113-8489] -->
+<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
+$ git commit --amend filename1..filenameN </pre>
+
+<p>
+ This will pickup any changes you made and recommit them again with the previous commit message.
+</p>
+
+</div>
+<!-- SECTION "... fix/change my last commit?" [8490-8698] -->
+<h3><a name="track_a_branch" id="track_a_branch">... track a branch?</a></h3>
+<div class="level3">
+<pre class="code">$ git checkout --track -b <local name> origin/<remote name></pre>
+
+<p>
+ This will create a branch with the <local name> which tracks the <remote name>â??d branch.
+</p>
+
+</div>
+<!-- SECTION "... track a branch?" [8699-8882] -->
+<h3><a name="create_a_branch_starting_at_a_tag" id="create_a_branch_starting_at_a_tag">... create a branch (starting at a tag)?</a></h3>
+<div class="level3">
+
+<p>
+ Run the following commands (using the stable-1.4 branch as an example):
+</p>
+<pre class="code"> $ git branch stable-1.4 1.4.0-20080127
+ $ git checkout stable-1.4
+ <make changes>
+ $ git commit -a </pre>
+
+<p>
+ To publish this branch in the central repository (requires write access to the central repository):
+</p>
+<pre class="code"> $ git push origin stable-1.4</pre>
+
+</div>
+<!-- SECTION "... create a branch (starting at a tag)?" [8883-9251] -->
+<h3><a name="fetch_a_development_branch_from_other_people" id="fetch_a_development_branch_from_other_people">... fetch a development branch from other people?</a></h3>
+<div class="level3">
+
+<p>
+Beside the <a href="http://git.gpleda.org/"; class="urlextern" title="http://git.gpleda.org/"; rel="nofollow">http://git.gpleda.org/</a> repository we have a mirror of that repository at <a href="http://repo.or.cz/w/geda-gaf.git"; class="urlextern" title="http://repo.or.cz/w/geda-gaf.git"; rel="nofollow">http://repo.or.cz/w/geda-gaf.git</a>. Some of the developers have forks of that repository with new feature branches.
+</p>
+
+<p>
+If you like to test one of the feature branches you have to fetch it from their repository. The easiest way to get a branch is to use the fetch command.
+</p>
+<pre class="code"> $ git fetch repository_url remote_branchname:local_branchname</pre>
+
+<p>
+ <strong>Examples:</strong> Getting the <em>cairo_experiment</em> branch from Peter C. would look like this:
+</p>
+<pre class="code"> $ git fetch git://repo.or.cz/geda-gaf/pcjc2.git cairo_experiment:peters_cairo_experiment</pre>
+
+<p>
+ Now you can switch to the local copy of the branch <em>peters_cairo_experiment</em> and play with it.
+</p>
+
+</div>
+<!-- SECTION "... fetch a development branch from other people?" [9252-10024] -->
+<h3><a name="format_a_patch_to_send_to_the_developers" id="format_a_patch_to_send_to_the_developers">... format a patch to send to the developers?</a></h3>
+<div class="level3">
+
+<p>
+The simplest possible way:
+</p>
+<pre class="code">$ git diff > name_of_patchfile</pre>
+
+<p>
+ A more complicated way:
+</p>
+<pre class="code">$ git add -i # select files to be committed
+$ git status # check you're committing what you think you're committing
+$ git commit # create a commit
+$ git format-patch -1 # create a patch file based on that commit</pre>
+
+<p>
+This will output a filename which contains the patch. Be sure to look at the documentation for format-patch for more information. This file can be e-mailed to developers who have write access and can be applied using git apply.
+</p>
+
+</div>
+<!-- SECTION "... format a patch to send to the developers?" [10025-10646] -->
+<h3><a name="recover_from_a_really_messed_up_local_repository" id="recover_from_a_really_messed_up_local_repository">... recover from a really messed up local repository?</a></h3>
+<div class="level3">
+
+<p>
+ First off, do not push any repository that you think is somehow messed up. Ask one of the experienced git people first.
+</p>
+
+<p>
+Second, the command that will really save your bacon is git-reflog. Using it works something like this:
+</p>
+<pre class="code"> $ git reflog
+ 086908e... HEAD@{0}: cherry-pick: Last minute updates to the READMEs for all pro
+ 2a79a23... HEAD@{1}: checkout: moving to master
+ 2a79a23... HEAD@{2}: checkout: moving to master
+ ...
+ $ git reset --hard HEAD@{1}</pre>
+
+<p>
+ The last command (git reset –hard …) will rollback all your changes to the â??checkout: moving to masterâ??. Remember: donâ??t panic! Most things are fixable when using git.
+</p>
+
+</div>
+<!-- SECTION "... recover from a really messed up local repository?" [10647-] --></body>
+</html>
diff --git a/docs/wiki/geda-sdb_howto.html b/docs/wiki/geda-sdb_howto.html
new file mode 100644
index 0000000..0cf4f90
--- /dev/null
+++ b/docs/wiki/geda-sdb_howto.html
@@ -0,0 +1,1067 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#spice_on_geda_howto" class="toc">SPICE on gEDA HOWTO</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#introduction" class="toc">Introduction</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#overview" class="toc">Overview</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#spice-sdb_netlister_installation_and_configuration" class="toc">Spice-sdb netlister installation and configuration</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#design_simulation_flow_summary" class="toc">Design/simulation flow summary</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#preliminary_notes_about_symbols_and_spice_model_files" class="toc">Preliminary notes about symbols and SPICE model files</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#symbol_creation_for_spice_netlisting" class="toc">Symbol creation for SPICE netlisting.</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#spice_file_configuration" class="toc">SPICE file configuration</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#schematic_capture" class="toc">Schematic capture</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#gschem_attributes_for_spice_netlisting" class="toc">Gschem attributes for spice netlisting</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#handling_hierarchical_models" class="toc">Handling hierarchical models</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#spice_netlist_generation" class="toc">SPICE netlist generation</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#creating_the_netlist" class="toc">Creating the netlist</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#common_netlisting_problems" class="toc">Common netlisting problems</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#spice_simulation" class="toc">SPICE simulation</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#ltspice" class="toc">LTSpice</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#ngspice_and_tclspice" class="toc">Ngspice and tclspice</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#appendix" class="toc">Appendix</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#component_attribute_summary" class="toc">Component attribute summary</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#valid_type_values" class="toc">Valid "type" values</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#document_history" class="toc">Document History</a></span></div></li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="spice_on_geda_howto" id="spice_on_geda_howto">SPICE on gEDA HOWTO</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "SPICE on gEDA HOWTO" [1-34] -->
+<h2><a name="introduction" id="introduction">Introduction</a></h2>
+<div class="level2">
+
+<p>
+The purpose of this document is to explain how to use the gEDA tools (running on Linux) to perform SPICE simulations. In particular, this HOWTO documents the usage of spice-sdb, which is an advanced backend for the gEDA netlister (gnetlist) used to create SPICE netlists. This HOWTO also provides advice about using LTSpice and/or ngspice to simulate a circuit netlisted with spice-sdb. I assume that you are already familiar with electronic design, the mechanics of schematic capture using EDA tools, and SPICE simulation in general. I also assume that you are reasonably familiar with the Linux operating system and its development environment.
+</p>
+
+</div>
+<!-- SECTION "Introduction" [35-708] -->
+<h3><a name="overview" id="overview">Overview</a></h3>
+<div class="level3">
+
+<p>
+From the top level, SPICE simulation in gEDA proceeds via the following steps:
+</p>
+<ol>
+<li class="level1"><div class="li"> Creation and gathering of schematic symbols and SPICE model files. Oftentimes, the SPICE model files are obtained from the component vendor.</div>
+</li>
+<li class="level1"><div class="li"> Schematic capture using symbols and SPICE models created in step 1.</div>
+</li>
+<li class="level1"><div class="li"> Netlist generation from the schematic created in step 2.</div>
+</li>
+<li class="level1"><div class="li"> SPICE simulation of the circuit described by the netlist created in step 3.</div>
+</li>
+</ol>
+
+<p>
+ To create a SPICE netlist, the netlister (gnetlist) iterates through the entire schematic and looks at several parts of each componentâ??s symbol in order to create a blob of SPICE code. In general, each component can generate one or more lines of SPICE code. Component information needed by the netlister is held in two places:
+</p>
+<ol>
+<li class="level1"><div class="li"> The symbol itself, in the â??deviceâ?? attribute, which is attached when the symbol is created, and is typically accessed through the symbol editor.</div>
+</li>
+<li class="level1"><div class="li"> In attributes manually attached to the component during schematic capture using gschem.</div>
+</li>
+</ol>
+
+<p>
+ Since there are two places the netlister looks for information, you must make sure that the required information is available in both places.
+</p>
+
+</div>
+<!-- SECTION "Overview" [709-1877] -->
+<h3><a name="spice-sdb_netlister_installation_and_configuration" id="spice-sdb_netlister_installation_and_configuration">Spice-sdb netlister installation and configuration</a></h3>
+<div class="level3">
+
+<p>
+This document was originally written around gEDA/gaf 20030223, and the SPICE netlister spice-SDB. Starting with gEDA/gaf 20030525, my netlister was incorporated into the main gEDA distribution, and renamed spice-sdb (lower case sdb). <strong>For smoothest operation, you are best off just downloading and installing the latest version of gEDA.</strong> However, if you have a gEDA version predating 20030525, and you want to hack, you can download and install spice-SDB using the instructions provided on <a href="http://www.brorson.com/gEDA/SPICE/SPICEonLinux.html"; class="urlextern" title="http://www.brorson.com/gEDA/SPICE/SPICEonLinux.html"; rel="nofollow">http://www.brorson.com/gEDA/SPICE/SPICEonLinux.html</a>. In any event, itâ??s a good idea to make sure that the file gnet-spice-sdb.scm is present in your scheme directory (usually <strong><code>${prefix}/geda/share/gEDA/scheme</code></strong>) if you are interested in performing SPICE simulations with gEDA as described in this HOWTO.
+</p>
+
+</div>
+<!-- SECTION "Spice-sdb netlister installation and configuration" [1878-2744] -->
+<h3><a name="design_simulation_flow_summary" id="design_simulation_flow_summary">Design/simulation flow summary</a></h3>
+<div class="level3">
+
+<p>
+The detailed steps required to create a circuit and simulate it with gEDA look like this:
+</p>
+<ol>
+<li class="level1"><div class="li"> Schematic symbol creation with correct â??deviceâ?? attribute. (Usually, the symbols have already been created with the correct â??deviceâ?? attribute, but if you are having problems, it doesnâ??t hurt to check them.)</div>
+</li>
+<li class="level1"><div class="li"> Schematic capture using gschem.</div>
+</li>
+<li class="level1"><div class="li"> Assignment of SPICE attributes (value, model, file, type, etc.) to components using gschem.</div>
+</li>
+<li class="level1"><div class="li"> Assignment of <strong><code>refdes</code></strong> using e.g. refdes_renum.</div>
+</li>
+<li class="level1"><div class="li"> Creation of netlist using â??gnetlist -g spice-sdbâ??.</div>
+</li>
+<li class="level1"><div class="li"> Check netlist for correctness (manually open and inspect netlist).</div>
+</li>
+<li class="level1"><div class="li"> Run spice using a simulator such as LTSpice or ngspice.</div>
+</li>
+<li class="level1"><div class="li"> Plot/analyze results (often plotting/analysis tools are incorporated in the simulator).</div>
+</li>
+</ol>
+
+<p>
+ The purpose of this HOWTO is to provide the detailed understanding necessary to successfully navigate this process.
+</p>
+
+</div>
+<!-- SECTION "Design/simulation flow summary" [2745-3673] -->
+<h2><a name="preliminary_notes_about_symbols_and_spice_model_files" id="preliminary_notes_about_symbols_and_spice_model_files">Preliminary notes about symbols and SPICE model files</a></h2>
+<div class="level2">
+
+</div>
+<!-- SECTION "Preliminary notes about symbols and SPICE model files" [3674-3739] -->
+<h3><a name="symbol_creation_for_spice_netlisting" id="symbol_creation_for_spice_netlisting">Symbol creation for SPICE netlisting.</a></h3>
+<div class="level3">
+
+<p>
+The SPICE netlister recognizes a particular symbol in two ways:
+</p>
+<ol>
+<li class="level1"><div class="li"> The symbolâ??s â??deviceâ?? attribute</div>
+</li>
+<li class="level1"><div class="li"> The symbolâ??s <strong><code>refdes</code></strong>. Both of these attributes are attached to the symbol when the symbol is created.</div>
+</li>
+</ol>
+
+<p>
+ Each symbol has a <strong><code>device</code></strong> attribute attached to it. The <strong><code>device</code></strong> attribute is the first thing the netlister examines when processing the symbol. There are a number of devices which are native to the netlister, meaning that the netlister knows exactly how to deal with these types of devices. Native device types include RESISTOR, CAPACITOR, NPN_TRANSISTOR, etc. The entire list of native devices is present in the <a href="#appendix" title=":geda:sdb_howto.txt ↵" class="wikilink1">Appendix</a>.<br/>
+ The <strong><code>device</code></strong> attribute is hidden during normal use of gschem. Most often, the symbolâ??s creator has already given the symbol the correct <strong><code>device</code></strong> attribute. However, because the <strong><code>device</code></strong> attribute is hidden from the ordinary user, it can sometimes cause problems with SPICE netlist creation when it is set to an unexpected value. To view the <strong><code>device</code></strong> attribute, go into the symbol editor (select the symbol to edit, and do â??Hierarchyâ?? → â??down symbolâ??), and turn on invisible attributes (Edit → show/hide inv text). If the <strong><code>device</code></strong> attribute is incorrect, you may change it by editing the symbol itself using a text editor.<br/>
+ If a symbol is not native (i.e. the netlister doesnâ??t recognize it as a built-in type), the netlister relies upon the first letter of the <strong><code>refdes</code></strong> to determine how to process the symbol. The <strong><code>refdes</code></strong> prefix is also built into the symbol when it is created. Example <strong><code>refdes</code></strong> prefixes are R for resistors, C for capacitors, Q for transistors, etc. <strong><code>refdes</code></strong> prefixes correct for SPICE are listed in the <a href="#appendix" title=":geda:sdb_howto.txt ↵" class="wikilink1">Appendix</a>. Note that relying upon the <strong><code>refdes</code></strong> to identify the component for SPICE is not foolproof – for example, the netlister cannot distinguish between NPN and PNP transistors based upon the <strong><code>refdes</code></strong>. Therefore, it is always best to use a native â??deviceâ?? in your symbols.
+</p>
+
+</div>
+<!-- SECTION "Symbol creation for SPICE netlisting." [3740-5819] -->
+<h3><a name="spice_file_configuration" id="spice_file_configuration">SPICE file configuration</a></h3>
+<div class="level3">
+
+<p>
+Files holding complicated SPICE models or other SPICE code may be incorporated into the final SPICE netlist by including appropriate symbols into the schematic. SPICE model files are usually obtained from component vendors. Dealing with these files is straightforward. However, some issues should be kept in mind when preparing models for use during schematic capture:
+</p>
+<ul>
+<li class="level1"><div class="li"> It is usually prudent to place these files into a dedicated directory distinct from the symbol directories.</div>
+</li>
+<li class="level1"><div class="li"> Make sure that the SPICE files pin assignments correctly correspond to the pins as defined in the componentâ??s symbol.</div>
+</li>
+<li class="level1"><div class="li"> Make sure that the last character in a SPICE model file is a carriage return. If no carriage return exists, then the next component listed in the netlist may be placed on the same line as the last line of the SPICE model file.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "SPICE file configuration" [5820-6689] -->
+<h2><a name="schematic_capture" id="schematic_capture">Schematic capture</a></h2>
+<div class="level2">
+
+<p>
+Schematic capture is the process by which one uses a special-purpose drawing program to draw a schematic diagram of the circuit under design. In the gEDA environment, the schematic capture program is called â??gschemâ??. I assume you already know how to use gschem. For the purposes of creating SPICE netlists, you must use gschem to attach attributes to components, and possibly also incorporate other SPICE directives into your netlist. After you are done with schematic capture, you create the SPICE netlist by running gEDAâ??s netlister â??gnetlistâ?? on your design.
+</p>
+
+</div>
+<!-- SECTION "Schematic capture" [6690-7282] -->
+<h3><a name="gschem_attributes_for_spice_netlisting" id="gschem_attributes_for_spice_netlisting">Gschem attributes for spice netlisting</a></h3>
+<div class="level3">
+
+<p>
+There are several ways that spice attributes may be associated with a component using gschem. The way you choose to do this depends upon many factors, including the type of component, and the size and format of the SPICE model.
+</p>
+
+</div>
+
+<h4><a name="component_attributes_and_meanings" id="component_attributes_and_meanings">Component attributes and meanings</a></h4>
+<div class="level4">
+
+<p>
+The following attributes are meaningful for SPICE netlisting, and may be attached from within gschem:
+</p>
+<table class="inline">
+ <tr>
+ <td><strong><code>refdes</code></strong></td><td>The reference designator of the component. Valid values depend upon the component type and are given in the appendix.</td>
+ </tr>
+ <tr>
+ <td><strong><code>value</code></strong></td><td>For passives, this is the component value. For actives, this is the type (model no) of the component (e.g. 2N3904, uA741). When a model for an active is instantiated separately from the component itself, the â??valueâ?? attribute holds the name of the spice model.</td>
+ </tr>
+ <tr>
+ <td><strong><code>model</code></strong></td><td>This holds a one line spice model for the component.</td>
+ </tr>
+ <tr>
+ <td><strong><code>file</code></strong></td><td>This holds the name of a file. Typically, this is a file holding e.g. a SPICE .MODEL, .SUBCKT, or other SPICE code.</td>
+ </tr>
+ <tr>
+ <td><strong><code>model-name</code></strong></td><td>This holds the name of the spice model referred to in a .MODEL or .SUBCKT statement. â??model-nameâ?? is mainly used to identify the spice model name in the symbol â??spice-model-1.symâ??. Active components should call out this name in the â??deviceâ?? attribute to associate the component with its particular spice model or subcircuit.</td>
+ </tr>
+ <tr>
+ <td><strong><code>type</code></strong></td><td>This specifies the type of component and is used by spice when interpreting the model parameters. Valid values depend upon the device being modeled.</td>
+ </tr>
+</table>
+
+</div>
+
+<h4><a name="refdes_conventions" id="refdes_conventions">refdes conventions</a></h4>
+<div class="level4">
+
+<p>
+As a prerequisite to handling SPICE-related attributes, the SPICE netlister requires that all components must have a refdes attached to them. The refdes may be attached either by hand (which is laborious), or using the program refdes_renum included in the gEDA distribution.<br/>
+ Note that the first letter of the refdes must correspond to the appropriate letter for spice simulation. The refdes convention is given in the <a href="#appendix" title=":geda:sdb_howto.txt ↵" class="wikilink1">Appendix</a>.
+</p>
+
+</div>
+
+<h4><a name="passives" id="passives">Passives</a></h4>
+<div class="level4">
+
+</div>
+
+<h5><a name="basic_passives" id="basic_passives">Basic passives</a></h5>
+<div class="level5">
+
+<p>
+The most basic components which one encounters in spice are passive components like resistors and capacitors which have numeric values, but no other modeling attributes. In this case the following attributes must be filled in:
+</p>
+<table class="inline">
+ <tr>
+ <td><strong><code>refdes</code></strong></td><td>The correct <strong><code>refdes</code></strong> for the component.</td>
+ </tr>
+ <tr>
+ <td><strong><code>value</code></strong></td><td>For passives, this is the numeric value of the component (e.g. 100pF). For actives, this attribute may be filled in, but if no model attribute is available elsewhere in the schematic, the value is not used (in SPICE netlisting, anyway).</td>
+ </tr>
+</table>
+
+<p>
+ If only a <strong><code>refdes</code></strong> and value attribute are encountered, the netlister will write a single line into the output file.<br/>
+ Example resistor:
+</p>
+<pre class="code">refdes = R2
+value = 220
+SPICE line generated: R2 0 4 220</pre>
+
+<p>
+Note that â??0â?? and â??4â?? correspond to the net nodes connected to the component, and are generated automatically by gnetlist.<br/>
+ Example capacitor:
+</p>
+<pre class="code">refdes = C22
+value = 1UF
+SPICE line generated: C22 4 23 1UF</pre>
+
+</div>
+
+<h5><a name="passives_with_additional_attributes" id="passives_with_additional_attributes">Passives with additional attributes</a></h5>
+<div class="level5">
+
+<p>
+Oftentimes, passive components have additional attributes attached to them for spice simulation. Examples of such attributes are temperature coefficients (for resistors) and initial conditions (for reactive components). These additional components may be incorporated into the SPICE file by simply attaching them to the componentâ??s â??modelâ?? attribute. Specifically, the required attributes are:
+</p>
+<table class="inline">
+ <tr>
+ <td><strong><code>refdes</code></strong></td><td>Correct component <strong><code>refdes</code></strong>.</td>
+ </tr>
+ <tr>
+ <td><strong><code>value</code></strong></td><td>Numerical component value, as always.</td>
+ </tr>
+ <tr>
+ <td><strong><code>model</code></strong></td><td>One line string holding additional parameters, formatted as a valid SPICE string.</td>
+ </tr>
+</table>
+
+<p>
+ This string is placed after the component value in the line generated by gnetlist. Therefore, it is important to format the string placed in the <strong><code>model</code></strong> line to be valid SPICE code. Otherwise, you will risk causing the SPICE simulator to barf.<br/>
+ Example resistor:
+</p>
+<pre class="code">refdes = R5
+value = 1MEG
+model = TC=0.001,0.015
+SPICE line generated: R2 0 4 220 TC=0.001,0.015</pre>
+
+</div>
+
+<h4><a name="transistors_and_diodes" id="transistors_and_diodes">Transistors and diodes</a></h4>
+<div class="level4">
+
+<p>
+Transistors and diodes are generally accompanied by a device-specific model – otherwise, SPICE simulation is pointless. The SPICE model may be either a short, one-line string of parameters, or a multi-line set of SPICE parameters. A typical one-line parameter string is a short list of parameters describing a small-signal diode. Typical multi-line models come from component vendors, who often provide models for their components in a text file. Since there are two broad formats of SPICE information, there are two approaches to incorporating these parameters into the schematic:
+</p>
+
+</div>
+
+<h5><a name="one_line_string_of_spice_parameters" id="one_line_string_of_spice_parameters">One line string of SPICE parameters</a></h5>
+<div class="level5">
+
+<p>
+To incorporate a one line string of SPICE parameters into the netlist, the following attributes must be attached to the component:
+</p>
+<table class="inline">
+ <tr>
+ <td><strong><code>refdes</code></strong></td><td>Correct component refdes.</td>
+ </tr>
+ <tr>
+ <td><strong><code>value</code></strong></td><td>The model number or part number of the component.</td>
+ </tr>
+ <tr>
+ <td><strong><code>model-name</code></strong></td><td>The name you wish to give the SPICE model. This is usually the model number or part number of the component. If you have already attached a â??valueâ?? attribute to the component, this parameter is optional.</td>
+ </tr>
+ <tr>
+ <td><strong><code>model</code></strong></td><td>One line string holding additional parameters. Do not place the model parameters in parentheses – gnetlist will do this for you.</td>
+ </tr>
+</table>
+
+<p>
+ Example diode:
+</p>
+<pre class="code">refdes = D5
+model-name = 1N1004
+model = IS=0.5UA RS=6 BV=5.20
+SPICE lines generated:
+D5 2 6 1N1004
+MODEL 1N1004 D (IS=0.5UA RS=6 BV=5.20)</pre>
+
+</div>
+
+<h5><a name="spice_model_file" id="spice_model_file">SPICE model file</a></h5>
+<div class="level5">
+
+<p>
+To incorporate a file-full of SPICE parameters into the netlist, the following attributes must be attached to the component:
+</p>
+<table class="inline">
+ <tr>
+ <td><strong><code>refdes</code></strong></td><td>Correct component refdes.</td>
+ </tr>
+ <tr>
+ <td><strong><code>value</code></strong></td><td>The model number or part number of the component.</td>
+ </tr>
+ <tr>
+ <td><strong><code>model-name</code></strong></td><td>The name you wish to give the SPICE model. This is usually the model number or part number of the component. If you have already attached a â??valueâ?? attribute to the component, this parameter is optional.</td>
+ </tr>
+ <tr>
+ <td><strong><code>file</code></strong></td><td>The file name of the SPICE model which you wish to incorporate into the netlist. This file name may specify either a relative or an absolute path, but it is probably better to use an absolute path to avoid problems if you ever move your schematic directory.</td>
+ </tr>
+</table>
+
+<p>
+ Note that you need to make sure that the model name held in your SPICE model file is the same as the <strong><code>value</code></strong> or <strong><code>model-name</code></strong> attributes you attached to the component. It is also a good idea to verify that the pin assignments in the model file correspond to the pin assignments made by the component symbol.
+</p>
+
+</div>
+
+<h4><a name="actives_--_integrated_circuits" id="actives_--_integrated_circuits">Actives -- integrated circuits</a></h4>
+<div class="level4">
+
+<p>
+Integrated circuits are incorporated into the netlist similarly to transistors and diodes. As such, you may incorporate the spice information either as a one-line parameter string, or as a model file.
+</p>
+
+</div>
+
+<h5><a name="one_line_string_of_spice_parameters1" id="one_line_string_of_spice_parameters1">One line string of SPICE parameters</a></h5>
+<div class="level5">
+
+<p>
+To incorporate a one line string of SPICE parameters into the netlist, the following attributes must be attached to the component:
+</p>
+<table class="inline">
+ <tr>
+ <td><strong><code>refdes</code></strong></td><td>Correct component refdes.</td>
+ </tr>
+ <tr>
+ <td><strong><code>value</code></strong></td><td>The model number or part number of the component.</td>
+ </tr>
+ <tr>
+ <td><strong><code>model-name</code></strong></td><td>the name you wish to give the SPICE model. This is usually the model number or part number of the component. If you have already attached a â??valueâ?? attribute to the component, this parameter is optional.</td>
+ </tr>
+ <tr>
+ <td><strong><code>model</code></strong></td><td>One line string holding additional parameters. Do not place the model parameters in parentheses – gnetlist will do this for you.</td>
+ </tr>
+</table>
+
+</div>
+
+<h5><a name="spice_.model_or_.subckt_file" id="spice_.model_or_.subckt_file">SPICE .MODEL or .SUBCKT file</a></h5>
+<div class="level5">
+
+<p>
+To incorporate a file-full of SPICE parameters into the netlist, the following attributes must be attached to the component:
+</p>
+<table class="inline">
+ <tr>
+ <td><strong><code>refdes</code></strong></td><td>Correct component refdes. <strong>Note that if the file holds a .MODEL, the refdes should start with U; if the file holds a .SUBCKT, the refdes should start with X.</strong> The netlister checks for the file type and tries to â??do the right thingâ??, but problems can arise if you donâ??t follow this rule.</td>
+ </tr>
+ <tr>
+ <td><strong><code>value</code></strong></td><td>The model number or part number of the component.</td>
+ </tr>
+ <tr>
+ <td><strong><code>model-name</code></strong></td><td>The name you wish to give the SPICE model. This is usually the model number or part number of the component. If you have already attached a â??valueâ?? attribute to the component, this parameter is optional.</td>
+ </tr>
+ <tr>
+ <td><strong><code>file</code></strong></td><td>The name of the file holding the SPICE .MODEL or .SUBCKT which you wish to incorporate into the netlist. This file name may specify either a relative or an absolute path, but it is probably better to use an absolute path to avoid problems if you ever move your schematic directory.</td>
+ </tr>
+</table>
+
+</div>
+
+<h4><a name="independent_sources" id="independent_sources">Independent sources</a></h4>
+<div class="level4">
+
+<p>
+There are two independent sources: voltage sources and current sources. For incorporation into a SPICE netlist, they both work the same way. To incorporate an independent source into your SPICE netlist, do the following:
+</p>
+<ol>
+<li class="level1"><div class="li"> Place the independent source on your schematic. (Do â??Addâ?? → â??Componentâ?? → â??spiceâ?? → "<independent source name>.symâ??)</div>
+</li>
+<li class="level1"><div class="li"> Double click on the block and add/edit the following attributes:</div>
+<ul>
+<li class="level2"><div class="li"> <strong><code>refdes</code></strong>: V? or I?</div>
+</li>
+<li class="level2"><div class="li"> <strong><code>value</code></strong>: A one line string in SPICE format describing the source.</div>
+</li>
+</ul>
+</li>
+</ol>
+
+</div>
+
+<h4><a name="dependent_sources" id="dependent_sources">Dependent sources</a></h4>
+<div class="level4">
+
+<p>
+There are four dependent sources:
+</p>
+<ul>
+<li class="level1"><div class="li"> This section remains TBD.</div>
+</li>
+</ul>
+
+</div>
+
+<h4><a name="spice_components" id="spice_components">SPICE components</a></h4>
+<div class="level4">
+
+</div>
+
+<h5><a name="spice_model_block" id="spice_model_block">Spice model block</a></h5>
+<div class="level5">
+
+<p>
+In certain situations, you may wish to embed a spice model block directly into your schematic. This is done when you have several devices with a â??valueâ?? attribute calling out for a spice model. Depending upon whether the spice block is one line or multi-line, you may embed the code in one of two ways:
+</p>
+<ol>
+<li class="level1"><div class="li"> One line SPICE model:</div>
+<ol>
+<li class="level2"><div class="li"> Place a spice model block on your schematic. (Do â??Addâ?? → â??Componentâ?? → â??spiceâ?? → â??spice-model-1.symâ??)</div>
+</li>
+<li class="level2"><div class="li"> Double click on the block and add/edit the following attributes:</div>
+<ul>
+<li class="level3"><div class="li"> <strong><code>refdes</code></strong>: a?</div>
+</li>
+<li class="level3"><div class="li"> <strong><code>model</code></strong>: model name (i.e. the model name used in the components being modeled.)</div>
+</li>
+<li class="level3"><div class="li"> <strong><code>type</code></strong>: One of the valid spice component types defined in the spice <acronym title="specification">spec</acronym>.</div>
+</li>
+<li class="level3"><div class="li"> <strong><code>value</code></strong>: The corresponding one-line spice model</div>
+</li>
+</ul>
+</li>
+</ol>
+</li>
+<li class="level1"><div class="li"> Multi-line SPICE model:</div>
+<ol>
+<li class="level2"><div class="li"> Place a spice model block on your schematic.(Do â??Addâ?? → â??Componentâ?? → â??spiceâ?? → â??spice-model-1.symâ??)</div>
+</li>
+<li class="level2"><div class="li"> Double click on the block and add/edit the following attributes:</div>
+<ul>
+<li class="level3"><div class="li"> <strong><code>refdes</code></strong>: a?</div>
+</li>
+<li class="level3"><div class="li"> <strong><code>model-name</code></strong>: model name</div>
+</li>
+<li class="level3"><div class="li"> <strong><code>file</code></strong>: Name of file holding SPICE model code (i.e. .MODEL or .SUBCKT).</div>
+</li>
+</ul>
+</li>
+</ol>
+</li>
+</ol>
+
+</div>
+
+<h5><a name="include_block" id="include_block">Include block</a></h5>
+<div class="level5">
+
+<p>
+The include block places a .INCLUDE directive into your netlist.
+</p>
+<ol>
+<li class="level1"><div class="li"> Place a spice model block on your schematic. (Do â??Addâ?? → â??Componentâ?? → â??spiceâ?? → â??spice-include-1.symâ??)</div>
+</li>
+<li class="level1"><div class="li"> Double click on the block and add/edit the following attributes:</div>
+<ul>
+<li class="level2"><div class="li"> <strong><code>refdes</code></strong>: a?</div>
+</li>
+<li class="level2"><div class="li"> <strong><code>file</code></strong>: The name of the file to include.</div>
+</li>
+</ul>
+</li>
+</ol>
+
+</div>
+
+<h5><a name="spice_directive_block" id="spice_directive_block">SPICE directive block</a></h5>
+<div class="level5">
+
+<p>
+Placing a SPICE directive block into your schematic creates an arbitrary block of SPICE code in the netlist. The directive may be either statements held in a file, or a one-line string held in the â??modelâ?? attribute. Examples of situations where this is useful include:
+</p>
+<ul>
+<li class="level1"><div class="li"> .TEMP statement</div>
+</li>
+<li class="level1"><div class="li"> .IC statement</div>
+</li>
+<li class="level1"><div class="li"> Other SPICE statements for which gschem has no symbol.</div>
+</li>
+</ul>
+
+<p>
+ To place a SPICE directive on your schematic, do the following:
+</p>
+<ol>
+<li class="level1"><div class="li"> Place a SPICE directive block on your schematic. (Do â??Addâ?? → â??Componentâ?? → â??spiceâ?? → â??spice-directive-1.symâ??)</div>
+</li>
+<li class="level1"><div class="li"> Double click on the block and add/edit the following attributes:</div>
+<ul>
+<li class="level2"><div class="li"> <strong><code>refdes</code></strong>: a?</div>
+</li>
+<li class="level2"><div class="li"> <strong><code>file</code></strong>: The name of the file to include.</div>
+</li>
+</ul>
+</li>
+</ol>
+
+</div>
+<!-- SECTION "Gschem attributes for spice netlisting" [7283-18697] -->
+<h3><a name="handling_hierarchical_models" id="handling_hierarchical_models">Handling hierarchical models</a></h3>
+<div class="level3">
+
+<p>
+In SPICE modeling, there are often situations where you wish to create a schematic representation of some particular component as a .SUBCKT, and then embed that componentâ??s model in a higher level schematic. A common example might be as follows: You are doing a microwave simulation, and want to use a capacitor model which includes parasitic inductances and resistances, as well as the capacitance. Capacitor manufacturers often supply a printed schematic showing a circuit topology incorporating parasitics, and specify values for the parasitics. You would like to draw the capacitor model using gschem, netlist it to create a .SUBCKT, and then use the .SUBCKT to model capacitors in a higher lever schematic.<br/>
+ Since this kind of task is very common in SPICE simulation, gnet-spice-sdb now supports it (starting with rev 20030331). To create a lower level .SUBCKT and use it in a higher level schematic, do the following:
+</p>
+<ol>
+<li class="level1"><div class="li"> Draw the schematic of the lower level component (e.g. the capacitor + parasitics) using gschem.</div>
+</li>
+<li class="level1"><div class="li"> On the lower level schematic, place a spice-subcircuit-LL block (spice-subcircuit-LL-1.sym). This alerts the netlister that the schematic is a Lower Level .SUBCKT. Attach the following attributes to the symbol:<br/>
+ <br/>
+ <strong><code>model-name</code></strong> = cap_with_parasitics<br/>
+ <br/>
+ (Of course, â??cap_with_parasiticsâ?? is the example we use here. Use your own model name in your schematic.) Upon netlisting, this schematic symbol will cause the netlist to insert ".SUBCKT cap_with_parasitics " into the first line of the netlist file.</div>
+</li>
+<li class="level1"><div class="li"> On the lower level schematic, attach a spice-subcircuit-IO symbol (spice-subcircuit-IO-1.sym) to each IO net (i.e. connection to the upper level). Number the refdeses of the IO symbols in the same order as you would like the IO nets to be listed in the .SUBCKT line in the output file. (i.e. P1 = first, P2 = second, etc.)</div>
+</li>
+<li class="level1"><div class="li"> When you are done with the lower level schematic, netlist it in the usual way. For example, if your schematic is called cap_with_parasitics.sch, netlist it by saying:<br/>
+ <br/>
+ <strong><code>gnetlist -g spice-sdb -o cap_with_parasitics.cir cap_with_parasitics.sch</code></strong><br/>
+ <br/>
+ This will dump the SPICE netlist into the file called â??cap_with_parasitics.cirâ??. Visually inspect the .cir file to make sure that netlisting worked correctly.</div>
+</li>
+<li class="level1"><div class="li"> Next, create a symbol for the upper level schematic which will point to the .SUBCKT. Note that the symbol must have a refdes starting with the letter â??Xâ??. To ensure that this happens, do the following:</div>
+<ul>
+<li class="level2"><div class="li"> Use gschem to draw the symbol. I usually draw a box around a model symbol to distinguish it from a normal component. Make any other annotations desired.</div>
+</li>
+<li class="level2"><div class="li"> In the symbol, make sure that the pins are ordered identically to the order in which you have placed the pins in the .SUBCKT. This is done by editing the symbol with a text editor and setting the â??PINSEQâ?? attribute. The netlister will output the pins in the order determined by the â??PINSEQâ?? attribute.</div>
+</li>
+<li class="level2"><div class="li"> Using a text editor, give the symbol a â??DEVICEâ?? attribute like â??capacitor-modelâ??. Do not assign the symbol one of the native device types listed in the appendix! The goal is to create a symbol whose refdes starts with â??Xâ??, and if the â??DEVICEâ?? is a recognized type, this will not happen.</div>
+</li>
+<li class="level2"><div class="li"> Using a text editor, give the symbol the â??REFDESâ?? attribute â??X?"</div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> Create the upper level schematic. Place your newly created symbol on the schematic as many times as required & wire up the schematic in the usual way.</div>
+</li>
+<li class="level1"><div class="li"> To point your symbol to the lower level .SUBCKT, double click on the symbol and set the following attributes:<br/>
+ <br/>
+ <strong><code>file</code></strong> = cap_with_parasitics.cir<br/>
+ <strong><code>model-name</code></strong> = cap_with_parasitics<br/>
+ <br/>
+ as well as any other attributes required (e.g. refdes).</div>
+</li>
+<li class="level1"><div class="li"> Now netlist your upper level schematic the usual way. The contents of each .SUBCKT file is dumped into the main netlist. Inspect your netlist visually using a text editor to ensure that it is correct. It is a good idea to pay particular attention to the following:</div>
+<ul>
+<li class="level2"><div class="li"> Verify that the ordering of the nets connecting the upper level netlist to the lower level .SUBCKT is correct.</div>
+</li>
+<li class="level2"><div class="li"> Make sure that the upper level model-name and the lower level model name (on the .SUBCKT declaration line) are the same.</div>
+</li>
+</ul>
+</li>
+</ol>
+
+<p>
+ Once the netlist is created, you may simulate your design using any SPICE simulator desired.<br/>
+
+</p>
+
+<p>
+One final note: The netlister writes the contents of the lower level .SUBCKT file into the main netlist <strong>every time</strong> it encounters a component with â??FILEâ?? attribute pointing to that file. Therefore, if you use the same component with the same model more than once in a design you should instantiate the model file using a â??spice-modelâ?? symbol and point to it with each component. This is described in the â??multi-line SPICE model blockâ?? section above.
+</p>
+
+</div>
+<!-- SECTION "Handling hierarchical models" [18698-23545] -->
+<h2><a name="spice_netlist_generation" id="spice_netlist_generation">SPICE netlist generation</a></h2>
+<div class="level2">
+
+<p>
+Once the schematic is captured, a SPICE netlist can be generated running the gEDA utility â??gnetlistâ?? on the schematic files. Gnetlist is built to be customizable, and is able to generate a netlist of any desired format using a Scheme back-end, which does the real heavy-lifting of creating the netlist. The back-end Scheme file which implements SPICE netlisting is called gnet-spice-sdb.scm, and it lives in the ${PREFIX}/geda/share/gEDA/scheme directory.
+</p>
+
+</div>
+<!-- SECTION "SPICE netlist generation" [23546-24039] -->
+<h2><a name="creating_the_netlist" id="creating_the_netlist">Creating the netlist</a></h2>
+<div class="level2">
+
+<p>
+Creating a netlist from a schematic is easy. To generate a SPICE netlist, just do the following:
+</p>
+<ul>
+<li class="level1"><div class="li"> Save your schematic to <filename.sch></div>
+</li>
+<li class="level1"><div class="li"> Create the SPICE netlist by doing â??gnetlist â??g spice-sdb <filename.sch>". The output is a netlist held in the file output.net. Alternatively, if you wish to give your output file a different name, set the output name using the -o switch. For example:<br/>
+ <br/>
+ <strong><code>gnetlist -g spice-sdb -o amplifier.cir amplifier.sch</code></strong> <br/>
+ <br/>
+ takes the design schematic called â??amplifier.schâ?? and outputs a SPICE netlist named â??amplifier.cirâ??.</div>
+</li>
+<li class="level1"><div class="li"> Inspect your SPICE netlist using a text editor. Verify that there are no missing attributes or other netlist problems.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Creating the netlist" [24040-24765] -->
+<h2><a name="common_netlisting_problems" id="common_netlisting_problems">Common netlisting problems</a></h2>
+<div class="level2">
+
+<p>
+It is important to manually inspect your SPICE netlist prior to using it in simulation. Please remember that the netlister is still â??alphaâ?? quality, and some problems may still exist in netlist generation. The following list attempts to catalog common problems with the netlist and the associated fixes.
+</p>
+<ul>
+<li class="level1"><div class="li"> ERROR_INVALID_<acronym title="Personal Identification Number">PIN</acronym>: This can happen if the symbolâ??s PINSEQ attributes donâ??t start at 1, or have gaps in the numbering. This must be fixed by editing the symbol itself in a text editor.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Common netlisting problems" [24766-25301] -->
+<h2><a name="spice_simulation" id="spice_simulation">SPICE simulation</a></h2>
+<div class="level2">
+
+<p>
+There are several options for doing SPICE simulations under Linux; I will highlight two:
+</p>
+<ul>
+<li class="level1"><div class="li"> <strong>LTSpice</strong>, which is a freeware SPICE simulator originally released by Linear Technologies as a component selection/design tool running under Windows. Because its SPICE engine is very fast and powerful, it has become a popular SPICE simulator amongst hobbyists and design engineers who prefer to use free tools. LTSpice has been tweaked to run under Linux using wine; I recommend using it if you need a robust, <strong>professional-quality</strong> SPICE simulator.</div>
+<ul>
+<li class="level2"><div class="li"> <strong>Ngspice/tclspice</strong>, which is a component of the gEDA distribution. Ngspice provides a simulation engine, a command-line driven front-end, and the capability to plot simulation results graphically under X. The main branch of ngspice development has been arrested since late 2001. However, a fork of the development tree, called â??tclspiceâ??, remains under active development. Tclspice is the package I recommend if you want to use a <strong>Linux-native</strong> SPICE simulator. </div>
+</li>
+</ul>
+</li>
+</ul>
+
+<p>
+ There is also a <acronym title="GNU General Public License">GPL</acronym>â??ed simulator called â??gnucapâ??, which is based upon (or is the descendent of) Alâ??s Circuit Simulator (ACS). I havenâ??t used it at all; information about gnucap is therefore TBD.
+</p>
+
+</div>
+<!-- SECTION "SPICE simulation" [25302-26547] -->
+<h3><a name="ltspice" id="ltspice">LTSpice</a></h3>
+<div class="level3">
+
+<p>
+LTSpice was written by Mike Englehardt at Linear Technologies, and was originally given away by LinearTech as a design aid for engineers wishing to simulate the performance of LinearTechâ??s switch mode power supply controllers. The package incorporates a schematic capture front end, fast and powerful SPICE engine, and the capability for plotting the results of many different types of SPICE analysis. Personally, I think the schematic capture front-end is hard to use and clunky; gschem knocks its socks off for ease of use and features. However, the SPICE engine and analysis stuff in LTSpice is simply great.<br/>
+ LTSpice was originally developed to run under Windows, but Mike has tweaked it so that it runs fairly well on Linux under wine. (Only the help menu system is broken – the rest of the package runs well.) Another good feature of LTSpice is that it is well supported – Mike reads the newsgroup sci.electronics.cad regularly and is generally happy to help people who experience problems with it. Therefore, despite its Windoze heritage, I recommend LTSpice as a powerful, professional-quality simulation and analysis back end for gEDA.
+</p>
+
+</div>
+
+<h4><a name="installation_and_configuration_of_ltspice" id="installation_and_configuration_of_ltspice">Installation and configuration of LTSpice</a></h4>
+<div class="level4">
+
+<p>
+To install and configure LTSpice, do the following:
+</p>
+<ol>
+<li class="level1"><div class="li"> Download and install wine. I have had success using Wine-20030219.</div>
+</li>
+<li class="level1"><div class="li"> Download LTSpice. It is available under <a href="http://www.linear.com/software"; class="urlextern" title="http://www.linear.com/software"; rel="nofollow">http://www.linear.com/software</a> under the name SwitcherCAD-III.</div>
+</li>
+<li class="level1"><div class="li"> Run the LTSpice installer under wine.</div>
+</li>
+</ol>
+
+</div>
+
+<h4><a name="running_ltspice_with_geda_designs" id="running_ltspice_with_geda_designs">Running LTSpice with gEDA designs</a></h4>
+<div class="level4">
+
+<p>
+LTSpice can read a file holding a gEDA SPICE netlist. I have had success doing LTSpice sumulations in the following way:
+</p>
+<ol>
+<li class="level1"><div class="li"> First of all, make sure that you are logged in as a normal user – Wine doesnâ??t like to run when invoked by root.</div>
+</li>
+<li class="level1"><div class="li"> Create a file in your project directory called â??Simulation.cmdâ??. In this file place your spice analysis commands (e.g. .OP, .AC, .DC, etc.)</div>
+</li>
+<li class="level1"><div class="li"> Place a SPICE include block into your schematic. For the file attribute, type in â??Simulation.cmdâ??.</div>
+</li>
+<li class="level1"><div class="li"> Netlist your design.</div>
+</li>
+<li class="level1"><div class="li"> Create a link from your netlist â??output.netâ?? and a netlist in the directory in which SwCADIII lives. Make the netlist suffix .cir. For example: ln -s ${DESIGN_HOME}/output.net ${WINE_HOME}/.wine/fake_windows/Program Files/LTC/SwCADIII/MyDesign.cir</div>
+</li>
+<li class="level1"><div class="li"> Run LTSpice: cd into the directory where SwCADIII lives and say â??wine scad3.exeâ??</div>
+</li>
+<li class="level1"><div class="li"> From the SwCADIII <acronym title="Graphical User Interface">GUI</acronym>, do: File → Open → (files of type netlist [.cir]), and select your file.</div>
+</li>
+<li class="level1"><div class="li"> Run the simulator by clicking on the run button, or doing: Simulate → Run.</div>
+</li>
+<li class="level1"><div class="li"> Select the variables to graph, and then click OK. SwCADIII does the rest of the work.</div>
+</li>
+</ol>
+
+<p>
+ Naturally, it is very important to play around with LTSpice to understand how to use it effectively, but the above description should suffice to get you started.
+</p>
+
+</div>
+<!-- SECTION "LTSpice" [26548-29363] -->
+<h3><a name="ngspice_and_tclspice" id="ngspice_and_tclspice">Ngspice and tclspice</a></h3>
+<div class="level3">
+
+<p>
+Ngspice was started at the University of Rome by Paolo Nenzi as an attempt to create a <acronym title="GNU General Public License">GPL</acronym>â??ed version of the standard Berkeley SPICE version 3 by re-writing the entire SPICE package. Plans were also laid to create better, more robust computational algorithms for the simulation engine. More information is available at the <a href="http://ngspice.sourceforge.net/"; class="urlextern" title="http://ngspice.sourceforge.net/"; rel="nofollow">ngspice website</a>. Unfortunately, development on ngspice seems to have ceased at the end of 2001. Moreover, my initial experiences with ngspice were not good – it crashed and burned when run on many of my netlists, and it couldnâ??t deal with SPICE 2â??s POLY construct in dependent sources. Dependent sources with PLOY attributes are common in vendor models, so this represents a real deficiency.
+</p>
+
+<p>
+Fortunately, some friendly people at <a href="http://www.multigig.com"; class="urlextern" title="http://www.multigig.com"; rel="nofollow">MultiGig Ltd.</a> were busy developing a branch of ngspice which they called â??tclspiceâ??. The purpose of tclspice is to enable SPICE commands to be embedded into TCL scripts, thereby enabling automated circuit optimization. The project homepage is at <a href="http://tclspice.sourceforge.net/"; class="urlextern" title="http://tclspice.sourceforge.net/"; rel="nofollow">http://tclspice.sourceforge.net/</a>. Since the tclspice branch of the code was alive, I decided to work on it, instead of the seemingly dead main ngspice branch. During spring 2003, I fixed tclspice in three useful (IMNSHO) ways:
+</p>
+<ol>
+<li class="level1"><div class="li"> I fixed the parser so that it would handle netnames with non-numeric/non-alphabetic characters like "+" or "-" which are common in real netlists (e.g. â??Vin+", or â??Vout1_pull-upâ??).</div>
+</li>
+<li class="level1"><div class="li"> I fixed the parser so that it would correctly handle hierarchical schematics, and correctly deal with the netnames inside the blocks.</div>
+</li>
+<li class="level1"><div class="li"> I got the POLY translation code (which exists in XSPICE) working so that one can now run SPICE 2 netlists with tclspice.</div>
+</li>
+</ol>
+
+<p>
+ Tclspice seems to work nicely now (although there are still some issues with memory leaks). Moreover, because the tclspice code is a superset of ngspice, <strong>if you build tclspice, you will also build the command-line driven ngspice program</strong>. Therefore, I recommend getting and installing tclspice if you want to do Linux-native SPICE simulations.
+</p>
+
+</div>
+
+<h4><a name="installation_and_configuration_of_ngspice_and_tclspice" id="installation_and_configuration_of_ngspice_and_tclspice">Installation and configuration of ngspice and tclspice</a></h4>
+<div class="level4">
+
+<p>
+To install ngspice and tclspice, do the following:
+</p>
+<ol>
+<li class="level1"><div class="li"> Get the latest tclspice distribution from <a href="http://tclspice.sourceforge.net/"; class="urlextern" title="http://tclspice.sourceforge.net/"; rel="nofollow">http://tclspice.sourceforge.net/</a>. As of this writing, the latest version is tclspice-0.2.12. This version incorporates the fixes I mentioned above, as well as other improvements made by the hard-working people at MultiGig, so make sure that your version is equal or greater than 0.2.12.</div>
+</li>
+<li class="level1"><div class="li"> Do the usual â??gunzip ; tar -xvfâ?? dance to create a source directory for tclspice.</div>
+</li>
+<li class="level1"><div class="li"> First build ngspice. Do "./configure –enable-xspice –prefix=/usr/local/gedaâ?? in the source directory. Of course, "–prefix=" should point to the place where you put your geda stuff. Note that you also must do "–enable-xspiceâ?? to be able to use SPICE 2 POLYs (and other XSpice goodies).</div>
+</li>
+<li class="level1"><div class="li"> Do â??make && make installâ?? to compile and install ngspice. As always, you will probably need to be root in order to install the packages in a public directory.</div>
+</li>
+<li class="level1"><div class="li"> At this point, you should be able to use ngspice. You can test your installation by trying one of the test circuits held in the tests directory. I recommend running the TransImpedanceAmp test, since it tests the SPICE2 POLY functionality. Information how to use ngspice is provided in the next section below.</div>
+</li>
+<li class="level1"><div class="li"> If you only want to use ngspice, you can stop now. Otherwise, next build tclspice. To build tclspice, you need to have the following other packages already installed:<br/>
+ <br/>
+ * TclX (tclx8.3.5 works for me.)<br/>
+ * tclreadline (tclreadline-2.1.0 works for me.)<br/>
+ * BLT for TCL (blt2.4z works for me.)<br/>
+ <br/>
+ If you donâ??t have these packages already on your Linux box, you need to get them and build them. Note that building TclX requires having the sources for TCL and Tk, so you will also need to get those sources if you donâ??t have them installed already. I am running successfully with TCL/Tk 8.4.3, although 8.3.X versions are also supposed to work.</div>
+</li>
+<li class="level1"><div class="li"> Assuming you have gotten the additional packages mentioned above installed, Do "./configure –enable-xspice –prefix=/usr/local/geda –enable-tcl –enable-experimental –disable-sharedâ?? to configure the Makefiles for tclspice. (If you donâ??t have the additional packages installed correctly , configure will complain and barf, so this step acts as a check on your installation.)</div>
+</li>
+<li class="level1"><div class="li"> Do â??make tcl && make install-tclâ?? to compile and install tclspice.</div>
+</li>
+<li class="level1"><div class="li"> Now you will be ready to write TCL scripts which incorporate SPICE commands. Information about using tclspice is given below.</div>
+</li>
+</ol>
+
+<p>
+ Finally, if you are interested in hacking tclspice (or even if you are not), itâ??s a good idea to read the NOTES file living in the top source directory for a couple of useful pointers.
+</p>
+
+</div>
+
+<h4><a name="use_of_ngspice" id="use_of_ngspice">Use of ngspice</a></h4>
+<div class="level4">
+
+<p>
+Running ngspice is very simple. Just issue the command â??ngspice filename.netâ?? at the unix command prompt, and ngspice will load the SPICE netlist called â??filename.netâ?? into its workspace, and leave you at an ngspice command prompt. You can run the simulator by saying â??runâ??. Your results will be stored in SPICE vectors for later printing or plotting. The command set available to you is documented at <a href="http://newton.ex.ac.uk/teaching/CDHW/Electronics2/userguide/sec5.html#5"; class="urlextern" title="http://newton.ex.ac.uk/teaching/CDHW/Electronics2/userguide/sec5.html#5"; rel="nofollow">http://newton.ex.ac.uk/teaching/CDHW/Electronics2/userguide/sec5.html#5</a>.<br/>
+ To make use of the SPICE2 POLY codemodel, you need to load it into ngspice <strong>before</strong> you load your netlist. (If you load it after loading your netlist, POLYs in your netlist are not translated, and therefore wonâ??t be simulated correctly.) To load the codemodel, just say â??codemodel /usr/local/src/tclspice-0.2.12/src/xspice/icm/spice2poly.cmâ?? at the ngspice prompt. Note that you must provide the <strong>absolute path</strong> to the location of the codemodel; ngspice isnâ??t smart enough to look for it in any default locations. (Also note that you should specify the location where spice2poly.cm lives on your machine; the path above is for mine.)<br/>
+ A better way to read in the spice2poly codemodel is to include it in the ngspice initialization file, â??spinitâ??. The initialization file lives in the directory /usr/local/geda/share/ng-spice-rework/scripts (or where ever you placed your geda installation). Other ngspice customizations may also be placed into the spinit file.
+</p>
+
+</div>
+
+<h4><a name="use_of_tclspice" id="use_of_tclspice">Use of tclspice</a></h4>
+<div class="level4">
+
+<p>
+The tclspice package is a superset of ngspice. Not only does the package include the ngspice interactive environment; tclspice also provides a facility which exports the ngspice command set as TCL commands for inclusion into a TCL script. This is a very powerful tool: With tclspice you can write a TCL script which runs a loop, tweaks component values, runs an analysis, and then evaluates the circuit performance with the tweaked components before looping again. Obviously, this ability can be used to perform automated, multi-dimensional circuit optimization.<br/>
+ To use tclspice, you just need to say â??package require spiceâ?? at the beginning of your TCL program. Thereafter, to invoke a SPICE command, you just call it in the spice namesapce. For example, the following TCL program will read in a SPICE netlist, command a transient analysis, run the simulation, and then plot the voltage observed over time on net Vout:
+</p>
+<pre class="code">#! tclsh
+package require spice
+spice::codemodel /usr/local/src/tclspice-0.2.12/src/xspice/icm/spice2poly.cm
+
+spice::source netlistname.cir
+spice::tran 0.1ns 40ns
+spice::run
+spice::plot Vout
+puts "All done now!"</pre>
+
+<p>
+Note that since tclspice doesnâ??t read the ngspice initialization file â??spinitâ??, you will need to put any initialization commands directly into the TCL program. For example, in the above example we read the spice2poly codemodel directly into the workspace. Many other commands are also available; the entire tclspice commandset is documented at <a href="http://tclspice.sourceforge.net/docs/tclspice_com.html"; class="urlextern" title="http://tclspice.sourceforge.net/docs/tclspice_com.html"; rel="nofollow">http://tclspice.sourceforge.net/docs/tclspice_com.html</a>.<br/>
+ A major problem with tclspice (which was inherited from ngspice) is that it leaks memory. Therefore, the time over which you may run a simulation is limited. This means that if you want to do an optimization by looping through a circuit many, many times, you may run out of memory before your program has completed its optimization. This is a known issue with tclspice, and efforts are underway to plug the leaks.<br/>
+ Meanwhile, there are some workarounds which can be used on moderate-sized designs to facilitate long optimization runs. One method I have employed is to have the optimizer write its current state into a file after every circuit analysis, and read its starting state from the same file. The optimizer also stores the current list of best components in another file, and reads this file at the start of every run. Then, I have a TCL program called TaskMgr.tcl which runs in a loop; at each iteration of the loop it forks a child process to run the optimizer. Meanwhile, the parent process waits for 5 minutes (a heuristically determined time), and then issues a â??KILLâ?? signal to the child before looping and starting the optimizer again. This way, the optimizer never runs long enough to consume all the memory in my machine. The TaskMgr.tcl program is shown here:
+</p>
+<pre class="code">#! tclsh
+package require Tclx
+while {1} {
+
+ set PID [fork]
+ if {$PID} {
+
+ # Parent
+ after 300000
+ puts "About to kill child PID = $PID . . . ."
+ kill $PID
+ wait $PID
+
+ } else {
+
+ # Child
+ source Optimize.tcl
+ # If we ever get through this, we can print out the following:
+ error "We are done now!!!!!!"
+
+ }
+
+}</pre>
+
+<p>
+Note that TaskMgr.tcl needs the TclX package you already installed to run tclspice. Also, you may want to change the wait time to a different value depending upon the memory and speed of your machine. Finally, the parent has to wait on $PID because that causes the child processâ??s corpse to be taken off the Linux kernalâ??s task list when it dies. Otherwise, you will end up with a lot of zombie processes lurking around your machine as the optimizer runs – a long optimization could turn your system into â??the night of the living deadâ??!<br/>
+ This method of waiting a specific amout of time for the child process is preferable if a single analysis run takes a relativly short time compared to the time required to eat all memory in the machine. If the analysis time is comparable to the time taken to eat all memory in the machine, a better approach is to have the parent keep track of the analysis state, kick off a single analysis run, and then have the run terminate after every iteration. Whether this is preferable depends upon the size and complexity of your design; you may want to experiment with your analysis to see just how long it takes and how much memory it consumes. I have found that a design comprised of six op amps (with corresponding vendor models) and 50 or so passives will run in under 10 seconds on a PIII 333MHz with 128MB RAM. Therefore, your design must be very big before a single analysis will eat a significant amount of RAM.
+</p>
+
+</div>
+<!-- SECTION "Ngspice and tclspice" [29364-40393] -->
+<h2><a name="appendix" id="appendix">Appendix</a></h2>
+<div class="level2">
+
+</div>
+<!-- SECTION "Appendix" [40394-40415] -->
+<h3><a name="component_attribute_summary" id="component_attribute_summary">Component attribute summary</a></h3>
+<div class="level3">
+
+<p>
+Native components and their attributes are given in the table below. <strong>Bold faced</strong> attributes are <strong>required</strong>, normal typeface attributes are optional. Note that the â??deviceâ?? attribute is invisible, and is normally attached to the symbol when it is created. The other attributes are attached to the symbol during schematic capture using gschem.
+</p>
+<table class="inline">
+ <tr>
+ <th><strong><code>device</code></strong></th><th><strong><code>refdes</code></strong></th><th><strong><code>value</code></strong></th><th><strong><code>model</code></strong></th><th><strong><code>file</code></strong></th><th><strong><code>model-name</code></strong></th><th><strong><code>type</code></strong></th><th>Comment</th>
+ </tr>
+ <tr>
+ <td><strong>RESISTOR</strong></td><td><strong>R?</strong></td><td><strong>Numeric comp. value</strong></td><td>One line of spice model parameters (e.g. TC)</td><td> </td><td>Name of model.</td><td> </td><td>â??modelâ?? parameters are placed inside parentheses after the component value.</td>
+ </tr>
+ <tr>
+ <td><strong>CAPACITOR</strong></td><td><strong>C?</strong></td><td><strong>Numeric comp. value</strong></td><td>One line of spice model parameters (e.g. IC, POLY, etc.)</td><td> </td><td>Name of model.</td><td> </td><td>â??modelâ?? parameters are placed inside parentheses after the component value.</td>
+ </tr>
+ <tr>
+ <td><strong>POLARIZED_CAPACITOR</strong></td><td><strong>C?</strong></td><td><strong>Numeric comp. value</strong></td><td>One line of spice model parameters (e.g. IC, POLY, etc.)</td><td> </td><td>Name of model.</td><td> </td><td>â??modelâ?? parameters are placed inside parentheses after the component value.</td>
+ </tr>
+ <tr>
+ <td><strong>INDUCTOR</strong></td><td><strong>L?</strong></td><td><strong>Numeric comp. value</strong></td><td>One line of spice model parameters (e.g. IC, POLY, etc.)</td><td> </td><td>Name of model.</td><td> </td><td>â??modelâ?? parameters are placed inside parentheses after the component value.</td>
+ </tr>
+ <tr>
+ <td><strong>SPICE-ccvs</strong></td><td><strong>H?</strong></td><td><strong>String describing source behavior</strong></td><td> </td><td> </td><td> </td><td> </td><td> </td>
+ </tr>
+ <tr>
+ <td><strong>SPICE-cccs</strong></td><td><strong>F?</strong></td><td><strong>String describing source behavior</strong></td><td> </td><td> </td><td> </td><td> </td><td> </td>
+ </tr>
+ <tr>
+ <td><strong>SPICE-vcvs</strong></td><td><strong>E?</strong></td><td><strong>String describing source behavior</strong></td><td> </td><td> </td><td> </td><td> </td><td> </td>
+ </tr>
+ <tr>
+ <td><strong>SPICE-vccs</strong></td><td><strong>G?</strong></td><td><strong>String describing source behavior</strong></td><td> </td><td> </td><td> </td><td> </td><td> </td>
+ </tr>
+ <tr>
+ <td><strong>SPICE-nullor</strong></td><td><strong>E?</strong></td><td><strong>String describing source behavior</strong></td><td> </td><td> </td><td> </td><td> </td><td> </td>
+ </tr>
+ <tr>
+ <td><strong>DIODE</strong></td><td><strong>D?</strong></td><td>Part number</td><td>One line SPICE model.</td><td>Model file name.</td><td><strong>Name of model.</strong></td><td> </td><td>For modeling, one must include either â??modelâ?? or â??fileâ??.</td>
+ </tr>
+ <tr>
+ <td><strong>PMOS_TRANSISTOR</strong></td><td><strong>M?</strong></td><td>Part number</td><td>One line SPICE model.</td><td>Model file name.</td><td><strong>Name of model.</strong></td><td> </td><td>For modeling, one must include either â??modelâ?? or â??fileâ??.</td>
+ </tr>
+ <tr>
+ <td><strong>NMOS_TRANSISTOR</strong></td><td><strong>M?</strong></td><td>Part number</td><td>One line SPICE model.</td><td>Model file name.</td><td><strong>Name of model.</strong></td><td> </td><td>For modeling, one must include either â??modelâ?? or â??fileâ??.</td>
+ </tr>
+ <tr>
+ <td><strong>PNP_TRANSISTOR</strong></td><td><strong>Q?</strong></td><td>Part number</td><td>One line SPICE model.</td><td>Model file name.</td><td><strong>Name of model.</strong></td><td> </td><td>For modeling, one must include either â??modelâ?? or â??fileâ??.</td>
+ </tr>
+ <tr>
+ <td><strong>NPN_TRANSISTOR</strong></td><td><strong>Q?</strong></td><td>Part number</td><td>One line SPICE model.</td><td>Model file name.</td><td><strong>Name of model.</strong></td><td> </td><td>For modeling, one must include either â??modelâ?? or â??fileâ??.</td>
+ </tr>
+ <tr>
+ <td><strong>PFET_TRANSISTOR (JFET)</strong></td><td><strong>J?</strong></td><td>Part number</td><td>One line SPICE model.</td><td>Model file name.</td><td><strong>Name of model.</strong></td><td> </td><td>For modeling, one must include either â??modelâ?? or â??fileâ??.</td>
+ </tr>
+ <tr>
+ <td><strong>NFET_TRANSISTOR (JFET)</strong></td><td><strong>J?</strong></td><td>Part number</td><td>One line SPICE model.</td><td>Model file name.</td><td><strong>Name of model.</strong></td><td> </td><td>For modeling, one must include either â??modelâ?? or â??fileâ??.</td>
+ </tr>
+ <tr>
+ <td><strong>MESFET_TRANSISTOR</strong></td><td><strong>B?</strong></td><td>Part number</td><td>One line SPICE model.</td><td>Model file name.</td><td><strong>Name of model.</strong></td><td> </td><td>For modeling, one must include either â??modelâ?? or â??fileâ??.</td>
+ </tr>
+ <tr>
+ <td><strong>IC</strong></td><td><strong>U?</strong></td><td>Part number</td><td>One line SPICE model.</td><td>Model file name.</td><td><strong>Name of model.</strong></td><td> </td><td>IC with .MODEL file</td>
+ </tr>
+ <tr>
+ <td><strong>IC</strong></td><td><strong>X?</strong></td><td>Part number</td><td> </td><td>Model file name.</td><td><strong>Name of model.</strong></td><td> </td><td>IC with .SUBCKT file</td>
+ </tr>
+ <tr>
+ <td><strong>model</strong></td><td colspan="2"><strong>A?</strong></td><td>One line spice model</td><td>Model file name.</td><td><strong>Name of model pointed to by other components.</strong></td><td><strong>Corresponding SPICE model type (valid types given below)</strong>.</td><td>For modeling, one must include either â??modelâ?? or â??fileâ??.</td>
+ </tr>
+ <tr>
+ <td><strong>include</strong></td><td><strong>A?</strong></td><td> </td><td> </td><td><strong>Include file name.</strong></td><td> </td><td> </td><td>Places .INCLUDE directive in SPICE netlist.</td>
+ </tr>
+ <tr>
+ <td><strong>options</strong></td><td><strong>A?</strong></td><td><strong>Line of options to include.</strong></td><td> </td><td> </td><td> </td><td> </td><td>Places .OPTIONS directive in SPICE netlist.</td>
+ </tr>
+ <tr>
+ <td><strong>directive</strong></td><td><strong>A?</strong></td><td><strong>One line string holding SPICE statements for inclusion in netlist.</strong></td><td> </td><td> </td><td> </td><td> </td><td>For modeling, one must include either â??modelâ?? or â??fileâ??.</td>
+ </tr>
+ <tr>
+ <td><strong>VOLTAGE_SOURCE</strong></td><td><strong>V?</strong></td><td><strong>One line string holding voltage source behavior.</strong></td><td> </td><td> </td><td> </td><td> </td><td>Independent voltage source</td>
+ </tr>
+ <tr>
+ <td><strong>CURRENT_SOURCE</strong></td><td><strong>I?</strong></td><td><strong>One line string holding current source behavior.</strong></td><td> </td><td> </td><td> </td><td> </td><td>Independent current source</td>
+ </tr>
+</table>
+
+<p>
+ â??Native to the netlisterâ?? means that there is a corresponding blob of scheme code which knows exactly how to handle these components and is guaranteed (almost) to generate correct spice code. Symbols having â??deviceâ?? attributes not on the above list are handled using the scheme function â??spice-sdb:write-default-componentâ??, which looks at the refdes of the component to make a decision about how to treat the component. In general, this function will â??do the right thingâ?? when generating spice code, but it is not guaranteed. In particular, this function cannot distinguish between N and P type transistors, and will generate an <unknown> type for the .MODEL string in the netlist. This will probably cause your SPICE simulator to barf. Therefore, it is best to make sure that all devices used have the proper â??deviceâ?? attribute.
+</p>
+
+</div>
+<!-- SECTION "Component attribute summary" [40416-45184] -->
+<h3><a name="valid_type_values" id="valid_type_values">Valid "type" values</a></h3>
+<div class="level3">
+
+<p>
+The â??typeâ?? attribute is a flag signaling the spice engine the component type, and prepares it to accept model parameters specific to that component type. The following values are valid SPICE â??typeâ??s:
+</p>
+<table class="inline">
+ <tr>
+ <th>Component</th><th>â??typeâ??</th><th>Comment</th>
+ </tr>
+ <tr>
+ <td>RESISTOR</td><td>RES</td><td> </td>
+ </tr>
+ <tr>
+ <td>CAPACITOR</td><td>CAP</td><td> </td>
+ </tr>
+ <tr>
+ <td>POLARIZED_CAPACITOR</td><td>CAP</td><td> </td>
+ </tr>
+ <tr>
+ <td>INDUCTOR</td><td>IND</td><td> </td>
+ </tr>
+ <tr>
+ <td>DIODE</td><td>D</td><td> </td>
+ </tr>
+ <tr>
+ <td>PMOS_TRANSISTOR</td><td>PMOS</td><td> </td>
+ </tr>
+ <tr>
+ <td>NMOS_TRANSISTOR</td><td>NMOS</td><td> </td>
+ </tr>
+ <tr>
+ <td>PNP_TRANSISTOR</td><td>PNP</td><td> </td>
+ </tr>
+ <tr>
+ <td>NPN_TRANSISTOR</td><td>NPN</td><td> </td>
+ </tr>
+ <tr>
+ <td>PFET_TRANSISTOR</td><td>PJF</td><td> </td>
+ </tr>
+ <tr>
+ <td>NFET_TRANSISTOR</td><td>NJF</td><td> </td>
+ </tr>
+ <tr>
+ <td>MESFET_TRANSISTOR</td><td> </td><td> </td>
+ </tr>
+</table>
+
+</div>
+<!-- SECTION "Valid type values" [45185-45703] -->
+<h2><a name="document_history" id="document_history">Document History</a></h2>
+<div class="level2">
+<table class="inline">
+ <tr>
+ <td>Revision 1.0</td><td>3.10.2003</td><td>SDB</td><td>Document creation.</td>
+ </tr>
+ <tr>
+ <td>Revision 1.1</td><td>3.19.2003</td><td>SDB</td><td>Added .SUBCKT stuff & stuff about LTSpice</td>
+ </tr>
+ <tr>
+ <td>Revision 1.2</td><td>3.31.2003</td><td>SDB</td><td>Added stuff about creating hierarchical projects (i.e. creating .SUBCKTs using gschem and incorporating a lower level .SUBCKT into a higher level schematic).</td>
+ </tr>
+ <tr>
+ <td>Revision 2.0</td><td>7.23.2003</td><td>SDB</td><td>Split doc into sections. Edited netlisting stuff to correspond to gEDA-20030525, which now includes spice-sdb in the distribution. Added new section about ngspice/tclspice.</td>
+ </tr>
+</table>
+
+<p>
+ The most recent copy of this document is always available at <a href="http://www.brorson.com/gEDA/SPICE/"; class="urlextern" title="http://www.brorson.com/gEDA/SPICE/"; rel="nofollow">http://www.brorson.com/gEDA/SPICE/</a>
+</p>
+
+</div>
+<!-- SECTION "Document History" [45704-] --></body>
+</html>
diff --git a/docs/wiki/geda-sn_readme.html b/docs/wiki/geda-sn_readme.html
new file mode 100644
index 0000000..039f97c
--- /dev/null
+++ b/docs/wiki/geda-sn_readme.html
@@ -0,0 +1,159 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="switcap_netlister_readme" id="switcap_netlister_readme">Switcap netlister README</a></h1>
+<div class="level1">
+<pre class="code">-----------------------------------------------------------------
+I. What is this?
+-----------------------------------------------------------------
+
+This archive contains a set of symbols and a netlister backend for the
+gEDA to drive SWITCAP simulations. gEDA is the GNU EDA project and
+includes a schematic capture tool and a highly flexible netlister.
+The SWITCAP program is a switched capacitor circuit simulator.
+
+-----------------------------------------------------------------
+II. Overview
+-----------------------------------------------------------------
+
+The basic steps involved with using gEDA as the frontend for SWITCAP
+simulations are:
+
+- configure the gEDA symbol search path
+- set the gEDA netlister backend search path
+- create schematics of the circuit
+- create an analysis file
+- extract the netlist
+- run the SWITCAP simulation
+
+
+-----------------------------------------------------------------
+III. Initial Setup
+-----------------------------------------------------------------
+ 1) Set your symbol search path for gschem and gnetlist by adding
+ the following line to the 'gschemrc' and 'gnetlistrc' files in
+ your project directory.
+
+ (component-library "/path/to/sym/switcap")
+
+ If those files do not exist, then create them. You will need to
+ replace /path/to/sym/switcap with the directory name where you
+ have installed the .sym files.
+
+ 2) Set the search path for scheme files for gnetlist by adding the
+ following line to your 'gnetlistrc' file.
+
+ (scheme-directory "/path/to/scheme")
+
+ You will need to replace /path/to/scheme with the path to where
+ you have installed the gnet-switcap.scm file.
+
+ 3)
+
+-----------------------------------------------------------------
+IV. Creating Schematics
+-----------------------------------------------------------------
+
+--------------------
+A. Required Symbols
+--------------------
+
+This section assumes you are familiar with using gschem to create and
+edit schematics. SWITCAP netlisting is only supported for the
+components contained in the SWITCAP symbol library as well as the
+ground symbol found in the 'power' library which comes with gEDA. All
+allowed SWITCAP elements except for subcircuits are supported. You
+_must_ include the following elements on your schematic:
+
+- one instance of the switcap-timing symbol. This symbol will set the
+ master clock period for your simulations.
+
+- one or more instances of the switcap-clock symbol. This symbol
+ defines a clock with a particular phase and period. The reference
+ designator of the clock symbol is used by the switches to set what
+ phase they switch on.
+
+- one or more instances of the switcap-analysis symbol. This symbol
+ defines an analysis by specifying a file to include in the SWITCAP
+ netlist.
+
+--------------------
+B. Optional Symbols
+--------------------
+
+You can also optionally add the following SWITCAP special symbols to
+your schematic:
+
+- zero or one instance of the switcap-title symbol. This will add a
+ TITLE: line to the SWITCAP netlist and will appear in the output
+ file.
+
+- zero or one instance of the switcap-options symbol. By editing the
+ OPTIONS attribute on this symbol you can set the various options
+ which can be passed to SWITCAP.
+
+--------------------
+C. Net Names
+--------------------
+
+When creating schematics to drive SWITCAP, you should name all nets
+that you wish to plot. To avoid possible conflicts with unnamed nets,
+you should avoid using purely numerical names for nets because
+all unnamed nets will be assigned (somewhat randomly) numbers.
+SWITCAP limits the length of node names to 7 characters.
+
+--------------------
+D. Switches
+--------------------
+
+When placing switches on your schematic, you will need to define
+which clock they are controlled with. This is done by setting
+the clock attribute on the switch to the reference designator
+of the clock which should control it.
+
+-----------------------------------------------------------------
+V. Extracting the SWITCAP Netlist
+-----------------------------------------------------------------
+
+To extract the SWITCAP netlist, run
+
+ gnetlist -g switcap -o test.scn file1.sch [file2.sch ...]
+
+For the example file contained in this archive, you can run:
+
+ gnetlist -g switcap -o example.scn ckt.sch clocks.sch analysis.sch
+
+The netlist will be left in example.scn.
+
+-----------------------------------------------------------------
+VI. Running SWITCAP
+-----------------------------------------------------------------
+
+I typically use something like:
+
+ printf "example.scn\nexample.out" | sw
+
+so I can use command history to rerun SWITCAP without having to
+manually type the file names each time.
+
+Refer to the SWITCAP manual for more details.
+
+
+</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-spice_improvements.html b/docs/wiki/geda-spice_improvements.html
new file mode 100644
index 0000000..8451e13
--- /dev/null
+++ b/docs/wiki/geda-spice_improvements.html
@@ -0,0 +1,26 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="spice_simulation_improvements_in_gschem" id="spice_simulation_improvements_in_gschem">Spice simulation improvements in gschem</a></h1>
+<div class="level1">
+
+<p>
+ This page has moved to the more neutral topic <a href="geda-circuit_simulation_improvements.html" class="wikilink1" title="geda-circuit_simulation_improvements.html">circuit_simulation_improvements</a>
+</p>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-ssan.html b/docs/wiki/geda-ssan.html
new file mode 100644
index 0000000..a7e6246
--- /dev/null
+++ b/docs/wiki/geda-ssan.html
@@ -0,0 +1,458 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#geda_gaf_switcap_symbols_and_netlister" class="toc">gEDA/gaf Switcap Symbols and Netlister</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#overview" class="toc">Overview</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#requirements" class="toc">Requirements</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#creating_schematics" class="toc">Creating Schematics</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#required_symbols" class="toc">Required Symbols</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#optional_symbols" class="toc">Optional Symbols</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#net_names" class="toc">Net Names</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#switches" class="toc">Switches</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#extracting_the_switcap_netlist" class="toc">Extracting the SWITCAP Netlist</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#running_switcap" class="toc">Running SWITCAP</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#appendix_a_--_symbols_in_the_library" class="toc">Appendix A -- Symbols in the Library</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#capacitors_switcap-capacitor" class="toc">Capacitors (switcap-capacitor)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#switches_switcap-switch" class="toc">Switches (switcap-switch)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#independent_voltage_sources_switcap-vsrc" class="toc">Independent Voltage Sources (switcap-vsrc)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#dependent_voltage_sources_switcap-vcvs" class="toc">Dependent Voltage Sources (switcap-vcvs)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#clock_specification_switcap-clock" class="toc">Clock Specification (switcap-clock)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#master_timing_specification_switcap-timing" class="toc">Master Timing Specification (switcap-timing)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#analysis_file_include_switcap-analysis" class="toc">Analysis File Include (switcap-analysis)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#simulation_title_specification_switcap-title" class="toc">Simulation Title Specification (switcap-title)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#simulation_options_specification_switcap-options" class="toc">Simulation Options Specification (switcap-options)</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#example" class="toc">Example</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#example_schematics" class="toc">Example Schematics</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#netlist_the_design" class="toc">Netlist the Design</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#run_the_simulation" class="toc">Run the Simulation</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#process_the_results" class="toc">Process the Results</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#plot_the_results" class="toc">Plot the Results</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#document_revision_history" class="toc">Document Revision History</a></span></div></li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="geda_gaf_switcap_symbols_and_netlister" id="geda_gaf_switcap_symbols_and_netlister">gEDA/gaf Switcap Symbols and Netlister</a></h1>
+<div class="level1">
+
+<p>
+by: Dan McMahill
+</p>
+
+<p>
+This document is released under <a href="http://www.gnu.org/copyleft/fdl.html"; class="urlextern" title="http://www.gnu.org/copyleft/fdl.html"; rel="nofollow">GFDL</a>
+</p>
+
+<p>
+April 13th, 2003
+</p>
+
+</div>
+<!-- SECTION "gEDA/gaf Switcap Symbols and Netlister" [1-168] -->
+<h2><a name="overview" id="overview">Overview</a></h2>
+<div class="level2">
+
+<p>
+This document describes the symbol library and gnetlist backend which supports driving SWITCAP simulations from the gEDA/gaf system. SWITCAP is a switched capacitor circuit simulator available from Columbia University. It is used in many classroom and research environments. One drawback to SWITCAP is the lack of a freely available schematic capture frontend. The gEDA/gaf SWITCAP symbol library and gnetlist backend tries to fill that gap.<br/>
+ The basic steps involved with using gEDA as the frontend for SWITCAP simulations are:
+</p>
+<ol>
+<li class="level1"><div class="li"> Create schematics of the circuit.</div>
+</li>
+<li class="level1"><div class="li"> Create an analysis file.</div>
+</li>
+<li class="level1"><div class="li"> Extract the netlist.</div>
+</li>
+<li class="level1"><div class="li"> Run the SWITCAP simulation.</div>
+</li>
+<li class="level1"><div class="li"> Run <strong>sw2asc</strong> to extract the results.</div>
+</li>
+<li class="level1"><div class="li"> View the results with <strong>gwave</strong>.</div>
+</li>
+</ol>
+
+</div>
+<!-- SECTION "Overview" [169-924] -->
+<h2><a name="requirements" id="requirements">Requirements</a></h2>
+<div class="level2">
+
+<p>
+You will need the following programs to be installed:
+</p>
+<ol>
+<li class="level1"><div class="li"> A recent version of gEDA/gaf. To see if your version is recent enough, see if the directory <strong><code>$prefix/share/gEDA/sym/switcap</code></strong> exists. <strong><code>$prefix</code></strong> is the installation prefix for gEDA on your system.</div>
+</li>
+<li class="level1"><div class="li"> SWITCAP. The executable is usually called <strong><code>sw</code></strong>. If you do not have SWITCAP available on your system, you will need to contact Columbia University to obtain a copy. The gEDA/gaf SWITCAP support was tested with SWITCAP Version A.5R Release 21-Sep-87.</div>
+</li>
+<li class="level1"><div class="li"> Although it is optional, you may wish to install a tool which can be used for plotting the output data. SWITCAP produces both <acronym title="American Standard Code for Information Interchange">ASCII</acronym> data listings as well as ugly <acronym title="American Standard Code for Information Interchange">ASCII</acronym> plots (note the release date of the version of SWITCAP used). Suitable tools are:</div>
+<ol>
+<li class="level2"><div class="li"> Gwave. Gwave is an analog waveform viewer. It is fairly basic, but easy to use, includes cursors, and has zoom/pan features. See <strong><a href="http://www.geda.seul.org"; class="urlextern" title="http://www.geda.seul.org"; rel="nofollow">http://www.geda.seul.org</a></strong></div>
+</li>
+<li class="level2"><div class="li"> Scilab. Similar to matlab. Powerful, but no cursors or panning. See <strong><a href="http://www-rocq.inria.fr/scilab"; class="urlextern" title="http://www-rocq.inria.fr/scilab"; rel="nofollow">http://www-rocq.inria.fr/scilab</a></strong></div>
+</li>
+<li class="level2"><div class="li"> Octave. Similar to matlab. See <strong><a href="http://www.octave.org"; class="urlextern" title="http://www.octave.org"; rel="nofollow">http://www.octave.org</a></strong></div>
+</li>
+<li class="level2"><div class="li"> Grace. See <strong><a href="http://plasma-gate.weizmann.ac.il/Grace/"; class="urlextern" title="http://plasma-gate.weizmann.ac.il/Grace/"; rel="nofollow">http://plasma-gate.weizmann.ac.il/Grace/</a></strong></div>
+</li>
+</ol>
+</li>
+</ol>
+
+</div>
+<!-- SECTION "Requirements" [925-2127] -->
+<h2><a name="creating_schematics" id="creating_schematics">Creating Schematics</a></h2>
+<div class="level2">
+
+</div>
+<!-- SECTION "Creating Schematics" [2128-2159] -->
+<h3><a name="required_symbols" id="required_symbols">Required Symbols</a></h3>
+<div class="level3">
+
+<p>
+This section assumes you are familiar with using gschem to create and edit schematics. SWITCAP netlisting is only supported for the components contained in the SWITCAP symbol library as well as the ground symbol found in the â??powerâ?? library which comes with gEDA. All allowed SWITCAP elements except for subcircuits are supported. You <em>must</em> include the following elements on your schematic:
+</p>
+<ol>
+<li class="level1"><div class="li"> One instance of the switcap-timing symbol. This symbol will set the master clock period for your simulations.</div>
+</li>
+<li class="level1"><div class="li"> One or more instances of the switcap-clock symbol. This symbol defines a clock with a particular phase and period. The reference designator of the clock symbol is used by the switches to set what phase they switch on.</div>
+</li>
+<li class="level1"><div class="li"> One or more instances of the switcap-analysis symbol. This symbol defines an analysis by specifying a file to include in the SWITCAP netlist. By including multiple instances of this symbol, multiple analysis files may be included.</div>
+</li>
+</ol>
+
+</div>
+<!-- SECTION "Required Symbols" [2160-3152] -->
+<h3><a name="optional_symbols" id="optional_symbols">Optional Symbols</a></h3>
+<div class="level3">
+
+<p>
+You can also optionally add the following SWITCAP special symbols to your schematic:
+</p>
+<ol>
+<li class="level1"><div class="li"> Zero or one instance of the switcap-title symbol. This will add a TITLE: line to the SWITCAP netlist and will appear in the output file.</div>
+</li>
+<li class="level1"><div class="li"> Zero or one instance of the switcap-options symbol. By editing the OPTIONS attribute on this symbol you can set the various options which can be passed to SWITCAP.</div>
+</li>
+</ol>
+
+</div>
+<!-- SECTION "Optional Symbols" [3153-3574] -->
+<h3><a name="net_names" id="net_names">Net Names</a></h3>
+<div class="level3">
+
+<p>
+When creating schematics to drive SWITCAP, you should name all nets that you wish to plot. To avoid possible conflicts with unnamed nets, you should avoid using purely numerical names for nets because all unnamed nets will be assigned (somewhat randomly) numbers without checking for possible conflicts with explicitly named nets. SWITCAP limits the length of node names to 7 characters.
+</p>
+
+</div>
+<!-- SECTION "Net Names" [3575-3983] -->
+<h3><a name="switches" id="switches">Switches</a></h3>
+<div class="level3">
+
+<p>
+When placing switches on your schematic, you will need to define which clock they are controlled with. This is done by setting the clock attribute on the switch to the reference designator of the clock which should control it.
+</p>
+
+</div>
+<!-- SECTION "Switches" [3984-4230] -->
+<h2><a name="extracting_the_switcap_netlist" id="extracting_the_switcap_netlist">Extracting the SWITCAP Netlist</a></h2>
+<div class="level2">
+
+<p>
+To extract the SWITCAP netlist, run:
+</p>
+<pre class="code">gnetlist -g switcap -o test.scn file1.sch [file2.sch ...]</pre>
+
+<p>
+For the example file contained in this archive, you can run:
+</p>
+<pre class="code">gnetlist -g switcap -o example.scn ckt.sch clocks.sch analysis.sch</pre>
+
+<p>
+The netlist will be left in <strong>example.scn</strong>.
+</p>
+
+</div>
+<!-- SECTION "Extracting the SWITCAP Netlist" [4231-4570] -->
+<h2><a name="running_switcap" id="running_switcap">Running SWITCAP</a></h2>
+<div class="level2">
+
+<p>
+I typically use something like:
+</p>
+<pre class="code">printf "example.scn\nexample.out\n" | sw</pre>
+
+<p>
+so I can use command history to rerun SWITCAP without having to manually type the file names each time.<br/>
+ Refer to the SWITCAP manual for more details.
+</p>
+
+</div>
+<!-- SECTION "Running SWITCAP" [4571-4838] -->
+<h2><a name="appendix_a_--_symbols_in_the_library" id="appendix_a_--_symbols_in_the_library">Appendix A -- Symbols in the Library</a></h2>
+<div class="level2">
+
+</div>
+<!-- SECTION "Appendix A -- Symbols in the Library" [4839-4887] -->
+<h3><a name="capacitors_switcap-capacitor" id="capacitors_switcap-capacitor">Capacitors (switcap-capacitor)</a></h3>
+<div class="level3">
+
+<p>
+Ideal capacitor. Attributes:
+</p>
+<ul>
+<li class="level1"><div class="li"> <strong>C</strong>=capacitance. Required. Specifies filename to be included.</div>
+</li>
+<li class="level1"><div class="li"> <strong>refdes</strong>=reference designator. Required. Must start with â??Câ?? and be unique.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Capacitors (switcap-capacitor)" [4888-5108] -->
+<h3><a name="switches_switcap-switch" id="switches_switcap-switch">Switches (switcap-switch)</a></h3>
+<div class="level3">
+
+<p>
+Ideal switch. Attributes:
+</p>
+<ul>
+<li class="level1"><div class="li"> <strong>clock</strong>=Controlling clock. Required. Specifies which clock controls this switch.</div>
+</li>
+<li class="level1"><div class="li"> <strong>refdes</strong>=reference designator. Required. Must start with â??Sâ?? and be unique.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Switches (switcap-switch)" [5109-5340] -->
+<h3><a name="independent_voltage_sources_switcap-vsrc" id="independent_voltage_sources_switcap-vsrc">Independent Voltage Sources (switcap-vsrc)</a></h3>
+<div class="level3">
+
+<p>
+Attributes:
+</p>
+<ul>
+<li class="level1"><div class="li"> <strong>refdes</strong>=reference designator. Required. Must start with â??Vâ?? and be unique.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Independent Voltage Sources (switcap-vsrc)" [5341-5488] -->
+<h3><a name="dependent_voltage_sources_switcap-vcvs" id="dependent_voltage_sources_switcap-vcvs">Dependent Voltage Sources (switcap-vcvs)</a></h3>
+<div class="level3">
+
+<p>
+Attributes:
+</p>
+<ul>
+<li class="level1"><div class="li"> <strong>gain</strong>=gain. Required. Specifies the gain of the controlled source.</div>
+</li>
+<li class="level1"><div class="li"> <strong>refdes</strong>=reference designator. Required. Must start with â??Eâ?? and be unique.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Dependent Voltage Sources (switcap-vcvs)" [5489-5708] -->
+<h3><a name="clock_specification_switcap-clock" id="clock_specification_switcap-clock">Clock Specification (switcap-clock)</a></h3>
+<div class="level3">
+
+<p>
+Attributes:
+</p>
+<ul>
+<li class="level1"><div class="li"> <strong>PSTART</strong>=starting clock phase. Required. Specifies on what phase of the master clock this clock turns on.</div>
+</li>
+<li class="level1"><div class="li"> <strong>PSTOP</strong>=ending clock phase. Required. Specifies on what phase of the master clock this clock turns off.</div>
+</li>
+<li class="level1"><div class="li"> <strong>PERIOD</strong>=clock period. Required. Specifies the period of the clock in terms of master clock cycles.</div>
+</li>
+<li class="level1"><div class="li"> <strong>refdes</strong>=reference designator. Required. The switches that are controlled by this clock will refer to it by the reference designator. As such, avoid running any reference designator renumbering tools.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Clock Specification (switcap-clock)" [5709-6302] -->
+<h3><a name="master_timing_specification_switcap-timing" id="master_timing_specification_switcap-timing">Master Timing Specification (switcap-timing)</a></h3>
+<div class="level3">
+
+<p>
+Attributes:
+</p>
+<ul>
+<li class="level1"><div class="li"> PERIOD=clock period. Required. Specifies the period of the master clock in seconds.</div>
+</li>
+</ul>
+
+<p>
+ Only a single instance of this symbol is allowed.
+</p>
+
+</div>
+<!-- SECTION "Master Timing Specification (switcap-timing)" [6303-6509] -->
+<h3><a name="analysis_file_include_switcap-analysis" id="analysis_file_include_switcap-analysis">Analysis File Include (switcap-analysis)</a></h3>
+<div class="level3">
+
+<p>
+This symbol will cause a specified file containing SWITCAP analysis commands to be included in the output netlist. Attributes:
+</p>
+<ul>
+<li class="level1"><div class="li"> <strong>file</strong>=filename. Required. Specifies filename to be included.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Analysis File Include (switcap-analysis)" [6510-6756] -->
+<h3><a name="simulation_title_specification_switcap-title" id="simulation_title_specification_switcap-title">Simulation Title Specification (switcap-title)</a></h3>
+<div class="level3">
+
+<p>
+Attributes:
+</p>
+<ul>
+<li class="level1"><div class="li"> <strong>TITLE</strong>=switcap title. Required. Specifies the TITLE line for the SWITCAP netlist.</div>
+</li>
+</ul>
+
+<p>
+ Only a single instance of this symbol is allowed.
+</p>
+
+</div>
+<!-- SECTION "Simulation Title Specification (switcap-title)" [6757-6966] -->
+<h3><a name="simulation_options_specification_switcap-options" id="simulation_options_specification_switcap-options">Simulation Options Specification (switcap-options)</a></h3>
+<div class="level3">
+
+<p>
+Attributes:
+</p>
+<ul>
+<li class="level1"><div class="li"> <strong>OPTIONS</strong>=switcap options. Required. Specifies the OPTIONS line for the SWITCAP netlist. See the SWITCAP manual for allowed values.</div>
+</li>
+</ul>
+
+<p>
+ Only a single instance of this symbol is allowed.
+</p>
+
+</div>
+<!-- SECTION "Simulation Options Specification (switcap-options)" [6967-7229] -->
+<h2><a name="example" id="example">Example</a></h2>
+<div class="level2">
+
+<p>
+This appendix provides a simple example of the entire process of generating a schematic, producing a SWITCAP netlist, running a simulation, and plotting the results.
+</p>
+<table class="inline">
+ <tr>
+ <td> <a href="media/geda/switcap_figure1.jpg" class="media" target="_blank" title="geda:switcap_figure1.jpg"><img src="media/geda/switcap_figure1.jpg" class="media" alt="" /></a> </td>
+ </tr>
+ <tr>
+ <td> <a href="media/geda/switcap_figure2.jpg" class="media" target="_blank" title="geda:switcap_figure2.jpg"><img src="media/geda/switcap_figure2.jpg" class="media" alt="" /></a> </td>
+ </tr>
+ <tr>
+ <td> <a href="media/geda/switcap_figure3.jpg" class="media" target="_blank" title="geda:switcap_figure3.jpg"><img src="media/geda/switcap_figure3.jpg" class="media" alt="" /></a> </td>
+ </tr>
+ <tr>
+ <td> <a href="media/geda/switcap_figure4.jpg" class="media" target="_blank" title="geda:switcap_figure4.jpg"><img src="media/geda/switcap_figure4.jpg" class="media" alt="" /></a> </td>
+ </tr>
+</table>
+
+<p>
+ Figure 5/6: Simulation Results - Transient MISSING
+</p>
+
+</div>
+<!-- SECTION "Example" [7230-7605] -->
+<h3><a name="example_schematics" id="example_schematics">Example Schematics</a></h3>
+<div class="level3">
+
+<p>
+<strong>Figure 1</strong> shows the schematic of a simple switched capacitor circuit. Note that some switches, S1 and S3 for example, are controlled by CLK1 while others, S2 and S4 for example, are controlled by the complement of CLK1 (#CLK1).<br/>
+ <strong>Figure 2</strong> shows the definition of a clock and the master clock. Here we define a master clock period (mcp) of 1.0 μs in the timing block. In the clock definition symbol, we define a clock called CLK1 that has a period equal to 1 master clock period (mcp). The phase of CLK1 turning on switches is 0 and the phase of CLK1 turning off switches is 3/8 mcp. Additional clock phases can be defined by creating more instances of the clock definition symbol.<br/>
+ <strong>Figure 3</strong> shows an instantiation of the title block symbol which will cause â??my titleâ?? to be used in the TITLE line in the SWITCAP netlist. Figure 3 also shows an instantiation of an analysis block which directs the netlister to include the contents of the file test.ana in the output netlist. <strong>Figure 4</strong> shows the contents of the test.ana file.
+</p>
+
+</div>
+<!-- SECTION "Example Schematics" [7606-8677] -->
+<h3><a name="netlist_the_design" id="netlist_the_design">Netlist the Design</a></h3>
+<div class="level3">
+
+<p>
+To netlist the design, run:
+</p>
+<pre class="code">gnetlist -g switcap -o example.scn ckt.sch clocks.sch analysis.sch</pre>
+
+</div>
+<!-- SECTION "Netlist the Design" [8678-8815] -->
+<h3><a name="run_the_simulation" id="run_the_simulation">Run the Simulation</a></h3>
+<div class="level3">
+
+<p>
+Run the simulation with:
+</p>
+<pre class="code">printf "example.scn\nexample.out\n" | sw</pre>
+
+</div>
+<!-- SECTION "Run the Simulation" [8816-8924] -->
+<h3><a name="process_the_results" id="process_the_results">Process the Results</a></h3>
+<div class="level3">
+
+<p>
+Convert the SWITCAP output file to something gwave can read by running:
+</p>
+<pre class="code">sw2asc example.out</pre>
+
+</div>
+<!-- SECTION "Process the Results" [8925-9059] -->
+<h3><a name="plot_the_results" id="plot_the_results">Plot the Results</a></h3>
+<div class="level3">
+
+<p>
+Start up the gwave program and load the first sinusoidal steady state result by running:
+</p>
+<pre class="code">gwave example.out.SSS.1.asc</pre>
+
+<p>
+Drag the two waveforms onto the two waveform panels and change the x-axis to a log scale. Figure 5 shows the output. Start up the gwave program and load the transient result by running:
+</p>
+<pre class="code">gwave example.out.TRAN.1.asc</pre>
+
+</div>
+<!-- SECTION "Plot the Results" [9060-9446] -->
+<h2><a name="document_revision_history" id="document_revision_history">Document Revision History</a></h2>
+<div class="level2">
+<table class="inline">
+ <tr>
+ <td> April 13th, 2003 </td><td> Created switcap.tex </td>
+ </tr>
+</table>
+
+</div>
+<!-- SECTION "Document Revision History" [9447-] --></body>
+</html>
diff --git a/docs/wiki/geda-start.html b/docs/wiki/geda-start.html
new file mode 100644
index 0000000..483bd45
--- /dev/null
+++ b/docs/wiki/geda-start.html
@@ -0,0 +1,23 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+<p>
+ This is just a placeholder page.
+</p>
+
+<p>
+You probably want <a href="http://geda.seul.org/wiki"; class="urlextern" title="http://geda.seul.org/wiki"; rel="nofollow"> main wiki page </a> or <a href="geda-documentation.html" class="wikilink1" title="geda-documentation.html">documentation</a>
+</p>
+</body>
+</html>
diff --git a/docs/wiki/geda-style_guide.html b/docs/wiki/geda-style_guide.html
new file mode 100644
index 0000000..37b05b7
--- /dev/null
+++ b/docs/wiki/geda-style_guide.html
@@ -0,0 +1,156 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#style_guide" class="toc">Style Guide</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#downloading_installing_pavuk" class="toc">Downloading/Installing pavuk</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#downloading_installing_htmldoc" class="toc">Downloading/Installing HTMLDOC</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#for_both_existing_and_new_documents" class="toc">For both existing and new documents</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#for_new_documents" class="toc">For new documents:</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#for_existing_documents" class="toc">For existing documents:</a></span></div></li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="style_guide" id="style_guide">Style Guide</a></h1>
+<div class="level1">
+
+<p>
+<span class="hilited">This is definitely a work in progress.</span><br/>
+ All documentation is eventually going to be made available as both <acronym title="HyperText Markup Language">HTML</acronym> and <acronym title="Portable Document Format">PDF</acronym>.<br/>
+ The problem is to convert the gEDA wikiâ??s Dokuwiki-pages (i.e., <acronym title="Extensible HyperText Markup Language">XHTML</acronym>) into a format that can be converted into <acronym title="Portable Document Format">PDF</acronym>.<br/>
+ The ideal path would be to use the pavuk application to mine the gEDA wiki, converting the <acronym title="Extensible HyperText Markup Language">XHTML</acronym> wiki-pages into <acronym title="HyperText Markup Language">HTML</acronym> pages, and then use the HTMLDOC application to convert the <acronym title="HyperText Markup Language">HTML</acronym> pages to <acronym title="Portable Document Format">PDF</acronym>.<br/>
+
+</p>
+
+</div>
+<!-- SECTION "Style Guide" [1-472] -->
+<h2><a name="downloading_installing_pavuk" id="downloading_installing_pavuk">Downloading/Installing pavuk</a></h2>
+<div class="level2">
+
+<p>
+pavuk is a function-testing, performance-measuring, site-mirroring, web spider that is widely portable and capable of using scenarios to process a wide range of web transactions, including ssl and forms.<br/>
+ pavuk is hosted on SourceForge at <a href="http://sourceforge.net/projects/pavuk"; class="urlextern" title="http://sourceforge.net/projects/pavuk"; rel="nofollow">http://sourceforge.net/projects/pavuk</a>. Simply check if your distribution already includes the latest version of pavuk (pavuk-0.9.34 used for the current wiki), and download/install if necessary.<br/>
+ pavuk comes as an RPM, a tar-ball, and a compressed tar-ball. Donâ??t install from the RPM, as this uses dated library dependencies and may not build on newer distributions.<br/>
+ pavuk has both a command-line interface and a <acronym title="Graphical User Interface">GUI</acronym> interface.
+</p>
+
+</div>
+<!-- SECTION "Downloading/Installing pavuk" [473-1190] -->
+<h2><a name="downloading_installing_htmldoc" id="downloading_installing_htmldoc">Downloading/Installing HTMLDOC</a></h2>
+<div class="level2">
+
+<p>
+HTMLDOC converts <acronym title="HyperText Markup Language">HTML</acronym> files and web pages into indexed <acronym title="HyperText Markup Language">HTML</acronym>, PostScript, and <acronym title="Portable Document Format">PDF</acronym> files suitable for on-line viewing and printing.<br/>
+ HTMLDOC is hosted at <a href="http://www.easysw.com/htmldoc/"; class="urlextern" title="http://www.easysw.com/htmldoc/"; rel="nofollow">http://www.easysw.com/htmldoc/</a>, and may be downloaded/installed under the open-source license for non-commercial applications. Simply check if you distribution already includes HTMLDOC version htmldoc-1.8-27 or later, and install as appropriate. Note that RPM distributions are available, so that your normal package install/update utilities may already contain HTMLDOC (e.g., htmldoc-1.8.27 is in Fedora Core 4 extras repository and may be installed using yum).<br/>
+ HTMLDOC version htmldoc-1.8.26 is broken, it will not generate appropriate <acronym title="Portable Document Format">PDF</acronym> documents.<br/>
+ Note one limitation of HTMLDOC. It is based on <acronym title="HyperText Markup Language">HTML</acronym> 3.o, not <acronym title="HyperText Markup Language">HTML</acronym> 4.01. Many <acronym title="HyperText Markup Language">HTML</acronym> 4.01 tags are not recognized by HTMLDOC.<br/>
+ HTMLDOC is both a <acronym title="Graphical User Interface">GUI</acronym> application and a command-line application. Use it as you feel most comfortable.
+</p>
+
+</div>
+<!-- SECTION "Downloading/Installing HTMLDOC" [1191-2172] -->
+<h2><a name="for_both_existing_and_new_documents" id="for_both_existing_and_new_documents">For both existing and new documents</a></h2>
+<div class="level2">
+
+<p>
+The following are meant to stimulate discussion on document style:
+</p>
+<ol>
+<li class="level1"><div class="li"> Consider that the document will be exported for inclusion on the â??gEDA Tools Suite CD-ROMâ?? as <acronym title="Extensible HyperText Markup Language">XHTML</acronym> and/or <acronym title="Portable Document Format">PDF</acronym>. Examples:</div>
+<ul>
+<li class="level2"><div class="li"> <a href="http://geda.seul.org/wiki/?do=export_raw"; class="urlextern" title="http://geda.seul.org/wiki/?do=export_raw"; rel="nofollow">http://geda.seul.org/wiki/?do=export_raw</a> will generate the gEDA Project Wikiâ??s start page as plain text. Simply use your browser to copy to a text file and include on the CD-ROM image.</div>
+</li>
+<li class="level2"><div class="li"> <a href="http://geda.seul.org/wiki/?do=export_xhtml"; class="urlextern" title="http://geda.seul.org/wiki/?do=export_xhtml"; rel="nofollow">http://geda.seul.org/wiki/?do=export_xhtml</a> will generate the gEDA Project Wikiâ??s start page as valid <acronym title="Extensible HyperText Markup Language">XHTML</acronym>. Simply use your browser to â??Save Page As…â??, and name the file {filename}.html. Note that the URLs in this file are NOT relative to this file, but are as they would be found on the gEDA Project Wiki.</div>
+</li>
+<li class="level2"><div class="li"> <a href="http://geda.seul.org/wiki/?do=export_xhtmlbody"; class="urlextern" title="http://geda.seul.org/wiki/?do=export_xhtmlbody"; rel="nofollow">http://geda.seul.org/wiki/?do=export_xhtmlbody</a> will generate the gEDA Project Wikiâ??s start page as valid rendered <acronym title="Extensible HyperText Markup Language">XHTML</acronym>. Simply use your browser to â??Save Page As…â??, and name the file {filename}.html. Note that the URLs in this file are NOT relative to this file, but are as they would be found on the gEDA Project Wiki.</div>
+</li>
+<li class="level2"><div class="li"> The following sequence of commands will retreive a gEDA Project Wiki page (for a list of the gEDA Project Wikiâ??s pages, use the Index button at the bottom of the page) from the â??gedaâ?? namespace (when new wiki-pages are created, we <em class="u">explicitly</em> create them in the â??gedaâ?? namespace) and convert that page into a <acronym title="Portable Document Format">PDF</acronym> document:<br/>
+ <pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">% wget --convert-links -O {page-name}.wget "http://geda.seul.org/wiki/geda:{page-name}?do=export_html"
+% sed -e 's/\&amp;/\&/g' {page-name}.wget > {page-name}.sed
+% iconv -f utf-8 -t iso-8859-1 {page-name}.sed > {page-name}.iconv
+% htmldoc {page-name}.iconv -t pdf14 --webpage --no-title --linkstyle underline --size letter --left 1.00in \\
+ --right 0.50in --top 0.50in --bottom 0.50in --header .t. --footer . --nup 1 --tocheader .t. --tocfooter ..i \\
+ --portrait --color --no-pscommands --no-xrxcomments --compression=1 --jpeg=0 --fontsize 11.0 --fontspacing 1.2 \\
+ --headingfont Helvetica --bodyfont Times --headfootsize 11.0 --headfootfont Helvetica --charset iso-8859-1 \\
+ --links --no-embedfonts --pagemode document --pagelayout single --firstpage p1 --pageeffect none \\
+ --pageduration 10 --effectduration 1.0 --no-encryption --permissions all --owner-password ""
+ --user-password "" --browserwidth 680 -f {page-name}.pdf</font></pre> <br/>
+ where <strong><code>{page-name}</code></strong> is the wikiâ??s page name as seen in the upper-left corner of the wiki.</div>
+</li>
+</ul>
+</li>
+</ol>
+
+<p>
+ For example, you would replace {page-name} above with the following for the related wiki-page:
+</p>
+<ul>
+<li class="level1"><div class="li"> start – The wikiâ??s main page, at <a href="http://geda.seul.org/wiki/"; class="urlextern" title="http://geda.seul.org/wiki/"; rel="nofollow">http://geda.seul.org/wiki/</a>.</div>
+</li>
+<li class="level1"><div class="li"> geda:style_guide – This wiki-page, at <a href="http://geda.seul.org/wiki/geda:style_guide"; class="urlextern" title="http://geda.seul.org/wiki/geda:style_guide"; rel="nofollow">http://geda.seul.org/wiki/geda:style_guide</a>.</div>
+</li>
+<li class="level1"><div class="li"> geda:faq – The wikiâ??s <acronym title="Frequently Asked Questions">FAQ</acronym> page, at <a href="http://geda.seul.org/wiki/geda:faq"; class="urlextern" title="http://geda.seul.org/wiki/geda:faq"; rel="nofollow">http://geda.seul.org/wiki/geda:faq</a></div>
+</li>
+</ul>
+
+<p>
+ A <span class="hilited">sample script</span> to convert a single wiki-page into a <acronym title="Portable Document Format">PDF</acronym> document.<br/>
+ A <span class="hilited">sample script</span> to convert multiple wiki-pages into a single <acronym title="Portable Document Format">PDF</acronym> document.
+</p>
+
+<p>
+An example of the current (as of 08 May 2006) version of the Wiki, <a href="http://www.offramp.com/wiki/FC5_files/Wiki.pdf"; class="urlextern" title="http://www.offramp.com/wiki/FC5_files/Wiki.pdf"; rel="nofollow">converted to PDF</a>.
+</p>
+
+</div>
+<!-- SECTION "For both existing and new documents" [2173-5272] -->
+<h2><a name="for_new_documents" id="for_new_documents">For new documents:</a></h2>
+<div class="level2">
+
+<p>
+The following are meant to stimulate discussion on document style:
+</p>
+<ol>
+<li class="level1"><div class="li"> You must â??ownâ?? all content in the document. If you do not â??ownâ?? the content, you must get explicit permission from the â??ownerâ?? to copy the content to the gEDA Project Wiki (see below). Documents on the gEDA Project Wiki should be stand-alone, in the event the source document web-site disappears.</div>
+</li>
+<li class="level1"><div class="li"> <strong>All</strong> document contents are to be hosted on the gEDA Project Wiki. Images and other media files are to be uploaded to the wiki, and linked to. Do NOT link to external sites unless absolutely necessary.</div>
+</li>
+<li class="level1"><div class="li"> All documents are to be maintained in the â??gedaâ?? <a href="http://wiki.splitbrain.org/wiki:namespaces"; class="urlextern" title="http://wiki.splitbrain.org/wiki:namespaces"; rel="nofollow">namespace</a>. If your document would take advantage of a separate namespace, ask Ales if â??geda:sub-namespaceâ?? is acceptable. This would be appropriate for very large documents with multiple chapters and lots of images. Such a namespace structure would allow the document to be â??brokenâ?? into chapters for easier navigation by the user (see <a href="http://wiki.splitbrain.org/wiki:index"; class="urlextern" title="http://wiki.splitbrain.org/wiki:index"; rel="nofollow">Index</a> for more details).</div>
+</li>
+</ol>
+
+</div>
+<!-- SECTION "For new documents:" [5273-6383] -->
+<h2><a name="for_existing_documents" id="for_existing_documents">For existing documents:</a></h2>
+<div class="level2">
+
+<p>
+The following are meant to stimulate discussion on document style:
+</p>
+<ol>
+<li class="level1"><div class="li"> </div>
+</li>
+</ol>
+
+</div>
+<!-- SECTION "For existing documents:" [6384-] --></body>
+</html>
diff --git a/docs/wiki/geda-suse_10.0.html b/docs/wiki/geda-suse_10.0.html
new file mode 100644
index 0000000..8559155
--- /dev/null
+++ b/docs/wiki/geda-suse_10.0.html
@@ -0,0 +1,73 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="suse_10.0_install_notes" id="suse_10.0_install_notes">Suse 10.0 install notes</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "Suse 10.0 install notes" [1-39] -->
+<h2><a name="prerequisites" id="prerequisites">Prerequisites:</a></h2>
+<div class="level2">
+
+<p>
+First off, I suggest you use the installer with date code 20051203 (or later). The 2005080X installer may not work with SuSE-10.0 without major upfront preparation.
+</p>
+
+<p>
+Secondly, if you are installing gEDA onto a pre-existing SuSE system, make sure your system runs the Gnome desktop, or at least has the Gnome libraries installed. If you have a KDE desktop system, unpredictable things may happen with the installer.
+</p>
+
+<p>
+The remainder of these instructions describe how to build your SuSE system so that you may install gEDA. If you already have gEDA built (and itâ??s a Gnome desktop), you can use YaST to install any of the below-mentioned packages you might be missing from your original install.
+</p>
+
+<p>
+When installing SuSE-10.0 using YaST, click on the â??changeâ?? button when YaST shows you your configuration. Select â??softwareâ?? â?? â??detailsâ??. Then add the following packages to your installation list:
+</p>
+<ul>
+<li class="level1"><div class="li"> C/C++ tools</div>
+</li>
+<li class="level1"><div class="li"> Kernal development</div>
+</li>
+<li class="level1"><div class="li"> Gnome development</div>
+</li>
+<li class="level1"><div class="li"> KDE development</div>
+</li>
+<li class="level1"><div class="li"> TCL/Tk development</div>
+</li>
+</ul>
+
+<p>
+ Then change the filter to search for and install the following packages:
+</p>
+<ul>
+<li class="level1"><div class="li"> Gtk-devel</div>
+</li>
+<li class="level1"><div class="li"> Termcap</div>
+</li>
+<li class="level1"><div class="li"> Ncurses-devel</div>
+</li>
+<li class="level1"><div class="li"> wxGTK-devel</div>
+</li>
+</ul>
+
+<p>
+ Once these packages are installed, the installer should run to completion.
+</p>
+
+</div>
+<!-- SECTION "Prerequisites:" [40-] --></body>
+</html>
diff --git a/docs/wiki/geda-suse_10.1.html b/docs/wiki/geda-suse_10.1.html
new file mode 100644
index 0000000..7605d8a
--- /dev/null
+++ b/docs/wiki/geda-suse_10.1.html
@@ -0,0 +1,49 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="suse_10.1_install_notes" id="suse_10.1_install_notes">Suse 10.1 install notes</a></h1>
+<div class="level1">
+
+<p>
+These notes pertain to the latest gEDA CD install (20060825).
+</p>
+
+</div>
+<!-- SECTION "Suse 10.1 install notes" [1-101] -->
+<h2><a name="prerequisites" id="prerequisites">Prerequisites:</a></h2>
+<div class="level2">
+
+<p>
+If you are installing gEDA onto a pre-existing SuSE system, make sure your system runs the Gnome desktop, or at least has the Gnome libraries installed. If you have a KDE desktop system, unpredictable things may happen with the installer.
+</p>
+
+<p>
+When installing SuSE-10.1, click on the â??changeâ?? button when YaST shows you your configuration. Select â??softwareâ?? â?? â??detailsâ??. Then add the following packages to your installation list:
+</p>
+<ul>
+<li class="level1"><div class="li"> C/C++ tools</div>
+</li>
+<li class="level1"><div class="li"> Gnome development</div>
+</li>
+</ul>
+
+<p>
+ Once these packages are installed, the installer should run to completion. You <strong>will</strong> need to let the installer become root to install gd-devel as well as WxGTK. If you donâ??t want to do this, then install gd-devel and WxGTK manually before running the installer.
+</p>
+
+</div>
+<!-- SECTION "Prerequisites:" [102-] --></body>
+</html>
diff --git a/docs/wiki/geda-suse_9.3.html b/docs/wiki/geda-suse_9.3.html
new file mode 100644
index 0000000..c0c8ce8
--- /dev/null
+++ b/docs/wiki/geda-suse_9.3.html
@@ -0,0 +1,65 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="installer_2005080x_on_suse_9.3_install_notes" id="installer_2005080x_on_suse_9.3_install_notes">Installer 2005080X on Suse 9.3 install notes</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "Installer 2005080X on Suse 9.3 install notes" [1-59] -->
+<h2><a name="prerequisites" id="prerequisites">Prerequisites:</a></h2>
+<div class="level2">
+
+<p>
+When installing SuSE using YaST, click on the â??changeâ?? button when YaST shows you your configuration. Select â??softwareâ?? â?? â??detailsâ??. Then add the following packages to your installation list:
+</p>
+<ul>
+<li class="level1"><div class="li"> C/C++ tools</div>
+</li>
+<li class="level1"><div class="li"> Kernal development</div>
+</li>
+<li class="level1"><div class="li"> Gnome development</div>
+</li>
+<li class="level1"><div class="li"> KDE development</div>
+</li>
+<li class="level1"><div class="li"> TCL/Tk development</div>
+</li>
+</ul>
+
+<p>
+ Then change the filter to search for and install the following packages:
+</p>
+<ul>
+<li class="level1"><div class="li"> Gtk-devel</div>
+</li>
+<li class="level1"><div class="li"> Termcap</div>
+</li>
+<li class="level1"><div class="li"> Ncurses-devel</div>
+</li>
+<li class="level1"><div class="li"> wxGTK-devel</div>
+</li>
+</ul>
+
+<p>
+ Once these packages are installed, the installer should run to completion.
+</p>
+
+<p>
+<span class="hilited">More SuSE info to come. . . . .</span>
+</p>
+
+</div>
+<!-- SECTION "Prerequisites:" [60-] --></body>
+</html>
diff --git a/docs/wiki/geda-suse_rpm_installation.html b/docs/wiki/geda-suse_rpm_installation.html
new file mode 100644
index 0000000..09f0df5
--- /dev/null
+++ b/docs/wiki/geda-suse_rpm_installation.html
@@ -0,0 +1,254 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#installing_geda_rpm_packages_on_suse" class="toc">Installing gEDA rpm packages on SuSE</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#available_rpm_packages" class="toc">Available rpm packages</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#installing_packages_from_the_suse_build_service" class="toc">Installing Packages from the SuSE Build Service</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>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#opensuse_10.2" class="toc">openSUSE 10.2</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#opensuse_10.3" class="toc">openSUSE 10.3</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#opensuse_11.0" class="toc">openSUSE 11.0</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#opensuse_11.1" class="toc">openSUSE 11.1</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#desktop_integration" class="toc">Desktop Integration</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#electronics_menu" class="toc">Electronics Menu</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#notes_about_rpm_spec_file" class="toc">Notes about rpm spec file</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#installing_rpm_packages_manually" class="toc">Installing rpm packages manually</a></span></div></li></ul>
+</li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="installing_geda_rpm_packages_on_suse" id="installing_geda_rpm_packages_on_suse">Installing gEDA rpm packages on SuSE</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "Installing gEDA rpm packages on SuSE" [1-54] -->
+<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"> geda (1.4.3)</div>
+</li>
+<li class="level1"><div class="li"> gerbv (2.2.0)</div>
+</li>
+<li class="level1"><div class="li"> pcb (20081128)</div>
+</li>
+<li class="level1"><div class="li"> ng-spice-rework (18)</div>
+</li>
+<li class="level1"><div class="li"> gnucap (0.35)</div>
+</li>
+<li class="level1"><div class="li"> gspiceui (0.9.65)</div>
+</li>
+<li class="level1"><div class="li"> gwave (20090114)</div>
+</li>
+<li class="level1"><div class="li"> gtkwave (3.1.10)</div>
+</li>
+<li class="level1"><div class="li"> dinotrace (9.3f)</div>
+</li>
+<li class="level1"><div class="li"> verilog (0.8.7)</div>
+</li>
+<li class="level1"><div class="li"> wcalc (1.0)</div>
+</li>
+<li class="level1"><div class="li"> xgsch2pcb (0.1.2)</div>
+</li>
+<li class="level1"><div class="li"> electronics-menu (1.0)</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Available rpm packages" [55-360] -->
+<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>
+<li class="level1"><div class="li"> Start Yast and go to â??Change Installation Sourceâ??</div>
+</li>
+<li class="level1"><div class="li"> Add a <acronym title="Hyper Text Transfer Protocol">HTTP</acronym> source with the following properties: </div>
+<ul>
+<li class="level3"><div class="li"> <strong>Servername:</strong> software.opensuse.org</div>
+</li>
+<li class="level3"><div class="li"> <strong>Directory:</strong> /download/repositories/science/openSUSE_11.0/ </div>
+</li>
+</ul>
+</li>
+</ol>
+
+<p>
+ (Choose the directory for your distribution)
+</p>
+<ol>
+<li class="level1"><div class="li"> Start â??Install Softwareâ?? in Yast, goto â??Searchâ?? and look for gEDA. All packages appear.</div>
+</li>
+<li class="level1"><div class="li"> Install the packages as usuall.</div>
+</li>
+</ol>
+
+<p>
+ 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/science/openSUSE_10.3/repodata/"; class="urlextern" title="http://software.opensuse.org/download/science/openSUSE_10.3/repodata/"; rel="nofollow"> openSUSE_10.3 repo</a>, <a href="http://software.opensuse.org/download/science/openSUSE_11.0/repodata/"; class="urlextern" title="http://software.opensuse.org/download/science/openSUSE_11.0/repodata/"; rel="nofollow"> openSUSE_11.0 repo</a>, <a href="http://software.opensuse.org/download/science/openSUSE_11.1/repodata/"; class="urlextern" title="http://software.opensuse.org/download/science/openSUSE_11.1/repodata/"; rel="nofollow"> openSUSE_11.1 repo</a>.
+</p>
+
+</div>
+<!-- SECTION "Installing Packages from the SuSE Build Service" [361-1362] -->
+<h2><a name="distribution_specific_notes" id="distribution_specific_notes">Distribution specific notes</a></h2>
+<div class="level2">
+
+<p>
+ Each distribution version has itâ??s own issues. Please read the notes below.
+</p>
+
+</div>
+<!-- SECTION "Distribution specific notes" [1363-1480] -->
+<h3><a name="opensuse_10.2" id="opensuse_10.2">openSUSE 10.2</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> no longer available</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "openSUSE 10.2" [1481-1529] -->
+<h3><a name="opensuse_10.3" id="opensuse_10.3">openSUSE 10.3</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> …</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "openSUSE 10.3" [1530-1562] -->
+<h3><a name="opensuse_11.0" id="opensuse_11.0">openSUSE 11.0</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> …</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "openSUSE 11.0" [1563-1595] -->
+<h3><a name="opensuse_11.1" id="opensuse_11.1">openSUSE 11.1</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> currently no electronics menu, all programs show up in the Education→Science menu</div>
+</li>
+<li class="level1"><div class="li"> …</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "openSUSE 11.1" [1596-1715] -->
+<h2><a name="desktop_integration" id="desktop_integration">Desktop Integration</a></h2>
+<div class="level2">
+
+<p>
+This is a summary how the gEDA and other electronic packages are integrated into the desktop of openSUSE.
+</p>
+
+</div>
+<!-- SECTION "Desktop Integration" [1716-1855] -->
+<h3><a name="electronics_menu" id="electronics_menu">Electronics Menu</a></h3>
+<div class="level3">
+
+<p>
+Unfortunatly the openSUSE distribution does not provide a electronics menu entry for all the nice gEDA programms. Peter Clifton has created a menu entry for electronics. This menu package is available in the <strong>electronics-menu</strong> rpm. It contains the menu item and some icons for it. The menu categorie is called <strong>Edutainment–>Electronics</strong> in openSUSE.
+</p>
+
+<p>
+If it is installed, it looks like this in KDE (manually combined with gimp):
+</p>
+
+<p>
+<a href="media/geda/suse_electronics_menu.png" class="media" target="_blank" title="geda:suse_electronics_menu.png"><img src="media/geda/suse_electronics_menu.png" class="media" alt="" /></a>
+</p>
+
+</div>
+<!-- SECTION "Electronics Menu" [1856-2356] -->
+<h3><a name="notes_about_rpm_spec_file" id="notes_about_rpm_spec_file">Notes about rpm spec file</a></h3>
+<div class="level3">
+
+<p>
+openSUSE calls itâ??s <em>SuSEconfig</em> program after every installation of rpm packages with YaST. Thus itâ??s not necessary to integrate all configuration calls into the <em>post</em> and <em>postun</em> rpm sections.
+</p>
+
+<p>
+The only additions in the <acronym title="specification">spec</acronym> files are for the <em>Shared <acronym title="Multipurpose Internet Mail Extension">MIME</acronym> Info</em>. It is described in this openSUSE <a href="http://en.opensuse.org/Packaging/SUSE_Package_Conventions/Specific_Packages#10.1.3._Shared_MIME_Info"; class="urlextern" title="http://en.opensuse.org/Packaging/SUSE_Package_Conventions/Specific_Packages#10.1.3._Shared_MIME_Info"; rel="nofollow">SUSE_Package_Conventions/Specific_Packages</a> article.
+</p>
+<pre class="code">PreReq: shared-mime-info
+[...]</pre>
+<pre class="code">%post
+if test -f %{_bindir}/update-mime-database ; then
+ %{_bindir}/update-mime-database %{_datadir}/mime >/dev/null
+fi</pre>
+<pre class="code">%postun
+if test -f %{_bindir}/update-mime-database ; then
+ %{_bindir}/update-mime-database %{_datadir}/mime >/dev/null
+fi</pre>
+
+<p>
+ Another addition is required to install the mimelnks properly in the KDE environment. KDE does not take care of the mimelnks installed in <em>/usr/share/mimelnk</em>/, thus they have to be copied to the KDE directory <em>/opt/kde3/mimelnk</em>/. This is done in the rpm <acronym title="specification">spec</acronym> file inside the %install section
+</p>
+<pre class="code">%install
+%makeinstall
+kdemimedir=$(kde-config --install mime)
+if test %{_datadir} != $kdemimedir ; then
+ mkdir -p $RPM_BUILD_ROOT$kdemimedir
+ mv $RPM_BUILD_ROOT%{_datadir}/mimelnk/* $RPM_BUILD_ROOT$kdemimedir
+ rmdir $RPM_BUILD_ROOT%{_datadir}/mimelnk
+fi</pre>
+
+</div>
+<!-- SECTION "Notes about rpm spec file" [2357-3746] -->
+<h3><a name="installing_rpm_packages_manually" id="installing_rpm_packages_manually">Installing rpm packages manually</a></h3>
+<div class="level3">
+
+<p>
+For those who donâ??t use YaST for installation the SuSEconfig command has to be executed manually after installing or removing any rpm package. You can either call the toplevel SuSEconfig command
+</p>
+<pre class="code">/sbin/SuSEconfig </pre>
+
+<p>
+ or call only the two required subconfiguration tools
+</p>
+<pre class="code">/sbin/conf.d/SuSEconfig.desktop-file-utils </pre>
+
+<p>
+ which calls
+</p>
+<pre class="code">/usr/bin/update-desktop-database</pre>
+
+<p>
+ and
+</p>
+<pre class="code">/sbin/conf.d/SuSEconfig.gtk2</pre>
+
+<p>
+ which calls
+</p>
+<pre class="code">/usr/bin/gtk-update-icon-cache --quiet --ignore-theme-index --remove-empty-cache "$SUBDIR"</pre>
+
+</div>
+<!-- SECTION "Installing rpm packages manually" [3747-] --></body>
+</html>
diff --git a/docs/wiki/geda-syntax_features.html b/docs/wiki/geda-syntax_features.html
new file mode 100644
index 0000000..8cdb288
--- /dev/null
+++ b/docs/wiki/geda-syntax_features.html
@@ -0,0 +1,59 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="syntax_features" id="syntax_features">Syntax features</a></h1>
+<div class="level1">
+
+<p>
+The new gEDA Project Wiki pages are hosted using Dokuwiki version 09 March 2006. This wiki-engine has several enhancements:
+</p>
+<ul>
+<li class="level1"><div class="li"> Bug fixes.</div>
+</li>
+<li class="level1"><div class="li"> A new toolbar in the editor.</div>
+</li>
+<li class="level1"><div class="li"> <a href="http://wiki.splitbrain.org/wiki:syntax"; class="urlextern" title="http://wiki.splitbrain.org/wiki:syntax"; rel="nofollow">Syntax</a> enhancements.</div>
+</li>
+<li class="level1"><div class="li"> Updates to the <a href="http://wiki.splitbrain.org/wiki:search"; class="urlextern" title="http://wiki.splitbrain.org/wiki:search"; rel="nofollow">Search</a> feature. You can now search for exact phrases by enclosing them with double quotes, and use â??*â?? wildcard searches.</div>
+</li>
+<li class="level1"><div class="li"> Google <a href="http://wiki.splitbrain.org/wiki:sitemap"; class="urlextern" title="http://wiki.splitbrain.org/wiki:sitemap"; rel="nofollow">sitemap</a> support. Your edited content will be indexed by Google much faster.</div>
+</li>
+<li class="level1"><div class="li"> You can upload and embed <a href="http://wiki.splitbrain.org/wiki:images"; class="urlextern" title="http://wiki.splitbrain.org/wiki:images"; rel="nofollow">other files</a> into the pages using the MediaPopup feature on the toolbar in the editor (including image files, flash files, <acronym title="Portable Document Format">PDF</acronym> files, etc.). Please note that image/media files can not be removed once uploaded by an author.</div>
+</li>
+<li class="level1"><div class="li"> Footnotes.</div>
+</li>
+<li class="level1"><div class="li"> Larger global cache, allowing for larger documents (currently set to 20 <acronym title="Megabyte">MB</acronym>).</div>
+</li>
+<li class="level1"><div class="li"> You can subscribe to e-mail pagechange notification, on a wiki-page by wiki-page basis. If you are interested in monitoring the changes made by others to a spicific page, simply press the â??Subscribe Changesâ?? button at the bottom of the wiki-page. To unsubscribe from a wiki-page, simply press the â??Unsubscribe Changesâ?? button.</div>
+</li>
+<li class="level1"><div class="li"> URLs are now â??prettyâ??.</div>
+</li>
+<li class="level1"><div class="li"> Breadcrumbs (i.e., the line at the top of the browserâ??s window that starts with â??Trace:". This is a â??where are youâ?? indicator.</div>
+</li>
+<li class="level1"><div class="li"> Wiki-pages can be <a href="http://wiki.splitbrain.org/wiki:export"; class="urlextern" title="http://wiki.splitbrain.org/wiki:export"; rel="nofollow">exported</a> to different formats (e.g., plain-text, simple <acronym title="Extensible HyperText Markup Language">XHTML</acronym> (the page without navigational elements), rendered <acronym title="Extensible HyperText Markup Language">XHTML</acronym> (no head or body tags), <acronym title="Hyper Text Transfer Protocol">HTTP</acronym>).</div>
+</li>
+<li class="level1"><div class="li"> The <code><code></code></code> tag supports syntax highlighting for numerous programming languages.</div>
+</li>
+<li class="level1"><div class="li"> A playground for authors to â??playâ?? with new features, before implimenting on the wikiâ??s pages.</div>
+</li>
+<li class="level1"><div class="li"> Control of Dokuwikiâ??s <a href="http://wiki.splitbrain.org/wiki:caching#purging_the_cache"; class="urlextern" title="http://wiki.splitbrain.org/wiki:caching#purging_the_cache"; rel="nofollow">caching</a> operations. This is important to wiki-page authors, as sometimes a page gets cached by Dokuwiki on the server, and needs to be purged. Remember, what the author sees may not be what others see.<br/>
+ This is different than your browserâ??s cache, which may occassionally need to be flushed. For example, when the <acronym title="Hypertext Preprocessor">PHP</acronym> global memory limit is exceeded, that wiki-page canâ??t be displayed, even if the <acronym title="Hypertext Preprocessor">PHP</acronym> global memory limit is changed on the server. You would need to flush your browserâ??s cache to load and view the wiki-page.</div>
+</li>
+</ul>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-systemc_netlister_readme.html b/docs/wiki/geda-systemc_netlister_readme.html
new file mode 100644
index 0000000..a1ed4d4
--- /dev/null
+++ b/docs/wiki/geda-systemc_netlister_readme.html
@@ -0,0 +1,108 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="systemc_netlister_readme" id="systemc_netlister_readme">SystemC netlister README</a></h1>
+<div class="level1">
+<pre class="code">TITLE:
+
+ Gnetlist SystemC Backend
+
+OBJECTIVE:
+
+ Transform a geda schematic into a transaction based structural systemc module.
+
+LIMITATIONS:
+
+ 1.- Only transaction based wires are considered (wire_name<user_type>).
+ 2.- Unnamed wires are eliminated.
+ 3.- In/out ports have to be inserted manually in the sysc code.
+ 4.- Duplicated include headers are not eliminated by the backend.
+ 5.- The maximum number of object constructor parameters is 31 (attr1->attr31).
+
+LINKS:
+
+ GPL Electronic Design Automation (geda-gnetlist): http://www.gpleda.org
+ SystemC: http://www.systemc.org
+
+ACK:
+
+ Based on gnet-verilog.scm by Mike Jarabek.
+
+EXAMPLE:
+
+ Schematic:
+
+ src1 alg1 snk1
+ ______________ _______________ _______________
+ | source | a<user_type> | algorithm | b<float> | sink |
+ | OUT|__ _________ __|IN OUT|__ _____ __|IN |
+ | | | | | |
+ | infile.data| | | | outfile.data|
+ |____________| |_____________| |_____________|
+
+
+ Attributes:
+
+ Schematic:
+ module_name=test_sch2sysc
+
+ Wires:
+ netname=a<user_type>
+ netname=b<float>
+ Symbols:
+ refdes=src1 attr1=infile.data
+ refdes=alg1
+ refdes=snk1 attr1=outfile.data
+ refdes=pina
+ refdes=pinb
+
+ SystemC:
+
+ #include "systemc.h"
+ #include "sink.h"
+ #include "source.h"
+ #include "algorithm.h"
+
+ SC_MODULE (test_sch2sysc)
+ {
+ /* Port directions begin here */
+
+ /* Wires from the design */
+ sc_signal<float> b;
+ sc_signal<packet_type> a;
+
+ /* Package instantiations */
+ sink snk1;
+ source src1;
+ algorithm alg1;
+
+ SC_CTOR(test_sch2sysc):
+ snk1("snk1","outfile.data"),
+ src1("src1","infile.data"),
+ alg1("alg1")
+ {
+ snk1.IN(b);
+ src1.OUT(a);
+ alg1.IN(a);
+ alg1.OUT(b);
+ }
+ };
+
+</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-tasks.html b/docs/wiki/geda-tasks.html
new file mode 100644
index 0000000..1bbaec6
--- /dev/null
+++ b/docs/wiki/geda-tasks.html
@@ -0,0 +1,89 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#geda_tasks" class="toc">gEDA Tasks</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#important_tasks_for_normal_volunteers" class="toc">Important tasks for normal volunteers</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#tasks_for_programmers" class="toc">Tasks for programmers</a></span></div></li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="geda_tasks" id="geda_tasks">gEDA Tasks</a></h1>
+<div class="level1">
+
+<p>
+gEDA is run by volunteers, so these are volunteer (read: unpaid) tasks. Please consider helping out. Thank you.
+</p>
+
+</div>
+<!-- SECTION "gEDA Tasks" [1-137] -->
+<h2><a name="important_tasks_for_normal_volunteers" id="important_tasks_for_normal_volunteers">Important tasks for normal volunteers</a></h2>
+<div class="level2">
+<ul>
+<li class="level1"><div class="li"> <strong>Documentation Writers/Editors</strong><br/>
+ Somebody is needed to act as an editor for the gEDA documentation effort. Basically this person would take whatever documentation already exists and/or is currently being written and formats it into something presentable. This individual does not write the actual documentation, but would instead perform editorial work. People who want to write the actual documentation are also needed. (The <a href="http://geda.seul.org/wiki/"; class="urlextern" title="http://geda.seul.org/wiki/"; rel="nofollow"> start</a> page explains how to get started editing the documentation on the wiki).</div>
+</li>
+<li class="level1"><div class="li"> <strong>PCB Publicity Manager</strong><br/>
+ Somebody is needed to do publicity for the gEDA project. This consists of posting release updates to the various PCB design websites (such as <a href="http://CircuitCalculator.com/"; class="urlextern" title="http://CircuitCalculator.com/"; rel="nofollow">http://CircuitCalculator.com/</a> , <a href="http://www.olimex.com/pcb/dtools.html"; class="urlextern" title="http://www.olimex.com/pcb/dtools.html"; rel="nofollow"> Olimex</a>, <a href="http://www.4pcb.com/index.php?load=content&page_id=46"; class="urlextern" title="http://www.4pcb.com/index.php?load=content&page_id=46"; rel="nofollow"> Advanced Circuits</a>, <a href="http://opencircuits.com/Techniques"; class="urlextern" title="http://opencircuits.com/Techniques"; rel="nofollow"> Open Circuits</a>, <a href="http://www.ePanorama.net/"; class="urlextern" title="http://www.ePanorama.net/"; rel="nofollow">http://www.ePanorama.net/</a> , <a href="http://docwiki.gumstix.org/"; class="urlextern" title="http://docwiki.gumstix.org/"; rel="nofollow"> gumstix</a>, <a href="http://reprap.org/bin/view"; class="urlextern" title="http://reprap.org/bin/view"; rel="nofollow"> RepRap</a>, etc.)</div>
+</li>
+<li class="level1"><div class="li"> <strong>Linux Publicity Manager</strong><br/>
+ Somebody is needed to do publicity for the gEDA project. This consists of posting release updates to the various Linux/Unix websites (like <a href="http://www.freshmeat.net"; class="urlextern" title="http://www.freshmeat.net"; rel="nofollow"> Freshmeat</a> or <a href="http://LWN.net/"; class="urlextern" title="http://LWN.net/"; rel="nofollow"> LWN</a> or <a href="http://LinuxRobots.org/"; class="urlextern" title="http://LinuxRobots.org/"; rel="nofollow">http://LinuxRobots.org/</a> )</div>
+</li>
+<li class="level1"><div class="li"> <strong>UNIX Port Testers</strong><br/>
+ People are always needed to test gEDA on different and new UNIX like operating systems. This person would basically download a new release and make sure it works on their platform of choice. Any problems found would be then submitted to the appropriate gEDA author.</div>
+</li>
+<li class="level1"><div class="li"> <strong>Website/Mirror Hacker</strong><br/>
+ Somebody to watch over the mirrors and maybe do some <acronym title="HyperText Markup Language">HTML</acronym> hacking is needed. There are currently three websites which need to be monitored and occasionally fixed. The person would also have influence in the changing/expansion of the gEDA website. Duties would be split among the current webmasters.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Important tasks for normal volunteers" [138-2142] -->
+<h2><a name="tasks_for_programmers" id="tasks_for_programmers">Tasks for programmers</a></h2>
+<div class="level2">
+
+<p>
+ <img src="images/smileys/fixme.gif" align="middle" alt="FIXME" />: <code>Should this list be combined with <a href="geda-todos.html" class="wikilink1" title="geda-todos.html">todos</a> ?</code>
+</p>
+<ul>
+<li class="level1"><div class="li"> <strong>Netlist Hacker</strong><br/>
+ Somebody who is familiar with the generation/management of netlists is needed to help work on and improve gnetlist. Whether the existing gnetlist is used or if a total rewrite is needed is always an open option. Must be extremely familiar with UNIX/C/C++ programming.</div>
+</li>
+<li class="level1"><div class="li"> <strong>Symbol Library Hacker</strong><br/>
+ Somebody is needed to help get the symbol library up to the current symbol <acronym title="specification">spec</acronym>. This individual would also help in the integration of new symbols and making sure that they meet the current symbol <acronym title="specification">spec</acronym>. The task of getting the symbol library up to <acronym title="specification">spec</acronym> is a combination of manual effort and automated updating (this sort of automated updating lends itself very well to a person with shell/perl scripting familiarity).</div>
+</li>
+<li class="level1"><div class="li"> <strong>geda <acronym title="Graphical User Interface">GUI</acronym> Hacker</strong><br/>
+ Somebody who knows C, UNIX, and GTK+ programming is needed to work on the gEDA <acronym title="Graphical User Interface">GUI</acronym> (the program named geda). This program has been stalled for the past year due to the lack of manpower. Whether the existing geda is used or a total rewrite is needed is always an open option.</div>
+</li>
+<li class="level1"><div class="li"> <strong>Windows Port Hacker/Manager</strong><br/>
+ Somebody with expertise building and testing gEDA on UNIX systems and familiarity with the <acronym title="Microsoft">MS</acronym> Windows 95/98/NT platform is needed to manage the gEDA Windows port. Testing, bug fixing, packaging, and releasing of gEDA on the Windows platform would be the primary responsibility of this person. This task requires a person who knows C, GTK+, UNIX, and <acronym title="Microsoft">MS</acronym> Windows programming. The Windows port will NOT move forward if this task is not filled.</div>
+</li>
+<li class="level1"><div class="li"> <strong>MacOS port manager</strong><br/>
+ Have the issues mentioned in <a href="http://www.evilmadscientist.com/article.php/pcbtools"; class="urlextern" title="http://www.evilmadscientist.com/article.php/pcbtools"; rel="nofollow"> "Laying out printed circuit boards with open-source tools"</a> been fixed already?</div>
+</li>
+<li class="level1"><div class="li"> <strong>Release Hacker</strong><br/>
+ Somebody who wants to create and manage releases is needed. Releases occur when the code is ready to be released, so thereâ??s no marketing pressure. This task requires gEDA building/testing familiarity as well perhaps some minor code hacking.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Tasks for programmers" [2143-] --></body>
+</html>
diff --git a/docs/wiki/geda-todos.html b/docs/wiki/geda-todos.html
new file mode 100644
index 0000000..a21fb9e
--- /dev/null
+++ b/docs/wiki/geda-todos.html
@@ -0,0 +1,402 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#todos" class="toc">Todos</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#release_roadmap" class="toc">Release roadmap</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#unstable" class="toc">1.5.3/1.5.4 (unstable)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#stable" class="toc">1.6 (stable)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#stable1" class="toc">1.8 (stable)</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#longer_term_upgrades_desired_for_specific_tools" class="toc">Longer term upgrades desired for specific tools</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#ideas_for_new_tools_or_geda_suite-wide_enhancements" class="toc">Ideas for new tools or gEDA Suite-wide enhancements</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#code_cleanup_and_refactoring" class="toc">Code cleanup and refactoring</a></span></div></li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="todos" id="todos">Todos</a></h1>
+<div class="level1">
+
+<p>
+These lists are meant to provide the developers a reminder of undone projects. It is also a wish list capturing userâ??s desires for new features. New developers can also look here for projects which they might be interested in working on.
+</p>
+
+<p>
+See <a href="geda-tasks.html" class="wikilink1" title="geda-tasks.html">tasks</a> for non-programmer tasks.
+</p>
+
+</div>
+<!-- SECTION "Todos" [1-304] -->
+<h2><a name="release_roadmap" id="release_roadmap">Release roadmap</a></h2>
+<div class="level2">
+
+<p>
+ This section should contain a list of <strong>only</strong> those issues that are considered as being important enough to block release until they are resolved. If a feature or bug gets bumped or has its importance reduced, please remove it from the list or move it to the appropriate later release.
+</p>
+
+<p>
+Todos for past releases can be seen on the <a href="geda-todos_historical.html" class="wikilink1" title="geda-todos_historical.html"> historical </a> page.
+</p>
+
+</div>
+<!-- SECTION "Release roadmap" [305-717] -->
+<h3><a name="unstable" id="unstable">1.5.3/1.5.4 (unstable)</a></h3>
+<div class="level3">
+
+<p>
+ Target release date: <strong>August 2009</strong> <br/>
+ Actual release date: <strong>August 29th 2009 and August 30th 2009</strong> <br/>
+ 1.5.3 was withdrawn from distribution after some release critical bugs were discovered. <br/>
+
+</p>
+<table class="inline">
+ <tr>
+ <th class="leftalign"> Description </th><th class="leftalign"> SF bug </th><th class="leftalign"> Developer(s) </th><th class="leftalign"> Status </th>
+ </tr>
+ <tr>
+ <td class="leftalign"> Renderer improvements (pango text on screen) </td><td class="rightalign"> </td><td class="leftalign"> Peter C </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=f8a0f1c1b5fd42c78a7165dcfa4b5135790a24a5"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=f8a0f1c1b5fd42c78a7165dcfa4b5135790a24a5"; rel="nofollow"> Done </a> </td>
+ </tr>
+ <tr>
+ <td> Embeded symbol contents different depending on how embedded </td><td> <a href="https://sourceforge.net/tracker2/?func=detail&aid=2460301&group_id=161080&atid=818426"; class="urlextern" title="https://sourceforge.net/tracker2/?func=detail&aid=2460301&group_id=161080&atid=818426"; rel="nofollow"> 2460301 </a> </td><td class="leftalign"> Peter B </td><td> Fixed (<a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=ea46d8defce4390b9650e8d2a5035de4794673df"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=ea46d8defce4390b9650e8d2a5035de4794673df"; rel="nofollow"> 1</a> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=a419f4f196ef6574940d082d88f46b95bbeb0ea9"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=a419f4f196ef6574940d082d88f46b95bbeb0ea9"; rel="nofollow"> 2</a>) </td>
+ </tr>
+ <tr>
+ <td> <del>gattrib: Fix file→load to do something useful</del> </td><td class="centeralign"> <del>n/a</del> </td><td> </td><td> Cancelled </td>
+ </tr>
+ <tr>
+ <td> gschem: Preselect current setting when editing fill and line styles </td><td> <a href="https://sourceforge.net/tracker2/?func=detail&aid=2344964&group_id=161080&atid=818426"; class="urlextern" title="https://sourceforge.net/tracker2/?func=detail&aid=2344964&group_id=161080&atid=818426"; rel="nofollow"> 2344964 </a> <a href="https://sourceforge.net/tracker2/?func=detail&aid=2344956&group_id=161080&atid=818426"; class="urlextern" title="https://sourceforge.net/tracker2/?func=detail&aid=2344956&group_id=161080&atid=818426"; rel="nofollow"> 2344956 </a> </td><td class="leftalign"> Werner </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=e84330457016f1bfb3db1cd6c8a6980a72a6e90c"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=e84330457016f1bfb3db1cd6c8a6980a72a6e90c"; rel="nofollow">Fixed</a> </td>
+ </tr>
+ <tr>
+ <td> Dangerous button focus in â??Save changesâ?? dialog at quit </td><td> <a href="https://sourceforge.net/tracker/index.php?func=detail&aid=2058707&group_id=161080&atid=818426"; class="urlextern" title="https://sourceforge.net/tracker/index.php?func=detail&aid=2058707&group_id=161080&atid=818426"; rel="nofollow"> 2058707</a> </td><td class="leftalign"> Peter C </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=c006ec0603fd570ec6c10386f3a3d19f9cbd525d"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=c006ec0603fd570ec6c10386f3a3d19f9cbd525d"; rel="nofollow"> Fixed gschem </a> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=7253fb551e683b3c7c15c0f8595178f88129e7c5"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=7253fb551e683b3c7c15c0f8595178f88129e7c5"; rel="nofollow"> Fixed gattrib </a> </td>
+ </tr>
+ <tr>
+ <td> Fix zooming with (warp-cursor â??disabledâ??) </td><td> <a href="https://sourceforge.net/tracker2/?func=detail&aid=2001299&group_id=161080&atid=818429"; class="urlextern" title="https://sourceforge.net/tracker2/?func=detail&aid=2001299&group_id=161080&atid=818429"; rel="nofollow"> 2001299 </a> <a href="https://sourceforge.net/tracker2/?func=detail&aid=2212748&group_id=161080&atid=818426"; class="urlextern" title="https://sourceforge.net/tracker2/?func=detail&aid=2212748&group_id=161080&atid=818426"; rel="nofollow"> 2212748 </a> </td><td> Werner </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=d48b0b36c5348abd52413de14afb6ab0958b260d"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=d48b0b36c5348abd52413de14afb6ab0958b260d"; rel="nofollow"> Fixed </a></td>
+ </tr>
+ <tr>
+ <td> Fix drawing artifact sometimes left after cancelling net mode </td><td> <a href="https://sourceforge.net/tracker2/?func=detail&aid=2449060&group_id=161080&atid=818426"; class="urlextern" title="https://sourceforge.net/tracker2/?func=detail&aid=2449060&group_id=161080&atid=818426"; rel="nofollow"> 2449060 </a> </td><td class="leftalign"> Peter C </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commitdiff;h=0fe820aa442bba02d164832ce771932f2189d231#patch14"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commitdiff;h=0fe820aa442bba02d164832ce771932f2189d231#patch14"; rel="nofollow"> Fixed </a> (in invalidate/expose code) </td>
+ </tr>
+ <tr>
+ <td> Deselecting component doesnâ??t deselect hidden attrib </td><td> <a href="https://sourceforge.net/tracker2/?func=detail&aid=2430369&group_id=161080&atid=818426"; class="urlextern" title="https://sourceforge.net/tracker2/?func=detail&aid=2430369&group_id=161080&atid=818426"; rel="nofollow"> 2430369 </a> </td><td class="leftalign"> Peter C </td><td class="leftalign"> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=d3bd67e8ccb5ed47f17603392f480f220380daa5"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=d3bd67e8ccb5ed47f17603392f480f220380daa5"; rel="nofollow"> Fixed </a> </td>
+ </tr>
+ <tr>
+ <td> Fix gnetlist ordering / test-suite against recent GLib </td><td> <a href="https://sourceforge.net/tracker2/?func=detail&aid=2455061&group_id=161080&atid=818426"; class="urlextern" title="https://sourceforge.net/tracker2/?func=detail&aid=2455061&group_id=161080&atid=818426"; rel="nofollow"> 2455061 </a> </td><td> Peter C </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=2d888258d954c993aa03e4a1beb7b03e62df4d95"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=2d888258d954c993aa03e4a1beb7b03e62df4d95"; rel="nofollow"> Fixed </a> </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> Unified build system </td><td> <a href="https://sourceforge.net/tracker2/?func=detail&aid=1758673&group_id=161080&atid=818429"; class="urlextern" title="https://sourceforge.net/tracker2/?func=detail&aid=1758673&group_id=161080&atid=818429"; rel="nofollow"> 1758673 </a> </td><td class="leftalign"> Peter B </td><td class="leftalign"> Done </td>
+ </tr>
+ <tr>
+ <td> Get rid of all obsolete auto* macros </td><td class="centeralign"> n/a </td><td class="leftalign"> Peter B </td><td class="leftalign"> Done </td>
+ </tr>
+</table>
+
+<p>
+ Wishlist
+</p>
+<table class="inline">
+ <tr>
+ <th class="leftalign"> Description </th><th class="leftalign"> SF bug </th><th class="leftalign"> Developer(s) </th><th class="leftalign"> Status </th>
+ </tr>
+ <tr>
+ <td> Printing improvements (Arbitrary UTF8 postscript) - print with cairo </td><td class="centeralign"> n/a </td><td class="leftalign"> Peter B, Peter C </td><td> 50% </td>
+ </tr>
+ <tr>
+ <td> gschem: interface for creating paths and inserting / deleting nodes </td><td class="centeralign"> n/a </td><td class="rightalign"> </td><td> </td>
+ </tr>
+ <tr>
+ <td> Bitmap export options: allow specifying DPI rather than / as well as absolute page size </td><td> <a href="https://sourceforge.net/tracker/?func=detail&atid=818429&aid=2226522&group_id=161080"; class="urlextern" title="https://sourceforge.net/tracker/?func=detail&atid=818429&aid=2226522&group_id=161080"; rel="nofollow"> 2226522 </a> </td><td> </td><td> </td>
+ </tr>
+ <tr>
+ <td> Set print border size </td><td> <a href="https://sourceforge.net/tracker/index.php?func=detail&aid=2243238&group_id=161080&atid=818429"; class="urlextern" title="https://sourceforge.net/tracker/index.php?func=detail&aid=2243238&group_id=161080&atid=818429"; rel="nofollow"> 2243238 </a> </td><td> Werner </td><td> </td>
+ </tr>
+ <tr>
+ <td> Allow setting gschem on-screen border </td><td> <a href="https://sourceforge.net/tracker/index.php?func=detail&aid=2243238&group_id=161080&atid=818429"; class="urlextern" title="https://sourceforge.net/tracker/index.php?func=detail&aid=2243238&group_id=161080&atid=818429"; rel="nofollow"> 2243238 </a> </td><td> </td><td> </td>
+ </tr>
+</table>
+
+</div>
+<!-- SECTION "1.5.3/1.5.4 (unstable)" [718-4896] -->
+<h3><a name="stable" id="stable">1.6 (stable)</a></h3>
+<div class="level3">
+
+<p>
+ Target release date: <strong>September 2009 (soon after 1.5.4 is complete) </strong> <br/>
+ Actual release date: <strong>TBD</strong>
+</p>
+<table class="inline">
+ <tr>
+ <th class="leftalign"> Description </th><th class="leftalign"> SF bug </th><th class="leftalign"> Developer(s) </th><th class="leftalign"> Status </th>
+ </tr>
+ <tr>
+ <td class="leftalign"> Fix gattrib build with recent GTK+ </td><td class="leftalign"> <a href="http://sourceforge.net/tracker/index.php?func=detail&aid=2832985&group_id=161080&atid=818426"; class="urlextern" title="http://sourceforge.net/tracker/index.php?func=detail&aid=2832985&group_id=161080&atid=818426"; rel="nofollow"> 2832985 </a> </td><td class="leftalign"> Peter C </td><td class="leftalign"> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=78da20ca286eb2f6e518c64dca94b888fc8c19af"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=78da20ca286eb2f6e518c64dca94b888fc8c19af"; rel="nofollow"> Fixed </a> </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> Update documentation from wiki </td><td class="rightalign"> </td><td class="leftalign"> Ales </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> Check copyright headers are up-to-date </td><td class="centeralign"> n/a </td><td class="rightalign"> </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td> <del>UTF-8 / system / filesystem encoding bugs</del> </td><td> <del><a href="https://sourceforge.net/tracker/?func=detail&group_id=161080&atid=818426&aid=1868072"; class="urlextern" title="https://sourceforge.net/tracker/?func=detail&group_id=161080&atid=818426&aid=1868072"; rel="nofollow"> 1868072</a></del> </td><td> </td><td> Cancelled (minor impact) </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> Portability patches for mingw32 landed in some form or other. </td><td> </td><td> Cesar S, Peter C </td><td> Awaiting testing and feedback </td>
+ </tr>
+ <tr>
+ <td> Screenshots of release version for a publicity revamp of gEDA website. </td><td class="centeralign"> n/a </td><td> Peter C </td><td> </td>
+ </tr>
+ <tr>
+ <td> Merge translations from Launchpad upstream. </td><td> </td><td> Peter C (?) </td><td> </td>
+ </tr>
+ <tr>
+ <td> Cure all: â??warning: format not a string literal and no format argumentsâ?? compiling with recent GCC versions </td><td> </td><td> </td><td> Fixed </td>
+ </tr>
+ <tr>
+ <td> Cure all: â??warning : ignoring return value of â??…â??, declared with attribute warn_unused_resultâ?? compiling with recent GCC versions </td><td> </td><td> </td><td> </td>
+ </tr>
+ <tr>
+ <td> gattrib: Remove all deliberately-non-functioning menu options / buttons </td><td class="centeralign"> n/a </td><td> Peter C </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=0deb0abc3d82a8127c9566d886858811c1dcc717"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=0deb0abc3d82a8127c9566d886858811c1dcc717"; rel="nofollow"> Fixed menu items </a> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=22d5b2abcd1aa5c098566ee5b292c6d7215b9b8e"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=22d5b2abcd1aa5c098566ee5b292c6d7215b9b8e"; rel="nofollow"> Fixed Nets sheet </a> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=721114eccc913dbbbd5e1d0700b87662aac316fc"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=721114eccc913dbbbd5e1d0700b87662aac316fc"; rel="nofollow"> Fixed Pins sheet </a> </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> <del>Prettify symbols (e.g. gates) using paths</del> </td><td class="centeralign"> <del>n/a</del> </td><td class="rightalign"> </td><td> Cancelled (cosmetic) </td>
+ </tr>
+ <tr>
+ <td> Fix symbols using explicit lines for overbars </td><td class="centeralign"> n/a </td><td> Bert T, Werner </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=9e3e45193643d5bca628df5074fd1aedd7ff619c"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=9e3e45193643d5bca628df5074fd1aedd7ff619c"; rel="nofollow">Done</a></td>
+ </tr>
+ <tr>
+ <td> utils: Teach gsch2pcb to detect and avoid the common â??footprint saved as PCB fileâ?? mistake </td><td class="centeralign"> n/a </td><td> Peter B </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=821845073b187409488bbf78ed947fd084439546"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=821845073b187409488bbf78ed947fd084439546"; rel="nofollow"> Done </a> </td>
+ </tr>
+ <tr>
+ <td> gschem: Fix broken net consolidation for certain scenarios </td><td class="centeralign"> n/a </td><td class="leftalign"> Peter C </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=399560caafde7046fe0e361712389e559969a424"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=399560caafde7046fe0e361712389e559969a424"; rel="nofollow"> Fixed </a> (hack) </td>
+ </tr>
+</table>
+
+</div>
+<!-- SECTION "1.6 (stable)" [4897-7452] -->
+<h3><a name="stable1" id="stable1">1.8 (stable)</a></h3>
+<div class="level3">
+
+<p>
+ Target release date: <strong>Unknown</strong> <br/>
+ Actual release date: <strong>TBD</strong>
+</p>
+<table class="inline">
+ <tr>
+ <th class="leftalign"> Description </th><th class="leftalign"> SF bug </th><th class="leftalign"> Developer(s) </th><th class="leftalign"> Status </th>
+ </tr>
+ <tr>
+ <td class="leftalign"> TinyScheme instead of Guile </td><td class="rightalign"> </td><td class="leftalign"> Peter B </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> Per-page netlisting in libgeda </td><td class="rightalign"> </td><td class="leftalign"> Peter C </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> Refactor / improve gnetlist </td><td class="rightalign"> </td><td class="leftalign"> Peter C </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> gnetlist support for buses </td><td class="rightalign"> </td><td class="leftalign"> Peter C </td><td class="leftalign"> Started! </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> Avoid direct use of /tmp/ for undo schemaics </td><td class="rightalign"> </td><td class="rightalign"> </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td> New config mechanism to support non-turing complete config </td><td class="rightalign"> </td><td class="leftalign"> Peter B </td><td class="leftalign"> Started! </td>
+ </tr>
+ <tr>
+ <td> Config <acronym title="Graphical User Interface">GUI</acronym> for gschem (and gattrib?) </td><td class="rightalign"> </td><td class="leftalign"> Peter B </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td> More non-modal dialog boxes in gschem </td><td class="rightalign"> </td><td class="leftalign"> Ed (?) </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td> Refactor gschemâ??s action state machine and event dispatching code </td><td class="rightalign"> </td><td class="leftalign"> Ed </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td> Where possible, ensure gEDA compiles with deprecated GTK / GLib APIs disabled </td><td class="rightalign"> </td><td class="rightalign"> </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> Edit embedded symbols </td><td class="rightalign"> </td><td class="leftalign"> Werner (?) </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td> Per project symbol storage to make the schematics independant from the symbol library </td><td class="rightalign"> </td><td class="leftalign"> Werner (?) </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td> <a href="geda-wip-clipboard.html" class="wikilink1" title="geda-wip-clipboard.html">Clipboard support</a> for copy / paste with text representations of gEDA schematic data </td><td class="rightalign"> </td><td> Peter C (?) </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td> <a href="geda-wip-clipboard.html" class="wikilink1" title="geda-wip-clipboard.html">Clipboard support</a> for copy / paste with graphic representation of gEDA schematic data </td><td> </td><td> Peter C (?) </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> Refactor rendering code to allow its use outside of gschem </td><td class="rightalign"> </td><td class="leftalign"> Peter C </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> Refactor preview widget to make it available outside gschem </td><td class="rightalign"> </td><td class="leftalign"> Peter C </td><td class="rightalign"> </td>
+ </tr>
+</table>
+
+</div>
+<!-- SECTION "1.8 (stable)" [7453-9505] -->
+<h2><a name="longer_term_upgrades_desired_for_specific_tools" id="longer_term_upgrades_desired_for_specific_tools">Longer term upgrades desired for specific tools</a></h2>
+<div class="level2">
+<ul>
+<li class="level1"><div class="li"> <strong>Libgeda</strong>:</div>
+<ul>
+<li class="level2"><div class="li"> Enable handling of .sch files with symbols having some (but not all) pins promoted onto the .sch file. This will enable pin-swapping via backannotation from PCB. (Architectural change)</div>
+</li>
+<li class="level2"><div class="li"> Merge per-page netlisting from gnetlist (or re-write if necessary). (Bounty)</div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> <strong>Gschem</strong>:</div>
+<ul>
+<li class="level2"><div class="li"> Create a button in gschem which will invoke gsch2pcb to create a netlist file ready for PCB to read in. (Bounty, once PCB is modified to support an action file.)</div>
+</li>
+<li class="level2"><div class="li"> Enable hierarchical bus support. (Architectural change)</div>
+</li>
+<li class="level2"><div class="li"> Make gschemrc variables settable from within gschem using a â??settingsâ?? pull-down menu item (new). The idea is to update the contents of the gschemrc or gafrc files using pull-down menus, and write the changes out to the correct RC files. (Bounty)</div>
+</li>
+<li class="level2"><div class="li"> Improve symbol library to handle very large symbol collections better.</div>
+</li>
+<li class="level2"><div class="li"> Now the SELECTION is a GedaList and we can get â??changedâ?? signals, make more dialogs non-modal:</div>
+<ul>
+<li class="level3"><div class="li"> Single attribute editor</div>
+</li>
+<li class="level3"><div class="li"> Text properties</div>
+</li>
+<li class="level3"><div class="li"> Line width and type</div>
+</li>
+<li class="level3"><div class="li"> Fill type</div>
+</li>
+<li class="level3"><div class="li"> Edit slot</div>
+</li>
+<li class="level3"><div class="li"> Edit color</div>
+</li>
+<li class="level3"><div class="li"> Text size (Sets size for new text, so doesnâ??t rely on the selection anyway)</div>
+</li>
+</ul>
+</li>
+<li class="level2"><div class="li"> Enable <strong><code>-</code><code>-</code>help</strong> flag. (Currently supports -h only). Consider using GTKâ??s mechanism for this. (Bounty)</div>
+</li>
+<li class="level2"><div class="li"> Support for embedding LaTeX maths to be rendered in text.</div>
+<ul>
+<li class="level3"><div class="li"> This could be output only, or preview bitmaps could be generated and cached by calling LaTeX, dvips and ps2epsi.</div>
+</li>
+<li class="level3"><div class="li"> Would we add a new type of object for this, or allow attaching a â??latex=1â?? attribute to the text object its self?</div>
+</li>
+</ul>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> <strong>Gnetlist</strong>:</div>
+<ul>
+<li class="level2"><div class="li"> Enable <strong><code>-</code><code>-</code>help</strong> flag. Do other gEDA/gaf programs recognize this flag? (Bounty)</div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> <strong>Gattrib</strong>:</div>
+<ul>
+<li class="level2"><div class="li"> Get printing working. (Bounty)</div>
+</li>
+<li class="level2"><div class="li"> Enable attachment of attributes to nets. (Architectural)</div>
+</li>
+<li class="level2"><div class="li"> Consider using GTKâ??s mechanism to display <strong><code>-</code><code>-</code>help</strong> flag text. (Bounty)</div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> <strong>Garchive</strong>:</div>
+<ul>
+<li class="level2"><div class="li"> Incorporate guile so that it reads RC files using the same mechanism as the rest of gEDA/gaf.</div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> <strong>CD Installer</strong>:</div>
+<ul>
+<li class="level2"><div class="li"> Change it so that the user is presented a pick-list at the beginning of the install, instead of blindly installing everything. (Architectural)</div>
+</li>
+<li class="level2"><div class="li"> Make the new CD Installer install Alesâ??s binary distribution. (Bounty)</div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> <strong>Refdes_renum</strong>:</div>
+<ul>
+<li class="level2"><div class="li"> Doesnâ??t currently work properly with slotted parts (it gives new refdes numbers to slotted parts). Fix it so it recognizes slotted parts and assigns refdes appropriately. (Bounty)</div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> <strong>PCB</strong></div>
+<ul>
+<li class="level2"><div class="li"> Put various commands which are only accessible via a :command(foo) into the top menu. Newbies want to see what actions are in the menus since that way they know what PCB can do. (Bounty on a per-action basis)</div>
+</li>
+<li class="level2"><div class="li"> Provide a toolbar of buttons for common actions. (Bounty)</div>
+</li>
+<li class="level2"><div class="li"> Make the difference between editing footprints and PCBs much more obvious. If youâ??re in footprint editing mode, then perhaps make the background color change. (Architectural)</div>
+</li>
+<li class="level2"><div class="li"> Create a â??file → saveâ?? dialog window. In the dialog window, provide a pull-down giving the option to save as a PCB (default) or as a footprint. (Bounty)</div>
+</li>
+<li class="level2"><div class="li"> Modify to PCB read an â??actionsâ?? file, which tells PCB what actions to take when importing a new layout. This actions file will be created by gsch2pcb and other forward annotation programs used to take a gschem design to layout. This will also harmonize the paths which *gsch2pcb use to find footprints. (Architectural)</div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> <strong>gsch2pcb</strong></div>
+<ul>
+<li class="level2"><div class="li"> Modify gsch2pcb to emit an â??actionâ?? file, which can be fed to PCB when forward annotating a new or updated PCB layout. (Bounty, once PCB is modified)</div>
+</li>
+</ul>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Longer term upgrades desired for specific tools" [9506-13235] -->
+<h2><a name="ideas_for_new_tools_or_geda_suite-wide_enhancements" id="ideas_for_new_tools_or_geda_suite-wide_enhancements">Ideas for new tools or gEDA Suite-wide enhancements</a></h2>
+<div class="level2">
+<ul>
+<li class="level1"><div class="li"> Develop scheme for backward annotation of changes from PCB to gschem. Requires modifications to libgeda to support, e.g. pin promotion from .sym file to .sch file (enabling pin swapping). (Architectural)</div>
+</li>
+<li class="level1"><div class="li"> Create a Gerber â?? .pcb conversion tool. Result is metal layer or footprint editable by PCB. This might be a <acronym title="Practical Extraction and Report Language">Perl</acronym> script. (Bounty)</div>
+</li>
+<li class="level1"><div class="li"> Implement lockfiles between gattrib and gschem. (Bounty)</div>
+</li>
+<li class="level1"><div class="li"> Upgrade PCB to use action files in forward annotation as described above. (Architectural)</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Ideas for new tools or gEDA Suite-wide enhancements" [13236-13802] -->
+<h2><a name="code_cleanup_and_refactoring" id="code_cleanup_and_refactoring">Code cleanup and refactoring</a></h2>
+<div class="level2">
+<ul>
+<li class="level1"><div class="li"> Remove use of non GList linked lists. This is very invasive work, but allows much code cleanup where mixtures of the old and GList methods were available.</div>
+</li>
+<li class="level1"><div class="li"> Remove unused variables and functions from various structures. Unused may also include â??usedâ??, but ineffective.</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> Remove back-exports to libgeda of global function pointers from gschem and other libgeda â??clientsâ??. These arenâ??t portable.</div>
+</li>
+<li class="level1"><div class="li"> Clean up / produce generic <acronym title="Application Programming Interface">API</acronym> interfaces to act on an object of any type, or lists of objects.</div>
+</li>
+<li class="level1"><div class="li"> Convert functions used within one ".câ?? file, and not useful for public <acronym title="Application Programming Interface">API</acronym> into static functions, removing from prototype.h.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Code cleanup and refactoring" [13803-] --></body>
+</html>
diff --git a/docs/wiki/geda-todos_historical.html b/docs/wiki/geda-todos_historical.html
new file mode 100644
index 0000000..d759dab
--- /dev/null
+++ b/docs/wiki/geda-todos_historical.html
@@ -0,0 +1,238 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#past_releases" class="toc">Past Releases</a></span></div>
+<ul class="toc">
+<li class="clear">
+
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#stable" class="toc">1.4.2 (stable)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#stable1" class="toc">1.4.3 (stable)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#unstable" class="toc">1.5.1 (unstable)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#unstable1" class="toc">1.5.2 (unstable)</a></span></div></li></ul>
+</li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="past_releases" id="past_releases">Past Releases</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "Past Releases" [1-29] -->
+<h3><a name="stable" id="stable">1.4.2 (stable)</a></h3>
+<div class="level3">
+
+<p>
+ Target release date: <strong>November 2008</strong> <br/>
+ Actual release date: <strong>December 20th 2008</strong>
+</p>
+<table class="inline">
+ <tr>
+ <th class="leftalign"> Description </th><th class="leftalign"> SF bug </th><th class="leftalign"> GIT Commit (to cherrypick) </th><th class="leftalign"> Developer(s) </th><th class="leftalign"> Status </th>
+ </tr>
+ <tr>
+ <td> Bump libgeda.so micro / minor version </td><td class="centeralign"> n/a </td><td class="centeralign"> n/a </td><td> Ales </td><td class="leftalign"> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=59f9593cf903345f96f78fbd365c008061cf600e"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=59f9593cf903345f96f78fbd365c008061cf600e"; rel="nofollow"> Done </a> </td>
+ </tr>
+ <tr>
+ <td> Backport fix for gattrib crash with graphical attribute </td><td> <a href="https://sourceforge.net/tracker/?func=detail&atid=818426&aid=2214739&group_id=161080"; class="urlextern" title="https://sourceforge.net/tracker/?func=detail&atid=818426&aid=2214739&group_id=161080"; rel="nofollow"> 2214739 </a> </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commitdiff;h=9bb639685d3d413d245ebf8f58cd55b6734bec2e"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commitdiff;h=9bb639685d3d413d245ebf8f58cd55b6734bec2e"; rel="nofollow"> 9bb639685d3d413d245ebf8f58cd55b6734bec2e </a> <a href="http://git.gpleda.org/?p=gaf.git;a=commitdiff;h=0b194eee257f5818cc0ad9b035f9b81134a87745"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commitdiff;h=0b194eee257f5818cc0ad9b035f9b81134a87745"; rel="nofollow"> 0b194eee257f5818cc0ad9b035f9b81134a87745 </a> </td><td> Peter B </td><td> Done </td>
+ </tr>
+ <tr>
+ <td> Backport fix for crash / ghost connections copying embedded symbols </td><td> <a href="https://sourceforge.net/tracker2/?func=detail&aid=2321269&group_id=161080&atid=818426"; class="urlextern" title="https://sourceforge.net/tracker2/?func=detail&aid=2321269&group_id=161080&atid=818426"; rel="nofollow"> 2321269 </a> <a href="https://sourceforge.net/tracker2/?func=detail&aid=1692626&group_id=161080&atid=818426"; class="urlextern" title="https://sourceforge.net/tracker2/?func=detail&aid=1692626&group_id=161080&atid=818426"; rel="nofollow"> 1692626 </a> </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commitdiff;h=0a823197e4d511cc5fdfb38013808847781dd2f5"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commitdiff;h=0a823197e4d511cc5fdfb38013808847781dd2f5"; rel="nofollow"> 0a823197e4d511cc5fdfb38013808847781dd2f5 </a> </td><td> Peter B </td><td> Done </td>
+ </tr>
+ <tr>
+ <td> Backport fix for recomputing bounds of copied embedded symbol </td><td> <a href="https://sourceforge.net/tracker2/?func=detail&aid=1977704&group_id=161080&atid=818426"; class="urlextern" title="https://sourceforge.net/tracker2/?func=detail&aid=1977704&group_id=161080&atid=818426"; rel="nofollow"> 1977704 </a> </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commitdiff;h=3db78903fb7bd41a0f2d8b4022c2afa18055a54a"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commitdiff;h=3db78903fb7bd41a0f2d8b4022c2afa18055a54a"; rel="nofollow"> 3db78903fb7bd41a0f2d8b4022c2afa18055a54a </a> </td><td> Peter B </td><td> Done </td>
+ </tr>
+ <tr>
+ <td> Backport security fix insecure /tmp usage in sch2eaglepos.sh </td><td class="centeralign"> n/a </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commitdiff;h=5bf126369c5f5a60f5ae039170c33ff4c767a4ee"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commitdiff;h=5bf126369c5f5a60f5ae039170c33ff4c767a4ee"; rel="nofollow"> 5bf126369c5f5a60f5ae039170c33ff4c767a4ee </a> </td><td> Peter B </td><td> Done </td>
+ </tr>
+</table>
+
+</div>
+<!-- SECTION "1.4.2 (stable)" [30-1936] -->
+<h3><a name="stable1" id="stable1">1.4.3 (stable)</a></h3>
+<div class="level3">
+
+<p>
+ Target release date: <strong>January 2009</strong> <br/>
+ Actual release date: <strong>December 31st 2008</strong>
+</p>
+<table class="inline">
+ <tr>
+ <th class="leftalign"> Description </th><th class="leftalign"> SF bug </th><th class="leftalign"> GIT Commit (to cherrypick) </th><th class="leftalign"> Developer(s) </th><th class="leftalign"> Status </th>
+ </tr>
+ <tr>
+ <td> Backport â??Enable promotion of attributes when adding a component from guile." </td><td> <a href="https://sourceforge.net/tracker2/?func=detail&aid=1932474&group_id=161080&atid=818426"; class="urlextern" title="https://sourceforge.net/tracker2/?func=detail&aid=1932474&group_id=161080&atid=818426"; rel="nofollow"> 1932474 </a> </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=f154fcb921e75e7940e0b4dbd9ad5bab6a61e704"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=f154fcb921e75e7940e0b4dbd9ad5bab6a61e704"; rel="nofollow"> f154fcb921e75e7940e0b4dbd9ad5bab6a61e704 </a> </td><td> Peter C </td><td> <a href="http://repo.or.cz/w/geda-gaf/pcjc2.git?a=commit;h=416c2900bcc126171a28e33341b90d9d49848ab8"; class="urlextern" title="http://repo.or.cz/w/geda-gaf/pcjc2.git?a=commit;h=416c2900bcc126171a28e33341b90d9d49848ab8"; rel="nofollow"> Done </a> </td>
+ </tr>
+ <tr>
+ <td> Backport crash fix for rubberbanded nets </td><td> <a href="https://sourceforge.net/tracker/index.php?func=detail&aid=2017356&group_id=161080&atid=818426"; class="urlextern" title="https://sourceforge.net/tracker/index.php?func=detail&aid=2017356&group_id=161080&atid=818426"; rel="nofollow"> 2017356 </a> </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=fe8640898cb843b72e1c3cc01ee52c33db736ccf"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=fe8640898cb843b72e1c3cc01ee52c33db736ccf"; rel="nofollow"> fe8640898cb843b72e1c3cc01ee52c33db736ccf </a> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=c69785fe267e2cdc70e2748dfab7268fbdcc3e7e"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=c69785fe267e2cdc70e2748dfab7268fbdcc3e7e"; rel="nofollow"> c69785fe267e2cdc70e2748dfab7268fbdcc3e7e </a> </td><td> Peter C </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=469f81a602ea8c5228f1553f6ee785499f24905e"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=469f81a602ea8c5228f1553f6ee785499f24905e"; rel="nofollow"> Done </a> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=794d0f1c804d366a0840a9ffc63e6bdf5da27b6b"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=794d0f1c804d366a0840a9ffc63e6bdf5da27b6b"; rel="nofollow"> Done </a> </td>
+ </tr>
+ <tr>
+ <td> Backport crash fix for coincident pins </td><td> <a href="https://sourceforge.net/tracker/index.php?func=detail&aid=1912859&group_id=161080&atid=818426"; class="urlextern" title="https://sourceforge.net/tracker/index.php?func=detail&aid=1912859&group_id=161080&atid=818426"; rel="nofollow"> 1912859 </a> </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=3d8b3efb5a4ce8672133658ccdbe5c57d341f0fc"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=3d8b3efb5a4ce8672133658ccdbe5c57d341f0fc"; rel="nofollow"> 3d8b3efb5a4ce8672133658ccdbe5c57d341f0fc </a> CAUTION: In 1.4.x, complex_parent is only set on HEAD of prim_objs list </td><td> Peter C </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=66140fd3956e8d4523c8a7ecc63e519144b9c4c6"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=66140fd3956e8d4523c8a7ecc63e519144b9c4c6"; rel="nofollow"> Done </a> </td>
+ </tr>
+ <tr>
+ <td> Backport crash fix invalid attributes </td><td> <a href="https://sourceforge.net/tracker/index.php?func=detail&aid=2061325&group_id=161080&atid=818426"; class="urlextern" title="https://sourceforge.net/tracker/index.php?func=detail&aid=2061325&group_id=161080&atid=818426"; rel="nofollow"> 2061325 </a> </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=b14f3bf215963529b89f650ff3bd6f0b0c90450f"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=b14f3bf215963529b89f650ff3bd6f0b0c90450f"; rel="nofollow"> b14f3bf215963529b89f650ff3bd6f0b0c90450f </a> CAUTION: MOFIDY FOR OLD o_attrib_get_name_value() </td><td class="leftalign"> Peter C </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=51926b0107a70e944c494f9a5a76d379b217f9fb"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=51926b0107a70e944c494f9a5a76d379b217f9fb"; rel="nofollow"> Done </a> </td>
+ </tr>
+ <tr>
+ <td> Backport â??Validate calls to scm_c_eval_string(). [2105219]" </td><td> <a href="https://sourceforge.net/tracker/index.php?func=detail&aid=2105219&group_id=161080&atid=818426"; class="urlextern" title="https://sourceforge.net/tracker/index.php?func=detail&aid=2105219&group_id=161080&atid=818426"; rel="nofollow"> 2105219 </a> </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=2a4fdb13021d0153e788fe3b2fc005f273dcdf4b"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=2a4fdb13021d0153e788fe3b2fc005f273dcdf4b"; rel="nofollow"> 2a4fdb13021d0153e788fe3b2fc005f273dcdf4b </a> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=16102ef095c959b5c1febb9b9259dda23c739258"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=16102ef095c959b5c1febb9b9259dda23c739258"; rel="nofollow"> 16102ef095c959b5c1febb9b9259dda23c739258 </a> </td><td class="leftalign"> Peter B </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=22d9457c68d756675facc5acfebebca96299a766"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=22d9457c68d756675facc5acfebebca96299a766"; rel="nofollow"> Done </a> </td>
+ </tr>
+ <tr>
+ <td> Backport â??Fix the â??systemcâ?? gnetlist backendâ?? </td><td class="centeralign"> n/a </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=bfd49ad477a49235c3e5ee1eda54e5009f6e347a"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=bfd49ad477a49235c3e5ee1eda54e5009f6e347a"; rel="nofollow"> bfd49ad477a49235c3e5ee1eda54e5009f6e347a </a> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=d13aadcbac4af912e0555b3696b59fc904c6cd9f"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=d13aadcbac4af912e0555b3696b59fc904c6cd9f"; rel="nofollow"> d13aadcbac4af912e0555b3696b59fc904c6cd9f </a> </td><td> Peter C </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=7b17b576aac3f59d880d5d28234833b3a9d82e26"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=7b17b576aac3f59d880d5d28234833b3a9d82e26"; rel="nofollow"> Done </a> </td>
+ </tr>
+ <tr>
+ <td> Fix invalidation of text origin and â??Iâ?? markers </td><td class="centeralign"> n/a </td><td class="centeralign"> n/a </td><td> Peter C </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=f8749da75c18866778067b6ad04adfebce80559c"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=f8749da75c18866778067b6ad04adfebce80559c"; rel="nofollow"> Done </a> </td>
+ </tr>
+ <tr>
+ <td> Backport redraw empty preview on configure events </td><td> <a href="https://sourceforge.net/tracker2/?func=detail&aid=2159047&group_id=161080&atid=818426"; class="urlextern" title="https://sourceforge.net/tracker2/?func=detail&aid=2159047&group_id=161080&atid=818426"; rel="nofollow"> 2159047 </a> </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=87a19a19e52a37f8ad14ae0c4c68f3292b0c3285"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=87a19a19e52a37f8ad14ae0c4c68f3292b0c3285"; rel="nofollow"> 87a19a19e52a37f8ad14ae0c4c68f3292b0c3285 </a> </td><td> Peter C </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=89bb8cf750c586b5b291f2fd90d204791650dae5"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=89bb8cf750c586b5b291f2fd90d204791650dae5"; rel="nofollow"> Done </a> </td>
+ </tr>
+ <tr>
+ <td> Backport â??gschlas: Fix segfault opening fileâ?? </td><td class="centeralign"> n/a </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=46fdb00b19d300dfcc5f9009f9c7dbbf0940834f"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=46fdb00b19d300dfcc5f9009f9c7dbbf0940834f"; rel="nofollow"> 46fdb00b19d300dfcc5f9009f9c7dbbf0940834f </a> </td><td class="leftalign"> Peter C </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=6f001abc5c1fc69bb5bfbece189efbd231a8ed4c"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=6f001abc5c1fc69bb5bfbece189efbd231a8ed4c"; rel="nofollow"> Done </a> </td>
+ </tr>
+</table>
+
+</div>
+<!-- SECTION "1.4.3 (stable)" [1937-6063] -->
+<h3><a name="unstable" id="unstable">1.5.1 (unstable)</a></h3>
+<div class="level3">
+
+<p>
+ Target release date: <strong>November 2008</strong> <br/>
+ Actual release date: <strong>December 21st 2008</strong>
+</p>
+<table class="inline">
+ <tr>
+ <th class="leftalign"> Description </th><th class="leftalign"> SF bug </th><th class="leftalign"> Developer(s) </th><th class="leftalign"> Status </th>
+ </tr>
+ <tr>
+ <td class="leftalign"> Selection of filled objects </td><td> <a href="https://sourceforge.net/tracker2/?func=detail&aid=2094571&group_id=161080&atid=818426"; class="urlextern" title="https://sourceforge.net/tracker2/?func=detail&aid=2094571&group_id=161080&atid=818426"; rel="nofollow"> 2094571 </a> </td><td> Ed Hennessy, Peter C </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=94602fdc724dd31527c3ceed2092ddeee1d954e0"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=94602fdc724dd31527c3ceed2092ddeee1d954e0"; rel="nofollow"> Mostly fixed </a> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=67daa4d705d62d16133feb2d9a3a77cacb9b34de"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=67daa4d705d62d16133feb2d9a3a77cacb9b34de"; rel="nofollow"> Fixed </a> </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> Selection mechanism tweaks </td><td class="centeralign"> n/a </td><td class="leftalign"> Ed Hennessy </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=1d7d0b9f7f0cc38a79b7e392756dcb359b61bdbb"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=1d7d0b9f7f0cc38a79b7e392756dcb359b61bdbb"; rel="nofollow"> Fixed</a> </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> Finalize polygon file format </td><td class="centeralign"> n/a </td><td class="leftalign"> Peter C </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=beae647a1e0217dc5802084a6e00522a59ad5a28"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=beae647a1e0217dc5802084a6e00522a59ad5a28"; rel="nofollow"> Fixed</a> </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> Update file format docs </td><td class="centeralign"> n/a </td><td class="leftalign"> Peter C </td><td> <a href="http://geda.seul.org/wiki/geda:file_format_spec"; class="urlextern" title="http://geda.seul.org/wiki/geda:file_format_spec"; rel="nofollow"> Fixed </a> </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> Bump file format version </td><td class="centeralign"> n/a </td><td class="leftalign"> Peter C </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=c2c94821ec6c9a83d0144adad7f6fa190f403af3"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=c2c94821ec6c9a83d0144adad7f6fa190f403af3"; rel="nofollow"> Fixed </a> </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> Check on BOM2 performance </td><td class="centeralign"> n/a </td><td class="leftalign"> Peter B </td><td class="leftalign"> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=51c2a5c9f7f9ad1c99b9da2774a051ae97f3e62e"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=51c2a5c9f7f9ad1c99b9da2774a051ae97f3e62e"; rel="nofollow"> Fixed </a> </td>
+ </tr>
+ <tr>
+ <td> gschem: Segmentation fault (another one) </td><td> <a href="https://sourceforge.net/tracker/index.php?func=detail&aid=2105219&group_id=161080&atid=818426"; class="urlextern" title="https://sourceforge.net/tracker/index.php?func=detail&aid=2105219&group_id=161080&atid=818426"; rel="nofollow"> 2105219</a> </td><td> Peter B </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=2a4fdb13021d0153e788fe3b2fc005f273dcdf4b"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=2a4fdb13021d0153e788fe3b2fc005f273dcdf4b"; rel="nofollow"> Fixed </a> </td>
+ </tr>
+ <tr>
+ <td> CRASH: Crash in multiattrib editor with unusal attribute </td><td> <a href="https://sourceforge.net/tracker/index.php?func=detail&aid=2061325&group_id=161080&atid=818426"; class="urlextern" title="https://sourceforge.net/tracker/index.php?func=detail&aid=2061325&group_id=161080&atid=818426"; rel="nofollow"> 2061325</a> </td><td> Peter C </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=b14f3bf215963529b89f650ff3bd6f0b0c90450f"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=b14f3bf215963529b89f650ff3bd6f0b0c90450f"; rel="nofollow"> Fixed crash </a> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=70590a2312e2650f61a220980f9cf58bdad88987"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=70590a2312e2650f61a220980f9cf58bdad88987"; rel="nofollow"> Fixed trigger </a> </td>
+ </tr>
+ <tr>
+ <td> gschem segfaults when stretching net segments </td><td> <a href="https://sourceforge.net/tracker/index.php?func=detail&aid=2017356&group_id=161080&atid=818426"; class="urlextern" title="https://sourceforge.net/tracker/index.php?func=detail&aid=2017356&group_id=161080&atid=818426"; rel="nofollow"> 2017356</a> </td><td> Peter C </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=fe8640898cb843b72e1c3cc01ee52c33db736ccf"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=fe8640898cb843b72e1c3cc01ee52c33db736ccf"; rel="nofollow"> Partly fixed </a> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=c69785fe267e2cdc70e2748dfab7268fbdcc3e7e"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=c69785fe267e2cdc70e2748dfab7268fbdcc3e7e"; rel="nofollow"> Fixed </a> </td>
+ </tr>
+ <tr>
+ <td> Crash removing symbol with coincident pins </td><td> <a href="https://sourceforge.net/tracker/index.php?func=detail&aid=1912859&group_id=161080&atid=818426"; class="urlextern" title="https://sourceforge.net/tracker/index.php?func=detail&aid=1912859&group_id=161080&atid=818426"; rel="nofollow"> 1912859</a> </td><td> Peter C </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=3d8b3efb5a4ce8672133658ccdbe5c57d341f0fc"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=3d8b3efb5a4ce8672133658ccdbe5c57d341f0fc"; rel="nofollow"> Fixed </a> </td>
+ </tr>
+ <tr>
+ <td> Fix breakage with Patrickâ??s re-written f_normalize_filename on mingw32 </td><td class="centeralign"> n/a </td><td> Peter C </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=b6f3379b8144b72492e3a9922939ba99ab4d4480"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=b6f3379b8144b72492e3a9922939ba99ab4d4480"; rel="nofollow"> Fixed </a> </td>
+ </tr>
+ <tr>
+ <td> Fix the â??systemcâ?? gnetlist backend </td><td class="centeralign"> n/a </td><td> Peter C </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=bfd49ad477a49235c3e5ee1eda54e5009f6e347a"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=bfd49ad477a49235c3e5ee1eda54e5009f6e347a"; rel="nofollow"> Mostly fixed </a> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=d13aadcbac4af912e0555b3696b59fc904c6cd9f"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=d13aadcbac4af912e0555b3696b59fc904c6cd9f"; rel="nofollow"> Fixed </a> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=4ff7f410e4e601b85e5b6d0b8d4b6b930e49072b"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=4ff7f410e4e601b85e5b6d0b8d4b6b930e49072b"; rel="nofollow"> Fixed test-suite </a> </td>
+ </tr>
+ <tr>
+ <td> Re-add â??spiceâ?? backend to common tests in gnetlist </td><td class="centeralign"> n/a </td><td> Peter C </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=227e5102e722675c93ecf897b1b1c422dd7f032c"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=227e5102e722675c93ecf897b1b1c422dd7f032c"; rel="nofollow"> Fixed </a> </td>
+ </tr>
+ <tr>
+ <td> Add LiquidPCB backend to common tests in gnetlist </td><td class="centeralign"> n/a </td><td> Peter C </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=55850bb331afc0596a18dac1807a487cb475b30d"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=55850bb331afc0596a18dac1807a487cb475b30d"; rel="nofollow"> Fixed </a> </td>
+ </tr>
+ <tr>
+ <td> Verify gnetlist test-suite passes </td><td class="centeralign"> n/a </td><td> Peter C </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=ba936e6bb6c321b7c9d433a8276d7cccd17c9889"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=ba936e6bb6c321b7c9d433a8276d7cccd17c9889"; rel="nofollow"> Fixed </a> </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> Renderer improvements (invalidate / expose model) </td><td class="centeralign"> n/a </td><td> Peter C </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=9f65e2f99a8c4658fab1b048d76089fc6897384d"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=9f65e2f99a8c4658fab1b048d76089fc6897384d"; rel="nofollow"> Merged </a> </td>
+ </tr>
+</table>
+
+</div>
+<!-- SECTION "1.5.1 (unstable)" [6064-10170] -->
+<h3><a name="unstable1" id="unstable1">1.5.2 (unstable)</a></h3>
+<div class="level3">
+
+<p>
+ Target release date: <strong>December 2008 / January 2009</strong> <br/>
+ Actual release date: <strong>March 28th, 2009</strong>
+</p>
+<table class="inline">
+ <tr>
+ <th class="leftalign"> Description </th><th class="leftalign"> SF bug </th><th class="leftalign"> Developer(s) </th><th class="leftalign"> Status </th>
+ </tr>
+ <tr>
+ <td class="leftalign"> Simplified color maps </td><td class="centeralign"> n/a </td><td class="leftalign"> Peter B </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=06449db86b91db91bf5d4551acc2794cf34c97f1"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=06449db86b91db91bf5d4551acc2794cf34c97f1"; rel="nofollow"> Done </a> </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> Renderer improvements (cairo for static drawing) </td><td class="centeralign"> n/a </td><td class="leftalign"> Peter C </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=6e8513e78fb37bfdeba7254a7670cb86e3608924"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=6e8513e78fb37bfdeba7254a7670cb86e3608924"; rel="nofollow"> Done </a> </td>
+ </tr>
+ <tr>
+ <td> Renderer improvements (cairo for rubberband drawing) </td><td class="centeralign"> n/a </td><td class="leftalign"> Peter C </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=212b0cf870e05a105fc5a6c134b7803cf6c63c28"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=212b0cf870e05a105fc5a6c134b7803cf6c63c28"; rel="nofollow"> Done place </a> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=fef99d7912ebc1feb4890e5babff1772f6b20703"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=fef99d7912ebc1feb4890e5babff1772f6b20703"; rel="nofollow"> Done rubber and stretch </a> </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> Renderer improvements (pango text on screen) </td><td class="rightalign"> </td><td class="leftalign"> Peter C </td><td> 80-90% finished; moved to 1.5.3 </td>
+ </tr>
+ <tr>
+ <td> Renderer improvements (get text bounds from gschem, not libgeda) </td><td class="rightalign"> </td><td class="leftalign"> Peter B, Peter C </td><td class="leftalign"> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=330e6bc49a83a176c549644011d186dbc5e1d8b9"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=330e6bc49a83a176c549644011d186dbc5e1d8b9"; rel="nofollow"> Support </a> But not used yet! </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> Embedding pin label colors </td><td> <a href="https://sourceforge.net/tracker/index.php?func=detail&aid=2157598&group_id=161080&atid=818426"; class="urlextern" title="https://sourceforge.net/tracker/index.php?func=detail&aid=2157598&group_id=161080&atid=818426"; rel="nofollow"> 2157598</a> </td><td> Peter C </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=0029ee5696a4f8c0fd2a0edb64c0096792e24912"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=0029ee5696a4f8c0fd2a0edb64c0096792e24912"; rel="nofollow"> Fixed </a> </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> Selection from inside closed paths </td><td class="centeralign"> n/a </td><td> Ed Hennessy, Peter C </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=7ad1508b5dfa3a38f30176a72b288d5eb68f5050"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=7ad1508b5dfa3a38f30176a72b288d5eb68f5050"; rel="nofollow"> Fixed</a> </td>
+ </tr>
+ <tr>
+ <td> Refactored object hatching (leading to hatched polygons) </td><td class="centeralign"> n/a </td><td> Ed Hennessy, Peter C </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=c01757cd814e7c92cb4c64a6e134aa670b9750d1"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=c01757cd814e7c92cb4c64a6e134aa670b9750d1"; rel="nofollow"> Fixed paths </a> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=3b8bbb1f0e4f549ad2e366e36365e59f7657622e"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=3b8bbb1f0e4f549ad2e366e36365e59f7657622e"; rel="nofollow"> Fixed circles </a> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=54d2fd7dc6bf09dad1d9657c5cd3635bb31e14b7"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=54d2fd7dc6bf09dad1d9657c5cd3635bb31e14b7"; rel="nofollow"> Fixed boxes </a> </td>
+ </tr>
+ <tr>
+ <td> gschem: redraw overlapping objects </td><td> <a href="https://sourceforge.net/tracker/index.php?func=detail&aid=1444319&group_id=161080&atid=818426"; class="urlextern" title="https://sourceforge.net/tracker/index.php?func=detail&aid=1444319&group_id=161080&atid=818426"; rel="nofollow"> 1444319 </a> </td><td> Peter C </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=9f65e2f99a8c4658fab1b048d76089fc6897384d"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=9f65e2f99a8c4658fab1b048d76089fc6897384d"; rel="nofollow"> Fixed </a> </td>
+ </tr>
+ <tr>
+ <td> gschem: Add undo point when editing fill and line styles </td><td> <a href="https://sourceforge.net/tracker2/?func=detail&aid=2344933&group_id=161080&atid=818426"; class="urlextern" title="https://sourceforge.net/tracker2/?func=detail&aid=2344933&group_id=161080&atid=818426"; rel="nofollow"> 2344933 </a> <a href="https://sourceforge.net/tracker2/?func=detail&aid=2344920&group_id=161080&atid=818426"; class="urlextern" title="https://sourceforge.net/tracker2/?func=detail&aid=2344920&group_id=161080&atid=818426"; rel="nofollow"> 2344920 </a> </td><td class="leftalign"> Peter B </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=51a19f38bdff7c3fa3f5656a0e9347b303a2c215"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=51a19f38bdff7c3fa3f5656a0e9347b303a2c215"; rel="nofollow"> Fixed </a> </td>
+ </tr>
+ <tr>
+ <td> Fix redraw of incidentally selected objects when rubberbanding </td><td> <a href="https://sourceforge.net/tracker2/?func=detail&aid=2482746&group_id=161080&atid=818426"; class="urlextern" title="https://sourceforge.net/tracker2/?func=detail&aid=2482746&group_id=161080&atid=818426"; rel="nofollow"> 2482746 </a> </td><td class="leftalign"> Peter C </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=30b150c00aa04b05dd6e85cd5f336f379b4def1b"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=30b150c00aa04b05dd6e85cd5f336f379b4def1b"; rel="nofollow"> Fixed </a> </td>
+ </tr>
+ <tr>
+ <td> Fix hit-detection of mirrored arcs (negative sweep) </td><td class="centeralign"> n/a </td><td class="leftalign"> Peter C </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=ba15c06da1ec82e3ff063e211def6d8a983f1bde"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=ba15c06da1ec82e3ff063e211def6d8a983f1bde"; rel="nofollow"> Fixed </a> </td>
+ </tr>
+ <tr>
+ <td> Fix rubberbanding of mirrored arcs (negative sweep) </td><td class="centeralign"> n/a </td><td class="leftalign"> Peter C </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=7a6b1a22fec9785f503c46d24406046feb04d87f"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=7a6b1a22fec9785f503c46d24406046feb04d87f"; rel="nofollow"> Fixed </a> </td>
+ </tr>
+ <tr>
+ <td> Fix mistakenly changed sizes of circular joint cues </td><td class="centeralign"> n/a </td><td class="leftalign"> Peter C </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=95432ccffdbb39434981f87050433c00f40125da"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=95432ccffdbb39434981f87050433c00f40125da"; rel="nofollow"> Fixed </a> </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> Ensure gnetlist doesnâ??t netlist buses / bus pins </td><td class="centeralign"> n/a </td><td class="leftalign"> Peter C </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=a838dece88323eb782b0ac301c5825ed693fbf0f"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=a838dece88323eb782b0ac301c5825ed693fbf0f"; rel="nofollow"> Fixed </a> </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> <a href="geda-wip-clipboard.html" class="wikilink1" title="geda-wip-clipboard.html">Clipboard support</a> for copy / paste of schematic data between gEDA applications </td><td class="rightalign"> </td><td class="leftalign"> Peter B </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=6a07d737a32a816f43e1f061409a10e616d7aa2a"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=6a07d737a32a816f43e1f061409a10e616d7aa2a"; rel="nofollow"> Done</a> </td>
+ </tr>
+</table>
+
+</div>
+<!-- SECTION "1.5.2 (unstable)" [10171-] --></body>
+</html>
diff --git a/docs/wiki/geda-tragesym_readme.html b/docs/wiki/geda-tragesym_readme.html
new file mode 100644
index 0000000..1d8087c
--- /dev/null
+++ b/docs/wiki/geda-tragesym_readme.html
@@ -0,0 +1,46 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="tragesym_symbol_generator_readme" id="tragesym_symbol_generator_readme">tragesym (symbol generator) README</a></h1>
+<div class="level1">
+<pre class="code">tragesym is a small python script that creates geda symbols out of
+structured textfiles.
+
+For creating a symbol you have to edit the sourcefile first. You can
+use the template.src file, which is in /examples/tragesym/ directory.
+Some examples are in the examples/tragesym directory too.
+
+For possible footprint names take a look into the ~geda directory
+of the PCB program.
+
+usage is:
+ tragesym <sourcefile> <symbolfile>
+
+After you have translated the sourcefile to the symbolfile you have to
+rearrange some pins with gschem, translate the symbol to the origin
+and save it in an appropriate symbol directory. Make the attributes
+visible while doing that (edit->show hidden text) and hide the text
+again before saving.
+
+tragesym requires python (versions greater 1.5 should work).
+
+Comment an questions are welcome.
+Send it to Werner Hoch (werner.ho@xxxxxx)
+</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-tragesym_tutorial.fr.html b/docs/wiki/geda-tragesym_tutorial.fr.html
new file mode 100644
index 0000000..d5dfb24
--- /dev/null
+++ b/docs/wiki/geda-tragesym_tutorial.fr.html
@@ -0,0 +1,258 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#creer_des_symboles_gschem_rapidement_et_facilement_en_utilisant_tragesym_et_un_tableur" class="toc">Créer des symboles gschem rapidement et facilement en utilisant tragesym et un tableur</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#etapes_necessaires" class="toc">�tapes nécessaires</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#etape_1ouvrir_un_fichier_de_formulaire_tragesym" class="toc">Ã?tape 1: Ouvrir un fichier de formulaire tragesym</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#etape_2telecharger_le_fichier_technique_du_composant_et_trouver_la_liste_des_broches" class="toc">�tape 2: Télécharger le fichier technique du composant et trouver la liste des broches</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#etape_3copier_la_liste_des_broches_dans_un_editeur_et_la_preparer" class="toc">�tape 3: Copier la liste des broches dans un éditeur et la préparer</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#etape_4inserer_toutes_les_donnees_manquantes_dans_la_feuille_de_calcul" class="toc">�tape 4: Insérer toutes les données manquantes dans la feuille de calcul</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#etape_5exporter_la_feuille_de_calcul_dans_un_fichier_texte_avec_separation_par_tabulation" class="toc">�tape 5: Exporter la feuille de calcul dans un fichier texte avec séparation par tabulation</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#etape_6lancer_tragesym_et_creer_le_symbole" class="toc">�tape 6: Lancer tragesym et créer le symbole</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#etape_7controler_le_resultat_avec_gschem_et_peaufiner_le_symbole" class="toc">�tape 7: Contrôler le résultat avec gschem et peaufiner le symbole</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#conclusion" class="toc">Conclusion</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#credits" class="toc">Crédits</a></span></div></li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="creer_des_symboles_gschem_rapidement_et_facilement_en_utilisant_tragesym_et_un_tableur" id="creer_des_symboles_gschem_rapidement_et_facilement_en_utilisant_tragesym_et_un_tableur">Créer des symboles gschem rapidement et facilement en utilisant tragesym et un tableur</a></h1>
+<div class="level1">
+
+<p>
+ La création de symboles pour le dessin de schémas peut prendre beaucoup de temps, générer beaucoup dâ??erreurs et de frustrations. Heureusement, gschem utilise un format de fichier texte ouvert qui est très facile à utiliser avec des scripts. Ce tutoriel succint décrit comment utiliser tragesym, un outil extérieur, pour créer des symboles très rapidement (probablement plus rapidement quâ??avec tout paquet commercial).
+</p>
+
+</div>
+<!-- SECTION "Créer des symboles gschem rapidement et facilement en utilisant tragesym et un tableur" [1-532] -->
+<h2><a name="etapes_necessaires" id="etapes_necessaires">�tapes nécessaires</a></h2>
+<div class="level2">
+<ul>
+<li class="level1"><div class="li"> Ã?tape 1: Ouvrir un fichier de formulaire tragesym</div>
+</li>
+<li class="level1"><div class="li"> �tape 2: Télécharger le fichier technique du composant et trouver la liste des broches</div>
+</li>
+<li class="level1"><div class="li"> �tape 3: Copier la liste des broches dans un éditeur et la préparer</div>
+</li>
+<li class="level1"><div class="li"> �tape 4: Insérer toutes les données manquantes dans la feuille de calcul</div>
+</li>
+<li class="level1"><div class="li"> �tape 5: Exporter la feuille de calcul dans un fichier texte avec séparation par tabulation</div>
+</li>
+<li class="level1"><div class="li"> �tape 6: Lancer tragesym et créer le symbole</div>
+</li>
+<li class="level1"><div class="li"> �tape 7: Contrôler le résultat avec gschem et peaufiner le symbole</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "�tapes nécessaires" [533-1094] -->
+<h2><a name="etape_1ouvrir_un_fichier_de_formulaire_tragesym" id="etape_1ouvrir_un_fichier_de_formulaire_tragesym">Ã?tape 1: Ouvrir un fichier de formulaire tragesym</a></h2>
+<div class="level2">
+
+<p>
+ tragesym est fourni avec deux fichiers de formulaires. Lâ??un est en <a href="media/tragesym/template.txt" class="media" target="_blank" title="tragesym:template.txt">texte ASCII</a>, le second est une <a href="media/tragesym/template.ods" class="media" target="_blank" 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>
+<!-- SECTION "Ã?tape 1: Ouvrir un fichier de formulaire tragesym" [1095-1958] -->
+<h2><a name="etape_2telecharger_le_fichier_technique_du_composant_et_trouver_la_liste_des_broches" id="etape_2telecharger_le_fichier_technique_du_composant_et_trouver_la_liste_des_broches">�tape 2: Télécharger le fichier technique du composant et trouver la liste des broches</a></h2>
+<div class="level2">
+
+<p>
+ Pour cet exemple, nous allons créer un symbole avec les ports IO du PCA9555 16-bit IIC IO de Philips Semiconductor. La description du produit et la fiche technique sont disponibles sur Philips : [<a href="http://www-us.semiconductors.philips.com/cgi-bin/pldb/pip/pca9555.html"; class="urlextern" title="http://www-us.semiconductors.philips.com/cgi-bin/pldb/pip/pca9555.html"; rel="nofollow">http://www-us.semiconductors.philips.com/cgi-bin/pldb/pip/pca9555.html</a>]. Téléchargez la fiche technique et ouvrez-la avec un visualiseur pdf qui permet la copie du texte à lâ??extérieur du <acronym title="Portable Document Format">PDF</acronym>, tel que xpdf (téléchargeable sur [<a href="http://www.foolabs.com/xpdf/home.html"; class="urlextern" title="http://www.foolabs.com/xpdf/home.html"; rel="nofollow">http://www.foolabs.com/xpdf/home.html</a>]). Passez les pages jusquâ??à ce que vous ayez trouvé le brochage ou le composant·:
+</p>
+
+<p>
+<a href="media/tragesym/kpdf_pinconfiguration.png" class="media" target="_blank" title="tragesym:kpdf_pinconfiguration.png"><img src="media/tragesym/kpdf_pinconfiguration.png" class="media" alt="" /></a> <a href="media/tragesym/acroread_selectiontable.png" class="media" target="_blank" title="tragesym:acroread_selectiontable.png"><img src="media/tragesym/acroread_selectiontable.png" class="media" alt="" /></a>
+</p>
+
+<p>
+Dans la feuille de calcul, la liste des broches peut être seulement présente dans le dessin du boîtier. Sâ??il existe une belle table, comme dans la second image, dâ??un autre fichie technique, utilisez-la.
+</p>
+
+</div>
+<!-- SECTION "�tape 2: Télécharger le fichier technique du composant et trouver la liste des broches" [1959-2906] -->
+<h2><a name="etape_3copier_la_liste_des_broches_dans_un_editeur_et_la_preparer" id="etape_3copier_la_liste_des_broches_dans_un_editeur_et_la_preparer">�tape 3: Copier la liste des broches dans un éditeur et la préparer</a></h2>
+<div class="level2">
+
+<p>
+ Sélectionnez la liste des broches et copiez-la dans un éditeur de texte. Câ??est une étape intermédiaire nécessaire car votre tableur a besoin de champs séparateurs spéciaux, comme les virgules ou les tabulations. Vous pouvez avoir à enlever les séparateurs en double ou de les remplacer avec des tabulations.
+</p>
+
+<p>
+<strong>Note:</strong> Le comportement lors de la sélection de kpdf est différent de celui de acroread. kpdf semble vous donner une copie qui ressemble plus à une présentation graphique, alors que acroread fournit une sortie qui est plus «·orientée fichier·». Si vous devez créer beaucoup de symboles, testez les deux et comparez les résultats (NdT: xpdf semble fonctionner très bien au 04/12/2006 et reste très léger).
+</p>
+
+<p>
+<a href="media/tragesym/xemacs_rawselection.png" class="media" target="_blank" title="tragesym:xemacs_rawselection.png"><img src="media/tragesym/xemacs_rawselection.png" class="media" alt="" /></a> <a href="media/tragesym/xemacs_modifiedselection.png" class="media" target="_blank" title="tragesym:xemacs_modifiedselection.png"><img src="media/tragesym/xemacs_modifiedselection.png" class="media" alt="" /></a> <a href="media/tragesym/ooo_selection.png" class="media" target="_blank" title="tragesym:ooo_selection.png"><img src="media/tragesym/ooo_selection.png" class="media" alt="" /></a>
+</p>
+
+<p>
+Lâ??image ci-dessus illustre les étapes·:
+</p>
+<ul>
+<li class="level1"><div class="li"> insérez la sélection depuis votre visualiseur pdf vers un éditeur de texte</div>
+</li>
+<li class="level1"><div class="li"> modifiez la liste des broches pour rendre votre tableur heureux </div>
+<ul>
+<li class="level2"><div class="li"> coupez la liste de 24 à 13 avec la sélection rectangulaire</div>
+</li>
+<li class="level2"><div class="li"> insérez la sélection rectangulaire sous les broches 1 à 12</div>
+</li>
+<li class="level2"><div class="li"> triez les lignes (xemacs peut le faire <img src="images/smileys/icon_wink.gif" align="middle" alt=";-)" />)</div>
+</li>
+<li class="level2"><div class="li"> enlevez ou réparez les lignes avec les numéros 2,3,… Ils ne sont pas sur la même ligne. Vous pouvez facilement recréer les numéros de broche plus tard</div>
+</li>
+<li class="level2"><div class="li"> remplacez les espaces avec des tabulations (pas réellement nécessaire en utilisant OpenOffice)</div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> copiez les données modifiées dans le formulaire feuille de calcul quelque part en dessous</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "�tape 3: Copier la liste des broches dans un éditeur et la préparer" [2907-4587] -->
+<h2><a name="etape_4inserer_toutes_les_donnees_manquantes_dans_la_feuille_de_calcul" id="etape_4inserer_toutes_les_donnees_manquantes_dans_la_feuille_de_calcul">�tape 4: Insérer toutes les données manquantes dans la feuille de calcul</a></h2>
+<div class="level2">
+
+<p>
+ Déplacez maintenant les étiquettes et les numéros de broches dans leurs colonnes respectives. Vous pouvez aussi utiliser la fonctionnalité dâ??autoremplissage de votre tableur pour créer les numéros de broche.
+</p>
+
+<p>
+<a href="media/tragesym/ooo_rearanged.png" class="media" target="_blank" title="tragesym:ooo_rearanged.png"><img src="media/tragesym/ooo_rearanged.png" class="media" alt="" /></a>
+</p>
+
+<p>
+Remplissez les colonens de type, de style et de position aux valeurs les plus habituelles. Vous pouvez à nouveau utiliser la fonctionnalité dâ??autoremplissage Maintenant vous allez changer quelques unes de ces valeurs. Jetez un coup dâ??oeil sur le tableau descriptif de la fiche technique:
+</p>
+
+<p>
+<a href="media/tragesym/kpdf_pindescription.png" class="media" target="_blank" title="tragesym:kpdf_pindescription.png"><img src="media/tragesym/kpdf_pindescription.png" class="media" alt="" /></a>
+</p>
+
+<p>
+Selon ce tableau, nous changeons les éléments suivants (voir le résultat ci-dessus):
+</p>
+<ul>
+<li class="level1"><div class="li"> La broche 1 est une sortie, nous voudrions avoir un rond dâ??inversion (NdT: trad à revoir) et une barre de négation</div>
+</li>
+<li class="level1"><div class="li"> A1 à A3 sont des entrées, nous changeons le type et les déplaçons sur le côté gauche</div>
+</li>
+<li class="level1"><div class="li"> mettez le type de SCL en entrée et déplacez aussi SCL et SDA sur le côté gauche </div>
+</li>
+<li class="level1"><div class="li"> changez le type des broches dâ??alimentations VSS et VDD et ajoutez des noms de net. Nous utilisons les habituels GND et Vcc.</div>
+</li>
+</ul>
+
+<p>
+ <strong>Note:</strong> Si une de vos étiquettes contient un backslash «·\·», vous devez le remplacer par sa séquence dâ??échapement «·\\·».
+</p>
+
+<p>
+<a href="media/tragesym/ooo_changedpins.png" class="media" target="_blank" title="tragesym:ooo_changedpins.png"><img src="media/tragesym/ooo_changedpins.png" class="media" alt="" /></a>
+</p>
+
+<p>
+Avant de configurer les attributs et les options aux valeurs appropriées.
+</p>
+
+<p>
+<a href="media/tragesym/ooo_attributes.png" class="media" target="_blank" title="tragesym:ooo_attributes.png"><img src="media/tragesym/ooo_attributes.png" class="media" alt="" /></a>
+</p>
+
+</div>
+<!-- SECTION "�tape 4: Insérer toutes les données manquantes dans la feuille de calcul" [4588-6061] -->
+<h2><a name="etape_5exporter_la_feuille_de_calcul_dans_un_fichier_texte_avec_separation_par_tabulation" id="etape_5exporter_la_feuille_de_calcul_dans_un_fichier_texte_avec_separation_par_tabulation">�tape 5: Exporter la feuille de calcul dans un fichier texte avec séparation par tabulation</a></h2>
+<div class="level2">
+
+<p>
+ Vous pouvez soit utiliser le fonction export de votre tableur pour créer un fichier texte délimité par des tabulations ou simplement sélectionner le tableau et copier son contenu dans votre éditeur de texte et sauvegarder le fichier.
+</p>
+
+</div>
+<!-- SECTION "�tape 5: Exporter la feuille de calcul dans un fichier texte avec séparation par tabulation" [6062-6409] -->
+<h2><a name="etape_6lancer_tragesym_et_creer_le_symbole" id="etape_6lancer_tragesym_et_creer_le_symbole">�tape 6: Lancer tragesym et créer le symbole</a></h2>
+<div class="level2">
+
+<p>
+ Utilisez un shell et exécutez tragesym:
+</p>
+
+<p>
+<code>werner@werner-amd64:~/Desktop/tragesym_tutorial> tragesym pca555.src pca555.sch</code>
+</p>
+
+<p>
+Si tragesym indique quâ??il y a une erreur, faites quelques changements dans la feuille de calcul et exportez à nouveau le fichier ou éditez simplement le fichier exporté.
+</p>
+
+</div>
+<!-- SECTION "�tape 6: Lancer tragesym et créer le symbole" [6410-6771] -->
+<h2><a name="etape_7controler_le_resultat_avec_gschem_et_peaufiner_le_symbole" id="etape_7controler_le_resultat_avec_gschem_et_peaufiner_le_symbole">�tape 7: Contrôler le résultat avec gschem et peaufiner le symbole</a></h2>
+<div class="level2">
+
+<p>
+ Ouvrez maintenant le symbole généré avec et contrôlez le résultat
+</p>
+
+<p>
+<code>werner@werner-amd64:~/Desktop/tragesym_tutorial> gschem pca555.sch</code>
+</p>
+
+<p>
+En validant le texte caché («·en·», Edit→Show/Hide Inv Text), vous pouvez voir le symbole généré en entier. Il nâ??est pas réellement nécessaire de changer quoi que ce soit mais cela peut améliorer lâ??aspect du symbole si vous réarrangez un peu les broches.
+</p>
+
+<p>
+<a href="media/tragesym/gschem_showhidden.png" class="media" target="_blank" title="tragesym:gschem_showhidden.png"><img src="media/tragesym/gschem_showhidden.png" class="media" alt="" /></a> <a href="media/tragesym/gschem_finished.png" class="media" target="_blank" title="tragesym:gschem_finished.png"><img src="media/tragesym/gschem_finished.png" class="media" alt="" /></a>
+</p>
+
+<p>
+Nous avons maintenant un symbole complet. Vous pouvez le copier dans votre bibliothèque locale de symboles, e.g. /usr/local/share/gEDA/sym/local/ et lâ??utiliser.
+</p>
+
+</div>
+<!-- SECTION "�tape 7: Contrôler le résultat avec gschem et peaufiner le symbole" [6772-7503] -->
+<h2><a name="conclusion" id="conclusion">Conclusion</a></h2>
+<div class="level2">
+
+<p>
+ Câ??était un exemple simple avec peu de broches mais cela est dâ??autant plus rentable lorsque vous en avez beaucoup (ie, bga-272, tfqp-100, etc.).
+</p>
+
+</div>
+<!-- SECTION "Conclusion" [7504-7673] -->
+<h2><a name="credits" id="credits">Crédits</a></h2>
+<div class="level2">
+
+<p>
+ De grands remerciements à <Russ.Dill(AT)asu.edu>, qui a écrti la première version de ce tutoriel. Vous pouvez trouver ce tutoriel sur <a href="http://www.geda.seul.org/docs/current/tutorials/tragesym/tragesym.html"; class="urlextern" title="http://www.geda.seul.org/docs/current/tutorials/tragesym/tragesym.html"; rel="nofollow">http://www.geda.seul.org/docs/current/tutorials/tragesym/tragesym.html</a> (version anglaise)
+</p>
+
+<p>
+NdT·: si vous voulez la version française: <a href="http://www.iznogood-factory.org/pub/gEDA/symboles.html"; class="urlextern" title="http://www.iznogood-factory.org/pub/gEDA/symboles.html"; rel="nofollow">http://www.iznogood-factory.org/pub/gEDA/symboles.html</a>
+</p>
+
+</div>
+<!-- SECTION "Crédits" [7674-] --></body>
+</html>
diff --git a/docs/wiki/geda-tragesym_tutorial.html b/docs/wiki/geda-tragesym_tutorial.html
new file mode 100644
index 0000000..c8563b8
--- /dev/null
+++ b/docs/wiki/geda-tragesym_tutorial.html
@@ -0,0 +1,258 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#creating_gschem_symbols_quickly_and_easily_using_tragesym_and_a_spreadsheet_programm" class="toc">Creating gschem symbols quickly and easily using tragesym and a spreadsheet programm</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#required_steps" class="toc">Required Steps</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#step1open_a_tragesym_template_file" class="toc">Step1: Open a tragesym template file</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#step2download_the_part_data_sheet_and_find_the_pin_list" class="toc">Step2: Download the part data sheet and find the pin list</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#step3copy_the_pin_list_into_an_editor_and_prepare_it" class="toc">Step3: Copy the pin list into an editor and prepare it</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#step4insert_all_missing_data_into_the_spreadsheet" class="toc">Step4: Insert all missing data into the spreadsheet</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#step5export_the_spreadsheet_into_a_tab_seperated_text_file" class="toc">Step5: Export the spreadsheet into a tab seperated text file</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#step6execute_tragesym_and_create_the_symbol" class="toc">Step6: execute tragesym and create the symbol</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#step7check_the_result_with_gschem_and_do_some_artwork" class="toc">Step7: check the result with gschem and do some artwork</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#conclusion" class="toc">Conclusion</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#credits" class="toc">Credits</a></span></div></li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="creating_gschem_symbols_quickly_and_easily_using_tragesym_and_a_spreadsheet_programm" id="creating_gschem_symbols_quickly_and_easily_using_tragesym_and_a_spreadsheet_programm">Creating gschem symbols quickly and easily using tragesym and a spreadsheet programm</a></h1>
+<div class="level1">
+
+<p>
+ Creating symbols for schematic capture can be very time consuming, error prone, and an all around pain. Luckily, gschem uses an open, text based file format that is very easy to use with scripting. This short tutorial describes how to use the tragesym script, to create symbols very quickly (probably more quickly than with any commercial package).
+</p>
+
+</div>
+<!-- SECTION "Creating gschem symbols quickly and easily using tragesym and a spreadsheet programm" [1-450] -->
+<h2><a name="required_steps" id="required_steps">Required Steps</a></h2>
+<div class="level2">
+<ul>
+<li class="level1"><div class="li"> Step1: Open a tragesym template file</div>
+</li>
+<li class="level1"><div class="li"> Step2: Download the part data sheet and find the pin list</div>
+</li>
+<li class="level1"><div class="li"> Step3: Copy the pin list into an editor and prepare it</div>
+</li>
+<li class="level1"><div class="li"> Step4: Insert all missing data into the spreadsheet</div>
+</li>
+<li class="level1"><div class="li"> Step5: Export the spreadsheet into a tab seperated text file</div>
+</li>
+<li class="level1"><div class="li"> Step6: execute tragesym and create the symbol</div>
+</li>
+<li class="level1"><div class="li"> Step7: check the result with gschem and do some artwork</div>
+</li>
+</ul>
+
+</div>
+<!-- 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/template2.txt.src" class="media" target="_blank" title="tragesym:template2.txt.src">ASCII text</a>, the second is a <a href="media/tragesym/template2.ods" class="media" target="_blank" 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" [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">
+
+<p>
+ For this example, we will create a symbol from the Philips Semiconductor PCA9555 16-bit IIC IO port. The description of product and datasheet is available at Philips: <a href="http://www-us.semiconductors.philips.com/cgi-bin/pldb/pip/pca9555.html"; class="urlextern" title="http://www-us.semiconductors.philips.com/cgi-bin/pldb/pip/pca9555.html"; rel="nofollow">http://www-us.semiconductors.philips.com/cgi-bin/pldb/pip/pca9555.html</a>. Download the datasheet and open it with a pdf viewer that allows copying text out of the pdf file, such as kpdf or acroread. Flip through the pages until you find the pinout for the device:
+</p>
+
+<p>
+<a href="media/tragesym/kpdf_pinconfiguration.png" class="media" target="_blank" title="tragesym:kpdf_pinconfiguration.png"><img src="media/tragesym/kpdf_pinconfiguration.png" class="media" alt="" /></a> <a href="media/tragesym/acroread_selectiontable.png" class="media" target="_blank" title="tragesym:acroread_selectiontable.png"><img src="media/tragesym/acroread_selectiontable.png" class="media" alt="" /></a>
+</p>
+
+<p>
+Inside the datasheet the pin list may only be in the drawing of the pin configuration. If thereâ??s a nice table, like in the second picture from a different datasheet, use this one.
+</p>
+
+</div>
+<!-- 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">
+
+<p>
+Select the pin list and copy it into a text editor. This intermediate step is required as your spreadsheet programm may need a special field seperator, like comma or tab. You may have to remove duplicate seperators or replace it with tabs.
+</p>
+
+<p>
+<strong>Note:</strong> The selection behaviour of kpdf is different from the acroread viewer. The kpdf viewer seems to give you a copy that looks more like the graphical representation, while the acroread viewer produces an output that is more â??file orderâ?? oriented. If you have to create a lot of symbols, try both and compare the results.
+</p>
+
+<p>
+<a href="media/tragesym/xemacs_rawselection.png" class="media" target="_blank" title="tragesym:xemacs_rawselection.png"><img src="media/tragesym/xemacs_rawselection.png" class="media" alt="" /></a> <a href="media/tragesym/xemacs_modifiedselection.png" class="media" target="_blank" title="tragesym:xemacs_modifiedselection.png"><img src="media/tragesym/xemacs_modifiedselection.png" class="media" alt="" /></a> <a href="media/tragesym/ooo_selection.png" class="media" target="_blank" title="tragesym:ooo_selection.png"><img src="media/tragesym/ooo_selection.png" class="media" alt="" /></a>
+</p>
+
+<p>
+The pictures above illustrate the steps:
+</p>
+<ul>
+<li class="level1"><div class="li"> insert the selection from your pdf viewer into a text editor</div>
+</li>
+<li class="level1"><div class="li"> modify the pinlist to make your spreadsheet programm happy </div>
+<ul>
+<li class="level2"><div class="li"> cut out pinlist 24 to 13 with a rectangular selection</div>
+</li>
+<li class="level2"><div class="li"> insert the rectangular selection below the pins 1 to 12</div>
+</li>
+<li class="level2"><div class="li"> sort the lines (xemacs can do that <img src="images/smileys/icon_wink.gif" align="middle" alt=";-)" />)</div>
+</li>
+<li class="level2"><div class="li"> remove or repair the lines with the numbers 2,3,… They are not in the same line. You can easily recreate the pin numbers later</div>
+</li>
+<li class="level2"><div class="li"> replace the spaces with tabs (not really need when using OpenOffice)</div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> copy the modified data into the spreadsheet template somewhere beside</div>
+</li>
+</ul>
+
+</div>
+<!-- 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">
+
+<p>
+ Now, move the labels into the label column and the pin numbers into the pin number column. You can use the autofill feature of your spreadsheet programm to create the pin numbers, too.
+</p>
+
+<p>
+<a href="media/tragesym/ooo_rearanged.png" class="media" target="_blank" title="tragesym:ooo_rearanged.png"><img src="media/tragesym/ooo_rearanged.png" class="media" alt="" /></a>
+</p>
+
+<p>
+Set the type, style and position column to the most common value. You can use the autofill feature again.
+</p>
+
+<p>
+Now you want to change some fo the values. Take a look at the pin description table in the datasheet:
+</p>
+
+<p>
+<a href="media/tragesym/kpdf_pindescription.png" class="media" target="_blank" title="tragesym:kpdf_pindescription.png"><img src="media/tragesym/kpdf_pindescription.png" class="media" alt="" /></a>
+</p>
+
+<p>
+Regarding to that table we change the following things (see result below):
+</p>
+<ul>
+<li class="level1"><div class="li"> Pin 1 is an output, we like to have a negation bubble and a negation overbar</div>
+</li>
+<li class="level1"><div class="li"> A1 to A3 are inputs, we change the type and move them to the left side</div>
+</li>
+<li class="level1"><div class="li"> set the SCL type to input and move SCL and SDA to the left side, too </div>
+</li>
+<li class="level1"><div class="li"> change the type of the power pins VSS and VDD and add net names. We use the more usual GND and Vcc.</div>
+</li>
+</ul>
+
+<p>
+ <strong>Note:</strong> If one of your pin labels has a backslash â??\â?? inside, you have to replace it with itâ??s escape sequence â??\\â??.
+</p>
+
+<p>
+<a href="media/tragesym/ooo_changedpins.png" class="media" target="_blank" title="tragesym:ooo_changedpins.png"><img src="media/tragesym/ooo_changedpins.png" class="media" alt="" /></a>
+</p>
+
+<p>
+Before going on set the attributes and the options to appropriate values.
+</p>
+
+<p>
+<a href="media/tragesym/ooo_attributes.png" class="media" target="_blank" title="tragesym:ooo_attributes.png"><img src="media/tragesym/ooo_attributes.png" class="media" alt="" /></a>
+</p>
+
+</div>
+<!-- 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">
+
+<p>
+ You can either use the export function of your spreadsheet programm to create a tab seperated textfile or just select the table and copy the content into your text editor and save the file.
+</p>
+
+</div>
+<!-- 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">
+
+<p>
+Use a shell and execute tragesym:
+</p>
+
+<p>
+<code>werner@werner-amd64:~/Desktop/tragesym_tutorial> tragesym pca555.src pca555.sch</code>
+</p>
+
+<p>
+If tragesym says that thereâ??s an error, just make some changes in the spreadsheet and export the file again, or just edit the exported file.
+</p>
+
+</div>
+<!-- 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">
+
+<p>
+ Now open the generated symbol with gschem and check the result
+</p>
+
+<p>
+<code>werner@werner-amd64:~/Desktop/tragesym_tutorial> gschem pca555.sch</code>
+</p>
+
+<p>
+Enabling the hidden text (â??enâ??, Edit→Show/Hide Inv Text), you can see the whole generated symbol. Itâ??s not really necessary to change anything, but it might improve the look of the symbol if you rearange the pins a little bit.
+</p>
+
+<p>
+<a href="media/tragesym/gschem_showhidden.png" class="media" target="_blank" title="tragesym:gschem_showhidden.png"><img src="media/tragesym/gschem_showhidden.png" class="media" alt="" /></a> <a href="media/tragesym/gschem_finished.png" class="media" target="_blank" title="tragesym:gschem_finished.png"><img src="media/tragesym/gschem_finished.png" class="media" alt="" /></a>
+</p>
+
+<p>
+Now we have a complete symbol. You can copy the symbol to your local symbol library e.g. /usr/local/share/gEDA/sym/local/ and use it.
+</p>
+
+</div>
+<!-- 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">
+
+<p>
+This was a simple example with a small pincount, but this method really pays off when you have high pin counts (ie, bga-272, tfqp-100, etc).
+</p>
+
+</div>
+<!-- SECTION "Conclusion" [6261-6425] -->
+<h2><a name="credits" id="credits">Credits</a></h2>
+<div class="level2">
+
+<p>
+Many thanks to <Russ.Dill(AT)asu.edu>, who wrote the first version of this tutorial. You can find that tutorial at <a href="http://www.geda.seul.org/docs/current/tutorials/tragesym/tragesym.html"; class="urlextern" title="http://www.geda.seul.org/docs/current/tutorials/tragesym/tragesym.html"; rel="nofollow">http://www.geda.seul.org/docs/current/tutorials/tragesym/tragesym.html</a>
+</p>
+
+</div>
+<!-- SECTION "Credits" [6426-] --></body>
+</html>
diff --git a/docs/wiki/geda-transistor_guide.html b/docs/wiki/geda-transistor_guide.html
new file mode 100644
index 0000000..03e2480
--- /dev/null
+++ b/docs/wiki/geda-transistor_guide.html
@@ -0,0 +1,127 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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></li>
+<li class="level2"><div class="li"><span class="li"><a href="#special_cases" class="toc">Special Cases</a></span></div></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-2551] -->
+<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 <a href="geda-transistor_guide.html#special_cases" class="wikilink1" title="geda-transistor_guide.html">TO-92o</a> 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" [2552-6414] -->
+<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" [6415-7541] -->
+<h2><a name="special_cases" id="special_cases">Special Cases</a></h2>
+<div class="level2">
+<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" [7542-] --></body>
+</html>
diff --git a/docs/wiki/geda-ubuntu.html b/docs/wiki/geda-ubuntu.html
new file mode 100644
index 0000000..f2fc7dd
--- /dev/null
+++ b/docs/wiki/geda-ubuntu.html
@@ -0,0 +1,35 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+<p>
+ <strong>Ubuntu Install Notes</strong>
+</p>
+
+<p>
+Basic Stable Installation: Use apt-get or synaptic to install a stable version from Debian repositories. (easy). Alternately download a binary .deb from Debian (thanks to Hamish) and you can just sudo dpkg -i <pcb-version.deb>.
+</p>
+
+<p>
+Build Installation: Ubuntu doesnâ??t include everything you need to compile software yourself. Youâ??ll want to install the â??build-essentialâ?? package using apt-get or synaptic to get the basic toolchain working on your machine. (Things like GCC are not inc. in Ubuntu). For a testing maturity level for PCB or geda, build-essential should be all you need.
+</p>
+
+<p>
+Be careful as synaptic can do extreme damage to your system. Do be fooled into replacing libc6 because synaptic will want to remove all applications that depend on it – meaning your entire system.
+</p>
+
+<p>
+<acronym title="Concurrent Versions System">CVS</acronym> Installation: For the <acronym title="Concurrent Versions System">CVS</acronym> version of PCB under Edgy, your ./configure step will require running with switch –enable-maintainer-mode. (more notes needed)
+</p>
+</body>
+</html>
diff --git a/docs/wiki/geda-usage.fr.html b/docs/wiki/geda-usage.fr.html
new file mode 100644
index 0000000..0a2eead
--- /dev/null
+++ b/docs/wiki/geda-usage.fr.html
@@ -0,0 +1,234 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#quelle_est_la_meilleure_maniere_d_apprendre_a_utiliser_geda" class="toc">Quelle est la meilleure manière d'apprendre à utiliser gEDA?</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#a_quoi_ressemble_de_le_flux_de_conception_de_geda" class="toc">Ã? quoi ressemble de le flux de conception de gEDA?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#quelles_sont_les_limitations_pour_les_outils_geda" class="toc">Quelles sont les limitations pour les outils gEDA?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#quels_fichiers_de_configuration_locaux_sont_utilises_pour_un_projet" class="toc">Quels fichiers de configuration locaux sont utilisés pour un projet?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#quels_sont_les_noms_et_les_emplacements_des_fichiers_rc_utilises_avec_les_applications_geda_gaf" class="toc">Quels sont les noms et les emplacements des fichiers RC utilisés avec les applications gEDA/gaf?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#qu_en_est-il_du_gestionnaire_de_projet" class="toc">Qu'en est-il du gestionnaire de projet?</a></span></div></li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="quelle_est_la_meilleure_maniere_d_apprendre_a_utiliser_geda" id="quelle_est_la_meilleure_maniere_d_apprendre_a_utiliser_geda">Quelle est la meilleure manière d'apprendre à utiliser gEDA?</a></h1>
+<div class="level1">
+
+<p>
+La première chose à faire est de lire et comprendre lâ??excellent <a href="geda-gsch2pcb_tutorial.html" class="wikilink1" title="geda-gsch2pcb_tutorial.html">gschem -> gsch2pcb -> PCB</a> tutoriel de Bill Wilson. Cela devrait vous permettre de débuter.
+</p>
+
+<p>
+Allez aussi voir les autres <a href="http://geda.seul.org/docs"; class="urlextern" title="http://geda.seul.org/docs"; rel="nofollow">documentations gEDA</a> disponible sur ce site.
+</p>
+
+<p>
+Néanmoins, peut être que la meilleure voie pour apprendre la suite gEDA est de le télécharger et de lâ??essayer vous-même! Si vous consultez le <a href="http://geda.seul.org/docs/current/tutorials/gsch2pcb/tutorial.html"; class="urlextern" title="http://geda.seul.org/docs/current/tutorials/gsch2pcb/tutorial.html"; rel="nofollow">tutoriel</a> de Bill Wilson en essayant la Suite pour vous-même, vous deviendrez un expert en peu de temps!
+</p>
+
+</div>
+<!-- SECTION "Quelle est la meilleure manière d'apprendre à utiliser gEDA?" [1-690] -->
+<h2><a name="a_quoi_ressemble_de_le_flux_de_conception_de_geda" id="a_quoi_ressemble_de_le_flux_de_conception_de_geda">Ã? quoi ressemble de le flux de conception de gEDA?</a></h2>
+<div class="level2">
+
+<p>
+Vous avez ici un schéma de synthèse pour un flux de création de PCB en utilisant la Suite gEDA:
+</p>
+
+<p>
+<a href="media/geda/design_flow.jpg" class="media" target="_blank" title="geda:design_flow.jpg"><img src="media/geda/design_flow.jpg" class="media" alt="" /></a>
+</p>
+
+<p>
+Mis en mots, le flux de conception pour un PCB simple se fait de la manière suivante:
+</p>
+<ol>
+<li class="level1"><div class="li"> Créez vos schémas en utilisant « gschem ».</div>
+</li>
+<li class="level1"><div class="li"> Contrôlez vos schémas avec le vérificateur de DRC. Vous pouvez apprendre à le maîtriser <a href="geda-faq-attribs.html#how_do_i_check_my_schematics" class="wikilink1" title="geda-faq-attribs.html">ici</a>.</div>
+</li>
+<li class="level1"><div class="li"> Assigner des références à vos composants en utilisant « grenum » ou « refdes_renum » (ou simplement les attacher depuis « gschem »).</div>
+</li>
+<li class="level1"><div class="li"> Assignez dâ??autres attributs de composants (tels que des empreintes) en utilisant « gattrib » (ou attachez les simplement manuellement en utilisant « gschem »).</div>
+</li>
+<li class="level1"><div class="li"> Créez un fichier préliminaire de synthèse et faites une netlist en utilisant « gsch2pcb ».</div>
+</li>
+<li class="level1"><div class="li"> Disposez les composants et routez les connexions de votre carte en utilisant « pcb ».</div>
+</li>
+<li class="level1"><div class="li"> Sortez les Gerbers depuis « pcb » en utilisant « File â??Print layout » et sélectionnez « Gerber/RS274X » comme type de fichier de sortie.</div>
+</li>
+</ol>
+
+<p>
+ Si vous faites des changements ou des ajouts à votre schéma ou des attributs, mettez votre fichier PCB comme ceci:
+</p>
+<ol>
+<li class="level1"><div class="li"> �ditez votre schéma et/ou les attributs (« gschem » ou « gattrib »).</div>
+</li>
+<li class="level1"><div class="li"> Contrôlez votre schéma avec le contrôleur de DRC. Vous pouvez apprendre à le maîtriser <a href="geda-faq-attribs.html#how_do_i_check_my_schematics" class="wikilink1" title="geda-faq-attribs.html">ici</a>.</div>
+</li>
+<li class="level1"><div class="li"> Annotez directement vos changements en utilisant « gsch2pcb ».</div>
+</li>
+<li class="level1"><div class="li"> Depuis « pcb », mettez à jour vos composants en utilisant « File â??Load layout data to paste buffer » puis cliquez sur la zone de dessin pour placer les composants.</div>
+</li>
+<li class="level1"><div class="li"> Depuis « pcb », mettez à jour votre netlist en utilisant « File â??Load netlist file ».</div>
+</li>
+</ol>
+
+<p>
+ Habituellement, les utilisateurs invoquent les outils individuels depuis la ligne de commande. Un gestionnaire de projet (« geda ») existe mais a besoin dâ??être amélioré.
+</p>
+
+</div>
+<!-- SECTION "Ã? quoi ressemble de le flux de conception de gEDA?" [691-2693] -->
+<h2><a name="quelles_sont_les_limitations_pour_les_outils_geda" id="quelles_sont_les_limitations_pour_les_outils_geda">Quelles sont les limitations pour les outils gEDA?</a></h2>
+<div class="level2">
+
+<p>
+La chose la plus importante à garder en mémoire à propos des limitations de gEDA est ceci: GEDA est un projet de logiciel open-source. Il possède quelques limitations mais contrairement à celles des logiciels commerciaux, ses limitations ne sont pas artificielles, arbitraires ou pilotées par le marketing. Ceci étant, gEDA nâ??est ni un nagware, ni un crippleware, ni un demoware, ni une « version étudiante limitée ». Toutes les limitations des outils gEDA existent car les programmeurs nâ??ont pas encore implementé ces fonctionnalités particulières. Comme le code est ouvert à tous pour la modification, tout le monde est le bienvenu sâ??il veut implémenter de nouvelles fonctionnalités ou supprimer des limitations puis de soumettre leurs patches au projet. Si vous êtes un hacker et que vous êtes intéressés pour une contribution au projet gEDA, veuillez considérer effacer une des limitations listée ci-dessous! Vous vous ferez un tas dâ??amis et gagnerez une notoriété internationale!
+</p>
+<ul>
+<li class="level1"><div class="li"> Le support hiérarchique de bus: Le support pour les bus hiérarchiques nâ??existe pas encore.</div>
+</li>
+<li class="level1"><div class="li"> Les attributs de nets et de broches dans gattrib: Lâ??attachement des attributs de routage pour les nets et les broches dans gattrib reste à faire. (Les attributs de net sont utiles pour les schémas à haute vitesse. Par exemple, il est souvent important que toutes les pistes dâ??un bus aient la même longueur électrique. Malheureusement, il nâ??est pas certain que PCB supprte actuellement ces attributs de routage.)</div>
+</li>
+<li class="level1"><div class="li"> La rétro-annotation depuis PCB vers gschem. Le support pour la permutation de broche et les modifications du fichier de conception de pcb avec les rétro-annotations induites vers gschem reste à faire.</div>
+</li>
+<li class="level1"><div class="li"> Le gestionnaire de projet « geda » est obsolète et nécessite une mise à jour.</div>
+</li>
+<li class="level1"><div class="li"> Le nombre de couches dans PCB: Actuellement, le nombre de couche de PCB est limité à 8 (ce qui est plus que adéquat pour les projets de petite et moyenne taille). Les développeurs de PCB travaillent sur lâ??augmentation du nombre de couches vers un nombre indéfini mais ce nâ??est pas encore fait. Contactez-les directement si vous êtes intéressés par ce projet.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Quelles sont les limitations pour les outils gEDA?" [2694-4952] -->
+<h2><a name="quels_fichiers_de_configuration_locaux_sont_utilises_pour_un_projet" id="quels_fichiers_de_configuration_locaux_sont_utilises_pour_un_projet">Quels fichiers de configuration locaux sont utilisés pour un projet?</a></h2>
+<div class="level2">
+
+<p>
+Une conception typique de PCB nécessite les fichiers de config suivants dans votre répertoire local:
+</p>
+<ul>
+<li class="level1"><div class="li"> gafrc: il contient les infos de configuration pour les programmes gEDA/gaf (i.e. gschem, gattrib, gnetlist, etc.). Il doit contenir des pointeurs de votre répertoire de symbole local (si vous en avez).</div>
+</li>
+<li class="level1"><div class="li"> attribs: si vous utilisez « gnetlist -g bom2 » pour créer un projet BOM (« Bill Of Material »: liste des éléments) puis vous avez besoin de ce fichier de manière à spéficier quels attributs sont écrits dans la BOM.</div>
+</li>
+<li class="level1"><div class="li"> projectrc: lorsque vous faites un pcb, « gsch2pcb projectrc » est une manière pratique de spécifier les chemins aux répertoires locaux dâ??empreintes, de même que les autres informations de configuration pour « gsch2pcb ». Notez que ce ficheir peut avoir tout nom que vous lui choisissez; jâ??aime utiliser projectrc comme son nom est suggestif de sa fonction.</div>
+</li>
+</ul>
+
+<p>
+ Des informations plus détaillées à propos de chaque fichier de configuration est fourni dans la <a href="http://geda.seul.org/docs/index.html"; class="urlextern" title="http://geda.seul.org/docs/index.html"; rel="nofollow">documentation</a> pour chaque élément.
+</p>
+
+</div>
+<!-- SECTION "Quels fichiers de configuration locaux sont utilisés pour un projet?" [4953-6122] -->
+<h2><a name="quels_sont_les_noms_et_les_emplacements_des_fichiers_rc_utilises_avec_les_applications_geda_gaf" id="quels_sont_les_noms_et_les_emplacements_des_fichiers_rc_utilises_avec_les_applications_geda_gaf">Quels sont les noms et les emplacements des fichiers RC utilisés avec les applications gEDA/gaf?</a></h2>
+<div class="level2">
+
+<p>
+Les diverses applications gEDA/gaf (gschem, gattrib, gnetlist, etc.) utilisent un jeu de fichiers RC pour initialiser différentes options configurables dans les outils eux-mêmes. Ces fichiers RC sont lus par chaque application lors de leur démarrage. Philosophiquement, il existe trois endroits où une application gEDA/gaf va chercher des fichiers RC:
+</p>
+<ul>
+<li class="level1"><div class="li"> Dans le répertoire dâ??installation du système: <strong><code>${prefix}/share/gEDA/</code></strong>. Cet endroit contient les fichiers RC globaux du système et à tous les utilisateurs. Ces fichiers RC doivent être trouvés et chargés avec succès pour que les applications gEDA fonctionnent correctement. <strong><code>${prefix}</code></strong> est initialisé avec le chemin où gEDA/gaf est installé.</div>
+</li>
+<li class="level1"><div class="li"> Dans le répertoire utilisateur: <strong><code>$HOME/.gEDA/</code></strong>. Cet endroit garde les fichiers RC qui sâ??appliquent à tous les projets dâ??utilisateurs. <strong><code>.gEDA</code></strong> est un répertoire. Ces fichiers sont optionels. Ne faites pas que placer une copie du system-gschemrc (ou un autre) dans ce répertoire; ceci ne fonctionnera pas correctement. La bonne chose à faire est de dépasser les choses spécifiques que vous voulez changer.</div>
+</li>
+<li class="level1"><div class="li"> Dans le répertoire local du projet. Cet endroit contient les fichiers RC qui sâ??appliquent au projet local (placé dans ce même répertoire). Ces fichiers RC fournissent des dépassements spécifiques, tels que des bibliothèques de composants ou de sources. Ce fichier est aussi optionel. Ne faites pas que placer une copie de system-gschemrc (ou un autre) dans ce répertoire; il ne fonctionnera pas correctement.</div>
+</li>
+</ul>
+
+<p>
+ Le système de fichier RC a évolué au fil du temps. Originellement, chaque application gEDA/gaf a utilisé ses propres fichiers RC (par exemple, gschem utilise gschemrc, gnetlist utilise gnetlistrc et ainsi de suite). Nénmoins, avec lâ??augmentation du nombre des applications gEDA/gaf, il est devenu clair que les fichiers RC individuels contenaient un lot dâ??informations redondantes et que les nouveaux utilisateurs étaient perturbés par les différents fichiers RC. Câ??est la raison pour laquelle les différents fichiers RC ont été compactés en un seul fichier, appelé « gafrc ». Néanmoins, comme gschem a besoin de tous les types de personalisations spéciaux, nous avons décidé de garder le gschemrc système en plus de tous les fichiers gafrc. Aussi, de manière à préserver une compatibilité arrière, lâ??ancien fichier RC système est encore maintenu dans le répertoire système. En conséquence, le fichier de configuration RC actuel ressemble à ceci:
+</p>
+<ul>
+<li class="level1"><div class="li"> Dans le répertoire dâ??installation du système:</div>
+<ul>
+<li class="level2"><div class="li"> <strong><code>system-gafrc</code></strong> â?? Il contient la plupart des initialisations globales de gaf.</div>
+</li>
+<li class="level2"><div class="li"> <strong><code>system-gattribrc</code></strong></div>
+</li>
+<li class="level2"><div class="li"> <strong><code>system-gnetlistrc</code></strong></div>
+</li>
+<li class="level2"><div class="li"> <strong><code>system-gschemrc</code></strong> â?? Il contient de nombreuses configurations spécifiques à gschem</div>
+</li>
+<li class="level2"><div class="li"> <strong><code>system-gschlasrc</code></strong></div>
+</li>
+<li class="level2"><div class="li"> <strong><code>system-gsymcheckrc</code></strong></div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> Dans le répertoire <strong><code>${HOME}</code></strong> de lâ??utilisateur:</div>
+<ul>
+<li class="level2"><div class="li"> <strong><code>.gEDA/gafrc</code></strong></div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> Dans le répertoire local du projet:</div>
+<ul>
+<li class="level2"><div class="li"> <strong><code>gafrc</code></strong> â?? Il devrait contenir les dépassements locaux, tels que les pointeurs vers les symboles localement définis.</div>
+</li>
+</ul>
+</li>
+</ul>
+
+<p>
+ Les définitions de couleurs gschem-darkbg ou gschem-lightbg sont aussi chargées par le system-gschemrc.
+</p>
+
+<p>
+Finalement, notez que les applications gEDA/gaf recherchent jusquâ??à six fichiers de configuration au démarrage:
+</p>
+<ol>
+<li class="level1"><div class="li"> <strong><code>system-gafrc</code></strong></div>
+</li>
+<li class="level1"><div class="li"> <strong><code>system-gschemrc</code></strong> (ou un autre)</div>
+</li>
+<li class="level1"><div class="li"> <strong><code>${HOME}/.geda/gafrc</code></strong></div>
+</li>
+<li class="level1"><div class="li"> <strong><code>${HOME}/.geda/gschemrc</code></strong> (ou un autre)</div>
+</li>
+<li class="level1"><div class="li"> <strong><code>./gafrc</code></strong></div>
+</li>
+<li class="level1"><div class="li"> <strong><code>./gschemrc</code></strong> (ou un autre)</div>
+</li>
+</ol>
+
+<p>
+ Si vous obtenez un avertissement comme quoi votre application ne peut pas trouver lâ??un ou lâ??autre de ces fichiers, ne vous inquiétez pas. La plupart dâ??entre eux sont optionels. Les seuls fichiers nécessaires sont les fichiers RC systèmes.
+</p>
+
+</div>
+<!-- SECTION "Quels sont les noms et les emplacements des fichiers RC utilisés avec les applications gEDA/gaf?" [6123-10078] -->
+<h2><a name="qu_en_est-il_du_gestionnaire_de_projet" id="qu_en_est-il_du_gestionnaire_de_projet">Qu'en est-il du gestionnaire de projet?</a></h2>
+<div class="level2">
+
+<p>
+Les composants individuels dans la suite de conception de gEDA ne forment pas un projet de bout en bout. A la place, ils traitent leurs propres fichiers (i.e. « gschem » â?? .sch, « pcb » â?? .pcb). Néanmoins, il existe un gestionnaire de projet appelé « geda », que vous pouvez invoquer depuis le ligne de commande. Son but est de vous faciliter la gestion de votre idée comme un tout depuis le concept, en passant par la saisie de schéma, lâ??attachement dâ??attributs, le placement, la génération de BOM, ainsi de suite.
+</p>
+
+<p>
+Malheureusement, le développement de « geda » nâ??a pas suivi le reste de gEDA/gaf. En particulier, « geda » nâ??utilise pas les derniers outils ou méthodes pour réaliser les tâches individuelles. Câ??est la raison pour laquelle nous recommandons aux utilisateurs dâ??utiliser les outils individuels (i.e. gschem, gattrib, gnetlist, gsch2pcb, etc) depuis la ligne de commande. Câ??est pourquoi, si vous êtes un hacker à la recherche dâ??un petit projet à adopter, améliorer « geda » serait une belle introduction à la Suite gEDA et vous vous feriez un tas dâ??amis en le faisant!
+</p>
+
+</div>
+<!-- SECTION "Qu'en est-il du gestionnaire de projet?" [10079-] --></body>
+</html>
diff --git a/docs/wiki/geda-usage.html b/docs/wiki/geda-usage.html
new file mode 100644
index 0000000..1ff47dc
--- /dev/null
+++ b/docs/wiki/geda-usage.html
@@ -0,0 +1,262 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#what_s_the_best_way_to_learn_to_use_geda" class="toc">What's the best way to learn to use gEDA?</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#what_does_the_design_flow_in_geda_look_like" class="toc">What does the design flow in gEDA look like?</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#what_limitations_exist_for_the_geda_tools" class="toc">What limitations exist for the gEDA tools?</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#what_local_configuration_files_are_used_for_a_project" class="toc">What local configuration files are used for a project?</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#what_are_the_names_and_locations_of_the_rc_files_used_with_geda_gaf_applications" class="toc">What are the names and locations of the RC files used with gEDA/gaf applications?</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#what_about_a_project_manager" class="toc">What about a project manager?</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#can_we_change_geda_to_use_an_xml_file_format" class="toc">Can we change gEDA to use an XML file format?</a></span></div></li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="what_s_the_best_way_to_learn_to_use_geda" id="what_s_the_best_way_to_learn_to_use_geda">What's the best way to learn to use gEDA?</a></h1>
+<div class="level1">
+
+<p>
+The first thing to do is to read and understand Bill Wilsonâ??s excellent <a href="geda-gsch2pcb_tutorial.html" class="wikilink1" title="geda-gsch2pcb_tutorial.html">gschem -> gsch2pcb -> PCB</a> tutorial and/or the DJ Delorieâ??s <a href="http://www.delorie.com/pcb/docs/gs/gs.html"; class="urlextern" title="http://www.delorie.com/pcb/docs/gs/gs.html"; rel="nofollow">pcb tutorial</a>. This should get you started.
+</p>
+
+<p>
+Also be sure to check out the other <a href="http://geda.seul.org/docs"; class="urlextern" title="http://geda.seul.org/docs"; rel="nofollow">gEDA documentation</a> available on this website.
+</p>
+
+<p>
+However, the best way to learn the gEDA Suite is to download it and try it out yourself! If you consult Bill Wilsonâ??s tutorial while trying the suite for yourself, you will become an expert in no time!
+</p>
+
+</div>
+<!-- SECTION "What's the best way to learn to use gEDA?" [1-627] -->
+<h1><a name="what_does_the_design_flow_in_geda_look_like" id="what_does_the_design_flow_in_geda_look_like">What does the design flow in gEDA look like?</a></h1>
+<div class="level1">
+
+<p>
+Here is a quick graphic for simple PCB design flow using the gEDA Suite:
+</p>
+
+<p>
+<a href="media/geda/design_flow.jpg" class="media" target="_blank" title="geda:design_flow.jpg"><img src="media/geda/design_flow.jpg" class="media" alt="" /></a>
+</p>
+
+<p>
+In words, the design flow for a simple PCB proceeds as follows:
+</p>
+<ol>
+<li class="level1"><div class="li"> Create your schematic using â??gschemâ??.</div>
+</li>
+<li class="level1"><div class="li"> Check your schematics with the DRC checker. Learn about it <a href="geda-faq-attribs.html#how_do_i_check_my_schematics" class="wikilink1" title="geda-faq-attribs.html">here</a>.</div>
+</li>
+<li class="level1"><div class="li"> Assign reference designators to your components using â??grenumâ?? or â??refdes_renumâ?? (or just attach them manually from within â??gschemâ??).</div>
+</li>
+<li class="level1"><div class="li"> Assign other component attributes (such as component footprints) using â??gattribâ?? (or just attach them manually using â??gschemâ??).</div>
+</li>
+<li class="level1"><div class="li"> Create a preliminary layout file and netlist using â??gsch2pcbâ??.</div>
+</li>
+<li class="level1"><div class="li"> Lay out and route your board using â??pcbâ??.</div>
+</li>
+<li class="level1"><div class="li"> Output Gerbers from within â??pcbâ?? using â??File â?? print layoutâ??, and select â??Gerber/RS274Xâ?? as the output file type.</div>
+</li>
+</ol>
+
+<p>
+ If you make changes, or add to your schematic or attributes while in layout, update your board file like this:
+</p>
+<ol>
+<li class="level1"><div class="li"> Edit your schematic and/or attributes (â??gschemâ?? or â??gattribâ??).</div>
+</li>
+<li class="level1"><div class="li"> Check your schematics with the DRC checker. Learn about it <a href="geda-faq-attribs.html#how_do_i_check_my_schematics" class="wikilink1" title="geda-faq-attribs.html">here</a>.</div>
+</li>
+<li class="level1"><div class="li"> Forward annotate your changes using â??gsch2pcbâ??.</div>
+</li>
+<li class="level1"><div class="li"> From within â??pcbâ??, update your components using â??File â?? load layout data to paste bufferâ??, and then click on the drawing area to place the components.</div>
+</li>
+<li class="level1"><div class="li"> From within â??pcbâ??, update your netlist using â??File â?? load netlist fileâ??.</div>
+</li>
+</ol>
+
+<p>
+ Usually, users invoke the individual tools from the command line. A project manager (â??gedaâ??) exists, but needs improvement.
+</p>
+
+</div>
+<!-- SECTION "What does the design flow in gEDA look like?" [628-2303] -->
+<h1><a name="what_limitations_exist_for_the_geda_tools" id="what_limitations_exist_for_the_geda_tools">What limitations exist for the gEDA tools?</a></h1>
+<div class="level1">
+
+<p>
+The most important thing to keep in mind about gEDAâ??s limitations is this: GEDA is an open-source software project. It has some limitations, but unlike many instances of commerical software, its limitations are not artificial, arbitrary, or driven by marketeering. That is, gEDA is neither nagware, crippleware, demoware, nor â??limited student editionâ??-ware. Any limitations to the gEDA tools exist because the programmers havenâ??t yet implemented that particular feature. Since the code is open for all to see and modify, anybody is welcome to implement a new feature or remove a limitation, and then submit their patches to the project. If you are a hacker and are interested in making a contribution to the gEDA project, consider tackling one of the limitations listed below! You will make a lot of friends, and earn international exposure!
+</p>
+<ul>
+<li class="level1"><div class="li"> Hierarchical bus support: Support for hierarchical busses doesnâ??t exist yet.</div>
+</li>
+<li class="level1"><div class="li"> Net and pin attributes in gattrib: Attaching routing attributes for nets and pins in gattrib remains TBD. (Net attributes are useful for high-speed design. For example, itâ??s often important that all tracks in a bus have the same electrical length. Unfortunately, itâ??s not clear that PCB will support these routing attributes right now.)</div>
+</li>
+<li class="level1"><div class="li"> Backannotation from PCB to gschem. Support for pinswapping and modification of the design file in pcb with subsequent backanno to gschem is TBD.</div>
+</li>
+<li class="level1"><div class="li"> The project manager â??gedaâ?? is out of date, and needs an update.</div>
+</li>
+<li class="level1"><div class="li"> Layer count in PCB: Currently, the layer count in PCB is limited to 16 layers plus two silk layers by default. This is more than adequate for small- and mid-sized projects. If necessary, the number of layers can be increased arbitrarily at compile time. </div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "What limitations exist for the gEDA tools?" [2304-4119] -->
+<h1><a name="what_local_configuration_files_are_used_for_a_project" id="what_local_configuration_files_are_used_for_a_project">What local configuration files are used for a project?</a></h1>
+<div class="level1">
+
+<p>
+A typical PCB design requires the following config files in your local directory:
+</p>
+<ul>
+<li class="level1"><div class="li"> gafrc: This holds configuration info for the gEDA/gaf programs (i.e. gschem, gattrib, gnetlist, etc.). It should hold pointers to your local symbol directory (if any).</div>
+</li>
+<li class="level1"><div class="li"> attribs: If you use â??gnetlist -g bom2â?? to create a project BOM, then you need this file in order to specify which attributes are written into the BOM.</div>
+</li>
+<li class="level1"><div class="li"> projectrc: When going to layout, â??gsch2pcb projectrcâ?? is a convenient way to specify paths to local footprint directories, as well as hold other configuration information for â??gsch2pcbâ??. Note that this file may have any name you choose; I like to use projectrc since its name is suggestive of its function.</div>
+</li>
+</ul>
+
+<p>
+ Further detailed information about each configuration file is provided in the <a href="http://geda.seul.org/docs/index.html"; class="urlextern" title="http://geda.seul.org/docs/index.html"; rel="nofollow">documentation</a> for each facility.
+</p>
+
+</div>
+<!-- SECTION "What local configuration files are used for a project?" [4120-5076] -->
+<h1><a name="what_are_the_names_and_locations_of_the_rc_files_used_with_geda_gaf_applications" id="what_are_the_names_and_locations_of_the_rc_files_used_with_geda_gaf_applications">What are the names and locations of the RC files used with gEDA/gaf applications?</a></h1>
+<div class="level1">
+
+<p>
+The various gEDA/gaf applications (gschem, gattrib, gnetlist, etc.) use a set of RC files to set various configurable options in the tools themselves. These RC files are read in by each application upon start-up. Philosophically, there are three places where a gEDA/gaf application looks for RC files:
+</p>
+<ul>
+<li class="level1"><div class="li"> In the system installation directory: <strong><code>${prefix}/share/gEDA/</code></strong>. This location holds RC files which are global to the entire system, and are common to all users. These RC files must be found and successfully loaded for the gEDA application to work properly. <strong><code>${prefix}</code></strong> is set to the path where you installed gEDA/gaf.</div>
+</li>
+<li class="level1"><div class="li"> In the userâ??s home directory: <strong><code>$HOME/.gEDA/</code></strong>. This location holds RC files which apply to all of this userâ??s projects. <strong><code>.gEDA</code></strong> is a directory. These files are optional. Do not just place a copy of the system-gschemrc (or whatever) into this directory; this will not work properly. The right thing to do is to override specific things you want to change.</div>
+</li>
+<li class="level1"><div class="li"> In the local project directory. This location holds RC files which apply to the local project (which also lives in this directory). These RC files provide specific overrides, such as component or source libraries. This file is also optional. Do not just place a copy of the system-gschemrc (or whatever) into this directory; this will not work properly.</div>
+</li>
+</ul>
+
+<p>
+ The RC file system has evolved over time. Originally, each gEDA/gaf application used its own RC file (for example, gschem used gschemrc, gnetlist used gnetlistrc, and so on). However, as the number of gEDA/gaf applications grew, it became clear that the individual RC files held a lot of redundant information, and that new users were confused by all the different RC files. Therefore, the different RC files were consolidated into a single file, called â??gafrcâ??. However, because gschem needs all kind of special customizations, we decided to keep the system gschemrc in addition to all the gafrc files. Also, in order to preserve backwards compatibility, the old RC file system is still maintained in the system directory. Accordingly, the current RC file configuration looks like this:
+</p>
+<ul>
+<li class="level1"><div class="li"> In the system installation directory:</div>
+<ul>
+<li class="level2"><div class="li"> <strong><code>system-gafrc</code></strong> â?? This contains most of the global gaf settings.</div>
+</li>
+<li class="level2"><div class="li"> <strong><code>system-gattribrc</code></strong></div>
+</li>
+<li class="level2"><div class="li"> <strong><code>system-gnetlistrc</code></strong></div>
+</li>
+<li class="level2"><div class="li"> <strong><code>system-gschemrc</code></strong> â?? This contains lots of settings specific to gschem</div>
+</li>
+<li class="level2"><div class="li"> <strong><code>system-gschlasrc</code></strong></div>
+</li>
+<li class="level2"><div class="li"> <strong><code>system-gsymcheckrc</code></strong></div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> In the userâ??s <strong><code>${HOME}</code></strong> directory:</div>
+<ul>
+<li class="level2"><div class="li"> <strong><code>.gEDA/gafrc</code></strong></div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> In the local project directory:</div>
+<ul>
+<li class="level2"><div class="li"> <strong><code>gafrc</code></strong> â?? This should contain your local overrides, such as pointers to locally defined symbols.</div>
+</li>
+</ul>
+</li>
+</ul>
+
+<p>
+ Also loaded by the system-gschemrc is the gschem-darkbg or gschem-lightbg color definitions.
+</p>
+
+<p>
+Finally, note that gEDA/gaf applications will look for up to six configuration files upon startup:
+</p>
+<ol>
+<li class="level1"><div class="li"> <strong><code>system-gafrc</code></strong></div>
+</li>
+<li class="level1"><div class="li"> <strong><code>system-gschemrc</code></strong> (or whatever)</div>
+</li>
+<li class="level1"><div class="li"> <strong><code>${HOME}/.gEDA/gafrc</code></strong></div>
+</li>
+<li class="level1"><div class="li"> <strong><code>${HOME}/.gEDA/gschemrc</code></strong> (or whatever)</div>
+</li>
+<li class="level1"><div class="li"> <strong><code>./gafrc</code></strong></div>
+</li>
+<li class="level1"><div class="li"> <strong><code>./gschemrc</code></strong> (or whatever)</div>
+</li>
+</ol>
+
+<p>
+ If you get a warning that your app canâ??t find one or another of these files, donâ??t worry. Most of them are optional. The only required files are the system RC files.
+</p>
+
+</div>
+<!-- SECTION "What are the names and locations of the RC files used with gEDA/gaf applications?" [5077-8455] -->
+<h1><a name="what_about_a_project_manager" id="what_about_a_project_manager">What about a project manager?</a></h1>
+<div class="level1">
+
+<p>
+The individual components in the gEDA design suite do not have the concept of an end-to-end project. Rather, they deal with their own files (e.g. â??gschemâ?? â?? .sch, â??pcbâ?? â?? .pcb). However, there is a project manager, called â??gedaâ??, which you can invoke from the command line. Itâ??s goal is to help manage your design as a whole as you take it from concept, through schematic capture, attribute attachment, layout, BOM generation, and so on.
+</p>
+
+<p>
+Unfortunately, development of â??gedaâ?? has not kept up with the rest of gEDA/gaf. In particular, â??gedaâ?? does not use the latest tools or methods to accomplish the individual design tasks. Therefore, we recommend that user simply invoke the individual tools (e.g. gschem, gattrib, gnetlist, gsch2pcb, etc) from the command line. Meanwhile, if your are a hacker are looking for a smallish project to adopt, polishing up â??gedaâ?? would make a nice introduction to the gEDA Suite, and you would make a lot of friends by doing so!
+</p>
+
+</div>
+<!-- SECTION "What about a project manager?" [8456-9491] -->
+<h1><a name="can_we_change_geda_to_use_an_xml_file_format" id="can_we_change_geda_to_use_an_xml_file_format">Can we change gEDA to use an XML file format?</a></h1>
+<div class="level1">
+
+<p>
+We have a recurrent debate about <acronym title="Extensible Markup Language">XML</acronym> file formats on geda-user every two or three years. I think it has to do with how long it takes us to lose our institutional memory due to churn on the mailing list.
+</p>
+
+<p>
+Itâ??s unlikely the gEDA Project will ever switch to an <acronym title="Extensible Markup Language">XML</acronym> file format for schematics or symbols, so get used to it. Some reasons against <acronym title="Extensible Markup Language">XML</acronym> are:
+</p>
+<ol>
+<li class="level1"><div class="li"> GEDA/gaf already has a fixed, well documented, <acronym title="American Standard Code for Information Interchange">ASCII</acronym> file format. Itâ??s over 8 years old as of 2007. Itâ??s well used and well tested.</div>
+</li>
+<li class="level1"><div class="li"> We already have a parser for our file format. Itâ??s lightweight & thoroughly debugged.</div>
+</li>
+<li class="level1"><div class="li"> There are lots of legacy designs using the file format out there already. People would scream if we switched file formats since their old designs would become obsolete. And supporting two file formats – old and new – would be a major <acronym title="Pain in the Ass">PITA</acronym>.</div>
+</li>
+<li class="level1"><div class="li"> <acronym title="Extensible Markup Language">XML</acronym> is a generalized file format. Therefore, <acronym title="Extensible Markup Language">XML</acronym> files tend to become bloated pigs. The gEDA file format is light & well adapted to its purpose: representing graphical information pertainent to schematic diagrams in electronics.</div>
+</li>
+<li class="level1"><div class="li"> One purported benefit for <acronym title="Extensible Markup Language">XML</acronym> files is that there are lots of open-source parsers for them available, making integration into libgeda trivial. Thatâ??s the theory, but in reality the job of a parser is to analyze and parse the input, and then stick it into datastructures suitable for use with the rest of gschemâ??s code. An open-source parser does about 1/3 of the job we need (i.e. reading & analyzing the file, and creating some kind of parse tree). The rest of the job involves putting the stuff in the parse tree into libgedaâ??s data structures. Thatâ??s lots of work. Therefore, the purported advantage of the freely-available <acronym title="Extensible Markup Language">XML</acronym> parser is a chimera. Yes, <acronym title="Extensible Markup Language">XML</acronym> may be of interest for a new program written from the ground up, but not for an existing program like gEDA.</div>
+</li>
+<li class="level1"><div class="li"> GEDA developer time is better used on implementing new features like backannotation. Using developer time on porting our file format to <acronym title="Extensible Markup Language">XML</acronym> is a sideways move which doesnâ??t provide the end user any more utility, but soaks up valuable developer time.</div>
+</li>
+<li class="level1"><div class="li"> The other benefit of <acronym title="Extensible Markup Language">XML</acronym> is that it is more-or-less human readable. Iâ??ll grant that this is a valid assertion. Our current file format is not readable by a human who has never read the documentation. However, our current file format *is* <acronym title="American Standard Code for Information Interchange">ASCII</acronym>, and is completely documented, so an essential reason for readability – the ability to write scripts against the file – is already taken care of. Also, a human can certainly read the file format once he has taken the time to <acronym title="Read The Fine Manual">RTFM</acronym>. Human readability – without knowing the file format – is a â??nice to haveâ?? which isnâ??t high on my priority list.</div>
+</li>
+</ol>
+
+</div>
+<!-- SECTION "Can we change gEDA to use an XML file format?" [9492-] --></body>
+</html>
diff --git a/docs/wiki/geda-vams_netlister_readme.html b/docs/wiki/geda-vams_netlister_readme.html
new file mode 100644
index 0000000..8505d6c
--- /dev/null
+++ b/docs/wiki/geda-vams_netlister_readme.html
@@ -0,0 +1,687 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#vams_netlister_readme" class="toc">VAMS netlister README</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#vams_netlister" class="toc">VAMS netlister</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#vams_netlister_syntax_architecture" class="toc">VAMS netlister syntax architecture</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#vams_netlister_syntax_entity" class="toc">VAMS netlister syntax entity</a></span></div></li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="vams_netlister_readme" id="vams_netlister_readme">VAMS netlister README</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "VAMS netlister README" [1-36] -->
+<h2><a name="vams_netlister" id="vams_netlister">VAMS netlister</a></h2>
+<div class="level2">
+<pre class="code">date: 10 october 2000
+gEDA: gnetlist vams mode
+first unrevised vams mode documentation
+
+
+Written by: Martin Lehmann
+-------------------------------------------------------------------------
+
+
+VHDL-AMS support for the gEDA gnetlist tool
+-------------------------------------------
+
+CONTENT:
+
+ 1. functionality
+ 1. ARCHITECTURE generation
+ 2. ENTITY generation
+ 3. automatisate gnetlist calls
+
+ 2. implementation
+ 1. the vams mode of gEDA gnetlist
+ 1. scheme
+ 1. settings and new definition
+ 2. gnet-vams.scm
+ 1. routines main structure
+ 3. helpfully setting in gEDA gschem environment
+
+ 2. new c-code
+ 1. routines
+ 2. code-adaptation
+
+ 2. automatic generating gnetlist calls in gEDA gschem
+ 1. generated gEDA gnetlist calls
+ 2. scheme
+ 1. generate_netlist.scm
+ 2. settings
+
+ 3. new c-code
+ 1. routines
+ 2. code-adaptation
+
+
+ The purpose of our endevour, is that gEDA gnelist completly
+ supportted VHDL-AMS (VHDL Analog and Mixed-Signal) netlist
+ generation.
+
+ The VHDL-AMS netlist support mode is called vams.
+
+
+ 1. FUNCTIONALITY
+
+ gEDA gnetlist in vams mode allow it to generate a VHDL-AMS
+ ARCHITECTURE or an ENTIY declaration. Which of both tasks is
+ performed, dependends on the generate-mode variable. This variable
+ is defined in the gnetlist command or will be set default.
+
+ If generate-mode=1 (default) gnetlist creates a netlist as an
+ VHDL-AMS ARCHITECTURE of the current schematic. Otherwise
+ (generate-mode=2), it creates an VHDL-AMS ENTITY declaration of the
+ selected component (this task needs information from gEDA gschem,
+ see below).
+
+ Now follows a stepwise discription of the program run in both
+ submodes.
+
+ We presuppose that you are familiar with the structure of gEDA
+ gnetlist usage (otherwise try gnetlist -help) and that you have
+ ever seen an VHDL-AMS ARCHITECTURE with its belonging ENTITY. If
+ you does not then the following distription will be seems very
+ strange to you. Maybe the syntax files (syntax_entity.txt,
+ syntax_architeture.txt) can helps you further.
+
+ ==================================================================
+
+ 1.1. ARCHITECTURE GENERATION
+
+
+ We suppose generate-mode is equal to 1, from this it follows that
+ vams creates a netlist as an ARCHITECTURE (saved to
+ <value-of-toplevel-attribute-entity>_arc.<output-fileextension>).
+
+
+ ARCHITECTURE <architecture-identifier> OF <entity-identifier> IS
+
+ The architecture-identifier we are getting from the toplevel
+ attribute architecture, which we have introduced. If it is not
+ defined, we are setting architecture-identifier default
+ (default_architecture). The same have we doing with the
+ entity-identifier (toplevel attribute entity, default_entity).
+
+
+ {<subnet-object> <subnet-name> : subnet-kind;}
+
+ In the signal declaration part all subnets of the schematic will be
+ declarated. A subnet declaration consists of an net-object, a
+ net-name and a net-kind. All subnets are connected to various
+ components pins. If this pins have all the same port-object and the
+ same port-kind it is ok, but if one of them different, the net is
+ faulty, and will be not declarated. Moreover, if the subnet-object
+ a quantity, then it will be checked, whether the subnet consists
+ exactly one output pin (port-mode), else the subnet is faulty too.
+ The three net attributes (object, kind, mode) we are getting from
+ the pin attribs, port_kind, port_object and port_mode (which we
+ have introduced newly) of a component pin.
+
+
+ BEGIN
+
+ Ok. it's only marks the start of the architecture body.
+
+
+ {<label> : ENTITY <entity> [(<architecture>)]
+ [GENERIC MAP (<set generic> => <generic-value>
+ {; <set-generic=> <generic-value>})]
+ PORT MAP ( <pin-name> => <subnet-name>{; <.. => ..>});}
+
+ We only support component instantiation statements, like this
+ above, because we generate simple VHDL-AMS netlists. The label of
+ an instance is defined from the uref of the instanciated
+ component. Watch out, this label must be unique,it is not checked
+ anywhere. The entity variable is not the same as the
+ entity-identifier, it is the value of the device attribute which on
+ its part identifies the precompiled ENTITY of this special
+ component. Similar is the architecture variable belonging to the
+ instanciated components ARCHITECTURE (note: one ENTITY can have more
+ ARCHITECTURES), hence we are getting it from the component
+ attribute ARCHITECTURE (newly introduced).
+
+ All generics of the generic-list are component parameters, which
+ are different from its default values (set in its ENTITY
+ declaration). How can we distinguish them? All defined generics
+ are attached to the component and looks like :
+
+ <attribute-name>=?<default-value> <- default, not in
+ generic-list
+
+ And if you want to change a parameter, you only must delete the
+ ?-character and replace the default-value with your wanted value,
+ like this :
+
+ <attribute-name>=<new-value> <- element of generic list
+
+ If you do it this way, the new assigned value and its attribute-name
+ will be appear in the GENERIC MAP (set-generic=attribute-name and
+ generic-value=new-value).
+
+ The PORT MAP consists of all pins of a component and which nets
+ them connected to. The pin-name is getting from the pin# attribute
+ of the pin and the subnet-name means the value of the label
+ attribute of a net (mostly default named), which the pin is
+ connected to. If the pin directly wired to a PORT component (=
+ component, which device attribute =PORT), then we assign the uref
+ of this component to subnet-name.
+
+
+ END ARCHITECTURE <architecture-identifier>;
+
+ I think, this line needs no more explanation. The
+ architecture-identifier is the same like in the first line of
+ ARCHITECTURE declaration. Hence, the ARCHITECTURE part ends here.
+
+ ==================================================================
+
+ 1.2. ENTITY GENERATION
+
+
+ Now, we suppose generate-mode is equal to 2, from this it follows
+ that vams creates an ENTITY declaration of a component (save to
+ <component-device>.vhdl). If there no component selected (empty
+ top-attribs list) then it will be created an toplevel ENTITY of the
+ current schematic (save to
+ <value-of-toplevel-attribute-entity>.vhdl).
+
+
+ LIBRARY <library-identifier>{,<library-identifier>};
+ USE <package-identidier>{,<package-identifier>};
+
+ Well, the context clause part is not very ingenious. All libraries
+ and packages you needs for your simulation you must insert staticly
+ (a library contents precompiled ENTITIES, ARCHITECTURES and
+ PACKAGES, which are needed from base components [base of the
+ hierachical netlist] of your schematic. a package contents
+ predefined types, constants, ...). We are searching for a better
+ usability of this part.
+
+
+ ENTITY <entity-identifier> IS
+ [genric_clause]
+ [port_clause]
+ END ENTITY;
+
+ If you want generate a toplevel ENTITY of your current schematic
+ then the entity-identifier is defined from the toplevel attribute
+ entity of the schematic-file. Moreover, there are no generic_clause
+ and no port_clause.
+
+ In case of an component based ENTITY declaration, the
+ entity-identifier is getting from the device attribute of the
+ selected component (this attribute is included in top-attribs list,
+ which is defined in the automatic generated gnetlist command .. more
+ about this, later).
+
+
+ generic_clause :=
+ GENERIC ( <generic-identifier> : REAL := <default-value>
+ {;<generic-identifier> : REAL := <default-value>});
+
+ All needed generic-identifiers and it default-values are getting
+ from the top-attribs list. Note: all attached attributes of a
+ component appears in the generic_clause, only special attributes,
+ like uref, source and architecture, are taked out. The values of
+ this attributes are taked from the top-attribs list, too, but it
+ does not matter whether the value starts with a ?-character or not
+ (?-character always will be deleted, if it exist in front of a
+ value).
+
+
+ port_clause :=
+ PORT (<port-kind> <port-identifier> : [<port-mode>] <port-type>
+ {;<port-kind> <port-identifier> : [<port-mode>] <port-type>});
+
+ All variables of this clause are grabbed from the symbol of the
+ selected component. Port-kind corresponds with the value of the
+ port_kind attribute of the pin, which pin# attribute value is equal
+ to port-identifier. Just as corresponds port-type with the the
+ value of the pin attribute port_type and port-mode with the value
+ of port_mode.
+
+ ===================================================================
+
+ 1.3. AUTOMATISATING gnetlist CALLS
+
+ Because it is very arduous to type the whole gnetlist command,
+ which all its parameters, per hand into the terminal, we are
+ implement an automatisation of this process in gEDA gschem. This
+ makes it possible to create a VHDL-AMS ARCHITECTURE or ENTITY
+ whitout any commandline actions. The only thing you must do, is to
+ use one of the following hotkeys:
+
+ <g e> for generating an ENTITY
+ <g n> for genarating an ARCHITECTURE.
+
+ NOTE to <g e> - hotkey : If one component of the schematic
+ selected then the ENTITY generation
+ will be applied to this component !!
+
+ ===================================================================
+
+ 2. IMPLEMENTATION
+
+ At this section it will be explained the basic concept of the
+ implementation, which is splited in two sections. The first one
+ aimed to the gnelist implementation and the second to the gschem
+ implementation.
+
+
+ 2.1. THE VAMS MODE OF gEDA gnetlist
+
+ To realize gnetlist VHDL-AMS support, it was necessary to create
+ new scheme and c stuff.
+
+
+ 2.1.1. SCHEME
+
+ The scheme implementation contents two parts. On one hand the new
+ file gnet-vams.scm, which realize the VHDL-AMS-code generation, and
+ on the other hand some settings in rc-files.
+
+
+ 2.1.1.1. SETTINGS AND NEW DEFINITIONS
+
+ The following lines insert in your gschemrc, or wherever you want,
+ but it must be loaded at gnetlist startup.
+
+ - load two modules, which we needs in our new implementation.
+
+ (define-module (ice-9 ls) :use-module (ice-9 common-list)
+ :use-module (ice-9 string-fun))
+
+ - load main file for VHDL-AMS support, which contents the
+ startup procedure vams.
+
+ (load "<path_of_gnet-vams.scm>/gnet-vams.scm")
+
+
+ 2.1.1.2. gnet-vams.scm
+
+ This file contents all necessary scheme-functions to generate
+ VHDL-AMS-code. Especially, the main procedure vams, which can be
+ execute from the gnetlist command.
+
+ For example :
+
+ gnetlist -g vams schematic_filename.sch
+
+ ...
+
+
+ 2.1.2.1. ROUTINES MAIN STRUCTURE
+
+ the mainly functions structure looks like:
+
+ - (vams output-filename)
+
+ ARCHITECTURE generation
+
+ - (vams:write-secondary-unit architecture entity output-port)
+
+ - (vams:write-architecture-declarative-part output-port)
+ - (vams:write-signal-declarations output-port)
+
+ - (vams:write-architecture-statement-part packages output-port)
+ - (vams:write-generic-map output-port package)
+ - (vams:write-port-map package output-port)
+
+ ENTITY declaraction
+
+ - (vams:write-primary-unit entity port-list generic-list output-port)
+
+ - (vams:write-context-clause output-port)
+
+ - (vams:write-generic-clause generic-list output-port)
+ - (vams:write-generic-list generic-list output-port)
+
+ - (vams:write-port-clause port-list output-port)
+ - (vams:write-port-list port-list output-port)
+
+
+ 2.1.1.3 HELPFULLY SETTING IN THE gEDA gschem ENVIRONMENT
+
+ This settings are not absolutly necessary, but they makes work
+ easier.
+
+ - set in .gEDA/gschemrc or wherever you want, but place it
+ right.
+
+ (attribute-promotion "enable")
+ (promote-invisible "enable")
+ (enforce-hierarchy "disabled")
+
+ (attribute-name "port_object")
+ (attribute-name "port_type")
+ (attribute-name "port_mode")
+ (attribute-name "entity")
+ (attribute-name "architecture")
+
+
+ 2.1.2. NEW C - CODE
+
+ To got all informations, which we needed for currently netlist
+ generation, we must implemented two new c - functions.
+
+
+ 2.1.2.1 NEW ROUTINES (saved in vams_misc.c)
+
+
+ SCM vams_get_package_attributes(SCM scm_uref)
+
+ The first function gets all attribute names (not its values) of a
+ component. This routine requires the name a component (package),
+ especially the uref of it, and returns a list of all attribute
+ names which are attached to this package.
+
+ We needs this functionality to produce a currectly
+ VHDL-AMS GENERIC MAP.
+
+
+ char* vams_get_attribs_list
+ (OBJECT *object, SCM *list, OBJECT **return_found)
+
+ It exists only for the support of the first function.
+
+
+ 2.1.2.2. CODE ADAPTATION
+
+ To place this new functions at gnetlist scheme's disposal, you must
+ perform the following actions.
+
+ (1) gnetlist/src/g_register.c
+
+ gh_new_procedure1_0
+ ("gnetlist:vams-get-package-attributes",
+ vams_get_package_attributes);
+
+
+ (2) gnetlist/include/prototype.h
+
+ SCM vams_get_package_attributes(SCM scm_uref);
+
+
+ (3) edit gnetlist/src/Makefile.in or directly in Makefile
+
+ (if you have edited Makefile.in you must run make config of
+ course)
+
+ - add "vams_misc.c" to gnetlist_SOURCES - variable
+ - add "vams_misc.o" to gnetlist_OBJECTS - variable
+
+ (4) copy vams_misc.c to gEDA/gnetlist/src/
+
+ (5) compile your code newly
+
+ ===================================================================
+
+ 2.2. AUTOMATIC GENERATING gnetlist CALLS IN gEDA gschem
+
+ To realize this new feature it was necessary to put more
+ information from the schematic to the scheme world of gEDA gschem.
+ Concretly, we needs the filename of the current schematic, because
+ gEDA gnetlist required it, and the attached attributes of a
+ selected component for creating an VHDL-AMS ENTITY. Hence, the
+ gnetlist command is mutated to an unidirectional interface between
+ the world of gschem scheme and the world of gnetlist scheme.
+
+ There are three important things, which transfer through this
+ interface:
+
+ (1) the source-file, which contents the complett filename
+ (with path) of the current schematic.
+
+ (2) the top-attribs list, which contents all attached
+ attributes of the selected component.
+
+ (3) the generate-mode, which is defined by the users actions.
+
+
+ 2.2.1. STRUCTURE OF gEDA gnetlist CALLS FROM COMMANDLINE OR FROM gEDA
+ gschem.
+
+ typical commandline call :
+
+ gnetlist [-o <output-filename>]
+ -g vams
+ <schematic-file>
+
+ There are nothing to explain. The top-attribs list and the
+ generate-mode variable are default defined ('() and 1).
+
+
+ calls from gEDA gschem (3 possible variations) :
+
+
+ Note: vhdl-path is a predefined variable, which is set in
+ generate_netlist.scm first times. You can it simple redefine
+ in your local gschemrc file, which is loading everytimes you
+ starts gEDA gschem.
+
+
+ (1) hot-key-stroke: - g n (generate netlist)
+
+ --> generates a netlist of the current schematic.
+
+
+ gnetlist -o <vhdl-path>/<target-file>
+ -g vams
+ <source-file>
+
+ The source-file variable is equate to the complett
+ path+filename of the current schematic, which we get with
+ help of a self coded c function. If you cut out the filename
+ of the source-file variable (source-file without path) then
+ you are getting the target-file.generate-mode and
+ top-attribs are default again.
+
+ (2) hot-key-stroke: - g e (generate-entity)
+ and no component is selected.
+
+ --> generates an toplevel ENTITY of the current
+ schematic.
+
+
+ gnetlist -c <scheme-comm>
+ -o <vhdl-path>/<target-file>
+ -g vams
+ <source-file>
+
+ scheme-comm="(define top-attribs '<top-attribs>)
+ (define generate-mode '2)"
+
+
+ Source-file needs no comment, because it is the same as in
+ (1). To get all attributes of a selected component, we are
+ must write a new c function again. The values, which we get
+ from this new function are saved in top-attribs. The sense
+ of the scheme-comm command is to put top-attribs and
+ generate-mode from the gschem to the gnetlist environment.
+ At last, the target-file consists of the pure basefilename
+ of the source-file and an .vhdl extention.
+
+ (3) hot-key-stroke: - g e (generate-entity)
+ and only one component is selected.
+
+ --> generates an ENTITY of the selected schematic.
+
+
+ commandline is the same as in (2).
+
+
+ Differences: The target-file is different, but it does not
+ matter, because gnetlist generate an new output-filename in
+ in this case (<device-name-of-selected-component>.vhdl,
+ normally).But one fact is very important: the top-attribs
+ variable includes all attached attributes of the selected
+ component now.
+
+ 2.2.2. SCHEME
+
+ The gnetlist command is generating from two scheme functions, which
+ are saved in generate_netlist.scm. This functions starts if the
+ gschem user is typing one of the specified hot-keys ([g e] starts
+ generate-entity and [g n] starts generate-netlis). Both routines
+ puts the whole gnetlist command together and execute it. The syntax
+ you see above.
+
+
+ 2.2.2.1. generate_netlist.scm
+
+
+ 2.2.2.2. SETTINGS
+
+ If you want use the new feature then you must do some entries in one
+ of your gEDA gschem rc-files
+
+ necessary defines:
+
+ - in system-gschemrc
+
+ ("g" . gnetlist-keymap)
+
+ Edit your global-keymap and if "g" always defined then find
+ out an other free hot-key-stroke.
+
+ Note: the documentation supports the "g" - key only.
+
+
+ - in one of the gschem startup files
+
+ (define gnetlist-keymap
+ '(("n" . generate-netlist)
+ ("e" . generate-entity)))
+
+
+ loads :
+
+ (load "/home/fliser3/.gEDA/generate_netlist.scm")
+
+
+ 2.2.3. NEW C-CODE
+
+ The c-code makes it possible to get directly informations from the
+ gschem tool, which is necessary for the online execution of
+ gnetlist.
+
+
+ 2.2.3.1. ROUTINES
+
+ It exists two new c-functions. Both are put down in
+ misc_for_gnetlist.c.
+
+
+ SCM get_selected_filename(gpointer data,
+ guint callback_action,
+ GtkWidget *widget)
+
+ This function returns the whole filename of the current schematic,
+ which is picked from the w_current->page_current->page_filename
+ string.
+
+
+ SCM get_selected_component_attributes(gpointer data,
+ guint callback_action,
+ GtkWidget *widget)
+
+ How the name is saying, this functions returns all attributes of
+ the selected component. It is realized with a simple while loop
+ over all objects of the schematic, which picked out all elements
+ where the selected flag is set.
+
+
+ 2.2.3.2. CODE-ADAPTATION
+
+ Here are some actions you must conclude to makes the software
+ runable.
+
+ (1) new lines in /gschem/src/g_register.c
+
+ gh_new_procedure0_0 ("get-selected-filename",g_get_selected_filename);
+
+
+ (2) new lines in /gschem/include/prototype.h
+
+ SCM g_get_selected_filename();
+
+
+ (3) copy the file misc_for_gnetlist.c to gschem/src
+
+ (4) add in file /gschem/src/Makefile.in or directly in Makefile.
+
+ (if you have edited Makefile.in you must run make config of
+ course)
+
+ - add "misc_for_gnetlist.c" to gschem_SOURCES - variable
+ - add "misc_for_gnetlist.o" to gschem_OBJECTS - variable
+
+ (5) add new lines in /gschem/src/g_key.c
+
+ SCM g_get_selected_filename(void)
+ {
+ return (get_selected_filename(window_current, 0, NULL));
+ }
+
+
+ (6) compile your changed c-code newly
+</pre>
+
+</div>
+<!-- SECTION "VAMS netlister" [37-20220] -->
+<h2><a name="vams_netlister_syntax_architecture" id="vams_netlister_syntax_architecture">VAMS netlister syntax architecture</a></h2>
+<div class="level2">
+<pre class="code">ARCHITECTURE <architecture-identifier> OF <entity-identifier> IS
+
+ {<subnet-object> <subnet-name> : subnet-kind;}
+
+BEGIN
+
+ {<label> : ENTITY <entity> [(<architecture>)]
+ [GENERIC MAP (<set-generic> => <generic-value>
+ {; <set-generic=> <generic-value>})]
+ PORT MAP ( <pin-name> => <subnet-name>{; <.. => ..>});}
+
+END ARCHITECTURE <architecture-identifier>;
+</pre>
+
+</div>
+<!-- SECTION "VAMS netlister syntax architecture" [20221-20667] -->
+<h2><a name="vams_netlister_syntax_entity" id="vams_netlister_syntax_entity">VAMS netlister syntax entity</a></h2>
+<div class="level2">
+<pre class="code">LIBRARY <library-identifier>{,<library-identifier>};
+USE <package-identidier>{,<package-identifier>};
+
+ENTITY <entity-identifier> IS
+ [GENERIC ( <generic-identifier> : REAL := <default-value>
+ {;<generic-identifier> : REAL := <default-value>}); ]
+ [PORT (<port-kind> <port-identifier> : [<port-mode>] <port-type>
+ {;<port-kind> <port-identifier> : [<port-mode>] <port-type>});]
+END ENTITY;
+</pre>
+
+</div>
+<!-- SECTION "VAMS netlister syntax entity" [20668-] --></body>
+</html>
diff --git a/docs/wiki/geda-verilog_netlister_readme.html b/docs/wiki/geda-verilog_netlister_readme.html
new file mode 100644
index 0000000..b55b04b
--- /dev/null
+++ b/docs/wiki/geda-verilog_netlister_readme.html
@@ -0,0 +1,441 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="verilog_netlister_readme" id="verilog_netlister_readme">Verilog netlister README</a></h1>
+<div class="level1">
+<pre class="code">Verilog netlister readme.
+
+THIS IS FREE SOFTWARE, see the included file COPYING for more info.
+
+Latest README:
+
+ This is the fifth release of the Verilog netlister for gEDA.
+
+ New in this release:
+
+ 1) Escaped Verilog identifiers.
+
+ To facilitate board level simulations, the Verilog netlister now
+outputs `escaped' Verilog identifiers for any net, port or instance name
+that does not appear to be a valid Verilog identifier. In this way,
+chips with numbered pins can be netlisted and models constructed to run
+digital simulations of complete circuits.
+
+
+ Mike Jarabek
+
+
+----- OLDER README.verilog's -----
+
+ This is the fourth release of the Verilog netlister for gEDA.
+
+ New in this release:
+
+ 1) Multiple width wires.
+
+How to use: (mostly taken from a previous readme... )
+
+ Here's how to proceed to make a schematic that can be netlisted
+to verilog.
+
+ 1) Create your modules by the standard method, keep in mind
+ that you must supply a `pin#' attribute for each port
+ you want to create in the generated verilog. gmk_sym is
+ useful for this.
+
+ 2) Place each of your newly created modules on the
+ schematic. You may also place primitives from the
+ `verilog' symbol library. Be sure to give a _unique_
+ `uref' to every symbol you place on the schematic,
+ unless two symbols are actually different parts of the
+ same module, and the pins listed on each symbol do not
+ have any names in common. Otherwise they will not get
+ netlisted.
+
+ 3) Connect nets between the modules you want. Remember, if
+ you want legible Verilog later, don't forget to name all
+ your nets by attaching `label' attributes to them. For
+ Multiple bit wires just use standard Verilog notation.
+ The netlister will figure out which bit ordering you
+ want. Be sure to have at least one net labeled with the
+ complete range expression, otherwise the netlister will
+ guess at whether you wanted net[15:0] or net[0:15] in
+ your declarations. Any inconsistent ranges will be
+ reported as a warning. Strings that appear to be
+ invalid Verilog identifiers will be printed with a
+ warning, but otherwise ignored. (If you get a warning
+ for a valid Verilog identifier, please post a bug
+ report!)
+
+ 4) Insert IPAD's, OPAD's, and IOPAD's for all the nets you
+ want to be visible in the module declaration statement.
+ It is especially important to make sure that the nets
+ you hook up to the pads are named, as the net names
+ could change from run to run, that's a bad thing. (I/O
+ pads would be a good place to put the aformentionned
+ full range expressions. Range expressions on I/O pads
+ are ignored when outputting the module declaration, but
+ they are used in figuring out the final bit ranges.)
+ Every pad must have a unique uref, otherwise the
+ netlister will get confused.
+
+ 5) Add an unattached attribute `module_name=Your_Module'
+ somewhere on the schematic, near the title block is
+ good. This will name the generated Verilog module
+ `Your_Module'.
+
+ 6) Save your design.
+
+ 7) Run the schematic through the netlister:
+
+ gnetlist -g verilog -o output.v schematic.sch
+
+ 7a) Check the output for correctness, _especially_ if you got
+ any warnings. (There should be no warnings.)
+
+ 8) Feed the netlist to your favorite simulator/synthesis tool.
+
+
+ Mike Jarabek
+
+
+ This is the third release of the Verilog netlister for geda.
+
+ Fixed in this release:
+
+ 1) Netlister no longer barfs if there are no
+ Input/Output/InOut ports on the module.
+
+ 2) Module instantiation code much improved/cleaned up, mostly
+ due to g_netlist.c patch.
+
+ New in this release:
+
+ 1) A whole wack-load of symbols, I created a C program that
+ generates n-input versions of and, nand, or, nor, xor, and
+ xnor symbols
+
+ 2) Modules instantiated with positional port connections.
+ Just add the attribute `VERILOG_PORTS=POSITIONAL' to your
+
+ symbol file as an unattached attribute, or attach it to the
+ symbol on the schematic.
+
+ 3) Added bufif?, notif?, not and buf symbols.
+
+ 4) Added example of positional port module instantiation to
+ the example schematic
+
+ 5) Added 7447 example schematic
+
+ Coming:
+
+ 1) Module instantiation parameters. (probably by an attribute)
+
+
+ Included in this tar-ball are three patch files against the
+ 19990705 version of gEDA. Apply g_netlist.c.diff and
+ g_register.c.diff to the files in gnetlist/src/ and
+ gnetlist.scm.diff to gnetlist.scm in the gnetlist/scheme
+ directory. You may have to regenerate prototype.h, or manually
+ patch it. Replace the symbols in the sym/verilog directory
+ with the symbols in this distribution. (I have modified all of
+ the symbols to use the new unattached attribute convention for
+ device et al.) (if you have applied the patch I sent to the
+ mailing list that fixes netlisting a module with no ports, you
+ may have trouble applying the gnetlist.scm.diff patch.) Don't
+ forget to do a `make all install' after applying the patches.
+
+ Once again, to netlist the example schematics to verilog type:
+ (Assuming gnetlist has been patched and is properly installed.)
+
+ gnetlist -g verilog -o test.v examples/sch/test.sch
+
+ or
+
+ gnetlist -g verilog -o 7447.v examples/sch/7447.sch
+
+
+(This README was from 19990629)
+Verilog netlister readme.
+
+THIS IS FREE SOFTWARE, see the included file COPYING for more info.
+
+ This is the second release of the Verilog netlister for geda.
+
+ Fixed in this release:
+
+ 1) The last comma in the argument list to instantiations and
+ module definitions is now suppressed
+
+ 2) Better handling of `special' components has been added
+
+ New in this release:
+
+ 1) Continuous assignments to 1'b0 and 1'b1 can now be
+ generated by connecting the `high' or `low' symbol to a
+ net.
+
+ Mike Jarabek
+ mjarabek@xxxxxxxxxxxxxx
+
+
+
+--
+
+
+ This the verilog netlister for gEDA. Included in the tarball
+are several diff files against the 19990327 gEDA distribution. All of
+the patches apply to the gnetlist subirectory. You should be able to
+apply them with `patch -p1'.
+
+ The netlister has its limitations: (most of these will
+eventually get fixed, I hope..)
+
+ 1) Components connected by reference, (i.e. by having named
+ net stubs attached to pins, but not conected by a
+ continuous line) create duplicate entries in the wire
+ declaration section of the verilog code.
+
+ 2) Multiple width wires don't work. (Busses will help
+ this)
+
+ 3) There is no way to force a signal to 1,0,z,x (yet).
+
+ 4) Some scheme code needs to be improved. (Mainly the
+ classification code, it inserts `()' elements into the
+ output lists. (I should know how to fix this in a day or
+ two.. too bad I never got a scheme course before..))
+
+ 5) I don't know if this will work on multiple page schematics.
+
+ 6) The top level module is outputted with the same name
+ every time, I don't currently think there is a way to
+ get at the name of the top level schematic.
+
+
+ The netlister does some neat things:
+
+
+ 1) It outputs a verilog module with proper port
+ declarations, outputs are declared as outputs, inputs
+ are declared as inputs, and bidirectional signals are
+ declared as inouts.
+
+ 2) All nets that are found on the design are declared as
+ wires. (This is to allow for net attributes later to
+ declare wand's and such)
+
+ 3) Any components placed on the schematic that are given
+ uref attributes create a verilog instantiation for the
+ name of the module as stored in the `device' attribute,
+ the instatiated name is given as the `uref' attribute.
+
+ 4) All connections into and out of instantiated modules are
+ made by name, and not by order, because I can't be sure
+ that the order will be right coming off the schematic.
+ (anyway, that's better for the long run.)
+
+ 5) A comment is inserted at the top of the module to say
+ that the file was automatically generated.
+
+
+
+ Here's how to proceed to make a schematic that can be netlisted
+to verilog.
+
+ 1) Create your modules by the standard method, keep in mind
+ that you must supply a `pin#' attribute for each port
+ you want to create in the generated verilog. gmk_sym is
+ useful for this (with the patch to allow ascii pin names).
+
+ 2) Place each of your newly created modules on the
+ schematic
+
+ 3) Connect nets between the modules you want. Remember, if
+ you want legible verilog later, don't forget to name all
+ your nets by attaching `label' attributes to them.
+
+ 4) Insert IPAD's, OPAD's, and IOPAD's for all the nets you
+ want to be visible in the module declaration statement.
+ It is especially important to make sure that the nets
+ you hook up to the pads are named, as the net names
+ could change from run to run, that's a bad thing.
+
+ 5) Save your design.
+
+ 6) Run the schematic through the netlister:
+
+ gnetlist -g verilog -o output.v schematic.sch
+
+ 6a) Edit the output file to have the right module name, and
+ to remove any duplicate wires.
+
+
+ There is an example schematic in the schematic directory, and a
+ copy of the verilog netlist generated.
+
+The mechanics:
+
+ The I/O ports for the module are detected by enumerating all of
+ the nets attached to any symbol bearing the device name of `IPAD',
+ `OPAD', or `IOPAD'. If you name one of your blocks with that
+ name, don't be surprised if you find `extra' ports in the module
+ declaration.
+
+ The wires are declared by walking through the list of nets
+ returned by the function that I patched into gnetlist. This is
+ the source of the duplicate wire declarations. This should
+ probably get fixed when `net_is_duplicate' gets set for
+ connections made by reference.
+
+ Module instantiations are created by enumerating the pins found on
+ a symbol and connecting the nets found to the pins. If your block
+ has spelling errors, then the module instantiation won't work.
+ You will have to manually trace back to find the error.
+
+
+ Mike Jarabek
+
+
+
+------------ Below is the previous version README -------------------
+
+Verilog netlister readme.
+
+THIS IS FREE SOFTWARE, see the included file COPYING for more info.
+
+
+ This the verilog netlister for gEDA. Included in the tarball
+are several diff files against the 19990327 gEDA distribution. All of
+the patches apply to the gnetlist subirectory. You should be able to
+apply them with `patch -p1'.
+
+[ editor's note, if you are reading this file in a gEDA dist, then all
+ the required patching and integration is already done ]
+
+ The netlister has its limitations: (most of these will
+eventually get fixed, I hope..)
+
+ 1) Components connected by reference, (i.e. by having named
+ net stubs attached to pins, but not conected by a
+ continuous line) create duplicate entries in the wire
+ declaration section of the verilog code.
+
+ 2) Multiple width wires don't work. (Busses will help
+ this)
+
+ 3) There is no way to force a signal to 1,0,z,x (yet).
+
+ 4) Some scheme code needs to be improved. (Mainly the
+ classification code, it inserts `()' elements into the
+ output lists. (I should know how to fix this in a day or
+ two.. too bad I never got a scheme course before..))
+
+ 5) I don't know if this will work on multiple page schematics.
+
+ 6) The top level module is outputted with the same name
+ every time, I don't currently think there is a way to
+ get at the name of the top level schematic.
+
+
+ The netlister does some neat things:
+
+
+ 1) It outputs a verilog module with proper port
+ declarations, outputs are declared as outputs, inputs
+ are declared as inputs, and bidirectional signals are
+ declared as inouts.
+
+ 2) All nets that are found on the design are declared as
+ wires. (This is to allow for net attributes later to
+ declare wand's and such)
+
+ 3) Any components placed on the schematic that are given
+ uref attributes create a verilog instantiation for the
+ name of the module as stored in the `device' attribute,
+ the instatiated name is given as the `uref' attribute.
+
+ 4) All connections into and out of instantiated modules are
+ made by name, and not by order, because I can't be sure
+ that the order will be right coming off the schematic.
+ (anyway, that's better for the long run.)
+
+ 5) A comment is inserted at the top of the module to say
+ that the file was automatically generated.
+
+
+
+ Here's how to proceed to make a schematic that can be netlisted
+to verilog.
+
+ 1) Create your modules by the standard method, keep in mind
+ that you must supply a `pin#' attribute for each port
+ you want to create in the generated verilog. gmk_sym is
+ useful for this (with the patch to allow ascii pin names).
+
+ 2) Place each of your newly created modules on the
+ schematic
+
+ 3) Connect nets between the modules you want. Remember, if
+ you want legible verilog later, don't forget to name all
+ your nets by attaching `label' attributes to them.
+
+ 4) Insert IPAD's, OPAD's, and IOPAD's for all the nets you
+ want to be visible in the module declaration statement.
+ It is especially important to make sure that the nets
+ you hook up to the pads are named, as the net names
+ could change from run to run, that's a bad thing.
+
+ 5) Save your design.
+
+ 6) Run the schematic through the netlister:
+
+ gnetlist -g verilog -o output.v schematic.sch
+
+ 6a) Edit the output file to have the right module name, and
+ to remove any duplicate wires.
+
+
+ There is an example schematic in the schematic directory, and a
+ copy of the verilog netlist generated.
+
+The mechanics:
+
+ The I/O ports for the module are detected by enumerating all of
+ the nets attached to any symbol bearing the device name of `IPAD',
+ `OPAD', or `IOPAD'. If you name one of your blocks with that
+ name, don't be surprised if you find `extra' ports in the module
+ declaration.
+
+ The wires are declared by walking through the list of nets
+ returned by the function that I patched into gnetlist. This is
+ the source of the duplicate wire declarations. This should
+ probably get fixed when `net_is_duplicate' gets set for
+ connections made by reference.
+
+ Module instantiations are created by enumerating the pins found on
+ a symbol and connecting the nets found to the pins. If your block
+ has spelling errors, then the module instantiation won't work.
+ You will have to manually trace back to find the error.
+
+
+ Mike Jarabek
+</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-version_control_migration.html b/docs/wiki/geda-version_control_migration.html
new file mode 100644
index 0000000..2d96277
--- /dev/null
+++ b/docs/wiki/geda-version_control_migration.html
@@ -0,0 +1,110 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#version_control_migration" class="toc">Version Control Migration</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#status_quo" class="toc">Status Quo</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#what_we_need" class="toc">What We Need</a></span></div></li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="version_control_migration" id="version_control_migration">Version Control Migration</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "Version Control Migration" [1-41] -->
+<h2><a name="status_quo" id="status_quo">Status Quo</a></h2>
+<div class="level2">
+
+<p>
+ Currently, gEDA uses <acronym title="Concurrent Versions System">CVS</acronym>. <acronym title="Concurrent Versions System">CVS</acronym> is the â??originalâ?? version control system used for collaborating on open source projects.
+</p>
+
+<p>
+Unfortunately, <acronym title="Concurrent Versions System">CVS</acronym> has a number of problems:
+</p>
+<ol>
+<li class="level1"><div class="li"> <acronym title="Concurrent Versions System">CVS</acronym> does not support the concept of patch sets. That is, itâ??s very difficult to work out what changes went into <acronym title="Concurrent Versions System">CVS</acronym> together without using dodgy tools like <a href="http://www.cobite.com/cvsps/"; class="urlextern" title="http://www.cobite.com/cvsps/"; rel="nofollow">cvsps</a>.</div>
+</li>
+<li class="level1"><div class="li"> Merging with <acronym title="Concurrent Versions System">CVS</acronym> is painful, especially when there is keyword expansion brokenness such as the <code>Log</code> keyword.</div>
+</li>
+<li class="level1"><div class="li"> <acronym title="Concurrent Versions System">CVS</acronym> doesnâ??t support renames preserving history.</div>
+</li>
+<li class="level1"><div class="li"> The overhead involved in creating and managing a branch in <acronym title="Concurrent Versions System">CVS</acronym> is such that people tend to do one of the following:</div>
+<ol>
+<li class="level2"><div class="li"> Donâ??t bother</div>
+</li>
+<li class="level2"><div class="li"> Use another VCS locally, then export patches, then commit patches to <acronym title="Concurrent Versions System">CVS</acronym>. This is a big hassle for everyone.</div>
+</li>
+<li class="level2"><div class="li"> Do II. <strong>and</strong> use a branch in <acronym title="Concurrent Versions System">CVS</acronym>, which is even more hassle, but means people can see the changes in advance.</div>
+</li>
+</ol>
+</li>
+<li class="level1"><div class="li"> You canâ??t do anything in <acronym title="Concurrent Versions System">CVS</acronym> (view logs, view â??blameâ?? for a line of code, create diffs to previous versions) without being online & connecting to the repository.</div>
+</li>
+</ol>
+
+</div>
+<!-- SECTION "Status Quo" [42-1144] -->
+<h2><a name="what_we_need" id="what_we_need">What We Need</a></h2>
+<div class="level2">
+
+<p>
+ gEDA has a development process that involves a number of people working independently on separate changes. Some of these are a single changeset hacked together in a few minutes, some involve several major changes and are developed over a matter of months. Often, in order to track down a tricky bug, it is necessary for a developer to try and work out what a fellow developer did several months ago.
+</p>
+
+<p>
+The following features would be deemed desirable in a version control system:
+</p>
+<ol>
+<li class="level1"><div class="li"> Free as in beer as well as free as in speech.</div>
+</li>
+<li class="level1"><div class="li"> Actively developed/maintained.</div>
+</li>
+<li class="level1"><div class="li"> Atomic commits (a.k.a. changesets).</div>
+</li>
+<li class="level1"><div class="li"> All users have their own copy of the history.</div>
+</li>
+<li class="level1"><div class="li"> Users can make local branches/commits without being logged onto a remote server (â??distributedâ?? repository model).</div>
+</li>
+<li class="level1"><div class="li"> Merge & rename tracking.</div>
+</li>
+<li class="level1"><div class="li"> Easy to transition to from <acronym title="Concurrent Versions System">CVS</acronym>.</div>
+</li>
+</ol>
+
+<p>
+ Using the <a href="http://en.wikipedia.org/wiki/Comparison_of_revision_control_software"; class="urlextern" title="http://en.wikipedia.org/wiki/Comparison_of_revision_control_software"; rel="nofollow">comparison matrix at Wikipedia</a>, it looks like only <a href="http://www.selenic.com/mercurial/wiki/"; class="urlextern" title="http://www.selenic.com/mercurial/wiki/"; rel="nofollow">Mercurial</a> and <a href="http://git.or.cz/"; class="urlextern" title="http://git.or.cz/"; rel="nofollow">git</a> have the features we require.
+</p>
+
+<p>
+A number of factors militate in favour of using git:
+</p>
+<ul>
+<li class="level1"><div class="li"> Existing experience within the the gEDA development community.</div>
+</li>
+<li class="level1"><div class="li"> More extensively used by major projects (Linux kernel, X.org X server, OLPC, WINE).</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "What We Need" [1145-] --></body>
+</html>
diff --git a/docs/wiki/geda-vhdl_netlister_readme.html b/docs/wiki/geda-vhdl_netlister_readme.html
new file mode 100644
index 0000000..90f1291
--- /dev/null
+++ b/docs/wiki/geda-vhdl_netlister_readme.html
@@ -0,0 +1,41 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="vhdl_netlister_readme" id="vhdl_netlister_readme">VHDL netlister README</a></h1>
+<div class="level1">
+<pre class="code">The VHDL backend
+
+Written by Magnus Danielson and improved by Thomas Heidel
+
+
+A few things you have to care about:
+
+1. In order to generate valid component declarations, you
+ have to add an additional attribute to each pin.
+ "type=IN" or "type=OUT" or "type=INOUT"
+
+2. The "device" attribute must be unique to a symbol!
+ The verilog symbols of the same type for example, have all
+ the same device attribute and will therefore not work.
+
+3. Make sure your component-library picks up the vhdl symbols instead
+ of the verilog symbols Library paths that show up last are searched
+ first!
+</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-wcalc_mp.html b/docs/wiki/geda-wcalc_mp.html
new file mode 100644
index 0000000..5e24064
--- /dev/null
+++ b/docs/wiki/geda-wcalc_mp.html
@@ -0,0 +1,70 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="wcalc_man-page" id="wcalc_man-page">Wcalc man-page</a></h1>
+<div class="level1">
+<pre class="code">WCALC(1) WCALC(1)
+
+
+
+NAME
+ wcalc - Transmission line analysis/synthesis calculator.
+
+
+SYNOPSIS
+ wcalc
+
+
+DESCRIPTION
+ The wcalc program is a tool for the analysis and synthesis of transmis-
+ sion line structures and related components. Wcalc provides the abil-
+ ity to analyze the electrical parameters of a particular structure
+ based on the physical dimensions and material parameters. The synthe-
+ sis portion calculates the required physical parameters to meet desired
+ electrical specifications. Wcalc includes several models and places an
+ emphasis on accuracy.
+
+
+ENVIRONMENT
+ WCALC_DATADIR
+ If set, wcalc searches in $WCALC_DATADIR for the EPS files used
+ when printing out models. The default value is the $pre-
+ fix/share/wcalc directory, where prefix is the installation pre-
+ fix.
+
+
+SEE ALSO
+ stdio-wcalc(1)
+
+
+AUTHORS
+ Wcalc was written by Dan McMahill <mcmahill@xxxxxxxxxxxx>
+
+
+BUGS
+ None known. Please report any on the Wcalc Sourceforge Project page at
+ http://www.sourceforge.net/projects/wcalc
+
+
+
+
+
+
+ WCALC(1)</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-wcalc_readme.html b/docs/wiki/geda-wcalc_readme.html
new file mode 100644
index 0000000..548b9f9
--- /dev/null
+++ b/docs/wiki/geda-wcalc_readme.html
@@ -0,0 +1,54 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="wcalc_readme" id="wcalc_readme">Wcalc README</a></h1>
+<div class="level1">
+<pre class="code">$Id: README,v 1.2 2005/10/24 21:12:42 dan Exp $
+
+Wcalc is a tool for the analysis and synthesis of transmission line structures and
+related components. Wcalc provides the ability to analyze the electrical parameters
+of a particular structure based on the physical dimensions and material parameters.
+The synthesis portion calculates the required physical parameters to meet desired
+electrical specifications. Wcalc includes several models and places an emphasis on
+accuracy. Several frontends provide the user with several options for its use.
+
+Models include:
+
+ - single layer solenoid inductor
+ - single microstrip and stripline
+ - coupled microstrip
+ - metal-insulator-semiconductor microstrip
+ - coaxial cable
+
+Frontends include:
+
+ - gtk gui
+ - web (cgi)
+ - scilab
+ - octave
+ - matlab
+ - stdio
+
+See the file INSTALL for building and installation instructions.
+
+Please report all bugs at the wcalc sourceforge project page
+at http://wcalc.sf.net
+
+See the file COPYING for copying conditions.</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-wcalc_stdio_mp.html b/docs/wiki/geda-wcalc_stdio_mp.html
new file mode 100644
index 0000000..43fb47e
--- /dev/null
+++ b/docs/wiki/geda-wcalc_stdio_mp.html
@@ -0,0 +1,77 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="stdio_wcalc_man-page" id="stdio_wcalc_man-page">stdio Wcalc man-page</a></h1>
+<div class="level1">
+<pre class="code">STDIO-WCALC(1) STDIO-WCALC(1)
+
+
+
+NAME
+ stdio-wcalc - Transmission line analysis/synthesis calculator.
+
+
+SYNOPSIS
+ stdio-wcalc [ -v|--verbose ] [ file ... ]
+ stdio-wcalc [ -h|--help ]
+ stdio-wcalc [ -V|--version ]
+
+
+DESCRIPTION
+ The stdio-wcalc program is a simple standard input/output interface to
+ libwcalc which is the numerical engine for the wcalc program. The
+ input is read from the standard input on a line at a time basis. Each
+ line consists of a command followed by the numerical arguments.
+
+ The analysis and synthesis functions supported by stdio-wcalc are the
+ same as those in the scilab, octave, and matlab frontends to wcalc.
+ Please refer to the man pages listed at the end of this man page for
+ details on each of the supported functions. The syntax used by
+ stdio-wcalc is slightly different than scilab/octave/matlab. Instead
+ of [a,b,c] = somefn(x,y,z) as you would use in scilab, octave, or mat-
+ lab, you simply enter somefn x y z as the input line to stdio-wcalc and
+ the standard output will be a b c
+
+ In addition to the analysis and synthesis functions, stdio-wcalc sup-
+ ports the "version" command which returns the current version of the
+ program.
+
+
+SEE ALSO
+ wcalc(1), air_coil_calc(n), air_coil_syn(n), coax_calc(n), coax_syn(n),
+ coupled_microstrip_calc(n), coupled_microstrip_syn(n),
+ ic_microstrip_calc(n), ic_microstrip_syn(n), microstrip_calc(n),
+ microstrip_syn(n), stripline_calc(n), stripline_syn(n)
+
+
+AUTHORS
+ Wcalc was written by Dan McMahill <mcmahill@xxxxxxxxxxxx>
+
+
+BUGS
+ Please report any on the Wcalc Sourceforge project website at
+ http://wcalc.sf.net
+
+
+
+
+
+
+ STDIO-WCALC(1)</pre>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-wip-clipboard.html b/docs/wiki/geda-wip-clipboard.html
new file mode 100644
index 0000000..9881d11
--- /dev/null
+++ b/docs/wiki/geda-wip-clipboard.html
@@ -0,0 +1,179 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#clipboard_support" class="toc">Clipboard Support</a></span></div>
+<ul class="toc">
+<li class="clear">
+
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#introduction" class="toc">Introduction</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#the_x_clipboard" class="toc">The X clipboard</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#the_windows_clipboard" class="toc">The Windows clipboard</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#gtk_clipboard_api" class="toc">GTK clipboard API</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#buffers_in_gschem" class="toc">Buffers in gschem</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#clipboard_data_types" class="toc">Clipboard data types</a></span></div></li></ul>
+</li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="clipboard_support" id="clipboard_support">Clipboard Support</a></h1>
+<div class="level1">
+
+<p>
+ Targetted for release in gEDA 1.8.0.
+</p>
+
+</div>
+<!-- SECTION "Clipboard Support" [1-71] -->
+<h3><a name="introduction" id="introduction">Introduction</a></h3>
+<div class="level3">
+
+<p>
+ Currently, if you â??copyâ?? in gschem and â??pasteâ?? in another program (or a different instance of gschem), nothing useful happens. We should ideally try and use the system clipboard to enable transparent copying and pasting of schematic data between multiple gschem windows as well as other programs.
+</p>
+
+<p>
+It would be nice to be able to:
+</p>
+<ol>
+<li class="level1"><div class="li"> Copy in gschem, paste in text editor. Should it paste schematic file source code equivalent to copied elements?</div>
+</li>
+<li class="level1"><div class="li"> Copy in gschem, paste in another instance of gschem. How should it handle differences in component library settings between programs?</div>
+</li>
+<li class="level1"><div class="li"> Copy in gschem, paste in <program that understands images>. Should paste an image representation of the copied elements.</div>
+</li>
+</ol>
+
+<p>
+ Consider the use case of â??I want this circuit in my OpenOffice presentation, letâ??s try the obvious thing to get it there."
+</p>
+
+</div>
+<!-- SECTION "Introduction" [72-930] -->
+<h3><a name="the_x_clipboard" id="the_x_clipboard">The X clipboard</a></h3>
+<div class="level3">
+
+<p>
+ The X window system uses the arcane â??selectionâ?? protocol for copy/paste between X client applications. By taking charge of a â??selectionâ??, an application is able to advertise a number of different datatypes, from which another application can request the most appropriate. Two selections are usually available:
+</p>
+<ol>
+<li class="level1"><div class="li"> The PRIMARY selection is customarily used to hold the last piece of text the user selected, and many programs paste its contents on middle-click.</div>
+</li>
+<li class="level1"><div class="li"> The CLIPBOARD selection is customarily used with an applicationâ??s â??Copyâ??, â??Cutâ?? and â??Pasteâ?? actions.</div>
+</li>
+</ol>
+
+<p>
+ Many desktop environments (including GNOME and KDE) run a â??clipboard daemonâ??, which copies the CLIPBOARD contents and makes it available even if the original application quits.
+</p>
+
+<p>
+Due to the primarily non-textual nature of schematic or symbol data, gschem should use the CLIPBOARD on copy/paste, and ignore the SELECTION.
+</p>
+
+</div>
+<!-- SECTION "The X clipboard" [931-1845] -->
+<h3><a name="the_windows_clipboard" id="the_windows_clipboard">The Windows clipboard</a></h3>
+<div class="level3">
+
+<p>
+ Research needed.
+</p>
+
+</div>
+<!-- SECTION "The Windows clipboard" [1846-1896] -->
+<h3><a name="gtk_clipboard_api" id="gtk_clipboard_api">GTK clipboard API</a></h3>
+<div class="level3">
+
+<p>
+ The Gimp Toolkit used by gschemâ??s <acronym title="Graphical User Interface">GUI</acronym> provides APIs for manipulating the X selection (see <a href="http://library.gnome.org/devel/gtk/stable/gtk-Clipboards.html"; class="urlextern" title="http://library.gnome.org/devel/gtk/stable/gtk-Clipboards.html"; rel="nofollow">the GTK manual</a>). Since gschem already links against GTK, and the GTK clipboard <acronym title="Application Programming Interface">API</acronym> is considerably simpler than using low-level X library calls (as well as being more portable), gschem should make use of it.
+</p>
+
+</div>
+<!-- SECTION "GTK clipboard API" [1897-2290] -->
+<h3><a name="buffers_in_gschem" id="buffers_in_gschem">Buffers in gschem</a></h3>
+<div class="level3">
+
+<p>
+ gschem currently uses â??buffersâ?? to store cut or copied objects for pasting. A buffer is simply a GList of OBJECTs.
+</p>
+
+<p>
+When a set of selected items is â??copiedâ??:
+</p>
+<ol>
+<li class="level1"><div class="li"> Any existing items in the buffer are freed (the GList and OBJECTS destroyed).</div>
+</li>
+<li class="level1"><div class="li"> The selection is recursively copied to the buffer.</div>
+</li>
+</ol>
+
+<p>
+ When a set of selected items is â??cutâ??:
+</p>
+<ol>
+<li class="level1"><div class="li"> The copying procedure is followed.</div>
+</li>
+<li class="level1"><div class="li"> All of the selected objects are deleted.</div>
+</li>
+</ol>
+
+<p>
+ When a set of selected items is â??pastedâ??:
+</p>
+<ol>
+<li class="level1"><div class="li"> All the items in the buffer are copied into the schematic or symbolâ??s GList, with an appropriate translation applied.</div>
+</li>
+</ol>
+
+</div>
+<!-- SECTION "Buffers in gschem" [2291-2910] -->
+<h3><a name="clipboard_data_types" id="clipboard_data_types">Clipboard data types</a></h3>
+<div class="level3">
+
+</div>
+
+<h4><a name="schematic_symbol_data" id="schematic_symbol_data">Schematic/symbol data</a></h4>
+<div class="level4">
+
+<p>
+ <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=6a07d737a32a816f43e1f061409a10e616d7aa2a"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=6a07d737a32a816f43e1f061409a10e616d7aa2a"; rel="nofollow"> Implemented in 1.5.2+</a>.
+</p>
+
+<p>
+On â??copy to clipboardâ??, gschem copies the selected objects to <code>GSCHEM_TOPLEVEL→clipboard_buffer</code>, gets control of the CLIPBOARD selection, and advertises <code>application/x-geda-schematic</code> data. On receiving a request, gschem uses <code>o_save_buffer()</code> to convert the selected objects to gEDAâ??s on-disk schematic format for transmission.
+</p>
+
+<p>
+On â??paste from clipboardâ??, gschem looks to see if the current owner of the CLIPBOARD selection is advertising <code>application/x-geda-schematic</code> data. If so, gschem requests the data, and uses <code>o_read_buffer()</code> to convert it to an object list, which it then enters the paste mode for.
+</p>
+
+<p>
+To simplify the implementation, the first schematic data buffer is currently used as an intermediate store for clipboard data.
+</p>
+
+<p>
+For the time being, it is assumed destination gschem instance has its library set up correctly – i.e. no changes made to the embedding status of the data being sent before serialisation.
+</p>
+
+</div>
+<!-- SECTION "Clipboard data types" [2911-] --></body>
+</html>
diff --git a/docs/wiki/geda-xml_file_formats.html b/docs/wiki/geda-xml_file_formats.html
new file mode 100644
index 0000000..3669f04
--- /dev/null
+++ b/docs/wiki/geda-xml_file_formats.html
@@ -0,0 +1,108 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="xml_file_formats" id="xml_file_formats">XML File Formats</a></h1>
+<div class="level1">
+
+<p>
+This page is a starting point for discussions on using <acronym title="Extensible Markup Language">XML</acronym> for commonality between gEDA applications.
+</p>
+
+<p>
+One major goal of this effort is to provide advanced file format features while still maintaining backward compatibility with the existing file formats (and be able to bring an old design forward with ease if you wish).
+</p>
+
+<p>
+Another main goal is to start addressing the Symbol Library Hacker task discussed at <a href="geda-tasks.html" class="wikilink1" title="geda-tasks.html">tasks</a>.
+</p>
+
+<p>
+Yes, this effort is self concious because of <a href="geda-usage.html#can_we_change_geda_to_use_an_xml_file_format" class="wikilink1" title="geda-usage.html">can_we_change_geda_to_use_an_xml_file_format</a> The concerns expressed there will hopefully be addressed as part of this effort to minimize the impact to existing file formats, and not tie up core developer time on this work. Specifically issues 2,3,4 and 5 are valid concerns, but they can be overcome with good design and a little bit of coding, especially if this is treated as a wrapper or evolution rather than a totally new file format.
+</p>
+
+<p>
+While the initial version of the schema has both a large and small format for gschem files, it is assumed that the smaller will progress further to reduce the amount of â??file bloatâ?? associated with putting the files in this format.
+</p>
+
+<p>
+While there are plenty of arguments for and against <acronym title="Extensible Markup Language">XML</acronym>, it does provide one key feature that can be difficult to implement in a custom file format, and that is unification of the different data types each gEDA program expects with minimal impact to the existing programs. What this schema currently does is separately define gschem file formats and PCB file formats. The part schema then allows for both of these to be combined into a â??partâ?? file without change thus allowing for â??heavyâ?? parts containing both symbols and PCB elements. It will also allow for a project to be stored in a single archive file if the user so chooses. It thus provides a kind of wrapper functionality that maintains internal structure formats.
+</p>
+
+<p>
+It also introduces file format validation making sure that the file is well-formed and also, using Schematron, makes sure that constraints on data in the file are checked. This can be a real plus for managing parts like on gedasymbols.org when files can be â??easilyâ?? validated for format and content on upload with some perl code.
+</p>
+
+<p>
+An initial git repository is at <a href="http://github.com/oblivian/geda-xml/tree/master"; class="urlextern" title="http://github.com/oblivian/geda-xml/tree/master"; rel="nofollow">http://github.com/oblivian/geda-xml/tree/master</a>
+</p>
+
+<p>
+Right now it provides schema for gschem symbol and schematic files, and a PCB file format (adapted from parse.y). The part/part.xsd schema is for combining the individual schemas into a part format capable of both regular and heavy parts.
+</p>
+
+<p>
+convert-symbol.pl (when it is done) will write a gschem symbol to the <acronym title="Extensible Markup Language">XML</acronym> format. It also performs validation against the <acronym title="Extensible Markup Language">XML</acronym> Schema itself and Schematron rules also stored in the schema files.
+</p>
+
+<p>
+The <acronym title="Extensible Markup Language">XML</acronym> Schema for gschem files provides for a â??lightweightâ?? file format that should allow for an overlay on the normal file reading routines in libgeda without modification.
+</p>
+
+<p>
+So a line in gschem is represented as
+</p>
+
+<p>
+<gs:l p=â??200 800 200 200 3 0 0 0 -1 -1â?? />
+</p>
+
+<p>
+instead of
+</p>
+
+<p>
+L 200 800 200 200 3 0 0 0 -1 -1
+</p>
+
+<p>
+But the validation is handled by the <acronym title="Extensible Markup Language">XML</acronym> parser rather than writing extra validation code.
+</p>
+
+<p>
+The <acronym title="Extensible Markup Language">XML</acronym> Schema makes sure the symbols are well-formed, and the Schematron makes sure the data is valid in the â??pâ?? attributes.
+</p>
+
+<p>
+Work completed:
+</p>
+<ul>
+<li class="level1"><div class="li"> <acronym title="Extensible Markup Language">XML</acronym> Schema for gschem, PCB and .xpart file format.</div>
+</li>
+</ul>
+
+<p>
+Work that needs to be done to get this effort really started:
+</p>
+<ul>
+<li class="level1"><div class="li"> Finish convert-symbol.pl.</div>
+</li>
+<li class="level1"><div class="li"> Write <acronym title="Extensible Stylesheet Language Transformations">XSLT</acronym> to convert â??xpartâ?? file back to .sym/.fp format.</div>
+</li>
+</ul>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda_bill_wilson_s.html b/docs/wiki/geda_bill_wilson_s.html
deleted file mode 100644
index d7f8f44..0000000
--- a/docs/wiki/geda_bill_wilson_s.html
+++ /dev/null
@@ -1,27 +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>geda:bill_wilson_s</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="noindex,follow" />
-<meta name="date" content="1969-12-31T19:00:00-0500" />
-<meta name="keywords" content="geda,bill_wilson_s" />
-<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/geda:bill_wilson_s?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:bill_wilson_s"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:bill_wilson_s"; />
-<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>
-</body>
-</html>
diff --git a/docs/wiki/geda_bom_readme.html b/docs/wiki/geda_bom_readme.html
deleted file mode 100644
index 5e42f23..0000000
--- a/docs/wiki/geda_bom_readme.html
+++ /dev/null
@@ -1,64 +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>geda:bom_readme</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="geda,bom_readme" />
-<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/geda:bom_readme?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:bom_readme"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:bom_readme"; />
-<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">
-
-
-
-<h1><a name="bill_of_material_netlister_readme" id="bill_of_material_netlister_readme">Bill of Material netlister README</a></h1>
-<div class="level1">
-<pre class="code">README for
-BOM - Bill Of Materials generater for gnetlist.
-
---------------------------------------------------------------------------
-
-I (Matt) put together a quick bill of materials generator for gnetlist.
-It takes a configuration file which tells it what attributes you want
-netlisted (i.e. vendor, part number).
-
-This is a sample config file:
-
-device
-label
-name
-
-Just call it with
- gnetlist -g bom -o test.bom test.sch
-
-The config file must be called "attribs" and be in the pwd, because
-there is no way to pass arguments to the netlister (at least that I
-could find).
-
-Eventually I'd like to integrate this with some sort of a database for
-production purposes. Let me know if you are interested in helping or
-have any ideas.
-
-Matt
-matt@xxxxxxxxx
-
-</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_circuit_simulation_improvements.html b/docs/wiki/geda_circuit_simulation_improvements.html
deleted file mode 100644
index 7fc3ebf..0000000
--- a/docs/wiki/geda_circuit_simulation_improvements.html
+++ /dev/null
@@ -1,394 +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>geda:circuit_simulation_improvements</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="keywords" content="geda,circuit_simulation_improvements" />
-<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/geda:circuit_simulation_improvements?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:circuit_simulation_improvements"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:circuit_simulation_improvements"; />
-<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="#circuit_simulation_improvements_in_gschem" class="toc">Circuit simulation improvements in gschem</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#rationale" class="toc">Rationale</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#draft" class="toc">Draft</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#the_probes" class="toc">The probes</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#voltage_and_current_sources" class="toc">Voltage and current sources</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#the_simulations" class="toc">The simulations</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#creating_a_simulation_dialog_inside_gschem" class="toc">Creating a simulation dialog inside gschem</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#the_option_dialog" class="toc">The option dialog</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#invoking_the_simulation" class="toc">Invoking the simulation</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#appendix" class="toc">Appendix</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#a_current_probe_symbol_draft" class="toc">A current probe symbol (draft)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#a_voltage_probe_symbol_draft" class="toc">A voltage probe symbol (draft)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#another_current_probe_symbol_used_by_kurt_peters" class="toc">Another current probe symbol used by Kurt Peters</a></span></div></li></ul>
-</li></ul>
-</li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="circuit_simulation_improvements_in_gschem" id="circuit_simulation_improvements_in_gschem">Circuit simulation improvements in gschem</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "Circuit simulation improvements in gschem" [1-58] -->
-<h2><a name="rationale" id="rationale">Rationale</a></h2>
-<div class="level2">
-
-<p>
-Using gschem as a circuit simulation (ngspice or gnucap) frontend is not easy for novice users. A new user would like to do the following things inside gschem:
-</p>
-<ul>
-<li class="level1"><div class="li"> specify what kinds of simulations should be run</div>
-</li>
-<li class="level1"><div class="li"> specify which voltages and currents should be plotted</div>
-</li>
-<li class="level1"><div class="li"> start the simulation</div>
-</li>
-</ul>
-
-<p>
- The simulation runs and the postprocessing may be in an external programm that is triggered by IPC.
-</p>
-
-<p>
-There are some graphical frontends around but they canâ??t solve all of the above problems
-</p>
-<ul>
-<li class="level1"><div class="li"> <a href="http://www.geda.seul.org/tools/gspiceui/index.html"; class="urlextern" title="http://www.geda.seul.org/tools/gspiceui/index.html"; rel="nofollow">gspiceui</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://www.comefly.us/"; class="urlextern" title="http://www.comefly.us/"; rel="nofollow">kjwaves</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://easy-spice.sourceforge.net/"; class="urlextern" title="http://easy-spice.sourceforge.net/"; rel="nofollow">easyspice</a></div>
-</li>
-</ul>
-
-<p>
- All frontends have the problem that you can not point to the net youâ??d like to see. You need to know the netname of the node.
-</p>
-
-</div>
-<!-- SECTION "Rationale" [59-862] -->
-<h2><a name="draft" id="draft">Draft</a></h2>
-<div class="level2">
-
-<p>
-Letâ??s assume we only want to make tiny changes to gschem and libgeda so that we can at least set some probes and ran a simulation.
-</p>
-
-</div>
-<!-- SECTION "Draft" [863-1012] -->
-<h3><a name="the_probes" id="the_probes">The probes</a></h3>
-<div class="level3">
-
-<p>
-<strong>Current probes</strong> can be ordinary dc voltage sources with 0V. The easy way to insert that probe would be a symbol with two pins like an normal ampere meter. If weâ??d like to set a current probe to an end of a pin we need a netlister that detects that current probe and replaces it with our â??ampere meterâ??. If we use a voltage source as an ampere meter the netlister does not need to know the netnames inside the schematic. All 0V voltage sources with a special device name are current probes.
-</p>
-
-<p>
-<strong>Voltage probes</strong> may be current sources with 0A. The second pin of the current source is tied to GND with a net attribute. Thus again the netlister does not need to know the netnames as it can use that net that is connected with that special current sources. Like above a voltage source could be a special (graphical) symbol that is detected by a netlister.
-</p>
-
-</div>
-<!-- SECTION "The probes" [1013-1888] -->
-<h3><a name="voltage_and_current_sources" id="voltage_and_current_sources">Voltage and current sources</a></h3>
-<div class="level3">
-
-<p>
-Specifying the parameters of sources is not that easy. Currently they are stored inside the â??valueâ?? attribute of the symbol. eg. â??value=pulse 0 1 10n 10n 100n 1u 2uâ??. These settings needs to match the spice attributes â??pulse(V1 V2 TD TR TF PW PER)".
-</p>
-
-<p>
-A dialog would be nice that prompts the user for the named attributes and not only for the value string.
-</p>
-
-<p>
-A modified edit attribute (ee) command could take care of voltage and current source devices and trigger a different property dialog for that sources. Currently the multiattrib edit dialog is triggered.
-</p>
-
-</div>
-<!-- SECTION "Voltage and current sources" [1889-2487] -->
-<h3><a name="the_simulations" id="the_simulations">The simulations</a></h3>
-<div class="level3">
-
-<p>
-How can we store a simulation inside gschem.
-</p>
-
-<p>
-To store one simulation we can use a symbol with the devicename â??SIMULATIONâ??. All options that define one simulation are stored as attributes attached to that object.
-</p>
-<ul>
-<li class="level1"><div class="li"> kind of simulation (dc, ac, tran, …)</div>
-</li>
-<li class="level1"><div class="li"> simulator options</div>
-</li>
-<li class="level1"><div class="li"> the simulator? (can we run the same circuit with too simulators in one step?)</div>
-</li>
-<li class="level1"><div class="li"> simulation parameters (global parameters, temperature, …)</div>
-</li>
-</ul>
-<pre class="code">
-v 20061020 1
-C 41500 49200 1 0 0 spice-directive-1.sym
-{
-device=spice_simulation_block
-refdes=A1
-simulation_name=random name
-simulation_active=1
-simulation_type=DC 0V 1V 0.1V
-parametric_simulation1=V1 lin 0 5 0.1
-parametric_simulation2=R1.value lin 10k 100k 10k
-option_TNOM=100 Deg
-option_ABSTOL=1e-3
-global_param1=???
-global_param2=???
-}
-</pre>
-
-<p>
-There may be many simulation objects inside a single schematic.
-</p>
-
-<p>
-To store additional libraries we can either use an include card or using a â??LIBRARYâ?? symbol that contains all libraries either as:
-</p>
-<ul>
-<li class="level1"><div class="li"> a multiline attribute</div>
-</li>
-<li class="level1"><div class="li"> multiple attached library attributes to the LIBRARY symbol</div>
-</li>
-</ul>
-
-<p>
- There should be a distinction between global, user and local libs. global and user libs may be specified by a gafrc or a new spicerc configuration file.
-</p>
-
-</div>
-<!-- SECTION "The simulations" [2488-3735] -->
-<h3><a name="creating_a_simulation_dialog_inside_gschem" id="creating_a_simulation_dialog_inside_gschem">Creating a simulation dialog inside gschem</a></h3>
-<div class="level3">
-
-<p>
- Lets assume anything we need to add simulation support to gschem is a single dialog.
-</p>
-<ul>
-<li class="level1"><div class="li"> It would have a list of simulations (listview with enable/disable buttons and simulation names)</div>
-</li>
-<li class="level1"><div class="li"> It would have some icons to add the probes. </div>
-</li>
-<li class="level1"><div class="li"> It may have buttons for the most common symbols: resistor, capacitor, inductor, diode, … [R,C,L,D,M,E,F,G,H..]</div>
-</li>
-<li class="level1"><div class="li"> It would have some dialog elements to do the spice settings</div>
-</li>
-<li class="level1"><div class="li"> It would have a simulate and a close button</div>
-</li>
-<li class="level1"><div class="li"> Some additional buttons like: Copy simulation, Remove simulation, general options…</div>
-</li>
-</ul>
-
-<p>
- When creating that dialog all simulation objects are collected into the simulation list (listview with enable/disable checkbutton)
-</p>
-
-<p>
-When changing the settings the attributes of the assosiated simulation object are changed.
-</p>
-
-</div>
-<!-- SECTION "Creating a simulation dialog inside gschem" [3736-4567] -->
-<h3><a name="the_option_dialog" id="the_option_dialog">The option dialog</a></h3>
-<div class="level3">
-
-<p>
-What kind of options do we need for that dialog? And Why?
-</p>
-
-<p>
-The probes that we have placed can be used to tell the simulator the variables that we like to save or tell the plotting application which plots weâ??d like to see. This is something completely different, we need an option for that:
-</p>
-<ul>
-<li class="level1"><div class="li"> plot all marks and only save the corresponding node voltages</div>
-</li>
-<li class="level1"><div class="li"> plot all marks but save all node voltages and currents (through voltage sources)</div>
-</li>
-<li class="level1"><div class="li"> only save voltage nodes of the current schematic level or store subcircuit node voltages, too.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "The option dialog" [4568-5135] -->
-<h3><a name="invoking_the_simulation" id="invoking_the_simulation">Invoking the simulation</a></h3>
-<div class="level3">
-
-<p>
-The simulation button of the dialog should lead to the following actions:
-</p>
-<ul>
-<li class="level1"><div class="li"> save the schematic (ask the user or use a temporary file?)</div>
-</li>
-<li class="level1"><div class="li"> create a netlist using gnetlist</div>
-</li>
-<li class="level1"><div class="li"> create simulation files and include the netlist (can this be done with gnetlist too?)</div>
-</li>
-<li class="level1"><div class="li"> execute the simulation startup script (guile, sh, …)</div>
-</li>
-</ul>
-
-<p>
- That startup script may even call a scheduler that can take lots of large simulations.
-</p>
-
-</div>
-<!-- SECTION "Invoking the simulation" [5136-5581] -->
-<h2><a name="appendix" id="appendix">Appendix</a></h2>
-<div class="level2">
-
-</div>
-<!-- SECTION "Appendix" [5582-5602] -->
-<h3><a name="a_current_probe_symbol_draft" id="a_current_probe_symbol_draft">A current probe symbol (draft)</a></h3>
-<div class="level3">
-<pre class="code">
-v 20061020 1
-P 0 0 200 200 1 0 0
-{
-T 100 0 5 10 0 1 0 0 1
-pintype=pas
-T 0 100 5 10 0 1 0 0 1
-pinseq=1
-T 0 100 5 10 0 1 0 0 1
-pinnumber=1
-T 0 100 5 10 0 1 0 0 1
-pinlabel=1
-}
-V 300 300 150 3 10 0 0 -1 -1 0 -1 -1 -1 -1 -1
-L 300 200 240 360 3 10 0 0 -1 -1
-L 300 200 360 360 3 10 0 0 -1 -1
-T 0 500 9 10 0 0 0 0 1
-device=VOLTAGE_PROBE
-T 200 50 9 6 1 1 0 0 1
-refdes=I_VP?
-T 0 700 9 10 0 0 0 0 1
-net=GND:2
-T 0 900 9 10 0 0 0 0 1
-value=DC 0A
-</pre>
-
-</div>
-<!-- SECTION "A current probe symbol (draft)" [5603-6092] -->
-<h3><a name="a_voltage_probe_symbol_draft" id="a_voltage_probe_symbol_draft">A voltage probe symbol (draft)</a></h3>
-<div class="level3">
-<pre class="code">
-v 20061020 1
-P 0 200 150 200 1 0 0
-{
-T -150 50 5 10 0 1 0 0 1
-pintype=pas
-T 50 250 5 10 0 1 0 0 1
-pinseq=1
-T 50 250 5 10 0 1 0 0 1
-pinnumber=1
-T 50 250 5 10 0 1 0 0 1
-pinlabel=1
-}
-V 300 200 150 3 10 0 0 -1 -1 0 -1 -1 -1 -1 -1
-L 300 300 380 140 3 10 0 0 -1 -1
-L 300 300 220 140 3 10 0 0 -1 -1
-T 0 500 9 10 0 0 0 0 1
-device=CURRENT_PROBE
-T 200 370 9 6 1 1 0 0 1
-refdes=V_IP?
-P 600 200 450 200 1 0 0
-{
-T 500 50 5 10 0 1 0 0 1
-pintype=pas
-T 500 250 5 10 0 1 0 0 1
-pinseq=2
-T 500 250 5 10 0 1 0 0 1
-pinnumber=2
-T 500 250 5 10 0 1 0 0 1
-pinlabel=2
-}
-L 240 180 360 180 3 10 0 0 -1 -1
-T 0 700 9 10 0 0 0 0 1
-value=DC 0V
-</pre>
-
-</div>
-<!-- SECTION "A voltage probe symbol (draft)" [6093-6761] -->
-<h3><a name="another_current_probe_symbol_used_by_kurt_peters" id="another_current_probe_symbol_used_by_kurt_peters">Another current probe symbol used by Kurt Peters</a></h3>
-<div class="level3">
-<pre class="code">
-v 20061020 1
-T 700 650 8 10 1 1 0 0 1
-refdes=VAM?
-T 700 850 5 10 1 1 0 0 1
-device=Ammeter
-T 700 1050 5 10 0 0 0 0 1
-footprint=none
-T 700 1250 5 10 0 0 0 0 1
-numslots=0
-T 700 1450 5 10 0 0 0 0 1
-description=ammeter for spice
-P 300 1200 300 900 1 0 0
-{
-T 350 1000 5 8 1 1 0 0 1
-pinnumber=1
-T 350 1000 5 8 0 1 0 2 1
-pinseq=1
-T 400 850 9 8 1 1 0 5 1
-pinlabel=+
-T 300 700 5 8 0 1 0 5 1
-pintype=pwr
-}
-P 300 0 300 300 1 0 0
-{
-T 350 100 5 8 1 1 0 0 1
-pinnumber=2
-T 350 100 5 8 0 1 0 2 1
-pinseq=2
-T 300 500 5 8 0 1 0 3 1
-pintype=pwr
-T 300 300 5 10 1 1 0 0 1
-pinlabel=-
-}
-L 300 400 400 500 3 0 0 0 -1 -1
-L 200 500 300 400 3 0 0 0 -1 -1
-T 700 450 5 10 0 1 0 0 1
-value=DC 0V
-L 300 400 300 800 3 0 0 0 -1 -1
-L 100 800 500 400 3 0 0 0 -1 -1
-B 0 300 600 600 3 0 0 0 -1 -1 0 -1 -1 -1 -1 -1
-L 200 800 100 800 3 0 0 0 -1 -1
-L 100 700 100 800 3 0 0 0 -1 -1
-</pre>
-
-</div>
-<!-- SECTION "Another current probe symbol used by Kurt Peters" [6762-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/geda_covered_mp.html b/docs/wiki/geda_covered_mp.html
deleted file mode 100644
index 524c009..0000000
--- a/docs/wiki/geda_covered_mp.html
+++ /dev/null
@@ -1,244 +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>geda:covered_mp</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="geda,covered_mp" />
-<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/geda:covered_mp?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:covered_mp"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:covered_mp"; />
-<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">
-
-
-
-<h1><a name="covered_man-page" id="covered_man-page">covered man-page</a></h1>
-<div class="level1">
-<pre class="code">Covered(1) Code Analysis Covered(1)
-
-
-
-NAME
- Covered - Verilog Code Coverage Analyzer
-
-SYNTAX
- covered [<options>] score [<options>]
- covered [<options>] merge [<options>] <existing_database>
- <database_to_merge>
- covered [<options>] report [<options>] <database_file>
-
-DESCRIPTION
- Covered is a Verilog code coverage analysis tool that can be useful for
- determining how well a diagnostic test suite is covering the design
- under test. Covered reads in the Verilog design files and a VCD or LXT
- formatted dumpfile from a diagnostic run and generates a database file
- called a Coverage Description Database (CDD) file, using the score com-
- mand. This file can be merged with other CDD files from the same
- design to create accummulated coverage, using the merge command. Once
- a CDD file is created, the user can use Covered to generate various
- human-readable coverage reports in an ASCII format or use Covered�s GUI
- to interactively look at coverage results, using the report command.
- Additionally, as part of Covered�s score command, race condition possi-
- bilities are found in the design files and can be either ignored,
- flagged as warnings or flagged as errors. By specifying race condi-
- tions as errors, Covered can also be used as a race condition checker.
-
-GLOBAL OPTIONS
- These options are placed immediately after the keyword covered in the
- command-line. They can be used for any command (with the exception of
- -v and -h) and have the same effect in each case.
-
- -D Debug. Display information helpful for debugging tool problems.
- Note: This option is now only available when covered is built
- with the --enable-debug configuration option.
-
- -h Help. Display this usage information.
-
- -Q Quiet mode. Causes all output to be suppressed.
-
- -v Version. Display current Covered version.
-
-COMMANDS
- score Parses Verilog files and VCD/LXT dumpfiles to create database
- file used for merging and reporting.
-
- merge Merges two database files into one.
-
- report Generates human-readable coverage reports from database file or
- starts the coverage report GUI.
-
-SCORE COMMAND
- The following options are valid for the score command:
-
- -D define_name
- Defines the specified name to 1.
-
- -D define_name=value
- Defines the specified name to the specified value.
-
- -e block_name
- Name of module, task, function or named begin/end block to not
- score. Causes all subblocks in the Verilog tree under this
- block to also not be scored.
-
- -ea Excludes all always blocks from being considered for coverage.
-
- -ec Excludes all continuous assignments from being considered for
- coverage.
-
- -ei Excludes all initial blocks from being considered for coverage.
-
- -F module_name=(in_expr,)out_expr
- Indicates to the parser where to find the FSM located in module
- module_name which has an input state expression called in_expr
- and output state expression called out_expr. If in_expr is not
- specified, out_expr is used as both the input and output state
- expression.
-
- -f filename
- Name of file containing additional arguments to parse.
-
- -h Displays this help information.
-
- -I directory
- Directory to find included Verilog files.
-
- -i instance_name
- Verilog hierarchical reference to the module that is at the top
- of the tree to be scored. This option is necessary if module to
- verify coverage is not the top-level module in the design. If
- not specified, -t value is used.
-
- -lxt filename
- Name of LXT/LXT2 dumpfile to score design with. If this or the
- -vcd option is not used, Covered will only create an initial CDD
- file from the design and will not attempt to score the design.
-
- -o database
- Name of database to write coverage information to. If not spec-
- ified, the output database filename will be "cov.cdd".
-
- -p filename
- Overrides default filename used to store intermediate preproces-
- sor output.
-
- -P parameter_scope=value
- Performs a defparam on the specified parameter with value.
-
- -r(S|W|E)
- Specifies action to take when race condition checking finds
- problems in design (-rS = Silent, -rW = Warning, -rE = Error).
-
- -S Outputs simulation statistics after simulation has completed.
- This information is currently only useful for the developers of
- Covered.
-
- -t top-level module
- Specifies the module name of the top-most module that will be
- measured. Note that this module does not need to be the
- top-most module in the simulator. This field is required for
- all calls to the score command.
-
- -ts number
- When scoring occurs, this option allows the user to see how far
- the simulator has progressed by outputting the current timestep
- to standard output. The value of number specifies how many
- timesteps are allowed to be simulated before outputting the cur-
- rent timestep (results in less calls to output stream).
-
- -T min|typ|max
- Specifies which value to use when encountering a delay expres-
- sion in the form: min:typ:max. If this option is not speci-
- fied, �typ� select is used by default.
-
- -v filename
- Name of specific Verilog file to score.
-
- -vcd filename
- Name of VCD dumpfile to score design with. If this or the -lxt
- option is not used, Covered will only create an initial CDD file
- from the design and will not attempt to score the design.
-
- -y directory
- Directory to find unspecified Verilog files.
-
- +libext+.extension(+.extension)*+
- Extensions of Verilog files to allow in scoring.
-
-MERGE COMMAND
- The following options are valid for the merge command:
-
- -h Displays this help information.
-
- -o filename
- File to output new database to. If this argument is not speci-
- fied, the existing_database is used as the output database name.
-
-REPORT COMMAND
- The following options are valid with the report command:
-
- -c If -v is specified, displays covered line, toggle and combina-
- tional cases. Default is to display uncovered information.
-
- -d (s|d|v)
- Level of detail to provide in coverage report information (s =
- summary, d = detailed, v = verbose). Default is summary.
-
- -h Displays this help information.
-
- -i Provides coverage information for instances instead of module.
-
- -m [l][t][c][f][r]
- Type(s) of metrics to report. Default is ltcf.
-
- -o filename
- File to output report information to. Default is standard out-
- put.
-
- -v Deprecated. Replaced by �-d d� or �-d v�.
-
- -view Starts the GUI interface for interactive coverage reporting.
-
- -w (number)
- Specifies the maximum line width (in characters) that can be
- used to output Verilog information. If this option is not spec-
- ified, all Verilog code in the report will retain the same for-
- matting as was specified in the original Verilog code. If this
- option is specified, Verilog code will be formatted to use as
- much of the current line as possible, wrapping text when the
- line reaches the maximum line width. The default maximum line
- width is 115 characters (this value is used if no number is
- specified with the -w option). If a number is specified with
- the -w option, this value is used for the maximum line width.
-
-AUTHORS
- Trevor Williams <trevorw@xxxxxxxxxxx>
-
- Arpan Sen <arpan_sen@xxxxxxxxx>
-
-SEE ALSO
- For more information on how to use the Covered code coverage tool,
- please consult the on-line User�s Guide at http://covered.source-
- forge.net/user/index.html.
-
-
-
-Trevor Williams covered-20060218 Covered(1)</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_covered_rv.html b/docs/wiki/geda_covered_rv.html
deleted file mode 100644
index 8968631..0000000
--- a/docs/wiki/geda_covered_rv.html
+++ /dev/null
@@ -1,27 +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>geda:covered_rv</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="noindex,follow" />
-<meta name="date" content="1969-12-31T19:00:00-0500" />
-<meta name="keywords" content="geda,covered_rv" />
-<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/geda:covered_rv?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:covered_rv"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:covered_rv"; />
-<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>
-</body>
-</html>
diff --git a/docs/wiki/geda_csygas.html b/docs/wiki/geda_csygas.html
deleted file mode 100644
index 644cf49..0000000
--- a/docs/wiki/geda_csygas.html
+++ /dev/null
@@ -1,1407 +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>geda:csygas</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2008-04-04T12:04:48-0400" />
-<meta name="keywords" content="geda,csygas" />
-<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/geda:csygas?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:csygas"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:csygas"; />
-<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="#circuit_simulation_using_geda_and_spice_-_howto" class="toc">Circuit Simulation using gEDA and SPICE - HOWTO</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#introduction" class="toc">Introduction</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#target_audience_for_this_howto" class="toc">Target audience for this HOWTO</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#acknowledgements" class="toc">Acknowledgements</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#the_big_picturethe_design_flow_in_geda" class="toc">The big picture: the design flow in gEDA</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#overview_of_spice_usage_with_geda" class="toc">Overview of SPICE usage with gEDA</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#detailed_design_simulation_flow_summary" class="toc">Detailed design/simulation flow summary</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#preliminary_workpreparing_your_symbols_and_spice_files" class="toc">Preliminary work: preparing your symbols and SPICE files</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#configuring_your_symbols" class="toc">Configuring your symbols</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#configuring_your_spice_files" class="toc">Configuring your SPICE files</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#creating_your_circuitschematic_capture" class="toc">Creating your circuit: schematic capture</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#gschem_attributes_for_spice_netlisting" class="toc">Gschem attributes for spice netlisting</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#component_attributes_and_meanings" class="toc">Component attributes and meanings</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#refdes_conventions" class="toc">refdes conventions</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#passives" class="toc">Passives</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#passives_with_additional_attributes" class="toc">Passives with additional attributes</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#passives_for_semiconductor_design" class="toc">Passives for semiconductor design</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#transistors_and_diodes" class="toc">Transistors and diodes</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#actives_--_integrated_circuits" class="toc">Actives -- integrated circuits</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#independent_sources" class="toc">Independent sources</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#dependent_sources" class="toc">Dependent sources</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#spice_components" class="toc">SPICE components</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#handling_hierarchical_models" class="toc">Handling hierarchical models</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#spice_netlist_generation" class="toc">SPICE netlist generation</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#using_gnetlist" class="toc">Using gnetlist</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#creating_the_netlist_using_gnetlist_and_spice-sdb" class="toc">Creating the netlist using gnetlist and spice-sdb</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#common_netlisting_problems" class="toc">Common netlisting problems</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#spice_simulation" class="toc">SPICE simulation</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#ltspice" class="toc">LTSpice</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#ngspice" class="toc">Ngspice</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#tclspice" class="toc">Tclspice</a></span></div></li>
-</ul>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"><span class="li"><a href="#appendix_a" class="toc">Appendix A</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#appendix_b" class="toc">Appendix B</a></span></div></li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="circuit_simulation_using_geda_and_spice_-_howto" id="circuit_simulation_using_geda_and_spice_-_howto">Circuit Simulation using gEDA and SPICE - HOWTO</a></h1>
-<div class="level1">
-
-<p>
-Stuart Brorson<br/>
- Electroniscript, inc.<br/>
- sdb@xxxxxxxxxxxxxxxxxxx<br/>
- <br/>
- 5th January 2006
-</p>
-
-<p>
-<strong>abstract</strong><br/>
- Linux will become an increasingly popular engineering platform in the future. Professional-quality CAD applications for circuit design are becoming available from programmers within the free-software community. For electronics, the gEDA suite is the preferred tool set for circuit design. Analog circuit simulation using SPICE is also now available on Linux. This HOWTO describes the design flow employed to perform SPICE simulations using gEDA tools on Linux.
-</p>
-
-<p>
-Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 2 or any later version published by the Free Software Foundation with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. You may obtain a copy of the GNU Free Documentation License from the Free Software Foundation by visiting their Web site (<a href="http://www.fsf.org/"; class="urlextern" title="http://www.fsf.org/"; rel="nofollow">http://www.fsf.org/</a>) by writing to: Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. <a href="#fn__1" name="fnt__1" id="fnt__1" class="fn_top">1)</a>.
-</p>
-
-</div>
-<!-- SECTION "Circuit Simulation using gEDA and SPICE - HOWTO" [1-1357] -->
-<h2><a name="introduction" id="introduction">Introduction</a></h2>
-<div class="level2">
-
-<p>
-Modern engineering is a computer-intensive discipline. Like professionals in other engineering disciplines, electrical engineers and electronics designers are heavy users of all kinds of CAD software, including software for circuit design and simulation, as well as PCB and chip production. Electrical engineers have a special name for the CAD software they use: EDA, which stands for â??Electronic Design Automationâ??. Under this rubric fall many different kinds of CAD software. For example, during the front-end stages of a design, an electrical engineer will use a program called a â??schematic captureâ?? package to enter his design into the computer. A schematic capture program is basically a specialized drawing program incorporating symbols used in creating a circuit design. After drawing his schematic, the electrical engineer may choose to simulate the behavior of his circuit in order to verify that his design will work as desired. The most popular program for this purpose is SPICE (Simulation Program with Integrated Circuit Emphasis), which was developed at Berkeley starting in the 1970s, and is widely available in multiple forms today. SPICE is now considered a fundamental engineering tool, and is an essential part of the repertoire of most practicing engineers.
-</p>
-
-<p>
-The <a href="http://www.geda.seul.org/"; class="urlextern" title="http://www.geda.seul.org/"; rel="nofollow">gEDA project</a> is an open-source effort to create a <acronym title="GNU General Public License">GPL</acronym>â??ed EDA suite running on Linux. GEDA has developed to the point where the power and quality of the tools is quite high; using the gEDA suite, you can now create complex SPICE netlists (files) incorporating vendor model files. You can then use various simulators running on Linux to perform SPICE simulations of your netlists. The purpose of this document is to explain how to use the gEDA tools (typically running on GNU/Linux) to perform SPICE simulations. In particular, this HOWTO documents the usage of <strong>spice-sdb</strong>, which is an advanced backend for the gEDA netlister (<strong>gnetlist</strong>) used to create SPICE netlists. <strong>spice-sdb</strong> is bundled with the gEDA tool suite; if you have installed gEDA, you are ready to create SPICE netlists. This HOWTO also provides advice about using ngspice/tclspice and/or LTSpice to simulate a circuit netlisted with <strong>spice-sdb</strong>.
-</p>
-
-</div>
-<!-- SECTION "Introduction" [1358-3623] -->
-<h3><a name="target_audience_for_this_howto" id="target_audience_for_this_howto">Target audience for this HOWTO</a></h3>
-<div class="level3">
-
-<p>
-This HOWTO is not a tutorial about circuit design or SPICE simulation. Rather, it is designed to help the practicing engineer begin using gEDA to perform SPICE simulations on the Linux platform. Therefore, I assume that you are already familiar with electronic design, the mechanics of schematic capture using EDA tools, and SPICE simulation in general. I also assume that you are reasonably familiar with the GNU/Linux operating system and its development environment. Finally, I assume that you have already installed gEDA, and know how to use it. If you need to come up to speed on any of these subjects, further information is available at the following websites:
-</p>
-<ul>
-<li class="level1"><div class="li"> The gEDA project: <a href="http://www.geda.seul.org/"; class="urlextern" title="http://www.geda.seul.org"; rel="nofollow">http://www.geda.seul.org</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:faq-simulation"; class="wikilink1" title="geda:faq-simulation">faq-simulation</a></div>
-</li>
-<li class="level1"><div class="li"> SPICE3 syntax and commands: <a href="http://newton.ex.ac.uk/teaching/CDHW/Electronics2/userguide/"; class="urlextern" title="http://newton.ex.ac.uk/teaching/CDHW/Electronics2/userguide/"; rel="nofollow">http://newton.ex.ac.uk/teaching/CDHW/Electronics2/userguide/</a></div>
-</li>
-<li class="level1"><div class="li"> Ngspice: <a href="http://ngspice.sourceforge.net/"; class="urlextern" title="http://ngspice.sourceforge.net/"; rel="nofollow">http://ngspice.sourceforge.net/</a></div>
-</li>
-<li class="level1"><div class="li"> Tclspice: <a href="http://tclspice.sourceforge.net/"; class="urlextern" title="http://tclspice.sourceforge.net/"; rel="nofollow">http://tclspice.sourceforge.net/</a></div>
-</li>
-<li class="level1"><div class="li"> LTSpice: <a href="http://www.linear.com/software/"; class="urlextern" title="http://www.linear.com/software/"; rel="nofollow">http://www.linear.com/software/</a></div>
-</li>
-<li class="level1"><div class="li"> Spice on Linux resources: <a href="http://www.brorson.com/gEDA/SPICE/"; class="urlextern" title="http://www.brorson.com/gEDA/SPICE/"; rel="nofollow">http://www.brorson.com/gEDA/SPICE/</a></div>
-</li>
-<li class="level1"><div class="li"> Free Dog – The Free EDA Users Group: <a href="http://www.freeedaug.org/"; class="urlextern" title="http://www.freeedaug.org/"; rel="nofollow">http://www.freeedaug.org/</a></div>
-</li>
-<li class="level1"><div class="li"> Starting with gEDA – slightly out of date, but a great resource <a href="http://www-mdp.eng.cam.ac.uk/CD/engapps/geda/starting_gEDA_long.pdf"; class="urlextern" title="http://www-mdp.eng.cam.ac.uk/CD/engapps/geda/starting_gEDA_long.pdf"; rel="nofollow">http://www-mdp.eng.cam.ac.uk/CD/engapps/geda/starting_gEDA_long.pdf</a></div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Target audience for this HOWTO" [3624-4971] -->
-<h3><a name="acknowledgements" id="acknowledgements">Acknowledgements</a></h3>
-<div class="level3">
-
-<p>
-This document does not live in isolation. Several active members of the free EDA community were instrumental in helping me to creat this HOWTO. First and foremost, Paolo Nenzi, the author of ngspice, took my original HOWTO and turned it into a Lyx document which I could then make a DocBook. Thanks, Paolo, for helping with this HOWTO, and more importantly, thanks for all the great work on ngspice! Also at the top of the list stands Ales Hvezda, who is the driving force behind the gEDA project. Without Ales, none of this would have been possible; his contribution of <strong>gschem</strong> is invaluable. Thanks, Ales, for creating gEDA and distributing it worldwide under the <acronym title="GNU General Public License">GPL</acronym> – youâ??ve started a revolution! Stefan Jones deserves a deep thank-you for his work on tclspice, and his graceous support and integration efforts when I submitted patches to the tclspice project. I should also thank W. Kazubski and S. Gieltjes – they wrote the original SPICE netlisters upon which I based gnet-spice-sdb.scm. I also want to thank Ken Healy for contributing the netlist sorting patch, and Peter Kaiser for pushing me to include some features useful for chip simulation. Peter also deserves thanks for writing some of the device-oriented sections of this document. Finally, I should acknolwedge the contributions and suggestions I receive from readers of the geda-user e-mail list. The beauty of free software is that it encourages collaboration, which means that the end product is greater than what one individual could acheive alone.
-</p>
-
-</div>
-<!-- SECTION "Acknowledgements" [4972-6526] -->
-<h3><a name="the_big_picturethe_design_flow_in_geda" id="the_big_picturethe_design_flow_in_geda">The big picture: the design flow in gEDA</a></h3>
-<div class="level3">
-
-<p>
-In EDA, the concept of â??design flowâ?? is important. GEDA is a suite of tools used to do electronic design – it is not a single application. â??Design flowâ?? refers to the order in which you use the tools to acheive your goal. Depending upon whether you are doing analog or digital design, designing boards or chips, the type of files required by the manufacturer of your boards, and a number of other factors, you will use different tools from the gEDA suite to acheive your goal.
-</p>
-
-<p>
-A flow diagram of the gEDA design flow is shown in the figure below. The diagram shows a simple flow suitable for designing, simulating, and laying out PC boards. As can be seen, the simulation activitiy (blue blocks) is a loop. That is, you create your design and simulate it repeatedly until it behaves according to your desired specifications. <a href="_detail/geda_geda_flow.html" class="media" title="geda:geda_flow.png"><img src="_media/geda_geda_flow.png" class="mediacenter" alt="" /></a> The design flow used in gEDA. Shown under â??simulationâ?? are several different types of simulator available. In this HOWTO, we are interested only in the SPICE variants (e.g. ngspice, tclspice).
-</p>
-
-</div>
-<!-- SECTION "The big picture: the design flow in gEDA" [6527-7623] -->
-<h3><a name="overview_of_spice_usage_with_geda" id="overview_of_spice_usage_with_geda">Overview of SPICE usage with gEDA</a></h3>
-<div class="level3">
-
-<p>
-Conceptually, SPICE simulation in gEDA proceeds via the following steps:
-</p>
-<ol>
-<li class="level1"><div class="li"> Creation and gathering of schematic symbols and SPICE model files. Often, the SPICE model files are obtained from your component vendor. You can generally find most models by checking the component vendorâ??s website.</div>
-</li>
-<li class="level1"><div class="li"> Schematic capture using symbols and SPICE models created in step 1.</div>
-</li>
-<li class="level1"><div class="li"> Netlist generation from the schematic created in step 2.</div>
-</li>
-<li class="level1"><div class="li"> SPICE simulation of the circuit described by the netlist created in step 3.</div>
-</li>
-</ol>
-
-<p>
- These steps are illustrated by the blue boxes in the flow diagram above.
-</p>
-
-<p>
-To create a SPICE netlist, the netlister (<strong>gnetlist</strong>) iterates through the entire schematic and looks at several parts of each componentâ??s symbol in order to create a blob of SPICE code. In general, each component can generate one or more lines of SPICE code. Component information needed by the netlister is held in two places:
-</p>
-<ol>
-<li class="level1"><div class="li"> The symbol itself, in the attribute, which is attached when the symbol is created, and is typically accessed through the symbol editor.</div>
-</li>
-<li class="level1"><div class="li"> In attributes manually attached to the component during schematic capture using <strong>gschem</strong>.</div>
-</li>
-</ol>
-
-<p>
- Since there are two places the netlister looks for information, <strong><em>you must make sure that the required information is available in both places</em></strong>.
-</p>
-
-</div>
-<!-- SECTION "Overview of SPICE usage with gEDA" [7624-8967] -->
-<h3><a name="detailed_design_simulation_flow_summary" id="detailed_design_simulation_flow_summary">Detailed design/simulation flow summary</a></h3>
-<div class="level3">
-
-<p>
-The detailed steps required to design and simulate a circuit using gEDA look like this:
-</p>
-<ol>
-<li class="level1"><div class="li"> Schematic symbol creation with correct <strong><code>device</code></strong> attribute. (Usually, the symbols have already been created with the correct <strong><code>device</code></strong> attribute, but if you are having problems, it doesnâ??t hurt to check them.)</div>
-</li>
-<li class="level1"><div class="li"> Schematic capture using <strong>gschem</strong>.</div>
-</li>
-<li class="level1"><div class="li"> Assignment of SPICE attributes (<strong><code>value</code></strong>, <strong><code>model</code></strong>, <strong><code>file</code></strong>, <strong><code>type</code></strong>, , etc.) to components using <strong>gschem</strong> or <strong>gattrib</strong>.</div>
-</li>
-<li class="level1"><div class="li"> Assignment of <strong><code>refdes</code></strong> using e.g. <strong>refdes_renum</strong>.</div>
-</li>
-<li class="level1"><div class="li"> Creation of netlist using: <strong><code>gnetlist -g spice-sdb</code></strong></div>
-</li>
-<li class="level1"><div class="li"> Check netlist for correctness (manually open and inspect netlist).</div>
-</li>
-<li class="level1"><div class="li"> Run spice using a simulator such as <strong>LTSpice</strong>, <strong>ngspice</strong>, or <strong>tclspice</strong>.</div>
-</li>
-<li class="level1"><div class="li"> Plot/analyze results (often plotting/analysis tools are incorporated in the simulator).</div>
-</li>
-<li class="level1"><div class="li"> If you are not happy with your circuitâ??s performance as revealed by simulation, go back to step 2, fix it using <strong>gschem</strong> and iterate.</div>
-</li>
-</ol>
-
-<p>
- The purpose of this HOWTO is to provide the detailed understanding necessary to successfully navigate this process.
-</p>
-
-</div>
-<!-- SECTION "Detailed design/simulation flow summary" [8968-10147] -->
-<h2><a name="preliminary_workpreparing_your_symbols_and_spice_files" id="preliminary_workpreparing_your_symbols_and_spice_files">Preliminary work: preparing your symbols and SPICE files</a></h2>
-<div class="level2">
-
-<p>
-When you create schematic symbols for inclusion into your schematic, you must make sure that certain built-in attributes are correctly configured. The steps outlined below are done by editing the symbol itself using the symbol editor in <strong>gschem</strong>, or by editing the symbol file itself using a text editor.
-</p>
-
-</div>
-<!-- SECTION "Preliminary work: preparing your symbols and SPICE files" [10148-10526] -->
-<h3><a name="configuring_your_symbols" id="configuring_your_symbols">Configuring your symbols</a></h3>
-<div class="level3">
-
-</div>
-
-<h4><a name="identifying_the_component_to_the_netlister" id="identifying_the_component_to_the_netlister">Identifying the component to the netlister</a></h4>
-<div class="level4">
-
-<p>
-The SPICE netlister can recognize any particular symbol in two ways:
-</p>
-<ol>
-<li class="level1"><div class="li"> The symbolâ??s <strong><code>device</code></strong> attribute, and</div>
-</li>
-<li class="level1"><div class="li"> The symbolâ??s <strong><code>refdes</code></strong>.</div>
-</li>
-</ol>
-
-<p>
- Both of these attributes are attached to the symbol when the symbol is created.
-</p>
-
-<p>
-Each symbol has a <strong><code>device</code></strong> attribute attached to it. The <strong><code>device</code></strong> attribute is the first thing the netlister examines when processing the symbol. There are a number of devices which are native to the netlister, meaning that the netlister knows exactly how to deal with these types of devices. Native device types include <strong>RESISTOR</strong>, <strong>CAPACITOR</strong>, <strong>NPN_TRANSISTOR</strong>, etc. The entire list of native devices is present in <a href="#appendix_a" title="geda:csygas ↵" class="wikilink1">Appendix A</a> - Native components and their attributes.
-</p>
-
-<p>
-The <strong><code>device</code></strong> attribute is hidden during normal use of <strong>gschem</strong>. Most often, the symbolâ??s creator has already given the symbol the correct <strong><code>device</code></strong> attribute. However, because the <strong><code>device</code></strong> attribute is hidden from the ordinary user, it can sometimes cause problems with SPICE netlist creation when it is set to an unexpected value. To view the <strong><code>device</code></strong> attribute, go into the symbol editor (select the symbol to edit, and do <strong><em>Hierarchy</em></strong> → <strong><em>down symbol</em></strong>, and turn on invisible attributes (<strong><em>Edit</em></strong> → <strong><em>show/hide inv text</em></strong>). If the <strong><code>device</code></strong> attribute is incorrect, you may change it by editing the symbol itself using a text editor.
-</p>
-
-<p>
-If a symbol is not native (i.e. the netlister doesnâ??t recognize it as a built-in type), the netlister relies upon the first letter of the <strong><code>refdes</code></strong> to determine how to process the symbol. The <strong><code>refdes</code></strong> prefix is also built into the symbol when it is created. Example <strong><code>refdes</code></strong> prefixes are <strong>R</strong> for resistors, <strong>C</strong> for capacitors, <strong>Q</strong> for transistors, etc. <strong><code>refdes</code></strong> prefixes correct for SPICE are listed in <a href="#appendix_a" title="geda:csygas ↵" class="wikilink1">Appendix A</a> - Native components and their attributes. Note that relying upon the <strong><code>refdes</code></strong> to identify the component for SPICE is not foolproof – for example, the netlister cannot distinguish between NPN and PNP transistors based upon the <strong><code>refdes</code></strong>. Therefore, it is always best to use a native <strong><code>device</code></strong> in your symbols.
-</p>
-
-</div>
-
-<h4><a name="setting_the_pin_order" id="setting_the_pin_order">Setting the pin order</a></h4>
-<div class="level4">
-
-<p>
-The netlister emits component pins in the order set by the <strong><code>pinseq</code></strong> attribute. Note that this is not the same as the physical pin location. To set the <strong><code>pinseq</code></strong> attribute, first determine the pin ordering you want. SPICE uses a specific pin order for many components, including diodes and transistors. For example, a bipolar transistorâ??s pins listed in CBE order. Another example: if your symbol is meant to represent an IC modeled with a vendorâ??s <strong><code>.subckt</code></strong>, the order of the connections to the subcircuit is set by the <strong><code>.subckt</code></strong> line in the file.
-</p>
-
-<p>
-Once you know the order in which to emit the pins, simply set the <strong><code>pinseq</code></strong> attribute with the correct order for the part. This will ensure that the partâ??s pins are emitted in the correct order.
-</p>
-
-</div>
-<!-- SECTION "Configuring your symbols" [10527-13603] -->
-<h3><a name="configuring_your_spice_files" id="configuring_your_spice_files">Configuring your SPICE files</a></h3>
-<div class="level3">
-
-<p>
-Files holding complicated SPICE models or other SPICE code may be incorporated into the final SPICE netlist by including appropriate symbols into the schematic. SPICE model files are usually obtained from component vendors. Dealing with these files is straightforward. However, some issues should be kept in mind when preparing models for use during schematic capture:
-</p>
-<ul>
-<li class="level1"><div class="li"> It is usually prudent to place these files into a dedicated directory distinct from the symbol directories.</div>
-</li>
-<li class="level1"><div class="li"> <em>Make sure that the SPICE files pin assignments correctly correspond to the pins as defined in the componentâ??s symbol!</em> This is hard to over-emphasize. The order in which pins are listed in a .subckt file do not necessarily correspond to the physical pin ordering of the part. As described above, pins are emitted from the netlister in the order given by the <strong><code>pinseq</code></strong> attribute.</div>
-</li>
-<li class="level1"><div class="li"> <em>Make sure that the last character in a SPICE model file is a carriage return.</em> If no carriage return exists, then the next component listed in the netlist may be placed on the same line as the last line of the SPICE model file.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Configuring your SPICE files" [13604-14750] -->
-<h2><a name="creating_your_circuitschematic_capture" id="creating_your_circuitschematic_capture">Creating your circuit: schematic capture</a></h2>
-<div class="level2">
-
-<p>
-Schematic capture is the process by which one uses a special-purpose drawing program to draw a schematic diagram of the circuit under design. In the gEDA environment, the schematic capture program is called <strong>gschem</strong>. I assume you already know how to use <strong>gschem</strong>. If not, consult the documentation available at the gEDA website: <a href="http://www.geda.seul.org/"; class="urlextern" title="http://www.geda.seul.org/"; rel="nofollow">http://www.geda.seul.org/</a>. For the purposes of creating SPICE netlists, you must use <strong>gschem</strong> to attach attributes to components, and possibly also incorporate other SPICE directives into your netlist. After you are done with schematic capture, you create the SPICE netlist by running gEDAâ??s netlister <strong>gnetlist</strong> on your design.
-</p>
-
-</div>
-<!-- SECTION "Creating your circuit: schematic capture" [14751-15474] -->
-<h3><a name="gschem_attributes_for_spice_netlisting" id="gschem_attributes_for_spice_netlisting">Gschem attributes for spice netlisting</a></h3>
-<div class="level3">
-
-<p>
-There are several ways that spice attributes may be associated with a component using <strong>gschem</strong>. The way you choose to do this depends upon many factors, including the type of component, and the size and format of the SPICE model.
-</p>
-
-</div>
-<!-- SECTION "Gschem attributes for spice netlisting" [15475-15756] -->
-<h3><a name="component_attributes_and_meanings" id="component_attributes_and_meanings">Component attributes and meanings</a></h3>
-<div class="level3">
-
-<p>
-The following attributes are meaningful for SPICE netlisting, and may be attached from within <strong>gschem</strong>:
-</p>
-<ul>
-<li class="level1"><div class="li"> <strong><code>refdes</code></strong>: The reference designator of the component. Valid values depend upon the component type and are given in <a href="#appendix_a" title="geda:csygas ↵" class="wikilink1">Appendix A</a> - Native components and their attributes.</div>
-</li>
-<li class="level1"><div class="li"> <strong><code>value</code></strong>: For passives, this is the component value. For actives, this is the type (model no.) of the component (e.g. 2N3904, uA741). When a model for an active is instantiated separately from the component itself, the <strong><code>value</code></strong> attribute holds the name of the spice model.</div>
-</li>
-<li class="level1"><div class="li"> <strong><code>model</code></strong>: This holds a one line spice model for the component.</div>
-</li>
-<li class="level1"><div class="li"> <strong><code>file</code></strong>: This holds the name of a file. Typically, this is a file holding e.g. a SPICE .MODEL, .SUBCKT, or other SPICE code.</div>
-</li>
-<li class="level1"><div class="li"> <strong><code>model-name</code></strong>: This holds the name of the spice model referred to in a .MODEL or .SUBCKT statement. <strong><code>model-name</code></strong> is mainly used to identify the spice model name in the symbol <strong><code>spice-model-1.sym</code></strong>. Active components should call out this name in the <strong><code>device</code></strong> attribute to associate the component with its particular spice model or subcircuit.</div>
-</li>
-<li class="level1"><div class="li"> <strong><code>type</code></strong>: This specifies the type of component and is used by spice when interpreting the model parameters. Valid values depend upon the device being modeled.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Component attributes and meanings" [15757-17116] -->
-<h3><a name="refdes_conventions" id="refdes_conventions">refdes conventions</a></h3>
-<div class="level3">
-
-<p>
-As a prerequisite to handling SPICE-related attributes, the SPICE netlister requires that all components must have a <strong><code>refdes</code></strong> attached to them. The <strong><code>refdes</code></strong> may be attached either by hand (which is laborious), or using the program <strong>refdes_renum</strong> included in the gEDA distribution.
-</p>
-
-<p>
-Note that the first letter of the <strong><code>refdes</code></strong> must correspond to the appropriate letter for spice simulation. The <strong><code>refdes</code></strong> convention is given in the appendix.
-</p>
-
-</div>
-<!-- SECTION "refdes conventions" [17117-17611] -->
-<h3><a name="passives" id="passives">Passives</a></h3>
-<div class="level3">
-
-</div>
-
-<h4><a name="basic_passives" id="basic_passives">Basic passives</a></h4>
-<div class="level4">
-
-<p>
-The most basic components which one encounters in SPICE are passive components like resistors and capacitors which have numeric values, but no other modeling attributes. In this case the following attributes must be filled in:
-</p>
-<ul>
-<li class="level1"><div class="li"> <strong><code>refdes</code></strong>: The correct <strong><code>refdes</code></strong> for the component.</div>
-</li>
-<li class="level1"><div class="li"> <strong><code>value</code></strong>: For passives, this is the numeric value of the component (e.g. 100pF). For actives, this attribute may be filled in, but if no model attribute is available elsewhere in the schematic, the value is not used (in SPICE netlisting, anyway).</div>
-</li>
-<li class="level1"><div class="li"> If only a <strong><code>refdes</code></strong> and <strong><code>value</code></strong> attribute are encountered, the netlister will write a single line into the output file.</div>
-</li>
-</ul>
-
-</div>
-
-<h4><a name="example_resistor" id="example_resistor">Example resistor:</a></h4>
-<div class="level4">
-<ul>
-<li class="level1"><div class="li"> <strong><code>refdes</code></strong> = R2</div>
-</li>
-<li class="level1"><div class="li"> <strong><code>value</code></strong> = 220</div>
-</li>
-</ul>
-
-<p>
- SPICE line generated: <strong><code>R2 0 4 220</code></strong>
-</p>
-
-<p>
-(note that â??0â?? and â??4â?? correspond to the net nodes connected to the component, and are generated automatically by <strong>gnetlist</strong>.)
-</p>
-
-</div>
-
-<h4><a name="example_capacitor" id="example_capacitor">Example capacitor:</a></h4>
-<div class="level4">
-<ul>
-<li class="level1"><div class="li"> <strong><code>refdes</code></strong> = C22</div>
-</li>
-<li class="level1"><div class="li"> <strong><code>value</code></strong> = 1UF</div>
-</li>
-</ul>
-
-<p>
- SPICE line generated: <strong><code>C22 4 23 1UF</code></strong>
-</p>
-
-</div>
-<!-- SECTION "Passives" [17612-18707] -->
-<h3><a name="passives_with_additional_attributes" id="passives_with_additional_attributes">Passives with additional attributes</a></h3>
-<div class="level3">
-
-<p>
-Oftentimes, passive components have additional attributes attached to them for spice simulation. Examples of such attributes are temperature coefficients (for resistors) and initial conditions (for reactive components). These additional components may be incorporated into the SPICE file by simply attaching them to the componentâ??s <strong><code>model</code></strong> attribute. Specifically, the required attributes are:
-</p>
-<ul>
-<li class="level1"><div class="li"> <strong><code>refdes</code></strong>: Correct component <strong><code>refdes</code></strong>.</div>
-</li>
-<li class="level1"><div class="li"> <strong><code>value</code></strong>: Numerical component <strong><code>value</code></strong>, as always.</div>
-</li>
-<li class="level1"><div class="li"> <strong><code>model</code></strong>: One line string holding additional parameters, formatted as a valid SPICE string.</div>
-</li>
-</ul>
-
-<p>
- This string is placed after the component value in the line generated by gnetlist. Therefore, it is important to format the string placed in the <strong><code>model</code></strong> line to be valid SPICE code. Otherwise, you will risk causing the SPICE simulator to barf.
-</p>
-
-</div>
-
-<h4><a name="example_resistor1" id="example_resistor1">Example resistor:</a></h4>
-<div class="level4">
-<ul>
-<li class="level1"><div class="li"> <strong><code>refdes</code></strong> = R5</div>
-</li>
-<li class="level1"><div class="li"> <strong><code>value</code></strong> = 1MEG</div>
-</li>
-<li class="level1"><div class="li"> <strong><code>model</code></strong> = TC=0.001,0.015</div>
-</li>
-</ul>
-
-<p>
- SPICE line generated: <strong><code>R2 0 4 220 TC=0.001,0.015</code></strong>
-</p>
-
-</div>
-<!-- SECTION "Passives with additional attributes" [18708-19793] -->
-<h3><a name="passives_for_semiconductor_design" id="passives_for_semiconductor_design">Passives for semiconductor design</a></h3>
-<div class="level3">
-
-<p>
-The values for resistors and capacitors are often given as dimensions in an ASIC design. SPICE takes from the technology library the typical value per square and calculates the actual value in Ohm or Farad by itself. Therefor the following attributes are required:
-</p>
-<ul>
-<li class="level1"><div class="li"> <strong><code>refdes</code></strong>: The correct refdes for the component.</div>
-</li>
-<li class="level1"><div class="li"> <strong><code>model-name</code></strong>: corresponds to the model in the technology library.</div>
-</li>
-<li class="level1"><div class="li"> <strong><code>w</code></strong>, <strong><code>l</code></strong>: dimensions of the device.</div>
-</li>
-</ul>
-
-<p>
- The technology library must be included with an <strong><code>.include</code></strong> line in the SPICE input file.
-</p>
-
-</div>
-
-<h4><a name="example_semiconductor_resistor" id="example_semiconductor_resistor">Example semiconductor resistor:</a></h4>
-<div class="level4">
-<ul>
-<li class="level1"><div class="li"> <strong><code>refdes</code></strong> = R6</div>
-</li>
-<li class="level1"><div class="li"> <strong><code>model-name</code></strong> = rpoly</div>
-</li>
-<li class="level1"><div class="li"> <strong><code>w</code></strong> = 3u</div>
-</li>
-<li class="level1"><div class="li"> <strong><code>l</code></strong> = 100u</div>
-</li>
-</ul>
-
-<p>
- SPICE line generated: <strong><code>R6 0 5 rpoly w=3u l=100u</code></strong>
-</p>
-
-</div>
-
-<h4><a name="example_semiconductor_resistor_model" id="example_semiconductor_resistor_model">Example semiconductor resistor model:</a></h4>
-<div class="level4">
-<ul>
-<li class="level1"><div class="li"> model rpoly R rsh=300</div>
-</li>
-</ul>
-
-<p>
- This should be part of the technology library from your ASIC vendor.
-</p>
-
-</div>
-<!-- SECTION "Passives for semiconductor design" [19794-20720] -->
-<h3><a name="transistors_and_diodes" id="transistors_and_diodes">Transistors and diodes</a></h3>
-<div class="level3">
-
-<p>
-Transistors and diodes are generally accompanied by a device-specific model. Each model attempts to capture the detailed nonlinear dynamics of its particular device; otherwise, SPICE simulation is pointless. The SPICE model may be either a short, one-line string of parameters, or a multi-line set of SPICE parameters. A typical one-line parameter string is a short list of parameters describing a small-signal diode. Typical multi-line models come from component vendors, who often provide models for their components in a text file. Since there are two broad formats of SPICE information, there are two approaches to incorporating these parameters into the schematic:
-</p>
-
-</div>
-
-<h4><a name="one_line_string_of_spice_parameters" id="one_line_string_of_spice_parameters">One line string of SPICE parameters</a></h4>
-<div class="level4">
-
-<p>
-To incorporate a one line string of SPICE parameters into the netlist, the following attributes must be attached to the component:
-</p>
-<ul>
-<li class="level1"><div class="li"> <strong><code>refdes</code></strong>: Correct component <strong><code>refdes</code></strong>.</div>
-</li>
-<li class="level1"><div class="li"> <strong><code>value</code></strong>: The model number or part number of the component.</div>
-</li>
-<li class="level1"><div class="li"> <strong><code>model-name</code></strong>: The name you wish to give the SPICE model. This is usually the model number or part number of the component. If you have already attached a <strong><code>value</code></strong> attribute to the component, this parameter is optional.</div>
-</li>
-<li class="level1"><div class="li"> <strong><code>model</code></strong>: One line string holding additional parameters. Do not place the model parameters in parentheses – <strong>gnetlist</strong> will do this for you.</div>
-</li>
-</ul>
-
-</div>
-
-<h4><a name="example_diode" id="example_diode">Example diode:</a></h4>
-<div class="level4">
-<ul>
-<li class="level1"><div class="li"> <strong><code>refdes</code></strong> = D5</div>
-</li>
-<li class="level1"><div class="li"> <strong><code>model-name</code></strong> = 1N1004</div>
-</li>
-<li class="level1"><div class="li"> <strong><code>model</code></strong> = IS=0.5UA RS=6 BV=5.20</div>
-</li>
-</ul>
-
-<p>
- SPICE lines generated: <strong><code>D5 2 6 1N1004 MODEL 1N1004 D (IS=0.5UA RS=6 BV=5.20)</code></strong>
-</p>
-
-</div>
-
-<h4><a name="spice_model_file" id="spice_model_file">SPICE model file</a></h4>
-<div class="level4">
-
-<p>
-To incorporate a file-full of SPICE parameters into the netlist, the following attributes must be attached to the component:
-</p>
-<ul>
-<li class="level1"><div class="li"> <strong><code>refdes</code></strong>: Correct component <strong><code>refdes</code></strong>.</div>
-</li>
-<li class="level1"><div class="li"> <strong><code>value</code></strong>: The model number or part number of the component.</div>
-</li>
-<li class="level1"><div class="li"> <strong><code>model-name</code></strong>: the name you wish to give the SPICE model. This is usually the model number or part number of the component. If you have already attached a <strong><code>value</code></strong> attribute to the component, this parameter is optional.</div>
-</li>
-<li class="level1"><div class="li"> <strong><code>file</code></strong>: The file name of the SPICE model which you wish to incorporate into the netlist. This file name may specify either a relative or an absolute path, but it is probably better to use an absolute path to avoid problems if you ever move your schematic directory.</div>
-</li>
-</ul>
-
-<p>
- Note that you need to make sure that the model name held in your SPICE model file is the same as the <strong><code>value</code></strong> or <strong><code>model-name</code></strong> attributes you attached to the component. It is also a good idea to verify that the pin assignments in the model file correspond to the pin assignments made by the component symbol.
-</p>
-
-</div>
-<!-- SECTION "Transistors and diodes" [20721-23421] -->
-<h3><a name="actives_--_integrated_circuits" id="actives_--_integrated_circuits">Actives -- integrated circuits</a></h3>
-<div class="level3">
-
-<p>
-Integrated circuits are incorporated into the netlist similarly to transistors and diodes. As such, you may incorporate the spice information either as a one-line parameter string, or as a model file.
-</p>
-
-</div>
-
-<h4><a name="one_line_string_of_spice_parameters1" id="one_line_string_of_spice_parameters1">One line string of SPICE parameters</a></h4>
-<div class="level4">
-
-<p>
-To incorporate a one line string of SPICE parameters into the netlist, the following attributes must be attached to the component:
-</p>
-<ul>
-<li class="level1"><div class="li"> <strong><code>refdes</code></strong>: Correct component <strong><code>refdes</code></strong>.</div>
-</li>
-<li class="level1"><div class="li"> <strong><code>value</code></strong>: The model number or part number of the component.</div>
-</li>
-<li class="level1"><div class="li"> <strong><code>model-name</code></strong>: the name you wish to give the SPICE model. This is usually the model number or part number of the component. If you have already attached a <strong><code>value</code></strong> attribute to the component, this parameter is optional.</div>
-</li>
-<li class="level1"><div class="li"> <strong><code>model</code></strong>: One line string holding additional parameters. Do not place the model parameters in parentheses – <strong>gnetlist</strong> will do this for you.</div>
-</li>
-</ul>
-
-</div>
-
-<h4><a name="spice_.model_or_.subckt_file" id="spice_.model_or_.subckt_file">SPICE .MODEL or .SUBCKT file</a></h4>
-<div class="level4">
-
-<p>
-To incorporate a file-full of SPICE parameters into the netlist, the following attributes must be attached to the component:
-</p>
-<ul>
-<li class="level1"><div class="li"> <strong><code>refdes</code></strong>: Correct component <strong><code>refdes</code></strong>. <em>Note that if the file holds a .MODEL, the</em> <strong><code>refdes</code></strong> <em>should start with U; if the file holds a .SUBCKT, the refdes should start with X.</em> The netlister checks for the file type and tries to â??do the right thingâ??, but problems can arise if you donâ??t follow this rule.</div>
-</li>
-<li class="level1"><div class="li"> <strong><code>value</code></strong>: The model number or part number of the component.</div>
-</li>
-<li class="level1"><div class="li"> <strong><code>model-name</code></strong>: The name you wish to give the SPICE model. This is usually the model number or part number of the component. If you have already attached a <strong><code>value</code></strong> attribute to the component, this parameter is optional.</div>
-</li>
-<li class="level1"><div class="li"> <strong><code>file</code></strong>: The name of the file holding the SPICE .MODEL or .SUBCKT which you wish to incorporate into the netlist. This file name may specify either a relative or an absolute path, but it is probably better to use an absolute path to avoid problems if you ever move your schematic directory.</div>
-</li>
-</ul>
-
-<p>
- Note that you need to make sure that the model name held in your SPICE model file is the same as the <strong><code>value</code></strong> or <strong><code>model-name</code></strong> attributes you attached to the component. It is also a good idea to verify that the pin assignments in the model file correspond to the pin assignments made by the component symbol.
-</p>
-
-</div>
-<!-- SECTION "Actives -- integrated circuits" [23422-25765] -->
-<h3><a name="independent_sources" id="independent_sources">Independent sources</a></h3>
-<div class="level3">
-
-<p>
-There are two independent sources: voltage sources and current sources. For incorporation into a SPICE netlist, they both work the same way. To incorporate an independent source into your SPICE netlist, do the following:
-</p>
-<ol>
-<li class="level1"><div class="li"> Place the independent source on your schematic. (Do <strong><em>Add</em></strong> → <strong><em>Component</em></strong> → <strong><em>spice</em></strong> → <strong><independent source name>.sym</strong>)</div>
-</li>
-<li class="level1"><div class="li"> Double click on the block and add/edit the following attributes:</div>
-<ul>
-<li class="level2"><div class="li"> <strong><code>refdes</code></strong>: V? or I?</div>
-</li>
-<li class="level2"><div class="li"> <strong><code>value</code></strong>: A one line string in SPICE format describing the source.</div>
-</li>
-</ul>
-</li>
-</ol>
-
-</div>
-<!-- SECTION "Independent sources" [25766-26339] -->
-<h3><a name="dependent_sources" id="dependent_sources">Dependent sources</a></h3>
-<div class="level3">
-
-<p>
-There are four dependent sources:
-</p>
-
-<p>
-This section remains TBD.
-</p>
-
-</div>
-<!-- SECTION "Dependent sources" [26340-26429] -->
-<h3><a name="spice_components" id="spice_components">SPICE components</a></h3>
-<div class="level3">
-
-</div>
-
-<h4><a name="spice_model_block" id="spice_model_block">Spice model block</a></h4>
-<div class="level4">
-
-<p>
-In certain situations, you may wish to embed a spice model block directly into your schematic. This is done when you have several devices with a â??valueâ?? attribute calling out for a spice model. Depending upon whether the spice block is one line or multi-line, you may embed the code in one of two ways:
-</p>
-
-</div>
-
-<h4><a name="one_line_spice_model" id="one_line_spice_model">One line SPICE model:</a></h4>
-<div class="level4">
-<ol>
-<li class="level1"><div class="li"> Place a spice model block on your schematic. (Do <strong><em>Add</em></strong> → <strong><em>Component</em></strong> → <strong><em>spice</em></strong> → <strong>spice-model-1.sym</strong>)</div>
-</li>
-<li class="level1"><div class="li"> Double click on the block and add/edit the following attributes:</div>
-<ul>
-<li class="level2"><div class="li"> <strong><code>refdes</code></strong>: A?</div>
-</li>
-<li class="level2"><div class="li"> <strong><code>model</code></strong>: model name (i.e. the model name used in the components being modeled)</div>
-</li>
-<li class="level2"><div class="li"> <strong><code>type</code></strong>: One of the valid spice component types defined in the spice <acronym title="specification">spec</acronym>.</div>
-</li>
-<li class="level2"><div class="li"> <strong><code>value</code></strong>: The corresponding one-line spice model</div>
-</li>
-</ul>
-</li>
-</ol>
-
-</div>
-
-<h4><a name="multi-line_spice_model" id="multi-line_spice_model">Multi-line SPICE model:</a></h4>
-<div class="level4">
-<ol>
-<li class="level1"><div class="li"> Place a spice model block on your schematic.(Do <strong><em>Add</em></strong> → <strong><em>Component</em></strong> → <strong><em>spice</em></strong> → <strong>spice-model-1.sym</strong>)</div>
-</li>
-<li class="level1"><div class="li"> Double click on the block and add/edit the following attributes:</div>
-<ul>
-<li class="level2"><div class="li"> <strong><code>refdes</code></strong>: A?</div>
-</li>
-<li class="level2"><div class="li"> <strong><code>model</code></strong>: model name</div>
-</li>
-<li class="level2"><div class="li"> <strong><code>file</code></strong>: Name of file holding SPICE model code (i.e. .MODEL or .SUBCKT).</div>
-</li>
-</ul>
-</li>
-</ol>
-
-</div>
-
-<h4><a name="include_block" id="include_block">Include block</a></h4>
-<div class="level4">
-
-<p>
-The include block places a .INCLUDE directive into your netlist.
-</p>
-<ol>
-<li class="level1"><div class="li"> Place a spice model block on your schematic. (Do <strong><em>Add</em></strong> → <strong><em>Component</em></strong> → <strong><em>spice</em></strong> → <strong>spice-include-1.sym</strong>)</div>
-</li>
-<li class="level1"><div class="li"> Double click on the block and add/edit the following attributes:</div>
-<ul>
-<li class="level2"><div class="li"> <strong><code>refdes</code></strong>: A?</div>
-</li>
-<li class="level2"><div class="li"> <strong><code>file</code></strong>: Name of file to include.</div>
-</li>
-</ul>
-</li>
-</ol>
-
-</div>
-
-<h4><a name="spice_directive_block" id="spice_directive_block">SPICE directive block</a></h4>
-<div class="level4">
-
-<p>
-Placing a SPICE directive block into your schematic creates an arbitrary block of SPICE code in the netlist. The directive may be either statements held in a file, or a one-line string held in the <strong><code>model</code></strong> attribute. The netlister will simply dump the contents of the string or the file into your netlist verbatim. Examples of situations where this is useful include:
-</p>
-<ul>
-<li class="level1"><div class="li"> .TEMP statement</div>
-</li>
-<li class="level1"><div class="li"> .IC statement</div>
-</li>
-<li class="level1"><div class="li"> Other SPICE statements for which <strong>gschem</strong> has no symbol.</div>
-</li>
-</ul>
-
-<p>
- To place a SPICE directive on your schematic, do:
-</p>
-<ol>
-<li class="level1"><div class="li"> Place a SPICE directive block on your schematic. (Do <strong><em>Add</em></strong> → <strong><em>Component</em></strong> → <strong><em>spice</em></strong> → <strong>spice-directive-1.sym</strong>)</div>
-</li>
-<li class="level1"><div class="li"> Double click on the block and add/edit the following attributes:</div>
-<ul>
-<li class="level2"><div class="li"> <strong><code>refdes</code></strong>: A?</div>
-</li>
-<li class="level2"><div class="li"> <strong><code>file</code></strong>: Name of file to include.</div>
-</li>
-</ul>
-</li>
-</ol>
-
-</div>
-<!-- SECTION "SPICE components" [26430-28839] -->
-<h3><a name="handling_hierarchical_models" id="handling_hierarchical_models">Handling hierarchical models</a></h3>
-<div class="level3">
-
-<p>
-In SPICE modeling, there are often situations where you wish to create a schematic representation of some particular component as a .SUBCKT, and then embed that componentâ??s model in a higher level schematic. A common example might be as follows: You are doing a microwave simulation, and want to use a capacitor model which includes parasitic inductances and resistances, as well as the capacitance. Capacitor manufacturers often supply a printed schematic showing a circuit topology incorporating parasitics, and specify values for the parasitics. You would like to draw the capacitor model using gschem, netlist it to create a .SUBCKT, and then use the .SUBCKT to model capacitors in a higher lever schematic.
-</p>
-
-<p>
-Since this kind of task is very common in SPICE simulation, <strong>gnet-spice-sdb</strong> now supports it (starting with rev 20030331). To create a lower level .SUBCKT and use it in a higher level schematic, do the following:
-</p>
-<ol>
-<li class="level1"><div class="li"> Draw the schematic of the lower level component (e.g. the capacitor + parasitics) using <strong>gschem</strong>.</div>
-</li>
-<li class="level1"><div class="li"> On the lower level schematic, place a <strong><code>spice-subcircuit-LL</code></strong> block (<strong>spice-subcircuit-LL-1.sym</strong>). This alerts the netlister that the schematic is a Lower Level .SUBCKT. Attach the following attributes to the symbol:<br/>
- <br/>
- * <strong><code>model-name</code></strong> = cap_with_parasitics<br/>
- <br/>
- (Of course, â??cap_with_parasiticsâ?? is the example we use here. Use your own model name in your schematic.) Upon netlisting, this schematic symbol will cause the netlist to insert ".SUBCKT cap_with_parasiticsâ?? into the first line of the netlist file.</div>
-</li>
-<li class="level1"><div class="li"> On the lower level schematic, attach a <strong><code>spice-subcircuit-IO</code></strong> symbol (<strong>spice-subcircuit-IO-1.sym</strong>) to each IO net (i.e. connection to the upper level). Number the refdeses of the IO symbols in the same order as you would like the IO nets to be listed in the .SUBCKT line in the output file. (i.e. P1 = first, P2 = second, etc.)</div>
-</li>
-<li class="level1"><div class="li"> When you are done with the lower level schematic, netlist it in the usual way. For example, if your schematic is called <strong><code>cap_with_parasitics.sch</code></strong>, netlist it by saying: <br/>
- <br/>
- <strong><code>gnetlist -g spice-sdb -o cap_with_parasitics.cir cap_with_parasitics.sch</code></strong><br/>
- <br/>
- This will dump the SPICE netlist into the file called â??<strong>cap_with_parasitics.cir</strong>â??. Visually inspect the .cir file to make sure that netlisting worked correctly.</div>
-</li>
-<li class="level1"><div class="li"> Next, create a symbol for the upper level schematic which will point to the .SUBCKT. Note that the symbol must have a starting with the letter â??Xâ??. To ensure that this happens, do the following:</div>
-<ul>
-<li class="level2"><div class="li"> Use <strong>gschem</strong> to draw the symbol. I usually draw a box around a model symbol to distinguish it from a normal component. Make any other annotations desired.</div>
-</li>
-<li class="level2"><div class="li"> In the symbol, make sure that the pins are ordered identically to the order in which you have placed the pins in the .SUBCKT. This is done by editing the symbol with a text editor and setting the <strong><code>pinseq</code></strong> attribute. The netlister will output the pins in the order determined by the <strong><code>pinseq</code></strong> attribute.</div>
-</li>
-<li class="level2"><div class="li"> Using a text editor, give the symbol a <strong><code>device</code></strong> attribute like â??capacitor-modelâ??. Do <strong>not</strong> assign the symbol one of the native device types listed in the appendix! The goal is to create a symbol whose <strong><code>refdes</code></strong> starts with â??Xâ??, and if the <strong><code>device</code></strong> is a recognized type, this will not happen.</div>
-</li>
-<li class="level2"><div class="li"> Using a text editor, give the symbol the <strong><code>refdefs</code></strong> attribute â??X?"</div>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"> Create the upper level schematic. Place your newly created symbol on the schematic as many times as required and wire up the schematic in the usual way.</div>
-</li>
-<li class="level1"><div class="li"> To point your symbol to the lower level .SUBCKT, double click on the symbol and set the following attributes:<br/>
- <br/>
- * <strong><code>file</code></strong> = cap_with_parasitics.cir<br/>
- * <strong><code>model-name</code></strong> = cap_with_parasitics<br/>
- <br/>
- as well as any other attributes required (e.g. <strong><code>refdes</code></strong>).</div>
-</li>
-<li class="level1"><div class="li"> Now netlist your upper level schematic the usual way. The contents of each .SUBCKT file is dumped into the main netlist. Inspect your netlist visually using a text editor to ensure that it is correct. It is a good idea to pay particular attention to the following:</div>
-<ul>
-<li class="level2"><div class="li"> Verify that the ordering of the nets connecting the upper level netlist to the lower level .SUBCKT is correct.</div>
-</li>
-<li class="level2"><div class="li"> Make sure that the upper level model-name and the lower level model name (on the .SUBCKT declaration line) are the same.</div>
-</li>
-</ul>
-</li>
-</ol>
-
-<p>
- Once the netlist is created, you may simulate your design using any SPICE simulator desired. Some simulators running on Linux are covered below.
-</p>
-
-</div>
-<!-- SECTION "Handling hierarchical models" [28840-33380] -->
-<h2><a name="spice_netlist_generation" id="spice_netlist_generation">SPICE netlist generation</a></h2>
-<div class="level2">
-
-</div>
-<!-- SECTION "SPICE netlist generation" [33381-33417] -->
-<h3><a name="using_gnetlist" id="using_gnetlist">Using gnetlist</a></h3>
-<div class="level3">
-
-<p>
-Once the schematic is captured, a SPICE netlist can be generated running gEDAâ??s command-line program <strong>gnetlist</strong> on the schematic files. <strong>gnetlist</strong> is architected in two sections: a front-end processor written in C which reads in the .sch file and creates from it an internal, generic representation of your design, and a back-end netlister written in SCHEME. Using this architecture, <strong>gnetlist</strong> is highly customizable; different SCHEME backends are used to write out different netlist formats. The beauty of this scheme (pun intended) is that gEDA users can easily write their own netlisters to suit their own applications. The back-end Scheme file which implements advanced SPICE netlisting is called <strong><code>gnet-spice-sdb.scm</code></strong>, and it lives in the <strong><code>${PREFIX}/geda/share/gEDA/scheme</code></strong> directory.
-</p>
-
-<p>
-<strong>gnetlist</strong> with <strong>spice-sdb</strong> is invoked from the command line in the following way: <strong><code>gnetlist [OPTIONS] -g spice-sdb filename1 … filenameN</code></strong>. The following command-line options are available with spice-sdb:
-</p>
-<pre class="code">-i Interactive scheme mode
--I Put .INCLUDE <filename> in output file instead of model file's contents
--q Quiet mode
--l filename Load scheme file before loading backend
--m filename Load scheme file after loading backend, but still before executing procedure
--g proc Scheme procedure to execute (i.e. spice-sdb)
--o filename Output netlist filename
--c string Execute string as a scheme script
--v Verbose mode on
--s Sort output netlist (for Gnucap)</pre>
-
-</div>
-<!-- SECTION "Using gnetlist" [33418-34978] -->
-<h3><a name="creating_the_netlist_using_gnetlist_and_spice-sdb" id="creating_the_netlist_using_gnetlist_and_spice-sdb">Creating the netlist using gnetlist and spice-sdb</a></h3>
-<div class="level3">
-
-<p>
-Creating a netlist from a schematic is easy. To generate a SPICE netlist, just do the following:
-</p>
-<ul>
-<li class="level1"><div class="li"> Save your schematic to <<strong><code>filename.sch</code></strong>></div>
-</li>
-<li class="level1"><div class="li"> Create the SPICE netlist by doing â??<strong><code>gnetlist -g spice-sdb <filename.sch></code></strong>â??. The output is a netlist held in the file <strong><code>output.net</code></strong>. Alternatively, if you wish to give your output file a different name, set the output name using the <strong>-o</strong> switch. For example:<br/>
- <br/>
- <strong><code>gnetlist -g spice-sdb -o amplifier.cir amplifier.sch</code></strong><br/>
- <br/>
- takes the design schematic called â??<strong><code>amplifier.sch</code></strong>â?? and outputs a SPICE netlist named â??<strong><code>amplifier.cir</code></strong>â??.</div>
-</li>
-<li class="level1"><div class="li"> Inspect your SPICE netlist using a text editor. Verify that there are no missing attributes or other netlist problems.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Creating the netlist using gnetlist and spice-sdb" [34979-35772] -->
-<h3><a name="common_netlisting_problems" id="common_netlisting_problems">Common netlisting problems</a></h3>
-<div class="level3">
-
-<p>
-The following list attempts to catalog common problems with the netlist and the associated fixes:
-</p>
-<ul>
-<li class="level1"><div class="li"> ERROR_INVALID_<acronym title="Personal Identification Number">PIN</acronym>:<br/>
- This can happen if the symbolâ??s <strong><code>pinseq</code></strong> attributes donâ??t start at 1, or have gaps in the numbering. This must be fixed by editing the symbol itself in a text editor.</div>
-</li>
-<li class="level1"><div class="li"> ERROR: In procedure caddr:<br/>
- This error is quite common. It usually occurs when you forget to add a mandatory attribute. To rectify the problem, try running gnetlist in verbose mode (<strong><code>gnetlist -v -g spice-sdb <filename.sch></code></strong>). The netlister will stop processing and bomb out at the part with the missing attribute. Having therefore identified the offending part, you can re-open the schematic in gnetlist and fix the attributes.</div>
-</li>
-</ul>
-
-<p>
- Finally, remember that it is important to manually inspect your SPICE netlist prior to using it in simulation. Please keep in mind that the netlister is still â??betaâ?? quality, and some problems may still exist in netlist generation.
-</p>
-
-</div>
-<!-- SECTION "Common netlisting problems" [35773-36778] -->
-<h2><a name="spice_simulation" id="spice_simulation">SPICE simulation</a></h2>
-<div class="level2">
-
-<p>
-There are several options for doing SPICE simulations under GNU/Linux; I will highlight three:
-</p>
-<ul>
-<li class="level1"><div class="li"> <strong>LTSpice</strong>, which is a freeware SPICE simulator originally released by Linear Technologies as a component selection/design tool running under Windows. Because its SPICE engine is very fast and powerful, it has become a popular SPICE simulator amongst hobbyists and design engineers who prefer to use free tools. Originally written for Windows, LTSpice has been tweaked to run under GNU/Linux using wine; I recommend using it if you need a robust, professional-quality SPICE simulator.</div>
-</li>
-<li class="level1"><div class="li"> <strong>Ngspice</strong>, which is the â??officialâ?? SPICE simulator of the gEDA suite. Ngspice is a revival of the SPICE 3 code for Linux. It provides a simulation engine, a command-line driven front-end, and the capability to plot simulation results graphically under the X Windows System. Ngspice is Linux-native and open-source. It is the SPICE of choice for those who want to do SPICE simulations easily on Linux, or want to hack and improve SPICEâ??s internals.</div>
-</li>
-<li class="level1"><div class="li"> <strong>Tclspice</strong>, is a fork off the ngspice development path. Tclspice is a superset of ngspice which (in theory) exports the SPICE command set to a TCL <acronym title="Application Programming Interface">API</acronym>, allowing you to embed SPICE analyses into a TCL program. This is useful for automating a design optimization, amongst other things. Tclspice is the simulator to use if you are interested in advanced, scripted design.</div>
-</li>
-</ul>
-
-<p>
- There is also a <acronym title="GNU General Public License">GPL</acronym>â??ed simulator called <strong>gnucap</strong>, which is based upon (or is the descendant of) Alâ??s Circuit Simulator (<strong><code>ACS</code></strong>). I havenâ??t used it very much; information about gnucap is therefore TBD.
-</p>
-
-</div>
-<!-- SECTION "SPICE simulation" [36779-38431] -->
-<h3><a name="ltspice" id="ltspice">LTSpice</a></h3>
-<div class="level3">
-
-<p>
-LTSpice was written by Mike Englehardt and others at Linear Technologies, and is given away by LinearTech as a design aid for engineers wishing to simulate the performance of LinearTechâ??s switch mode power supply controllers. The package incorporates a schematic capture front end, fast and powerful SPICE engine, and the capability for plotting the results of many different types of SPICE analysis. Personally, I think the schematic capture front-end is hard to use and clunky; <strong>gschem</strong> knocks its socks off for ease of use and features. However, the SPICE engine and analysis stuff in LTSpice is simply great.
-</p>
-
-<p>
-LTSpice was originally developed to run under Windows, but Mike has tweaked it so that it runs fairly well on GNU/Linux under wine. (Only the help menu system is broken – the rest of the package runs well). Another good feature of LTSpice is that it is well supported – Mike reads the newsgroup <strong><code>sci.electronics.cad</code></strong> regularly and is generally happy to help people who experience problems with it. Therefore, despite its Windoze heritage, I recommend LTSpice as a powerful, professional-quality simulation and analysis back end for gEDA.
-</p>
-
-</div>
-
-<h4><a name="installation_and_configuration_of_ltspice" id="installation_and_configuration_of_ltspice">Installation and configuration of LTSpice</a></h4>
-<div class="level4">
-
-<p>
-To install and configure LTSpice, do the following:
-</p>
-<ol>
-<li class="level1"><div class="li"> Download and install wine. I have had success using Wine-20030219. Later versions probably also work.</div>
-</li>
-<li class="level1"><div class="li"> Download LTSpice. It is available under <a href="http://www.linear.com/software"; class="urlextern" title="http://www.linear.com/software"; rel="nofollow">http://www.linear.com/software</a> under the name SwitcherCAD-III.</div>
-</li>
-<li class="level1"><div class="li"> Run the LTSpice installer under wine.</div>
-</li>
-</ol>
-
-</div>
-
-<h4><a name="running_ltspice_with_geda_designs" id="running_ltspice_with_geda_designs">Running LTSpice with gEDA designs</a></h4>
-<div class="level4">
-
-<p>
-LTSpice can read a file holding a gEDA SPICE netlist. I have had success doing LTSpice simulations in the following way:
-</p>
-<ol>
-<li class="level1"><div class="li"> First of all, make sure that you are logged in as a normal user – Wine doesnâ??t like to run when invoked by root.</div>
-</li>
-<li class="level1"><div class="li"> Create a file in your project directory called â??Simulation.cmdâ??. In this file place your spice analysis commands (e.g. .OP, .AC, .DC, etc.)</div>
-</li>
-<li class="level1"><div class="li"> Place a SPICE include block into your schematic. For the file attribute, type in â??Simulation.cmdâ??.</div>
-</li>
-<li class="level1"><div class="li"> Netlist your design.</div>
-</li>
-<li class="level1"><div class="li"> Create a link from your netlist <strong><code>output.net</code></strong> and a netlist in the directory in which SwCADIII lives. Make the netlist suffix <strong><code>.cir</code></strong>. For example:<br/>
- <br/>
- ln -s ${DESIGN_HOME}/output.net ${WINE_HOME}/.wine/fake_windows/Program Files/LTC/SwCADIII/MyDesign.cir<br/>
- <br/>
-</div>
-</li>
-<li class="level1"><div class="li"> Run LTSpice: cd into the directory where SwCADIII lives and say â??<strong><code>wine scad3.exe</code></strong>â??</div>
-</li>
-<li class="level1"><div class="li"> From the SwCADIII <acronym title="Graphical User Interface">GUI</acronym>, do: <strong><em>File</em></strong> → <strong><em>Open</em></strong> → <strong><em>(files of type netlist [.cir])</em></strong>, and select your file.</div>
-</li>
-<li class="level1"><div class="li"> Run the simulator by clicking on the run button, or doing: <strong><em>Simulate</em></strong> → <strong><em>Run</em></strong>.</div>
-</li>
-<li class="level1"><div class="li"> Select the variables to graph, and then click OK. SwCADIII does the rest of the work.</div>
-</li>
-</ol>
-
-<p>
- Naturally, it is very important to play around with LTSpice to understand how to use it effectively, but the above description should suffice to get you started.
-</p>
-
-</div>
-<!-- SECTION "LTSpice" [38432-41371] -->
-<h3><a name="ngspice" id="ngspice">Ngspice</a></h3>
-<div class="level3">
-
-<p>
-Ngspice was started at the University of Rome â??La Sapienzaâ?? by Paolo Nenzi as an attempt to create a <acronym title="GNU General Public License">GPL</acronym>â??ed version of the standard Berkeley SPICE version 3 by re-writing the entire SPICE package. Plans were also laid to create better, more robust computational algorithms for the simulation engine. More information is available at the ngspice website: <a href="http://ngspice.sourceforge.net/"; class="urlextern" title="http://ngspice.sourceforge.net/"; rel="nofollow">http://ngspice.sourceforge.net/</a>. In light of his lofty plans, what Paolo did, however, was a little different: He took the SPICE 3 code which had been floating around the internet for many years, refactored it, and hacked the build system so that it would compile using the normal GNU make procedure. This was a major achievement for which Paolo deserves great praise. Unfortunately, from the look of the webpage, development on <strong>ngspice</strong> seems to have ceased at the end of 2001. Indeed, development did slow down considerably after 2001, but recently Paolo has been working on <strong>ngspice</strong> again. He released the latest version, <strong>ngspice-rework-15</strong>, in February 2004. This version is available only on the Sourceforge download page; Paolo hasnâ??t updated the rest of the projectâ??s website.
-</p>
-
-</div>
-
-<h4><a name="installation_and_configuration_of_ngspice" id="installation_and_configuration_of_ngspice">Installation and configuration of ngspice</a></h4>
-<div class="level4">
-
-<p>
-I generally find it best to download, configure, and compile the source of <strong>ngspice</strong> instead of trying to install a binary package. Thatâ??s the approach I outline here.
-</p>
-
-</div>
-
-<h4><a name="downloading_the_source_code" id="downloading_the_source_code">Downloading the source code</a></h4>
-<div class="level4">
-
-<p>
-Get the latest distribution from: <a href="http://sourceforge.net/projetcs/ngspice"; class="urlextern" title="http://sourceforge.net/projetcs/ngspice"; rel="nofollow">http://sourceforge.net/projetcs/ngspice</a>. Make sure that you get the latest version for best performance and the most features. As of May 2004, the latest release is <strong>ngspice-rework-15</strong>. Install the source in the place you typically put your sources. I like to keep my gEDA sources in a separate directory, for example <strong><code>/usr/local/geda/sources/ngspice</code></strong>. You might adopt a similar system.
-</p>
-
-</div>
-
-<h4><a name="extracting_the_source_code" id="extracting_the_source_code">Extracting the source code</a></h4>
-<div class="level4">
-
-<p>
-The source code you downloaded is distributed in a â??tarballâ??, a compressed archive. You have to extract archived files by doing:
-</p>
-<pre class="code">user@host:~$ cd <directory where you want to extract the source>
-user@host:~sources$ tar -xvzf </path/to/package.tar.gz>
-user@host:~sources$ cd <extracted dir></pre>
-
-<p>
-At this point you are in the top level directory of ngspice. Read the usual files, like <strong><code>README</code></strong>, and <strong><code>INSTALL</code></strong>, to learn about the simulator and the installation process. Reading <strong><code>NOTES</code></strong> file is also a good idea; it holds information valuable if you want to hack or debug features present in ngspice.
-</p>
-
-</div>
-
-<h4><a name="configuration_and_compilation_of_ngspice" id="configuration_and_compilation_of_ngspice">Configuration and compilation of ngspice.</a></h4>
-<div class="level4">
-
-<p>
-Ngspice uses the typical â??<strong><code>configure && make && make install</code></strong>â?? sequence used by other GNU software. There are numerous configure time options available for ngspice. A complete listing with attendant documentation is TBD; the best way to see them all is to look at <strong><code>configure.ac</code></strong> itself. Many of the configure time options pertain to debugging the simulator, or are to enable experimental analyses. For newbies, three configure time options are worth mentioning:
-</p>
-<ul>
-<li class="level1"><div class="li"> <strong><code>–enable-xspice</code></strong>: This flag compiles in support for XSpice extensions. These extensions allow you to define devices whose behavior is given by arbitrary â??code modelsâ??. Arguably, the most important code model is <strong><code>spice2poly</code></strong>, which is a model which translates SPICE2 style POLY constructs into an XSpice model usable by SPICE 3.</div>
-</li>
-<li class="level1"><div class="li"> <strong><code>–with-readline</code></strong>: This flag compiles GNU readline support into <strong>ngspice</strong>, which means that you can use emacs-style key commands, as well as the arrow keys to move around in the command line interface (CLI). Without this feature, the command line interface can be hostile, meaning that if you make a mistake in typing a long command, you have no choice but to type it all over again. Paolo discourages use of the readline feature because it mixes <acronym title="GNU General Public License">GPL</acronym> code (readline) with BSD code (<strong>ngspice</strong>), but he left the option open to other to decide for themselves how pure they wanted to be.</div>
-</li>
-<li class="level1"><div class="li"> <strong><code>–prefix</code></strong>: This flag point to the base directory where you want your binaries to be installed.</div>
-</li>
-</ul>
-
-<p>
- Before you run configure, you should check the options you want to include, a brief description is given in appendix TBD. Once ready type:
-</p>
-<pre class="code">user@host:~sources/<tld>$./configure --enable-xspice --with-readline --prefix=/usr/local/geda <other configure options></pre>
-
-<p>
-Of course, â??<strong><code>–prefix=</code></strong>â?? should point to the place where you put <strong>your</strong> gEDA stuff. After issuing the command, your simulator is configured and ready to be compiled. Compilation is straightforward:
-</p>
-<pre class="code">user@host:~sources/<tld>$ make && make install</pre>
-
-<p>
-As always, you will probably need to be root in order to install the packages in a public directory, in such case you should do:
-</p>
-<pre class="code">user@host:~sources/<tld>$ make
-user@host:~sources/<tld>$ su -c make install</pre>
-
-</div>
-
-<h4><a name="testing_the_installation" id="testing_the_installation">Testing the installation</a></h4>
-<div class="level4">
-
-<p>
-At this point, you should be able to use ngspice. You can test your installation by trying one of the test circuits held in the tests directory. I recommend running the TransImpedanceAmp test, since it tests the SPICE2 POLY functionality.
-</p>
-
-</div>
-
-<h4><a name="using_ngspice" id="using_ngspice">Using ngspice</a></h4>
-<div class="level4">
-
-<p>
-Running ngspice is very simple. Just issue the command:
-</p>
-<pre class="code">user@host:~$ ngspice filename.net</pre>
-
-<p>
-at the unix command prompt, and ngspice will load the SPICE netlist called <strong><code>filename.net</code></strong> into its workspace, and leave you at an ngspice command prompt. You can run the simulator by saying â??runâ??. Your results will be stored in SPICE vectors for later printing or plotting. The command set available to you is documented at: <a href="http://newton.ex.ac.uk/teaching/CDHW/Electronics2/userguide/sec5.html#5"; class="urlextern" title="http://newton.ex.ac.uk/teaching/CDHW/Electronics2/userguide/sec5.html#5"; rel="nofollow">http://newton.ex.ac.uk/teaching/CDHW/Electronics2/userguide/sec5.html#5</a>
-</p>
-
-<p>
-To make use of the SPICE2 POLY codemodel, you need to load it into <strong>ngspice</strong> <strong><em class="u">before</em></strong> you load your netlist. (If you load it after loading your netlist, POLYs in your netlist are not translated, and therefore wonâ??t be simulated correctly.) To load the codemodel, just say:
-</p>
-<pre class="code">codemodel /usr/local/geda/lib/spice/spice2poly.cm</pre>
-
-<p>
-(or wherever you put your codemodels) at the ngspice prompt. Note that you must provide the <strong>absolute path</strong> to the location of the codemodel; ngspice isnâ??t smart enough to look for it in any default locations. (Also note that you should specify the location where <strong><code>spice2poly.cm</code></strong> lives on your machine; the path above is for mine).
-</p>
-
-<p>
-A better way to read in the <strong><code>spice2poly</code></strong> codemodel is to include it in the ngspice initialization file, <strong><code>spinit</code></strong>. The initialization file lives in the directory <strong><code>/usr/local/geda/share/ng-spice-rework/scripts</code></strong> (or where ever you placed your gEDA installation). Other ngspice customizations may also be placed into the <strong><code>spinit</code></strong> file.
-</p>
-
-</div>
-<!-- SECTION "Ngspice" [41372-48076] -->
-<h3><a name="tclspice" id="tclspice">Tclspice</a></h3>
-<div class="level3">
-
-<p>
-While the main branch of ngspice development hibernated in 2002, some friendly people at MultiGig Ltd. (<a href="http://www.multigig.com/"; class="urlextern" title="http://www.multigig.com/"; rel="nofollow">http://www.multigig.com/</a>) were busy developing a branch of ngspice which they called <strong>tclspice</strong>. Tclspice is a superset of ngspice in which much of the SPICE command set is exported as an <acronym title="Application Programming Interface">API</acronym> to TCL. The purpose of this is to facilitate scripting of SPICE analyses. This is a very powerful tool: With tclspice you can write a TCL script which runs a loop, tweaks component values, runs an analysis, and then evaluates the circuit performance with the tweaked components before looping again. Obviously, this ability can be used to perform automated, multi-dimensional circuit optimization. When complete, tclspice might possibly become a â??killer-appâ?? for open-source EDA.
-</p>
-
-</div>
-
-<h4><a name="downloading_installing_and_building_tclspice" id="downloading_installing_and_building_tclspice">Downloading, installing, and building tclspice</a></h4>
-<div class="level4">
-
-<p>
-Tclspiceâ??s project homepage is at: <a href="http://tclspice.sourceforge.net/"; class="urlextern" title="http://tclspice.sourceforge.net/"; rel="nofollow">http://tclspice.sourceforge.net/</a>. The tclspice source lives at <a href="http://sourceforge.net/projects/tclspice"; class="urlextern" title="http://sourceforge.net/projects/tclspice"; rel="nofollow">http://sourceforge.net/projects/tclspice</a>. Download and installation of tclspice follow the same steps as those detailed for ngspice above. Since tclspice is a superset of ngspice, you can install ngspice alone from the tclspice sources if desired. To build the entire package requires a couple of extra steps. Here, I present a series of steps which will build both ngspice (the stand-alone, CLI driven program) and the TCL <acronym title="Application Programming Interface">API</acronym> from the tclspice source.
-</p>
-
-<p>
-Before building tclspice, you need to have the following packages already installed:
-</p>
-<ul>
-<li class="level1"><div class="li"> TclX (tclx8.3.5 works for me.)</div>
-</li>
-<li class="level1"><div class="li"> tclreadline (tclreadline-2.1.0 works for me.)</div>
-</li>
-<li class="level1"><div class="li"> BLT for TCL (blt2.4z works for me.)</div>
-</li>
-<li class="level1"><div class="li"> TCL/Tk (8.4.3. works for me)</div>
-</li>
-</ul>
-
-<p>
- If you donâ??t have these packages already on your Linux box, you need to get and build them. Note that building TclX requires having the sources for TCL and Tk, so you will also need to get those sources if you donâ??t have them installed already. I am running successfully with TCL/Tk 8.4.3, although 8.3.X versions are also supposed to work. Also, if you want to run spice in the background you need to recompile TCL and Tk to enable thread support if they havenâ??t got it enabled already (redhat packages havenâ??t).
-</p>
-
-<p>
-Assuming you have downloaded and installed the additional packages mentioned above, the following steps will build both ngspice and the TCL <acronym title="Application Programming Interface">API</acronym> on your machine:
-</p>
-<pre class="code">user@host:~sources/<tld>$ ./configure --enable-xspice --with-readline --prefix=/usr/local/geda
-user@host:~sources/<tld>$ make && make install (this makes and installs regular old ngspice)
-user@host:~sources/<tld>$ ./configure --enable-xspice --prefix=/usr/local/geda --enable-tcl --enable-experimental --disable-shared
-user@host:~sources/<tld>$ make tcl && make install-tcl</pre>
-
-<p>
-As always, you will probably need to be root in order to install the packages in a public directory, in such case you should do:
-</p>
-<pre class="code">user@host:~sources/<tld>$ su -c make install
-user@host:~sources/<tld>$ su -c make install-tcl</pre>
-
-<p>
-to install your packages. Now you will be ready to write TCL scripts which incorporate SPICE commands. Information about using tclspice is given below. Finally, if you are interested in hacking tclspice (or even if you are not), itâ??s a good idea to read the <strong><code>NOTES</code></strong> file living in the top source directory for a couple of useful pointers.
-</p>
-
-</div>
-
-<h4><a name="use_of_tclspice" id="use_of_tclspice">Use of tclspice</a></h4>
-<div class="level4">
-
-<p>
-Tclspice is designed to export SPICE commands to TCL programs. To use tclspice, you just need to say â??<strong><code>package require spice</code></strong>â?? at the beginning of your TCL program. Thereafter, to invoke a SPICE command, you just call it in the spice namespace. For example, the following TCL program will read in a SPICE netlist, command a transient analysis, run the simulation, and then plot the voltage observed over time on net Vout:
-</p>
-<pre class="code">#! tclsh
-package require spice
-spice::codemodel /usr/local/src/tclspice-0.2.12/src/xspice/icm/spice2poly.cm
-spice::source netlistname.cir
-spice::tran 0.1ns 40ns
-spice::run
-spice::plot Vout
-puts "All done now!"</pre>
-
-<p>
-Note that since tclspice doesnâ??t read the ngspice initialization file <strong><code>spinit</code></strong>, you will need to put any initialization commands directly into the TCL program. For example, in the above example we read the spice2poly codemodel directly into the workspace. Many other commands are also available; the entire tclspice commandset is documented at: <a href="http://tclspice.sourceforge.net/docs/tclspice_com.html"; class="urlextern" title="http://tclspice.sourceforge.net/docs/tclspice_com.html"; rel="nofollow">http://tclspice.sourceforge.net/docs/tclspice_com.html</a>
-</p>
-
-</div>
-
-<h4><a name="tclspice_problems" id="tclspice_problems">Tclspice problems</a></h4>
-<div class="level4">
-
-<p>
-A major problem with tclspice (which was inherited from ngspice) is that it leaks memory. Therefore, the time over which you may run a simulation is limited. This means that if you want to do an optimization by looping through a circuit many, many times, you may run out of memory before your program has completed its optimization. This is a known issue with tclspice, and efforts are underway to plug the leaks.
-</p>
-
-<p>
-Meanwhile, there are some workarounds which can be used on moderate-sized designs to facilitate long optimization runs. One method I have employed is to have the optimizer write its current state into a file after every circuit analysis, and read its starting state from the same file. The optimizer also stores the current list of best components in another file, and reads this file at the start of every run. Then, I have a TCL program called <strong><code>TaskMgr.tcl</code></strong> which runs in a loop; at each iteration of the loop it forks a child process to run the optimizer. Meanwhile, the parent process waits for 5 minutes (a heuristically determined time), and then issues a â??KILLâ?? signal to the child before looping and starting the optimizer again. This way, the optimizer never runs long enough to consume all the memory in my machine. The <strong><code>TaskMgr.tcl</code></strong> program is shown here:
-</p>
-<pre class="code">#! tclsh
-package require Tclx
-while {1} {
- set PID [fork]
- if {$PID} {
- # Parent
- after 300000
- puts "About to kill child PID = $PID . . . ."
- kill $PID
- wait $PID
- } else {
- # Child
- source Optimize.tcl
- # If we ever get through this, we can print out the following:
- error "We are done now!!!!!!"
- }
-}</pre>
-
-<p>
-Note that <strong><code>TaskMgr.tcl</code></strong> needs the TclX package you already installed to run tclspice. Also, you may want to change the wait time to a different value depending upon the memory and speed of your machine. Finally, the parent has to wait on $PID because that causes the child processâ??s corpse to be taken off the Linux kernelâ??s task list when it dies. Otherwise, you will end up with a lot of zombie processes lurking around your machine as the optimizer runs – a long optimization could turn your system into â??the night of the living deadâ??!
-</p>
-
-<p>
-This method of waiting a specific amount of time for the child process is preferable if a single analysis run takes a relatively short time compared to the time required to eat all memory in the machine. If the analysis time is comparable to the time taken to eat all memory in the machine, a better approach is to have the parent keep track of the analysis state, kick off a single analysis run, and then have the run terminate after every iteration. Whether this is preferable depends upon the size and complexity of your design; you may want to experiment with your analysis to see just how long it takes and how much memory it consumes. I have found that a design comprised of six op amps (with corresponding vendor models) and 50 or so passives will run in under 10 seconds on a PIII 333MHz with 128MB RAM. Therefore, your design must be very big before a single analysis will eat a significant amount of RAM.
-</p>
-
-</div>
-<!-- SECTION "Tclspice" [48077-55608] -->
-<h1><a name="appendix_a" id="appendix_a">Appendix A</a></h1>
-<div class="level1">
-
-<p>
-<strong>Native components and their attributes</strong>
-</p>
-
-<p>
-Presented in table 1 are the devices and associated attributes used with spice-sdb. Bold faced attributes are required, normal typeface attributes are optional. Note that the <strong><code>device</code></strong> attribute is invisible, and is normally attached to the symbol when it is created. The other attributes are attached to the symbol during schematic capture using <strong>gschem</strong>.
-</p>
-
-<p>
-When dealing with simple actives (diodes, transistors) having SPICE models held in files, you only need to set the <strong><code>model-name</code></strong> and <strong><code>file</code></strong> attributes; you donâ??t need to set the <strong><code>model</code></strong> attribute. However, if your simple active has a one-line SPICE model which you wish to enter directly into the schematic, then set the <strong><code>model</code></strong> and <strong><code>model-name</code></strong> attribures; you donâ??t need to set the <strong><code>file</code></strong> attribute.
-</p>
-<table class="inline">
- <tr>
- <th>device</th><th>refdes</th><th>value</th><th>model</th><th>file</th><th>model-name</th><th>type</th><th>comment</th>
- </tr>
- <tr>
- <td>RESISTOR</td><td class="centeralign"> R? </td><td class="centeralign"> (4) </td><td class="centeralign"> (2) </td><td class="centeralign"> - </td><td class="centeralign"> Name of model </td><td class="centeralign"> - </td><td class="centeralign"> (11) </td>
- </tr>
- <tr>
- <td>CAPACITOR</td><td class="centeralign"> C? </td><td class="centeralign"> (4) </td><td class="centeralign"> (3) </td><td class="centeralign"> - </td><td class="centeralign"> Name of model </td><td class="centeralign"> - </td><td class="centeralign"> (11) </td>
- </tr>
- <tr>
- <td>POLARIZED_CAPACITOR</td><td class="centeralign"> C? </td><td class="centeralign"> (4) </td><td class="centeralign"> (3) </td><td class="centeralign"> - </td><td class="centeralign"> Name of model </td><td class="centeralign"> - </td><td class="centeralign"> (11) </td>
- </tr>
- <tr>
- <td>INDUCTOR</td><td class="centeralign"> L? </td><td class="centeralign"> (4) </td><td class="centeralign"> (3) </td><td class="centeralign"> - </td><td class="centeralign"> Name of model </td><td class="centeralign"> - </td><td class="centeralign"> (11) </td>
- </tr>
- <tr>
- <td>SPICE-ccvs</td><td class="centeralign"> H? </td><td class="centeralign"> (5) </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="rightalign"> </td>
- </tr>
- <tr>
- <td>SPICE-cccs</td><td class="centeralign"> F? </td><td class="centeralign"> (5) </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="rightalign"> </td>
- </tr>
- <tr>
- <td>SPICE-vscs</td><td class="centeralign"> E? </td><td class="centeralign"> (5) </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="rightalign"> </td>
- </tr>
- <tr>
- <td>SPICE-vccs</td><td class="centeralign"> G? </td><td class="centeralign"> (5) </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="rightalign"> </td>
- </tr>
- <tr>
- <td>SPICE-nullor</td><td class="centeralign"> E? </td><td class="centeralign"> (5) </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="rightalign"> </td>
- </tr>
- <tr>
- <td>DIODE</td><td class="centeralign"> D? </td><td class="centeralign"> Part number </td><td class="centeralign"> One line SPICE model </td><td class="centeralign"> Model file name </td><td class="centeralign"> Name of model </td><td class="centeralign"> - </td><td class="centeralign"> (12) </td>
- </tr>
- <tr>
- <td>PMOS_TRANSISTOR</td><td class="centeralign"> M? </td><td class="centeralign"> Part number </td><td class="centeralign"> One line SPICE model </td><td class="centeralign"> Model file name </td><td class="centeralign"> Name of model </td><td class="centeralign"> - </td><td class="centeralign"> (12) </td>
- </tr>
- <tr>
- <td>NMOS_TRANSISTOR</td><td class="centeralign"> M? </td><td class="centeralign"> Part number </td><td class="centeralign"> One line SPICE model </td><td class="centeralign"> Model file name </td><td class="centeralign"> Name of model </td><td class="centeralign"> - </td><td class="centeralign"> (12) </td>
- </tr>
- <tr>
- <td>PNP_TRANSISTOR</td><td class="centeralign"> Q? </td><td class="centeralign"> Part number </td><td class="centeralign"> One line SPICE model </td><td class="centeralign"> Model file name </td><td class="centeralign"> Name of model </td><td class="centeralign"> - </td><td class="centeralign"> (12) </td>
- </tr>
- <tr>
- <td>NPN_TRANSISTOR</td><td class="centeralign"> Q? </td><td class="centeralign"> Part number </td><td class="centeralign"> One line SPICE model </td><td class="centeralign"> Model file name </td><td class="centeralign"> Name of model </td><td class="centeralign"> - </td><td class="centeralign"> (12) </td>
- </tr>
- <tr>
- <td>PFET_TRANSISTOR</td><td class="centeralign"> J? </td><td class="centeralign"> Part number </td><td class="centeralign"> One line SPICE model </td><td class="centeralign"> Model file name </td><td class="centeralign"> Name of model </td><td class="centeralign"> - </td><td class="centeralign"> (12) </td>
- </tr>
- <tr>
- <td>NFET_TRANSISTOR</td><td class="centeralign"> J? </td><td class="centeralign"> Part number </td><td class="centeralign"> One line SPICE model </td><td class="centeralign"> Model file name </td><td class="centeralign"> Name of model </td><td class="centeralign"> - </td><td class="centeralign"> (12) </td>
- </tr>
- <tr>
- <td>MESFET_TRANSISTOR</td><td class="centeralign"> B? </td><td class="centeralign"> Part number </td><td class="centeralign"> One line SPICE model </td><td class="centeralign"> Model file name </td><td class="centeralign"> Name of model </td><td class="centeralign"> - </td><td class="centeralign"> (12) </td>
- </tr>
- <tr>
- <td>IC</td><td class="centeralign"> U? </td><td class="centeralign"> Part number </td><td class="rightalign"> </td><td class="centeralign"> .model file name </td><td class="centeralign"> Name of model </td><td class="centeralign"> - </td><td class="centeralign"> For IC with .model file </td>
- </tr>
- <tr>
- <td>IC</td><td class="centeralign"> X? </td><td class="centeralign"> Part number </td><td class="rightalign"> </td><td class="centeralign"> .subckt file name </td><td class="centeralign"> Name of .subckt </td><td class="centeralign"> - </td><td class="centeralign"> For IC with .subckt file </td>
- </tr>
- <tr>
- <td>model</td><td class="centeralign"> A? </td><td class="centeralign"> - </td><td class="centeralign"> One line SPICE model </td><td class="centeralign"> .model file name </td><td class="centeralign"> (9) </td><td class="centeralign"> (10) </td><td class="centeralign"> (12) </td>
- </tr>
- <tr>
- <td>include</td><td class="centeralign"> A? </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="centeralign"> .include file name </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="centeralign"> (13) </td>
- </tr>
- <tr>
- <td>options</td><td class="centeralign"> A? </td><td class="centeralign"> (8) </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="centeralign"> (13) </td>
- </tr>
- <tr>
- <td>directive</td><td class="centeralign"> A? </td><td class="centeralign"> (1) </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="centeralign"> (12) </td>
- </tr>
- <tr>
- <td>VOLTAGE_SOURCE</td><td class="centeralign"> V? </td><td class="centeralign"> (6) </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="centeralign"> Independent voltage source </td>
- </tr>
- <tr>
- <td>CURRENT_SOURCE</td><td class="centeralign"> I? </td><td class="centeralign"> (7) </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="centeralign"> - </td><td class="centeralign"> Independent current source </td>
- </tr>
-</table>
-
-<p>
- (1) One line string holding SPICE statements for inclusion in netlist<br/>
- (2) One line of SPICE model parameters (e.g. TC, etc.)<br/>
- (3) One line of SPICE model parameters (e.g. IC, POLY, etc.)<br/>
- (4) Component numeric value<br/>
- (5) String describing source behavior<br/>
- (6) One line string holding voltage source behavior<br/>
- (7) One line string holding current source behavior<br/>
- (8) line of options to include<br/>
- (9) Name of model pointed to by other components<br/>
- (10) Corresponding SPICE model type (valid types given below)<br/>
- (11) Model parameters are placed inside parentheses after component value<br/>
- (12) For modeling, one must include either model or file<br/>
- (13) Places .include directive in SPICE netlist<br/>
-
-</p>
-
-<p>
-â??Native to the netlisterâ?? means that there is a corresponding blob of scheme code which knows exactly how to handle these components and is guaranteed (almost) to generate correct spice code. Symbols having â??deviceâ?? attributes not on the above list are handled using the scheme function â??spice-sdb:write-default-componentâ??, which looks at the refdes of the component to make a decision about how to treat the component. In general, this function will â??do the right thingâ?? when generating spice code, but it is not guaranteed. In particular, this function cannot distinguish between N and P type transistors, and will generate an <unknown> type for the .MODEL string in the netlist. This will probably cause your SPICE simulator to barf. Therefore, it is best to make sure that all devices used have the proper â??deviceâ?? attribute.
-</p>
-
-</div>
-<!-- SECTION "Appendix A" [55609-60280] -->
-<h1><a name="appendix_b" id="appendix_b">Appendix B</a></h1>
-<div class="level1">
-
-<p>
-<strong>Valid â??typeâ?? values.</strong>
-</p>
-
-<p>
-The â??typeâ?? attribute is a flag signaling the spice engine the component type, and prepares it to accept model parameters specific to that component type. The following values are valid SPICE â??typeâ??s:
-</p>
-<table class="inline">
- <tr>
- <th class="centeralign"> Component </th><th class="centeralign"> â??typeâ?? </th><th class="centeralign"> Comment </th>
- </tr>
- <tr>
- <td class="centeralign"> RESISTOR </td><td class="centeralign"> RES </td><td class="rightalign"> </td>
- </tr>
- <tr>
- <td class="centeralign"> CAPACITOR </td><td class="centeralign"> CAP </td><td class="rightalign"> </td>
- </tr>
- <tr>
- <td class="centeralign"> POLARIZED_CAPACITOR </td><td class="centeralign"> CAP </td><td class="rightalign"> </td>
- </tr>
- <tr>
- <td class="centeralign"> INDUCTOR </td><td class="centeralign"> IND </td><td class="rightalign"> </td>
- </tr>
- <tr>
- <td class="centeralign"> DIODE </td><td class="centeralign"> D </td><td class="rightalign"> </td>
- </tr>
- <tr>
- <td class="centeralign"> PMOS_TRANSISTOR </td><td class="centeralign"> PMOS </td><td class="rightalign"> </td>
- </tr>
- <tr>
- <td class="centeralign"> NMOS_TRANSISTOR </td><td class="centeralign"> NMOS </td><td class="rightalign"> </td>
- </tr>
- <tr>
- <td class="centeralign"> PNP_TRANSISTOR </td><td class="centeralign"> PNP </td><td class="rightalign"> </td>
- </tr>
- <tr>
- <td class="centeralign"> NPN_TRANSISTOR </td><td class="centeralign"> NPN </td><td class="rightalign"> </td>
- </tr>
- <tr>
- <td class="centeralign"> PFET_TRANSISTOR </td><td class="centeralign"> PJF </td><td class="rightalign"> </td>
- </tr>
- <tr>
- <td class="centeralign"> NFET_TRANSISTOR </td><td class="centeralign"> NJF </td><td class="rightalign"> </td>
- </tr>
- <tr>
- <td class="centeralign"> MESFET_TRANSISTOR </td><td class="centeralign"> - </td><td class="rightalign"> </td>
- </tr>
-</table>
-
-<p>
- Table 2: Valid â??typeâ?? attributes for components.
-</p>
-
-</div>
-<!-- SECTION "Appendix B" [60281-] --><div class="footnotes">
-<div class="fn"><a href="#fnt__1" id="fn__1" name="fn__1" class="fn_bot">1)</a>
-This HOWTO is released under the GNU Free Documentation License thanks to the generosity of Electroniscript, inc. The most recent copy can always be found at <a href="http://www.brorson.com/gEDA/HOWTO/"; class="urlextern" title="http://www.brorson.com/gEDA/HOWTO/"; rel="nofollow">http://www.brorson.com/gEDA/HOWTO/</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_cygwin.html b/docs/wiki/geda_cygwin.html
deleted file mode 100644
index 861c898..0000000
--- a/docs/wiki/geda_cygwin.html
+++ /dev/null
@@ -1,132 +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>geda:cygwin</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-10-08T13:25:47-0400" />
-<meta name="keywords" content="geda,cygwin" />
-<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/geda:cygwin?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:cygwin"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:cygwin"; />
-<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">
-
-
-
-<h1><a name="installing_geda_gaf_on_windows_-_the_cygwin_way" id="installing_geda_gaf_on_windows_-_the_cygwin_way">Installing gEDA/gaf on Windows - the Cygwin way</a></h1>
-<div class="level1">
-
-<p>
- This guide describes one way to build gEDA/gaf (gschem and friends) on the Windows operating system. It uses Cygwin as the layer between Windows and the *nix world (ie gcc, make, bash etc…).
-</p>
-
-</div>
-<!-- SECTION "Installing gEDA/gaf on Windows - the Cygwin way" [1-257] -->
-<h2><a name="instructions" id="instructions">Instructions</a></h2>
-<div class="level2">
-
-<p>
- <strong>1. Download and run setup.exe from cygwin website:</strong> <a href="http://www.cygwin.com/"; class="urlextern" title="http://www.cygwin.com"; rel="nofollow">http://www.cygwin.com</a>.
-</p>
-
-<p>
-In the package selection dialog, select the following packages:
-</p>
-
-<p>
-(Hint: press the â??viewâ?? button once to arrange the list in alphabetical order)
-</p>
-<pre class="code">atk-devel
-crypt
-file
-gcc
-gtk2-x11-devel
-guile-devel
-libgmp-devel
-libtool1.5
-make
-pango-devel
-patchutils
-pcre-devel
-pcre-doc
-pkg-config
-xorg-x11-devel
-xorg-x11-fscl
-xterm</pre>
-
-<p>
- <strong>2. Append these lines to your .bash_profile:</strong>
-</p>
-<pre class="code">export LD_LIBRARY_PATH=$HOME/geda/lib:$LD_LIBRARY_PATH
-export PATH=$HOME/geda/bin:$PATH
-export PKG_CONFIG_PATH=$HOME/geda/lib/pkgconfig:$PKG_CONFIG_PATH</pre>
-
-<p>
- Update your environment:
-</p>
-<pre class="code">$ source .bash_profile</pre>
-
-<p>
- <strong>3. Go to the <a href="http://www.geda.seul.org/sources.html"; class="urlextern" title="http://www.geda.seul.org/sources.html"; rel="nofollow">gEDA sources download page</a>.</strong>
-</p>
-
-<p>
-From the gEDA/gaf group, download <strong>only</strong> the packages which have a date as its version. The necessary dependencies were already installed in step 1. However, if you havenâ??t installed or built the libstroke package, be sure to uncomment the opts= line in the gaf Makefile and change it to
-</p>
-<pre class="code">opts=--disable-stroke</pre>
-
-<p>
- <strong>4. Go to the download directory and type:</strong>
-</p>
-<pre class="code">$ make open
-$ make install
-( ...patience... )</pre>
-
-<p>
- <strong>5. Now, to properly view the documentation from the help menu of gschem:</strong>
-</p>
-
-<p>
-Locate the executables of your browser and <acronym title="Portable Document Format">PDF</acronym> reader and create links from /usr/bin. Examples:
-</p>
-<pre class="code">$ ln -s "c:\Program Files\Internet Explorer\iexplore.exe" /usr/bin/iexplore
-$ ln -s "c:\Program Files\Firefox\firefox.exe" /usr/bin/firefox
-$ ln -s "c:\Program Files\Adobe\Acrobat 7.0\Reader\AcroRd32.exe" /usr/bin/acroread</pre>
-
-<p>
- Try:
-</p>
-<pre class="code">$ iexplore
-( Microsoft Internet Explorer appears )
-$ firefox
-( Firefox appears - if installed )
-$ acroread
-( Adobe Acrobat Reader appears )
-$ gschemdoc -m
-( gEDA documentation appears )</pre>
-
-<p>
- <strong>6. Finally, start the X server:</strong>
-</p>
-<pre class="code">$ startx</pre>
-
-<p>
- Have fun!
-</p>
-
-</div>
-<!-- SECTION "Instructions" [258-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/geda_data_plotting_improvements.html b/docs/wiki/geda_data_plotting_improvements.html
deleted file mode 100644
index b2dfa12..0000000
--- a/docs/wiki/geda_data_plotting_improvements.html
+++ /dev/null
@@ -1,148 +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>geda:data_plotting_improvements</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="keywords" content="geda,data_plotting_improvements" />
-<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/geda:data_plotting_improvements?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:data_plotting_improvements"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:data_plotting_improvements"; />
-<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="#simulation_data_plotting" class="toc">Simulation Data Plotting</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#rationale" class="toc">Rationale</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#draft1extend_gtkwaves" class="toc">Draft1: Extend gtkwaves</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#draft2improve_gwave" class="toc">Draft2: improve gwave</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#draft3search_for_existing_data_exploring_programs" class="toc">Draft3: Search for existing data exploring programs</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#draft4a_new_plotting_application" class="toc">Draft4: A new plotting application</a></span></div></li></ul>
-</li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="simulation_data_plotting" id="simulation_data_plotting">Simulation Data Plotting</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "Simulation Data Plotting" [1-41] -->
-<h2><a name="rationale" id="rationale">Rationale</a></h2>
-<div class="level2">
-
-<p>
-This article discusses on how data plotting can be improved. There are various programs out there, each has itâ??s own pros and cons:
-</p>
-<ul>
-<li class="level1"><div class="li"> <a href="http://home.nc.rr.com/gtkwave/"; class="urlextern" title="http://home.nc.rr.com/gtkwave/"; rel="nofollow"> gtkwave</a>: a great viewer for digital simulation data</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://www.telltronics.org/software/gwave/"; class="urlextern" title="http://www.telltronics.org/software/gwave/"; rel="nofollow"> gwave</a>: analog waveform viewer</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://sourceforge.net/projects/kjwaves"; class="urlextern" title="http://sourceforge.net/projects/kjwaves"; rel="nofollow"> KJWaves</a>: simulation frontend with plotting window</div>
-</li>
-<li class="level1"><div class="li"> buildin plotting functions in ngspice</div>
-</li>
-<li class="level1"><div class="li"> gnuplot / octave / scipy / … or similar programs as postprocessing script languages</div>
-</li>
-<li class="level1"><div class="li"> …</div>
-</li>
-</ul>
-
-<p>
- There have been various suggestions on the mailing lists about the feature a plotting program could have:
-</p>
-<ul>
-<li class="level1"><div class="li"> postprocessing: integrate, add, diff, fft, …</div>
-</li>
-<li class="level1"><div class="li"> view, examine: cursors, multiple windows, …</div>
-</li>
-<li class="level1"><div class="li"> data import, file format: circuit simulation data (gnucap, spice, …) <a href="http://www.hdfgroup.org/HDF5/"; class="urlextern" title="http://www.hdfgroup.org/HDF5/"; rel="nofollow"> hdf5 </a>, measured data from oscilloscopes, spectrum analysers, …</div>
-</li>
-<li class="level1"><div class="li"> data export, file format: hdf5, pictures (png, ps, …), ascii</div>
-</li>
-<li class="level1"><div class="li"> communication backends: dbus, …</div>
-</li>
-<li class="level1"><div class="li"> extension/scripting language</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Rationale" [42-1133] -->
-<h2><a name="draft1extend_gtkwaves" id="draft1extend_gtkwaves">Draft1: Extend gtkwaves</a></h2>
-<div class="level2">
-<ul>
-<li class="level1"><div class="li"> write some import functions for analog data</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Draft1: Extend gtkwaves" [1134-1219] -->
-<h2><a name="draft2improve_gwave" id="draft2improve_gwave">Draft2: improve gwave</a></h2>
-<div class="level2">
-
-<p>
- gwave requires an old <a href="http://www.gnu.org/software/guile-gtk/"; class="urlextern" title="http://www.gnu.org/software/guile-gtk/"; rel="nofollow"> guile-gtk</a> for GTK1.2.
-</p>
-<ul>
-<li class="level1"><div class="li"> port gwave to guile-gtk2.0 for GTK2.x</div>
-</li>
-<li class="level1"><div class="li"> remove the guile-gtk requirement. Maybe create a native gtk2 application with libglade?</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Draft2: improve gwave" [1220-1479] -->
-<h2><a name="draft3search_for_existing_data_exploring_programs" id="draft3search_for_existing_data_exploring_programs">Draft3: Search for existing data exploring programs</a></h2>
-<div class="level2">
-
-<p>
- Are there any programs out there that can show and postprocess simulation data? If yes, how can they be extended to work as a waveform viewer for the simulators (gnucap, ngspice)
-</p>
-
-</div>
-<!-- SECTION "Draft3: Search for existing data exploring programs" [1480-1724] -->
-<h2><a name="draft4a_new_plotting_application" id="draft4a_new_plotting_application">Draft4: A new plotting application</a></h2>
-<div class="level2">
-
-<p>
- Some vague notes on how a new plotting application could be written. This notes currently relate on python as programming language.
-</p>
-<ul>
-<li class="level1"><div class="li"> the <acronym title="Graphical User Interface">GUI</acronym> could be created with <a href="http://www.jamesh.id.au/software/libglade/"; class="urlextern" title="http://www.jamesh.id.au/software/libglade/"; rel="nofollow">libglade</a></div>
-</li>
-<li class="level1"><div class="li"> the data storage format could be <a href="http://www.hdfgroup.org/HDF5/"; class="urlextern" title="http://www.hdfgroup.org/HDF5/"; rel="nofollow"> hdf5 </a>, maybe together with <a href="http://www.pytables.org/moin"; class="urlextern" title="http://www.pytables.org/moin"; rel="nofollow">pytables</a></div>
-</li>
-<li class="level1"><div class="li"> the plotting engine could be <a href="http://matplotlib.sourceforge.net/"; class="urlextern" title="http://matplotlib.sourceforge.net/"; rel="nofollow"> matplotlib</a> (png, ps export included)</div>
-</li>
-<li class="level1"><div class="li"> postprocessing could be done with <a href="http://www.scipy.org/"; class="urlextern" title="http://www.scipy.org"; rel="nofollow"> scipy</a></div>
-</li>
-<li class="level1"><div class="li"> the scripting language is python. Thus import filter to hdf5 can easily be written. Even an integrated python shell would be possible. Seen on <a href="http://code.enthought.com/mayavi2-screenshot.shtml"; class="urlextern" title="http://code.enthought.com/mayavi2-screenshot.shtml"; rel="nofollow"> MayaVi 2</a></div>
-</li>
-</ul>
-
-<p>
- Disadvantage: This configuration has a huge rucksack of additional required packages.
-</p>
-
-</div>
-<!-- SECTION "Draft4: A new plotting application" [1725-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/geda_data_structure_design_discussion.html b/docs/wiki/geda_data_structure_design_discussion.html
deleted file mode 100644
index 00c8abd..0000000
--- a/docs/wiki/geda_data_structure_design_discussion.html
+++ /dev/null
@@ -1,238 +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>geda:data_structure_design_discussion</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="keywords" content="geda,data_structure_design_discussion" />
-<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/geda:data_structure_design_discussion?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:data_structure_design_discussion"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:data_structure_design_discussion"; />
-<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="#data_structure_design_discussion" class="toc">Data structure design discussion</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#concept_diagram" class="toc">Concept diagram</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#concepts_behind_the_structures" class="toc">Concepts behind the structures</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#design" class="toc">Design</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#circuit" class="toc">Circuit</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#mport" class="toc">MPort</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#instance" class="toc">Instance</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#attrib" class="toc">Attrib</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#netlist" class="toc">Netlist</a></span></div></li>
-<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="#page" class="toc">Page</a></span></div></li>
-</ul>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"><span class="li"><a href="#brainstorms" class="toc">Brainstorms</a></span></div></li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="data_structure_design_discussion" id="data_structure_design_discussion">Data structure design discussion</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "Data structure design discussion" [1-48] -->
-<h1><a name="concept_diagram" id="concept_diagram">Concept diagram</a></h1>
-<div class="level1">
-
-<p>
- (Inspired by gnetman, by Bill Cox)
-</p>
-
-<p>
-<a href="http://geda.seul.org/wiki/lib/exe/fetch.php?cache=cache&media=http%3A%2F%2Fwww2.eng.cam.ac.uk%2F%7Epcjc2%2Fgeda%2Fdatastructures.png"; class="media" title="http://www2.eng.cam.ac.uk/~pcjc2/geda/datastructures.png";><img src="http://geda.seul.org/wiki/lib/exe/fetch.php?w=&h=&cache=cache&media=http%3A%2F%2Fwww2.eng.cam.ac.uk%2F%7Epcjc2%2Fgeda%2Fdatastructures.png"; class="media" alt="" /></a>
-</p>
-
-</div>
-<!-- SECTION "Concept diagram" [49-178] -->
-<h2><a name="concepts_behind_the_structures" id="concepts_behind_the_structures">Concepts behind the structures</a></h2>
-<div class="level2">
-
-</div>
-<!-- SECTION "Concepts behind the structures" [179-222] -->
-<h3><a name="design" id="design">Design</a></h3>
-<div class="level3">
-
-<p>
- This is might not exist as a â??fileâ??, as such, but exists as a data structure entity to be the owner of the circuits required in a particular design. The â??root circuitâ?? is the uppermost level of hierarchy.
-</p>
-
-</div>
-<!-- SECTION "Design" [223-446] -->
-<h3><a name="circuit" id="circuit">Circuit</a></h3>
-<div class="level3">
-
-<p>
- A <strong>circuit</strong> entity is the key concept in this model. It defines an electrical block by a its external connections (<strong>MPort</strong>s). A schematic is one way of representing a circuit, hence a circuit object may own or more <strong>page</strong> of schematics.
-</p>
-
-<p>
-We may also define a <strong>symbolic</strong> (graphic) representation of a circuit - this is like a schematic <strong>page</strong>, however its representation should fit within a single sheet. The minimum a symbolic representation must contain is the <strong>pins</strong> which connect it to higher levels of circuit hierarchy.
-</p>
-
-</div>
-<!-- SECTION "Circuit" [447-1004] -->
-<h3><a name="mport" id="mport">MPort</a></h3>
-<div class="level3">
-
-<p>
- If it is to be useful as a re-usable block, a sub-<strong>circuit</strong> must expose electrical connectivity for a parent <strong>circuit</strong> to connect with. Each such connection is represented by an <strong>Mport</strong> (Master port). This term (re-used from gnetman) represents the fact that once a circuit is instantiated, we need to differentiate between the connections of each specific instance. This is done with instance specific <strong>Port</strong> structures. The <strong>port</strong>s point back at the <strong>Mport</strong>s (master ports) of the circuit representation.
-</p>
-
-</div>
-<!-- SECTION "MPort" [1005-1541] -->
-<h3><a name="instance" id="instance">Instance</a></h3>
-<div class="level3">
-
-<p>
- A <strong>circuit</strong> represents a re-usable electrical entity which we may replicate at various points in our design hierarchy. This is done by instantiating the sub-<strong>circuit </strong> in a higher level of hierarchy. Each instance is associated with an <strong>Instance</strong> structure, which is a placeholder for instance specific attributes such as the sub-circuitâ??s hierarchical refdes.
-</p>
-
-</div>
-<!-- SECTION "Instance" [1542-1929] -->
-<h3><a name="attrib" id="attrib">Attrib</a></h3>
-<div class="level3">
-
-<p>
- An <strong>Attrib</strong> defines meta-data attached which might be attached to a <strong>circuit</strong>, a <strong>circuit</strong>â??s <strong>Mport</strong>, a specific <strong>circuit</strong> <strong>instance</strong>, or a <strong>Net</strong>.
-</p>
-
-<p>
-In a break from gEDAâ??s current <strong>attrib</strong> model, it makes sense to associate the meta-data directly with the particular entity it pertains to, rather than the graphic representation. This is because some forms of sub-<strong>circuit</strong> entity may be defined without a schematic, and could still require this meta-data. It will be possible to reference any <strong>attrib</strong> within the realm of a <strong>circuit</strong> for display on its schematic <strong>page</strong>(s) where that is desired.
-</p>
-
-</div>
-<!-- SECTION "Attrib" [1930-2569] -->
-<h3><a name="netlist" id="netlist">Netlist</a></h3>
-<div class="level3">
-
-<p>
- A <strong>Netlist</strong> defines the electrical connectivity of a <strong>circuit</strong>. It owns a number of <strong>Net</strong>s, which individually represent a single connection between <strong>Mport</strong>s belonging to this <strong>circuit</strong>, and <strong>ports</strong> of instantiated sub-<strong>circuits</strong>.
-</p>
-
-<p>
-Initially, it is likely there will only be one netlist for a <strong>circuit</strong> - the one constructed from processing the electrically relevant objects on <strong>page</strong>(s) of the <strong>circuit</strong>â??s schematic.
-</p>
-
-<p>
-Future developments may see multiple netlists for a circuit, possibly some generated / written in an HDL language, and critically, re-exported from a layout package (e.g. PCB). It will be possible to identify and flag up differences in connectivity throughout a design flow, be that from HDL to schematic, or schematic to layout.
-</p>
-
-<p>
-This has real applications in back-annotation and in design verification.
-</p>
-
-</div>
-<!-- SECTION "Netlist" [2570-3435] -->
-<h3><a name="net" id="net">Net</a></h3>
-<div class="level3">
-
-<p>
- A <strong>net</strong> associates with structures forming a given electrical connection within this <strong>circuit</strong>.
-</p>
-
-<p>
-As we also have a graphical representation of the wires (<strong>ConnSegment</strong>s) which make up this connection, each <strong>Net</strong> can be associated with multiple <strong>ConnSegment</strong>s. The association to <strong>Pins</strong> representing <strong>Mport</strong>s of this <strong>circuit</strong> and to the <strong>Pins</strong> of any instantiated sub-<strong>circuits</strong> is made via a <strong>net</strong>â??s association to the appropriate <strong>Mport</strong> and <strong>port</strong> structures.
-</p>
-
-</div>
-<!-- SECTION "Net" [3436-3940] -->
-<h3><a name="page" id="page">Page</a></h3>
-<div class="level3">
-
-<p>
- A <strong>page</strong> is a canvas for placing graphical objects representing a circuit. A <strong>page</strong> can be used to draw an electrically meaningful schematic, or it can be used to draw a symbolic representation of the circuit entity.
-</p>
-
-<p>
-Whilst most objects on a <strong>page</strong> are graphic primitives, there are some which have a relation to the <strong>circuit</strong>â??s electrical specification.
-</p>
-<ul>
-<li class="level1"><div class="li"> <strong>ConnSegments</strong> (or <strong>net</strong>s) represent connected electrical signals within the circuit represented.</div>
-<ul>
-<li class="level2"><div class="li"> A connectivity representation (<strong>netlist</strong>) can be built by considering the end-point positioning of these objects.</div>
-</li>
-<li class="level2"><div class="li"> <strong>ConnSegment</strong> is intended to be a generalisation of <strong>net</strong>s and <strong>bus</strong>es for the purpose of this diagram.</div>
-</li>
-</ul>
-</li>
-</ul>
-<ul>
-<li class="level1"><div class="li"> <strong>Pins</strong> represent a connection outside this circuit.</div>
-<ul>
-<li class="level2"><div class="li"> When constructing a netlist, coincidence of a <strong>ConnSegment</strong> end on these implies an electrical connection to that external port.</div>
-</li>
-<li class="level2"><div class="li"> Each <strong>pin</strong> (or group of pins?) represent an external electrical connection with this <strong>circuit</strong>.</div>
-</li>
-<li class="level2"><div class="li"> There is a necessary link between a <strong>pin</strong> and the circuitâ??s <strong>Mport</strong> which it represents.</div>
-</li>
-</ul>
-</li>
-</ul>
-<ul>
-<li class="level1"><div class="li"> <strong>complex</strong> objects represent instantiating a sub-<strong>circuit</strong>, and will be linked to a specific <strong>instance</strong> structure.</div>
-<ul>
-<li class="level2"><div class="li"> Graphically, this means a <strong>symbolic</strong> representation of the instantiated circuit will be placed on the page.</div>
-</li>
-<li class="level2"><div class="li"> Nets ending co-incident with the <strong>pins</strong> of that embedded symbol represent electrical connectivity with the instantiated sub-<strong>circuit</strong> entity.</div>
-</li>
-</ul>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Page" [3941-5460] -->
-<h1><a name="brainstorms" id="brainstorms">Brainstorms</a></h1>
-<div class="level1">
-
-<p>
- (from conversation on MSN/<acronym title="Internet Relay Chat">IRC</acronym> on 10th April 2007 – Peter Brett / Peter Clifton)
-</p>
-<ul>
-<li class="level1"><div class="li"> In order to do back annotation, need to be able to change the board part references for anywhere in the schematic. It then makes sense to dissociate the concepts of <strong>InstanceID</strong> and <strong>Board Reference</strong>, and use an <strong>override table</strong> that can override an attribute at any given path within the current <strong>circuit</strong> based on a path composed of <strong>InstanceID</strong>s. <strong>InstanceID</strong>s would be special-cased throughout libgeda as a means for uniquely identifying circuits and instances. An entry in the override table might have the form "/id1/id2/id3:refdes:U3â??</div>
-</li>
-</ul>
-<ul>
-<li class="level1"><div class="li"> It might be useful to allow nets to have attributes, for instance to specify minimum copper width and spacing for a net, independently from the attributes of net segments.</div>
-</li>
-</ul>
-<ul>
-<li class="level1"><div class="li"> The schematic editor needs to have sidebars for browsing hierarchy and inspecting attributes. This needs to include a way of seeing where the attributes have been inherited from.</div>
-</li>
-</ul>
-<ul>
-<li class="level1"><div class="li"> We need to do lazy netlisting, on a circuit-by-circuit basis – the netlists should only be combined into a flat netlist when required by a tool (and even then, most tools can potentially make good use of hierarchy information).</div>
-</li>
-</ul>
-<ul>
-<li class="level1"><div class="li"> In order to make finding objects by hierarchical path fast (e.g. to implement override tables discussed above) there needs to be a fast way of generating unique identifiers for objects (e.g. 32-bit ints) that can then be used as keys in hashtables.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Brainstorms" [5461-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/geda_debian.html b/docs/wiki/geda_debian.html
deleted file mode 100644
index 2355f06..0000000
--- a/docs/wiki/geda_debian.html
+++ /dev/null
@@ -1,64 +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>geda:debian</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="keywords" content="geda,debian" />
-<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/geda:debian?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:debian"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:debian"; />
-<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">
-
-
-
-<h1><a name="installer_20070221_on_debian_testing" id="installer_20070221_on_debian_testing">Installer 20070221 on Debian/testing</a></h1>
-<div class="level1">
-
-<p>
-The iso image contains binary packages to all the open source development utilities needed to build the geda suite. Nevertheless, it is advisable to stick with the native debian versions to avoid an inconsistent mix of packages. In april 2007 an install of the geda/gaf iso image 20070221 the following additional packages were necessary on a fresh debian/lenny box:
-</p>
-<ul>
-<li class="level1"><div class="li"> pkg-config</div>
-</li>
-<li class="level1"><div class="li"> libreadline5-dev</div>
-</li>
-<li class="level1"><div class="li"> libgd2</div>
-</li>
-<li class="level1"><div class="li"> libgd2-dev</div>
-</li>
-<li class="level1"><div class="li"> guile1.6-dev</div>
-</li>
-<li class="level1"><div class="li"> libwxgtk2.6-dev</div>
-</li>
-<li class="level1"><div class="li"> libgtk2.0-dev</div>
-</li>
-<li class="level1"><div class="li"> flex</div>
-</li>
-<li class="level1"><div class="li"> bison</div>
-</li>
-<li class="level1"><div class="li"> g++</div>
-</li>
-</ul>
-
-<p>
-The debian package manager will expand this list significantly as required by the debian database of dependencies.
-</p>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_design_flow_and_hierarchy_roadmap.html b/docs/wiki/geda_design_flow_and_hierarchy_roadmap.html
deleted file mode 100644
index f3d53dc..0000000
--- a/docs/wiki/geda_design_flow_and_hierarchy_roadmap.html
+++ /dev/null
@@ -1,271 +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>geda:design_flow_and_hierarchy_roadmap</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="keywords" content="geda,design_flow_and_hierarchy_roadmap" />
-<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/geda:design_flow_and_hierarchy_roadmap?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:design_flow_and_hierarchy_roadmap"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:design_flow_and_hierarchy_roadmap"; />
-<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="#required_for_production_circuits" class="toc">Required for production circuits</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#intermediate_translation_file_format_vhdl_edif" class="toc">intermediate translation file format VHDL? EDIF?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#hierarchical_buses" class="toc">Hierarchical Buses</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#ipc_improvements" class="toc">IPC Improvements</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#robust_function" class="toc">Robust Function</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#other_improvements" class="toc">Other Improvements</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#too_detailed" class="toc">Too Detailed</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#implementation" class="toc">Implementation</a></span></div></li></ul>
-</li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="required_for_production_circuits" id="required_for_production_circuits">Required for production circuits</a></h1>
-<div class="level1">
-<ul>
-<li class="level1"><div class="li"> hierarchy in schematic and netlist and pcb – modules that can be reused, arrayed.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Required for production circuits" [1-135] -->
-<h2><a name="intermediate_translation_file_format_vhdl_edif" id="intermediate_translation_file_format_vhdl_edif">intermediate translation file format VHDL? EDIF?</a></h2>
-<div class="level2">
-
-</div>
-
-<h4><a name="schematic_layout_logic_sim_analog_sim_etc" id="schematic_layout_logic_sim_analog_sim_etc">Schematic, Layout, logic sim, analog sim, etc</a></h4>
-<div class="level4">
-
-<p>
- In an *AMS language, nets have types. Itâ??s not just â??wireâ??. The schematic needs to be extended so that pins on symbols can have types. It is not prohibited to mix types. Verilog has something called a â??connectmoduleâ?? to define how to resolve mixed types. <strong>gschem attributes need to have types.</strong> [Al Davis]
-</p>
-
-<p>
- I certainly agree that the (gnetlist-ed.) Verilog output is not â??losslessâ?? – itâ??s only an interchange format for the interconnect…[Mike Jarabek]
-</p>
-
-<p>
- Heâ??s not actually proposing to use VHDL (as modeling language-ed.) but to steal some <strong>syntax from VHDL</strong> and interpret it as he sees fit for the task. In particular, heâ??s only interested in the <strong>entity-architecture separation</strong>[Steve Williams]
-</p>
-
-<p>
-More useful, (than creating intermediate file formats-ed.) is to <strong>refactor libgeda and define an <acronym title="Application Programming Interface">API</acronym></strong> which can be exposed via C, scheme, DBus, and other scripting languages directly modifying the underlying design. [Peter Clifton]
-</p>
-
-<p>
- Any extraction should preserve hierarchy, in hopes that the target tool also benefits from it. Translation must be 100%, lossless, from netlist to PCB refdes, and from PCB refdes used to create a module or back annotate a schematic. [Al Davis] [paraphrased heavily by JGriessen – correct?]
-</p>
-
-<p>
- The <strong>file format should be designed as a language</strong> meaningful and expressive of IC, programmable logic, and printed circuits. File formats that are data structure dumps cause big problems. We need an interchange file format..[Al Davis]
-</p>
-
-<p>
- If EDIF has layout objects or schematic objects built-in, that is actually a weakness. Just like SPICE having resistors and transistors built-in has become a weakness.[Al Davis]
-</p>
-
-<p>
- <strong>EDIFâ??s not mainstream.</strong> VHDL and Verilog are mainstream. That is one reason for my preference. Itâ??s not all technical[Al Davis]
-</p>
-
-<p>
- <strong>PCB behavior with a hierarchic netlist</strong> Right click on a symbol, select â??go insideâ??, and another drawing opens up showing whatâ??s inside. gschem also should act this way. [Al Davis] Display in place whatâ??s inside, <strong>turn on/off the visibility</strong> or â??editabilityâ?? of any subcells. [Igor] <strong>Ability to visually toggle</strong> [Dan McMahill] <strong>â??blocksâ?? should be translucent.</strong> (To show in place)ed. even when youâ??re not editing it. [DJ Delorie] Yep. [John Griessen] Dive into a block so you can edit it. When done, <strong>close and updated in place</strong>. [DJ Delorie]
-</p>
-
-<p>
-<strong>how to handle re-use blocks?</strong> [Stuart Brorson] That is, if I have a sub-schematic which I instantiate four times, how should it be refdesed in the netlist?
-</p>
-
-</div>
-<!-- SECTION "intermediate translation file format VHDL? EDIF?" [136-2788] -->
-<h2><a name="hierarchical_buses" id="hierarchical_buses">Hierarchical Buses</a></h2>
-<div class="level2">
-
-</div>
-<!-- SECTION "Hierarchical Buses" [2789-2821] -->
-<h2><a name="ipc_improvements" id="ipc_improvements">IPC Improvements</a></h2>
-<div class="level2">
-
-<p>
- (InterProcess Communication -ed.) between gschem and PCB using DBus will benefit from netlisting changes (certainly cross probing and back annotation).[Peter Clifton]
-</p>
-
-<p>
- Peter Brett and I put together a graphical frontend to gsch2pcb which uses gsch2pcbâ??s output to feed changes into a live PCB layout. [Peter Clifton]
-</p>
-
-<p>
- For <strong>cross-probing</strong> / interactive simulation / back annotation, we require libgeda to <strong>give gschem, gattrib etc.. the circuit representation</strong> underlying your schematic drawing.[Peter Clifton]
-</p>
-
-</div>
-<!-- SECTION "IPC Improvements" [2822-3368] -->
-<h2><a name="robust_function" id="robust_function">Robust Function</a></h2>
-<div class="level2">
-
-<p>
- libgeda could/should evolve - as a backend to different tools. Since the PCB file-format is PCBâ??s, and may change, it is wiser to use a defined <acronym title="Application Programming Interface">API</acronym> to PCB to make PCB write the file. This entails adding to PCBâ??s action interface as necessary, and making gsch2pcb output a script of actions rather than a â??PCBâ?? file. [Peter Clifton]
-</p>
-
-<p>
- Iâ??m hoping to separate much of the <acronym title="Graphical User Interface">GUI</acronym> structure and cram that back in the applications it belongs in, re-structuring libgeda to be design data-oriented.[Peter Clifton]
-</p>
-
-<p>
-<strong>function library with bindings to users language of choice</strong> a proper, â??officialâ?? <acronym title="Practical Extraction and Report Language">Perl</acronym>-callable library to parse a layout file, a footprint file, or a schematic file, and load the data into an in-memory data structure. Such a library to read and write these file formats would dramatically reduce the activation energy hump to write a rich set of tools for all of us. [CP Tarun]
-</p>
-
-<p>
- It would not fall out of sync with the changing file-formats, because you wouldnâ??t write yet another implementation of the parser, data-structures etc, nor would you copy-paste code. You would have one library which is used by all tools (probably in C as this is what the suite mostly uses), then you would provide language bindings so people can write the useful utilities they want. If this means having to split code out of existing tools and into a library, that is the way forward in terms of code reuse. [Peter Clifton]
-</p>
-
-<p>
- I completely agree. [Dan McMahill]
-</p>
-
-<p>
- Also consider libgpmi which currently supports 8 languages, will support guile [Igor]
-</p>
-
-</div>
-<!-- SECTION "Robust Function" [3369-4944] -->
-<h2><a name="other_improvements" id="other_improvements">Other Improvements</a></h2>
-<div class="level2">
-
-<p>
-It is very useful I think to let DRC run to completion and <strong>have a DRC layer</strong> (or perhaps 1 DRC layer per copper layer as you suggest) that identifies exactly the <strong>offending feature</strong>.[Dan McMahill]
-</p>
-
-<p>
-<strong>layout and save a hierarchy module</strong> [Steve Meier]
-</p>
-
-<p>
- have a block (in PCB)ed. that is a modular entity. Normally, you canâ??t do anything but move it around as a whole. A special action â??opensâ?? this block (and hides everything else) so you can edit it. When youâ??re done, itâ??s closed again - and any copies of the block are automatically updated in place. [DJ Delorie]
-</p>
-
-<p>
-<strong>be able in the netlist to tell pcb which slots are swapable</strong>, which i/o pins are swapable and which pin pairs can function as differential pairs (these last two have to be able to be limited to specific banks) such that pcb could correctly change the net list itself. Then I would like PCB to be able to tell me what pins and in what order the pins were swapped so that this could be imported back into the original design.[Steve Meier]
-</p>
-
-<p>
- <strong>gschem attribute editable as symbols placed</strong>, (such as description of the layout footprint attribute) [CP Tarun]
-</p>
-
-<p>
-<strong> recesses in boards, (holes in PCB layers)</strong>[Steve Meier] Required for straight leads out side of packages and flex circuits.
-</p>
-
-<p>
- Yeah, youâ??d need the â??layer typesâ?? patch to really manage that, as youâ??d be able to tag multiple pcb layers as â??outlineâ?? layers[DJ Delorie]
-</p>
-
-<p>
-<strong> PCB should be able to do hidden vias</strong>, buried vias and micro vias. [Steve Meier]
-</p>
-
-<p>
- Answered by non-copper layers, multi-pin projects in SoC list [DJ Delorie]
-</p>
-
-<p>
- Use padstack to build elements with copper and non-copper layers independent.[Levente]
-</p>
-
-<p>
- <strong>a PCB interface for presenting dynamic dialog boxes</strong> for importers [Igor] I think this is part of having easy scripting of userâ??s choice, so an important design flow consideration[John Griessen]
-</p>
-
-</div>
-<!-- SECTION "Other Improvements" [4945-6847] -->
-<h2><a name="too_detailed" id="too_detailed">Too Detailed</a></h2>
-<div class="level2">
-
-<p>
-<strong>change only the top of hierarchy string</strong> of a layout module to netlist correctly.[Steve Meier]
-</p>
-
-<p>
-<strong>Separate the hierarchy</strong> from the rest of the refdes. [Steve Meier]
-</p>
-
-<p>
- PCB doesnâ??t care what the refdes is, a heirarchical one is just as valid [DJ Delorie]
-</p>
-
-<p>
-<strong>In gschem, visually browse the symbol library</strong>.[CP Tarun]
-</p>
-
-<p>
- Can be putoff and done as a <acronym title="Graphical User Interface">GUI</acronym> plugin script – a detail of easy scripting wants [JGriessen]
-</p>
-
-<p>
-<strong>In gschem, more control over printed or exporting</strong>, as in CAM files a la Eagle.[CP Tarun]
-</p>
-
-<p>
- Can be putoff and done as a <acronym title="Graphical User Interface">GUI</acronym> plugin script – a detail of easy scripting wants [JGriessen]
-</p>
-
-</div>
-<!-- SECTION "Too Detailed" [6848-7493] -->
-<h2><a name="implementation" id="implementation">Implementation</a></h2>
-<div class="level2">
-
-<p>
- <strong>What kind of data structures are desirable?</strong> How would they look? [Stuart Brorson] <strong>Once a datastructure is decided upon, then what does the file format look like?</strong> Preserving the current close mapping of files to data structures is a desirable goal. The data structures defining hierarchy dictate what the file format should look like. [Stuart Brorson]
-</p>
-
-<p>
- Right now, the main data structure for a schematic is a linear linked list of graphical objects (for each schematic page). Some list items point to others (i.e. to support component attributes). How would that change to support hierarchy? [Stuart Brorson]
-</p>
-
-<p>
- PCB has a second format it uses called a â??resource fileâ??. Itâ??s a semi-lisp-ish format that allows for arbitrarily nested data. It could be used to hold pretty much anything, but it isnâ??t â??designed for the dataâ??.[DJ Delorie]
-</p>
-
-<p>
-<strong>How should gschem behave once hierarchy is architected in?</strong> Right now you attach a source= attribute to a symbol. Then you do â??schematic downâ?? on that symbol to dive into the sub-schematic. Is that OK? Or whatâ??s a better scheme?
-</p>
-
-<p>
-<strong>Some work has already been done using gnetman by Bill Cox,</strong> but it has never been part of the distribution gnetlist. Dan McMahill wrote: â??a reason to use the gnetman database as opposed to one designed by one of usâ?? is that without availing Bill Coxâ??s substantial tested work, we may â??find that the underlying database structure and methods for accessing it still arenâ??t complete enough, fast enough, or scalable enough."
-</p>
-
-<p>
-<strong>Some work has already been done by Steve Meier</strong> to enable practical work on FPGAs.
-</p>
-
-<p>
-<strong>Some design work has been done by Peter Brett and Peter Clifton,</strong> producing a concept diagram of a sub-circuit oriented data-structure based on gnetmanâ??s structure diagram for netlisting. See <a href="geda_data_structure_design_discussion.html" class="wikilink1" title="geda:data_structure_design_discussion">data structure design discussion</a>
-</p>
-
-</div>
-<!-- SECTION "Implementation" [7494-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/geda_devel-tips.html b/docs/wiki/geda_devel-tips.html
deleted file mode 100644
index 04b9a0b..0000000
--- a/docs/wiki/geda_devel-tips.html
+++ /dev/null
@@ -1,759 +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>geda:devel-tips</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-05-24T22:27:26-0400" />
-<meta name="keywords" content="geda,devel-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/"; />
-<link rel="contents" href="http://geda.seul.org/wiki/geda:devel-tips?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:devel-tips"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:devel-tips"; />
-<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="#geda_developer_tips_tricks_and_hints" class="toc">gEDA Developer Tips, tricks and hints</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#how_to_branch_correctly_using_cvs" class="toc">How to branch correctly using CVS</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#doxygen_comments_and_styles" class="toc">Doxygen Comments and styles</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#dialogsdesign_and_behaviour" class="toc">Dialogs: Design and Behaviour</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#dialog_design" class="toc">Dialog Design</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#modal_or_nonmodal_dialogs" class="toc">Modal or Nonmodal dialogs</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#where_to_place_the_dialog" class="toc">Where to place the dialog</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#placing_dialogs_in_front_of_their_parent_window" class="toc">Placing dialogs in front of their parent window</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#button_order_in_dialogs" class="toc">Button order in dialogs</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#dialog_design_of_the_current_dialogs" class="toc">Dialog design of the current dialogs</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#source_template_for_simple_dialogs" class="toc">Source template for simple dialogs</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#current_dialog_issues_in_gschem" class="toc">Current Dialog Issues in Gschem</a></span></div></li></ul>
-</li></ul>
-</li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="geda_developer_tips_tricks_and_hints" id="geda_developer_tips_tricks_and_hints">gEDA Developer Tips, tricks and hints</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "gEDA Developer Tips, tricks and hints" [1-53] -->
-<h2><a name="how_to_branch_correctly_using_cvs" id="how_to_branch_correctly_using_cvs">How to branch correctly using CVS</a></h2>
-<div class="level2">
-
-<p>
- Hereâ??s a summary of what should happen with development on a branch that is intended to later be merged to the trunk. Suppose the branch is called â??mineâ??.
-</p>
-
-<p>
-1) tag the repository (trunk) to create a branch point tag:
-</p>
-<pre class="code"> cvs tag mine-base </pre>
-
-<p>
- 2) branch
-</p>
-<pre class="code"> cvs tag -b -r mine-base mine</pre>
-
-<p>
- What step #1 does is to keep track of where the â??mineâ?? branch started <br/>
- from. The "-r mine-baseâ?? in step #2 says to create the branch starting <br/>
- from the tag â??mine-baseâ??. It is important to do this because you need<br/>
- to be able to know where each file is rooted (i.e., what version in the <br/>
- trunk it is derived from).
-</p>
-
-<p>
-Usually, it is a good idea to periodically merge changes which have taken <br/>
- place on the trunk to the branch. This will reduce the amount of work when <br/>
- the work on the branch is ready to go back to the trunk.
-</p>
-
-<p>
-# go to where the trunk is checked out and update it
-</p>
-<pre class="code"> cd /to/my/trunk/sources
- cvs update -PdA</pre>
-
-<p>
- # create a temporary tag in case someone commits stuff while youâ??re<br/>
- # in the middle of this procedure. This keeps you from losing anything.
-</p>
-<pre class="code"> cvs tag merge-mine</pre>
-
-<p>
- # go to your branch source tree
-</p>
-<pre class="code">
- cd /to/my/branch/sources
- cvs update -Pd</pre>
-
-<p>
- # the following says to apply the changes that have taken place on<br/>
- # the trunk between the version tagged with â??mine-baseâ?? and â??merge-mineâ??<br/>
- # to your branch source tree
-</p>
-<pre class="code"> cvs update -j mine-base -j merge-mine -dP</pre>
-
-<p>
- # if all goes well, youâ??ll have no conflicts. It is not uncommon <br/>
- # for there to be some cases where you have to resolve conflicts by<br/>
- # hand. In this case the affected files will have a special comment<br/>
- # showing what your file on the branch had and what the file tagged as<br/>
- # merge-mine had. You, as the programmer, have to figure out what is<br/>
- # correct. Once this is all done, proceed.<br/>
-
-</p>
-
-<p>
-# checkin with a message like â??sync with trunkâ?? or<br/>
- # â??pull up revs #### from the trunkâ?? (if you were pulling up<br/>
- # a specific change).
-</p>
-<pre class="code"> cvs ci</pre>
-
-<p>
- # Now we move the branch point tag to the temporary merge tag<br/>
- # This is because we have changed what rev each file in the branch<br/>
- # is based on in the trunk. This is known as re-rooting.
-</p>
-<pre class="code"> cvs tag -F -r merge-mine mine-base</pre>
-
-<p>
- # now we donâ??t need the temporary merge tag anymore so remove it
-</p>
-<pre class="code"> cvs tag -d merge-mine</pre>
-
-<p>
- When it is time to merge changes that have taken place on a branch back<br/>
- to the trunk (usually marking the end of that branch), first do a final <br/>
- trunk → branch merge as mentioned above. Then do a branch → trunk merge.
-</p>
-
-<p>
-Now for a branch to trunk merge youâ??d do
-</p>
-<pre class="code"> cd /to/my/trunk/sources
- cvs update -PdA
- cvs update -j mine-base -j mine -dP</pre>
-
-<p>
- # resolve conflicts
-</p>
-<pre class="code"> cvs ci
- cvs tag -F mine-base</pre>
-
-<p>
- This takes any changes between â??mine-baseâ?? and â??mineâ?? and tries to apply <br/>
- it to the trunk. If it all goes cleanly, you just check it in otherwise you <br/>
- have to resolve conflicts. Then you move the branch point tag because the trunk<br/>
- now reflects the lastest in the branch.
-</p>
-
-<p>
-The above was contributed by Dan McMahill
-</p>
-
-</div>
-<!-- SECTION "How to branch correctly using CVS" [54-3116] -->
-<h2><a name="doxygen_comments_and_styles" id="doxygen_comments_and_styles">Doxygen Comments and styles</a></h2>
-<div class="level2">
-
-<p>
- Any volunteer for writing some notes?
-</p>
-<ul>
-<li class="level1"><div class="li"> which keywords to use</div>
-</li>
-<li class="level1"><div class="li"> a template for a function</div>
-</li>
-<li class="level1"><div class="li"> a template for structs?</div>
-</li>
-<li class="level1"><div class="li"> bug, todo and fixme tags</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Doxygen Comments and styles" [3117-3310] -->
-<h2><a name="dialogsdesign_and_behaviour" id="dialogsdesign_and_behaviour">Dialogs: Design and Behaviour</a></h2>
-<div class="level2">
-
-</div>
-<!-- SECTION "Dialogs: Design and Behaviour" [3311-3353] -->
-<h3><a name="dialog_design" id="dialog_design">Dialog Design</a></h3>
-<div class="level3">
-
-<p>
-Thereâ??s a nice document from the gnome guys called <a href="http://developer.gnome.org/projects/gup/hig/2.0/"; class="urlextern" title="http://developer.gnome.org/projects/gup/hig/2.0/"; rel="nofollow"> Gnome HIG</a>. There are several suggestions on how to design dialogs and how they should behave.
-</p>
-
-<p>
-<strong> The dialog design is mostly a matter of taste:</strong>
-</p>
-<ul>
-<li class="level1"><div class="li"> alignment of elements. See <a href="http://developer.gnome.org/projects/gup/hig/2.0/design-window.html"; class="urlextern" title="http://developer.gnome.org/projects/gup/hig/2.0/design-window.html"; rel="nofollow"> Window Layout</a></div>
-</li>
-<li class="level1"><div class="li"> right alignment of dialog buttons</div>
-</li>
-<li class="level1"><div class="li"> some spacing around the dialog (but how much?)</div>
-</li>
-<li class="level1"><div class="li"> some spacing between the elements (vertical and horizontal)</div>
-</li>
-<li class="level1"><div class="li"> option groups with frames or indentation?</div>
-</li>
-<li class="level1"><div class="li"> frame labels or bold headlines?</div>
-</li>
-</ul>
-
-<p>
- <strong>Misc:</strong>
-</p>
-<ul>
-<li class="level1"><div class="li"> with a <a href="http://www.chipx86.com/wiki/Libsexy#SexyIconEntry"; class="urlextern" title="http://www.chipx86.com/wiki/Libsexy#SexyIconEntry"; rel="nofollow"> libsexy widget</a> it would be possible to place an icon inside the text entry this would be usefull for some dialogs: </div>
-<ul>
-<li class="level3"><div class="li"> the filter entry in the component select dialog</div>
-</li>
-<li class="level3"><div class="li"> the file select in the print dialog</div>
-</li>
-<li class="level3"><div class="li"> the file select in the export png dialog</div>
-</li>
-</ul>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Dialog Design" [3354-4328] -->
-<h3><a name="modal_or_nonmodal_dialogs" id="modal_or_nonmodal_dialogs">Modal or Nonmodal dialogs</a></h3>
-<div class="level3">
-
-<p>
-A modal dialog is required whenever the main application provides data for the dialog.
-</p>
-<pre class="code">Example:
- The dialog is called with a selection list and the dialog only should operate on this selection.</pre>
-
-<p>
- A modal dialog is OK too, if the dialog is only called very seldom. The file open dialog could be nonmodal because it does not require any input from the application.
-</p>
-
-<p>
-A modal dialog is not OK if there is a lot of user interaction with the dialog. The component selection is a good example.
-</p>
-
-</div>
-<!-- SECTION "Modal or Nonmodal dialogs" [4329-4859] -->
-<h3><a name="where_to_place_the_dialog" id="where_to_place_the_dialog">Where to place the dialog</a></h3>
-<div class="level3">
-
-<p>
-A dialog can be put on different places in on the screen. A list of possible places can be found in the <a href="http://developer.gnome.org/doc/API/2.0/gtk/gtk-Standard-Enumerations.html#GtkWindowPosition"; class="urlextern" title="http://developer.gnome.org/doc/API/2.0/gtk/gtk-Standard-Enumerations.html#GtkWindowPosition"; rel="nofollow"> GtkReference</a>
-</p>
-
-<p>
-The current dialogs are placed either on the mouse position (GTK_WIN_POS_MOUSE) or at no preset position (GTK_WIN_POS_NONE). The Gnome HID does not say anything about that topic.
-</p>
-
-<p>
-The default setting is GTK_WIN_POS_NONE for GtkWindow see <a href="http://developer.gnome.org/doc/API/2.0/gtk/GtkWindow.html#GtkWindow--window-position"; class="urlextern" title="http://developer.gnome.org/doc/API/2.0/gtk/GtkWindow.html#GtkWindow--window-position"; rel="nofollow"> GtkWindow</a>. The default for GtkDialog is GTK_WIN_POS_CENTER_ON_PARENT (<a href="http://cvs.gnome.org/viewcvs/gtk%2B/gtk/gtkdialog.c"; class="urlextern" title="http://cvs.gnome.org/viewcvs/gtk%2B/gtk/gtkdialog.c"; rel="nofollow"> taken from the GtkDialog source</a>).
-</p>
-
-</div>
-<!-- SECTION "Where to place the dialog" [4860-5604] -->
-<h3><a name="placing_dialogs_in_front_of_their_parent_window" id="placing_dialogs_in_front_of_their_parent_window">Placing dialogs in front of their parent window</a></h3>
-<div class="level3">
-
-<p>
-Most of the dialogs are placed in front of their parent window using the transient_for property (see. <a href="http://developer.gnome.org/doc/API/2.0/gtk/GtkWindow.html#gtk-window-set-transient-for"; class="urlextern" title="http://developer.gnome.org/doc/API/2.0/gtk/GtkWindow.html#gtk-window-set-transient-for"; rel="nofollow"> GtkReference</a>). This property should be set for all modal dialogs.
-</p>
-
-<p>
-For nonmodal dialogs the setting of transient_for property is not obvious. While in gschem for example the coord dialog should stay above the parent window, the log window does not need to stay in front of it.
-</p>
-
-<p>
-<strong>Note:</strong> There is an older mechanism that keeps the the dialogs in front of gschem. If the <em>raise-dialog-boxes-on-expose</em> variable is set to <em>enable</em> in one of gschemâ??s configuration files, it may cause problems with some window managers. If dialogs are flickering at 100% CPU load, then disable that setting.
-</p>
-<pre class="code lisp"><span class="co1">; raise-dialog-boxes-on-expose string</span>
-<span class="co1">;</span>
-<span class="co1">; Controls if dialog boxes are raised whenever an expose event happens</span>
-<span class="co1">; Default is enabled</span>
-<span class="co1">;</span>
-<span class="co1">;(raise-dialog-boxes-on-expose "enabled")</span>
-<span class="br0">(</span>raise-dialog-boxes-on-expose <span class="st0">"disabled"</span><span class="br0">)</span></pre>
-</div>
-<!-- SECTION "Placing dialogs in front of their parent window" [5605-6690] -->
-<h3><a name="button_order_in_dialogs" id="button_order_in_dialogs">Button order in dialogs</a></h3>
-<div class="level3">
-
-<p>
- Button order at the bottom of the dialog depends on which operating system the user is using. GTK handles this automatically (require version > 2.6.0) , but requires the developers set the alternative button order. For more information, check the GTK documentation <a href="http://developer.gnome.org/doc/API/2.0/gtk/GtkSettings.html"; class="urlextern" title="http://developer.gnome.org/doc/API/2.0/gtk/GtkSettings.html"; rel="nofollow">here</a>.
-</p>
-
-<p>
-The alternative button order is set with just one call to a GTK function:
-</p>
-<pre class="code C"><span class="co2">#if GTK_CHECK_VERSION (2,6,0)</span>
- <span class="coMULTI">/* Set the alternative button order (ok, cancel, help) for other systems */</span>
- gtk_dialog_set_alternative_button_order<span class="br0">(</span>GTK_DIALOG<span class="br0">(</span>dialog<span class="br0">)</span>,
- GTK_RESPONSE_OK,
- GTK_RESPONSE_NO,
- GTK_RESPONSE_CANCEL,
- GTK_RESPONSE_HELP,
- <span class="nu0">-1</span><span class="br0">)</span>;
-<span class="co2">#endif</span></pre>
-<p>
-This should be done for every new dialog created, before running it.
-</p>
-
-</div>
-<!-- SECTION "Button order in dialogs" [6691-7514] -->
-<h3><a name="dialog_design_of_the_current_dialogs" id="dialog_design_of_the_current_dialogs">Dialog design of the current dialogs</a></h3>
-<div class="level3">
-
-<p>
-<a href="_detail/devel_tips_dialog_picture.html" class="media" title="devel_tips:dialog_picture.png"><img src="_media/devel_tips_dialog_picture.png" class="media" alt="" /></a>
-</p>
-<ul>
-<li class="level1"><div class="li"> There is some space around the whole dialog (<em>DIALOG_BORDER_SPACING</em>). </div>
-</li>
-<li class="level1"><div class="li"> Some indentation to show the topic group (<em>DIALOG_INDENTATION</em>) below itâ??s bold headline.</div>
-</li>
-<li class="level1"><div class="li"> The vertikal and the horizontal separation is done with <em>DIALOG_H_SPACING</em> and <em>DIALOG_V_SPACING</em>.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Dialog design of the current dialogs" [7515-7879] -->
-<h3><a name="source_template_for_simple_dialogs" id="source_template_for_simple_dialogs">Source template for simple dialogs</a></h3>
-<div class="level3">
-
-<p>
-This template is not intented to compile, but you can easily copy the code block that you need.
-</p>
-<pre class="code c"><span class="kw4">void</span> dialog <span class="br0">(</span>TOPLEVEL *w_current<span class="br0">)</span>
-<span class="br0">{</span>
- GtkWidget *vbox, *label, *alignment, *table;
- GtkWidget *dialog;
-
- <span class="coMULTI">/* only create the dialog if it is not there yet. This usually is a
- widget pointer in the w_current structure:
- dialog = w_current->tewindow */</span>
- <span class="kw1">if</span> <span class="br0">(</span>!dialog<span class="br0">)</span> <span class="br0">{</span>
- dialog = gtk_dialog_new_with_buttons<span class="br0">(</span>_<span class="br0">(</span><span class="st0">"Dialog title"</span><span class="br0">)</span>,
- <span class="coMULTI">/* the parent window or NULL */</span>
- GTK_WINDOW<span class="br0">(</span>w_current->main_window<span class="br0">)</span>,
- <span class="coMULTI">/* dialog properties */</span>
- GTK_DIALOG_MODAL, <span class="coMULTI">/* 0 for nonmodal dialogs */</span>
- <span class="coMULTI">/* dialog buttons and response signals */</span>
- GTK_STOCK_CANCEL,
- GTK_RESPONSE_REJECT,
- GTK_STOCK_OK,
- GTK_RESPONSE_ACCEPT,
- <span class="kw2">NULL</span><span class="br0">)</span>;
-
-<span class="co2">#if GTK_CHECK_VERSION (2,6,0)</span>
- <span class="coMULTI">/* Set the alternative button order (ok, cancel, help) for other systems */</span>
- gtk_dialog_set_alternative_button_order<span class="br0">(</span>GTK_DIALOG<span class="br0">(</span>dialog<span class="br0">)</span>,
- GTK_RESPONSE_OK,
- GTK_RESPONSE_NO,
- GTK_RESPONSE_CANCEL,
- GTK_RESPONSE_HELP,
- <span class="nu0">-1</span><span class="br0">)</span>;
-<span class="co2">#endif</span>
-
- <span class="coMULTI">/* set default response signal. This is usually triggered by the
- "Return" key */</span>
- gtk_dialog_set_default_response<span class="br0">(</span>GTK_DIALOG<span class="br0">(</span>dialog<span class="br0">)</span>,
- GTK_RESPONSE_ACCEPT<span class="br0">)</span>;
-
- <span class="coMULTI">/* set the function for handling the button responses and dialog close
- for nonmodal dialogs you can use dialog_run() too.*/</span>
- gtk_signal_connect<span class="br0">(</span>GTK_OBJECT<span class="br0">(</span>dialog<span class="br0">)</span>, <span class="st0">"response"</span>,
- GTK_SIGNAL_FUNC<span class="br0">(</span>dialog_response<span class="br0">)</span>, w_current<span class="br0">)</span>;
-
- <span class="coMULTI">/* where to place the dialog: GTK_WIN_POS_MOUSE or GTK_WIN_POS_NONE */</span>
- gtk_window_position<span class="br0">(</span>GTK_WINDOW <span class="br0">(</span>dialog<span class="br0">)</span>, GTK_WIN_POS_MOUSE<span class="br0">)</span>;
-
- <span class="coMULTI">/* set the border spacing and the vbox spacing of the dialog */</span>
- vbox = GTK_DIALOG<span class="br0">(</span>dialog<span class="br0">)</span>->vbox;
- gtk_container_set_border_width<span class="br0">(</span>GTK_CONTAINER<span class="br0">(</span>dialog<span class="br0">)</span>,DIALOG_BORDER_SPACING<span class="br0">)</span>;
- gtk_box_set_spacing<span class="br0">(</span>GTK_BOX<span class="br0">(</span>vbox<span class="br0">)</span>, DIALOG_V_SPACING<span class="br0">)</span>;
-
- <span class="coMULTI">/* create a label (with markup) and pack it into the dialog box */</span>
- label = gtk_label_new<span class="br0">(</span>_<span class="br0">(</span><span class="st0">"<b>Section label</b>"</span><span class="br0">)</span><span class="br0">)</span>;
- gtk_label_set_use_markup<span class="br0">(</span>GTK_LABEL<span class="br0">(</span>label<span class="br0">)</span>, <span class="kw2">TRUE</span><span class="br0">)</span>;
- gtk_misc_set_alignment<span class="br0">(</span>GTK_MISC<span class="br0">(</span>label<span class="br0">)</span>,<span class="nu0">0</span>,<span class="nu0">0</span><span class="br0">)</span>;
- gtk_box_pack_start<span class="br0">(</span>GTK_BOX<span class="br0">(</span>vbox<span class="br0">)</span>, label, <span class="kw2">FALSE</span>, <span class="kw2">FALSE</span>, <span class="nu0">0</span><span class="br0">)</span>;
-
- <span class="coMULTI">/* create a alignment container with the DIALOG_INDENTATION on the left */</span>
- alignment = gtk_alignment_new<span class="br0">(</span><span class="nu0">0</span>,<span class="nu0">0</span>,<span class="nu0">1</span>,<span class="nu0">1</span><span class="br0">)</span>;
- gtk_alignment_set_padding<span class="br0">(</span>GTK_ALIGNMENT<span class="br0">(</span>alignment<span class="br0">)</span>, <span class="nu0">0</span>, <span class="nu0">0</span>,
- DIALOG_INDENTATION, <span class="nu0">0</span><span class="br0">)</span>;
- gtk_box_pack_start<span class="br0">(</span>GTK_BOX<span class="br0">(</span>vbox<span class="br0">)</span>, alignment, <span class="kw2">FALSE</span>, <span class="kw2">FALSE</span>, <span class="nu0">0</span><span class="br0">)</span>;
-
- <span class="coMULTI">/* a table can store several entries. It is stored in the aligment container.
- Note: the vertical and horizontal cell spacings */</span>
- table = gtk_table_new <span class="br0">(</span><span class="nu0">3</span>, <span class="nu0">2</span>, <span class="kw2">FALSE</span><span class="br0">)</span>;
- gtk_table_set_row_spacings<span class="br0">(</span>GTK_TABLE<span class="br0">(</span>table<span class="br0">)</span>, DIALOG_V_SPACING<span class="br0">)</span>;
- gtk_table_set_col_spacings<span class="br0">(</span>GTK_TABLE<span class="br0">(</span>table<span class="br0">)</span>, DIALOG_H_SPACING<span class="br0">)</span>;
- gtk_container_add<span class="br0">(</span>GTK_CONTAINER<span class="br0">(</span>alignment<span class="br0">)</span>, table<span class="br0">)</span>;
-
- <span class="coMULTI">/* a simple text label in one table cell with left alignment.
- Note: the GTK_FILL in the third line is required */</span>
- label = gtk_label_new<span class="br0">(</span>_<span class="br0">(</span><span class="st0">"Text:"</span><span class="br0">)</span><span class="br0">)</span>;
- gtk_misc_set_alignment<span class="br0">(</span>GTK_MISC<span class="br0">(</span>label<span class="br0">)</span>,<span class="nu0">0</span>,<span class="nu0">0</span><span class="br0">)</span>;
- gtk_table_attach<span class="br0">(</span>GTK_TABLE<span class="br0">(</span>table<span class="br0">)</span>, label, <span class="nu0">0</span>,<span class="nu0">1</span>,<span class="nu0">0</span>,<span class="nu0">1</span>, GTK_FILL,<span class="nu0">0</span>,<span class="nu0">0</span>,<span class="nu0">0</span><span class="br0">)</span>;
-
- <span class="coMULTI">/* a simple text entry completes the option row */</span>
- textentry = gtk_entry_new_with_max_length <span class="br0">(</span><span class="nu0">10</span><span class="br0">)</span>;
- gtk_table_attach_defaults<span class="br0">(</span>GTK_TABLE<span class="br0">(</span>table<span class="br0">)</span>, textentry, <span class="nu0">1</span>,<span class="nu0">2</span>,<span class="nu0">0</span>,<span class="nu0">1</span><span class="br0">)</span>;
- gtk_entry_set_activates_default<span class="br0">(</span>GTK_ENTRY<span class="br0">(</span>textentry<span class="br0">)</span>, <span class="kw2">TRUE</span><span class="br0">)</span>;
-
- <span class="coMULTI">/* ..... more table rows with options, or new sections */</span>
-
- <span class="coMULTI">/* create references to all widgets that you need later */</span>
- GLADE_HOOKUP_OBJECT<span class="br0">(</span>dialog, sizeentry,<span class="st0">"textentry"</span><span class="br0">)</span>;
-
- <span class="coMULTI">/* show all widgets recursivly */</span>
- gtk_widget_show_all<span class="br0">(</span>dialog<span class="br0">)</span>;
- <span class="br0">}</span>
-
- <span class="kw1">else</span> <span class="br0">{</span>
- <span class="coMULTI">/* Dialog is already there. Present it to the user.
- This is only required if you have a nonmodal dialog */</span>
- gtk_window_present<span class="br0">(</span>GTK_WINDOW<span class="br0">(</span>dialog<span class="br0">)</span><span class="br0">)</span>;
- <span class="br0">}</span>
-
- <span class="coMULTI">/* always set the current values to the dialog
- If you're placing that part at the end of the dialog function you can
- easily create dialogs that can be called, even if they are already open */</span>
- textentry = g_object_get_data<span class="br0">(</span>G_OBJECT<span class="br0">(</span>dialog<span class="br0">)</span>, <span class="st0">"textentry"</span><span class="br0">)</span>;
- gtk_entry_set_text<span class="br0">(</span>GTK_ENTRY<span class="br0">(</span>textentry<span class="br0">)</span>, <span class="kw4">string</span><span class="br0">)</span>;
- <span class="coMULTI">/* select the text region that the user usually likes to overwrite */</span>
- gtk_entry_select_region<span class="br0">(</span>GTK_ENTRY<span class="br0">(</span>textentry<span class="br0">)</span>, <span class="nu0">0</span>, strlen<span class="br0">(</span><span class="kw4">string</span><span class="br0">)</span><span class="br0">)</span>;
-<span class="br0">}</span></pre>
-<p>
-The response function for such a dialog may look like this:
-</p>
-<pre class="code c"><span class="kw4">void</span> dialog_response<span class="br0">(</span>GtkWidget *widget, gint response, TOPLEVEL *w_current<span class="br0">)</span>
-<span class="br0">{</span>
- <span class="kw1">switch</span> <span class="br0">(</span>response<span class="br0">)</span> <span class="br0">{</span>
- <span class="kw1">case</span> GTK_RESPONSE_ACCEPT:
- <span class="coMULTI">/* apply the dialog settings:
- just insert your code here if it is short
- call an extra apply function if the required code is long */</span>
- <span class="kw2">break</span>;
- <span class="kw1">case</span> GTK_RESPONSE_REJECT:
- <span class="kw1">case</span> GTK_RESPONSE_DELETE_EVENT:
- <span class="coMULTI">/* for modal dialogs just do nothing,
- for nonmodal dialogs, destroy the dialog and clean up */</span>
- <span class="kw2">break</span>;
- <span class="kw1">default</span>:
- <span class="coMULTI">/* catch wrong signals signals (paranoid error checking ;-)) */</span>
- <a href="http://www.opengroup.org/onlinepubs/009695399/functions/printf.html";><span class="kw3">printf</span></a><span class="br0">(</span><span class="st0">"dialog_response(): strange signal %d<span class="es0">\n</span>"</span>, response<span class="br0">)</span>;
- <span class="br0">}</span>
-
- <span class="coMULTI">/* for nonmodal dialogs just do nothing,
- for modal dialogs, always destroy the dialog and clean up */</span>
-<span class="br0">}</span></pre>
-</div>
-<!-- SECTION "Source template for simple dialogs" [7880-13015] -->
-<h3><a name="current_dialog_issues_in_gschem" id="current_dialog_issues_in_gschem">Current Dialog Issues in Gschem</a></h3>
-<div class="level3">
-<ul>
-<li class="level1"><div class="li"> every dialog has itâ??s own design</div>
-</li>
-<li class="level1"><div class="li"> dialog placement: mouse position or no predefined position?</div>
-</li>
-<li class="level1"><div class="li"> dialogs do not remember their last size, position and contents.</div>
-</li>
-<li class="level1"><div class="li"> missing keyboard shortcuts</div>
-</li>
-</ul>
-
-<p>
- <strong>Hereâ??s a list of things that could be improved:</strong>
-</p>
-
-</div>
-
-<h5><a name="print_dialog" id="print_dialog">Print Dialog</a></h5>
-<div class="level5">
-<ul>
-<li class="level1"><div class="li"> change design?</div>
-</li>
-</ul>
-
-</div>
-
-<h5><a name="write_image" id="write_image">Write Image</a></h5>
-<div class="level5">
-<ul>
-<li class="level1"><div class="li"> In the fileselect dialog the default filename is missing if the file does not exist</div>
-</li>
-<li class="level1"><div class="li"> Return key does not work in the filename entry</div>
-</li>
-</ul>
-
-</div>
-
-<h5><a name="execute_script" id="execute_script">Execute Script</a></h5>
-<div class="level5">
-<ul>
-<li class="level1"><div class="li"> </div>
-</li>
-</ul>
-
-</div>
-
-<h5><a name="edit_text" id="edit_text">Edit Text</a></h5>
-<div class="level5">
-<ul>
-<li class="level1"><div class="li"> some missing keyboard shortcuts</div>
-</li>
-<li class="level1"><div class="li"> add *unmodified* tags if there are multiple selections</div>
-</li>
-<li class="level1"><div class="li"> maybe add some color pixbufs for the color</div>
-</li>
-<li class="level1"><div class="li"> maybe replace the text alignment with nine ratio buttons, toggle buttons with icons or …</div>
-</li>
-</ul>
-
-</div>
-
-<h5><a name="color_dialog" id="color_dialog">Color Dialog</a></h5>
-<div class="level5">
-<ul>
-<li class="level1"><div class="li"> maybe add some color pixbufs for the color</div>
-</li>
-</ul>
-
-</div>
-
-<h5><a name="line_width_and_type" id="line_width_and_type">Line Width and Type</a></h5>
-<div class="level5">
-<ul>
-<li class="level1"><div class="li"> keyboard shortcuts missing</div>
-</li>
-<li class="level1"><div class="li"> icons for the line type</div>
-</li>
-</ul>
-
-</div>
-
-<h5><a name="fill_type" id="fill_type">Fill Type</a></h5>
-<div class="level5">
-<ul>
-<li class="level1"><div class="li"> keyboard shortcuts missing</div>
-</li>
-<li class="level1"><div class="li"> icons in the fill type</div>
-</li>
-</ul>
-
-</div>
-
-<h5><a name="translate_symbol" id="translate_symbol">Translate Symbol</a></h5>
-<div class="level5">
-<ul>
-<li class="level1"><div class="li"> </div>
-</li>
-</ul>
-
-</div>
-
-<h5><a name="page_manager" id="page_manager">Page Manager</a></h5>
-<div class="level5">
-<ul>
-<li class="level1"><div class="li"> wrong button order? Depends on whether you think the refresh button is the main action button or just an extra button.</div>
-</li>
-<li class="level1"><div class="li"> Maybe the â??Returnâ?? key should trigger Refresh</div>
-</li>
-</ul>
-
-</div>
-
-<h5><a name="component_selector" id="component_selector">Component Selector</a></h5>
-<div class="level5">
-<ul>
-<li class="level1"><div class="li"> strange edit widget when typing and the tree is selected (Itâ??s a search helper widget, disable it?!)</div>
-</li>
-</ul>
-
-</div>
-
-<h5><a name="single_attribut_editor" id="single_attribut_editor">Single Attribut Editor</a></h5>
-<div class="level5">
-<ul>
-<li class="level1"><div class="li"> when multiple elements are selected and you call edit (ee) there are a few problems:</div>
-<ul>
-<li class="level3"><div class="li"> if the first object is text, then this dialog is opened (but with the wrong list parameter</div>
-</li>
-<li class="level3"><div class="li"> if the first object is complex then the multiple attribute editor is called</div>
-</li>
-</ul>
-</li>
-</ul>
-
-</div>
-
-<h5><a name="multi_attribute_editor" id="multi_attribute_editor">Multi Attribute Editor</a></h5>
-<div class="level5">
-<ul>
-<li class="level1"><div class="li"> </div>
-</li>
-</ul>
-
-</div>
-
-<h5><a name="add_text" id="add_text">Add Text</a></h5>
-<div class="level5">
-<ul>
-<li class="level1"><div class="li"> </div>
-</li>
-</ul>
-
-</div>
-
-<h5><a name="arc_params" id="arc_params">Arc Params</a></h5>
-<div class="level5">
-<ul>
-<li class="level1"><div class="li"> add the diameter to the dialog, but select the start angle entry (increment = grid)</div>
-</li>
-<li class="level1"><div class="li"> let â??eeâ?? call that dialog if only a single arc is selected</div>
-</li>
-<li class="level1"><div class="li"> maybe add a section label</div>
-</li>
-</ul>
-
-</div>
-
-<h5><a name="insert_picture" id="insert_picture">Insert Picture</a></h5>
-<div class="level5">
-<ul>
-<li class="level1"><div class="li"> </div>
-</li>
-</ul>
-
-</div>
-
-<h5><a name="picture_replace" id="picture_replace">Picture Replace</a></h5>
-<div class="level5">
-<ul>
-<li class="level1"><div class="li"> the new picture uses the aspect ratio of the old picture</div>
-</li>
-<li class="level1"><div class="li"> the dialog has lots in common with the Insert Picture dialog. They could use some code together</div>
-</li>
-</ul>
-
-</div>
-
-<h5><a name="find_text" id="find_text">Find Text</a></h5>
-<div class="level5">
-<ul>
-<li class="level1"><div class="li"> manipulates the mouse pointer (maybe the zooming code is the culprit). Just press â??Returnâ?? to trigger a FindNext</div>
-</li>
-<li class="level1"><div class="li"> if you select hierarchy and the found text is in a different schematic, then the filename in the title is not updated</div>
-</li>
-<li class="level1"><div class="li"> maybe add an option: â??Select all matching text objectsâ??, disable hierarchy for that feature!</div>
-</li>
-<li class="level1"><div class="li"> <img src="lib/images/smileys/fixme.gif" class="middle" alt="FIXME" /> gschem hangs if you use that dialog with hierarchical schematics that have dependancy loops (e.g. the autonumber test schematics)</div>
-</li>
-<li class="level1"><div class="li"> add an option â??search for visible text onlyâ??</div>
-</li>
-<li class="level1"><div class="li"> maybe use regular expressions instead of the substring for the searchtext</div>
-</li>
-</ul>
-
-</div>
-
-<h5><a name="hide_text" id="hide_text">Hide Text</a></h5>
-<div class="level5">
-<ul>
-<li class="level1"><div class="li"> use regular expressions instead of starting substring</div>
-</li>
-</ul>
-
-</div>
-
-<h5><a name="show_text" id="show_text">Show Text</a></h5>
-<div class="level5">
-<ul>
-<li class="level1"><div class="li"> use regular expressions instead of starting substring</div>
-</li>
-<li class="level1"><div class="li"> Maybe merge that dialog together with the â??Hide Textâ?? dialog</div>
-</li>
-</ul>
-
-</div>
-
-<h5><a name="autonumber_text" id="autonumber_text">Autonumber Text</a></h5>
-<div class="level5">
-<ul>
-<li class="level1"><div class="li"> Maybe disable the skip option if the renumber scope is â??selectionâ??. The other skip options (Page and Hierarchy) are really stupid.</div>
-</li>
-</ul>
-
-</div>
-
-<h5><a name="text_size" id="text_size">Text Size</a></h5>
-<div class="level5">
-<ul>
-<li class="level1"><div class="li"> </div>
-</li>
-</ul>
-
-</div>
-
-<h5><a name="snap_grid_spacing" id="snap_grid_spacing">Snap Grid Spacing</a></h5>
-<div class="level5">
-<ul>
-<li class="level1"><div class="li"> </div>
-</li>
-</ul>
-
-</div>
-
-<h5><a name="coord_dialog" id="coord_dialog">Coord Dialog</a></h5>
-<div class="level5">
-<ul>
-<li class="level1"><div class="li"> maybe move the world coordinates to the main window status bar</div>
-</li>
-</ul>
-
-</div>
-
-<h5><a name="about_dialog" id="about_dialog">About Dialog</a></h5>
-<div class="level5">
-<ul>
-<li class="level1"><div class="li"> </div>
-</li>
-</ul>
-
-</div>
-
-<h5><a name="hotkeys" id="hotkeys">Hotkeys</a></h5>
-<div class="level5">
-<ul>
-<li class="level1"><div class="li"> </div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Current Dialog Issues in Gschem" [13016-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/geda_documentation.html b/docs/wiki/geda_documentation.html
deleted file mode 100644
index b57af4c..0000000
--- a/docs/wiki/geda_documentation.html
+++ /dev/null
@@ -1,405 +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>geda:documentation</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2008-04-02T11:01:51-0400" />
-<meta name="keywords" content="geda,documentation" />
-<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/geda:documentation?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:documentation"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:documentation"; />
-<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="#geda_tool_suite_on-line_documentation" class="toc">gEDA Tool Suite on-line documentation</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#tutorials" class="toc">Tutorials</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#gschem_-_schematic_capture" class="toc">gschem - Schematic Capture</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#gnetlist_-_netlister" class="toc">gnetlist - Netlister</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#gsymcheck_-_symbol_checker" class="toc">gsymcheck - Symbol Checker</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#utils_-_geda_utilities" class="toc">utils - gEDA Utilities</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#examples" class="toc">Examples</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#attribute_file_format_details" class="toc">Attribute/File Format Details</a></span></div></li>
-</ul>
-</li>
-<li class="level1"><div class="li"><span class="li"><a href="#spice" class="toc">SPICE</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#ngspice" class="toc">ngspice</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#gnucap" class="toc">gnucap</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#gspiceui" class="toc">gSpiceUI</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#pcb" class="toc">PCB</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#gerbv" class="toc">gerbv</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#icarus_verilog" class="toc">Icarus Verilog</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#gtkwave" class="toc">GTKWave</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#wcalc" class="toc">Wcalc</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#mcalc" class="toc">mcalc</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#covered" class="toc">covered</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#for_document_authors" class="toc">For document authors</a></span></div></li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="geda_tool_suite_on-line_documentation" id="geda_tool_suite_on-line_documentation">gEDA Tool Suite on-line documentation</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "gEDA Tool Suite on-line documentation" [1-60] -->
-<h2><a name="tutorials" id="tutorials">Tutorials</a></h2>
-<div class="level2">
-<ul>
-<li class="level1"><div class="li"> <a href="geda_gsch2pcb_tutorial.html" class="wikilink1" title="geda:gsch2pcb_tutorial">gschem to pcb tutorial </a> Read This First!</div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_gschem_warmup.html" class="wikilink1" title="geda:gschem_warmup">gschem warmup</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_transistor_guide.html" class="wikilink1" title="geda:transistor_guide">gschem Symbol and PCB Element Transistor Guide</a></div>
-</li>
-</ul>
-
-<p>
- All of these tutorials were written by Bill Wilson (many thanks)!
-</p>
-<ul>
-<li class="level1"><div class="li"> <a href="geda_ngspice_and_gschem.html" class="wikilink1" title="geda:ngspice_and_gschem">ngspice and gschem</a></div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Tutorials" [61-372] -->
-<h2><a name="gschem_-_schematic_capture" id="gschem_-_schematic_capture">gschem - Schematic Capture</a></h2>
-<div class="level2">
-<ul>
-<li class="level1"><div class="li"> <a href="geda_gschem_ug.html" class="wikilink1" title="geda:gschem_ug">gschem User's Guide</a> – also in transition, please comment</div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_gschem_mp.html" class="wikilink1" title="geda:gschem_mp">gschem man-page</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_scg.html" class="wikilink1" title="geda:scg">Symbol Creation Guide</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_hse_howto.html" class="wikilink1" title="geda:hse_howto">Hooks/Scheme Extension HOWTO</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_kig_howto.html" class="wikilink1" title="geda:kig_howto">Keymapping in gschem HOWTO</a></div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "gschem - Schematic Capture" [373-673] -->
-<h2><a name="gnetlist_-_netlister" id="gnetlist_-_netlister">gnetlist - Netlister</a></h2>
-<div class="level2">
-<ul>
-<li class="level1"><div class="li"> <a href="geda_gnetlist_ug.html" class="wikilink1" title="geda:gnetlist_ug">gnetlist User's Guide</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_gnetlist_mp.html" class="wikilink1" title="geda:gnetlist_mp">gnetlist man-page</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_sdb_howto.html" class="wikilink1" title="geda:sdb_howto">Spice netlisting (SDB) HOWTO</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_na_howto.html" class="wikilink1" title="geda:na_howto">net= attribute mini-HOWTO</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_ssan.html" class="wikilink1" title="geda:ssan">Switcap Symbols and Netlister</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_sn_readme.html" class="wikilink1" title="geda:sn_readme">Switcap netlister README</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_fbabgapp.html" class="wikilink1" title="geda:fbabgapp">Forward/Backward Annotation Between gEDA and Pads PowerPCB</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_grcsan.html" class="wikilink1" title="geda:grcsan">gEDA RF Cascade Symbols and Netlister</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_bom_readme.html" class="wikilink1" title="geda:bom_readme">Bill of Material netlister README</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_gschem2pcb_readme.html" class="wikilink1" title="geda:gschem2pcb_readme">gschem2pcb README</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_verilog_netlister_readme.html" class="wikilink1" title="geda:verilog_netlister_readme">Verilog netlister README</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_vhdl_netlister_readme.html" class="wikilink1" title="geda:vhdl_netlister_readme">VHDL netlister README</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_vams_netlister_readme.html" class="wikilink1" title="geda:vams_netlister_readme">VAMS netlister README</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_systemc_netlister_readme.html" class="wikilink1" title="geda:systemc_netlister_readme">SystemC netlister README</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_eagle_pcb_netlister_readme.html" class="wikilink1" title="geda:eagle_pcb_netlister_readme">Eagle PCB netlister README</a></div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "gnetlist - Netlister" [674-1546] -->
-<h2><a name="gsymcheck_-_symbol_checker" id="gsymcheck_-_symbol_checker">gsymcheck - Symbol Checker</a></h2>
-<div class="level2">
-<ul>
-<li class="level1"><div class="li"> <a href="geda_gsymcheck_mp.html" class="wikilink1" title="geda:gsymcheck_mp">gsymcheck man-page</a></div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "gsymcheck - Symbol Checker" [1547-1632] -->
-<h2><a name="utils_-_geda_utilities" id="utils_-_geda_utilities">utils - gEDA Utilities</a></h2>
-<div class="level2">
-<ul>
-<li class="level1"><div class="li"> <a href="geda_gsch2pcb_readme.html" class="wikilink1" title="geda:gsch2pcb_readme">gsch2pcb (gschem to PCB) README</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_gsch2pcb_tutorial.html" class="wikilink1" title="geda:gsch2pcb_tutorial">gsch2pcb tutorial</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_tragesym_readme.html" class="wikilink1" title="geda:tragesym_readme">tragesym (symbol generator) README</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_tragesym_tutorial.html" class="wikilink1" title="geda:tragesym_tutorial">tragesym Tutorial</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_olib_readme.html" class="wikilink1" title="geda:olib_readme">olib (OrCAD (TM) converter) README</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_grenum_mp.html" class="wikilink1" title="geda:grenum_mp">grenum man-page</a> – note</div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_gattrib_readme.html" class="wikilink1" title="geda:gattrib_readme">gattrib README</a> – note</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "utils - gEDA Utilities" [1633-2049] -->
-<h2><a name="examples" id="examples">Examples</a></h2>
-<div class="level2">
-<ul>
-<li class="level1"><div class="li"> <a href="geda_example_hsm.html" class="wikilink1" title="geda:example_hsm">Hierarchical SPICE model</a> – note</div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_example_usbjtag.html" class="wikilink1" title="geda:example_usbjtag">Example USB-based JTAG interface</a> – note</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Examples" [2050-2199] -->
-<h2><a name="attribute_file_format_details" id="attribute_file_format_details">Attribute/File Format Details</a></h2>
-<div class="level2">
-<ul>
-<li class="level1"><div class="li"> <a href="geda_master_attributes_list.html" class="wikilink1" title="geda:master_attributes_list">Master Attributes List</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_file_format_spec.html" class="wikilink1" title="geda:file_format_spec">sym/sch File Format Specification</a></div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Attribute/File Format Details" [2200-2365] -->
-<h1><a name="spice" id="spice">SPICE</a></h1>
-<div class="level1">
-<ul>
-<li class="level1"><div class="li"> <a href="http://www.geda.seul.org/tools/gnucap/papers/al-davis-dissertation.pdf"; class="urlextern" title="http://www.geda.seul.org/tools/gnucap/papers/al-davis-dissertation.pdf"; rel="nofollow">Implicit Mixed-Mode Simulation of VLSI Circuits</a> by Albert Tatum Davis (1991)<br/>
- Please report if this <acronym title="Uniform Resource Locator">URL</acronym> goes dead.</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://www.brorson.com/gEDA/SPICE/intro.html"; class="urlextern" title="http://www.brorson.com/gEDA/SPICE/intro.html"; rel="nofollow">Circuit Simulation using gEDA and SPICE - HOWTO</a> (<acronym title="HyperText Markup Language">HTML</acronym> version)<br/>
- by Stuart Brorson (20 December 2004).<br/>
- Please report if this <acronym title="Uniform Resource Locator">URL</acronym> is not the latest version.</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://www.brorson.com/gEDA/HOWTO/gEDA_Spice_HOWTO-20050103.pdf"; class="urlextern" title="http://www.brorson.com/gEDA/HOWTO/gEDA_Spice_HOWTO-20050103.pdf"; rel="nofollow">Circuit Simulation using gEDA and SPICE - HOWTO</a> (<acronym title="Portable Document Format">PDF</acronym> version)<br/>
- by Stuart Brorson ( 5 January 2005).</div>
-</li>
-</ul>
-
-<p>
- Testing:
-</p>
-<ul>
-<li class="level1"><div class="li"> <a href="geda_csygas.html" class="wikilink1" title="geda:csygas">Circuit Simulation using gEDA and SPICE - HOWTO</a> – Done converting. Please comment on this conversion to a wiki-format.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "SPICE" [2366-3115] -->
-<h1><a name="ngspice" id="ngspice">ngspice</a></h1>
-<div class="level1">
-<ul>
-<li class="level1"><div class="li"> <a href="http://www-ti.informatik.uni-tuebingen.de/~bernauer/lehre/ti-1-0506/spice/ngspice.pdf"; class="urlextern" title="http://www-ti.informatik.uni-tuebingen.de/~bernauer/lehre/ti-1-0506/spice/ngspice.pdf"; rel="nofollow">NGSPICE User Manual</a> – describes ngspice-rework-17, Draft Version 0.2<br/>
- Please report if this <acronym title="Uniform Resource Locator">URL</acronym> is not the appropriated version, or if it goes dead.</div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_ngspice_mp.html" class="wikilink1" title="geda:ngspice_mp">ngspice man-page</a> – note</div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_ngnutmeg_mp.html" class="wikilink1" title="geda:ngnutmeg_mp">ngnutmeg man-page</a> – note</div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_ngsconvert_mp.html" class="wikilink1" title="geda:ngsconvert_mp">ngsconvert man-page</a> – note</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "ngspice" [3116-3538] -->
-<h1><a name="gnucap" id="gnucap">gnucap</a></h1>
-<div class="level1">
-<ul>
-<li class="level1"><div class="li"> <a href="http://www.geda.seul.org/tools/gnucap/gnucap-man.pdf"; class="urlextern" title="http://www.geda.seul.org/tools/gnucap/gnucap-man.pdf"; rel="nofollow">The Gnu Circuit Analysis Package Users manual</a> – January 21,2004 version</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://www.geda.seul.org/tools/gnucap/papers/gnucap-model-compiler.pdf"; class="urlextern" title="http://www.geda.seul.org/tools/gnucap/papers/gnucap-model-compiler.pdf"; rel="nofollow">The Gnucap Model Compiler</a></div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "gnucap" [3539-3799] -->
-<h1><a name="gspiceui" id="gspiceui">gSpiceUI</a></h1>
-<div class="level1">
-<ul>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/shared/gEDA-20060124/Documents/gSpiceUI/gSpiceUI.html"; class="urlextern" title="file:///shared/gEDA-20060124/Documents/gSpiceUI/gSpiceUI.html" rel="nofollow">GNU Spice GUI</a></div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "gSpiceUI" [3800-3907] -->
-<h1><a name="pcb" id="pcb">PCB</a></h1>
-<div class="level1">
-<ul>
-<li class="level1"><div class="li"> The pcb <acronym title="Frequently Asked Questions">FAQ</acronym>: <a href="geda_faq-pcb.html" class="wikilink1" title="geda:faq-pcb">faq-pcb</a></div>
-</li>
-<li class="level1"><div class="li"> The official <a href="http://pcb.sourceforge.net/manual.html"; class="urlextern" title="http://pcb.sourceforge.net/manual.html"; rel="nofollow">manual of pcb</a></div>
-</li>
-<li class="level1"><div class="li"> A very detailed <a href="http://www.brorson.com/gEDA/land_patterns_20070818.pdf"; class="urlextern" title="http://www.brorson.com/gEDA/land_patterns_20070818.pdf"; rel="nofollow">manual on footprint creation</a> by Stephen Meier and Stuart Brorson. It also covers most of the syntax of the *.pcb format. The document refers to the 2007 version of pcb.</div>
-</li>
-<li class="level1"><div class="li"> The <a href="geda_pcb_mp.html" class="wikilink1" title="geda:pcb_mp">man-page of pcb</a></div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "PCB" [3908-4317] -->
-<h1><a name="gerbv" id="gerbv">gerbv</a></h1>
-<div class="level1">
-<ul>
-<li class="level1"><div class="li"> <a href="geda_gerbv_mp.html" class="wikilink1" title="geda:gerbv_mp">gerbv man-page</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_gerbv_pnp_readme.html" class="wikilink1" title="geda:gerbv_pnp_readme">Searching for Parts and marking them on screen (in gerbv)</a></div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "gerbv" [4318-4463] -->
-<h1><a name="icarus_verilog" id="icarus_verilog">Icarus Verilog</a></h1>
-<div class="level1">
-<ul>
-<li class="level1"><div class="li"> <a href="geda_icarus_quick_start.html" class="wikilink1" title="geda:icarus_quick_start">Getting Started with Icarus Verilog</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://www.rowetel.com/blog/?p=13"; class="urlextern" title="http://www.rowetel.com/blog/?p=13"; rel="nofollow">Icarus Verilog Mini How To</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_icarus_mp.html" class="wikilink1" title="geda:icarus_mp">Icarus Verilog compiler man-page</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_icarus_vpi_mp.html" class="wikilink1" title="geda:icarus_vpi_mp">Compile front end for VPI modules man-page</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_icarus_vvp_runtime.html" class="wikilink1" title="geda:icarus_vvp_runtime">Icarus Verilog vvp runtime engine man-page</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_icarus_readme.html" class="wikilink1" title="geda:icarus_readme">The Icarus Verilog Compilation System</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_igarus_fpga_lcg.html" class="wikilink1" title="geda:igarus_fpga_lcg">FPGA Loadable Code Generator for Icarus Verilog</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_icarus_xilinx_hints.html" class="wikilink1" title="geda:icarus_xilinx_hints">Xilinx Hints</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_icarus_xnf.html" class="wikilink1" title="geda:icarus_xnf">Xilinx Netlist Format</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_icarus_ieee1364.html" class="wikilink1" title="geda:icarus_ieee1364">Icarus Verilog vs. IEEE1364</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_icarus_anc.html" class="wikilink1" title="geda:icarus_anc">Icarus Attribute Naming Conventions</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_icarus_extensions.html" class="wikilink1" title="geda:icarus_extensions">Icarus Verilog Extensions</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_icarus_glossary.html" class="wikilink1" title="geda:icarus_glossary">Icarus Verilog Glossary</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_icarus_opcodes.html" class="wikilink1" title="geda:icarus_opcodes">Executable Instruction Opcodes</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_icarus_vpi_within_vvp.html" class="wikilink1" title="geda:icarus_vpi_within_vvp">VPI_within_VVP</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_icarus_vvp_simulation.html" class="wikilink1" title="geda:icarus_vvp_simulation">VVP Simulation Engine</a></div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Icarus Verilog" [4464-5458] -->
-<h1><a name="gtkwave" id="gtkwave">GTKWave</a></h1>
-<div class="level1">
-<ul>
-<li class="level1"><div class="li"> <a href="http://home.nc.rr.com/gtkwave/"; class="urlextern" title="http://home.nc.rr.com/gtkwave/"; rel="nofollow">Welcome to GTKWave</a> – Now for version 3.0 (the promoted version 1.3)</div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_gtkwave_mp.html" class="wikilink1" title="geda:gtkwave_mp">Visualization tool for VCD, LXT, and VZT files (gtkwave)</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_gtkwave_lxt2miner_mp.html" class="wikilink1" title="geda:gtkwave_lxt2miner_mp">Data mining of LXT2 files (lxt2miner)</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_gtkwave_lxt2vcd_mp.html" class="wikilink1" title="geda:gtkwave_lxt2vcd_mp">Coverts LXT2 files to VCD (lxt2vcd)</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_gtkwave_mvl2lxt_mp.html" class="wikilink1" title="geda:gtkwave_mvl2lxt_mp">Coverts MVLSIM AET files to LXT (mvl2lxt)</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_gtkwave_mvl2vcd_mp.html" class="wikilink1" title="geda:gtkwave_mvl2vcd_mp">Coverts MVLSIM AET files to VCD (mvl2vcd)</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_gtkwave_tex2vcd_mp.html" class="wikilink1" title="geda:gtkwave_tex2vcd_mp">Coverts TEXSIM AET files to VCD (tex2vcd)</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_gtkwave_tla2vcd_mp.html" class="wikilink1" title="geda:gtkwave_tla2vcd_mp">Converts TLA to VCD or LST files (tla2vcd)</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_gtkwave_vcd2lxt_mp.html" class="wikilink1" title="geda:gtkwave_vcd2lxt_mp">Converts VCD files to interlaced or linear LXT files (vcd2lxt)</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_gtkwave_vcd2lxt2_mp.html" class="wikilink1" title="geda:gtkwave_vcd2lxt2_mp">Converts VCD files to LXT2 files (vcd2lxt2)</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_gtkwave_vcd2vzt_mp.html" class="wikilink1" title="geda:gtkwave_vcd2vzt_mp">Converts VCD files to VZT files
- (vcd2vzt)</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_gtkwave_vzt2vcd_mp.html" class="wikilink1" title="geda:gtkwave_vzt2vcd_mp">Coverts VZT files to VCD (vzt2vcd)</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_gtkwave_vztminer_mp.html" class="wikilink1" title="geda:gtkwave_vztminer_mp">Data mining of VZT files (vztminer)</a></div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "GTKWave" [5459-6490] -->
-<h1><a name="wcalc" id="wcalc">Wcalc</a></h1>
-<div class="level1">
-<ul>
-<li class="level1"><div class="li"> <a href="geda_wcalc_readme.html" class="wikilink1" title="geda:wcalc_readme">Wcalc README</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_wcalc_mp.html" class="wikilink1" title="geda:wcalc_mp">Wcalc man-page</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_wcalc_stdio_mp.html" class="wikilink1" title="geda:wcalc_stdio_mp">stdio Wcalc man-page</a></div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Wcalc" [6491-6637] -->
-<h1><a name="mcalc" id="mcalc">mcalc</a></h1>
-<div class="level1">
-<ul>
-<li class="level1"><div class="li"> <a href="http://mcalc.sourceforge.net/"; class="urlextern" title="http://mcalc.sourceforge.net/"; rel="nofollow">Microstrip Analysis/Synthesis Calculator</a> – latest documentation from sourceforge</div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_mcalc_readme.html" class="wikilink1" title="geda:mcalc_readme">mcalc README</a></div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "mcalc" [6638-6817] -->
-<h1><a name="covered" id="covered">covered</a></h1>
-<div class="level1">
-<ul>
-<li class="level1"><div class="li"> <a href="http://covered.sourceforge.net/user/index.html"; class="urlextern" title="http://covered.sourceforge.net/user/index.html"; rel="nofollow">covered User Manual</a> – link to latest covered documentation on sourceforge</div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_covered_rv.html" class="wikilink2" title="geda:covered_rv">covered Report Viewer</a> – available in the Help menu of the <acronym title="Graphical User Interface">GUI</acronym> report utility</div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_covered_mp.html" class="wikilink1" title="geda:covered_mp">covered man-page</a></div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "covered" [6818-7115] -->
-<h1><a name="for_document_authors" id="for_document_authors">For document authors</a></h1>
-<div class="level1">
-
-<p>
-New features are available for document authors:
-</p>
-<ul>
-<li class="level1"><div class="li"> <a href="geda_syntax_features.html" class="wikilink1" title="geda:syntax_features">Syntax features</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_installed_plugins.html" class="wikilink1" title="geda:installed_plugins">Installed plugins</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_style_guide.html" class="wikilink1" title="geda:style_guide">Style Guide</a> – A work in progress, please contribute</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "For document authors" [7116-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/geda_eagle_pcb_netlister_readme.html b/docs/wiki/geda_eagle_pcb_netlister_readme.html
deleted file mode 100644
index fdf9c19..0000000
--- a/docs/wiki/geda_eagle_pcb_netlister_readme.html
+++ /dev/null
@@ -1,55 +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>geda:eagle_pcb_netlister_readme</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="geda,eagle_pcb_netlister_readme" />
-<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/geda:eagle_pcb_netlister_readme?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:eagle_pcb_netlister_readme"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:eagle_pcb_netlister_readme"; />
-<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">
-
-
-
-<h1><a name="eagle_pcb_netlister_readme" id="eagle_pcb_netlister_readme">Eagle PCB netlister README</a></h1>
-<div class="level1">
-<pre class="code">Basic information about the Eagle PCB backend and sch2eaglepos.sh
-
-gnet-eagle.scm
-
-The script uses the component's package, footprint, value, and (if no
-value) device attributes, as well as the netlist, to generate an Eagle
-script that will add and connect all components. It also introduces a
-"lib" attribute, which specifies the Eagle library where the footprint
-can be found...if a "lib" attribute is not set for a component, then
-the library defaults to "smd-ipc" (the default Eagle surface mount library).
-
-sch2eaglepos.sh
-
-I am also including a simple shell script that I wrote which has saved
-me hours by extracting the relative locations of the parts from a
-gschem schematic, and generating an Eagle script to place the
-components in the same relative locations on the layout. By default
-all packages are piled on top of each other, and with a large design
-it takes a long time to sort out which cap bypasses which IC, etc.
-
-</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_example_hsm.html b/docs/wiki/geda_example_hsm.html
deleted file mode 100644
index 1fb1dec..0000000
--- a/docs/wiki/geda_example_hsm.html
+++ /dev/null
@@ -1,147 +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>geda:example_hsm</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="keywords" content="geda,example_hsm" />
-<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/geda:example_hsm?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:example_hsm"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:example_hsm"; />
-<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">
-
-
-
-<h1><a name="hierarchical_spice_model" id="hierarchical_spice_model">Hierarchical SPICE model</a></h1>
-<div class="level1">
-
-<p>
-If you installed the gEDA Tool Suite from the distribution CD-ROM, then you should have this example of a hierarchical analog RF SPICE model in the:<br/>
- <strong><code>{source_install_path}geda-sources/gedagaf/geda-examples-20060123/RF_Amp</code></strong> <br/>
- directory.
-</p>
-<pre class="code">This README created 3.31.2003
-
---------------------- Contents of directories -----------------------
-
-This directory holds the schematics and associated materials for a
-SPICE model of Agilent's MSA-2643 bipolar amp. The model was obtained
-from Agilent's datasheet 5980-2396E. The directory structure is as
-follows:
-
-RF_Amp (base directory)
-
-MSA-2643.sch -- schematic of stuff inside device package (as shown in
-p. 7 of datasheet. Note that I have not included the transmission
-lines in this schematic because no value of Z was included in the data
-sheet. (Yes, it's probably 50 ohms, but including them was a
-sideshow compared to my main intent: build a hierarchical model of an
-RF circuit.)
-MSA-2643.cir -- netlisted circuit ready for SPICE simulation.
-
-Q1.sch -- schematic model of Q1 MSA-26 transistor shown on p. 8 of datasheet.
-Q1.cir -- netlisted circuit holding .SUBCKT model of Q1.
-
-Q2.sch -- schematic model of Q2 MSA-26 transistor shown on p. 8 of datasheet.
-Q2.cir -- netlisted circuit holding .SUBCKT model of Q2.
-
-README -- this file.
-
-Simulation.cmd -- a file holding SPICE analysis commands which is read
-at simulation time by the SPICE simulator.
-
-5980-2396E.pdf -- Agilent datasheet about the MSA-2643.
-
-
-./model/
-
-BJTM1_Q1.mod -- text-based SPICE model of BJT1 used in Q1 .SUBCKT
-DiodeM1_Q1.mod -- text-based SPICE model of diode M1 used in Q1 .SUBCKT
-DiodeM2_Q1.mod -- SPICE model of diode M2 used in Q1 .SUBCKT
-DiodeM3_Q1.mod -- SPICE model of diode M3 used in Q1 .SUBCKT
-(similar files for Q2 models. . . .)
-These models were obtained from parameters give in p. 8 of the datasheet.
-
-./sym/
-
-BJT_Model.sym
-spice-subcircuit-IO-1.sym
-spice-subcircuit-LL-1.sym
-Q_Model.sym -- symbol pointing to lower level models placed on upper
-level schematic.
-
------------- Usage of hierarchical spice models ---------------------
-This project exemplifies construction of a hierarchical SPICE
-simulation using gEDA. The project is built in the following way:
-
-1. Use a text editor to create .mod files containing SPICE models of
-the transistors and diodes on p. 8 of the datasheet.
-
-2. Create Q1 and Q2 transistor model schematics using gschem. Place
-the .SUBCKT SPICE block on the schematic to alert the netlister that
-the schematic is a lower level .SUBCKT for incorporation into other
-schematics. Place spice-IO pads on the schematic to instantiate the
-IOs. Make sure to number the spice-IO pads in the same order as you
-wish them to appear in the .SUBCKT line in the .cir.
-
-3. Generate the .SUBCKT netlist by saying:
-
-gnetlist -g spice-sdb -o Q1.cir Q1.sch
-gnetlist -g spice-sdb -o Q2.cir Q2.sch
-
-4. Create a symbol for Q1.cir and Q2.cir which will be dropped onto
-the higher lever schematic. Name the symbol Q_Model.sym. Set the
-symbol "DEVICE" attribute = NPN_TRANSISTOR_subcircuit. This causes
-the netlister to use "write-default-component" to write out the SPICE
-line for the component. Make sure that the "REFDES" attribute is X?
-and not Q? -- this enables the .SUBCKT file to be attached to the
-device.
-
-5. Create the higher layer schematic MSA-2643.sch. Place
-two copies of Q_Model.sym onto the schematic, corresponding to Q1 and
-Q2. Make Q1 point to its model by setting the following attributes:
-
-model-name: Q1_MSA26F
-file: Q1.cir
-
-Do the same for Q2.
-
-6. Create the rest of the higher layer schematic the usual way. Make
-sure to place a spice-include block on the schematic and point it to
-"Simulation.cmd". Place any analysis commands (e.g. .DC, .AC, .TRAN,
-etc.) into the file "Simulation.cmd".
-
-7. Netlist the higher layer design:
-
-gnetlist -g spice-sdb -o MSA-2643.cir MSA-2643.sch
-
-8. The circuit may be simulated by any desired SPICE simulation
-and analysis package, e.g. LTSpice.
-
--------------------- Contact ----------------------------
-Documentation and other materials relevant to SPICE simulation under
-gEDA lives at http://www.brorson.com/gEDA/SPICE
-
-For inquiries or bug reports, please contact me:
-
-Stuart Brorson
-mailto:sdb@xxxxxxxxxx
-</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_example_usbjtag.html b/docs/wiki/geda_example_usbjtag.html
deleted file mode 100644
index f0a413a..0000000
--- a/docs/wiki/geda_example_usbjtag.html
+++ /dev/null
@@ -1,88 +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>geda:example_usbjtag</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="keywords" content="geda,example_usbjtag" />
-<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/geda:example_usbjtag?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:example_usbjtag"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:example_usbjtag"; />
-<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">
-
-
-
-<h1><a name="example_usb-based_jtag_interface" id="example_usb-based_jtag_interface">Example USB-based JTAG interface</a></h1>
-<div class="level1">
-
-<p>
-If you installed the gEDA Tool Suite from the distribution CD-ROM, then you should have this example of a USB-based JTAG interface in the:<br/>
- <strong><code>{source-code_installation_path}geda-sources/gedagaf/geda-examples-20060123/gTAG</code></strong> <br/>
- directory.
-</p>
-<pre class="code"> gTAG - USB to JTAG interface
- ============================
-
-This is the README file for the schematic of gTAG.
-
-Short description
------------------
-gTAG is an interface to connect your USB port of computer to talk
-to your circuits which talks JTAG.
-
-Copyright
----------
-These schematics is (C) by Stefan Petersen (spe@xxxxxxxxxxxxxx) and
-released under GPL (see the attached file COPYING). GPL is mainly
-written for software, ie intellectual property in electronic form.
-By making this schematic an intellectual property in electronic
-form gTAG schematics can be covered by GPL.
-
-How?
-----
-These schematics are made with gschem and netlists are then generated
-with gnetlist. Both gschem and gnetlist are part of gEDA
-(http://www.geda.seul.org/).
-
-Files
------
-The distribution of the schematics of gTAG should consist of:
-* README - this file.
-* COPYING - GPL copyright notice.
-* crdist.sh - shell script used to generate the tar.gz.
-* ChangeLog - tries to scribble down what has changed between versions.
-* Four component symbols:
- - 7414-1.sym - Original 7414 from gschem without power attributes.
- - max882.sym - 5-to-3.3 V converter.
- - cy7c64603-52nc.sym - USB microcontroller from Cypress.
- - sn75240pw.sym - Surge supressor for USB
- - copyleft.sym - Symbol with GPL text for all schematics.
-* Five schematics with four symbols:
- - gTAG.sch.sch - Toplevel schematic for gTAG
- - gTAG-jtagio.[sym/sch]
- - gTAG-ucont.[sym/sch]
- - gTAG-consio.[sym/sch]
- - gTAG-psu.[sym/sch]
-* gEDA rc-files for this project:
- - commonrc - contains common declarations for both gschem and gnetlist
- - gnetlistrc - gnetlist specific and and calls commonrc
- - gschemrc - gschem specific and and calls commonrc
-</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_faq-attribs.html b/docs/wiki/geda_faq-attribs.html
deleted file mode 100644
index 7cf0591..0000000
--- a/docs/wiki/geda_faq-attribs.html
+++ /dev/null
@@ -1,251 +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>geda:faq-attribs</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2008-01-25T11:56:58-0500" />
-<meta name="keywords" content="geda,faq-attribs" />
-<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/geda:faq-attribs?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:faq-attribs"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:faq-attribs"; />
-<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="#bom_generation" class="toc">BOM generation</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#i_have_created_a_new_design._how_do_i_create_a_bom" class="toc">I have created a new design. How do I create a BOM?</a></span></div></li>
-</ul>
-</li>
-<li class="level1"><div class="li"><span class="li"><a href="#drcs" class="toc">DRCs</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_check_my_schematics" class="toc">How do I check my schematics?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_see_the_drc_output_in_the_screen_without_writing_to_a_file" class="toc">How do I see the DRC output in the screen, without writing to a file?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#i_want_to_disable_some_of_the_schematic_drc_checks._how_can_i_do_it" class="toc">I want to disable some of the schematic DRC checks. How can I do it?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#can_i_include_the_drc_checking_into_a_makefile_and_stop_when_errors_or_warnings_are_found" class="toc">Can I include the DRC checking into a Makefile and stop when errors or warnings are found?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#there_are_some_warnings_in_my_design_i_m_aware_of._can_i_ignore_the_warnings_in_the_return_value" class="toc">There are some warnings in my design I'm aware of. Can I ignore the warnings in the return value?</a></span></div></li>
-</ul>
-</li>
-<li class="level1"><div class="li"><span class="li"><a href="#attribute_management" class="toc">Attribute management</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#help_my_design_has_hundreds_of_components_and_it_s_a_pain_to_use_gschem_to_attach_all_my_attributes" class="toc">Help! My design has hundreds of components, and it's a pain to use gschem to attach all my attributes!</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_know_what_footprint_name_to_use_for_layout_using_pcb" class="toc">How do I know what footprint name to use for layout using PCB?</a></span></div></li></ul>
-</li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="bom_generation" id="bom_generation">BOM generation</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "BOM generation" [1-31] -->
-<h2><a name="i_have_created_a_new_design._how_do_i_create_a_bom" id="i_have_created_a_new_design._how_do_i_create_a_bom">I have created a new design. How do I create a BOM?</a></h2>
-<div class="level2">
-
-<p>
-There are as many ways to export a BOM from your design as there are gEDA developers. Indeed, there are five or six different backends for gnetlist which enable you to export a BOM. Therefore, itâ??s easy for the newbie to be confused about which approach to use. A good, simple, and reasonably complete method is this:
-</p>
-<ul>
-<li class="level1"><div class="li"> Create a file called â??attribsâ?? in your project directory. In this file, place each attrib whose value you wish to export on a separate line. You donâ??t need to include refdes. This is the one attribute which is assumed to exist for every component. Hereâ??s an example attribs file:<pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">value
-Mfr
-Mfr_PN
-Vendor
-Vendor_PN</font></pre></div>
-</li>
-<li class="level1"><div class="li"> Netlist your design using the following command:<br/>
- <br/>
- <code>gnetlist -v -g bom2 -o MyDesign.bom MyDesign.sch</code> <br/>
- <br/>
- Note that the <strong><code>-v</code></strong> flag will provide a verbose spew telling you what is going in gnetlist while it is running. This can be useful if you need to diagnose a problem with netlisting.</div>
-</li>
-<li class="level1"><div class="li"> With this command, gnetlist will dump a BOM into the file â??MyDesign.bomâ??. The BOM items will be separated using a â??:â?? (colon) character. Components with the same value are collected into a single line. You may then read this file into any spreadsheet program. Make sure to import the BOM as a .csv file, and specify the â??:â?? character as the item separator.</div>
-</li>
-</ul>
-
-<p>
- Many other methods to create BOMs exist. Perhaps other geda-users will post their favorite methods here?!?!?
-</p>
-
-</div>
-<!-- SECTION "I have created a new design. How do I create a BOM?" [32-1541] -->
-<h1><a name="drcs" id="drcs">DRCs</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "DRCs" [1542-1560] -->
-<h2><a name="how_do_i_check_my_schematics" id="how_do_i_check_my_schematics">How do I check my schematics?</a></h2>
-<div class="level2">
-
-<p>
-You can check your schematics using the drc2 gnetlistâ??s backend. It will check your schematics for some common errors, like duplicate references, unconnected pins, unused slots and more.
-</p>
-
-<p>
-Run the drc2 backend with the following command:
-</p>
-<pre class="code">gnetlist -g drc2 -o MyDesign.drc MyDesign.sch</pre>
-
-<p>
-With this command, the DRC output is written into the file â??MyDesign.drcâ??. You can then view this file with a text editor and see the DRC warnings and errors.
-</p>
-
-</div>
-<!-- SECTION "How do I check my schematics?" [1561-2065] -->
-<h2><a name="how_do_i_see_the_drc_output_in_the_screen_without_writing_to_a_file" id="how_do_i_see_the_drc_output_in_the_screen_without_writing_to_a_file">How do I see the DRC output in the screen, without writing to a file?</a></h2>
-<div class="level2">
-
-<p>
-Run the drc2 backend with the following command:
-</p>
-<pre class="code">gnetlist -g drc2 -o - MyDesign.sch</pre>
-
-<p>
-This way, you will see the DRC output directly in your screen.
-</p>
-
-</div>
-<!-- SECTION "How do I see the DRC output in the screen, without writing to a file?" [2066-2309] -->
-<h2><a name="i_want_to_disable_some_of_the_schematic_drc_checks._how_can_i_do_it" id="i_want_to_disable_some_of_the_schematic_drc_checks._how_can_i_do_it">I want to disable some of the schematic DRC checks. How can I do it?</a></h2>
-<div class="level2">
-
-<p>
-The drc2 backend is highly configurable. You have to put some special commands into a file and use the â??-lâ?? option of gnetlist with it.
-</p>
-
-<p>
-The most common commands are:
-</p>
-<ul>
-<li class="level1"><div class="li"> (define dont-check-non-numbered-parts 1) ;; Disable the non-numbered parts check</div>
-</li>
-<li class="level1"><div class="li"> (define dont-check-duplicated-references 1) ;; Disable the duplicate references check</div>
-</li>
-<li class="level1"><div class="li"> (define dont-check-one-connection-nets 1) ;; Disable the check for nets with only one connection.</div>
-</li>
-<li class="level1"><div class="li"> (define dont-check-pintypes-of-nets 1) ;; Disable the pintype check</div>
-</li>
-<li class="level1"><div class="li"> (define dont-check-not-driven-nets 1) ;; Disable the driven net check</div>
-</li>
-<li class="level1"><div class="li"> (define dont-check-unconnected-pins 1) ;; Disable the unconnected pins check</div>
-</li>
-<li class="level1"><div class="li"> (define dont-check-duplicated-slots 1) ;; Disable the duplicated slots check</div>
-</li>
-<li class="level1"><div class="li"> (define dont-check-unused-slots 1) ;; Disable the unused slots check</div>
-</li>
-<li class="level1"><div class="li"> (define dont-check-slots 1) ;; Disable slot number check</div>
-</li>
-<li class="level1"><div class="li"> (define action-unused-slots #\w) ;; Output an unused slots as a warning</div>
-</li>
-<li class="level1"><div class="li"> (define action-unused-slots #\e) ;; Output an unused slots as an error</div>
-</li>
-<li class="level1"><div class="li"> (define action-unused-slots #\c) ;; An unused slot is OK.</div>
-</li>
-<li class="level1"><div class="li"> (define case_insensitive 1) ;; Do all checks case insensitive</div>
-</li>
-</ul>
-
-<p>
- There are some other advanced commands, to modify the DRC matrix and the pintype which can drive a net. See the backend file â??gnet-drc2.scmâ?? with a text editor. At the beginning there is the available documentation.
-</p>
-
-<p>
-Copy the above lines you want into a file (for example â??drc_rules.txtâ??), one per line, and run the drc checker:
-</p>
-<pre class="code">gnetlist -g drc2 -l drc_rules.txt -o MyDesign.drc MyDesign.sch</pre>
-
-<p>
-With this command, the DRC output is written into the file â??MyDesign.drcâ??. You can then view this file with a text editor and see the DRC warnings and errors.
-</p>
-
-</div>
-<!-- SECTION "I want to disable some of the schematic DRC checks. How can I do it?" [2310-4138] -->
-<h2><a name="can_i_include_the_drc_checking_into_a_makefile_and_stop_when_errors_or_warnings_are_found" id="can_i_include_the_drc_checking_into_a_makefile_and_stop_when_errors_or_warnings_are_found">Can I include the DRC checking into a Makefile and stop when errors or warnings are found?</a></h2>
-<div class="level2">
-
-<p>
-Yes. The drc2 backend will return an error if there are errors or warnings, so you can add the following to your Makefile:
-</p>
-<pre class="code">$(objects).drc : $(objects).sch
- gnetlist -g drc2 $(objects).sch -o $(objects).drc</pre>
-
-<p>
-If you are going to simulate your design, then you can add the following to your Makefile:
-</p>
-<pre class="code">$(objects).cir : $(objects).sch $(objects).drc
- grep -v ERROR $(objects).drc >/dev/null 2>&1
- gnetlist -g spice-sdb $(objects).sch -o $(objects).cir</pre>
-
-<p>
-If not, please use the above example and adapt it to your own workflow.
-</p>
-
-</div>
-<!-- SECTION "Can I include the DRC checking into a Makefile and stop when errors or warnings are found?" [4139-4816] -->
-<h2><a name="there_are_some_warnings_in_my_design_i_m_aware_of._can_i_ignore_the_warnings_in_the_return_value" id="there_are_some_warnings_in_my_design_i_m_aware_of._can_i_ignore_the_warnings_in_the_return_value">There are some warnings in my design I'm aware of. Can I ignore the warnings in the return value?</a></h2>
-<div class="level2">
-
-<p>
-Use the â??-O ignore-warnings-in-return-valueâ?? option:
-</p>
-<pre class="code">gnetlist -g drc2 -o - MyDesign.sch -O ignore-warnings-in-return-value</pre>
-
-<p>
-Do this with caution! You will be missing all the warnings!
-</p>
-
-</div>
-<!-- SECTION "There are some warnings in my design I'm aware of. Can I ignore the warnings in the return value?" [4817-5128] -->
-<h1><a name="attribute_management" id="attribute_management">Attribute management</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "Attribute management" [5129-5164] -->
-<h2><a name="help_my_design_has_hundreds_of_components_and_it_s_a_pain_to_use_gschem_to_attach_all_my_attributes" id="help_my_design_has_hundreds_of_components_and_it_s_a_pain_to_use_gschem_to_attach_all_my_attributes">Help! My design has hundreds of components, and it's a pain to use gschem to attach all my attributes!</a></h2>
-<div class="level2">
-
-<p>
-The answer here is the gEDA/gaf utility â??gattribâ??. Gattrib is an attribute editor for gEDA. It reads your .sch file(s) and creates a spreadsheet showing all components, nets, and pins in rows, with the associated attributes listed in the columns. Gattrib allows you to add, modify, or delete attributes outside of gschem, and then save the .sch files back out. Hereâ??s a screenshot:
-</p>
-
-<p>
-<a href="_detail/geda_faq_attrib.html" class="media" title="geda:faq_attrib.jpg"><img src="_media/geda_faq_attrib.jpg" class="media" title="faq_attrib.jpg" alt="faq_attrib.jpg" /></a>
-</p>
-
-<p>
-Note that gattrib is the gEDA Projectâ??s current answer to the question of heavy symbols. That is, rather than putting all attributes (such as SPICE model files, footprint names, manufacturer part nos and the like), you are encouraged to put this information into your schematic using gattrib, where it is visible and easily manipulable with gattrib.
-</p>
-
-<p>
-When using gattrib, make sure you exit gschem first. Gattrib and gschem both save your work into the same file, so you should have only one program running at a time to avoid conflicts. There is no lockfile mechanism in gEDA/gaf (yet), so itâ??s your responsibility to avoid conflicts.
-</p>
-
-</div>
-<!-- SECTION "Help! My design has hundreds of components, and it's a pain to use gschem to attach all my attributes!" [5165-6334] -->
-<h2><a name="how_do_i_know_what_footprint_name_to_use_for_layout_using_pcb" id="how_do_i_know_what_footprint_name_to_use_for_layout_using_pcb">How do I know what footprint name to use for layout using PCB?</a></h2>
-<div class="level2">
-
-<p>
-<a href="geda_pcb_tips.html" class="wikilink1" title="geda:pcb_tips">Answered here</a>.
-</p>
-
-</div>
-<!-- SECTION "How do I know what footprint name to use for layout using PCB?" [6335-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/geda_faq-gnetlist.html b/docs/wiki/geda_faq-gnetlist.html
deleted file mode 100644
index 21c6240..0000000
--- a/docs/wiki/geda_faq-gnetlist.html
+++ /dev/null
@@ -1,155 +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>geda:faq-gnetlist</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2008-05-27T00:44:25-0400" />
-<meta name="keywords" content="geda,faq-gnetlist" />
-<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/geda:faq-gnetlist?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:faq-gnetlist"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:faq-gnetlist"; />
-<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="#gnetlist_build_run-time_problems" class="toc">Gnetlist build/run-time problems</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#i_get_a_parenthesis_mismatch_error_when_running_gnetlist._what_s_up" class="toc">I get a "parenthesis mismatch" error when running gnetlist. What's up?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#the_gnetlist_bom_backend_does_not_work._what_is_wrong" class="toc">The gnetlist bom backend does not work. What is wrong?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#some_gnetlist_backends_overflow_the_stack._how_do_i_solve_this" class="toc">Some gnetlist backends overflow the stack. How do I solve this?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#gnetlist_has_created_a_netlist_with_duplicate_pins" class="toc">gnetlist has created a netlist with duplicate pins!?</a></span></div></li></ul>
-</li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="gnetlist_build_run-time_problems" id="gnetlist_build_run-time_problems">Gnetlist build/run-time problems</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "Gnetlist build/run-time problems" [1-48] -->
-<h2><a name="i_get_a_parenthesis_mismatch_error_when_running_gnetlist._what_s_up" id="i_get_a_parenthesis_mismatch_error_when_running_gnetlist._what_s_up">I get a "parenthesis mismatch" error when running gnetlist. What's up?</a></h2>
-<div class="level2">
-
-<p>
- Starting with Fedorea Core 6 and SuSE 10.2, many users have reported an error which looks like this:
-</p>
-<pre class="code">
-$gnetlist -g spice-sdb -o TwoStageAmp.cir TwoStageAmp.sch
-Command line passed = gnetlist -g spice-sdb -o TwoStageAmp.cir TwoStageAmp.sch
-gEDA/gnetlist version 20061020
-gEDA/gnetlist comes with ABSOLUTELY NO WARRANTY; see COPYING for more details.
-This is free software, and you are welcome to redistribute it under certain
-conditions; please see the COPYING file for more details.
-
-Remember to check that your schematic has no errors using the drc2 backend.
-You can do it running 'gnetlist -g drc2 your_schematic.sch -o drc_output.txt'
-and seeing the contents of the file drc_output.txt.
-
-Loading schematic [/home/nano/TwoStageAmp/TwoStageAmp.sch]
-Probably parenthesis mismatch in /usr/share/gEDA/scheme/gnet-spice-sdb.scm
-Most recently read form: (#@begin #<unspecified>)
-ERROR: Unbound variable: spice-sdb
-</pre>
-
-<p>
-Several gnetlist backends evince this problem, including spice-sdb and drc2.
-</p>
-
-<p>
-This is a bug in guile-1.8.X. The gEDA developers are working on a fix. Meanwhile, try to backrev your version of guile to 1.6.7, which is known to work flawlessly with gEDA.
-</p>
-
-</div>
-<!-- SECTION "I get a parenthesis mismatch error when running gnetlist. What's up?" [49-1315] -->
-<h2><a name="the_gnetlist_bom_backend_does_not_work._what_is_wrong" id="the_gnetlist_bom_backend_does_not_work._what_is_wrong">The gnetlist bom backend does not work. What is wrong?</a></h2>
-<div class="level2">
-
-<p>
-If when running gnetlist like this:
-</p>
-<pre class="code">gnetlist -g bom filename.sch</pre>
-
-<p>
-and gnetlist outputs an error message like:
-</p>
-<pre class="code">Loading schematic [filename.sch]
-ERROR: In procedure open-file:
-ERROR: No such file or directory: â??attribsâ??</pre>
-
-<p>
-then you need to create a file called â??attribsâ?? in the current directory which contains the attributes which you want inside the bom file. An example of this file would be: <pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">device
-value</font></pre>
-</p>
-
-<p>
-For information about BOM generation see the <a href="http://geda.seul.org/wiki/geda:faq-attribs#bom_generation"; class="wikilink1" title="geda:faq-attribs">FAQ-attribs</a>.
-</p>
-
-</div>
-<!-- SECTION "The gnetlist bom backend does not work. What is wrong?" [1316-1932] -->
-<h2><a name="some_gnetlist_backends_overflow_the_stack._how_do_i_solve_this" id="some_gnetlist_backends_overflow_the_stack._how_do_i_solve_this">Some gnetlist backends overflow the stack. How do I solve this?</a></h2>
-<div class="level2">
-
-<p>
-If you get an error message like:
-</p>
-<pre class="code">ERROR: Stack overflow</pre>
-
-<p>
-when running certain larger sized schematics through some of the backends, then add the following to a <strong><code>~/.gEDA/gnetlistrc</code></strong> or a local <strong><code>gnetlistrc</code></strong> (in the current working directory):
-</p>
-<pre class="code">(debug-options (list 'stack 200000))
-(eval-options (list 'stack 200000))</pre>
-
-<p>
-If this does not work, then edit the appropriate backend (usually named: gnet-backend_name.scm) and put the above lines at the top of this file. The gnetlist backends can be found in <strong><code>${prefix}/share/gEDA/scheme</code></strong>. Also send an e-mail to geda-dev reminding the developers to fix this. Remember, you must subscribe to geda-dev before you post to the geda-dev e-mail list.
-</p>
-
-</div>
-<!-- SECTION "Some gnetlist backends overflow the stack. How do I solve this?" [1933-2738] -->
-<h2><a name="gnetlist_has_created_a_netlist_with_duplicate_pins" id="gnetlist_has_created_a_netlist_with_duplicate_pins">gnetlist has created a netlist with duplicate pins!?</a></h2>
-<div class="level2">
-
-<p>
-There has been at least one report of the following message coming from PCB after loading up a netlist created by gnetlist:
-</p>
-<pre class="code">28: Error! Element R117 pin 2 appears multiple times in the netlist file.
-29: Error! Element C167 pin 2 appears multiple times in the netlist file.</pre>
-
-<p>
-What has happened is gnetlist (really libgeda) created two nets instead of one. This happens when you draw two nets that cross each other and a pin connecting to the intersection of the two crossing nets. Note the cross nets are not connected together. A schematic which demonstrates this looks like this:
-</p>
-
-<p>
-<a href="_detail/geda_ambiguous1.html" class="media" title="geda:ambiguous1.png"><img src="_media/geda_ambiguous1.png" class="media" alt="" /></a>
-</p>
-
-<p>
-The developers are debating whether or not this is a bug in gnetlist, but for now make sure your net connections, especially those that involve pins connecting to the middle of other nets, are explicitly drawn. Here is how the above connection should be drawn to netlist properly:
-</p>
-
-<p>
-<a href="_detail/geda_ambiguous1_fixed.html" class="media" title="geda:ambiguous1_fixed.png"><img src="_media/geda_ambiguous1_fixed.png" class="media" alt="" /></a>
-</p>
-
-</div>
-<!-- SECTION "gnetlist has created a netlist with duplicate pins!?" [2739-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/geda_faq-gsch2pcb.html b/docs/wiki/geda_faq-gsch2pcb.html
deleted file mode 100644
index 6e6b12a..0000000
--- a/docs/wiki/geda_faq-gsch2pcb.html
+++ /dev/null
@@ -1,117 +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>geda:faq-gsch2pcb</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-10-17T12:54:25-0400" />
-<meta name="keywords" content="geda,faq-gsch2pcb" />
-<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/geda:faq-gsch2pcb?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:faq-gsch2pcb"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:faq-gsch2pcb"; />
-<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="#gsch2pcb" class="toc">gsch2pcb</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#where_is_the_gsch2pcb_tutorial" class="toc">Where is the gsch2pcb tutorial?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#where_can_i_download_gsch2pcb" class="toc">Where can I download gsch2pcb?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#gsch2pcb_can_t_find_some_of_my_footprints_or_errors_out._what_can_i_do_to_diagnose_my_problem" class="toc">gsch2pcb can't find some of my footprints, or errors out. What can I do to diagnose my problem?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#i_don_t_like_the_default_layer_stack_of_gschem2pcb._how_can_i_change_this" class="toc">I don't like the default layer stack of gschem2pcb. How can I change this?</a></span></div></li></ul>
-</li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="gsch2pcb" id="gsch2pcb">gsch2pcb</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "gsch2pcb" [1-24] -->
-<h2><a name="where_is_the_gsch2pcb_tutorial" id="where_is_the_gsch2pcb_tutorial">Where is the gsch2pcb tutorial?</a></h2>
-<div class="level2">
-
-<p>
-Currently, the best information about how to get started with gsch2pcb is contained in Bill Wilsonâ??s outstanding <a href="geda_gsch2pcb_tutorial.html" class="wikilink1" title="geda:gsch2pcb_tutorial">tutorial</a>.
-</p>
-
-<p>
-There is a wrapper script for gsch2pcb called sch2pcb. Read about it in the <a href="geda_pcb_tips.html" class="wikilink1" title="geda:pcb_tips">pcb_tips</a> section of this wiki.
-</p>
-
-</div>
-<!-- SECTION "Where is the gsch2pcb tutorial?" [25-335] -->
-<h2><a name="where_can_i_download_gsch2pcb" id="where_can_i_download_gsch2pcb">Where can I download gsch2pcb?</a></h2>
-<div class="level2">
-
-<p>
-gsch2pcb is part of gEDA/gaf, in the utils. It is normally installed by default (along with everything else) if you install the entirety of gEDA/gaf. If you donâ??t have it installed on your machine for some reason you can either download the utils tarball from:
-</p>
-<ul>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/download.html"; class="urlextern" title="http://geda.seul.org/download.html"; rel="nofollow">http://geda.seul.org/download.html</a></div>
-</li>
-</ul>
-
-<p>
- or grab it directly from <acronym title="Concurrent Versions System">CVS</acronym> at:
-</p>
-<ul>
-<li class="level1"><div class="li"> <a href="http://cvs.seul.org/viewcvs/viewcvs.cgi/eda/geda/gaf/utils/src/"; class="urlextern" title="http://cvs.seul.org/viewcvs/viewcvs.cgi/eda/geda/gaf/utils/src/"; rel="nofollow">http://cvs.seul.org/viewcvs/viewcvs.cgi/eda/geda/gaf/utils/src/</a></div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Where can I download gsch2pcb?" [336-791] -->
-<h2><a name="gsch2pcb_can_t_find_some_of_my_footprints_or_errors_out._what_can_i_do_to_diagnose_my_problem" id="gsch2pcb_can_t_find_some_of_my_footprints_or_errors_out._what_can_i_do_to_diagnose_my_problem">gsch2pcb can't find some of my footprints, or errors out. What can I do to diagnose my problem?</a></h2>
-<div class="level2">
-
-<p>
-Try running gsch2pcb in double verbose mode: â??gsch2pcb -v -vâ??. This will produce lots of spew telling you where gsch2pcb is looking while it tries to find footprints. It will also tell you where it does find the footprints it uses.
-</p>
-
-</div>
-<!-- SECTION "gsch2pcb can't find some of my footprints, or errors out. What can I do to diagnose my problem?" [792-1136] -->
-<h2><a name="i_don_t_like_the_default_layer_stack_of_gschem2pcb._how_can_i_change_this" id="i_don_t_like_the_default_layer_stack_of_gschem2pcb._how_can_i_change_this">I don't like the default layer stack of gschem2pcb. How can I change this?</a></h2>
-<div class="level2">
-
-<p>
-Edit $INSTALLDIR/share/gEDA/schemegnet-gsch2pcb.scm to reflect your preferred layer stack. In particular you may have to modify the line that defines the layer groups:
-</p>
-<pre class="code"> (display "Groups(\"1,2,3,s:4,5,6,c:7:8\")\n" port) </pre>
-
-<p>
- and the layer stack itself:
-</p>
-<pre class="code">(lambda (port)
- (display "Layer(1 \"bottom\")\n(\n)\n" port)
- (display "Layer(2 \"bott.-poly.\")\n(\n)\n" port)
- ...
- (display "Layer(8 \"lineout\")\n(\n)" port)
- (display "Layer(9 \"ignored\")\n(\n)\n" port)
- (display "Layer(10 \"ignored\")\n(\n)" port)
- (newline port)))</pre>
-
-<p>
- Note, the last two layers will map to silk on both sides of the board. So you will have to define two more layers than you want for your copper layout.
-</p>
-
-</div>
-<!-- SECTION "I don't like the default layer stack of gschem2pcb. How can I change this?" [1137-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/geda_faq-gschem.html b/docs/wiki/geda_faq-gschem.html
deleted file mode 100644
index 23fe257..0000000
--- a/docs/wiki/geda_faq-gschem.html
+++ /dev/null
@@ -1,932 +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>geda:faq-gschem</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2008-02-13T07:21:54-0500" />
-<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/"; />
-<link rel="contents" href="http://geda.seul.org/wiki/geda:faq-gschem?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:faq-gschem"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:faq-gschem"; />
-<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="#general" class="toc">General</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#i_found_a_bug_what_can_i_do_about_it" class="toc">I found a bug! What can I do about it?</a></span></div></li>
-</ul>
-</li>
-<li class="level1"><div class="li"><span class="li"><a href="#gschem_usage" class="toc">Gschem usage</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_move_a_component" class="toc">How do I move a component?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_move_components_without_dragging_a_tail_of_connectet_nets" class="toc">How do I move components without dragging a tail of connectet nets?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_change_the_size_of_the_text_on_a_symbol" class="toc">How do I change the size of the text on a symbol?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_unlock_a_locked_component" class="toc">How do I unlock a locked component</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#how_can_i_get_refdes_automatically_numbered_when_i_draw_a_schematic" class="toc">How can I get refdes automatically numbered when I draw a schematic?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#what_is_a_bus_and_how_do_i_use_it" class="toc">What is a Bus and how do I use it?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#how_can_i_change_key_bindings_in_gschem" class="toc">How can I change Key Bindings in gschem?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#what_are_the_mouse_bindings_in_gschem" class="toc">What are the mouse bindings in gschem?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#can_gschem_do_hierarchical_designs_with_sub_sheets" class="toc">Can gschem do hierarchical designs with sub sheets?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#can_gschem_do_a_hierarchy_where_the_top-level_symbol_points_to_a_multi-page_schematic" class="toc">Can gschem do a hierarchy where the top-level symbol points to a multi-page schematic?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#can_the_hierarchy_be_setup_in_multiple_directories" class="toc">Can the hierarchy be setup in multiple directories?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#how_can_options_and_libraries_be_specific_on_subsheet_level" class="toc">How can options and libraries be specific on subsheet level?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#are_there_limitations_to_hierarchy_design" class="toc">Are there limitations to hierarchy design?</a></span></div></li>
-</ul>
-</li>
-<li class="level1"><div class="li"><span class="li"><a href="#gschem_symbols" class="toc">gschem symbols</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#where_do_i_find_symbols_beyond_the_default_library" class="toc">Where do I find symbols beyond the default library?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#what_s_this_business_about_heavy_vs._light_symbols" class="toc">What's this business about heavy vs. light symbols?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#i_am_using_a_symbol_out_of_the_library._how_come_it_s_not_aligned_to_the_grid" class="toc">I am using a symbol out of the library. How come it's not aligned to the grid?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#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" class="toc">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></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_promote_an_invisible_symbol_attribute_into_the_schematic" class="toc">How do I promote an invisible symbol attribute into the schematic?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#what_should_i_do_about_power_pins_on_my_symbolsmake_them_visible_explicit_or_invisible_implicit" class="toc">What should I do about power pins on my symbols: Make them visible (explicit) or invisible (implicit)?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#is_there_a_specification_or_manual_for_creating_gschem_symbols_where_is_it" class="toc">Is there a specification or manual for creating gschem symbols? Where is it?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#can_my_local_library_cover_frequently_needed_sub_circuits" class="toc">Can my local library cover frequently needed sub circuits?</a></span></div></li>
-</ul>
-</li>
-<li class="level1"><div class="li"><span class="li"><a href="#gschem_configuration_customization" class="toc">Gschem configuration/customization</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_configure_my_local_gafrc_to_find_my_local_symbol_directory" class="toc">How do I configure my local gafrc to find my local symbol directory?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#can_gafrc_use_a_variable_to_set_the_root_of_my_library" class="toc">Can gafrc use a variable to set the root of my library?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#the_library_window_is_cluttered_with_default_symbols._can_i_restrict_to_my_local_lib" class="toc">The library window is cluttered with default symbols. Can I restrict to my local lib?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#how_can_i_change_the_default_size_of_floating_text" class="toc">How can I change the default size of floating text?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#how_can_i_have_a_different_background_color_other_than_black" class="toc">How can I have a different background color other than black?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#each_time_i_start_gschem_the_log_message_window_is_shown._can_i_disable_it" class="toc">Each time I start gschem, the log message window is shown. Can I disable it?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#can_i_get_a_customized_title_block_with_new_schematics" class="toc">Can I get a customized title block with new schematics?</a></span></div></li>
-</ul>
-</li>
-<li class="level1"><div class="li"><span class="li"><a href="#printing_output" class="toc">Printing/Output</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_print_schematics_from_the_command_line" class="toc">How do I print schematics from the command line?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#how_can_i_get_color_postscript_png_output" class="toc">How can I get color postscript/PNG output?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#how_can_i_get_black_and_white_postscript_png_output" class="toc">How can I get black and white postscript/PNG output?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#how_can_i_insert_schematics_into_my_latex_document" class="toc">How can I insert schematics into my LaTex document?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#how_can_i_split_postscript_output_over_multiple_pages" class="toc">How can I split Postscript output over multiple pages?</a></span></div></li>
-</ul>
-</li>
-<li class="level1"><div class="li"><span class="li"><a href="#gschem_installation_run-time_problems" class="toc">Gschem installation/run-time problems</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#gschem_segfaults_when_i_delete_components_on_fc5_and_other_linux_distributions_is_there_a_work-around" class="toc">Gschem segfaults when I delete components on FC5 (and other Linux distributions)! Is there a work-around?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#after_installation_gschem_does_not_work_what_could_be_wrong" class="toc">After installation gschem does not work!? What could be wrong?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#add_components_offers_no_symbols_what_can_i_do_about_it" class="toc">"Add Components" offers no symbols! What can I do about it?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#i_m_using_gschem_gaf_through_a_ssh_connection_and_i_get_an_error_likexlibextension_render_missing_on_display_localhost10.0" class="toc">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></span></div></li></ul>
-</li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="general" id="general">General</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "General" [1-24] -->
-<h2><a name="i_found_a_bug_what_can_i_do_about_it" id="i_found_a_bug_what_can_i_do_about_it">I found a bug! What can I do about it?</a></h2>
-<div class="level2">
-<ol>
-<li class="level1"><div class="li"> See if you can reproduce the bug.</div>
-</li>
-<li class="level1"><div class="li"> Ask on the <a href="http://www.geda.seul.org/mailinglist/index.html"; class="urlextern" title="http://www.geda.seul.org/mailinglist/index.html"; rel="nofollow">geda-user mailing</a> list if there is a work around, or has been dealt with in the bleeding edge version of gEDA/gaf. Note, that you must subscribe to the geda-user e-mail list before you can post to this list.</div>
-</li>
-<li class="level1"><div class="li"> See whether the issue is already in the <a href="http://sourceforge.net/tracker/?group_id=161080&atid=818426"; class="urlextern" title="http://sourceforge.net/tracker/?group_id=161080&atid=818426"; rel="nofollow">bug tracking system of geda/gaf</a>. If not, file a bug report. Make sure to give all information necessary to reproduce the bug and add the version of gEDA/gaf that contains the bug.</div>
-</li>
-<li class="level1"><div class="li"> Finally, as with all open source projects, you may flex your programming muscles and try to fix the bug yourself. Please file a patch of the changes you had to make to the BTS of geda/gaf. The patch will be gladly accepted to improve the next release of gEDA/gaf.</div>
-</li>
-</ol>
-
-</div>
-<!-- SECTION "I found a bug! What can I do about it?" [25-946] -->
-<h1><a name="gschem_usage" id="gschem_usage">Gschem usage</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "Gschem usage" [947-974] -->
-<h2><a name="how_do_i_move_a_component" id="how_do_i_move_a_component">How do I move a component?</a></h2>
-<div class="level2">
-
-<p>
- 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>
-</li>
-<li class="level1"><div class="li"> Drag the component (using the left mouse button) to the place you want it.</div>
-</li>
-</ol>
-
-<p>
- This is probably what you are already used to doing.
-</p>
-
-<p>
-For folks with older versions of gschem, here are three ways to move components within gschem:
-</p>
-
-<p>
-One:
-</p>
-<ol>
-<li class="level1"><div class="li"> Grab the component with the middle mouse button. The component will follow the cursor around as you move it.</div>
-</li>
-<li class="level1"><div class="li"> To place the component, release the middle mouse button. The component will stay where you placed it.</div>
-</li>
-</ol>
-
-<p>
- Two:
-</p>
-<ol>
-<li class="level1"><div class="li"> Select the component by clicking it with the left mouse button. The component will highlight.</div>
-</li>
-<li class="level1"><div class="li"> Hit the â??Mâ?? key on the keyboard. The component will now follow the cursor around as you move it.</div>
-</li>
-<li class="level1"><div class="li"> To place the component, click the left mouse button. The component will stay where you placed it.</div>
-</li>
-</ol>
-
-<p>
- Three:
-</p>
-<ol>
-<li class="level1"><div class="li"> Select the component by clicking it with the left mouse button. The component will highlight.</div>
-</li>
-<li class="level1"><div class="li"> Click the right mouse button. A pop-up menu will appear.</div>
-</li>
-<li class="level1"><div class="li"> With the left mouse button, click on the â??moveâ?? option in the pop-up menu.</div>
-</li>
-<li class="level1"><div class="li"> Click on the component with the left mouse button. The component will now follow the cursor around as you move it.</div>
-</li>
-<li class="level1"><div class="li"> To place the component, click the left mouse button. The component will stay where you placed it.</div>
-</li>
-</ol>
-
-</div>
-<!-- SECTION "How do I move a component?" [975-2409] -->
-<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">
-
-<p>
-Type [or] to toggle this behaviour. That is, the â??oâ?? key followed by the â??râ?? key. The status window will report if the toggle command was performed. The command can also be accessed via the Options menu.
-</p>
-
-</div>
-<!-- SECTION "How do I move components without dragging a tail of connectet nets?" [2410-2694] -->
-<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>
-<li class="level1"><div class="li"> Select the symbol.</div>
-</li>
-<li class="level1"><div class="li"> Right click â?? down symbol (or do Hierarchy â?? down symbol). This takes you to the symbol editor.</div>
-</li>
-<li class="level1"><div class="li"> Select the pinnumber you want to change.</div>
-</li>
-<li class="level1"><div class="li"> Do Edit â?? Edit Text (or type keyboard shortcut â??exâ??).</div>
-</li>
-<li class="level1"><div class="li"> Change the font size in the pop-up box.</div>
-</li>
-<li class="level1"><div class="li"> Repeat for all desired text elements.</div>
-</li>
-<li class="level1"><div class="li"> File â?? save</div>
-</li>
-<li class="level1"><div class="li"> Right click â?? up (or Hierarchy â?? Up). Now you are back in the schematic editor.</div>
-</li>
-<li class="level1"><div class="li"> With the symbol still selected do Edit â?? Update component (or use the keyboard shortcut â??epâ??). If this doesnâ??t work, just delete the symbol and reload it.</div>
-</li>
-</ol>
-
-<p>
- More generally, you can use this procedure to edit anything on a symbol. (Substitute â??Edit Textâ?? for your desired edit, of course.)
-</p>
-
-</div>
-<!-- SECTION "How do I change the size of the text on a symbol?" [2695-3485] -->
-<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">
-
-<p>
-When a component is locked it cannot be selected with the middle mouse button; however it is selectable using a window select. To window select a component, click and hold the left mouse button and drag the mouse to create a rectangular region containing the component to be unlocked. Execute the command <strong><em>Edit</em></strong> <strong>â??</strong> <strong><em>unLock</em></strong> to unlock the component.
-</p>
-
-</div>
-<!-- SECTION "How do I unlock a locked component" [3486-3900] -->
-<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">
-
-<p>
-Edit the system-gschemrc file or place the following into a gschemrc file (either <strong><code>~/.gEDA/gschemrc</code></strong> or a <strong><code>gschemrc</code></strong> file in the local directory where you invoke gschem):
-</p>
-<pre class="code">
-(load (string-append gedadata "/scheme/auto-uref.scm")) ; load the autonumbering script
-(add-hook! add-component-hook auto-uref) ; autonumber when adding a component
-(add-hook! copy-component-hook auto-uref) ; autonumber when copying a component
-</pre>
-
-<p>
-<strong>Note:</strong> Starting with version 1.2 of gschem the name of the path variable has changed:
-</p>
-<pre class="code">
-(load (string-append geda-data-path "/scheme/auto-uref.scm")) ; load the autonumbering script
-(add-hook! add-component-hook auto-uref) ; autonumber when adding a component
-(add-hook! copy-component-hook auto-uref) ; autonumber when copying a component
-</pre>
-
-</div>
-<!-- SECTION "How can I get refdes automatically numbered when I draw a schematic?" [3901-4805] -->
-<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">
-
-<p>
- A â??busâ?? is purely decoration. The netlister ignores it. The netname= attribute does actual work of connecting points together–this is what gnetlist reads and transforms into your netlist. It is not possible to connect to a discrete line or â??bitâ?? on a bus because, again, the bus is merely a graphical entity.
-</p>
-
-<p>
-Some users have found it helpful to organize their nets by incorporating a bus name into the net name. For example â??net=busA:1â?? may be added to each busripper to aid in sorting out the nets.
-</p>
-
-</div>
-<!-- SECTION "What is a Bus and how do I use it?" [4806-5361] -->
-<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">
-
-<p>
-Key accels are determined by configuration files read on start-up. The default key bindings are set in the file system-gschemrc. If you want to change them, it is recommended to copy and modify the corresponding keymap section to a local config file ($HOME/.gEDA/gschemrc, or $PWD/gschemrc). The modified section will override the the definitions given in system-gschemrc.
-</p>
-
-</div>
-<!-- SECTION "How can I change Key Bindings in gschem?" [5362-5788] -->
-<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">
-
-<p>
-By default you get:
-</p>
-<ul>
-<li class="level1"><div class="li"> Left mouse button is used for picking and drawing.</div>
-</li>
-<li class="level1"><div class="li"> Middle mouse button is either move object (just hold down the middle button over an object and move the mouse) or copy object (ALT key held down while holding down the middle button over object and move the mouse).</div>
-</li>
-<li class="level1"><div class="li"> Right mouse button is a popup menu.</div>
-</li>
-</ul>
-
-<p>
- You can change the middle button by adding the following to a gschemrc file:
-</p>
-<pre class="code">(middle-button "action") ;default binding, move or copy an object</pre>
-
-<p>
-or:
-</p>
-<pre class="code">(middle-button "stroke") ;draw mouse gestures/strokes (must install libstroke to enable</pre>
-
-<p>
-or:
-</p>
-<pre class="code">(middle-button "repeat") ;repeat the last command executed</pre>
-
-<p>
-You can change the right button by adding the following to a gschemrc file:
-</p>
-<pre class="code">(third-button "popup") ;default binding, show a popup menu</pre>
-
-<p>
-or:
-</p>
-<pre class="code">(third-button "mousepan") ;use the mouse to pan around the schematic</pre>
-
-<p>
-For more information on these options, please see the <code>${install_prefix}/share/gEDA/system-gschemrc</code> file.
-</p>
-
-</div>
-<!-- SECTION "What are the mouse bindings in gschem?" [5789-6872] -->
-<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">
-
-<p>
-Yes. Sub sheets are represented by special symbols on the top level schematic. You can find an example for a hierarchical design in the doc section of gschem (<code>geda-doc/examples/gTAG/gTAG.sch</code>). Currently, there is no way to automatically build a sub sheet symbol from an actual sub sheet. The sub sheet symbol has to be drawn manually. Any patches or external scripts that get the job done would be greatly appreciated.
-</p>
-
-<p>
-A <code>source=</code> attribute attached to the sub sheet symbol gives the path to the sub sheet file. The pins of the symbol correspond to ports from top sheet to sub sheet. These ports should correspond to a refdes of a port symbol on the sub sheet. The port symbols in the default library of geda are <code>in-1.sym</code> and <code>out-1.sym</code>. Use the hierarchy menu to navigate within the hierarchy of sub sheets. Alternatively, you can navigate with the page manager.
-</p>
-
-<p>
-To convert a hierarchy to a netlist just call gsch2pcb on the top level schematic. By default, net names and refdesâ??s of components are strictly local to the subsheet. They get the sub sheet symbol refdes as a prefix when inserted into the net list. You can even use multiple instances of a sub sheet symbol without undue short cuts. Whether or not net names and refdesâ??s are mangled and thus local to the sub sheet can be configured in the config file gnetlistrc. Copy the corresponding lines from <code>system-gnetlistrc</code> to <code>gnetlistrc</code> in the current working directory or to <code>$HOME/.gEDA/gnetlistrc</code>. A convenient configuration is to make nets delivered by power symbols global while ordinary nets remain local to the sub sheet. This can be achieved with â??hierarchy-netattrib-mangleâ?? enabled.
-</p>
-
-</div>
-<!-- SECTION "Can gschem do hierarchical designs with sub sheets?" [6873-8615] -->
-<h2><a name="can_gschem_do_a_hierarchy_where_the_top-level_symbol_points_to_a_multi-page_schematic" id="can_gschem_do_a_hierarchy_where_the_top-level_symbol_points_to_a_multi-page_schematic">Can gschem do a hierarchy where the top-level symbol points to a multi-page schematic?</a></h2>
-<div class="level2">
-
-<p>
-Yes. Just attach the <code>source=</code> attribute multiple times with different values. Drill down into the schematic from the symbol, then use [page-up] / [page-down] to navigate through the pages on that level.
-</p>
-
-</div>
-<!-- SECTION "Can gschem do a hierarchy where the top-level symbol points to a multi-page schematic?" [8616-8922] -->
-<h2><a name="can_the_hierarchy_be_setup_in_multiple_directories" id="can_the_hierarchy_be_setup_in_multiple_directories">Can the hierarchy be setup in multiple directories?</a></h2>
-<div class="level2">
-
-<p>
-Yes. Make sure, the <code>(source-library "…â??)</code> and <code>(component-library "…â??)</code> declarations in your gafrc file list the appropriate paths.
-</p>
-
-</div>
-<!-- SECTION "Can the hierarchy be setup in multiple directories?" [8923-9128] -->
-<h2><a name="how_can_options_and_libraries_be_specific_on_subsheet_level" id="how_can_options_and_libraries_be_specific_on_subsheet_level">How can options and libraries be specific on subsheet level?</a></h2>
-<div class="level2">
-
-<p>
-When opening schematics, libgeda changes directory. So it should load any gafrc in the sub-dirs too, as and when the schematics are processed.
-</p>
-
-</div>
-<!-- SECTION "How can options and libraries be specific on subsheet level?" [9129-9345] -->
-<h2><a name="are_there_limitations_to_hierarchy_design" id="are_there_limitations_to_hierarchy_design">Are there limitations to hierarchy design?</a></h2>
-<div class="level2">
-
-<p>
-Although support for subsheets covers many aspects of hierachical design, there are some limitations:
-</p>
-<ul>
-<li class="level1"><div class="li"> Buses cannot connect into subsheets. </div>
-</li>
-<li class="level1"><div class="li"> There is no <acronym title="Graphical User Interface">GUI</acronym> way to start subsheets. You need to manually create a seperate symbol for each subsheet. </div>
-</li>
-</ul>
-
-<p>
-Feel free to fix these issues. Contributions are welcome.
-</p>
-
-</div>
-<!-- SECTION "Are there limitations to hierarchy design?" [9346-9715] -->
-<h1><a name="gschem_symbols" id="gschem_symbols">gschem symbols</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "gschem symbols" [9716-9746] -->
-<h2><a name="where_do_i_find_symbols_beyond_the_default_library" id="where_do_i_find_symbols_beyond_the_default_library">Where do I find symbols beyond the default library?</a></h2>
-<div class="level2">
-
-<p>
-There is a website <a href="http://geda.seul.org/www.gedasymbols.org/"; class="urlextern" title="http:///www.gedasymbols.org/"; rel="nofollow">gedasymbols.org</a> dedicated to user contributed resources for gEDA. You can search the site, preview symbols and download them individually. If you have configured your gafrc files accordingly you can put the symbols right next to the schematics file of your project. You might want to build a local library of symbols, so all projects can access the new symbols. See <span class="curid"><a href="http://geda.seul.org/wiki/geda:faq-gschem#can_gafrc_use_a_variable_to_set_the_root_of_my_library"; class="wikilink1" title="geda:faq-gschem">below</a></span> for the details.
-</p>
-
-<p>
-You can even download all user contributed content from gedasymbols. See the instructions on how to <a href="http://www.gedasymbols.org/cvs.html"; class="urlextern" title="http://www.gedasymbols.org/cvs.html"; rel="nofollow">access gedasymbols using CVS</a>.
-</p>
-
-</div>
-<!-- SECTION "Where do I find symbols beyond the default library?" [9747-10494] -->
-<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">
-
-<p>
-This nomenclature arose from a discussion which frequently appears on the geda-user and geda-dev mailing lists. A light symbol is one which contains very few built-in attributes in the symbol itself. It requires that the user attach almost all attributes at the schematic level (e.g. using either gschem or gattrib). A heavy symbol is one which contains many attributes (such as package footprints, SPICE model names, etc.) built into the symbol file itself. A heavy symbol therefore requires very little attribute attachment at the schematic level â?? you just place it and youâ??re done.
-</p>
-
-<p>
-The debate between proponents of heavy and light symbols is very detailed and involved. Briefly, proponents of heavy symbols believe that they provide better integration between gschem and PCB since the important layout attributes (such as <a href="geda_pcb_tips.html" class="wikilink1" title="geda:pcb_tips">footprint name</a>) are already built into the symbol. This is considered a good thing for new users (noobs) who just want to design a simple board and donâ??t appreciate or donâ??t care about the zillions of variations that even a simple resistor might have (e.g. different footprint, TCR, precision, material composition, etc). Proponents of light symbols prefer to deal with attributes at the schematic level because they believe it to be more flexible. They are quick to point out that a library of heavy symbols will quickly grow into the thousands of parts with grotesquely long names trying to distinguish between the different variations of the part. They also point out that the utility â??gattribâ?? is the preferred tool for dealing with attributes at the schematic level (i.e. in the .sch file).
-</p>
-
-<p>
-GEDA/gaf, as default configured, uses light symbols, although it can be configured to use heavy symbols. For further information, you may read these dicussions from the geda-user mailing list:
-</p>
-
-<p>
-<a href="http://archives.seul.org/geda/user/Jun-2005/msg00001.html"; class="urlextern" title="http://archives.seul.org/geda/user/Jun-2005/msg00001.html"; rel="nofollow">http://archives.seul.org/geda/user/Jun-2005/msg00001.html</a>
-</p>
-
-<p>
-<a href="http://archives.seul.org/geda/dev/Oct-2005/msg00043.html"; class="urlextern" title="http://archives.seul.org/geda/dev/Oct-2005/msg00043.html"; rel="nofollow">http://archives.seul.org/geda/dev/Oct-2005/msg00043.html</a>
-</p>
-
-</div>
-<!-- SECTION "What's this business about heavy vs. light symbols?" [10495-12623] -->
-<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">
-
-<p>
-The symbols in the symbol library, like those available at the <a href="http://www.gedasymbols.org/"; class="urlextern" title="http://www.gedasymbols.org"; rel="nofollow"> gedasymbols</a> website are contributed by users just like you. Some people use different grid settings than other people (e.g. 50mil vs. 100mil). If you discover a symbol which seems to be off the grid, try reducing your grid spacing, move the symbol so that it sits on <strong>your</strong> grid, then revert to your preferred grid settings.
-</p>
-
-<p>
-Yes, the gEDA docs suggest that you use a 100mil grid spacing. But everybody likes to do things their own way, and there is no overall symbol dictator to enforce the rules on contributed symbols. Therefore, you just need to be aware of this possibility.
-</p>
-
-</div>
-<!-- SECTION "I am using a symbol out of the library. How come it's not aligned to the grid?" [12624-13397] -->
-<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">
-
-<p>
-Answer: misc â?? nc-left, nc-right, nc-top, nc-bottom.
-</p>
-
-<p>
-Caution: occassionally this may create a net called â??no_connectâ?? (or â??NC??") which may lead to no-connect pins being connected together in gnetlist â?? which you probably _donâ??t_ want to happen.
-</p>
-
-<p>
-If you want an entire symbol to be graphical (no elec. connections) , add a â??graphical=1â?? attribute. The netlister will ignore these symbols entirely.
-</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?" [13398-13967] -->
-<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">
-
-<p>
-Most attributes living in the symbol do not get promoted to the schematic unless they are visible. To promote invisible symbol attributes, look for the following keywords in the system-gschemrc file:
-</p>
-<pre class="code">(attribute-promotion "enabled");
-(promote-invisible "disabled") ; â?? This one
-(keep-invisible "enabled")</pre>
-
-<p>
-Add to your gschemrc file:
-</p>
-<pre class="code">(promote-invisible "enabled")</pre>
-
-<p>
-and you will get all the attributes promoted. The â??keep-invisibleâ?? keyword will keep hidden those attributes that are hidden in the symbol file.
-</p>
-
-</div>
-<!-- SECTION "How do I promote an invisible symbol attribute into the schematic?" [13968-14587] -->
-<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">
-
-<p>
-In the past, digital logic circuits often hid the power pin, and attached power nets using an attribute inside the symbol. Modern thought is that this is a bad practice (although religious wars still occasionally rage about this topic).
-</p>
-
-<p>
-Itâ??s marginally OK for an old logic circuit which is all 5V TTL to have hidden power and GND pins. If you only have +5V on your board, then hiding the power pin can simplify your schematic somewhat. However, few designers design such circuits nowadays; 5V TTL (and 5V CMOS) are rapidly becoming antique technologies.
-</p>
-
-<p>
-Itâ??s always been unacceptable to hide the power pins on analog chips. First, analog often has multiple power connections (VCC, VEE) which need to be explicitly drawn out. Second, good design practice is to place decoupling caps on each and every power pin. Sometimes one places an inductor in series with power also. Since these should be drawn into the schematic, it is best done by attaching them to an explicit power pin. Therefore, one should never use hidden power pins for analog symbols.
-</p>
-
-<p>
-New logic circuits often use multiple supplies for different chip sections (OVDD, DVDD, etc). It is also typical to have several logic families on a single board (5V, 3.3V etc.). Therefore, itâ??s best to explicitly place and wire the power pins on the symbol. Hidden power pins are a recipe for disaster since you can all too easily misconnect a 5V part to a 3.3V power net, for example.
-</p>
-
-<p>
-To paraphrase Nancy Reagan: Just say â??noâ?? to hidden power pins.
-</p>
-
-<p>
-That said, it may still be useful to detach the power pins from the functional part of the symbol. To do so, define a seperate power symbol and give it the same <a href="http://geda.seul.org/wiki/geda:glossary"; class="wikilink1" title="geda:glossary">refdes</a> as the functional part. A run of gsch2pcb will treat the siblings properly as one single component. As neither gschem nor gsch2pcb explicitely know that the component is only complete with both symbols defined, you have to check yourself. With this workaround, you can draw all power related circuitry in one corner of the schematic where it does not interfere with the signal nets. In many cases this is advantageous with analog circuits.
-</p>
-
-</div>
-<!-- SECTION "What should I do about power pins on my symbols: Make them visible (explicit) or invisible (implicit)?" [14588-16844] -->
-<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">
-
-<p>
-Yes. It is the <a href="geda_scg.html" class="wikilink1" title="geda:scg">Symbol Creation Guide</a>.
-</p>
-
-</div>
-<!-- SECTION "Is there a specification or manual for creating gschem symbols? Where is it?" [16845-16985] -->
-<h2><a name="can_my_local_library_cover_frequently_needed_sub_circuits" id="can_my_local_library_cover_frequently_needed_sub_circuits">Can my local library cover frequently needed sub circuits?</a></h2>
-<div class="level2">
-
-<p>
-Yes. Symbols can contain symbols and nets.
-</p>
-<ol>
-<li class="level1"><div class="li"> Copy the subcircuit to a fresh sheet. (unlock and remove the default title block as you wonâ??t need it)</div>
-</li>
-<li class="level1"><div class="li"> The values of refdes attributes should end with "?", to allow to auto number them later. </div>
-</li>
-<li class="level1"><div class="li"> Move the sub circuit to the lower left of the available space. (You can use symbol-translate from the edit menu)</div>
-</li>
-<li class="level1"><div class="li"> Save the sub circuit as a *.sym file in your local library. </div>
-</li>
-<li class="level1"><div class="li"> Choose â??Include component as individual objectsâ?? when selecting this complex symbol for your actual schematic. The whole sub circuit will be pasted to your sheet. Be sure to switch back to the default mode for inclusion of ordinary symbols. </div>
-</li>
-</ol>
-
-</div>
-<!-- SECTION "Can my local library cover frequently needed sub circuits?" [16986-17731] -->
-<h1><a name="gschem_configuration_customization" id="gschem_configuration_customization">Gschem configuration/customization</a></h1>
-<div class="level1">
-
-<p>
-Gschem is configurable in more ways than can be describe here. Look at â??system-gschemrcâ?? for suggestions what else can be done.
-</p>
-
-</div>
-<!-- SECTION "Gschem configuration/customization" [17732-17910] -->
-<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>
-<li class="level1"><div class="li"> Create a project directory, for example ${HOME}/myproj.</div>
-</li>
-<li class="level1"><div class="li"> Place the symbols you want to use into ${HOME}/myproj/symbols.</div>
-</li>
-<li class="level1"><div class="li"> Create a gafrc file in ${HOME}/myproj.</div>
-</li>
-<li class="level1"><div class="li"> In gafrc, put this line: <pre class="code"> (component-library "./symbols") </pre>
-</div>
-</li>
-<li class="level1"><div class="li"> Run gschem from your project directory ${HOME}/myproj. That is, do this to run gschem:<pre class="code">cd ${HOME}/myproj
-gschem myschematic.sch</pre>
-</div>
-</li>
-</ol>
-
-<p>
- Points to remember:
-</p>
-<ul>
-<li class="level1"><div class="li"> The guile stuff which processes your RC file doesnâ??t understand or expand shell wildcards like "~" or ${HOME}. It does understand "." as the current working directory, and it does understand absolute file paths. If you want to do something tricky, you can try to use Scheme functions to get directory information.</div>
-</li>
-<li class="level1"><div class="li"> Make sure gafrc lives in your main project directory. </div>
-</li>
-<li class="level1"><div class="li"> Run all gEDA programs from your main project directory. </div>
-</li>
-<li class="level1"><div class="li"> Run the programs from the command line in a terminal shell – donâ??t use any whizzy, shiny desktop icons to run gschem (if you have them) since you wonâ??t know what directory gschem is starting in, and gschem might not find gafrc.</div>
-</li>
-<li class="level1"><div class="li"> The key is: start gschem in the same directory as where your gafrc lives.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "How do I configure my local gafrc to find my local symbol directory?" [17911-19165] -->
-<h2><a name="can_gafrc_use_a_variable_to_set_the_root_of_my_library" id="can_gafrc_use_a_variable_to_set_the_root_of_my_library">Can gafrc use a variable to set the root of my library?</a></h2>
-<div class="level2">
-
-<p>
-Currently (v1.3.1) gschem does not descend into subdirectories of the symbol library. You have to give individually each and every directory of your local lib in your gafrc file. However, you donâ??t have to repeat the absolute base path over and over. You can use the function â??build-pathâ?? to concatenate the path on the fly:
-</p>
-<pre class="code">(define gedasymbols "/path/to/local/library")
-(component-library (build-path gedasymbols "analog"))
-(component-library (build-path gedasymbols "block"))
-(component-library (build-path gedasymbols "connector"))</pre>
-
-</div>
-<!-- SECTION "Can gafrc use a variable to set the root of my library?" [19166-19782] -->
-<h2><a name="the_library_window_is_cluttered_with_default_symbols._can_i_restrict_to_my_local_lib" id="the_library_window_is_cluttered_with_default_symbols._can_i_restrict_to_my_local_lib">The library window is cluttered with default symbols. Can I restrict to my local lib?</a></h2>
-<div class="level2">
-
-<p>
-Put a localized version of the following lines in a gafrc.
-</p>
-<pre class="code">
-; empty the library path and populate it with local paths
-(reset-component-library)
-(component-library "/foo/localgedalib1")
-(component-library "/bar/foo/localgedalib2")
-</pre>
-
-<p>
- You have to add each and every dir of your local library. Subdirs are not automatically reckognized by gschem and gsch2pcb. Its a good idea to place this gafrc in your projects dir. That way, if you start gschem from some other place, you still get the system symbols shown. This also allows to configure special symbol libs for specific projects.
-</p>
-
-</div>
-<!-- SECTION "The library window is cluttered with default symbols. Can I restrict to my local lib?" [19783-20474] -->
-<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">
-
-<p>
-Put
-</p>
-<pre class="code">(text-size 10)</pre>
-
-<p>
- into your gschemrc and replace â??10â?? with your favorite size.
-</p>
-
-</div>
-<!-- SECTION "How can I change the default size of floating text?" [20475-20633] -->
-<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">
-
-<p>
-Edit the system-gschemrc file and near the top you will find lines like:
-</p>
-<pre class="code">;
-; Start of color section
-;
-; Load up a color scheme has a light (almost white) background
-; Comment out the first line and comment in the second line for a
-; dark (black) background. The dark background is the original look.
-;
-(load (string-append gedadatarc "/gschem-darkbg")) ; dark background
-;(load (string-append gedadatarc "/gschem-lightbg")) ; light background</pre>
-
-<p>
-Comment out the <strong><code>darkbg</code></strong> line (with a ;) and comment in the <strong><code>lightbg</code></strong> line. This will give you a light background instead of a black background. It also adjust all the other colors to be compatible with a light background.
-</p>
-
-<p>
-Note, starting with version 1.2 of gschem the syntax of this line changed to
-</p>
-<pre class="code">(load (build-path geda-rc-path "gschem-lightbg")) ; light background</pre>
-
-<p>
- If you want more control over the colors, please edit <strong><code>${prefix}/share/gEDA/gschem-darkbg</code></strong> or <strong><code>${prefix}/share/gEDA/gschem-lightbg</code></strong> or create your own file and load it in the <strong><code>system-gschemrc</code></strong> file.
-</p>
-
-<p>
-A dark background is preferred by many users.
-</p>
-
-</div>
-<!-- SECTION "How can I have a different background color other than black?" [20634-21832] -->
-<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">
-
-<p>
-In the system-gschemrc file, you will find the following section:
-</p>
-<pre class="code">
-; log-window string
-;
-; Controls if the log message window is mapped when gschem is started up
-; Possible options:
-; startup - opened up when gschem starts
-; later - NOT opened up when gschem starts
-; (can be opened by Options/Show Log Window)
-;
-(log-window "startup")
-;(log-window "later")</pre>
-
-<p>
-Comment out the <strong><code>startup</code></strong> line (with a ;) and comment in the <strong><code>later</code></strong> line, or add the following line to your gschemrc file:
-</p>
-<pre class="code">(log-window "later")</pre>
-
-</div>
-<!-- SECTION "Each time I start gschem, the log message window is shown. Can I disable it?" [21833-22495] -->
-<h2><a name="can_i_get_a_customized_title_block_with_new_schematics" id="can_i_get_a_customized_title_block_with_new_schematics">Can I get a customized title block with new schematics?</a></h2>
-<div class="level2">
-
-<p>
-Put the following line into your gschemrc file:
-</p>
-<pre class="code">(define default-titleblock "title-A3.sym")</pre>
-
-<p>
- Replace â??title-A3.symâ?? with the file name of your favorite title block symbol.
-</p>
-
-</div>
-<!-- SECTION "Can I get a customized title block with new schematics?" [22496-22748] -->
-<h1><a name="printing_output" id="printing_output">Printing/Output</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "Printing/Output" [22749-22778] -->
-<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">
-
-<p>
-Running the script <strong><code>gschem-print.scm</code></strong> will create the Postscript file that is specified on the command line.
-</p>
-
-<p>
-The command line below creates a Postscript file from a schematic file (replace MY_SCH with the name of your schematic and GEDA_SCHEME_DIR with the name of the directory where your gEDA scheme files are installed):
-</p>
-<pre class="code">gschem -p -oMY_SCH.ps -sGEDA_SCHEME_DIR/gschem-print.scm MY_SCH.sch</pre>
-
-<p>
-The <code>bash</code> script below, which I name <strong><code>gschem-print</code></strong>, creates a Postscript file for each schematic file that is specified on the command line and then outputs each Postscript file to the default printer:
-</p>
-<pre class="code">#!/bin/bash
-
-# gschem options
-# -oPS_FILENAME output to Postscript file PS_FILENAME
-# -sSCRIPT_FILENAME run script SCRIPT_FILENAME
-# -p autoplace windows
-
-for name in $*
-do
- base="${name%.*}"
- gschem -p -o$base.ps -sGEDA_SCHEME_DIR/gschem-print.scm $base.sch
- lpr -P$PRINTER $base.ps
-done</pre>
-
-</div>
-<!-- SECTION "How do I print schematics from the command line?" [22779-23776] -->
-<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">
-
-<p>
-Edit the <strong><code>system-gschemrc</code></strong> file or place the following into a <strong><code>gschemrc</code></strong> file (either <strong><code>~/.gEDA/gschemrc</code></strong> or a <strong><code>gschemrc</code></strong> file in the local directory where you invoke gschem):
-</p>
-<pre class="code">(output-color "enabled") ; for color postscript output
-(image-color "enabled") ; for color PNG output (enabled by default)</pre>
-
-<p>
-To control the background of the PS output, change the following line in either gschem-darkbg (for the default black colored background) or gschem-lightbg (for the alternative light colored background):
-</p>
-<pre class="code">(output-color-background 16 "black" "null" "0 0 0" 0 0 0)</pre>
-
-<p>
-The â??0 0 0â?? is the RGB components (between 0..1) for the background color of the PS output.
-</p>
-
-<p>
-To control the background of the <acronym title="Portable Network Graphics">PNG</acronym> output, change the following line in either gschem-darkbg (for the default black colored background) or gschem-lightbg (for the alternative light colored background):
-</p>
-<pre class="code">(background-color 0 "grey94" "null" "1 1 1" 255 255 255)</pre>
-
-<p>
-The 255 255 255 are the RGB components for the background color of the <acronym title="Portable Network Graphics">PNG</acronym> image.
-</p>
-
-</div>
-<!-- SECTION "How can I get color postscript/PNG output?" [23777-24908] -->
-<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">
-
-<p>
-For black and white PS output, place the following into a gschemrc file:
-</p>
-<pre class="code">(output-color "disabled") ; for monochrome postscript output</pre>
-
-<p>
-For black and white <acronym title="Portable Network Graphics">PNG</acronym> images, place the following into a gschemrc file:
-</p>
-<pre class="code">(image-color "disabled") ; for monochromoe PNG output</pre>
-
-</div>
-<!-- SECTION "How can I get black and white postscript/PNG output?" [24909-25274] -->
-<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>
-<li class="level1"><div class="li"> Print the schematic to a file. This will be generic postscript (*.ps).</div>
-</li>
-<li class="level1"><div class="li"> Convert the postscript file to epsi with the tool ps2epsi. This is a script from the ghostscript suite.</div>
-</li>
-<li class="level1"><div class="li"> Include usepackage{graphicx} to the preamble of your latex document. Use the command <strong>includegraphics</strong> to place your schematic.</div>
-</li>
-</ol>
-
-<p>
- A simple example:
-</p>
-<pre class="code">\documentclass{article}
-\usepackage{graphicx}
-\begin{document}
- \begin{image}
- \includegraphics[width=100mm]{ModulPID.epsi}
- \end{image}
-\end{document}</pre>
-
-</div>
-<!-- SECTION "How can I insert schematics into my LaTex document?" [25275-25843] -->
-<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">
-
-<p>
-gschem does not provide this functionality internally, however there is a program called â??posterâ?? which does exactly this. It can be downloaded from either <a href="http://www.gnu.org/directory/poster.html"; class="urlextern" title="http://www.gnu.org/directory/poster.html"; rel="nofollow">here</a> (GNU) or <a href="http://printing.kde.org/downloads/"; class="urlextern" title="http://printing.kde.org/downloads/"; rel="nofollow">here</a> (KDE Print).
-</p>
-
-</div>
-<!-- SECTION "How can I split Postscript output over multiple pages?" [25844-26187] -->
-<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" [26188-26240] -->
-<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">
-
-<p>
-This bug emerged in mid 2006 for users of Fedora Core 5 (and other linux distributions that use glib 2.10.x). The bug has been fixed by the developers; the latest versions of gEDA/gaf (i.e. Oct 2006 and beyond) shouldnâ??t have this problem.
-</p>
-
-<p>
-If you happen to have an older version of gEDA/gaf, you can work around this bug by setting the environment variable G_SLICE to â??always-mallocâ??. Specifically, before you run gschem, do this:
-</p>
-
-<p>
-bash:
-</p>
-<pre class="code">export G_SLICE=always-malloc</pre>
-
-<p>
-csh:
-</p>
-<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?" [26241-26895] -->
-<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">
-
-<p>
-If you run gschem and you get a window without a menu bar, no colors, and the program terminates when you press a key with the following message:
-</p>
-<pre class="code">ERROR: Unbound variable: current-keymap</pre>
-
-<p>
-Or you get errors like this:
-</p>
-<pre class="code">Gtk-CRITICAL : file gtkpixmap.c: line 97 (gtk_pixmap_new): assertion `val != NULLâ?? failed.
-Gtk-CRITICAL : file gtkpixmap.c: line 97 (gtk_pixmap_new): assertion `val != NULLâ?? failed.
-Tried to get an invalid color: 0
-Tried to get an invalid color: 7
-Tried to get an invalid color: 0
-Tried to get an invalid color: 7</pre>
-
-<p>
-then gschem is not finding an rc file. There are two required rc files. The first is <strong><code>system-gschemrc</code></strong> and the second is <strong><code>system-commonrc</code></strong>.
-</p>
-<ul>
-<li class="level1"><div class="li"> The system-gschemrc rc file should be installed when you install gschem and typically resides in <strong><code>${prefix}/share/gEDA/system-gschemrc</code></strong>. <strong><code>${prefix}</code></strong> is where you installed gschem (usually <strong><code>/usr</code></strong> or <strong><code>/usr/local</code></strong> or <strong><code>$HOME/geda</code></strong>). This file can also be installed in /etc/gEDA (the .debs packages do this).</div>
-</li>
-<li class="level1"><div class="li"> The system-commonrc rc file should be installed when you install the symbol library for gEDA/gaf. It resides in <strong><code>${prefix}/share/gEDA/system-commonrc</code></strong>. This file can also be installed in <strong><code>/etc/gEDA</code></strong> (the .debs packages do this). This file is not loaded directly by gschem. It is loaded by a â??(load …)â?? in the system-gschemrc rc file.</div>
-</li>
-</ul>
-
-<p>
- Make sure these file are installed. The gschem.log file (which is created everytime you run gschem) holds valuable debugging information which should help in determining what is wrong. Check this file for where gschem is looking for the rc files.
-</p>
-
-<p>
-Also, some older releases of gEDA/gaf had some bugs when the rc files were installed in other locations (other that <strong><code>${prefix}/share/gEDA</code></strong>), so please upgrade to a more current release.
-</p>
-
-</div>
-<!-- SECTION "After installation gschem does not work!? What could be wrong?" [26896-28819] -->
-<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">
-
-<p>
-Make sure that at least one of your config files contains a valid path to a symbol library. At startup, gschem checks for the following config files (on a Debian system):
-</p>
-<ol>
-<li class="level1"><div class="li"> system gafrc file: <code>/etc/gEDA/system-gafrc</code></div>
-</li>
-<li class="level1"><div class="li"> user gafrc file: <code>~/.gEDA/gafrc</code></div>
-</li>
-<li class="level1"><div class="li"> local gafrc file: <code>$PWD/gafrc</code></div>
-</li>
-<li class="level1"><div class="li"> system gschemrc file: <code>/etc/gEDA/system-gschemrc</code></div>
-</li>
-<li class="level1"><div class="li"> user gschemrc file: <code>~/.gEDA/gschemrc</code></div>
-</li>
-<li class="level1"><div class="li"> local gschemrc file: <code>$PWD/gschemrc</code></div>
-</li>
-</ol>
-
-<p>
-All of these config files may or may not append paths to the library search list. If a config file conatins the command
-</p>
-<pre class="code">(reset-component-library)</pre>
-
-<p>
- the library search path will be emptied. Order is obviously important, as this command will erase any previously appended paths.
-</p>
-
-</div>
-<!-- SECTION "Add Components offers no symbols! What can I do about it?" [28820-29623] -->
-<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">
-
-<p>
- If you are getting into the remote machine by doing:
-</p>
-<pre class="code">$ ssh -X your_username@your_remote_machine</pre>
-
-<p>
-and afterwards you get the Xlib RENDER message, then try using:
-</p>
-<pre class="code">$ ssh -Y your_username@your_remote_machine</pre>
-
-<p>
-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.'" [29624-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/geda_faq-pcb.html b/docs/wiki/geda_faq-pcb.html
deleted file mode 100644
index 23a0f43..0000000
--- a/docs/wiki/geda_faq-pcb.html
+++ /dev/null
@@ -1,152 +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>geda:faq-pcb</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/"; />
-<link rel="contents" href="http://geda.seul.org/wiki/geda:faq-pcb?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:faq-pcb"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:faq-pcb"; />
-<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="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>
-
-
-
-<h2><a name="pcb_faq" id="pcb_faq">pcb FAQ</a></h2>
-<div class="level2">
-
-</div>
-<!-- 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>
-<!-- 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>.
-</p>
-
-</div>
-<!-- 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 …
-</p>
-
-</div>
-<!-- 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.
-</p>
-
-</div>
-<!-- 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. 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>
-<!-- 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
-</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>
-</li>
-<li class="level1"><div class="li"> <a href="http://en.wikibooks.org/wiki/Practical_Electronics/PCB_Layout"; class="urlextern" title="http://en.wikibooks.org/wiki/Practical_Electronics/PCB_Layout"; rel="nofollow">http://en.wikibooks.org/wiki/Practical_Electronics/PCB_Layout</a></div>
-</li>
-</ul>
-
-</div>
-<!-- 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>
-</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>?
-</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">
-
-<p>
-See <a href="geda_pcb_footprints.html" class="wikilink1" title="geda:pcb_footprints">pcb_footprints</a>.
-</p>
-
-<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>.
-</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>
-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 "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_faq-simulation.html b/docs/wiki/geda_faq-simulation.html
deleted file mode 100644
index fe4ac48..0000000
--- a/docs/wiki/geda_faq-simulation.html
+++ /dev/null
@@ -1,177 +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>geda:faq-simulation</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2008-04-04T10:16:12-0400" />
-<meta name="keywords" content="geda,faq-simulation" />
-<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/geda:faq-simulation?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:faq-simulation"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:faq-simulation"; />
-<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="#simulation" class="toc">Simulation</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#i_want_to_simulate_my_analog_circuit_design._what_are_my_options" class="toc">I want to simulate my analog circuit design. What are my options?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#what_about_tclspice_what_is_it_should_i_use_it" class="toc">What about tclspice? What is it? Should I use it?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#isn_t_there_a_nice_graphical_schematic_capture_front_end_so_i_can_just_place_components_and_press_a_simulate_button" class="toc">Isn't there a nice graphical (schematic capture) front end so I can just place components and press a "simulate" button?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_create_my_schematic_to_facilitate_analog_simulation" class="toc">How do I create my schematic to facilitate analog simulation?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#which_spice_netlister_backend_to_gnetlist_should_i_use_there_are_several_of_them" class="toc">Which spice netlister backend to gnetlist should I use? There are several of them. . . .</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#how_about_if_i_want_to_use_gnucap_can_i_use_spice-sdb_to_create_my_gnucap_netlists" class="toc">How about if I want to use gnucap, can I use spice-sdb to create my gnucap netlists?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#why_not_reuse_my_simulation_schematic_for_layout" class="toc">Why not reuse my simulation schematic for layout?</a></span></div></li></ul>
-</li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="simulation" id="simulation">Simulation</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "Simulation" [1-26] -->
-<h2><a name="i_want_to_simulate_my_analog_circuit_design._what_are_my_options" id="i_want_to_simulate_my_analog_circuit_design._what_are_my_options">I want to simulate my analog circuit design. What are my options?</a></h2>
-<div class="level2">
-
-<p>
-Within the cannonical gEDA Suite apps there are two analog circuit simulators: ngspice and gnucap. In (slightly) more detail:
-</p>
-<ul>
-<li class="level1"><div class="li"> <a href="http://ngspice.sourceforge.net/"; class="urlextern" title="http://ngspice.sourceforge.net/"; rel="nofollow">Ngspice</a> is a port/clean-up of classical SPICE 3f5 to the GNU/Linux platform. It is fully functional, includes the XSpice extensions (such as SPICE 2 POLY constructs), and the CIDER framework.</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://www.gnucap.org/"; class="urlextern" title="http://www.gnucap.org/"; rel="nofollow">Gnucap</a> is a new circuit simulator written from the ground up. It offers the ability to perform event-driven â?? as well as continuous time â?? simulations. It is the work of Al Davis. If you wish to download it, make sure you grab the latest version, available through the â??developement releasesâ?? link on the gnucap website.</div>
-</li>
-</ul>
-
-<p>
- Both are CLI (command line interface) programs, meaning that you intereact with the simulator by typing commands at a command line. It also means that you need to learn the simulator-specific command set.
-</p>
-
-<p>
-If you prefer a graphical interface, the new gEDA app GSpiceUI provides a nice <acronym title="Graphical User Interface">GUI</acronym> front-end to drive the simulation programs. However, GSpiceUI is not a complete schematic-to-simulation-output simulator like LTSpice or PSpice. Rather, it just provides a <acronym title="Graphical User Interface">GUI</acronym> menu which helps you navigate the commands you need to perform your ngspice/gnucap simulation.
-</p>
-
-</div>
-<!-- SECTION "I want to simulate my analog circuit design. What are my options?" [27-1384] -->
-<h2><a name="what_about_tclspice_what_is_it_should_i_use_it" id="what_about_tclspice_what_is_it_should_i_use_it">What about tclspice? What is it? Should I use it?</a></h2>
-<div class="level2">
-
-<p>
-<a href="http://tclspice.sourceforge.net/"; class="urlextern" title="http://tclspice.sourceforge.net/"; rel="nofollow">Tclspice</a> was a fork off the ngspice development path. It was begun in the 2002 timeframe. In principle, tclspice would export the SPICE command set to a TCL <acronym title="Application Programming Interface">API</acronym>, allowing you to embed SPICE analyses into a TCL program. This vision is certainly very attractive since TCL is a powerful scripting language â?? much more powerful than the scripting constructs available from within SPICE itself. Using TCL, one could imagine writing complex circuit optimizers, adding behavioral elements to a simulation, and finally gaining control over SPICEâ??s graphical output.
-</p>
-
-<p>
-As it turns out, this goal was partially met â?? with tclspice you can indeed do something like this:
-</p>
-<pre class="code">#! tclsh
-package require spice
-spice::codemodel /usr/local/src/tclspice-0.2.12/src/xspice/icm/spice2poly.cm
-
-spice::source netlistname.cir
-spice::tran 0.1ns 40ns
-spice::run
-spice::plot Vout
-puts "All done now!"</pre>
-
-<p>
-Unfortunately, tclspice lacks certain important features, like providing you a return code which tells you whether your simulation actually worked or errored out instead. Also, the graphics functionality never seemed to work (at least for me … and the developers admit that the graphics stink). Converting TCL variables to and from SPICE vectors never seemed to work â?? again at least for me. Finally, ngspice (at least) has a lot of memory leaks, making long simulation runs difficult. Therefore, tclspice doesnâ??t meet the promise it originally held out: a convenient, scriptable way to drive SPICE simulations.
-</p>
-
-<p>
-Developement on tclspice effectively stopped in 2004. Perhaps some day somebody will pick it up again. In the meantime, the main <a href="http://ngspice.sourceforge.net/"; class="urlextern" title="http://ngspice.sourceforge.net/"; rel="nofollow">ngspice</a> development branch has picked up the tclspice features if you want them (they require separate configuration options), and the code is fresher.
-</p>
-
-</div>
-<!-- SECTION "What about tclspice? What is it? Should I use it?" [1385-3314] -->
-<h2><a name="isn_t_there_a_nice_graphical_schematic_capture_front_end_so_i_can_just_place_components_and_press_a_simulate_button" id="isn_t_there_a_nice_graphical_schematic_capture_front_end_so_i_can_just_place_components_and_press_a_simulate_button">Isn't there a nice graphical (schematic capture) front end so I can just place components and press a "simulate" button?</a></h2>
-<div class="level2">
-
-<p>
-No. The best you can do is use <a href="http://www.geda.seul.org/tools/gspiceui/index.html"; class="urlextern" title="http://www.geda.seul.org/tools/gspiceui/index.html"; rel="nofollow">GSpiceUI</a>.
-</p>
-
-</div>
-<!-- SECTION "Isn't there a nice graphical (schematic capture) front end so I can just place components and press a simulate button?" [3315-3544] -->
-<h2><a name="how_do_i_create_my_schematic_to_facilitate_analog_simulation" id="how_do_i_create_my_schematic_to_facilitate_analog_simulation">How do I create my schematic to facilitate analog simulation?</a></h2>
-<div class="level2">
-
-<p>
-The usual design path is â??gschemâ?? â?? â??gnetlist -g spice-sdbâ?? â?? [â??ngspiceâ?? | â??gnucapâ??]. You need to attach attributes to the components in your schematic to provide attributes needed by SPICE/Gnucap. You can also attach attributes using gattrib.
-</p>
-
-<p>
-The <a href="geda_csygas.html" class="wikilink1" title="geda:csygas">Circuit Simulation using gEDA and SPICE - HOWTO</a> describes all this in great detail.
-</p>
-
-<p>
- Some <a href="http://www.brorson.com/gEDA/SPICE/"; class="urlextern" title="http://www.brorson.com/gEDA/SPICE/"; rel="nofollow">SPICE resources</a> will help you understand how to use spice-sdb.
-</p>
-
-</div>
-<!-- SECTION "How do I create my schematic to facilitate analog simulation?" [3545-4097] -->
-<h2><a name="which_spice_netlister_backend_to_gnetlist_should_i_use_there_are_several_of_them" id="which_spice_netlister_backend_to_gnetlist_should_i_use_there_are_several_of_them">Which spice netlister backend to gnetlist should I use? There are several of them. . . .</a></h2>
-<div class="level2">
-
-<p>
-Use spice-sdb. It is by far the most advanced and feature rich. The others are there only for reasons of history. Note that spice-sdb is an extension of one of the other SPICE backends, so you arenâ??t missing anything by using spice-sdb.
-</p>
-
-</div>
-<!-- SECTION "Which spice netlister backend to gnetlist should I use? There are several of them. . . ." [4098-4438] -->
-<h2><a name="how_about_if_i_want_to_use_gnucap_can_i_use_spice-sdb_to_create_my_gnucap_netlists" id="how_about_if_i_want_to_use_gnucap_can_i_use_spice-sdb_to_create_my_gnucap_netlists">How about if I want to use gnucap, can I use spice-sdb to create my gnucap netlists?</a></h2>
-<div class="level2">
-
-<p>
-Yes. Also, you can draw your schematic using gnucap directives available in the â??spiceâ?? symbol directory.
-</p>
-
-<p>
-It is better to just draw the circuit, without directives, and run the simulator interactively.
-</p>
-
-</div>
-<!-- SECTION "How about if I want to use gnucap, can I use spice-sdb to create my gnucap netlists?" [4439-4743] -->
-<h2><a name="why_not_reuse_my_simulation_schematic_for_layout" id="why_not_reuse_my_simulation_schematic_for_layout">Why not reuse my simulation schematic for layout?</a></h2>
-<div class="level2">
-
-<p>
-Newbies commonly want to create a single schematic for both design simulation/validation as well as layout. This vision seems very attractive at first, since your layout will have been tested & validated before committing it to FR-4. However, the devil is in the details; using a single schematic for simulation and layout usually doesnâ??t work for the following reasons:
-</p>
-<ul>
-<li class="level1"><div class="li"> Components required for simulation and layout are normally very different. For example, simulation often requires a schematic holding a bunch of SPICE-related devices such as voltage sources, dependent sources, SPICE directives, and so on. On the other hand, layout requires non-SPICEable components such as connectors, logic devices, and even things like voltage regulators which might have no SPICE models available, but will pollute your SPICE netlist, possibly making the netlister and the simulator unhappy.</div>
-</li>
-<li class="level1"><div class="li"> Some real electronic components donâ??t have built-in SPICE models. There are plenty of components which donâ??t have native SPICE models like potentiometers, transformers, thermistors, EMI filters, logic gates, crystals, vacuum tubes, and on and on. Therefore, if your design uses any of these components, you must mock up the device using an equivalent circuit for simulation. This makes it very difficult to reuse the simulation schematic for layout.</div>
-</li>
-<li class="level1"><div class="li"> Usually, you only really need to simulate a subset of your design. For example, you might want to simulate the behavior of a filter or oscillator circuit, but donâ??t care about (or canâ??t simulate) your power supply, glue logic, or other part of your design. If you insist upon creating a SPICE model for these circuit subsections, you might need to jump through a lot of hoops â?? and do a lot of unnecessary hard work â?? in order to find or create SPICE models for parts of your design which arenâ??t important.</div>
-</li>
-</ul>
-
-<p>
- Therefore, I (SDB) normally recommend that you shouldnâ??t try too hard to use the same schematic for simulation and for layout. If you can do it, great! But usually you canâ??t.
-</p>
-
-<p>
-Personally, I tend to create SPICE models of only the critical analog sections of my design. A larger project might therefore have a couple of simulation schematics validating a couple of analog subcircuits. Besides the simulation schematics, Iâ??ll have a main schematic which is used for layout.
-</p>
-
-</div>
-<!-- SECTION "Why not reuse my simulation schematic for layout?" [4744-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/geda_faq.html b/docs/wiki/geda_faq.html
deleted file mode 100644
index 0c4d12c..0000000
--- a/docs/wiki/geda_faq.html
+++ /dev/null
@@ -1,355 +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>geda:faq</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-06-27T07:21:45-0400" />
-<meta name="keywords" content="geda,faq" />
-<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/geda:faq?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:faq"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:faq"; />
-<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="#geda_faq" class="toc">gEDA FAQ</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#what_is_the_geda_project" class="toc">What is the gEDA project?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#what_is_geda_gaf_and_how_does_it_relate_to_geda" class="toc">What is gEDA/gaf and how does it relate to gEDA?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#what_is_the_geda_suite" class="toc">What is the gEDA suite?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#why_what_makes_geda_so_different_from_other_eda_tools" class="toc">Why? What makes gEDA so different from other EDA tools?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#why_does_the_geda_suite_seem_like_a_collection_of_random_programs_and_not_a_single_integrated_application" class="toc">Why does the gEDA Suite seem like a collection of random programs, and not a single integrated application?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#so_which_is_better_a_suite_i.e._confederacy_of_programs_or_an_integrated_application" class="toc">So which is better, a suite (i.e. confederacy) of programs or an integrated application?</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#suite_confederacy_pros" class="toc">Suite (confederacy) pros:</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#suite_confederacy_cons" class="toc">Suite (confederacy) cons:</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#monolithic_application_pros" class="toc">Monolithic application pros:</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#monolithic_application_cons" class="toc">Monolithic application cons:</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#tool_xxx_is_missing_critical_feature_yyy_what_can_i_do" class="toc">Tool XXX is missing critical feature YYY! What can I do?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#what_license_does_geda_use" class="toc">What license does gEDA use?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#where_can_i_get_more_information_about_and_download_geda" class="toc">Where can I get more information about and download gEDA?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#okay_how_do_i_start_using_geda" class="toc">Okay, how do I start using gEDA?</a></span></div></li></ul>
-</li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="geda_faq" id="geda_faq">gEDA FAQ</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "gEDA FAQ" [1-24] -->
-<h2><a name="what_is_the_geda_project" id="what_is_the_geda_project">What is the gEDA project?</a></h2>
-<div class="level2">
-
-<p>
-The gEDA project is working on producing a full <acronym title="GNU General Public License">GPL</acronym>â??d suite of EDA (<em class="u">E</em>lectronic <em class="u">D</em>esign <em class="u">A</em>utomation) tools. These tools are used for electrical circuit design, schematic capture, simulation, prototyping, and production. Currently, the gEDA project offers a mature suite of free software applications for electronics design, including schematic capture, attribute management, bill of materials (BOM) generation, netlisting into over 20 netlist formats, analog and digital simulation, and printed circuit board (PCB) layout.
-</p>
-
-<p>
-The gEDA project was launched by Ales Hvezda in Spring 1998 and both the software and the community have grown considerably since then. A few people are contributing to the original tools, while others are doing their own development on their own tools. â??gEDAâ?? does not refer solely to the original tools anymore (those tools now stand on their own), but instead to all the projects which are free and are somehow associated with this webpage or the geda-dev/geda-user mailing lists. By associating with gEDA, free software authors do not give up any control over their tools, but they gain a community which cares about quality and free (as in freedom) EDA tools.
-</p>
-
-<p>
-gEDA can be pronounced â??gee-daahhhâ?? (rhymes with cheetah) or â??g-dahhh (short g).
-</p>
-
-</div>
-<!-- SECTION "What is the gEDA project?" [25-1353] -->
-<h2><a name="what_is_geda_gaf_and_how_does_it_relate_to_geda" id="what_is_geda_gaf_and_how_does_it_relate_to_geda">What is gEDA/gaf and how does it relate to gEDA?</a></h2>
-<div class="level2">
-
-<p>
-<strong>gaf</strong> stands for â??<em class="u">g</em>schem <em class="u">a</em>nd <em class="u">f</em>riendsâ??. It is a subset of the entire tool suite grouped together under the gEDA name. gEDA/gaf is a collection of tools which currently includes:
-</p>
-<ul>
-<li class="level1"><div class="li"> gschem: A schematic capture program</div>
-</li>
-<li class="level1"><div class="li"> gnetlist: A netlist generation program</div>
-</li>
-<li class="level1"><div class="li"> gsymcheck: A syntax checker for schematic symbols</div>
-</li>
-<li class="level1"><div class="li"> gattrib: A spreadsheet programm that manipulates the properties of symbols of a schematic</div>
-</li>
-<li class="level1"><div class="li"> libgeda: Libraries for gschem gnetlist and gsymcheck</div>
-</li>
-<li class="level1"><div class="li"> gsch2pcb: A tool to forward annotation from your schematic to layout using <a href="geda_pcb.html" class="wikilink2" title="geda:pcb">PCB</a></div>
-</li>
-<li class="level1"><div class="li"> some minor utilities</div>
-</li>
-</ul>
-
-<p>
- The gEDA/gaf tools share a common file format (.sch) and also share a common link library (libgeda.so). The gEDA/gaf source distribution can be found on this website (geda.seul.org).
-</p>
-
-<p>
-Even though gaf is very much a part of gEDA, the gEDA name does not necessarily only apply to gaf â?? tools gathered under the â??gEDAâ?? moniker include many other programs. Indeed, gEDA refers to <strong>any</strong> <acronym title="GNU General Public License">GPL</acronym>â??d EDA tool which decides to associate itself with the gEDA website/mailing list. Important examples of gEDA tools include the layout program <a href="geda_pcb.html" class="wikilink2" title="geda:pcb">PCB</a>, the Verilog compiler <a href="http://www.icarus.com/eda/verilog/"; class="urlextern" title="http://www.icarus.com/eda/verilog/"; rel="nofollow">Icarus Verilog</a>, the analog circuit simulator <a href="http://www.gnucap.org/"; class="urlextern" title="http://www.gnucap.org/"; rel="nofollow">gnucap</a>, and the open-source SPICE simulator <a href="http://www.ngspice.org/"; class="urlextern" title="http://www.ngspice.org/"; rel="nofollow">ngspice</a>. Many other gEDA programs also exist.
-</p>
-
-<p>
-For historical reasons, on <a href="http://freshmeat.net/"; class="urlextern" title="http://freshmeat.net/"; rel="nofollow">freshmeat</a> gaf is known as the package â??gEDAâ??.
-</p>
-
-</div>
-<!-- SECTION "What is gEDA/gaf and how does it relate to gEDA?" [1354-2919] -->
-<h2><a name="what_is_the_geda_suite" id="what_is_the_geda_suite">What is the gEDA suite?</a></h2>
-<div class="level2">
-
-<p>
-The gEDA suite is a CDROM image (.iso) created by Stuart Brorson to make it easier to install all the various tools that are part of, associated with, or just plain work with the gEDA projectâ??s software. The vision is that the tools collected on the gEDA suite CDROM constitute a coherent, complete, open-source design environment gathered into one convenient download. Currently the gEDA suite CDROM includes:
-</p>
-<ul>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/tools/"; class="urlextern" title="http://geda.seul.org/tools/"; rel="nofollow">gEDA/gaf</a> â?? schematic capture and netlisting</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/tools/ngspice"; class="urlextern" title="http://geda.seul.org/tools/ngspice"; rel="nofollow">ngspice</a> â?? SPICE simulation</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/tools/gnucap"; class="urlextern" title="http://geda.seul.org/tools/gnucap"; rel="nofollow">gnucap</a> â?? analog simulation</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/tools/gspiceui"; class="urlextern" title="http://geda.seul.org/tools/gspiceui"; rel="nofollow">gspiceui</a> â?? <acronym title="Graphical User Interface">GUI</acronym> front end for ngspice/gnucap</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/tools/pcb"; class="urlextern" title="http://geda.seul.org/tools/pcb"; rel="nofollow">pcb</a> â?? PCB layout</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/tools/gerbv"; class="urlextern" title="http://geda.seul.org/tools/gerbv"; rel="nofollow">gerbv</a> â?? Gerber viewer</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/tools/icarus"; class="urlextern" title="http://geda.seul.org/tools/icarus"; rel="nofollow">Icarus Verilog</a> â?? Verilog simulator</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/tools/gtkwave"; class="urlextern" title="http://geda.seul.org/tools/gtkwave"; rel="nofollow">GTKWave</a> â?? Digital waveform viewer</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://wcalc.sourceforge.net/"; class="urlextern" title="http://wcalc.sourceforge.net/"; rel="nofollow">wcalc</a> â?? Transmission line and electromagnetic structure analysis</div>
-</li>
-</ul>
-
-<p>
- At the center of the gEDA suite CDROM is an easy to use installer that automates the building and installing of all the various packages from source â?? making it easy to install the whole suite for the first time user. The gEDA suite CDROM image is available from the <a href="http://geda.seul.org/download.html"; class="urlextern" title="http://geda.seul.org/download.html"; rel="nofollow">download</a> page. <strong>Note: The installer works only with Linux!</strong>
-</p>
-
-</div>
-<!-- SECTION "What is the gEDA suite?" [2920-4441] -->
-<h2><a name="why_what_makes_geda_so_different_from_other_eda_tools" id="why_what_makes_geda_so_different_from_other_eda_tools">Why? What makes gEDA so different from other EDA tools?</a></h2>
-<div class="level2">
-
-<p>
-Tools in the gEDA suite and associated tools have the following characteristics:
-</p>
-<ul>
-<li class="level1"><div class="li"> Free in the monetary sense (no cost).</div>
-</li>
-<li class="level1"><div class="li"> All the file formats and source code are available via the <acronym title="GNU General Public License">GPL</acronym> license. This license grants specific rights to the authors and users of <acronym title="GNU General Public License">GPL</acronym>â??d software.</div>
-</li>
-<li class="level1"><div class="li"> Independence from any one vendor. All gEDA tools come with full source. You may freely redistribute, change, improve and port the tools. You may also distribute your changes, if you follow the terms of the <acronym title="GNU General Public License">GPL</acronym>.</div>
-</li>
-<li class="level1"><div class="li"> No mechanism is used to restrict the use of the tools (like making use of hard disk serial numbers or ethernet addresses to force the software to only run on one machine).</div>
-</li>
-<li class="level1"><div class="li"> No arbitrary, marketeering-driven limitations. Free versions of commercial tools usually include capricious limitations (i.e. limited design size, inability to print, inability to export netlists, etc.) which cripple the program, and force the serious user to buy the real tool. In contrast, the gEDA tools are fully-featured, and do not arbitrarily impose limits on design as a way of extracting money from you.</div>
-</li>
-<li class="level1"><div class="li"> Legacy design protection. Since the software will always be available, and can always be updated to work with updated operating systems or libraries, gEDA tool design files will always be viewable and editable.</div>
-</li>
-<li class="level1"><div class="li"> Open design flow. This means that the tools talk to each other via known and documented means (files / APIs). It is easy to replace a tool or augment the tools with something else if you so desire.</div>
-</li>
-<li class="level1"><div class="li"> Stability - Bugs which cause crashes are investigated immediately and fixed as soon as possible.</div>
-</li>
-<li class="level1"><div class="li"> Minimize bloat and unnecessary features.</div>
-</li>
-<li class="level1"><div class="li"> Run on as many platforms as possible. For gEDA/gaf: GNU/Linux, various other Unix systems.</div>
-</li>
-<li class="level1"><div class="li"> Developed in an open (no secrets) fashion.</div>
-</li>
-<li class="level1"><div class="li"> Strive to be documented.</div>
-</li>
-</ul>
-
-<p>
- gEDA may not have all the latest cutting edge features found in other packages and may be viewed sometimes as being on the trailing edge of EDA technology, but the tools are becoming useful to a lot of people for the above mentioned reasons.
-</p>
-
-</div>
-<!-- SECTION "Why? What makes gEDA so different from other EDA tools?" [4442-6574] -->
-<h2><a name="why_does_the_geda_suite_seem_like_a_collection_of_random_programs_and_not_a_single_integrated_application" id="why_does_the_geda_suite_seem_like_a_collection_of_random_programs_and_not_a_single_integrated_application">Why does the gEDA Suite seem like a collection of random programs, and not a single integrated application?</a></h2>
-<div class="level2">
-
-<p>
-The gEDA suite is indeed a confederacy of somewhat independent programs. This happened for reasons of history: Ales Hvezda started the gEDA project more or less on his own. The original vision was to produce an end-to-end software suite for creating PC boards so that robotics hobbiests could design their own boards. However, as the gEDA project progressed the large magnitude of this task became clear â?? and coding many of the proposed apps had not even begun!
-</p>
-
-<p>
-Meanwhile, other software developers â?? with their own independently written applications â?? found the gEDA project vision compelling. The authors of those applications joined Ales and contributed their programs to the gEDA project. Amongst the contributed projects was â??pcbâ??, a ten year old (at that time) PCB layout program. With the contribution of â??pcbâ??, gEDAâ??s originally planned layout tool â??gpcbâ?? was scuttled. At the same time, other developers contributed analog and digital simulators, waveform viewers, and so on.
-</p>
-
-<p>
-In this way the gEDA suite came together. It is not shared code, or a common user interface which distinguishes the gEDA suite. Rather, the shared vision of an open-source EDA environment is the thread which holds the project together. Today, the gEDA Suite is a collection of many different programs contributed by many different authors. The apps strive to work together, and usually succeed. But the separate beginnings of each program in the suite are still observable. Nonetheless, with a little work the various components of the suite are interoperable, and many people have completed quite complex board designs using the gEDA suite.
-</p>
-
-</div>
-<!-- SECTION "Why does the gEDA Suite seem like a collection of random programs, and not a single integrated application?" [6575-8345] -->
-<h2><a name="so_which_is_better_a_suite_i.e._confederacy_of_programs_or_an_integrated_application" id="so_which_is_better_a_suite_i.e._confederacy_of_programs_or_an_integrated_application">So which is better, a suite (i.e. confederacy) of programs or an integrated application?</a></h2>
-<div class="level2">
-
-<p>
-This is ultimately a matter of religion. Iâ??ll summarize some of the pros and cons (as I see them) of each approach here.
-</p>
-
-</div>
-<!-- SECTION "So which is better, a suite (i.e. confederacy) of programs or an integrated application?" [8346-8570] -->
-<h3><a name="suite_confederacy_pros" id="suite_confederacy_pros">Suite (confederacy) pros:</a></h3>
-<div class="level3">
-<ul>
-<li class="level1"><div class="li"> You can use â??best of breedâ?? applications for each part of the design flow. That is, you can use the standard gEDA flow gschem â?? gsch2pcb â?? pcb to create a PC Board. However, if you think that the open-source application â??pcbâ?? stinks, you can use the flow gschem â?? gnetlist â?? Protel (for example). Recall that gnetlist can output more than twenty different netlist formats! Moreover, if you donâ??t like one component of the flow, you can write another tool to replace it. Now at this time it is true that only a single application generally exists to perform a particular task. However, this situation will likely change with time â?? witness the forking of the â??pcbâ?? project, the contributed netlister <a href="http://www.viasic.com/opensource/"; class="urlextern" title="http://www.viasic.com/opensource/"; rel="nofollow">gnetman</a>, as well as the <a href="http://web.comhem.se/~u31829222/"; class="urlextern" title="http://web.comhem.se/~u31829222/"; rel="nofollow">HEC</a> project. As a general rule, the suite approach offers the greatest freedom to the user.</div>
-</li>
-<li class="level1"><div class="li"> The design flow has a lot of natural breakpoints. These occur where one design tool completes its job and writes out a file (i.e. gschem writes out a .sch file, or gnetlist writes out a SPICE netlist). At this point, you can easily break into the flow and write scripts which process and/or munge the design data. For big, advanced designs, this is a real advantage to the â??design suiteâ?? approach. This advantage may appeal only to the â??power userâ??, but note its importance: professional-grade EDA suites (Synopsys, Xilinx) also work the same way.</div>
-</li>
-<li class="level1"><div class="li"> Usage of an applications suite can be automated using a Makefile, or even a <acronym title="Practical Extraction and Report Language">Perl</acronym> script. ASIC designers do this all the time with their design and synthesis tools. Some gEDA users have stated on the e-mail list that they do this too, and point to it as an important feature of the gEDA suite.</div>
-</li>
-<li class="level1"><div class="li"> Scalability: A monolithic application is almost always developed by a lone developer who has a single-minded vision for his program. This developer can enforce stylistic and UI standards throughout all his tools. The problem with this is that a single developer â?? even one who is uniquely gifted â?? can only write one or two parts of an EDA application. Therefore, any open-source, monolithic EDA app will likely always be limited in scope and features by the abilities of a single developer. (I would love to be proven wrong on this point. I welcome counter-examples, but none have come to my attention as of this writing.) On the other hand, a confederacy of developers working independently on their own apps â?? but meanwhile contributing to a greater whole â?? can create a very large and capable EDA environment indeed.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Suite (confederacy) pros:" [8571-11215] -->
-<h3><a name="suite_confederacy_cons" id="suite_confederacy_cons">Suite (confederacy) cons:</a></h3>
-<div class="level3">
-<ul>
-<li class="level1"><div class="li"> More confusing to new users, since they donâ??t know the flow right off the bat. That is, they actually need to <acronym title="Read The Fine Manual">RTFM</acronym> to know what tool to run next. Good documentation helps (thatâ??s why youâ??re reading this), but documentation is always second choice behind developing an intuitive application interface.</div>
-</li>
-<li class="level1"><div class="li"> Different programs have different UI conventions (i.e. menu organization is different, keyboard or mouse bindings are different). This can be uncomfortable to those who arenâ??t familiar with the programs.</div>
-</li>
-<li class="level1"><div class="li"> Since no assumptions are made about the design flow, schematic symbols are necessarily <a href="geda_faq-gschem.html" class="wikilink1" title="geda:faq-gschem">light</a>. This forces the user to spend more time attaching e.g. footprint attributes to his design. Moreover, the user must spend more time actually researching which footprints to use. However, a good suite (like the gEDA suite) will offer multiple methods to perform this task (e.g. gattrib, <acronym title="Practical Extraction and Report Language">Perl</acronym> scripts to populate footprints, etc.).</div>
-</li>
-<li class="level1"><div class="li"> Some developers are more energetic than others, or have more free time. Therefore, some programs in a suite will be more developed (and less buggy) than others. Unfortunately, a single buggy program in a suite can unfairly taint a new userâ??s perception of the entire suite.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Suite (confederacy) cons:" [11216-12551] -->
-<h3><a name="monolithic_application_pros" id="monolithic_application_pros">Monolithic application pros:</a></h3>
-<div class="level3">
-<ul>
-<li class="level1"><div class="li"> A single, unified design environment is easier for new users to grasp. UI conventions may be harmonized. The tool might be intuitive enough that it can be driven without needing to <acronym title="Read The Fine Manual">RTFM</acronym>.</div>
-</li>
-<li class="level1"><div class="li"> Schematic capture symbols can be heavy, so less work is required in attaching attributes to each symbol in a schematic.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Monolithic application pros:" [12552-12906] -->
-<h3><a name="monolithic_application_cons" id="monolithic_application_cons">Monolithic application cons:</a></h3>
-<div class="level3">
-<ul>
-<li class="level1"><div class="li"> Not infinitely scalable. One developer canâ??t do everything, no matter how smart. Therefore, a monolithic app will never approach the size or power of a suite developed by a confederacy of programmers.</div>
-</li>
-<li class="level1"><div class="li"> Lack of choice. If the developer doesnâ??t like your way of doing things, you have no choice. Even if you submit patches to enable your way of performing a task, there is a chance the main developer will ignore or reject your patches. This is probably not an issue for newbies, but for â??power usersâ?? it represents a problem.</div>
-</li>
-<li class="level1"><div class="li"> Risk. If the developer quits, the code becomes abandoned, and the users suffer. This effectively happened to the program <a href="http://sourceforge.net/projects/xtrkcad"; class="urlextern" title="http://sourceforge.net/projects/xtrkcad"; rel="nofollow">XTrkCAD</a>, a CAD program for designing model railroads. The author of this program quit developing it, but thankfully placed his stuff on Sourceforge so that the program wouldnâ??t simply disappear. Unfortunately, without the original developerâ??s involvement, the code languished. Patches contributed to the project went to /dev/null. Eventually, a coalition of concerned user/developers created a <a href="http://xtrkcad-fork.sourceforge.net/"; class="urlextern" title="http://xtrkcad-fork.sourceforge.net/"; rel="nofollow">fork</a> of the code to enable further development. However, work on the forked code has been piecemeal and sporadic. (Hopefully, this will change someday.) Meanwhile, for the ordinary user, the fact that the original developer quit represents a catastrophe.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Monolithic application cons:" [12907-14349] -->
-<h2><a name="tool_xxx_is_missing_critical_feature_yyy_what_can_i_do" id="tool_xxx_is_missing_critical_feature_yyy_what_can_i_do">Tool XXX is missing critical feature YYY! What can I do?</a></h2>
-<div class="level2">
-
-<p>
-Newbies sometimes show up on the gEDA mailing lists and flame the project for missing features, perceived bugs, and supppoesd UI quirks. The gEDA developers are very interested in receiving constructive feedback and criticism, so we do welcome feature requests and bug reports. But please keep in mind that the developers are full-time professional EEs or software engineers, and work on gEDA as an unpaid, fun hobby. Unconstructive or ill-informed flames are not the way to get new features implemented.
-</p>
-
-<p>
-If you need a new feature implemented in one of the gEDA tools, here are your options:
-</p>
-<ul>
-<li class="level1"><div class="li"> Write it yourself. The code is open and available for everybody to see, understand, and modify. If you have implemented a new feature, please <a href="http://sourceforge.net/tracker/?atid=818428&group_id=161080&func=browse"; class="urlextern" title="http://sourceforge.net/tracker/?atid=818428&group_id=161080&func=browse"; rel="nofollow">submit your patches</a> to the project; chances are good that they will be incorporated into the main development branch.</div>
-</li>
-</ul>
-<ul>
-<li class="level1"><div class="li"> Ask politely on the gEDA e-mail lists. If your feature request is simple, or of interest to one of the developers, itâ??s possible that somebody will implement your feature. If itâ??s more complicated, itâ??s likely that the feature is already under discussion amongst the developers, but nobody has enough spare time to implement it. (You can also submit feature requests via the <a href="http://sourceforge.net/tracker/?atid=818429&group_id=161080&func=browse"; class="urlextern" title="http://sourceforge.net/tracker/?atid=818429&group_id=161080&func=browse"; rel="nofollow">SourceForge feature requests tracker.</a>) Please donâ??t rant or flame on the e-mail lists, since you will likely be flamed right back and you wonâ??t get your feature either. Why waste your time?</div>
-</li>
-</ul>
-<ul>
-<li class="level1"><div class="li"> If the above possibilities donâ??t work for you, hire an open-source developer to write the feature for you! Itâ??s amazing how often this possibility is ignored. People willing to pay $25,000 – $100,000 for commercial EDA tools will balk at paying a teen-age programming whiz $10/hr to re-create the same features in the gEDA Suite. Why? If youâ??re an educator, consider hiring some students for a UROP project to work on gEDA. If you run a business, hire a teenager or somebody fresh out of school! And if you want seasoned help, you can (soon) turn to some of the main gEDA developers who do consulting. Find them at <a href="http://www.gedaconsulting.com/"; class="urlextern" title="http://www.gedaconsulting.com"; rel="nofollow">www.gedaconsulting.com</a>. <img src="lib/images/smileys/fixme.gif" class="middle" alt="FIXME" /></div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Tool XXX is missing critical feature YYY! What can I do?" [14350-16658] -->
-<h2><a name="what_license_does_geda_use" id="what_license_does_geda_use">What license does gEDA use?</a></h2>
-<div class="level2">
-
-<p>
-All of the tools and associated files in gEDA will be released under the GNU General Public License version 2 (<acronym title="GNU General Public License">GPL</acronym>), from the Free Software Foundation.
-</p>
-
-<p>
-From the license:
-</p>
-
-<p>
-â??When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things."
-</p>
-
-<p>
-This cannot be stressed enough: <strong>gEDA is GPLed software</strong>. Therefore nothing proprietary can be distributed with gEDA like part libraries from proprietary EDA products. Conversion programs for proprietary libraries will be available, but any converted files which are part of a proprietary product must never find their way into gEDA. Contributed files must be GPLable (or be placed under another free license). Please keep this in mind if you wish to contribute something.
-</p>
-
-<p>
-Even though the focus of gEDA is GPLed software, other software licenses are more than welcome to be mixed with the existing software, as long as they are compatible with the <acronym title="GNU General Public License">GPL</acronym>.
-</p>
-
-</div>
-<!-- SECTION "What license does gEDA use?" [16659-17940] -->
-<h2><a name="where_can_i_get_more_information_about_and_download_geda" id="where_can_i_get_more_information_about_and_download_geda">Where can I get more information about and download gEDA?</a></h2>
-<div class="level2">
-
-<p>
-The official website is <a href="http://geda.seul.org/"; class="urlextern" title="http://geda.seul.org/"; rel="nofollow">gEDA Project</a> hosted by the <a href="http://www.seul.org/"; class="urlextern" title="http://www.seul.org/"; rel="nofollow">SEUL Project</a>. The European mirror is at <a href="http://ftp.sunet.se/geda/"; class="urlextern" title="http://ftp.sunet.se/geda/"; rel="nofollow">European gEDA Project mirror</a> hosted by Swedish University Network - Sweden, Northern Europe.
-</p>
-
-<p>
-There are several mailing lists. Please look at the mailing list <a href="http://geda.seul.org/mailinglist"; class="urlextern" title="http://geda.seul.org/mailinglist"; rel="nofollow">info page</a> for how to subscribe and post.
-</p>
-
-<p>
-You can download all the software, including the gEDA suite CDROM, from the <a href="http://geda.seul.org/download.html"; class="urlextern" title="http://geda.seul.org/download.html"; rel="nofollow">download</a> page.
-</p>
-
-<p>
-You can find the latest set of documentation on the top-level <a href="http://geda.seul.org/docs/"; class="urlextern" title="http://geda.seul.org/docs/"; rel="nofollow">documentation</a> page.
-</p>
-
-<p>
-Come to the Free EDA Users Group (Freedog) meeeting in Cambridge, MA. The meeting is at 7 PM on the first Wednesday of each month at the <a href="http://www.starbucks.com/retail/locator/MapResults.aspx?a=1&StoreKey=93728&IC_O=42.3599350625432%3a-71.1021394862385%3a32%3a02139+(postal+code)%2c+Massachusetts%2c+United+States&GAD1_O=&GAD2_O=&GAD3_O=02139+(postal+code)%2c+Massachusetts%2c+United+States&GAD4_O=&radius=5&countryID=244&dataSource=MapPoint.NA" class="urlextern" title="http://www.starbucks.com/retail/locator/MapResults.aspx?a=1&StoreKey=93728&IC_O=42.3599350625432%3a-71.1021394862385%3a32%3a02139+(postal+code)%2c+Massachusetts%2c+United+States&GAD1_O=&GAD2_O=&GAD3_O=02139+(postal+code)%2c+Massachusetts%2c+United+States&GAD4_O=&radius=5&countryID=244&dataSource=MapPoint.NA" rel="nofollow">Kendal Square Starbucks</a>.
-</p>
-
-</div>
-<!-- SECTION "Where can I get more information about and download gEDA?" [17941-19141] -->
-<h2><a name="okay_how_do_i_start_using_geda" id="okay_how_do_i_start_using_geda">Okay, how do I start using gEDA?</a></h2>
-<div class="level2">
-
-<p>
-The most important thing to do is to read and understand Bill Wilsonâ??s excellent <a href="geda_gsch2pcb_tutorial.html" class="wikilink1" title="geda:gsch2pcb_tutorial">gschem -> gsch2pcb -> PCB</a> tutorial. This should get you started.
-</p>
-
-<p>
-Also be sure to check out the other <a href="http://geda.seul.org/docs"; class="urlextern" title="http://geda.seul.org/docs"; rel="nofollow">gEDA documentation</a>. An installation guide is contained in this Wiki, as is some general information about how to use the tools. Spend some time browsing, download the gEDA Suite, and try it out for yourself!
-</p>
-
-</div>
-<!-- SECTION "Okay, how do I start using gEDA?" [19142-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/geda_fbabgapp.html b/docs/wiki/geda_fbabgapp.html
deleted file mode 100644
index a683380..0000000
--- a/docs/wiki/geda_fbabgapp.html
+++ /dev/null
@@ -1,223 +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>geda:fbabgapp</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="keywords" content="geda,fbabgapp" />
-<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/geda:fbabgapp?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:fbabgapp"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:fbabgapp"; />
-<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="#forward_backward_annotation_between_geda_gaf_and_pads_powerpcb" class="toc">Forward/Backward Annotation Between gEDA/gaf and PADS PowerPCB</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#forward_annotation_of_geda_schematic_changes_to_pads_powerpcb_layout" class="toc">Forward Annotation of gEDA Schematic Changes to PADS PowerPCB Layout</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#overview" class="toc">Overview</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#detailed_forward_annotation_procedure" class="toc">Detailed Forward Annotation Procedure</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#back_annotation_of_pads_powerpcb_layout_changes_to_geda_schematic" class="toc">Back Annotation of PADS PowerPCB Layout Changes to gEDA Schematic</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#detailed_backannotation_procedure" class="toc">Detailed Backannotation Procedure</a></span></div></li></ul>
-</li></ul>
-</li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="forward_backward_annotation_between_geda_gaf_and_pads_powerpcb" id="forward_backward_annotation_between_geda_gaf_and_pads_powerpcb">Forward/Backward Annotation Between gEDA/gaf and PADS PowerPCB</a></h1>
-<div class="level1">
-
-<p>
-by: Dan McMahill
-</p>
-
-<p>
-This document is released under <a href="http://www.gnu.org/copyleft/fdl.html"; class="urlextern" title="http://www.gnu.org/copyleft/fdl.html"; rel="nofollow">GFDL</a>
-</p>
-
-<p>
-March 6th, 2003
-</p>
-
-</div>
-<!-- SECTION "Forward/Backward Annotation Between gEDA/gaf and PADS PowerPCB" [1-191] -->
-<h2><a name="forward_annotation_of_geda_schematic_changes_to_pads_powerpcb_layout" id="forward_annotation_of_geda_schematic_changes_to_pads_powerpcb_layout">Forward Annotation of gEDA Schematic Changes to PADS PowerPCB Layout</a></h2>
-<div class="level2">
-
-</div>
-<!-- SECTION "Forward Annotation of gEDA Schematic Changes to PADS PowerPCB Layout" [192-272] -->
-<h2><a name="overview" id="overview">Overview</a></h2>
-<div class="level2">
-
-<p>
-Forward annotation is the process of updating a layout to reflect changes made in the schematic. This process is used when, for example, a new component is added to a schematic and needs to be included in the layout. This section describes how to forward annotate changes in a gEDA schematic to a PADS PowerPCB layout.<br/>
- PADS implements forward annotation through the use of an ECO (Engineering Change Order) file. The ECO file describes the differences between a current design and the desired design. PADS generates the ECO file by performing a netlist comparison between a new netlist file and the netlist contained in the current layout.
-</p>
-
-</div>
-<!-- SECTION "Overview" [273-936] -->
-<h2><a name="detailed_forward_annotation_procedure" id="detailed_forward_annotation_procedure">Detailed Forward Annotation Procedure</a></h2>
-<div class="level2">
-
-<p>
-This procedure assumes you have a board layout open in PADS and that you have made your schematic changes in gschem. For the purposes of illustration, assume your schematic is split into two pages in the files pg1.sch and pg2.sch.
-</p>
-<ul>
-<li class="level1"><div class="li"> Create an updated PADS netlist by running:<br/>
- <strong><code>gnetlist -g pads -o mynet.asc pg1.sch pg2.sch</code></strong><br/>
- This will create the netlist file <strong><code>mynet.asc</code></strong>.</div>
-</li>
-<li class="level1"><div class="li"> Make a backup copy of your PADS layout in case things fail in a destructive way.</div>
-</li>
-<li class="level1"><div class="li"> From within PADS, choose the â??Tools → Compare Netlistâ?? menu item and choose the following options in the form:</div>
-</li>
-</ul>
-<table class="inline">
- <tr>
- <td>original design to compare</td><td>use current PCB design</td>
- </tr>
- <tr>
- <td>new design with changes</td><td>mynet.asc</td>
- </tr>
- <tr>
- <td>â??</td><td>generate differences report</td>
- </tr>
- <tr>
- <td>â??</td><td>generate eco file</td>
- </tr>
- <tr>
-
- </tr>
- <tr>
- <td colspan="2">comparison options</td>
- </tr>
- <tr>
- <td>â??</td><td>compare only ECO registered parts</td>
- </tr>
- <tr>
- <td colspan="2"> </td>
- </tr>
- <tr>
- <td colspan="2">attribute comparison level</td>
- </tr>
- <tr>
- <td>â??</td><td>ignore all attributes</td>
- </tr>
-</table>
-
-<p>
- Click the OK button to create the ECO file.
-</p>
-<ul>
-<li class="level1"><div class="li"> Examine the ECO file to make sure it looks ok (the ECO file is a text file which can be viewed with any text editor).</div>
-</li>
-<li class="level1"><div class="li"> From within PADS, choose the â??File → Import…â?? menu item. Locate and choose the ECO file created previously.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Detailed Forward Annotation Procedure" [937-2135] -->
-<h2><a name="back_annotation_of_pads_powerpcb_layout_changes_to_geda_schematic" id="back_annotation_of_pads_powerpcb_layout_changes_to_geda_schematic">Back Annotation of PADS PowerPCB Layout Changes to gEDA Schematic</a></h2>
-<div class="level2">
-
-<p>
-Backannotation is the process of updating schematics to reflect changes made in the layout. This process is used, for example, when the reference designators have been renumbered on the layout, when pins have been swapped (e.g., on an AND gate), or slots have been swapped (e.g., on a multi-gate package). This section describes how to backannotate changes in a PADS PowerPCB layout to a gEDA schematic. The PADS PowerPCB tool supports three types of schematic backannotation:
-</p>
-<ol>
-<li class="level1"><div class="li"> Reference designator changes. This is often times used at the end of a layout to give components which are geographically close a set of reference designators which are numerically close.</div>
-</li>
-<li class="level1"><div class="li"> Slot swapping. This is commonly found in digital designs where there may be multiple identical gates in a single package. For example, you may wish to swap which slot is used in a hex inverter.</div>
-</li>
-<li class="level1"><div class="li"> Pin swapping. During layout, the designer may wish to swap equivalent pins on a chip. For example, the two inputs on a NAND gate.</div>
-</li>
-</ol>
-
-<p>
- Currently only reference designator changes are automatically processed by the PADS to gschem backannotation tool. The slot and pin swapping changes are provided in a report which the schematic designer must use to manually correct the schematic.
-</p>
-
-</div>
-<!-- SECTION "Back Annotation of PADS PowerPCB Layout Changes to gEDA Schematic" [2136-3463] -->
-<h3><a name="detailed_backannotation_procedure" id="detailed_backannotation_procedure">Detailed Backannotation Procedure</a></h3>
-<div class="level3">
-
-<p>
-This procedure assumes you have a board layout open in PADS. For the purposes of illustration, assume your schematic is split into two pages in the files pg1.sch and pg2.sch.
-</p>
-<ul>
-<li class="level1"><div class="li"> Create an up to date PADS netlist by running:<br/>
- <strong><code>gnetlist -g pads -o mynet.asc pg1.sch pg2.sch</code></strong><br/>
- This will create the netlist file <strong><code>mynet.asc</code></strong>.</div>
-</li>
-<li class="level1"><div class="li"> From within PADS, choose the â??Tools → Compare Netlistâ?? menu item and choose the following options in the form:</div>
-</li>
-</ul>
-<table class="inline">
- <tr>
- <td>original design to compare</td><td>mynet.asc</td>
- </tr>
- <tr>
- <td>new design with changes</td><td>use current PCB design</td>
- </tr>
- <tr>
- <td>â??</td><td>generate differences report</td>
- </tr>
- <tr>
- <td>â??</td><td>generate eco file</td>
- </tr>
- <tr>
- <td colspan="2"> </td>
- </tr>
- <tr>
- <td colspan="2">comparison options</td>
- </tr>
- <tr>
- <td>â??</td><td>compare only ECO registered parts</td>
- </tr>
- <tr>
- <td colspan="2"> </td>
- </tr>
- <tr>
- <td colspan="2">attribute comparison level</td>
- </tr>
- <tr>
- <td>â??</td><td>ignore all attributes</td>
- </tr>
-</table>
-
-<p>
- Click the OK button to create the ECO file.
-</p>
-<ul>
-<li class="level1"><div class="li"> Examine the ECO file to make sure it looks ok (the ECO file is a text file which can be viewed with any text editor).</div>
-</li>
-<li class="level1"><div class="li"> Make a backup copy of your gEDA schematic files in case things fail in a destructive way.</div>
-</li>
-<li class="level1"><div class="li"> Run:<br/>
- <strong><code>pads_backannotate file.eco pg1.sch pg2.sch | tee backanno.log</code></strong><br/>
- where <strong><code>file.eco</code></strong> is the name of the ECO file created previously and <strong><code>pg1.sch</code></strong> and <strong><code>pg2.sch</code></strong> are all of your schematic pages. This will apply the reference designator change portion of the ECO file and also generate a list of pin and slot swapping which must be performed by hand. The file <strong><code>backanno.log</code></strong> will contain a log of the session that can be refered to when performing the pin and slot swapping.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Detailed Backannotation Procedure" [3464-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/geda_fc1.html b/docs/wiki/geda_fc1.html
deleted file mode 100644
index c33a924..0000000
--- a/docs/wiki/geda_fc1.html
+++ /dev/null
@@ -1,64 +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>geda:fc1</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-05-24T22:27:26-0400" />
-<meta name="keywords" content="geda,fc1" />
-<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/geda:fc1?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:fc1"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:fc1"; />
-<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="#installer_2005080x_on_fedora_core_1_install_notes" class="toc">Installer 2005080X on Fedora Core 1 install notes</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#prerequisites" class="toc">Prerequisites:</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#problems" class="toc">Problems:</a></span></div></li></ul>
-</li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="installer_2005080x_on_fedora_core_1_install_notes" id="installer_2005080x_on_fedora_core_1_install_notes">Installer 2005080X on Fedora Core 1 install notes</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "Installer 2005080X on Fedora Core 1 install notes" [1-64] -->
-<h2><a name="prerequisites" id="prerequisites">Prerequisites:</a></h2>
-<div class="level2">
-
-<p>
-When you install FC1, make sure you install the â??workstationâ?? version, and not the â??desktopâ?? version. (You are presented with this choice when you first install the distribution off of the distribution media.) The â??workstationâ?? version includes important header files and other tools which are necessary to build many components of the gEDA Suite using the installer.
-</p>
-
-</div>
-<!-- SECTION "Prerequisites:" [65-472] -->
-<h2><a name="problems" id="problems">Problems:</a></h2>
-<div class="level2">
-
-<p>
-The installer has been thoroughly tested on this platform. No problems are known, and none have been reported.
-</p>
-
-</div>
-<!-- SECTION "Problems:" [473-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/geda_fc2.html b/docs/wiki/geda_fc2.html
deleted file mode 100644
index e93dff0..0000000
--- a/docs/wiki/geda_fc2.html
+++ /dev/null
@@ -1,64 +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>geda:fc2</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-05-24T22:27:26-0400" />
-<meta name="keywords" content="geda,fc2" />
-<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/geda:fc2?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:fc2"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:fc2"; />
-<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="#installer_2005080x_on_fedora_core_2_install_notes" class="toc">Installer 2005080X on Fedora Core 2 install notes</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#prerequisites" class="toc">Prerequisites:</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#problems" class="toc">Problems:</a></span></div></li></ul>
-</li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="installer_2005080x_on_fedora_core_2_install_notes" id="installer_2005080x_on_fedora_core_2_install_notes">Installer 2005080X on Fedora Core 2 install notes</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "Installer 2005080X on Fedora Core 2 install notes" [1-64] -->
-<h2><a name="prerequisites" id="prerequisites">Prerequisites:</a></h2>
-<div class="level2">
-
-<p>
-When you install FC2, make sure you install the â??workstationâ?? version, and not the â??desktopâ?? version. (You are presented with this choice when you first install the distribution off of the distribution media.) The â??workstationâ?? version includes important header files and other tools which are necessary to build many components of the gEDA Suite using the installer.
-</p>
-
-</div>
-<!-- SECTION "Prerequisites:" [65-472] -->
-<h2><a name="problems" id="problems">Problems:</a></h2>
-<div class="level2">
-
-<p>
-The installer has been thoroughly tested on this platform. No problems are known, and none have been reported.
-</p>
-
-</div>
-<!-- SECTION "Problems:" [473-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/geda_fc3.html b/docs/wiki/geda_fc3.html
deleted file mode 100644
index 436db2d..0000000
--- a/docs/wiki/geda_fc3.html
+++ /dev/null
@@ -1,64 +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>geda:fc3</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-05-24T22:27:26-0400" />
-<meta name="keywords" content="geda,fc3" />
-<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/geda:fc3?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:fc3"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:fc3"; />
-<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="#installer_2005080x_on_fedora_core_3_install_notes" class="toc">Installer 2005080X on Fedora Core 3 install notes</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#prerequisites" class="toc">Prerequisites:</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#problems" class="toc">Problems:</a></span></div></li></ul>
-</li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="installer_2005080x_on_fedora_core_3_install_notes" id="installer_2005080x_on_fedora_core_3_install_notes">Installer 2005080X on Fedora Core 3 install notes</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "Installer 2005080X on Fedora Core 3 install notes" [1-64] -->
-<h2><a name="prerequisites" id="prerequisites">Prerequisites:</a></h2>
-<div class="level2">
-
-<p>
-When you install FC3, make sure you install the â??workstationâ?? version, and not the â??desktopâ?? version. (You are presented with this choice when you first install the distribution off of the distribution media.) The â??workstationâ?? version includes important header files and other tools which are necessary to build many components of the gEDA Suite using the installer.
-</p>
-
-</div>
-<!-- SECTION "Prerequisites:" [65-472] -->
-<h2><a name="problems" id="problems">Problems:</a></h2>
-<div class="level2">
-
-<p>
-No problems are known, and none have been reported.
-</p>
-
-</div>
-<!-- SECTION "Problems:" [473-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/geda_fc4.html b/docs/wiki/geda_fc4.html
deleted file mode 100644
index 08e58a4..0000000
--- a/docs/wiki/geda_fc4.html
+++ /dev/null
@@ -1,156 +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>geda:fc4</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-05-24T22:27:26-0400" />
-<meta name="keywords" content="geda,fc4" />
-<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/geda:fc4?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:fc4"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:fc4"; />
-<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="#installer_20060825_on_fedora_core_4_install_notes" class="toc">Installer 20060825 on Fedora Core 4 install notes</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#installer_2005080x_on_fedora_core_4_install_notes" class="toc">Installer 2005080X on Fedora Core 4 install notes</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#prerequisites" class="toc">Prerequisites:</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#problems" class="toc">Problems:</a></span></div></li></ul>
-</li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="installer_20060825_on_fedora_core_4_install_notes" id="installer_20060825_on_fedora_core_4_install_notes">Installer 20060825 on Fedora Core 4 install notes</a></h1>
-<div class="level1">
-
-<p>
-The latest CD installer will work fine on Fedora Core 4. All gEDA Suite programs now compile happily with gcc-4.X. When you build your FC4 system, make sure you select â??devlopement worstationâ?? as your system type, and include as many -devel packages into the build as you can. The following packages are particularly important:
-</p>
-<ul>
-<li class="level1"><div class="li"> gtk-devel</div>
-</li>
-<li class="level1"><div class="li"> gnome-devel</div>
-</li>
-<li class="level1"><div class="li"> guile-devel</div>
-</li>
-<li class="level1"><div class="li"> tcl-devel</div>
-</li>
-<li class="level1"><div class="li"> tk-devel</div>
-</li>
-</ul>
-
-<p>
-If you are missing most of these -devel packages, the installer will do the right thing, but itâ??s better to pre-install them so the installer doesnâ??t have to become root to do it.
-</p>
-
-</div>
-<!-- SECTION "Installer 20060825 on Fedora Core 4 install notes" [1-650] -->
-<h1><a name="installer_2005080x_on_fedora_core_4_install_notes" id="installer_2005080x_on_fedora_core_4_install_notes">Installer 2005080X on Fedora Core 4 install notes</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "Installer 2005080X on Fedora Core 4 install notes" [651-714] -->
-<h2><a name="prerequisites" id="prerequisites">Prerequisites:</a></h2>
-<div class="level2">
-
-<p>
-When you install FC4, make sure you install the â??workstationâ?? version, and not the â??desktopâ?? version. (You are presented with this choice when you first install the distribution off of the distribution media.) The â??workstationâ?? version includes important header files and other tools which are necessary to build many components of the gEDA Suite using the installer.
-</p>
-
-<p>
-Also, the following additional RPMs are required:
-</p>
-<ul>
-<li class="level1"><div class="li"> guile-1.6.7-devel</div>
-</li>
-<li class="level1"><div class="li"> gettext-XX-devel.</div>
-</li>
-<li class="level1"><div class="li"> compat-gcc-3.2.3-47.fc4.i386.rpm</div>
-</li>
-<li class="level1"><div class="li"> compat-gcc-32-c++-3.2.3-47.fc4.i386.rpm</div>
-</li>
-<li class="level1"><div class="li"> compat-libstdc++-33-0:3.2.3-47.fc4.i386.rpm (installed automatically when g++ is installed by rpm)</div>
-</li>
-</ul>
-
-<p>
- These RPMs are not automatically installed by RedHatâ??s installer; you need to install them manually. The devel packages live on the 4th FC4 disk. The gcc compatability compiler lives on the 3rd FC4 disk. Install all these packages before trying to build the gEDA Suite.
-</p>
-
-<p>
-Before installing the gEDA Suite on an FC4 system, you should set the CC environment variable to point to gcc32. This is explained further in the â??Problemsâ?? section below.
-</p>
-
-</div>
-<!-- SECTION "Prerequisites:" [715-1851] -->
-<h2><a name="problems" id="problems">Problems:</a></h2>
-<div class="level2">
-
-<p>
-The 200508XX installer will fail on FC4 systems. There seem to be several independent problems:
-</p>
-<ol>
-<li class="level1"><div class="li"> The installer doesnâ??t find guile, even though it comes pre-installed on the platform.<br/>
- The problem here is that the installer tries to find guile by issuing the â??guile-configâ?? command. This command lives in the guile-devel RPM which is not installed by default (see above). To fix the problem, install the guile-devel RPM which lives on the FC4 install CD no. 4.</div>
-</li>
-<li class="level1"><div class="li"> The installer doesnâ??t find gettext, even though it comes pre-installed on the platform. Gettext is used by gschem, so this error is raised during the configure stage for gschem.<br/>
- Again, the gettext header files live in the gettext-devel RPM which is not installed by default (see above). To fix this problem, install the gettext-devel RPM which lives on the FC4 install CD no. 4.</div>
-</li>
-<li class="level1"><div class="li"> Many different applications (e.g. GTKWave, GSpiceUI, Icarus Verilog) fail during compilation. The error message typically says something about a problem involving a â??typeâ??.</div>
-</li>
-</ol>
-
-<p>
- This problem obtains because FC4 incorporates the new gcc-4.0 compiler. Gcc-4.0 incorporates much stricter type checking than the older gcc versions. This has caused many open-source applications to fail to compile.
-</p>
-
-<p>
-Fortunately, RedHat still provides the older version of gcc on the FC4 disks. This version of gcc is called â??gcc32â??. It is not installed as part of the normal installation, so you must install it yourself. The RPM lives on the FC4 install media, disk 3, and is called â??compat-gcc-32-3.2.3-47.fc4.i386.rpmâ??. Allow rpm to install any dependencies it finds.
-</p>
-
-<p>
-A similar situation holds for the C++ compiler g++. You need to install the older version too; get it on the FC4 disk 4. It is called â??compat-gcc-32-c++-3.2.3-47.fc4.i386.rpmâ??. Also install any dependencies found by rpm when you install these pacakges.
-</p>
-
-<p>
-Once they are installed, set the gcc environment variables as follows:
-</p>
-
-<p>
-for bash:
-</p>
-<pre class="code">export CC=gcc32
-export CXX=g++32</pre>
-
-<p>
-for csh:
-</p>
-<pre class="code">setenv CC gcc32
-setenv CXX g++32</pre>
-
-<p>
-and then run the installer. Make sure you run the installer from the same window as where you set the CC environment variable!
-</p>
-
-</div>
-<!-- SECTION "Problems:" [1852-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/geda_fedora_rpm_installation.html b/docs/wiki/geda_fedora_rpm_installation.html
deleted file mode 100644
index e3785e0..0000000
--- a/docs/wiki/geda_fedora_rpm_installation.html
+++ /dev/null
@@ -1,317 +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>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-08-24T19:50:12-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/"; />
-<link rel="contents" href="http://geda.seul.org/wiki/geda:fedora_rpm_installation?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:fedora_rpm_installation"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:fedora_rpm_installation"; />
-<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="#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="#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="#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>
-</div>
-
-
-
-<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" [1-54] -->
-<h2><a name="geda_gaf_for_fedora" id="geda_gaf_for_fedora">gEDA/gaf for fedora</a></h2>
-<div class="level2">
-
-<p>
- 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>
- 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 "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\* 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>
-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 "The easiest way" [871-1851] -->
-<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 "Compile it yourself" [1852-2506] -->
-<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>
-
-<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="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 "Rebuild your own rpms" [2507-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/geda_file_format_spec.html b/docs/wiki/geda_file_format_spec.html
deleted file mode 100644
index 61282a3..0000000
--- a/docs/wiki/geda_file_format_spec.html
+++ /dev/null
@@ -1,1296 +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>geda:file_format_spec</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2008-01-26T18:49:35-0500" />
-<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/"; />
-<link rel="contents" href="http://geda.seul.org/wiki/geda:file_format_spec?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:file_format_spec"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:file_format_spec"; />
-<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="#geda_gaf_file_format_document" class="toc">gEDA/gaf File Format Document</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#overview" class="toc">Overview</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#coordinate_space" class="toc">Coordinate Space</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#filenames" class="toc">Filenames</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#object_types" class="toc">Object types</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#version" class="toc">version</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#line" class="toc">line</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#picture" class="toc">picture</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#box" class="toc">box</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#circle" class="toc">circle</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#arc" class="toc">arc</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#text" class="toc">text</a></span></div></li>
-<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="#bus" class="toc">bus</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#pin" class="toc">pin</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#component" class="toc">component</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#font" class="toc">font</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#colors" class="toc">Colors</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#attributes" class="toc">Attributes</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#embedded_components" class="toc">Embedded Components</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#document_revision_history" class="toc">Document Revision History</a></span></div></li></ul>
-</li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="geda_gaf_file_format_document" id="geda_gaf_file_format_document">gEDA/gaf File Format Document</a></h1>
-<div class="level1">
-
-<p>
-by: Ales V. Hvezda, ahvezda@xxxxxxxxxxxxx
-</p>
-
-<p>
-This document is released under <a href="http://www.gnu.org/copyleft/fdl.html"; class="urlextern" title="http://www.gnu.org/copyleft/fdl.html"; rel="nofollow">GFDL</a>
-</p>
-
-<p>
-December 31st, 2003
-</p>
-
-</div>
-<!-- SECTION "gEDA/gaf File Format Document" [1-187] -->
-<h2><a name="overview" id="overview">Overview</a></h2>
-<div class="level2">
-
-<p>
-This file is the official documentation for the file formats in gEDA/gaf (gschem And Friends). The primary file format used in gEDA/gaf is the schematic/symbol format. Files which end with .sch or .sym are schematics or symbol files. Until there is another file type in gEDA/gaf, then this document will only cover the symbol/schematic file format.<br/>
- This file format document is current as of gEDA/gaf version 20040111. This document covers file format version 1.<br/>
- Note, this file format and any other file formats associated with gEDA are placed under the General Public License (<acronym title="GNU General Public License">GPL</acronym>) version 2.0. The gEDA/gaf symbol and schematic file format is Copyright (C) 1998-2004 Ales Hvezda.
-</p>
-
-</div>
-<!-- SECTION "Overview" [188-896] -->
-<h2><a name="coordinate_space" id="coordinate_space">Coordinate Space</a></h2>
-<div class="level2">
-
-<p>
-All coordinates are in mils (1/1000 or an inch). This is an arbitrary decision. Remember in there is no concept of physical lengths/dimensions in schematics and symbols (for schematic capture only).<br/>
-
-</p>
-<ul>
-<li class="level1"><div class="li"> Origin is in lower left hand corner.</div>
-</li>
-<li class="level1"><div class="li"> The size of the coordinate space is unlimited, but it is recommended that all objects stay within (120.0, 90.0) (x, y inches).</div>
-</li>
-<li class="level1"><div class="li"> It is generally advisable to have positive x and y coordinates, however, negative coordinates work too, but not recommended.</div>
-</li>
-</ul>
-
-<p>
- The following figure shows how the coordinate space is setup:
-</p>
-<table class="inline">
- <tr>
- <td><a href="_detail/geda_coordinatespace.html" class="media" title="geda:coordinatespace.jpg"><img src="_media/geda_coordinatespace.jpg" class="mediaright" title=":geda:coordinatespace.jpg " alt=":geda:coordinatespace.jpg " /></a></td>
- </tr>
-</table>
-
-<p>
- X axis increases going to the right. Y axis increase going up. Coordinate system is landscape and corresponds to a sheet of paper turned on its side.
-</p>
-
-</div>
-<!-- SECTION "Coordinate Space" [897-1703] -->
-<h2><a name="filenames" id="filenames">Filenames</a></h2>
-<div class="level2">
-
-<p>
-Symbols end in .sym. The only symbol filename convention that is used in gEDA/gaf is that if there are multiple instances of a symbol with the same name (like a 7400), then a -1, -2, -3, … -N suffix is added to the end of the filename. Example: 7400-1.sym, 7400-2.sym, 7400-3.sym…<br/>
- Schematics end in .sch. There used to be a schematic filename convention (adding a -1 .. -N to the end of the basename), but this convention is now obsolete. Schematic filenames can be anything that makes sense to the creator.
-</p>
-
-</div>
-<!-- SECTION "Filenames" [1704-2240] -->
-<h2><a name="object_types" id="object_types">Object types</a></h2>
-<div class="level2">
-
-<p>
-A schematic/symbol file for gEDA/gaf consists of:
-</p>
-<ul>
-<li class="level1"><div class="li"> A version (v) as the first item in the file. This is required.</div>
-</li>
-<li class="level1"><div class="li"> Any number of objects and the correct data. Objects are specified by an â??object typeâ??</div>
-</li>
-<li class="level1"><div class="li"> Most objects are a single line, however text objects are two lines long.</div>
-</li>
-<li class="level1"><div class="li"> No blank lines at the end of the file (these are ignored by the tools)</div>
-</li>
-<li class="level1"><div class="li"> For all enumerated types in the gEDA/gaf file formats, the field takes on the numeric value.</div>
-</li>
-</ul>
-
-<p>
- The â??object typeâ?? id is a single letter and this id must start in the first column. The object type id is case sensitive.<br/>
- The schematic and symbol files share the same file layout. A symbol is nothing more than a collection of primitive objects (lines, boxes, circles, arcs, text, and pins). A schematic is a collection of symbols (components), nets, and buses.<br/>
- The following sections describe the specifics of each recognized object type. Each section has the name of the object, which file type (sch/sym) the object can appear in, the format of the data, a description of each individual field, details and caveats of the fields, and finally an example with description.<br/>
- For information on the color index (which is used in practically all objects), see the Color section.
-</p>
-
-</div>
-<!-- SECTION "Object types" [2241-3511] -->
-<h3><a name="version" id="version">version</a></h3>
-<div class="level3">
-
-<p>
-Valid in: Schematic and Symbol files<br/>
- <strong><code>type version fileformat_version</code></strong>
-</p>
-<table class="inline">
- <tr>
- <th>Field</th><th>Type/unit</th><th>Description</th>
- </tr>
- <tr>
- <td>type</td><td>char</td><td>v</td>
- </tr>
- <tr>
- <td>version</td><td>int</td><td>version of gEDA/gaf that wrote this file</td>
- </tr>
- <tr>
- <td>fileformat_version</td><td>int</td><td>gEDA/gaf file format version number</td>
- </tr>
-</table>
-<ul>
-<li class="level1"><div class="li"> The type is a lower case â??vâ?? (as in Victor).</div>
-</li>
-<li class="level1"><div class="li"> This object must be in every file used or created by the gEDA/gaf tools.</div>
-</li>
-<li class="level1"><div class="li"> The format of the first version field is YYYYMMDD.</div>
-</li>
-<li class="level1"><div class="li"> The version number is not an arbitrary timestamp. Do not make up a version number and expect the tools to behave properly.</div>
-</li>
-<li class="level1"><div class="li"> The â??version of gEDA/gaf that wrote this fileâ?? was used in all versions of gEDA/gaf up to 20030921 as the file formats version. This field should no longer be used to determine the file format. It is used for information purposes only now.</div>
-</li>
-<li class="level1"><div class="li"> Starting at and after gEDA/gaf version 20031004, the fileformat version field is used to determine the file format version. All file format code should key off of this field.</div>
-</li>
-<li class="level1"><div class="li"> fileformat version increases when the file format changes.</div>
-</li>
-<li class="level1"><div class="li"> The starting point for fileformat version is 1.</div>
-</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"> 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, 20070818, 20071229, 20080110</div>
-</li>
-<li class="level1"><div class="li"> Stable versions include: 20070526, 20070626, 20070902, 20071231, 20080127</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>
-<li class="level1"><div class="li"> Keep in mind that each of the above listed versions might have had file format variations. This document only covers the last versionâ??s file format.</div>
-</li>
-</ul>
-
-<p>
- Example:<br/>
-
-</p>
-<pre class="code">v 20040111 1</pre>
-
-</div>
-<!-- SECTION "version" [3512-5439] -->
-<h3><a name="line" id="line">line</a></h3>
-<div class="level3">
-
-<p>
-Valid in: Schematic and Symbol files<br/>
- <strong><code>type x1 y1 x2 y2 color width capstyle dashstyle dashlength dashspace</code></strong>
-</p>
-<table class="inline">
- <tr>
- <th>Field</th><th>Type/unit</th><th>Description</th>
- </tr>
- <tr>
- <td>type</td><td>char</td><td>L</td>
- </tr>
- <tr>
- <td>x1</td><td>int/mils</td><td>First X coordinate</td>
- </tr>
- <tr>
- <td>y1</td><td>int/mils</td><td>First Y coordinate</td>
- </tr>
- <tr>
- <td>x2</td><td>int/mils</td><td>Second X coordinate</td>
- </tr>
- <tr>
- <td>y2</td><td>int/mils</td><td>Second Y coordinate</td>
- </tr>
- <tr>
- <td>color</td><td>int</td><td>Color index</td>
- </tr>
- <tr>
- <td>width</td><td>int/mils</td><td>Width of line</td>
- </tr>
- <tr>
- <td>capstyle</td><td>int</td><td>Line cap style</td>
- </tr>
- <tr>
- <td>dashstyle</td><td>int</td><td>Type of dash style</td>
- </tr>
- <tr>
- <td>dashlength</td><td>int</td><td>Length of dash</td>
- </tr>
- <tr>
- <td>dashspace</td><td>int</td><td>Space inbetween dashes</td>
- </tr>
-</table>
-<ul>
-<li class="level1"><div class="li"> The capstyle is an enumerated type:</div>
-<ul>
-<li class="level2"><div class="li"> END NONE = 0</div>
-</li>
-<li class="level2"><div class="li"> END SQUARE = 1</div>
-</li>
-<li class="level2"><div class="li"> END ROUND = 2</div>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"> The dashstyle is an enumerated type:</div>
-<ul>
-<li class="level2"><div class="li"> TYPE SOLID = 0</div>
-</li>
-<li class="level2"><div class="li"> TYPE DOTTED = 1</div>
-</li>
-<li class="level2"><div class="li"> TYPE DASHED = 2</div>
-</li>
-<li class="level2"><div class="li"> TYPE CENTER = 3</div>
-</li>
-<li class="level2"><div class="li"> TYPE PHANTOM = 4</div>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"> The dashlength parameter is not used for TYPE SOLID and TYPE DOTTED. This parameter should take on a value of -1 in these cases.</div>
-</li>
-<li class="level1"><div class="li"> The dashspace paramater is not used for TYPE SOLID. This parameter should take on a value of -1 in these case.</div>
-</li>
-</ul>
-
-<p>
- Example:<br/>
-
-</p>
-<pre class="code">L 23000 69000 28000 69000 3 40 0 1 -1 75</pre>
-
-<p>
-A line segment from (23000, 69000) to (28000, 69000) with color index 3, 40 mils thick, no cap, dotted line style, and with a spacing of 75 mils in between each dot.
-</p>
-
-</div>
-<!-- SECTION "line" [5440-6674] -->
-<h3><a name="picture" id="picture">picture</a></h3>
-<div class="level3">
-
-<p>
-Valid in: Schematic and Symbol files<br/>
- <strong><code>type x1 y1 width height angle ratio mirrored embedded<br/>
-
-filename<br/>
-
-[encoded picture data<br/>
-
-encoded picture end]</code></strong>
-</p>
-<table class="inline">
- <tr>
- <th>Field</th><th>Type/unit</th><th>Description</th>
- </tr>
- <tr>
- <td>type</td><td>char</td><td>G</td>
- </tr>
- <tr>
- <td>x</td><td>int/mils</td><td>Lower left X coordinate</td>
- </tr>
- <tr>
- <td>y</td><td>int/mils</td><td>Lower left Y coordinate</td>
- </tr>
- <tr>
- <td>width</td><td>int/mils</td><td>Width of the picture</td>
- </tr>
- <tr>
- <td>height</td><td>int/mils</td><td>Height of the picture</td>
- </tr>
- <tr>
- <td>angle</td><td>int/degrees</td><td>Angle of the picture</td>
- </tr>
- <tr>
- <td>mirrored</td><td>char</td><td>Mirrored or normal picture</td>
- </tr>
- <tr>
- <td>embedded</td><td>char</td><td>Embedded or link to the picture file</td>
- </tr>
- <tr>
- <td>filename</td><td>string</td><td>path and filename of a not embedded picture</td>
- </tr>
- <tr>
- <td>encoded picture data</td><td>string</td><td>Serialized picture encoded using base64</td>
- </tr>
- <tr>
- <td>encoded picture end</td><td>string</td><td>A line containing only a dot character</td>
- </tr>
-</table>
-<ul>
-<li class="level1"><div class="li"> This object is a picture object. The first line contains all the picture parameters, and the second line is the path and filename of the picture. The filename is not used if the picture is embedded.</div>
-</li>
-<li class="level1"><div class="li"> The angle of the picture can only take on one of the following values: 0, 90, 180, 270.</div>
-</li>
-<li class="level1"><div class="li"> The mirrored field is an enumerated type:</div>
-<ul>
-<li class="level2"><div class="li"> NOT MIRRORED = 0</div>
-</li>
-<li class="level2"><div class="li"> MIRRORED = 1</div>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"> The embedded field is an enumerated type:</div>
-<ul>
-<li class="level2"><div class="li"> NOT EMBEDDED = 0</div>
-</li>
-<li class="level2"><div class="li"> EMBEDDED = 1 (not yet supported)</div>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"> The encoded picture and encoded picture end fields are only in the file if the picture is embedded in the schematic:</div>
-<ul>
-<li class="level2"><div class="li"> encoded picture data: This is a multiple line field. The picture is serialized and then encoded using base64. This way the encoded data uses only printable characters. This field is the result of these two operations.</div>
-</li>
-<li class="level2"><div class="li"> encoded picture end : A line containing only a single dot '.' character marks the end of the encoded picture data.</div>
-</li>
-</ul>
-</li>
-</ul>
-
-<p>
- Example:<br/>
-
-</p>
-<pre class="code">G 16900 35800 1400 2175 0 6.435331e-01 0 0
-../bitmaps/logo.jpg</pre>
-
-<p>
-A picture object with the lower left corner at (16900, 35800). The width of the image is 1400 mils, and its height is 2175 mils (i.e.: the ratio is 0.6353). The picture rotation is 0 degrees and the picture is not mirrored, neither embedded.<br/>
- The picture path and filename is showed in the second line.<br/>
- Example:<br/>
-
-</p>
-<pre class="code">G 16900 35800 1400 2175 0 6.435331e-01 0 1
-../bitmaps/logo.jpg
-AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
-BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB
-.</pre>
-
-<p>
-A picture object with the lower left corner at (16900, 35800). The width of the image is 1400 mils, and its height is 2175 mils (i.e.: the ratio is 0.6353).<br/>
- The picture rotation is 0 degrees, it is not mirrored, and it is embedded.<br/>
- The picture path and filename is showed in the second line. Since this is an embedded picture, the filename and path are not used.<br/>
- The encoded picture data is only an example (it is not real data). The last line containing a single dot '.' character marks the end of the encoded picture data.
-</p>
-
-</div>
-<!-- SECTION "picture" [6675-9468] -->
-<h3><a name="box" id="box">box</a></h3>
-<div class="level3">
-
-<p>
-Valid in: Schematic and Symbol files<br/>
- <strong><code>type x y width height color width capstyle dashtype dashlength dashspace
-filltype fillwidth angle1 pitch1 angle2 pitch2</code></strong>
-</p>
-<table class="inline">
- <tr>
- <th>Field</th><th>Type/unit</th><th>Description</th>
- </tr>
- <tr>
- <td>type</td><td>char</td><td>B</td>
- </tr>
- <tr>
- <td>x</td><td>int/mils</td><td>Lower left hand X coordinate</td>
- </tr>
- <tr>
- <td>y</td><td>int/mils</td><td>Lower left hand Y coordinate</td>
- </tr>
- <tr>
- <td>width</td><td>int/mils</td><td>Width of the box (x direction)</td>
- </tr>
- <tr>
- <td>height</td><td>int/mils</td><td>Height of the box (y direction)</td>
- </tr>
- <tr>
- <td>color</td><td>int</td><td>Color index</td>
- </tr>
- <tr>
- <td>width</td><td>int/mils</td><td>Width of lines</td>
- </tr>
- <tr>
- <td>capstyle</td><td>int/mils</td><td>Line cap style</td>
- </tr>
- <tr>
- <td>dashstyle</td><td>int</td><td>Type of dash style</td>
- </tr>
- <tr>
- <td>dashlength</td><td>int/mils</td><td>Length of dash</td>
- </tr>
- <tr>
- <td>dashspace</td><td>int/mils</td><td>Space inbetween dashes</td>
- </tr>
- <tr>
- <td>filltype</td><td>int</td><td>Type of fill</td>
- </tr>
- <tr>
- <td>fillwidth</td><td>int/mils</td><td>Width of the fill lines</td>
- </tr>
- <tr>
- <td>angle1</td><td>int/degrees</td><td>First angle of fill</td>
- </tr>
- <tr>
- <td>pitch1</td><td>int/mils</td><td>First pitch/spacing of fill</td>
- </tr>
- <tr>
- <td>angle2</td><td>int/degrees</td><td>Second angle of fill</td>
- </tr>
- <tr>
- <td>pitch2</td><td>int/mils</td><td>Second pitch/spacing of fill</td>
- </tr>
-</table>
-<ul>
-<li class="level1"><div class="li"> The capstyle is an enumerated type:</div>
-<ul>
-<li class="level2"><div class="li"> END NONE = 0</div>
-</li>
-<li class="level2"><div class="li"> END SQUARE = 1</div>
-</li>
-<li class="level2"><div class="li"> END ROUND = 2</div>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"> The dashstyle is an enumerated type:</div>
-<ul>
-<li class="level2"><div class="li"> TYPE SOLID = 0</div>
-</li>
-<li class="level2"><div class="li"> TYPE DOTTED = 1</div>
-</li>
-<li class="level2"><div class="li"> TYPE DASHED = 2</div>
-</li>
-<li class="level2"><div class="li"> TYPE CENTER = 3</div>
-</li>
-<li class="level2"><div class="li"> TYPE PHANTOM = 4</div>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"> The dashlength parameter is not used for TYPE SOLID and TYPE DOTTED. This parameter should take on a value of -1 in these cases.</div>
-</li>
-<li class="level1"><div class="li"> The dashspace paramater is not used for TYPE SOLID. This parameter should take on a value of -1 in these case.</div>
-</li>
-<li class="level1"><div class="li"> The filltype parameter is an enumerated type:</div>
-<ul>
-<li class="level2"><div class="li"> FILLING HOLLOW = 0</div>
-</li>
-<li class="level2"><div class="li"> FILLING FILL = 1</div>
-</li>
-<li class="level2"><div class="li"> FILLING MESH = 2</div>
-</li>
-<li class="level2"><div class="li"> FILLING HATCH = 3</div>
-</li>
-<li class="level2"><div class="li"> FILLING VOID = 4 unused</div>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"> If the filltype is 0 (FILLING HOLLOW), then all the fill parameters should take on a value of -1.</div>
-</li>
-<li class="level1"><div class="li"> The fill type FILLING FILL is a solid color fill.</div>
-</li>
-<li class="level1"><div class="li"> The two pairs of pitch and spacing control the fill or hatch if the fill type is FILLING MESH.</div>
-</li>
-<li class="level1"><div class="li"> Only the first pair of pitch and spacing are used if the fill type is FILLING HATCH.</div>
-</li>
-</ul>
-
-<p>
- Example:<br/>
-
-</p>
-<pre class="code">B 33000 67300 2000 2000 3 60 0 2 75 50 0 -1 -1 -1 -1 -1</pre>
-
-<p>
-A box with the lower left hand corner at (33000, 67300) and a width and height of (2000, 2000), color index 3, line width of 60 mils, no cap, dashed line type, dash length of 75 mils, dash spacing of 50 mils, no fill, rest parameters unset.
-</p>
-
-</div>
-<!-- SECTION "box" [9469-11675] -->
-<h3><a name="circle" id="circle">circle</a></h3>
-<div class="level3">
-
-<p>
-Valid in: Schematic and Symbol files<br/>
- <strong><code>type x y radius color width capstyle dashtype dashlength dashspace
-filltype fillwidth angle1 pitch1 angle2 pitch2</code></strong>
-</p>
-<table class="inline">
- <tr>
- <th>Field</th><th>Type/unit</th><th>Description</th>
- </tr>
- <tr>
- <td>type</td><td>char</td><td>V</td>
- </tr>
- <tr>
- <td>x</td><td>int/mils</td><td>Center X coordinate</td>
- </tr>
- <tr>
- <td>y</td><td>int/mils</td><td>Center Y coordinate</td>
- </tr>
- <tr>
- <td>radius</td><td>int/mils</td><td>Radius of the circle</td>
- </tr>
- <tr>
- <td>color</td><td>int</td><td>Color index</td>
- </tr>
- <tr>
- <td>width</td><td>int/mils</td><td>Width of circle line</td>
- </tr>
- <tr>
- <td>capstyle</td><td>int/mils</td><td>0 unused</td>
- </tr>
- <tr>
- <td>dashstyle</td><td>int</td><td>Type of dash style</td>
- </tr>
- <tr>
- <td>dashlength</td><td>int/mils</td><td>Length of dash</td>
- </tr>
- <tr>
- <td>dashspace</td><td>int/mils</td><td>Space inbetween dashes</td>
- </tr>
- <tr>
- <td>filltype</td><td>int</td><td>Type of fill</td>
- </tr>
- <tr>
- <td>fillwidth</td><td>int/mils</td><td>Width of the fill lines</td>
- </tr>
- <tr>
- <td>angle1</td><td>int/degrees</td><td>First angle of fill</td>
- </tr>
- <tr>
- <td>pitch1</td><td>int/mils</td><td>First pitch/spacing of fill</td>
- </tr>
- <tr>
- <td>angle2</td><td>int/degrees</td><td>Second angle of fill</td>
- </tr>
- <tr>
- <td>pitch2</td><td>int/mils</td><td>Second pitch/spacing of fill</td>
- </tr>
-</table>
-<ul>
-<li class="level1"><div class="li"> The dashstyle is an enumerated type:</div>
-<ul>
-<li class="level2"><div class="li"> TYPE SOLID = 0</div>
-</li>
-<li class="level2"><div class="li"> TYPE DOTTED = 1</div>
-</li>
-<li class="level2"><div class="li"> TYPE DASHED = 2</div>
-</li>
-<li class="level2"><div class="li"> TYPE CENTER = 3</div>
-</li>
-<li class="level2"><div class="li"> TYPE PHANTOM = 4</div>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"> The dashlength parameter is not used for TYPE SOLID and TYPE DOTTED. This parameter should take on a value of -1 in these cases.</div>
-</li>
-<li class="level1"><div class="li"> The dashspace paramater is not used for TYPE SOLID. This parameter should take on a value of -1 in these case.</div>
-</li>
-<li class="level1"><div class="li"> The filltype parameter is an enumerated type:</div>
-<ul>
-<li class="level2"><div class="li"> FILLING HOLLOW = 0</div>
-</li>
-<li class="level2"><div class="li"> FILLING FILL = 1</div>
-</li>
-<li class="level2"><div class="li"> FILLING MESH = 2</div>
-</li>
-<li class="level2"><div class="li"> FILLING HATCH = 3</div>
-</li>
-<li class="level2"><div class="li"> FILLING VOID = 4 unused</div>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"> If the filltype is 0 (FILLING HOLLOW), then all the fill parameters should take on a value of -1.</div>
-</li>
-<li class="level1"><div class="li"> The fill type FILLING FILL is a solid color fill.</div>
-</li>
-<li class="level1"><div class="li"> The two pairs of pitch and spacing control the fill or hatch if the fill type is FILLING MESH.</div>
-</li>
-<li class="level1"><div class="li"> Only the first pair of pitch and spacing are used if the fill type is FILLING HATCH.</div>
-</li>
-</ul>
-
-<p>
- Example:<br/>
-
-</p>
-<pre class="code">V 38000 67000 900 3 0 0 2 75 50 2 10 20 30 90 50</pre>
-
-<p>
-A circle with the center at (38000, 67000) and a radius of 900 mils, color index 3, line width of 0 mils (smallest size), no cap, dashed line type, dash length of 75 mils, dash spacing of 50 mils, mesh fill, 10 mils thick mesh lines, first mesh line: 20 degrees, with a spacing of 30 mils, second mesh line: 90 degrees, with a spacing of 50 mils.
-</p>
-
-</div>
-<!-- SECTION "circle" [11676-13801] -->
-<h3><a name="arc" id="arc">arc</a></h3>
-<div class="level3">
-
-<p>
-Valid in: Schematic and Symbol files<br/>
- <strong><code>type x y radius startangle sweepangle color width capstyle dashtype
-dashlength dashspace</code></strong>
-</p>
-<table class="inline">
- <tr>
- <th>Field</th><th>Type/unit</th><th>Description</th>
- </tr>
- <tr>
- <td>type</td><td>char</td><td>A</td>
- </tr>
- <tr>
- <td>x</td><td>int/mils</td><td>Center X coordinate</td>
- </tr>
- <tr>
- <td>y</td><td>int/mils</td><td>Center Y coordinate</td>
- </tr>
- <tr>
- <td>radius</td><td>int/mils</td><td>Radius of the arc</td>
- </tr>
- <tr>
- <td>startangle</td><td>int/degrees</td><td>Starting angle of the arc</td>
- </tr>
- <tr>
- <td>sweepangle</td><td>int/degrees</td><td>Amount the arc sweeps</td>
- </tr>
- <tr>
- <td>color</td><td>int</td><td>Color index</td>
- </tr>
- <tr>
- <td>width</td><td>int/mils</td><td>Width of circle line</td>
- </tr>
- <tr>
- <td>capstyle</td><td>int</td><td>Cap style</td>
- </tr>
- <tr>
- <td>dashstyle</td><td>int</td><td>Type of dash style</td>
- </tr>
- <tr>
- <td>dashlength</td><td>int/mils</td><td>Length of dash</td>
- </tr>
- <tr>
- <td>dashspace</td><td>int/mils</td><td>Space inbetween dashes</td>
- </tr>
-</table>
-<ul>
-<li class="level1"><div class="li"> The startangle can be negative, but not recommended.</div>
-</li>
-<li class="level1"><div class="li"> The sweepangle can be negative, but not recommended.</div>
-</li>
-<li class="level1"><div class="li"> The capstyle is an enumerated type:</div>
-<ul>
-<li class="level2"><div class="li"> END NONE = 0</div>
-</li>
-<li class="level2"><div class="li"> END SQUARE = 1</div>
-</li>
-<li class="level2"><div class="li"> END ROUND = 2</div>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"> The dashstyle is an enumerated type:</div>
-<ul>
-<li class="level2"><div class="li"> TYPE SOLID = 0</div>
-</li>
-<li class="level2"><div class="li"> TYPE DOTTED = 1</div>
-</li>
-<li class="level2"><div class="li"> TYPE DASHED = 2</div>
-</li>
-<li class="level2"><div class="li"> TYPE CENTER = 3</div>
-</li>
-<li class="level2"><div class="li"> TYPE PHANTOM = 4</div>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"> The dashlength parameter is not used for TYPE SOLID and TYPE DOTTED. This parameter should take on a value of -1 in these cases.</div>
-</li>
-<li class="level1"><div class="li"> The dashspace paramater is not used for TYPE SOLID. This parameter should take on a value of -1 in these case.</div>
-</li>
-</ul>
-
-<p>
- Example:<br/>
-
-</p>
-<pre class="code">A 30600 75000 2000 0 45 3 0 0 3 75 50</pre>
-
-<p>
- An arc with the center at (30600, 75000) and a radius of 2000 mils, a starting angle of 0, sweeping 45 degrees, color index 3, line width of 0 mils (smallest size), no cap, center line type, dash length of 75 mils, dash spacing of 50 mils.
-</p>
-
-</div>
-<!-- SECTION "arc" [13802-15317] -->
-<h3><a name="text" id="text">text</a></h3>
-<div class="level3">
-
-<p>
-Valid in: Schematic and Symbol files<br/>
- <strong><code>type x y color size visibility show_name_value angle alignment num_lines<br/>
-
-string line 1<br/>
-
-string line 2<br/>
-
-string line 3<br/>
-
-…<br/>
-
-string line N</code></strong>
-</p>
-<table class="inline">
- <tr>
- <th>Field</th><th>Type/unit</th><th>Description</th>
- </tr>
- <tr>
- <td>type</td><td>char</td><td>T</td>
- </tr>
- <tr>
- <td>x</td><td>int/mils</td><td>First X coordinate</td>
- </tr>
- <tr>
- <td>y</td><td>int/mils</td><td>First Y coordinate</td>
- </tr>
- <tr>
- <td>color</td><td>int</td><td>Color index</td>
- </tr>
- <tr>
- <td>size</td><td>int/points</td><td>Size of text</td>
- </tr>
- <tr>
- <td>visibility</td><td>int</td><td>Visibility of text</td>
- </tr>
- <tr>
- <td>show_name_value</td><td>int</td><td>Attribute visibility control</td>
- </tr>
- <tr>
- <td>angle</td><td>int/degrees</td><td>Angle of the text</td>
- </tr>
- <tr>
- <td>alignment</td><td>int</td><td>Alignment/origin of the text</td>
- </tr>
- <tr>
- <td>num_lines</td><td>int</td><td>Number of lines of text (1 based)</td>
- </tr>
- <tr>
- <td>string line 1 … N</td><td>string</td><td>The text strings, on a seperate line</td>
- </tr>
-</table>
-<ul>
-<li class="level1"><div class="li"> This object is a multi line object. The first line contains all the text parameters and the subsequent lines are the text strings.</div>
-</li>
-<li class="level1"><div class="li"> There must be exactly num lines of text following the T … string.</div>
-</li>
-<li class="level1"><div class="li"> The maximum length of any single text string is 1024, however there is no limit to the number of text string lines.</div>
-</li>
-<li class="level1"><div class="li"> The minimum size is 2 points (1/72 of an inch).</div>
-</li>
-<li class="level1"><div class="li"> There is no maximum size.</div>
-</li>
-<li class="level1"><div class="li"> The coordinate pair is the origin of the text item.</div>
-</li>
-<li class="level1"><div class="li"> The visibility field is an enumerated type:</div>
-<ul>
-<li class="level2"><div class="li"> INVISIBLE = 0</div>
-</li>
-<li class="level2"><div class="li"> VISIBLE = 1</div>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"> The show_name_value is an enumerated type:</div>
-<ul>
-<li class="level2"><div class="li"> SHOW NAME VALUE = 0 (show both name and value of an attribute)</div>
-</li>
-<li class="level2"><div class="li"> SHOW VALUE = 1 (show only the value of an attribute)</div>
-</li>
-<li class="level2"><div class="li"> SHOW NAME = 2 (show only the name of an attribute)</div>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"> The show_name_value field is only valid if the string is an attribute (string has to be in the form: name=value to be considered an attribute).</div>
-</li>
-<li class="level1"><div class="li"> The angle of the text can only take on one of the following values: 0, 90, 180, 270. A value of 270 will always generate upright text.</div>
-</li>
-<li class="level1"><div class="li"> The alignment/origin field controls the relative location of the origin.</div>
-</li>
-<li class="level1"><div class="li"> The alignment field can take a value from 0 to 8.</div>
-</li>
-<li class="level1"><div class="li"> The num_lines field always starts at 1.</div>
-</li>
-<li class="level1"><div class="li"> The num_lines field was added starting with file format version 1. Past versions (0 or earlier) only supported single line text objects.<br/>
- The following diagram shows what the values for the alignment field mean:</div>
-</li>
-</ul>
-<table class="inline">
- <tr>
- <td> <a href="_detail/geda_fileformat_textgraphic.html" class="media" title="geda:fileformat_textgraphic.jpg"><img src="_media/geda_fileformat_textgraphic.jpg" class="media" title="fileformat_textgraphic.jpg" alt="fileformat_textgraphic.jpg" /></a> </td>
- </tr>
-</table>
-
-<p>
- Example:<br/>
-
-</p>
-<pre class="code">T 16900 35800 3 10 1 0 0 0 1
-Text string!</pre>
-
-<p>
-A text object with the origin at (16900, 35800), color index 3, 10 points in size, visible, attribute ags not valid (not an attribute), origin at lower left, string: Text string!
-</p>
-
-<p>
-Example:<br/>
-
-</p>
-<pre class="code">T 16900 35800 3 10 1 0 0 0 5
-Text string line 1
-Text string line 2
-Text string line 3
-Text string line 4
-Text string line 5</pre>
-
-<p>
-This is a similar text object as the above example, however here there are five lines of text.
-</p>
-
-</div>
-<!-- SECTION "text" [15318-17971] -->
-<h3><a name="net" id="net">net</a></h3>
-<div class="level3">
-
-<p>
-Valid in: Schematic files ONLY<br/>
- <strong><code>type x1 y1 x2 y2 color</code></strong>
-</p>
-<table class="inline">
- <tr>
- <th>Field</th><th>Type/unit</th><th>Description</th>
- </tr>
- <tr>
- <td>type</td><td>char</td><td>N</td>
- </tr>
- <tr>
- <td>x1</td><td>int/mils</td><td>First X coordinate</td>
- </tr>
- <tr>
- <td>y1</td><td>int/mils</td><td>First Y coordinate</td>
- </tr>
- <tr>
- <td>x2</td><td>int/mils</td><td>Second X coordinate</td>
- </tr>
- <tr>
- <td>y2</td><td>int/mils</td><td>Second Y coordinate</td>
- </tr>
- <tr>
- <td>color</td><td>int</td><td>Color index</td>
- </tr>
-</table>
-<ul>
-<li class="level1"><div class="li"> Nets can only appear in schematic files.</div>
-</li>
-<li class="level1"><div class="li"> You cannot have a zero length net (the tools will throw them away).</div>
-</li>
-</ul>
-
-<p>
- Example:<br/>
-
-</p>
-<pre class="code">N 12700 29400 32900 29400 4</pre>
-
-<p>
-A net segment from (12700, 29400) to (32900, 29400) with color index 4.
-</p>
-
-</div>
-<!-- SECTION "net" [17972-18497] -->
-<h3><a name="bus" id="bus">bus</a></h3>
-<div class="level3">
-
-<p>
-Valid in: Schematic files ONLY<br/>
- <strong><code>type x1 y1 x2 y2 color ripperdir</code></strong>
-</p>
-<table class="inline">
- <tr>
- <th>Field</th><th>Type/unit</th><th>Description</th>
- </tr>
- <tr>
- <td>type</td><td>char</td><td>U</td>
- </tr>
- <tr>
- <td>x1</td><td>int/mils</td><td>First X coordinate</td>
- </tr>
- <tr>
- <td>y1</td><td>int/mils</td><td>First Y coordinate</td>
- </tr>
- <tr>
- <td>x2</td><td>int/mils</td><td>Second X coordinate</td>
- </tr>
- <tr>
- <td>y2</td><td>int/mils</td><td>Second Y coordinate</td>
- </tr>
- <tr>
- <td>color</td><td>int</td><td>Color index</td>
- </tr>
- <tr>
- <td>ripperdir</td><td>int</td><td>Direction of bus rippers</td>
- </tr>
-</table>
-<ul>
-<li class="level1"><div class="li"> The ripperdir field for an brand new bus is 0.</div>
-</li>
-<li class="level1"><div class="li"> The ripperdir field takes on a value of 1 or -1 when a net is connected to the bus for the first time. This value indicates the direction of the ripper symbol. The ripper direction is set to the same value for the entire life of the bus object.</div>
-</li>
-<li class="level1"><div class="li"> Buses can only appear in schematic files.</div>
-</li>
-<li class="level1"><div class="li"> You cannot have a zero length bus (the tools will throw them away).</div>
-</li>
-</ul>
-
-<p>
- Example:<br/>
-
-</p>
-<pre class="code">U 27300 37400 27300 35300 3 0</pre>
-
-<p>
-A bus segment from (27300, 37400) to (27300, 35300) with color index 3 and no nets have been connected to this bus segment.
-</p>
-
-</div>
-<!-- SECTION "bus" [18498-19429] -->
-<h3><a name="pin" id="pin">pin</a></h3>
-<div class="level3">
-
-<p>
-Valid in: Symbol files ONLY<br/>
- <strong><code>type x1 y1 x2 y2 color pintype whichend</code></strong>
-</p>
-<table class="inline">
- <tr>
- <th>Field</th><th>Type/unit</th><th>Description</th>
- </tr>
- <tr>
- <td>type</td><td>char</td><td>P</td>
- </tr>
- <tr>
- <td>x1</td><td>int/mils</td><td>First X coordinate</td>
- </tr>
- <tr>
- <td>y1</td><td>int/mils</td><td>First Y coordinate</td>
- </tr>
- <tr>
- <td>x2</td><td>int/mils</td><td>Second X coordinate</td>
- </tr>
- <tr>
- <td>y2</td><td>int/mils</td><td>Second Y coordinate</td>
- </tr>
- <tr>
- <td>color</td><td>int</td><td>Color index</td>
- </tr>
- <tr>
- <td>pintype</td><td>int</td><td>Type of pin</td>
- </tr>
- <tr>
- <td>whichend</td><td>int</td><td>Specifies the active end</td>
- </tr>
-</table>
-<ul>
-<li class="level1"><div class="li"> The pintype is an enumerated type:</div>
-<ul>
-<li class="level2"><div class="li"> NORMAL <acronym title="Personal Identification Number">PIN</acronym> = 0</div>
-</li>
-<li class="level2"><div class="li"> BUS <acronym title="Personal Identification Number">PIN</acronym> = 1 unused</div>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"> The whichend specifies which end point of the pin is the active connection port. Only this end point can have other pins or nets connected to it.</div>
-</li>
-<li class="level1"><div class="li"> To make the first end point active, whichend should be 0, else to specify the other end, whichend should be 1.</div>
-</li>
-<li class="level1"><div class="li"> Pins can only appear in symbol files.</div>
-</li>
-<li class="level1"><div class="li"> You cannot have a zero length pen (the tools will throw them away).</div>
-</li>
-</ul>
-
-<p>
- Example:<br/>
-
-</p>
-<pre class="code">P 0 200 200 200 1 0 0</pre>
-
-<p>
-A pin from (0, 200) to (200, 200) with color index 1, a regular pin, and the first point being the active connection end.
-</p>
-
-</div>
-<!-- SECTION "pin" [19430-20426] -->
-<h3><a name="component" id="component">component</a></h3>
-<div class="level3">
-
-<p>
-Valid in: Schematic files ONLY<br/>
- <strong><code>type x y selectable angle mirror basename</code></strong>
-</p>
-<table class="inline">
- <tr>
- <th>Field</th><th>Type/unit</th><th>Description</th>
- </tr>
- <tr>
- <td>type</td><td>char</td><td>C</td>
- </tr>
- <tr>
- <td>x</td><td>int/mils</td><td>Origin X coordinate</td>
- </tr>
- <tr>
- <td>y</td><td>int/mils</td><td>Origin Y coordinate</td>
- </tr>
- <tr>
- <td>selectable</td><td>int</td><td>Selectable flag</td>
- </tr>
- <tr>
- <td>angle</td><td>int/degrees</td><td>Angle of the component</td>
- </tr>
- <tr>
- <td>mirror</td><td>int</td><td>Mirror around Y axis</td>
- </tr>
- <tr>
- <td>basename</td><td>string</td><td>The filename of the component</td>
- </tr>
-</table>
-
-<p>
- The selectable field is either 1 for selectable or 0 if not selectable.
-</p>
-<ul>
-<li class="level1"><div class="li"> The angle field can only take on the following values: 0, 90, 180, 270.</div>
-</li>
-<li class="level1"><div class="li"> The angle field can only be positive.</div>
-</li>
-<li class="level1"><div class="li"> The mirror flag is 0 if the component is not mirrored (around the Y axis).</div>
-</li>
-<li class="level1"><div class="li"> The mirror flag is 1 if the component is mirrored (around the Y axis).</div>
-</li>
-<li class="level1"><div class="li"> The just basename is the filename of the component. This filename is not the full path.</div>
-</li>
-</ul>
-
-<p>
- Example:<br/>
-
-</p>
-<pre class="code">C 18600 19900 1 0 0 7400-1.sym</pre>
-
-<p>
-A component whoâ??s origin is at (18600,19900), is selectable, not rotated, not mirrored, and the basename of the component is 7400-1.sym.
-</p>
-
-</div>
-<!-- SECTION "component" [20427-21430] -->
-<h3><a name="font" id="font">font</a></h3>
-<div class="level3">
-
-<p>
-Valid in: Special font files ONLY<br/>
- <strong><code>type character width flag</code></strong>
-</p>
-<table class="inline">
- <tr>
- <th>Field</th><th>Type/unit</th><th>Description</th>
- </tr>
- <tr>
- <td>type</td><td>char</td><td>F</td>
- </tr>
- <tr>
- <td>character</td><td>char</td><td>The character being defined</td>
- </tr>
- <tr>
- <td>width</td><td>int/mils</td><td>Width of the character (mils)</td>
- </tr>
- <tr>
- <td>flag</td><td>int</td><td>Special space flag</td>
- </tr>
-</table>
-<ul>
-<li class="level1"><div class="li"> This is a special tag and should ONLY show up in font definition files.</div>
-</li>
-<li class="level1"><div class="li"> If the font character being defined is the space character (32) then flag should be 1, otherwise 0.</div>
-</li>
-</ul>
-
-<p>
- Example:<br/>
-
-</p>
-<pre class="code">F 11 1</pre>
-
-<p>
-The above font definition is for the space character.
-</p>
-
-</div>
-<!-- SECTION "font" [21431-21951] -->
-<h2><a name="colors" id="colors">Colors</a></h2>
-<div class="level2">
-
-<p>
-In the gEDA/gaf schematic and symbol file format colors are specified via an integer index. The relationship between integer and color is based on object type. Each object type typically has one or more colors. Here is a table of color index to object type:
-</p>
-<table class="inline">
- <tr>
- <th>Index</th><th>Object type</th>
- </tr>
- <tr>
- <td>0</td><td>BACKGROUND_COLOR</td>
- </tr>
- <tr>
- <td>1</td><td><acronym title="Personal Identification Number">PIN</acronym>_COLOR</td>
- </tr>
- <tr>
- <td>2</td><td>NET_ENDPOINT_COLOR</td>
- </tr>
- <tr>
- <td>3</td><td>GRAPHIC_COLOR</td>
- </tr>
- <tr>
- <td>4</td><td>NET_COLOR</td>
- </tr>
- <tr>
- <td>5</td><td>ATTRIBUTE_COLOR</td>
- </tr>
- <tr>
- <td>6</td><td>LOGIC_BUBBLE_COLOR</td>
- </tr>
- <tr>
- <td>7</td><td>GRID_COLOR</td>
- </tr>
- <tr>
- <td>8</td><td>DETACHED_ATTRIBUTE_COLOR</td>
- </tr>
- <tr>
- <td>9</td><td>TEXT_COLOR</td>
- </tr>
- <tr>
- <td>10</td><td>BUS_COLOR</td>
- </tr>
- <tr>
- <td>11</td><td>SELECT_COLOR</td>
- </tr>
- <tr>
- <td>12</td><td>BOUNDINGBOX_COLOR</td>
- </tr>
- <tr>
- <td>13</td><td>ZOOM_BOX_COLOR</td>
- </tr>
- <tr>
- <td>14</td><td>STROKE_COLOR</td>
- </tr>
- <tr>
- <td>15</td><td>LOCK_COLOR</td>
- </tr>
- <tr>
- <td>16</td><td>OUTPUT_BACKGROUND_COLOR</td>
- </tr>
-</table>
-
-<p>
- The actual color associated with the color index is defined on a per tool bases. Objects are typically assigned their corresponding color index, but it is permissible (sometimes) to assign other color index values to different object types.
-</p>
-
-</div>
-<!-- SECTION "Colors" [21952-22823] -->
-<h2><a name="attributes" id="attributes">Attributes</a></h2>
-<div class="level2">
-
-<p>
-Attributes are enclosed in braces {} and can only be text. Attributes are text items which take on the form name=value. If it doesnâ??t have name=value, itâ??s not an attribute. Attributes are attached to the previous object. Hereâ??s an example:
-</p>
-<pre class="code">P 988 500 1300 500 1
-{
-T 1000 570 5 8 1 1 0
-pinseq=3
-T 1000 550 5 8 1 1 0
-pinnumber=3
-}</pre>
-
-<p>
-The object is a pin which has an attribute pinnumber=3 and pinseq=3 (name=value). You can have multiple text objects (both the T … and text string are required) in between the braces {}. As of 20021103, you can only attached text items as attributes. Attaching other object types as attributes is unsupported.<br/>
- You can also have â??toplevelâ?? attributes. These attributes are not attached to any object, but instead are just text objects that take on the form name=value.<br/>
- These attributes are useful when you need to convey some info about a schematic page or symbol and need the netlister to have access to this info.
-</p>
-
-</div>
-<!-- SECTION "Attributes" [22824-23811] -->
-<h2><a name="embedded_components" id="embedded_components">Embedded Components</a></h2>
-<div class="level2">
-
-<p>
-Embedded components are components which have all of their definition stored within the schematic file. When a users place a component onto a schematic page, they have the option of making the component embedded. Other than storing all the symbol information inside of the schematic, an embedded component is just any other component. Embedded components are defined as:
-</p>
-<pre class="code">C 18600 21500 1 0 0 EMBEDDED555-1.sym
-[
-...
-... Embedded primitive objects
-...
-]</pre>
-
-<p>
-In the example above, <strong>555-1.sym</strong> is the component. The EMBEDDED tag and the [ ] are the distinguishing characteristics of embedded components. <strong>componentname.sym</strong> must exist in one of the specified component-libraries if you want to unembed the component.
-</p>
-
-</div>
-<!-- SECTION "Embedded Components" [23812-24571] -->
-<h2><a name="document_revision_history" id="document_revision_history">Document Revision History</a></h2>
-<div class="level2">
-<table class="inline">
- <tr>
- <td>November 30th, 2002</td><td>Created fleformats.tex from fleformats.html.</td>
- </tr>
- <tr>
- <td>December 1st, 2002</td><td>Continued work on this document.</td>
- </tr>
- <tr>
- <td>October 4th, 2003</td><td>Added new file format version flag info.</td>
- </tr>
- <tr>
- <td>October 19th, 2003</td><td>Added num lines text field.</td>
- </tr>
-</table>
-
-</div>
-<!-- SECTION "Document Revision History" [24572-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/geda_footprint_creation.html b/docs/wiki/geda_footprint_creation.html
deleted file mode 100644
index 8917a94..0000000
--- a/docs/wiki/geda_footprint_creation.html
+++ /dev/null
@@ -1,27 +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>geda:footprint_creation</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="noindex,follow" />
-<meta name="date" content="1969-12-31T19:00:00-0500" />
-<meta name="keywords" content="geda,footprint_creation" />
-<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/geda:footprint_creation?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:footprint_creation"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:footprint_creation"; />
-<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>
-</body>
-</html>
diff --git a/docs/wiki/geda_gattrib_readme.html b/docs/wiki/geda_gattrib_readme.html
deleted file mode 100644
index e81d772..0000000
--- a/docs/wiki/geda_gattrib_readme.html
+++ /dev/null
@@ -1,164 +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>geda:gattrib_readme</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="keywords" content="geda,gattrib_readme" />
-<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/geda:gattrib_readme?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gattrib_readme"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gattrib_readme"; />
-<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">
-
-
-
-<h1><a name="gattrib_readme" id="gattrib_readme">gattrib README</a></h1>
-<div class="level1">
-<pre class="code">******************************************************************
-************* DANGER!! Read the entirety of this **************
-************ README before you try runing gattrib! *************
-******************************************************************
-
-
-INTRODUCTION
-
-Gattrib is gEDA's attribute editor. It reads a set of gschem .sch
-files (schematic files), and creates a spreadsheet showing all
-components in rows, with the associated component attributes listed in
-the columns. It allows the user to add, modify, or delete component
-attributes outside of gschem, and then save the .sch files back
-out. When it is completed, it will allow the user to edit attributes
-attached to components, nets, and pins. (Currently, only component
-attribute editing is implemented; pin attributes are displayed only,
-and net attributes are TBD.)
-
-Gattrib is useful in situations where you need to view, add, modify,
-or delete a number of attributes all at once. It saves you the pain
-of clicking on each component and repeatedly using gschem's attribute
-editor to modify component attributes. For example, if you create a
-large design with generic components, and then later want to attach
-"footprint" attributes to your components, it is a real hassle to do
-so using gschem. In this situation, you can run gattrib on your
-design files to attach the "footprint" attributes all at once using an
-easy-to-use spreadsheet.
-
-WARNING NOTE: Gattrib is currently PRE-ALPHA SOFTWARE!
-It has been tested on several designs, but is not garuanteed to work.
-It may even trash your design! Therefore, if you wish to try gattrib
-out, please create a backup copy of your design before you run it!
-
-------------------------------------------------------------------
-USAGE
-
-You can invoke gattrib on your design from the command line in the
-following way:
-
-gattrib my_design_*.sch
-
-(This assumes you have a multi-page design with file names
-"my_design_1.sch", "my_design_2.sch", etc.) Gattrib will then read in
-your design, and present you with a spreadsheet showing all components
-and associated attributes.
-
-You can also just run gattrib, and specify the input files using the
-file->open dialog box.
-
-To edit your attributes, just edit the cells in the spreadsheet.
-
-To save your design, just select "save" from the command menu. Note
-that no checks are currently done when you select save. Be careful!
-
-To quit, just select "quit" from the command menu. Note that
-currently no checks thet you have saved your design are done when you
-quit.
-
-If you want to add an entirely new attribute to your design (i.e. one
-which doesn't exist on any component), you must first attach at least
-one instance of that attribute to a component using gschem. Then you
-can use gattrib to attach the attribute to the remaining components.
-(The reason for this is that gattrib creates its spreadsheet columns
-based upon all attributes it finds when reading in the design.
-Therefore, to create a column for a new attribute, you need to make
-sure that that new attribute pre-exists in the design.) In the future,
-you will be able to add new attribute columns directly from gattrib,
-but this feature is currently unimplemented.
-
-------------------------------------------------------------------
-FEATURES
-
-The following features are currently implemented:
-
-* .sch file read in from command line.
-* .sch file read in from menu.
-* .sch file save out from menu.
-* Component attribute editing (of course).
-* Pin attribute viewing.
-* Quit from menu.
-
-The following features are currently unimplemented, but will be
-incorporated at some future date:
-
-* Throw up "Are you sure" dialog boxes upon selecting "save" and
- "quit" from menu.
-* Alphabetic sort of rows. (Should happen automatically upon read-in
- of design.)
-* Editing of net attributes (important for setting routing
- attributes).
-* Adding/deleting attribute columns (to add/delete entire sets of
- attributes from a design.)
-* Search/replace of individual attributes.
-* Search for component refdeses & netnames.
-* Set/view component & net visibility (through options pull-down
- menu). Currently, visibility is "invisible", and both name & value
- are displayed (if you turn on the visibility).
-
-Note that if you select unimplemented features from the menu, nothing
-will happen.
-
-------------------------------------------------------------------
-INSTALLATION
-
-To install gattrib, place the tarball in the directory where your gEDA
-sources live. Then do:
-
-tar -zxvf geda-gattrib-20040806.tar.gz
-cd geda-gattrib-20040806
-./configure --prefix=/path/to/your/geda/stuff
-make
-make install
-
-Note that you may need to set some environment variables first. If
-your compilation barfs, try setting these (for csh):
-
-setenv LD_LIBRARY_PATH /usr/local/geda/lib:$LD_LIBRARY_PATH
-setenv PATH /usr/local/geda/bin:$PATH
-setenv PKG_CONFIG_PATH /usr/local/geda/lib/pkgconfig:$PKG_CONFIG_PATH
-
-------------------------------------------------------------------
-CREDITS/CONTACT:
-
-Gattrib was cobbled together by Stuart Brorson starting in December
-2003 from parts culled from GtkSheet (GTK+Extra) and gEDA. Please
-mail bug reports to: sdb@xxxxxxxxxx
-
-
-
-</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_gedasuite_installation.html b/docs/wiki/geda_gedasuite_installation.html
deleted file mode 100644
index 9665e17..0000000
--- a/docs/wiki/geda_gedasuite_installation.html
+++ /dev/null
@@ -1,283 +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>geda:gedasuite_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="keywords" content="geda,gedasuite_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/"; />
-<link rel="contents" href="http://geda.seul.org/wiki/geda:gedasuite_installation?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gedasuite_installation"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gedasuite_installation"; />
-<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="clear">
-
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_install_the_geda_suite" class="toc">How do I install the gEDA Suite?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_uninstall_the_geda_suite" class="toc">How do I uninstall the gEDA Suite?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#why_would_i_want_to_uninstall_the_geda_suite" class="toc">Why would I want to uninstall the gEDA Suite?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#aaaargh_i_put_the_cd_into_my_reader_and_mounted_the_cd_but_nothing_happened" class="toc">Aaaargh! I put the CD into my reader, and mounted the CD, but nothing happened!</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#help_me_i_m_trying_to_install_using_the_cd_rom_but_the_install_wizard_says_i_have_an_error" class="toc">Help me! I'm trying to install using the CD ROM, but the install wizard says I have an error!</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#waaaa_the_installation_ran_to_completion_but_i_get_a_segfault_or_other_problem_when_i_run_gschem_or_gattrib_or_gnetlist_or" class="toc">Waaaa! The installation ran to completion, but I get a segfault (or other problem) when I run gschem (or gattrib, or gnetlist, or. . . )!</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#fedora_core_4_install_notes" class="toc">Fedora Core 4 install notes</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#fedora_core_3_install_notes" class="toc">Fedora Core 3 install notes</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#fedora_core_2_install_notes" class="toc">Fedora Core 2 install notes</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#fedora_core_1_install_notes" class="toc">Fedora Core 1 install notes</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#suse_9.3_install_notes" class="toc">Suse 9.3 install notes</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#suse_10.0_install_notes" class="toc">Suse 10.0 install notes</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#suse_10.1_install_notes" class="toc">Suse 10.1 install notes</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#debian_install_notes" class="toc">Debian install notes</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#ubuntu_install_notes" class="toc">Ubuntu install notes</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#windows_install_notes" class="toc">Windows install notes</a></span></div></li></ul>
-</li></ul>
-</div>
-</div>
-
-
-
-<h2><a name="how_do_i_install_the_geda_suite" id="how_do_i_install_the_geda_suite">How do I install the gEDA Suite?</a></h2>
-<div class="level2">
-
-<p>
-The easiest way to install the gEDA Suite is to grab the gEDA Suite CD ROM and use it. The instructions are contained in the README available on the <a href="http://geda.seul.org/download.html"; class="urlextern" title="http://geda.seul.org/download.html"; rel="nofollow">downloads page</a>. <strong><em>Note that the CD ROM installer assumes that you are running the Gnome desktop! The same is true of the gEDA tools: They use the GTK widget set which underlies Gnome. If you are running KDE, you need to at least get the Gnome libraries installed on your machine before trying to run the installer.</em></strong>
-</p>
-
-<p>
-The gEDA Suite CD holds the tarballs of more than one dozen popular gEDA applications. It also incorporates a <acronym title="Graphical User Interface">GUI</acronym>-based install wizard which checks your system configuration, asks you a few questions, and then oversees the compilation and installation of the different gEDA applications. The install wizard just automates the normal â??./configure && make && make installâ?? process used to build GNU software from source. Therefore, it is more or less platform independent (as long as you are running Linux).
-</p>
-
-<p>
-In the event that the install wizard canâ??t automatically install the gEDA Suite, you can still get the source tarballs off the CD and build them manually. The instructions are available from the download web page, as well as in the INSTALL file on the CD.
-</p>
-
-<p>
-Also, people have created RedHat RPMs, Debian Debs, and Mac OSX Fink packages if you prefer to install that way. These binary distributions are available on the <a href="http://geda.seul.org/download.html"; class="urlextern" title="http://geda.seul.org/download.html"; rel="nofollow">downloads page</a>. Finally, source tarballs for all programs are also available on the <a href="http://geda.seul.org/download.html"; class="urlextern" title="http://geda.seul.org/download.html"; rel="nofollow">downloads page</a>.
-</p>
-
-<p>
-By the way, itâ??s always a good idea to install gEDA into its own directory. That way, when you want to upgrade the package you just need to delete the directory and re-install. (This advice is true for any large suite of applications in unix.) More on this below.
-</p>
-
-<p>
-Finally, if the instructions here arenâ??t enough, David Hart has placed a useful and detailed <a href="http://www.offramp.com/Lab-Install/doku.php?id=fc4#create_user_geda_account_and_install_geda_tool_suite"; class="urlextern" title="http://www.offramp.com/Lab-Install/doku.php?id=fc4#create_user_geda_account_and_install_geda_tool_suite"; rel="nofollow">guide for configuring and installing gEDA</a> (for Fedora Core 4, but probably helpful with other distros too), as well as a <a href="http://www.offramp.com/Lab-Install/doku.php?id=fc4#geda_tutorial"; class="urlextern" title="http://www.offramp.com/Lab-Install/doku.php?id=fc4#geda_tutorial"; rel="nofollow">gEDA Tutorial</a> for new users.
-</p>
-
-</div>
-<!-- SECTION "How do I install the gEDA Suite?" [1-2359] -->
-<h2><a name="how_do_i_uninstall_the_geda_suite" id="how_do_i_uninstall_the_geda_suite">How do I uninstall the gEDA Suite?</a></h2>
-<div class="level2">
-
-<p>
-As of this writing, no advanced method to uninstall the gEDA Suite exists. Unlike a certain commercial operating system, Linux (and unix) were not designed with the goal of easy package management in mind, and we all suffer with this legacy.
-</p>
-
-<p>
-Therefore, we recommend that you install the gEDA Suite into its own special directory. For example, the CD Installer will place the Suiteâ??s executables into <strong><code>${HOME}/geda-install</code></strong> by default. Then, if you need to uninistall the gEDA Suite, you can just delete the entire directory.
-</p>
-
-<p>
-<span class="hilited">(More advanced methods to install/uninstall packages on Linux/unix also exist. Could somebody please write about them here?)</span>
-</p>
-
-</div>
-<!-- SECTION "How do I uninstall the gEDA Suite?" [2360-3071] -->
-<h2><a name="why_would_i_want_to_uninstall_the_geda_suite" id="why_would_i_want_to_uninstall_the_geda_suite">Why would I want to uninstall the gEDA Suite?</a></h2>
-<div class="level2">
-
-<p>
-Different applications belonging to gEDA/gaf all use the same shared library, libgeda.so. Things in the library change from one gEDA release to another. Therefore, applications are prevented from linking to libgeda.so if their release codes donâ??t match.
-</p>
-
-<p>
-If you need to upgrade one application in gEDA/gaf, you will need to first uninstall your old version, and then install an entirely new set of applications, including the library and all components of gEDA/gaf.
-</p>
-
-<p>
-Alternately, you can install the new gEDA/gaf into a new directory, and then edit your <strong><code>${PATH}</code></strong>, <strong><code>${PKG_CONFIG_PATH}</code></strong>, and <strong><code>${LD_LIBRARY_PATH}</code></strong> environment variables to remove the old directory, and point to the new one. Make sure you do this <strong>before</strong> you try installing the new gEDA/gaf.
-</p>
-
-</div>
-<!-- SECTION "Why would I want to uninstall the gEDA Suite?" [3072-3909] -->
-<h2><a name="aaaargh_i_put_the_cd_into_my_reader_and_mounted_the_cd_but_nothing_happened" id="aaaargh_i_put_the_cd_into_my_reader_and_mounted_the_cd_but_nothing_happened">Aaaargh! I put the CD into my reader, and mounted the CD, but nothing happened!</a></h2>
-<div class="level2">
-
-<p>
- Amazingly enough, some people simply copy the installer .iso file using â??cpâ?? onto a blank CD, and then try to use it. This wonâ??t work. You need to â??burnâ?? a CD with the .iso in a way which writes the whole filesystem directly onto the CDROM. The linux/unix command to do this is usually â??cdrecordâ??, or perhaps a <acronym title="Graphical User Interface">GUI</acronym> derivative of this utility. Donâ??t just â??cpâ?? the .iso file onto a blank CD!
-</p>
-
-<p>
-Many modern Linux distributions will not automatically run executables on installed media. This is a security precaution. To overcome this, you need to mount the CD in a way which grants permission for executables to run. For example, in Gentoo and Debian you should mount the CD ROM this way:
-</p>
-<pre class="code">mount -o exec -t iso9660 /dev/cdrom /mnt/cdrom</pre>
-
-<p>
-The detailed flag or mount point relevant to your distribution might be a little different; read the manual for mount (â??man mountâ??) if you have any questions about how to do this.
-</p>
-
-<p>
-After you have mounted the CD with execute permission, you can then run the installer from the command line like this:
-</p>
-<pre class="code">/mnt/cdrom/installer</pre>
-
-<p>
-At this point, the install wizardâ??s <acronym title="Graphical User Interface">GUI</acronym> should pop up, and you can get to installing. If you canâ??t install, please try doing an â??lsâ?? of the CD to see if it is readable. That is, do this:
-</p>
-<pre class="code">ls -l /mnt/cdrom/</pre>
-
-<p>
-And verify that you get a directory listing instead of an error message (or nothing at all).
-</p>
-
-</div>
-<!-- SECTION "Aaaargh! I put the CD into my reader, and mounted the CD, but nothing happened!" [3910-5428] -->
-<h2><a name="help_me_i_m_trying_to_install_using_the_cd_rom_but_the_install_wizard_says_i_have_an_error" id="help_me_i_m_trying_to_install_using_the_cd_rom_but_the_install_wizard_says_i_have_an_error">Help me! I'm trying to install using the CD ROM, but the install wizard says I have an error!</a></h2>
-<div class="level2">
-
-<p>
- First off, please keep in mind that the CD ROMâ??s installer only works on Linux. The CD ROM installer will not work on Sun, BSD, or Mac OSX, and it certainly wonâ??t work on Windows.
-</p>
-
-<p>
-As a general rule, if you are having problems installing gEDA from the CD, here are the things you can try:
-</p>
-<ol>
-<li class="level1"><div class="li"> If you run the installer with the <strong><code>â??log</code></strong> flag set, it will place a file called Install.log into your local directory (where you are running the installer). This file is a log of all commands issued and all responses generated during the install process. It allows you to save the data displayed on the log window displayed during the install process. Running the installer with <strong><code>â??log</code></strong> set is a good idea if you are experiencing problems; you can send your Install.log file to an expert who might be able to diagnose your problem. More on this later.</div>
-</li>
-<li class="level1"><div class="li"> After experiencing a problem, the first thing you should do is look through the gEDA Wiki. Itâ??s quite likely that somebody has already experienced your problem, reported it, and a work around has been found and posted. Different Linux distributions have displayed different problems in the past. Depending upon your distribution, consult the help sections below.</div>
-</li>
-<li class="level1"><div class="li"> If no mention of your specific problem has been posted on the Wiki, try a Google search. GEDA tips and tricks show up in many different places on the web, and Google can find them for you. Also, the geda-user list is continually indexed by Google. Since people frequently post bugs and bug workarounds there, Google will help you find these reports.</div>
-</li>
-<li class="level1"><div class="li"> Next, try posting a question on the geda-user e-mail list. Note that you must first subscribe to the geda-user e-mail list before posting any e-mail to the list. Others may have already developed a work-around for your problem. Some of the experts hang out on that list, and might offer a few helpful suggestions.</div>
-</li>
-</ol>
-
-</div>
-<!-- SECTION "Help me! I'm trying to install using the CD ROM, but the install wizard says I have an error!" [5429-7440] -->
-<h2><a name="waaaa_the_installation_ran_to_completion_but_i_get_a_segfault_or_other_problem_when_i_run_gschem_or_gattrib_or_gnetlist_or" id="waaaa_the_installation_ran_to_completion_but_i_get_a_segfault_or_other_problem_when_i_run_gschem_or_gattrib_or_gnetlist_or">Waaaa! The installation ran to completion, but I get a segfault (or other problem) when I run gschem (or gattrib, or gnetlist, or. . . )!</a></h2>
-<div class="level2">
-
-<p>
-After you install the gEDA Suite off the CD ROM, make sure you do the following:
-</p>
-<ol>
-<li class="level1"><div class="li"> Set your <strong><code>${PATH}</code></strong> to point to the location where your new gEDA executables live (for example, <strong><code>/home/your-name/geda-install/bin</code></strong>). Make sure that you remove pointers to old gEDA editions, if they exist. You should not only set the <strong><code>${PATH}</code></strong> in your current shell, but you should also set it in your shell config scripts (i.e. .bashrc or .cshrc)</div>
-</li>
-<li class="level1"><div class="li"> Type â??rehashâ?? to update your executable search path.</div>
-</li>
-<li class="level1"><div class="li"> Set your <strong><code>${LD_LIBRARY_PATH}</code></strong> to point to the location where your new gEDA executables live (for example, <strong><code>/home/your-name/geda-install/lib</code></strong>). Make sure to remove pointers to old gEDA editions, if they exist. You should not only set the <strong><code>${LD_LIBRARY_PATH}</code></strong> in your current shell, but you should also set it in your shell config scripts (i.e. .bashrc or .cshrc)</div>
-</li>
-<li class="level1"><div class="li"> Run â??su -c ldconfigâ?? to tell the kernel where to find your new libgeda.so.</div>
-</li>
-</ol>
-
-</div>
-<!-- SECTION "Waaaa! The installation ran to completion, but I get a segfault (or other problem) when I run gschem (or gattrib, or gnetlist, or. . . )!" [7441-8568] -->
-<h2><a name="fedora_core_4_install_notes" id="fedora_core_4_install_notes">Fedora Core 4 install notes</a></h2>
-<div class="level2">
-
-<p>
-<a href="geda_fc4.html" class="wikilink1" title="geda:fc4">FC4 notes available here</a>
-</p>
-
-</div>
-<!-- SECTION "Fedora Core 4 install notes" [8569-8647] -->
-<h2><a name="fedora_core_3_install_notes" id="fedora_core_3_install_notes">Fedora Core 3 install notes</a></h2>
-<div class="level2">
-
-<p>
-<a href="geda_fc3.html" class="wikilink1" title="geda:fc3">FC3 notes available here</a>
-</p>
-
-</div>
-<!-- SECTION "Fedora Core 3 install notes" [8648-8726] -->
-<h2><a name="fedora_core_2_install_notes" id="fedora_core_2_install_notes">Fedora Core 2 install notes</a></h2>
-<div class="level2">
-
-<p>
-<a href="geda_fc2.html" class="wikilink1" title="geda:fc2">FC2 notes available here</a>
-</p>
-
-</div>
-<!-- SECTION "Fedora Core 2 install notes" [8727-8805] -->
-<h2><a name="fedora_core_1_install_notes" id="fedora_core_1_install_notes">Fedora Core 1 install notes</a></h2>
-<div class="level2">
-
-<p>
-<a href="geda_fc1.html" class="wikilink1" title="geda:fc1">FC1 notes available here</a>
-</p>
-
-</div>
-<!-- SECTION "Fedora Core 1 install notes" [8806-8884] -->
-<h2><a name="suse_9.3_install_notes" id="suse_9.3_install_notes">Suse 9.3 install notes</a></h2>
-<div class="level2">
-
-<p>
-<a href="geda_suse_9.html" class="wikilink1" title="geda:suse_9.3">SuSE 9.3 notes available here</a>
-</p>
-
-</div>
-<!-- SECTION "Suse 9.3 install notes" [8885-8968] -->
-<h2><a name="suse_10.0_install_notes" id="suse_10.0_install_notes">Suse 10.0 install notes</a></h2>
-<div class="level2">
-
-<p>
-<a href="geda_suse_10.html" class="wikilink1" title="geda:suse_10.0">SuSE 10.0 notes available here</a>
-</p>
-
-</div>
-<!-- SECTION "Suse 10.0 install notes" [8969-9055] -->
-<h2><a name="suse_10.1_install_notes" id="suse_10.1_install_notes">Suse 10.1 install notes</a></h2>
-<div class="level2">
-
-<p>
-<a href="001geda_suse_10.html" class="wikilink1" title="geda:suse_10.1">SuSE 10.1 notes available here</a>
-</p>
-
-</div>
-<!-- SECTION "Suse 10.1 install notes" [9056-9142] -->
-<h2><a name="debian_install_notes" id="debian_install_notes">Debian install notes</a></h2>
-<div class="level2">
-
-<p>
-<a href="http://geda.seul.org/wiki/geda:debian"; class="wikilink1" title="geda:debian">Debian notes available here</a>
-</p>
-
-</div>
-<!-- SECTION "Debian install notes" [9143-9220] -->
-<h2><a name="ubuntu_install_notes" id="ubuntu_install_notes">Ubuntu install notes</a></h2>
-<div class="level2">
-
-<p>
-<a href="geda_ubuntu.html" class="wikilink1" title="geda:ubuntu">Ubuntu notes available here</a>
-</p>
-
-</div>
-<!-- SECTION "Ubuntu install notes" [9221-9299] -->
-<h2><a name="windows_install_notes" id="windows_install_notes">Windows install notes</a></h2>
-<div class="level2">
-
-<p>
-<a href="geda_cygwin.html" class="wikilink1" title="geda:cygwin">Cygwin notes available here</a>
-</p>
-
-</div>
-<!-- SECTION "Windows install notes" [9300-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/geda_gerbv_mp.html b/docs/wiki/geda_gerbv_mp.html
deleted file mode 100644
index 7de8951..0000000
--- a/docs/wiki/geda_gerbv_mp.html
+++ /dev/null
@@ -1,270 +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>geda:gerbv_mp</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="geda,gerbv_mp" />
-<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/geda:gerbv_mp?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gerbv_mp"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gerbv_mp"; />
-<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">
-
-
-
-<h1><a name="gerbv_man-page" id="gerbv_man-page">gerbv man-page</a></h1>
-<div class="level1">
-<pre class="code">gerbv(1) cvs-20051023 gerbv(1)
-
-
-
-NAME
- gerbv - Gerber Viewer
-
-SYNOPSIS
- gerbv [OPTIONS] [gerberfile[s]]
-
-DESCRIPTION
- gerbv is a viewer for Gerber files. Gerber files is generated from dif-
- ferent PCB CAD programs and are sent to subcontractors to actually make
- the PCB. gerbv also supports Excellon/NC drill files.
-
-
-OPTIONS
- Warning! On some platforms, which hasn�t long option available, only
- short options are available.
-
-
- gerbv Options
- -V|--version Prints the version number of gerbv and exits.
-
- -h|--help
- Prints a brief usage guide.
-
- -l <filename>|--log=<filename>
- All error messages etc are stored in a file with filename <file-
- name>.
-
- -t <filename>|--tools=<filename>
- Read Excellon tools from the file <filename>.
-
- --geometry=<width>x<height>[<+->x-position[<+->y-position]]
- Sets the the size of the window. X-position and y-position are
- currently ignored by gerbv.
-
- -p <project filename>|--project=<project filename>
- Load a stored project. Please note that the project file must be
- stored in the same directory as the gerber files.
-
-
- GTK Options
- --gtk-module=MODULE Load an additional GTK module
-
- --g-fatal-warnings
- Make all warnings fatal
-
- --gtk-debug=FLAGS
- GTK debugging flags to set
-
- --gtk-no-debug=FLAGS
- GTK debugging flags to unset
-
- --gdk-debug=FLAGS
- GDK debugging flags to set
-
- --gdk-no-debug=FLAGS
- GDK debugging flags to unset
-
- --display=DISPLAY
- X display to use
-
- --sync Make X call synchronous
-
- --no-xshm
- Don�t use X shared memory extension
-
- --name=NAME
- Program name as used by the window manager
-
- --class=CLASS
- Program class as used by the window manager
-
-
-GENERAL
- When you start gerbv you can give the files to be loaded on the command
- line, either as each file separated with a space or by using wildcards.
-
- The user interface is graphical. Simply press left mouse button and the
- image will pan as you move the mouse. To manipulate a layer, right-
- click on one of the rightmost buttons. That will bring up a pop-up menu
- where you can select what you want to do with that layer (load file,
- change color, etc).
-
- If you hold the mouse button over one the rightmost button a tooltips
- will show you the name of the file loaded on that layer.
-
- Default of concurrently loaded files are 20 layers. You can change this
- during configure with:
-
- ./configure with-maxfiles=<number>
-
-
-ACTIVATION AND DEACTIVATION OF LAYERS
- You can load several files at one time. You can then turn displaying of
- the layers on and off by clicking on one of the rightmost buttons.
-
- You can also control this from the keyboard. Press Alt, enter the num-
- ber on the layer you want activate/deactivate on the numerical keypad
- and then release the Alt key.
-
-
-ZOOMING
- Zooming can be handled by either menu choices, keypressing, middle
- mouse button or scroll wheel. If you press Alt+I you will zoom in and
- if you press Alt+O you will zoom out.If you press middle mouse button
- you will zoom out, and if you press Shift and middle mouse button you
- will zoom in. Scroll wheel works if you enabled that in your X server
- and mapped it to button 4 and 5. You can also zoom in by pressing z and
- zoom out by pressing shift+z (ie Z). You can make the image fit by
- pressing f (there is also a menu alternativ for this).
-
- You can also do zooming by outline. Press right mouse button, draw,
- release. The dashed line shows how the zooming will be dependent on
- the resolution of the window. The non-dashed outline will show what you
- actually selected. If you change your mind when started to mark out-
- line, you can always abort by pressing escape. By holding down the
- shift key when you press the right mouse button, you will select an
- area where the point you started at will be the center of your selec-
- tion.
-
-
-MEASUREMENTS
- You can do measurement on the image displayed. By pressing shift, the
- cursor changes to a plus. By using left mouse button you can draw the
- lines that you want to measure. The result of the last measurement is
- also displayed on the statusbar. All measurements are in the drawing
- until you either zoom, pan or press the escape key.
-
- The statusbar shows the current mouse position on the layer in the same
- coordinates as in the file. Ie if you have (0,0) in the middle of the
- image in the gerber files, the statusbar will show (0,0) at the same
- place.
-
-
-SUPERIMPOSING
- When you load several Gerber files, you can display them "on top of
- each other", ie superimposing. The general way to display them are that
- upper layers cover the layers beneath, which is called copy (GTK+
- terms).
-
- The other ways selectable are and, or, xor and invert. They map
- directly to corresponding functions in GTK. In GTK they are described
- as: "For colored images, only GDK_COPY, GDK_XOR and GDK_INVERT are gen-
- erally useful. For bitmaps, GDK_AND and GDK_OR are also useful."
-
-
-PROJECTS
- gerbv can also handle projects. A project consist of bunch of loaded
- layers with their resp. color and the background color. The easiest way
- to create a project is to load all files you want into the layer you
- want, set all the colors etc and do a "Save Project As...".
-
- You load a project either from the menu bar or by using the commandline
- switches -p or --project.
-
- Currently there is a limit in that the project file must be in the same
- directory as the gerber files to be loaded.
-
-
-SCHEME
- The project files are simple Scheme programs that is interpreted by a
- built in Scheme interpreter. The Scheme interpreter is TinyScheme and
- needs a Scheme program called init.scm to initialize itself. The search
- path for init.scm is (in the following order)
- /usr/local/gEDA-20060124/share/gerbv/scheme/share/gerbv/scheme/, the
- directory with the executable gerbv, the directory gerbv was invoked
- from and finally according to the environment variable
- GERBV_SCHEMEINIT.
-
-
-TOOLS FILE
- Not every Excellon drill file is self-sufficient. Some CADs produce
- .drd files where tools are only referenced, but never defined (such as
- what diameter of the tool is.) Eagle CAD is one of such CADs, and there
- are more since many board houses require Tools files.
-
- A Tools file is a plain text file which you create in an editor. Each
- line of the file describes one tool (the name and the diameter, in
- inches):
-
- T01 0.024
- T02 0.040
- ...
-
- These are the same tools (T01 etc.) that are used in the Drill file. A
- standard practice with Eagle is to create an empty Tools file, run the
- CAM processor, and the error report tells you which tools you "forgot".
- Then you put these tools into the file and rerun the CAM processor.
-
- You load a tool file by using the commandline switches -t or --tools.
- The file can have any name you wish, but Eagle expects the file type to
- be ".drl", so it makes sense to keep it this way. Some board houses are
- still using CAM software from DOS era, so you may want to excercise
- caution before going beyond the 8.3 naming convention.
-
- When gerbv reads the Tools file it also checks that there are no dupli-
- cate definitions of tools. This does happen from time to time as you
- edit the file by hand, especially if you, during design, add or remove
- parts from the board and then have to add new tools into the Tools
- file. The duplicate tools are a very serious error which will stop
- (HOLD) your board until you fix the Tools file and maybe the Excellon
- file. gerbv will detect duplicate tools if they are present, and will
- exit immediately to indicate such a fatal error in a very obvious way.
- A message will also be printed to standard error.
-
- If your Excellon file does not contain tool definitions then gerbv will
- preconfigure the tools by deriving the diameter of the drill bit from
- the tool number. This is probably not what you want, and you will see
- warnings printed on the console.
-
-
-ENVIRONMENT
- GERBV_SCHEMEINIT
- Defines where the init.scm file is stored. Used by scheme inter-
- preter, which is used by the project reader.
-
-
-AUTHOR
- Stefan Petersen (spetm at users.sourceforge.net): Overall hacker and project leader
- Andreas Andersson (e92_aan at e.kth.se): Drill file support and general hacking
- Anders Eriksson (aenfaldor at users.sourceforge.net) : X and GTK+ ideas and hacking
-
-
-COPYRIGHT
- Copyright �© 2001-2004 Stefan Petersen
-
- This document can be freely redistributed according to the terms of the
- GNU General Public License version 2.0
-
-
-
-Version Feb 8th, 2004 gerbv(1)
-</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_gerbv_pnp_readme.html b/docs/wiki/geda_gerbv_pnp_readme.html
deleted file mode 100644
index 8a72f5e..0000000
--- a/docs/wiki/geda_gerbv_pnp_readme.html
+++ /dev/null
@@ -1,145 +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>geda:gerbv_pnp_readme</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="geda,gerbv_pnp_readme" />
-<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/geda:gerbv_pnp_readme?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gerbv_pnp_readme"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gerbv_pnp_readme"; />
-<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">
-
-
-
-<h1><a name="searching_for_parts_and_marking_them_on_screen_in_gerbv" id="searching_for_parts_and_marking_them_on_screen_in_gerbv">Searching for Parts and marking them on screen (in gerbv)</a></h1>
-<div class="level1">
-<pre class="code">Searching for Parts and marking them on screen (in gerbv)
-
-THIS FUNCTIONALITY IS ONLY AVAILABLE WHEN COMPILING GERBV AGAINST GTK2!
-
-Please direct any comments, suggestions etc. to Juergen <juergenhaas@xxxxxxx>
-=============================================================================
-*** Support for Pick and Place files: ***
-*** csv-style files with/without quotes ***
-*** the following delimiters are supported ';' ':' '|' ',' ***
-----------------------------------------------------------------------------
-
-
-----------------------------------------------------------------------------
-A pick and place file has 11 columns (the first two lines a file in gerbv/examplei
-are shown here) and looks like this:
-
-Designator:Footprint:Mid X:Mid Y:Ref X:Ref Y:Pad X:Pad Y:Layer:Rotation:Comment
-
-R29:0805_REFL:25.4mm:72.644mm:25.4mm:72.644mm:25.4mm:71.6788mm:T:90.00:1K/1%
-----------------------------------------------------------------------------
-
-Some instructions for the first time user:
-
-after loading a PNP file a new dialog will come up offering various option of
-selecting and graphically marking electronic parts.
-
-Three modes of selecting items do exist:
-1)enter any search phrase and hit enter
- (See also paragraph "SCROLLING" further down)
- -Generally under linux regexp expressions are used such as ".*" i.e. '*'
- -All matches will be marked in the list AND on the screen
- -if you press ESC or press <ENTER> on an empty line it will deselect all
- items
- -if you had a selection already and you would like to add single items
- one by one, just hold down CTRL key while you left-click on the desired
- fields
-
-2)just simply use left click combined with Shift and/or CTRL for manual
- mouse driven selections
- Pressing right button of mouse will not only select but also draw item on
- selected layer
-
-3)if you have pressed <ENTER> on an empty phrase you first of all will deselect
- anything which was selected and you can then enter the so-called "assembly
- mode" by left clicking on an item and afterwards pressing space as often as
- desired, while the select parts dialog is active. The selection will move
- down the list one by one displaying the selected part in the window
- automatically (with the corresponding layer being active).
-
- Alternatively 1:
- If you had more than one item selected and you did not clear the selections list
- by <ENTER> on an empty phrase, only the first item will be taken into account
- and all others will be deselected.
-
- Alternatively 2:
- You can of course also select an item by clicking on it, pressing space will
- then proceed as described
-
- This mode also features arrows Up/Down selection, where arrow Up will reverse
- the action of arrow Down/Spacebar. Furthermore, holding SHIFT while pressing
- arrow Up/Down will increase the selection in either direction
--------------------------
-More Features:
-
-4)Inversion of selection:
- pressing this button at any given time inverts the selection concerning the
- whole list and upon clicking Mark button this new selection will be drawn
- onto screen.
-
-
-5)Top/bottom selection
- General: press mark to mark selections on screen, after choosing to select
- top or bottom parts.
-
- a)in existing selection will only remove non wanted items
- (e.g. all bottom parts if you press "top parts") from selection
-
- b)if there is no selection, all top or all bottoms parts are selected
-
-
-6)Choose available layers for marking selected parts from drop-down list
- HINT: if pick and place file is loaded last, already occupied layers
- will not be in the drop-down list
-
--------------------------------------------------------------------
-Hint 1:
-right click functionality to know Part description.
-After you have graphically marked a number of parts (say all resistors) you can
-right click onto a part which is selected in the scroll-down list of available
-parts in the search dialog.
-Its designator, comment and footprint are then shown in the statusbar and in the log window.
-This comes in handy if there are many parts you want to look at, but e.g. you already
-know a fault has occurred only on one side of the board.
-
--------------------------------------------------------------------
-Hint 2:
-SCROLLING (in the dialog window)
- Scrolling generally only occurs, if search for comments is not activated AND
- also whenever enter is hit the list will bescrolled to the first hit,
- regardless of the search mode.
- The use of BackSpace is supported.
- If you decide to select an entry from the list of completions offered, then the
- scrolling will only occur once you press enter.
-
-Example:
- imagine you are looking for an element labelled EU3:
- If you hit the first key (E) to enter a search phrase in the entry field, the
- list will be scrolled to the first element matching this key (E), also entering
- a subsequent key (U) will then further refine that and scroll to the first
- element with EU etc.
-====================================================================</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_gfdl.html b/docs/wiki/geda_gfdl.html
deleted file mode 100644
index 4deaaa5..0000000
--- a/docs/wiki/geda_gfdl.html
+++ /dev/null
@@ -1,432 +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>geda:gfdl</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="geda,gfdl" />
-<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/geda:gfdl?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gfdl"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gfdl"; />
-<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">
-
-
-
-<h1><a name="gnu_free_documentation_license" id="gnu_free_documentation_license">GNU Free Documentation License</a></h1>
-<div class="level1">
-<pre class="code"> GNU Free Documentation License
- Version 1.2, November 2002
-
-
- Copyright (C) 2000,2001,2002 Free Software Foundation, Inc.
- 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
-
-
-0. PREAMBLE
-
-The purpose of this License is to make a manual, textbook, or other
-functional and useful document "free" in the sense of freedom: to
-assure everyone the effective freedom to copy and redistribute it,
-with or without modifying it, either commercially or noncommercially.
-Secondarily, this License preserves for the author and publisher a way
-to get credit for their work, while not being considered responsible
-for modifications made by others.
-
-This License is a kind of "copyleft", which means that derivative
-works of the document must themselves be free in the same sense. It
-complements the GNU General Public License, which is a copyleft
-license designed for free software.
-
-We have designed this License in order to use it for manuals for free
-software, because free software needs free documentation: a free
-program should come with manuals providing the same freedoms that the
-software does. But this License is not limited to software manuals;
-it can be used for any textual work, regardless of subject matter or
-whether it is published as a printed book. We recommend this License
-principally for works whose purpose is instruction or reference.
-
-
-1. APPLICABILITY AND DEFINITIONS
-
-This License applies to any manual or other work, in any medium, that
-contains a notice placed by the copyright holder saying it can be
-distributed under the terms of this License. Such a notice grants a
-world-wide, royalty-free license, unlimited in duration, to use that
-work under the conditions stated herein. The "Document", below,
-refers to any such manual or work. Any member of the public is a
-licensee, and is addressed as "you". You accept the license if you
-copy, modify or distribute the work in a way requiring permission
-under copyright law.
-
-A "Modified Version" of the Document means any work containing the
-Document or a portion of it, either copied verbatim, or with
-modifications and/or translated into another language.
-
-A "Secondary Section" is a named appendix or a front-matter section of
-the Document that deals exclusively with the relationship of the
-publishers or authors of the Document to the Document's overall subject
-(or to related matters) and contains nothing that could fall directly
-within that overall subject. (Thus, if the Document is in part a
-textbook of mathematics, a Secondary Section may not explain any
-mathematics.) The relationship could be a matter of historical
-connection with the subject or with related matters, or of legal,
-commercial, philosophical, ethical or political position regarding
-them.
-
-The "Invariant Sections" are certain Secondary Sections whose titles
-are designated, as being those of Invariant Sections, in the notice
-that says that the Document is released under this License. If a
-section does not fit the above definition of Secondary then it is not
-allowed to be designated as Invariant. The Document may contain zero
-Invariant Sections. If the Document does not identify any Invariant
-Sections then there are none.
-
-The "Cover Texts" are certain short passages of text that are listed,
-as Front-Cover Texts or Back-Cover Texts, in the notice that says that
-the Document is released under this License. A Front-Cover Text may
-be at most 5 words, and a Back-Cover Text may be at most 25 words.
-
-A "Transparent" copy of the Document means a machine-readable copy,
-represented in a format whose specification is available to the
-general public, that is suitable for revising the document
-straightforwardly with generic text editors or (for images composed of
-pixels) generic paint programs or (for drawings) some widely available
-drawing editor, and that is suitable for input to text formatters or
-for automatic translation to a variety of formats suitable for input
-to text formatters. A copy made in an otherwise Transparent file
-format whose markup, or absence of markup, has been arranged to thwart
-or discourage subsequent modification by readers is not Transparent.
-An image format is not Transparent if used for any substantial amount
-of text. A copy that is not "Transparent" is called "Opaque".
-
-Examples of suitable formats for Transparent copies include plain
-ASCII without markup, Texinfo input format, LaTeX input format, SGML
-or XML using a publicly available DTD, and standard-conforming simple
-HTML, PostScript or PDF designed for human modification. Examples of
-transparent image formats include PNG, XCF and JPG. Opaque formats
-include proprietary formats that can be read and edited only by
-proprietary word processors, SGML or XML for which the DTD and/or
-processing tools are not generally available, and the
-machine-generated HTML, PostScript or PDF produced by some word
-processors for output purposes only.
-
-The "Title Page" means, for a printed book, the title page itself,
-plus such following pages as are needed to hold, legibly, the material
-this License requires to appear in the title page. For works in
-formats which do not have any title page as such, "Title Page" means
-the text near the most prominent appearance of the work's title,
-preceding the beginning of the body of the text.
-
-A section "Entitled XYZ" means a named subunit of the Document whose
-title either is precisely XYZ or contains XYZ in parentheses following
-text that translates XYZ in another language. (Here XYZ stands for a
-specific section name mentioned below, such as "Acknowledgements",
-"Dedications", "Endorsements", or "History".) To "Preserve the Title"
-of such a section when you modify the Document means that it remains a
-section "Entitled XYZ" according to this definition.
-
-The Document may include Warranty Disclaimers next to the notice which
-states that this License applies to the Document. These Warranty
-Disclaimers are considered to be included by reference in this
-License, but only as regards disclaiming warranties: any other
-implication that these Warranty Disclaimers may have is void and has
-no effect on the meaning of this License.
-
-
-2. VERBATIM COPYING
-
-You may copy and distribute the Document in any medium, either
-commercially or noncommercially, provided that this License, the
-copyright notices, and the license notice saying this License applies
-to the Document are reproduced in all copies, and that you add no other
-conditions whatsoever to those of this License. You may not use
-technical measures to obstruct or control the reading or further
-copying of the copies you make or distribute. However, you may accept
-compensation in exchange for copies. If you distribute a large enough
-number of copies you must also follow the conditions in section 3.
-
-You may also lend copies, under the same conditions stated above, and
-you may publicly display copies.
-
-
-3. COPYING IN QUANTITY
-
-If you publish printed copies (or copies in media that commonly have
-printed covers) of the Document, numbering more than 100, and the
-Document's license notice requires Cover Texts, you must enclose the
-copies in covers that carry, clearly and legibly, all these Cover
-Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on
-the back cover. Both covers must also clearly and legibly identify
-you as the publisher of these copies. The front cover must present
-the full title with all words of the title equally prominent and
-visible. You may add other material on the covers in addition.
-Copying with changes limited to the covers, as long as they preserve
-the title of the Document and satisfy these conditions, can be treated
-as verbatim copying in other respects.
-
-If the required texts for either cover are too voluminous to fit
-legibly, you should put the first ones listed (as many as fit
-reasonably) on the actual cover, and continue the rest onto adjacent
-pages.
-
-If you publish or distribute Opaque copies of the Document numbering
-more than 100, you must either include a machine-readable Transparent
-copy along with each Opaque copy, or state in or with each Opaque copy
-a computer-network location from which the general network-using
-public has access to download using public-standard network protocols
-a complete Transparent copy of the Document, free of added material.
-If you use the latter option, you must take reasonably prudent steps,
-when you begin distribution of Opaque copies in quantity, to ensure
-that this Transparent copy will remain thus accessible at the stated
-location until at least one year after the last time you distribute an
-Opaque copy (directly or through your agents or retailers) of that
-edition to the public.
-
-It is requested, but not required, that you contact the authors of the
-Document well before redistributing any large number of copies, to give
-them a chance to provide you with an updated version of the Document.
-
-
-4. MODIFICATIONS
-
-You may copy and distribute a Modified Version of the Document under
-the conditions of sections 2 and 3 above, provided that you release
-the Modified Version under precisely this License, with the Modified
-Version filling the role of the Document, thus licensing distribution
-and modification of the Modified Version to whoever possesses a copy
-of it. In addition, you must do these things in the Modified Version:
-
-A. Use in the Title Page (and on the covers, if any) a title distinct
- from that of the Document, and from those of previous versions
- (which should, if there were any, be listed in the History section
- of the Document). You may use the same title as a previous version
- if the original publisher of that version gives permission.
-B. List on the Title Page, as authors, one or more persons or entities
- responsible for authorship of the modifications in the Modified
- Version, together with at least five of the principal authors of the
- Document (all of its principal authors, if it has fewer than five),
- unless they release you from this requirement.
-C. State on the Title page the name of the publisher of the
- Modified Version, as the publisher.
-D. Preserve all the copyright notices of the Document.
-E. Add an appropriate copyright notice for your modifications
- adjacent to the other copyright notices.
-F. Include, immediately after the copyright notices, a license notice
- giving the public permission to use the Modified Version under the
- terms of this License, in the form shown in the Addendum below.
-G. Preserve in that license notice the full lists of Invariant Sections
- and required Cover Texts given in the Document's license notice.
-H. Include an unaltered copy of this License.
-I. Preserve the section Entitled "History", Preserve its Title, and add
- to it an item stating at least the title, year, new authors, and
- publisher of the Modified Version as given on the Title Page. If
- there is no section Entitled "History" in the Document, create one
- stating the title, year, authors, and publisher of the Document as
- given on its Title Page, then add an item describing the Modified
- Version as stated in the previous sentence.
-J. Preserve the network location, if any, given in the Document for
- public access to a Transparent copy of the Document, and likewise
- the network locations given in the Document for previous versions
- it was based on. These may be placed in the "History" section.
- You may omit a network location for a work that was published at
- least four years before the Document itself, or if the original
- publisher of the version it refers to gives permission.
-K. For any section Entitled "Acknowledgements" or "Dedications",
- Preserve the Title of the section, and preserve in the section all
- the substance and tone of each of the contributor acknowledgements
- and/or dedications given therein.
-L. Preserve all the Invariant Sections of the Document,
- unaltered in their text and in their titles. Section numbers
- or the equivalent are not considered part of the section titles.
-M. Delete any section Entitled "Endorsements". Such a section
- may not be included in the Modified Version.
-N. Do not retitle any existing section to be Entitled "Endorsements"
- or to conflict in title with any Invariant Section.
-O. Preserve any Warranty Disclaimers.
-
-If the Modified Version includes new front-matter sections or
-appendices that qualify as Secondary Sections and contain no material
-copied from the Document, you may at your option designate some or all
-of these sections as invariant. To do this, add their titles to the
-list of Invariant Sections in the Modified Version's license notice.
-These titles must be distinct from any other section titles.
-
-You may add a section Entitled "Endorsements", provided it contains
-nothing but endorsements of your Modified Version by various
-parties--for example, statements of peer review or that the text has
-been approved by an organization as the authoritative definition of a
-standard.
-
-You may add a passage of up to five words as a Front-Cover Text, and a
-passage of up to 25 words as a Back-Cover Text, to the end of the list
-of Cover Texts in the Modified Version. Only one passage of
-Front-Cover Text and one of Back-Cover Text may be added by (or
-through arrangements made by) any one entity. If the Document already
-includes a cover text for the same cover, previously added by you or
-by arrangement made by the same entity you are acting on behalf of,
-you may not add another; but you may replace the old one, on explicit
-permission from the previous publisher that added the old one.
-
-The author(s) and publisher(s) of the Document do not by this License
-give permission to use their names for publicity for or to assert or
-imply endorsement of any Modified Version.
-
-
-5. COMBINING DOCUMENTS
-
-You may combine the Document with other documents released under this
-License, under the terms defined in section 4 above for modified
-versions, provided that you include in the combination all of the
-Invariant Sections of all of the original documents, unmodified, and
-list them all as Invariant Sections of your combined work in its
-license notice, and that you preserve all their Warranty Disclaimers.
-
-The combined work need only contain one copy of this License, and
-multiple identical Invariant Sections may be replaced with a single
-copy. If there are multiple Invariant Sections with the same name but
-different contents, make the title of each such section unique by
-adding at the end of it, in parentheses, the name of the original
-author or publisher of that section if known, or else a unique number.
-Make the same adjustment to the section titles in the list of
-Invariant Sections in the license notice of the combined work.
-
-In the combination, you must combine any sections Entitled "History"
-in the various original documents, forming one section Entitled
-"History"; likewise combine any sections Entitled "Acknowledgements",
-and any sections Entitled "Dedications". You must delete all sections
-Entitled "Endorsements".
-
-
-6. COLLECTIONS OF DOCUMENTS
-
-You may make a collection consisting of the Document and other documents
-released under this License, and replace the individual copies of this
-License in the various documents with a single copy that is included in
-the collection, provided that you follow the rules of this License for
-verbatim copying of each of the documents in all other respects.
-
-You may extract a single document from such a collection, and distribute
-it individually under this License, provided you insert a copy of this
-License into the extracted document, and follow this License in all
-other respects regarding verbatim copying of that document.
-
-
-7. AGGREGATION WITH INDEPENDENT WORKS
-
-A compilation of the Document or its derivatives with other separate
-and independent documents or works, in or on a volume of a storage or
-distribution medium, is called an "aggregate" if the copyright
-resulting from the compilation is not used to limit the legal rights
-of the compilation's users beyond what the individual works permit.
-When the Document is included in an aggregate, this License does not
-apply to the other works in the aggregate which are not themselves
-derivative works of the Document.
-
-If the Cover Text requirement of section 3 is applicable to these
-copies of the Document, then if the Document is less than one half of
-the entire aggregate, the Document's Cover Texts may be placed on
-covers that bracket the Document within the aggregate, or the
-electronic equivalent of covers if the Document is in electronic form.
-Otherwise they must appear on printed covers that bracket the whole
-aggregate.
-
-
-8. TRANSLATION
-
-Translation is considered a kind of modification, so you may
-distribute translations of the Document under the terms of section 4.
-Replacing Invariant Sections with translations requires special
-permission from their copyright holders, but you may include
-translations of some or all Invariant Sections in addition to the
-original versions of these Invariant Sections. You may include a
-translation of this License, and all the license notices in the
-Document, and any Warranty Disclaimers, provided that you also include
-the original English version of this License and the original versions
-of those notices and disclaimers. In case of a disagreement between
-the translation and the original version of this License or a notice
-or disclaimer, the original version will prevail.
-
-If a section in the Document is Entitled "Acknowledgements",
-"Dedications", or "History", the requirement (section 4) to Preserve
-its Title (section 1) will typically require changing the actual
-title.
-
-
-9. TERMINATION
-
-You may not copy, modify, sublicense, or distribute the Document except
-as expressly provided for under this License. Any other attempt to
-copy, modify, sublicense or distribute the Document is void, and will
-automatically terminate your rights under this License. However,
-parties who have received copies, or rights, from you under this
-License will not have their licenses terminated so long as such
-parties remain in full compliance.
-
-
-10. FUTURE REVISIONS OF THIS LICENSE
-
-The Free Software Foundation may publish new, revised versions
-of the GNU Free Documentation License from time to time. Such new
-versions will be similar in spirit to the present version, but may
-differ in detail to address new problems or concerns. See
-http://www.gnu.org/copyleft/.
-
-Each version of the License is given a distinguishing version number.
-If the Document specifies that a particular numbered version of this
-License "or any later version" applies to it, you have the option of
-following the terms and conditions either of that specified version or
-of any later version that has been published (not as a draft) by the
-Free Software Foundation. If the Document does not specify a version
-number of this License, you may choose any version ever published (not
-as a draft) by the Free Software Foundation.
-
-
-ADDENDUM: How to use this License for your documents
-
-To use this License in a document you have written, include a copy of
-the License in the document and put the following copyright and
-license notices just after the title page:
-
- Copyright (c) YEAR YOUR NAME.
- Permission is granted to copy, distribute and/or modify this document
- under the terms of the GNU Free Documentation License, Version 1.2
- or any later version published by the Free Software Foundation;
- with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
- A copy of the license is included in the section entitled "GNU
- Free Documentation License".
-
-If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts,
-replace the "with...Texts." line with this:
-
- with the Invariant Sections being LIST THEIR TITLES, with the
- Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.
-
-If you have Invariant Sections without Cover Texts, or some other
-combination of the three, merge those two alternatives to suit the
-situation.
-
-If your document contains nontrivial examples of program code, we
-recommend releasing these examples in parallel under your choice of
-free software license, such as the GNU General Public License,
-to permit their use in free software.
-</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_glossaire.html b/docs/wiki/geda_glossaire.html
deleted file mode 100644
index 35de765..0000000
--- a/docs/wiki/geda_glossaire.html
+++ /dev/null
@@ -1,76 +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>geda:glossaire.fr</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-05-24T22:27:26-0400" />
-<meta name="keywords" content="geda,glossaire.fr" />
-<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/geda:glossaire.fr?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:glossaire.fr"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:glossaire.fr"; />
-<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">
-
-
-
-<h1><a name="glossaire_des_termes_de_geda_et_des_eda" id="glossaire_des_termes_de_geda_et_des_eda">Glossaire des termes de gEDA (et des EDA)</a></h1>
-<div class="level1">
-
-<p>
- La conception en électronique implique beaucoup de termes spécifiques. Quelques termes ont une signification qui ne ressemble que vaguement à leur utilisation dans la vie de tous les jours. Ce glossaire est destiné à devenir un dictionaire de termes spécifiques à la suite gEDA, de même que monde plus grand des CAO pour lâ??électronique. Malheureusement, il nâ??existe pas de méthode universelle de nommage des concepts dans le champ de la conception électronique. Le glossaire donnera des éléments sur la manière dont les choses sont appelées dans les autres suites de conception.
-</p>
-
-<p>
-<span class="hilited">(Aux auteurs du Wiki:Veuillez insérer les nouveaux termes dans lâ??ordre de lâ??alphabet)</span>
-</p>
-<ul>
-<li class="level1"><div class="li"> <strong>anneau annulaire (annular ring)</strong>: Lâ??anneau annulaire, quelque fois aussi appelé <strong>annulus</strong>, est un diamètre de cuivre qui doit être placé autour des trous métallisés comme les pastilles et les vias. La taille minimum de lâ??anneau annulaire est spécifié par les fabricants de pcb. Une spécification habituelle est de 16 mil plus large que le trou.</div>
-</li>
-<li class="level1"><div class="li"> <strong>empreinte (footprint)</strong>: Le dessin de métal et de silkscreen qui définit où vous placez un composant sur un circuit. Les empreintes sont disposées par lâ??utilisateur sur le circuit imprimé lors de la phase de « placement » (en utilisant i.e. lâ??outil open-source PCB). Une empreinte est aussi quelque fois appelée un « decal » (PADS) ou un « land-pattern ».</div>
-</li>
-<li class="level1"><div class="li"> <strong>flux de conception (design flow)</strong>: Lâ??ordre des étapes dans lequel vous faites progresser votre étude depuis le concept initial, par la saisie de schéma, lâ??ajout dâ??attribut, le netlisting et le circuit imprimé. On utilisera typiquement plusieurs outils pour accomplir différentes tâches pendant la réalisation. La Suite gEDA utilise des programmes entièrement séparés pour les différents étapes du cheminement; chaque outil de la suite lit le fichier de sortie produit par lâ??outil précédent et écrit un fichier pouvant être lu par lâ??outil suivant dans la chaîne. Le flux de conception de gEDA pour réaliser un PCB est illustré <a href="http://geda.seul.org/dokuwiki/doku.php?id=geda:usage#what_does_the_design_flow_in_geda_look_like"; class="urlextern" title="http://geda.seul.org/dokuwiki/doku.php?id=geda:usage#what_does_the_design_flow_in_geda_look_like"; rel="nofollow">ici</a>. Notez que le flux du cheminement pour des tâches différentes peut varier. Par exemple, si votre but est de simuler votre circuit, vous utiliserez un flux différent de celui montré dans le lien ci-dessus. Finalement, les autres outils de conception de PCB â?? habituellement plus simples â?? utilisent une approche monolithique dans laquelle un seul programme (albeit avec différents modes dâ??édition) est utilisé pour réaliser le montage complet. Déterminer la meilleure approche est plus une affaire de croyance personnelle.</div>
-</li>
-<li class="level1"><div class="li"> <strong>net</strong>: Un net est la représentation dâ??un fil ou dâ??une connexion électrique dans un schéma. Câ??est, basiquement, une ligne connectant deux broches de symbole. Le terme « net » est aussi quelque fois utilisé pour parler dâ??une connexion électrique (via une fil ou une piste de PCB) dans un circuit réel. Quelques outils de saisie de schéma appellent un net un « fil ».</div>
-</li>
-<li class="level1"><div class="li"> <strong>netlist</strong>: Une netlist est une représentation en fichier texte de votre circuit qui souligne les connexions entre les différents éléments du circuit, peut être indépendants des boîtiers physiques constituants les composants réels du circuit.</div>
-</li>
-<li class="level1"><div class="li"> <strong>pad</strong>: Une pastille est une zone de cuivre sur lequel un SMD sera soudé. Bien que les pastilles soient habituellement carrées, elles peuvent aussi être rondes.</div>
-</li>
-<li class="level1"><div class="li"> <strong>pin</strong>: Une patte/broche est un trou dans un circuit imprimé qui permet de connecter un composant câblé. Dans plusieurs cas, le trou est rempli de cuivre par le fabricant.</div>
-</li>
-<li class="level1"><div class="li"> <strong>pcb</strong>: Dans le contexte de gEDA, cet acronyme a deux significations distinctes:</div>
-<ol>
-<li class="level2"><div class="li"> Un abbréviation de « printed circuit board ». Câ??est la partie qui est utilisée pour connecter les composants électroniques. Elle est aussi quelque fois appelée une « carte de câblage imprimée » (PWB), bien que cette utilisation ait été abandonné.</div>
-</li>
-<li class="level2"><div class="li"> Un puissant outil open-source, utilisé pour concevoir la disposition dâ??un circuit imprimé. La sortie des outils de gaf peut être utilisée comme entrée à pcb. (<a href="http://pcb.sourceforge.net/index.html"; class="urlextern" title="http://pcb.sourceforge.net/index.html"; rel="nofollow">page d'accueil de pcb</a>)</div>
-</li>
-</ol>
-</li>
-<li class="level1"><div class="li"> <strong>rats nest</strong>: Les lignes dessinées sur la zone de travail du circuit, qui relient les pastilles devant encore être connectées avec des pistes. Contrairement aux pistes réelles, les rats nest sont des lignes droites. Si plusieurs pastilles sont impliquées dans un net, pcb tente de dessiner les rats nests avec les longueurs les plus courtes possibles.</div>
-</li>
-<li class="level1"><div class="li"> <strong>refdes</strong>: Raccourci pour « reference designator » (numéro de référence). Le numéro de référence (ou nom) dâ??un composant. Les outils gEDA se réfèrent aux refdes pour organiser les composants en internes. Câ??est la raison pour laquelle, pour une création réussie de circuit imprimé, chaque composant doit être lié avec un refdes. Habituellement, le refdes consiste quelques majuscules et un chiffre. Exemples: R1, R2, U115, CONN3. (Protel: « Designator »)</div>
-</li>
-<li class="level1"><div class="li"> <strong>slot</strong>: Quelques composants contiennent de multiples parties identiques à lâ??intérieur dâ??un boîtier. Les IO (Input/output, entrées/sorties) pour chaque partie sont disposées pour différents jeux de broches sur le boîtier. Un exemple classique est la quadruple porte NAND TTL 7400. Gschem (comme dâ??autres paquets de saisie de schéma) traite ce type de composant en vous permettant de dessiner quatre symboles NAND séparés et de sélectionner ensuite quel « slot » devrait avoir chaque symbole en attachant un attribut de slot au symbole. Dans lâ??exemple du quadruple NAND 7400, vous sélectionneriez « <code>slot=1</code> » pour la première apparition du symbole, slot=2 pour la seconde et ainsi de suite. Notez que dans gschem, vous nâ??avez besoin dâ??attacher les liaisons dâ??alimentation à un composant en slot quâ??une seule fois. (Les autres programme de saisie de schéma comme Orcad vous demandent dâ??attacher les liaisons communes â?? comme lâ??alimentation â?? sur chaque instantiation du symbole en slot.)</div>
-</li>
-<li class="level1"><div class="li"> <strong>symbole</strong>: Un symbole est la représentation dâ??un composant particulier dans votre schéma. Les exemples classiques sont les lignes en zig-zag pour les résistances (dans lâ??utilisation US néanmoins) ou un triangle pour un ampli opérationnel. En utilisant un programme de saisie de schémas (i.e. gschem), vous placez les symboles sur votre carte et alors les câbler pour créer une représentation de votre circuit.</div>
-</li>
-<li class="level1"><div class="li"> <strong>via</strong>: Un via est un trou métallisé qui qui est destiné à connecter électriquement des différentes couches du circuit imprimé. Habituellement, les vias sont aussi petits que possible pour sauvegarder de la place sur le le pcb.</div>
-</li>
-</ul>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_glossary.html b/docs/wiki/geda_glossary.html
deleted file mode 100644
index 1703a40..0000000
--- a/docs/wiki/geda_glossary.html
+++ /dev/null
@@ -1,90 +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>geda:glossary</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2008-02-02T12:10:43-0500" />
-<meta name="keywords" content="geda,glossary" />
-<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/geda:glossary?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:glossary"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:glossary"; />
-<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">
-
-
-
-<h1><a name="glossary_of_geda_and_eda_terms" id="glossary_of_geda_and_eda_terms">Glossary of gEDA (and EDA) terms</a></h1>
-<div class="level1">
-
-<p>
- The design of electronics involves a host of specific terms. Some words have a meaning that only vaguely resembles the use in everyday life. This glossary aims to be a dictionary of terms specific to the gEDA suite, as well as to the larger world of CAD for electronics. Unfortunately, there is no universal naming scheme for concepts in the area of electronic design. The glossary will give hints on how things are called in other design suites.
-</p>
-
-<p>
-<span class="hilited">(Wiki-authors: Please insert new terms according to the alphabet)</span>
-</p>
-<ul>
-<li class="level1"><div class="li"> <strong>annular ring</strong>: The annular ring, sometimes also called <strong>annulus</strong>, is a diameter of copper that needs to be placed arround metalized holes like pads and vias. The minimum size of the annular ring is specified by the pcb-fab. A common requirements is 16 mil larger than the hole.</div>
-</li>
-<li class="level1"><div class="li"> <strong>dead copper</strong>: A part of the copper layer which is not connected to any net defined in the netlist. By definition, this may be any object pcb defines. However, the term commonly refers to unconnected snippets of a polygon which is devided by a track. </div>
-</li>
-<li class="level1"><div class="li"> <strong>design flow</strong>: The order or stages through which you take your design as you progress from initial concept, through schematic capture, attribute attachment, netlisting, and layout. One typically uses different tools to accomplish different tasks during the design process. The gEDA Suite uses entirely separate programs for different stages of the flow; each tool in the suite reads the output file produced by the previous tool, and writes a file to be read by the next tool in the flow. The gEDA design flow for designing a PCB is illustrated <a href="http://geda.seul.org/dokuwiki/doku.php?id=geda:usage#what_does_the_design_flow_in_geda_look_like"; class="urlextern" title="http://geda.seul.org/dokuwiki/doku.php?id=geda:usage#what_does_the_design_flow_in_geda_look_like"; rel="nofollow">here</a>. Note that the design flow for different tasks might look different. For example, if your goal is to simulate your circuit, you will use a different flow than that shown in the link above. Finally, other â?? usually simpler â?? PCB design tools use a monolithic approach in which one single program (albeit with different edit modes) is used for the entire design. Which approach is better usually is a matter of personal religion.</div>
-</li>
-<li class="level1"><div class="li"> <strong>footprint</strong>: The pattern of metal and silkscreen which defines where you place a component on a PCB. Footprints are the placed by the user onto the PC board during the â??placementâ?? phase of PCB layout (using e.g. the open-source tool PCB). A footprint is also sometimes called called a â??decalâ?? (PADS), or a â??land-patternâ??.</div>
-</li>
-<li class="level1"><div class="li"> <strong>GTK-HID</strong>: The GTK version of the pcb user interface. â??HIDâ?? is an acronym for â??human interface deviceâ??. As the name sugests, GTK-HID uses the GTK+ widgetset and tries to comply with GTK usability standards.This is the default <acronym title="Graphical User Interface">GUI</acronym> of pcb. Menu and keyboard configuration is read from gpcb-menu.res. (See Lesstif-HID for an alternative)</div>
-</li>
-<li class="level1"><div class="li"> <strong>Lesstif-HID</strong>: The Lesstif version of the pcb user interface. It uses the Lesstif widgetset, which is the open source version of Motif. Menu and keyboard configuration read from <code>pcb-menu.res</code> try to comply with Lesstif usability standards. If you want to give this interface a try, you have to give the option <code>–with-gui=lesstif</code> at compile time.</div>
-</li>
-<li class="level1"><div class="li"> <strong>net</strong>: A net is the representation of a wire, or electrical connection in your schematic diagram. It is basically a line connecting two symbol pins. The term â??netâ?? is also sometimes used loosely to talk about an electrical connection (via a wire or PCB trace) in a real circuit. Some schematic capture tools call a net a â??wireâ??.</div>
-</li>
-<li class="level1"><div class="li"> <strong>netlist</strong>: A netlist is an text file representation of your circuit which emphasizes the connections between the different circuit elements, perhaps independently of the physical packages constituting the actual components in the circuit.</div>
-</li>
-<li class="level1"><div class="li"> <strong>pad</strong>: A pad is the patch of copper to which a SMD-component is to be soldered. Although pads are usually square, they can also be rounded.</div>
-</li>
-<li class="level1"><div class="li"> <strong>pin</strong>: A pin is a hole in the printed circuit that allows to connect a wired component. In many cases the hole is clad with copper by the pcb-fab.</div>
-</li>
-<li class="level1"><div class="li"> <strong>pcb</strong>: In the context of gEDA this acronym has two distict meanings:</div>
-<ol>
-<li class="level2"><div class="li"> An abbreviation of â??printed circuit boardâ??. This is the actual hardware that is used to connect electronic components. It is also sometimes called a â??printed wiring boardâ?? (PWB), although this usage may be dying out.</div>
-</li>
-<li class="level2"><div class="li"> A powerful, open-source tool used to design the layout of a printed circuit board. The output of the gaf tools can be used as an input to pcb.(<a href="http://pcb.sourceforge.net/index.html"; class="urlextern" title="http://pcb.sourceforge.net/index.html"; rel="nofollow">homepage of pcb</a>)</div>
-</li>
-</ol>
-</li>
-<li class="level1"><div class="li"> <strong>rats nest</strong>: The lines drawn on the pcb working area that hint which pads still need to be connected with tracks. Unlike the actual tracks the rats nest are straight lines. If multiple pads are involved in a net, pcb tries to draw rats nests with the shortest possible length.</div>
-</li>
-<li class="level1"><div class="li"> <strong>refdes</strong>: Short for â??reference designatorâ??. The unique designator (or name) of a component. The gEDA tools rely on the refdefs to organize the components internally. Therefore, for successful creation of a printed circuit board every component has to be linked with a refdes. Usually, the refdes consists of a few upper case letters and a digit. Examples: R1, R2, U115, CONN3. (Protel: â??Designatorâ??)</div>
-</li>
-<li class="level1"><div class="li"> <strong>silkscreen</strong>: This is the layer that defines the text and graphics printed on the pcb board. It usually contains the name of the board, outlines of the components and possibly their values or refdes. The origin of the name is the silk traditionally used during the print process. </div>
-</li>
-<li class="level1"><div class="li"> <strong>slot</strong>: Some components contain multiple, identical devices inside a single package. The IOs for each component are mapped to different pin sets on the package. A classic example is the TTL 7400 quad nand gate. Gschem (like other schematic capture packages) handles this type of component by allowing you to draw four separate nand gate symbols, and then selecting which <strong>slot</strong> each symbol should have by attaching a slot attribute to the symbol. In the example of the 7400 quad nand, you would select <strong><code>slot=1</code></strong> for the first appearance of the symbol, slot=2 for the second appearance, and so on. Note that in gschem you need to attach power nets to a slotted component only <strong>once</strong>. (Other schematic capture programs like Orcad require you to attach common nets â?? like power nets â?? on each instantiation of the slotted symbol.)</div>
-</li>
-<li class="level1"><div class="li"> <strong>solder layer</strong>: This is the side of the board where traditional, thru hole components are soldered. (Protel: â??Bottom Layerâ??)</div>
-</li>
-<li class="level1"><div class="li"> <strong>symbol</strong>: A symbol is the representation of a particular component in your schematic diagram. The classic examples are squiggley lines for resistors (in US usage anyway), or a triangle for an op-amp. Using a schematic capture program (e.g. gschem) you place symbols on your board, and then wire them up to create a representation of your circuit.</div>
-</li>
-<li class="level1"><div class="li"> <strong>component layer</strong>: This is the side of the board where traditional, thru hole components sit, Usually the top side of the board. (Protel: â??Top Layerâ??)</div>
-</li>
-<li class="level1"><div class="li"> <strong>thermal</strong>: A thermal is a way to connect a via with a copper plane through narrow bridges. The aim is to connect electrically, but provide enough thermal resistance to allow for convenient soldering. There is a special mode in pcb to convert the annular ring of vias into thermals. </div>
-</li>
-<li class="level1"><div class="li"> <strong>via</strong>: A via is a metalized hole that is meant to electrically connect different layers of the pcb. Usually, vias are as small as possible to save valuable real estate on the pcb.</div>
-</li>
-</ul>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_gnetlist_mp.html b/docs/wiki/geda_gnetlist_mp.html
deleted file mode 100644
index 1214a1a..0000000
--- a/docs/wiki/geda_gnetlist_mp.html
+++ /dev/null
@@ -1,242 +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>geda:gnetlist_mp</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="geda,gnetlist_mp" />
-<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/geda:gnetlist_mp?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gnetlist_mp"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gnetlist_mp"; />
-<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">
-
-
-
-<h1><a name="gnetlist_man-page" id="gnetlist_man-page">gnetlist man-page</a></h1>
-<div class="level1">
-<pre class="code">gnetlist(1) 20031231 gnetlist(1)
-
-
-
-NAME
- gnetlist - gEDA/gaf Netlist extraction/generation
-
-SYNOPSIS
- gnetlist [-i] [-I] [-q] [-s] [-v] [-l schem_file] [-m schem_file ] [-g
- guile_procedure] [-c scheme_string ] [-o output_filename] schematic1
- [... schematicN]
-
-DESCRIPTION
- gnetlist is the netlist extraction/generation program which is part
- gEDA (GPL Electronic Design Automation) toolset. This program takes a
- schematic for its input and outputs a netlist.
-
- gnetlist depends heavily on guile (a scheme based scripting language).
- It uses guile to define the output format. Basically gnetlist reads a
- schematic, creates an internal representation of the various connec-
- tions, and then a guile script extracts the connections into some
- netlist format.
-
- gnetlist is very much so a work in progress. Currently it supports the
- following backends:
-
- 1) Allegro netlist format (-g allegro)
-
- 2) BAE netlist format (-g bae)
-
- 3) BOM / BOM2 - Bill of Materials (-g bom and -g bom2)
-
- 4) Partslist 1,2,3 - More Bill of Materials (-g partslist[1-3])
-
- 5) DRC - Start of a design rule checker (-g drc)
-
- 6) DRC2 - A second design rule checker (-g drc2)
-
- 7) gEDA - native format, mainly used for testing (-g geda)
-
- 8) Gossip netlist format (-g gossip)
-
- 9) PADS netlist format (-g pads)
-
- 10) PCB / PCBboard (-g PCB and -g PCBboard)
-
- 11) gsch2pcb backend (-g gsch2pcb)
-
- 12) ProtelII netlist format (-g protelII)
-
- 13) Spice compatible netlist format (-g spice)
-
- 14) Enhanced spice compatible netlist format (-g spice-sdb)
-
- 15) Switcap netlist format (-g switcap)
-
- 16) Tango netlist format (-g tango)
-
- 17) Verilog code (-g verilog)
-
- 18) VHDL code (-g vhdl)
-
- 19) VIPEC netlist format (-g vipec)
-
- 20) Bartels Autoengineer netlist format (-g bae)
-
- 21) GOSSIP system simulation system netlist format (-g gossip)
-
- 22) MAXASCII netlist format (-g maxascii)
-
- 23) VHDL-AMS netlist format (-g vams)
-
- 24) Futurenet2 netlist format (-g futurenet2 )
-
- 25) SWITCAP switched capacitor simulator netlist format (-g
- switcap )
-
- 26) RF Cascade netlist format (-g cascade )
-
- 27) RACAL-REDAC netlist format (-g redac )
-
- 28) PCB actions file for forward annotating pin/pad names from
- schematic to layout (-g pcbpins)
-
-
- For more info on these formats please look at the README.*
-
- Please read the official (non-existant) documentation on how to use
- gnetlist, since this man page just describes the command line arguments
- and a few examples on how to run gnetlist.
-
-
-OPTIONS
- gnelist accepts the following options:
-
- -q Quiet mode on. This mode turns off all warnings/notes/mes-
- sages. (optional)
-
- -v Verbose mode on. This mode gives as much feedback to the user
- as possible. (optional)
-
- -g guile_procedure
- Specify the guile procedure which is executed to create the
- netlist.
-
- -o output_filename
- Specify the filename which will contain the netlist generated
- by gnetlist. If this option is not specified the default file-
- name is "output.net".
-
- -l scheme_file
- Specify a filename which contains scheme code to be loaded and
- execute before any backend is loaded or any guile procedure
- (using -g flag) is executed. This flag can be specified multi-
- ple times and can be used to pass information to backends.
-
- -m scheme_file
- Specify a filename which contains scheme code to be loaded and
- execute after the backend is loaded but still before any guile
- procedure (using -g flag) is executed. This flag can be speci-
- fied multiple times and can be used to pass information to
- backends. This flag, for example, allows the user to override
- variables inside of the backends (such as paths).
-
- -c string
- Pass the specified string to the guile interpreter. This
- allows you to execute arbitrary guile scripts from the command
- line. Be sure to surround the string with either single or
- double quotes to satisfy your shell. The string is execute
- before any init or netlist backend scheme code is loaded or
- executed.
-
- -I Put .INCLUDE <filename> in output file instead of model fileâ??s
- contents.
-
- -i Interactive mode. After the schematic is read in and parsed
- then go into interactive mode. Interactive mode allows the
- user to execute guile procedures directly.
-
- -s Sort output netlist (for Gnucap)
-
- schematic1 [... schematicN]
- At least one schematic file must be specified. If multiple
- schematics are specified then they are sequentially read in and
- parsed with the assumption that they are all part of the same
- design. It is important that the schematic(s) follow all the
- options (ie last).
-
-
-EXAMPLES
- These examples assume that you have a stack_1.sch in the current direc-
- tory.
-
- gnetlist requires that at least one schematic to be specified on the
- command line:
-
- ./gnetlist stack_1.sch
-
- This is not very useful since it does not direct gnetlist to do
- anything.
-
- Specify a guile procedure name to get gnetlist to output a netlist:
-
- ./gnetlist -g geda stack_1.sch
-
- The netlist output will be written to a file called "output.net"
- in the current working directory.
-
- You can specify the output filename by using the -o flag:
-
- ./gnetlist -g geda stack_1.sch -o stack.netlist
-
- The spice backend is run against the schematic(s) if you specify
- -g spice and the tango backend is run if you specify -g tango.
-
- To interact with the guile interpreter:
-
- ./gnetlist -i stack_1.sch
-
- You will get a prompt where you can execute guile procedures.
-
- To get a more verbose feedback as to what gnetlist is doing run
- with the -v flag:
-
- ./gnetlist -v -g geda stack_1.sch
-
-
-ENVIRONMENT
- No environment variables are used.
-
-
-AUTHOR
- Ales Hvezda and many others
-
-
-SEE ALSO
- gschem(1), gsymcheck(1)
-
-COPYRIGHT
- Copyright © 1999-2004 Ales Hvezda
-
- This document can be freely redistributed according to the terms of the
- GNU General Public License version 2.0
-
-
-
-
-Version December 31st, 2003 gnetlist(1)</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_gnetlist_ug.html b/docs/wiki/geda_gnetlist_ug.html
deleted file mode 100644
index 8fad7c5..0000000
--- a/docs/wiki/geda_gnetlist_ug.html
+++ /dev/null
@@ -1,431 +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>geda:gnetlist_ug</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="keywords" content="geda,gnetlist_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/"; />
-<link rel="contents" href="http://geda.seul.org/wiki/geda:gnetlist_ug?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gnetlist_ug"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gnetlist_ug"; />
-<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="#geda_gnetlist_users_guide" class="toc">gEDA gnetlist Users Guide</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#introduction" class="toc">Introduction</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#overview" class="toc">Overview</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#installation" class="toc">Installation</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#running_gnetlist" class="toc">Running gnetlist</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#schematic_symbol_requirements" class="toc">Schematic / symbol requirements</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#symbol_requirements" class="toc">Symbol requirements</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#schematic_requirements" class="toc">Schematic requirements</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#random_notes" class="toc">Random notes</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#hierarchy_support" class="toc">Hierarchy Support</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#specific_backend_info" class="toc">Specific backend info</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#scheme_backend_api" class="toc">Scheme backend API</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#overview1" class="toc">Overview</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#entry_point" class="toc">Entry Point</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#initialization_of_the_backend" class="toc">Initialization of the Backend</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#net_name_and_reference_designator_aliasing" class="toc">Net Name and Reference Designator Aliasing</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#debugging_hints" class="toc">Debugging Hints</a></span></div></li></ul>
-</li></ul>
-</li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="geda_gnetlist_users_guide" id="geda_gnetlist_users_guide">gEDA gnetlist Users Guide</a></h1>
-<div class="level1">
-
-<p>
-by: Ales Hvezda
-</p>
-
-<p>
-This document is released under <a href="http://www.gnu.org/copyleft/fdl.html"; class="urlextern" title="http://www.gnu.org/copyleft/fdl.html"; rel="nofollow">GFDL</a>
-</p>
-
-<p>
-September 21st, 2003
-</p>
-
-</div>
-<!-- SECTION "gEDA gnetlist Users Guide" [1-158] -->
-<h2><a name="introduction" id="introduction">Introduction</a></h2>
-<div class="level2">
-
-<p>
-This document describes how to use <strong>gnetlist</strong>. This document and <strong>gnetlist</strong> in general are pretty ALPHA, so keep that in mind as you use it to generate netlists. As all engineers know, it is very important that you do not blindly trust tools, assuming that they will always create correct output. <strong>gnetlist</strong> is certainly no exception to this rule. It is very important that you verify *every* netlists you create. As with most programs (including all the programs in gEDA), <strong>gnetlist</strong> comes with NO WARRANTY. Blah, I hate having to say that, but Iâ??m hoping that this warning will keep the user from assuming that <strong>gnetlist</strong> generates perfect netlists. Though if you find a bug, please let <strong>ahvezda@xxxxxxxxxxxxx</strong> know.<br/>
- This document is very rough, so please e-mail all corrections to <strong>ahvezda@xxxxxxxxxxxxx</strong> or file a bug report on the gEDA homepage at <a href="http://www.geda.seul.org/"; class="urlextern" title="http://www.geda.seul.org"; rel="nofollow">http://www.geda.seul.org</a>. Thanks!
-</p>
-
-</div>
-<!-- SECTION "Introduction" [159-1087] -->
-<h2><a name="overview" id="overview">Overview</a></h2>
-<div class="level2">
-
-<p>
-<strong>gnetlist</strong> is the gEDA netlister. It takes as input schematic files and produces a netlist. A netlist is a textual representation of a schematic. This textual representation has all of the connections between devices completely resolved. This means that all the connections associated with a net are grouped together. The netlister also handles hierarchies of schematics.<br/>
- <strong>gnetlist</strong> has a very exible architecture. The main program, which is written in C, reads in a schematic (using routines from libgeda) and creates an internal representation of the schematic data. This internal representation is then manipulated by a backend which is responsible for writing the various netlist formats. The backend for each netlist format is written in scheme (specifically Guile). This architecture not only allows for an infinite number of netlist formats, but also allows the netlister to generate other reports (like bill of material lists).<br/>
- As of 20001006 <strong>gnetlist</strong> has scheme backends to support the following netlist formats:
-</p>
-<ol>
-<li class="level1"><div class="li"> PCB & PCBboard - UNIX PCB netlist format.</div>
-</li>
-<li class="level1"><div class="li"> Allegro netlist format</div>
-</li>
-<li class="level1"><div class="li"> BAE netlist format</div>
-</li>
-<li class="level1"><div class="li"> BOM & BOM2 - Bill of Material generators</div>
-</li>
-<li class="level1"><div class="li"> DRC - Start of a design rule checker</div>
-</li>
-<li class="level1"><div class="li"> gEDA - the native format of gEDA, mainly used for testing</div>
-</li>
-<li class="level1"><div class="li"> Gossip netlist format</div>
-</li>
-<li class="level1"><div class="li"> PADS netlist format</div>
-</li>
-<li class="level1"><div class="li"> ProtelII netlist format</div>
-</li>
-<li class="level1"><div class="li"> Spice compatible netlist format</div>
-</li>
-<li class="level1"><div class="li"> Tango netlist format</div>
-</li>
-<li class="level1"><div class="li"> Verilog code</div>
-</li>
-<li class="level1"><div class="li"> VHDL code</div>
-</li>
-<li class="level1"><div class="li"> VIPEC netlist format</div>
-</li>
-<li class="level1"><div class="li"> VAMS - VHDL-AMS netlist format</div>
-</li>
-</ol>
-
-<p>
- This list is constantly growing. Several lacking features (as of 20001006) are: no support for buses, error detection and reporting is fairly limited, and … (many more).
-</p>
-
-</div>
-<!-- SECTION "Overview" [1088-2791] -->
-<h2><a name="installation" id="installation">Installation</a></h2>
-<div class="level2">
-
-<p>
-Hopefully by now you have already installed <strong>gnetlist</strong> on your machine. This document does not cover installation. You can verify the installation by running:
-</p>
-<pre class="code">libgeda-config --version
-gesym-config --version
-which gnetlist
-ldd `which gnetlist`</pre>
-
-<p>
-The first two should return the version of the installed tools (libgeda and the symbol library) and the next command should return the path to the <strong>gnetlist</strong> binary. The final command (only on Unix-like operating systems which include the ldd utility for listing dynamic dependencies of executable files or shared objects) will return which libraries are linked to <strong>gnetlist</strong>; all of the request libraries must be found for <strong>gnetlist</strong> to run. If these commands do not return the expected results, then most likely the gEDA tools are not installed properly. Please see the appropriate INSTALL docs (which came with the distribution) for more info on installing the gEDA tools.
-</p>
-
-</div>
-<!-- SECTION "Installation" [2792-3759] -->
-<h2><a name="running_gnetlist" id="running_gnetlist">Running gnetlist</a></h2>
-<div class="level2">
-
-<p>
-It is very easy to run <strong>gnetlist</strong>. <strong>gnetlist</strong> is a pure command line interface so there is no pesky <acronym title="Graphical User Interface">GUI</acronym> to get in the way <img src="lib/images/smileys/icon_smile.gif" class="middle" alt=":-)" /> For a list of command line arguments please run <code>gnetlist -h</code>.<br/>
- You need to specify the following two parameters to run gnetlists:
-</p>
-<ul>
-<li class="level1"><div class="li"> <strong>-g pro</strong>c (this specifies which backend to run against the schematics)</div>
-</li>
-<li class="level1"><div class="li"> <strong>filename.sch</strong> (this specifies the schematic files)</div>
-</li>
-</ul>
-
-<p>
- You can specify multiple schematics on the command line. The default filename for the generated netlist goes into â??<strong>output.net</strong>â?? You can change this default location by using the <strong>-o filename</strong> option.<br/>
- A few examples on running <strong>gnetlist</strong>:
-</p>
-<pre class="code">gnetlist -g geda -o stack.net stack_1.sch</pre>
-
-<p>
-(output netlist (in <strong>stack.net</strong>) for <strong>stack_1.sch</strong> using the gEDA native format)
-</p>
-
-<p>
-There are also a few debugging flags. The first one is the <strong>-v</strong> flag which enables verbose mode. Verbose mode outputs a whole bunch of information on what <strong>gnetlist</strong> is doing as well a dump of the internal representation. The <strong>-i</strong> flag which puts <strong>gnetlist</strong> into a interactive mode is very useful in debugging scheme backends and typically is not used by the end user.<br/>
- For a detailed list of command line arguments please see the <strong>gnetlist</strong> man page.
-</p>
-
-</div>
-<!-- SECTION "Running gnetlist" [3760-5041] -->
-<h2><a name="schematic_symbol_requirements" id="schematic_symbol_requirements">Schematic / symbol requirements</a></h2>
-<div class="level2">
-
-<p>
-This section describes what schematics/symbols need to have to be usable with <strong>gnetlist</strong>. In order for <strong>gnetlist</strong> to work correctly, both the schematics and supporting symbols must be correct. Basically these requirements consist of attribute specification. Attributes are used through out the gEDA system to represent information. Attributes are the only way of adding information to components, nets, pins, etc… For more detailed information about the attributes mentioned in this document, please see the <a href="geda_master_attributes_list.html" class="wikilink1" title="geda:master_attributes_list">Master Attributes List</a> document.
-</p>
-
-</div>
-<!-- SECTION "Schematic / symbol requirements" [5042-5666] -->
-<h3><a name="symbol_requirements" id="symbol_requirements">Symbol requirements</a></h3>
-<div class="level3">
-<ul>
-<li class="level1"><div class="li"> All symbols must have a <code>device=</code> attribute.</div>
-</li>
-<li class="level1"><div class="li"> All pins must have the <code>pin#=#</code> attribute. This attribute will eventually change form, but for now it is required as <code>pin#=#</code></div>
-</li>
-<li class="level1"><div class="li"> All pin should also have a <code>pinlabel=</code> attribute.</div>
-</li>
-<li class="level1"><div class="li"> For symbols which are slotted you also need the <code>slot=</code> attribute, for each slot a <code>slot#=#</code> attribute, and the <code>numslots=#</code> attribute. Slotting will also change in the near future, but for now it should be specified as above.</div>
-</li>
-<li class="level1"><div class="li"> For any power/gnd/arbitrary you need to put <code>net=</code> attributes inside the symbol. See the netattrib.txt document for more info.</div>
-</li>
-<li class="level1"><div class="li"> You can supply default values for various parameters (this is dependent on which backend you use) by taking advantage of the attribute â??promotionâ?? mechanism. See below for more info as well as the gschem documentation.</div>
-</li>
-<li class="level1"><div class="li"> For symbols which you want the netlister to completely ignore use the <code>graphical=1</code> attribute</div>
-</li>
-<li class="level1"><div class="li"> For more tips on symbols, please see the <a href="http://geda.seul.org/wiki/geda:scg"; class="wikilink1" title="geda:scg">Symbol Creation Guide</a>.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Symbol requirements" [5667-6712] -->
-<h3><a name="schematic_requirements" id="schematic_requirements">Schematic requirements</a></h3>
-<div class="level3">
-<ul>
-<li class="level1"><div class="li"> Most importantly, every component you want to show up in a netlist must have a <code>refdes=</code> attribute. This is <strong>VERY</strong> important. <strong>gnetlist</strong> should warn you if you have a component which doesnâ??t have a <code>refdes=</code>, but there have been bugs which do not cause this warning.</div>
-</li>
-<li class="level1"><div class="li"> You can label all nets using the <code>label=</code> attribute. You only need to attach this label to one net segment (of an electrically connected net) for all the net segments to inherit the label.</div>
-</li>
-<li class="level1"><div class="li"> You can have multiple schematics in a design (which is actually a confusing term since it means many different things to people). To use multiple schematics to create a single netlist, just specify them on the <strong>gnetlist</strong> command line.</div>
-</li>
-<li class="level1"><div class="li"> If you name nets the same, then these nets will be electrically connected. Same net names spawn all the specified schematics.</div>
-</li>
-<li class="level1"><div class="li"> There are quite a few issues that deal with hierarchy please see the hierarchy section below.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Schematic requirements" [6713-7689] -->
-<h3><a name="random_notes" id="random_notes">Random notes</a></h3>
-<div class="level3">
-<ul>
-<li class="level1"><div class="li"> Attributes which are not attached to anything and are inside a symbol are â??promotedâ?? to the outside of the symbol when the symbol is placed inside a schematic (in gschem). These promoted attributes are always looked at/for first before going into the symbol. So, in other words, if there is an attribute with the same name is inside a symbol and attached to the outside of the instantiated component, then the outside attribute takes precedence.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Random notes" [7690-8163] -->
-<h2><a name="hierarchy_support" id="hierarchy_support">Hierarchy Support</a></h2>
-<div class="level2">
-
-<p>
-TBA
-</p>
-
-</div>
-<!-- SECTION "Hierarchy Support" [8164-8198] -->
-<h2><a name="specific_backend_info" id="specific_backend_info">Specific backend info</a></h2>
-<div class="level2">
-
-<p>
-TBA
-</p>
-
-</div>
-<!-- SECTION "Specific backend info" [8199-8237] -->
-<h2><a name="scheme_backend_api" id="scheme_backend_api">Scheme backend API</a></h2>
-<div class="level2">
-
-<p>
-Please note that this section is still under construction. The information here should be correct, but it is not complete.
-</p>
-
-</div>
-<!-- SECTION "Scheme backend API" [8238-8392] -->
-<h3><a name="overview1" id="overview1">Overview</a></h3>
-<div class="level3">
-
-<p>
-<strong>gnetlist</strong> operates by loading the schematic database from the .sch files, building an internal representation and then calling a function specific to the desired output netlist type which performs the actual netlisting. Each <strong>gnetlist</strong> backend is contained in a file called gnet-<backend>.scm. Where <backend> is the name of the particular backend. For example, gnet-switcap.scm contains the code used by â??gnetlist -g switcapâ?? and gnet-drc.scm contains the code used by â??gnetlist -g drcâ??. The backends are written in the Scheme programming language. The particular implementation of scheme is guile which stands for GNUâ??s Ubiquitous Intelligent Language for Extensions. More information about guile may be found at <a href="http://www.gnu.org/software/guile/guile.html"; class="urlextern" title="http://www.gnu.org/software/guile/guile.html"; rel="nofollow">http://www.gnu.org/software/guile/guile.html</a>.
-</p>
-
-</div>
-<!-- SECTION "Overview" [8393-9182] -->
-<h3><a name="entry_point" id="entry_point">Entry Point</a></h3>
-<div class="level3">
-
-<p>
-Each netlist backend is required to provide a function whose name matches the netlist type. For example, the switcap backend contained in gnet-switcap.scm must provide a function called â??switcapâ??. That is the function which <strong>gnetlist</strong> will call to initiate the netlisting. The entry point function is given a single argument which is the filename for the output netlist. Typically the first thing a netlister does is to open the output file for writing.<br/>
- The following excerpt from the switcap backend shows the start of the entry point function and shows the output file being opened. At the end of the function, the output file is closed.
-</p>
-<pre class="code">;; ---------------------------------------
-;; Switcap netlist generation -- top level
-;; ---------------------------------------
-(define switcap
- (lambda (output-filename)
- (let ((port (open-output-file output-filename)))
-
-;; rest of netlisting goes here
-
-;; close the output file and return
- (close-output-port port))))</pre>
-
-</div>
-<!-- SECTION "Entry Point" [9183-10192] -->
-<h3><a name="initialization_of_the_backend" id="initialization_of_the_backend">Initialization of the Backend</a></h3>
-<div class="level3">
-
-<p>
-After opening the output netlist, any specific initializations which must be done for the particular netlist are done. In the switcap example, we must initialize a net name and reference designator (refdes) aliasing database. This is because switcap has more restrictive requirements on its net names than gschem does. In addition, the reference designators in a switcap netlist have special requirements. To deal with this situation, <strong>gnetlist</strong> provides some general purpose functions which rename nets and reference designators to comply with the target netlist requirements. More details on this later. For now, just note that the switcap backend uses the following code:
-</p>
-<pre class="code">;; initialize the net-name aliasing
-(gnetlist:build-net-aliases switcap:map-net-names
- all-unique-nets)
-
-;; initialize the refdes aliasing
-(gnetlist:build-refdes-aliases switcap:map-refdes
- packages)</pre>
-
-<p>
-The other initialization which is typically done, although not required by all netlist types, is to output some sort of header. This header may be explicitly contained in the entry point function or it may be contained in its own function for code clarity. In the switcap backend, the call is:
-</p>
-<pre class="code">(switcap:write-top-header port)</pre>
-
-<p>
-Note that the convention is for any backend specific functions to have their names prefixed by the backend name. For example all switcap specific functions begin with â??switcap:". Functions which are available to all backends and provided by <strong>gnetlist</strong> are prefixed by â??gnetlist:".<br/>
- The definition of â??switcap:write-top-headerâ?? is
-</p>
-<pre class="code">;;
-;; Switcap netlist header
-;;
-(define switcap:write-top-header
- (lambda (port)
- (display
- "/* Switcap netlist produced by gnetlist (part of gEDA) */\n"
- port)
- (display
- "/* See http://www.geda.seul.org for more information. */\n"
- port)
- (display
- "/* Switcap backend written by Dan McMahill */\n"
- port)
- (display "\n\n" port)
- )
- )</pre>
-
-<p>
-The entry point function continues by calling functions for each section in the output netlist. The variable â??packagesâ?? is predefined by <strong>gnetlist</strong> to be a list of all components in the design and â??all-unique-netsâ?? is a list of all the nets in the design. The various functions used by the backend for each section in the netlist will use these variables. For example, the main part of the switcap netlist which contains the components and their connectivity is written to the output file with
-</p>
-<pre class="code">(switcap:write-netlist port packages)</pre>
-
-</div>
-<!-- SECTION "Initialization of the Backend" [10193-12761] -->
-<h3><a name="net_name_and_reference_designator_aliasing" id="net_name_and_reference_designator_aliasing">Net Name and Reference Designator Aliasing</a></h3>
-<div class="level3">
-
-<p>
-It is common for a target netlist type to have a more restrictive requirement for the net names than gschem does. For example, there may be restrictions on length, allowed characters, or case. To address this issue, <strong>gnetlist</strong> provides a net name aliasing feature. To use this feature, the function â??gnetlist:build-netaliasesâ?? is called as part of the initialization section of the entry point function.<br/>
- For example in the switcap backend,
-</p>
-<pre class="code">;; initialize the net-name aliasing
-(gnetlist:build-net-aliases switcap:map-net-names
- all-unique-nets)</pre>
-
-<p>
-The function â??switcap:map-net-namesâ?? is a backend specific (switcap in this case) function which accepts a gschem net name as an argument and returns a modified net name which meets the requirements for the output netlist format. In the case of switcap, the requirement is ground must be called â??0â??, nets may have no more than 7 characters, and the netlist is not case sensitive.
-</p>
-<pre class="code">;; This procedure takes a net name as determined by
-;; gnetlist and modifies it to be a valid SWITCAP net name.
-;;
-(define switcap:map-net-names
- (lambda (net-name)
- (let ((rx (make-regexp "^unnamed_net"))
- (net-alias net-name)
- )
- ;; XXX we should use a dynamic regexp based on the
- ;; current value for the unnamed net base string.
-
- (cond
- ;; Change "GND" to "0"
- ((string=? net-name "GND") (set! net-alias "0"))
- ;; remove the 'unnamed_net' part
- ((regexp-exec rx net-name)
- (set! net-alias (substring net-name 11)))
- (else net-name)
- )
-
- ;; Truncate to 7 characters
- (if (> (string-length net-alias) 7)
- (set! net-alias (substring net-alias 0 7))
- )
-
- ;; Convert to all upper case
- (string-upcase net-alias)
-
- )
- )
-)</pre>
-
-<p>
-The function â??gnetlist:build-net-aliasesâ?? creates a database which later on lets you look up the output net name from the gschem net name or the gschem net name from the output net name. In addition it does the very important task of ensuring that no shorts are created by modifying the net names. As an example suppose you had a net called â??MyNetâ?? and another called â??mynetâ?? in the schematic. Those are unique but after converting both to upper case they become a single net. â??gnetlist:build-net-aliasesâ?? will detect this condition and issue an error and stop netlisting.<br/>
- Now that the database has been initialized, the netlister simply uses
-</p>
-<pre class="code">(gnetlist:alias-net somenet)</pre>
-
-<p>
-to retrive the netlist net name from the gschem net name.<br/>
- A similar set of functions are provided for reference designator aliasing.
-</p>
-
-</div>
-<!-- SECTION "Net Name and Reference Designator Aliasing" [12762-15433] -->
-<h3><a name="debugging_hints" id="debugging_hints">Debugging Hints</a></h3>
-<div class="level3">
-
-<p>
-A useful debugging tool is to run <strong>gnetlist</strong> in interactive mode. This is done by using the "-iâ?? option to <strong>gnetlist</strong>. This will give you a shell where you may enter scheme commands. This provides a simple way to examine various variables and try out various functions.<br/>
- An example of running <strong>gnetlist</strong> in interactive mode is shown below.
-</p>
-<pre class="code">% gnetlist -i ../../gnetlist/examples/switcap/*.sch
-gEDA/gnetlist version 20041228
-gEDA/gnetlist comes with ABSOLUTELY NO WARRANTY; see COPYING for more details.
-This is free software, and you are welcome to redistribute it under certain
-conditions; please see the COPYING file for more details.
-
-Loading schematic [../../gnetlist/examples/switcap/analysis.sch]
-Loading schematic [../../gnetlist/examples/switcap/ckt.sch]
-Loading schematic [../../gnetlist/examples/switcap/clocks.sch]
-gnetlist> all-unique-nets
- ("unnamed_net6" "unnamed_net5" "unnamed_net4" "OUT" "unnamed_net3"
- "unnamed_net2" "unnamed_net1" "GND")
- gnetlist> packages
- ("TIMING" "CLK1" "S7" "S8" "S6" "S5" "C3" "S4" "C2" "C1" "E1" "S3"
- "S1" "V1" "S2" "OPTIONS" "TITLE" "ANA1")
- gnetlist> (quit)
- %</pre>
-
-</div>
-<!-- SECTION "Debugging Hints" [15434-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/geda_grcsan.html b/docs/wiki/geda_grcsan.html
deleted file mode 100644
index dabb120..0000000
--- a/docs/wiki/geda_grcsan.html
+++ /dev/null
@@ -1,305 +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>geda:grcsan</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="keywords" content="geda,grcsan" />
-<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/geda:grcsan?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:grcsan"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:grcsan"; />
-<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="#geda_gaf_rf_cascade_symbols_and_netlister" class="toc">gEDA/gaf RF Cascade Symbols and Netlister</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#overview" class="toc">Overview</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#requirements" class="toc">Requirements</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#creating_schematics" class="toc">Creating Schematics</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#extracting_the_cascade_input_file" class="toc">Extracting the Cascade Input File</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#running_cascade" class="toc">Running Cascade</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#appendix_a_--_symbols_in_the_library" class="toc">Appendix A -- Symbols in the Library</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#sources_cascade-source" class="toc">Sources (cascade-source)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#defaults_cascade-default" class="toc">Defaults (cascade-default)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#elements" class="toc">Elements</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#example" class="toc">Example</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#example_schematics" class="toc">Example Schematics</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#netlist_the_design" class="toc">Netlist the Design</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#run_the_analysis" class="toc">Run the Analysis</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#document_revision_history" class="toc">Document Revision History</a></span></div></li></ul>
-</li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="geda_gaf_rf_cascade_symbols_and_netlister" id="geda_gaf_rf_cascade_symbols_and_netlister">gEDA/gaf RF Cascade Symbols and Netlister</a></h1>
-<div class="level1">
-
-<p>
-by: Dan McMahill
-</p>
-
-<p>
-This document is released under <a href="http://www.gnu.org/copyleft/fdl.html"; class="urlextern" title="http://www.gnu.org/copyleft/fdl.html"; rel="nofollow">GFDL</a>
-</p>
-
-<p>
-December 3rd, 2003
-</p>
-
-</div>
-<!-- SECTION "gEDA/gaf RF Cascade Symbols and Netlister" [1-173] -->
-<h2><a name="overview" id="overview">Overview</a></h2>
-<div class="level2">
-
-<p>
-This document describes the symbol library and gnetlist backend which support driving RF Cascade (<a href="http://rfcascade.sourceforge.net/"; class="urlextern" title="http://rfcascade.sourceforge.net"; rel="nofollow">http://rfcascade.sourceforge.net</a>) simulations from the gEDA/gaf system. Cascade is a noise figure and distortion analysis tool geared towards radio receiver design.<br/>
- The basic steps involved with using gEDA as the frontend for Cascade simulations are:
-</p>
-<ol>
-<li class="level1"><div class="li"> Create schematics of the circuit.</div>
-</li>
-<li class="level1"><div class="li"> Extract the netlist.</div>
-</li>
-<li class="level1"><div class="li"> Run Cascade.</div>
-</li>
-</ol>
-
-</div>
-<!-- SECTION "Overview" [174-630] -->
-<h2><a name="requirements" id="requirements">Requirements</a></h2>
-<div class="level2">
-
-<p>
-You will need the following programs to be installed:
-</p>
-<ul>
-<li class="level1"><div class="li"> A recent version of gEDA/gaf. To see if your version is recent enough, see if the directory <strong><code>$prefix/share/gEDA/sym/cascade</code></strong> exists. <strong><code>$prefix</code></strong> is the installation prefix for gEDA on your system.</div>
-</li>
-<li class="level1"><div class="li"> RF Cascade. The executable is usually called cascade. If you do not have Cascade available on your system, you will need to get a copy from <a href="http://rfcascade.sourceforge.net/"; class="urlextern" title="http://rfcascade.sourceforge.net"; rel="nofollow">http://rfcascade.sourceforge.net</a>.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Requirements" [631-1103] -->
-<h2><a name="creating_schematics" id="creating_schematics">Creating Schematics</a></h2>
-<div class="level2">
-
-<p>
-When creating a block diagram in the gschem schematic editor, use only the symbols from the cascade library. Every block diagram must have a \cascadesourceâ?? element. In addition, the block diagram must be a simple cascade. No parallel paths or branches are allowed.<br/>
- All instances must have a unique reference designator. For a receiver block diagram, this is often times best achieved by manually entering them. The only restriction on reference designator names is that they contain no spaces. A descriptive name such as \RF Filterâ?? or \First Mixerâ?? is useful as it will show up in the cascade output report.
-</p>
-
-</div>
-<!-- SECTION "Creating Schematics" [1104-1748] -->
-<h2><a name="extracting_the_cascade_input_file" id="extracting_the_cascade_input_file">Extracting the Cascade Input File</a></h2>
-<div class="level2">
-
-<p>
-To extract the Cascade input file, run:
-</p>
-<pre class="code">gnetlist -g cascade -o test.cas file1.sch [file2.sch ...]</pre>
-
-<p>
-For the example file contained in this archive, you can run:
-</p>
-<pre class="code">gnetlist -g cascade -o example.cas example.sch</pre>
-
-<p>
-The netlist will be left in <strong><code>example.cas</code></strong>.
-</p>
-
-</div>
-<!-- SECTION "Extracting the Cascade Input File" [1749-2078] -->
-<h2><a name="running_cascade" id="running_cascade">Running Cascade</a></h2>
-<div class="level2">
-
-<p>
-Cascade is exceptionally simple to run. Just run:
-</p>
-<pre class="code">cascade example.cas > example.out</pre>
-
-<p>
-to run the analysis on the system contained in the file <strong><code>example.cas</code></strong> and write the results to the file <strong><code>example.out</code></strong>. Refer to the Cascade documentation for complete details.
-</p>
-
-</div>
-<!-- SECTION "Running Cascade" [2079-2393] -->
-<h2><a name="appendix_a_--_symbols_in_the_library" id="appendix_a_--_symbols_in_the_library">Appendix A -- Symbols in the Library</a></h2>
-<div class="level2">
-
-<p>
-Please note that all instances must have the <strong><code>refdes=</code></strong> attribute set.
-</p>
-
-</div>
-<!-- SECTION "Appendix A -- Symbols in the Library" [2394-2519] -->
-<h3><a name="sources_cascade-source" id="sources_cascade-source">Sources (cascade-source)</a></h3>
-<div class="level3">
-
-<p>
-Source. Attributes:
-</p>
-<ul>
-<li class="level1"><div class="li"> C=Carrier level in dBm. Optional.</div>
-</li>
-<li class="level1"><div class="li"> CN0=Carrier to Noise Spectral Density Ratio in dBm/Hz. Optional.</div>
-</li>
-<li class="level1"><div class="li"> CN=Carrier to Noise Ratio in dB. Optional.</div>
-</li>
-<li class="level1"><div class="li"> BW=Signal Bandwidth in Hz. Optional, but requred if CN= is used.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Sources (cascade-source)" [2520-2798] -->
-<h3><a name="defaults_cascade-default" id="defaults_cascade-default">Defaults (cascade-default)</a></h3>
-<div class="level3">
-
-<p>
-This symbol sets the default impedance levels as well as the correlation coeffcient used for third order distortion calculations. There are two versions of this symbol. One is used to set the defaults at the beginnng of the definition. The other can be placed in series with the cascade to change the defaults part way through. This is useful if you wish to change impedance levels in the middle of the receiver chain. Attributes:
-</p>
-<ul>
-<li class="level1"><div class="li"> RIN=Default block input resistance in Ohms. Optional.</div>
-</li>
-<li class="level1"><div class="li"> ROUT=Default block output resistance in Ohms. Optional.</div>
-</li>
-<li class="level1"><div class="li"> RHO=Default third order distortion correlation coeffcient. Optional.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Defaults (cascade-default)" [2799-3458] -->
-<h3><a name="elements" id="elements">Elements</a></h3>
-<div class="level3">
-
-<p>
-Cascade characterizes each block in a system by its gain and optionally noise figure and third order intercept point. As such, there is no distinction between various elements such as amplifiers, filters, and mixers. The gEDA/gaf RF Cascade symbol library contains different symbols for clarity in the diagram only. The currently available element symbols are: Attributes:
-</p>
-<table class="inline">
- <tr>
- <td>cascade-amp</td><td>Amplifier</td>
- </tr>
- <tr>
- <td>cascade-filter</td><td>Filter</td>
- </tr>
- <tr>
- <td>cascade-mixer</td><td>Mixer</td>
- </tr>
- <tr>
- <td>cascade-transformer</td><td>Transformer</td>
- </tr>
- <tr>
- <td colspan="2"> </td>
- </tr>
- <tr>
- <td colspan="2"> Table 1: Element Types </td>
- </tr>
-</table>
-<ul>
-<li class="level1"><div class="li"> Gain is specified by one of the following:</div>
-<ul>
-<li class="level2"><div class="li"> <strong>G</strong>=Power gain in dB.</div>
-</li>
-<li class="level2"><div class="li"> <strong>GP</strong>=Power gain in dB.</div>
-</li>
-<li class="level2"><div class="li"> <strong>GV</strong>=Voltage gain in dB.</div>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"> <strong>NF</strong>=Noise Figure in dB. Optional.</div>
-</li>
-<li class="level1"><div class="li"> <strong>IIP3</strong>=Input Third Order Intercept Point in dBm. Optional.</div>
-</li>
-<li class="level1"><div class="li"> <strong>RIN</strong>=Block input resistance in Ohms. Optional.</div>
-</li>
-<li class="level1"><div class="li"> <strong>ROUT</strong>=Block output resistance in Ohms. Optional.</div>
-</li>
-<li class="level1"><div class="li"> <strong>RHO</strong>=Third order distortion correlation coeffcient. Optional.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Elements" [3459-4416] -->
-<h2><a name="example" id="example">Example</a></h2>
-<div class="level2">
-
-<p>
-This appendix provides a simple example of the entire process of generating a schematic, producing a Cascade input file, running an analysis and looking at the result.
-</p>
-
-</div>
-<!-- SECTION "Example" [4417-4605] -->
-<h3><a name="example_schematics" id="example_schematics">Example Schematics</a></h3>
-<div class="level3">
-
-<p>
-Figure 1 shows the schematic of a simple receiver signal chain.<br/>
- Figure 2 shows the contents of the example.cas file.
-</p>
-<table class="inline">
- <tr>
- <td> <a href="_detail/geda_rf_cascade_figure1.html" class="media" title="geda:rf_cascade_figure1.jpg"><img src="_media/geda_rf_cascade_figure1.jpg" class="media" title="rf_cascade_figure1.jpg" alt="rf_cascade_figure1.jpg" /></a> </td>
- </tr>
- <tr>
- <td> <a href="_detail/geda_rf_cascade_figure2.html" class="media" title="geda:rf_cascade_figure2.jpg"><img src="_media/geda_rf_cascade_figure2.jpg" class="media" title="rf_cascade_figure2.jpg" alt="rf_cascade_figure2.jpg" /></a> </td>
- </tr>
-</table>
-
-</div>
-<!-- SECTION "Example Schematics" [4606-4829] -->
-<h3><a name="netlist_the_design" id="netlist_the_design">Netlist the Design</a></h3>
-<div class="level3">
-
-<p>
-To netlist the design, run:
-</p>
-<pre class="code">gnetlist -g cascade example.cas example.sch</pre>
-
-</div>
-<!-- SECTION "Netlist the Design" [4830-4944] -->
-<h3><a name="run_the_analysis" id="run_the_analysis">Run the Analysis</a></h3>
-<div class="level3">
-
-<p>
-Run the analysis with:
-</p>
-<pre class="code">cascade example.cas</pre>
-
-</div>
-<!-- SECTION "Run the Analysis" [4945-5028] -->
-<h2><a name="document_revision_history" id="document_revision_history">Document Revision History</a></h2>
-<div class="level2">
-<table class="inline">
- <tr>
- <td>December 3rd, 2003</td><td>Created cascade.tex</td>
- </tr>
-</table>
-
-</div>
-<!-- SECTION "Document Revision History" [5029-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/geda_grenum_mp.html b/docs/wiki/geda_grenum_mp.html
deleted file mode 100644
index b3330d7..0000000
--- a/docs/wiki/geda_grenum_mp.html
+++ /dev/null
@@ -1,88 +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>geda:grenum_mp</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="keywords" content="geda,grenum_mp" />
-<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/geda:grenum_mp?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:grenum_mp"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:grenum_mp"; />
-<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">
-
-
-
-<h1><a name="grenum_man-page" id="grenum_man-page">grenum man-page</a></h1>
-<div class="level1">
-<pre class="code">grenum(1) grenum(1)
-
-
-
-NAME
- grenum - An advanced refdes renumber utility
-
-
-SYNOPSIS
- grenum [-v|--version -h|--help -p|--pagejump] infile1.sch infile2.sch
- ...
-
-
-
-DESCRIPTION
- The grenum program will renumber the refdes definitions read from
- infile.
-
-
-OPTIONS
- -p, --pagejump
- This will switch on the page jump mode. It means that refdes�s
- from each inputfile gets renumbered from 100,200... etc.
-
- -v, --version
- prints version information
-
- -h, --help
- prints help message
-
-
-RETURN VALUE
- grenum will return 0 if all files processed successfully, -1 if there
- was no input file specified, -2 if I/O files can�t be opened/written,
- -3 if there is parse error in input file, -4 if there is not enough
- memory to store refdes prefixes.
-
-BUGS
- If you find one, please report it to:
-
-
-AUTHOR
- Levente Kovacs
-
- Levente.Kovacs@xxxxxxxxxxxx
-
-
-SEE ALSO
- gschem(1)
-
-
-
- grenum(1)
-</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_gsch2pcb_readme.html b/docs/wiki/geda_gsch2pcb_readme.html
deleted file mode 100644
index 0044578..0000000
--- a/docs/wiki/geda_gsch2pcb_readme.html
+++ /dev/null
@@ -1,143 +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>geda:gsch2pcb_readme</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="geda,gsch2pcb_readme" />
-<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/geda:gsch2pcb_readme?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gsch2pcb_readme"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gsch2pcb_readme"; />
-<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">
-
-
-
-<h1><a name="gsch2pcb_gschem_to_pcb_readme" id="gsch2pcb_gschem_to_pcb_readme">gsch2pcb (gschem to PCB) README</a></h1>
-<div class="level1">
-<pre class="code">gsch2pcb
---------
-gsch2pcb is a program that interfaces a set of schematics generated with
-with the gEDA gschem to PCB layout files.
-
-gsch2pcb is conceptually similar to the gschem2pcb shell script, but
-additionally handles multiple schematics, handles file element footprints,
-and removes pc board elements corresponding to components deleted from the
-schematics. It also forward annotates component value changes.
-
-Using gsch2pcb allows you to drive all design changes from the gschem
-schematics without the headache of manually keeping PCB elements and
-element values in sync.
-
-It requires that the gnet-gsch2pcb.scm file be install into the gEDA
-scheme directory. On Debian this is /usr/share/gEDA/scheme, but see
-the INSTALL file.
-
-Typical usage
--------------
-1) Create your custom PCB elements and save each one into its own file.
- Some compatibility tips if you will be inserting elements into a
- layout manually as well as with gsch2pcb:
- * Make the initial "Description" field of these elements the same
- as the file name because gsch2pcb depends on this name (which is
- the gschem footprint
- value) to know when footprints/elements are changed.
- * Make the initial layout-name field (displayed when the "name on PCB"
- menu entry is selected) empty (ie "") so that gsch2pcb
- will not delete your element when you want it to be in the layout
- even though it is not in the schematic. You can later edit the
- layout-name to be some refdes value, but I'm not sure it makes sense
- to name a PCB element that is not referenced in the schematic.
-
- Note: since once a layout element is named PCB won't let you reset it
- to an empty name, a sort of kludge is that setting the first character
- of the layout-name to a non-alphanumeric will protect the element from
- being deleted by gsch2pcb.
-
- These file elements should be placed in a directory heirarchy that
- gsch2pcb will search. The default directories /usr/local/pcb_lib and
- ./packages are searched in addition to any directories you specify with
- --elements-dir dirname arguments to gsch2pcb.
-
-2) Create your schematic with gschem. Make sure each component has a
- unique refdes attribute and a footprint attribute that matches either
- a PCB m4 element or one of your custom file element names. Beware of
- file element names that collide with PCB m4 macro names (or specify the
- use-files option).
- Make a project file if you wish.
-
-3) Run "gsch2pcb foo.sch" or "gsch2pcb myproject" if you've created the
- myproject file. If you didn't specify an output name, this will generate
- a foo.pcb and a foo.net file.
- If you get errors about footprints not found, you need to create PCB
- elements for them and repeat this step until you get no errors.
- Or, just run gsch2pcb again and it will shift unfound elements to
- foo.new.pcb and you can proceed using PCB on foo.pcb if you wish to
- fix the errors from inside of PCB.
-
-4) Run "pcb foo.pcb". All the elements will be stacked on top of each other,
- so move them to desired locations. Load the netlist file foo.net and
- proceed with using PCB.
-
-5) Modify foo.sch and again run "gsch2pcb foo.sch".
- * If components were added, PCB elements for them will be placed in the
- file foo.new.pcb. If components were deleted, the elements for them
- will be removed from foo.pcb and the original foo.pcb will be renamed
- to a foo.pcb.bak sequence.
- * If elements can't be found for new schematic footprints, then the
- unfound elements will be indicated with PKG_ lines in foo.new.pcb
- unless you run "gsch2pcb --remove-unfound foo.sch" which will omit
- the PKG_ lines so you can go ahead and load foo.new.pcb into PCB.
- * Note that If you have added elements to the .pcb layout which
- will not exist on the schematics (mounting holes, etc), make sure
- there is no "name on PCB" (the gschem refdes) for them or else gsch2pcb
- will delete them when they don't match a schematic refdes and footprint.
- You could use the --preserve option to prevent deleting any elements at
- all, but this is really not the best way to use gsch2pcb.
-
-6) Run "pcb foo.pcb" and clean up any dangling traces left over from removed
- elements. Load any new elements in foo.new.pcb with the "Load layout
- data to paste-buffer" function. Load the new netlist foo.net.
-
-
-Caveats
--------
-* gsch2pcb uses a gnetlist backend gnet-gsch2pcb.scm, so be sure when you
- install gsch2pcb that the gnet-gsch2pcb.scm file gets installed into the
- right place. Look at the INSTALL file in the tarball.
-
-* WARNING: if you wish to start processing with gsch2pcb any existing PCB
- files that have m4 elements and were originally generated with gschem2pcb,
- then be sure to run first with at least gsch2pcb 0.4:
-
- gsch2pcb --fix-elements
-
- on the PCB file schematics or else gsch2pcb will want to delete the
- m4 elements.
-
-* footprint information is saved into PCB element's Description fields,
- so it's probably not a good idea to change element Description values
- in your layout while using gsch2pcb unless it is a protected element
- that has an empty layout-name.
-
-
-
-Bill Wilson billw@xxxxxx
-</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_gsch2pcb_tutorial.html b/docs/wiki/geda_gsch2pcb_tutorial.html
deleted file mode 100644
index 465937b..0000000
--- a/docs/wiki/geda_gsch2pcb_tutorial.html
+++ /dev/null
@@ -1,882 +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>geda:gsch2pcb_tutorial</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2008-02-28T17:48:29-0500" />
-<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/"; />
-<link rel="contents" href="http://geda.seul.org/wiki/geda:gsch2pcb_tutorial?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gsch2pcb_tutorial"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gsch2pcb_tutorial"; />
-<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_-_gsch2pcb_-_pcb" class="toc">gschem -> gsch2pcb -> PCB</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#terminology" class="toc">Terminology</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#setup" class="toc">Setup</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#simple_example" class="toc">Simple Example</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#create_schematicone.sch" class="toc">Create schematic: one.sch</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#edit_the_attributes_of_the_components_on_the_schematic" class="toc">Edit the attributes of the components on the schematic.</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#create_schematictwo.sch" class="toc">Create schematic: two.sch</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#generate_pcb_files_from_schematics" class="toc">Generate PCB Files from Schematics</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#layout_pcb_files" class="toc">Layout PCB Files</a></span></div></li>
-</ul>
-</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="#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>
-</div>
-</div>
-
-
-
-<h1><a name="gschem_-_gsch2pcb_-_pcb" id="gschem_-_gsch2pcb_-_pcb">gschem -> gsch2pcb -> PCB</a></h1>
-<div class="level1">
-
-<p>
-This is a tutorial on the process of using gsch2pcb as an interface between gschem and PCB. It assumes the gEDA, PCB and gsch2pcb packages are already installed and ready to use. Starting with gEDA 20030901, gsch2pcb is packaged with gEDA and doesnâ??t need to be separately installed. This tutorial is functional and intended to generate results as quickly as possible. It is not a complete reference on gschem or PCB, but it does show with a simple example design all the steps one might need to take.
-</p>
-
-<p>
-The goal is to use gsch2pcb as the bridge between gschem and PCB so that the schematics can always be in sync with the PCB layout because all element additions or deletions in the layout will automatically be driven by changes in the schematics. Back annotation from PCB to gschem is currently not possible.
-</p>
-
-<p>
-See the <a href="geda_gsch2pcb_tutorial_releasenotes.html" class="wikilink1" title="geda:gsch2pcb_tutorial_releasenotes">release notes</a> for the history of this tutorial.
-</p>
-
-</div>
-<!-- SECTION "gschem -> gsch2pcb -> PCB" [1-947] -->
-<h2><a name="terminology" id="terminology">Terminology</a></h2>
-<div class="level2">
-
-<p>
-With gschem, you add symbols representing electronic components to a schematic. A symbol is a group of pins, attributes, and lines showing an iconic representation of an electronic component. Pins in symbols are connected to other pins by drawing a net connection between them. Attributes are just named tags attached to symbols to convey some bit of information. For using the schematic with PCB, there are three of these attributes which are relevant and must be specified. Each added symbol should have a <strong>footprint, value,</strong> and <strong>refdes</strong> attribute.
-</p>
-
-<p>
-The schematic <strong>footprint</strong> attribute value of a symbol is the name of the PCB element to be placed on the layout for that instance of the symbol. A PCB element is a group of pins, pads, and silk layer outlines physically corresponding to electronic components. It is probably a source of confusion for newcomers to PCB that elements are of two different types. There are the original m4 macro generated PCB elements and since PCB version 1.7 there are also the newlib style file elements. A file element is a single fixed element in a single file. However, many m4 macro element definitions may exist in a single m4 element file. The macros can be given arguments to provide programmable elements of variable number of pins or spacings. Using these two types will be covered in this tutorial and I will be referring to these distinct element types as <strong>m4 elements</strong> and <strong>file elements</strong>. When you run PCB, the gschem <strong>footprint</strong> attribute value will appear as the displayed element name when you select <strong>Description</strong> from the <strong>Screen→Displayed Element Name</strong> menu because gsch2pcb uses this field to keep track of which <strong>footprint</strong> corresponds to a particular PCB element.
-</p>
-
-<p>
-The gschem <strong>refdes</strong> attribute value is the reference designator on the schematic such as Q1, U1, R1, etc. When you run PCB, this refdes will appear as the displayed element name when you select <strong>Reference Designator</strong> from the <strong>Screen→Displayed Element Name</strong> menu.
-</p>
-
-<p>
-The gschem <strong>value</strong> attribute value is the particular component value such as BC546, 7400, 1K, etc. When you run PCB, this <strong>value</strong> will appear as the displayed element name when you select <strong>Value</strong> from the <strong>Screen→Displayed Element Name</strong> menu.
-</p>
-
-</div>
-<!-- SECTION "Terminology" [948-3250] -->
-<h2><a name="setup" id="setup">Setup</a></h2>
-<div class="level2">
-
-<p>
-You should have a directory structure in mind for organizing your design projects. The install of gEDA and PCB gives you a set of default gschem symbols and default PCB elements, but you can also provide for creating your own custom libraries of gschem symbols and PCB elements.
-</p>
-<ul>
-<li class="level1"><div class="li"> Somewhere, probably under your home directory, create a directory structure for your projects. Use directory names you like, but this tutorial will reference the directory name structure I use:</div>
-</li>
-</ul>
-<pre class="code">gaf/
-gaf/gschem-sym/ Where I put the custom gschem symbols I create.
-gaf/gschem-sym/transistors/ You can organize your custom symbols into subdirectories.
-gaf/pcb-elements/ Where I put the custom PCB file elements I create.
-These can also be organized into subdirectories.
-gaf/myproject1/ And finally, separate directories for each
-gaf/myproject2/ design project.
-...</pre>
-
-<p>
- With this organization, any custom gschem symbols and PCB elements you make can be common to all of your projects and this is good enough to get you started. However, Iâ??ll mention other possibilities which will be revealed below: There can be project specific PCB <strong>file element</strong> subdirectories or <strong>m4 element</strong> files. Or, CAD administrators can set up site wide custom PCB <strong>file element</strong> directories and <strong>m4 element</strong> files.
-</p>
-<ul>
-<li class="level1"><div class="li"> <strong>gEDA setup (for new versions released >= 2005): </strong> the gschem, gnetlist, and other programs you may use such as gattrib, etc, all need to be able to find any custom symbols you will make, so you need to make your custom gschem symbol directories known to these programs in a gEDA gafrc file by adding <strong>component-library</strong> lines to either a user <strong>${HOME}/gafrc</strong> file or a project specific <strong>gafrc</strong> file in the project directory. There is also a system wide <strong>${GEDADATA}/system-gafrc</strong> file administrators can set up. The <strong>HOME</strong> and <strong>GEDADATA</strong> environment variables must be respectively set for those <strong>gafrc</strong> files to be found. For our directory structure setup above, we could add these lines to <strong>${HOME}/gafrc</strong> (plus lines for each additional <strong>gschem-sym </strong> subdirectory you want):</div>
-</li>
-</ul>
-<pre class="code">(component-library "${HOME}/gaf/gschem-sym")
-(component-library "${HOME}/gaf/gschem-sym/transistors")</pre>
-
-<p>
-or, in each project directory there could be a <strong>gafrc</strong> file with the lines:
-</p>
-<pre class="code">(component-library "../gaf/gschem-sym")
-(component-library "../gaf/gschem-sym/transistors")</pre>
-<ul>
-<li class="level1"><div class="li"> <strong>gEDA setup (for old versions released >= 2004): </strong> The <strong>gafrc</strong> file is not supported. Well, the feature was actually introduced mid 2004, but to get the full functionality described here (relative paths) you really need a 2005 gEDA. Anyway, when using an older gEDA it is necessary to duplicate the <strong>component-library</strong> setup lines in multiple rc files that apply to the various gEDA programs: </div>
-<ul>
-<li class="level2"><div class="li"> <strong>gschem program setup: </strong> create the file <strong>~/.gEDA/gschemrc</strong> with this content:</div>
-</li>
-</ul>
-</li>
-</ul>
-<pre class="code">(component-library "${HOME}/gaf/gschem-sym")
-(component-library "${HOME}/gaf/gschem-sym/transistors")</pre>
-<ul>
-<li class="level1"><div class="li"> <strong>gnetlist program setup: </strong> gnetlist will also need to find these symbols so duplicate those lines into <strong>~/.gEDA/gnetlistrc</strong>.</div>
-</li>
-</ul>
-<ul>
-<li class="level1"><div class="li"> If you want a more detailed customization of gschem and gnetlist, you can override other initializations that are setup in the global rc files. In Debian, look at rc files in <strong>/etc/gEDA/</strong> for settings you can make. For example, I like the light gschem background, so I also put in my <strong>~/.gEDA/gschemrc</strong> the line:</div>
-</li>
-</ul>
-<pre class="code">(load (string-append gedadatarc "/gschem-lightbg")) ; light background</pre>
-<ul>
-<li class="level1"><div class="li"> <strong>PCB setup: </strong> A PCB distribution usually is set up so that PCB will automatically look in a <strong>packages</strong> subdirectory of the working directory. So, to make PCB find all the custom elements I put in <strong>gaf/pcb-elements</strong> I make a link in each of my project directories. Note that this link is actually not required when using gsch2pcb because, as described below, you may alternatively specify the <strong>pcb-elements</strong> directory in a <strong>project</strong> file. But if you do want to make the link, in directory <strong>gaf/myproject1</strong> enter the command:</div>
-</li>
-</ul>
-<pre class="code">ln -s ../pcb-elements packages</pre>
-<ul>
-<li class="level1"><div class="li"> <strong> gsch2pcb setup: </strong> In each of your project directories, create a gsch2pcb project file which can be named anything that does not end in <em>.sch</em>. A poject file will be created in the example below.</div>
-</li>
-</ul>
-
-<p>
- This is all the setup you need beyond the initial install of the gschem, gsch2pcb, and PCB packages.
-</p>
-
-</div>
-<!-- SECTION "Setup" [3251-7817] -->
-<h2><a name="simple_example" id="simple_example">Simple Example</a></h2>
-<div class="level2">
-
-<p>
-Letâ??s generate a trivial design from schematics to PCB layout almost as quickly as possible and then we can use it as a base for doing some more advanced stuff. Iâ??ll complicate it just a bit by making it a two schematic design.
-</p>
-
-<p>
- Assuming you setup the directory structure described above, go to the <strong>gaf/myproject1</strong> directory and create a file named <strong>project</strong> with this content:
-</p>
-<pre class="code">schematics one.sch two.sch
-output-name board
-</pre>
-
-</div>
-<!-- SECTION "Simple Example" [7818-8290] -->
-<h3><a name="create_schematicone.sch" id="create_schematicone.sch">Create schematic: one.sch</a></h3>
-<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>.
-</p>
-
-<p>
-<a href="_detail/geda_one-sch-1.html" class="media" title="geda:one-sch-1.png"><img src="_media/geda_one-sch-1.png" class="medialeft" title="one.sch" alt="one.sch" /></a> Run <strong>gschem one.sch</strong> and create this schematic (the second opamp is redundant, but this is just a tutorial):
-</p>
-<ul>
-<li class="level1"><div class="li"> Add components:</div>
-<ul>
-<li class="level2"><div class="li"> From the <strong>analog</strong> library three <strong>resistor-1.sym</strong> and two <strong>dual-opamp-1.sym</strong>.</div>
-</li>
-<li class="level2"><div class="li"> From the <strong>io</strong> library one <strong>output-2.sym</strong>.</div>
-</li>
-<li class="level2"><div class="li"> From the <strong>power</strong> library one <strong>gnd-1.sym</strong>, two <strong>vcc-1.sym</strong> and two <strong>vee-1.sym</strong></div>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"> Move components with the middle mouse button and rotate selected components by hitting keys <strong>er</strong> until everything is placed nicely. Rotate the bottom opamp and mirror it with the <strong>ei</strong> keys.</div>
-</li>
-<li class="level1"><div class="li"> Use the <strong>n</strong> key and the mouse to draw net connections.</div>
-</li>
-</ul>
-
-<p>
- The large frame of the titleblock is a component too. It has been locked for convienience to prevent the mouse from catching it all the time. To unlock it, select it by dragging with left mouse button held down and press [e - shift-L]. You can find title blocks with different sizes in the default library. Remember, to lock the new title block with [el] while the tiotle block is selected.
-</p>
-
-</div>
-<!-- SECTION "Create schematic: one.sch" [8291-9493] -->
-<h3><a name="edit_the_attributes_of_the_components_on_the_schematic" id="edit_the_attributes_of_the_components_on_the_schematic">Edit the attributes of the components on the schematic.</a></h3>
-<div class="level3">
-
-<p>
-<a href="_detail/geda_one-sch-2.html" class="media" title="geda:one-sch-2.png"><img src="_media/geda_one-sch-2.png" class="mediaright" title="one.sch" alt="one.sch" /></a> For each component, select it and bring up its attributes window by hitting keys <strong>ee</strong>. Do not edit the <strong>refdes</strong> attribute here, but do make these edits:
-</p>
-<ul>
-<li class="level1"><div class="li"> For resistors and the opamps, add visible <strong>value</strong> attributes and assign appropriate values to them (10K, TL072). Move these newly visible attributes to nice locations with the middle mouse button. Zoom in and repeat clicking the middle mouse button if it is difficult to select them.</div>
-</li>
-<li class="level1"><div class="li"> For the resistors, add a <strong>footprint</strong> attribute and give it the value <strong>R025</strong> which is the PCB <em>m4 element</em> for a 1/4 watt resistor. Make this attribute invisible.</div>
-</li>
-<li class="level1"><div class="li"> For the opamps, edit the already existing <strong>footprint</strong> attribute to be <strong>DIL 8 300</strong>. Yes, include those spaces because <strong>DIL</strong> is a <strong>m4 element</strong> that takes two args. Weâ??re telling it to make a dual in line package with 8 pins in a 300 mil package. Edit the <strong>slot</strong> attribute of the second opamp to be <strong>2</strong>. Its I/O pin numbers should change from (1,2,3) to (5,6,7).</div>
-</li>
-<li class="level1"><div class="li"> For the output module port, edit its <strong>net</strong> attribute to be <strong>vmixer:1</strong> and make it invisible. Edit its <strong>value</strong> attribute to be <strong>Vmixer</strong>.</div>
-</li>
-</ul>
-
-<p>
- It may have occurred to you that this editing will be painful for a schematic with a large number of components that donâ??t have reasonable initial attribute values. At least for the footprints, there are a couple of things that could help. You can create your own library symbols having an initial <strong>footprint</strong> (and even <strong>value</strong>) attribute default that covers most of your uses. Or, when you add your first component, edit it to have a good footprint default and then copy it (select it and hit the <strong>ec</strong> keys) for all remaining components instead of adding them from the library.<br/>
-
-</p>
-
-<p>
-Anyway, weâ??re done for now with <strong>one.sch</strong>, so save it with the menu <strong>File→Save Page</strong> and quit gschem.
-</p>
-
-</div>
-<!-- SECTION "Edit the attributes of the components on the schematic." [9494-11442] -->
-<h3><a name="create_schematictwo.sch" id="create_schematictwo.sch">Create schematic: two.sch</a></h3>
-<div class="level3">
-
-<p>
-This will be really trivial and stupid since weâ??re doing it only to demonstrate multiple schematic capability. <a href="_detail/geda_two-sch-1.html" class="media" title="geda:two-sch-1.png"><img src="_media/geda_two-sch-1.png" class="medialeft" title="two.sch" alt="two.sch" /></a> Run <strong>gschem two.sch:</strong>
-</p>
-<ul>
-<li class="level1"><div class="li"> Add component <strong>title-B.sym</strong> as you did in one.sch.</div>
-</li>
-<li class="level1"><div class="li"> Add components:</div>
-<ul>
-<li class="level2"><div class="li"> From the <strong>io</strong> library one <strong>input-2.sym</strong>.</div>
-</li>
-<li class="level2"><div class="li"> From the <strong>analog</strong> library one <strong>resistor-1.sym</strong>.</div>
-</li>
-<li class="level2"><div class="li"> From the <strong>transistor</strong> library one <strong>2N3904-1.sym</strong>.</div>
-</li>
-<li class="level2"><div class="li"> From the <strong>power</strong> library one <strong>gnd-1.sym</strong>, one <strong>vcc-1.sym</strong> and one <strong>vee-1.sym</strong>.</div>
-</li>
-<li class="level2"><div class="li"> From the <strong>connector</strong> library one <strong>BNC-1.sym</strong>.</div>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"> Move components and draw nets as before.</div>
-</li>
-<li class="level1"><div class="li"> Edit component attributes:</div>
-<ul>
-<li class="level2"><div class="li"> Input module port: edit <strong>net</strong> attribute to be invisible and have value <strong>vmixer:1</strong> so this net will be connected to the <strong>vmixer</strong> in one.sch. Make the <strong>value</strong> attribute be <strong>Vmixer</strong>.</div>
-</li>
-<li class="level2"><div class="li"> Resistor: give it invisible <strong>footprint</strong> attribute <strong>R025</strong> and a visible <strong>value</strong> attribute 10K.</div>
-</li>
-<li class="level2"><div class="li"> Transistor: add <strong>value</strong> attribute <strong>2N3904</strong> and invisible <strong>footprint</strong> attribute <strong>TO92</strong>.</div>
-</li>
-<li class="level2"><div class="li"> BNC connector: add invisible <strong>footprint</strong> attribute <strong>CONNECTOR 2 1</strong>. which is a <strong>m4 element</strong> that takes arguments and weâ??re telling it to make a connector with 2 rows and 1 column. We put a BNC connector on the schematic, but Iâ??m pretending weâ??ll just jumper wires from this pc board header to a panel mounted connector.</div>
-</li>
-</ul>
-</li>
-</ul>
-
-<p>
- Unfortunately, the 2N3904 symbol we added has the text â??2N3904â?? as an integral part of its symbol. So when we add the <strong>value</strong> attribute (which we want so the PCB layout will show appropriate values), there are two â??2N3904â?? designations visible on our schematic unless we would make the <strong>value</strong> attribute invisible. This is not good and for this example we have to live with it, but note that in most cases itâ??s not a good idea to hardwire information into symbols like this. Also the default <strong>device</strong> attribute is wrong and should be <strong>NPN_TRANSISTOR</strong> but it wonâ??t affect this tutorial. This is just to inform you that currently there are some symbols in gschem that carry over outdated attribute usage from older versions of gschem. If you get into running spice on schematics, then your symbols will need to have proper <strong>device</strong> attributes.
-</p>
-
-<p>
-Now we are done with the schematics except for assigning <strong>refdes</strong> attributes and we can use the command <strong>refdes_renum</strong> to do this for both schematics at once. So, save <strong>two.sch</strong>, quit gschem and run:
-</p>
-<pre class="code">$ refdes_renum --pgskip one.sch two.sch
-</pre>
-
-<p>
- Run gschem on the schematics again to see how the components have been given a <strong>refdes</strong> attribute. The <em>–pgksip</em> option makes numbering begin at 101 for one.sch and at 201 for two.sch. But you should know that running <strong>refdes_renum</strong> is really only useful for an initial numbering. If you later edit your schematics and add or delete components, there is no guarantee when rerunning <strong>refdes_renum</strong> that components will keep an existing <strong>refdes</strong> value. If in the meantime youâ??ve generated a pc board using gsch2pcb, this reference designator number mixup will put your schematics out of sync with your PCB layout. So, after you initially run <strong>refdes_renum</strong> and start a PCB layout, to be safe you will need to manually add (unique) <strong>refdes</strong> attributes for any schematic components you might add. Also note that <strong>refdes_renum</strong> may number your resistors differently than it did for my examples here depending on the order in which resistors were added. Keep that in mind when comparing your eventual PCB layout to what you see in the images below.
-</p>
-
-</div>
-<!-- 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">
-
-<p>
-We have to fix one thing in <strong>one.sch</strong> before we can proceed. Run <strong>gschem one.sch</strong> and notice that <strong>refdes_renum</strong> has given our opamps <strong>refdes</strong> values of <strong>U101</strong> and <strong>U102</strong> and did not know we really want to be using two opamps out of a single TL072 package. Thatâ??s why we edited the <strong>slot</strong> attribute of the second opamp. We have to go back and fix this by editing the <strong>refdes</strong> attribute of the second opamp to be <strong>U101</strong> so both opamps will have the same <strong>refdes</strong> and there will be only one TL072 package on our pc board.
-</p>
-
-<p>
- Now, since we have already set up a gsch2pcb <strong>project</strong> file, all we need to do to create an initial set of PCB files is to run gsch2pcb:
-</p>
-<pre class="code">~/gaf/myproject1$ gsch2pcb project
-0 file elements and 7 m4 elements added to board.pcb.
-</pre>
-
-<p>
- Since the project file specifed <strong>board</strong> as the output-name, the PCB files created are named <strong>board.pcb</strong> and <strong>board.net</strong>.
-</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 <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" [15047-16645] -->
-<h3><a name="layout_pcb_files" id="layout_pcb_files">Layout PCB Files</a></h3>
-<div class="level3">
-
-</div>
-
-<h4><a name="set_the_defaults" id="set_the_defaults">Set the defaults</a></h4>
-<div class="level4">
-
-<p>
-<a href="_detail/geda_board-1.html" class="media" title="geda:board-1.png"><img src="_media/geda_board-1.png" class="medialeft" title="pcb, step 1" alt="pcb, step 1" /></a>Run <strong>pcb board.pcb</strong>. Youâ??ll see grouped into a big pile the PCB elements for all the schematic component footprints. This is ok, we will clean up this mess later.
-</p>
-
-<p>
-When you run PCB on a <strong>.pcb</strong> file for the first time, you should set up various initial values. I usually set a 25 mil grid spacing with <strong>Screen→Grid Setting→25 mil</strong> for the bulk of my layout work and then change grid spacing to smaller values as needed for tight layout situations. Note that if you have enabled millimeter units with <strong>Screen→Enable millimeter grid units</strong> you will see a set of millimeter size options to select from instead of mils in the <strong>Screen→Grid Setting</strong> menu. You may change between millimeter and mil grid units at any time when doing a layout.
-</p>
-
-<p>
-You should also set the default line and via sizes you want for the Signal, Power, Fat, and Skinny drawing route styles. Simply select one of these four route styles at the lower left of the PCB window and then press the <strong>Route Style</strong> button to edit the sizes. You can set your board size now or wait until later while working on the layout. To change the board size, bring up the <strong>File→Preferences</strong> window and select the <strong>Sizes</strong> page. Other design rule checking and increment sizes can also be edited in the Preferences window. You should review PCB documentation for definitions of these items. And you may find it useful to select <strong>Screen→Enable visible grid</strong>.
-</p>
-
-</div>
-
-<h4><a name="disperse_the_components" id="disperse_the_components">Disperse the Components</a></h4>
-<div class="level4">
-
-<p>
-<a href="_detail/geda_board-2.html" class="media" title="geda:board-2.png"><img src="_media/geda_board-2.png" class="mediaright" title="step 2" alt="step 2" /></a> Use the middle mouse button to grab and move elements one at a time until you have separated all the elements.
-</p>
-
-<p>
-Or, you can let PCB spread out the elements with <strong>Select→Disperse all elements</strong> before you fine tune the positions with the middle mouse button.
-</p>
-
-</div>
-
-<h4><a name="load_the_netlist" id="load_the_netlist">Load the Netlist</a></h4>
-<div class="level4">
-
-<p>
-<a href="_detail/geda_board-3.html" class="media" title="geda:board-3.png"><img src="_media/geda_board-3.png" class="medialeft" title="Step 3" alt="Step 3" /></a>
-</p>
-<ul>
-<li class="level1"><div class="li"> Go to <strong>File→load netlist file</strong> and select <strong>board.net</strong> </div>
-</li>
-<li class="level1"><div class="li"> Do <strong>Connects→optimize rats-nest</strong>. Now, the pins and pads of components should be connected with straight lines according to the schematic. These are â??ratsâ??.</div>
-</li>
-</ul>
-
-<p>
- To minimize confusion, PCB tries to draw the rats of complex connections such that the sum of all rats is as short as possible. Try to drag an element to the other side of the working area. The rats will follow like a rubber band, but the end of the rats will not jump to a different node, although the resulting length might be shorter. The action <strong>optimize rats-nest</strong> rats will make the rats jump to this â??betterâ?? geometry. This action can be applied conviniently anytime with a troke of the the key <strong>o</strong>.
-</p>
-
-</div>
-
-<h4><a name="place_the_components" id="place_the_components">Place the Components</a></h4>
-<div class="level4">
-
-<p>
-<a href="_detail/geda_board-4.html" class="media" title="geda:board-4.png"><img src="_media/geda_board-4.png" class="mediaright" title="Step 4" alt="Step 4" /></a>You will have to replace the rats with traces that can be etched in copper. After â??Disperse all elementsâ?? the rats are usually in a random mess with lots of crossings. You should move and rotate the components around and try to disentangle the rats as much as possible. The key to a well routed pcb is proper placement of the components. Although PCB tries to clean up the rats lines while you move the components around, it is good practice to occasionly initiate rats optimization with the <strong>o</strong>-key.
-</p>
-
-<p>
-Select the <strong>ROT</strong> tool (<strong>F-9</strong>) to move elements with the middle mouse button and rotate them with the left mouse button. The right mouse button will move the viewport to the canvas when zoomed in. Zoom in and out with the mouse wheel or alternatively with <strong>z</strong> and <strong>Shift z</strong>. Hit the <strong>f</strong> key while the mouse hovers over a pin to highlight the particular that touches this pin to help visualize the routes. Use <strong>Shift f</strong> to unhighlight. You can undo changes anytime with the <strong>u</strong> key.
-</p>
-
-<p>
-Note: you can use the PCB auto placement feature instead of manually placing (or dispersing with the <strong>Select→Disperse …</strong> commands) the components as described above. To do this, you would load the netlist, select the components you want to be autoplaced (if this is the first PCB run, just <b>Select→Select all objects</b>) then do <strong>Select→Auto place selected elements</strong>. Then you can again manually tune the PCB generated placements. The auto place function should place elements more intelligently than the disperse function, but it is also much slower as layouts get larger.
-</p>
-
-</div>
-
-<h4><a name="replace_rats_nests_with_routes" id="replace_rats_nests_with_routes">Replace rats nests with routes</a></h4>
-<div class="level4">
-
-<p>
-<a href="_detail/geda_board-5.html" class="media" title="geda:board-5.png"><img src="_media/geda_board-5.png" class="medialeft" title="Step 5" alt="Step 5" /></a> At this point you can start routing traces between pins connected by rats nest lines. On the left PCB toolbar, select the <strong>LINE</strong> tool, select the layer you want to draw on (solder, component, etc), and start drawing lines by selecting endpoints with the left mouse button. Again, it can help to use the <strong>f</strong> key to highlight routes that need to be connected. If you want to stop the current trace so you can start drawing a new trace somewhere else, finish the current trace with a middle mouse click. Or you can play with auto routing here.
-</p>
-
-<p>
-A very useful operation with the <strong>SEL</strong> tool is to select multiple objects and then cut or copy them to a buffer with the menu <strong>Buffer→Cut selection to buffer</strong> (or copy). You can immediately paste the buffer contents or abort the current paste by selecting another tool. The buffer contents can be pasted any time later with <strong>Buffer→Paste buffer to layout</strong>. With this you can move layout areas around or step and repeat common trace patterns. To select multiple objects with the <strong>SEL</strong> tool, click and drag to select rectangular regions, and SHIFT click to toggle additional selections to the currently selected set.
-</p>
-
-<p>
-When youâ??ve finished routing the traces (PCB will congratulate you if all traces are routed when you optimze the rats nest) the board can look something like this. For this view Iâ??ve selected <strong>Screen→Displayed element name→Value</strong>.
-</p>
-
-<p>
-You will want more information on using PCB and there is a set of html docs in the PCB source tarball. I donâ??t know of a link to put here, but you can get the latest tarball from the <a href="http://sourceforge.net/projects/pcb/"; class="urlextern" title="http://sourceforge.net/projects/pcb/"; rel="nofollow">PCB development </a> site. Or the docs may be installed somewhere on your system. The Debian package has them installed in <strong>/usr/share/doc/pcb/html/</strong>. PCB also has some convenient â??liveâ?? documentation that can help you become familiar with keyboard shortcuts or keyboard commands. Bring up the keyboard shortcuts window with the menu <strong>Window→Key Reference</strong> and youâ??ll probably find just reading through the shortcuts available will teach you a lot about what you can do with PCB. If you have selected in the <strong>File→Preferences</strong> window the <em>Use separate window for command entry</em> option, then when you bring up the Command window with <strong>Window→Command Entry</strong> (or the ':' key), you will see a <strong>Command Reference</strong> expander arrow. Click on the arrow and a command reference will be shown which lists some commands you can type in that may not be available from the menus or a keyboard shortcut.
-</p>
-
-<p>
- For example, say you have in the <strong>Preferences→Increments</strong> page configured a size increment of 5 mils. With this you can select some lines and then increase their width by 5 mils by selecting from the menu <strong>Select→Change size of selected objects→Increment lines by 5 mils.</strong> However, suppose you want to be changing widths by random values and itâ??s inconvenient to be changing the Preferences each time. For this, you can select some lines, bring up the command window (hit â??<strong>:</strong>â??) and type in the command:
-</p>
-<pre class="code"> changesize(selectedlines, +3, mils)
-</pre>
-
-<p>
- and the selected lines will increase by 3 mils. This command is now in a history list which you can recall and quickly edit in the command window to change sizes by other values.
-</p>
-
-</div>
-
-<h4><a name="looking_at_the_other_side_of_the_board" id="looking_at_the_other_side_of_the_board">Looking at the other side of the board</a></h4>
-<div class="level4">
-
-<p>
-In some layouts it is important to put components on either side of the board, although not for the preceeding example. In such a case the â??tabâ?? key can be used to flip the board over and view it from the back while the â??bâ?? key can be used to put a selected component on the other side of the board. On dual sided boards it is also important to note what side a particular layer of traces is on. This can be seen, and set, in the File→Preferences→Layers→Groups dialog. Layers on the â??componentâ?? side will be on the top of the board and layers on the â??solderâ?? side will be on the bottom. In this dialog you should make sure that all layers which are to be fabricated in the same step (i.e. etched with photo-lithography) are grouped together.
-</p>
-
-</div>
-<!-- SECTION "Layout PCB Files" [16646-25079] -->
-<h2><a name="modifying_schematics" id="modifying_schematics">Modifying Schematics</a></h2>
-<div class="level2">
-
-<p>
-The process of transfering schematic modifications to your PCB layout is made very simple by using gsch2pcb. After the first <strong>board.pcb</strong> was created when you initially ran gsch2pcb, each time you run gschem on your schematics and make changes, run <strong>gsch2pcb project</strong>. Then run <strong>pcb board.pcb</strong> and do whatever is necessary based on the work gsch2pcb has done. Each time gsch2pcb is run, this will happen:
-</p>
-<ul>
-<li class="level1"><div class="li"> gsch2pcb always generates a new <strong>board.net</strong>. If the net was changed, load the new netlist file when you run pcb. *</div>
-</li>
-</ul>
-
-<p>
- If you added components (with a footprint attribute) to a schematic gsch2pcb will generate a <strong>board.new.pcb</strong> containing all the new PCB elements corresponding to the footprints. You then run <strong>pcb board.pcb</strong> and load the <strong>board.new.pcb</strong> with new elements into the existing layout with <strong>File→load layout data to paste-buffer</strong>. Place the new elements, load the new netlist, and route new traces.<br/>
-
-</p>
-<ul>
-<li class="level1"><div class="li"> If you deleted components from a schematic, gsch2pcb will delete the corresponding PCB elements from <strong>board.pcb</strong>. You only need to run <strong>pcb board.pcb</strong> and clean up dangling traces from around the deleted elements.</div>
-</li>
-</ul>
-<ul>
-<li class="level1"><div class="li"> If you change an existing componentâ??s <strong>footprint</strong>, gsch2pcb will delete the corresponding old element from <strong>board.pcb</strong> and add the new element to <strong>board.new.pcb</strong>.</div>
-</li>
-</ul>
-<ul>
-<li class="level1"><div class="li"> If you changed schematic component <strong>value</strong> attributes, the value changes will be forward annotated to <strong>board.pcb</strong> in place.</div>
-</li>
-</ul>
-
-<p>
-So by using gsch2pcb, all PCB element changes are driven by the schematics and you should never need to manually add or delete elements for schematic components.
-</p>
-
-<p>
- However, you will need to manually add PCB elements that are not part of the schematics such as pc board mounting holes. For these manually added PCB elements, make sure you never give them a <strong>name on PCB</strong> name because that is reserved for schematic component <strong>refdes</strong> attributes and gsch2pcb will want to delete elements which have a non-empty <strong>name on PCB</strong> and donâ??t match any schematic component <strong>refdes</strong>.
-</p>
-
-<p>
- Now, so far weâ??ve only used <strong>m4 elements</strong> in our layout so letâ??s modify a schematic to use a <strong>file element</strong>. But first, it would help to know about the default elements PCB provides. Depending on the location of your PCB install there will be a directory <strong>/usr/local/share/pcb/newlib, /usr/share/pcb/newlib</strong>, or possibly something else (depending on the <em>prefix</em> specified when PCB was installed). PCB versions before 20031113 used <strong>pcb_lib</strong> instead of <strong>newlib</strong> in the locations <strong>/usr/local/pcb_lib, </strong> or <strong>/usr/lib/pcb_lib,</strong>. Once you find your <strong>newlib</strong> directory, look at the file names in each subdirectory. Each file name is a name which may be used as a <strong>footprint</strong> attribute for a schematic component. For example, there is the file <strong>xxx/newlib/2_pin_thru-hole_packages/0.125W_Carbon_Resistor</strong> so if we wanted 1/8 watt resistors on our layout, we could use <strong>0.125W_Carbon_Resistor</strong> as the resistor <strong>footprint</strong> attribute instead of <strong>R025</strong>. Try changing, say resistor R101 to use <strong>0.125W_Carbon_Resistor</strong> in <strong>one.sch</strong> and then run <strong>gsch2pcb project</strong>. If gsch2pcb does not find this element, then you need to add your <strong>newlib</strong> directory to your <strong>project</strong> file with a line like:
-</p>
-<pre class="code">elements-dir /usr/lib/newlib
-</pre>
-
-<p>
- If gsch2pcb does find it, you will get:
-</p>
-<pre class="code">~/gaf/myproject1$ gsch2pcb project
-board.pcb is backed up as board.pcb.bak1.
-1 elements deleted from board.pcb.
-1 file elements and 0 m4 elements added to board.new.pcb.
-</pre>
-
-<p>
- Now you need to run <strong>pcb board.pcb</strong>. You will see that the element for resistor R101 is gone and that you will get the new element by loading <strong>board.new.pcb</strong> with <strong>File→load layout data to paste-buffer</strong>.
-</p>
-
-</div>
-<!-- SECTION "Modifying Schematics" [25080-28885] -->
-<h2><a name="custom_gschem_symbols" id="custom_gschem_symbols">Custom gschem Symbols</a></h2>
-<div class="level2">
-
-<p>
-A common way to generate a custom symbol is to start with an existing symbol and modify it. One thing I donâ??t like about the <strong>dual-opamp-1.sym</strong> we used is that the power pins are repeated on each symbol. While some will prefer this, I think it makes a page full of opamps look a little cluttered and it presents a good opportunity to learn about <strong>net</strong> attributes in this tutorial. Itâ??s possible with gschem for symbols to have <strong>net</strong> attributes which can assign pins to a particular net. Instead of hooking up each opamp pin 8 to Vcc and pin 4 to to Vee on the schematic, we can have that happen automatically and eliminate the pins on the schematic. To do this, just copy the original symbol to our custom gschem symbol directory, giving it a new name, and edit it. Do the steps described below. (Your gEDA symbol install directory may be something different like <strong>/usr/local/share/gEDA/sym/</strong>):
-</p>
-
-</div>
-
-<h5><a name="make_attributes_visible" id="make_attributes_visible">Make Attributes Visible</a></h5>
-<div class="level5">
-
-<p>
-<a href="_detail/geda_gschem-sym-1.html" class="media" title="geda:gschem-sym-1.png"><img src="_media/geda_gschem-sym-1.png" class="medialeft" title="Step 1" alt="Step 1" /></a>
-</p>
-<pre class="code">cd /usr/share/gEDA/sym/analog/
-cp dual-opamp-1.sym ~/gaf/gschem-sym/opamp-dual.sym
-cd ~/gaf/gschem-sym
-gschem opamp-dual.sym
-</pre>
-<ul>
-<li class="level1"><div class="li"> Hit keys <strong>en</strong> to make attributes visible.</div>
-</li>
-<li class="level1"><div class="li"> Hit keys <strong>ve</strong> to view extents.</div>
-</li>
-<li class="level1"><div class="li"> Left mouse click on pin 8 to select it.</div>
-</li>
-</ul>
-
-</div>
-
-<h5><a name="remove_the_visible_supply_pins" id="remove_the_visible_supply_pins">Remove the Visible Supply Pins</a></h5>
-<div class="level5">
-
-<p>
-<a href="_detail/geda_gschem-sym-2.html" class="media" title="geda:gschem-sym-2.png"><img src="_media/geda_gschem-sym-2.png" class="medialeft" title="Step 2" alt="Step 2" /></a> * Hit <strong>Delete</strong> key to delete pin 8.
-</p>
-<ul>
-<li class="level1"><div class="li"> Similarly select and delete pin 4.</div>
-</li>
-<li class="level1"><div class="li"> Double click to select and edit the <strong>slotdef</strong> lines. Edit them by removing the pins 4 and 8.</div>
-</li>
-</ul>
-
-</div>
-
-<h5><a name="add_global_nets_to_in_numbers" id="add_global_nets_to_in_numbers">Add global Nets to in Numbers</a></h5>
-<div class="level5">
-
-<p>
-<a href="_detail/geda_gschem-sym-3.html" class="media" title="geda:gschem-sym-3.png"><img src="_media/geda_gschem-sym-3.png" class="medialeft" title="Step 3" alt="Step 3" /></a>From the menu <strong>Add→Attribute</strong>
-</p>
-<ul>
-<li class="level1"><div class="li"> Add a <strong>net</strong> attribute with value <strong>Vcc:8</strong> Select <strong>Show Name &amp; Value</strong> and make it invisible.</div>
-</li>
-<li class="level1"><div class="li"> Add a <strong>net</strong> attribute with value <strong>Vee:4</strong> Make it <strong>Show Name &amp; Value</strong> and invisible.</div>
-</li>
-<li class="level1"><div class="li"> Make the <strong>device</strong> attribute be just <strong>OPAMP</strong>.</div>
-</li>
-</ul>
-
-<p>
- Clean up by moving these new attributes as shown.
-</p>
-
-<p>
-Change the footprint default if you wish. When all the edits are done, itâ??s very important when editing symbols to do a <strong>Edit→Symbol Translate</strong> to zero before saving. Do that and then save the symbol with <strong>File→Save Page</strong> I made the <strong>footprint</strong> default be <strong>DIP8</strong> because I have that as a custom element.
-</p>
-
-</div>
-
-<h5><a name="run_gschem_with_the_new_symbol" id="run_gschem_with_the_new_symbol">Run gschem with the New Symbol</a></h5>
-<div class="level5">
-
-<p>
-<a href="_detail/geda_one-sch-3.html" class="media" title="geda:one-sch-3.png"><img src="_media/geda_one-sch-3.png" class="medialeft" title="one.sch" alt="one.sch" /></a> Run <strong>gschem one.sch</strong>. Select and delete with the <strong>Delete</strong> key both opamps. Also delete the <strong>Vcc</strong> and <strong>Vee</strong> symbols that were connected to them. Bring up the Add Components window and from the <strong>gschem-sym</strong> library which should now have your new custom symbol, place two of the <strong>opamp-dual.sym</strong> Move them to the right place on the schematic and donâ??t forget to mirror and rotate the bottom opamp as before. Edit the attributes of each opamp giving them the same attributes they had, that is make the <strong>footprint</strong> be <strong>DIL 8 300</strong>, add a <strong>value</strong> attribute of <strong>TL072</strong>, and make the <strong>refdes</strong> of both opamps be <strong>U101</strong>. Make the <strong>slot</strong> of the second opamp be <strong>2</strong>. If you donâ??t make the attributes the same as they were before, gsch2pcb will think it is a different component and delete the existing <strong>DIL</strong> package from the layout. If you did everything right, running gsch2pcb should give:
-</p>
-<pre class="code">~/gaf/myproject1$ gsch2pcb project
-Found a cpinlist head with a netname! [Vcc]
-Found a cpinlist head with a netname! [Vee]
-Found a cpinlist head with a netname! [Vcc]
-Found a cpinlist head with a netname! [Vee]
-Found a cpinlist head with a netname! [Vcc]
-Found a cpinlist head with a netname! [Vee]
-Found a cpinlist head with a netname! [Vcc]
-Found a cpinlist head with a netname! [Vee]
-No elements to add so not creating board.new.pcb
-</pre>
-
-<p>
- Where the gEDA gnetlist program seems a bit â??excitedâ?? about finding the new Vcc and Vee <strong>net</strong> attributes we just added, and a new netlist was generated. Now I think the schematic looks cleaner. And if you run <strong>pcb board.pcb</strong> and load the new netlist and then optimize the rats nest, PCB should tell you the board is complete which means connecting the opamp power pins via the <strong>net</strong> attribute has worked.
-</p>
-
-<p>
-For complete details on making symbols, read through the <a href="http://geda.seul.org/wiki/geda:scg"; 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" [28886-33139] -->
-<h2><a name="custom_file_elements" id="custom_file_elements">Custom file elements</a></h2>
-<div class="level2">
-
-<p>
-You can create custom <strong>file elements</strong> in the middle of running PCB on any layout or you can run PCB just for making the element. As a demonstration, lets make a custom element for a 1N4004 diode. There are axial packages provided by PCB, but we want to be sure the drill size will be right for this 1 amp diode with slightly fatter leads. It needs about a 42 mil (#58) drill.
-</p>
-
-<p>
- Run <strong>pcb</strong> and the first thing to do is select the <strong>Signal</strong> routing style and edit its sizes (press the <strong>Route Style</strong> button) Set the <strong>Via hole</strong> size to 42 and the <strong>via size</strong> to 70 or larger as you like. Select <strong>Screen→Grid setting→25 mil</strong> and <strong>Screen→Enable visible grid</strong>. Zoom in a couple of steps, then make the element: <a href="_detail/geda_pcb-el-1.html" class="media" title="geda:pcb-el-1.png"><img src="_media/geda_pcb-el-1.png" class="medialeft" title="Step 1" alt="Step 1" /></a>
-</p>
-<ul>
-<li class="level1"><div class="li"> Select the <strong>VIA</strong> tool and place two vias 400 milsapart.</div>
-</li>
-<li class="level1"><div class="li"> With the mouse on the left via, hit the <strong>n</strong> key and give the via the name <strong>1</strong>. Give the right via the name <strong>2</strong></div>
-</li>
-<li class="level1"><div class="li"> Pin 1 will be the cathode and this must agree with the pin numbers in your diode gschem symbol.</div>
-</li>
-</ul>
-
-<p>
- <a href="_detail/geda_pcb-el-2.html" class="media" title="geda:pcb-el-2.png"><img src="_media/geda_pcb-el-2.png" class="mediaright" title="Step 2" alt="Step 2" /></a>
-</p>
-<ul>
-<li class="level1"><div class="li"> Select the <strong>Silk</strong> layer and the <strong>LINE</strong> tool.</div>
-</li>
-<li class="level1"><div class="li"> Draw the component outline as shown with line width set to 10 mils and the grid setting set to 10 mils.</div>
-</li>
-<li class="level1"><div class="li"> Draw the left fat cathode indicator with three lines after setting the line width to 20 mils.</div>
-</li>
-<li class="level1"><div class="li"> Donâ??t let silk layer lines overlap solder pads. </div>
-</li>
-</ul>
-
-<p>
-Select the vias and the outline just drawn using the <strong>SEL</strong> tool and finish making the element:
-</p>
-<ul>
-<li class="level1"><div class="li"> <strong>Buffer→Cut selection to buffer</strong> and move the cursor to the center of the left via and click.</div>
-</li>
-<li class="level1"><div class="li"> <strong>Buffer→Convert buffer to element</strong></div>
-</li>
-<li class="level1"><div class="li"> <strong>Buffer→Save buffer elements to file</strong> and navigate to <strong>~/gaf/pcb-elements</strong> and save the element as <strong>D400-1A</strong> since itâ??s a package for a 1A diode with 400 mil spaced pins. Or give it any descriptive name you like.</div>
-</li>
-</ul>
-
-<p>
- <strong>Note:</strong> if you save the element with a name which is the same as a <strong>m4 element</strong>, gsch2pcb will preferentially use the m4 element unless you give gsch2pcb the –use-files (or -f) option. You may put <strong>use-files</strong> in a project file if you want to always give priority to using <strong>file elements</strong>. The m4 element names appear to use upper case, so you could also avoid the problem by using lower case in your file element names. Also, the only way I know to make the pin 1 of the symbol square is to edit the D400-1A file manually and change the square flag in the Pin â??1â?? line. For example, change the line:
-</p>
-<pre class="code"> Pin(0 0 70 20 70 42 "" "1" 0x00000001)
-to:
-Pin(0 0 70 20 70 42 "" "1" 0x00000101)
-</pre>
-
-<p>
- You can now use <strong>D400-1A</strong> in a gschem schematic symbol <strong>footprint</strong> attribute and gsch2pcb will find it provided you have made the <strong>packages</strong> link described in the <strong>Setup</strong> section. If you have not made that link, you can still tell gsch2pcb about the elements directory with a line in a project file:
-</p>
-<pre class="code">elements-dir ~/gaf/pcb-elements
-</pre>
-
-<p>
- Possibly youâ??ve noticed, but there are some things not right about the <strong>myproject1</strong> example. For one thing, silk layer lines are overlapping solder pads on some of the elements, and for another, the transistor is backwards on the layout! You otherwise shouldnâ??t have a problem like this when working with gschem and PCB, but transistor pin numbering can be confusing. If you will be using transistors in your designs, hereâ??s a description of my approach to making sure my gschem transistor symbol pin numbering is coordinated with PCB element pin numbers: <a href="geda_transistor_guide.html" class="wikilink1" title="geda:transistor_guide">transistor guide.</a>
-</p>
-
-<p>
- From the transistor guide, you can see that the problem here is that the <strong>TO92</strong> element has its pins numbered in the less common (3,2,1) configuration while the <strong>2N3904-1.sym</strong> is like a npn-ebc symbol which needs a (1,2,3) numbering. You can see the 2N3904 pin numbers in gschem by hitting the <strong>en</strong> keys (and donâ??t be confused by the <strong>pinseq</strong> attribute that nearly covers up the <strong>pinnumber</strong>). And in PCB, you can see the <strong>TO92</strong> pin numbers by hitting the <strong>d</strong> key with the mouse over the element. To be sure you are seeing pin numbers and not pin names, select <strong>Screen→pinout shows number</strong>.
-</p>
-
-<p>
- I have libraries with transistor symbols and elements that you might find useful, so as a convenience you can get your custom libraries initially populated by installing my <a href="http://www.geda.seul.org/docs/current/tutorials/gsch2pcb/gsch2pcb-libs-20040110.tar.gz"; class="urlextern" title="http://www.geda.seul.org/docs/current/tutorials/gsch2pcb/gsch2pcb-libs-20040110.tar.gz"; rel="nofollow"> gschem/PCB libraries </a>. Untar them under ~/gaf to mirror the setup of our example and there will also be a <strong>~/gaf/pcb-elements.Readme</strong> which documents the PCB elements. <i>Note: as of 1/10/2004 Iâ??ve corrected the tarball pcb elements to not overlap solder pads with silk layer lines.</i> If you untar them somewhere else, you will need to make sure that gschem knows about them with gschemrc/gnetlistrc <strong>component-library</strong> lines and that gsch2pcb can find them with <strong>elements-dir</strong> lines in a project file.
-</p>
-
-<p>
- If you install them, you can fix Q201 in <strong>two.sch</strong> by changing its footprint to <strong>TO-92</strong> which is my custom element with (1,2,3) pin numbering. Then run <strong>gsch2pcb project</strong> and then <strong>pcb board.pcb</strong> and load the new element for the transistor. In the next images, <strong>two.sch</strong> is showing the <strong>footprint</strong> attribute visible to emphasize it, and it also shows a new symbol for the 2N3904 which I created from my custom <strong>npn-ebc.sym</strong> as described in my transistor guide. In the updated board.pcb layout, if you compare the outline appearance of the transistor to the original layout you see that the orientation is now correct and that silk layer lines donâ??t overlap the solder pads. I also changed the <strong>footprint</strong> attribute for resistors R102 and R103 in <strong>one.sch</strong> to my custom 1/8 watt <strong>R0w8</strong> and 1/4 watt <strong>R0w4</strong> elements to illustrate the differences in style you can have with custom elements. You can also see the R101 style after its footprint was changed to <strong>0.125W_Carbon_Resistor</strong> as suggested above. As you evaluate the differences in these styles, Iâ??ll mention that for my custom elements I wanted to maximize room to display value and refdes text (the 0.125W… element body could be a little larger) and I wanted the solder pad diameter a little larger so it will be more forgiving of board fabrication technique. Also, the resistor pin spacing for my <strong>R0w4</strong> is slightly less than in <strong>R025</strong> to improve component density.
-</p>
-
-<p>
-<a href="_detail/geda_two-sch-2.html" class="media" title="geda:two-sch-2.png"><img src="_media/geda_two-sch-2.png" class="medialeft" title="two.sch" alt="two.sch" /></a> <a href="_detail/geda_board-6.html" class="media" title="geda:board-6.png"><img src="_media/geda_board-6.png" class="mediaright" title="pcb" alt="pcb" /></a>
-</p>
-
-</div>
-<!-- SECTION "Custom file elements" [33140-39601] -->
-<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>
-First, some words about how to find out about the default <strong>m4 elements</strong> available in PCB. I think there is some documention forthcoming in the PCB project, but at this point I donâ??t know of anything to refer you to and you canâ??t just look at filenames as you can for the <strong>file elements</strong>. Not only that, but many of these elements require arguments and you need to determine what they are. So for now all I can say is that the best way to find out whatâ??s available is to read the m4 element files and for this you need to know where the PCB m4 files install location is. As of PCB 20031113 this install directory will most likely be <strong>/usr/share/pcb/m4</strong> or <strong>/usr/local/share/pcb/m4</strong>, while on earlier PCB versions it could be <strong>/usr/X11R6/lib/X11/pcb/m4</strong> (run <em>gsch2pcb –help</em> or <em>gsch2pcb -v project</em> to see which of these directories gsch2pcb is using). But if your install is somewhere else you will have to track it down. By the way, if the m4 directory <em>is</em> somewhere different from the above three, then gsch2pcb wonâ??t be finding your <strong>m4 elements</strong> in the above examples and you will need to add the correct m4 directory to your <strong>project</strong> file with a line like:
-</p>
-<pre class="code">m4-pcbdir /path/to/pcb/m4
-</pre>
-
-<p>
- Just read the <strong>.inc</strong> files in the m4 install directory. For example, in the <strong>misc.inc</strong> file you will find the <strong>R025</strong> element weâ??ve used and it starts out with:
-</p>
-<pre class="code"># -------------------------------------------------------------------
-# the definition of a resistor (0.25W) package
-# $1: canonical name
-# $2: name on PCB
-# $3: value
-define(`PKG_R025',
-`Element(0x00 "$1" "$2" "$3" 120 30 0 100 0x00)
-(
-...
-</pre>
-
-<p>
- The information you can extract from this is that a m4 <strong>PKG_</strong> macro named <strong>R025</strong> is being defined and it takes 3 arguments. Now, all PCB <strong>m4 element</strong> macros take at least three arguments and these are automatically filled in by gsch2pcb with the gschem attributes <strong>footprint</strong> for <strong>canonical name</strong>, <strong>refdes</strong> for <strong>name on PCB</strong>, and <strong>value</strong> for <strong>value</strong>. The â??canonical nameâ?? used in these m4 files is just an older way of referring to the current PCB usage of <strong>description</strong> as mentioned above in the <strong>Terminology</strong> section. Since these args are automatically filled in, you donâ??t need to specify any additional args to <strong>R025</strong> when you use it as a gschem <strong>footprint</strong>. But now look at the very next m4 element define in <strong>misc.inc</strong>:
-</p>
-<pre class="code"># -------------------------------------------------------------------
-# the definition of a SIL package without a common pin
-# $1: canonical name
-# $2: name on PCB
-# $3: value
-# $4: number of pins
-define(`PKG_SIL',
-`define(`MAXY', `eval(`$4' * 100 -50)')
-Element(0x00 "$1" "$2" "$3" 160 10 3 100 0x00)
-(
-...
-</pre>
-
-<p>
- From this you can determine there is a <strong>SIL</strong> package you can use as a <strong>footprint</strong>. It has 4 arguments, but only the first three are handled automatically so there is one argument you must give when using it. You get a flash of insight and realize this is a â??Single In Lineâ?? package! So, instead of the <strong>CONNECTOR 2 1</strong> element specifying 1 column we used in our example above, you might think we could have used <strong>SIL 2</strong>. But you would be wrong! Because if you read the macro body you will see that if the argument is <strong>2</strong> the second forloop canâ??t handle it. In fact, it will only work for arguments >= 4. If you ever run gsch2pcb and it appears stuck in an infinite loop, a m4 macro argument problem is likely the cause. As you look through <strong>misc.inc</strong> hereâ??s a summary of what you will find as possible elements you can use:
-</p>
-<pre class="code">Package Args you need to supply
-SD 1 number of pins of a ZIP package
-MULTIWATT15 0
-R025 0
-SIL 1 number of pins (we know now must be >= 4)
-CSIL 1 number of pins
-QFP132 0
-LED 1 diameter of LED
-DIODE_LAY 1 pin separation
-AXIAL_LAY 1 pin separation
-CRYSTAL 1 package width
-OSC 0
-ISA8 0
-OVEN_OSC 0
-RADIAL_CAN 1
-SMD_BASE 2 length and width of surface mount device
-SMD_CHIP 1 package length
-</pre>
-
-<p>
- And so on for the other <strong>.inc</strong> files…
-</p>
-
-<p>
- The reality is that the m4 setup is less user friendly (you canâ??t create the elements graphically) and more complicated (you need to understand m4 macros) than the simple <strong>file element</strong> approach. So for most of your custom elements I suggest you are better off staying with <strong>file elements</strong>. However, with the m4 macro method a single element definition that takes arguments gives you a programmable element which can be very useful for large pin count packages. It is particularly nice for IC packages with variable widths and number of pins, so a good example of using a custom <strong>m4 element</strong> would be to copy and modify to our taste the existing m4 macro for IC packages (the <strong>DIL</strong> macro) into a m4 file gsch2pcb will search. The destination m4 file can be any of these:
-</p>
-<ul>
-<li class="level1"><div class="li"> <strong>pcb.inc</strong> in our <strong>myproject1</strong> directory and the custom element will be local to this project.</div>
-</li>
-</ul>
-<ul>
-<li class="level1"><div class="li"> <strong>~/.pcb/pcb.inc</strong> and the element will be known to all of our projects.</div>
-</li>
-</ul>
-<ul>
-<li class="level1"><div class="li"> <strong>/path/to/anyfile</strong> if this path is made known to gsch2pcb by adding a line to a project file like:<pre class="code">m4-file /path/to/anyfile
- </pre>
-
-<p>
- Depending on whether you want the file known only to this project, to all of your projects, or to all projects of all users, this line may be added to any of the project files:
-</p>
-<pre class="code">~/gaf/myproject1/project
-~/.gsch2pcb
-/usr/local/etc/gsch2pcb
-/etc/gsch2pcb
- </pre>
-</div>
-</li>
-</ul>
-
-<p>
-For this tutorial, Iâ??ll use the first <strong>pcb.inc</strong> way, so copy over the existing macro file:
-</p>
-<pre class="code">cd /usr/local/share/pcb/m4 (or /usr/share/pcb/m4 or /usr/X11R6/lib/X11/pcb/m4)
-cp dil.inc ~/gaf/myproject1/pcb.inc
-cd ~/gaf/myproject1
-</pre>
-
-<p>
- Now, edit the <strong>pcb.inc</strong> file you just copied and cut everything out except for the PKG_DIL macro. Change the name of the package to something like PKG_DILFAT because the change weâ??ll make will be to make larger diameter pins. Actually, we could leave the name alone and our new definition would override the old one, but for now letâ??s go with the new name. Change the pin diameter from <strong>60</strong> to <strong>70</strong> on the <strong><acronym title="Personal Identification Number">PIN</acronym></strong> lines. When done, this should be the entire contents of the new <strong>pcb.inc</strong> file:
-</p>
-<pre class="code"># -------------------------------------------------------------------
-# the definition of a dual-inline package N and similar types
-# $1: canonical name
-# $2: name on PCB
-# $3: value
-# $4: number of pins
-# $5: package size (300, 600, 900 + 100 for socket space)
-#
-define(`PKG_DILFAT',
-`define(`MAXY', `eval(`$4' / 2 * 100)')
-define(`MAXX', `eval(`$5' + 100)')
-define(`CENTERX', `eval(MAXX / 2)')
-Element(0x00 "$1" "$2" "$3" eval(CENTERX + 20) 100 3 100 0x00)
-(
-forloop(`i', 1, eval($4 / 2),
-`PIN(50, eval(i * 100 -50), 70, 28, i)
-')
-forloop(`i', 1, eval($4 / 2),
-`PIN(eval(MAXX -50), eval(MAXY - i * 100 +50), 70, 28, eval(i + $4/2))
-')
-ElementLine(0 0 0 MAXY 10)
-ElementLine(0 MAXY MAXX MAXY 10)
-ElementLine(MAXX MAXY MAXX 0 10)
-ElementLine(0 0 eval(CENTERX - 50) 0 10)
-ElementLine(eval(CENTERX + 50) 0 MAXX 0 10)
-ElementArc(CENTERX 0 50 50 0 180 10)
-Mark(50 50)
-)')
-</pre>
-
-<p>
- Run <strong>gschem one.sch</strong> and edit the <strong>footprint</strong> attribute of the opamps to be <strong>DILFAT 8 300</strong>. Then run <strong>gsch2pcb project</strong> and gsch2pcb will remove the <strong>DIL</strong> element from <strong>board.pcb</strong> and add into <strong>board.new.pcb</strong> a new <strong>DILFAT</strong> element from your custom m4 file <strong>pcb.inc</strong>. Run <strong>pcb board.pcb</strong> and load the <strong>board.new.pcb</strong> into your layout. Move the new element with its fatter pins to the location left vacant by the removal of the old element.
-</p>
-
-</div>
-<!-- SECTION "Custom m4 elements (Requires gsch2pcb >= 1.0)" [39602-47289] -->
-<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">
-
-<p>
-The above examples are oriented towards a single user with projects and custom gschem and PCB libraries under his home directory. Hereâ??s a way to set up for multiple users who need to share resources:
-</p>
-<ul>
-<li class="level1"><div class="li"> Put site wide custom PCB <strong>file elements</strong> under, for example, <strong>/usr/local/share/pcb/pcb-elements</strong>. Make this directory searched by gsch2pcb for all users by putting a line into <strong>/etc/gsch2pcb</strong> or <strong>/usr/local/etc/gsch2pcb</strong>:<pre class="code">elements-dir /usr/local/share/pcb/pcb-elements
- </pre>
-
-<p>
- If there are any site wide custom PCB <strong>m4 element</strong> files, for example, <strong>/usr/local/share/pcb/pcb.inc</strong>, add another line into <strong>/etc/gsch2pcb</strong> or <strong>/usr/local/etc/gsch2pcb</strong>:
-</p>
-<pre class="code">m4-file /usr/local/share/pcb/pcb.inc
- </pre>
-</div>
-</li>
-</ul>
-<ul>
-<li class="level1"><div class="li"> If the default PCB m4 install is not <strong>/usr/local/share/pcb/m4, /usr/share/pcb/m4,</strong> or <strong>/usr/X11R6/lib/X11/pcb/m4</strong>, then make the install location known to all users of gsch2pcb by putting into <strong>/etc/gsch2pcb</strong> or <strong>/usr/local/etc/gsch2pcb</strong> the line:<pre class="code">m4-pcbdir /path/to/pcb/m4
- </pre>
-
-<p>
- If the m4 program is gm4 instead of m4, add to the gsch2pcb file:
-</p>
-<pre class="code">m4-command gm4
- </pre>
-</div>
-</li>
-</ul>
-<ul>
-<li class="level1"><div class="li"> If there are site wide custom gschem symbols under some directory, you will have to edit the system gschemrc and gnetlistrc files and add <strong>component-library</strong> lines for them.</div>
-</li>
-</ul>
-
-<p>
-With the above, users will have access to site wide libraries and only need to put in a design <strong>project</strong> file lines for <strong>schematics</strong> and <strong>output-name</strong>. But they also are free to have their own additional user and/or project specific symbol and element libraries.
-</p>
-
-</div>
-<!-- SECTION "Multi-user Setup (requires gsch2pcb >= 1.0)" [47290-48927] -->
-<h2><a name="pc_board_fabrication" id="pc_board_fabrication">PC Board Fabrication</a></h2>
-<div class="level2">
-
-<p>
-The tutorial should cover pcb fabrication too.
-</p>
-
-</div>
-
-<h5><a name="photo-lithography" id="photo-lithography">Photo-lithography</a></h5>
-<div class="level5">
-
-<p>
- Use File→Export layout→ps to make a postscript file suitable for printing on a transparency. Note the presence of the â??mirrorâ?? and â??ps-invertâ?? options which you may need depending on your process.
-</p>
-
-<p>
-Open the ps file and print only the pages that you will actually need for fabrication. There are a large number of pages here, many of which you may not need.
-</p>
-
-<p>
-If you find that your pads and traces donâ??t print on the same page, or are placed on the wrong side you need to check the settings under File→Preferences→Layers to group the layers appropriately and place them on the correct side.
-</p>
-
-</div>
-
-<h5><a name="machining" id="machining">Machining</a></h5>
-<div class="level5">
-
-<p>
- <a href="http://www.lpkf.com/"; class="urlextern" title="http://www.lpkf.com"; rel="nofollow">LPKF</a> (and probably other companies) have a pcb plotting machines that accept gerber files. These files can be produced by choosing File→Export Layout→gerber which produces a large number of files. The files can be viewed using <a href="http://geda.seul.org/tools/gerbv/index.html"; class="urlextern" title="http://geda.seul.org/tools/gerbv/index.html"; rel="nofollow">gerbv</a> and the visualization saved. Once you are satisfied with the output gerber files just hand them off to whomever controls the pcb plotting machine and wait for the boards to be completed!
-</p>
-
-</div>
-<!-- SECTION "PC Board Fabrication" [48928-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/geda_gsch2pcb_tutorial_releasenotes.html b/docs/wiki/geda_gsch2pcb_tutorial_releasenotes.html
deleted file mode 100644
index cee89aa..0000000
--- a/docs/wiki/geda_gsch2pcb_tutorial_releasenotes.html
+++ /dev/null
@@ -1,82 +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>geda:gsch2pcb_tutorial_releasenotes</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="keywords" content="geda,gsch2pcb_tutorial_releasenotes" />
-<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/geda:gsch2pcb_tutorial_releasenotes?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gsch2pcb_tutorial_releasenotes"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gsch2pcb_tutorial_releasenotes"; />
-<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">
-
-
-
-<h1><a name="release_notes_for_gsch2pcb_tutorial" id="release_notes_for_gsch2pcb_tutorial">Release Notes for gsch2pcb Tutorial</a></h1>
-<div class="level1">
-
-<p>
-These are the relase notes to the <a href="http://geda.seul.org/wiki/geda:gsch2pcb_tutorial"; class="wikilink1" title="geda:gsch2pcb_tutorial">gsch2pcb tutorial</a>.
-</p>
-<ul>
-<li class="level1"><div class="li"> Starting with the PCB-20050609 snapshot, PCB has a new Gtk user interface which replaces the old Xaw interface and this tutorial will describe using the Gtk interface. If you are using the Xaw PCB, you can look at this <a href="http://www.geda.seul.org/docs/current/tutorials/gsch2pcb/tutorial-old.html"; class="urlextern" title="http://www.geda.seul.org/docs/current/tutorials/gsch2pcb/tutorial-old.html"; rel="nofollow"> older version of this tutorial,</a> which is also not up to date with info on the gEDA gafrc files.</div>
-</li>
-</ul>
-<ul>
-<li class="level1"><div class="li"> If you have a gschem version less than 20030525 these tutorial examples may not work as expected.</div>
-</li>
-</ul>
-<ul>
-<li class="level1"><div class="li"> If you have gEDA version 20030901 installed such that you are using its included gsch2pcb 0.9 and you are getting an error:<pre class="code">ERROR: Unbound variable: open-output-pipe</pre>
-
-<p>
- then the problem is syntax in <em>gnet-gsch2pcb.scm</em> that worked in guile 1.4 but does not work in guile 1.6. Youâ??ll need to upgrade to using at least gsch2pcb 1.0.1 to solve this problem.
-</p>
-</div>
-</li>
-</ul>
-<ul>
-<li class="level1"><div class="li"> As of about 1/9/2004 <acronym title="Concurrent Versions System">CVS</acronym> PCB versions changed to using a hi resolution output file format which will require using at least gsch2pcb-1.4.</div>
-</li>
-</ul>
-<ul>
-<li class="level1"><div class="li"> <strong> Mini Changelog</strong></div>
-<ul>
-<li class="level2"><div class="li"> 5/16/2007 Imported into wiki. Weâ??ll see if itâ??s worth keeping this Changelog up to date after this.</div>
-</li>
-<li class="level2"><div class="li"> 6/23/2005 Added gafrc file info to setup section. Updated the tutorial to use the Gtk PCB.</div>
-</li>
-<li class="level2"><div class="li"> 1/10/2004 Corrected my sloppy PCB file elements which had silkscreen lines overlapping solder pads.</div>
-</li>
-<li class="level2"><div class="li"> 12/23/2003 Added comments about new <acronym title="Concurrent Versions System">CVS</acronym> PCB versions which have the m4 and newlib directories default installed under /usr/share or /usr/local/share.</div>
-</li>
-</ul>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Release Notes for gsch2pcb Tutorial" [1-1644] -->
-<h2><a name="source_of_the_original_document" id="source_of_the_original_document">Source of the original document</a></h2>
-<div class="level2">
-
-<p>
-The tutorial was originally prepared by Bill Wilson (bill–at–gkrellm.net). <a href="http://members.dslextreme.com/users/billw/gsch2pcb/gsch2pcb.html"; class="urlextern" title="http://members.dslextreme.com/users/billw/gsch2pcb/gsch2pcb.html"; rel="nofollow">gsch2pcb Home</a>
-</p>
-
-</div>
-<!-- SECTION "Source of the original document" [1645-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/geda_gschem2pcb_readme.html b/docs/wiki/geda_gschem2pcb_readme.html
deleted file mode 100644
index 5c7d4e2..0000000
--- a/docs/wiki/geda_gschem2pcb_readme.html
+++ /dev/null
@@ -1,166 +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>geda:gschem2pcb_readme</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="geda,gschem2pcb_readme" />
-<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/geda:gschem2pcb_readme?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gschem2pcb_readme"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gschem2pcb_readme"; />
-<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">
-
-
-
-<h1><a name="gschem2pcb_readme" id="gschem2pcb_readme">gschem2pcb README</a></h1>
-<div class="level1">
-<pre class="code">------------------------------------------------------------------
-JM Routoure. routoure@xxxxxxxxxxxxxx
-17/01/2000
-
-I would like to thank Stefan Petersen for debuging the scheme program.
-
--------------------------------------------------------------------
-
-
-This document describes how to install (section I) and use (section II) the
-gschem2pcb package. Section III describes some of the footprints
-available in pcb
-
-The purpose of this package is to interface gschem with pcb. It uses a scheme
-program and a script.
-
-
-Section I : Installation.
-
-1. Untar the gschem2pcb.tar. You must obtain 3 files gschem2pcb.sh,
-GNET-PCBboard.scm and the README file.
-
-2. Move gschem2pcb.sh in a directory which is in your PATH (/usr/local/bin for
-instance ). Be sure that gschem2pcb.sh can be executed (chmod 755 gschem2pcb.sh)
-
-3. Move GNET-PCBboard.scm in the share directory of your gEDA distribution.
-Normally, it should be /usr/local/share/gEDA/scheme.
-
-4. Modify the common.m4 file of the pcb program (should be found in
-/usr/X11R6/lib/X11/pcb/m4/) like this : the include keywords at the end of the
-file must be replace by
-
-include(/usr/X11R6/lib/X11/pcb/m4/connector.inc)
-include(/usr/X11R6/lib/X11/pcb/m4/dil.inc)
-include(/usr/X11R6/lib/X11/pcb/m4/misc.inc)
-include(/usr/X11R6/lib/X11/pcb/m4/plcc.inc)
-include(/usr/X11R6/lib/X11/pcb/m4/to.inc)
-include(/usr/X11R6/lib/X11/pcb/m4/qfp.inc)
-
-5. Edit the ~/.gEDA/gschemrc file and be sure that the following line exists :
-(attribute-name "footprint")
-
-
-6. Be sure that grep, sed and gawk are installed. That's all..
-
-
-Section II : using gschem2pcb.
-
-1. With gschem, create a schematic. All the device you want to have in pcb must
-have a Uref attribute. The footprint that you want to use in pcb are indicated
-by the footprint attribute (see section III for the description of the footprint
-in pcb)
-
-Be careful that the attributes Uref, name, value and device must not contain
-space char.
---------------------------------------------------------
-
-2. Save your work (ultralownoise.sch for instance -ambitious design!) and type in a shell
-
- gschem2pcb.sh ultralownoise.sch.
-
-note : the gschem file must end by .sch
-
-Error messages will appear if some space characters are found in the
-attributes Uref, name, value and device and if the name of the footprint was not
-found. Warning, pcb files are created even if errors occur!
-
-- if ultralownoise.pcb does not exist, it will be created. A netlist file
-ultralownoise.net will also be created. In pcb, load the pcb (load layout). All
-the footprints will appears at the top-left corner of the windows. Load the
-netlist (load netlist file) and type the key "w". Place the footprints and type
-"o" to optimize the rastnet. See the pcb documentation for details.
-
-- if ultralownoise.pcb exists, a ultralownoise.new.pcb file should be
-created. It should contain only the new device that have been added in the
-schematic since the last save of the ultralownoise.pcb file. Use "load layout
-data to paste buffer" to include the new footprints in the pcb file. The nestlist
-file is also updated so read it again.
-
-
-Section III. Description of the name of the footprint in pcb.
-pcb uses macro to define the footprints. For DIL packages, for instance, 2
-arguments are used to indicate the number of pins and the width in mil of the
-footprint. In gschem the footprint attribute of a 300 mil width and 8 pins DIL
-is:
-DIL 8 300.
-Warning, for that attribute, you have to included the space char!
-
-In the following. I describe the footprint attribute that are to be used in
-gschem for the footprint avalaible in pcb. N stands
-for the number of pins, W the width in mil, L the length in mil and D the
-diameter in mil
-CONNECTOR ROWS COLS # single connector
-DIN41_651LAY N # DIN 41.651 laying
-DIN41_651STAND N # DIN 41.651 standing
-SUBD_LAY_BASE N # SUB-D connector laying
-SUBD_MALE_LAY_BASE N # SUB-D connector male laying
-SUBD_FEMALE_LAY_BASE N # SUB-D connector female laying
-DIL N W # dual-inline standard
-D N # dual inline with W=244
-DW N # dual inline with W=419
-SD N # SD (ZIP)
-MULTIWATT15 # 15 pins multiwatt footprint
-R025 # standard 1/4W resistor !now attributes
-SIL N # SIL
-CSIL # SIL package with a common pin
-QFP132 # QFP132 flat pack
-LED D # standing LED
-DIODE_LAY L # laying diode
-AXIAL_LAY L # standard axial footprint
-CRYSTAL W # crystal package
-OSC # a can oscillator
-ISA8 # 8 bit ISA Slot card
-OVEN_OSC # ovenized-oscillator package
-RADIAL_CAN W # a radial capcitor package
-PLCC N # pllc
-PLCC N add # pllc with additionnal border add
-QFP N add # qfp with additionnal border add
-No additional parameters for the to footprints
-TO3_90
-TO3_45
-TO5
-TO92
-TO126
-TO126LAY-WIDE
-TO126STAND-WIDE
-TO220
-TO220LAY-WIDE
-TO220STAND
-TO220STAND-WIDE
-
-</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_gschem_mp.html b/docs/wiki/geda_gschem_mp.html
deleted file mode 100644
index 8677d80..0000000
--- a/docs/wiki/geda_gschem_mp.html
+++ /dev/null
@@ -1,144 +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>geda:gschem_mp</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="geda,gschem_mp" />
-<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/geda:gschem_mp?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gschem_mp"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gschem_mp"; />
-<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">
-
-
-
-<h1><a name="gschem_man-page" id="gschem_man-page">gschem man-page</a></h1>
-<div class="level1">
-<pre class="code">gschem(1) 20031231 gschem(1)
-
-
-
-NAME
- gschem - gEDA/gaf Schematic Capture
-
-SYNOPSIS
- gschem [-q] [-v] [-t] [-r rcfilename] [-s scriptfilename] [-o output-
- filename] [-p] [schematic1 ... schematicN]
-
-DESCRIPTION
- gschem is the schematic capture program which is part gEDA (GPL Elec-
- tronic Design Automation) toolset. This program is used to draw elec-
- tronic schematics. Schematics consist of standard symbols (which are
- either part of a standard library or created by the user) which repre-
- sent the various gates and components. These components are then
- interconnected by nets (wires). Schematics may be printed to a
- PostScript file for printing or further conversion to other output for-
- mats.
-
- gschem is also the symbol creation editor. All the standard methods of
- creating schematics are used in the creation of symbols. There are a
- few special rules when creating symbols, so please refer to the (non-
- existant as of now) symbol creation document.
-
- Please read the official documentation (very minimal at this point) on
- how to use gschem, since this man page just describes the command line
- arguments and a few examples on how to run gschem.
-
-
-OPTIONS
- gschem accepts the following options:
-
- -q Quiet mode on. This mode turns off all warnings/notes/mes-
- sages. (optional)
-
- -v Verbose mode on. This mode gives as much feedback to the user
- as possible. (optional)
-
- -t Print out more information when using mouse strokes. With this
- command line flag and the middle button configured for mouse
- strokes, gschem will output the stroke sequence numbers as the
- user executes strokes. These numbers can be used to define new
- strokes in the system-gschemrc file.
-
- -r filename
- Specify a rc filename. Normally gschem searches for the sys-
- tem-gschemrc, then ~/.gEDA/gschemrc, and finally for a gschemrc
- in the current directory. This options allows the user to
- specify an additional rc file which is read after all the other
- rc files are read. (optional)
-
- -s filename
- Specify a guile script to be executed at startup. (optional)
-
- -o filename
- Specify a filename for postscript output. This command line
- argument is useful when running gschem from a shell script and
- with a guile script. The filename can be changed through the
- print dialog box.
-
- -p Automatically place the window, especially useful if running
- gschem from the command line and generating output.
-
- schematic1 [... schematicN]
- Schematic file to be loaded. Specifing a schematic file is
- optional. If multiple schematic files are specified they are
- read in sequentially and put on seperate pages. It is impor-
- tant that the schematic(s) follow all the options (ie last).
-
-
-EXAMPLES
- These examples assume that you have a schematic called stack_1.sch in
- the current directory
-
- To run gschem and then interact with the program:
-
- ./gschem
-
- To run gschem in interactive mode but load a sample schematic:
-
- ./gschem adders_1.sch
-
- To run gschem and load up all schematics in the current subdirectory:
-
- ./gschem *.sch
-
-
-ENVIRONMENT
- No environment variables are used.
-
-
-AUTHOR
- Ales Hvezda and many others
-
-
-SEE ALSO
- gnetlist(1), gsymcheck(1)
-
-COPYRIGHT
- Copyright © 1999-2004 Ales Hvezda
-
- This document can be freely redistributed according to the terms of the
- GNU General Public License version 2.0
-
-
-
-
-Version December 31st, 2003 gschem(1)</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_gschem_ug.html b/docs/wiki/geda_gschem_ug.html
deleted file mode 100644
index 27745bb..0000000
--- a/docs/wiki/geda_gschem_ug.html
+++ /dev/null
@@ -1,3684 +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>geda:gschem_ug</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2008-05-17T12:07:52-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/"; />
-<link rel="contents" href="http://geda.seul.org/wiki/geda:gschem_ug?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gschem_ug"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gschem_ug"; />
-<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="#geda_gschem_user_guide" class="toc">gEDA gschem User Guide</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#about_this_document" class="toc">About this document ...</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#introduction" class="toc">Introduction</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#overview" class="toc">Overview</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#resources" class="toc">Resources</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#how_to_ask_questions" class="toc">How To Ask Questions</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#installing_gschem" class="toc">Installing gschem</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#latest_stable" class="toc">Latest Stable</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#geda_tools_suite_cd-rom" class="toc">"gEDA Tools Suite" CD-ROM</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#debian_distributions" class="toc">Debian distributions</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#fedora_and_redhat_distributions" class="toc">Fedora and RedHat distributions</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#suse_and_opensuse_distributions" class="toc">SuSE and OpenSuSE distributions</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#mac_osx_distributions" class="toc">Mac OSX distributions</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#cvs_unstable_testing" class="toc">CVS Unstable/Testing</a></span></div></li>
-</ul>
-</li>
-<li class="level1"><div class="li"><span class="li"><a href="#configuring_gschem" class="toc">Configuring gschem</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#gschemrc" class="toc">gschemrc</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#gafrc" class="toc">gafrc</a></span></div></li>
-</ul>
-</li>
-<li class="level1"><div class="li"><span class="li"><a href="#running_gschem" class="toc">Running gschem</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#confirming_gschem_is_installed" class="toc">Confirming gschem is installed</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#the_shell_prompt" class="toc">The Shell Prompt</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#backups" class="toc">Backups</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#classic_linux_backups" class="toc">Classic Linux backups</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#incremental_backups" class="toc">Incremental backups</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#relevant_configuration_settings" class="toc">Relevant configuration settings</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#on-line_documentation" class="toc">On-line documentation</a></span></div></li>
-</ul>
-</li>
-<li class="level1"><div class="li"><span class="li"><a href="#electrical_connectivity" class="toc">Electrical Connectivity</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#components_symbols_objects_attributes" class="toc">Components & Symbols & Objects & Attributes</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#components" class="toc">Components</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#symbols" class="toc">Symbols</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#objects" class="toc">Objects</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#attributes" class="toc">Attributes</a></span></div></li>
-</ul>
-</li>
-<li class="level1"><div class="li"><span class="li"><a href="#the_main_window" class="toc">The Main Window</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#the_status_window" class="toc">The Status Window</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#the_schematic_file" class="toc">The Schematic File</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#the_symbol_file" class="toc">The Symbol File</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#symbol_libraries" class="toc">Symbol Libraries</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#the_log_file" class="toc">The Log File</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#grips" class="toc">Grips</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#menu_operations" class="toc">Menu Operations</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#file" class="toc">File</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#new_window_fw" class="toc">New Window (fw)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#new_page_fn" class="toc">New Page (fn)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#open_page..._fo" class="toc">Open Page... (fo)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#close_page_pc" class="toc">Close Page (pc)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#revert_page_pr" class="toc">Revert Page (pr)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#save_page_fs" class="toc">Save Page (fs)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#save_page_as..._fa" class="toc">Save Page As... (fa)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#save_all_fl_fl" class="toc">Save All (fl) (fl)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#print..._fp" class="toc">Print... (fp)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#write_png..._fi" class="toc">Write PNG... (fi)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#execute_script..._ft" class="toc">Execute Script... (ft)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#close_window_fc" class="toc">Close Window (fc)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#quit_alt-q" class="toc">Quit (Alt-q)</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#edit" class="toc">Edit</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#undo_shift-u" class="toc">Undo (shift-u)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#redo_shift-r" class="toc">Redo (shift-r)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#select_mode_s" class="toc">Select Mode (s)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#edit..._ee" class="toc">Edit... (ee)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#edit_text..._ex" class="toc">Edit Text... (ex)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#copy_mode_ec" class="toc">Copy Mode (ec)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#move_mode_em" class="toc">Move Mode (em)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#delete_delete-key" class="toc">Delete (Delete-key)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#rotate_90_mode_er" class="toc">Rotate 90 Mode (er)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#mirror_mode_ei" class="toc">Mirror Mode (ei)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#slot..._e_shift-s" class="toc">Slot... (e shift-s)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#color..._eo" class="toc">Color... (eo)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#lock_el_unlock_e_shift-l" class="toc">Lock (el) / Unlock (e shift-l)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#line_width_type..._ew" class="toc">Line Width & Type... (ew)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#fill_type..._ef" class="toc">Fill Type... (ef)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#symbol_translate..._et" class="toc">Symbol Translate... (et)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#embed_component_picture_eb" class="toc">Embed Component/Picture (eb)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#unembed_component_picture_eu" class="toc">Unembed Component/Picture (eu)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#update_component_ep" class="toc">Update Component (ep)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#show_hide_inv_text_en" class="toc">Show/Hide Inv Text (en)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#make_inv_text_vis_ev" class="toc">Make Inv Text Vis (ev)</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#buffer" class="toc">Buffer</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#copy_into_1_2_3_4_5_yc" class="toc">Copy into 1/2/3/4/5 (yc)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#cut_into_1_2_3_4_5_yu" class="toc">Cut into 1/2/3/4/5 (yu)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#paste_from_1_2_3_4_5_yp" class="toc">Paste from 1/2/3/4/5 (yp)</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#view" class="toc">View</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#redraw_vr" class="toc">Redraw (vr)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#pan_x" class="toc">Pan (x)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#zoom_box_w" class="toc">Zoom Box (w)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#zoom_extents_ve" class="toc">Zoom Extents (ve)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#zoom_in_z" class="toc">Zoom In (z)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#zoom_out_z" class="toc">Zoom Out (Z)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#zoom_full_vf" class="toc">Zoom Full (vf)</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#page" class="toc">Page</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#manager..._pm" class="toc">Manager... (pm)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#next" class="toc">Next (>)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#previous" class="toc">Previous (<)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#new_pe" class="toc">New (pe)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#revert_pr" class="toc">Revert (pr)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#close_pc" class="toc">Close (pc)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#discard_pd" class="toc">Discard (pd)</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#add" class="toc">Add</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#component..._i" class="toc">Component... (i)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#net_n" class="toc">Net (n)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#bus_u" class="toc">Bus (u)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#attribute..._aa" class="toc">Attribute... (aa)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#text..._at" class="toc">Text... (at)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#line_l" class="toc">Line (l)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#box_b" class="toc">Box (b)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#circle_ai" class="toc">Circle (ai)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#arc_ar" class="toc">Arc (ar)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#pin_ap" class="toc">Pin (ap)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#picture..._ag" class="toc">Picture... (ag)</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#hierarchy" class="toc">Hierarchy</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#down_schematic_hd" class="toc">Down Schematic (Hd)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#down_symbol_hs" class="toc">Down Symbol (Hs)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#up_hu" class="toc">Up (Hu)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#documentation_ho" class="toc">Documentation (Ho)</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#attributes1" class="toc">Attributes</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#attach_ta" class="toc">Attach (ta)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#detach_td" class="toc">Detach (td)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#show_value_tv" class="toc">Show Value (tv)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#show_name_tn" class="toc">Show Name (tn)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#show_both_tb" class="toc">Show Both (tb)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#toggle_visibility_tt" class="toc">Toggle Visibility (tt)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#find_specific_text..._t_shift-f" class="toc">Find Specific Text... (t shift-f)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#hide_specific_text..._th" class="toc">Hide Specific Text... (th)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#show_specific_text..._t_shift-h" class="toc">Show Specific Text... (t shift-h)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#autonumber_text..._tu" class="toc">Autonumber Text... (tu)</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#options" class="toc">Options</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#text_size..._ot" class="toc">Text Size... (ot)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#toggle_grid_on_off_og" class="toc">Toggle Grid On/Off (og)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#toggle_snap_on_off_os" class="toc">Toggle Snap On/Off (os)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#snap_grid_spacing..._os" class="toc">Snap Grid Spacing... (oS)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#toggle_outline_box_oa" class="toc">Toggle Outline/Box (oa)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#toggle_net_rubberband_or" class="toc">Toggle Net/Rubberband (or)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#show_log_window_ol" class="toc">Show Log Window (ol)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#show_coord_window..._oc" class="toc">Show Coord Window... (oc)</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#help" class="toc">Help</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#about..._ha" class="toc">About... (ha)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#manual..._hm" class="toc">Manual... (hm)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#hotkeys..._hh" class="toc">Hotkeys... (hh)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#component..._ho" class="toc">Component... (Ho)</a></span></div></li>
-</ul>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"><span class="li"><a href="#appendix_a_--_heavy_vs_light_symbol_libraries" class="toc">Appendix A -- Heavy vs Light Symbol Libraries</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#appendix_b_--_printing_schematics_and_symbols" class="toc">Appendix B -- Printing Schematics and Symbols</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#appendix_c_--_writing_guile_scripts" class="toc">Appendix C -- Writing guile Scripts</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#appendix_d_--_i_want_to_build_a_printed_circuit_board" class="toc">Appendix D -- I Want To Build A Printed Circuit Board</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#appendix_e_--_i_want_to_simulate_my_design" class="toc">Appendix E -- I Want To Simulate My Design</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#appendix_f_--_change_gschemdoc_user-defined_preferences" class="toc">Appendix F -- Change gschemdoc User-Defined Preferences</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#appendix_g_--_breaking_a_large_symbol_into_smaller_symbols" class="toc">Appendix G -- Breaking a Large Symbol Into Smaller Symbols</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#appendix_h_--_definition_of_terms" class="toc">Appendix H -- Definition of Terms</a></span></div></li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="geda_gschem_user_guide" id="geda_gschem_user_guide">gEDA gschem User Guide</a></h1>
-<div class="level1">
-
-<p>
-by: Ales Hvezda / September 21st, 2003
-</p>
-
-<p>
-The latest version of this document may be found at: <a href="http://geda.seul.org/wiki/geda:gschem_ug"; class="urlextern" title="http://geda.seul.org/wiki/geda:gschem_ug"; rel="nofollow">http://geda.seul.org/wiki/geda:gschem_ug</a>
-</p>
-
-<p>
-This document is released under the <a href="geda_gfdl.html" class="wikilink1" title="geda:gfdl">GNU Free Documentation License (GFDL)</a>.
-</p>
-
-<p>
- Please report any errors/inconsistencies in this document by commenting in the Discussion area at the bottom of the associated page.
-</p>
-
-</div>
-<!-- SECTION "gEDA gschem User Guide" [1-397] -->
-<h1><a name="about_this_document" id="about_this_document">About this document ...</a></h1>
-<div class="level1">
-
-<p>
-gEDA gschem Users Guide
-</p>
-
-<p>
-This document was generated using the LaTeX2HTML translator Version 2002-2-1 (1.70)
-</p>
-
-<p>
-Copyright © 1993, 1994, 1995, 1996, Nikos Drakos, Computer Based Learning Unit, University of Leeds. Copyright © 1997, 1998, 1999, Ross Moore, Mathematics Department, Macquarie University, Sydney.
-</p>
-
-<p>
-The command line arguments were: latex2html -local_icons gschem
-</p>
-
-<p>
-The translation was initiated by Ales Hvezda on 2005-08-20
-</p>
-
-</div>
-<!-- SECTION "About this document ..." [398-871] -->
-<h1><a name="introduction" id="introduction">Introduction</a></h1>
-<div class="level1">
-
-<p>
-This document describes the installation, configuration, and operation of the <strong>gschem</strong> application.<br/>
- This document does not describe the process of generating schematics. For this, refer to the various tutorials on using the gEDA Tool Suite:
-</p>
-<ul>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:gschem_warmup"; class="wikilink1" title="geda:gschem_warmup">Bill Wilson's gschem warmup</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:gsch2pcb_tutorial"; class="wikilink1" title="geda:gsch2pcb_tutorial">Bill Wilson's gsch2pcb tutorial</a></div>
-</li>
-<li class="level1"><div class="li"> â??Optical Proximity Sensor for Robots (Part 1), Simple PCB Design with the gEDA Suiteâ??, by Stuart Brorson (March 2006 Circuit Cellar article)</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://www-mdp.eng.cam.ac.uk/urop05/files/gedalib/starting_gEDA.pdf"; class="urlextern" title="http://www-mdp.eng.cam.ac.uk/urop05/files/gedalib/starting_gEDA.pdf"; rel="nofollow">Starting with gEDA at the Cambridge University Engineering Department</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://www.brorson.com/gEDA/SPICE/t1.html"; class="urlextern" title="http://www.brorson.com/gEDA/SPICE/t1.html"; rel="nofollow">"Circuit simulation using gEDA and SPICE -- HOWTO" by Stuart Brorson</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://www.circuitcellar.com/magazine/176toc.htm"; class="urlextern" title="http://www.circuitcellar.com/magazine/176toc.htm"; rel="nofollow">"gEDA Design Suite for Linux" by Stuart Brorson, Ales Hvezda, & Dan McMahill (03 Mar 2005 Circuit Cellar article)</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://www.linuxjournal.com/article/8438"; class="urlextern" title="http://www.linuxjournal.com/article/8438"; rel="nofollow">"Circuit Design on Your Linux Box Using gEDA" by Stuart Brorson (29 November 2005 Linux Journal article)</a></div>
-</li>
-<li class="level1"><div class="li"> Optical Proximity Sensor for Robots (Part 1): Simple PCB Design with the gEDA Suite, by Stuart Brorson, Circuit Cellar magazine, March 2006 (Issue 188), p. 48</div>
-</li>
-<li class="level1"><div class="li"> And, of course, <a href="http://www.google.com/search?hl=en&lr=&q=gEDA+%22schematic+capture%22+tutorial&btnG=Search"; class="urlextern" title="http://www.google.com/search?hl=en&lr=&q=gEDA+%22schematic+capture%22+tutorial&btnG=Search"; rel="nofollow">Google is your friend</a>.</div>
-</li>
-</ul>
-
-<p>
- This document assumes you understand basic schematic capture concepts. For example: that a component represents something and that nets and buses interconnect these components to form a schematic, etc… For a basic understanding of the various work-flows available in the gEDA Tool Suite, please read the above tutorials. For more detailed understanding of specific tool issues, please refer to <a href="docs_20060124_gschem_ug_how_to_ask_questions.html" class="wikilink2" title="docs:20060124:gschem_ug:how_to_ask_questions">How To Ask Questions</a> and to the <a href="docs_20060124_gschem_ug_resources.html" class="wikilink2" title="docs:20060124:gschem_ug:resources">Resources</a>.
-</p>
-
-</div>
-<!-- SECTION "Introduction" [872-2794] -->
-<h1><a name="overview" id="overview">Overview</a></h1>
-<div class="level1">
-
-<p>
-<strong>gschem</strong> is the schematic capture program in the gEDA Tool Suite. Its purpose is to facilitate the graphical input of:
-</p>
-<ul>
-<li class="level1"><div class="li"> circuit schematics</div>
-</li>
-<li class="level1"><div class="li"> component symbols</div>
-</li>
-<li class="level1"><div class="li"> block diagrams</div>
-</li>
-</ul>
-
-<p>
- Once <strong>gschem</strong> has been used to enter the symbols/schematics for your design, several gEDA Tool Suite â??utilityâ?? programs are used to extract information for other purposes:
-</p>
-<ul>
-<li class="level1"><div class="li"> <strong>gattrib</strong> – <strong>gattrib</strong> is a gEDA Tool Suite productivity aid. <strong>gattrib</strong> reads a [hierarchical set of] gschem schematic files and creates a spreadsheet showing all components in rows, with the associated component attributes listed in the columns. It allows the user to add, modify, or delete component attributes outside of <strong>gschem</strong>, and then save the .sch files.</div>
-</li>
-<li class="level1"><div class="li"> <strong>gnetlist</strong> – A tool that converts a [hierarchical set of] schematic files into an equivalent netlist (a textual representation of a schematic) in various formats. Various gnetlist back-ends are used to create:</div>
-<ul>
-<li class="level2"><div class="li"> Bill of Materials (BOM) files.</div>
-</li>
-<li class="level2"><div class="li"> Design Rule Checks (DRCs).</div>
-</li>
-<li class="level2"><div class="li"> Netlist files for use as input to various printed circuit board layout programs (e.g., Allegro, PADS, <strong>pcb</strong> (part of the gEDA Tool Suite), Protell, Tango, RACAL-REDAC, etc.).</div>
-</li>
-<li class="level2"><div class="li"> Files for input to SPICE simulation programs.</div>
-</li>
-<li class="level2"><div class="li"> VHDL code.</div>
-</li>
-<li class="level2"><div class="li"> Verilog code.</div>
-</li>
-<li class="level2"><div class="li"> etc.</div>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"> <strong>grenum</strong> – <strong>grenum</strong> is a gEDA Tool Suite productivity aid that will renumber the reference designators (i.e., refdes) in a [hierarchical set of] schematic files.</div>
-</li>
-<li class="level1"><div class="li"> <strong>gsch2pcb</strong> – The prefered method to create a netlist for the <strong>pcb</strong> printed circuit board layout tool (part of the gEDA Tool Suite).</div>
-</li>
-<li class="level1"><div class="li"> <strong>gspiceui</strong> – GNU Spice <acronym title="Graphical User Interface">GUI</acronym> (i.e., <strong>gspiceui</strong>) provides a <acronym title="Graphical User Interface">GUI</acronym> for freely available Spice electronic cicuit simulation engines (e.g., <strong>gnucap</strong> and <strong>ngspice</strong>). It uses <strong>gnetlist</strong> (to convert schematic files to net list files) and <strong>gwave</strong> (to display simulation results). gSchem is the preferred schematic capture tool.</div>
-</li>
-<li class="level1"><div class="li"> <strong>gsymcheck</strong> – A checker for symbols created with gEDA Tool Suite (e.g., <strong>gschem</strong>, <strong>tragesym</strong>, etc.).</div>
-</li>
-<li class="level1"><div class="li"> <strong>pcb</strong> – A tool for the layout of printed circuit boards.</div>
-</li>
-<li class="level1"><div class="li"> <strong>refdes_renum</strong> – Reads a [hierarchical set of] <strong>gschem</strong> schematic files and renumbers all reference designators. The reference designators are numbered starting with 1 and the old schematic file is replaced by the modified schematic file.</div>
-</li>
-<li class="level1"><div class="li"> <strong>tragesym</strong> – A python script that creates geda symbols from structured textfiles. The symbols usually need to be â??cleaned upâ?? in gschem.</div>
-</li>
-</ul>
-<table class="inline">
- <tr>
- <td> <a href="_detail/geda_gschem_workflow_01.html" class="media" title="geda:gschem_workflow_01.jpg"><img src="_media/geda_gschem_workflow_01.jpg" class="media" title="gschem_workflow_01.jpg" alt="gschem_workflow_01.jpg" /></a> </td>
- </tr>
-</table>
-
-</div>
-<!-- SECTION "Overview" [2795-5375] -->
-<h1><a name="resources" id="resources">Resources</a></h1>
-<div class="level1">
-
-<p>
-The following on-line resources are useful for designers using <strong>gschem</strong>:
-</p>
-<ul>
-<li class="level1"><div class="li"> <a href="http://www.geda.seul.org/docs/current/tutorials/gsch2pcb/gschem-warmup.html"; class="urlextern" title="http://www.geda.seul.org/docs/current/tutorials/gsch2pcb/gschem-warmup.html"; rel="nofollow">Bill Wilson's gschem warmup tutorial</a> – If you are new to the gEDA tools, read this before you read Billâ??s â??Bill Wilsonâ??s gsch2pcb tutorialâ??.</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://www.geda.seul.org/docs/current/tutorials/gsch2pcb/tutorial.html"; class="urlextern" title="http://www.geda.seul.org/docs/current/tutorials/gsch2pcb/tutorial.html"; rel="nofollow">Bill Wilson's gsch2pcb tutorial</a> – If you are new to the gEDA tools, this tutorial will bring you up to speed quickly.</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://www.circuitcellar.com/"; class="urlextern" title="http://www.circuitcellar.com/"; rel="nofollow">Circuit Cellar Magazine</a> – Practical, hands-on applications and solutions for embedded designers:</div>
-<ul>
-<li class="level2"><div class="li"> gEDA Design Suite for Linux, by Stuart Brorson, Ales Hvezda, & Dan McMahill, Circuit Cellar magazine, March 2005 (Issue 176), p. 12</div>
-</li>
-<li class="level2"><div class="li"> Optical Proximity Sensor for Robots (Part 1): Simple PCB Design with the gEDA Suite, by Stuart Brorson, Circuit Cellar magazine, March 2006 (Issue 188), p. 48</div>
-</li>
-<li class="level2"><div class="li"> Optical Proximity Sensor for Robots (Part 2): Open-Source PCB Layout Editor, by Stuart Borson, Circuit Cellar magazine, April 2006 (Issue 189), p. 40</div>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"> <a href="http://www.geda.seul.org/index.html"; class="urlextern" title="http://www.geda.seul.org/index.html"; rel="nofollow">gEDA Project home page</a> – The homepage for the gEDA Tools Suite. A rather mature site, includes (but not limited to):</div>
-<ul>
-<li class="level2"><div class="li"> <a href="http://www.geda.seul.org/news/index.html"; class="urlextern" title="http://www.geda.seul.org/news/index.html"; rel="nofollow">News</a> – from 2002</div>
-</li>
-<li class="level2"><div class="li"> <a href="http://www.geda.seul.org/screenshots/index.html"; class="urlextern" title="http://www.geda.seul.org/screenshots/index.html"; rel="nofollow">Screenshots</a> – <strong>gschem</strong> in action</div>
-</li>
-<li class="level2"><div class="li"> <a href="http://www.geda.seul.org/tools/index.html"; class="urlextern" title="http://www.geda.seul.org/tools/index.html"; rel="nofollow">Tools</a> – links to project homepages</div>
-</li>
-<li class="level2"><div class="li"> <a href="http://www.geda.seul.org/download.html"; class="urlextern" title="http://www.geda.seul.org/download.html"; rel="nofollow">Download</a> – <acronym title="International Organization for Standardization">ISO</acronym> images, binaries, and sources</div>
-</li>
-<li class="level2"><div class="li"> <a href="http://www.geda.seul.org/mailinglist/index.html"; class="urlextern" title="http://www.geda.seul.org/mailinglist/index.html"; rel="nofollow">Lists</a> – e-mail list subscription and archives</div>
-</li>
-<li class="level2"><div class="li"> <a href="http://www.geda.seul.org/docs/index.html"; class="urlextern" title="http://www.geda.seul.org/docs/index.html"; rel="nofollow">Docs</a> – current gEDA/gaf documentation (not gEDA Tools Suite documentation), wiki, slide presentations</div>
-</li>
-<li class="level2"><div class="li"> <a href="http://www.geda.seul.org/developer.html"; class="urlextern" title="http://www.geda.seul.org/developer.html"; rel="nofollow">Devel</a> – nonymous <acronym title="Concurrent Versions System">CVS</acronym> access</div>
-</li>
-<li class="level2"><div class="li"> <a href="http://www.geda.seul.org/search.html"; class="urlextern" title="http://www.geda.seul.org/search.html"; rel="nofollow">Search</a> – by Google</div>
-</li>
-<li class="level2"><div class="li"> <a href="http://www.geda.seul.org/links.html"; class="urlextern" title="http://www.geda.seul.org/links.html"; rel="nofollow">Links</a> – links associated with gEDA, projects developed using gEDA Tools Suite, gEDA-related press</div>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"> <a href="http://sourceforge.net/tracker/?group_id=161080&atid=818426"; class="urlextern" title="http://sourceforge.net/tracker/?group_id=161080&atid=818426"; rel="nofollow">gEDA Bug Tracker</a> – On SourceForge</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/dokuwiki/doku.php?id=geda"; class="urlextern" title="http://geda.seul.org/dokuwiki/doku.php?id=geda"; rel="nofollow">gEDA Project's Wiki</a> – All things related to the gEDA Tools Suite.</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://www.gedasymbols.org/"; class="urlextern" title="http://www.gedasymbols.org"; rel="nofollow">gedasymbols.org</a> – On-line repository of user-developed symbols for <strong>gschem</strong>, SPICE models, and footprints for <strong>pcb</strong>.</div>
-</li>
-<li class="level1"><div class="li"> John C. Lucianiâ??s proposed <a href="http://www.luciani.org/geda/pcb/footprint-name-spec.pdf"; class="urlextern" title="http://www.luciani.org/geda/pcb/footprint-name-spec.pdf"; rel="nofollow">Land Pattern Naming Convention</a> – Footprint naming conventions document, used by him, and often used by those submitting to the <a href="http://www.gedasymbols.org/"; class="urlextern" title="http://www.gedasymbols.org"; rel="nofollow">gedasymbols.org</a> symbols/footprint repository.</div>
-</li>
-<li class="level1"><div class="li"> John C. Lucianiâ??s <a href="http://geda.seul.org/shared/HomePages/dhart/index.html"; class="urlextern" title="file:///shared/HomePages/dhart/index.html" rel="nofollow">PCB Footprints Library</a> – A rather inclusive collection of non-<acronym title="GNU General Public License">GPL</acronym> licensed footprints and the scripts used to create them.</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://www.opencollector.org/"; class="urlextern" title="http://www.opencollector.org/"; rel="nofollow">OpenCollector</a> carries listings and news for free EDA software and circuit designs. Open Collector supports gEDA.</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://alternatezone.com/electronics/files/PCBDesignTutorialRevA.pdf"; class="urlextern" title="http://alternatezone.com/electronics/files/PCBDesignTutorialRevA.pdf"; rel="nofollow">PCB Design Tutorial; RevA</a> – Document describing the process of taking a schematic to a pcb. Excellent for the beginner.</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://pcblibraries.com/"; class="urlextern" title="http://pcblibraries.com/"; rel="nofollow">PCB Libraries website</a> – Advocates of the IPC standard Land Pattern (a.k.a., footprint) Naming Conventions and Land Pattern Calculators. A useful site if you have the money to subscribe to the services.</div>
-<ul>
-<li class="level2"><div class="li"> The free (windows-based) <a href="http://landpatterns.ipc.org/default.asp"; class="urlextern" title="http://landpatterns.ipc.org/default.asp"; rel="nofollow">IPC-7351 Land Pattern Viewer</a> is a very useful tool for viewing the latest IPC footprints.</div>
-</li>
-<li class="level2"><div class="li"> <a href="http://www.pcblibraries.com/resources/LibDoc.asp"; class="urlextern" title="http://www.pcblibraries.com/resources/LibDoc.asp"; rel="nofollow">CAD Data Files to be used with PCB Libraries' IPC-7351A LP Programs</a> – please note the license restrictions.</div>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"> <a href="http://www-mdp.eng.cam.ac.uk/urop05/files/gedalib/starting_gEDA.pdf"; class="urlextern" title="http://www-mdp.eng.cam.ac.uk/urop05/files/gedalib/starting_gEDA.pdf"; rel="nofollow">Starting with gEDA at the Cambridge University Engineering Department</a> – The Cambridge University Engineering Departmentâ??s tutorial for using gEDA.</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://www.brorson.com/gEDA/"; class="urlextern" title="http://www.brorson.com/gEDA/"; rel="nofollow">Stuart Brorson's gEDA tools and tips</a> – gEDA related tools and information.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Resources" [5376-9677] -->
-<h1><a name="how_to_ask_questions" id="how_to_ask_questions">How To Ask Questions</a></h1>
-<div class="level1">
-
-<p>
-<strong>gschem</strong> is an OpenSource, community driven, development. As such, the emphasis has been on developing the gEDA Tools Suite, not on developing commercial-level documentation and support. Much of the burden on learning how to use the gEDA Tools Suite applications is placed on the user, who must understand the basics of electronics, Electronics Design Automation (EDA), and the terminology used in schematic capture, circuit simulation, and printed circuit board design.<br/>
- As a typical OpenSource development, the gEDA Tools Suite development community provides timely and insightful response to user inquiries, but please perform the following steps before bothering the developers (they need to focus on making gEDA Tools Suite applications better, and you can actually learn to answer your own questions and become independent of the developers):
-</p>
-<ol>
-<li class="level1"><div class="li"> Read Rick Moenâ??s <a href="http://www.catb.org/~esr/faqs/smart-questions.html"; class="urlextern" title="http://www.catb.org/~esr/faqs/smart-questions.html"; rel="nofollow">How To Ask Questions The Smart Way</a>, about how to ask for help. This is a must read for everybody.</div>
-</li>
-<li class="level1"><div class="li"> Read this document. I know, itâ??s a lot to expect engineers to actually read a userâ??s guide. The latest version of this document is maintained on the gEDA web-site at <a href="http://geda.seul.org/wiki/geda:gschem_ug"; class="urlextern" title="http://geda.seul.org/wiki/geda:gschem_ug"; rel="nofollow">gschem User Guide</a>. The information should be here. If it isnâ??t, comment to the fact in one of the on-line documentâ??s â??Discussionâ?? areas (at the bottom of each wiki-page). Helpful comments are clear, to the point, and may even contain the wording that should be inserted into the document.</div>
-</li>
-<li class="level1"><div class="li"> Read the <a href="http://geda.seul.org/dokuwiki/doku.php?id=geda:faq-gschem"; class="urlextern" title="http://geda.seul.org/dokuwiki/doku.php?id=geda:faq-gschem"; rel="nofollow">gschem Frequently Asked Questions (FAQ)</a> wiki-page. This on-line document is updated often to reflect user and developer experiences with <strong>gschem</strong>.</div>
-</li>
-<li class="level1"><div class="li"> Read the <a href="http://www.geda.seul.org/docs/current/index.html"; class="urlextern" title="http://www.geda.seul.org/docs/current/index.html"; rel="nofollow">gEDA/gaf Documentation</a>. This information was installed on your computer if the gEDA Tools Suite was installed from the gEDA Tools Suite CD-ROM.</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://www.google.com/"; class="urlextern" title="http://www.google.com"; rel="nofollow">Google</a> is your friend. People that have asked questions that obviously didnâ??t do any simple Google search will not be treated well when asking for help. This is particularly true if your problem is not unique to the gEDA Tools Suite applications.</div>
-</li>
-<li class="level1"><div class="li"> Ask for a pointer to the right direction. It is considered good â??net etiquetteâ?? to ask for a pointer to information, so that you can learn where such information can be found, rather than have someone search the information for you.</div>
-</li>
-<li class="level1"><div class="li"> If you are software literate, look at the source code to see what it is doing.</div>
-</li>
-<li class="level1"><div class="li"> Subscribe to the gEDA e-mail lists (i.e., you can only post to the e-mail lists if you are a subscriber). Then:</div>
-<ol>
-<li class="level2"><div class="li"> Start reading recent messages in the <a href="http://archives.seul.org/geda/user/"; class="urlextern" title="http://archives.seul.org/geda/user/"; rel="nofollow">geda-user e-mail list archives</a>. Get a feel for the listâ??s ettiquite so that you learn how to properly ask questions.</div>
-</li>
-<li class="level2"><div class="li"> Search the archives for issues similar to yours. You may find the question has been asked of the developers and users before, and answered.</div>
-</li>
-<li class="level2"><div class="li"> In the event that you can find no information concerning your problem, submit a concise description of the problem and a request for the type of help you are requesting.</div>
-</li>
-</ol>
-</li>
-</ol>
-
-</div>
-<!-- SECTION "How To Ask Questions" [9678-12915] -->
-<h1><a name="installing_gschem" id="installing_gschem">Installing gschem</a></h1>
-<div class="level1">
-
-<p>
-As a mature OpenSource project, the gEDA Tools Suite and its components have been installed on many Linux distributions. The following are by no means the only methods of installing the gEDA Tools Suite and/or its components.
-</p>
-
-</div>
-<!-- SECTION "Installing gschem" [12916-13174] -->
-<h2><a name="latest_stable" id="latest_stable">Latest Stable</a></h2>
-<div class="level2">
-
-<p>
-<strong>gschem</strong> is a component of the gEDA/gaf set of tools which tend to integrate together in the development and maintenance of schematics and symbols. The term â??gafâ?? stands for â??<em class="u">g</em>EDA <em class="u">a</em>nd <em class="u">f</em>riendsâ??). The gEDA/gaf applications are actually rather stable, and receive significant testing prior to release.<br/>
- There are multiple methods of installing <strong>gschem</strong>. The appropriate method depends on your distribution. See the following for some examples.
-</p>
-
-</div>
-<!-- SECTION "Latest Stable" [13175-13659] -->
-<h3><a name="geda_tools_suite_cd-rom" id="geda_tools_suite_cd-rom">"gEDA Tools Suite" CD-ROM</a></h3>
-<div class="level3">
-
-<p>
-The recommended method is installation from the â??gEDA Tools Suiteâ?? CD-ROM, gratefully prepared by Stuart Brorson. The latest version of this CD-ROM is available on-line for free download as an <acronym title="International Organization for Standardization">ISO</acronym> image from the <a href="http://www.geda.seul.org/download.html"; class="urlextern" title="http://www.geda.seul.org/download.html"; rel="nofollow">gEDA Downloads</a> web-page. Simply burn this <acronym title="International Organization for Standardization">ISO</acronym> image to a CD-ROM using your favorite CD burning software (e.g., K3b, …). Insert the CD-ROM, and if your computer supports autodetection of the CD-ROM, the built-in installation wizzard will launch. This wizzard will first check if your computer has some required software (informing you if you donâ??t and optionally installing these if you want), then build all of the â??gEDA Tool Suiteâ?? applications (including <strong>gschem</strong>) from source. The whole process can take 2 hours on a slower computer.
-</p>
-
-<p>
-If the installation wizzard did not launch, enter as follows to install the gEDA Tool Suite for access by all users on this computer (i.e., when prompted for the installation directory, enter something like: â??/usr/local/gEDA-20060124â??): <pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0"><strong>sudo sh /media/cdrecorder/installer –log –verbose</strong></font></pre>
-</p>
-
-<p>
-The above command requires superuser permissions configured for the user invoking the command. If you do not have the proper permissions to execute this command, ask your administrator to install the gEDA Tool Suite for you.
-</p>
-
-<p>
-If the installation wizzard did not launch, enter as follows to install the gEDA Tool Suite for access by just the user doing the installation(i.e., when prompted for the installation directory, accept the default "/home/{login id}/geda-installâ??): <pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0"><strong>sh /media/cdrecorder/installer –log –verbose</strong></font></pre>
-</p>
-
-</div>
-<!-- SECTION "gEDA Tools Suite CD-ROM" [13660-15346] -->
-<h3><a name="debian_distributions" id="debian_distributions">Debian distributions</a></h3>
-<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.
-</p>
-
-</div>
-<!-- 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">
-
-<p>
-For RedHat distributions you may wish to download the <a href="http://www.sp5pbe.waw.pl/~sp5smk/software.html"; class="urlextern" title="http://www.sp5pbe.waw.pl/~sp5smk/software.html"; rel="nofollow"> RPM binaries</a> prepared by Wojciech Kazubski.
-</p>
-
-<p>
-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 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" [15784-16188] -->
-<h3><a name="suse_and_opensuse_distributions" id="suse_and_opensuse_distributions">SuSE and OpenSuSE distributions</a></h3>
-<div class="level3">
-
-<p>
-For SuSE and OpenSuSE distributions there are rpm packages for several gEDA related programms. Theyâ??ve been prepared by Werner Hoch using the OpenSuSE Build Service.
-</p>
-
-<p>
-You can install the rpm packages with YaST, yum or any other installation tool. The packages are located at <a href="ftp://ftp-1.gwdg.de/pub/opensuse/repositories/home%3A/werner2101/"; class="urlextern" title="ftp://ftp-1.gwdg.de/pub/opensuse/repositories/home%3A/werner2101/"; rel="nofollow">ftp://ftp-1.gwdg.de/pub/opensuse/repositories/home%3A/werner2101/</a>.
-</p>
-
-<p>
-For more informations read the <a href="geda_suse_rpm_installation.html" class="wikilink1" title="geda:suse_rpm_installation"> SuSE rpm installation notes</a>.
-</p>
-
-</div>
-<!-- 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">
-
-<p>
-For Mac OSX 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 Fink binaries</a> prepared by Charles Lepple.
-</p>
-
-</div>
-<!-- SECTION "Mac OSX distributions" [16672-16851] -->
-<h2><a name="cvs_unstable_testing" id="cvs_unstable_testing">CVS Unstable/Testing</a></h2>
-<div class="level2">
-
-<p>
-For those already familiar with the gEDA/gaf applications on the â??gEDA Tools Suiteâ?? CD-ROM, access to the <acronym title="Concurrent Versions System">CVS</acronym> repository is available. This is the latest developer source-code version of the application.<br/>
- Installation from <acronym title="Concurrent Versions System">CVS</acronym> is appropriate for those:
-</p>
-<ul>
-<li class="level1"><div class="li"> Seeking a solution to a specific problem that was submitted to the development team, to test the â??fixâ?? so that the developers can be informed that the â??fixâ?? works.</div>
-</li>
-<li class="level1"><div class="li"> With significant working knowledge of the â??gEDA Tools Suiteâ?? and industry expertise, wishing to test the latest version of the application(s) prior to the next release. This usually requires access to several existing designs known to work in the current stable release of the â??gEDA Tools Suiteâ?? <acronym title="International Organization for Standardization">ISO</acronym> image, so that comparisons can be made and issues brought to the attention of the developer/user community (via the e-mail lists).</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "CVS Unstable/Testing" [16852-17746] -->
-<h1><a name="configuring_gschem" id="configuring_gschem">Configuring gschem</a></h1>
-<div class="level1">
-
-<p>
-Assume that you have installed the gEDA Tools Suite from CD-ROM (the most common installation method), and that you are ready to configure <strong>gschem</strong> to your personal likes. When installing, you were prompted for the path where the gEDA executables would be placed. The default was the <strong>/home/{login id}/geda-install</strong> directory, where {login id} is the username you logged into your account with, but you may have changed this to another directory on the computer. This directory is referred to below as the <strong>{binary-install-path}</strong> because this is where the gEDA binary executables are placed. If you forgot where the binaries were installed, simply issue the following command to find where <strong>gschem</strong> is installed (in this case the {binary-install-path} is <strong>/usr/local/gEDA-20060124</strong>): <pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">% which gschem
-/usr/local/gEDA-20060124/bin/gschem
-%</font></pre>
-</p>
-
-<p>
-The gEDA Tools Suite applications follow normal Unix/Linux conventions for placement of configuration files; there are usually system-wide, user-wide, and project-specific configuration settings. The system-wide settings are placed in a sub-directory of the {binary-install-path}. The user-wide settings are placed in the userâ??s home directory, also known as the login directory (referred to in Unix/Linux parlance as the <strong>$HOME</strong> directory). The project-specific settings are placed in a project-specific directory.<br/>
-
-</p>
-
-<p>
-Now that we know the above, we can configure <strong>gschem</strong>.<br/>
- <strong>gschem</strong> is highly configurable. All configuration is handled through the following resource files (written using the GNU Guile programming language, an interpreter for Scheme, a version of Lisp):
-</p>
-<ul>
-<li class="level1"><div class="li"> <strong>system-gschemrc</strong>: The system-wide initialization file for <strong>gschem</strong>. Installed in the {binary-install-path}/share/gEDA/system-gschemrc file, it is required for <strong>gschem</strong> to run. Users should not modify this file, but should override the settings in this file by creating their own $HOME/.gEDA/gschemrc file and/or â??pwdâ??/gschemrc file and putting the new settings in those files. The {binary-install-path} directory is where your gEDA/gaf executables were installed, including <strong>gschem</strong>. Depends on your install method. Refer to <a href="docs_20060124_gschem_ug_installing_gschem.html" class="wikilink2" title="docs:20060124:gschem_ug:installing_gschem">Installing gschem</a> for more details.</div>
-</li>
-<li class="level1"><div class="li"> <strong>$HOME/.gEDA/gschemrc</strong>: The per-user initialization file for <strong>gschem</strong>. Created by the user under the userâ??s home directory. Settings placed in this file will override settings in the system-gschemrc file. Users should put settings in this file they want to apply to all of their sessions, such as (to change the default black background color scheme to a light background color scheme):</div>
-</li>
-</ul>
-
-<p>
-<pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">; Load up a color scheme
-(load (build-path geda-rc-path "gschem-lightbg")) ; light background</font></pre>
-</p>
-<ul>
-<li class="level1"><div class="li"> <strong>â??pwdâ??/gschemrc</strong>: The per-project initialization file for <strong>gschem</strong>. Created by the user in the userâ??s project directory. Settings placed in this file will override settings in both the system-gschemrc file and the $HOME/.gEDA/gschemrc file. Users should put settings in this file they want to apply to this particular project, such as (to autonumber reference designators when components are placed on the schematic):</div>
-</li>
-</ul>
-
-<p>
-<pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">; Comment in this scheme code if you want automatic numbering when
-; placing new component and copying components
-;
-(load (string-append gedadata "/scheme/auto-uref.scm"))
-(add-hook! add-component-hook auto-uref)</font></pre>
-</p>
-<ul>
-<li class="level1"><div class="li"> <strong>system-gafrc</strong>: The system-wide initialization file for gEDA/gaf applications (includes <strong>gschem</strong>, <strong>gnetlist</strong>). Installed in the {binary-install-path}/share/gEDA/system-gafrc file, it is required for <strong>gschem</strong> to run. Users should not modify this file, but should override the settings in this file by creating their own $HOME/.gEDA/gafrc file and/or â??pwdâ??/gafrc file and putting the new settings in those files. The {binary-install-path} directory is where your gEDA/gaf executables were installed, including <strong>gschem</strong>. Depends on your install method. Refer to <a href="docs_20060124_gschem_ug_installing_gschem.html" class="wikilink2" title="docs:20060124:gschem_ug:installing_gschem">Installing gschem</a> for more details.</div>
-</li>
-<li class="level1"><div class="li"> <strong>$HOME/.gEDA/gafrc</strong>: The per-user initialization file for gEDA/gaf applications. Created by the user under the userâ??s home directory. Settings placed in this file will override settings in the system-gafrc file. Users should put settings in this file they want to apply to all of their sessions. </div>
-</li>
-<li class="level1"><div class="li"> <strong>â??pwdâ??/gafrc</strong>: The per-project initialization file for the gEDA/gaf applications. Created by the user in the userâ??s project directory. Settings placed in this file will override settings in both the system-gafrc file and the $HOME/.gEDA/gafrc file. Users should put settings in this file they want to apply to this particular project. Settings such as the <strong>component-library</strong> or <strong>source-library</strong> keywords go into this file.</div>
-</li>
-<li class="level1"><div class="li"> <strong>gschem-gtkrc</strong>: Installed in the {binary-install-path}/share/gEDA/gschem-gtkrc file. Used to define the font for all gtk+ widgets in <strong>gschem</strong>.</div>
-</li>
-</ul>
-
-<p>
- A few comments about changing the files:
-</p>
-<ul>
-<li class="level1"><div class="li"> Donâ??t break any guile syntax rules. Doing so will cause the scheme interpreter (guile) to stop interpreting.</div>
-</li>
-<li class="level1"><div class="li"> To add a setting to the $HOME/.gEDA/gschemrc file (or to the â??pwdâ??/gschemrc file), copy the settingâ??s text from the {binary-install-directory}/share/gEDA/system-gschemrc file to the $HOME/.gEDA/gschemrc file (or the â??pwdâ??/gschemrc file) and make the setting change there.</div>
-</li>
-<li class="level1"><div class="li"> To add a setting to the $HOME/.gEDA/gafrc file (or the â??pwdâ??/gafrc file), copy the relevant settingâ??s text from the {binary-install-directory}/share/gEDA/system-gafrc file to the $HOME/.gEDA/gafrc file (or the â??pwdâ??/gafrc file) and make the setting change there.</div>
-</li>
-<li class="level1"><div class="li"> Keywords/defaults always override what came before, with the exception of cumulative keywords (like component-library).</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Configuring gschem" [17747-23531] -->
-<h2><a name="gschemrc" id="gschemrc">gschemrc</a></h2>
-<div class="level2">
-
-<p>
-The {binary-install-path}/share/gEDA/system-gschemrc file is well commented. Read this file for more details on the settings available.<br/>
- Some of the settings appropriate for override (by placing in either the userâ??s $HOME/gschemrc file or the projectâ??s â??pwdâ??/gschemrc file) are:
-</p>
-
-</div>
-<!-- SECTION "gschemrc" [23532-23833] -->
-<h2><a name="gafrc" id="gafrc">gafrc</a></h2>
-<div class="level2">
-
-<p>
-The {binary-install-path}/share/gEDA/system-gafrc file is well commented. Read this file for more details on the settings available.<br/>
- Some of the settings appropriate for override (by placing in either the userâ??s $HOME/gafrc file or the projectâ??s â??pwdâ??/gafrc file) are:
-</p>
-
-</div>
-<!-- SECTION "gafrc" [23834-24123] -->
-<h1><a name="running_gschem" id="running_gschem">Running gschem</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "Running gschem" [24124-24153] -->
-<h2><a name="confirming_gschem_is_installed" id="confirming_gschem_is_installed">Confirming gschem is installed</a></h2>
-<div class="level2">
-
-<p>
-You should determine if <strong>gschem</strong> has been correctly installed on your Linux computer.<br/>
- Log into your Linux account, and launch your favorite interactive shell. The different Linux distributions will usually offer more than one interactive shell such as xterm, gnome-term, konsole, etc.<br/>
- You will see a shell prompt, which will depend on your Linux distribution and on your selection of interactive shell. It is common practice in Linux documentation to refer to the userâ??s interactive login shell prompt as â??<strong>%</strong>â??, and to refer to the superuserâ??s (i.e., user â??rootâ??) interactive login shell prompt as â??<strong>#</strong>â??.<br/>
- At the shell prompt, enter the following commands to determine if <strong>gschem</strong> is installed:
-</p>
-
-<p>
-<pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">% <strong>echo $PATH</strong>
-<strong>/usr/local/gEDA-20060124/bin</strong>:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/home/<strong>gEDA</strong>/bin
-% <strong>which gschem</strong>
-/usr/local/gEDA-20060124/bin/gschem
-% <strong>ldd /usr/local/gEDA-20060124/bin/gschem</strong>
- linux-gate.so.1 => (0x00345000)
- libgeda.so.25 => /usr/local/gEDA-20060124/lib/libgeda.so.25 (0x00d7d000)
- libguile.so.12 => /usr/lib/libguile.so.12 (0x00588000)
- libguile-ltdl.so.1 => /usr/lib/libguile-ltdl.so.1 (0x00b62000)
- libqthreads.so.12 => /usr/lib/libqthreads.so.12 (0x009f7000)
- libpthread.so.0 => /lib/libpthread.so.0 (0x006d4000)
- libcrypt.so.1 => /lib/libcrypt.so.1 (0x03266000)
- libgdk-x11-2.0.so.0 => /usr/lib/libgdk-x11-2.0.so.0 (0x00c10000)
- libgdk_pixbuf-2.0.so.0 => /usr/lib/libgdk_pixbuf-2.0.so.0 (0x006ac000)
- libm.so.6 => /lib/libm.so.6 (0x008df000)
- libpangoxft-1.0.so.0 => /usr/lib/libpangoxft-1.0.so.0 (0x003e7000)
- libpangox-1.0.so.0 => /usr/lib/libpangox-1.0.so.0 (0x00a57000)
- libpango-1.0.so.0 => /usr/lib/libpango-1.0.so.0 (0x00bd8000)
- libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0x00a01000)
- libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0x009fb000)
- libdl.so.2 => /lib/libdl.so.2 (0x00906000)
- libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x0448e000)
- libgtk-x11-2.0.so.0 => /usr/lib/libgtk-x11-2.0.so.0 (0x06a81000)
- libatk-1.0.so.0 => /usr/lib/libatk-1.0.so.0 (0x00c96000)
- libSM.so.6 => /usr/X11R6/lib/libSM.so.6 (0x00d4f000)
- libICE.so.6 => /usr/X11R6/lib/libICE.so.6 (0x00d33000)
- libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00921000)
- libc.so.6 => /lib/libc.so.6 (0x007b4000)
- /lib/ld-linux.so.2 (0x00796000)
- libXrandr.so.2 => /usr/X11R6/lib/libXrandr.so.2 (0x00bac000)
- libXi.so.6 => /usr/X11R6/lib/libXi.so.6 (0x00cca000)
- libXinerama.so.1 => /usr/X11R6/lib/libXinerama.so.1 (0x00bb2000)
- libXft.so.2 => /usr/X11R6/lib/libXft.so.2 (0x00ad1000)
- libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x00af8000)
- libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0x00111000)
- libXfixes.so.3 => /usr/X11R6/lib/libXfixes.so.3 (0x00d0d000)
- libXcursor.so.1 => /usr/X11R6/lib/libXcursor.so.1 (0x00bcc000)
- libXrender.so.1 => /usr/X11R6/lib/libXrender.so.1 (0x00ba2000)
- libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x00a82000)
- libpangoft2-1.0.so.0 => /usr/lib/libpangoft2-1.0.so.0 (0x05362000)
- libexpat.so.0 => /usr/lib/libexpat.so.0 (0x0068b000)
- libz.so.1 => /usr/lib/libz.so.1 (0x0090c000)</font></pre>
-</p>
-
-<p>
-The <strong>echo $PATH</strong> command displays the userâ??s current setting for the <strong>PATH</strong> environment variable. In the above example for a Fedora Core 4 installation, user <strong>gEDA</strong> executed the command and determined that the <strong>PATH</strong> included the /usr/local/gEDA-20060124/bin directory (this will differ depending on where you put the gEDA Tools Suite executables). If you installed from the gEDA Tools Suite CD-ROM (the most common method of installing the gEDA tools), as the last step of the installation wizzard you were prompted to:
-</p>
-<ol>
-<li class="level1"><div class="li"> Set your $PATH environment variable to {the directory in which the install wizzard installed gEDAâ??s executables}</div>
-</li>
-<li class="level1"><div class="li"> Set your $LD_LIBRARY_PATH environment variable to {the directory in which the install wizzard installed gEDAâ??s libraries}</div>
-</li>
-</ol>
-
-<p>
- The <strong>which</strong> command displays the full path of a commandâ??s executable, searching for the command on the userâ??s list of directories, as defined in the <strong>PATH</strong> environment variable. In this case, it will return the full path to the <strong>gschem</strong> executable if it is on the userâ??s <strong>PATH</strong>. If this command does not return the full path to the <strong>gschem</strong> executable, make sure your <strong>PATH</strong> environment variable has been properly set.
-</p>
-
-<p>
-The <strong>ldd</strong> command displays shared libraries required by a program. All of the requested libraries must be found for <strong>gschem</strong> to run. Donâ??t be intimidated by the long list of libraries, this is common for mature Linux applications. If we had not received this output (or something very similar), we would have to check on our setting for the <strong>LD_LIBRARY_PATH</strong> environment variable.
-</p>
-
-<p>
-And of course, there is always attempting to just run <strong>gschem</strong> as follows: <pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">% <strong>gschem -h</strong>
-Usage: gschem [OPTIONS] schematic_filename1 ... schematic_filenameN
- -q Quiet mode
- -v Verbose mode on
- -r filename Rc filename
- -s filename Script (guile) filename
- -o filename Output filename (for printing)
- -p Automatically place the window
- -t Print stroke information
- -h Help; this message</font></pre>
-</p>
-
-<p>
-where we displayed the <strong>gschem</strong> help.
-</p>
-
-<p>
-If these commands do not return the expected results, then most likely the gEDA tools are not installed properly. Please see the appropriate INSTALL docs (which came with the gEDA distribution) for more info on installing the gEDA tools. If you installed from the gEDA Tools Suite CD-ROM, read the INSTALL document on the CD-ROM first.<br/>
-
-</p>
-
-</div>
-<!-- SECTION "Confirming gschem is installed" [24154-29859] -->
-<h2><a name="the_shell_prompt" id="the_shell_prompt">The Shell Prompt</a></h2>
-<div class="level2">
-<table class="inline">
- <tr>
- <td> <a href="_detail/geda_terminal_screenshot_001.html" class="media" title="geda:terminal_screenshot_001.jpg"><img src="_media/geda_terminal_screenshot_001.jpg" class="media" title="terminal_screenshot_001.jpg" alt="terminal_screenshot_001.jpg" /></a> </td>
- </tr>
- <tr>
- <td> Figure 1 – gnome-terminal </td>
- </tr>
-</table>
-
-<p>
- You launch <strong>gschem</strong> from your favorite shell prompt (in this case, gnome-terminal on Fedora Core 4).<br/>
- There are several command-line switches:
-</p>
-<ul>
-<li class="level1"><div class="li"> <strong>-q</strong> – Quiet mode<br/>
- Turns on â??quiet modeâ??. Output (i.e., stdout and stderr) is not generated to the shell. Useful if calling <strong>gschem</strong> from a script (e.g., bash, sh, csh, etc.) to perform batch operations such as printing a large number of schematics or symbols.</div>
-</li>
-<li class="level1"><div class="li"> <strong>-v</strong> – Verbose mode ON<br/>
- Generate verbose information. Not used very much in <strong>gschem</strong>.</div>
-</li>
-<li class="level1"><div class="li"> <strong>-r filename</strong> – Process additional configuration settings from <strong>filename</strong><br/>
- <strong>filename</strong> is a file containing settings of the form found in either system-gschemrc or system-gafrc<br/>
- In addition to the following files, <strong>gschem</strong> will process <strong>filename</strong> for additional configuration settings:<br/>
- * {binary-install-path}/share/gEDA/system-gschemrc<br/>
- * $HOME/gschemrc<br/>
- * â??pwdâ??/gschemrc<br/>
- * {binary-install-path}/share/gEDA/system-gafrc<br/>
- * $HOME/gafrc<br/>
- * â??pwdâ??/gafrc</div>
-</li>
-<li class="level1"><div class="li"> <strong>-s filename</strong> – Process <strong>filename</strong> as a guile script<br/>
- The name of a script file (written in guile) for <strong>gschem</strong> to process.<br/>
- Refer to <a href="docs_20060124_gschem_ug_app_b.html" class="wikilink2" title="docs:20060124:gschem_ug:app_b">Appendix B -- Printing Schematics and Symbols</a> and <a href="docs_20060124_gschem_ug_app_c.html" class="wikilink2" title="docs:20060124:gschem_ug:app_c">Appendix C -- Writing guile Scripts</a> for more details.<br/>
- For example, in your $HOME/geda-sources/gedagaf/{gEDA Tools Suite version}/scripts/ directory is the <strong>print.scm</strong> file, a template script file directing <strong>gschem</strong> to generate a PostScript file of a schematic appropriate for printing. This <strong>print.scm</strong> file works as is, but you may want to customize it for your own needs. To print the schematic_1.sch schematic to the schematic_1.ps PostScript file from within a bash script, you would enter: <code>gschem -q -p -o schematic_1.ps -s print.scm schematic_1.sch</code><br/>
- Then, simply use your favorite printing solution to print the file, such as: <code>lp schematic_1.ps</code><br/>
- to a PostScript printer.</div>
-</li>
-<li class="level1"><div class="li"> <strong>-o filename</strong> – Output <strong>filename</strong> (e.g., for printing)<br/>
- Specify the output filename. For example, as used to specify the Postscript filename in the example above.</div>
-</li>
-<li class="level1"><div class="li"> <strong>-p</strong> – Automatically place the window<br/>
- Donâ??t wait for the windowmanager to place the window.<br/>
- When a new window is opened, some window managers display the bounding box of the window and wait for the user to place the window manually. The "-pâ?? option avoids that, letting the window manager decide where to put the new window.</div>
-</li>
-<li class="level1"><div class="li"> <strong>-t</strong> – Print stroke information<br/>
- </div>
-</li>
-<li class="level1"><div class="li"> <strong>-h</strong> – Help<br/>
- Generate a short usage printout.</div>
-</li>
-</ul>
-
-<p>
- Running <strong>gschem</strong> is straightforward once you have installed it on your GNU/Linux system.<br/>
- Although <strong>gschem</strong> is a <acronym title="Graphical User Interface">GUI</acronym> application, <strong>gschem</strong> is meant to be launched from the command-line, as it takes command-line arguements (see Figure 1 above).<br/>
- To open an empty schematic, run: <code><strong>% gschem</strong></code><br/>
-
-</p>
-
-<p>
-To open a specific schematic, run: <code><strong>% gschem schematic_name.sch</strong></code><br/>
-
-</p>
-
-<p>
-To open a list of schematics, run: <code><strong>% gschem schematic_1.sch schematic_2.sch, schematic_3.sch …</strong></code><br/>
- or use wildcards to specify multiple filenames: <code><strong>% gschem schematic_*.sch</strong></code>
-</p>
-
-<p>
-As operations are performed in the <strong>gschem</strong> <a href="docs_20060124_gschem_ug_the_main_window.html" class="wikilink2" title="docs:20060124:gschem_ug:the_main_window">Main Window</a> the <strong>gschem</strong> <a href="docs_20060124_gschem_ug_the_status_window.html" class="wikilink2" title="docs:20060124:gschem_ug:the_status_window">Status Window</a> continues to output information, and the shell promptâ??s window continues to output information, consisting of:
-</p>
-<ul>
-<li class="level1"><div class="li"> …</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "The Shell Prompt" [29860-33394] -->
-<h2><a name="backups" id="backups">Backups</a></h2>
-<div class="level2">
-
-<p>
-There are two basic mechanisms in <strong>gschem</strong> for backing up schematics and symbols, classic Linux backups and incremental backups.
-</p>
-
-</div>
-<!-- SECTION "Backups" [33395-33546] -->
-<h3><a name="classic_linux_backups" id="classic_linux_backups">Classic Linux backups</a></h3>
-<div class="level3">
-
-<p>
-While creating and/or editing schematic file(s) or symbol file(s), snapshots are triggered by the <strong>autosave</strong> interval setting in the {binary-install-path}/share/gEDA/system-gschemrc file (see <a href="#relevant_configuration_settings" title="geda:gschem_ug ↵" class="wikilink1">Relevant configuration settings</a> below). If the file has not been manually saved, and the interval expires (current default 2 minutes), the snapshot is saved the next time a change is made in the <strong>gschem</strong> main window (to either a schematic or to a symbol). The interval timer starts again as soon as the snapshot file(s) have been written, and once the timer expires the next change to the main window will trigger the snapshot to be written.<br/>
- This snapshot includes all work up to, but not including, the last operation performed in the <strong>gschem</strong> main window. This is to allow for easier recovery from a crash that may have been caused by the last operation.<br/>
- When <strong>gschem</strong> exits normally, the snapshot file(s) are deleted. So, if <strong>gschem</strong> were to crash, or not terminate normally for some reason (e.g., power failure, soda → keyboard, etc.), the shapshot file(s) would be found the next time <strong>gschem</strong> opened the file(s). <strong>gschem</strong> will display the following warning message when it finds a snapshot file associated with the schematic file(s) or symbol file(s) it opens: <pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">WARNING: Found and autosave backup file:
- {full path to autosave file}
-
-The backup copy is newer than the schematic, so it seems you
-should load it instead of the original fil.
-Gschem usually makes backup copies automatically, and this
-situation happens when it crashed or it was forced to exit
-abruptely.
-
-If you load the original file, the backup file will be overwritten in
-the next autosave timeout and it will be lost.
-
-Do you want to load the backup file?</font></pre>
-</p>
-
-<p>
-The snapshots are saved to a file whose filename is constructed from the original filename (schematic or symbol) as follows:
-</p>
-<ul>
-<li class="level1"><div class="li"> add a "#" to the beginning of the original filename</div>
-</li>
-<li class="level1"><div class="li"> add a "#" to the end</div>
-</li>
-</ul>
-
-<p>
- so that:
-</p>
-<ul>
-<li class="level1"><div class="li"> â??schematic_1.schâ?? becomes "#schematic_1.sch#"</div>
-</li>
-<li class="level1"><div class="li"> â??symbol.symâ?? becomes "#symbol.sym#"</div>
-</li>
-</ul>
-
-<p>
- And yes, the "#" at the front and back of the filename are part of the filename.<br/>
-
-</p>
-
-<p>
-When the user does finally manually save the file, the original file (i.e., the file that was opened) is renamed to "{filename~}" and the latest snapshot file (i.e., "#{filename}#") gets copied as "{filename}". Note that this new "{filename}" file may not contain the latest information as displayed on the <strong>gschem</strong> main window, as the <strong>autosave</strong> interval timer may not have expired since the last change to the schematic/symbol.<br/>
- When the user finally decides to close <strong>gschem</strong>, the latest snapshot file (i.e., "#{filename}#") is saved to the original file (i.e., "{filename}".<br/>
- When you exit <strong>gschem</strong> and are prompted to save any unsaved schematic file(s) or symbol file(s), this constitutes a manual save.
-</p>
-
-</div>
-<!-- SECTION "Classic Linux backups" [33547-36453] -->
-<h3><a name="incremental_backups" id="incremental_backups">Incremental backups</a></h3>
-<div class="level3">
-
-</div>
-<!-- SECTION "Incremental backups" [36454-36487] -->
-<h3><a name="relevant_configuration_settings" id="relevant_configuration_settings">Relevant configuration settings</a></h3>
-<div class="level3">
-
-<p>
-There are the following configuration settings in the {binary-install-path}/share/gEDA/system-gschemrc file that effect backups:
-</p>
-<ul>
-<li class="level1"><div class="li"> <strong>undo-control</strong> : Controls if the undo feature is enabled or not.</div>
-</li>
-<li class="level1"><div class="li"> <strong>undo-levels</strong> : Determines the number of levels of undo. Basically this number decides how many backup schematics are saved.</div>
-</li>
-<li class="level1"><div class="li"> <strong>undo-type</strong> : Controls which kind of undo is used, disk or memory. The default is to use the disk as the storage medium (i.e., after every action the undo information is stored to a new file on disk). The disk mechanism is nice because you get that many backups of the schematic, written to disk as backups, so you should never lose a schematic due to a crash.</div>
-</li>
-<li class="level1"><div class="li"> <strong>autosave</strong> : Controls if a backup copy is made every â??intervalâ?? seconds. Note that a backup copy is only made when you make some change to the schematic, and there were more than â??intervalâ?? seconds from the last autosave. Autosaving will not be allowed if the â??intervalâ?? setting is set to zero.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Relevant configuration settings" [36488-37529] -->
-<h2><a name="on-line_documentation" id="on-line_documentation">On-line documentation</a></h2>
-<div class="level2">
-
-<p>
-For a listing of the various command line flags run â??<strong>gschem -h</strong>â??: <pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">% <strong>gschem -h</strong>
-Usage: gschem [OPTIONS] schematic_filename1 ... schematic_filenameN
- -q Quiet mode
- -v Verbose mode on
- -r filename Rc filename
- -s filename Script (guile) filename
- -o filename Output filename (for printing)
- -p Automatically place the window
- -t Print stroke information
- -h Help; this message</font></pre>
-</p>
-
-<p>
-For a detailed explanation of the command line flags look at the <strong>gschem</strong> man page: <pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">% <strong>man gschem</strong>
-gschem(1) 20031231 gschem(1)
-
-
-
-NAME
- gschem - gEDA/gaf Schematic Capture
-
-SYNOPSIS
- gschem [-q] [-v] [-t] [-r rcfilename] [-s scriptfilename] [-o output-
- filename] [-p] [schematic1 ... schematicN]
-
-DESCRIPTION
- gschem is the schematic capture program which is part gEDA (GPL Elec-
- tronic Design Automation) toolset. This program is used to draw elec-
- tronic schematics. Schematics consist of standard symbols (which are
- either part of a standard library or created by the user) which repre-
- sent the various gates and components. These components are then
- interconnected by nets (wires). Schematics may be printed to a
- PostScript file for printing or further conversion to other output for-
- mats.
-
- gschem is also the symbol creation editor. All the standard methods of
- creating schematics are used in the creation of symbols. There are a
- few special rules when creating symbols, so please refer to the (non-
- existant as of now) symbol creation document.
-
- Please read the official documentation (very minimal at this point) on
- how to use gschem, since this man page just describes the command line
- arguments and a few examples on how to run gschem.
-
-
-OPTIONS
- gschem accepts the following options:
-
- -q Quiet mode on. This mode turns off all warnings/notes/mes-
- sages. (optional)
-
- -v Verbose mode on. This mode gives as much feedback to the user
- as possible. (optional)
-
- -t Print out more information when using mouse strokes. With this
- command line flag and the middle button configured for mouse
- strokes, gschem will output the stroke sequence numbers as the
- user executes strokes. These numbers can be used to define new
- strokes in the system-gschemrc file.
-
- -r filename
- Specify a rc filename. Normally gschem searches for the sys-
- tem-gschemrc, then ~/.gEDA/gschemrc, and finally for a gschemrc
- in the current directory. This options allows the user to
- specify an additional rc file which is read after all the other
- rc files are read. (optional)
-
- -s filename
- Specify a guile script to be executed at startup. (optional)
-
- -o filename
- Specify a filename for postscript output. This command line
- argument is useful when running gschem from a shell script and
- with a guile script. The filename can be changed through the
- print dialog box.
-
- -p Automatically place the window, especially useful if running
- gschem from the command line and generating output.
-
- schematic1 [... schematicN]
- Schematic file to be loaded. Specifing a schematic file is
- optional. If multiple schematic files are specified they are
- read in sequentially and put on seperate pages. It is impor-
- tant that the schematic(s) follow all the options (ie last).
-
-
-EXAMPLES
- These examples assume that you have a schematic called stack_1.sch in
- the current directory
-
- To run gschem and then interact with the program:
-
- ./gschem
-
- To run gschem in interactive mode but load a sample schematic:
-
- ./gschem adders_1.sch
-
- To run gschem and load up all schematics in the current subdirectory:
-
- ./gschem *.sch
-
-
-ENVIRONMENT
- No environment variables are used.
-
-
-AUTHOR
- Ales Hvezda and many others
-
-
-SEE ALSO
- gnetlist(1), gsymcheck(1)
-
-COPYRIGHT
- Copyright © 1999-2004 Ales Hvezda
-
- This document can be freely redistributed according to the terms of the
- GNU General Public License version 2.0
-
-
-
-
-Version December 31st, 2003 gschem(1)</font></pre>
-</p>
-
-</div>
-<!-- SECTION "On-line documentation" [37530-41999] -->
-<h1><a name="electrical_connectivity" id="electrical_connectivity">Electrical Connectivity</a></h1>
-<div class="level1">
-
-<p>
-As you draw schematics you need be aware of what is considered to be electrically connected by the gEDA programs.<br/>
- Nets which are visually connected to other nets are electrically connected. This connection may be endpoint to endpoint or endpoint to midpoint. When a single endpoint to endpoint (net or pin endpoint) connection is drawn, the visual dangling net cue disappears. When an endpoint ends in the middle of another net (or multiple endpoints coming together at a single point) then a circular filled connectivity cue is drawn. You cannot connect a net to the middle of a pin. Nets can only be connected to the endpoints of pins. You cannot connect to a net if that net is not orthogonal (horizontal or vertical). The visual cues are the primary way of telling if nets/pins are connected.<br/>
- Bus are similar to nets with the exception that you cannot connect a net to the endpoint of a bus (only to the middle). If you do try to connect a net to the end of a bus you will see a big red X at the invalid endpoint connection. Buses are still very new so there are still many quirks.<br/>
- You can label nets by using the <code>label=</code> attribute. Do not attach more than one <code>label=</code> to a net. You only need to attach the <code>label=</code> attribute to one net segment. Different nets (i.e. multiple net segments which arenâ??t connected together) which have the same attribute <code>label=</code> attached to them are also considered electrically connected. You will not get any indication of this connection by <strong>gschem</strong>, but the netlister (<strong>gnetlist</strong>) considers nets with the same <code>label=</code> attribute electrically connected. The naming convention for buses has not been formalized yet.
-</p>
-
-</div>
-<!-- SECTION "Electrical Connectivity" [42000-43716] -->
-<h1><a name="components_symbols_objects_attributes" id="components_symbols_objects_attributes">Components & Symbols & Objects & Attributes</a></h1>
-<div class="level1">
-
-<p>
-There is a hierarchical association between components, symbols, objects, and attributes.
-</p>
-
-</div>
-<!-- SECTION "Components & Symbols & Objects & Attributes" [43717-43865] -->
-<h2><a name="components" id="components">Components</a></h2>
-<div class="level2">
-
-<p>
-A component is the instantiation of a specific symbol, as placed on the schematic. When discussing a schematic you refer to <em class="u">components</em> on the schematic, not <em class="u">symbols</em> on the schematic. Think of symbols as being <em class="u">conceptual</em>, and components as being <em class="u">concrete</em>.<br/>
- The component consists of a graphic representation and the attributes describing the componentâ??s features.<br/>
- The component inherits all of the attributes defined in the symbol. Certain attributes in the symbol:
-</p>
-<ul>
-<li class="level1"><div class="li"> those explicitly defined as visible unattached attributes (see <a href="#attributes" title="geda:gschem_ug ↵" class="wikilink1">Attributes</a>)</div>
-</li>
-<li class="level1"><div class="li"> specific attributes such as <code>symversion</code> and <code>refdes</code></div>
-</li>
-</ul>
-
-<p>
- are promoted to the component level for manipulation by the circuit designer. These attributes may optionally be exposed (made viewable) with the componentâ??s graphic, and their values may be changed.<br/>
- Any attribute not defined in the symbol may be defined in the component. For example, if the symbol does not define the <code>comment</code> attribute, this attribute may be added to the component, perhaps to add a comment for the Bill of Material or Assembly Instructions.<br/>
- Unfortunately, it is difficult to determine a componentâ??s attributes from <strong>gschem</strong> while entering the schematic. You have to place a symbol on the schematic, select the resulting component, and select <strong>Hierarchy | Down Symbol</strong> from the pull-down menus. Then, you have to unhide all attributes with <strong>Edit | Make Inv Text Vis</strong> from the pull-down menus. Then you have to expand your view of the symbol with <strong>View | Extents</strong>. Then, you have to go back to the schematic by selecting <strong>Hierarchy | Up</strong> from the pull-down menus. Then, you have to select <strong>Edit | Edit…</strong> to bring up the â??Edit Attributesâ?? dialog box to determine if any attributes have been added at the component level.
-</p>
-
-</div>
-<!-- SECTION "Components" [43866-45680] -->
-<h2><a name="symbols" id="symbols">Symbols</a></h2>
-<div class="level2">
-
-<p>
-Symbols are just a collection of objects and attributes.<br/>
- The objects have positional significance in the symbol, and define the graphic that is viewed.<br/>
- Attributes may be attached to objects, or they may be attached to the symbol itself (termed as â??unattachedâ?? attributes, because they are not attached to an object).
-</p>
-
-</div>
-<!-- SECTION "Symbols" [45681-46022] -->
-<h2><a name="objects" id="objects">Objects</a></h2>
-<div class="level2">
-
-<p>
-The following are objects:
-</p>
-<ul>
-<li class="level1"><div class="li"> Line</div>
-</li>
-<li class="level1"><div class="li"> Box</div>
-</li>
-<li class="level1"><div class="li"> Circle</div>
-</li>
-<li class="level1"><div class="li"> Arc</div>
-</li>
-<li class="level1"><div class="li"> Pin</div>
-</li>
-<li class="level1"><div class="li"> Picture</div>
-</li>
-<li class="level1"><div class="li"> Text</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Objects" [46023-46136] -->
-<h2><a name="attributes" id="attributes">Attributes</a></h2>
-<div class="level2">
-
-<p>
-An attribute is text which is in the form <code>name=value</code> (there are no spaces to the left or right of the name,value pair). An attribute can be either attached to an object or unattached. Attributes are used extensively in the gEDA project to convey information (e.g., device name, pin numbers, hidden nets, and unit reference numbers). Check <a href="geda_master_attributes_list.html" class="wikilink1" title="geda:master_attributes_list">gEDA/gaf Master Attribute Document</a> for a complete list of attributes.<br/>
- There are three kinds of attributes:
-</p>
-<ul>
-<li class="level1"><div class="li"> <strong>Attached attributes:</strong> These are attributes which take on the standard form and are attached to some object (pin, net, component, or box etc…) to associate a value with the attribute. For example: a pin number associated with a pin. <span class="hilited">These attributes are usually yellow in color.</span></div>
-</li>
-<li class="level1"><div class="li"> <strong>Unattached attributes:</strong> These are attributes which take on the standard form, but are not attached to any object and usually convey some information which is global in nature. For example: a <code>device=</code> attribute (which lives inside symbols) and specifies what device the entire symbol represents. These attributes are also known as floating or toplevel attributes.</div>
-</li>
-<li class="level1"><div class="li"> <strong>Promoted attributes:</strong> These are unattached attributes in the symbolâ??s definition that get turned into attached attributes in the componentâ??s definition when the symbol is instantiated as a component when placed in the schematic. If you place an unattached visible attribute inside a symbol and then instantiate that symbol, then that unattached attribute gets â??promotedâ??; that is, it becomes an attached attribute. This mechanism of attribute reattachement (from within a symbol) is known as attribute promotion.</div>
-</li>
-</ul>
-
-<p>
- There are some gotchas about attribute promotion:
-</p>
-<ul>
-<li class="level1"><div class="li"> Promotion <strong>only</strong> happens when the symbol is first placed. That means that if you place a symbol (e.g., sym1) and then change it on disk (by adding or removing new unattached attributes), existing sym1â??s will not reflect these new unattached attributes (i.e., they wonâ??t get promoted) in any schematic.</div>
-</li>
-<li class="level1"><div class="li"> The <code>device=</code> attribute is not promoted.</div>
-</li>
-<li class="level1"><div class="li"> Invisible attributes are not promoted by default. If you add an unattached attribute (e.g., numslots=#) and make it invisible, it will not be promoted.</div>
-</li>
-</ul>
-
-<p>
- Now, in order to make everybody happy, this attribute promotion behavior is configurable.<br/>
- The system-gschemrc file defines:
-</p>
-<pre class="code lisp"><span class="br0">(</span>attribute-promotion <span class="st0">"enabled"</span><span class="br0">)</span></pre>
-<p>
-which enables attribute promotion.<br/>
- If you override the system-gschemrcâ??s default promote-invisible setting by adding:
-</p>
-<pre class="code lisp"><span class="br0">(</span>promote-invisible <span class="st0">"enabled"</span><span class="br0">)</span></pre>
-<p>
-to either your userâ??s ~/gschemrc or local â??pwdâ??/gschemrc file, invisible unattached attributes will also be promoted <span class="hilited">(and in memory removed)</span>.
-</p>
-
-<p>
-However, if you do this, component slotting will break because <strong>gschem</strong> expects certain unattached attributes inside the symbol <span class="hilited">(in memory even though they are invisible)</span>.<br/>
- So you can add:
-</p>
-<pre class="code lisp"><span class="br0">(</span>keep-invisible <span class="st0">"enabled"</span><span class="br0">)</span></pre>
-<p>
-to either your userâ??s ~/gschemrc or local â??pwdâ??/gschemrc file. This is enabled by default, but has no effect unless promote-invisible is enabled.
-</p>
-
-<p>
-So, to summarize, attribute promotion takes unattached attributes inside symbols and attaches them to the outside of a placed symbol. Three *rc keywords control this behavior: attribute-promotion, promote-invisible, and keep-invisible.
-</p>
-
-</div>
-<!-- SECTION "Attributes" [46137-49509] -->
-<h1><a name="the_main_window" id="the_main_window">The Main Window</a></h1>
-<div class="level1">
-<table class="inline">
- <tr>
- <td> <a href="_detail/geda_gschem_screenshot_001.html" class="media" title="geda:gschem_screenshot_001.jpg"><img src="_media/geda_gschem_screenshot_001.jpg" class="media" title="gschem_screenshot_001.jpg" alt="gschem_screenshot_001.jpg" /></a> </td>
- </tr>
-</table>
-
-<p>
- There are several ways to interact with <strong>gschem</strong>. <strong>gschem</strong> requires a keyboard and mouse. There are three ways to initiate an operation or command:
-</p>
-<ul>
-<li class="level1"><div class="li"> Using the mouse to select the operation off a menu</div>
-</li>
-<li class="level1"><div class="li"> Typing the keyboard shortcut(s).</div>
-</li>
-<li class="level1"><div class="li"> Draw the appropriate stroke (if stroke support is enabled)</div>
-</li>
-</ul>
-
-<p>
- To make usage matters more confusing, selecting an operation off of the menus behaves slightly differently than typing the keyboard shortcut. Most of the operations operate on the currently selected object(s), hence you need to select the object first before manipulating them. The menu selected operations usually require some more input (usually a mouse click) after they are picked off of the menu. The keyboard shortcut operations take that required input as the current mouse position. This saves an extra click since you can position the mouse at the right place, type in the shortcut(s), and the command then executes. Note, you can change this so that both menu and shortcut behavior is exactly the same. See the section on the resource file for more info on how to configure this.<br/>
- Most of the interaction with <strong>gschem</strong> is fairly mode oriented (similar to the great text editor vi). If you select operations off of the menu, then you are placed into the corresponding mode (like copy or move mode). You must then select an anchor point (or whatever the appropriate point is) to continue the operation. Most of the commands off of the menu expect the objects to be already selected. Some of the modes persist after being execute while other immediately return you into select mode (the default mode).<br/>
- The shortcuts are also mode like in nature. Most of the default shortcuts are for the various commands are not single keystrokes. There are a few which are single keystrokes (like zoom in: `zâ?? or pan: `xâ??), but most are typically two keystrokes long. As examples, to execute File/Save you would type `fâ?? and `sâ?? (without the quotes) or Add/Line is `aâ?? and `lâ??. You can get a listing of the shortcuts by picking Help/Hotkeys. You can also see the hotkey assignments in the pulldown menus as well. The shortcuts are defined in the resource files (<strong>system-gschemrc</strong>, <strong>/.gEDA/gschemrc</strong>, or <strong>`pwd`/gschemrc</strong>). See the section on the resource file for more info.<br/>
- The mouse button actions in <strong>gschem</strong> are mostly configurable. The first mouse button is always used to select objects or pick points. This button is not configurable. The second mouse button is either a copy/move action (when held down over an object), a repeat last command or used to draw a stroke to execute a command. The third mouse button is either a mouse pan (when held down as the mouse is moved) or a popup menu. The behavior of the second and third mouse buttons is controlled through the resource file (see the section below for more info).
-</p>
-
-</div>
-<!-- SECTION "The Main Window" [49510-52423] -->
-<h1><a name="the_status_window" id="the_status_window">The Status Window</a></h1>
-<div class="level1">
-<table class="inline">
- <tr>
- <td> <a href="_detail/geda_status_screenshot.html" class="media" title="geda:status_screenshot.jpg"><img src="_media/geda_status_screenshot.jpg" class="media" title=":geda:status_screenshot.jpg" alt=":geda:status_screenshot.jpg" /></a> </td>
- </tr>
-</table>
-
-<p>
- Add some details about what gets displayed in the status window.
-</p>
-
-</div>
-<!-- SECTION "The Status Window" [52424-52586] -->
-<h1><a name="the_schematic_file" id="the_schematic_file">The Schematic File</a></h1>
-<div class="level1">
-
-<p>
-Schematic files. These files contain components, nets, text, and sometimes primitive objects (like lines, circles, box etc…) Schematics do not contain pins. Schematic filenames should follow this convention: name_#.sch where:
-</p>
-<ul>
-<li class="level1"><div class="li"> name is a text string which describes what this schematic contains.</div>
-</li>
-<li class="level1"><div class="li"> _# is an underscore and a number (like _1, _2, _7, _13, etc…) This number is used to sequence schematic pages in a multiple page schematic.</div>
-</li>
-<li class="level1"><div class="li"> .sch is the schematic extension/suffix. It is important the schematic pages have this extension.</div>
-</li>
-</ul>
-
-<p>
- Schematic files are pure <acronym title="American Standard Code for Information Interchange">ASCII</acronym> and will always be pure <acronym title="American Standard Code for Information Interchange">ASCII</acronym>. gEDA does not support any binary file formats. The file format for schematics is described in the gEDA file formats document.
-</p>
-
-</div>
-<!-- SECTION "The Schematic File" [52587-53356] -->
-<h1><a name="the_symbol_file" id="the_symbol_file">The Symbol File</a></h1>
-<div class="level1">
-
-<p>
-Symbol files. The schematic and symbol file formats are identical. <strong>gschem</strong> (or a text editor) is used to create symbol files as well as schematics. Symbol files contain lines, circles, boxes, arcs, pins, text, and attributes.<br/>
- The naming convention for symbol files is: name-#.sym where:
-</p>
-<ul>
-<li class="level1"><div class="li"> name is a text string which describes what the symbol represents.</div>
-</li>
-<li class="level1"><div class="li"> -# is a dash and a number (like -1, -2 etc…) The number is used to allow for a symbols to have the same name yet different contents. There might be multiple representations for resistors so these symbols should be called: resistor-1.sym, resistor-2.sym, and resistor-3.sym.</div>
-</li>
-<li class="level1"><div class="li"> .sym is the symbol extension/suffix. It is important the symbols have this extension.</div>
-</li>
-</ul>
-
-<p>
- The way of specifying hierarchy is by using the source= attribute. Please see the master attribute document for info on this mechanism.<br/>
- The hierarchy mechanism is still in heavy flux, so there might be some more changes.
-</p>
-
-</div>
-<!-- SECTION "The Symbol File" [53357-54343] -->
-<h1><a name="symbol_libraries" id="symbol_libraries">Symbol Libraries</a></h1>
-<div class="level1">
-
-<p>
-Components are searched for by specifying (component-library "…â??) inside one of the *rc files. See below for more info.
-</p>
-
-</div>
-<!-- SECTION "Symbol Libraries" [54344-54497] -->
-<h1><a name="the_log_file" id="the_log_file">The Log File</a></h1>
-<div class="level1">
-
-<p>
-Log file. This file contains informative, error, warnings etc… messages when <strong>gschem</strong> was run. This file is created in the working directory that <strong>gschem</strong> was started in. This allows the user to preserve log files between independent projects.
-</p>
-
-</div>
-<!-- SECTION "The Log File" [54498-54775] -->
-<h1><a name="grips" id="grips">Grips</a></h1>
-<div class="level1">
-
-<p>
-Grips are a mechanism used in <strong>gschem</strong> to provide an easy way of modifying objects inside schematics. When you select an object, little squares are placed in strategic locations (line end points or circle radius point or corners of a box) which allow you to change the object quickly. Grip support currently exists for lines, nets, pins, buses, circles, and boxes. Arcs do not yet have grips, but will eventually have them.
-</p>
-
-<p>
-Using grips is easy:
-</p>
-<ul>
-<li class="level1"><div class="li"> Select the object you want to change. The grips (the little boxes) will appear.</div>
-</li>
-<li class="level1"><div class="li"> Click and hold the first mouse button inside the box.</div>
-</li>
-<li class="level1"><div class="li"> Move the mouse around till you have the object where you want it</div>
-</li>
-<li class="level1"><div class="li"> Release the mouse button.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Grips" [54776-55485] -->
-<h1><a name="menu_operations" id="menu_operations">Menu Operations</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "Menu Operations" [55486-55515] -->
-<h2><a name="file" id="file">File</a></h2>
-<div class="level2">
-
-<p>
-The <strong>gschem</strong> application is primarily used for the creation of schematic files (i.e., filename.sch) and symbol files (filename.sym).<br/>
- The following operations are related to the manipulation of these files.<br/>
- Note that <strong>gschem</strong> automatically maintains backups of open schematic/symbol files, in the /tmp directory, for the purpose of Undo/Redo. <strong>gschem</strong> cleans up these files when it exits gracefully. If <strong>gschem</strong> does not exit gracefully, the next time you launch <strong>gschem</strong> you will be prompted with a dialog similar to: <pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">WARNING: Found an autosave backup file:
- {filename}
-
- The backup copy is newer than the schematic, so it seems you
- load it instead of the original file.
- gschem usually makes backup copies automatically, and this
- situation happens when it crashed or it was forced to exit
- abruptly.
-
- If you load the original file, the backup file will be overwritten in
- the next autosave timeout and it will be lost.
-
- Do you want to load the backup file?</font></pre>
-</p>
-
-<p>
-The following are available from the <strong>gschem</strong> main windowâ??s menu-bar when you expand <strong>File</strong>:
-</p>
-
-</div>
-<!-- SECTION "File" [55516-56669] -->
-<h3><a name="new_window_fw" id="new_window_fw">New Window (fw)</a></h3>
-<div class="level3">
-
-<p>
-<strong>File | New Window</strong> opens a new window, in addition to any already open windows. Each window is totally separate from the other windows.
-</p>
-
-</div>
-<!-- SECTION "New Window (fw)" [56670-56835] -->
-<h3><a name="new_page_fn" id="new_page_fn">New Page (fn)</a></h3>
-<div class="level3">
-
-<p>
-<strong>File | New Page</strong> opens a new page, in addition to any existing open pages. Usually this page will be named â??untitled_N.schâ??, where N is an incrementing number.
-</p>
-
-</div>
-<!-- SECTION "New Page (fn)" [56836-57023] -->
-<h3><a name="open_page..._fo" id="open_page..._fo">Open Page... (fo)</a></h3>
-<div class="level3">
-
-<p>
-<strong>File | Open Page…</strong> opens an existing page from disk.<br/>
- The â??Open…â?? dialog box pops up providing:
-</p>
-<ul>
-<li class="level1"><div class="li"> Directory navigation aids</div>
-</li>
-<li class="level1"><div class="li"> Filters for restricting the displayed files:</div>
-<ul>
-<li class="level2"><div class="li"> Schematics</div>
-</li>
-<li class="level2"><div class="li"> Symbols</div>
-</li>
-<li class="level2"><div class="li"> Schematics and Symbols</div>
-</li>
-<li class="level2"><div class="li"> All files</div>
-</li>
-</ul>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Open Page... (fo)" [57024-57311] -->
-<h3><a name="close_page_pc" id="close_page_pc">Close Page (pc)</a></h3>
-<div class="level3">
-
-<p>
-<strong>File | Close Page</strong> closes the currently displayed page. This will prompt you to save if you have modified the page.
-</p>
-
-</div>
-<!-- SECTION "Close Page (pc)" [57312-57457] -->
-<h3><a name="revert_page_pr" id="revert_page_pr">Revert Page (pr)</a></h3>
-<div class="level3">
-
-<p>
-<strong>File | Revert Page</strong> closes and reopens the currently displayed page. This will not prompt you to save the current page, but will quickly discard any changes you have made and reopen the saved schematic from disk. Use with caution.
-</p>
-
-</div>
-<!-- SECTION "Revert Page (pr)" [57458-57719] -->
-<h3><a name="save_page_fs" id="save_page_fs">Save Page (fs)</a></h3>
-<div class="level3">
-
-<p>
-<strong>File | Save Page</strong> saves the current page. The current filename is displayed in the <strong>gschem</strong> status-bar.<br/>
- If the pageâ??s filename is â??untitled_N.schâ?? (where N is a integer), then the Save As… dialog box will be displayed, prompting for a new filename.<br/>
- If the pageâ??s filename is NOT â??untitled_N.schâ?? (where N is a integer), then the Save As… dialog box will NOT be displayed, and:
-</p>
-<ul>
-<li class="level1"><div class="li"> the backup file will be created for the previous version, named {filename}~ That is, the "~" (tilde character) is appended to the filename. Any previous backup file is lost.</div>
-</li>
-<li class="level1"><div class="li"> the file will be saved to the current filename.<br/>
-</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Save Page (fs)" [57720-58367] -->
-<h3><a name="save_page_as..._fa" id="save_page_as..._fa">Save Page As... (fa)</a></h3>
-<div class="level3">
-
-<p>
-<strong>File | Save Page As…</strong> opens the Save As.. dialog box.<br/>
- If the current filename is â??untitled_N.schâ??, the Save As… dialog box prompts for a new filename.<br/>
- If the current filename is NOT â??untitled_N.schâ??, the Save As… dialog box prompts for a new filename, filling in the current filename as a default.<br/>
- In either case the filename may be changed, and a new file created when the Save As button is clicked.
-</p>
-
-</div>
-<!-- SECTION "Save Page As... (fa)" [58368-58815] -->
-<h3><a name="save_all_fl_fl" id="save_all_fl_fl">Save All (fl) (fl)</a></h3>
-<div class="level3">
-
-<p>
-<strong>File | Save All</strong> unconditionally saves all schematics loaded in memory.
-</p>
-
-</div>
-<!-- SECTION "Save All (fl) (fl)" [58816-58920] -->
-<h3><a name="print..._fp" id="print..._fp">Print... (fp)</a></h3>
-<div class="level3">
-
-<p>
-<strong>File | Print…</strong> brings up the Print… dialog box.<br/>
- The following may be selected:
-</p>
-<ul>
-<li class="level1"><div class="li"> Filename (if <strong>gschem</strong> has multiple pages loaded, this filename defaults to the page currently displayed).</div>
-</li>
-<li class="level1"><div class="li"> Paper size (that is loaded into your printer).</div>
-</li>
-<li class="level1"><div class="li"> The print type:</div>
-<ul>
-<li class="level2"><div class="li"> Extents with margins – the current page, with margins where the printer doesnâ??t output.</div>
-</li>
-<li class="level2"><div class="li"> Extents no margins – the current page, but without margins where the printer doesnâ??t output. The printer output may be scaled larger than when using â??Entents with marginsâ??, but at the loss along the borders of the schematic.</div>
-</li>
-<li class="level2"><div class="li"> Current window – Scaled to fit the page size, but not optimally.</div>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"> Orientation:</div>
-<ul>
-<li class="level2"><div class="li"> Landscape</div>
-</li>
-<li class="level2"><div class="li"> Portrait</div>
-</li>
-</ul>
-</li>
-</ul>
-
-<p>
- Pressing Print will generate a PostScript file with the filname format of the form {filename}.ps (e.g., printing schematic file First_1.sch would generate First_1.ps).<br/>
- Printing the PostScript file to your printer is distribution dependent:</p>
-<dl>
-<dt><span class='term'> Fedora Core (from the command-line):</span></dt>
-<dd><code>lp First_1.ps</code></dd>
-</dl>
-
-
-</div>
-<!-- SECTION "Print... (fp)" [58921-59967] -->
-<h3><a name="write_png..._fi" id="write_png..._fi">Write PNG... (fi)</a></h3>
-<div class="level3">
-
-<p>
-<strong>File | Write <acronym title="Portable Network Graphics">PNG</acronym>…</strong> brings up the Write <acronym title="Portable Network Graphics">PNG</acronym>… dialog box. Note you must have libgdgeda installed (and any required dependencies) if you want to output images.<br/>
- The dialog box allows you to select:
-</p>
-<ul>
-<li class="level1"><div class="li"> Width x Height:</div>
-<ul>
-<li class="level2"><div class="li"> 320 x 240</div>
-</li>
-<li class="level2"><div class="li"> 640 x 480</div>
-</li>
-<li class="level2"><div class="li"> 800 x 600</div>
-</li>
-<li class="level2"><div class="li"> 1024 x 768</div>
-</li>
-<li class="level2"><div class="li"> 1280 x 960</div>
-</li>
-<li class="level2"><div class="li"> 1600 x 1200</div>
-</li>
-<li class="level2"><div class="li"> 3200 x 2400</div>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"> Filename (if <strong>gschem</strong> has multiple pages loaded, the currently displayed pageâ??s filname is given)</div>
-</li>
-</ul>
-
-<p>
- When the OK button is clicked, a <acronym title="Portable Network Graphics">PNG</acronym> graphic file with a filename of the form {filename}.png is created (e.g., writing a <acronym title="Portable Network Graphics">PNG</acronym> for schematic file First_1.sch will generate a First_1.png file).<br/>
- This file may be used any way a <acronym title="Portable Network Graphics">PNG</acronym> file is used (e.g., web-page, document insertion, image manipulation with the GIMP, etc.).
-</p>
-
-</div>
-<!-- SECTION "Write PNG... (fi)" [59968-60762] -->
-<h3><a name="execute_script..._ft" id="execute_script..._ft">Execute Script... (ft)</a></h3>
-<div class="level3">
-
-<p>
-<strong>File | Execute Script…</strong> …..TBD
-</p>
-
-</div>
-<!-- SECTION "Execute Script... (ft)" [60763-60834] -->
-<h3><a name="close_window_fc" id="close_window_fc">Close Window (fc)</a></h3>
-<div class="level3">
-
-<p>
-<strong>File | Close Window</strong> closes the current window. If there are any modified schematics, the â??There are unsaved schematicsâ?? dialog box will appear. Clicking OK will cause all unsaved schematics to be lost.
-</p>
-
-</div>
-<!-- SECTION "Close Window (fc)" [60835-61073] -->
-<h3><a name="quit_alt-q" id="quit_alt-q">Quit (Alt-q)</a></h3>
-<div class="level3">
-
-<p>
-<strong>File | Quit</strong> closes all opened windows and exits <strong>gschem</strong>. A â??There are unsaved schematicsâ?? dialog box will appear for each window that has unsaved schematics.
-</p>
-
-</div>
-<!-- SECTION "Quit (Alt-q)" [61074-61266] -->
-<h2><a name="edit" id="edit">Edit</a></h2>
-<div class="level2">
-
-<p>
-The following are available from the <strong>gschem</strong> main windowâ??s menu-bar when you expand <strong>Edit</strong>:
-</p>
-
-</div>
-<!-- SECTION "Edit" [61267-61383] -->
-<h3><a name="undo_shift-u" id="undo_shift-u">Undo (shift-u)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Edit | Undo</strong> does exactly that, it undos the last action which changed the schematic.<br/>
- The depth of undo (how many undo steps can be performed) is set in the system-gschemrc file. The default is 10. Simply override this setting by placing the following lines in either your ~/.gEDA/gschemrc file or your local gschemrc file: <pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">; undo-levels number
-;
-; Determines the number of levels of undo. Basically this number decides
-; how many backup schematics are saved on disk.
-;
-(undo-levels 10)</font></pre>
-</p>
-
-<p>
-After every action (including zooming and panning) the schematic is saved to disk (in /tmp). The undo-levels setting determines how many of these temporary files are maintained in the /tmp directory. <strong>gschem</strong> does clean-up after itself when you exit.<br/>
- Should <strong>gschem</strong> crash, the saved files remain in /tmp for disaster recovery. You will be prompted the next time the schematic is opened to recover from the backup.<br/>
-
-</p>
-
-</div>
-<!-- SECTION "Undo (shift-u)" [61384-62342] -->
-<h3><a name="redo_shift-r" id="redo_shift-r">Redo (shift-r)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Edit | Redo</strong> only applies after you have done an <strong>Edit | Undo</strong>. You can undo something and then immediately redo it. However if you do anything in between you will lose the undo info. You can undo and redo to your hearts desire up and down till you reach the max undo levels.<br/>
-
-</p>
-
-</div>
-<!-- SECTION "Redo (shift-r)" [62343-62651] -->
-<h3><a name="select_mode_s" id="select_mode_s">Select Mode (s)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Edit | Select Mode</strong> is the initial mode in which <strong>gschem</strong> starts.<br/>
- When in <strong>Select Mode</strong>, an unlocked object (i.e., component, line, box, circle, …) may be selected by placing the mouse pointer within the outline of the object and single-clicking, or by dragging a box (i.e., holding down the first mouse-button) around the object. Selecting an already selected object will leave the object selected (i.e., you can not unselect an object by single-clicking it). Multiple unlocked objects may be selected by dragging a box around the objects.<br/>
- A locked object may be selected by dragging a box around the object.<br/>
- To de-select all objects, single-click anywhere on the schematic where there is no object.<br/>
- A visible attribute for an unlocked component may be selected by placing the mouse pointer over the componentâ??s visible attribute and single-clicking. Placing the mouse pointer over the unlocked componentâ??s visible attribute and double-clicking will open the edit dialog box appropriate for the attribute.<br/>
- Objects will change color when selected.<br/>
- You stay in <strong>Select Mode</strong> until you select one of the other Modes (e.g., Line, Copy, Move, etc.).<br/>
- Your current Mode is displayed on the status-bar, in the lower-right corner of the <strong>gschem</strong> window.<br/>
- If multiple objects overlap, single-clicking where they overlap will cycle through the objects.<br/>
- If you hold down the SHIFT key and single-click, you can select and deselect multiple objects. Doing this with multiple overlapping objects will cause the selection to cycle among the possible object selections.<br/>
- If you hold down the CONTROL key and single-click, you will toggle the object in and out of the current selection list.<br/>
- If you hold down the SHIFT key while drawing a selection box you will add to the currently selected objects. Objects cannot be removed using the selection box and holding down the SHIFT key.<br/>
- If you hold down the CONTROL key while drawing a selection box then you will toggle any encompassed objects. If an object was selected then it will be unselected and vice versa.<br/>
- If you pick a component, its visible and invisible attributes are selected as well. If you just want to select the object, you must deselect the attributes.<br/>
- The selection mechanisms are not obvious and do require some practice. There are some quirks so please report them as you come across them.
-</p>
-
-</div>
-<!-- SECTION "Select Mode (s)" [62652-65059] -->
-<h3><a name="edit..._ee" id="edit..._ee">Edit... (ee)</a></h3>
-<div class="level3">
-
-<p>
-First, select the object to be edited (i.e., in <strong>Select Mode</strong>).<br/>
- If the object is a component, <strong>Edit | Edit…</strong> then pops up a dialog box that allows you to edit the componentâ??s attributes:
-</p>
-<ul>
-<li class="level1"><div class="li"> Existing attributes (e.g., refdes) are displayed.</div>
-</li>
-<li class="level1"><div class="li"> A drop-down list of pre-defined attributes permits selection, and a edit-box provides association of a value to the attribute.</div>
-</li>
-<li class="level1"><div class="li"> The attributeâ?? name and/or value may be made visible or invisible,</div>
-</li>
-</ul>
-
-<p>
- If the ojbect is a text string, <strong>Edit…</strong> then pops up a dialog box that allows you to modify the text stringâ??s attributes:
-</p>
-<ul>
-<li class="level1"><div class="li"> The text string may be modified. Multiple lines of text may be entered by inserting carriage-returns.</div>
-</li>
-<li class="level1"><div class="li"> The text color may be modified.</div>
-</li>
-<li class="level1"><div class="li"> The text size may be modified.</div>
-</li>
-<li class="level1"><div class="li"> The text alignment:</div>
-<ul>
-<li class="level2"><div class="li"> Lower/middle/upper left</div>
-</li>
-<li class="level2"><div class="li"> Lower/middle/upper middle</div>
-</li>
-<li class="level2"><div class="li"> Lower/middle/upper right</div>
-</li>
-</ul>
-</li>
-</ul>
-
-<p>
- Apply the changes by pressing OK.
-</p>
-
-<p>
-<strong>Notes:</strong><br/>
- If you need to change the attributes to more than just a few components, consider saving your schematics, closing <strong>gschem</strong>, and using the <strong>gattrib</strong> application, the <strong>grenum</strong> application, or the <strong>refdes_renum</strong> application to make the changes.
-</p>
-
-</div>
-<!-- SECTION "Edit... (ee)" [65060-66254] -->
-<h3><a name="edit_text..._ex" id="edit_text..._ex">Edit Text... (ex)</a></h3>
-<div class="level3">
-
-<p>
-First, select the text object to be edited (i.e., in <strong>Select Mode</strong>).<br/>
- <strong>Edit | Edit Text…</strong> allows you to edit just text.<br/>
- <strong>Edit | Edit Text…</strong> then pops up a dialog box that allows you to modify the text stringâ??s attributes:
-</p>
-<ul>
-<li class="level1"><div class="li"> The text string may be modified. Multiple lines of text may be entered by inserting carriage-returns.</div>
-</li>
-<li class="level1"><div class="li"> The text color may be modified.</div>
-</li>
-<li class="level1"><div class="li"> The text size may be modified.</div>
-</li>
-<li class="level1"><div class="li"> The text alignment:</div>
-<ul>
-<li class="level2"><div class="li"> Lower/middle/upper left</div>
-</li>
-<li class="level2"><div class="li"> Lower/middle/upper middle</div>
-</li>
-<li class="level2"><div class="li"> Lower/middle/upper right</div>
-</li>
-</ul>
-</li>
-</ul>
-
-<p>
- Apply the changes by pressing OK.
-</p>
-
-<p>
-<strong>Notes:</strong><br/>
- If you need to change the attributes to more than just a few text strings, consider saving your schematics, closing <strong>gschem</strong>, and using the <strong>gattrib</strong> application, the <strong>grenum</strong> application, or the <strong>refdes_renum</strong> application to make the changes.
-</p>
-
-</div>
-<!-- SECTION "Edit Text... (ex)" [66255-67113] -->
-<h3><a name="copy_mode_ec" id="copy_mode_ec">Copy Mode (ec)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Edit | Copy Mode</strong> allows you to copy (i.e., duplicate) the currently selected objects.<br/>
- To copy the object(s):
-</p>
-<ul>
-<li class="level1"><div class="li"> Select the objects to be copied (i.e., in <strong>Select Mode</strong>)</div>
-</li>
-<li class="level1"><div class="li"> Select <strong>Edit | Copy Mode</strong></div>
-</li>
-<li class="level1"><div class="li"> Observe the status-bar now indicates <strong>Copy Mode</strong></div>
-</li>
-<li class="level1"><div class="li"> Click on the selected component(s) to establish an origin of reference</div>
-</li>
-<li class="level1"><div class="li"> Observe a shadow/outline appears for the selected components that moves with the mouse</div>
-</li>
-<li class="level1"><div class="li"> Place the components where you want them</div>
-</li>
-<li class="level1"><div class="li"> Click to anchor the copied components in place.</div>
-</li>
-</ul>
-
-<p>
- After finishing the copy, you automatically return to <strong>Select Mode</strong>.<br/>
- Holding down the CONTROL key as you move the outline around will constrain the movement to be either horizontal or vertical.<br/>
- To copy objects using the shortcut keys is almost the same as above except that the origin point is selected automatically for you once you hit the copy mode shortcut.<br/>
-
-</p>
-
-</div>
-<!-- SECTION "Copy Mode (ec)" [67114-68038] -->
-<h3><a name="move_mode_em" id="move_mode_em">Move Mode (em)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Edit | Move Mode</strong> allows you to move the currently selected objects.<br/>
- To move the object(s):
-</p>
-<ul>
-<li class="level1"><div class="li"> Select the objects to be moved (i.e., in <strong>Select Mode</strong>)</div>
-</li>
-<li class="level1"><div class="li"> Select <strong>Edit | Move Mode</strong></div>
-</li>
-<li class="level1"><div class="li"> Observe the status-bar now indicates <strong>Move Mode</strong></div>
-</li>
-<li class="level1"><div class="li"> Click on the selected component(s) to establish an origin of reference</div>
-</li>
-<li class="level1"><div class="li"> Observe a shadow/outline appears for the selected components that moves with the mouse</div>
-</li>
-<li class="level1"><div class="li"> Place the components where you want them</div>
-</li>
-<li class="level1"><div class="li"> Click to anchor the moved components in place.</div>
-</li>
-</ul>
-
-<p>
- After finishing the move, you automatically return to <strong>Select Mode</strong>.<br/>
- Holding down the CONTROL key as you move the outline around will constrain the movement to be either horizontal or vertical.<br/>
- To move objects using the shortcut keys is almost the same as above except that the origin point is selected automatically for you once you hit the copy mode shortcut.<br/>
-
-</p>
-
-<p>
-Since version 20060906, there is another way to move object(s):<br/>
-
-</p>
-<ul>
-<li class="level1"><div class="li"> Select the objects to be moved (i.e., in <strong>Select Mode</strong>).<br/>
-</div>
-</li>
-<li class="level1"><div class="li"> Put the mouse pointer on one of the selected objects, then drag the objects and drop them where you want them.<br/>
-</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Move Mode (em)" [68039-69192] -->
-<h3><a name="delete_delete-key" id="delete_delete-key">Delete (Delete-key)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Edit | Delete</strong> allows you to remove objects off of the page.<br/>
- To delete objects:
-</p>
-<ul>
-<li class="level1"><div class="li"> Select the desired object(s) (i.e., in <strong>Select Mode</strong>)</div>
-</li>
-<li class="level1"><div class="li"> Select <strong>Edit | Delete</strong></div>
-</li>
-</ul>
-
-<p>
- The object(s) will be deleted immediately. If you inadvertantly delete a component, you can use Undo to recover.
-</p>
-
-</div>
-<!-- SECTION "Delete (Delete-key)" [69193-69511] -->
-<h3><a name="rotate_90_mode_er" id="rotate_90_mode_er">Rotate 90 Mode (er)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Edit | Rotate 90 Mode</strong> allows you to rotate objects 90 degrees around a pivot/center point.<br/>
- To rotate objects:
-</p>
-<ul>
-<li class="level1"><div class="li"> Select the desired object(s) (i.e., in <strong>Select Mode</strong>)</div>
-</li>
-<li class="level1"><div class="li"> Select <strong>Edit | Rotate 90 Mode</strong></div>
-</li>
-<li class="level1"><div class="li"> Click on the pivot (or center) point of the rotate</div>
-</li>
-</ul>
-
-<p>
- The object(s) will be rotated 90º counter-clockwise immediately. If you inadvertantly rotate a component, you can use Undo to recover.<br/>
- Rotating objects using the shortcut keys is similar to above except that the center point is the last mouse position at which you typed the shortcut.<br/>
-
-</p>
-
-</div>
-<!-- SECTION "Rotate 90 Mode (er)" [69512-70101] -->
-<h3><a name="mirror_mode_ei" id="mirror_mode_ei">Mirror Mode (ei)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Edit | Mirror Mode</strong> allows you to mirror objects horizontally around a pivot point.<br/>
- To mirror objects:
-</p>
-<ul>
-<li class="level1"><div class="li"> Select the desired object(s) (i.e., in <strong>Select Mode</strong>)</div>
-</li>
-<li class="level1"><div class="li"> Select <strong>Edit | Mirror Mode</strong></div>
-</li>
-<li class="level1"><div class="li"> Click on the pivot (or center) point of the mirror</div>
-</li>
-</ul>
-
-<p>
- Mirroring objects using the shortcut keys is similar to above except that the pivot point is the last mouse position at which you typed the shortcut.<br/>
- Objects are mirrored horizontally about the pivot point. If you want to get a vertical mirror then rotate and mirror the object(s) till you get the desired position.<br/>
- Mirroring of embedded components is not supported.
-</p>
-
-</div>
-<!-- SECTION "Mirror Mode (ei)" [70102-70758] -->
-<h3><a name="slot..._e_shift-s" id="slot..._e_shift-s">Slot... (e shift-s)</a></h3>
-<div class="level3">
-
-<p>
-Some physical packages (e.g., the classic 7400 Quad NAND gate) contain more than one logical component (e.g., one of the NAND gates). In <strong>gchem</strong> terminology, each of these logical components is termed a â??slotâ?? (e.g., there would be 4 slots in the 7400 Quad NAND gate). Each slot is associated with specific pins on the physical package.<br/>
- <strong>Edit | Slot…</strong> allows you to change the slot number of a multiple-slot package. The package must support slotting. Refer to the <a href="http://www.geda.seul.org/docs/current/symbols/index.html"; class="urlextern" title="http://www.geda.seul.org/docs/current/symbols/index.html"; rel="nofollow">gEDA/gaf Symbol Creation Document</a> for more details.<br/>
- To change the slot number (i.e., select which package pins are associated with a logical component):
-</p>
-<ul>
-<li class="level1"><div class="li"> Select the desired logical component (i.e., in <strong>Select Mode</strong>)</div>
-</li>
-<li class="level1"><div class="li"> Select <strong>Edit | Slot…</strong></div>
-</li>
-<li class="level1"><div class="li"> Change the â??slot=nâ?? value in the â??Edit slot numberâ?? dialog box</div>
-</li>
-<li class="level1"><div class="li"> Press OK</div>
-</li>
-</ul>
-
-<p>
- Note that selecting the slot on a package often effects the layout of the printed circuit board, as the slot may be on the wrong side of the package for effecient routing of nets. Donâ??t worry, you can always come back and change the slot selection once you start laying out your board and know which slots route best.
-</p>
-
-</div>
-<!-- SECTION "Slot... (e shift-s)" [70759-71975] -->
-<h3><a name="color..._eo" id="color..._eo">Color... (eo)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Edit | Color…</strong> allows you to change the color of any selected object (with the exception of components).<br/>
- To change the color of the currently selected objects:
-</p>
-<ul>
-<li class="level1"><div class="li"> Select the desired object(s) (i.e., in <strong>Select Mode</strong>)</div>
-</li>
-<li class="level1"><div class="li"> Select <strong>Edit | Color…</strong></div>
-</li>
-<li class="level1"><div class="li"> The â??Edit | Color Editâ?? dialog box, with a drop down list for colors, will appear:</div>
-<ul>
-<li class="level2"><div class="li"> 1 | pin | black</div>
-</li>
-<li class="level2"><div class="li"> 2 | net endpoint | red</div>
-</li>
-<li class="level2"><div class="li"> 3 | graphic | green4</div>
-</li>
-<li class="level2"><div class="li"> 4 | net | blue2</div>
-</li>
-<li class="level2"><div class="li"> 5 | attribute | black</div>
-</li>
-<li class="level2"><div class="li"> 6 | logic bubble | DarkCyan</div>
-</li>
-<li class="level2"><div class="li"> 8 | detached attribute | red</div>
-</li>
-<li class="level2"><div class="li"> 9 | text | green4</div>
-</li>
-<li class="level2"><div class="li"> 10 | bus | green2</div>
-</li>
-<li class="level2"><div class="li"> 11 | select | firebrick</div>
-</li>
-<li class="level2"><div class="li"> 12 | bounding box | orange</div>
-</li>
-<li class="level2"><div class="li"> 13 | zoom box | DarkCyan</div>
-</li>
-<li class="level2"><div class="li"> 14 | stroke | grey90</div>
-</li>
-<li class="level2"><div class="li"> 15 | lock | grey40</div>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"> Pick the new color</div>
-</li>
-<li class="level1"><div class="li"> Press Apply</div>
-</li>
-</ul>
-
-<p>
- The color change will take effect once you press Apply.<br/>
- You can leave this dialog box up and select other objects and change their color by pressing Apply.
-</p>
-
-</div>
-<!-- SECTION "Color... (eo)" [71976-72934] -->
-<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">
-
-<p>
-<strong>Edit | Lock</strong> and <strong>Edit | Unlock</strong> allow you to lock/unlock components in a schematic. A locked component cannot be selected by a single click. To select locked component(s), drag a box around the component(s).<br/>
- Locking a component is useful for components such as title blocks, which should not be selectable because there are other objects inside its boundaries. If the titleblock was not locked, and you missed selecting a component by clicking it with the mouse, you would end up selecting the titleblock instead.<br/>
- Locking a component is also useful just to prevent it from being inadvertantly selected.<br/>
- To lock/unlock components:
-</p>
-<ul>
-<li class="level1"><div class="li"> Select the desired object(s) (i.e., in <strong>Select Mode</strong>)</div>
-</li>
-<li class="level1"><div class="li"> Select <strong>Edit | Lock</strong> or <strong>Edit | Unlock</strong></div>
-</li>
-</ul>
-
-<p>
- The locked/unlocked state of components is preserved when <strong>gschem</strong> exits, so components which were locked remain locked the next time the schematic is opened.<br/>
- You can lock and unlock regular objects (e.g., lines, pins, boxes…). This is nice when you are drawing something and an object is in the way. Just lock it, and you will not have to think about it when you click to select other objects. Locking an object is not preserved in the file format, so once you quit <strong>gschem</strong> any locked objects will be unlocked the next time the schematic is opened.<br/>
- Note that if a component is locked, you can not single-click to select a visible attribute, or double-click to select and edit a visible component. First unlock such locked components.
-</p>
-
-</div>
-<!-- SECTION "Lock (el) / Unlock (e shift-l)" [72935-74473] -->
-<h3><a name="line_width_type..._ew" id="line_width_type..._ew">Line Width & Type... (ew)</a></h3>
-<div class="level3">
-
-<p>
-The <strong>Edit | Line Width & Type…</strong> dialog box lets you control the width and type of lines, boxes, circles, and arcs on the schematic/symbol.<br/>
- To change the <strong>Line Width & Type…</strong>:
-</p>
-<ul>
-<li class="level1"><div class="li"> Select the desired object(s) (i.e., in <strong>Select Mode</strong>)</div>
-</li>
-<li class="level1"><div class="li"> Select <strong>Edit | Line Width & Type…</strong></div>
-</li>
-<li class="level1"><div class="li"> The â??Edit Line Width * Typeâ?? dialog box displays</div>
-</li>
-<li class="level1"><div class="li"> Change the following as suites the object:</div>
-<ul>
-<li class="level2"><div class="li"> Line Width</div>
-</li>
-<li class="level2"><div class="li"> Line Type</div>
-</li>
-<li class="level2"><div class="li"> Line Dash Length</div>
-</li>
-<li class="level2"><div class="li"> Line Dash Space</div>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"> Press OK to apply the changes</div>
-</li>
-</ul>
-
-<p>
- Note that if the line width doesnâ??t seem to change, just pick a larger value.
-</p>
-
-</div>
-<!-- SECTION "Line Width & Type... (ew)" [74474-75089] -->
-<h3><a name="fill_type..._ef" id="fill_type..._ef">Fill Type... (ef)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Edit | Fill Type…</strong> is used to fill boxes and circles.<br/>
- To fill a box or circle:
-</p>
-<ul>
-<li class="level1"><div class="li"> Select the box or circle.</div>
-</li>
-<li class="level1"><div class="li"> Select <strong>Edit | Fill Type…</strong>. The â??Edit FIll Typeâ?? dialog box is displayed.</div>
-</li>
-<li class="level1"><div class="li"> Enter:</div>
-<ul>
-<li class="level2"><div class="li"> Fill Type</div>
-</li>
-<li class="level2"><div class="li"> Line Width</div>
-</li>
-<li class="level2"><div class="li"> Angle 1</div>
-</li>
-<li class="level2"><div class="li"> Pitch 1</div>
-</li>
-<li class="level2"><div class="li"> Angle 2</div>
-</li>
-<li class="level2"><div class="li"> Pitch 2</div>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"> Press OK.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Fill Type... (ef)" [75090-75430] -->
-<h3><a name="symbol_translate..._et" id="symbol_translate..._et">Symbol Translate... (et)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Edit | Symbol Translate…</strong> is used when creating a symbol, to translate the symbol to an origin for subsequent placement. The symbol may take an optional offset (in mils), as appropriate to the symbol.<br/>
- To translate the symbol:
-</p>
-<ul>
-<li class="level1"><div class="li"> Open a file for the symbol</div>
-</li>
-<li class="level1"><div class="li"> Set the grid snap spacing to 100 mils (<strong>Options</strong> | <strong>Snap Grid Spacing…</strong>).</div>
-</li>
-<li class="level1"><div class="li"> Toggle the grid ON (<strong>Options</strong> | <strong>Toggle Grid On/Off</strong>)</div>
-</li>
-<li class="level1"><div class="li"> Toggle the grid snap ON (<strong>Options</strong> | <strong>Toggle Snap On/Off</strong>)</div>
-</li>
-<li class="level1"><div class="li"> Zoom as appropriate for the symbolâ??s dimensions</div>
-</li>
-<li class="level1"><div class="li"> Draw the symbol, according to the recommendations in the <a href="http://www.geda.seul.org/docs/current/symbols/index.html"; class="urlextern" title="http://www.geda.seul.org/docs/current/symbols/index.html"; rel="nofollow">gEDA/gaf Symbol Creation Document</a></div>
-</li>
-<li class="level1"><div class="li"> Select <strong>Edit | Symbol Translate…</strong></div>
-</li>
-<li class="level1"><div class="li"> The â??Translateâ?? dialog box is displayed.</div>
-</li>
-<li class="level1"><div class="li"> Enter 0 to translate to the origin, or enter a value (in mils), positive or negative, to offset the symbol from the origin.</div>
-</li>
-<li class="level1"><div class="li"> Press OK to apply</div>
-</li>
-<li class="level1"><div class="li"> Save the symbol to the file</div>
-</li>
-</ul>
-
-<p>
- If you enter a 0, then all the objects will be translated to the origin.<br/>
- If you enter a non-zero offset, this will be applied equally in both the X and the Y directions.<br/>
-
-</p>
-
-</div>
-<!-- SECTION "Symbol Translate... (et)" [75431-76595] -->
-<h3><a name="embed_component_picture_eb" id="embed_component_picture_eb">Embed Component/Picture (eb)</a></h3>
-<div class="level3">
-
-<p>
-<strong>gschem</strong> supports the concept of embedded components and graphics, where all the information necessary to display a component/graphic is placed in the schematic file. <strong>Edit | Embed Component/Picture</strong> causes schematic files to be significantly larger, but it makes it easy to share schematics with other people or archive schematics. You should only embed components when absolutely necessary.<br/>
- To <strong>Embed Component/Picture</strong>:
-</p>
-<ul>
-<li class="level1"><div class="li"> Select the component/picture (in <strong>Select Mode</strong>)</div>
-</li>
-<li class="level1"><div class="li"> Select <strong>Edit | Embed Component/Picture</strong></div>
-</li>
-</ul>
-
-<p>
- Save the schematic. The schematic file will now contain the text strings for the embedded component or embedded graphic.<br/>
- The <strong>Add Component…</strong> dialog box allows you to optionally embed the component.<br/>
- The <strong>Add Picture…</strong> dialog box does NOT allow you to optionally embed the component.<br/>
- You can only embed and unembed components. Also, you cannot embed and then mirror a component (this is a limitation of <strong>gschem</strong> and will eventually be fixed).
-</p>
-
-</div>
-<!-- SECTION "Embed Component/Picture (eb)" [76596-77625] -->
-<h3><a name="unembed_component_picture_eu" id="unembed_component_picture_eu">Unembed Component/Picture (eu)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Edit | Unembed Component/Picture</strong> will move the componentâ??s or graphicâ??s information from the schematic fileâ??s contents and output it to the original fileâ??s path/filename (i.e., the schematic file includes the path/filename information). To <strong>Unembed Component/Picture</strong>:
-</p>
-<ul>
-<li class="level1"><div class="li"> Select the component/picture (in <strong>Select Mode</strong>)</div>
-</li>
-<li class="level1"><div class="li"> Select <strong>Edit | Unembed Component/Picture</strong></div>
-</li>
-</ul>
-
-<p>
- Save the schematic. The schematic file will now NOT contain the text strings for the embedded component or embedded graphic.<br/>
- You can only embed and unembed components.
-</p>
-
-</div>
-<!-- SECTION "Unembed Component/Picture (eu)" [77626-78215] -->
-<h3><a name="update_component_ep" id="update_component_ep">Update Component (ep)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Edit | Update Component</strong> updates a componentâ??s definition.<br/>
- A symbol can be modified from within <strong>gschem</strong> using the following sequence:
-</p>
-<ul>
-<li class="level1"><div class="li"> Select the component for which the symbol should be changed.</div>
-</li>
-<li class="level1"><div class="li"> Select <strong>Hierarchy | Down Symbol</strong>. This takes you to the symbol editor</div>
-</li>
-<li class="level1"><div class="li"> Modify the symbol. This includes modifying the symbolâ??s graphic objects, adding/changing/deleting attributes, and moving objects with respect to the origin</div>
-</li>
-<li class="level1"><div class="li"> Donâ??t forget to <strong>Edit | Symbol Translate</strong></div>
-</li>
-<li class="level1"><div class="li"> Select <strong>File | Save Page</strong> to save the symbol to itâ??s file</div>
-</li>
-<li class="level1"><div class="li"> Select <strong>Hierarchy | Up Symbol</strong>. This returns you to the schematic editor</div>
-</li>
-<li class="level1"><div class="li"> With the component still selected, select <strong>Edit | Update Component</strong> to update the componetâ??s description from the modified symbolâ??s definition</div>
-</li>
-<li class="level1"><div class="li"> Select each component on the schematic(s) made from this symbol, and select <strong>Edit | Update Component</strong></div>
-</li>
-</ul>
-
-<p>
- New components placed on the schematic from this updated symbol will use the new symbol definition.<br/>
- Components placed on the schematic from this symbol will be updated the next time this schematic is opened.<br/>
- The symbolâ??s <code>symversion</code> attribute will automatically be incremented for non-trivial changes when the symbol is saved. When a schematic is opened by <strong>gschem</strong>, all symbols used by the schematic are read from their libraries. The <code>symversion</code> attribute of the symbol read from the library is compared to the <code>symversion</code> attribute of the components in the schematic. If the <code>symversion</code> attributes are different, the <code>symversion</code> attribute is exposed on the schematic for those symbols effected. Note that:
-</p>
-<ul>
-<li class="level1"><div class="li"> This is a â??hintâ?? to the designer to check the symbol.</div>
-</li>
-<li class="level1"><div class="li"> You need to actually open a schematic file with <strong>gschem</strong> for the components to be updated.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Update Component (ep)" [78216-80025] -->
-<h3><a name="show_hide_inv_text_en" id="show_hide_inv_text_en">Show/Hide Inv Text (en)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Edit | Show/Hide Inv Text</strong> is most appropriate when creating or editing symbols, to view or hide the text for all of the symbolâ??s invisible attributes.<br/>
- <a href="#make_inv_text_vis" title="geda:gschem_ug ↵" class="wikilink1">Make Inv Text Vis</a> is most appropriate when adding symbols to schematics, to view the text for the symbolâ??s modifiable invisible attributes.<br/>
- <strong>Edit | Show/Hide Inv Text</strong> toggles between making all invisible text visible and hiding all invisible text. When selected, all objects in the symbol are effected.<br/>
- Visible text always remains visible.<br/>
- A symbol has the following <em class="u">potential</em> attributes :
-</p>
-<ul>
-<li class="level1"><div class="li"> netname</div>
-</li>
-<li class="level1"><div class="li"> refdes</div>
-</li>
-<li class="level1"><div class="li"> slot</div>
-</li>
-<li class="level1"><div class="li"> value</div>
-</li>
-<li class="level1"><div class="li"> net</div>
-</li>
-<li class="level1"><div class="li"> device</div>
-</li>
-<li class="level1"><div class="li"> pinnumber</div>
-</li>
-<li class="level1"><div class="li"> pinseq</div>
-</li>
-<li class="level1"><div class="li"> pintype</div>
-</li>
-<li class="level1"><div class="li"> pinlabel</div>
-</li>
-<li class="level1"><div class="li"> source</div>
-</li>
-<li class="level1"><div class="li"> numslots</div>
-</li>
-<li class="level1"><div class="li"> slotdef</div>
-</li>
-<li class="level1"><div class="li"> graphical</div>
-</li>
-<li class="level1"><div class="li"> footprint</div>
-</li>
-<li class="level1"><div class="li"> description</div>
-</li>
-<li class="level1"><div class="li"> documentation</div>
-</li>
-<li class="level1"><div class="li"> symversion</div>
-</li>
-<li class="level1"><div class="li"> comment</div>
-</li>
-<li class="level1"><div class="li"> file</div>
-</li>
-<li class="level1"><div class="li"> model-name</div>
-</li>
-</ul>
-
-<p>
- Not all attributes need to be used to define a symbol (see the discussion of <a href="docs_20060124_gschem_ug_app_a.html" class="wikilink2" title="docs:20060124:gschem_ug:app_a">Appendix A -- Heavy vs Light Symbol Libraries</a>). The <strong>gschem</strong> default is to define symbols as â??lightâ??, indicating that the symbol includes as few attributes as necessary to describe the symbol. â??lightâ?? symbols depend on the designer attaching additional descriptive attributes to the symbol when the symbol is placed on the schematic. For example: a â??lightâ?? symbol for a resistor might include just the graphic for a resistor, its pin attributes, and the â??refdesâ?? attribute. This describes a resistor. It would be the designerâ??s responsibility, after the resistor has been placed on the schematic, to add the â??valueâ?? and â??footprintâ?? attributes appropriate for the specific resistor in the circuit. A â??heavyâ?? symbol includes more descriptive attributes. Using â??lightâ?? vs. â??heavyâ?? symbols is up to the designer.<br/>
- A symbolâ??s attributes may be flagged as either visible or invisible. Attributes are flagged as invisible to reduce the clutter around a symbol on the schematic.<br/>
- When creating or editing the symbol, and changing a visible attribute to an invisible attribute, the attribute can not be viewed during further editing of the symbol. It becomes difficult to place attribute text. To view both the visible and invisible text, select <strong>Edit | Show/Hide Inv Text</strong>.<br/>
- When a symbol is instantiated on a schematic as a component, only the symbolâ??s visible attributes are promoted to the component. For example: if a resistorâ??s symbol defines â??refdesâ?? as the only visible attribute defined in the symbol, the only attribute that the component contains is the â??refdesâ?? attribute). Those attributes not included in the symbol definition may be added at the schematic level, component-by-component.<br/>
- This operation is useful when drawing/debugging symbols.<br/>
- When hidden text is visible, â??Show Hiddenâ?? will appear on the status-bar in the lower right.
-</p>
-
-</div>
-<!-- SECTION "Show/Hide Inv Text (en)" [80026-82853] -->
-<h3><a name="make_inv_text_vis_ev" id="make_inv_text_vis_ev">Make Inv Text Vis (ev)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Edit | Make Inv Text Vis</strong> is a quick method of making all of a componentâ??s invisible attributes visible. The same effect can be accomplished by double-clicking on the component and marking all of the entries in the Attributes listbox as â??Vis?" (i.e., visible).<br/>
- To <strong>Make Inv Text Vis</strong> for a component:
-</p>
-<ul>
-<li class="level1"><div class="li"> Select the component(s) in <strong>Select Mode</strong></div>
-</li>
-<li class="level1"><div class="li"> Select <strong>Edit | Make Inv Text Vis</strong></div>
-</li>
-</ul>
-
-<p>
- The attributes that had been hidden are displayed.<br/>
- To hide the attributes again, you need to double-click the component to bring up itâ??s â??Edit Attributesâ?? dialog box, and explicitly place a check for each attribute you want hidden.
-</p>
-
-</div>
-<!-- SECTION "Make Inv Text Vis (ev)" [82854-83517] -->
-<h2><a name="buffer" id="buffer">Buffer</a></h2>
-<div class="level2">
-
-<p>
-<strong>gschem</strong> supports 5 copy/cut/paste buffers which are visible across all opened pages and windows.
-</p>
-
-</div>
-<!-- SECTION "Buffer" [83518-83637] -->
-<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">
-
-<p>
-To copy something into a buffer:
-</p>
-<ol>
-<li class="level1"><div class="li"> Select the objects you want to copy.</div>
-</li>
-<li class="level1"><div class="li"> Select Buffer/Copy/Copy into buffer #.</div>
-</li>
-</ol>
-
-</div>
-<!-- SECTION "Copy into 1/2/3/4/5 (yc)" [83638-83790] -->
-<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">
-
-<p>
-Cut is like copy in that it removes the objects from the schematic
-</p>
-
-</div>
-<!-- SECTION "Cut into 1/2/3/4/5 (yu)" [83791-83892] -->
-<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">
-
-<p>
-To paste a buffer into the current schematic:
-</p>
-<ol>
-<li class="level1"><div class="li"> Fill the buffer using the above Copy or Cut.</div>
-</li>
-<li class="level1"><div class="li"> Go to the new schematic page/window.</div>
-</li>
-<li class="level1"><div class="li"> Select Buffer/Paste/Paste from buffer #.</div>
-</li>
-<li class="level1"><div class="li"> Click the first mouse button to pick an anchor point.</div>
-</li>
-<li class="level1"><div class="li"> Move the mouse to the final spot.</div>
-</li>
-<li class="level1"><div class="li"> Click the first mouse button again.</div>
-</li>
-</ol>
-
-</div>
-<!-- SECTION "Paste from 1/2/3/4/5 (yp)" [83893-84246] -->
-<h2><a name="view" id="view">View</a></h2>
-<div class="level2">
-
-</div>
-<!-- SECTION "View" [84247-84264] -->
-<h3><a name="redraw_vr" id="redraw_vr">Redraw (vr)</a></h3>
-<div class="level3">
-
-<p>
-<strong>View | Redraw</strong> re-paints the current window.<br/>
- This is useful when you have mouse/component/line/text etc… droppings left over from a previous action. It is also useful when you want to update all visual connectivity cues.
-</p>
-
-</div>
-<!-- SECTION "Redraw (vr)" [84265-84515] -->
-<h3><a name="pan_x" id="pan_x">Pan (x)</a></h3>
-<div class="level3">
-
-<p>
-<strong>View | Pan</strong> lets you change the focus of the display.<br/>
- To pan the display:
-</p>
-<ul>
-<li class="level1"><div class="li"> Select <strong>View | Pan</strong></div>
-</li>
-<li class="level1"><div class="li"> Click the first mouse button at the new center of the display.</div>
-</li>
-</ul>
-
-<p>
- To pan the display using the shortcut is much simpler, simply place the mouse pointer where you want the display centered and type â??xâ??. The display will jump to the mouseâ??s location.<br/>
- Pan behavior is configurable. The system-gschemrc file defines: <pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">(third-button "popup")</font></pre>
-</p>
-
-<p>
-If you override the system-gschemrcâ??s default, of popping up a menu when the third mouse button is clicked, by adding: <pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">(third-button "mousepan")</font></pre>
-</p>
-
-<p>
-to either your userâ??s ~/gschemrc file or local â??pwdâ??/gschemrc file, the third mouse button (i.e., the right mouse button on scroll-wheel mice) will allow you to pan the schematic by holding down the third mouse button and dragging.<br/>
- The system-gschemrc file also defines: <pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">(fast-mousepan "enabled")</font></pre>
-</p>
-
-<p>
-If you override the system-gschemrcâ??s default by adding: <pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">(fast-mousepan "disabled")</font></pre>
-</p>
-
-<p>
-to either your userâ??s ~/gschemrc file or local â??pwdâ??/gschemrc file, text will be displayed properly when the third mouse button is held down while dragging. The <code>(third-button â??mousepanâ??)</code> setting must also be applied for this to work. Disabling <code>fast-mousepan</code> adversely effects rendering speed while panning on large â??complicatedâ?? schematics.<br/>
- The system-gschemrc file also defines: <pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">(zoom-with-pan "enabled")</font></pre>
-</p>
-
-<p>
-If you override the system-gschemrcâ??s default by adding: <pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">(zoom-with-pan "disabled")</font></pre>
-</p>
-
-<p>
-to either your userâ??s ~/gschemrc file or local â??pwdâ??/gschemrc file, whenever you zoom in/out, the zoom will NOT center on the mouse pointer, effectively removing the pan feature of the zoom in/out operations.
-</p>
-
-</div>
-<!-- SECTION "Pan (x)" [84516-86312] -->
-<h3><a name="zoom_box_w" id="zoom_box_w">Zoom Box (w)</a></h3>
-<div class="level3">
-
-<p>
-<strong>View | Zoom Box</strong> allows you to draw a box around a part of the <strong>gschem</strong> window and zoom in.<br/>
- To use <strong>View | Zoom Box</strong>:
-</p>
-<ul>
-<li class="level1"><div class="li"> Select <strong>View | Zoom Box</strong></div>
-</li>
-<li class="level1"><div class="li"> Position the mouse pointer at one corner of the box you want to draw</div>
-</li>
-<li class="level1"><div class="li"> Click and hold down the first mouse button</div>
-</li>
-<li class="level1"><div class="li"> Drag the mouse, drawing the zoom box around the area to which you want to zoom</div>
-</li>
-<li class="level1"><div class="li"> Release the mouse button and the display will zoom</div>
-</li>
-</ul>
-
-<p>
- To use <strong>View | Zoom Box</strong> by typing the equivalent shortcut (i.e., â??<strong>w</strong>â??) is more convenient. Simply position the mouse pointer at one corner of the zoom box, then type â??<strong>w</strong>â??. The zoom box will start immediately using the current mouse location as the first corner of the box.<br/>
- <strong>View | Zoom Box</strong> will attempt to zoom to the requested area, but some boxes are not legal and <strong>gschem</strong> will do itâ??s best to zoom the requested area.
-</p>
-
-</div>
-<!-- SECTION "Zoom Box (w)" [86313-87193] -->
-<h3><a name="zoom_extents_ve" id="zoom_extents_ve">Zoom Extents (ve)</a></h3>
-<div class="level3">
-
-<p>
-<strong>View | Extents</strong> will zoom the display to fit all of the placed objects into the current window.<br/>
- To view all of the current windowâ??s objects:
-</p>
-<ul>
-<li class="level1"><div class="li"> Select <strong>View | Extents</strong></div>
-</li>
-</ul>
-
-<p>
- Typing the <strong>View | Extents</strong> shortcut (i.e., â??<strong>ve</strong>â??) is particularly convenient for those that have learned to navigate the schematics using the shortcuts.<br/>
-
-</p>
-
-</div>
-<!-- SECTION "Zoom Extents (ve)" [87194-87560] -->
-<h3><a name="zoom_in_z" id="zoom_in_z">Zoom In (z)</a></h3>
-<div class="level3">
-
-<p>
-<strong>View | Zoom In</strong> zooms the display in. The current center of the window is the center of the new window. This command zooms in by a factor.<br/>
- To zoom in:
-</p>
-<ul>
-<li class="level1"><div class="li"> Select <strong>View | Zoom In</strong></div>
-</li>
-</ul>
-
-<p>
- The (zoom-with-pan â??enabledâ??) configuration setting in the gschemrc files effects the operation of the zoom in shortcut (i.e., â??<strong>z</strong>â??). The default system-gschemrc setting for: <pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">(zoom-with-pan "enabled")</font></pre>
-</p>
-
-<p>
-enables zooming in, using the mouse pointerâ??s location as the new center of the window. If this changed to: <pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">(zoom-with-pan "disabled")</font></pre>
-</p>
-
-<p>
-in either your userâ??s ~/gschemrc file or local â??pwdâ??/gschemrc file, whenever you zoom in, the zoom will NOT center on the mouse pointer but will center on the current center of the window, effectively removing the pan feature of the zoom in operation.<br/>
- To zoom in using the shortcut:
-</p>
-<ul>
-<li class="level1"><div class="li"> If the default (zoom-with-pan â??enabledâ??) is configured in one of the gschemrc files, position the mouse pointer in the window where you want the new center</div>
-</li>
-<li class="level1"><div class="li"> Type â??<strong>z</strong>â??</div>
-</li>
-</ul>
-
-<p>
- Typing â??<strong>z</strong>â?? is particularly convenient for those that have learned to navigate the schematics using the shortcuts.
-</p>
-
-</div>
-<!-- SECTION "Zoom In (z)" [87561-88722] -->
-<h3><a name="zoom_out_z" id="zoom_out_z">Zoom Out (Z)</a></h3>
-<div class="level3">
-
-<p>
-<strong>View | Zoom Out</strong> zooms the display out. The current center of the window is the center of the new window. This command zooms out by a factor.<br/>
- To zoom out:
-</p>
-<ul>
-<li class="level1"><div class="li"> Select <strong>View | Zoom Out</strong></div>
-</li>
-</ul>
-
-<p>
- The (zoom-with-pan â??enabledâ??) configuration setting in the gschemrc files effects the operation of the zoom out shortcut (i.e., â??<strong>z</strong>â??). The default system-gschemrc setting for: <pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">(zoom-with-pan "enabled")</font></pre>
-</p>
-
-<p>
-enables zooming out, using the mouse pointerâ??s location as the new center of the window. If this changed to: <pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">(zoom-with-pan "disabled")</font></pre>
-</p>
-
-<p>
-in either your userâ??s ~/gschemrc file or local â??pwdâ??/gschemrc file, whenever you zoom out, the zoom will NOT center on the mouse pointer but will center on the current center of the window, effectively removing the pan feature of the zoom out operation.<br/>
- To zoom out using the shortcut:
-</p>
-<ul>
-<li class="level1"><div class="li"> If the default (zoom-with-pan â??enabledâ??) is configured in one of the gschemrc files, position the mouse pointer in the window where you want the new center</div>
-</li>
-<li class="level1"><div class="li"> Type â??<strong>Z</strong>â?? (i.e., shift-z)</div>
-</li>
-</ul>
-
-<p>
- Typing â??<strong>Z</strong>â?? is particularly convenient for those that have learned to navigate the schematics using the shortcuts.
-</p>
-
-</div>
-<!-- SECTION "Zoom Out (Z)" [88723-89911] -->
-<h3><a name="zoom_full_vf" id="zoom_full_vf">Zoom Full (vf)</a></h3>
-<div class="level3">
-
-<p>
-<strong>View | Zoom Full</strong> will zoom the display to the maximum possible displayable view.<br/>
-
-</p>
-
-<p>
-To view the maximum displayable area:
-</p>
-<ul>
-<li class="level1"><div class="li"> Select <strong>View | Zoom Full</strong></div>
-</li>
-</ul>
-
-<p>
- The window contents will immediately change to show the maximum possible displayable view.<br/>
-
-</p>
-
-<p>
-To view the maximum displayable area using the keyboard shortcut (i.e., â??<strong>vf</strong>â??):
-</p>
-<ul>
-<li class="level1"><div class="li"> Type â??<strong>vf</strong>â??</div>
-</li>
-</ul>
-
-<p>
- The window contents will immediately change to show the maximum possible displayable view.<br/>
-
-</p>
-
-<p>
-<strong>View | Zoom Full</strong> is useful if you like to put your working notes outside the titleblock for you schematic, for example. Just remember, these notes would now be considered part of the windows extents, so if you were to <strong>View | Extents</strong>, the display would show the titleblock and your working notes.
-</p>
-
-</div>
-<!-- SECTION "Zoom Full (vf)" [89912-90690] -->
-<h2><a name="page" id="page">Page</a></h2>
-<div class="level2">
-
-</div>
-<!-- SECTION "Page" [90691-90709] -->
-<h3><a name="manager..._pm" id="manager..._pm">Manager... (pm)</a></h3>
-<div class="level3">
-
-</div>
-<!-- SECTION "Manager... (pm)" [90710-90737] -->
-<h3><a name="next" id="next">Next (>)</a></h3>
-<div class="level3">
-
-</div>
-<!-- SECTION "Next (>)" [90738-90758] -->
-<h3><a name="previous" id="previous">Previous (<)</a></h3>
-<div class="level3">
-
-</div>
-<!-- SECTION "Previous (<)" [90759-90783] -->
-<h3><a name="new_pe" id="new_pe">New (pe)</a></h3>
-<div class="level3">
-
-</div>
-<!-- SECTION "New (pe)" [90784-90804] -->
-<h3><a name="revert_pr" id="revert_pr">Revert (pr)</a></h3>
-<div class="level3">
-
-</div>
-<!-- SECTION "Revert (pr)" [90805-90828] -->
-<h3><a name="close_pc" id="close_pc">Close (pc)</a></h3>
-<div class="level3">
-
-</div>
-<!-- SECTION "Close (pc)" [90829-90851] -->
-<h3><a name="discard_pd" id="discard_pd">Discard (pd)</a></h3>
-<div class="level3">
-
-</div>
-<!-- SECTION "Discard (pd)" [90852-90876] -->
-<h2><a name="add" id="add">Add</a></h2>
-<div class="level2">
-
-</div>
-<!-- SECTION "Add" [90877-90893] -->
-<h3><a name="component..._i" id="component..._i">Component... (i)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Add | Component…</strong> opens a dialog box which lets you place components from the component libraries.<br/>
- To place a component:
-</p>
-<ul>
-<li class="level1"><div class="li"> Select <strong>Add |Component…</strong></div>
-</li>
-<li class="level1"><div class="li"> Select a component Library from the left list-box</div>
-</li>
-<li class="level1"><div class="li"> Select a component from the right list-box</div>
-</li>
-<li class="level1"><div class="li"> Confirm the symbol is correct by reviewing the image in the Preview window</div>
-</li>
-<li class="level1"><div class="li"> Move the mouse into the main drawing window (you should see an outline follow the mouse pointer).</div>
-</li>
-<li class="level1"><div class="li"> Press the first mouse button to anchor the component</div>
-</li>
-<li class="level1"><div class="li"> Position the mouse pointer, and keep pressing the first mouse button to anchor additional instances of the component</div>
-</li>
-<li class="level1"><div class="li"> When finished anchoring components, press the last mouse button or the ESC key</div>
-</li>
-</ul>
-
-<p>
- If a component name is already selected, hitting apply and moving the mouse into the main window will allow you to place that component again.<br/>
- You can rotate the component before you place it by clicking the middle button. For every button click, the component will be rotate counter-clockwise 90 degrees.<br/>
- Care has been taken to give components descriptive names in the libraries, though it is sometimes difficult to determine what the component really represents from its name.<br/>
- For example: in the analog library there are four capacitor entries:
-</p>
-<ul>
-<li class="level1"><div class="li"> capacitor-1.sym</div>
-</li>
-<li class="level1"><div class="li"> capacitor-2.sym</div>
-</li>
-<li class="level1"><div class="li"> capacitor-3.sym</div>
-</li>
-<li class="level1"><div class="li"> capacitor-4.sym</div>
-</li>
-</ul>
-
-<p>
- It helps to preview the symbol in the â??Select Componentâ?? dialog box before selecting and placing the symbol.
-</p>
-
-</div>
-<!-- SECTION "Component... (i)" [90894-92370] -->
-<h3><a name="net_n" id="net_n">Net (n)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Net</strong> draws a net segment.<br/>
- A net is typically a contiguous set of line segments between two pins, though it is possible to draw nets between a pin and a point on another net, or between two nets.<br/>
- For example, the following diagram shows 3 net segments:
-</p>
-<ul>
-<li class="level1"><div class="li"> Between R1 and R2</div>
-</li>
-<li class="level1"><div class="li"> Between R3 and R4</div>
-</li>
-<li class="level1"><div class="li"> Between the two nets</div>
-</li>
-</ul>
-<table class="inline">
- <tr>
- <td> <a href="_detail/geda_nets.html" class="media" title="geda:nets.jpg"><img src="_media/geda_nets.jpg" class="media" title="nets.jpg" alt="nets.jpg" /></a> </td>
- </tr>
-</table>
-
-<p>
- Note the small red segment at the end of the resistorâ??s pins. All pins in <strong>gschem</strong> have this red segment. This is the connectivity cue for the pin. It is sometimes difficult to â??grabâ?? this attachment point when drawing nets, you may need to zoom in on the pin. To zoom in, press the â??zâ?? key. To zoom out, press the â??Zâ?? (i.e., shift-z) key.<br/>
- To begin drawing a net using the menu:
-</p>
-<ul>
-<li class="level1"><div class="li"> Select <strong>Add | Net</strong></div>
-</li>
-<li class="level1"><div class="li"> Zoom in on the component where the net is to start, so that you can easily grab the pinâ??s attachment point</div>
-</li>
-<li class="level1"><div class="li"> Position the mouse pointer over the pinâ??s connectivity cue</div>
-</li>
-<li class="level1"><div class="li"> Press the first mouse button to start the net</div>
-</li>
-</ul>
-
-<p>
- To begin drawing the net using the shortcut:
-</p>
-<ul>
-<li class="level1"><div class="li"> Zoom in on the component where the net is to start, so that you can easily grab the pinâ??s attachment point</div>
-</li>
-<li class="level1"><div class="li"> Position the mouse pointer over the pinâ??s connectivity cue</div>
-</li>
-<li class="level1"><div class="li"> Press the â??nâ?? key</div>
-</li>
-</ul>
-
-<p>
- To continue drawing the net segment(s):
-</p>
-<ul>
-<li class="level1"><div class="li"> Drag the mouse pointer in the direction of the end-point</div>
-</li>
-<li class="level1"><div class="li"> For any necessary 90º turns, single-click the mouse, and continue dragging the mouse pointer toward the end-point</div>
-</li>
-<li class="level1"><div class="li"> For any necessary non-orthogonal net segments (e.g., 45º angle), hold down the CONTROL button, single-click the mouse, and continue dragging the mouse pointer to the end-point</div>
-</li>
-<li class="level1"><div class="li"> When you reach the end-point, press the first mouse button to end the net segment</div>
-</li>
-<li class="level1"><div class="li"> Another net segment will start at the last end-point</div>
-<ul>
-<li class="level2"><div class="li"> If this second pin is to be connected to a third pin, continue as above</div>
-</li>
-<li class="level2"><div class="li"> If this is the end of the connections, press the last mouse button (or ESC) to end the net</div>
-</li>
-</ul>
-</li>
-</ul>
-
-<p>
- Press the last mouse button or ESC to cancel any net in progress.<br/>
- If the net is cancelled you are automatically placed in <strong>Select Mode</strong>. You must pick <strong>Add | Net</strong> again or type the shortcut to add more nets.<br/>
- You cannot connect a net segment to the middle of a non-orthogonal net.<br/>
- The boxes at the end of the nets are connectivity cues. Red boxes signify a dangling net (not connected to anything).<br/>
- Filled circles are midpoint connections/junctions. These cues are drawn automatically and are an indicator of electrical connectivity.<br/>
- See <a href="docs_20060124_gschem_ug_electrical_connectivity.html" class="wikilink2" title="docs:20060124:gschem_ug:electrical_connectivity">Electrical Connectivity</a> for more information.
-</p>
-
-</div>
-<!-- SECTION "Net (n)" [92371-94962] -->
-<h3><a name="bus_u" id="bus_u">Bus (u)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Add | Bus</strong> is basically the same as <strong>Add | Net</strong>, except that it draws buses.<br/>
- Buses are very new and there are many aspects which are not defined yet, so keep that in mind as you uses buses. More to be added here eventually.
-</p>
-
-</div>
-<!-- SECTION "Bus (u)" [94963-95212] -->
-<h3><a name="attribute..._aa" id="attribute..._aa">Attribute... (aa)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Add | Attribute…</strong> is appropriate when creating or editing symbols, to add a new attribute.<br/>
- <strong>Add | Attribute…</strong> brings up the â??Single Attribute Editorâ?? dialog box. This dialog box is ONLY used to add attributes. It does not display or manipulate already placed attributes.<br/>
- An attribute is nothing more than a text item which is in the form <code>name=value</code> (there cannot be any spaces to the left or right of the name,value pair). It can be either attached to an object, or unattached.<br/>
- To add an unattached attribute (e.g., â??commentâ??, â??documentationâ??, etc.) to the symbol:
-</p>
-<ul>
-<li class="level1"><div class="li"> Select <strong>Add | Attribute…</strong></div>
-</li>
-<li class="level1"><div class="li"> Select an attribute name off of the pulldown list, or type the attribute name into the name entry</div>
-</li>
-<li class="level1"><div class="li"> Type in a value for the attribute</div>
-</li>
-<li class="level1"><div class="li"> Pick any of the attribute options</div>
-</li>
-<li class="level1"><div class="li"> Click OK, and the attribute will be placed.</div>
-</li>
-</ul>
-
-<p>
- If you want to attach an attribute to an object, then select the desired object first and then <strong>Add | Attribute…</strong> from the pull-down menu. If you click on an object which has attached attributes, the attached attributes should be selected as well.<br/>
- If you select <strong>Add | Attribute…</strong> off of the pull down menus then you do not have much control as to where the attribute gets placed (it gets places either at the lower left hand corner of the object extents or at the origin of any selected object). However, if you use the hot key (i.e., â??aaâ??) then the current mouse position is used as the anchor point for the attribute item.<br/>
- You cannot place an incomplete attribute (an attribute without a name and value).<br/>
- Please see <a href="docs_20060124_gschem_ug_components_symbols_objects_attributes.html" class="wikilink2" title="docs:20060124:gschem_ug:components_symbols_objects_attributes">Components/Symbols/Objects/Attributes</a> for more info on how to use attributes.
-</p>
-
-</div>
-<!-- SECTION "Attribute... (aa)" [95213-96925] -->
-<h3><a name="text..._at" id="text..._at">Text... (at)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Add | Text…</strong> displays the â??Text Entry…â?? dialog box. To place text:
-</p>
-<ul>
-<li class="level1"><div class="li"> Select <strong>Options | Text Size…</strong> and select the size for the text</div>
-</li>
-<li class="level1"><div class="li"> Select <strong>Add | Text…</strong></div>
-</li>
-<li class="level1"><div class="li"> Type the text in the entry field (multiple lines may be entered by pressing Enter)</div>
-</li>
-<li class="level1"><div class="li"> Press Apply or type Enter</div>
-</li>
-<li class="level1"><div class="li"> Move the mouse into the main window (an outline of the text should appear and follow the mouse)</div>
-</li>
-<li class="level1"><div class="li"> Press the first mouse button to anchor the text</div>
-</li>
-<li class="level1"><div class="li"> Close the â??Text Entry…â?? dialog box</div>
-</li>
-</ul>
-
-<p>
- If you leave the <strong>Add | Text…</strong> dialog box open you can place the same text item again and again by just clicking Apply (or pressing Enter) and moving the mouse into the main window.<br/>
- The following settings in the system-gschemrc file, the userâ??s ~/gschemrc file, or the local â??pwdâ??/gschemrc file control how text is displayed:
-</p>
-<pre class="code lisp"><span class="co1">; text-origin-marker : Controls if the text origin markers are displayed.</span>
-<span class="co1">; text-size : Sets the default text size.</span>
-<span class="co1">; text-caps-style : Sets the default caps style used for the display of text</span>
-<span class="co1">; output-text : Controls how text is rendered to postscript</span></pre>
-<p>
-Text which is placed will be automatically capitalized. Please see the Resource file section below on how to control this behavior.<br/>
- To cancel a text place press the last mouse button or the ESC key.<br/>
- If you create text in the form name=value, then you are creating attributes. gEDA allows for general attributes to be free floating (or unattached). It is a good idea to change the color of these floating attributes to the current attribute color (which is also called the attached attribute color) to signify that this text item is an attribute.<br/>
- You can rotate the text before you place it by clicking the middle button. For every button click, the text will be rotate 90 degrees.<br/>
-
-</p>
-
-</div>
-<!-- SECTION "Text... (at)" [96926-98729] -->
-<h3><a name="line_l" id="line_l">Line (l)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Add | Line</strong> draws a single line segment.<br/>
- To draw a line:
-</p>
-<ul>
-<li class="level1"><div class="li"> If you want to snap the line to the grid, set the grid spacing by selecting <strong>Options | Snap Grid Spacing…</strong> and entering the grid spacing, and then selecting <strong>Options | Toggle Snap On/Off</strong> until you donâ??t see â??Snap Offâ?? on the status-bar</div>
-</li>
-<li class="level1"><div class="li"> Select <strong>Add | Line</strong></div>
-</li>
-<li class="level1"><div class="li"> If you want to constrain the line to 90º movements, hold the CONTROL key down while moving the mouse</div>
-</li>
-<li class="level1"><div class="li"> Position the mouse pointer to the start-point</div>
-</li>
-<li class="level1"><div class="li"> Press the first mouse button</div>
-</li>
-<li class="level1"><div class="li"> Move the mouse in the intended direction</div>
-</li>
-<li class="level1"><div class="li"> When positioned at the end-point, press the first mouse button</div>
-</li>
-<li class="level1"><div class="li"> Continue placing lines, until you either press the second mouse button or type the Escape key</div>
-</li>
-</ul>
-
-<p>
- <strong>Add | Line</strong> draws a line in the same fashion as drawing nets with the following exceptions:
-</p>
-<ul>
-<li class="level1"><div class="li"> A line has no electrical significance</div>
-</li>
-<li class="level1"><div class="li"> Only a single line segment can be drawn</div>
-</li>
-<li class="level1"><div class="li"> You keep drawing lines as long as you are in line <strong>Line Mode</strong>.</div>
-</li>
-</ul>
-
-<p>
- To cancel a line in progress, press the last mouse button or type the ESC key.
-</p>
-
-</div>
-<!-- SECTION "Line (l)" [98730-99816] -->
-<h3><a name="box_b" id="box_b">Box (b)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Add | Box</strong> draws a box. To draw a box:
-</p>
-<ul>
-<li class="level1"><div class="li"> If you want to snap the box to the grid, set the grid spacing by selecting <strong>Options | Snap Grid Spacing…</strong> and entering the grid spacing, and then selecting <strong>Options | Toggle Snap On/Off</strong> until you donâ??t see â??Snap Offâ?? on the status-bar</div>
-</li>
-<li class="level1"><div class="li"> Select <strong>Add | Box</strong></div>
-</li>
-<li class="level1"><div class="li"> Position the mouse pointer to the start-point</div>
-</li>
-<li class="level1"><div class="li"> Press the first mouse button</div>
-</li>
-<li class="level1"><div class="li"> Move the mouse in the intended direction</div>
-</li>
-<li class="level1"><div class="li"> When positioned at the end-point, press the first mouse button again</div>
-</li>
-<li class="level1"><div class="li"> Continue placing boxes, until you either press the second mouse button or type the ESC key</div>
-</li>
-</ul>
-
-<p>
- To cancel a box in progress, press the last mouse button or type the ESC key.<br/>
- A box has no electrical significance.
-</p>
-
-</div>
-<!-- SECTION "Box (b)" [99817-100569] -->
-<h3><a name="circle_ai" id="circle_ai">Circle (ai)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Add | Circle</strong> creates a circle.<br/>
- To draw a circle:
-</p>
-<ul>
-<li class="level1"><div class="li"> If you want to snap the box to the grid, set the grid spacing by selecting <strong>Options | Snap Grid Spacing…</strong> and entering the grid spacing, and then selecting <strong>Options | Toggle Snap On/Off</strong> until you donâ??t see â??Snap Offâ?? on the status-bar</div>
-</li>
-<li class="level1"><div class="li"> Select <strong>Add | Circle</strong></div>
-</li>
-<li class="level1"><div class="li"> Place the mouse pointer at the center of the circle</div>
-</li>
-<li class="level1"><div class="li"> Press the first button</div>
-</li>
-<li class="level1"><div class="li"> Move the mouse to see an outline of the circle</div>
-</li>
-<li class="level1"><div class="li"> Press the first mouse button to finish the circle</div>
-</li>
-<li class="level1"><div class="li"> Continue placing circles, until you either press the second mouse button or type the ESC key</div>
-</li>
-</ul>
-
-<p>
- To draw a circle (typing the shortcut), same as above except that you position the mouse pointer to the center-point of the circle before you type the shortcut.<br/>
- To cancel a circle in progress, press the last mouse button or the ESC key.<br/>
-
-</p>
-
-</div>
-<!-- SECTION "Circle (ai)" [100570-101454] -->
-<h3><a name="arc_ar" id="arc_ar">Arc (ar)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Add | Arc</strong> draws an arc. To draw an arc:
-</p>
-<ul>
-<li class="level1"><div class="li"> If you want to snap the box to the grid, set the grid spacing by selecting <strong>Options | Snap Grid Spacing…</strong> and entering the grid spacing, and then selecting <strong>Options | Toggle Snap On/Off</strong> until you donâ??t see â??Snap Offâ?? on the status-bar</div>
-</li>
-<li class="level1"><div class="li"> Select <strong>Add | Arc</strong></div>
-</li>
-<li class="level1"><div class="li"> Place the mouse pointer at the center-point for the arc</div>
-</li>
-<li class="level1"><div class="li"> Press the first mouse button</div>
-</li>
-<li class="level1"><div class="li"> Move the mouse to the right, to define the radius of the arc</div>
-</li>
-<li class="level1"><div class="li"> Press the first mouse button again</div>
-</li>
-<li class="level1"><div class="li"> Enter the Start Angle (in degrees) – 0º is the â??xâ?? axis</div>
-</li>
-<li class="level1"><div class="li"> Enter the Degrees of Sweep (for counter-clockwise sweep)</div>
-</li>
-<li class="level1"><div class="li"> Press OK</div>
-</li>
-<li class="level1"><div class="li"> Continue placing arcs, until you either press the second mouse button or type the ESC key</div>
-</li>
-</ul>
-
-<p>
- The Start Angle can be positive or negative. The degrees are specified using the standard Cartesian coordinate system. The degrees of sweep can be positive or negative.<br/>
- To cancel an arc in progress (while rubberband the radius), press the last mouse button or the ESC key or press the Cancel button in the arc dialog box.
-</p>
-
-</div>
-<!-- SECTION "Arc (ar)" [101455-102547] -->
-<h3><a name="pin_ap" id="pin_ap">Pin (ap)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Add | Pin</strong> adds a pin.<br/>
- Though you can <strong>Add | Pin</strong> while entering a schematic, it only makes sense to create pins while creating or editing symbol files.<br/>
- To draw a pin:
-</p>
-<ul>
-<li class="level1"><div class="li"> Set the grid spacing by selecting <strong>Options | Snap Grid Spacing…</strong> and entering the grid spacing, and then selecting <strong>Options | Toggle Snap On/Off</strong> until you donâ??t see â??Snap Offâ?? on the status-bar. The <a href="http://www.geda.seul.org/docs/current/symbols/symbols.pdf"; class="urlextern" title="http://www.geda.seul.org/docs/current/symbols/symbols.pdf"; rel="nofollow">gEDA/gaf Symbol Creation Document</a> specifies grid settings for pin placement in gEDA/gaf compliant symbols files.</div>
-</li>
-<li class="level1"><div class="li"> Select <strong>Add | Pin</strong></div>
-</li>
-<li class="level1"><div class="li"> Pins are constrained to 90º movements</div>
-</li>
-<li class="level1"><div class="li"> Position the mouse pointer to the start-point</div>
-</li>
-<li class="level1"><div class="li"> Press the first mouse button</div>
-</li>
-<li class="level1"><div class="li"> Move the mouse in the intended direction. The <a href="http://www.geda.seul.org/docs/current/symbols/symbols.pdf"; class="urlextern" title="http://www.geda.seul.org/docs/current/symbols/symbols.pdf"; rel="nofollow">gEDA/gaf Symbol Creation Document</a> specifies the length of pins in gEDA/gaf compliant symbol files.</div>
-</li>
-<li class="level1"><div class="li"> When positioned at the end-point, press the first mouse button</div>
-</li>
-<li class="level1"><div class="li"> Continue placing pins, until you either press the second mouse button or type the Escape key</div>
-</li>
-</ul>
-
-<p>
- To cancel a pin in progress, press the last mouse button or the ESC key.
-</p>
-
-</div>
-<!-- SECTION "Pin (ap)" [102548-103735] -->
-<h3><a name="picture..._ag" id="picture..._ag">Picture... (ag)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Add | Picture</strong> places a graphic in the schematic. To draw a picture:
-</p>
-<ul>
-<li class="level1"><div class="li"> If you want to snap the picture to the grid, set the grid spacing by selecting <strong>Options | Snap Grid Spacing…</strong> and entering the grid spacing, and then selecting <strong>Options | Toggle Snap On/Off</strong> until you donâ??t see â??Snap Offâ?? on the status-bar</div>
-</li>
-<li class="level1"><div class="li"> Select <strong>Add | Picture</strong></div>
-</li>
-<li class="level1"><div class="li"> Select the graphic file from the â??Please select a picture fileâ?? dialog box</div>
-</li>
-<li class="level1"><div class="li"> Press OK</div>
-</li>
-<li class="level1"><div class="li"> Position the mouse pointer to the start-point</div>
-</li>
-<li class="level1"><div class="li"> Press the first mouse button</div>
-</li>
-<li class="level1"><div class="li"> Move the mouse in the intended direction. The outline of the picture will appear, retaining the aspect ratio of the original picture.</div>
-</li>
-<li class="level1"><div class="li"> When positioned at the end-point, press the first mouse button again.</div>
-</li>
-<li class="level1"><div class="li"> Continue placing pictures, until you either press the second mouse button or type the ESC key</div>
-</li>
-</ul>
-
-<p>
- To cancel a picture in progress, press the last mouse button or type the ESC key.<br/>
- A picture has no electrical significance.
-</p>
-
-</div>
-<!-- SECTION "Picture... (ag)" [103736-104731] -->
-<h2><a name="hierarchy" id="hierarchy">Hierarchy</a></h2>
-<div class="level2">
-
-</div>
-<!-- SECTION "Hierarchy" [104732-104754] -->
-<h3><a name="down_schematic_hd" id="down_schematic_hd">Down Schematic (Hd)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Hierarchy | Down Schematic</strong> shifts the focus from the current schematic to a sub-schematic.<br/>
- Go down into a symbol, opening up any underlying schematics. Basically this will open up an underlying schematic of the selected component if it exists in the source library search path. See the Resource File section on how to define this path.<br/>
- There are currently two ways of specifying that a symbol has an underlying schematic or schematics:
-</p>
-<ol>
-<li class="level1"><div class="li"> The underlying schematic must have the same name as the symbol but have a .sch extension and must follow the _# suffix naming convention. See the Files section below on this convention.</div>
-</li>
-<li class="level1"><div class="li"> Attach an attribute to the symbol called source=filename.sch filename.sch is not a path to the symbol, but rather the basename (last file in the path specifier) of the symbol path. The underlying schematic will still be searched in the source-library path. You can specify multiple source= attributes. The underlying schematics will be opened in the order that the source= attribute is found.</div>
-</li>
-</ol>
-
-<p>
- If there multiple underlying schematics, they will be loaded. Movement between the schematic pages is restricted (to the same level of the same set of underlying schematics) unless the rc keyword enforce-hierarchy is modified to allow for a freer hierarchy traversal mode. See the Resource File section for more info.<br/>
- It is also recommend that you maintain unique names for the various levels (when using the source= attribute) to avoid possible confusion. The hierarchy mechanisms are fairly new so expect some odd behavior (and please report it)
-</p>
-
-</div>
-<!-- SECTION "Down Schematic (Hd)" [104755-106367] -->
-<h3><a name="down_symbol_hs" id="down_symbol_hs">Down Symbol (Hs)</a></h3>
-<div class="level3">
-
-<p>
-This option will open up the symbol of the selected component.<br/>
- Once the symbol is open, the user can edit it and save it.<br/>
- At this time, the toplevel schematic will not see the symbol change unless the toplevel schematic is reloaded or File/Revert is executed. This will be fixed eventually.
-</p>
-
-</div>
-<!-- SECTION "Down Symbol (Hs)" [106368-106690] -->
-<h3><a name="up_hu" id="up_hu">Up (Hu)</a></h3>
-<div class="level3">
-
-<p>
-This option will move up the hierarchy (if there are pages above the currently displayed page).
-</p>
-
-</div>
-<!-- SECTION "Up (Hu)" [106691-106805] -->
-<h3><a name="documentation_ho" id="documentation_ho">Documentation (Ho)</a></h3>
-<div class="level3">
-
-<p>
-Open any documentation available for the selected symbol/component.<br/>
- The job is handed over to â??gschemdocâ??, which makes a best-effort attempt of finding relevant documentation.<br/>
- The documention would normally be in <acronym title="Portable Document Format">PDF</acronym>, <acronym title="HyperText Markup Language">HTML</acronym>, text or image format, but gschemdoc tries to be as transparent as possible on this account.<br/>
- First and foremost, the attribute â??documentation=" is assumed to point to the documentation. This attribute should either be the filename (basename) of the document, or it should be a complete <acronym title="Uniform Resource Locator">URL</acronym>.<br/>
- If it is a filename, and the file is found locally (in /usr/share/gEDA/documentation or otherwise), the relevant viewer will be initiated. Otherwise, a Google search for the document will be initiated.<br/>
- If there is no documentation attribute, the attributes â??deviceâ?? and possibly â??valueâ?? will be consulted in much the same way as for â??documentationâ??. File searches will be made in forms of filenames like â??device-value.pdfâ?? and â??device.pdfâ??.<br/>
- Failing that, the file name for the symbol itself will be used as basis for the search.
-</p>
-
-</div>
-<!-- SECTION "Documentation (Ho)" [106806-107890] -->
-<h2><a name="attributes1" id="attributes1">Attributes</a></h2>
-<div class="level2">
-
-</div>
-<!-- SECTION "Attributes" [107891-107914] -->
-<h3><a name="attach_ta" id="attach_ta">Attach (ta)</a></h3>
-<div class="level3">
-
-<p>
-The Attach command allows you to take a text item (in the proper form; <code>name=value</code>) and attach it to another object.<br/>
- To use Attributes/Attach:
-</p>
-<ol>
-<li class="level1"><div class="li"> Select the object which will receive the attributes</div>
-</li>
-<li class="level1"><div class="li"> Select the text object(s) which will be attached to the above object</div>
-</li>
-<li class="level1"><div class="li"> Pick or type the shortcut for Attributes/Attach</div>
-</li>
-</ol>
-
-<p>
- The order of the sequence of selecting the object and then the text items is important; <strong>gschem</strong> will not allow you to select the text items first and then the object. After going through the above sequence the text item will turn yellow (or the current attached attribute color) signifying that the text item is an attached attribute.<br/>
- You cannot attach a single attribute to several different objects. You cannot attach non-text items as attributes.
-</p>
-
-</div>
-<!-- SECTION "Attach (ta)" [107915-108722] -->
-<h3><a name="detach_td" id="detach_td">Detach (td)</a></h3>
-<div class="level3">
-
-<p>
-Detach allows you to deassociate attributes from objects.<br/>
- To deselect an object of all attributes:
-</p>
-<ol>
-<li class="level1"><div class="li"> Select the object of interest</div>
-</li>
-<li class="level1"><div class="li"> Pick or type the shortcut for Attributes/Detach</div>
-</li>
-</ol>
-
-<p>
- All the attached attributes (even if they are not selected) will be detached from the object. This behavior is probably broken and will eventually be fixed (so that only selected attributes are detached).<br/>
- When you detach attributes then they turn red (or the current detached attribute color). This color changes allows you to spot text which was an attribute and is now dangling (unattached).
-</p>
-
-</div>
-<!-- SECTION "Detach (td)" [108723-109329] -->
-<h3><a name="show_value_tv" id="show_value_tv">Show Value (tv)</a></h3>
-<div class="level3">
-
-<p>
-These operations allow you to control which part of the attribute string is visible. Usually you are just interested in seeing the <code>value</code> of the attribute, but there are circumstances where seeing the <code>name</code> and <code>value</code> (or maybe just the <code>name</code>) would be useful.<br/>
- To use the options:
-</p>
-<ol>
-<li class="level1"><div class="li"> Select the attribute(s) of interest</div>
-</li>
-<li class="level1"><div class="li"> Pick or type the shortcut for Attributes/Show *</div>
-</li>
-</ol>
-
-<p>
- The text item(s) should immediately change.<br/>
- These operations only work on text items which are in the form <code>name=value</code>
-</p>
-
-</div>
-<!-- SECTION "Show Value (tv)" [109330-109868] -->
-<h3><a name="show_name_tn" id="show_name_tn">Show Name (tn)</a></h3>
-<div class="level3">
-
-<p>
-These operations allow you to control which part of the attribute string is visible. Usually you are just interested in seeing the <code>value</code> of the attribute, but there are circumstances where seeing the <code>name</code> and <code>value</code> (or maybe just the <code>name</code>) would be useful.<br/>
- To use the options:
-</p>
-<ol>
-<li class="level1"><div class="li"> Select the attribute(s) of interest</div>
-</li>
-<li class="level1"><div class="li"> Pick or type the shortcut for Attributes/Show *</div>
-</li>
-</ol>
-
-<p>
- The text item(s) should immediately change.<br/>
- These operations only work on text items which are in the form <code>name=value</code>
-</p>
-
-</div>
-<!-- SECTION "Show Name (tn)" [109869-110406] -->
-<h3><a name="show_both_tb" id="show_both_tb">Show Both (tb)</a></h3>
-<div class="level3">
-
-<p>
-These operations allow you to control which part of the attribute string is visible. Usually you are just interested in seeing the <code>value</code> of the attribute, but there are circumstances where seeing the <code>name</code> and <code>value</code> (or maybe just the <code>name</code>) would be useful.<br/>
- To use the options:
-</p>
-<ol>
-<li class="level1"><div class="li"> Select the attribute(s) of interest</div>
-</li>
-<li class="level1"><div class="li"> Pick or type the shortcut for Attributes/Show *</div>
-</li>
-</ol>
-
-<p>
- The text item(s) should immediately change.<br/>
- These operations only work on text items which are in the form <code>name=value</code>
-</p>
-
-</div>
-<!-- SECTION "Show Both (tb)" [110407-110944] -->
-<h3><a name="toggle_visibility_tt" id="toggle_visibility_tt">Toggle Visibility (tt)</a></h3>
-<div class="level3">
-
-<p>
-This operation allows you to toggle the visibility of attributes.<br/>
- To use this option:
-</p>
-<ol>
-<li class="level1"><div class="li"> Select the text item(s) of interest</div>
-</li>
-<li class="level1"><div class="li"> Pick or type the shortcut for Attributes/Toggle Vis</div>
-</li>
-</ol>
-
-<p>
- The text item(s) should change their visibility immediately.<br/>
- If you make an attached attribute invisible, then you can simply select the parent object and select Toggle Vis and the attribute will be come visible (likewise any visible attributes attached to that object will become invisible).<br/>
- If you make a free floating (unattached) attribute invisible, then the only way to make it visible (and all other invisible attributes) is to use the Edit/Show Hidden Text option.
-</p>
-
-</div>
-<!-- SECTION "Toggle Visibility (tt)" [110945-111640] -->
-<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">
-
-<p>
- This operation allows you to find a text element in a schematic.
-</p>
-
-<p>
-To use this operation:
-</p>
-<ol>
-<li class="level1"><div class="li"> open the dialog and enter the substring you want to search for</div>
-</li>
-<li class="level1"><div class="li"> select whether you only want to search in the current page or in the whole hierarchy of a multipage schematic</div>
-</li>
-<li class="level1"><div class="li"> press the find button</div>
-</li>
-</ol>
-
-<p>
- If the text is found in the schematic, gschem will zoom and pan to that element. Pressing the find button again will find the next matching text element. If no more text is found the dialog closes.
-</p>
-
-<p>
-<strong>Note:</strong> gschem will find hidden text elements, too. If you donâ??t see the found element, try to show the hidden text.
-</p>
-
-</div>
-<!-- SECTION "Find Specific Text... (t shift-f)" [111641-112301] -->
-<h3><a name="hide_specific_text..._th" id="hide_specific_text..._th">Hide Specific Text... (th)</a></h3>
-<div class="level3">
-
-<p>
- This operation allows you to hide text elements.
-</p>
-
-<p>
-To use this operation:
-</p>
-<ol>
-<li class="level1"><div class="li"> open the dialog and enter your text string</div>
-</li>
-<li class="level1"><div class="li"> press the apply button</div>
-</li>
-</ol>
-
-<p>
- gschem will hide all text elements that start with the given search string.
-</p>
-
-<p>
-This operation is useful if you like to hide pintype and pinseq attributes when creating symbols.
-</p>
-
-</div>
-<!-- SECTION "Hide Specific Text... (th)" [112302-112663] -->
-<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">
-
-<p>
- This operation allows you to show hidden text elements.
-</p>
-
-<p>
-To use this operation:
-</p>
-<ol>
-<li class="level1"><div class="li"> open the dialog and enter your text string</div>
-</li>
-<li class="level1"><div class="li"> press the apply button</div>
-</li>
-</ol>
-
-<p>
- gschem will unhide all hidden text elements that starts with the given search string.
-</p>
-
-<p>
-This operation is useful if you like to see only one specific attribute in the whole schematic (the footprint attribute for example). Use this operation together with the <em>Hide Specific Text</em> operation.
-</p>
-
-</div>
-<!-- SECTION "Show Specific Text... (t shift-h)" [112664-113155] -->
-<h3><a name="autonumber_text..._tu" id="autonumber_text..._tu">Autonumber Text... (tu)</a></h3>
-<div class="level3">
-
-<p>
- This operation allows you to renumber text elements in your schematics and symbols.
-</p>
-
-<p>
-You can use it to:
-</p>
-<ul>
-<li class="level1"><div class="li"> renumber pinseq and pinnumber attributes when creating symbols</div>
-</li>
-<li class="level1"><div class="li"> renumber components in a schematic (the refdes attribute)</div>
-</li>
-<li class="level1"><div class="li"> renumber netnames to create address and data busses</div>
-</li>
-</ul>
-
-<p>
- To use that operation:
-</p>
-<ol>
-<li class="level1"><div class="li"> select or enter the text elements you like to renumber in the <em>search for</em> entry. searchtext with a "?" at the end will match trailing "?" and trailing numbers in the text elements you are searching for. searchtext with a â??*â?? at the end will match the given searchtext, followed by arbitrary text and followed by a trailing "?" or trailing numbers.</div>
-</li>
-<li class="level1"><div class="li"> the <em>autonumber text in</em> option specifies where to search for the given searchstring.</div>
-</li>
-<li class="level1"><div class="li"> the <em>skip numbers found in</em> option specifies in which region you donâ??t want have duplicate numbers. <strong>Example:</strong> If you renumber your components you usually want uniq numbers on a page or even uniq number in the whole hierarchy of a multipage schematic. If you renumber netnames of a bus you usually want to apply the new numbers only to selected net elements. Thus you can have multiple equal netnames on a schematic sheet.</div>
-</li>
-<li class="level1"><div class="li"> the <em>overwrite existing numbers</em> option specifies whether you only want to number unnumbered elements or if you like to renumber elements too.</div>
-</li>
-<li class="level1"><div class="li"> The <em>starting number</em> entry allows you to specify the start number you like. It is common to number each schematic sheet starting with numbers like 100, 200 and so on. For bus netnames you may need numbers starting at 8, 16.</div>
-</li>
-<li class="level1"><div class="li"> The <em>sort order</em> tells in which direction you like to number your elements. For components you usually use the <em>diagonal</em>, the <em>top to bottom</em> or the <em>left to right</em> option. For bus netnames you may need <em>right to left</em> and <em>bottom to top</em> numbering. The <em>file order</em> means that the found text elements are not sorted before renumbering them. The fileorder is usually the order you have placed the objects to your sheet.</div>
-</li>
-<li class="level1"><div class="li"> the <em>remove numbers</em> options is a special option. It removes all numbers from the text elements you have selected in the <em>Scope</em> section of the dialog.</div>
-</li>
-<li class="level1"><div class="li"> the <em>automatic slotting</em> option is the second special option. When renumbering components it will add the slot attribute to slotted components like logik gates.</div>
-</li>
-</ol>
-
-<p>
- Pressing the apply button will start the autonumbering action.
-</p>
-
-</div>
-<!-- SECTION "Autonumber Text... (tu)" [113156-115593] -->
-<h2><a name="options" id="options">Options</a></h2>
-<div class="level2">
-
-</div>
-<!-- SECTION "Options" [115594-115614] -->
-<h3><a name="text_size..._ot" id="text_size..._ot">Text Size... (ot)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Options | Text Size…</strong> pops up a dialog box which allows you to specify the text size of all text (including attributes placed with the Add/Attribute… dialog box).<br/>
- The text size is in points (1/72â??). The default text size is 10 point text. The smallest text size is 2 points.
-</p>
-
-</div>
-<!-- SECTION "Text Size... (ot)" [115615-115927] -->
-<h3><a name="toggle_grid_on_off_og" id="toggle_grid_on_off_og">Toggle Grid On/Off (og)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Options | Toggle Grid On/Off</strong> toggles the visible grid.
-</p>
-
-</div>
-<!-- SECTION "Toggle Grid On/Off (og)" [115928-116021] -->
-<h3><a name="toggle_snap_on_off_os" id="toggle_snap_on_off_os">Toggle Snap On/Off (os)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Options | Toggle Snap On/Off</strong> toggles the snap. Be very careful using this. Connections between pins and nets (and nets to nets) depends on being exactly connected. Turning of the grid will almost guarantee that nets/pins do not connect.<br/>
- Before you translate a symbol using Edit/Symbol Translate, make sure the snap is on.<br/>
- When snap mode is off, the text â??Snap Offâ?? will appear in the lower, righthand corner.
-</p>
-
-</div>
-<!-- SECTION "Toggle Snap On/Off (os)" [116022-116473] -->
-<h3><a name="snap_grid_spacing..._os" id="snap_grid_spacing..._os">Snap Grid Spacing... (oS)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Options | Snap Grid Spacing…</strong> brings up a dialog box which allows you to change the snap grid spacing (not the grid spacing). The units for this spacing are mils.<br/>
- Before you translate a symbol using Edit/Symbol Translate, make sure this spacing is set to 100.
-</p>
-
-</div>
-<!-- SECTION "Snap Grid Spacing... (oS)" [116474-116777] -->
-<h3><a name="toggle_outline_box_oa" id="toggle_outline_box_oa">Toggle Outline/Box (oa)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Options | Toggle Outline/Box</strong> toggles between drawing the outline of the current selection or just drawing a box when doing moves/copies/component and text places. The outline mode looks better, but tends to be significantly slower than using the box (bounding box) mode.
-</p>
-
-</div>
-<!-- SECTION "Toggle Outline/Box (oa)" [116778-117087] -->
-<h3><a name="toggle_net_rubberband_or" id="toggle_net_rubberband_or">Toggle Net/Rubberband (or)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Options | Toggle Net/Rubberband</strong> …..????
-</p>
-
-</div>
-<!-- SECTION "Toggle Net/Rubberband (or)" [117088-117171] -->
-<h3><a name="show_log_window_ol" id="show_log_window_ol">Show Log Window (ol)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Options | Show Log Window</strong> displays the log window if it has been closed or disabled from being displayed when you start up <strong>gschem</strong>.
-</p>
-
-</div>
-<!-- SECTION "Show Log Window (ol)" [117172-117342] -->
-<h3><a name="show_coord_window..._oc" id="show_coord_window..._oc">Show Coord Window... (oc)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Options | Show Coord Window…</strong> displays a pop-up window that displays the coordinates of the mouse pointer on the schematic. Useful for accurately placing objects.
-</p>
-
-</div>
-<!-- SECTION "Show Coord Window... (oc)" [117343-117547] -->
-<h2><a name="help" id="help">Help</a></h2>
-<div class="level2">
-
-</div>
-<!-- SECTION "Help" [117548-117565] -->
-<h3><a name="about..._ha" id="about..._ha">About... (ha)</a></h3>
-<div class="level3">
-
-<p>
-Every <acronym title="Graphical User Interface">GUI</acronym> application needs an <strong>Help | About…</strong> feature, to display:
-</p>
-<ul>
-<li class="level1"><div class="li"> The applicationâ??s name.</div>
-</li>
-<li class="level1"><div class="li"> The version of the software.</div>
-</li>
-<li class="level1"><div class="li"> The authorâ??s name(s) and how to contact.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "About... (ha)" [117566-117768] -->
-<h3><a name="manual..._hm" id="manual..._hm">Manual... (hm)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Help | Manual…</strong> brings up the â??gEDA/gaf Documentionâ?? web-page installed on this computer. Very useful for accessing the various documentation available for the gEDA/gaf applications.
-</p>
-
-</div>
-<!-- SECTION "Manual... (hm)" [117769-117982] -->
-<h3><a name="hotkeys..._hh" id="hotkeys..._hh">Hotkeys... (hh)</a></h3>
-<div class="level3">
-
-<p>
-<strong>Help | Hotkeys…</strong> lists the current hotkeys (a.k.a., shortcuts, a.k.a., keyboard accellerators).
-</p>
-
-</div>
-<!-- SECTION "Hotkeys... (hh)" [117983-118110] -->
-<h3><a name="component..._ho" id="component..._ho">Component... (Ho)</a></h3>
-<div class="level3">
-
-<p>
-If you select a component on the schematic, and select <strong>Help | Component…</strong>, <strong>gschem</strong> uses the gschemdoc script to do its best job finding some documentation appropriate for the component:
-</p>
-<ul>
-<li class="level1"><div class="li"> If the componentâ??s symbol included the <code>documentation=documentation_locator</code> attribute, this <acronym title="Uniform Resource Identifier">URI</acronym> is used to retreive the documentation. If the full <acronym title="Uniform Resource Identifier">URI</acronym> is given, the <acronym title="Uniform Resource Identifier">URI</acronym> on the internet is retrieved. If the <acronym title="Uniform Resource Identifier">URI</acronym> is not fully qualified, it is considered to be local to this computer, and is searched for and displayed.</div>
-</li>
-<li class="level1"><div class="li"> If the componentâ??s symbol does not include the <code>documentation=documentation_locator</code> attribute, a Google search is performed for <acronym title="Portable Document Format">PDF</acronym> documents, based on the <code>device=</code> attribute, the <code>value=</code> attribute, and the symbol basename.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Component... (Ho)" [118111-118893] -->
-<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">
-
-<p>
-A short discussion of Light Symbol Libraries as the default for <strong>gschem</strong>, and the option to build your own Heavy Symbol Libraries.
-</p>
-
-</div>
-<!-- SECTION "Appendix A -- Heavy vs Light Symbol Libraries" [118894-119087] -->
-<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">
-
-<p>
-To be supplied…
-</p>
-
-</div>
-<!-- SECTION "Appendix B -- Printing Schematics and Symbols" [119088-119166] -->
-<h1><a name="appendix_c_--_writing_guile_scripts" id="appendix_c_--_writing_guile_scripts">Appendix C -- Writing guile Scripts</a></h1>
-<div class="level1">
-
-<p>
-To be supplied…
-</p>
-
-</div>
-<!-- SECTION "Appendix C -- Writing guile Scripts" [119167-119235] -->
-<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">
-
-<p>
-<strong>gschem</strong> is used for two primary design workflows:
-</p>
-<ul>
-<li class="level1"><div class="li"> Circuit design intended for production of Printed Circuit Boards (PCBs).</div>
-</li>
-<li class="level1"><div class="li"> Circuit design intended for simulation.</div>
-</li>
-</ul>
-
-<p>
- The following guidelines will assist you in developing quality designs intended for use by applications that support the creation of Printed Circuit Boards:
-</p>
-<ul>
-<li class="level1"><div class="li"> <span class="hilited">To be supplied…</span></div>
-</li>
-</ul>
-
-<p>
- The following on-line tutorials are an excellent method for the beginner to learn the gEDA Tools Suite design workflow resulting in a PCB:
-</p>
-<ul>
-<li class="level1"><div class="li"> <a href="http://www.geda.seul.org/docs/current/tutorials/gsch2pcb/gschem-warmup.html"; class="urlextern" title="http://www.geda.seul.org/docs/current/tutorials/gsch2pcb/gschem-warmup.html"; rel="nofollow">Bill Wilson's gschem warmup</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://www.geda.seul.org/docs/current/tutorials/gsch2pcb/tutorial.html"; class="urlextern" title="http://www.geda.seul.org/docs/current/tutorials/gsch2pcb/tutorial.html"; rel="nofollow">Bill Wilson's gsch2pcb tutorial</a></div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Appendix D -- I Want To Build A Printed Circuit Board" [119236-120025] -->
-<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">
-
-<p>
-<strong>gschem</strong> is used for two primary design workflows:
-</p>
-<ul>
-<li class="level1"><div class="li"> Circuit design intended for production of Printed Circuit Boards.</div>
-</li>
-<li class="level1"><div class="li"> Circuit design intended for simulation.</div>
-</li>
-</ul>
-
-<p>
- The following guidelines will assist you in developing quality designs intended for simulation:
-</p>
-<ul>
-<li class="level1"><div class="li"> Discuss attributes appropriate for a SPICE model, and how these differ from attributes appropriate for a PCB.</div>
-</li>
-<li class="level1"><div class="li"> <span class="hilited">To be supplied…</span></div>
-</li>
-</ul>
-
-<p>
- The following on-line tutorials are an excellent method for the beginner to learn the gEDA Tools Suite design workflow resulting in a SPICE simulation:
-</p>
-<ul>
-<li class="level1"><div class="li"> <a href="http://www.brorson.com/gEDA/SPICE/t1.html"; class="urlextern" title="http://www.brorson.com/gEDA/SPICE/t1.html"; rel="nofollow">"Circuit simulation using gEDA and SPICE -- HOWTO" by Stuart Brorson</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://www-mdp.eng.cam.ac.uk/urop05/files/gedalib/starting_gEDA.pdf"; class="urlextern" title="http://www-mdp.eng.cam.ac.uk/urop05/files/gedalib/starting_gEDA.pdf"; rel="nofollow">Starting with gEDA at the Cambridge University Engineering Department</a></div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Appendix E -- I Want To Simulate My Design" [120026-120905] -->
-<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">
-
-<p>
-As installed, the <strong>gschemdoc</strong> utility script is used by <strong>gschem</strong> to:
-</p>
-<ul>
-<li class="level1"><div class="li"> Display the â??gEDA/gaf Documentationâ?? (i.e., <strong>Help | Manual…</strong>)</div>
-</li>
-<li class="level1"><div class="li"> Display component documentation (i.e., <strong>Help | Component…</strong>)</div>
-</li>
-</ul>
-
-<p>
- The list of application launchers that <strong>gschemdoc</strong> uses are defined in the {binary-install-path}/bin/gschemdoc file: <pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">#
-# these may be changed to suit local preferences
-#
-CANDIDATE_BROWSER="galeon mozilla phoenix netscape netscape-navigator opera firefox konqueror"
-CANDIDATE_PDFREADER="xpdf acroread ggv gv"
-CANDIDATE_LOCATE="slocate locate"</font></pre>
-</p>
-
-<p>
-To select a different application launcher, simply edit the {binary-install-path}/bin/gschemdoc file, find the above lines, and move your favorite application to the beginning of the list. For example, to use <strong>firefox</strong> as your preferred browser, move it to the beginning of the <strong>CANDIDATE_BROWSER=</strong> list, to use <strong>acroread</strong> (Adobeâ??s Acrobat Reader) as your preferred <acronym title="Portable Document Format">PDF</acronym> reader, move it to the beginning of the <strong>CANDIDATE_PDFREADER=</strong> list, and to use <strong>locate</strong> as your preferred filesystem search utility, move it to the beginning of the <strong>CANDIDATE_LOCATE=</strong> list.
-</p>
-
-</div>
-<!-- SECTION "Appendix F -- Change gschemdoc User-Defined Preferences" [120906-122122] -->
-<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">
-
-<p>
-To be supplied…
-</p>
-
-</div>
-<!-- SECTION "Appendix G -- Breaking a Large Symbol Into Smaller Symbols" [122123-122214] -->
-<h1><a name="appendix_h_--_definition_of_terms" id="appendix_h_--_definition_of_terms">Appendix H -- Definition of Terms</a></h1>
-<div class="level1">
-
-<p>
-Some terms used in the art of schematic capture:</p>
-<dl>
-<dt><span class='term'> <strong>attribute</strong></span></dt>
-<dd>A text item which is in the form <code>name=value</code>. It can be either unattached or attached.</dd>
-<dt><span class='term'> <strong>buffer</strong></span></dt>
-<dd>…</dd>
-<dt><span class='term'> <strong>component</strong></span></dt>
-<dd>Also know as <strong>part</strong>. The equivalent of an [electronics] device, as one may place on a printed circuit board. Components are instances of a <strong>symbol</strong> placed on a schematic.</dd>
-<dt><span class='term'> <strong>device</strong></span></dt>
-<dd>Also known as â??packageâ??. The equivalent of an [electronics] device, as one may place on a printed circuit board.</dd>
-<dt><span class='term'> <strong>dialog box</strong></span></dt>
-<dd>…</dd>
-<dt><span class='term'> <strong>embedded component</strong></span></dt>
-<dd>A component whose definition is saved as part of the schematicâ??s file.</dd>
-<dt><span class='term'> <strong>footprint</strong></span></dt>
-<dd>Also known as a <strong>land pattern</strong>. The surface space occupied by a <strong>component</strong>/<strong>package</strong>/<strong>part</strong>.</dd>
-<dt><span class='term'> <strong>gEDA/gaf</strong></span></dt>
-<dd><strong>gschem</strong> is a component of the gEDA/gaf set of tools, which tend to integrate together in the development and maintenance of schematics and symbols. The term â??gafâ?? stands for â??<em class="u">g</em>EDA <em class="u">a</em>nd <em class="u">f</em>riendsâ??).</dd>
-<dt><span class='term'> <strong>grip</strong></span></dt>
-<dd>…</dd>
-<dt><span class='term'> <strong>guile</strong></span></dt>
-<dd><a href="http://www.gnu.org/software/guile/"; class="urlextern" title="http://www.gnu.org/software/guile/"; rel="nofollow">GNU Guile</a> is an interpreter for Scheme, a version of Lisp.</dd>
-<dt><span class='term'> <strong>HDL</strong></span></dt>
-<dd>Hardware Description Language (e.g., VHDL, Verilog, etc.). Used to simulate or document a device.</dd>
-<dt><span class='term'> <strong>hierarchical</strong></span></dt>
-<dd>The concept that designs can contain nested levels of schematics, so that all the circuit doesnâ??t need to be placed on a single sheet.</dd>
-<dt><span class='term'> <strong>land pattern</strong></span></dt>
-<dd>Also known as a <strong>footprint</strong>. The surface space occupied by a structure or device.</dd>
-<dt><span class='term'> <strong>library</strong></span></dt>
-<dd>A collection of symbols.</dd>
-<dt><span class='term'> <strong>line</strong></span></dt>
-<dd>A straight drawing element, connecting two points. On the schematic it has no electrical significance. In a symbol, a line is part of the symbolâ??s graphic elements.</dd>
-<dt><span class='term'> <strong>model</strong></span></dt>
-<dd>A description of how a device behaves. Most often this is a SPICE model. The model is defined in <strong>gschem</strong>, but used in subsequent applications such as <strong>ngspice</strong>, <strong>gnucap</strong>, etc.</dd>
-<dt><span class='term'> <strong>net</strong></span></dt>
-<dd>A net connects two or more pins on a schematic, and is made up of segments. The netâ??s equivalent is a â??wireâ?? or â??traceâ?? on the printed circuit board.</dd>
-<dt><span class='term'> <strong>object</strong></span></dt>
-<dd>A line, circle, pin, net, box, bus, text/attribute, or picture.</dd>
-<dt><span class='term'> <strong>package</strong></span></dt>
-<dd>Also known as <strong>device</strong>. The equivalent of an [electronics] device, as one may place on a printed circuit board.</dd>
-<dt><span class='term'> <strong>page</strong></span></dt>
-<dd>Also known as a schematicâ??s <strong>sheet</strong>.</dd>
-<dt><span class='term'> <strong>part</strong></span></dt>
-<dd> Also know as <strong>component</strong>. The equivalent of an [electronics] device, as one may place on a printed circuit board.</dd>
-<dt><span class='term'> <strong>project</strong></span></dt>
-<dd>A collection of schematics, custom symbols, models, documentation, etc.</dd>
-<dt><span class='term'> <strong>segment</strong></span></dt>
-<dd>Part of a net. A segment has two end-points, or â??gripsâ??.</dd>
-<dt><span class='term'> <strong>schematic</strong></span></dt>
-<dd>A <strong>page</strong>/<strong>sheet</strong> with electronics symbols, text, and drawing elements (i.e., lines, circles, boxes, etc.) representing a diagram of an electrical or mechanical system.</dd>
-<dt><span class='term'> <strong>series</strong></span></dt>
-<dd>A collection of schematics which share a common basename (e.g., schematic_1.sch, schematic_2.sch, schematic_3.sch, etc.). The series basename ties schematics together.</dd>
-<dt><span class='term'> <strong>slotted device</strong></span></dt>
-<dd>Also known as a <strong>slotted package</strong>. A physical [electronics] device consisting of multiple identical components (e.g., the 7400 quad NAND device consists of 4 identical NAND gates).</dd>
-<dt><span class='term'> <strong>source</strong></span></dt>
-<dd>A schematic, HDL code, or model which implements, describes, or documents some aspect of the project.</dd>
-<dt><span class='term'> <strong>symbol</strong></span></dt>
-<dd>A collection of <strong>objects</strong>. The objects may have <strong>attributes</strong> attatched (i.e., associated) with them. There may also be <strong>attributes</strong> attached (i.e., associated) to the <strong>symbol</strong> itself (i.e., not specifically associated with an object).</dd>
-<dt><span class='term'> <strong>sheet</strong></span></dt>
-<dd>Also known as a schematicâ??s <strong>page</strong>.</dd>
-<dt><span class='term'> <strong>trace</strong></span></dt>
-<dd>The equivalent of a wire on a printed circuit board.</dd>
-<dt><span class='term'> <strong>window</strong></span></dt>
-<dd>…</dd>
-<dt><span class='term'> <strong>workflow</strong></span></dt>
-<dd>The process of designing. Usually includes continuous review and re-design, until it works. In the gEDA Tools Suite design workflow, multiple applications are used. One application typically is followed by another. The flow of data collected and how this data effects the design is considered the workflow.</dd>
-</dl>
-<p>~~DISCUSSION~~
-</p>
-
-</div>
-<!-- SECTION "Appendix H -- Definition of Terms" [122215-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/geda_gschem_warmup.html b/docs/wiki/geda_gschem_warmup.html
deleted file mode 100644
index 3632169..0000000
--- a/docs/wiki/geda_gschem_warmup.html
+++ /dev/null
@@ -1,111 +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>geda:gschem_warmup</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="keywords" content="geda,gschem_warmup" />
-<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/geda:gschem_warmup?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gschem_warmup"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gschem_warmup"; />
-<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">
-
-
-
-<h1><a name="gschem_warmup_for_beginners" id="gschem_warmup_for_beginners">gschem Warmup for Beginners</a></h1>
-<div class="level1">
-
-<p>
- You need to become familiar with doing a few things in <em><strong>gschem</strong></em>, so just run <em><strong>gschem</strong></em> and start playing around:
-</p>
-
-<p>
-You get an initial blank page with a menus and a toolbar at the top. As you select operations from the menus, notice that there are usually keyboard shortcuts which can alternatively be used to access the menu functions.
-</p>
-
-<p>
-When drawing a schematic, Itâ??s a good idea to always start by setting some schematic boundaries to draw within, so we will do this by adding a title-block. I find that using a B sized title-block lets my schematics print at a nice size on letter sized paper:
-</p>
-<ul>
-<li class="level1"><div class="li"> Bring up the <strong>Select Component</strong> window by selecting from the menu <strong>Add→Component</strong> or hit keyboard shortcut <strong>i</strong>. Or you could click the add component icon on the toobar (<a href="_detail/geda_warmup_add_component.html" class="media" title="geda:warmup_add_component.png"><img src="_media/geda_warmup_add_component.png" class="media" alt="" /></a>).</div>
-</li>
-<li class="level1"><div class="li"> In the <strong>Libraries</strong> list, select <strong>title-block</strong>.</div>
-</li>
-<li class="level1"><div class="li"> Under the <strong>Components list</strong>, select <strong>title-B.sym</strong>.</div>
-</li>
-<li class="level1"><div class="li"> Move the mouse onto the <em><strong>gschem</strong></em> drawing area and place the title-block symbol by clicking the left mouse button. Then click the right mouse button to abort adding more title-block symbols.</div>
-</li>
-</ul>
-
-<p>
- <a href="_detail/geda_warmup_gschem01.html" class="media" title="geda:warmup_gschem01.png"><img src="_media/geda_warmup_gschem01.png" class="media" alt="" /></a>
-</p>
-<ul>
-<li class="level1"><div class="li"> With the mouse in the <em><strong>gschem</strong></em> drawing area, hit the keys <strong>ve</strong> (or select from menu <strong>View→Zoom Extents</strong>) to zoom the view to the title-block symbol extents.</div>
-</li>
-<li class="level1"><div class="li"> Back in the select components window, (bring it up again if you closed it), select the <strong>analog</strong> library and then select the component <strong>resistor-1.sym</strong> and place a couple of resistors on the schematic with the left mouse button. Notice that as you place each one it is a red color and that indicates it is selected.</div>
-</li>
-<li class="level1"><div class="li"> Zoom in (keyboard shortcut <strong>z</strong>) and zoom out (keyboard shortcut <strong>SHIFT z</strong>) in the area where you placed the resistors. If you get lost, zoom back to extents with <strong>ve</strong>. Notice that as you zoom in or out the viewable area centers around the mouse cursor.</div>
-</li>
-<li class="level1"><div class="li"> Alternate left clicking on both resistors to select them, but notice that if you donâ??t hit the resistor just right, the title-block is selected instead. We really donâ??t want to ever select the title-block again, so we can lock it to prevent its irritating selection: click so the title-block IS selected, then select <strong>Edit→Lock</strong>. Now itâ??s easier to select the resistors as we like.</div>
-</li>
-<li class="level1"><div class="li"> Move the resistors around with the middle mouse button.</div>
-</li>
-<li class="level1"><div class="li"> Select a resistor and then rotate with the <strong>er</strong> keys or the <strong>Edit→Rotate 90 Mode</strong>.</div>
-</li>
-<li class="level1"><div class="li"> Move the resistors relatively close together and then zoom in on them.</div>
-</li>
-<li class="level1"><div class="li"> Place the mouse on one of the resistor pins and hit the <strong>n</strong> key to start adding a net. Move the mouse to a pin on the other resistor and left click to attach the net to the pin. Right click to abort adding this net but notice that if you left click again you will start adding another net.</div>
-</li>
-</ul>
-
-<p>
- <a href="_detail/geda_warmup_gschem02.html" class="media" title="geda:warmup_gschem02.png"><img src="_media/geda_warmup_gschem02.png" class="media" alt="" /></a>
-</p>
-<ul>
-<li class="level1"><div class="li"> Look at the toolbar and see that your mode has switched to adding nets. Before you can change resistor selections again, you will have to re-enter select mode with the <strong>s</strong> key or by clicking the select toolbar icon or by using the menu <strong>Edit→Select Mode</strong>. But if you try to move a resistor with the middle mouse button, you can do it and you will automatically re-enter select mode. You will have to play with doing things to get used to the <em><strong>gschem</strong></em> modes.</div>
-</li>
-<li class="level1"><div class="li"> If when you added the net between the resistors you get something that looks like this:</div>
-</li>
-</ul>
-
-<p>
- <a href="_detail/geda_warmup_gschem03.html" class="media" title="geda:warmup_gschem03.png"><img src="_media/geda_warmup_gschem03.png" class="media" alt="" /></a>
-</p>
-
-<p>
-it means you missed the pin on the right resistor. Look closely and youâ??ll see the tip of the pin is red and you must start and stop nets with the mouse on this red spot to make a connection to the pin.
-</p>
-<ul>
-<li class="level1"><div class="li"> Select the net between the resistors and delete it with the <strong>Delete</strong> key.</div>
-</li>
-<li class="level1"><div class="li"> Select a resistor and hit the <strong>ee</strong> keys. This will pop up the attribute editing window for the resistor. Here you can change existing attribute values or add new attributes with values to the resistor. Practice well with adding attributes and changing attribute values because you will need to be very familiar with managing attributes when using <em><strong>gschem</strong></em>.</div>
-</li>
-</ul>
-
-<p>
- Now go back to the tutorial and try working through the simple example there. If you encounter steps that arenâ??t clear, look through the <em><strong>gschem</strong></em> user documentation and attributes documentation on the <a href="geda_gschem_ug.html" class="wikilink1" title="geda:gschem_ug">gschem Documentation</a> page.
-</p>
-<hr />
-
-<p>
-tutorial by Bill Wilson (bill–at–gkrellm.net)
-</p>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_gsymcheck_mp.html b/docs/wiki/geda_gsymcheck_mp.html
deleted file mode 100644
index f25fb18..0000000
--- a/docs/wiki/geda_gsymcheck_mp.html
+++ /dev/null
@@ -1,99 +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>geda:gsymcheck_mp</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="geda,gsymcheck_mp" />
-<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/geda:gsymcheck_mp?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gsymcheck_mp"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gsymcheck_mp"; />
-<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">
-
-
-
-<h1><a name="gsymcheck_man-page" id="gsymcheck_man-page">gsymcheck man-page</a></h1>
-<div class="level1">
-<pre class="code">gsymcheck(1) 20031231 gsymcheck(1)
-
-
-
-NAME
- gsymcheck - gEDA/gaf Symbol Checker
-
-SYNOPSIS
- gnetlist [-h] [-v] [-q] symbol1 [... symbolN]
-
-DESCRIPTION
- gsymcheck is a symbol checker for gEDA. Eventually there will be a
- list of checks performed on the symbols listed here.
-
-
-OPTIONS
- gsymcheck accepts the following options:
-
- -q Quiet mode on. This mode turns off all warnings/notes/mes-
- sages. (optional)
-
- -v Verbose mode 1. This mode will show all error messages
- (optional)
-
- -vv Verbose mode 2. This mode will show all error and warning mes-
- sages (optional)
-
- -vvv Verbose mode 2. This mode will show all error, warning, and
- info messages (optional)
-
- -h Usage summary / gsymcheck help
-
- symbol1 [... symbolN]
- At least one symbol file must be specified. If multiple sym-
- bols are specified then they are sequentially read in and
- checked. It is important that the schematic(s) follow all the
- options (ie last).
-
-
-EXAMPLES
- Examples to be listed here eventually
-
-
-ENVIRONMENT
- No environment variables are used.
-
-
-AUTHOR
- Ales Hvezda and many others
-
-
-SEE ALSO
- gschem(1), gnetlist(1)
-
-COPYRIGHT
- Copyright © 1999-2004 Ales Hvezda
-
- This document can be freely redistributed according to the terms of the
- GNU General Public License version 2.0
-
-
-
-
-Version December 31st, 2003 gsymcheck(1)
-</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_gtkwave_lxt2miner_mp.html b/docs/wiki/geda_gtkwave_lxt2miner_mp.html
deleted file mode 100644
index e24dd7a..0000000
--- a/docs/wiki/geda_gtkwave_lxt2miner_mp.html
+++ /dev/null
@@ -1,91 +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>geda:gtkwave_lxt2miner_mp</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="keywords" content="geda,gtkwave_lxt2miner_mp" />
-<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/geda:gtkwave_lxt2miner_mp?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gtkwave_lxt2miner_mp"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gtkwave_lxt2miner_mp"; />
-<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">
-
-
-
-<h1><a name="data_mining_of_lxt2_files_lxt2miner" id="data_mining_of_lxt2_files_lxt2miner">Data mining of LXT2 files (lxt2miner)</a></h1>
-<div class="level1">
-<pre class="code">LXT2MINER(1) Dumpfile Data Mining LXT2MINER(1)
-
-
-
-NAME
- lxt2miner - Data mining of LXT2 files
-
-SYNTAX
- lxt2miner [option]... [LXT2FILE]
-
-DESCRIPTION
- Mines LXT2 files for specific data values and generates gtkwave save
- files to stdout for future reload.
-
-OPTIONS
- -d,--dumpfile <filename>
- Specify LXT2 input dumpfile.
-
- -m,--match <filename>
- Specifies "bitwise" match data (binary, real, string)
-
- -x,--hex <value>
- Specifies hexadecimal match data that will automatically be con-
- verted to binary for searches
-
- -n,--namesonly
- Indicates that only facnames should be printed in a gtkwave
- savefile compatible format. By doing this, the file can be used
- to specify which traces are to be imported into gtkwave.
-
- -h,--help
- Show help screen.
-
-EXAMPLES
- lxt2miner dumpfile.lxt2 --match 20470000 -n
-
- This attempts to match the hex value 20470000 across all facilities and
- when the value is encountered, the facname only is printed to stdout in
- order to generate a gtkwave compatible save file.
-
-LIMITATIONS
- lxt2miner only prints the first time a value is encountered for a spe-
- cific net. This is done in order to cut down on the size of output
- files and to aid in following data such as addresses through a simula-
- tion model.
-
-
-AUTHORS
- Anthony Bybell <bybell@xxxxxxxxx>
-
-SEE ALSO
- vztminer(1) vzt2vcd(1) lxt2vcd(1) vcd2lxt2(1) gtkwave(1)
-
-
-
-Anthony Bybell 1.3.64 LXT2MINER(1)
-</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_gtkwave_lxt2vcd_mp.html b/docs/wiki/geda_gtkwave_lxt2vcd_mp.html
deleted file mode 100644
index acbe10e..0000000
--- a/docs/wiki/geda_gtkwave_lxt2vcd_mp.html
+++ /dev/null
@@ -1,72 +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>geda:gtkwave_lxt2vcd_mp</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="keywords" content="geda,gtkwave_lxt2vcd_mp" />
-<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/geda:gtkwave_lxt2vcd_mp?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gtkwave_lxt2vcd_mp"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gtkwave_lxt2vcd_mp"; />
-<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">
-
-
-
-<h1><a name="coverts_lxt2_files_to_vcd_lxt2vcd" id="coverts_lxt2_files_to_vcd_lxt2vcd">Coverts LXT2 files to VCD (lxt2vcd)</a></h1>
-<div class="level1">
-<pre class="code">LXT2VCD(1) Filetype Conversion LXT2VCD(1)
-
-
-
-NAME
- lxt2vcd - Coverts LXT2 files to VCD
-
-SYNTAX
- lxt2vcd <filename>
-
-DESCRIPTION
- Converts LXT2 files to VCD files on stdout. Note that "regular" LXT2
- files will convert to VCD files with monotonically increasing time val-
- ues. LXT2 files which are dumped with the "partial" option (to speed
- up access in wave viewers) will dump with monotonically increasing time
- values per 2k block of nets. This may be fixed in later versions of
- lxt2vcd.
-
-EXAMPLES
- To run this program the standard way type:
-
- lxt2vcd filename.lxt
- The VCD conversion is emitted to stdout.
-
-LIMITATIONS
- lxt2vcd does not re-create glitches as these are coalesced together
- into one value change during the writing of the LXT2 file.
-
-
-AUTHORS
- Anthony Bybell <bybell@xxxxxxxxx>
-
-SEE ALSO
- vcd2lxt2(1) vcd2lxt(1) gtkwave(1)
-
-
-
-Anthony Bybell 1.3.34 LXT2VCD(1)</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_gtkwave_mp.html b/docs/wiki/geda_gtkwave_mp.html
deleted file mode 100644
index 01f8f6b..0000000
--- a/docs/wiki/geda_gtkwave_mp.html
+++ /dev/null
@@ -1,135 +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>geda:gtkwave_mp</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="keywords" content="geda,gtkwave_mp" />
-<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/geda:gtkwave_mp?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gtkwave_mp"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gtkwave_mp"; />
-<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">
-
-
-
-<h1><a name="visualization_tool_for_vcd_lxt_and_vzt_files_gtkwave" id="visualization_tool_for_vcd_lxt_and_vzt_files_gtkwave">Visualization tool for VCD, LXT, and VZT files (gtkwave)</a></h1>
-<div class="level1">
-<pre class="code">GTKWAVE(1) Simulation Wave Viewer GTKWAVE(1)
-
-
-
-NAME
- gtkwave - Visualization tool for VCD, LXT, and VZT files
-
-SYNTAX
- gtkwave [option]... [DUMPFILE] [SAVEFILE] [RCFILE]
-
-
-DESCRIPTION
- Visualization tool for VCD, LXT, LXT2, and VZT. VCD is an industry
- standard simulation dump format. LXT, LXT2, and VZT have been designed
- specifically for use with gtkwave. Native dumpers exist in Icarus Ver-
- ilog for the LXT formats so conversion with vcd2lxt(1) or vcd2lxt2(1)
- is not necessary to take direct advantage of LXT with that simulator.
- AET2 files can also be processed provided that libae2rw is available
- but this is only of interest to people who use IBM EDA toolsets.
-
-OPTIONS
- -n,--nocli <directory name>
- Use file requester for dumpfile name
-
- -f,--dump <filename>
- Specify dumpfile name.
-
- -r,--rcfile <filename>
- Specify override .gtkwaverc filename.
-
- -i,--indirect <filename>
- Specify indirect facs file name. The file contains a series of
- regular expressions used to limit what signals can be browsed.
- Signal names which match any of the regular expressions will be
- viewable. Typically, indirect files are used to reduce memory
- requirements for extremely large models containing millions of
- facilities or to strip out top-level hierarchy clutter from
- BugSpray models. This feature is only available with the AET2
- loader.
-
- -l,--logfile <filename>
- Specify simulation logfile name. Multiple logfiles may be spec-
- ified by preceeding each with the command flag. By selecting
- the numbers in the text widget, the marker will immediately zoom
- to the specific time value.
-
- -d,--defaultskip
- If there is not a .gtkwaverc file in the home directory or cur-
- rent directory and it is not explicitly specified on the command
- line, when this option is enabled, do not use an implicit con-
- figuration file and instead default to the old "whitescreen"
- behavior.
-
- -s,--start <time>
- Specify start time for LXT2/VZT block skip.
-
- -e,--end <time>
- Specify end time for LXT2/VZT block skip.
-
- -c,--cpu <numcpus>
- Specify number of CPUs available for parallelizable ops (e.g.,
- block prefetching on VZT reads).
-
- -v,--vcd
- Use stdin as a VCD dumpfile.
-
- -V,--version
- Display version banner then exit.
-
- -h,--help
- Display help then exit.
-
- -x,--exit
- Exit after loading trace (for loader benchmarking).
-
-FILES
- ~/.gtkwaverc
-
-
-EXAMPLES
- To run this program the standard way type:
- gtkwave dumpfile.vcd
-
- Alternatively you can run it with a save file as:
- gtkwave dumpfile.vcd dumpfile.sav
-
- Command line options are not necessary for representing the dumpfile,
- savefile, and rcfile names. They are merely provided to allow specify-
- ing them out of order. Note that on non-glibc systems, the long com-
- mand line options will not be available and that the short ones will
- have to be used instead.
-
-AUTHORS
- Anthony Bybell <bybell@xxxxxxxxx>
-
-SEE ALSO
- lxt2vcd(1) vcd2lxt(1) vcd2lxt2(1) vzt2vcd(1) vcd2vzt(1)
-
-
-
-Anthony Bybell 1.3.70 GTKWAVE(1)</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_gtkwave_mvl2lxt_mp.html b/docs/wiki/geda_gtkwave_mvl2lxt_mp.html
deleted file mode 100644
index 96d2a32..0000000
--- a/docs/wiki/geda_gtkwave_mvl2lxt_mp.html
+++ /dev/null
@@ -1,57 +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>geda:gtkwave_mvl2lxt_mp</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-05-24T22:27:26-0400" />
-<meta name="keywords" content="geda,gtkwave_mvl2lxt_mp" />
-<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/geda:gtkwave_mvl2lxt_mp?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gtkwave_mvl2lxt_mp"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gtkwave_mvl2lxt_mp"; />
-<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">
-
-
-
-<h1><a name="coverts_mvlsim_aet_files_to_lxt_mvl2lxt" id="coverts_mvlsim_aet_files_to_lxt_mvl2lxt">Coverts MVLSIM AET files to LXT (mvl2lxt)</a></h1>
-<div class="level1">
-<pre class="code">MVL2LXT(1) Filetype Conversion MVL2LXT(1)
-
-
-
-NAME
- mvl2lxt - Coverts MVLSIM AET files to LXT
-
-SYNTAX
- mvl2lxt <filename.aet> <filename.lxt>
-
-DESCRIPTION
- Converts AET files to LXT. This is experimental as it is not a com-
- plete implementation and is not intended for general use.
-
-AUTHORS
- Anthony Bybell <bybell@xxxxxxxxx>
-
-SEE ALSO
- tex2vcd(1) mvl2vcd(1) lxt2vcd(1) vcd2lxt2(1) vcd2lxt(1) gtkwave(1)
-
-
-
-Anthony Bybell 1.3.34 MVL2LXT(1)</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_gtkwave_mvl2vcd_mp.html b/docs/wiki/geda_gtkwave_mvl2vcd_mp.html
deleted file mode 100644
index 195f8bf..0000000
--- a/docs/wiki/geda_gtkwave_mvl2vcd_mp.html
+++ /dev/null
@@ -1,58 +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>geda:gtkwave_mvl2vcd_mp</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-05-24T22:27:26-0400" />
-<meta name="keywords" content="geda,gtkwave_mvl2vcd_mp" />
-<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/geda:gtkwave_mvl2vcd_mp?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gtkwave_mvl2vcd_mp"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gtkwave_mvl2vcd_mp"; />
-<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">
-
-
-
-<h1><a name="coverts_mvlsim_aet_files_to_vcd_mvl2vcd" id="coverts_mvlsim_aet_files_to_vcd_mvl2vcd">Coverts MVLSIM AET files to VCD (mvl2vcd)</a></h1>
-<div class="level1">
-<pre class="code">MVL2VCD(1) Filetype Conversion MVL2VCD(1)
-
-
-
-NAME
- mvl2vcd - Coverts MVLSIM AET files to VCD
-
-SYNTAX
- mvl2vcd <filename.aet>
-
-DESCRIPTION
- Converts AET files to VCD on stdout. This is experimental as it is not
- a complete implementation and is not intended for general use.
-
-AUTHORS
- Anthony Bybell <bybell@xxxxxxxxx>
-
-SEE ALSO
- tex2vcd(1) mvl2lxt(1) lxt2vcd(1) vcd2lxt2(1) vcd2lxt(1) gtkwave(1)
-
-
-
-Anthony Bybell 1.3.34 MVL2VCD(1)
-</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_gtkwave_tex2vcd_mp.html b/docs/wiki/geda_gtkwave_tex2vcd_mp.html
deleted file mode 100644
index 6ab0dcd..0000000
--- a/docs/wiki/geda_gtkwave_tex2vcd_mp.html
+++ /dev/null
@@ -1,57 +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>geda:gtkwave_tex2vcd_mp</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-05-24T22:27:26-0400" />
-<meta name="keywords" content="geda,gtkwave_tex2vcd_mp" />
-<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/geda:gtkwave_tex2vcd_mp?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gtkwave_tex2vcd_mp"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gtkwave_tex2vcd_mp"; />
-<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">
-
-
-
-<h1><a name="coverts_texsim_aet_files_to_vcd_tex2vcd" id="coverts_texsim_aet_files_to_vcd_tex2vcd">Coverts TEXSIM AET files to VCD (tex2vcd)</a></h1>
-<div class="level1">
-<pre class="code">TEX2VCD(1) Filetype Conversion TEX2VCD(1)
-
-
-
-NAME
- tex2vcd - Coverts TEXSIM AET files to VCD
-
-SYNTAX
- mvl2vcd <filename.aet>
-
-DESCRIPTION
- Converts AET files to VCD on stdout. This is experimental as it is not
- a complete implementation and is not intended for general use.
-
-AUTHORS
- Anthony Bybell <bybell@xxxxxxxxx>
-
-SEE ALSO
- mvl2vcd(1) mvl2lxt(1) lxt2vcd(1) vcd2lxt2(1) vcd2lxt(1) gtkwave(1)
-
-
-
-Anthony Bybell 1.3.34 TEX2VCD(1)</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_gtkwave_tla2vcd_mp.html b/docs/wiki/geda_gtkwave_tla2vcd_mp.html
deleted file mode 100644
index c6aa055..0000000
--- a/docs/wiki/geda_gtkwave_tla2vcd_mp.html
+++ /dev/null
@@ -1,75 +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>geda:gtkwave_tla2vcd_mp</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="keywords" content="geda,gtkwave_tla2vcd_mp" />
-<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/geda:gtkwave_tla2vcd_mp?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gtkwave_tla2vcd_mp"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gtkwave_tla2vcd_mp"; />
-<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">
-
-
-
-<h1><a name="converts_tla_to_vcd_or_lst_files_tla2vcd" id="converts_tla_to_vcd_or_lst_files_tla2vcd">Converts TLA to VCD or LST files (tla2vcd)</a></h1>
-<div class="level1">
-<pre class="code">TLA2VCD(1) Tektronix File Format Conversion TLA2VCD(1)
-
-
-
-NAME
- tla2vcd - Converts TLA to VCD or LST files
-
-SYNTAX
- tla2vcd [option]... TLAFILE [[TLAFILE]...]
-
-
-DESCRIPTION
- Converts TLA files from Tektronix logic analyzers to VCD or LST files.
- Conversion to VCD allows viewing in tools such as gtkwave(1).
-
-OPTIONS
- -t Generate text LST file instead of VCD file
-
- -l List the available channels/groups and exit
-
- -s <signal_list>
- Select signals from regular expression list
-
- -a All channels
-
- -m Append MagniVu info (only in listing mode)
-
- -z Compress output
-
- -v Verbose
-
-
-AUTHORS
- Emil
-
-SEE ALSO
- lxt2vcd(1) vzt2vcd(1) gtkwave(1)
-
-
-
-Emil 1.0 TLA2VCD(1)</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_gtkwave_vcd2lxt2_mp.html b/docs/wiki/geda_gtkwave_vcd2lxt2_mp.html
deleted file mode 100644
index 6feddeb..0000000
--- a/docs/wiki/geda_gtkwave_vcd2lxt2_mp.html
+++ /dev/null
@@ -1,108 +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>geda:gtkwave_vcd2lxt2_mp</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="keywords" content="geda,gtkwave_vcd2lxt2_mp" />
-<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/geda:gtkwave_vcd2lxt2_mp?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gtkwave_vcd2lxt2_mp"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gtkwave_vcd2lxt2_mp"; />
-<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">
-
-
-
-<h1><a name="converts_vcd_files_to_lxt2_files_vcd2lxt2" id="converts_vcd_files_to_lxt2_files_vcd2lxt2">Converts VCD files to LXT2 files (vcd2lxt2)</a></h1>
-<div class="level1">
-<pre class="code">VCD2LXT2(1) Filetype Conversion VCD2LXT2(1)
-
-
-
-NAME
- vcd2lxt2 - Converts VCD files to LXT2 files
-
-SYNTAX
- vcd2lxt2 [option]... [VCDFILE] [LXTFILE]
-
-DESCRIPTION
- Converts VCD files to LXT2 files.
-
-OPTIONS
- -v,--vcdname <filename>
- Specify VCD input filename.
-
- -l,--lxtname <filename>
- Specify LXT2 output filename.
-
- -d,--depth <value>
- Specify 0..9 gzip compression depth, default is 4.
-
- -m,--maxgranule <value>
- Specify number of granules per section, default is 8. One gran-
- ule is equal to 32 timsteps.
-
- -b,--break <value>
- Specify break size (default = 0 = off). When the break size is
- exceeded, the LXT2 dumper will dump all state information at the
- next convenient granule plus dictionary boundary.
-
- -p,--partialmode <mode>
- Specify partial zip mode 0 = monolithic, 1 = separation. Using
- a value of 1 expands LXT2 filesize but provides fast access for
- very large traces. Note that the default mode is neither mono-
- lithic nor separation: partial zip is disabled.
-
- -c,--checkpoint <mode>
- Specify checkpoint mode. 0 is on which is default, and 1 is
- off. This is disabled when the break size is active.
-
- -h,--help
- Show help screen.
-
-
-
- EXAMPLES
-
- Note that you should specify dumpfile.vcd directly or use "-" for
- stdin.
-
- vcd2lxt dumpfile.vcd dumpfile.lxt --depth 9 --break 1073741824
- This sets the compression level to 9 and sets the break size to
- 1GB.
-
- vcd2lxt dumpfile.vcd dumpfile.lxt --depth 9 --maxgranule 256
- Allows more granules per section which allows for greater com-
- pression.
-
-LIMITATIONS
- vcd2lxt2 does not store glitches as these are coalesced together into
- one value change during the writing of the LXT2 file.
-
-
-AUTHORS
- Anthony Bybell <bybell@xxxxxxxxx>
-
-SEE ALSO
- lxt2vcd(1) vcd2lxt2(1) gtkwave(1)
-
-
-
-Anthony Bybell 1.3.42 VCD2LXT2(1)</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_gtkwave_vcd2lxt_mp.html b/docs/wiki/geda_gtkwave_vcd2lxt_mp.html
deleted file mode 100644
index 49ea706..0000000
--- a/docs/wiki/geda_gtkwave_vcd2lxt_mp.html
+++ /dev/null
@@ -1,95 +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>geda:gtkwave_vcd2lxt_mp</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="keywords" content="geda,gtkwave_vcd2lxt_mp" />
-<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/geda:gtkwave_vcd2lxt_mp?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gtkwave_vcd2lxt_mp"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gtkwave_vcd2lxt_mp"; />
-<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">
-
-
-
-<h1><a name="converts_vcd_files_to_interlaced_or_linear_lxt_files_vcd2lxt" id="converts_vcd_files_to_interlaced_or_linear_lxt_files_vcd2lxt">Converts VCD files to interlaced or linear LXT files (vcd2lxt)</a></h1>
-<div class="level1">
-<pre class="code">VCD2LXT(1) Filetype Conversion VCD2LXT(1)
-
-
-
-NAME
- vcd2lxt - Converts VCD files to interlaced or linear LXT files
-
-SYNTAX
- vcd2lxt [VCDFILE] [LXTFILE] [option]...
-
-DESCRIPTION
- Converts VCD files to interlaced or linear LXT files. Noncompressed
- interlaced files will provide the fastest access, linear files will
- provide the slowest yet have the greatest compression ratios.
-
-OPTIONS
- -stats Prints out statistics on all nets in VCD file in addition to
- performing the conversion.
-
- -clockpack
- Apply two-way subtraction algorithm in order to identify nets
- whose value changes by a constant XOR or whose value
- increases/decreases by a constant amount per constant unit of
- time. This option can reduce dumpfile size dramatically as
- value changes can be represented by an equation rather than
- explicitly as a triple of time, net, and value.
-
- -chgpack
- Emit data to file after being filtered through zlib (gzip).
-
- -linear
- Write out LXT in "linear" format with no backpointers. These
- are re-generated during initialization in gtkwave. Addition-
- ally, use libbz2 (bzip2) as the compression filter.
-
- -dictpack <size>
- Store value changes greater than or equal to size bits as an
- index into a dictionary. Experimentation shows that a value of
- 18 is optimal for most cases.
-
-EXAMPLES
- Note that you should specify dumpfile.vcd directly or use "-" for
- stdin.
-
- vcd2lxt dumpfile.vcd dumpfile.lxt -clockpack -chgpack -dictpack 18
- This turns on clock packing, zlib compression, and enables the
- dictionary encoding. Note that using no options writes out a
- normal LXT file.
-
- vcd2lxt dumpfile.vcd dumpfile.lxt -clockpack -linear -dictpack 18
- Uses linear mode for even smaller files.
-
-AUTHORS
- Anthony Bybell <bybell@xxxxxxxxx>
-
-SEE ALSO
- lxt2vcd(1) vcd2lxt2(1) gtkwave(1)
-
-
-
-Anthony Bybell 1.3.34 VCD2LXT(1)</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_gtkwave_vcd2vzt_mp.html b/docs/wiki/geda_gtkwave_vcd2vzt_mp.html
deleted file mode 100644
index 612fdaa..0000000
--- a/docs/wiki/geda_gtkwave_vcd2vzt_mp.html
+++ /dev/null
@@ -1,117 +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>geda:gtkwave_vcd2vzt_mp</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="keywords" content="geda,gtkwave_vcd2vzt_mp" />
-<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/geda:gtkwave_vcd2vzt_mp?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gtkwave_vcd2vzt_mp"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gtkwave_vcd2vzt_mp"; />
-<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">
-
-
-
-<h1><a name="converts_vcd_files_to_vzt_files_vcd2vzt" id="converts_vcd_files_to_vzt_files_vcd2vzt">Converts VCD files to VZT files (vcd2vzt)</a></h1>
-<div class="level1">
-<pre class="code">VCD2VZT(1) Filetype Conversion VCD2VZT(1)
-
-
-
-NAME
- vcd2vzt - Converts VCD files to VZT files
-
-SYNTAX
- vcd2vzt [option]... [VCDFILE] [VZTFILE]
-
-DESCRIPTION
- Converts VCD files to VZT files.
-
-OPTIONS
- -v,--vcdname <filename>
- Specify VCD input filename.
-
- -l,--vztname <filename>
- Specify VZT output filename.
-
- -d,--depth <value>
- Specify 0..9 gzip compression depth, default is 4.
-
- -m,--maxgranule <value>
- Specify number of granules per section, default is 8. One gran-
- ule is equal to 32 timesteps.
-
- -b,--break <value>
- Specify break size (default = 0 = off). When the break size is
- exceeded, the VZT dumper will dump all state information at the
- next convenient granule plus dictionary boundary.
-
- -z,--ziptype <value>
- Specify zip type (default = 0 gzip, 1 = bzip2). This allows you
- to override the default compression algorithm to use a more
- effective one at the expense of greater runtime. Note that
- bzip2 does not decompress as fast as gzip so the viewer will be
- about two times slower when decompressing blocks.
-
- -t,--twostate
- Forces MVL2 twostate mode (default is MVL4). When enabled, the
- trace will only store 0/1 values for binary facilities. This is
- useful for functional simulation and will speed up dumping as
- well as make traces somewhat smaller.
-
- -r, --rle
- Uses an bitwise RLE compression on the value table. Default is
- off. When enabled, this causes the trace data table to be
- stored using an alternate representation which can improve com-
- pression in many cases.
-
- -h,--help
- Show help screen.
-
-
-
- EXAMPLES
-
- Note that you should specify dumpfile.vcd directly or use "-" for
- stdin.
-
- vcd2vzt dumpfile.vcd dumpfile.lxt --depth 9 --break 1073741824
- This sets the compression level to 9 and sets the break size to
- 1GB.
-
- vcd2vzt dumpfile.vcd dumpfile.lxt --depth 9 --maxgranule 512
- Allows more granules per section which allows for greater com-
- pression at the expense of memory usage.
-
-LIMITATIONS
- vcd2vzt does not store glitches as these are coalesced together into
- one value change during the writing of the VZT file.
-
-
-AUTHORS
- Anthony Bybell <bybell@xxxxxxxxx>
-
-SEE ALSO
- vzt2vcd(1) lxt2vcd(1) vcd2lxt2(1) gtkwave(1)
-
-
-
-Anthony Bybell 1.3.48 VCD2VZT(1)</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_gtkwave_vzt2vcd_mp.html b/docs/wiki/geda_gtkwave_vzt2vcd_mp.html
deleted file mode 100644
index 55d1b1f..0000000
--- a/docs/wiki/geda_gtkwave_vzt2vcd_mp.html
+++ /dev/null
@@ -1,67 +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>geda:gtkwave_vzt2vcd_mp</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="keywords" content="geda,gtkwave_vzt2vcd_mp" />
-<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/geda:gtkwave_vzt2vcd_mp?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gtkwave_vzt2vcd_mp"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gtkwave_vzt2vcd_mp"; />
-<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">
-
-
-
-<h1><a name="coverts_vzt_files_to_vcd_vzt2vcd" id="coverts_vzt_files_to_vcd_vzt2vcd">Coverts VZT files to VCD (vzt2vcd)</a></h1>
-<div class="level1">
-<pre class="code">VZT2VCD(1) Filetype Conversion VZT2VCD(1)
-
-
-
-NAME
- vzt2vcd - Coverts VZT files to VCD
-
-SYNTAX
- vzt2vcd <filename>
-
-DESCRIPTION
- Converts VZT files to VCD files on stdout.
-
-EXAMPLES
- To run this program the standard way type:
-
- vzt2vcd filename.vzt
- The VCD conversion is emitted to stdout.
-
-LIMITATIONS
- vzt2vcd does not re-create glitches as these are coalesced together
- into one value change during the writing of the VZT file.
-
-
-AUTHORS
- Anthony Bybell <bybell@xxxxxxxxx>
-
-SEE ALSO
- vcd2lxt2(1) vcd2lxt(1) lxt2vcd(1) gtkwave(1)
-
-
-
-Anthony Bybell 1.3.44 VZT2VCD(1)</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_gtkwave_vztminer_mp.html b/docs/wiki/geda_gtkwave_vztminer_mp.html
deleted file mode 100644
index 1388a7a..0000000
--- a/docs/wiki/geda_gtkwave_vztminer_mp.html
+++ /dev/null
@@ -1,90 +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>geda:gtkwave_vztminer_mp</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="keywords" content="geda,gtkwave_vztminer_mp" />
-<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/geda:gtkwave_vztminer_mp?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:gtkwave_vztminer_mp"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:gtkwave_vztminer_mp"; />
-<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">
-
-
-
-<h1><a name="data_mining_of_vzt_files_vztminer" id="data_mining_of_vzt_files_vztminer">Data mining of VZT files (vztminer)</a></h1>
-<div class="level1">
-<pre class="code">VZTMINER(1) Dumpfile Data Mining VZTMINER(1)
-
-
-
-NAME
- vztminer - Data mining of VZT files
-
-SYNTAX
- vztminer [option]... [VZTFILE]
-
-DESCRIPTION
- Mines VZT files for specific data values and generates gtkwave save
- files to stdout for future reload.
-
-OPTIONS
- -d,--dumpfile <filename>
- Specify VZT input dumpfile.
-
- -m,--match <filename>
- Specifies "bitwise" match data (binary, real, string)
-
- -x,--hex <value>
- Specifies hexadecimal match data that will automatically be con-
- verted to binary for searches
-
- -n,--namesonly
- Indicates that only facnames should be printed in a gtkwave
- savefile compatible format. By doing this, the file can be used
- to specify which traces are to be imported into gtkwave.
-
- -h,--help
- Show help screen.
-
-EXAMPLES
- vztminer dumpfile.vzt --match 20470000 -n
-
- This attempts to match the hex value 20470000 across all facilities and
- when the value is encountered, the facname only is printed to stdout in
- order to generate a gtkwave compatible save file.
-
-LIMITATIONS
- vztminer only prints the first time a value is encountered for a spe-
- cific net. This is done in order to cut down on the size of output
- files and to aid in following data such as addresses through a simula-
- tion model.
-
-
-AUTHORS
- Anthony Bybell <bybell@xxxxxxxxx>
-
-SEE ALSO
- lxt2miner(1) vzt2vcd(1) lxt2vcd(1) vcd2lxt2(1) gtkwave(1)
-
-
-
-Anthony Bybell 1.3.64 VZTMINER(1)</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_guile_scripting.html b/docs/wiki/geda_guile_scripting.html
deleted file mode 100644
index df3e372..0000000
--- a/docs/wiki/geda_guile_scripting.html
+++ /dev/null
@@ -1,236 +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>geda:guile_scripting</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-12-20T12:38:57-0500" />
-<meta name="keywords" content="geda,guile_scripting" />
-<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/geda:guile_scripting?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:guile_scripting"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:guile_scripting"; />
-<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="clear">
-
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#guile_scripting_reference" class="toc">Guile scripting reference</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#libgeda_c_library" class="toc">libgeda C library</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#libgeda_geda.scm" class="toc">libgeda geda.scm</a></span></div></li></ul>
-</li></ul>
-</li></ul>
-</div>
-</div>
-
-
-
-<h2><a name="guile_scripting_reference" id="guile_scripting_reference">Guile scripting reference</a></h2>
-<div class="level2">
-
-</div>
-<!-- SECTION "Guile scripting reference" [1-39] -->
-<h3><a name="libgeda_c_library" id="libgeda_c_library">libgeda C library</a></h3>
-<div class="level3">
-
-<p>
- libgeda defines a number of low-level functions in C for configuring its behaviour and manipulating features such as the component and subcircuit libraries.
-</p>
-
-</div>
-
-<h4><a name="types" id="types">Types</a></h4>
-<div class="level4">
-<ul>
-<li class="level1"><div class="li"> attribute</div>
-</li>
-<li class="level1"><div class="li"> object</div>
-</li>
-<li class="level1"><div class="li"> page</div>
-</li>
-</ul>
-
-</div>
-
-<h4><a name="variables" id="variables">Variables</a></h4>
-<div class="level4">
-
-<p>
- Basic configuration (defined by libgeda, read-only)
-</p>
-<ul>
-<li class="level1"><div class="li"> path-sep</div>
-</li>
-<li class="level1"><div class="li"> geda-rc-path</div>
-</li>
-<li class="level1"><div class="li"> geda-data-path</div>
-</li>
-</ul>
-
-<p>
- Object type identifiers (defined by libgeda, read-only)
-</p>
-<ul>
-<li class="level1"><div class="li"> OBJ_LINE</div>
-</li>
-<li class="level1"><div class="li"> OBJ_BOX</div>
-</li>
-<li class="level1"><div class="li"> OBJ_PICTURE</div>
-</li>
-<li class="level1"><div class="li"> OBJ_CIRCLE</div>
-</li>
-<li class="level1"><div class="li"> OBJ_NET</div>
-</li>
-<li class="level1"><div class="li"> OBJ_BUS</div>
-</li>
-<li class="level1"><div class="li"> OBJ_COMPLEX</div>
-</li>
-<li class="level1"><div class="li"> OBJ_TEXT</div>
-</li>
-<li class="level1"><div class="li"> OBJ_<acronym title="Personal Identification Number">PIN</acronym></div>
-</li>
-<li class="level1"><div class="li"> OBJ_ARC</div>
-</li>
-<li class="level1"><div class="li"> OBJ_ROUTE</div>
-</li>
-<li class="level1"><div class="li"> OBJ_THRU_HOLE</div>
-</li>
-<li class="level1"><div class="li"> OBJ_PLACEHOLDER</div>
-</li>
-</ul>
-
-</div>
-
-<h4><a name="functions" id="functions">Functions</a></h4>
-<div class="level4">
-
-<p>
- Component library:
-</p>
-<ul>
-<li class="level1"><div class="li"> component-library</div>
-</li>
-<li class="level1"><div class="li"> component-library-command</div>
-</li>
-<li class="level1"><div class="li"> component-library-funcs</div>
-</li>
-<li class="level1"><div class="li"> component-library-search</div>
-</li>
-<li class="level1"><div class="li"> reset-component-library</div>
-</li>
-</ul>
-
-<p>
- Subcircuit library:
-</p>
-<ul>
-<li class="level1"><div class="li"> source-library</div>
-</li>
-<li class="level1"><div class="li"> source-library-search</div>
-</li>
-<li class="level1"><div class="li"> reset-source-library</div>
-</li>
-</ul>
-
-<p>
- Libgeda behaviour configuration (write-only):
-</p>
-<ul>
-<li class="level1"><div class="li"> always-promote-attributes</div>
-</li>
-<li class="level1"><div class="li"> attribute-promotion</div>
-</li>
-<li class="level1"><div class="li"> bitmap-directory</div>
-</li>
-<li class="level1"><div class="li"> bus-ripper-symname</div>
-</li>
-<li class="level1"><div class="li"> default-series-name</div>
-</li>
-<li class="level1"><div class="li"> font-directory</div>
-</li>
-<li class="level1"><div class="li"> keep-invisible</div>
-</li>
-<li class="level1"><div class="li"> map-font-character-to-file</div>
-</li>
-<li class="level1"><div class="li"> postscript-prolog</div>
-</li>
-<li class="level1"><div class="li"> promote-invisible</div>
-</li>
-<li class="level1"><div class="li"> scheme-directory</div>
-</li>
-<li class="level1"><div class="li"> untitled-name</div>
-</li>
-<li class="level1"><div class="li"> world-size</div>
-</li>
-</ul>
-
-<p>
- Smob type manipulators:
-</p>
-<ul>
-<li class="level1"><div class="li"> get-attribute-name-value</div>
-</li>
-<li class="level1"><div class="li"> get-attribute-bounds</div>
-</li>
-<li class="level1"><div class="li"> get-attribute-angle</div>
-</li>
-<li class="level1"><div class="li"> calcule-new-attrib-bounds</div>
-</li>
-<li class="level1"><div class="li"> get-object-attributes</div>
-</li>
-<li class="level1"><div class="li"> get-attrib-value-by-attrib-name</div>
-</li>
-<li class="level1"><div class="li"> get-object-type</div>
-</li>
-<li class="level1"><div class="li"> get-line-width</div>
-</li>
-<li class="level1"><div class="li"> get-page-filename</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "libgeda C library" [40-1504] -->
-<h3><a name="libgeda_geda.scm" id="libgeda_geda.scm">libgeda geda.scm</a></h3>
-<div class="level3">
-
-<p>
- geda.scm, installed with libgeda, provides several useful functions for doing simple manipulation of paths and files, as well as loading rc files from gafrc.d directories.
-</p>
-
-</div>
-
-<h4><a name="functions1" id="functions1">Functions</a></h4>
-<div class="level4">
-<ul>
-<li class="level1"><div class="li"> build-path</div>
-</li>
-<li class="level1"><div class="li"> regular-file?</div>
-</li>
-<li class="level1"><div class="li"> directory?</div>
-</li>
-<li class="level1"><div class="li"> has-suffix?</div>
-</li>
-<li class="level1"><div class="li"> load-scheme-dir</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "libgeda geda.scm" [1505-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/geda_hse_howto.html b/docs/wiki/geda_hse_howto.html
deleted file mode 100644
index 4138f61..0000000
--- a/docs/wiki/geda_hse_howto.html
+++ /dev/null
@@ -1,149 +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>geda:hse_howto</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="keywords" content="geda,hse_howto" />
-<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/geda:hse_howto?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:hse_howto"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:hse_howto"; />
-<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">
-
-
-
-<h1><a name="hooks_scheme_extension_howto" id="hooks_scheme_extension_howto">Hooks/Scheme Extension HOWTO</a></h1>
-<div class="level1">
-<pre class="code">gEDA - GPL Electronic Design Automation
-
-HOOKS AND SCHEME EXTENSION IN GSCHEM
-====================================
-
-Copyright (C) 2000 Stefan Petersen
-
-This program is free software; you can redistribute it and/or modify
-it under the terms of the GNU General Public License as published by
-the Free Software Foundation; either version 2 of the License, or
-(at your option) any later version.
-
-This program is distributed in the hope that it will be useful,
-but WITHOUT ANY WARRANTY; without even the implied warranty of
-MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
-GNU General Public License for more details.
-
-You should have received a copy of the GNU General Public License
-along with this program; if not, write to the Free Software
-Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
-
-
-Introduction
-------------
-gschem has a scheme interpreter (called Guile) built in. Though not
-complete, there are extensions to this interpreter to get access to
-different parts of the schematic.
-
-There are a couple of other scheme extensions available that will not be
-described here. They belong mainly to rc-files (resource files in
-gEDA programs are really scheme scripts) and to the keymapping system
-(described in separate keymapping documentation).
-
-The rest I will try to describe here.
-
-
-Scheme functions
-----------------
-There are two function available for handling attributes in the schematic.
-
-* get-attribute-name-value
-Inparameter : an attribute
-Outparameter : a pair with the name of the attribute as string in the
- car element and the value of the attribute in the cdr
- element.
-Description : Simply an accessor to the information hidden in the type
- attribute. The functionality of this is placed in libgeda
- since the C-type ATTRIBUTE is defined there.
-
-* set-attribute-value!
-Inparameter : an attribute and a string.
-Outparameter : undefined.
-Description : Sets a new value to an attribute. The attribute must
- be defined, the function can't create a new attribute.
- Defined both in gschem and libgeda, mainly because
- where different variables and information are available.
-
-
-Hooks
------
-Hooks are a way to define functions that will be called during different
-part of a programs execution. In gschem there are (currently) three
-different hooks available:
-* add-component-hook
-* copy-component-hook
-* move-component-hook
-
-As their name indicate, they are called at different occasions. When
-you add a component add-component-hook is called, etc.
-
-To add a function to be called you simply use the Guile funtion add-hook!.
-An example; to run the function auto-uref when you add a component you
-simply add the following line, preferrably in ${HOME}/.gEDA/gschemrc:
-(add-hook! add-component-hook auto-uref)
-
-The function to be called from a hook (for example auto-uref above) has
-to accept one parameter, a list of attributes.
-
-A small example that prints all attributes on a component to be placed:
-
-(define (print-all-attributes attribute-list)
- (foreach (lambda (attribute) (display attribute)) attribute-list))
-
-
-How to use this
----------------
-The most complete example utilizing all of the above functions are in fact
-the auto-uref scheme script that currently is part of the gschem distribution.
-You can find it <where gschem is installed>/share/gEDA/scheme/auto-uref.scm.
-Uninstalled it's available at gschem/scheme/auto-uref.scm
-
-All components have a reference designator that must be unique so
-gnetlist can handle it properly. By automatically assigning a number
-to each instance of a component when you place and copy it, you can
-simplify the naming operation.
-
-All components has, per default, an uref attribute, for example uref=R?.
-The letter varies with component type. The auto-uref script enumerates
-uref based on what prefix the component has and assigns a number.
-
-For example, the first component you place has per default uref=U? gets
-the attribute uref=U1. Next component with uref=U? gets uref=U2 and so on.
-
-To be able to use the auto-uref script you simply add two lines in
-${HOME}/.gEDA/gschemrc. They are:
-(load "<where gschem is installed>/share/gEDA/scheme/auto-uref.scm")
-(add-hook! add-component-hook auto-uref)
-
-If you want auto enumeration to work when you copy the component too, you
-simply add the following line:
-(add-hook! copy-component-hook auto-uref)
-
-Good luck!
-
-</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_icarus_anc.html b/docs/wiki/geda_icarus_anc.html
deleted file mode 100644
index 53db137..0000000
--- a/docs/wiki/geda_icarus_anc.html
+++ /dev/null
@@ -1,118 +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>geda:icarus_anc</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="keywords" content="geda,icarus_anc" />
-<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/geda:icarus_anc?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:icarus_anc"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:icarus_anc"; />
-<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">
-
-
-
-<h1><a name="icarus_attribute_naming_conventions" id="icarus_attribute_naming_conventions">Icarus Attribute Naming Conventions</a></h1>
-<div class="level1">
-<pre class="code">ATTRIBUTE NAMING CONVENTIONS
-
-Attributes that are specific to Icarus Verilog, and are intended to be
-of use to programmers, start with the prefix "ivl_".
-
-Attributes with the "_ivl_" prefix are set aside for internal
-use. They may be generated internally by the compiler. They need not
-be documented here.
-
-ATTRIBUTES TO CONTROL SYNTHESIS
-
-The following is a summary of Verilog attributes that Icarus Verilog
-understands within Verilog source files to control synthesis
-behavior. This section documents generic synthesis attributes. For
-target specific attributes, see target specific documentation.
-
-These attributes only effect the behavior of the synthesizer. For
-example, the ivl_combinational will not generate an error message
-if the Verilog is being compiled for simulation. (It may generate a
-warning.)
-
-
-* Attributes for "always" and "initial" statements
-
-(* ivl_combinational *)
-
- This attribute tells the compiler that the statement models
- combinational logic. If the compiler finds that it cannot make
- combinational logic out of a marked always statement, it will
- report an error.
-
- This attribute can be used to prevent accidentally inferring
- latches or flip-flops where the user intended combinational
- logic.
-
-(* ivl_synthesis_on *)
-
- This attribute tells the compiler that the marked always statement
- is synthesizable. The compiler will attempt to synthesize the
- code in the marked "always" statement. If it cannot in any way
- synthesize it, then it will report an error.
-
-(* ivl_synthesis_off *)
-
- If this value is attached to an "always" statement, then the
- compiler will *not* synthesize the "always" statement. This can be
- used, for example, to mark embedded test bench code.
-
-
-* Attributes for modules
-
-(* ivl_synthesis_cell *)
-
- If this value is attached to a module during synthesis, that
- module will be considered a target architecture primitive, and
- its interior will not be synthesized further. The module can
- therefore hold a model for simulation purposes.
-
-
-* Attributes for signals (wire/reg/integer/tri/etc.)
-
-(* PAD = "<pad assignment list>" *)
-
- If this attribute is attached to a signal that happens to be a
- root module port, then targets that support it will use the string
- value as a list of pin assignments for the port/signal. The format
- is a comma separated list of location tokens, with the format of
- the token itself defined by the back-end tools in use.
-
-* Other Attributes
-
-[ none defined yet ]
-
-
-MISC
-
-(* _ivl_schedule_push *)
-
- If this attribute is attached to a thread object (always or
- initial statement) then the vvp code generator will generate code
- that causes the scheduler to push this thread at compile time. The
- compiler may internally add this attribute to always statements if
- it detects that it is combinational. This helps resolve time-0
- races.</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_icarus_extensions.html b/docs/wiki/geda_icarus_extensions.html
deleted file mode 100644
index 5add6c6..0000000
--- a/docs/wiki/geda_icarus_extensions.html
+++ /dev/null
@@ -1,117 +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>geda:icarus_extensions</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="keywords" content="geda,icarus_extensions" />
-<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/geda:icarus_extensions?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:icarus_extensions"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:icarus_extensions"; />
-<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">
-
-
-
-<h1><a name="icarus_verilog_extensions" id="icarus_verilog_extensions">Icarus Verilog Extensions</a></h1>
-<div class="level1">
-<pre class="code">Icarus Verilog Extensions
-
-Icarus Verilog supports certain extensions to the baseline IEEE1364
-standard. Some of these are picked from extended variants of the
-language, such as SystemVerilog, and some are expressions of internal
-behavior of Icarus Verilog, made available as a tool debugging aid.
-
-* Builtin System Functions
-
-** Extended Verilog Data Types
-
-This feature is turned off if the generation flag "-g" is set to other
-then the default "2x". For example, "iverilog -g2x" enables extended
-data types, and "iverilog -g2" disables them.
-
-Icarus Verilog adds support for extended data types. This extended
-type syntax is based on a proposal by Cadence Design Systems,
-originally as an update to the IEEE1364. That original proposal has
-apparently been absorbed by the IEEE1800 SystemVerilog
-standard. Icarus Verilog currently only takes the new primitive types
-from the proposal.
-
-Extended data types separates the concept of net/variable from the
-data type. Both nets and variables can declared with any data
-type. The primitive types available are:
-
- logic - The familiar 0, 1, x and z, optionally with strength.
- bool - Limited to only 0 and 1
- real - 64bit real values
-
-Nets with logic type may have multiple drivers with strength, and the
-value is resolved the usual way. Only logic values may be driven to
-logic nets, so bool values driven onto logic nets are implicitly
-converted to logic.
-
-Nets with any other type may not have multiple drivers. The compiler
-should detect the multiple drivers and report an error.
-
-- Declarations
-
-The declaration of a net is extended to include the type of the wire,
-with the syntax:
-
- wire <type> <wire-assignment-list>... ;
-
-The <type>, if omitted, is taken to be logic. The "wire" can be any of
-the net keywords. Wires can be logic, bool, real, or vectors of logic
-or bool. Some valid examples:
-
- wire real foo = 1.0;
- tri logic bus[31:0];
- wire bool addr[23:0];
- ... and so on.
-
-The declarations of variables is similar. The "reg" keyword is used to
-specify that this is a variable. Variables can have the same data
-types as nets.
-
-- Ports
-
-Module and task ports in standard verilog are restricted to logic
-types. This extension removes that restriction, allowing any type to
-pass through the port consistent with the continuous assignment
-connectivity that is implied by the type.
-
-- Expressions
-
-Expressions in the face of real values is covered by the baseline
-Verilog standard.
-
-The bool type supports the same operators as the logic type, with the
-obvious differences imposed by the limited domain.
-
-Comparison operators (not case compare) return logic if either of
-their operands is logic. If both are bool or real (including mix of
-bool and real) then the result is bool. This is because comparison of
-bools and reals always return exactly true or false.
-
-Case comparison returns bool. This differs from baseline Verilog,
-which strictly speaking returns a logic, but only 0 or 1 values.
-
-All the arithmetic operators return bool if both of their operands are
-bool or real. Otherwise, they return logic.</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_icarus_glossary.html b/docs/wiki/geda_icarus_glossary.html
deleted file mode 100644
index 933afe5..0000000
--- a/docs/wiki/geda_icarus_glossary.html
+++ /dev/null
@@ -1,73 +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>geda:icarus_glossary</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="keywords" content="geda,icarus_glossary" />
-<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/geda:icarus_glossary?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:icarus_glossary"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:icarus_glossary"; />
-<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">
-
-
-
-<h1><a name="icarus_verilog_glossary" id="icarus_verilog_glossary">Icarus Verilog Glossary</a></h1>
-<div class="level1">
-<pre class="code">Throughout Icarus Verilog descriptions and source code, I use a
-variety of terms and acronyms that might be specific to Icarus
-Verilog, have an Icarus Verilog specific meaning, or just aren't
-widely known. So here I define these terms.
-
-
-LRM - Language Reference Manual
- This is a generic acronym, but in the Verilog world we sometimes
- mean *the* language reference manual, the IEEE1364 standard.
-
-
-PLI - Programming Language Interface
- This is a C API into Verilog simulators that is defined by the
- IEEE1364. There are two major interfaces, sometimes called PLI 1
- and PLI 2. PLI 2 is also often called VPI.
-
-
-UDP - User Defined Primitive
- These are objects that Verilog programmers define with the
- "primitive" keyword. They are truth-table based devices. The
- syntax for defining them is described in the LRM.
-
-
-VPI -
- This is the C API that is defined by the Verilog standard, and
- that Icarus Verilog partially implements. See also PLI.
-
-
-VVM - Verilog Virtual Machine
- This is the Icarus Verilog runtime that works with the code
- generator that generates C++.
-
-
-VVP - Verilog Virtual Processor
- This is the Icarus Verilog runtime that reads in custom code in a
- form that I call "VVP Assembly". See the vvp/ directory for
- documentation on that.
-
-</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_icarus_ieee1364.html b/docs/wiki/geda_icarus_ieee1364.html
deleted file mode 100644
index 00ddca7..0000000
--- a/docs/wiki/geda_icarus_ieee1364.html
+++ /dev/null
@@ -1,586 +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>geda:icarus_ieee1364</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="keywords" content="geda,icarus_ieee1364" />
-<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/geda:icarus_ieee1364?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:icarus_ieee1364"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:icarus_ieee1364"; />
-<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">
-
-
-
-<h1><a name="icarus_verilog_vs._ieee1364" id="icarus_verilog_vs._ieee1364">Icarus Verilog vs. IEEE1364</a></h1>
-<div class="level1">
-<pre class="code"> Icarus Verilog vs. IEEE1364
- Copyright 2000 Stephen Williams
-
-The IEEE1364 standard is the bible that defines the correctness of the
-Icarus Verilog implementation and behavior of the compiled
-program. The IEEE1364.1 is also referenced for matters of
-synthesis. So the ultimate definition of right and wrong comes from
-those documents.
-
-That does not mean that a Verilog implementation is fully
-constrained. The standard document allows for implementation specific
-behavior that, when properly accounted for, does not effect the
-intended semantics of the specified language. It is therefore possible
-and common to write programs that produce different results when run
-by different Verilog implementations.
-
-
-STANDARDIZATION ISSUES
-
-These are some issues where the IEEE1364 left unclear, unspecified or
-simply wrong. I'll try to be precise as I can, and reference the
-standard as needed. I've made implementation decisions for Icarus
-Verilog, and I will make clear what those decisions are and how they
-affect the language.
-
-* OBJECTS CAN BE DECLARED ANYWHERE IN THE MODULE
-
-Consider this module:
-
- module sample1;
- initial foo = 1;
- reg foo;
- wire tmp = bar;
- initial #1 $display("foo = %b, bar = %b", foo, tmp);
- endmodule
-
-Notice that the ``reg foo;'' declaration is placed after the first
-initial statement. It turns out that this is a perfectly legal module
-according to the -1995 and -2000 versions of the standard. The
-statement ``reg foo;'' is a module_item_declaration which is in turn a
-module_item. The BNF in the appendix of IEEE1364-1995 treats all
-module_item statements equally, so no order is imposed.
-
-Furthermore, there is no text (that I can find) elsewhere in the
-standard that imposes any ordering restriction. The sorts of
-restrictions I would look for are "module_item_declarations must
-appear before all other module_items" or "variables must be declared
-textually before they are referenced." Such statements simply do not
-exist. (Personally, I think it is fine that they don't.)
-
-The closest is the rules for implicit declarations of variables that
-are otherwise undeclared. In the above example, ``bar'' is implicitly
-declared and is therefore a wire. However, although ``initial foo = 1;''
-is written before foo is declared, foo *is* declared within the
-module, and declared legally by the BNF of the standard.
-
-Here is another example:
-
- module sample2;
- initial x.foo = 1;
- test x;
- initial #1 $display("foo = %b", x.foo);
- endmodule
-
- module test;
- reg foo;
- endmodule;
-
-From this example one can clearly see that foo is once again declared
-after its use in behavioral code. One also sees a forward reference of
-an entire module. Once again, the standard places no restriction on
-the order of module declarations in a source file, so this program is,
-according to the standard, perfectly well formed.
-
-Icarus Verilog interprets both of these examples according to "The
-Standard As I Understand It." However, commercial tools in general
-break down with these programs. In particular, the first example
-may generate different errors depending on the tool. The most common
-error is to claim that ``foo'' is declared twice, once (implicitly) as
-a wire and once as a reg.
-
-So the question now becomes, "Is the standard broken, or are the tools
-limited?" Coverage of the standard seems to vary widely from tool to
-tool so it is not clear that the standard really is at fault. It is
-clear, however, that somebody goofed somewhere.
-
-My personal opinion is that there is no logical need to require that
-all module_item_declarations precede any other module items. I
-personally would oppose such a restriction. It may make sense to
-require that declarations of variables within a module be preceded by
-their use, although even that is not necessary for the implementation
-of efficient compilers.
-
-However, the existence hierarchical naming syntax as demonstrated in
-sample2 can have implications that affect any declaration order
-rules. When reaching into a module with a hierarchical name, the
-module being referenced is already completely declared (or not
-declared at all, as in sample2) so module_item order is completely
-irrelevant. But a "declare before use" rule would infect module
-ordering, by requiring that modules that are used be first defined.
-
-
-* TASK AND FUNCTION PARAMETERS CANNOT HAVE EXPLICIT TYPES
-
-Consider a function negate that wants to take a signed integer value
-and return its negative:
-
- function integer negate;
- input [15:0] val;
- negate = -val;
- endfunction
-
-This is not quite right, because the input is implicitly a reg type,
-which is unsigned. The result, then, will always be a negative value,
-even if a negative val is passed in.
-
-It is possible to fix up this specific example to work properly with
-the bit pattern of a 16bit number, but that is not the point. What's
-needed is clarification on whether an input can be declared in the
-port declaration as well as in the contained block declaration.
-
-As I understand the situation, this should be allowed:
-
- function integer negate;
- input [15:0] val;
- reg signed [15:0] val;
- negate = -val;
- endfunction
-
-In the -1995 standard, the variable is already implicitly a reg if
-declared within a function or task. However, in the -2000 standard
-there is now (as in this example) a reason why one might want to
-actually declare the type explicitly.
-
-I think that a port *cannot* be declared as an integer or time type
-(though the result can) because the range of the port declaration must
-match the range of the integer/time declaration, but the range of
-integers is unspecified. This, by the way, also applies to module
-ports.
-
-With the above in mind, I have decided to *allow* function and task
-ports to be declared with types, as long as the types are variable
-types, such as reg or integer. Without this, there would be no
-portable way to pass integers into functions/tasks. The standard does
-not say it is allowed, but it doesn't *disallow* it, and other
-commercial tools seem to work similarly.
-
-
-* ROUNDING OF TIME
-
-When the `timescale directive is present, the compiler is supposed to
-round fractional times (after scaling) to the nearest integer. The
-confusing bit here is that it is apparently conventional that if the
-`timescale directive is *not* present, times are rounded towards zero
-always.
-
-
-* VALUE OF X IN PRIMITIVE OUTPUTS
-
-The IEEE1364-1995 standard clearly states in Table 8-1 that the x
-symbols is allowed in input columns, but is not allowed in
-outputs. Furthermore, none of the examples have an x in the output of
-a primitive. Table 8-1 in the IEEE1364-2000 also says the same thing.
-
-However, the BNF clearly states that 0, 1, x and X are valid
-output_symbol characters. The standard is self contradictory. So I
-take it that x is allowed, as that is what Verilog-XL does.
-
-
-* REPEAT LOOPS vs. REPEAT EVENT CONTROL
-
-There seems to be ambiguity in how code like this should be parsed:
-
- repeat (5) @(posedge clk) <statement>;
-
-There are two valid interpretations of this code, from the
-IEEE1364-1995 standard. One looks like this:
-
- procedural_timing_control_statement ::=
- delay_or_event_control statement_or_null
-
- delay_or_event_control ::=
- event_control
- | repeat ( expression ) event_control
-
-If this interpretation is used, then the statement <statement> should
-be executed after the 5th posedge of clk. However, there is also this
-interpretation:
-
- loop_statement ::=
- repeat ( expression ) statement
-
-If *this* interpretation is used, then <statement> should be executed
-5 times on the posedge of clk. The way the -1995 standard is written,
-these are both equally valid interpretations of the example, yet they
-produce very different results. The standard offers no guidance on how
-to resolve this conflict, and the IEEE1364-2000 DRAFT does not improve
-the situation.
-
-Practice suggests that a repeat followed by an event control should be
-interpreted as a loop head, and this is what Icarus Verilog does, as
-well as all the other major Verilog tools, but the standard does not
-say this.
-
-* UNSIZED NUMERIC CONSTANTS ARE NOT LIMITED TO 32 BITS
-
-The Verilog standard allows Verilog implementations to limit the size
-of unsized constants to a bit width of at least 32. That means that a
-constant 17179869183 (36'h3_ffff_ffff) may overflow some compilers. In
-fact, it is common to limit these values to 32bits. However, a
-compiler may just as easily choose another width limit, for example
-64bits. That value is equally good.
-
-However, it is not *required* that an implementation truncate at 32
-bits, and in fact Icarus Verilog does not truncate at all. It will
-make the unsized constant as big as it needs to be to hold the value
-accurately. This is especially useful in situations like this;
-
- reg [width-1:0] foo = 17179869183;
-
-The programmer wants the constant to take on the width of the reg,
-which in this example is parameterized. Since constant sizes cannot be
-parameterized, the programmer ideally gives an unsized constant, which
-the compiler then expands/contracts to match the l-value.
-
-Also, by choosing to not ever truncate, Icarus Verilog can handle code
-written for a 64bit compiler as easily as for a 32bit compiler. In
-particular, any constants that the user does not expect to be
-arbitrarily truncated by his compiler will also not be truncated by
-Icarus Verilog, no matter what that other compiler chooses as a
-truncation point.
-
-
-* UNSIZED EXPRESSIONS AS PARAMETERS TO CONCATENATION {}
-
-The Verilog standard clearly states in 4.1.14:
-
- "Unsized constant numbers shall not be allowed in
- concatenations. This is because the size of each
- operand in the concatenation is needed to calculate
- the complete size of the concatenation."
-
-So for example the expression {1'b0, 16} is clearly illegal. It
-also stands to reason that {1'b0, 15+1} is illegal, for exactly the
-same justification. What is the size of the expression (15+1)?
-Furthermore, it is reasonable to expect that (16) and (15+1) are
-exactly the same so far as the compiler is concerned.
-
-Unfortunately, Cadence seems to feel otherwise. In particular, it has
-been reported that although {1'b0, 16} causes an error, {1'b0, 15+1}
-is accepted. Further testing shows that any expression other then a
-simple unsized constant is accepted there, even if all the operands of
-all the operators that make up the expression are unsized integers.
-
-This is a semantic problem. Icarus Verilog doesn't limit the size of
-integer constants. This is valid as stated in 2.5.1 Note 3:
-
- "The number of bits that make up an unsized number
- (which is a simple decimal number or a number without
- the size specification) shall be *at*least* 32."
- [emphasis added]
-
-Icarus Verilog will hold any integer constant, so the size will be as
-large as it needs to be, whether that is 64bits, 128bits, or
-more. With this in mind, what is the value of these expressions?
-
- {'h1_00_00_00_00}
- {'h1 << 32}
- {'h0_00_00_00_01 << 32}
- {'h5_00_00_00_00 + 1}
-
-These examples show that the standard is justified in requiring that
-the operands of concatenation have size. The dispute is what it takes
-to cause an expression to have a size, and what that size is.
-Verilog-XL claims that (16) does not have a size, but (15+1) does. The
-size of the expression (15+1) is the size of the adder that is
-created, but how wide is the adder when adding unsized constants?
-
-One might note that the quote from section 4.1.14 says "Unsized
-*constant*numbers* shall not be allowed." It does not say "Unsized
-expressions...", so arguably accepting (15+1) or even (16+0) as an
-operand to a concatenation is not a violation of the letter of the
-law. However, the very next sentence of the quote expresses the
-intent, and accepting (15+1) as having a more defined size then (16)
-seems to be a violation of that intent.
-
-Whatever a compiler decides the size is, the user has no way to
-predict it, and the compiler should not have the right to treat (15+1)
-any differently then (16). Therefore, Icarus Verilog takes the
-position that such expressions are *unsized* and are not allowed as
-operands to concatenations. Icarus Verilog will in general assume that
-operations on unsized numbers produce unsized results. There are
-exceptions when the operator itself does define a size, such as the
-comparison operators or the reduction operators. Icarus Verilog will
-generate appropriate error messages.
-
-
-* MODULE INSTANCE WITH WRONG SIZE PORT LIST
-
-A module declaration like this declares a module that takes three ports:
-
- module three (a, b, c);
- input a, b, c;
- reg x;
- endmodule
-
-This is fine and obvious. It is also clear from the standard that
-these are legal instantiations of this module:
-
- three u1 (x,y,z);
- three u2 ( ,y, );
- three u3 ( , , );
- three u4 (.b(y));
-
-In some of the above examples, there are unconnected ports. In the
-case of u4, the pass by name connects only port b, and leaves a and c
-unconnected. u2 and u4 are the same thing, in fact, but using
-positional or by-name syntax. The next example is a little less
-obvious:
-
- three u4 ();
-
-The trick here is that strictly speaking, the parser cannot tell
-whether this is a list of no pass by name ports (that is, all
-unconnected) or an empty positional list. If this were an empty
-positional list, then the wrong number of ports is given, but if it is
-an empty by-name list, it is an obviously valid instantiation. So it
-is fine to accept this case as valid.
-
-These are more doubtful:
-
- three u5(x,y);
- three u6(,);
-
-These are definitely positional port lists, and they are definitely
-the wrong length. In this case, the standard is not explicit about
-what to do about positional port lists in module instantiations,
-except that the first is connected to the first, second to second,
-etc. It does not say that the list must be the right length, but every
-example of unconnected ports used by-name syntax, and every example of
-ordered list has the right size list.
-
-Icarus Verilog takes the (very weak) hint that ordered lists should be
-the right length, and will therefore flag instances u5 and u6 as
-errors. The IEEE1364 standard should be more specific one way or the
-other.
-
-* UNKNOWN VALUES IN L-VALUE BIT SELECTS
-
-Consider this example:
-
- reg [7:0] vec;
- wire [4:0] idx = <expr>;
- [...]
- vec[idx] = 1;
-
-So long as the value of idx is a valid bit select address, the
-behavior of this assignment is obvious. However, there is no explicit
-word in the standard as to what happens if the value is out of
-range. The standard clearly states the value of an expression when the
-bit-select or part select is out of range (the value is x) but does
-not address the behavior when the expression is an l-value.
-
-Icarus Verilog will take the position that bit select expressions in
-the l-value will select oblivion if it is out of range. That is, if
-idx has a value that is not a valid bit select of vec, then the
-assignment will have no effect.
-
-
-* SCHEDULING VALUES IN LOGIC
-
-The interaction between blocking assignments in procedural code and
-logic gates in gate-level code and expressions is poorly defined in
-Verilog. Consider this example:
-
- reg a;
- reg b;
- wire q = a & b;
-
- initial begin
- a = 1;
- b = 0;
- #1 b = 1;
- if (q !== 0) begin
- $display("FAILED -- q changed too soon? %b", q);
- $finish;
- end
- end
-
-This is a confusing situation. It is clear from the Verilog standard
-that an assignment to a variable using a blocking assign causes the
-l-value to receive the value before the assignment completes. This
-means that a subsequent read of the assigned variable *must* read back
-what was blocking-assigned.
-
-However, in the example above, the "wire q = a & b" expresses some
-gate logic between a/b and q. The standard does not say whether a read
-out of logic should read the value computed from previous assigns to
-the input from the same thread. Specifically, when "a" and "b" are
-assigned by blocking assignments, will a read of "q" get the computed
-value or the existing value?
-
-In fact, existing commercial tools do it both ways. Some tools print
-the FAILED message in the above example, and some do not. Icarus
-Verilog does not print the FAILED message in the above example,
-because the gate value change is *scheduled* when inputs are assigned,
-but not propagated until the thread gives up the processor.
-
-Icarus Verilog chooses this behavior in order to filter out zero-width
-pulses as early as possible. The implication of this is that a read of
-the output of combinational logic will most likely *not* reflect the
-changes in inputs until the thread that changed the inputs yields
-execution.
-
-
-* BIT AND PART SELECTS OF PARAMETERS
-
-Bit and part selects are supposed to only be supported on vector nets
-and variables (wires, regs, etc.) However, it is common for Verilog
-compilers to also support bit and part select on parameters. Icarus
-Verilog also chooses to support bit and part selects on parameter
-names, but we need to define what that means.
-
-A bit or a part select on a parameter expression returns an unsigned
-value with a defined size. The parameter value is considered be a
-constant vector of bits foo[X:0]. That is, zero based. The bit and
-part selects operate from that assumption.
-
-Verilog 2001 adds syntax to allow the user to explicitly declare the
-parameter range (i.e. parameter [5:0] foo = 9;) so Icarus Verilog will
-(or should) use the explicitly declared vector dimensions to interpret
-bit and part selects.
-
-
-* EDGES OF VECTORS
-
-Consider this example:
-
- reg [ 5:0] clock;
- always @(posedge clock) [do stuff]
-
-The IEEE1364 standard clearly states that the @(posedge clock) looks
-only at the bit clock[0] (the least significant bit) to search for
-edges. It has been pointed out by some that Verilog XL instead
-implements it as "@(posedge |clock)": it looks for a rise in the
-reduction or of the vector. Cadence Design Systems technical support
-has been rumored to claim that the IEEE1364 specification is wrong,
-but NC-Verilog behaves according to the specification, and thus
-different from XL.
-
-Icarus Verilog, therefore, takes the position that the specification
-is clear and correct, and it behaves as does NC-Verilog in this
-matter.
-
-
-* REAL VARIABLES IN $dumpoff DEAD-ZONES
-
-The IEEE1364 standard clearly states that in VCD files, the $dumpoff
-section checkpoints all the dumped variables as X values. For reg and
-wire bits/vectors, this obviously means 'bx values. Icarus Verilog
-does this, for example:
-
- $dumpoff
- x!
- x"
- $end
-
-Real variables can also be included in VCD dumps, but it is not at
-all obvious what is supposed to be dumped into the $dumpoff-$end
-section of the VCD file. Verilog-XL dumps "r0 !" to set the real
-variables to the dead-zone value of 0.0, whereas other tools, such as
-ModelTech, ignore real variables in this section.
-
-For example (from XL):
-
- $dumpoff
- r0 !
- r0 "
- $end
-
-Icarus Verilog dumps NaN values for real variables in the
-$dumpoff-$end section of the VCD file. The NaN value is the IEEE754
-equivalent of an unknown value, and so better reflects the unknown
-(during the dead zone) status of the variable, like this:
-
- $dumpoff
- rNaN !
- rNaN "
- $end
-
-It turns out that NaN is conventionally accepted by scanf functions,
-and viewers that support real variables support NaN values. So while
-the IEEE1364 doesn't require this behavior, and given the variety that
-already seems to exist amongst VCD viewers in the wild, this behavior
-seems to be acceptable according to the standard, is a better mirror
-of 4-value behavior in the dead zone, and appears more user friendly
-when viewed by reasonable viewers.
-
-
-$Id: ieee1364-notes.txt,v 1.17 2003/07/15 03:49:22 steve Exp $
-$Log: ieee1364-notes.txt,v $
-Revision 1.17 2003/07/15 03:49:22 steve
- Spelling fixes.
-
-Revision 1.16 2003/04/14 03:40:21 steve
- Make some effort to preserve bits while
- operating on constant values.
-
-Revision 1.15 2003/02/16 23:39:08 steve
- NaN in dead zones of VCD dumps.
-
-Revision 1.14 2003/02/06 17:51:36 steve
- Edge of vectors notes.
-
-Revision 1.13 2002/08/20 04:11:53 steve
- Support parameters with defined ranges.
-
-Revision 1.12 2002/06/11 03:34:33 steve
- Spelling patch (Larry Doolittle)
-
-Revision 1.11 2002/04/27 02:38:04 steve
- Support selecting bits from parameters.
-
-Revision 1.10 2002/03/31 01:54:13 steve
- Notes about scheduling
-
-Revision 1.9 2002/01/26 02:08:07 steve
- Handle x in l-value of set/x
-
-Revision 1.8 2001/08/01 05:17:31 steve
- Accept empty port lists to module instantiation.
-
-Revision 1.7 2001/02/17 05:27:31 steve
- I allow function ports to have types.
-
-Revision 1.6 2001/02/12 16:48:04 steve
- Rant about bit widths.
-
-Revision 1.5 2001/01/02 17:28:08 steve
- Resolve repeat ambiguity in favor of loop.
-
-Revision 1.4 2001/01/01 19:12:35 steve
- repeat loops ambiguity.
-
-Revision 1.3 2000/12/15 00:21:46 steve
- rounding of time and x in primitives.
-
-Revision 1.2 2000/11/19 22:03:04 steve
- Integer parameter comments.
-
-Revision 1.1 2000/07/23 18:06:31 steve
- Document ieee1364 issues.</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_icarus_mp.html b/docs/wiki/geda_icarus_mp.html
deleted file mode 100644
index f931da4..0000000
--- a/docs/wiki/geda_icarus_mp.html
+++ /dev/null
@@ -1,389 +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>geda:icarus_mp</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="geda,icarus_mp" />
-<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/geda:icarus_mp?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:icarus_mp"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:icarus_mp"; />
-<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">
-
-
-
-<h1><a name="icarus_verilog_compiler_man-page" id="icarus_verilog_compiler_man-page">Icarus Verilog compiler man-page</a></h1>
-<div class="level1">
-<pre class="code">iverilog(1) $Date: 2005/06/28 04:25:55 $ iverilog(1)
-
-
-
-NAME
- iverilog - Icarus Verilog compiler
-
-
-SYNOPSIS
- iverilog [-ESVv] [-Bpath] [-ccmdfile] [-g1|-g2|-g2x] [-Dmacro[=defn]]
- [-pflag=value] [-Iincludedir] [-mmodule] [-Mfile] [-Nfile] [-ooutput-
- filename] [-stopmodule] [-ttype] [-Tmin/typ/max] [-Wclass] [-ypath]
- sourcefile
-
-
-DESCRIPTION
- iverilog is a compiler that translates Verilog source code into exe-
- cutable programs for simulation, or other netlist formats for further
- processing. The currently supported targets are vvp for simulation, and
- xnf and fpga for synthesis. Other target types are added as code gener-
- ators are implemented.
-
-
-OPTIONS
- iverilog accepts the following options:
-
- -Bbase The iverilog program uses external programs and configuration
- files to preprocess and compile the Verilog source. Normally,
- the path used to locate these tools is built into the iverilog
- program. However, the -B switch allows the user to select a
- different set of programs. The path given is used to locate
- ivlpp, ivl, code generators and the VPI modules.
-
- -cfile This flag specifies an input file that contains a list of Ver-
- ilog source files. This is similar to the command file of other
- Verilog simulators, in that it is a file that contains the file
- names instead of taking them on the command line. See Command
- Files below.
-
- -Dmacro Defines macro macro with the string ââ?¬Ë?1ââ?¬â?¢ as its definition. This
- form is normally only used to trigger ifdef conditionals in the
- Verilog source.
-
- -Dmacro=defn
- Defines macro macro as defn.
-
- -E Preprocess the Verilog source, but do not compile it. The out-
- put file is the Verilog input, but with file inclusions and
- macro references expanded and removed. This is useful, for
- example, to preprocess Verilog source for use by other compil-
- ers.
-
- -g1|-g2|-g2x
- Select the Verilog language generation to support in the com-
- piler. This selects between IEEE1364-1995(1), IEEE1364-2001(2),
- or Verilog with extension(2x). Normally, Icarus Verilog
- defaults to the latest known generation of the language. This
- flag is most useful to restrict the language to a set supported
- by tools of specific generations, for compatibility with other
- tools.
-
- -Iincludedir
- Append directory includedir to list of directories searched for
- Verilog include files. The -I switch may be used many times to
- specify several directories to search, the directories are
- searched in the order they appear on the command line.
-
- -Mpath Write into the file specified by path a list of files that con-
- tribute to the compilation of the design. This includes files
- that are included by include directives and files that are
- automatically loaded by library support. The output is one file
- name per line, with no leading or trailing space.
-
- -mmodule
- Add this module to the list of VPI modules to be loaded by the
- simulation. Many modules can be specified, and all will be
- loaded, in the order specified. The system module is implicit
- and always included.
-
- -Npath This is used for debugging the compiler proper. Dump the final
- netlist form of the design to the specified file. It otherwise
- does not affect operation of the compiler. The dump happens
- after the design is elaborated and optimized.
-
- -o filename
- Place output in the file filename. If no output file name is
- specified, iverilog uses the default name a.out.
-
- -pflag=value
- Assign a value to a target specific flag. The -p switch may be
- used as often as necessary to specify all the desired flags.
- The flags that are used depend on the target that is selected,
- and are described in target specific documentation. Flags that
- are not used are ignored.
-
- -S Synthesize. Normally, if the target can accept behavioral
- descriptions the compiler will leave processes in behavioral
- form. The -S switch causes the compiler to perform synthesis
- even if it is not necessary for the target. If the target type
- is a netlist format, the -S switch is unnecessary and has no
- effect.
-
- -s topmodule
- Specify the top level module to elaborate. Icarus Verilog will
- by default choose modules that are not instantiated in any
- other modules, but sometimes that is not sufficient, or instan-
- tiates too many modules. If the user specifies one or more root
- modules with -s flags, then they will be used as root modules
- instead.
-
- -Tmin|typ|max
- Use this switch to select min, typ or max times from
- min:typ:max expressions. Normally, the compiler will simply use
- the typ value from these expressions (with a warning) but this
- switch will tell the compiler explicitly which value to use.
- This will suppress the warning that the compiler is making a
- choice.
-
- -ttarget
- Use this switch to specify the target output format. See the
- TARGETS section below for a list of valid output formats.
-
- -v Turn on verbose messages. This will print the command lines
- that are executed to perform the actual compilation, along with
- version information from the various components, as well as the
- version of the product as a whole. You will notice that the
- command lines include a reference to a key temporary file that
- passes information to the compiler proper. To keep that file
- from being deleted at the end of the process, provide a file
- name of your own in the environment variable IVERILOG_ICONFIG.
-
- -V Print the version of the compiler, and exit.
-
- -Wclass Turn on different classes of warnings. See the WARNING TYPES
- section below for descriptions of the different warning groups.
- If multiple -W switches are used, the warning set is the union
- of all the requested classes.
-
- -ylibdir
- Append the directory to the library module search path. When
- the compiler finds an undefined module, it looks in these
- directories for files with the right name.
-
-
-MODULE LIBRARIES
- The Icarus Verilog compiler supports module libraries as directories
- that contain Verilog source files. During elaboration, the compiler
- notices the instantiation of undefined module types. If the user speci-
- fies library search directories, the compiler will search the directory
- for files with the name of the missing module type. If it finds such a
- file, it loads it as a Verilog source file, they tries again to elabo-
- rate the module.
-
- Library module files should contain only a single module, but this is
- not a requirement. Library modules may reference other modules in the
- library or in the main design.
-
-
-TARGETS
- The Icarus Verilog compiler supports a variety of targets, for differ-
- ent purposes, and the -t switch is used to select the desired target.
-
-
- null The null target causes no code to be generated. It is useful
- for checking the syntax of the Verilog source.
-
- vvp This is the default. The vvp target generates code for the vvp
- runtime. The output is a complete program that simulates the
- design but must be run by the vvp command.
-
- xnf This is the Xilinx Netlist Format used by many tools for plac-
- ing devices in FPGAs or other programmable devices. This target
- is obsolete, use the fpga target instead.
-
- fpga This is a synthesis target that supports a variety of fpga
- devices, mostly by EDIF format output. The Icarus Verilog fpga
- code generator can generate complete designs or EDIF macros
- that can in turn be imported into larger designs by other
- tools. The fpga target implies the synthesis -S flag.
-
-
-WARNING TYPES
- These are the types of warnings that can be selected by the -W switch.
- All the warning types (other then all) can also be prefixed with no- to
- turn off that warning. This is most useful after a -Wall argument to
- suppress isolated warning types.
-
-
- all This enables all supported warning categories.
-
-
- implicit
- This enables warnings for creation of implicit declarations.
- For example, if a scalar wire X is used but not declared in the
- Verilog source, this will print a warning at its first use.
-
-
- portbind
- This enables warnings for ports of module instantiations that
- are not connected but probably should be. Dangling input ports,
- for example, will generate a warning.
-
-
- timescale
- This enables warnings for inconsistent use of the timescale
- directive. It detects if some modules have no timescale, or if
- modules inherit timescale from another file. Both probably mean
- that timescales are inconsistent, and simulation timing can be
- confusing and dependent on compilation order.
-
-
-SYSTEM FUNCTION TABLE FILES
- If the source file name as a .sft suffix, then it is taken to be a sys-
- tem function table file. A System function table file is used to
- describe to the compiler the return types for system functions. This is
- necessary because the compiler needs this information to elaborate
- expressions that contain these system functions, but cannot run the
- sizetf functions since it has no run-time.
-
- The format of the table is ASCII, one function per line. Empty lines
- are ignored, and lines that start with the �#� character are comment
- lines. Each non-comment line starts with the function name, then the
- vpi type (i.e. vpiSysFuncReal). The following types are supported:
-
-
- vpiSysFuncReal
- The function returns a real/realtime value.
-
-
- vpiSysFuncInt
- The function returns an integer.
-
-
- vpiSysFuncSized <wid> <signed|unsigned>
- The function returns a vector with the given width, and is
- signed or unsigned according to the flag.
-
-
-COMMAND FILES
- The command file allows the user to place source file names and certain
- command line switches into a text file instead of on a long command
- line. Command files can include C or C++ style comments, as well as #
- comments, if the # starts the line.
-
-
- file name
- A simple file name or file path is taken to be the name of a
- Verilog source file. The path starts with the first non-white-
- space character. Variables are substitued in file names.
-
-
- -y libdir
- A -y token prefixes a library directory in the command file,
- exactly like it does on the command line. The parameter to the
- -y flag may be on the same line or the next non-comment line.
-
- Variables in the libdir are substituted.
-
-
- +incdir+includedir
- The +incdir+ token in command files gives directories to search
- for include files in much the same way that -I flags work on
- the command line. The difference is that multiple +includedir
- directories are valid parameters to a single +incdir+ token,
- although you may also have multiple +incdir+ lines.
-
- Variables in the includedir are substituted.
-
-
- +libext+ext
- The +libext token in command files fives file extensions to try
- when looking for a library file. This is useful in conjunction
- with -y flags to list suffixes to try in each directory before
- moving on to the next library directory.
-
-
- +libdir+dir
- This is another way to specify library directories. See the -y
- flag.
-
-
- +libdir-nocase+dir
- This is like the +libdir statement, but file names inside the
- directories declared here are case insensitive. The missing
- module name in a lookup need not match the file name case, as
- long as the letters are correct. For example, "foo" matches
- "Foo.v" but not "bar.v".
-
-
- +define+NAME=value
- The +define+ token is the same as the -D option on the command
- line. The value part of the token is optional.
-
-
- +toupper-filename
- This token causes file names after this in the command file to
- be translated to uppercase. This helps with situations where a
- directory has passed through a DOS machine, and in the process
- the file names become munged.
-
-
- +tolower-filename
- This is similar to the +toupper-filename hack described above.
-
-
-VARIABLES IN COMMAND FILES
- In certain cases, iverilog supports variables in command files. These
- are strings of the form "$(varname)", where varname is the name of the
- environment variable to read. The entire string is replaced with the
- contents of that variable. Variables are only substitued in contexts
- that explicitly support them, including file and directory strings.
-
- Variable values come from the operating system environment, and not
- from preprocessor defines elsewhere in the file or the command line.
-
-
-EXAMPLES
- These examples assume that you have a Verilog source file called
- hello.v in the current directory
-
- To compile hello.v to an executable file called a.out:
-
- iverilog hello.v
-
- To compile hello.v to an executable file called hello:
-
- iverilog -o hello hello.v
-
- To compile and run explicitly using the vvp runtime:
-
- iverilog -ohello.vvp -tvvp hello.v
-
- To compile hello.v to a file in XNF-format called hello.xnf
-
- iverilog -txnf -ohello.xnf hello.v
-
-
-
-AUTHOR
- Steve Williams (steve@xxxxxxxxxx)
-
-
-SEE ALSO
- vvp(1), <http://www.icarus.com/eda/verilog/>
-
-
-COPYRIGHT
- Copyright �© 2002 Stephen Williams
-
- This document can be freely redistributed according to the terms of the
- GNU General Public License version 2.0
-
-
-
-Version $Date: 2005/06/28 04:25:55 $ iverilog(1)</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_icarus_opcodes.html b/docs/wiki/geda_icarus_opcodes.html
deleted file mode 100644
index 265dabe..0000000
--- a/docs/wiki/geda_icarus_opcodes.html
+++ /dev/null
@@ -1,712 +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>geda:icarus_opcodes</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="geda,icarus_opcodes" />
-<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/geda:icarus_opcodes?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:icarus_opcodes"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:icarus_opcodes"; />
-<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">
-
-
-
-<h1><a name="executable_instruction_opcodes" id="executable_instruction_opcodes">Executable Instruction Opcodes</a></h1>
-<div class="level1">
-<pre class="code">/*
- * Copyright (c) 2001-2003 Stephen Williams (steve@xxxxxxxxxx)
- *
- * $Id: opcodes.txt,v 1.69 2005/11/26 17:16:05 steve Exp $
- */
-
-
-
-EXECUTABLE INSTRUCTION OPCODES
-
-Instruction opcodes all start with a % character and have 0 or more
-operands. In no case are there more then 3 operands. This chapter
-describes the specific behavior of each opcode, in enough detail
-(I hope) that its complete effect can be predicted.
-
-General principles of Arithmetic:
-
-The binary arithmetic instruction in general take three parameters,
-the left operand, the right operand, and the base. The left operand is
-replaced with the result, which is the same width as the left and
-right operands.
-
-
-* %add <bit-l>, <bit-r>, <wid>
-
-This instruction adds the right vector into the left vector, the
-vectors having the width <wid>. If any of the bits of either vector
-are x or z, the result is x. Otherwise, the result is the arithmetic
-sum.
-
-See also the %sub instruction.
-
-
-* %add/wr <bit-l>, <bit-r>
-
-This is the real valued version of the %add instruction. The arguments
-are word indices of the operands. The right operand is added into the
-left operand.
-
-See also the %sub/wr instruction.
-
-
-* %addi <bit-l>, <imm>, <wid>
-
-This instruction adds the immediate value (no x or z bits) into the
-left vector. The imm value is limited to 16 significant bits, but it
-is zero extended to match any width.
-
-* %and <bit-l>, <bit-r>, <wid>
-
-Perform the bitwise AND of the two vectors, and store the result in
-the left vector. Each bit is calculated independent of other bits. AND
-means the following:
-
- 0 and ? --> 0
- ? and 0 --> 0
- 1 and 1 --> 1
- otherwise x
-
-* %assign/m <memory-label>, <delay>, <bit> (OBSOLETE)
-
-This instruction does a non-blocking assignment to a bit in a memory
-from the specified thread register <bit>. The memory bit is addressed
-by index register 3. Bit address zero is the LSB of the first memory
-word.
-
-* %assign/mv <memory-label>, <delay>, <bit>
-
-the %assign/mv instruction assigns a vector value to a word in the
-labeled memory. The <delay> is the delay in simulation time to the
-assignment (0 for non-blocking assignment) and the <bit> is the base
-of the vector to write.
-
-The width of the word is retrieved from index register 0.
-
-The address of the word in the memory is from index register 3. The
-address is canonical form.
-
-* %assign/v0 <var-label>, <delay>, <bit>
-* %assign/v0/d <var-label>, <delayx>, <bit>
-
-The %assign/v0 instruction is a vector version of non-blocking
-assignment. The <delay> is the number of clock ticks in the future
-where the assignment should be schedule, and the <bit> is the base of
-the vector to be assigned to the destination. The vector width is in
-index register 0.
-
-The %assign/v0/d variation puts the delay instead into an integer
-register that is given by the <delayx> value. This should not be 0, of
-course, because integer 0 is taken with the vector width.
-
-The <var-label> references a .var object that can receive non-blocking
-assignments. For blocking assignments, see %set/v.
-
-* %assign/v0x1 <var-label>, <delay>, <bit>
-
-This is similar to the %assign/v0 instruction, but adds the index-1
-index register with the canonical index of the destination where the
-vector is to be written. This allows for part writes into the vector.
-
-* %assign/wr <vpi-label>, <delay>, <index>
-
-This instruction causes a non-blocking assign of the indexed value to
-the real object addressed by the <vpi-label> label.
-
-* %assign/x0 <var-label>, <delay>, <bit> (OBSOLETE -- See %assign/v0x)
-
-This does a non-blocking assignment to a functor, similar to the
-%assign instruction. The <var-label> identifies the base functor of
-the affected variable, and the <delay> gives the delay when the
-assignment takes place. The delay may be 0. The actual functor used is
-calculated by using <var-label> as a base, and indexing with the
-index[0] index register. This supports indexed assignment.
-
-The <bit> is the address of the thread register that contains the bit
-value to assign.
-
-
-* %blend <bit-l>, <bit-r>, <wid>
-
-This instruction blends the bits of a vector into the destination in a
-manner like the expression (x ? <a> : <b>). The truth table is:
-
- 1 1 --> 1
- 0 0 --> 0
- z z --> z
- x x --> x
- .... --> x
-
-In other words, if the bits are identical, then take that
-value. Otherwise, the value is x.
-
-* %breakpoint
-
-This instruction unconditionally breaks the simulator into the
-interactive debugger. The idea is to stop the simulator here and give
-the user a chance to display the state of the simulation using
-debugger commands.
-
-This may not work on all platforms. If run-time debugging is compiled
-out, then this function is a no-op.
-
-* %cassign/v <var-label>, <bit>, <wid>
-
-Perform a continuous assign of a constant value to the target
-variable. This is similar to %set, but it uses the cassign port
-(port-1) of the signal functor instead of the normal assign, so the
-signal responds differently. See "VARIABLE STATEMENTS" in the
-README.txt file.
-
-
-* %cmp/u <bit-l>, <bit-r>, <wid>
-* %cmp/s <bit-l>, <bit-r>, <wid>
-
-These instructions perform a generic comparison of two vectors of equal
-size. The <bit-l> and <bit-r> numbers address the least-significant
-bit of each vector, and <wid> is the width. If either operand is 0,
-1, 2 or 3 then it is taken to be a constant replicated to the selected
-width.
-
-The results of the comparison go into bits 4, 5, 6 and 7:
-
- 4: eq (equal)
- 5: lt (less than)
- 6: eeq (case equal)
-
-The eeq bit is set to 1 if all the bits in the vectors are exactly the
-same, or 0 otherwise. The eq bit is true if the values are logically
-the same. That is, x and z are considered equal. In other words the eq
-bit is the same as ``=='' and the eeq bit ``===''.
-
-The lt bit is 1 if the left vector is less then the right vector, or 0
-if greater then or equal to the right vector. It is the equivalent of
-the Verilog < operator. Combinations of these three bits can be used
-to implement all the Verilog comparison operators.
-
-The %cmp/u and %cmp/s differ only in the handling of the lt bit. The
-%cmp/u does an unsigned compare, whereas the %cmp/s does a signed
-compare. In either case, if either operand contains x or z, then lt
-bit gets the x value.
-
-
-* %cmp/wr <bit-l>, <bit-r>
-
-[compare real values.]
-
-* %cmp/ws <bit-l>, <bit-r>
-* %cmp/wu <bit-l>, <bit-r>
-
-[compare signed/unsigned integer words.]
-
-* %cmp/z <bit-l>, <bit-r>, <wid>
-* %cmp/x <bit-l>, <bit-r>, <wid>
-
-These instructions are for implementing the casez and casex
-comparisons. These work similar to the %cmp/u instructions, except
-only an eq bit is calculated. These comparisons both treat z values in
-the left or right operand as don't care positions. The %cmp/x
-instruction will also treat x values in either operand as don't care.
-
-Only bit 4 is set by these instructions.
-
-
-* %cvt/ir <bit-l>, <bit-r>
-* %cvt/ri <bit-l>, <bit-r>
-* %cvt/vr <bit-l>, <bit-r>, <wid>
-
-Copy a word from r to l, converting it from real to integer (ir) or
-integer to real (ri) in the process. The source and destination may
-be the same word address, leading to a convert in place.
-
-The %cvt/vr opcode converts a real word <bit-r> to a thread vector
-starting at <bit-l> and with the width <wid>. Non-integer precision is
-lost in the conversion.
-
-* %deassign <var-label>
-
-Deactivate and disconnect a procedural continuous assignment to a
-variable. The <var-label> identifies the affected variable.
-
-* %delay <delay>
-
-This opcode pauses the thread, and causes it to be rescheduled for a
-time in the future. The <amount> is the number of the ticks in the
-future to reschedule, and is >= 0. If the %delay is zero, then the
-thread yields the processor for another thread, but will be resumed in
-the current time step.
-
-* %delayx <idx>
-
-This is similar to the %delay opcode, except that the parameter
-selects an index register, which contains the actual delay. This
-supports run-time calculated delays.
-
-* %disable <scope-label>
-
-This instruction terminates threads that are part of a specific
-scope. The label identifies the scope in question, and the threads are
-the threads that are currently within that scope.
-
-
-* %div <bit-l>, <bit-r>, <wid>
-* %div/s <bit-l>, <bit-r>, <wid>
-
-This instruction arithmetically divides the <bit-l> vector by the
-<bit-r> vector, and leaves the result in the <bit-l> vector. IF any of
-the bits in either vector are x or z, the entire result is x.
-
-The %div/s instruction is the same as %div, but does signed division.
-
-
-* %div/wr <bit-l>, <bit-r>
-
-This opcode divides the left operand by the right operand. If the
-right operand is 0, then the result is NaN.
-
-
-* %force/v <label>, <bit>, <wid>
-
-Force a constant value to the target variable. This is similar to %set
-and %cassign/v, but it uses the force port (port-2) of the signal
-functor instead of the normal assign port (port-0), so the signal
-responds differently. See "VARIABLE STATEMENTS" and "NET STATEMENTS"
-in the README.txt file.
-
-* %force/x0 <label>, <bit>, <wid>
-
-Force a constant value to part target variable. This is similar to
-%set/x instruction, but it uses the force port (port-2) of the signal
-functor instead of the normal assign port (port-0), so the signal
-responds differently. See "VARIABLE STATEMENTS" and "NET STATEMENTS"
-in the README.txt file.
-
-* %fork <code-label>, <scope-label>
-
-This instruction is similar to %jmp, except that it creates a new
-thread to start executing at the specified address. The new thread is
-created and pushed onto the child stack. It is also marked runnable,
-but is not necessarily started until the current thread yields.
-
-The %fork instruction has no effect other then to push a child thread.
-
-See also %join.
-
-
-* %inv <bit>, <wid>
-
-Perform a bitwise invert of the vector starting at <bit>. The result
-replaces the input. Invert means the following, independently for each
-bit:
-
- 0 --> 1
- 1 --> 0
- x --> x
- z --> x
-
-
-* %ix/get <idx>, <bit>, <wid>
-
-This instruction loads a thread vector starting at <bit>, size <wid>,
-into the index register <idx>. The <bit> is the lsb of the value in
-thread bit space, and <wid> is the width of the vector.
-
-The function converts the 4-value bits into a binary number, without
-sign extension. If any of the bits of the vector is x or z, then the
-index register gets the value 0.
-
-The function also writes into bit 4 a 1 if any of the bits of the
-input vector are x or z. This is a flag that the 0 value written into
-the index register is really the result of calculating from unknown
-bits.
-
- 4: unknown value
- 5: (reserved)
- 6: (reserved)
-
-
-* %ix/load <idx>, <value>
-
-This instruction loads an immediate value into the addressed index
-register. The index register holds numeric values, so the <value> is a
-number. The idx value selects the index register, and may be 0, 1, 2
-or 3. This is different from %ix/get, which loads the index register
-from a value in the thread bit vector.
-
-
-* %ix/add <idx>, <value>
-* %ix/sub <idx>, <value>
-* %ix/mul <idx>, <value>
-
-This instruction adds, subtracts, or multiplies an immediate value to
-the addressed index register. The index register holds numeric values,
-so the <value> is a number. The <idx> value selects the index register,
-and may be 0, 1, 2 or 3.
-
-
-* %jmp <code-label>
-
-The %jmp instruction performs an unconditional branch to a given
-location. The parameter is the label of the destination instruction.
-
-* %jmp/[01xz] <code-label>, <bit>
-
-This is a conditional version of the %jmp instruction. In this case,
-a single bit (addressed by <bit>) is tested. If it is one of the
-values in the part after the /, the jump is taken. For example:
-
- %jmp/xz T_label, 8;
-
-will jump to T_label if bit 8 is x or z.
-
-* %join
-
-This is the partner to %fork. This instruction causes the thread to
-wait for the top thread in the child stack to terminate, then
-continues. It has no effect in the current thread other then to wait
-until the top child is cleared.
-
-It is an error to execute %join if there are no children in the child
-stack. Every %join in the thread must have a matching %fork that
-spawned off a child thread.
-
-If the matching child instruction is still running, a %join suspends
-the calling thread until the child ends. If the child is already
-ended, then the %join does not block or yield the thread.
-
-* %load/m <bit>, <memory-label> (OBSOLETE)
-
-This instruction loads a value from a memory bit into the specified
-thread register bit. The memory bit is addressed by index register 3.
-Bit address zero is the LSB of the first memory word. This
-instruction loads only a single bit.
-
-* %load/mv <bit>, <memory-label>, <wid>
-
-this instruction loads a word from the specified memory. The word
-address is in index register 3. The width should match the width of
-the memory word.
-
-* %load/nx <bit>, <vpi-label>, <idx>
-
-This instruction load a value from a .net object bit. Since .net
-objects don't really exist (they are only named indirection into the
-netlist) this instruction indexes into the .net list of bits.
-
-* %load/v <bit>, <functor-label>, <wid>
-
-This instruction loads a vector value from the given functor node into
-the specified thread register bit. The functor-label can refer to a
-.net, a .var or a .functor with a vector output. The entire vector,
-from the least significant up to <wid> bits, is loaded starting at
-thread bit <bit>. It is an error for the width to not match the vector
-width at the functor.
-
-* %load/wr <bit>, <vpi-label>
-
-This instruction reads a real value from the vpi-like object to a word
-register.
-
-* %load/x <bit>, <functor-label>, <idx>
-* %load/x.p <bit>, <functor-label>, <idx>
-
-This is an indexed load. It uses the contents of the specified index
-register to select a bit from a vector functor at <functor-label>. The
-bit is pulled from the indexed bit of the addressed functor and loaded
-into the destination thread bit. If the indexed value is beyond the
-width of the vector, then the result is X.
-
-The %load/x.p is the same, but when the operation is done, it
-increments the specified index register. This provides a basic
-auto-increment feature.
-
-* %loadi/wr <bit>, <mant>, <exp>
-
-This opcode loads an immediate value, floating point, into the word
-register selected by <bit>. The mantissa is an unsigned integer value,
-up to 32 bits, that multiplied by 2**(<exp>-0x1000) to make a real
-value. The sign bit is OR-ed into the <exp> value at bit 0x2000, and
-is removed from the <exp> before calculating the real value.
-
-
-* %mod <bit-l>, <bit-r>, <wid>
-* %mod/s <bit-l>, <bit-r>, <wid>
-
-This instruction calculates the modulus %r of the left operand, and
-replaces the left operand with the result. The <wid> gives the width
-of the left and the right vectors, and the left vector is completely
-replaced with the result.
-
-The /s form does signed %.
-
-* %mov <dst>, <src>, <wid>
-
-This instruction copies a vector from one place in register space to
-another. The destination and source vectors are assumed to be the same
-width and non-overlapping. The <dst> may not be 0-3, but if the <src>
-is one of the 4 constant bits, the effect is to replicate the value
-into the destination vector. This is useful for filling a vector.
-
-
-* %mul <bit-l>, <bit-r>, <wid>
-
-This instruction multiplies the left vector by the right vector, the
-vectors having the width <wid>. If any of the bits of either vector
-are x or z, the result is x. Otherwise, the result is the arithmetic
-product.
-
-
-* %mul/wr <bit-l>, <bit-r>
-
-This opcode multiplies two real words together. The result replaces
-the left operand.
-
-
-* %muli <bit-l>, <imm>, <wid>
-
-This instruction is the same as %mul, but the second operand is an
-immediate value that is padded to the width of the result.
-
-
-* %nand <dst>, <src>, <wid>
-
-Perform the bitwise NAND of the two vectors, and store the result in
-the left vector. Each bit is calculated independent of other bits. NAND
-means the following:
-
- 0 and ? --> 1
- ? and 0 --> 1
- 1 and 1 --> 0
- otherwise x
-
-
-* %nor <dst>, <src>, <wid>
-
-Perform the bitwise nor of the vectors. Each bit in the <dst> is
-combined with the corresponding bit in the source, according to the
-truth table:
-
- 1 nor ? --> 0
- ? nor 1 --> 0
- 0 nor 0 --> 1
- otherwise x
-
-
-* %nor/r <dst>, <src>, <wid>
-
-The %nor/r instruction is a reduction nor. That is, the <src> is a
-vector with width, but the result is a single bit. The <src> vector is
-not affected by the operation unless the <dst> bit is within the
-vector. The result is calculated before the <dst> bit is written, so
-it is valid to place the <dst> within the <src>.
-
-The actual operation performed is the inverted or of all the bits in
-the vector.
-
-
-* %or <dst>, <src>, <wid>
-
-Perform the bitwise or of the vectors. Each bit in the <dst> is
-combined with the corresponding bit in the source, according to the
-truth table:
-
- 1 or ? --> 1
- ? or 1 --> 1
- 0 or 0 --> 0
- otherwise x
-
-
-* %or/r <dst>, <src>, <wid>
-
-This is a reduction version of the %or opcode. The <src> is a vector,
-and the <dst> is a writable scalar. The <dst> gets the value of the
-or of all the bits of the src vector.
-
-
-* %release/net <functor-label>
-* %release/reg <functor-label>
-
-Release the force on the signal that is represented by the functor
-<functor-label>. The force was previously activated with a %force/v
-statement. If no force was active on this functor the statement does
-nothing. The %release/net sends to the labeled functor the release
-command with net semantics: the unforced value is propagated to the
-output of the signal after the release is complete. The %release/reg
-sends the release command with reg semantics: the signal holds its
-forced value until another value propagates through.
-
-* %set/v <var-label>, <bit>, <wid>
-
-This sets a vector to a variable, and is used to implement blocking
-assignments. The <var-label> identifies the variable to receive the
-new value. Once the set completes, the value is immediately available
-to be read out of the variable. The <bit> is the address of the thread
-register that contains the LSB of the vector, and the <wid> is the
-size of the vector. The width must exactly match the width of the
-signal.
-
-* %set/mv <memory-label>, <bit>, <wid>
-
-This sets a thread vector to a memory word. The <memory-label>
-addresses a memory device, and the <bit>,<wid> describe a vector to be
-written. Index register 3 contains the address of the word within the
-memory. The address (in canonical form) is precalculated and loaded
-into index register 3.
-
-
-* %set/wr <vpi-label>, <bit>
-
-This instruction writes a real word to the specified VPI-like object.
-
-* %set/x0 <var-label>, <bit>, <wid>
-
-This sets the part of a signal vector, the address calculated by
-using the index register 0 to index the base within the vector of
-<var-label>. The destination must be a signal of some sort. Otherwise,
-the instruction will fail.
-
-The addressing is canonical (0-based) so the compiler must figure out
-non-zero offsets, if any. The width is the width of the part being
-written. The other bits of the vector are not touched.
-
-The index may be signed, and if less then 0, the beginning bits are
-not assigned. Also, if the bits go beyond the end of the signal, those
-bits are not written anywhere.
-
-
-* %shiftl/i0 <bit>, <wid>
-
-This instruction shifts the vector left (towards more significant
-bits) by the amount in index register 0. The <bit> is the address of
-the lsb of the vector, and <wid> the width of the vector. The shift is
-done in place. Zero values are shifted in.
-
-* %shiftr/i0 <bit>, <wid>
-* %shiftr/s/i0 <bit>, <wid>
-
-This instruction shifts the vector right (towards the less significant
-bits) by the amount in the index register 0. The <bit> is the address
-of the lsb of the vector, and <wid> is the width of the vector. The
-shift is done in place.
-
-%shiftr/i0 is an unsigned down shift, so zeros are shifted into the
-top bits. %shiftr/s/i0 is a signed shift, so the value is sign-extended.
-
-* %sub <bit-l>, <bit-r>, <wid>
-
-This instruction arithmetically subtracts the right vector out of the
-left vector. It accomplishes this by adding to the left vector 1 plus
-the 1s complement of the right vector. The carry value is dropped, and
-the result, placed in <bit-l>, is the subtraction of <bit-r> from the
-input <bit-l>. Both vectors have the same width. If any bits in either
-operand are x, then the entire result is x.
-
-See also the %add instruction.
-
-* %subi <bit-l>, <imm>, <wid>
-
-This instruction arithmetically subtracts the immediate value from the
-left vector. The <imm> value is a 16bit unsigned value zero-extended to
-the <wid> of the left vector. The result replaces the left vector.
-
-See also the %addi instruction.
-
-
-* %sub/wr <bit-l>, <bit-r>
-
-This instruction operates on real values in word registers. The right
-indexed value is subtracted from the left indexed value, and the
-result placed in the left index.
-
-
-* %vpi_call <name> [, ...]
-
-This instruction makes a call to a system task that was declared using
-VPI. The operands are compiled down to a vpiHandle for the call. The
-instruction contains only the vpiHandle for the call. See the vpi.txt
-file for more on system task/function calls.
-
-
-* %vpi_func <name>, <dst>, <wid> [, ...]
-
-This instruction is similar to %vpi_call, except that it is for
-calling system functions. The difference here is the <dst> and <wid>
-parameters that specify where the return value is to go. The normal
-means that the VPI code uses to write the return value causes those
-bits to go here.
-
-
-* %wait <functor-label>
-
-When a thread executes this instruction, it places itself in the
-sensitive list for the addressed functor. The functor holds all the
-threads that await the functor. When the defined sort of event occurs
-on the functor, a thread schedule event is created for all the threads
-in its list and the list is cleared.
-
-* %xnor <dst>, <src>, <wid>
-
-This does a bitwise exclusive nor (~^) of the <src> and <dst> vector,
-and leaves the result in the <dst> vector. xnor is this:
-
- 0 xnor 0 --> 1
- 0 xnor 1 --> 0
- 1 xnor 0 --> 0
- 1 xnor 1 --> 1
- otherwise x
-
-
-* %xor <dst>, <src>, <wid>
-
-This does a bitwise exclusive or (^) of the <src> and <dst> vector,
-and leaves the result in the <dst> vector. xor is this:
-
- 0 xnor 0 --> 0
- 0 xnor 1 --> 1
- 1 xnor 0 --> 1
- 1 xnor 1 --> 0
- otherwise x
-
-
-/*
- * Copyright (c) 2001-2003 Stephen Williams (steve@xxxxxxxxxx)
- *
- * This source code is free software; you can redistribute it
- * and/or modify it in source code form under the terms of the GNU
- * General Public License as published by the Free Software
- * Foundation; either version 2 of the License, or (at your option)
- * any later version.
- *
- * This program is distributed in the hope that it will be useful,
- * but WITHOUT ANY WARRANTY; without even the implied warranty of
- * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
- * GNU General Public License for more details.
- *
- * You should have received a copy of the GNU General Public License
- * along with this program; if not, write to the Free Software
- * Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA
- */</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_icarus_quick_start.html b/docs/wiki/geda_icarus_quick_start.html
deleted file mode 100644
index 6ee2a88..0000000
--- a/docs/wiki/geda_icarus_quick_start.html
+++ /dev/null
@@ -1,116 +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>geda:icarus_quick_start</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="keywords" content="geda,icarus_quick_start" />
-<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/geda:icarus_quick_start?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:icarus_quick_start"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:icarus_quick_start"; />
-<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">
-
-
-
-<h1><a name="getting_started_with_icarus_verilog" id="getting_started_with_icarus_verilog">Getting Started with Icarus Verilog</a></h1>
-<div class="level1">
-<pre class="code">* Getting Started with Icarus Verilog
-
-Icarus Verilog is a Verilog compiler. It is suitable for use as a
-simulator, and, to some degree, synthesizer. Icarus Verilog runs under
-Linux and a variety of UNIX systems, as well as Windows as a command
-line tool, so the instructions are generally applicable to all
-environments. Note that this is only a quick start. For more detailed
-documentation, see the manual page for the iverilog command.
-
-
-* Hello, World!
-
-The first thing you want to do as a user is learn how to compile and
-execute even the most trivial design. For the purposes of simulation,
-we use as our example *the* most trivial simulation:
-
- module main;
-
- initial
- begin
- $display("Hello, World");
- $finish ;
- end
-
- endmodule
-
-By a text editor (or copy hello.vl from the Icarus Verilog examples
-directory) arrange for this program to be in a text file, "hello.vl".
-Next, compile this program with a command like this:
-
- % iverilog -o hello hello.vl
-
-The results of this compile are placed into the file "hello", as the
-"-o" flag tells the compiler where to place the compiled result. Next,
-execute the compiled program like so:
-
- % vvp hello
- Hello, World
-
-And there it is, the program has been executed. So what happened? The
-first step, the "iverilog" command, read and interpreted the source
-file, then generated a compiled result. The compiled form may be
-selected by command line switches, but the default form is the VVP
-format, which is actually run by the "vvp" command.
-
-The "iverilog" and "vvp" commands are the only commands that users
-use to invoke Icarus Verilog. What the compiler actually does is
-controlled by command line switches. In our little example, we asked
-the compiler to compile the source program to the default vvp form,
-which is in turn executed by the vvp program.
-
-
-* Windows Install
-
-The easiest way to install under Windows is to get a precompiled
-installer for the version you wish to install. Icarus Verilog is
-distributed for Windows users as a self-installing .exe. Just execute
-the installer and follow the instructions. During the install, take
-note of the directory where the program is installed: for example,
-C:\iverilog is a good place to install.
-
-Once the binary is installed, you need to add the bin directory to
-your execution path. The executables you need are in C:\iverilog\bin,
-where the "C:\iverilog" part is actually the root of where you
-installed the package. The programs are in the bin subdirectory. Put
-this directory in your PATH environment variable, and the above
-commands become accessible to you at the command line prompt, or even
-in batch files.
-
-
-* Linux Install
-
-Under Linux, the install is even easier. For RedHat and Mandrake based
-systems, there is the appropriate RPM file. Just install the package
-with the "rpm -U <file>" command. Debian users should get Icarus
-Verilog packages from the main Debian software site.
-
-
-* Install From Source
-
-In this case, see README.txt and other documentation that comes with
-the source.</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_icarus_readme.html b/docs/wiki/geda_icarus_readme.html
deleted file mode 100644
index 5b33825..0000000
--- a/docs/wiki/geda_icarus_readme.html
+++ /dev/null
@@ -1,529 +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>geda:icarus_readme</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="keywords" content="geda,icarus_readme" />
-<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/geda:icarus_readme?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:icarus_readme"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:icarus_readme"; />
-<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">
-
-
-
-<h1><a name="the_icarus_verilog_compilation_system" id="the_icarus_verilog_compilation_system">The Icarus Verilog Compilation System</a></h1>
-<div class="level1">
-<pre class="code"> THE ICARUS VERILOG COMPILATION SYSTEM
- Copyright 2000-2004 Stephen Williams
-
-
-1.0 What is ICARUS Verilog?
-
-Icarus Verilog is intended to compile ALL of the Verilog HDL as
-described in the IEEE-1364 standard. Of course, it's not quite there
-yet. It does currently handle a mix of structural and behavioral
-constructs. For a view of the current state of Icarus Verilog, see its
-home page at <http://www.icarus.com/eda/verilog>.
-
-Icarus Verilog is not aimed at being a simulator in the traditional
-sense, but a compiler that generates code employed by back-end
-tools. These back-end tools currently include a simulator engine
-called VVP, an XNF (Xilinx Netlist Format) generator and an EDIF FPGA
-netlist generator. In the future, backends are expected for EDIF/LPM,
-structural Verilog, VHDL, etc.
-
- For instructions on how to run Icarus Verilog,
- see the ``iverilog'' man page.
-
-
-2.0 Building/Installing Icarus Verilog From Source
-
-If you are starting from source, the build process is designed to be
-as simple as practical. Someone basically familiar with the target
-system and C/C++ compilation should be able to build the source
-distribution with little effort. Some actual programming skills are
-not required, but helpful in case of problems.
-
-If you are building for Windows, see the mingw.txt file.
-
-2.1 Compile Time Prerequisites
-
-You need the following software to compile Icarus Verilog from source
-on a UNIX-like system:
-
- - GNU Make
- The Makefiles use some GNU extensions, so a basic POSIX
- make will not work. Linux systems typically come with a
- satisfactory make. BSD based systems (i.e., NetBSD, FreeBSD)
- typically have GNU make as the gmake program.
-
- - ISO C++ Compiler
- The ivl and ivlpp programs are written in C++ and make use
- of templates and some of the standard C++ library. egcs and
- recent gcc compilers with the associated libstdc++ are known
- to work. MSVC++ 5 and 6 are known to definitely *not* work.
-
- - bison and flex
-
- - gperf 2.7
- The lexical analyzer doesn't recognize keywords directly,
- but instead matches symbols and looks them up in a hash
- table in order to get the proper lexical code. The gperf
- program generates the lookup table.
-
- A version problem with this program is the most common cause
- of difficulty. See the Icarus Verilog FAQ.
-
- - readline 4.2
- On Linux systems, this usually means the readline-devel
- rpm. In any case, it is the development headers of readline
- that are needed.
-
- - termcap
- The readline library in turn uses termcap.
-
-If you are building from CVS, you will also need software to generate
-the configure scripts.
-
- - autoconf 2.53
- This generates configure scripts from configure.in. The 2.53
- or later versions are known to work, autoconf 2.13 is
- reported to *not* work.
-
-2.2 Compilation
-
-Unpack the tar-ball and cd into the verilog-######### directory
-(presumably that is how you got to this README) and compile the source
-with the commands:
-
- ./configure
- make
-
-Normally, this command automatically figures out everything it needs
-to know. It generally works pretty well. There are a few flags to the
-configure script that modify its behavior:
-
- --without-ipal
- This turns off support for Icarus PAL, whether ipal
- libraries are installed or not.
-
- --prefix=<root>
- The default is /usr/local, which causes the tool suite to
- be compiled for install in /usr/local/bin,
- /usr/local/share/ivl, etc.
-
- I recommend that if you are configuring for precompiled
- binaries, use --prefix=/usr. On Solaris systems, it is
- common to use --prefix=/opt. You can configure for a non-root
- install with --prefix=$HOME.
-
- --enable-vvp32 (experimental)
- If compiling on AMD64 systems, this enables the
- compilation of 32bit compatible vvp (vvp32) and the vpi
- modules that match.
-
-2.2.1 Special AMD64 Instructions
-
-(The Icarus Verilog RPM for x86_64 is build using these instructions.)
-
-If you are building for Linux/AMD64 (a.k.a x86_64) then to get the
-most out of your install, first make sure you have both 64bit and
-32bit development libraries installed. Then configure with this
-somewhat more complicated command:
-
- ./configure libdir64='$(prefix)/lib64' vpidir1=vpi64 vpidir2=. --enable-vvp32
-
-This reflects the convention on AMD64 systems that 64bit libraries go
-into lib64 directories. The "--enable-vvp32" also turns on 32bit
-compatibility files. A 32bit version of vvp (vvp32) will be created,
-as well as 32bit versions of the development libraries and bundled VPI
-libraries.
-
-2.3 (Optional) Testing
-
-To run a simple test before installation, execute
-
- make check
-
-The commands printed by this run might help you in running Icarus
-Verilog on your own Verilog sources before the package is installed
-by root.
-
-2.4 Installation
-
-Now install the files in an appropriate place. (The makefiles by
-default install in /usr/local unless you specify a different prefix
-with the --prefix=<path> flag to the configure command.) You may need
-to do this as root to gain access to installation directories.
-
- make install
-
-2.5 Uninstallation
-
-The generated Makefiles also include the uninstall target. This should
-remove all the files that ``make install'' creates.
-
-3.0 How Icarus Verilog Works
-
-This tool includes a parser which reads in Verilog (plus extensions)
-and generates an internal netlist. The netlist is passed to various
-processing steps that transform the design to more optimal/practical
-forms, then is passed to a code generator for final output. The
-processing steps and the code generator are selected by command line
-switches.
-
-3.1 Preprocessing
-
-There is a separate program, ivlpp, that does the preprocessing. This
-program implements the `include and `define directives producing
-output that is equivalent but without the directives. The output is a
-single file with line number directives, so that the actual compiler
-only sees a single input file. See ivlpp/ivlpp.txt for details.
-
-3.2 Parse
-
-The Verilog compiler starts by parsing the Verilog source file. The
-output of the parse is a list of Module objects in "pform". The pform
-(see pform.h) is mostly a direct reflection of the compilation
-step. There may be dangling references, and it is not yet clear which
-module is the root.
-
-One can see a human readable version of the final pform by using the
-``-P <path>'' flag to the compiler. This will cause iverilog to dump
-the pform into the file named <path>.
-
-3.3 Elaboration
-
-This phase takes the pform and generates a netlist. The driver selects
-(by user request or lucky guess) the root module to elaborate,
-resolves references and expands the instantiations to form the design
-netlist. (See netlist.txt.) Final semantic checks are performed during
-elaboration, and some simple optimizations are performed. The netlist
-includes all the behavioral descriptions, as well as gates and wires.
-
-The elaborate() function performs the elaboration.
-
-One can see a human readable version of the final, elaborated and
-optimized netlist by using the ``-N <path>'' flag to the compiler. If
-elaboration succeeds, the final netlist (i.e., after optimizations but
-before code generation) will be dumped into the file named <path>.
-
-Elaboration is actually performed in two steps: scopes and parameters
-first, followed by the structural and behavioral elaboration.
-
-3.3.1 Scope Elaboration
-
-This pass scans through the pform looking for scopes and parameters. A
-tree of NetScope objects is built up and placed in the Design object,
-with the root module represented by the root NetScope object. The
-elab_scope.cc and elab_pexpr.cc files contain most of the code for
-handling this phase.
-
-The tail of the elaborate_scope behavior (after the pform is
-traversed) includes a scan of the NetScope tree to locate defparam
-assignments that were collected during scope elaboration. This is when
-the defparam overrides are applied to the parameters.
-
-3.3.2 Netlist Elaboration
-
-After the scopes and parameters are generated and the NetScope tree
-fully formed, the elaboration runs through the pform again, this time
-generating the structural and behavioral netlist. Parameters are
-elaborated and evaluated by now so all the constants of code
-generation are now known locally, so the netlist can be generated by
-simply passing through the pform.
-
-3.4 Optimization
-
-This is actually a collection of processing steps that perform
-optimizations that do not depend on the target technology. Examples of
-some useful transformations are
-
- - eliminate null effect circuitry
- - combinational reduction
- - constant propagation
-
-The actual functions performed are specified on the ivl command line by
-the -F flags (see below).
-
-3.5 Code Generation
-
-This step takes the design netlist and uses it to drive the code
-generator (see target.h). This may require transforming the
-design to suit the technology.
-
-The emit() method of the Design class performs this step. It runs
-through the design elements, calling target functions as need arises
-to generate actual output.
-
-The user selects the target code generator with the -t flag on the
-command line.
-
-3.6 ATTRIBUTES
-
- NOTE: The $attribute syntax will soon be deprecated in favor of the
- Verilog-2001 attribute syntax, which is cleaner and standardized.
-
-The parser accepts, as an extension to Verilog, the $attribute module
-item. The syntax of the $attribute item is:
-
- $attribute (<identifier>, <key>, <value>);
-
-The $attribute keyword looks like a system task invocation. The
-difference here is that the parameters are more restricted then those
-of a system task. The <identifier> must be an identifier. This will be
-the item to get an attribute. The <key> and <value> are strings, not
-expressions, that give the key and the value of the attribute to be
-attached to the identified object.
-
-Attributes are [<key> <value>] pairs and are used to communicate with
-the various processing steps. See the documentation for the processing
-step for a list of the pertinent attributes.
-
-Attributes can also be applied to gate types. When this is done, the
-attribute is given to every instantiation of the primitive. The syntax
-for the attribute statement is the same, except that the <identifier>
-names a primitive earlier in the compilation unit and the statement is
-placed in global scope, instead of within a module. The semicolon is
-not part of a type attribute.
-
-Note that attributes are also occasionally used for communication
-between processing steps. Processing steps that are aware of others
-may place attributes on netlist objects to communicate information to
-later steps.
-
-Icarus Verilog also accepts the Verilog 2001 syntax for
-attributes. They have the same general meaning as with the $attribute
-syntax, but they are attached to objects by position instead of by
-name. Also, the key is a Verilog identifier instead of a string.
-
-4.0 Running iverilog
-
-The preferred way to invoke the compiler is with the iverilog(1)
-command. This program invokes the preprocessor (ivlpp) and the
-compiler (ivl) with the proper command line options to get the job
-done in a friendly way. See the iverilog(1) man page for usage details.
-
-
-4.1 EXAMPLES
-
-Example: Compiling "hello.vl"
-
------------------------- hello.vl ----------------------------
-module main();
-
-initial
- begin
- $display("Hi there");
- $finish ;
- end
-
-endmodule
-
---------------------------------------------------------------
-
-Ensure that "iverilog" is on your search path, and the vpi library
-is available.
-
-To compile the program:
-
- iverilog hello.vl
-
-(The above presumes that /usr/local/include and /usr/local/lib are
-part of the compiler search path, which is usually the case for gcc.)
-
-To run the program:
-
- ./a.out
-
-You can use the "-o" switch to name the output command to be generated
-by the compiler. See the iverilog(1) man page.
-
-5.0 Unsupported Constructs
-
-Icarus Verilog is in development - as such it still only supports a
-(growing) subset of Verilog. Below is a description of some of the
-currently unsupported Verilog features. This list is not exhaustive,
-and does not account for errors in the compiler. See the Icarus
-Verilog web page for the current state of support for Verilog, and in
-particular, browse the bug report database for reported unsupported
-constructs.
-
- - System functions are supported, but the return value is a little
- tricky. See SYSTEM FUNCTION TABLE FILES in the iverilog man page.
-
- - Specify blocks are parsed but ignored in general.
-
- - trireg is not supported. tri0 and tri1 are supported.
-
- - tran primitives, i.e. tran, tranif1, tranif0, rtran, rtranif1
- and rtranif0 are not supported.
-
- - Net delays, of the form "wire #N foo;" do not work. Delays in
- every other context do work properly, including the V2001 form
- "wire #5 foo = bar;"
-
- - Event controls inside non-blocking assignments are not supported.
- i.e.: a <= @(posedge clk) b;
-
- - Macro arguments are not supported. `define macros are supported,
- but they cannot take arguments.
-
-5.1 Nonstandard Constructs or Behaviors
-
-Icarus Verilog includes some features that are not part of the
-IEEE1364 standard, but have well defined meaning, and also sometimes
-gives nonstandard (but extended) meanings to some features of the
-language that are defined. See the "extensions.txt" documentation for
-more details.
-
- $is_signed(<expr>)
- This system function returns 1 if the expression contained is
- signed, or 0 otherwise. This is mostly of use for compiler
- regression tests.
-
- $sizeof(<expr>)
- $bits(<expr>)
- The $bits system function returns the size in bits of the
- expression that is its argument. The result of this
- function is undefined if the argument doesn't have a
- self-determined size.
-
- The $sizeof function is deprecated in favor of $bits, which is
- the same thing, but included in the SystemVerilog definition.
-
- $simtime
- The $simtime system function returns as a 64bit value the
- simulation time, unscaled by the time units of local
- scope. This is different from the $time and $stime functions
- which return the scaled times. This function is added for
- regression testing of the compiler and run time, but can be
- used by applications who really want the simulation time.
-
- Note that the simulation time can be confusing if there are
- lots of different `timescales within a design. It is not in
- general possible to predict what the simulation precision will
- turn out to be.
-
- $mti_random()
- $mti_dist_uniform
- These functions are similar to the IEEE1364 standard $random
- functions, but they use the Mersenne Twister (MT19937)
- algorithm. This is considered an excellent random number
- generator, but does not generate the same sequence as the
- standardized $random.
-
- Builtin system functions
-
- Certain of the system functions have well defined meanings, so
- can theoretically be evaluated at compile time, instead of
- using runtime VPI code. Doing so means that VPI cannot
- override the definitions of functions handled in this
- manner. On the other hand, this makes them synthesizable, and
- also allows for more aggressive constant propagation. The
- functions handled in this manner are:
-
- $bits
- $signed
- $sizeof
- $unsigned
-
- Implementations of these system functions in VPI modules will
- be ignored.
-
- Preprocessing Library Modules
-
- Icarus Verilog does preprocess modules that are loaded from
- libraries via the -y mechanism. However, the only macros
- defined during compilation of that file are those that it
- defines itself (or includes) or that are defined on the
- command line or command file.
-
- Specifically, macros defined in the non-library source files
- are not remembered when the library module is loaded. This is
- intentional. If it were otherwise, then compilation results
- might vary depending on the order that libraries are loaded,
- and that is too unpredictable.
-
- It is said that some commercial compilers do allow macro
- definitions to span library modules. That's just plain weird.
-
- Width in %t Time Formats
-
- Standard Verilog does not allow width fields in the %t formats
- of display strings. For example, this is illegal:
-
- $display("Time is %0t", %time);
-
- Standard Verilog instead relies on the $timeformat to
- completely specify the format.
-
- Icarus Verilog allows the programmer to specify the field
- width. The "%t" format in Icarus Verilog works exactly as it
- does in standard Verilog. However, if the programmer chooses
- to specify a minimum width (i.e., "%5t"), then for that display
- Icarus Verilog will override the $timeformat minimum width and
- use the explicit minimum width.
-
- vpiScope iterator on vpiScope objects.
-
- In the VPI, the normal way to iterate over vpiScope objects
- contained within a vpiScope object, is the vpiInternalScope
- iterator. Icarus Verilog adds support for the vpiScope
- iterator of a vpiScope object, that iterates over *everything*
- the is contained in the current scope. This is useful in cases
- where one wants to iterate over all the objects in a scope
- without iterating over all the contained types explicitly.
-
- time 0 race resolution.
-
- Combinational logic is routinely modeled using always
- blocks. However, this can lead to race conditions if the
- inputs to the combinational block are initialized in initial
- statements. Icarus Verilog slightly modifies time 0 scheduling
- by arranging for always statements with ANYEDGE sensitivity
- lists to be scheduled before any other threads. This causes
- combinational always blocks to be triggered when the values in
- the sensitivity list are initialized by initial threads.
-
- Nets with Types
-
- Icarus Verilog support an extension syntax that allows nets
- and regs to be explicitly typed. The currently supported types
- are logic, bool and real. This implies that "logic" and "bool"
- are new keywords. Typical syntax is:
-
- wire real foo = 1.0;
- reg logic bar, bat;
-
- ... and so forth. The syntax can be turned off by using the
- -g2 flag to iverilog, and turned on explicitly with the -g2x
- flag to iverilog.
-
-6.0 CREDITS
-
-Except where otherwise noted, Icarus Verilog, ivl and ivlpp are
-Copyright Stephen Williams. The proper notices are in the head of each
-file. However, I have early on received aid in the form of fixes,
-Verilog guidance, and especially testing from many people. Testers in
-particular include a larger community of people interested in a GPL
-Verilog for Linux.</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_icarus_vpi_mp.html b/docs/wiki/geda_icarus_vpi_mp.html
deleted file mode 100644
index 4d09414..0000000
--- a/docs/wiki/geda_icarus_vpi_mp.html
+++ /dev/null
@@ -1,155 +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>geda:icarus_vpi_mp</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="geda,icarus_vpi_mp" />
-<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/geda:icarus_vpi_mp?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:icarus_vpi_mp"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:icarus_vpi_mp"; />
-<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">
-
-
-
-<h1><a name="compile_front_end_for_vpi_modules_man-page" id="compile_front_end_for_vpi_modules_man-page">Compile front end for VPI modules man-page</a></h1>
-<div class="level1">
-<pre class="code">iverilog-vpi(1) $Date: 2004/10/04 01:10:53 $ iverilog-vpi(1)
-
-
-
-NAME
- iverilog-vpi - Compile front end for VPI modules
-
-
-SYNOPSIS
- iverilog-vpi [--name=name] sourcefile...
-
-
-DESCRIPTION
- iverilog-vpi is a tool to simplify the compilation of VPI modules for
- use with Icarus Verilog. It takes on the command line a list of C or
- C++ source files, and generates as output a linked VPI module. See the
- vvp(1) man page for a description of how the linked module is loaded by
- a simulation.
-
- The output is named after the first source file. For example, if the
- first source file is named foo.c, the output becomes foo.vpi.
-
-
-OPTIONS
- iverilog-vpi accepts the following options:
-
- -llibrary
- Include the named library in the link of the VPI module. This
- allows VPI modules to further reference external libraries.
-
-
- --name=name
- Normally, the output VPI module will be named after the first
- source file passed to the command. This flag sets the name
- (without the .vpi suffix) of the output vpi module.
-
-
- --install-dir
- This flag causes the program to print the install directory for
- VPI modules, then exit. It is a convenience for makefiles or
- automated plug-in installers.
-
-
-PC-ONLY OPTIONS
- The PC port of iverilog-vpi includes two special flags needed to sup-
- port the more intractable development environment. These flags help the
- program locate parts that it needs.
-
-
- -mingw=path
- Tell the program the root of the Mingw compiler tool suite. The
- vvp runtime is compiled with this compiler, and this is the
- compiler that iverilog-vpi expects to use to compile your
- source code. This is normally not needed, and if you do use it,
- it is only needed once. The compiler will save the path in the
- registry for use later.
-
-
- -ivl=path
- Set for the use during compilation the root if the Icarus Ver-
- ilog install. This is the place where you installed Icarus Ver-
- ilog when you ran the installer. This flag is also only needed
- once, and the path is stored in the registry for future use.
-
-
-UNIX-ONLY OPTIONS
- The UNIX version of iverilog-vpi includes additional flags to let Make-
- file gurus peek at the configuration of the iverilog installation.
- This way, Makefiles can be written that handle complex VPI builds
- natively, and without hard-coding values that depend on the system and
- installation. If used at all, these options must be used one at a
- time, and without any other options or directives.
-
-
- --cflags
- Print the compiler flags (CFLAGS or CXXFLAGS) needed to compile
- source code destined for a VPI module.
-
-
- --ldflags
- Print the linker flags (LDFLAGS) needed to link a VPI module.
-
-
- --ldlibs
- Print the libraries (LDLIBS) needed to link a VPI module.
-
-
- -m32 On 64bit systems that support it (and support vvp32) this flag
- requests a 32bit vpi binary instead of the default 64bit
- binary.
-
-
- Example GNU makefile that takes advantage of these flags:
-
- CFLAGS = -Wall -O $(CFLAGS_$@)
- VPI_CFLAGS := $(shell iverilog-vpi --cflags)
- CFLAGS_messagev.o = $(VPI_CFLAGS)
- CFLAGS_fifo.o = $(VPI_CFLAGS)
- messagev.o fifo.o: transport.h
- messagev.vpi: messagev.o fifo.o
- iverilog-vpi $^
-
-
-AUTHOR
- Steve Williams (steve@xxxxxxxxxx)
-
-
-SEE ALSO
- iverilog(1), vvp(1), <http://www.icarus.com/eda/verilog/>,
- <http://www.mingw.org>,
-
-
-COPYRIGHT
- Copyright �© 2002 Stephen Williams
-
- This document can be freely redistributed according to the terms of the
- GNU General Public License version 2.0
-
-
-
-Version $Date: 2004/10/04 01:10:53 $ iverilog-vpi(1)</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_icarus_vpi_within_vvp.html b/docs/wiki/geda_icarus_vpi_within_vvp.html
deleted file mode 100644
index 7643666..0000000
--- a/docs/wiki/geda_icarus_vpi_within_vvp.html
+++ /dev/null
@@ -1,200 +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>geda:icarus_vpi_within_vvp</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="geda,icarus_vpi_within_vvp" />
-<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/geda:icarus_vpi_within_vvp?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:icarus_vpi_within_vvp"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:icarus_vpi_within_vvp"; />
-<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">
-
-
-
-<h1><a name="vpi_within_vvp" id="vpi_within_vvp">VPI_within_VVP</a></h1>
-<div class="level1">
-<pre class="code">/*
- * Copyright (c) 2001 Stephen Williams (steve@xxxxxxxxxx)
- *
- * $Id: vpi.txt,v 1.7 2003/02/09 23:33:26 steve Exp $
- */
-
-
-VPI WITHIN VVP
-
-System tasks and functions in Verilog are implemented in Icarus
-Verilog by C routines written with VPI. This implies that the vvp
-engine must provide at least a subset of the Verilog VPI
-interface. The minimalist concepts of vvp, however, make the method
-less then obvious.
-
-Within a Verilog design, there is a more or less fixed web of
-vpiHandles that is the design database as is available to VPI
-functions. The Verilog standard defines quite a lot of types, but the
-vvp only implements the ones it needs. The VPI web is added into the
-design using special pseudo-ops that create the needed objects.
-
-
-LOADING VPI MODULES
-
-The vvp runtime loads VPI modules at runtime before the parser reads
-in the source files. This gives the modules a chance to register tasks
-and functions before the source is compiled. This allows the compiler
-to resolve references to system tasks and system functions to a
-vpiHandle at compile time. References to missing tasks/function can
-thus be caught before the simulation is run.
-
- NOTE: This also, miraculously, allows for some minimal support of
- the compiletf call. From the perspective of VPI code, compilation
- of the VVP source is not unlike compilation of the original
- Verilog.
-
-The handle that the vvp threads have to the VPI are the vpiHandles of
-the system tasks and functions. The %vpi_call instruction, once compiled,
-carries the vpiHandle of the system task.
-
-
-SYSTEM TASK CALLS
-
-A system task call invokes a VPI routine, and makes available to that
-routine the arguments to the system task. The called routine gets
-access to the system task call by calling back the VPI requesting the
-handle. It uses the handle, in turn, to get hold of the operands for
-the task.
-
-All that vvp needs to know about a system task call is the handle of
-the system task definitions (created by the vpi_register_systf
-function) and the arguments of the actual call. The arguments are
-tricky because the list has no bound, even though each particular call
-in the Verilog source has a specific set of parameters.
-
-Since each call takes a fixed number of parameters, the input source
-can include in the statement the list of arguments. The argument list
-will not fit in a single generated instruction, but a vpiHandle that
-refers to a vpiSysTfCall does. Therefore, the compiler can take the
-long argument list and form a vpiSysTaskCall object. The generated
-instruction then only needs to be a %vpi_call with the single parameter
-that is the vpiHandle for the call.
-
-
-SYSTEM FUNCTION CALLS
-
-System function calls are similar to system tasks. The only
-differences are that all the arguments are input only, and there is a
-single magic output that is the return value. The same %vpi_call can
-even be used to call a function.
-
-System functions, like system tasks, can only be called from thread
-code. However, they can appear in expressions, even when that
-expression is entirely structural. The desired effect is achieved by
-writing a wrapper thread that calls the function when inputs change,
-and that writes the output into the containing expression.
-
-
-SYSTEM TASK/FUNCTION ARGUMENTS
-
-The arguments to each system task or call are not stored in the
-instruction op-code, but in the vpiSysTfCall object that the compiler
-creates and that the %vpi_call instruction ultimately refers to. All
-the arguments must be some sort of object that can be represented by a
-vpiHandle at compile time.
-
-Arguments are handled at compile time by the parser, which uses the
-argument_list rule to build a list of vpiHandle objects. Each argument
-in the argument_list invokes whatever function is appropriate for the
-token in order to make a vpiHandle object for the argument_list. When
-all this is done, an array of vpiHandles is passed to code to create a
-vpiSysTfCall object that has all that is needed to make the call.
-
-
-SCOPES
-
-VPI can access scopes as objects of type vpiScope. Scopes have names
-and can also contain other sub-scopes, all of which the VPI function
-can access by the vpiInternalScope reference. Therefore, the run-time
-needs to form a tree of scopes into which other scoped VPI objects are
-placed.
-
-A scope is created with a .scope directive, like so:
-
- <label> .scope "name" [, <parent>];
- .timescale <units>;
-
-The scope takes a string name as the first parameter. If there is an
-additional parameter, it is a label of the directive for the parent
-scope. Scopes that have no parent are root scopes. It is an error to
-declare a scope with the same name more then once in a parent scope.
-
-The name string given when creating the scope is the basename for the
-scope. The vvp automatically constructs full names from the scope
-hierarchy, and runtime VPI code can access that full name with the
-vpiFullname reference.
-
-The .timescale directive changes the scope units from the simulation
-precision to the specified precision. The .timescale directive affects
-the current scope.
-
-Objects that place themselves in a scope place themselves in the
-current scope. The current scope is the one that was last mentioned by
-a .scope directive. If the wrong scope is current, the label on a
-scope directive can be used to resume a scope. The syntax works like
-this:
-
- .scope <symbol>;
-
-In this case, the <symbol> is the label of a previous scope directive,
-and is used to identify the scope to be resumed. A scope resume
-directive cannot have a label.
-
-
-VARIABLES
-
-Reg vectors (scalars are vectors of length 1) are created by .var
-statements in the source. The .var statement includes the declared
-name of the variable, and the indices of the MSB and LSB of the
-vector. The vpiHandle is then created with this information, and the
-vpi_ipoint_t pointer to the LSB functor of the variable. VPI programs
-access the vector through the vpiHandle and related functions. The VPI
-code gets access to the declared indices.
-
-The VPI interface to variable (vpiReg objects) uses the MSB and LSB
-values that the user defined to describe the dimensions of the
-object.
-
-/*
- * Copyright (c) 2001 Stephen Williams (steve@xxxxxxxxxx)
- *
- * This source code is free software; you can redistribute it
- * and/or modify it in source code form under the terms of the GNU
- * General Public License as published by the Free Software
- * Foundation; either version 2 of the License, or (at your option)
- * any later version.
- *
- * This program is distributed in the hope that it will be useful,
- * but WITHOUT ANY WARRANTY; without even the implied warranty of
- * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
- * GNU General Public License for more details.
- *
- * You should have received a copy of the GNU General Public License
- * along with this program; if not, write to the Free Software
- * Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA
- */</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_icarus_vvp_runtime.html b/docs/wiki/geda_icarus_vvp_runtime.html
deleted file mode 100644
index 0eee6c8..0000000
--- a/docs/wiki/geda_icarus_vvp_runtime.html
+++ /dev/null
@@ -1,179 +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>geda:icarus_vvp_runtime</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="geda,icarus_vvp_runtime" />
-<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/geda:icarus_vvp_runtime?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:icarus_vvp_runtime"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:icarus_vvp_runtime"; />
-<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">
-
-
-
-<h1><a name="icarus_verilog_vvp_runtime_engine_man-page" id="icarus_verilog_vvp_runtime_engine_man-page">Icarus Verilog vvp runtime engine man-page</a></h1>
-<div class="level1">
-<pre class="code">vvp(1) $Date: 2005/01/29 06:28:19 $ vvp(1)
-
-
-
-NAME
- vvp - Icarus Verilog vvp runtime engine
-
-
-SYNOPSIS
- vvp [-sv] [-Mpath] [-mmodule] [-llogfile] inputfile [extended-args...]
-
-
-DESCRIPTION
- vvp is the run time engine that executes the default compiled form gen-
- erated by Icarus Verilog. The output from the iverilog command is not
- by itself executable on any platform. Instead, the vvp program is
- invoked to execute the generated output file.
-
-
-OPTIONS
- vvp accepts the following options:
-
- -llogfile
- This flag specifies a logfile where all MCI <stdlog> output
- goes. Specify logfile as �-� to send log output to <stderr>.
- $display and friends send their output both to <stdout> and
- <stdlog>.
-
- -Mpath This flag adds a directory to the path list used to locate VPI
- modules. The default path includes only the install directory
- for the system.vpi module, but this flag can add other directo-
- ries. Multiple paths are allowed, and modules will be searched
- in order.
-
- -mmodule
- Tell the vvp run time to load the named module before executing
- the simulation. The system.vpi module is loaded by default, but
- additional modules, including modules that you compiled
- locally, can be specified with this flag. Any number of modules
- can be loaded, and they will be linked in the order they are
- listed on the command line.
-
- Normally, you only need to specify the name of the module,
- without any directory path or .vpi suffix and the search path
- is scanned to find the module. However, if the name includes at
- least one directory character, then the search path is not
- scanned and the name is assumed to be a complete file name.
-
- -s Stop. This will cause the simulation to stop in the beginning,
- before any events are scheduled. This allows the interactive
- user to get hold of the simulation just before it starts.
-
- -v Turn on verbose messages. This will cause information about run
- time progress to be printed to standard out.
-
-
-EXTENDED ARGUMENTS
- The vvp options described above must come before the design file name.
- After the design file name, however, there may be any number of unspec-
- ified arguments. These arguments are not interpreted by vvp but are
- instead passed on to the executed design, and are available via the
- $test$plusargs and $value$plusargs system functions.
-
- Arguments that do not start with the plus(+) character are not avail-
- able to the $plusargs system tasks, but can still be accessed via PLI
- code via the vpi_get_vlog_info function. This means that vpi modules
- may use arguments that do not start with + and be assured that they do
- not interfere with user defined plus-args.
-
- There are a few extended arguments that are interpreted by the standard
- system.vpi module, which implements the standard system tasks and so is
- always included. These arguments are described here.
-
- -vcd|-vcd-none
- This extended argument sets the wave dump format to VCD. This
- is the default in the absence of any IVERILOG_DUMPER environ-
- ment variable. The VCD dump files are large and ponderous, but
- are also maximally compatible with third party tools that read
- waveform dumps.
-
- The -vcd-none variant actually suppresses all waveform output. This can
- make long simulations run faster.
-
-
- -lxt|-lxt-speed|-lxt-space|-lxt-none
- These extended arguments set the wave dump format to lxt, pos-
- sibly with format optimizations. The -lxt-space flag sets the
- output format to lxt with full compression enabled. The result-
- ing files are quite small. The -lxt-speed chooses the lxt com-
- pression mode that leads to the best execution time and the
- fastest read time, at the expense of some file size.
-
- The -lxt-none variant actually suppresses all waveform output. This can
- make long simulations run faster.
-
-
- -lxt2 The LXT2 format is slower then LXT (faster then VCD) but takes
- less space, and is written out incrementally. Thus, you can
- view lxt2 files while a simulation is still running (or paused)
- or if your simulation crashes or is killed, you still have a
- useful dump.
-
-
-ENVIRONMENT
- The vvp command also accepts some environment variables that control
- its behavior. These can be used to make semi-permanent changes.
-
-
- IVERILOG_DUMPER=lxt|lxt2|vcd|none
- This selects the output format for the waveform output. Nor-
- mally, waveforms are dumped in vcd format, but this variable
- can be used to select lxt format, which is far more compact,
- though limited to gtkwave or compatible viewers. It can also be
- used to suppress VCD output, a time-saver for regression tests.
-
-
-INTERACTIVE MODE
- The simulation engine supports an interactive mode. The user may inter-
- rupt the simulation (typically by typing Ctrl-C) to get to the interac-
- tive prompt. From that prompt, the help command prints a brief summary
- of the available commands.
-
- The interactive mode may also be entered by a call to the $stop system
- task from within the simulation, or by a call to the vpi_control VPI
- function with the vpiStop control argument. These means of entering
- interactive mode are equivalent.
-
-
-AUTHOR
- Steve Williams (steve@xxxxxxxxxx)
-
-
-SEE ALSO
- iverilog(1), iverilog-vpi(1), <http://www.icarus.com/eda/verilog/>
-
-
-COPYRIGHT
- Copyright �© 2001-2003 Stephen Williams
-
- This document can be freely redistributed according to the terms of the
- GNU General Public License version 2.0
-
-
-
-Version $Date: 2005/01/29 06:28:19 $ vvp(1)</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_icarus_vvp_simulation.html b/docs/wiki/geda_icarus_vvp_simulation.html
deleted file mode 100644
index 11617e8..0000000
--- a/docs/wiki/geda_icarus_vvp_simulation.html
+++ /dev/null
@@ -1,1026 +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>geda:icarus_vvp_simulation</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="keywords" content="geda,icarus_vvp_simulation" />
-<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/geda:icarus_vvp_simulation?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:icarus_vvp_simulation"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:icarus_vvp_simulation"; />
-<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">
-
-
-
-<h1><a name="vvp_simulation_engine" id="vvp_simulation_engine">VVP Simulation Engine</a></h1>
-<div class="level1">
-<pre class="code">/*
- * Copyright (c) 2001 Stephen Williams (steve@xxxxxxxxxx)
- *
- * $Id: README.txt,v 1.74 2005/11/25 17:55:26 steve Exp $
- */
-
-VVP SIMULATION ENGINE
-
-The VVP simulator takes as input source code not unlike assembly
-language for a conventional processor. It is intended to be machine
-generated code emitted by other tools, including the Icarus Verilog
-compiler, so the syntax, though readable, is not necessarily
-convenient for humans.
-
-
-GENERAL FORMAT
-
-The source file is a collection of statements. Each statement may have
-a label, an opcode, and operands that depend on the opcode. For some
-opcodes, the label is optional (or meaningless) and for others it is
-required.
-
-Every statement is terminated by a semicolon. The semicolon is also
-the start of a comment line, so you can put comment text after the
-semicolon that terminates a statement. Like so:
-
- Label .functor and, 0x5a, x, y ; This is a comment.
-
-The semicolon is required, whether the comment is there or not.
-
-Statements may span multiple lines, as long as there is no text (other
-then the first character of a label) in the first column of the
-continuation line.
-
-HEADER SYNTAX
-
-Before any other non-commentary code starts, the source may contain
-some header statements. These are used for passing parameters or
-global details from the compiler to the vvp run-time. In all cases,
-the header statement starts with a left-justified keyword.
-
-* :module "name" ;
-
-This header statement names a vpi module that vvp should load before
-the rest of the program is compiled. The compiler looks in the
-standard VPI_MODULE_PATH for files named "name.vpi", and tries to
-dynamic load them.
-
-* :vpi_time_precision [+|-]<value>;
-
-This header statement specifies the time precision of a single tick of
-the simulation clock. This is mostly used for display (and VPI)
-purposes, because the engine itself does not care about units. The
-compiler scales time values ahead of time.
-
-The value is the size of a simulation tick in seconds, and is
-expressed as a power of 10. For example, +0 is 1 second, and -9 is 1
-nanosecond. If the record is left out, then the precision is taken to
-be +0.
-
-LABELS AND SYMBOLS
-
-Labels and symbols consist of the characters:
-
- a-z
- A-Z
- 0-9
- .$_<>
-
-Labels and symbols may not start with a digit or a '.', so that they
-are easily distinguished from keywords and numbers. A Label is a
-symbol that starts a statement. If a label is present in a statement,
-it must start in the first text column. This is how the lexical
-analyzer distinguishes a label from a symbol. If a symbol is present
-in a statement, it is in the operand. Opcodes of statements must be a
-keyword.
-
-Symbols are references to labels. It is not necessary for a label to
-be declared before its use in a symbol, but it must be declared
-eventually. When symbols refer to functors, the symbol represents the
-vvp_ipoint_t pointer to the output. (Inputs cannot, and need not, be
-references symbolically.)
-
-If the functor is part of a vector, then the symbol is the
-vvp_ipoint_t for the first functor. The [] operator can then be used
-to reference a functor other then the first in the vector.
-
-There are some special symbols that in certain contexts have special
-meanings. As inputs to functors, the symbols "C<0>", "C<1>", "C<x>"
-and "C<z>" represent a constant driver of the given value.
-
-
-SCOPE STATEMENTS:
-
-
-PARAMETER STATEMENTS:
-
-Parameters are named constants within a scope. These parameters have a
-type and value, and also a label so that they can be referenced as VPI
-objects.
-
-The syntax of a parameter is:
-
- <label> .param <name>, <type>, <value>;
-
-The <name> is a string that names the parameter. The name is placed in
-the current scope as a vpiParameter object. The <type> is one of the
-following:
-
- real -- The parameter has a real value
- string -- The parameter has a string value
- [<msb>,<lsb>,<s>]
- -- The parameter is a vector, with specified
- indices. The <s> is s or u for signed or
- unsigned.
-
-The value, then, is appropriate for the data type. For example:
-
- P_123 .param "hello", string, "Hello, World.";
-
-
-FUNCTOR STATEMENTS:
-
-A functor statement is a statement that uses the ``.functor''
-opcode. Functors are the basic structural units of a simulation, and
-include a type (in the form of a truth table) and up to four inputs. A
-label is required for functors.
-
-The general syntax of a functor is:
-
- <label> .functor <type> [ (<delay>) ], symbol_list ;
-
-The symbol list is 4 names of labels of other functors. These connect
-inputs of the functor of the statement to the output of other
-functors. If the input is unconnected, use a C<?> symbol instead. The
-type selects the truth lookup table to use for the functor
-implementation. Most of the core gate types have built in tables.
-
-The initial values of all the inputs and the output is x. Any other
-value is passed around as run-time behavior. If the inputs have C<?>
-symbols, then the inputs are initialized to the specified bit value,
-and if this causes the output to be something other then x, a
-propagation event is created to be executed at the start of run time.
-
-The strengths of inputs are ignored by functors, and the output has
-fixed drive0 and drive1 strengths. So strength information is
-typically lost as it passes through functors.
-
-Almost all of the structural aspects of a simulation can be
-represented by functors, which perform the very basic task of
-combining up to four inputs down to one output.
-
-- MUXZ
-
- Q | A B S n/a
- --+-------------
- A | * * 0
- B | * * 1
-
-
-DFF STATEMENTS:
-
-The Verilog language itself does not have a DFF primitive, but post
-synthesis readily creates DFF devices that are best simulated with a
-common device. Thus, there is the DFF statement to create DFF devices:
-
- <label> .dff <d>, <clk>, <ce>, <async-input>;
-
-The generated functor is generally synchronous on the <clk> rising
-edge of <clk>, with the <ce> enable active high. The <clk> and <ce>
-are single bit vectors (or scalars) on ports 1 and 2. Port-0 is any
-type of datum at all. The device will transfer the input to the output
-when it is loaded by a clock. The <async-input> is a special
-asynchronous input that is immediately stored and transferred to the
-output when data arrives here. This is useful for implementing
-asynchronous set/clear functions.
-
-UDP STATEMENTS:
-
-A UDP statement either defines a User Defined Primitive, or
-instantiates a previously defined UDP by creating a UDP functor. A
-UDP functor has as many inputs as the UDP definition requires.
-
-UDPs come in sequential and combinatorial flavors. Sequential UDPs
-carry an output state and can respond to edges at the inputs. The
-output of combinatorial UDPs is a function of its current inputs
-only.
-
-The function of a UDP is defined via a table. The rows of the table
-are strings which describe input states or edges, and the new output
-state. Combinatorial UDPs require one character for each input, and
-one character at the end for the output state. Sequential UDPs need
-an additional char for the current state, which is the first char of
-the row.
-
-Any input transition or the new state must match at most one row (or
-all matches must provide the same output state). If no row matches,
-the output becomes 1'bx.
-
-The output state can be specified as "0", "1", or "x". Sequential
-UDPs may also have "-": no change.
-
-An input or current output state can be
-
- "1": 1
- "0": 0
- "x": x
- "b": 1, 0
- "h": 1, x
- "l": 0, x
- "?": 1, 0, x
-
-For Sequential UDPs, at most one input state specification may be
-replaced by an edge specification. Valid edges are:
-
- "*": (??) "_": (?0) "+": (?1) "%": (?x)
- "P": (0?) "r": (01) "Q": (0x)
- "N": (1?) "f": (10) "M": (1x)
- "B": (x?) "F": (x0) "R": (x1)
-
- "n": (1?) | (?0)
- "p": (0?) | (?1)
-
-A combinatorial UDP is defined like this:
-
- <type> .udp/comb "<name>", <number>, "<row0>", "<row1>", ... ;
-
-<type> is a label that identifies the UDP. <number> is the number of
-inputs. "<name>" is there for public identification. Sequential UDPs
-need an additional initialization value:
-
- <type> .udp/sequ "<name>", <number>, <init>, "<row0>", "<row1>", ... ;
-
-<init> is the initial value for all instances of the UDP. We do not
-provide initial values for individual instances. <init> must be a
-number 0, 1, or 2 (for 1'bx).
-
-A UDP functor instance is created so:
-
- <label> .udp <type>, <symbol_list> ;
-
-Where <label> identifies the functor, <type> is the label of a UDP
-defined earlier, and <symbol_list> is a list of symbols, one for each
-input of the UDP.
-
-
-VARIABLE STATEMENTS:
-
-A variable is a bit vector that can be written by behavioral code (so
-has no structural input) and propagates its output to a functor. The
-general syntax of a variable is:
-
- <label> .var "name", <msb>, <lsb>;
- <label> .var/s "name", <msb>, <lsb>;
- <label> .var/real "name", <msb>, <lsb>;
-
-The "name" is the declared base name of the original variable, for the
-sake of VPI code that might access it. The variable is placed in the
-current scope. The variable also has a width, defined by the indices
-for the most significant and lest significant bits. If the indices are
-equal (normally 0) the vector has width of one. If the width is greater
-then one, a contiguous array of functors is created and the value of
-the label is the address of the least significant bit.
-
-A variable does not take inputs, since its value is set behaviorally
-by assignment events. It does have output, though, and its output is
-propagated into the net of functors in the usual way.
-
-A variable gets its value by assignments from procedural code: %set
-and %assign. These instructions write values to the port-0 input. From
-there, the value is held.
-
-Behavioral code can also invoke %cassign/v statements that work like
-%set/v, but instead write to port-1 of the variable node. Writes to
-port-1 of a variable activate continuous assign mode, where the values
-written to port-0 are ignored. The continuous assign mode remains
-active until a long(1) is written to port-3 (a command port).
-
-Behavioral code may also invoke %force/v statements that write to port-2
-to invoke force mode. This overrides continuous assign mode until a
-long(2) is written to port-3 to disable force mode.
-
-NET STATEMENTS:
-
-A net is similar to a variable, except that a thread cannot write to
-it (unless it uses a force) and it is given a different VPI type
-code. The syntax of a .net statement is also similar to but not
-exactly the same as the .var statement:
-
- <label> .net "name", <msb>, <lsb>, <symbol>;
- <label> .net/s "name", <msb>, <lsb>, <symbol>;
- <label> .net8 "name", <msb>, <lsb>, <symbol>;
- <label> .net8/s "name", <msb>, <lsb>, <symbol>;
- <label> .net/real "name", <msb>, <lsb>, <symbol>;
- <label> .alias "name", <msb>, <lsb>, <symbol>;
-
-
-Like a .var statement, the .net statement creates a VPI object with
-the basename and dimensions given as parameters. The symbol is a
-functor that feeds into the vector of the net, and the vpiHandle
-holds references to that functor.
-
-The input of a .net is replicated to its output. In this sense, it
-acts like a diode. The purpose of this node is to hold various VPI
-and event trappings. The .net and .net8 nodes are vector types. They
-both may represent wires, but the .net8 nodes preserve strength values
-that arrive through them, while .net nodes reduce strength values to
-4-value logic. The .net8 nodes should only be used when strength
-information really is possible.
-
-The <label> is required and is used to locate the net object that is
-represents. This label does not map to a functor, so only references
-that know they want to access .nets are able to locate the symbol. In
-particular, this includes behavioral %load and %wait instructions. The
-references to net and reg objects are done through the .net label
-instead of a general functor symbol. The instruction stores the
-functor pointer, though.
-
-The .alias statements do not create new nodes, but instead create net
-names that are aliases of an existing node. This handles special cases
-where a net has different names, possibly in different scopes.
-
-MEMORY STATEMENTS:
-
-Memories are arrays of words, each word a vvp_vector4_t vector of the
-same width. The memory is canonically addressed as a 1-dimensional
-array of words, although indices are stored with the memory for
-calculating a canonical address from a multi-dimensional address.
-
-Three types of memory statement perform (1) creation of a memory, (2)
-connecting a read port to an existing memory, and (3) initializing the
-memory's contents.
-
- <label> .mem "name", <msb>,<lsb>, <last>,<first> ... ;
-
-The pair of numbers <msb>,<lsb> defines the word width. The pair
-<last>,<first> defines the address range. Multiple address ranges are
-allowed for multidimensional indexing. This statement creates the
-memory array and makes it available to procedural code.
-
-Procedural access to the memory references the memory as single array
-of words, with the base address==0, and the last address the size (in
-words) of the memory -1. It is up to the compiler to convert Verilog
-index sets to a canonical address. The multi-dimensional index set is
-available for VPI use.
-
-Structural read access is implemented in terms of address and data
-ports. The addresses applied to the address port are expected to be
-in canonical form.
-
-A read port is a functor that takes a single input, the read address,
-and outputs the word value at the given (canonical) address.
-
- <label> .mem/port <memid>, <address> ;
-
-<label> identifies the vector of output functors, to allow connections
-to the data output. <memid> is the label of the memory.
-
-Any address input change, or any change in the addressed memory
-contents, is immediately propagated to the port output.
-
-A write port is a superset of a read port. It is a 4-input functor
-that accepts the word address, an event input, a write enable input,
-and the data input.
-
- <label> .mem/port <memid>, <address>, <event>, <we>, <data> ;
-
-<event> is an event functor that triggers a write, if the <we> input
-is true. <data> is the input that connect to the data input
-port. For asynchronous transparent write operation, connect
-<event> to C4<z>, the RAM will transparently follow any changes on
-address and data lines, while <we> is true.
-
-There is no Verilog construct that calls for a structural write port
-to a memory, but synthesis may ask for lpm_ram_d[pq] objects.
-
-To initialize a memory, use:
-
- .mem/init <memid> <start>, val , val ... ;
-
-<memid> is the label of the memory, and the <start> is the start
-address (canonical) of the first word to be initialized. The start
-address allows multiple statements be used to initialize words of a
-memory.
-
-The values are one per word.
-
-Procedural access to the memory employs an index register to address a
-bit location in the memory, via the commands:
-
- %load/m <bit>, <memid> ;
- %set/m <memid>, <bit> ;
- %assign/m <memid>, <delay>, <bit> ;
-
-The memory bit is addressed by index register 3. The value of
-register 3 is the index in the memory's bit space, where each data
-word occupies a multiple of four bits.
-
-
-EVENT STATEMENTS
-
-Threads need to interact with the functors of a netlist synchronously,
-as well as asynchronously. There are cases where the web of functors
-needs to wake up a waiting thread. The web of functors signals threads
-through .event objects, that are declared like so:
-
- <label> .event <type>, <symbols_list>;
- <label> .event "name";
-
-
-This event statement declares an object that a %wait instruction
-can take as an operand. When a thread executes a %wait, it puts
-itself in the notification list of the event and suspends. The
-<symbols_list> is a set of inputs that can trigger the event.
-
-The <type> describes the conditions needed to trigger the event. It
-may be posedge, negedge or edge. If the type is instead a "name"
-string, then this is a named event which receives events by the %set
-instruction instead of from the output of a functor.
-
-If the event has inputs (a requirement unless it is a named event)
-then it has up to 4 symbols that address functors. The event then
-detects the appropriate edge on any of the inputs and signals when the
-event is true. Normally (in Verilog) a posedge or negedge event only
-watches a single bit, so the generated code would only include a
-single symbol for the addressed bit. However, if there are several
-events of the same edge in an event OR expression, the compiler may
-combine up to 4 into a single event.
-
-If many more events need to be combined together (for example due to
-an event or expression in the Verilog) then this form can be used:
-
- <label> .event/or <symbols_list>;
-
-In this case, the symbols list all the events that are to be combined
-to trigger this event. Only one of the input events needs to trigger
-to make this one go.
-
-
-RESOLVER STATEMENTS:
-
-Resolver statements are strength-aware functors with 4 inputs, but
-their job typically is to calculate a resolved output using strength
-resolution. The type of the functor is used to select a specific
-resolution function.
-
- <label> .resolv tri, <symbols_list>;
- <label> .resolv tri0, <symbols_list>;
- <label> .resolv tri1, <symbols_list>;
-
-The output from the resolver is vvp_vector8_t value. That is, the
-result is a vector with strength included.
-
-
-PART SELECT STATEMENTS:
-
-Part select statements are functors with three inputs. They take in at
-port-0 a vector, and output a selected (likely smaller) part of that
-vector. The other inputs specify what those parts are, as a canonical
-bit number, and a width. Normally, those bits are constant values.
-
- <label> .part <symbol>, <base>, <wid>;
- <label> .part/pv <symbol>, <base>, <wid>, <vector_wid>;
- <label> .part/v <symbol>, <symbol>, <wid>;
-
-The input is typically a .reg or .net, but can be any vector node in
-the netlist.
-
-The .part/pv variation is the inverse of the .part version, in that
-the output is actually written to a *part* of the output. The node
-uses special part-select-write functions to propagate a part of a
-network. The <vector_wid> is the total width of the destination net
-that part is written to. Destination nodes use this value to check
-further output widths.
-
-The .part/v variation takes a vector (or long) input on port-1 as the
-base of the part select. Thus, the part select can move around.
-
-PART CONCATENATION STATEMENTS:
-
-The opposite of the part select statement is the part concatenation
-statement. The .concat statement is a functor node that takes at input
-vector values and produces a single vector output that is the
-concatenation of all the inputs.
-
- <label> .concat [W X Y Z], <symbols_list> ;
-
-The "[" and "]" tokens surround a set of 4 numbers that are the
-expected widths of all the inputs. These widths are needed to figure
-the positions of the input vectors in the generated output, and are
-listed in order LSB to MSB. The inputs themselves are also listed LSB
-to MSB, with the LSB vector input coming through port-0 of the real
-functor.
-
-The initial output value is (W+X+Y+Z) bits of 'bx. As input values are
-propagated, the bits are placed in the correct place in the output
-vector value, and a new output value is propagated.
-
-
-REPEAT VECTOR STATEMENTS:
-
-The repeat vector statement is similar to the concatenation statement,
-expect that the input is repeated a constant number of times. The
-format of the repeat vector statement is:
-
- <label> .repeat <wid>, <rept count>, <symbol> ;
-
-In this statement, the <wid> is a decimal number that is the width of
-the *output* vector. The <rept count> is the number of time the input
-vector value is repeated to make the output width. The input width is
-implicit from these numbers. The <symbol> is then the input source.
-
-REDUCTION LOGIC
-
-The reduction logic statements take in a single vector, and propagate
-a single bit.
-
- <label> .reduce/and <symbol> ;
- <label> .reduce/or <symbol> ;
- <label> .reduce/xor <symbol> ;
- <label> .reduce/nand <symbol> ;
- <label> .reduce/nor <symbol> ;
- <label> .reduce/xnor <symbol> ;
-
-the device has a single input, which is a vector of any width. The
-device performs the logic on all the bits of the vector (a la Verilog)
-and produces and propagates a single bit width vector.
-
-EXPANSION LOGIC
-
-Sign extension nodes are the opposite of reduction logic, in that they
-take a narrow vector, or single bit, and pad it out to a wider
-vector.
-
- <label> .expand/s <wid>, <symbol> ;
-
-The .expand/s node takes an input symbol and sign-extends it to the
-given width.
-
-FORCE STATEMENTS (old method - remove me):
-
-A force statement creates functors that represent a Verilog force
-statement.
-
- <label> .force <signal>, <symbol_list>;
-
-The symbol <signal> represents the signal which is to be forced. The
-<symbol_list> specifies the bits of the expression that is to be
-forced on the <signal>. The <label> identifies the force functors.
-There will be as many force functors as there are symbols in the
-<symbol_list>.
-
-To activate and deactivate a force on a single bit, use:
-
- %force <label>, <width>;
- %release <signal>;
-
-<label>/<width> is the label/width of a vector of force functors.
-<signal> is the label of the functor that drives the signal that is
-being forced.
-
-FORCE STATEMENTS (new method - implement me):
-
-A %force instruction, as described in the .var section, forces a
-constant value onto a .var or .net, and the matching %release releases
-that value. However, there are times when the value of a functor
-(i.e. another .net) needs to be forced onto a .var or .net. For this
-task, the %force/link instruction exists:
-
- %force/link <dst>, <src> ;
- %release/link <dst> ;
-
-This causes the output of the node <src> to be linked to the force
-input of the <dst> .var/.net node. When linked, the output functor
-will automatically drive values to the force port of the destination
-node. The matching %release/link instruction removes the link (a
-%release is still needed) to the destination. The %release/link
-releases the last %force/link, no matter where the link is from. A new
-%force/link will remove a previous link.
-
-The instructions:
-
- %cassign/link <dst>, <src> ;
- %deassign/link <dst> ;
-
-are the same concept, but for the continuous assign port.
-
-STRUCTURAL ARITHMETIC STATEMENTS:
-
-The various Verilog arithmetic operators (+-*/%) are available to
-structural contexts as two-input functors that take in vectors. All of
-these operators take two inputs and generate a fixed width output. The
-input vectors will be padded if needed to get the desired output width.
-
- <label> .arith/sub <wid>, <A>, <B>;
- <label> .arith/sum <wid>, <A>, <B>;
- <label> .arith/mult <wid>, <A>, <B>;
- <label> .arith/div <wid>, <A>, <B>;
- <label> .arith/mod <wid>, <A>, <B>;
-
-In all cases, there are no width limits, so long as the width is
-fixed.
-
-NOTE: The .arith/mult inputs are not necessarily the width of the
-output. I have not decided how to handle this.
-
-These devices support .s and .r suffixes. The .s means the node is a
-signed vector device, the .r a real valued device.
-
-STRUCTURAL COMPARE STATEMENTS:
-
-The arithmetic statements handle various arithmetic operators that
-have wide outputs, but the comparators have single bit output, so they
-are implemented a bit differently. The syntax, however, is very
-similar:
-
- <label> .cmp/eeq <wid>, <A>, <B>;
- <label> .cmp/nee <wid>, <A>, <B>;
- <label> .cmp/eq <wid>, <A>, <B>;
- <label> .cmp/ne <wid>, <A>, <B>;
- <label> .cmp/ge <wid>, <A>, <B>;
- <label> .cmp/gt <wid>, <A>, <B>;
- <label> .cmp/ge.s <wid>, <A>, <B>;
- <label> .cmp/gt.s <wid>, <A>, <B>;
-
-Whereas the arithmetic statements generate an output the width of
-<wid>, the comparisons produce a single bit vector result. The plain
-versions do unsigned comparison, but the ".s" versions to signed
-comparisons. (Equality doesn't need to care about sign.)
-
-
-STRUCTURAL SHIFTER STATEMENTS:
-
-Variable shifts in structural context are implemented with .shift
-statements:
-
- <label> .shift/l <wid>, <data symbol>, <shift symbol>;
- <label> .shift/r <wid>, <data symbol>, <shift symbol>;
-
-The shifter has a width that defines the vector width of the output, a
-<data symbol> that is the input data to be shifted and a <shift-symbol>
-that is the amount to shift. The vectors that come from port 0 are the
-data to be shifted and must have exactly the width of the output. The
-input to port 1 is the amount to shift.
-
-
-STRUCTURAL FUNCTION CALLS:
-
-The .ufunc statement defines a call to a user defined function.
-
- <label> .ufunc <flabel>, <wid>, <isymbols> ( <psymbols> ) <rsymbol> ;
-
-The <flabel> is the code label for the first instruction of the
-function implementation. This is code that the simulator will branch
-to.
-
-The <wid> is the width of the output vector in bits.
-
-The <isymbols> is a list of net symbols for each of the inputs to the
-function. These are points in the net, and the ufunc device watches
-these nets for input changes.
-
-The <psymbols> list is exactly the same size as the <isymbols>
-list. The <psymbols> are variables that represent the input ports for
-the function. The ufunc performs an assignment to these variables
-before calling the function.
-
-Finally, the <rsymbol> is the variable within the function where the
-result will be found when the function code ends. This value is picked
-up and propagated to the output of the functor.
-
-THREAD STATEMENTS:
-
-Thread statements create the initial threads for a simulation. These
-represent the initial and always blocks, and possibly other causes to
-create threads at startup.
-
- .thread <symbol> [, <flag>]
-
-This statement creates a thread with a starting address at the
-instruction given by <symbol>. When the simulation starts, a thread is
-created for the .thread statement, and it starts at the <symbol>
-addressed instruction.
-
-The <flag> modifies the creation/execution behavior of the
-thread. Supported flags are:
-
- $push -- Cause the thread to be pushed in the scheduler. This
- only effects startup (time 0) by arranging for pushed
- threads to be started before non-pushed threads. This
- is useful for resolving time-0 races.
-
-* Threads in general
-
-Thread statements create the initial threads of a design. These
-include the ``initial'' and ``always'' statements of the original
-Verilog, and possibly some other synthetic threads for various
-purposes. It is also possible to create transient threads from
-behavioral code. These are needed to support such constructs as
-fork/join, named blocks and task activation.
-
-A transient thread is created with a %fork instruction. When a
-transient thread is created this way, the operand to the %fork gives
-the starting address, and the new thread is said to be a child of the
-forking thread. The children of a thread are pushed onto a stack of
-children. A thread can have only one direct child.
-
-A transient thread is reaped with a %join instruction. %join waits for
-the top thread in the stack of children to complete, then
-continues. It is an error to %join when there are no children.
-
-As you can see, the transient thread in VVP is a cross between a
-conventional thread and a function call. In fact, there is no %call
-instruction in vvp, the job is accomplished with %fork/%join in the
-caller and %end in the callee. The %fork, then is simply a
-generalization of a function call, where the caller does not
-necessarily wait for the callee.
-
-For all the behavior of threads and thread parentage to work
-correctly, all %fork statements must have a corresponding %join in the
-parent, and %end in the child. Without this proper matching, the
-hierarchical relationships can get confused. The behavior of erroneous
-code is undefined.
-
-* Thread Context
-
-The context of a thread is all the local data that only that thread
-can address. The local data is broken into two addresses spaces: bit
-memory and word memory.
-
-The bit memory is a region of 4-value bits (0,1,x,z) that can be
-addressed in strips of arbitrary length. For example, an 8-bit value
-can be in locations 8 through and including 15. The bits at address 0,
-1, 2 and 3 are special constant values. Reads from those locations
-make vectors of 0, 1, x or z values, so these can be used to
-manufacture complex values elsewhere.
-
-The word memory is a region of tagged words. The value in each word
-may be native long or real. These words have a distinct address space
-from the bits.
-
-* Threads and scopes
-
-The Verilog ``disable'' statement deserves some special mention
-because of how it interacts with threads. In particular, threads
-throughout the design can affect (end) other threads in the design
-using the disable statement.
-
-In Verilog, the operand to the disable statement is the name of a
-scope. The behavior of the disable is to cause all threads executing
-in the scope to end. Termination of a thread includes all the children
-of the thread. In vvp, all threads are in a scope, so this is how the
-disable gains access to the desired thread.
-
-It is obvious how initial/always thread join a scope. They become part
-of the scope simply by being declared after a .scope declaration. (See
-vvp.txt for .scope declarations.) The .thread statement placed in the
-assembly source after a .scope statement causes the thread to join the
-named scope.
-
-Transient threads join a scope that is the operand to the %fork
-instruction. The scope is referenced by name, and the thread created
-by the fork atomically joins that scope. Once the transient thread
-joins the scope, it stays there until it ends. Threads never change
-scopes, not even transient threads.
-
-TRUTH TABLES
-
-The logic that a functor represents is expressed as a truth table. The
-functor has four inputs and one output. Each input and output has one
-of four possible values (0, 1, x and z) so two bits are needed to
-represent them. So the input of the functor is 8 bits, and the output
-2 bits. A complete lookup table for generating the 2-bit output from
-an 8-bit input is 512 bits. That can be packed into 64 bytes. This is
-small enough that the table should take less space then the code to
-implement the logic.
-
-To implement the truth table, we need to assign 2-bit encodings for
-the 4-value signals. I choose, pseudo-randomly, the following
-encoding:
-
- 1'b0 : 00
- 1'b1 : 01
- 1'bx : 10
- 1'bz : 11
-
-The table is an array of 64 bytes, each byte holding 4 2-bit
-outputs. Construct a 6-bit byte address with inputs 1, 2 and 3 like
-so:
- 332211
-
-The input 0 2-bits can then be used to select which of the 4 2-bit
-pairs in the 8-bit byte are the output:
-
- MSB -> zzxx1100 <- LSB
-
-A complete truth table, then is described as 64 8-bit bytes.
-
-The vvp engine includes truth tables for the primitive gate types, so
-none needs to be given by the programmer. It is sufficient to name the
-type to get that truth table.
-
-
-EXECUTABLE INSTRUCTIONS
-
-Threads run executable code, much like a processor executes machine
-code. VVP has a variety of opcodes for executable instructions. All of
-those instructions start with '%' and go into a single address
-space. Labels attached to executable instructions get assigned the
-address of the instruction, and can be the target of %jmp instructions
-and starting points for threads.
-
-The opcodes.txt file has a more detailed description of all the
-various instructions.
-
-
-THE RELATIONSHIP BETWEEN FUNCTORS, THREADS AND EVENTS
-
-Given the above summary of the major components of vvp, some
-description of their relationship is warranted. Functors provide a
-structural description of the design (so far as it can be described
-structurally) and these functors run independently of the threads. In
-particular, when an input to a functor is set, it calculates a new
-output value; and if that output is different from the existing
-output, a propagation event is created. Functor output is calculated
-by truth table lookup, without the aid of threads.
-
-Propagation events are one of three kinds of events in vvp. They are
-scheduled to execute at some time, and they simply point to the functor
-that is to have its output propagated. When the event expires, the
-output of the referenced functor is propagated to all the inputs that
-it is connected to, and those functors in turn create new events if
-needed.
-
-Assignment events (the second of three types of events) are created
-by non-blocking assignments in behavioral code. When the ``<='' is
-executed (a %assign in vvp) an assign event is created, which includes
-the vvp_ipoint_t pointer to the functor input to receive the value,
-as well as the value. These are distinct from propagation events because:
-
- a) There is no functor that has as its output the value to be
- assigned (this is how values get into the functor net in
- the first place), and
-
- b) This allows for behavioral code to create waveforms of
- arbitrary length that feed into a variable. Verilog allows
- this of non-blocking assignments, but not of gate outputs.
-
-The last type of event is the thread schedule event. This event simply
-points to a thread to be executed. Threads are made up of a virtual
-processor with a program counter and some private storage. Threads
-can execute %assign instructions to create assignment events, and can
-execute %set instructions to do blocking assignments. Threads can also
-use %load to read the output of functors.
-
-The core event scheduler takes these three kinds of events and calls
-the right kind of code to cause things to happen in the design. If the
-event is a propagate or assignment event, the network of functors is
-tickled; if the event is a thread schedule, then a thread is run. The
-implementation of the event queue is not important, but currently is
-implemented as a ``skip list''. That is, it is a sorted singly linked
-list with skip pointers that skip over delta-time events.
-
-The functor net and the threads are distinct. They communicate through
-thread instructions %set, %assign, %waitfor and %load. So far as a thread
-is concerned, the functor net is a blob of structure that it pokes and
-prods via certain functor access instructions.
-
-
-VVP COMPILATION AND EXECUTION
-
-The vvp program operates in a few steps:
-
- 1) Initialization
- Data structures are cleared to empty, and tables are
- readied for compilation.
-
- 2) Compilation
- The input file is read and compiled. Symbol tables are
- build up as needed, objects are allocated and linked
- together.
-
- 3) Cleanup
- Symbol tables and other resources used only for
- compilation are released to reduce the memory
- footprint.
-
- 4) Simulation
- Event simulation is run.
-
-
-The initialization step is performed by the compile_init() function in
-compile.cc. This function in turn calls all the *_init() functions in
-other parts of the source that need initialization for compile. All
-the various sub-init functions are called <foo>_init().
-
-Compilation is controlled by the parser, it parse.y. As the parser
-reads and parses input, the compilation proceeds in the rules by
-calling various compile_* functions. All these functions live in the
-compile.cc file. Compilation calls other sections of the code as
-needed.
-
-When the parser completes compilation, compile_cleanup() is called to
-finish the compilation process. Unresolved references are completed,
-then all the symbol tables and other compile-time-only resources are
-released. Once compile_cleanup() returns, there is no more use for the
-parser for the function in compile.cc.
-
-After cleanup, the simulation is started. This is done by executing
-the schedule_simulate() function. This does any final setup and starts
-the simulation running and the event queue running.
-
-
-HOW TO GET FROM THERE TO HERE
-
-The vvp simulation engine is designed to be able to take as input a
-compiled form of Verilog. That implies that there is a compiler that
-compiles Verilog into a form that the vvp engine can read.
-
-
-* Boolean logic gates
-
-Gates like AND, OR and NAND are implemented simply and obviously by
-functor statements. Any logic up to 4 inputs can be implemented with a
-single functor. For example:
-
- and gate (out, i1, i2, i3);
-
-becomes:
-
- gate .functor and, i1, i2, i3;
-
-Notice the first parameter of the .functor is the type. The type
-includes a truth table that describes the output with a given
-input. If the gate is wider then four inputs, then cascade
-functors. For example:
-
- and gate (out, i1, i2, i3, i4, i5, i6, i7, i8);
-
-becomes:
-
- gate.0 .functor and, i1, i2, i3, i4;
- gate.1 .functor and, i5, i6, i7, i8;
- gate .functor and, gate.0, gate.1;
-
-
-* reg and other variables
-
-Reg and integer are cases of what Verilog calls ``variables.''
-Variables are, simply put, things that behavioral code can assign
-to. These are not the same as ``nets,'' which include wires and the
-like.
-
-Each bit of a variable is created by a ``.var'' statement. For example:
-
- reg a;
-
-becomes:
-
- a .var "a", 0, 0;
-
-
-* named events
-
-Events in general are implemented as functors, but named events in
-particular have no inputs and only the event output. The way to
-generate code for these is like so:
-
- a .event "name";
-
-This creates a functor and makes it into a mode-2 functor. Then the
-trigger statement, "-> a", cause a ``%set a, 0;'' statement be
-generated. This is sufficient to trigger the event.
-
-/*
- * Copyright (c) 2001 Stephen Williams (steve@xxxxxxxxxx)
- *
- * This source code is free software; you can redistribute it
- * and/or modify it in source code form under the terms of the GNU
- * General Public License as published by the Free Software
- * Foundation; either version 2 of the License, or (at your option)
- * any later version.
- *
- * This program is distributed in the hope that it will be useful,
- * but WITHOUT ANY WARRANTY; without even the implied warranty of
- * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
- * GNU General Public License for more details.
- *
- * You should have received a copy of the GNU General Public License
- * along with this program; if not, write to the Free Software
- * Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA
- */</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_icarus_xilinx_hints.html b/docs/wiki/geda_icarus_xilinx_hints.html
deleted file mode 100644
index d7d0ce5..0000000
--- a/docs/wiki/geda_icarus_xilinx_hints.html
+++ /dev/null
@@ -1,130 +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>geda:icarus_xilinx_hints</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="keywords" content="geda,icarus_xilinx_hints" />
-<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/geda:icarus_xilinx_hints?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:icarus_xilinx_hints"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:icarus_xilinx_hints"; />
-<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">
-
-
-
-<h1><a name="xilinx_hints" id="xilinx_hints">Xilinx Hints</a></h1>
-<div class="level1">
-<pre class="code">For those of you who wish to use Icarus Verilog, in combination with
-the Xilinx back end (Foundation or Alliance), it can be done. I have
-run some admittedly simple (2300 equivalent gates) designs through this
-setup, targeting a Spartan XCS10.
-
-Verilog:
-
- Older versions of Icarus Verilog (like 19990814) couldn't synthesize
- logic buried in procedural (flip-flop) assignment. Newer versions
- (like 20000120) don't have this limitation.
-
- Procedural assignments have to be given one at a time, to be
- "found" by xnfsyn. Say
- always @ (posedge Clk) Y = newY;
- always @ (posedge Clk) Z = newZ;
- rather than
- always @ (posedge Clk) begin
- Y = newY;
- Z = newZ;
- end
-
- Steve's xnf.txt covers most buffer and pin constructs, but I had reason
- to use a global clock net not connected to an input pin. The standard
- Verilog for a buffer, combined with a declaration to turn that into a
- BUFG, is:
- buf BUFG( your_output_here, your_input_here );
- $attribute(BUFG,"XNF-LCA","BUFG:O,I")
-
- I use post-processing on my .xnf files to add "FAST" attributes to
- output pins.
-
-Running ivl:
-
- The -F switches are important. The following order seems to robustly
- generate valid XNF files, and is used by "verilog -X":
- -Fsynth -Fnodangle -Fxnfio
-
-Generating .pcf files:
-
- The ngdbuild step seems to lose pin placement information that ivl
- puts in the XNF file. Use xnf2pcf to extract this information to
- a .pcf file, which the Xilinx place-and-route software _will_ pay
- attention to. Steve says he now makes that information available
- in an NCF file, with -fncf=<path>, but I haven't tested that.
-
-Running the Xilinx back end:
-
- You can presumably use the GUI, but that doesn't fit in Makefiles :-).
- Here is the command sequence in pseudo-shell-script:
- ngdbuild -p $part $1.xnf $1.ngd
- map -p $part -o map.ncd $1.ngd
- xnf2pcf <$1.xnf >$1.pcf # see above
- par -w -ol 2 -d 0 map.ncd $1.ncd $1.pcf
- bitgen_flags = -g ConfigRate:SLOW -g TdoPin:PULLNONE -g DonePin:PULLUP \
- -g CRC:enable -g StartUpClk:CCLK -g SyncToDone:no \
- -g DoneActive:C1 -g OutputsActive:C3 -g GSRInactive:C4 \
- -g ReadClk:CCLK -g ReadCapture:enable -g ReadAbort:disable
- bitgen $1.ncd -l -w $bitgen_flags
-
- The Xilinx software has diarrhea of the temp files (14, not including
- .xnf, .pcf, .ngd, .ncd, and .bit), so this sequence is best done in a
- dedicated directory. Note in particular that map.ncd is a generic name.
-
- I had reason to run this remotely (and transparently within a Makefile)
- via ssh. I use the gmake rule
-%.bit : %.xnf
- ssh -x -a -o 'BatchMode yes' ${ALLIANCE_HOST} \
- remote_alliance ${REMOTE_DIR} $(basename $@) 2>&1 < $<
- scp ${ALLIANCE_HOST}:${REMOTE_DIR}/$@ .
- and the remote_alliance script (on ${ALLIANCE_HOST})
-/bin/csh
-cd $1
-cat >! $2.xnf
-xnf2pcf <$2.xnf >! $2.pcf
-./backend $2
-
- There is now a "Xilinx on Linux HOWTO" at
- http://www.polybus.com/xilinx_on_linux.html
- I haven't tried this yet, it looks interesting.
-
-Downloading:
-
- I use the XESS (http://www.xess.com/) XSP-10 development board, which
- uses the PC parallel (printer) port for downloading and interaction
- with the host. They made an old version of their download program
- public domain, posted it at
- http://www.xess.com/FPGA/xstools.zip ,
- and now there is a Linux port at
- ftp://ftp.microux.com/pub/pilotscope/xstools.tar.gz .
-
-The above hints are based on my experience with Foundation 1.5 on NT
-(gack) and Alliance 2.1i on Solaris. Your mileage may vary. Good luck!
-
- - Larry Doolittle <LRDoolittle@xxxxxxx> August 19, 1999
- updated February 1, 2000
-</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_icarus_xnf.html b/docs/wiki/geda_icarus_xnf.html
deleted file mode 100644
index 6b2ca09..0000000
--- a/docs/wiki/geda_icarus_xnf.html
+++ /dev/null
@@ -1,330 +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>geda:icarus_xnf</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="keywords" content="geda,icarus_xnf" />
-<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/geda:icarus_xnf?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:icarus_xnf"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:icarus_xnf"; />
-<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">
-
-
-
-<h1><a name="xilinx_netlist_format" id="xilinx_netlist_format">Xilinx Netlist Format</a></h1>
-<div class="level1">
-<pre class="code">WHAT IS XNF
-
-XNF is the Xilinx Netlist Format. This is somewhat specific to the
-Xilinx tool chain, but it is sufficiently ubiquitous that it's still
-worth it. This format can be fed to place and route tools and
-simulators. Since some third party simulators accept XNF, the format
-may be useful even independent of Xilinx parts.
-
-Icarus Verilog supports XNF as specified by the Xilinx Netlist Format
-Specification, Version 6.1.
-
-GENERATE XNF OUTPUT -- THE SHORT STORY
-
-The easiest way to compile for XNF output is with the "verilog"
-command (man verilog) and the -X switch:
-
- % iverilog -fpart=4010e -fncf=prog.ncf -txnf prog.v
-
-This generates from the prog.v Verilog source file the prog.xnf output
-and the prog.ncf netlist constraints file. The verilog program
-arranges to call the preprocessor and the ivl compiler with all the
-correct switches for generating XNF.
-
-GENERATING XNF MACROS
-
-Icarus Verilog can be used to generate XNF implementations of devices
-that are written in Verilog and used by schematic editors such as
-OrCAD. The trick here is that the code generator automatically notices
-ports to the root module and generates the PIN= attributes needed so
-that external tools can link to the generated XNF.
-
-Icarus Verilog chooses a name for the pin. The name it chooses is the
-port name of the module. If the port is a vector, a pin is generated
-for all the bits of the vector with the bit number appended. For
-example:
-
- module foo(in);
- input [3:0] in;
-
-causes the single bit ports ``in0'' through ``in3'' be
-generated. Internally, the XNF file uses the bussed names instead of
-the pin name.
-
-The implication of this is that there is a chance of name collision
-with the generated XNF macro if the port names are chosen badly. It is
-best to not end a port name with decimal digits, as that can cause
-trouble at link time. Also, XNF is not case sensitive and that should
-be accounted for as well.
-
-XNF PADS IN VERILOG SOURCE
-
-You can assign wires to pads using the Icarus Verilog $attribute
-extension. Attach to a scalar signal (wire or register) the PAD
-attribute with the value that specifies the direction and pin
-number. For example:
-
- wire foo, bar, bid;
- $attribute(foo, "PAD", "i1"); // Input pad on pin 1
- $attribute(bar, "PAD", "o2"); // Output pad on pin 2
- $attribute(bid, "PAD", "b3"); // Bi-directional pad on pin 3
-
-The XNFIO function uses these attributes to locate signals that are
-connected to pads, and generates XNF I/O block devices to connect to
-the pad to do the FPGA pin buffering that is needed. So the Verilog
-programmer need not in general specify the IBUF/OBUF buffers.
-
-If the programmer does connect buffers to pads, the compiler will
-notice them and convert them to I/OBUFs automatically. For example:
-
- buf b1 (sig, foo);
-
-connects to pad foo, so will be converted into an XNF IBUF
-device. Also:
-
- bufif1 bt (bar, value, en);
-
-connects to pad bar so will automatically be converted into an OBUFT
-device. Icarus Verilog understands OBUF, IBUF and OBUFT (with optionally
-inverted enable) devices and will convert Verilog devices from the
-source, or generate missing devices.
-
-In addition, the Verilog programmer may explicitly declare a device as
-an I/OBUF by attaching an attribute to the device, like so:
-
- buf b1 (sig, foo);
- $attribute(b1, "XNF-LCA", "OBUF:O,I");
-
-This latter feature is not entirely recommended as it expects that the
-programmer really knows how the pins of the XNF device are to be
-connected. It also bypasses the efforts of the compiler, so is not
-checked for correctness.
-
-XNF STORAGE ELEMENTS
-
-Storage elements in XNF include flip-flops, latches and CLB
-rams. These devices are generated from the LPM equivalents that the
--Fsynth functor synthesizes from behavioral descriptions.
-
-Flip-flops, or more specifically DFF devices, are generated to
-implement behavioral code like this:
-
- reg Q;
- always @(posedge clk) Q <= <expr>;
-
-The edge can be positive or negative, and the expression can be any
-synthesizable expression. Furthermore, the register "Q" can have
-width, which will cause the appropriate number of flip-flops to be
-created. A clock enable expression can also be added like so:
-
- reg Q;
- always @(posedge clk) if (<ce>) Q <= <expr>;
-
-The <ce> expression can be any synthesizable expression.
-
-With or without the CE, the generated DFF devices are written into the
-XNF output one bit at a time, with the clock input inverted if necessary.
-
-Xilinx parts also support CLB circuitry as synchronous RAMS. These
-devices are created from Verilog memories if the properties are
-right. The behavioral description that the -Fsynth functor matches to
-get a synchronous RAM looks very similar to that for a DFF:
-
- reg [15:0] M;
- always @(posedge clk) if (<we>) M[<addr>] <= <expr>;
-
-Note that in this case the l-value of the assignment is an addressed
-memory. This statement models writes into the memory. Reads from the
-device can be modeled with ordinary structural code, i.e.:
-
- assign foo <= M[<addr>];
-
-For the memory to be synthesizable in the XNF target, the address
-lines for writes and reads must be connected. This corresponds to the
-limitations of the real hardware.
-
-OTHER XNF SPECIAL DEVICES
-
-There are certain special devices in XNF that Verilog does not
-naturally represent, although there are similar more generic Verilog
-devices. The most obvious and useful example is the clock driver,
-otherwise known as the global buffer BUFG. As with pads, Icarus
-Verilog uses the $attribute extension to allow you to specify special
-devices.
-
-The $attribute statement can be applied to devices much the same way
-one applies them to wires. For example, to turn a buffer into a clock
-buffer:
-
- wire iclk, clk;
- buf BUFG (clk, iclk);
- $attribute(iclk, "PAD", "i1");
- $attribute(BUFG, "XNF-LCA", "BUFG:O,I");
-
-The above statements cause the buffer BUFG to be emitted in the XNF
-output as a BUFG device with the first signal called "O" and the
-second called "I". The rest of this example connects the input of the
-BUFG to a signal from the input pin #1 and connects the output to the
-internal wire "clk". Incidentally, this example will cause an IBUF to
-be generated to connect the iclk signal to input pin #1.
-
-SUMMARY OF IVL SUPPORT FOR XNF
-
-Icarus Verilog has a code generator and synthesis functions that
-support generation of XNF netlists. The XNF modules also allow the
-programmer to use $attributes to control certain aspects of code
-generation.
-
-XNF code generation is enabled with the ``-t xnf'' flag on the command
-line. The code generator needs to know the type of part to generate
-code for, so the ``-fpart=<type>'' flag is also needed. For example,
-to generate code for the 4010E the command line might start out as:
-
- ivl -txnf -fpart=4010e -Fsynth -Fnodangle -Fxnfio [...]
-
-Icarus Verilog includes the functions ``synth'' and ``xnfio'' to
-perform transformations and optimizations on the design before code is
-generated. The ``synth'' function matches certain behavioral constructs
-to structural components, and the xnfio function generates pads and
-fills the IOBs.
-
-SUPPORTED FLAGS
-
- -fpart=<part>
- Specify the type of part to target. This string is written
- literally into the PART, record of the XNF, and may also be
- used to control synthesis and placement.
-
- -fncf=<path>
- Cause the code generator to write into <path> the netlist
- constraints needed for controlling placement and timing. This
- switch is required if pin assignments are assigned in the
- Verilog source.
-
-THE SYNTH FUNCTION
-
-This function does synthesis transformations on the entered design,
-making it possible to generate XNF netlist components from certain
-behavioral constructs. This is needed in Verilog for example to model
-some of the synchronous components of the XNF library.
-
-It is a bit much to expect a Verilog compiler in general to generate
-components from arbitrary behavioral descriptions, so the synth
-function works by matching statements that have some documented
-structure, and substituting them for the equivalent XNF component. A
-fully synthesize-able design, then, is one where the behavioral
-statements can all be matched and substituted by the synth function.
-
-THE XNFIO FUNCTION
-
-The "xnfio" function transforms the netlist where the IOBs are
-concerned. The signals with PAD attributes are checked, and
-surrounding circuitry generated to conform to the logic available in
-the IOB.
-
-If the pad is an OPAD, the function will look for an existing buf or
-not gate connected to the PAD signal. If the gate is appropriately
-connected, the buf or not gate will be turned into an OBUF. This pulls
-the buf or inverter into the IOB, freeing a CLB and providing the
-required pin circuitry.
-
-If the pad is an IPAD, the function will look for a buf, and convert
-that to an IBUF. Since Xilinx IOBs cannot invert the output from an
-IBUF, NOT gates cannot be absorbed as in the OPAD case.
-
-
-/*
- * Copyright (c) 1998-1999 Stephen Williams (steve@xxxxxxxxxx)
- *
- * This source code is free software; you can redistribute it
- * and/or modify it in source code form under the terms of the GNU
- * General Public License as published by the Free Software
- * Foundation; either version 2 of the License, or (at your option)
- * any later version.
- *
- * This program is distributed in the hope that it will be useful,
- * but WITHOUT ANY WARRANTY; without even the implied warranty of
- * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
- * GNU General Public License for more details.
- *
- * You should have received a copy of the GNU General Public License
- * along with this program; if not, write to the Free Software
- * Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA
- */
-
-
- $Log: xnf.txt,v $
- Revision 1.16 2003/07/15 03:49:22 steve
- Spelling fixes.
-
- Revision 1.15 2003/01/30 16:23:08 steve
- Spelling fixes.
-
- Revision 1.14 2000/08/01 21:32:40 steve
- Use the iverilog command in documentation.
-
- Revision 1.13 2000/08/01 02:48:42 steve
- Support <= in synthesis of DFF and ram devices.
-
- Revision 1.12 2000/07/25 22:49:32 steve
- memory is not a data type in verilog.
-
- Revision 1.11 2000/04/23 23:03:13 steve
- automatically generate macro interface code.
-
- Revision 1.10 1999/12/05 19:30:43 steve
- Generate XNF RAMS from synthesized memories.
-
- Revision 1.9 1999/11/18 03:52:20 steve
- Turn NetTmp objects into normal local NetNet objects,
- and add the nodangle functor to clean up the local
- symbols generated by elaboration and other steps.
-
- Revision 1.8 1999/11/06 04:51:42 steve
- Support writing some XNF things into an NCF file.
-
- Revision 1.7 1999/11/03 05:18:18 steve
- XNF synthesis now uses the synth functor.
-
- Revision 1.6 1999/11/02 01:43:55 steve
- Fix iobuf and iobufif handling.
-
- Revision 1.5 1999/10/09 17:52:27 steve
- support XNF OBUFT devices.
-
- Revision 1.4 1999/08/14 22:48:21 steve
- Mention the sigfold function.
-
- Revision 1.3 1999/07/22 02:05:20 steve
- is_constant method for PEConcat.
-
- Revision 1.2 1999/07/18 21:17:51 steve
- Add support for CE input to XNF DFF, and do
- complete cleanup of replaced design nodes.
-
- Revision 1.1 1999/05/01 02:57:11 steve
- XNF target documentation.</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_igarus_fpga_lcg.html b/docs/wiki/geda_igarus_fpga_lcg.html
deleted file mode 100644
index 20af6ee..0000000
--- a/docs/wiki/geda_igarus_fpga_lcg.html
+++ /dev/null
@@ -1,261 +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>geda:igarus_fpga_lcg</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="geda,igarus_fpga_lcg" />
-<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/geda:igarus_fpga_lcg?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:igarus_fpga_lcg"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:igarus_fpga_lcg"; />
-<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">
-
-
-
-<h1><a name="fpga_loadable_code_generator_for_icarus_verilog" id="fpga_loadable_code_generator_for_icarus_verilog">FPGA Loadable Code Generator for Icarus Verilog</a></h1>
-<div class="level1">
-<pre class="code">FPGA LOADABLE CODE GENERATOR FOR Icarus Verilog
-
- Copyright 2001 Stephen Williams
- $Id: fpga.txt,v 1.12 2005/09/19 21:45:36 steve Exp $
-
-The FPGA code generator supports a variety of FPGA devices, writing
-XNF or EDIF depending on the target. You can select the architecture
-of the device, and the detailed part name. The architecture is used to
-select library primitives, and the detailed part name is written into
-the generated file for the use of downstream tools.
-
-INVOKING THE FPGA TARGET
-
-The code generator is invoked with the -tfpga flag to iverilog. It
-understands the part= and the arch= parameters, which can be set with
-the -p flag of iverilog:
-
- iverilog -parch=virtex -ppart=v50-pq240-6 -tfpga foo.vl
-
-This example selects the Virtex architecture, and give the detailed
-part number as v50-pq240-6. The output is written into a.out unless a
-different output file is specified with the -o flag.
-
-The following is a list of architecture types that this code generator
-supports.
-
-* arch=lpm
-
-This is a device independent format, where the gates are device types
-as defined by the LPM 2 1 0 specification. Some backend tools may take
-this format, or users may write interface libraries to connect these
-netlists to the device in question.
-
-* arch=generic-edif (obsolete)
-
-This is generic EDIF code. It doesn't necessarily work because the
-external library is not available to the code generator. But, what it
-does is generate generic style gates that a portability library can
-map to target gates if desired.
-
-* arch=generic-xnf (obsolete)
-
-If this is selected, then the output is formatted as an XNF file,
-suitable for most any type of device. The devices that it emits
-are generic devices from the unified library. Some devices are macros,
-you may need to further resolve the generated XNF to get working
-code for your part.
-
-* arch=virtex
-
-If this is selected, then the output is formatted as an EDIF 200 file,
-suitable for Virtex class devices. This is supposed to know that you
-are targeting a Virtex part, so can generate primitives instead of
-using external macros. It includes the VIRTEX internal library, and
-should work properly for any Virtex part.
-
-* arch=virtex2
-
-If this is selected, then the output is EDIF 2 0 0 suitable for
-Virtex-II and Virtex-II Pro devices. It uses the VIRTEX2 library, but
-is very similar to the Virtex target.
-
-XNF ROOT PORTS
-
- NOTE: As parts are moved over to EDIF format, XNF support will be
- phased out. Current Xilinx implementation tools will accept EDIF
- format files even for the older parts, and non-Xilinx implementation
- tools accept nothing else.
-
-When the output format is XNF, the code generator will generate "SIG"
-records for the signals that are ports of the root module. The name is
-declared as an external pin that this macro makes available.
-
-The name given to the macro pin is generated from the base name of the
-signal. If the signal is one bit wide, then the pin name is exactly
-the module port name. If the port is a vector, then the pin number is
-given as a vector. For example, the module:
-
- module main(out, in);
- output out;
- input [2:0] in;
- [...]
- endmodule
-
-leads to these SIG, records:
-
- SIG, main/out, PIN=out
- SIG, main/in<2>, PIN=in2
- SIG, main/in<1>, PIN=in1
- SIG, main/in<0>, PIN=in0
-
-
-EDIF ROOT PORTS
-
-The EDIF format is more explicit about the interface into an EDIF
-file. The code generator uses that control to generate an explicit
-interface definition into the design. (This is *not* the same as the
-PADS of a part.) The generated EDIF interface section contains port
-definitions, including the proper direction marks.
-
-With the (rename ...) s-exp in EDIF, it is possible to assign
-arbitrary text to port names. The EDIF code generator therefore does
-not resort to the mangling that is needed for the XNF target. The base
-name of the signal that is an input or output is used as the name of
-the port, complete with the proper case.
-
-However, since the ports are single bit ports, the name of vectors
-includes the string "[0]" where the number is the bit number. For
-example, the module:
-
-
- module main(out, in);
- output out;
- input [2:0] in;
- [...]
- endmodule
-
-creates these ports:
-
- out OUTPUT
- in[0] INPUT
- in[1] INPUT
- in[2] INPUT
-
-Target tools, including Xilinx Foundation tools, understand the []
-characters in the name and recollect the signals into a proper bus
-when presenting the vector to the user.
-
-
-PADS AND PIN ASSIGNMENT
-
-The ports of a root module may be assigned to specific pins, or to a
-generic pad. If a signal (that is a port) has a PAD attribute, then
-the value of that attribute is a list of locations, one for each bit
-of the signal, that specifies the pin for each bit of the signal. For
-example:
-
- module main( (* PAD = "P10" *) output out,
- (* PAD = "P20,P21,P22" *) input [2:0] in);
-
- [...]
-
- endmodule
-
-In this example, port ``out'' is assigned to pin 10, and port ``in''
-is assigned to pins 20-22. If the architecture supports it, a pin
-number of 0 means let the back end tools choose a pin. The format of
-the pin number depends on the architecture family being targeted, so
-for example Xilinx family devices take the name that is associated
-with the "LOC" attribute.
-
-NOTE: If a module port is assigned to a pin (and therefore attached to
-a PAD) then it is *not* connected to a port of the EDIF file. This is
-because the PAD (and possibly IBUF or OBUF) would become an extra
-driver to the port. An error.
-
-
-SPECIAL DEVICES
-
-The code generator supports the "cellref" attribute attached to logic
-devices to cause specific device types be generated, instead of the
-usual device that the code generator might generate. For example, to
-get a clock buffer out of a Verilog buf:
-
- buf my_gbuf(out, in);
- $attribute(my_buf, "cellref", "GBUF:O,I");
-
-The "cellref" attribute tells the code generator to use the given
-cell. The syntax of the value is:
-
- <cell type>:<pin name>,...
-
-The cell type is the name of the library part to use. The pin names
-are the names of the type in the library, in the order that the logic
-device pins are connected.
-
-
-COMPILING WITH XILINX FOUNDATION
-
-Compile a single-file design with command line tools like so:
-
- % iverilog -parch=virtex -o foo.edf foo.vl
- % edif2ngd foo.edf foo.ngo
- % ngdbuild -p v50-pq240 foo.ngo foo.ngd
- % map -o map.ncd foo.ngd
- % par -w map.ncd foo.ncd
-
----
-$Log: fpga.txt,v $
-Revision 1.12 2005/09/19 21:45:36 steve
- Spelling patches from Larry.
-
-Revision 1.11 2003/08/07 05:17:34 steve
- Add arch=lpm to the documentation.
-
-Revision 1.10 2003/07/04 03:57:19 steve
- Allow attributes on Verilog 2001 port declarations.
-
-Revision 1.9 2003/07/04 01:08:03 steve
- PAD attribute can be used to assign pins.
-
-Revision 1.8 2003/07/02 00:26:49 steve
- Fix spelling of part= flag.
-
-Revision 1.7 2003/03/24 02:28:38 steve
- Document the virtex2 architecture.
-
-Revision 1.6 2003/03/24 00:47:54 steve
- Add new virtex2 architecture family, and
- also the new edif.h EDIF management functions.
-
-Revision 1.5 2002/04/30 04:26:42 steve
- Spelling errors.
-
-Revision 1.4 2001/09/16 22:26:47 steve
- Support the cellref attribute.
-
-Revision 1.3 2001/09/16 01:48:16 steve
- Suppor the PAD attribute on signals.
-
-Revision 1.2 2001/09/06 04:28:40 steve
- Separate the virtex and generic-edif code generators.
-
-Revision 1.1 2001/09/02 23:58:49 steve
- Add documentation for the code generator.
-
-</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_installation.html b/docs/wiki/geda_installation.html
deleted file mode 100644
index 60533e5..0000000
--- a/docs/wiki/geda_installation.html
+++ /dev/null
@@ -1,156 +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>geda:installation</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2008-03-27T04:41:59-0400" />
-<meta name="keywords" content="geda,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/"; />
-<link rel="contents" href="http://geda.seul.org/wiki/geda:installation?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:installation"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:installation"; />
-<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="#installation_help" class="toc">Installation help</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#debian_distributions" class="toc">Debian distributions</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#fedora_and_redhat_distributions" class="toc">Fedora and RedHat distributions</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#suse_and_opensuse_distributions" class="toc">SuSE and OpenSuSE distributions</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#mac_osx_distributions" class="toc">Mac OSX distributions</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#geda_tools_suite_cd-rom" class="toc">"gEDA Tools Suite" CD-ROM</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#cvs_gitunstable_testing" class="toc">CVS / git: Unstable/Testing</a></span></div></li></ul>
-</li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="installation_help" id="installation_help">Installation help</a></h1>
-<div class="level1">
-
-<p>
-This section provides some information useful to people who want to install gEDA onto their computers.
-</p>
-
-</div>
-<!-- SECTION "Installation help" [1-136] -->
-<h2><a name="debian_distributions" id="debian_distributions">Debian distributions</a></h2>
-<div class="level2">
-
-<p>
-The repository of the Debian distribution contains <a href="http://packages.debian.org/cgi-bin/search_packages.pl?keywords=geda&searchon=names&subword=1&version=all&release=all"; class="urlextern" title="http://packages.debian.org/cgi-bin/search_packages.pl?keywords=geda&searchon=names&subword=1&version=all&release=all"; rel="nofollow">binary packages</a> of the core geda/gaf tools including <a href="http://packages.debian.org/cgi-bin/search_packages.pl?keywords=gschem&searchon=names&subword=1&version=all&release=all"; class="urlextern" title="http://packages.debian.org/cgi-bin/search_packages.pl?keywords=gschem&searchon=names&subword=1&version=all&release=all"; rel="nofollow">gschem</a>, <a href="http://packages.debian.org/cgi-bin/search_packages.pl?keywords=pcb&searchon=names&subword=1&version=all&release=all"; class="urlextern" title="http://packages.debian.org/cgi-bin/search_packages.pl?keywords=pcb&searchon=names&subword=1&version=all&release=all"; rel="nofollow">pcb</a>, <a href="http://packages.debian.org/cgi-bin/search_packages.pl?keywords=gnucap&searchon=names&subword=1&version=all&release=all"; class="urlextern" title="http://packages.debian.org/cgi-bin/search_packages.pl?keywords=gnucap&searchon=names&subword=1&version=all&release=all"; rel="nofollow">gnucap</a> and <a href="http://packages.debian.org/cgi-bin/search_packages.pl?keywords=gerbv&searchon=names&subword=1&version=all&release=all"; class="urlextern" title="http://packages.debian.org/cgi-bin/search_packages.pl?keywords=gerbv&searchon=names&subword=1&version=all&release=all"; rel="nofollow">gerbv</a>. Due to license specifics some tools like ngspice cannot be distributed by Debian. However, the geda suite iso image will work nicely on Debian, if you have have prepared your box by installing some development packages. For more detailed information, see the <a href="geda_debian.html" class="wikilink1" title="geda:debian">debian installation notes</a>.
-</p>
-
-</div>
-<!-- SECTION "Debian distributions" [137-1217] -->
-<h2><a name="fedora_and_redhat_distributions" id="fedora_and_redhat_distributions">Fedora and RedHat distributions</a></h2>
-<div class="level2">
-
-<p>
-For RedHat distributions you may wish to download the <a href="http://www.sp5pbe.waw.pl/~sp5smk/software.html"; class="urlextern" title="http://www.sp5pbe.waw.pl/~sp5smk/software.html"; rel="nofollow"> RPM binaries</a> prepared by Wojciech Kazubski.
-</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>.
-</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>.
-</p>
-
-</div>
-<!-- SECTION "Fedora and RedHat distributions" [1218-1660] -->
-<h2><a name="suse_and_opensuse_distributions" id="suse_and_opensuse_distributions">SuSE and OpenSuSE distributions</a></h2>
-<div class="level2">
-
-<p>
-For SuSE and OpenSuSE distributions there are rpm packages for several gEDA related programms. Theyâ??ve been prepared by Werner Hoch using the OpenSuSE Build Service.
-</p>
-
-<p>
-You can install the rpm packages with YaST, yum or any other installation tool. The packages are located in a yum repository at <a href="http://download.opensuse.org/repositories/science/"; class="urlextern" title="http://download.opensuse.org/repositories/science/"; rel="nofollow">OpenSuSE</a> or <a href="ftp://ftp-1.gwdg.de/pub/opensuse/repositories/science/"; class="urlextern" title="ftp://ftp-1.gwdg.de/pub/opensuse/repositories/science/"; rel="nofollow">OpenSuSE mirror</a>.
-</p>
-
-<p>
-For more informations read the <a href="geda_suse_rpm_installation.html" class="wikilink1" title="geda:suse_rpm_installation"> SuSE rpm installation notes</a>.
-</p>
-
-</div>
-<!-- SECTION "SuSE and OpenSuSE distributions" [1661-2241] -->
-<h2><a name="mac_osx_distributions" id="mac_osx_distributions">Mac OSX distributions</a></h2>
-<div class="level2">
-
-<p>
-For Mac OSX 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 Fink binaries</a> prepared by Charles Lepple.
-</p>
-
-</div>
-<!-- SECTION "Mac OSX distributions" [2242-2423] -->
-<h2><a name="geda_tools_suite_cd-rom" id="geda_tools_suite_cd-rom">"gEDA Tools Suite" CD-ROM</a></h2>
-<div class="level2">
-
-<p>
-If there are no current packages for your distribution available, the recommended method is installation from the â??gEDA Tools Suiteâ?? CD-ROM, prepared by Stuart Brorson. The latest version of this CD-ROM is available on-line for free download as an <acronym title="International Organization for Standardization">ISO</acronym> image from the <a href="http://www.geda.seul.org/download.html"; class="urlextern" title="http://www.geda.seul.org/download.html"; rel="nofollow">gEDA Downloads</a> web-page.
-</p>
-
-<p>
-Burn this <acronym title="International Organization for Standardization">ISO</acronym> image to a CD-ROM using your favorite CD burning software. Insert the CD-ROM, and if your computer supports autodetection of the CD-ROM, the built-in installation wizzard will launch.
-</p>
-
-<p>
-For more informations read the <a href="geda_gedasuite_installation.html" class="wikilink1" title="geda:gedasuite_installation"> gEDA Tools Suite installation notes</a>
-</p>
-
-</div>
-<!-- SECTION "gEDA Tools Suite CD-ROM" [2424-3102] -->
-<h2><a name="cvs_gitunstable_testing" id="cvs_gitunstable_testing">CVS / git: Unstable/Testing</a></h2>
-<div class="level2">
-
-<p>
-For those already familiar with the gEDA/gaf applications and those who need the latest stuff, access to source-code repository is available (this has changed from <acronym title="Concurrent Versions System">CVS</acronym> to a <a href="http://git.or.cz/"; class="urlextern" title="http://git.or.cz/"; rel="nofollow">git</a> repository). This is the latest developer source-code version of the application.<br/>
- Installation from the Unstable/Testing repository is appropriate for those:
-</p>
-<ul>
-<li class="level1"><div class="li"> Seeking a solution to a specific problem that was submitted to the development team, e.g., to test the â??fixâ?? so that the developers can be informed that the â??fixâ?? works.</div>
-</li>
-<li class="level1"><div class="li"> With significant working knowledge of the gEDA Tools and quite some knowledge in using and installing from <acronym title="Concurrent Versions System">CVS</acronym>.</div>
-</li>
-</ul>
-
-<p>
- This usually requires access to several existing designs known to work in the current stable release of the gEDA Tools, so that comparisons can be made and issues brought to the attention of the developer/user community (via the e-mail lists or the bug tracker). You must build and install the packages in the following order:
-</p>
-<pre class="code"> 1. libgeda
- 2. symbols
- 3. gschem
- 4. gnetlist
- 5. gsymcheck
- 6. gattrib
- 7. utils
- 8. docs
- 9. examples</pre>
-
-<p>
- The repository can be found <a href="http://geda.seul.org/developer.html"; class="urlextern" title="http://geda.seul.org/developer.html"; rel="nofollow">here</a>.
-</p>
-
-</div>
-<!-- SECTION "CVS / git: Unstable/Testing" [3103-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/geda_installed_plugins.html b/docs/wiki/geda_installed_plugins.html
deleted file mode 100644
index ae82ef7..0000000
--- a/docs/wiki/geda_installed_plugins.html
+++ /dev/null
@@ -1,107 +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>geda:installed_plugins</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="keywords" content="geda,installed_plugins" />
-<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/geda:installed_plugins?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:installed_plugins"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:installed_plugins"; />
-<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="#installed_plugins" class="toc">Installed plugins</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#hilited" class="toc">hilited</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#xterm" class="toc">xterm</a></span></div></li></ul>
-</li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="installed_plugins" id="installed_plugins">Installed plugins</a></h1>
-<div class="level1">
-
-<p>
-The following plugins have been installed, to give the gEDA Project Wiki additional functionality.
-</p>
-
-</div>
-<!-- SECTION "Installed plugins" [1-132] -->
-<h2><a name="hilited" id="hilited">hilited</a></h2>
-<div class="level2">
-
-<p>
-The â??hilitedâ?? plugin acts as a yellow highlighter. Surround the text you want to highlight with double-exclamation marks.
-</p>
-
-<p>
-Example:<br/>
-
-</p>
-<pre class="code">Sample text !!highlighted!! in a paragraph.</pre>
-
-<p>
-becomes:<br/>
- Sample text <span class="hilited">highlighted</span> in a paragraph.
-</p>
-
-</div>
-<!-- SECTION "hilited" [133-400] -->
-<h2><a name="xterm" id="xterm">xterm</a></h2>
-<div class="level2">
-
-<p>
-The â??xtermâ?? plugin allows you to embed preformatted text.<br/>
- The <code><</code>xterm<code>><</code>/xterm<code>></code> tags surround the text you wish to embed.<br/>
- The <code><</code>xterm<code>><</code>/xterm<code>></code> tags differ from the built-in <code><</code>code<code>><</code>/code<code>></code> tags as follows:
-</p>
-<ul>
-<li class="level1"><div class="li"> The text is indented.</div>
-</li>
-<li class="level1"><div class="li"> You can emphasize parts of the text.</div>
-</li>
-<li class="level1"><div class="li"> The text will have a lightgreen background, so it will stand out on the wiki-page.</div>
-</li>
-</ul>
-
-<p>
- Example:<br/>
- The following is indented from the current sectionâ??s left margin: <pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">embedded <strong>preformatted</strong> words</font></pre>
-</p>
-
-<p>
-The following shows how the preformatted text will follow the <acronym title="Extensible HyperText Markup Language">XHTML</acronym> indent levels:
-</p>
-<ul>
-<li class="level1"><div class="li"> Test line 1.</div>
-</li>
-<li class="level1"><div class="li"> Test line 2.<br/>
- <pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">Indented test line 3.</font></pre></div>
-</li>
-<li class="level1"><div class="li"> Test line 4.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "xterm" [401-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/geda_kig_howto.html b/docs/wiki/geda_kig_howto.html
deleted file mode 100644
index 0d998b2..0000000
--- a/docs/wiki/geda_kig_howto.html
+++ /dev/null
@@ -1,330 +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>geda:kig_howto</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="keywords" content="geda,kig_howto" />
-<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/geda:kig_howto?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:kig_howto"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:kig_howto"; />
-<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="#how_to_setup_keymapping_in_gschem" class="toc">How To Setup Keymapping In gschem</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#about_this_document" class="toc">About this document</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#functionality" class="toc">Functionality</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#keymaps" class="toc">Keymaps</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#an_example_on_keymaps" class="toc">An example on keymaps</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#description_of_keys" class="toc">Description of keys</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#actions" class="toc">Actions</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#function_calls" class="toc">Function calls</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#another_keymap" class="toc">Another keymap</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#where_are_the_key_mappings_stored" class="toc">Where are the key mappings stored</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#appendix_a_--_dictionary" class="toc">Appendix A -- Dictionary</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#appendix_b_--_built-in_actions_in_gschem" class="toc">Appendix B -- Built-in actions in gschem</a></span></div></li></ul>
-</li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="how_to_setup_keymapping_in_gschem" id="how_to_setup_keymapping_in_gschem">How To Setup Keymapping In gschem</a></h1>
-<div class="level1">
-
-<p>
-by: Stefan Petersen, spe@xxxxxxxxxxxxx This document is released under <a href="http://www.fsf.org/copyleft/gpl.html"; class="urlextern" title="http://www.fsf.org/copyleft/gpl.html"; rel="nofollow">GPL</a>
-</p>
-
-<p>
-1999-07-24
-</p>
-
-</div>
-<!-- SECTION "How To Setup Keymapping In gschem" [1-177] -->
-<h2><a name="about_this_document" id="about_this_document">About this document</a></h2>
-<div class="level2">
-
-<p>
-The purpose of this document is to try to explain how key mapping works in gEDA/gschem schematic entry program. It uses the langauge Scheme a lot, which is a Lisp-dialect and is used in gschem as a scripting language. If youâ??re not familiar with this language, please see the dictionary (see appendix A, page X, for a short description of common data structures used in Scheme.
-</p>
-
-</div>
-<!-- SECTION "About this document" [178-588] -->
-<h2><a name="functionality" id="functionality">Functionality</a></h2>
-<div class="level2">
-
-<p>
-When you press a button in gschem, a Scheme function is called. This function (press-key) accepts one argument, the name of the pressed key. Then there are Scheme routines to evaluate which key you pressed and call the appropriate action.<br/>
- Since the evaluation routines are written in Scheme itâ??s simple to change the behaviour of what happens when you presses a key. You can implement macros or do several things at each key press. For example, the â??repeat-last-keyâ?? command is implemented completly in Scheme.
-</p>
-
-</div>
-<!-- SECTION "Functionality" [589-1128] -->
-<h2><a name="keymaps" id="keymaps">Keymaps</a></h2>
-<div class="level2">
-
-<p>
-The current implementation is built-up around â??keymapsâ??. A keymap is a list with pairs. Each pairs first element (the car-element) is which key to react on, and the second element (cdr) is a â??what-to-do-nextâ??. This can either be an action, a function to call or another keymap.
-</p>
-
-</div>
-<!-- SECTION "Keymaps" [1129-1427] -->
-<h3><a name="an_example_on_keymaps" id="an_example_on_keymaps">An example on keymaps</a></h3>
-<div class="level3">
-
-<p>
-Two simple examples of keymaps are seen in Figure 1 and Figure 2.
-</p>
-<pre class="code">(define global-keymap
- '(("Escape" . cancel)
- ("a" . add-keymap)))</pre>
-
-<p>
-Figure 1: First example of an simple keymap
-</p>
-
-<p>
-In figure 1 is the keymap called global-keymap. This keymap is the first keymap used. If you for example press the â??aâ??-key, global-keymap tells us that next key pressed will be interpreted by add-keymap (see figure 2).
-</p>
-<pre class="code">(define add-keymap
- '(("c" . add-component)
- ("a" . add-attribute)
- ("n" . add-net-hotkey)))</pre>
-
-<p>
-Figure 2: Second example of an simple keymap
-</p>
-
-<p>
-If you, after you pressed â??aâ??, press a â??câ?? the built-in action add-component comes to live. This is exactly what had happend if you had selected Add, Component…in the menubar.<br/>
- When an action has been performed the current keymap is reset back to global-keymap.<br/>
- Available built-in actions are listed in appendix B.
-</p>
-
-</div>
-<!-- SECTION "An example on keymaps" [1428-2357] -->
-<h3><a name="description_of_keys" id="description_of_keys">Description of keys</a></h3>
-<div class="level3">
-
-<p>
-The key are described as:
-</p>
-<table class="inline">
- <tr>
- <td> For a </td><td> â??aâ?? </td>
- </tr>
- <tr>
- <td class="leftalign"> For Shift-A </td><td> â??Shift Aâ?? </td>
- </tr>
- <tr>
- <td> For Control-a </td><td> â??Control aâ?? </td>
- </tr>
- <tr>
- <td> For Alt-a </td><td> â??Alt aâ?? </td>
- </tr>
-</table>
-
-<p>
- There are a few simple rules to follow when keys for a new keymap is defined:
-</p>
-<ul>
-<li class="level1"><div class="li"> Everything is case sensitive</div>
-</li>
-<li class="level1"><div class="li"> At this point in time you can only have one modifier (shift, control, alt) at a time.</div>
-</li>
-<li class="level1"><div class="li"> Keys must be unique in each keymap, especially the global one</div>
-</li>
-<li class="level1"><div class="li"> Strings (without any modifers) are the same strings specified for the keys in the file /usr/lib/X11/XKeysymDB (at least on a linux box) </div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Description of keys" [2358-2925] -->
-<h3><a name="actions" id="actions">Actions</a></h3>
-<div class="level3">
-
-<p>
-The built-in actions that can be called are listed in Appendix B.<br/>
- Sometimes you may notice that there are similar actions, like edit-rotate-90 and edit-rotate-90-hotkey. They do the same thing, just that the -hotkey actions is run immediately, while the other wait for you to select something.
-</p>
-
-</div>
-<!-- SECTION "Actions" [2926-3240] -->
-<h3><a name="function_calls" id="function_calls">Function calls</a></h3>
-<div class="level3">
-
-<p>
-If the cdr-element is an ordinary Scheme function that function is called. The function canâ??t receive any arguments.<br/>
- This can be used if you want to do complex tasks, like several actions in a row or do some calculation. You can do rather advanced actions since the Guile dialect of Scheme used in gschem is extended from plain Scheme. For further information on Guile, please see the Guile documentation.
-</p>
-
-</div>
-<!-- SECTION "Function calls" [3241-3674] -->
-<h3><a name="another_keymap" id="another_keymap">Another keymap</a></h3>
-<div class="level3">
-
-<p>
-If the cdr-element is another keymap then that command is a multi-key command, ie you need to press at least two keys to cause an action. The first key is desribed in the first keymap, which points to the next keymap. The second keymap describes what should happen when the second key is pressed.
-</p>
-
-</div>
-<!-- SECTION "Another keymap" [3675-3997] -->
-<h2><a name="where_are_the_key_mappings_stored" id="where_are_the_key_mappings_stored">Where are the key mappings stored</a></h2>
-<div class="level2">
-
-<p>
-The keymap is stored in the startup file for gschem, namely <code><startpath, typically /usr/local>/share/gEDA/system-gschemrc</code>.<br/>
- You can then redefine or add keymaps as you like (I think) in your local setup file for gschem, ~/.gEDA/gschemrc
-</p>
-
-<p>
-The Scheme functions used to resolve keypresses to actions are stored at <code><startpath, typically /usr/local>/share/gEDA/scheme/gschem.scm</code>. This is configurable in the gschemrc files.
-</p>
-
-</div>
-<!-- SECTION "Where are the key mappings stored" [3998-4471] -->
-<h3><a name="appendix_a_--_dictionary" id="appendix_a_--_dictionary">Appendix A -- Dictionary</a></h3>
-<div class="level3">
-<table class="inline">
- <tr>
- <td> <strong>function</strong> </td><td>A subprogram in Scheme, C or other programming languages. </td>
- </tr>
- <tr>
- <td><strong>action</strong> </td><td>What gschem (in this case) does when you press a key or a set of keys. </td>
- </tr>
- <tr>
- <td><strong>list</strong> </td><td>A data structure very common in Lisp-looking languages like Scheme. Simply put, a long list of values. </td>
- </tr>
- <tr>
- <td><strong>pair</strong> </td><td>(also dotted pair) A datstructure also very common in Lisp-looking languages. </td>
- </tr>
- <tr>
- <td><strong>car element</strong> </td><td>First element in a pair. Since lists are decendents from pairs, car is also the first element in a list. </td>
- </tr>
- <tr>
- <td><strong>cdr element</strong> </td><td>(pronounced cudr) The second element in a pair. In the list case it denotes the rest of list. </td>
- </tr>
-</table>
-
-</div>
-<!-- SECTION "Appendix A -- Dictionary" [4472-5116] -->
-<h2><a name="appendix_b_--_built-in_actions_in_gschem" id="appendix_b_--_built-in_actions_in_gschem">Appendix B -- Built-in actions in gschem</a></h2>
-<div class="level2">
-
-<p>
-Run: <pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">grep gh_register_procedure_0_0 gschem/src/g_register.c</font></pre>
-</p>
-
-<p>
-and do some work in emacsen.
-</p>
-
-<p>
-<pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">file-new-window
-file-new
-file-open
-file-script
-file-save
-file-save-as
-file-save-all
-file-print
-file-image
-file-close-window
-file-quit
-edit-select
-edit-copy
-edit-copy-hotkey
-edit-move
-edit-move-hotkey
-edit-delete
-edit-rotate-90
-edit-rotate-90-hotkey
-edit-mirror
-edit-mirror-hotkey
-edit-slot
-edit-color
-edit-edit
-edit-lock
-edit-unlock
-edit-translate
-edit-embed
-edit-unembed
-edit-hidden
-view-redraw
-view-zoom-full
-view-zoom-limits
-view-zoom-in
-view-zoom-out
-view-zoom-box
-view-zoom-box-hotkey
-view-pan
-view-pan-hotkey
-view-update-nets
-page-manager
-page-next
-page-prev
-page-new
-page-close
-page-discard
-page-print
-add-component
-add-attribute
-add-net
-add-net-hotkey
-add-text
-add-line
-add-line-hotkey
-add-box
-add-box-hotkey
-add-circle
-add-circle-hotkey
-add-arc
-add-arc-hotkey
-add-pin
-add-pin-hotkey
-hierarchy-open-symbol
-attributes-attach
-attributes-detach
-attributes-show-name
-attributes-show-value
-attributes-show-both
-attributes-visibility-toggle
-options-text-size
-options-snap-size
-options-action-feedback
-options-grid
-options-snap
-options-show-log-window
-options-show-coord-window
-misc-misc
-cancel</font></pre>
-</p>
-
-</div>
-<!-- SECTION "Appendix B -- Built-in actions in gschem" [5117-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/geda_master_attributes_list.html b/docs/wiki/geda_master_attributes_list.html
deleted file mode 100644
index 02fe8c4..0000000
--- a/docs/wiki/geda_master_attributes_list.html
+++ /dev/null
@@ -1,595 +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>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-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/"; />
-<link rel="contents" href="http://geda.seul.org/wiki/geda:master_attributes_list?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:master_attributes_list"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:master_attributes_list"; />
-<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="#geda_gaf_master_attribute_document" class="toc">gEDA/gaf Master Attribute Document</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#overview" class="toc">Overview</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#what_are_attributes" class="toc">What are Attributes?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#symbol_only_attributes" class="toc">Symbol only Attributes</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#device" class="toc">device</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#graphical" class="toc">graphical</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#description" class="toc">description</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#author" class="toc">author</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#comment" class="toc">comment</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#pinseq" class="toc">pinseq</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#pinnumber" class="toc">pinnumber</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#pintype" class="toc">pintype</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#pinlabel" class="toc">pinlabel</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#numslots" class="toc">numslots</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#slotdef" class="toc">slotdef</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#footprint" class="toc">footprint</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#documentation" class="toc">documentation</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#schematic_only_attributes" class="toc">Schematic only Attributes</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#netname" class="toc">netname</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#source" class="toc">source</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#symbol_and_schematic_attributes" class="toc">Symbol and Schematic Attributes</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#refdes" class="toc">refdes</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#slot" class="toc">slot</a></span></div></li>
-<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>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#uref" class="toc">uref</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#name" class="toc">name</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#label" class="toc">label</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#pin" class="toc">pin#</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#slot1" class="toc">slot#</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#type" class="toc">type</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#email" class="toc">email</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#document_revision_history" class="toc">Document Revision History</a></span></div></li></ul>
-</li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="geda_gaf_master_attribute_document" id="geda_gaf_master_attribute_document">gEDA/gaf Master Attribute Document</a></h1>
-<div class="level1">
-
-<p>
-by: Ales Hvezda, ahvezda@xxxxxxxxxxxxx
-</p>
-
-<p>
-This document is released under <a href="http://www.gnu.org/copyleft/fdl.html"; class="urlextern" title="http://www.gnu.org/copyleft/fdl.html"; rel="nofollow">GFDL</a>
-</p>
-
-<p>
-July 10th, 2007
-</p>
-
-</div>
-<!-- SECTION "gEDA/gaf Master Attribute Document" [1-185] -->
-<h2><a name="overview" id="overview">Overview</a></h2>
-<div class="level2">
-
-<p>
-This document describes all the attributes used in in gEDA/gaf (<acronym title="GNU General Public License">GPL</acronym>â??d Electronic Design Automation / Gschem And Friends). This document is broken down into several section: this overview, symbol only attributes, schematic only attributes, attributes which can appear in both symbols and schematics, and attributes which are obsolete or deprecated.<br/>
- In this document, attribute names are in <strong>bold</strong> and examples are in the <code>typewriter</code> font.
-</p>
-
-</div>
-<!-- SECTION "Overview" [186-652] -->
-<h2><a name="what_are_attributes" id="what_are_attributes">What are Attributes?</a></h2>
-<div class="level2">
-
-<p>
-Attributes in the gEDA/gaf system are nothing more than text items which take on the form: <strong>name</strong>=value. Name can be anything just as long as it doesnâ??t contain a equals sign. Value can also be anything just as long as it is something (vs nothing). <strong>name</strong>= (without a value part) is not a valid attribute. Also, there cannot be any spaces immediately before or after the equals sign.<br/>
- Attributes can be attached to some part of the symbol. If the attribute conveys information specific to an object, then the attribute should be attached directly to the object, otherwise the attribute should be free standing or floating. Free standing attributes just exist in the symbol file as text items which take on the form <strong>name</strong>=value.
-</p>
-
-</div>
-<!-- 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" [1424-1459] -->
-<h3><a name="device" id="device">device</a></h3>
-<div class="level3">
-
-<p>
-<strong>device</strong>= is the device name of the symbol and is required by gnetlist.<br/>
- <strong>device</strong>= should be placed somewhere in the symbol and made invisible. This is a free standing or floating attribute. If the object is a graphic then <strong>device</strong>= should be set to none (<strong>device</strong>=none) and attach a <a href="#graphical" title="geda:master_attributes_list ↵" class="wikilink1">graphical</a>= attribute. Do not confuse this attribute with just having a text label which the device name. Do not put spaces into the device name; there are some programs which dislike spaces in the device specifier. Generally the device name is in all caps.<br/>
- Examples: <code>device=7400 device=CONNECTOR 10 device=NPN TRANSISTOR</code>
-</p>
-
-</div>
-<!-- SECTION "device" [1460-2103] -->
-<h3><a name="graphical" id="graphical">graphical</a></h3>
-<div class="level3">
-
-<p>
-Symbols which have no electrical or circuit significance need a <strong>graphical</strong>=1 attribute. Symbols like titleboxes are purely graphical symbols. Any symbol which has <strong>graphical</strong>=1 is ignored by gnetlist.<br/>
- <strong>graphical</strong>=1 should exist somewhere in the symbol and made invisible. This is a free standing or floating attribute. Donâ??t forget to set <a href="#device" title="geda:master_attributes_list ↵" class="wikilink1">device</a>=none.<br/>
- Example: <code>graphical=1</code>
-</p>
-
-</div>
-<!-- SECTION "graphical" [2104-2518] -->
-<h3><a name="description" id="description">description</a></h3>
-<div class="level3">
-
-<p>
-The <strong>description</strong> attribute provides a simple one line description of what the symbol is supposed to represent.<br/>
- Example: <code>description=4 NAND gates with 2 inputs</code>
-</p>
-
-</div>
-<!-- SECTION "description" [2519-2709] -->
-<h3><a name="author" id="author">author</a></h3>
-<div class="level3">
-
-<p>
-The <strong>author</strong> attribute identifies the name of the author of this symbol and their e-mail address. This attribute is optional, but it is nice to know who created which symbols. It also serves the purpose of known who to contact if there are questions about the intent(s) of the symbol. This attribute is free form and it can also include peopleâ??s names who modified the symbol as well as multiple e-mail addresses. It is probably also a good idea to obfuscate the e-mail address so it is not harvested for spam purposes.<br/>
- Example: <code>author=Ales Hvezda ahvezdaATgeda.seul.org</code>
-</p>
-
-</div>
-<!-- SECTION "author" [2710-3306] -->
-<h3><a name="comment" id="comment">comment</a></h3>
-<div class="level3">
-
-<p>
-The <code>comment</code> attribute can contain anything. This attribute can convey any additional information which might not fit into any other attribute. There can be multiple instances of this attribute.<br/>
- Example: <code>comment=This is a comment inside a symbol</code>
-</p>
-
-</div>
-<!-- SECTION "comment" [3307-3580] -->
-<h3><a name="pinseq" id="pinseq">pinseq</a></h3>
-<div class="level3">
-
-<p>
-This attribute is used to give each pin an unique number or sequence. All pins must have a <strong>pinseq</strong>=# attribute attached to the pin object. This attribute should be hidden. This attribute is used extensively by gschem and gnetlist.<br/>
- In some backends (especially the SPICE backend), gnetlist will output pins in the order of increasing pin sequence. The sequence numbers start at 1 and should increase without skipping any numbers. This attribute is not the pin number (i.e. device pin numbers, like GND is 7 on TTL). For pin numbers see the <a href="#pinnumber" title="geda:master_attributes_list ↵" class="wikilink1">pinnumber</a> attribute.<br/>
- Examples: <code>pinseq=1 pinseq=2 pinseq=3</code><br/>
-
-</p>
-
-<p>
-This attribute replaces the obsolete <strong>pin#</strong>=# attribute.
-</p>
-
-</div>
-<!-- SECTION "pinseq" [3581-4273] -->
-<h3><a name="pinnumber" id="pinnumber">pinnumber</a></h3>
-<div class="level3">
-
-<p>
-This attribute is the pin number (i.e. like GND is 7 on 74 TTL). All pins must have a <strong>pinnumber</strong>=# attribute attached to the pin object.<br/>
- You can have numbers or letters for the value. This attribute should be visible with the value only visible. You also need a <a href="#pinseq" title="geda:master_attributes_list ↵" class="wikilink1">pinseq</a> attribute.<br/>
- Examples: <code>pinnumber=1 pinnumber=13 pinnumber=A0</code><br/>
-
-</p>
-
-<p>
-This attribute replaces the obsolete pin#=# attribute.
-</p>
-
-</div>
-<!-- SECTION "pinnumber" [4274-4696] -->
-<h3><a name="pintype" id="pintype">pintype</a></h3>
-<div class="level3">
-
-<p>
-Each pin must have a <strong>pintype</strong>=value attribute attached to it and should be make hidden. Table 1 shows valid values for this attribute.<br/>
- This attribute is not used extensively in the symbol library, but it will be used for DRC and netlisting.<br/>
- Examples: <code>pintype=clk pintype=in pintype=pas</code><br/>
-
-</p>
-<table class="inline">
- <tr>
- <td>in</td><td>Input</td>
- </tr>
- <tr>
- <td>out</td><td>Output</td>
- </tr>
- <tr>
- <td>io</td><td>Input/Output</td>
- </tr>
- <tr>
- <td>oc</td><td>Open collector</td>
- </tr>
- <tr>
- <td>oe</td><td>Open emitter</td>
- </tr>
- <tr>
- <td>pas</td><td>Passive</td>
- </tr>
- <tr>
- <td>tp</td><td>Totem pole</td>
- </tr>
- <tr>
- <td>tri</td><td>Tristate (high impedance)</td>
- </tr>
- <tr>
- <td>clk</td><td>Clock</td>
- </tr>
- <tr>
- <td>pwr</td><td>Power/Ground</td>
- </tr>
- <tr>
- <td colspan="2">Table 1: pintype values</td>
- </tr>
-</table>
-
-</div>
-<!-- SECTION "pintype" [4697-5215] -->
-<h3><a name="pinlabel" id="pinlabel">pinlabel</a></h3>
-<div class="level3">
-
-<p>
-This attribute labels a pin object. This attribute is primarily used by gnetlist to support hierarchical designs.<br/>
- This attribute must be attached to the pin and be left visible. Please make this attribute green (instead of the default attribute yellow).<br/>
- Examples: <code>pinlabel=A0 pinlabel=DATA1 pinlabel=CLK</code><br/>
-
-</p>
-
-</div>
-<!-- SECTION "pinlabel" [5216-5549] -->
-<h3><a name="numslots" id="numslots">numslots</a></h3>
-<div class="level3">
-
-<p>
-If a component has multiple slots in a physical package (such as a 7400 (NAND) which has 4 NANDs per package) then you need a <strong>numslots</strong>=# attribute. The # is the number of slots that are in a physical device. <strong>numslots</strong>=# should exist somewhere in the symbol and be made invisible. This is a free standing or floating attribute. If the symbol does not need slotting, then put <strong>numslots</strong>=0 into the symbol file.<br/>
- Example: <code>numslots=4</code>
-</p>
-
-</div>
-<!-- SECTION "numslots" [5550-6013] -->
-<h3><a name="slotdef" id="slotdef">slotdef</a></h3>
-<div class="level3">
-
-<p>
-If a component has multiple slots in a physical package then you must attach a <strong>slotdef</strong>=slotnumber:#,#,#… for every device inside the physical package.<br/>
- The slotnumber corresponds to the slot number. The colon after the slot number is required. For example, if a device has 4 slots then there would be <strong>slotdef</strong>=1:…, <strong>slotdef</strong>=2:…, <strong>slotdef</strong>=3:…, and slotdef=4:… attributes somewhere in the symbol and be made invisible. This is a free standing or floating attribute.<br/>
- The #â??s have a one-to-one correspondence to the <strong>pinseq</strong> attributes and specify which <strong>pinnumber</strong>=# is used during display (gschem) or netlisting (gnetlist).<br/>
- It is recommended that all symbols which have slots have a <a href="#slot" title="geda:master_attributes_list ↵" class="wikilink1">slot</a>=1 attribute attached in the same fashion as the <a href="#device" title="geda:master_attributes_list ↵" class="wikilink1">device</a>= attribute.<br/>
- See 7400-1.sym as a concrete example.<br/>
- Examples: <code>slotdef=1:1,2,3 slotdef=2:4,5,6 slotdef=3:7,8,9</code><br/>
- This attribute replaces the obsolete <strong>slot</strong>#=# attribute.
-</p>
-
-</div>
-<!-- SECTION "slotdef" [6014-6994] -->
-<h3><a name="footprint" id="footprint">footprint</a></h3>
-<div class="level3">
-
-<p>
-<strong>footprint</strong>=package name should exist somewhere in the symbol and be made invisible. This attribute is used by gnetlist and primarily for the PCB package.<br/>
- Attach this attribute just like the <a href="#device" title="geda:master_attributes_list ↵" class="wikilink1">device</a>= attribute. This is a free standing or floating attribute.<br/>
- package name is the pcb footprint or package type like DIP14 or DIP40. Although this attribute in principle is pcb package dependent, gEDA/gaf conventions exist to make this attribute as portable as possible, allowing for easy collaboration and sharing between users. See the <a href="http://geda.seul.org/wiki/geda:scg#footprint_naming_conventions"; class="wikilink1" title="geda:scg">Footprint naming conventions in the Symbol Creation Guide</a>.<br/>
- If the symbol does not have a footprint, then the value of <strong>footprint</strong>= should be set to none. If the footprint must be overridden in a schematic, then the value of <strong>footprint</strong>= should be set to none. If the footprint is not known, then the value of footprint= should be set to unknown.
-</p>
-
-</div>
-<!-- SECTION "footprint" [6995-7953] -->
-<h3><a name="documentation" id="documentation">documentation</a></h3>
-<div class="level3">
-
-<p>
-<strong>documentation</strong>=documentation_locator may exist somewhere in the symbol and be made invisible. This attribute is used by gschemdoc to find relevant documentation for the symbol, or rather, the device or component associated with the symbol.<br/>
- Attach this attribute just like the <a href="#device" title="geda:master_attributes_list ↵" class="wikilink1">device</a>= attribute. This is a freestanding or floating attribute.<br/>
- documentation_locator is either the base filename of the documentation, or it is the complete Internet <acronym title="Uniform Resource Locator">URL</acronym> (Uniform Resource Locator). If it is the filename, an attempt will be made to search for it in the local gEDA share directory named <strong>documentation</strong>.<br/>
- Filename example: <code>documentation=sn74ls00.pdf</code><br/>
- <acronym title="Uniform Resource Locator">URL</acronym> example: <code>documentation=<a href="http://www-s.ti.com/sc/ds/sn74ls00.pdf"; class="urlextern" title="http://www-s.ti.com/sc/ds/sn74ls00.pdf"; rel="nofollow">http://www-s.ti.com/sc/ds/sn74ls00.pdf</a></code>
-</p>
-
-</div>
-<!-- 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" [8713-8750] -->
-<h3><a name="netname" id="netname">netname</a></h3>
-<div class="level3">
-
-<p>
-This attribute should be attached to a net object to give it a name. Multiple net names for connected net segments is discouraged. All nets which have the same value are considered electrically connected. This attribute is not valid inside symbols (as you cannot have nets inside of symbols).<br/>
- Examples: <code>netname=DATA0 H netname=CLK L</code><br/>
-
-</p>
-
-</div>
-<!-- SECTION "netname" [8751-9110] -->
-<h3><a name="source" id="source">source</a></h3>
-<div class="level3">
-
-<p>
-The source= attribute is used to specify that a symbol has underlying schematics. This attribute is attached directly to a component.<br/>
- This attribute should only be attached to instantiated components in schematics. Attach the attribute to a component and specify the filename (not the path) of the underlying schematic (like block.sch) for the value. The specified schematic must be in a source-library path. This attribute can be attached multiple times with difierent values which basically means that there are multiple underlying schematics.<br/>
- Examples: <code>source=underlying.sch source=memory.sch</code>
-</p>
-
-</div>
-<!-- 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" [9733-9777] -->
-<h3><a name="refdes" id="refdes">refdes</a></h3>
-<div class="level3">
-
-<p>
-This attribute is used to specify the reference designator to a particular instantiated component. It must be on ALL components which have some sort of electrical significance. This attribute can also be on the inside of a symbol (it will be promoted, i.e. attached to the outside of the symbol, if it is visible) to provide a default refdes value (such as U?). Usually this attribute is composed by a prefix (â??Uâ?? for example) and a number (different for each component).<br/>
- Examples: <code>refdes=U1 refdes=R10 refdes=CONN1</code><br/>
- There is a convention of the reference designator used for each kind of component. Here are some of them (substitute a cardinal value for <n>):
-</p>
-<table class="inline">
- <tr>
- <th> Prefix </th><th> Component type</th>
- </tr>
- <tr>
- <td class="leftalign"> R<n> </td><td>Resistor</td>
- </tr>
- <tr>
- <td class="leftalign"> RN<n> </td><td>Resistor Network</td>
- </tr>
- <tr>
- <td class="leftalign"> FB<n> </td><td>Ferrite Bead</td>
- </tr>
- <tr>
- <td class="leftalign"> L<n> </td><td>Inductor</td>
- </tr>
- <tr>
- <td class="leftalign"> C<n> </td><td>Capacitor</td>
- </tr>
- <tr>
- <td class="leftalign"> B<n> </td><td>Battery </td>
- </tr>
- <tr>
- <td class="leftalign"> F<n> </td><td class="leftalign">Fuse </td>
- </tr>
- <tr>
- <td class="leftalign"> J<n> </td><td>Connector</td>
- </tr>
- <tr>
- <td class="leftalign"> P<n> </td><td>Connector (usually plugs that mate with J<n>)</td>
- </tr>
- <tr>
- <td class="leftalign"> K<n> </td><td>Relay</td>
- </tr>
- <tr>
- <td class="leftalign"> S<n> </td><td>Switch</td>
- </tr>
- <tr>
- <td class="leftalign"> T<n> </td><td>Transformer</td>
- </tr>
- <tr>
- <td class="leftalign"> TP<n> </td><td>Testpoint</td>
- </tr>
- <tr>
- <td class="leftalign"> M<n> </td><td>Motor</td>
- </tr>
- <tr>
- <td class="leftalign"> D<n> </td><td>Diode</td>
- </tr>
- <tr>
- <td class="leftalign"> Q<n> </td><td>Transistor</td>
- </tr>
- <tr>
- <td class="leftalign"> U<n> </td><td>IC</td>
- </tr>
- <tr>
- <td class="leftalign"> X<n> </td><td>Crystal</td>
- </tr>
-</table>
-
-</div>
-<!-- SECTION "refdes" [9778-10889] -->
-<h3><a name="slot" id="slot">slot</a></h3>
-<div class="level3">
-
-<p>
-This attribute is used to specify a slot for a slotted component. It should be attached to an instantiated component. This attribute can also be on the inside of a symbol (it will be promoted, i.e. attached to the outside of the symbol, if it is visible) to provide a default slot.
-</p>
-
-</div>
-<!-- SECTION "slot" [10890-11187] -->
-<h3><a name="net" id="net">net</a></h3>
-<div class="level3">
-
-<p>
-The <strong>net</strong>= attribute is used to create power/ground and arbitrary nets. Please see the <a href="http://geda.seul.org/wiki/geda:na_howto"; class="wikilink1" title="geda:na_howto">net= attribute mini-HOWTO</a> for more info. When this attribute is inside a symbol, it is used to create nets. When this attribute is attached to an instantiated component (in a schematic), then the <strong>net</strong>= can also be used to create new nets and can used to override existing nets.
-</p>
-
-</div>
-<!-- SECTION "net" [11188-11591] -->
-<h3><a name="value" id="value">value</a></h3>
-<div class="level3">
-
-<p>
-Used mainly in the spice backend netlister to specify the value of the various elements. No translation is done on this, and it is placed as is into the netlist.<br/>
- Examples: <code>value=1K value=10V</code><br/>
-
-</p>
-
-</div>
-<!-- SECTION "value" [11592-11807] -->
-<h3><a name="symversion" id="symversion">symversion</a></h3>
-<div class="level3">
-
-<p>
-The <strong>symversion</strong>= attribute is used to version the contents of symbols. Normally this attribute is not present, but once a symbol has been accepted into the main gEDA symbol library and there are changes to it, this attribute must be placed into the symbol file and properly incremented. The value of this attribute takes the following form:<br/>
- <strong>major.minor</strong>
-</p>
-
-<p>
-where major and minor are just plain integers (separated by a period). The major number is incremented when a symbol has some sort of a change which will break or might break an existing schematic. The minor number is only incremented when a cosmetic or very minor change is made to the symbol. The major and minor numbers are not coupled in any way, however, when making major version changes, the minor version number can be reset to zero.<br/>
- If this attribute is inside of a symbol and that symbol is placed onto a schematic, then the <strong>symversion</strong>= attribute will be automatically promoted and attached to the outside of the symbol. During the load of the symbol from disk, the value of the <strong>symversion</strong>= inside the symbol file (if any) and the <strong>symversion</strong>= attached to the symbol (if any) are compared. If the values are the same then the placed symbol matches the disk symbol file, however if the values do not match, then libgeda will output a warning/error message (based on whether it is a major or minor version change).<br/>
- New symbols should not receive this attribute at all. Only when the symbol is change should this attribute be placed into the symbol file and maintained. Users should not attach this attribute manually to instantiated symbols. This attribute should normally be made invisible when placed inside of a symbol file. This attribute is always promoted when it is found inside of a symbol (during component placement).<br/>
- Examples: <code>symversion=1.1</code><br/>
-
-</p>
-
-</div>
-<!-- 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" [14458-14489] -->
-<h3><a name="uref" id="uref">uref</a></h3>
-<div class="level3">
-
-<p>
-The uref= attribute is obsolete and cannot not be used. It was used to provide the same information as <a href="#refdes" title="geda:master_attributes_list ↵" class="wikilink1">refdes</a>.
-</p>
-
-</div>
-<!-- SECTION "uref" [14490-14621] -->
-<h3><a name="name" id="name">name</a></h3>
-<div class="level3">
-
-<p>
-The <strong>name</strong>= attribute should not be attached or appear in any symbol. It is considered ambiguous. <strong>name</strong>= was never used by gEDA/gaf.
-</p>
-
-</div>
-<!-- SECTION "name" [14622-14775] -->
-<h3><a name="label" id="label">label</a></h3>
-<div class="level3">
-
-<p>
-The <strong>label</strong>= attribute is obsolete and cannot be used. It was used to give nets names/labels and to label pins. The replacement attributes for this are <a href="#netname" title="geda:master_attributes_list ↵" class="wikilink1">netname</a> and <a href="#pinlabel" title="geda:master_attributes_list ↵" class="wikilink1">pinlabel</a> respectively.
-</p>
-
-</div>
-<!-- SECTION "label" [14776-14991] -->
-<h3><a name="pin" id="pin">pin#</a></h3>
-<div class="level3">
-
-<p>
-The <strong>pin#</strong>=# attribute is obsolete and cannot be used. It was used to provide sequence and number information to pins. The replacement attributes for this are <a href="#pinseq" title="geda:master_attributes_list ↵" class="wikilink1">pinseq</a> and <a href="#pinnumber" title="geda:master_attributes_list ↵" class="wikilink1">pinnumber</a>.
-</p>
-
-</div>
-<!-- SECTION "pin#" [14992-15200] -->
-<h3><a name="slot1" id="slot1">slot#</a></h3>
-<div class="level3">
-
-<p>
-The <strong>slot#</strong>=# attribute is obsolete and cannot be used. It was used to provide slotting information to components. The replacement attribute for this is <a href="#slotdef" title="geda:master_attributes_list ↵" class="wikilink1">slotdef</a>.
-</p>
-
-</div>
-<!-- SECTION "slot#" [15201-15386] -->
-<h3><a name="type" id="type">type</a></h3>
-<div class="level3">
-
-<p>
-The <strong>type</strong>= attribute is obsolete and cannot be used. It was used to provide type information on pins. The replacement attribute for this is <a href="#pintype" title="geda:master_attributes_list ↵" class="wikilink1">pintype</a>.
-</p>
-
-</div>
-<!-- SECTION "type" [15387-15559] -->
-<h3><a name="email" id="email">email</a></h3>
-<div class="level3">
-
-<p>
-The information in this attribute has been merged with <a href="#author" title="geda:master_attributes_list ↵" class="wikilink1">author</a>.
-</p>
-
-</div>
-<!-- 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">
- <tr>
- <td>July 14th, 2002</td><td>Created attributes.tex from attributes.txt.</td>
- </tr>
- <tr>
- <td>July 14th, 2002</td><td>Updated doc to be in sync with post-20020527.</td>
- </tr>
- <tr>
- <td>August 25th, 2002</td><td>Added obsolete type= attribute.</td>
- </tr>
- <tr>
- <td>September 14, 2002</td><td>Added description= attribute. Minor xes</td>
- </tr>
- <tr>
- <td>October 7, 2002</td><td>Added doc= attribute; Egil Kvaleberg.</td>
- </tr>
- <tr>
- <td>February 11, 2003</td><td>Added reference to footprint conventions.</td>
- </tr>
- <tr>
- <td>February 23, 2003</td><td>Added author=, email=, and comment= attributes.</td>
- </tr>
- <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" [15645-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/geda_mcalc_readme.html b/docs/wiki/geda_mcalc_readme.html
deleted file mode 100644
index 084128f..0000000
--- a/docs/wiki/geda_mcalc_readme.html
+++ /dev/null
@@ -1,63 +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>geda:mcalc_readme</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="geda,mcalc_readme" />
-<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/geda:mcalc_readme?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:mcalc_readme"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:mcalc_readme"; />
-<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">
-
-
-
-<h1><a name="mcalc_readme" id="mcalc_readme">mcalc README</a></h1>
-<div class="level1">
-<pre class="code">$Id: README,v 1.1 2001/08/16 11:19:01 dan Exp $
-
-WHAT IS IT?
-------------
-
-mstrip is a JavaScript based microstrip analysis/synthesis calculator.
-It is designed to be easy to use and fairly accurate. The accuracy is
-generally within a percent or so for the characteristic impedance which
-greatly exceeds the simplified formulations found in most text books.
-
-
-HOW DO I INSTALL IT?
---------------------
-
-To install this package, simply copy all the files in the archive to the
-installation directory.
-
-To use this pacakge, just point your JavaScript capable web broswer at
-the file 'index.html'.
-
-
-CAN I COPY IT?
---------------
-Please refer to the file 'copying.html' for copyright information.
-
-
-IS THERE A HISTORY FILE?
-------------------------
-Please refer to the file 'verinfo.html' for version history.</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_na_howto.html b/docs/wiki/geda_na_howto.html
deleted file mode 100644
index a59dad5..0000000
--- a/docs/wiki/geda_na_howto.html
+++ /dev/null
@@ -1,249 +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>geda:na_howto</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="keywords" content="geda,na_howto" />
-<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/geda:na_howto?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:na_howto"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:na_howto"; />
-<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="#net_attribute_mini-howto" class="toc">net= attribute mini-HOWTO</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#what_is_the_net_attribute_used_for" class="toc">What is the net= attribute used for?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#what_is_the_format_of_the_net_attribute" class="toc">What is the format of the net= attribute?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#how_do_you_actually_use_the_net_attribute" class="toc">How do you actually use the net= attribute?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#caveats_bugs" class="toc">Caveats / Bugs</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#example" class="toc">Example</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#final_notes" class="toc">Final notes</a></span></div></li></ul>
-</li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="net_attribute_mini-howto" id="net_attribute_mini-howto">net= attribute mini-HOWTO</a></h1>
-<div class="level1">
-
-<p>
-by: Ales Hvezda
-</p>
-
-<p>
-This document is released under <a href="http://www.gnu.org/copyleft/fdl.html"; class="urlextern" title="http://www.gnu.org/copyleft/fdl.html"; rel="nofollow">GFDL</a>
-</p>
-
-<p>
-October 2nd, 2003
-</p>
-
-<p>
-The information in this document is current as of 19991011.
-</p>
-
-</div>
-<!-- SECTION "net= attribute mini-HOWTO" [1-216] -->
-<h2><a name="what_is_the_net_attribute_used_for" id="what_is_the_net_attribute_used_for">What is the net= attribute used for?</a></h2>
-<div class="level2">
-
-<p>
-The <strong><code>net=</code></strong> attribute is used to specify power, ground, and/or arbitrary nets in the gEDA system.<br/>
- The <strong><code>net=</code></strong> attribute is used instead some of the other systems of specifying power/ground (such as having power/ground pins on symbols or power boxes). Some devices have lots of power/ground pins and having all of these pins on the symbol would increase its size and make it unmanageable. The <strong><code>net=</code></strong> attribute is the power/ground specification of choice in the gEDA system because of its simplicity and versatility. Now having said all this, you can have power/ground pins on a symbol, but gnetlist will probably not recognize these nets connected to these pins as separate power/ground nets. Please keep this in mind as you draw symbols.
-</p>
-
-</div>
-<!-- SECTION "What is the net= attribute used for?" [217-1022] -->
-<h2><a name="what_is_the_format_of_the_net_attribute" id="what_is_the_format_of_the_net_attribute">What is the format of the net= attribute?</a></h2>
-<div class="level2">
-
-<p>
-Attributes in gEDA are simple text items which are in the form <code>name=value</code>. All proper attributes follow this form. Attribute names are always lower case, but the value can be upper or lower case. gnetlist and friends are case sensitive. Typically net/signal names by default are upper case.<br/>
- Attribute can be attached to an object or in certain cases (like the <strong><code>net=</code></strong> attribute) can be free oating (not attached to anything). The free floating attributes are also called toplevel attributes.<br/>
- The <strong><code>net=</code></strong> attribute is a text item which takes on the following form:
-</p>
-<pre class="code">net=signalname:pinname,pinname,pinname,...</pre>
-
-<p>
-where:
-</p>
-<table class="inline">
- <tr>
- <td> <strong><code>net=</code></strong> </td><td> The attribute name (always the same, lowercase) </td>
- </tr>
- <tr>
- <td> signalname </td><td> The signal or net being defines (like +5V, GND, etc…) </td>
- </tr>
- <tr>
- <td> pinname </td><td> The pin name (or number) which is assigned to this signal/net (or pin names/numbers) </td>
- </tr>
-</table>
-
-<p>
- The signalname cannot contain the ":" character (since it is a delimiter). The pinname is the pin name (A1, P2, D1, etc…) or pin number (1, 2, 5, 13, etc…). The pinname cannot contain the "," character (since it is also a delimiter). pinnames are typically the same sort of numbers/names like the <code>pin#=#</code> attribute (if you are familiar with that attribute).<br/>
- You can only have ONE signalname per <strong><code>net=</code></strong> attribute, but you can have as many pinnames/numbers as you want.
-</p>
-
-</div>
-<!-- SECTION "What is the format of the net= attribute?" [1023-2446] -->
-<h2><a name="how_do_you_actually_use_the_net_attribute" id="how_do_you_actually_use_the_net_attribute">How do you actually use the net= attribute?</a></h2>
-<div class="level2">
-
-<p>
-You can place the <strong><code>net=</code></strong> attribute in several places. Hereâ??s the list so far:
-</p>
-<ul>
-<li class="level1"><div class="li"> Inside a symbol either as an attached attribute or an unattached attribute (toplevel attribute). Example which creates power/gnd nets: <strong><code>net=GND:7</code></strong> or <strong><code>net=+5V:14</code></strong></div>
-</li>
-<li class="level1"><div class="li"> Outside a symbol (which is instantiated on a schematic) attached as an attribute to override an existing <strong><code>net=</code></strong> created net/signal. Suppose a symbol has a <strong><code>net=GND:7</code></strong> inside it already; attaching this to the symbol: <strong><code>net=AGND:7</code></strong> overrides the GND net (on pin 7) calling it AGND and connects/associates it to pin 7.</div>
-</li>
-<li class="level1"><div class="li"> Outside or inside a symbol to connect a net to a visible pin automatically. This is still untested and still might have some undesirable (negative) side effects. Use with caution.</div>
-</li>
-<li class="level1"><div class="li"> Attached to one of those special power/gnd symbol (like vcc/gnd/vdd) and you can change what that symbol represents. You could change the ground symbol to create a net called DIGITAL GND without editing the symbol (<strong><code>net=DIGITAL_GND:1</code></strong>).<br/>
- In the current symbol (19991011) library there are symbols named <strong>vdd-1.sym</strong>, <strong>vcc-1.sym</strong>, <strong>vee-1.sym</strong>, etc… which do not have a <strong><code>net=</code></strong> attribute inside, so you must attach the <strong><code>net=</code></strong> attribute yourself (in the schematic).<br/>
- There also symbols named 5V-minus-1.sym, 12V-plus-1.sym, 9V-plus-1.sym, etc… which have the appropriate <strong><code>net=</code></strong> attribute in them already (can be overridden though). You can use these symbol as examples of how to use the <strong><code>net=</code></strong> attribute.<br/>
-</div>
-</li>
-</ul>
-
-<p>
-You can have as many <strong><code>net=</code></strong> attributes as you want. Just remember that <strong><code>net=</code></strong> attributes attached to the outside of a symbol override any equivalent internal (inside the symbol) <strong><code>net=</code></strong> attributes. If you run into a case where this doesnâ??t work, please let <strong>ahvezdaATgeda.seul.org</strong>. In fact, send any bug reports to that individual.
-</p>
-
-</div>
-<!-- SECTION "How do you actually use the net= attribute?" [2447-4387] -->
-<h2><a name="caveats_bugs" id="caveats_bugs">Caveats / Bugs</a></h2>
-<div class="level2">
-
-<p>
-The <strong><code>net=</code></strong> attribute/mechanism is fairly new, so there are bound to be bugs (many bugs). Here are some of the identified issues:
-</p>
-<ul>
-<li class="level1"><div class="li"> As of 19991011 almost all of the symbols in the standard library do not have the <strong><code>net=</code></strong> attribute or any other power/ground specifiers. Hopefully this will be updated sometime (any volunteers?).</div>
-</li>
-<li class="level1"><div class="li"> Attach a special power symbol (vcc/gnd) to a already named net will alias (rename) that net to the signalname specified in the <strong><code>net=</code></strong> attribute (in/attached to the vcc/gnd symbol). You can override this (so the reverse is true) by playing with the â??net-naming-priorityâ??. Be careful with this. There might be other â??aliasingâ?? issues which have not been identified yet.</div>
-</li>
-<li class="level1"><div class="li"> Creating a <strong><code>net=</code></strong> attribute which associates a signal name with a pin which is already visible on the symbol, is probably a bad idea. This does work, but all the ramifications have not been explored yet.</div>
-</li>
-<li class="level1"><div class="li"> It is probably a bad idea to have the same <strong><code>net=</code></strong> attribute attached several times. Ales has not formalized what happens in this case. Just remember that the <strong><code>net=</code></strong> attribute on the outside of a symbol should override the internal one.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Caveats / Bugs" [4388-5599] -->
-<h2><a name="example" id="example">Example</a></h2>
-<div class="level2">
-
-<p>
-Hereâ??s a schematic which uses standard symbols (note: the 7400 does not have the <strong><code>net=</code></strong> attribute inside yet). This schematic consists of a 7400 with the <strong><code>net=</code></strong> attributes attached for power and ground, One of the input pins grounded using a gnd symbol and the other at a logic one using the vcc symbol (with an attached <strong><code>net=</code></strong> attribute). One of the input net is named, but as you will see, the netname is replaced by the <strong><code>net=</code></strong> signal name (see above for more info on this). The output is pulled up with a pull up resistor which has power specified using the +5V symbol.<br/>
-
-</p>
-<table class="inline">
- <tr>
- <td> <a href="_detail/geda_net.html" class="media" title="geda:net.jpg"><img src="_media/geda_net.jpg" class="media" title="net.jpg" alt="net.jpg" /></a> </td>
- </tr>
-</table>
-<pre class="code">v 19991011
-C 38700 58100 1 0 0 7400-1.sym
-{
-T 39000 59000 5 10 1 1 0
-uref=U100
-T 38900 59500 5 10 1 1 0
-net=GND:7
-T 38900 59300 5 10 1 1 0
-net=+5V:14
-}
-N 38700 58800 37400 58800 4
-{
-T 37600 58900 5 10 1 1 0
-netname=NETLABEL
-}
-N 37400 58800 37400 59200 4
-N 38700 58400 37400 58400 4
-N 37400 58000 37400 58400 4
-C 37300 57700 1 0 0 gnd-1.sym
-C 37200 59200 1 0 0 vcc-1.sym
-{
-T 36800 59200 5 10 1 1 0
-net=+5V:1
-}
-N 40000 58600 41600 58600 4
-{
-T 41200 58700 5 10 1 1 0
-netname=OUTPUT
-}
-C 40700 58800 1 90 0 resistor-1.sym
-{
-T 40800 59200 5 10 1 1 0
-uref=R1
-}
-N 40600 58800 40600 58600 4
-N 40600 59900 40600 59700 4
-C 40400 59900 1 0 0 5V-plus-1.sym</pre>
-
-<p>
-<strong>gnetlist</strong> (using the geda netlist format) run using this sample schematic outputs this:
-</p>
-<pre class="code">START header
-
-gEDA's netlist format
-Created specifically for testing of gnetlist
-
-END header
-
-START components
-
-R1 device=RESISTOR
-U100 device=7400
-
-END components
-
-START renamed-nets
-
-NETLABEL -> +5V
-
-END renamed-nets
-
-START nets
-
-+5V : R1 2, U100 14, U100 1
-GND : U100 7, U100 2
-OUTPUT : R1 1, U100 3
-
-END nets</pre>
-
-<p>
-Notice how NETLABEL was renamed (aliased to the +5V net).
-</p>
-
-</div>
-<!-- SECTION "Example" [5600-7377] -->
-<h2><a name="final_notes" id="final_notes">Final notes</a></h2>
-<div class="level2">
-
-<p>
-Send all bugs to <strong>ahvezdaATgeda.seul.org</strong> or <strong>geda-devATgeda.seul.org</strong> (mailing list, please subscribe first). [Iâ??m sure thereâ??s more to say here]
-</p>
-
-</div>
-<!-- SECTION "Final notes" [7378-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/geda_ngnutmeg_mp.html b/docs/wiki/geda_ngnutmeg_mp.html
deleted file mode 100644
index 293f2ba..0000000
--- a/docs/wiki/geda_ngnutmeg_mp.html
+++ /dev/null
@@ -1,924 +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>geda:ngnutmeg_mp</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="keywords" content="geda,ngnutmeg_mp" />
-<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/geda:ngnutmeg_mp?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:ngnutmeg_mp"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:ngnutmeg_mp"; />
-<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">
-
-
-
-<h1><a name="ngnutmeg_man-page" id="ngnutmeg_man-page">ngnutmeg man-page</a></h1>
-<div class="level1">
-<pre class="code">NUTMEG(1) NUTMEG(1)
-
-
-
-NAME
- nutmeg - spice post-processor
-
-SYNOPSIS
- nutmeg [ - ] [ -n ] [ -t term ] [ datafile ... ]
-
-DESCRIPTION
- Nutmeg is a post processor for SPICE - it takes the raw output file
- created by spice -r and plots the data on a graphics terminal or a
- workstation display. Note that the raw output file is different from
- the data that SPICE writes to the standard output.
-
- Arguments are:
-
- - Don�t try to load the default data file ("rawspice") if no other
- files are given.
-
- -n (or --no-spiceinit)
- Don�t try to source the file ".spiceinit" upon startup. Normally
- nutmeg tries to find the file in the current directory, and if
- it is not found then in the user�s home directory.
-
- -t term (or --term=term)
- The program is being run on a terminal with mfb name term.
-
- -h (or --help)
- Display a verbose help on the arguments available to the pro-
- gram.
-
- -v (or --version)
- Display a version number and copyright information of the pro-
- gram.
-
- Further arguments are taken to be data files in binary or ascii format
- (see sconvert(1)) which are loaded into nutmeg. If the file is in
- binary format, it may be only partially completed (useful for examining
- SPICE ouput before the simulation is finished). One file may contain
- any number of data sets from different analyses.
-
- Nutmeg data is in the form of vectors: time, voltage, etc. Each vector
- has a type, and vectors can be operated on and combined algebraicly in
- ways consistent with their types. Vectors are normally created when a
- data file is read in (see the load command below), and when the initial
- datafile is loaded. They can also be created with the let command.
-
- An expression is an algebraic formula involving vectors and scalars (a
- scalar is a vector of length 1), and the following operations:
-
- +, -, *, %, /, ^, and ,.
-
- % is the modulo operator, and the comma operator has two meanings: if
- it is present in the argument list of a user-definable function, it
- serves to seperate the arguments. Otherwise, the term x , y is synony-
- mous with x + j(y).
-
- Also available are the logical operations & (and), | (or), ! (not), and
- the relational operations <, >, >=, <=, =, and <> (not equal). If used
- in an algebraic expression they work like they would in C, producing
- values of 0 or 1. The relational operators have the following syn-
- onyms: "gt" is >, "lt" is <, "ge" is >=, "le" is <=, "ne" is <>, "eq"
- is =, "and" is &, "or" is |, and "not" is !. These are useful when <
- and > might be confused with IO redirection (which is almost always).
-
- The following functions are available:
-
- mag(vector) - The magnitude of vector.
-
- ph(vector) - The phase of vector.
-
- j(vector) - i (sqrt(-1)) times vector.
-
- real(vector) - The real component of vector.
-
- imag(vector) - The imaginary part of vector.
-
- db(vector) - 20 * log10(mag(vector)).
-
- log(vector) - The logarithm (base 10) of the vector.
-
- ln(vector) - The natural logarithm (base e) of vector.
-
- exp(vector) - e to the vector power.
-
- abs(vector) - The absolute value of vector.
-
- sqrt(vector) - The square root of vector.
-
- sin(vector) - The sin of vector.
-
- cos(vector) - The cosine of vector.
-
- tan(vector) - The tangent of vector.
-
- atan(vector) - The inverse tangent of vector.
-
- norm(vector) - The vector normalized to 1 (i.e, the largest mag-
- nitude of any component will be 1).
-
- rnd(vector) - A vector with each component a random integer
- between 0 and the absolute value of the vectors�s corresponding
- component.
-
- mean(vector) - The result is a scalar (a length 1 vector) that
- is the mean of the elements of vector.
-
- vector(number) - The result is a vector of length number, with
- elements 0, 1, ... number - 1. If number is a vector then just
- the first element is taken, and if it isn�t an integer then the
- floor of the magnitude is used.
-
- length(vector) - The length of vector.
-
- interpolate(plot.vector) - The result of interpolating the named
- vector onto the scale of the current plot. This function uses
- the variable polydegree to determine the degree of interpola-
- tion.
-
- A vector may be either the name of a vector already defined, a float-
- ing- point number (a scalar), or a list like [elt1 elt2 ... eltn],
- which is a vector of length n. A number may be written in any format
- acceptable to SPICE, such as 14.6MEG or -1.231E-4. Note that you can
- either use scientific notation or one of the abbreviations like MEG or
- G, but not both. As with SPICE, a number may have trailing alphabetic
- characters after it.
-
- The notation expr [lower upper], where lower and upper are numbers,
- denotes the range of elements from expr between lower and upper. The
- notation expr [num] denotes the num�th element of expr. If upper is
- lower than lower, the order of the elements in the vector is reversed.
- In all other cases, [ and ] serve to surround literal vectors as
- described above. (You may have to use a lot of parentheses to make
- sure that you get what you want. For instance, you have to type print
- (foo) ([1 2]) to print the two vectors. Otherwise it will be inter-
- preted as a function call or a vector with an index.) Note that the
- expression foo[10 20][5] will not yield the 15th element of foo, but
- rather the 5th. In general only the last index suffix on an expression
- will take effect.
-
- To reference vectors in a plot that is not the current plot (see the
- setplot command, below), the notation plotname.vecname can be used.
-
- Either a plotname or a vector name may be the wildcard all. If the
- plotname is all, matching vectors from all plots are specified, and if
- the vector name is all, all vectors in the specified plots are refer-
- enced. Note that you may not use binary operations on expressions
- involving wildcards - it is not obvious what all + all should denote,
- for instance.
-
- Thus some (contrived) examples of expressions are:
-
- cos(TIME) + db(v(3))
-
- sin(cos(log([1 2 3 4 5 6 7 8 9 10])))
-
- TIME * rnd(v(9)) - 15 * cos(vin#branch) ^ [7.9e5 8]
-
- not ((ac3.FREQ[32] & tran1.TIME[10]) gt 3)
-
- Nutmeg commands are as follows:
-
- plot exprs [ylimit ylo yhi] [xlimit xlo xhi] [xindices xilo xihi]
- [xcompress comp] [xdelta xdel] [ydelta ydel] [xlog] [ylog] [vs xname]
- [xlabel word] [ylabel word] [title word] [samep]
- Plot the given exprs on the screen (if you are on a graphics
- terminal). The xlimit and ylimit arguments determine the high
- and low x- and y-limits of the axes, respectively. The xindices
- arguments determine what range of points are to be plotted -
- everything between the xilo�th point and the xihi�th point is
- plotted. The xcompress argument specifies that only one out of
- every comp points should be plotted. If an xdelta or a ydelta
- parameter is present, it specifies the spacing between grid
- lines on the X- and Y-axis. These parameter names may be abbre-
- viated to xl, yl, xind, xcomp, xdel, and ydel respectively. The
- xname argument is an expression to use as the scale on the x-
- axis. If xlog or ylog are present, the X or Y scale respec-
- tively will be logarithmic. The xlabel and ylabel arguments
- cause the specified labels to be used for the X and Y axes,
- respectively. If samep is given, the values of the other param-
- eters (other than xname) from the previous plot, hardcopy, or
- asciiplot command will be used unless re-defined on the command
- line. Finally, the title argument will be used in the place of
- the plot name at the bottom of the graph.
-
- hardcopy file plotargs
- Just like plot, except creates a file called file containing the
- plot. The file is an image in plot(5) format, and can be
- printed by either the plot(1) program or lpr with the -g flag.
-
- asciiplot plotargs
- Produce a line printer plot of the vectors. The plot is sent to
- the standard output, so you can put it into a file with asci-
- iplot args ... > file. The set options width, height, and
- nobreak determine the width and height of the plot, and whether
- there are page breaks, respectively. Note that you will have
- problems if you try to asciiplot something with an X-scale that
- isn�t monotonic (i.e, something like sin(TIME) ), because asci-
- iplot uses a simple-minded sort of linear interpolation.
-
- define function(arg1, arg2, ...) expression
- Define the user-definable function with the name function and
- arguments arg1, arg2, ... to be expression, which may involve
- the arguments. When the function is later used, the arguments it
- is given are substituted for the formal arguments when it is
- parsed. If expression is not present, any definition for func-
- tion is printed, and if there are no arguments to define then
- all currently active definitions are printed. Note that you may
- have different functions defined with the same name but differ-
- ent arities. Some useful definitions are:
-
- define max(x,y) (x > y) * x + (x <= y) * y
- define min(x,y) (x < y) * x + (x >= y) * y
-
- undefine function ...
- Definitions for the named user-defined functions are deleted.
-
- let name = expr
- Creates a new vector called name with the value specified by
- expr, an expression as described above. If expr is [] (a zero-
- length vector) then the vector becomes undefined. If there are
- no arguments, let is the same as display.
-
- print [col] [line] expr ...
- Prints the vector described by the expression expr. If the col
- argument is present, print the vectors named side by side. If
- line is given, the vectors are printed horizontally. col is the
- default, unless all the vectors named have a length of one, in
- which case line is the default. The options width, length, and
- nobreak are effective for this command (see asciiplot). If the
- expression is all, all of the vectors available are printed.
- Thus print col all > file will print everything in the file in
- SPICE2 format. The scale vector (time, frequency) will always
- be in the first column unless the variable noprintscale is true.
-
- load [filename] ...
- Loads the raw data in either binary or ascii format from the
- files named. The default filename is rawspice, or the argument
- to the -r flag if there was one.
-
- source filename
- Reads commands from the file filename. Lines beginning with the
- character * are considered comments and ignored.
-
- help [all] [command ...]
- Prints help. If the argument all is given, a short description
- of everything you could possibly type is printed. If commands
- are given, descriptions of those commands are printed. Other-
- wise help for only a few major commands is printed.
-
- display [varname ...]
- Prints a summary of currently defined vectors, or of the names
- specified. The vectors are sorted by name unless the variable
- nosort is set. The information given is the name of the vector,
- the length, the type of the vector, and whether it is real or
- complex data. Additionally, one vector will be labeled [scale].
- When a command such as plot is given without a vs argument, this
- scale is used for the X-axis. It is always the first vector in a
- rawfile, or the first vector defined in a new plot. If you unde-
- fine the scale (i.e, let TIME = []), a random remaining vector
- will become the scale.
-
- setplot [plotname]
- Set the current plot to the plot with the given name, or if no
- name is given, prompt the user with a menu. (Note that the
- plots are named as they are loaded, with names like tran1 or
- op2. These names are shown by the setplot and display commands
- and are used by diff, below.) If the "New plot" item is
- selected, the current plot will become one with no vectors
- defined. Note that here the word "plot" refers to a group of
- vectors that are the result of one SPICE run. When more than
- one file is loaded in, or more than one plot is present in one
- file, nutmeg keeps them seperate and only shows you the vectors
- in the current plot.
-
- settype type vector ...
- Change the type of the named vectors to type. Type names can be
- found in the manual page for sconvert.
-
- diff plot1 plot2 [vec ...]
- Compare all the vectors in the specified plots, or only the
- named vectors if any are given. There are different vectors in
- the two plots, or any values in the vectors differ significantly
- the difference is reported. The variables abstol, reltol, and
- vntol are used to determine what "significantly" means (see the
- SPICE3 User�s Manual).
-
- quit Quit nutmeg.
-
- bug Send a bug report. (If you have defined BUGADDR, the mail will
- go there.)
-
- write [file] [exprs]
- Writes out the expr�s to file. First vectors are grouped
- together by plots, and written out as such. (I.e, if the
- expression list contained three vectors from one plot and two
- from another, then two plots will be written, one with three
- vectors and one with two.) Additionally, if the scale for a
- vector isn�t present, it is automatically written out as well.
- The default format is ascii, but this can be changed with the
- set filetype command. The default filename is rawspice, or the
- argument to the -r flag on the command line, if there was one,
- and the default expression list is all.
-
- shell [args ...]
- Fork a shell, or execute the arguments as a command to the
- shell.
-
- alias [word] [text ...]
- Causes word to be aliased to text. History substitutions may be
- used, as in C-shell aliases.
-
- unalias [word ...]
- Removes any aliases present for the words.
-
- history [number]
- Print out the history, or the last number commands typed at the
- keyboard. Note: in version 3a7 and earlier, all commands
- (including ones read from files) were saved.
-
- set [word] [word = value] ...
- Set the value of word to be value, if it is present. You can
- set any word to be any value, numeric or string. If no value is
- given then the value is the boolean �true�. The value of word
- may be inserted into a command by writing $word. If a variable
- is set to a list of values that are enclosed in parentheses
- (which must be seperated from their values by white space), the
- value of the variable is the list. The variables meaningful to
- nutmeg (of which there are too many) are:
-
- abstol
- The absolute tolerance used by the diff command.
-
- appendwrite
- Append to the file when a write command is issued, if
- one already exists.
-
- colorN
- These variables determine the colors used, if X is
- being run on a color display. N may be between 0 and
- 15. Color 0 is the background, color 1 is the grid and
- text color, and colors 2 through 15 are used in order
- for vectors plotted. The value of the color variables
- should be names of colors, which may be found in the
- file /usr/lib/rgb.txt.
-
- combplot
- Plot vectors by drawing a vertical line from each point
- to the X-axis, as opposed to joining the points. Note
- that this option is subsumed in the plottype option,
- below.
-
- cpdebug
- Print cshpar debugging information. (Must be complied
- with the -DCPDEBUG flag.)
-
- debug
- If set then a lot of debugging information is printed.
- (Must be compiled with the -DFTEDEBUG flag.)
-
- device
- The name (/dev/tty??) of the graphics device. If this
- variable isn�t set then the user�s terminal is used. To
- do plotting on another monitor you will probably have
- to set both the device and term variables. (If device
- is set to the name of a file, nutmeg will dump the
- graphics control codes into this file -- this is useful
- for saving plots.)
-
- echo
- Print out each command before it is executed.
-
- filetype
- This can be either ascii or binary, and determines what
- the format of rawfiles will be. The default is ascii.
-
- fourgridsize
- How many points to use for interpolating into when
- doing fourier analysis.
-
- gridsize
- If this variable is set to an integer, this number will
- be used as the number of equally spaced points to use
- for the Y-axis when plotting. Otherwise the current
- scale will be used (which may not have equally spaced
- points). If the current scale isn�t strictly mono-
- tonic, then this option will have no effect.
-
- hcopydev
- If this is set, when the hardcopy command is run the
- resulting file is automatically printed on the printer
- named hcopydev with the command lpr -Phcopydev -g file.
-
- hcopydevtype
- This variable specifies the type of the printer output
- to use in the hardcopy command. If hcopydevtype is not
- set, plot (5) format is assumed. The standard distri-
- bution currently recognizes postscript as an alterna-
- tive output format. When used in conjunction with
- hcopydev, hcopydevtype should specify a format sup-
- ported by the printer.
-
- height
- The length of the page for asciiplot and print col.
-
- history
- The number of events to save in the history list.
-
- nfreqs
- The number of frequencies to compute in the fourier
- command. (Defaults to 10.)
-
- nobreak
- Don�t have asciiplot and print col break between pages.
-
- noasciiplotvalue
- Don�t print the first vector plotted to the left when
- doing an asciiplot.
-
- noclobber
- Don�t overwrite existing files when doing IO redirec-
- tion.
-
- noglob
- Donââ?¬â?¢t expand the global characters ââ?¬Ë?*ââ?¬â?¢, ââ?¬Ë??ââ?¬â?¢, ââ?¬Ë?[ââ?¬â?¢, and
- ââ?¬Ë?]ââ?¬â?¢. This is the default.
-
- nogrid
- Don�t plot a grid when graphing curves (but do label
- the axes).
-
- nomoremode
- If nomoremode is not set, whenever a large amount of
- data is being printed to the screen (e.g, the print or
- asciiplot commands), the output will be stopped every
- screenful and will continue when a carriage return is
- typed. If nomoremode is set then data will scroll off
- the screen without hesitation.
-
- nonomatch
- If noglob is unset and a global expression cannot be
- matched, use the global characters literally instead of
- complaining.
-
- nosort
- Don�t have display sort the variable names.
-
- noprintscale
- Don�t print the scale in the leftmost column when a
- print col command is given.
-
- numdgt
- The number of digits to print when printing tables of
- data (fourier, print col). The default precision is 6
- digits. On the VAX, approximately 16 decimal digits
- are available using double precision, so numdgt should
- not be more than 16. If the number is negative, one
- fewer digit is printed to ensure constant widths in
- tables.
-
- plottype
- This should be one of normal, comb, or point:chars.
- normal, the default, causes points to be plotted as
- parts of connected lines. comb causes a comb plot to
- be done (see the description of the combplot variable
- above). point causes each point to be plotted seper-
- ately - the chars are a list of characters that will be
- used for each vector plotted. If they are omitted then
- a default set is used.
-
- polydegree
- The degree of the polynomial that the plot command
- should fit to the data. If polydegree is N, then nutmeg
- will fit a degree N polynomial to every set of N points
- and draw 10 intermediate points in between each end-
- point. If the points aren�t monotonic, then it will try
- rotating the curve and reducing the degree until a fit
- is achieved.
-
- polysteps
- The number of points to interpolate between every pair
- of points available when doing curve fitting. The
- default is 10. (This should really be done automati-
- cally.)
-
- program
- The name of the current program (argv[0]).
-
- prompt
- The prompt, with the character ââ?¬Ë?!ââ?¬â?¢ replaced by the cur-
- rent event number.
-
- rawfile
- The default name for rawfiles created.
-
- reltol
- The relative tolerance used by the diff command.
-
- rhost
- The machine to use for remote SPICE-3 runs, instead of
- the default one. (See the description of the rspice
- command, below.)
-
- rprogram
- The name of the remote program to use in the rspice
- command.
-
- slowplot
- Stop between each graph plotted and wait for the user
- to type return before continuing.
-
- sourcepath
- A list of the directories to search when a source com-
- mand is given. The default is the current directory
- and the standard spice library (/usr/local/lib/spice,
- or whatever LIBPATH is #defined to in the source.
-
- spicepath
- The program to use for the aspice command. The default
- is /cad/bin/spice.
-
- term
- The mfb name of the current terminal.
-
- units
- If this is degrees, then all the trig functions will
- use degrees instead of radians.
-
- unixcom
- If a command isn�t defined, try to execute it as a UNIX
- command. Setting this option has the effect of giving
- a rehash command, below. This is useful for people who
- want to use nutmeg as a login shell.
-
- verbose
- Be verbose. This is midway between echo and debug /
- cpdebug.
-
- vntol
- The absolute voltage tolerance used by the diff com-
- mand.
-
- width
- The width of the page for asciiplot and print col.
-
- xbrushheight
- The height of the brush to use if X is being run.
-
- xbrushwidth
- The width of the brush to use if X is being run.
-
- xfont
- The name of the X font to use when plotting data and
- entering labels. The plot may not look entirely great
- if this is a variable-width font.
-
-
- unset [word] ...
- Unset the variables word.
-
- shift [varname] [number]
- If varname is the name of a list variable, it is shifted to the
- left by number elements. (I.e, the number leftmost elements are
- removed.) The default varname is argv, and the default number
- is 1.
-
- rusage [resource ...]
- Print resource usage statistics. If any resources are given,
- just print the usage of that resource. Currently valid
- resources are:
-
- elapsed
- The amount of time elapsed since the last rusage elaped
- call.
-
- faults
- Number of page faults and context switches (BSD only).
-
- space
- Data space used.
-
- time
- CPU time used so far.
-
- everything
- All of the above.
-
- cd [directory] Change the current working directory to directory, or
- to the user�s home directory if none is given.
-
- aspice [output-file]
- Start a SPICE-3 run, and when it is finished load the
- data. The raw data is kept in a temporary file. If out-
- put-file is specified then the diagnostic output is
- directed into that file, otherwise it is thrown away.
-
- jobs Report on the asynchronous SPICE-3 jobs currently run-
- ning. Nutmeg checks to see if the jobs are finished
- every time you execute a command. If it is done then
- the data is loaded and becomes available.
-
- rspice [input file]
- Runs a SPICE-3 remotely taking the input file as a
- SPICE-3 input deck, or the current circuit if no argu-
- ment is given. Nutmeg waits for the job to complete,
- and passes output from the remote job to the user�s
- standard output. When the job is finished the data is
- loaded in as with aspice. If the variable rhost is set,
- nutmeg will connect to this host instead of the default
- remote SPICE-3 server machine. Note that this command
- will only work if your system administrator is running
- a SPICE-3 daemon on the remote host. If the variable
- rprogram is set, then rspice will use this as the path-
- name to the program to run.
-
- echo [stuff...] Echos the arguments.
-
- fourier fundamental_frequency [value ...]
- Does a fourier analysis of each of the given values,
- using the first 10 multiples of the fundamental fre-
- quency (or the first nfreqs, if that variable is set -
- see below). The output is like that of the .four card.
- The values may be any valid expression. The values are
- interpolated onto a fixed-space grid with the number of
- points given by the fourgridsize variable, or 200 if it
- is not set. The interpolation will be of degree poly-
- degree if that variable is set, or 1. If polydegree is
- 0, then no interpolation will be done. This is likely
- to give erroneous results if the time scale is not
- monotonic, though.
-
- version [version id]
- Print out the version of nutmeg that is running. If
- there are arguments, it checks to make sure that the
- arguments match the current version of SPICE. (This is
- mainly used as a Command: line in rawfiles.)
-
- rehash Recalculate the internal hash tables used when looking
- up UNIX commands, and make all UNIX commands in the
- user�s PATH available for command completion. This is
- useless unless you have set unixcom first (see above).
-
- The following control structures are available:
-
- while condition
- statement
- ...
- end
-
- While condition, an arbitrary algebraic expression, is true, execute
- the statements.
-
- repeat [number]
- statement
- ...
- end
-
- Execute the statements number times, or forever if no argument is
- given.
-
- dowhile condition
- statement
- ...
- end
-
- The same as while, except that the condition is tested after the
- statements are executed.
-
- foreach var value ...
- statement
- ...
- end
-
- The statements are executed once for each of the values, each time with
- the variable var set to the current one. (var can be accessed by the
- $var notation - see below).
-
- if condition
- statement
- ...
- else
- statement
- ...
- end
-
- If the condition is non-zero then the first set of statements are exe-
- cuted, otherwise the second set. The else and the second set of state-
- ments may be omitted.
-
- label word
-
- If a statement of the form goto word is encountered, control is trans-
- fered to this point, otherwise this is a no-op.
-
- goto word
-
- If a statement of the form label word is present in the block or an
- enclosing block, control is transfered there. Note that if the label
- is at the top level, it must be before the goto statement (i.e, a for-
- ward goto may occur only within a block).
-
- continue
-
- If there is a while, dowhile, or foreach block enclosing this state-
- ment, control passes to the test, or in the case of foreach, the next
- value is taken. Otherwise an error results.
-
- break
-
- If there is a while, dowhile, or foreach block enclosing this state-
- ment, control passes out of the block. Otherwise an error results.
-
- Of course, control structures may be nested. When a block is entered
- and the input is the terminal, the prompt becomes a number of >�s
- equalling the number of blocks the user has entered. The current con-
- trol structures may be examined with the debugging command cdump.
-
- If a word is typed as a command, and there is no built-in command with
- that name, the directories in the sourcepath list are searched in order
- for the file. If it is found, it is read in as a command file (as if
- it were sourced). Before it is read, however, the variables argc and
- argv are set to the number of words following the filename on the com-
- mand line, and a list of those words respectively. After the file is
- finished, these variables are unset. Note that if a command file calls
- another, it must save its argv and argc since they will get altered.
- Also, command files may not be re-entrant since there are no local
- variables. (Of course, the procedures may explicitly manipulate a
- stack...) This way one can write scripts analogous to shell scripts
- for nutmeg and . Note that for the script to work with , it must begin
- with a blank line (or whatever you like, since it will be thrown away)
- and then a line with .control on it. This is an unfortunate result of
- the source command being used for both circuit input and command file
- execution. Note also that this allows the user to merely type the name
- of a circuit file as a command, and it will be automatically run.
-
- There are various command scripts installed in
- /usr/local/lib/spice/scripts (or whatever the path is on your machine),
- and the default sourcepath includes this directory, so you can use
- these command files (almost) like builtin commands.
-
- Nutmeg will use either X or MFB, depending on whether it finds the
- variable DISPLAY in the environment. If you are using X on a worksta-
- tion, it should already be present, but if you want to display graphics
- on a different machine than the one you are running nutmeg on, DISPLAY
- should be of the form machine:0.
-
- If X is being used, the cursor may be positioned at any point on the
- screen when the window is up and characters typed at the keyboard will
- be added to the window at that point. The window may then be sent to a
- printer using the xpr(1) program.
-
- There are a number of pre-defined constants in nutmeg. They are:
- pi pi
- e The base of natural logarithms
- c The speed of light
- i The square root of -1
- kelvin Absolute 0 in Centigrade
- echarge The charge on an electron
- boltz Boltzman�s constant
- planck Planck�s constant (h)
-
-
- These are all in MKS units. If you have another variable with a name
- that conflicts with one of these then it takes precedence.
-
- Nutmeg occasionally checks to see if it is getting close to running out
- of space, and warns the user if this is the case. (This is more likely
- to be useful with the SPICE front end.)
-
- C-shell type quoting with "" and ��, and backquote substitution may be
- used. Within single quotes, no further substitution (like history sub-
- stitution) is done, and within double quotes, the words are kept
- together but further substitution is done. Any text between backquotes
- is replaced by the result of executing the text as a command to the
- shell.
-
- Tenex-style (�set filec� in the 4.3 C-shell) command, filename, and
- keyword completion is possible: If EOF (control-D) is typed after the
- first character on the line, a list of the commands or possible argu-
- ments is printed. (If it is alone on the line it will exit nutmeg.) If
- escape is typed, then nutmeg will try to complete what the user has
- already typed. To get a list of all commands, the user should type
- <space> ^D.
-
- The values of variables may be used in commands by writing $varname
- where the value of the variable is to appear. The special variables $$
- and $< refer to the process ID of the program and a line of input which
- is read from the terminal when the variable is evaluated, respectively.
- If a variable has a name of the form $&word, then word is considered a
- vector (see above), and its value is taken to be the value of the vari-
- able. If $foo is a valid variable, and is of type list, then the
- expression $foo[low-high] represents a range of elements. Either the
- upper index or the lower may be left out, and the reverse of a list may
- be obtained with $foo[len-0]. Also, the notation $?foo evaluates to 1
- if the variable foo is defined, 0 otherwise, and $#foo evaluates to the
- number of elements in foo if it is a list, 1 if it is a number or
- string, and 0 if it is a boolean variable.
-
- History substitutions, similar to C-shell history substitutions, are
- also available - see the C-shell manual page for all of the details.
-
- The characters ~, {, and } have the same effects as they do in the C-
- Shell, i.e., home directory and alternative expansion. It is possible
- to use the wildcard characters *, ?, [, and ] also, but only if you
- unset noglob first. This makes them rather useless for typing algebraic
- expressions, so you should set noglob again after you are done with
- wildcard expansion. Note that the pattern [^abc] will match all charac-
- ters except a, b, and c.
-
- IO redirection is available - the symbols >, >>, >&, >>&, and < have
- the same effects as in the C-shell.
-
- You may type multiple commands on one line, seperated by semicolons.
-
- If you want to use a different mfbcap file than the default (usually
- ~cad/lib/mfbcap), you have to set the environment variable MFBCAP
- before you start nutmeg. The -m option and the mfbcap variable no
- longer work.
-
-VMS NOTES
- Nutmeg can be run under VAX/VMS. Some features like command, etc com-
- pletion, expansion of *, ?, and [], backquote substitution, the shell
- command, and so forth do not work. (In fact command completion only
- works on 4.2 or 4.3 BSD.)
-
- Nutmeg will look for start-up commands in the file spice.rc in the cur-
- rent directory.
-
- The standard suffix for rawspice files in VMS is ".raw".
-
- You will have to respond to the -more- prompt during plot with a car-
- riage return instead of any key as you can do on UNIX.
-
-SEE ALSO
- sconvert(1), spice(1), mfb(3), writedata(3)
-
-AUTHOR
- Wayne Christopher (faustus@xxxxxxxxxxxxxxxx)
-
-BUGS
- The label entry facilities are very primitive - after all, nutmeg isn�t
- a graphics editor (yet). You must be careful to type very slowly when
- entering labels -- nutmeg checks the X event queue once every second,
- and can get very confused if characters arrive faster than that.
-
- If you redefine colors after creating a plot window with X, and then
- cause the window to be redrawn, it will not to the right thing.
-
- When defining aliases like
-
- alias pdb plot db( �!:1� - �!:2� )
-
- you must be careful to quote the argument list substitutions in this
- manner. If you quote the whole argument it might not work properly.
-
- In a user-defined function, the arguments cannot be part of a name that
- uses the plot.vec syntax. I.e,
-
- define poke(duck) cos(tran1.duck)
-
- won�t do the right thing.
-
- If you type plot all all, or otherwise use a wildcard reference for one
- plot twice in a command, bad things will happen.
-
- The asciiplot command doesn�t deal with log scales or the delta key-
- words.
-
- There are probably some features that nutmeg doesn�t have yet.
-
-CAVEATS
- Often the names of terminals recognised by MFB are different from those
- in /etc/termcap. Thus you may have to reset your terminal type with the
- command
-
- set term = termname
-
- where termname is the name in the mfbcap file.
-
- The hardcopy command is useless on VMS and other systems without the
- plot command, unless the user has a program that understands plot(5)
- format.
-
-
-
-
-4th Berkeley Distribution 27 April 1987 NUTMEG(1)
-</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_ngsconvert_mp.html b/docs/wiki/geda_ngsconvert_mp.html
deleted file mode 100644
index 905a30e..0000000
--- a/docs/wiki/geda_ngsconvert_mp.html
+++ /dev/null
@@ -1,151 +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>geda:ngsconvert_mp</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-05-24T22:27:26-0400" />
-<meta name="keywords" content="geda,ngsconvert_mp" />
-<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/geda:ngsconvert_mp?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:ngsconvert_mp"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:ngsconvert_mp"; />
-<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">
-
-
-
-<h1><a name="ngsconvert_man-page" id="ngsconvert_man-page">ngsconvert man-page</a></h1>
-<div class="level1">
-<pre class="code">SCONVERT(1) SCONVERT(1)
-
-
-
-NAME
- sconvert - convert spice formats
-
-SYNOPSIS
- sconvert fromtype fromfile totype tofile
- sconvert fromtype totype
- sconvert
-
-DESCRIPTION
- Sconvert translates spice output files among three formats: the old
- binary format, a new binary format, and a new ascii format. The for-
- mats are specified by the fromtype and totype arguments: ââ?¬Ë?oââ?¬â?¢ for the
- old format, ââ?¬Ë?bââ?¬â?¢ for the new binary format, and ââ?¬Ë?aââ?¬â?¢ for the new ascii
- format. Fromtype specifies the format to be read, and totype specifies
- the format to be written. If fromfile and tofile are given, then they
- are used as the input and output, otherwise standard input and output
- are used. (Note that this second option is only available on UNIX sys-
- tems - on VMS and other systems you must supply the filenames.) If no
- arguments are given, the parameters are prompted for.
-
- Binary format is the preferred format for general use, as it is the
- most economical in terms of space and speed of access, and ascii is
- provided to make it easy to modify data files and transfer them between
- machines with different floating-point formats. The old format is pro-
- vided only for backward compatibility. The three formats are as fol-
- lows:
-
- Old:
-
- What Size in Bytes
-
- title 80
- date 8
- time 8
- numoutputs 2
- the integer 4 2
- variable names --
- char[numoutputs][8] numoutputs * 8
- types of output numoutputs * 2
- node index numoutputs * 2
- plot title numoutputs * 24
- the actual data numpoints * numoutputs * 8
-
- Ascii:
-
- Title: Title Card String
- Date: Date
- [ Plotname: Plot Name
- Flags: complex or real
- No. Variables: numoutputs
- No. Points: numpoints
- Command: nutmeg command
- Variables: 0 varname1 typename1
- 1 varname2 typename2
- etc...
- Values:
- 0 n n n n ...
- 1 n n n n ...
- And so forth...
- ] repeated one or more times
-
-
- If one of the flags is complex, the points look like r,i where r and i
- are floating point (in %e format). Otherwise they are in %e format.
- Only one of real and complex should appear.
-
- The lines are guaranteed to be less than 80 columns wide (unless the
- plot title or variable names are very long), so this format is safe
- to mail between systems like CMS.
-
- Any number of Command: lines may appear between the No. Points:
- and the Variables: lines, and whenever the plot is loaded into
- nutmeg they will be executed.
-
- Binary:
-
- Title Card (a NULL terminated string)
- Date, Time (a NULL terminated string)
- [
- Plot title (a NULL terminated string)
- Number of variables (an int)
- Number of data points (an int)
- flags (a short)
- variable header struct (repeated numoutputs times)
- variable name (a NULL terminated string)
- variable type (an int)
- set of outputs (repeated numpoints times)
- ] repeated one or more times.
-
-
- A set of outputs is a vector of doubles of length numoutputs, or
- a vector of real-imaginary pairs of doubles if the data is complex.
-
-SEE ALSO
- nutmeg(1), spice(1), writedata(3)
-
-AUTHOR
- Wayne Christopher (faustus@xxxxxxxxxxxxxxxx)
-
-BUGS
- If variable names and the title and plotname strings have trailing
- blanks in them they will be stripped off when the file is read, if it
- is in ascii format.
-
- If a plot title begins with "Title:" nutmeg will be fooled into think-
- ing that this is an ascii format file. Sconvert always requires the
- type to be specified, however.
-
-
-
-
-4th Berkeley Distribution 20 March 1986 SCONVERT(1)
-</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_ngspice_and_gschem.html b/docs/wiki/geda_ngspice_and_gschem.html
deleted file mode 100644
index 70c410b..0000000
--- a/docs/wiki/geda_ngspice_and_gschem.html
+++ /dev/null
@@ -1,192 +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>geda:ngspice_and_gschem</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2008-04-04T11:51:14-0400" />
-<meta name="keywords" content="geda,ngspice_and_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/"; />
-<link rel="contents" href="http://geda.seul.org/wiki/geda:ngspice_and_gschem?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:ngspice_and_gschem"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:ngspice_and_gschem"; />
-<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="#overview" class="toc">Overview</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#setup" class="toc">Setup</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#adding_some_spice_stuff" class="toc">Adding some SPICE stuff</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#simulation" class="toc">Simulation</a></span></div></li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="overview" id="overview">Overview</a></h1>
-<div class="level1">
-
-<p>
- It is possible to use gschem to make circuit diagrams which can then be simulated with ngspice. The advantage is that you can iteratively design and simulate before you commit to fabrication. The purpose of this tutorial is not to teach the details of SPICE but rather to work a very simple example so that the required steps are made clear. More detailed documents on both Spice and gEDA can be found at:
-</p>
-<ul>
-<li class="level1"><div class="li"> <a href="http://ngspice.sourceforge.net/index.html"; class="urlextern" title="http://ngspice.sourceforge.net/index.html"; rel="nofollow">ngspice</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="geda_csygas.html" class="wikilink1" title="geda:csygas">geda and Spice</a></div>
-</li>
-</ul>
-
-<p>
- There is a <acronym title="Frequently Asked Questions">FAQ</acronym> in the wiki that may be of help: <a href="http://geda.seul.org/wiki/geda:faq-simulation"; class="wikilink1" title="geda:faq-simulation">faq-simulation</a>
-</p>
-
-<p>
- This tutorial is based on the example â??TwoStageAmp.schâ?? in the examples which ship in gEDAâ??s documentation and constructs the first half of that example step by step.
-</p>
-
-</div>
-<!-- SECTION "Overview" [1-772] -->
-<h1><a name="setup" id="setup">Setup</a></h1>
-<div class="level1">
-
-<p>
- It is assumed that you are able to construct schematics with gschem. If you are unsure how to do this please visit <a href="http://geda.seul.org/wiki/geda:gsch2pcb_tutorial"; class="wikilink1" title="geda:gsch2pcb_tutorial">gsch2pcb_tutorial</a>. So letâ??s start by making a project directory â??simpleSPICEâ?? and creating a schematic file named â??simplespice.schâ?? in that directory.
-</p>
-
-<p>
-Use gschem to build up a schematic that looks like:
-</p>
-
-<p>
-<a href="_detail/geda_simple1.html" class="media" title="geda:simple1.png"><img src="_media/geda_simple1.png" class="media" alt="" /></a>
-</p>
-
-<p>
-Note that three named nets have been created, â??Vinâ??, â??Voutâ??, and â??Vbaseâ??. Although this is not necessary, it is an easy way to keep track of important points in the circuit. Naming nets is done by editing either by right-clicking or by hitting â??eeâ?? while a net is selected; then just add the attribute â??netnameâ?? and give it an appropriate name. Although we now have a circuit to simulate, we need to add some SPICE specific information before we can get any results.
-</p>
-
-</div>
-<!-- SECTION "Setup" [773-1612] -->
-<h1><a name="adding_some_spice_stuff" id="adding_some_spice_stuff">Adding some SPICE stuff</a></h1>
-<div class="level1">
-
-<p>
- There are four things that we will need to add to the schematic to make it suitable for simulation. We must include an input signal, describe the properties of the transistor, explicitly define Vcc, and add some lines to the SPICE file. When all these things are done the schematic will look like:
-</p>
-
-<p>
-<a href="_detail/geda_schematicfinished2.html" class="media" title="geda:schematicfinished2.png"><img src="_media/geda_schematicfinished2.png" class="media" title="" alt="" /></a>
-</p>
-
-<p>
-The input signal is added by choosing â??SPICE simulation elements→vac-1.symâ?? from the components menu and, after placing the device, editing its properties to read:
-</p>
-
-<p>
-<a href="_detail/geda_dialogvac.html" class="media" title="geda:dialogvac.png"><img src="_media/geda_dialogvac.png" class="media" title="" alt="" /></a>
-</p>
-
-<p>
-Notice that the â??valueâ?? is a string that will be read by SPICE. You learn about SPICE syntax in the links given above.
-</p>
-
-<p>
-Vcc is set in basically the same way except we choose â??SPICE simulation elements→vdc-1.symâ?? from the components menu. Its properties should be edited to read:
-</p>
-
-<p>
-<a href="_detail/geda_dialogvdc1.html" class="media" title="geda:dialogvdc1.png"><img src="_media/geda_dialogvdc1.png" class="media" title="" alt="" /></a>
-</p>
-
-<p>
-The transistor setup is a bit more complicated. We must first have access to a SPICE model for the transistor of interest. This can usually be found from the transistor datasheet or downloaded from a manufacturer website. For this example we will consider the ubiquitous 2N3904. Which has the following model:
-</p>
-<pre class="code">.model 2N3904 NPN(Is=6.734f Xti=3 Eg=1.11 Vaf=74.03 Bf=416.4 Ne=1.259
-+ Ise=6.734f Ikf=66.78m Xtb=1.5 Br=.7371 Nc=2 Isc=0 Ikr=0 Rc=1
-+ Cjc=3.638p Mjc=.3085 Vjc=.75 Fc=.5 Cje=4.493p Mje=.2593 Vje=.75
-+ Tr=239.5n Tf=301.2p Itf=.4 Vtf=4 Xtf=2 Rb=10)
-* Fairchild pid=23 case=TO92
-* 88-09-08 bam creation </pre>
-
-<p>
-Make a sub-folder named â??modelsâ?? in our project folder â??simpleSPICEâ?? and make a file named â??2N3904.modâ?? in that folder and fill it with the model text given above. Make sure that there is a newline at the end of the file, this is important so that when the final SPICE file is created everything will be on its own line. Okay, now that we have a model for the transistor we have to apply it. Edit the transistor properties to read:
-</p>
-
-<p>
-<a href="_detail/geda_dialogtrans.html" class="media" title="geda:dialogtrans.png"><img src="_media/geda_dialogtrans.png" class="media" title="" alt="" /></a>
-</p>
-
-<p>
-Now we also need to inform gschem of the model file we created. This is done by adding a â??spice-model-1.symâ?? symbol to the schematic. Edit its properties to read:
-</p>
-
-<p>
-<a href="_detail/geda_dialogmodel.html" class="media" title="geda:dialogmodel.png"><img src="_media/geda_dialogmodel.png" class="media" title="" alt="" /></a>
-</p>
-
-<p>
-Okay, there are two more symbols to add. The first is â??spice-include-1.symâ?? which will include a text file which describes the SPICE simulation you may want to run and the other is â??spice-directive-1.symâ?? which allows additional lines to be added to the SPICE file. The properties of these symbols can be set as:
-</p>
-
-<p>
-<a href="_detail/geda_dialoginclude.html" class="media" title="geda:dialoginclude.png"><img src="_media/geda_dialoginclude.png" class="media" alt="" /></a>
-</p>
-
-<p>
-<a href="_detail/geda_dialogdirective.html" class="media" title="geda:dialogdirective.png"><img src="_media/geda_dialogdirective.png" class="media" alt="" /></a>
-</p>
-
-<p>
-Congratulations! We now have a schematic that is ready for simulation.
-</p>
-
-</div>
-<!-- SECTION "Adding some SPICE stuff" [1613-4297] -->
-<h1><a name="simulation" id="simulation">Simulation</a></h1>
-<div class="level1">
-
-<p>
- Although the schematic is in place, we still need to write out what the simulation will do. This information will be written in the './Simulation.cmdâ?? that was referenced in the include symbol added in the last section. For now, create a file './Simulation.cmdâ?? and make it read:
-</p>
-<pre class="code">.OP
-.AC DEC 20 1Hz 100MegHz
-* .DC VINPUT 0 5 .01
-* .DC VINPUT 1 2 .01
-.plot ac v(Vout) v(Vin)
-.print ac v(Vout) v(Vin)</pre>
-
-<p>
-Which does one AC analysis while two lines for DC analysis are commented out. Then both Vout and Vin are plotted as well as having their numerical values printed. As mentioned previously, SPICE can be learned from the links given above.
-</p>
-
-<p>
-Now that we have described the simulation we want done, open a terminal, move to the â??simpleSPICEâ?? directory and type the command:
-</p>
-<pre class="code">gnetlist -g spice-sdb -o spice.net simplespice.sch</pre>
-
-<p>
- to produce the SPICE file â??spice.netâ??. Now the simulation can be run in batch mode by typing:
-</p>
-<pre class="code">ngspice -b spice.net > result.txt</pre>
-
-<p>
- which will spew a great deal of text to â??result.txtâ??. The file should include the numerical output we requested as well as a crude ascii plot of the results. Note that the 10mV input signal has been amplified to about -280mV over a wide frequency range. If you want to veiw graphical plots ngspice can be operated in interactive mode by removing the -b option. The ngspice website describes this in more detail. In any event, we now have the simulation results in a nice text format suitable for reading with a script, perhaps something written in python or octave, for further graphing or analysis.
-</p>
-
-</div>
-<!-- SECTION "Simulation" [4298-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/geda_ngspice_mp.html b/docs/wiki/geda_ngspice_mp.html
deleted file mode 100644
index ab47781..0000000
--- a/docs/wiki/geda_ngspice_mp.html
+++ /dev/null
@@ -1,351 +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>geda:ngspice_mp</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="keywords" content="geda,ngspice_mp" />
-<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/geda:ngspice_mp?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:ngspice_mp"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:ngspice_mp"; />
-<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">
-
-
-
-<h1><a name="ngspice_man-page" id="ngspice_man-page">ngspice man-page</a></h1>
-<div class="level1">
-<pre class="code">SPICE(1) SPICE(1)
-
-
-
-NAME
- spice - circuit simulator
-
-SYNOPSIS
- spice [ -n ] [ -t term ] [ -r rawfile] [ -b ] [ -i ] [ input file ... ]
-
-DESCRIPTION
- This manual page describes the commands available for interactive use
- of SPICE3. For details of circuit descriptions and the process of simu-
- lating a circuit, see the SPICE3 User�s Manual. The commands available
- are a superset of those available for nutmeg - only the additional com-
- mands available in SPICE3 are described here. You should be familiar
- with the manual page for nutmeg(1) before reading this manual page.
-
- Arguments are:
-
- -n (or --no-spiceinit)
- Don�t try to source the file ".spiceinit" upon startup. Normally
- SPICE3 tries to find the file in the current directory, and if
- it is not found then in the user�s home directory.
-
- -q (or --completion)
- Enable command completion.
-
- -t term (or --term=term)
- The program is being run on a terminal with mfb name term.
-
- -b (or --batch)
- Run in batch mode. SPICE3 will read the standard input or the
- specified input file and do the simulation. Note that if the
- standard input is not a terminal, SPICE3 will default to batch
- mode, unless the -i flag is given.
-
- -s (or --server)
- Run in server mode. This is like batch mode, except that a tem-
- porary rawfile is used and then written to the standard output,
- preceded by a line with a single "@", after the simulation is
- done. This mode is used by the spice daemon.
-
- -i (or --interactive)
- Run in interactive mode. This is useful if the standard input is
- not a terminal but interactive mode is desired. Command comple-
- tion is not available unless the standard input is a terminal,
- however.
-
- -r rawfile (or --rawfile=file)
- Use rawfile as the default file into which the results of the
- simulation are saved.
-
- -c circuitfile (or --circuitfile=circuitfile)
- Use circuitfile as the default input deck.
-
- -h (or --help)
- Display a verbose help on the arguments available to the pro-
- gram.
-
- -v (or --version)
- Display a version number and copyright information of the pro-
- gram.
-
- Further arguments are taken to be SPICE3 input decks, which are read
- and saved. (If batch mode is requested then they are run immediately.)
-
- SPICE3 will accept any SPICE2 input decks, and output ascii plots,
- fourier analyses, and node printouts as specified in .plot, .four, and
- .print cards. If a out parameter is given on a .width card, the effect
- is the same as set width = .... Since SPICE3 ascii plots do not use
- multiple ranges, however, if vectors together on a .plot card have dif-
- ferent ranges they will not provide as much information as they would
- in SPICE2. The output of SPICE3 is also much less verbose than SPICE2,
- in that the only data printed is that requested by the above cards.
-
- Vector names are the same as in nutmeg, with this addition: a name such
- as @name[param], where name is either the name of a device instance or
- model, denotes the value of the param parameter of the device or model.
- See the SPICE3 User�s Manual for details of what parameters are avail-
- able. The value is a vector of length 1. This function is also avail-
- able with the show command, and is available with variables for conve-
- nience for command scripts.
-
- SPICE3 commands are as follows (these are only those commands not also
- available in nutmeg - consult the nutmeg manual page for more com-
- mands):
-
- setcirc [circuit name]
- Change the current circuit. The current circuit is the one that
- is used for the simulation commands below. When a circuit is
- loaded with the source command (see below) it becomes the cur-
- rent circuit.
-
- op [.op card args]
- Do an operating point analysis.
-
- tran [.tran card args]
- Do a transient analysis.
-
- ac [.ac card args]
- Do an ac analysis.
-
- dc [.dc card args]
- Do a dc transfer curve analysis.
-
- listing [logical] [physical] [deck] [expand]
- Print a listing of the current circuit. If the logical argument
- is given, the listing is with all continuation lines collapsed
- into one line, and if the physical argument is given the lines
- are printed out as they were found in the file. The default is
- logical. A deck listing is just like the physical listing,
- except without the line numbers it recreates the input file ver-
- batim (except that it does not preserve case). If the word
- expand is present, the circuit will be printed with all subcir-
- cuits expanded.
-
- edit [file]
- Print the current SPICE3 deck into a file, call up the editor on
- that file and allow the user to modify it, and then read it back
- in, replacing the origonal deck. If a filename is given, then
- edit that file and load it, making the circuit the current one.
-
- resume Resume a simulation after a stop.
-
- show Show a device parameter.
-
- alter Alter a device parameter.
-
- state Print the state of the circuit. (This command is largely unim-
- plemented.)
-
- save [all] [output ...] or .save [all] [output ...]
- Save a set of outputs, discarding the rest. If a node has been
- mentioned in a save command, it will appear in the working plot
- after a run has completed, or in the rawfile if spice is run in
- batch mode. If a node is traced or plotted (see below) it will
- also be saved. For backward compatibility, if there are no save
- commands given, all outputs are saved.
-
- stop [ after n] [ when something cond something ] ...
- Set a breakpoint. The argument after n means stop after n itera-
- tion number n, and the argument when something cond something
- means stop when the first something is in the given relation
- with the second something, the possible relations being eq or =
- (equal to), ne or <> (not equal to), gt or > (greater than), lt
- or < (less than), ge or >= (greater than or equal to), and le or
- <= (less than or equal to). IO redirection is disabled for the
- stop command, since the relational operations conflict with it
- (it doesn�t produce any output anyway). The somethings above
- may be node names in the running circuit, or real values. If
- more than one condition is given, e.g. stop after 4 when v(1) >
- 4 when v(2) < 2, the conjunction of the conditions is implied.
-
- trace [ node ...]
- Trace nodes. Every iteration the value of the node is printed to
- the standard output.
-
- iplot [ node ...]
- Incrementally plot the values of the nodes while SPICE3 runs.
-
- step [number]
- Iterate number times, or once, and then stop.
-
- status Display all of the traces and breakpoints currently in effect.
-
- delete [debug number ...]
- Delete the specified breakpoints and traces. The debug numbers
- are those shown by the status command. (Unless you do status >
- file, in which case the debug numbers aren�t printed.)
-
- reset Throw out any intermediate data in the circuit (e.g, after a
- breakpoint or after one or more analyses have been done
- already), and re-parse the deck. The circuit can then be re-run.
- (Note: this command used to be end in SPICE 3a5 and earlier ver-
- sions -- end is now used for control structures.) The run com-
- mand will take care of this automatically, so this command
- should not be necessary...
-
- run [rawfile]
- Run the simulation as specified in the input file. If there were
- any of the control cards .ac, .op, .tran, or .dc, they are exe-
- cuted. The output is put in rawfile if it was given, in addition
- to being available interactively.
-
- source file
- Read the SPICE3 input file file. Nutmeg and SPICE3 commands may
- be included in the file, and must be enclosed between the lines
- .control and .endc. These commands are executed immediately
- after the circuit is loaded, so a control line of ac ... will
- work the same as the corresponding .ac card. The first line in
- any input file is considered a title line and not parsed but
- kept as the name of the circuit. The exception to this rule is
- the file .spiceinit. Thus, a SPICE3 command script must begin
- with a blank line and then with a .control line. Also, any line
- beginning with the characters *# is considered a control line.
- This makes it possible to imbed commands in SPICE3 input files
- that will be ignored by earlier versions of SPICE. Note: in
- spice3a7 and before, the .control and .endc lines were not
- needed, and any line beginning with the name of a front-end com-
- mand would be executed.
-
- linearize vec ...
- Create a new plot with all of the vectors in the current plot,
- or only those mentioned if arguments are given. The new vectors
- will be interpolated onto a linear time scale, which is deter-
- mined by the values of tstep, tstart, and tstop in the currently
- active transient analysis. The currently loaded deck must
- include a transient analysis (a tran command may be run interac-
- tively before the last reset, alternately), and the current plot
- must be from this transient analysis. This command is needed
- because SPICE3 doesn�t output the results from a transient anal-
- ysis in the same manner that SPICE2 did.
-
- There are several set variables that SPICE3 uses but nutmeg does not.
- They are:
-
- editor
- The editor to use for the edit command.
-
- modelcard
- The name of the model card (normally .model).
-
- noaskquit
- Do not check to make sure that there are no circuits
- suspended and no plots unsaved. Normally SPICE3 will
- warn the user when he tries to quit if this is the
- case.
-
- nobjthack
- Assume that BJT�s have 4 nodes.
-
- noparse
- Don�t attempt to parse decks when they are read in
- (useful for debugging). Of course, they cannot be run
- if they are not parsed.
-
- nosubckt
- Don�t expand subcircuits.
-
- renumber
- Renumber input lines when a deck has .include�s.
-
- subend
- The card to end subcircuits (normally .ends).
-
- subinvoke
- The prefix to invoke subcircuits (normally x).
-
- substart
- The card to begin subcircuits (normally .subckt).
-
- There are a number of rusage parameters available, in addition to the
- ones available in nutmeg:
-
-
-
- If there are subcircuits in the input file, SPICE3 expands instances of
- them. A subcircuit is delimited by the cards .subckt and .ends, or
- whatever the value of the variables substart and subend is, respec-
- tively. An instance of a subcircuit is created by specifying a device
- with type �x� - the device line is written
-
- xname node1 node2 ... subcktname
-
- where the nodes are the node names that replace the formal parameters
- on the .subckt line. All nodes that are not formal parameters are
- prepended with the name given to the instance and a �:�, as are the
- names of the devices in the subcircuit. If there are several nested
- subcircuits, node and device names look like subckt1:subckt2:...:name.
- If the variable subinvoke is set, then it is used as the prefix that
- specifies instances of subcircuits, instead of �x�.
-
-VMS NOTES
- The standard suffix for rawspice files in VMS is ".raw".
-
- You may have to redefine the value EDITOR if you wish to use the edit
- command, since the default for VMS is "vi".
-
-SEE ALSO
- nutmeg(1), sconvert(1), spice(1), mfb(3), writedata(3) SPICE3 User�s
- Guide
-
-AUTHORS
- SPICE3: Tom Quarles (quarles@xxxxxxxxxxxxxxxx)
- nutmeg / User interface: Wayne Christopher (faustus@xxxxxxxxxxxxxxxx)
-
-BUGS
- SPICE3 will recognise all the notations used in SPICE2 .plot cards, and
- will translate vp(1) into ph(v(1)), and so forth. However, if there are
- spaces in these names it won�t work. Hence v(1, 2) and (-.5, .5) aren�t
- recognised.
-
- BJT�s can have either 3 or 4 nodes, which makes it difficult for the
- subcircuit expansion routines to decide what to rename. If the fourth
- parameter has been declared as a model name, then it is assumed that
- there are 3 nodes, otherwise it is considered a node. To disable this
- kludge, you can set the variable "nobjthack", which will force BJT�s to
- have 4 nodes (for the purposes of subcircuit expansion, at least).
-
- The @name[param] notation might not work with trace, iplot, etc. yet.
-
- The first line of a command file (except for the .spiceinit file)
- should be a comment. Otherwise SPICE may create an empty circuit
- structure.
-
-CAVEATS
- SPICE3 files specified on the command line are read in before the .spi-
- ceinit file is read. Thus if you define aliases there that you call in
- a SPICE3 source file mentioned on the command line, they won�t be
- recognised.
-
-
-
-
-4th Berkeley Distribution 20 March 1986 SPICE(1)
-</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_olib_readme.html b/docs/wiki/geda_olib_readme.html
deleted file mode 100644
index 84d72fa..0000000
--- a/docs/wiki/geda_olib_readme.html
+++ /dev/null
@@ -1,135 +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>geda:olib_readme</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="keywords" content="geda,olib_readme" />
-<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/geda:olib_readme?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:olib_readme"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:olib_readme"; />
-<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">
-
-
-
-<h1><a name="olib_orcad_tm_converter_readme" id="olib_orcad_tm_converter_readme">olib (OrCAD (TM) converter) README</a></h1>
-<div class="level1">
-<pre class="code">###############################################################
-README and release notes for olib2geda - 1 settembre 2002
-OrCAD (TM) lib ASCII dump to gEDA .sym converter
-###############################################################
-
-
-What it olib2geda?
-It's a simple automated converter from OrCAD v4 (in SDT version 1.10) parts
-library (in ASCII dump format, through "decomp" utility) to gEDA component
-definition in .sym format file.
-It allow an initial dumb conversion file to file, with one lib converted in
-multiple .sym file, one per component in library.
-The converted component file needs little editing to become usable, but in some
-case needs no editing at all.
-
-
-What olib do.
-* Convert box shaped component in OrCAD (TM) lib in .sym file in gEDA format
-* Place pin, pin name, pin type, pin number
-* Place logic bubble when needed (DOT attribute in OrCAD (TM), for logic nega-
- tion)
-* Place clock arrow when needed (CLK attribute)
-* Place reference, from REFERENCE statement in OrCAD (TM)
-* Place Part name as label and device name as attribute
-* Parse and draw non-box component, with LINE, ARC, CIRCLE and TEXT
-* Add power pin as invisible net=name:pin attribute when detected (in OrCAD (TM)
- invisible pin has tipically T0 and B0 coords)
-* Through command line switch, hides pin name in VECTOR drawed symbols, allowing
- better appearance
-* Write both new (20020825) and old (20020209) file format for .sym files
- through a switch on the command line
-
-
-What olib do not.
-* Do not parse and store alternate component drawing (statement CONVERT in
- OrCAD (TM))
-* Do not handle drawing part using VECTOR list from another part (statement
- VECTOR 'partname' in OrCAD (TM))
-* Do not handle FILL statement in VECTOR statement (incompatible with gEDA, but
- for what i know is used only for "better" part drawing)
-* Do not handle multiple part in one package (slots in gEDA)
-
-
-Bugs.
-More and more. But for the use that I do bugs aren't so critical.
-If you find a bug or want improvements to the program, feel free to contact me
-at the e-mail address at the end of this text.
-
-
-How to obtain last version.
-Open the URL:
-http://digilander.libero.it/tailchaser
-in section "Linux" you can see the main page of olib.
-
-
-Compile and install.
-[[ Ales here, I have incorperated olib into the ./configure build mechanism,
- so these instructions only apply if you build from Mario's distribution ]]
-
-To compile program go in directory 'src' of the unpacked tarball, and type
-'make'. This produces the binary executable, named 'olib'.
-Compilation process uses the flex scanner generator to generate the file
-'olib.c' from the 'olib.lex', and link the library math to the code. The binary
-included in the distribution is compiled on a P266-MMX with RedHat 7.2, with gcc
-version 2.96 and flex 2.5.4, but the program don't require any special feature
-or critical function, as far as I know. At the end of compilation phase, you can
-see two warnings:
-* warning, -s option given but default rule can be matched
-* warning: `yyunput' defined but not used
-this is normal, don't affect program functionality, and you can safely ignore
-it.
-Installation is not needed for normal operations, but if you want you can copy
-only the executable (olib) on a directory in the PATH.
-
-
-Use of olib.
-To convert library, first convert it to ASCII dump with 'decomp' utility
-included in the OrCAD (TM) distribution. After that invoke the lib converter:
-olib path/to/file/file_ascii prefix where 'prefix' is used to generate file name
-of every symbol, like:
-prefix-partname-1.sym
-During the process, you can see a lot of ugly text scrolling in the terminal,
-that show the progress of the conversion. If you want to read this text, you can
-redirect the stderr output to a file:
-olib path/to/file/file_ascii prefix 2> logfile.txt
-where '2>' instruct the shell to redirect stderr output to logfile.txt.
-The converter write one file per part, in the current directory. At the end of
-the execution you can see a lot of file in the directory, extracted from OrCAD
-library.
-In the (not so improbable) case of incomplete conversion of a part (i.e. because
-of unsupported VECTOR 'partname' statement), the file of the incomplete part
-will be named 'prefix-partname-1.sym.part', stand for partial conversion.
-If the conversion process stops with the message: "flex scanner jammed", the
-converter has encountered an unknown statement, an incompatible version of
-library, or a bug. If you can, please report the complete log and the library
-dump, to allow corrections or improvements.
-
-
-Mario Pascucci
-<m.pas@xxxxxxxxx>
-</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_pcb-quick_reference.html b/docs/wiki/geda_pcb-quick_reference.html
deleted file mode 100644
index 9759359..0000000
--- a/docs/wiki/geda_pcb-quick_reference.html
+++ /dev/null
@@ -1,459 +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>geda:pcb-quick_reference</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-05-24T22:27:26-0400" />
-<meta name="keywords" content="geda,pcb-quick_reference" />
-<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/geda:pcb-quick_reference?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:pcb-quick_reference"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:pcb-quick_reference"; />
-<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="#pcbquick_reference" class="toc">PCB: Quick Reference</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#key_mapping" class="toc">Key Mapping</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#pcb_keystrokes" class="toc">PCB Keystrokes</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#viewport_keystrokes" class="toc">Viewport Keystrokes</a></span></div></li>
-</ul>
-</li>
-<li class="level1"><div class="li"><span class="li"><a href="#footprint_reference" class="toc">Footprint Reference</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#general_syntax" class="toc">General syntax</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#elements" class="toc">Elements</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#pads" class="toc">Pads</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#pins" class="toc">Pins</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#examples" class="toc">Examples</a></span></div></li></ul>
-</li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="pcbquick_reference" id="pcbquick_reference">PCB: Quick Reference</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "PCB: Quick Reference" [1-35] -->
-<h2><a name="key_mapping" id="key_mapping">Key Mapping</a></h2>
-<div class="level2">
-
-</div>
-<!-- SECTION "Key Mapping" [36-60] -->
-<h3><a name="pcb_keystrokes" id="pcb_keystrokes">PCB Keystrokes</a></h3>
-<div class="level3">
-<table class="inline">
- <tr>
- <th class="centeralign"> KEY </th><th class="leftalign"> MNEMONIC </th><th class="centeralign"> DESCRIPTION </th>
- </tr>
- <tr>
- <td class="centeralign"> esc </td><td class="leftalign"> panner </td><td> enter panning mode </td>
- </tr>
- <tr>
- <td class="centeralign"> insert </td><td class="leftalign"> insert point </td><td> enter insert point mode. Click and drag on track to insert a point </td>
- </tr>
- <tr>
- <td class="centeralign"> space </td><td class="leftalign"> select </td><td class="leftalign"> enter select mode </td>
- </tr>
- <tr>
- <td class="centeralign"> tab </td><td class="leftalign"> flip view </td><td class="leftalign"> view: flip board </td>
- </tr>
- <tr>
- <td class="centeralign"> shift-del </td><td class="leftalign"> del-cu </td><td class="leftalign"> deletes connected copper (rats are considered a connection) </td>
- </tr>
- <tr>
- <td class="centeralign"> \ </td><td class="leftalign"> thin-draw </td><td class="leftalign"> toggles thin draw mode </td>
- </tr>
- <tr>
- <td class="centeralign"> shift-alt-a </td><td class="leftalign"> unselect </td><td class="leftalign"> clear selection </td>
- </tr>
- <tr>
- <td class="centeralign"> b </td><td class="leftalign"> to other side </td><td class="leftalign"> flip object to the other side of the board </td>
- </tr>
- <tr>
- <td class="centeralign"> shift-b </td><td class="leftalign"> flip view </td><td class="leftalign"> view: flip board </td>
- </tr>
- <tr>
- <td class="centeralign"> c </td><td class="leftalign"> center </td><td class="leftalign"> view: center display at cursor position </td>
- </tr>
- <tr>
- <td class="centeralign"> ctrl-c </td><td> copy to buffer</td><td class="leftalign"> copy selection to buffer and unselect </td>
- </tr>
- <tr>
- <td class="centeralign"> d </td><td class="leftalign"> display name </td><td class="leftalign"> display pin or pad name </td>
- </tr>
- <tr>
- <td class="centeralign"> shift-d </td><td class="leftalign"> pinout dialog </td><td class="leftalign"> open pinout window for element under mouse cursor </td>
- </tr>
- <tr>
- <td class="centeralign"> e </td><td> eliminate rats</td><td class="leftalign"> delete all rats </td>
- </tr>
- <tr>
- <td class="centeralign"> shift-e </td><td class="leftalign"> eliminate some rats </td><td class="leftalign"> delete selected rats </td>
- </tr>
- <tr>
- <td class="centeralign"> f </td><td class="leftalign"> find </td><td class="leftalign"> highlight connections to object under mouse cursor </td>
- </tr>
- <tr>
- <td class="centeralign"> shift-f </td><td class="leftalign"> un-find </td><td class="leftalign"> un-highlight found connections </td>
- </tr>
- <tr>
- <td class="centeralign"> g </td><td class="leftalign"> increase grid </td><td class="leftalign"> increment grid by configured grid increment </td>
- </tr>
- <tr>
- <td class="centeralign"> shift-g </td><td class="leftalign"> decrease grid </td><td class="leftalign"> decrement grid by configured grid increment </td>
- </tr>
- <tr>
- <td class="centeralign"> h </td><td class="leftalign"> hide </td><td class="leftalign"> toggle the visiblity of the refdes or value attached to the current component </td>
- </tr>
- <tr>
- <td class="centeralign"> ctrl-h </td><td class="leftalign"> holeplate </td><td class="leftalign"> toggle plating of a via. Used to produce non metalized mounting holes </td>
- </tr>
- <tr>
- <td class="centeralign"> k </td><td class="leftalign"> klearance </td><td class="leftalign"> increment clearance (soldermask to copper edge) </td>
- </tr>
- <tr>
- <td class="centeralign"> shift-k </td><td class="leftalign"> klear (-) </td><td class="leftalign"> decrement clearance (soldermask to copper edge (NOTE: can go negative!)) </td>
- </tr>
- <tr>
- <td class="centeralign"> l </td><td class="leftalign"> increase line </td><td class="leftalign"> increment width of the line tool, adds to the settings of the current line style </td>
- </tr>
- <tr>
- <td class="centeralign"> shift-l </td><td class="leftalign"> decrease line </td><td> reduce the current linewidth </td>
- </tr>
- <tr>
- <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="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>
- </tr>
- <tr>
- <td class="centeralign"> n </td><td class="leftalign"> name </td><td> show object refdes / pin number at mouse pointer </td>
- </tr>
- <tr>
- <td class="centeralign"> shift-n </td><td class="leftalign"> next </td><td> Select the shortest unselected rat on the board </td>
- </tr>
- <tr>
- <td class="centeralign"> o </td><td class="leftalign"> optimize rats </td><td> optimize and redraw all rats </td>
- </tr>
- <tr>
- <td class="centeralign"> shift-o </td><td class="leftalign"> optimize some rats </td><td> optimize and redraw selected nets only </td>
- </tr>
- <tr>
- <td class="centeralign"> shift-p </td><td class="leftalign"> polygon close </td><td class="leftalign"> connect the first point of a polygon with the last </td>
- </tr>
- <tr>
- <td class="centeralign"> q </td><td class="leftalign"> square toggle </td><td class="leftalign"> toggle square/round corners on pads </td>
- </tr>
- <tr>
- <td class="centeralign"> ctrl-r </td><td class="leftalign"> report </td><td class="leftalign"> show object report </td>
- </tr>
- <tr>
- <td class="centeralign"> s </td><td class="leftalign"> size </td><td class="leftalign"> increment size </td>
- </tr>
- <tr>
- <td class="centeralign"> shift-s </td><td class="leftalign"> size (-) </td><td class="leftalign"> decrement size </td>
- </tr>
- <tr>
- <td class="centeralign"> alt-s </td><td class="leftalign"> sizehole </td><td class="leftalign"> increase the hole size </td>
- </tr>
- <tr>
- <td class="centeralign"> alt-shift-s </td><td class="leftalign"> sizehole (-) </td><td class="leftalign"> decrease the hole size </td>
- </tr>
- <tr>
- <td class="centeralign"> ctrl-s </td><td class="leftalign"> sizehole </td><td class="leftalign"> increase the hole size </td>
- </tr>
- <tr>
- <td class="centeralign"> ctrl-shift-s </td><td class="leftalign"> sizehole (-) </td><td class="leftalign"> decrease the hole size </td>
- </tr>
- <tr>
- <td class="centeralign"> v </td><td class="leftalign"> view extents </td><td class="leftalign"> global view of working area </td>
- </tr>
- <tr>
- <td class="centeralign"> z </td><td class="leftalign"> zoom </td><td class="leftalign"> view: zoom in </td>
- </tr>
- <tr>
- <td class="centeralign"> shift-z </td><td class="leftalign"> un-zoom </td><td class="leftalign"> view: zoom out </td>
- </tr>
- <tr>
- <td class="centeralign"> F1 </td><td class="leftalign"> via </td><td> enter via tool </td>
- </tr>
- <tr>
- <td class="centeralign"> F2 </td><td class="leftalign"> line </td><td class="leftalign"> enter line tool </td>
- </tr>
- <tr>
- <td class="centeralign"> F3 </td><td class="leftalign"> arc </td><td> enter arc tool </td>
- </tr>
- <tr>
- <td class="centeralign"> F4 </td><td class="leftalign"> text </td><td> enter text tool </td>
- </tr>
- <tr>
- <td class="centeralign"> F5 </td><td class="leftalign"> rectangle </td><td> enter rectangle tool</td>
- </tr>
- <tr>
- <td class="centeralign"> F6 </td><td class="leftalign"> polygon </td><td> enter polygon tool </td>
- </tr>
- <tr>
- <td class="centeralign"> F7 </td><td class="leftalign"> buffer </td><td> enter buffer mode </td>
- </tr>
- <tr>
- <td class="centeralign"> F8 </td><td class="leftalign"> delete </td><td> enter remove mode </td>
- </tr>
- <tr>
- <td class="centeralign"> F9 </td><td class="leftalign"> rotate </td><td class="leftalign"> enter rotate mode </td>
- </tr>
- <tr>
- <td class="centeralign"> F10 </td><td class="leftalign"> file menu </td><td> file menu </td>
- </tr>
- <tr>
- <td class="centeralign"> F11 </td><td class="leftalign"> select </td><td class="leftalign"> enter select mode (same as [space]) </td>
- </tr>
- <tr>
- <td class="centeralign"> F12 </td><td class="leftalign"> lock </td><td> enter lock mode </td>
- </tr>
-</table>
-
-</div>
-<!-- SECTION "PCB Keystrokes" [61-3535] -->
-<h2><a name="viewport_keystrokes" id="viewport_keystrokes">Viewport Keystrokes</a></h2>
-<div class="level2">
-<table class="inline">
- <tr>
- <th class="centeralign"> KEY </th><th class="centeralign"> MNEMONIC </th><th class="centeralign"> DESCRIPTION </th>
- </tr>
- <tr>
- <td class="centeralign"> esc </td><td class="centeralign"> panner </td><td class="rightalign"> </td>
- </tr>
- <tr>
- <td class="centeralign"> v </td><td class="centeralign"> view extents </td><td>global view of working area</td>
- </tr>
- <tr>
- <td class="centeralign"> c </td><td class="centeralign"> center </td><td>centers view on cursor</td>
- </tr>
- <tr>
- <td class="centeralign"> z </td><td class="centeralign"> zoom </td><td>zoom in</td>
- </tr>
- <tr>
- <td class="centeralign"> shift-z </td><td class="centeralign"> un-zoom </td><td class="rightalign"> </td>
- </tr>
- <tr>
- <td class="centeralign"> \ </td><td class="centeralign"> thin-draw on/off </td><td>toggles thin draw mode</td>
- </tr>
- <tr>
- <td class="centeralign"> tab </td><td class="centeralign"> flip view </td><td>flip board</td>
- </tr>
- <tr>
- <td class="centeralign"> shift-b </td><td class="centeralign"> flip view </td><td>flip board</td>
- </tr>
-</table>
-
-</div>
-<!-- SECTION "Viewport Keystrokes" [3536-3909] -->
-<h1><a name="footprint_reference" id="footprint_reference">Footprint Reference</a></h1>
-<div class="level1">
-
-<p>
-The Master document for footprint creation is the <a href="http://pcb.sourceforge.net/index.html#dir"; class="urlextern" title="http://pcb.sourceforge.net/index.html#dir"; rel="nofollow">PCB Manual</a>. There is also Stuart Brorsonâ??s <a href="http://www.brorson.com/gEDA/land_patterns_20050129.pdf"; class="urlextern" title="http://www.brorson.com/gEDA/land_patterns_20050129.pdf"; rel="nofollow">Footprint Creation for the Open-Source Layout Program PCB</a>.
-</p>
-
-</div>
-<!-- SECTION "Footprint Reference" [3910-4203] -->
-<h2><a name="general_syntax" id="general_syntax">General syntax</a></h2>
-<div class="level2">
-
-<p>
-A pcb footprint file may contain any of the following commands:
-</p>
-<ul>
-<li class="level1"><div class="li"> <strong><code>Element [element_flags, description, pcb-name, value, mark_x, mark_y, text_x, text_y, text_direction, text_scale, text_flags]</code></strong></div>
-</li>
-<li class="level1"><div class="li"> <strong><code>Pad [x1 y1 x2 y2 thickness clearance mask name pad_number flags]</code></strong></div>
-</li>
-<li class="level1"><div class="li"> <strong><code>Pin [x y thickness clearance mask drillholedia name number flags]</code></strong></div>
-</li>
-<li class="level1"><div class="li"> <strong><code>ElementArc [x y r1 r2 startangle sweepangle thickness]</code></strong></div>
-</li>
-<li class="level1"><div class="li"> <strong><code>ElementLine [x1 y1 x2 y2 thickness] â??> thickness != 1000 = 10 mils almost for all footprints</code></strong></div>
-</li>
-<li class="level1"><div class="li"> Comment lines start with the â??<strong><code>#</code></strong>â??-sign</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "General syntax" [4204-4816] -->
-<h2><a name="elements" id="elements">Elements</a></h2>
-<div class="level2">
-
-<p>
-<strong><code>Element [element_flags, description, pcb-name, value, mark_x, mark_y, text_x, text_y, text_direction, text_scale, text_flags]</code></strong>
-</p>
-<table class="inline">
- <tr>
- <th class="centeralign"> item </th><th class="centeralign"> allowed value </th><th class="centeralign"> explanation </th><th class="centeralign"> comment </th>
- </tr>
- <tr>
- <td class="centeralign"> element_flags </td><td class="centeralign"> unsigned hex value </td><td class="rightalign"> </td><td class="rightalign"> </td>
- </tr>
- <tr>
- <td class="centeralign"> description </td><td class="centeralign"> string </td><td class="centeralign"> text description of footprint </td><td class="leftalign">written by footprint author </td>
- </tr>
- <tr>
- <td class="centeralign"> pcb name </td><td class="centeralign"> string </td><td class="centeralign"> refdes used on this particular pcb </td><td class="leftalign">xxx </td>
- </tr>
- <tr>
- <td class="centeralign"> value </td><td class="centeralign"> string </td><td class="centeralign"> value of component on this particular pcb layout </td><td class="leftalign">xxx </td>
- </tr>
- <tr>
- <td class="centeralign"> mark_x </td><td class="centeralign"> 1/100th mils </td><td class="rightalign"> </td><td class="rightalign"> </td>
- </tr>
- <tr>
- <td class="centeralign"> mark_y </td><td class="centeralign"> 1/100th mils </td><td class="rightalign"> </td><td class="rightalign"> </td>
- </tr>
- <tr>
- <td class="centeralign"> text_x </td><td class="centeralign"> 1/100th mils </td><td class="rightalign"> </td><td class="rightalign"> </td>
- </tr>
- <tr>
- <td class="centeralign"> text_y </td><td class="centeralign"> 1/100th mils </td><td class="rightalign"> </td><td class="rightalign"> </td>
- </tr>
- <tr>
- <td class="centeralign"> text direction </td><td class="centeralign"> decimal integer </td><td class="centeralign"> 0=horiz; 1=ccw90; 2=180; 3=cw90 </td><td class="rightalign"> </td>
- </tr>
- <tr>
- <td class="centeralign"> text_scale </td><td class="centeralign"> decimal integer </td><td class="rightalign"> </td><td class="leftalign">usu. set 100 </td>
- </tr>
- <tr>
- <td class="centeralign"> text_flags </td><td class="centeralign"> unsigned hex </td><td class="rightalign"> </td><td class="rightalign"> </td>
- </tr>
-</table>
-
-</div>
-<!-- SECTION "Elements" [4817-5644] -->
-<h2><a name="pads" id="pads">Pads</a></h2>
-<div class="level2">
-
-<p>
-<strong><code>Pad[x1 y1 x2 y2 thickness clearance mask name pad_number flags]</code></strong>
-</p>
-<table class="inline">
- <tr>
- <th class="centeralign"> Item </th><th class="centeralign"> Allowed Value </th><th class="centeralign"> Explanation </th><th class="centeralign"> Comment </th>
- </tr>
- <tr>
- <td class="centeralign"> x1 </td><td class="centeralign"> 1/100th mils </td><td class="centeralign"> x(1st point) </td><td class="rightalign"> </td>
- </tr>
- <tr>
- <td class="centeralign"> y1 </td><td class="centeralign"> 1/100th mils </td><td class="centeralign"> y(1st point) </td><td class="rightalign"> </td>
- </tr>
- <tr>
- <td class="centeralign"> x2 </td><td class="centeralign"> 1/100th mils </td><td class="centeralign"> x(2nd point) </td><td class="rightalign"> </td>
- </tr>
- <tr>
- <td class="centeralign"> y2 </td><td class="centeralign"> 1/100th mils </td><td class="centeralign"> y(2nd point) </td><td class="rightalign"> </td>
- </tr>
- <tr>
- <td class="centeralign"> thickness </td><td class="centeralign"> 1/100 mils </td><td class="centeralign"> width of metal surrounding line segment </td><td class="leftalign">see Brorson .pdf </td>
- </tr>
- <tr>
- <td class="centeralign"> clearance </td><td class="centeralign"> 1/100 mils </td><td class="centeralign"> distance to any other copper on any layer </td><td class="leftalign">actually 1/2 of this number is used! </td>
- </tr>
- <tr>
- <td class="centeralign"> mask </td><td class="centeralign"> 1/100th mils </td><td class="centeralign"> width of mask relief </td><td class="leftalign">actual width of the mask centered on pad copper </td>
- </tr>
- <tr>
- <td class="centeralign"> name </td><td class="centeralign"> string </td><td class="centeralign"> name of pad (arb. string) </td><td class="leftalign">e.g. â??pad_1â?? or â??positiveâ?? or any other string </td>
- </tr>
- <tr>
- <td class="centeralign"> pad_number </td><td class="centeralign"> string </td><td class="centeralign"> pad # </td><td class="leftalign">used for nets. it MUST be consistent with the definitions on the netlist. </td>
- </tr>
- <tr>
- <td class="centeralign"> flags </td><td class="centeralign"> hex value </td><td class="centeralign"> xxx </td><td class="rightalign"> </td>
- </tr>
-</table>
-
-</div>
-<!-- SECTION "Pads" [5645-6549] -->
-<h2><a name="pins" id="pins">Pins</a></h2>
-<div class="level2">
-
-<p>
-<strong><code>Pin[x y thickness clearance mask drillholedia name number flags]</code></strong>
-</p>
-<table class="inline">
- <tr>
- <th class="centeralign"> Item </th><th class="leftalign"> Allowed Value </th><th class="centeralign"> Explanation </th><th class="centeralign"> Comment </th>
- </tr>
- <tr>
- <td class="centeralign"> x </td><td class="centeralign"> 1/100th mils </td><td class="centeralign"> pin x coord. </td><td class="rightalign"> </td>
- </tr>
- <tr>
- <td class="centeralign"> y </td><td class="centeralign"> 1/100th mils </td><td class="centeralign"> pin y coord. </td><td class="rightalign"> </td>
- </tr>
- <tr>
- <td class="centeralign"> thickness </td><td class="centeralign"> 1/100th mils </td><td class="centeralign"> copper diameter </td><td class="rightalign"> </td>
- </tr>
- <tr>
- <td class="centeralign"> clearance </td><td class="centeralign"> 1/100th mils </td><td class="centeralign"> 2*(cu to cu clearance) </td><td class="leftalign">if you want a 10 mil clearance, put 2000 (20 mils) here </td>
- </tr>
- <tr>
- <td class="centeralign"> mask </td><td class="centeralign"> 1/100th mils </td><td class="centeralign"> diameter of mask aperture </td><td class="leftalign">actual dia. of hole in mask </td>
- </tr>
- <tr>
- <td class="centeralign"> drillholedia </td><td class="centeralign"> 1/100th mils </td><td class="centeralign"> dia. of hole </td><td class="rightalign"> </td>
- </tr>
- <tr>
- <td class="centeralign"> name </td><td class="centeralign"> string </td><td class="centeralign"> arb. pin name </td><td class="rightalign"> </td>
- </tr>
- <tr>
- <td class="centeralign"> number </td><td class="centeralign"> decimal integer </td><td class="centeralign"> pin number used by nets/rats </td><td class="rightalign"> </td>
- </tr>
- <tr>
- <td class="centeralign"> flags </td><td class="centeralign"> hex </td><td class="centeralign"> xxx </td><td class="rightalign"> </td>
- </tr>
-</table>
-
-</div>
-<!-- SECTION "Pins" [6550-7248] -->
-<h2><a name="examples" id="examples">Examples</a></h2>
-<div class="level2">
-<ul>
-<li class="level1"><div class="li"> <strong><code>Pad[-24606 14760 -19538 14760 1181 2000 3181 â??â?? â??16â?? â??squareâ??]</code></strong></div>
-</li>
-<li class="level1"><div class="li"> <strong><code>Pad[-14760 19538 -14760 24606 1181 2000 3181 â??â?? â??17â?? â??square,edge2â??]</code></strong></div>
-</li>
-<li class="level1"><div class="li"> <strong><code>Pin[0 0 12000 2000 12500 6400 â??â?? â??1â?? 0Ã?00000001]</code></strong></div>
-</li>
-<li class="level1"><div class="li"> <strong><code>ElementArc [0 0 6800 6800 0 360 1000]</code></strong></div>
-</li>
-<li class="level1"><div class="li"> <strong><code>ElementLine [-26696 -26696 26696 -26696 1000]</code></strong></div>
-</li>
-<li class="level1"><div class="li"> <strong><code># notes within PCB Footprints go after the pound sign</code></strong></div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Examples" [7249-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/geda_pcb.html b/docs/wiki/geda_pcb.html
deleted file mode 100644
index 0131284..0000000
--- a/docs/wiki/geda_pcb.html
+++ /dev/null
@@ -1,27 +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>geda:pcb</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="noindex,follow" />
-<meta name="date" content="1969-12-31T19:00:00-0500" />
-<meta name="keywords" content="geda,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/"; />
-<link rel="contents" href="http://geda.seul.org/wiki/geda:pcb?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:pcb"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:pcb"; />
-<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>
-</body>
-</html>
diff --git a/docs/wiki/geda_pcb_footprints.html b/docs/wiki/geda_pcb_footprints.html
deleted file mode 100644
index fde55c8..0000000
--- a/docs/wiki/geda_pcb_footprints.html
+++ /dev/null
@@ -1,102 +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>geda:pcb_footprints</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<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" />
-<link rel="start" href="http://geda.seul.org/wiki/"; />
-<link rel="contents" href="http://geda.seul.org/wiki/geda:pcb_footprints?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:pcb_footprints"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:pcb_footprints"; />
-<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="#pcb_footprint_guide" class="toc">PCB Footprint Guide</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#using_pcb_footprints" class="toc">Using PCB Footprints</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#creating_pcb_footprints" class="toc">Creating PCB Footprints</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#sharing_pcb_footprints" class="toc">Sharing PCB Footprints</a></span></div></li></ul>
-</li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="pcb_footprint_guide" id="pcb_footprint_guide">PCB Footprint Guide</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "PCB Footprint Guide" [3-37] -->
-<h2><a name="using_pcb_footprints" id="using_pcb_footprints">Using PCB Footprints</a></h2>
-<div class="level2">
-
-</div>
-<!-- SECTION "Using PCB Footprints" [38-70] -->
-<h2><a name="creating_pcb_footprints" id="creating_pcb_footprints">Creating PCB Footprints</a></h2>
-<div class="level2">
-
-</div>
-
-<h5><a name="what_are_some_references_for_making_surface_mount_pads_and_footprints" id="what_are_some_references_for_making_surface_mount_pads_and_footprints">What are some references for making surface mount pads and footprints?</a></h5>
-<div class="level5">
-<ul>
-<li class="level1"><div class="li"> <a href="http://www.nxp.com/package"; class="urlextern" title="http://www.nxp.com/package"; rel="nofollow">http://www.nxp.com/package</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://focus.ti.com/general/docs/packaging.jsp"; class="urlextern" title="http://focus.ti.com/general/docs/packaging.jsp"; rel="nofollow">http://focus.ti.com/general/docs/packaging.jsp</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://www.maxim-ic.com/design/packaging/"; class="urlextern" title="http://www.maxim-ic.com/design/packaging/"; rel="nofollow">http://www.maxim-ic.com/design/packaging/</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://www.national.com/packaging/folders/pkg_index.html"; class="urlextern" title="http://www.national.com/packaging/folders/pkg_index.html"; rel="nofollow">http://www.national.com/packaging/folders/pkg_index.html</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://www.irf.com/package/"; class="urlextern" title="http://www.irf.com/package/"; rel="nofollow">http://www.irf.com/package/</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://www.onsemi.com/PowerSolutions/supportTechDoc.do?id=1165"; class="urlextern" title="http://www.onsemi.com/PowerSolutions/supportTechDoc.do?id=1165"; rel="nofollow">http://www.onsemi.com/PowerSolutions/supportTechDoc.do?id=1165</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://www.analog.com/Analog_Root/Packages/Packages_Home/"; class="urlextern" title="http://www.analog.com/Analog_Root/Packages/Packages_Home/"; rel="nofollow">http://www.analog.com/Analog_Root/Packages/Packages_Home/</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://www.linear.com/designtools/PkgInfo.jsp"; class="urlextern" title="http://www.linear.com/designtools/PkgInfo.jsp"; rel="nofollow">http://www.linear.com/designtools/PkgInfo.jsp</a></div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Creating PCB Footprints" [71-585] -->
-<h2><a name="sharing_pcb_footprints" id="sharing_pcb_footprints">Sharing PCB Footprints</a></h2>
-<div class="level2">
-
-</div>
-
-<h5><a name="popular_sources_of_footprints" id="popular_sources_of_footprints">Popular Sources of Footprints</a></h5>
-<div class="level5">
-
-<p>
- * The place to share symbols and footprints is <a href="http://www.gedasymbols.org/"; class="urlextern" title="http://www.gedasymbols.org"; rel="nofollow"> gedasymbols.org</a>
-</p>
-
-<p>
-* You can find many PCB footprints at <a href="http://www.luciani.org/geda/pcb/pcb-footprint-list.html"; class="urlextern" title="http://www.luciani.org/geda/pcb/pcb-footprint-list.html"; rel="nofollow">John Luciani's footprint page</a>
-</p>
-
-<p>
-* You can share <a href="http://opencircuits.com/PCB_Footprints"; class="urlextern" title="http://opencircuits.com/PCB_Footprints"; rel="nofollow"> gEDA footprints at Open Circuits</a>.
-</p>
-
-</div>
-<!-- SECTION "Sharing PCB Footprints" [586-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/geda_pcb_mp.html b/docs/wiki/geda_pcb_mp.html
deleted file mode 100644
index 308d2dd..0000000
--- a/docs/wiki/geda_pcb_mp.html
+++ /dev/null
@@ -1,62 +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>geda:pcb_mp</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="keywords" content="geda,pcb_mp" />
-<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/geda:pcb_mp?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:pcb_mp"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:pcb_mp"; />
-<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">
-
-
-
-<h1><a name="pcb_man-page" id="pcb_man-page">PCB man-page</a></h1>
-<div class="level1">
-<pre class="code">PCB(1) PCB(1)
-
-
-
-NAME
- pcb - Printed circuit board layout tool
-
-
-SYNOPSIS
- pcb [options] [pcb file]
-
-
-DESCRIPTION
- The pcb program is a tool for the layout of printed circuit boards.
- The complete manual for pcb is provided in a GNU texinfo format as well
- as HTML and PDF. The texinfo version of the manual is typically viewed
- with the info program or alternatively with emacs or a graphical info
- viewer such as tkinfo /usr/local/share/pcb/pcb.html and
- /usr/local/share/pcb/pcb.pdf. The prefix "/usr/local" may vary at your
- site.
-
-
-
-
-
-
-
- PCB(1)</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_pcb_tips.html b/docs/wiki/geda_pcb_tips.html
deleted file mode 100644
index 2fe5838..0000000
--- a/docs/wiki/geda_pcb_tips.html
+++ /dev/null
@@ -1,1326 +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>geda:pcb_tips</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2008-06-20T14:10:59-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/"; />
-<link rel="contents" href="http://geda.seul.org/wiki/geda:pcb_tips?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:pcb_tips"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:pcb_tips"; />
-<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="#about_pcb_layout_and_routing" class="toc">About PCB layout and routing</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#what_s_a_footprint_what_s_a_via_what_s_a_track" class="toc">What's a footprint? What's a via? What's a track?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#what_s_this_business_about_flashed_pads" class="toc">What's this business about flashed pads?</a></span></div></li>
-</ul>
-</li>
-<li class="level1"><div class="li"><span class="li"><a href="#pcb_tools" class="toc">PCB Tools</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#where_can_i_read_about_the_basics_of_using_pcb" class="toc">Where can I read about the basics of using pcb?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#i_found_a_bug_what_can_i_do_about_it" class="toc">I found a bug! What can I do about it?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#how_can_i_set_the_manufacturing_rules_to_use_i.e._drill_diameters_trace_width_space_specs" class="toc">How can I set the manufacturing rules to use (i.e. drill diameters, trace width/space specs)?</a></span></div></li>
-</ul>
-</li>
-<li class="level1"><div class="li"><span class="li"><a href="#non-obvious_aspects_of_the_gui" class="toc">Non-obvious aspects of the GUI</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#auto-pan_bugs_me._what_can_i_do_about_it" class="toc">Auto-pan bugs me. What can I do about it?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#the_delete_key_sometimes_refuses_to_delete" class="toc">The delete key sometimes refuses to delete</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#i_try_to_move_an_object_but_pcb_won_t_let_me_what_can_i_do_about_it" class="toc">I try to move an object, but pcb won't let me! What can I do about it?</a></span></div></li>
-</ul>
-</li>
-<li class="level1"><div class="li"><span class="li"><a href="#footprint_issues" class="toc">Footprint issues</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#how_do_pcb_s_footprints_work" class="toc">How do PCB's footprints work?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#where_can_i_get_pre-drawn_footprints_for_pcb" class="toc">Where can I get pre-drawn footprints for PCB?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#i_want_to_use_pcb_to_do_layout._how_do_i_know_what_value_to_use_for_the_footprint_attribute" class="toc">I want to use PCB to do layout. How do I know what value to use for the footprint attribute?</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#newlib" class="toc">Newlib</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#m4_library" class="toc">M4 library</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#what_is_the_recommended_way_to_deal_with_different_footprints_for_the_same_sort_of_device" class="toc">What is the recommended way to deal with different footprints for the same sort of device?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_draw_a_new_footprint" class="toc">How do I draw a new footprint?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_edit_change_an_existing_footprint" class="toc">How do I edit/change an existing footprint?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_add_a_footprint_library_to_pcb" class="toc">How do I add a footprint library to PCB?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_update_a_footprint_in_my_layout" class="toc">How do I update a footprint in my layout?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#pcb_is_not_finding_my_footprints._why" class="toc">PCB is not finding my footprints. Why?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#now_that_i_have_all_of_these_footprints_where_do_i_put_them" class="toc">Now that I have all of these footprints where do I put them?</a></span></div></li>
-</ul>
-</li>
-<li class="level1"><div class="li"><span class="li"><a href="#component_placement" class="toc">Component placement</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_rotate_a_selection_i.e._of_more_than_one_item" class="toc">How do I rotate a selection (i.e. of more than one item)?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_change_the_size_of_a_graphical_object_such_as_text_silkscreen_lines_etc" class="toc">How do I change the size of a graphical object (such as text, silkscreen lines, etc)?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_put_components_on_both_faces_in_pcb" class="toc">How do I put components on both faces in PCB?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_define_a_silkscreen_layer_for_the_other_side_of_the_board" class="toc">How do I define a silkscreen layer for the other side of the board?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_set_the_origin_in_pcb" class="toc">How do I set the origin in pcb?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_measure_distances_and_dimensions_of_components" class="toc">How do I measure distances and dimensions of components?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_hide_rats_of_specific_nets" class="toc">How do I hide rats of specific nets?</a></span></div></li>
-</ul>
-</li>
-<li class="level1"><div class="li"><span class="li"><a href="#routing" class="toc">Routing</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_route_a_connection_from_solder_to_component_side_and_back" class="toc">How do I route a connection from solder to component side and back?</a></span></div></li>
-<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_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>
-<li class="level2"><div class="li"><span class="li"><a href="#i_want_to_draw_a_track_between_two_segments_on_the_same_net_but_pcb_won_t_let_me_why" class="toc">I want to draw a track between two segments on the same net, but PCB won't let me! Why?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#pcb_seems_to_munge_my_components_names_and_complains_that_it_can_t_find_proper_nets_for_the_pins_how_come" class="toc">PCB seems to munge my components names and complains that it can't find proper nets for the pins! How come?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#how_can_i_set_color_and_thickness_of_the_rats_nests" class="toc">How can I set color and thickness of the rats nests?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#where_is_that_last_remaining_rat" class="toc">Where is that last remaining rat?</a></span></div></li>
-</ul>
-</li>
-<li class="level1"><div class="li"><span class="li"><a href="#beyond_tracks_and_footprints" class="toc">Beyond tracks and footprints</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_trace_a_drawing_a_print_or_another_pcb" class="toc">How do I trace a drawing, a print, or another PCB?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#i_can_t_copy_component_pads_in_a_layout._what_gives" class="toc">I can't copy component pads in a layout. What gives?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_fill_areas_with_copper" class="toc">How do I fill areas with copper?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#how_can_i_assign_my_polygon_to_a_net" class="toc">How can I assign my polygon to a net?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#how_can_i_connect_tracks_pads_or_vias_to_my_polygon" class="toc">How can I connect tracks, pads, or vias to my polygon?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#the_polygons_are_shorting_my_tracks_what_can_i_do_about_it" class="toc">The polygons are shorting my tracks! What can I do about it?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_change_polygon_clearance" class="toc">How do I change polygon clearance?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_hide_the_polygons_while_i_edit_the_layout" class="toc">How do I hide the polygons while I edit the layout?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#polygons_are_making_the_gui_sluggish._what_i_can_do_about_it" class="toc">Polygons are making the GUI sluggish. What I can do about it?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#after_i_defined_those_ground_planes_pcb_takes_ages_to_load._how_come" class="toc">After I defined those ground planes, pcb takes ages to load. How come?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_edit_polygons" class="toc">How do I edit polygons?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_place_vias_that_connect_to_a_polygon_for_full_thermal_dissipation_or_full_shielding_integrity" class="toc">How do I place vias that connect to a polygon for full thermal dissipation or full shielding integrity?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#can_polygons_be_un-masked_can_a_polygon_be_made_bare-copper_with_no_solder_mask" class="toc">Can polygons be un-masked? (Can a polygon be made bare-copper with no solder mask?)</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_place_mounting_holes" class="toc">How do I place mounting holes?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#why_is_it_possible_to_make_a_thermal_for_pin_but_not_for_a_pad" class="toc">Why is it possible to make a thermal for pin, but not for a pad?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#can_pcb_be_used_to_make_single_layer_boards" class="toc">Can PCB be used to make single layer boards?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#what_resources_exist_to_process_pcb_files_using_scripts" class="toc">What resources exist to process PCB files using scripts?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_import_external_vector_graphics" class="toc">How do I import external vector graphics?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_attach_a_name_to_my_layout" class="toc">How Do I attach a name to my layout?</a></span></div></li>
-</ul>
-</li>
-<li class="level1"><div class="li"><span class="li"><a href="#auto_router" class="toc">Auto Router</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_force_the_autorouter_to_only_put_traces_on_a_particular_layer" class="toc">How do I force the autorouter to only put traces on a particular layer?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_make_autorouter_leave_particular_nets_alone" class="toc">How do I make autorouter leave particular nets alone?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_force_the_autorouter_to_route_only_within_my_pcb_outline" class="toc">How do I force the autorouter to route only within my pcb outline?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_route_power_and_ground_planes_with_the_autorouter" class="toc">How do I route power and ground planes with the autorouter?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#the_layout_produced_by_the_autorouter_is_inefficient" class="toc">The layout produced by the autorouter is inefficient!</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#the_layout_produced_by_the_autorouter_is_ugly" class="toc">The layout produced by the autorouter is ugly!</a></span></div></li>
-</ul>
-</li>
-<li class="level1"><div class="li"><span class="li"><a href="#gerber_generation_and_file_i_o_issues" class="toc">Gerber generation and file I/O issues</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_make_a_board_outline_to_go_with_my_gerbers_to_the_board_maker" class="toc">How do I make a board outline to go with my gerbers to the board maker?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#yes_i_tried_that_but_the_gerber_exporter_didn_t_give_me_an_outline_file._why" class="toc">Yes, I tried that, but the gerber exporter didn't give me an outline file. Why?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#i_m_done_with_my_layout._how_should_i_check_my_design" class="toc">I'm done with my layout. How should I check my design?</a></span></div></li>
-</ul>
-</li>
-<li class="level1"><div class="li"><span class="li"><a href="#exporting_other_formatsraster_and_ps_files" class="toc">Exporting Other Formats: Raster and PS Files</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#what_is_xy-max_in_the_png_export_dialog_box" class="toc">What is xy-max in the PNG export dialog box?</a></span></div></li>
-</ul>
-</li>
-<li class="level1"><div class="li"><span class="li"><a href="#customization" class="toc">Customization</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#i_don_t_like_that_old-style_black_backgropund._how_can_i_get_a_light_canvas" class="toc">I don't like that old-style black backgropund. How can I get a light canvas?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_set_the_default_values_of_the_postscript_dialog" class="toc">How do I set the default values of the postscript dialog?</a></span></div></li>
-</ul>
-</li>
-<li class="level1"><div class="li"><span class="li"><a href="#you_didn_t_answer_my_question._what_other_resources_exist_for_pcb_information" class="toc">You didn't answer my question. What other resources exist for PCB information?</a></span></div></li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="about_pcb_layout_and_routing" id="about_pcb_layout_and_routing">About PCB layout and routing</a></h1>
-<div class="level1">
-
-<p>
-This section answers general questions about PCB technology. If youâ??re just beginning to learn about electronics, you might benefit from some of the answers given here.
-</p>
-
-</div>
-<!-- SECTION "About PCB layout and routing" [1-215] -->
-<h2><a name="what_s_a_footprint_what_s_a_via_what_s_a_track" id="what_s_a_footprint_what_s_a_via_what_s_a_track">What's a footprint? What's a via? What's a track?</a></h2>
-<div class="level2">
-
-<p>
-You can find a glossary of terms <a href="http://geda.seul.org/wiki/geda:glossary"; class="urlextern" title="http://geda.seul.org/wiki/geda:glossary"; rel="nofollow">here</a>.
-</p>
-
-</div>
-<!-- SECTION "What's a footprint? What's a via? What's a track?" [216-361] -->
-<h2><a name="what_s_this_business_about_flashed_pads" id="what_s_this_business_about_flashed_pads">What's this business about flashed pads?</a></h2>
-<div class="level2">
-
-<p>
-Pads may be â??flashedâ?? as opposed to â??drawnâ??. In the old days, the photo plotters had a big wheel with holes called apertures cut in it. The machine would turn the wheel to pick the correct aperture, position the film at the right place relative to the aperture and turn on a light that would shine through the aperture and expose the photo sensitive film behind. A â??flashedâ?? pad means that the pad shape and size exactly matched one of the apertures and to make a pad, youâ??d position the aperture over the pad location and flash the light (like a camera flash). A â??drawnâ?? pad by contrast is one where youâ??d use a small aperture, position it, turn on the light and then draw back and forth until you drew your pad shape. Think of this like taking a marker and coloring in a pad.
-</p>
-
-<p>
-Since these aperture wheels were physical things that had to be made, companies would typically have a set aperture list that theyâ??d use for everything so they wouldnâ??t have to buy a new aperture wheel every time they ordered boards. This is why the older RS274-D (â??gerberâ??) files did not include the aperture list but instead there would be a single aperture file that got used over and over.
-</p>
-
-<p>
-Now the plotters I believe are all laser plotters and the concept of flashed vs drawn doesnâ??t have much bearing on exactly what happens mechanically during photo plotting. Also, there is no problem with changing aperture lists all the time. This is part of why the newer RS274-X format with embedded aperture definitions exists. Still, youâ??ll see in RS274-X files that some pads are in fact specified as flashed vs drawn.
-</p>
-
-</div>
-<!-- SECTION "What's this business about flashed pads?" [362-2022] -->
-<h1><a name="pcb_tools" id="pcb_tools">PCB Tools</a></h1>
-<div class="level1">
-
-<p>
-This section provides answers about the open-source layout tool â??PCBâ?? itself.
-</p>
-
-</div>
-<!-- SECTION "PCB Tools" [2023-2125] -->
-<h2><a name="where_can_i_read_about_the_basics_of_using_pcb" id="where_can_i_read_about_the_basics_of_using_pcb">Where can I read about the basics of using pcb?</a></h2>
-<div class="level2">
-
-<p>
-The <a href="http://pcb.sourceforge.net/manual.html"; class="urlextern" title="http://pcb.sourceforge.net/manual.html"; rel="nofollow">pcb manual</a> contains a concise description of the user interface in the section â??Getting Startedâ??(<a href="http://pcb.sourceforge.net/pcb-20060822/pcb.html#Getting%20Started"; class="urlextern" title="http://pcb.sourceforge.net/pcb-20060822/pcb.html#Getting%20Started"; rel="nofollow">version 20060822</a>)
-</p>
-
-</div>
-<!-- SECTION "Where can I read about the basics of using pcb?" [2126-2423] -->
-<h2><a name="i_found_a_bug_what_can_i_do_about_it" id="i_found_a_bug_what_can_i_do_about_it">I found a bug! What can I do about it?</a></h2>
-<div class="level2">
-<ol>
-<li class="level1"><div class="li"> Start by reading <a href="http://pcb.sourceforge.net/bugs.html"; class="urlextern" title="http://pcb.sourceforge.net/bugs.html"; rel="nofollow">the pcb bug reporting page</a>.</div>
-</li>
-<li class="level1"><div class="li"> Check, what it needs to reproduce the bug.</div>
-</li>
-<li class="level1"><div class="li"> Ask on the <a href="http://www.geda.seul.org/mailinglist/index.html"; class="urlextern" title="http://www.geda.seul.org/mailinglist/index.html"; rel="nofollow">geda-user mailing</a> list if there is a work around, or has been dealt with in the bleading edge version of pcb. Note that you must subscribe to the geda-user e-mail list before you can post to this list.</div>
-</li>
-<li class="level1"><div class="li"> Check, wether the issue is already in the <a href="http://sourceforge.net/tracker/?group_id=73743&atid=538811"; class="urlextern" title="http://sourceforge.net/tracker/?group_id=73743&atid=538811"; rel="nofollow">bug tracking system of pcb</a>. If not, file a bug report. Make sure to give every information necessary to reproduce the bug and add the version of pcb that contains the bug.</div>
-</li>
-<li class="level1"><div class="li"> Finally, as with all open source projects, you may flex your programming muscles and try to squish the bug yourself. Please file a patch of the changes you had to make to the <a href="http://sourceforge.net/tracker/?group_id=73743&atid=538811"; class="urlextern" title="http://sourceforge.net/tracker/?group_id=73743&atid=538811"; rel="nofollow">BTS of pcb</a>. The patch will be gladly accepted to improve the next release of pcb.</div>
-</li>
-</ol>
-
-</div>
-<!-- SECTION "I found a bug! What can I do about it?" [2424-3486] -->
-<h2><a name="how_can_i_set_the_manufacturing_rules_to_use_i.e._drill_diameters_trace_width_space_specs" id="how_can_i_set_the_manufacturing_rules_to_use_i.e._drill_diameters_trace_width_space_specs">How can I set the manufacturing rules to use (i.e. drill diameters, trace width/space specs)?</a></h2>
-<div class="level2">
-
-<p>
-This topic is covered <a href="http://pcb.sourceforge.net/pcb-20060422/pcb.html#Vendor%20drill%20mapping"; class="urlextern" title="http://pcb.sourceforge.net/pcb-20060422/pcb.html#Vendor%20drill%20mapping"; rel="nofollow">in the documentation available at the PCB website</a>.
-</p>
-
-</div>
-<!-- SECTION "How can I set the manufacturing rules to use (i.e. drill diameters, trace width/space specs)?" [3487-3744] -->
-<h1><a name="non-obvious_aspects_of_the_gui" id="non-obvious_aspects_of_the_gui">Non-obvious aspects of the GUI</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "Non-obvious aspects of the GUI" [3745-3790] -->
-<h2><a name="auto-pan_bugs_me._what_can_i_do_about_it" id="auto-pan_bugs_me._what_can_i_do_about_it">Auto-pan bugs me. What can I do about it?</a></h2>
-<div class="level2">
-<ul>
-<li class="level1"><div class="li"> You can tell, whether the screen will auto-pan by looking for little squares at the end of the cross hair cursor.</div>
-</li>
-<li class="level1"><div class="li"> Auto-pan can be toggled during move with a right mouse button click.</div>
-</li>
-<li class="level1"><div class="li"> Auto-pan speed can be set in <code>$HOME/.pcb/preferences</code> </div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Auto-pan bugs me. What can I do about it?" [3791-4098] -->
-<h2><a name="the_delete_key_sometimes_refuses_to_delete" id="the_delete_key_sometimes_refuses_to_delete">The delete key sometimes refuses to delete</a></h2>
-<div class="level2">
-
-<p>
-Probably you try to delete a selected object. In pcb the delete button does not act on the selection, but on the object currently under the mouse. Consequently nothing will be deleted if an object is selected and the mouse hovers at some other place. Bottom line: Just position the mouse over an object and press the delete button. No need to select the object.
-</p>
-
-<p>
-However, the Select menu contains an action that lets you delete the current selection. Currently, there is no accel key attached to this action.
-</p>
-
-<p>
-Note, for versions younger than summer 2007 this issue is resolved. The delete key acts on selected objects too.
-</p>
-
-</div>
-<!-- SECTION "The delete key sometimes refuses to delete" [4099-4777] -->
-<h2><a name="i_try_to_move_an_object_but_pcb_won_t_let_me_what_can_i_do_about_it" id="i_try_to_move_an_object_but_pcb_won_t_let_me_what_can_i_do_about_it">I try to move an object, but pcb won't let me! What can I do about it?</a></h2>
-<div class="level2">
-
-<p>
-Most probably the object is locked. To see, wether it indeeed is, select-all-connected-objects from the select menu. Locked objects wonâ??t highlight. Use the lock tool to unlock the object in question. Note, that the lock tool always toggles the lock state of the object you click at. Afterwards an n object report pops up that contains the lock state in the last line.
-</p>
-
-<p>
-If you want to remove all locks, you may consider to remove all occurences of the string <em>lock</em> in the *.pcb file with your favorite ascii editor.
-</p>
-
-</div>
-<!-- SECTION "I try to move an object, but pcb won't let me! What can I do about it?" [4778-5383] -->
-<h1><a name="footprint_issues" id="footprint_issues">Footprint issues</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "Footprint issues" [5384-5415] -->
-<h2><a name="how_do_pcb_s_footprints_work" id="how_do_pcb_s_footprints_work">How do PCB's footprints work?</a></h2>
-<div class="level2">
-
-<p>
-PCB supports two entirely separate footprint library mechanisms:
-</p>
-<ol>
-<li class="level1"><div class="li"> The first is referred to as the â??oldlibâ??, â??pcblibâ??, or the â??M4 libraryâ??. This system uses the macro language M4 to generate footprints on the fly. The M4 library is fairly large. A powerful feature of the m4 library is that an entire family of footprints can quickly be defined by defining an appropriate base macro. Several standard families of footprints exist in pcblib. Starting with the pcb-20070208 snapshot, the entire m4 library is available as â??newlibâ?? footprints (see the following paragraph) under the name â??pcblib-newlibâ??.</div>
-</li>
-<li class="level1"><div class="li"> The second footprint library for PCB is called the â??newlibâ??. Newlib footprints are defined using <acronym title="American Standard Code for Information Interchange">ASCII</acronym> text files which call out each graphical primitive which makes up an entire footprint. Newlib footprints can either be created graphically using PCB or via any other method which can produce a text file (text editor, awk/perl/ruby script, etc.). The use of a scripting or programming language is especially powerful because you can generate large footprints or families of footprints.</div>
-</li>
-</ol>
-
-<p>
- Therefore, during layout, you can use footprints which are distributed with PCB, you can find footprints via a web search, or you can create your own, and put them in a dedicated directory. The <a href="http://pcb.sourceforge.net/manual.html"; class="urlextern" title="http://pcb.sourceforge.net/manual.html"; rel="nofollow">pcb manual</a> has complete and up to date documentation for the element file format. <a href="http://gedasymbols.org/"; class="urlextern" title="http://gedasymbols.org"; rel="nofollow">Gedasymbols.org</a> has a number of user contributed footprints. A somewhat incomplete but useful tutorial is available on the web at: <a href="http://www.brorson.com/gEDA/"; class="urlextern" title="http://www.brorson.com/gEDA/"; rel="nofollow">http://www.brorson.com/gEDA/</a> (search for the term â??newlibâ??).
-</p>
-
-</div>
-<!-- SECTION "How do PCB's footprints work?" [5416-7120] -->
-<h2><a name="where_can_i_get_pre-drawn_footprints_for_pcb" id="where_can_i_get_pre-drawn_footprints_for_pcb">Where can I get pre-drawn footprints for PCB?</a></h2>
-<div class="level2">
-
-<p>
-Currently, the best place to get footprints (besides in the PCB distribution) is the <a href="http://www.gedasymbols.org/"; class="urlextern" title="http://www.gedasymbols.org"; rel="nofollow">gEDA Symbols website</a>. <a href="http://www.luciani.org/geda/pcb/pcb-footprint-list.html"; class="urlextern" title="http://www.luciani.org/geda/pcb/pcb-footprint-list.html"; rel="nofollow">John Luciani's website</a> has a large number of footprints and tools. Also, Darrell Harmon provides a nice footprint generating script <a href="http://www.dlharmon.com/geda/footgen.html"; class="urlextern" title="http://www.dlharmon.com/geda/footgen.html"; rel="nofollow">on his website</a>. You are welcome to contribute to the project and share your footprints. Finally, you can ask on the geda-user list, and somebody might take pity on you and send you a symbol. Note that you must subscribe to the geda-user e-mail list before you can post an e-mail to the geda-user list.
-</p>
-
-</div>
-<!-- SECTION "Where can I get pre-drawn footprints for PCB?" [7121-7859] -->
-<h2><a name="i_want_to_use_pcb_to_do_layout._how_do_i_know_what_value_to_use_for_the_footprint_attribute" id="i_want_to_use_pcb_to_do_layout._how_do_i_know_what_value_to_use_for_the_footprint_attribute">I want to use PCB to do layout. How do I know what value to use for the footprint attribute?</a></h2>
-<div class="level2">
-
-<p>
-This question is a common one amongst new gEDA users. Indeed, helping newbies determine the appropriate footprint names lies at the core of the ongoing <a href="http://geda.seul.org/wiki/geda:faq-gschem#what_s_this_business_about_heavy_vs._light_symbols"; class="wikilink1" title="geda:faq-gschem">light vs. heavy symbol</a> debate. In the current, light symbol gEDA/gaf distribution, you need to attach the footprint attribute at the schematic level (i.e. using either gschem or gattrib). The name of the footprint to use depends upon whether you are using the newlib or the M4 library (pcblib).
-</p>
-
-</div>
-<!-- SECTION "I want to use PCB to do layout. How do I know what value to use for the footprint attribute?" [7860-8483] -->
-<h3><a name="newlib" id="newlib">Newlib</a></h3>
-<div class="level3">
-
-<p>
-The newlib stores one footprint per file, and the footprint names used by the newlib are the file names of the footprint files.
-</p>
-
-<p>
-There are several ways to determine the newlib footprint names to use:
-</p>
-<ul>
-<li class="level1"><div class="li"> You can browse the available footprints by running pcb and opening the footprint library window (available from the menu bar via â??Window â?? libraryâ??). Click on the â??newlibâ?? library group, and then select a sublibrary to browse its symbols. The name of each footprint appears in the â??Elementsâ?? window on the right hand side of the footprint library browser. Use the name exactly as it appears in the browser for the footprint attribute in gschem or gattrib.</div>
-</li>
-<li class="level1"><div class="li"> The newlib footprints distributed with PCB are stored in the directories under <strong><code>${PREFIX}/share/pcb/newlib</code></strong>. (<strong><code>${PREFIX}</code></strong> is the install directory you specified when configuring/building PCB.) The name to stick in the â??footprintâ?? attribute is the filename of the footprint you wish to use.<br/>
- For example, on my machine I installed gEDA with the prefix <strong><code>/usr/local/geda/</code></strong>. The 0805 package (for SMT resistors or caps) lives in a file with absolute path<br/>
- <strong><code>/usr/local/geda/share/pcb/newlib/generic_SMD_packages/0805_reflow_solder</code></strong> <br/>
- Therefore, to use this footprint on a component I set its â??footprintâ?? attribute to <strong><code>0805_reflow_solder</code></strong> using gschem or gattrib.<br/>
- Note that if the newlib symbol you want to use lives in a non-standard directory, gsch2pcb needs you to specify a path to that directory, either within your project.rc file (if you use one) or using the <strong><code>â??elements-dir</code></strong> flag (from the command line).</div>
-</li>
-<li class="level1"><div class="li"> Finally, since each new design typically requires you to draw at least a couple of new footprints, itâ??s likely you will have a local â??footprintsâ?? directory. As previously, the footprint name to use is the filename you assign to each of your new footprints. Again, donâ??t forget to add a line to your project.rc file telling gsch2pcb where to find your local footprints. Alternately, you can run gsch2pcb with the <strong><code>â??elements-dir</code></strong> flag set to point to your local footprint directory.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Newlib" [8484-10638] -->
-<h3><a name="m4_library" id="m4_library">M4 library</a></h3>
-<div class="level3">
-
-<p>
-The M4 library stores the footprints as M4 macros; there are usually several (many) footprints contained in each footprint file. The different footprints in a single file are generally variations on a single pattern (e.g. DIP-8, DIP-14, DIP-16, etc.) The easiest way to find the correct footprint attribute name is by browsing through the â??pcblibâ?? library in the PCB library window. The footprint attribute is given in square brackets in the description. Also you can view the list of footprints from pcblib at the <a href="http://www.gedasymbols.org/footprints/"; class="urlextern" title="http://www.gedasymbols.org/footprints/"; rel="nofollow">gEDA Symbols webpage</a>.
-</p>
-
-<p>
-The following m4 libraries have received more attention and improvements than the others:
-</p>
-<ul>
-<li class="level1"><div class="li"> ~amp for Amp connectors</div>
-</li>
-<li class="level1"><div class="li"> ~amphenol for Amphenol connectors</div>
-</li>
-<li class="level1"><div class="li"> ~geda for many diverse parts used in basic design using gEDA (resistors, caps, etc).</div>
-</li>
-<li class="level1"><div class="li"> ~bourns for products like trim pots from Bourns</div>
-</li>
-<li class="level1"><div class="li"> ~cts for products like resistor packs from CTS</div>
-</li>
-<li class="level1"><div class="li"> ~johnstech for Johnstech sockets</div>
-</li>
-<li class="level1"><div class="li"> ~minicircuits for Minicircuits specific footprints</div>
-</li>
-<li class="level1"><div class="li"> ~panasonic for some Panasonic specific footprints</div>
-</li>
-</ul>
-
-<p>
- Finally, for both the newlib and the M4 lib, it is extremely important that you verify that the footprint name you use instantiates *exactly* the footprint you want when you place it in PCB. Therefore, it is critical to inspect the footprint before you use it. You can verify the footprint you want to use by clicking on it in the â??footprint libraryâ?? window, and then placing it onto an empty spot in PCBâ??s drawing area. Manually inspect the footprint to ensure that it has the correct number of pins/pads, correct dimensions, etc.
-</p>
-
-<p>
-Also, once you generate Gerber files, make sure you <span class="curid"><a href="http://geda.seul.org/wiki/geda:pcb_tips#i_m_done_with_my_layout._how_should_i_check_my_design"; class="wikilink1" title="geda:pcb_tips">inspect all footprints instantiated in your Gerbers</a></span> using gerbv (or an equivalent Gerber viewer) before you send your design out for fabrication.
-</p>
-
-</div>
-<!-- SECTION "M4 library" [10639-12548] -->
-<h2><a name="what_is_the_recommended_way_to_deal_with_different_footprints_for_the_same_sort_of_device" id="what_is_the_recommended_way_to_deal_with_different_footprints_for_the_same_sort_of_device">What is the recommended way to deal with different footprints for the same sort of device?</a></h2>
-<div class="level2">
-
-<p>
-For example, an opamp may be DIP8 or SO8. A resistor may be 0603, 0805, 1208, or through-hole. How do I know what package and footprint to use, and how do I manage the choices?
-</p>
-
-<p>
-First off, the footprint you should use is a decision for you to make, not your CAD tool. It is up to you to choose your preferred package type/footprint, and then attach the correct footprint attribute to the component in the schematic. Once you have choosen which package (and footprint) you wish to use, then either <span class="curid"><a href="http://geda.seul.org/wiki/geda:pcb_tips#where_can_i_get_pre-drawn_footprints_for_pcb"; class="wikilink1" title="geda:pcb_tips">find an appropriate footprint</a></span>, or <span class="curid"><a href="http://geda.seul.org/wiki/geda:pcb_tips#how_do_i_draw_a_new_footprint"; class="wikilink1" title="geda:pcb_tips">draw one yourself</a></span> and save it in a local directory.
-</p>
-
-<p>
-As far as managing the footprint choices (and indeed the large number of component attributes you are likely to have): Use <a href="http://geda.seul.org/wiki/geda:faq-attribs#help_my_design_has_hundreds_of_components_and_it_s_a_pain_to_use_gschem_to_attach_all_my_attributes"; class="wikilink1" title="geda:faq-attribs">gattrib</a>. Thatâ??s what itâ??s for.
-</p>
-
-</div>
-<!-- SECTION "What is the recommended way to deal with different footprints for the same sort of device?" [12549-13626] -->
-<h2><a name="how_do_i_draw_a_new_footprint" id="how_do_i_draw_a_new_footprint">How do I draw a new footprint?</a></h2>
-<div class="level2">
-
-<p>
-Everybody does this a little differently. Some people draw the footprint entirely using PCB. Some people first draw a preliminary footprint in PCB, and then finish it off by hand editing it (e.g. using emacs). Some people write <acronym title="Practical Extraction and Report Language">Perl</acronym> or Python scripts to autogenerate footprints.
-</p>
-<ul>
-<li class="level1"><div class="li"> text editor: safe and efficient way to create most footprints. <a href="http://www.brorson.com/gEDA/land_patterns_20050129.pdf"; class="urlextern" title="http://www.brorson.com/gEDA/land_patterns_20050129.pdf"; rel="nofollow"> THE manual on footprint creation</a></div>
-</li>
-<li class="level1"><div class="li"> draw the part in PCB and convert to a footprint: <acronym title="What You See Is What You Get">WYSIWYG</acronym>. <a href="http://ronja.twibright.com/guidelines/footprints.php"; class="urlextern" title="http://ronja.twibright.com/guidelines/footprints.php"; rel="nofollow">how Karel Kulhavy does it this way</a></div>
-</li>
-<li class="level1"><div class="li"> use either the perl script <a href="http://www.luciani.org/geda/pcb/pcb-perl-library.html"; class="urlextern" title="http://www.luciani.org/geda/pcb/pcb-perl-library.html"; rel="nofollow">from John Luciani</a> or the python script <a href="http://dlharmon.com/geda/footgen.html"; class="urlextern" title="http://dlharmon.com/geda/footgen.html"; rel="nofollow"> by Darrel Harmon</a></div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "How do I draw a new footprint?" [13627-14454] -->
-<h2><a name="how_do_i_edit_change_an_existing_footprint" id="how_do_i_edit_change_an_existing_footprint">How do I edit/change an existing footprint?</a></h2>
-<div class="level2">
-
-<p>
-You can convert a footprint into a ordinary layout, edit the parts and convert them back to footprint. In the following list the parts in mono space font are actions from the buffer menu.
-</p>
-<ol>
-<li class="level1"><div class="li"> Select element</div>
-</li>
-<li class="level1"><div class="li"> Copy selection to buffer</div>
-</li>
-<li class="level1"><div class="li"> <code>Break buffer into pieces</code></div>
-</li>
-<li class="level1"><div class="li"> <code>Paste buffer to layout</code></div>
-</li>
-<li class="level1"><div class="li"> Do the desired changes</div>
-</li>
-<li class="level1"><div class="li"> Select all objects that belong to the footprint</div>
-</li>
-<li class="level1"><div class="li"> <code>Copy selection to buffer</code></div>
-</li>
-<li class="level1"><div class="li"> <code>Convert buffer to element</code></div>
-</li>
-<li class="level1"><div class="li"> <code>Paste buffer to layout</code></div>
-</li>
-<li class="level1"><div class="li"> Place the mouse over the pads that got rounded during step 4 and press q. This squares off the rounded pad edges.</div>
-</li>
-<li class="level1"><div class="li"> Go over every pad, press n and give a name to the pad</div>
-</li>
-<li class="level1"><div class="li"> Select everything and <code>copy selection to buffer</code></div>
-</li>
-<li class="level1"><div class="li"> <code>Save buffer as elements to file</code>. The footprint file will created at the path where pcb was called.</div>
-</li>
-</ol>
-
-<p>
-Alternatively, you can use your favorite text editor and edit the source code of the footprint.
-</p>
-
-</div>
-<!-- SECTION "How do I edit/change an existing footprint?" [14455-15422] -->
-<h2><a name="how_do_i_add_a_footprint_library_to_pcb" id="how_do_i_add_a_footprint_library_to_pcb">How do I add a footprint library to PCB?</a></h2>
-<div class="level2">
-
-<p>
-Adding footprint libraries can be done from the <acronym title="Graphical User Interface">GUI</acronym>:<br/>
- <strong><em>File</em></strong> â??> <strong><em>Preferences</em></strong> â??> <strong><em>Library</em></strong> â??> <strong>FOOTPRINTDIRECTORY</strong><br/>
- Alternatively you can edit the file <code>$HOME/.pcb/preferences</code>. Make sure, no instance of pcb is currently running. Look for the line that starts with â??library-newlibâ??. Donâ??t forget to include the new directory into either your gsch2pcbrc, or your local gafrc file (if you are using gsch2pcb, that is).
-</p>
-
-</div>
-<!-- SECTION "How do I add a footprint library to PCB?" [15423-15928] -->
-<h2><a name="how_do_i_update_a_footprint_in_my_layout" id="how_do_i_update_a_footprint_in_my_layout">How do I update a footprint in my layout?</a></h2>
-<div class="level2">
-
-<p>
-There is no way to automatically replace all instances of a footprint with the new version, yet. But there is a special mode of the buffer-paste tool, that will reduce the amount of clicks for manual replacement.<br/>
- Use the Window→Library dialog box to manually choose the new footprint. The tool becomes the buffer-paste tool, with the new footprint preloaded. Rotate it if needed with Buffer→Rotate Buffer. Position the new footprint over the old one, and shift-left-mouse-click to replace the old footprint with the new one. Watch out for being 180 degrees off, use â??oâ?? to check the rats nest after each placement, and undo if it appears you placed it backwards.
-</p>
-
-</div>
-<!-- SECTION "How do I update a footprint in my layout?" [15929-16651] -->
-<h2><a name="pcb_is_not_finding_my_footprints._why" id="pcb_is_not_finding_my_footprints._why">PCB is not finding my footprints. Why?</a></h2>
-<div class="level2">
-
-<p>
-The footprint path that PCB uses is defined using the <strong><code>Pcb.elementPath</code></strong> variable in the app-defaults file named <strong><code>PCB</code></strong>. The path for the <strong><code>PCB</code></strong> file is set using the <strong><code>XAPPLRESDIR</code></strong> environment variable which is typically set from within the wrapper script named <strong><code>pcb</code></strong>.
-</p>
-
-</div>
-<!-- SECTION "PCB is not finding my footprints. Why?" [16652-16999] -->
-<h2><a name="now_that_i_have_all_of_these_footprints_where_do_i_put_them" id="now_that_i_have_all_of_these_footprints_where_do_i_put_them">Now that I have all of these footprints where do I put them?</a></h2>
-<div class="level2">
-
-<p>
-I prefer to place all â??production-readyâ?? footprints in a single directory that is not in the gEDA/PCB install tree. When a new version of gEDA/PCB comes out I do not make any changes to project files or libraries. If there are newlib footprints in the PCB library that I want to use I copy them to the â??production-readyâ?? footprint directory.
-</p>
-
-<p>
-Rather than change configuration files to get gsch2pcb to find the footprints I create a wrapper script called <strong><code>sch2pcb</code></strong> that contains the footprint path. All users use the same script and access the same production footprints.
-</p>
-
-<p>
-To use the <strong><code>sch2pcb</code></strong> script that is listed below replace the string <strong><code>FOOTPRINT_DIR</code></strong> with your footprint directory:
-</p>
-<pre class="code">
-#!/bin/bash
-gsch2pcb --elements-dir FOOTPRINT_DIR $@
-</pre>
-
-<p>
-Or another userâ??s version:
-</p>
-<pre class="code">
-#!/bin/bash
-#this script was written by John Luciani
-gsch2pcb --elements-dir /home/user/pcb/footprints/user --use-files $@
-</pre>
-
-</div>
-<!-- SECTION "Now that I have all of these footprints where do I put them?" [17000-18016] -->
-<h1><a name="component_placement" id="component_placement">Component placement</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "Component placement" [18017-18051] -->
-<h2><a name="how_do_i_rotate_a_selection_i.e._of_more_than_one_item" id="how_do_i_rotate_a_selection_i.e._of_more_than_one_item">How do I rotate a selection (i.e. of more than one item)?</a></h2>
-<div class="level2">
-<ol>
-<li class="level1"><div class="li"> Select the items</div>
-</li>
-<li class="level1"><div class="li"> Buffer â?? Cut selection to buffer</div>
-</li>
-<li class="level1"><div class="li"> Buffer â?? Rotate buffer 90 deg CCW (or CW)</div>
-</li>
-<li class="level1"><div class="li"> Click anywhere on the board and the selection is pasted on the design again.</div>
-</li>
-</ol>
-
-</div>
-<!-- SECTION "How do I rotate a selection (i.e. of more than one item)?" [18052-18311] -->
-<h2><a name="how_do_i_change_the_size_of_a_graphical_object_such_as_text_silkscreen_lines_etc" id="how_do_i_change_the_size_of_a_graphical_object_such_as_text_silkscreen_lines_etc">How do I change the size of a graphical object (such as text, silkscreen lines, etc)?</a></h2>
-<div class="level2">
-<ul>
-<li class="level1"><div class="li"> Mouse over the object and hit [<strong><code>s</code></strong>]. This will increase the size of the object you are mousing over.</div>
-</li>
-<li class="level1"><div class="li"> Mouse over the object and hit [<strong><code><shift>-S</code></strong>]. This will decrease the size of the object you are mousing over.</div>
-</li>
-</ul>
-
-<p>
- You can alter the increase/decrease quantum using the <strong><em>file</em></strong> â?? <strong><em>preferences</em></strong> â?? <strong><em>increments</em></strong> menu.
-</p>
-
-</div>
-<!-- SECTION "How do I change the size of a graphical object (such as text, silkscreen lines, etc)?" [18312-18762] -->
-<h2><a name="how_do_i_put_components_on_both_faces_in_pcb" id="how_do_i_put_components_on_both_faces_in_pcb">How do I put components on both faces in PCB?</a></h2>
-<div class="level2">
-
-<p>
-There are two ways to do it:
-</p>
-<ul>
-<li class="level1"><div class="li"> Pressing the tab key will alternate the active side between the component and solder sides. When you place components, they will go on the active side.</div>
-</li>
-<li class="level1"><div class="li"> If you are viewing one side of the board, place a component there and (with the cursor over it) press the [<strong><code>b</code></strong>] key (wich means, send the component to the Back side) the component go to the other side of the board.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "How do I put components on both faces in PCB?" [18763-19231] -->
-<h2><a name="how_do_i_define_a_silkscreen_layer_for_the_other_side_of_the_board" id="how_do_i_define_a_silkscreen_layer_for_the_other_side_of_the_board">How do I define a silkscreen layer for the other side of the board?</a></h2>
-<div class="level2">
-
-<p>
-Although only one silk layer button is visible in the <acronym title="Graphical User Interface">GUI</acronym>, silkscreen for both sides is automatically configured. In default view the silk layer button refers to silkscreen on the component side of the board. To place text or lines on solder silk you have to flip the board with the tab key (or shift-tab if you prefer a left-right flip). This is like physically turning the board to the other side. It turns the solder layer on top, and component layer on bottom. Objects on component silk layer will be greyed out. If you draw to silk, lines will always go to the current top silk layer, which is solder now. The same happens to components and their silk screen. Flip the board again to return to default view.
-</p>
-
-</div>
-<!-- SECTION "How do I define a silkscreen layer for the other side of the board?" [19232-20025] -->
-<h2><a name="how_do_i_set_the_origin_in_pcb" id="how_do_i_set_the_origin_in_pcb">How do I set the origin in pcb?</a></h2>
-<div class="level2">
-
-<p>
-The absolute origin is always in the upper left corner of the accessible area. This cannot be set to some other place. However, coordinates of objects can also be given relative to the current grid. In the GTK2 version of pcb coordinates are shown in the upper right corner of the main window. The right pair is the absolute position, while the left pair reflects the position relative to an arbitrary marker. This marker is set to the current position of the mouse by the key sequence [<strong><code>ctrl-m</code></strong>]. You may want to set the marker to a grid point or a specific pin.
-</p>
-
-</div>
-<!-- SECTION "How do I set the origin in pcb?" [20026-20640] -->
-<h2><a name="how_do_i_measure_distances_and_dimensions_of_components" id="how_do_i_measure_distances_and_dimensions_of_components">How do I measure distances and dimensions of components?</a></h2>
-<div class="level2">
-
-<p>
-Use [<strong><code>ctrl-m</code></strong>] to set the origin and read the distance of the mouse pointer relative to this point on the upper left of the pcb window. Some objects like vias and tracks yield usefull information in object reports. Access the report of the object currently under the mouse pointer with [<strong><code>ctrl-r</code></strong>].
-</p>
-
-</div>
-<!-- SECTION "How do I measure distances and dimensions of components?" [20641-21020] -->
-<h2><a name="how_do_i_hide_rats_of_specific_nets" id="how_do_i_hide_rats_of_specific_nets">How do I hide rats of specific nets?</a></h2>
-<div class="level2">
-
-<p>
-In the netlist window, doubleclick on the specific rat name, then press â??oâ?? on your board window. Your rats are hidden for that net. In the Netlist window an asterisk appears in from of the rat name. To reverse: follow the same procedure.
-</p>
-
-</div>
-<!-- SECTION "How do I hide rats of specific nets?" [21021-21309] -->
-<h1><a name="routing" id="routing">Routing</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "Routing" [21310-21331] -->
-<h2><a name="how_do_i_route_a_connection_from_solder_to_component_side_and_back" id="how_do_i_route_a_connection_from_solder_to_component_side_and_back">How do I route a connection from solder to component side and back?</a></h2>
-<div class="level2">
-
-<p>
-While using the line tool, use the number keys on top of the keyboard to switch layers. A via will be placed automatically at the endpoint of the last complete segment.
-</p>
-
-</div>
-<!-- SECTION "How do I route a connection from solder to component side and back?" [21332-21582] -->
-<h2><a name="how_do_i_change_the_routing_style" id="how_do_i_change_the_routing_style">How do I change the routing style?</a></h2>
-<div class="level2">
-
-<p>
-There is a set of predefined sizes for routing. The sets bear suggestive names (Signal, Power, Fat and Skinny). Hit the button â??Route Styleâ?? to configure the sizes of the current set to your needs. You can set the names and the default values of these parameter sets in a config file ( ~/.pcb/settings for the <a href="http://geda.seul.org/wiki/geda:glossary"; class="wikilink1" title="geda:glossary">GTK-HID</a>, or ~/.Xdefaults for the <a href="http://geda.seul.org/wiki/geda:glossary"; class="wikilink1" title="geda:glossary">Lesstif-HID</a>). Example for such a setting:
-</p>
-<pre class="code">
-route-styles = Signal,1000,3600,2000,1000:Power,2500,6000,3500,1000:Fat,4000,6000,3500,1000:Skinny,600,2402,1181,600
-</pre>
-
-<p>
- Be sure, to remove any route-style line in ~/.pcb/preferences . Else, the line in settings will be ignored.
-</p>
-
-<p>
-The line tool knows about different modes to deal with transversal connections. The status line on the bottom of the page tells, which mode is in effect:
-</p>
-<ol>
-<li class="level1"><div class="li"> 45° plus vertical/horizontal (status line: â??\_â??)</div>
-</li>
-<li class="level1"><div class="li"> vertical plus 45° (status line: â??_/â??)</div>
-</li>
-<li class="level1"><div class="li"> either vertical or 45° (status line: â??45â??)</div>
-</li>
-<li class="level1"><div class="li"> arbitrary angle (status line: â??allâ??)</div>
-</li>
-</ol>
-
-<p>
-The way to access these modes differs among the <acronym title="Graphical User Interface">GUI</acronym> versions. The current GTK snapshot (v20060288) defaults to â??_/â?? but can be temporarily turned to â??\_â?? with the shift key. You can switch to 45° mode with the slash key â??/â??. For arbitrary angles, press the period key â??.â??, or choose â??enable all line directionsâ?? in the setting menu.
-</p>
-
-</div>
-<!-- SECTION "How do I change the routing style?" [21583-22996] -->
-<h2><a name="i_got_stuck_how_do_i_go_back" id="i_got_stuck_how_do_i_go_back">I got stuck! How do I go back?</a></h2>
-<div class="level2">
-
-<p>
-The universal undo key [<strong><code>U</code></strong>] works even while in the middle of track layout actions. It will remove the last segment but keep the line tool attached to the mouse. So you can immediately go on routing and find a better way.
-</p>
-
-</div>
-<!-- SECTION "I got stuck! How do I go back?" [22997-23269] -->
-<h2><a name="how_do_i_move_one_set_of_layer_tracks_to_a_different_layer" id="how_do_i_move_one_set_of_layer_tracks_to_a_different_layer">How do I move one set of layer tracks to a different layer?</a></h2>
-<div class="level2">
-<ol>
-<li class="level1"><div class="li"> Select the tracks. Itâ??s easiest to do this if you shut off everything but that layer first (i.e. silk, pins, other layers, etc).</div>
-</li>
-<li class="level1"><div class="li"> Now set the current layer to be the new layer. Yes, the layer might get displayed; not a problem as youâ??ve already selected the tracks you want.</div>
-</li>
-<li class="level1"><div class="li"> Press [<strong><code>shift-M</code></strong>] to move all the selected tracks to the current layer.</div>
-</li>
-</ol>
-
-</div>
-<!-- SECTION "How do I move one set of layer tracks to a different layer?" [23270-23710] -->
-<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>
-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" [23711-25486] -->
-<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/pad?" [25487-26013] -->
-<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">
-
-<p>
-There are a number of ways to change the size of already laid down tracks:
-</p>
-<ol>
-<li class="level1"><div class="li"> Use [<strong><code>s</code></strong>] and [<strong><code>shift-s</code></strong>] to increase and decrease the size of the track currenty under the mouse cursor.</div>
-</li>
-<li class="level1"><div class="li"> choose <strong><code>Select/Change_size_of_selected_objects/Decrement_lines_by_4mil</code></strong> from the <strong><code>Select</code></strong> menu. The actual amount of change can be set in <strong><code>File/Preferences/Sizes</code></strong>. This only acts on the tracks. So the selection may contain components, text, vias and the like.</div>
-</li>
-<li class="level1"><div class="li"> Select the tracks to be changed and type <strong><code>:ChangeSize(SelectedLines,+4,mils)</code></strong>. The colon gets you to the command line and <strong><code>ChangeSize()</code></strong> is the command version of the previously described action. Replace â??<strong><code>+4</code></strong>â?? by the amount you want to increase the track size. Use the minus sign to decrease the tracksize. If you omit the sign the command sets the track size to the value given.</div>
-</li>
-</ol>
-
-</div>
-<!-- SECTION "How do I change the size of my tracks?" [26014-26951] -->
-<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>
-<li class="level1"><div class="li"> Set the GND plane layer as the active layer.</div>
-</li>
-<li class="level1"><div class="li"> Select the â??viaâ?? tool.</div>
-</li>
-<li class="level1"><div class="li"> Place the via where you want it to live (left click to place).</div>
-</li>
-<li class="level1"><div class="li"> Now select the â??thermalâ?? tool.</div>
-</li>
-<li class="level1"><div class="li"> Left click on the via you just placed.</div>
-</li>
-<li class="level1"><div class="li"> Now change the active layer to your desired routing layer.</div>
-</li>
-<li class="level1"><div class="li"> Select the â??lineâ?? tool.</div>
-</li>
-<li class="level1"><div class="li"> Route the track on the active layer to or from the via as usual.</div>
-</li>
-</ol>
-
-</div>
-<!-- SECTION "How do I drive a via to connect a track to a ground plane on a different layer?" [26952-27437] -->
-<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">
-
-<p>
-A â??thermal viaâ?? is not a via with a thermal relief. Rather, itâ??s a via with no thermal relief punched into polygons on both sides of the board. These vias get filled with solder to help create a large thermal mass to be used as a heat sink. For more info, see Freescale App-Note AN4005.
-</p>
-
-<p>
-Here are some suggestions:
-</p>
-<ul>
-<li class="level1"><div class="li"> Draw a rectangle to comfortably surround the vias. Then, mouse over the rectangle and hit â??sâ??. This will flood the thermal reliefs on the vias. If you want to ever de-solder the part from the back, make sure the pad on the opposite side has the solder resist cleared.</div>
-</li>
-<li class="level1"><div class="li"> Just put a normal thermal relief on the via and then shift click on it to cycle through to the one with no relief. </div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "What is the easiest way to create a thermal via?" [27438-28215] -->
-<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">
-
-<p>
-You are likely drawing tracks with auto-DRC on. To connect the two segments, here are some suggestions:
-</p>
-<ul>
-<li class="level1"><div class="li"> DRC enforcement uses the ratsnest to determine where a track is allowed to go. Thus, you must have the ratsnest drawn in order to make connections in auto-DRC mode. Otherwise you will not be allowed to connect (or approach) any copper that is not already connected to your net. (If the rat visibility bothers you, you can hide the rats layer â?? but the rats must exist).</div>
-</li>
-<li class="level1"><div class="li"> You should also refresh the rats regularly when drawing. Hit [<strong><code>o</code></strong>] to redraw/re-optimize the rats. Make sure a rat is visibly connecting the two pieces of metal you want to connect.</div>
-</li>
-<li class="level1"><div class="li"> It is also possible that you will experience this situation when drawing tracks between pins in a connector. In this case, it is possible that your track width violates the clearance requirements of the pin field. Try decreasing the pin-to-metal clearance, or use a narrower track width.</div>
-</li>
-<li class="level1"><div class="li"> Sometimes this route-blocking behaviour can come about from an error in your netlist. Donâ??t end refdesâ??s with lower case letters - theyâ??re reserved for gates within devices. End with upper case or a digit; the lowercase letters are simply ignored.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "I want to draw a track between two segments on the same net, but PCB won't let me! Why?" [28216-29534] -->
-<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">
-
-<p>
-Most likely you named them such that pcb believes they are one part. Lower case letters at the end of a refdes are ignored. Thus, the components U2foo and U2bar both look like U2 to pcb. When building the rat nests pcb is will look for nets to U2 that, of course donâ??t exist. Lower case letters are meant to differentiate slots of a multi-component. E.g. the four opamp symbols of a quad operational amplifier.<br/>
- Bottom line: Donâ??t use lower case letters at the end of a refdes, unless you know what you are doing.
-</p>
-
-</div>
-<!-- SECTION "PCB seems to munge my components names and complains that it can't find proper nets for the pins! How come?" [29535-30172] -->
-<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">
-
-<p>
-You can set the color of the rats in <code>File - Preference - Colors - Main colors</code>
-</p>
-
-<p>
-There is currently no <acronym title="Graphical User Interface">GUI</acronym> way to set the rat width, but you can edit your <code>$HOME/.pcb/preference</code> file manually. Close all instances of pcb and look for the line that starts with <code>rat-thickness</code>.
-</p>
-
-</div>
-<!-- SECTION "How can I set color and thickness of the rats nests?" [30173-30524] -->
-<h2><a name="where_is_that_last_remaining_rat" id="where_is_that_last_remaining_rat">Where is that last remaining rat?</a></h2>
-<div class="level2">
-
-<p>
-Sometimes remaining rats are hard to see, because they have zero length. This will be the case if a via is missing for some reason. You can make them pop into your eye by setting the rat thickness to some big value e.g. 3000 mil. Rat thickness is set in <code>$HOME/.pcb/preference</code>.
-</p>
-
-</div>
-<!-- SECTION "Where is that last remaining rat?" [30525-30852] -->
-<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" [30853-30895] -->
-<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">
-
-<p>
-See the page <a href="http://www.delorie.com/pcb/bg-image.html"; class="urlextern" title="http://www.delorie.com/pcb/bg-image.html"; rel="nofollow">http://www.delorie.com/pcb/bg-image.html</a> at DJ Delorieâ??s PCB HID website.
-</p>
-
-<p>
-This is a great way to trace hand-drawn artwork or another PCB, say one you made in software with a proprietary format, which youâ??d now like to â??unlockâ??. Furthermore, you can use the background image as tool for making board revisions or redesigns.
-</p>
-
-<p>
-If you donâ??t like to use PCB confined to the area of the board, i.e. if you want margins around your board, then add them in the GIMP. I like to make a 1.00000 inch margin around the board. When you set your PCB size in PCB, youâ??ll want to add the margin area. CTRL-M will help you verify the scaling. Also, the time to correct distortions from your scanner, or from your drawing is before you load it, in the GIMP or the like.
-</p>
-
-</div>
-<!-- SECTION "How do I trace a drawing, a print, or another PCB?" [30896-31736] -->
-<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">
-
-<p>
-<strong>Question:</strong> I want to copy a section of my existing layout to another spot.
-</p>
-
-<p>
-I can select the existing area. Everything turns pretty blue.
-</p>
-
-<p>
-â??Bufferâ??–>â??Copy Selection To Bufferâ?? seems to succeed (no complaints).
-</p>
-
-<p>
-Then I go to paste the copied area… and all that moves are a couple of traces and some vias. The pads Iâ??ve painstakingly created arenâ??t copied. What gives!?!?!?
-</p>
-
-<p>
-<strong>Answer:</strong> If the silk layer is off, you canâ??t copy elements through the paste buffer. Weird, but thatâ??s how it works. Therefore, turn on the silk layer before trying to copy a section of a layout.
-</p>
-
-</div>
-<!-- SECTION "I can't copy component pads in a layout. What gives?" [31737-32391] -->
-<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">
-
-<p>
-Use rectangles and polygon planes. These items will always avoid vias, pads and pins. Tracks are also avoided, if they have the clear polygons flag set. (menu: Settings/Enable_new_lines_clear_polygons). Since version 20070208 of pcb the resulting polygon will be one contiguous piece. Isolated snippets are removed.
-</p>
-
-</div>
-<!-- SECTION "How do I fill areas with copper?" [32392-32755] -->
-<h2><a name="how_can_i_assign_my_polygon_to_a_net" id="how_can_i_assign_my_polygon_to_a_net">How can I assign my polygon to a net?</a></h2>
-<div class="level2">
-
-<p>
-Polygons are not â??assignedâ?? to nets, theyâ??re connected to them. Pads are the only carriers of netnames in pcb. This means, you need to design some copper to connect the polygon with a pad. The net of the pad automatically transfers to the polygon.
-</p>
-
-</div>
-<!-- SECTION "How can I assign my polygon to a net?" [32756-33056] -->
-<h2><a name="how_can_i_connect_tracks_pads_or_vias_to_my_polygon" id="how_can_i_connect_tracks_pads_or_vias_to_my_polygon">How can I connect tracks, pads, or vias to my polygon?</a></h2>
-<div class="level2">
-
-<p>
-There are different ways to adequately connect different types of objects to a polygon:
-</p>
-<ul>
-<li class="level1"><div class="li"> tracks: Clear the join flag of the track. You can do this with the [<strong><code>j</code></strong>] key, while the mous hovers above the track. Alternatively you can uncheck the new-lines-clear-polygons in the settings menu. The polygon will immediately flow into the track.</div>
-</li>
-<li class="level1"><div class="li"> pads: Currently, there is nao way to directly connect a polygon to a pad. Draw a track without the join flag from the pad to the polygon. (see above) </div>
-</li>
-<li class="level1"><div class="li"> pins and vias: Choose the thermal tool (â??THRMâ??). Select the layer the polygon sits on. Shift-Click on the via to circle through the available styles of the connection. </div>
-</li>
-<li class="level1"><div class="li"> polygons: Just define them geometrically overlapping.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "How can I connect tracks, pads, or vias to my polygon?" [33057-33857] -->
-<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">
-
-<p>
-You didnâ??t have â??Enable_new_lines_clear_polygonsâ?? checked in the settings menu when you layed down the tracks. Enter â??changejoin(selected)â?? in the command window to toggle this flag for all tracks that are currently selected. The keyboard shortcut to this action is [<strong><code>shift-j</code></strong>]. If you want to set or clear the join flag rather than toggle it, you can use the commands â??SetFlag(selected, join)â?? and â??ClrFlag(selected, join)". See the SetFlag description in the <a href="http://pcb.sourceforge.net/manual.html"; class="urlextern" title="http://pcb.sourceforge.net/manual.html"; rel="nofollow">pcb manual</a> for more details on these commands.
-</p>
-
-</div>
-<!-- SECTION "The polygons are shorting my tracks! What can I do about it?" [33858-34507] -->
-<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">
-
-<p>
-Press [<strong><code>k</code></strong>] to increase the clearence of the object under the cursor. Use [<strong><code>ctrl-k</code></strong>] to increase the clearence of selected objects. Add the [<strong><code>shift</code></strong>] modifier to decrease the clearence. To change a whole track press [<strong><code>f</code></strong>] to find all segments that are connected to the object under the cursor and apply the action â??select(connection)â??.
-</p>
-
-<p>
-The amount of the increment can be configured in the dialog File/Preference/Increments.
-</p>
-
-</div>
-<!-- SECTION "How do I change polygon clearance?" [34508-35008] -->
-<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">
-
-<p>
-Put the polygons (and rectangles) on a separate layer. Use the preference to make sure, this layer is not in the same group as the tracks. Disable the layer by a click on the corresponding layer button in the main window. After you are finished with the changes, use the preference dialog to let the polygon layer join the layer of the tracks. You will have to save and reload the layout to trigger recalculation of polygons so they are adapted to your edits. Alternatively a restart will recaalculate the polygons too.
-</p>
-
-</div>
-<!-- SECTION "How do I hide the polygons while I edit the layout?" [35009-35594] -->
-<h2><a name="polygons_are_making_the_gui_sluggish._what_i_can_do_about_it" id="polygons_are_making_the_gui_sluggish._what_i_can_do_about_it">Polygons are making the GUI sluggish. What I can do about it?</a></h2>
-<div class="level2">
-
-<p>
-Parts of the polygon that are not connected to some net are automatically eliminated. This effectively removes <a href="http://geda.seul.org/wiki/geda:glossary"; class="wikilink1" title="geda:glossary">dead copper</a>. While this is desirable for the actual board, it requires calculation of quite extensive algorithms. So it is not necessarily a bug, but a price to be paid for a powerful feature. Still, there is a couple of things you can do to improve the situation:
-</p>
-<ul>
-<li class="level1"><div class="li"> Temporarily hide the polygons. (see above)</div>
-</li>
-<li class="level1"><div class="li"> Choose â??thin draw polyâ?? from the settings menu to display only the outlines of the polygons and disable dead copper removal. In recent versions of gschem, i.e. later than september 2007, you can select through the polygons. </div>
-</li>
-<li class="level1"><div class="li"> Make sure, you donâ??t have redundant polygons defined, which multiply overlay the same area. These polygons wonâ??t display becaus they shade each other. But they demand calculation resources. The best way to check for redundant polygons is to edit the source of your layout with an ascii editor. </div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Polygons are making the GUI sluggish. What I can do about it?" [35595-36638] -->
-<h2><a name="after_i_defined_those_ground_planes_pcb_takes_ages_to_load._how_come" id="after_i_defined_those_ground_planes_pcb_takes_ages_to_load._how_come">After I defined those ground planes, pcb takes ages to load. How come?</a></h2>
-<div class="level2">
-
-<p>
-Polygon calculation is potentially an expensive operation in terms of processor cyles. Unless your layout is pretty complex, you most likely have redundant polygons defined. Look into the source of your layout to find and delete unnecessary polygons. If this does not apply, see above for possible measures to ameliorate the situation.
-</p>
-
-</div>
-<!-- SECTION "After I defined those ground planes, pcb takes ages to load. How come?" [36639-37059] -->
-<h2><a name="how_do_i_edit_polygons" id="how_do_i_edit_polygons">How do I edit polygons?</a></h2>
-<div class="level2">
-
-<p>
-There are four basic ways to edit polygon outlines. You can move and delete vertices and you can insert vertices using two techniques. Polygons can be edited equally well in â??thin line drawâ?? mode (settings â??> enable thin line draw) or in normal mode. Moving a vertex is easily accomplished by un-selecting your polygon and then clicking and dragging that vertex to a new location. To delete a vertex, a corner in your polygon, put your crosshairs over the point and hit â??deleteâ?? on the keyboard. To insert a vertex, youâ??ll use the insert tool (â??insertâ?? keystroke). Start by clicking the edge you want to split with a new point. Click and drag a new point into the polygon. A variation on this technique is 1) click to select, followed by 2) click to place new vertex.
-</p>
-
-<p>
-(NOTE: Inserting points into polygon will generally work ONLY with â??all direction linesâ?? enabled (â??settings â??> enable all direction linesâ??). This is because PCB has a powerful 45/90 degree constraints system. If you try to insert new vertices into a polygon that donâ??t fall onto lines of proper 45 and 90 degree constraints, PCB disallows the action!)
-</p>
-
-</div>
-<!-- SECTION "How do I edit polygons?" [37060-38245] -->
-<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">
-
-<p>
-Often itâ??s useful to have vias connect completely to a polygon (a field of copper) for heat transferâ?? the apparent problem is that PCB polygons have only a single â??clear pins/viasâ?? flag for the entire polygon (toggled by the [<strong><code>s</code></strong>] key). Our goal is to only connect some of the pins/vias to the polygon, but to connect them better than a thermal does. Here are a few ways to do this:
-</p>
-
-<p>
-One way, youâ??ll make an object thatâ??s almost just like a thermal in that it goes between your via and the polygonâ??the difference is that youâ??ll actually create an annulus to completely fill the space between the hole and polygon (which because itâ??s clearance is turned on, is not connected to the pin). This annulus is four arc segments. You can copy these four items to the buffer to create a â??zero-clearance thermal toolâ??. The drawback of this trick is that when you change via size, youâ??ll also have to modify the size of these filler parts.
-</p>
-
-<p>
-The arcs allow you to use this fill trick in tight places by only placing, say two of the four arcs.
-</p>
-
-<p>
-Another trick is to make a zero-length line. Take a single line segment and move the end-point on top of the start-point. Now you have a â??single point lineâ?? (a circle) with the diameter equal to the line thickness. Move to different layers ([<strong><code>m</code></strong>] key) as you see fit. Place this object centered on your via to connect it to a polygon.
-</p>
-
-<p>
-Power-users may want to keep a small custom library of these parts by saving them as elements. Itâ??s also handy to put these â??partsâ?? in one of your PCB buffers so theyâ??re at your fingertips.
-</p>
-
-<p>
-You can also add another polygon on-top of the polygon to which you want to connect you vias. Youâ??ll un-set the â??clear pins/viasâ?? flag and the vias will be connected to the larger polygon underneath.
-</p>
-
-</div>
-<!-- SECTION "How do I place vias that connect to a polygon for full thermal dissipation or full shielding integrity?" [38246-40167] -->
-<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">
-
-<p>
-Currently, there is no way to directly make polgons clear solder mask. The usual workaround is to work with pads.
-</p>
-<ol>
-<li class="level1"><div class="li"> Draw a track in the middle of the desired no solder mask area. Every track will become a pad.</div>
-</li>
-<li class="level1"><div class="li"> Select the tracks</div>
-</li>
-<li class="level1"><div class="li"> Do convert-selection-to-element from the select menu</div>
-</li>
-<li class="level1"><div class="li"> Activate the solder mask layer. The solder mask should keep clear of the tracks</div>
-</li>
-<li class="level1"><div class="li"> Increase the clearance of the pads to match the desired bare copper area. To do this, press [k] while the mouse cursor hovers above the pads.</div>
-</li>
-<li class="level1"><div class="li"> Optionally press q to set the square flag of the pads.</div>
-</li>
-</ol>
-
-<p>
-While the pad witdth is limited to 250 mil, clearance can be arbitrary.
-</p>
-
-</div>
-<!-- SECTION "Can polygons be un-masked? (Can a polygon be made bare-copper with no solder mask?)" [40168-40917] -->
-<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">
-
-<p>
-Use a footprint for the mounting hole or place a via.
-</p>
-
-<p>
-If the pads surrounding the mounting hole need to be electrically connected then you should show the connection in your schematic. Add a symbol for the mounting hole and change its footprint attribute.
-</p>
-
-<p>
-My preference is to create PCB footprints for the various types of mounting hardware. I have a variety of silkscreens for various hardware combinations (hex nut, hex nut with washer, etc.) The silkscreen provides a convenient placement reference during PCB layout.
-</p>
-
-<p>
-For footprint examples see <a href="http://www.luciani.org/geda/pcb/pcb-footprint-list.html#Hardware"; class="urlextern" title="http://www.luciani.org/geda/pcb/pcb-footprint-list.html#Hardware"; rel="nofollow">http://www.luciani.org/geda/pcb/pcb-footprint-list.html#Hardware</a>.
-</p>
-
-</div>
-<!-- SECTION "How do I place mounting holes?" [40918-41582] -->
-<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">
-
-<p>
-The reason is that pins usually have sufficient spacing that the plane surrounding them remains intact on all sides and pads usually are so tightly spaced that they do not. Because of this you must manually draw the thermal â??fingersâ?? to connect the pad to the ground plane. Be sure that you have the settings such that new lines connect to planes when you draw them. If you need to make several such thermals, spend a little time making the first one just the way you want then copy the fingers to the buffer and paste it where you want the others.
-</p>
-
-</div>
-<!-- SECTION "Why is it possible to make a thermal for pin, but not for a pad?" [41583-42213] -->
-<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">
-
-<p>
-Yes. Just plot your gerbers and toss any layers that are not needed. You can just draw the layout as you want (freestyle). If you want to verify connectivity, you have two choices:
-</p>
-<ol>
-<li class="level1"><div class="li"> Assuming your copper is on the bottom side, use the top side in layout to put down traces where jumpers will be. This is probably the easiest. Then just fab the bottom side and put jumpers wherever you have top side copper.</div>
-</li>
-<li class="level1"><div class="li"> Create a â??jumperâ?? symbol in the schematic and put that in places where you need a jumper. This is likely to be a major pain, but you can enforce dimensions of the jumpers this way if you care.</div>
-</li>
-</ol>
-
-<p>
- If youâ??re trying to use the autorouter, just turn off all but the bottom layer when you route and it will stick to that layer.
-</p>
-
-</div>
-<!-- SECTION "Can PCB be used to make single layer boards?" [42214-43011] -->
-<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">
-
-<p>
-One of PCBâ??s great features is that it uses an easily understood <acronym title="American Standard Code for Information Interchange">ASCII</acronym> file format. Therefore, many people use scripts (commonly <acronym title="Practical Extraction and Report Language">Perl</acronym>) to process their boards in various ways. You can use these scripts either as they are, or modify them to suit your own goals. Here are some links to available scripts:
-</p>
-<ol>
-<li class="level1"><div class="li"> John Luciani has a large number of <a href="http://www.luciani.org/geda/pcb/pcb-perl-library.html"; class="urlextern" title="http://www.luciani.org/geda/pcb/pcb-perl-library.html"; rel="nofollow">scripts</a> available on <a href="http://www.luciani.org/"; class="urlextern" title="http://www.luciani.org"; rel="nofollow"> his website</a>. Included in his collection are scripts for generating footprints, as well as </div>
-</li>
-<li class="level1"><div class="li"> David Rowe has scripts for updating elements as well as adding/subtracting PCB files from each other on <a href="http://www.rowetel.com/perl4pcb.html"; class="urlextern" title="http://www.rowetel.com/perl4pcb.html"; rel="nofollow">his website.</a></div>
-</li>
-<li class="level1"><div class="li"> Stuart Brorson wrote a simple script which generates footprints for two terminal SMT passives. A gzipped tarball is available <a href="http://www.brorson.com/gEDA/Smtgen.pl.gz"; class="urlextern" title="http://www.brorson.com/gEDA/Smtgen.pl.gz"; rel="nofollow"> here </a>.</div>
-</li>
-<li class="level1"><div class="li"> The website <a href="http://www.gedasymbols.org/"; class="urlextern" title="http://www.gedasymbols.org/"; rel="nofollow"> gedasymbols.org</a> has gathered a collection of footprints, symbols, scripts, and other materials from many different gEDA contributors. The website is organized by contributor, so if you take the time to browse around there, you may find exactly what you are looking for!</div>
-</li>
-</ol>
-
-</div>
-<!-- SECTION "What resources exist to process PCB files using scripts?" [43012-44296] -->
-<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">
-
-<p>
-There is a third party open source utility called <a href="http://www.pstoedit.net/"; class="urlextern" title="http://www.pstoedit.net/"; rel="nofollow">pstoedit</a> that converts postscript data to pcb format. It is included in most major linux distributions. You can use your favorite vector graphics utility to produce a logo or any kind of fancy layout. Export as eps if you can and make sure that your logo fits into the bounding box (check with a postscript viewer such as ggv). If there is no eps export available, you can produce postscript by printing to a file. In this case you may add a bounding box with <a href="http://www.cs.wisc.edu/~ghost/doc/gnu/6.53/Ps2epsi.htm"; class="urlextern" title="http://www.cs.wisc.edu/~ghost/doc/gnu/6.53/Ps2epsi.htm"; rel="nofollow">ps2epsi</a>. Call pstoedit with the option "<code>-f pcb</code>â?? to produce a valid pcb file that contains the graphics as tracks on layer 1. Load this file to pcb. The graphics will sit somewhere on the lower left of the view port. You may have to zoom out to get it on the screen.
-</p>
-
-<p>
-Import of external vector graphics is usefull if an irregular shape of the pcb is required. Use the cut buffer to copy the shape to your actual design.
-</p>
-
-</div>
-<!-- SECTION "How do I import external vector graphics?" [44297-45375] -->
-<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">
-
-<p>
-You can set the name of the current pcb with <code>Menu Edit - Edit name of - layout</code>. This sets the title attribute of the layout. This attribute is used for the export actions. It does not interfere with the file name.
-</p>
-
-</div>
-<!-- SECTION "How Do I attach a name to my layout?" [45376-45646] -->
-<h1><a name="auto_router" id="auto_router">Auto Router</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "Auto Router" [45647-45673] -->
-<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">
-
-<p>
-Just unselect the layers you donâ??t want (usually green and blue) by clicking on the name of the layer. then press autoroute.
-</p>
-
-</div>
-<!-- SECTION "How do I force the autorouter to only put traces on a particular layer?" [45674-45885] -->
-<h2><a name="how_do_i_make_autorouter_leave_particular_nets_alone" id="how_do_i_make_autorouter_leave_particular_nets_alone">How do I make autorouter leave particular nets alone?</a></h2>
-<div class="level2">
-
-<p>
-Open up the netlist window. It has options for including or excluding nets from the ratlist. If you use the GTK-HID double-click a route to disable it. Make sure, only the nets you want are enabled. Optimize the rats with key [o]. Do â??autoroute all ratsâ??.
-</p>
-
-</div>
-<!-- SECTION "How do I make autorouter leave particular nets alone?" [45886-46210] -->
-<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">
-
-<p>
-You can have the autorouter work only within a given area by drawing a copper polygon conforming to your boardâ??s boundary and placing it in each layer youâ??re trying to autoroute. You can also use this trick to autoroute only with small areas. Of course, if you accidentally have a net touching the polygon, all routes will get shorted to that net.
-</p>
-
-</div>
-<!-- SECTION "How do I force the autorouter to route only within my pcb outline?" [46211-46642] -->
-<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">
-
-<p>
-Connect the polygon that will become your power planes to a net and the autorouter will figure it all out. You may need some trick polygon clearances to get power routing _and_ routing within a board outline.
-</p>
-
-</div>
-<!-- SECTION "How do I route power and ground planes with the autorouter?" [46643-46924] -->
-<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">
-
-<p>
-This is a technological limitation of the current auto router. It is gridless and uses geometric rectangles only.
-</p>
-
-</div>
-<!-- SECTION "The layout produced by the autorouter is inefficient!" [46925-47105] -->
-<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">
-
-<p>
-Have you tried the various clean-up tools under connects–>optimize routed tracks?
-</p>
-
-</div>
-<!-- SECTION "The layout produced by the autorouter is ugly!" [47106-47248] -->
-<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" [47249-47301] -->
-<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">
-
-<p>
-You can add an outline layer to your pcb projects. PCB interprets any layer called â??outlineâ?? (edit â??> edit name of â??> active layer) as though it is the absolute edge of the pcb. PCB prints gerber files that rigidly represent this.
-</p>
-
-<p>
-You can enter your outline layer thru PCBâ??s <acronym title="Graphical User Interface">GUI</acronym>. You just draw the lines of the board outline. You can generate boards of any shape this way.
-</p>
-
-<p>
-Itâ??s also possible to edit the native .pcb file format of your layout. I usually use Layer 8 for outlines:
-</p>
-<pre class="code">Layer(8 "outline")
-(
- Line[x1 y1 x2 y2 1000 2000 0x00000000]
- Line[x2 y2 x3 y3 1000 2000 0x00000000]
- Line[x3 y3 x4 y4 1000 2000 0x00000000]
- Line[x4 y4 x1 y1 1000 2000 0x00000000]
- Line[<more points go here for non-square boards> 1000 2000 0x00000000]
-)</pre>
-
-</div>
-<!-- SECTION "How do I make a board outline to go with my gerbers to the board maker?" [47302-48148] -->
-<h2><a name="yes_i_tried_that_but_the_gerber_exporter_didn_t_give_me_an_outline_file._why" id="yes_i_tried_that_but_the_gerber_exporter_didn_t_give_me_an_outline_file._why">Yes, I tried that, but the gerber exporter didn't give me an outline file. Why?</a></h2>
-<div class="level2">
-
-<p>
- By default, gsch2pcb creates layer groups in a way which prevents your outline layer from being treated properly. So you should remove all the unnecessary layers (i.e, all but your copper layers and silkscreen), then add an outline layer (named <code>outline</code>), on which you define your outline. The gerber exporter should then give you the outline gerber file.
-</p>
-
-</div>
-<!-- SECTION "Yes, I tried that, but the gerber exporter didn't give me an outline file. Why?" [48149-48601] -->
-<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>
-<li class="level1"><div class="li"> Run a check of design rules either through the command interface (â??DRC()") or from the menu (Connects - Design Rule Checker). You can set the rules in the sizes section of the preference dialog. Results of the check are shown in the log window. </div>
-</li>
-</ul>
-
-<p>
-Besides running the DRC checker, it is essential to check your Gerber files. The gEDA Suite includes the program â??gerbvâ?? for this task. Here are some things to check/verify:
-</p>
-<ul>
-<li class="level1"><div class="li"> Check that all trace widths are the correct size. Also make sure your trace widths and metal-metal separations are above the minimum specified by your PCB vendor.</div>
-</li>
-<li class="level1"><div class="li"> Check that all hole diameters are called out at the correct size.</div>
-</li>
-<li class="level1"><div class="li"> Check that metal annular rings around holes/vias are large enough. The annular ring is the distance between the holeâ??s edge and the outer diameter of the metallization. The annular ring must be large enough to accomodate drill location + layer registration + other manufacturing inaccuracy. This information should be available from your PCB fabrication house; they normally publish the minimum annular ring requirements in their manufacturing rules document.</div>
-</li>
-<li class="level1"><div class="li"> Check that your antipads (clearance around holes/vias) are large enough. This information should be available from your PCB fabrication house; ask them for their manufacturing rules document.</div>
-</li>
-<li class="level1"><div class="li"> Verify that no soldermask or silkscreen overlays a copper pad or through-hole.</div>
-</li>
-<li class="level1"><div class="li"> On plane layers, verify that at least some vias connect to it (yes, I have seen a board where the entire ground plane was floating â?? not done in pcb btw)</div>
-</li>
-<li class="level1"><div class="li"> On plane layers, verify that at least some vias _donâ??t_ connect to it.</div>
-</li>
-<li class="level1"><div class="li"> Do a visual sanity check of all layers. Nothing detailed, just does it look approximately like you think it should.</div>
-</li>
-<li class="level1"><div class="li"> Are all layers negative/positive as they should be? Note that some fab houses want positive layers only. PCB will automatically create negative Gerbers on outer layer planes with no tracks. If you want an all-plane layer to be output as a positive layer, draw a single track somewhere in an unused part of the plane. This will trigger PCB to render that layer as a positive layer.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "I'm done with my layout. How should I check my design?" [48602-50821] -->
-<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" [50822-50881] -->
-<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">
-
-<p>
-It limits the size of the image to NxN pixels, but maintains the aspect ratio. For example, if you set it to 400, a 6000×8000 mil board would yield a 300×400 image, but a 6000×4500 board yeilds a 400×300 image.
-</p>
-
-</div>
-<!-- SECTION "What is xy-max in the PNG export dialog box?" [50882-51152] -->
-<h1><a name="customization" id="customization">Customization</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "Customization" [51153-51180] -->
-<h2><a name="i_don_t_like_that_old-style_black_backgropund._how_can_i_get_a_light_canvas" id="i_don_t_like_that_old-style_black_backgropund._how_can_i_get_a_light_canvas">I don't like that old-style black backgropund. How can I get a light canvas?</a></h2>
-<div class="level2">
-
-<p>
-In <a href="http://geda.seul.org/wiki/geda:glossary"; class="wikilink1" title="geda:glossary">GTK-HID</a> there is a preference dialog in the file menu. The Colors tab presents a convinient way to set all the colros pcb uses via the standard GTK color chooser. The colors are saved to $HOME/.pcb/preferences on shut down of the application. With <a href="http://geda.seul.org/wiki/geda:glossary"; class="wikilink1" title="geda:glossary">Lesstif-HID</a> there is no preference dialog. Colors can be set in <code>$HOME/.pcb/settings</code>
-</p>
-
-</div>
-<!-- SECTION "I don't like that old-style black backgropund. How can I get a light canvas?" [51181-51636] -->
-<h2><a name="how_do_i_set_the_default_values_of_the_postscript_dialog" id="how_do_i_set_the_default_values_of_the_postscript_dialog">How do I set the default values of the postscript dialog?</a></h2>
-<div class="level2">
-
-<p>
-You can set the default options of the postscript printing dialog as command line parameters when invoking pcb. Type <code>pcb –help</code> for a list of available options. These options can also be set in a file <code>$HOME/.pcb/settings</code>. A settings file for a4 paper, no alignment marks, multi page output would contain:
-</p>
-<pre class="code">media = A4
-align-marks = 0
-multi-file = 1</pre>
-
-</div>
-<!-- SECTION "How do I set the default values of the postscript dialog?" [51637-52075] -->
-<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">
-
-<p>
-<a href="http://www.luciani.org/geda/pcb/faq-pcb-footprint.html"; class="urlextern" title="http://www.luciani.org/geda/pcb/faq-pcb-footprint.html"; rel="nofollow">http://www.luciani.org/geda/pcb/faq-pcb-footprint.html</a><br/>
- <a href="http://pcb.sourceforge.net/faq.html"; class="urlextern" title="http://pcb.sourceforge.net/faq.html"; rel="nofollow">http://pcb.sourceforge.net/faq.html</a><br/>
- <a href="http://pcb.sourceforge.net/pcb-20060822/pcb.html#Top"; class="urlextern" title="http://pcb.sourceforge.net/pcb-20060822/pcb.html#Top"; rel="nofollow">http://pcb.sourceforge.net/pcb-20060822/pcb.html#Top</a>
-</p>
-
-<p>
-You can get fast responses from the geda-user email list. If you havenâ??t found an answer to your question about PCB on this page, or in the other documentation, then post to the list! Note that you must subscribe to the geda-user e-mail list before you can post to the list. The gEDA e-mail lists, and their archives, are at: <a href="http://geda.seul.org/mailinglist/index.html"; class="urlextern" title="http://geda.seul.org/mailinglist/index.html"; rel="nofollow">http://geda.seul.org/mailinglist/index.html</a>
-</p>
-
-</div>
-<!-- SECTION "You didn't answer my question. What other resources exist for PCB information?" [52076-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/geda_pcb_ug.html b/docs/wiki/geda_pcb_ug.html
deleted file mode 100644
index 4f61c05..0000000
--- a/docs/wiki/geda_pcb_ug.html
+++ /dev/null
@@ -1,27 +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>geda:pcb_ug</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="noindex,follow" />
-<meta name="date" content="1969-12-31T19:00:00-0500" />
-<meta name="keywords" content="geda,pcb_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/"; />
-<link rel="contents" href="http://geda.seul.org/wiki/geda:pcb_ug?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:pcb_ug"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:pcb_ug"; />
-<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>
-</body>
-</html>
diff --git a/docs/wiki/geda_release_engineering.html b/docs/wiki/geda_release_engineering.html
deleted file mode 100644
index d4c54b4..0000000
--- a/docs/wiki/geda_release_engineering.html
+++ /dev/null
@@ -1,137 +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>geda:release_engineering</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2008-01-26T19:08:07-0500" />
-<meta name="keywords" content="geda,release_engineering" />
-<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/geda:release_engineering?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:release_engineering"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:release_engineering"; />
-<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">
-
-
-
-<h1><a name="geda_s_release_engineering" id="geda_s_release_engineering">gEDA's Release Engineering</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "gEDA's Release Engineering" [1-43] -->
-<h2><a name="geda_gaf_release_creation_checklist" id="geda_gaf_release_creation_checklist">gEDA/gaf Release Creation Checklist</a></h2>
-<div class="level2">
-
-<p>
- Here is a list of steps that are taken every time when creating a new gEDA/gaf release:
-</p>
-<ul>
-<li class="level1"><div class="li"> Manually run all tests. gnetlist has a nice set of regression tests in gnetlist/tests. Open up all schematics in gschem/examples and gschem/tests. Run the tests in gsymcheck/tests. You can do this by running the following in each of the directories:</div>
-</li>
-</ul>
-<pre class="code">
- make check
-</pre>
-<ul>
-<li class="level1"><div class="li"> Run make update-po in all po directories. Commit these changes before continuing.</div>
-</li>
-<li class="level1"><div class="li"> Update all versions running update-versions.sh in the toplevel directory (libgedaâ??s so version should follow what is described in <a href="http://sourceware.org/autobook/autobook/autobook_91.html"; class="urlextern" title="http://sourceware.org/autobook/autobook/autobook_91.html"; rel="nofollow"> Autobook's library versioning</a> chapter).</div>
-</li>
-</ul>
-<pre class="code">
- ./update-versions.sh 1.0.1 20070626 29:1:0
-</pre>
-<ul>
-<li class="level1"><div class="li"> Update all the versions and dates in the man pages (gschem.1, gnetlist.1, gsymcheck.1)</div>
-</li>
-<li class="level1"><div class="li"> Update the wiki documentation (this is far far far too manual)</div>
-</li>
-</ul>
-<pre class="code">
- cd docs
- mkdir wip
- cd wip
- ../scripts/wikifetch.sh
- rm -f *.txt
- mv geda.seul.org/wiki/* .
- rmdir geda.seul.org/wiki
- rmdir geda.seul.org
- ../scripts/postproc.sh
- find . -name *.orig -exec rm -f {} \; -print
- cd ..
- scripts/copygitignores.sh
- cd wip
- ../scripts/populatemkfiles.sh
- vi `find . -name Makefile.am` (Make sure all files have correct install path)
- cd ..
- diff -r -q wiki wip | grep -v Only | sed "s/Files /tkdiff /" | sed "s/ and//" | sed "s/differ//" > diffs
- sh diffs (and examine all changes; you need to have tkdiff installer or use just plain diff above)
- mv wiki wiki.original
- mv wip wiki
- git status
- git add <any new files>
- git commit -a
-</pre>
-<ul>
-<li class="level1"><div class="li"> Update the ChangeLogs by running:</div>
-</li>
-</ul>
-<pre class="code">
- ./update-changelogs.sh 1.0-20070526..master
- or
- ./update-changelogs.sh 1.0-20070526..stable-1.2 (if you are on a branch)
-</pre>
-<ul>
-<li class="level1"><div class="li"> Commit all of the above changes (preferably in between each step)</div>
-</li>
-<li class="level1"><div class="li"> Run: make distcheck and make sure it completes without any errors. After this is complete you will find all the tarballs in the toplevel directory.</div>
-</li>
-<li class="level1"><div class="li"> Copy all these tarballs some place else along with the toplevel README and Makefile</div>
-</li>
-<li class="level1"><div class="li"> Modify the toplevel Makefile to use the Released version of CD_VERSION and DIR_PREFIX environment variables. Comment out repository versions of these variables</div>
-</li>
-<li class="level1"><div class="li"> Untar the tarballs and compare what is inside to what is in the repository. You should only find additional dist files inside the tarballs and no missing required files.</div>
-</li>
-<li class="level1"><div class="li"> Build and test the tarballs one last time.</div>
-</li>
-<li class="level1"><div class="li"> Make sure everything is committed and pushed and then put down the correctly formatted tag:</div>
-</li>
-</ul>
-<pre class="code">
- git-tag -a 1.3.0-20071229
-</pre>
-<ul>
-<li class="level1"><div class="li"> Push the tag to the main repository:</div>
-</li>
-</ul>
-<pre class="code">
- git push --tags
-</pre>
-<ul>
-<li class="level1"><div class="li"> Upload files to the correct place</div>
-</li>
-<li class="level1"><div class="li"> Write release announcement and send to mailing lists</div>
-</li>
-<li class="level1"><div class="li"> Write up release notes and send pointer to mailing lists</div>
-</li>
-<li class="level1"><div class="li"> Update news update the sources download pages on the website with links to the new version</div>
-</li>
-<li class="level1"><div class="li"> Done!</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "gEDA/gaf Release Creation Checklist" [44-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/geda_scg.html b/docs/wiki/geda_scg.html
deleted file mode 100644
index 2f471b3..0000000
--- a/docs/wiki/geda_scg.html
+++ /dev/null
@@ -1,619 +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>geda:scg</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="geda,scg" />
-<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/geda:scg?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:scg"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:scg"; />
-<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="#geda_gaf_symbol_creation_document" class="toc">gEDA/gaf Symbol Creation Document</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#overview" class="toc">Overview</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#component_symbol_creation" class="toc">Component symbol creation</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#requirements" class="toc">Requirements</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#style" class="toc">Style</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#text" class="toc">Text</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#attributes" class="toc">Attributes</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#graphics" class="toc">Graphics</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#pins" class="toc">Pins</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#electrical" class="toc">Electrical</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#footprint_naming_conventions" class="toc">Footprint naming conventions</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#notes" class="toc">Notes</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#integrated_circuit_packages" class="toc">Integrated circuit packages</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#integrated_circuit_smt_packages" class="toc">Integrated circuit SMT packages</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#basic_semiconductors" class="toc">Basic semiconductors</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#basic_smt_semiconductors" class="toc">Basic SMT semiconductors</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#passive_components" class="toc">Passive components</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#passive_smt_components" class="toc">Passive SMT components</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#hints_and_tips" class="toc">Hints and Tips</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#example" class="toc">Example</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#document_revision_history" class="toc">Document Revision History</a></span></div></li></ul>
-</li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="geda_gaf_symbol_creation_document" id="geda_gaf_symbol_creation_document">gEDA/gaf Symbol Creation Document</a></h1>
-<div class="level1">
-
-<p>
-by: Ales V. Hvezda / July 6th, 2004
-</p>
-
-<p>
-The latest version of this document may be found at: <a href="http://geda.seul.org/wiki/geda:scg"; class="urlextern" title="http://geda.seul.org/wiki/geda:scg"; rel="nofollow">http://geda.seul.org/wiki/geda:scg</a>
-</p>
-
-<p>
-This document is released under the <a href="geda_gfdl.html" class="wikilink1" title="geda:gfdl">GNU Free Documentation License (GFDL)</a>.
-</p>
-
-</div>
-<!-- SECTION "gEDA/gaf Symbol Creation Document" [1-264] -->
-<h2><a name="overview" id="overview">Overview</a></h2>
-<div class="level2">
-
-<p>
-This document describes the creation of component symbols, including style conventions, and hints/tips and things to look out for when drawing symbols for the gEDA/gaf system.
-</p>
-
-</div>
-<!-- SECTION "Overview" [265-462] -->
-<h2><a name="component_symbol_creation" id="component_symbol_creation">Component symbol creation</a></h2>
-<div class="level2">
-
-<p>
-Component symbols (from here on known as â??symbolsâ??) are drawn using gschem just like drawing a schematic sheet. Here are the steps in a symbol in the gEDA/gaf system:<br/>
- 1. Run gschem and find a blank page or run: gschem filename-1.sym<br/>
- 2. Draw the symbol (see the style guide below for some conventions).<br/>
- 3. Translate the symbol to the origin using Edit/Symbol Translate…<br/>
-
-</p>
-<ul>
-<li class="level1"><div class="li"> Zoom in at least one step.</div>
-</li>
-<li class="level1"><div class="li"> Make sure the snap is ON (this is critical).</div>
-</li>
-<li class="level1"><div class="li"> Make sure grid snap size is set to 100 (this is critical).</div>
-</li>
-<li class="level1"><div class="li"> Select â??Symbol Translate…â?? or the press equivalent hotkey.</div>
-</li>
-<li class="level1"><div class="li"> Enter 0 into the entry field and press OK.<br/>
-</div>
-</li>
-</ul>
-
-<p>
-Translating the symbol to the origin is a required step. To translate a symbol elsewhere, enter a offset (in mils) which is a even multiple of 100. Make sure all pins are snapped to a 100 mil grid point.
-</p>
-
-<p>
-4. Save the symbol using Save or SaveAs… Here are some symbol naming conventions:<br/>
-
-</p>
-<ul>
-<li class="level1"><div class="li"> Symbols are named: symbolname-#.sym</div>
-</li>
-<li class="level1"><div class="li"> Symbols end with a .sym extension.</div>
-</li>
-<li class="level1"><div class="li"> Symbols have a -# where # is a number. Typically # is 1 but if there are multiple symbols for a device then this number simply increments.</div>
-</li>
-<li class="level1"><div class="li"> Symbol names are typically lowercase but letters which are part of a part number are uppercase.</div>
-</li>
-<li class="level1"><div class="li"> The above case rule can be broken if the filename looks incorrect or wrong.</div>
-</li>
-</ul>
-
-<p>
- 5. Place the symbol in one of the directories specified by the componentlibrary keyword in the system-gafrc file. Once this is done, the symbol should be visible immediately and can be selected and placed with the â??Add/Select Component…â?? menu item.
-</p>
-
-</div>
-<!-- SECTION "Component symbol creation" [463-2082] -->
-<h2><a name="requirements" id="requirements">Requirements</a></h2>
-<div class="level2">
-
-<p>
-This section describes the various requirements which must be met in order to create a valid symbol which will display and netlist in the gEDA/gaf system. Most of the requirements center around having certain attributes attached or inside the symbol.<br/>
- Running gsymcheck will check that all of these requirements are met. gsymcheck will output fatal errors which are quite serious and must be corrected. gsymcheck will also output warnings on things which should be fixed but are not fatal.<br/>
- For more information on the attributes presented here, please see the Master Attribute Document.
-</p>
-<ul>
-<li class="level1"><div class="li"> device=DEVICENAME should be placed somewhere in the symbol and made invisible. device= is the device name and is required. Typically the devicename is in all caps (capital letters). This attribute should not be used as a label. Use a separate text object for the label. If the object is a graphic then device= should be set to none (device=none). It is no longer required to attach this attribute anything; just having it exist as device=DEVICENAME is good enough.</div>
-</li>
-<li class="level1"><div class="li"> graphical=1 should exist somewhere in a symbol which is purely graphical (such as a title block or decon symbol). Symbols which have this attribute have no electrical or circuit significance. Donâ??t forget to set device=none.</div>
-</li>
-<li class="level1"><div class="li"> description=text should exist somewhere in the symbol. This attribute provides an one line description of the symbol.</div>
-</li>
-<li class="level1"><div class="li"> All pins should have a pair of attributes attached to them: pinseq=# and pinnumber=#. The first attribute, pinseq=# is just a sequence number and increments sequentially starting at 1. The second attribute pinnumber=# is the number of the pin. When a symbol is netlisted, the pin numbers are output in order of pin sequence. The pin number can be alphanumeric (i.e. like E or C).</div>
-</li>
-<li class="level1"><div class="li"> All pins should also have pinlabel=value attached to them. This attribute is the name or label of the pin (vs the pin number). This attribute is also used when a symbol is used in a hierarchical schematic. Please make this attribute green (instead of the default attribute yellow).</div>
-</li>
-<li class="level1"><div class="li"> All pins should also have pintype=value attached to them. This attribute describes the kind of a pin. Possible values are: in, out, io, oc, oe, pas, tp, tri, clk, pwr. Please see the Master Attribute Document for more info.</div>
-</li>
-<li class="level1"><div class="li"> If a component has multiple slots in a package (such as a 7400 (NAND) which has 4 NANDs per package) then you need a numslots=# attribute. The # is the number of slots the device has. numslots= should be exist somewhere in the symbol and made invisible. Additional slot related required attributes are described below.</div>
-</li>
-<li class="level1"><div class="li"> If a component has multiple slots in a physical package then you also need to include a slotdef=#:#,#,#… for every slot. The first # corresponds to the slot number. If a device has 4 slots then there should be slotdef=1:…, slotdef=2:…, slotdef=3:…, and slotdef=4:…, attributes existing somewhere in the symbol and made invisible. The subsequent # have a one-to-one correspondence to pinseq=# attributes and specify what corresponding pinnumber=# should be when that slot is set. See The attached 7400-1.sym as an example of how this should all work.</div>
-</li>
-<li class="level1"><div class="li"> It is recommended that all symbols which have slots have a slot=1 attribute inside the symbol.</div>
-</li>
-<li class="level1"><div class="li"> footprint=PACKAGENAME should exist somewhere in the symbol which might be used with the PCB netlister. PACKAGENAME is the PCB footprint or package type like DIP14 or DIP40. Please see the Footprint naming conventions chapter for further detail. See also the PCB documentation and gnetlist/docs/README.pcb for more info on this attribute.</div>
-</li>
-<li class="level1"><div class="li"> You should put a refdes=U? attribute inside the symbol. Make only the value visible and it will be promoted (attached to the outside of the symbol (so it can be edited) when the symbol is placed in a schematic.</div>
-</li>
-<li class="level1"><div class="li"> The label= attribute should not be attached anywhere in the symbol. It is obsolete.</div>
-</li>
-<li class="level1"><div class="li"> The name= attribute should not be attached anywhere in the symbol.</div>
-</li>
-<li class="level1"><div class="li"> The netname= attribute should not be attached anywhere in the symbol. It is only used in schematics.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Requirements" [2083-6223] -->
-<h2><a name="style" id="style">Style</a></h2>
-<div class="level2">
-
-<p>
-This section describes the style in which is used in the standard gEDA/gaf symbol library.
-</p>
-
-</div>
-<!-- SECTION "Style" [6224-6333] -->
-<h3><a name="text" id="text">Text</a></h3>
-<div class="level3">
-<ul>
-<li class="level1"><div class="li"> All Text labels should all be 10 pt in size.</div>
-</li>
-<li class="level1"><div class="li"> Text (labels not attributes) should be color number 9 (text | green).</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Text" [6334-6472] -->
-<h3><a name="attributes" id="attributes">Attributes</a></h3>
-<div class="level3">
-<ul>
-<li class="level1"><div class="li"> Pin numbers (which are attributes) should all be 8 pt in size.</div>
-</li>
-<li class="level1"><div class="li"> Attached attributes should be yellow. The color is set automatically to yellow if the text item is attached.</div>
-</li>
-<li class="level1"><div class="li"> The only exception to this is pinlabel= attributes, those should be color number 9 (text | green). If every text item within a symbol is yellow, the symbol looks too yellow.</div>
-</li>
-<li class="level1"><div class="li"> Attributes can be attached to some part of the symbol. Toplevel attributes (like the device= or net= attributes) used to be required to be attached to something to be attributes, but now they just have to exist in the symbol file as name=value.</div>
-</li>
-<li class="level1"><div class="li"> Expanding a bit on the last sentence, as long as the text item has the format name=value, it is considered an attribute. Attributes inside a symbol do not have to be attached to anything. In order to see hidden attributes in gschem select Edit/Show/Hide Inv Text.</div>
-</li>
-<li class="level1"><div class="li"> There is a symbol content versioning system in libgeda which is based on the symversion= attribute. Please see the Master Attribute Document for more information on using this versioning scheme.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Attributes" [6473-7569] -->
-<h3><a name="graphics" id="graphics">Graphics</a></h3>
-<div class="level3">
-<ul>
-<li class="level1"><div class="li"> Lines, boxes, arcs, and any other graphics should be color number 3 (graphic | green).</div>
-</li>
-<li class="level1"><div class="li"> Polarity bubbles should be color number 6 (logic bubble | cyan)</div>
-</li>
-<li class="level1"><div class="li"> If you are unsure on how to make a new symbol look or how big to make a new symbol, look at the existing symbols to get a feel for the appropriate appearance and size.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Graphics" [7570-7920] -->
-<h3><a name="pins" id="pins">Pins</a></h3>
-<div class="level3">
-<ul>
-<li class="level1"><div class="li"> Pins should all be 300 mils (3 grid spaces) long.</div>
-</li>
-<li class="level1"><div class="li"> For pins which are next to a logic bubble, make the pins 200 mils (2 grid spaces) long and then make the logic bubble 100 mils in diameter. In order to draw a 100 mil diameter circle, you will need to change the snap spacing to 50.</div>
-</li>
-<li class="level1"><div class="li"> A pin has two ends: one end has a red endpoint and one end that does not. The red endpoint is where nets can be connected. You can either rotate the pin so that this active end is in the right place or manually edit the symbol file changing the â??whichendâ?? parameter on the pin object. See the File Format document for more info.</div>
-</li>
-<li class="level1"><div class="li"> Be that all endpoints of pins which are meant to be connected to are on the 100 mil grid. The endpoint which is not active can be off the grid if necessary.</div>
-</li>
-<li class="level1"><div class="li"> Pins should be color number 1 (pins | white).</div>
-</li>
-<li class="level1"><div class="li"> Leave 400 mils (4 grid spaces) between (vertically) pins, unless you are drawing a special symbol, then just try to make it look good.</div>
-</li>
-<li class="level1"><div class="li"> Pin number attributes should be 50 mils above (or below; which ever makes the most sense) the pin which they are attached to.</div>
-</li>
-<li class="level1"><div class="li"> Input pins belong on the left and output pins belong on the right of the symbol.</div>
-</li>
-<li class="level1"><div class="li"> Please do not mix inputs and outputs on the same side of the symbol, unless absolutely necessary.</div>
-</li>
-<li class="level1"><div class="li"> You can have pins on the top or bottom of a symbol.</div>
-</li>
-<li class="level1"><div class="li"> The order for rows of pins (buses) should be LSB (least significant bit) to MSB (most significant bit). When drawing pins which are part of a bus, make sure the LSB of the bus is at the top (or for pins on top/bottom of a symbol, left of the rest of the other pins). Look at 74/74181-1.sym for a correct example of this order (A0 on top through A3 and B0 on top through B3). Violating this rule will make connecting buses much more diffcult.</div>
-</li>
-<li class="level1"><div class="li"> When placing pins on logic gates, be sure to place the smallest pin numbers toward the top (or left) and then increment going down (or across).</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Pins" [7921-9876] -->
-<h3><a name="electrical" id="electrical">Electrical</a></h3>
-<div class="level3">
-<ul>
-<li class="level1"><div class="li"> Do not draw power and ground pins. That information will be conveyed using attributes (see the netattrib document).</div>
-</li>
-<li class="level1"><div class="li"> The above rule can be broken if necessary, but keep in mind most of the standard library does not have power pins showing.</div>
-</li>
-<li class="level1"><div class="li"> Keep in mind, symbols are supposed to be symbolic, they do not represent the physical package that the device comes in.</div>
-</li>
-<li class="level1"><div class="li"> There is some disagreement on above, so this is okay too: Arrange the pins on a symbol logically so that they promote an uncluttered schematic. Note that this is frequently not the same pin arrangement as the physical device.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Electrical" [9877-10499] -->
-<h2><a name="footprint_naming_conventions" id="footprint_naming_conventions">Footprint naming conventions</a></h2>
-<div class="level2">
-
-<p>
-This section describes the conventions for naming of footprints used in gEDA/gaf.<br/>
- The purpose of the naming convention is to establish a standard to maintain the same naming convention through the different phases of the CAD chain. This helps in ensuring that the collaborative effort of gEDA/gaf is not lost.
-</p>
-
-</div>
-<!-- SECTION "Footprint naming conventions" [10500-10853] -->
-<h3><a name="notes" id="notes">Notes</a></h3>
-<div class="level3">
-<ul>
-<li class="level1"><div class="li"> Unless otherwise noted, numerical pin names will be used, starting from 1.</div>
-</li>
-<li class="level1"><div class="li"> n is for the pin count.</div>
-</li>
-<li class="level1"><div class="li"> m is for the pin spacing in mils.</div>
-</li>
-<li class="level1"><div class="li"> x is for the x dimension of the package (excluding pins). In particular this is used for the QFP package family.</div>
-</li>
-<li class="level1"><div class="li"> SMT means surface mount, other components are through-hole.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Notes" [10854-11196] -->
-<h3><a name="integrated_circuit_packages" id="integrated_circuit_packages">Integrated circuit packages</a></h3>
-<div class="level3">
-<ul>
-<li class="level1"><div class="li"> Dual in line packages with up to 22 100 mil spaced pins and 300 mil row spacing are called DIPn.</div>
-</li>
-<li class="level1"><div class="li"> Dual in line packages with 24 or more 100 mil spaced pins and 300 mil row spacing are called DIPnN.</div>
-</li>
-<li class="level1"><div class="li"> Dual in line packages with 100 mil spaced pins and 400 mil row spacing are called DIPnH.</div>
-</li>
-<li class="level1"><div class="li"> Dual in line packages with 24 or more 100 mil spaced pins and 600 mil row spacing are called DIPn.</div>
-</li>
-<li class="level1"><div class="li"> Shrink dual in line packages with up to 24 70 mil spaced pins and 300 mil row spacing are called SDIPn.</div>
-</li>
-<li class="level1"><div class="li"> Shrink dual in line packages with more than 24 70 mil spaced pins and 400 mil row spacing are called SDIPn.</div>
-</li>
-<li class="level1"><div class="li"> Single in line packages with 100 mil spaced pins are called SIPnN. See also JUMPER, below.</div>
-</li>
-<li class="level1"><div class="li"> Zig-zag in-line package are called ZIPn.</div>
-</li>
-<li class="level1"><div class="li"> Plastic leadless chip carrier with pin socket are called PLCCnX.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Integrated circuit packages" [11197-12065] -->
-<h3><a name="integrated_circuit_smt_packages" id="integrated_circuit_smt_packages">Integrated circuit SMT packages</a></h3>
-<div class="level3">
-<ul>
-<li class="level1"><div class="li"> Small outline SMT packages with up to 16 50 mil spaced pins and 150 mil total width are called SOn.</div>
-</li>
-<li class="level1"><div class="li"> Small outline SMT packages with more than 16 50 mil spaced pins and 150 mil total width are called SOnN.</div>
-</li>
-<li class="level1"><div class="li"> Small outline SMT packages with 50 mil spaced pins and 200 mil total width are called SOnM.</div>
-</li>
-<li class="level1"><div class="li"> Small outline SMT packages with up to 20 50 mil spaced pins and 300 mil total width are called SOnW.</div>
-</li>
-<li class="level1"><div class="li"> Small outline SMT packages with more than 20 50 mil spaced pins and 300 mil total width are called SOn.</div>
-</li>
-<li class="level1"><div class="li"> Small outline SMT packages with 44 or more 50 mil spaced pins and 525 mil total width are called SOn.</div>
-</li>
-<li class="level1"><div class="li"> Metric shrink small outline SMT packages with 0.65 mm spaced pins and 323 mil total width are called MSSOPn. NOTE: To be confirmed.</div>
-</li>
-<li class="level1"><div class="li"> Metric shrink small outline SMT packages with up to 44 0.65 mm spaced pins and 420 mil total width are called MSSOPnW.</div>
-</li>
-<li class="level1"><div class="li"> Metric shrink small outline SMT packages with over 44 0.65 mm spaced pins and 545 mil total width are called MSSOPnW.</div>
-</li>
-<li class="level1"><div class="li"> Shrink small outline SMT packages with 25 mil spaced pins and 420 mil total width are called SSOPnW.</div>
-</li>
-<li class="level1"><div class="li"> Quarter size small outline SMT packages with 25 mil spaced pins and 244 mil total width are called SSOPn.</div>
-</li>
-<li class="level1"><div class="li"> Thin small outline SMT packages with 21.65 mil spaced pins and 535 mil total width are called TSOPn.</div>
-</li>
-<li class="level1"><div class="li"> Thin small outline SMT packages with 20 mil spaced pins and 795 mil total width are called TSOPnA.</div>
-</li>
-<li class="level1"><div class="li"> Thin small outline SMT packages with 20 mil spaced pins and 559 mil total width are called TSOPnB.</div>
-</li>
-<li class="level1"><div class="li"> Thin shrink small outline SMT packages with up to 28 26 mil spaced pins and 260 mil total width are called TSSOPn.</div>
-</li>
-<li class="level1"><div class="li"> Thin shrink small outline SMT packages with over 28 20 mil spaced pins and 319 mil total width are called TSSOPn.</div>
-</li>
-<li class="level1"><div class="li"> Ultra Super Mini SMT packages with up to 16 0.5 mm spaced pins are called USn.</div>
-</li>
-<li class="level1"><div class="li"> Plastic leadless chip carrier SMT are called PLCCn.</div>
-</li>
-<li class="level1"><div class="li"> Square quad-side at pack SMT are called QFPn x.</div>
-</li>
-<li class="level1"><div class="li"> Rectangular quad-side at pack SMT are called QFPn R.</div>
-</li>
-<li class="level1"><div class="li"> Square low profile quad-side at pack SMT are called LQFPn x.</div>
-</li>
-<li class="level1"><div class="li"> Square thin quad-side at pack SMT are called TQFPn x.</div>
-</li>
-<li class="level1"><div class="li"> Square Quad-side at no-lead SMT without exposed paddle (back side contact) are called QFNn x. Pin count is n and package size is x mm.</div>
-</li>
-<li class="level1"><div class="li"> Square Quad-side at no-lead SMT with exposed paddle (back side contact) are called QFNn x EP. Pin count is n and package size is x mm.</div>
-</li>
-<li class="level1"><div class="li"> Thin profile square Quad-side at no-lead SMT without exposed paddle (back side contact) are called TQFNn x. Pin count is n and package size is x mm.</div>
-</li>
-<li class="level1"><div class="li"> Thin profile square Quad-side at no-lead SMT with exposed paddle (back side contact) are called TQFNn x EP. Pin count is n and package size is x mm.</div>
-</li>
-<li class="level1"><div class="li"> Dual in line style crystal oscillators are OSC8 and OSC14.</div>
-</li>
-<li class="level1"><div class="li"> 5 pin SOT SMT packages are SOT25 and SOT325.</div>
-</li>
-<li class="level1"><div class="li"> 6 pin SOT SMT packages are SOT26 and SOT326.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Integrated circuit SMT packages" [12066-14996] -->
-<h3><a name="basic_semiconductors" id="basic_semiconductors">Basic semiconductors</a></h3>
-<div class="level3">
-<ul>
-<li class="level1"><div class="li"> Axial diodes are called ALFm. Pin 1 is the cathode.</div>
-</li>
-<li class="level1"><div class="li"> Conventional through hole LED is LED3 and LED5 for 3 and 5 mm respectively. Pin 1 is plus. NOTE: Should probably be changed to be in line with diode convention.</div>
-</li>
-<li class="level1"><div class="li"> TO transistors are TO5, TO92, TO126, TO220 etc. Suxes may apply, e.g. TO126W is for wide, TO126S is for standing, TO126SW is for standing, wide.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Basic semiconductors" [14997-15399] -->
-<h3><a name="basic_smt_semiconductors" id="basic_smt_semiconductors">Basic SMT semiconductors</a></h3>
-<div class="level3">
-<ul>
-<li class="level1"><div class="li"> SOD diode SMT packages use their standard package name, e.g. SOD80, SOD87, SOD106A, SOD110. There are also SOD123, SOD323 with narrow pads.</div>
-</li>
-<li class="level1"><div class="li"> SOT transistor SMT packages use their standard package name, e.g. SOT23, SOT323. There is also an SC90.</div>
-</li>
-<li class="level1"><div class="li"> SOT transistor SMT packages with numbering as for diodes (pin 1 is cathode, pin 2 anode) are SOT23D, SOT323D.</div>
-</li>
-<li class="level1"><div class="li"> 4 pin SOT SMT packages are SOT89, SOT143, SOT223.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Basic SMT semiconductors" [15400-15855] -->
-<h3><a name="passive_components" id="passive_components">Passive components</a></h3>
-<div class="level3">
-<ul>
-<li class="level1"><div class="li"> Axial non-polar components (typically resistor, capacitor) are called ACYm.</div>
-</li>
-<li class="level1"><div class="li"> Bottom lead (radial) non-polar circular component (typically capacitor) is RCYm.</div>
-</li>
-<li class="level1"><div class="li"> Bottom lead non-polar rectangular component (typically capacitor) is BREm.</div>
-</li>
-<li class="level1"><div class="li"> A standard crystal is HC49, or other HC designations as required.</div>
-</li>
-<li class="level1"><div class="li"> Single row 100 mil pin spacing jumpers are JUMPERn. The main difference compared to single in line package is the hole size.</div>
-</li>
-<li class="level1"><div class="li"> Dual row 100 mil spacing headers with DIP pin numbering are HEADERn 1. Note that n is an even number.</div>
-</li>
-<li class="level1"><div class="li"> Dual row 100 mil spacing headers with ribbon cable numbering are HEADERn 2. Note that n is an even number.</div>
-</li>
-<li class="level1"><div class="li"> Angled full header connectors with latches are DIN41651 n.</div>
-</li>
-<li class="level1"><div class="li"> Standing full header connectors with latches are DIN41651 nS.</div>
-</li>
-<li class="level1"><div class="li"> DSUB connectors female are DBnF.</div>
-</li>
-<li class="level1"><div class="li"> DSUB connectors male are DBnM.</div>
-</li>
-<li class="level1"><div class="li"> Female DIN card-to-card connectors are DIN41612CnF. Add S suffix for standing.</div>
-</li>
-<li class="level1"><div class="li"> Male DIN card-to-card connectors are DIN41612CnM. Add S suffix for standing.</div>
-</li>
-<li class="level1"><div class="li"> AMP modular RJ connectors with screen are RJ11, RJ12 and RJ45.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Passive components" [15856-16977] -->
-<h3><a name="passive_smt_components" id="passive_smt_components">Passive SMT components</a></h3>
-<div class="level3">
-<ul>
-<li class="level1"><div class="li"> Standard SMT resistors, inductors, capacitors etc are 0201, 0402, 0603, 0805, 1206, 1210, 1806, 1812, 1825, 2020, 2706.</div>
-</li>
-<li class="level1"><div class="li"> Tantalum SMT capacitors are EIA3216, EIA3528, EIA6032, and EIA7343. Pin 1 is plus.</div>
-</li>
-<li class="level1"><div class="li"> SMT electrolytics are designated by can diameter in 1/10 mm: SME33, SME43, SME53, SME66, SME84, SME104.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Passive SMT components" [16978-17330] -->
-<h2><a name="hints_and_tips" id="hints_and_tips">Hints and Tips</a></h2>
-<div class="level2">
-
-<p>
-This section describes some hints and tips which will make your symbol creation experience easier.<br/>
-
-</p>
-<ul>
-<li class="level1"><div class="li"> Avoid drawing things off of the grid. If you do, you cannot move the object(s) using the move command (if the grid is on) since the object will be snapped to the grid. [This was an old bug, which I think has been fixed, but avoid doing this anyway]. Use the symbol translate command instead (or move the object with grid snap off)</div>
-</li>
-<li class="level1"><div class="li"> If you need a finer grid then use Options/Snap Grid Spacing… to set a finer grid snap spacing. Just remember to set this back to 100 once you are ready to translate the symbol to the origin.</div>
-</li>
-<li class="level1"><div class="li"> If you want to translate a symbol from the origin to elsewhere, then use the â??Symbol translateâ?? command and enter a non zero number. Make sure this number is a multiple of 100 (ie 1000, or 1100).</div>
-</li>
-<li class="level1"><div class="li"> Pins MUST be snapped on the 100 spaced grid (at least the end which will have nets connected to it).</div>
-</li>
-<li class="level1"><div class="li"> Pins MUST be snapped on the 100 spaced grid (at least the end which will have nets connected to it). Yes this is line a duplicate. I canâ??t stress this point enough.</div>
-</li>
-<li class="level1"><div class="li"> Remember that pins are special objects; if you want to add a pin, make sure it is a pin and not a line or net. Use the Add/Pin command to place a pin.</div>
-</li>
-<li class="level1"><div class="li"> Donâ??t include nets or buses inside symbols. That is not supported and doesnâ??t make much sense anyway.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Hints and Tips" [17331-18726] -->
-<h2><a name="example" id="example">Example</a></h2>
-<div class="level2">
-
-<p>
-This section provides a simple example which tries to follow all of the above rules. This symbol is of a 7400 (NAND gate).<br/>
-
-</p>
-
-<p>
-<pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">v 20031231 1
-L 300 200 300 800 3 0 0 0 -1 -1
-T 300 0 9 8 1 0 0 0 1
-7400
-L 300 800 700 800 3 0 0 0 -1 -1
-T 500 900 5 10 0 0 0 0 1
-device=7400
-T 500 1100 5 10 0 0 0 0 1
-slot=1
-T 500 1300 5 10 0 0 0 0 1
-numslots=4
-T 500 1500 5 10 0 0 0 0 1
-slotdef=1:1,2,3
-T 500 1700 5 10 0 0 0 0 1
-slotdef=2:4,5,6
-T 500 1900 5 10 0 0 0 0 1
-slotdef=3:9,10,8
-T 500 2100 5 10 0 0 0 0 1
-slotdef=4:12,13,11
-L 300 200 700 200 3 0 0 0 -1 -1
-A 700 500 300 270 180 3 0 0 0 -1 -1
-V 1050 500 50 6 0 0 0 -1 -1 0 -1 -1 -1 -1 -1
-P 1100 500 1300 500 1 0 1
-{
-T 1100 550 5 8 1 1 0 0 1
-pinnumber=3
-T 1100 450 5 8 0 1 0 2 1
-pinseq=3
-T 950 500 9 8 0 1 0 6 1
-pinlabel=Y
-T 950 500 5 8 0 1 0 8 1
-pintype=out
-}
-P 300 300 0 300 1 0 1
-{
-T 200 350 5 8 1 1 0 6 1
-pinnumber=2
-T 200 250 5 8 0 1 0 8 1
-pinseq=2
-T 350 300 9 8 0 1 0 0 1
-pinlabel=B
-T 350 300 5 8 0 1 0 2 1
-pintype=in
-}
-P 300 700 0 700 1 0 1
-{
-T 200 750 5 8 1 1 0 6 1
-pinnumber=1
-T 200 650 5 8 0 1 0 8 1
-pinseq=1
-T 350 700 9 8 0 1 0 0 1
-pinlabel=A
-T 350 700 5 8 0 1 0 2 1
-pintype=in
-}
-T 300 900 8 10 1 1 0 0 1
-refdes=U?
-T 500 2250 5 10 0 0 0 0 1
-footprint=DIP14
-T 500 2450 5 10 0 0 0 0 1
-description=4 NAND gates with 2 inputs
-T 500 2850 5 10 0 0 0 0 1
-net=Vcc:14
-T 500 3050 5 10 0 0 0 0 1
-net=GND:7
-T 500 2650 5 10 0 0 0 0 1
-documentation=http://www-s.ti.com/sc/ds/sn74hc00.pdf
-</font></pre>
-</p>
-
-<p>
-This example produces the following (using gschem):
-</p>
-
-<p>
-<a href="_detail/geda_symbol_7400-1_hidden.html" class="media" title="geda:symbol_7400-1_hidden.png"><img src="_media/geda_symbol_7400-1_hidden.png" class="media" title=":geda:symbol_7400-1_hidden.png" alt=":geda:symbol_7400-1_hidden.png" /></a>
-</p>
-
-<p>
-This is the same symbol with all the hidden text visible (via Edit/Show/Hide Inv Text):
-</p>
-
-<p>
-<a href="_detail/geda_symbol_7400-1.html" class="media" title="geda:symbol_7400-1.png"><img src="_media/geda_symbol_7400-1.png" class="media" title=":geda:symbol_7400-1.png" alt=":geda:symbol_7400-1.png" /></a>
-</p>
-
-</div>
-<!-- SECTION "Example" [18727-20443] -->
-<h2><a name="document_revision_history" id="document_revision_history">Document Revision History</a></h2>
-<div class="level2">
-<table class="inline">
- <tr>
- <td> September 14th, 2002</td><td>Created symbol.tex from symbols.html </td>
- </tr>
- <tr>
- <td> October 31st, 2002</td><td>Fixed bad example symbol </td>
- </tr>
- <tr>
- <td> February 11th, 2003</td><td>Footprint naming conventions added </td>
- </tr>
- <tr>
- <td> September 27th, 2003</td><td>Applied Dan McMahillâ??s QFP and QFN patch </td>
- </tr>
- <tr>
- <td> July 6th, 2004</td><td>Added a bunch more details/hints to the pin section </td>
- </tr>
-</table>
-
-</div>
-<!-- SECTION "Document Revision History" [20444-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/geda_scm.html b/docs/wiki/geda_scm.html
deleted file mode 100644
index 61792f7..0000000
--- a/docs/wiki/geda_scm.html
+++ /dev/null
@@ -1,467 +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>geda:scm</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2008-03-11T21:48:36-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/"; />
-<link rel="contents" href="http://geda.seul.org/wiki/geda:scm?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:scm"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:scm"; />
-<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="#geda_gaf_s_source_control_management" class="toc">gEDA/gaf's Source Control Management</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#installing_git_related_tools" class="toc">Installing git & related tools</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#debian-based" class="toc">Debian-based</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#fedora_linux" class="toc">Fedora Linux</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#learning_to_use_git" class="toc">Learning to use git</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#accessing_the_repository" class="toc">Accessing the repository</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#making_and_committing_changes" class="toc">Making and committing changes</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#setting_up_user_information" class="toc">Setting up user information</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#committing_patches_from_other_contributors" class="toc">Committing patches from other contributors</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#writing_good_commit_messages" class="toc">Writing good commit messages</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#push_is_destructive" class="toc">Push is Destructive</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#how_do_i" class="toc">How Do I ... ?</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#get_a_copy_of_geda_gaf_git_repository" class="toc">... get a copy of gEDA/gaf git repository?</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#keep_my_local_copy_current" class="toc">... keep my local copy current?</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#commit_my_changes_to_the_local_git_repository" class="toc">... commit my changes to the local git repository?</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#undo_any_uncommitted_local_changes" class="toc">... undo any uncommitted local changes?</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#fix_change_my_last_commit" class="toc">... fix/change my last commit?</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#track_a_branch" class="toc">... track a branch?</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#create_a_branch_starting_at_a_tag" class="toc">... create a branch (starting at a tag)?</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#recover_from_a_really_messed_up_local_repository" class="toc">... recover from a really messed up local repository?</a></span></div></li></ul>
-</li></ul>
-</li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="geda_gaf_s_source_control_management" id="geda_gaf_s_source_control_management">gEDA/gaf's Source Control Management</a></h1>
-<div class="level1">
-
-<p>
- gEDA uses <strong>git</strong> for source code management. git is a distributed version control system, where every user has his or her own full copy of the revision history.
-</p>
-<ul>
-<li class="level1"><div class="li"> <a href="http://git.or.cz/"; class="urlextern" title="http://git.or.cz/"; rel="nofollow">Official git website</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://www.kernel.org/pub/software/scm/git/docs/"; class="urlextern" title="http://www.kernel.org/pub/software/scm/git/docs/"; rel="nofollow">git documentation online</a></div>
-</li>
-<li class="level1"><div class="li"> <a href="http://en.wikipedia.org/wiki/Git_(software)" class="urlextern" title="http://en.wikipedia.org/wiki/Git_(software)" rel="nofollow">git Wikipedia page</a></div>
-</li>
-</ul>
-
-<p>
- The web interface to the gEDA git repository is at <a href="http://git.gpleda.org/"; class="urlextern" title="http://git.gpleda.org/"; rel="nofollow">http://git.gpleda.org/</a>.
-</p>
-
-</div>
-<!-- SECTION "gEDA/gaf's Source Control Management" [1-494] -->
-<h2><a name="installing_git_related_tools" id="installing_git_related_tools">Installing git & related tools</a></h2>
-<div class="level2">
-
-<p>
- The core git tools are of course required for using the repository, and the documentation is always useful. However, other tools are often helpful for working with git:
-</p>
-<ul>
-<li class="level1"><div class="li"> <a href="http://www.kernel.org/pub/software/scm/git/docs/gitk.html"; class="urlextern" title="http://www.kernel.org/pub/software/scm/git/docs/gitk.html"; rel="nofollow">gitk</a>, a visual history repository browser</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://www.procode.org/stgit/"; class="urlextern" title="http://www.procode.org/stgit/"; rel="nofollow">Stacked Git</a>, for working with patchsets</div>
-</li>
-</ul>
-
-<p>
- Make sure that you install at least version 1.5.x of git if you are planning on pushing changes to the central git repository.
-</p>
-
-</div>
-<!-- SECTION "Installing git & related tools" [495-1027] -->
-<h3><a name="debian-based" id="debian-based">Debian-based</a></h3>
-<div class="level3">
-<pre class="code">apt-get install git-core git-doc gitk stgit</pre>
-
-<p>
- you may also want:
-</p>
-<pre class="code">apt-get install git-email git-completion</pre>
-
-<p>
- Note, as of 2007/06/25, Debian stable (etch) and Debian testing (lenny) have git version 1.4.x. Debian unstable (sid) has 1.5.2.2.
-</p>
-
-</div>
-<!-- SECTION "Debian-based" [1028-1295] -->
-<h3><a name="fedora_linux" id="fedora_linux">Fedora Linux</a></h3>
-<div class="level3">
-<pre class="code">yum install git stgit </pre>
-
-</div>
-<!-- SECTION "Fedora Linux" [1296-1346] -->
-<h2><a name="learning_to_use_git" id="learning_to_use_git">Learning to use git</a></h2>
-<div class="level2">
-
-<p>
- The toplevel documentation for git can be found at:
-</p>
-
-<p>
-<a href="http://www.kernel.org/pub/software/scm/git/docs/"; class="urlextern" title="http://www.kernel.org/pub/software/scm/git/docs/"; rel="nofollow">Official git docs</a>
-</p>
-
-<p>
-The userâ??s manual for git can be found at:
-</p>
-
-<p>
-<a href="http://www.kernel.org/pub/software/scm/git/docs/user-manual.html"; class="urlextern" title="http://www.kernel.org/pub/software/scm/git/docs/user-manual.html"; rel="nofollow">git user manual</a>
-</p>
-
-<p>
-A current tutorial can be found at:
-</p>
-
-<p>
-<a href="http://www.kernel.org/pub/software/scm/git/docs/core-tutorial.html"; class="urlextern" title="http://www.kernel.org/pub/software/scm/git/docs/core-tutorial.html"; rel="nofollow">git core tutorial</a>
-</p>
-
-<p>
-Other nice tutorials/webpages:
-</p>
-
-<p>
-<a href="http://wiki.sourcemage.org/Git_Guide"; class="urlextern" title="http://wiki.sourcemage.org/Git_Guide"; rel="nofollow">Git Guide</a><br/>
- <a href="http://git.or.cz/course/index.html"; class="urlextern" title="http://git.or.cz/course/index.html"; rel="nofollow">git Crash Courses</a><br/>
- <a href="http://www.kernel.org/pub/software/scm/git/docs/tutorial.html"; class="urlextern" title="http://www.kernel.org/pub/software/scm/git/docs/tutorial.html"; rel="nofollow">Git for Everyone</a><br/>
-
-</p>
-
-<p>
-Keep in mind that some of these tutorials are a little dated and may not cover current git syntax.
-</p>
-
-</div>
-<!-- SECTION "Learning to use git" [1347-2097] -->
-<h2><a name="accessing_the_repository" id="accessing_the_repository">Accessing the repository</a></h2>
-<div class="level2">
-
-<p>
- To clone the gaf.git repository using anonymous git access:
-</p>
-<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>
-
-<p>
- If you have ssh access you will also need to edit your ~/.ssh/config file (create it if it doesnâ??t exist) and put the following text into it:
-</p>
-<pre class="code">Host git.gpleda.org
-Port 5022</pre>
-
-<p>
- Finally, it is possible to access the repository using <acronym title="Concurrent Versions System">CVS</acronym>, as there is a git-cvsserver running. This is read-only access.
-</p>
-<pre class="code"> export CVSROOT=:pserver:anonymous@xxxxxxxxxxxxxx/home/git/gaf.git
- cvs co master </pre>
-
-<p>
- You can only checkout exported heads (for example: master).
-</p>
-
-</div>
-<!-- SECTION "Accessing the repository" [2098-3082] -->
-<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" [3083-3127] -->
-<h3><a name="setting_up_user_information" id="setting_up_user_information">Setting up user information</a></h3>
-<div class="level3">
-
-<p>
- You should make sure that your username & e-mail address are set in your git configuration file.
-</p>
-<pre class="code">$ git config --global user.name "Your Name Comes Here"
-$ git config --global user.email you@xxxxxxxxxxxxxxxxxxxxxx</pre>
-
-</div>
-<!-- SECTION "Setting up user information" [3128-3385] -->
-<h3><a name="committing_patches_from_other_contributors" id="committing_patches_from_other_contributors">Committing patches from other contributors</a></h3>
-<div class="level3">
-
-<p>
- If you apply a patch from someone else (e.g. from a SourceForge patch record) there are a few things to consider. Git stores two different names and e-mail addresses for a given commit: the â??authorâ?? of the patch, and the â??committerâ?? of the patch, so these details must be set correctly when making the commit.
-</p>
-
-<p>
-First of all, check a few things:
-</p>
-<ul>
-<li class="level1"><div class="li"> You have the latest version of the patch.</div>
-</li>
-<li class="level1"><div class="li"> The author of the patch is happy for it to be committed (and wasnâ??t still working on it)</div>
-</li>
-<li class="level1"><div class="li"> That the youâ??re happy with the patch, and taking responsibility for committing those changes.</div>
-</li>
-</ul>
-
-<p>
- For simplicity, start from an unmodified up-to date tree (git status shows no changes).
-</p>
-
-<p>
-Apply the patch as usual (as an example):
-</p>
-<pre class="code">$ patch -p1 < example_changes.patch</pre>
-
-<p>
- You can also use the git apply command:
-</p>
-<pre class="code">$ git apply example_changes.patch</pre>
-
-<p>
- If the patch needs any minor editing before it is committed (eg. white-space changes), please inform the author this was done. They may have other work based on their patch and will want to know if there were changes to the applied version.
-</p>
-
-<p>
-Note: <em>This is easy to miss accidentally if your editor introduces tabs. Please avoid letting it do so!</em>
-</p>
-
-<p>
-For every file changed, added or removed, you need to inform git before it will commit the changes. To see the modified files, run:
-</p>
-<pre class="code">$ git status</pre>
-
-<p>
- For speed, the command:
-</p>
-<pre class="code">$ git add -u</pre>
-
-<p>
- will update all files which git tracks, including any files which were deleted.
-</p>
-
-<p>
-For adding any new files the patch introduced, use the command
-</p>
-<pre class="code">$ git add new_file.c</pre>
-
-<p>
- Note: git add also takes wild-cards.
-</p>
-
-<p>
-Commit the patch, making sure that the Authorâ??s name and e-mail address are specified:
-</p>
-<pre class="code">$ git commit --author "Author's Name Comes Here <author@xxxxxxxxxxx>"</pre>
-
-<p>
- As an alternative, you can set the GIT_AUTHOR_NAME and GIT_AUTHOR_EMAIL environment variables before issuing the normal commit command
-</p>
-
-</div>
-<!-- SECTION "Committing patches from other contributors" [3386-5315] -->
-<h3><a name="writing_good_commit_messages" id="writing_good_commit_messages">Writing good commit messages</a></h3>
-<div class="level3">
-
-<p>
- The commit message format is as follows: a *strictly* one-line summary of the patch, followed by a blank line, followed by a long description. If you can fit the whole description of the patch on one line, thatâ??s fine; donâ??t bother with the long description.
-</p>
-
-<p>
-The one-line summary is used for generating e-mail subject lines, and for the gitk & gitweb log displays. Having a good one-line summary is really useful, because it means those tools can be used to quickly find a commit of interest.
-</p>
-
-<p>
-<strong>Do not</strong> put a list of files changed into commit messages. This information can be trivially obtained using the git tools.
-</p>
-
-<p>
-Example:
-</p>
-<pre class="code">
-Added new GedaList class derived from GObject
-
-This abstracts a GList with API for write access. Its main use is in list
-change notification, as it emits a "changed" g_signal when modified.
-Read only access to the underlying GList is provided by an accessor,
-currenly implemented as a macro.
-</pre>
-
-</div>
-<!-- SECTION "Writing good commit messages" [5316-6297] -->
-<h3><a name="push_is_destructive" id="push_is_destructive">Push is Destructive</a></h3>
-<div class="level3">
-
-<p>
- <strong>Warning: pushing changes to the remote repository is destructive</strong>
-</p>
-
-<p>
-Unlike <acronym title="Concurrent Versions System">CVS</acronym>, it is not the committing of changes which changes the master repository, but pushing changes using git-push. You should always double- (or triple-) check that the commits you are about to push are actually meant for the main repository.
-</p>
-
-</div>
-<!-- SECTION "Push is Destructive" [6298-6651] -->
-<h2><a name="how_do_i" id="how_do_i">How Do I ... ?</a></h2>
-<div class="level2">
-
-<p>
- For a more information please checkout the <a href="http://wiki.sourcemage.org/Git_Guide"; class="urlextern" title="http://wiki.sourcemage.org/Git_Guide"; rel="nofollow">Git Guide</a>.
-</p>
-
-</div>
-<!-- SECTION "How Do I ... ?" [6652-6775] -->
-<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">
-
-<p>
- For anonymous read-only access:
-</p>
-<pre class="code">$ git clone git://git.gpleda.org/gaf</pre>
-
-<p>
- For developers with read/write access:
-</p>
-<pre class="code">$ git clone git://git.gpleda.org/home/git/gaf.git</pre>
-
-</div>
-<!-- SECTION "... get a copy of gEDA/gaf git repository?" [6776-6995] -->
-<h3><a name="keep_my_local_copy_current" id="keep_my_local_copy_current">... keep my local copy current?</a></h3>
-<div class="level3">
-
-<p>
- For those who are are not merging changes back into the central git repository you can run:
-</p>
-<pre class="code">$ git pull</pre>
-
-<p>
- However, for those of you who are going to be pushing your changes back into the central git repository, using git pull will clutter up the history with merge messages (â??Merge branch â??masterâ??â??). To avoid this you should run:
-</p>
-<pre class="code">$ git fetch
-$ git rebase origin</pre>
-
-</div>
-<!-- SECTION "... keep my local copy current?" [6996-7410] -->
-<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>
-
-<p>
- This command will find all changed files that git knows about (added with git-add) and prompt you for a commit message. Be sure to follow the above commit message convention if you plan on pushing your changes to the central repository.
-</p>
-
-<p>
-If you want to commit files in the current directory or want to explicitly commit only certain files, do not specify the -a flag and/or specify the individual filenames on the command line like:
-</p>
-<pre class="code">$ git commit filename1 filename2</pre>
-
-</div>
-<!-- SECTION "... commit my changes to the local git repository?" [7411-7964] -->
-<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>
-
-<p>
- Note this will discard any changes to any files that are being tracked by git.
-</p>
-
-</div>
-<!-- SECTION "... undo any uncommitted local changes?" [7965-8118] -->
-<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
-$ git commit --amend filename1..filenameN </pre>
-
-<p>
- This will pickup any changes you made and recommit them again with the previous commit message.
-</p>
-
-</div>
-<!-- SECTION "... fix/change my last commit?" [8119-8327] -->
-<h3><a name="track_a_branch" id="track_a_branch">... track a branch?</a></h3>
-<div class="level3">
-<pre class="code">$ git checkout --track -b <local name> origin/<remote name></pre>
-
-<p>
- This will create a branch with the <local name> which tracks the <remote name>â??d branch.
-</p>
-
-</div>
-<!-- SECTION "... track a branch?" [8328-8511] -->
-<h3><a name="create_a_branch_starting_at_a_tag" id="create_a_branch_starting_at_a_tag">... create a branch (starting at a tag)?</a></h3>
-<div class="level3">
-
-<p>
- Run the following commands (using the stable-1.4 branch as an example):
-</p>
-<pre class="code"> $ git branch stable-1.4 1.4.0-20080127
- $ git checkout stable-1.4
- <make changes>
- $ git commit -a </pre>
-
-<p>
- To publish this branch in the central repository (requires write access to the central repository):
-</p>
-<pre class="code"> $ git push origin stable-1.4</pre>
-
-</div>
-<!-- SECTION "... create a branch (starting at a tag)?" [8512-8881] -->
-<h3><a name="recover_from_a_really_messed_up_local_repository" id="recover_from_a_really_messed_up_local_repository">... recover from a really messed up local repository?</a></h3>
-<div class="level3">
-
-<p>
- First off, do not push any repository that you think is somehow messed up. Ask one of the experienced git people first.
-</p>
-
-<p>
-Second, the command that will really save your bacon is git-reflog. Using it works something like this:
-</p>
-<pre class="code"> $ git reflog
- 086908e... HEAD@{0}: cherry-pick: Last minute updates to the READMEs for all pro
- 2a79a23... HEAD@{1}: checkout: moving to master
- 2a79a23... HEAD@{2}: checkout: moving to master
- ...
- $ git reset --hard HEAD@{1}</pre>
-
-<p>
- The last command (git reset –hard …) will rollback all your changes to the â??checkout: moving to masterâ??. Remember: donâ??t panic! Most things are fixable when using git.
-</p>
-
-</div>
-<!-- SECTION "... recover from a really messed up local repository?" [8882-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/geda_sdb_howto.html b/docs/wiki/geda_sdb_howto.html
deleted file mode 100644
index 5f3a06a..0000000
--- a/docs/wiki/geda_sdb_howto.html
+++ /dev/null
@@ -1,1079 +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>geda:sdb_howto</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="keywords" content="geda,sdb_howto" />
-<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/geda:sdb_howto?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:sdb_howto"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:sdb_howto"; />
-<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="#spice_on_geda_howto" class="toc">SPICE on gEDA HOWTO</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#introduction" class="toc">Introduction</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#overview" class="toc">Overview</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#spice-sdb_netlister_installation_and_configuration" class="toc">Spice-sdb netlister installation and configuration</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#design_simulation_flow_summary" class="toc">Design/simulation flow summary</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#preliminary_notes_about_symbols_and_spice_model_files" class="toc">Preliminary notes about symbols and SPICE model files</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#symbol_creation_for_spice_netlisting" class="toc">Symbol creation for SPICE netlisting.</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#spice_file_configuration" class="toc">SPICE file configuration</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#schematic_capture" class="toc">Schematic capture</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#gschem_attributes_for_spice_netlisting" class="toc">Gschem attributes for spice netlisting</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#handling_hierarchical_models" class="toc">Handling hierarchical models</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#spice_netlist_generation" class="toc">SPICE netlist generation</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#creating_the_netlist" class="toc">Creating the netlist</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#common_netlisting_problems" class="toc">Common netlisting problems</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#spice_simulation" class="toc">SPICE simulation</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#ltspice" class="toc">LTSpice</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#ngspice_and_tclspice" class="toc">Ngspice and tclspice</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#appendix" class="toc">Appendix</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#component_attribute_summary" class="toc">Component attribute summary</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#valid_type_values" class="toc">Valid "type" values</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#document_history" class="toc">Document History</a></span></div></li></ul>
-</li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="spice_on_geda_howto" id="spice_on_geda_howto">SPICE on gEDA HOWTO</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "SPICE on gEDA HOWTO" [1-34] -->
-<h2><a name="introduction" id="introduction">Introduction</a></h2>
-<div class="level2">
-
-<p>
-The purpose of this document is to explain how to use the gEDA tools (running on Linux) to perform SPICE simulations. In particular, this HOWTO documents the usage of spice-sdb, which is an advanced backend for the gEDA netlister (gnetlist) used to create SPICE netlists. This HOWTO also provides advice about using LTSpice and/or ngspice to simulate a circuit netlisted with spice-sdb. I assume that you are already familiar with electronic design, the mechanics of schematic capture using EDA tools, and SPICE simulation in general. I also assume that you are reasonably familiar with the Linux operating system and its development environment.
-</p>
-
-</div>
-<!-- SECTION "Introduction" [35-708] -->
-<h3><a name="overview" id="overview">Overview</a></h3>
-<div class="level3">
-
-<p>
-From the top level, SPICE simulation in gEDA proceeds via the following steps:
-</p>
-<ol>
-<li class="level1"><div class="li"> Creation and gathering of schematic symbols and SPICE model files. Oftentimes, the SPICE model files are obtained from the component vendor.</div>
-</li>
-<li class="level1"><div class="li"> Schematic capture using symbols and SPICE models created in step 1.</div>
-</li>
-<li class="level1"><div class="li"> Netlist generation from the schematic created in step 2.</div>
-</li>
-<li class="level1"><div class="li"> SPICE simulation of the circuit described by the netlist created in step 3.</div>
-</li>
-</ol>
-
-<p>
- To create a SPICE netlist, the netlister (gnetlist) iterates through the entire schematic and looks at several parts of each componentâ??s symbol in order to create a blob of SPICE code. In general, each component can generate one or more lines of SPICE code. Component information needed by the netlister is held in two places:
-</p>
-<ol>
-<li class="level1"><div class="li"> The symbol itself, in the â??deviceâ?? attribute, which is attached when the symbol is created, and is typically accessed through the symbol editor.</div>
-</li>
-<li class="level1"><div class="li"> In attributes manually attached to the component during schematic capture using gschem.</div>
-</li>
-</ol>
-
-<p>
- Since there are two places the netlister looks for information, you must make sure that the required information is available in both places.
-</p>
-
-</div>
-<!-- SECTION "Overview" [709-1877] -->
-<h3><a name="spice-sdb_netlister_installation_and_configuration" id="spice-sdb_netlister_installation_and_configuration">Spice-sdb netlister installation and configuration</a></h3>
-<div class="level3">
-
-<p>
-This document was originally written around gEDA/gaf 20030223, and the SPICE netlister spice-SDB. Starting with gEDA/gaf 20030525, my netlister was incorporated into the main gEDA distribution, and renamed spice-sdb (lower case sdb). <strong>For smoothest operation, you are best off just downloading and installing the latest version of gEDA.</strong> However, if you have a gEDA version predating 20030525, and you want to hack, you can download and install spice-SDB using the instructions provided on <a href="http://www.brorson.com/gEDA/SPICE/SPICEonLinux.html"; class="urlextern" title="http://www.brorson.com/gEDA/SPICE/SPICEonLinux.html"; rel="nofollow">http://www.brorson.com/gEDA/SPICE/SPICEonLinux.html</a>. In any event, itâ??s a good idea to make sure that the file gnet-spice-sdb.scm is present in your scheme directory (usually <strong><code>${prefix}/geda/share/gEDA/scheme</code></strong>) if you are interested in performing SPICE simulations with gEDA as described in this HOWTO.
-</p>
-
-</div>
-<!-- SECTION "Spice-sdb netlister installation and configuration" [1878-2744] -->
-<h3><a name="design_simulation_flow_summary" id="design_simulation_flow_summary">Design/simulation flow summary</a></h3>
-<div class="level3">
-
-<p>
-The detailed steps required to create a circuit and simulate it with gEDA look like this:
-</p>
-<ol>
-<li class="level1"><div class="li"> Schematic symbol creation with correct â??deviceâ?? attribute. (Usually, the symbols have already been created with the correct â??deviceâ?? attribute, but if you are having problems, it doesnâ??t hurt to check them.)</div>
-</li>
-<li class="level1"><div class="li"> Schematic capture using gschem.</div>
-</li>
-<li class="level1"><div class="li"> Assignment of SPICE attributes (value, model, file, type, etc.) to components using gschem.</div>
-</li>
-<li class="level1"><div class="li"> Assignment of <strong><code>refdes</code></strong> using e.g. refdes_renum.</div>
-</li>
-<li class="level1"><div class="li"> Creation of netlist using â??gnetlist -g spice-sdbâ??.</div>
-</li>
-<li class="level1"><div class="li"> Check netlist for correctness (manually open and inspect netlist).</div>
-</li>
-<li class="level1"><div class="li"> Run spice using a simulator such as LTSpice or ngspice.</div>
-</li>
-<li class="level1"><div class="li"> Plot/analyze results (often plotting/analysis tools are incorporated in the simulator).</div>
-</li>
-</ol>
-
-<p>
- The purpose of this HOWTO is to provide the detailed understanding necessary to successfully navigate this process.
-</p>
-
-</div>
-<!-- SECTION "Design/simulation flow summary" [2745-3673] -->
-<h2><a name="preliminary_notes_about_symbols_and_spice_model_files" id="preliminary_notes_about_symbols_and_spice_model_files">Preliminary notes about symbols and SPICE model files</a></h2>
-<div class="level2">
-
-</div>
-<!-- SECTION "Preliminary notes about symbols and SPICE model files" [3674-3739] -->
-<h3><a name="symbol_creation_for_spice_netlisting" id="symbol_creation_for_spice_netlisting">Symbol creation for SPICE netlisting.</a></h3>
-<div class="level3">
-
-<p>
-The SPICE netlister recognizes a particular symbol in two ways:
-</p>
-<ol>
-<li class="level1"><div class="li"> The symbolâ??s â??deviceâ?? attribute</div>
-</li>
-<li class="level1"><div class="li"> The symbolâ??s <strong><code>refdes</code></strong>. Both of these attributes are attached to the symbol when the symbol is created.</div>
-</li>
-</ol>
-
-<p>
- Each symbol has a <strong><code>device</code></strong> attribute attached to it. The <strong><code>device</code></strong> attribute is the first thing the netlister examines when processing the symbol. There are a number of devices which are native to the netlister, meaning that the netlister knows exactly how to deal with these types of devices. Native device types include RESISTOR, CAPACITOR, NPN_TRANSISTOR, etc. The entire list of native devices is present in the <a href="#appendix" title="geda:sdb_howto ↵" class="wikilink1">Appendix</a>.<br/>
- The <strong><code>device</code></strong> attribute is hidden during normal use of gschem. Most often, the symbolâ??s creator has already given the symbol the correct <strong><code>device</code></strong> attribute. However, because the <strong><code>device</code></strong> attribute is hidden from the ordinary user, it can sometimes cause problems with SPICE netlist creation when it is set to an unexpected value. To view the <strong><code>device</code></strong> attribute, go into the symbol editor (select the symbol to edit, and do â??Hierarchyâ?? → â??down symbolâ??), and turn on invisible attributes (Edit → show/hide inv text). If the <strong><code>device</code></strong> attribute is incorrect, you may change it by editing the symbol itself using a text editor.<br/>
- If a symbol is not native (i.e. the netlister doesnâ??t recognize it as a built-in type), the netlister relies upon the first letter of the <strong><code>refdes</code></strong> to determine how to process the symbol. The <strong><code>refdes</code></strong> prefix is also built into the symbol when it is created. Example <strong><code>refdes</code></strong> prefixes are R for resistors, C for capacitors, Q for transistors, etc. <strong><code>refdes</code></strong> prefixes correct for SPICE are listed in the <a href="#appendix" title="geda:sdb_howto ↵" class="wikilink1">Appendix</a>. Note that relying upon the <strong><code>refdes</code></strong> to identify the component for SPICE is not foolproof – for example, the netlister cannot distinguish between NPN and PNP transistors based upon the <strong><code>refdes</code></strong>. Therefore, it is always best to use a native â??deviceâ?? in your symbols.
-</p>
-
-</div>
-<!-- SECTION "Symbol creation for SPICE netlisting." [3740-5819] -->
-<h3><a name="spice_file_configuration" id="spice_file_configuration">SPICE file configuration</a></h3>
-<div class="level3">
-
-<p>
-Files holding complicated SPICE models or other SPICE code may be incorporated into the final SPICE netlist by including appropriate symbols into the schematic. SPICE model files are usually obtained from component vendors. Dealing with these files is straightforward. However, some issues should be kept in mind when preparing models for use during schematic capture:
-</p>
-<ul>
-<li class="level1"><div class="li"> It is usually prudent to place these files into a dedicated directory distinct from the symbol directories.</div>
-</li>
-<li class="level1"><div class="li"> Make sure that the SPICE files pin assignments correctly correspond to the pins as defined in the componentâ??s symbol.</div>
-</li>
-<li class="level1"><div class="li"> Make sure that the last character in a SPICE model file is a carriage return. If no carriage return exists, then the next component listed in the netlist may be placed on the same line as the last line of the SPICE model file.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "SPICE file configuration" [5820-6689] -->
-<h2><a name="schematic_capture" id="schematic_capture">Schematic capture</a></h2>
-<div class="level2">
-
-<p>
-Schematic capture is the process by which one uses a special-purpose drawing program to draw a schematic diagram of the circuit under design. In the gEDA environment, the schematic capture program is called â??gschemâ??. I assume you already know how to use gschem. For the purposes of creating SPICE netlists, you must use gschem to attach attributes to components, and possibly also incorporate other SPICE directives into your netlist. After you are done with schematic capture, you create the SPICE netlist by running gEDAâ??s netlister â??gnetlistâ?? on your design.
-</p>
-
-</div>
-<!-- SECTION "Schematic capture" [6690-7282] -->
-<h3><a name="gschem_attributes_for_spice_netlisting" id="gschem_attributes_for_spice_netlisting">Gschem attributes for spice netlisting</a></h3>
-<div class="level3">
-
-<p>
-There are several ways that spice attributes may be associated with a component using gschem. The way you choose to do this depends upon many factors, including the type of component, and the size and format of the SPICE model.
-</p>
-
-</div>
-
-<h4><a name="component_attributes_and_meanings" id="component_attributes_and_meanings">Component attributes and meanings</a></h4>
-<div class="level4">
-
-<p>
-The following attributes are meaningful for SPICE netlisting, and may be attached from within gschem:
-</p>
-<table class="inline">
- <tr>
- <td><strong><code>refdes</code></strong></td><td>The reference designator of the component. Valid values depend upon the component type and are given in the appendix.</td>
- </tr>
- <tr>
- <td><strong><code>value</code></strong></td><td>For passives, this is the component value. For actives, this is the type (model no) of the component (e.g. 2N3904, uA741). When a model for an active is instantiated separately from the component itself, the â??valueâ?? attribute holds the name of the spice model.</td>
- </tr>
- <tr>
- <td><strong><code>model</code></strong></td><td>This holds a one line spice model for the component.</td>
- </tr>
- <tr>
- <td><strong><code>file</code></strong></td><td>This holds the name of a file. Typically, this is a file holding e.g. a SPICE .MODEL, .SUBCKT, or other SPICE code.</td>
- </tr>
- <tr>
- <td><strong><code>model-name</code></strong></td><td>This holds the name of the spice model referred to in a .MODEL or .SUBCKT statement. â??model-nameâ?? is mainly used to identify the spice model name in the symbol â??spice-model-1.symâ??. Active components should call out this name in the â??deviceâ?? attribute to associate the component with its particular spice model or subcircuit.</td>
- </tr>
- <tr>
- <td><strong><code>type</code></strong></td><td>This specifies the type of component and is used by spice when interpreting the model parameters. Valid values depend upon the device being modeled.</td>
- </tr>
-</table>
-
-</div>
-
-<h4><a name="refdes_conventions" id="refdes_conventions">refdes conventions</a></h4>
-<div class="level4">
-
-<p>
-As a prerequisite to handling SPICE-related attributes, the SPICE netlister requires that all components must have a refdes attached to them. The refdes may be attached either by hand (which is laborious), or using the program refdes_renum included in the gEDA distribution.<br/>
- Note that the first letter of the refdes must correspond to the appropriate letter for spice simulation. The refdes convention is given in the <a href="#appendix" title="geda:sdb_howto ↵" class="wikilink1">Appendix</a>.
-</p>
-
-</div>
-
-<h4><a name="passives" id="passives">Passives</a></h4>
-<div class="level4">
-
-</div>
-
-<h5><a name="basic_passives" id="basic_passives">Basic passives</a></h5>
-<div class="level5">
-
-<p>
-The most basic components which one encounters in spice are passive components like resistors and capacitors which have numeric values, but no other modeling attributes. In this case the following attributes must be filled in:
-</p>
-<table class="inline">
- <tr>
- <td><strong><code>refdes</code></strong></td><td>The correct <strong><code>refdes</code></strong> for the component.</td>
- </tr>
- <tr>
- <td><strong><code>value</code></strong></td><td>For passives, this is the numeric value of the component (e.g. 100pF). For actives, this attribute may be filled in, but if no model attribute is available elsewhere in the schematic, the value is not used (in SPICE netlisting, anyway).</td>
- </tr>
-</table>
-
-<p>
- If only a <strong><code>refdes</code></strong> and value attribute are encountered, the netlister will write a single line into the output file.<br/>
- Example resistor:
-</p>
-<pre class="code">refdes = R2
-value = 220
-SPICE line generated: R2 0 4 220</pre>
-
-<p>
-Note that â??0â?? and â??4â?? correspond to the net nodes connected to the component, and are generated automatically by gnetlist.<br/>
- Example capacitor:
-</p>
-<pre class="code">refdes = C22
-value = 1UF
-SPICE line generated: C22 4 23 1UF</pre>
-
-</div>
-
-<h5><a name="passives_with_additional_attributes" id="passives_with_additional_attributes">Passives with additional attributes</a></h5>
-<div class="level5">
-
-<p>
-Oftentimes, passive components have additional attributes attached to them for spice simulation. Examples of such attributes are temperature coefficients (for resistors) and initial conditions (for reactive components). These additional components may be incorporated into the SPICE file by simply attaching them to the componentâ??s â??modelâ?? attribute. Specifically, the required attributes are:
-</p>
-<table class="inline">
- <tr>
- <td><strong><code>refdes</code></strong></td><td>Correct component <strong><code>refdes</code></strong>.</td>
- </tr>
- <tr>
- <td><strong><code>value</code></strong></td><td>Numerical component value, as always.</td>
- </tr>
- <tr>
- <td><strong><code>model</code></strong></td><td>One line string holding additional parameters, formatted as a valid SPICE string.</td>
- </tr>
-</table>
-
-<p>
- This string is placed after the component value in the line generated by gnetlist. Therefore, it is important to format the string placed in the <strong><code>model</code></strong> line to be valid SPICE code. Otherwise, you will risk causing the SPICE simulator to barf.<br/>
- Example resistor:
-</p>
-<pre class="code">refdes = R5
-value = 1MEG
-model = TC=0.001,0.015
-SPICE line generated: R2 0 4 220 TC=0.001,0.015</pre>
-
-</div>
-
-<h4><a name="transistors_and_diodes" id="transistors_and_diodes">Transistors and diodes</a></h4>
-<div class="level4">
-
-<p>
-Transistors and diodes are generally accompanied by a device-specific model – otherwise, SPICE simulation is pointless. The SPICE model may be either a short, one-line string of parameters, or a multi-line set of SPICE parameters. A typical one-line parameter string is a short list of parameters describing a small-signal diode. Typical multi-line models come from component vendors, who often provide models for their components in a text file. Since there are two broad formats of SPICE information, there are two approaches to incorporating these parameters into the schematic:
-</p>
-
-</div>
-
-<h5><a name="one_line_string_of_spice_parameters" id="one_line_string_of_spice_parameters">One line string of SPICE parameters</a></h5>
-<div class="level5">
-
-<p>
-To incorporate a one line string of SPICE parameters into the netlist, the following attributes must be attached to the component:
-</p>
-<table class="inline">
- <tr>
- <td><strong><code>refdes</code></strong></td><td>Correct component refdes.</td>
- </tr>
- <tr>
- <td><strong><code>value</code></strong></td><td>The model number or part number of the component.</td>
- </tr>
- <tr>
- <td><strong><code>model-name</code></strong></td><td>The name you wish to give the SPICE model. This is usually the model number or part number of the component. If you have already attached a â??valueâ?? attribute to the component, this parameter is optional.</td>
- </tr>
- <tr>
- <td><strong><code>model</code></strong></td><td>One line string holding additional parameters. Do not place the model parameters in parentheses – gnetlist will do this for you.</td>
- </tr>
-</table>
-
-<p>
- Example diode:
-</p>
-<pre class="code">refdes = D5
-model-name = 1N1004
-model = IS=0.5UA RS=6 BV=5.20
-SPICE lines generated:
-D5 2 6 1N1004
-MODEL 1N1004 D (IS=0.5UA RS=6 BV=5.20)</pre>
-
-</div>
-
-<h5><a name="spice_model_file" id="spice_model_file">SPICE model file</a></h5>
-<div class="level5">
-
-<p>
-To incorporate a file-full of SPICE parameters into the netlist, the following attributes must be attached to the component:
-</p>
-<table class="inline">
- <tr>
- <td><strong><code>refdes</code></strong></td><td>Correct component refdes.</td>
- </tr>
- <tr>
- <td><strong><code>value</code></strong></td><td>The model number or part number of the component.</td>
- </tr>
- <tr>
- <td><strong><code>model-name</code></strong></td><td>The name you wish to give the SPICE model. This is usually the model number or part number of the component. If you have already attached a â??valueâ?? attribute to the component, this parameter is optional.</td>
- </tr>
- <tr>
- <td><strong><code>file</code></strong></td><td>The file name of the SPICE model which you wish to incorporate into the netlist. This file name may specify either a relative or an absolute path, but it is probably better to use an absolute path to avoid problems if you ever move your schematic directory.</td>
- </tr>
-</table>
-
-<p>
- Note that you need to make sure that the model name held in your SPICE model file is the same as the <strong><code>value</code></strong> or <strong><code>model-name</code></strong> attributes you attached to the component. It is also a good idea to verify that the pin assignments in the model file correspond to the pin assignments made by the component symbol.
-</p>
-
-</div>
-
-<h4><a name="actives_--_integrated_circuits" id="actives_--_integrated_circuits">Actives -- integrated circuits</a></h4>
-<div class="level4">
-
-<p>
-Integrated circuits are incorporated into the netlist similarly to transistors and diodes. As such, you may incorporate the spice information either as a one-line parameter string, or as a model file.
-</p>
-
-</div>
-
-<h5><a name="one_line_string_of_spice_parameters1" id="one_line_string_of_spice_parameters1">One line string of SPICE parameters</a></h5>
-<div class="level5">
-
-<p>
-To incorporate a one line string of SPICE parameters into the netlist, the following attributes must be attached to the component:
-</p>
-<table class="inline">
- <tr>
- <td><strong><code>refdes</code></strong></td><td>Correct component refdes.</td>
- </tr>
- <tr>
- <td><strong><code>value</code></strong></td><td>The model number or part number of the component.</td>
- </tr>
- <tr>
- <td><strong><code>model-name</code></strong></td><td>the name you wish to give the SPICE model. This is usually the model number or part number of the component. If you have already attached a â??valueâ?? attribute to the component, this parameter is optional.</td>
- </tr>
- <tr>
- <td><strong><code>model</code></strong></td><td>One line string holding additional parameters. Do not place the model parameters in parentheses – gnetlist will do this for you.</td>
- </tr>
-</table>
-
-</div>
-
-<h5><a name="spice_.model_or_.subckt_file" id="spice_.model_or_.subckt_file">SPICE .MODEL or .SUBCKT file</a></h5>
-<div class="level5">
-
-<p>
-To incorporate a file-full of SPICE parameters into the netlist, the following attributes must be attached to the component:
-</p>
-<table class="inline">
- <tr>
- <td><strong><code>refdes</code></strong></td><td>Correct component refdes. <strong>Note that if the file holds a .MODEL, the refdes should start with U; if the file holds a .SUBCKT, the refdes should start with X.</strong> The netlister checks for the file type and tries to â??do the right thingâ??, but problems can arise if you donâ??t follow this rule.</td>
- </tr>
- <tr>
- <td><strong><code>value</code></strong></td><td>The model number or part number of the component.</td>
- </tr>
- <tr>
- <td><strong><code>model-name</code></strong></td><td>The name you wish to give the SPICE model. This is usually the model number or part number of the component. If you have already attached a â??valueâ?? attribute to the component, this parameter is optional.</td>
- </tr>
- <tr>
- <td><strong><code>file</code></strong></td><td>The name of the file holding the SPICE .MODEL or .SUBCKT which you wish to incorporate into the netlist. This file name may specify either a relative or an absolute path, but it is probably better to use an absolute path to avoid problems if you ever move your schematic directory.</td>
- </tr>
-</table>
-
-</div>
-
-<h4><a name="independent_sources" id="independent_sources">Independent sources</a></h4>
-<div class="level4">
-
-<p>
-There are two independent sources: voltage sources and current sources. For incorporation into a SPICE netlist, they both work the same way. To incorporate an independent source into your SPICE netlist, do the following:
-</p>
-<ol>
-<li class="level1"><div class="li"> Place the independent source on your schematic. (Do â??Addâ?? → â??Componentâ?? → â??spiceâ?? → "<independent source name>.symâ??)</div>
-</li>
-<li class="level1"><div class="li"> Double click on the block and add/edit the following attributes:</div>
-<ul>
-<li class="level2"><div class="li"> <strong><code>refdes</code></strong>: V? or I?</div>
-</li>
-<li class="level2"><div class="li"> <strong><code>value</code></strong>: A one line string in SPICE format describing the source.</div>
-</li>
-</ul>
-</li>
-</ol>
-
-</div>
-
-<h4><a name="dependent_sources" id="dependent_sources">Dependent sources</a></h4>
-<div class="level4">
-
-<p>
-There are four dependent sources:
-</p>
-<ul>
-<li class="level1"><div class="li"> This section remains TBD.</div>
-</li>
-</ul>
-
-</div>
-
-<h4><a name="spice_components" id="spice_components">SPICE components</a></h4>
-<div class="level4">
-
-</div>
-
-<h5><a name="spice_model_block" id="spice_model_block">Spice model block</a></h5>
-<div class="level5">
-
-<p>
-In certain situations, you may wish to embed a spice model block directly into your schematic. This is done when you have several devices with a â??valueâ?? attribute calling out for a spice model. Depending upon whether the spice block is one line or multi-line, you may embed the code in one of two ways:
-</p>
-<ol>
-<li class="level1"><div class="li"> One line SPICE model:</div>
-<ol>
-<li class="level2"><div class="li"> Place a spice model block on your schematic. (Do â??Addâ?? → â??Componentâ?? → â??spiceâ?? → â??spice-model-1.symâ??)</div>
-</li>
-<li class="level2"><div class="li"> Double click on the block and add/edit the following attributes:</div>
-<ul>
-<li class="level3"><div class="li"> <strong><code>refdes</code></strong>: a?</div>
-</li>
-<li class="level3"><div class="li"> <strong><code>model</code></strong>: model name (i.e. the model name used in the components being modeled.)</div>
-</li>
-<li class="level3"><div class="li"> <strong><code>type</code></strong>: One of the valid spice component types defined in the spice <acronym title="specification">spec</acronym>.</div>
-</li>
-<li class="level3"><div class="li"> <strong><code>value</code></strong>: The corresponding one-line spice model</div>
-</li>
-</ul>
-</li>
-</ol>
-</li>
-<li class="level1"><div class="li"> Multi-line SPICE model:</div>
-<ol>
-<li class="level2"><div class="li"> Place a spice model block on your schematic.(Do â??Addâ?? → â??Componentâ?? → â??spiceâ?? → â??spice-model-1.symâ??)</div>
-</li>
-<li class="level2"><div class="li"> Double click on the block and add/edit the following attributes:</div>
-<ul>
-<li class="level3"><div class="li"> <strong><code>refdes</code></strong>: a?</div>
-</li>
-<li class="level3"><div class="li"> <strong><code>model-name</code></strong>: model name</div>
-</li>
-<li class="level3"><div class="li"> <strong><code>file</code></strong>: Name of file holding SPICE model code (i.e. .MODEL or .SUBCKT).</div>
-</li>
-</ul>
-</li>
-</ol>
-</li>
-</ol>
-
-</div>
-
-<h5><a name="include_block" id="include_block">Include block</a></h5>
-<div class="level5">
-
-<p>
-The include block places a .INCLUDE directive into your netlist.
-</p>
-<ol>
-<li class="level1"><div class="li"> Place a spice model block on your schematic. (Do â??Addâ?? → â??Componentâ?? → â??spiceâ?? → â??spice-include-1.symâ??)</div>
-</li>
-<li class="level1"><div class="li"> Double click on the block and add/edit the following attributes:</div>
-<ul>
-<li class="level2"><div class="li"> <strong><code>refdes</code></strong>: a?</div>
-</li>
-<li class="level2"><div class="li"> <strong><code>file</code></strong>: The name of the file to include.</div>
-</li>
-</ul>
-</li>
-</ol>
-
-</div>
-
-<h5><a name="spice_directive_block" id="spice_directive_block">SPICE directive block</a></h5>
-<div class="level5">
-
-<p>
-Placing a SPICE directive block into your schematic creates an arbitrary block of SPICE code in the netlist. The directive may be either statements held in a file, or a one-line string held in the â??modelâ?? attribute. Examples of situations where this is useful include:
-</p>
-<ul>
-<li class="level1"><div class="li"> .TEMP statement</div>
-</li>
-<li class="level1"><div class="li"> .IC statement</div>
-</li>
-<li class="level1"><div class="li"> Other SPICE statements for which gschem has no symbol.</div>
-</li>
-</ul>
-
-<p>
- To place a SPICE directive on your schematic, do the following:
-</p>
-<ol>
-<li class="level1"><div class="li"> Place a SPICE directive block on your schematic. (Do â??Addâ?? → â??Componentâ?? → â??spiceâ?? → â??spice-directive-1.symâ??)</div>
-</li>
-<li class="level1"><div class="li"> Double click on the block and add/edit the following attributes:</div>
-<ul>
-<li class="level2"><div class="li"> <strong><code>refdes</code></strong>: a?</div>
-</li>
-<li class="level2"><div class="li"> <strong><code>file</code></strong>: The name of the file to include.</div>
-</li>
-</ul>
-</li>
-</ol>
-
-</div>
-<!-- SECTION "Gschem attributes for spice netlisting" [7283-18697] -->
-<h3><a name="handling_hierarchical_models" id="handling_hierarchical_models">Handling hierarchical models</a></h3>
-<div class="level3">
-
-<p>
-In SPICE modeling, there are often situations where you wish to create a schematic representation of some particular component as a .SUBCKT, and then embed that componentâ??s model in a higher level schematic. A common example might be as follows: You are doing a microwave simulation, and want to use a capacitor model which includes parasitic inductances and resistances, as well as the capacitance. Capacitor manufacturers often supply a printed schematic showing a circuit topology incorporating parasitics, and specify values for the parasitics. You would like to draw the capacitor model using gschem, netlist it to create a .SUBCKT, and then use the .SUBCKT to model capacitors in a higher lever schematic.<br/>
- Since this kind of task is very common in SPICE simulation, gnet-spice-sdb now supports it (starting with rev 20030331). To create a lower level .SUBCKT and use it in a higher level schematic, do the following:
-</p>
-<ol>
-<li class="level1"><div class="li"> Draw the schematic of the lower level component (e.g. the capacitor + parasitics) using gschem.</div>
-</li>
-<li class="level1"><div class="li"> On the lower level schematic, place a spice-subcircuit-LL block (spice-subcircuit-LL-1.sym). This alerts the netlister that the schematic is a Lower Level .SUBCKT. Attach the following attributes to the symbol:<br/>
- <br/>
- <strong><code>model-name</code></strong> = cap_with_parasitics<br/>
- <br/>
- (Of course, â??cap_with_parasiticsâ?? is the example we use here. Use your own model name in your schematic.) Upon netlisting, this schematic symbol will cause the netlist to insert ".SUBCKT cap_with_parasitics " into the first line of the netlist file.</div>
-</li>
-<li class="level1"><div class="li"> On the lower level schematic, attach a spice-subcircuit-IO symbol (spice-subcircuit-IO-1.sym) to each IO net (i.e. connection to the upper level). Number the refdeses of the IO symbols in the same order as you would like the IO nets to be listed in the .SUBCKT line in the output file. (i.e. P1 = first, P2 = second, etc.)</div>
-</li>
-<li class="level1"><div class="li"> When you are done with the lower level schematic, netlist it in the usual way. For example, if your schematic is called cap_with_parasitics.sch, netlist it by saying:<br/>
- <br/>
- <strong><code>gnetlist -g spice-sdb -o cap_with_parasitics.cir cap_with_parasitics.sch</code></strong><br/>
- <br/>
- This will dump the SPICE netlist into the file called â??cap_with_parasitics.cirâ??. Visually inspect the .cir file to make sure that netlisting worked correctly.</div>
-</li>
-<li class="level1"><div class="li"> Next, create a symbol for the upper level schematic which will point to the .SUBCKT. Note that the symbol must have a refdes starting with the letter â??Xâ??. To ensure that this happens, do the following:</div>
-<ul>
-<li class="level2"><div class="li"> Use gschem to draw the symbol. I usually draw a box around a model symbol to distinguish it from a normal component. Make any other annotations desired.</div>
-</li>
-<li class="level2"><div class="li"> In the symbol, make sure that the pins are ordered identically to the order in which you have placed the pins in the .SUBCKT. This is done by editing the symbol with a text editor and setting the â??PINSEQâ?? attribute. The netlister will output the pins in the order determined by the â??PINSEQâ?? attribute.</div>
-</li>
-<li class="level2"><div class="li"> Using a text editor, give the symbol a â??DEVICEâ?? attribute like â??capacitor-modelâ??. Do not assign the symbol one of the native device types listed in the appendix! The goal is to create a symbol whose refdes starts with â??Xâ??, and if the â??DEVICEâ?? is a recognized type, this will not happen.</div>
-</li>
-<li class="level2"><div class="li"> Using a text editor, give the symbol the â??REFDESâ?? attribute â??X?"</div>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"> Create the upper level schematic. Place your newly created symbol on the schematic as many times as required & wire up the schematic in the usual way.</div>
-</li>
-<li class="level1"><div class="li"> To point your symbol to the lower level .SUBCKT, double click on the symbol and set the following attributes:<br/>
- <br/>
- <strong><code>file</code></strong> = cap_with_parasitics.cir<br/>
- <strong><code>model-name</code></strong> = cap_with_parasitics<br/>
- <br/>
- as well as any other attributes required (e.g. refdes).</div>
-</li>
-<li class="level1"><div class="li"> Now netlist your upper level schematic the usual way. The contents of each .SUBCKT file is dumped into the main netlist. Inspect your netlist visually using a text editor to ensure that it is correct. It is a good idea to pay particular attention to the following:</div>
-<ul>
-<li class="level2"><div class="li"> Verify that the ordering of the nets connecting the upper level netlist to the lower level .SUBCKT is correct.</div>
-</li>
-<li class="level2"><div class="li"> Make sure that the upper level model-name and the lower level model name (on the .SUBCKT declaration line) are the same.</div>
-</li>
-</ul>
-</li>
-</ol>
-
-<p>
- Once the netlist is created, you may simulate your design using any SPICE simulator desired.<br/>
-
-</p>
-
-<p>
-One final note: The netlister writes the contents of the lower level .SUBCKT file into the main netlist <strong>every time</strong> it encounters a component with â??FILEâ?? attribute pointing to that file. Therefore, if you use the same component with the same model more than once in a design you should instantiate the model file using a â??spice-modelâ?? symbol and point to it with each component. This is described in the â??multi-line SPICE model blockâ?? section above.
-</p>
-
-</div>
-<!-- SECTION "Handling hierarchical models" [18698-23545] -->
-<h2><a name="spice_netlist_generation" id="spice_netlist_generation">SPICE netlist generation</a></h2>
-<div class="level2">
-
-<p>
-Once the schematic is captured, a SPICE netlist can be generated running the gEDA utility â??gnetlistâ?? on the schematic files. Gnetlist is built to be customizable, and is able to generate a netlist of any desired format using a Scheme back-end, which does the real heavy-lifting of creating the netlist. The back-end Scheme file which implements SPICE netlisting is called gnet-spice-sdb.scm, and it lives in the ${PREFIX}/geda/share/gEDA/scheme directory.
-</p>
-
-</div>
-<!-- SECTION "SPICE netlist generation" [23546-24039] -->
-<h2><a name="creating_the_netlist" id="creating_the_netlist">Creating the netlist</a></h2>
-<div class="level2">
-
-<p>
-Creating a netlist from a schematic is easy. To generate a SPICE netlist, just do the following:
-</p>
-<ul>
-<li class="level1"><div class="li"> Save your schematic to <filename.sch></div>
-</li>
-<li class="level1"><div class="li"> Create the SPICE netlist by doing â??gnetlist â??g spice-sdb <filename.sch>". The output is a netlist held in the file output.net. Alternatively, if you wish to give your output file a different name, set the output name using the -o switch. For example:<br/>
- <br/>
- <strong><code>gnetlist -g spice-sdb -o amplifier.cir amplifier.sch</code></strong> <br/>
- <br/>
- takes the design schematic called â??amplifier.schâ?? and outputs a SPICE netlist named â??amplifier.cirâ??.</div>
-</li>
-<li class="level1"><div class="li"> Inspect your SPICE netlist using a text editor. Verify that there are no missing attributes or other netlist problems.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Creating the netlist" [24040-24765] -->
-<h2><a name="common_netlisting_problems" id="common_netlisting_problems">Common netlisting problems</a></h2>
-<div class="level2">
-
-<p>
-It is important to manually inspect your SPICE netlist prior to using it in simulation. Please remember that the netlister is still â??alphaâ?? quality, and some problems may still exist in netlist generation. The following list attempts to catalog common problems with the netlist and the associated fixes.
-</p>
-<ul>
-<li class="level1"><div class="li"> ERROR_INVALID_<acronym title="Personal Identification Number">PIN</acronym>: This can happen if the symbolâ??s PINSEQ attributes donâ??t start at 1, or have gaps in the numbering. This must be fixed by editing the symbol itself in a text editor.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Common netlisting problems" [24766-25301] -->
-<h2><a name="spice_simulation" id="spice_simulation">SPICE simulation</a></h2>
-<div class="level2">
-
-<p>
-There are several options for doing SPICE simulations under Linux; I will highlight two:
-</p>
-<ul>
-<li class="level1"><div class="li"> <strong>LTSpice</strong>, which is a freeware SPICE simulator originally released by Linear Technologies as a component selection/design tool running under Windows. Because its SPICE engine is very fast and powerful, it has become a popular SPICE simulator amongst hobbyists and design engineers who prefer to use free tools. LTSpice has been tweaked to run under Linux using wine; I recommend using it if you need a robust, <strong>professional-quality</strong> SPICE simulator.</div>
-<ul>
-<li class="level2"><div class="li"> <strong>Ngspice/tclspice</strong>, which is a component of the gEDA distribution. Ngspice provides a simulation engine, a command-line driven front-end, and the capability to plot simulation results graphically under X. The main branch of ngspice development has been arrested since late 2001. However, a fork of the development tree, called â??tclspiceâ??, remains under active development. Tclspice is the package I recommend if you want to use a <strong>Linux-native</strong> SPICE simulator. </div>
-</li>
-</ul>
-</li>
-</ul>
-
-<p>
- There is also a <acronym title="GNU General Public License">GPL</acronym>â??ed simulator called â??gnucapâ??, which is based upon (or is the descendent of) Alâ??s Circuit Simulator (ACS). I havenâ??t used it at all; information about gnucap is therefore TBD.
-</p>
-
-</div>
-<!-- SECTION "SPICE simulation" [25302-26547] -->
-<h3><a name="ltspice" id="ltspice">LTSpice</a></h3>
-<div class="level3">
-
-<p>
-LTSpice was written by Mike Englehardt at Linear Technologies, and was originally given away by LinearTech as a design aid for engineers wishing to simulate the performance of LinearTechâ??s switch mode power supply controllers. The package incorporates a schematic capture front end, fast and powerful SPICE engine, and the capability for plotting the results of many different types of SPICE analysis. Personally, I think the schematic capture front-end is hard to use and clunky; gschem knocks its socks off for ease of use and features. However, the SPICE engine and analysis stuff in LTSpice is simply great.<br/>
- LTSpice was originally developed to run under Windows, but Mike has tweaked it so that it runs fairly well on Linux under wine. (Only the help menu system is broken – the rest of the package runs well.) Another good feature of LTSpice is that it is well supported – Mike reads the newsgroup sci.electronics.cad regularly and is generally happy to help people who experience problems with it. Therefore, despite its Windoze heritage, I recommend LTSpice as a powerful, professional-quality simulation and analysis back end for gEDA.
-</p>
-
-</div>
-
-<h4><a name="installation_and_configuration_of_ltspice" id="installation_and_configuration_of_ltspice">Installation and configuration of LTSpice</a></h4>
-<div class="level4">
-
-<p>
-To install and configure LTSpice, do the following:
-</p>
-<ol>
-<li class="level1"><div class="li"> Download and install wine. I have had success using Wine-20030219.</div>
-</li>
-<li class="level1"><div class="li"> Download LTSpice. It is available under <a href="http://www.linear.com/software"; class="urlextern" title="http://www.linear.com/software"; rel="nofollow">http://www.linear.com/software</a> under the name SwitcherCAD-III.</div>
-</li>
-<li class="level1"><div class="li"> Run the LTSpice installer under wine.</div>
-</li>
-</ol>
-
-</div>
-
-<h4><a name="running_ltspice_with_geda_designs" id="running_ltspice_with_geda_designs">Running LTSpice with gEDA designs</a></h4>
-<div class="level4">
-
-<p>
-LTSpice can read a file holding a gEDA SPICE netlist. I have had success doing LTSpice sumulations in the following way:
-</p>
-<ol>
-<li class="level1"><div class="li"> First of all, make sure that you are logged in as a normal user – Wine doesnâ??t like to run when invoked by root.</div>
-</li>
-<li class="level1"><div class="li"> Create a file in your project directory called â??Simulation.cmdâ??. In this file place your spice analysis commands (e.g. .OP, .AC, .DC, etc.)</div>
-</li>
-<li class="level1"><div class="li"> Place a SPICE include block into your schematic. For the file attribute, type in â??Simulation.cmdâ??.</div>
-</li>
-<li class="level1"><div class="li"> Netlist your design.</div>
-</li>
-<li class="level1"><div class="li"> Create a link from your netlist â??output.netâ?? and a netlist in the directory in which SwCADIII lives. Make the netlist suffix .cir. For example: ln -s ${DESIGN_HOME}/output.net ${WINE_HOME}/.wine/fake_windows/Program Files/LTC/SwCADIII/MyDesign.cir</div>
-</li>
-<li class="level1"><div class="li"> Run LTSpice: cd into the directory where SwCADIII lives and say â??wine scad3.exeâ??</div>
-</li>
-<li class="level1"><div class="li"> From the SwCADIII <acronym title="Graphical User Interface">GUI</acronym>, do: File → Open → (files of type netlist [.cir]), and select your file.</div>
-</li>
-<li class="level1"><div class="li"> Run the simulator by clicking on the run button, or doing: Simulate → Run.</div>
-</li>
-<li class="level1"><div class="li"> Select the variables to graph, and then click OK. SwCADIII does the rest of the work.</div>
-</li>
-</ol>
-
-<p>
- Naturally, it is very important to play around with LTSpice to understand how to use it effectively, but the above description should suffice to get you started.
-</p>
-
-</div>
-<!-- SECTION "LTSpice" [26548-29363] -->
-<h3><a name="ngspice_and_tclspice" id="ngspice_and_tclspice">Ngspice and tclspice</a></h3>
-<div class="level3">
-
-<p>
-Ngspice was started at the University of Rome by Paolo Nenzi as an attempt to create a <acronym title="GNU General Public License">GPL</acronym>â??ed version of the standard Berkeley SPICE version 3 by re-writing the entire SPICE package. Plans were also laid to create better, more robust computational algorithms for the simulation engine. More information is available at the <a href="http://ngspice.sourceforge.net/"; class="urlextern" title="http://ngspice.sourceforge.net/"; rel="nofollow">ngspice website</a>. Unfortunately, development on ngspice seems to have ceased at the end of 2001. Moreover, my initial experiences with ngspice were not good – it crashed and burned when run on many of my netlists, and it couldnâ??t deal with SPICE 2â??s POLY construct in dependent sources. Dependent sources with PLOY attributes are common in vendor models, so this represents a real deficiency.
-</p>
-
-<p>
-Fortunately, some friendly people at <a href="http://www.multigig.com/"; class="urlextern" title="http://www.multigig.com"; rel="nofollow">MultiGig Ltd.</a> were busy developing a branch of ngspice which they called â??tclspiceâ??. The purpose of tclspice is to enable SPICE commands to be embedded into TCL scripts, thereby enabling automated circuit optimization. The project homepage is at <a href="http://tclspice.sourceforge.net/"; class="urlextern" title="http://tclspice.sourceforge.net/"; rel="nofollow">http://tclspice.sourceforge.net/</a>. Since the tclspice branch of the code was alive, I decided to work on it, instead of the seemingly dead main ngspice branch. During spring 2003, I fixed tclspice in three useful (IMNSHO) ways:
-</p>
-<ol>
-<li class="level1"><div class="li"> I fixed the parser so that it would handle netnames with non-numeric/non-alphabetic characters like "+" or "-" which are common in real netlists (e.g. â??Vin+", or â??Vout1_pull-upâ??).</div>
-</li>
-<li class="level1"><div class="li"> I fixed the parser so that it would correctly handle hierarchical schematics, and correctly deal with the netnames inside the blocks.</div>
-</li>
-<li class="level1"><div class="li"> I got the POLY translation code (which exists in XSPICE) working so that one can now run SPICE 2 netlists with tclspice.</div>
-</li>
-</ol>
-
-<p>
- Tclspice seems to work nicely now (although there are still some issues with memory leaks). Moreover, because the tclspice code is a superset of ngspice, <strong>if you build tclspice, you will also build the command-line driven ngspice program</strong>. Therefore, I recommend getting and installing tclspice if you want to do Linux-native SPICE simulations.
-</p>
-
-</div>
-
-<h4><a name="installation_and_configuration_of_ngspice_and_tclspice" id="installation_and_configuration_of_ngspice_and_tclspice">Installation and configuration of ngspice and tclspice</a></h4>
-<div class="level4">
-
-<p>
-To install ngspice and tclspice, do the following:
-</p>
-<ol>
-<li class="level1"><div class="li"> Get the latest tclspice distribution from <a href="http://tclspice.sourceforge.net/"; class="urlextern" title="http://tclspice.sourceforge.net/"; rel="nofollow">http://tclspice.sourceforge.net/</a>. As of this writing, the latest version is tclspice-0.2.12. This version incorporates the fixes I mentioned above, as well as other improvements made by the hard-working people at MultiGig, so make sure that your version is equal or greater than 0.2.12.</div>
-</li>
-<li class="level1"><div class="li"> Do the usual â??gunzip ; tar -xvfâ?? dance to create a source directory for tclspice.</div>
-</li>
-<li class="level1"><div class="li"> First build ngspice. Do "./configure –enable-xspice –prefix=/usr/local/gedaâ?? in the source directory. Of course, "–prefix=" should point to the place where you put your geda stuff. Note that you also must do "–enable-xspiceâ?? to be able to use SPICE 2 POLYs (and other XSpice goodies).</div>
-</li>
-<li class="level1"><div class="li"> Do â??make && make installâ?? to compile and install ngspice. As always, you will probably need to be root in order to install the packages in a public directory.</div>
-</li>
-<li class="level1"><div class="li"> At this point, you should be able to use ngspice. You can test your installation by trying one of the test circuits held in the tests directory. I recommend running the TransImpedanceAmp test, since it tests the SPICE2 POLY functionality. Information how to use ngspice is provided in the next section below.</div>
-</li>
-<li class="level1"><div class="li"> If you only want to use ngspice, you can stop now. Otherwise, next build tclspice. To build tclspice, you need to have the following other packages already installed:<br/>
- <br/>
- * TclX (tclx8.3.5 works for me.)<br/>
- * tclreadline (tclreadline-2.1.0 works for me.)<br/>
- * BLT for TCL (blt2.4z works for me.)<br/>
- <br/>
- If you donâ??t have these packages already on your Linux box, you need to get them and build them. Note that building TclX requires having the sources for TCL and Tk, so you will also need to get those sources if you donâ??t have them installed already. I am running successfully with TCL/Tk 8.4.3, although 8.3.X versions are also supposed to work.</div>
-</li>
-<li class="level1"><div class="li"> Assuming you have gotten the additional packages mentioned above installed, Do "./configure –enable-xspice –prefix=/usr/local/geda –enable-tcl –enable-experimental –disable-sharedâ?? to configure the Makefiles for tclspice. (If you donâ??t have the additional packages installed correctly , configure will complain and barf, so this step acts as a check on your installation.)</div>
-</li>
-<li class="level1"><div class="li"> Do â??make tcl && make install-tclâ?? to compile and install tclspice.</div>
-</li>
-<li class="level1"><div class="li"> Now you will be ready to write TCL scripts which incorporate SPICE commands. Information about using tclspice is given below.</div>
-</li>
-</ol>
-
-<p>
- Finally, if you are interested in hacking tclspice (or even if you are not), itâ??s a good idea to read the NOTES file living in the top source directory for a couple of useful pointers.
-</p>
-
-</div>
-
-<h4><a name="use_of_ngspice" id="use_of_ngspice">Use of ngspice</a></h4>
-<div class="level4">
-
-<p>
-Running ngspice is very simple. Just issue the command â??ngspice filename.netâ?? at the unix command prompt, and ngspice will load the SPICE netlist called â??filename.netâ?? into its workspace, and leave you at an ngspice command prompt. You can run the simulator by saying â??runâ??. Your results will be stored in SPICE vectors for later printing or plotting. The command set available to you is documented at <a href="http://newton.ex.ac.uk/teaching/CDHW/Electronics2/userguide/sec5.html#5"; class="urlextern" title="http://newton.ex.ac.uk/teaching/CDHW/Electronics2/userguide/sec5.html#5"; rel="nofollow">http://newton.ex.ac.uk/teaching/CDHW/Electronics2/userguide/sec5.html#5</a>.<br/>
- To make use of the SPICE2 POLY codemodel, you need to load it into ngspice <strong>before</strong> you load your netlist. (If you load it after loading your netlist, POLYs in your netlist are not translated, and therefore wonâ??t be simulated correctly.) To load the codemodel, just say â??codemodel /usr/local/src/tclspice-0.2.12/src/xspice/icm/spice2poly.cmâ?? at the ngspice prompt. Note that you must provide the <strong>absolute path</strong> to the location of the codemodel; ngspice isnâ??t smart enough to look for it in any default locations. (Also note that you should specify the location where spice2poly.cm lives on your machine; the path above is for mine.)<br/>
- A better way to read in the spice2poly codemodel is to include it in the ngspice initialization file, â??spinitâ??. The initialization file lives in the directory /usr/local/geda/share/ng-spice-rework/scripts (or where ever you placed your geda installation). Other ngspice customizations may also be placed into the spinit file.
-</p>
-
-</div>
-
-<h4><a name="use_of_tclspice" id="use_of_tclspice">Use of tclspice</a></h4>
-<div class="level4">
-
-<p>
-The tclspice package is a superset of ngspice. Not only does the package include the ngspice interactive environment; tclspice also provides a facility which exports the ngspice command set as TCL commands for inclusion into a TCL script. This is a very powerful tool: With tclspice you can write a TCL script which runs a loop, tweaks component values, runs an analysis, and then evaluates the circuit performance with the tweaked components before looping again. Obviously, this ability can be used to perform automated, multi-dimensional circuit optimization.<br/>
- To use tclspice, you just need to say â??package require spiceâ?? at the beginning of your TCL program. Thereafter, to invoke a SPICE command, you just call it in the spice namesapce. For example, the following TCL program will read in a SPICE netlist, command a transient analysis, run the simulation, and then plot the voltage observed over time on net Vout:
-</p>
-<pre class="code">#! tclsh
-package require spice
-spice::codemodel /usr/local/src/tclspice-0.2.12/src/xspice/icm/spice2poly.cm
-
-spice::source netlistname.cir
-spice::tran 0.1ns 40ns
-spice::run
-spice::plot Vout
-puts "All done now!"</pre>
-
-<p>
-Note that since tclspice doesnâ??t read the ngspice initialization file â??spinitâ??, you will need to put any initialization commands directly into the TCL program. For example, in the above example we read the spice2poly codemodel directly into the workspace. Many other commands are also available; the entire tclspice commandset is documented at <a href="http://tclspice.sourceforge.net/docs/tclspice_com.html"; class="urlextern" title="http://tclspice.sourceforge.net/docs/tclspice_com.html"; rel="nofollow">http://tclspice.sourceforge.net/docs/tclspice_com.html</a>.<br/>
- A major problem with tclspice (which was inherited from ngspice) is that it leaks memory. Therefore, the time over which you may run a simulation is limited. This means that if you want to do an optimization by looping through a circuit many, many times, you may run out of memory before your program has completed its optimization. This is a known issue with tclspice, and efforts are underway to plug the leaks.<br/>
- Meanwhile, there are some workarounds which can be used on moderate-sized designs to facilitate long optimization runs. One method I have employed is to have the optimizer write its current state into a file after every circuit analysis, and read its starting state from the same file. The optimizer also stores the current list of best components in another file, and reads this file at the start of every run. Then, I have a TCL program called TaskMgr.tcl which runs in a loop; at each iteration of the loop it forks a child process to run the optimizer. Meanwhile, the parent process waits for 5 minutes (a heuristically determined time), and then issues a â??KILLâ?? signal to the child before looping and starting the optimizer again. This way, the optimizer never runs long enough to consume all the memory in my machine. The TaskMgr.tcl program is shown here:
-</p>
-<pre class="code">#! tclsh
-package require Tclx
-while {1} {
-
- set PID [fork]
- if {$PID} {
-
- # Parent
- after 300000
- puts "About to kill child PID = $PID . . . ."
- kill $PID
- wait $PID
-
- } else {
-
- # Child
- source Optimize.tcl
- # If we ever get through this, we can print out the following:
- error "We are done now!!!!!!"
-
- }
-
-}</pre>
-
-<p>
-Note that TaskMgr.tcl needs the TclX package you already installed to run tclspice. Also, you may want to change the wait time to a different value depending upon the memory and speed of your machine. Finally, the parent has to wait on $PID because that causes the child processâ??s corpse to be taken off the Linux kernalâ??s task list when it dies. Otherwise, you will end up with a lot of zombie processes lurking around your machine as the optimizer runs – a long optimization could turn your system into â??the night of the living deadâ??!<br/>
- This method of waiting a specific amout of time for the child process is preferable if a single analysis run takes a relativly short time compared to the time required to eat all memory in the machine. If the analysis time is comparable to the time taken to eat all memory in the machine, a better approach is to have the parent keep track of the analysis state, kick off a single analysis run, and then have the run terminate after every iteration. Whether this is preferable depends upon the size and complexity of your design; you may want to experiment with your analysis to see just how long it takes and how much memory it consumes. I have found that a design comprised of six op amps (with corresponding vendor models) and 50 or so passives will run in under 10 seconds on a PIII 333MHz with 128MB RAM. Therefore, your design must be very big before a single analysis will eat a significant amount of RAM.
-</p>
-
-</div>
-<!-- SECTION "Ngspice and tclspice" [29364-40393] -->
-<h2><a name="appendix" id="appendix">Appendix</a></h2>
-<div class="level2">
-
-</div>
-<!-- SECTION "Appendix" [40394-40415] -->
-<h3><a name="component_attribute_summary" id="component_attribute_summary">Component attribute summary</a></h3>
-<div class="level3">
-
-<p>
-Native components and their attributes are given in the table below. <strong>Bold faced</strong> attributes are <strong>required</strong>, normal typeface attributes are optional. Note that the â??deviceâ?? attribute is invisible, and is normally attached to the symbol when it is created. The other attributes are attached to the symbol during schematic capture using gschem.
-</p>
-<table class="inline">
- <tr>
- <th><strong><code>device</code></strong></th><th><strong><code>refdes</code></strong></th><th><strong><code>value</code></strong></th><th><strong><code>model</code></strong></th><th><strong><code>file</code></strong></th><th><strong><code>model-name</code></strong></th><th><strong><code>type</code></strong></th><th>Comment</th>
- </tr>
- <tr>
- <td><strong>RESISTOR</strong></td><td><strong>R?</strong></td><td><strong>Numeric comp. value</strong></td><td>One line of spice model parameters (e.g. TC)</td><td> </td><td>Name of model.</td><td> </td><td>â??modelâ?? parameters are placed inside parentheses after the component value.</td>
- </tr>
- <tr>
- <td><strong>CAPACITOR</strong></td><td><strong>C?</strong></td><td><strong>Numeric comp. value</strong></td><td>One line of spice model parameters (e.g. IC, POLY, etc.)</td><td> </td><td>Name of model.</td><td> </td><td>â??modelâ?? parameters are placed inside parentheses after the component value.</td>
- </tr>
- <tr>
- <td><strong>POLARIZED_CAPACITOR</strong></td><td><strong>C?</strong></td><td><strong>Numeric comp. value</strong></td><td>One line of spice model parameters (e.g. IC, POLY, etc.)</td><td> </td><td>Name of model.</td><td> </td><td>â??modelâ?? parameters are placed inside parentheses after the component value.</td>
- </tr>
- <tr>
- <td><strong>INDUCTOR</strong></td><td><strong>L?</strong></td><td><strong>Numeric comp. value</strong></td><td>One line of spice model parameters (e.g. IC, POLY, etc.)</td><td> </td><td>Name of model.</td><td> </td><td>â??modelâ?? parameters are placed inside parentheses after the component value.</td>
- </tr>
- <tr>
- <td><strong>SPICE-ccvs</strong></td><td><strong>H?</strong></td><td><strong>String describing source behavior</strong></td><td> </td><td> </td><td> </td><td> </td><td> </td>
- </tr>
- <tr>
- <td><strong>SPICE-cccs</strong></td><td><strong>F?</strong></td><td><strong>String describing source behavior</strong></td><td> </td><td> </td><td> </td><td> </td><td> </td>
- </tr>
- <tr>
- <td><strong>SPICE-vcvs</strong></td><td><strong>E?</strong></td><td><strong>String describing source behavior</strong></td><td> </td><td> </td><td> </td><td> </td><td> </td>
- </tr>
- <tr>
- <td><strong>SPICE-vccs</strong></td><td><strong>G?</strong></td><td><strong>String describing source behavior</strong></td><td> </td><td> </td><td> </td><td> </td><td> </td>
- </tr>
- <tr>
- <td><strong>SPICE-nullor</strong></td><td><strong>E?</strong></td><td><strong>String describing source behavior</strong></td><td> </td><td> </td><td> </td><td> </td><td> </td>
- </tr>
- <tr>
- <td><strong>DIODE</strong></td><td><strong>D?</strong></td><td>Part number</td><td>One line SPICE model.</td><td>Model file name.</td><td><strong>Name of model.</strong></td><td> </td><td>For modeling, one must include either â??modelâ?? or â??fileâ??.</td>
- </tr>
- <tr>
- <td><strong>PMOS_TRANSISTOR</strong></td><td><strong>M?</strong></td><td>Part number</td><td>One line SPICE model.</td><td>Model file name.</td><td><strong>Name of model.</strong></td><td> </td><td>For modeling, one must include either â??modelâ?? or â??fileâ??.</td>
- </tr>
- <tr>
- <td><strong>NMOS_TRANSISTOR</strong></td><td><strong>M?</strong></td><td>Part number</td><td>One line SPICE model.</td><td>Model file name.</td><td><strong>Name of model.</strong></td><td> </td><td>For modeling, one must include either â??modelâ?? or â??fileâ??.</td>
- </tr>
- <tr>
- <td><strong>PNP_TRANSISTOR</strong></td><td><strong>Q?</strong></td><td>Part number</td><td>One line SPICE model.</td><td>Model file name.</td><td><strong>Name of model.</strong></td><td> </td><td>For modeling, one must include either â??modelâ?? or â??fileâ??.</td>
- </tr>
- <tr>
- <td><strong>NPN_TRANSISTOR</strong></td><td><strong>Q?</strong></td><td>Part number</td><td>One line SPICE model.</td><td>Model file name.</td><td><strong>Name of model.</strong></td><td> </td><td>For modeling, one must include either â??modelâ?? or â??fileâ??.</td>
- </tr>
- <tr>
- <td><strong>PFET_TRANSISTOR (JFET)</strong></td><td><strong>J?</strong></td><td>Part number</td><td>One line SPICE model.</td><td>Model file name.</td><td><strong>Name of model.</strong></td><td> </td><td>For modeling, one must include either â??modelâ?? or â??fileâ??.</td>
- </tr>
- <tr>
- <td><strong>NFET_TRANSISTOR (JFET)</strong></td><td><strong>J?</strong></td><td>Part number</td><td>One line SPICE model.</td><td>Model file name.</td><td><strong>Name of model.</strong></td><td> </td><td>For modeling, one must include either â??modelâ?? or â??fileâ??.</td>
- </tr>
- <tr>
- <td><strong>MESFET_TRANSISTOR</strong></td><td><strong>B?</strong></td><td>Part number</td><td>One line SPICE model.</td><td>Model file name.</td><td><strong>Name of model.</strong></td><td> </td><td>For modeling, one must include either â??modelâ?? or â??fileâ??.</td>
- </tr>
- <tr>
- <td><strong>IC</strong></td><td><strong>U?</strong></td><td>Part number</td><td>One line SPICE model.</td><td>Model file name.</td><td><strong>Name of model.</strong></td><td> </td><td>IC with .MODEL file</td>
- </tr>
- <tr>
- <td><strong>IC</strong></td><td><strong>X?</strong></td><td>Part number</td><td> </td><td>Model file name.</td><td><strong>Name of model.</strong></td><td> </td><td>IC with .SUBCKT file</td>
- </tr>
- <tr>
- <td><strong>model</strong></td><td colspan="2"><strong>A?</strong></td><td>One line spice model</td><td>Model file name.</td><td><strong>Name of model pointed to by other components.</strong></td><td><strong>Corresponding SPICE model type (valid types given below)</strong>.</td><td>For modeling, one must include either â??modelâ?? or â??fileâ??.</td>
- </tr>
- <tr>
- <td><strong>include</strong></td><td><strong>A?</strong></td><td> </td><td> </td><td><strong>Include file name.</strong></td><td> </td><td> </td><td>Places .INCLUDE directive in SPICE netlist.</td>
- </tr>
- <tr>
- <td><strong>options</strong></td><td><strong>A?</strong></td><td><strong>Line of options to include.</strong></td><td> </td><td> </td><td> </td><td> </td><td>Places .OPTIONS directive in SPICE netlist.</td>
- </tr>
- <tr>
- <td><strong>directive</strong></td><td><strong>A?</strong></td><td><strong>One line string holding SPICE statements for inclusion in netlist.</strong></td><td> </td><td> </td><td> </td><td> </td><td>For modeling, one must include either â??modelâ?? or â??fileâ??.</td>
- </tr>
- <tr>
- <td><strong>VOLTAGE_SOURCE</strong></td><td><strong>V?</strong></td><td><strong>One line string holding voltage source behavior.</strong></td><td> </td><td> </td><td> </td><td> </td><td>Independent voltage source</td>
- </tr>
- <tr>
- <td><strong>CURRENT_SOURCE</strong></td><td><strong>I?</strong></td><td><strong>One line string holding current source behavior.</strong></td><td> </td><td> </td><td> </td><td> </td><td>Independent current source</td>
- </tr>
-</table>
-
-<p>
- â??Native to the netlisterâ?? means that there is a corresponding blob of scheme code which knows exactly how to handle these components and is guaranteed (almost) to generate correct spice code. Symbols having â??deviceâ?? attributes not on the above list are handled using the scheme function â??spice-sdb:write-default-componentâ??, which looks at the refdes of the component to make a decision about how to treat the component. In general, this function will â??do the right thingâ?? when generating spice code, but it is not guaranteed. In particular, this function cannot distinguish between N and P type transistors, and will generate an <unknown> type for the .MODEL string in the netlist. This will probably cause your SPICE simulator to barf. Therefore, it is best to make sure that all devices used have the proper â??deviceâ?? attribute.
-</p>
-
-</div>
-<!-- SECTION "Component attribute summary" [40416-45184] -->
-<h3><a name="valid_type_values" id="valid_type_values">Valid "type" values</a></h3>
-<div class="level3">
-
-<p>
-The â??typeâ?? attribute is a flag signaling the spice engine the component type, and prepares it to accept model parameters specific to that component type. The following values are valid SPICE â??typeâ??s:
-</p>
-<table class="inline">
- <tr>
- <th>Component</th><th>â??typeâ??</th><th>Comment</th>
- </tr>
- <tr>
- <td>RESISTOR</td><td>RES</td><td> </td>
- </tr>
- <tr>
- <td>CAPACITOR</td><td>CAP</td><td> </td>
- </tr>
- <tr>
- <td>POLARIZED_CAPACITOR</td><td>CAP</td><td> </td>
- </tr>
- <tr>
- <td>INDUCTOR</td><td>IND</td><td> </td>
- </tr>
- <tr>
- <td>DIODE</td><td>D</td><td> </td>
- </tr>
- <tr>
- <td>PMOS_TRANSISTOR</td><td>PMOS</td><td> </td>
- </tr>
- <tr>
- <td>NMOS_TRANSISTOR</td><td>NMOS</td><td> </td>
- </tr>
- <tr>
- <td>PNP_TRANSISTOR</td><td>PNP</td><td> </td>
- </tr>
- <tr>
- <td>NPN_TRANSISTOR</td><td>NPN</td><td> </td>
- </tr>
- <tr>
- <td>PFET_TRANSISTOR</td><td>PJF</td><td> </td>
- </tr>
- <tr>
- <td>NFET_TRANSISTOR</td><td>NJF</td><td> </td>
- </tr>
- <tr>
- <td>MESFET_TRANSISTOR</td><td> </td><td> </td>
- </tr>
-</table>
-
-</div>
-<!-- SECTION "Valid type values" [45185-45703] -->
-<h2><a name="document_history" id="document_history">Document History</a></h2>
-<div class="level2">
-<table class="inline">
- <tr>
- <td>Revision 1.0</td><td>3.10.2003</td><td>SDB</td><td>Document creation.</td>
- </tr>
- <tr>
- <td>Revision 1.1</td><td>3.19.2003</td><td>SDB</td><td>Added .SUBCKT stuff & stuff about LTSpice</td>
- </tr>
- <tr>
- <td>Revision 1.2</td><td>3.31.2003</td><td>SDB</td><td>Added stuff about creating hierarchical projects (i.e. creating .SUBCKTs using gschem and incorporating a lower level .SUBCKT into a higher level schematic).</td>
- </tr>
- <tr>
- <td>Revision 2.0</td><td>7.23.2003</td><td>SDB</td><td>Split doc into sections. Edited netlisting stuff to correspond to gEDA-20030525, which now includes spice-sdb in the distribution. Added new section about ngspice/tclspice.</td>
- </tr>
-</table>
-
-<p>
- The most recent copy of this document is always available at <a href="http://www.brorson.com/gEDA/SPICE/"; class="urlextern" title="http://www.brorson.com/gEDA/SPICE/"; rel="nofollow">http://www.brorson.com/gEDA/SPICE/</a>
-</p>
-
-</div>
-<!-- SECTION "Document History" [45704-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/geda_sn_readme.html b/docs/wiki/geda_sn_readme.html
deleted file mode 100644
index 70f3fef..0000000
--- a/docs/wiki/geda_sn_readme.html
+++ /dev/null
@@ -1,171 +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>geda:sn_readme</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="geda,sn_readme" />
-<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/geda:sn_readme?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:sn_readme"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:sn_readme"; />
-<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">
-
-
-
-<h1><a name="switcap_netlister_readme" id="switcap_netlister_readme">Switcap netlister README</a></h1>
-<div class="level1">
-<pre class="code">-----------------------------------------------------------------
-I. What is this?
------------------------------------------------------------------
-
-This archive contains a set of symbols and a netlister backend for the
-gEDA to drive SWITCAP simulations. gEDA is the GNU EDA project and
-includes a schematic capture tool and a highly flexible netlister.
-The SWITCAP program is a switched capacitor circuit simulator.
-
------------------------------------------------------------------
-II. Overview
------------------------------------------------------------------
-
-The basic steps involved with using gEDA as the frontend for SWITCAP
-simulations are:
-
-- configure the gEDA symbol search path
-- set the gEDA netlister backend search path
-- create schematics of the circuit
-- create an analysis file
-- extract the netlist
-- run the SWITCAP simulation
-
-
------------------------------------------------------------------
-III. Initial Setup
------------------------------------------------------------------
- 1) Set your symbol search path for gschem and gnetlist by adding
- the following line to the 'gschemrc' and 'gnetlistrc' files in
- your project directory.
-
- (component-library "/path/to/sym/switcap")
-
- If those files do not exist, then create them. You will need to
- replace /path/to/sym/switcap with the directory name where you
- have installed the .sym files.
-
- 2) Set the search path for scheme files for gnetlist by adding the
- following line to your 'gnetlistrc' file.
-
- (scheme-directory "/path/to/scheme")
-
- You will need to replace /path/to/scheme with the path to where
- you have installed the gnet-switcap.scm file.
-
- 3)
-
------------------------------------------------------------------
-IV. Creating Schematics
------------------------------------------------------------------
-
---------------------
-A. Required Symbols
---------------------
-
-This section assumes you are familiar with using gschem to create and
-edit schematics. SWITCAP netlisting is only supported for the
-components contained in the SWITCAP symbol library as well as the
-ground symbol found in the 'power' library which comes with gEDA. All
-allowed SWITCAP elements except for subcircuits are supported. You
-_must_ include the following elements on your schematic:
-
-- one instance of the switcap-timing symbol. This symbol will set the
- master clock period for your simulations.
-
-- one or more instances of the switcap-clock symbol. This symbol
- defines a clock with a particular phase and period. The reference
- designator of the clock symbol is used by the switches to set what
- phase they switch on.
-
-- one or more instances of the switcap-analysis symbol. This symbol
- defines an analysis by specifying a file to include in the SWITCAP
- netlist.
-
---------------------
-B. Optional Symbols
---------------------
-
-You can also optionally add the following SWITCAP special symbols to
-your schematic:
-
-- zero or one instance of the switcap-title symbol. This will add a
- TITLE: line to the SWITCAP netlist and will appear in the output
- file.
-
-- zero or one instance of the switcap-options symbol. By editing the
- OPTIONS attribute on this symbol you can set the various options
- which can be passed to SWITCAP.
-
---------------------
-C. Net Names
---------------------
-
-When creating schematics to drive SWITCAP, you should name all nets
-that you wish to plot. To avoid possible conflicts with unnamed nets,
-you should avoid using purely numerical names for nets because
-all unnamed nets will be assigned (somewhat randomly) numbers.
-SWITCAP limits the length of node names to 7 characters.
-
---------------------
-D. Switches
---------------------
-
-When placing switches on your schematic, you will need to define
-which clock they are controlled with. This is done by setting
-the clock attribute on the switch to the reference designator
-of the clock which should control it.
-
------------------------------------------------------------------
-V. Extracting the SWITCAP Netlist
------------------------------------------------------------------
-
-To extract the SWITCAP netlist, run
-
- gnetlist -g switcap -o test.scn file1.sch [file2.sch ...]
-
-For the example file contained in this archive, you can run:
-
- gnetlist -g switcap -o example.scn ckt.sch clocks.sch analysis.sch
-
-The netlist will be left in example.scn.
-
------------------------------------------------------------------
-VI. Running SWITCAP
------------------------------------------------------------------
-
-I typically use something like:
-
- printf "example.scn\nexample.out" | sw
-
-so I can use command history to rerun SWITCAP without having to
-manually type the file names each time.
-
-Refer to the SWITCAP manual for more details.
-
-
-</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_ssan.html b/docs/wiki/geda_ssan.html
deleted file mode 100644
index 9ebdf53..0000000
--- a/docs/wiki/geda_ssan.html
+++ /dev/null
@@ -1,470 +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>geda:ssan</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="keywords" content="geda,ssan" />
-<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/geda:ssan?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:ssan"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:ssan"; />
-<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="#geda_gaf_switcap_symbols_and_netlister" class="toc">gEDA/gaf Switcap Symbols and Netlister</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#overview" class="toc">Overview</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#requirements" class="toc">Requirements</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#creating_schematics" class="toc">Creating Schematics</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#required_symbols" class="toc">Required Symbols</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#optional_symbols" class="toc">Optional Symbols</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#net_names" class="toc">Net Names</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#switches" class="toc">Switches</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#extracting_the_switcap_netlist" class="toc">Extracting the SWITCAP Netlist</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#running_switcap" class="toc">Running SWITCAP</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#appendix_a_--_symbols_in_the_library" class="toc">Appendix A -- Symbols in the Library</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#capacitors_switcap-capacitor" class="toc">Capacitors (switcap-capacitor)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#switches_switcap-switch" class="toc">Switches (switcap-switch)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#independent_voltage_sources_switcap-vsrc" class="toc">Independent Voltage Sources (switcap-vsrc)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#dependent_voltage_sources_switcap-vcvs" class="toc">Dependent Voltage Sources (switcap-vcvs)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#clock_specification_switcap-clock" class="toc">Clock Specification (switcap-clock)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#master_timing_specification_switcap-timing" class="toc">Master Timing Specification (switcap-timing)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#analysis_file_include_switcap-analysis" class="toc">Analysis File Include (switcap-analysis)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#simulation_title_specification_switcap-title" class="toc">Simulation Title Specification (switcap-title)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#simulation_options_specification_switcap-options" class="toc">Simulation Options Specification (switcap-options)</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#example" class="toc">Example</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#example_schematics" class="toc">Example Schematics</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#netlist_the_design" class="toc">Netlist the Design</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#run_the_simulation" class="toc">Run the Simulation</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#process_the_results" class="toc">Process the Results</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#plot_the_results" class="toc">Plot the Results</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#document_revision_history" class="toc">Document Revision History</a></span></div></li></ul>
-</li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="geda_gaf_switcap_symbols_and_netlister" id="geda_gaf_switcap_symbols_and_netlister">gEDA/gaf Switcap Symbols and Netlister</a></h1>
-<div class="level1">
-
-<p>
-by: Dan McMahill
-</p>
-
-<p>
-This document is released under <a href="http://www.gnu.org/copyleft/fdl.html"; class="urlextern" title="http://www.gnu.org/copyleft/fdl.html"; rel="nofollow">GFDL</a>
-</p>
-
-<p>
-April 13th, 2003
-</p>
-
-</div>
-<!-- SECTION "gEDA/gaf Switcap Symbols and Netlister" [1-168] -->
-<h2><a name="overview" id="overview">Overview</a></h2>
-<div class="level2">
-
-<p>
-This document describes the symbol library and gnetlist backend which supports driving SWITCAP simulations from the gEDA/gaf system. SWITCAP is a switched capacitor circuit simulator available from Columbia University. It is used in many classroom and research environments. One drawback to SWITCAP is the lack of a freely available schematic capture frontend. The gEDA/gaf SWITCAP symbol library and gnetlist backend tries to fill that gap.<br/>
- The basic steps involved with using gEDA as the frontend for SWITCAP simulations are:
-</p>
-<ol>
-<li class="level1"><div class="li"> Create schematics of the circuit.</div>
-</li>
-<li class="level1"><div class="li"> Create an analysis file.</div>
-</li>
-<li class="level1"><div class="li"> Extract the netlist.</div>
-</li>
-<li class="level1"><div class="li"> Run the SWITCAP simulation.</div>
-</li>
-<li class="level1"><div class="li"> Run <strong>sw2asc</strong> to extract the results.</div>
-</li>
-<li class="level1"><div class="li"> View the results with <strong>gwave</strong>.</div>
-</li>
-</ol>
-
-</div>
-<!-- SECTION "Overview" [169-924] -->
-<h2><a name="requirements" id="requirements">Requirements</a></h2>
-<div class="level2">
-
-<p>
-You will need the following programs to be installed:
-</p>
-<ol>
-<li class="level1"><div class="li"> A recent version of gEDA/gaf. To see if your version is recent enough, see if the directory <strong><code>$prefix/share/gEDA/sym/switcap</code></strong> exists. <strong><code>$prefix</code></strong> is the installation prefix for gEDA on your system.</div>
-</li>
-<li class="level1"><div class="li"> SWITCAP. The executable is usually called <strong><code>sw</code></strong>. If you do not have SWITCAP available on your system, you will need to contact Columbia University to obtain a copy. The gEDA/gaf SWITCAP support was tested with SWITCAP Version A.5R Release 21-Sep-87.</div>
-</li>
-<li class="level1"><div class="li"> Although it is optional, you may wish to install a tool which can be used for plotting the output data. SWITCAP produces both <acronym title="American Standard Code for Information Interchange">ASCII</acronym> data listings as well as ugly <acronym title="American Standard Code for Information Interchange">ASCII</acronym> plots (note the release date of the version of SWITCAP used). Suitable tools are:</div>
-<ol>
-<li class="level2"><div class="li"> Gwave. Gwave is an analog waveform viewer. It is fairly basic, but easy to use, includes cursors, and has zoom/pan features. See <strong><a href="http://www.geda.seul.org/"; class="urlextern" title="http://www.geda.seul.org"; rel="nofollow">http://www.geda.seul.org</a></strong></div>
-</li>
-<li class="level2"><div class="li"> Scilab. Similar to matlab. Powerful, but no cursors or panning. See <strong><a href="http://www-rocq.inria.fr/scilab"; class="urlextern" title="http://www-rocq.inria.fr/scilab"; rel="nofollow">http://www-rocq.inria.fr/scilab</a></strong></div>
-</li>
-<li class="level2"><div class="li"> Octave. Similar to matlab. See <strong><a href="http://www.octave.org/"; class="urlextern" title="http://www.octave.org"; rel="nofollow">http://www.octave.org</a></strong></div>
-</li>
-<li class="level2"><div class="li"> Grace. See <strong><a href="http://plasma-gate.weizmann.ac.il/Grace/"; class="urlextern" title="http://plasma-gate.weizmann.ac.il/Grace/"; rel="nofollow">http://plasma-gate.weizmann.ac.il/Grace/</a></strong></div>
-</li>
-</ol>
-</li>
-</ol>
-
-</div>
-<!-- SECTION "Requirements" [925-2127] -->
-<h2><a name="creating_schematics" id="creating_schematics">Creating Schematics</a></h2>
-<div class="level2">
-
-</div>
-<!-- SECTION "Creating Schematics" [2128-2159] -->
-<h3><a name="required_symbols" id="required_symbols">Required Symbols</a></h3>
-<div class="level3">
-
-<p>
-This section assumes you are familiar with using gschem to create and edit schematics. SWITCAP netlisting is only supported for the components contained in the SWITCAP symbol library as well as the ground symbol found in the â??powerâ?? library which comes with gEDA. All allowed SWITCAP elements except for subcircuits are supported. You <em>must</em> include the following elements on your schematic:
-</p>
-<ol>
-<li class="level1"><div class="li"> One instance of the switcap-timing symbol. This symbol will set the master clock period for your simulations.</div>
-</li>
-<li class="level1"><div class="li"> One or more instances of the switcap-clock symbol. This symbol defines a clock with a particular phase and period. The reference designator of the clock symbol is used by the switches to set what phase they switch on.</div>
-</li>
-<li class="level1"><div class="li"> One or more instances of the switcap-analysis symbol. This symbol defines an analysis by specifying a file to include in the SWITCAP netlist. By including multiple instances of this symbol, multiple analysis files may be included.</div>
-</li>
-</ol>
-
-</div>
-<!-- SECTION "Required Symbols" [2160-3152] -->
-<h3><a name="optional_symbols" id="optional_symbols">Optional Symbols</a></h3>
-<div class="level3">
-
-<p>
-You can also optionally add the following SWITCAP special symbols to your schematic:
-</p>
-<ol>
-<li class="level1"><div class="li"> Zero or one instance of the switcap-title symbol. This will add a TITLE: line to the SWITCAP netlist and will appear in the output file.</div>
-</li>
-<li class="level1"><div class="li"> Zero or one instance of the switcap-options symbol. By editing the OPTIONS attribute on this symbol you can set the various options which can be passed to SWITCAP.</div>
-</li>
-</ol>
-
-</div>
-<!-- SECTION "Optional Symbols" [3153-3574] -->
-<h3><a name="net_names" id="net_names">Net Names</a></h3>
-<div class="level3">
-
-<p>
-When creating schematics to drive SWITCAP, you should name all nets that you wish to plot. To avoid possible conflicts with unnamed nets, you should avoid using purely numerical names for nets because all unnamed nets will be assigned (somewhat randomly) numbers without checking for possible conflicts with explicitly named nets. SWITCAP limits the length of node names to 7 characters.
-</p>
-
-</div>
-<!-- SECTION "Net Names" [3575-3983] -->
-<h3><a name="switches" id="switches">Switches</a></h3>
-<div class="level3">
-
-<p>
-When placing switches on your schematic, you will need to define which clock they are controlled with. This is done by setting the clock attribute on the switch to the reference designator of the clock which should control it.
-</p>
-
-</div>
-<!-- SECTION "Switches" [3984-4230] -->
-<h2><a name="extracting_the_switcap_netlist" id="extracting_the_switcap_netlist">Extracting the SWITCAP Netlist</a></h2>
-<div class="level2">
-
-<p>
-To extract the SWITCAP netlist, run:
-</p>
-<pre class="code">gnetlist -g switcap -o test.scn file1.sch [file2.sch ...]</pre>
-
-<p>
-For the example file contained in this archive, you can run:
-</p>
-<pre class="code">gnetlist -g switcap -o example.scn ckt.sch clocks.sch analysis.sch</pre>
-
-<p>
-The netlist will be left in <strong>example.scn</strong>.
-</p>
-
-</div>
-<!-- SECTION "Extracting the SWITCAP Netlist" [4231-4570] -->
-<h2><a name="running_switcap" id="running_switcap">Running SWITCAP</a></h2>
-<div class="level2">
-
-<p>
-I typically use something like:
-</p>
-<pre class="code">printf "example.scn\nexample.out\n" | sw</pre>
-
-<p>
-so I can use command history to rerun SWITCAP without having to manually type the file names each time.<br/>
- Refer to the SWITCAP manual for more details.
-</p>
-
-</div>
-<!-- SECTION "Running SWITCAP" [4571-4838] -->
-<h2><a name="appendix_a_--_symbols_in_the_library" id="appendix_a_--_symbols_in_the_library">Appendix A -- Symbols in the Library</a></h2>
-<div class="level2">
-
-</div>
-<!-- SECTION "Appendix A -- Symbols in the Library" [4839-4887] -->
-<h3><a name="capacitors_switcap-capacitor" id="capacitors_switcap-capacitor">Capacitors (switcap-capacitor)</a></h3>
-<div class="level3">
-
-<p>
-Ideal capacitor. Attributes:
-</p>
-<ul>
-<li class="level1"><div class="li"> <strong>C</strong>=capacitance. Required. Specifies filename to be included.</div>
-</li>
-<li class="level1"><div class="li"> <strong>refdes</strong>=reference designator. Required. Must start with â??Câ?? and be unique.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Capacitors (switcap-capacitor)" [4888-5108] -->
-<h3><a name="switches_switcap-switch" id="switches_switcap-switch">Switches (switcap-switch)</a></h3>
-<div class="level3">
-
-<p>
-Ideal switch. Attributes:
-</p>
-<ul>
-<li class="level1"><div class="li"> <strong>clock</strong>=Controlling clock. Required. Specifies which clock controls this switch.</div>
-</li>
-<li class="level1"><div class="li"> <strong>refdes</strong>=reference designator. Required. Must start with â??Sâ?? and be unique.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Switches (switcap-switch)" [5109-5340] -->
-<h3><a name="independent_voltage_sources_switcap-vsrc" id="independent_voltage_sources_switcap-vsrc">Independent Voltage Sources (switcap-vsrc)</a></h3>
-<div class="level3">
-
-<p>
-Attributes:
-</p>
-<ul>
-<li class="level1"><div class="li"> <strong>refdes</strong>=reference designator. Required. Must start with â??Vâ?? and be unique.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Independent Voltage Sources (switcap-vsrc)" [5341-5488] -->
-<h3><a name="dependent_voltage_sources_switcap-vcvs" id="dependent_voltage_sources_switcap-vcvs">Dependent Voltage Sources (switcap-vcvs)</a></h3>
-<div class="level3">
-
-<p>
-Attributes:
-</p>
-<ul>
-<li class="level1"><div class="li"> <strong>gain</strong>=gain. Required. Specifies the gain of the controlled source.</div>
-</li>
-<li class="level1"><div class="li"> <strong>refdes</strong>=reference designator. Required. Must start with â??Eâ?? and be unique.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Dependent Voltage Sources (switcap-vcvs)" [5489-5708] -->
-<h3><a name="clock_specification_switcap-clock" id="clock_specification_switcap-clock">Clock Specification (switcap-clock)</a></h3>
-<div class="level3">
-
-<p>
-Attributes:
-</p>
-<ul>
-<li class="level1"><div class="li"> <strong>PSTART</strong>=starting clock phase. Required. Specifies on what phase of the master clock this clock turns on.</div>
-</li>
-<li class="level1"><div class="li"> <strong>PSTOP</strong>=ending clock phase. Required. Specifies on what phase of the master clock this clock turns off.</div>
-</li>
-<li class="level1"><div class="li"> <strong>PERIOD</strong>=clock period. Required. Specifies the period of the clock in terms of master clock cycles.</div>
-</li>
-<li class="level1"><div class="li"> <strong>refdes</strong>=reference designator. Required. The switches that are controlled by this clock will refer to it by the reference designator. As such, avoid running any reference designator renumbering tools.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Clock Specification (switcap-clock)" [5709-6302] -->
-<h3><a name="master_timing_specification_switcap-timing" id="master_timing_specification_switcap-timing">Master Timing Specification (switcap-timing)</a></h3>
-<div class="level3">
-
-<p>
-Attributes:
-</p>
-<ul>
-<li class="level1"><div class="li"> PERIOD=clock period. Required. Specifies the period of the master clock in seconds.</div>
-</li>
-</ul>
-
-<p>
- Only a single instance of this symbol is allowed.
-</p>
-
-</div>
-<!-- SECTION "Master Timing Specification (switcap-timing)" [6303-6509] -->
-<h3><a name="analysis_file_include_switcap-analysis" id="analysis_file_include_switcap-analysis">Analysis File Include (switcap-analysis)</a></h3>
-<div class="level3">
-
-<p>
-This symbol will cause a specified file containing SWITCAP analysis commands to be included in the output netlist. Attributes:
-</p>
-<ul>
-<li class="level1"><div class="li"> <strong>file</strong>=filename. Required. Specifies filename to be included.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Analysis File Include (switcap-analysis)" [6510-6756] -->
-<h3><a name="simulation_title_specification_switcap-title" id="simulation_title_specification_switcap-title">Simulation Title Specification (switcap-title)</a></h3>
-<div class="level3">
-
-<p>
-Attributes:
-</p>
-<ul>
-<li class="level1"><div class="li"> <strong>TITLE</strong>=switcap title. Required. Specifies the TITLE line for the SWITCAP netlist.</div>
-</li>
-</ul>
-
-<p>
- Only a single instance of this symbol is allowed.
-</p>
-
-</div>
-<!-- SECTION "Simulation Title Specification (switcap-title)" [6757-6966] -->
-<h3><a name="simulation_options_specification_switcap-options" id="simulation_options_specification_switcap-options">Simulation Options Specification (switcap-options)</a></h3>
-<div class="level3">
-
-<p>
-Attributes:
-</p>
-<ul>
-<li class="level1"><div class="li"> <strong>OPTIONS</strong>=switcap options. Required. Specifies the OPTIONS line for the SWITCAP netlist. See the SWITCAP manual for allowed values.</div>
-</li>
-</ul>
-
-<p>
- Only a single instance of this symbol is allowed.
-</p>
-
-</div>
-<!-- SECTION "Simulation Options Specification (switcap-options)" [6967-7229] -->
-<h2><a name="example" id="example">Example</a></h2>
-<div class="level2">
-
-<p>
-This appendix provides a simple example of the entire process of generating a schematic, producing a SWITCAP netlist, running a simulation, and plotting the results.
-</p>
-<table class="inline">
- <tr>
- <td> <a href="_detail/geda_switcap_figure1.html" class="media" title="geda:switcap_figure1.jpg"><img src="_media/geda_switcap_figure1.jpg" class="media" title="switcap_figure1.jpg" alt="switcap_figure1.jpg" /></a> </td>
- </tr>
- <tr>
- <td> <a href="_detail/geda_switcap_figure2.html" class="media" title="geda:switcap_figure2.jpg"><img src="_media/geda_switcap_figure2.jpg" class="media" title="switcap_figure2.jpg" alt="switcap_figure2.jpg" /></a> </td>
- </tr>
- <tr>
- <td> <a href="_detail/geda_switcap_figure3.html" class="media" title="geda:switcap_figure3.jpg"><img src="_media/geda_switcap_figure3.jpg" class="media" title="switcap_figure3.jpg" alt="switcap_figure3.jpg" /></a> </td>
- </tr>
- <tr>
- <td> <a href="_detail/geda_switcap_figure4.html" class="media" title="geda:switcap_figure4.jpg"><img src="_media/geda_switcap_figure4.jpg" class="media" title="switcap_figure4.jpg" alt="switcap_figure4.jpg" /></a> </td>
- </tr>
-</table>
-
-<p>
- Figure 5/6: Simulation Results - Transient MISSING
-</p>
-
-</div>
-<!-- SECTION "Example" [7230-7605] -->
-<h3><a name="example_schematics" id="example_schematics">Example Schematics</a></h3>
-<div class="level3">
-
-<p>
-<strong>Figure 1</strong> shows the schematic of a simple switched capacitor circuit. Note that some switches, S1 and S3 for example, are controlled by CLK1 while others, S2 and S4 for example, are controlled by the complement of CLK1 (#CLK1).<br/>
- <strong>Figure 2</strong> shows the definition of a clock and the master clock. Here we define a master clock period (mcp) of 1.0 μs in the timing block. In the clock definition symbol, we define a clock called CLK1 that has a period equal to 1 master clock period (mcp). The phase of CLK1 turning on switches is 0 and the phase of CLK1 turning off switches is 3/8 mcp. Additional clock phases can be defined by creating more instances of the clock definition symbol.<br/>
- <strong>Figure 3</strong> shows an instantiation of the title block symbol which will cause â??my titleâ?? to be used in the TITLE line in the SWITCAP netlist. Figure 3 also shows an instantiation of an analysis block which directs the netlister to include the contents of the file test.ana in the output netlist. <strong>Figure 4</strong> shows the contents of the test.ana file.
-</p>
-
-</div>
-<!-- SECTION "Example Schematics" [7606-8677] -->
-<h3><a name="netlist_the_design" id="netlist_the_design">Netlist the Design</a></h3>
-<div class="level3">
-
-<p>
-To netlist the design, run:
-</p>
-<pre class="code">gnetlist -g switcap -o example.scn ckt.sch clocks.sch analysis.sch</pre>
-
-</div>
-<!-- SECTION "Netlist the Design" [8678-8815] -->
-<h3><a name="run_the_simulation" id="run_the_simulation">Run the Simulation</a></h3>
-<div class="level3">
-
-<p>
-Run the simulation with:
-</p>
-<pre class="code">printf "example.scn\nexample.out\n" | sw</pre>
-
-</div>
-<!-- SECTION "Run the Simulation" [8816-8924] -->
-<h3><a name="process_the_results" id="process_the_results">Process the Results</a></h3>
-<div class="level3">
-
-<p>
-Convert the SWITCAP output file to something gwave can read by running:
-</p>
-<pre class="code">sw2asc example.out</pre>
-
-</div>
-<!-- SECTION "Process the Results" [8925-9059] -->
-<h3><a name="plot_the_results" id="plot_the_results">Plot the Results</a></h3>
-<div class="level3">
-
-<p>
-Start up the gwave program and load the first sinusoidal steady state result by running:
-</p>
-<pre class="code">gwave example.out.SSS.1.asc</pre>
-
-<p>
-Drag the two waveforms onto the two waveform panels and change the x-axis to a log scale. Figure 5 shows the output. Start up the gwave program and load the transient result by running:
-</p>
-<pre class="code">gwave example.out.TRAN.1.asc</pre>
-
-</div>
-<!-- SECTION "Plot the Results" [9060-9446] -->
-<h2><a name="document_revision_history" id="document_revision_history">Document Revision History</a></h2>
-<div class="level2">
-<table class="inline">
- <tr>
- <td> April 13th, 2003 </td><td> Created switcap.tex </td>
- </tr>
-</table>
-
-</div>
-<!-- SECTION "Document Revision History" [9447-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/geda_style_guide.html b/docs/wiki/geda_style_guide.html
deleted file mode 100644
index 3b742a6..0000000
--- a/docs/wiki/geda_style_guide.html
+++ /dev/null
@@ -1,167 +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>geda:style_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:25-0400" />
-<meta name="keywords" content="geda,style_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/geda:style_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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:style_guide"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:style_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="#style_guide" class="toc">Style Guide</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#downloading_installing_pavuk" class="toc">Downloading/Installing pavuk</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#downloading_installing_htmldoc" class="toc">Downloading/Installing HTMLDOC</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#for_both_existing_and_new_documents" class="toc">For both existing and new documents</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#for_new_documents" class="toc">For new documents:</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#for_existing_documents" class="toc">For existing documents:</a></span></div></li></ul>
-</li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="style_guide" id="style_guide">Style Guide</a></h1>
-<div class="level1">
-
-<p>
-<span class="hilited">This is definitely a work in progress.</span><br/>
- All documentation is eventually going to be made available as both <acronym title="HyperText Markup Language">HTML</acronym> and <acronym title="Portable Document Format">PDF</acronym>.<br/>
- The problem is to convert the gEDA wikiâ??s Dokuwiki-pages (i.e., <acronym title="Extensible HyperText Markup Language">XHTML</acronym>) into a format that can be converted into <acronym title="Portable Document Format">PDF</acronym>.<br/>
- The ideal path would be to use the pavuk application to mine the gEDA wiki, converting the <acronym title="Extensible HyperText Markup Language">XHTML</acronym> wiki-pages into <acronym title="HyperText Markup Language">HTML</acronym> pages, and then use the HTMLDOC application to convert the <acronym title="HyperText Markup Language">HTML</acronym> pages to <acronym title="Portable Document Format">PDF</acronym>.<br/>
-
-</p>
-
-</div>
-<!-- SECTION "Style Guide" [1-472] -->
-<h2><a name="downloading_installing_pavuk" id="downloading_installing_pavuk">Downloading/Installing pavuk</a></h2>
-<div class="level2">
-
-<p>
-pavuk is a function-testing, performance-measuring, site-mirroring, web spider that is widely portable and capable of using scenarios to process a wide range of web transactions, including ssl and forms.<br/>
- pavuk is hosted on SourceForge at <a href="http://sourceforge.net/projects/pavuk"; class="urlextern" title="http://sourceforge.net/projects/pavuk"; rel="nofollow">http://sourceforge.net/projects/pavuk</a>. Simply check if your distribution already includes the latest version of pavuk (pavuk-0.9.34 used for the current wiki), and download/install if necessary.<br/>
- pavuk comes as an RPM, a tar-ball, and a compressed tar-ball. Donâ??t install from the RPM, as this uses dated library dependencies and may not build on newer distributions.<br/>
- pavuk has both a command-line interface and a <acronym title="Graphical User Interface">GUI</acronym> interface.
-</p>
-
-</div>
-<!-- SECTION "Downloading/Installing pavuk" [473-1190] -->
-<h2><a name="downloading_installing_htmldoc" id="downloading_installing_htmldoc">Downloading/Installing HTMLDOC</a></h2>
-<div class="level2">
-
-<p>
-HTMLDOC converts <acronym title="HyperText Markup Language">HTML</acronym> files and web pages into indexed <acronym title="HyperText Markup Language">HTML</acronym>, PostScript, and <acronym title="Portable Document Format">PDF</acronym> files suitable for on-line viewing and printing.<br/>
- HTMLDOC is hosted at <a href="http://www.easysw.com/htmldoc/"; class="urlextern" title="http://www.easysw.com/htmldoc/"; rel="nofollow">http://www.easysw.com/htmldoc/</a>, and may be downloaded/installed under the open-source license for non-commercial applications. Simply check if you distribution already includes HTMLDOC version htmldoc-1.8-27 or later, and install as appropriate. Note that RPM distributions are available, so that your normal package install/update utilities may already contain HTMLDOC (e.g., htmldoc-1.8.27 is in Fedora Core 4 extras repository and may be installed using yum).<br/>
- HTMLDOC version htmldoc-1.8.26 is broken, it will not generate appropriate <acronym title="Portable Document Format">PDF</acronym> documents.<br/>
- Note one limitation of HTMLDOC. It is based on <acronym title="HyperText Markup Language">HTML</acronym> 3.o, not <acronym title="HyperText Markup Language">HTML</acronym> 4.01. Many <acronym title="HyperText Markup Language">HTML</acronym> 4.01 tags are not recognized by HTMLDOC.<br/>
- HTMLDOC is both a <acronym title="Graphical User Interface">GUI</acronym> application and a command-line application. Use it as you feel most comfortable.
-</p>
-
-</div>
-<!-- SECTION "Downloading/Installing HTMLDOC" [1191-2172] -->
-<h2><a name="for_both_existing_and_new_documents" id="for_both_existing_and_new_documents">For both existing and new documents</a></h2>
-<div class="level2">
-
-<p>
-The following are meant to stimulate discussion on document style:
-</p>
-<ol>
-<li class="level1"><div class="li"> Consider that the document will be exported for inclusion on the â??gEDA Tools Suite CD-ROMâ?? as <acronym title="Extensible HyperText Markup Language">XHTML</acronym> and/or <acronym title="Portable Document Format">PDF</acronym>. Examples:</div>
-<ul>
-<li class="level2"><div class="li"> <a href="http://geda.seul.org/wiki/?do=export_raw"; class="urlextern" title="http://geda.seul.org/wiki/?do=export_raw"; rel="nofollow">http://geda.seul.org/wiki/?do=export_raw</a> will generate the gEDA Project Wikiâ??s start page as plain text. Simply use your browser to copy to a text file and include on the CD-ROM image.</div>
-</li>
-<li class="level2"><div class="li"> <a href="http://geda.seul.org/wiki/?do=export_xhtml"; class="urlextern" title="http://geda.seul.org/wiki/?do=export_xhtml"; rel="nofollow">http://geda.seul.org/wiki/?do=export_xhtml</a> will generate the gEDA Project Wikiâ??s start page as valid <acronym title="Extensible HyperText Markup Language">XHTML</acronym>. Simply use your browser to â??Save Page As…â??, and name the file {filename}.html. Note that the URLs in this file are NOT relative to this file, but are as they would be found on the gEDA Project Wiki.</div>
-</li>
-<li class="level2"><div class="li"> <a href="http://geda.seul.org/wiki/?do=export_xhtmlbody"; class="urlextern" title="http://geda.seul.org/wiki/?do=export_xhtmlbody"; rel="nofollow">http://geda.seul.org/wiki/?do=export_xhtmlbody</a> will generate the gEDA Project Wikiâ??s start page as valid rendered <acronym title="Extensible HyperText Markup Language">XHTML</acronym>. Simply use your browser to â??Save Page As…â??, and name the file {filename}.html. Note that the URLs in this file are NOT relative to this file, but are as they would be found on the gEDA Project Wiki.</div>
-</li>
-<li class="level2"><div class="li"> The following sequence of commands will retreive a gEDA Project Wiki page (for a list of the gEDA Project Wikiâ??s pages, use the Index button at the bottom of the page) from the â??gedaâ?? namespace (when new wiki-pages are created, we <em class="u">explicitly</em> create them in the â??gedaâ?? namespace) and convert that page into a <acronym title="Portable Document Format">PDF</acronym> document:<br/>
- <pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">% wget --convert-links -O {page-name}.wget "http://geda.seul.org/wiki/geda:{page-name}?do=export_html"
-% sed -e 's/\&amp;/\&/g' {page-name}.wget > {page-name}.sed
-% iconv -f utf-8 -t iso-8859-1 {page-name}.sed > {page-name}.iconv
-% htmldoc {page-name}.iconv -t pdf14 --webpage --no-title --linkstyle underline --size letter --left 1.00in \\
- --right 0.50in --top 0.50in --bottom 0.50in --header .t. --footer . --nup 1 --tocheader .t. --tocfooter ..i \\
- --portrait --color --no-pscommands --no-xrxcomments --compression=1 --jpeg=0 --fontsize 11.0 --fontspacing 1.2 \\
- --headingfont Helvetica --bodyfont Times --headfootsize 11.0 --headfootfont Helvetica --charset iso-8859-1 \\
- --links --no-embedfonts --pagemode document --pagelayout single --firstpage p1 --pageeffect none \\
- --pageduration 10 --effectduration 1.0 --no-encryption --permissions all --owner-password ""
- --user-password "" --browserwidth 680 -f {page-name}.pdf</font></pre> <br/>
- where <strong><code>{page-name}</code></strong> is the wikiâ??s page name as seen in the upper-left corner of the wiki.</div>
-</li>
-</ul>
-</li>
-</ol>
-
-<p>
- For example, you would replace {page-name} above with the following for the related wiki-page:
-</p>
-<ul>
-<li class="level1"><div class="li"> start – The wikiâ??s main page, at <a href="http://geda.seul.org/wiki/"; class="urlextern" title="http://geda.seul.org/wiki/"; rel="nofollow">http://geda.seul.org/wiki/</a>.</div>
-</li>
-<li class="level1"><div class="li"> geda:style_guide – This wiki-page, at <a href="http://geda.seul.org/wiki/geda:style_guide"; class="urlextern" title="http://geda.seul.org/wiki/geda:style_guide"; rel="nofollow">http://geda.seul.org/wiki/geda:style_guide</a>.</div>
-</li>
-<li class="level1"><div class="li"> geda:faq – The wikiâ??s <acronym title="Frequently Asked Questions">FAQ</acronym> page, at <a href="http://geda.seul.org/wiki/geda:faq"; class="urlextern" title="http://geda.seul.org/wiki/geda:faq"; rel="nofollow">http://geda.seul.org/wiki/geda:faq</a></div>
-</li>
-</ul>
-
-<p>
- A <span class="hilited">sample script</span> to convert a single wiki-page into a <acronym title="Portable Document Format">PDF</acronym> document.<br/>
- A <span class="hilited">sample script</span> to convert multiple wiki-pages into a single <acronym title="Portable Document Format">PDF</acronym> document.
-</p>
-
-<p>
-An example of the current (as of 08 May 2006) version of the Wiki, <a href="http://www.offramp.com/wiki/FC5_files/Wiki.pdf"; class="urlextern" title="http://www.offramp.com/wiki/FC5_files/Wiki.pdf"; rel="nofollow">converted to PDF</a>.
-</p>
-
-</div>
-<!-- SECTION "For both existing and new documents" [2173-5272] -->
-<h2><a name="for_new_documents" id="for_new_documents">For new documents:</a></h2>
-<div class="level2">
-
-<p>
-The following are meant to stimulate discussion on document style:
-</p>
-<ol>
-<li class="level1"><div class="li"> You must â??ownâ?? all content in the document. If you do not â??ownâ?? the content, you must get explicit permission from the â??ownerâ?? to copy the content to the gEDA Project Wiki (see below). Documents on the gEDA Project Wiki should be stand-alone, in the event the source document web-site disappears.</div>
-</li>
-<li class="level1"><div class="li"> <strong>All</strong> document contents are to be hosted on the gEDA Project Wiki. Images and other media files are to be uploaded to the wiki, and linked to. Do NOT link to external sites unless absolutely necessary.</div>
-</li>
-<li class="level1"><div class="li"> All documents are to be maintained in the â??gedaâ?? <a href="http://wiki.splitbrain.org/wiki:namespaces"; class="urlextern" title="http://wiki.splitbrain.org/wiki:namespaces"; rel="nofollow">namespace</a>. If your document would take advantage of a separate namespace, ask Ales if â??geda:sub-namespaceâ?? is acceptable. This would be appropriate for very large documents with multiple chapters and lots of images. Such a namespace structure would allow the document to be â??brokenâ?? into chapters for easier navigation by the user (see <a href="http://wiki.splitbrain.org/wiki:index"; class="urlextern" title="http://wiki.splitbrain.org/wiki:index"; rel="nofollow">Index</a> for more details).</div>
-</li>
-</ol>
-
-</div>
-<!-- SECTION "For new documents:" [5273-6383] -->
-<h2><a name="for_existing_documents" id="for_existing_documents">For existing documents:</a></h2>
-<div class="level2">
-
-<p>
-The following are meant to stimulate discussion on document style:
-</p>
-<ol>
-<li class="level1"><div class="li"> </div>
-</li>
-</ol>
-
-</div>
-<!-- SECTION "For existing documents:" [6384-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/geda_suse_10.html b/docs/wiki/geda_suse_10.html
deleted file mode 100644
index ab05eb6..0000000
--- a/docs/wiki/geda_suse_10.html
+++ /dev/null
@@ -1,85 +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>geda:suse_10.0</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-05-24T22:27:26-0400" />
-<meta name="keywords" content="geda,suse_10.0" />
-<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/geda:suse_10.0?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:suse_10.0"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:suse_10.0"; />
-<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">
-
-
-
-<h1><a name="suse_10.0_install_notes" id="suse_10.0_install_notes">Suse 10.0 install notes</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "Suse 10.0 install notes" [1-39] -->
-<h2><a name="prerequisites" id="prerequisites">Prerequisites:</a></h2>
-<div class="level2">
-
-<p>
-First off, I suggest you use the installer with date code 20051203 (or later). The 2005080X installer may not work with SuSE-10.0 without major upfront preparation.
-</p>
-
-<p>
-Secondly, if you are installing gEDA onto a pre-existing SuSE system, make sure your system runs the Gnome desktop, or at least has the Gnome libraries installed. If you have a KDE desktop system, unpredictable things may happen with the installer.
-</p>
-
-<p>
-The remainder of these instructions describe how to build your SuSE system so that you may install gEDA. If you already have gEDA built (and itâ??s a Gnome desktop), you can use YaST to install any of the below-mentioned packages you might be missing from your original install.
-</p>
-
-<p>
-When installing SuSE-10.0 using YaST, click on the â??changeâ?? button when YaST shows you your configuration. Select â??softwareâ?? â?? â??detailsâ??. Then add the following packages to your installation list:
-</p>
-<ul>
-<li class="level1"><div class="li"> C/C++ tools</div>
-</li>
-<li class="level1"><div class="li"> Kernal development</div>
-</li>
-<li class="level1"><div class="li"> Gnome development</div>
-</li>
-<li class="level1"><div class="li"> KDE development</div>
-</li>
-<li class="level1"><div class="li"> TCL/Tk development</div>
-</li>
-</ul>
-
-<p>
- Then change the filter to search for and install the following packages:
-</p>
-<ul>
-<li class="level1"><div class="li"> Gtk-devel</div>
-</li>
-<li class="level1"><div class="li"> Termcap</div>
-</li>
-<li class="level1"><div class="li"> Ncurses-devel</div>
-</li>
-<li class="level1"><div class="li"> wxGTK-devel</div>
-</li>
-</ul>
-
-<p>
- Once these packages are installed, the installer should run to completion.
-</p>
-
-</div>
-<!-- SECTION "Prerequisites:" [40-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/geda_suse_9.html b/docs/wiki/geda_suse_9.html
deleted file mode 100644
index b924f98..0000000
--- a/docs/wiki/geda_suse_9.html
+++ /dev/null
@@ -1,77 +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>geda:suse_9.3</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-05-24T22:27:26-0400" />
-<meta name="keywords" content="geda,suse_9.3" />
-<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/geda:suse_9.3?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:suse_9.3"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:suse_9.3"; />
-<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">
-
-
-
-<h1><a name="installer_2005080x_on_suse_9.3_install_notes" id="installer_2005080x_on_suse_9.3_install_notes">Installer 2005080X on Suse 9.3 install notes</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "Installer 2005080X on Suse 9.3 install notes" [1-59] -->
-<h2><a name="prerequisites" id="prerequisites">Prerequisites:</a></h2>
-<div class="level2">
-
-<p>
-When installing SuSE using YaST, click on the â??changeâ?? button when YaST shows you your configuration. Select â??softwareâ?? â?? â??detailsâ??. Then add the following packages to your installation list:
-</p>
-<ul>
-<li class="level1"><div class="li"> C/C++ tools</div>
-</li>
-<li class="level1"><div class="li"> Kernal development</div>
-</li>
-<li class="level1"><div class="li"> Gnome development</div>
-</li>
-<li class="level1"><div class="li"> KDE development</div>
-</li>
-<li class="level1"><div class="li"> TCL/Tk development</div>
-</li>
-</ul>
-
-<p>
- Then change the filter to search for and install the following packages:
-</p>
-<ul>
-<li class="level1"><div class="li"> Gtk-devel</div>
-</li>
-<li class="level1"><div class="li"> Termcap</div>
-</li>
-<li class="level1"><div class="li"> Ncurses-devel</div>
-</li>
-<li class="level1"><div class="li"> wxGTK-devel</div>
-</li>
-</ul>
-
-<p>
- Once these packages are installed, the installer should run to completion.
-</p>
-
-<p>
-<span class="hilited">More SuSE info to come. . . . .</span>
-</p>
-
-</div>
-<!-- SECTION "Prerequisites:" [60-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/geda_suse_rpm_installation.html b/docs/wiki/geda_suse_rpm_installation.html
deleted file mode 100644
index 132d401..0000000
--- a/docs/wiki/geda_suse_rpm_installation.html
+++ /dev/null
@@ -1,273 +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>geda:suse_rpm_installation</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2008-03-27T04:50:13-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/"; />
-<link rel="contents" href="http://geda.seul.org/wiki/geda:suse_rpm_installation?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:suse_rpm_installation"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:suse_rpm_installation"; />
-<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="#installing_geda_rpm_packages_on_suse" class="toc">Installing gEDA rpm packages on SuSE</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#available_rpm_packages" class="toc">Available rpm packages</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#installing_packages_from_the_suse_build_service" class="toc">Installing Packages from the SuSE Build Service</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>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#suse_10.0" class="toc">SuSE 10.0</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#suse_10.1" class="toc">SuSE 10.1</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#suse_10.2" class="toc">SuSE 10.2</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#suse_10.3" class="toc">SuSE 10.3</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#desktop_integration" class="toc">Desktop Integration</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#electronics_menu" class="toc">Electronics Menu</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#notes_about_rpm_spec_file" class="toc">Notes about rpm spec file</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#installing_rpm_packages_manually" class="toc">Installing rpm packages manually</a></span></div></li></ul>
-</li></ul>
-</li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="installing_geda_rpm_packages_on_suse" id="installing_geda_rpm_packages_on_suse">Installing gEDA rpm packages on SuSE</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "Installing gEDA rpm packages on SuSE" [1-52] -->
-<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 (1.4.0)</div>
-</li>
-<li class="level1"><div class="li"> geda-docs (1.4.0)</div>
-</li>
-<li class="level1"><div class="li"> geda-examples (1.4.0)</div>
-</li>
-<li class="level1"><div class="li"> geda-gattrib (1.4.0)</div>
-</li>
-<li class="level1"><div class="li"> geda-gnetlist (1.4.0)</div>
-</li>
-<li class="level1"><div class="li"> geda-gschem (1.4.0)</div>
-</li>
-<li class="level1"><div class="li"> geda-gsymcheck (1.4.0)</div>
-</li>
-<li class="level1"><div class="li"> geda-symbols (1.4.0)</div>
-</li>
-<li class="level1"><div class="li"> geda-utils (1.4.0)</div>
-</li>
-<li class="level1"><div class="li"> gerbv (2.0.1)</div>
-</li>
-<li class="level1"><div class="li"> pcb (20080202)</div>
-</li>
-<li class="level1"><div class="li"> ng-spice-rework (17)</div>
-</li>
-<li class="level1"><div class="li"> gnucap (0.35)</div>
-</li>
-<li class="level1"><div class="li"> gspiceui (0.9.65)</div>
-</li>
-<li class="level1"><div class="li"> gwave (20051222)</div>
-</li>
-<li class="level1"><div class="li"> gtkwave (3.1.7)</div>
-</li>
-<li class="level1"><div class="li"> dinotrace (9.3f)</div>
-</li>
-<li class="level1"><div class="li"> verilog (0.8.6)</div>
-</li>
-<li class="level1"><div class="li"> wcalc (1.0)</div>
-</li>
-<li class="level1"><div class="li"> xgsch2pcb (0.1.2)</div>
-</li>
-<li class="level1"><div class="li"> electronics-menu (1.0)</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Available rpm packages" [53-558] -->
-<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>
-<li class="level1"><div class="li"> Start Yast and go to â??Change Installation Sourceâ??</div>
-</li>
-<li class="level1"><div class="li"> Add a <acronym title="Hyper Text Transfer Protocol">HTTP</acronym> source with the following properties: </div>
-<ul>
-<li class="level3"><div class="li"> <strong>Servername:</strong> software.opensuse.org</div>
-</li>
-<li class="level3"><div class="li"> <strong>Directory:</strong> /download/repositories/science/openSUSE_10.2/ </div>
-</li>
-</ul>
-</li>
-</ol>
-
-<p>
- (Choose the directory for your distribution)
-</p>
-<ol>
-<li class="level1"><div class="li"> Start â??Install Softwareâ?? in Yast, goto â??Searchâ?? and look for gEDA. All packages appear.</div>
-</li>
-<li class="level1"><div class="li"> Install the packages as usuall.</div>
-</li>
-</ol>
-
-<p>
- 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/science/SUSE_Linux_10.0/repodata/"; class="urlextern" title="http://software.opensuse.org/download/science/SUSE_Linux_10.0/repodata/"; rel="nofollow"> SUSE_Linux_10.0 repo</a>, <a href="http://software.opensuse.org/download/science/SUSE_Linux_10.1/repodata/"; class="urlextern" title="http://software.opensuse.org/download/science/SUSE_Linux_10.1/repodata/"; rel="nofollow"> SUSE_Linux_10.1 repo</a>, <a href="http://software.opensuse.org/download/science/openSUSE_10.2/repodata/"; class="urlextern" title="http://software.opensuse.org/download/science/openSUSE_10.2/repodata/"; rel="nofollow"> openSUSE_10.2 repo</a>, <a href="http://software.opensuse.org/download/science/openSUSE_10.3/repodata/"; class="urlextern" title="http://software.opensuse.org/download/science/openSUSE_10.3/repodata/"; rel="nofollow"> openSUSE_10.3 repo</a>
-</p>
-
-</div>
-<!-- SECTION "Installing Packages from the SuSE Build Service" [559-1663] -->
-<h2><a name="distribution_specific_notes" id="distribution_specific_notes">Distribution specific notes</a></h2>
-<div class="level2">
-
-<p>
- Each distribution version has itâ??s own issues. Please read the notes below.
-</p>
-
-</div>
-<!-- SECTION "Distribution specific notes" [1664-1782] -->
-<h3><a name="suse_10.0" id="suse_10.0">SuSE 10.0</a></h3>
-<div class="level3">
-<ul>
-<li class="level1"><div class="li"> <strong>xgschem2pcb</strong> not available, it requires a more recent dbus library</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "SuSE 10.0" [1783-1879] -->
-<h3><a name="suse_10.1" id="suse_10.1">SuSE 10.1</a></h3>
-<div class="level3">
-<ul>
-<li class="level1"><div class="li"> <strong>xgschem2pcb</strong> not available, it requires a more recent dbus library</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "SuSE 10.1" [1880-1974] -->
-<h3><a name="suse_10.2" id="suse_10.2">SuSE 10.2</a></h3>
-<div class="level3">
-<ul>
-<li class="level1"><div class="li"> <strong>gwave cannot be build</strong>, it requires guile-gtk which requires libglade and gtk12. libglade is no longer part of the SuSE distribution.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "SuSE 10.2" [1975-2137] -->
-<h3><a name="suse_10.3" id="suse_10.3">SuSE 10.3</a></h3>
-<div class="level3">
-<ul>
-<li class="level1"><div class="li"> <strong>gwave cannot be build</strong>, it requires guile-gtk which requires libglade and gtk12. libglade is no longer part of the SuSE distribution.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "SuSE 10.3" [2138-2301] -->
-<h2><a name="desktop_integration" id="desktop_integration">Desktop Integration</a></h2>
-<div class="level2">
-
-<p>
-This is a summary how the gEDA and other electronic packages are integrated into the desktop of openSUSE.
-</p>
-
-</div>
-<!-- SECTION "Desktop Integration" [2302-2441] -->
-<h3><a name="electronics_menu" id="electronics_menu">Electronics Menu</a></h3>
-<div class="level3">
-
-<p>
-Unfortunatly the openSUSE distribution does not provide a electronics menu entry for all the nice gEDA programms. Peter Clifton has created a menu entry for electronics. This menu package is available in the <strong>electronics-menu</strong> rpm. It contains the menu item and some icons for it. The menu categorie is called <strong>Edutainment–>Electronics</strong> in openSUSE.
-</p>
-
-<p>
-If it is installed, it looks like this in KDE (manually combined with gimp):
-</p>
-
-<p>
-<a href="_detail/geda_suse_electronics_menu.html" class="media" title="geda:suse_electronics_menu.png"><img src="_media/geda_suse_electronics_menu.png" class="media" alt="" /></a>
-</p>
-
-</div>
-<!-- SECTION "Electronics Menu" [2442-2942] -->
-<h3><a name="notes_about_rpm_spec_file" id="notes_about_rpm_spec_file">Notes about rpm spec file</a></h3>
-<div class="level3">
-
-<p>
-openSUSE calls itâ??s <em>SuSEconfig</em> program after every installation of rpm packages with YaST. Thus itâ??s not necessary to integrate all configuration calls into the <em>post</em> and <em>postun</em> rpm sections.
-</p>
-
-<p>
-The only additions in the <acronym title="specification">spec</acronym> files are for the <em>Shared <acronym title="Multipurpose Internet Mail Extension">MIME</acronym> Info</em>. It is described in this openSUSE <a href="http://en.opensuse.org/Packaging/SUSE_Package_Conventions/Specific_Packages#10.1.3._Shared_MIME_Info"; class="urlextern" title="http://en.opensuse.org/Packaging/SUSE_Package_Conventions/Specific_Packages#10.1.3._Shared_MIME_Info"; rel="nofollow">SUSE_Package_Conventions/Specific_Packages</a> article.
-</p>
-<pre class="code">PreReq: shared-mime-info
-[...]</pre>
-<pre class="code">%post
-/usr/bin/update-mime-database /opt/gnome/share/mime >/dev/null</pre>
-<pre class="code">%postun
-/usr/bin/update-mime-database /opt/gnome/share/mime >/dev/null</pre>
-
-<p>
- Another addition is required to install the mimelnks properly in the KDE environment. KDE does not take care of the mimelnks installed in <em>/usr/share/mimelnk</em>/, thus they have to be copied to the KDE directory <em>/opt/kde3/mimelnk</em>/. This is done in the rpm <acronym title="specification">spec</acronym> file inside the %install section
-</p>
-<pre class="code">%install
-%makeinstall
-kdemimedir=$(kde-config --install mime)
-mkdir -p "$RPM_BUILD_ROOT""$kdemimedir""/application"
-cp "$RPM_BUILD_ROOT"/usr/share/mimelnk/application/* "$RPM_BUILD_ROOT""$kdemimedir""/application/"</pre>
-
-</div>
-<!-- SECTION "Notes about rpm spec file" [2943-4164] -->
-<h3><a name="installing_rpm_packages_manually" id="installing_rpm_packages_manually">Installing rpm packages manually</a></h3>
-<div class="level3">
-
-<p>
-For those who donâ??t use YaST for installation the SuSEconfig command has to be executed manually after installing or removing any rpm package. You can either call the toplevel SuSEconfig command
-</p>
-<pre class="code">/sbin/SuSEconfig </pre>
-
-<p>
- or call only the two required subconfiguration tools
-</p>
-<pre class="code">/sbin/conf.d/SuSEconfig.desktop-file-utils </pre>
-
-<p>
- which calls
-</p>
-<pre class="code">/usr/bin/update-desktop-database</pre>
-
-<p>
- and
-</p>
-<pre class="code">/sbin/conf.d/SuSEconfig.gtk2</pre>
-
-<p>
- which calls
-</p>
-<pre class="code">/usr/bin/gtk-update-icon-cache --quiet --ignore-theme-index --remove-empty-cache "$SUBDIR"</pre>
-
-</div>
-<!-- SECTION "Installing rpm packages manually" [4165-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/geda_syntax_features.html b/docs/wiki/geda_syntax_features.html
deleted file mode 100644
index e4d5cd8..0000000
--- a/docs/wiki/geda_syntax_features.html
+++ /dev/null
@@ -1,71 +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>geda:syntax_features</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="keywords" content="geda,syntax_features" />
-<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/geda:syntax_features?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:syntax_features"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:syntax_features"; />
-<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">
-
-
-
-<h1><a name="syntax_features" id="syntax_features">Syntax features</a></h1>
-<div class="level1">
-
-<p>
-The new gEDA Project Wiki pages are hosted using Dokuwiki version 09 March 2006. This wiki-engine has several enhancements:
-</p>
-<ul>
-<li class="level1"><div class="li"> Bug fixes.</div>
-</li>
-<li class="level1"><div class="li"> A new toolbar in the editor.</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://wiki.splitbrain.org/wiki:syntax"; class="urlextern" title="http://wiki.splitbrain.org/wiki:syntax"; rel="nofollow">Syntax</a> enhancements.</div>
-</li>
-<li class="level1"><div class="li"> Updates to the <a href="http://wiki.splitbrain.org/wiki:search"; class="urlextern" title="http://wiki.splitbrain.org/wiki:search"; rel="nofollow">Search</a> feature. You can now search for exact phrases by enclosing them with double quotes, and use â??*â?? wildcard searches.</div>
-</li>
-<li class="level1"><div class="li"> Google <a href="http://wiki.splitbrain.org/wiki:sitemap"; class="urlextern" title="http://wiki.splitbrain.org/wiki:sitemap"; rel="nofollow">sitemap</a> support. Your edited content will be indexed by Google much faster.</div>
-</li>
-<li class="level1"><div class="li"> You can upload and embed <a href="http://wiki.splitbrain.org/wiki:images"; class="urlextern" title="http://wiki.splitbrain.org/wiki:images"; rel="nofollow">other files</a> into the pages using the MediaPopup feature on the toolbar in the editor (including image files, flash files, <acronym title="Portable Document Format">PDF</acronym> files, etc.). Please note that image/media files can not be removed once uploaded by an author.</div>
-</li>
-<li class="level1"><div class="li"> Footnotes.</div>
-</li>
-<li class="level1"><div class="li"> Larger global cache, allowing for larger documents (currently set to 20 <acronym title="Megabyte">MB</acronym>).</div>
-</li>
-<li class="level1"><div class="li"> You can subscribe to e-mail pagechange notification, on a wiki-page by wiki-page basis. If you are interested in monitoring the changes made by others to a spicific page, simply press the â??Subscribe Changesâ?? button at the bottom of the wiki-page. To unsubscribe from a wiki-page, simply press the â??Unsubscribe Changesâ?? button.</div>
-</li>
-<li class="level1"><div class="li"> URLs are now â??prettyâ??.</div>
-</li>
-<li class="level1"><div class="li"> Breadcrumbs (i.e., the line at the top of the browserâ??s window that starts with â??Trace:". This is a â??where are youâ?? indicator.</div>
-</li>
-<li class="level1"><div class="li"> Wiki-pages can be <a href="http://wiki.splitbrain.org/wiki:export"; class="urlextern" title="http://wiki.splitbrain.org/wiki:export"; rel="nofollow">exported</a> to different formats (e.g., plain-text, simple <acronym title="Extensible HyperText Markup Language">XHTML</acronym> (the page without navigational elements), rendered <acronym title="Extensible HyperText Markup Language">XHTML</acronym> (no head or body tags), <acronym title="Hyper Text Transfer Protocol">HTTP</acronym>).</div>
-</li>
-<li class="level1"><div class="li"> The <code><code></code></code> tag supports syntax highlighting for numerous programming languages.</div>
-</li>
-<li class="level1"><div class="li"> A playground for authors to â??playâ?? with new features, before implimenting on the wikiâ??s pages.</div>
-</li>
-<li class="level1"><div class="li"> Control of Dokuwikiâ??s <a href="http://wiki.splitbrain.org/wiki:caching#purging_the_cache"; class="urlextern" title="http://wiki.splitbrain.org/wiki:caching#purging_the_cache"; rel="nofollow">caching</a> operations. This is important to wiki-page authors, as sometimes a page gets cached by Dokuwiki on the server, and needs to be purged. Remember, what the author sees may not be what others see.<br/>
- This is different than your browserâ??s cache, which may occassionally need to be flushed. For example, when the <acronym title="Hypertext Preprocessor">PHP</acronym> global memory limit is exceeded, that wiki-page canâ??t be displayed, even if the <acronym title="Hypertext Preprocessor">PHP</acronym> global memory limit is changed on the server. You would need to flush your browserâ??s cache to load and view the wiki-page.</div>
-</li>
-</ul>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_systemc_netlister_readme.html b/docs/wiki/geda_systemc_netlister_readme.html
deleted file mode 100644
index 98df741..0000000
--- a/docs/wiki/geda_systemc_netlister_readme.html
+++ /dev/null
@@ -1,120 +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>geda:systemc_netlister_readme</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="geda,systemc_netlister_readme" />
-<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/geda:systemc_netlister_readme?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:systemc_netlister_readme"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:systemc_netlister_readme"; />
-<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">
-
-
-
-<h1><a name="systemc_netlister_readme" id="systemc_netlister_readme">SystemC netlister README</a></h1>
-<div class="level1">
-<pre class="code">TITLE:
-
- Gnetlist SystemC Backend
-
-OBJECTIVE:
-
- Transform a geda schematic into a transaction based structural systemc module.
-
-LIMITATIONS:
-
- 1.- Only transaction based wires are considered (wire_name<user_type>).
- 2.- Unnamed wires are eliminated.
- 3.- In/out ports have to be inserted manually in the sysc code.
- 4.- Duplicated include headers are not eliminated by the backend.
- 5.- The maximum number of object constructor parameters is 31 (attr1->attr31).
-
-LINKS:
-
- GPL Electronic Design Automation (geda-gnetlist): http://www.geda.seul.org
- SystemC: http://www.systemc.org
-
-ACK:
-
- Based on gnet-verilog.scm by Mike Jarabek.
-
-EXAMPLE:
-
- Schematic:
-
- src1 alg1 snk1
- ______________ _______________ _______________
- | source | a<user_type> | algorithm | b<float> | sink |
- | OUT|__ _________ __|IN OUT|__ _____ __|IN |
- | | | | | |
- | infile.data| | | | outfile.data|
- |____________| |_____________| |_____________|
-
-
- Attributes:
-
- Schematic:
- module_name=test_sch2sysc
-
- Wires:
- netname=a<user_type>
- netname=b<float>
- Symbols:
- refdes=src1 attr1=infile.data
- refdes=alg1
- refdes=snk1 attr1=outfile.data
- refdes=pina
- refdes=pinb
-
- SystemC:
-
- #include "systemc.h"
- #include "sink.h"
- #include "source.h"
- #include "algorithm.h"
-
- SC_MODULE (test_sch2sysc)
- {
- /* Port directions begin here */
-
- /* Wires from the design */
- sc_signal<float> b;
- sc_signal<packet_type> a;
-
- /* Package instantiations */
- sink snk1;
- source src1;
- algorithm alg1;
-
- SC_CTOR(test_sch2sysc):
- snk1("snk1","outfile.data"),
- src1("src1","infile.data"),
- alg1("alg1")
- {
- snk1.IN(b);
- src1.OUT(a);
- alg1.IN(a);
- alg1.OUT(b);
- }
- };
-
-</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_tasks.html b/docs/wiki/geda_tasks.html
deleted file mode 100644
index c541e79..0000000
--- a/docs/wiki/geda_tasks.html
+++ /dev/null
@@ -1,100 +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>geda:tasks</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-09-25T06:10:05-0400" />
-<meta name="keywords" content="geda,tasks" />
-<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/geda:tasks?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:tasks"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:tasks"; />
-<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="#geda_tasks" class="toc">gEDA Tasks</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#important_tasks_for_normal_volunteers" class="toc">important tasks for normal volunteers</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#tasks_for_programmers" class="toc">tasks for programmers</a></span></div></li></ul>
-</li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="geda_tasks" id="geda_tasks">gEDA Tasks</a></h1>
-<div class="level1">
-
-<p>
-gEDA is run by volunteers, so these are volunteer (read: unpaid) tasks. Please consider helping out. Thank you.
-</p>
-
-</div>
-<!-- SECTION "gEDA Tasks" [1-137] -->
-<h2><a name="important_tasks_for_normal_volunteers" id="important_tasks_for_normal_volunteers">important tasks for normal volunteers</a></h2>
-<div class="level2">
-<ul>
-<li class="level1"><div class="li"> <strong>Documentation Writers/Editors</strong><br/>
- Somebody is needed to act as an editor for the gEDA documentation effort. Basically this person would take whatever documentation already exists and/or is currently being written and formats it into something presentable. This individual does not write the actual documentation, but would instead perform editorial work. People who want to write the actual documentation are also needed. (The <a href="http://geda.seul.org/wiki/"; class="urlextern" title="http://geda.seul.org/wiki/"; rel="nofollow"> start</a> page explains how to get started editing the documentation on the wiki).</div>
-</li>
-<li class="level1"><div class="li"> <strong>PCB Publicity Manager</strong><br/>
- Somebody is needed to do publicity for the gEDA project. This consists of posting release updates to the various PCB design websites (such as <a href="http://circuitcalculator.com/"; class="urlextern" title="http://CircuitCalculator.com/"; rel="nofollow">http://CircuitCalculator.com/</a> , <a href="http://www.olimex.com/pcb/dtools.html"; class="urlextern" title="http://www.olimex.com/pcb/dtools.html"; rel="nofollow"> Olimex</a>, <a href="http://www.4pcb.com/index.php?load=content&page_id=46"; class="urlextern" title="http://www.4pcb.com/index.php?load=content&page_id=46"; rel="nofollow"> Advanced Circuits</a>, <a href="http://opencircuits.com/Techniques"; class="urlextern" title="http://opencircuits.com/Techniques"; rel="nofollow"> Open Circuits</a>, <a href="http://www.epanorama.net/"; class="urlextern" title="http://www.ePanorama.net/"; rel="nofollow">http://www.ePanorama.net/</a> , <a href="http://docwiki.gumstix.org/"; class="urlextern" title="http://docwiki.gumstix.org/"; rel="nofollow"> gumstix</a>, <a href="http://reprap.org/bin/view"; class="urlextern" title="http://reprap.org/bin/view"; rel="nofollow"> RepRap</a>, etc.)</div>
-</li>
-<li class="level1"><div class="li"> <strong>Linux Publicity Manager</strong><br/>
- Somebody is needed to do publicity for the gEDA project. This consists of posting release updates to the various Linux/Unix websites (like Freshmeat or <a href="http://lwn.net/"; class="urlextern" title="http://LWN.net/"; rel="nofollow"> LWN</a> or <a href="http://linuxrobots.org/"; class="urlextern" title="http://LinuxRobots.org/"; rel="nofollow">http://LinuxRobots.org/</a> )</div>
-</li>
-<li class="level1"><div class="li"> <strong>UNIX Port Testers</strong><br/>
- People are always needed to test gEDA on different and new UNIX like operating systems. This person would basically download a new release and make sure it works on their platform of choice. Any problems found would be then submitted to the appropriate gEDA author.</div>
-</li>
-<li class="level1"><div class="li"> <strong>Website/Mirror Hacker</strong><br/>
- Somebody to watch over the mirrors and maybe do some <acronym title="HyperText Markup Language">HTML</acronym> hacking is needed. There are currently three websites which need to be monitored and occasionally fixed. The person would also have influence in the changing/expansion of the gEDA website. Duties would be split among the current webmasters.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "important tasks for normal volunteers" [138-2111] -->
-<h2><a name="tasks_for_programmers" id="tasks_for_programmers">tasks for programmers</a></h2>
-<div class="level2">
-
-<p>
- <img src="lib/images/smileys/fixme.gif" class="middle" alt="FIXME" />: <code>should this list be combined with <a href="geda_todos.html" class="wikilink1" title="geda:todos">todos</a> ?</code>
-</p>
-<ul>
-<li class="level1"><div class="li"> <strong>Netlist Hacker</strong><br/>
- Somebody who is familiar with the generation/management of netlists is needed to help work on and improve gnetlist. Whether the existing gnetlist is used or if a total rewrite is needed is always an open option. Must be extremely familiar with UNIX/C/C++ programming.</div>
-</li>
-<li class="level1"><div class="li"> <strong>Symbol Library Hacker</strong><br/>
- Somebody is needed to help get the symbol library up to the current symbol <acronym title="specification">spec</acronym>. This individual would also help in the integration of new symbols and making sure that they meet the current symbol <acronym title="specification">spec</acronym>. The task of getting the symbol library up to <acronym title="specification">spec</acronym> is a combination of manual effort and automated updating (this sort of automated updating lends itself very well to a person with shell/perl scripting familiarity).</div>
-</li>
-<li class="level1"><div class="li"> <strong>geda <acronym title="Graphical User Interface">GUI</acronym> Hacker</strong><br/>
- Somebody who knows C, UNIX, and gtk+ programming is needed to work on the gEDA <acronym title="Graphical User Interface">GUI</acronym> (the program named geda). This program has been stalled for the past year due to the lack of manpower. Whether the existing geda is used or a total rewrite is needed is always an open option.</div>
-</li>
-<li class="level1"><div class="li"> <strong>Windows Port Hacker/Manager</strong><br/>
- Somebody with expertise building and testing gEDA on UNIX systems and familiarity with the <acronym title="Microsoft">MS</acronym> Windows 95/98/NT platform is needed to manage the gEDA Windows port. Testing, bug fixing, packaging, and releasing of gEDA on the Windows platform would be the primary responsibility of this person. This task requires a person who knows C, gtk+, UNIX, and <acronym title="Microsoft">MS</acronym> Windows programming. The Windows port will NOT move forward if this task is not filled.</div>
-</li>
-<li class="level1"><div class="li"> <strong>MacOS port manager</strong>: Have the issues mentioned in <a href="http://www.evilmadscientist.com/article.php/pcbtools"; class="urlextern" title="http://www.evilmadscientist.com/article.php/pcbtools"; rel="nofollow"> "Laying out printed circuit boards with open-source tools"</a> been fixed already?</div>
-</li>
-<li class="level1"><div class="li"> <strong>Release Hacker</strong><br/>
- Somebody who wants to create and manage releases is needed. Releases occur when the code is ready to be released, so thereâ??s no marketing pressure. This task requires gEDA building/testing familiarity as well perhaps some minor code hacking.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "tasks for programmers" [2112-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/geda_todos.html b/docs/wiki/geda_todos.html
deleted file mode 100644
index 6b90f45..0000000
--- a/docs/wiki/geda_todos.html
+++ /dev/null
@@ -1,194 +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>geda:todos</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-08-23T09:28:32-0400" />
-<meta name="keywords" content="geda,todos" />
-<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/geda:todos?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:todos"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:todos"; />
-<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="#todo" class="toc">ToDo</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#things_to_be_done_before_the_next_release" class="toc">Things to be done before the next release</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#longer_term_upgrades_desired_for_specific_tools" class="toc">Longer term upgrades desired for specific tools</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#ideas_for_new_tools_or_geda_suite-wide_enhancements" class="toc">Ideas for new tools or gEDA Suite-wide enhancements</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#code_cleanup_and_refactoring" class="toc">Code cleanup and refactoring</a></span></div></li></ul>
-</li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="todo" id="todo">ToDo</a></h1>
-<div class="level1">
-
-<p>
-These lists are meant to provide developers a reminder of undone projects. It is also a wish list capturing userâ??s desires for new features. New developers can also look here for projects which they might be interested in working on.
-</p>
-
-<p>
-See <a href="http://geda.seul.org/wiki/geda:tasks"; class="wikilink1" title="geda:tasks">tasks</a> for non-programmer tasks.
-</p>
-
-</div>
-<!-- SECTION "ToDo" [1-298] -->
-<h2><a name="things_to_be_done_before_the_next_release" id="things_to_be_done_before_the_next_release">Things to be done before the next release</a></h2>
-<div class="level2">
-<ul>
-<li class="level1"><div class="li"> TBD</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Things to be done before the next release" [299-362] -->
-<h2><a name="longer_term_upgrades_desired_for_specific_tools" id="longer_term_upgrades_desired_for_specific_tools">Longer term upgrades desired for specific tools</a></h2>
-<div class="level2">
-<ul>
-<li class="level1"><div class="li"> <strong>Libgeda</strong>:</div>
-<ul>
-<li class="level2"><div class="li"> Enable handling of .sch files with symbols having some (but not all) pins promoted onto the .sch file. This will enable pin-swapping via backannotation from PCB</div>
-</li>
-<li class="level2"><div class="li"> Merge per-page netlisting from gnetlist (or re-write if necessary).</div>
-</li>
-<li class="level2"><div class="li"> Make postscript output more friendly to the LaTeX package â??pstricksâ??.</div>
-<ul>
-<li class="level3"><div class="li"> Use the â??showâ?? command to display a whole string at once instead of rendering character by character.</div>
-</li>
-<li class="level3"><div class="li"> Might not be possible / simple as the current approach is due to the overbar drawing postscript.</div>
-</li>
-</ul>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"> <strong>Gschem</strong>:</div>
-<ul>
-<li class="level2"><div class="li"> Enable hierarchical bus support.</div>
-</li>
-<li class="level2"><div class="li"> Make gschemrc variables settable from within gschem using a â??settingsâ?? pull-down menu item (new).</div>
-</li>
-<li class="level2"><div class="li"> Improve symbol library to handle very large symbol collections better</div>
-</li>
-<li class="level2"><div class="li"> Now the SELECTION is a GedaList and we can get â??changedâ?? signals, make more dialogs non-modal:</div>
-<ul>
-<li class="level3"><div class="li"> Single attribute editor</div>
-</li>
-<li class="level3"><div class="li"> Text properties</div>
-</li>
-<li class="level3"><div class="li"> Line width and type</div>
-</li>
-<li class="level3"><div class="li"> Fill type</div>
-</li>
-<li class="level3"><div class="li"> Edit slot</div>
-</li>
-<li class="level3"><div class="li"> Edit color</div>
-</li>
-<li class="level3"><div class="li"> Text size (Sets size for new text, so doesnâ??t rely on the selection anyway)</div>
-</li>
-</ul>
-</li>
-<li class="level2"><div class="li"> Enable <strong><code>-</code><code>-</code>help</strong> flag. (Currently supports -h only). Consider using GTKâ??s mechanism for this.</div>
-</li>
-<li class="level2"><div class="li"> Support for embedding LaTeX maths to be rendered in text.</div>
-<ul>
-<li class="level3"><div class="li"> This could be output only, or preview bitmaps could be generated and cached by calling LaTeX, dvips and ps2epsi.</div>
-</li>
-<li class="level3"><div class="li"> Would we add a new type of object for this, or allow attaching a â??latex=1â?? attribute to the text object its self?</div>
-</li>
-</ul>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"> <strong>Gnetlist</strong>:</div>
-<ul>
-<li class="level2"><div class="li"> Enable <strong><code>-</code><code>-</code>help</strong> flag. Do other gEDA/gaf programs recognize this flag?</div>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"> <strong>Gattrib</strong>:</div>
-<ul>
-<li class="level2"><div class="li"> Make it export CSV to support BOM generation.</div>
-</li>
-<li class="level2"><div class="li"> Get printing working.</div>
-</li>
-<li class="level2"><div class="li"> Enable attachment of attributes to nets.</div>
-</li>
-<li class="level2"><div class="li"> Consider using GTKâ??s mechanism to display <strong><code>-</code><code>-</code>help</strong> flag text.</div>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"> <strong>Garchive</strong>:</div>
-<ul>
-<li class="level2"><div class="li"> Incorporate guile so that it reads RC files using the same mechanism as the rest of gEDA/gaf.</div>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"> <strong>CD Installer</strong>:</div>
-<ul>
-<li class="level2"><div class="li"> Change it so that the user is presented a pick-list at the beginning of the install, instead of blindly installing everything.</div>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"> <strong>Refdes_renum</strong>:</div>
-<ul>
-<li class="level2"><div class="li"> Doesnâ??t currently work properly with slotted parts (it gives new refdes numbers to slotted parts). Fix it so it recognizes slotted parts and assigns refdes appropriately.</div>
-</li>
-<li class="level2"><div class="li"> Provide <strong><code>-</code><code>-</code>gentle</strong> option, which doesnâ??t clobber (overwrite) any refdeses which are already assigned.</div>
-</li>
-</ul>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Longer term upgrades desired for specific tools" [363-2872] -->
-<h2><a name="ideas_for_new_tools_or_geda_suite-wide_enhancements" id="ideas_for_new_tools_or_geda_suite-wide_enhancements">Ideas for new tools or gEDA Suite-wide enhancements</a></h2>
-<div class="level2">
-<ul>
-<li class="level1"><div class="li"> Develop scheme for backward annotation of changes from PCB to gschem. Requires modifications to libgeda to support, e.g. pin promotion from .sym file to .sch file (enabling pin swapping).</div>
-</li>
-<li class="level1"><div class="li"> Create a Gerber â?? .pcb conversion tool. Result is metal layer or footprint editable by PCB. This might be a <acronym title="Practical Extraction and Report Language">Perl</acronym> script.</div>
-</li>
-<li class="level1"><div class="li"> Implement lockfiles between gattrib and gschem.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Ideas for new tools or gEDA Suite-wide enhancements" [2873-3309] -->
-<h2><a name="code_cleanup_and_refactoring" id="code_cleanup_and_refactoring">Code cleanup and refactoring</a></h2>
-<div class="level2">
-<ul>
-<li class="level1"><div class="li"> Remove use of non GList linked lists. This is very invasive work, but allows much code cleanup where mixtures of the old and GList methods were available.</div>
-</li>
-<li class="level1"><div class="li"> Remove unused variables and functions from various structures. Unused may also include â??usedâ??, but ineffective.</div>
-</li>
-<li class="level1"><div class="li"> Remove back-exports to libgeda of global function pointers from gschem and other libgeda â??clientsâ??. These arenâ??t portable.</div>
-</li>
-<li class="level1"><div class="li"> Clean up / produce generic <acronym title="Application Programming Interface">API</acronym> interfaces to act on an object of any type, or lists of objects.</div>
-</li>
-<li class="level1"><div class="li"> Convert functions used within one ".câ?? file, and not useful for public <acronym title="Application Programming Interface">API</acronym> into static functions, removing from prototype.h.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Code cleanup and refactoring" [3310-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/geda_tragesym_readme.html b/docs/wiki/geda_tragesym_readme.html
deleted file mode 100644
index 0388a1a..0000000
--- a/docs/wiki/geda_tragesym_readme.html
+++ /dev/null
@@ -1,58 +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>geda:tragesym_readme</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="geda,tragesym_readme" />
-<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/geda:tragesym_readme?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:tragesym_readme"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:tragesym_readme"; />
-<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">
-
-
-
-<h1><a name="tragesym_symbol_generator_readme" id="tragesym_symbol_generator_readme">tragesym (symbol generator) README</a></h1>
-<div class="level1">
-<pre class="code">tragesym is a small python script that creates geda symbols out of
-structured textfiles.
-
-For creating a symbol you have to edit the sourcefile first. You can
-use the template.src file, which is in /examples/tragesym/ directory.
-Some examples are in the examples/tragesym directory too.
-
-For possible footprint names take a look into the ~geda directory
-of the PCB program.
-
-usage is:
- tragesym <sourcefile> <symbolfile>
-
-After you have translated the sourcefile to the symbolfile you have to
-rearrange some pins with gschem, translate the symbol to the origin
-and save it in an appropriate symbol directory. Make the attributes
-visible while doing that (edit->show hidden text) and hide the text
-again before saving.
-
-tragesym requires python (versions greater 1.5 should work).
-
-Comment an questions are welcome.
-Send it to Werner Hoch (werner.ho@xxxxxx)
-</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_tragesym_tutorial.html b/docs/wiki/geda_tragesym_tutorial.html
deleted file mode 100644
index e20df8d..0000000
--- a/docs/wiki/geda_tragesym_tutorial.html
+++ /dev/null
@@ -1,270 +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>geda:tragesym_tutorial</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/"; />
-<link rel="contents" href="http://geda.seul.org/wiki/geda:tragesym_tutorial?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:tragesym_tutorial"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:tragesym_tutorial"; />
-<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="#creating_gschem_symbols_quickly_and_easily_using_tragesym_and_a_spreadsheet_programm" class="toc">Creating gschem symbols quickly and easily using tragesym and a spreadsheet programm</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#required_steps" class="toc">Required Steps</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#step1open_a_tragesym_template_file" class="toc">Step1: Open a tragesym template file</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#step2download_the_part_data_sheet_and_find_the_pin_list" class="toc">Step2: Download the part data sheet and find the pin list</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#step3copy_the_pin_list_into_an_editor_and_prepare_it" class="toc">Step3: Copy the pin list into an editor and prepare it</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#step4insert_all_missing_data_into_the_spreadsheet" class="toc">Step4: Insert all missing data into the spreadsheet</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#step5export_the_spreadsheet_into_a_tab_seperated_text_file" class="toc">Step5: Export the spreadsheet into a tab seperated text file</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#step6execute_tragesym_and_create_the_symbol" class="toc">Step6: execute tragesym and create the symbol</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#step7check_the_result_with_gschem_and_do_some_artwork" class="toc">Step7: check the result with gschem and do some artwork</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#conclusion" class="toc">Conclusion</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#credits" class="toc">Credits</a></span></div></li></ul>
-</li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="creating_gschem_symbols_quickly_and_easily_using_tragesym_and_a_spreadsheet_programm" id="creating_gschem_symbols_quickly_and_easily_using_tragesym_and_a_spreadsheet_programm">Creating gschem symbols quickly and easily using tragesym and a spreadsheet programm</a></h1>
-<div class="level1">
-
-<p>
- Creating symbols for schematic capture can be very time consuming, error prone, and an all around pain. Luckily, gschem uses an open, text based file format that is very easy to use with scripting. This short tutorial describes how to use the tragesym script, to create symbols very quickly (probably more quickly than with any commercial package).
-</p>
-
-</div>
-<!-- SECTION "Creating gschem symbols quickly and easily using tragesym and a spreadsheet programm" [1-450] -->
-<h2><a name="required_steps" id="required_steps">Required Steps</a></h2>
-<div class="level2">
-<ul>
-<li class="level1"><div class="li"> Step1: Open a tragesym template file</div>
-</li>
-<li class="level1"><div class="li"> Step2: Download the part data sheet and find the pin list</div>
-</li>
-<li class="level1"><div class="li"> Step3: Copy the pin list into an editor and prepare it</div>
-</li>
-<li class="level1"><div class="li"> Step4: Insert all missing data into the spreadsheet</div>
-</li>
-<li class="level1"><div class="li"> Step5: Export the spreadsheet into a tab seperated text file</div>
-</li>
-<li class="level1"><div class="li"> Step6: execute tragesym and create the symbol</div>
-</li>
-<li class="level1"><div class="li"> Step7: check the result with gschem and do some artwork</div>
-</li>
-</ul>
-
-</div>
-<!-- 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_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" [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">
-
-<p>
- For this example, we will create a symbol from the Philips Semiconductor PCA9555 16-bit IIC IO port. The description of product and datasheet is available at Philips: <a href="http://www-us.semiconductors.philips.com/cgi-bin/pldb/pip/pca9555.html"; class="urlextern" title="http://www-us.semiconductors.philips.com/cgi-bin/pldb/pip/pca9555.html"; rel="nofollow">http://www-us.semiconductors.philips.com/cgi-bin/pldb/pip/pca9555.html</a>. Download the datasheet and open it with a pdf viewer that allows copying text out of the pdf file, such as kpdf or acroread. Flip through the pages until you find the pinout for the device:
-</p>
-
-<p>
-<a href="_detail/tragesym_kpdf_pinconfiguration.html" class="media" title="tragesym:kpdf_pinconfiguration.png"><img src="_media/tragesym_kpdf_pinconfiguration.png" class="media" alt="" /></a> <a href="_detail/tragesym_acroread_selectiontable.html" class="media" title="tragesym:acroread_selectiontable.png"><img src="_media/tragesym_acroread_selectiontable.png" class="media" alt="" /></a>
-</p>
-
-<p>
-Inside the datasheet the pin list may only be in the drawing of the pin configuration. If thereâ??s a nice table, like in the second picture from a different datasheet, use this one.
-</p>
-
-</div>
-<!-- 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">
-
-<p>
-Select the pin list and copy it into a text editor. This intermediate step is required as your spreadsheet programm may need a special field seperator, like comma or tab. You may have to remove duplicate seperators or replace it with tabs.
-</p>
-
-<p>
-<strong>Note:</strong> The selection behaviour of kpdf is different from the acroread viewer. The kpdf viewer seems to give you a copy that looks more like the graphical representation, while the acroread viewer produces an output that is more â??file orderâ?? oriented. If you have to create a lot of symbols, try both and compare the results.
-</p>
-
-<p>
-<a href="_detail/tragesym_xemacs_rawselection.html" class="media" title="tragesym:xemacs_rawselection.png"><img src="_media/tragesym_xemacs_rawselection.png" class="media" alt="" /></a> <a href="_detail/tragesym_xemacs_modifiedselection.html" class="media" title="tragesym:xemacs_modifiedselection.png"><img src="_media/tragesym_xemacs_modifiedselection.png" class="media" alt="" /></a> <a href="_detail/tragesym_ooo_selection.html" class="media" title="tragesym:ooo_selection.png"><img src="_media/tragesym_ooo_selection.png" class="media" alt="" /></a>
-</p>
-
-<p>
-The pictures above illustrate the steps:
-</p>
-<ul>
-<li class="level1"><div class="li"> insert the selection from your pdf viewer into a text editor</div>
-</li>
-<li class="level1"><div class="li"> modify the pinlist to make your spreadsheet programm happy </div>
-<ul>
-<li class="level2"><div class="li"> cut out pinlist 24 to 13 with a rectangular selection</div>
-</li>
-<li class="level2"><div class="li"> insert the rectangular selection below the pins 1 to 12</div>
-</li>
-<li class="level2"><div class="li"> sort the lines (xemacs can do that <img src="lib/images/smileys/icon_wink.gif" class="middle" alt=";-)" />)</div>
-</li>
-<li class="level2"><div class="li"> remove or repair the lines with the numbers 2,3,… They are not in the same line. You can easily recreate the pin numbers later</div>
-</li>
-<li class="level2"><div class="li"> replace the spaces with tabs (not really need when using OpenOffice)</div>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"> copy the modified data into the spreadsheet template somewhere beside</div>
-</li>
-</ul>
-
-</div>
-<!-- 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">
-
-<p>
- Now, move the labels into the label column and the pin numbers into the pin number column. You can use the autofill feature of your spreadsheet programm to create the pin numbers, too.
-</p>
-
-<p>
-<a href="_detail/tragesym_ooo_rearanged.html" class="media" title="tragesym:ooo_rearanged.png"><img src="_media/tragesym_ooo_rearanged.png" class="media" alt="" /></a>
-</p>
-
-<p>
-Set the type, style and position column to the most common value. You can use the autofill feature again.
-</p>
-
-<p>
-Now you want to change some fo the values. Take a look at the pin description table in the datasheet:
-</p>
-
-<p>
-<a href="_detail/tragesym_kpdf_pindescription.html" class="media" title="tragesym:kpdf_pindescription.png"><img src="_media/tragesym_kpdf_pindescription.png" class="media" alt="" /></a>
-</p>
-
-<p>
-Regarding to that table we change the following things (see result below):
-</p>
-<ul>
-<li class="level1"><div class="li"> Pin 1 is an output, we like to have a negation bubble and a negation overbar</div>
-</li>
-<li class="level1"><div class="li"> A1 to A3 are inputs, we change the type and move them to the left side</div>
-</li>
-<li class="level1"><div class="li"> set the SCL type to input and move SCL and SDA to the left side, too </div>
-</li>
-<li class="level1"><div class="li"> change the type of the power pins VSS and VDD and add net names. We use the more usual GND and Vcc.</div>
-</li>
-</ul>
-
-<p>
- <strong>Note:</strong> If one of your pin labels has a backslash â??\â?? inside, you have to replace it with itâ??s escape sequence â??\\â??.
-</p>
-
-<p>
-<a href="_detail/tragesym_ooo_changedpins.html" class="media" title="tragesym:ooo_changedpins.png"><img src="_media/tragesym_ooo_changedpins.png" class="media" alt="" /></a>
-</p>
-
-<p>
-Before going on set the attributes and the options to appropriate values.
-</p>
-
-<p>
-<a href="_detail/tragesym_ooo_attributes.html" class="media" title="tragesym:ooo_attributes.png"><img src="_media/tragesym_ooo_attributes.png" class="media" alt="" /></a>
-</p>
-
-</div>
-<!-- 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">
-
-<p>
- You can either use the export function of your spreadsheet programm to create a tab seperated textfile or just select the table and copy the content into your text editor and save the file.
-</p>
-
-</div>
-<!-- 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">
-
-<p>
-Use a shell and execute tragesym:
-</p>
-
-<p>
-<code>werner@werner-amd64:~/Desktop/tragesym_tutorial> tragesym pca555.src pca555.sch</code>
-</p>
-
-<p>
-If tragesym says that thereâ??s an error, just make some changes in the spreadsheet and export the file again, or just edit the exported file.
-</p>
-
-</div>
-<!-- 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">
-
-<p>
- Now open the generated symbol with gschem and check the result
-</p>
-
-<p>
-<code>werner@werner-amd64:~/Desktop/tragesym_tutorial> gschem pca555.sch</code>
-</p>
-
-<p>
-Enabling the hidden text (â??enâ??, Edit→Show/Hide Inv Text), you can see the whole generated symbol. Itâ??s not really necessary to change anything, but it might improve the look of the symbol if you rearange the pins a little bit.
-</p>
-
-<p>
-<a href="_detail/tragesym_gschem_showhidden.html" class="media" title="tragesym:gschem_showhidden.png"><img src="_media/tragesym_gschem_showhidden.png" class="media" alt="" /></a> <a href="_detail/tragesym_gschem_finished.html" class="media" title="tragesym:gschem_finished.png"><img src="_media/tragesym_gschem_finished.png" class="media" alt="" /></a>
-</p>
-
-<p>
-Now we have a complete symbol. You can copy the symbol to your local symbol library e.g. /usr/local/share/gEDA/sym/local/ and use it.
-</p>
-
-</div>
-<!-- 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">
-
-<p>
-This was a simple example with a small pincount, but this method really pays off when you have high pin counts (ie, bga-272, tfqp-100, etc).
-</p>
-
-</div>
-<!-- SECTION "Conclusion" [6261-6425] -->
-<h2><a name="credits" id="credits">Credits</a></h2>
-<div class="level2">
-
-<p>
-Many thanks to <Russ.Dill(AT)asu.edu>, who wrote the first version of this tutorial. You can find that tutorial at <a href="http://www.geda.seul.org/docs/current/tutorials/tragesym/tragesym.html"; class="urlextern" title="http://www.geda.seul.org/docs/current/tutorials/tragesym/tragesym.html"; rel="nofollow">http://www.geda.seul.org/docs/current/tutorials/tragesym/tragesym.html</a>
-</p>
-
-</div>
-<!-- SECTION "Credits" [6426-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/geda_transistor_guide.html b/docs/wiki/geda_transistor_guide.html
deleted file mode 100644
index e2dccd7..0000000
--- a/docs/wiki/geda_transistor_guide.html
+++ /dev/null
@@ -1,139 +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>geda:transistor_guide</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<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/"; />
-<link rel="contents" href="http://geda.seul.org/wiki/geda: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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:transistor_guide"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda: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></li>
-<li class="level2"><div class="li"><span class="li"><a href="#special_cases" class="toc">Special Cases</a></span></div></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-2551] -->
-<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/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" [2552-6414] -->
-<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" [6415-7541] -->
-<h2><a name="special_cases" id="special_cases">Special Cases</a></h2>
-<div class="level2">
-<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" [7542-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/geda_ubuntu.html b/docs/wiki/geda_ubuntu.html
deleted file mode 100644
index 0663520..0000000
--- a/docs/wiki/geda_ubuntu.html
+++ /dev/null
@@ -1,47 +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>geda:ubuntu</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="keywords" content="geda,ubuntu" />
-<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/geda:ubuntu?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:ubuntu"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:ubuntu"; />
-<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">
-
-<p>
- <strong>Ubuntu Install Notes</strong>
-</p>
-
-<p>
-Basic Stable Installation: Use apt-get or synaptic to install a stable version from Debian repositories. (easy). Alternately download a binary .deb from Debian (thanks to Hamish) and you can just sudo dpkg -i <pcb-version.deb>.
-</p>
-
-<p>
-Build Installation: Ubuntu doesnâ??t include everything you need to compile software yourself. Youâ??ll want to install the â??build-essentialâ?? package using apt-get or synaptic to get the basic toolchain working on your machine. (Things like GCC are not inc. in Ubuntu). For a testing maturity level for PCB or geda, build-essential should be all you need.
-</p>
-
-<p>
-Be careful as synaptic can do extreme damage to your system. Do be fooled into replacing libc6 because synaptic will want to remove all applications that depend on it – meaning your entire system.
-</p>
-
-<p>
-<acronym title="Concurrent Versions System">CVS</acronym> Installation: For the <acronym title="Concurrent Versions System">CVS</acronym> version of PCB under Edgy, your ./configure step will require running with switch –enable-maintainer-mode. (more notes needed)
-</p>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_usage.html b/docs/wiki/geda_usage.html
deleted file mode 100644
index d0f6c7c..0000000
--- a/docs/wiki/geda_usage.html
+++ /dev/null
@@ -1,274 +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>geda:usage</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2008-02-02T12:19:33-0500" />
-<meta name="keywords" content="geda,usage" />
-<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/geda:usage?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:usage"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:usage"; />
-<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="#what_s_the_best_way_to_learn_to_use_geda" class="toc">What's the best way to learn to use gEDA?</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#what_does_the_design_flow_in_geda_look_like" class="toc">What does the design flow in gEDA look like?</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#what_limitations_exist_for_the_geda_tools" class="toc">What limitations exist for the gEDA tools?</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#what_local_configuration_files_are_used_for_a_project" class="toc">What local configuration files are used for a project?</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#what_are_the_names_and_locations_of_the_rc_files_used_with_geda_gaf_applications" class="toc">What are the names and locations of the RC files used with gEDA/gaf applications?</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#what_about_a_project_manager" class="toc">What about a project manager?</a></span></div></li>
-<li class="level1"><div class="li"><span class="li"><a href="#can_we_change_geda_to_use_an_xml_file_format" class="toc">Can we change gEDA to use an XML file format?</a></span></div></li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="what_s_the_best_way_to_learn_to_use_geda" id="what_s_the_best_way_to_learn_to_use_geda">What's the best way to learn to use gEDA?</a></h1>
-<div class="level1">
-
-<p>
-The first thing to do is to read and understand Bill Wilsonâ??s excellent <a href="geda_gsch2pcb_tutorial.html" class="wikilink1" title="geda:gsch2pcb_tutorial">gschem -> gsch2pcb -> PCB</a> tutorial. This should get you started.
-</p>
-
-<p>
-Also be sure to check out the other <a href="http://geda.seul.org/docs"; class="urlextern" title="http://geda.seul.org/docs"; rel="nofollow">gEDA documentation</a> available on this website.
-</p>
-
-<p>
-However, the best way to learn the gEDA Suite is to download it and try it out yourself! If you consult Bill Wilsonâ??s tutorial while trying the suite for yourself, you will become an expert in no time!
-</p>
-
-</div>
-<!-- SECTION "What's the best way to learn to use gEDA?" [1-541] -->
-<h1><a name="what_does_the_design_flow_in_geda_look_like" id="what_does_the_design_flow_in_geda_look_like">What does the design flow in gEDA look like?</a></h1>
-<div class="level1">
-
-<p>
-Here is a quick graphic for simple PCB design flow using the gEDA Suite:
-</p>
-
-<p>
-<a href="_detail/geda_design_flow.html" class="media" title="geda:design_flow.jpg"><img src="_media/geda_design_flow.jpg" class="media" title="design_flow.jpg" alt="design_flow.jpg" /></a>
-</p>
-
-<p>
-In words, the design flow for a simple PCB proceeds as follows:
-</p>
-<ol>
-<li class="level1"><div class="li"> Create your schematic using â??gschemâ??.</div>
-</li>
-<li class="level1"><div class="li"> Check your schematics with the DRC checker. Learn about it <a href="geda_faq-attribs.html" class="wikilink1" title="geda:faq-attribs">here</a>.</div>
-</li>
-<li class="level1"><div class="li"> Assign reference designators to your components using â??grenumâ?? or â??refdes_renumâ?? (or just attach them manually from within â??gschemâ??).</div>
-</li>
-<li class="level1"><div class="li"> Assign other component attributes (such as component footprints) using â??gattribâ?? (or just attach them manually using â??gschemâ??).</div>
-</li>
-<li class="level1"><div class="li"> Create a preliminary layout file and netlist using â??gsch2pcbâ??.</div>
-</li>
-<li class="level1"><div class="li"> Lay out and route your board using â??pcbâ??.</div>
-</li>
-<li class="level1"><div class="li"> Output Gerbers from within â??pcbâ?? using â??File â?? print layoutâ??, and select â??Gerber/RS274Xâ?? as the output file type.</div>
-</li>
-</ol>
-
-<p>
- If you make changes, or add to your schematic or attributes while in layout, update your board file like this:
-</p>
-<ol>
-<li class="level1"><div class="li"> Edit your schematic and/or attributes (â??gschemâ?? or â??gattribâ??).</div>
-</li>
-<li class="level1"><div class="li"> Check your schematics with the DRC checker. Learn about it <a href="geda_faq-attribs.html" class="wikilink1" title="geda:faq-attribs">here</a>.</div>
-</li>
-<li class="level1"><div class="li"> Forward annotate your changes using â??gsch2pcbâ??.</div>
-</li>
-<li class="level1"><div class="li"> From within â??pcbâ??, update your components using â??File â?? load layout data to paste bufferâ??, and then click on the drawing area to place the components.</div>
-</li>
-<li class="level1"><div class="li"> From within â??pcbâ??, update your netlist using â??File â?? load netlist fileâ??.</div>
-</li>
-</ol>
-
-<p>
- Usually, users invoke the individual tools from the command line. A project manager (â??gedaâ??) exists, but needs improvement.
-</p>
-
-</div>
-<!-- SECTION "What does the design flow in gEDA look like?" [542-2217] -->
-<h1><a name="what_limitations_exist_for_the_geda_tools" id="what_limitations_exist_for_the_geda_tools">What limitations exist for the gEDA tools?</a></h1>
-<div class="level1">
-
-<p>
-The most important thing to keep in mind about gEDAâ??s limitations is this: GEDA is an open-source software project. It has some limitations, but unlike many instances of commerical software, its limitations are not artificial, arbitrary, or driven by marketeering. That is, gEDA is neither nagware, crippleware, demoware, nor â??limited student editionâ??-ware. Any limitations to the gEDA tools exist because the programmers havenâ??t yet implemented that particular feature. Since the code is open for all to see and modify, anybody is welcome to implement a new feature or remove a limitation, and then submit their patches to the project. If you are a hacker and are interested in making a contribution to the gEDA project, consider tackling one of the limitations listed below! You will make a lot of friends, and earn international exposure!
-</p>
-<ul>
-<li class="level1"><div class="li"> Hierarchical bus support: Support for hierarchical busses doesnâ??t exist yet.</div>
-</li>
-<li class="level1"><div class="li"> Net and pin attributes in gattrib: Attaching routing attributes for nets and pins in gattrib remains TBD. (Net attributes are useful for high-speed design. For example, itâ??s often important that all tracks in a bus have the same electrical length. Unfortunately, itâ??s not clear that PCB will support these routing attributes right now.)</div>
-</li>
-<li class="level1"><div class="li"> Backannotation from PCB to gschem. Support for pinswapping and modification of the design file in pcb with subsequent backanno to gschem is TBD.</div>
-</li>
-<li class="level1"><div class="li"> The project manager â??gedaâ?? is out of date, and needs an update.</div>
-</li>
-<li class="level1"><div class="li"> Layer count in PCB: Currently, the layer count in PCB is limited to 16 layers plus two silk layers by default. This is more than adequate for small- and mid-sized projects. If necessary, the number of layers can be increased arbitrarily at compile time. </div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "What limitations exist for the gEDA tools?" [2218-4033] -->
-<h1><a name="what_local_configuration_files_are_used_for_a_project" id="what_local_configuration_files_are_used_for_a_project">What local configuration files are used for a project?</a></h1>
-<div class="level1">
-
-<p>
-A typical PCB design requires the following config files in your local directory:
-</p>
-<ul>
-<li class="level1"><div class="li"> gafrc: This holds configuration info for the gEDA/gaf programs (i.e. gschem, gattrib, gnetlist, etc.). It should hold pointers to your local symbol directory (if any).</div>
-</li>
-<li class="level1"><div class="li"> attribs: If you use â??gnetlist -g bom2â?? to create a project BOM, then you need this file in order to specify which attributes are written into the BOM.</div>
-</li>
-<li class="level1"><div class="li"> projectrc: When going to layout, â??gsch2pcb projectrcâ?? is a convenient way to specify paths to local footprint directories, as well as hold other configuration information for â??gsch2pcbâ??. Note that this file may have any name you choose; I like to use projectrc since its name is suggestive of its function.</div>
-</li>
-</ul>
-
-<p>
- Further detailed information about each configuration file is provided in the <a href="http://geda.seul.org/docs/index.html"; class="urlextern" title="http://geda.seul.org/docs/index.html"; rel="nofollow">documentation</a> for each facility.
-</p>
-
-</div>
-<!-- SECTION "What local configuration files are used for a project?" [4034-4990] -->
-<h1><a name="what_are_the_names_and_locations_of_the_rc_files_used_with_geda_gaf_applications" id="what_are_the_names_and_locations_of_the_rc_files_used_with_geda_gaf_applications">What are the names and locations of the RC files used with gEDA/gaf applications?</a></h1>
-<div class="level1">
-
-<p>
-The various gEDA/gaf applications (gschem, gattrib, gnetlist, etc.) use a set of RC files to set various configurable options in the tools themselves. These RC files are read in by each application upon start-up. Philosophically, there are three places where a gEDA/gaf application looks for RC files:
-</p>
-<ul>
-<li class="level1"><div class="li"> In the system installation directory: <strong><code>${prefix}/share/gEDA/</code></strong>. This location holds RC files which are global to the entire system, and are common to all users. These RC files must be found and successfully loaded for the gEDA application to work properly. <strong><code>${prefix}</code></strong> is set to the path where you installed gEDA/gaf.</div>
-</li>
-<li class="level1"><div class="li"> In the userâ??s home directory: <strong><code>$HOME/.gEDA/</code></strong>. This location holds RC files which apply to all of this userâ??s projects. <strong><code>.gEDA</code></strong> is a directory. These files are optional. Do not just place a copy of the system-gschemrc (or whatever) into this directory; this will not work properly. The right thing to do is to override specific things you want to change.</div>
-</li>
-<li class="level1"><div class="li"> In the local project directory. This location holds RC files which apply to the local project (which also lives in this directory). These RC files provide specific overrides, such as component or source libraries. This file is also optional. Do not just place a copy of the system-gschemrc (or whatever) into this directory; this will not work properly.</div>
-</li>
-</ul>
-
-<p>
- The RC file system has evolved over time. Originally, each gEDA/gaf application used its own RC file (for example, gschem used gschemrc, gnetlist used gnetlistrc, and so on). However, as the number of gEDA/gaf applications grew, it became clear that the individual RC files held a lot of redundant information, and that new users were confused by all the different RC files. Therefore, the different RC files were consolidated into a single file, called â??gafrcâ??. However, because gschem needs all kind of special customizations, we decided to keep the system gschemrc in addition to all the gafrc files. Also, in order to preserve backwards compatibility, the old RC file system is still maintained in the system directory. Accordingly, the current RC file configuration looks like this:
-</p>
-<ul>
-<li class="level1"><div class="li"> In the system installation directory:</div>
-<ul>
-<li class="level2"><div class="li"> <strong><code>system-gafrc</code></strong> â?? This contains most of the global gaf settings.</div>
-</li>
-<li class="level2"><div class="li"> <strong><code>system-gattribrc</code></strong></div>
-</li>
-<li class="level2"><div class="li"> <strong><code>system-gnetlistrc</code></strong></div>
-</li>
-<li class="level2"><div class="li"> <strong><code>system-gschemrc</code></strong> â?? This contains lots of settings specific to gschem</div>
-</li>
-<li class="level2"><div class="li"> <strong><code>system-gschlasrc</code></strong></div>
-</li>
-<li class="level2"><div class="li"> <strong><code>system-gsymcheckrc</code></strong></div>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"> In the userâ??s <strong><code>${HOME}</code></strong> directory:</div>
-<ul>
-<li class="level2"><div class="li"> <strong><code>.gEDA/gafrc</code></strong></div>
-</li>
-</ul>
-</li>
-<li class="level1"><div class="li"> In the local project directory:</div>
-<ul>
-<li class="level2"><div class="li"> <strong><code>gafrc</code></strong> â?? This should contain your local overrides, such as pointers to locally defined symbols.</div>
-</li>
-</ul>
-</li>
-</ul>
-
-<p>
- Also loaded by the system-gschemrc is the gschem-darkbg or gschem-lightbg color definitions.
-</p>
-
-<p>
-Finally, note that gEDA/gaf applications will look for up to six configuration files upon startup:
-</p>
-<ol>
-<li class="level1"><div class="li"> <strong><code>system-gafrc</code></strong></div>
-</li>
-<li class="level1"><div class="li"> <strong><code>system-gschemrc</code></strong> (or whatever)</div>
-</li>
-<li class="level1"><div class="li"> <strong><code>${HOME}/.gEDA/gafrc</code></strong></div>
-</li>
-<li class="level1"><div class="li"> <strong><code>${HOME}/.gEDA/gschemrc</code></strong> (or whatever)</div>
-</li>
-<li class="level1"><div class="li"> <strong><code>./gafrc</code></strong></div>
-</li>
-<li class="level1"><div class="li"> <strong><code>./gschemrc</code></strong> (or whatever)</div>
-</li>
-</ol>
-
-<p>
- If you get a warning that your app canâ??t find one or another of these files, donâ??t worry. Most of them are optional. The only required files are the system RC files.
-</p>
-
-</div>
-<!-- SECTION "What are the names and locations of the RC files used with gEDA/gaf applications?" [4991-8369] -->
-<h1><a name="what_about_a_project_manager" id="what_about_a_project_manager">What about a project manager?</a></h1>
-<div class="level1">
-
-<p>
-The individual components in the gEDA design suite do not have the concept of an end-to-end project. Rather, they deal with their own files (e.g. â??gschemâ?? â?? .sch, â??pcbâ?? â?? .pcb). However, there is a project manager, called â??gedaâ??, which you can invoke from the command line. Itâ??s goal is to help manage your design as a whole as you take it from concept, through schematic capture, attribute attachment, layout, BOM generation, and so on.
-</p>
-
-<p>
-Unfortunately, development of â??gedaâ?? has not kept up with the rest of gEDA/gaf. In particular, â??gedaâ?? does not use the latest tools or methods to accomplish the individual design tasks. Therefore, we recommend that user simply invoke the individual tools (e.g. gschem, gattrib, gnetlist, gsch2pcb, etc) from the command line. Meanwhile, if your are a hacker are looking for a smallish project to adopt, polishing up â??gedaâ?? would make a nice introduction to the gEDA Suite, and you would make a lot of friends by doing so!
-</p>
-
-</div>
-<!-- SECTION "What about a project manager?" [8370-9405] -->
-<h1><a name="can_we_change_geda_to_use_an_xml_file_format" id="can_we_change_geda_to_use_an_xml_file_format">Can we change gEDA to use an XML file format?</a></h1>
-<div class="level1">
-
-<p>
-We have a recurrent debate about <acronym title="Extensible Markup Language">XML</acronym> file formats on geda-user every two or three years. I think it has to do with how long it takes us to lose our institutional memory due to churn on the mailing list.
-</p>
-
-<p>
-Itâ??s unlikely the gEDA Project will ever switch to an <acronym title="Extensible Markup Language">XML</acronym> file format for schematics or symbols, so get used to it. Some reasons against <acronym title="Extensible Markup Language">XML</acronym> are:
-</p>
-<ol>
-<li class="level1"><div class="li"> GEDA/gaf already has a fixed, well documented, <acronym title="American Standard Code for Information Interchange">ASCII</acronym> file format. Itâ??s over 8 years old as of 2007. Itâ??s well used and well tested.</div>
-</li>
-<li class="level1"><div class="li"> We already have a parser for our file format. Itâ??s lightweight & thoroughly debugged.</div>
-</li>
-<li class="level1"><div class="li"> There are lots of legacy designs using the file format out there already. People would scream if we switched file formats since their old designs would become obsolete. And supporting two file formats – old and new – would be a major <acronym title="Pain in the Ass">PITA</acronym>.</div>
-</li>
-<li class="level1"><div class="li"> <acronym title="Extensible Markup Language">XML</acronym> is a generalized file format. Therefore, <acronym title="Extensible Markup Language">XML</acronym> files tend to become bloated pigs. The gEDA file format is light & well adapted to its purpose: representing graphical information pertainent to schematic diagrams in electronics.</div>
-</li>
-<li class="level1"><div class="li"> One purported benefit for <acronym title="Extensible Markup Language">XML</acronym> files is that there are lots of open-source parsers for them available, making integration into libgeda trivial. Thatâ??s the theory, but in reality the job of a parser is to analyze and parse the input, and then stick it into datastructures suitable for use with the rest of gschemâ??s code. An open-source parser does about 1/3 of the job we need (i.e. reading & analyzing the file, and creating some kind of parse tree). The rest of the job involves putting the stuff in the parse tree into libgedaâ??s data structures. Thatâ??s lots of work. Therefore, the purported advantage of the freely-available <acronym title="Extensible Markup Language">XML</acronym> parser is a chimera. Yes, <acronym title="Extensible Markup Language">XML</acronym> may be of interest for a new program written from the ground up, but not for an existing program like gEDA.</div>
-</li>
-<li class="level1"><div class="li"> GEDA developer time is better used on implementing new features like backannotation. Using developer time on porting our file format to <acronym title="Extensible Markup Language">XML</acronym> is a sideways move which doesnâ??t provide the end user any more utility, but soaks up valuable developer time.</div>
-</li>
-<li class="level1"><div class="li"> The other benefit of <acronym title="Extensible Markup Language">XML</acronym> is that it is more-or-less human readable. Iâ??ll grant that this is a valid assertion. Our current file format is not readable by a human who has never read the documentation. However, our current file format *is* <acronym title="American Standard Code for Information Interchange">ASCII</acronym>, and is completely documented, so an essential reason for readability – the ability to write scripts against the file – is already taken care of. Also, a human can certainly read the file format once he has taken the time to <acronym title="Read The Fine Manual">RTFM</acronym>. Human readability – without knowing the file format – is a â??nice to haveâ?? which isnâ??t high on my priority list.</div>
-</li>
-</ol>
-
-</div>
-<!-- SECTION "Can we change gEDA to use an XML file format?" [9406-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/geda_vams_netlister_readme.html b/docs/wiki/geda_vams_netlister_readme.html
deleted file mode 100644
index 5da308c..0000000
--- a/docs/wiki/geda_vams_netlister_readme.html
+++ /dev/null
@@ -1,699 +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>geda:vams_netlister_readme</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="geda,vams_netlister_readme" />
-<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/geda:vams_netlister_readme?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:vams_netlister_readme"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:vams_netlister_readme"; />
-<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="#vams_netlister_readme" class="toc">VAMS netlister README</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#vams_netlister" class="toc">VAMS netlister</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#vams_netlister_syntax_architecture" class="toc">VAMS netlister syntax architecture</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#vams_netlister_syntax_entity" class="toc">VAMS netlister syntax entity</a></span></div></li></ul>
-</li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="vams_netlister_readme" id="vams_netlister_readme">VAMS netlister README</a></h1>
-<div class="level1">
-
-</div>
-<!-- SECTION "VAMS netlister README" [1-36] -->
-<h2><a name="vams_netlister" id="vams_netlister">VAMS netlister</a></h2>
-<div class="level2">
-<pre class="code">date: 10 october 2000
-gEDA: gnetlist vams mode
-first unrevised vams mode documentation
-
-
-Written by: Martin Lehmann
--------------------------------------------------------------------------
-
-
-VHDL-AMS support for the gEDA gnetlist tool
--------------------------------------------
-
-CONTENT:
-
- 1. functionality
- 1. ARCHITECTURE generation
- 2. ENTITY generation
- 3. automatisate gnetlist calls
-
- 2. implementation
- 1. the vams mode of gEDA gnetlist
- 1. scheme
- 1. settings and new definition
- 2. gnet-vams.scm
- 1. routines main structure
- 3. helpfully setting in gEDA gschem environment
-
- 2. new c-code
- 1. routines
- 2. code-adaptation
-
- 2. automatic generating gnetlist calls in gEDA gschem
- 1. generated gEDA gnetlist calls
- 2. scheme
- 1. generate_netlist.scm
- 2. settings
-
- 3. new c-code
- 1. routines
- 2. code-adaptation
-
-
- The purpose of our endevour, is that gEDA gnelist completly
- supportted VHDL-AMS (VHDL Analog and Mixed-Signal) netlist
- generation.
-
- The VHDL-AMS netlist support mode is called vams.
-
-
- 1. FUNCTIONALITY
-
- gEDA gnetlist in vams mode allow it to generate a VHDL-AMS
- ARCHITECTURE or an ENTIY declaration. Which of both tasks is
- performed, dependends on the generate-mode variable. This variable
- is defined in the gnetlist command or will be set default.
-
- If generate-mode=1 (default) gnetlist creates a netlist as an
- VHDL-AMS ARCHITECTURE of the current schematic. Otherwise
- (generate-mode=2), it creates an VHDL-AMS ENTITY declaration of the
- selected component (this task needs information from gEDA gschem,
- see below).
-
- Now follows a stepwise discription of the program run in both
- submodes.
-
- We presuppose that you are familiar with the structure of gEDA
- gnetlist usage (otherwise try gnetlist -help) and that you have
- ever seen an VHDL-AMS ARCHITECTURE with its belonging ENTITY. If
- you does not then the following distription will be seems very
- strange to you. Maybe the syntax files (syntax_entity.txt,
- syntax_architeture.txt) can helps you further.
-
- ==================================================================
-
- 1.1. ARCHITECTURE GENERATION
-
-
- We suppose generate-mode is equal to 1, from this it follows that
- vams creates a netlist as an ARCHITECTURE (saved to
- <value-of-toplevel-attribute-entity>_arc.<output-fileextension>).
-
-
- ARCHITECTURE <architecture-identifier> OF <entity-identifier> IS
-
- The architecture-identifier we are getting from the toplevel
- attribute architecture, which we have introduced. If it is not
- defined, we are setting architecture-identifier default
- (default_architecture). The same have we doing with the
- entity-identifier (toplevel attribute entity, default_entity).
-
-
- {<subnet-object> <subnet-name> : subnet-kind;}
-
- In the signal declaration part all subnets of the schematic will be
- declarated. A subnet declaration consists of an net-object, a
- net-name and a net-kind. All subnets are connected to various
- components pins. If this pins have all the same port-object and the
- same port-kind it is ok, but if one of them different, the net is
- faulty, and will be not declarated. Moreover, if the subnet-object
- a quantity, then it will be checked, whether the subnet consists
- exactly one output pin (port-mode), else the subnet is faulty too.
- The three net attributes (object, kind, mode) we are getting from
- the pin attribs, port_kind, port_object and port_mode (which we
- have introduced newly) of a component pin.
-
-
- BEGIN
-
- Ok. it's only marks the start of the architecture body.
-
-
- {<label> : ENTITY <entity> [(<architecture>)]
- [GENERIC MAP (<set generic> => <generic-value>
- {; <set-generic=> <generic-value>})]
- PORT MAP ( <pin-name> => <subnet-name>{; <.. => ..>});}
-
- We only support component instantiation statements, like this
- above, because we generate simple VHDL-AMS netlists. The label of
- an instance is defined from the uref of the instanciated
- component. Watch out, this label must be unique,it is not checked
- anywhere. The entity variable is not the same as the
- entity-identifier, it is the value of the device attribute which on
- its part identifies the precompiled ENTITY of this special
- component. Similar is the architecture variable belonging to the
- instanciated components ARCHITECTURE (note: one ENTITY can have more
- ARCHITECTURES), hence we are getting it from the component
- attribute ARCHITECTURE (newly introduced).
-
- All generics of the generic-list are component parameters, which
- are different from its default values (set in its ENTITY
- declaration). How can we distinguish them? All defined generics
- are attached to the component and looks like :
-
- <attribute-name>=?<default-value> <- default, not in
- generic-list
-
- And if you want to change a parameter, you only must delete the
- ?-character and replace the default-value with your wanted value,
- like this :
-
- <attribute-name>=<new-value> <- element of generic list
-
- If you do it this way, the new assigned value and its attribute-name
- will be appear in the GENERIC MAP (set-generic=attribute-name and
- generic-value=new-value).
-
- The PORT MAP consists of all pins of a component and which nets
- them connected to. The pin-name is getting from the pin# attribute
- of the pin and the subnet-name means the value of the label
- attribute of a net (mostly default named), which the pin is
- connected to. If the pin directly wired to a PORT component (=
- component, which device attribute =PORT), then we assign the uref
- of this component to subnet-name.
-
-
- END ARCHITECTURE <architecture-identifier>;
-
- I think, this line needs no more explanation. The
- architecture-identifier is the same like in the first line of
- ARCHITECTURE declaration. Hence, the ARCHITECTURE part ends here.
-
- ==================================================================
-
- 1.2. ENTITY GENERATION
-
-
- Now, we suppose generate-mode is equal to 2, from this it follows
- that vams creates an ENTITY declaration of a component (save to
- <component-device>.vhdl). If there no component selected (empty
- top-attribs list) then it will be created an toplevel ENTITY of the
- current schematic (save to
- <value-of-toplevel-attribute-entity>.vhdl).
-
-
- LIBRARY <library-identifier>{,<library-identifier>};
- USE <package-identidier>{,<package-identifier>};
-
- Well, the context clause part is not very ingenious. All libraries
- and packages you needs for your simulation you must insert staticly
- (a library contents precompiled ENTITIES, ARCHITECTURES and
- PACKAGES, which are needed from base components [base of the
- hierachical netlist] of your schematic. a package contents
- predefined types, constants, ...). We are searching for a better
- usability of this part.
-
-
- ENTITY <entity-identifier> IS
- [genric_clause]
- [port_clause]
- END ENTITY;
-
- If you want generate a toplevel ENTITY of your current schematic
- then the entity-identifier is defined from the toplevel attribute
- entity of the schematic-file. Moreover, there are no generic_clause
- and no port_clause.
-
- In case of an component based ENTITY declaration, the
- entity-identifier is getting from the device attribute of the
- selected component (this attribute is included in top-attribs list,
- which is defined in the automatic generated gnetlist command .. more
- about this, later).
-
-
- generic_clause :=
- GENERIC ( <generic-identifier> : REAL := <default-value>
- {;<generic-identifier> : REAL := <default-value>});
-
- All needed generic-identifiers and it default-values are getting
- from the top-attribs list. Note: all attached attributes of a
- component appears in the generic_clause, only special attributes,
- like uref, source and architecture, are taked out. The values of
- this attributes are taked from the top-attribs list, too, but it
- does not matter whether the value starts with a ?-character or not
- (?-character always will be deleted, if it exist in front of a
- value).
-
-
- port_clause :=
- PORT (<port-kind> <port-identifier> : [<port-mode>] <port-type>
- {;<port-kind> <port-identifier> : [<port-mode>] <port-type>});
-
- All variables of this clause are grabbed from the symbol of the
- selected component. Port-kind corresponds with the value of the
- port_kind attribute of the pin, which pin# attribute value is equal
- to port-identifier. Just as corresponds port-type with the the
- value of the pin attribute port_type and port-mode with the value
- of port_mode.
-
- ===================================================================
-
- 1.3. AUTOMATISATING gnetlist CALLS
-
- Because it is very arduous to type the whole gnetlist command,
- which all its parameters, per hand into the terminal, we are
- implement an automatisation of this process in gEDA gschem. This
- makes it possible to create a VHDL-AMS ARCHITECTURE or ENTITY
- whitout any commandline actions. The only thing you must do, is to
- use one of the following hotkeys:
-
- <g e> for generating an ENTITY
- <g n> for genarating an ARCHITECTURE.
-
- NOTE to <g e> - hotkey : If one component of the schematic
- selected then the ENTITY generation
- will be applied to this component !!
-
- ===================================================================
-
- 2. IMPLEMENTATION
-
- At this section it will be explained the basic concept of the
- implementation, which is splited in two sections. The first one
- aimed to the gnelist implementation and the second to the gschem
- implementation.
-
-
- 2.1. THE VAMS MODE OF gEDA gnetlist
-
- To realize gnetlist VHDL-AMS support, it was necessary to create
- new scheme and c stuff.
-
-
- 2.1.1. SCHEME
-
- The scheme implementation contents two parts. On one hand the new
- file gnet-vams.scm, which realize the VHDL-AMS-code generation, and
- on the other hand some settings in rc-files.
-
-
- 2.1.1.1. SETTINGS AND NEW DEFINITIONS
-
- The following lines insert in your gschemrc, or wherever you want,
- but it must be loaded at gnetlist startup.
-
- - load two modules, which we needs in our new implementation.
-
- (define-module (ice-9 ls) :use-module (ice-9 common-list)
- :use-module (ice-9 string-fun))
-
- - load main file for VHDL-AMS support, which contents the
- startup procedure vams.
-
- (load "<path_of_gnet-vams.scm>/gnet-vams.scm")
-
-
- 2.1.1.2. gnet-vams.scm
-
- This file contents all necessary scheme-functions to generate
- VHDL-AMS-code. Especially, the main procedure vams, which can be
- execute from the gnetlist command.
-
- For example :
-
- gnetlist -g vams schematic_filename.sch
-
- ...
-
-
- 2.1.2.1. ROUTINES MAIN STRUCTURE
-
- the mainly functions structure looks like:
-
- - (vams output-filename)
-
- ARCHITECTURE generation
-
- - (vams:write-secondary-unit architecture entity output-port)
-
- - (vams:write-architecture-declarative-part output-port)
- - (vams:write-signal-declarations output-port)
-
- - (vams:write-architecture-statement-part packages output-port)
- - (vams:write-generic-map output-port package)
- - (vams:write-port-map package output-port)
-
- ENTITY declaraction
-
- - (vams:write-primary-unit entity port-list generic-list output-port)
-
- - (vams:write-context-clause output-port)
-
- - (vams:write-generic-clause generic-list output-port)
- - (vams:write-generic-list generic-list output-port)
-
- - (vams:write-port-clause port-list output-port)
- - (vams:write-port-list port-list output-port)
-
-
- 2.1.1.3 HELPFULLY SETTING IN THE gEDA gschem ENVIRONMENT
-
- This settings are not absolutly necessary, but they makes work
- easier.
-
- - set in .gEDA/gschemrc or wherever you want, but place it
- right.
-
- (attribute-promotion "enable")
- (promote-invisible "enable")
- (enforce-hierarchy "disabled")
-
- (attribute-name "port_object")
- (attribute-name "port_type")
- (attribute-name "port_mode")
- (attribute-name "entity")
- (attribute-name "architecture")
-
-
- 2.1.2. NEW C - CODE
-
- To got all informations, which we needed for currently netlist
- generation, we must implemented two new c - functions.
-
-
- 2.1.2.1 NEW ROUTINES (saved in vams_misc.c)
-
-
- SCM vams_get_package_attributes(SCM scm_uref)
-
- The first function gets all attribute names (not its values) of a
- component. This routine requires the name a component (package),
- especially the uref of it, and returns a list of all attribute
- names which are attached to this package.
-
- We needs this functionality to produce a currectly
- VHDL-AMS GENERIC MAP.
-
-
- char* vams_get_attribs_list
- (OBJECT *object, SCM *list, OBJECT **return_found)
-
- It exists only for the support of the first function.
-
-
- 2.1.2.2. CODE ADAPTATION
-
- To place this new functions at gnetlist scheme's disposal, you must
- perform the following actions.
-
- (1) gnetlist/src/g_register.c
-
- gh_new_procedure1_0
- ("gnetlist:vams-get-package-attributes",
- vams_get_package_attributes);
-
-
- (2) gnetlist/include/prototype.h
-
- SCM vams_get_package_attributes(SCM scm_uref);
-
-
- (3) edit gnetlist/src/Makefile.in or directly in Makefile
-
- (if you have edited Makefile.in you must run make config of
- course)
-
- - add "vams_misc.c" to gnetlist_SOURCES - variable
- - add "vams_misc.o" to gnetlist_OBJECTS - variable
-
- (4) copy vams_misc.c to gEDA/gnetlist/src/
-
- (5) compile your code newly
-
- ===================================================================
-
- 2.2. AUTOMATIC GENERATING gnetlist CALLS IN gEDA gschem
-
- To realize this new feature it was necessary to put more
- information from the schematic to the scheme world of gEDA gschem.
- Concretly, we needs the filename of the current schematic, because
- gEDA gnetlist required it, and the attached attributes of a
- selected component for creating an VHDL-AMS ENTITY. Hence, the
- gnetlist command is mutated to an unidirectional interface between
- the world of gschem scheme and the world of gnetlist scheme.
-
- There are three important things, which transfer through this
- interface:
-
- (1) the source-file, which contents the complett filename
- (with path) of the current schematic.
-
- (2) the top-attribs list, which contents all attached
- attributes of the selected component.
-
- (3) the generate-mode, which is defined by the users actions.
-
-
- 2.2.1. STRUCTURE OF gEDA gnetlist CALLS FROM COMMANDLINE OR FROM gEDA
- gschem.
-
- typical commandline call :
-
- gnetlist [-o <output-filename>]
- -g vams
- <schematic-file>
-
- There are nothing to explain. The top-attribs list and the
- generate-mode variable are default defined ('() and 1).
-
-
- calls from gEDA gschem (3 possible variations) :
-
-
- Note: vhdl-path is a predefined variable, which is set in
- generate_netlist.scm first times. You can it simple redefine
- in your local gschemrc file, which is loading everytimes you
- starts gEDA gschem.
-
-
- (1) hot-key-stroke: - g n (generate netlist)
-
- --> generates a netlist of the current schematic.
-
-
- gnetlist -o <vhdl-path>/<target-file>
- -g vams
- <source-file>
-
- The source-file variable is equate to the complett
- path+filename of the current schematic, which we get with
- help of a self coded c function. If you cut out the filename
- of the source-file variable (source-file without path) then
- you are getting the target-file.generate-mode and
- top-attribs are default again.
-
- (2) hot-key-stroke: - g e (generate-entity)
- and no component is selected.
-
- --> generates an toplevel ENTITY of the current
- schematic.
-
-
- gnetlist -c <scheme-comm>
- -o <vhdl-path>/<target-file>
- -g vams
- <source-file>
-
- scheme-comm="(define top-attribs '<top-attribs>)
- (define generate-mode '2)"
-
-
- Source-file needs no comment, because it is the same as in
- (1). To get all attributes of a selected component, we are
- must write a new c function again. The values, which we get
- from this new function are saved in top-attribs. The sense
- of the scheme-comm command is to put top-attribs and
- generate-mode from the gschem to the gnetlist environment.
- At last, the target-file consists of the pure basefilename
- of the source-file and an .vhdl extention.
-
- (3) hot-key-stroke: - g e (generate-entity)
- and only one component is selected.
-
- --> generates an ENTITY of the selected schematic.
-
-
- commandline is the same as in (2).
-
-
- Differences: The target-file is different, but it does not
- matter, because gnetlist generate an new output-filename in
- in this case (<device-name-of-selected-component>.vhdl,
- normally).But one fact is very important: the top-attribs
- variable includes all attached attributes of the selected
- component now.
-
- 2.2.2. SCHEME
-
- The gnetlist command is generating from two scheme functions, which
- are saved in generate_netlist.scm. This functions starts if the
- gschem user is typing one of the specified hot-keys ([g e] starts
- generate-entity and [g n] starts generate-netlis). Both routines
- puts the whole gnetlist command together and execute it. The syntax
- you see above.
-
-
- 2.2.2.1. generate_netlist.scm
-
-
- 2.2.2.2. SETTINGS
-
- If you want use the new feature then you must do some entries in one
- of your gEDA gschem rc-files
-
- necessary defines:
-
- - in system-gschemrc
-
- ("g" . gnetlist-keymap)
-
- Edit your global-keymap and if "g" always defined then find
- out an other free hot-key-stroke.
-
- Note: the documentation supports the "g" - key only.
-
-
- - in one of the gschem startup files
-
- (define gnetlist-keymap
- '(("n" . generate-netlist)
- ("e" . generate-entity)))
-
-
- loads :
-
- (load "/home/fliser3/.gEDA/generate_netlist.scm")
-
-
- 2.2.3. NEW C-CODE
-
- The c-code makes it possible to get directly informations from the
- gschem tool, which is necessary for the online execution of
- gnetlist.
-
-
- 2.2.3.1. ROUTINES
-
- It exists two new c-functions. Both are put down in
- misc_for_gnetlist.c.
-
-
- SCM get_selected_filename(gpointer data,
- guint callback_action,
- GtkWidget *widget)
-
- This function returns the whole filename of the current schematic,
- which is picked from the w_current->page_current->page_filename
- string.
-
-
- SCM get_selected_component_attributes(gpointer data,
- guint callback_action,
- GtkWidget *widget)
-
- How the name is saying, this functions returns all attributes of
- the selected component. It is realized with a simple while loop
- over all objects of the schematic, which picked out all elements
- where the selected flag is set.
-
-
- 2.2.3.2. CODE-ADAPTATION
-
- Here are some actions you must conclude to makes the software
- runable.
-
- (1) new lines in /gschem/src/g_register.c
-
- gh_new_procedure0_0 ("get-selected-filename",g_get_selected_filename);
-
-
- (2) new lines in /gschem/include/prototype.h
-
- SCM g_get_selected_filename();
-
-
- (3) copy the file misc_for_gnetlist.c to gschem/src
-
- (4) add in file /gschem/src/Makefile.in or directly in Makefile.
-
- (if you have edited Makefile.in you must run make config of
- course)
-
- - add "misc_for_gnetlist.c" to gschem_SOURCES - variable
- - add "misc_for_gnetlist.o" to gschem_OBJECTS - variable
-
- (5) add new lines in /gschem/src/g_key.c
-
- SCM g_get_selected_filename(void)
- {
- return (get_selected_filename(window_current, 0, NULL));
- }
-
-
- (6) compile your changed c-code newly
-</pre>
-
-</div>
-<!-- SECTION "VAMS netlister" [37-20220] -->
-<h2><a name="vams_netlister_syntax_architecture" id="vams_netlister_syntax_architecture">VAMS netlister syntax architecture</a></h2>
-<div class="level2">
-<pre class="code">ARCHITECTURE <architecture-identifier> OF <entity-identifier> IS
-
- {<subnet-object> <subnet-name> : subnet-kind;}
-
-BEGIN
-
- {<label> : ENTITY <entity> [(<architecture>)]
- [GENERIC MAP (<set-generic> => <generic-value>
- {; <set-generic=> <generic-value>})]
- PORT MAP ( <pin-name> => <subnet-name>{; <.. => ..>});}
-
-END ARCHITECTURE <architecture-identifier>;
-</pre>
-
-</div>
-<!-- SECTION "VAMS netlister syntax architecture" [20221-20667] -->
-<h2><a name="vams_netlister_syntax_entity" id="vams_netlister_syntax_entity">VAMS netlister syntax entity</a></h2>
-<div class="level2">
-<pre class="code">LIBRARY <library-identifier>{,<library-identifier>};
-USE <package-identidier>{,<package-identifier>};
-
-ENTITY <entity-identifier> IS
- [GENERIC ( <generic-identifier> : REAL := <default-value>
- {;<generic-identifier> : REAL := <default-value>}); ]
- [PORT (<port-kind> <port-identifier> : [<port-mode>] <port-type>
- {;<port-kind> <port-identifier> : [<port-mode>] <port-type>});]
-END ENTITY;
-</pre>
-
-</div>
-<!-- SECTION "VAMS netlister syntax entity" [20668-] --></div>
-</body>
-</html>
diff --git a/docs/wiki/geda_verilog_netlister_readme.html b/docs/wiki/geda_verilog_netlister_readme.html
deleted file mode 100644
index 206114b..0000000
--- a/docs/wiki/geda_verilog_netlister_readme.html
+++ /dev/null
@@ -1,453 +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>geda:verilog_netlister_readme</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="geda,verilog_netlister_readme" />
-<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/geda:verilog_netlister_readme?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:verilog_netlister_readme"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:verilog_netlister_readme"; />
-<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">
-
-
-
-<h1><a name="verilog_netlister_readme" id="verilog_netlister_readme">Verilog netlister README</a></h1>
-<div class="level1">
-<pre class="code">Verilog netlister readme.
-
-THIS IS FREE SOFTWARE, see the included file COPYING for more info.
-
-Latest README:
-
- This is the fifth release of the Verilog netlister for gEDA.
-
- New in this release:
-
- 1) Escaped Verilog identifiers.
-
- To facilitate board level simulations, the Verilog netlister now
-outputs `escaped' Verilog identifiers for any net, port or instance name
-that does not appear to be a valid Verilog identifier. In this way,
-chips with numbered pins can be netlisted and models constructed to run
-digital simulations of complete circuits.
-
-
- Mike Jarabek
-
-
------ OLDER README.verilog's -----
-
- This is the fourth release of the Verilog netlister for gEDA.
-
- New in this release:
-
- 1) Multiple width wires.
-
-How to use: (mostly taken from a previous readme... )
-
- Here's how to proceed to make a schematic that can be netlisted
-to verilog.
-
- 1) Create your modules by the standard method, keep in mind
- that you must supply a `pin#' attribute for each port
- you want to create in the generated verilog. gmk_sym is
- useful for this.
-
- 2) Place each of your newly created modules on the
- schematic. You may also place primitives from the
- `verilog' symbol library. Be sure to give a _unique_
- `uref' to every symbol you place on the schematic,
- unless two symbols are actually different parts of the
- same module, and the pins listed on each symbol do not
- have any names in common. Otherwise they will not get
- netlisted.
-
- 3) Connect nets between the modules you want. Remember, if
- you want legible Verilog later, don't forget to name all
- your nets by attaching `label' attributes to them. For
- Multiple bit wires just use standard Verilog notation.
- The netlister will figure out which bit ordering you
- want. Be sure to have at least one net labeled with the
- complete range expression, otherwise the netlister will
- guess at whether you wanted net[15:0] or net[0:15] in
- your declarations. Any inconsistent ranges will be
- reported as a warning. Strings that appear to be
- invalid Verilog identifiers will be printed with a
- warning, but otherwise ignored. (If you get a warning
- for a valid Verilog identifier, please post a bug
- report!)
-
- 4) Insert IPAD's, OPAD's, and IOPAD's for all the nets you
- want to be visible in the module declaration statement.
- It is especially important to make sure that the nets
- you hook up to the pads are named, as the net names
- could change from run to run, that's a bad thing. (I/O
- pads would be a good place to put the aformentionned
- full range expressions. Range expressions on I/O pads
- are ignored when outputting the module declaration, but
- they are used in figuring out the final bit ranges.)
- Every pad must have a unique uref, otherwise the
- netlister will get confused.
-
- 5) Add an unattached attribute `module_name=Your_Module'
- somewhere on the schematic, near the title block is
- good. This will name the generated Verilog module
- `Your_Module'.
-
- 6) Save your design.
-
- 7) Run the schematic through the netlister:
-
- gnetlist -g verilog -o output.v schematic.sch
-
- 7a) Check the output for correctness, _especially_ if you got
- any warnings. (There should be no warnings.)
-
- 8) Feed the netlist to your favorite simulator/synthesis tool.
-
-
- Mike Jarabek
-
-
- This is the third release of the Verilog netlister for geda.
-
- Fixed in this release:
-
- 1) Netlister no longer barfs if there are no
- Input/Output/InOut ports on the module.
-
- 2) Module instantiation code much improved/cleaned up, mostly
- due to g_netlist.c patch.
-
- New in this release:
-
- 1) A whole wack-load of symbols, I created a C program that
- generates n-input versions of and, nand, or, nor, xor, and
- xnor symbols
-
- 2) Modules instantiated with positional port connections.
- Just add the attribute `VERILOG_PORTS=POSITIONAL' to your
-
- symbol file as an unattached attribute, or attach it to the
- symbol on the schematic.
-
- 3) Added bufif?, notif?, not and buf symbols.
-
- 4) Added example of positional port module instantiation to
- the example schematic
-
- 5) Added 7447 example schematic
-
- Coming:
-
- 1) Module instantiation parameters. (probably by an attribute)
-
-
- Included in this tar-ball are three patch files against the
- 19990705 version of gEDA. Apply g_netlist.c.diff and
- g_register.c.diff to the files in gnetlist/src/ and
- gnetlist.scm.diff to gnetlist.scm in the gnetlist/scheme
- directory. You may have to regenerate prototype.h, or manually
- patch it. Replace the symbols in the sym/verilog directory
- with the symbols in this distribution. (I have modified all of
- the symbols to use the new unattached attribute convention for
- device et al.) (if you have applied the patch I sent to the
- mailing list that fixes netlisting a module with no ports, you
- may have trouble applying the gnetlist.scm.diff patch.) Don't
- forget to do a `make all install' after applying the patches.
-
- Once again, to netlist the example schematics to verilog type:
- (Assuming gnetlist has been patched and is properly installed.)
-
- gnetlist -g verilog -o test.v examples/sch/test.sch
-
- or
-
- gnetlist -g verilog -o 7447.v examples/sch/7447.sch
-
-
-(This README was from 19990629)
-Verilog netlister readme.
-
-THIS IS FREE SOFTWARE, see the included file COPYING for more info.
-
- This is the second release of the Verilog netlister for geda.
-
- Fixed in this release:
-
- 1) The last comma in the argument list to instantiations and
- module definitions is now suppressed
-
- 2) Better handling of `special' components has been added
-
- New in this release:
-
- 1) Continuous assignments to 1'b0 and 1'b1 can now be
- generated by connecting the `high' or `low' symbol to a
- net.
-
- Mike Jarabek
- mjarabek@xxxxxxxxxxxxxx
-
-
-
---
-
-
- This the verilog netlister for gEDA. Included in the tarball
-are several diff files against the 19990327 gEDA distribution. All of
-the patches apply to the gnetlist subirectory. You should be able to
-apply them with `patch -p1'.
-
- The netlister has its limitations: (most of these will
-eventually get fixed, I hope..)
-
- 1) Components connected by reference, (i.e. by having named
- net stubs attached to pins, but not conected by a
- continuous line) create duplicate entries in the wire
- declaration section of the verilog code.
-
- 2) Multiple width wires don't work. (Busses will help
- this)
-
- 3) There is no way to force a signal to 1,0,z,x (yet).
-
- 4) Some scheme code needs to be improved. (Mainly the
- classification code, it inserts `()' elements into the
- output lists. (I should know how to fix this in a day or
- two.. too bad I never got a scheme course before..))
-
- 5) I don't know if this will work on multiple page schematics.
-
- 6) The top level module is outputted with the same name
- every time, I don't currently think there is a way to
- get at the name of the top level schematic.
-
-
- The netlister does some neat things:
-
-
- 1) It outputs a verilog module with proper port
- declarations, outputs are declared as outputs, inputs
- are declared as inputs, and bidirectional signals are
- declared as inouts.
-
- 2) All nets that are found on the design are declared as
- wires. (This is to allow for net attributes later to
- declare wand's and such)
-
- 3) Any components placed on the schematic that are given
- uref attributes create a verilog instantiation for the
- name of the module as stored in the `device' attribute,
- the instatiated name is given as the `uref' attribute.
-
- 4) All connections into and out of instantiated modules are
- made by name, and not by order, because I can't be sure
- that the order will be right coming off the schematic.
- (anyway, that's better for the long run.)
-
- 5) A comment is inserted at the top of the module to say
- that the file was automatically generated.
-
-
-
- Here's how to proceed to make a schematic that can be netlisted
-to verilog.
-
- 1) Create your modules by the standard method, keep in mind
- that you must supply a `pin#' attribute for each port
- you want to create in the generated verilog. gmk_sym is
- useful for this (with the patch to allow ascii pin names).
-
- 2) Place each of your newly created modules on the
- schematic
-
- 3) Connect nets between the modules you want. Remember, if
- you want legible verilog later, don't forget to name all
- your nets by attaching `label' attributes to them.
-
- 4) Insert IPAD's, OPAD's, and IOPAD's for all the nets you
- want to be visible in the module declaration statement.
- It is especially important to make sure that the nets
- you hook up to the pads are named, as the net names
- could change from run to run, that's a bad thing.
-
- 5) Save your design.
-
- 6) Run the schematic through the netlister:
-
- gnetlist -g verilog -o output.v schematic.sch
-
- 6a) Edit the output file to have the right module name, and
- to remove any duplicate wires.
-
-
- There is an example schematic in the schematic directory, and a
- copy of the verilog netlist generated.
-
-The mechanics:
-
- The I/O ports for the module are detected by enumerating all of
- the nets attached to any symbol bearing the device name of `IPAD',
- `OPAD', or `IOPAD'. If you name one of your blocks with that
- name, don't be surprised if you find `extra' ports in the module
- declaration.
-
- The wires are declared by walking through the list of nets
- returned by the function that I patched into gnetlist. This is
- the source of the duplicate wire declarations. This should
- probably get fixed when `net_is_duplicate' gets set for
- connections made by reference.
-
- Module instantiations are created by enumerating the pins found on
- a symbol and connecting the nets found to the pins. If your block
- has spelling errors, then the module instantiation won't work.
- You will have to manually trace back to find the error.
-
-
- Mike Jarabek
-
-
-
------------- Below is the previous version README -------------------
-
-Verilog netlister readme.
-
-THIS IS FREE SOFTWARE, see the included file COPYING for more info.
-
-
- This the verilog netlister for gEDA. Included in the tarball
-are several diff files against the 19990327 gEDA distribution. All of
-the patches apply to the gnetlist subirectory. You should be able to
-apply them with `patch -p1'.
-
-[ editor's note, if you are reading this file in a gEDA dist, then all
- the required patching and integration is already done ]
-
- The netlister has its limitations: (most of these will
-eventually get fixed, I hope..)
-
- 1) Components connected by reference, (i.e. by having named
- net stubs attached to pins, but not conected by a
- continuous line) create duplicate entries in the wire
- declaration section of the verilog code.
-
- 2) Multiple width wires don't work. (Busses will help
- this)
-
- 3) There is no way to force a signal to 1,0,z,x (yet).
-
- 4) Some scheme code needs to be improved. (Mainly the
- classification code, it inserts `()' elements into the
- output lists. (I should know how to fix this in a day or
- two.. too bad I never got a scheme course before..))
-
- 5) I don't know if this will work on multiple page schematics.
-
- 6) The top level module is outputted with the same name
- every time, I don't currently think there is a way to
- get at the name of the top level schematic.
-
-
- The netlister does some neat things:
-
-
- 1) It outputs a verilog module with proper port
- declarations, outputs are declared as outputs, inputs
- are declared as inputs, and bidirectional signals are
- declared as inouts.
-
- 2) All nets that are found on the design are declared as
- wires. (This is to allow for net attributes later to
- declare wand's and such)
-
- 3) Any components placed on the schematic that are given
- uref attributes create a verilog instantiation for the
- name of the module as stored in the `device' attribute,
- the instatiated name is given as the `uref' attribute.
-
- 4) All connections into and out of instantiated modules are
- made by name, and not by order, because I can't be sure
- that the order will be right coming off the schematic.
- (anyway, that's better for the long run.)
-
- 5) A comment is inserted at the top of the module to say
- that the file was automatically generated.
-
-
-
- Here's how to proceed to make a schematic that can be netlisted
-to verilog.
-
- 1) Create your modules by the standard method, keep in mind
- that you must supply a `pin#' attribute for each port
- you want to create in the generated verilog. gmk_sym is
- useful for this (with the patch to allow ascii pin names).
-
- 2) Place each of your newly created modules on the
- schematic
-
- 3) Connect nets between the modules you want. Remember, if
- you want legible verilog later, don't forget to name all
- your nets by attaching `label' attributes to them.
-
- 4) Insert IPAD's, OPAD's, and IOPAD's for all the nets you
- want to be visible in the module declaration statement.
- It is especially important to make sure that the nets
- you hook up to the pads are named, as the net names
- could change from run to run, that's a bad thing.
-
- 5) Save your design.
-
- 6) Run the schematic through the netlister:
-
- gnetlist -g verilog -o output.v schematic.sch
-
- 6a) Edit the output file to have the right module name, and
- to remove any duplicate wires.
-
-
- There is an example schematic in the schematic directory, and a
- copy of the verilog netlist generated.
-
-The mechanics:
-
- The I/O ports for the module are detected by enumerating all of
- the nets attached to any symbol bearing the device name of `IPAD',
- `OPAD', or `IOPAD'. If you name one of your blocks with that
- name, don't be surprised if you find `extra' ports in the module
- declaration.
-
- The wires are declared by walking through the list of nets
- returned by the function that I patched into gnetlist. This is
- the source of the duplicate wire declarations. This should
- probably get fixed when `net_is_duplicate' gets set for
- connections made by reference.
-
- Module instantiations are created by enumerating the pins found on
- a symbol and connecting the nets found to the pins. If your block
- has spelling errors, then the module instantiation won't work.
- You will have to manually trace back to find the error.
-
-
- Mike Jarabek
-</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_vhdl_netlister_readme.html b/docs/wiki/geda_vhdl_netlister_readme.html
deleted file mode 100644
index eb53fb0..0000000
--- a/docs/wiki/geda_vhdl_netlister_readme.html
+++ /dev/null
@@ -1,53 +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>geda:vhdl_netlister_readme</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="geda,vhdl_netlister_readme" />
-<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/geda:vhdl_netlister_readme?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:vhdl_netlister_readme"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:vhdl_netlister_readme"; />
-<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">
-
-
-
-<h1><a name="vhdl_netlister_readme" id="vhdl_netlister_readme">VHDL netlister README</a></h1>
-<div class="level1">
-<pre class="code">The VHDL backend
-
-Written by Magnus Danielson and improved by Thomas Heidel
-
-
-A few things you have to care about:
-
-1. In order to generate valid component declarations, you
- have to add an additional attribute to each pin.
- "type=IN" or "type=OUT" or "type=INOUT"
-
-2. The "device" attribute must be unique to a symbol!
- The verilog symbols of the same type for example, have all
- the same device attribute and will therefore not work.
-
-3. Make sure your component-library picks up the vhdl symbols instead
- of the verilog symbols Library paths that show up last are searched
- first!
-</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_wcalc_mp.html b/docs/wiki/geda_wcalc_mp.html
deleted file mode 100644
index 71232ee..0000000
--- a/docs/wiki/geda_wcalc_mp.html
+++ /dev/null
@@ -1,82 +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>geda:wcalc_mp</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="geda,wcalc_mp" />
-<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/geda:wcalc_mp?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:wcalc_mp"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:wcalc_mp"; />
-<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">
-
-
-
-<h1><a name="wcalc_man-page" id="wcalc_man-page">Wcalc man-page</a></h1>
-<div class="level1">
-<pre class="code">WCALC(1) WCALC(1)
-
-
-
-NAME
- wcalc - Transmission line analysis/synthesis calculator.
-
-
-SYNOPSIS
- wcalc
-
-
-DESCRIPTION
- The wcalc program is a tool for the analysis and synthesis of transmis-
- sion line structures and related components. Wcalc provides the abil-
- ity to analyze the electrical parameters of a particular structure
- based on the physical dimensions and material parameters. The synthe-
- sis portion calculates the required physical parameters to meet desired
- electrical specifications. Wcalc includes several models and places an
- emphasis on accuracy.
-
-
-ENVIRONMENT
- WCALC_DATADIR
- If set, wcalc searches in $WCALC_DATADIR for the EPS files used
- when printing out models. The default value is the $pre-
- fix/share/wcalc directory, where prefix is the installation pre-
- fix.
-
-
-SEE ALSO
- stdio-wcalc(1)
-
-
-AUTHORS
- Wcalc was written by Dan McMahill <mcmahill@xxxxxxxxxxxx>
-
-
-BUGS
- None known. Please report any on the Wcalc Sourceforge Project page at
- http://www.sourceforge.net/projects/wcalc
-
-
-
-
-
-
- WCALC(1)</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_wcalc_readme.html b/docs/wiki/geda_wcalc_readme.html
deleted file mode 100644
index 3e195a9..0000000
--- a/docs/wiki/geda_wcalc_readme.html
+++ /dev/null
@@ -1,66 +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>geda:wcalc_readme</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="geda,wcalc_readme" />
-<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/geda:wcalc_readme?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:wcalc_readme"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:wcalc_readme"; />
-<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">
-
-
-
-<h1><a name="wcalc_readme" id="wcalc_readme">Wcalc README</a></h1>
-<div class="level1">
-<pre class="code">$Id: README,v 1.2 2005/10/24 21:12:42 dan Exp $
-
-Wcalc is a tool for the analysis and synthesis of transmission line structures and
-related components. Wcalc provides the ability to analyze the electrical parameters
-of a particular structure based on the physical dimensions and material parameters.
-The synthesis portion calculates the required physical parameters to meet desired
-electrical specifications. Wcalc includes several models and places an emphasis on
-accuracy. Several frontends provide the user with several options for its use.
-
-Models include:
-
- - single layer solenoid inductor
- - single microstrip and stripline
- - coupled microstrip
- - metal-insulator-semiconductor microstrip
- - coaxial cable
-
-Frontends include:
-
- - gtk gui
- - web (cgi)
- - scilab
- - octave
- - matlab
- - stdio
-
-See the file INSTALL for building and installation instructions.
-
-Please report all bugs at the wcalc sourceforge project page
-at http://wcalc.sf.net
-
-See the file COPYING for copying conditions.</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda_wcalc_stdio_mp.html b/docs/wiki/geda_wcalc_stdio_mp.html
deleted file mode 100644
index 5b94155..0000000
--- a/docs/wiki/geda_wcalc_stdio_mp.html
+++ /dev/null
@@ -1,89 +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>geda:wcalc_stdio_mp</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="geda,wcalc_stdio_mp" />
-<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/geda:wcalc_stdio_mp?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=geda"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:wcalc_stdio_mp"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:wcalc_stdio_mp"; />
-<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">
-
-
-
-<h1><a name="stdio_wcalc_man-page" id="stdio_wcalc_man-page">stdio Wcalc man-page</a></h1>
-<div class="level1">
-<pre class="code">STDIO-WCALC(1) STDIO-WCALC(1)
-
-
-
-NAME
- stdio-wcalc - Transmission line analysis/synthesis calculator.
-
-
-SYNOPSIS
- stdio-wcalc [ -v|--verbose ] [ file ... ]
- stdio-wcalc [ -h|--help ]
- stdio-wcalc [ -V|--version ]
-
-
-DESCRIPTION
- The stdio-wcalc program is a simple standard input/output interface to
- libwcalc which is the numerical engine for the wcalc program. The
- input is read from the standard input on a line at a time basis. Each
- line consists of a command followed by the numerical arguments.
-
- The analysis and synthesis functions supported by stdio-wcalc are the
- same as those in the scilab, octave, and matlab frontends to wcalc.
- Please refer to the man pages listed at the end of this man page for
- details on each of the supported functions. The syntax used by
- stdio-wcalc is slightly different than scilab/octave/matlab. Instead
- of [a,b,c] = somefn(x,y,z) as you would use in scilab, octave, or mat-
- lab, you simply enter somefn x y z as the input line to stdio-wcalc and
- the standard output will be a b c
-
- In addition to the analysis and synthesis functions, stdio-wcalc sup-
- ports the "version" command which returns the current version of the
- program.
-
-
-SEE ALSO
- wcalc(1), air_coil_calc(n), air_coil_syn(n), coax_calc(n), coax_syn(n),
- coupled_microstrip_calc(n), coupled_microstrip_syn(n),
- ic_microstrip_calc(n), ic_microstrip_syn(n), microstrip_calc(n),
- microstrip_syn(n), stripline_calc(n), stripline_syn(n)
-
-
-AUTHORS
- Wcalc was written by Dan McMahill <mcmahill@xxxxxxxxxxxx>
-
-
-BUGS
- Please report any on the Wcalc Sourceforge project website at
- http://wcalc.sf.net
-
-
-
-
-
-
- STDIO-WCALC(1)</pre>
-
-</div>
-</div>
-</body>
-</html>
diff --git a/docs/wiki/gerbv-projects.html b/docs/wiki/gerbv-projects.html
index d7183d3..71c9684 100644
--- a/docs/wiki/gerbv-projects.html
+++ b/docs/wiki/gerbv-projects.html
@@ -1,27 +1,16 @@
<!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">
+<html>
<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
- <title>gerbv-projects</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2008-03-21T01:00:30-0400" />
-<meta name="keywords" content="gerbv-projects" />
-<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/gerbv-projects?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/gerbv-projects"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/gerbv-projects"; />
-<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">
+
@@ -43,6 +32,19 @@ Difficulty = 4
</div>
+<h5><a name="add_design_rule_checking_drc_functionality_to_gerbv" id="add_design_rule_checking_drc_functionality_to_gerbv">Add Design Rule Checking (DRC) functionality to Gerbv</a></h5>
+<div class="level5">
+
+<p>
+ Most commercial Gerber file viewers allow the user to check if a Gerber file meets certain layout requirements (like minimum clearances between traces, etc). This project would involve implementing DRC capability into Gerbv, either by importing existing code from PCB, or writing new code. This capability should ideally be put into the libgerbv library, allowing other programs to tap into the DRC capability and allow scripting support.
+</p>
+
+<p>
+Difficulty: 5
+</p>
+
+</div>
+
<h5><a name="autodetection_of_footprints_and_footprint_centroid_location" id="autodetection_of_footprints_and_footprint_centroid_location">Autodetection of footprints, and footprint centroid location</a></h5>
<div class="level5">
@@ -68,6 +70,5 @@ Difficulty = 3
</p>
</div>
-</div>
</body>
</html>
diff --git a/docs/wiki/glue-projects.html b/docs/wiki/glue-projects.html
index f02b688..ed144ed 100644
--- a/docs/wiki/glue-projects.html
+++ b/docs/wiki/glue-projects.html
@@ -1,27 +1,16 @@
<!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">
+<html>
<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
- <title>glue-projects</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2008-03-23T01:12:11-0400" />
-<meta name="keywords" content="glue-projects" />
-<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/glue-projects?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/glue-projects"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/glue-projects"; />
-<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">
+
@@ -34,29 +23,15 @@
</div>
-<h5><a name="xgsch2pcb_project_manager" id="xgsch2pcb_project_manager">Xgsch2pcb project manager</a></h5>
+<h5><a name="autogeneration_of_fab_drawing_with_embedded_fab_notes" id="autogeneration_of_fab_drawing_with_embedded_fab_notes">Autogeneration of fab drawing with embedded fab notes</a></h5>
<div class="level5">
<p>
- gEDA has recently acquired a project manager called xgsch2pcb. It is written in Python. It provides the user a â??dashboardâ?? interface to the various programs comprising the gEDA Suite, such as gschem, gattrib, and PCB. It also handles forward annotation of a design captured in gschem into a board file which may be laid out in PCB.
-</p>
-
-<p>
-The project manager is currently in working prototype stage. This project involves adopting the existing project manager and incorporating new features like:
+ This project involves creating a system which can create an annotated fab drawing from the drill file output by PCB, along with other inputs. In one possible implementation, you could use LaTeX/metapost driven from an external script. The script would read in some type of template holding boilerplate fab notes, insert a .eps version of the drill file, also read in some type of file holding stack-up information and other info for the PCB fab house, run LaTeX on it all, and then output an annotated .ps or .pdf fab drawing.
</p>
-<ul>
-<li class="level1"><div class="li"> Creation of SPICE netlists</div>
-</li>
-<li class="level1"><div class="li"> Invocation of simulators like gnucap or ngspice.</div>
-</li>
-<li class="level1"><div class="li"> Clean up of existing netlist to PCB. </div>
-</li>
-<li class="level1"><div class="li"> Maybe work with the PCB developers to implement a command-oriented list of instructions to PCB (instead of just a board file). This would solve some footprint search path issues.</div>
-</li>
-</ul>
<p>
- Difficulty = 3 or 4, depending upon what is done.
+Difficulty: 2
</p>
</div>
@@ -98,7 +73,7 @@ A new user would like to do the following things inside gschem:
</ul>
<p>
- The simulation runs and the postprocessing may be in an extra program that is triggered by IPC. More thoughts about the project have been entered by Werner Hoch on the gEDA Wiki (<a href="http://geda.seul.org/wiki/geda:circuit_simulation_improvements"; class="wikilink1" title="geda:circuit_simulation_improvements">Circuit simulation improvements</a>, <a href="http://geda.seul.org/wiki/geda:data_plotting_improvements"; class="wikilink1" title="geda:data_plotting_improvements"> Plotting improvements</a>).
+ The simulation runs and the postprocessing may be in an extra program that is triggered by IPC. More thoughts about the project have been entered by Werner Hoch on the gEDA Wiki (<a href="geda-circuit_simulation_improvements.html" class="wikilink1" title="geda-circuit_simulation_improvements.html">Circuit simulation improvements</a>, <a href="geda-data_plotting_improvements.html" class="wikilink1" title="geda-data_plotting_improvements.html"> Plotting improvements</a>).
</p>
<p>
@@ -198,6 +173,5 @@ Difficulty = 1 to 5 depending on the format(s).
</p>
</div>
-</div>
</body>
</html>
diff --git a/docs/wiki/gschem-projects.html b/docs/wiki/gschem-projects.html
index 84f1e0e..1e26b36 100644
--- a/docs/wiki/gschem-projects.html
+++ b/docs/wiki/gschem-projects.html
@@ -1,27 +1,16 @@
<!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">
+<html>
<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
- <title>gschem-projects</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2008-04-04T13:35:50-0400" />
-<meta name="keywords" content="gschem-projects" />
-<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/gschem-projects?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/gschem-projects"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/gschem-projects"; />
-<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">
+
@@ -108,6 +97,19 @@ Difficulty = 1 to 2
</div>
+<h5><a name="improved_and_formalized_mechanism_for_forward_backward_annotation" id="improved_and_formalized_mechanism_for_forward_backward_annotation">Improved and formalized mechanism for forward/backward annotation</a></h5>
+<div class="level5">
+
+<p>
+ Add hooks into gschem needed to fully support things like backannotation of simulation results and click-to-plot results. Specifically, this would enable you to draw a schematic in gschem, then simulate it in ngspice without leaving gschem. The simulation plots would then appear in a graphical pop-up window.
+</p>
+
+<p>
+Difficulty = 3
+</p>
+
+</div>
+
<h5><a name="visual_feedback_for_attached_attributes" id="visual_feedback_for_attached_attributes">Visual feedback for attached attributes</a></h5>
<div class="level5">
@@ -206,19 +208,6 @@ Difficulty = 2 to 3
</div>
-<h5><a name="filled_polygon_object" id="filled_polygon_object">Filled polygon object</a></h5>
-<div class="level5">
-
-<p>
- Adding a filled polygon graphical object type to the gschem symbol file format and, of course, gschem would be a nice project. This would be useful for filled arrows (transistors) and a filled triangle for diodes.
-</p>
-
-<p>
-Difficulty = 2 to 3
-</p>
-
-</div>
-
<h5><a name="an_interactive_sub_sheet_generator" id="an_interactive_sub_sheet_generator">An Interactive Sub Sheet Generator</a></h5>
<div class="level5">
@@ -227,7 +216,7 @@ Difficulty = 2 to 3
</p>
<p>
-Some work has already been done to deal with the bottom-up case. See <a href="http://sourceforge.net/tracker/index.php?func=detail&aid=1800913&group_id=161080&atid=818428"; class="urlextern" title="http://sourceforge.net/tracker/index.php?func=detail&aid=1800913&group_id=161080&atid=818428"; rel="nofollow">the bash script geda_sch2sym</a> available at sourceforge. This may be used as a starting point. However, a restart from scratch would be welcome too.
+Some work has already been done to deal with the bottom-up case. See <a href="http://sourceforge.net/tracker/index.php?func=detail&aid=1800913&group_id=161080&atid=818428"; class="urlextern" title="http://sourceforge.net/tracker/index.php?func=detail&aid=1800913&group_id=161080&atid=818428"; rel="nofollow">the bash script geda_sch2sym</a> available at sourceforge. This may be used as a starting point. However, a restart from scratch would be welcome too.
</p>
<p>
@@ -235,6 +224,5 @@ Difficulty = 2
</p>
</div>
-</div>
</body>
</html>
diff --git a/docs/wiki/gsoc2007.html b/docs/wiki/gsoc2007.html
index 21474d5..8ece0bd 100644
--- a/docs/wiki/gsoc2007.html
+++ b/docs/wiki/gsoc2007.html
@@ -1,27 +1,16 @@
<!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">
+<html>
<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
- <title>gsoc2007</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-10-28T22:49:28-0400" />
-<meta name="keywords" content="gsoc2007" />
-<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/gsoc2007?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/gsoc2007"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/gsoc2007"; />
-<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">
@@ -168,7 +157,7 @@ It is important for us to understand how your project will fit into the rest of
<div class="level3">
<p>
- The list of suggested projects is available <a href="gsoc2007_projects.html" class="wikilink1" title="gsoc2007_projects">here</a>
+ The list of suggested projects is available <a href="gsoc2007_projects.html" class="wikilink1" title="gsoc2007_projects.html">here</a>
</p>
</div>
@@ -193,6 +182,5 @@ It is important for us to understand how your project will fit into the rest of
</ul>
</div>
-<!-- SECTION "Mentors" [5895-] --></div>
-</body>
+<!-- SECTION "Mentors" [5895-] --></body>
</html>
diff --git a/docs/wiki/gsoc2007_projects.html b/docs/wiki/gsoc2007_projects.html
index 61e0f65..c2b847c 100644
--- a/docs/wiki/gsoc2007_projects.html
+++ b/docs/wiki/gsoc2007_projects.html
@@ -1,27 +1,16 @@
<!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">
+<html>
<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
- <title>gsoc2007_projects</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-10-28T22:55:15-0400" />
-<meta name="keywords" content="gsoc2007_projects" />
-<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/gsoc2007_projects?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/gsoc2007_projects"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/gsoc2007_projects"; />
-<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">
@@ -645,6 +634,5 @@ Difficulty = 2
</p>
</div>
-<!-- SECTION "IPC Footprint Calculator" [20651-] --></div>
-</body>
+<!-- SECTION "IPC Footprint Calculator" [20651-] --></body>
</html>
diff --git a/docs/wiki/gsoc2008.html b/docs/wiki/gsoc2008.html
index 94e92d9..04e07a2 100644
--- a/docs/wiki/gsoc2008.html
+++ b/docs/wiki/gsoc2008.html
@@ -1,27 +1,16 @@
<!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">
+<html>
<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
- <title>gsoc2008</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2008-03-17T20:48:01-0400" />
-<meta name="keywords" content="gsoc2008" />
-<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/gsoc2008?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/gsoc2008"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/gsoc2008"; />
-<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">
@@ -57,7 +46,7 @@ The gEDA Project has been accepted into the <a href="http://code.google.com/soc/
<div class="level3">
<p>
- You are welcome to either suggest a new project idea, or select one from our <a href="gsoc2008_projects.html" class="wikilink1" title="gsoc2008_projects">list of suggested projects</a>.
+ You are welcome to either suggest a new project idea, or select one from our <a href="gsoc2008_projects.html" class="wikilink1" title="gsoc2008_projects.html">list of suggested projects</a>.
</p>
</div>
@@ -66,7 +55,7 @@ The gEDA Project has been accepted into the <a href="http://code.google.com/soc/
<div class="level3">
<p>
- 2008 is the second year in which the gEDA Project has participated in Googleâ??s Summer of Code program. Through our experience, we have learned a couple of things about running a successful program. <a href="best_practices.html" class="wikilink1" title="best_practices">Here are the things we ask of our
+ 2008 is the second year in which the gEDA Project has participated in Googleâ??s Summer of Code program. Through our experience, we have learned a couple of things about running a successful program. <a href="best_practices.html" class="wikilink1" title="best_practices.html">Here are the things we ask of our
students</a> to help make the GSoC experience a success for everybody. (<a href="http://code.google.com/soc/2007/geda/about.html"; class="urlextern" title="http://code.google.com/soc/2007/geda/about.html"; rel="nofollow">sponsored gEDA projects in 2007</a>)
</p>
@@ -118,6 +107,5 @@ students</a> to help make the GSoC experience a success for everybody. (<a href=
</ul>
</div>
-<!-- SECTION "Mentors and Administrators" [990-] --></div>
-</body>
+<!-- SECTION "Mentors and Administrators" [990-] --></body>
</html>
diff --git a/docs/wiki/gsoc2008_projects.html b/docs/wiki/gsoc2008_projects.html
index 692d895..22c3f3a 100644
--- a/docs/wiki/gsoc2008_projects.html
+++ b/docs/wiki/gsoc2008_projects.html
@@ -1,27 +1,16 @@
<!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">
+<html>
<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
- <title>gsoc2008_projects</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2008-03-21T01:17:54-0400" />
-<meta name="keywords" content="gsoc2008_projects" />
-<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/gsoc2008_projects?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/gsoc2008_projects"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/gsoc2008_projects"; />
-<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">
@@ -61,7 +50,7 @@
<div class="level3">
<p>
- Projects that make the tools work together are on <a href="glue-projects.html" class="wikilink1" title="glue-projects"> this webpage</a>
+ Projects that make the tools work together are on <a href="glue-projects.html" class="wikilink1" title="glue-projects.html"> this webpage</a>
</p>
</div>
@@ -79,7 +68,7 @@
<div class="level3">
<p>
- Project ideas for PCB are on <a href="pcb-projects.html" class="wikilink1" title="pcb-projects"> this webpage</a>
+ Project ideas for PCB are on <a href="pcb-projects.html" class="wikilink1" title="pcb-projects.html"> this webpage</a>
</p>
</div>
@@ -88,7 +77,7 @@
<div class="level3">
<p>
- Project ideas for Gwave are on <a href="gwave-projects.html" class="wikilink1" title="gwave-projects"> this webpage</a>
+ Project ideas for Gwave are on <a href="gwave-projects.html" class="wikilink1" title="gwave-projects.html"> this webpage</a>
</p>
</div>
@@ -97,7 +86,7 @@
<div class="level3">
<p>
- Project ideas for Gschem are on <a href="gschem-projects.html" class="wikilink1" title="gschem-projects"> this webpage</a>
+ Project ideas for Gschem are on <a href="gschem-projects.html" class="wikilink1" title="gschem-projects.html"> this webpage</a>
</p>
</div>
@@ -115,10 +104,9 @@
<div class="level3">
<p>
- Project ideas for gerbv are on <a href="gerbv-projects.html" class="wikilink1" title="gerbv-projects"> this webpage</a>
+ Project ideas for gerbv are on <a href="gerbv-projects.html" class="wikilink1" title="gerbv-projects.html"> this webpage</a>
</p>
</div>
-<!-- SECTION "Gerbv" [1061-] --></div>
-</body>
+<!-- SECTION "Gerbv" [1061-] --></body>
</html>
diff --git a/docs/wiki/gsoc2009.html b/docs/wiki/gsoc2009.html
new file mode 100644
index 0000000..f9bf230
--- /dev/null
+++ b/docs/wiki/gsoc2009.html
@@ -0,0 +1,134 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="clear">
+
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#google_summer_of_code_2009" class="toc">Google Summer of Code 2009</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#suggested_projects" class="toc">Suggested Projects</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#what_we_ask_from_students" class="toc">What we ask from Students</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#archived_project_info" class="toc">Archived project info</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#mentors_and_administrators" class="toc">Mentors and Administrators</a></span></div></li></ul>
+</li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h3><a name="google_summer_of_code_2009" id="google_summer_of_code_2009">Google Summer of Code 2009</a></h3>
+<div class="level3">
+
+<p>
+The gEDA Project has (not yet!!!) been accepted into the <a href="http://code.google.com/soc/2009/"; class="urlextern" title="http://code.google.com/soc/2009/"; rel="nofollow">Google's Summer of Code</a> 2009 program! Therefore, this page is a work in progress, and will be publically announced if and when the gEDA Project does get accepted into GSoC 2009.
+</p>
+
+<p>
+The gEDA project is excited to have this opportunity again (third year for gEDA in GSoc!) and thanks Google for investing in and organizing the GSoC program. This wiki page will develop as we plan our GSoC 2009 activities.
+</p>
+
+</div>
+<!-- SECTION "Google Summer of Code 2009" [1-538] -->
+<h3><a name="suggested_projects" id="suggested_projects">Suggested Projects</a></h3>
+<div class="level3">
+
+<p>
+ You are welcome to either suggest a new project idea, or select one from our <a href="gsoc2009_projects.html" class="wikilink1" title="gsoc2009_projects.html">list of suggested projects</a>.
+</p>
+
+</div>
+<!-- SECTION "Suggested Projects" [539-704] -->
+<h3><a name="what_we_ask_from_students" id="what_we_ask_from_students">What we ask from Students</a></h3>
+<div class="level3">
+
+<p>
+ 2009 is the third year in which the gEDA Project has participated in Googleâ??s Summer of Code program. Through our experience, we have learned a couple of things about running a successful program. Most importantly, keep in mind that <strong>Google Summer
+of Code is meant to be a full time summer job</strong>. We donâ??t want applicants who work a different job during the day and then try to work on GSoC at night. Itâ??s not fair to us since you wonâ??t be productive, itâ??s not fair to Google since theyâ??re paying you for full-time work, and itâ??s not good for you since youâ??ll soon exhaust yourself and wonâ??t enjoy the GSoC experience!
+</p>
+
+<p>
+<a href="best_practices.html" class="wikilink1" title="best_practices.html">Here are the things we ask of our
+students</a> to help make the GSoC experience a success for everybody.
+</p>
+
+</div>
+<!-- SECTION "What we ask from Students" [705-1486] -->
+<h3><a name="archived_project_info" id="archived_project_info">Archived project info</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> (<a href="http://code.google.com/soc/2008/geda/about.html"; class="urlextern" title="http://code.google.com/soc/2008/geda/about.html"; rel="nofollow">sponsored gEDA projects in 2008</a>)</div>
+</li>
+<li class="level1"><div class="li"> (<a href="http://code.google.com/soc/2007/geda/about.html"; class="urlextern" title="http://code.google.com/soc/2007/geda/about.html"; rel="nofollow">sponsored gEDA projects in 2007</a>)</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Archived project info" [1487-1706] -->
+<h3><a name="mentors_and_administrators" id="mentors_and_administrators">Mentors and Administrators</a></h3>
+<div class="level3">
+
+<p>
+ Here is a list of mentors and administrators for the gEDA Projectâ??s GSoC in 2009. Please feel free to contact any of us with any questions you may have.
+</p>
+
+</div>
+
+<h5><a name="mentors" id="mentors">Mentors</a></h5>
+<div class="level5">
+<ul>
+<li class="level1"><div class="li"> DJ Delorie (dj (AT) delorie (DOT) com) - <strong>PCB</strong> </div>
+</li>
+<li class="level2"><div class="li"> Ben Jackson (ben (AT) ben (DOT) com - <strong>PCB</strong></div>
+</li>
+<li class="level2"><div class="li"> Al Davis (ad151 (AT) freeelectron (DOT) net) - <strong>gnucap</strong></div>
+</li>
+<li class="level2"><div class="li"> Steve Tell (tell (AT) telltronics (DOT) org) - <strong>gwave</strong></div>
+</li>
+<li class="level2"><div class="li"> Peter Brett (peter (AT) peter-b (DOT) co (DOT) uk) - <strong>gEDA/gaf</strong></div>
+</li>
+<li class="level2"><div class="li"> Peter Clifton (pcjc2 (AT) cam (DOT) ac (DOT) uk) - <strong>gEDA/gaf</strong></div>
+</li>
+<li class="level2"><div class="li"> Stuart Brorson (sdb (AT) cloud9 (DOT) net) - <strong>gerbv, gattrib</strong></div>
+</li>
+<li class="level2"><div class="li"> Julian Lamb (thepurlieu (AT) gmail (DOT) com) - <strong>gerbv</strong></div>
+</li>
+<li class="level2"><div class="li"> Steve Williams (steve (AT) icarus (DOT) com) - <strong>Icarus Verilog</strong></div>
+</li>
+<li class="level2"><div class="li"> Cary R. (cygcary (AT) yahoo (DOT) com - <strong>Icarus Verilog</strong></div>
+</li>
+<li class="level2"><div class="li"> Tony Bybell (bybell (AT) nc (DOT) rr (DOT) com - <strong>GTKWave</strong></div>
+</li>
+</ul>
+
+</div>
+
+<h5><a name="administrators" id="administrators">Administrators</a></h5>
+<div class="level5">
+<ul>
+<li class="level1"><div class="li"> Stuart Brorson (sdb (AT) cloud9 (DOT) net) - Primary GSoC admin</div>
+</li>
+<li class="level2"><div class="li"> Ales Hvezda (ahvezda (AT) moria (DOT) seul (DOT) org) - Back-up GSoC admin</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Mentors and Administrators" [1707-] --></body>
+</html>
diff --git a/docs/wiki/gsoc2009_projects.html b/docs/wiki/gsoc2009_projects.html
new file mode 100644
index 0000000..e3157dd
--- /dev/null
+++ b/docs/wiki/gsoc2009_projects.html
@@ -0,0 +1,122 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="clear">
+
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#geda_gsoc_2009_project_ideas" class="toc">gEDA GSoC 2009 Project Ideas</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#general_glue_and_related_gaf_projects" class="toc">General, "glue" and related gaf projects</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#gnucap_circuit_simulation_analysis_program" class="toc">Gnucap circuit simulation/analysis program</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#gwave_analog_waveform_viewer" class="toc">Gwave analog waveform viewer</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#pcb_layout_editor" class="toc">PCB Layout Editor</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#gschem_schematic_capture_tool" class="toc">Gschem schematic capture tool</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#icarus_verilog" class="toc">Icarus Verilog</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#gtkwave" class="toc">GTKWave</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#gerbv" class="toc">Gerbv</a></span></div></li></ul>
+</li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h3><a name="geda_gsoc_2009_project_ideas" id="geda_gsoc_2009_project_ideas">gEDA GSoC 2009 Project Ideas</a></h3>
+<div class="level3">
+
+<p>
+ This page contains various ideas for projects, organized by the tool. You can use these as fodder for creating your application to Google. Also, if you have your own idea, feel free to share it with the gEDA developers – they might like it more than any project on this list!
+</p>
+
+</div>
+<!-- SECTION "gEDA GSoC 2009 Project Ideas" [1-320] -->
+<h3><a name="general_glue_and_related_gaf_projects" id="general_glue_and_related_gaf_projects">General, "glue" and related gaf projects</a></h3>
+<div class="level3">
+
+<p>
+ Projects that make the tools work together are on <a href="glue-projects.html" class="wikilink1" title="glue-projects.html"> this webpage</a>
+</p>
+
+</div>
+<!-- SECTION "General, glue and related gaf projects" [321-457] -->
+<h3><a name="gnucap_circuit_simulation_analysis_program" id="gnucap_circuit_simulation_analysis_program">Gnucap circuit simulation/analysis program</a></h3>
+<div class="level3">
+
+<p>
+ Project ideas for Gnucap are on <a href="http://wiki.gnucap.org/dokuwiki/doku.php?id=gnucap:projects"; class="urlextern" title="http://wiki.gnucap.org/dokuwiki/doku.php?id=gnucap:projects"; rel="nofollow"> this webpage</a>
+</p>
+
+</div>
+<!-- SECTION "Gnucap circuit simulation/analysis program" [458-623] -->
+<h3><a name="gwave_analog_waveform_viewer" id="gwave_analog_waveform_viewer">Gwave analog waveform viewer</a></h3>
+<div class="level3">
+
+<p>
+ Project ideas for gwave are on <a href="gwave-projects.html" class="wikilink1" title="gwave-projects.html"> this webpage</a>
+</p>
+
+</div>
+<!-- SECTION "Gwave analog waveform viewer" [624-732] -->
+<h3><a name="pcb_layout_editor" id="pcb_layout_editor">PCB Layout Editor</a></h3>
+<div class="level3">
+
+<p>
+ Project ideas for PCB are on <a href="pcb-projects.html" class="wikilink1" title="pcb-projects.html"> this webpage</a>
+</p>
+
+</div>
+<!-- SECTION "PCB Layout Editor" [733-824] -->
+<h3><a name="gschem_schematic_capture_tool" id="gschem_schematic_capture_tool">Gschem schematic capture tool</a></h3>
+<div class="level3">
+
+<p>
+ Project ideas for Gschem are on <a href="gschem-projects.html" class="wikilink1" title="gschem-projects.html"> this webpage</a>
+</p>
+
+</div>
+<!-- SECTION "Gschem schematic capture tool" [825-935] -->
+<h3><a name="icarus_verilog" id="icarus_verilog">Icarus Verilog</a></h3>
+<div class="level3">
+
+<p>
+ Project ideas for Icarus Verilog are on <a href="http://iverilog.wikia.com/wiki/Projects"; class="urlextern" title="http://iverilog.wikia.com/wiki/Projects"; rel="nofollow"> this webpage</a>
+</p>
+
+</div>
+<!-- SECTION "Icarus Verilog" [936-1062] -->
+<h3><a name="gtkwave" id="gtkwave">GTKWave</a></h3>
+<div class="level3">
+
+<p>
+ Project ideas for Icarus Verilog are on <a href="gtkwave-projects.html" class="wikilink1" title="gtkwave-projects.html"> this webpage</a>
+</p>
+
+</div>
+<!-- SECTION "GTKWave" [1063-1159] -->
+<h3><a name="gerbv" id="gerbv">Gerbv</a></h3>
+<div class="level3">
+
+<p>
+ Project ideas for gerbv are on <a href="gerbv-projects.html" class="wikilink1" title="gerbv-projects.html"> this webpage</a>
+</p>
+
+</div>
+<!-- SECTION "Gerbv" [1160-] --></body>
+</html>
diff --git a/docs/wiki/gtkwave-projects.html b/docs/wiki/gtkwave-projects.html
new file mode 100644
index 0000000..74ba1d3
--- /dev/null
+++ b/docs/wiki/gtkwave-projects.html
@@ -0,0 +1,38 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h3><a name="gtkwave_projects" id="gtkwave_projects">GTKWave projects</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> System Verilog and/or VHDL support for RTLBrowse. Currently itâ??s only plain-vanilla verilog from the 1995 <acronym title="specification">spec</acronym>.</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> More â??interestingâ?? integrations with other tools. The new Tcl interface adds a bunch of possibilities. I know one guy is using it to allow remote control from emacs through a bridge server.</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> Improved analog support. This would also mean being able to read various spice rawfiles, etc.</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> An open source equivalent to FSDB in terms of speed, file size, and capabilities of the different types of data it can store. This wouldnâ??t necessarily be a gtkwave-only project given that Iâ??d expect a reader/writer <acronym title="Application Programming Interface">API</acronym> that for example, icarus/ghdl and gtkwave can interface to. This is the most challenging of the bunch and would require not only coding, but lots of experimentation + throwing away code + restarting over when itâ??s realized a better way can be used to do something.</div>
+</li>
+</ul>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/gwave-projects.html b/docs/wiki/gwave-projects.html
index 09217db..78d0530 100644
--- a/docs/wiki/gwave-projects.html
+++ b/docs/wiki/gwave-projects.html
@@ -1,27 +1,16 @@
<!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">
+<html>
<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
- <title>gwave-projects</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2008-03-21T00:50:23-0400" />
-<meta name="keywords" content="gwave-projects" />
-<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/gwave-projects?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/gwave-projects"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/gwave-projects"; />
-<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">
+
@@ -34,6 +23,24 @@
</div>
+<h5><a name="geda_integration" id="geda_integration">gEDA integration</a></h5>
+<div class="level5">
+
+<p>
+ This project involves improving the integration of gwave into the interprocess-communication to and from the other tools, especialy gschem and gnucap. While gwave has an X11-based remote mechanism, Dbus is now the standard, and should probably be used instead.
+</p>
+
+</div>
+
+<h5><a name="developing_unit_tests_for_gtk_-2.0" id="developing_unit_tests_for_gtk_-2.0">Developing unit tests for GTK+-2.0</a></h5>
+<div class="level5">
+
+<p>
+ Gwave has been ported to Gtk2. As part of this effort, developing a battery of unit tests for gwave would be useful. The idea is to create a variety of different input files which exercise gwaveâ??s ability to import and display waveforms. An important feature for testing will be to compare the displayed waveform against a â??goldenâ?? waveform to verify rendering correctness.
+</p>
+
+</div>
+
<h5><a name="user_interface" id="user_interface">User Interface</a></h5>
<div class="level5">
<ul>
@@ -135,19 +142,5 @@
</ul>
</div>
-
-<h5><a name="geda_integration" id="geda_integration">gEDA integration</a></h5>
-<div class="level5">
-<ul>
-<li class="level1"><div class="li"> communication with gschem: choose variable to plot from the schematic, etc.</div>
-</li>
-</ul>
-<ul>
-<li class="level1"><div class="li"> comunication with gnucap and other simulators</div>
-</li>
-</ul>
-
-</div>
-</div>
</body>
</html>
diff --git a/docs/wiki/images/.gitignore b/docs/wiki/images/.gitignore
new file mode 100644
index 0000000..23c1897
--- /dev/null
+++ b/docs/wiki/images/.gitignore
@@ -0,0 +1,3 @@
+Makefile
+Makefile.in
+*~
diff --git a/docs/wiki/images/Makefile.am b/docs/wiki/images/Makefile.am
new file mode 100644
index 0000000..b8db727
--- /dev/null
+++ b/docs/wiki/images/Makefile.am
@@ -0,0 +1,13 @@
+
+
+docname=wiki
+docsdir = $(docdir)/$(docname)/images
+
+SUBDIRS = smileys interwiki
+
+docs_DATA = link_icon.gif open.gif interwiki.png closed.gif button-cc.gif button-donate.gif mail_icon.gif tocdot2.gif button-rss.png button-php.gif button-xhtml.png bullet.gif button-css.png button-dw.png windows.gif
+
+EXTRA_DIST = $(docs_DATA)
+
+MAINTAINERCLEANFILES = *.log core FILE *~ Makefile.in
+
diff --git a/docs/wiki/images/bullet.gif b/docs/wiki/images/bullet.gif
new file mode 100644
index 0000000..b43de48
Binary files /dev/null and b/docs/wiki/images/bullet.gif differ
diff --git a/docs/wiki/images/button-cc.gif b/docs/wiki/images/button-cc.gif
new file mode 100644
index 0000000..5861d63
Binary files /dev/null and b/docs/wiki/images/button-cc.gif differ
diff --git a/docs/wiki/images/button-css.png b/docs/wiki/images/button-css.png
new file mode 100644
index 0000000..706325e
Binary files /dev/null and b/docs/wiki/images/button-css.png differ
diff --git a/docs/wiki/images/button-donate.gif b/docs/wiki/images/button-donate.gif
new file mode 100644
index 0000000..ec682c6
Binary files /dev/null and b/docs/wiki/images/button-donate.gif differ
diff --git a/docs/wiki/images/button-dw.png b/docs/wiki/images/button-dw.png
new file mode 100644
index 0000000..39d5f56
Binary files /dev/null and b/docs/wiki/images/button-dw.png differ
diff --git a/docs/wiki/images/button-php.gif b/docs/wiki/images/button-php.gif
new file mode 100644
index 0000000..28f329a
Binary files /dev/null and b/docs/wiki/images/button-php.gif differ
diff --git a/docs/wiki/images/button-rss.png b/docs/wiki/images/button-rss.png
new file mode 100644
index 0000000..b036f71
Binary files /dev/null and b/docs/wiki/images/button-rss.png differ
diff --git a/docs/wiki/images/button-xhtml.png b/docs/wiki/images/button-xhtml.png
new file mode 100644
index 0000000..ec68644
Binary files /dev/null and b/docs/wiki/images/button-xhtml.png differ
diff --git a/docs/wiki/images/closed.gif b/docs/wiki/images/closed.gif
new file mode 100644
index 0000000..8414d4d
Binary files /dev/null and b/docs/wiki/images/closed.gif differ
diff --git a/docs/wiki/images/interwiki.png b/docs/wiki/images/interwiki.png
new file mode 100644
index 0000000..73d6f8d
Binary files /dev/null and b/docs/wiki/images/interwiki.png differ
diff --git a/docs/wiki/images/interwiki/.gitignore b/docs/wiki/images/interwiki/.gitignore
new file mode 100644
index 0000000..23c1897
--- /dev/null
+++ b/docs/wiki/images/interwiki/.gitignore
@@ -0,0 +1,3 @@
+Makefile
+Makefile.in
+*~
diff --git a/docs/wiki/images/interwiki/Makefile.am b/docs/wiki/images/interwiki/Makefile.am
new file mode 100644
index 0000000..a294f2c
--- /dev/null
+++ b/docs/wiki/images/interwiki/Makefile.am
@@ -0,0 +1,11 @@
+
+
+docname=wiki
+docsdir = $(docdir)/$(docname)/images/interwiki
+
+docs_DATA = bug.gif coral.gif amazon.de.gif google.gif amazon.gif wpmeta.gif sb.gif doku.gif wiki.gif amazon.uk.gif wp.gif wpde.gif meatball.gif phpfn.gif
+
+EXTRA_DIST = $(docs_DATA)
+
+MAINTAINERCLEANFILES = *.log core FILE *~ Makefile.in
+
diff --git a/docs/wiki/images/interwiki/amazon.de.gif b/docs/wiki/images/interwiki/amazon.de.gif
new file mode 100644
index 0000000..f52c1c5
Binary files /dev/null and b/docs/wiki/images/interwiki/amazon.de.gif differ
diff --git a/docs/wiki/images/interwiki/amazon.gif b/docs/wiki/images/interwiki/amazon.gif
new file mode 100644
index 0000000..f52c1c5
Binary files /dev/null and b/docs/wiki/images/interwiki/amazon.gif differ
diff --git a/docs/wiki/images/interwiki/amazon.uk.gif b/docs/wiki/images/interwiki/amazon.uk.gif
new file mode 100644
index 0000000..f52c1c5
Binary files /dev/null and b/docs/wiki/images/interwiki/amazon.uk.gif differ
diff --git a/docs/wiki/images/interwiki/bug.gif b/docs/wiki/images/interwiki/bug.gif
new file mode 100644
index 0000000..3432b8d
Binary files /dev/null and b/docs/wiki/images/interwiki/bug.gif differ
diff --git a/docs/wiki/images/interwiki/coral.gif b/docs/wiki/images/interwiki/coral.gif
new file mode 100644
index 0000000..0f9f675
Binary files /dev/null and b/docs/wiki/images/interwiki/coral.gif differ
diff --git a/docs/wiki/images/interwiki/doku.gif b/docs/wiki/images/interwiki/doku.gif
new file mode 100644
index 0000000..7dc4248
Binary files /dev/null and b/docs/wiki/images/interwiki/doku.gif differ
diff --git a/docs/wiki/images/interwiki/google.gif b/docs/wiki/images/interwiki/google.gif
new file mode 100644
index 0000000..fb39f61
Binary files /dev/null and b/docs/wiki/images/interwiki/google.gif differ
diff --git a/docs/wiki/images/interwiki/meatball.gif b/docs/wiki/images/interwiki/meatball.gif
new file mode 100644
index 0000000..7ac5454
Binary files /dev/null and b/docs/wiki/images/interwiki/meatball.gif differ
diff --git a/docs/wiki/images/interwiki/phpfn.gif b/docs/wiki/images/interwiki/phpfn.gif
new file mode 100644
index 0000000..638d4c4
Binary files /dev/null and b/docs/wiki/images/interwiki/phpfn.gif differ
diff --git a/docs/wiki/images/interwiki/sb.gif b/docs/wiki/images/interwiki/sb.gif
new file mode 100644
index 0000000..e272a29
Binary files /dev/null and b/docs/wiki/images/interwiki/sb.gif differ
diff --git a/docs/wiki/images/interwiki/wiki.gif b/docs/wiki/images/interwiki/wiki.gif
new file mode 100644
index 0000000..e8dc5d2
Binary files /dev/null and b/docs/wiki/images/interwiki/wiki.gif differ
diff --git a/docs/wiki/images/interwiki/wp.gif b/docs/wiki/images/interwiki/wp.gif
new file mode 100644
index 0000000..ca853b8
Binary files /dev/null and b/docs/wiki/images/interwiki/wp.gif differ
diff --git a/docs/wiki/images/interwiki/wpde.gif b/docs/wiki/images/interwiki/wpde.gif
new file mode 100644
index 0000000..ca853b8
Binary files /dev/null and b/docs/wiki/images/interwiki/wpde.gif differ
diff --git a/docs/wiki/images/interwiki/wpmeta.gif b/docs/wiki/images/interwiki/wpmeta.gif
new file mode 100644
index 0000000..ca853b8
Binary files /dev/null and b/docs/wiki/images/interwiki/wpmeta.gif differ
diff --git a/docs/wiki/images/link_icon.gif b/docs/wiki/images/link_icon.gif
new file mode 100644
index 0000000..815ccb1
Binary files /dev/null and b/docs/wiki/images/link_icon.gif differ
diff --git a/docs/wiki/images/mail_icon.gif b/docs/wiki/images/mail_icon.gif
new file mode 100644
index 0000000..50a87a9
Binary files /dev/null and b/docs/wiki/images/mail_icon.gif differ
diff --git a/docs/wiki/images/open.gif b/docs/wiki/images/open.gif
new file mode 100644
index 0000000..f5d5c7e
Binary files /dev/null and b/docs/wiki/images/open.gif differ
diff --git a/docs/wiki/images/smileys/.gitignore b/docs/wiki/images/smileys/.gitignore
new file mode 100644
index 0000000..23c1897
--- /dev/null
+++ b/docs/wiki/images/smileys/.gitignore
@@ -0,0 +1,3 @@
+Makefile
+Makefile.in
+*~
diff --git a/docs/wiki/images/smileys/Makefile.am b/docs/wiki/images/smileys/Makefile.am
new file mode 100644
index 0000000..2e01243
--- /dev/null
+++ b/docs/wiki/images/smileys/Makefile.am
@@ -0,0 +1,11 @@
+
+
+docname=wiki
+docsdir = $(docdir)/$(docname)/images/smileys
+
+docs_DATA = icon_twisted.gif icon_neutral.gif icon_wink.gif fixme.gif icon_evil.gif icon_idea.gif icon_doubt2.gif icon_razz.gif icon_eek.gif delete.gif icon_doubt.gif icon_redface.gif icon_mrgreen.gif icon_smile.gif icon_frown.gif icon_silenced.gif icon_cool.gif icon_rolleyes.gif icon_biggrin.gif icon_question.gif icon_exclaim.gif icon_surprised.gif icon_arrow.gif icon_lol.gif icon_kaddi.gif icon_sad.gif icon_smile2.gif icon_cry.gif icon_confused.gif icon_fun.gif
+
+EXTRA_DIST = $(docs_DATA)
+
+MAINTAINERCLEANFILES = *.log core FILE *~ Makefile.in
+
diff --git a/docs/wiki/images/smileys/delete.gif b/docs/wiki/images/smileys/delete.gif
new file mode 100644
index 0000000..d668348
Binary files /dev/null and b/docs/wiki/images/smileys/delete.gif differ
diff --git a/docs/wiki/images/smileys/fixme.gif b/docs/wiki/images/smileys/fixme.gif
new file mode 100644
index 0000000..b66ea99
Binary files /dev/null and b/docs/wiki/images/smileys/fixme.gif differ
diff --git a/docs/wiki/images/smileys/icon_arrow.gif b/docs/wiki/images/smileys/icon_arrow.gif
new file mode 100644
index 0000000..2880055
Binary files /dev/null and b/docs/wiki/images/smileys/icon_arrow.gif differ
diff --git a/docs/wiki/images/smileys/icon_biggrin.gif b/docs/wiki/images/smileys/icon_biggrin.gif
new file mode 100644
index 0000000..d352772
Binary files /dev/null and b/docs/wiki/images/smileys/icon_biggrin.gif differ
diff --git a/docs/wiki/images/smileys/icon_confused.gif b/docs/wiki/images/smileys/icon_confused.gif
new file mode 100644
index 0000000..0c49e06
Binary files /dev/null and b/docs/wiki/images/smileys/icon_confused.gif differ
diff --git a/docs/wiki/images/smileys/icon_cool.gif b/docs/wiki/images/smileys/icon_cool.gif
new file mode 100644
index 0000000..cead030
Binary files /dev/null and b/docs/wiki/images/smileys/icon_cool.gif differ
diff --git a/docs/wiki/images/smileys/icon_cry.gif b/docs/wiki/images/smileys/icon_cry.gif
new file mode 100644
index 0000000..7d54b1f
Binary files /dev/null and b/docs/wiki/images/smileys/icon_cry.gif differ
diff --git a/docs/wiki/images/smileys/icon_doubt.gif b/docs/wiki/images/smileys/icon_doubt.gif
new file mode 100644
index 0000000..fd7903b
Binary files /dev/null and b/docs/wiki/images/smileys/icon_doubt.gif differ
diff --git a/docs/wiki/images/smileys/icon_doubt2.gif b/docs/wiki/images/smileys/icon_doubt2.gif
new file mode 100644
index 0000000..eb4b70b
Binary files /dev/null and b/docs/wiki/images/smileys/icon_doubt2.gif differ
diff --git a/docs/wiki/images/smileys/icon_eek.gif b/docs/wiki/images/smileys/icon_eek.gif
new file mode 100644
index 0000000..5d39781
Binary files /dev/null and b/docs/wiki/images/smileys/icon_eek.gif differ
diff --git a/docs/wiki/images/smileys/icon_evil.gif b/docs/wiki/images/smileys/icon_evil.gif
new file mode 100644
index 0000000..ab1aa8e
Binary files /dev/null and b/docs/wiki/images/smileys/icon_evil.gif differ
diff --git a/docs/wiki/images/smileys/icon_exclaim.gif b/docs/wiki/images/smileys/icon_exclaim.gif
new file mode 100644
index 0000000..6e50e2e
Binary files /dev/null and b/docs/wiki/images/smileys/icon_exclaim.gif differ
diff --git a/docs/wiki/images/smileys/icon_frown.gif b/docs/wiki/images/smileys/icon_frown.gif
new file mode 100644
index 0000000..d2ac78c
Binary files /dev/null and b/docs/wiki/images/smileys/icon_frown.gif differ
diff --git a/docs/wiki/images/smileys/icon_fun.gif b/docs/wiki/images/smileys/icon_fun.gif
new file mode 100644
index 0000000..a8bb8a3
Binary files /dev/null and b/docs/wiki/images/smileys/icon_fun.gif differ
diff --git a/docs/wiki/images/smileys/icon_idea.gif b/docs/wiki/images/smileys/icon_idea.gif
new file mode 100644
index 0000000..a40ae0d
Binary files /dev/null and b/docs/wiki/images/smileys/icon_idea.gif differ
diff --git a/docs/wiki/images/smileys/icon_kaddi.gif b/docs/wiki/images/smileys/icon_kaddi.gif
new file mode 100644
index 0000000..1410f7f
Binary files /dev/null and b/docs/wiki/images/smileys/icon_kaddi.gif differ
diff --git a/docs/wiki/images/smileys/icon_lol.gif b/docs/wiki/images/smileys/icon_lol.gif
new file mode 100644
index 0000000..374ba15
Binary files /dev/null and b/docs/wiki/images/smileys/icon_lol.gif differ
diff --git a/docs/wiki/images/smileys/icon_mrgreen.gif b/docs/wiki/images/smileys/icon_mrgreen.gif
new file mode 100644
index 0000000..b54cd0f
Binary files /dev/null and b/docs/wiki/images/smileys/icon_mrgreen.gif differ
diff --git a/docs/wiki/images/smileys/icon_neutral.gif b/docs/wiki/images/smileys/icon_neutral.gif
new file mode 100644
index 0000000..4f31156
Binary files /dev/null and b/docs/wiki/images/smileys/icon_neutral.gif differ
diff --git a/docs/wiki/images/smileys/icon_question.gif b/docs/wiki/images/smileys/icon_question.gif
new file mode 100644
index 0000000..9d07226
Binary files /dev/null and b/docs/wiki/images/smileys/icon_question.gif differ
diff --git a/docs/wiki/images/smileys/icon_razz.gif b/docs/wiki/images/smileys/icon_razz.gif
new file mode 100644
index 0000000..29da2a2
Binary files /dev/null and b/docs/wiki/images/smileys/icon_razz.gif differ
diff --git a/docs/wiki/images/smileys/icon_redface.gif b/docs/wiki/images/smileys/icon_redface.gif
new file mode 100644
index 0000000..ad76283
Binary files /dev/null and b/docs/wiki/images/smileys/icon_redface.gif differ
diff --git a/docs/wiki/images/smileys/icon_rolleyes.gif b/docs/wiki/images/smileys/icon_rolleyes.gif
new file mode 100644
index 0000000..d7f5f2f
Binary files /dev/null and b/docs/wiki/images/smileys/icon_rolleyes.gif differ
diff --git a/docs/wiki/images/smileys/icon_sad.gif b/docs/wiki/images/smileys/icon_sad.gif
new file mode 100644
index 0000000..d2ac78c
Binary files /dev/null and b/docs/wiki/images/smileys/icon_sad.gif differ
diff --git a/docs/wiki/images/smileys/icon_silenced.gif b/docs/wiki/images/smileys/icon_silenced.gif
new file mode 100644
index 0000000..448399b
Binary files /dev/null and b/docs/wiki/images/smileys/icon_silenced.gif differ
diff --git a/docs/wiki/images/smileys/icon_smile.gif b/docs/wiki/images/smileys/icon_smile.gif
new file mode 100644
index 0000000..7b1f6d3
Binary files /dev/null and b/docs/wiki/images/smileys/icon_smile.gif differ
diff --git a/docs/wiki/images/smileys/icon_smile2.gif b/docs/wiki/images/smileys/icon_smile2.gif
new file mode 100644
index 0000000..769639d
Binary files /dev/null and b/docs/wiki/images/smileys/icon_smile2.gif differ
diff --git a/docs/wiki/images/smileys/icon_surprised.gif b/docs/wiki/images/smileys/icon_surprised.gif
new file mode 100644
index 0000000..cb21424
Binary files /dev/null and b/docs/wiki/images/smileys/icon_surprised.gif differ
diff --git a/docs/wiki/images/smileys/icon_twisted.gif b/docs/wiki/images/smileys/icon_twisted.gif
new file mode 100644
index 0000000..502fe24
Binary files /dev/null and b/docs/wiki/images/smileys/icon_twisted.gif differ
diff --git a/docs/wiki/images/smileys/icon_wink.gif b/docs/wiki/images/smileys/icon_wink.gif
new file mode 100644
index 0000000..d148288
Binary files /dev/null and b/docs/wiki/images/smileys/icon_wink.gif differ
diff --git a/docs/wiki/images/tocdot2.gif b/docs/wiki/images/tocdot2.gif
new file mode 100644
index 0000000..3d39c2e
Binary files /dev/null and b/docs/wiki/images/tocdot2.gif differ
diff --git a/docs/wiki/images/windows.gif b/docs/wiki/images/windows.gif
new file mode 100644
index 0000000..4f12acc
Binary files /dev/null and b/docs/wiki/images/windows.gif differ
diff --git a/docs/wiki/index.html b/docs/wiki/index.html
index 91d4bf3..d876a26 100644
--- a/docs/wiki/index.html
+++ b/docs/wiki/index.html
@@ -1,27 +1,16 @@
<!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">
+<html>
<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
- <title>start</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2008-03-01T12:15:14-0500" />
-<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/"; />
-<link rel="contents" href="http://geda.seul.org/wiki/start?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/start"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/start"; />
-<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">
@@ -48,12 +37,12 @@
<div class="level1">
</div>
-<!-- SECTION "gEDA Project Wiki" [2-34] -->
+<!-- SECTION "gEDA Project Wiki" [2-35] -->
<h2><a name="what_is_geda" id="what_is_geda">What is gEDA?</a></h2>
<div class="level2">
<p>
- The <a href="http://geda.seul.org/"; class="urlextern" title="http://geda.seul.org"; rel="nofollow">gEDA project</a> is developing a full <acronym title="GNU General Public License">GPL</acronym>â??d suite of Electronic Design Automation tools. These tools are used for electrical circuit design, schematic capture, simulation, prototyping, and production. Currently, the gEDA project offers a mature suite of free software applications for electronics design, including schematic capture, attribute management, bill of materials (BOM) generation, netlisting into over 20 netlist formats, analog and digital simulation, and printed circuit board (PCB) layout.
+ The <a href="http://www.gpleda.org"; class="urlextern" title="http://www.gpleda.org"; rel="nofollow">gEDA project</a> is developing a full <acronym title="GNU General Public License">GPL</acronym>â??d suite and toolkit of Electronic Design Automation tools. These tools are used for electrical circuit design, schematic capture, simulation, prototyping, and production. Currently, the gEDA project offers a mature suite of free software applications for electronics design, including schematic capture, attribute management, bill of materials (BOM) generation, netlisting into over 20 netlist formats, analog and digital simulation, and printed circuit board (PCB) layout.
</p>
<p>
@@ -61,11 +50,11 @@ The tools involved in the Suite enable you to professional-quality design of low
</p>
<p>
-All of the software in the gEDA suite can be found on the <a href="http://geda.seul.org/download.html"; class="urlextern" title="http://geda.seul.org/download.html"; rel="nofollow">downloads page</a>.
+All of the software in the gEDA suite can be found on the <a href="http://www.gpleda.org/download.html"; class="urlextern" title="http://www.gpleda.org/download.html"; rel="nofollow">downloads page</a>.
</p>
</div>
-<!-- SECTION "What is gEDA?" [35-1160] -->
+<!-- SECTION "What is gEDA?" [36-1175] -->
<h2><a name="official_project_documentation" id="official_project_documentation">Official Project documentation</a></h2>
<div class="level2">
@@ -73,12 +62,12 @@ All of the software in the gEDA suite can be found on the <a href="http://geda.s
These are the official project docs. They have been converted from LaTeX and <acronym title="HyperText Markup Language">HTML</acronym> documents into Wiki pages so that the gEDA community may more easily maintain them.
</p>
<ul>
-<li class="level1"><div class="li"> <a href="geda_documentation.html" class="wikilink1" title="geda:documentation">Documentation</a> : The latest versions of the gEDA Tool Suite documentation.</div>
+<li class="level1"><div class="li"> <a href="geda-documentation.html" class="wikilink1" title="geda-documentation.html">Documentation</a> : The latest versions of the gEDA Tool Suite documentation.</div>
</li>
</ul>
</div>
-<!-- SECTION "Official Project documentation" [1161-1461] -->
+<!-- SECTION "Official Project documentation" [1176-1478] -->
<h2><a name="faqs_and_informal_project_documentation" id="faqs_and_informal_project_documentation">FAQs and Informal Project Documentation</a></h2>
<div class="level2">
@@ -86,71 +75,81 @@ These are the official project docs. They have been converted from LaTeX and <a
These are FAQs, HOWTOs, and tips/tricks to help you with the practical details of using the gEDA Suite. If you are having a problem, browse these pages first.
</p>
<ul>
-<li class="level1"><div class="li"> <a href="geda_faq.html" class="wikilink1" title="geda:faq">FAQ</a> : Frequently Asked Questions about the gEDA project itself.</div>
+<li class="level1"><div class="li"> <a href="geda-faq.html" class="wikilink1" title="geda-faq.html">FAQ</a> : Frequently Asked Questions about the gEDA project itself.</div>
</li>
-<li class="level1"><div class="li"> <a href="geda_installation.html" class="wikilink1" title="geda:installation">Installation</a> : gEDA installation HOWTO and <acronym title="Frequently Asked Questions">FAQ</acronym>.</div>
+<li class="level1"><div class="li"> <a href="geda-installation.html" class="wikilink1" title="geda-installation.html">Installation</a> : gEDA installation HOWTO and <acronym title="Frequently Asked Questions">FAQ</acronym>.</div>
</li>
-<li class="level1"><div class="li"> <a href="geda_glossary.html" class="wikilink1" title="geda:glossary">Glossary</a> : Glossary of terms that are specific to the gEDA Suite</div>
+<li class="level1"><div class="li"> <a href="geda-glossary.html" class="wikilink1" title="geda-glossary.html">Glossary</a> : Glossary of terms that are specific to the gEDA Suite.</div>
</li>
-<li class="level1"><div class="li"> <a href="geda_usage.html" class="wikilink1" title="geda:usage">Usage</a> : Questions about how to do electronic design using the gEDA toolset – information which applies to several or all tools in the gEDA Suite.</div>
+<li class="level1"><div class="li"> <a href="geda-usage.html" class="wikilink1" title="geda-usage.html">Usage</a> : Questions about how to do electronic design using the gEDA toolset – information which applies to several or all tools in the gEDA Suite.</div>
</li>
-<li class="level1"><div class="li"> <a href="geda_faq-gschem.html" class="wikilink1" title="geda:faq-gschem">FAQ-gschem</a> : Questions about installing, configuring, and using gschem. Also, questions about creating and using gschem symbols.</div>
+<li class="level1"><div class="li"> <a href="geda-faq-gschem.html" class="wikilink1" title="geda-faq-gschem.html">FAQ-gschem</a> : Questions about installing, configuring, and using gschem. Also, questions about creating and using gschem symbols.</div>
</li>
-<li class="level1"><div class="li"> <a href="geda_faq-attribs.html" class="wikilink1" title="geda:faq-attribs">FAQ-attribs</a> : Dealing with BOMs, DRCs, attribute management, and all that.</div>
+<li class="level1"><div class="li"> <a href="geda-faq-attribs.html" class="wikilink1" title="geda-faq-attribs.html">FAQ-attribs</a> : Dealing with BOMs, DRCs, attribute management, and all that.</div>
</li>
-<li class="level1"><div class="li"> <a href="geda_faq-gnetlist.html" class="wikilink1" title="geda:faq-gnetlist">FAQ-gnetlist</a> : Questions about installing, configuring, and using gnetlist.</div>
+<li class="level1"><div class="li"> <a href="geda-faq-gnetlist.html" class="wikilink1" title="geda-faq-gnetlist.html">FAQ-gnetlist</a> : Questions about installing, configuring, and using gnetlist.</div>
</li>
-<li class="level1"><div class="li"> <a href="geda_faq-simulation.html" class="wikilink1" title="geda:faq-simulation">FAQ-simulation</a> : Questions about simulating your design using gEDA tools.</div>
+<li class="level1"><div class="li"> <a href="geda-faq-simulation.html" class="wikilink1" title="geda-faq-simulation.html">FAQ-simulation</a> : Questions about simulating your design using gEDA tools.</div>
</li>
-<li class="level1"><div class="li"> <a href="geda_faq-gsch2pcb.html" class="wikilink1" title="geda:faq-gsch2pcb">FAQ-gsch2pcb</a> : How to take your design to layout using PCB.</div>
+<li class="level1"><div class="li"> <a href="geda-faq-gsch2pcb.html" class="wikilink1" title="geda-faq-gsch2pcb.html">FAQ-gsch2pcb</a> : How to take your design to layout using PCB.</div>
</li>
-<li class="level1"><div class="li"> <a href="geda_faq-pcb.html" class="wikilink1" title="geda:faq-pcb">FAQ-pcb</a> : Questions about the printed circuit board tool â??pcbâ??.</div>
+<li class="level1"><div class="li"> <a href="geda-faq-pcb.html" class="wikilink1" title="geda-faq-pcb.html">FAQ-pcb</a> : Questions about the printed circuit board tool â??pcbâ??.</div>
</li>
-<li class="level1"><div class="li"> <a href="geda_pcb-quick_reference.html" class="wikilink1" title="geda:pcb-quick_reference">PCB-quick reference</a> : PCB Quick Reference Sheet.</div>
+<li class="level1"><div class="li"> <a href="geda-pcb-quick_reference.html" class="wikilink1" title="geda-pcb-quick_reference.html">PCB-quick reference</a> : PCB Quick Reference Sheet.</div>
</li>
-<li class="level1"><div class="li"> <a href="geda_pcb_tips.html" class="wikilink1" title="geda:pcb_tips">PCB tips</a> : Tips and tricks for using PCB.</div>
+<li class="level1"><div class="li"> <a href="geda-pcb_tips.html" class="wikilink1" title="geda-pcb_tips.html">PCB tips</a> : Tips and tricks for using PCB.</div>
</li>
-<li class="level1"><div class="li"> <a href="geda_pcb_footprints.html" class="wikilink1" title="geda:pcb_footprints">PCB footprints</a> : The ins and outs of using, creating, and sharing footprints.</div>
+<li class="level1"><div class="li"> <a href="geda-pcb_footprints.html" class="wikilink1" title="geda-pcb_footprints.html">PCB footprints</a> : How to create, use and share footprints.</div>
</li>
-<li class="level1"><div class="li"> <a href="geda_scg.html" class="wikilink1" title="geda:scg">scg</a> : gschem symbol creation guide.</div>
+<li class="level1"><div class="li"> <a href="geda-scg.html" class="wikilink1" title="geda-scg.html">scg</a> : gschem symbol creation guide.</div>
</li>
-<li class="level1"><div class="li"> <a href="geda_guile_scripting.html" class="wikilink1" title="geda:guile_scripting">Guile scripting</a> : Guile functions & variables provided by the gEDA tools.</div>
+<li class="level1"><div class="li"> <a href="geda-guile_scripting.html" class="wikilink1" title="geda-guile_scripting.html">Guile scripting</a> : Guile functions & variables provided by the gEDA tools.</div>
</li>
</ul>
</div>
-<!-- SECTION "FAQs and Informal Project Documentation" [1462-2984] -->
+<!-- SECTION "FAQs and Informal Project Documentation" [1479-2986] -->
<h2><a name="developer_documentation" id="developer_documentation">Developer Documentation</a></h2>
<div class="level2">
<p>
-These are pages concerning the development of the gEDA suite.
+The following pages are related to the day-to-day development of the gEDA suite:
</p>
<ul>
-<li class="level1"><div class="li"> <a href="http://www.geda.seul.org/developer.html"; class="urlextern" title="http://www.geda.seul.org/developer.html"; rel="nofollow"> developer.html</a> : All information a gEDA developer needs </div>
+<li class="level1"><div class="li"> <a href="http://www.gpleda.org/developer.html"; class="urlextern" title="http://www.gpleda.org/developer.html"; rel="nofollow"> developer.html</a> : Code repository, developer mailing list and list of developers.</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-todos.html" class="wikilink1" title="geda-todos.html">Todos</a> : For developers only: lists of pending project enhancements and todos.</div>
</li>
-<li class="level1"><div class="li"> <a href="geda_devel-tips.html" class="wikilink1" title="geda:devel-tips">devel-tips</a> : For developers only: various tips and tricks when doing gEDA development.</div>
+<li class="level1"><div class="li"> <a href="geda-tasks.html" class="wikilink1" title="geda-tasks.html">Tasks</a> : Top-level list of jobs/tasks that need help.</div>
</li>
-<li class="level1"><div class="li"> <a href="geda_release_engineering.html" class="wikilink1" title="geda:release_engineering">Release Engineering</a> : Description of various Release Engineering procedures </div>
+<li class="level1"><div class="li"> <a href="geda-scm.html" class="wikilink1" title="geda-scm.html">SCM</a> : Information on gEDA/gafâ??s source control management (SCM) system and process.</div>
</li>
-<li class="level1"><div class="li"> <a href="geda_tasks.html" class="wikilink1" title="geda:tasks">Tasks</a> : Top-level list of jobs/tasks that need help.</div>
+<li class="level1"><div class="li"> <a href="geda-release_engineering.html" class="wikilink1" title="geda-release_engineering.html">Release Engineering</a> : Description of various Release Engineering procedures.</div>
</li>
-<li class="level1"><div class="li"> <a href="geda_scm.html" class="wikilink1" title="geda:scm">scm</a> : Information on gEDA/gafâ??s source control management (SCM) system and process.</div>
+<li class="level1"><div class="li"> <a href="geda-devel-tips.html" class="wikilink1" title="geda-devel-tips.html">devel-tips</a> : For developers only: various tips and tricks when doing gEDA development.</div>
+</li>
+</ul>
+
+<p>
+ The following pages are work-in-progress discussions and/or brainstorming:
+</p>
+<ul>
+<li class="level1"><div class="li"> <a href="libgeda3.html" class="wikilink1" title="libgeda3.html">libgeda3</a> : For developers only: Discussion of <acronym title="Application Programming Interface">API</acronym> and design for a next generation libgeda.</div>
</li>
-<li class="level1"><div class="li"> <a href="geda_todos.html" class="wikilink1" title="geda:todos">ToDos</a> : For developers only: lists of pending project enhancements and to-dos.</div>
+<li class="level1"><div class="li"> <a href="geda-circuit_simulation_improvements.html" class="wikilink1" title="geda-circuit_simulation_improvements.html">Circuit Simulation Improvements</a> : For developers only: Discussion on how to better integrate circuit simulations, gschem and gnetlist.</div>
</li>
-<li class="level1"><div class="li"> <a href="libgeda3.html" class="wikilink1" title="libgeda3">libgeda3</a> : For developers only: Discussion of <acronym title="Application Programming Interface">API</acronym> and design for a next generation libgeda.</div>
+<li class="level1"><div class="li"> <a href="geda-data_plotting_improvements.html" class="wikilink1" title="geda-data_plotting_improvements.html">Data Plotting Improvements</a> : For developers only: Discussion on how to better plot simulation data.</div>
</li>
-<li class="level1"><div class="li"> <a href="geda_circuit_simulation_improvements.html" class="wikilink1" title="geda:circuit_simulation_improvements">Circuit Simulation Improvements</a> : For developers only: Discussion on how to better integrate circuit simulations, gschem and gnetlist.</div>
+<li class="level1"><div class="li"> <a href="geda-design_flow_and_hierarchy_roadmap.html" class="wikilink1" title="geda-design_flow_and_hierarchy_roadmap.html">Design Flow and Hierarchy Roadmap</a> : For users and developers: Discussion of wants for circuit design, reusing modules in a hierarchy.</div>
</li>
-<li class="level1"><div class="li"> <a href="geda_data_plotting_improvements.html" class="wikilink1" title="geda:data_plotting_improvements">Data Plotting Improvements</a> : For developers only: Discussion on how to better plot simulation data.</div>
+<li class="level1"><div class="li"> <a href="geda-pcb_funding_sow.html" class="wikilink1" title="geda-pcb_funding_sow.html"> PCB Funding SOW</a> : An SOW specifying improvements to PCB performed within a funding program.</div>
</li>
-<li class="level1"><div class="li"> <a href="geda_design_flow_and_hierarchy_roadmap.html" class="wikilink1" title="geda:design_flow_and_hierarchy_roadmap">Design Flow and Hierarchy Roadmap</a> : For users and developers: Discussion of wants for circuit design, reusing modules in a hierarchy.</div>
+<li class="level1"><div class="li"> <a href="geda-format_translation.html" class="wikilink1" title="geda-format_translation.html">format translation</a> : Some notes on file format translation.</div>
</li>
</ul>
</div>
-<!-- SECTION "Developer Documentation" [2985-4163] -->
+<!-- SECTION "Developer Documentation" [2987-4465] -->
<h2><a name="talks" id="talks">Talks</a></h2>
<div class="level2">
@@ -163,42 +162,54 @@ These are slides of presentations done about gEDA. They provide a good top-leve
</ul>
</div>
-<!-- SECTION "Talks" [4164-4406] -->
+<!-- SECTION "Talks" [4466-4706] -->
<h2><a name="google_summer_of_code" id="google_summer_of_code">Google Summer of Code</a></h2>
<div class="level2">
<p>
- The gEDA project participated in the Google Summer of Code for the following years:
+ The gEDA project regularly participates in the Google Summer of Code. The gEDA project was not accepted into GSoC 2009, hopefully we will do better next year.
+</p>
+
+<p>
+Here is this yearâ??s Google Summer of Code page:
+</p>
+<ul>
+<li class="level1"><div class="li"> <a href="gsoc2009.html" class="wikilink1" title="gsoc2009.html">2009</a></div>
+</li>
+</ul>
+
+<p>
+ Here are archived instructions and ideas from previous years:
</p>
<ul>
-<li class="level1"><div class="li"> <a href="gsoc2007.html" class="wikilink1" title="gsoc2007">2007</a></div>
+<li class="level1"><div class="li"> <a href="gsoc2007.html" class="wikilink1" title="gsoc2007.html">2007</a></div>
</li>
-<li class="level1"><div class="li"> <a href="gsoc2008.html" class="wikilink1" title="gsoc2008">2008</a></div>
+<li class="level1"><div class="li"> <a href="gsoc2008.html" class="wikilink1" title="gsoc2008.html">2008</a></div>
</li>
</ul>
</div>
-<!-- SECTION "Google Summer of Code" [4407-4574] -->
+<!-- SECTION "Google Summer of Code" [4707-5086] -->
<h2><a name="translations" id="translations">Translations</a></h2>
<div class="level2">
<ul>
-<li class="level1"><div class="li"> En français, cela débute <a href="start_fr.html" class="wikilink1" title="start_fr">ici</a>.</div>
+<li class="level1"><div class="li"> En français, cela débute <a href="start_fr.html" class="wikilink1" title="start_fr.html">ici</a>.</div>
</li>
-<li class="level1"><div class="li"> Spanish language <a href="start_es.html" class="wikilink1" title="start_es">links</a></div>
+<li class="level1"><div class="li"> Spanish language <a href="start_es.html" class="wikilink1" title="start_es.html">links</a></div>
</li>
</ul>
</div>
-<!-- SECTION "Translations" [4575-4690] -->
+<!-- SECTION "Translations" [5087-5203] -->
<h2><a name="geda_users" id="geda_users">gEDA Users</a></h2>
<div class="level2">
<p>
-Users may discuss development, help, installation, and working tips thru the mailing lists at geda.seul.org. <a href="http://geda.seul.org/mailinglist/index.html"; class="urlextern" title="http://geda.seul.org/mailinglist/index.html"; rel="nofollow">Mailing lists</a>.
+Users may discuss development, help, installation, and working tips through the <a href="http://www.gpleda.org/mailinglists.html"; class="urlextern" title="http://www.gpleda.org/mailinglists.html"; rel="nofollow">mailing lists</a>.
</p>
<p>
-There is also a gEDA <acronym title="Internet Relay Chat">IRC</acronym> channel at irc.seul.org/6667 on the #geda channel. Sometimes this channel is full of activity and sometimes it is quite silent. Please be patient when asking questions in the irc channel.
+There is also a gEDA <acronym title="Internet Relay Chat">IRC</acronym> channel at <strong>irc.seul.org/6667</strong> on the <strong>#geda</strong> channel. Sometimes this channel is full of activity and sometimes it is quite silent. Please be patient when asking questions in the <acronym title="Internet Relay Chat">IRC</acronym> channel.
</p>
<p>
@@ -206,7 +217,7 @@ The so-called â??Free Dogâ?? organization ( <a href="http://freeedaug.org/"; clas
</p>
</div>
-<!-- SECTION "gEDA Users" [4691-5248] -->
+<!-- SECTION "gEDA Users" [5204-5736] -->
<h2><a name="about_this_wiki" id="about_this_wiki">About this Wiki</a></h2>
<div class="level2">
@@ -215,10 +226,9 @@ This section of the gEDA website is dedicated to documentation that is contribut
</p>
<p>
-Anyone is welcome to contribute. Unlike wikipedia there is no button to create a login by yourself. This is because nobody at the gEDA site has the nerves to deal with anonymous vandalism. Consequently, you have to write an email to the site admin (ahvezda AT geda.seul.org) to gain access. He will gladly send you a login.
+Anyone is welcome to contribute. Unlike Wikipedia there is no button to create a login by yourself. This is because nobody at the gEDA site has the nerves to deal with anonymous vandalism. Consequently, you have to write an email to the site admin (ahvezda AT geda.seul.org) to gain access. He will gladly send you a login.
</p>
</div>
-<!-- SECTION "About this Wiki" [5249-] --></div>
-</body>
+<!-- SECTION "About this Wiki" [5737-] --></body>
</html>
diff --git a/docs/wiki/lib/.gitignore b/docs/wiki/lib/.gitignore
deleted file mode 100644
index 23c1897..0000000
--- a/docs/wiki/lib/.gitignore
+++ /dev/null
@@ -1,3 +0,0 @@
-Makefile
-Makefile.in
-*~
diff --git a/docs/wiki/lib/Makefile.am b/docs/wiki/lib/Makefile.am
deleted file mode 100644
index 928bc60..0000000
--- a/docs/wiki/lib/Makefile.am
+++ /dev/null
@@ -1,13 +0,0 @@
-
-
-docname=wiki
-docsdir = $(docdir)/$(docname)/lib
-
-SUBDIRS = exe tpl images plugins
-
-docs_DATA =
-
-EXTRA_DIST = $(docs_DATA)
-
-MAINTAINERCLEANFILES = *.log core FILE *~ Makefile.in
-
diff --git a/docs/wiki/lib/exe/.gitignore b/docs/wiki/lib/exe/.gitignore
deleted file mode 100644
index 23c1897..0000000
--- a/docs/wiki/lib/exe/.gitignore
+++ /dev/null
@@ -1,3 +0,0 @@
-Makefile
-Makefile.in
-*~
diff --git a/docs/wiki/lib/exe/001css b/docs/wiki/lib/exe/001css
deleted file mode 100644
index a090af9..0000000
--- a/docs/wiki/lib/exe/001css
+++ /dev/null
@@ -1 +0,0 @@
-a.interwiki{background:transparent url('../images/interwiki.png') 0px 1px no-repeat;padding-left:16px;}a.iw_wp{background-image:url('../images/interwiki/wp.gif')}a.iw_wpde{background-image:url('../images/interwiki/wpde.gif')}a.iw_wpmeta{background-image:url('../images/interwiki/wpmeta.gif')}a.iw_doku{background-image:url('../images/interwiki/doku.gif')}a.iw_sb{background-image:url('../images/interwiki/sb.gif')}a.iw_amazon{background-image:url('../images/interwiki/amazon.gif')}a.iw_amazon_de{background-image:url('../images/interwiki/amazon.de.gif')}a.iw_amazon_uk{background-image:url('../images/interwiki/amazon.uk.gif')}a.iw_phpfn{background-image:url('../images/interwiki/phpfn.gif')}a.iw_dokubug{background-image:url('../images/interwiki/dokubug.gif')}a.iw_coral{background-image:url('../images/interwiki/coral.gif')}a.iw_google{background-image:url('../images/interwiki/google.gif')}a.iw_meatball{background-image:url('../images/interwiki/meatball.gif')}a.iw_wiki{background-image:url('../images/interwiki/wiki.gif')}a.mediafile{background:transparent url('../images/fileicons/file.png') 0px 1px no-repeat;padding-left:18px;padding-bottom:1px;}a.mf_jpg{background-image:url('../images/fileicons/jpg.png')}a.mf_jpeg{background-image:url('../images/fileicons/jpeg.png')}a.mf_gif{background-image:url('../images/fileicons/gif.png')}a.mf_png{background-image:url('../images/fileicons/png.png')}a.mf_tgz{background-image:url('../images/fileicons/tgz.png')}a.mf_tar{background-image:url('../images/fileicons/tar.png')}a.mf_gz{background-image:url('../images/fileicons/gz.png')}a.mf_zip{background-image:url('../images/fileicons/zip.png')}a.mf_rar{background-image:url('../images/fileicons/rar.png')}a.mf_pdf{background-image:url('../images/fileicons/pdf.png')}a.mf_ps{background-image:url('../images/fileicons/ps.png')}a.mf_doc{background-image:url('../images/fileicons/doc.png')}a.mf_xls{background-image:url('../images/fileicons/xls.png')}a.mf_ppt{background-image:url('../images/fileicons/ppt.png')}a.mf_rtf{background-image:url('../images/fileicons/rtf.png')}a.mf_swf{background-image:url('../images/fileicons/swf.png')}a.mf_rpm{background-image:url('../images/fileicons/rpm.png')}a.mf_deb{background-image:url('../images/fileicons/deb.png')}a.mf_sxw{background-image:url('../images/fileicons/sxw.png')}a.mf_sxc{background-image:url('../images/fileicons/sxc.png')}a.mf_sxi{background-image:url('../images/fileicons/sxi.png')}a.mf_sxd{background-image:url('../images/fileicons/sxd.png')}a.mf_odc{background-image:url('../images/fileicons/odc.png')}a.mf_odf{background-image:url('../images/fileicons/odf.png')}a.mf_odg{background-image:url('../images/fileicons/odg.png')}a.mf_odi{background-image:url('../images/fileicons/odi.png')}a.mf_odp{background-image:url('../images/fileicons/odp.png')}a.mf_ods{background-image:url('../images/fileicons/ods.png')}a.mf_odt{background-image:url('../images/fileicons/odt.png')}a.mf_src{background-image:url('../images/fileicons/src.png')}div.clearer{clear:both;line-height:0px;height:0;overflow:hidden;}div.no{display:inline;margin:0;padding:0;}.hidden{display:none;}div.error{background:#fcc url('../images/error.png') 0.5em 0px no-repeat;color:#000;border-bottom:1px solid #faa;font-size:90%;margin:0;padding-left:3em;overflow:hidden;}div.info{background:#ccf url('../images/info.png') 0.5em 0px no-repeat;color:#000;border-bottom:1px solid #aaf;font-size:90%;margin:0;padding-left:3em;overflow:hidden;}div.success{background:#cfc url('../images/success.png') 0.5em 0px no-repeat;color:#000;border-bottom:1px solid #afa;font-size:90%;margin:0;padding-left:3em;overflow:hidden;}div.notify{background:#ffc url('../images/notify.png') 0.5em 0px no-repeat;color:#000;border-bottom:1px solid #ffa;font-size:90%;margin:0;padding-left:3em;overflow:hidden;}.medialeft{float:left;}.mediaright{float:right;}.mediacenter{display:block;margin-left:auto;margin-right:auto;}.leftalign{text-align:left;}.centeralign{text-align:center;}.rightalign{text-align:right;}em.u{font-style:normal;text-decoration:underline;}em em.u{font-style:italic;}.code .br0{color:#6c6;}.code .co1{color:#808080;font-style:italic;}.code .co2{color:#808080;font-style:italic;}.code .coMULTI{color:#808080;font-style:italic;}.code .es0{color:#009;font-weight:bold;}.code .kw1{color:#b1b100;}.code .kw2{color:#000;font-weight:bold;}.code .kw3{color:#006;}.code .kw4{color:#933;}.code .kw5{color:#00f;}.code .me0{color:#060;}.code .nu0{color:#c6c;}.code .re0{color:#00f;}.code .re1{color:#00f;}.code .re2{color:#00f;}.code .re4{color:#099;}.code .sc0{color:#0bd;}.code .sc1{color:#db0;}.code .sc2{color:#090;}.code .st0{color:#f00;}div.dokuwiki div#spell__suggest{position:absolute;left:0;top:0;display:none;z-index:2;}div.dokuwiki div#spell__result{display:none;font-family:monospace;overflow:auto;z-index:1;}#acl__manager label{text-align:left;font-weight:normal;display:inline;}#acl__manager table{margin-left:10%;width:80%;}#config__manager div.success,#config__manager div.error,#config__manager div.info{background-position:0.5em;padding:0.5em;text-align:center;}#config__manager fieldset{margin:1em;width:auto;margin-bottom:2em;background-color:#F8F8F8;color:#000;padding:0 1em;}#config__manager legend{font-size:1.25em;}#config__manager form{}#config__manager table{margin:1em 0;width:100%;}#config__manager fieldset td{text-align:left;}#config__manager fieldset td.value{width:30em;}#config__manager td input.edit{width:30em;}#config__manager td select.edit{}#config__manager td textarea.edit{width:27.5em;height:4em;}#config__manager tr .input,#config__manager tr input,#config__manager tr textarea,#config__manager tr select{background-color:#fff;color:#000;}#config__manager tr.default .input,#config__manager tr.default input,#config__manager tr.default textarea,#config__manager tr.default select,#config__manager .selectiondefault{background-color:#cdf;color:#000;}#config__manager tr.protected .input,#config__manager tr.protected input,#config__manager tr.protected textarea,#config__manager tr.protected select,#config__manager tr.protected .selection{background-color:#fcc!important;color:#000 !important;}#config__manager td.error{background-color:red;color:#000;}#config__manager .selection{width:14.8em;float:left;margin:0 0.3em 2px 0;}#config__manager .selection label{float:right;width:14em;font-size:90%;}* html #config__manager .selection label{padding-top:2px;}#config__manager .selection input.checkbox{padding-left:0.7em;}#config__manager .other{clear:both;padding-top:0.5em;}#config__manager .other label{padding-left:2px;font-size:90%;}#plugin__manager{}#plugin__manager h2{margin-left:0;}#plugin__manager form{display:block;margin:0;padding:0;}#plugin__manager legend{display:none;}#plugin__manager fieldset{width:auto;}#plugin__manager .button{margin:0;}#plugin__manager p,#plugin__manager label{text-align:left;}#plugin__manager .hidden{display:none;}#plugin__manager .new{background:#dee7ec;}#plugin__manager input[disabled]{color:#ccc;border-color:#ccc;}#plugin__manager .pm_menu,#plugin__manager .pm_info{margin-left:0;text-align:left;}#plugin__manager .pm_menu{float:left;width:48%;}#plugin__manager .pm_info{float:right;width:50%;}#plugin__manager .common{}#plugin__manager .common form{}#plugin__manager .common fieldset{margin:0;padding:0 0 1.0em 0;text-align:left;border:none;}#plugin__manager .common label{padding:0 0 0.5em 0;}#plugin__manager .common input{}#plugin__manager .common input.edit{width:24em;margin:0.5em;}#plugin__manager .common .button{}#plugin__manager form.plugins{}#plugin__manager .plugins fieldset{color:#000;background:#fff;text-align:right;border-top:none;border-right:none;border-left:none;}#plugin__manager .plugins fieldset.protected{background:#fdd;color:#000;}#plugin__manager .plugins fieldset.disabled{background:#e0e0e0;color:#a8a8a8;}#plugin__manager .plugins .legend{color:#000;background:inherit;display:block;margin:0;padding:0;font-size:1em;line-height:1.4em;font-weight:normal;text-align:left;float:left;padding:0;clear:none;}#plugin__manager .plugins .button{font-size:95%;}#plugin__manager .plugins fieldset.buttons{border:none;}#plugin__manager .plugins fieldset.buttons .button{float:left;}#plugin__manager .pm_info h3{margin-left:0;}#plugin__manager .pm_info dl{margin:1em 0;padding:0;}#plugin__manager .pm_info dt{width:6em;float:left;clear:left;margin:0;padding:0;}#plugin__manager .pm_info dd{margin:0 0 0 7em;padding:0;background:none;}#plugin__manager .plugins .enable{float:left;width:auto;margin-right:0.5em;}#user__manager tr.disabled{color:#6f6f6f;background:#e4e4e4;}#user__manager tr.user_info{vertical-align:top;}#user__manager div.edit_user{width:46%;float:left;}#user__manager table{margin-bottom:1em;}#user__manager input.button[disabled]{color:#ccc!important;border-color:#ccc!important;}dl,dt,dd{margin:0;padding:0}dl{font-size:90%;padding-top:1px;}html>body dl{padding-bottom:0.5em;border-bottom:1px dashed #e0e0e0;}dl:after{content:'.';display:block;clear:both;height:0;visibility:hidden;}dt{clear:left;margin-top:0.5em;}dt+dt{margin-top:0;}dd+dt{border-top:1px dashed #e0e0e0;padding-top:0.5em;}dt span.term{float:left;width:10em;}dd{margin-left:10.3em;padding-left:0.8em;background:url('../plugins/definitionlist/images/bullet.gif') no-repeat 0 0.4em;}dd p{margin:0;padding:0;}* html dl{height:1px;}#plugin_manager dd{background-image:none;}.hilited{background-color:#ff0;}.noteclassic,.noteimportant,.notewarning,.notetip{margin:2em;margin-left:auto;margin-right:auto;width:70% !important;min-height:40px;clear:both;text-align:justify;vertical-align:middle;border-collapse:collapse;padding:15px 20px 15px 80px;background-position:20px 50%;background-repeat:no-repeat;-moz-border-radius:20px;-khtml-border-radius:20px;border-radius:20px;}.noteclassic{background-color:#eef;background-image:url('../plugins/note/images/note.png');}.noteimportant{background-color:#ffc;background-image:url('../plugins/note/images/important.png');}.notewarning{background-color:#fdd;background-image:url('../plugins/note/images/warning.png');}.notetip{background-color:#dfd;background-image:url('../plugins/note/images/tip.png');}div.dokuwiki .header{}div.dokuwiki .pagename{float:left;font-size:150%;color:#F8F8F8;z-index:20;}div.dokuwiki .pagename a{color:#00B !important;text-decoration:none !important;}div.dokuwiki .logo{float:right;font-size:220%;font-weight:bolder;text-align:right;vertical-align:middle;}div.dokuwiki .logo a{color:#F8F8F8 !important;text-decoration:none !important;font-variant:small-caps;letter-spacing:2pt;}div.dokuwiki .nav{width:100%;}div.dokuwiki .navavoid{width:1px;height:5px;}div.dokuwiki .nav ul{position:relative;top:2px;right:5px;width:100%;font-size:100%;z-index:10;padding:0px;margin:0px;text-align:right;line-height:1.2;}div.dokuwiki .navundertext{position:relative;top:-30px;height:50px;width:100%;}div.dokuwiki .navlogo{position:absolute;width:266px;height:73px;padding:0px;border:0px;margin:0px;z-index:1;}div.dokuwiki .navrule{position:absolute;left:0px;width:100%;height:2px;top:35px;padding:0px;margin:0px;border-top:2px solid #00F;z-index:0;}div.dokuwiki .nav h1{position:absolute;top:5px;left:10px;z-index:2;margin:0px;padding:0px;font-size:18pt;text-align:left;}div.dokuwiki .nav h2{position:absolute;top:7px;left:84px;z-index:2;margin:0px;padding:0px;font-size:70%;text-align:left;color:#A0A0A0;}div.dokuwiki .nav h3{position:absolute;top:40px;width:100%;right:5px;font-size:100%;z-index:10;padding:0px;margin:0px;text-align:right;}div.dokuwiki .nav img{border:none;}div.dokuwiki .nav li{display:inline;font-family:sans-serif;margin-right:0em;margin-left:0em;color:#000;text-decoration:none;font-weight:bold;}div.dokuwiki .nav a{text-decoration:none;font-weight:normal;color:#00B;}div.dokuwiki .nav a:visited{color:#551a8b;}div.dokuwiki .nav a:active{color:#F00;}div.dokuwiki .nav a:hover{color:#F00;}div.dokuwiki .bar{background:#F8F8F8;padding:0.1em 0.15em;clear:both;}div.dokuwiki .bar-left{float:left;}div.dokuwiki .bar-right{float:right;text-align:right;}div.dokuwiki #bar__bottom{margin-bottom:3px;}div.dokuwiki div.meta{clear:both;margin-top:1em;color:#638c9c;font-size:70%;}div.dokuwiki div.meta div.user{float:left;}div.dokuwiki div.meta div.doc{text-align:right;}*{padding:0;margin:0;}body{font-family:sans-serif;background-color:#f8f8f8;color:#000;}div.dokuwiki div.page{margin:4px 2em 0 1em;text-align:justify;}div.dokuwiki table{font-size:100%;}div.dokuwiki tr,div.dokuwiki td,div.dokuwiki th{}div.dokuwiki img{border:0;}div.dokuwiki p,div.dokuwiki blockquote,div.dokuwiki table,div.dokuwiki pre{margin:0 0 1.0em 0;}div.dokuwiki hr{border:0px;border-top:1px solid #8cacbb;text-align:center;height:0px;}div.dokuwiki div.nothing{text-align:center;margin:2em;}div.dokuwiki form{border:none;display:inline;}div.dokuwiki label.block{display:block;text-align:right;font-weight:bold;}div.dokuwiki label.simple{display:block;text-align:left;font-weight:normal;}div.dokuwiki label.block input.edit{width:50%;}div.dokuwiki fieldset{width:300px;text-align:center;border:1px solid #8cacbb;padding:0.5em;margin:auto;}div.dokuwiki textarea.edit{font-family:monospace;font-size:14px;color:#000;background-color:#f8f8f8;border:1px solid #8cacbb;padding:0.3em 0 0 0.3em;width:100%;}html>body div.dokuwiki textarea.edit{background:#f8f8f8 url('../tpl/geda/images/inputshadow.png') repeat-x top;}div.dokuwiki input.edit,div.dokuwiki select.edit{font-size:100%;border:1px solid #8cacbb;color:#000;background-color:#f8f8f8;vertical-align:middle;margin:1px;display:inline;}html>body div.dokuwiki input.edit,html>body div.dokuwiki select.edit{}div.dokuwiki select.edit{padding:0.1em 0;}div.dokuwiki input.missing{font-size:100%;border:1px solid #8cacbb;color:#000;background-color:#fcc;vertical-align:middle;margin:1px;padding:0.20em 0.3em;display:inline;}div.dokuwiki textarea.edit[disabled],div.dokuwiki textarea.edit[readonly],div.dokuwiki input.edit[disabled],div.dokuwiki input.edit[readonly],div.dokuwiki select.edit[disabled]{background-color:#F8F8F8!important;color:#666!important;}div.dokuwiki div.toolbar,div.dokuwiki div#wiki__editbar{margin:2px 0;text-align:left;}div.dokuwiki div#size__ctl{float:right;width:60px;height:2.7em;}div.dokuwiki #size__ctl img{cursor:pointer;}div.dokuwiki div#wiki__editbar div.editButtons{float:left;padding:0 1.0em 0.7em 0;}div.dokuwiki div#wiki__editbar div.summary{float:left;}div.dokuwiki .nowrap{white-space:nowrap;}div.dokuwiki div#draft__status{float:right;color:#638c9c;}div.dokuwiki input.button,div.dokuwiki button.button{border:1px solid #8cacbb;color:#000;background-color:#f8f8f8;vertical-align:middle;text-decoration:none;font-size:80%;cursor:pointer;margin:1px;padding:0.125em 0.4em;}html>body div.dokuwiki input.button,html>body div.dokuwiki button.button{}* html div.dokuwiki input.button,* html div.dokuwiki button.button{height:1.8em;}div.dokuwiki div.secedit input.button{border:1px solid #8cacbb;color:#000;background-color:#f8f8f8;vertical-align:middle;text-decoration:none;margin:0;padding:0;font-size:10px;cursor:pointer;float:right;display:inline;}div.dokuwiki div.pagenav{margin:1em 0 0 0;}div.dokuwiki div.pagenav-prev{text-align:right;float:left;width:49%}div.dokuwiki div.pagenav-next{text-align:left;float:right;width:49%}div.dokuwiki a:link,div.dokuwiki a:visited{color:#00B;text-decoration:none;}div.dokuwiki a:hover,div.dokuwiki a:active{color:#000;text-decoration:underline;}div.dokuwiki h1 a,div.dokuwiki h2 a,div.dokuwiki h3 a,div.dokuwiki h4 a,div.dokuwiki h5 a,div.dokuwiki a.nolink{color:#000 !important;text-decoration:none !important;}div.dokuwiki a.urlextern{background:transparent url('../tpl/geda/images/link_icon.gif') 0px 1px no-repeat;padding:1px 0px 1px 16px;}div.dokuwiki a.windows{background:transparent url('../tpl/geda/images/windows.gif') 0px 1px no-repeat;padding:1px 0px 1px 16px;}div.dokuwiki a.interwiki{}div.dokuwiki a.media{}div.dokuwiki a.urlextern:link,div.dokuwiki a.windows:link,div.dokuwiki a.interwiki:link{color:#00B;}div.dokuwiki a.urlextern:visited,div.dokuwiki a.windows:visited,div.dokuwiki a.interwiki:visited{color:purple;}div.dokuwiki a.urlextern:hover,div.dokuwiki a.urlextern:active,div.dokuwiki a.windows:hover,div.dokuwiki a.windows:active,div.dokuwiki a.interwiki:hover,div.dokuwiki a.interwiki:active{color:#000;}div.dokuwiki a.mail{background:transparent url('../tpl/geda/images/mail_icon.gif') 0px 1px no-repeat;padding:1px 0px 1px 16px;}div.dokuwiki a.wikilink1{color:#00B !important;}div.dokuwiki a.wikilink2{color:#f30 !important;text-decoration:none !important;border-bottom:dashed 1px #f30 !important;}div.dokuwiki div.preview{background-color:#F8F8F8;margin:0 0 0 2em;padding:4px;border:1px dashed #000;}div.dokuwiki div.breadcrumbs{font-size:100%;padding:0 8px 0px 4px;}div.dokuwiki span.user{color:#ccc;font-size:90%;}div.dokuwiki li.minor{color:#666;font-style:italic;}div.dokuwiki img.media{margin:3px;}div.dokuwiki img.medialeft{border:0;float:left;margin:0 1.5em 0 0;}div.dokuwiki img.mediaright{border:0;float:right;margin:0 0 0 1.5em;}div.dokuwiki img.mediacenter{border:0;display:block;margin:0 auto;}div.dokuwiki img.middle{vertical-align:middle;}div.dokuwiki acronym{cursor:help;border-bottom:1px dotted #000;}div.dokuwiki h1,div.dokuwiki h2,div.dokuwiki h3,div.dokuwiki h4,div.dokuwiki h5{color:#000;background-color:inherit;font-size:100%;font-weight:normal;margin:0 0 1em 0;padding:0.5em 0 0 0;border-bottom:1px solid #8cacbb;clear:left;}div.dokuwiki h1{font-size:160%;margin-left:0px;font-weight:bold;}div.dokuwiki h2{font-size:150%;margin-left:20px;}div.dokuwiki h3{font-size:140%;margin-left:40px;border-bottom:none;font-weight:bold;}div.dokuwiki h4{font-size:120%;margin-left:60px;border-bottom:none;font-weight:bold;}div.dokuwiki h5{font-size:100%;margin-left:80px;border-bottom:none;font-weight:bold;}div.dokuwiki div.level1{margin-left:3px;}div.dokuwiki div.level2{margin-left:23px;}div.dokuwiki div.level3{margin-left:43px;}div.dokuwiki div.level4{margin-left:63px;}div.dokuwiki div.level5{margin-left:83px;}div.dokuwiki ul{line-height:1.5em;list-style-type:square;list-style-image:none;margin:0 0 0.5em 1.5em;color:#638c9c;}div.dokuwiki ol{line-height:1.5em;list-style-image:none;margin:0 0 0.5em 1.5em;color:#638c9c;font-weight:bold;}div.dokuwiki .li{color:#000;font-weight:normal;}div.dokuwiki ol{list-style-type:decimal}div.dokuwiki ol ol{list-style-type:upper-roman}div.dokuwiki ol ol ol{list-style-type:lower-alpha}div.dokuwiki ol ol ol ol{list-style-type:lower-greek}div.dokuwiki li.open{list-style-image:url('../tpl/geda/images/open.gif');}div.dokuwiki li.closed{list-style-image:url('../tpl/geda/images/closed.gif');}div.dokuwiki blockquote{border-left:2px solid #8cacbb;padding-left:3px;}div.dokuwiki pre{font-size:120%;padding:0.5em;border:1px dashed #8cacbb;color:#000;overflow:auto;}div.dokuwiki pre.pre{background-color:#f7f9fa;}div.dokuwiki pre.code{background-color:#f7f9fa;}div.dokuwiki code{font-size:120%;}div.dokuwiki pre.file{background-color:#F8F8F8;}div.dokuwiki table.inline{background-color:#f8f8f8;border-spacing:0px;border-collapse:collapse;}div.dokuwiki table.inline th{padding:3px;border:1px solid #8cacbb;background-color:#F8F8F8;}div.dokuwiki table.inline td{padding:3px;border:1px solid #8cacbb;}div.dokuwiki div.toc{margin:1.2em 0 0 2em;float:right;width:200px;font-size:80%;clear:both;}div.dokuwiki div.tocheader{border:1px solid #8cacbb;background-color:#F8F8F8;text-align:left;font-weight:bold;padding:3px;margin-bottom:2px;}div.dokuwiki span.toc_open,div.dokuwiki span.toc_close{border:0.4em solid #F8F8F8;float:right;display:block;margin:0.4em 3px 0 0;}div.dokuwiki span.toc_open span,div.dokuwiki span.toc_close span{display:none;}div.dokuwiki span.toc_open{margin-top:0.4em;border-top:0.4em solid #000;}div.dokuwiki span.toc_close{margin-top:0;border-bottom:0.4em solid #000;}div.dokuwiki #toc__inside{border:1px solid #8cacbb;background-color:#FFF;text-align:left;padding:0.5em 0 0.7em 0;}div.dokuwiki ul.toc{list-style-type:none;list-style-image:none;line-height:1.2em;padding-left:1em;margin:0;}div.dokuwiki ul.toc li{background:transparent url('../tpl/geda/images/tocdot2.gif') 0 0.6em no-repeat;padding-left:0.4em;}div.dokuwiki ul.toc li.clear{background-image:none;padding-left:0.4em;}div.dokuwiki a.toc:link,div.dokuwiki a.toc:visited{color:#00B;}div.dokuwiki a.toc:hover,div.dokuwiki a.toc:active{color:#000;}div.dokuwiki table.diff{background-color:#f8f8f8;width:100%;}div.dokuwiki td.diff-blockheader{font-weight:bold;}div.dokuwiki table.diff th{border-bottom:1px solid #8cacbb;font-size:120%;width:50%;font-weight:normal;text-align:left;}div.dokuwiki table.diff td{font-family:monospace;font-size:100%;}div.dokuwiki td.diff-addedline{background-color:#dfd;}div.dokuwiki td.diff-deletedline{background-color:#ffb;}div.dokuwiki td.diff-context{background-color:#F8F8F8;}div.dokuwiki table.diff td.diff-addedline strong,div.dokuwiki table.diff td.diff-deletedline strong{color:red;}div.dokuwiki div.footnotes{clear:both;border-top:1px solid #8cacbb;padding-left:1em;margin-top:1em;}div.dokuwiki div.fn{font-size:90%;}div.dokuwiki a.fn_top{vertical-align:super;font-size:80%;}div.dokuwiki a.fn_bot{vertical-align:super;font-size:80%;font-weight:bold;}div.insitu-footnote{font-size:80%;line-height:1.2em;border:1px solid #8cacbb;background-color:#f7f9fa;text-align:left;padding:4px;max-width:40%;}* html .insitu-footnote pre.code,* html .insitu-footnote pre.file{padding-bottom:18px;}div.dokuwiki .search_result{margin-bottom:6px;padding:0 10px 0 30px;}div.dokuwiki .search_snippet{color:#ccc;font-size:12px;margin-left:20px;}div.dokuwiki .search_sep{color:#000;}div.dokuwiki .search_hit{color:#000;background-color:#ff9;}div.dokuwiki strong.search_hit{font-weight:normal;}div.dokuwiki div.search_quickresult{margin:0 0 15px 30px;padding:0 10px 10px 0;border-bottom:1px dashed #8cacbb;}div.dokuwiki div.search_quickresult h3{margin:0 0 1.0em 0;font-size:1em;font-weight:bold;}div.dokuwiki ul.search_quickhits{margin:0 0 0.5em 1.0em;}div.dokuwiki ul.search_quickhits li{margin:0 1.0em 0 1.0em;float:left;width:30%;}div.footerinc{text-align:center;}.footerinc a img{opacity:0.5;border:0;}.footerinc a:hover img{opacity:1;}div.dokuwiki div.ajax_qsearch{position:absolute;right:237px;;width:200px;opacity:0.9;display:none;font-size:80%;line-height:1.2em;border:1px solid #8cacbb;background-color:#f7f9fa;text-align:left;padding:4px;}button.toolbutton{background-color:#f8f8f8;padding:0px;margin:0 1px 0 0;border:1px solid #8cacbb;cursor:pointer;}html>body button.toolbutton{background:#f8f8f8 url('../tpl/geda/images/buttonshadow.png') repeat-x bottom;}div.picker{width:250px;border:1px solid #8cacbb;background-color:#F8F8F8;}button.pickerbutton{padding:0px;margin:0 1px 1px 0;border:0;background-color:transparent;font-size:80%;cursor:pointer;}div.dokuwiki a.spell_error{color:#f00;text-decoration:underline;}div.dokuwiki div#spell__suggest{background-color:#f8f8f8;padding:2px;border:1px solid #000;font-size:80%;display:none;}div.dokuwiki div#spell__result{border:1px solid #8cacbb;color:#000;font-size:14px;padding:3px;background-color:#f7f9fa;display:none;}div.dokuwiki span.spell_noerr{color:#093;}div.dokuwiki span.spell_wait{color:#06c;}div.dokuwiki div.img_big{float:left;margin-right:0.5em;}div.dokuwiki dl.img_tags dt{font-weight:bold;background-color:#F8F8F8;}div.dokuwiki dl.img_tags dd{background-color:#F8F8F8;}div.dokuwiki div.imagemeta{color:#666;font-size:70%;line-height:95%;}div.dokuwiki div.imagemeta img.thumb{float:left;margin-right:0.1em;}#media__manager{height:100%;overflow:hidden;}#media__left{width:30%;border-right:solid 1px #8cacbb;height:100%;overflow:auto;position:absolute;left:0;}#media__right{width:69.7%;height:100%;overflow:auto;position:absolute;right:0;}#media__manager h1{margin:0;padding:0;margin-bottom:0.5em;}#media__tree img{float:left;padding:0.5em 0.3em 0 0;}#media__tree ul{list-style-type:none;list-style-image:none;}#media__tree li{clear:left;list-style-type:none;list-style-image:none;}* html #media__tree li{border:1px solid #f8f8f8;}#media__opts{padding-left:1em;margin-bottom:0.5em;}#media__opts input{float:left;position:absolute;}* html #media__opts input{position:static;}#media__opts label{display:block;float:left;margin-left:30px;}* html #media__opts label{margin-left:10px;}#media__opts br{clear:left;}#media__content img.load{margin:1em auto;}#media__content #scroll__here{border:1px dashed #8cacbb;}#media__content .odd{background-color:#f7f9fa;padding:0.4em;}#media__content .even{padding:0.4em;}#media__content a.mediafile{margin-right:1.5em;font-weight:bold;}#media__content div.detail{padding:0.3em 0 0.3em 2em;}#media__content div.detail div.thumb{float:left;width:130px;text-align:center;margin-right:0.4em;}#media__content img.btn{vertical-align:text-bottom;}#media__content div.example{color:#666;margin-left:1em;}#media__content div.upload{font-size:90%;padding:0 0.5em 0.5em 0.5em;}#media__content form.upload{display:block;border-bottom:solid 1px #8cacbb;padding:0 0.5em 1em 0.5em;}#media__content form.upload fieldset{padding:0;margin:0;border:none;width:auto;}#media__content form.upload p{clear:left;text-align:left;padding:0.25em 0;margin:0;line-height:1.0em;}#media__content form.upload label{float:left;width:30%;}#media__content form.upload label.check{float:none;width:auto;}#media__content form.upload input.check{margin-left:30%;}#media__content form.meta{display:block;padding:0 0 1em 0;}#media__content form.meta label{display:block;width:25%;float:left;font-weight:bold;margin-left:1em;clear:left;}#media__content form.meta .edit{font:100% "Lucida Grande",Verdana,Lucida,Helvetica,Arial,sans-serif;float:left;width:70%;padding-right:0;padding-left:0.2em;margin:2px;}#media__content form.meta textarea.edit{height:8em;}#media__content form.meta div.metafield{clear:left;}#media__content form.meta div.buttons{clear:left;margin-left:20%;padding-left:1em;}
\ No newline at end of file
diff --git a/docs/wiki/lib/exe/002css b/docs/wiki/lib/exe/002css
deleted file mode 100644
index 632fd89..0000000
--- a/docs/wiki/lib/exe/002css
+++ /dev/null
@@ -1 +0,0 @@
-a.interwiki{background:transparent url('../images/interwiki.png') 0px 1px no-repeat;padding-left:16px;}a.iw_wp{background-image:url('../images/interwiki/wp.gif')}a.iw_wpde{background-image:url('../images/interwiki/wpde.gif')}a.iw_wpmeta{background-image:url('../images/interwiki/wpmeta.gif')}a.iw_doku{background-image:url('../images/interwiki/doku.gif')}a.iw_sb{background-image:url('../images/interwiki/sb.gif')}a.iw_amazon{background-image:url('../images/interwiki/amazon.gif')}a.iw_amazon_de{background-image:url('../images/interwiki/amazon.de.gif')}a.iw_amazon_uk{background-image:url('../images/interwiki/amazon.uk.gif')}a.iw_phpfn{background-image:url('../images/interwiki/phpfn.gif')}a.iw_dokubug{background-image:url('../images/interwiki/dokubug.gif')}a.iw_coral{background-image:url('../images/interwiki/coral.gif')}a.iw_google{background-image:url('../images/interwiki/google.gif')}a.iw_meatball{background-image:url('../images/interwiki/meatball.gif')}a.iw_wiki{background-image:url('../images/interwiki/wiki.gif')}a.mediafile{background:transparent url('../images/fileicons/file.png') 0px 1px no-repeat;padding-left:18px;padding-bottom:1px;}a.mf_jpg{background-image:url('../images/fileicons/jpg.png')}a.mf_jpeg{background-image:url('../images/fileicons/jpeg.png')}a.mf_gif{background-image:url('../images/fileicons/gif.png')}a.mf_png{background-image:url('../images/fileicons/png.png')}a.mf_tgz{background-image:url('../images/fileicons/tgz.png')}a.mf_tar{background-image:url('../images/fileicons/tar.png')}a.mf_gz{background-image:url('../images/fileicons/gz.png')}a.mf_zip{background-image:url('../images/fileicons/zip.png')}a.mf_rar{background-image:url('../images/fileicons/rar.png')}a.mf_pdf{background-image:url('../images/fileicons/pdf.png')}a.mf_ps{background-image:url('../images/fileicons/ps.png')}a.mf_doc{background-image:url('../images/fileicons/doc.png')}a.mf_xls{background-image:url('../images/fileicons/xls.png')}a.mf_ppt{background-image:url('../images/fileicons/ppt.png')}a.mf_rtf{background-image:url('../images/fileicons/rtf.png')}a.mf_swf{background-image:url('../images/fileicons/swf.png')}a.mf_rpm{background-image:url('../images/fileicons/rpm.png')}a.mf_deb{background-image:url('../images/fileicons/deb.png')}a.mf_sxw{background-image:url('../images/fileicons/sxw.png')}a.mf_sxc{background-image:url('../images/fileicons/sxc.png')}a.mf_sxi{background-image:url('../images/fileicons/sxi.png')}a.mf_sxd{background-image:url('../images/fileicons/sxd.png')}a.mf_odc{background-image:url('../images/fileicons/odc.png')}a.mf_odf{background-image:url('../images/fileicons/odf.png')}a.mf_odg{background-image:url('../images/fileicons/odg.png')}a.mf_odi{background-image:url('../images/fileicons/odi.png')}a.mf_odp{background-image:url('../images/fileicons/odp.png')}a.mf_ods{background-image:url('../images/fileicons/ods.png')}a.mf_odt{background-image:url('../images/fileicons/odt.png')}a.mf_src{background-image:url('../images/fileicons/src.png')}body{font:10pt "Lucida Grande",Verdana,Lucida,Helvetica,Arial,sans-serif;background-color:White;color:Black;}table{font-size:100%;padding:0;margin:0;}tr,td,th{padding:0;margin:0;}img{border:0}a{color:#000;text-decoration:none;background:none !important;}div.meta{clear:both;margin-top:1em;font-size:70%;text-align:right;}div.notify,div.info,div.success,div.error,div.breadcrumbs,div.secedit{display:none;}a.urlextern:after{content:" [" attr(href) "]";font-size:90%;}a.interwiki:after{content:" [" attr(href) "]";font-size:90%;}a.mail:after{content:" [" attr(href) "]";font-size:90%;}a.wikilink1{text-decoration:underline}div.page{text-align:justify;}h1,h2,h3,h4,h5{color:Black;background-color:transparent;font-family:"Lucida Grande",Verdana,Lucida,Helvetica,Arial,sans-serif;font-size:100%;font-weight:normal;margin-left:0;margin-right:0;margin-top:0;margin-bottom:1em;padding-left:0;padding-right:0;padding-top:0.5em;padding-bottom:0;border-bottom:1px solid #000;clear:left;}h1{font-size:160%;font-weight:bold;}h2{font-size:150%;}h3{font-size:140%;border-bottom:none;}h4{font-size:120%;border-bottom:none;}h5{font-size:100%;border-bottom:none;}img.media{margin:3px;}img.medialeft{border:0;float:left;margin:0 1.5em 0 0;}img.mediaright{border:0;float:right;margin:0 0 0 1.5em;}ul{line-height:1.5em;list-style-type:square;margin:0 0 0.5em 1.5em;padding:0;}ol{line-height:1.5em;margin:0 0 0.5em 2.5em;padding:0;font-weight:normal;}ol ol{margin:0 0 0.5em 1.5em;}div.dokuwiki ol{list-style-type:decimal}div.dokuwiki ol ol{list-style-type:upper-roman}div.dokuwiki ol ol ol{list-style-type:lower-alpha}div.dokuwiki ol ol ol ol{list-style-type:lower-greek}span.li{font-weight:normal;}pre.pre{font-size:8pt;padding:0.5em;border:1px dashed #000;color:Black;overflow:visible;}pre.code{font-size:8pt;padding:0.5em;border:1px dashed #000;color:Black;overflow:visible;}code{font-size:120%;}pre.file{font-size:8pt;padding:0.5em;border:1px dotted #000;color:Black;overflow:visible;}div.footnotes{clear:both;border-top:1px solid #000;padding-left:1em;margin-top:1em;}div.fn{font-size:90%;}a.fn_top{vertical-align:super;font-size:80%;}a.fn_bot{vertical-align:super;font-size:80%;font-weight:bold;}acronym{border:0;}table.inline{font-size:80%;background-color:#fff;border-spacing:0px;border-collapse:collapse;}table.inline th{padding:3px;border:1px solid #000;border-bottom:2px solid #000;}table.inline td{padding:3px;border:1px solid #000;}.leftalign{text-align:left;}.centeralign{text-align:center;}.rightalign{text-align:right;}.toc,.footerinc,.header,.bar,.user{display:none}
\ No newline at end of file
diff --git a/docs/wiki/lib/exe/Makefile.am b/docs/wiki/lib/exe/Makefile.am
deleted file mode 100644
index 3155292..0000000
--- a/docs/wiki/lib/exe/Makefile.am
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-docname=wiki
-docsdir = $(docdir)/$(docname)/lib/exe
-
-docs_DATA = css 002css 001css opensearch
-
-EXTRA_DIST = $(docs_DATA)
-
-MAINTAINERCLEANFILES = *.log core FILE *~ Makefile.in
-
diff --git a/docs/wiki/lib/exe/css b/docs/wiki/lib/exe/css
deleted file mode 100644
index 6501c40..0000000
--- a/docs/wiki/lib/exe/css
+++ /dev/null
@@ -1 +0,0 @@
-a.interwiki{background:transparent url('../images/interwiki.png') 0px 1px no-repeat;padding-left:16px;}a.iw_wp{background-image:url('../images/interwiki/wp.gif')}a.iw_wpde{background-image:url('../images/interwiki/wpde.gif')}a.iw_wpmeta{background-image:url('../images/interwiki/wpmeta.gif')}a.iw_doku{background-image:url('../images/interwiki/doku.gif')}a.iw_sb{background-image:url('../images/interwiki/sb.gif')}a.iw_amazon{background-image:url('../images/interwiki/amazon.gif')}a.iw_amazon_de{background-image:url('../images/interwiki/amazon.de.gif')}a.iw_amazon_uk{background-image:url('../images/interwiki/amazon.uk.gif')}a.iw_phpfn{background-image:url('../images/interwiki/phpfn.gif')}a.iw_dokubug{background-image:url('../images/interwiki/dokubug.gif')}a.iw_coral{background-image:url('../images/interwiki/coral.gif')}a.iw_google{background-image:url('../images/interwiki/google.gif')}a.iw_meatball{background-image:url('../images/interwiki/meatball.gif')}a.iw_wiki{background-image:url('../images/interwiki/wiki.gif')}a.mediafile{background:transparent url('../images/fileicons/file.png') 0px 1px no-repeat;padding-left:18px;padding-bottom:1px;}a.mf_jpg{background-image:url('../images/fileicons/jpg.png')}a.mf_jpeg{background-image:url('../images/fileicons/jpeg.png')}a.mf_gif{background-image:url('../images/fileicons/gif.png')}a.mf_png{background-image:url('../images/fileicons/png.png')}a.mf_tgz{background-image:url('../images/fileicons/tgz.png')}a.mf_tar{background-image:url('../images/fileicons/tar.png')}a.mf_gz{background-image:url('../images/fileicons/gz.png')}a.mf_zip{background-image:url('../images/fileicons/zip.png')}a.mf_rar{background-image:url('../images/fileicons/rar.png')}a.mf_pdf{background-image:url('../images/fileicons/pdf.png')}a.mf_ps{background-image:url('../images/fileicons/ps.png')}a.mf_doc{background-image:url('../images/fileicons/doc.png')}a.mf_xls{background-image:url('../images/fileicons/xls.png')}a.mf_ppt{background-image:url('../images/fileicons/ppt.png')}a.mf_rtf{background-image:url('../images/fileicons/rtf.png')}a.mf_swf{background-image:url('../images/fileicons/swf.png')}a.mf_rpm{background-image:url('../images/fileicons/rpm.png')}a.mf_deb{background-image:url('../images/fileicons/deb.png')}a.mf_sxw{background-image:url('../images/fileicons/sxw.png')}a.mf_sxc{background-image:url('../images/fileicons/sxc.png')}a.mf_sxi{background-image:url('../images/fileicons/sxi.png')}a.mf_sxd{background-image:url('../images/fileicons/sxd.png')}a.mf_odc{background-image:url('../images/fileicons/odc.png')}a.mf_odf{background-image:url('../images/fileicons/odf.png')}a.mf_odg{background-image:url('../images/fileicons/odg.png')}a.mf_odi{background-image:url('../images/fileicons/odi.png')}a.mf_odp{background-image:url('../images/fileicons/odp.png')}a.mf_ods{background-image:url('../images/fileicons/ods.png')}a.mf_odt{background-image:url('../images/fileicons/odt.png')}a.mf_src{background-image:url('../images/fileicons/src.png')}
\ No newline at end of file
diff --git a/docs/wiki/lib/exe/opensearch b/docs/wiki/lib/exe/opensearch
deleted file mode 100644
index 698d1c1..0000000
--- a/docs/wiki/lib/exe/opensearch
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<OpenSearchDescription xmlns="http://a9.com/-/spec/opensearch/1.1/";>
- <ShortName>geda Wiki</ShortName>
- <Image width="16" height="16" type="image/x-icon">http://geda.seul.org/wiki/lib/tpl/geda/images/favicon.ico</Image>
- <Url type="text/html" template="http://geda.seul.org/wiki/doku.php?do=search&id={searchTerms}"; />
- <Url type="application/x-suggestions+json" template="http://geda.seul.org/wiki/lib/exe/ajax.php?call=suggestions&q={searchTerms}"; />
-</OpenSearchDescription>
diff --git a/docs/wiki/lib/images/.gitignore b/docs/wiki/lib/images/.gitignore
deleted file mode 100644
index 23c1897..0000000
--- a/docs/wiki/lib/images/.gitignore
+++ /dev/null
@@ -1,3 +0,0 @@
-Makefile
-Makefile.in
-*~
diff --git a/docs/wiki/lib/images/Makefile.am b/docs/wiki/lib/images/Makefile.am
deleted file mode 100644
index 3180c77..0000000
--- a/docs/wiki/lib/images/Makefile.am
+++ /dev/null
@@ -1,13 +0,0 @@
-
-
-docname=wiki
-docsdir = $(docdir)/$(docname)/lib/images
-
-SUBDIRS = smileys interwiki fileicons
-
-docs_DATA = info.png interwiki.png success.png notify.png error.png
-
-EXTRA_DIST = $(docs_DATA)
-
-MAINTAINERCLEANFILES = *.log core FILE *~ Makefile.in
-
diff --git a/docs/wiki/lib/images/error.png b/docs/wiki/lib/images/error.png
deleted file mode 100644
index 8a1ba4c..0000000
Binary files a/docs/wiki/lib/images/error.png and /dev/null differ
diff --git a/docs/wiki/lib/images/fileicons/.gitignore b/docs/wiki/lib/images/fileicons/.gitignore
deleted file mode 100644
index 23c1897..0000000
--- a/docs/wiki/lib/images/fileicons/.gitignore
+++ /dev/null
@@ -1,3 +0,0 @@
-Makefile
-Makefile.in
-*~
diff --git a/docs/wiki/lib/images/fileicons/Makefile.am b/docs/wiki/lib/images/fileicons/Makefile.am
deleted file mode 100644
index 39d9948..0000000
--- a/docs/wiki/lib/images/fileicons/Makefile.am
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-docname=wiki
-docsdir = $(docdir)/$(docname)/lib/images/fileicons
-
-docs_DATA = doc.png sxc.png odc.png xls.png pdf.png gz.png tgz.png jpeg.png jpg.png odi.png ps.png odt.png file.png sxi.png odg.png sxw.png ppt.png rar.png rtf.png sxd.png rpm.png odp.png png.png zip.png swf.png odf.png deb.png src.png gif.png tar.png ods.png
-
-EXTRA_DIST = $(docs_DATA)
-
-MAINTAINERCLEANFILES = *.log core FILE *~ Makefile.in
-
diff --git a/docs/wiki/lib/images/fileicons/deb.png b/docs/wiki/lib/images/fileicons/deb.png
deleted file mode 100644
index 9229d87..0000000
Binary files a/docs/wiki/lib/images/fileicons/deb.png and /dev/null differ
diff --git a/docs/wiki/lib/images/fileicons/doc.png b/docs/wiki/lib/images/fileicons/doc.png
deleted file mode 100644
index 932567f..0000000
Binary files a/docs/wiki/lib/images/fileicons/doc.png and /dev/null differ
diff --git a/docs/wiki/lib/images/fileicons/file.png b/docs/wiki/lib/images/fileicons/file.png
deleted file mode 100644
index 817014f..0000000
Binary files a/docs/wiki/lib/images/fileicons/file.png and /dev/null differ
diff --git a/docs/wiki/lib/images/fileicons/gif.png b/docs/wiki/lib/images/fileicons/gif.png
deleted file mode 100644
index b4c07a9..0000000
Binary files a/docs/wiki/lib/images/fileicons/gif.png and /dev/null differ
diff --git a/docs/wiki/lib/images/fileicons/gz.png b/docs/wiki/lib/images/fileicons/gz.png
deleted file mode 100644
index 2426bd1..0000000
Binary files a/docs/wiki/lib/images/fileicons/gz.png and /dev/null differ
diff --git a/docs/wiki/lib/images/fileicons/jpeg.png b/docs/wiki/lib/images/fileicons/jpeg.png
deleted file mode 100644
index aa4cc23..0000000
Binary files a/docs/wiki/lib/images/fileicons/jpeg.png and /dev/null differ
diff --git a/docs/wiki/lib/images/fileicons/jpg.png b/docs/wiki/lib/images/fileicons/jpg.png
deleted file mode 100644
index 1fb6cc1..0000000
Binary files a/docs/wiki/lib/images/fileicons/jpg.png and /dev/null differ
diff --git a/docs/wiki/lib/images/fileicons/odc.png b/docs/wiki/lib/images/fileicons/odc.png
deleted file mode 100644
index 47f65c8..0000000
Binary files a/docs/wiki/lib/images/fileicons/odc.png and /dev/null differ
diff --git a/docs/wiki/lib/images/fileicons/odf.png b/docs/wiki/lib/images/fileicons/odf.png
deleted file mode 100644
index a2fbc51..0000000
Binary files a/docs/wiki/lib/images/fileicons/odf.png and /dev/null differ
diff --git a/docs/wiki/lib/images/fileicons/odg.png b/docs/wiki/lib/images/fileicons/odg.png
deleted file mode 100644
index 434f182..0000000
Binary files a/docs/wiki/lib/images/fileicons/odg.png and /dev/null differ
diff --git a/docs/wiki/lib/images/fileicons/odi.png b/docs/wiki/lib/images/fileicons/odi.png
deleted file mode 100644
index 74f6303..0000000
Binary files a/docs/wiki/lib/images/fileicons/odi.png and /dev/null differ
diff --git a/docs/wiki/lib/images/fileicons/odp.png b/docs/wiki/lib/images/fileicons/odp.png
deleted file mode 100644
index a5c77f8..0000000
Binary files a/docs/wiki/lib/images/fileicons/odp.png and /dev/null differ
diff --git a/docs/wiki/lib/images/fileicons/ods.png b/docs/wiki/lib/images/fileicons/ods.png
deleted file mode 100644
index 2ab1273..0000000
Binary files a/docs/wiki/lib/images/fileicons/ods.png and /dev/null differ
diff --git a/docs/wiki/lib/images/fileicons/odt.png b/docs/wiki/lib/images/fileicons/odt.png
deleted file mode 100644
index b0c21fc..0000000
Binary files a/docs/wiki/lib/images/fileicons/odt.png and /dev/null differ
diff --git a/docs/wiki/lib/images/fileicons/pdf.png b/docs/wiki/lib/images/fileicons/pdf.png
deleted file mode 100644
index 638066d..0000000
Binary files a/docs/wiki/lib/images/fileicons/pdf.png and /dev/null differ
diff --git a/docs/wiki/lib/images/fileicons/png.png b/docs/wiki/lib/images/fileicons/png.png
deleted file mode 100644
index f0b5b00..0000000
Binary files a/docs/wiki/lib/images/fileicons/png.png and /dev/null differ
diff --git a/docs/wiki/lib/images/fileicons/ppt.png b/docs/wiki/lib/images/fileicons/ppt.png
deleted file mode 100644
index adaefc6..0000000
Binary files a/docs/wiki/lib/images/fileicons/ppt.png and /dev/null differ
diff --git a/docs/wiki/lib/images/fileicons/ps.png b/docs/wiki/lib/images/fileicons/ps.png
deleted file mode 100644
index c51c763..0000000
Binary files a/docs/wiki/lib/images/fileicons/ps.png and /dev/null differ
diff --git a/docs/wiki/lib/images/fileicons/rar.png b/docs/wiki/lib/images/fileicons/rar.png
deleted file mode 100644
index a6af4d1..0000000
Binary files a/docs/wiki/lib/images/fileicons/rar.png and /dev/null differ
diff --git a/docs/wiki/lib/images/fileicons/rpm.png b/docs/wiki/lib/images/fileicons/rpm.png
deleted file mode 100644
index 22212ea..0000000
Binary files a/docs/wiki/lib/images/fileicons/rpm.png and /dev/null differ
diff --git a/docs/wiki/lib/images/fileicons/rtf.png b/docs/wiki/lib/images/fileicons/rtf.png
deleted file mode 100644
index d8bada5..0000000
Binary files a/docs/wiki/lib/images/fileicons/rtf.png and /dev/null differ
diff --git a/docs/wiki/lib/images/fileicons/src.png b/docs/wiki/lib/images/fileicons/src.png
deleted file mode 100644
index da20009..0000000
Binary files a/docs/wiki/lib/images/fileicons/src.png and /dev/null differ
diff --git a/docs/wiki/lib/images/fileicons/swf.png b/docs/wiki/lib/images/fileicons/swf.png
deleted file mode 100644
index 0729ed0..0000000
Binary files a/docs/wiki/lib/images/fileicons/swf.png and /dev/null differ
diff --git a/docs/wiki/lib/images/fileicons/sxc.png b/docs/wiki/lib/images/fileicons/sxc.png
deleted file mode 100644
index 419c183..0000000
Binary files a/docs/wiki/lib/images/fileicons/sxc.png and /dev/null differ
diff --git a/docs/wiki/lib/images/fileicons/sxd.png b/docs/wiki/lib/images/fileicons/sxd.png
deleted file mode 100644
index 5801bb2..0000000
Binary files a/docs/wiki/lib/images/fileicons/sxd.png and /dev/null differ
diff --git a/docs/wiki/lib/images/fileicons/sxi.png b/docs/wiki/lib/images/fileicons/sxi.png
deleted file mode 100644
index 2a94290..0000000
Binary files a/docs/wiki/lib/images/fileicons/sxi.png and /dev/null differ
diff --git a/docs/wiki/lib/images/fileicons/sxw.png b/docs/wiki/lib/images/fileicons/sxw.png
deleted file mode 100644
index 6da97be..0000000
Binary files a/docs/wiki/lib/images/fileicons/sxw.png and /dev/null differ
diff --git a/docs/wiki/lib/images/fileicons/tar.png b/docs/wiki/lib/images/fileicons/tar.png
deleted file mode 100644
index 5a2f717..0000000
Binary files a/docs/wiki/lib/images/fileicons/tar.png and /dev/null differ
diff --git a/docs/wiki/lib/images/fileicons/tgz.png b/docs/wiki/lib/images/fileicons/tgz.png
deleted file mode 100644
index 141acf5..0000000
Binary files a/docs/wiki/lib/images/fileicons/tgz.png and /dev/null differ
diff --git a/docs/wiki/lib/images/fileicons/xls.png b/docs/wiki/lib/images/fileicons/xls.png
deleted file mode 100644
index e8cd58d..0000000
Binary files a/docs/wiki/lib/images/fileicons/xls.png and /dev/null differ
diff --git a/docs/wiki/lib/images/fileicons/zip.png b/docs/wiki/lib/images/fileicons/zip.png
deleted file mode 100644
index 999ffbe..0000000
Binary files a/docs/wiki/lib/images/fileicons/zip.png and /dev/null differ
diff --git a/docs/wiki/lib/images/info.png b/docs/wiki/lib/images/info.png
deleted file mode 100644
index a237c17..0000000
Binary files a/docs/wiki/lib/images/info.png and /dev/null differ
diff --git a/docs/wiki/lib/images/interwiki.png b/docs/wiki/lib/images/interwiki.png
deleted file mode 100644
index 73d6f8d..0000000
Binary files a/docs/wiki/lib/images/interwiki.png and /dev/null differ
diff --git a/docs/wiki/lib/images/interwiki/.gitignore b/docs/wiki/lib/images/interwiki/.gitignore
deleted file mode 100644
index 23c1897..0000000
--- a/docs/wiki/lib/images/interwiki/.gitignore
+++ /dev/null
@@ -1,3 +0,0 @@
-Makefile
-Makefile.in
-*~
diff --git a/docs/wiki/lib/images/interwiki/Makefile.am b/docs/wiki/lib/images/interwiki/Makefile.am
deleted file mode 100644
index af23805..0000000
--- a/docs/wiki/lib/images/interwiki/Makefile.am
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-docname=wiki
-docsdir = $(docdir)/$(docname)/lib/images/interwiki
-
-docs_DATA = dokubug.gif coral.gif amazon.de.gif google.gif amazon.gif wpmeta.gif sb.gif doku.gif wiki.gif amazon.uk.gif wp.gif wpde.gif meatball.gif phpfn.gif
-
-EXTRA_DIST = $(docs_DATA)
-
-MAINTAINERCLEANFILES = *.log core FILE *~ Makefile.in
-
diff --git a/docs/wiki/lib/images/interwiki/amazon.de.gif b/docs/wiki/lib/images/interwiki/amazon.de.gif
deleted file mode 100644
index f52c1c5..0000000
Binary files a/docs/wiki/lib/images/interwiki/amazon.de.gif and /dev/null differ
diff --git a/docs/wiki/lib/images/interwiki/amazon.gif b/docs/wiki/lib/images/interwiki/amazon.gif
deleted file mode 100644
index f52c1c5..0000000
Binary files a/docs/wiki/lib/images/interwiki/amazon.gif and /dev/null differ
diff --git a/docs/wiki/lib/images/interwiki/amazon.uk.gif b/docs/wiki/lib/images/interwiki/amazon.uk.gif
deleted file mode 100644
index f52c1c5..0000000
Binary files a/docs/wiki/lib/images/interwiki/amazon.uk.gif and /dev/null differ
diff --git a/docs/wiki/lib/images/interwiki/coral.gif b/docs/wiki/lib/images/interwiki/coral.gif
deleted file mode 100644
index 0f9f675..0000000
Binary files a/docs/wiki/lib/images/interwiki/coral.gif and /dev/null differ
diff --git a/docs/wiki/lib/images/interwiki/doku.gif b/docs/wiki/lib/images/interwiki/doku.gif
deleted file mode 100644
index 7dc4248..0000000
Binary files a/docs/wiki/lib/images/interwiki/doku.gif and /dev/null differ
diff --git a/docs/wiki/lib/images/interwiki/dokubug.gif b/docs/wiki/lib/images/interwiki/dokubug.gif
deleted file mode 100644
index 3432b8d..0000000
Binary files a/docs/wiki/lib/images/interwiki/dokubug.gif and /dev/null differ
diff --git a/docs/wiki/lib/images/interwiki/google.gif b/docs/wiki/lib/images/interwiki/google.gif
deleted file mode 100644
index fb39f61..0000000
Binary files a/docs/wiki/lib/images/interwiki/google.gif and /dev/null differ
diff --git a/docs/wiki/lib/images/interwiki/meatball.gif b/docs/wiki/lib/images/interwiki/meatball.gif
deleted file mode 100644
index 7ac5454..0000000
Binary files a/docs/wiki/lib/images/interwiki/meatball.gif and /dev/null differ
diff --git a/docs/wiki/lib/images/interwiki/phpfn.gif b/docs/wiki/lib/images/interwiki/phpfn.gif
deleted file mode 100644
index 638d4c4..0000000
Binary files a/docs/wiki/lib/images/interwiki/phpfn.gif and /dev/null differ
diff --git a/docs/wiki/lib/images/interwiki/sb.gif b/docs/wiki/lib/images/interwiki/sb.gif
deleted file mode 100644
index e272a29..0000000
Binary files a/docs/wiki/lib/images/interwiki/sb.gif and /dev/null differ
diff --git a/docs/wiki/lib/images/interwiki/wiki.gif b/docs/wiki/lib/images/interwiki/wiki.gif
deleted file mode 100644
index e8dc5d2..0000000
Binary files a/docs/wiki/lib/images/interwiki/wiki.gif and /dev/null differ
diff --git a/docs/wiki/lib/images/interwiki/wp.gif b/docs/wiki/lib/images/interwiki/wp.gif
deleted file mode 100644
index ca853b8..0000000
Binary files a/docs/wiki/lib/images/interwiki/wp.gif and /dev/null differ
diff --git a/docs/wiki/lib/images/interwiki/wpde.gif b/docs/wiki/lib/images/interwiki/wpde.gif
deleted file mode 100644
index ca853b8..0000000
Binary files a/docs/wiki/lib/images/interwiki/wpde.gif and /dev/null differ
diff --git a/docs/wiki/lib/images/interwiki/wpmeta.gif b/docs/wiki/lib/images/interwiki/wpmeta.gif
deleted file mode 100644
index ca853b8..0000000
Binary files a/docs/wiki/lib/images/interwiki/wpmeta.gif and /dev/null differ
diff --git a/docs/wiki/lib/images/notify.png b/docs/wiki/lib/images/notify.png
deleted file mode 100644
index 6e0015d..0000000
Binary files a/docs/wiki/lib/images/notify.png and /dev/null differ
diff --git a/docs/wiki/lib/images/smileys/.gitignore b/docs/wiki/lib/images/smileys/.gitignore
deleted file mode 100644
index 23c1897..0000000
--- a/docs/wiki/lib/images/smileys/.gitignore
+++ /dev/null
@@ -1,3 +0,0 @@
-Makefile
-Makefile.in
-*~
diff --git a/docs/wiki/lib/images/smileys/Makefile.am b/docs/wiki/lib/images/smileys/Makefile.am
deleted file mode 100644
index 0615d35..0000000
--- a/docs/wiki/lib/images/smileys/Makefile.am
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-docname=wiki
-docsdir = $(docdir)/$(docname)/lib/images/smileys
-
-docs_DATA = icon_wink.gif fixme.gif icon_smile.gif icon_smile2.gif
-
-EXTRA_DIST = $(docs_DATA)
-
-MAINTAINERCLEANFILES = *.log core FILE *~ Makefile.in
-
diff --git a/docs/wiki/lib/images/smileys/fixme.gif b/docs/wiki/lib/images/smileys/fixme.gif
deleted file mode 100644
index b66ea99..0000000
Binary files a/docs/wiki/lib/images/smileys/fixme.gif and /dev/null differ
diff --git a/docs/wiki/lib/images/smileys/icon_smile.gif b/docs/wiki/lib/images/smileys/icon_smile.gif
deleted file mode 100644
index 7b1f6d3..0000000
Binary files a/docs/wiki/lib/images/smileys/icon_smile.gif and /dev/null differ
diff --git a/docs/wiki/lib/images/smileys/icon_smile2.gif b/docs/wiki/lib/images/smileys/icon_smile2.gif
deleted file mode 100644
index 769639d..0000000
Binary files a/docs/wiki/lib/images/smileys/icon_smile2.gif and /dev/null differ
diff --git a/docs/wiki/lib/images/smileys/icon_wink.gif b/docs/wiki/lib/images/smileys/icon_wink.gif
deleted file mode 100644
index d148288..0000000
Binary files a/docs/wiki/lib/images/smileys/icon_wink.gif and /dev/null differ
diff --git a/docs/wiki/lib/images/success.png b/docs/wiki/lib/images/success.png
deleted file mode 100644
index a5ae9f1..0000000
Binary files a/docs/wiki/lib/images/success.png and /dev/null differ
diff --git a/docs/wiki/lib/plugins/.gitignore b/docs/wiki/lib/plugins/.gitignore
deleted file mode 100644
index 23c1897..0000000
--- a/docs/wiki/lib/plugins/.gitignore
+++ /dev/null
@@ -1,3 +0,0 @@
-Makefile
-Makefile.in
-*~
diff --git a/docs/wiki/lib/plugins/Makefile.am b/docs/wiki/lib/plugins/Makefile.am
deleted file mode 100644
index 2abed10..0000000
--- a/docs/wiki/lib/plugins/Makefile.am
+++ /dev/null
@@ -1,13 +0,0 @@
-
-
-docname=wiki
-docsdir = $(docdir)/$(docname)/lib/plugins
-
-SUBDIRS = note definitionlist
-
-docs_DATA =
-
-EXTRA_DIST = $(docs_DATA)
-
-MAINTAINERCLEANFILES = *.log core FILE *~ Makefile.in
-
diff --git a/docs/wiki/lib/plugins/definitionlist/.gitignore b/docs/wiki/lib/plugins/definitionlist/.gitignore
deleted file mode 100644
index 23c1897..0000000
--- a/docs/wiki/lib/plugins/definitionlist/.gitignore
+++ /dev/null
@@ -1,3 +0,0 @@
-Makefile
-Makefile.in
-*~
diff --git a/docs/wiki/lib/plugins/definitionlist/Makefile.am b/docs/wiki/lib/plugins/definitionlist/Makefile.am
deleted file mode 100644
index a6bc1c7..0000000
--- a/docs/wiki/lib/plugins/definitionlist/Makefile.am
+++ /dev/null
@@ -1,13 +0,0 @@
-
-
-docname=wiki
-docsdir = $(docdir)/$(docname)/lib/plugins/definitionlist
-
-SUBDIRS = images
-
-docs_DATA =
-
-EXTRA_DIST = $(docs_DATA)
-
-MAINTAINERCLEANFILES = *.log core FILE *~ Makefile.in
-
diff --git a/docs/wiki/lib/plugins/definitionlist/images/.gitignore b/docs/wiki/lib/plugins/definitionlist/images/.gitignore
deleted file mode 100644
index 23c1897..0000000
--- a/docs/wiki/lib/plugins/definitionlist/images/.gitignore
+++ /dev/null
@@ -1,3 +0,0 @@
-Makefile
-Makefile.in
-*~
diff --git a/docs/wiki/lib/plugins/definitionlist/images/Makefile.am b/docs/wiki/lib/plugins/definitionlist/images/Makefile.am
deleted file mode 100644
index 8cf81aa..0000000
--- a/docs/wiki/lib/plugins/definitionlist/images/Makefile.am
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-docname=wiki
-docsdir = $(docdir)/$(docname)/lib/plugins/definitionlist/images
-
-docs_DATA = bullet.gif
-
-EXTRA_DIST = $(docs_DATA)
-
-MAINTAINERCLEANFILES = *.log core FILE *~ Makefile.in
-
diff --git a/docs/wiki/lib/plugins/definitionlist/images/bullet.gif b/docs/wiki/lib/plugins/definitionlist/images/bullet.gif
deleted file mode 100644
index ad7b49a..0000000
Binary files a/docs/wiki/lib/plugins/definitionlist/images/bullet.gif and /dev/null differ
diff --git a/docs/wiki/lib/plugins/note/.gitignore b/docs/wiki/lib/plugins/note/.gitignore
deleted file mode 100644
index 23c1897..0000000
--- a/docs/wiki/lib/plugins/note/.gitignore
+++ /dev/null
@@ -1,3 +0,0 @@
-Makefile
-Makefile.in
-*~
diff --git a/docs/wiki/lib/plugins/note/Makefile.am b/docs/wiki/lib/plugins/note/Makefile.am
deleted file mode 100644
index dca90ce..0000000
--- a/docs/wiki/lib/plugins/note/Makefile.am
+++ /dev/null
@@ -1,13 +0,0 @@
-
-
-docname=wiki
-docsdir = $(docdir)/$(docname)/lib/plugins/note
-
-SUBDIRS = images
-
-docs_DATA =
-
-EXTRA_DIST = $(docs_DATA)
-
-MAINTAINERCLEANFILES = *.log core FILE *~ Makefile.in
-
diff --git a/docs/wiki/lib/plugins/note/images/.gitignore b/docs/wiki/lib/plugins/note/images/.gitignore
deleted file mode 100644
index 23c1897..0000000
--- a/docs/wiki/lib/plugins/note/images/.gitignore
+++ /dev/null
@@ -1,3 +0,0 @@
-Makefile
-Makefile.in
-*~
diff --git a/docs/wiki/lib/plugins/note/images/Makefile.am b/docs/wiki/lib/plugins/note/images/Makefile.am
deleted file mode 100644
index 4c4ac06..0000000
--- a/docs/wiki/lib/plugins/note/images/Makefile.am
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-docname=wiki
-docsdir = $(docdir)/$(docname)/lib/plugins/note/images
-
-docs_DATA = warning.png important.png tip.png note.png
-
-EXTRA_DIST = $(docs_DATA)
-
-MAINTAINERCLEANFILES = *.log core FILE *~ Makefile.in
-
diff --git a/docs/wiki/lib/plugins/note/images/important.png b/docs/wiki/lib/plugins/note/images/important.png
deleted file mode 100644
index dc8c8a4..0000000
Binary files a/docs/wiki/lib/plugins/note/images/important.png and /dev/null differ
diff --git a/docs/wiki/lib/plugins/note/images/note.png b/docs/wiki/lib/plugins/note/images/note.png
deleted file mode 100644
index df1e0a9..0000000
Binary files a/docs/wiki/lib/plugins/note/images/note.png and /dev/null differ
diff --git a/docs/wiki/lib/plugins/note/images/tip.png b/docs/wiki/lib/plugins/note/images/tip.png
deleted file mode 100644
index 2000f20..0000000
Binary files a/docs/wiki/lib/plugins/note/images/tip.png and /dev/null differ
diff --git a/docs/wiki/lib/plugins/note/images/warning.png b/docs/wiki/lib/plugins/note/images/warning.png
deleted file mode 100644
index 3c8a37d..0000000
Binary files a/docs/wiki/lib/plugins/note/images/warning.png and /dev/null differ
diff --git a/docs/wiki/lib/tpl/.gitignore b/docs/wiki/lib/tpl/.gitignore
deleted file mode 100644
index 23c1897..0000000
--- a/docs/wiki/lib/tpl/.gitignore
+++ /dev/null
@@ -1,3 +0,0 @@
-Makefile
-Makefile.in
-*~
diff --git a/docs/wiki/lib/tpl/Makefile.am b/docs/wiki/lib/tpl/Makefile.am
deleted file mode 100644
index aa18857..0000000
--- a/docs/wiki/lib/tpl/Makefile.am
+++ /dev/null
@@ -1,13 +0,0 @@
-
-
-docname=wiki
-docsdir = $(docdir)/$(docname)/lib/tpl
-
-SUBDIRS = geda
-
-docs_DATA =
-
-EXTRA_DIST = $(docs_DATA)
-
-MAINTAINERCLEANFILES = *.log core FILE *~ Makefile.in
-
diff --git a/docs/wiki/lib/tpl/geda/Makefile.am b/docs/wiki/lib/tpl/geda/Makefile.am
deleted file mode 100644
index ba35770..0000000
--- a/docs/wiki/lib/tpl/geda/Makefile.am
+++ /dev/null
@@ -1,9 +0,0 @@
-
-
-docname=wiki
-docsdir = $(docdir)/$(docname)/lib/tpl/geda
-
-SUBDIRS = images
-
-MAINTAINERCLEANFILES = *.log core FILE *~ Makefile.in
-
diff --git a/docs/wiki/lib/tpl/geda/images/Makefile.am b/docs/wiki/lib/tpl/geda/images/Makefile.am
deleted file mode 100644
index ce39b5e..0000000
--- a/docs/wiki/lib/tpl/geda/images/Makefile.am
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-docname=wiki
-docsdir = $(docdir)/$(docname)/lib/tpl/geda/images
-
-docs_DATA = link_icon.gif open.gif closed.gif mail_icon.gif tocdot2.gif inputshadow.png favicon buttonshadow.png windows.gif
-
-EXTRA_DIST = $(docs_DATA)
-
-MAINTAINERCLEANFILES = *.log core FILE *~ Makefile.in
-
diff --git a/docs/wiki/lib/tpl/geda/images/buttonshadow.png b/docs/wiki/lib/tpl/geda/images/buttonshadow.png
deleted file mode 100644
index f60be30..0000000
Binary files a/docs/wiki/lib/tpl/geda/images/buttonshadow.png and /dev/null differ
diff --git a/docs/wiki/lib/tpl/geda/images/closed.gif b/docs/wiki/lib/tpl/geda/images/closed.gif
deleted file mode 100644
index 8414d4d..0000000
Binary files a/docs/wiki/lib/tpl/geda/images/closed.gif and /dev/null differ
diff --git a/docs/wiki/lib/tpl/geda/images/favicon b/docs/wiki/lib/tpl/geda/images/favicon
deleted file mode 100644
index 8b9616a..0000000
Binary files a/docs/wiki/lib/tpl/geda/images/favicon and /dev/null differ
diff --git a/docs/wiki/lib/tpl/geda/images/inputshadow.png b/docs/wiki/lib/tpl/geda/images/inputshadow.png
deleted file mode 100644
index d286beb..0000000
Binary files a/docs/wiki/lib/tpl/geda/images/inputshadow.png and /dev/null differ
diff --git a/docs/wiki/lib/tpl/geda/images/link_icon.gif b/docs/wiki/lib/tpl/geda/images/link_icon.gif
deleted file mode 100644
index 815ccb1..0000000
Binary files a/docs/wiki/lib/tpl/geda/images/link_icon.gif and /dev/null differ
diff --git a/docs/wiki/lib/tpl/geda/images/mail_icon.gif b/docs/wiki/lib/tpl/geda/images/mail_icon.gif
deleted file mode 100644
index 50a87a9..0000000
Binary files a/docs/wiki/lib/tpl/geda/images/mail_icon.gif and /dev/null differ
diff --git a/docs/wiki/lib/tpl/geda/images/open.gif b/docs/wiki/lib/tpl/geda/images/open.gif
deleted file mode 100644
index f5d5c7e..0000000
Binary files a/docs/wiki/lib/tpl/geda/images/open.gif and /dev/null differ
diff --git a/docs/wiki/lib/tpl/geda/images/tocdot2.gif b/docs/wiki/lib/tpl/geda/images/tocdot2.gif
deleted file mode 100644
index 3d39c2e..0000000
Binary files a/docs/wiki/lib/tpl/geda/images/tocdot2.gif and /dev/null differ
diff --git a/docs/wiki/lib/tpl/geda/images/windows.gif b/docs/wiki/lib/tpl/geda/images/windows.gif
deleted file mode 100644
index 4f12acc..0000000
Binary files a/docs/wiki/lib/tpl/geda/images/windows.gif and /dev/null differ
diff --git a/docs/wiki/libgeda3.html b/docs/wiki/libgeda3.html
index eea723f..094f657 100644
--- a/docs/wiki/libgeda3.html
+++ b/docs/wiki/libgeda3.html
@@ -1,27 +1,16 @@
<!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">
+<html>
<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
- <title>libgeda3</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-08-22T15:49:47-0400" />
-<meta name="keywords" content="libgeda3" />
-<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/libgeda3?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/libgeda3"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/libgeda3"; />
-<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">
@@ -128,7 +117,7 @@
<div class="level2">
<p>
- Because libgeda should â??make no assumptions about applications which will use the library," libgeda should use only â??worldâ?? coordinates throughout (the same coordinate system as used in the files). See the <a href="geda_file_format_spec.html" class="wikilink1" title="geda:file_format_spec">file format specification</a>.
+ Because libgeda should â??make no assumptions about applications which will use the library," libgeda should use only â??worldâ?? coordinates throughout (the same coordinate system as used in the files). See the <a href="geda-file_format_spec.html" class="wikilink1" title="geda-file_format_spec.html">file format specification</a>.
</p>
</div>
@@ -221,6 +210,5 @@ GObject is currently used in libgeda for the GedaList class which wrapps a GList
</ul>
</div>
-<!-- SECTION "References" [4336-] --></div>
-</body>
+<!-- SECTION "References" [4336-] --></body>
</html>
diff --git a/docs/wiki/libgeda3_object_based_design.html b/docs/wiki/libgeda3_object_based_design.html
new file mode 100644
index 0000000..161d4a2
--- /dev/null
+++ b/docs/wiki/libgeda3_object_based_design.html
@@ -0,0 +1,265 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#overview" class="toc">Overview</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#description_of_the_needs_in_an_electrical_cad_system" class="toc">Description of the needs in an Electrical CAD system</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#object_based_design" class="toc">Object based design</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#geda_objects" class="toc">geda objects</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#integration_with_current_code" class="toc">Integration with current code</a></span></div></li>
+<li class="level1"><div class="li"><span class="li"><a href="#comments" class="toc">Comments?</a></span></div></li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="overview" id="overview">Overview</a></h1>
+<div class="level1">
+
+<p>
+As stated in <a href="libgeda3.html" class="wikilink1" title="libgeda3.html">libgeda3</a>, libgeda has some design problems that needs to be addressed. The structure described in this page is very different from the current libgeda structure and design, while hopefully can be flexible enough to be the basement of future developments.
+</p>
+
+</div>
+<!-- SECTION "Overview" [1-296] -->
+<h1><a name="description_of_the_needs_in_an_electrical_cad_system" id="description_of_the_needs_in_an_electrical_cad_system">Description of the needs in an Electrical CAD system</a></h1>
+<div class="level1">
+
+<p>
+ Schematics and PCB (or IC) designs are, by nature, a graphical representation of objects, with interconnections between them.
+</p>
+
+<p>
+The basic primitives used in the graphical artwork are:
+</p>
+<ul>
+<li class="level1"><div class="li"> Lines</div>
+</li>
+<li class="level1"><div class="li"> Arcs</div>
+</li>
+<li class="level1"><div class="li"> Rectangles</div>
+</li>
+<li class="level1"><div class="li"> Circles</div>
+</li>
+<li class="level1"><div class="li"> Text</div>
+</li>
+<li class="level1"><div class="li"> Images (not very often)</div>
+</li>
+</ul>
+
+<p>
+ These basic shapes can have attributes modifying how they are drawn in the screen: dashed or dotted lines, filled or unfilled shapes,… , and can be grouped into a composed object (this object is drawn as a combination of one or more basic primitives). The graphical representation of a composed object is a symbol.
+</p>
+
+<p>
+An electrical or electronic CAD must be able to draw components (composed objects) and interconnections between them. The interconnections is the key difference from other CAD packages, and are the basis of further engineering work, such as simulations or layouts. They are drawn as lines, but they are not only lines and therefore should be handled differently. The interconnection primitives are:
+</p>
+<ul>
+<li class="level1"><div class="li"> Pin or ports: points of a composed object which can be used for interconnection, or connection points between pages.</div>
+</li>
+<li class="level1"><div class="li"> Nets: define the interconnections between pin or ports. It is usually drawn as a line.</div>
+</li>
+<li class="level1"><div class="li"> Junction: define the connection between crossing nets. It is usually drawn as a dot at the intersection of two crossing nets.</div>
+</li>
+<li class="level1"><div class="li"> Buses: group of nets. Trying to make things simple, they are drawn as a line, usually thicker than nets.</div>
+</li>
+<li class="level1"><div class="li"> Bus ripper: connects a net to a bus. It is needed because there should be a way to specify which net of the bus should be connected.</div>
+</li>
+</ul>
+
+<p>
+ An electric circuit can be drawn in a page, but, as designs grow in complexity, it is usually divided into several interconnected pages, or is drawn as a hierarchy. One common way is to draw a circuit defining some ports (where it is going to connect to other circuits), make a symbol for it, and include the symbol in other pages as it was a common composed object. So a design is composed of one or several pages, which can also include other pageâ??s symbols, and so on. Therefore, a design can be drawn as a hiearchy tree.
+</p>
+
+<p>
+Finally, but not less important, every object described can have properties attached, describing the nature of the component, its attributes, or other representations (simulation models, graphical representation for PCB design,…).
+</p>
+
+</div>
+<!-- SECTION "Description of the needs in an Electrical CAD system" [297-2701] -->
+<h1><a name="object_based_design" id="object_based_design">Object based design</a></h1>
+<div class="level1">
+
+<p>
+Despite its title, this is not a section talking about Object Oriented Programming. <img src="images/smileys/icon_smile.gif" align="middle" alt=":-)" />
+</p>
+
+<p>
+It is a known fact that all schematics are graphical representations of components, interconnections and properties, organized as a plain or hierarchical tree.
+</p>
+
+<p>
+One of the current issues with libgeda is that the schematic program itself, and hence the developers, should take care of all the drawing stuff associated with schematics. Plus, there are drawing transforms, like moving, rotating, mirroring, etc… This is very time consuming for the developer, and the results are not always the best.
+</p>
+
+<p>
+This was fine at the moment when it was born, but technology is continuously evolving. Today there are more advanced widgets that take care of all the object drawing, and lets the applications concentrate on what they should do. This kind of widgets are called â??canvasâ??.
+</p>
+
+<p>
+Letâ??s take a look at one of them: <a href="http://sourceforge.net/projects/goocanvas"; class="urlextern" title="http://sourceforge.net/projects/goocanvas"; rel="nofollow">goocanvas</a>. There are no screenshots, no official webpage, but donâ??t be scared and look further. Download it and take a look at the documentation into the â??docâ?? directory. You can also compile a demo, but you will need GTK 2.10 (for goocanvas version greater than 0.4), or GTK2.8 (goocanvas 0.4). I can tell you that the demo of the last version (0.8 at this moment) is quite impressive. If you have time, try it!. It is worth!.
+</p>
+
+<p>
+Basically what it provides is:
+</p>
+<ul>
+<li class="level1"><div class="li"> Already defined primitives: ellipse, image, path, polyline, rectangle, text, and even support for other GTK widges.</div>
+</li>
+<li class="level1"><div class="li"> Takes care of all the drawing stuff.</div>
+</li>
+<li class="level1"><div class="li"> Model/view implementation: several views of the same page is easily supported.</div>
+</li>
+<li class="level1"><div class="li"> Full hierarchy/nesting capability: there are no nesting limits.</div>
+</li>
+<li class="level1"><div class="li"> Uses cairo, already in GTK. This can be a drawback for some people, but if you have problems with cairo, itâ??s likely you are going to have problems with the current gschem when GTK complete the transition into cairo.</div>
+</li>
+<li class="level1"><div class="li"> Built-in drawing transforms (rotating, scaling, moving,…).</div>
+</li>
+<li class="level1"><div class="li"> Full international text support without creating a new font. This is something true with some programs using a custom font: if you want it to support your language, you have to create the font for your special characters. (This is the case of the current gschem).</div>
+</li>
+<li class="level1"><div class="li"> Built-in object visibility and clipping handling.</div>
+</li>
+<li class="level1"><div class="li"> Built-in object events: it can detect clicks on objects, for example.</div>
+</li>
+<li class="level1"><div class="li"> Written in C using GObject.</div>
+</li>
+</ul>
+
+<p>
+ The advantage is clear: all the basic drawing primitives and operations are already done.
+</p>
+
+<p>
+ So the proposal is to base all the geda objects on the objects supplied by the canvas (note that every canvas you find is going to provide its own object classes, so this is a canvas based generic design.
+</p>
+
+</div>
+<!-- SECTION "Object based design" [2702-5463] -->
+<h1><a name="geda_objects" id="geda_objects">geda objects</a></h1>
+<div class="level1">
+
+<p>
+ The geda object definition could be something as simple as:
+</p>
+<pre class="code C"><span class="kw4">struct</span> GedaObject <span class="br0">{</span>
+ <span class="kw4">int</span> GedaType;
+ GList *views; <span class="coMULTI">/* List of pointers to GooCanvasItems
+ This could solve the problem about heterogeneus parts:
+ We can store as many graphical representations of they object as we want */</span>
+ <span class="coMULTI">/* Still not sure about this, though */</span>
+ GooCanvasItem *current_view;
+<span class="br0">}</span>;
+
+<span class="kw4">struct</span> GedaObjectGroup <span class="br0">{</span>
+ <span class="kw4">int</span> GedaType;
+ GooCanvasItem group; <span class="coMULTI">/* There is also an item for groups of objects */</span>
+<span class="br0">}</span>;</pre>
+<p>
+There is no need to store graphic attributes in GedaObject. If the position is needed, since the canvas item can be queried. Some special definition for properties is needed (they shouldnâ??t be handled as just text):
+</p>
+<pre class="code C"><span class="kw4">struct</span> GedaObjectProperty <span class="br0">{</span>
+ GedaType;
+ GooCanvasItem *name;
+ GooCanvasItem *value;
+<span class="br0">}</span>;</pre>
+<p>
+and another one for connectivity items:
+</p>
+<pre class="code C"><span class="kw4">struct</span> GedaObjectPort <span class="br0">{</span>
+ <span class="kw4">int</span> GedaType;
+ GooCanvasItem *graphic;
+ GedaObject *connected_object;
+<span class="br0">}</span>;
+
+<span class="kw4">struct</span> GedaObjectDotConnection <span class="br0">{</span>
+ <span class="kw4">int</span> GedaType;
+ GooCanvasItem *graphic;
+ GList *connected_objects;
+<span class="br0">}</span>;
+
+<span class="kw4">struct</span> GedaObjectNet <span class="br0">{</span> <span class="coMULTI">/* or bus, or bus ripper */</span>
+ <span class="kw4">int</span> GedaType;
+ GooCanvasItem *graphic;
+ GList *connected_objects;
+<span class="br0">}</span>;</pre>
+<p>
+Everything else can be done attaching properties to the defined objects. For example, a page is just as any other GedaObject, where the view item points to a GedaObjectGroup. Notice that having multiple views for a page could be just like a page having multiple pages (at the same hierarchy level).
+</p>
+
+<p>
+No object naming is required, although it is already supported by default: you can add a GedaProperty to any other object (it will become part of the object).
+</p>
+
+<p>
+Example: a 7400 symbol, with a footprint attribute â??DIP-16â??, and reference designator â??U1â?? would look as:
+</p>
+<pre class="code">
+GedaObject
+ |- views
+ | |- GedaObjectGroup
+ | | |- GedaObjectGroup /* the graphic representation */
+ | | |- GedaObjectProperty /* name = "refdes", value="U1" */
+ | | |- GedaObjectProperty /* name = "footprint", value="DIP-16" */
+ v v
+</pre>
+
+</div>
+<!-- SECTION "geda objects" [5464-7610] -->
+<h1><a name="integration_with_current_code" id="integration_with_current_code">Integration with current code</a></h1>
+<div class="level1">
+
+<p>
+ There is no easy and direct way to get this structure into the current codebase. However, the current codebase can be adapted progressively to use this structure.
+</p>
+
+<p>
+All canvas specific code can be hidden by a common interface or a runtime plugin, so a possible change of the used canvas could be easy.
+</p>
+
+</div>
+<!-- SECTION "Integration with current code" [7611-7959] -->
+<h1><a name="comments" id="comments">Comments?</a></h1>
+<div class="level1">
+
+<p>
+ Leave your comment here!
+</p>
+
+<p>
+[Peter C] {
+</p>
+
+<p>
+Hi. I think a canvas could be the right way to go with gschem, however we should design libgeda structures to represent the underlying circuit, design, and CAD / graphics concepts involved. Iâ??d hope we can avoid linking any canvas or UI specific structures into libgeda. In a sense, part of what libgedaâ??s does is define canvas independent data-structures and manipulation functions for for the graphic objects on a schematic page.
+</p>
+
+<p>
+We can write a wrapper between libgeda and the canvas for actual rendering. It looks (superficially) that this is possible with goocanvas. The two basic cases are â??compoundâ?? gEDA objects which map to groups of other objects (like complex objects, the current font implementation etc.), and gEDA objects which map to primitives like lines and arcs.
+</p>
+
+<p>
+I think some of the important design decisions to make now involve defining the <acronym title="Application Programming Interface">API</acronym> for object / design database manipulation, and what signals and hooks we might expose to other code. Iâ??d start by considering starting with basic â??translate, rotate, mirror, …." operations like libgeda has now, and then explore signals notifying that an object has changed.
+</p>
+
+<p>
+}
+</p>
+
+</div>
+<!-- SECTION "Comments?" [7960-] --></body>
+</html>
diff --git a/docs/wiki/media/.gitignore b/docs/wiki/media/.gitignore
new file mode 100644
index 0000000..23c1897
--- /dev/null
+++ b/docs/wiki/media/.gitignore
@@ -0,0 +1,3 @@
+Makefile
+Makefile.in
+*~
diff --git a/docs/wiki/media/Makefile.am b/docs/wiki/media/Makefile.am
new file mode 100644
index 0000000..8ce7d79
--- /dev/null
+++ b/docs/wiki/media/Makefile.am
@@ -0,0 +1,8 @@
+
+
+docname=wiki
+docsdir = $(docdir)/$(docname)/media
+
+SUBDIRS = geda wiki tragesym devel_tips
+
+
diff --git a/docs/wiki/media/devel_tips/.gitignore b/docs/wiki/media/devel_tips/.gitignore
new file mode 100644
index 0000000..23c1897
--- /dev/null
+++ b/docs/wiki/media/devel_tips/.gitignore
@@ -0,0 +1,3 @@
+Makefile
+Makefile.in
+*~
diff --git a/docs/wiki/media/devel_tips/Makefile.am b/docs/wiki/media/devel_tips/Makefile.am
new file mode 100644
index 0000000..2161fde
--- /dev/null
+++ b/docs/wiki/media/devel_tips/Makefile.am
@@ -0,0 +1,11 @@
+
+
+docname=wiki
+docsdir = $(docdir)/$(docname)/media/devel_tips
+
+docs_DATA = dialog_picture.png
+
+EXTRA_DIST = $(docs_DATA)
+
+MAINTAINERCLEANFILES = *.log core FILE *~ Makefile.in
+
diff --git a/docs/wiki/media/devel_tips/dialog_picture.png b/docs/wiki/media/devel_tips/dialog_picture.png
new file mode 100644
index 0000000..3108609
Binary files /dev/null and b/docs/wiki/media/devel_tips/dialog_picture.png differ
diff --git a/docs/wiki/media/geda/.gitignore b/docs/wiki/media/geda/.gitignore
new file mode 100644
index 0000000..23c1897
--- /dev/null
+++ b/docs/wiki/media/geda/.gitignore
@@ -0,0 +1,3 @@
+Makefile
+Makefile.in
+*~
diff --git a/docs/wiki/media/geda/Makefile.am b/docs/wiki/media/geda/Makefile.am
new file mode 100644
index 0000000..ab3fb70
--- /dev/null
+++ b/docs/wiki/media/geda/Makefile.am
@@ -0,0 +1,11 @@
+
+
+docname=wiki
+docsdir = $(docdir)/$(docname)/media/geda
+
+docs_DATA = board-5.png symbol_7400-1_hidden.png dialogvdc1.png pcb-el-2.png warmup_add_component.png ambiguous1.png schematicfinished2.png net.jpg board-3.png one-sch-1.png switcap_figure4.jpg gschem-sym-1.png dialogdirective.png faq_attrib.jpg two-sch-1.png board-4.png symbol_7400-1.png dialogmodel.png gschem-sym-2.png geda_flow.png dialoginclude.png status_screenshot.jpg ambiguous1_fixed.png board-1.png gschem_workflow_01.jpg schematicfinished.png nets.jpg gschem_screenshot_001.jpg pcb-el-1.png path_example_and_gate-smaller.png path_example_and_gate.png warmup_gschem03.png switcap_figure1.jpg dialogvac.png design_flow.jpg simple1.png board-6.png board-2.png switcap_figure2.jpg coordinatespace.jpg one-sch-2.png terminal_screenshot_001.jpg suse_electronics_menu.png switcap_figure3.jpg warmup_gschem01.png dialogtrans.png fileformat_textgraphic.jpg warmup_gschem02.png gschem-sym-3.png rf_cascade_figure1.jpg paper1.gif one-sch-3.png rf_cascade_figure2.jpg two-sch-2.png
+
+EXTRA_DIST = $(docs_DATA)
+
+MAINTAINERCLEANFILES = *.log core FILE *~ Makefile.in
+
diff --git a/docs/wiki/media/geda/ambiguous1.png b/docs/wiki/media/geda/ambiguous1.png
new file mode 100644
index 0000000..29ffddb
Binary files /dev/null and b/docs/wiki/media/geda/ambiguous1.png differ
diff --git a/docs/wiki/media/geda/ambiguous1_fixed.png b/docs/wiki/media/geda/ambiguous1_fixed.png
new file mode 100644
index 0000000..ae3dc52
Binary files /dev/null and b/docs/wiki/media/geda/ambiguous1_fixed.png differ
diff --git a/docs/wiki/media/geda/board-1.png b/docs/wiki/media/geda/board-1.png
new file mode 100644
index 0000000..6189478
Binary files /dev/null and b/docs/wiki/media/geda/board-1.png differ
diff --git a/docs/wiki/media/geda/board-2.png b/docs/wiki/media/geda/board-2.png
new file mode 100644
index 0000000..62c351c
Binary files /dev/null and b/docs/wiki/media/geda/board-2.png differ
diff --git a/docs/wiki/media/geda/board-3.png b/docs/wiki/media/geda/board-3.png
new file mode 100644
index 0000000..f0406e3
Binary files /dev/null and b/docs/wiki/media/geda/board-3.png differ
diff --git a/docs/wiki/media/geda/board-4.png b/docs/wiki/media/geda/board-4.png
new file mode 100644
index 0000000..ec6eba5
Binary files /dev/null and b/docs/wiki/media/geda/board-4.png differ
diff --git a/docs/wiki/media/geda/board-5.png b/docs/wiki/media/geda/board-5.png
new file mode 100644
index 0000000..57ff80d
Binary files /dev/null and b/docs/wiki/media/geda/board-5.png differ
diff --git a/docs/wiki/media/geda/board-6.png b/docs/wiki/media/geda/board-6.png
new file mode 100644
index 0000000..0e1189a
Binary files /dev/null and b/docs/wiki/media/geda/board-6.png differ
diff --git a/docs/wiki/media/geda/coordinatespace.jpg b/docs/wiki/media/geda/coordinatespace.jpg
new file mode 100644
index 0000000..83b57fc
Binary files /dev/null and b/docs/wiki/media/geda/coordinatespace.jpg differ
diff --git a/docs/wiki/media/geda/design_flow.jpg b/docs/wiki/media/geda/design_flow.jpg
new file mode 100644
index 0000000..0d6f152
Binary files /dev/null and b/docs/wiki/media/geda/design_flow.jpg differ
diff --git a/docs/wiki/media/geda/dialogdirective.png b/docs/wiki/media/geda/dialogdirective.png
new file mode 100644
index 0000000..e1f21db
Binary files /dev/null and b/docs/wiki/media/geda/dialogdirective.png differ
diff --git a/docs/wiki/media/geda/dialoginclude.png b/docs/wiki/media/geda/dialoginclude.png
new file mode 100644
index 0000000..5d300bd
Binary files /dev/null and b/docs/wiki/media/geda/dialoginclude.png differ
diff --git a/docs/wiki/media/geda/dialogmodel.png b/docs/wiki/media/geda/dialogmodel.png
new file mode 100644
index 0000000..49e8e42
Binary files /dev/null and b/docs/wiki/media/geda/dialogmodel.png differ
diff --git a/docs/wiki/media/geda/dialogtrans.png b/docs/wiki/media/geda/dialogtrans.png
new file mode 100644
index 0000000..4a7f9a1
Binary files /dev/null and b/docs/wiki/media/geda/dialogtrans.png differ
diff --git a/docs/wiki/media/geda/dialogvac.png b/docs/wiki/media/geda/dialogvac.png
new file mode 100644
index 0000000..744893e
Binary files /dev/null and b/docs/wiki/media/geda/dialogvac.png differ
diff --git a/docs/wiki/media/geda/dialogvdc1.png b/docs/wiki/media/geda/dialogvdc1.png
new file mode 100644
index 0000000..3e16535
Binary files /dev/null and b/docs/wiki/media/geda/dialogvdc1.png differ
diff --git a/docs/wiki/media/geda/faq_attrib.jpg b/docs/wiki/media/geda/faq_attrib.jpg
new file mode 100644
index 0000000..cca6286
Binary files /dev/null and b/docs/wiki/media/geda/faq_attrib.jpg differ
diff --git a/docs/wiki/media/geda/fileformat_textgraphic.jpg b/docs/wiki/media/geda/fileformat_textgraphic.jpg
new file mode 100644
index 0000000..1f49c1c
Binary files /dev/null and b/docs/wiki/media/geda/fileformat_textgraphic.jpg differ
diff --git a/docs/wiki/media/geda/geda_flow.png b/docs/wiki/media/geda/geda_flow.png
new file mode 100644
index 0000000..79fbf9f
Binary files /dev/null and b/docs/wiki/media/geda/geda_flow.png differ
diff --git a/docs/wiki/media/geda/gschem-sym-1.png b/docs/wiki/media/geda/gschem-sym-1.png
new file mode 100644
index 0000000..dfae00a
Binary files /dev/null and b/docs/wiki/media/geda/gschem-sym-1.png differ
diff --git a/docs/wiki/media/geda/gschem-sym-2.png b/docs/wiki/media/geda/gschem-sym-2.png
new file mode 100644
index 0000000..dfc7d84
Binary files /dev/null and b/docs/wiki/media/geda/gschem-sym-2.png differ
diff --git a/docs/wiki/media/geda/gschem-sym-3.png b/docs/wiki/media/geda/gschem-sym-3.png
new file mode 100644
index 0000000..b76217d
Binary files /dev/null and b/docs/wiki/media/geda/gschem-sym-3.png differ
diff --git a/docs/wiki/media/geda/gschem_screenshot_001.jpg b/docs/wiki/media/geda/gschem_screenshot_001.jpg
new file mode 100644
index 0000000..2e0cf68
Binary files /dev/null and b/docs/wiki/media/geda/gschem_screenshot_001.jpg differ
diff --git a/docs/wiki/media/geda/gschem_workflow_01.jpg b/docs/wiki/media/geda/gschem_workflow_01.jpg
new file mode 100644
index 0000000..d1326bc
Binary files /dev/null and b/docs/wiki/media/geda/gschem_workflow_01.jpg differ
diff --git a/docs/wiki/media/geda/net.jpg b/docs/wiki/media/geda/net.jpg
new file mode 100644
index 0000000..3311666
Binary files /dev/null and b/docs/wiki/media/geda/net.jpg differ
diff --git a/docs/wiki/media/geda/nets.jpg b/docs/wiki/media/geda/nets.jpg
new file mode 100644
index 0000000..264690e
Binary files /dev/null and b/docs/wiki/media/geda/nets.jpg differ
diff --git a/docs/wiki/media/geda/one-sch-1.png b/docs/wiki/media/geda/one-sch-1.png
new file mode 100644
index 0000000..3824b47
Binary files /dev/null and b/docs/wiki/media/geda/one-sch-1.png differ
diff --git a/docs/wiki/media/geda/one-sch-2.png b/docs/wiki/media/geda/one-sch-2.png
new file mode 100644
index 0000000..9028fc2
Binary files /dev/null and b/docs/wiki/media/geda/one-sch-2.png differ
diff --git a/docs/wiki/media/geda/one-sch-3.png b/docs/wiki/media/geda/one-sch-3.png
new file mode 100644
index 0000000..82e65ea
Binary files /dev/null and b/docs/wiki/media/geda/one-sch-3.png differ
diff --git a/docs/wiki/media/geda/paper1.gif b/docs/wiki/media/geda/paper1.gif
new file mode 100644
index 0000000..6920014
Binary files /dev/null and b/docs/wiki/media/geda/paper1.gif differ
diff --git a/docs/wiki/media/geda/path_example_and_gate-smaller.png b/docs/wiki/media/geda/path_example_and_gate-smaller.png
new file mode 100644
index 0000000..303863f
Binary files /dev/null and b/docs/wiki/media/geda/path_example_and_gate-smaller.png differ
diff --git a/docs/wiki/media/geda/path_example_and_gate.png b/docs/wiki/media/geda/path_example_and_gate.png
new file mode 100644
index 0000000..7e46fa9
Binary files /dev/null and b/docs/wiki/media/geda/path_example_and_gate.png differ
diff --git a/docs/wiki/media/geda/pcb-el-1.png b/docs/wiki/media/geda/pcb-el-1.png
new file mode 100644
index 0000000..84d5bc3
Binary files /dev/null and b/docs/wiki/media/geda/pcb-el-1.png differ
diff --git a/docs/wiki/media/geda/pcb-el-2.png b/docs/wiki/media/geda/pcb-el-2.png
new file mode 100644
index 0000000..41d7322
Binary files /dev/null and b/docs/wiki/media/geda/pcb-el-2.png differ
diff --git a/docs/wiki/media/geda/rf_cascade_figure1.jpg b/docs/wiki/media/geda/rf_cascade_figure1.jpg
new file mode 100644
index 0000000..2521dfe
Binary files /dev/null and b/docs/wiki/media/geda/rf_cascade_figure1.jpg differ
diff --git a/docs/wiki/media/geda/rf_cascade_figure2.jpg b/docs/wiki/media/geda/rf_cascade_figure2.jpg
new file mode 100644
index 0000000..b271a65
Binary files /dev/null and b/docs/wiki/media/geda/rf_cascade_figure2.jpg differ
diff --git a/docs/wiki/media/geda/schematicfinished.png b/docs/wiki/media/geda/schematicfinished.png
new file mode 100644
index 0000000..b3fcf5e
Binary files /dev/null and b/docs/wiki/media/geda/schematicfinished.png differ
diff --git a/docs/wiki/media/geda/schematicfinished2.png b/docs/wiki/media/geda/schematicfinished2.png
new file mode 100644
index 0000000..6a381b7
Binary files /dev/null and b/docs/wiki/media/geda/schematicfinished2.png differ
diff --git a/docs/wiki/media/geda/simple1.png b/docs/wiki/media/geda/simple1.png
new file mode 100644
index 0000000..a7fce1e
Binary files /dev/null and b/docs/wiki/media/geda/simple1.png differ
diff --git a/docs/wiki/media/geda/status_screenshot.jpg b/docs/wiki/media/geda/status_screenshot.jpg
new file mode 100644
index 0000000..394ef3a
Binary files /dev/null and b/docs/wiki/media/geda/status_screenshot.jpg differ
diff --git a/docs/wiki/media/geda/suse_electronics_menu.png b/docs/wiki/media/geda/suse_electronics_menu.png
new file mode 100644
index 0000000..16881ed
Binary files /dev/null and b/docs/wiki/media/geda/suse_electronics_menu.png differ
diff --git a/docs/wiki/media/geda/switcap_figure1.jpg b/docs/wiki/media/geda/switcap_figure1.jpg
new file mode 100644
index 0000000..5313e53
Binary files /dev/null and b/docs/wiki/media/geda/switcap_figure1.jpg differ
diff --git a/docs/wiki/media/geda/switcap_figure2.jpg b/docs/wiki/media/geda/switcap_figure2.jpg
new file mode 100644
index 0000000..b9e0f6a
Binary files /dev/null and b/docs/wiki/media/geda/switcap_figure2.jpg differ
diff --git a/docs/wiki/media/geda/switcap_figure3.jpg b/docs/wiki/media/geda/switcap_figure3.jpg
new file mode 100644
index 0000000..6617c00
Binary files /dev/null and b/docs/wiki/media/geda/switcap_figure3.jpg differ
diff --git a/docs/wiki/media/geda/switcap_figure4.jpg b/docs/wiki/media/geda/switcap_figure4.jpg
new file mode 100644
index 0000000..639985b
Binary files /dev/null and b/docs/wiki/media/geda/switcap_figure4.jpg differ
diff --git a/docs/wiki/media/geda/symbol_7400-1.png b/docs/wiki/media/geda/symbol_7400-1.png
new file mode 100644
index 0000000..e817f55
Binary files /dev/null and b/docs/wiki/media/geda/symbol_7400-1.png differ
diff --git a/docs/wiki/media/geda/symbol_7400-1_hidden.png b/docs/wiki/media/geda/symbol_7400-1_hidden.png
new file mode 100644
index 0000000..22807da
Binary files /dev/null and b/docs/wiki/media/geda/symbol_7400-1_hidden.png differ
diff --git a/docs/wiki/media/geda/terminal_screenshot_001.jpg b/docs/wiki/media/geda/terminal_screenshot_001.jpg
new file mode 100644
index 0000000..1b28256
Binary files /dev/null and b/docs/wiki/media/geda/terminal_screenshot_001.jpg differ
diff --git a/docs/wiki/media/geda/two-sch-1.png b/docs/wiki/media/geda/two-sch-1.png
new file mode 100644
index 0000000..74b59c9
Binary files /dev/null and b/docs/wiki/media/geda/two-sch-1.png differ
diff --git a/docs/wiki/media/geda/two-sch-2.png b/docs/wiki/media/geda/two-sch-2.png
new file mode 100644
index 0000000..9448d26
Binary files /dev/null and b/docs/wiki/media/geda/two-sch-2.png differ
diff --git a/docs/wiki/media/geda/warmup_add_component.png b/docs/wiki/media/geda/warmup_add_component.png
new file mode 100644
index 0000000..cfd5794
Binary files /dev/null and b/docs/wiki/media/geda/warmup_add_component.png differ
diff --git a/docs/wiki/media/geda/warmup_gschem01.png b/docs/wiki/media/geda/warmup_gschem01.png
new file mode 100644
index 0000000..1191d90
Binary files /dev/null and b/docs/wiki/media/geda/warmup_gschem01.png differ
diff --git a/docs/wiki/media/geda/warmup_gschem02.png b/docs/wiki/media/geda/warmup_gschem02.png
new file mode 100644
index 0000000..af49239
Binary files /dev/null and b/docs/wiki/media/geda/warmup_gschem02.png differ
diff --git a/docs/wiki/media/geda/warmup_gschem03.png b/docs/wiki/media/geda/warmup_gschem03.png
new file mode 100644
index 0000000..e9da8d3
Binary files /dev/null and b/docs/wiki/media/geda/warmup_gschem03.png differ
diff --git a/docs/wiki/media/tragesym/.gitignore b/docs/wiki/media/tragesym/.gitignore
new file mode 100644
index 0000000..23c1897
--- /dev/null
+++ b/docs/wiki/media/tragesym/.gitignore
@@ -0,0 +1,3 @@
+Makefile
+Makefile.in
+*~
diff --git a/docs/wiki/media/tragesym/Makefile.am b/docs/wiki/media/tragesym/Makefile.am
new file mode 100644
index 0000000..857988c
--- /dev/null
+++ b/docs/wiki/media/tragesym/Makefile.am
@@ -0,0 +1,13 @@
+
+
+docname=wiki
+docsdir = $(docdir)/$(docname)/media/tragesym
+
+SUBDIRS = tragesym
+
+docs_DATA = gschem_finished.png ooo_rearanged.png kpdf_pindescription.png acroread_selectiontable.png xemacs_rawselection.png gschem_showhidden.png template.txt kpdf_pinconfiguration.png template2.ods template.ods ooo_attributes.png ooo_selection.png xemacs_modifiedselection.png ooo_changedpins.png template2.txt.src
+
+EXTRA_DIST = $(docs_DATA)
+
+MAINTAINERCLEANFILES = *.log core FILE *~ Makefile.in
+
diff --git a/docs/wiki/media/tragesym/acroread_selectiontable.png b/docs/wiki/media/tragesym/acroread_selectiontable.png
new file mode 100644
index 0000000..796cd9b
Binary files /dev/null and b/docs/wiki/media/tragesym/acroread_selectiontable.png differ
diff --git a/docs/wiki/media/tragesym/gschem_finished.png b/docs/wiki/media/tragesym/gschem_finished.png
new file mode 100644
index 0000000..ccd4d82
Binary files /dev/null and b/docs/wiki/media/tragesym/gschem_finished.png differ
diff --git a/docs/wiki/media/tragesym/gschem_showhidden.png b/docs/wiki/media/tragesym/gschem_showhidden.png
new file mode 100644
index 0000000..8a2a067
Binary files /dev/null and b/docs/wiki/media/tragesym/gschem_showhidden.png differ
diff --git a/docs/wiki/media/tragesym/kpdf_pinconfiguration.png b/docs/wiki/media/tragesym/kpdf_pinconfiguration.png
new file mode 100644
index 0000000..72fc148
Binary files /dev/null and b/docs/wiki/media/tragesym/kpdf_pinconfiguration.png differ
diff --git a/docs/wiki/media/tragesym/kpdf_pindescription.png b/docs/wiki/media/tragesym/kpdf_pindescription.png
new file mode 100644
index 0000000..6c5b49e
Binary files /dev/null and b/docs/wiki/media/tragesym/kpdf_pindescription.png differ
diff --git a/docs/wiki/media/tragesym/ooo_attributes.png b/docs/wiki/media/tragesym/ooo_attributes.png
new file mode 100644
index 0000000..3e6fdc8
Binary files /dev/null and b/docs/wiki/media/tragesym/ooo_attributes.png differ
diff --git a/docs/wiki/media/tragesym/ooo_changedpins.png b/docs/wiki/media/tragesym/ooo_changedpins.png
new file mode 100644
index 0000000..5446849
Binary files /dev/null and b/docs/wiki/media/tragesym/ooo_changedpins.png differ
diff --git a/docs/wiki/media/tragesym/ooo_rearanged.png b/docs/wiki/media/tragesym/ooo_rearanged.png
new file mode 100644
index 0000000..100395b
Binary files /dev/null and b/docs/wiki/media/tragesym/ooo_rearanged.png differ
diff --git a/docs/wiki/media/tragesym/ooo_selection.png b/docs/wiki/media/tragesym/ooo_selection.png
new file mode 100644
index 0000000..41a6a11
Binary files /dev/null and b/docs/wiki/media/tragesym/ooo_selection.png differ
diff --git a/docs/wiki/media/tragesym/template.ods b/docs/wiki/media/tragesym/template.ods
new file mode 100644
index 0000000..425e9af
Binary files /dev/null and b/docs/wiki/media/tragesym/template.ods differ
diff --git a/docs/wiki/media/tragesym/template.txt b/docs/wiki/media/tragesym/template.txt
new file mode 100644
index 0000000..ac3839e
--- /dev/null
+++ b/docs/wiki/media/tragesym/template.txt
@@ -0,0 +1,55 @@
+# 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/tragesym/template2.ods b/docs/wiki/media/tragesym/template2.ods
new file mode 100644
index 0000000..f414b79
Binary files /dev/null and b/docs/wiki/media/tragesym/template2.ods differ
diff --git a/docs/wiki/media/tragesym/template2.txt.src b/docs/wiki/media/tragesym/template2.txt.src
new file mode 100644
index 0000000..4e507c3
--- /dev/null
+++ b/docs/wiki/media/tragesym/template2.txt.src
@@ -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
+#-----------------------------------------------------
diff --git a/docs/wiki/media/tragesym/tragesym/.gitignore b/docs/wiki/media/tragesym/tragesym/.gitignore
new file mode 100644
index 0000000..23c1897
--- /dev/null
+++ b/docs/wiki/media/tragesym/tragesym/.gitignore
@@ -0,0 +1,3 @@
+Makefile
+Makefile.in
+*~
diff --git a/docs/wiki/media/tragesym/tragesym/Makefile.am b/docs/wiki/media/tragesym/tragesym/Makefile.am
new file mode 100644
index 0000000..f9a94aa
--- /dev/null
+++ b/docs/wiki/media/tragesym/tragesym/Makefile.am
@@ -0,0 +1,11 @@
+
+
+docname=wiki
+docsdir = $(docdir)/$(docname)/media/tragesym/tragesym
+
+docs_DATA = kpdf_pindescription.png
+
+EXTRA_DIST = $(docs_DATA)
+
+MAINTAINERCLEANFILES = *.log core FILE *~ Makefile.in
+
diff --git a/docs/wiki/media/tragesym/tragesym/kpdf_pindescription.png b/docs/wiki/media/tragesym/tragesym/kpdf_pindescription.png
new file mode 100644
index 0000000..6c5b49e
Binary files /dev/null and b/docs/wiki/media/tragesym/tragesym/kpdf_pindescription.png differ
diff --git a/docs/wiki/media/tragesym/xemacs_modifiedselection.png b/docs/wiki/media/tragesym/xemacs_modifiedselection.png
new file mode 100644
index 0000000..dd2ce2d
Binary files /dev/null and b/docs/wiki/media/tragesym/xemacs_modifiedselection.png differ
diff --git a/docs/wiki/media/tragesym/xemacs_rawselection.png b/docs/wiki/media/tragesym/xemacs_rawselection.png
new file mode 100644
index 0000000..8a86702
Binary files /dev/null and b/docs/wiki/media/tragesym/xemacs_rawselection.png differ
diff --git a/docs/wiki/media/wiki/.gitignore b/docs/wiki/media/wiki/.gitignore
new file mode 100644
index 0000000..23c1897
--- /dev/null
+++ b/docs/wiki/media/wiki/.gitignore
@@ -0,0 +1,3 @@
+Makefile
+Makefile.in
+*~
diff --git a/docs/wiki/media/wiki/Makefile.am b/docs/wiki/media/wiki/Makefile.am
new file mode 100644
index 0000000..5b6761f
--- /dev/null
+++ b/docs/wiki/media/wiki/Makefile.am
@@ -0,0 +1,10 @@
+
+docname=wiki
+docsdir = $(docdir)/$(docname)/media/wiki
+
+docs_DATA = dokuwiki-128.png
+
+EXTRA_DIST = $(docs_DATA)
+
+MAINTAINERCLEANFILES = *.log core FILE *~ Makefile.in
+
diff --git a/docs/wiki/media/wiki/dokuwiki-128.png b/docs/wiki/media/wiki/dokuwiki-128.png
new file mode 100644
index 0000000..b2306ac
Binary files /dev/null and b/docs/wiki/media/wiki/dokuwiki-128.png differ
diff --git a/docs/wiki/pcb-projects.html b/docs/wiki/pcb-projects.html
index 313e973..f546a40 100644
--- a/docs/wiki/pcb-projects.html
+++ b/docs/wiki/pcb-projects.html
@@ -1,27 +1,16 @@
<!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">
+<html>
<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
- <title>pcb-projects</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2008-03-21T07:21:01-0400" />
-<meta name="keywords" content="pcb-projects" />
-<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/pcb-projects?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/pcb-projects"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/pcb-projects"; />
-<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">
+
@@ -30,58 +19,6 @@
</div>
-<h5><a name="improve_handling_of_non-copper_layers_in_pcb" id="improve_handling_of_non-copper_layers_in_pcb">Improve handling of non-copper layers in pcb</a></h5>
-<div class="level5">
-
-<p>
- PCBâ??s support for non-copper layers needs improvement. In this project, you would add support for more easily-editable non-copper layers. These non-copper layers would be used for things like keepout regions, assembly drawing, and an actual board outline layer that is not just a copper layer. For more thoughts on the issue of layers in PCB, please see database.txt and keepouts.txt
-</p>
-
-<p>
-Difficulty = 2
-</p>
-
-</div>
-
-<h5><a name="pcb_drc_interface_improvements" id="pcb_drc_interface_improvements">PCB DRC interface improvements</a></h5>
-<div class="level5">
-
-<p>
- Improve the DRC interface for PCB. Perhaps have a DRC layer that gets generated when you run DRC. Then you could have an interface that lets you step through them and see on that layer, exactly what failed. Maybe this could be combined with making the DRC checks more unit testable.
-</p>
-
-<p>
-Difficulty = 2
-</p>
-
-</div>
-
-<h5><a name="pcb_autorouter" id="pcb_autorouter">PCB Autorouter</a></h5>
-<div class="level5">
-
-<p>
- PCB currently incorporates a simple autorouter. However, a topological autorouter would represent a significant improvement over the existing autorouter. In this ambitious project, the student would create a topological autorouter for PCB.
-</p>
-
-<p>
-Difficulty = 5
-</p>
-
-</div>
-
-<h5><a name="improved_and_formalized_mechanism_for_forward_backward_annotation" id="improved_and_formalized_mechanism_for_forward_backward_annotation">Improved and formalized mechanism for forward/backward annotation</a></h5>
-<div class="level5">
-
-<p>
- Add hooks into gschem needed to fully support things like backannotation of simulation results and click-to-plot results. Specifically, this would enable you to draw a schematic in gschem, then simulate it in ngspice without leaving gschem. The simulation plots would then appear in a graphical pop-up window.
-</p>
-
-<p>
-Difficulty = 3
-</p>
-
-</div>
-
<h5><a name="ipc_footprint_calculator" id="ipc_footprint_calculator">IPC Footprint Calculator</a></h5>
<div class="level5">
@@ -133,6 +70,5 @@ Difficulty = 1
</p>
</div>
-</div>
</body>
</html>
diff --git a/docs/wiki/playground-playground.html b/docs/wiki/playground-playground.html
new file mode 100644
index 0000000..4f6c787
--- /dev/null
+++ b/docs/wiki/playground-playground.html
@@ -0,0 +1,99 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+<p>
+Playground. <img src="images/smileys/icon_fun.gif" align="middle" alt="^_^" /><br/>
+ <em class="u"><em><strong>It is a simple text.</strong></em></em> <pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">
+<linux:/home/zabbix$ <strong>ls -l | grep</strong>
+drwxr-xr-x 2 zabbix zabbix 4096 Mar 23 2004 autom4te.cache
+drwxr-xr-x 2 zabbix zabbix 4096 Oct 4 2004 bin
+drwxr-xr-x 5 zabbix zabbix 4096 Mar 23 2004 create
+drwxr-xr-x 2 zabbix zabbix 4096 Mar 23 2004 doc
+</font></pre>
+</p>
+
+<p>
+A schematic symbol for gschem, that I made is for the 36-pin Centronics connector.<br/>
+ See the picture!<br/>
+ But I donâ??t know, how to upload a picture?
+</p>
+<div class="box round orange" style="width: 80%; ">
+ <b class='xtop'><b class='xb1'></b><b class='xb2'></b><b class='xb3'></b><b class='xb4'></b></b>
+ <div class='xbox'>
+<p class='box_title'>a title</p>
+<div class='box_content'> the box contents</div>
+ </div>
+ <b class='xbottom'><b class='xb4'></b><b class='xb3'></b><b class='xb2'></b><b class='xb1'></b></b>
+</div>
+<div class="box left blue" style="width: 50%; ">
+ <b class='xtop'><b class='xb1'></b><b class='xb2'></b><b class='xb3'></b><b class='xb4'></b></b>
+ <div class='xbox'>
+<div class='box_content'>the box contents</div>
+<p class='box_caption'>a caption</p>
+ </div>
+ <b class='xbottom'><b class='xb4'></b><b class='xb3'></b><b class='xb2'></b><b class='xb1'></b></b>
+</div>
+<div class="box round" style="width: 60%; background-color: rgb(255,204,204); border-color: rgb(255,102,0);">
+ <b class='xtop'><b class='xb1' style="background-color: rgb(255,204,204); border-color: rgb(255,102,0);"></b><b class='xb2' style="background-color: rgb(255,204,204); border-color: rgb(255,102,0);"></b><b class='xb3' style="background-color: rgb(255,204,204); border-color: rgb(255,102,0);"></b><b class='xb4' style="background-color: rgb(255,204,204); border-color: rgb(255,102,0);"></b></b>
+ <div class='xbox' style="background-color: rgb(255,204,204); border-color: rgb(255,102,0);">
+<p class='box_title'style="background-color: rgb(255,204,153);">title</p>
+<div class='box_content'style="background-color: rgb(255,153,153); border-color: rgb(255,102,0)">the box contents></div>
+<p class='box_caption'style="background-color: rgb(255,204,153);">caption</p>
+ </div>
+ <b class='xbottom'><b class='xb4' style="background-color: rgb(255,204,204); border-color: rgb(255,102,0);"></b><b class='xb3' style="background-color: rgb(255,204,204); border-color: rgb(255,102,0);"></b><b class='xb2' style="background-color: rgb(255,204,204); border-color: rgb(255,102,0);"></b><b class='xb1' style="background-color: rgb(255,204,204); border-color: rgb(255,102,0);"></b></b>
+</div>
+<div class="box green">
+ <b class='xtop'><b class='xb1'></b><b class='xb2'></b><b class='xb3'></b><b class='xb4'></b></b>
+ <div class='xbox'>
+<div class='box_content'> this is also boxed </div>
+<p class='box_caption'>boxed & captioned</p>
+ </div>
+ <b class='xbottom'><b class='xb4'></b><b class='xb3'></b><b class='xb2'></b><b class='xb1'></b></b>
+</div>
+<div class="box">
+ <b class='xtop'><b class='xb1'></b><b class='xb2'></b><b class='xb3'></b><b class='xb4'></b></b>
+ <div class='xbox'>
+<div class='box_content'> the box contents 1 2 3 4 5 </div>
+ </div>
+ <b class='xbottom'><b class='xb4'></b><b class='xb3'></b><b class='xb2'></b><b class='xb1'></b></b>
+</div>
+<div class="box">
+ <b class='xtop'><b class='xb1'></b><b class='xb2'></b><b class='xb3'></b><b class='xb4'></b></b>
+ <div class='xbox'>
+<p class='box_title'>Example box</p>
+<div class='box_content'> to test what is possible: <strong>NICE PLUGIN:</strong> You can <ul>
+<li class="level1"><div class="li"> make Lists</div>
+</li>
+<li class="level1"><div class="li"> other markup</div>
+</li>
+<li class="level1"><div class="li"> set the color of the box</div>
+</li>
+<li class="level1"><div class="li"> …</div>
+</li>
+</ul>
+
+<p>
+ looks good?
+</p>
+</div>
+ </div>
+ <b class='xbottom'><b class='xb4'></b><b class='xb3'></b><b class='xb2'></b><b class='xb1'></b></b>
+</div>
+
+<p>
+Just testing if I can log in and edit.
+</p>
+</body>
+</html>
diff --git a/docs/wiki/playground-transistor_guide.html b/docs/wiki/playground-transistor_guide.html
new file mode 100644
index 0000000..f13fe82
--- /dev/null
+++ b/docs/wiki/playground-transistor_guide.html
@@ -0,0 +1,129 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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 <a href="playground-transistor_guide.html#special_cases" class="wikilink1" title="playground-transistor_guide.html">TO-92o</a> 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-] --></body>
+</html>
diff --git a/docs/wiki/print.css b/docs/wiki/print.css
new file mode 100644
index 0000000..77c82a5
--- /dev/null
+++ b/docs/wiki/print.css
@@ -0,0 +1,223 @@
+
+body {
+ font: 12pt "Lucida Grande", Verdana, Lucida, Helvetica, Arial, sans-serif;
+ background-color: White;
+ color: Black;
+}
+
+table {
+ font-size: 100%;
+ padding:0;
+ margin:0;
+}
+
+tr,td,th {padding:0; margin:0;}
+
+img {border:0}
+
+a {
+ color:#000000;
+ text-decoration:none;
+}
+
+
+div.meta {
+ clear:both;
+ margin-top: 1em;
+ font-size:70%;
+ text-align:right;
+}
+
+div.breadcrumbs{
+ display:none;
+}
+
+div.secedit{
+ display:none;
+}
+
+/* --------------------- Text formating -------------------------------- */
+
+/* external link */
+a.urlextern:after {
+ content: " [" attr(href) "]";
+ font-size: 90%;
+}
+
+/* interwiki link */
+a.interwiki:after {
+ content: " [" attr(href) "]";
+ font-size: 90%;
+}
+
+/* email link */
+a.mail:after {
+ content: " [" attr(href) "]";
+ font-size: 90%;
+}
+
+/* existing wikilink */
+a.wikilink1 {text-decoration:underline }
+
+/* the document */
+div.page {
+ text-align: justify;
+}
+
+/* general headline setup */
+h1, h2, h3, h4, h5 {
+ color: Black;
+ background-color: transparent;
+ font-family: "Lucida Grande", Verdana, Lucida, Helvetica, Arial, sans-serif;
+ font-size: 100%;
+ font-weight: normal;
+ margin-left: 0;
+ margin-right: 0;
+ margin-top: 0;
+ margin-bottom: 1em;
+ padding-left: 0;
+ padding-right: 0;
+ padding-top: 0.5em;
+ padding-bottom: 0;
+ border-bottom: 1px solid #000000;
+ clear:left;
+}
+
+/* special headlines */
+h1 {font-size: 160%; font-weight: bold;}
+h2 {font-size: 150%; }
+h3 {font-size: 140%; border-bottom: none; font-weight: bold;}
+h4 {font-size: 120%; border-bottom: none; font-weight: bold;}
+h5 {font-size: 100%; border-bottom: none; font-weight: bold;}
+
+/* embedded images */
+img.media {
+ margin: 3px;
+}
+
+img.medialeft {
+ border: 0;
+ float: left;
+ margin: 0 1.5em 0 0;
+}
+
+img.mediaright {
+ border: 0;
+ float: right;
+ margin: 0 0 0 1.5em;
+}
+
+/* unordered lists */
+ul {
+ line-height: 1.5em;
+ list-style-type: square;
+ margin: 0 0 1.0em 1.5em;
+ padding: 0;
+
+}
+
+/* ordered lists */
+ol {
+ line-height: 1.5em;
+ margin: 0 0 1.0em 1.5em;
+ padding: 0;
+ font-weight: bold;
+}
+
+/* the list items overriding the ol definition */
+span.li {
+ font-weight: normal;
+}
+
+/* code blocks by indention */
+pre.pre {
+ font-size: 8pt;
+ padding: 0.5em;
+ border: 1px dashed #000000;
+ color: Black;
+ overflow: visible;
+}
+
+/* code blocks by code tag */
+pre.code {
+ font-size: 8pt;
+ padding: 0.5em;
+ border: 1px dashed #000000;
+ color: Black;
+ overflow: visible;
+}
+
+/* inline code words */
+code {
+ font-size: 120%;
+}
+
+/* code blocks by file tag */
+pre.file {
+ font-size: 8pt;
+ padding: 0.5em;
+ border: 1px dotted #000000;
+ color: Black;
+ overflow: visible;
+}
+
+/* footnotes */
+div.footnotes{
+ clear:both;
+ border-top: 1px solid #000000;
+ padding-left: 1em;
+ margin-top: 1em;
+}
+
+div.fn{
+ font-size:90%;
+}
+
+a.fn_top{
+ vertical-align:super;
+ font-size:80%;
+}
+
+a.fn_bot{
+ vertical-align:super;
+ font-size:80%;
+ font-weight:bold;
+}
+
+acronym{
+ border: 0;
+}
+
+/* ---------- inline tables ------------------- */
+
+table.inline {
+ font-size: 80%;
+ background-color: #ffffff;
+ border-spacing: 0px;
+ border-collapse: collapse;
+}
+
+table.inline th {
+ padding: 3px;
+ border: 1px solid #000000;
+ border-bottom: 2px solid #000000;
+}
+
+table.inline td {
+ padding: 3px;
+ border: 1px solid #000000;
+}
+
+.leftalign{
+ text-align: left;
+}
+
+.centeralign{
+ text-align: center;
+}
+
+.rightalign{
+ text-align: right;
+}
+
+.toc, .footerinc, .header, .bar, .user {display:none}
diff --git a/docs/wiki/start.html b/docs/wiki/start.html
new file mode 100644
index 0000000..d876a26
--- /dev/null
+++ b/docs/wiki/start.html
@@ -0,0 +1,234 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#geda_project_wiki" class="toc">gEDA Project Wiki</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#what_is_geda" class="toc">What is gEDA?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#official_project_documentation" class="toc">Official Project documentation</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#faqs_and_informal_project_documentation" class="toc">FAQs and Informal Project Documentation</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#developer_documentation" class="toc">Developer Documentation</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#talks" class="toc">Talks</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#google_summer_of_code" class="toc">Google Summer of Code</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#translations" class="toc">Translations</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#geda_users" class="toc">gEDA Users</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#about_this_wiki" class="toc">About this Wiki</a></span></div></li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="geda_project_wiki" id="geda_project_wiki">gEDA Project Wiki</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "gEDA Project Wiki" [2-35] -->
+<h2><a name="what_is_geda" id="what_is_geda">What is gEDA?</a></h2>
+<div class="level2">
+
+<p>
+ The <a href="http://www.gpleda.org"; class="urlextern" title="http://www.gpleda.org"; rel="nofollow">gEDA project</a> is developing a full <acronym title="GNU General Public License">GPL</acronym>â??d suite and toolkit of Electronic Design Automation tools. These tools are used for electrical circuit design, schematic capture, simulation, prototyping, and production. Currently, the gEDA project offers a mature suite of free software applications for electronics design, including schematic capture, attribute management, bill of materials (BOM) generation, netlisting into over 20 netlist formats, analog and digital simulation, and printed circuit board (PCB) layout.
+</p>
+
+<p>
+The tools involved in the Suite enable you to professional-quality design of low- to mid-level complexity. Using the gEDA tools, you can create PCB of up to 8 layers (soon more) with an unlimited number of components and nets. The tools are suitable for use by students, educators, hobbyists, consultants, small businesses, and even in large corporations where an engineer might need to crank out a quick PC board (e.g. for a test stand) in a hurry.
+</p>
+
+<p>
+All of the software in the gEDA suite can be found on the <a href="http://www.gpleda.org/download.html"; class="urlextern" title="http://www.gpleda.org/download.html"; rel="nofollow">downloads page</a>.
+</p>
+
+</div>
+<!-- SECTION "What is gEDA?" [36-1175] -->
+<h2><a name="official_project_documentation" id="official_project_documentation">Official Project documentation</a></h2>
+<div class="level2">
+
+<p>
+These are the official project docs. They have been converted from LaTeX and <acronym title="HyperText Markup Language">HTML</acronym> documents into Wiki pages so that the gEDA community may more easily maintain them.
+</p>
+<ul>
+<li class="level1"><div class="li"> <a href="geda-documentation.html" class="wikilink1" title="geda-documentation.html">Documentation</a> : The latest versions of the gEDA Tool Suite documentation.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Official Project documentation" [1176-1478] -->
+<h2><a name="faqs_and_informal_project_documentation" id="faqs_and_informal_project_documentation">FAQs and Informal Project Documentation</a></h2>
+<div class="level2">
+
+<p>
+These are FAQs, HOWTOs, and tips/tricks to help you with the practical details of using the gEDA Suite. If you are having a problem, browse these pages first.
+</p>
+<ul>
+<li class="level1"><div class="li"> <a href="geda-faq.html" class="wikilink1" title="geda-faq.html">FAQ</a> : Frequently Asked Questions about the gEDA project itself.</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-installation.html" class="wikilink1" title="geda-installation.html">Installation</a> : gEDA installation HOWTO and <acronym title="Frequently Asked Questions">FAQ</acronym>.</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-glossary.html" class="wikilink1" title="geda-glossary.html">Glossary</a> : Glossary of terms that are specific to the gEDA Suite.</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-usage.html" class="wikilink1" title="geda-usage.html">Usage</a> : Questions about how to do electronic design using the gEDA toolset – information which applies to several or all tools in the gEDA Suite.</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-faq-gschem.html" class="wikilink1" title="geda-faq-gschem.html">FAQ-gschem</a> : Questions about installing, configuring, and using gschem. Also, questions about creating and using gschem symbols.</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-faq-attribs.html" class="wikilink1" title="geda-faq-attribs.html">FAQ-attribs</a> : Dealing with BOMs, DRCs, attribute management, and all that.</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-faq-gnetlist.html" class="wikilink1" title="geda-faq-gnetlist.html">FAQ-gnetlist</a> : Questions about installing, configuring, and using gnetlist.</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-faq-simulation.html" class="wikilink1" title="geda-faq-simulation.html">FAQ-simulation</a> : Questions about simulating your design using gEDA tools.</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-faq-gsch2pcb.html" class="wikilink1" title="geda-faq-gsch2pcb.html">FAQ-gsch2pcb</a> : How to take your design to layout using PCB.</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-faq-pcb.html" class="wikilink1" title="geda-faq-pcb.html">FAQ-pcb</a> : Questions about the printed circuit board tool â??pcbâ??.</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-pcb-quick_reference.html" class="wikilink1" title="geda-pcb-quick_reference.html">PCB-quick reference</a> : PCB Quick Reference Sheet.</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-pcb_tips.html" class="wikilink1" title="geda-pcb_tips.html">PCB tips</a> : Tips and tricks for using PCB.</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-pcb_footprints.html" class="wikilink1" title="geda-pcb_footprints.html">PCB footprints</a> : How to create, use and share footprints.</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-scg.html" class="wikilink1" title="geda-scg.html">scg</a> : gschem symbol creation guide.</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-guile_scripting.html" class="wikilink1" title="geda-guile_scripting.html">Guile scripting</a> : Guile functions & variables provided by the gEDA tools.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "FAQs and Informal Project Documentation" [1479-2986] -->
+<h2><a name="developer_documentation" id="developer_documentation">Developer Documentation</a></h2>
+<div class="level2">
+
+<p>
+The following pages are related to the day-to-day development of the gEDA suite:
+</p>
+<ul>
+<li class="level1"><div class="li"> <a href="http://www.gpleda.org/developer.html"; class="urlextern" title="http://www.gpleda.org/developer.html"; rel="nofollow"> developer.html</a> : Code repository, developer mailing list and list of developers.</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-todos.html" class="wikilink1" title="geda-todos.html">Todos</a> : For developers only: lists of pending project enhancements and todos.</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-tasks.html" class="wikilink1" title="geda-tasks.html">Tasks</a> : Top-level list of jobs/tasks that need help.</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-scm.html" class="wikilink1" title="geda-scm.html">SCM</a> : Information on gEDA/gafâ??s source control management (SCM) system and process.</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-release_engineering.html" class="wikilink1" title="geda-release_engineering.html">Release Engineering</a> : Description of various Release Engineering procedures.</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-devel-tips.html" class="wikilink1" title="geda-devel-tips.html">devel-tips</a> : For developers only: various tips and tricks when doing gEDA development.</div>
+</li>
+</ul>
+
+<p>
+ The following pages are work-in-progress discussions and/or brainstorming:
+</p>
+<ul>
+<li class="level1"><div class="li"> <a href="libgeda3.html" class="wikilink1" title="libgeda3.html">libgeda3</a> : For developers only: Discussion of <acronym title="Application Programming Interface">API</acronym> and design for a next generation libgeda.</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-circuit_simulation_improvements.html" class="wikilink1" title="geda-circuit_simulation_improvements.html">Circuit Simulation Improvements</a> : For developers only: Discussion on how to better integrate circuit simulations, gschem and gnetlist.</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-data_plotting_improvements.html" class="wikilink1" title="geda-data_plotting_improvements.html">Data Plotting Improvements</a> : For developers only: Discussion on how to better plot simulation data.</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-design_flow_and_hierarchy_roadmap.html" class="wikilink1" title="geda-design_flow_and_hierarchy_roadmap.html">Design Flow and Hierarchy Roadmap</a> : For users and developers: Discussion of wants for circuit design, reusing modules in a hierarchy.</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-pcb_funding_sow.html" class="wikilink1" title="geda-pcb_funding_sow.html"> PCB Funding SOW</a> : An SOW specifying improvements to PCB performed within a funding program.</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-format_translation.html" class="wikilink1" title="geda-format_translation.html">format translation</a> : Some notes on file format translation.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Developer Documentation" [2987-4465] -->
+<h2><a name="talks" id="talks">Talks</a></h2>
+<div class="level2">
+
+<p>
+These are slides of presentations done about gEDA. They provide a good top-level overview of the project for those who are interested.
+</p>
+<ul>
+<li class="level1"><div class="li"> <a href="http://geda.seul.org/talks/"; class="urlextern" title="http://geda.seul.org/talks/"; rel="nofollow">talks</a>: Various talks and presentations on gEDA </div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Talks" [4466-4706] -->
+<h2><a name="google_summer_of_code" id="google_summer_of_code">Google Summer of Code</a></h2>
+<div class="level2">
+
+<p>
+ The gEDA project regularly participates in the Google Summer of Code. The gEDA project was not accepted into GSoC 2009, hopefully we will do better next year.
+</p>
+
+<p>
+Here is this yearâ??s Google Summer of Code page:
+</p>
+<ul>
+<li class="level1"><div class="li"> <a href="gsoc2009.html" class="wikilink1" title="gsoc2009.html">2009</a></div>
+</li>
+</ul>
+
+<p>
+ Here are archived instructions and ideas from previous years:
+</p>
+<ul>
+<li class="level1"><div class="li"> <a href="gsoc2007.html" class="wikilink1" title="gsoc2007.html">2007</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="gsoc2008.html" class="wikilink1" title="gsoc2008.html">2008</a></div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Google Summer of Code" [4707-5086] -->
+<h2><a name="translations" id="translations">Translations</a></h2>
+<div class="level2">
+<ul>
+<li class="level1"><div class="li"> En français, cela débute <a href="start_fr.html" class="wikilink1" title="start_fr.html">ici</a>.</div>
+</li>
+<li class="level1"><div class="li"> Spanish language <a href="start_es.html" class="wikilink1" title="start_es.html">links</a></div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Translations" [5087-5203] -->
+<h2><a name="geda_users" id="geda_users">gEDA Users</a></h2>
+<div class="level2">
+
+<p>
+Users may discuss development, help, installation, and working tips through the <a href="http://www.gpleda.org/mailinglists.html"; class="urlextern" title="http://www.gpleda.org/mailinglists.html"; rel="nofollow">mailing lists</a>.
+</p>
+
+<p>
+There is also a gEDA <acronym title="Internet Relay Chat">IRC</acronym> channel at <strong>irc.seul.org/6667</strong> on the <strong>#geda</strong> channel. Sometimes this channel is full of activity and sometimes it is quite silent. Please be patient when asking questions in the <acronym title="Internet Relay Chat">IRC</acronym> channel.
+</p>
+
+<p>
+The so-called â??Free Dogâ?? organization ( <a href="http://freeedaug.org/"; class="urlextern" title="http://freeedaug.org/"; rel="nofollow">Freeedaug</a> ) meets in the Boston area and discusses gEDA and related topics.
+</p>
+
+</div>
+<!-- SECTION "gEDA Users" [5204-5736] -->
+<h2><a name="about_this_wiki" id="about_this_wiki">About this Wiki</a></h2>
+<div class="level2">
+
+<p>
+This section of the gEDA website is dedicated to documentation that is contributed by a multitude of authors, including users. In particular, it should grow into a resource of information for those who just started to work with the tools.
+</p>
+
+<p>
+Anyone is welcome to contribute. Unlike Wikipedia there is no button to create a login by yourself. This is because nobody at the gEDA site has the nerves to deal with anonymous vandalism. Consequently, you have to write an email to the site admin (ahvezda AT geda.seul.org) to gain access. He will gladly send you a login.
+</p>
+
+</div>
+<!-- SECTION "About this Wiki" [5737-] --></body>
+</html>
diff --git a/docs/wiki/start_es.html b/docs/wiki/start_es.html
index 22ace54..540ce33 100644
--- a/docs/wiki/start_es.html
+++ b/docs/wiki/start_es.html
@@ -1,27 +1,16 @@
<!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">
+<html>
<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
- <title>start_es</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-08-23T14:48:11-0400" />
-<meta name="keywords" content="start_es" />
-<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/start_es?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/start_es"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/start_es"; />
-<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">
@@ -51,20 +40,20 @@
</p>
</div>
-<!-- SECTION "Traducciones" [53-173] -->
+<!-- SECTION "Traducciones" [53-174] -->
<h2><a name="tutoriales" id="tutoriales">Tutoriales</a></h2>
<div class="level2">
<p>
- <a href="http://slcolombia.org/ProyectoTale/Tutoriales/geda"; class="urlextern" title="http://slcolombia.org/ProyectoTale/Tutoriales/geda"; rel="nofollow"> Tutorial de gEDA</a>
+ <a href="http://el-directorio.org/ProyectoTale/Tutoriales/geda"; class="urlextern" title="http://el-directorio.org/ProyectoTale/Tutoriales/geda"; rel="nofollow"> Tutorial de gEDA</a>
</p>
<p>
-<a href="http://slcolombia.org/ProyectoTale/Tutoriales/gnucap"; class="urlextern" title="http://slcolombia.org/ProyectoTale/Tutoriales/gnucap"; rel="nofollow"> Tutorial de gnucap</a>
+<a href="http://el-directorio.org/ProyectoTale/Tutoriales/gnucap"; class="urlextern" title="http://el-directorio.org/ProyectoTale/Tutoriales/gnucap"; rel="nofollow"> Tutorial de gnucap</a>
</p>
</div>
-<!-- SECTION "Tutoriales" [174-351] -->
+<!-- SECTION "Tutoriales" [175-358] -->
<h2><a name="otros" id="otros">Otros</a></h2>
<div class="level2">
@@ -81,6 +70,5 @@
</p>
</div>
-<!-- SECTION "Otros" [352-] --></div>
-</body>
+<!-- SECTION "Otros" [359-] --></body>
</html>
diff --git a/docs/wiki/start_fr.html b/docs/wiki/start_fr.html
index ba5c00a..b629fc9 100644
--- a/docs/wiki/start_fr.html
+++ b/docs/wiki/start_fr.html
@@ -1,27 +1,16 @@
<!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">
+<html>
<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
- <title>start_fr</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="keywords" content="start_fr" />
-<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/start_fr?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="; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/start_fr"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/start_fr"; />
-<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">
@@ -49,7 +38,7 @@
<div class="level2">
<p>
- Le <a href="http://geda.seul.org/"; class="urlextern" title="http://geda.seul.org"; rel="nofollow">projet gEDA</a> est de développer une suite complète dâ??outils <acronym title="GNU General Public License">GPL</acronym> de « Electronic Design Automation ». Ces outils sont utilisés pour la conception de circuits électriques, de saisie de schémas, de simulation, de prototypage et de produciton. Le projet gEDA offre actuellement une suite mature dâ??applications de logiciels libres pour la conception électronique, incluant le la saisie de schémas, la gestion dâ??attributs, la génération de bill of materials (BOM), le netlisting dans plus de 20 formats de netlist, la simulation analogique et numérique et le placement sur circuit imprimé « printed circuit board (PCB) ».
+ Le <a href="http://geda.seul.org"; class="urlextern" title="http://geda.seul.org"; rel="nofollow">projet gEDA</a> est de développer une suite complète dâ??outils <acronym title="GNU General Public License">GPL</acronym> de « Electronic Design Automation ». Ces outils sont utilisés pour la conception de circuits électriques, de saisie de schémas, de simulation, de prototypage et de produciton. Le projet gEDA offre actuellement une suite mature dâ??applications de logiciels libres pour la conception électronique, incluant le la saisie de schémas, la gestion dâ??attributs, la génération de bill of materials (BOM), le netlisting dans plus de 20 formats de netlist, la simulation analogique et numérique et le placement sur circuit imprimé « printed circuit board (PCB) ».
</p>
<p>
@@ -69,7 +58,7 @@ Tous les logiciels de la suite gEDA peuvent être trouvés sur la <a href="http:
Ce sont les docs officielles du projet. Elles ont été converties depuis des documents LaTeX et <acronym title="HyperText Markup Language">HTML</acronym> en des pages Wiki de telle manière que la communauté gEDA puisse les maintenir plus facilement.
</p>
<ul>
-<li class="level1"><div class="li"> <a href="001geda_documentation.html" class="wikilink1" title="geda:documentation.fr">Documentation.fr</a> : Les dernières versions de la documentation de la Suite dâ??Outils de gEDA.</div>
+<li class="level1"><div class="li"> <a href="geda-documentation.fr.html" class="wikilink1" title="geda-documentation.fr.html">Documentation.fr</a> : Les dernières versions de la documentation de la Suite dâ??Outils de gEDA.</div>
</li>
</ul>
@@ -82,33 +71,33 @@ Ce sont les docs officielles du projet. Elles ont été converties depuis des do
Ce sont les <acronym title="Frequently Asked Questions">FAQ</acronym>, les HOWTO et les trucs/astuces pour vous aider avec les détails pratiques de lâ??utilisation de la Suite gEDA. Si vous avez un problème, naviguez dâ??abord sur ces pages.
</p>
<ul>
-<li class="level1"><div class="li"> <a href="001geda_faq.html" class="wikilink1" title="geda:faq.fr">FAQ.fr</a> : Questions les plus fréquement posées sur le projet gEDA lui-même.</div>
+<li class="level1"><div class="li"> <a href="geda-faq.fr.html" class="wikilink1" title="geda-faq.fr.html">FAQ.fr</a> : Questions les plus fréquement posées sur le projet gEDA lui-même.</div>
</li>
-<li class="level1"><div class="li"> <a href="001geda_installation.html" class="wikilink1" title="geda:installation.fr">Installation.fr</a> : HOWTO et <acronym title="Frequently Asked Questions">FAQ</acronym> de lâ??installation de gEDA.</div>
+<li class="level1"><div class="li"> <a href="geda-installation.fr.html" class="wikilink1" title="geda-installation.fr.html">Installation.fr</a> : HOWTO et <acronym title="Frequently Asked Questions">FAQ</acronym> de lâ??installation de gEDA.</div>
</li>
-<li class="level1"><div class="li"> <a href="geda_glossaire.html" class="wikilink1" title="geda:glossaire.fr">Glossaire.fr</a> : Glossaire de termes qui sont spécifiques à la Suite gEDA</div>
+<li class="level1"><div class="li"> <a href="geda-glossaire.fr.html" class="wikilink1" title="geda-glossaire.fr.html">Glossaire.fr</a> : Glossaire de termes qui sont spécifiques à la Suite gEDA</div>
</li>
-<li class="level1"><div class="li"> <a href="001geda_usage.html" class="wikilink1" title="geda:usage.fr">Usage.fr</a> : Questions sur la manière dâ??effectuer de la conception électronique en utilisant le jeu dâ??outils – informations qui sâ??appliquent à plusieurs ou à tous les outils de la Suite de gEDA.</div>
+<li class="level1"><div class="li"> <a href="geda-usage.fr.html" class="wikilink1" title="geda-usage.fr.html">Usage.fr</a> : Questions sur la manière dâ??effectuer de la conception électronique en utilisant le jeu dâ??outils – informations qui sâ??appliquent à plusieurs ou à tous les outils de la Suite de gEDA.</div>
</li>
-<li class="level1"><div class="li"> <a href="001geda_faq-gschem.html" class="wikilink1" title="geda:faq-gschem.fr">FAQ-gschem.fr</a> : Questions sur lâ??installation, la configuration et lâ??utilisation de gschem. De même, les questions sur la création et lâ??utilisation de symboles avec gschem.</div>
+<li class="level1"><div class="li"> <a href="geda-faq-gschem.fr.html" class="wikilink1" title="geda-faq-gschem.fr.html">FAQ-gschem.fr</a> : Questions sur lâ??installation, la configuration et lâ??utilisation de gschem. De même, les questions sur la création et lâ??utilisation de symboles avec gschem.</div>
</li>
-<li class="level1"><div class="li"> <a href="001geda_faq-attribs.html" class="wikilink1" title="geda:faq-attribs.fr">FAQ-attribs.fr</a> : De lâ??utilisation des BOM, des DRC, de la gestion des attributs et ainsi de suite.</div>
+<li class="level1"><div class="li"> <a href="geda-faq-attribs.fr.html" class="wikilink1" title="geda-faq-attribs.fr.html">FAQ-attribs.fr</a> : De lâ??utilisation des BOM, des DRC, de la gestion des attributs et ainsi de suite.</div>
</li>
-<li class="level1"><div class="li"> <a href="001geda_faq-gnetlist.html" class="wikilink1" title="geda:faq-gnetlist.fr">FAQ-gnetlist.fr</a> : Questions sur lâ??installation, la configuration et lâ??utilisation de gnetlist.</div>
+<li class="level1"><div class="li"> <a href="geda-faq-gnetlist.fr.html" class="wikilink1" title="geda-faq-gnetlist.fr.html">FAQ-gnetlist.fr</a> : Questions sur lâ??installation, la configuration et lâ??utilisation de gnetlist.</div>
</li>
-<li class="level1"><div class="li"> <a href="001geda_faq-simulation.html" class="wikilink1" title="geda:faq-simulation.fr">FAQ-simulation.fr</a> : Questions sur la simulation de votre schéma en utilisant les outils gEDA.</div>
+<li class="level1"><div class="li"> <a href="geda-faq-simulation.fr.html" class="wikilink1" title="geda-faq-simulation.fr.html">FAQ-simulation.fr</a> : Questions sur la simulation de votre schéma en utilisant les outils gEDA.</div>
</li>
-<li class="level1"><div class="li"> <a href="001geda_faq-gsch2pcb.html" class="wikilink1" title="geda:faq-gsch2pcb.fr">FAQ-gsch2pcb.fr</a> : Comment transformer votre schéma en un circuit avec PCB.</div>
+<li class="level1"><div class="li"> <a href="geda-faq-gsch2pcb.fr.html" class="wikilink1" title="geda-faq-gsch2pcb.fr.html">FAQ-gsch2pcb.fr</a> : Comment transformer votre schéma en un circuit avec PCB.</div>
</li>
-<li class="level1"><div class="li"> <a href="001geda_pcb_tips.html" class="wikilink1" title="geda:pcb_tips.fr">PCB tips.fr</a> : Trucs et astuces pour lâ??utilisation de PCB.</div>
+<li class="level1"><div class="li"> <a href="geda-pcb_tips.fr.html" class="wikilink1" title="geda-pcb_tips.fr.html">PCB tips.fr</a> : Trucs et astuces pour lâ??utilisation de PCB.</div>
</li>
-<li class="level1"><div class="li"> <a href="001geda_pcb-quick_reference.html" class="wikilink1" title="geda:pcb-quick_reference.fr">PCB-quick reference.fr</a> : PCB Quick Reference Sheet.</div>
+<li class="level1"><div class="li"> <a href="geda-pcb-quick_reference.fr.html" class="wikilink1" title="geda-pcb-quick_reference.fr.html">PCB-quick reference.fr</a> : PCB Quick Reference Sheet.</div>
</li>
-<li class="level1"><div class="li"> <a href="001geda_tasks.html" class="wikilink2" title="geda:tasks.fr">Tasks.fr</a> : Une liste des travaux/tâches prioritaires qui nécessitent de lâ??aide. </div>
+<li class="level1"><div class="li"> <a href="geda-tasks.fr.html" class="wikilink2" title="geda-tasks.fr.html">Tasks.fr</a> : Une liste des travaux/tâches prioritaires qui nécessitent de lâ??aide. </div>
</li>
-<li class="level1"><div class="li"> <a href="001geda_todos.html" class="wikilink2" title="geda:todos.fr">ToDos.fr</a> : Pour les développeurs seulement: liste dâ??améliorations de projets en cours et à faire.</div>
+<li class="level1"><div class="li"> <a href="geda-todos.fr.html" class="wikilink2" title="geda-todos.fr.html">ToDos.fr</a> : Pour les développeurs seulement: liste dâ??améliorations de projets en cours et à faire.</div>
</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:devel-tips"; class="wikilink1" title="geda:devel-tips">devel-tips</a> : Pour les développeurs seulement: divers trucs et astuces pour le développement de gEDA.</div>
+<li class="level1"><div class="li"> <a href="geda-devel-tips.html" class="wikilink1" title="geda-devel-tips.html">devel-tips</a> : Pour les développeurs seulement: divers trucs et astuces pour le développement de gEDA.</div>
</li>
</ul>
@@ -139,6 +128,5 @@ Toutes les contributions sont les bienvenues. Mais contrairement à wikipedia, i
</p>
</div>
-<!-- SECTION "Ã? propos du Wiki" [3861-] --></div>
-</body>
+<!-- SECTION "Ã? propos du Wiki" [3861-] --></body>
</html>
diff --git a/docs/wiki/style.css b/docs/wiki/style.css
new file mode 100644
index 0000000..4e19909
--- /dev/null
+++ b/docs/wiki/style.css
@@ -0,0 +1,44 @@
+div.clearer {clear: both; line-height: 0; height: 0;}
+
+div.error{
+ background: #ff6666 url(images/error.png) 0.5em 0px no-repeat;
+ font-size: 90%;
+ margin: 0px;
+ padding-left: 3em;
+}
+
+div.info{
+ background: #ffff66 url(images/info.png) 0.5em 0px no-repeat;
+ font-size: 90%;
+ margin: 0;
+ padding-left: 3em;
+}
+
+div.success{
+ background: #66ff66 url(images/thumbup.gif) 0.5em 0px no-repeat;
+ font-size: 90%;
+ margin: 0;
+ padding-left: 3em;
+}
+
+/* syntax highlighting code */
+.code .br0 { color: #66cc66; }
+.code .co1 { color: #808080; font-style: italic; }
+.code .co2 { color: #808080; font-style: italic; }
+.code .coMULTI { color: #808080; font-style: italic; }
+.code .es0 { color: #000099; font-weight: bold; }
+.code .kw1 { color: #b1b100; }
+.code .kw2 { color: #000000; font-weight: bold; }
+.code .kw3 { color: #000066; }
+.code .kw4 { color: #993333; }
+.code .kw5 { color: #0000ff; }
+.code .me0 { color: #006600; }
+.code .nu0 { color: #cc66cc; }
+.code .re0 { color: #0000ff; }
+.code .re1 { color: #0000ff; }
+.code .re2 { color: #0000ff; }
+.code .re4 { color: #009999; }
+.code .sc0 { color: #00bbdd; }
+.code .sc1 { color: #ddbb00; }
+.code .sc2 { color: #009900; }
+.code .st0 { color: #ff0000; }
diff --git a/docs/wiki/wiki-dokuwiki.html b/docs/wiki/wiki-dokuwiki.html
new file mode 100644
index 0000000..aac904c
--- /dev/null
+++ b/docs/wiki/wiki-dokuwiki.html
@@ -0,0 +1,166 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#dokuwiki" class="toc">DokuWiki</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#download" class="toc">Download</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#read_more" class="toc">Read More</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#copyright" class="toc">Copyright</a></span></div></li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="dokuwiki" id="dokuwiki">DokuWiki</a></h1>
+<div class="level1">
+
+<p>
+ <a href="http://wiki.splitbrain.org/wiki%3Adokuwiki"; class="media" title="http://wiki.splitbrain.org/wiki%3Adokuwiki";><img src="media/wiki/dokuwiki-128.png" class="medialeft" alt="" /></a> DokuWiki is a standards compliant, simple to use <a href="http://en.wikipedia.org/wiki/Wiki"; class="interwiki iw_wp" title="http://en.wikipedia.org/wiki/Wiki";>Wiki</a>, mainly aimed at creating documentation of any kind. It is targeted at developer teams, workgroups and small companies. It has a simple but powerful <a href="wiki-syntax.html" class="wikilink1" title="wiki-syntax.html">syntax</a> which makes sure the datafiles remain readable outside the Wiki and eases the creation of structured texts. All data is stored in plain text files – no database is required.
+</p>
+
+<p>
+Read the <a href="http://wiki.splitbrain.org/wiki%3Amanual"; class="interwiki iw_doku" title="http://wiki.splitbrain.org/wiki%3Amanual";>DokuWiki Manual</a> to unleash the full power of DokuWiki.
+</p>
+
+</div>
+<!-- SECTION "DokuWiki" [1-562] -->
+<h2><a name="download" id="download">Download</a></h2>
+<div class="level2">
+
+<p>
+ DokuWiki is available at <a href="http://www.splitbrain.org/go/dokuwiki"; class="urlextern" title="http://www.splitbrain.org/go/dokuwiki"; rel="nofollow">http://www.splitbrain.org/go/dokuwiki</a>
+</p>
+
+</div>
+<!-- SECTION "Download" [563-648] -->
+<h2><a name="read_more" id="read_more">Read More</a></h2>
+<div class="level2">
+
+<p>
+ All documentation and additional information besides the <a href="wiki-syntax.html" class="wikilink1" title="wiki-syntax.html">syntax description</a> is maintained in the DokuWiki at <a href="http://wiki.splitbrain.org/wiki%3Adokuwiki"; class="interwiki iw_doku" title="http://wiki.splitbrain.org/wiki%3Adokuwiki";>wiki.splitbrain.org</a>.
+</p>
+
+<p>
+<strong>About DokuWiki</strong>
+</p>
+<ul>
+<li class="level1"><div class="li"> <a href="http://wiki.splitbrain.org/wiki%3Afeatures"; class="interwiki iw_doku" title="http://wiki.splitbrain.org/wiki%3Afeatures";>A feature list</a> <img src="images/smileys/icon_exclaim.gif" align="middle" alt=":!:" /></div>
+</li>
+<li class="level1"><div class="li"> <a href="http://wiki.splitbrain.org/wiki%3Ausers"; class="interwiki iw_doku" title="http://wiki.splitbrain.org/wiki%3Ausers";>Happy Users</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="http://wiki.splitbrain.org/wiki%3Apress"; class="interwiki iw_doku" title="http://wiki.splitbrain.org/wiki%3Apress";>Who wrote about it</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="http://wiki.splitbrain.org/wiki%3Ablogroll"; class="interwiki iw_doku" title="http://wiki.splitbrain.org/wiki%3Ablogroll";>What Bloggers think</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="http://www.wikimatrix.org/show/DokuWiki"; class="urlextern" title="http://www.wikimatrix.org/show/DokuWiki"; rel="nofollow">Compare it with other wiki software</a></div>
+</li>
+</ul>
+
+<p>
+ <strong>Installing DokuWiki</strong>
+</p>
+<ul>
+<li class="level1"><div class="li"> <a href="http://wiki.splitbrain.org/wiki%3Arequirements"; class="interwiki iw_doku" title="http://wiki.splitbrain.org/wiki%3Arequirements";>System Requirements</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="http://www.splitbrain.org/go/dokuwiki"; class="urlextern" title="http://www.splitbrain.org/go/dokuwiki"; rel="nofollow">Download DokuWiki</a> <img src="images/smileys/icon_exclaim.gif" align="middle" alt=":!:" /></div>
+</li>
+<li class="level1"><div class="li"> <a href="http://wiki.splitbrain.org/wiki%3Achanges"; class="interwiki iw_doku" title="http://wiki.splitbrain.org/wiki%3Achanges";>Change Log</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="http://wiki.splitbrain.org/wiki%3AInstall"; class="interwiki iw_doku" title="http://wiki.splitbrain.org/wiki%3AInstall";>How to install or upgrade</a> <img src="images/smileys/icon_exclaim.gif" align="middle" alt=":!:" /></div>
+</li>
+<li class="level1"><div class="li"> <a href="http://wiki.splitbrain.org/wiki%3Aconfig"; class="interwiki iw_doku" title="http://wiki.splitbrain.org/wiki%3Aconfig";>Configuration</a></div>
+</li>
+</ul>
+
+<p>
+ <strong>Using DokuWiki</strong>
+</p>
+<ul>
+<li class="level1"><div class="li"> <a href="wiki-syntax.html" class="wikilink1" title="wiki-syntax.html">Wiki Syntax</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="http://wiki.splitbrain.org/wiki%3Amanual"; class="interwiki iw_doku" title="http://wiki.splitbrain.org/wiki%3Amanual";>The manual</a> <img src="images/smileys/icon_exclaim.gif" align="middle" alt=":!:" /></div>
+</li>
+<li class="level1"><div class="li"> <a href="http://wiki.splitbrain.org/wiki%3AFAQ"; class="interwiki iw_doku" title="http://wiki.splitbrain.org/wiki%3AFAQ";>Frequently Asked Questions (FAQ)</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="http://wiki.splitbrain.org/wiki%3Aglossary"; class="interwiki iw_doku" title="http://wiki.splitbrain.org/wiki%3Aglossary";>Glossary</a></div>
+</li>
+</ul>
+
+<p>
+ <strong>Customizing DokuWiki</strong>
+</p>
+<ul>
+<li class="level1"><div class="li"> <a href="http://wiki.splitbrain.org/wiki%3Atips"; class="interwiki iw_doku" title="http://wiki.splitbrain.org/wiki%3Atips";>Tips and Tricks</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="http://wiki.splitbrain.org/wiki%3Atpl%3Atemplates"; class="interwiki iw_doku" title="http://wiki.splitbrain.org/wiki%3Atpl%3Atemplates";>How to create and use templates</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="http://wiki.splitbrain.org/wiki%3Aplugins"; class="interwiki iw_doku" title="http://wiki.splitbrain.org/wiki%3Aplugins";>Installing plugins</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="http://wiki.splitbrain.org/wiki%3Adevelopment"; class="interwiki iw_doku" title="http://wiki.splitbrain.org/wiki%3Adevelopment";>Development Resources</a></div>
+</li>
+</ul>
+
+<p>
+ <strong>DokuWiki Feedback</strong>
+</p>
+<ul>
+<li class="level1"><div class="li"> <a href="http://wiki.splitbrain.org/wiki%3Amailinglist"; class="interwiki iw_doku" title="http://wiki.splitbrain.org/wiki%3Amailinglist";>Join the mailing list</a> <img src="images/smileys/icon_exclaim.gif" align="middle" alt=":!:" /></div>
+</li>
+<li class="level1"><div class="li"> <a href="http://bugs.splitbrain.org/index.php?project=1"; class="urlextern" title="http://bugs.splitbrain.org/index.php?project=1"; rel="nofollow">Submit bugs and feature wishes</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="http://wiki.splitbrain.org/wiki%3Adiscussion%3Adiscussion"; class="interwiki iw_doku" title="http://wiki.splitbrain.org/wiki%3Adiscussion%3Adiscussion";>The discussion pages</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="http://www.wikimatrix.org/forum/viewforum.php?id=10"; class="urlextern" title="http://www.wikimatrix.org/forum/viewforum.php?id=10"; rel="nofollow">Share your experiences in the WikiMatrix forum</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="http://wiki.splitbrain.org/wiki%3Athanks"; class="interwiki iw_doku" title="http://wiki.splitbrain.org/wiki%3Athanks";>Some humble thanks</a></div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Read More" [649-2179] -->
+<h2><a name="copyright" id="copyright">Copyright</a></h2>
+<div class="level2">
+
+<p>
+ 2004-2006 © Andreas Gohr <a href="mailto:andi@splitbrain.org"; class="mail JSnocheck" title="andi@splitbrain.org">andi@splitbrain.org</a>
+</p>
+
+<p>
+The DokuWiki engine is licensed under <a href="http://www.gnu.org/licenses/gpl.html"; class="urlextern" title="http://www.gnu.org/licenses/gpl.html"; rel="nofollow">GNU General Public License</a> Version 2. If you use DokuWiki in your company, consider donating a few bucks to me via <a href="https://www.paypal.com/xclick/business=andi%40splitbrain.org&item_name=DokuWiki+Donation&no_shipping=1&no_note=1&tax=0&currency_code=EUR&lc=US"; class="urlextern" title="https://www.paypal.com/xclick/business=andi%40splitbrain.org&item_name=DokuWiki+Donation&no_shipping=1&no_note=1&tax=0&currency_code=EUR&lc=US"; rel="nofollow">PayPal</a> <img src="images/smileys/icon_wink.gif" align="middle" alt=";-)" />.
+</p>
+
+<p>
+The content published in the DokuWiki at <a href="http://www.splitbrain.org/dokuwiki/"; class="urlextern" title="http://www.splitbrain.org/dokuwiki/"; rel="nofollow">http://www.splitbrain.org/dokuwiki/</a> is licensed under the <a href="http://creativecommons.org/licenses/by-nc-sa/2.0/"; class="urlextern" title="http://creativecommons.org/licenses/by-nc-sa/2.0/"; rel="nofollow">Creative Commons Attribution-NonCommercial-ShareAlike License</a> Version 2.0.
+</p>
+
+<p>
+An exception is made for the content which distributed in the download tarball <a href="#fn__1" name="fnt__1" id="fnt__1" class="fn_top">1)</a> which is, for compatibility reasons, licensed under the GNU General Public License Version 2 as well.
+</p>
+
+<p>
+Not sure what this means? See the <a href="http://wiki.splitbrain.org/wiki%3Afaq%23licenses_explained"; class="interwiki iw_doku" title="http://wiki.splitbrain.org/wiki%3Afaq%23licenses_explained";>FAQ on the Licenses</a>.
+</p>
+
+</div>
+<!-- SECTION "Copyright" [2180-] --><div class="footnotes">
+<div class="fn"><a href="#fnt__1" id="fn__1" name="fn__1" class="fn_bot">1)</a>
+files inside the <code>data</code> directory – eg: <code>dokuwiki.txt</code>, <code>syntax.txt</code>, <code>dokuwiki-128.png</code></div>
+</div>
+</body>
+</html>
diff --git a/docs/wiki/wiki-syntax.html b/docs/wiki/wiki-syntax.html
new file mode 100644
index 0000000..17b47f2
--- /dev/null
+++ b/docs/wiki/wiki-syntax.html
@@ -0,0 +1,666 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<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="#formatting_syntax" class="toc">Formatting Syntax</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#basic_text_formatting" class="toc">Basic text formatting</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#links" class="toc">Links</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#external" class="toc">External</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#internal" class="toc">Internal</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#interwiki" class="toc">Interwiki</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#windows_shares" class="toc">Windows Shares</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#image_links" class="toc">Image Links</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#footnotes" class="toc">Footnotes</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#sectioning" class="toc">Sectioning</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#headline_level_3" class="toc">Headline Level 3</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#images_and_other_files" class="toc">Images and other files</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#lists" class="toc">Lists</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#smileys" class="toc">Smileys</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#typography" class="toc">Typography</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#quoting" class="toc">Quoting</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#tables" class="toc">Tables</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#nonparsed_blocks" class="toc">Nonparsed Blocks</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#syntax_highlighting" class="toc">Syntax Highlighting</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#embedding_html_and_php" class="toc">Embedding HTML and PHP</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#syntax_plugins" class="toc">Syntax Plugins</a></span></div></li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="formatting_syntax" id="formatting_syntax">Formatting Syntax</a></h1>
+<div class="level1">
+
+<p>
+ <a href="wiki-dokuwiki.html" class="wikilink1" title="wiki-dokuwiki.html">DokuWiki</a> supports some simple markup language, which tries to make the datafiles to be as readable as possible. This page contains all possible syntax you may use when editing the pages. Simply have a look at the source of this page by pressing the <em>Edit this page</em> button at the top or bottom of the page. If you want to try something, just use the <a href="playground-playground.html" class="wikilink1" title="playground-playground.html">playground</a> page. The simpler markup is easily accessible via <a href="http://wiki.splitbrain.org/wiki%3Aquickbuttons"; class="interwiki iw_doku" title="http://wiki.splitbrain.org/wiki%3Aquickbuttons";>quickbuttons</a>, too.
+</p>
+
+</div>
+<!-- SECTION "Formatting Syntax" [1-528] -->
+<h2><a name="basic_text_formatting" id="basic_text_formatting">Basic text formatting</a></h2>
+<div class="level2">
+
+<p>
+ DokuWiki supports <strong>bold</strong>, <em>italic</em>, <em class="u">underlined</em> and <code>monospaced</code> texts. Of course you can <strong><em class="u"><em><code>combine</code></em></em></strong> all these.
+</p>
+<pre class="code">DokuWiki supports **bold**, //italic//, __underlined__ and ''monospaced'' texts.
+Of course you can **__//''combine''//__** all these.</pre>
+
+<p>
+ You can use <sub>subscript</sub> and <sup>superscript</sup>, too.
+</p>
+<pre class="code">You can use <sub>subscript</sub> and <sup>superscript</sup>, too.</pre>
+
+<p>
+ You can mark something as <del>deleted</del> as well.
+</p>
+<pre class="code">You can mark something as <del>deleted</del> as well.</pre>
+
+<p>
+ <strong>Paragraphs</strong> are created from blank lines. If you want to <strong>force a newline</strong> without a paragraph, you can use two backslashes followed by a whitespace or the end of line.
+</p>
+
+<p>
+This is some text with some linebreaks<br/>
+ Note that the two backslashes are only recognized at the end of a line<br/>
+ or followed by<br/>
+ a whitespace \\this happens without it.
+</p>
+<pre class="code">This is some text with some linebreaks\\ Note that the
+two backslashes are only recognized at the end of a line\\
+or followed by\\ a whitespace \\this happens without it.</pre>
+
+<p>
+ You should use forced newlines only if really needed.
+</p>
+
+</div>
+<!-- SECTION "Basic text formatting" [529-1665] -->
+<h2><a name="links" id="links">Links</a></h2>
+<div class="level2">
+
+<p>
+ DokuWiki supports multiple ways of creating links.
+</p>
+
+</div>
+<!-- SECTION "Links" [1666-1736] -->
+<h3><a name="external" id="external">External</a></h3>
+<div class="level3">
+
+<p>
+ External links are recognized automagically: <a href="http://www.google.com"; class="urlextern" title="http://www.google.com"; rel="nofollow">http://www.google.com</a> or simply <a href="http://www.google.com"; class="urlextern" title="http://www.google.com"; rel="nofollow">www.google.com</a> - You can set Linknames, too: <a href="http://www.google.com"; class="urlextern" title="http://www.google.com"; rel="nofollow">This Link points to google</a>. Email addresses like this one: <a href="mailto:andi@splitbrain.org"; class="mail JSnocheck" title="andi@splitbrain.org">andi@splitbrain.org</a> are recognized, too.
+</p>
+<pre class="code">DokuWiki supports multiple ways of creating links. External links are recognized
+automagically: http://www.google.com or simply www.google.com - You can set
+Linknames, too: [[http://www.google.com|This Link points to google]]. Email
+addresses like this one: <andi@xxxxxxxxxxxxxx> are recognized, too.</pre>
+
+</div>
+<!-- SECTION "External" [1737-2317] -->
+<h3><a name="internal" id="internal">Internal</a></h3>
+<div class="level3">
+
+<p>
+ Internal links are created by using square brackets. You can either just give a <a href="http://wiki.splitbrain.org/wiki%3Apagename"; class="interwiki iw_doku" title="http://wiki.splitbrain.org/wiki%3Apagename";>wiki:pagename</a> or use an additional <a href="http://wiki.splitbrain.org/wiki%3Apagename"; class="interwiki iw_doku" title="http://wiki.splitbrain.org/wiki%3Apagename";>Title Text</a>. Wiki pagenames are converted to lowercase automatically, special characters are not allowed.
+</p>
+<pre class="code">Internal links are created by using square brackets. You can either just give
+a [[pagename]] or use an additional [[pagename|Title Text]]. Wiki pagenames
+are converted to lowercase automatically, special chars are not allowed.</pre>
+
+<p>
+ You can use <a href="wiki-namespaces.html" class="wikilink2" title="wiki-namespaces.html">namespaces</a> by using a colon in the pagename.
+</p>
+<pre class="code">You can use [[wiki:namespaces]] by using a colon in the pagename.</pre>
+
+<p>
+ For details about namespaces see <a href="http://wiki.splitbrain.org/wiki%3Anamespaces"; class="interwiki iw_doku" title="http://wiki.splitbrain.org/wiki%3Anamespaces";>wiki:namespaces</a>.
+</p>
+
+<p>
+Linking to a specific section is possible, too. Just add the sectionname behind a hash character as known from <acronym title="HyperText Markup Language">HTML</acronym>. This links to <a href="wiki-syntax.html#internal" class="wikilink1" title="wiki-syntax.html">this Section</a>.
+</p>
+<pre class="code">This links to [[syntax#internal|this Section]].</pre>
+
+<p>
+ Notes:
+</p>
+<ul>
+<li class="level1"><div class="li"> Links to <a href="wiki-syntax.html" class="wikilink1" title="wiki-syntax.html">existing pages</a> are shown in a different style from <a href="wiki-nonexisting.html" class="wikilink2" title="wiki-nonexisting.html">nonexisting</a> ones.</div>
+</li>
+<li class="level1"><div class="li"> DokuWiki does not use <a href="http://en.wikipedia.org/wiki/CamelCase"; class="interwiki iw_wp" title="http://en.wikipedia.org/wiki/CamelCase";>CamelCase</a> to automatically create links by default, but this behaviour can be enabled in the <a href="http://wiki.splitbrain.org/config"; class="interwiki iw_doku" title="http://wiki.splitbrain.org/config";>config</a> file. Hint: If DokuWiki is a link, then itâ??s enabled.</div>
+</li>
+<li class="level1"><div class="li"> When a sectionâ??s heading is changed, its bookmark changes, too. So donâ??t rely on section linking too much.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Internal" [2318-3661] -->
+<h3><a name="interwiki" id="interwiki">Interwiki</a></h3>
+<div class="level3">
+
+<p>
+ DokuWiki supports <a href="http://wiki.splitbrain.org/wiki%3Ainterwiki"; class="interwiki iw_doku" title="http://wiki.splitbrain.org/wiki%3Ainterwiki";>Interwiki</a> links. These are quick links to other Wikis. For example this is a link to Wikipediaâ??s page about Wikis: <a href="http://en.wikipedia.org/wiki/Wiki"; class="interwiki iw_wp" title="http://en.wikipedia.org/wiki/Wiki";>Wiki</a>.
+</p>
+<pre class="code">DokuWiki supports [[doku>wiki:interwiki|Interwiki]] links. These are quick links to other Wikis.
+For example this is a link to Wikipedia's page about Wikis: [[wp>Wiki]].</pre>
+
+</div>
+<!-- SECTION "Interwiki" [3662-4028] -->
+<h3><a name="windows_shares" id="windows_shares">Windows Shares</a></h3>
+<div class="level3">
+
+<p>
+ Windows shares like <a href="file://///server/share" class="windows" title="\\server\share" onclick="if(document.all == null){alert('Linking to Windows shares only works in Microsoft Internet Explorer.\nYou still can copy and paste the link.');}" onkeypress="if(document.all == null){alert('Linking to Windows shares only works in Microsoft Internet Explorer.\nYou still can copy and paste the link.');}">this</a> are recognized, too. Please note that these only make sense in a homogenous user group like a corporate <a href="http://en.wikipedia.org/wiki/Intranet"; class="interwiki iw_wp" title="http://en.wikipedia.org/wiki/Intranet";>Intranet</a>.
+</p>
+<pre class="code">Windows Shares like [[\\server\share|this]] are recognized, too.</pre>
+
+<p>
+ Notes:
+</p>
+<ul>
+<li class="level1"><div class="li"> For security reasons direct browsing of windows shares only works in Microsoft Internet Explorer per default (and only in the â??local zoneâ??).</div>
+</li>
+<li class="level1"><div class="li"> For Mozilla and Firefox it can be enabled through the config option <a href="http://www.mozilla.org/quality/networking/docs/netprefs.html#file"; class="urlextern" title="http://www.mozilla.org/quality/networking/docs/netprefs.html#file"; rel="nofollow">security.checkloaduri</a> but this is not recommended</div>
+</li>
+<li class="level1"><div class="li"> See <a href="http://www.google.com/search?q=151&btnI=lucky"; class="interwiki iw_go" title="http://www.google.com/search?q=151&btnI=lucky";>151</a> for more info</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Windows Shares" [4029-4668] -->
+<h3><a name="image_links" id="image_links">Image Links</a></h3>
+<div class="level3">
+
+<p>
+ You can also use an image to link to another internal or external page by combining the syntax for links and <a href="#images_and_other_files" title=":wiki:syntax.txt ↵" class="wikilink1">images</a> (see below) like this:
+</p>
+<pre class="code">[[http://www.php.net|{{wiki:dokuwiki-128.png}}]]</pre>
+
+<p>
+ <a href="http://www.php.net"; class="media" title="http://www.php.net"; rel="nofollow"><img src="media/wiki/dokuwiki-128.png" class="media" alt="" /></a>
+</p>
+
+<p>
+Please note: The image formatting is the only formatting syntax accepted in link names.
+</p>
+
+<p>
+The whole <a href="#images_and_other_files" title=":wiki:syntax.txt ↵" class="wikilink1">image</a> and <a href="#links" title=":wiki:syntax.txt ↵" class="wikilink1">link</a> syntax is supported (including image resizing, internal and external images and URLs and interwiki links).
+</p>
+
+</div>
+<!-- SECTION "Image Links" [4669-5222] -->
+<h2><a name="footnotes" id="footnotes">Footnotes</a></h2>
+<div class="level2">
+
+<p>
+ You can add footnotes <a href="#fn__1" name="fnt__1" id="fnt__1" class="fn_top">1)</a> by using double parentheses.
+</p>
+<pre class="code">You can add footnotes ((This is a footnote)) by using double parentheses.</pre>
+
+</div>
+<!-- SECTION "Footnotes" [5223-5397] -->
+<h2><a name="sectioning" id="sectioning">Sectioning</a></h2>
+<div class="level2">
+
+<p>
+ You can use up to five different levels of headlines to structure your content. If you have more than three headlines, a table of contents is generated automatically – this can be disabled by including the string <code>~~NOTOC~~</code> in the document.
+</p>
+
+</div>
+<!-- SECTION "Sectioning" [5398-5684] -->
+<h3><a name="headline_level_3" id="headline_level_3">Headline Level 3</a></h3>
+<div class="level3">
+
+</div>
+
+<h4><a name="headline_level_4" id="headline_level_4">Headline Level 4</a></h4>
+<div class="level4">
+
+</div>
+
+<h5><a name="headline_level_5" id="headline_level_5">Headline Level 5</a></h5>
+<div class="level5">
+<pre class="code">==== Headline Level 3 ====
+=== Headline Level 4 ===
+== Headline Level 5 ==</pre>
+
+<p>
+ By using four or more dashes, you can make a horizontal line:
+</p>
+<hr />
+
+</div>
+<!-- SECTION "Headline Level 3" [5685-5911] -->
+<h2><a name="images_and_other_files" id="images_and_other_files">Images and other files</a></h2>
+<div class="level2">
+
+<p>
+ You can include external and internal <a href="http://wiki.splitbrain.org/images"; class="interwiki iw_doku" title="http://wiki.splitbrain.org/images";>images</a> with curly brackets. Optionally you can specify the size of them.
+</p>
+
+<p>
+Real size: <a href="media/wiki/dokuwiki-128.png" class="media" target="_blank" title="wiki:dokuwiki-128.png"><img src="media/wiki/dokuwiki-128.png" class="media" alt="" /></a>
+</p>
+
+<p>
+Resize to given width: <a href="media/wiki/dokuwiki-128.png" class="media" target="_blank" title="wiki:dokuwiki-128.png"><img src="media/wiki/dokuwiki-128.png" class="media" alt="" width="50" /></a>
+</p>
+
+<p>
+Resize to given width and height: <a href="media/wiki/dokuwiki-128.png" class="media" target="_blank" title="wiki:dokuwiki-128.png"><img src="media/wiki/dokuwiki-128.png" class="media" alt="" width="200" height="50" /></a>
+</p>
+
+<p>
+Resized external image: <a href="./lib/exe/fetch.php?cache=cache&media=http%3A%2F%2Fde3.php.net%2Fimages%2Fphp.gif" class="media" title="http://de3.php.net/images/php.gif";><img src="media/http///de3.php.net/images/php.gif" class="media" alt="" width="200" height="50" /></a>
+</p>
+<pre class="code">Real size: {{wiki:dokuwiki-128.png}}
+Resize to given width: {{wiki:dokuwiki-128.png?50}}
+Resize to given width and height: {{wiki:dokuwiki-128.png?200x50}}
+Resized external image: {{http://de3.php.net/images/php.gif?200x50}}</pre>
+
+<p>
+By using left or right whitespaces you can choose the alignment
+</p>
+
+<p>
+<a href="media/wiki/dokuwiki-128.png" class="media" target="_blank" title="wiki:dokuwiki-128.png"><img src="media/wiki/dokuwiki-128.png" class="mediaright" alt="" /></a>
+</p>
+
+<p>
+<a href="media/wiki/dokuwiki-128.png" class="media" target="_blank" title="wiki:dokuwiki-128.png"><img src="media/wiki/dokuwiki-128.png" class="medialeft" alt="" /></a>
+</p>
+
+<p>
+<a href="media/wiki/dokuwiki-128.png" class="media" target="_blank" title="wiki:dokuwiki-128.png"><img src="media/wiki/dokuwiki-128.png" class="mediacenter" alt="" /></a>
+</p>
+<pre class="code">{{ wiki:dokuwiki-128.png}}
+{{wiki:dokuwiki-128.png }}
+{{ wiki:dokuwiki-128.png }}</pre>
+
+<p>
+ Of course, you can add a title (displayed as a tooltip by most browsers), too.
+</p>
+
+<p>
+<a href="media/wiki/dokuwiki-128.png" class="media" target="_blank" title="wiki:dokuwiki-128.png"><img src="media/wiki/dokuwiki-128.png" class="mediacenter" title="This is the caption" alt="This is the caption" /></a>
+</p>
+<pre class="code">{{ wiki:dokuwiki-128.png |This is the caption}}</pre>
+
+<p>
+ If you specify a filename (external or internal) that is not an image (<code>gif,jpeg,png</code>), then it will be displayed as a link instead.
+</p>
+
+<p>
+For linking an image to another page see <a href="wiki-image_links.html" class="wikilink2" title="wiki-image_links.html">Image Links</a> above.
+</p>
+
+</div>
+<!-- SECTION "Images and other files" [5912-7240] -->
+<h2><a name="lists" id="lists">Lists</a></h2>
+<div class="level2">
+
+<p>
+ Dokuwiki supports ordered and unordered lists. To create a list item, indent your text by two spaces and use a <code>*</code> for unordered lists or a <code>-</code> for ordered ones.
+</p>
+<ul>
+<li class="level1"><div class="li"> This is a list</div>
+</li>
+<li class="level1"><div class="li"> The second item</div>
+<ul>
+<li class="level2"><div class="li"> You may have different levels</div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> Another item</div>
+</li>
+</ul>
+<ol>
+<li class="level1"><div class="li"> The same list but ordered</div>
+</li>
+<li class="level1"><div class="li"> Another item</div>
+<ol>
+<li class="level2"><div class="li"> Just use indention for deeper levels</div>
+</li>
+</ol>
+</li>
+<li class="level1"><div class="li"> Thatâ??s it</div>
+</li>
+</ol>
+<pre class="code">
+ * This is a list
+ * The second item
+ * You may have different levels
+ * Another item
+
+ - The same list but ordered
+ - Another item
+ - Just use indention for deeper levels
+ - That's it
+</pre>
+
+</div>
+<!-- SECTION "Lists" [7241-7837] -->
+<h2><a name="smileys" id="smileys">Smileys</a></h2>
+<div class="level2">
+
+<p>
+ DokuWiki converts commonly used <a href="http://en.wikipedia.org/wiki/emoticon"; class="interwiki iw_wp" title="http://en.wikipedia.org/wiki/emoticon";>emoticon</a>s to their graphical equivalents. More smileys can be placed in the <code>smiley</code> directory and configured in the <code>conf/smileys.conf</code> file. Here is an overview of Smileys included in DokuWiki.
+</p>
+<ul>
+<li class="level1"><div class="li"> <img src="images/smileys/icon_cool.gif" align="middle" alt="8-)" /> 8-) </div>
+</li>
+<li class="level1"><div class="li"> <img src="images/smileys/icon_eek.gif" align="middle" alt="8-O" /> 8-O </div>
+</li>
+<li class="level1"><div class="li"> <img src="images/smileys/icon_sad.gif" align="middle" alt=":-(" /> :-( </div>
+</li>
+<li class="level1"><div class="li"> <img src="images/smileys/icon_smile.gif" align="middle" alt=":-)" /> :-) </div>
+</li>
+<li class="level1"><div class="li"> <img src="images/smileys/icon_smile2.gif" align="middle" alt="=)" /> =) </div>
+</li>
+<li class="level1"><div class="li"> <img src="images/smileys/icon_doubt.gif" align="middle" alt=":-/" /> :-/ </div>
+</li>
+<li class="level1"><div class="li"> <img src="images/smileys/icon_doubt2.gif" align="middle" alt=":-\" /> :-\ </div>
+</li>
+<li class="level1"><div class="li"> <img src="images/smileys/icon_confused.gif" align="middle" alt=":-?" /> :-? </div>
+</li>
+<li class="level1"><div class="li"> <img src="images/smileys/icon_biggrin.gif" align="middle" alt=":-D" /> :-D </div>
+</li>
+<li class="level1"><div class="li"> <img src="images/smileys/icon_razz.gif" align="middle" alt=":-P" /> :-P </div>
+</li>
+<li class="level1"><div class="li"> <img src="images/smileys/icon_surprised.gif" align="middle" alt=":-O" /> :-O </div>
+</li>
+<li class="level1"><div class="li"> <img src="images/smileys/icon_silenced.gif" align="middle" alt=":-X" /> :-X </div>
+</li>
+<li class="level1"><div class="li"> <img src="images/smileys/icon_neutral.gif" align="middle" alt=":-|" /> :-| </div>
+</li>
+<li class="level1"><div class="li"> <img src="images/smileys/icon_wink.gif" align="middle" alt=";-)" /> ;-) </div>
+</li>
+<li class="level1"><div class="li"> <img src="images/smileys/icon_fun.gif" align="middle" alt="^_^" /> ^_^ </div>
+</li>
+<li class="level1"><div class="li"> <img src="images/smileys/icon_question.gif" align="middle" alt=":?:" /> :?: </div>
+</li>
+<li class="level1"><div class="li"> <img src="images/smileys/icon_exclaim.gif" align="middle" alt=":!:" /> :!: </div>
+</li>
+<li class="level1"><div class="li"> <img src="images/smileys/icon_lol.gif" align="middle" alt="LOL" /> LOL </div>
+</li>
+<li class="level1"><div class="li"> <img src="images/smileys/fixme.gif" align="middle" alt="FIXME" /> FIXME </div>
+</li>
+<li class="level1"><div class="li"> <img src="images/smileys/delete.gif" align="middle" alt="DELETEME" /> DELETEME </div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Smileys" [7838-8510] -->
+<h2><a name="typography" id="typography">Typography</a></h2>
+<div class="level2">
+
+<p>
+ <a href="wiki-dokuwiki.html" class="wikilink1" title="wiki-dokuwiki.html">DokuWiki</a> can convert simple text characters to their typographically correct entities. Here is an example of recognized characters.
+</p>
+
+<p>
+→ ← ↔ ⇒ ⇐ ⇔ » « – — 640×480 © ™ ® â??He thought â??Itâ??s a manâ??s worldâ??…â??
+</p>
+<pre class="code">
+-> <- <-> => <= <=> >> << -- --- 640x480 (c) (tm) (r)
+"He thought 'It's a man's world'..."
+</pre>
+
+<p>
+Please note: These conversions can be turned off through a <a href="http://wiki.splitbrain.org/wiki%3Aconfig%23typography"; class="interwiki iw_doku" title="http://wiki.splitbrain.org/wiki%3Aconfig%23typography";>config option</a> and a <a href="http://wiki.splitbrain.org/wiki%3Aentities"; class="interwiki iw_doku" title="http://wiki.splitbrain.org/wiki%3Aentities";>pattern file</a>.
+</p>
+
+</div>
+<!-- SECTION "Typography" [8511-9019] -->
+<h2><a name="quoting" id="quoting">Quoting</a></h2>
+<div class="level2">
+
+<p>
+ Some times you want to mark some text to show itâ??s a reply or comment. You can use the following syntax:
+</p>
+<pre class="code">I think we should do it
+
+> No we shouldn't
+
+>> Well, I say we should
+
+> Really?
+
+>> Yes!
+
+>>> Then lets do it!</pre>
+
+<p>
+ I think we should do it
+</p>
+<blockquote><div class="no">
+ No we shouldnâ??t</div></blockquote>
+<blockquote><div class="no">
+<blockquote><div class="no">
+ Well, I say we should</div></blockquote>
+</div></blockquote>
+<blockquote><div class="no">
+ Really?</div></blockquote>
+<blockquote><div class="no">
+<blockquote><div class="no">
+ Yes!</div></blockquote>
+</div></blockquote>
+<blockquote><div class="no">
+<blockquote><div class="no">
+<blockquote><div class="no">
+ Then lets do it!</div></blockquote>
+</div></blockquote>
+</div></blockquote>
+
+</div>
+<!-- SECTION "Quoting" [9020-9392] -->
+<h2><a name="tables" id="tables">Tables</a></h2>
+<div class="level2">
+
+<p>
+ DokuWiki supports a simple syntax to create tables.
+</p>
+<table class="inline">
+ <tr>
+ <th class="leftalign"> Heading 1 </th><th class="leftalign"> Heading 2 </th><th class="leftalign"> Heading 3 </th>
+ </tr>
+ <tr>
+ <td class="leftalign"> Row 1 Col 1 </td><td class="leftalign"> Row 1 Col 2 </td><td class="leftalign"> Row 1 Col 3 </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> Row 2 Col 1 </td><td colspan="2"> some colspan (note the double pipe) </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> Row 3 Col 1 </td><td class="leftalign"> Row 2 Col 2 </td><td class="leftalign"> Row 2 Col 3 </td>
+ </tr>
+</table>
+
+<p>
+ Table rows have to start and end with a <code>|</code> for normal rows or a <code>^</code> for headers.
+</p>
+<pre class="code">^ Heading 1 ^ Heading 2 ^ Heading 3 ^
+| Row 1 Col 1 | Row 1 Col 2 | Row 1 Col 3 |
+| Row 2 Col 1 | some colspan (note the double pipe) ||
+| Row 3 Col 1 | Row 2 Col 2 | Row 2 Col 3 |</pre>
+
+<p>
+ To connect cells horizontally, just make the next cell completely empty as shown above. Be sure to have always the same amount of cell separators!
+</p>
+
+<p>
+Vertical tableheaders are possible, too.
+</p>
+<table class="inline">
+ <tr>
+ <td class="rightalign"> </td><th class="leftalign"> Heading 1 </th><th class="leftalign"> Heading 2 </th>
+ </tr>
+ <tr>
+ <th class="leftalign"> Heading 3 </th><td class="leftalign"> Row 1 Col 2 </td><td class="leftalign"> Row 1 Col 3 </td>
+ </tr>
+ <tr>
+ <th class="leftalign"> Heading 4 </th><td> no colspan this time </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <th class="leftalign"> Heading 5 </th><td class="leftalign"> Row 2 Col 2 </td><td class="leftalign"> Row 2 Col 3 </td>
+ </tr>
+</table>
+
+<p>
+ As you can see, itâ??s the cell separator before a cell which decides about the formatting:
+</p>
+<pre class="code">| ^ Heading 1 ^ Heading 2 ^
+^ Heading 3 | Row 1 Col 2 | Row 1 Col 3 |
+^ Heading 4 | no colspan this time | |
+^ Heading 5 | Row 2 Col 2 | Row 2 Col 3 |</pre>
+
+<p>
+ Note: Vertical spans (rowspan) are not possible.
+</p>
+
+<p>
+You can align the table contents, too. Just add at least two whitespaces at the opposite end of your text: Add two spaces on the left to align right, two spaces on the right to align left and two spaces at least at both ends for centered text.
+</p>
+<table class="inline">
+ <tr>
+ <th class="centeralign" colspan="3"> Table with alignment </th>
+ </tr>
+ <tr>
+ <td class="rightalign"> right</td><td class="centeralign"> center </td><td class="leftalign">left </td>
+ </tr>
+ <tr>
+ <td class="leftalign">left </td><td class="rightalign"> right</td><td class="centeralign"> center </td>
+ </tr>
+ <tr>
+ <td> xxxxxxxxxxxx </td><td> xxxxxxxxxxxx </td><td> xxxxxxxxxxxx </td>
+ </tr>
+</table>
+
+<p>
+ This is how it looks in the source:
+</p>
+<pre class="code">^ Table with alignment ^^^
+| right| center |left |
+|left | right| center |
+| xxxxxxxxxxxx | xxxxxxxxxxxx | xxxxxxxxxxxx |</pre>
+
+</div>
+<!-- SECTION "Tables" [9393-11524] -->
+<h2><a name="nonparsed_blocks" id="nonparsed_blocks">Nonparsed Blocks</a></h2>
+<div class="level2">
+
+<p>
+ You can include non parsed blocks into your documents by either indenting them by at least two spaces (like used for the previous examples) or by using the tags <code>code</code> or <code>file</code>.
+</p>
+<pre class="code">
+This is preformatted code all spaces are preserved: like <-this
+</pre>
+<pre class="file">
+This is pretty much the same, but you could use it to show that you quoted a file.
+</pre>
+
+<p>
+To let the parser ignore an area completely (ie. do no formatting on it), enclose the area either with <code>nowiki</code> tags or even simpler, with double percent signs <code>%%</code>.
+</p>
+
+<p>
+
+This is some text which contains addresses like this: http://www.splitbrain.org and **formatting**, but nothing is done with it.
+
+</p>
+
+<p>
+See the source of this page to see how to use these blocks.
+</p>
+
+</div>
+<!-- SECTION "Nonparsed Blocks" [11525-12330] -->
+<h2><a name="syntax_highlighting" id="syntax_highlighting">Syntax Highlighting</a></h2>
+<div class="level2">
+
+<p>
+ <a href="wiki-dokuwiki.html" class="wikilink1" title="wiki-dokuwiki.html">DokuWiki</a> can highlight sourcecode, which makes it easier to read. It uses the <a href="http://qbnz.com/highlighter/"; class="urlextern" title="http://qbnz.com/highlighter/"; rel="nofollow">GeSHi</a> Generic Syntax Highlighter – so any language supported by GeSHi is supported. The syntax is the same like in the code block in the previous section, but this time the name of the used language is inserted inside the tag. Eg. <code><code java></code>.
+</p>
+<pre class="code java"><span class="coMULTI">/**
+ * The HelloWorldApp class implements an application that
+ * simply displays "Hello World!" to the standard output.
+ */</span>
+<span class="kw2">class</span> HelloWorldApp <span class="br0">{</span>
+ <span class="kw2">public</span> <span class="kw2">static</span> <span class="kw4">void</span> main<span class="br0">(</span><a href="http://www.google.com/search?hl=en&q=allinurl%3AString+java.sun.com&bntI=I%27m%20Feeling%20Lucky";><span class="kw3">String</span></a><span class="br0">[</span><span class="br0">]</span> args<span class="br0">)</span> <span class="br0">{</span>
+ <a href="http://www.google.com/search?hl=en&q=allinurl%3ASystem+java.sun.com&bntI=I%27m%20Feeling%20Lucky";><span class="kw3">System</span></a>.<span class="me1">out</span>.<span class="me1">println</span><span class="br0">(</span><span class="st0">"Hello World!"</span><span class="br0">)</span>; <span class="co1">//Display the string.</span>
+ <span class="br0">}</span>
+<span class="br0">}</span></pre>
+<p>
+The following language strings are currently recognized: <em>actionscript, actionscript-french, ada, apache, applescript, asm, asp, autoit, bash, blitzbasic, caddcl, cadlisp, c, c_mac, cfm, cpp, csharp, css, delphi, diff, d, div, dos, eiffel, freebasic, gml, html4strict, ini, inno, java, java5, javascript, lisp, lua, matlab, mpasm, mysql, nsis, objc, ocaml, ocaml-brief, oobas, oracle8, pascal, perl, php-brief, php, python, qbasic, scheme, sdlbasic, smarty, sql, tsql, robots, ruby, vb, vbnet, vhdl, visualfoxpro, xml</em>
+</p>
+
+</div>
+<!-- SECTION "Syntax Highlighting" [12331-13554] -->
+<h2><a name="embedding_html_and_php" id="embedding_html_and_php">Embedding HTML and PHP</a></h2>
+<div class="level2">
+
+<p>
+ You can embed raw <acronym title="HyperText Markup Language">HTML</acronym> or <acronym title="Hypertext Preprocessor">PHP</acronym> code into your documents by using the <code>html</code> or <code>php</code> tags like this:
+</p>
+<pre class="code">
+<html>
+This is some <font color="red" size="+1">HTML</font>
+</html>
+</pre>
+<pre class="file">
+This is some <font color="red" size="+1">HTML</font>
+</pre>
+<pre class="code">
+<php>
+echo 'A logo generated by PHP:';
+echo '<img src="' . $_SERVER['PHP_SELF'] . '?=' . php_logo_guid() . '" alt="PHP Logo !" />';
+</php>
+</pre>
+<pre class="file">
+echo 'A logo generated by PHP:';
+echo '<img src="' . $_SERVER['PHP_SELF'] . '?=' . php_logo_guid() . '" alt="PHP Logo !" />';
+</pre>
+
+<p>
+<strong>Please Note</strong>: <acronym title="HyperText Markup Language">HTML</acronym> and <acronym title="Hypertext Preprocessor">PHP</acronym> embedding is disabled by default in the configuration. If disabled, the code is displayed instead of executed.
+</p>
+
+</div>
+<!-- SECTION "Embedding HTML and PHP" [13555-14284] -->
+<h2><a name="syntax_plugins" id="syntax_plugins">Syntax Plugins</a></h2>
+<div class="level2">
+
+<p>
+ DokuWikiâ??s syntax can be extended by <a href="http://wiki.splitbrain.org/wiki%3Aplugins"; class="interwiki iw_doku" title="http://wiki.splitbrain.org/wiki%3Aplugins";>Plugins</a>. How the installed plugins are used is described on their appropriate description pages. The following syntax plugins are available in this particular DokuWiki installation:
+</p>
+<ul><li><div class="li"><a href="http://wiki.splitbrain.org/plugin:info"; class="urlextern" title="http://wiki.splitbrain.org/plugin:info"; rel="nofollow">Info Plugin</a> <em>2006-12-09</em> by <a href="mailto:andi@splitbrain.org"; class="mail JSnocheck" title="andi@splitbrain.org">Andreas Gohr</a><br />Displays information about various DokuWiki internals</div></li><li><div class="li"><a href="http://wiki.splitbrain.org/plugin:definitions"; class="urlextern" title="http://wiki.splitbrain.org/plugin:definitions"; rel="nofollow">Definition list plugin</a> <em>2005-09-17</em> by <a href="mailto:chris@jalakai.co.uk"; class="mail JSnocheck" title="chris@jalakai.co.uk">Christopher Smith</a><br />Add HTML style definition list ; term : definition</div></li><li><div class="li"><a href="http://wiki.splitbrain.org/plugin:hilited"; class="urlextern" title="http://wiki.splitbrain.org/plugin:hilited"; rel="nofollow">Hilited Plugin</a> <em>2005-06-27</em> by <a href="mailto:esther@kaffeehaus.ch"; class="mail JSnocheck" title="esther@kaffeehaus.ch">Esther Brunner</a><br />Enables highlighted text</div></li><li><div class="li"><a href="http://wiki.splitbrain.org/plugin:note"; class="urlextern" title="http://wiki.splitbrain.org/plugin:note"; rel="nofollow">Note Plugin</a> <em>2006-03-29</em> by <a href="mailto:olive@deep-ocean.net"; class="mail JSnocheck" title="olive@deep-ocean.net">Olivier Cortès / Eric Hameleers / Christopher Smith</a><br />Add Note/Important/Tip/Warning Capability (DIV+CSS box)</div></li><li><div class="li"><a href="http://wiki.splitbrain.org/plugin:xterm"; class="urlextern" title="http://wiki.splitbrain.org/plugin:xterm"; rel="nofollow">xterm Plugin</a> <em>2005-10-12</em> by <a href="mailto:tom_trenker@yahoo.com"; class="mail JSnocheck" title="tom_trenker@yahoo.com">Tom Trenker</a><br />for displaying xterm with formatting.<br /> <xterm> text **bold text** </xterm></div></li><li><div class="li"><a href="http://wiki.splitbrain.org/plugin:boxes"; class="urlextern" title="http://wiki.splitbrain.org/plugin:boxes"; rel="nofollow">Box Plugin</a> <em>2008-03-03</em> by <a href="mailto:chris@jalakai.co.uk"; class="mail JSnocheck" title="chris@jalakai.co.uk">Christopher Smith</a><br />Boxes with titles, colour and rounded corners. <br /> Syntax: <box width class colours|title> ... </box|caption><br /> width, class, colours title & caption are optional.<br /> The title can include some wiki markup, the box<br /> contents can include almost any wiki markup.</div></li></ul>
+</div>
+<!-- SECTION "Syntax Plugins" [14285-] --><div class="footnotes">
+<div class="fn"><a href="#fnt__1" id="fn__1" name="fn__1" class="fn_bot">1)</a>
+This is a footnote</div>
+</div>
+</body>
+</html>
diff --git a/gschem/scripts/gschemdoc.sh b/gschem/scripts/gschemdoc.sh
index 8cbfc4b..c24cde8 100644
--- a/gschem/scripts/gschemdoc.sh
+++ b/gschem/scripts/gschemdoc.sh
@@ -144,7 +144,7 @@ lookup_wiki()
LIVEWIKIROOT="http://geda.seul.org/wiki/";
# Munge wiki path to remove bad chars
- LOCALNAME=$(echo "$1" | tr "?\!*:" "____")
+ LOCALNAME=$(echo "$1" | tr "?\!*:" "___-")
if test -z "$LOCALNAME"; then
LOCALNAME="index"
fi
_______________________________________________
geda-cvs mailing list
geda-cvs@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-cvs