[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
gEDA-cvs: gaf.git: branch: master updated (1.6.1-20100214-296-gdc66dc0)
The branch, master has been updated
via dc66dc0af3426f92381e9b35573f5365371e527a (commit)
via 5497774003ce85443f774937b8f10df319b2a168 (commit)
via cb0eaabe02c154e6fe95ac49dd638fd6057e9883 (commit)
via 799d67452921ed1447e8b030ee268fe8c34c5785 (commit)
via 2e2e2bf53458d6fea7e4c8dd7736818470fde248 (commit)
via 5093ab820cdee5c2a41a4106567bbc87570f2e04 (commit)
from 1c531ec953bb3a7fe895eafc65c3d4f85c2603c6 (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 | 6 +-
docs/wiki/Makefile.am | 3 +-
docs/wiki/best_practices.html | 23 +-
docs/wiki/geda-bom_readme.html | 5 +-
docs/wiki/geda-bug_triage_guide.html | 100 +
.../wiki/geda-circuit_simulation_improvements.html | 157 +-
docs/wiki/geda-covered_mp.html | 4 +-
docs/wiki/geda-csygas.html | 661 +++---
docs/wiki/geda-cygwin.html | 65 +-
docs/wiki/geda-data_plotting_improvements.html | 95 +-
.../geda-data_structure_design_discussion.html | 123 +-
docs/wiki/geda-debian.fr.html | 14 +-
docs/wiki/geda-debian.html | 7 +-
.../geda-design_flow_and_hierarchy_roadmap.html | 110 +-
docs/wiki/geda-design_flow_roadmap.html | 8 +-
docs/wiki/geda-devel-tips.html | 311 ++--
docs/wiki/geda-developer.html | 135 ++
docs/wiki/geda-devmacosx.html | 77 +-
docs/wiki/geda-documentation.fr.html | 156 +-
docs/wiki/geda-documentation.html | 156 +-
docs/wiki/geda-download.html | 102 +
docs/wiki/geda-eagle_pcb_netlister_readme.html | 5 +-
docs/wiki/geda-example_hsm.html | 11 +-
docs/wiki/geda-example_usbjtag.html | 11 +-
docs/wiki/geda-experiences.html | 44 +-
docs/wiki/geda-faq-attribs.fr.html | 121 +-
docs/wiki/geda-faq-attribs.html | 249 +---
docs/wiki/geda-faq-gnetlist.fr.html | 58 +-
docs/wiki/geda-faq-gnetlist.html | 268 +++-
docs/wiki/geda-faq-gsch2pcb.fr.html | 47 +-
docs/wiki/geda-faq-gsch2pcb.html | 69 +-
docs/wiki/geda-faq-gschem.fr.html | 338 ++--
docs/wiki/geda-faq-gschem.html | 717 ++++---
docs/wiki/geda-faq-pcb.html | 92 +-
docs/wiki/geda-faq-simulation.fr.html | 90 +-
docs/wiki/geda-faq-simulation.html | 85 +-
docs/wiki/geda-faq.fr.html | 164 +-
docs/wiki/geda-faq.html | 127 +-
docs/wiki/geda-fbabgapp.html | 164 +-
docs/wiki/geda-fc1.html | 26 +-
docs/wiki/geda-fc2.html | 26 +-
docs/wiki/geda-fc3.html | 26 +-
docs/wiki/geda-fc4.html | 49 +-
docs/wiki/geda-fedora_rpm_installation.html | 235 +--
docs/wiki/geda-file_format_spec.html | 1199 ++++++-----
docs/wiki/geda-format_translation.html | 149 +-
docs/wiki/geda-gaf.html | 61 +
docs/wiki/geda-gaf_building_git_version.html | 105 +
docs/wiki/geda-gattrib_readme.html | 5 +-
docs/wiki/geda-gedasuite_installation.html | 71 +-
docs/wiki/geda-gerbv_mp.html | 7 +-
docs/wiki/geda-gerbv_pnp_readme.html | 4 +-
docs/wiki/geda-gfdl.html | 7 +-
docs/wiki/geda-glossaire.fr.html | 27 +-
docs/wiki/geda-glossary.fr.html | 27 +-
docs/wiki/geda-glossary.html | 23 +-
docs/wiki/geda-gnetlist_mp.html | 4 +-
docs/wiki/geda-gnetlist_scheme_tutorial.html | 165 +-
docs/wiki/geda-gnetlist_ug.html | 167 +-
docs/wiki/geda-gparts_dd.html | 1097 ++++++----
docs/wiki/geda-gparts_id.html | 66 +
docs/wiki/geda-gparts_ii.html | 351 ++++
docs/wiki/geda-gparts_tc.html | 34 +
docs/wiki/geda-gparts_ug.html | 107 +
docs/wiki/geda-grcsan.html | 181 +-
docs/wiki/geda-grenum_mp.html | 7 +-
docs/wiki/geda-gsch2pcb_readme.html | 7 +-
docs/wiki/geda-gsch2pcb_tutorial.html | 859 ++++++--
docs/wiki/geda-gsch2pcb_tutorial_releasenotes.html | 20 +-
docs/wiki/geda-gschem_mp.html | 4 +-
docs/wiki/geda-gschem_symbol_creation.html | 165 +-
docs/wiki/geda-gschem_ug.fr.html | 2055 ++++++++++---------
docs/wiki/geda-gschem_ug.html | 2195 ++++++++++----------
docs/wiki/geda-gschem_warmup.html | 39 +-
docs/wiki/geda-gsymcheck_mp.html | 7 +-
docs/wiki/geda-gtkwave_lxt2miner_mp.html | 7 +-
docs/wiki/geda-gtkwave_lxt2vcd_mp.html | 4 +-
docs/wiki/geda-gtkwave_mp.html | 4 +-
docs/wiki/geda-gtkwave_mvl2lxt_mp.html | 4 +-
docs/wiki/geda-gtkwave_mvl2vcd_mp.html | 7 +-
docs/wiki/geda-gtkwave_tex2vcd_mp.html | 4 +-
docs/wiki/geda-gtkwave_tla2vcd_mp.html | 4 +-
docs/wiki/geda-gtkwave_vcd2lxt2_mp.html | 4 +-
docs/wiki/geda-gtkwave_vcd2lxt_mp.html | 4 +-
docs/wiki/geda-gtkwave_vcd2vzt_mp.html | 4 +-
docs/wiki/geda-gtkwave_vzt2vcd_mp.html | 4 +-
docs/wiki/geda-gtkwave_vztminer_mp.html | 4 +-
docs/wiki/geda-guile_scripting.html | 65 +-
docs/wiki/geda-howto_report_bugs.html | 48 +
docs/wiki/geda-hse_howto.html | 5 +-
docs/wiki/geda-icarus_anc.html | 4 +-
docs/wiki/geda-icarus_extensions.html | 4 +-
docs/wiki/geda-icarus_glossary.html | 5 +-
docs/wiki/geda-icarus_ieee1364.html | 4 +-
docs/wiki/geda-icarus_mp.html | 4 +-
docs/wiki/geda-icarus_opcodes.html | 6 +-
docs/wiki/geda-icarus_quick_start.html | 4 +-
docs/wiki/geda-icarus_readme.html | 4 +-
docs/wiki/geda-icarus_vpi_mp.html | 4 +-
docs/wiki/geda-icarus_vpi_within_vvp.html | 6 +-
docs/wiki/geda-icarus_vvp_runtime.html | 4 +-
docs/wiki/geda-icarus_vvp_simulation.html | 6 +-
docs/wiki/geda-icarus_xilinx_hints.html | 7 +-
docs/wiki/geda-icarus_xnf.html | 6 +-
docs/wiki/geda-igarus_fpga_lcg.html | 5 +-
docs/wiki/geda-installation.fr.html | 145 +-
docs/wiki/geda-installation.html | 82 +-
docs/wiki/geda-installed_plugins.html | 47 +-
docs/wiki/geda-kig_howto.html | 175 +-
docs/wiki/geda-license.html | 121 ++
docs/wiki/geda-links.html | 545 +++++
docs/wiki/geda-mailinglists.html | 119 ++
docs/wiki/geda-master_attributes_list.html | 575 +++---
docs/wiki/geda-mcalc_readme.html | 4 +-
docs/wiki/geda-na_howto.html | 112 +-
docs/wiki/geda-ngnutmeg_mp.html | 7 +-
docs/wiki/geda-ngsconvert_mp.html | 7 +-
docs/wiki/geda-ngspice_and_gschem.html | 79 +-
docs/wiki/geda-ngspice_mp.html | 7 +-
docs/wiki/geda-olib_readme.html | 7 +-
docs/wiki/geda-pcb-quick_reference.fr.html | 508 +++---
docs/wiki/geda-pcb-quick_reference.html | 619 ++++---
.../geda-pcb_footprint_naming_conventions.html | 60 +-
docs/wiki/geda-pcb_footprints.html | 58 +-
docs/wiki/geda-pcb_funding_sow-fwdann_ideas.html | 47 +-
docs/wiki/geda-pcb_funding_sow-gui_ideas.html | 14 +-
docs/wiki/geda-pcb_funding_sow.html | 303 ++-
docs/wiki/geda-pcb_mp.html | 4 +-
docs/wiki/geda-pcb_tips.fr.html | 579 +++---
docs/wiki/geda-pcb_tips.html | 1009 +++++----
docs/wiki/geda-release_engineering.html | 124 +-
docs/wiki/geda-scg.fr.html | 207 +--
docs/wiki/geda-scg.html | 12 +-
docs/wiki/geda-scm.html | 331 ++--
docs/wiki/geda-screenshots.html | 65 +
docs/wiki/geda-sdb_howto.html | 699 ++++----
docs/wiki/geda-sn_readme.html | 5 +-
docs/wiki/geda-spice_improvements.html | 8 +-
docs/wiki/geda-spice_polys.html | 79 +
docs/wiki/geda-ssan.html | 241 +--
docs/wiki/geda-start.html | 6 +-
docs/wiki/geda-style_guide.html | 157 +-
docs/wiki/geda-suse_10.0.html | 19 +-
docs/wiki/geda-suse_10.1.html | 13 +-
docs/wiki/geda-suse_9.3.html | 16 +-
docs/wiki/geda-suse_rpm_installation.html | 161 +-
docs/wiki/geda-syntax_features.html | 12 +-
docs/wiki/geda-systemc_netlister_readme.html | 5 +-
docs/wiki/geda-tasks.html | 55 +-
docs/wiki/geda-todos.html | 273 ++--
docs/wiki/geda-todos_historical.html | 418 ++--
docs/wiki/geda-tools.html | 26 +
docs/wiki/geda-tragesym_readme.html | 7 +-
docs/wiki/geda-tragesym_tutorial.fr.html | 129 +-
docs/wiki/geda-tragesym_tutorial.html | 104 +-
docs/wiki/geda-transistor_guide.html | 69 +-
docs/wiki/geda-ubuntu.html | 15 +-
docs/wiki/geda-usage.fr.html | 92 +-
docs/wiki/geda-usage.html | 79 +-
docs/wiki/geda-vams_netlister_readme.html | 40 +-
docs/wiki/geda-verilog_netlister_readme.html | 7 +-
docs/wiki/geda-version_control_migration.html | 52 +-
docs/wiki/geda-vhdl_netlister_readme.html | 7 +-
docs/wiki/geda-wcalc_mp.html | 4 +-
docs/wiki/geda-wcalc_readme.html | 4 +-
docs/wiki/geda-wcalc_stdio_mp.html | 4 +-
docs/wiki/geda-wip-clipboard.html | 101 +-
docs/wiki/geda-xml_file_formats.html | 13 +-
docs/wiki/gerbv-projects.html | 26 +-
docs/wiki/glue-projects.html | 38 +-
docs/wiki/gschem-projects.html | 52 +-
docs/wiki/gsoc2007.html | 93 +-
docs/wiki/gsoc2007_projects.html | 329 ++--
docs/wiki/gsoc2008.html | 56 +-
docs/wiki/gsoc2008_projects.html | 82 +-
docs/wiki/gsoc2009.html | 59 +-
docs/wiki/gsoc2009_projects.html | 90 +-
docs/wiki/gsoc2010.html | 108 +
docs/wiki/gsoc2010_projects.html | 85 +
docs/wiki/gtkwave-projects.html | 8 +-
docs/wiki/gwave-projects.html | 18 +-
docs/wiki/images/Makefile.am | 4 +-
docs/wiki/images/interwiki/Makefile.am | 2 +-
docs/wiki/images/smileys/Makefile.am | 2 +-
docs/wiki/index.html | 133 +-
docs/wiki/libgeda3.html | 114 +-
docs/wiki/libgeda3_object_based_design.html | 150 +-
docs/wiki/media/Makefile.am | 2 +-
docs/wiki/media/geda/Makefile.am | 2 +-
docs/wiki/media/geda/gparts-bulk-import.png | Bin 0 -> 20538 bytes
docs/wiki/media/geda/gparts-ss-connect-types.png | Bin 0 -> 24112 bytes
docs/wiki/media/geda/gparts-ss-parts-3.png | Bin 0 -> 193784 bytes
docs/wiki/media/geda/gparts-ss-parts-4.png | Bin 0 -> 178949 bytes
docs/wiki/media/geda/gparts-ss-parts-4b.png | Bin 0 -> 37817 bytes
docs/wiki/media/geda/gparts_pkg.png | Bin 0 -> 5404 bytes
docs/wiki/media/geda/gparts_pkg_2.png | Bin 0 -> 7857 bytes
docs/wiki/media/geda/gparts_pkg_geom.png | Bin 0 -> 40525 bytes
docs/wiki/media/geda/gparts_pkg_sch.png | Bin 0 -> 37736 bytes
docs/wiki/media/geda/screenshot_gerbv.png | Bin 0 -> 1104802 bytes
docs/wiki/media/geda/screenshot_gerbv_thumb.png | Bin 0 -> 88735 bytes
docs/wiki/media/geda/screenshot_gschem.png | Bin 0 -> 326031 bytes
docs/wiki/media/geda/screenshot_gschem_osx.png | Bin 0 -> 207224 bytes
.../media/geda/screenshot_gschem_osx_thumb.png | Bin 0 -> 65666 bytes
docs/wiki/media/geda/screenshot_gschem_thumb.png | Bin 0 -> 40157 bytes
docs/wiki/media/geda/screenshot_pcb.png | Bin 0 -> 108201 bytes
docs/wiki/media/geda/screenshot_pcb_osx.png | Bin 0 -> 238430 bytes
docs/wiki/media/geda/screenshot_pcb_osx_thumb.png | Bin 0 -> 125615 bytes
docs/wiki/media/geda/screenshot_pcb_thumb.png | Bin 0 -> 129509 bytes
docs/wiki/media/tragesym/Makefile.am | 2 +-
docs/wiki/media/wiki/Makefile.am | 1 +
docs/wiki/pcb-projects.html | 111 +-
docs/wiki/pcb-roadmap.html | 323 +++
docs/wiki/start.html | 133 +-
docs/wiki/start_es.html | 43 +-
docs/wiki/start_fr.html | 78 +-
docs/wiki/wiki-dokuwiki.html | 166 --
docs/wiki/wiki-syntax.html | 666 ------
gattrib/docs/gattrib.1 | 2 +-
gattrib/po/ar.po | 2 +-
gattrib/po/bg.po | 2 +-
gattrib/po/de.po | 2 +-
gattrib/po/es.po | 2 +-
gattrib/po/fr.po | 2 +-
gattrib/po/hu.po | 2 +-
gattrib/po/it.po | 2 +-
gattrib/po/ml.po | 2 +-
gattrib/po/nl.po | 2 +-
gattrib/po/pl.po | 2 +-
gattrib/po/pt.po | 2 +-
gattrib/po/pt_BR.po | 2 +-
gattrib/po/ru.po | 2 +-
gattrib/po/tr.po | 2 +-
gattrib/po/zh_CN.po | 2 +-
gattrib/po/zh_TW.po | 2 +-
gnetlist/docs/gnetlist.1 | 2 +-
gschem/docs/gschem.1 | 2 +-
gschem/po/af.po | 899 ++++----
gschem/po/ar.po | 932 +++++----
gschem/po/bg.po | 883 ++++----
gschem/po/de.po | 932 +++++----
gschem/po/en_GB.po | 932 +++++----
gschem/po/es.po | 931 +++++----
gschem/po/fa.po | 886 ++++----
gschem/po/fr.po | 932 +++++----
gschem/po/he.po | 886 ++++----
gschem/po/hu.po | 932 +++++----
gschem/po/it.po | 932 +++++----
gschem/po/ja.po | 896 ++++----
gschem/po/ml.po | 883 ++++----
gschem/po/nl.po | 931 +++++----
gschem/po/pl.po | 932 +++++----
gschem/po/pt.po | 883 ++++----
gschem/po/pt_BR.po | 929 +++++----
gschem/po/ru.po | 932 +++++----
gschem/po/tr.po | 889 ++++----
gschem/po/zh_CN.po | 883 ++++----
gschem/po/zh_TW.po | 884 ++++----
gschem/src/x_dialog.c | 4 +-
gsymcheck/docs/gsymcheck.1 | 2 +-
libgeda/po/ar.po | 206 +-
libgeda/po/de.po | 241 ++--
libgeda/po/en_GB.po | 238 ++--
libgeda/po/es.po | 246 ++--
libgeda/po/fr.po | 240 ++--
libgeda/po/hu.po | 190 +-
libgeda/po/it.po | 205 +-
libgeda/po/nl.po | 242 ++--
libgeda/po/pl.po | 238 ++--
libgeda/po/ru.po | 238 ++--
libgeda/po/tr.po | 187 +-
libgeda/po/zh_CN.po | 184 +-
libgeda/po/zh_TW.po | 184 +-
utils/docs/grenum.1 | 2 +-
utils/docs/gsch2pcb.1 | 2 +-
274 files changed, 25536 insertions(+), 23138 deletions(-)
create mode 100644 docs/wiki/geda-bug_triage_guide.html
create mode 100644 docs/wiki/geda-developer.html
create mode 100644 docs/wiki/geda-download.html
create mode 100644 docs/wiki/geda-gaf.html
create mode 100644 docs/wiki/geda-gaf_building_git_version.html
create mode 100644 docs/wiki/geda-gparts_id.html
create mode 100644 docs/wiki/geda-gparts_ii.html
create mode 100644 docs/wiki/geda-gparts_tc.html
create mode 100644 docs/wiki/geda-gparts_ug.html
create mode 100644 docs/wiki/geda-howto_report_bugs.html
create mode 100644 docs/wiki/geda-license.html
create mode 100644 docs/wiki/geda-links.html
create mode 100644 docs/wiki/geda-mailinglists.html
create mode 100644 docs/wiki/geda-screenshots.html
create mode 100644 docs/wiki/geda-spice_polys.html
create mode 100644 docs/wiki/geda-tools.html
create mode 100644 docs/wiki/gsoc2010.html
create mode 100644 docs/wiki/gsoc2010_projects.html
create mode 100644 docs/wiki/media/geda/gparts-bulk-import.png
create mode 100644 docs/wiki/media/geda/gparts-ss-connect-types.png
create mode 100644 docs/wiki/media/geda/gparts-ss-parts-3.png
create mode 100644 docs/wiki/media/geda/gparts-ss-parts-4.png
create mode 100644 docs/wiki/media/geda/gparts-ss-parts-4b.png
create mode 100644 docs/wiki/media/geda/gparts_pkg.png
create mode 100644 docs/wiki/media/geda/gparts_pkg_2.png
create mode 100644 docs/wiki/media/geda/gparts_pkg_geom.png
create mode 100644 docs/wiki/media/geda/gparts_pkg_sch.png
create mode 100644 docs/wiki/media/geda/screenshot_gerbv.png
create mode 100644 docs/wiki/media/geda/screenshot_gerbv_thumb.png
create mode 100644 docs/wiki/media/geda/screenshot_gschem.png
create mode 100644 docs/wiki/media/geda/screenshot_gschem_osx.png
create mode 100644 docs/wiki/media/geda/screenshot_gschem_osx_thumb.png
create mode 100644 docs/wiki/media/geda/screenshot_gschem_thumb.png
create mode 100644 docs/wiki/media/geda/screenshot_pcb.png
create mode 100644 docs/wiki/media/geda/screenshot_pcb_osx.png
create mode 100644 docs/wiki/media/geda/screenshot_pcb_osx_thumb.png
create mode 100644 docs/wiki/media/geda/screenshot_pcb_thumb.png
create mode 100644 docs/wiki/pcb-roadmap.html
delete mode 100644 docs/wiki/wiki-dokuwiki.html
delete mode 100644 docs/wiki/wiki-syntax.html
=================
Commit Messages
=================
commit dc66dc0af3426f92381e9b35573f5365371e527a
Author: Ales Hvezda <ahvezda@xxxxxxxx>
Commit: Ales Hvezda <ahvezda@xxxxxxxx>
Another set of changes to all the po files
These changes were made when 'make distcheck' was run to create the
1.7.0 tarball.
:100644 100644 344fd37... 2ff7b7e... M gschem/po/af.po
:100644 100644 f65be7d... cc31fd5... M gschem/po/ar.po
:100644 100644 8a2ce11... 1242314... M gschem/po/bg.po
:100644 100644 a451abc... 86fffff... M gschem/po/de.po
:100644 100644 8d9a2f7... 8e5bcc8... M gschem/po/en_GB.po
:100644 100644 0777568... 3b0e86f... M gschem/po/es.po
:100644 100644 0fe1f19... bbd7425... M gschem/po/fa.po
:100644 100644 95e0b48... 1129313... M gschem/po/fr.po
:100644 100644 6289517... ccf7fe9... M gschem/po/he.po
:100644 100644 a02dbc4... 574b05c... M gschem/po/hu.po
:100644 100644 bfae2b6... e17e863... M gschem/po/it.po
:100644 100644 37b6a0a... 5680822... M gschem/po/ja.po
:100644 100644 bece1f2... 0708531... M gschem/po/ml.po
:100644 100644 ad9b9a3... 17e9fe8... M gschem/po/nl.po
:100644 100644 c7d713e... ce2ce13... M gschem/po/pl.po
:100644 100644 734e87c... 739d1fd... M gschem/po/pt.po
:100644 100644 5f41c80... 4b3e40e... M gschem/po/pt_BR.po
:100644 100644 fcef772... 04857fe... M gschem/po/ru.po
:100644 100644 816201f... 6316dbf... M gschem/po/tr.po
:100644 100644 9ef4f27... da865fc... M gschem/po/zh_CN.po
:100644 100644 0c5be66... 2f8e6d9... M gschem/po/zh_TW.po
commit 5497774003ce85443f774937b8f10df319b2a168
Author: Ales Hvezda <ahvezda@xxxxxxxx>
Commit: Ales Hvezda <ahvezda@xxxxxxxx>
Updated docs from the gEDA wiki
:100644 100644 59b3563... 8b208dc... M docs/wiki/Makefile.am
:100644 100644 06511f8... 783e08e... M docs/wiki/best_practices.html
:100644 100644 3d1659f... 3a2b908... M docs/wiki/geda-bom_readme.html
:000000 100644 0000000... 9ecbb2c... A docs/wiki/geda-bug_triage_guide.html
:100644 100644 f14db5f... 745f0cd... M docs/wiki/geda-circuit_simulation_improvements.html
:100644 100644 c456378... 16dd95a... M docs/wiki/geda-covered_mp.html
:100644 100644 8433488... c40c2ed... M docs/wiki/geda-csygas.html
:100644 100644 60d2f33... b223376... M docs/wiki/geda-cygwin.html
:100644 100644 329b69c... afc7032... M docs/wiki/geda-data_plotting_improvements.html
:100644 100644 d639d15... f79b679... M docs/wiki/geda-data_structure_design_discussion.html
:100644 100644 0679bda... 189c66a... M docs/wiki/geda-debian.fr.html
:100644 100644 110b34c... 210d20a... M docs/wiki/geda-debian.html
:100644 100644 261d0da... 79b086c... M docs/wiki/geda-design_flow_and_hierarchy_roadmap.html
:100644 100644 45f3a9a... d9f11c8... M docs/wiki/geda-design_flow_roadmap.html
:100644 100644 519e21d... bc7dbb0... M docs/wiki/geda-devel-tips.html
:000000 100644 0000000... 262fb88... A docs/wiki/geda-developer.html
:100644 100644 e0dc148... bcffe89... M docs/wiki/geda-devmacosx.html
:100644 100644 013d4a3... 37dec61... M docs/wiki/geda-documentation.fr.html
:100644 100644 51965f0... fcdf93b... M docs/wiki/geda-documentation.html
:000000 100644 0000000... 133369e... A docs/wiki/geda-download.html
:100644 100644 95a3fdc... ef0c394... M docs/wiki/geda-eagle_pcb_netlister_readme.html
:100644 100644 9068295... 18dc930... M docs/wiki/geda-example_hsm.html
:100644 100644 e1ff867... 7517b9e... M docs/wiki/geda-example_usbjtag.html
:100644 100644 45d8583... 67c5915... M docs/wiki/geda-experiences.html
:100644 100644 4df4505... c487c60... M docs/wiki/geda-faq-attribs.fr.html
:100644 100644 2fcd29a... de5e14f... M docs/wiki/geda-faq-attribs.html
:100644 100644 260a236... 9f5940b... M docs/wiki/geda-faq-gnetlist.fr.html
:100644 100644 078f1f7... 713bdae... M docs/wiki/geda-faq-gnetlist.html
:100644 100644 f78f399... 016024b... M docs/wiki/geda-faq-gsch2pcb.fr.html
:100644 100644 8531b3b... a0f6b40... M docs/wiki/geda-faq-gsch2pcb.html
:100644 100644 52b341f... 4935eb4... M docs/wiki/geda-faq-gschem.fr.html
:100644 100644 bc95071... 5fedcb2... M docs/wiki/geda-faq-gschem.html
:100644 100644 5ea33d3... 3c6b7f0... M docs/wiki/geda-faq-pcb.html
:100644 100644 843eb8f... b597792... M docs/wiki/geda-faq-simulation.fr.html
:100644 100644 ad780dd... 021683b... M docs/wiki/geda-faq-simulation.html
:100644 100644 8fbfef9... a8e1936... M docs/wiki/geda-faq.fr.html
:100644 100644 10d1663... f42d6bc... M docs/wiki/geda-faq.html
:100644 100644 f6a5e7e... 9824cbf... M docs/wiki/geda-fbabgapp.html
:100644 100644 6890814... f033ca6... M docs/wiki/geda-fc1.html
:100644 100644 f3893d4... 89f3e10... M docs/wiki/geda-fc2.html
:100644 100644 0ca4a9e... f7b4055... M docs/wiki/geda-fc3.html
:100644 100644 a57f8c6... 2c1ce2c... M docs/wiki/geda-fc4.html
:100644 100644 406a5b8... 7aa944f... M docs/wiki/geda-fedora_rpm_installation.html
:100644 100644 e408185... fe1c95c... M docs/wiki/geda-file_format_spec.html
:100644 100644 6c8d8ee... fa6ae3c... M docs/wiki/geda-format_translation.html
:000000 100644 0000000... bafea63... A docs/wiki/geda-gaf.html
:000000 100644 0000000... 44bd432... A docs/wiki/geda-gaf_building_git_version.html
:100644 100644 f4a7b19... 27975a0... M docs/wiki/geda-gattrib_readme.html
:100644 100644 c1ad0f4... 6ca54bb... M docs/wiki/geda-gedasuite_installation.html
:100644 100644 4a094e7... 3bfb4c6... M docs/wiki/geda-gerbv_mp.html
:100644 100644 ee4d44e... 87d2f4a... M docs/wiki/geda-gerbv_pnp_readme.html
:100644 100644 92b2690... e492549... M docs/wiki/geda-gfdl.html
:100644 100644 28974b3... c99d301... M docs/wiki/geda-glossaire.fr.html
:100644 100644 28974b3... e1198e3... M docs/wiki/geda-glossary.fr.html
:100644 100644 04218e3... 4e53508... M docs/wiki/geda-glossary.html
:100644 100644 2bcadf5... 5da3c24... M docs/wiki/geda-gnetlist_mp.html
:100644 100644 33306cf... e8901a6... M docs/wiki/geda-gnetlist_scheme_tutorial.html
:100644 100644 febcf24... 63fbd5e... M docs/wiki/geda-gnetlist_ug.html
:100644 100644 fbba04f... 0ce1753... M docs/wiki/geda-gparts_dd.html
:000000 100644 0000000... ec2a3de... A docs/wiki/geda-gparts_id.html
:000000 100644 0000000... 3e850a4... A docs/wiki/geda-gparts_ii.html
:000000 100644 0000000... 244c3e4... A docs/wiki/geda-gparts_tc.html
:000000 100644 0000000... 22bf695... A docs/wiki/geda-gparts_ug.html
:100644 100644 5be5687... aa33587... M docs/wiki/geda-grcsan.html
:100644 100644 2f63000... 6efa6a8... M docs/wiki/geda-grenum_mp.html
:100644 100644 6d22cf8... a30ad5a... M docs/wiki/geda-gsch2pcb_readme.html
:100644 100644 c03a9a4... 8ae86d7... M docs/wiki/geda-gsch2pcb_tutorial.html
:100644 100644 fc4aa9c... ab8efbf... M docs/wiki/geda-gsch2pcb_tutorial_releasenotes.html
:100644 100644 5710d10... 89fd0e1... M docs/wiki/geda-gschem_mp.html
:100644 100644 3eefee0... e9947f9... M docs/wiki/geda-gschem_symbol_creation.html
:100644 100644 673f062... c29806e... M docs/wiki/geda-gschem_ug.fr.html
:100644 100644 37fdbeb... 95ef68b... M docs/wiki/geda-gschem_ug.html
:100644 100644 b572695... 81b4af5... M docs/wiki/geda-gschem_warmup.html
:100644 100644 4324138... 1f83c8f... M docs/wiki/geda-gsymcheck_mp.html
:100644 100644 2015f50... 4523e58... M docs/wiki/geda-gtkwave_lxt2miner_mp.html
:100644 100644 0ea03ad... b570ce4... M docs/wiki/geda-gtkwave_lxt2vcd_mp.html
:100644 100644 74c42c8... 16b9779... M docs/wiki/geda-gtkwave_mp.html
:100644 100644 395911b... aa43916... M docs/wiki/geda-gtkwave_mvl2lxt_mp.html
:100644 100644 9725a35... a92ba65... M docs/wiki/geda-gtkwave_mvl2vcd_mp.html
:100644 100644 71825cd... 18d33ba... M docs/wiki/geda-gtkwave_tex2vcd_mp.html
:100644 100644 806b81c... 4815986... M docs/wiki/geda-gtkwave_tla2vcd_mp.html
:100644 100644 5b11ecf... 12a1e8e... M docs/wiki/geda-gtkwave_vcd2lxt2_mp.html
:100644 100644 2da6354... 0f229de... M docs/wiki/geda-gtkwave_vcd2lxt_mp.html
:100644 100644 30df085... 9b90e17... M docs/wiki/geda-gtkwave_vcd2vzt_mp.html
:100644 100644 b5b3636... 8b3e56e... M docs/wiki/geda-gtkwave_vzt2vcd_mp.html
:100644 100644 76771eb... b51687f... M docs/wiki/geda-gtkwave_vztminer_mp.html
:100644 100644 f807ac3... df250a2... M docs/wiki/geda-guile_scripting.html
:000000 100644 0000000... 6f3c0a1... A docs/wiki/geda-howto_report_bugs.html
:100644 100644 d5f8744... 2e0e076... M docs/wiki/geda-hse_howto.html
:100644 100644 41bb037... 0b5306d... M docs/wiki/geda-icarus_anc.html
:100644 100644 0004418... 5886b11... M docs/wiki/geda-icarus_extensions.html
:100644 100644 53a519e... a446fc6... M docs/wiki/geda-icarus_glossary.html
:100644 100644 89361ff... faadbb9... M docs/wiki/geda-icarus_ieee1364.html
:100644 100644 f98d924... 4f257a7... M docs/wiki/geda-icarus_mp.html
:100644 100644 961e601... 2021a54... M docs/wiki/geda-icarus_opcodes.html
:100644 100644 068bbf3... f05306f... M docs/wiki/geda-icarus_quick_start.html
:100644 100644 2ea4a48... db7dd02... M docs/wiki/geda-icarus_readme.html
:100644 100644 f3a8a41... 76e1cf1... M docs/wiki/geda-icarus_vpi_mp.html
:100644 100644 104378d... a734fc2... M docs/wiki/geda-icarus_vpi_within_vvp.html
:100644 100644 08277ee... cd00e5d... M docs/wiki/geda-icarus_vvp_runtime.html
:100644 100644 5a0b660... 8ec43b0... M docs/wiki/geda-icarus_vvp_simulation.html
:100644 100644 dc8b682... 0a825b6... M docs/wiki/geda-icarus_xilinx_hints.html
:100644 100644 fefadfb... 523fb49... M docs/wiki/geda-icarus_xnf.html
:100644 100644 806a427... 3c09cbd... M docs/wiki/geda-igarus_fpga_lcg.html
:100644 100644 9aa6a9e... 1100cc2... M docs/wiki/geda-installation.fr.html
:100644 100644 a035f2d... a4be17c... M docs/wiki/geda-installation.html
:100644 100644 39ae539... e042f2d... M docs/wiki/geda-installed_plugins.html
:100644 100644 b857166... ec77c9a... M docs/wiki/geda-kig_howto.html
:000000 100644 0000000... 85b5d40... A docs/wiki/geda-license.html
:000000 100644 0000000... 4ef5909... A docs/wiki/geda-links.html
:000000 100644 0000000... 9c72e9b... A docs/wiki/geda-mailinglists.html
:100644 100644 7287213... 2049806... M docs/wiki/geda-master_attributes_list.html
:100644 100644 ba58606... 1e807df... M docs/wiki/geda-mcalc_readme.html
:100644 100644 3328309... efd3829... M docs/wiki/geda-na_howto.html
:100644 100644 93cec8c... 7351162... M docs/wiki/geda-ngnutmeg_mp.html
:100644 100644 bf4030a... f1caa80... M docs/wiki/geda-ngsconvert_mp.html
:100644 100644 7cad960... fa7c3cb... M docs/wiki/geda-ngspice_and_gschem.html
:100644 100644 e2a68a9... 87bf9ce... M docs/wiki/geda-ngspice_mp.html
:100644 100644 72f3264... 55337b0... M docs/wiki/geda-olib_readme.html
:100644 100644 0bd7a4c... 743cb79... M docs/wiki/geda-pcb-quick_reference.fr.html
:100644 100644 45ce5fd... a3ac41f... M docs/wiki/geda-pcb-quick_reference.html
:100644 100644 983826d... 3232e23... M docs/wiki/geda-pcb_footprint_naming_conventions.html
:100644 100644 85352ff... ea1d00c... M docs/wiki/geda-pcb_footprints.html
:100644 100644 f0072a4... 59dc390... M docs/wiki/geda-pcb_funding_sow-fwdann_ideas.html
:100644 100644 326c2b3... 62ed20a... M docs/wiki/geda-pcb_funding_sow-gui_ideas.html
:100644 100644 8e933ee... 28d1de9... M docs/wiki/geda-pcb_funding_sow.html
:100644 100644 ed86825... 71d69f7... M docs/wiki/geda-pcb_mp.html
:100644 100644 a1ba425... ed306ba... M docs/wiki/geda-pcb_tips.fr.html
:100644 100644 998095a... 295019c... M docs/wiki/geda-pcb_tips.html
:100644 100644 bde39e2... aff5905... M docs/wiki/geda-release_engineering.html
:100644 100644 dae7f3d... 61b6519... M docs/wiki/geda-scg.fr.html
:100644 100644 3da3c56... 0b3d406... M docs/wiki/geda-scg.html
:100644 100644 840db3e... b2bde2f... M docs/wiki/geda-scm.html
:000000 100644 0000000... e956ba2... A docs/wiki/geda-screenshots.html
:100644 100644 0cf4f90... a4118b6... M docs/wiki/geda-sdb_howto.html
:100644 100644 039f97c... dc3013d... M docs/wiki/geda-sn_readme.html
:100644 100644 8451e13... b602fec... M docs/wiki/geda-spice_improvements.html
:000000 100644 0000000... 7bdb750... A docs/wiki/geda-spice_polys.html
:100644 100644 a7e6246... 7b5f68c... M docs/wiki/geda-ssan.html
:100644 100644 483bd45... 5f91f6c... M docs/wiki/geda-start.html
:100644 100644 37b05b7... 789d35d... M docs/wiki/geda-style_guide.html
:100644 100644 8559155... cfbc10f... M docs/wiki/geda-suse_10.0.html
:100644 100644 7605d8a... ca0dc73... M docs/wiki/geda-suse_10.1.html
:100644 100644 c0c8ce8... 1d9f311... M docs/wiki/geda-suse_9.3.html
:100644 100644 09f0df5... 51fa953... M docs/wiki/geda-suse_rpm_installation.html
:100644 100644 8cdb288... ef4912e... M docs/wiki/geda-syntax_features.html
:100644 100644 a1ed4d4... 4ee0c50... M docs/wiki/geda-systemc_netlister_readme.html
:100644 100644 1bbaec6... 132f4b1... M docs/wiki/geda-tasks.html
:100644 100644 ae00cd4... 8758d79... M docs/wiki/geda-todos.html
:100644 100644 967cb5b... 5f0533f... M docs/wiki/geda-todos_historical.html
:000000 100644 0000000... cc72b4a... A docs/wiki/geda-tools.html
:100644 100644 1d8087c... 3877d22... M docs/wiki/geda-tragesym_readme.html
:100644 100644 d5dfb24... 996f7d7... M docs/wiki/geda-tragesym_tutorial.fr.html
:100644 100644 c8563b8... 5432667... M docs/wiki/geda-tragesym_tutorial.html
:100644 100644 03e2480... ddbdaa0... M docs/wiki/geda-transistor_guide.html
:100644 100644 f2fc7dd... dd0b1a2... M docs/wiki/geda-ubuntu.html
:100644 100644 0a2eead... 6c664a9... M docs/wiki/geda-usage.fr.html
:100644 100644 1ff47dc... 95316d2... M docs/wiki/geda-usage.html
:100644 100644 8505d6c... f8d6caa... M docs/wiki/geda-vams_netlister_readme.html
:100644 100644 b55b04b... ecfbd19... M docs/wiki/geda-verilog_netlister_readme.html
:100644 100644 2d96277... 2a4c271... M docs/wiki/geda-version_control_migration.html
:100644 100644 90f1291... d0dcf03... M docs/wiki/geda-vhdl_netlister_readme.html
:100644 100644 5e24064... 3907f9d... M docs/wiki/geda-wcalc_mp.html
:100644 100644 548b9f9... b924338... M docs/wiki/geda-wcalc_readme.html
:100644 100644 43fb47e... 9a0502d... M docs/wiki/geda-wcalc_stdio_mp.html
:100644 100644 9881d11... 28a9c8a... M docs/wiki/geda-wip-clipboard.html
:100644 100644 3669f04... c531971... M docs/wiki/geda-xml_file_formats.html
:100644 100644 71c9684... 7c75431... M docs/wiki/gerbv-projects.html
:100644 100644 ed144ed... fc00763... M docs/wiki/glue-projects.html
:100644 100644 1e26b36... 77659ee... M docs/wiki/gschem-projects.html
:100644 100644 8ece0bd... 67e71e0... M docs/wiki/gsoc2007.html
:100644 100644 c2b847c... 75171d0... M docs/wiki/gsoc2007_projects.html
:100644 100644 04e07a2... aecec65... M docs/wiki/gsoc2008.html
:100644 100644 22c3f3a... 059082b... M docs/wiki/gsoc2008_projects.html
:100644 100644 f9bf230... 63635a2... M docs/wiki/gsoc2009.html
:100644 100644 e3157dd... 3e04c12... M docs/wiki/gsoc2009_projects.html
:000000 100644 0000000... 3728373... A docs/wiki/gsoc2010.html
:000000 100644 0000000... 016dd8e... A docs/wiki/gsoc2010_projects.html
:100644 100644 74ba1d3... 24693e5... M docs/wiki/gtkwave-projects.html
:100644 100644 78d0530... 59438fe... M docs/wiki/gwave-projects.html
:100644 100644 c971ff5... b8db727... M docs/wiki/images/Makefile.am
:100644 100644 0723035... a294f2c... M docs/wiki/images/interwiki/Makefile.am
:100644 100644 77e5024... 2e01243... M docs/wiki/images/smileys/Makefile.am
:100644 100644 19d0714... b68edad... M docs/wiki/index.html
:100644 100644 094f657... c74a2fe... M docs/wiki/libgeda3.html
:100644 100644 161d4a2... fad33c7... M docs/wiki/libgeda3_object_based_design.html
:100644 100644 943c93a... 2d837ea... M docs/wiki/media/Makefile.am
:100644 100644 64ae657... 7a5dfdc... M docs/wiki/media/geda/Makefile.am
:000000 100644 0000000... b80df8d... A docs/wiki/media/geda/gparts-bulk-import.png
:000000 100644 0000000... c72f543... A docs/wiki/media/geda/gparts-ss-connect-types.png
:000000 100644 0000000... 97b5919... A docs/wiki/media/geda/gparts-ss-parts-3.png
:000000 100644 0000000... 531a0e7... A docs/wiki/media/geda/gparts-ss-parts-4.png
:000000 100644 0000000... 73aef60... A docs/wiki/media/geda/gparts-ss-parts-4b.png
:000000 100644 0000000... de9c94a... A docs/wiki/media/geda/gparts_pkg.png
:000000 100644 0000000... bcd5a5a... A docs/wiki/media/geda/gparts_pkg_2.png
:000000 100644 0000000... 8af8819... A docs/wiki/media/geda/gparts_pkg_geom.png
:000000 100644 0000000... 4f20c77... A docs/wiki/media/geda/gparts_pkg_sch.png
:000000 100644 0000000... ce72032... A docs/wiki/media/geda/screenshot_gerbv.png
:000000 100644 0000000... 70da8e9... A docs/wiki/media/geda/screenshot_gerbv_thumb.png
:000000 100644 0000000... 6dffb58... A docs/wiki/media/geda/screenshot_gschem.png
:000000 100644 0000000... 30af0bd... A docs/wiki/media/geda/screenshot_gschem_osx.png
:000000 100644 0000000... 94eb0d4... A docs/wiki/media/geda/screenshot_gschem_osx_thumb.png
:000000 100644 0000000... 6b4344e... A docs/wiki/media/geda/screenshot_gschem_thumb.png
:000000 100644 0000000... dc0e15f... A docs/wiki/media/geda/screenshot_pcb.png
:000000 100644 0000000... 118fd94... A docs/wiki/media/geda/screenshot_pcb_osx.png
:000000 100644 0000000... 6b2e8a6... A docs/wiki/media/geda/screenshot_pcb_osx_thumb.png
:000000 100644 0000000... 271ecbb... A docs/wiki/media/geda/screenshot_pcb_thumb.png
:100644 100644 fd88f56... 857988c... M docs/wiki/media/tragesym/Makefile.am
:100644 100644 5b6761f... e048a23... M docs/wiki/media/wiki/Makefile.am
:100644 100644 f546a40... 65a2956... M docs/wiki/pcb-projects.html
:000000 100644 0000000... 547a224... A docs/wiki/pcb-roadmap.html
:100644 100644 19d0714... b68edad... M docs/wiki/start.html
:100644 100644 4408be8... 69a5df9... M docs/wiki/start_es.html
:100644 100644 b629fc9... 700398c... M docs/wiki/start_fr.html
:100644 000000 aac904c... 0000000... D docs/wiki/wiki-dokuwiki.html
:100644 000000 156e0c2... 0000000... D docs/wiki/wiki-syntax.html
commit cb0eaabe02c154e6fe95ac49dd638fd6057e9883
Author: Ales Hvezda <ahvezda@xxxxxxxx>
Commit: Ales Hvezda <ahvezda@xxxxxxxx>
Updated copyright data in gschem's about box
:100644 100644 4cd4c62... 3b2b4be... M gschem/src/x_dialog.c
commit 799d67452921ed1447e8b030ee268fe8c34c5785
Author: Ales Hvezda <ahvezda@xxxxxxxx>
Commit: Ales Hvezda <ahvezda@xxxxxxxx>
Updated version strings in all man pages
:100644 100644 6096e1c... 20ec6cf... M gattrib/docs/gattrib.1
:100644 100644 a20edb1... 601d1f5... M gnetlist/docs/gnetlist.1
:100644 100644 153b884... f198fa4... M gschem/docs/gschem.1
:100644 100644 9a0985a... e855b33... M gsymcheck/docs/gsymcheck.1
:100644 100644 4bc1652... 075c4ab... M utils/docs/grenum.1
:100644 100644 9013896... 8d90676... M utils/docs/gsch2pcb.1
commit 2e2e2bf53458d6fea7e4c8dd7736818470fde248
Author: Ales Hvezda <ahvezda@xxxxxxxx>
Commit: Ales Hvezda <ahvezda@xxxxxxxx>
Manually ran make update-po in order to prep for the make distcheck
:100644 100644 6b8260c... 9330bc8... M gattrib/po/ar.po
:100644 100644 4f3aae9... 5497432... M gattrib/po/bg.po
:100644 100644 07f4773... 933002f... M gattrib/po/de.po
:100644 100644 717665f... d5199b4... M gattrib/po/es.po
:100644 100644 0acdf84... acdc17f... M gattrib/po/fr.po
:100644 100644 0e028b7... f6de63f... M gattrib/po/hu.po
:100644 100644 25b3374... 4204129... M gattrib/po/it.po
:100644 100644 9ff5c2d... 955f78e... M gattrib/po/ml.po
:100644 100644 01a858b... 19802dd... M gattrib/po/nl.po
:100644 100644 ff54c62... 5520537... M gattrib/po/pl.po
:100644 100644 019bd25... fe54074... M gattrib/po/pt.po
:100644 100644 a7c8ce0... 72d64ce... M gattrib/po/pt_BR.po
:100644 100644 8f0e7da... 3b8aa10... M gattrib/po/ru.po
:100644 100644 b7d4b37... e4ac29c... M gattrib/po/tr.po
:100644 100644 28700a1... d1875a9... M gattrib/po/zh_CN.po
:100644 100644 5c10844... bdb511a... M gattrib/po/zh_TW.po
:100644 100644 5c14ad5... 344fd37... M gschem/po/af.po
:100644 100644 41f2910... f65be7d... M gschem/po/ar.po
:100644 100644 1e19020... 8a2ce11... M gschem/po/bg.po
:100644 100644 3c12062... a451abc... M gschem/po/de.po
:100644 100644 b2278b2... 8d9a2f7... M gschem/po/en_GB.po
:100644 100644 6c4967b... 0777568... M gschem/po/es.po
:100644 100644 3918f72... 0fe1f19... M gschem/po/fa.po
:100644 100644 5466d5b... 95e0b48... M gschem/po/fr.po
:100644 100644 a3e8427... 6289517... M gschem/po/he.po
:100644 100644 e84e9fa... a02dbc4... M gschem/po/hu.po
:100644 100644 d0fea1e... bfae2b6... M gschem/po/it.po
:100644 100644 7a6debb... 37b6a0a... M gschem/po/ja.po
:100644 100644 b9b39bc... bece1f2... M gschem/po/ml.po
:100644 100644 98f931d... ad9b9a3... M gschem/po/nl.po
:100644 100644 e31f16f... c7d713e... M gschem/po/pl.po
:100644 100644 e01018e... 734e87c... M gschem/po/pt.po
:100644 100644 16ac716... 5f41c80... M gschem/po/pt_BR.po
:100644 100644 9e2c71b... fcef772... M gschem/po/ru.po
:100644 100644 7fe046b... 816201f... M gschem/po/tr.po
:100644 100644 b5c5a1a... 9ef4f27... M gschem/po/zh_CN.po
:100644 100644 1f916e2... 0c5be66... M gschem/po/zh_TW.po
:100644 100644 8741629... d060821... M libgeda/po/ar.po
:100644 100644 08a2bc6... a5714d0... M libgeda/po/de.po
:100644 100644 7f53502... 27859ef... M libgeda/po/en_GB.po
:100644 100644 1265398... f9153e5... M libgeda/po/es.po
:100644 100644 8c178c8... 08ab32d... M libgeda/po/fr.po
:100644 100644 65b134b... 3f2f642... M libgeda/po/hu.po
:100644 100644 321a2f2... 1a28e05... M libgeda/po/it.po
:100644 100644 405a147... 8cbe316... M libgeda/po/nl.po
:100644 100644 a5e166d... f939f2f... M libgeda/po/pl.po
:100644 100644 4da7e8b... 253247d... M libgeda/po/ru.po
:100644 100644 9948e2e... 0d29927... M libgeda/po/tr.po
:100644 100644 01d863a... c626b52... M libgeda/po/zh_CN.po
:100644 100644 de460c5... 4d25861... M libgeda/po/zh_TW.po
commit 5093ab820cdee5c2a41a4106567bbc87570f2e04
Author: Ales Hvezda <ahvezda@xxxxxxxx>
Commit: Ales Hvezda <ahvezda@xxxxxxxx>
Updated package version, release date, and libgeda revision for 1.7.0
:100644 100644 69a5c5a... bb6f33a... M configure.ac
=========
Changes
=========
commit dc66dc0af3426f92381e9b35573f5365371e527a
Author: Ales Hvezda <ahvezda@xxxxxxxx>
Commit: Ales Hvezda <ahvezda@xxxxxxxx>
Another set of changes to all the po files
These changes were made when 'make distcheck' was run to create the
1.7.0 tarball.
diff --git a/gschem/po/af.po b/gschem/po/af.po
index 344fd37..2ff7b7e 100644
--- a/gschem/po/af.po
+++ b/gschem/po/af.po
@@ -6,7 +6,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda-gschem\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2011-01-16 00:11-0500\n"
+"POT-Creation-Date: 2011-01-16 01:15-0500\n"
"PO-Revision-Date: 2010-02-14 01:03+0000\n"
"Last-Translator: Bernd Jendrissek <Unknown>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -1345,8 +1345,8 @@ msgstr "gEDA: GPL Elektroniese Ontwerp Outomatisering"
#: gschem/src/x_dialog.c:2146
msgid ""
-"Copyright © 1998-2009 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
-"Copyright © 1998-2009 gEDA Contributors (see ChangeLog for details)"
+"Copyright © 1998-2011 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
+"Copyright © 1998-2011 gEDA Contributors (see ChangeLog for details)"
msgstr ""
# FIXME: May need to have a deëlteken on second 'o'.
diff --git a/gschem/po/ar.po b/gschem/po/ar.po
index f65be7d..cc31fd5 100644
--- a/gschem/po/ar.po
+++ b/gschem/po/ar.po
@@ -6,7 +6,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2011-01-16 00:11-0500\n"
+"POT-Creation-Date: 2011-01-16 01:15-0500\n"
"PO-Revision-Date: 2010-02-14 06:08+0000\n"
"Last-Translator: عبداÙ?Ù?Ù? Ø´Ù?Ù? (Abdellah Chelli) <Unknown>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -1351,8 +1351,8 @@ msgstr "gEDA: GPL Electronic Design Automation (أتÙ?تة اÙ?تصÙ?Ù?Ù? اÙ?Ø¥
#: gschem/src/x_dialog.c:2146
msgid ""
-"Copyright © 1998-2009 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
-"Copyright © 1998-2009 gEDA Contributors (see ChangeLog for details)"
+"Copyright © 1998-2011 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
+"Copyright © 1998-2011 gEDA Contributors (see ChangeLog for details)"
msgstr ""
#: gschem/src/x_dialog.c:2205
diff --git a/gschem/po/bg.po b/gschem/po/bg.po
index 8a2ce11..1242314 100644
--- a/gschem/po/bg.po
+++ b/gschem/po/bg.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2011-01-16 00:11-0500\n"
+"POT-Creation-Date: 2011-01-16 01:15-0500\n"
"PO-Revision-Date: 2010-02-11 03:36+0000\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -1332,8 +1332,8 @@ msgstr ""
#: gschem/src/x_dialog.c:2146
msgid ""
-"Copyright © 1998-2009 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
-"Copyright © 1998-2009 gEDA Contributors (see ChangeLog for details)"
+"Copyright © 1998-2011 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
+"Copyright © 1998-2011 gEDA Contributors (see ChangeLog for details)"
msgstr ""
#: gschem/src/x_dialog.c:2205
diff --git a/gschem/po/de.po b/gschem/po/de.po
index a451abc..86fffff 100644
--- a/gschem/po/de.po
+++ b/gschem/po/de.po
@@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2011-01-16 00:11-0500\n"
+"POT-Creation-Date: 2011-01-16 01:15-0500\n"
"PO-Revision-Date: 2010-02-14 01:05+0000\n"
"Last-Translator: Werner Hoch <werner.ho@xxxxxx>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -1386,8 +1386,8 @@ msgstr ""
#: gschem/src/x_dialog.c:2146
msgid ""
-"Copyright © 1998-2009 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
-"Copyright © 1998-2009 gEDA Contributors (see ChangeLog for details)"
+"Copyright © 1998-2011 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
+"Copyright © 1998-2011 gEDA Contributors (see ChangeLog for details)"
msgstr ""
#: gschem/src/x_dialog.c:2205
diff --git a/gschem/po/en_GB.po b/gschem/po/en_GB.po
index 8d9a2f7..8e5bcc8 100644
--- a/gschem/po/en_GB.po
+++ b/gschem/po/en_GB.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2011-01-16 00:11-0500\n"
+"POT-Creation-Date: 2011-01-16 01:15-0500\n"
"PO-Revision-Date: 2010-02-11 03:01+0000\n"
"Last-Translator: Peter Clifton <pcjc2@xxxxxxxxx>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -1359,8 +1359,8 @@ msgstr "gEDA: GPL Electronic Design Automation"
#: gschem/src/x_dialog.c:2146
msgid ""
-"Copyright © 1998-2009 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
-"Copyright © 1998-2009 gEDA Contributors (see ChangeLog for details)"
+"Copyright © 1998-2011 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
+"Copyright © 1998-2011 gEDA Contributors (see ChangeLog for details)"
msgstr ""
#: gschem/src/x_dialog.c:2205
diff --git a/gschem/po/es.po b/gschem/po/es.po
index 0777568..3b0e86f 100644
--- a/gschem/po/es.po
+++ b/gschem/po/es.po
@@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: gschem VERSION\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2011-01-16 00:11-0500\n"
+"POT-Creation-Date: 2011-01-16 01:15-0500\n"
"PO-Revision-Date: 2010-02-14 01:04+0000\n"
"Last-Translator: Carlos Nieves Ã?nega <Unknown>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -1404,9 +1404,10 @@ msgid "gEDA: GPL Electronic Design Automation"
msgstr "gEDA: Automatización de Diseño Electrónico GPL"
#: gschem/src/x_dialog.c:2146
+#, fuzzy
msgid ""
-"Copyright © 1998-2009 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
-"Copyright © 1998-2009 gEDA Contributors (see ChangeLog for details)"
+"Copyright © 1998-2011 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
+"Copyright © 1998-2011 gEDA Contributors (see ChangeLog for details)"
msgstr ""
"Copyright © 1998-2009 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
"Copyright © 1998-2009 gEDA Contributors (véase fichero ChangeLog para más "
diff --git a/gschem/po/fa.po b/gschem/po/fa.po
index 0fe1f19..bbd7425 100644
--- a/gschem/po/fa.po
+++ b/gschem/po/fa.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2011-01-16 00:11-0500\n"
+"POT-Creation-Date: 2011-01-16 01:15-0500\n"
"PO-Revision-Date: 2010-01-31 15:45+0000\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -1332,8 +1332,8 @@ msgstr ""
#: gschem/src/x_dialog.c:2146
msgid ""
-"Copyright © 1998-2009 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
-"Copyright © 1998-2009 gEDA Contributors (see ChangeLog for details)"
+"Copyright © 1998-2011 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
+"Copyright © 1998-2011 gEDA Contributors (see ChangeLog for details)"
msgstr ""
#: gschem/src/x_dialog.c:2205
diff --git a/gschem/po/fr.po b/gschem/po/fr.po
index 95e0b48..1129313 100644
--- a/gschem/po/fr.po
+++ b/gschem/po/fr.po
@@ -10,7 +10,7 @@ msgid ""
msgstr ""
"Project-Id-Version: fr_FR\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2011-01-16 00:11-0500\n"
+"POT-Creation-Date: 2011-01-16 01:15-0500\n"
"PO-Revision-Date: 2010-02-14 01:03+0000\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -1367,8 +1367,8 @@ msgstr ""
#: gschem/src/x_dialog.c:2146
msgid ""
-"Copyright © 1998-2009 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
-"Copyright © 1998-2009 gEDA Contributors (see ChangeLog for details)"
+"Copyright © 1998-2011 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
+"Copyright © 1998-2011 gEDA Contributors (see ChangeLog for details)"
msgstr ""
#: gschem/src/x_dialog.c:2205
diff --git a/gschem/po/he.po b/gschem/po/he.po
index 6289517..ccf7fe9 100644
--- a/gschem/po/he.po
+++ b/gschem/po/he.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2011-01-16 00:11-0500\n"
+"POT-Creation-Date: 2011-01-16 01:15-0500\n"
"PO-Revision-Date: 2010-02-11 03:50+0000\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -1332,8 +1332,8 @@ msgstr ""
#: gschem/src/x_dialog.c:2146
msgid ""
-"Copyright © 1998-2009 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
-"Copyright © 1998-2009 gEDA Contributors (see ChangeLog for details)"
+"Copyright © 1998-2011 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
+"Copyright © 1998-2011 gEDA Contributors (see ChangeLog for details)"
msgstr ""
#: gschem/src/x_dialog.c:2205
diff --git a/gschem/po/hu.po b/gschem/po/hu.po
index a02dbc4..574b05c 100644
--- a/gschem/po/hu.po
+++ b/gschem/po/hu.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2011-01-16 00:11-0500\n"
+"POT-Creation-Date: 2011-01-16 01:15-0500\n"
"PO-Revision-Date: 2010-02-13 10:43+0000\n"
"Last-Translator: kop <Unknown>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -1346,8 +1346,8 @@ msgstr ""
#: gschem/src/x_dialog.c:2146
msgid ""
-"Copyright © 1998-2009 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
-"Copyright © 1998-2009 gEDA Contributors (see ChangeLog for details)"
+"Copyright © 1998-2011 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
+"Copyright © 1998-2011 gEDA Contributors (see ChangeLog for details)"
msgstr ""
#: gschem/src/x_dialog.c:2205
diff --git a/gschem/po/it.po b/gschem/po/it.po
index bfae2b6..e17e863 100644
--- a/gschem/po/it.po
+++ b/gschem/po/it.po
@@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2011-01-16 00:11-0500\n"
+"POT-Creation-Date: 2011-01-16 01:15-0500\n"
"PO-Revision-Date: 2010-02-14 01:07+0000\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -1377,8 +1377,8 @@ msgstr ""
#: gschem/src/x_dialog.c:2146
msgid ""
-"Copyright © 1998-2009 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
-"Copyright © 1998-2009 gEDA Contributors (see ChangeLog for details)"
+"Copyright © 1998-2011 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
+"Copyright © 1998-2011 gEDA Contributors (see ChangeLog for details)"
msgstr ""
#: gschem/src/x_dialog.c:2205
diff --git a/gschem/po/ja.po b/gschem/po/ja.po
index 37b6a0a..5680822 100644
--- a/gschem/po/ja.po
+++ b/gschem/po/ja.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2011-01-16 00:11-0500\n"
+"POT-Creation-Date: 2011-01-16 01:15-0500\n"
"PO-Revision-Date: 2010-02-14 01:03+0000\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -1345,8 +1345,8 @@ msgstr ""
#: gschem/src/x_dialog.c:2146
msgid ""
-"Copyright © 1998-2009 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
-"Copyright © 1998-2009 gEDA Contributors (see ChangeLog for details)"
+"Copyright © 1998-2011 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
+"Copyright © 1998-2011 gEDA Contributors (see ChangeLog for details)"
msgstr ""
#: gschem/src/x_dialog.c:2205
diff --git a/gschem/po/ml.po b/gschem/po/ml.po
index bece1f2..0708531 100644
--- a/gschem/po/ml.po
+++ b/gschem/po/ml.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2011-01-16 00:11-0500\n"
+"POT-Creation-Date: 2011-01-16 01:15-0500\n"
"PO-Revision-Date: 2010-02-11 03:33+0000\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -1332,8 +1332,8 @@ msgstr ""
#: gschem/src/x_dialog.c:2146
msgid ""
-"Copyright © 1998-2009 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
-"Copyright © 1998-2009 gEDA Contributors (see ChangeLog for details)"
+"Copyright © 1998-2011 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
+"Copyright © 1998-2011 gEDA Contributors (see ChangeLog for details)"
msgstr ""
#: gschem/src/x_dialog.c:2205
diff --git a/gschem/po/nl.po b/gschem/po/nl.po
index ad9b9a3..17e9fe8 100644
--- a/gschem/po/nl.po
+++ b/gschem/po/nl.po
@@ -6,7 +6,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda-gschem\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2011-01-16 00:11-0500\n"
+"POT-Creation-Date: 2011-01-16 01:15-0500\n"
"PO-Revision-Date: 2010-02-14 01:04+0000\n"
"Last-Translator: Bert Timmerman <bert.timmerman@xxxxxxxxx>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -1367,9 +1367,10 @@ msgid "gEDA: GPL Electronic Design Automation"
msgstr "gEDA: GPL Elektronische Ontwerp Automatisering"
#: gschem/src/x_dialog.c:2146
+#, fuzzy
msgid ""
-"Copyright © 1998-2009 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
-"Copyright © 1998-2009 gEDA Contributors (see ChangeLog for details)"
+"Copyright © 1998-2011 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
+"Copyright © 1998-2011 gEDA Contributors (see ChangeLog for details)"
msgstr ""
"Copyright © 1998-2009 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
"Copyright © 1998-2009 gEDA Contributors (zie het WijzigingsLogboek voor "
diff --git a/gschem/po/pl.po b/gschem/po/pl.po
index c7d713e..ce2ce13 100644
--- a/gschem/po/pl.po
+++ b/gschem/po/pl.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2011-01-16 00:11-0500\n"
+"POT-Creation-Date: 2011-01-16 01:15-0500\n"
"PO-Revision-Date: 2010-02-12 13:16+0000\n"
"Last-Translator: Krzysztof KoÅ?ciuszkiewicz <k.kosciuszkiewicz@xxxxxxxxx>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -1352,8 +1352,8 @@ msgstr ""
#: gschem/src/x_dialog.c:2146
msgid ""
-"Copyright © 1998-2009 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
-"Copyright © 1998-2009 gEDA Contributors (see ChangeLog for details)"
+"Copyright © 1998-2011 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
+"Copyright © 1998-2011 gEDA Contributors (see ChangeLog for details)"
msgstr ""
#: gschem/src/x_dialog.c:2205
diff --git a/gschem/po/pt.po b/gschem/po/pt.po
index 734e87c..739d1fd 100644
--- a/gschem/po/pt.po
+++ b/gschem/po/pt.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2011-01-16 00:11-0500\n"
+"POT-Creation-Date: 2011-01-16 01:15-0500\n"
"PO-Revision-Date: 2010-02-11 02:58+0000\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -1332,8 +1332,8 @@ msgstr ""
#: gschem/src/x_dialog.c:2146
msgid ""
-"Copyright © 1998-2009 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
-"Copyright © 1998-2009 gEDA Contributors (see ChangeLog for details)"
+"Copyright © 1998-2011 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
+"Copyright © 1998-2011 gEDA Contributors (see ChangeLog for details)"
msgstr ""
#: gschem/src/x_dialog.c:2205
diff --git a/gschem/po/pt_BR.po b/gschem/po/pt_BR.po
index 5f41c80..4b3e40e 100644
--- a/gschem/po/pt_BR.po
+++ b/gschem/po/pt_BR.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2011-01-16 00:11-0500\n"
+"POT-Creation-Date: 2011-01-16 01:15-0500\n"
"PO-Revision-Date: 2010-02-14 01:04+0000\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -1349,8 +1349,8 @@ msgstr ""
#: gschem/src/x_dialog.c:2146
msgid ""
-"Copyright © 1998-2009 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
-"Copyright © 1998-2009 gEDA Contributors (see ChangeLog for details)"
+"Copyright © 1998-2011 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
+"Copyright © 1998-2011 gEDA Contributors (see ChangeLog for details)"
msgstr ""
#: gschem/src/x_dialog.c:2205
diff --git a/gschem/po/ru.po b/gschem/po/ru.po
index fcef772..04857fe 100644
--- a/gschem/po/ru.po
+++ b/gschem/po/ru.po
@@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2011-01-16 00:11-0500\n"
+"POT-Creation-Date: 2011-01-16 01:15-0500\n"
"PO-Revision-Date: 2010-02-14 01:05+0000\n"
"Last-Translator: Sergey Alyoshin <alyoshin.s@xxxxxxxxx>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -1367,8 +1367,8 @@ msgstr ""
#: gschem/src/x_dialog.c:2146
msgid ""
-"Copyright © 1998-2009 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
-"Copyright © 1998-2009 gEDA Contributors (see ChangeLog for details)"
+"Copyright © 1998-2011 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
+"Copyright © 1998-2011 gEDA Contributors (see ChangeLog for details)"
msgstr ""
#: gschem/src/x_dialog.c:2205
diff --git a/gschem/po/tr.po b/gschem/po/tr.po
index 816201f..6316dbf 100644
--- a/gschem/po/tr.po
+++ b/gschem/po/tr.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2011-01-16 00:11-0500\n"
+"POT-Creation-Date: 2011-01-16 01:15-0500\n"
"PO-Revision-Date: 2010-02-11 03:48+0000\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -1332,8 +1332,8 @@ msgstr ""
#: gschem/src/x_dialog.c:2146
msgid ""
-"Copyright © 1998-2009 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
-"Copyright © 1998-2009 gEDA Contributors (see ChangeLog for details)"
+"Copyright © 1998-2011 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
+"Copyright © 1998-2011 gEDA Contributors (see ChangeLog for details)"
msgstr ""
#: gschem/src/x_dialog.c:2205
diff --git a/gschem/po/zh_CN.po b/gschem/po/zh_CN.po
index 9ef4f27..da865fc 100644
--- a/gschem/po/zh_CN.po
+++ b/gschem/po/zh_CN.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2011-01-16 00:11-0500\n"
+"POT-Creation-Date: 2011-01-16 01:15-0500\n"
"PO-Revision-Date: 2010-02-11 03:18+0000\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -1332,8 +1332,8 @@ msgstr ""
#: gschem/src/x_dialog.c:2146
msgid ""
-"Copyright © 1998-2009 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
-"Copyright © 1998-2009 gEDA Contributors (see ChangeLog for details)"
+"Copyright © 1998-2011 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
+"Copyright © 1998-2011 gEDA Contributors (see ChangeLog for details)"
msgstr ""
#: gschem/src/x_dialog.c:2205
diff --git a/gschem/po/zh_TW.po b/gschem/po/zh_TW.po
index 0c5be66..2f8e6d9 100644
--- a/gschem/po/zh_TW.po
+++ b/gschem/po/zh_TW.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2011-01-16 00:11-0500\n"
+"POT-Creation-Date: 2011-01-16 01:15-0500\n"
"PO-Revision-Date: 2010-02-11 03:31+0000\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -1332,8 +1332,8 @@ msgstr ""
#: gschem/src/x_dialog.c:2146
msgid ""
-"Copyright © 1998-2009 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
-"Copyright © 1998-2009 gEDA Contributors (see ChangeLog for details)"
+"Copyright © 1998-2011 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
+"Copyright © 1998-2011 gEDA Contributors (see ChangeLog for details)"
msgstr ""
#: gschem/src/x_dialog.c:2205
commit 5497774003ce85443f774937b8f10df319b2a168
Author: Ales Hvezda <ahvezda@xxxxxxxx>
Commit: Ales Hvezda <ahvezda@xxxxxxxx>
Updated docs from the gEDA wiki
diff --git a/docs/wiki/Makefile.am b/docs/wiki/Makefile.am
index 59b3563..8b208dc 100644
--- a/docs/wiki/Makefile.am
+++ b/docs/wiki/Makefile.am
@@ -1,10 +1,11 @@
+
docname=wiki
docsdir = $(docdir)/$(docname)/
SUBDIRS = images media
-docs_DATA = geda-faq-gschem.html geda-experiences.html geda-icarus_xnf.html geda-verilog_netlister_readme.html geda-tragesym_tutorial.fr.html geda-ngnutmeg_mp.html wiki-syntax.html geda-ssan.html geda-example_usbjtag.html geda-gnetlist_scheme_tutorial.html geda-faq-gsch2pcb.fr.html geda-icarus_readme.html geda-gsch2pcb_tutorial.html geda-na_howto.html gsoc2009.html geda-example_hsm.html libgeda3_object_based_design.html geda-fc3.html geda-glossary.html geda-kig_howto.html geda-icarus_vvp_simulation.html geda-pcb_footprints.html geda-wip-clipboard.html geda-faq.html geda-faq-gsch2pcb.html geda-todos_historical.html geda-covered_mp.html geda-pcb_tips.html gsoc2009_projects.html geda-wcalc_mp.html best_practices.html index.html geda-syntax_features.html geda-icarus_opcodes.html geda-gparts_dd.html geda-gtkwave_vztminer_mp.html geda-grcsan.html geda-scg.fr.html geda-gsch2pcb_readme.html geda-debian.fr.html geda-gtkwave_vcd2vzt_mp.html geda-installation.fr.html geda-gtkwave_mp.html geda-format_translation.html geda-glossary.fr.html geda-ngsconvert_mp.html geda-documentation.fr.html geda-glossaire.fr.html geda-icarus_mp.html geda-icarus_vpi_mp.html geda-devel-tips.html geda-gschem_warmup.html geda-style_guide.html geda-fc1.html geda-transistor_guide.html geda-icarus_vvp_runtime.html geda-tragesym_tutorial.html start_fr.html geda-release_engineering.html gsoc2007_projects.html gsoc2007.html geda-gsymcheck_mp.html geda-gtkwave_mvl2vcd_mp.html design.css geda-ngspice_and_gschem.html gsoc2008_projects.html geda-data_plotting_improvements.html geda-tragesym_readme.html geda-suse_10.1.html geda-hse_howto.html style.css geda-eagle_pcb_netlister_readme.html geda-gattrib_readme.html geda-systemc_netlister_readme.html geda-spice_improvements.html geda-pcb_funding_sow-fwdann_ideas.html geda-faq-gschem.fr.html geda-ngspice_mp.html geda-version_control_migration.html geda-usage.fr.html geda-pcb-quick_reference.fr.html geda-olib_readme.html geda-wcalc_readme.html geda-sn_readme.html libgeda3.html geda-fedora_rpm_installation.html geda-gnetlist_ug.html wiki-dokuwiki.html geda-debian.html geda-gschem_ug.html geda-faq-attribs.fr.html geda-gtkwave_lxt2miner_mp.html geda-suse_10.0.html geda-design_flow_roadmap.html geda-faq-simulation.html geda-gtkwave_vcd2lxt_mp.html geda-master_attributes_list.html geda-pcb_tips.fr.html geda-gschem_ug.fr.html geda-icarus_vpi_within_vvp.html geda-gschem_mp.html geda-suse_rpm_installation.html geda-gnetlist_mp.html gsoc2008.html geda-installation.html geda-gerbv_pnp_readme.html geda-mcalc_readme.html geda-icarus_xilinx_hints.html geda-ubuntu.html geda-pcb_funding_sow-gui_ideas.html geda-todos.html geda-fbabgapp.html geda-fc4.html geda-pcb_footprint_naming_conventions.html geda-gtkwave_vcd2lxt2_mp.html geda-faq-attribs.html geda-pcb-quick_reference.html geda-xml_file_formats.html geda-icarus_extensions.html geda-pcb_funding_sow.html geda-scm.html geda-gtkwave_lxt2vcd_mp.html geda-faq-pcb.html geda-faq-simulation.fr.html geda-icarus_ieee1364.html geda-gtkwave_vzt2vcd_mp.html geda-grenum_mp.html geda-guile_scripting.html start_es.html geda-bom_readme.html geda-vhdl_netlister_readme.html geda-usage.html geda-gschem_symbol_creation.html geda-vams_netlister_readme.html geda-csygas.html geda-gfdl.html geda-devmacosx.html glue-projects.html geda-wcalc_stdio_mp.html geda-gerbv_mp.html geda-fc2.html geda-gedasuite_installation.html geda-igarus_fpga_lcg.html geda-installed_plugins.html geda-suse_9.3.html geda-faq-gnetlist.html gwave-projects.html geda-faq.fr.html gtkwave-projects.html geda-file_format_spec.html geda-faq-gnetlist.fr.html geda-icarus_anc.html print.css geda-gtkwave_tla2vcd_mp.html gschem-projects.html geda-gtkwave_mvl2lxt_mp.html start.html geda-design_flow_and_hierarchy_roadmap.html geda-start.html geda-tasks.html geda-gsch2pcb_tutorial_releasenotes.html geda-icarus_quick_start.html geda-data_structure_design_discussion.html geda-documentation.html geda-sdb_howto.html gerbv-projects.html geda-circuit_simulation_improvements.html pcb-projects.html geda-gtkwave_tex2vcd_mp.html geda-icarus_glossary.html geda-pcb_mp.html geda-cygwin.html geda-scg.html
+docs_DATA = geda-license.html geda-gtkwave_tex2vcd_mp.html geda-na_howto.html geda-wip-clipboard.html geda-icarus_vpi_mp.html geda-debian.html geda-mailinglists.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-developer.html geda-todos_historical.html geda-icarus_extensions.html libgeda3_object_based_design.html geda-igarus_fpga_lcg.html geda-icarus_xnf.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-gschem_symbol_creation.html geda-gtkwave_vcd2lxt2_mp.html gsoc2010.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-download.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 pcb-roadmap.html geda-example_usbjtag.html geda-suse_10.1.html geda-screenshots.html start_es.html geda-todos.html geda-icarus_opcodes.html geda-gschem_warmup.html geda-links.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-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-spice_polys.html geda-gschem_mp.html geda-tools.html geda-pcb_mp.html gsoc2010_projects.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-gparts_dd.html geda-suse_10.0.html geda-gparts_id.html gwave-projects.html geda-gsch2pcb_tutorial_releasenotes.html geda-gaf.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-pcb_footprint_naming_conventions.html geda-bug_triage_guide.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-gparts_tc.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-howto_report_bugs.html geda-gnetlist_scheme_tutorial.html geda-icarus_xilinx_hints.html geda-transistor_guide.html geda-verilog_netlister_readme.html geda-icarus_vpi_within_vvp.html geda-scg.fr.html geda-faq-gsch2pcb.html geda-tragesym_tutorial.html geda-gedasuite_installation.html geda-gparts_ug.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-gparts_ii.html geda-gaf_building_git_version.html geda-vams_netlister_readme.html geda-icarus_mp.html
EXTRA_DIST = $(docs_DATA)
diff --git a/docs/wiki/best_practices.html b/docs/wiki/best_practices.html
index 06511f8..783e08e 100644
--- a/docs/wiki/best_practices.html
+++ b/docs/wiki/best_practices.html
@@ -12,41 +12,42 @@
<body>
-
-
-<h3><a name="google_summer_of_code_best_practices" id="google_summer_of_code_best_practices">Google Summer of Code Best Practices</a></h3>
+<h3 class="sectionedit1491"><a name="google_summer_of_code_best_practices" id="google_summer_of_code_best_practices">Google Summer of Code Best Practices</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. Here are the things we ask of our students to help make the GSoC experience a success for everybody.
+
+2010 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"> 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 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>
-<li class="level2"><div class="li"> Oftentimes, a different developer on the list can answer a question before the mentor even realizes that heâ??s been asked.</div>
+<li class="level2"><div class="li"> Oftentimes, a different developer on the list can answer a question before the mentor even realizes that he's been asked.</div>
</li>
<li class="level2"><div class="li"> It increases the sense of community for both the GSoC student, and the rest of the gEDA developers. And the gEDA Project is a community of developers, so community building is a benefit to all.</div>
</li>
-<li class="level2"><div class="li"> It provides transparency into whatâ??s going on with the project.</div>
+<li class="level2"><div class="li"> It provides transparency into what's going on with the project.</div>
</li>
</ul>
</li>
-<li class="level1"><div class="li"> Students and mentors should also hold a weekly (or at least a regular) progress review. This review session can take place on <acronym title="Internet Relay Chat">IRC</acronym>, Skype, telephone, or whatever medium is amenable to both. The reason is to make sure that the student is making progress, and isnâ??t falling behind. </div>
+<li class="level1"><div class="li"> Students and mentors should also hold a weekly progress review. This review session can take place on <acronym title="Internet Relay Chat">IRC</acronym>, Skype, telephone, or whatever medium is amenable to both. The reason is to make sure that the student is making progress, and isn't falling behind. </div>
</li>
-<li class="level1"><div class="li"> Students should make at least one code check-in per week. Again, this helps ensure that the student is making progress, and isnâ??t flailing around with a problem he or she canâ??t solve.</div>
+<li class="level1"><div class="li"> Students should make at least one code check-in per week. Again, this helps ensure that the student is making progress, and isn't flailing around with a problem he or she can't solve.</div>
</li>
-<li class="level1"><div class="li"> It would be useful if the mentor could post a summary of the weekly progress review somewhere, either on a project blog, a wiki, or just to geda-dev. This summary doesnâ??t need to be more than a couple of sentences, but it helps give everybody a sense of what is going on. </div>
+<li class="level1"><div class="li"> It would be useful if the mentor could post a summary of the weekly progress review somewhere, either on a project blog, a wiki, or just to geda-dev. This summary doesn't need to be more than a couple of sentences, but it helps give everybody a sense of what is going on. </div>
</li>
<li class="level1"><div class="li"> The gEDA Project holds occasional code sprints, typically on a Saturday. GSoC students should show up and participate at these code sprints, either in person (where possible) or via <acronym title="Internet Relay Chat">IRC</acronym>.</div>
</li>
</ul>
<p>
- Remember – the point behind working on the gEDA Project under the GSoC program is to join a community of developers, hack code, have fun, and make some money while doing it! Following the above practices will help make sure that you become part of the community, which is good for everybody!
+
+Remember â?? the point behind working on the gEDA Project under the GSoC program is to join a community of developers, hack code, have fun, and make some money while doing it! Following the above practices will help make sure that you become part of the community, which is good for everybody!
</p>
</div>
diff --git a/docs/wiki/geda-bom_readme.html b/docs/wiki/geda-bom_readme.html
index 3d1659f..3a2b908 100644
--- a/docs/wiki/geda-bom_readme.html
+++ b/docs/wiki/geda-bom_readme.html
@@ -12,9 +12,7 @@
<body>
-
-
-<h1><a name="bill_of_material_netlister_readme" id="bill_of_material_netlister_readme">Bill of Material netlister README</a></h1>
+<h1 class="sectionedit12"><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.
@@ -44,7 +42,6 @@ have any ideas.
Matt
matt@xxxxxxxxx
-
</pre>
</div>
diff --git a/docs/wiki/geda-bug_triage_guide.html b/docs/wiki/geda-bug_triage_guide.html
new file mode 100644
index 0000000..9ecbb2c
--- /dev/null
+++ b/docs/wiki/geda-bug_triage_guide.html
@@ -0,0 +1,100 @@
+<!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 class="sectionedit1446"><a name="geda_gaf_and_pcb_bug_feature_request_triage_guide" id="geda_gaf_and_pcb_bug_feature_request_triage_guide">gEDA/gaf and PCB Bug/Feature Request Triage Guide</a></h1>
+<div class="level1">
+
+<p>
+
+gEDA/gaf uses <a href="http://launchpad.net"; class="urlextern" title="http://launchpad.net"; rel="nofollow">Launchpad</a> for bug and feature request tracking - the gEDA landing page is <a href="http://bugs.launchpad.net/geda"; class="urlextern" title="http://bugs.launchpad.net/geda"; rel="nofollow"> here</a>.
+</p>
+
+<p>
+Newly filed bugs and feature requests must be triaged periodically by the developers and others close to the project, in order to progress them smoothly through development and avoid them getting stuck.
+</p>
+
+<p>
+Anyone who wants to help triage bugs for the community, please apply to
+join the geda-bugs team for <a href="https://launchpad.net/~geda-bugs/+join"; class="urlextern" title="https://launchpad.net/~geda-bugs/+join"; rel="nofollow">gEDA/gaf</a> and/or <a href="https://launchpad.net/~pcb-bugs/+join"; class="urlextern" title="https://launchpad.net/~pcb-bugs/+join"; rel="nofollow">PCB</a>.
+</p>
+
+</div>
+<!-- EDIT1446 SECTION "gEDA/gaf and PCB Bug/Feature Request Triage Guide" [1-633] -->
+<h2 class="sectionedit1447"><a name="triaging_bugs" id="triaging_bugs">Triaging bugs</a></h2>
+<div class="level2">
+<ol>
+<li class="level1"><div class="li"> Choose a bug from</div>
+<ul>
+<li class="level2"><div class="li"> <a href="https://launchpad.net/geda/+bugs?search=Search&field.status=New"; class="urlextern" title="https://launchpad.net/geda/+bugs?search=Search&field.status=New"; rel="nofollow">https://launchpad.net/geda/+bugs?search=Search&field.status=New</a></div>
+</li>
+<li class="level2"><div class="li"> <a href="https://launchpad.net/pcb/+bugs?search=Search&field.status=New"; class="urlextern" title="https://launchpad.net/pcb/+bugs?search=Search&field.status=New"; rel="nofollow">https://launchpad.net/pcb/+bugs?search=Search&field.status=New</a></div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> Grab â??git HEADâ?? of whichever package the bug is in (if you don't have it already) and try to confirm whether the bug is still present or not.</div>
+</li>
+<li class="level1"><div class="li"> If the bug is still present, move the status from â??Newâ?? to â??Confirmedâ??</div>
+<ul>
+<li class="level2"><div class="li"> If and only if there is a good testcase uploaded that reproduces the bug (or you have created and uploaded one as part of triage), you can move the status to â??Triagedâ??</div>
+</li>
+<li class="level2"><div class="li"> <em><strong>Note:</strong> it is not good form to mark your own bug â??Confirmedâ??.</em></div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> If the bug is absent, make a comment and set the status to one of </div>
+<ul>
+<li class="level2"><div class="li"> â??Invalid,â?? if you are confident that the bug is bogus or misfiled.</div>
+<ul>
+<li class="level3"><div class="li"> If the bug is tagged with â??sf-patchesâ?? shouldn't be closed â??Invalidâ??. If the patch cannot or will not be accepted, mark it as â??WontFixâ??.</div>
+</li>
+</ul>
+</li>
+<li class="level2"><div class="li"> â??Fix Committed,â?? if you believe a fix has been committed in git since the last release;</div>
+</li>
+<li class="level2"><div class="li"> â??Fix Released,â?? if you believe a fix has been committed that has been in a released version; </div>
+</li>
+<li class="level2"><div class="li"> â??Incomplete,â?? if you ask the reporter a question which needs to be answered to properly assess the bug.</div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> If the bug affects you personally, hit the link under the title of the bug that lets you state that.</div>
+</li>
+<li class="level1"><div class="li"> If you want to be emailed when the bug is modified, click â??Subscribeâ?? on the right hand toolbar.</div>
+</li>
+</ol>
+
+</div>
+<!-- EDIT1447 SECTION "Triaging bugs" [634-2091] -->
+<h2 class="sectionedit1448"><a name="triaging_feature_requests" id="triaging_feature_requests">Triaging Feature Requests</a></h2>
+<div class="level2">
+<ol>
+<li class="level1"><div class="li"> Choose a feature request from</div>
+<ul>
+<li class="level2"><div class="li"> <a href="https://launchpad.net/geda/+bugs?search=Search&field.status=New"; class="urlextern" title="https://launchpad.net/geda/+bugs?search=Search&field.status=New"; rel="nofollow">https://launchpad.net/geda/+bugs?search=Search&field.status=New</a></div>
+</li>
+<li class="level2"><div class="li"> <a href="https://launchpad.net/pcb/+bugs?search=Search&field.status=New"; class="urlextern" title="https://launchpad.net/pcb/+bugs?search=Search&field.status=New"; rel="nofollow">https://launchpad.net/pcb/+bugs?search=Search&field.status=New</a></div>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> If it's not already set, set the Importance to â??Wishlistâ??</div>
+</li>
+<li class="level1"><div class="li"> If you agree with the feature request, select the â??Bug affects meâ?? option. This will allow us to track the popularity of a request.</div>
+</li>
+<li class="level1"><div class="li"> A developer who is sufficiently familiar with the design issues will move the Status from â??Newâ?? to either â??Confirmedâ??, â??WontFixâ?? or â??Opinionâ??.</div>
+</li>
+</ol>
+
+</div>
+<!-- EDIT1448 SECTION "Triaging Feature Requests" [2092-] --></body>
+</html>
diff --git a/docs/wiki/geda-circuit_simulation_improvements.html b/docs/wiki/geda-circuit_simulation_improvements.html
index f14db5f..745f0cd 100644
--- a/docs/wiki/geda-circuit_simulation_improvements.html
+++ b/docs/wiki/geda-circuit_simulation_improvements.html
@@ -11,46 +11,18 @@
</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>
+<h1 class="sectionedit14"><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>
+<!-- EDIT14 SECTION "Circuit simulation improvements in gschem" [1-58] -->
+<h2 class="sectionedit15"><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:
+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>
@@ -62,11 +34,13 @@ Using gschem as a circuit simulation (ngspice or gnucap) frontend is not easy fo
</ul>
<p>
- The simulation runs and the postprocessing may be in an external programm that is triggered by IPC.
+
+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
+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>
@@ -78,38 +52,43 @@ There are some graphical frontends around but they canâ??t solve all of the abov
</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.
+
+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>
+<!-- EDIT15 SECTION "Rationale" [59-862] -->
+<h2 class="sectionedit16"><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.
+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>
+<!-- EDIT16 SECTION "Draft" [863-1012] -->
+<h3 class="sectionedit17"><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.
+<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.
+<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>
+<!-- EDIT17 SECTION "The probes" [1013-1888] -->
+<h3 class="sectionedit18"><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)".
+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>
@@ -121,8 +100,8 @@ A modified edit attribute (ee) command could take care of voltage and current so
</p>
</div>
-<!-- SECTION "Voltage and current sources" [1889-2487] -->
-<h3><a name="the_simulations" id="the_simulations">The simulations</a></h3>
+<!-- EDIT18 SECTION "Voltage and current sources" [1889-2487] -->
+<h3 class="sectionedit19"><a name="the_simulations" id="the_simulations">The simulations</a></h3>
<div class="level3">
<p>
@@ -130,20 +109,20 @@ 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.
+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 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 class="level1"><div class="li"> simulation parameters (global parameters, temperature, â?¦)</div>
</li>
</ul>
-<pre class="code">
-v 20061020 1
+<pre class="code">v 20061020 1
C 41500 49200 1 0 0 spice-directive-1.sym
{
device=spice_simulation_block
@@ -157,8 +136,7 @@ option_TNOM=100 Deg
option_ABSTOL=1e-3
global_param1=???
global_param2=???
-}
-</pre>
+}</pre>
<p>
There may be many simulation objects inside a single schematic.
@@ -175,34 +153,38 @@ To store additional libraries we can either use an include card or using a â??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.
+
+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>
+<!-- EDIT19 SECTION "The simulations" [2488-3735] -->
+<h3 class="sectionedit20"><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.
+
+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 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 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)
+
+When creating that dialog all simulation objects are collected into the simulation list (listview with enable/disable checkbutton)
</p>
<p>
@@ -210,8 +192,8 @@ When changing the settings the attributes of the assosiated simulation object ar
</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>
+<!-- EDIT20 SECTION "Creating a simulation dialog inside gschem" [3736-4567] -->
+<h3 class="sectionedit21"><a name="the_option_dialog" id="the_option_dialog">The option dialog</a></h3>
<div class="level3">
<p>
@@ -219,7 +201,7 @@ 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:
+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>
@@ -231,8 +213,8 @@ The probes that we have placed can be used to tell the simulator the variables t
</ul>
</div>
-<!-- SECTION "The option dialog" [4568-5135] -->
-<h3><a name="invoking_the_simulation" id="invoking_the_simulation">Invoking the simulation</a></h3>
+<!-- EDIT21 SECTION "The option dialog" [4568-5135] -->
+<h3 class="sectionedit22"><a name="invoking_the_simulation" id="invoking_the_simulation">Invoking the simulation</a></h3>
<div class="level3">
<p>
@@ -245,25 +227,25 @@ The simulation button of the dialog should lead to the following actions:
</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 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.
+
+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>
+<!-- EDIT22 SECTION "Invoking the simulation" [5136-5581] -->
+<h2 class="sectionedit23"><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>
+<!-- EDIT23 SECTION "Appendix" [5582-5602] -->
+<h3 class="sectionedit24"><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
+<pre class="code">v 20061020 1
P 0 0 200 200 1 0 0
{
T 100 0 5 10 0 1 0 0 1
@@ -285,15 +267,13 @@ 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>
+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>
+<!-- EDIT24 SECTION "A current probe symbol (draft)" [5603-6092] -->
+<h3 class="sectionedit25"><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
+<pre class="code">v 20061020 1
P 0 200 150 200 1 0 0
{
T -150 50 5 10 0 1 0 0 1
@@ -325,15 +305,13 @@ 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>
+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>
+<!-- EDIT25 SECTION "A voltage probe symbol (draft)" [6093-6761] -->
+<h3 class="sectionedit26"><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
+<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
@@ -374,9 +352,8 @@ 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>
+L 100 700 100 800 3 0 0 0 -1 -1</pre>
</div>
-<!-- SECTION "Another current probe symbol used by Kurt Peters" [6762-] --></body>
+<!-- EDIT26 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
index c456378..16dd95a 100644
--- a/docs/wiki/geda-covered_mp.html
+++ b/docs/wiki/geda-covered_mp.html
@@ -12,9 +12,7 @@
<body>
-
-
-<h1><a name="covered_man-page" id="covered_man-page">covered man-page</a></h1>
+<h1 class="sectionedit28"><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)
diff --git a/docs/wiki/geda-csygas.html b/docs/wiki/geda-csygas.html
index 8433488..c40c2ed 100644
--- a/docs/wiki/geda-csygas.html
+++ b/docs/wiki/geda-csygas.html
@@ -11,90 +11,31 @@
</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>
+<h1 class="sectionedit36"><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
+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.
+
+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>.
+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., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA. <sup><a href="#fn__1" name="fnt__1" id="fnt__1" class="fn_top">1)</a></sup>.
</p>
</div>
-<!-- SECTION "Circuit Simulation using gEDA and SPICE - HOWTO" [1-1357] -->
-<h2><a name="introduction" id="introduction">Introduction</a></h2>
+<!-- EDIT36 SECTION "Circuit Simulation using gEDA and SPICE - HOWTO" [1-1359] -->
+<h2 class="sectionedit37"><a name="introduction" id="introduction">Introduction</a></h2>
<div class="level2">
<p>
@@ -102,12 +43,12 @@ Modern engineering is a computer-intensive discipline. Like professionals in ot
</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>.
+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>
+<!-- EDIT37 SECTION "Introduction" [1360-3625] -->
+<h3 class="sectionedit38"><a name="target_audience_for_this_howto" id="target_audience_for_this_howto">Target audience for this HOWTO</a></h3>
<div class="level3">
<p>
@@ -128,44 +69,46 @@ This HOWTO is not a tutorial about circuit design or SPICE simulation. Rather, i
</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 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 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>
+<!-- EDIT38 SECTION "Target audience for this HOWTO" [3626-4973] -->
+<h3 class="sectionedit39"><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.
+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>
+<!-- EDIT39 SECTION "Acknowledgements" [4974-6528] -->
+<h3 class="sectionedit40"><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.
+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).
+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>
+<!-- EDIT40 SECTION "The big picture: the design flow in gEDA" [6529-7625] -->
+<h3 class="sectionedit41"><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 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>
@@ -176,11 +119,12 @@ Conceptually, SPICE simulation in gEDA proceeds via the following steps:
</ol>
<p>
- These steps are illustrated by the blue boxes in the flow diagram above.
+
+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:
+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>
@@ -190,19 +134,20 @@ To create a SPICE netlist, the netlister (<strong>gnetlist</strong>) iterates th
</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>.
+
+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>
+<!-- EDIT41 SECTION "Overview of SPICE usage with gEDA" [7626-8969] -->
+<h3 class="sectionedit42"><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 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>
@@ -218,17 +163,18 @@ The detailed steps required to design and simulate a circuit using gEDA look lik
</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 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.
+
+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>
+<!-- EDIT42 SECTION "Detailed design/simulation flow summary" [8970-10149] -->
+<h2 class="sectionedit43"><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>
@@ -236,8 +182,8 @@ When you create schematic symbols for inclusion into your schematic, you must ma
</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>
+<!-- EDIT43 SECTION "Preliminary work: preparing your symbols and SPICE files" [10150-10528] -->
+<h3 class="sectionedit44"><a name="configuring_your_symbols" id="configuring_your_symbols">Configuring your symbols</a></h3>
<div class="level3">
</div>
@@ -249,14 +195,15 @@ When you create schematic symbols for inclusion into your schematic, you must ma
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 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 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.
+
+Both of these attributes are attached to the symbol when the symbol is created.
</p>
<p>
@@ -264,11 +211,11 @@ Each symbol has a <strong><code>device</code></strong> attribute attached to it
</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.
+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.
+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>
@@ -277,16 +224,16 @@ If a symbol is not native (i.e. the netlister doesnâ??t recognize it as a built-
<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.
+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.
+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>
+<!-- EDIT44 SECTION "Configuring your symbols" [10529-13605] -->
+<h3 class="sectionedit45"><a name="configuring_your_spice_files" id="configuring_your_spice_files">Configuring your SPICE files</a></h3>
<div class="level3">
<p>
@@ -295,24 +242,24 @@ Files holding complicated SPICE models or other SPICE code may be incorporated i
<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 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>
+<!-- EDIT45 SECTION "Configuring your SPICE files" [13606-14752] -->
+<h2 class="sectionedit46"><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.
+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>
+<!-- EDIT46 SECTION "Creating your circuit: schematic capture" [14753-15476] -->
+<h3 class="sectionedit47"><a name="gschem_attributes_for_spice_netlisting" id="gschem_attributes_for_spice_netlisting">Gschem attributes for spice netlisting</a></h3>
<div class="level3">
<p>
@@ -320,8 +267,8 @@ There are several ways that spice attributes may be associated with a component
</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>
+<!-- EDIT47 SECTION "Gschem attributes for spice netlisting" [15477-15758] -->
+<h3 class="sectionedit48"><a name="component_attributes_and_meanings" id="component_attributes_and_meanings">Component attributes and meanings</a></h3>
<div class="level3">
<p>
@@ -343,8 +290,8 @@ The following attributes are meaningful for SPICE netlisting, and may be attache
</ul>
</div>
-<!-- SECTION "Component attributes and meanings" [15757-17116] -->
-<h3><a name="refdes_conventions" id="refdes_conventions">refdes conventions</a></h3>
+<!-- EDIT48 SECTION "Component attributes and meanings" [15759-17118] -->
+<h3 class="sectionedit49"><a name="refdes_conventions" id="refdes_conventions">refdes conventions</a></h3>
<div class="level3">
<p>
@@ -356,8 +303,8 @@ Note that the first letter of the <strong><code>refdes</code></strong> must corr
</p>
</div>
-<!-- SECTION "refdes conventions" [17117-17611] -->
-<h3><a name="passives" id="passives">Passives</a></h3>
+<!-- EDIT49 SECTION "refdes conventions" [17119-17613] -->
+<h3 class="sectionedit50"><a name="passives" id="passives">Passives</a></h3>
<div class="level3">
</div>
@@ -389,7 +336,8 @@ The most basic components which one encounters in SPICE are passive components l
</ul>
<p>
- SPICE line generated: <strong><code>R2 0 4 220</code></strong>
+
+SPICE line generated: <strong><code>R2 0 4 220</code></strong>
</p>
<p>
@@ -408,16 +356,17 @@ The most basic components which one encounters in SPICE are passive components l
</ul>
<p>
- SPICE line generated: <strong><code>C22 4 23 1UF</code></strong>
+
+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>
+<!-- EDIT50 SECTION "Passives" [17614-18709] -->
+<h3 class="sectionedit51"><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:
+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>
@@ -429,7 +378,8 @@ Oftentimes, passive components have additional attributes attached to them for s
</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.
+
+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>
@@ -446,12 +396,13 @@ Oftentimes, passive components have additional attributes attached to them for s
</ul>
<p>
- SPICE line generated: <strong><code>R2 0 4 220 TC=0.001,0.015</code></strong>
+
+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>
+<!-- EDIT51 SECTION "Passives with additional attributes" [18710-19795] -->
+<h3 class="sectionedit52"><a name="passives_for_semiconductor_design" id="passives_for_semiconductor_design">Passives for semiconductor design</a></h3>
<div class="level3">
<p>
@@ -467,7 +418,8 @@ The values for resistors and capacitors are often given as dimensions in an ASIC
</ul>
<p>
- The technology library must be included with an <strong><code>.include</code></strong> line in the SPICE input file.
+
+The technology library must be included with an <strong><code>.include</code></strong> line in the SPICE input file.
</p>
</div>
@@ -486,7 +438,8 @@ The values for resistors and capacitors are often given as dimensions in an ASIC
</ul>
<p>
- SPICE line generated: <strong><code>R6 0 5 rpoly w=3u l=100u</code></strong>
+
+SPICE line generated: <strong><code>R6 0 5 rpoly w=3u l=100u</code></strong>
</p>
</div>
@@ -499,12 +452,13 @@ The values for resistors and capacitors are often given as dimensions in an ASIC
</ul>
<p>
- This should be part of the technology library from your ASIC vendor.
+
+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>
+<!-- EDIT52 SECTION "Passives for semiconductor design" [19796-20722] -->
+<h3 class="sectionedit53"><a name="transistors_and_diodes" id="transistors_and_diodes">Transistors and diodes</a></h3>
<div class="level3">
<p>
@@ -526,7 +480,7 @@ To incorporate a one line string of SPICE parameters into the netlist, the follo
</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 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>
@@ -544,7 +498,8 @@ To incorporate a one line string of SPICE parameters into the netlist, the follo
</ul>
<p>
- SPICE lines generated: <strong><code>D5 2 6 1N1004 MODEL 1N1004 D (IS=0.5UA RS=6 BV=5.20)</code></strong>
+
+SPICE lines generated: <strong><code>D5 2 6 1N1004 MODEL 1N1004 D (IS=0.5UA RS=6 BV=5.20)</code></strong>
</p>
</div>
@@ -567,12 +522,13 @@ To incorporate a file-full of SPICE parameters into the netlist, the following a
</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.
+
+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>
+<!-- EDIT53 SECTION "Transistors and diodes" [20723-23423] -->
+<h3 class="sectionedit54"><a name="actives_--_integrated_circuits" id="actives_--_integrated_circuits">Actives -- integrated circuits</a></h3>
<div class="level3">
<p>
@@ -594,20 +550,20 @@ To incorporate a one line string of SPICE parameters into the netlist, the follo
</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 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>
+<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 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>
@@ -618,19 +574,20 @@ To incorporate a file-full of SPICE parameters into the netlist, the following a
</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.
+
+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>
+<!-- EDIT54 SECTION "Actives -- integrated circuits" [23424-25767] -->
+<h3 class="sectionedit55"><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 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>
@@ -643,8 +600,8 @@ There are two independent sources: voltage sources and current sources. For inco
</ol>
</div>
-<!-- SECTION "Independent sources" [25766-26339] -->
-<h3><a name="dependent_sources" id="dependent_sources">Dependent sources</a></h3>
+<!-- EDIT55 SECTION "Independent sources" [25768-26341] -->
+<h3 class="sectionedit56"><a name="dependent_sources" id="dependent_sources">Dependent sources</a></h3>
<div class="level3">
<p>
@@ -656,8 +613,8 @@ This section remains TBD.
</p>
</div>
-<!-- SECTION "Dependent sources" [26340-26429] -->
-<h3><a name="spice_components" id="spice_components">SPICE components</a></h3>
+<!-- EDIT56 SECTION "Dependent sources" [26342-26431] -->
+<h3 class="sectionedit57"><a name="spice_components" id="spice_components">SPICE components</a></h3>
<div class="level3">
</div>
@@ -666,7 +623,8 @@ This section remains TBD.
<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:
+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>
@@ -674,7 +632,7 @@ In certain situations, you may wish to embed a spice model block directly into y
<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 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>
@@ -695,7 +653,7 @@ In certain situations, you may wish to embed a spice model block directly into y
<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 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>
@@ -718,7 +676,7 @@ In certain situations, you may wish to embed a spice model block directly into y
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 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>
@@ -748,10 +706,11 @@ Placing a SPICE directive block into your schematic creates an arbitrary block o
</ul>
<p>
- To place a SPICE directive on your schematic, do:
+
+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 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>
@@ -764,12 +723,12 @@ Placing a SPICE directive block into your schematic creates an arbitrary block o
</ol>
</div>
-<!-- SECTION "SPICE components" [26430-28839] -->
-<h3><a name="handling_hierarchical_models" id="handling_hierarchical_models">Handling hierarchical models</a></h3>
+<!-- EDIT57 SECTION "SPICE components" [26432-28841] -->
+<h3 class="sectionedit58"><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.
+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>
@@ -779,18 +738,18 @@ Since this kind of task is very common in SPICE simulation, <strong>gnet-spice-s
<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>
+<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>
+<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>
@@ -800,18 +759,18 @@ Since this kind of task is very common in SPICE simulation, <strong>gnet-spice-s
</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 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>
+<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>
@@ -824,25 +783,27 @@ Since this kind of task is very common in SPICE simulation, <strong>gnet-spice-s
</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.
+
+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>
+<!-- EDIT58 SECTION "Handling hierarchical models" [28842-33382] -->
+<h2 class="sectionedit59"><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>
+<!-- EDIT59 SECTION "SPICE netlist generation" [33383-33419] -->
+<h3 class="sectionedit60"><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.
+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:
+<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
@@ -856,8 +817,8 @@ Once the schematic is captured, a SPICE netlist can be generated running gEDAâ??
-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>
+<!-- EDIT60 SECTION "Using gnetlist" [33420-34980] -->
+<h3 class="sectionedit61"><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>
@@ -867,18 +828,18 @@ Creating a netlist from a schematic is easy. To generate a SPICE netlist, just d
<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>
+<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>
+<!-- EDIT61 SECTION "Creating the netlist using gnetlist and spice-sdb" [34981-35774] -->
+<h3 class="sectionedit62"><a name="common_netlisting_problems" id="common_netlisting_problems">Common netlisting problems</a></h3>
<div class="level3">
<p>
@@ -886,20 +847,21 @@ The following list attempts to catalog common problems with the netlist and the
</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>
+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>
+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.
+
+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>
+<!-- EDIT62 SECTION "Common netlisting problems" [35775-36780] -->
+<h2 class="sectionedit63"><a name="spice_simulation" id="spice_simulation">SPICE simulation</a></h2>
<div class="level2">
<p>
@@ -908,27 +870,28 @@ There are several options for doing SPICE simulations under GNU/Linux; I will hi
<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 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.
+
+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>
+<!-- EDIT63 SECTION "SPICE simulation" [36781-38433] -->
+<h3 class="sectionedit64"><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.
+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.
+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>
@@ -957,7 +920,7 @@ To install and configure LTSpice, do the following:
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 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>
@@ -966,32 +929,33 @@ LTSpice can read a file holding a gEDA SPICE netlist. I have had success doing L
<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/>
+<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 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 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.
+
+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>
+<!-- EDIT64 SECTION "LTSpice" [38434-41373] -->
+<h3 class="sectionedit65"><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.
+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>
@@ -1000,7 +964,7 @@ Ngspice was started at the University of Rome â??La Sapienzaâ?? by Paolo Nenzi a
<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.
+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>
@@ -1018,7 +982,8 @@ Get the latest distribution from: <a href="http://sourceforge.net/projetcs/ngspi
<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:
+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>
@@ -1037,26 +1002,30 @@ At this point you are in the top level directory of ngspice. Read the usual file
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 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 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 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:
+
+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:
+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:
+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>
@@ -1076,7 +1045,8 @@ At this point, you should be able to use ngspice. You can test your installation
<div class="level4">
<p>
-Running ngspice is very simple. Just issue the command:
+Running ngspice is very simple. Just issue the command:
+
</p>
<pre class="code">user@host:~$ ngspice filename.net</pre>
@@ -1085,12 +1055,13 @@ at the unix command prompt, and ngspice will load the SPICE netlist called <stro
</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:
+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).
+(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>
@@ -1098,8 +1069,8 @@ A better way to read in the <strong><code>spice2poly</code></strong> codemodel i
</p>
</div>
-<!-- SECTION "Ngspice" [41372-48076] -->
-<h3><a name="tclspice" id="tclspice">Tclspice</a></h3>
+<!-- EDIT65 SECTION "Ngspice" [41374-48078] -->
+<h3 class="sectionedit66"><a name="tclspice" id="tclspice">Tclspice</a></h3>
<div class="level3">
<p>
@@ -1112,7 +1083,7 @@ While the main branch of ngspice development hibernated in 2002, some friendly p
<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.
+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>
@@ -1130,11 +1101,13 @@ Before building tclspice, you need to have the following packages already instal
</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).
+
+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:
+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)
@@ -1142,13 +1115,14 @@ user@host:~sources/<tld>$ ./configure --enable-xspice --prefix=/usr/local/
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:
+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.
+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>
@@ -1157,7 +1131,8 @@ to install your packages. Now you will be ready to write TCL scripts which incor
<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:
+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
@@ -1169,7 +1144,7 @@ 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>
+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>
@@ -1182,7 +1157,8 @@ A major problem with tclspice (which was inherited from ngspice) is that it leak
</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:
+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
@@ -1203,7 +1179,7 @@ while {1} {
}</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â??!
+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>
@@ -1211,8 +1187,8 @@ This method of waiting a specific amount of time for the child process is prefer
</p>
</div>
-<!-- SECTION "Tclspice" [48077-55608] -->
-<h1><a name="appendix_a" id="appendix_a">Appendix A</a></h1>
+<!-- EDIT66 SECTION "Tclspice" [48079-55610] -->
+<h1 class="sectionedit67"><a name="appendix_a" id="appendix_a">Appendix A</a></h1>
<div class="level1">
<p>
@@ -1224,103 +1200,117 @@ Presented in table 1 are the devices and associated attributes used with spice-s
</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.
+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>
+<div class="table sectionedit68"><table class="inline">
+ <tr class="row0">
+ <th class="col0">device</th><th class="col1">refdes</th><th class="col2">value</th><th class="col3">model</th><th class="col4">file</th><th class="col5">model-name</th><th class="col6">type</th><th class="col7">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 class="row1">
+ <td class="col0">RESISTOR</td><td class="col1 centeralign"> R? </td><td class="col2 centeralign"> (4) </td><td class="col3 centeralign"> (2) </td><td class="col4 centeralign"> - </td><td class="col5 centeralign"> Name of model </td><td class="col6 centeralign"> - </td><td class="col7 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 class="row2">
+ <td class="col0">CAPACITOR</td><td class="col1 centeralign"> C? </td><td class="col2 centeralign"> (4) </td><td class="col3 centeralign"> (3) </td><td class="col4 centeralign"> - </td><td class="col5 centeralign"> Name of model </td><td class="col6 centeralign"> - </td><td class="col7 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 class="row3">
+ <td class="col0">POLARIZED_CAPACITOR</td><td class="col1 centeralign"> C? </td><td class="col2 centeralign"> (4) </td><td class="col3 centeralign"> (3) </td><td class="col4 centeralign"> - </td><td class="col5 centeralign"> Name of model </td><td class="col6 centeralign"> - </td><td class="col7 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 class="row4">
+ <td class="col0">INDUCTOR</td><td class="col1 centeralign"> L? </td><td class="col2 centeralign"> (4) </td><td class="col3 centeralign"> (3) </td><td class="col4 centeralign"> - </td><td class="col5 centeralign"> Name of model </td><td class="col6 centeralign"> - </td><td class="col7 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 class="row5">
+ <td class="col0">SPICE-ccvs</td><td class="col1 centeralign"> H? </td><td class="col2 centeralign"> (5) </td><td class="col3 centeralign"> - </td><td class="col4 centeralign"> - </td><td class="col5 centeralign"> - </td><td class="col6 centeralign"> - </td><td class="col7 leftalign"> </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 class="row6">
+ <td class="col0">SPICE-cccs</td><td class="col1 centeralign"> F? </td><td class="col2 centeralign"> (5) </td><td class="col3 centeralign"> - </td><td class="col4 centeralign"> - </td><td class="col5 centeralign"> - </td><td class="col6 centeralign"> - </td><td class="col7 leftalign"> </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 class="row7">
+ <td class="col0">SPICE-vscs</td><td class="col1 centeralign"> E? </td><td class="col2 centeralign"> (5) </td><td class="col3 centeralign"> - </td><td class="col4 centeralign"> - </td><td class="col5 centeralign"> - </td><td class="col6 centeralign"> - </td><td class="col7 leftalign"> </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 class="row8">
+ <td class="col0">SPICE-vccs</td><td class="col1 centeralign"> G? </td><td class="col2 centeralign"> (5) </td><td class="col3 centeralign"> - </td><td class="col4 centeralign"> - </td><td class="col5 centeralign"> - </td><td class="col6 centeralign"> - </td><td class="col7 leftalign"> </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 class="row9">
+ <td class="col0">SPICE-nullor</td><td class="col1 centeralign"> E? </td><td class="col2 centeralign"> (5) </td><td class="col3 centeralign"> - </td><td class="col4 centeralign"> - </td><td class="col5 centeralign"> - </td><td class="col6 centeralign"> - </td><td class="col7 leftalign"> </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 class="row10">
+ <td class="col0">DIODE</td><td class="col1 centeralign"> D? </td><td class="col2 centeralign"> Part number </td><td class="col3 centeralign"> One line SPICE model </td><td class="col4 centeralign"> Model file name </td><td class="col5 centeralign"> Name of model </td><td class="col6 centeralign"> - </td><td class="col7 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 class="row11">
+ <td class="col0">PMOS_TRANSISTOR</td><td class="col1 centeralign"> M? </td><td class="col2 centeralign"> Part number </td><td class="col3 centeralign"> One line SPICE model </td><td class="col4 centeralign"> Model file name </td><td class="col5 centeralign"> Name of model </td><td class="col6 centeralign"> - </td><td class="col7 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 class="row12">
+ <td class="col0">NMOS_TRANSISTOR</td><td class="col1 centeralign"> M? </td><td class="col2 centeralign"> Part number </td><td class="col3 centeralign"> One line SPICE model </td><td class="col4 centeralign"> Model file name </td><td class="col5 centeralign"> Name of model </td><td class="col6 centeralign"> - </td><td class="col7 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 class="row13">
+ <td class="col0">PNP_TRANSISTOR</td><td class="col1 centeralign"> Q? </td><td class="col2 centeralign"> Part number </td><td class="col3 centeralign"> One line SPICE model </td><td class="col4 centeralign"> Model file name </td><td class="col5 centeralign"> Name of model </td><td class="col6 centeralign"> - </td><td class="col7 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 class="row14">
+ <td class="col0">NPN_TRANSISTOR</td><td class="col1 centeralign"> Q? </td><td class="col2 centeralign"> Part number </td><td class="col3 centeralign"> One line SPICE model </td><td class="col4 centeralign"> Model file name </td><td class="col5 centeralign"> Name of model </td><td class="col6 centeralign"> - </td><td class="col7 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 class="row15">
+ <td class="col0">PFET_TRANSISTOR</td><td class="col1 centeralign"> J? </td><td class="col2 centeralign"> Part number </td><td class="col3 centeralign"> One line SPICE model </td><td class="col4 centeralign"> Model file name </td><td class="col5 centeralign"> Name of model </td><td class="col6 centeralign"> - </td><td class="col7 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 class="row16">
+ <td class="col0">NFET_TRANSISTOR</td><td class="col1 centeralign"> J? </td><td class="col2 centeralign"> Part number </td><td class="col3 centeralign"> One line SPICE model </td><td class="col4 centeralign"> Model file name </td><td class="col5 centeralign"> Name of model </td><td class="col6 centeralign"> - </td><td class="col7 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 class="row17">
+ <td class="col0">MESFET_TRANSISTOR</td><td class="col1 centeralign"> B? </td><td class="col2 centeralign"> Part number </td><td class="col3 centeralign"> One line SPICE model </td><td class="col4 centeralign"> Model file name </td><td class="col5 centeralign"> Name of model </td><td class="col6 centeralign"> - </td><td class="col7 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 class="row18">
+ <td class="col0">IC</td><td class="col1 centeralign"> U? </td><td class="col2 centeralign"> Part number </td><td class="col3 leftalign"> </td><td class="col4 centeralign"> .model file name </td><td class="col5 centeralign"> Name of model </td><td class="col6 centeralign"> - </td><td class="col7 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 class="row19">
+ <td class="col0">IC</td><td class="col1 centeralign"> X? </td><td class="col2 centeralign"> Part number </td><td class="col3 leftalign"> </td><td class="col4 centeralign"> .subckt file name </td><td class="col5 centeralign"> Name of .subckt </td><td class="col6 centeralign"> - </td><td class="col7 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 class="row20">
+ <td class="col0">model</td><td class="col1 centeralign"> A? </td><td class="col2 centeralign"> - </td><td class="col3 centeralign"> One line SPICE model </td><td class="col4 centeralign"> .model file name </td><td class="col5 centeralign"> (9) </td><td class="col6 centeralign"> (10) </td><td class="col7 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 class="row21">
+ <td class="col0">include</td><td class="col1 centeralign"> A? </td><td class="col2 centeralign"> - </td><td class="col3 centeralign"> - </td><td class="col4 centeralign"> .include file name </td><td class="col5 centeralign"> - </td><td class="col6 centeralign"> - </td><td class="col7 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 class="row22">
+ <td class="col0">options</td><td class="col1 centeralign"> A? </td><td class="col2 centeralign"> (8) </td><td class="col3 centeralign"> - </td><td class="col4 centeralign"> - </td><td class="col5 centeralign"> - </td><td class="col6 centeralign"> - </td><td class="col7 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 class="row23">
+ <td class="col0">directive</td><td class="col1 centeralign"> A? </td><td class="col2 centeralign"> (1) </td><td class="col3 centeralign"> - </td><td class="col4 centeralign"> - </td><td class="col5 centeralign"> - </td><td class="col6 centeralign"> - </td><td class="col7 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 class="row24">
+ <td class="col0">VOLTAGE_SOURCE</td><td class="col1 centeralign"> V? </td><td class="col2 centeralign"> (6) </td><td class="col3 centeralign"> - </td><td class="col4 centeralign"> - </td><td class="col5 centeralign"> - </td><td class="col6 centeralign"> - </td><td class="col7 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 class="row25">
+ <td class="col0">CURRENT_SOURCE</td><td class="col1 centeralign"> I? </td><td class="col2 centeralign"> (7) </td><td class="col3 centeralign"> - </td><td class="col4 centeralign"> - </td><td class="col5 centeralign"> - </td><td class="col6 centeralign"> - </td><td class="col7 centeralign"> Independent current source </td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT68 TABLE [56483-58746] -->
<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/>
+
+(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>
@@ -1329,8 +1319,8 @@ When dealing with simple actives (diodes, transistors) having SPICE models held
</p>
</div>
-<!-- SECTION "Appendix A" [55609-60280] -->
-<h1><a name="appendix_b" id="appendix_b">Appendix B</a></h1>
+<!-- EDIT67 SECTION "Appendix A" [55611-60282] -->
+<h1 class="sectionedit69"><a name="appendix_b" id="appendix_b">Appendix B</a></h1>
<div class="level1">
<p>
@@ -1338,57 +1328,60 @@ When dealing with simple actives (diodes, transistors) having SPICE models held
</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:
+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>
+<div class="table sectionedit70"><table class="inline">
+ <tr class="row0">
+ <th class="col0 centeralign"> Component </th><th class="col1 centeralign"> â??typeâ?? </th><th class="col2 centeralign"> Comment </th>
</tr>
- <tr>
- <td class="centeralign"> RESISTOR </td><td class="centeralign"> RES </td><td class="rightalign"> </td>
+ <tr class="row1">
+ <td class="col0 centeralign"> RESISTOR </td><td class="col1 centeralign"> RES </td><td class="col2 leftalign"> </td>
</tr>
- <tr>
- <td class="centeralign"> CAPACITOR </td><td class="centeralign"> CAP </td><td class="rightalign"> </td>
+ <tr class="row2">
+ <td class="col0 centeralign"> CAPACITOR </td><td class="col1 centeralign"> CAP </td><td class="col2 leftalign"> </td>
</tr>
- <tr>
- <td class="centeralign"> POLARIZED_CAPACITOR </td><td class="centeralign"> CAP </td><td class="rightalign"> </td>
+ <tr class="row3">
+ <td class="col0 centeralign"> POLARIZED_CAPACITOR </td><td class="col1 centeralign"> CAP </td><td class="col2 leftalign"> </td>
</tr>
- <tr>
- <td class="centeralign"> INDUCTOR </td><td class="centeralign"> IND </td><td class="rightalign"> </td>
+ <tr class="row4">
+ <td class="col0 centeralign"> INDUCTOR </td><td class="col1 centeralign"> IND </td><td class="col2 leftalign"> </td>
</tr>
- <tr>
- <td class="centeralign"> DIODE </td><td class="centeralign"> D </td><td class="rightalign"> </td>
+ <tr class="row5">
+ <td class="col0 centeralign"> DIODE </td><td class="col1 centeralign"> D </td><td class="col2 leftalign"> </td>
</tr>
- <tr>
- <td class="centeralign"> PMOS_TRANSISTOR </td><td class="centeralign"> PMOS </td><td class="rightalign"> </td>
+ <tr class="row6">
+ <td class="col0 centeralign"> PMOS_TRANSISTOR </td><td class="col1 centeralign"> PMOS </td><td class="col2 leftalign"> </td>
</tr>
- <tr>
- <td class="centeralign"> NMOS_TRANSISTOR </td><td class="centeralign"> NMOS </td><td class="rightalign"> </td>
+ <tr class="row7">
+ <td class="col0 centeralign"> NMOS_TRANSISTOR </td><td class="col1 centeralign"> NMOS </td><td class="col2 leftalign"> </td>
</tr>
- <tr>
- <td class="centeralign"> PNP_TRANSISTOR </td><td class="centeralign"> PNP </td><td class="rightalign"> </td>
+ <tr class="row8">
+ <td class="col0 centeralign"> PNP_TRANSISTOR </td><td class="col1 centeralign"> PNP </td><td class="col2 leftalign"> </td>
</tr>
- <tr>
- <td class="centeralign"> NPN_TRANSISTOR </td><td class="centeralign"> NPN </td><td class="rightalign"> </td>
+ <tr class="row9">
+ <td class="col0 centeralign"> NPN_TRANSISTOR </td><td class="col1 centeralign"> NPN </td><td class="col2 leftalign"> </td>
</tr>
- <tr>
- <td class="centeralign"> PFET_TRANSISTOR </td><td class="centeralign"> PJF </td><td class="rightalign"> </td>
+ <tr class="row10">
+ <td class="col0 centeralign"> PFET_TRANSISTOR </td><td class="col1 centeralign"> PJF </td><td class="col2 leftalign"> </td>
</tr>
- <tr>
- <td class="centeralign"> NFET_TRANSISTOR </td><td class="centeralign"> NJF </td><td class="rightalign"> </td>
+ <tr class="row11">
+ <td class="col0 centeralign"> NFET_TRANSISTOR </td><td class="col1 centeralign"> NJF </td><td class="col2 leftalign"> </td>
</tr>
- <tr>
- <td class="centeralign"> MESFET_TRANSISTOR </td><td class="centeralign"> - </td><td class="rightalign"> </td>
+ <tr class="row12">
+ <td class="col0 centeralign"> MESFET_TRANSISTOR </td><td class="col1 centeralign"> - </td><td class="col2 leftalign"> </td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT70 TABLE [60535-60967] -->
<p>
- Table 2: Valid â??typeâ?? attributes for components.
+
+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>
+<!-- EDIT69 SECTION "Appendix B" [60283-] --><div class="footnotes">
+<div class="fn"><sup><a href="#fnt__1" id="fn__1" name="fn__1" class="fn_bot">1)</a></sup>
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>
diff --git a/docs/wiki/geda-cygwin.html b/docs/wiki/geda-cygwin.html
index 60d2f33..b223376 100644
--- a/docs/wiki/geda-cygwin.html
+++ b/docs/wiki/geda-cygwin.html
@@ -12,22 +12,25 @@
<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>
+<h1 class="sectionedit74"><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…).
+
+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>
+<!-- EDIT74 SECTION "Installing gEDA/gaf on Windows - the Cygwin way" [1-258] -->
+<h2 class="sectionedit75"><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>.
+
+<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>
@@ -35,7 +38,9 @@ In the package selection dialog, select the following packages:
</p>
<p>
-(Hint: press the â??viewâ?? button once to arrange the list in alphabetical order)
+(Hint: press the â??viewâ?? button once to arrange the list in
+alphabetical order)
+
</p>
<pre class="code">atk-devel
crypt
@@ -56,34 +61,39 @@ xorg-x11-fscl
xterm</pre>
<p>
- <strong>2. Append these lines to your .bash_profile:</strong>
+
+<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:
+
+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>
+
+<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
+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>
+<pre class="code">--disable-stroke</pre>
<p>
- to the opts= line. Add the following options to the opts= line in the Makefile
+
+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>
+<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>
@@ -93,18 +103,21 @@ $ make install
( ...patience... )</pre>
<p>
- <strong>5. Now, to properly view the documentation from the help menu of gschem:</strong>
+
+<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:
+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:
+
+Try:
</p>
<pre class="code">$ iexplore
( Microsoft Internet Explorer appears )
@@ -116,14 +129,16 @@ $ gschemdoc -m
( gEDA documentation appears )</pre>
<p>
- <strong>6. Finally, start the X server:</strong>
+
+<strong>6. Finally, start the X server:</strong>
</p>
<pre class="code">$ startx</pre>
<p>
- Have fun!
+
+Have fun!
</p>
</div>
-<!-- SECTION "Instructions" [259-] --></body>
+<!-- EDIT75 SECTION "Instructions" [259-] --></body>
</html>
diff --git a/docs/wiki/geda-data_plotting_improvements.html b/docs/wiki/geda-data_plotting_improvements.html
index 329b69c..afc7032 100644
--- a/docs/wiki/geda-data_plotting_improvements.html
+++ b/docs/wiki/geda-data_plotting_improvements.html
@@ -11,34 +11,19 @@
</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>
+<h1 class="sectionedit80"><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>
+<!-- EDIT80 SECTION "Simulation Data Plotting" [1-41] -->
+<h2 class="sectionedit81"><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:
+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>
@@ -49,33 +34,35 @@ This article discusses on how data plotting can be improved. There are various p
</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 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 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:
+
+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 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 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 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 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 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>
+<!-- EDIT81 SECTION "Rationale" [42-1133] -->
+<h2 class="sectionedit82"><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>
@@ -83,12 +70,14 @@ This article discusses on how data plotting can be improved. There are various p
</ul>
</div>
-<!-- SECTION "Draft1: Extend gtkwaves" [1134-1219] -->
-<h2><a name="draft2improve_gwave" id="draft2improve_gwave">Draft2: improve gwave</a></h2>
+<!-- EDIT82 SECTION "Draft1: Extend gtkwaves" [1134-1219] -->
+<h2 class="sectionedit83"><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.
+
+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>
@@ -98,21 +87,26 @@ This article discusses on how data plotting can be improved. There are various p
</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>
+<!-- EDIT83 SECTION "Draft2: improve gwave" [1220-1479] -->
+<h2 class="sectionedit84"><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)
+
+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>
+<!-- EDIT84 SECTION "Draft3: Search for existing data exploring programs" [1480-1725] -->
+<h2 class="sectionedit85"><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.
+
+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>
@@ -128,9 +122,26 @@ This article discusses on how data plotting can be improved. There are various p
</ul>
<p>
- Disadvantage: This configuration has a huge rucksack of additional required packages.
+
+Disadvantage: This configuration has a huge rucksack of additional required packages.
+</p>
+
+<p>
+<strong>Update</strong>
+</p>
+
+<p>
+There are now some programs out there, that use the python, numpy, matplotlib tool chain.
</p>
+<ul>
+<li class="level1"><div class="li"> oscopy: <a href="http://repo.or.cz/w/oscopy.git"; class="urlextern" title="http://repo.or.cz/w/oscopy.git"; rel="nofollow">http://repo.or.cz/w/oscopy.git</a></div>
+</li>
+<li class="level1"><div class="li"> dataplot: <a href="http://www.h-renrew.de/h/dataplot/dataplot.html"; class="urlextern" title="http://www.h-renrew.de/h/dataplot/dataplot.html"; rel="nofollow">http://www.h-renrew.de/h/dataplot/dataplot.html</a>, <a href="http://repo.or.cz/w/dataplot.git"; class="urlextern" title="http://repo.or.cz/w/dataplot.git"; rel="nofollow">http://repo.or.cz/w/dataplot.git</a></div>
+</li>
+<li class="level1"><div class="li"> gsim: <a href="http://kiwiki.fmtnuni.sk/mediawiki/index.php/Description_of_gsim"; class="urlextern" title="http://kiwiki.fmtnuni.sk/mediawiki/index.php/Description_of_gsim"; rel="nofollow">http://kiwiki.fmtnuni.sk/mediawiki/index.php/Description_of_gsim</a></div>
+</li>
+</ul>
</div>
-<!-- SECTION "Draft4: A new plotting application" [1725-] --></body>
+<!-- EDIT85 SECTION "Draft4: A new plotting application" [1726-] --></body>
</html>
diff --git a/docs/wiki/geda-data_structure_design_discussion.html b/docs/wiki/geda-data_structure_design_discussion.html
index d639d15..f79b679 100644
--- a/docs/wiki/geda-data_structure_design_discussion.html
+++ b/docs/wiki/geda-data_structure_design_discussion.html
@@ -11,71 +11,47 @@
</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>
+<h1 class="sectionedit105"><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>
+<!-- EDIT105 SECTION "Data structure design discussion" [1-48] -->
+<h1 class="sectionedit106"><a name="concept_diagram" id="concept_diagram">Concept diagram</a></h1>
<div class="level1">
<p>
- (Inspired by gnetman, by Bill Cox)
+
+(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>
+<a href="/./lib/exe/fetch.php?hash=d4505f&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>
+<!-- EDIT106 SECTION "Concept diagram" [49-178] -->
+<h2 class="sectionedit107"><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>
+<!-- EDIT107 SECTION "Concepts behind the structures" [179-222] -->
+<h3 class="sectionedit108"><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.
+
+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>
+<!-- EDIT108 SECTION "Design" [223-446] -->
+<h3 class="sectionedit109"><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.
+
+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>
@@ -83,47 +59,51 @@ We may also define a <strong>symbolic</strong> (graphic) representation of a cir
</p>
</div>
-<!-- SECTION "Circuit" [447-1004] -->
-<h3><a name="mport" id="mport">MPort</a></h3>
+<!-- EDIT109 SECTION "Circuit" [447-1004] -->
+<h3 class="sectionedit110"><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.
+
+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>
+<!-- EDIT110 SECTION "MPort" [1005-1541] -->
+<h3 class="sectionedit111"><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.
+
+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>
+<!-- EDIT111 SECTION "Instance" [1542-1929] -->
+<h3 class="sectionedit112"><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>.
+
+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.
+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>
+<!-- EDIT112 SECTION "Attrib" [1930-2569] -->
+<h3 class="sectionedit113"><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>.
+
+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.
+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>
@@ -135,29 +115,32 @@ 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>
+<!-- EDIT113 SECTION "Netlist" [2570-3435] -->
+<h3 class="sectionedit114"><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>.
+
+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.
+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>
+<!-- EDIT114 SECTION "Net" [3436-3940] -->
+<h3 class="sectionedit115"><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.
+
+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.
+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>
@@ -176,7 +159,7 @@ Whilst most objects on a <strong>page</strong> are graphic primitives, there are
</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 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>
@@ -193,15 +176,17 @@ Whilst most objects on a <strong>page</strong> are graphic primitives, there are
</ul>
</div>
-<!-- SECTION "Page" [3941-5460] -->
-<h1><a name="brainstorms" id="brainstorms">Brainstorms</a></h1>
+<!-- EDIT115 SECTION "Page" [3941-5460] -->
+<h1 class="sectionedit116"><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)
+
+(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 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>
@@ -213,7 +198,7 @@ Whilst most objects on a <strong>page</strong> are graphic primitives, there are
</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 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>
@@ -222,5 +207,5 @@ Whilst most objects on a <strong>page</strong> are graphic primitives, there are
</ul>
</div>
-<!-- SECTION "Brainstorms" [5461-] --></body>
+<!-- EDIT116 SECTION "Brainstorms" [5461-] --></body>
</html>
diff --git a/docs/wiki/geda-debian.fr.html b/docs/wiki/geda-debian.fr.html
index 0679bda..189c66a 100644
--- a/docs/wiki/geda-debian.fr.html
+++ b/docs/wiki/geda-debian.fr.html
@@ -12,16 +12,15 @@
<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>
+<h1 class="sectionedit131"><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.
+
+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
+<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:
@@ -38,8 +37,7 @@ On my system /usr/lib/libqthreads.so pointed to a non existing
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>
+ sudo ln -s libqthreads.so.12.3.0 libqthreads.so.12.3.1</pre>
</div>
</body>
diff --git a/docs/wiki/geda-debian.html b/docs/wiki/geda-debian.html
index 110b34c..210d20a 100644
--- a/docs/wiki/geda-debian.html
+++ b/docs/wiki/geda-debian.html
@@ -12,9 +12,7 @@
<body>
-
-
-<h1><a name="installer_20070221_on_debian_testing" id="installer_20070221_on_debian_testing">Installer 20070221 on Debian/testing</a></h1>
+<h1 class="sectionedit133"><a name="installer_20070221_on_debian_testing" id="installer_20070221_on_debian_testing">Installer 20070221 on Debian/testing</a></h1>
<div class="level1">
<p>
@@ -44,7 +42,8 @@ The iso image contains binary packages to all the open source development utilit
</ul>
<p>
-The debian package manager will expand this list significantly as required by the debian database of dependencies.
+The debian package manager will expand this list significantly as required by the debian database of dependencies.
+
</p>
</div>
diff --git a/docs/wiki/geda-design_flow_and_hierarchy_roadmap.html b/docs/wiki/geda-design_flow_and_hierarchy_roadmap.html
index 261d0da..79b086c 100644
--- a/docs/wiki/geda-design_flow_and_hierarchy_roadmap.html
+++ b/docs/wiki/geda-design_flow_and_hierarchy_roadmap.html
@@ -11,36 +11,17 @@
</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>
+<h1 class="sectionedit178"><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 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>
+<!-- EDIT178 SECTION "Required for production circuits" [1-135] -->
+<h2 class="sectionedit179"><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>
@@ -49,15 +30,15 @@
<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]
+ 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]
+ 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]
+ 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>
@@ -65,7 +46,7 @@ More useful, (than creating intermediate file formats-ed.) is to <strong>refacto
</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?]
+ 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>
@@ -73,29 +54,33 @@ More useful, (than creating intermediate file formats-ed.) is to <strong>refacto
</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]
+ 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]
+ <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]
+
+<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?
+<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>
+<!-- EDIT179 SECTION "intermediate translation file format VHDL? EDIF?" [136-2788] -->
+<h2 class="sectionedit180"><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>
+<!-- EDIT180 SECTION "Hierarchical Buses" [2789-2821] -->
+<h2 class="sectionedit181"><a name="ipc_improvements" id="ipc_improvements">IPC Improvements</a></h2>
<div class="level2">
<p>
@@ -103,7 +88,7 @@ More useful, (than creating intermediate file formats-ed.) is to <strong>refacto
</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]
+ 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>
@@ -111,16 +96,16 @@ More useful, (than creating intermediate file formats-ed.) is to <strong>refacto
</p>
</div>
-<!-- SECTION "IPC Improvements" [2822-3368] -->
-<h2><a name="robust_function" id="robust_function">Robust Function</a></h2>
+<!-- EDIT181 SECTION "IPC Improvements" [2822-3368] -->
+<h2 class="sectionedit182"><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]
+ 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]
+ 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>
@@ -128,7 +113,7 @@ More useful, (than creating intermediate file formats-ed.) is to <strong>refacto
</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]
+ 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>
@@ -140,8 +125,8 @@ More useful, (than creating intermediate file formats-ed.) is to <strong>refacto
</p>
</div>
-<!-- SECTION "Robust Function" [3369-4944] -->
-<h2><a name="other_improvements" id="other_improvements">Other Improvements</a></h2>
+<!-- EDIT182 SECTION "Robust Function" [3369-4944] -->
+<h2 class="sectionedit183"><a name="other_improvements" id="other_improvements">Other Improvements</a></h2>
<div class="level2">
<p>
@@ -153,7 +138,7 @@ It is very useful I think to let DRC run to completion and <strong>have a DRC la
</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]
+ 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>
@@ -161,7 +146,8 @@ It is very useful I think to let DRC run to completion and <strong>have a DRC la
</p>
<p>
- <strong>gschem attribute editable as symbols placed</strong>, (such as description of the layout footprint attribute) [CP Tarun]
+
+<strong>gschem attribute editable as symbols placed</strong>, (such as description of the layout footprint attribute) [CP Tarun]
</p>
<p>
@@ -169,7 +155,7 @@ It is very useful I think to let DRC run to completion and <strong>have a DRC la
</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]
+ 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>
@@ -185,12 +171,13 @@ It is very useful I think to let DRC run to completion and <strong>have a DRC la
</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]
+
+<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>
+<!-- EDIT183 SECTION "Other Improvements" [4945-6847] -->
+<h2 class="sectionedit184"><a name="too_detailed" id="too_detailed">Too Detailed</a></h2>
<div class="level2">
<p>
@@ -202,7 +189,7 @@ It is very useful I think to let DRC run to completion and <strong>have a DRC la
</p>
<p>
- PCB doesnâ??t care what the refdes is, a heirarchical one is just as valid [DJ Delorie]
+ PCB doesn't care what the refdes is, a heirarchical one is just as valid [DJ Delorie]
</p>
<p>
@@ -210,7 +197,7 @@ It is very useful I think to let DRC run to completion and <strong>have a DRC la
</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]
+ 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>
@@ -218,16 +205,18 @@ It is very useful I think to let DRC run to completion and <strong>have a DRC la
</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]
+ 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>
+<!-- EDIT184 SECTION "Too Detailed" [6848-7493] -->
+<h2 class="sectionedit185"><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]
+
+<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>
@@ -235,15 +224,15 @@ It is very useful I think to let DRC run to completion and <strong>have a DRC la
</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]
+ 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?
+<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."
+<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>
@@ -251,9 +240,10 @@ It is very useful I think to let DRC run to completion and <strong>have a DRC la
</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>
+<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>
+<!-- EDIT185 SECTION "Implementation" [7494-] --></body>
</html>
diff --git a/docs/wiki/geda-design_flow_roadmap.html b/docs/wiki/geda-design_flow_roadmap.html
index 45f3a9a..d9f11c8 100644
--- a/docs/wiki/geda-design_flow_roadmap.html
+++ b/docs/wiki/geda-design_flow_roadmap.html
@@ -12,13 +12,13 @@
<body>
-
-
-<h2><a name="page_moved" id="page_moved">Page moved</a></h2>
+<h2 class="sectionedit189"><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>.
+
+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>
diff --git a/docs/wiki/geda-devel-tips.html b/docs/wiki/geda-devel-tips.html
index 519e21d..bc7dbb0 100644
--- a/docs/wiki/geda-devel-tips.html
+++ b/docs/wiki/geda-devel-tips.html
@@ -11,46 +11,13 @@
</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>
+<h1 class="sectionedit191"><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>
+<!-- EDIT191 SECTION "gEDA Developer Tips, tricks and hints" [1-54] -->
+<h2 class="sectionedit192"><a name="data_structure_of_a_schematic" id="data_structure_of_a_schematic">Data Structure of a Schematic</a></h2>
<div class="level2">
<p>
@@ -62,20 +29,21 @@ An overview of the data structure of a schematic can be retrieved <a href="http:
</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>
+<!-- EDIT192 SECTION "Data Structure of a Schematic" [55-503] -->
+<h2 class="sectionedit193"><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.
+
+<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.
+Some sections of the gaf source have already been doxyfied. Currently, this includes libgeda, gschem, gnetlist, gsymcheck 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>.
+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>
@@ -83,12 +51,14 @@ The following sections provide an introduction on how gschem and libgeda are cus
</p>
</div>
-<!-- SECTION "Doxygen Comments and styles" [504-1809] -->
-<h3><a name="documenting_files" id="documenting_files">Documenting Files</a></h3>
+<!-- EDIT193 SECTION "Doxygen Comments and Styles" [504-1838] -->
+<h3 class="sectionedit194"><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.
+
+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...
@@ -97,27 +67,33 @@ The following sections provide an introduction on how gschem and libgeda are cus
*/</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>
+<!-- EDIT194 SECTION "Documenting Files" [1839-2288] -->
+<h3 class="sectionedit195"><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.
+
+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>
+<!-- EDIT195 SECTION "Documenting Variables/Defines/Typedefs" [2289-2662] -->
+<h3 class="sectionedit196"><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.
+
+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.
+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
@@ -130,12 +106,14 @@ Usually an additional <strong>Function Description</strong> paragraph is used fo
*/</pre>
</div>
-<!-- SECTION "Documenting Functions" [2634-3504] -->
-<h3><a name="structure_documentation" id="structure_documentation">Structure Documentation</a></h3>
+<!-- EDIT196 SECTION "Documenting Functions" [2663-3533] -->
+<h3 class="sectionedit197"><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.
+
+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
*
@@ -155,33 +133,35 @@ struct st_conn {
};</pre>
</div>
-<!-- SECTION "Structure Documentation" [3505-4565] -->
-<h3><a name="bug_todo_commands" id="bug_todo_commands">Bug/Todo Commands</a></h3>
+<!-- EDIT197 SECTION "Structure Documentation" [3534-4594] -->
+<h3 class="sectionedit198"><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.
+
+<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>
+<!-- EDIT198 SECTION "Bug/Todo Commands" [4595-4892] -->
+<h2 class="sectionedit199"><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>
+<!-- EDIT199 SECTION "Dialogs: Design and Behaviour" [4893-4937] -->
+<h3 class="sectionedit200"><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.
+There's a nice document from the gnome guys called <a href="http://library.gnome.org/devel/hig-book/"; class="urlextern" title="http://library.gnome.org/devel/hig-book/"; 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 class="level1"><div class="li"> alignment of elements. See <a href="http://library.gnome.org/devel/hig-book/nightly/windows.html.en"; class="urlextern" title="http://library.gnome.org/devel/hig-book/nightly/windows.html.en"; rel="nofollow"> Window Layout</a></div>
</li>
<li class="level1"><div class="li"> right alignment of dialog buttons</div>
</li>
@@ -196,18 +176,20 @@ Thereâ??s a nice document from the gnome guys called <a href="http://developer.g
</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>
+<!-- EDIT200 SECTION "Dialog Design" [4938-5557] -->
+<h3 class="sectionedit201"><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.
+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.
+
+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>
@@ -215,25 +197,28 @@ A modal dialog is not OK if there is a lot of user interaction with the dialog.
</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>
+<!-- EDIT201 SECTION "Modal or Nonmodal dialogs" [5558-6089] -->
+<h3 class="sectionedit202"><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>
+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://library.gnome.org/devel/gtk/unstable/gtk3-Standard-Enumerations.html#GtkWindowPosition"; class="urlextern" title="http://library.gnome.org/devel/gtk/unstable/gtk3-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.
+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>).
+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://git.gnome.org/browse/gtk+/tree/gtk/gtkdialog.c"; class="urlextern" title="http://git.gnome.org/browse/gtk+/tree/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>
+<!-- EDIT202 SECTION "Where to place the dialog" [6090-6838] -->
+<h3 class="sectionedit203"><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>
@@ -245,171 +230,177 @@ For nonmodal dialogs the setting of transient_for property is not obvious. While
</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.
+<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>
+<pre class="code lisp"><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>
+<span class="br0">(</span>raise-dialog-boxes-on-expose <span class="st0">"disabled"</span><span class="br0">)</span></pre></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>
+<!-- EDIT203 SECTION "Placing dialogs in front of their parent window" [6839-7924] -->
+<h3 class="sectionedit204"><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>.
+
+Button order at the bottom of the dialog depends on which operating system the user is using.
+GTK handles this automatically, but requires the developers set the alternative button order. For more information, check the GTK documentation <a href="http://library.gnome.org/devel/gtk/unstable/GtkDialog.html#gtk-dialog-set-alternative-button-order"; class="urlextern" title="http://library.gnome.org/devel/gtk/unstable/GtkDialog.html#gtk-dialog-set-alternative-button-order"; rel="nofollow">here</a>.
</p>
<p>
-The alternative button order is set with just one call to a GTK function:
+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>
+<pre class="code C"><span class="coMULTI">/* Set the alternative button order (ok, no, 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><span class="sy0">,</span>
+ GTK_RESPONSE_OK<span class="sy0">,</span>
+ GTK_RESPONSE_NO<span class="sy0">,</span>
+ GTK_RESPONSE_CANCEL<span class="sy0">,</span>
+ GTK_RESPONSE_HELP<span class="sy0">,</span>
+ <span class="sy0">-</span><span class="nu0">1</span><span class="br0">)</span><span class="sy0">;</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>
+<!-- EDIT204 SECTION "Button order in dialogs" [7925-8727] -->
+<h3 class="sectionedit205"><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>
+<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 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>
+<!-- EDIT205 SECTION "Dialog design of the current dialogs" [8728-9092] -->
+<h3 class="sectionedit206"><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>
+<pre class="code c"><span class="kw4">void</span> dialog <span class="br0">(</span>TOPLEVEL <span class="sy0">*</span>w_current<span class="br0">)</span>
<span class="br0">{</span>
- GtkWidget *vbox, *label, *alignment, *table;
- GtkWidget *dialog;
+ GtkWidget <span class="sy0">*</span>vbox<span class="sy0">,</span> <span class="sy0">*</span>label<span class="sy0">,</span> <span class="sy0">*</span>alignment<span class="sy0">,</span> <span class="sy0">*</span>table<span class="sy0">;</span>
+ GtkWidget <span class="sy0">*</span>dialog<span class="sy0">;</span>
<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="kw1">if</span> <span class="br0">(</span><span class="sy0">!</span>dialog<span class="br0">)</span> <span class="br0">{</span>
+ dialog <span class="sy0">=</span> 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="sy0">,</span>
<span class="coMULTI">/* the parent window or NULL */</span>
- GTK_WINDOW<span class="br0">(</span>w_current->main_window<span class="br0">)</span>,
+ GTK_WINDOW<span class="br0">(</span>w_current<span class="sy0">-></span>main_window<span class="br0">)</span><span class="sy0">,</span>
<span class="coMULTI">/* dialog properties */</span>
- GTK_DIALOG_MODAL, <span class="coMULTI">/* 0 for nonmodal dialogs */</span>
+ GTK_DIALOG_MODAL<span class="sy0">,</span> <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>;
+ GTK_STOCK_CANCEL<span class="sy0">,</span>
+ GTK_RESPONSE_REJECT<span class="sy0">,</span>
+ GTK_STOCK_OK<span class="sy0">,</span>
+ GTK_RESPONSE_ACCEPT<span class="sy0">,</span>
+ NULL<span class="br0">)</span><span class="sy0">;</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 the alternative button order (ok, no, 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><span class="sy0">,</span>
+ GTK_RESPONSE_OK<span class="sy0">,</span>
+ GTK_RESPONSE_NO<span class="sy0">,</span>
+ GTK_RESPONSE_CANCEL<span class="sy0">,</span>
+ GTK_RESPONSE_HELP<span class="sy0">,</span>
+ <span class="sy0">-</span><span class="nu0">1</span><span class="br0">)</span><span class="sy0">;</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>;
+ gtk_dialog_set_default_response<span class="br0">(</span>GTK_DIALOG<span class="br0">(</span>dialog<span class="br0">)</span><span class="sy0">,</span>
+ GTK_RESPONSE_ACCEPT<span class="br0">)</span><span class="sy0">;</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>;
+ gtk_signal_connect<span class="br0">(</span>GTK_OBJECT<span class="br0">(</span>dialog<span class="br0">)</span><span class="sy0">,</span> <span class="st0">"response"</span><span class="sy0">,</span>
+ GTK_SIGNAL_FUNC<span class="br0">(</span>dialog_response<span class="br0">)</span><span class="sy0">,</span> w_current<span class="br0">)</span><span class="sy0">;</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>;
+ gtk_window_position<span class="br0">(</span>GTK_WINDOW <span class="br0">(</span>dialog<span class="br0">)</span><span class="sy0">,</span> GTK_WIN_POS_MOUSE<span class="br0">)</span><span class="sy0">;</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>;
+ vbox <span class="sy0">=</span> GTK_DIALOG<span class="br0">(</span>dialog<span class="br0">)</span><span class="sy0">-></span>vbox<span class="sy0">;</span>
+ gtk_container_set_border_width<span class="br0">(</span>GTK_CONTAINER<span class="br0">(</span>dialog<span class="br0">)</span><span class="sy0">,</span>DIALOG_BORDER_SPACING<span class="br0">)</span><span class="sy0">;</span>
+ gtk_box_set_spacing<span class="br0">(</span>GTK_BOX<span class="br0">(</span>vbox<span class="br0">)</span><span class="sy0">,</span> DIALOG_V_SPACING<span class="br0">)</span><span class="sy0">;</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>;
+ label <span class="sy0">=</span> 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><span class="sy0">;</span>
+ gtk_label_set_use_markup<span class="br0">(</span>GTK_LABEL<span class="br0">(</span>label<span class="br0">)</span><span class="sy0">,</span> TRUE<span class="br0">)</span><span class="sy0">;</span>
+ gtk_misc_set_alignment<span class="br0">(</span>GTK_MISC<span class="br0">(</span>label<span class="br0">)</span><span class="sy0">,</span><span class="nu0">0</span><span class="sy0">,</span><span class="nu0">0</span><span class="br0">)</span><span class="sy0">;</span>
+ gtk_box_pack_start<span class="br0">(</span>GTK_BOX<span class="br0">(</span>vbox<span class="br0">)</span><span class="sy0">,</span> label<span class="sy0">,</span> FALSE<span class="sy0">,</span> FALSE<span class="sy0">,</span> <span class="nu0">0</span><span class="br0">)</span><span class="sy0">;</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>;
+ alignment <span class="sy0">=</span> gtk_alignment_new<span class="br0">(</span><span class="nu0">0</span><span class="sy0">,</span><span class="nu0">0</span><span class="sy0">,</span><span class="nu0">1</span><span class="sy0">,</span><span class="nu0">1</span><span class="br0">)</span><span class="sy0">;</span>
+ gtk_alignment_set_padding<span class="br0">(</span>GTK_ALIGNMENT<span class="br0">(</span>alignment<span class="br0">)</span><span class="sy0">,</span> <span class="nu0">0</span><span class="sy0">,</span> <span class="nu0">0</span><span class="sy0">,</span>
+ DIALOG_INDENTATION<span class="sy0">,</span> <span class="nu0">0</span><span class="br0">)</span><span class="sy0">;</span>
+ gtk_box_pack_start<span class="br0">(</span>GTK_BOX<span class="br0">(</span>vbox<span class="br0">)</span><span class="sy0">,</span> alignment<span class="sy0">,</span> FALSE<span class="sy0">,</span> FALSE<span class="sy0">,</span> <span class="nu0">0</span><span class="br0">)</span><span class="sy0">;</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>;
+ table <span class="sy0">=</span> gtk_table_new <span class="br0">(</span><span class="nu0">3</span><span class="sy0">,</span> <span class="nu0">2</span><span class="sy0">,</span> FALSE<span class="br0">)</span><span class="sy0">;</span>
+ gtk_table_set_row_spacings<span class="br0">(</span>GTK_TABLE<span class="br0">(</span>table<span class="br0">)</span><span class="sy0">,</span> DIALOG_V_SPACING<span class="br0">)</span><span class="sy0">;</span>
+ gtk_table_set_col_spacings<span class="br0">(</span>GTK_TABLE<span class="br0">(</span>table<span class="br0">)</span><span class="sy0">,</span> DIALOG_H_SPACING<span class="br0">)</span><span class="sy0">;</span>
+ gtk_container_add<span class="br0">(</span>GTK_CONTAINER<span class="br0">(</span>alignment<span class="br0">)</span><span class="sy0">,</span> table<span class="br0">)</span><span class="sy0">;</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>;
+ label <span class="sy0">=</span> gtk_label_new<span class="br0">(</span>_<span class="br0">(</span><span class="st0">"Text:"</span><span class="br0">)</span><span class="br0">)</span><span class="sy0">;</span>
+ gtk_misc_set_alignment<span class="br0">(</span>GTK_MISC<span class="br0">(</span>label<span class="br0">)</span><span class="sy0">,</span><span class="nu0">0</span><span class="sy0">,</span><span class="nu0">0</span><span class="br0">)</span><span class="sy0">;</span>
+ gtk_table_attach<span class="br0">(</span>GTK_TABLE<span class="br0">(</span>table<span class="br0">)</span><span class="sy0">,</span> label<span class="sy0">,</span> <span class="nu0">0</span><span class="sy0">,</span><span class="nu0">1</span><span class="sy0">,</span><span class="nu0">0</span><span class="sy0">,</span><span class="nu0">1</span><span class="sy0">,</span> GTK_FILL<span class="sy0">,</span><span class="nu0">0</span><span class="sy0">,</span><span class="nu0">0</span><span class="sy0">,</span><span class="nu0">0</span><span class="br0">)</span><span class="sy0">;</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>;
+ textentry <span class="sy0">=</span> gtk_entry_new_with_max_length <span class="br0">(</span><span class="nu0">10</span><span class="br0">)</span><span class="sy0">;</span>
+ gtk_table_attach_defaults<span class="br0">(</span>GTK_TABLE<span class="br0">(</span>table<span class="br0">)</span><span class="sy0">,</span> textentry<span class="sy0">,</span> <span class="nu0">1</span><span class="sy0">,</span><span class="nu0">2</span><span class="sy0">,</span><span class="nu0">0</span><span class="sy0">,</span><span class="nu0">1</span><span class="br0">)</span><span class="sy0">;</span>
+ gtk_entry_set_activates_default<span class="br0">(</span>GTK_ENTRY<span class="br0">(</span>textentry<span class="br0">)</span><span class="sy0">,</span> TRUE<span class="br0">)</span><span class="sy0">;</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>;
+ GLADE_HOOKUP_OBJECT<span class="br0">(</span>dialog<span class="sy0">,</span> sizeentry<span class="sy0">,</span><span class="st0">"textentry"</span><span class="br0">)</span><span class="sy0">;</span>
<span class="coMULTI">/* show all widgets recursivly */</span>
- gtk_widget_show_all<span class="br0">(</span>dialog<span class="br0">)</span>;
+ gtk_widget_show_all<span class="br0">(</span>dialog<span class="br0">)</span><span class="sy0">;</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>;
+ gtk_window_present<span class="br0">(</span>GTK_WINDOW<span class="br0">(</span>dialog<span class="br0">)</span><span class="br0">)</span><span class="sy0">;</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>;
+ textentry <span class="sy0">=</span> g_object_get_data<span class="br0">(</span>G_OBJECT<span class="br0">(</span>dialog<span class="br0">)</span><span class="sy0">,</span> <span class="st0">"textentry"</span><span class="br0">)</span><span class="sy0">;</span>
+ gtk_entry_set_text<span class="br0">(</span>GTK_ENTRY<span class="br0">(</span>textentry<span class="br0">)</span><span class="sy0">,</span> string<span class="br0">)</span><span class="sy0">;</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>;
+ gtk_entry_select_region<span class="br0">(</span>GTK_ENTRY<span class="br0">(</span>textentry<span class="br0">)</span><span class="sy0">,</span> <span class="nu0">0</span><span class="sy0">,</span> strlen<span class="br0">(</span>string<span class="br0">)</span><span class="br0">)</span><span class="sy0">;</span>
<span class="br0">}</span></pre>
+
<p>
-The response function for such a dialog may look like this:
+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>
+<pre class="code c"><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:
@@ -429,13 +420,14 @@ The response function for such a dialog may look like this:
<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>
+<span class="br0">}</span></pre></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>
+<!-- EDIT206 SECTION "Source template for simple dialogs" [9093-14195] -->
+<h3 class="sectionedit207"><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 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>
@@ -446,7 +438,8 @@ The response function for such a dialog may look like this:
</ul>
<p>
- <strong>Hereâ??s a list of things that could be improved:</strong>
+
+<strong>Here's a list of things that could be improved:</strong>
</p>
</div>
@@ -489,7 +482,7 @@ The response function for such a dialog may look like this:
</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 class="level1"><div class="li"> maybe replace the text alignment with nine ratio buttons, toggle buttons with icons or â?¦</div>
</li>
</ul>
@@ -549,7 +542,7 @@ The response function for such a dialog may look like this:
<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 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>
@@ -713,5 +706,5 @@ The response function for such a dialog may look like this:
</ul>
</div>
-<!-- SECTION "Current Dialog Issues in Gschem" [14226-] --></body>
+<!-- EDIT207 SECTION "Current Dialog Issues in Gschem" [14196-] --></body>
</html>
diff --git a/docs/wiki/geda-developer.html b/docs/wiki/geda-developer.html
new file mode 100644
index 0000000..262fb88
--- /dev/null
+++ b/docs/wiki/geda-developer.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 class="sectionedit1395"><a name="geda_developer_information" id="geda_developer_information">gEDA Developer Information</a></h1>
+<div class="level1">
+
+</div>
+<!-- EDIT1395 SECTION "gEDA Developer Information" [1-43] -->
+<h2 class="sectionedit1396"><a name="resources" id="resources">Resources</a></h2>
+<div class="level2">
+
+</div>
+
+<h4><a name="source_code_repository" id="source_code_repository">Source Code Repository</a></h4>
+<div class="level4">
+<ul>
+<li class="level1"><div class="li"> <a href="http://git.gpleda.org/"; class="urlextern" title="http://git.gpleda.org/"; rel="nofollow"> gEDA repository web view </a></div>
+</li>
+</ul>
+
+</div>
+
+<h4><a name="bug_trackers" id="bug_trackers">Bug Trackers</a></h4>
+<div class="level4">
+<ul>
+<li class="level1"><div class="li"> <a href="http://launchpad.net/geda/+bugs"; class="urlextern" title="http://launchpad.net/geda/+bugs"; rel="nofollow"> gEDA/gaf bug tracker </a> <a href="http://launchpad.net/geda/+filebug"; class="urlextern" title="http://launchpad.net/geda/+filebug"; rel="nofollow"> Submit new bug </a></div>
+</li>
+<li class="level1"><div class="li"> <a href="http://launchpad.net/pcb/+bugs"; class="urlextern" title="http://launchpad.net/pcb/+bugs"; rel="nofollow"> pcb bug tracker </a> <a href="http://launchpad.net/pcb/+filebug"; class="urlextern" title="http://launchpad.net/pcb/+filebug"; rel="nofollow"> Submit new bug </a></div>
+</li>
+</ul>
+
+<p>
+
+<a href="geda-bug_triage_guide.html" class="wikilink1" title="geda-bug_triage_guide.html"> Bug Triage Guide (for gEDA/gaf and pcb) </a>
+
+</p>
+<ul>
+<li class="level1"><div class="li"> <a href="http://sourceforge.net/tracker/?atid=409538&group_id=33921"; class="urlextern" title="http://sourceforge.net/tracker/?atid=409538&group_id=33921"; rel="nofollow"> Submit gerbv bug report </a></div>
+</li>
+<li class="level1"><div class="li"> <a href="http://sourceforge.net/tracker/?atid=409540&group_id=33921"; class="urlextern" title="http://sourceforge.net/tracker/?atid=409540&group_id=33921"; rel="nofollow"> Submit gerbv patch </a> </div>
+</li>
+<li class="level1"><div class="li"> <a href="http://sourceforge.net/tracker/?atid=409541&group_id=33921"; class="urlextern" title="http://sourceforge.net/tracker/?atid=409541&group_id=33921"; rel="nofollow"> Submit gerbv feature request </a></div>
+</li>
+</ul>
+
+</div>
+
+<h4><a name="symbols" id="symbols">Symbols</a></h4>
+<div class="level4">
+<ul>
+<li class="level1"><div class="li"> <a href="http://gedasymbols.org"; class="urlextern" title="http://gedasymbols.org"; rel="nofollow"> Contribute symbol </a></div>
+</li>
+</ul>
+
+</div>
+
+<h4><a name="directories" id="directories">Directories</a></h4>
+<div class="level4">
+<ul>
+<li class="level1"><div class="li"> <a href="http://geda.seul.org/release"; class="urlextern" title="http://geda.seul.org/release"; rel="nofollow"> gEDA/gaf Release Directory </a></div>
+</li>
+<li class="level1"><div class="li"> <a href="http://geda.seul.org/devel"; class="urlextern" title="http://geda.seul.org/devel"; rel="nofollow"> gEDA/gaf Development Directory </a></div>
+</li>
+<li class="level1"><div class="li"> <a href="http://geda.seul.org/dist"; class="urlextern" title="http://geda.seul.org/dist"; rel="nofollow"> gEDA Distribution Directory </a></div>
+</li>
+</ul>
+
+</div>
+
+<h4><a name="developer_mailing_list" id="developer_mailing_list">Developer Mailing List</a></h4>
+<div class="level4">
+<ul>
+<li class="level1"><div class="li"> The geda-dev mailing list is a â??subscription by invitation onlyâ?? list.</div>
+</li>
+<li class="level1"><div class="li"> This is a departure from the past where anybody could join the developer list. Unfortunately (or fortunately?) the gEDA community has grown so large that there were â??too many food critics in the kitchenâ?? and that was impeding development progress.</div>
+</li>
+<li class="level1"><div class="li"> This policy might change in the future depending on the response and feedback.</div>
+</li>
+<li class="level1"><div class="li"> All users and new developers, please subscribe to the geda-user list to discuss any issues, as all developers hang out there too.</div>
+</li>
+<li class="level1"><div class="li"> New developers: As you interact with the project (and the various individuals), you will be invited to join the geda-dev mailing list.</div>
+</li>
+<li class="level1"><div class="li"> All discussions are public and archived <a href="http://www.seul.org/archives/geda/dev/"; class="urlextern" title="http://www.seul.org/archives/geda/dev/"; rel="nofollow"> here</a>. This policy will always be in effect.</div>
+</li>
+<li class="level1"><div class="li"> Access: <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"> Web interface</a></div>
+</li>
+<li class="level1"><div class="li"> Archives: <a href="http://www.seul.org/archives/geda/dev/"; class="urlextern" title="http://www.seul.org/archives/geda/dev/"; rel="nofollow"> Monthly</a> <a href="http://www.seul.org/pipermail/geda-dev/"; class="urlextern" title="http://www.seul.org/pipermail/geda-dev/"; rel="nofollow"> Monthly</a> </div>
+</li>
+</ul>
+
+</div>
+<!-- EDIT1396 SECTION "Resources" [44-2145] -->
+<h2 class="sectionedit1397"><a name="accessing_geda_s_source_code_repositories" id="accessing_geda_s_source_code_repositories">Accessing gEDA's source code repositories</a></h2>
+<div class="level2">
+
+<p>
+
+Please see the gEDA <a href="geda-scm.html" class="wikilink1" title="geda-scm.html"> Source Control Management</a> page for information on how to access the gEDA/gaf repository using git or <acronym title="Concurrent Versions System">CVS</acronym>.
+</p>
+
+</div>
+<!-- EDIT1397 SECTION "Accessing gEDA's source code repositories" [2146-2346] -->
+<h2 class="sectionedit1398"><a name="building_geda_gaf_from_git" id="building_geda_gaf_from_git">Building gEDA/gaf from git</a></h2>
+<div class="level2">
+
+<p>
+
+Please see the <a href="geda-gaf_building_git_version.html" class="wikilink1" title="geda-gaf_building_git_version.html"> gEDA/gaf building from git</a> page for more information on how to build the git repository version of gEDA/gaf.
+</p>
+
+</div>
+<!-- EDIT1398 SECTION "Building gEDA/gaf from git" [2347-2547] -->
+<h2 class="sectionedit1399"><a name="developers" id="developers">Developers</a></h2>
+<div class="level2">
+
+<p>
+
+Please see the <a href="http://www.gpleda.org/people.html"; class="urlextern" title="http://www.gpleda.org/people.html"; rel="nofollow"> people</a> page for a list of all active and inactive gEDA developers.
+
+</p>
+
+</div>
+<!-- EDIT1399 SECTION "Developers" [2548-] --></body>
+</html>
diff --git a/docs/wiki/geda-devmacosx.html b/docs/wiki/geda-devmacosx.html
index e0dc148..bcffe89 100644
--- a/docs/wiki/geda-devmacosx.html
+++ b/docs/wiki/geda-devmacosx.html
@@ -11,43 +11,23 @@
</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>
+<h2 class="sectionedit209"><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.
+
+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.
+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?:"
+<pre class="code">PS3="Which port?:"
echo "Choose from the list below."
select NAME in macports fink mac
do
@@ -60,12 +40,11 @@ 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>
+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>
+<!-- EDIT209 SECTION "gEDA On The Mac" [1-1251] -->
+<h2 class="sectionedit210"><a name="geda_via_fink" id="geda_via_fink">gEDA via Fink</a></h2>
<div class="level2">
<p>
@@ -73,13 +52,15 @@ You can link to instructions on installing gEDA via fink from the gEDA <a href="
</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:
+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>
+<!-- EDIT210 SECTION "gEDA via Fink" [1252-1994] -->
+<h2 class="sectionedit211"><a name="geda_via_macports" id="geda_via_macports">gEDA via macports</a></h2>
<div class="level2">
<p>
@@ -87,7 +68,8 @@ I am in the process of putting together a macports release of gEDA. You can dow
</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.
+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>
@@ -98,26 +80,26 @@ Until the macports release is ready, you can use Porticus (or macports command l
</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.
+
+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>
+<!-- EDIT211 SECTION "gEDA via macports" [1995-2641] -->
+<h2 class="sectionedit212"><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.
+
+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>
+<!-- EDIT212 SECTION "Building The Project" [2642-3145] -->
+<h2 class="sectionedit213"><a name="working_with_python" id="working_with_python">Working With Python</a></h2>
<div class="level2">
<p>
@@ -125,8 +107,8 @@ Currently I am working with myEclipse and the PyDev python plugin. You can down
</p>
</div>
-<!-- SECTION "Working With Python" [3159-3657] -->
-<h2><a name="current_mac_issues" id="current_mac_issues">Current Mac Issues</a></h2>
+<!-- EDIT213 SECTION "Working With Python" [3146-3644] -->
+<h2 class="sectionedit214"><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>
@@ -134,8 +116,8 @@ Currently I am working with myEclipse and the PyDev python plugin. You can down
</ul>
</div>
-<!-- SECTION "Current Mac Issues" [3658-3962] -->
-<h2><a name="geda_via_virtualbox" id="geda_via_virtualbox">gEDA via VirtualBox</a></h2>
+<!-- EDIT214 SECTION "Current Mac Issues" [3645-3949] -->
+<h2 class="sectionedit215"><a name="geda_via_virtualbox" id="geda_via_virtualbox">gEDA via VirtualBox</a></h2>
<div class="level2">
<p>
@@ -148,7 +130,8 @@ The gEDA suite programs have been tested and appear to work properly under Ubunt
<pre class="code">sudo apt-get install geda</pre>
<p>
- This installs gschem , gnetlist, & gattrib. Then, to install additional applications:
+
+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
@@ -156,5 +139,5 @@ sudo apt-get install gerbv
sudo apt-get install geda-xgsch2pcb</pre>
</div>
-<!-- SECTION "gEDA via VirtualBox" [3963-] --></body>
+<!-- EDIT215 SECTION "gEDA via VirtualBox" [3950-] --></body>
</html>
diff --git a/docs/wiki/geda-documentation.fr.html b/docs/wiki/geda-documentation.fr.html
index 013d4a3..37dec61 100644
--- a/docs/wiki/geda-documentation.fr.html
+++ b/docs/wiki/geda-documentation.fr.html
@@ -11,44 +11,13 @@
</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>
+<h1 class="sectionedit217"><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>
+<!-- EDIT217 SECTION "Documentation en ligne de la Suite d'Outils gEDA" [1-64] -->
+<h2 class="sectionedit218"><a name="for_document_authors" id="for_document_authors">For document authors</a></h2>
<div class="level2">
<p>
@@ -59,16 +28,16 @@ New features are available for document authors:
</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 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>
+<!-- EDIT218 SECTION "For document authors" [65-273] -->
+<h2 class="sectionedit219"><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 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>
@@ -81,8 +50,8 @@ New features are available for document authors:
</ul>
</div>
-<!-- SECTION "gschem - Saisie de Schémas" [274-634] -->
-<h2><a name="gnetlist_-_netlister" id="gnetlist_-_netlister">gnetlist - Netlister</a></h2>
+<!-- EDIT219 SECTION "gschem - Saisie de Schémas" [274-634] -->
+<h2 class="sectionedit220"><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>
@@ -118,8 +87,8 @@ New features are available for document authors:
</ul>
</div>
-<!-- SECTION "gnetlist - Netlister" [635-1507] -->
-<h2><a name="gsymcheck_-_symbol_checker" id="gsymcheck_-_symbol_checker">gsymcheck - Symbol Checker</a></h2>
+<!-- EDIT220 SECTION "gnetlist - Netlister" [635-1507] -->
+<h2 class="sectionedit221"><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>
@@ -127,8 +96,8 @@ New features are available for document authors:
</ul>
</div>
-<!-- SECTION "gsymcheck - Symbol Checker" [1508-1592] -->
-<h2><a name="utils_-_geda_utilities" id="utils_-_geda_utilities">utils - gEDA Utilities</a></h2>
+<!-- EDIT221 SECTION "gsymcheck - Symbol Checker" [1508-1592] -->
+<h2 class="sectionedit222"><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>
@@ -141,26 +110,26 @@ New features are available for document authors:
</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 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 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>
+<!-- EDIT222 SECTION "utils - gEDA Utilities" [1593-2012] -->
+<h2 class="sectionedit223"><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 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 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>
+<!-- EDIT223 SECTION "Examples" [2013-2162] -->
+<h2 class="sectionedit224"><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>
@@ -170,60 +139,61 @@ New features are available for document authors:
</ul>
</div>
-<!-- SECTION "Attribute/File Format Details" [2163-2328] -->
-<h1><a name="spice" id="spice">SPICE</a></h1>
+<!-- EDIT224 SECTION "Attribute/File Format Details" [2163-2328] -->
+<h1 class="sectionedit225"><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>
+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>
+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>
+by Stuart Brorson ( 5 January 2005).</div>
</li>
</ul>
<p>
- Testing:
+
+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 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>
+<!-- EDIT225 SECTION "SPICE" [2329-3078] -->
+<h1 class="sectionedit226"><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 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 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 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 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>
+<!-- EDIT226 SECTION "ngspice" [3079-3501] -->
+<h1 class="sectionedit227"><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 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>
+<!-- EDIT227 SECTION "gnucap" [3502-3762] -->
+<h1 class="sectionedit228"><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>
@@ -231,13 +201,13 @@ New features are available for document authors:
</ul>
</div>
-<!-- SECTION "gSpiceUI" [3763-3870] -->
-<h1><a name="pcb" id="pcb">PCB</a></h1>
+<!-- EDIT228 SECTION "gSpiceUI" [3763-3870] -->
+<h1 class="sectionedit229"><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 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 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>
@@ -248,8 +218,8 @@ New features are available for document authors:
</ul>
</div>
-<!-- SECTION "PCB" [3871-4187] -->
-<h1><a name="gerbv" id="gerbv">gerbv</a></h1>
+<!-- EDIT229 SECTION "PCB" [3871-4187] -->
+<h1 class="sectionedit230"><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>
@@ -259,8 +229,8 @@ New features are available for document authors:
</ul>
</div>
-<!-- SECTION "gerbv" [4188-4333] -->
-<h1><a name="icarus_verilog" id="icarus_verilog">Icarus Verilog</a></h1>
+<!-- EDIT230 SECTION "gerbv" [4188-4333] -->
+<h1 class="sectionedit231"><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>
@@ -296,11 +266,11 @@ New features are available for document authors:
</ul>
</div>
-<!-- SECTION "Icarus Verilog" [4334-5259] -->
-<h1><a name="gtkwave" id="gtkwave">GTKWave</a></h1>
+<!-- EDIT231 SECTION "Icarus Verilog" [4334-5259] -->
+<h1 class="sectionedit232"><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 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>
@@ -330,8 +300,8 @@ New features are available for document authors:
</ul>
</div>
-<!-- SECTION "GTKWave" [5260-6291] -->
-<h1><a name="wcalc" id="wcalc">Wcalc</a></h1>
+<!-- EDIT232 SECTION "GTKWave" [5260-6291] -->
+<h1 class="sectionedit233"><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>
@@ -343,29 +313,29 @@ New features are available for document authors:
</ul>
</div>
-<!-- SECTION "Wcalc" [6292-6438] -->
-<h1><a name="mcalc" id="mcalc">mcalc</a></h1>
+<!-- EDIT233 SECTION "Wcalc" [6292-6438] -->
+<h1 class="sectionedit234"><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 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>
+<!-- EDIT234 SECTION "mcalc" [6439-6618] -->
+<h1 class="sectionedit235"><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 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 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>
+<!-- EDIT235 SECTION "covered" [6619-] --></body>
</html>
diff --git a/docs/wiki/geda-documentation.html b/docs/wiki/geda-documentation.html
index 51965f0..fcdf93b 100644
--- a/docs/wiki/geda-documentation.html
+++ b/docs/wiki/geda-documentation.html
@@ -11,45 +11,13 @@
</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>
+<h1 class="sectionedit237"><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-56] -->
-<h2><a name="tutorials" id="tutorials">Tutorials</a></h2>
+<!-- EDIT237 SECTION "gEDA Tool Suite on-line documentation" [1-56] -->
+<h2 class="sectionedit238"><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>
@@ -69,11 +37,11 @@
</ul>
</div>
-<!-- SECTION "Tutorials" [57-600] -->
-<h2><a name="gschem_-_schematic_capture" id="gschem_-_schematic_capture">gschem - Schematic Capture</a></h2>
+<!-- EDIT238 SECTION "Tutorials" [57-600] -->
+<h2 class="sectionedit239"><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 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>
@@ -86,8 +54,8 @@
</ul>
</div>
-<!-- SECTION "gschem - Schematic Capture" [601-920] -->
-<h2><a name="gnetlist_-_netlister" id="gnetlist_-_netlister">gnetlist - Netlister</a></h2>
+<!-- EDIT239 SECTION "gschem - Schematic Capture" [601-920] -->
+<h2 class="sectionedit240"><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>
@@ -121,8 +89,8 @@
</ul>
</div>
-<!-- SECTION "gnetlist - Netlister" [921-1744] -->
-<h2><a name="gsymcheck_-_symbol_checker" id="gsymcheck_-_symbol_checker">gsymcheck - Symbol Checker</a></h2>
+<!-- EDIT240 SECTION "gnetlist - Netlister" [921-1744] -->
+<h2 class="sectionedit241"><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>
@@ -130,8 +98,8 @@
</ul>
</div>
-<!-- SECTION "gsymcheck - Symbol Checker" [1745-1830] -->
-<h2><a name="utils_-_geda_utilities" id="utils_-_geda_utilities">utils - gEDA Utilities</a></h2>
+<!-- EDIT241 SECTION "gsymcheck - Symbol Checker" [1745-1830] -->
+<h2 class="sectionedit242"><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>
@@ -144,26 +112,26 @@
</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 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 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" [1831-2247] -->
-<h2><a name="examples" id="examples">Examples</a></h2>
+<!-- EDIT242 SECTION "utils - gEDA Utilities" [1831-2247] -->
+<h2 class="sectionedit243"><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 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 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" [2248-2397] -->
-<h2><a name="attribute_file_format_details" id="attribute_file_format_details">Attribute/File Format Details</a></h2>
+<!-- EDIT243 SECTION "Examples" [2248-2397] -->
+<h2 class="sectionedit244"><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>
@@ -173,60 +141,60 @@
</ul>
</div>
-<!-- SECTION "Attribute/File Format Details" [2398-2563] -->
-<h1><a name="spice" id="spice">SPICE</a></h1>
+<!-- EDIT244 SECTION "Attribute/File Format Details" [2398-2563] -->
+<h1 class="sectionedit245"><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>
+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>
+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>
+by Stuart Brorson ( 5 January 2005).</div>
</li>
</ul>
<p>
- Testing:
+
+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 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" [2564-3297] -->
-<h1><a name="ngspice" id="ngspice">ngspice</a></h1>
+<!-- EDIT245 SECTION "SPICE" [2564-3298] -->
+<h1 class="sectionedit246"><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 class="level1"><div class="li"> <a href="http://ngspice.sourceforge.net/docs/ngspice-manual.pdf"; class="urlextern" title="http://ngspice.sourceforge.net/docs/ngspice-manual.pdf"; rel="nofollow">ngspice User Manual</a></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 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 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 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" [3298-3720] -->
-<h1><a name="gnucap" id="gnucap">gnucap</a></h1>
+<!-- EDIT246 SECTION "ngspice" [3299-3559] -->
+<h1 class="sectionedit247"><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 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" [3721-3949] -->
-<h1><a name="gspiceui" id="gspiceui">gSpiceUI</a></h1>
+<!-- EDIT247 SECTION "gnucap" [3560-3788] -->
+<h1 class="sectionedit248"><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>
@@ -234,8 +202,8 @@
</ul>
</div>
-<!-- SECTION "gSpiceUI" [3950-4035] -->
-<h1><a name="pcb" id="pcb">PCB</a></h1>
+<!-- EDIT248 SECTION "gSpiceUI" [3789-3874] -->
+<h1 class="sectionedit249"><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>
@@ -249,8 +217,8 @@
</ul>
</div>
-<!-- SECTION "PCB" [4036-4440] -->
-<h1><a name="gerbv" id="gerbv">gerbv</a></h1>
+<!-- EDIT249 SECTION "PCB" [3875-4279] -->
+<h1 class="sectionedit250"><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>
@@ -260,8 +228,8 @@
</ul>
</div>
-<!-- SECTION "gerbv" [4441-4586] -->
-<h1><a name="icarus_verilog" id="icarus_verilog">Icarus Verilog</a></h1>
+<!-- EDIT250 SECTION "gerbv" [4280-4425] -->
+<h1 class="sectionedit251"><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>
@@ -299,11 +267,11 @@
</ul>
</div>
-<!-- SECTION "Icarus Verilog" [4587-5581] -->
-<h1><a name="gtkwave" id="gtkwave">GTKWave</a></h1>
+<!-- EDIT251 SECTION "Icarus Verilog" [4426-5420] -->
+<h1 class="sectionedit252"><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 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>
@@ -333,8 +301,8 @@
</ul>
</div>
-<!-- SECTION "GTKWave" [5582-6614] -->
-<h1><a name="wcalc" id="wcalc">Wcalc</a></h1>
+<!-- EDIT252 SECTION "GTKWave" [5421-6453] -->
+<h1 class="sectionedit253"><a name="wcalc" id="wcalc">Wcalc</a></h1>
<div class="level1">
<ul>
<li class="level1"><div class="li"> <a href="http://wcalc.sourceforge.net/"; class="urlextern" title="http://wcalc.sourceforge.net/"; rel="nofollow">wcalc Home Page</a></div>
@@ -348,32 +316,32 @@
</ul>
</div>
-<!-- SECTION "Wcalc" [6615-6815] -->
-<h1><a name="mcalc" id="mcalc">mcalc</a></h1>
+<!-- EDIT253 SECTION "Wcalc" [6454-6654] -->
+<h1 class="sectionedit254"><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 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" [6816-6995] -->
-<h1><a name="covered" id="covered">covered</a></h1>
+<!-- EDIT254 SECTION "mcalc" [6655-6834] -->
+<h1 class="sectionedit255"><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 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 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" [6996-7293] -->
-<h1><a name="for_document_authors" id="for_document_authors">For document authors</a></h1>
+<!-- EDIT255 SECTION "covered" [6835-7132] -->
+<h1 class="sectionedit256"><a name="for_document_authors" id="for_document_authors">For document authors</a></h1>
<div class="level1">
<p>
@@ -384,10 +352,10 @@ New features are available for document authors:
</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 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" [7294-] --></body>
+<!-- EDIT256 SECTION "For document authors" [7133-] --></body>
</html>
diff --git a/docs/wiki/geda-download.html b/docs/wiki/geda-download.html
new file mode 100644
index 0000000..133369e
--- /dev/null
+++ b/docs/wiki/geda-download.html
@@ -0,0 +1,102 @@
+<!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 class="sectionedit1413"><a name="download" id="download">Download</a></h1>
+<div class="level1">
+
+</div>
+<!-- EDIT1413 SECTION "Download" [1-24] -->
+<h2 class="sectionedit1414"><a name="readme" id="readme">README</a></h2>
+<div class="level2">
+
+<p>
+
+Several different methods to install gEDA exist. Select your installation method depending upon your Linux distribution and your level of expertise. If one install method doesn't work for you, please try a different one. Consult the gEDA wiki for further download/install tips. Also, if this is your first time installing gEDA, please read the following:
+
+</p>
+<ul>
+<li class="level1"><div class="li"> gEDA is a set of GNU/Linux or Unix-native programs. There is no supported Windows version. However, since most programs are based on the cross-platform GTK+ libraries, it is theoretically possible to build a Windows version. Therefore, if you want a Windows version, please feel free to grab the sources and try to build one yourself.</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> The gEDA programs use the GTK+ <acronym title="Graphical User Interface">GUI</acronym> toolkit. If you are running KDE, you should have no problem building and installing them as long as the GTK+ libraries and headers are installed on your system.</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> gEDA/gaf, as well as the gEDA-allied programs have certain dependencies. These are libraries and other programs which must be present on your system to build and run gEDA successfully. When trying to install gEDA, you may find that you need to install other, seemingly unrelated programs first. If you find you are missing dependencies during the installation process don't despair! Overcoming any dependency issue is a simple matter of installing the required program or library. </div>
+</li>
+</ul>
+
+</div>
+<!-- EDIT1414 SECTION "README" [25-1435] -->
+<h2 class="sectionedit1415"><a name="distribution_packages_binaries" id="distribution_packages_binaries">Distribution Packages / Binaries</a></h2>
+<div class="level2">
+<div class="table sectionedit1416"><table class="inline">
+ <tr class="row0">
+ <th class="col0"> Linux Distro </th><th class="col1"> Installation method </th><th class="col2"> Install files </th><th class="col3"> Creator/maintainer </th><th class="col4"> Comment </th>
+ </tr>
+ <tr class="row1">
+ <td class="col0 leftalign"> SuSE </td><td class="col1"> yast </td><td class="col2"> <a href="http://download.opensuse.org/repositories/science/"; class="urlextern" title="http://download.opensuse.org/repositories/science/"; rel="nofollow"> RPMs </a> </td><td class="col3"> Werner Hoch </td><td class="col4"> </td>
+ </tr>
+ <tr class="row2">
+ <td class="col0"> Debian </td><td class="col1"> apt-get install geda </td><td class="col2"> <a href="http://packages.debian.org/search?keywords=geda"; class="urlextern" title="http://packages.debian.org/search?keywords=geda"; rel="nofollow"> .deb files </a> </td><td class="col3"> Hamish Moffatt </td><td class="col4"> Download .debs appropriate for the maturity level of your distro (stable, testing, etc.) </td>
+ </tr>
+ <tr class="row3">
+ <td class="col0"> Mac OSX </td><td class="col1"> </td><td class="col2"> <a href="http://www.ghz.cc/charles/fink/"; class="urlextern" title="http://www.ghz.cc/charles/fink/"; rel="nofollow"> fink packages </a> </td><td class="col3"> Charles Lepple </td><td class="col4"> Instructions provided in the <a href="http://www.ghz.cc/charles/fink"; class="urlextern" title="http://www.ghz.cc/charles/fink"; rel="nofollow"> here </a> </td>
+ </tr>
+</table></div>
+<!-- EDIT1416 TABLE [1482-2041] -->
+</div>
+<!-- EDIT1415 SECTION "Distribution Packages / Binaries" [1436-2043] -->
+<h2 class="sectionedit1417"><a name="sources" id="sources">Sources</a></h2>
+<div class="level2">
+<div class="table sectionedit1418"><table class="inline">
+ <tr class="row0">
+ <th class="col0"> Name </th><th class="col1"> Notes </th><th class="col2"> Tarball </th><th class="col3"> Description </th>
+ </tr>
+ <tr class="row1">
+ <td class="col0"> gEDA/gaf (stable) </td><td class="col1"> <a href="http://geda.seul.org/release/v1.6/1.6.1/geda-gaf-1.6.1-releasenotes.html"; class="urlextern" title="http://geda.seul.org/release/v1.6/1.6.1/geda-gaf-1.6.1-releasenotes.html"; rel="nofollow"> Release Notes </a> <a href="http://geda.seul.org/release/v1.6/1.6.1/geda-gaf-1.6.1-README.txt"; class="urlextern" title="http://geda.seul.org/release/v1.6/1.6.1/geda-gaf-1.6.1-README.txt"; rel="nofollow"> README </a> </td><td class="col2"> <a href="http://geda.seul.org/release/v1.6/1.6.1/geda-gaf-1.6.1.tar.gz"; class="urlextern" title="http://geda.seul.org/release/v1.6/1.6.1/geda-gaf-1.6.1.tar.gz"; rel="nofollow"> 1.6.1-20100214 </a> </td><td class="col3"> Schematic capture, netlister, symbols, symbol checker, and utils </td>
+ </tr>
+ <tr class="row2">
+ <td class="col0"> PCB </td><td class="col1"> <a href="http://archives.seul.org/geda/user/Sep-2010/msg00724.html"; class="urlextern" title="http://archives.seul.org/geda/user/Sep-2010/msg00724.html"; rel="nofollow"> Announcement </a> </td><td class="col2"> <a href="http://geda.seul.org/dist/pcb-20100929.tar.gz"; class="urlextern" title="http://geda.seul.org/dist/pcb-20100929.tar.gz"; rel="nofollow"> 20100929 </a> </td><td class="col3"> Printed Circuit Board layout tool </td>
+ </tr>
+ <tr class="row3">
+ <td class="col0"> gerbv </td><td class="col1"> <a href="http://gerbv.gpleda.org/ANNOUNCEMENT-2.3.0"; class="urlextern" title="http://gerbv.gpleda.org/ANNOUNCEMENT-2.3.0"; rel="nofollow"> Announcement </a> </td><td class="col2"> <a href="http://geda.seul.org/dist/gerbv-2.4.0.tar.gz"; class="urlextern" title="http://geda.seul.org/dist/gerbv-2.4.0.tar.gz"; rel="nofollow"> 2.4.0 </a> </td><td class="col3"> Gerber file viewer </td>
+ </tr>
+ <tr class="row4">
+ <td class="col0"> xgsch2pcb </td><td class="col1"> <a href="http://www.seul.org/pipermail/geda-announce/2009-December/000093.html"; class="urlextern" title="http://www.seul.org/pipermail/geda-announce/2009-December/000093.html"; rel="nofollow"> Announcement </a> </td><td class="col2"><a href="http://geda.seul.org/dist/geda-xgsch2pcb-0.1.3.tar.gz"; class="urlextern" title="http://geda.seul.org/dist/geda-xgsch2pcb-0.1.3.tar.gz"; rel="nofollow"> 0.1.3 </a> </td><td class="col3">Graphical front-end for the gschem â?? pcb workflow </td>
+ </tr>
+ <tr class="row5">
+ <td class="col0"> gnucap </td><td class="col1"> </td><td class="col2"> <a href="http://www.gnucap.org/devel"; class="urlextern" title="http://www.gnucap.org/devel"; rel="nofollow"> devel </a> </td><td class="col3"> GPLed mixed-mode/mixed-level circuit simulator </td>
+ </tr>
+ <tr class="row6">
+ <td class="col0"> Icarus Verilog </td><td class="col1"> </td><td class="col2"> <a href="ftp://ftp.icarus.com/pub/eda/verilog/v0.9/"; class="urlextern" title="ftp://ftp.icarus.com/pub/eda/verilog/v0.9/"; rel="nofollow"> Stable </a> <a href="ftp://ftp.icarus.com/pub/eda/verilog/snapshots/"; class="urlextern" title="ftp://ftp.icarus.com/pub/eda/verilog/snapshots/"; rel="nofollow"> snapshots </a> </td><td class="col3 leftalign"> Verilog simulation and synthesis tool </td>
+ </tr>
+ <tr class="row7">
+ <td class="col0"> GSpiceUI </td><td class="col1"> </td><td class="col2"> <a href="http://sourceforge.net/projects/gspiceui/"; class="urlextern" title="http://sourceforge.net/projects/gspiceui/"; rel="nofollow"> Homepage </a> </td><td class="col3"> <acronym title="Graphical User Interface">GUI</acronym> Frontend to SPICE </td>
+ </tr>
+ <tr class="row8">
+ <td class="col0"> GTKWave </td><td class="col1"> </td><td class="col2"> <a href="http://gtkwave.sourceforge.net/"; class="urlextern" title="http://gtkwave.sourceforge.net/"; rel="nofollow"> Homepage </a> </td><td class="col3"> Electronic waveform viewer </td>
+ </tr>
+ <tr class="row9">
+ <td class="col0"> gwave </td><td class="col1"> </td><td class="col2"> <a href="http://gwave.sourceforge.net/"; class="urlextern" title="http://gwave.sourceforge.net/"; rel="nofollow"> Homepage </a> </td><td class="col3"> Analog waveform viewer </td>
+ </tr>
+ <tr class="row10">
+ <td class="col0"> ngspice </td><td class="col1"> </td><td class="col2"> <a href="http://ngspice.sourceforge.net/download.html"; class="urlextern" title="http://ngspice.sourceforge.net/download.html"; rel="nofollow"> Download </a> </td><td class="col3"> An improved SPICE </td>
+ </tr>
+</table></div>
+<!-- EDIT1418 TABLE [2065-3707] -->
+</div>
+<!-- EDIT1417 SECTION "Sources" [2044-] --></body>
+</html>
diff --git a/docs/wiki/geda-eagle_pcb_netlister_readme.html b/docs/wiki/geda-eagle_pcb_netlister_readme.html
index 95a3fdc..ef0c394 100644
--- a/docs/wiki/geda-eagle_pcb_netlister_readme.html
+++ b/docs/wiki/geda-eagle_pcb_netlister_readme.html
@@ -12,9 +12,7 @@
<body>
-
-
-<h1><a name="eagle_pcb_netlister_readme" id="eagle_pcb_netlister_readme">Eagle PCB netlister README</a></h1>
+<h1 class="sectionedit276"><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
@@ -35,7 +33,6 @@ 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>
diff --git a/docs/wiki/geda-example_hsm.html b/docs/wiki/geda-example_hsm.html
index 9068295..18dc930 100644
--- a/docs/wiki/geda-example_hsm.html
+++ b/docs/wiki/geda-example_hsm.html
@@ -12,15 +12,13 @@
<body>
-
-
-<h1><a name="hierarchical_spice_model" id="hierarchical_spice_model">Hierarchical SPICE model</a></h1>
+<h1 class="sectionedit278"><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.
+<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
@@ -127,8 +125,7 @@ gEDA lives at http://www.brorson.com/gEDA/SPICE
For inquiries or bug reports, please contact me:
Stuart Brorson
-mailto:sdb@xxxxxxxxxx
-</pre>
+mailto:sdb@xxxxxxxxxx</pre>
</div>
</body>
diff --git a/docs/wiki/geda-example_usbjtag.html b/docs/wiki/geda-example_usbjtag.html
index e1ff867..7517b9e 100644
--- a/docs/wiki/geda-example_usbjtag.html
+++ b/docs/wiki/geda-example_usbjtag.html
@@ -12,15 +12,13 @@
<body>
-
-
-<h1><a name="example_usb-based_jtag_interface" id="example_usb-based_jtag_interface">Example USB-based JTAG interface</a></h1>
+<h1 class="sectionedit280"><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.
+<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
============================
@@ -68,8 +66,7 @@ The distribution of the schematics of gTAG should consist of:
* 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>
+ - gschemrc - gschem specific and and calls commonrc</pre>
</div>
</body>
diff --git a/docs/wiki/geda-experiences.html b/docs/wiki/geda-experiences.html
index 45d8583..67c5915 100644
--- a/docs/wiki/geda-experiences.html
+++ b/docs/wiki/geda-experiences.html
@@ -12,9 +12,7 @@
<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>
+<h1 class="sectionedit282"><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>
@@ -38,11 +36,12 @@ I tried first the gEDA <acronym title="Graphical User Interface">GUI</acronym>,
</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.
+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>.
+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>
@@ -80,12 +79,13 @@ From the â??Tragesym tutorialâ??:
</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 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>
+
+<strong>Step2: Download the part data sheet and find the pin list</strong>
</p>
<p>
@@ -97,15 +97,17 @@ From the â??Tragesym tutorialâ??:
</ul>
<p>
- <strong>Step4: Insert all missing data into the spreadsheet</strong>
+
+<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 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>
+
+<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>
@@ -113,7 +115,8 @@ From the â??Tragesym tutorialâ??:
</ul>
<p>
- <strong>Step6: execute tragesym and create the symbol</strong>
+
+<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>
@@ -121,12 +124,13 @@ From the â??Tragesym tutorialâ??:
</ul>
<p>
- <strong>Step7: check the result with gschem and do some artwork</strong>
+
+<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 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/>
+<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>
@@ -137,18 +141,22 @@ cp 36-pin_centronics.sch /home/username/gEDA/gaf/gschem-sym/connectors/36-pin_ce
<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>
+
+<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.
+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=":-)" />
+
+<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>
+<!-- EDIT282 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
index 4df4505..c487c60 100644
--- a/docs/wiki/geda-faq-attribs.fr.html
+++ b/docs/wiki/geda-faq-attribs.fr.html
@@ -11,45 +11,17 @@
</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>
+<h1 class="sectionedit284"><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>
+<!-- EDIT284 SECTION "Génération de BOM (Bill Of Materials)" [1-55] -->
+<h2 class="sectionedit285"><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:
+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;
@@ -60,27 +32,28 @@ 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>
+<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 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?!?!?
+
+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>
+<!-- EDIT285 SECTION "J'ai créé un nouveau dessin. Comment je crée une BOM?" [56-1593] -->
+<h1 class="sectionedit286"><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>
+<!-- EDIT286 SECTION "DRC" [1594-1611] -->
+<h2 class="sectionedit287"><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>
@@ -88,7 +61,8 @@ Vous pouvez contrôler votre schéma en utilisant le programme de gnetlist drc2.
</p>
<p>
-Lancez le programme drc2 avec la commande suivante:
+Lancez le programme drc2 avec la commande suivante:
+
</p>
<pre class="code">gnetlist -g drc2 -o MyDesign.drc MyDesign.sch</pre>
@@ -97,12 +71,13 @@ Avec cette commande, la sortie DRC est écrite dans le ficheir «·MyDesign.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>
+<!-- EDIT287 SECTION "Comment je contrôle mes schémas?" [1612-2221] -->
+<h2 class="sectionedit288"><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:
+Lancez drc2 avec la commande suivante:
+
</p>
<pre class="code">gnetlist -g drc2 -o - MyDesign.sch</pre>
@@ -111,12 +86,12 @@ 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>
+<!-- EDIT288 SECTION "Comment je peux voir la sortie de DRC à l'écran, sans l'écrire dans un fichier?" [2222-2480] -->
+<h2 class="sectionedit289"><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.
+drc2 est hautement configurable. Vous devez placer quelques commandes spéciales dans un fichier et utiliser l'option «·-l·» de gnetlist.
</p>
<p>
@@ -152,11 +127,13 @@ Les commandes les plus habituelles sont:
</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.
+
+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:
+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>
@@ -165,34 +142,37 @@ Avec cette commande, la sortie de DRC est écrite dans un ficheir «·MyDesign.d
</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>
+<!-- EDIT289 SECTION "Je veux désactiver quelque uns des contrôles de DRC du schéma. Comment faire?" [2481-4415] -->
+<h2 class="sectionedit290"><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:
+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:
+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.
+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>
+<!-- EDIT290 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 class="sectionedit291"><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·»:
+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>
@@ -201,17 +181,17 @@ 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>
+<!-- EDIT291 SECTION "Il y a quelques avertissements sur mon schéma que je connais. Puis-je les ignorer dans la return value?" [5139-5464] -->
+<h1 class="sectionedit292"><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>
+<!-- EDIT292 SECTION "Gestion d'attribut" [5465-5498] -->
+<h2 class="sectionedit293"><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:
+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>
@@ -219,22 +199,23 @@ Ici, la réponse est lâ??utilitaire de gEDA/gaf, «·gattrib·». Gattrib est un
</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.
+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é.
+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>
+<!-- EDIT293 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 class="sectionedit294"><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>.
+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>
+<!-- EDIT294 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
index 2fcd29a..de5e14f 100644
--- a/docs/wiki/geda-faq-attribs.html
+++ b/docs/wiki/geda-faq-attribs.html
@@ -11,247 +11,13 @@
</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>
+<h1 class="sectionedit299"><a name="attribute_management" id="attribute_management">Attribute management</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>
+<!-- EDIT299 SECTION "Attribute management" [3-38] -->
+<h2 class="sectionedit300"><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>
@@ -271,14 +37,15 @@ When using gattrib, make sure you exit gschem first. Gattrib and gschem both sav
</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>
+<!-- EDIT300 SECTION "Help! My design has hundreds of components, and it's a pain to use gschem to attach all my attributes!" [39-1208] -->
+<h2 class="sectionedit301"><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>.
+<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>
+<!-- EDIT301 SECTION "How do I know what footprint name to use for layout using PCB?" [1209-] --></body>
</html>
diff --git a/docs/wiki/geda-faq-gnetlist.fr.html b/docs/wiki/geda-faq-gnetlist.fr.html
index 260a236..9f5940b 100644
--- a/docs/wiki/geda-faq-gnetlist.fr.html
+++ b/docs/wiki/geda-faq-gnetlist.fr.html
@@ -11,82 +11,73 @@
</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>
+<h1 class="sectionedit303"><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>
+<!-- EDIT303 SECTION "Problèmes avec gnetlist lors de l'installation/exécution" [1-73] -->
+<h2 class="sectionedit304"><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:
+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:
+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;
+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>
+<!-- EDIT304 SECTION "la bom de gnetlist ne fonctionne pas. D'où vient le problème?" [74-654] -->
+<h2 class="sectionedit305"><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:
+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):
+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.
+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>
+<!-- EDIT305 SECTION "Quelques unes des commandes de gnetlist débordent la pile. Comment je résoud ce problème?" [655-1562] -->
+<h2 class="sectionedit306"><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:
+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:
+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>
@@ -94,13 +85,14 @@ Ce qui sâ??est produit est que gnetlist (libgeda en fait) a créé deux nets au
</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:
+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>
+<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>
+<!-- EDIT306 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
index 078f1f7..713bdae 100644
--- a/docs/wiki/geda-faq-gnetlist.html
+++ b/docs/wiki/geda-faq-gnetlist.html
@@ -11,36 +11,232 @@
</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>
+<h1 class="sectionedit308"><a name="gnetlist" id="gnetlist">Gnetlist</a></h1>
+<div class="level1">
+
+</div>
+<!-- EDIT308 SECTION "Gnetlist" [1-28] -->
+<h1 class="sectionedit309"><a name="bill_of_materials_bom_generation" id="bill_of_materials_bom_generation">Bill of Materials (BOM) Generation</a></h1>
+<div class="level1">
+
+<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>
-<h1><a name="gnetlist_build_run-time_problems" id="gnetlist_build_run-time_problems">Gnetlist build/run-time problems</a></h1>
+</div>
+<!-- EDIT309 SECTION "Bill of Materials (BOM) Generation" [29-2012] -->
+<h1 class="sectionedit310"><a name="design_rule_check_drc" id="design_rule_check_drc">Design Rule Check (DRC)</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>
+<!-- EDIT310 SECTION "Design Rule Check (DRC)" [2013-2050] -->
+<h2 class="sectionedit311"><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>
- Starting with Fedorea Core 6 and SuSE 10.2, many users have reported an error which looks like this:
+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>
+<!-- EDIT311 SECTION "How do I check my schematics?" [2051-2555] -->
+<h2 class="sectionedit312"><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>
-<pre class="code">
-$gnetlist -g spice-sdb -o TwoStageAmp.cir TwoStageAmp.sch
+
+</div>
+<!-- EDIT312 SECTION "How do I see the DRC output in the screen, without writing to a file?" [2556-2799] -->
+<h2 class="sectionedit313"><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>
+<!-- EDIT313 SECTION "I want to disable some of the schematic DRC checks. How can I do it?" [2800-4628] -->
+<h2 class="sectionedit314"><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>
+<!-- EDIT314 SECTION "Can I include the DRC checking into a Makefile and stop when errors or warnings are found?" [4629-5306] -->
+<h2 class="sectionedit315"><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>
+<!-- EDIT315 SECTION "There are some warnings in my design I'm aware of. Can I ignore the warnings in the return value?" [5307-5617] -->
+<h1 class="sectionedit316"><a name="gnetlist_build_run-time_problems" id="gnetlist_build_run-time_problems">Gnetlist build/run-time problems</a></h1>
+<div class="level1">
+
+</div>
+<!-- EDIT316 SECTION "Gnetlist build/run-time problems" [5618-5665] -->
+<h2 class="sectionedit317"><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.
@@ -54,8 +250,7 @@ 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>
+ERROR: Unbound variable: spice-sdb</pre>
<p>
Several gnetlist backends evince this problem, including spice-sdb and drc2.
@@ -66,24 +261,27 @@ This is a bug in guile-1.8.X. The gEDA developers are working on a fix. Meanwh
</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>
+<!-- EDIT317 SECTION "I get a parenthesis mismatch error when running gnetlist. What's up?" [5666-6932] -->
+<h2 class="sectionedit318"><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:
+If when running gnetlist like this:
+
</p>
<pre class="code">gnetlist -g bom filename.sch</pre>
<p>
-and gnetlist outputs an error message like:
+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;
+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>
@@ -93,17 +291,19 @@ For information about BOM generation see the <a href="geda-faq-attribs.html#bom_
</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>
+<!-- EDIT318 SECTION "The gnetlist bom backend does not work. What is wrong?" [6933-7549] -->
+<h2 class="sectionedit319"><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:
+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):
+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>
@@ -113,12 +313,13 @@ If this does not work, then edit the appropriate backend (usually named: gnet-ba
</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>
+<!-- EDIT319 SECTION "Some gnetlist backends overflow the stack. How do I solve this?" [7550-8355] -->
+<h2 class="sectionedit320"><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:
+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>
@@ -136,9 +337,10 @@ The developers are debating whether or not this is a bug in gnetlist, but for no
</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>
+<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>
+<!-- EDIT320 SECTION "gnetlist has created a netlist with duplicate pins!?" [8356-] --></body>
</html>
diff --git a/docs/wiki/geda-faq-gsch2pcb.fr.html b/docs/wiki/geda-faq-gsch2pcb.fr.html
index f78f399..016024b 100644
--- a/docs/wiki/geda-faq-gsch2pcb.fr.html
+++ b/docs/wiki/geda-faq-gsch2pcb.fr.html
@@ -11,46 +11,33 @@
</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>
+<h1 class="sectionedit322"><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>
+<!-- EDIT322 SECTION "gsch2pcb" [1-24] -->
+<h2 class="sectionedit323"><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>
+
+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.
+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>
+<!-- EDIT323 SECTION "Où est le tutoriel gsch2pcb?" [25-436] -->
+<h2 class="sectionedit324"><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:
+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>
@@ -58,7 +45,8 @@ gsch2pcb est une part de gEDA/gaf, dans les utils. Il est normalement installé
</ul>
<p>
- ou le prendre directement depuis le <acronym title="Concurrent Versions System">CVS</acronym> sur:
+
+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>
@@ -66,14 +54,15 @@ gsch2pcb est une part de gEDA/gaf, dans les utils. Il est normalement installé
</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>
+<!-- EDIT324 SECTION "Où puis-je télécharger gsch2pcb?" [437-905] -->
+<h2 class="sectionedit325"><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.
+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>
+<!-- EDIT325 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
index 8531b3b..a0f6b40 100644
--- a/docs/wiki/geda-faq-gsch2pcb.html
+++ b/docs/wiki/geda-faq-gsch2pcb.html
@@ -11,42 +11,41 @@
</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>
+<h1 class="sectionedit327"><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>
+<!-- EDIT327 SECTION "gsch2pcb" [1-24] -->
+<h2 class="sectionedit328"><a name="overview" id="overview">Overview</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>.
+gsch2pcb is a shell script that will automate the process of moving a design from gschem to PCB. It takes the footprint and part value information from your schematic (or set of schematics) and runs them thru the netlister. The end result is a set of files that, in PCB, are the basics of your design: the part footprints, the netlist that shows all of the connections from one part to another, the physical circuit board and whatever other physical information you included in your schematic as graphical objects (like board outlines).
</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.
+gsch2pcb is included in gEDA/gaf. It is installed by default with gEDA/gaf. Run it from the command line with ./gsch2pcb.
</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>
+<!-- EDIT328 SECTION "Overview" [25-709] -->
+<h2 class="sectionedit329"><a name="gsch2pcb_resources" id="gsch2pcb_resources">gsch2pcb Resources</a></h2>
+<div class="level2">
+<ul>
+<li class="level1"><div class="li"> Bill Wilson's gsch2pcb outstanding tutorial: <a href="geda-gsch2pcb_tutorial.html" class="wikilink1" title="geda-gsch2pcb_tutorial.html">tutorial</a>. </div>
+</li>
+<li class="level1"><div class="li"> sch2pcb wrapper script for gsch2pcb </div>
+</li>
+<li class="level1"><div class="li"> </div>
+</li>
+<li class="level1"><div class="li"> </div>
+</li>
+</ul>
+
+</div>
+<!-- EDIT329 SECTION "gsch2pcb Resources" [710-879] -->
+<h2 class="sectionedit330"><a name="where_can_i_download_gsch2pcb" id="where_can_i_download_gsch2pcb">Where can I download gsch2pcb?</a></h2>
<div class="level2">
<p>
@@ -58,7 +57,8 @@ gsch2pcb is part of gEDA/gaf, in the utils. It is normally installed by default
</ul>
<p>
- or grab it directly from git at:
+
+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>
@@ -66,8 +66,8 @@ gsch2pcb is part of gEDA/gaf, in the utils. It is normally installed by default
</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>
+<!-- EDIT330 SECTION "Where can I download gsch2pcb?" [880-1374] -->
+<h2 class="sectionedit331"><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>
@@ -75,17 +75,20 @@ Try running gsch2pcb in double verbose mode: â??gsch2pcb -v -vâ??. This will pro
</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>
+<!-- EDIT331 SECTION "gsch2pcb can't find some of my footprints, or errors out. What can I do to diagnose my problem?" [1375-1720] -->
+<h2 class="sectionedit332"><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:
+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:
+
+and the layer stack itself:
+
</p>
<pre class="code">(lambda (port)
(display "Layer(1 \"bottom\")\n(\n)\n" port)
@@ -97,9 +100,11 @@ Edit $INSTALLDIR/share/gEDA/scheme/gnet-gsch2pcb.scm to reflect your preferred l
(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.
+
+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>
+<!-- EDIT332 SECTION "I don't like the default layer stack of gschem2pcb. How can I change this?" [1721-] --></body>
</html>
diff --git a/docs/wiki/geda-faq-gschem.fr.html b/docs/wiki/geda-faq-gschem.fr.html
index 52b341f..4935eb4 100644
--- a/docs/wiki/geda-faq-gschem.fr.html
+++ b/docs/wiki/geda-faq-gschem.fr.html
@@ -11,68 +11,17 @@
</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>
+<h1 class="sectionedit334"><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>
+<!-- EDIT334 SECTION "Usage de Gschem" [1-33] -->
+<h2 class="sectionedit335"><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:
+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>
@@ -82,20 +31,21 @@ Ce nâ??est plus un problème·; déplacer un composant peut être réalisé en u
</ol>
<p>
- Câ??est probablement ce que vous avez lâ??habitude de faire.
+
+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:
+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 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 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>
@@ -105,9 +55,9 @@ Deux:
<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 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 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>
@@ -115,18 +65,18 @@ Deux:
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 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>
+<!-- EDIT335 SECTION "Comment je déplace un composant?" [34-1443] -->
+<h2 class="sectionedit336"><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 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>
@@ -138,65 +88,66 @@ Trois:
</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 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.)
+
+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>
+<!-- EDIT336 SECTION "Comment je change la taille du texte sur un symbole?" [1444-2401] -->
+<h2 class="sectionedit337"><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.
+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>
+<!-- EDIT337 SECTION "Comment dévérouiller un composant" [2402-2929] -->
+<h2 class="sectionedit338"><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):
+�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
+<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>
+(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.
+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>
+<!-- EDIT338 SECTION "Comment refdes peut-il être automatiquement numéroté lorsque je dessine un schéma?" [2930-3664] -->
+<h2 class="sectionedit339"><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.
+
+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.
+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>
+<!-- EDIT339 SECTION "Qu'est-ce qu'un bus et comment l'utiliser?" [3665-4273] -->
+<h2 class="sectionedit340"><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>
+<!-- EDIT340 SECTION "Que sont les Liaisons de Touches dans gschem?" [4274-4332] -->
+<h2 class="sectionedit341"><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>
@@ -205,34 +156,40 @@ Par défaut, vous avez:
<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 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:
+
+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:
+ou:
+
</p>
<pre class="code">(middle-button "stroke") ;draw mouse gestures/strokes (must install libstroke to enable</pre>
<p>
-ou:
+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:
+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:
+ou:
+
</p>
<pre class="code">(third-button "mousepan") ;use the mouse to pan around the schematic</pre>
@@ -241,47 +198,49 @@ Pour plus informations sur ces options, veuillez aller voir le fichier <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>
+<!-- EDIT341 SECTION "Quelles sont les liaisons avec la souris dans gschem?" [4333-5537] -->
+<h1 class="sectionedit342"><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>
+<!-- EDIT342 SECTION "Symboles gschem" [5538-5568] -->
+<h2 class="sectionedit343"><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.
+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).
+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:
+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>
+<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>
+<!-- EDIT343 SECTION "Quel est l'objet de cette polémique entre les symboles lourds et légers?" [5569-7909] -->
+<h2 class="sectionedit344"><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.
+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é.
+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>
+<!-- EDIT344 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 class="sectionedit345"><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>
@@ -297,19 +256,21 @@ Si vous voulez un symbole graphiquement complet (sans connexions électriques),
</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>
+<!-- EDIT345 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 class="sectionedit346"><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:
+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:
+Ajoutez à votre fichier gschemrc:
+
</p>
<pre class="code">(promote-invisible â??enabledâ??)</pre>
@@ -318,73 +279,77 @@ et vous verrez tous les attributs. Le mot « keep-invisible » gardera caché ce
</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>
+<!-- EDIT346 SECTION "Comment placer un un attribut de symbole invisible dans un schéma?" [9472-10132] -->
+<h2 class="sectionedit347"><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).
+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.
+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.
+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.
+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.
+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.
+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>
+<!-- EDIT347 SECTION "Que dois-je faire à propos des broches d'alimentation sur mon symbole: Les rendre visible (explicites) ou invisibles (implicites)?" [10133-13027] -->
+<h2 class="sectionedit348"><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>.
+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>
+<!-- EDIT348 SECTION "Existe-t-il une spécification ou un manuel pour créer les symboles gschem? Où est-il?" [13028-13190] -->
+<h1 class="sectionedit349"><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.
+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>
+<!-- EDIT349 SECTION "Configuration/personnalisation de gschem" [13191-13425] -->
+<h2 class="sectionedit350"><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
+Placez
+
</p>
<pre class="code">(text-size 10)</pre>
<p>
- dans votre gschemrc et replacez «·10·» avec votre taille favorite.
+
+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>
+<!-- EDIT350 SECTION "Comment changer la taille par défaut d'un texte flottant?" [13426-13605] -->
+<h2 class="sectionedit351"><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:
+
+�ditez le fichier system-gschemrc et au début du fichier, vous trouvezrez des lignes comme:
+
</p>
<pre class="code">;
; Start of color section
@@ -414,28 +379,31 @@ Avec les versions récentes de gscgem, vous pouvez aussi placer ceci dans gschem
<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>
+<!-- EDIT351 SECTION "Comment je peux avoir une couleur fond différente?" [13606-14819] -->
+<h1 class="sectionedit352"><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>
+<!-- EDIT352 SECTION "Impression/Sortie" [14820-14853] -->
+<h2 class="sectionedit353"><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.
+
+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):
+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:
+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
@@ -452,18 +420,20 @@ 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>
+<!-- EDIT353 SECTION "Comment imprimer les schémas depuis le ligne de commande?" [14854-16038] -->
+<h2 class="sectionedit354"><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):
+�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):
+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>
@@ -472,44 +442,49 @@ Les â??0 0 0â?? sont les composantes RGB (entre 0..1) pour la couleur de fond de
</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):
+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>.
+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>
+<!-- EDIT354 SECTION "Comment je peux sortie le postscript/PNG en couleurs?" [16039-17194] -->
+<h2 class="sectionedit355"><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:
+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:
+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>
+<!-- EDIT355 SECTION "Comment je peux avoir une sortie postscript/PNG en noir et blanc?" [17195-17592] -->
+<h2 class="sectionedit356"><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 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:
+
+Un exemple simple:
+
</p>
<pre class="code">\documentclass{article}
\usepackage{graphicx}
@@ -520,8 +495,8 @@ Pour les images <acronym title="Portable Network Graphics">PNG</acronym> en noir
\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>
+<!-- EDIT356 SECTION "Comment j'insère des schémas dans mon document LaTex?" [17593-18183] -->
+<h2 class="sectionedit357"><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>
@@ -529,45 +504,51 @@ gschem ne fournit pas cette fonctionnalité en interne; il existe néanmoins un
</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>
+<!-- EDIT357 SECTION "Comment je scinde un fichier postscript en plusieurs pages?" [18184-18554] -->
+<h1 class="sectionedit358"><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>
+<!-- EDIT358 SECTION "Problèmes d'installation/d'exécution de gschem" [18555-18618] -->
+<h2 class="sectionedit359"><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.
+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:
+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:
+bash:
+
</p>
<pre class="code">export G_SLICE=always-malloc</pre>
<p>
-csh:
+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>
+<!-- EDIT359 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 class="sectionedit360"><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:
+
+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:
+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.
@@ -580,27 +561,29 @@ Tried to get an invalid color: 7</pre>
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 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 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.
+
+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.
+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>
+<!-- EDIT360 SECTION "Après l'installation, gschem ne fonctionne pas!? Que ce qui a pu aller mal?" [19270-21459] -->
+<h2 class="sectionedit361"><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):
+
+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>
@@ -618,14 +601,17 @@ Aussi, quelques anciennes versions de gEDA/gaf ont quelques bogues lorsque les f
</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
+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é.
+
+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>
+<!-- EDIT361 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
index bc95071..5fedcb2 100644
--- a/docs/wiki/geda-faq-gschem.html
+++ b/docs/wiki/geda-faq-gschem.html
@@ -11,109 +11,33 @@
</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>
+<h1 class="sectionedit363"><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>
+<!-- EDIT363 SECTION "General" [1-24] -->
+<h2 class="sectionedit364"><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 class="level1"><div class="li"> See whether the issue is already in the <a href="https://bugs.launchpad.net/geda"; class="urlextern" title="https://bugs.launchpad.net/geda"; 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>
+<!-- EDIT364 SECTION "I found a bug! What can I do about it?" [25-918] -->
+<h1 class="sectionedit365"><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>
+<!-- EDIT365 SECTION "Gschem usage" [919-947] -->
+<h2 class="sectionedit366"><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>
@@ -121,12 +45,13 @@ The chooser dialog presents a list of captions of the library sections. Click on
</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>
+<!-- EDIT366 SECTION "There is no symbol in the chooser dialog!" [948-1224] -->
+<h2 class="sectionedit367"><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:
+
+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>
@@ -136,7 +61,8 @@ The chooser dialog presents a list of captions of the library sections. Click on
</ol>
<p>
- This is probably what you are already used to doing.
+
+This is probably what you are already used to doing.
</p>
<p>
@@ -154,7 +80,8 @@ One:
</ol>
<p>
- Two:
+
+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>
@@ -166,7 +93,8 @@ One:
</ol>
<p>
- Three:
+
+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>
@@ -182,8 +110,8 @@ One:
</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>
+<!-- EDIT367 SECTION "How do I move a component?" [1225-2659] -->
+<h2 class="sectionedit368"><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>
@@ -191,8 +119,8 @@ Type [or] to toggle this behaviour. That is, the â??oâ?? key followed by the â??
</p>
</div>
-<!-- SECTION "How do I move components without dragging a tail of connectet nets?" [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>
+<!-- EDIT368 SECTION "How do I move components without dragging a tail of connectet nets?" [2660-2945] -->
+<h2 class="sectionedit369"><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>
@@ -216,12 +144,13 @@ Type [or] to toggle this behaviour. That is, the â??oâ?? key followed by the â??
</ol>
<p>
- More generally, you can use this procedure to edit anything on a symbol. (Substitute â??Edit Textâ?? for your desired edit, of course.)
+
+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>
+<!-- EDIT369 SECTION "How do I change the size of the text on a symbol?" [2946-3737] -->
+<h2 class="sectionedit370"><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>
@@ -233,8 +162,8 @@ Note, on transfer to pcb, there will be no overline on the layout.The backslash
</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>
+<!-- EDIT370 SECTION "Is it possible to overline text in gschem?" [3738-4182] -->
+<h2 class="sectionedit371"><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>
@@ -242,35 +171,34 @@ When a component is locked it cannot be selected with the middle mouse button; h
</p>
</div>
-<!-- SECTION "How do I unlock a locked component" [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>
+<!-- EDIT371 SECTION "How do I unlock a locked component" [4183-4597] -->
+<h2 class="sectionedit372"><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):
+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
+<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>
+(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:
+<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
+<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>
+(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>
+<!-- EDIT372 SECTION "How can I get refdes automatically numbered when I draw a schematic?" [4598-5502] -->
+<h2 class="sectionedit373"><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.
+
+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>
@@ -278,8 +206,8 @@ Some users have found it helpful to organize their nets by incorporating a bus n
</p>
</div>
-<!-- SECTION "What is a Bus and how do I use it?" [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>
+<!-- EDIT373 SECTION "What is a Bus and how do I use it?" [5503-6058] -->
+<h2 class="sectionedit374"><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>
@@ -287,8 +215,8 @@ Key accels are determined by configuration files read on start-up. The default k
</p>
</div>
-<!-- SECTION "How can I change Key Bindings in gschem?" [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>
+<!-- EDIT374 SECTION "How can I change Key Bindings in gschem?" [6059-6485] -->
+<h2 class="sectionedit375"><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>
@@ -304,27 +232,33 @@ By default you get:
</ul>
<p>
- You can change the middle button by adding the following to a gschemrc file:
+
+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:
+or:
+
</p>
<pre class="code">(middle-button "stroke") ;draw mouse gestures/strokes (must install libstroke to enable</pre>
<p>
-or:
+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:
+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:
+or:
+
</p>
<pre class="code">(third-button "mousepan") ;use the mouse to pan around the schematic</pre>
@@ -333,8 +267,8 @@ For more information on these options, please see the <code>${install_prefix}/sh
</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>
+<!-- EDIT375 SECTION "What are the mouse bindings in gschem?" [6486-7569] -->
+<h2 class="sectionedit376"><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>
@@ -346,52 +280,58 @@ A <code>source=</code> attribute attached to the sub sheet symbol gives the path
</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.
+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>
+<!-- EDIT376 SECTION "Can gschem do hierarchical designs with sub sheets?" [7570-9312] -->
+<h2 class="sectionedit377"><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.
+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>
+<!-- EDIT377 SECTION "Can gschem do a hierarchy where the top-level symbol points to a multi-page schematic?" [9313-9620] -->
+<h2 class="sectionedit378"><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.
+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>
+<!-- EDIT378 SECTION "Can the hierarchy be setup in multiple directories?" [9621-9826] -->
+<h2 class="sectionedit379"><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.
+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.
+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>
+<!-- EDIT379 SECTION "How do I declare a global net" [9827-10562] -->
+<h2 class="sectionedit380"><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.
+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>
+<!-- EDIT380 SECTION "How can options and libraries be specific on subsheet level?" [10563-10780] -->
+<h2 class="sectionedit381"><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>
@@ -409,13 +349,29 @@ 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>
+<!-- EDIT381 SECTION "Are there limitations to hierarchy design?" [10781-11150] -->
+<h2 class="sectionedit382"><a name="the_log_window_in_gschem_bugs_me" id="the_log_window_in_gschem_bugs_me">The log window in gschem bugs me</a></h2>
+<div class="level2">
+
+<p>
+gschem's log window can be persuaded not to appear with this line in a gschemrc:
+
+</p>
+<pre class="code">(log-window "later")</pre>
+
+<p>
+
+You may put the line in $HOME/.gEDA/gschemrc , or in the project directory, or modify the file $INSTALLDIR/share/gEDA/system-schemrc to make it a system wide default.
+</p>
+
+</div>
+<!-- EDIT382 SECTION "The log window in gschem bugs me" [11151-11478] -->
+<h1 class="sectionedit383"><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>
+<!-- EDIT383 SECTION "gschem symbols" [11479-11510] -->
+<h2 class="sectionedit384"><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>
@@ -423,12 +379,13 @@ There is a website <a href="http://www.gedasymbols.org/"; class="urlextern" title
</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>.
+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>
+<!-- EDIT384 SECTION "Where do I find symbols beyond the default library?" [11511-12257] -->
+<h2 class="sectionedit385"><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>
@@ -456,21 +413,26 @@ GEDA/gaf, as default configured, uses light symbols, although it can be configur
</p>
</div>
-<!-- SECTION "What's this business about heavy vs. light symbols?" [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>
+<!-- EDIT385 SECTION "What's this business about heavy vs. light symbols?" [12258-14449] -->
+<h2 class="sectionedit386"><a name="i_am_loaded_a_symbol_from_the_library_how_come_it_is_not_aligned_to_the_grid" id="i_am_loaded_a_symbol_from_the_library_how_come_it_is_not_aligned_to_the_grid">I am loaded a symbol from the library. How come it is 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.
+The vast majority of symbols in the library is designed for 100 units grid. Maeke sure, your grid is set to 100 units. Choose â??Snap_Grid_Spacingâ?? in the options menu for a dialog to check and change the grid.
+</p>
+
+<p>
+The symbols in the symbol library, were contributed by users just like you. Some people use different grid settings than other people (e.g. 50 units rather than 100). If you discover a symbol which seems to be off the grid, try to reduce your grid spacing and move the hot spots of the pins so that they sit on the grid. Then revert to your preferred grid settings. In addition, you may send the corrected symbol to the <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">mailinglist geda-user</a>
</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.
+The symbols at <a href="http://www.gedasymbols.org"; class="urlextern" title="http://www.gedasymbols.org"; rel="nofollow"> gedasymbols.org</a> are even more adapted to the specific preference of their author.
+Yes, the gEDA docs strongly suggest that symbols use 100 units 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. That said, the vast majoriuty of symbols out there conform to the recommendation. 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>
+<!-- EDIT386 SECTION "I am loaded a symbol from the library. How come it is not aligned to the grid?" [14450-15727] -->
+<h2 class="sectionedit387"><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>
@@ -478,7 +440,7 @@ 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.
+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>
@@ -486,19 +448,21 @@ If you want an entire symbol to be graphical (no elec. connections) , add a â??g
</p>
</div>
-<!-- SECTION "Is there an explicit no connect symbol that I can/should place in the schematic to prevent gnetlist from thinking I've forgotten a connection?" [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>
+<!-- EDIT387 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?" [15728-16298] -->
+<h2 class="sectionedit388"><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:
+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:
+Add to your gafrc file:
+
</p>
<pre class="code">(promote-invisible "enabled")</pre>
@@ -507,8 +471,8 @@ and you will get all the attributes promoted. The â??keep-invisibleâ?? keyword w
</p>
</div>
-<!-- SECTION "How do I promote an invisible symbol attribute into the schematic?" [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>
+<!-- EDIT388 SECTION "How do I promote an invisible symbol attribute into the schematic?" [16299-16912] -->
+<h2 class="sectionedit389"><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>
@@ -536,17 +500,33 @@ That said, it may still be useful to detach the power pins from the functional p
</p>
</div>
-<!-- SECTION "What should I do about power pins on my symbols: Make them visible (explicit) or invisible (implicit)?" [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>
+<!-- EDIT389 SECTION "What should I do about power pins on my symbols: Make them visible (explicit) or invisible (implicit)?" [16913-19169] -->
+<h2 class="sectionedit390"><a name="is_it_possible_to_have_zero_length_pins" id="is_it_possible_to_have_zero_length_pins">Is it possible to have zero length pins?</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>.
+You can set both ends of the pin to the same coordinate. This will give you a pure red marker without a pin extending from it. Currently, the <acronym title="Graphical User Interface">GUI</acronym> won't let you draw such a pin. Append the following line to a symbol file in a file editor:
+
+</p>
+<pre class="code">P 100 100 100 100 1 0 0</pre>
+
+<p>
+
+This is a zero size pin at the bottom left of the canvas. You can move it around, attach attributes, or copy it like any other pin. Unattached, it looks like a little red flag, while with a net attached it disappears. Gnetlist has no trouble treating it as a pin.
</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>
+<!-- EDIT390 SECTION "Is it possible to have zero length pins?" [19170-19764] -->
+<h2 class="sectionedit391"><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="http://geda.seul.org/wiki/geda:gschem_symbol_creation"; class="urlextern" title="http://geda.seul.org/wiki/geda:gschem_symbol_creation"; rel="nofollow">Symbol Creation Guide</a>.
+</p>
+
+</div>
+<!-- EDIT391 SECTION "Is there a specification or manual for creating gschem symbols? Where is it?" [19765-19951] -->
+<h2 class="sectionedit392"><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>
@@ -558,29 +538,78 @@ One of the major contributors to the project wrote his own symbol creation scrip
</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>
+<!-- EDIT392 SECTION "Is there a symbol wizard in gschem?" [19952-20483] -->
+<h2 class="sectionedit393"><a name="how_do_i_move_the_diamond_of_a_footprint" id="how_do_i_move_the_diamond_of_a_footprint">How do I move the diamond of a footprint</a></h2>
<div class="level2">
<p>
-Yes, symbols can contain symbols and nets.
+The origin of a footprint is marked with a little diamond. To move it to some other position relative to the footprint you have to modify all coordinates. This can be done manually with a texteditor. If you want to do it from wihtin the <acronym title="Graphical User Interface">GUI</acronym>, you need to break the footprint into pieces and assemble it again:
</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 class="level1"><div class="li"> open a new layout</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 class="level1"><div class="li"> open the footprint chooser (accel key: [i])</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 class="level1"><div class="li"> select the footprint to be modified</div>
</li>
-<li class="level1"><div class="li"> Save the sub circuit as a *.sym file in your local library. </div>
+<li class="level1"><div class="li"> from the buffer menu do break_buffer_elements_to_pieces</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 class="level1"><div class="li"> click somewhere on the canvas to place the pieces</div>
+</li>
+<li class="level1"><div class="li"> select all pieces by dragging with the mouse</div>
+</li>
+<li class="level1"><div class="li"> position the mouse cursor where the diamond shall be</div>
+</li>
+<li class="level1"><div class="li"> cut the pieces to buffer (accel key [ctrl-x])</div>
+</li>
+<li class="level1"><div class="li"> from the buffer menu do convert_buffer_to_element</div>
+</li>
+<li class="level1"><div class="li"> click somewhere on the canvas to place the footprint. It should have the diamond on the right position.</div>
+</li>
+<li class="level1"><div class="li"> regenerate the information of the footprint that got lost during the process: </div>
+<ol>
+<li class="level2"><div class="li"> pin and pad numbers â??> do [n] on pins and pads</div>
+</li>
+<li class="level2"><div class="li"> square flags â??> do [q] on pins and pads</div>
+</li>
+<li class="level2"><div class="li"> proper solder mask clearance:</div>
+<ol>
+<li class="level3"><div class="li"> activate the solder mask layer</div>
+</li>
+<li class="level3"><div class="li"> go over every pad/pin and type [ctrl-k] twice. This will decrement the size of the hole in the solder mask</div>
+</li>
+<li class="level3"><div class="li"> deactivate the solder mask layer</div>
</li>
</ol>
+</li>
+<li class="level2"><div class="li"> position of the text associated with the footprint:</div>
+<ol>
+<li class="level3"><div class="li"> type [n] somewhere inside the footprint where no pins or pads are</div>
+</li>
+<li class="level3"><div class="li"> type an arbitrary string in the dialog â??> click ok</div>
+</li>
+<li class="level3"><div class="li"> move the string to the desired posion</div>
+</li>
+</ol>
+</li>
+</ol>
+</li>
+<li class="level1"><div class="li"> select the footprint (click on footprint)</div>
+</li>
+<li class="level1"><div class="li"> cut the footprint to buffer ([ctrl-x]). Mouse cursor position does not matter at this step.</div>
+</li>
+<li class="level1"><div class="li"> from the buffer menu: save_buffer to_file</div>
+</li>
+</ol>
+
+<p>
+
+Yes, this is tedious. The reason for it is the lack of a real footprint editing mode in pcb.
+</p>
</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>
+<!-- EDIT393 SECTION "How do I move the diamond of a footprint" [20484-22324] -->
+<h2 class="sectionedit394"><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>
@@ -588,8 +617,34 @@ Unlike many other EDA software, the format of gschem is strictly human readable
</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>
+<!-- EDIT394 SECTION "Where can I find information on gschems file format?" [22325-22641] -->
+<h2 class="sectionedit395"><a name="why_are_symbols_so_big" id="why_are_symbols_so_big">Why are symbols so big?</a></h2>
+<div class="level2">
+
+<p>
+There is nothing in gschem that defines the absolute size of objects. The only connection to real world units is the file name of the various title blocks. For some long forgotten reason, the frame of the title block symbols named â??title-A4.symâ??, or â??title-B.symâ?? can contain only relatively simple circuits made of the symbols in the default library. If you'd like to put a frame around more complex circuits just choose a title page symbol that fits.
+</p>
+
+<p>
+When printing, gschem scales the output so that everything fits within the desired paper format. This paper format is completely independent of the title page symbol used in the schematic. So there is no need to scale the symbols themselves to make them fit a particular paper size.
+Most people prefer to use title-A2.sym or title-A3.sym when printing to A4 sized paper. Some use title block symbols with no frame at all and draw a rectangle as needed (e.g. <a href="http://www.gedasymbols.org/user/kai_martin_knaak/symbols/titleblock/title-block.sym"; class="urlextern" title="http://www.gedasymbols.org/user/kai_martin_knaak/symbols/titleblock/title-block.sym"; rel="nofollow">title-block.sym</a> by Kai-Martin Knaak).
+</p>
+
+<p>
+That said, there may be circumstances where you actually want scaled symbols. There is a number of options to achieve this:
+</p>
+<ul>
+<li class="level1"><div class="li"> DJ Delorie contributed a pearl script called <a href="http://www.gedasymbols.org/user/dj_delorie/tools/scale-schematic"; class="urlextern" title="http://www.gedasymbols.org/user/dj_delorie/tools/scale-schematic"; rel="nofollow">scale-schematic</a> on his pages in <a href="geda-glossary.html" class="wikilink1" title="geda-glossary.html">gedasymbols.org</a>.</div>
+</li>
+<li class="level1"><div class="li"> Build your own library of symbols. This is not that far off, since many people end-up using exclusively their own symbols anyway.</div>
+</li>
+<li class="level1"><div class="li"> Wojciech Kazubski maintains a package of small gEDA symbols at <a href="http://www.sp5pbe.waw.pl/~sp5smk/my-gaf-pcb.html"; class="urlextern" title="http://www.sp5pbe.waw.pl/~sp5smk/my-gaf-pcb.html"; rel="nofollow">http://www.sp5pbe.waw.pl</a></div>
+</li>
+</ul>
+
+</div>
+<!-- EDIT395 SECTION "Why are symbols so big?" [22642-24307] -->
+<h1 class="sectionedit396"><a name="gschem_configuration_customization" id="gschem_configuration_customization">Gschem configuration/customization</a></h1>
<div class="level1">
<p>
@@ -597,8 +652,8 @@ Gschem is configurable in more ways than can be describe here. Look at â??system
</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>
+<!-- EDIT396 SECTION "Gschem configuration/customization" [24308-24486] -->
+<h2 class="sectionedit397"><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>
@@ -617,28 +672,30 @@ gschem myschematic.sch</pre>
</ol>
<p>
- Points to remember:
+
+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 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 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>
+<!-- EDIT397 SECTION "How do I configure my local gafrc to find my local symbol directory?" [24487-25740] -->
+<h2 class="sectionedit398"><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:
+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"))
@@ -646,83 +703,144 @@ Currently (v1.3.1) gschem does not descend into subdirectories of the symbol lib
(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>
+<!-- EDIT398 SECTION "Can gafrc use a variable to set the root of my library?" [25741-26357] -->
+<h2 class="sectionedit399"><a name="can_the_library_path_contain_environment_variables" id="can_the_library_path_contain_environment_variables">Can the library path contain environment variables?</a></h2>
<div class="level2">
<p>
-Put a localized version of the following lines in a gafrc.
+Use <code>getenv â??ENVâ??</code> to refer to the environment variable ENV inside the scheme stanzas of gafrc lines:
+
+</p>
+<pre class="code">; Define a path to the local repository:
+(define symbolspath (build-path (getenv "HOME") "geda" "symbols"))
+; Use the path to point to a specific component-library:
+(component-library (build-path symbolspath "analog"))</pre>
+
+<p>
+An alternative syntax is <code>${ENV}</code>:
+
</p>
-<pre class="code">
-; empty the library path and populate it with local paths
+<pre class="code">(component-library "${HOME}/geda/symbols/analog")</pre>
+
+</div>
+<!-- EDIT399 SECTION "Can the library path contain environment variables?" [26358-26860] -->
+<h2 class="sectionedit400"><a name="is_there_a_way_to_give_a_library_a_name_that_differs_from_its_directory" id="is_there_a_way_to_give_a_library_a_name_that_differs_from_its_directory">Is there a way to give a library a name that differs from its directory?</a></h2>
+<div class="level2">
+
+<p>
+Add a third argument to the component-library stanza in gafrc, e.g.:
+
+</p>
+<pre class="code">(component-library "/home/comp/sch_symbols/AutoGen/Panasonic/0603/1P" "Panasonic 0603 1P")</pre>
+
+</div>
+<!-- EDIT400 SECTION "Is there a way to give a library a name that differs from its directory?" [26861-27121] -->
+<h2 class="sectionedit401"><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>
+<!-- EDIT401 SECTION "Can my local library cover frequently needed sub circuits?" [27122-27867] -->
+<h2 class="sectionedit402"><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>
+(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.
+
+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>
+<!-- EDIT402 SECTION "The library window is cluttered with default symbols. Can I restrict to my local lib?" [27868-28559] -->
+<h2 class="sectionedit403"><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
+Put
+
</p>
<pre class="code">(text-size 10)</pre>
<p>
- into your gschemrc and replace â??10â?? with your favorite size.
+
+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>
+<!-- EDIT403 SECTION "How can I change the default size of floating text?" [28560-28722] -->
+<h2 class="sectionedit404"><a name="can_i_have_light_background_color_please" id="can_i_have_light_background_color_please">Can I have light background color, please?</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>
+Put this line in a gschemrc file at a place where gschem looks at start-up:
-<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>
+<pre class="code">(load (build-path geda-rc-path "gschem-colormap-lightbg"))</pre>
<p>
-Note, starting with version 1.2 of gschem the syntax of this line changed to
+Note, this syntax is valid for recent versions of gschem (>2009). Older versions need a line like
+
</p>
-<pre class="code">(load (build-path geda-rc-path "gschem-lightbg")) ; light background</pre>
+<pre class="code">(load (build-path geda-rc-path "gschem-colormap-lightbg")) </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.
+
+Even older versions before 1.2 needed this line:
+
</p>
+<pre class="code">(load (string-append gedadatarc "/gschem-lightbg")) </pre>
+
+</div>
+<!-- EDIT404 SECTION "Can I have light background color, please?" [28723-29216] -->
+<h2 class="sectionedit405"><a name="how_can_i_tweak_colors_in_gschem" id="how_can_i_tweak_colors_in_gschem">How can I tweak colors in gschem?</a></h2>
+<div class="level2">
<p>
-A dark background is preferred by many users.
+Currently, there is no <acronym title="Graphical User Interface">GUI</acronym> to tweak the colors of gschem interactively. However, you can set them in a RC file.
</p>
+<ol>
+<li class="level1"><div class="li"> Copy the file <code>gschem-colormap-lightbg</code> or<code>gschem-colormap-darkbg</code> to <code>$HOME/.gEDA/mycolors</code> directory.</div>
+</li>
+<li class="level1"><div class="li"> Edit the settings in <code>.gEDA/mycolors</code> to please your taste.</div>
+</li>
+<li class="level1"><div class="li"> Add this line to your <code>gschemrc</code>:</div>
+</li>
+</ol>
+<pre class="code">(load (build-path (getenv "HOME") ".gEDA" "gschemcolor"))</pre>
</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>
+<!-- EDIT405 SECTION "How can I tweak colors in gschem?" [29217-29667] -->
+<h2 class="sectionedit406"><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:
+In the system-gschemrc file, you will find the following section:
+
</p>
-<pre class="code">
-; log-window string
+<pre class="code">; log-window string
;
; Controls if the log message window is mapped when gschem is started up
; Possible options:
@@ -734,32 +852,52 @@ In the system-gschemrc file, you will find the following section:
;(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:
+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>
+<p>
+If you want to see the logging messages on stdout instead of the log window, put this line in your gschemrc file:
+
+</p>
+<pre class="code">(logging-destination "tty")</pre>
+
+</div>
+<!-- EDIT406 SECTION "Each time I start gschem, the log message window is shown. Can I disable it?" [29668-30485] -->
+<h2 class="sectionedit407"><a name="is_there_a_way_to_disable_logging_to_home_geda_log" id="is_there_a_way_to_disable_logging_to_home_geda_log">Is there a way to disable logging to $HOME/.gEDA/log/ ?</a></h2>
+<div class="level2">
+
+<p>
+Put this line in your gschemrc file:
+
+</p>
+<pre class="code">(logging "disabled")</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>
+<!-- EDIT407 SECTION "Is there a way to disable logging to $HOME/.gEDA/log/ ?" [30486-30625] -->
+<h2 class="sectionedit408"><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:
+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.
+
+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>
+<!-- EDIT408 SECTION "Can I get a customized title block with new schematics?" [30626-30878] -->
+<h1 class="sectionedit409"><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>
+<!-- EDIT409 SECTION "Printing/Output" [30879-30909] -->
+<h2 class="sectionedit410"><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>
@@ -767,12 +905,14 @@ Running the script <strong><code>print.scm</code></strong> will create the Posts
</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):
+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:
+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
@@ -789,27 +929,31 @@ do
done</pre>
<p>
-The default printing size is used when printing from the command line. To set the default printing size to A4 add
+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>.
+
+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-26444] -->
-<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>
+<!-- EDIT410 SECTION "How do I print schematics from the command line?" [30910-32201] -->
+<h2 class="sectionedit411"><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):
+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):
+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>
@@ -818,7 +962,8 @@ The â??0 0 0â?? is the RGB components (between 0..1) for the background color of
</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):
+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>
@@ -832,23 +977,25 @@ From version 1.5.2 onwards, print and display color maps are separate. In order
<pre class="code">(load (build-path geda-rc-path "print-colormap-lightbg"))</pre>
</div>
-<!-- SECTION "How can I get color postscript/PNG output?" [26445-27815] -->
-<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>
+<!-- EDIT411 SECTION "How can I get color postscript/PNG output?" [32202-33572] -->
+<h2 class="sectionedit412"><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:
+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:
+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?" [27816-28181] -->
-<h2><a name="how_can_i_produce_pdf_output" id="how_can_i_produce_pdf_output">How can I produce PDF output?</a></h2>
+<!-- EDIT412 SECTION "How can I get black and white postscript/PNG output?" [33573-33938] -->
+<h2 class="sectionedit413"><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>
@@ -862,26 +1009,31 @@ There are different ways to produce <acronym title="Portable Document Format">PD
</ol>
<p>
- The second option is more convenient, but needs a little more administration.
+
+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:
+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.
+
+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:
+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?" [28182-29154] -->
-<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>
+<!-- EDIT413 SECTION "How can I produce PDF output?" [33939-34911] -->
+<h2 class="sectionedit414"><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>
@@ -893,7 +1045,9 @@ In a KDE environment the print command is â??kprinterâ?? with the output option
</ol>
<p>
- A simple example:
+
+A simple example:
+
</p>
<pre class="code">\documentclass{article}
\usepackage{graphicx}
@@ -904,8 +1058,8 @@ In a KDE environment the print command is â??kprinterâ?? with the output option
\end{document}</pre>
</div>
-<!-- SECTION "How can I insert schematics into my LaTex document?" [29155-29723] -->
-<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>
+<!-- EDIT414 SECTION "How can I insert schematics into my LaTex document?" [34912-35480] -->
+<h2 class="sectionedit415"><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>
@@ -913,17 +1067,17 @@ gschem does not provide this functionality internally, however there is a progra
</p>
</div>
-<!-- SECTION "How can I split Postscript output over multiple pages?" [29724-30067] -->
-<h1><a name="gschem_installation_run-time_problems" id="gschem_installation_run-time_problems">Gschem installation/run-time problems</a></h1>
+<!-- EDIT415 SECTION "How can I split Postscript output over multiple pages?" [35481-35824] -->
+<h1 class="sectionedit416"><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" [30068-30120] -->
-<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>
+<!-- EDIT416 SECTION "Gschem installation/run-time problems" [35825-35877] -->
+<h2 class="sectionedit417"><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.
+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>
@@ -931,27 +1085,31 @@ If you happen to have an older version of gEDA/gaf, you can work around this bug
</p>
<p>
-bash:
+bash:
+
</p>
<pre class="code">export G_SLICE=always-malloc</pre>
<p>
-csh:
+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?" [30121-30775] -->
-<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>
+<!-- EDIT417 SECTION "Gschem segfaults when I delete components on FC5 (and other Linux distributions)! Is there a work-around?" [35878-36532] -->
+<h2 class="sectionedit418"><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:
+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:
+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.
@@ -966,12 +1124,13 @@ then gschem is not finding an rc file. There are two required rc files. The firs
<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 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.
+
+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>
@@ -979,8 +1138,8 @@ Also, some older releases of gEDA/gaf had some bugs when the rc files were insta
</p>
</div>
-<!-- SECTION "After installation gschem does not work!? What could be wrong?" [30776-32700] -->
-<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>
+<!-- EDIT418 SECTION "After installation gschem does not work!? What could be wrong?" [36533-38457] -->
+<h2 class="sectionedit419"><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>
@@ -1004,21 +1163,24 @@ Make sure that at least one of your config files contains a valid path to a symb
</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
+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.
+
+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?" [32701-33659] -->
-<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>
+<!-- EDIT419 SECTION "Add Components offers no symbols! What can I do about it?" [38458-39416] -->
+<h2 class="sectionedit420"><a name="i_m_using_gschem_gaf_through_a_ssh_connection_and_i_get_an_error_likexlibextension_render_missing_on_display_localhost100" id="i_m_using_gschem_gaf_through_a_ssh_connection_and_i_get_an_error_likexlibextension_render_missing_on_display_localhost100">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:
+
+If you are getting into the remote machine by doing:
</p>
<pre class="code">$ ssh -X your_username@your_remote_machine</pre>
@@ -1028,9 +1190,10 @@ and afterwards you get the Xlib RENDER message, then try using:
<pre class="code">$ ssh -Y your_username@your_remote_machine</pre>
<p>
-The latter enables trusted X11 forwarding.
+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.'" [33660-] --></body>
+<!-- EDIT420 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.'" [39417-] --></body>
</html>
diff --git a/docs/wiki/geda-faq-pcb.html b/docs/wiki/geda-faq-pcb.html
index 5ea33d3..3c6b7f0 100644
--- a/docs/wiki/geda-faq-pcb.html
+++ b/docs/wiki/geda-faq-pcb.html
@@ -11,75 +11,41 @@
</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>
+<h2 class="sectionedit422"><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>
+<!-- EDIT422 SECTION "pcb FAQ" [1-21] -->
+<h3 class="sectionedit423"><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>.
+â??pcbâ?? is software to help you draw (â??lay outâ??) the wires for a custom â??printed wire boardâ?? (â??PCBâ??).
</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>
+<!-- EDIT423 SECTION "What is pcb ?" [22-147] -->
+<h3 class="sectionedit424"><a name="how_do_i_install_pcb" id="how_do_i_install_pcb">How do I install pcb?</a></h3>
<div class="level3">
<p>
-No. â??Out-of-the-boxâ??, pcb supports 16 copper layers and …
+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 "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>
+<!-- EDIT424 SECTION "How do I install pcb?" [148-282] -->
+<h3 class="sectionedit425"><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.
+No. â??Out-of-the-boxâ??, pcb supports 16 copper layers and â?¦
</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>
+<!-- EDIT425 SECTION "Is it true that pcb is limited to exactly 8 copper layers and 2 silkscreen layers?" [283-437] -->
+<h3 class="sectionedit426"><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>
@@ -87,12 +53,13 @@ No. Lines on a layer with layer name <code>outline</code> will be interpreted as
</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>
+<!-- EDIT426 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 ?" [438-824] -->
+<h3 class="sectionedit427"><a name="how_do_i_design_a_pcb" id="how_do_i_design_a_pcb">How do I design a PCB?</a></h3>
<div class="level3">
<p>
-This is well beyond the scope of this <acronym title="Frequently Asked Questions">FAQ</acronym>. There are a few tips at
+This is well beyond the scope of this <acronym title="Frequently Asked Questions">FAQ</acronym>.
+There are a few tips at
</p>
<ul>
<li class="level1"><div class="li"> <a href="http://en.wikipedia.org/wiki/Printed_circuit_board"; class="urlextern" title="http://en.wikipedia.org/wiki/Printed_circuit_board"; rel="nofollow">http://en.wikipedia.org/wiki/Printed_circuit_board</a></div>
@@ -102,21 +69,22 @@ This is well beyond the scope of this <acronym title="Frequently Asked Questions
</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>
+<!-- EDIT427 SECTION "How do I design a PCB?" [825-1046] -->
+<h3 class="sectionedit428"><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>
+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>?
+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>
+<!-- EDIT428 SECTION "Yes, but how do I design a PCB with pcb?" [1047-1363] -->
+<h3 class="sectionedit429"><a name="what_about_footprints" id="what_about_footprints">What about footprints?</a></h3>
<div class="level3">
<p>
@@ -128,8 +96,8 @@ There are also some unofficial gEDA footprints at Open Circuits <a href="http://
</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>
+<!-- EDIT429 SECTION "What about footprints?" [1364-1526] -->
+<h3 class="sectionedit430"><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>
@@ -137,14 +105,16 @@ The application is a fairly old project, with roots way back in the era of <a hr
</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>
+<!-- EDIT430 SECTION "I had a hard time to find info on pcb due its ambigous name. Why don't you rename the app?" [1527-1863] -->
+<h3 class="sectionedit431"><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> ?
+
+<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>
+<!-- EDIT431 SECTION "Is there any relation between the gEDA PCB and the opencircuitdesign PCB?" [1864-] --></body>
</html>
diff --git a/docs/wiki/geda-faq-simulation.fr.html b/docs/wiki/geda-faq-simulation.fr.html
index 843eb8f..b597792 100644
--- a/docs/wiki/geda-faq-simulation.fr.html
+++ b/docs/wiki/geda-faq-simulation.fr.html
@@ -11,32 +11,13 @@
</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>
+<h1 class="sectionedit433"><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>
+<!-- EDIT433 SECTION "Simulation" [1-25] -->
+<h2 class="sectionedit434"><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>
@@ -45,29 +26,31 @@ Parmi les applications de la Suite gEDA, il y a deux simulateurs de circuits ana
<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 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.
+
+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.
+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>
+<!-- EDIT434 SECTION "Je veux simuler mon circuit analogique. Quelles sont mes options?" [26-1717] -->
+<h2 class="sectionedit435"><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.
+<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:
+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
@@ -80,29 +63,29 @@ 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.
+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.
+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>
+<!-- EDIT435 SECTION "Qu'en est-il de tclspice? Qu'est ce que c'est? Dois-je l'utiliser?" [1718-3965] -->
+<h2 class="sectionedit436"><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.
+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>
+<!-- EDIT436 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 class="sectionedit437"><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.
+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>
@@ -110,21 +93,22 @@ Le <a href="geda-csygas.html" class="wikilink1" title="geda-csygas.html">Circuit
</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.
+
+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>
+<!-- EDIT437 SECTION "Comment puis-je créer mes schémas pour faciliter les simulations analogiques?" [4211-4853] -->
+<h2 class="sectionedit438"><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.
+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>
+<!-- EDIT438 SECTION "Quelles sont les commandes gnetlist pour SPICE sont à utiliser ici? Il y en a beaucoup. . . ." [4854-5201] -->
+<h2 class="sectionedit439"><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>
@@ -132,30 +116,32 @@ Oui. Vous pouvez aussi dessiner votre schéma en utilisant les directives gnucap
</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>
+<!-- EDIT439 SECTION "Comment faire si on veut utiliser gnucap, puis-je utiliser spice-sdb pour créer mes netlists gnucap?" [5202-5455] -->
+<h2 class="sectionedit440"><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:
+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 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 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 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.
+
+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.
+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>
+<!-- EDIT440 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
index ad780dd..021683b 100644
--- a/docs/wiki/geda-faq-simulation.html
+++ b/docs/wiki/geda-faq-simulation.html
@@ -11,32 +11,13 @@
</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>
+<h1 class="sectionedit442"><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>
+<!-- EDIT442 SECTION "Simulation" [1-26] -->
+<h2 class="sectionedit443"><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>
@@ -50,7 +31,8 @@ Within the cannonical gEDA Suite apps there are two analog circuit simulators: n
</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.
+
+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>
@@ -58,8 +40,8 @@ If you prefer a graphical interface, the new gEDA app GSpiceUI provides a nice <
</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>
+<!-- EDIT443 SECTION "I want to simulate my analog circuit design. What are my options?" [27-1384] -->
+<h2 class="sectionedit444"><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>
@@ -67,7 +49,8 @@ If you prefer a graphical interface, the new gEDA app GSpiceUI provides a nice <
</p>
<p>
-As it turns out, this goal was partially met â?? with tclspice you can indeed do something like this:
+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
@@ -80,7 +63,7 @@ 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.
+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>
@@ -88,8 +71,25 @@ Developement on tclspice effectively stopped in 2004. Perhaps some day somebody
</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>
+<!-- EDIT444 SECTION "What about tclspice? What is it? Should I use it?" [1385-3313] -->
+<h2 class="sectionedit445"><a name="where_are_the_models" id="where_are_the_models">Where are the models?</a></h2>
+<div class="level2">
+
+<p>
+There are only very few open source models made available by enthusiasts. This is why there is no extensive library of models included in the gnucap or ngspice package. If you rolled your own and feel like contributing to the project, this would be an excellent opportunity (hint, hintâ?¦).
+</p>
+
+<p>
+Although many manufaturers provide SPICE models free of charge, they keep the license propriatary. This means, that the models can't be distributed with the gEDA suite. In addition, different implementations of SPICE have slightly different ideas about the correct syntax. As a consequence, some models as supplied by the manufacturer need to be tweaked to work with specific implementation.
+</p>
+
+<p>
+Spicelib provides a way to receive models tweaked for gnucap and ngpice. It is a set of scripts that will fetch vendors' models directly from the source, solving the redistribution problem. Then it will patch them for compatibility with gnucap and ng-spice. You can download spicelib from <a href="http://www.h-renrew.de/h/spicelib/doc/index.html"; class="urlextern" title="http://www.h-renrew.de/h/spicelib/doc/index.html"; rel="nofollow">http://www.h-renrew.de/h/spicelib/doc/index.html</a>.
+</p>
+
+</div>
+<!-- EDIT445 SECTION "Where are the models?" [3314-4377] -->
+<h2 class="sectionedit446"><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>
@@ -97,8 +97,8 @@ No. The best you can do is use <a href="http://www.geda.seul.org/tools/gspiceui/
</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>
+<!-- EDIT446 SECTION "Isn't there a nice graphical (schematic capture) front end so I can just place components and press a simulate button?" [4378-4607] -->
+<h2 class="sectionedit447"><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>
@@ -110,12 +110,13 @@ The <a href="geda-csygas.html" class="wikilink1" title="geda-csygas.html">Circui
</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.
+
+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>
+<!-- EDIT447 SECTION "How do I create my schematic to facilitate analog simulation?" [4608-5160] -->
+<h2 class="sectionedit448"><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>
@@ -123,8 +124,8 @@ Use spice-sdb. It is by far the most advanced and feature rich. The others are t
</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>
+<!-- EDIT448 SECTION "Which spice netlister backend to gnetlist should I use? There are several of them. . . ." [5161-5501] -->
+<h2 class="sectionedit449"><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>
@@ -136,8 +137,8 @@ It is better to just draw the circuit, without directives, and run the simulator
</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>
+<!-- EDIT449 SECTION "How about if I want to use gnucap, can I use spice-sdb to create my gnucap netlists?" [5502-5806] -->
+<h2 class="sectionedit450"><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>
@@ -153,13 +154,15 @@ Newbies commonly want to create a single schematic for both design simulation/va
</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.
+
+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.
+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>
+<!-- EDIT450 SECTION "Why not reuse my simulation schematic for layout?" [5807-] --></body>
</html>
diff --git a/docs/wiki/geda-faq.fr.html b/docs/wiki/geda-faq.fr.html
index 8fbfef9..a8e1936 100644
--- a/docs/wiki/geda-faq.fr.html
+++ b/docs/wiki/geda-faq.fr.html
@@ -11,49 +11,21 @@
</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>
+<h1 class="sectionedit452"><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>
+<!-- EDIT452 SECTION "FAQ gEDA" [1-24] -->
+<h2 class="sectionedit453"><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) ».
+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.
+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>
@@ -61,12 +33,12 @@ gEDA peut être prononcé « gee-daahhh » (rhymes with cheetah) ou â??g-dahhh (
</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>
+<!-- EDIT453 SECTION "Qu'est ce que le projet gEDA?" [25-1585] -->
+<h2 class="sectionedit454"><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:
+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>
@@ -75,7 +47,7 @@ gaf signifie « <em class="u">g</em>schem <em class="u">a</em>nd <em class="u">f
</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 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>
@@ -86,11 +58,12 @@ gaf signifie « <em class="u">g</em>schem <em class="u">a</em>nd <em class="u">f
</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).
+
+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.
+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>
@@ -98,12 +71,12 @@ Pour des raisons historiques, sur <a href="http://freshmeat.net/"; class="urlexte
</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>
+<!-- EDIT454 SECTION "qu'est ce que gEDA/gaf et quelle est sa relation avec gEDA?" [1586-3369] -->
+<h2 class="sectionedit455"><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:
+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>
@@ -120,19 +93,20 @@ La suite gEDA est une image CDROM (.iso) crée par Stuart Brorson pour faciliter
</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 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>
+
+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>
+<!-- EDIT455 SECTION "Qu'est ce que la suite gEDA?" [3370-4962] -->
+<h2 class="sectionedit456"><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>
@@ -143,115 +117,116 @@ Les outils de la suite gEDA et leurs associés ont les caractéristiques suivant
</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 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 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 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 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 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 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.
+
+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>
+<!-- EDIT456 SECTION "Pourquoi? Qu'est ce qui rend gEDA si différent des autres outils d'EDA ?" [4963-7518] -->
+<h2 class="sectionedit457"><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é!
+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.
+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.
+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>
+<!-- EDIT457 SECTION "Pourquoi la Suite gEDA ressemble-t-elle à une collection de programmes épars et pas une seule application intégrée?" [7519-9623] -->
+<h2 class="sectionedit458"><a name="qu_est_ce_qui_est_mieux_une_suite_ie_confederee_de_programmes_ou_une_application_integree" id="qu_est_ce_qui_est_mieux_une_suite_ie_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.
+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>
+<!-- EDIT458 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 class="sectionedit459"><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 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 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 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 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>
+<!-- EDIT459 SECTION "Pour la Suite (l'association):" [9862-13042] -->
+<h3 class="sectionedit460"><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 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 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 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 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>
+<!-- EDIT460 SECTION "Contre la Suite (l'association):" [13043-14705] -->
+<h3 class="sectionedit461"><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 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 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>
+<!-- EDIT461 SECTION "Pour les applications monolithiques:" [14706-15166] -->
+<h3 class="sectionedit462"><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 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 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 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>
+<!-- EDIT462 SECTION "Contre les applications monolithiques:" [15167-16800] -->
+<h2 class="sectionedit463"><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>
@@ -263,20 +238,20 @@ 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.
+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.
+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>.
+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>
+<!-- EDIT463 SECTION "Quelle est la licence utilisée par gEDA?" [16801-18267] -->
+<h2 class="sectionedit464"><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>
@@ -300,18 +275,19 @@ Venez à la réunion des « Free EDA Users Group » (Freedog) de Cambridge, MA.
</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>
+<!-- EDIT464 SECTION "Où puis-je avoir plus d'informations à propos de gEDA et sur son téléchargement?" [18268-19571] -->
+<h2 class="sectionedit465"><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.
+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!
+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>
+<!-- EDIT465 SECTION "OK, comment je comence à utiliser gEDA?" [19572-] --></body>
</html>
diff --git a/docs/wiki/geda-faq.html b/docs/wiki/geda-faq.html
index 10d1663..f42d6bc 100644
--- a/docs/wiki/geda-faq.html
+++ b/docs/wiki/geda-faq.html
@@ -11,46 +11,17 @@
</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>
+<h1 class="sectionedit470"><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>
+<!-- EDIT470 SECTION "gEDA FAQ" [1-25] -->
+<h2 class="sectionedit471"><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.
+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>
@@ -62,8 +33,8 @@ gEDA can be pronounced â??gee-daahhhâ?? (rhymes with cheetah) or â??g-dahhh (sho
</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>
+<!-- EDIT471 SECTION "What is the gEDA project?" [26-1445] -->
+<h2 class="sectionedit472"><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>
@@ -87,11 +58,12 @@ gEDA can be pronounced â??gee-daahhhâ?? (rhymes with cheetah) or â??g-dahhh (sho
</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).
+
+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.
+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>
@@ -99,8 +71,8 @@ For historical reasons, on <a href="http://freshmeat.net/"; class="urlextern" tit
</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>
+<!-- EDIT472 SECTION "What is gEDA/gaf and how does it relate to gEDA?" [1446-3012] -->
+<h2 class="sectionedit473"><a name="what_is_the_geda_suite" id="what_is_the_geda_suite">What is the gEDA suite?</a></h2>
<div class="level2">
<p>
@@ -128,12 +100,13 @@ The gEDA suite is the collection of all the various tools that are part of, asso
</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>
+
+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>
+<!-- EDIT473 SECTION "What is the gEDA suite?" [3013-4204] -->
+<h2 class="sectionedit474"><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>
@@ -142,7 +115,7 @@ Tools in the gEDA suite and associated tools have the following characteristics:
<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 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>
@@ -167,12 +140,13 @@ Tools in the gEDA suite and associated tools have the following characteristics:
</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.
+
+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>
+<!-- EDIT474 SECTION "Why? What makes gEDA so different from other EDA tools?" [4205-6491] -->
+<h2 class="sectionedit475"><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>
@@ -192,8 +166,8 @@ In the end, the best way to think about the gEDA suite is as an EDA toolkit. Th
</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>
+<!-- EDIT475 SECTION "Why does the gEDA Suite seem like a collection of random programs, and not a single integrated application?" [6492-8506] -->
+<h2 class="sectionedit476"><a name="so_which_is_better_a_suite_ie_confederacy_of_programs_or_an_integrated_application" id="so_which_is_better_a_suite_ie_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>
@@ -201,8 +175,8 @@ This is ultimately a matter of religion. Iâ??ll summarize some of the pros and c
</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>
+<!-- EDIT476 SECTION "So which is better, a suite (i.e. confederacy) of programs or an integrated application?" [8507-8731] -->
+<h3 class="sectionedit477"><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>
@@ -216,8 +190,8 @@ This is ultimately a matter of religion. Iâ??ll summarize some of the pros and c
</ul>
</div>
-<!-- SECTION "Suite (confederacy) pros:" [8732-11376] -->
-<h3><a name="suite_confederacy_cons" id="suite_confederacy_cons">Suite (confederacy) cons:</a></h3>
+<!-- EDIT477 SECTION "Suite (confederacy) pros:" [8732-11376] -->
+<h3 class="sectionedit478"><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>
@@ -231,8 +205,8 @@ This is ultimately a matter of religion. Iâ??ll summarize some of the pros and c
</ul>
</div>
-<!-- SECTION "Suite (confederacy) cons:" [11377-12712] -->
-<h3><a name="monolithic_application_pros" id="monolithic_application_pros">Monolithic application pros:</a></h3>
+<!-- EDIT478 SECTION "Suite (confederacy) cons:" [11377-12712] -->
+<h3 class="sectionedit479"><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>
@@ -242,8 +216,8 @@ This is ultimately a matter of religion. Iâ??ll summarize some of the pros and c
</ul>
</div>
-<!-- SECTION "Monolithic application pros:" [12713-13067] -->
-<h3><a name="monolithic_application_cons" id="monolithic_application_cons">Monolithic application cons:</a></h3>
+<!-- EDIT479 SECTION "Monolithic application pros:" [12713-13067] -->
+<h3 class="sectionedit480"><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>
@@ -255,8 +229,8 @@ This is ultimately a matter of religion. Iâ??ll summarize some of the pros and c
</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>
+<!-- EDIT480 SECTION "Monolithic application cons:" [13068-14511] -->
+<h2 class="sectionedit481"><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>
@@ -264,24 +238,25 @@ Newbies sometimes show up on the gEDA mailing lists and flame the project for mi
</p>
<p>
-If you need a new feature implemented in one of the gEDA tools, here are your options:
+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 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://bugs.launchpad.net/geda"; class="urlextern" title="http://bugs.launchpad.net/geda"; 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 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://bugs.launchpad.net/geda"; class="urlextern" title="http://bugs.launchpad.net/geda"; rel="nofollow">Launchpad bug 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 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>
+<!-- EDIT481 SECTION "Tool XXX is missing critical feature YYY! What can I do?" [14512-16681] -->
+<h2 class="sectionedit482"><a name="what_license_does_geda_use" id="what_license_does_geda_use">What license does gEDA use?</a></h2>
<div class="level2">
<p>
@@ -293,7 +268,7 @@ 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."
+â??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>
@@ -304,9 +279,13 @@ This cannot be stressed enough: <strong>gEDA is GPLed software</strong>. Therefo
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>
+<p>
+For more information about the license used by gEDA, please read the <a href="geda-license.html" class="wikilink1" title="geda-license.html"> licensing </a> page.
+</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>
+<!-- EDIT482 SECTION "What license does gEDA use?" [16682-18072] -->
+<h2 class="sectionedit483"><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>
@@ -322,16 +301,16 @@ You can download all the software, including the gEDA Suite Binary installer, fr
</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.
+You can find the latest set of documentation on the top-level <a href="http://geda.seul.org/wiki/geda:documentation"; class="urlextern" title="http://geda.seul.org/wiki/geda:documentation"; 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.
+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>
+<!-- EDIT483 SECTION "Where can I get more information about and download gEDA?" [18073-19220] -->
+<h2 class="sectionedit484"><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>
@@ -345,9 +324,11 @@ The most important thing to do is to read and understand one or both of the tuto
</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!
+
+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>
+<!-- EDIT484 SECTION "Okay, how do I start using gEDA?" [19221-] --></body>
</html>
diff --git a/docs/wiki/geda-fbabgapp.html b/docs/wiki/geda-fbabgapp.html
index f6a5e7e..9824cbf 100644
--- a/docs/wiki/geda-fbabgapp.html
+++ b/docs/wiki/geda-fbabgapp.html
@@ -11,27 +11,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>
+<h1 class="sectionedit494"><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>
@@ -47,23 +28,24 @@ 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>
+<!-- EDIT494 SECTION "Forward/Backward Annotation Between gEDA/gaf and PADS PowerPCB" [1-191] -->
+<h2 class="sectionedit495"><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>
+<!-- EDIT495 SECTION "Forward Annotation of gEDA Schematic Changes to PADS PowerPCB Layout" [192-272] -->
+<h2 class="sectionedit496"><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.
+
+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>
+<!-- EDIT496 SECTION "Overview" [273-936] -->
+<h2 class="sectionedit497"><a name="detailed_forward_annotation_procedure" id="detailed_forward_annotation_procedure">Detailed Forward Annotation Procedure</a></h2>
<div class="level2">
<p>
@@ -71,60 +53,61 @@ This procedure assumes you have a board layout open in PADS and that you have ma
</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>
+<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 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>
+<div class="table sectionedit498"><table class="inline">
+ <tr class="row0">
+ <td class="col0">original design to compare</td><td class="col1">use current PCB design</td>
</tr>
- <tr>
- <td>new design with changes</td><td>mynet.asc</td>
+ <tr class="row1">
+ <td class="col0">new design with changes</td><td class="col1">mynet.asc</td>
</tr>
- <tr>
- <td>â??</td><td>generate differences report</td>
+ <tr class="row2">
+ <td class="col0">â??</td><td class="col1">generate differences report</td>
</tr>
- <tr>
- <td>â??</td><td>generate eco file</td>
+ <tr class="row3">
+ <td class="col0">â??</td><td class="col1">generate eco file</td>
</tr>
- <tr>
+ <tr class="row4">
</tr>
- <tr>
- <td colspan="2">comparison options</td>
+ <tr class="row5">
+ <td class="col0" colspan="2">comparison options</td>
</tr>
- <tr>
- <td>â??</td><td>compare only ECO registered parts</td>
+ <tr class="row6">
+ <td class="col0">â??</td><td class="col1">compare only ECO registered parts</td>
</tr>
- <tr>
- <td colspan="2"> </td>
+ <tr class="row7">
+ <td class="col0" colspan="2"> </td>
</tr>
- <tr>
- <td colspan="2">attribute comparison level</td>
+ <tr class="row8">
+ <td class="col0" colspan="2">attribute comparison level</td>
</tr>
- <tr>
- <td>â??</td><td>ignore all attributes</td>
+ <tr class="row9">
+ <td class="col0">â??</td><td class="col1">ignore all attributes</td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT498 TABLE [1578-1852] -->
<p>
- Click the OK button to create the ECO file.
+
+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 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>
+<!-- EDIT497 SECTION "Detailed Forward Annotation Procedure" [937-2135] -->
+<h2 class="sectionedit499"><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>
@@ -140,12 +123,13 @@ Backannotation is the process of updating schematics to reflect changes made in
</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.
+
+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>
+<!-- EDIT499 SECTION "Back Annotation of PADS PowerPCB Layout Changes to gEDA Schematic" [2136-3463] -->
+<h3 class="sectionedit500"><a name="detailed_backannotation_procedure" id="detailed_backannotation_procedure">Detailed Backannotation Procedure</a></h3>
<div class="level3">
<p>
@@ -153,47 +137,49 @@ This procedure assumes you have a board layout open in PADS. For the purposes of
</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>
+<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 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>
+<div class="table sectionedit501"><table class="inline">
+ <tr class="row0">
+ <td class="col0">original design to compare</td><td class="col1">mynet.asc</td>
</tr>
- <tr>
- <td>new design with changes</td><td>use current PCB design</td>
+ <tr class="row1">
+ <td class="col0">new design with changes</td><td class="col1">use current PCB design</td>
</tr>
- <tr>
- <td>â??</td><td>generate differences report</td>
+ <tr class="row2">
+ <td class="col0">â??</td><td class="col1">generate differences report</td>
</tr>
- <tr>
- <td>â??</td><td>generate eco file</td>
+ <tr class="row3">
+ <td class="col0">â??</td><td class="col1">generate eco file</td>
</tr>
- <tr>
- <td colspan="2"> </td>
+ <tr class="row4">
+ <td class="col0" colspan="2"> </td>
</tr>
- <tr>
- <td colspan="2">comparison options</td>
+ <tr class="row5">
+ <td class="col0" colspan="2">comparison options</td>
</tr>
- <tr>
- <td>â??</td><td>compare only ECO registered parts</td>
+ <tr class="row6">
+ <td class="col0">â??</td><td class="col1">compare only ECO registered parts</td>
</tr>
- <tr>
- <td colspan="2"> </td>
+ <tr class="row7">
+ <td class="col0" colspan="2"> </td>
</tr>
- <tr>
- <td colspan="2">attribute comparison level</td>
+ <tr class="row8">
+ <td class="col0" colspan="2">attribute comparison level</td>
</tr>
- <tr>
- <td>â??</td><td>ignore all attributes</td>
+ <tr class="row9">
+ <td class="col0">â??</td><td class="col1">ignore all attributes</td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT501 TABLE [3961-4236] -->
<p>
- Click the OK button to create the ECO file.
+
+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>
@@ -201,11 +187,11 @@ This procedure assumes you have a board layout open in PADS. For the purposes of
<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>
+<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>
+<!-- EDIT500 SECTION "Detailed Backannotation Procedure" [3464-] --></body>
</html>
diff --git a/docs/wiki/geda-fc1.html b/docs/wiki/geda-fc1.html
index 6890814..f033ca6 100644
--- a/docs/wiki/geda-fc1.html
+++ b/docs/wiki/geda-fc1.html
@@ -11,27 +11,13 @@
</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>
+<h1 class="sectionedit503"><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>
+<!-- EDIT503 SECTION "Installer 2005080X on Fedora Core 1 install notes" [1-64] -->
+<h2 class="sectionedit504"><a name="prerequisites" id="prerequisites">Prerequisites:</a></h2>
<div class="level2">
<p>
@@ -39,8 +25,8 @@ When you install FC1, make sure you install the â??workstationâ?? version, and n
</p>
</div>
-<!-- SECTION "Prerequisites:" [65-472] -->
-<h2><a name="problems" id="problems">Problems:</a></h2>
+<!-- EDIT504 SECTION "Prerequisites:" [65-472] -->
+<h2 class="sectionedit505"><a name="problems" id="problems">Problems:</a></h2>
<div class="level2">
<p>
@@ -48,5 +34,5 @@ The installer has been thoroughly tested on this platform. No problems are known
</p>
</div>
-<!-- SECTION "Problems:" [473-] --></body>
+<!-- EDIT505 SECTION "Problems:" [473-] --></body>
</html>
diff --git a/docs/wiki/geda-fc2.html b/docs/wiki/geda-fc2.html
index f3893d4..89f3e10 100644
--- a/docs/wiki/geda-fc2.html
+++ b/docs/wiki/geda-fc2.html
@@ -11,27 +11,13 @@
</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>
+<h1 class="sectionedit565"><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>
+<!-- EDIT565 SECTION "Installer 2005080X on Fedora Core 2 install notes" [1-64] -->
+<h2 class="sectionedit566"><a name="prerequisites" id="prerequisites">Prerequisites:</a></h2>
<div class="level2">
<p>
@@ -39,8 +25,8 @@ When you install FC2, make sure you install the â??workstationâ?? version, and n
</p>
</div>
-<!-- SECTION "Prerequisites:" [65-472] -->
-<h2><a name="problems" id="problems">Problems:</a></h2>
+<!-- EDIT566 SECTION "Prerequisites:" [65-472] -->
+<h2 class="sectionedit567"><a name="problems" id="problems">Problems:</a></h2>
<div class="level2">
<p>
@@ -48,5 +34,5 @@ The installer has been thoroughly tested on this platform. No problems are known
</p>
</div>
-<!-- SECTION "Problems:" [473-] --></body>
+<!-- EDIT567 SECTION "Problems:" [473-] --></body>
</html>
diff --git a/docs/wiki/geda-fc3.html b/docs/wiki/geda-fc3.html
index 0ca4a9e..f7b4055 100644
--- a/docs/wiki/geda-fc3.html
+++ b/docs/wiki/geda-fc3.html
@@ -11,27 +11,13 @@
</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>
+<h1 class="sectionedit666"><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>
+<!-- EDIT666 SECTION "Installer 2005080X on Fedora Core 3 install notes" [1-64] -->
+<h2 class="sectionedit667"><a name="prerequisites" id="prerequisites">Prerequisites:</a></h2>
<div class="level2">
<p>
@@ -39,8 +25,8 @@ When you install FC3, make sure you install the â??workstationâ?? version, and n
</p>
</div>
-<!-- SECTION "Prerequisites:" [65-472] -->
-<h2><a name="problems" id="problems">Problems:</a></h2>
+<!-- EDIT667 SECTION "Prerequisites:" [65-472] -->
+<h2 class="sectionedit668"><a name="problems" id="problems">Problems:</a></h2>
<div class="level2">
<p>
@@ -48,5 +34,5 @@ No problems are known, and none have been reported.
</p>
</div>
-<!-- SECTION "Problems:" [473-] --></body>
+<!-- EDIT668 SECTION "Problems:" [473-] --></body>
</html>
diff --git a/docs/wiki/geda-fc4.html b/docs/wiki/geda-fc4.html
index a57f8c6..2c1ce2c 100644
--- a/docs/wiki/geda-fc4.html
+++ b/docs/wiki/geda-fc4.html
@@ -11,23 +11,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>
+<h1 class="sectionedit689"><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>
@@ -47,17 +32,17 @@ The latest CD installer will work fine on Fedora Core 4. All gEDA Suite program
</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.
+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>
+<!-- EDIT689 SECTION "Installer 20060825 on Fedora Core 4 install notes" [1-650] -->
+<h1 class="sectionedit690"><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>
+<!-- EDIT690 SECTION "Installer 2005080X on Fedora Core 4 install notes" [651-714] -->
+<h2 class="sectionedit691"><a name="prerequisites" id="prerequisites">Prerequisites:</a></h2>
<div class="level2">
<p>
@@ -81,7 +66,8 @@ Also, the following additional RPMs are required:
</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.
+
+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>
@@ -89,8 +75,8 @@ Before installing the gEDA Suite on an FC4 system, you should set the CC environ
</p>
</div>
-<!-- SECTION "Prerequisites:" [715-1851] -->
-<h2><a name="problems" id="problems">Problems:</a></h2>
+<!-- EDIT691 SECTION "Prerequisites:" [715-1851] -->
+<h2 class="sectionedit692"><a name="problems" id="problems">Problems:</a></h2>
<div class="level2">
<p>
@@ -98,17 +84,18 @@ The 200508XX installer will fail on FC4 systems. There seem to be several indepe
</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>
+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>
+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.
+
+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>
@@ -124,13 +111,15 @@ Once they are installed, set the gcc environment variables as follows:
</p>
<p>
-for bash:
+for bash:
+
</p>
<pre class="code">export CC=gcc32
export CXX=g++32</pre>
<p>
-for csh:
+for csh:
+
</p>
<pre class="code">setenv CC gcc32
setenv CXX g++32</pre>
@@ -140,5 +129,5 @@ and then run the installer. Make sure you run the installer from the same window
</p>
</div>
-<!-- SECTION "Problems:" [1852-] --></body>
+<!-- EDIT692 SECTION "Problems:" [1852-] --></body>
</html>
diff --git a/docs/wiki/geda-fedora_rpm_installation.html b/docs/wiki/geda-fedora_rpm_installation.html
index 406a5b8..7aa944f 100644
--- a/docs/wiki/geda-fedora_rpm_installation.html
+++ b/docs/wiki/geda-fedora_rpm_installation.html
@@ -11,112 +11,38 @@
</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>
+<h1 class="sectionedit694"><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.)
+gEDA/gaf applications are available in the default Fedora repositories. The Fedora packages are maintained by Chitlesh Goorah.
</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>
+<!-- EDIT694 SECTION "Installing gEDA rpm packages on Fedora" [1-183] -->
+<h3 class="sectionedit695"><a name="installing_from_fedora_repositories" id="installing_from_fedora_repositories">Installing from Fedora repositories</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>
+It is recommended to install gEDA/gaf releases on Fedora using <code>yum</code> or <code>pirut</code>. Pirut (listed in the menu as â??Add/Remove Softwareâ??) is a graphical interface for <code>yum</code>.
-<p>
-Note: you have to be under root (su -) to install packages.
</p>
+<pre class="code">yum install geda\* pcb gerbv</pre>
<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.
+
+Note: you have to be root (<code>su -</code>) to install packages.
</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.
+Each gEDA/gaf release takes one to two days to be packaged up and synchronised with the Fedora mirrors. If a release seems to be missing, you could 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
+You can follow:
</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>
@@ -125,75 +51,33 @@ One can follow up
</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>
+<!-- EDIT695 SECTION "Installing from Fedora repositories" [184-998] -->
+<h3 class="sectionedit696"><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>
+If you want to get their hands dirty by building gEDA/gaf on Fedora, you will need to install the dependencies listed in the gEDA/gaf <code>README</code> file. They can be installed with <code>yum</code>:
-<p>
- Note: Fedora Core 5 has guile 1.6.x whereas Fedora Core 6 and onwards has guile 1.8.x
</p>
+<pre class="code">yum install libstroke-devel groff autoconf gtk2-devel gd-devel gettext-devel guile-devel</pre>
</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>
+<!-- EDIT696 SECTION "Compile it yourself" [999-1310] -->
+<h3 class="sectionedit697"><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.
+The Fedora Project provides simple tools for anyone to rebuild RPMs from SRPMs. An SRPM contains the upstream sources, the <acronym title="specification">spec</acronym> file and the patches required (if any).
</p>
<p>
-<code><strong>yum install rpmdevtools</strong></code> (as root)
+To be able to build RPMs, you will need a build platform, which does <strong>NOT</strong> require root access. <code>rpmdevtools</code> provides the requires tools to do so.
+
</p>
+<pre class="code">yum install rpmdevtools</pre>
</div>
@@ -201,15 +85,15 @@ To be able to build RPMs, one will need a build platform, which does <strong>NOT
<div class="level4">
<p>
- The build platform should be built under a NON-root account.
-</p>
-<p>
-<code>$ <strong>fedora-buildrpmtree</strong></code>
+The build platform should be built under a NON-root account.
+
</p>
+<pre class="code">fedora-buildrpmtree</pre>
<p>
-You can see a <code>rpmbuild</code> folder under your $HOME directory. This directory will be your build platform.
+
+You will see a <code>rpmbuild</code> folder in your <code>$HOME</code> directory. This directory will be your build platform.
</p>
</div>
@@ -218,35 +102,36 @@ You can see a <code>rpmbuild</code> folder under your $HOME directory. This dire
<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>
+Fedora provides SRPM of every package it has. You can download those SRPMs using the <code>yumdownloader</code> tool from the <code>yum-utils</code> package.
-<p>
- Download a particular SRPM (under a NON-root account) by <code>$ <strong>yumdownloader –source package –enablerepo=development-source</strong> </code>
</p>
+<pre class="code">yum install yum-utils</pre>
<p>
-package is the name of the package you want to download.
+if you don't have <code>yum-utils</code> installed already.
</p>
<p>
-Once the download is complete the package can be found under the current directory under the filename %{name}-%{version}-%{dist}.src.rpm.
+Download a the <code>geda-gaf</code> SRPM (under a NON-root account) using:
+
</p>
+<pre class="code">yumdownloader --source geda-gaf</pre>
<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:
+
+Once the download is complete the package can be found under the current directory under the filename <code>geda-gaf-%{version}-%{dist}.src.rpm</code>, where <code>%{version}</code> is the current version of gEDA/gaf packaged by Fedora, and <code>%{dist}</code> is the current Fedora version. For example, the gEDA/gaf SRPM for Fedora 14 is called <code>geda-gaf-1.6.1-1.fc14.src.rpm</code>.
</p>
<p>
-<code>$ <strong>rpm -ivh %{name}-%{version}-%{dist}.src.rpm</strong></code>
+The <acronym title="specification">spec</acronym> file, upstream sources and distribution patches can be extracted from the SRPM using:
+
</p>
+<pre class="code">rpm -ivh geda-gaf-%{version}-%{dist}.src.rpm</pre>
<p>
-(I remind you that this should at no cost be executed as root !)
+
+(I remind you that this should never be executed as root!)
</p>
<p>
@@ -263,43 +148,41 @@ You will see
<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>
+
+<p>
+
+First:
+
+</p>
+<ol>
+<li class="level1"><div class="li"> Download your new sources, as described in the previous section.</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 class="level1"><div class="li"> Edit the rpmbuild/SPECS/%{name}.<acronym title="specification">spec</acronym></div>
+<ol>
+<li class="level2"><div class="li"> Edit version tag</div>
</li>
-<li class="level3"><div class="li"> edit release tag</div>
+<li class="level2"><div class="li"> Edit release tag</div>
</li>
-</ul>
+</ol>
</li>
-</ul>
+<li class="level1"><div class="li"> Make any other changes you require</div>
+</li>
+</ol>
<p>
-with repect to your newly downloaded sources.
-</p>
-<p>
-<code><strong> cd rpmbuild/SPECS/ </strong></code>
-</p>
+Once the previous steps have been completed, you can compile the new RPMs.
-<p>
-now start building the RPMS:
</p>
+<pre class="code">cd $HOME/rpmbuild/SPECS/
+rpmbuild -ba %{name}.spec</pre>
<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>
+The successfully built RPMS will be found in <code>$HOME/rpmbuild/RPMS/</code>, and the corresponding SRPM in <code>$HOME/rpmbuild/SPRMS</code>.
-<p>
-The successfully build RPMS will be found in the folders of ~/rpmbuild/RPMS/.
</p>
</div>
-<!-- SECTION "Rebuild your own rpms" [2507-] --></body>
+<!-- EDIT697 SECTION "Rebuild your own RPMs" [1311-] --></body>
</html>
diff --git a/docs/wiki/geda-file_format_spec.html b/docs/wiki/geda-file_format_spec.html
index e408185..fe1c95c 100644
--- a/docs/wiki/geda-file_format_spec.html
+++ b/docs/wiki/geda-file_format_spec.html
@@ -11,45 +11,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>
+<h1 class="sectionedit699"><a name="geda_gaf_file_format_document" id="geda_gaf_file_format_document">gEDA/gaf File Format Document</a></h1>
<div class="level1">
<p>
@@ -65,19 +28,21 @@ December 31st, 2003
</p>
</div>
-<!-- SECTION "gEDA/gaf File Format Document" [1-187] -->
-<h2><a name="overview" id="overview">Overview</a></h2>
+<!-- EDIT699 SECTION "gEDA/gaf File Format Document" [1-187] -->
+<h2 class="sectionedit700"><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.
+
+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>
+<!-- EDIT700 SECTION "Overview" [188-902] -->
+<h2 class="sectionedit701"><a name="coordinate_space" id="coordinate_space">Coordinate Space</a></h2>
<div class="level2">
<p>
@@ -94,31 +59,35 @@ All coordinates are in mils (1/1000 or an inch). This is an arbitrary decision.
</ul>
<p>
- The following figure shows how the coordinate space is setup:
+
+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>
+<div class="table sectionedit702"><table class="inline">
+ <tr class="row0">
+ <td class="col0"><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>
-
+</table></div>
+<!-- EDIT702 TABLE [1498-1557] -->
<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.
+
+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>
+<!-- EDIT701 SECTION "Coordinate Space" [903-1709] -->
+<h2 class="sectionedit703"><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.
+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>
+<!-- EDIT703 SECTION "Filenames" [1710-2246] -->
+<h2 class="sectionedit704"><a name="object_types" id="object_types">Object types</a></h2>
<div class="level2">
<p>
@@ -138,36 +107,42 @@ A schematic/symbol file for gEDA/gaf consists of:
</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.
+
+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-3519] -->
-<h3><a name="version" id="version">version</a></h3>
+<!-- EDIT704 SECTION "Object types" [2247-3519] -->
+<h3 class="sectionedit705"><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>
+
+<strong><code>type version fileformat_version</code></strong>
+
</p>
-<table class="inline">
- <tr>
- <th>Field</th><th>Type/unit</th><th>Description</th>
+<div class="table sectionedit706"><table class="inline">
+ <tr class="row0">
+ <th class="col0">Field</th><th class="col1">Type/unit</th><th class="col2">Description</th>
</tr>
- <tr>
- <td>type</td><td>char</td><td>v</td>
+ <tr class="row1">
+ <td class="col0">type</td><td class="col1">char</td><td class="col2">v</td>
</tr>
- <tr>
- <td>version</td><td>int</td><td>version of gEDA/gaf that wrote this file</td>
+ <tr class="row2">
+ <td class="col0">version</td><td class="col1">int</td><td class="col2">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 class="row3">
+ <td class="col0">fileformat_version</td><td class="col1">int</td><td class="col2">gEDA/gaf file format version number</td>
</tr>
-</table>
-<ul>
+</table></div>
+<!-- EDIT706 TABLE [3618-3777] --><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>
@@ -186,70 +161,74 @@ Valid in: Schematic and Symbol files<br/>
</li>
<li class="level1"><div class="li"> fileformat version is just an integer with no minor number.</div>
</li>
-<li class="level1"><div class="li"> 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, 20080127, 20080706, 20081220, 20081221, 20090328, 20090829, 20090830</div>
+<li class="level1"><div class="li"> Development versions include: 19990601, 19990610, 19990705, 19990829, 19990919, 19991011, 20000220, 20000704, 20001006, 20001217, 20010304, 20010708, 20010722, 20020209, 20020414, 20020527, 20020825, 20021103, 20030223, 20030525, 20030901, 20040111, 20040710, 20041228, 20050313, 20050820, 20060123, 20060824, 20060906, 20061020, 20070216, 20070705, 20070708, 20070818, 20071229, 20080110, 20080127, 20080706, 20081220, 20081221, 20090328, 20090829, 20090830, 20110116</div>
</li>
-<li class="level1"><div class="li"> Stable versions include: 20070526, 20070626, 20070902, 20071231, 20080127, 20080929, 20081220, 20081231, 20091004, 20100214</div>
+<li class="level1"><div class="li"> Stable versions include: 20070526, 20070626, 20070902, 20071231, 20080127, 20080929, 20081220, 20081231, 20091004, 20100214, 20110115</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 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/>
-
+
+Example:<br/>
+
+
</p>
<pre class="code">v 20040111 1</pre>
</div>
-<!-- SECTION "version" [3520-5597] -->
-<h3><a name="line" id="line">line</a></h3>
+<!-- EDIT705 SECTION "version" [3520-5607] -->
+<h3 class="sectionedit707"><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>
+
+<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>
+<div class="table sectionedit708"><table class="inline">
+ <tr class="row0">
+ <th class="col0">Field</th><th class="col1">Type/unit</th><th class="col2">Description</th>
</tr>
- <tr>
- <td>type</td><td>char</td><td>L</td>
+ <tr class="row1">
+ <td class="col0">type</td><td class="col1">char</td><td class="col2">L</td>
</tr>
- <tr>
- <td>x1</td><td>int/mils</td><td>First X coordinate</td>
+ <tr class="row2">
+ <td class="col0">x1</td><td class="col1">int/mils</td><td class="col2">First X coordinate</td>
</tr>
- <tr>
- <td>y1</td><td>int/mils</td><td>First Y coordinate</td>
+ <tr class="row3">
+ <td class="col0">y1</td><td class="col1">int/mils</td><td class="col2">First Y coordinate</td>
</tr>
- <tr>
- <td>x2</td><td>int/mils</td><td>Second X coordinate</td>
+ <tr class="row4">
+ <td class="col0">x2</td><td class="col1">int/mils</td><td class="col2">Second X coordinate</td>
</tr>
- <tr>
- <td>y2</td><td>int/mils</td><td>Second Y coordinate</td>
+ <tr class="row5">
+ <td class="col0">y2</td><td class="col1">int/mils</td><td class="col2">Second Y coordinate</td>
</tr>
- <tr>
- <td>color</td><td>int</td><td>Color index</td>
+ <tr class="row6">
+ <td class="col0">color</td><td class="col1">int</td><td class="col2">Color index</td>
</tr>
- <tr>
- <td>width</td><td>int/mils</td><td>Width of line</td>
+ <tr class="row7">
+ <td class="col0">width</td><td class="col1">int/mils</td><td class="col2">Width of line</td>
</tr>
- <tr>
- <td>capstyle</td><td>int</td><td>Line cap style</td>
+ <tr class="row8">
+ <td class="col0">capstyle</td><td class="col1">int</td><td class="col2">Line cap style</td>
</tr>
- <tr>
- <td>dashstyle</td><td>int</td><td>Type of dash style</td>
+ <tr class="row9">
+ <td class="col0">dashstyle</td><td class="col1">int</td><td class="col2">Type of dash style</td>
</tr>
- <tr>
- <td>dashlength</td><td>int</td><td>Length of dash</td>
+ <tr class="row10">
+ <td class="col0">dashlength</td><td class="col1">int</td><td class="col2">Length of dash</td>
</tr>
- <tr>
- <td>dashspace</td><td>int</td><td>Space inbetween dashes</td>
+ <tr class="row11">
+ <td class="col0">dashspace</td><td class="col1">int</td><td class="col2">Space inbetween dashes</td>
</tr>
-</table>
-<ul>
+</table></div>
+<!-- EDIT708 TABLE [5740-6108] --><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>
@@ -281,8 +260,10 @@ Valid in: Schematic and Symbol files<br/>
</ul>
<p>
- Example:<br/>
-
+
+Example:<br/>
+
+
</p>
<pre class="code">L 23000 69000 28000 69000 3 40 0 1 -1 75</pre>
@@ -291,59 +272,61 @@ A line segment from (23000, 69000) to (28000, 69000) with color index 3, 40 mils
</p>
</div>
-<!-- SECTION "line" [5598-6832] -->
-<h3><a name="picture" id="picture">picture</a></h3>
+<!-- EDIT707 SECTION "line" [5608-6842] -->
+<h3 class="sectionedit709"><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/>
+
+<strong><code>type x1 y1 width height angle ratio mirrored embedded<br/>
filename<br/>
[encoded picture data<br/>
-encoded picture end]</code></strong>
+encoded picture end]</code></strong>
+
</p>
-<table class="inline">
- <tr>
- <th>Field</th><th>Type/unit</th><th>Description</th>
+<div class="table sectionedit710"><table class="inline">
+ <tr class="row0">
+ <th class="col0">Field</th><th class="col1">Type/unit</th><th class="col2">Description</th>
</tr>
- <tr>
- <td>type</td><td>char</td><td>G</td>
+ <tr class="row1">
+ <td class="col0">type</td><td class="col1">char</td><td class="col2">G</td>
</tr>
- <tr>
- <td>x</td><td>int/mils</td><td>Lower left X coordinate</td>
+ <tr class="row2">
+ <td class="col0">x</td><td class="col1">int/mils</td><td class="col2">Lower left X coordinate</td>
</tr>
- <tr>
- <td>y</td><td>int/mils</td><td>Lower left Y coordinate</td>
+ <tr class="row3">
+ <td class="col0">y</td><td class="col1">int/mils</td><td class="col2">Lower left Y coordinate</td>
</tr>
- <tr>
- <td>width</td><td>int/mils</td><td>Width of the picture</td>
+ <tr class="row4">
+ <td class="col0">width</td><td class="col1">int/mils</td><td class="col2">Width of the picture</td>
</tr>
- <tr>
- <td>height</td><td>int/mils</td><td>Height of the picture</td>
+ <tr class="row5">
+ <td class="col0">height</td><td class="col1">int/mils</td><td class="col2">Height of the picture</td>
</tr>
- <tr>
- <td>angle</td><td>int/degrees</td><td>Angle of the picture</td>
+ <tr class="row6">
+ <td class="col0">angle</td><td class="col1">int/degrees</td><td class="col2">Angle of the picture</td>
</tr>
- <tr>
- <td>mirrored</td><td>char</td><td>Mirrored or normal picture</td>
+ <tr class="row7">
+ <td class="col0">mirrored</td><td class="col1">char</td><td class="col2">Mirrored or normal picture</td>
</tr>
- <tr>
- <td>embedded</td><td>char</td><td>Embedded or link to the picture file</td>
+ <tr class="row8">
+ <td class="col0">embedded</td><td class="col1">char</td><td class="col2">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 class="row9">
+ <td class="col0">filename</td><td class="col1">string</td><td class="col2">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 class="row10">
+ <td class="col0">encoded picture data</td><td class="col1">string</td><td class="col2">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 class="row11">
+ <td class="col0">encoded picture end</td><td class="col1">string</td><td class="col2">A line containing only a dot character</td>
</tr>
-</table>
-<ul>
+</table></div>
+<!-- EDIT710 TABLE [7021-7553] --><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>
@@ -375,17 +358,22 @@ encoded picture end]</code></strong>
</ul>
<p>
- Example:<br/>
-
+
+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/>
-
+
+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
@@ -395,78 +383,83 @@ BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB
<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.
+
+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" [6833-9626] -->
-<h3><a name="box" id="box">box</a></h3>
+<!-- EDIT709 SECTION "picture" [6843-9636] -->
+<h3 class="sectionedit711"><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>
+
+<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>
+<div class="table sectionedit712"><table class="inline">
+ <tr class="row0">
+ <th class="col0">Field</th><th class="col1">Type/unit</th><th class="col2">Description</th>
</tr>
- <tr>
- <td>type</td><td>char</td><td>B</td>
+ <tr class="row1">
+ <td class="col0">type</td><td class="col1">char</td><td class="col2">B</td>
</tr>
- <tr>
- <td>x</td><td>int/mils</td><td>Lower left hand X coordinate</td>
+ <tr class="row2">
+ <td class="col0">x</td><td class="col1">int/mils</td><td class="col2">Lower left hand X coordinate</td>
</tr>
- <tr>
- <td>y</td><td>int/mils</td><td>Lower left hand Y coordinate</td>
+ <tr class="row3">
+ <td class="col0">y</td><td class="col1">int/mils</td><td class="col2">Lower left hand Y coordinate</td>
</tr>
- <tr>
- <td>width</td><td>int/mils</td><td>Width of the box (x direction)</td>
+ <tr class="row4">
+ <td class="col0">width</td><td class="col1">int/mils</td><td class="col2">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 class="row5">
+ <td class="col0">height</td><td class="col1">int/mils</td><td class="col2">Height of the box (y direction)</td>
</tr>
- <tr>
- <td>color</td><td>int</td><td>Color index</td>
+ <tr class="row6">
+ <td class="col0">color</td><td class="col1">int</td><td class="col2">Color index</td>
</tr>
- <tr>
- <td>width</td><td>int/mils</td><td>Width of lines</td>
+ <tr class="row7">
+ <td class="col0">width</td><td class="col1">int/mils</td><td class="col2">Width of lines</td>
</tr>
- <tr>
- <td>capstyle</td><td>int/mils</td><td>Line cap style</td>
+ <tr class="row8">
+ <td class="col0">capstyle</td><td class="col1">int/mils</td><td class="col2">Line cap style</td>
</tr>
- <tr>
- <td>dashstyle</td><td>int</td><td>Type of dash style</td>
+ <tr class="row9">
+ <td class="col0">dashstyle</td><td class="col1">int</td><td class="col2">Type of dash style</td>
</tr>
- <tr>
- <td>dashlength</td><td>int/mils</td><td>Length of dash</td>
+ <tr class="row10">
+ <td class="col0">dashlength</td><td class="col1">int/mils</td><td class="col2">Length of dash</td>
</tr>
- <tr>
- <td>dashspace</td><td>int/mils</td><td>Space inbetween dashes</td>
+ <tr class="row11">
+ <td class="col0">dashspace</td><td class="col1">int/mils</td><td class="col2">Space inbetween dashes</td>
</tr>
- <tr>
- <td>filltype</td><td>int</td><td>Type of fill</td>
+ <tr class="row12">
+ <td class="col0">filltype</td><td class="col1">int</td><td class="col2">Type of fill</td>
</tr>
- <tr>
- <td>fillwidth</td><td>int/mils</td><td>Width of the fill lines</td>
+ <tr class="row13">
+ <td class="col0">fillwidth</td><td class="col1">int/mils</td><td class="col2">Width of the fill lines</td>
</tr>
- <tr>
- <td>angle1</td><td>int/degrees</td><td>First angle of fill</td>
+ <tr class="row14">
+ <td class="col0">angle1</td><td class="col1">int/degrees</td><td class="col2">First angle of fill</td>
</tr>
- <tr>
- <td>pitch1</td><td>int/mils</td><td>First pitch/spacing of fill</td>
+ <tr class="row15">
+ <td class="col0">pitch1</td><td class="col1">int/mils</td><td class="col2">First pitch/spacing of fill</td>
</tr>
- <tr>
- <td>angle2</td><td>int/degrees</td><td>Second angle of fill</td>
+ <tr class="row16">
+ <td class="col0">angle2</td><td class="col1">int/degrees</td><td class="col2">Second angle of fill</td>
</tr>
- <tr>
- <td>pitch2</td><td>int/mils</td><td>Second pitch/spacing of fill</td>
+ <tr class="row17">
+ <td class="col0">pitch2</td><td class="col1">int/mils</td><td class="col2">Second pitch/spacing of fill</td>
</tr>
-</table>
-<ul>
+</table></div>
+<!-- EDIT712 TABLE [9819-10500] --><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>
@@ -520,8 +513,10 @@ filltype fillwidth angle1 pitch1 angle2 pitch2</code></strong>
</ul>
<p>
- Example:<br/>
-
+
+Example:<br/>
+
+
</p>
<pre class="code">B 33000 67300 2000 2000 3 60 0 2 75 50 0 -1 -1 -1 -1 -1</pre>
@@ -530,69 +525,71 @@ A box with the lower left hand corner at (33000, 67300) and a width and height o
</p>
</div>
-<!-- SECTION "box" [9627-11833] -->
-<h3><a name="circle" id="circle">circle</a></h3>
+<!-- EDIT711 SECTION "box" [9637-11843] -->
+<h3 class="sectionedit713"><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>
+
+<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>
+<div class="table sectionedit714"><table class="inline">
+ <tr class="row0">
+ <th class="col0">Field</th><th class="col1">Type/unit</th><th class="col2">Description</th>
</tr>
- <tr>
- <td>type</td><td>char</td><td>V</td>
+ <tr class="row1">
+ <td class="col0">type</td><td class="col1">char</td><td class="col2">V</td>
</tr>
- <tr>
- <td>x</td><td>int/mils</td><td>Center X coordinate</td>
+ <tr class="row2">
+ <td class="col0">x</td><td class="col1">int/mils</td><td class="col2">Center X coordinate</td>
</tr>
- <tr>
- <td>y</td><td>int/mils</td><td>Center Y coordinate</td>
+ <tr class="row3">
+ <td class="col0">y</td><td class="col1">int/mils</td><td class="col2">Center Y coordinate</td>
</tr>
- <tr>
- <td>radius</td><td>int/mils</td><td>Radius of the circle</td>
+ <tr class="row4">
+ <td class="col0">radius</td><td class="col1">int/mils</td><td class="col2">Radius of the circle</td>
</tr>
- <tr>
- <td>color</td><td>int</td><td>Color index</td>
+ <tr class="row5">
+ <td class="col0">color</td><td class="col1">int</td><td class="col2">Color index</td>
</tr>
- <tr>
- <td>width</td><td>int/mils</td><td>Width of circle line</td>
+ <tr class="row6">
+ <td class="col0">width</td><td class="col1">int/mils</td><td class="col2">Width of circle line</td>
</tr>
- <tr>
- <td>capstyle</td><td>int/mils</td><td>0 unused</td>
+ <tr class="row7">
+ <td class="col0">capstyle</td><td class="col1">int/mils</td><td class="col2">0 unused</td>
</tr>
- <tr>
- <td>dashstyle</td><td>int</td><td>Type of dash style</td>
+ <tr class="row8">
+ <td class="col0">dashstyle</td><td class="col1">int</td><td class="col2">Type of dash style</td>
</tr>
- <tr>
- <td>dashlength</td><td>int/mils</td><td>Length of dash</td>
+ <tr class="row9">
+ <td class="col0">dashlength</td><td class="col1">int/mils</td><td class="col2">Length of dash</td>
</tr>
- <tr>
- <td>dashspace</td><td>int/mils</td><td>Space inbetween dashes</td>
+ <tr class="row10">
+ <td class="col0">dashspace</td><td class="col1">int/mils</td><td class="col2">Space inbetween dashes</td>
</tr>
- <tr>
- <td>filltype</td><td>int</td><td>Type of fill</td>
+ <tr class="row11">
+ <td class="col0">filltype</td><td class="col1">int</td><td class="col2">Type of fill</td>
</tr>
- <tr>
- <td>fillwidth</td><td>int/mils</td><td>Width of the fill lines</td>
+ <tr class="row12">
+ <td class="col0">fillwidth</td><td class="col1">int/mils</td><td class="col2">Width of the fill lines</td>
</tr>
- <tr>
- <td>angle1</td><td>int/degrees</td><td>First angle of fill</td>
+ <tr class="row13">
+ <td class="col0">angle1</td><td class="col1">int/degrees</td><td class="col2">First angle of fill</td>
</tr>
- <tr>
- <td>pitch1</td><td>int/mils</td><td>First pitch/spacing of fill</td>
+ <tr class="row14">
+ <td class="col0">pitch1</td><td class="col1">int/mils</td><td class="col2">First pitch/spacing of fill</td>
</tr>
- <tr>
- <td>angle2</td><td>int/degrees</td><td>Second angle of fill</td>
+ <tr class="row15">
+ <td class="col0">angle2</td><td class="col1">int/degrees</td><td class="col2">Second angle of fill</td>
</tr>
- <tr>
- <td>pitch2</td><td>int/mils</td><td>Second pitch/spacing of fill</td>
+ <tr class="row16">
+ <td class="col0">pitch2</td><td class="col1">int/mils</td><td class="col2">Second pitch/spacing of fill</td>
</tr>
-</table>
-<ul>
+</table></div>
+<!-- EDIT714 TABLE [12023-12627] --><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>
@@ -636,8 +633,10 @@ filltype fillwidth angle1 pitch1 angle2 pitch2</code></strong>
</ul>
<p>
- Example:<br/>
-
+
+Example:<br/>
+
+
</p>
<pre class="code">V 38000 67000 900 3 0 0 2 75 50 2 10 20 30 90 50</pre>
@@ -646,57 +645,59 @@ A circle with the center at (38000, 67000) and a radius of 900 mils, color index
</p>
</div>
-<!-- SECTION "circle" [11834-13959] -->
-<h3><a name="arc" id="arc">arc</a></h3>
+<!-- EDIT713 SECTION "circle" [11844-13969] -->
+<h3 class="sectionedit715"><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>
+
+<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>
+<div class="table sectionedit716"><table class="inline">
+ <tr class="row0">
+ <th class="col0">Field</th><th class="col1">Type/unit</th><th class="col2">Description</th>
</tr>
- <tr>
- <td>type</td><td>char</td><td>A</td>
+ <tr class="row1">
+ <td class="col0">type</td><td class="col1">char</td><td class="col2">A</td>
</tr>
- <tr>
- <td>x</td><td>int/mils</td><td>Center X coordinate</td>
+ <tr class="row2">
+ <td class="col0">x</td><td class="col1">int/mils</td><td class="col2">Center X coordinate</td>
</tr>
- <tr>
- <td>y</td><td>int/mils</td><td>Center Y coordinate</td>
+ <tr class="row3">
+ <td class="col0">y</td><td class="col1">int/mils</td><td class="col2">Center Y coordinate</td>
</tr>
- <tr>
- <td>radius</td><td>int/mils</td><td>Radius of the arc</td>
+ <tr class="row4">
+ <td class="col0">radius</td><td class="col1">int/mils</td><td class="col2">Radius of the arc</td>
</tr>
- <tr>
- <td>startangle</td><td>int/degrees</td><td>Starting angle of the arc</td>
+ <tr class="row5">
+ <td class="col0">startangle</td><td class="col1">int/degrees</td><td class="col2">Starting angle of the arc</td>
</tr>
- <tr>
- <td>sweepangle</td><td>int/degrees</td><td>Amount the arc sweeps</td>
+ <tr class="row6">
+ <td class="col0">sweepangle</td><td class="col1">int/degrees</td><td class="col2">Amount the arc sweeps</td>
</tr>
- <tr>
- <td>color</td><td>int</td><td>Color index</td>
+ <tr class="row7">
+ <td class="col0">color</td><td class="col1">int</td><td class="col2">Color index</td>
</tr>
- <tr>
- <td>width</td><td>int/mils</td><td>Width of circle line</td>
+ <tr class="row8">
+ <td class="col0">width</td><td class="col1">int/mils</td><td class="col2">Width of circle line</td>
</tr>
- <tr>
- <td>capstyle</td><td>int</td><td>Cap style</td>
+ <tr class="row9">
+ <td class="col0">capstyle</td><td class="col1">int</td><td class="col2">Cap style</td>
</tr>
- <tr>
- <td>dashstyle</td><td>int</td><td>Type of dash style</td>
+ <tr class="row10">
+ <td class="col0">dashstyle</td><td class="col1">int</td><td class="col2">Type of dash style</td>
</tr>
- <tr>
- <td>dashlength</td><td>int/mils</td><td>Length of dash</td>
+ <tr class="row11">
+ <td class="col0">dashlength</td><td class="col1">int/mils</td><td class="col2">Length of dash</td>
</tr>
- <tr>
- <td>dashspace</td><td>int/mils</td><td>Space inbetween dashes</td>
+ <tr class="row12">
+ <td class="col0">dashspace</td><td class="col1">int/mils</td><td class="col2">Space inbetween dashes</td>
</tr>
-</table>
-<ul>
+</table></div>
+<!-- EDIT716 TABLE [14121-14567] --><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>
@@ -732,23 +733,27 @@ dashlength dashspace</code></strong>
</ul>
<p>
- Example:<br/>
-
+
+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.
+
+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" [13960-15476] -->
-<h3><a name="text" id="text">text</a></h3>
+<!-- EDIT715 SECTION "arc" [13970-15486] -->
+<h3 class="sectionedit717"><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/>
+
+<strong><code>type x y color size visibility show_name_value angle alignment num_lines<br/>
string line 1<br/>
@@ -756,52 +761,53 @@ string line 2<br/>
string line 3<br/>
-…<br/>
+â?¦<br/>
+
+string line N</code></strong>
-string line N</code></strong>
</p>
-<table class="inline">
- <tr>
- <th>Field</th><th>Type/unit</th><th>Description</th>
+<div class="table sectionedit718"><table class="inline">
+ <tr class="row0">
+ <th class="col0">Field</th><th class="col1">Type/unit</th><th class="col2">Description</th>
</tr>
- <tr>
- <td>type</td><td>char</td><td>T</td>
+ <tr class="row1">
+ <td class="col0">type</td><td class="col1">char</td><td class="col2">T</td>
</tr>
- <tr>
- <td>x</td><td>int/mils</td><td>First X coordinate</td>
+ <tr class="row2">
+ <td class="col0">x</td><td class="col1">int/mils</td><td class="col2">First X coordinate</td>
</tr>
- <tr>
- <td>y</td><td>int/mils</td><td>First Y coordinate</td>
+ <tr class="row3">
+ <td class="col0">y</td><td class="col1">int/mils</td><td class="col2">First Y coordinate</td>
</tr>
- <tr>
- <td>color</td><td>int</td><td>Color index</td>
+ <tr class="row4">
+ <td class="col0">color</td><td class="col1">int</td><td class="col2">Color index</td>
</tr>
- <tr>
- <td>size</td><td>int/points</td><td>Size of text</td>
+ <tr class="row5">
+ <td class="col0">size</td><td class="col1">int/points</td><td class="col2">Size of text</td>
</tr>
- <tr>
- <td>visibility</td><td>int</td><td>Visibility of text</td>
+ <tr class="row6">
+ <td class="col0">visibility</td><td class="col1">int</td><td class="col2">Visibility of text</td>
</tr>
- <tr>
- <td>show_name_value</td><td>int</td><td>Attribute visibility control</td>
+ <tr class="row7">
+ <td class="col0">show_name_value</td><td class="col1">int</td><td class="col2">Attribute visibility control</td>
</tr>
- <tr>
- <td>angle</td><td>int/degrees</td><td>Angle of the text</td>
+ <tr class="row8">
+ <td class="col0">angle</td><td class="col1">int/degrees</td><td class="col2">Angle of the text</td>
</tr>
- <tr>
- <td>alignment</td><td>int</td><td>Alignment/origin of the text</td>
+ <tr class="row9">
+ <td class="col0">alignment</td><td class="col1">int</td><td class="col2">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 class="row10">
+ <td class="col0">num_lines</td><td class="col1">int</td><td class="col2">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 class="row11">
+ <td class="col0">string line 1 â?¦ N</td><td class="col1">string</td><td class="col2">The text strings, on a seperate line</td>
</tr>
-</table>
-<ul>
+</table></div>
+<!-- EDIT718 TABLE [15693-16141] --><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 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>
@@ -836,16 +842,16 @@ string line N</code></strong>
<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>
+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>
+ <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>
+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>
@@ -853,18 +859,21 @@ string line N</code></strong>
<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!
+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
@@ -879,7 +888,8 @@ This is a similar text object as the above example, however here there are five
<p>
Example3:<br/>
-
+
+
</p>
<pre class="code">T 10000 20000 3 10 1 1 8 90 1
pinlabel=R/\_W\_</pre>
@@ -889,38 +899,40 @@ A text object with the origin at (10000, 20000), color index 3, 10 points in siz
</p>
</div>
-<!-- SECTION "text" [15477-18631] -->
-<h3><a name="net" id="net">net</a></h3>
+<!-- EDIT717 SECTION "text" [15487-18641] -->
+<h3 class="sectionedit719"><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>
+
+<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>
+<div class="table sectionedit720"><table class="inline">
+ <tr class="row0">
+ <th class="col0">Field</th><th class="col1">Type/unit</th><th class="col2">Description</th>
</tr>
- <tr>
- <td>type</td><td>char</td><td>N</td>
+ <tr class="row1">
+ <td class="col0">type</td><td class="col1">char</td><td class="col2">N</td>
</tr>
- <tr>
- <td>x1</td><td>int/mils</td><td>First X coordinate</td>
+ <tr class="row2">
+ <td class="col0">x1</td><td class="col1">int/mils</td><td class="col2">First X coordinate</td>
</tr>
- <tr>
- <td>y1</td><td>int/mils</td><td>First Y coordinate</td>
+ <tr class="row3">
+ <td class="col0">y1</td><td class="col1">int/mils</td><td class="col2">First Y coordinate</td>
</tr>
- <tr>
- <td>x2</td><td>int/mils</td><td>Second X coordinate</td>
+ <tr class="row4">
+ <td class="col0">x2</td><td class="col1">int/mils</td><td class="col2">Second X coordinate</td>
</tr>
- <tr>
- <td>y2</td><td>int/mils</td><td>Second Y coordinate</td>
+ <tr class="row5">
+ <td class="col0">y2</td><td class="col1">int/mils</td><td class="col2">Second Y coordinate</td>
</tr>
- <tr>
- <td>color</td><td>int</td><td>Color index</td>
+ <tr class="row6">
+ <td class="col0">color</td><td class="col1">int</td><td class="col2">Color index</td>
</tr>
-</table>
-<ul>
+</table></div>
+<!-- EDIT720 TABLE [18721-18922] --><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>
@@ -928,8 +940,10 @@ Valid in: Schematic files ONLY<br/>
</ul>
<p>
- Example:<br/>
-
+
+Example:<br/>
+
+
</p>
<pre class="code">N 12700 29400 32900 29400 4</pre>
@@ -938,41 +952,43 @@ A net segment from (12700, 29400) to (32900, 29400) with color index 4.
</p>
</div>
-<!-- SECTION "net" [18632-19157] -->
-<h3><a name="bus" id="bus">bus</a></h3>
+<!-- EDIT719 SECTION "net" [18642-19167] -->
+<h3 class="sectionedit721"><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>
+
+<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>
+<div class="table sectionedit722"><table class="inline">
+ <tr class="row0">
+ <th class="col0">Field</th><th class="col1">Type/unit</th><th class="col2">Description</th>
</tr>
- <tr>
- <td>type</td><td>char</td><td>U</td>
+ <tr class="row1">
+ <td class="col0">type</td><td class="col1">char</td><td class="col2">U</td>
</tr>
- <tr>
- <td>x1</td><td>int/mils</td><td>First X coordinate</td>
+ <tr class="row2">
+ <td class="col0">x1</td><td class="col1">int/mils</td><td class="col2">First X coordinate</td>
</tr>
- <tr>
- <td>y1</td><td>int/mils</td><td>First Y coordinate</td>
+ <tr class="row3">
+ <td class="col0">y1</td><td class="col1">int/mils</td><td class="col2">First Y coordinate</td>
</tr>
- <tr>
- <td>x2</td><td>int/mils</td><td>Second X coordinate</td>
+ <tr class="row4">
+ <td class="col0">x2</td><td class="col1">int/mils</td><td class="col2">Second X coordinate</td>
</tr>
- <tr>
- <td>y2</td><td>int/mils</td><td>Second Y coordinate</td>
+ <tr class="row5">
+ <td class="col0">y2</td><td class="col1">int/mils</td><td class="col2">Second Y coordinate</td>
</tr>
- <tr>
- <td>color</td><td>int</td><td>Color index</td>
+ <tr class="row6">
+ <td class="col0">color</td><td class="col1">int</td><td class="col2">Color index</td>
</tr>
- <tr>
- <td>ripperdir</td><td>int</td><td>Direction of bus rippers</td>
+ <tr class="row7">
+ <td class="col0">ripperdir</td><td class="col1">int</td><td class="col2">Direction of bus rippers</td>
</tr>
-</table>
-<ul>
+</table></div>
+<!-- EDIT722 TABLE [19257-19499] --><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>
@@ -984,8 +1000,10 @@ Valid in: Schematic files ONLY<br/>
</ul>
<p>
- Example:<br/>
-
+
+Example:<br/>
+
+
</p>
<pre class="code">U 27300 37400 27300 35300 3 0</pre>
@@ -994,44 +1012,46 @@ A bus segment from (27300, 37400) to (27300, 35300) with color index 3 and no ne
</p>
</div>
-<!-- SECTION "bus" [19158-20089] -->
-<h3><a name="pin" id="pin">pin</a></h3>
+<!-- EDIT721 SECTION "bus" [19168-20099] -->
+<h3 class="sectionedit723"><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>
+
+<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>
+<div class="table sectionedit724"><table class="inline">
+ <tr class="row0">
+ <th class="col0">Field</th><th class="col1">Type/unit</th><th class="col2">Description</th>
</tr>
- <tr>
- <td>type</td><td>char</td><td>P</td>
+ <tr class="row1">
+ <td class="col0">type</td><td class="col1">char</td><td class="col2">P</td>
</tr>
- <tr>
- <td>x1</td><td>int/mils</td><td>First X coordinate</td>
+ <tr class="row2">
+ <td class="col0">x1</td><td class="col1">int/mils</td><td class="col2">First X coordinate</td>
</tr>
- <tr>
- <td>y1</td><td>int/mils</td><td>First Y coordinate</td>
+ <tr class="row3">
+ <td class="col0">y1</td><td class="col1">int/mils</td><td class="col2">First Y coordinate</td>
</tr>
- <tr>
- <td>x2</td><td>int/mils</td><td>Second X coordinate</td>
+ <tr class="row4">
+ <td class="col0">x2</td><td class="col1">int/mils</td><td class="col2">Second X coordinate</td>
</tr>
- <tr>
- <td>y2</td><td>int/mils</td><td>Second Y coordinate</td>
+ <tr class="row5">
+ <td class="col0">y2</td><td class="col1">int/mils</td><td class="col2">Second Y coordinate</td>
</tr>
- <tr>
- <td>color</td><td>int</td><td>Color index</td>
+ <tr class="row6">
+ <td class="col0">color</td><td class="col1">int</td><td class="col2">Color index</td>
</tr>
- <tr>
- <td>pintype</td><td>int</td><td>Type of pin</td>
+ <tr class="row7">
+ <td class="col0">pintype</td><td class="col1">int</td><td class="col2">Type of pin</td>
</tr>
- <tr>
- <td>whichend</td><td>int</td><td>Specifies the active end</td>
+ <tr class="row8">
+ <td class="col0">whichend</td><td class="col1">int</td><td class="col2">Specifies the active end</td>
</tr>
-</table>
-<ul>
+</table></div>
+<!-- EDIT724 TABLE [20193-20460] --><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>
@@ -1051,8 +1071,10 @@ Valid in: Symbol files ONLY<br/>
</ul>
<p>
- Example:<br/>
-
+
+Example:<br/>
+
+
</p>
<pre class="code">P 0 200 200 200 1 0 0</pre>
@@ -1061,43 +1083,46 @@ A pin from (0, 200) to (200, 200) with color index 1, a regular pin, and the fir
</p>
</div>
-<!-- SECTION "pin" [20090-21086] -->
-<h3><a name="component" id="component">component</a></h3>
+<!-- EDIT723 SECTION "pin" [20100-21096] -->
+<h3 class="sectionedit725"><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>
+
+<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>
+<div class="table sectionedit726"><table class="inline">
+ <tr class="row0">
+ <th class="col0">Field</th><th class="col1">Type/unit</th><th class="col2">Description</th>
</tr>
- <tr>
- <td>type</td><td>char</td><td>C</td>
+ <tr class="row1">
+ <td class="col0">type</td><td class="col1">char</td><td class="col2">C</td>
</tr>
- <tr>
- <td>x</td><td>int/mils</td><td>Origin X coordinate</td>
+ <tr class="row2">
+ <td class="col0">x</td><td class="col1">int/mils</td><td class="col2">Origin X coordinate</td>
</tr>
- <tr>
- <td>y</td><td>int/mils</td><td>Origin Y coordinate</td>
+ <tr class="row3">
+ <td class="col0">y</td><td class="col1">int/mils</td><td class="col2">Origin Y coordinate</td>
</tr>
- <tr>
- <td>selectable</td><td>int</td><td>Selectable flag</td>
+ <tr class="row4">
+ <td class="col0">selectable</td><td class="col1">int</td><td class="col2">Selectable flag</td>
</tr>
- <tr>
- <td>angle</td><td>int/degrees</td><td>Angle of the component</td>
+ <tr class="row5">
+ <td class="col0">angle</td><td class="col1">int/degrees</td><td class="col2">Angle of the component</td>
</tr>
- <tr>
- <td>mirror</td><td>int</td><td>Mirror around Y axis</td>
+ <tr class="row6">
+ <td class="col0">mirror</td><td class="col1">int</td><td class="col2">Mirror around Y axis</td>
</tr>
- <tr>
- <td>basename</td><td>string</td><td>The filename of the component</td>
+ <tr class="row7">
+ <td class="col0">basename</td><td class="col1">string</td><td class="col2">The filename of the component</td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT726 TABLE [21201-21468] -->
<p>
- The selectable field is either 1 for selectable or 0 if not selectable.
+
+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>
@@ -1113,24 +1138,28 @@ Valid in: Schematic files ONLY<br/>
</ul>
<p>
- Example:<br/>
-
+
+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.
+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" [21087-22091] -->
-<h3><a name="path" id="path">path</a></h3>
+<!-- EDIT725 SECTION "component" [21097-22101] -->
+<h3 class="sectionedit727"><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/>
+
+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/>
@@ -1138,61 +1167,62 @@ path data line 2<br/>
path data line 3<br/>
-…<br/>
+â?¦<br/>
+
+path data line N</code></strong>
-path data line N</code></strong>
</p>
-<table class="inline">
- <tr>
- <th>Field</th><th>Type/unit</th><th>Description</th>
+<div class="table sectionedit728"><table class="inline">
+ <tr class="row0">
+ <th class="col0">Field</th><th class="col1">Type/unit</th><th class="col2">Description</th>
</tr>
- <tr>
- <td>type</td><td>char</td><td>H</td>
+ <tr class="row1">
+ <td class="col0">type</td><td class="col1">char</td><td class="col2">H</td>
</tr>
- <tr>
- <td>color</td><td>int</td><td>Color index</td>
+ <tr class="row2">
+ <td class="col0">color</td><td class="col1">int</td><td class="col2">Color index</td>
</tr>
- <tr>
- <td>width</td><td>int/mils</td><td>Width of line</td>
+ <tr class="row3">
+ <td class="col0">width</td><td class="col1">int/mils</td><td class="col2">Width of line</td>
</tr>
- <tr>
- <td>capstyle</td><td>int</td><td>Line cap style</td>
+ <tr class="row4">
+ <td class="col0">capstyle</td><td class="col1">int</td><td class="col2">Line cap style</td>
</tr>
- <tr>
- <td>dashstyle</td><td>int</td><td>Type of dash style</td>
+ <tr class="row5">
+ <td class="col0">dashstyle</td><td class="col1">int</td><td class="col2">Type of dash style</td>
</tr>
- <tr>
- <td>dashlength</td><td>int</td><td>Length of dash</td>
+ <tr class="row6">
+ <td class="col0">dashlength</td><td class="col1">int</td><td class="col2">Length of dash</td>
</tr>
- <tr>
- <td>dashspace</td><td>int</td><td>Space inbetween dashes</td>
+ <tr class="row7">
+ <td class="col0">dashspace</td><td class="col1">int</td><td class="col2">Space inbetween dashes</td>
</tr>
- <tr>
- <td>filltype</td><td>int</td><td>Type of fill</td>
+ <tr class="row8">
+ <td class="col0">filltype</td><td class="col1">int</td><td class="col2">Type of fill</td>
</tr>
- <tr>
- <td>fillwidth</td><td>int/mils</td><td>Width of the fill lines</td>
+ <tr class="row9">
+ <td class="col0">fillwidth</td><td class="col1">int/mils</td><td class="col2">Width of the fill lines</td>
</tr>
- <tr>
- <td>angle1</td><td>int/degrees</td><td>First angle of fill</td>
+ <tr class="row10">
+ <td class="col0">angle1</td><td class="col1">int/degrees</td><td class="col2">First angle of fill</td>
</tr>
- <tr>
- <td>pitch1</td><td>int/mils</td><td>First pitch/spacing of fill</td>
+ <tr class="row11">
+ <td class="col0">pitch1</td><td class="col1">int/mils</td><td class="col2">First pitch/spacing of fill</td>
</tr>
- <tr>
- <td>angle2</td><td>int/degrees</td><td>Second angle of fill</td>
+ <tr class="row12">
+ <td class="col0">angle2</td><td class="col1">int/degrees</td><td class="col2">Second angle of fill</td>
</tr>
- <tr>
- <td>pitch2</td><td>int/mils</td><td>Second pitch/spacing of fill</td>
+ <tr class="row13">
+ <td class="col0">pitch2</td><td class="col1">int/mils</td><td class="col2">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 class="row14">
+ <td class="col0">num_lines</td><td class="col1">int</td><td class="col2">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 class="row15">
+ <td class="col0">path data line 1 â?¦ N</td><td class="col1">path data</td><td class="col2">The path data, on seperate lines</td>
</tr>
-</table>
-<ul>
+</table></div>
+<!-- EDIT728 TABLE [22412-23018] --><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>
@@ -1260,7 +1290,9 @@ path data line N</code></strong>
</ul>
<p>
- Example:
+
+Example:
+
</p>
<pre class="code">H 3 10 0 0 -1 -1 0 -1 -1 -1 -1 -1 5
M 410,240
@@ -1274,32 +1306,34 @@ A path starting at (410,240) with lines drawn from there, and joining points (50
</p>
</div>
-<!-- SECTION "path" [22092-24942] -->
-<h3><a name="font" id="font">font</a></h3>
+<!-- EDIT727 SECTION "path" [22102-24952] -->
+<h3 class="sectionedit729"><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>
+
+<strong><code>type character width flag</code></strong>
+
</p>
-<table class="inline">
- <tr>
- <th>Field</th><th>Type/unit</th><th>Description</th>
+<div class="table sectionedit730"><table class="inline">
+ <tr class="row0">
+ <th class="col0">Field</th><th class="col1">Type/unit</th><th class="col2">Description</th>
</tr>
- <tr>
- <td>type</td><td>char</td><td>F</td>
+ <tr class="row1">
+ <td class="col0">type</td><td class="col1">char</td><td class="col2">F</td>
</tr>
- <tr>
- <td>character</td><td>char</td><td>The character being defined</td>
+ <tr class="row2">
+ <td class="col0">character</td><td class="col1">char</td><td class="col2">The character being defined</td>
</tr>
- <tr>
- <td>width</td><td>int/mils</td><td>Width of the character (mils)</td>
+ <tr class="row3">
+ <td class="col0">width</td><td class="col1">int/mils</td><td class="col2">Width of the character (mils)</td>
</tr>
- <tr>
- <td>flag</td><td>int</td><td>Special space flag</td>
+ <tr class="row4">
+ <td class="col0">flag</td><td class="col1">int</td><td class="col2">Special space flag</td>
</tr>
-</table>
-<ul>
+</table></div>
+<!-- EDIT730 TABLE [25039-25204] --><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>
@@ -1307,8 +1341,10 @@ Valid in: Special font files ONLY<br/>
</ul>
<p>
- Example:<br/>
-
+
+Example:<br/>
+
+
</p>
<pre class="code">F 11 1</pre>
@@ -1317,102 +1353,105 @@ The above font definition is for the space character.
</p>
</div>
-<!-- SECTION "font" [24943-25464] -->
-<h2><a name="colors" id="colors">Colors</a></h2>
+<!-- EDIT729 SECTION "font" [24953-25474] -->
+<h2 class="sectionedit731"><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:
+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>
+<div class="table sectionedit732"><table class="inline">
+ <tr class="row0">
+ <th class="col0">Index</th><th class="col1">Object type</th>
</tr>
- <tr>
- <td>0</td><td>BACKGROUND_COLOR</td>
+ <tr class="row1">
+ <td class="col0">0</td><td class="col1">BACKGROUND_COLOR</td>
</tr>
- <tr>
- <td>1</td><td><acronym title="Personal Identification Number">PIN</acronym>_COLOR</td>
+ <tr class="row2">
+ <td class="col0">1</td><td class="col1"><acronym title="Personal Identification Number">PIN</acronym>_COLOR</td>
</tr>
- <tr>
- <td>2</td><td>NET_ENDPOINT_COLOR</td>
+ <tr class="row3">
+ <td class="col0">2</td><td class="col1">NET_ENDPOINT_COLOR</td>
</tr>
- <tr>
- <td>3</td><td>GRAPHIC_COLOR</td>
+ <tr class="row4">
+ <td class="col0">3</td><td class="col1">GRAPHIC_COLOR</td>
</tr>
- <tr>
- <td>4</td><td>NET_COLOR</td>
+ <tr class="row5">
+ <td class="col0">4</td><td class="col1">NET_COLOR</td>
</tr>
- <tr>
- <td>5</td><td>ATTRIBUTE_COLOR</td>
+ <tr class="row6">
+ <td class="col0">5</td><td class="col1">ATTRIBUTE_COLOR</td>
</tr>
- <tr>
- <td>6</td><td>LOGIC_BUBBLE_COLOR</td>
+ <tr class="row7">
+ <td class="col0">6</td><td class="col1">LOGIC_BUBBLE_COLOR</td>
</tr>
- <tr>
- <td>7</td><td>DOTS_GRID_COLOR</td>
+ <tr class="row8">
+ <td class="col0">7</td><td class="col1">DOTS_GRID_COLOR</td>
</tr>
- <tr>
- <td>8</td><td>DETACHED_ATTRIBUTE_COLOR</td>
+ <tr class="row9">
+ <td class="col0">8</td><td class="col1">DETACHED_ATTRIBUTE_COLOR</td>
</tr>
- <tr>
- <td>9</td><td>TEXT_COLOR</td>
+ <tr class="row10">
+ <td class="col0">9</td><td class="col1">TEXT_COLOR</td>
</tr>
- <tr>
- <td>10</td><td>BUS_COLOR</td>
+ <tr class="row11">
+ <td class="col0">10</td><td class="col1">BUS_COLOR</td>
</tr>
- <tr>
- <td>11</td><td>SELECT_COLOR</td>
+ <tr class="row12">
+ <td class="col0">11</td><td class="col1">SELECT_COLOR</td>
</tr>
- <tr>
- <td>12</td><td>BOUNDINGBOX_COLOR</td>
+ <tr class="row13">
+ <td class="col0">12</td><td class="col1">BOUNDINGBOX_COLOR</td>
</tr>
- <tr>
- <td>13</td><td>ZOOM_BOX_COLOR</td>
+ <tr class="row14">
+ <td class="col0">13</td><td class="col1">ZOOM_BOX_COLOR</td>
</tr>
- <tr>
- <td>14</td><td>STROKE_COLOR</td>
+ <tr class="row15">
+ <td class="col0">14</td><td class="col1">STROKE_COLOR</td>
</tr>
- <tr>
- <td>15</td><td>LOCK_COLOR</td>
+ <tr class="row16">
+ <td class="col0">15</td><td class="col1">LOCK_COLOR</td>
</tr>
- <tr>
- <td>16</td><td>OUTPUT_BACKGROUND_COLOR</td>
+ <tr class="row17">
+ <td class="col0">16</td><td class="col1">OUTPUT_BACKGROUND_COLOR</td>
</tr>
- <tr>
- <td>17</td><td>FREESTYLE1_COLOR</td>
+ <tr class="row18">
+ <td class="col0">17</td><td class="col1">FREESTYLE1_COLOR</td>
</tr>
- <tr>
- <td>18</td><td>FREESTYLE2_COLOR</td>
+ <tr class="row19">
+ <td class="col0">18</td><td class="col1">FREESTYLE2_COLOR</td>
</tr>
- <tr>
- <td>19</td><td>FREESTYLE3_COLOR</td>
+ <tr class="row20">
+ <td class="col0">19</td><td class="col1">FREESTYLE3_COLOR</td>
</tr>
- <tr>
- <td>20</td><td>FREESTYLE4_COLOR</td>
+ <tr class="row21">
+ <td class="col0">20</td><td class="col1">FREESTYLE4_COLOR</td>
</tr>
- <tr>
- <td>21</td><td>JUNCTION_COLOR</td>
+ <tr class="row22">
+ <td class="col0">21</td><td class="col1">JUNCTION_COLOR</td>
</tr>
- <tr>
- <td>22</td><td>MESH_GRID_MAJOR_COLOR</td>
+ <tr class="row23">
+ <td class="col0">22</td><td class="col1">MESH_GRID_MAJOR_COLOR</td>
</tr>
- <tr>
- <td>23</td><td>MESH_GRID_MINOR_COLOR</td>
+ <tr class="row24">
+ <td class="col0">23</td><td class="col1">MESH_GRID_MINOR_COLOR</td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT732 TABLE [25753-26270] -->
<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.
+
+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" [25465-26503] -->
-<h2><a name="attributes" id="attributes">Attributes</a></h2>
+<!-- EDIT731 SECTION "Colors" [25475-26513] -->
+<h2 class="sectionedit733"><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:
+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
{
@@ -1423,18 +1462,21 @@ 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.
+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" [26504-27491] -->
-<h2><a name="embedded_components" id="embedded_components">Embedded Components</a></h2>
+<!-- EDIT733 SECTION "Attributes" [26514-27501] -->
+<h2 class="sectionedit734"><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:
+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
[
@@ -1448,12 +1490,13 @@ In the example above, <strong>555-1.sym</strong> is the component. The EMBEDDED
</p>
</div>
-<!-- SECTION "Embedded Components" [27492-28256] -->
-<h2><a name="path_data" id="path_data">Path data</a></h2>
+<!-- EDIT734 SECTION "Embedded Components" [27502-28266] -->
+<h2 class="sectionedit735"><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>.
+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>
@@ -1468,7 +1511,8 @@ The gEDA/gaf path data format has been deliberately specified to match a subset
</ul>
<p>
-(Text taken from the above <acronym title="Scalable Vector Graphics">SVG</acronym> specification).
+(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>
@@ -1480,38 +1524,39 @@ The gEDA/gaf path data format has been deliberately specified to match a subset
</ul>
</li>
</ul>
-<table class="inline">
- <tr>
- <th>Command</th><th>Name</th><th>Parameters</th><th>Description</th>
+<div class="table sectionedit736"><table class="inline">
+ <tr class="row0">
+ <th class="col0">Command</th><th class="col1">Name</th><th class="col2">Parameters</th><th class="col3">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 class="row1">
+ <td class="col0">M (absolute)</td><td class="col1">moveto</td><td class="col2">(x,y)+</td><td class="col3">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 class="row2">
+ <td class="col0">L (absolute)</td><td class="col1">lineto</td><td class="col2">(x,y)+</td><td class="col3">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 class="row3">
+ <td class="col0">C (absolute)</td><td class="col1">curveto</td><td class="col2">(x1,y1 x2,y2 x,y)+</td><td class="col3">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 class="row4">
+ <td class="col0">Z or z</td><td class="col1">closepath</td><td class="col2">(none)</td><td class="col3">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>
+</table></div>
+<!-- EDIT736 TABLE [29114-30693] --><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 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 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 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:
+
+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>
@@ -1537,27 +1582,27 @@ The resulting path (with control points drawn on to illustrate their positions)
</p>
</div>
-<!-- SECTION "Path data" [28257-31685] -->
-<h2><a name="document_revision_history" id="document_revision_history">Document Revision History</a></h2>
+<!-- EDIT735 SECTION "Path data" [28267-31695] -->
+<h2 class="sectionedit737"><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>
+<div class="table sectionedit738"><table class="inline">
+ <tr class="row0">
+ <td class="col0">November 30th, 2002</td><td class="col1">Created fleformats.tex from fleformats.html.</td>
</tr>
- <tr>
- <td>December 1st, 2002</td><td>Continued work on this document.</td>
+ <tr class="row1">
+ <td class="col0">December 1st, 2002</td><td class="col1">Continued work on this document.</td>
</tr>
- <tr>
- <td>October 4th, 2003</td><td>Added new file format version flag info.</td>
+ <tr class="row2">
+ <td class="col0">October 4th, 2003</td><td class="col1">Added new file format version flag info.</td>
</tr>
- <tr>
- <td>October 19th, 2003</td><td>Added num lines text field.</td>
+ <tr class="row3">
+ <td class="col0">October 19th, 2003</td><td class="col1">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 class="row4">
+ <td class="col0">November 2nd, 2008</td><td class="col1">Added path object, bumping file format version to 2</td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT738 TABLE [31734-32037] -->
</div>
-<!-- SECTION "Document Revision History" [31686-] --></body>
+<!-- EDIT737 SECTION "Document Revision History" [31696-] --></body>
</html>
diff --git a/docs/wiki/geda-format_translation.html b/docs/wiki/geda-format_translation.html
index 6c8d8ee..fa6ae3c 100644
--- a/docs/wiki/geda-format_translation.html
+++ b/docs/wiki/geda-format_translation.html
@@ -11,50 +11,23 @@
</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>
+<h1 class="sectionedit754"><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.
+
+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>
+<!-- EDIT754 SECTION "File format translation" [1-225] -->
+<h2 class="sectionedit755"><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.
+
+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>
@@ -62,7 +35,7 @@ The idea is to have an intermediate format. First translate to the intermediate
</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.
+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>
@@ -86,8 +59,8 @@ There needs to be a way to merge changes from any target/source without messing
</p>
</div>
-<!-- SECTION "Scope" [226-1514] -->
-<h3><a name="tool_types_needing_support" id="tool_types_needing_support">Tool types needing support</a></h3>
+<!-- EDIT755 SECTION "Scope" [226-1514] -->
+<h3 class="sectionedit756"><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>
@@ -99,8 +72,8 @@ There needs to be a way to merge changes from any target/source without messing
</ul>
</div>
-<!-- SECTION "Tool types needing support" [1515-1592] -->
-<h3><a name="geda_tools" id="geda_tools">gEDA tools</a></h3>
+<!-- EDIT756 SECTION "Tool types needing support" [1515-1592] -->
+<h3 class="sectionedit757"><a name="geda_tools" id="geda_tools">gEDA tools</a></h3>
<div class="level3">
<p>
@@ -118,8 +91,8 @@ Lossless round trip is required, so archival storage can use the intermediate fo
</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>
+<!-- EDIT757 SECTION "gEDA tools" [1593-1749] -->
+<h3 class="sectionedit758"><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>
@@ -143,12 +116,12 @@ These tools are free, too. The standard needs to support them on an equal basis
</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>
+<!-- EDIT758 SECTION "Other free tools that should be well supported" [1750-1980] -->
+<h3 class="sectionedit759"><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.
+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>
@@ -162,8 +135,8 @@ Support for these will allow gEDA tools to play nice with the commercial world.
</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>
+<!-- EDIT759 SECTION "Non-free import and export" [1981-2293] -->
+<h3 class="sectionedit760"><a name="geda_missing_functionality" id="geda_missing_functionality">gEDA missing functionality</a></h3>
<div class="level3">
<p>
@@ -183,8 +156,8 @@ Hopefully having a translator system will provide a seed so these can be done.
</ul>
</div>
-<!-- SECTION "gEDA missing functionality" [2294-2628] -->
-<h3><a name="explicitly_not_supported" id="explicitly_not_supported">Explicitly not supported</a></h3>
+<!-- EDIT760 SECTION "gEDA missing functionality" [2294-2628] -->
+<h3 class="sectionedit761"><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>
@@ -196,12 +169,13 @@ Hopefully having a translator system will provide a seed so these can be done.
</ul>
</div>
-<!-- SECTION "Explicitly not supported" [2629-2714] -->
-<h2><a name="concepts" id="concepts">Concepts</a></h2>
+<!-- EDIT761 SECTION "Explicitly not supported" [2629-2714] -->
+<h2 class="sectionedit762"><a name="concepts" id="concepts">Concepts</a></h2>
<div class="level2">
<p>
- All of these consist of lists of objects, with connections and attributes.
+
+All of these consist of lists of objects, with connections and attributes.
</p>
<p>
@@ -209,7 +183,7 @@ It is tradition that a netlist is used for interchange, but the traditional appr
</p>
<p>
-The format must convey the meaning, not necessarily in the same way as the toolâ??s native format or internal storage.
+The format must convey the meaning, not necessarily in the same way as the tool's native format or internal storage.
</p>
<p>
@@ -221,8 +195,8 @@ 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>
+<!-- EDIT762 SECTION "Concepts" [2715-3299] -->
+<h3 class="sectionedit763"><a name="some_possible_formats" id="some_possible_formats">Some possible formats</a></h3>
<div class="level3">
</div>
@@ -231,7 +205,8 @@ All contenders for possible formats must support a loss round-trip to any other.
<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.
+
+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>
@@ -240,7 +215,8 @@ All contenders for possible formats must support a loss round-trip to any other.
<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.
+
+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>
@@ -249,7 +225,8 @@ All contenders for possible formats must support a loss round-trip to any other.
<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.
+
+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>
@@ -258,7 +235,8 @@ All contenders for possible formats must support a loss round-trip to any other.
<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.
+
+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>
@@ -267,20 +245,23 @@ All contenders for possible formats must support a loss round-trip to any other.
<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.
+
+<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>
+<!-- EDIT763 SECTION "Some possible formats" [3300-4524] -->
+<h3 class="sectionedit764"><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.
+
+This part is the only part where there is not a strong history of use for VHDL and Verilog.
</p>
<p>
-Ideas:
+Ideas:
+
</p>
<ul>
<li class="level1"><div class="li"> Nets are also objects with connections and attributes. Nets have meaning in all contexts.</div>
@@ -291,7 +272,7 @@ Ideas:
</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 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>
@@ -300,34 +281,41 @@ Ideas:
</ul>
</div>
-<!-- SECTION "Representation of physical placement" [4525-5482] -->
-<h2><a name="applications" id="applications">Applications</a></h2>
+<!-- EDIT764 SECTION "Representation of physical placement" [4525-5482] -->
+<h2 class="sectionedit765"><a name="applications" id="applications">Applications</a></h2>
<div class="level2">
<p>
- Choosing the Verilog format as one possibility.
+
+Choosing the Verilog format as one possibility.
</p>
<p>
-The unit of encapsulation is the â??moduleâ??:
+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:
+
+Each object in the list has a consistent syntax:
+
</p>
<pre class="code">type #(attributes) name (connections);</pre>
<p>
- Example:
+
+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).
+
+â??râ?? is the name of an attribute. â??1kâ?? is the value (a string).
</p>
<p>
@@ -339,18 +327,21 @@ 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â??
+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.
+
+The name of the net is â??bâ??. It has no attributes.
</p>
<p>
-For schematic, you can now place the nodes:
+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);
@@ -358,7 +349,9 @@ 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:
+
+Portions that apply in only certain contexts can be selectively included with 'ifdef:
+
</p>
<pre class="code">module my_circuit;
`ifdef SCHEMATIC
@@ -371,7 +364,9 @@ place #(.x(2932), .y(2384)) place34983 (c2);</pre>
endmodule</pre>
<p>
- Complex nets can be encapsulated:
+
+Complex nets can be encapsulated:
+
</p>
<pre class="code">module net23842 (1,2,3);
net n23482 (1,2);
@@ -387,5 +382,5 @@ endmodule</pre>
endmodule</pre>
</div>
-<!-- SECTION "Applications" [5483-] --></body>
+<!-- EDIT765 SECTION "Applications" [5483-] --></body>
</html>
diff --git a/docs/wiki/geda-gaf.html b/docs/wiki/geda-gaf.html
new file mode 100644
index 0000000..bafea63
--- /dev/null
+++ b/docs/wiki/geda-gaf.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 class="sectionedit1421"><a name="geda_gaf" id="geda_gaf">gEDA/gaf</a></h1>
+<div class="level1">
+
+</div>
+<!-- EDIT1421 SECTION "gEDA/gaf" [1-24] -->
+<h2 class="sectionedit1422"><a name="gschem_and_friends" id="gschem_and_friends">gschem and friends</a></h2>
+<div class="level2">
+
+<p>
+
+Here is a list of programs that are part of gEDA/gaf (gschem and friends):
+
+</p>
+<ul>
+<li class="level1"><div class="li"> gschem is the schematic capture program/tool which is part of gEDA. Its sole purpose is to facilitate the graphical input of components/circuits. </div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> gnetlist is a netlist generation program. It takes as input gEDA/gaf .sch (schematic) file and the required .sym (symbol) files and converts them into netlists.</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> 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. </div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> symbols (on a schematic) are an abstract representation of the physical components used in electronic circuits.</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> There are many utilities included as part of gEDA/gaf.</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> gsymcheck is the symbol checker for the gEDA/gaf system. Give it a symbol file and it will go through and verify that the symbol will work in gschem and friends.</div>
+</li>
+</ul>
+
+<p>
+
+This page is under construction as there is much information that needs to be migrated into this wiki. <img src="images/smileys/fixme.gif" align="middle" alt="FIXME" />
+
+</p>
+
+</div>
+<!-- EDIT1422 SECTION "gschem and friends" [25-] --></body>
+</html>
diff --git a/docs/wiki/geda-gaf_building_git_version.html b/docs/wiki/geda-gaf_building_git_version.html
new file mode 100644
index 0000000..44bd432
--- /dev/null
+++ b/docs/wiki/geda-gaf_building_git_version.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>
+
+
+<h2 class="sectionedit1400"><a name="building_the_geda_gaf_git_repository_version" id="building_the_geda_gaf_git_repository_version">Building the gEDA/gaf git repository version</a></h2>
+<div class="level2">
+
+<p>
+To build the git repository version of gEDA/gaf, follow these instructions:
+
+</p>
+<ul>
+<li class="level1"><div class="li"> Download and install all the following dependencies. You will probably want to use your distributions package management system (such as apt-get or yum) to install the dependencies.</div>
+<ul>
+<li class="level2"><div class="li"> A C compiler and C standard library (<a href="http://gcc.gnu.org/"; class="urlextern" title="http://gcc.gnu.org/"; rel="nofollow"> GCC </a> and <a href="http://www.gnu.org/software/libc/"; class="urlextern" title="http://www.gnu.org/software/libc/"; rel="nofollow"> GNU Libc </a> are recommended)</div>
+</li>
+<li class="level2"><div class="li"> <a href="http://flex.sourceforge.net/"; class="urlextern" title="http://flex.sourceforge.net/"; rel="nofollow"> flex </a> current</div>
+</li>
+<li class="level2"><div class="li"> <a href="http://www.gnu.org/software/gawk/"; class="urlextern" title="http://www.gnu.org/software/gawk/"; rel="nofollow"> GNU awk </a> current</div>
+</li>
+<li class="level2"><div class="li"> <a href="http://www.gnu.org/software/automake"; class="urlextern" title="http://www.gnu.org/software/automake"; rel="nofollow"> automake </a> 1.6.x or later</div>
+</li>
+<li class="level2"><div class="li"> <a href="http://www.gnu.org/software/autoconf/"; class="urlextern" title="http://www.gnu.org/software/autoconf/"; rel="nofollow"> autoconf </a> 2.60 or later</div>
+</li>
+<li class="level2"><div class="li"> <a href="http://www.gnu.org/software/libtool/"; class="urlextern" title="http://www.gnu.org/software/libtool/"; rel="nofollow"> libtool </a> current</div>
+</li>
+<li class="level2"><div class="li"> <a href="http://pkgconfig.freedesktop.org/wiki"; class="urlextern" title="http://pkgconfig.freedesktop.org/wiki"; rel="nofollow"> pkg-config </a> current</div>
+</li>
+<li class="level2"><div class="li"> <a href="http://www.gnu.org/software/gettext/"; class="urlextern" title="http://www.gnu.org/software/gettext/"; rel="nofollow"> gettext </a> 0.16 or later</div>
+</li>
+<li class="level2"><div class="li"> <a href="http://www.gnu.org/software/guile%22"; class="urlextern" title="http://www.gnu.org/software/guile""; rel="nofollow"> guile </a> 1.8.x (1.6.x is no longer supported)</div>
+</li>
+<li class="level2"><div class="li"> <a href="http://www.gtk.org/"; class="urlextern" title="http://www.gtk.org/"; rel="nofollow"> gtk+ </a> 2.10.x or later</div>
+</li>
+<li class="level2"><div class="li"> <a href="http://www.gnu.org/software/groff/groff.html"; class="urlextern" title="http://www.gnu.org/software/groff/groff.html"; rel="nofollow"> groff </a> current</div>
+</li>
+<li class="level2"><div class="li"> <a href="http://git-scm.com"; class="urlextern" title="http://git-scm.com"; rel="nofollow"> git </a> 1.6.x or later</div>
+</li>
+<li class="level2"><div class="li"> <a href="http://www.nongnu.org/cvs/"; class="urlextern" title="http://www.nongnu.org/cvs/"; rel="nofollow"> cvs </a> current</div>
+</li>
+<li class="level2"><div class="li"> <a href="http://freedesktop.org/Software/shared-mime-info"; class="urlextern" title="http://freedesktop.org/Software/shared-mime-info"; rel="nofollow"> freedesktop.org MIME info database </a> current</div>
+</li>
+<li class="level2"><div class="li"> <a href="http://www.freedesktop.org/software/desktop-file-utils/releases"; class="urlextern" title="http://www.freedesktop.org/software/desktop-file-utils/releases"; rel="nofollow"> freedesktop.org utilities for manipulating .desktop files </a> current </div>
+</li>
+</ul>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> It is pretty important to have all of the above programs (especially automake, autoconf, libtool, gtk, and guile) installed in the same prefix (like /usr or /usr/local). If you do not have them all installed in the same prefix, then building and installing gEDA/gaf is much harder.</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> Clone the source from the official git repository. For information on how to do this, read the <a href="geda-scm.html" class="wikilink1" title="geda-scm.html"> gEDA SCM page </a></div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> Build the software by executing the following commands inside of the newly cloned git repository:</div>
+</li>
+</ul>
+<pre class="code"> ./autogen.sh
+ ./configure --prefix=$HOME/geda
+ make
+ make install</pre>
+<ul>
+<li class="level1"><div class="li"> If the above commands execute without <strong>any</strong> error messages, then you have successfully built and installed gEDA/gaf. If you encounter any errors, be sure to read the README and INSTALL files contained within the tarball.</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> You can now run the various programs in the gEDA suite. Please read the toplevel README file which describes what is available.</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> gschem is the schematic capture program and can be run by executing: <code>PATH_WHERE_gEDA_GAF_IS_INSTALLED/bin/gschem</code></div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> It is recommended that you add <code>PATH_WHERE_gEDA_GAF_IS_INSTALLED/bin</code> to your PATH environment variable (typically done by modifying one of the following files: <code>$HOME/.bashrc</code>, <code>$HOME/.bash_profile</code>, or <code>$HOME/.profile</code>).</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> It is highly recommended that you read the gEDA documentation at this point. You can access the gEDA documentation by running gschem and select Help/gEDA Documentationâ?¦ from the top menu.</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> If you want to get gEDA/gaf repository commit log e-mail messages, please subscribe to the geda-cvs mailing list. Please see the <a href="geda-mailinglists.html" class="wikilink1" title="geda-mailinglists.html"> mailing lists page </a> for info on how to do this.</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> For build problems, please be sure to read the <a href="geda-mailinglists.html" class="wikilink1" title="geda-mailinglists.html"> mailing list archives </a> or <a href="http://www.gpleda.org/search.html"; class="urlextern" title="http://www.gpleda.org/search.html"; rel="nofollow"> search </a> this site. Also look at the <a href="start.html" class="wikilink1" title="start.html"> gEDA wiki </a> for more hints.</div>
+</li>
+</ul>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-gattrib_readme.html b/docs/wiki/geda-gattrib_readme.html
index f4a7b19..27975a0 100644
--- a/docs/wiki/geda-gattrib_readme.html
+++ b/docs/wiki/geda-gattrib_readme.html
@@ -12,9 +12,7 @@
<body>
-
-
-<h1><a name="gattrib_readme" id="gattrib_readme">gattrib README</a></h1>
+<h1 class="sectionedit767"><a name="gattrib_readme" id="gattrib_readme">gattrib README</a></h1>
<div class="level1">
<pre class="code">******************************************************************
************* DANGER!! Read the entirety of this **************
@@ -144,7 +142,6 @@ Gattrib was cobbled together by Stuart Brorson starting in December
mail bug reports to: sdb@xxxxxxxxxx
-
</pre>
</div>
diff --git a/docs/wiki/geda-gedasuite_installation.html b/docs/wiki/geda-gedasuite_installation.html
index c1ad0f4..6ca54bb 100644
--- a/docs/wiki/geda-gedasuite_installation.html
+++ b/docs/wiki/geda-gedasuite_installation.html
@@ -11,32 +11,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>
+<h2 class="sectionedit770"><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>
@@ -48,8 +24,8 @@ Also, people have created RedHat RPMs, Debian Debs, and Mac OSX Fink packages if
</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>
+<!-- EDIT770 SECTION "How do I install the gEDA Suite?" [1-601] -->
+<h2 class="sectionedit771"><a name="fedora_core_4_install_notes" id="fedora_core_4_install_notes">Fedora Core 4 install notes</a></h2>
<div class="level2">
<p>
@@ -57,8 +33,8 @@ Also, people have created RedHat RPMs, Debian Debs, and Mac OSX Fink packages if
</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>
+<!-- EDIT771 SECTION "Fedora Core 4 install notes" [602-680] -->
+<h2 class="sectionedit772"><a name="fedora_core_3_install_notes" id="fedora_core_3_install_notes">Fedora Core 3 install notes</a></h2>
<div class="level2">
<p>
@@ -66,8 +42,8 @@ Also, people have created RedHat RPMs, Debian Debs, and Mac OSX Fink packages if
</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>
+<!-- EDIT772 SECTION "Fedora Core 3 install notes" [681-759] -->
+<h2 class="sectionedit773"><a name="fedora_core_2_install_notes" id="fedora_core_2_install_notes">Fedora Core 2 install notes</a></h2>
<div class="level2">
<p>
@@ -75,8 +51,8 @@ Also, people have created RedHat RPMs, Debian Debs, and Mac OSX Fink packages if
</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>
+<!-- EDIT773 SECTION "Fedora Core 2 install notes" [760-838] -->
+<h2 class="sectionedit774"><a name="fedora_core_1_install_notes" id="fedora_core_1_install_notes">Fedora Core 1 install notes</a></h2>
<div class="level2">
<p>
@@ -84,8 +60,8 @@ Also, people have created RedHat RPMs, Debian Debs, and Mac OSX Fink packages if
</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>
+<!-- EDIT774 SECTION "Fedora Core 1 install notes" [839-917] -->
+<h2 class="sectionedit775"><a name="suse_93_install_notes" id="suse_93_install_notes">Suse 9.3 install notes</a></h2>
<div class="level2">
<p>
@@ -93,8 +69,8 @@ Also, people have created RedHat RPMs, Debian Debs, and Mac OSX Fink packages if
</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>
+<!-- EDIT775 SECTION "Suse 9.3 install notes" [918-1001] -->
+<h2 class="sectionedit776"><a name="suse_100_install_notes" id="suse_100_install_notes">Suse 10.0 install notes</a></h2>
<div class="level2">
<p>
@@ -102,8 +78,8 @@ Also, people have created RedHat RPMs, Debian Debs, and Mac OSX Fink packages if
</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>
+<!-- EDIT776 SECTION "Suse 10.0 install notes" [1002-1088] -->
+<h2 class="sectionedit777"><a name="suse_101_install_notes" id="suse_101_install_notes">Suse 10.1 install notes</a></h2>
<div class="level2">
<p>
@@ -111,8 +87,8 @@ Also, people have created RedHat RPMs, Debian Debs, and Mac OSX Fink packages if
</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>
+<!-- EDIT777 SECTION "Suse 10.1 install notes" [1089-1175] -->
+<h2 class="sectionedit778"><a name="debian_install_notes" id="debian_install_notes">Debian install notes</a></h2>
<div class="level2">
<p>
@@ -120,8 +96,8 @@ Also, people have created RedHat RPMs, Debian Debs, and Mac OSX Fink packages if
</p>
</div>
-<!-- SECTION "Debian install notes" [1176-1253] -->
-<h2><a name="ubuntu_install_notes" id="ubuntu_install_notes">Ubuntu install notes</a></h2>
+<!-- EDIT778 SECTION "Debian install notes" [1176-1253] -->
+<h2 class="sectionedit779"><a name="ubuntu_install_notes" id="ubuntu_install_notes">Ubuntu install notes</a></h2>
<div class="level2">
<p>
@@ -129,14 +105,15 @@ Also, people have created RedHat RPMs, Debian Debs, and Mac OSX Fink packages if
</p>
</div>
-<!-- SECTION "Ubuntu install notes" [1254-1332] -->
-<h2><a name="windows_install_notes" id="windows_install_notes">Windows install notes</a></h2>
+<!-- EDIT779 SECTION "Ubuntu install notes" [1254-1332] -->
+<h2 class="sectionedit780"><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>
+<a href="geda-cygwin.html" class="wikilink1" title="geda-cygwin.html">Cygwin notes available here</a>
+
</p>
</div>
-<!-- SECTION "Windows install notes" [1333-] --></body>
+<!-- EDIT780 SECTION "Windows install notes" [1333-] --></body>
</html>
diff --git a/docs/wiki/geda-gerbv_mp.html b/docs/wiki/geda-gerbv_mp.html
index 4a094e7..3bfb4c6 100644
--- a/docs/wiki/geda-gerbv_mp.html
+++ b/docs/wiki/geda-gerbv_mp.html
@@ -12,9 +12,7 @@
<body>
-
-
-<h1><a name="gerbv_man-page" id="gerbv_man-page">gerbv man-page</a></h1>
+<h1 class="sectionedit782"><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)
@@ -250,8 +248,7 @@ COPYRIGHT
-Version Feb 8th, 2004 gerbv(1)
-</pre>
+Version Feb 8th, 2004 gerbv(1)</pre>
</div>
</body>
diff --git a/docs/wiki/geda-gerbv_pnp_readme.html b/docs/wiki/geda-gerbv_pnp_readme.html
index ee4d44e..87d2f4a 100644
--- a/docs/wiki/geda-gerbv_pnp_readme.html
+++ b/docs/wiki/geda-gerbv_pnp_readme.html
@@ -12,9 +12,7 @@
<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>
+<h1 class="sectionedit784"><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)
diff --git a/docs/wiki/geda-gfdl.html b/docs/wiki/geda-gfdl.html
index 92b2690..e492549 100644
--- a/docs/wiki/geda-gfdl.html
+++ b/docs/wiki/geda-gfdl.html
@@ -12,9 +12,7 @@
<body>
-
-
-<h1><a name="gnu_free_documentation_license" id="gnu_free_documentation_license">GNU Free Documentation License</a></h1>
+<h1 class="sectionedit806"><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
@@ -412,8 +410,7 @@ 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>
+to permit their use in free software.</pre>
</div>
</body>
diff --git a/docs/wiki/geda-glossaire.fr.html b/docs/wiki/geda-glossaire.fr.html
index 28974b3..c99d301 100644
--- a/docs/wiki/geda-glossaire.fr.html
+++ b/docs/wiki/geda-glossaire.fr.html
@@ -12,26 +12,25 @@
<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>
+<h1 class="sectionedit808"><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.
+
+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>
+<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 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 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 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 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>
@@ -41,19 +40,19 @@
</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 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 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 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 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 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>
diff --git a/docs/wiki/geda-glossary.fr.html b/docs/wiki/geda-glossary.fr.html
index 28974b3..e1198e3 100644
--- a/docs/wiki/geda-glossary.fr.html
+++ b/docs/wiki/geda-glossary.fr.html
@@ -12,26 +12,25 @@
<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>
+<h1 class="sectionedit810"><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.
+
+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>
+<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 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 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 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 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>
@@ -41,19 +40,19 @@
</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 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 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.gpleda.org"; class="urlextern" title="http://pcb.gpleda.org"; 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 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 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 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>
diff --git a/docs/wiki/geda-glossary.html b/docs/wiki/geda-glossary.html
index 04218e3..4e53508 100644
--- a/docs/wiki/geda-glossary.html
+++ b/docs/wiki/geda-glossary.html
@@ -12,30 +12,37 @@
<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>
+<h1 class="sectionedit842"><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.
+
+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>action</strong>: In pcb, an action is an internal command. Actions can be triggered via the <acronym title="Graphical User Interface">GUI</acronym> or via the command line interface. A sequence of assembled in a file can be executed on start-up of the application.</div>
+</li>
<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>flag</strong>: Objects can contain a number of flags. These indicate specific properties of the object. Examples are the <code>square</code> flag for angular pads, or the <code>onsolder</code> flag for objects on the other side of the board. </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>gedasymbols.org</strong>: A website dedicated to present symbols, footprints, scripts, plug-ins and other stuff users contributed to the geda project. Contributions can be accessed by mouse click. The whole site can be downloaded via concurrent versions system (<a href="http://en.wikipedia.org/wiki/Concurrent_Versions_System"; class="urlextern" title="http://en.wikipedia.org/wiki/Concurrent_Versions_System"; rel="nofollow">CVS</a>). This also the way users maintain their page on the site. See, <a href="http://gedasymbols.org"; class="urlextern" title="http://gedasymbols.org"; rel="nofollow">http://gedasymbols.org</a>.</div>
+</li>
+<li class="level1"><div class="li"> <strong>gerbers</strong>: A set of files sent to a fab representing the geometry of tracks, silk, solder mask and the outline of the board. Because each layer is represented by a separate file, it is customary to bundle them in a zip file. The offical name of the file format is â??Gerber 247Xâ??. See <a href="http://www.artwork.com/gerber/appl2.htm"; class="urlextern" title="http://www.artwork.com/gerber/appl2.htm"; rel="nofollow">this web page</a> for a cursory description of the format and <a href="http://www.artwork.com/gerber/appl2.htm"; class="urlextern" title="http://www.artwork.com/gerber/appl2.htm"; rel="nofollow">this PDF</a> for a comprehensive specification.</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 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>
@@ -49,7 +56,7 @@
<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 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.gpleda.org"; class="urlextern" title="http://pcb.gpleda.org"; rel="nofollow">home page of pcb</a>)</div>
</li>
</ol>
</li>
@@ -67,9 +74,9 @@
</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 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 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>
diff --git a/docs/wiki/geda-gnetlist_mp.html b/docs/wiki/geda-gnetlist_mp.html
index 2bcadf5..5da3c24 100644
--- a/docs/wiki/geda-gnetlist_mp.html
+++ b/docs/wiki/geda-gnetlist_mp.html
@@ -12,9 +12,7 @@
<body>
-
-
-<h1><a name="gnetlist_man-page" id="gnetlist_man-page">gnetlist man-page</a></h1>
+<h1 class="sectionedit844"><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)
diff --git a/docs/wiki/geda-gnetlist_scheme_tutorial.html b/docs/wiki/geda-gnetlist_scheme_tutorial.html
index 33306cf..e8901a6 100644
--- a/docs/wiki/geda-gnetlist_scheme_tutorial.html
+++ b/docs/wiki/geda-gnetlist_scheme_tutorial.html
@@ -12,13 +12,12 @@
<body>
-
-
-<h1><a name="scripting_a_gnetlist_backend_in_scheme" id="scripting_a_gnetlist_backend_in_scheme">Scripting a gnetlist backend in Scheme</a></h1>
+<h1 class="sectionedit13"><a name="scripting_a_gnetlist_backend_in_scheme" id="scripting_a_gnetlist_backend_in_scheme">Scripting a gnetlist backend in Scheme</a></h1>
<div class="level1">
<p>
- <strong>by John Doty</strong>
+
+<strong>by John Doty</strong>
</p>
<p>
@@ -26,19 +25,23 @@
</p>
<p>
-Donâ??t Panic!
+Don't Panic!
</p>
<p>
-If youâ??ve never written a program in Lisp, it looks daunting. But itâ??s a lot easier than it looks. Wrap a little bit of â??syntactic sugarâ?? around Lisp, and it becomes Logo, which elementary school children can learn.
+If you've never written a program in Lisp, it looks daunting. But it's a lot easier than it looks. Wrap a little bit of â??syntactic
+sugarâ?? around Lisp, and it becomes Logo, which elementary school children can learn.
</p>
<p>
-And, just to make it clear what some of the funny words mean, <a href="http://en.wikipedia.org/wiki/Lisp_%28programming_language%29"; class="interwiki iw_wp" title="http://en.wikipedia.org/wiki/Lisp_%28programming_language%29";>Lisp</a> is a computer language, <a href="http://en.wikipedia.org/wiki/Scheme_%28programming_language%29"; class="interwiki iw_wp" title="http://en.wikipedia.org/wiki/Scheme_%28programming_language%29";>Scheme</a> is a dialect of Lisp, and <a href="http://en.wikipedia.org/wiki/GNU_Guile"; class="interwiki iw_wp" title="http://en.wikipedia.org/wiki/GNU_Guile";>Guile</a> is an implementation of Scheme. Guile is used for â??scriptingâ?? gEDA. In particular, the gnetlist front end, written in C, extracts topology and attribute information from schematics, and then presents that data to â??back endâ?? Guile scripts for processing and output.
+And, just to make it clear what some of the funny words mean, <a href="http://en.wikipedia.org/wiki/Lisp_(programming_language)" class="interwiki iw_wp" title="http://en.wikipedia.org/wiki/Lisp_(programming_language)">Lisp</a> is a computer language, <a href="http://en.wikipedia.org/wiki/Scheme_(programming_language)" class="interwiki iw_wp" title="http://en.wikipedia.org/wiki/Scheme_(programming_language)">Scheme</a> is a dialect of Lisp, and <a href="http://en.wikipedia.org/wiki/GNU_Guile"; class="interwiki iw_wp" title="http://en.wikipedia.org/wiki/GNU_Guile";>Guile</a> is an
+implementation of Scheme. Guile is used for â??scriptingâ?? gEDA. In particular, the gnetlist front end, written in C, extracts topology
+and attribute information from schematics, and then presents that data to â??back endâ?? Guile scripts for processing and output.
</p>
<p>
-This tutorial is specifically about programming gnetlist back ends in Scheme. If you donâ??t already know Scheme, you should probably look at other material too, such as:
+This tutorial is specifically about programming gnetlist back ends in Scheme. If you don't already know Scheme, you should probably look at
+other material too, such as:
</p>
<p>
@@ -62,86 +65,84 @@ may also be useful.
</p>
<p>
-OK, letâ??s get started. Hereâ??s a particularly simple back end:
+OK, let's get started. Here's a particularly simple back end:
</p>
-<pre class="code scheme"><span class="co1">;; gnetlist development playground</span>
+<pre class="code scheme"><pre class="code scheme"><span class="co1">;; gnetlist development playground</span>
<span class="br0">(</span>use-modules <span class="br0">(</span>ice<span class="nu0">-9</span> readline<span class="br0">)</span><span class="br0">)</span>
<span class="br0">(</span>activate-readline<span class="br0">)</span>
<span class="br0">(</span><span class="kw1">define</span> <span class="br0">(</span>devel output-filename<span class="br0">)</span>
<span class="br0">(</span>scm-style-repl<span class="br0">)</span>
-<span class="br0">)</span></pre>
+<span class="br0">)</span></pre></pre>
+
<p>
-To use this, put it in a file called <code>gnet-devel.scm</code>. Copy this file to wherever gnetlist Scheme files are kept on your system. On the machine Iâ??m using today, the command is:
+To use this, put it in a file called <code>gnet-devel.scm</code>. Copy this file
+to wherever gnetlist Scheme files are kept on your system. On the
+machine I'm using today, the command is:
</p>
-<pre class="code bash">$ sudo cp gnet-devel.scm /sw/share/gEDA/scheme/</pre>
+<pre class="code bash"><pre class="code bash">$ sudo cp gnet-devel.scm /sw/share/gEDA/scheme/</pre></pre>
+
<p>
-The <code>â??/sw/"</code> will be <code>â??/usr/"</code> for most Linux package installations, maybe <code>â??/usr/localâ??</code> or <code>â??~/mygeda/"</code> for a tarball installation. Youâ??ll have to figure that out. If the target location is writable by you without superuser privileges, you wonâ??t need the <code>â??sudoâ??</code>.
+The <code>â??/sw/â??</code> will be <code>â??/usr/â??</code> for most Linux package installations, maybe <code>â??/usr/localâ??</code> or <code>â??~/mygeda/â??</code> for a tarball installation. You'll have to figure that out. If the target location is writable by you without superuser privileges, you won't need the <code>â??sudoâ??</code>.
</p>
<p>
-Now, translating <code>â??/sw/"</code> as needed, type:
+Now, translating <code>â??/sw/â??</code> as needed, type:
</p>
-<pre class="code bash">$ gnetlist -g devel /sw/share/gEDA/examples/lightning_detector/lightning.sch</pre>
+<pre class="code bash"><pre class="code bash">$ gnetlist -g devel /sw/share/gEDA/examples/lightning_detector/lightning.sch</pre></pre>
+
<p>
You should see the usual gnetlist boiler plate, followed by:
</p>
-<pre class="code">
-guile>
-</pre>
+<pre class="code">guile></pre>
<p>
Try:
</p>
-<pre class="code">
-guile> packages
-</pre>
+<pre class="code">guile> packages</pre>
<p>
You should see:
</p>
-<pre class="code scheme"><span class="br0">(</span><span class="st0">"Q3"</span> <span class="st0">"R5"</span> <span class="st0">"Q2"</span> <span class="st0">"R4"</span> <span class="st0">"Q1"</span> <span class="st0">"C6"</span> <span class="st0">"R3"</span> <span class="st0">"L2"</span> <span class="st0">"A1"</span> <span class="st0">"bat(+3v)"</span> <span class="st0">"lamp(1)"</span> <span class="st0">"R2"</span> <span class="st0">"C5"</span> <span class="st0">"L1"</span> <span class="st0">"R1"</span> <span class="st0">"C4"</span> <span class="st0">"lamp(2)"</span> <span class="st0">"C3"</span> <span class="st0">"C2"</span> <span class="st0">"C1"</span> <span class="st0">"D1"</span> <span class="st0">"bat(0v)"</span> <span class="st0">"R7"</span> <span class="st0">"Q4"</span> <span class="st0">"R6"</span><span class="br0">)</span></pre>
+<pre class="code scheme"><pre class="code scheme"><span class="br0">(</span><span class="st0">"Q3"</span> <span class="st0">"R5"</span> <span class="st0">"Q2"</span> <span class="st0">"R4"</span> <span class="st0">"Q1"</span> <span class="st0">"C6"</span> <span class="st0">"R3"</span> <span class="st0">"L2"</span> <span class="st0">"A1"</span> <span class="st0">"bat(+3v)"</span> <span class="st0">"lamp(1)"</span> <span class="st0">"R2"</span> <span class="st0">"C5"</span> <span class="st0">"L1"</span> <span class="st0">"R1"</span> <span class="st0">"C4"</span> <span class="st0">"lamp(2)"</span> <span class="st0">"C3"</span> <span class="st0">"C2"</span> <span class="st0">"C1"</span> <span class="st0">"D1"</span> <span class="st0">"bat(0v)"</span> <span class="st0">"R7"</span> <span class="st0">"Q4"</span> <span class="st0">"R6"</span><span class="br0">)</span></pre></pre>
+
<p>
-<code>â??packagesâ??</code> is a handy variable, containing a list of all unique <code>â??refdes="</code> attribute values. By typing it, you fed it to the â??REPLâ??, the Read, Evaluate, Print Loop. So, the REPL read it, evaluated it (getting a list), and printed it.
+<code>â??packagesâ??</code> is a handy variable, containing a list of all unique <code>â??refdes=â??</code> attribute values. By typing it, you fed it to the â??REPLâ??,
+the Read, Evaluate, Print Loop. So, the REPL read it, evaluated it (getting a list), and printed it.
</p>
<p>
Now try:
</p>
-<pre class="code">
-guile> (length packages)
-25
-</pre>
+<pre class="code">guile> (length packages)
+25</pre>
<p>
What happened here? Here, the REPL evaluated the list
</p>
-<pre class="code scheme"><span class="br0">(</span><span class="kw1">length</span> packages<span class="br0">)</span></pre>
+<pre class="code scheme"><pre class="code scheme"><span class="br0">(</span><span class="kw1">length</span> packages<span class="br0">)</span></pre></pre>
+
<p>
-In most programming languages, youâ??d write this expression in more traditional functional notation as <code>â??length( packages )"</code>. <code>â??lengthâ??</code> is a function, which tells you the length of a list.
+In most programming languages, you'd write this expression in more traditional functional notation as <code>â??length( packages )â??</code>. <code>â??lengthâ??</code> is a function, which tells you the length of a list.
</p>
<p>
Use the same notation to do arithmetic. For example, calculate â??2+3â?? as:
</p>
-<pre class="code">
-guile> (+ 2 3)
-5
-</pre>
+<pre class="code">guile> (+ 2 3)
+5</pre>
<p>
-Note that the procedure "+" can be used to add any number of quantities, including none at all:
+Note that the procedure â??+â?? can be used to add any number of quantities, including none at all:
</p>
-<pre class="code">
-guile> (+)
+<pre class="code">guile> (+)
0
guile> (+ 1 2 3)
-6
-</pre>
+6</pre>
<p>
-Weâ??ll make use of this later on.
+We'll make use of this later on.
</p>
<p>
@@ -149,53 +150,45 @@ The readline stuff in our <code>gnet-devel.scm</code> back end allows you to use
</p>
<p>
-Another useful variable gnetlist defines is <code>â??all-unique-netsâ??</code> (type it). Just as <code>â??(length packages)"</code> tells you how many packages you have, <code>â??(length all-unique-nets)"</code> will tell you how many nets you have.
+Another useful variable gnetlist defines is <code>â??all-unique-netsâ??</code> (type it). Just as <code>â??(length packages)â??</code> tells you how many packages you
+have, <code>â??(length all-unique-nets)â??</code> will tell you how many nets you have.
</p>
<p>
-Then thereâ??s <code>all-pins</code>:
+Then there's <code>all-pins</code>:
</p>
-<pre class="code">
-guile> all-pins
-(("1" "2" "3") ("2" "3" "1") ("2" "1") ("1" "2") ("1" "2") ("1" "2") ("1" "2") ("1" "2") ("1" "2") ("2" "1") ("2" "1") ("2" "1") ("1" "2") ("2" "1") ("1") ("1") ("2" "1") ("2" "3" "1") ("2" "3" "1") ("1") ("2" "1") ("2" "3" "1") ("1" "2") ("1") ("1"))
-</pre>
+<pre class="code">guile> all-pins
+(("1" "2" "3") ("2" "3" "1") ("2" "1") ("1" "2") ("1" "2") ("1" "2") ("1" "2") ("1" "2") ("1" "2") ("2" "1") ("2" "1") ("2" "1") ("1" "2") ("2" "1") ("1") ("1") ("2" "1") ("2" "3" "1") ("2" "3" "1") ("1") ("2" "1") ("2" "3" "1") ("1" "2") ("1") ("1"))</pre>
<p>
-Note that this is a little more complicated than the previous examples: itâ??s a list of lists, not just a list of strings. Each of the lists corresponds to the pins on one package. One thing we might want to extract from this is a count of the number of pins. We canâ??t just take the length of <code>all-pins</code> to get this: that gives us the number of lists it contains, which is the number of packages:
+Note that this is a little more complicated than the previous examples: it's a list of lists, not just a list of strings. Each of the lists corresponds to the pins on one package. One thing we might want to extract from this is a count of the number of pins. We can't just take the length of <code>all-pins</code> to get this: that gives us the number of lists it contains, which is the number of packages:
</p>
-<pre class="code">
-guile> (length all-pins)
-25
-</pre>
+<pre class="code">guile> (length all-pins)
+25</pre>
<p>
To get the pin count, first get the individual pin counts for each package:
</p>
-<pre class="code">
-guile> (map length all-pins)
-(3 3 2 2 2 2 2 2 2 2 2 2 2 2 1 1 2 3 3 1 2 3 2 1 1)
-</pre>
+<pre class="code">guile> (map length all-pins)
+(3 3 2 2 2 2 2 2 2 2 2 2 2 2 1 1 2 3 3 1 2 3 2 1 1)</pre>
<p>
This is one of the easy ways to do a â??loopâ?? in Scheme; <code>(map p x)</code> yields a list of the results of calling procedure <code>p</code> individually for each element of <code>x</code>. Then we can add them up with a slightly different kind of â??loopâ??:
</p>
-<pre class="code">
-guile> (apply + (map length all-pins))
-50
-</pre>
+<pre class="code">guile> (apply + (map length all-pins))
+50</pre>
<p>
(apply p x) calls procedure p once, with all of the elements of x as arguments. So the expression above winds up evaluating:
</p>
-<pre class="code scheme"><span class="br0">(</span>+ <span class="nu0">3</span> <span class="nu0">3</span> <span class="nu0">2</span> <span class="nu0">2</span> <span class="nu0">2</span> <span class="nu0">2</span> <span class="nu0">2</span> <span class="nu0">2</span> <span class="nu0">2</span> <span class="nu0">2</span> <span class="nu0">2</span> <span class="nu0">2</span> <span class="nu0">2</span> <span class="nu0">2</span> <span class="nu0">1</span> <span class="nu0">1</span> <span class="nu0">2</span> <span class="nu0">3</span> <span class="nu0">3</span> <span class="nu0">1</span> <span class="nu0">2</span> <span class="nu0">3</span> <span class="nu0">2</span> <span class="nu0">1</span> <span class="nu0">1</span><span class="br0">)</span></pre>
+<pre class="code scheme"><pre class="code scheme"><span class="br0">(</span>+ <span class="nu0">3</span> <span class="nu0">3</span> <span class="nu0">2</span> <span class="nu0">2</span> <span class="nu0">2</span> <span class="nu0">2</span> <span class="nu0">2</span> <span class="nu0">2</span> <span class="nu0">2</span> <span class="nu0">2</span> <span class="nu0">2</span> <span class="nu0">2</span> <span class="nu0">2</span> <span class="nu0">2</span> <span class="nu0">1</span> <span class="nu0">1</span> <span class="nu0">2</span> <span class="nu0">3</span> <span class="nu0">3</span> <span class="nu0">1</span> <span class="nu0">2</span> <span class="nu0">3</span> <span class="nu0">2</span> <span class="nu0">1</span> <span class="nu0">1</span><span class="br0">)</span></pre></pre>
+
<p>
-Thus far weâ??ve been using predefined variables and procedures. Weâ??ll want to be able to define our own. Itâ??s easy:
+Thus far we've been using predefined variables and procedures. We'll want to be able to define our own. It's easy:
</p>
-<pre class="code">
-guile> (define the-answer 42)
+<pre class="code">guile> (define the-answer 42)
guile> the-answer
-42
-</pre>
+42</pre>
<p>
This defines a variable, <code>the-answer</code>, and gives it the value 42.
@@ -204,46 +197,44 @@ This defines a variable, <code>the-answer</code>, and gives it the value 42.
<p>
We can also define procedures:
</p>
-<pre class="code">
-guile> (define add1 (lambda (x) (+ x 1)))
+<pre class="code">guile> (define add1 (lambda (x) (+ x 1)))
guile> (add1 100)
-101
-</pre>
+101</pre>
<p>
-When you see <code>â??lambdaâ??</code> think â??procedureâ??. The first thing (the technical term is â??formâ??) following <code>â??lambdaâ??</code> is a list of the arguments of the procedure, in this case <code>â??(x)"</code>. When the the procedure is called, Guile evaluates the remaining forms, in this case just one, <code>â??(+ x 1)"</code>, with actual arguments substituted. The result of the procedure is the result of evaluating the last form. So, <code>â??(add1 100)"</code> becomes <code>â??(+ 100 1)"</code>, which evaluates to 101.
+When you see <code>â??lambdaâ??</code> think â??procedureâ??. The first thing (the technical term is â??formâ??) following <code>â??lambdaâ??</code> is a list of the arguments of the procedure, in this case <code>â??(x)â??</code>. When the the procedure is called, Guile evaluates the remaining forms, in this case just one, <code>â??(+ x 1)â??</code>, with actual arguments substituted. The result of the procedure is the result of evaluating the last form. So, <code>â??(add1 100)â??</code> becomes <code>â??(+ 100 1)â??</code>, which evaluates to 101.
</p>
<p>
Now we can put our statistics collection together into a back end. First, define a procedure to write a line of output:
</p>
-<pre class="code scheme"><span class="br0">(</span><span class="kw1">define</span> format-line
+<pre class="code scheme"><pre class="code scheme"><span class="br0">(</span><span class="kw1">define</span> format-line
<span class="br0">(</span><span class="kw1">lambda</span> <span class="br0">(</span>name value<span class="br0">)</span>
<span class="br0">(</span><span class="kw1">display</span> name<span class="br0">)</span>
<span class="br0">(</span><span class="kw1">display</span> value<span class="br0">)</span>
<span class="br0">(</span><span class="kw1">newline</span><span class="br0">)</span>
<span class="br0">)</span>
-<span class="br0">)</span></pre>
+<span class="br0">)</span></pre></pre>
+
<p>
-Weâ??re using two new builtin procedures here, <code>â??displayâ??</code> and <code>â??newlineâ??</code>, which should be self-explanatory. Now:
+We're using two new builtin procedures here, <code>â??displayâ??</code> and <code>â??newlineâ??</code>, which should be self-explanatory. Now:
</p>
-<pre class="code scheme"><span class="br0">(</span><span class="kw1">define</span> display-stats
+<pre class="code scheme"><pre class="code scheme"><span class="br0">(</span><span class="kw1">define</span> display-stats
<span class="br0">(</span><span class="kw1">lambda</span> <span class="br0">(</span><span class="br0">)</span> <span class="co1">; no arguments</span>
<span class="br0">(</span>format-line <span class="st0">"pins: "</span> <span class="br0">(</span>apply + <span class="br0">(</span><span class="kw1">map</span> <span class="kw1">length</span> all-pins<span class="br0">)</span><span class="br0">)</span><span class="br0">)</span>
<span class="br0">(</span>format-line <span class="st0">"packages: "</span> <span class="br0">(</span><span class="kw1">length</span> packages<span class="br0">)</span><span class="br0">)</span>
<span class="br0">(</span>format-line <span class="st0">"nets: "</span> <span class="br0">(</span><span class="kw1">length</span> all-unique-nets<span class="br0">)</span><span class="br0">)</span>
<span class="br0">)</span>
-<span class="br0">)</span></pre><pre class="code">
-guile> (display-stats)
+<span class="br0">)</span></pre></pre>
+<pre class="code">guile> (display-stats)
pins: 50
packages: 25
-nets: 13
-</pre>
+nets: 13</pre>
<p>
To finish off a back end, we need a â??main programâ??. By convention, that has the name of the back end. It has the responsibility of opening the output file, too. So, for a â??statsâ?? back end for collecting the stats, the entire file looks like:
</p>
-<pre class="code scheme"><span class="co1">;; gnetlist back end for extracting design statistics</span>
+<pre class="code scheme"><pre class="code scheme"><span class="co1">;; gnetlist back end for extracting design statistics</span>
<span class="co1">;;</span>
<span class="co1">;; Legal boilerplate here as needed</span>
@@ -272,17 +263,23 @@ To finish off a back end, we need a â??main programâ??. By convention, that has
<span class="br0">(</span><span class="kw1">display</span> value<span class="br0">)</span>
<span class="br0">(</span><span class="kw1">newline</span><span class="br0">)</span>
<span class="br0">)</span>
-<span class="br0">)</span></pre>
+<span class="br0">)</span></pre></pre>
+
<p>
-Put this in a file named <code>gnet-stats.scm</code>, copy it to where it belongs with something like
+Put this in a file named <code>gnet-stats.scm</code>, copy it to where it belongs with something like
+
</p>
-<pre class="code bash">$ sudo cp gnet-stats.scm /sw/share/gEDA/scheme/</pre>
+<pre class="code bash"><pre class="code bash">$ sudo cp gnet-stats.scm /sw/share/gEDA/scheme/</pre></pre>
+
<p>
- and then <code>â??gnetlist -g statsâ??</code> followed by the usual other arguments and schematic pathnames will put your designâ??s statistics in the output file (default <code>output.net</code>).
+
+and then <code>â??gnetlist -g statsâ??</code> followed by the usual other arguments and schematic pathnames will put your design's statistics in the
+output file (default <code>output.net</code>).
</p>
<p>
-Pretty easy, huh? Useful, too. Lately Iâ??ve been designing systems that consist of stacks of boards: statistics like these are helpful in figuring out which subsystems I should combine on each board.
+Pretty easy, huh? Useful, too. Lately I've been designing systems that consist of stacks of boards: statistics like these are helpful
+in figuring out which subsystems I should combine on each board.
</p>
</div>
diff --git a/docs/wiki/geda-gnetlist_ug.html b/docs/wiki/geda-gnetlist_ug.html
index febcf24..63fbd5e 100644
--- a/docs/wiki/geda-gnetlist_ug.html
+++ b/docs/wiki/geda-gnetlist_ug.html
@@ -11,41 +11,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>
+<h1 class="sectionedit86"><a name="geda_gnetlist_users_guide" id="geda_gnetlist_users_guide">gEDA gnetlist Users Guide</a></h1>
<div class="level1">
<p>
@@ -61,24 +28,27 @@ September 21st, 2003
</p>
</div>
-<!-- SECTION "gEDA gnetlist Users Guide" [1-158] -->
-<h2><a name="introduction" id="introduction">Introduction</a></h2>
+<!-- EDIT86 SECTION "gEDA gnetlist Users Guide" [1-158] -->
+<h2 class="sectionedit87"><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!
+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>
+<!-- EDIT87 SECTION "Introduction" [159-1084] -->
+<h2 class="sectionedit88"><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:
+
+<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>
@@ -114,12 +84,13 @@ This document describes how to use <strong>gnetlist</strong>. This document and
</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).
+
+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>
+<!-- EDIT88 SECTION "Overview" [1085-2789] -->
+<h2 class="sectionedit89"><a name="installation" id="installation">Installation</a></h2>
<div class="level2">
<p>
@@ -135,13 +106,14 @@ The first two should return the version of the installed tools (libgeda and the
</p>
</div>
-<!-- SECTION "Installation" [2790-3757] -->
-<h2><a name="running_gnetlist" id="running_gnetlist">Running gnetlist</a></h2>
+<!-- EDIT89 SECTION "Installation" [2790-3757] -->
+<h2 class="sectionedit90"><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>:
+
+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>
@@ -151,8 +123,11 @@ It is very easy to run <strong>gnetlist</strong>. <strong>gnetlist</strong> is a
</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>:
+
+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>
@@ -162,21 +137,22 @@ It is very easy to run <strong>gnetlist</strong>. <strong>gnetlist</strong> is a
<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.
+
+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>
+<!-- EDIT90 SECTION "Running gnetlist" [3758-5053] -->
+<h2 class="sectionedit91"><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.
+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>
+<!-- EDIT91 SECTION "Schematic / symbol requirements" [5054-5677] -->
+<h3 class="sectionedit92"><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>
@@ -198,11 +174,11 @@ This section describes what schematics/symbols need to have to be usable with <s
</ul>
</div>
-<!-- SECTION "Symbol requirements" [5678-6726] -->
-<h3><a name="schematic_requirements" id="schematic_requirements">Schematic requirements</a></h3>
+<!-- EDIT92 SECTION "Symbol requirements" [5678-6726] -->
+<h3 class="sectionedit93"><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 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>
@@ -215,8 +191,8 @@ This section describes what schematics/symbols need to have to be usable with <s
</ul>
</div>
-<!-- SECTION "Schematic requirements" [6727-7703] -->
-<h3><a name="random_notes" id="random_notes">Random notes</a></h3>
+<!-- EDIT93 SECTION "Schematic requirements" [6727-7703] -->
+<h3 class="sectionedit94"><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>
@@ -224,8 +200,8 @@ This section describes what schematics/symbols need to have to be usable with <s
</ul>
</div>
-<!-- SECTION "Random notes" [7704-8177] -->
-<h2><a name="hierarchy_support" id="hierarchy_support">Hierarchy Support</a></h2>
+<!-- EDIT94 SECTION "Random notes" [7704-8177] -->
+<h2 class="sectionedit95"><a name="hierarchy_support" id="hierarchy_support">Hierarchy Support</a></h2>
<div class="level2">
<p>
@@ -233,8 +209,8 @@ TBA
</p>
</div>
-<!-- SECTION "Hierarchy Support" [8178-8212] -->
-<h2><a name="specific_backend_info" id="specific_backend_info">Specific backend info</a></h2>
+<!-- EDIT95 SECTION "Hierarchy Support" [8178-8212] -->
+<h2 class="sectionedit96"><a name="specific_backend_info" id="specific_backend_info">Specific backend info</a></h2>
<div class="level2">
<p>
@@ -242,8 +218,8 @@ TBA
</p>
</div>
-<!-- SECTION "Specific backend info" [8213-8251] -->
-<h2><a name="scheme_backend_api" id="scheme_backend_api">Scheme backend API</a></h2>
+<!-- EDIT96 SECTION "Specific backend info" [8213-8251] -->
+<h2 class="sectionedit97"><a name="scheme_backend_api" id="scheme_backend_api">Scheme backend API</a></h2>
<div class="level2">
<p>
@@ -251,22 +227,24 @@ Please note that this section is still under construction. The information here
</p>
</div>
-<!-- SECTION "Scheme backend API" [8252-8406] -->
-<h3><a name="overview1" id="overview1">Overview</a></h3>
+<!-- EDIT97 SECTION "Scheme backend API" [8252-8406] -->
+<h3 class="sectionedit98"><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>.
+<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>
+<!-- EDIT98 SECTION "Overview" [8407-9196] -->
+<h3 class="sectionedit99"><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.
+
+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
@@ -281,8 +259,8 @@ Each netlist backend is required to provide a function whose name matches the ne
(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>
+<!-- EDIT99 SECTION "Entry Point" [9197-10206] -->
+<h3 class="sectionedit100"><a name="initialization_of_the_backend" id="initialization_of_the_backend">Initialization of the Backend</a></h3>
<div class="level3">
<p>
@@ -302,8 +280,10 @@ The other initialization which is typically done, although not required by all n
<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
+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
@@ -324,25 +304,29 @@ Note that the convention is for any backend specific functions to have their nam
)</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
+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>
+<!-- EDIT100 SECTION "Initialization of the Backend" [10207-12775] -->
+<h3 class="sectionedit101"><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,
+
+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.
+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.
@@ -378,23 +362,28 @@ The function â??switcap:map-net-namesâ?? is a backend specific (switcap in this
<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
+
+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.
+
+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>
+<!-- EDIT101 SECTION "Net Name and Reference Designator Aliasing" [12776-15447] -->
+<h3 class="sectionedit102"><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.
+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
@@ -415,5 +404,5 @@ gnetlist> all-unique-nets
%</pre>
</div>
-<!-- SECTION "Debugging Hints" [15448-] --></body>
+<!-- EDIT102 SECTION "Debugging Hints" [15448-] --></body>
</html>
diff --git a/docs/wiki/geda-gparts_dd.html b/docs/wiki/geda-gparts_dd.html
index fbba04f..0ce1753 100644
--- a/docs/wiki/geda-gparts_dd.html
+++ b/docs/wiki/geda-gparts_dd.html
@@ -11,41 +11,25 @@
</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="#part_manager" class="toc">Part Manager</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#part_database" class="toc">Part Database</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#entities" class="toc">Entities</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#part_categories" class="toc">Part Categories</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#part_hierarchy" class="toc">Part Hierarchy</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#part_manager_gui" class="toc">Part Manager GUI</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#use_cases" class="toc">Use Cases</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#ui_design" class="toc">UI Design</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#configuration" class="toc">Configuration</a></span></div></li></ul>
-</li></ul>
-</li></ul>
-</div>
-</div>
<p>
This page serves as a working document for the design of a parts manager for gEDA. Please submit feedback to the geda-dev or geda-user mailing lists.
</p>
+<p>
+For implementation details, see <a href="geda-gparts_id.html" class="wikilink1" title="geda-gparts_id.html">gparts_id</a>.
+</p>
+<p>
+Or, return to the <a href="geda-gparts_tc.html" class="wikilink1" title="geda-gparts_tc.html">part manager top level</a> page.
+</p>
-<h1><a name="part_manager" id="part_manager">Part Manager</a></h1>
+<h1 class="sectionedit134"><a name="part_manager" id="part_manager">Part Manager</a></h1>
<div class="level1">
<p>
- The part manager uses a relational database to store parts used in the development of electronic assemblies. The part manager also stores attributes for these parts and can place these attributes into a component or symbol for placement into schematics.
+
+The part manager uses a relational database to store parts used in the development of electronic assemblies. The part manager also stores attributes for these parts and can place these attributes into a component or symbol for placement into schematics.
</p>
<p>
@@ -65,12 +49,13 @@ The part database can be configured as either local or remote. In the remote co
</p>
</div>
-<!-- SECTION "Part Manager" [152-914] -->
-<h2><a name="part_database" id="part_database">Part Database</a></h2>
+<!-- EDIT134 SECTION "Part Manager" [262-1024] -->
+<h2 class="sectionedit135"><a name="part_database" id="part_database">Part Database</a></h2>
<div class="level2">
<p>
- The following figure shows the entity relationships for a part in the resistor category. The category does not reference any tables in the resistor category, but only contains the view name and stored procedures to manipulate a part within the resistor category. This mechanism allows the tables and relationships to vary by category.
+
+The following figure shows the entity relationships for a part in the resistor category. The category does not reference any tables in the resistor category, but only contains the view name and stored procedures to manipulate a part within the resistor category. This mechanism allows the tables and relationships to vary by category.
</p>
<p>
@@ -78,12 +63,13 @@ The part database can be configured as either local or remote. In the remote co
</p>
</div>
-<!-- SECTION "Part Database" [915-1308] -->
-<h3><a name="entities" id="entities">Entities</a></h3>
+<!-- EDIT135 SECTION "Part Database" [1025-1418] -->
+<h3 class="sectionedit136"><a name="entities" id="entities">Entities</a></h3>
<div class="level3">
<p>
- The database always contains tables to store the following entities. The database contains additional tables to store specific categories of parts (e.g. a capacitor table, a diode table, a resistor table, etc…). This list excludes junction tables and metadata tables.
+
+The database always contains tables to store the following entities. The database contains additional tables to store specific categories of parts (e.g. a capacitor table, a diode table, a resistor table, etcâ?¦). This list excludes junction tables and metadata tables.
</p>
</div>
@@ -92,190 +78,205 @@ The part database can be configured as either local or remote. In the remote co
<div class="level4">
<p>
- A class of parts (e.g. capacitors, diodes, resistors, transistors, etc…). A category can contain sub-categories (e.g. small-signal diodes, TVS diodes, zener diodes, etc…) Sub-categories can include additional sub-categories. All parts within a category or sub-category share the same set of attributes (e.g. forward voltage, maximum current, power dissipation, etc…). Sub-categories do not need to inherit the attributes of their parent.
+
+A class of parts (e.g. capacitors, diodes, resistors, transistors, etcâ?¦). A category can contain sub-categories (e.g. small-signal diodes, TVS diodes, zener diodes, etcâ?¦) Sub-categories can include additional sub-categories. All parts within a category or sub-category share the same set of attributes (e.g. forward voltage, maximum current, power dissipation, etcâ?¦). Sub-categories do not need to inherit the attributes of their parent.
</p>
<p>
-The category stores metadata for mapping the partâ??s database columns to the component attributes. For numeric attributes, the category stores the columnâ??s unit of measure (e.g. amps, farads, ohms, volts, etc…).
+The category stores metadata for mapping the partâ??s database columns to the component attributes. For numeric attributes, the category stores the columnâ??s unit of measure (e.g. amps, farads, ohms, volts, etcâ?¦).
</p>
<p>
-The category also stores the names of database views and stored procedures to access and manipulate the tables of parts within the category.
+The category also stores the names of database views and stored procedures to access and manipulate the tables of parts within the category.
+
</p>
-<table class="inline">
- <tr>
- <th class="leftalign"> Field </th><th class="leftalign"> Type </th><th class="leftalign"> Description </th>
+<div class="table sectionedit137"><table class="inline">
+ <tr class="row0">
+ <th class="col0 leftalign"> Field </th><th class="col1 leftalign"> Type </th><th class="col2 leftalign"> Description </th>
</tr>
- <tr>
- <td class="leftalign"> CategoryID </td><td class="rightalign"> </td><td class="leftalign"> Surrogate key </td>
+ <tr class="row1">
+ <td class="col0 leftalign"> CategoryID </td><td class="col1 leftalign"> </td><td class="col2 leftalign"> Surrogate key </td>
</tr>
- <tr>
- <td> CategoryName </td><td> String </td><td> The unique name of the category </td>
+ <tr class="row2">
+ <td class="col0"> CategoryName </td><td class="col1"> String </td><td class="col2"> The unique name of the category </td>
</tr>
- <tr>
- <td class="leftalign"> ParentID </td><td class="rightalign"> </td><td class="leftalign"> Foreign key to Category </td>
+ <tr class="row3">
+ <td class="col0 leftalign"> ParentID </td><td class="col1 leftalign"> </td><td class="col2 leftalign"> Foreign key to Category </td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT137 TABLE [2539-2778] -->
</div>
<h4><a name="company" id="company">Company</a></h4>
<div class="level4">
<p>
- Currently, a company represents a partâ??s manufacturer.
+
+Currently, a company represents a partâ??s manufacturer.
+
</p>
-<table class="inline">
- <tr>
- <th class="leftalign"> Field </th><th class="leftalign"> Type </th><th class="leftalign"> Description </th>
+<div class="table sectionedit138"><table class="inline">
+ <tr class="row0">
+ <th class="col0 leftalign"> Field </th><th class="col1 leftalign"> Type </th><th class="col2 leftalign"> Description </th>
</tr>
- <tr>
- <td class="leftalign"> CompanyID </td><td class="rightalign"> </td><td class="leftalign"> Surrogate key </td>
+ <tr class="row1">
+ <td class="col0 leftalign"> CompanyID </td><td class="col1 leftalign"> </td><td class="col2 leftalign"> Surrogate key </td>
</tr>
- <tr>
- <td> CompanyName </td><td> String </td><td> The unique name of the company </td>
+ <tr class="row2">
+ <td class="col0"> CompanyName </td><td class="col1"> String </td><td class="col2"> The unique name of the company </td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT138 TABLE [2857-3030] -->
</div>
<h4><a name="device" id="device">Device</a></h4>
<div class="level4">
<p>
- A type of part. The device name only provides a mechanism to map parts to symbols. A part in the library of device resistor can use all the symbols in the library where device is resistor. Similarly, a symbol where device is resistor can represent any part of device resistor. When importing a symbol, the database uses the value of the symbol attribute DEVICE as the initial value for the device field. The user can change the device field after import using the part manager <acronym title="Graphical User Interface">GUI</acronym>.
+
+A type of part. The device name only provides a mechanism to map parts to symbols. A part in the library of device resistor can use all the symbols in the library where device is resistor. Similarly, a symbol where device is resistor can represent any part of device resistor. When importing a symbol, the database uses the value of the symbol attribute DEVICE as the initial value for the device field. The user can change the device field after import using the part manager <acronym title="Graphical User Interface">GUI</acronym>.
+
</p>
-<table class="inline">
- <tr>
- <th class="leftalign"> Field </th><th class="leftalign"> Type </th><th class="leftalign"> Description </th>
+<div class="table sectionedit139"><table class="inline">
+ <tr class="row0">
+ <th class="col0 leftalign"> Field </th><th class="col1 leftalign"> Type </th><th class="col2 leftalign"> Description </th>
</tr>
- <tr>
- <td class="leftalign"> DeviceID </td><td class="rightalign"> </td><td class="leftalign"> Surrogate key </td>
+ <tr class="row1">
+ <td class="col0 leftalign"> DeviceID </td><td class="col1 leftalign"> </td><td class="col2 leftalign"> Surrogate key </td>
</tr>
- <tr>
- <td> DeviceName </td><td> String </td><td> The unique name of the device </td>
+ <tr class="row2">
+ <td class="col0"> DeviceName </td><td class="col1"> String </td><td class="col2"> The unique name of the device </td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT139 TABLE [3536-3703] -->
</div>
<h4><a name="document" id="document">Document</a></h4>
<div class="level4">
<p>
- Any file associated with a part. Documents can include datasheets, erata, user manuals, etc… This entity stores a path to the actual document file. The path could either be local or network. The path stored in the database is relative to the base path stored in the configuration file.
+
+Any file associated with a part. Documents can include datasheets, erata, user manuals, etcâ?¦ This entity stores a path to the actual document file. The path could either be local or network. The path stored in the database is relative to the base path stored in the configuration file.
+
</p>
-<table class="inline">
- <tr>
- <th class="leftalign"> Field </th><th class="leftalign"> Type </th><th class="leftalign"> Description </th>
+<div class="table sectionedit140"><table class="inline">
+ <tr class="row0">
+ <th class="col0 leftalign"> Field </th><th class="col1 leftalign"> Type </th><th class="col2 leftalign"> Description </th>
</tr>
- <tr>
- <td class="leftalign"> DocumentID </td><td class="rightalign"> </td><td class="leftalign"> Surrogate key </td>
+ <tr class="row1">
+ <td class="col0 leftalign"> DocumentID </td><td class="col1 leftalign"> </td><td class="col2 leftalign"> Surrogate key </td>
</tr>
- <tr>
- <td class="leftalign"> Category </td><td> String </td><td> The documentâ??s category (e.g. â??Datasheetâ??, â??Erataâ??, â??User Manualâ??) </td>
+ <tr class="row2">
+ <td class="col0 leftalign"> Category </td><td class="col1"> String </td><td class="col2"> The document's category (e.g. â??Datasheetâ??, â??Erataâ??, â??User Manualâ??) </td>
</tr>
- <tr>
- <td class="leftalign"> Title </td><td> String </td><td class="leftalign"> The documentâ??s title </td>
+ <tr class="row3">
+ <td class="col0 leftalign"> Title </td><td class="col1"> String </td><td class="col2 leftalign"> The document's title </td>
</tr>
- <tr>
- <td class="leftalign"> SourceURL </td><td> String </td><td class="leftalign"> The <acronym title="Uniform Resource Locator">URL</acronym> where the document can be obtained on the Internet </td>
+ <tr class="row4">
+ <td class="col0 leftalign"> SourceURL </td><td class="col1"> String </td><td class="col2 leftalign"> The <acronym title="Uniform Resource Locator">URL</acronym> where the document can be obtained on the Internet </td>
</tr>
- <tr>
- <td> FileLocation </td><td> String </td><td class="leftalign"> The location of the locally stored document </td>
+ <tr class="row5">
+ <td class="col0"> FileLocation </td><td class="col1"> String </td><td class="col2 leftalign"> The location of the locally stored document </td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT140 TABLE [4015-4584] -->
</div>
<h4><a name="footprint" id="footprint">Footprint</a></h4>
<div class="level4">
<p>
- The PCB artwork associated with a package. This entity stores a path to the actual PCB footprint file. The path could either be local or network. The path stored in the database is relative to the base path stored in the configuration file.
+
+The PCB artwork associated with a package. This entity stores a path to the actual PCB footprint file. The path could either be local or network. The path stored in the database is relative to the base path stored in the configuration file.
+
</p>
-<table class="inline">
- <tr>
- <th class="leftalign"> Field </th><th class="leftalign"> Type </th><th class="leftalign"> Description </th>
+<div class="table sectionedit141"><table class="inline">
+ <tr class="row0">
+ <th class="col0 leftalign"> Field </th><th class="col1 leftalign"> Type </th><th class="col2 leftalign"> Description </th>
</tr>
- <tr>
- <td class="leftalign"> FootprintID </td><td class="rightalign"> </td><td class="leftalign"> Surrogate key </td>
+ <tr class="row1">
+ <td class="col0 leftalign"> FootprintID </td><td class="col1 leftalign"> </td><td class="col2 leftalign"> Surrogate key </td>
</tr>
- <tr>
- <td> FootprintName </td><td> String </td><td> The unique name of the footprint </td>
+ <tr class="row2">
+ <td class="col0"> FootprintName </td><td class="col1"> String </td><td class="col2"> The unique name of the footprint </td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT141 TABLE [4850-5035] -->
</div>
<h4><a name="model" id="model">Model</a></h4>
<div class="level4">
-<table class="inline">
- <tr>
- <th class="leftalign"> Field </th><th class="leftalign"> Type </th><th class="leftalign"> Description </th>
+<div class="table sectionedit142"><table class="inline">
+ <tr class="row0">
+ <th class="col0 leftalign"> Field </th><th class="col1 leftalign"> Type </th><th class="col2 leftalign"> Description </th>
</tr>
- <tr>
- <td class="leftalign"> ModelID </td><td class="rightalign"> </td><td class="leftalign"> Surrogate key </td>
+ <tr class="row1">
+ <td class="col0 leftalign"> ModelID </td><td class="col1 leftalign"> </td><td class="col2 leftalign"> Surrogate key </td>
</tr>
- <tr>
- <td> ModelName </td><td> String </td><td class="leftalign"> The name of the MODEL within the model file. </td>
+ <tr class="row2">
+ <td class="col0"> ModelName </td><td class="col1"> String </td><td class="col2 leftalign"> The name of the MODEL within the model file. </td>
</tr>
- <tr>
- <td> ModelPath </td><td> String </td><td class="leftalign"> Absolute path to the model file. </td>
+ <tr class="row3">
+ <td class="col0"> ModelPath </td><td class="col1"> String </td><td class="col2 leftalign"> Absolute path to the model file. </td>
</tr>
- <tr>
- <td> ModelType </td><td> String </td><td class="leftalign"> The model type: IBIS, PSPICE, etc… </td>
+ <tr class="row4">
+ <td class="col0"> ModelType </td><td class="col1"> String </td><td class="col2 leftalign"> The model type: IBIS, PSPICE, etcâ?¦ </td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT142 TABLE [5052-5431] -->
</div>
<h5><a name="spice" id="spice">Spice</a></h5>
<div class="level5">
<p>
- When instantiating a component or creating a heavy symbol that uses a Spice model, the following database columns map to the following attributes.
+
+When instantiating a component or creating a heavy symbol that uses a Spice model, the following database columns map to the following attributes.
+
</p>
-<table class="inline">
- <tr>
- <th class="leftalign"> Column </th><th class="leftalign"> Attribute </th><th class="leftalign"> Notes </th>
+<div class="table sectionedit143"><table class="inline">
+ <tr class="row0">
+ <th class="col0 leftalign"> Column </th><th class="col1 leftalign"> Attribute </th><th class="col2 leftalign"> Notes </th>
</tr>
- <tr>
- <td> Model.ModelName </td><td> MODEL-NAME </td><td class="rightalign"> </td>
+ <tr class="row1">
+ <td class="col0"> Model.ModelName </td><td class="col1"> MODEL-NAME </td><td class="col2 leftalign"> </td>
</tr>
- <tr>
- <td> Model.ModelPath </td><td class="leftalign"> FILE </td><td> Should use absolute path. </td>
+ <tr class="row2">
+ <td class="col0"> Model.ModelPath </td><td class="col1 leftalign"> FILE </td><td class="col2"> Should use absolute path. </td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT143 TABLE [5594-5776] -->
</div>
<h4><a name="part_flat" id="part_flat">Part (Flat)</a></h4>
<div class="level4">
<p>
- A part represents a class of components. The database uses this version of the part table when configured to use a flat part table. The flat and hierarchical parts tables are mutually exclusive. The database uses one or the other.
+
+A part represents a class of components. The database uses this version of the part table when configured to use a flat part table. The flat and hierarchical parts tables are mutually exclusive. The database uses one or the other.
+
</p>
-<table class="inline">
- <tr>
- <th class="leftalign"> Field </th><th> Type </th><th class="leftalign"> Description </th>
+<div class="table sectionedit144"><table class="inline">
+ <tr class="row0">
+ <th class="col0 leftalign"> Field </th><th class="col1"> Type </th><th class="col2 leftalign"> Description </th>
</tr>
- <tr>
- <td class="leftalign"> PartID </td><td class="rightalign"> </td><td class="leftalign"> Surrogate key </td>
+ <tr class="row1">
+ <td class="col0 leftalign"> PartID </td><td class="col1 leftalign"> </td><td class="col2 leftalign"> Surrogate key </td>
</tr>
- <tr>
- <td class="leftalign"> CompanyID </td><td class="rightalign"> </td><td> Foreign key to company specifies manufacturer </td>
+ <tr class="row2">
+ <td class="col0 leftalign"> CompanyID </td><td class="col1 leftalign"> </td><td class="col2"> Foreign key to company specifies manufacturer </td>
</tr>
- <tr>
- <td> PartNumber </td><td> String </td><td class="leftalign"> The manufacturersâ??s part number </td>
+ <tr class="row3">
+ <td class="col0"> PartNumber </td><td class="col1"> String </td><td class="col2 leftalign"> The manufacturers's part number </td>
</tr>
- <tr>
- <td class="leftalign"> DeviceID </td><td class="rightalign"> </td><td class="leftalign"> Foreign key to Device </td>
+ <tr class="row4">
+ <td class="col0 leftalign"> DeviceID </td><td class="col1 leftalign"> </td><td class="col2 leftalign"> Foreign key to Device </td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT144 TABLE [6031-6388] -->
<p>
- Other columns TBD.
+
+Other columns TBD.
</p>
</div>
@@ -284,79 +285,86 @@ The category also stores the names of database views and stored procedures to ac
<div class="level4">
<p>
- A part represents a class of components. The database uses this version of the part table when configured to use hierarchical part tables. The flat and hierarchical parts tables are mutually exclusive. The database uses one or the other.
+
+A part represents a class of components. The database uses this version of the part table when configured to use hierarchical part tables. The flat and hierarchical parts tables are mutually exclusive. The database uses one or the other.
+
</p>
-<table class="inline">
- <tr>
- <th class="leftalign"> Field </th><th> Type </th><th class="leftalign"> Description </th>
+<div class="table sectionedit145"><table class="inline">
+ <tr class="row0">
+ <th class="col0 leftalign"> Field </th><th class="col1"> Type </th><th class="col2 leftalign"> Description </th>
</tr>
- <tr>
- <td class="leftalign"> PartID </td><td class="rightalign"> </td><td class="leftalign"> Surrogate key </td>
+ <tr class="row1">
+ <td class="col0 leftalign"> PartID </td><td class="col1 leftalign"> </td><td class="col2 leftalign"> Surrogate key </td>
</tr>
- <tr>
- <td class="leftalign"> CompanyID </td><td class="rightalign"> </td><td> Foreign key to company specifies manufacturer </td>
+ <tr class="row2">
+ <td class="col0 leftalign"> CompanyID </td><td class="col1 leftalign"> </td><td class="col2"> Foreign key to company specifies manufacturer </td>
</tr>
- <tr>
- <td> PartNumber </td><td> String </td><td class="leftalign"> The manufacturersâ??s part number </td>
+ <tr class="row3">
+ <td class="col0"> PartNumber </td><td class="col1"> String </td><td class="col2 leftalign"> The manufacturers's part number </td>
</tr>
- <tr>
- <td class="leftalign"> DeviceID </td><td class="rightalign"> </td><td class="leftalign"> Foreign key to Device </td>
+ <tr class="row4">
+ <td class="col0 leftalign"> DeviceID </td><td class="col1 leftalign"> </td><td class="col2 leftalign"> Foreign key to Device </td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT145 TABLE [6679-7036] -->
</div>
<h4><a name="package" id="package">Package</a></h4>
<div class="level4">
<p>
- The physical structure, or form-factor, of a part (i.e. 0603, SOT-23, PDIP16). Each package can associate with zero or more footprints. Also, each footprint could represent zero or more packages.
+
+The physical structure, or form-factor, of a part (i.e. 0603, SOT-23, PDIP16). Each package can associate with zero or more footprints. Also, each footprint could represent zero or more packages.
+
</p>
-<table class="inline">
- <tr>
- <th class="leftalign"> Field </th><th class="leftalign"> Type </th><th class="leftalign"> Description </th>
+<div class="table sectionedit146"><table class="inline">
+ <tr class="row0">
+ <th class="col0 leftalign"> Field </th><th class="col1 leftalign"> Type </th><th class="col2 leftalign"> Description </th>
</tr>
- <tr>
- <td class="leftalign"> PackageID </td><td class="rightalign"> </td><td class="leftalign"> Surrogate key </td>
+ <tr class="row1">
+ <td class="col0 leftalign"> PackageID </td><td class="col1 leftalign"> </td><td class="col2 leftalign"> Surrogate key </td>
</tr>
- <tr>
- <td> PackageName </td><td> String </td><td class="leftalign"> The unique name of the package </td>
+ <tr class="row2">
+ <td class="col0"> PackageName </td><td class="col1"> String </td><td class="col2 leftalign"> The unique name of the package </td>
</tr>
- <tr>
- <td class="leftalign"> Technology </td><td> String </td><td> The type of package. Either â??SMTâ?? or â??THâ?? </td>
+ <tr class="row3">
+ <td class="col0 leftalign"> Technology </td><td class="col1"> String </td><td class="col2"> The type of package. Either â??SMTâ?? or â??THâ?? </td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT146 TABLE [7254-7533] -->
</div>
<h4><a name="symbol" id="symbol">Symbol</a></h4>
<div class="level4">
<p>
- The graphical representation of a part. This entity uses the symbol base filename as the unique name of the symbol. This base filename is relative to one of the component libraries found in the configuration files. The component library paths can either be local or network.
+
+The graphical representation of a part. This entity uses the symbol base filename as the unique name of the symbol. This base filename is relative to one of the component libraries found in the configuration files. The component library paths can either be local or network.
+
</p>
-<table class="inline">
- <tr>
- <th class="leftalign"> Field </th><th class="leftalign"> Type </th><th class="leftalign"> Description </th>
+<div class="table sectionedit147"><table class="inline">
+ <tr class="row0">
+ <th class="col0 leftalign"> Field </th><th class="col1 leftalign"> Type </th><th class="col2 leftalign"> Description </th>
</tr>
- <tr>
- <td class="leftalign"> SymbolID </td><td class="rightalign"> </td><td class="leftalign"> Surrogate key </td>
+ <tr class="row1">
+ <td class="col0 leftalign"> SymbolID </td><td class="col1 leftalign"> </td><td class="col2 leftalign"> Surrogate key </td>
</tr>
- <tr>
- <td> SymbolName </td><td> String </td><td> The unique name of the symbol. This field contains the base filename of the symbol. </td>
+ <tr class="row2">
+ <td class="col0"> SymbolName </td><td class="col1"> String </td><td class="col2"> The unique name of the symbol. This field contains the base filename of the symbol. </td>
</tr>
- <tr>
- <td class="leftalign"> DeviceID </td><td class="rightalign"> </td><td class="leftalign"> Foreign key to Device </td>
+ <tr class="row3">
+ <td class="col0 leftalign"> DeviceID </td><td class="col1 leftalign"> </td><td class="col2 leftalign"> Foreign key to Device </td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT147 TABLE [7827-8212] -->
</div>
-<!-- SECTION "Entities" [1309-8103] -->
-<h3><a name="part_categories" id="part_categories">Part Categories</a></h3>
+<!-- EDIT136 SECTION "Entities" [1419-8213] -->
+<h3 class="sectionedit148"><a name="part_categories" id="part_categories">Part Categories</a></h3>
<div class="level3">
<p>
- Part categories break down classes of parts hierarchically. The category hierarchy exists separately than the part hierarchy. The category hierarchy only provides the user with a system to locate parts quickly. A child in the category hierarchy does not need to inherit the attributes of a parent.
+
+Part categories break down classes of parts hierarchically. The category hierarchy exists separately than the part hierarchy. The category hierarchy only provides the user with a system to locate parts quickly. A child in the category hierarchy does not need to inherit the attributes of a parent.
</p>
<p>
@@ -371,7 +379,8 @@ It may be difficult to change the categories, using a <acronym title="Graphical
</div>
<p>
-The default hierarchy of parts follow:
+The default hierarchy of parts follow:
+
</p>
<ul>
<li class="level1"><div class="li"> Discretes</div>
@@ -401,19 +410,21 @@ The default hierarchy of parts follow:
</ul>
</div>
-<!-- SECTION "Part Categories" [8104-9162] -->
-<h3><a name="part_hierarchy" id="part_hierarchy">Part Hierarchy</a></h3>
+<!-- EDIT148 SECTION "Part Categories" [8214-9277] -->
+<h3 class="sectionedit149"><a name="part_hierarchy" id="part_hierarchy">Part Hierarchy</a></h3>
<div class="level3">
<p>
- The part hierarchy allows the database to attach additional attributes to a class of parts. These attributes provide a faster means to locate and select parts, especially commodity parts. The database only provides these additional attributes when configured to use hierarchical part tables.
+
+The part hierarchy allows the database to attach additional attributes to a class of parts. These attributes provide a faster means to locate and select parts, especially commodity parts. The database only provides these additional attributes when configured to use hierarchical part tables.
</p>
<p>
These additional attributes, stored in numeric format, allow <acronym title="Structured Query Language">SQL</acronym> to select parts. For example, to locate diodes with reverse voltage greater than 60 volts, use the following <acronym title="Structured Query Language">SQL</acronym> statement.
</p>
-<pre class="code sql"><span class="kw1">SELECT</span> * <span class="kw1">FROM</span> DiodeV
- <span class="kw1">WHERE</span> VR > <span class="nu0">60</span>;</pre>
+<pre class="code sql"><pre class="code sql"><span class="kw1">SELECT</span> * <span class="kw1">FROM</span> DiodeV
+ <span class="kw1">WHERE</span> VR > <span class="nu0">60</span>;</pre></pre>
+
<p>
The intent of the part hierarchy does not include exhaustively classifying all electronic parts or fully parameterizing any class of electronic part. The part hierarchy simply intends to allow the user to quickly locate a part, such as a 4.75 kΩ 1% 0603.
</p>
@@ -423,7 +434,8 @@ The intent of the part hierarchy does not include exhaustively classifying all e
</p>
<p>
-Proposed guidelines for including attributes:
+Proposed guidelines for including attributes:
+
</p>
<ul>
<li class="level1"><div class="li"> Include attributes that are encoded in the manufacturer part number.</div>
@@ -435,228 +447,388 @@ Proposed guidelines for including attributes:
</ul>
<p>
- These attributes may not work for everyone, so the database allows the user to customize these part tables.
+
+These attributes may not work for everyone, so the database allows the user to customize these part tables.
</p>
</div>
-<h4><a name="capacitors" id="capacitors">Capacitors</a></h4>
+<h4><a name="bjts" id="bjts">BJTs</a></h4>
<div class="level4">
<p>
- Capacitors extend part with one additional table of attributes.
+
+Bipolar Junction Transistors (BJTs) extend part with one additional table of attributes.
</p>
-<table class="inline">
- <tr>
- <th class="leftalign"> Field </th><th class="leftalign"> Type </th><th class="leftalign"> Units </th><th class="leftalign"> Description </th>
+
+<p>
+Table name: BJT
+</p>
+
+<p>
+View name: BJTV
+
+</p>
+<div class="table sectionedit150"><table class="inline">
+ <tr class="row0">
+ <th class="col0 leftalign"> Field </th><th class="col1 leftalign"> Type </th><th class="col2 leftalign"> Units </th><th class="col3 leftalign"> Description </th>
+ </tr>
+ <tr class="row1">
+ <td class="col0 leftalign"> PartID </td><td class="col1 leftalign"> </td><td class="col2 leftalign"> </td><td class="col3 leftalign"> Foreign key to Part </td>
+ </tr>
+ <tr class="row2">
+ <td class="col0 leftalign"> PackageID </td><td class="col1 leftalign"> </td><td class="col2 leftalign"> </td><td class="col3 leftalign"> Foreign key to Package </td>
+ </tr>
+ <tr class="row3">
+ <td class="col0 leftalign"> Polarity </td><td class="col1 leftalign"> </td><td class="col2 leftalign"> </td><td class="col3 leftalign"> Either NPN or PNP </td>
+ </tr>
+ <tr class="row4">
+ <td class="col0 leftalign"> MaxCollectorCurrent </td><td class="col1"> Physical </td><td class="col2 leftalign"> AMPS </td><td class="col3 leftalign"> Maximum collector current (Absolute maximum rating) </td>
+ </tr>
+ <tr class="row5">
+ <td class="col0 leftalign"> MaxCollectorEmitterVoltage </td><td class="col1"> Physical </td><td class="col2 leftalign"> VOLTS </td><td class="col3"> Maximum collector-emitter voltage (Absolute maximum rating) </td>
</tr>
- <tr>
- <td class="leftalign"> PartID </td><td class="rightalign"> </td><td class="rightalign"> </td><td class="leftalign"> Foreign key to Part </td>
+ <tr class="row6">
+ <td class="col0 leftalign"> TransitionFrequency </td><td class="col1"> Physical </td><td class="col2 leftalign"> HERTZ </td><td class="col3 leftalign"> </td>
</tr>
- <tr>
- <td class="leftalign"> PackageID </td><td class="rightalign"> </td><td class="rightalign"> </td><td> Foreign key to Package </td>
+ <tr class="row7">
+ <td class="col0 leftalign"> PowerDissipation </td><td class="col1"> Physical </td><td class="col2 leftalign"> WATTS </td><td class="col3 leftalign"> Power dissipation (Pd) not including any derating </td>
</tr>
- <tr>
- <td> Capacitance </td><td> Physical </td><td class="leftalign"> FARADS </td><td class="leftalign"> Capacitance </td>
+</table></div>
+<!-- EDIT150 TABLE [10688-11623] -->
+<p>
+
+The same table contains small-signal and power BJTs. These transistors can be
+placed into separate views using the following criteria.
+
+</p>
+<div class="table sectionedit151"><table class="inline">
+ <tr class="row0">
+ <th class="col0 leftalign"> Category </th><th class="col1 leftalign"> Criteria </th><th class="col2"> View Name </th>
</tr>
-</table>
+ <tr class="row1">
+ <td class="col0"> Small-signal BJT </td><td class="col1"> PowerDissipation < 1.0 </td><td class="col2 leftalign"> TBD </td>
+ </tr>
+ <tr class="row2">
+ <td class="col0 leftalign"> Power BJT </td><td class="col1"> PowerDissipation >= 1.0 </td><td class="col2 leftalign"> TBD </td>
+ </tr>
+</table></div>
+<!-- EDIT151 TABLE [11761-11937] -->
+</div>
+
+<h4><a name="capacitors" id="capacitors">Capacitors</a></h4>
+<div class="level4">
<p>
- When instantiating a component or creating a heavy symbol, the following database columns map to the following attributes.
+
+Capacitors extend part with one additional table of attributes.
+
</p>
-<table class="inline">
- <tr>
- <th class="leftalign"> Column </th><th> Attribute </th><th class="leftalign"> Notes </th>
+<div class="table sectionedit152"><table class="inline">
+ <tr class="row0">
+ <th class="col0 leftalign"> Field </th><th class="col1 leftalign"> Type </th><th class="col2 leftalign"> Units </th><th class="col3 leftalign"> Description </th>
+ </tr>
+ <tr class="row1">
+ <td class="col0 leftalign"> PartID </td><td class="col1 leftalign"> </td><td class="col2 leftalign"> </td><td class="col3 leftalign"> Foreign key to Part </td>
</tr>
- <tr>
- <td class="leftalign"> Device.DeviceName </td><td class="leftalign"> DEVICE </td><td class="rightalign"> </td>
+ <tr class="row2">
+ <td class="col0 leftalign"> PackageID </td><td class="col1 leftalign"> </td><td class="col2 leftalign"> </td><td class="col3"> Foreign key to Package </td>
</tr>
- <tr>
- <td> Capacitor.Capacitance </td><td class="leftalign"> VALUE </td><td class="rightalign"> </td>
+ <tr class="row3">
+ <td class="col0"> Capacitance </td><td class="col1"> Physical </td><td class="col2 leftalign"> FARADS </td><td class="col3 leftalign"> Capacitance </td>
</tr>
-</table>
+</table></div>
+<!-- EDIT152 TABLE [12024-12271] -->
+<p>
+When instantiating a component or creating a heavy symbol, the following database columns map to the following attributes.
+
+</p>
+<div class="table sectionedit153"><table class="inline">
+ <tr class="row0">
+ <th class="col0 leftalign"> Column </th><th class="col1"> Attribute </th><th class="col2 leftalign"> Notes </th>
+ </tr>
+ <tr class="row1">
+ <td class="col0 leftalign"> Device.DeviceName </td><td class="col1 leftalign"> DEVICE </td><td class="col2 leftalign"> </td>
+ </tr>
+ <tr class="row2">
+ <td class="col0"> Capacitor.Capacitance </td><td class="col1 leftalign"> VALUE </td><td class="col2 leftalign"> </td>
+ </tr>
+</table></div>
+<!-- EDIT153 TABLE [12397-12585] -->
</div>
<h4><a name="inductors" id="inductors">Inductors</a></h4>
<div class="level4">
<p>
- Inductors extend part with one additional table of attributes.
+
+Inductors extend part with one additional table of attributes.
+
</p>
-<table class="inline">
- <tr>
- <th class="leftalign"> Field </th><th class="leftalign"> Type </th><th class="leftalign"> Units </th><th class="leftalign"> Description </th>
+<div class="table sectionedit154"><table class="inline">
+ <tr class="row0">
+ <th class="col0 leftalign"> Field </th><th class="col1 leftalign"> Type </th><th class="col2 leftalign"> Units </th><th class="col3 leftalign"> Description </th>
</tr>
- <tr>
- <td class="leftalign"> PartID </td><td class="rightalign"> </td><td class="rightalign"> </td><td class="leftalign"> Foreign key to Part </td>
+ <tr class="row1">
+ <td class="col0 leftalign"> PartID </td><td class="col1 leftalign"> </td><td class="col2 leftalign"> </td><td class="col3 leftalign"> Foreign key to Part </td>
</tr>
- <tr>
- <td class="leftalign"> PackageID </td><td class="rightalign"> </td><td class="rightalign"> </td><td> Foreign key to Package </td>
+ <tr class="row2">
+ <td class="col0 leftalign"> PackageID </td><td class="col1 leftalign"> </td><td class="col2 leftalign"> </td><td class="col3"> Foreign key to Package </td>
</tr>
- <tr>
- <td> Inductance </td><td> Physical </td><td class="leftalign"> HENRYS </td><td class="leftalign"> Inductance </td>
+ <tr class="row3">
+ <td class="col0"> Inductance </td><td class="col1"> Physical </td><td class="col2 leftalign"> HENRYS </td><td class="col3 leftalign"> Inductance </td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT154 TABLE [12670-12913] -->
<p>
- When instantiating a component or creating a heavy symbol, the following database columns map to the following attributes.
+
+When instantiating a component or creating a heavy symbol, the following database columns map to the following attributes.
+
</p>
-<table class="inline">
- <tr>
- <th class="leftalign"> Column </th><th> Attribute </th><th class="leftalign"> Notes </th>
+<div class="table sectionedit155"><table class="inline">
+ <tr class="row0">
+ <th class="col0 leftalign"> Column </th><th class="col1"> Attribute </th><th class="col2 leftalign"> Notes </th>
</tr>
- <tr>
- <td class="leftalign"> Device.DeviceName </td><td class="leftalign"> DEVICE </td><td class="rightalign"> </td>
+ <tr class="row1">
+ <td class="col0 leftalign"> Device.DeviceName </td><td class="col1 leftalign"> DEVICE </td><td class="col2 leftalign"> </td>
</tr>
- <tr>
- <td> Inductor.Inductance </td><td class="leftalign"> VALUE </td><td class="rightalign"> </td>
+ <tr class="row2">
+ <td class="col0"> Inductor.Inductance </td><td class="col1 leftalign"> VALUE </td><td class="col2 leftalign"> </td>
</tr>
-</table>
+</table></div>
+<!-- EDIT155 TABLE [13039-13221] -->
+</div>
+
+<h4><a name="mosfets" id="mosfets">MOSFETs</a></h4>
+<div class="level4">
+
+<p>
+
+MOSFETs extend part with one additional table of attributes.
+</p>
+<div class="table sectionedit156"><table class="inline">
+ <tr class="row0">
+ <th class="col0 leftalign"> Field </th><th class="col1 leftalign"> Type </th><th class="col2 leftalign"> Units </th><th class="col3 leftalign"> Description </th>
+ </tr>
+ <tr class="row1">
+ <td class="col0 leftalign"> PartID </td><td class="col1 leftalign"> </td><td class="col2 leftalign"> </td><td class="col3 leftalign"> Foreign key to Part </td>
+ </tr>
+ <tr class="row2">
+ <td class="col0 leftalign"> PackageID </td><td class="col1 leftalign"> </td><td class="col2 leftalign"> </td><td class="col3 leftalign"> Foreign key to Package </td>
+ </tr>
+ <tr class="row3">
+ <td class="col0 leftalign"> Polarity </td><td class="col1 leftalign"> </td><td class="col2 leftalign"> </td><td class="col3 leftalign"> Either N or P </td>
+ </tr>
+ <tr class="row4">
+ <td class="col0 leftalign"> MaxDrainSourceVoltage </td><td class="col1"> Physical </td><td class="col2 leftalign"> VOLTS </td><td class="col3 leftalign"> Maximum drain-source voltage (Absolute maximum rating) </td>
+ </tr>
+ <tr class="row5">
+ <td class="col0 leftalign"> MaxDrainCurrent </td><td class="col1"> Physical </td><td class="col2 leftalign"> AMPS </td><td class="col3"> Maximum continuous drain current (Absolute maximum rating) </td>
+ </tr>
+ <tr class="row6">
+ <td class="col0"> TypGateThresholdVoltage </td><td class="col1"> Physical </td><td class="col2 leftalign"> VOLTS </td><td class="col3 leftalign"> Typical gate threshold voltage </td>
+ </tr>
+ <tr class="row7">
+ <td class="col0 leftalign"> PowerDissipation </td><td class="col1"> Physical </td><td class="col2 leftalign"> WATTS </td><td class="col3 leftalign"> Power dissipation (Pd) not including any derating </td>
+ </tr>
+</table></div>
+<!-- EDIT156 TABLE [13302-14181] -->
</div>
-<h4><a name="rectifier_and_switching_diodes" id="rectifier_and_switching_diodes">Rectifier and Switching Diodes</a></h4>
+<h4><a name="rectifier_small-signal_and_switching_diodes" id="rectifier_small-signal_and_switching_diodes">Rectifier, Small-signal and Switching Diodes</a></h4>
<div class="level4">
<p>
- Rectifier and switching diodes extend part with one additional table of attributes. Most diodes can be placed into this table.
+
+Rectifier, small-signal and switching diodes extend part with one additional table of
+attributes. Most diodes can be placed into this table.
</p>
-<table class="inline">
- <tr>
- <th class="leftalign"> Field </th><th class="leftalign"> Type </th><th> Units </th><th class="leftalign"> Description </th>
+
+<p>
+Table name: Diode
+</p>
+
+<p>
+View name: DiodeV
+
+</p>
+<div class="table sectionedit157"><table class="inline">
+ <tr class="row0">
+ <th class="col0 leftalign"> Field </th><th class="col1 leftalign"> Type </th><th class="col2"> Units </th><th class="col3 leftalign"> Description </th>
</tr>
- <tr>
- <td class="leftalign"> PartID </td><td class="rightalign"> </td><td class="rightalign"> </td><td class="leftalign"> Foreign key to Part </td>
+ <tr class="row1">
+ <td class="col0 leftalign"> PartID </td><td class="col1 leftalign"> </td><td class="col2 leftalign"> </td><td class="col3 leftalign"> Foreign key to Part </td>
</tr>
- <tr>
- <td class="leftalign"> PackageID </td><td class="rightalign"> </td><td class="rightalign"> </td><td class="leftalign"> Foreign key to Package </td>
+ <tr class="row2">
+ <td class="col0 leftalign"> PackageID </td><td class="col1 leftalign"> </td><td class="col2 leftalign"> </td><td class="col3 leftalign"> Foreign key to Package </td>
</tr>
- <tr>
- <td> MaxReverseVoltage </td><td> Physical </td><td> VOLTS </td><td> Maximum reverse voltage (Absolute maximum rating) </td>
+ <tr class="row3">
+ <td class="col0"> MaxReverseVoltage </td><td class="col1"> Physical </td><td class="col2"> VOLTS </td><td class="col3"> Maximum reverse voltage (Absolute maximum rating) </td>
</tr>
- <tr>
- <td> MaxForwardCurrent </td><td> Physical </td><td class="leftalign"> AMPS </td><td> Maximum forward current (Absolute maximum rating) </td>
+ <tr class="row4">
+ <td class="col0"> MaxForwardCurrent </td><td class="col1"> Physical </td><td class="col2 leftalign"> AMPS </td><td class="col3"> Maximum forward current (Absolute maximum rating) </td>
</tr>
- <tr>
- <td> TypForwardVoltage </td><td> Physical </td><td> VOLTS </td><td class="leftalign"> Typical forward voltage </td>
+ <tr class="row5">
+ <td class="col0"> TypForwardVoltage </td><td class="col1"> Physical </td><td class="col2"> VOLTS </td><td class="col3 leftalign"> Typical forward voltage </td>
</tr>
- <tr>
- <td> AveForwardCurrent </td><td> Physical </td><td class="leftalign"> AMPS </td><td class="leftalign"> Average forward current </td>
+ <tr class="row6">
+ <td class="col0"> AveForwardCurrent </td><td class="col1"> Physical </td><td class="col2 leftalign"> AMPS </td><td class="col3 leftalign"> Average forward current </td>
</tr>
-</table>
+</table></div>
+<!-- EDIT157 TABLE [14417-15067] -->
+<p>
+The same table contains rectifier, small-signal and switching diodes. These diodes can be
+placed into separate views using the following criteria.
+
+</p>
+<div class="table sectionedit158"><table class="inline">
+ <tr class="row0">
+ <th class="col0 leftalign"> Category </th><th class="col1 leftalign"> Criteria </th><th class="col2"> View Name </th>
+ </tr>
+ <tr class="row1">
+ <td class="col0"> Small-signal and switching diodes </td><td class="col1"> AveForwardCurrent < 0.5 </td><td class="col2 leftalign"> TBD </td>
+ </tr>
+ <tr class="row2">
+ <td class="col0 leftalign"> Rectifier diodes </td><td class="col1"> AveForwardCurrent >= 0.5 </td><td class="col2 leftalign"> TBD </td>
+ </tr>
+</table></div>
+<!-- EDIT158 TABLE [15217-15447] -->
</div>
<h4><a name="resistors" id="resistors">Resistors</a></h4>
<div class="level4">
<p>
- Resistors extend part with one additional table of attributes.
+
+Resistors extend part with one additional table of attributes.
+
</p>
-<table class="inline">
- <tr>
- <th class="leftalign"> Field </th><th class="leftalign"> Type </th><th class="leftalign"> Units </th><th class="leftalign"> Description </th>
+<div class="table sectionedit159"><table class="inline">
+ <tr class="row0">
+ <th class="col0 leftalign"> Field </th><th class="col1 leftalign"> Type </th><th class="col2 leftalign"> Units </th><th class="col3 leftalign"> Description </th>
</tr>
- <tr>
- <td class="leftalign"> PartID </td><td class="rightalign"> </td><td class="rightalign"> </td><td class="leftalign"> Foreign key to Part </td>
+ <tr class="row1">
+ <td class="col0 leftalign"> PartID </td><td class="col1 leftalign"> </td><td class="col2 leftalign"> </td><td class="col3 leftalign"> Foreign key to Part </td>
</tr>
- <tr>
- <td class="leftalign"> PackageID </td><td class="rightalign"> </td><td class="rightalign"> </td><td> Foreign key to Package </td>
+ <tr class="row2">
+ <td class="col0 leftalign"> PackageID </td><td class="col1 leftalign"> </td><td class="col2 leftalign"> </td><td class="col3"> Foreign key to Package </td>
</tr>
- <tr>
- <td> Resistance </td><td> Physical </td><td class="leftalign"> OHMS </td><td class="leftalign"> Resistance </td>
+ <tr class="row3">
+ <td class="col0"> Resistance </td><td class="col1"> Physical </td><td class="col2 leftalign"> OHMS </td><td class="col3 leftalign"> Resistance </td>
</tr>
- <tr>
- <td class="leftalign"> Tolerance </td><td> Physical </td><td> PERCENT </td><td class="leftalign"> Tolerance </td>
+ <tr class="row4">
+ <td class="col0 leftalign"> Tolerance </td><td class="col1"> Physical </td><td class="col2"> PERCENT </td><td class="col3 leftalign"> Tolerance </td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT159 TABLE [15532-15836] -->
<p>
- When instantiating a component or creating a heavy symbol, the following database columns map to the following attributes.
+
+When instantiating a component or creating a heavy symbol, the following database columns map to the following attributes.
+
</p>
-<table class="inline">
- <tr>
- <th class="leftalign"> Column </th><th> Attribute </th><th class="leftalign"> Notes </th>
+<div class="table sectionedit160"><table class="inline">
+ <tr class="row0">
+ <th class="col0 leftalign"> Column </th><th class="col1"> Attribute </th><th class="col2 leftalign"> Notes </th>
</tr>
- <tr>
- <td class="leftalign"> Device.DeviceName </td><td class="leftalign"> DEVICE </td><td class="rightalign"> </td>
+ <tr class="row1">
+ <td class="col0 leftalign"> Device.DeviceName </td><td class="col1 leftalign"> DEVICE </td><td class="col2 leftalign"> </td>
</tr>
- <tr>
- <td> Resistor.Resistance </td><td class="leftalign"> VALUE </td><td class="rightalign"> </td>
+ <tr class="row2">
+ <td class="col0"> Resistor.Resistance </td><td class="col1 leftalign"> VALUE </td><td class="col2 leftalign"> </td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT160 TABLE [15962-16144] -->
</div>
<h4><a name="tvs_diodes" id="tvs_diodes">TVS Diodes</a></h4>
<div class="level4">
<p>
- TVS diodes extend part with one additional table of attributes.
+
+TVS diodes extend part with one additional table of attributes.
+
</p>
-<table class="inline">
- <tr>
- <th class="leftalign"> Field </th><th class="leftalign"> Type </th><th> Units </th><th class="leftalign"> Description </th>
+<div class="table sectionedit161"><table class="inline">
+ <tr class="row0">
+ <th class="col0 leftalign"> Field </th><th class="col1 leftalign"> Type </th><th class="col2"> Units </th><th class="col3 leftalign"> Description </th>
</tr>
- <tr>
- <td class="leftalign"> PartID </td><td class="rightalign"> </td><td class="rightalign"> </td><td class="leftalign"> Foreign key to Part </td>
+ <tr class="row1">
+ <td class="col0 leftalign"> PartID </td><td class="col1 leftalign"> </td><td class="col2 leftalign"> </td><td class="col3 leftalign"> Foreign key to Part </td>
</tr>
- <tr>
- <td class="leftalign"> PackageID </td><td class="rightalign"> </td><td class="rightalign"> </td><td> Foreign key to Package </td>
+ <tr class="row2">
+ <td class="col0 leftalign"> PackageID </td><td class="col1 leftalign"> </td><td class="col2 leftalign"> </td><td class="col3"> Foreign key to Package </td>
</tr>
- <tr>
- <td class="leftalign"> WorkingVoltage </td><td> Physical </td><td> VOLTS </td><td class="leftalign"> Working voltage </td>
+ <tr class="row3">
+ <td class="col0 leftalign"> WorkingVoltage </td><td class="col1"> Physical </td><td class="col2"> VOLTS </td><td class="col3 leftalign"> Working voltage </td>
</tr>
- <tr>
- <td> BreakdownVoltage </td><td> Physical </td><td> VOLTS </td><td class="leftalign"> Breakdown voltage </td>
+ <tr class="row4">
+ <td class="col0"> BreakdownVoltage </td><td class="col1"> Physical </td><td class="col2"> VOLTS </td><td class="col3 leftalign"> Breakdown voltage </td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT161 TABLE [16231-16555] -->
</div>
<h4><a name="zener_diodes" id="zener_diodes">Zener Diodes</a></h4>
<div class="level4">
<p>
- Zener diodes extend part with one additional table of attributes.
+
+Zener diodes extend part with one additional table of attributes.
+</p>
+
+<p>
+Table name: ZenerDiode
+</p>
+
+<p>
+View name: ZenerDiodeV
+
</p>
-<table class="inline">
- <tr>
- <th class="leftalign"> Field </th><th class="leftalign"> Type </th><th> Units </th><th class="leftalign"> Description </th>
+<div class="table sectionedit162"><table class="inline">
+ <tr class="row0">
+ <th class="col0 leftalign"> Field </th><th class="col1 leftalign"> Type </th><th class="col2"> Units </th><th class="col3 leftalign"> Description </th>
</tr>
- <tr>
- <td class="leftalign"> PartID </td><td class="rightalign"> </td><td class="rightalign"> </td><td class="leftalign"> Foreign key to Part </td>
+ <tr class="row1">
+ <td class="col0 leftalign"> PartID </td><td class="col1 leftalign"> </td><td class="col2 leftalign"> </td><td class="col3 leftalign"> Foreign key to Part </td>
</tr>
- <tr>
- <td class="leftalign"> PackageID </td><td class="rightalign"> </td><td class="rightalign"> </td><td> Foreign key to Package </td>
+ <tr class="row2">
+ <td class="col0 leftalign"> PackageID </td><td class="col1 leftalign"> </td><td class="col2 leftalign"> </td><td class="col3 leftalign"> Foreign key to Package </td>
</tr>
- <tr>
- <td> ZenerVoltage </td><td> Physical </td><td> VOLTS </td><td class="leftalign"> Zener voltage </td>
+ <tr class="row3">
+ <td class="col0 leftalign"> TypZenerVoltage </td><td class="col1"> Physical </td><td class="col2"> VOLTS </td><td class="col3 leftalign"> Zener voltage </td>
</tr>
-</table>
-
+ <tr class="row4">
+ <td class="col0"> PowerDissipation </td><td class="col1"> Physical </td><td class="col2"> WATTS </td><td class="col3"> Power dissipation (Pd) not including any derating </td>
+ </tr>
+</table></div>
+<!-- EDIT162 TABLE [16694-17153] -->
</div>
-<!-- SECTION "Part Hierarchy" [9163-13953] -->
-<h2><a name="part_manager_gui" id="part_manager_gui">Part Manager GUI</a></h2>
+<!-- EDIT149 SECTION "Part Hierarchy" [9278-17154] -->
+<h2 class="sectionedit163"><a name="part_manager_gui" id="part_manager_gui">Part Manager GUI</a></h2>
<div class="level2">
<p>
- The part manager <acronym title="Graphical User Interface">GUI</acronym> is the main component of the part management system. The part manager <acronym title="Graphical User Interface">GUI</acronym> allows the user to browse and manipulate the part database and to cut and paste symbols into the schematic editor.
+
+The part manager <acronym title="Graphical User Interface">GUI</acronym> is the main component of the part management system. The part manager <acronym title="Graphical User Interface">GUI</acronym> allows the user to browse and manipulate the part database and to cut and paste symbols into the schematic editor.
</p>
</div>
-<!-- SECTION "Part Manager GUI" [13954-14195] -->
-<h3><a name="use_cases" id="use_cases">Use Cases</a></h3>
+<!-- EDIT163 SECTION "Part Manager GUI" [17155-17396] -->
+<h3 class="sectionedit164"><a name="use_cases" id="use_cases">Use Cases</a></h3>
<div class="level3">
</div>
-<h4><a name="uc.component.copy.clipboard" id="uc.component.copy.clipboard">uc.component.copy.clipboard</a></h4>
+<h4><a name="uccomponentcopyclipboard" id="uccomponentcopyclipboard">uc.component.copy.clipboard</a></h4>
<div class="level4">
<p>
- Copy a part to the clipboard as a component (light symbol).
+
+Copy a part to the clipboard as a component (light symbol).
+
</p>
<ol>
<li class="level1"><div class="li"> The user selects a part in the database.</div>
@@ -677,11 +849,13 @@ Proposed guidelines for including attributes:
</div>
-<h4><a name="uc.component.export.file" id="uc.component.export.file">uc.component.export.file</a></h4>
+<h4><a name="uccomponentexportfile" id="uccomponentexportfile">uc.component.export.file</a></h4>
<div class="level4">
<p>
- Export a part to a file as a heavy symbol.
+
+Export a part to a file as a heavy symbol.
+
</p>
<ol>
<li class="level1"><div class="li"> The user selects a part in the database.</div>
@@ -702,11 +876,13 @@ Proposed guidelines for including attributes:
</div>
-<h4><a name="uc.database.create" id="uc.database.create">uc.database.create</a></h4>
+<h4><a name="ucdatabasecreate" id="ucdatabasecreate">uc.database.create</a></h4>
<div class="level4">
<p>
- Create a new part database.
+
+Create a new part database.
+
</p>
<ol>
<li class="level1"><div class="li"> TBD</div>
@@ -715,11 +891,13 @@ Proposed guidelines for including attributes:
</div>
-<h4><a name="uc.database.destroy" id="uc.database.destroy">uc.database.destroy</a></h4>
+<h4><a name="ucdatabasedestroy" id="ucdatabasedestroy">uc.database.destroy</a></h4>
<div class="level4">
<p>
- Destroy an existing database.
+
+Destroy an existing database.
+
</p>
<ol>
<li class="level1"><div class="li"> The user selects the destroy database action.</div>
@@ -732,11 +910,13 @@ Proposed guidelines for including attributes:
</div>
-<h4><a name="uc.document.add" id="uc.document.add">uc.document.add</a></h4>
+<h4><a name="ucdocumentadd" id="ucdocumentadd">uc.document.add</a></h4>
<div class="level4">
<p>
- Add a new document to the database.
+
+Add a new document to the database.
+
</p>
<ol>
<li class="level1"><div class="li"> The user selects the add document action.</div>
@@ -749,11 +929,13 @@ Proposed guidelines for including attributes:
</div>
-<h4><a name="uc.document.attach" id="uc.document.attach">uc.document.attach</a></h4>
+<h4><a name="ucdocumentattach" id="ucdocumentattach">uc.document.attach</a></h4>
<div class="level4">
<p>
- Associate a document(s) with a part(s).
+
+Associate a document(s) with a part(s).
+
</p>
<ol>
<li class="level1"><div class="li"> The user selects one or more parts from the database.</div>
@@ -770,11 +952,13 @@ Proposed guidelines for including attributes:
</div>
-<h4><a name="uc.document.delete" id="uc.document.delete">uc.document.delete</a></h4>
+<h4><a name="ucdocumentdelete" id="ucdocumentdelete">uc.document.delete</a></h4>
<div class="level4">
<p>
- Delete a document(s) from the database. Remove all references.
+
+Delete a document(s) from the database. Remove all references.
+
</p>
<ol>
<li class="level1"><div class="li"> The user selects one or more documents in the database.</div>
@@ -789,11 +973,13 @@ Proposed guidelines for including attributes:
</div>
-<h4><a name="uc.document.detach" id="uc.document.detach">uc.document.detach</a></h4>
+<h4><a name="ucdocumentdetach" id="ucdocumentdetach">uc.document.detach</a></h4>
<div class="level4">
<p>
- Disassociate a document(s) from a part(s). All parts and documents remain in the database. Only the relationship is removed.
+
+Disassociate a document(s) from a part(s). All parts and documents remain in the database. Only the relationship is removed.
+
</p>
<ol>
<li class="level1"><div class="li"> The user selects one or more parts from the database.</div>
@@ -812,11 +998,13 @@ Proposed guidelines for including attributes:
</div>
-<h4><a name="uc.document.edit" id="uc.document.edit">uc.document.edit</a></h4>
+<h4><a name="ucdocumentedit" id="ucdocumentedit">uc.document.edit</a></h4>
<div class="level4">
<p>
- Edit the metadata associated with a document.
+
+Edit the metadata associated with a document.
+
</p>
<ol>
<li class="level1"><div class="li"> TBD</div>
@@ -825,11 +1013,13 @@ Proposed guidelines for including attributes:
</div>
-<h4><a name="uc.document.view" id="uc.document.view">uc.document.view</a></h4>
+<h4><a name="ucdocumentview" id="ucdocumentview">uc.document.view</a></h4>
<div class="level4">
<p>
- View a document.
+
+View a document.
+
</p>
<ol>
<li class="level1"><div class="li"> TBD</div>
@@ -838,11 +1028,13 @@ Proposed guidelines for including attributes:
</div>
-<h4><a name="uc.footprint.delete" id="uc.footprint.delete">uc.footprint.delete</a></h4>
+<h4><a name="ucfootprintdelete" id="ucfootprintdelete">uc.footprint.delete</a></h4>
<div class="level4">
<p>
- Delete a footprint(s) from the database. Remove all references.
+
+Delete a footprint(s) from the database. Remove all references.
+
</p>
<ol>
<li class="level1"><div class="li"> The user selects one or more footprints in the database.</div>
@@ -857,20 +1049,23 @@ Proposed guidelines for including attributes:
</div>
-<h4><a name="uc.footprint.edit" id="uc.footprint.edit">uc.footprint.edit</a></h4>
+<h4><a name="ucfootprintedit" id="ucfootprintedit">uc.footprint.edit</a></h4>
<div class="level4">
<p>
- Edit the metadata associated with a footprint.
+
+Edit the metadata associated with a footprint.
</p>
</div>
-<h4><a name="uc.footprint.import.file" id="uc.footprint.import.file">uc.footprint.import.file</a></h4>
+<h4><a name="ucfootprintimportfile" id="ucfootprintimportfile">uc.footprint.import.file</a></h4>
<div class="level4">
<p>
- Import a single footprint file into the database.
+
+Import a single footprint file into the database.
+
</p>
<ol>
<li class="level1"><div class="li"> The user selects the import footprint file action.</div>
@@ -885,11 +1080,13 @@ Proposed guidelines for including attributes:
</div>
-<h4><a name="uc.footprint.import.library" id="uc.footprint.import.library">uc.footprint.import.library</a></h4>
+<h4><a name="ucfootprintimportlibrary" id="ucfootprintimportlibrary">uc.footprint.import.library</a></h4>
<div class="level4">
<p>
- Import all footprint files from the library into the database.
+
+Import all footprint files from the library into the database.
+
</p>
<ol>
<li class="level1"><div class="li"> The user selects the import footprint library action.</div>
@@ -904,11 +1101,13 @@ Proposed guidelines for including attributes:
</div>
-<h4><a name="uc.model.add" id="uc.model.add">uc.model.add</a></h4>
+<h4><a name="ucmodeladd" id="ucmodeladd">uc.model.add</a></h4>
<div class="level4">
<p>
- Add a new model to the database.
+
+Add a new model to the database.
+
</p>
<ol>
<li class="level1"><div class="li"> The user selects the add model action.</div>
@@ -921,11 +1120,13 @@ Proposed guidelines for including attributes:
</div>
-<h4><a name="uc.model.attach" id="uc.model.attach">uc.model.attach</a></h4>
+<h4><a name="ucmodelattach" id="ucmodelattach">uc.model.attach</a></h4>
<div class="level4">
<p>
- Associate a model(s) with a part(s).
+
+Associate a model(s) with a part(s).
+
</p>
<ol>
<li class="level1"><div class="li"> The user selects one or more parts from the database.</div>
@@ -942,11 +1143,13 @@ Proposed guidelines for including attributes:
</div>
-<h4><a name="uc.model.delete" id="uc.model.delete">uc.model.delete</a></h4>
+<h4><a name="ucmodeldelete" id="ucmodeldelete">uc.model.delete</a></h4>
<div class="level4">
<p>
- Delete a model(s) from the database. Remove all references.
+
+Delete a model(s) from the database. Remove all references.
+
</p>
<ol>
<li class="level1"><div class="li"> The user selects one or more models in the database.</div>
@@ -961,11 +1164,13 @@ Proposed guidelines for including attributes:
</div>
-<h4><a name="uc.model.detach" id="uc.model.detach">uc.model.detach</a></h4>
+<h4><a name="ucmodeldetach" id="ucmodeldetach">uc.model.detach</a></h4>
<div class="level4">
<p>
- Disassociate a model(s) from a part(s). All parts and models remain in the database. Only the relationship is removed.
+
+Disassociate a model(s) from a part(s). All parts and models remain in the database. Only the relationship is removed.
+
</p>
<ol>
<li class="level1"><div class="li"> The user selects one or more parts from the database.</div>
@@ -984,11 +1189,13 @@ Proposed guidelines for including attributes:
</div>
-<h4><a name="uc.model.import.library.spice" id="uc.model.import.library.spice">uc.model.import.library.spice</a></h4>
+<h4><a name="ucmodelimportlibraryspice" id="ucmodelimportlibraryspice">uc.model.import.library.spice</a></h4>
<div class="level4">
<p>
- Import all Spice files from the library into the database.
+
+Import all Spice files from the library into the database.
+
</p>
<ol>
<li class="level1"><div class="li"> The user selects the import Spice library action.</div>
@@ -1005,20 +1212,23 @@ Proposed guidelines for including attributes:
</div>
-<h4><a name="uc.model.view" id="uc.model.view">uc.model.view</a></h4>
+<h4><a name="ucmodelview" id="ucmodelview">uc.model.view</a></h4>
<div class="level4">
<p>
- TBD
+
+TBD
</p>
</div>
-<h4><a name="uc.package.add" id="uc.package.add">uc.package.add</a></h4>
+<h4><a name="ucpackageadd" id="ucpackageadd">uc.package.add</a></h4>
<div class="level4">
<p>
- Add a new package to the database.
+
+Add a new package to the database.
+
</p>
<ol>
<li class="level1"><div class="li"> TBD</div>
@@ -1027,11 +1237,13 @@ Proposed guidelines for including attributes:
</div>
-<h4><a name="uc.package.delete" id="uc.package.delete">uc.package.delete</a></h4>
+<h4><a name="ucpackagedelete" id="ucpackagedelete">uc.package.delete</a></h4>
<div class="level4">
<p>
- Delete a package(s) from the database. Remove all references.
+
+Delete a package(s) from the database. Remove all references.
+
</p>
<ol>
<li class="level1"><div class="li"> The user selects one or more packages in the database.</div>
@@ -1046,11 +1258,13 @@ Proposed guidelines for including attributes:
</div>
-<h4><a name="uc.package.edit" id="uc.package.edit">uc.package.edit</a></h4>
+<h4><a name="ucpackageedit" id="ucpackageedit">uc.package.edit</a></h4>
<div class="level4">
<p>
- Edit the package data.
+
+Edit the package data.
+
</p>
<ol>
<li class="level1"><div class="li"> TBD</div>
@@ -1059,11 +1273,13 @@ Proposed guidelines for including attributes:
</div>
-<h4><a name="uc.part.add" id="uc.part.add">uc.part.add</a></h4>
+<h4><a name="ucpartadd" id="ucpartadd">uc.part.add</a></h4>
<div class="level4">
<p>
- Add a new part to the database.
+
+Add a new part to the database.
+
</p>
<ol>
<li class="level1"><div class="li"> TBD</div>
@@ -1072,11 +1288,13 @@ Proposed guidelines for including attributes:
</div>
-<h4><a name="uc.part.delete" id="uc.part.delete">uc.part.delete</a></h4>
+<h4><a name="ucpartdelete" id="ucpartdelete">uc.part.delete</a></h4>
<div class="level4">
<p>
- Delete a part(s) from the database. Remove all references.
+
+Delete a part(s) from the database. Remove all references.
+
</p>
<ol>
<li class="level1"><div class="li"> The user selects one or more parts in the database.</div>
@@ -1091,11 +1309,13 @@ Proposed guidelines for including attributes:
</div>
-<h4><a name="uc.part.edit" id="uc.part.edit">uc.part.edit</a></h4>
+<h4><a name="ucpartedit" id="ucpartedit">uc.part.edit</a></h4>
<div class="level4">
<p>
- Edit the part data.
+
+Edit the part data.
+
</p>
<ol>
<li class="level1"><div class="li"> TBD</div>
@@ -1104,20 +1324,23 @@ Proposed guidelines for including attributes:
</div>
-<h4><a name="uc.part.search" id="uc.part.search">uc.part.search</a></h4>
+<h4><a name="ucpartsearch" id="ucpartsearch">uc.part.search</a></h4>
<div class="level4">
<p>
- Search for a part in the database using the manufacturer part number.
+
+Search for a part in the database using the manufacturer part number.
</p>
</div>
-<h4><a name="uc.symbol.delete" id="uc.symbol.delete">uc.symbol.delete</a></h4>
+<h4><a name="ucsymboldelete" id="ucsymboldelete">uc.symbol.delete</a></h4>
<div class="level4">
<p>
- Delete a symbol(s) from the database. Remove all references.
+
+Delete a symbol(s) from the database. Remove all references.
+
</p>
<ol>
<li class="level1"><div class="li"> The user selects one or more symbols in the database.</div>
@@ -1132,11 +1355,13 @@ Proposed guidelines for including attributes:
</div>
-<h4><a name="uc.symbol.edit" id="uc.symbol.edit">uc.symbol.edit</a></h4>
+<h4><a name="ucsymboledit" id="ucsymboledit">uc.symbol.edit</a></h4>
<div class="level4">
<p>
- Edit the metadata associated with a symbol.
+
+Edit the metadata associated with a symbol.
+
</p>
<ol>
<li class="level1"><div class="li"> TBD</div>
@@ -1145,11 +1370,13 @@ Proposed guidelines for including attributes:
</div>
-<h4><a name="uc.symbol.import.file" id="uc.symbol.import.file">uc.symbol.import.file</a></h4>
+<h4><a name="ucsymbolimportfile" id="ucsymbolimportfile">uc.symbol.import.file</a></h4>
<div class="level4">
<p>
- Import a single symbol file into the database.
+
+Import a single symbol file into the database.
+
</p>
<ol>
<li class="level1"><div class="li"> The user selects the import symbol file action.</div>
@@ -1164,11 +1391,13 @@ Proposed guidelines for including attributes:
</div>
-<h4><a name="uc.symbol.import.library" id="uc.symbol.import.library">uc.symbol.import.library</a></h4>
+<h4><a name="ucsymbolimportlibrary" id="ucsymbolimportlibrary">uc.symbol.import.library</a></h4>
<div class="level4">
<p>
- Import the contents of the component library into the database.
+
+Import the contents of the component library into the database.
+
</p>
<ol>
<li class="level1"><div class="li"> The user selects the import symbol library action.</div>
@@ -1182,8 +1411,8 @@ Proposed guidelines for including attributes:
</ol>
</div>
-<!-- SECTION "Use Cases" [14196-22131] -->
-<h3><a name="ui_design" id="ui_design">UI Design</a></h3>
+<!-- EDIT164 SECTION "Use Cases" [17397-25332] -->
+<h3 class="sectionedit165"><a name="ui_design" id="ui_design">UI Design</a></h3>
<div class="level3">
</div>
@@ -1192,7 +1421,8 @@ Proposed guidelines for including attributes:
<div class="level4">
<p>
- The company view lists all the companies in the database.
+
+The company view lists all the companies in the database.
</p>
<p>
@@ -1205,7 +1435,8 @@ Proposed guidelines for including attributes:
<div class="level4">
<p>
- The device view lists all the devices stored in the database.
+
+The device view lists all the devices stored in the database.
</p>
<p>
@@ -1218,7 +1449,8 @@ Proposed guidelines for including attributes:
<div class="level4">
<p>
- The documentation view shows all the documents stored in the database.
+
+The documentation view shows all the documents stored in the database.
</p>
<p>
@@ -1231,7 +1463,8 @@ Proposed guidelines for including attributes:
<div class="level4">
<p>
- The footprint view shows all the footprints stored in the database.
+
+The footprint view shows all the footprints stored in the database.
</p>
<p>
@@ -1244,7 +1477,8 @@ Proposed guidelines for including attributes:
<div class="level4">
<p>
- The package view shows all the packages stored in the database.
+
+The package view shows all the packages stored in the database.
</p>
<p>
@@ -1257,11 +1491,20 @@ Proposed guidelines for including attributes:
<div class="level4">
<p>
- The part view shows parts stored in the database. The user selects the category from the left pane. The parts within the given category show in the middle pane. After selecting a part from the middle pane, the symbols available for that part show in the lower right pane. The upper right pane shows the symbol preview.
+
+The part view shows parts stored in the database. The user selects the category from the left pane. The parts within the given category show in the middle pane. After selecting a part from the middle pane, the symbols available for that part show in the lower right pane. The upper right pane shows the symbol preview.
+</p>
+
+<p>
+<a href="media/geda/gparts-ss-parts-4.png" class="media" target="_blank" title="geda:gparts-ss-parts-4.png"><img src="media/geda/gparts-ss-parts-4.png" class="media" title="" alt="" /></a>
</p>
<p>
-<a href="media/geda/gparts-ss-parts-2.png" class="media" target="_blank" title="geda:gparts-ss-parts-2.png"><img src="media/geda/gparts-ss-parts-2.png" class="media" title="" alt="" /></a>
+The editâ??copy command places the component on the clipboard. The component can then be pasted into gschem.
+</p>
+
+<p>
+<a href="media/geda/gparts-ss-parts-4b.png" class="media" target="_blank" title="geda:gparts-ss-parts-4b.png"><img src="media/geda/gparts-ss-parts-4b.png" class="media" title="" alt="" /></a>
</p>
</div>
@@ -1270,7 +1513,8 @@ Proposed guidelines for including attributes:
<div class="level4">
<p>
- The symbol view shows all the symbols stored in the database. The upper right pane shows the symbol preview.
+
+The symbol view shows all the symbols stored in the database. The upper right pane shows the symbol preview.
</p>
<p>
@@ -1278,12 +1522,14 @@ Proposed guidelines for including attributes:
</p>
</div>
-<!-- SECTION "UI Design" [22132-23316] -->
-<h3><a name="configuration" id="configuration">Configuration</a></h3>
+<!-- EDIT165 SECTION "UI Design" [25333-26660] -->
+<h3 class="sectionedit166"><a name="configuration" id="configuration">Configuration</a></h3>
<div class="level3">
<p>
- The parts manager reads gafâ??s Scheme configuration files using Guile-1.8. The parts manager reads the following configuration files in order. The parts manager attempts reading the file in each of the given paths in order.
+
+The parts manager reads gaf's Scheme configuration files using Guile-1.8. The parts manager reads the following configuration files in order. The parts manager attempts reading the file in each of the given paths in order.
+
</p>
<ol>
<li class="level1"><div class="li"> system-gafrc</div>
@@ -1337,84 +1583,90 @@ Proposed guidelines for including attributes:
</ol>
<p>
- The parts manager supports the following configuration items from gaf.
+
+The parts manager supports the following configuration items from gaf.
+
</p>
-<table class="inline">
- <tr>
- <th class="leftalign"> Item </th><th class="leftalign"> Parser </th><th> Description </th>
+<div class="table sectionedit167"><table class="inline">
+ <tr class="row0">
+ <th class="col0 leftalign"> Item </th><th class="col1 leftalign"> Parser </th><th class="col2"> Description </th>
</tr>
- <tr>
- <td> always-promote-attributes </td><td> libgeda </td><td class="rightalign"> </td>
+ <tr class="row1">
+ <td class="col0"> always-promote-attributes </td><td class="col1"> libgeda </td><td class="col2 leftalign"> </td>
</tr>
- <tr>
- <td class="leftalign"> attribute-promotion </td><td> libgeda </td><td class="rightalign"> </td>
+ <tr class="row2">
+ <td class="col0 leftalign"> attribute-promotion </td><td class="col1"> libgeda </td><td class="col2 leftalign"> </td>
</tr>
- <tr>
- <td class="leftalign"> bitmap-directory </td><td> libgeda </td><td class="leftalign"> Specifies the directory for bitmap images </td>
+ <tr class="row3">
+ <td class="col0 leftalign"> bitmap-directory </td><td class="col1"> libgeda </td><td class="col2 leftalign"> Specifies the directory for bitmap images </td>
</tr>
- <tr>
- <td class="leftalign"> bus-style </td><td class="leftalign"> gschem </td><td class="leftalign"> Specifies the line thickness for busses </td>
+ <tr class="row4">
+ <td class="col0 leftalign"> bus-style </td><td class="col1 leftalign"> gschem </td><td class="col2 leftalign"> Specifies the line thickness for busses </td>
</tr>
- <tr>
- <td class="leftalign"> component-library </td><td> libgeda </td><td class="leftalign"> Adds a directory to the component library </td>
+ <tr class="row5">
+ <td class="col0 leftalign"> component-library </td><td class="col1"> libgeda </td><td class="col2 leftalign"> Adds a directory to the component library </td>
</tr>
- <tr>
- <td class="leftalign"> display-color-map </td><td class="leftalign"> gschem </td><td class="leftalign"> Specifies schematic colors for display </td>
+ <tr class="row6">
+ <td class="col0 leftalign"> display-color-map </td><td class="col1 leftalign"> gschem </td><td class="col2 leftalign"> Specifies schematic colors for display </td>
</tr>
- <tr>
- <td> display-outline-color-map </td><td class="leftalign"> gschem </td><td class="rightalign"> </td>
+ <tr class="row7">
+ <td class="col0"> display-outline-color-map </td><td class="col1 leftalign"> gschem </td><td class="col2 leftalign"> </td>
</tr>
- <tr>
- <td class="leftalign"> eval-protected </td><td> libgeda </td><td class="leftalign"> For the parts manager, simply â??evalâ?? </td>
+ <tr class="row8">
+ <td class="col0 leftalign"> eval-protected </td><td class="col1"> libgeda </td><td class="col2 leftalign"> For the parts manager, simply 'eval' </td>
</tr>
- <tr>
- <td class="leftalign"> keep-invisible </td><td> libgeda </td><td class="rightalign"> </td>
+ <tr class="row9">
+ <td class="col0 leftalign"> keep-invisible </td><td class="col1"> libgeda </td><td class="col2 leftalign"> </td>
</tr>
- <tr>
- <td class="leftalign"> net-style </td><td class="leftalign"> gschem </td><td class="leftalign"> Specifies the line thickness for nets </td>
+ <tr class="row10">
+ <td class="col0 leftalign"> net-style </td><td class="col1 leftalign"> gschem </td><td class="col2 leftalign"> Specifies the line thickness for nets </td>
</tr>
- <tr>
- <td class="leftalign"> postscript-prolog </td><td> libgeda </td><td class="leftalign"> Ignored by the parts manager </td>
+ <tr class="row11">
+ <td class="col0 leftalign"> postscript-prolog </td><td class="col1"> libgeda </td><td class="col2 leftalign"> Ignored by the parts manager </td>
</tr>
- <tr>
- <td class="leftalign"> print-color-map </td><td> libgeda </td><td class="leftalign"> Specifies schematic colors for printing </td>
+ <tr class="row12">
+ <td class="col0 leftalign"> print-color-map </td><td class="col1"> libgeda </td><td class="col2 leftalign"> Specifies schematic colors for printing </td>
</tr>
- <tr>
- <td class="leftalign"> promote-invisible </td><td> libgeda </td><td class="rightalign"> </td>
+ <tr class="row13">
+ <td class="col0 leftalign"> promote-invisible </td><td class="col1"> libgeda </td><td class="col2 leftalign"> </td>
</tr>
- <tr>
- <td class="leftalign"> scheme-directory </td><td> libgeda </td><td> Specifies the directory for additional scheme files </td>
+ <tr class="row14">
+ <td class="col0 leftalign"> scheme-directory </td><td class="col1"> libgeda </td><td class="col2"> Specifies the directory for additional scheme files </td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT167 TABLE [27627-28996] -->
<p>
- The parts manager supports the following private configuration items.
+
+The parts manager supports the following private configuration items.
+
</p>
-<table class="inline">
- <tr>
- <th class="leftalign"> Item </th><th> Parser </th><th> Description </th>
+<div class="table sectionedit168"><table class="inline">
+ <tr class="row0">
+ <th class="col0 leftalign"> Item </th><th class="col1"> Parser </th><th class="col2"> Description </th>
</tr>
- <tr>
- <td class="leftalign"> database-interface </td><td> gparts </td><td class="leftalign"> Adds a database interface module </td>
+ <tr class="row1">
+ <td class="col0 leftalign"> database-interface </td><td class="col1"> gparts </td><td class="col2 leftalign"> Adds a database interface module </td>
</tr>
- <tr>
- <td class="leftalign"> document-library </td><td> gparts </td><td class="leftalign"> Adds a directory to the document library </td>
+ <tr class="row2">
+ <td class="col0 leftalign"> document-library </td><td class="col1"> gparts </td><td class="col2 leftalign"> Adds a directory to the document library </td>
</tr>
- <tr>
- <td class="leftalign"> footprint-library </td><td> gparts </td><td> Adds a directory to the footprint library </td>
+ <tr class="row3">
+ <td class="col0 leftalign"> footprint-library </td><td class="col1"> gparts </td><td class="col2"> Adds a directory to the footprint library </td>
</tr>
- <tr>
- <td class="leftalign"> spice-library </td><td> gparts </td><td class="leftalign"> Adds a directory to the spice library </td>
+ <tr class="row4">
+ <td class="col0 leftalign"> spice-library </td><td class="col1"> gparts </td><td class="col2 leftalign"> Adds a directory to the spice library </td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT168 TABLE [29069-29453] -->
</div>
<h4><a name="database-interface" id="database-interface">database-interface</a></h4>
<div class="level4">
<p>
- The parts manager uses dynamically loadable modules to support the various database engines. The parts manager uses a separate module to support each database engine.
+
+The parts manager uses dynamically loadable modules to support the various database engines. The parts manager uses a separate module to support each database engine.
+
</p>
<ul>
<li class="level1"><div class="li"> MySQL</div>
@@ -1431,7 +1683,8 @@ Proposed guidelines for including attributes:
<div class="level4">
<p>
- Adds a directory to the list of directories where documentation is stored.
+
+Adds a directory to the list of directories where documentation is stored.
</p>
</div>
@@ -1440,7 +1693,8 @@ Proposed guidelines for including attributes:
<div class="level4">
<p>
- Adds a directory to the list of directories where footprints are stored. The parts manager can import newlib footprints from these directories.
+
+Adds a directory to the list of directories where footprints are stored. The parts manager can import newlib footprints from these directories.
</p>
</div>
@@ -1449,9 +1703,10 @@ Proposed guidelines for including attributes:
<div class="level4">
<p>
- Adds a directory to the list of directories where SPICE models are stored. The parts manager can import these models from these directories.
+
+Adds a directory to the list of directories where SPICE models are stored. The parts manager can import these models from these directories.
</p>
</div>
-<!-- SECTION "Configuration" [23317-] --></body>
+<!-- EDIT166 SECTION "Configuration" [26661-] --></body>
</html>
diff --git a/docs/wiki/geda-gparts_id.html b/docs/wiki/geda-gparts_id.html
new file mode 100644
index 0000000..ec2a3de
--- /dev/null
+++ b/docs/wiki/geda-gparts_id.html
@@ -0,0 +1,66 @@
+<!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 page covers the implementation details of a parts manager for gEDA. Please submit feedback to the geda-dev or geda-user mailing lists.
+</p>
+
+<p>
+For design details, see <a href="geda-gparts_dd.html" class="wikilink1" title="geda-gparts_dd.html">gparts_dd</a>.
+</p>
+
+<h1 class="sectionedit1423"><a name="packages" id="packages">Packages</a></h1>
+<div class="level1">
+
+<p>
+The following diagram shows the package dependencies â?? cycles removed â?? within the part manager.
+</p>
+
+<p>
+<a href="media/geda/gparts_pkg_2.png" class="media" target="_blank" title="geda:gparts_pkg_2.png"><img src="media/geda/gparts_pkg_2.png" class="media" title="" alt="" /></a>
+</p>
+
+</div>
+<!-- EDIT1423 SECTION "Packages" [182-332] -->
+<h2 class="sectionedit1424"><a name="geometry_package" id="geometry_package">Geometry Package</a></h2>
+<div class="level2">
+
+<p>
+
+<a href="media/geda/gparts_pkg_geom.png" class="media" target="_blank" title="geda:gparts_pkg_geom.png"><img src="media/geda/gparts_pkg_geom.png" class="media" title="" alt="" /></a>
+</p>
+
+</div>
+<!-- EDIT1424 SECTION "Geometry Package" [333-393] -->
+<h2 class="sectionedit1425"><a name="schematic_package" id="schematic_package">Schematic Package</a></h2>
+<div class="level2">
+
+<p>
+
+<a href="media/geda/gparts_pkg_sch.png" class="media" target="_blank" title="geda:gparts_pkg_sch.png"><img src="media/geda/gparts_pkg_sch.png" class="media" title="" alt="" /></a>
+</p>
+
+</div>
+<!-- EDIT1425 SECTION "Schematic Package" [394-454] -->
+<h2 class="sectionedit1426"><a name="schematic_gui_package" id="schematic_gui_package">Schematic GUI Package</a></h2>
+<div class="level2">
+
+</div>
+<!-- EDIT1426 SECTION "Schematic GUI Package" [455-489] -->
+<h2 class="sectionedit1427"><a name="scheme_configuration_package" id="scheme_configuration_package">Scheme Configuration Package</a></h2>
+<div class="level2">
+
+</div>
+<!-- EDIT1427 SECTION "Scheme Configuration Package" [490-] --></body>
+</html>
diff --git a/docs/wiki/geda-gparts_ii.html b/docs/wiki/geda-gparts_ii.html
new file mode 100644
index 0000000..3e850a4
--- /dev/null
+++ b/docs/wiki/geda-gparts_ii.html
@@ -0,0 +1,351 @@
+<!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 class="sectionedit1428"><a name="part_manager_installation" id="part_manager_installation">Part Manager Installation</a></h1>
+<div class="level1">
+
+<p>
+
+The parts manager is in development. All required functionality is not implemented.
+</p>
+
+</div>
+<!-- EDIT1428 SECTION "Part Manager Installation" [1-127] -->
+<h2 class="sectionedit1429"><a name="requirements" id="requirements">Requirements</a></h2>
+<div class="level2">
+
+<p>
+
+Building and using the part manager requires the following packages:
+
+</p>
+<div class="table sectionedit1430"><table class="inline">
+ <tr class="row0">
+ <th class="col0 leftalign"> PackageName </th><th class="col1 leftalign"> Description </th><th class="col2 leftalign"> Use </th>
+ </tr>
+ <tr class="row1">
+ <td class="col0 leftalign"> autoconf </td><td class="col1 leftalign"> automatic configure script builder </td><td class="col2"> Required </td>
+ </tr>
+ <tr class="row2">
+ <td class="col0 leftalign"> automake </td><td class="col1"> A tool for generating GNU Standards-compliant Makefiles </td><td class="col2"> Required </td>
+ </tr>
+ <tr class="row3">
+ <td class="col0 leftalign"> gcc </td><td class="col1 leftalign"> The GNU C compiler </td><td class="col2"> Required </td>
+ </tr>
+ <tr class="row4">
+ <td class="col0 leftalign"> geda </td><td class="col1 leftalign"> <acronym title="GNU General Public License">GPL</acronym> EDA â?? Electronics design software (metapackage) </td><td class="col2"> Required </td>
+ </tr>
+ <tr class="row5">
+ <td class="col0 leftalign"> git-core </td><td class="col1 leftalign"> fast, scalable, distributed revision control system </td><td class="col2"> Required </td>
+ </tr>
+ <tr class="row6">
+ <td class="col0 leftalign"> guile-1.8 </td><td class="col1 leftalign"> The GNU extension language and Scheme interpreter </td><td class="col2"> Required </td>
+ </tr>
+ <tr class="row7">
+ <td class="col0"> guile-1.8-dev </td><td class="col1 leftalign"> Development files for Guile 1.8 </td><td class="col2"> Required </td>
+ </tr>
+ <tr class="row8">
+ <td class="col0"> libgtk2.0-dev </td><td class="col1 leftalign"> Development files for the GTK+ library </td><td class="col2"> Required </td>
+ </tr>
+ <tr class="row9">
+ <td class="col0 leftalign"> libtool </td><td class="col1 leftalign"> Generic library support script </td><td class="col2"> Required </td>
+ </tr>
+ <tr class="row10">
+ <td class="col0 leftalign"> pkg-config </td><td class="col1 leftalign"> Manage compile and link flags for libraries </td><td class="col2"> Required </td>
+ </tr>
+ <tr class="row11">
+ <td class="col0 leftalign"> xsltproc </td><td class="col1 leftalign"> <acronym title="Extensible Stylesheet Language Transformations">XSLT</acronym> command line processor </td><td class="col2"> Required </td>
+ </tr>
+</table></div>
+<!-- EDIT1430 TABLE [224-1267] -->
+<p>
+
+Additionally, GParts requires a database for the back-end. Currently, GParts
+can use either MySQL, PostgreSQL, or SQLite.
+</p>
+
+</div>
+<!-- EDIT1429 SECTION "Requirements" [128-1392] -->
+<h3 class="sectionedit1431"><a name="mysql" id="mysql">MySQL</a></h3>
+<div class="level3">
+
+<p>
+In order to use MySQL, the packages listed below must be installed. The
+mysql-server package may not be required if configured to use a remote server.
+
+</p>
+<div class="table sectionedit1432"><table class="inline">
+ <tr class="row0">
+ <th class="col0 leftalign"> PackageName </th><th class="col1 leftalign"> Description </th><th class="col2 leftalign"> Use </th>
+ </tr>
+ <tr class="row1">
+ <td class="col0"> libmysqlclient-dev </td><td class="col1"> MySQL database development files </td><td class="col2"> Required </td>
+ </tr>
+ <tr class="row2">
+ <td class="col0 leftalign"> mysql-client </td><td class="col1 leftalign"> MySQL database client </td><td class="col2"> Required </td>
+ </tr>
+ <tr class="row3">
+ <td class="col0 leftalign"> mysql-server </td><td class="col1 leftalign"> MySQL database server </td><td class="col2"> Required </td>
+ </tr>
+</table></div>
+<!-- EDIT1432 TABLE [1563-1838] -->
+</div>
+<!-- EDIT1431 SECTION "MySQL" [1393-1839] -->
+<h3 class="sectionedit1433"><a name="postgresql" id="postgresql">PostgreSQL</a></h3>
+<div class="level3">
+
+<p>
+
+In order to use PostgreSQL, the following packages must be installed:
+(TODO: PostgreSQL not supported yet.)
+
+</p>
+<div class="table sectionedit1434"><table class="inline">
+ <tr class="row0">
+ <th class="col0"> PackageName </th><th class="col1 leftalign"> Description </th><th class="col2 leftalign"> Use </th>
+ </tr>
+ <tr class="row1">
+ <td class="col0 leftalign"> libpq-dev </td><td class="col1"> Header files for PostgreSQL library </td><td class="col2"> Required </td>
+ </tr>
+ <tr class="row2">
+ <td class="col0 leftalign"> postgresql </td><td class="col1 leftalign"> Object-relational <acronym title="Structured Query Language">SQL</acronym> database </td><td class="col2"> Required </td>
+ </tr>
+</table></div>
+<!-- EDIT1434 TABLE [1971-2165] -->
+</div>
+<!-- EDIT1433 SECTION "PostgreSQL" [1840-2166] -->
+<h3 class="sectionedit1435"><a name="sqlite" id="sqlite">SQLite</a></h3>
+<div class="level3">
+
+<p>
+
+In order to use SQLite, the following packages must be installed:
+
+</p>
+<div class="table sectionedit1436"><table class="inline">
+ <tr class="row0">
+ <th class="col0 leftalign"> PackageName </th><th class="col1 leftalign"> Description </th><th class="col2 leftalign"> Use </th>
+ </tr>
+ <tr class="row1">
+ <td class="col0 leftalign"> libsqlite3-0 </td><td class="col1 leftalign"> SQLite 3 shared library </td><td class="col2"> Required </td>
+ </tr>
+ <tr class="row2">
+ <td class="col0"> libsqlite3-0-dbg </td><td class="col1 leftalign"> SQLite 3 debugging symbols </td><td class="col2"> Optional </td>
+ </tr>
+ <tr class="row3">
+ <td class="col0 leftalign"> libsqlite3-dev </td><td class="col1 leftalign"> SQLite 3 development files </td><td class="col2"> Required </td>
+ </tr>
+ <tr class="row4">
+ <td class="col0 leftalign"> sqlite3 </td><td class="col1"> A command line interface for SQLite 3 </td><td class="col2"> Required </td>
+ </tr>
+ <tr class="row5">
+ <td class="col0 leftalign"> sqlite3-doc </td><td class="col1 leftalign"> SQLite 3 documentation </td><td class="col2"> Optional </td>
+ </tr>
+</table></div>
+<!-- EDIT1436 TABLE [2252-2680] -->
+<p>
+
+Of course, installing all packages before building allows the application to
+use either database for the back-end.
+</p>
+
+</div>
+<!-- EDIT1435 SECTION "SQLite" [2167-2797] -->
+<h2 class="sectionedit1437"><a name="building_gparts_from_source" id="building_gparts_from_source">Building GParts from Source</a></h2>
+<div class="level2">
+
+<p>
+
+If needed, obtain the source from the source repository.
+</p>
+
+<p>
+<pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">$ git clone git:<em>git.gpleda.org/gparts.git
+Initialized empty Git repository in /home/username/Projects/gparts/.git/
+remote: Counting objects: 930, done.
+remote: Compressing objects: 100% (712/712), done.
+remote: Total 930 (delta 735), reused 269 (delta 207)
+Receiving objects: 100% (930/930), 745.34 KiB | 283 KiB/s, done.
+Resolving deltas: 100% (735/735), done.
+$ cd gparts
+$ </xterm>
+
+In the top directory of the source package, execute the following commands.
+Support for PostgreSQL is incomplete, so use the configure option.
+
+<pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">$ ./autogen.sh
+$ ./configure --without-postgresql
+$ make</font></pre>
+
+The install requires root privileges.
+
+<pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">$ sudo make install</font></pre>
+
+Finally, test the executable.
+
+<pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">$ gparts</font></pre>
+
+To ensure dynamically loaded modules for database support work, select
+Databaseâ??Connectâ?¦ from the part manager menu. The combo box Database
+Type should so options for the various databases supported.
+
+<a href="media/geda/gparts-ss-connect-types.png" class="media" target="_blank" title="geda:gparts-ss-connect-types.png"><img src="media/geda/gparts-ss-connect-types.png" class="media" title="" alt="" /></a>
+
+If no database modules appear in the combo box, it is likely the parts manager
+could not find the rc files. The parts manager needs to know the location of
+system-gafrc file. The parts manager will search for this file, but sometimes
+cannot locate it. Providing the following environment variable provides better
+results. For distributions using Debian packages, the system-gafrc file can be
+located with dpkg.
+
+<pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">$ dpkg -S system-gafrc
+libgeda-common: /etc/gEDA/system-gafrc
+
+$ GEDADATARC=/etc/gEDA
+$ export GEDADATARC</font></pre>
+
+===== Database Creation =====
+
+
+==== MySQL ====
+
+Install MySQL.
+
+ * Tested under 5.0.51a-3ubuntu5.1.
+
+To create the database, enter MySQL command line mode as root and enter the <acronym title="Structured Query Language">SQL</acronym>
+commands below. Placing the password in the command line could leave the
+password in the command line history. Using only the -p option will cause
+mysql to prompt for the password and avoid this situation. A different
+database name, other than gparts, can be specified by the user. Using
+different names, the user can create multiple GPart databases. Additionally,
+user accounts may need to be created.
+
+<pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">$ mysql -u root -p</font></pre>
+
+<pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">mysql> create database GParts;
+mysql> use GParts;
+mysql> grant all privileges on *.* to 'user'@'localhost'
+ identified by 'password';</font></pre>
+
+After creating the database, the base tables and part-specific tables must be
+created. All the <acronym title="Structured Query Language">SQL</acronym> commands to perform these operations are included in the
+distributed files. Enter the following commands at the MySQL command line.
+
+<pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">mysql> source sql/mysql/create-basic.sql
+mysql> source sql/mysql/create-categories.sql
+mysql> source sql/mysql/create-discretes.sql
+mysql> source sql/mysql/create-passives.sql</font></pre>
+
+Begin loading the database, starting with package data. The package data must
+be loaded before any parts.
+
+<pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">mysql> source data/packages.sql</font></pre>
+
+The package includes a tool to parse the symbol libraries and generate an
+<acronym title="Structured Query Language">SQL</acronym> file for import into the database. Run the tool at the shell prompt, then
+import the file from an MySQL prompt. The tool requires the root gEDA
+directory as the only parameter. Your gEDA root directory may be different than
+below. The symbol data must be loaded before any parts.
+
+<pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">$ tools/symbols.py /usr/share/gEDA >tmp/symbols.sql</font></pre>
+
+<pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">mysql> source tmp/symbols.sql</font></pre>
+
+The package includes a script to generate some sample part data. Similar to
+the symbol tool, run the script at the shell prompt, then import the data at
+the MySQL prompt.
+
+<pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">$ data/parts-bourns.py >tmp/parts-bourns.sql</font></pre>
+
+<pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">mysql> source tmp/parts-bourns.sql</font></pre>
+
+
+==== PostgreSQL ====
+
+TODO: Finish implementation
+
+==== SQLite ====
+
+The source package contains a sample database in the location below. This
+database can be opened from directly within the parts manager.
+
+ * gparts/sql/sqlite/sample.db
+
+If required, use the following command line to create a new database or recreate
+the sample database. In this example, the present working directory must be
+gparts/sql/sqlite.
+
+<pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">$ sqlite3 sample.db
+SQLite version 3.6.22
+Enter ".help" for instructions
+Enter SQL statements terminated with a ";"
+sqlite></font></pre>
+
+After creating the database, read base and part specific tables into the
+database.
+
+<pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">sqlite> .read create-basic.sql
+sqlite> .read create-categories.sql
+sqlite> .read create-discretes.sql
+sqlite> .read create-passives.sql</font></pre>
+
+Read sample symbols into the database.
+
+<pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">sqlite> .read symbols.sql</font></pre>
+
+Exit the command line interface.
+
+<pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">sqlite> .exit</font></pre>
+
+Read sample companies and packages into the database. The source distribution stores packages in <acronym title="Extensible Markup Language">XML</acronym>. The distribution contains an <acronym title="Extensible Stylesheet Language Transformations">XSLT</acronym> stylesheet to convert <acronym title="Extensible Markup Language">XML</acronym> into <acronym title="Structured Query Language">SQL</acronym> for importing into SQLite. Use the following command line to perform this operation.
+
+<pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">$ xsltproc convert.xml ../../data/companies.xml | sqlite3 sample.db
+$ xsltproc convert.xml ../../data/packages.xml | sqlite3 sample.db</font></pre>
+
+Read sample parts into the database.
+
+<pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">$ ../../data/parts-bourns.py >../../tmp/parts-bourns.xml
+$ xsltproc convert.xml ../../tmp/parts-bourns.xml | sqlite3 sample.db</font></pre>
+
+For other sample parts, the data is not generated with a script.
+
+<pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">$ xsltproc convert.xml ../../tmp/rhom-discretes.xml | sqlite3 sample.db</font></pre>
+
+
+</p>
+
+</div>
+<!-- EDIT1437 SECTION "Building GParts from Source" [2798-] --></body>
+</html>
diff --git a/docs/wiki/geda-gparts_tc.html b/docs/wiki/geda-gparts_tc.html
new file mode 100644
index 0000000..244c3e4
--- /dev/null
+++ b/docs/wiki/geda-gparts_tc.html
@@ -0,0 +1,34 @@
+<!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 class="sectionedit1438"><a name="parts_manager" id="parts_manager">Parts Manager</a></h1>
+<div class="level1">
+<ul>
+<li class="level1"><div class="li"> <a href="geda-gparts_dd.html" class="wikilink1" title="geda-gparts_dd.html">Design Document</a> : The design and architecture of the parts manager.</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-gparts_id.html" class="wikilink1" title="geda-gparts_id.html">Implementation Details</a> : Implementation data for developers.</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> <a href="geda-gparts_ii.html" class="wikilink1" title="geda-gparts_ii.html">Installation Instructions</a> : Installing the parts manager from source.</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> <a href="geda-gparts_ug.html" class="wikilink1" title="geda-gparts_ug.html">User Guide</a> : Using the part manager application.</div>
+</li>
+</ul>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-gparts_ug.html b/docs/wiki/geda-gparts_ug.html
new file mode 100644
index 0000000..22bf695
--- /dev/null
+++ b/docs/wiki/geda-gparts_ug.html
@@ -0,0 +1,107 @@
+<!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 class="sectionedit1439"><a name="part_manager_user_guide" id="part_manager_user_guide">Part Manager User Guide</a></h1>
+<div class="level1">
+
+</div>
+<!-- EDIT1439 SECTION "Part Manager User Guide" [1-39] -->
+<h2 class="sectionedit1440"><a name="bulk_import" id="bulk_import">Bulk Import</a></h2>
+<div class="level2">
+
+<p>
+Currently, the part manager only provides a command line interface for bulk import of data. <acronym title="Extensible Stylesheet Language Transformations">XSLT</acronym> converts <acronym title="Extensible Markup Language">XML</acronym> data into <acronym title="Structured Query Language">SQL</acronym> using a stylesheet. Then, the <acronym title="Structured Query Language">SQL</acronym> can be read by a command line interface for the database. The following diagram shows the dataflow for a bulk import:
+</p>
+
+<p>
+<a href="media/geda/gparts-bulk-import.png" class="media" target="_blank" title="geda:gparts-bulk-import.png"><img src="media/geda/gparts-bulk-import.png" class="media" title="Bulk Import Dataflow" alt="Bulk Import Dataflow" /></a>
+</p>
+
+<p>
+The import can be accomplished with the following command line when in the gparts/sql/sqlite directory:
+</p>
+
+<p>
+<pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">$ xsltproc convert.xml ../../data/companies.xml | sqlite3 sample.db</font></pre>
+</p>
+
+<p>
+See the <acronym title="Extensible Markup Language">XML</acronym> files in the gparts/data directory for examples. Any combination of company, package, and part elements can be used within the data element.
+</p>
+
+<p>
+Use the following as an example for specifying a company.
+</p>
+<pre class="file"> <company>
+ <company-name>Altera</company-name>
+ <website>http://www.altera.com</website>
+ </company></pre>
+
+<p>
+Use the following as an example for specifying a package.
+
+</p>
+<pre class="file"> <package>
+ <package-name>0201(0603)</package-name>
+ <technology>SMT</technology>
+ </package></pre>
+
+<p>
+Use the following as an example for specifying a resistor. The resistor, as any part, can have multiple document elements associated with it. The category specifies the type of document, such as datasheet, user manual, errata, etcâ?¦
+</p>
+<pre class="file"> <resistor>
+ <company-name>Bourns</company-name>
+ <part-number>CR0603-FX-10R0ELF</part-number>
+ <package-name>0603(1608)</package-name>
+ <device-name>resistor</device-name>
+ <resistance>10.000000</resistance>
+ <tolerance>0.010000</tolerance>
+ <document category="Datasheet">http://www.bourns.com/data/global/pdfs/CHPREZTR.pdf</document>
+ </resistor></pre>
+
+</div>
+<!-- EDIT1440 SECTION "Bulk Import" [40-1774] -->
+<h2 class="sectionedit1441"><a name="part_attributes" id="part_attributes">Part Attributes</a></h2>
+<div class="level2">
+
+<p>
+The part manager places database fields into component attributes using macros. The macros use the form $(column_name). Unfortunately, this mechanism requires modification of symbols in the library for use with the part manager. The part manager performs the operation in the following steps:
+
+</p>
+<ol>
+<li class="level1"><div class="li"> loads the symbol drawing</div>
+</li>
+<li class="level1"><div class="li"> instantiates a component from the symbol drawing</div>
+</li>
+<li class="level1"><div class="li"> places inherited attributes in the component</div>
+</li>
+<li class="level1"><div class="li"> performs macro expansion on inherited attributes</div>
+</li>
+</ol>
+
+<p>
+
+Currently, macros can only be used in attributes that get promoted. The logic for attribute promotion must match between gschem and the part manager.
+</p>
+
+<p>
+The following gschem file snippet shows the macro used place the field from the database column 'Resistance' into the 'VALUE' attribute.
+</p>
+<pre class="file">T 195 200 8 10 1 1 0 0 1
+VALUE=$(Resistance)</pre>
+
+</div>
+<!-- EDIT1441 SECTION "Part Attributes" [1775-] --></body>
+</html>
diff --git a/docs/wiki/geda-grcsan.html b/docs/wiki/geda-grcsan.html
index 5be5687..aa33587 100644
--- a/docs/wiki/geda-grcsan.html
+++ b/docs/wiki/geda-grcsan.html
@@ -11,40 +11,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>
+<h1 class="sectionedit257"><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>
@@ -60,13 +28,14 @@ December 3rd, 2003
</p>
</div>
-<!-- SECTION "gEDA/gaf RF Cascade Symbols and Netlister" [1-173] -->
-<h2><a name="overview" id="overview">Overview</a></h2>
+<!-- EDIT257 SECTION "gEDA/gaf RF Cascade Symbols and Netlister" [1-173] -->
+<h2 class="sectionedit258"><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:
+
+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>
@@ -78,8 +47,8 @@ This document describes the symbol library and gnetlist backend which support dr
</ol>
</div>
-<!-- SECTION "Overview" [174-630] -->
-<h2><a name="requirements" id="requirements">Requirements</a></h2>
+<!-- EDIT258 SECTION "Overview" [174-630] -->
+<h2 class="sectionedit259"><a name="requirements" id="requirements">Requirements</a></h2>
<div class="level2">
<p>
@@ -93,27 +62,30 @@ You will need the following programs to be installed:
</ul>
</div>
-<!-- SECTION "Requirements" [631-1103] -->
-<h2><a name="creating_schematics" id="creating_schematics">Creating Schematics</a></h2>
+<!-- EDIT259 SECTION "Requirements" [631-1103] -->
+<h2 class="sectionedit260"><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.
+
+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>
+<!-- EDIT260 SECTION "Creating Schematics" [1104-1748] -->
+<h2 class="sectionedit261"><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:
+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:
+For the example file contained in this archive, you can run:
+
</p>
<pre class="code">gnetlist -g cascade -o example.cas example.sch</pre>
@@ -122,12 +94,13 @@ 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>
+<!-- EDIT261 SECTION "Extracting the Cascade Input File" [1749-2078] -->
+<h2 class="sectionedit262"><a name="running_cascade" id="running_cascade">Running Cascade</a></h2>
<div class="level2">
<p>
-Cascade is exceptionally simple to run. Just run:
+Cascade is exceptionally simple to run. Just run:
+
</p>
<pre class="code">cascade example.cas > example.out</pre>
@@ -136,8 +109,8 @@ to run the analysis on the system contained in the file <strong><code>example.ca
</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>
+<!-- EDIT262 SECTION "Running Cascade" [2079-2393] -->
+<h2 class="sectionedit263"><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>
@@ -145,12 +118,13 @@ Please note that all instances must have the <strong><code>refdes=</code></stron
</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>
+<!-- EDIT263 SECTION "Appendix A -- Symbols in the Library" [2394-2519] -->
+<h3 class="sectionedit264"><a name="sources_cascade-source" id="sources_cascade-source">Sources (cascade-source)</a></h3>
<div class="level3">
<p>
-Source. Attributes:
+Source.
+Attributes:
</p>
<ul>
<li class="level1"><div class="li"> C=Carrier level in dBm. Optional.</div>
@@ -164,12 +138,13 @@ Source. Attributes:
</ul>
</div>
-<!-- SECTION "Sources (cascade-source)" [2520-2798] -->
-<h3><a name="defaults_cascade-default" id="defaults_cascade-default">Defaults (cascade-default)</a></h3>
+<!-- EDIT264 SECTION "Sources (cascade-source)" [2520-2798] -->
+<h3 class="sectionedit265"><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:
+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>
@@ -181,34 +156,36 @@ This symbol sets the default impedance levels as well as the correlation coeffci
</ul>
</div>
-<!-- SECTION "Defaults (cascade-default)" [2799-3458] -->
-<h3><a name="elements" id="elements">Elements</a></h3>
+<!-- EDIT265 SECTION "Defaults (cascade-default)" [2799-3458] -->
+<h3 class="sectionedit266"><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:
+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>
+<div class="table sectionedit267"><table class="inline">
+ <tr class="row0">
+ <td class="col0">cascade-amp</td><td class="col1">Amplifier</td>
</tr>
- <tr>
- <td>cascade-filter</td><td>Filter</td>
+ <tr class="row1">
+ <td class="col0">cascade-filter</td><td class="col1">Filter</td>
</tr>
- <tr>
- <td>cascade-mixer</td><td>Mixer</td>
+ <tr class="row2">
+ <td class="col0">cascade-mixer</td><td class="col1">Mixer</td>
</tr>
- <tr>
- <td>cascade-transformer</td><td>Transformer</td>
+ <tr class="row3">
+ <td class="col0">cascade-transformer</td><td class="col1">Transformer</td>
</tr>
- <tr>
- <td colspan="2"> </td>
+ <tr class="row4">
+ <td class="col0" colspan="2"> </td>
</tr>
- <tr>
- <td colspan="2"> Table 1: Element Types </td>
+ <tr class="row5">
+ <td class="col0" colspan="2"> Table 1: Element Types </td>
</tr>
-</table>
-<ul>
+</table></div>
+<!-- EDIT267 TABLE [3852-3988] --><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>
@@ -232,8 +209,8 @@ Cascade characterizes each block in a system by its gain and optionally noise fi
</ul>
</div>
-<!-- SECTION "Elements" [3459-4416] -->
-<h2><a name="example" id="example">Example</a></h2>
+<!-- EDIT266 SECTION "Elements" [3459-4416] -->
+<h2 class="sectionedit268"><a name="example" id="example">Example</a></h2>
<div class="level2">
<p>
@@ -241,53 +218,57 @@ This appendix provides a simple example of the entire process of generating a sc
</p>
</div>
-<!-- SECTION "Example" [4417-4605] -->
-<h3><a name="example_schematics" id="example_schematics">Example Schematics</a></h3>
+<!-- EDIT268 SECTION "Example" [4417-4605] -->
+<h3 class="sectionedit269"><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.
+
+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>
+<div class="table sectionedit270"><table class="inline">
+ <tr class="row0">
+ <td class="col0"> <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 class="row1">
+ <td class="col0"> <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>
-
+</table></div>
+<!-- EDIT270 TABLE [4755-4828] -->
</div>
-<!-- SECTION "Example Schematics" [4606-4829] -->
-<h3><a name="netlist_the_design" id="netlist_the_design">Netlist the Design</a></h3>
+<!-- EDIT269 SECTION "Example Schematics" [4606-4829] -->
+<h3 class="sectionedit271"><a name="netlist_the_design" id="netlist_the_design">Netlist the Design</a></h3>
<div class="level3">
<p>
-To netlist the design, run:
+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>
+<!-- EDIT271 SECTION "Netlist the Design" [4830-4944] -->
+<h3 class="sectionedit272"><a name="run_the_analysis" id="run_the_analysis">Run the Analysis</a></h3>
<div class="level3">
<p>
-Run the analysis with:
+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>
+<!-- EDIT272 SECTION "Run the Analysis" [4945-5028] -->
+<h2 class="sectionedit273"><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>
+<div class="table sectionedit274"><table class="inline">
+ <tr class="row0">
+ <td class="col0">December 3rd, 2003</td><td class="col1">Created cascade.tex</td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT274 TABLE [5068-5108] -->
</div>
-<!-- SECTION "Document Revision History" [5029-] --></body>
+<!-- EDIT273 SECTION "Document Revision History" [5029-] --></body>
</html>
diff --git a/docs/wiki/geda-grenum_mp.html b/docs/wiki/geda-grenum_mp.html
index 2f63000..6efa6a8 100644
--- a/docs/wiki/geda-grenum_mp.html
+++ b/docs/wiki/geda-grenum_mp.html
@@ -12,9 +12,7 @@
<body>
-
-
-<h1><a name="grenum_man-page" id="grenum_man-page">grenum man-page</a></h1>
+<h1 class="sectionedit186"><a name="grenum_man-page" id="grenum_man-page">grenum man-page</a></h1>
<div class="level1">
<pre class="code">grenum(1) grenum(1)
@@ -68,8 +66,7 @@ SEE ALSO
- grenum(1)
-</pre>
+ grenum(1)</pre>
</div>
</body>
diff --git a/docs/wiki/geda-gsch2pcb_readme.html b/docs/wiki/geda-gsch2pcb_readme.html
index 6d22cf8..a30ad5a 100644
--- a/docs/wiki/geda-gsch2pcb_readme.html
+++ b/docs/wiki/geda-gsch2pcb_readme.html
@@ -12,9 +12,7 @@
<body>
-
-
-<h1><a name="gsch2pcb_gschem_to_pcb_readme" id="gsch2pcb_gschem_to_pcb_readme">gsch2pcb (gschem to PCB) README</a></h1>
+<h1 class="sectionedit693"><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
--------
@@ -123,8 +121,7 @@ Caveats
-Bill Wilson billw@xxxxxx
-</pre>
+Bill Wilson billw@xxxxxx</pre>
</div>
</body>
diff --git a/docs/wiki/geda-gsch2pcb_tutorial.html b/docs/wiki/geda-gsch2pcb_tutorial.html
index c03a9a4..8ae86d7 100644
--- a/docs/wiki/geda-gsch2pcb_tutorial.html
+++ b/docs/wiki/geda-gsch2pcb_tutorial.html
@@ -11,45 +11,28 @@
</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>
+<h1 class="sectionedit739"><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.
+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.
+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>
@@ -57,33 +40,73 @@ See the <a href="geda-gsch2pcb_tutorial_releasenotes.html" class="wikilink1" tit
</p>
</div>
-<!-- SECTION "gschem -> gsch2pcb -> PCB" [1-947] -->
-<h2><a name="terminology" id="terminology">Terminology</a></h2>
+<!-- EDIT739 SECTION "gschem -> gsch2pcb -> PCB" [1-947] -->
+<h2 class="sectionedit740"><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.
+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.
+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.
+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.
+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-3252] -->
-<h2><a name="setup" id="setup">Setup</a></h2>
+<!-- EDIT740 SECTION "Terminology" [948-3253] -->
+<h2 class="sectionedit741"><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.
+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>
@@ -99,7 +122,9 @@ 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.
+
+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>
@@ -109,10 +134,10 @@ gaf/myproject2/ design project.
(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:
+or, in each project directory (like myproject1 and myproject2) 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>
+<pre class="code">(component-library "../gschem-sym")
+(component-library "../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>
@@ -143,32 +168,41 @@ or, in each project directory there could be a <strong>gafrc</strong> file with
</ul>
<p>
- This is all the setup you need beyond the initial install of the gschem, gsch2pcb, and PCB packages.
+
+This is all the setup you need beyond the initial install of the gschem, gsch2pcb, and PCB packages.
</p>
</div>
-<!-- SECTION "Setup" [3253-7827] -->
-<h2><a name="simple_example" id="simple_example">Simple Example</a></h2>
+<!-- EDIT741 SECTION "Setup" [3254-7853] -->
+<h2 class="sectionedit742"><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.
+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:
+
+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>
+output-name board</pre>
</div>
-<!-- SECTION "Simple Example" [7828-8303] -->
-<h3><a name="create_schematicone.sch" id="create_schematicone.sch">Create schematic: one.sch</a></h3>
+<!-- EDIT742 SECTION "Simple Example" [7854-8329] -->
+<h3 class="sectionedit743"><a name="create_schematiconesch" id="create_schematiconesch">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>.
+
+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>
@@ -196,12 +230,13 @@ output-name board
</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.
+
+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" [8304-9705] -->
-<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>
+<!-- EDIT743 SECTION "Create schematic: one.sch" [8330-9731] -->
+<h3 class="sectionedit744"><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>
@@ -212,28 +247,40 @@ output-name board
</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 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/>
+
+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.
+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." [9706-11656] -->
-<h3><a name="create_schematictwo.sch" id="create_schematictwo.sch">Create schematic: two.sch</a></h3>
+<!-- EDIT744 SECTION "Edit the attributes of the components on the schematic." [9732-11682] -->
+<h3 class="sectionedit745"><a name="create_schematictwosch" id="create_schematictwosch">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>
+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>
@@ -262,57 +309,119 @@ This will be really trivial and stupid since weâ??re doing it only to demonstrat
</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 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.
+
+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:
+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>
+<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.
+
+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" [11657-15285] -->
-<h3><a name="generate_pcb_files_from_schematics" id="generate_pcb_files_from_schematics">Generate PCB Files from Schematics</a></h3>
+<!-- EDIT745 SECTION "Create schematic: two.sch" [11683-15311] -->
+<h3 class="sectionedit746"><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.
+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:
+
+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>
+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>.
+
+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)
+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.
+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" [15286-17524] -->
-<h3><a name="layout_pcb_files" id="layout_pcb_files">Layout PCB Files</a></h3>
+<!-- EDIT746 SECTION "Generate PCB Files from Schematics" [15312-17550] -->
+<h3 class="sectionedit747"><a name="layout_pcb_files" id="layout_pcb_files">Layout PCB Files</a></h3>
<div class="level3">
</div>
@@ -321,15 +430,33 @@ If you get output from gsch2pcb like: <em>2 unknown elements added to board.pcb.
<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.
+<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.
+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>.
+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>
@@ -338,11 +465,15 @@ You should also set the default line and via sizes you want for the Signal, Powe
<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.
+<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.
+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>
@@ -354,14 +485,15 @@ Or, you can let PCB spread out the elements with <strong>Select→Disperse al
<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 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 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>.
+
+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>
@@ -374,12 +506,27 @@ Or, you can let PCB spread out the elements with <strong>Select→Disperse al
</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.
+
+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 <strong>Select→Select all
-objects</strong>) 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.
+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 <strong>Selectâ??Select all
+objects</strong>) 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>
@@ -388,29 +535,82 @@ objects</strong>) then do <strong>Select→Auto place selected elements</stro
<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.
+<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.
+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>.
+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.
+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:
+
+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>
+<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.
+
+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>
@@ -419,16 +619,33 @@ You will want more information on using PCB and there is a set of html docs in t
<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.
+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" [17525-25956] -->
-<h2><a name="modifying_schematics" id="modifying_schematics">Modifying Schematics</a></h2>
+<!-- EDIT747 SECTION "Layout PCB Files" [17551-25982] -->
+<h2 class="sectionedit748"><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:
+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>
@@ -436,7 +653,13 @@ The process of transfering schematic modifications to your PCB layout is made ve
</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/>
+ 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>
@@ -444,7 +667,7 @@ The process of transfering schematic modifications to your PCB layout is made ve
</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 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>
@@ -453,39 +676,88 @@ The process of transfering schematic modifications to your PCB layout is made ve
</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.
+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>.
+
+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:
+
+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>
+<pre class="code">elements-dir /usr/lib/newlib</pre>
<p>
- If gsch2pcb does find it, you will get:
+
+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>
+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>.
+
+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" [25957-29762] -->
-<h2><a name="custom_gschem_symbols" id="custom_gschem_symbols">Custom gschem Symbols</a></h2>
+<!-- EDIT748 SECTION "Modifying Schematics" [25983-29788] -->
+<h2 class="sectionedit749"><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>):
+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>
@@ -499,8 +771,7 @@ A common way to generate a custom symbol is to start with an existing symbol and
<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>
+gschem opamp-dual.sym</pre>
<ul>
<li class="level1"><div class="li"> Hit keys <strong>en</strong> to make attributes visible.</div>
</li>
@@ -531,7 +802,7 @@ gschem opamp-dual.sym
<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>
+<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>
@@ -543,11 +814,17 @@ gschem opamp-dual.sym
</ul>
<p>
- Clean up by moving these new attributes as shown.
+
+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.
+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>
@@ -556,7 +833,22 @@ Change the footprint default if you wish. When all the edits are done, itâ??s ve
<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:
+<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]
@@ -567,28 +859,52 @@ 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>
+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.
+
+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.
+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" [29763-34016] -->
-<h2><a name="custom_file_elements" id="custom_file_elements">Custom file elements</a></h2>
+<!-- EDIT749 SECTION "Custom gschem Symbols" [29789-34042] -->
+<h2 class="sectionedit750"><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.
+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>
+
+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>
@@ -600,7 +916,8 @@ You can create custom <strong>file elements</strong> in the middle of running PC
</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>
+
+<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>
@@ -609,50 +926,128 @@ You can create custom <strong>file elements</strong> in the middle of running PC
</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 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:
+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 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 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 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:
+
+<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>
+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:
+
+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>
+<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>
+
+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>.
+
+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.
+
+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.
+
+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>
@@ -660,18 +1055,42 @@ Pin(0 0 70 20 70 42 "" "1" 0x00000101)
</p>
</div>
-<!-- SECTION "Custom file elements" [34017-40478] -->
-<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>
+<!-- EDIT750 SECTION "Custom file elements" [34043-40504] -->
+<h2 class="sectionedit751"><a name="custom_m4_elements_requires_gsch2pcb_10" id="custom_m4_elements_requires_gsch2pcb_10">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:
+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>
+<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:
+
+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
@@ -681,11 +1100,24 @@ First, some words about how to find out about the default <strong>m4 elements</
define(`PKG_R025',
`Element(0x00 "$1" "$2" "$3" 120 30 0 100 0x00)
(
-...
-</pre>
+...</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>:
+
+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
@@ -697,11 +1129,23 @@ define(`PKG_SIL',
`define(`MAXY', `eval(`$4' * 100 -50)')
Element(0x00 "$1" "$2" "$3" 160 10 3 100 0x00)
(
-...
-</pre>
+...</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:
+
+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
@@ -719,15 +1163,29 @@ ISA8 0
OVEN_OSC 0
RADIAL_CAN 1
SMD_BASE 2 length and width of surface mount device
-SMD_CHIP 1 package length
-</pre>
+SMD_CHIP 1 package length</pre>
<p>
- And so on for the other <strong>.inc</strong> files…
+
+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:
+
+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>
@@ -754,15 +1212,26 @@ SMD_CHIP 1 package length
</ul>
<p>
-For this tutorial, Iâ??ll use the first <strong>pcb.inc</strong> way, so copy over the existing macro file:
+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>
+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:
+
+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
@@ -791,20 +1260,30 @@ 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>
+)')</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.
+
+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)" [40479-48166] -->
-<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>
+<!-- EDIT751 SECTION "Custom m4 elements (Requires gsch2pcb >= 1.0)" [40505-48192] -->
+<h2 class="sectionedit752"><a name="multi-user_setup_requires_gsch2pcb_10" id="multi-user_setup_requires_gsch2pcb_10">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:
+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
@@ -836,12 +1315,16 @@ The above examples are oriented towards a single user with projects and custom g
</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.
+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)" [48167-49804] -->
-<h2><a name="pc_board_fabrication" id="pc_board_fabrication">PC Board Fabrication</a></h2>
+<!-- EDIT752 SECTION "Multi-user Setup (requires gsch2pcb >= 1.0)" [48193-49830] -->
+<h2 class="sectionedit753"><a name="pc_board_fabrication" id="pc_board_fabrication">PC Board Fabrication</a></h2>
<div class="level2">
<p>
@@ -854,15 +1337,22 @@ The tutorial should cover pcb fabrication too.
<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.
+
+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.
+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.
+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>
@@ -871,9 +1361,14 @@ If you find that your pads and traces donâ??t print on the same page, or are pla
<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!
+
+<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" [49805-] --></body>
+<!-- EDIT753 SECTION "PC Board Fabrication" [49831-] --></body>
</html>
diff --git a/docs/wiki/geda-gsch2pcb_tutorial_releasenotes.html b/docs/wiki/geda-gsch2pcb_tutorial_releasenotes.html
index fc4aa9c..ab8efbf 100644
--- a/docs/wiki/geda-gsch2pcb_tutorial_releasenotes.html
+++ b/docs/wiki/geda-gsch2pcb_tutorial_releasenotes.html
@@ -12,13 +12,12 @@
<body>
-
-
-<h1><a name="release_notes_for_gsch2pcb_tutorial" id="release_notes_for_gsch2pcb_tutorial">Release Notes for gsch2pcb Tutorial</a></h1>
+<h1 class="sectionedit768"><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>.
+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>
@@ -32,7 +31,7 @@ These are the relase notes to the <a href="geda-gsch2pcb_tutorial.html" class="w
<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.
+ 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>
@@ -44,7 +43,7 @@ These are the relase notes to the <a href="geda-gsch2pcb_tutorial.html" class="w
<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 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>
@@ -57,14 +56,15 @@ These are the relase notes to the <a href="geda-gsch2pcb_tutorial.html" class="w
</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>
+<!-- EDIT768 SECTION "Release Notes for gsch2pcb Tutorial" [1-1644] -->
+<h2 class="sectionedit769"><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>
+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>
+<!-- EDIT769 SECTION "Source of the original document" [1645-] --></body>
</html>
diff --git a/docs/wiki/geda-gschem_mp.html b/docs/wiki/geda-gschem_mp.html
index 5710d10..89fd0e1 100644
--- a/docs/wiki/geda-gschem_mp.html
+++ b/docs/wiki/geda-gschem_mp.html
@@ -12,9 +12,7 @@
<body>
-
-
-<h1><a name="gschem_man-page" id="gschem_man-page">gschem man-page</a></h1>
+<h1 class="sectionedit845"><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)
diff --git a/docs/wiki/geda-gschem_symbol_creation.html b/docs/wiki/geda-gschem_symbol_creation.html
index 3eefee0..e9947f9 100644
--- a/docs/wiki/geda-gschem_symbol_creation.html
+++ b/docs/wiki/geda-gschem_symbol_creation.html
@@ -11,47 +11,22 @@
</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="#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>
+<h1 class="sectionedit847"><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<br/>
- The latest version of this document may be found at: <a href="http://geda.seul.org/wiki/geda:gschem_symbol_creation"; class="urlextern" title="http://geda.seul.org/wiki/geda:gschem_symbol_creation"; rel="nofollow">http://geda.seul.org/wiki/geda:gschem_symbol_creation</a><br/>
- This document is released under the <a href="geda-gfdl.html" class="wikilink1" title="geda-gfdl.html">GNU Free Documentation License (GFDL)</a>.<br/>
-
+
+The latest version of this document may be found at: <a href="http://geda.seul.org/wiki/geda:gschem_symbol_creation"; class="urlextern" title="http://geda.seul.org/wiki/geda:gschem_symbol_creation"; rel="nofollow">http://geda.seul.org/wiki/geda:gschem_symbol_creation</a><br/>
+
+This document is released under the <a href="geda-gfdl.html" class="wikilink1" title="geda-gfdl.html">GNU Free Documentation License (GFDL)</a>.<br/>
+
</p>
</div>
-<!-- SECTION "gEDA/gaf Symbol Creation Document" [1-294] -->
-<h2><a name="overview" id="overview">Overview</a></h2>
+<!-- EDIT847 SECTION "gEDA/gaf Symbol Creation Document" [1-291] -->
+<h2 class="sectionedit848"><a name="overview" id="overview">Overview</a></h2>
<div class="level2">
<p>
@@ -59,8 +34,8 @@ This document describes the creation of component symbols, including style conve
</p>
</div>
-<!-- SECTION "Overview" [295-494] -->
-<h2><a name="component_symbol_creation" id="component_symbol_creation">Component symbol creation</a></h2>
+<!-- EDIT848 SECTION "Overview" [292-490] -->
+<h2 class="sectionedit849"><a name="component_symbol_creation" id="component_symbol_creation">Component symbol creation</a></h2>
<div class="level2">
<p>
@@ -69,8 +44,10 @@ Component symbols (from here on known as â??symbolsâ??) are drawn using gschem.
<p>
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/>
+
+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>
@@ -80,7 +57,7 @@ Component symbols (from here on known as â??symbolsâ??) are drawn using gschem.
</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 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>
@@ -92,7 +69,8 @@ Translating the symbol to the origin is a required step. To translate a symbol e
</p>
<p>
-4. Save the symbol using Save or SaveAs… Here are some symbol naming conventions:<br/>
+4. Save the symbol using Save or SaveAsâ?¦ Here are some symbol naming
+conventions:<br/>
</p>
<ul>
@@ -109,24 +87,32 @@ Translating the symbol to the origin is a required step. To translate a symbol e
</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.
+
+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" [495-2132] -->
-<h2><a name="requirements" id="requirements">Requirements</a></h2>
+<!-- EDIT849 SECTION "Component symbol creation" [491-2128] -->
+<h2 class="sectionedit850"><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 <a href="geda-master_attributes_list.html" class="wikilink1" title="geda-master_attributes_list.html">Master
+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 <a href="geda-master_attributes_list.html" class="wikilink1" title="geda-master_attributes_list.html">Master
Attribute Document</a>.
</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 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>
@@ -138,11 +124,11 @@ Attribute Document</a>.
</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 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 class="level1"><div class="li"> footprint=PACKAGENAME should exist somewhere in the symbol which might be used with a pcb netlister. PACKAGENAME is a pcb footprint or package type like DIP14 or DIP40. Please see the <a href="geda-pcb_footprint_naming_conventions.html" class="wikilink1" title="geda-pcb_footprint_naming_conventions.html"> footprint naming conventions</a> page for further detail. If you are using gEDA / PCB, also see the PCB documentation and gnetlist/docs/README.pcb for more info on this attribute and how it is used.</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>
@@ -155,17 +141,17 @@ Attribute Document</a>.
</ul>
</div>
-<!-- SECTION "Requirements" [2133-6327] -->
-<h2><a name="style" id="style">Style</a></h2>
+<!-- EDIT850 SECTION "Requirements" [2129-6404] -->
+<h2 class="sectionedit851"><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.
+This section describes the style which is used in the standard gEDA/gaf symbol library.
</p>
</div>
-<!-- SECTION "Style" [6328-6438] -->
-<h3><a name="text" id="text">Text</a></h3>
+<!-- EDIT851 SECTION "Style" [6405-6512] -->
+<h3 class="sectionedit852"><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>
@@ -177,8 +163,8 @@ This section describes the style in which is used in the standard gEDA/gaf symbo
</ul>
</div>
-<!-- SECTION "Text" [6439-6675] -->
-<h3><a name="attributes" id="attributes">Attributes</a></h3>
+<!-- EDIT852 SECTION "Text" [6513-6749] -->
+<h3 class="sectionedit853"><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>
@@ -198,8 +184,8 @@ This section describes the style in which is used in the standard gEDA/gaf symbo
</ul>
</div>
-<!-- SECTION "Attributes" [6676-7845] -->
-<h3><a name="graphics" id="graphics">Graphics</a></h3>
+<!-- EDIT853 SECTION "Attributes" [6750-7919] -->
+<h3 class="sectionedit854"><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>
@@ -211,8 +197,8 @@ This section describes the style in which is used in the standard gEDA/gaf symbo
</ul>
</div>
-<!-- SECTION "Graphics" [7846-8196] -->
-<h3><a name="pins" id="pins">Pins</a></h3>
+<!-- EDIT854 SECTION "Graphics" [7920-8270] -->
+<h3 class="sectionedit855"><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>
@@ -242,8 +228,8 @@ This section describes the style in which is used in the standard gEDA/gaf symbo
</ul>
</div>
-<!-- SECTION "Pins" [8197-10152] -->
-<h3><a name="electrical" id="electrical">Electrical</a></h3>
+<!-- EDIT855 SECTION "Pins" [8271-10226] -->
+<h3 class="sectionedit856"><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>
@@ -257,12 +243,13 @@ This section describes the style in which is used in the standard gEDA/gaf symbo
</ul>
</div>
-<!-- SECTION "Electrical" [10153-10777] -->
-<h2><a name="hints_and_tips" id="hints_and_tips">Hints and Tips</a></h2>
+<!-- EDIT856 SECTION "Electrical" [10227-10851] -->
+<h2 class="sectionedit857"><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/>
+This section describes some hints and tips which will make your symbol creation
+experience easier.<br/>
</p>
<ul>
@@ -276,15 +263,15 @@ This section describes some hints and tips which will make your symbol creation
</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 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>
<li class="level1"><div class="li"> Pinnumber should be the visible attribute for pins, along with pinlabel if any.</div>
</li>
</ul>
</div>
-<!-- SECTION "Hints and Tips" [10778-12015] -->
-<h2><a name="example" id="example">Example</a></h2>
+<!-- EDIT857 SECTION "Hints and Tips" [10852-12089] -->
+<h2 class="sectionedit858"><a name="example" id="example">Example</a></h2>
<div class="level2">
<p>
@@ -360,48 +347,26 @@ 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>
+documentation=http:<em>www-s.ti.com/sc/ds/sn74hc00.pdf
+</xterm>
-<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" [12016-13732] -->
-<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>
+===== Document Revision History =====
+| September 14th, 2002|Created symbol.tex from symbols.html |
+| October 31st, 2002|Fixed bad example symbol |
+| February 11th, 2003|Footprint naming conventions added |
+| September 27th, 2003|Applied Dan McMahill's QFP and QFN patch |
+| July 6th, 2004|Added a bunch more details/hints to the pin section |
+
+</p>
</div>
-<!-- SECTION "Document Revision History" [13733-] --></body>
+<!-- EDIT858 SECTION "Example" [12090-] --></body>
</html>
diff --git a/docs/wiki/geda-gschem_ug.fr.html b/docs/wiki/geda-gschem_ug.fr.html
index 673f062..c29806e 100644
--- a/docs/wiki/geda-gschem_ug.fr.html
+++ b/docs/wiki/geda-gschem_ug.fr.html
@@ -11,212 +11,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>
+
+<h1 class="sectionedit860"><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>
@@ -232,12 +28,13 @@ This document is released under the <a href="geda-gfdl.html" class="wikilink1" t
</p>
<p>
- Please report any errors/inconsistencies in this document by commenting in the Discussion area at the bottom of the associated page.
+
+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>
+<!-- EDIT860 SECTION "Guide de l'utilisateur gschem gEDA" [1-409] -->
+<h1 class="sectionedit861"><a name="about_this_document" id="about_this_document">About this document ...</a></h1>
<div class="level1">
<p>
@@ -249,11 +46,13 @@ This document was generated using the LaTeX2HTML translator Version 2002-2-1 (1.
</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.
+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
+The command line arguments were:
+latex2html -local_icons gschem
</p>
<p>
@@ -261,18 +60,19 @@ 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>
+<!-- EDIT861 SECTION "About this document ..." [410-882] -->
+<h1 class="sectionedit862"><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:
+
+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 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>
@@ -291,12 +91,13 @@ This document describes the installation, configuration, and operation of the <s
</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>.
+
+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>
+<!-- EDIT862 SECTION "Introduction" [883-2837] -->
+<h1 class="sectionedit863"><a name="overview" id="overview">Overview</a></h1>
<div class="level1">
<p>
@@ -312,12 +113,13 @@ This document describes the installation, configuration, and operation of the <s
</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:
+
+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 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>
+<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>
@@ -335,41 +137,41 @@ This document describes the installation, configuration, and operation of the <s
</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 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 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 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 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 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 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 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>
+<div class="table sectionedit864"><table class="inline">
+ <tr class="row0">
+ <td class="col0"> <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>
-
+</table></div>
+<!-- EDIT864 TABLE [5381-5417] -->
</div>
-<!-- SECTION "Overview" [2838-5418] -->
-<h1><a name="resources" id="resources">Resources</a></h1>
+<!-- EDIT863 SECTION "Overview" [2838-5418] -->
+<h1 class="sectionedit865"><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 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 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>
+<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>
@@ -379,69 +181,70 @@ The following on-line resources are useful for designers using <strong>gschem</s
</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>
+<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 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 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 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 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 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 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 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 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 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 class="level1"><div class="li"> <a href="http://bugs.launchpad.net/geda"; class="urlextern" title="http://bugs.launchpad.net/geda"; rel="nofollow">gEDA Bug Tracker</a> â?? On launchpad</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 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 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 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 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 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>
+<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 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 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 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>
+<!-- EDIT865 SECTION "Resources" [5419-9647] -->
+<h1 class="sectionedit866"><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):
+
+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 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 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>
@@ -455,7 +258,7 @@ The following on-line resources are useful for designers using <strong>gschem</s
</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 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>
@@ -466,8 +269,8 @@ The following on-line resources are useful for designers using <strong>gschem</s
</ol>
</div>
-<!-- SECTION "How To Ask Questions" [9679-12860] -->
-<h1><a name="installing_gschem" id="installing_gschem">Installing gschem</a></h1>
+<!-- EDIT866 SECTION "How To Ask Questions" [9648-12829] -->
+<h1 class="sectionedit867"><a name="installing_gschem" id="installing_gschem">Installing gschem</a></h1>
<div class="level1">
<p>
@@ -475,27 +278,30 @@ As a mature OpenSource project, the gEDA Tools Suite and its components have bee
</p>
</div>
-<!-- SECTION "Installing gschem" [12861-13119] -->
-<h2><a name="latest_stable" id="latest_stable">Latest Stable</a></h2>
+<!-- EDIT867 SECTION "Installing gschem" [12830-13088] -->
+<h2 class="sectionedit868"><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.
+<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>
+<!-- EDIT868 SECTION "Latest Stable" [13089-13573] -->
+<h3 class="sectionedit869"><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.
+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>
+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>
@@ -503,13 +309,14 @@ The above command requires superuser permissions configured for the user invokin
</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>
+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>
+<!-- EDIT869 SECTION "gEDA Tools Suite CD-ROM" [13574-15260] -->
+<h3 class="sectionedit870"><a name="debian_distributions" id="debian_distributions">Debian distributions</a></h3>
<div class="level3">
<p>
@@ -517,8 +324,8 @@ For Debian distributions, you may wish to download the <a href="http://www.geda.
</p>
</div>
-<!-- SECTION "Debian distributions" [15292-15640] -->
-<h3><a name="red_hat_distributions" id="red_hat_distributions">Red Hat distributions</a></h3>
+<!-- EDIT870 SECTION "Debian distributions" [15261-15609] -->
+<h3 class="sectionedit871"><a name="red_hat_distributions" id="red_hat_distributions">Red Hat distributions</a></h3>
<div class="level3">
<p>
@@ -526,8 +333,8 @@ For Red Hat distributions (and possibly others) you may wish to download the lat
</p>
</div>
-<!-- SECTION "Red Hat distributions" [15641-15803] -->
-<h3><a name="mac_osx_distributions" id="mac_osx_distributions">Mac OSX distributions</a></h3>
+<!-- EDIT871 SECTION "Red Hat distributions" [15610-15772] -->
+<h3 class="sectionedit872"><a name="mac_osx_distributions" id="mac_osx_distributions">Mac OSX distributions</a></h3>
<div class="level3">
<p>
@@ -535,13 +342,14 @@ For Mac OSX distributions you may wish to download the <a href="http://www.geda.
</p>
</div>
-<!-- SECTION "Mac OSX distributions" [15804-15983] -->
-<h2><a name="cvs_unstable_testing" id="cvs_unstable_testing">CVS Unstable/Testing</a></h2>
+<!-- EDIT872 SECTION "Mac OSX distributions" [15773-15952] -->
+<h2 class="sectionedit873"><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:
+
+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>
@@ -551,30 +359,32 @@ For those already familiar with the gEDA/gaf applications on the â??gEDA Tools S
</ul>
</div>
-<!-- SECTION "CVS Unstable/Testing" [15984-16874] -->
-<h1><a name="configuring_gschem" id="configuring_gschem">Configuring gschem</a></h1>
+<!-- EDIT873 SECTION "CVS Unstable/Testing" [15953-16843] -->
+<h1 class="sectionedit874"><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;
+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/>
+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):
+
+<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 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 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>
@@ -584,7 +394,7 @@ 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 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>
@@ -597,65 +407,71 @@ margin-left : 2em"><font size="+0">; Comment in this scheme code if you want aut
(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 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 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 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:
+
+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 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 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 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>
+<!-- EDIT874 SECTION "Configuring gschem" [16844-22564] -->
+<h2 class="sectionedit875"><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:
+
+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>
+<!-- EDIT875 SECTION "gschemrc" [22565-22866] -->
+<h2 class="sectionedit876"><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:
+
+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>
+<!-- EDIT876 SECTION "gafrc" [22867-23156] -->
+<h1 class="sectionedit877"><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>
+<!-- EDIT877 SECTION "Lancer gschem" [23157-23185] -->
+<h2 class="sectionedit878"><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:
+
+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>
@@ -705,25 +521,27 @@ margin-left : 2em"><font size="+0">% <strong>echo $PATH</strong>
</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:
+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 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 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.
+
+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.
+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;
+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
@@ -746,65 +564,70 @@ If these commands do not return the expected results, then most likely the gEDA
</p>
</div>
-<!-- SECTION "Confirming gschem is installed" [23217-28922] -->
-<h2><a name="the_shell_prompt" id="the_shell_prompt">The Shell Prompt</a></h2>
+<!-- EDIT878 SECTION "Confirming gschem is installed" [23186-28891] -->
+<h2 class="sectionedit879"><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>
+<div class="table sectionedit880"><table class="inline">
+ <tr class="row0">
+ <td class="col0"> <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 class="row1">
+ <td class="col0"> Figure 1 â?? gnome-terminal </td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT880 TABLE [28921-28993] -->
<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:
+
+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 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 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 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 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 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 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 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 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/>
+
+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>
@@ -814,21 +637,21 @@ To open a specific schematic, run: <code><strong>% gschem schematic_name.sch</st
</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>
+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:
+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 class="level1"><div class="li"> â?¦</div>
</li>
</ul>
</div>
-<!-- SECTION "The Shell Prompt" [28923-32457] -->
-<h2><a name="backups" id="backups">Backups</a></h2>
+<!-- EDIT879 SECTION "The Shell Prompt" [28892-32426] -->
+<h2 class="sectionedit881"><a name="backups" id="backups">Backups</a></h2>
<div class="level2">
<p>
@@ -836,14 +659,17 @@ There are two basic mechanisms in <strong>gschem</strong> for backing up schemat
</p>
</div>
-<!-- SECTION "Backups" [32458-32609] -->
-<h3><a name="classic_linux_backups" id="classic_linux_backups">Classic Linux backups</a></h3>
+<!-- EDIT881 SECTION "Backups" [32427-32578] -->
+<h3 class="sectionedit882"><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;
+
+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}
@@ -863,41 +689,45 @@ Do you want to load the backup file?</font></pre>
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 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 class="level1"><div class="li"> add a â??#â?? to the end</div>
</li>
</ul>
<p>
- so that:
+
+so that:
</p>
<ul>
-<li class="level1"><div class="li"> â??schematic_1.schâ?? becomes "#schematic_1.sch#"</div>
+<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 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/>
+
+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.
+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>
+<!-- EDIT882 SECTION "Classic Linux backups" [32579-35485] -->
+<h3 class="sectionedit883"><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>
+<!-- EDIT883 SECTION "Incremental backups" [35486-35519] -->
+<h3 class="sectionedit884"><a name="relevant_configuration_settings" id="relevant_configuration_settings">Relevant configuration settings</a></h3>
<div class="level3">
<p>
@@ -915,12 +745,13 @@ There are the following configuration settings in the {binary-install-path}/shar
</ul>
</div>
-<!-- SECTION "Relevant configuration settings" [35551-36592] -->
-<h2><a name="on-line_documentation" id="on-line_documentation">On-line documentation</a></h2>
+<!-- EDIT884 SECTION "Relevant configuration settings" [35520-36561] -->
+<h2 class="sectionedit885"><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;
+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
@@ -934,7 +765,8 @@ Usage: gschem [OPTIONS] schematic_filename1 ... schematic_filenameN
</p>
<p>
-For a detailed explanation of the command line flags look at the <strong>gschem</strong> man page: <pre STYLE="background : LightGreen;
+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)
@@ -1049,20 +881,23 @@ 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>
+<!-- EDIT885 SECTION "On-line documentation" [36562-41031] -->
+<h1 class="sectionedit886"><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.
+
+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>
+<!-- EDIT886 SECTION "Electrical Connectivity" [41032-42748] -->
+<h1 class="sectionedit887"><a name="components_symbols_objects_attributes" id="components_symbols_objects_attributes">Components & Symbols & Objects & Attributes</a></h1>
<div class="level1">
<p>
@@ -1070,14 +905,16 @@ There is a hierarchical association between components, symbols, objects, and at
</p>
</div>
-<!-- SECTION "Components & Symbols & Objects & Attributes" [42780-42928] -->
-<h2><a name="components" id="components">Components</a></h2>
+<!-- EDIT887 SECTION "Components & Symbols & Objects & Attributes" [42749-42897] -->
+<h2 class="sectionedit888"><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:
+
+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>
@@ -1087,25 +924,30 @@ A component is the instantiation of a specific symbol, as placed on the schemati
</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.
+
+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>
+<!-- EDIT888 SECTION "Components" [42898-44712] -->
+<h2 class="sectionedit889"><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).
+
+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>
+<!-- EDIT889 SECTION "Symbols" [44713-45054] -->
+<h2 class="sectionedit890"><a name="objects" id="objects">Objects</a></h2>
<div class="level2">
<p>
@@ -1129,25 +971,26 @@ The following are objects:
</ul>
</div>
-<!-- SECTION "Objects" [45086-45198] -->
-<h2><a name="attributes" id="attributes">Attributes</a></h2>
+<!-- EDIT890 SECTION "Objects" [45055-45167] -->
+<h2 class="sectionedit891"><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>
+
+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>
+<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>
+<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 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>
@@ -1156,29 +999,36 @@ An attribute is text which is in the form <code>name=value</code> (there are no
</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;
+
+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;
+
+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>.
+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;
+
+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.
+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>
@@ -1186,17 +1036,18 @@ So, to summarize, attribute promotion takes unattached attributes inside symbols
</p>
</div>
-<!-- SECTION "Attributes" [45199-48585] -->
-<h1><a name="the_main_window" id="the_main_window">The Main Window</a></h1>
+<!-- EDIT891 SECTION "Attributes" [45168-48554] -->
+<h1 class="sectionedit892"><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>
+<div class="table sectionedit893"><table class="inline">
+ <tr class="row0">
+ <td class="col0"> <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>
-
+</table></div>
+<!-- EDIT893 TABLE [48585-48624] -->
<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:
+
+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>
@@ -1208,91 +1059,100 @@ So, to summarize, attribute promotion takes unattached attributes inside symbols
</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).
+
+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>
+<!-- EDIT892 SECTION "The Main Window" [48555-51468] -->
+<h1 class="sectionedit894"><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>
+<div class="table sectionedit895"><table class="inline">
+ <tr class="row0">
+ <td class="col0"> <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>
-
+</table></div>
+<!-- EDIT895 TABLE [51501-51564] -->
<p>
- Add some details about what gets displayed in the status window.
+
+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>
+<!-- EDIT894 SECTION "The Status Window" [51469-51631] -->
+<h1 class="sectionedit896"><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:
+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 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.
+
+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>
+<!-- EDIT896 SECTION "The Schematic File" [51632-52401] -->
+<h1 class="sectionedit897"><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:
+
+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 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.
+
+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>
+<!-- EDIT897 SECTION "The Symbol File" [52402-53388] -->
+<h1 class="sectionedit898"><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.
+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>
+<!-- EDIT898 SECTION "Symbol Libraries" [53389-53542] -->
+<h1 class="sectionedit899"><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.
+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>
+<!-- EDIT899 SECTION "The Log File" [53543-53820] -->
+<h1 class="sectionedit900"><a name="grips" id="grips">Grips</a></h1>
<div class="level1">
<p>
@@ -1314,19 +1174,22 @@ Using grips is easy:
</ul>
</div>
-<!-- SECTION "Grips" [53852-54561] -->
-<h1><a name="menu_operations" id="menu_operations">Menu Operations</a></h1>
+<!-- EDIT900 SECTION "Grips" [53821-54530] -->
+<h1 class="sectionedit901"><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>
+<!-- EDIT901 SECTION "Menu Operations" [54531-54560] -->
+<h2 class="sectionedit902"><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;
+
+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}
@@ -1343,12 +1206,12 @@ margin-left : 2em"><font size="+0">WARNING: Found an autosave backup file:
</p>
<p>
-The following are available from the <strong>gschem</strong> main windowâ??s menu-bar when you expand <strong>File</strong>:
+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>
+<!-- EDIT902 SECTION "File" [54561-55714] -->
+<h3 class="sectionedit903"><a name="new_window_fw" id="new_window_fw">New Window (fw)</a></h3>
<div class="level3">
<p>
@@ -1356,8 +1219,8 @@ The following are available from the <strong>gschem</strong> main windowâ??s men
</p>
</div>
-<!-- SECTION "New Window (fw)" [55746-55886] -->
-<h3><a name="new_page_fn" id="new_page_fn">New Page (fn)</a></h3>
+<!-- EDIT903 SECTION "New Window (fw)" [55715-55855] -->
+<h3 class="sectionedit904"><a name="new_page_fn" id="new_page_fn">New Page (fn)</a></h3>
<div class="level3">
<p>
@@ -1365,13 +1228,14 @@ The following are available from the <strong>gschem</strong> main windowâ??s men
</p>
</div>
-<!-- SECTION "New Page (fn)" [55887-56093] -->
-<h3><a name="open_page..._fo" id="open_page..._fo">Open Page... (fo)</a></h3>
+<!-- EDIT904 SECTION "New Page (fn)" [55856-56062] -->
+<h3 class="sectionedit905"><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:
+<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>
@@ -1391,8 +1255,8 @@ The following are available from the <strong>gschem</strong> main windowâ??s men
</ul>
</div>
-<!-- SECTION "Open Page... (fo)" [56094-56380] -->
-<h3><a name="close_page_pc" id="close_page_pc">Close Page (pc)</a></h3>
+<!-- EDIT905 SECTION "Open Page... (fo)" [56063-56349] -->
+<h3 class="sectionedit906"><a name="close_page_pc" id="close_page_pc">Close Page (pc)</a></h3>
<div class="level3">
<p>
@@ -1400,8 +1264,8 @@ The following are available from the <strong>gschem</strong> main windowâ??s men
</p>
</div>
-<!-- SECTION "Close Page (pc)" [56381-56563] -->
-<h3><a name="revert_page_pr" id="revert_page_pr">Revert Page (pr)</a></h3>
+<!-- EDIT906 SECTION "Close Page (pc)" [56350-56532] -->
+<h3 class="sectionedit907"><a name="revert_page_pr" id="revert_page_pr">Revert Page (pr)</a></h3>
<div class="level3">
<p>
@@ -1409,17 +1273,19 @@ The following are available from the <strong>gschem</strong> main windowâ??s men
</p>
</div>
-<!-- SECTION "Revert Page (pr)" [56564-56861] -->
-<h3><a name="save_page_fs" id="save_page_fs">Save Page (fs)</a></h3>
+<!-- EDIT907 SECTION "Revert Page (pr)" [56533-56830] -->
+<h3 class="sectionedit908"><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:
+
+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 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>
@@ -1427,20 +1293,23 @@ The following are available from the <strong>gschem</strong> main windowâ??s men
</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>
+<!-- EDIT908 SECTION "Save Page (fs)" [56831-57484] -->
+<h3 class="sectionedit909"><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.
+<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>
+<!-- EDIT909 SECTION "Save Page As... (fa)" [57485-57937] -->
+<h3 class="sectionedit910"><a name="save_all_fl_fl" id="save_all_fl_fl">Save All (fl) (fl)</a></h3>
<div class="level3">
<p>
@@ -1448,13 +1317,14 @@ The following are available from the <strong>gschem</strong> main windowâ??s men
</p>
</div>
-<!-- SECTION "Save All (fl) (fl)" [57969-58094] -->
-<h3><a name="print..._fp" id="print..._fp">Print... (fp)</a></h3>
+<!-- EDIT910 SECTION "Save All (fl) (fl)" [57938-58063] -->
+<h3 class="sectionedit911"><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:
+<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>
@@ -1463,11 +1333,11 @@ The following are available from the <strong>gschem</strong> main windowâ??s men
</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 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 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 class="level2"><div class="li"> Current window â?? Scaled to fit the page size, but not optimally.</div>
</li>
</ul>
</li>
@@ -1482,8 +1352,10 @@ The following are available from the <strong>gschem</strong> main windowâ??s men
</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>
+
+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>
@@ -1491,13 +1363,14 @@ The following are available from the <strong>gschem</strong> main windowâ??s men
</div>
-<!-- SECTION "Print... (fp)" [58095-59143] -->
-<h3><a name="write_png..._fi" id="write_png..._fi">Write PNG... (fi)</a></h3>
+<!-- EDIT911 SECTION "Print... (fp)" [58064-59112] -->
+<h3 class="sectionedit912"><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:
+<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>
@@ -1518,27 +1391,29 @@ The following are available from the <strong>gschem</strong> main windowâ??s men
</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 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.).
+
+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>
+<!-- EDIT912 SECTION "Write PNG... (fi)" [59113-59909] -->
+<h3 class="sectionedit913"><a name="execute_script_ft" id="execute_script_ft">Execute Script... (ft)</a></h3>
<div class="level3">
<p>
-<strong>File | Execute Script…</strong> …..TBD
+<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>
+<!-- EDIT913 SECTION "Execute Script... (ft)" [59910-59981] -->
+<h3 class="sectionedit914"><a name="close_window_fc" id="close_window_fc">Close Window (fc)</a></h3>
<div class="level3">
<p>
@@ -1546,8 +1421,8 @@ The following are available from the <strong>gschem</strong> main windowâ??s men
</p>
</div>
-<!-- SECTION "Close Window (fc)" [60013-60263] -->
-<h3><a name="quit_alt-q" id="quit_alt-q">Quit (Alt-q)</a></h3>
+<!-- EDIT914 SECTION "Close Window (fc)" [59982-60232] -->
+<h3 class="sectionedit915"><a name="quit_alt-q" id="quit_alt-q">Quit (Alt-q)</a></h3>
<div class="level3">
<p>
@@ -1555,8 +1430,8 @@ The following are available from the <strong>gschem</strong> main windowâ??s men
</p>
</div>
-<!-- SECTION "Quit (Alt-q)" [60264-60456] -->
-<h2><a name="edit" id="edit">Edit</a></h2>
+<!-- EDIT915 SECTION "Quit (Alt-q)" [60233-60425] -->
+<h2 class="sectionedit916"><a name="edit" id="edit">Edit</a></h2>
<div class="level2">
<p>
@@ -1564,13 +1439,15 @@ The following are available from the <strong>gschem</strong> main windowâ??s men
</p>
</div>
-<!-- SECTION "Edit" [60457-60573] -->
-<h3><a name="undo_shift-u" id="undo_shift-u">Undo (shift-u)</a></h3>
+<!-- EDIT916 SECTION "Edit" [60426-60542] -->
+<h3 class="sectionedit917"><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;
+
+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
@@ -1581,13 +1458,14 @@ margin-left : 2em"><font size="+0">; undo-levels number
<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/>
+
+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>
+<!-- EDIT917 SECTION "Undo (shift-u)" [60543-61501] -->
+<h3 class="sectionedit918"><a name="redo_shift-r" id="redo_shift-r">Redo (shift-r)</a></h3>
<div class="level3">
<p>
@@ -1596,48 +1474,65 @@ After every action (including zooming and panning) the schematic is saved to dis
</p>
</div>
-<!-- SECTION "Redo (shift-r)" [61533-61841] -->
-<h3><a name="select_mode_s" id="select_mode_s">Select Mode (s)</a></h3>
+<!-- EDIT918 SECTION "Redo (shift-r)" [61502-61810] -->
+<h3 class="sectionedit919"><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.
+
+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>
+<!-- EDIT919 SECTION "Select Mode (s)" [61811-64218] -->
+<h3 class="sectionedit920"><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:
+
+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 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:
+
+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>
@@ -1659,23 +1554,27 @@ First, select the object to be edited (i.e., in <strong>Select Mode</strong>).<b
</ul>
<p>
- Apply the changes by pressing OK.
+
+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.
+
+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>
+<!-- EDIT920 SECTION "Edit... (ee)" [64219-65413] -->
+<h3 class="sectionedit921"><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:
+
+<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>
@@ -1697,22 +1596,25 @@ First, select the text object to be edited (i.e., in <strong>Select Mode</strong
</ul>
<p>
- Apply the changes by pressing OK.
+
+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.
+
+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>
+<!-- EDIT921 SECTION "Edit Text... (ex)" [65414-66272] -->
+<h3 class="sectionedit922"><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):
+
+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>
@@ -1732,20 +1634,24 @@ First, select the text object to be edited (i.e., in <strong>Select Mode</strong
</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/>
+
+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>
+<!-- EDIT922 SECTION "Copy Mode (ec)" [66273-67197] -->
+<h3 class="sectionedit923"><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):
+
+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>
@@ -1765,9 +1671,12 @@ First, select the text object to be edited (i.e., in <strong>Select Mode</strong
</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/>
+
+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>
@@ -1785,13 +1694,14 @@ Since version 20060906, there is another way to move object(s):<br/>
</ul>
</div>
-<!-- SECTION "Move Mode (em)" [67229-68382] -->
-<h3><a name="delete_delete-key" id="delete_delete-key">Delete (Delete-key)</a></h3>
+<!-- EDIT923 SECTION "Move Mode (em)" [67198-68351] -->
+<h3 class="sectionedit924"><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:
+
+To delete objects:
</p>
<ul>
<li class="level1"><div class="li"> Select the desired object(s) (i.e., in <strong>Select Mode</strong>)</div>
@@ -1801,17 +1711,19 @@ Since version 20060906, there is another way to move object(s):<br/>
</ul>
<p>
- The object(s) will be deleted immediately. If you inadvertantly delete a component, you can use Undo to recover.
+
+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>
+<!-- EDIT924 SECTION "Delete (Delete-key)" [68352-68670] -->
+<h3 class="sectionedit925"><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:
+
+To rotate objects:
</p>
<ul>
<li class="level1"><div class="li"> Select the desired object(s) (i.e., in <strong>Select Mode</strong>)</div>
@@ -1823,19 +1735,22 @@ Since version 20060906, there is another way to move object(s):<br/>
</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/>
+
+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>
+<!-- EDIT925 SECTION "Rotate 90 Mode (er)" [68671-69260] -->
+<h3 class="sectionedit926"><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:
+
+To mirror objects:
</p>
<ul>
<li class="level1"><div class="li"> Select the desired object(s) (i.e., in <strong>Select Mode</strong>)</div>
@@ -1847,25 +1762,30 @@ Since version 20060906, there is another way to move object(s):<br/>
</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.
+
+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>
+<!-- EDIT926 SECTION "Mirror Mode (ei)" [69261-69917] -->
+<h3 class="sectionedit927"><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):
+
+<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 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>
@@ -1874,22 +1794,24 @@ Some physical packages (e.g., the classic 7400 Quad NAND gate) contain more than
</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.
+
+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>
+<!-- EDIT927 SECTION "Slot... (e shift-s)" [69918-71134] -->
+<h3 class="sectionedit928"><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:
+<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 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>
@@ -1930,20 +1852,25 @@ Some physical packages (e.g., the classic 7400 Quad NAND gate) contain more than
</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.
+
+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>
+<!-- EDIT928 SECTION "Color... (eo)" [71135-72093] -->
+<h3 class="sectionedit929"><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:
+
+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>
@@ -1953,24 +1880,28 @@ Some physical packages (e.g., the classic 7400 Quad NAND gate) contain more than
</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.
+
+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>
+<!-- EDIT929 SECTION "Lock (el) / Unlock (e shift-l)" [72094-73632] -->
+<h3 class="sectionedit930"><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>:
+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 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>
@@ -1991,22 +1922,24 @@ The <strong>Edit | Line Width & Type…</strong> dialog box lets you co
</ul>
<p>
- Note that if the line width doesnâ??t seem to change, just pick a larger value.
+
+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>
+<!-- EDIT930 SECTION "Line Width & Type... (ew)" [73633-74248] -->
+<h3 class="sectionedit931"><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:
+<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 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>
@@ -2029,28 +1962,29 @@ The <strong>Edit | Line Width & Type…</strong> dialog box lets you co
</ul>
</div>
-<!-- SECTION "Fill Type... (ef)" [74280-74620] -->
-<h3><a name="symbol_translate..._et" id="symbol_translate..._et">Symbol Translate... (et)</a></h3>
+<!-- EDIT931 SECTION "Fill Type... (ef)" [74249-74589] -->
+<h3 class="sectionedit932"><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:
+<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 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 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 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>
@@ -2063,19 +1997,22 @@ The <strong>Edit | Line Width & Type…</strong> dialog box lets you co
</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/>
+
+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>
+<!-- EDIT932 SECTION "Symbol Translate... (et)" [74590-75754] -->
+<h3 class="sectionedit933"><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>:
+
+To <strong>Embed Component/Picture</strong>:
</p>
<ul>
<li class="level1"><div class="li"> Select the component/picture (in <strong>Select Mode</strong>)</div>
@@ -2085,19 +2022,24 @@ The <strong>Edit | Line Width & Type…</strong> dialog box lets you co
</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).
+
+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>
+<!-- EDIT933 SECTION "Embed Component/Picture (eb)" [75755-76784] -->
+<h3 class="sectionedit934"><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>:
+<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>
@@ -2107,42 +2049,48 @@ The <strong>Edit | Line Width & Type…</strong> dialog box lets you co
</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.
+
+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>
+<!-- EDIT934 SECTION "Unembed Component/Picture (eu)" [76785-77374] -->
+<h3 class="sectionedit935"><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:
+<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 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 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 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 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:
+
+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>
@@ -2152,16 +2100,20 @@ The <strong>Edit | Line Width & Type…</strong> dialog box lets you co
</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>
+<!-- EDIT935 SECTION "Update Component (ep)" [77375-79184] -->
+<h3 class="sectionedit936"><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 :
+<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>
@@ -2209,22 +2161,29 @@ The <strong>Edit | Line Width & Type…</strong> dialog box lets you co
</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.
+
+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>
+<!-- EDIT936 SECTION "Show/Hide Inv Text (en)" [79185-82012] -->
+<h3 class="sectionedit937"><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:
+<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>
@@ -2234,13 +2193,15 @@ The <strong>Edit | Line Width & Type…</strong> dialog box lets you co
</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.
+
+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>
+<!-- EDIT937 SECTION "Make Inv Text Vis (ev)" [82013-82676] -->
+<h2 class="sectionedit938"><a name="buffer" id="buffer">Buffer</a></h2>
<div class="level2">
<p>
@@ -2248,8 +2209,8 @@ The <strong>Edit | Line Width & Type…</strong> dialog box lets you co
</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>
+<!-- EDIT938 SECTION "Buffer" [82677-82796] -->
+<h3 class="sectionedit939"><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>
@@ -2263,8 +2224,8 @@ To copy something into a buffer:
</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>
+<!-- EDIT939 SECTION "Copy into 1/2/3/4/5 (yc)" [82797-82949] -->
+<h3 class="sectionedit940"><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>
@@ -2272,8 +2233,8 @@ 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>
+<!-- EDIT940 SECTION "Cut into 1/2/3/4/5 (yu)" [82950-83051] -->
+<h3 class="sectionedit941"><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>
@@ -2295,28 +2256,30 @@ To paste a buffer into the current schematic:
</ol>
</div>
-<!-- SECTION "Paste from 1/2/3/4/5 (yp)" [83083-83436] -->
-<h2><a name="view" id="view">View</a></h2>
+<!-- EDIT941 SECTION "Paste from 1/2/3/4/5 (yp)" [83052-83405] -->
+<h2 class="sectionedit942"><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>
+<!-- EDIT942 SECTION "View" [83406-83423] -->
+<h3 class="sectionedit943"><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.
+
+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>
+<!-- EDIT943 SECTION "Redraw (vr)" [83424-83674] -->
+<h3 class="sectionedit944"><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:
+
+To pan the display:
</p>
<ul>
<li class="level1"><div class="li"> Select <strong>View | Pan</strong></div>
@@ -2326,50 +2289,61 @@ To paste a buffer into the current schematic:
</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;
+
+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;
+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;
+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;
+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;
+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;
+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.
+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>
+<!-- EDIT944 SECTION "Pan (x)" [83675-85471] -->
+<h3 class="sectionedit945"><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>:
+
+To use <strong>View | Zoom Box</strong>:
</p>
<ul>
<li class="level1"><div class="li"> Select <strong>View | Zoom Box</strong></div>
@@ -2385,18 +2359,21 @@ to either your userâ??s ~/gschemrc file or local â??pwdâ??/gschemrc file, whenev
</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.
+
+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>
+<!-- EDIT945 SECTION "Zoom Box (w)" [85472-86352] -->
+<h3 class="sectionedit946"><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:
+
+To view all of the current window's objects:
</p>
<ul>
<li class="level1"><div class="li"> Select <strong>View | Extents</strong></div>
@@ -2404,18 +2381,20 @@ to either your userâ??s ~/gschemrc file or local â??pwdâ??/gschemrc file, whenev
</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/>
+
+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>
+<!-- EDIT946 SECTION "Zoom Extents (ve)" [86353-86719] -->
+<h3 class="sectionedit947"><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:
+
+To zoom in:
</p>
<ul>
<li class="level1"><div class="li"> Select <strong>View | Zoom In</strong></div>
@@ -2423,18 +2402,22 @@ to either your userâ??s ~/gschemrc file or local â??pwdâ??/gschemrc file, whenev
</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;
+
+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;
+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:
+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>
@@ -2444,17 +2427,19 @@ in either your userâ??s ~/gschemrc file or local â??pwdâ??/gschemrc file, whenev
</ul>
<p>
- Typing â??<strong>z</strong>â?? is particularly convenient for those that have learned to navigate the schematics using the shortcuts.
+
+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>
+<!-- EDIT947 SECTION "Zoom In (z)" [86720-87881] -->
+<h3 class="sectionedit948"><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:
+
+To zoom out:
</p>
<ul>
<li class="level1"><div class="li"> Select <strong>View | Zoom Out</strong></div>
@@ -2462,18 +2447,22 @@ in either your userâ??s ~/gschemrc file or local â??pwdâ??/gschemrc file, whenev
</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;
+
+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;
+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:
+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>
@@ -2483,12 +2472,13 @@ in either your userâ??s ~/gschemrc file or local â??pwdâ??/gschemrc file, whenev
</ul>
<p>
- Typing â??<strong>Z</strong>â?? is particularly convenient for those that have learned to navigate the schematics using the shortcuts.
+
+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>
+<!-- EDIT948 SECTION "Zoom Out (Z)" [87882-89070] -->
+<h3 class="sectionedit949"><a name="zoom_full_vf" id="zoom_full_vf">Zoom Full (vf)</a></h3>
<div class="level3">
<p>
@@ -2505,7 +2495,8 @@ To view the maximum displayable area:
</ul>
<p>
- The window contents will immediately change to show the maximum possible displayable view.<br/>
+
+The window contents will immediately change to show the maximum possible displayable view.<br/>
</p>
@@ -2518,7 +2509,8 @@ To view the maximum displayable area using the keyboard shortcut (i.e., â??<stro
</ul>
<p>
- The window contents will immediately change to show the maximum possible displayable view.<br/>
+
+The window contents will immediately change to show the maximum possible displayable view.<br/>
</p>
@@ -2527,57 +2519,57 @@ To view the maximum displayable area using the keyboard shortcut (i.e., â??<stro
</p>
</div>
-<!-- SECTION "Zoom Full (vf)" [89102-89880] -->
-<h2><a name="page" id="page">Page</a></h2>
+<!-- EDIT949 SECTION "Zoom Full (vf)" [89071-89849] -->
+<h2 class="sectionedit950"><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>
+<!-- EDIT950 SECTION "Page" [89850-89868] -->
+<h3 class="sectionedit951"><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>
+<!-- EDIT951 SECTION "Manager... (pm)" [89869-89896] -->
+<h3 class="sectionedit952"><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>
+<!-- EDIT952 SECTION "Next (>)" [89897-89917] -->
+<h3 class="sectionedit953"><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>
+<!-- EDIT953 SECTION "Previous (<)" [89918-89942] -->
+<h3 class="sectionedit954"><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>
+<!-- EDIT954 SECTION "New (pe)" [89943-89963] -->
+<h3 class="sectionedit955"><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>
+<!-- EDIT955 SECTION "Revert (pr)" [89964-89987] -->
+<h3 class="sectionedit956"><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>
+<!-- EDIT956 SECTION "Close (pc)" [89988-90010] -->
+<h3 class="sectionedit957"><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>
+<!-- EDIT957 SECTION "Discard (pd)" [90011-90035] -->
+<h2 class="sectionedit958"><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>
+<!-- EDIT958 SECTION "Add" [90036-90052] -->
+<h3 class="sectionedit959"><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
+<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>
@@ -2585,7 +2577,7 @@ To view the maximum displayable area using the keyboard shortcut (i.e., â??<stro
Pour placer un composant:
</p>
<ul>
-<li class="level1"><div class="li"> Select <strong>Add |Component…</strong></div>
+<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>
@@ -2604,10 +2596,14 @@ Pour placer un composant:
</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:
+
+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>
@@ -2621,18 +2617,21 @@ Pour placer un composant:
</ul>
<p>
- It helps to preview the symbol in the â??Select Componentâ?? dialog box before selecting and placing the symbol.
+
+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>
+<!-- EDIT959 SECTION "Component... (i)" [90053-91651] -->
+<h3 class="sectionedit960"><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:
+
+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>
@@ -2642,41 +2641,45 @@ Pour placer un composant:
<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>
+<div class="table sectionedit961"><table class="inline">
+ <tr class="row0">
+ <td class="col0"> <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>
-
+</table></div>
+<!-- EDIT961 TABLE [92017-92039] -->
<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:
+
+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 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 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:
+
+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 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 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):
+
+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>
@@ -2698,67 +2701,83 @@ Pour placer un composant:
</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.
+
+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>
+<!-- EDIT960 SECTION "Net (n)" [91652-94283] -->
+<h3 class="sectionedit962"><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.
+
+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>
+<!-- EDIT962 SECTION "Bus (u)" [94284-94543] -->
+<h3 class="sectionedit963"><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:
+<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 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 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 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.
+
+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>
+<!-- EDIT963 SECTION "Attribute... (aa)" [94544-96350] -->
+<h3 class="sectionedit964"><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:
+<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 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 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>
@@ -2774,13 +2793,15 @@ la souris)
<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 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>
+
+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>
@@ -2791,24 +2812,29 @@ la souris)
<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>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>
+<!-- EDIT964 SECTION "Text... (at)" [96351-98361] -->
+<h3 class="sectionedit965"><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:
+
+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 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>
@@ -2827,10 +2853,11 @@ la souris)
</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:
+
+<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 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>
@@ -2839,19 +2866,21 @@ la souris)
</ul>
<p>
- Pour effacer une ligne directe en cours, pressez le dernier bouton de souris ou la touche ESC.
+
+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>
+<!-- EDIT965 SECTION "Line (l)" [98362-99530] -->
+<h3 class="sectionedit966"><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:
+<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 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>
@@ -2868,21 +2897,24 @@ la souris)
</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.
+
+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>
+<!-- EDIT966 SECTION "Box (b)" [99531-100283] -->
+<h3 class="sectionedit967"><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:
+
+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 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>
@@ -2899,21 +2931,25 @@ la souris)
</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/>
+
+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>
+<!-- EDIT967 SECTION "Circle (ai)" [100284-101234] -->
+<h3 class="sectionedit968"><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:
+<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 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>
@@ -2925,7 +2961,7 @@ la souris)
</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 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>
@@ -2936,22 +2972,26 @@ la souris)
</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.
+
+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>
+<!-- EDIT968 SECTION "Arc (ar)" [101235-102395] -->
+<h3 class="sectionedit969"><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:
+
+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 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>
@@ -2970,19 +3010,21 @@ la souris)
</ul>
<p>
- To cancel a pin in progress, press the last mouse button or the ESC key.
+
+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>
+<!-- EDIT969 SECTION "Pin (ap)" [102396-103583] -->
+<h3 class="sectionedit970"><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:
+<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 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>
@@ -3003,85 +3045,103 @@ la souris)
</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.
+
+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>
+<!-- EDIT970 SECTION "Picture... (ag)" [103584-104579] -->
+<h2 class="sectionedit971"><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>
+<!-- EDIT971 SECTION "Hierarchy" [104580-104602] -->
+<h3 class="sectionedit972"><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:
+
+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 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).
+
+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=) 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>
+<!-- EDIT972 SECTION "Down Schematic (Hd)" [104603-106479] -->
+<h3 class="sectionedit973"><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.
+
+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>
+<!-- EDIT973 SECTION "Down Symbol (Hs)" [106480-106848] -->
+<h3 class="sectionedit974"><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).
+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>
+<!-- EDIT974 SECTION "Up (Hu)" [106849-106989] -->
+<h3 class="sectionedit975"><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.
+
+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>
+<!-- EDIT975 SECTION "Documentation (Ho)" [106990-108074] -->
+<h2 class="sectionedit976"><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>
+<!-- EDIT976 SECTION "Attributes" [108075-108098] -->
+<h3 class="sectionedit977"><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:
+
+To use Attributes/Attach:
</p>
<ol>
<li class="level1"><div class="li"> Select the object which will receive the attributes</div>
@@ -3093,18 +3153,21 @@ The Attach command allows you to take a text item (in the proper form; <code>nam
</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.
+
+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>
+<!-- EDIT977 SECTION "Attach (ta)" [108099-108906] -->
+<h3 class="sectionedit978"><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:
+
+To deselect an object of all attributes:
</p>
<ol>
<li class="level1"><div class="li"> Select the object of interest</div>
@@ -3114,18 +3177,21 @@ Detach allows you to deassociate attributes from objects.<br/>
</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).
+
+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>
+<!-- EDIT978 SECTION "Detach (td)" [108907-109513] -->
+<h3 class="sectionedit979"><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:
+
+To use the options:
</p>
<ol>
<li class="level1"><div class="li"> Select the attribute(s) of interest</div>
@@ -3135,18 +3201,21 @@ These operations allow you to control which part of the attribute string is visi
</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>
+
+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>
+<!-- EDIT979 SECTION "Show Value (tv)" [109514-110052] -->
+<h3 class="sectionedit980"><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:
+
+To use the options:
</p>
<ol>
<li class="level1"><div class="li"> Select the attribute(s) of interest</div>
@@ -3156,18 +3225,21 @@ These operations allow you to control which part of the attribute string is visi
</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>
+
+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>
+<!-- EDIT980 SECTION "Show Name (tn)" [110053-110590] -->
+<h3 class="sectionedit981"><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:
+
+To use the options:
</p>
<ol>
<li class="level1"><div class="li"> Select the attribute(s) of interest</div>
@@ -3177,18 +3249,21 @@ These operations allow you to control which part of the attribute string is visi
</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>
+
+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>
+<!-- EDIT981 SECTION "Show Both (tb)" [110591-111128] -->
+<h3 class="sectionedit982"><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:
+
+To use this option:
</p>
<ol>
<li class="level1"><div class="li"> Select the text item(s) of interest</div>
@@ -3198,49 +3273,53 @@ This operation allows you to toggle the visibility of attributes.<br/>
</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.
+
+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>
+<!-- EDIT982 SECTION "Toggle Visibility (tt)" [111129-111824] -->
+<h3 class="sectionedit983"><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>
+<!-- EDIT983 SECTION "Find Specific Text... (t shift-f)" [111825-111869] -->
+<h3 class="sectionedit984"><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>
+<!-- EDIT984 SECTION "Hide Specific Text... (th)" [111870-111907] -->
+<h3 class="sectionedit985"><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>
+<!-- EDIT985 SECTION "Show Specific Text... (t shift-h)" [111908-111951] -->
+<h3 class="sectionedit986"><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>
+<!-- EDIT986 SECTION "Autonumber Text... (tu)" [111952-111986] -->
+<h2 class="sectionedit987"><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>
+<!-- EDIT987 SECTION "Options" [111987-112007] -->
+<h3 class="sectionedit988"><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.
+<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>
+<!-- EDIT988 SECTION "Text Size... (ot)" [112008-112320] -->
+<h3 class="sectionedit989"><a name="toggle_grid_on_off_og" id="toggle_grid_on_off_og">Toggle Grid On/Off (og)</a></h3>
<div class="level3">
<p>
@@ -3248,29 +3327,32 @@ This operation allows you to toggle the visibility of attributes.<br/>
</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>
+<!-- EDIT989 SECTION "Toggle Grid On/Off (og)" [112321-112414] -->
+<h3 class="sectionedit990"><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.
+
+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>
+<!-- EDIT990 SECTION "Toggle Snap On/Off (os)" [112415-112866] -->
+<h3 class="sectionedit991"><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.
+<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>
+<!-- EDIT991 SECTION "Snap Grid Spacing... (oS)" [112867-113170] -->
+<h3 class="sectionedit992"><a name="toggle_outline_box_oa" id="toggle_outline_box_oa">Toggle Outline/Box (oa)</a></h3>
<div class="level3">
<p>
@@ -3278,17 +3360,17 @@ This operation allows you to toggle the visibility of attributes.<br/>
</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>
+<!-- EDIT992 SECTION "Toggle Outline/Box (oa)" [113171-113480] -->
+<h3 class="sectionedit993"><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> …..????
+<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>
+<!-- EDIT993 SECTION "Toggle Net/Rubberband (or)" [113481-113564] -->
+<h3 class="sectionedit994"><a name="show_log_window_ol" id="show_log_window_ol">Show Log Window (ol)</a></h3>
<div class="level3">
<p>
@@ -3296,72 +3378,72 @@ This operation allows you to toggle the visibility of attributes.<br/>
</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>
+<!-- EDIT994 SECTION "Show Log Window (ol)" [113565-113735] -->
+<h3 class="sectionedit995"><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.
+<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>
+<!-- EDIT995 SECTION "Show Coord Window... (oc)" [113736-113940] -->
+<h2 class="sectionedit996"><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>
+<!-- EDIT996 SECTION "Help" [113941-113958] -->
+<h3 class="sectionedit997"><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:
+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 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 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>
+<!-- EDIT997 SECTION "About... (ha)" [113959-114161] -->
+<h3 class="sectionedit998"><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.
+<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>
+<!-- EDIT998 SECTION "Manual... (hm)" [114162-114375] -->
+<h3 class="sectionedit999"><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).
+<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>
+<!-- EDIT999 SECTION "Hotkeys... (hh)" [114376-114503] -->
+<h3 class="sectionedit1000"><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:
+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 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 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>
+<!-- EDIT1000 SECTION "Component... (Ho)" [114504-115286] -->
+<h1 class="sectionedit1001"><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>
@@ -3369,26 +3451,26 @@ A short discussion of Light Symbol Libraries as the default for <strong>gschem</
</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>
+<!-- EDIT1001 SECTION "Appendix A -- Heavy vs Light Symbol Libraries" [115287-115480] -->
+<h1 class="sectionedit1002"><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…
+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>
+<!-- EDIT1002 SECTION "Appendix B -- Printing Schematics and Symbols" [115481-115559] -->
+<h1 class="sectionedit1003"><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…
+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>
+<!-- EDIT1003 SECTION "Appendix C -- Writing guile Scripts" [115560-115628] -->
+<h1 class="sectionedit1004"><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>
@@ -3402,15 +3484,17 @@ To be supplied…
</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:
+
+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 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:
+
+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>
@@ -3420,8 +3504,8 @@ To be supplied…
</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>
+<!-- EDIT1004 SECTION "Appendix D -- I Want To Build A Printed Circuit Board" [115629-116418] -->
+<h1 class="sectionedit1005"><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>
@@ -3435,17 +3519,19 @@ To be supplied…
</ul>
<p>
- The following guidelines will assist you in developing quality designs intended for simulation:
+
+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 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:
+
+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>
@@ -3455,22 +3541,24 @@ To be supplied…
</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>
+<!-- EDIT1005 SECTION "Appendix E -- I Want To Simulate My Design" [116419-117298] -->
+<h1 class="sectionedit1006"><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 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 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;
+
+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
#
@@ -3480,21 +3568,21 @@ 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.
+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>
+<!-- EDIT1006 SECTION "Appendix F -- Change gschemdoc User-Defined Preferences" [117299-118515] -->
+<h1 class="sectionedit1007"><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…
+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>
+<!-- EDIT1007 SECTION "Appendix G -- Breaking a Large Symbol Into Smaller Symbols" [118516-118607] -->
+<h1 class="sectionedit1008"><a name="appendix_h_--_definition_of_terms" id="appendix_h_--_definition_of_terms">Appendix H -- Definition of Terms</a></h1>
<div class="level1">
<p>
@@ -3503,43 +3591,43 @@ Some terms used in the art of schematic capture:</p>
<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>
+<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>
+<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>
+<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>
+<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>
+<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>
+<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>
+<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>
+<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>
@@ -3557,17 +3645,18 @@ Some terms used in the art of schematic capture:</p>
<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>
+<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>
+<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>~~DISCUSSION~~
+
</p>
</div>
-<!-- SECTION "Appendix H -- Definition of Terms" [118639-] --></body>
+<!-- EDIT1008 SECTION "Appendix H -- Definition of Terms" [118608-] --></body>
</html>
diff --git a/docs/wiki/geda-gschem_ug.html b/docs/wiki/geda-gschem_ug.html
index 37fdbeb..95ef68b 100644
--- a/docs/wiki/geda-gschem_ug.html
+++ b/docs/wiki/geda-gschem_ug.html
@@ -11,213 +11,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>
+
+<h1 class="sectionedit1010"><a name="geda_gschem_user_guide" id="geda_gschem_user_guide">gEDA gschem User Guide</a></h1>
<div class="level1">
<p>
@@ -233,12 +28,13 @@ This document is released under the <a href="geda-gfdl.html" class="wikilink1" t
</p>
<p>
- Please report any errors/inconsistencies in this document by commenting in the Discussion area at the bottom of the associated page.
+
+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>
+<!-- EDIT1010 SECTION "gEDA gschem User Guide" [1-397] -->
+<h1 class="sectionedit1011"><a name="about_this_document" id="about_this_document">About this document ...</a></h1>
<div class="level1">
<p>
@@ -250,11 +46,13 @@ This document was generated using the LaTeX2HTML translator Version 2002-2-1 (1.
</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.
+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
+The command line arguments were:
+latex2html -local_icons gschem
</p>
<p>
@@ -262,13 +60,14 @@ 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>
+<!-- EDIT1011 SECTION "About this document ..." [398-873] -->
+<h1 class="sectionedit1012"><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:
+
+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>
@@ -292,12 +91,13 @@ This document describes the installation, configuration, and operation of the <s
</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>.
+
+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>
+<!-- EDIT1012 SECTION "Introduction" [874-2809] -->
+<h1 class="sectionedit1013"><a name="overview" id="overview">Overview</a></h1>
<div class="level1">
<p>
@@ -313,12 +113,13 @@ This document describes the installation, configuration, and operation of the <s
</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:
+
+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 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>
+<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>
@@ -336,41 +137,41 @@ This document describes the installation, configuration, and operation of the <s
</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 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 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 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 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 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 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 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>
+<div class="table sectionedit1014"><table class="inline">
+ <tr class="row0">
+ <td class="col0"> <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>
-
+</table></div>
+<!-- EDIT1014 TABLE [5353-5389] -->
</div>
-<!-- SECTION "Overview" [2810-5392] -->
-<h1><a name="resources" id="resources">Resources</a></h1>
+<!-- EDIT1013 SECTION "Overview" [2810-5392] -->
+<h1 class="sectionedit1015"><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 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 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>
+<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>
@@ -380,49 +181,50 @@ The following on-line resources are useful for designers using <strong>gschem</s
</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 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 class="level1"><div class="li"> <a href="https://bugs.launchpad.net/geda"; class="urlextern" title="https://bugs.launchpad.net/geda"; rel="nofollow">gEDA Bug Tracker</a> â?? On Launchpad</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 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 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 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 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 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>
+<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 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 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 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>
+<!-- EDIT1015 SECTION "Resources" [5393-8589] -->
+<h1 class="sectionedit1016"><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):
+
+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 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 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>
@@ -436,7 +238,7 @@ The following on-line resources are useful for designers using <strong>gschem</s
</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 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>
@@ -447,8 +249,8 @@ The following on-line resources are useful for designers using <strong>gschem</s
</ol>
</div>
-<!-- SECTION "How To Ask Questions" [8620-11789] -->
-<h1><a name="installing_gschem" id="installing_gschem">Installing gschem</a></h1>
+<!-- EDIT1016 SECTION "How To Ask Questions" [8590-11759] -->
+<h1 class="sectionedit1017"><a name="installing_gschem" id="installing_gschem">Installing gschem</a></h1>
<div class="level1">
<p>
@@ -456,18 +258,20 @@ As a mature OpenSource project, the gEDA Tools Suite and its components have bee
</p>
</div>
-<!-- SECTION "Installing gschem" [11790-12048] -->
-<h2><a name="latest_stable" id="latest_stable">Latest Stable</a></h2>
+<!-- EDIT1017 SECTION "Installing gschem" [11760-12018] -->
+<h2 class="sectionedit1018"><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.
+<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>
+<!-- EDIT1018 SECTION "Latest Stable" [12019-12505] -->
+<h3 class="sectionedit1019"><a name="geda_binary_suite" id="geda_binary_suite">gEDA Binary Suite</a></h3>
<div class="level3">
<p>
@@ -483,8 +287,8 @@ Please read the <a href="http://geda.seul.org/dist/suite/v0.0.2/README"; class="u
</p>
</div>
-<!-- SECTION "gEDA Binary Suite" [12536-12991] -->
-<h3><a name="debian_based_distributions" id="debian_based_distributions">Debian based distributions</a></h3>
+<!-- EDIT1019 SECTION "gEDA Binary Suite" [12506-12961] -->
+<h3 class="sectionedit1020"><a name="debian_based_distributions" id="debian_based_distributions">Debian based distributions</a></h3>
<div class="level3">
<p>
@@ -492,8 +296,8 @@ For Debian distributions, you may wish to download the <a href="http://www.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>
+<!-- EDIT1020 SECTION "Debian based distributions" [12962-13222] -->
+<h3 class="sectionedit1021"><a name="fedora_and_redhat_distributions" id="fedora_and_redhat_distributions">Fedora and RedHat distributions</a></h3>
<div class="level3">
<p>
@@ -505,16 +309,17 @@ Since Fedora Core 5, major parts of gEDA are available from <a href="http://fedo
</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>.
+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>
+<!-- EDIT1021 SECTION "Fedora and RedHat distributions" [13223-13628] -->
+<h3 class="sectionedit1022"><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.
+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>
@@ -526,8 +331,8 @@ For more informations read the <a href="geda-suse_rpm_installation.html" class="
</p>
</div>
-<!-- SECTION "SuSE and OpenSuSE distributions" [13659-14130] -->
-<h3><a name="mac_osx_distributions" id="mac_osx_distributions">Mac OSX distributions</a></h3>
+<!-- EDIT1022 SECTION "SuSE and OpenSuSE distributions" [13629-14100] -->
+<h3 class="sectionedit1023"><a name="mac_osx_distributions" id="mac_osx_distributions">Mac OSX distributions</a></h3>
<div class="level3">
<p>
@@ -535,13 +340,14 @@ For Mac OSX distributions you may wish to download the <a href="http://www.geda.
</p>
</div>
-<!-- SECTION "Mac OSX distributions" [14131-14311] -->
-<h2><a name="developer_unstable_testing" id="developer_unstable_testing">Developer Unstable/Testing</a></h2>
+<!-- EDIT1023 SECTION "Mac OSX distributions" [14101-14281] -->
+<h2 class="sectionedit1024"><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:
+
+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>
@@ -551,40 +357,42 @@ For those already familiar with the gEDA/gaf applications, access to the develop
</ul>
</div>
-<!-- SECTION "Developer Unstable/Testing" [14312-15197] -->
-<h1><a name="configuring_gschem" id="configuring_gschem">Configuring gschem</a></h1>
+<!-- EDIT1024 SECTION "Developer Unstable/Testing" [14282-15167] -->
+<h1 class="sectionedit1025"><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;
+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/>
+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):
+
+<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 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 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>
+(load (build-path geda-rc-path "gschem-colormap-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 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>
@@ -597,65 +405,71 @@ margin-left : 2em"><font size="+0">; Comment in this scheme code if you want aut
(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 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 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 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:
+
+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 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 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 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>
+<!-- EDIT1025 SECTION "Configuring gschem" [15168-20950] -->
+<h2 class="sectionedit1026"><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:
+
+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>
+<!-- EDIT1026 SECTION "gschemrc" [20951-21252] -->
+<h2 class="sectionedit1027"><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:
+
+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>
+<!-- EDIT1027 SECTION "gafrc" [21253-21542] -->
+<h1 class="sectionedit1028"><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>
+<!-- EDIT1028 SECTION "Running gschem" [21543-21574] -->
+<h2 class="sectionedit1029"><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:
+
+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>
@@ -705,7 +519,8 @@ margin-left : 2em"><font size="+0">% <strong>echo $PATH</strong>
</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).
+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>
@@ -715,15 +530,17 @@ The <strong>echo $PATH</strong> command displays the userâ??s current setting fo
</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.
+
+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.
+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;
+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
@@ -746,65 +563,70 @@ If these commands do not return the expected results, then most likely the gEDA
</p>
</div>
-<!-- SECTION "Confirming gschem is installed" [21596-27003] -->
-<h2><a name="the_shell_prompt" id="the_shell_prompt">The Shell Prompt</a></h2>
+<!-- EDIT1029 SECTION "Confirming gschem is installed" [21575-26982] -->
+<h2 class="sectionedit1030"><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>
+<div class="table sectionedit1031"><table class="inline">
+ <tr class="row0">
+ <td class="col0"> <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 class="row1">
+ <td class="col0"> Figure 1 â?? gnome-terminal </td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT1031 TABLE [27012-27084] -->
<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:
+
+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 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 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 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 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 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 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 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 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/>
+
+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>
@@ -814,21 +636,21 @@ To open a specific schematic, run: <code><strong>% gschem schematic_name.sch</st
</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>
+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:
+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 class="level1"><div class="li"> â?¦</div>
</li>
</ul>
</div>
-<!-- SECTION "The Shell Prompt" [27004-30538] -->
-<h2><a name="backups" id="backups">Backups</a></h2>
+<!-- EDIT1030 SECTION "The Shell Prompt" [26983-30517] -->
+<h2 class="sectionedit1032"><a name="backups" id="backups">Backups</a></h2>
<div class="level2">
<p>
@@ -836,14 +658,17 @@ There are two basic mechanisms in <strong>gschem</strong> for backing up schemat
</p>
</div>
-<!-- SECTION "Backups" [30539-30690] -->
-<h3><a name="classic_linux_backups" id="classic_linux_backups">Classic Linux backups</a></h3>
+<!-- EDIT1032 SECTION "Backups" [30518-30669] -->
+<h3 class="sectionedit1033"><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;
+
+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}
@@ -863,41 +688,45 @@ Do you want to load the backup file?</font></pre>
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 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 class="level1"><div class="li"> add a â??#â?? to the end</div>
</li>
</ul>
<p>
- so that:
+
+so that:
</p>
<ul>
-<li class="level1"><div class="li"> â??schematic_1.schâ?? becomes "#schematic_1.sch#"</div>
+<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 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/>
+
+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.
+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>
+<!-- EDIT1033 SECTION "Classic Linux backups" [30670-33576] -->
+<h3 class="sectionedit1034"><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>
+<!-- EDIT1034 SECTION "Incremental backups" [33577-33610] -->
+<h3 class="sectionedit1035"><a name="relevant_configuration_settings" id="relevant_configuration_settings">Relevant configuration settings</a></h3>
<div class="level3">
<p>
@@ -915,13 +744,14 @@ There are the following configuration settings in the {binary-install-path}/shar
</ul>
</div>
-<!-- SECTION "Relevant configuration settings" [33632-34673] -->
-<h2><a name="on-line_documentation" id="on-line_documentation">On-line documentation</a></h2>
+<!-- EDIT1035 SECTION "Relevant configuration settings" [33611-34652] -->
+<h2 class="sectionedit1036"><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>
+The <code>-h</code> option to gschem provides a list of the various command line flags that gschem supports.
+<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
@@ -930,139 +760,45 @@ Usage: gschem [OPTIONS] schematic_filename1 ... schematic_filenameN
-o filename Output filename (for printing)
-p Automatically place the window
-t Print stroke information
+ -V Show version 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
+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></font></pre>
+</p>
- This document can be freely redistributed according to the terms of the
- GNU General Public License version 2.0
+<p>
+Access to this documentation can also be obtained directly from gschem's <strong>Help</strong> menu.
+</p>
+</div>
+<!-- EDIT1036 SECTION "On-line documentation" [34653-35431] -->
+<h1 class="sectionedit1037"><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.
+</p>
-Version December 31st, 2003 gschem(1)</font></pre>
+<p>
+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.
</p>
-</div>
-<!-- SECTION "On-line documentation" [34674-39143] -->
-<h1><a name="electrical_connectivity" id="electrical_connectivity">Electrical Connectivity</a></h1>
-<div class="level1">
+<p>
+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.
+</p>
<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.
+You can label nets by using the <code>netname=</code> attribute. Do not attach more than one <code>netname=</code> to a net. You only need to attach the <code>netname=</code> attribute to one net segment. Different nets (i.e. multiple net segments which arenâ??t connected together) which have the same attribute <code>netname=</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>netname=</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>
+<!-- EDIT1037 SECTION "Electrical Connectivity" [35432-37155] -->
+<h1 class="sectionedit1038"><a name="components_symbols_objects_attributes" id="components_symbols_objects_attributes">Components & Symbols & Objects & Attributes</a></h1>
<div class="level1">
<p>
@@ -1070,14 +806,16 @@ There is a hierarchical association between components, symbols, objects, and at
</p>
</div>
-<!-- SECTION "Components & Symbols & Objects & Attributes" [40861-41009] -->
-<h2><a name="components" id="components">Components</a></h2>
+<!-- EDIT1038 SECTION "Components & Symbols & Objects & Attributes" [37156-37304] -->
+<h2 class="sectionedit1039"><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:
+
+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>
@@ -1087,25 +825,30 @@ A component is the instantiation of a specific symbol, as placed on the schemati
</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.
+
+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>
+<!-- EDIT1039 SECTION "Components" [37305-39119] -->
+<h2 class="sectionedit1040"><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).
+
+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>
+<!-- EDIT1040 SECTION "Symbols" [39120-39461] -->
+<h2 class="sectionedit1041"><a name="objects" id="objects">Objects</a></h2>
<div class="level2">
<p>
@@ -1129,28 +872,30 @@ The following are objects:
</ul>
</div>
-<!-- SECTION "Objects" [43167-43280] -->
-<h2><a name="attributes" id="attributes">Attributes</a></h2>
+<!-- EDIT1041 SECTION "Objects" [39462-39575] -->
+<h2 class="sectionedit1042"><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:
+
+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 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 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:
+
+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 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>
@@ -1159,26 +904,36 @@ An attribute is text which is in the form <code>name=value</code> (there are no
</ul>
<p>
- Now, in order to make everybody happy, this attribute promotion behavior is configurable.<br/>
- The system-gschemrc file defines:
+
+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>
+<pre class="code lisp"><pre class="code lisp"><span class="br0">(</span>attribute-promotion <span class="st0">"enabled"</span><span class="br0">)</span></pre></pre>
+
<p>
which enables attribute promotion.<br/>
- If you override the system-gschemrcâ??s default promote-invisible setting by adding:
+
+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>
+<pre class="code lisp"><pre class="code lisp"><span class="br0">(</span>promote-invisible <span class="st0">"enabled"</span><span class="br0">)</span></pre></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>.
+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:
+
+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>
+<pre class="code lisp"><pre class="code lisp"><span class="br0">(</span>keep-invisible <span class="st0">"enabled"</span><span class="br0">)</span></pre></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.
+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>
@@ -1186,17 +941,18 @@ So, to summarize, attribute promotion takes unattached attributes inside symbols
</p>
</div>
-<!-- SECTION "Attributes" [43281-46653] -->
-<h1><a name="the_main_window" id="the_main_window">The Main Window</a></h1>
+<!-- EDIT1042 SECTION "Attributes" [39576-42948] -->
+<h1 class="sectionedit1043"><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>
+<div class="table sectionedit1044"><table class="inline">
+ <tr class="row0">
+ <td class="col0"> <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>
-
+</table></div>
+<!-- EDIT1044 TABLE [42979-43018] -->
<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:
+
+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>
@@ -1208,91 +964,100 @@ So, to summarize, attribute promotion takes unattached attributes inside symbols
</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).
+
+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>
+<!-- EDIT1043 SECTION "The Main Window" [42949-45862] -->
+<h1 class="sectionedit1045"><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>
+<div class="table sectionedit1046"><table class="inline">
+ <tr class="row0">
+ <td class="col0"> <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>
-
+</table></div>
+<!-- EDIT1046 TABLE [45895-45958] -->
<p>
- Add some details about what gets displayed in the status window.
+
+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>
+<!-- EDIT1045 SECTION "The Status Window" [45863-46025] -->
+<h1 class="sectionedit1047"><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:
+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 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.
+
+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>
+<!-- EDIT1047 SECTION "The Schematic File" [46026-46795] -->
+<h1 class="sectionedit1048"><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:
+
+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 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.
+
+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>
+<!-- EDIT1048 SECTION "The Symbol File" [46796-47782] -->
+<h1 class="sectionedit1049"><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.
+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>
+<!-- EDIT1049 SECTION "Symbol Libraries" [47783-47936] -->
+<h1 class="sectionedit1050"><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.
+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>
+<!-- EDIT1050 SECTION "The Log File" [47937-48214] -->
+<h1 class="sectionedit1051"><a name="grips" id="grips">Grips</a></h1>
<div class="level1">
<p>
@@ -1314,19 +1079,22 @@ Using grips is easy:
</ul>
</div>
-<!-- SECTION "Grips" [51920-52629] -->
-<h1><a name="menu_operations" id="menu_operations">Menu Operations</a></h1>
+<!-- EDIT1051 SECTION "Grips" [48215-48924] -->
+<h1 class="sectionedit1052"><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>
+<!-- EDIT1052 SECTION "Menu Operations" [48925-48954] -->
+<h2 class="sectionedit1053"><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;
+
+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}
@@ -1343,12 +1111,12 @@ margin-left : 2em"><font size="+0">WARNING: Found an autosave backup file:
</p>
<p>
-The following are available from the <strong>gschem</strong> main windowâ??s menu-bar when you expand <strong>File</strong>:
+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>
+<!-- EDIT1053 SECTION "File" [48955-50108] -->
+<h3 class="sectionedit1054"><a name="new_window_fw" id="new_window_fw">New Window (fw)</a></h3>
<div class="level3">
<p>
@@ -1356,8 +1124,8 @@ The following are available from the <strong>gschem</strong> main windowâ??s men
</p>
</div>
-<!-- SECTION "New Window (fw)" [53814-53979] -->
-<h3><a name="new_page_fn" id="new_page_fn">New Page (fn)</a></h3>
+<!-- EDIT1054 SECTION "New Window (fw)" [50109-50274] -->
+<h3 class="sectionedit1055"><a name="new_page_fn" id="new_page_fn">New Page (fn)</a></h3>
<div class="level3">
<p>
@@ -1365,13 +1133,14 @@ The following are available from the <strong>gschem</strong> main windowâ??s men
</p>
</div>
-<!-- SECTION "New Page (fn)" [53980-54167] -->
-<h3><a name="open_page..._fo" id="open_page..._fo">Open Page... (fo)</a></h3>
+<!-- EDIT1055 SECTION "New Page (fn)" [50275-50462] -->
+<h3 class="sectionedit1056"><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:
+<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>
@@ -1391,8 +1160,8 @@ The following are available from the <strong>gschem</strong> main windowâ??s men
</ul>
</div>
-<!-- SECTION "Open Page... (fo)" [54168-54455] -->
-<h3><a name="close_page_pc" id="close_page_pc">Close Page (pc)</a></h3>
+<!-- EDIT1056 SECTION "Open Page... (fo)" [50463-50750] -->
+<h3 class="sectionedit1057"><a name="close_page_pc" id="close_page_pc">Close Page (pc)</a></h3>
<div class="level3">
<p>
@@ -1400,8 +1169,8 @@ The following are available from the <strong>gschem</strong> main windowâ??s men
</p>
</div>
-<!-- SECTION "Close Page (pc)" [54456-54601] -->
-<h3><a name="revert_page_pr" id="revert_page_pr">Revert Page (pr)</a></h3>
+<!-- EDIT1057 SECTION "Close Page (pc)" [50751-50896] -->
+<h3 class="sectionedit1058"><a name="revert_page_pr" id="revert_page_pr">Revert Page (pr)</a></h3>
<div class="level3">
<p>
@@ -1409,17 +1178,19 @@ The following are available from the <strong>gschem</strong> main windowâ??s men
</p>
</div>
-<!-- SECTION "Revert Page (pr)" [54602-54863] -->
-<h3><a name="save_page_fs" id="save_page_fs">Save Page (fs)</a></h3>
+<!-- EDIT1058 SECTION "Revert Page (pr)" [50897-51158] -->
+<h3 class="sectionedit1059"><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:
+
+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 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>
@@ -1427,20 +1198,23 @@ The following are available from the <strong>gschem</strong> main windowâ??s men
</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>
+<!-- EDIT1059 SECTION "Save Page (fs)" [51159-51806] -->
+<h3 class="sectionedit1060"><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.
+<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>
+<!-- EDIT1060 SECTION "Save Page As... (fa)" [51807-52254] -->
+<h3 class="sectionedit1061"><a name="save_all_fl_fl" id="save_all_fl_fl">Save All (fl) (fl)</a></h3>
<div class="level3">
<p>
@@ -1448,13 +1222,14 @@ The following are available from the <strong>gschem</strong> main windowâ??s men
</p>
</div>
-<!-- SECTION "Save All (fl) (fl)" [55960-56064] -->
-<h3><a name="print..._fp" id="print..._fp">Print... (fp)</a></h3>
+<!-- EDIT1061 SECTION "Save All (fl) (fl)" [52255-52359] -->
+<h3 class="sectionedit1062"><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:
+<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>
@@ -1463,11 +1238,11 @@ The following are available from the <strong>gschem</strong> main windowâ??s men
</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 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 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 class="level2"><div class="li"> Current window â?? Scaled to fit the page size, but not optimally.</div>
</li>
</ul>
</li>
@@ -1482,8 +1257,10 @@ The following are available from the <strong>gschem</strong> main windowâ??s men
</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>
+
+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>
@@ -1491,13 +1268,14 @@ The following are available from the <strong>gschem</strong> main windowâ??s men
</div>
-<!-- SECTION "Print... (fp)" [56065-57111] -->
-<h3><a name="write_png..._fi" id="write_png..._fi">Write PNG... (fi)</a></h3>
+<!-- EDIT1062 SECTION "Print... (fp)" [52360-53406] -->
+<h3 class="sectionedit1063"><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:
+<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>
@@ -1518,27 +1296,29 @@ The following are available from the <strong>gschem</strong> main windowâ??s men
</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 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.).
+
+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>
+<!-- EDIT1063 SECTION "Write PNG... (fi)" [53407-54201] -->
+<h3 class="sectionedit1064"><a name="execute_script_ft" id="execute_script_ft">Execute Script... (ft)</a></h3>
<div class="level3">
<p>
-<strong>File | Execute Script…</strong> …..TBD
+<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>
+<!-- EDIT1064 SECTION "Execute Script... (ft)" [54202-54273] -->
+<h3 class="sectionedit1065"><a name="close_window_fc" id="close_window_fc">Close Window (fc)</a></h3>
<div class="level3">
<p>
@@ -1546,8 +1326,8 @@ The following are available from the <strong>gschem</strong> main windowâ??s men
</p>
</div>
-<!-- SECTION "Close Window (fc)" [57979-58217] -->
-<h3><a name="quit_alt-q" id="quit_alt-q">Quit (Alt-q)</a></h3>
+<!-- EDIT1065 SECTION "Close Window (fc)" [54274-54512] -->
+<h3 class="sectionedit1066"><a name="quit_alt-q" id="quit_alt-q">Quit (Alt-q)</a></h3>
<div class="level3">
<p>
@@ -1555,8 +1335,8 @@ The following are available from the <strong>gschem</strong> main windowâ??s men
</p>
</div>
-<!-- SECTION "Quit (Alt-q)" [58218-58410] -->
-<h2><a name="edit" id="edit">Edit</a></h2>
+<!-- EDIT1066 SECTION "Quit (Alt-q)" [54513-54705] -->
+<h2 class="sectionedit1067"><a name="edit" id="edit">Edit</a></h2>
<div class="level2">
<p>
@@ -1564,13 +1344,15 @@ The following are available from the <strong>gschem</strong> main windowâ??s men
</p>
</div>
-<!-- SECTION "Edit" [58411-58527] -->
-<h3><a name="undo_shift-u" id="undo_shift-u">Undo (shift-u)</a></h3>
+<!-- EDIT1067 SECTION "Edit" [54706-54822] -->
+<h3 class="sectionedit1068"><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;
+
+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
@@ -1581,13 +1363,14 @@ margin-left : 2em"><font size="+0">; undo-levels number
<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/>
+
+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>
+<!-- EDIT1068 SECTION "Undo (shift-u)" [54823-55781] -->
+<h3 class="sectionedit1069"><a name="redo_shift-r" id="redo_shift-r">Redo (shift-r)</a></h3>
<div class="level3">
<p>
@@ -1596,48 +1379,65 @@ After every action (including zooming and panning) the schematic is saved to dis
</p>
</div>
-<!-- SECTION "Redo (shift-r)" [59487-59795] -->
-<h3><a name="select_mode_s" id="select_mode_s">Select Mode (s)</a></h3>
+<!-- EDIT1069 SECTION "Redo (shift-r)" [55782-56090] -->
+<h3 class="sectionedit1070"><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.
+
+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>
+<!-- EDIT1070 SECTION "Select Mode (s)" [56091-58498] -->
+<h3 class="sectionedit1071"><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:
+
+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 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:
+
+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>
@@ -1659,23 +1459,27 @@ First, select the object to be edited (i.e., in <strong>Select Mode</strong>).<b
</ul>
<p>
- Apply the changes by pressing OK.
+
+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.
+
+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>
+<!-- EDIT1071 SECTION "Edit... (ee)" [58499-59693] -->
+<h3 class="sectionedit1072"><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:
+
+<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>
@@ -1697,22 +1501,25 @@ First, select the text object to be edited (i.e., in <strong>Select Mode</strong
</ul>
<p>
- Apply the changes by pressing OK.
+
+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.
+
+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>
+<!-- EDIT1072 SECTION "Edit Text... (ex)" [59694-60552] -->
+<h3 class="sectionedit1073"><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):
+
+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>
@@ -1732,20 +1539,24 @@ First, select the text object to be edited (i.e., in <strong>Select Mode</strong
</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/>
+
+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>
+<!-- EDIT1073 SECTION "Copy Mode (ec)" [60553-61477] -->
+<h3 class="sectionedit1074"><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):
+
+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>
@@ -1765,9 +1576,12 @@ First, select the text object to be edited (i.e., in <strong>Select Mode</strong
</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/>
+
+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>
@@ -1785,13 +1599,14 @@ Since version 20060906, there is another way to move object(s):<br/>
</ul>
</div>
-<!-- SECTION "Move Mode (em)" [65183-66336] -->
-<h3><a name="delete_delete-key" id="delete_delete-key">Delete (Delete-key)</a></h3>
+<!-- EDIT1074 SECTION "Move Mode (em)" [61478-62631] -->
+<h3 class="sectionedit1075"><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:
+
+To delete objects:
</p>
<ul>
<li class="level1"><div class="li"> Select the desired object(s) (i.e., in <strong>Select Mode</strong>)</div>
@@ -1801,17 +1616,19 @@ Since version 20060906, there is another way to move object(s):<br/>
</ul>
<p>
- The object(s) will be deleted immediately. If you inadvertantly delete a component, you can use Undo to recover.
+
+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>
+<!-- EDIT1075 SECTION "Delete (Delete-key)" [62632-62950] -->
+<h3 class="sectionedit1076"><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:
+
+To rotate objects:
</p>
<ul>
<li class="level1"><div class="li"> Select the desired object(s) (i.e., in <strong>Select Mode</strong>)</div>
@@ -1823,19 +1640,22 @@ Since version 20060906, there is another way to move object(s):<br/>
</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/>
+
+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>
+<!-- EDIT1076 SECTION "Rotate 90 Mode (er)" [62951-63540] -->
+<h3 class="sectionedit1077"><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:
+
+To mirror objects:
</p>
<ul>
<li class="level1"><div class="li"> Select the desired object(s) (i.e., in <strong>Select Mode</strong>)</div>
@@ -1847,25 +1667,30 @@ Since version 20060906, there is another way to move object(s):<br/>
</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.
+
+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>
+<!-- EDIT1077 SECTION "Mirror Mode (ei)" [63541-64197] -->
+<h3 class="sectionedit1078"><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):
+
+<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 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>
@@ -1874,22 +1699,24 @@ Some physical packages (e.g., the classic 7400 Quad NAND gate) contain more than
</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.
+
+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>
+<!-- EDIT1078 SECTION "Slot... (e shift-s)" [64198-65414] -->
+<h3 class="sectionedit1079"><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:
+<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 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>
@@ -1930,20 +1757,25 @@ Some physical packages (e.g., the classic 7400 Quad NAND gate) contain more than
</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.
+
+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>
+<!-- EDIT1079 SECTION "Color... (eo)" [65415-66373] -->
+<h3 class="sectionedit1080"><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:
+
+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>
@@ -1953,24 +1785,28 @@ Some physical packages (e.g., the classic 7400 Quad NAND gate) contain more than
</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.
+
+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>
+<!-- EDIT1080 SECTION "Lock (el) / Unlock (e shift-l)" [66374-67912] -->
+<h3 class="sectionedit1081"><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>:
+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 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>
@@ -1991,22 +1827,24 @@ The <strong>Edit | Line Width & Type…</strong> dialog box lets you co
</ul>
<p>
- Note that if the line width doesnâ??t seem to change, just pick a larger value.
+
+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>
+<!-- EDIT1081 SECTION "Line Width & Type... (ew)" [67913-68528] -->
+<h3 class="sectionedit1082"><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:
+<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 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>
@@ -2029,28 +1867,29 @@ The <strong>Edit | Line Width & Type…</strong> dialog box lets you co
</ul>
</div>
-<!-- SECTION "Fill Type... (ef)" [72234-72574] -->
-<h3><a name="symbol_translate..._et" id="symbol_translate..._et">Symbol Translate... (et)</a></h3>
+<!-- EDIT1082 SECTION "Fill Type... (ef)" [68529-68869] -->
+<h3 class="sectionedit1083"><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:
+<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 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 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 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>
@@ -2063,19 +1902,22 @@ The <strong>Edit | Line Width & Type…</strong> dialog box lets you co
</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/>
+
+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>
+<!-- EDIT1083 SECTION "Symbol Translate... (et)" [68870-70034] -->
+<h3 class="sectionedit1084"><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>:
+
+To <strong>Embed Component/Picture</strong>:
</p>
<ul>
<li class="level1"><div class="li"> Select the component/picture (in <strong>Select Mode</strong>)</div>
@@ -2085,19 +1927,24 @@ The <strong>Edit | Line Width & Type…</strong> dialog box lets you co
</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).
+
+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>
+<!-- EDIT1084 SECTION "Embed Component/Picture (eb)" [70035-71064] -->
+<h3 class="sectionedit1085"><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>:
+<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>
@@ -2107,42 +1954,48 @@ The <strong>Edit | Line Width & Type…</strong> dialog box lets you co
</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.
+
+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>
+<!-- EDIT1085 SECTION "Unembed Component/Picture (eu)" [71065-71654] -->
+<h3 class="sectionedit1086"><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:
+<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 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 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 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 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:
+
+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>
@@ -2152,16 +2005,20 @@ The <strong>Edit | Line Width & Type…</strong> dialog box lets you co
</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>
+<!-- EDIT1086 SECTION "Update Component (ep)" [71655-73464] -->
+<h3 class="sectionedit1087"><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 :
+<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>
@@ -2209,22 +2066,29 @@ The <strong>Edit | Line Width & Type…</strong> dialog box lets you co
</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.
+
+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>
+<!-- EDIT1087 SECTION "Show/Hide Inv Text (en)" [73465-76292] -->
+<h3 class="sectionedit1088"><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:
+<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>
@@ -2234,13 +2098,15 @@ The <strong>Edit | Line Width & Type…</strong> dialog box lets you co
</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.
+
+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>
+<!-- EDIT1088 SECTION "Make Inv Text Vis (ev)" [76293-76956] -->
+<h2 class="sectionedit1089"><a name="buffer" id="buffer">Buffer</a></h2>
<div class="level2">
<p>
@@ -2248,8 +2114,8 @@ The <strong>Edit | Line Width & Type…</strong> dialog box lets you co
</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>
+<!-- EDIT1089 SECTION "Buffer" [76957-77076] -->
+<h3 class="sectionedit1090"><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>
@@ -2263,8 +2129,8 @@ To copy something into a buffer:
</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>
+<!-- EDIT1090 SECTION "Copy into 1/2/3/4/5 (yc)" [77077-77229] -->
+<h3 class="sectionedit1091"><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>
@@ -2272,8 +2138,8 @@ 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>
+<!-- EDIT1091 SECTION "Cut into 1/2/3/4/5 (yu)" [77230-77331] -->
+<h3 class="sectionedit1092"><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>
@@ -2295,28 +2161,30 @@ To paste a buffer into the current schematic:
</ol>
</div>
-<!-- SECTION "Paste from 1/2/3/4/5 (yp)" [81037-81390] -->
-<h2><a name="view" id="view">View</a></h2>
+<!-- EDIT1092 SECTION "Paste from 1/2/3/4/5 (yp)" [77332-77685] -->
+<h2 class="sectionedit1093"><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>
+<!-- EDIT1093 SECTION "View" [77686-77703] -->
+<h3 class="sectionedit1094"><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.
+
+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>
+<!-- EDIT1094 SECTION "Redraw (vr)" [77704-77954] -->
+<h3 class="sectionedit1095"><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:
+
+To pan the display:
</p>
<ul>
<li class="level1"><div class="li"> Select <strong>View | Pan</strong></div>
@@ -2326,50 +2194,61 @@ To paste a buffer into the current schematic:
</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;
+
+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;
+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;
+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;
+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;
+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;
+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.
+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>
+<!-- EDIT1095 SECTION "Pan (x)" [77955-79751] -->
+<h3 class="sectionedit1096"><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>:
+
+To use <strong>View | Zoom Box</strong>:
</p>
<ul>
<li class="level1"><div class="li"> Select <strong>View | Zoom Box</strong></div>
@@ -2385,18 +2264,21 @@ to either your userâ??s ~/gschemrc file or local â??pwdâ??/gschemrc file, whenev
</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.
+
+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>
+<!-- EDIT1096 SECTION "Zoom Box (w)" [79752-80632] -->
+<h3 class="sectionedit1097"><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:
+
+To view all of the current window's objects:
</p>
<ul>
<li class="level1"><div class="li"> Select <strong>View | Extents</strong></div>
@@ -2404,18 +2286,20 @@ to either your userâ??s ~/gschemrc file or local â??pwdâ??/gschemrc file, whenev
</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/>
+
+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>
+<!-- EDIT1097 SECTION "Zoom Extents (ve)" [80633-80999] -->
+<h3 class="sectionedit1098"><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:
+
+To zoom in:
</p>
<ul>
<li class="level1"><div class="li"> Select <strong>View | Zoom In</strong></div>
@@ -2423,18 +2307,22 @@ to either your userâ??s ~/gschemrc file or local â??pwdâ??/gschemrc file, whenev
</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;
+
+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;
+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:
+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>
@@ -2444,17 +2332,19 @@ in either your userâ??s ~/gschemrc file or local â??pwdâ??/gschemrc file, whenev
</ul>
<p>
- Typing â??<strong>z</strong>â?? is particularly convenient for those that have learned to navigate the schematics using the shortcuts.
+
+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>
+<!-- EDIT1098 SECTION "Zoom In (z)" [81000-82161] -->
+<h3 class="sectionedit1099"><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:
+
+To zoom out:
</p>
<ul>
<li class="level1"><div class="li"> Select <strong>View | Zoom Out</strong></div>
@@ -2462,18 +2352,22 @@ in either your userâ??s ~/gschemrc file or local â??pwdâ??/gschemrc file, whenev
</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;
+
+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;
+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:
+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>
@@ -2483,12 +2377,13 @@ in either your userâ??s ~/gschemrc file or local â??pwdâ??/gschemrc file, whenev
</ul>
<p>
- Typing â??<strong>Z</strong>â?? is particularly convenient for those that have learned to navigate the schematics using the shortcuts.
+
+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>
+<!-- EDIT1099 SECTION "Zoom Out (Z)" [82162-83350] -->
+<h3 class="sectionedit1100"><a name="zoom_full_vf" id="zoom_full_vf">Zoom Full (vf)</a></h3>
<div class="level3">
<p>
@@ -2505,7 +2400,8 @@ To view the maximum displayable area:
</ul>
<p>
- The window contents will immediately change to show the maximum possible displayable view.<br/>
+
+The window contents will immediately change to show the maximum possible displayable view.<br/>
</p>
@@ -2518,7 +2414,8 @@ To view the maximum displayable area using the keyboard shortcut (i.e., â??<stro
</ul>
<p>
- The window contents will immediately change to show the maximum possible displayable view.<br/>
+
+The window contents will immediately change to show the maximum possible displayable view.<br/>
</p>
@@ -2527,61 +2424,62 @@ To view the maximum displayable area using the keyboard shortcut (i.e., â??<stro
</p>
</div>
-<!-- SECTION "Zoom Full (vf)" [87056-87834] -->
-<h2><a name="page" id="page">Page</a></h2>
+<!-- EDIT1100 SECTION "Zoom Full (vf)" [83351-84129] -->
+<h2 class="sectionedit1101"><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>
+<!-- EDIT1101 SECTION "Page" [84130-84148] -->
+<h3 class="sectionedit1102"><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>
+<!-- EDIT1102 SECTION "Manager... (pm)" [84149-84176] -->
+<h3 class="sectionedit1103"><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>
+<!-- EDIT1103 SECTION "Next (>)" [84177-84197] -->
+<h3 class="sectionedit1104"><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>
+<!-- EDIT1104 SECTION "Previous (<)" [84198-84222] -->
+<h3 class="sectionedit1105"><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>
+<!-- EDIT1105 SECTION "New (pe)" [84223-84243] -->
+<h3 class="sectionedit1106"><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>
+<!-- EDIT1106 SECTION "Revert (pr)" [84244-84267] -->
+<h3 class="sectionedit1107"><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>
+<!-- EDIT1107 SECTION "Close (pc)" [84268-84290] -->
+<h3 class="sectionedit1108"><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>
+<!-- EDIT1108 SECTION "Discard (pd)" [84291-84315] -->
+<h2 class="sectionedit1109"><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>
+<!-- EDIT1109 SECTION "Add" [84316-84332] -->
+<h3 class="sectionedit1110"><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:
+<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 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>
@@ -2600,10 +2498,14 @@ To view the maximum displayable area using the keyboard shortcut (i.e., â??<stro
</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:
+
+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>
@@ -2617,18 +2519,21 @@ To view the maximum displayable area using the keyboard shortcut (i.e., â??<stro
</ul>
<p>
- It helps to preview the symbol in the â??Select Componentâ?? dialog box before selecting and placing the symbol.
+
+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>
+<!-- EDIT1110 SECTION "Component... (i)" [84333-85809] -->
+<h3 class="sectionedit1111"><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:
+
+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>
@@ -2638,41 +2543,45 @@ To view the maximum displayable area using the keyboard shortcut (i.e., â??<stro
<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>
+<div class="table sectionedit1112"><table class="inline">
+ <tr class="row0">
+ <td class="col0"> <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>
-
+</table></div>
+<!-- EDIT1112 TABLE [86157-86179] -->
<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:
+
+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 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 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:
+
+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 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 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):
+
+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>
@@ -2694,37 +2603,47 @@ To view the maximum displayable area using the keyboard shortcut (i.e., â??<stro
</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.
+
+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>
+<!-- EDIT1111 SECTION "Net (n)" [85810-88401] -->
+<h3 class="sectionedit1113"><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.
+
+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>
+<!-- EDIT1113 SECTION "Bus (u)" [88402-88651] -->
+<h3 class="sectionedit1114"><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:
+<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 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>
@@ -2737,24 +2656,29 @@ To view the maximum displayable area using the keyboard shortcut (i.e., â??<stro
</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.
+
+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>
+<!-- EDIT1114 SECTION "Attribute... (aa)" [88652-90364] -->
+<h3 class="sectionedit1115"><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:
+<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 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 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>
@@ -2764,37 +2688,45 @@ To view the maximum displayable area using the keyboard shortcut (i.e., â??<stro
</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 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:
+
+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>
+<pre class="code lisp"><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>
+<span class="co1">; output-text : Controls how text is rendered to postscript</span></pre></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/>
+
+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>
+<!-- EDIT1115 SECTION "Text... (at)" [90365-92168] -->
+<h3 class="sectionedit1116"><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:
+
+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 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>
@@ -2813,7 +2745,8 @@ Text which is placed will be automatically capitalized. Please see the Resource
</ul>
<p>
- <strong>Add | Line</strong> draws a line in the same fashion as drawing nets with the following exceptions:
+
+<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>
@@ -2825,19 +2758,21 @@ Text which is placed will be automatically capitalized. Please see the Resource
</ul>
<p>
- To cancel a line in progress, press the last mouse button or type the ESC key.
+
+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>
+<!-- EDIT1116 SECTION "Line (l)" [92169-93255] -->
+<h3 class="sectionedit1117"><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:
+<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 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>
@@ -2854,21 +2789,24 @@ Text which is placed will be automatically capitalized. Please see the Resource
</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.
+
+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>
+<!-- EDIT1117 SECTION "Box (b)" [93256-94008] -->
+<h3 class="sectionedit1118"><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:
+
+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 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>
@@ -2885,21 +2823,24 @@ Text which is placed will be automatically capitalized. Please see the Resource
</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/>
+
+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>
+<!-- EDIT1118 SECTION "Circle (ai)" [94009-94893] -->
+<h3 class="sectionedit1119"><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:
+<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 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>
@@ -2911,7 +2852,7 @@ Text which is placed will be automatically capitalized. Please see the Resource
</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 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>
@@ -2922,22 +2863,26 @@ Text which is placed will be automatically capitalized. Please see the Resource
</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.
+
+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>
+<!-- EDIT1119 SECTION "Arc (ar)" [94894-95986] -->
+<h3 class="sectionedit1120"><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:
+
+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 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>
@@ -2956,19 +2901,21 @@ Text which is placed will be automatically capitalized. Please see the Resource
</ul>
<p>
- To cancel a pin in progress, press the last mouse button or the ESC key.
+
+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>
+<!-- EDIT1120 SECTION "Pin (ap)" [95987-97174] -->
+<h3 class="sectionedit1121"><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:
+<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 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>
@@ -2989,24 +2936,28 @@ Text which is placed will be automatically capitalized. Please see the Resource
</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.
+
+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>
+<!-- EDIT1121 SECTION "Picture... (ag)" [97175-98170] -->
+<h2 class="sectionedit1122"><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>
+<!-- EDIT1122 SECTION "Hierarchy" [98171-98193] -->
+<h3 class="sectionedit1123"><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:
+
+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>
@@ -3016,24 +2967,28 @@ Text which is placed will be automatically capitalized. Please see the Resource
</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)
+
+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>
+<!-- EDIT1123 SECTION "Down Schematic (Hd)" [98194-99806] -->
+<h3 class="sectionedit1124"><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.
+
+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>
+<!-- EDIT1124 SECTION "Down Symbol (Hs)" [99807-100129] -->
+<h3 class="sectionedit1125"><a name="up_hu" id="up_hu">Up (Hu)</a></h3>
<div class="level3">
<p>
@@ -3041,33 +2996,40 @@ This option will move up the hierarchy (if there are pages above the currently d
</p>
</div>
-<!-- SECTION "Up (Hu)" [103835-103949] -->
-<h3><a name="documentation_ho" id="documentation_ho">Documentation (Ho)</a></h3>
+<!-- EDIT1125 SECTION "Up (Hu)" [100130-100244] -->
+<h3 class="sectionedit1126"><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.
+
+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>
+<!-- EDIT1126 SECTION "Documentation (Ho)" [100245-101329] -->
+<h2 class="sectionedit1127"><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>
+<!-- EDIT1127 SECTION "Attributes" [101330-101353] -->
+<h3 class="sectionedit1128"><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:
+
+To use Attributes/Attach:
</p>
<ol>
<li class="level1"><div class="li"> Select the object which will receive the attributes</div>
@@ -3079,18 +3041,21 @@ The Attach command allows you to take a text item (in the proper form; <code>nam
</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.
+
+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>
+<!-- EDIT1128 SECTION "Attach (ta)" [101354-102161] -->
+<h3 class="sectionedit1129"><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:
+
+To deselect an object of all attributes:
</p>
<ol>
<li class="level1"><div class="li"> Select the object of interest</div>
@@ -3100,18 +3065,21 @@ Detach allows you to deassociate attributes from objects.<br/>
</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).
+
+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>
+<!-- EDIT1129 SECTION "Detach (td)" [102162-102768] -->
+<h3 class="sectionedit1130"><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:
+
+To use the options:
</p>
<ol>
<li class="level1"><div class="li"> Select the attribute(s) of interest</div>
@@ -3121,18 +3089,21 @@ These operations allow you to control which part of the attribute string is visi
</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>
+
+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>
+<!-- EDIT1130 SECTION "Show Value (tv)" [102769-103307] -->
+<h3 class="sectionedit1131"><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:
+
+To use the options:
</p>
<ol>
<li class="level1"><div class="li"> Select the attribute(s) of interest</div>
@@ -3142,18 +3113,21 @@ These operations allow you to control which part of the attribute string is visi
</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>
+
+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>
+<!-- EDIT1131 SECTION "Show Name (tn)" [103308-103845] -->
+<h3 class="sectionedit1132"><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:
+
+To use the options:
</p>
<ol>
<li class="level1"><div class="li"> Select the attribute(s) of interest</div>
@@ -3163,18 +3137,21 @@ These operations allow you to control which part of the attribute string is visi
</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>
+
+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>
+<!-- EDIT1132 SECTION "Show Both (tb)" [103846-104383] -->
+<h3 class="sectionedit1133"><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:
+
+To use this option:
</p>
<ol>
<li class="level1"><div class="li"> Select the text item(s) of interest</div>
@@ -3184,18 +3161,22 @@ This operation allows you to toggle the visibility of attributes.<br/>
</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.
+
+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>
+<!-- EDIT1133 SECTION "Toggle Visibility (tt)" [104384-105079] -->
+<h3 class="sectionedit1134"><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.
+
+This operation allows you to find a text element in a schematic.
</p>
<p>
@@ -3211,20 +3192,23 @@ To use this operation:
</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.
+
+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.
+<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>
+<!-- EDIT1134 SECTION "Find Specific Text... (t shift-f)" [105080-105740] -->
+<h3 class="sectionedit1135"><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.
+
+This operation allows you to hide text elements.
</p>
<p>
@@ -3238,7 +3222,8 @@ To use this operation:
</ol>
<p>
- gschem will hide all text elements that start with the given search string.
+
+gschem will hide all text elements that start with the given search string.
</p>
<p>
@@ -3246,12 +3231,13 @@ This operation is useful if you like to hide pintype and pinseq attributes when
</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>
+<!-- EDIT1135 SECTION "Hide Specific Text... (th)" [105741-106102] -->
+<h3 class="sectionedit1136"><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.
+
+This operation allows you to show hidden text elements.
</p>
<p>
@@ -3265,20 +3251,23 @@ To use this operation:
</ol>
<p>
- gschem will unhide all hidden text elements that starts with the given search string.
+
+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.
+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>
+<!-- EDIT1136 SECTION "Show Specific Text... (t shift-h)" [106103-106594] -->
+<h3 class="sectionedit1137"><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.
+
+This operation allows you to renumber text elements in your schematics and symbols.
</p>
<p>
@@ -3294,14 +3283,16 @@ You can use it to:
</ul>
<p>
- To use that operation:
+
+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 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 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>
@@ -3316,27 +3307,29 @@ You can use it to:
</ol>
<p>
- Pressing the apply button will start the autonumbering action.
+
+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>
+<!-- EDIT1137 SECTION "Autonumber Text... (tu)" [106595-109032] -->
+<h2 class="sectionedit1138"><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>
+<!-- EDIT1138 SECTION "Options" [109033-109053] -->
+<h3 class="sectionedit1139"><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.
+<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>
+<!-- EDIT1139 SECTION "Text Size... (ot)" [109054-109366] -->
+<h3 class="sectionedit1140"><a name="toggle_grid_on_off_og" id="toggle_grid_on_off_og">Toggle Grid On/Off (og)</a></h3>
<div class="level3">
<p>
@@ -3344,29 +3337,32 @@ You can use it to:
</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>
+<!-- EDIT1140 SECTION "Toggle Grid On/Off (og)" [109367-109460] -->
+<h3 class="sectionedit1141"><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.
+
+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>
+<!-- EDIT1141 SECTION "Toggle Snap On/Off (os)" [109461-109912] -->
+<h3 class="sectionedit1142"><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.
+<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>
+<!-- EDIT1142 SECTION "Snap Grid Spacing... (oS)" [109913-110216] -->
+<h3 class="sectionedit1143"><a name="toggle_outline_box_oa" id="toggle_outline_box_oa">Toggle Outline/Box (oa)</a></h3>
<div class="level3">
<p>
@@ -3374,17 +3370,17 @@ You can use it to:
</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>
+<!-- EDIT1143 SECTION "Toggle Outline/Box (oa)" [110217-110526] -->
+<h3 class="sectionedit1144"><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> …..????
+<strong>Options | Toggle Net/Rubberband</strong> This option makes the nets stick to the pins of symbols. It is on by default. When switched off, symbols don't drag on nets when moved.
</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>
+<!-- EDIT1144 SECTION "Toggle Net/Rubberband (or)" [110527-110738] -->
+<h3 class="sectionedit1145"><a name="show_log_window_ol" id="show_log_window_ol">Show Log Window (ol)</a></h3>
<div class="level3">
<p>
@@ -3392,72 +3388,72 @@ You can use it to:
</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>
+<!-- EDIT1145 SECTION "Show Log Window (ol)" [110739-110909] -->
+<h3 class="sectionedit1146"><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.
+<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>
+<!-- EDIT1146 SECTION "Show Coord Window... (oc)" [110910-111114] -->
+<h2 class="sectionedit1147"><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>
+<!-- EDIT1147 SECTION "Help" [111115-111132] -->
+<h3 class="sectionedit1148"><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:
+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 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 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>
+<!-- EDIT1148 SECTION "About... (ha)" [111133-111335] -->
+<h3 class="sectionedit1149"><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.
+<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>
+<!-- EDIT1149 SECTION "Manual... (hm)" [111336-111549] -->
+<h3 class="sectionedit1150"><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).
+<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>
+<!-- EDIT1150 SECTION "Hotkeys... (hh)" [111550-111677] -->
+<h3 class="sectionedit1151"><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:
+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 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 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>
+<!-- EDIT1151 SECTION "Component... (Ho)" [111678-112460] -->
+<h1 class="sectionedit1152"><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>
@@ -3465,26 +3461,26 @@ A short discussion of Light Symbol Libraries as the default for <strong>gschem</
</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>
+<!-- EDIT1152 SECTION "Appendix A -- Heavy vs Light Symbol Libraries" [112461-112654] -->
+<h1 class="sectionedit1153"><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…
+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>
+<!-- EDIT1153 SECTION "Appendix B -- Printing Schematics and Symbols" [112655-112733] -->
+<h1 class="sectionedit1154"><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…
+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>
+<!-- EDIT1154 SECTION "Appendix C -- Writing guile Scripts" [112734-112802] -->
+<h1 class="sectionedit1155"><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>
@@ -3498,15 +3494,17 @@ To be supplied…
</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:
+
+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 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:
+
+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>
@@ -3516,8 +3514,8 @@ To be supplied…
</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>
+<!-- EDIT1155 SECTION "Appendix D -- I Want To Build A Printed Circuit Board" [112803-113592] -->
+<h1 class="sectionedit1156"><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>
@@ -3531,17 +3529,19 @@ To be supplied…
</ul>
<p>
- The following guidelines will assist you in developing quality designs intended for simulation:
+
+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 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:
+
+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>
@@ -3551,22 +3551,24 @@ To be supplied…
</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>
+<!-- EDIT1156 SECTION "Appendix E -- I Want To Simulate My Design" [113593-114472] -->
+<h1 class="sectionedit1157"><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 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 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;
+
+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
#
@@ -3576,21 +3578,21 @@ 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.
+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>
+<!-- EDIT1157 SECTION "Appendix F -- Change gschemdoc User-Defined Preferences" [114473-115689] -->
+<h1 class="sectionedit1158"><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…
+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>
+<!-- EDIT1158 SECTION "Appendix G -- Breaking a Large Symbol Into Smaller Symbols" [115690-115781] -->
+<h1 class="sectionedit1159"><a name="appendix_h_--_definition_of_terms" id="appendix_h_--_definition_of_terms">Appendix H -- Definition of Terms</a></h1>
<div class="level1">
<p>
@@ -3599,43 +3601,43 @@ Some terms used in the art of schematic capture:</p>
<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>
+<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>
+<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>
+<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>
+<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>
+<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>
+<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>
+<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>
+<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>
@@ -3653,17 +3655,18 @@ Some terms used in the art of schematic capture:</p>
<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>
+<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>
+<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>~~DISCUSSION~~
+
</p>
</div>
-<!-- SECTION "Appendix H -- Definition of Terms" [119359-] --></body>
+<!-- EDIT1159 SECTION "Appendix H -- Definition of Terms" [115782-] --></body>
</html>
diff --git a/docs/wiki/geda-gschem_warmup.html b/docs/wiki/geda-gschem_warmup.html
index b572695..81b4af5 100644
--- a/docs/wiki/geda-gschem_warmup.html
+++ b/docs/wiki/geda-gschem_warmup.html
@@ -12,13 +12,12 @@
<body>
-
-
-<h1><a name="gschem_warmup_for_beginners" id="gschem_warmup_for_beginners">gschem Warmup for Beginners</a></h1>
+<h1 class="sectionedit1161"><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:
+
+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>
@@ -26,10 +25,11 @@ You get an initial blank page with menus and a toolbar at the top. As you select
</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:
+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 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>
@@ -40,20 +40,22 @@ When drawing a schematic, Itâ??s a good idea to always start by setting some sch
</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>
+
+<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 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 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 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>
@@ -62,21 +64,24 @@ When drawing a schematic, Itâ??s a good idea to always start by setting some sch
</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>
+
+<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 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>
+
+<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.
+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>
@@ -86,12 +91,14 @@ it means you missed the pin on the right resistor. Look closely and youâ??ll see
</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.
+
+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)
+tutorial by Bill Wilson (billâ??atâ??gkrellm.net)
</p>
</div>
diff --git a/docs/wiki/geda-gsymcheck_mp.html b/docs/wiki/geda-gsymcheck_mp.html
index 4324138..1f83c8f 100644
--- a/docs/wiki/geda-gsymcheck_mp.html
+++ b/docs/wiki/geda-gsymcheck_mp.html
@@ -12,9 +12,7 @@
<body>
-
-
-<h1><a name="gsymcheck_man-page" id="gsymcheck_man-page">gsymcheck man-page</a></h1>
+<h1 class="sectionedit1178"><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)
@@ -79,8 +77,7 @@ COPYRIGHT
-Version December 31st, 2003 gsymcheck(1)
-</pre>
+Version December 31st, 2003 gsymcheck(1)</pre>
</div>
</body>
diff --git a/docs/wiki/geda-gtkwave_lxt2miner_mp.html b/docs/wiki/geda-gtkwave_lxt2miner_mp.html
index 2015f50..4523e58 100644
--- a/docs/wiki/geda-gtkwave_lxt2miner_mp.html
+++ b/docs/wiki/geda-gtkwave_lxt2miner_mp.html
@@ -12,9 +12,7 @@
<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>
+<h1 class="sectionedit1180"><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)
@@ -71,8 +69,7 @@ SEE ALSO
-Anthony Bybell 1.3.64 LXT2MINER(1)
-</pre>
+Anthony Bybell 1.3.64 LXT2MINER(1)</pre>
</div>
</body>
diff --git a/docs/wiki/geda-gtkwave_lxt2vcd_mp.html b/docs/wiki/geda-gtkwave_lxt2vcd_mp.html
index 0ea03ad..b570ce4 100644
--- a/docs/wiki/geda-gtkwave_lxt2vcd_mp.html
+++ b/docs/wiki/geda-gtkwave_lxt2vcd_mp.html
@@ -12,9 +12,7 @@
<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>
+<h1 class="sectionedit846"><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)
diff --git a/docs/wiki/geda-gtkwave_mp.html b/docs/wiki/geda-gtkwave_mp.html
index 74c42c8..16b9779 100644
--- a/docs/wiki/geda-gtkwave_mp.html
+++ b/docs/wiki/geda-gtkwave_mp.html
@@ -12,9 +12,7 @@
<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>
+<h1 class="sectionedit1179"><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)
diff --git a/docs/wiki/geda-gtkwave_mvl2lxt_mp.html b/docs/wiki/geda-gtkwave_mvl2lxt_mp.html
index 395911b..aa43916 100644
--- a/docs/wiki/geda-gtkwave_mvl2lxt_mp.html
+++ b/docs/wiki/geda-gtkwave_mvl2lxt_mp.html
@@ -12,9 +12,7 @@
<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>
+<h1 class="sectionedit11"><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)
diff --git a/docs/wiki/geda-gtkwave_mvl2vcd_mp.html b/docs/wiki/geda-gtkwave_mvl2vcd_mp.html
index 9725a35..a92ba65 100644
--- a/docs/wiki/geda-gtkwave_mvl2vcd_mp.html
+++ b/docs/wiki/geda-gtkwave_mvl2vcd_mp.html
@@ -12,9 +12,7 @@
<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>
+<h1 class="sectionedit27"><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)
@@ -38,8 +36,7 @@ SEE ALSO
-Anthony Bybell 1.3.34 MVL2VCD(1)
-</pre>
+Anthony Bybell 1.3.34 MVL2VCD(1)</pre>
</div>
</body>
diff --git a/docs/wiki/geda-gtkwave_tex2vcd_mp.html b/docs/wiki/geda-gtkwave_tex2vcd_mp.html
index 71825cd..18d33ba 100644
--- a/docs/wiki/geda-gtkwave_tex2vcd_mp.html
+++ b/docs/wiki/geda-gtkwave_tex2vcd_mp.html
@@ -12,9 +12,7 @@
<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>
+<h1 class="sectionedit190"><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)
diff --git a/docs/wiki/geda-gtkwave_tla2vcd_mp.html b/docs/wiki/geda-gtkwave_tla2vcd_mp.html
index 806b81c..4815986 100644
--- a/docs/wiki/geda-gtkwave_tla2vcd_mp.html
+++ b/docs/wiki/geda-gtkwave_tla2vcd_mp.html
@@ -12,9 +12,7 @@
<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>
+<h1 class="sectionedit216"><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)
diff --git a/docs/wiki/geda-gtkwave_vcd2lxt2_mp.html b/docs/wiki/geda-gtkwave_vcd2lxt2_mp.html
index 5b11ecf..12a1e8e 100644
--- a/docs/wiki/geda-gtkwave_vcd2lxt2_mp.html
+++ b/docs/wiki/geda-gtkwave_vcd2lxt2_mp.html
@@ -12,9 +12,7 @@
<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>
+<h1 class="sectionedit236"><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)
diff --git a/docs/wiki/geda-gtkwave_vcd2lxt_mp.html b/docs/wiki/geda-gtkwave_vcd2lxt_mp.html
index 2da6354..0f229de 100644
--- a/docs/wiki/geda-gtkwave_vcd2lxt_mp.html
+++ b/docs/wiki/geda-gtkwave_vcd2lxt_mp.html
@@ -12,9 +12,7 @@
<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>
+<h1 class="sectionedit277"><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)
diff --git a/docs/wiki/geda-gtkwave_vcd2vzt_mp.html b/docs/wiki/geda-gtkwave_vcd2vzt_mp.html
index 30df085..9b90e17 100644
--- a/docs/wiki/geda-gtkwave_vcd2vzt_mp.html
+++ b/docs/wiki/geda-gtkwave_vcd2vzt_mp.html
@@ -12,9 +12,7 @@
<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>
+<h1 class="sectionedit279"><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)
diff --git a/docs/wiki/geda-gtkwave_vzt2vcd_mp.html b/docs/wiki/geda-gtkwave_vzt2vcd_mp.html
index b5b3636..8b3e56e 100644
--- a/docs/wiki/geda-gtkwave_vzt2vcd_mp.html
+++ b/docs/wiki/geda-gtkwave_vzt2vcd_mp.html
@@ -12,9 +12,7 @@
<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>
+<h1 class="sectionedit281"><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)
diff --git a/docs/wiki/geda-gtkwave_vztminer_mp.html b/docs/wiki/geda-gtkwave_vztminer_mp.html
index 76771eb..b51687f 100644
--- a/docs/wiki/geda-gtkwave_vztminer_mp.html
+++ b/docs/wiki/geda-gtkwave_vztminer_mp.html
@@ -12,9 +12,7 @@
<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>
+<h1 class="sectionedit283"><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)
diff --git a/docs/wiki/geda-guile_scripting.html b/docs/wiki/geda-guile_scripting.html
index f807ac3..df250a2 100644
--- a/docs/wiki/geda-guile_scripting.html
+++ b/docs/wiki/geda-guile_scripting.html
@@ -11,32 +11,13 @@
</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" class="toc">Guile scripting</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#tutorials" class="toc">Tutorials</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#libgeda_c_library_reference" class="toc">libgeda C library reference</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" id="guile_scripting">Guile scripting</a></h2>
+<h2 class="sectionedit295"><a name="guile_scripting" id="guile_scripting">Guile scripting</a></h2>
<div class="level2">
</div>
-<!-- SECTION "Guile scripting" [1-31] -->
-<h3><a name="tutorials" id="tutorials">Tutorials</a></h3>
+<!-- EDIT295 SECTION "Guile scripting" [1-31] -->
+<h3 class="sectionedit296"><a name="tutorials" id="tutorials">Tutorials</a></h3>
<div class="level3">
<ul>
<li class="level1"><div class="li"> <a href="geda-gnetlist_scheme_tutorial.html" class="wikilink1" title="geda-gnetlist_scheme_tutorial.html">Scripting a gnetlist backend in scheme</a> (John Doty)</div>
@@ -46,12 +27,13 @@
</ul>
</div>
-<!-- SECTION "Tutorials" [32-249] -->
-<h3><a name="libgeda_c_library_reference" id="libgeda_c_library_reference">libgeda C library reference</a></h3>
+<!-- EDIT296 SECTION "Tutorials" [32-249] -->
+<h3 class="sectionedit297"><a name="libgeda_c_library_reference" id="libgeda_c_library_reference">libgeda C library reference</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.
+
+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>
@@ -73,7 +55,9 @@
<div class="level4">
<p>
- Basic configuration (defined by libgeda, read-only)
+
+Basic configuration (defined by libgeda, read-only)
+
</p>
<ul>
<li class="level1"><div class="li"> path-sep</div>
@@ -85,7 +69,9 @@
</ul>
<p>
- Object type identifiers (defined by libgeda, read-only)
+
+Object type identifiers (defined by libgeda, read-only)
+
</p>
<ul>
<li class="level1"><div class="li"> OBJ_LINE</div>
@@ -122,7 +108,9 @@
<div class="level4">
<p>
- Component library:
+
+Component library:
+
</p>
<ul>
<li class="level1"><div class="li"> component-library</div>
@@ -138,7 +126,9 @@
</ul>
<p>
- Subcircuit library:
+
+Subcircuit library:
+
</p>
<ul>
<li class="level1"><div class="li"> source-library</div>
@@ -150,7 +140,9 @@
</ul>
<p>
- Libgeda behaviour configuration (write-only):
+
+Libgeda behaviour configuration (write-only):
+
</p>
<ul>
<li class="level1"><div class="li"> always-promote-attributes</div>
@@ -180,7 +172,9 @@
</ul>
<p>
- Smob type manipulators:
+
+Smob type manipulators:
+
</p>
<ul>
<li class="level1"><div class="li"> get-attribute-name-value</div>
@@ -204,12 +198,13 @@
</ul>
</div>
-<!-- SECTION "libgeda C library reference" [250-1700] -->
-<h3><a name="libgeda_geda.scm" id="libgeda_geda.scm">libgeda geda.scm</a></h3>
+<!-- EDIT297 SECTION "libgeda C library reference" [250-1700] -->
+<h3 class="sectionedit298"><a name="libgeda_gedascm" id="libgeda_gedascm">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.
+
+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>
@@ -230,5 +225,5 @@
</ul>
</div>
-<!-- SECTION "libgeda geda.scm" [1701-] --></body>
+<!-- EDIT298 SECTION "libgeda geda.scm" [1701-] --></body>
</html>
diff --git a/docs/wiki/geda-howto_report_bugs.html b/docs/wiki/geda-howto_report_bugs.html
new file mode 100644
index 0000000..6f3c0a1
--- /dev/null
+++ b/docs/wiki/geda-howto_report_bugs.html
@@ -0,0 +1,48 @@
+<!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 class="sectionedit1443"><a name="howto_report_bugs" id="howto_report_bugs">Howto report bugs</a></h1>
+<div class="level1">
+
+</div>
+<!-- EDIT1443 SECTION "Howto report bugs" [1-33] -->
+<h2 class="sectionedit1444"><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 bug tracking system of the component (see below). 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>
+<!-- EDIT1444 SECTION "I found a bug! What can I do about it?" [34-907] -->
+<h2 class="sectionedit1445"><a name="bug_trackers" id="bug_trackers">Bug trackers</a></h2>
+<div class="level2">
+<ul>
+<li class="level1"><div class="li"> gaf (geschem, gnetlist, gsch2pcb, xgsch2pcb, gattrib, etc): <a href="https://bugs.launchpad.net/geda"; class="urlextern" title="https://bugs.launchpad.net/geda"; rel="nofollow">https://bugs.launchpad.net/geda</a></div>
+</li>
+<li class="level1"><div class="li"> pcb: <a href="https://bugs.launchpad.net/pcb"; class="urlextern" title="https://bugs.launchpad.net/pcb"; rel="nofollow">https://bugs.launchpad.net/pcb</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-bug_triage_guide.html" class="wikilink1" title="geda-bug_triage_guide.html">Bug Triage Guide</a></div>
+</li>
+</ul>
+
+</div>
+<!-- EDIT1445 SECTION "Bug trackers" [908-] --></body>
+</html>
diff --git a/docs/wiki/geda-hse_howto.html b/docs/wiki/geda-hse_howto.html
index d5f8744..2e0e076 100644
--- a/docs/wiki/geda-hse_howto.html
+++ b/docs/wiki/geda-hse_howto.html
@@ -12,9 +12,7 @@
<body>
-
-
-<h1><a name="hooks_scheme_extension_howto" id="hooks_scheme_extension_howto">Hooks/Scheme Extension HOWTO</a></h1>
+<h1 class="sectionedit302"><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
@@ -129,7 +127,6 @@ simply add the following line:
(add-hook! copy-component-hook auto-uref)
Good luck!
-
</pre>
</div>
diff --git a/docs/wiki/geda-icarus_anc.html b/docs/wiki/geda-icarus_anc.html
index 41bb037..0b5306d 100644
--- a/docs/wiki/geda-icarus_anc.html
+++ b/docs/wiki/geda-icarus_anc.html
@@ -12,9 +12,7 @@
<body>
-
-
-<h1><a name="icarus_attribute_naming_conventions" id="icarus_attribute_naming_conventions">Icarus Attribute Naming Conventions</a></h1>
+<h1 class="sectionedit307"><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
diff --git a/docs/wiki/geda-icarus_extensions.html b/docs/wiki/geda-icarus_extensions.html
index 0004418..5886b11 100644
--- a/docs/wiki/geda-icarus_extensions.html
+++ b/docs/wiki/geda-icarus_extensions.html
@@ -12,9 +12,7 @@
<body>
-
-
-<h1><a name="icarus_verilog_extensions" id="icarus_verilog_extensions">Icarus Verilog Extensions</a></h1>
+<h1 class="sectionedit321"><a name="icarus_verilog_extensions" id="icarus_verilog_extensions">Icarus Verilog Extensions</a></h1>
<div class="level1">
<pre class="code">Icarus Verilog Extensions
diff --git a/docs/wiki/geda-icarus_glossary.html b/docs/wiki/geda-icarus_glossary.html
index 53a519e..a446fc6 100644
--- a/docs/wiki/geda-icarus_glossary.html
+++ b/docs/wiki/geda-icarus_glossary.html
@@ -12,9 +12,7 @@
<body>
-
-
-<h1><a name="icarus_verilog_glossary" id="icarus_verilog_glossary">Icarus Verilog Glossary</a></h1>
+<h1 class="sectionedit326"><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
@@ -53,7 +51,6 @@ 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>
diff --git a/docs/wiki/geda-icarus_ieee1364.html b/docs/wiki/geda-icarus_ieee1364.html
index 89361ff..faadbb9 100644
--- a/docs/wiki/geda-icarus_ieee1364.html
+++ b/docs/wiki/geda-icarus_ieee1364.html
@@ -12,9 +12,7 @@
<body>
-
-
-<h1><a name="icarus_verilog_vs._ieee1364" id="icarus_verilog_vs._ieee1364">Icarus Verilog vs. IEEE1364</a></h1>
+<h1 class="sectionedit333"><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
diff --git a/docs/wiki/geda-icarus_mp.html b/docs/wiki/geda-icarus_mp.html
index f98d924..4f257a7 100644
--- a/docs/wiki/geda-icarus_mp.html
+++ b/docs/wiki/geda-icarus_mp.html
@@ -12,9 +12,7 @@
<body>
-
-
-<h1><a name="icarus_verilog_compiler_man-page" id="icarus_verilog_compiler_man-page">Icarus Verilog compiler man-page</a></h1>
+<h1 class="sectionedit362"><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)
diff --git a/docs/wiki/geda-icarus_opcodes.html b/docs/wiki/geda-icarus_opcodes.html
index 961e601..2021a54 100644
--- a/docs/wiki/geda-icarus_opcodes.html
+++ b/docs/wiki/geda-icarus_opcodes.html
@@ -12,9 +12,7 @@
<body>
-
-
-<h1><a name="executable_instruction_opcodes" id="executable_instruction_opcodes">Executable Instruction Opcodes</a></h1>
+<h1 class="sectionedit432"><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)
@@ -692,7 +690,7 @@ and leaves the result in the <dst> vector. xor is this:
*
* 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
+ * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
*/</pre>
</div>
diff --git a/docs/wiki/geda-icarus_quick_start.html b/docs/wiki/geda-icarus_quick_start.html
index 068bbf3..f05306f 100644
--- a/docs/wiki/geda-icarus_quick_start.html
+++ b/docs/wiki/geda-icarus_quick_start.html
@@ -12,9 +12,7 @@
<body>
-
-
-<h1><a name="getting_started_with_icarus_verilog" id="getting_started_with_icarus_verilog">Getting Started with Icarus Verilog</a></h1>
+<h1 class="sectionedit441"><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
diff --git a/docs/wiki/geda-icarus_readme.html b/docs/wiki/geda-icarus_readme.html
index 2ea4a48..db7dd02 100644
--- a/docs/wiki/geda-icarus_readme.html
+++ b/docs/wiki/geda-icarus_readme.html
@@ -12,9 +12,7 @@
<body>
-
-
-<h1><a name="the_icarus_verilog_compilation_system" id="the_icarus_verilog_compilation_system">The Icarus Verilog Compilation System</a></h1>
+<h1 class="sectionedit698"><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
diff --git a/docs/wiki/geda-icarus_vpi_mp.html b/docs/wiki/geda-icarus_vpi_mp.html
index f3a8a41..76e1cf1 100644
--- a/docs/wiki/geda-icarus_vpi_mp.html
+++ b/docs/wiki/geda-icarus_vpi_mp.html
@@ -12,9 +12,7 @@
<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>
+<h1 class="sectionedit766"><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)
diff --git a/docs/wiki/geda-icarus_vpi_within_vvp.html b/docs/wiki/geda-icarus_vpi_within_vvp.html
index 104378d..a734fc2 100644
--- a/docs/wiki/geda-icarus_vpi_within_vvp.html
+++ b/docs/wiki/geda-icarus_vpi_within_vvp.html
@@ -12,9 +12,7 @@
<body>
-
-
-<h1><a name="vpi_within_vvp" id="vpi_within_vvp">VPI_within_VVP</a></h1>
+<h1 class="sectionedit783"><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)
@@ -180,7 +178,7 @@ object.
*
* 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
+ * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
*/</pre>
</div>
diff --git a/docs/wiki/geda-icarus_vvp_runtime.html b/docs/wiki/geda-icarus_vvp_runtime.html
index 08277ee..cd00e5d 100644
--- a/docs/wiki/geda-icarus_vvp_runtime.html
+++ b/docs/wiki/geda-icarus_vvp_runtime.html
@@ -12,9 +12,7 @@
<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>
+<h1 class="sectionedit807"><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)
diff --git a/docs/wiki/geda-icarus_vvp_simulation.html b/docs/wiki/geda-icarus_vvp_simulation.html
index 5a0b660..8ec43b0 100644
--- a/docs/wiki/geda-icarus_vvp_simulation.html
+++ b/docs/wiki/geda-icarus_vvp_simulation.html
@@ -12,9 +12,7 @@
<body>
-
-
-<h1><a name="vvp_simulation_engine" id="vvp_simulation_engine">VVP Simulation Engine</a></h1>
+<h1 class="sectionedit809"><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)
@@ -1006,7 +1004,7 @@ generated. This is sufficient to trigger the event.
*
* 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
+ * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
*/</pre>
</div>
diff --git a/docs/wiki/geda-icarus_xilinx_hints.html b/docs/wiki/geda-icarus_xilinx_hints.html
index dc8b682..0a825b6 100644
--- a/docs/wiki/geda-icarus_xilinx_hints.html
+++ b/docs/wiki/geda-icarus_xilinx_hints.html
@@ -12,9 +12,7 @@
<body>
-
-
-<h1><a name="xilinx_hints" id="xilinx_hints">Xilinx Hints</a></h1>
+<h1 class="sectionedit843"><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
@@ -110,8 +108,7 @@ 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>
+ updated February 1, 2000</pre>
</div>
</body>
diff --git a/docs/wiki/geda-icarus_xnf.html b/docs/wiki/geda-icarus_xnf.html
index fefadfb..523fb49 100644
--- a/docs/wiki/geda-icarus_xnf.html
+++ b/docs/wiki/geda-icarus_xnf.html
@@ -12,9 +12,7 @@
<body>
-
-
-<h1><a name="xilinx_netlist_format" id="xilinx_netlist_format">Xilinx Netlist Format</a></h1>
+<h1 class="sectionedit859"><a name="xilinx_netlist_format" id="xilinx_netlist_format">Xilinx Netlist Format</a></h1>
<div class="level1">
<pre class="code">WHAT IS XNF
@@ -257,7 +255,7 @@ IBUF, NOT gates cannot be absorbed as in the OPAD case.
*
* 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
+ * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
*/
diff --git a/docs/wiki/geda-igarus_fpga_lcg.html b/docs/wiki/geda-igarus_fpga_lcg.html
index 806a427..3c09cbd 100644
--- a/docs/wiki/geda-igarus_fpga_lcg.html
+++ b/docs/wiki/geda-igarus_fpga_lcg.html
@@ -12,9 +12,7 @@
<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>
+<h1 class="sectionedit1160"><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
@@ -241,7 +239,6 @@ Revision 1.2 2001/09/06 04:28:40 steve
Revision 1.1 2001/09/02 23:58:49 steve
Add documentation for the code generator.
-
</pre>
</div>
diff --git a/docs/wiki/geda-installation.fr.html b/docs/wiki/geda-installation.fr.html
index 9aa6a9e..1100cc2 100644
--- a/docs/wiki/geda-installation.fr.html
+++ b/docs/wiki/geda-installation.fr.html
@@ -11,35 +11,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>
+<h1 class="sectionedit1162"><a name="aide_a_l_installation" id="aide_a_l_installation">Aide à l'installation</a></h1>
<div class="level1">
<p>
@@ -47,20 +20,20 @@ Cette section fournit quelques informations utiles aux personnes qui veulent ins
</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>
+<!-- EDIT1162 SECTION "Aide à l'installation" [1-151] -->
+<h2 class="sectionedit1163"><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>
+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).
+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.
+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>
@@ -68,58 +41,59 @@ De la même manière, des personnes ont créé des RPM RedHat, des Debs Debian e
</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.
+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.
+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>
+<!-- EDIT1163 SECTION "Comment installer la Suite gEDA?" [152-2869] -->
+<h2 class="sectionedit1164"><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.
+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.
+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>
+<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>
+<!-- EDIT1164 SECTION "Comment désinstaller la Suite gEDA?" [2870-3713] -->
+<h2 class="sectionedit1165"><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.
+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.
+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.
+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>
+<!-- EDIT1165 SECTION "Pourquoi voudrais-je désinstaller la Suite gEDA?" [3714-4683] -->
+<h2 class="sectionedit1166"><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!
+ 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:
+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>
@@ -128,64 +102,66 @@ Le drapeau précis ou le point de montage adéquat de votre distribution peut ê
</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·:
+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:
+� 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).
+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>
+<!-- EDIT1166 SECTION "Aaaaargh! J'ai mis un CD dans le lecteur, je l'ai monté mais rien ne se produit!" [4684-6523] -->
+<h2 class="sectionedit1167"><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.
+ 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 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 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 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 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>
+<!-- EDIT1167 SECTION "Aidez-moi! Je tente une installation en utilisant le CD ROM mais le magicien d'installation m'indique une erreur!" [6524-8722] -->
+<h2 class="sectionedit1168"><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:
+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 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 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>
+<!-- EDIT1168 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 class="sectionedit1169"><a name="fedora_core_4_install_notes" id="fedora_core_4_install_notes">Fedora Core 4 install notes</a></h2>
<div class="level2">
<p>
@@ -193,8 +169,8 @@ Après que vous ayiez installé la Suite gEDA depuis le CD ROM, assurez-vous d
</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>
+<!-- EDIT1169 SECTION "Fedora Core 4 install notes" [10034-10112] -->
+<h2 class="sectionedit1170"><a name="fedora_core_3_install_notes" id="fedora_core_3_install_notes">Fedora Core 3 install notes</a></h2>
<div class="level2">
<p>
@@ -202,8 +178,8 @@ Après que vous ayiez installé la Suite gEDA depuis le CD ROM, assurez-vous d
</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>
+<!-- EDIT1170 SECTION "Fedora Core 3 install notes" [10113-10191] -->
+<h2 class="sectionedit1171"><a name="fedora_core_2_install_notes" id="fedora_core_2_install_notes">Fedora Core 2 install notes</a></h2>
<div class="level2">
<p>
@@ -211,8 +187,8 @@ Après que vous ayiez installé la Suite gEDA depuis le CD ROM, assurez-vous d
</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>
+<!-- EDIT1171 SECTION "Fedora Core 2 install notes" [10192-10270] -->
+<h2 class="sectionedit1172"><a name="fedora_core_1_install_notes" id="fedora_core_1_install_notes">Fedora Core 1 install notes</a></h2>
<div class="level2">
<p>
@@ -220,8 +196,8 @@ Après que vous ayiez installé la Suite gEDA depuis le CD ROM, assurez-vous d
</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>
+<!-- EDIT1172 SECTION "Fedora Core 1 install notes" [10271-10349] -->
+<h2 class="sectionedit1173"><a name="suse_93_install_notes" id="suse_93_install_notes">Suse 9.3 install notes</a></h2>
<div class="level2">
<p>
@@ -229,8 +205,8 @@ Après que vous ayiez installé la Suite gEDA depuis le CD ROM, assurez-vous d
</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>
+<!-- EDIT1173 SECTION "Suse 9.3 install notes" [10350-10433] -->
+<h2 class="sectionedit1174"><a name="suse_100_install_notes" id="suse_100_install_notes">Suse 10.0 install notes</a></h2>
<div class="level2">
<p>
@@ -238,8 +214,8 @@ Après que vous ayiez installé la Suite gEDA depuis le CD ROM, assurez-vous d
</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>
+<!-- EDIT1174 SECTION "Suse 10.0 install notes" [10434-10520] -->
+<h2 class="sectionedit1175"><a name="suse_101_install_notes" id="suse_101_install_notes">Suse 10.1 install notes</a></h2>
<div class="level2">
<p>
@@ -247,8 +223,8 @@ Après que vous ayiez installé la Suite gEDA depuis le CD ROM, assurez-vous d
</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>
+<!-- EDIT1175 SECTION "Suse 10.1 install notes" [10521-10607] -->
+<h2 class="sectionedit1176"><a name="notes_d_installation_debian" id="notes_d_installation_debian">Notes d'installation Debian</a></h2>
<div class="level2">
<p>
@@ -256,14 +232,15 @@ Les <a href="geda-debian.fr.html" class="wikilink1" title="geda-debian.fr.html">
</p>
</div>
-<!-- SECTION "Notes d'installation Debian" [10608-10720] -->
-<h2><a name="windows_install_notes" id="windows_install_notes">Windows install notes</a></h2>
+<!-- EDIT1176 SECTION "Notes d'installation Debian" [10608-10720] -->
+<h2 class="sectionedit1177"><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>
+<a href="geda-cygwin.html" class="wikilink1" title="geda-cygwin.html">Cygwin notes available here</a>
+
</p>
</div>
-<!-- SECTION "Windows install notes" [10721-] --></body>
+<!-- EDIT1177 SECTION "Windows install notes" [10721-] --></body>
</html>
diff --git a/docs/wiki/geda-installation.html b/docs/wiki/geda-installation.html
index a035f2d..a4be17c 100644
--- a/docs/wiki/geda-installation.html
+++ b/docs/wiki/geda-installation.html
@@ -11,27 +11,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>
+<h1 class="sectionedit29"><a name="installation_help" id="installation_help">Installation help</a></h1>
<div class="level1">
<p>
@@ -39,17 +20,17 @@ This section provides some information useful to people who want to install gEDA
</p>
</div>
-<!-- SECTION "Installation help" [1-136] -->
-<h2><a name="debian_distributions" id="debian_distributions">Debian distributions</a></h2>
+<!-- EDIT29 SECTION "Installation help" [1-137] -->
+<h2 class="sectionedit30"><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>.
+The repository of the Debian distribution contains <a href="http://packages.debian.org/search?suite=default&section=all&arch=any&searchon=names&keywords=geda"; class="urlextern" title="http://packages.debian.org/search?suite=default&section=all&arch=any&searchon=names&keywords=geda"; rel="nofollow">binary packages</a> of the core geda/gaf tools including <a href="http://packages.debian.org/search?suite=default&section=all&arch=any&searchon=names&keywords=gschem"; class="urlextern" title="http://packages.debian.org/search?suite=default&section=all&arch=any&searchon=names&keywords=gschem"; rel="nofollow">gschem</a>, <a href="http://packages.debian.org/search?suite=default&section=all&arch=any&searchon=names&keywords=pcb"; class="urlextern" title="http://packages.debian.org/search?suite=default&section=all&arch=any&searchon=names&keywords=pcb"; rel="nofollow">pcb</a>, <a href="http://packages.debian.org/search?suite=default&section=all&arch=any&searchon=names&keywords=gnucap"; class="urlextern" title="http://packages.debian.org/search?suite=default&section=all&arch=any&searchon=names&keywords=gnucap"; rel="nofollow">gnucap</a> and <a href="http://packages.debian.org/search?suite=default&section=all&arch=any&searchon=names&keywords=gerbv"; class="urlextern" title="http://packages.debian.org/search?suite=default&section=all&arch=any&searchon=names&keywords=gerbv"; 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>
+<!-- EDIT30 SECTION "Debian distributions" [138-1123] -->
+<h2 class="sectionedit31"><a name="fedora_and_redhat_distributions" id="fedora_and_redhat_distributions">Fedora and RedHat distributions</a></h2>
<div class="level2">
<p>
@@ -65,12 +46,13 @@ For more informations read the <a href="geda-fedora_rpm_installation.html" class
</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>
+<!-- EDIT31 SECTION "Fedora and RedHat distributions" [1124-1566] -->
+<h2 class="sectionedit32"><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.
+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>
@@ -82,17 +64,18 @@ For more informations read the <a href="geda-suse_rpm_installation.html" class="
</p>
</div>
-<!-- SECTION "SuSE and OpenSuSE distributions" [1661-2241] -->
-<h2><a name="mac_osx_distributions" id="mac_osx_distributions">Mac OSX distributions</a></h2>
+<!-- EDIT32 SECTION "SuSE and OpenSuSE distributions" [1567-2147] -->
+<h2 class="sectionedit33"><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>.
+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>
+<!-- EDIT33 SECTION "Mac OSX distributions" [2148-2386] -->
+<h2 class="sectionedit34"><a name="windows_distributions" id="windows_distributions">Windows distributions</a></h2>
<div class="level2">
<p>
@@ -104,22 +87,14 @@ Please see the <a href="geda-cygwin.html" class="wikilink1" title="geda-cygwin.h
</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>
+<!-- EDIT34 SECTION "Windows distributions" [2387-3034] -->
+<h2 class="sectionedit35"><a name="gitunstable_testing" id="gitunstable_testing">git: Unstable/Testing</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>
+For those already familiar with the gEDA/gaf applications and those who need the latest stuff, access to source-code repository is available. This is the latest developer source-code version of the application.<br/>
-</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:
+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>
@@ -129,22 +104,15 @@ For those already familiar with the gEDA/gaf applications and those who need the
</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:
+
+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).
</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>.
+Information on how to fetch the gEDA git repository can be found <a href="geda-scm.html" class="wikilink1" title="geda-scm.html"> here</a>.
+
</p>
</div>
-<!-- SECTION "CVS / git: Unstable/Testing" [3450-] --></body>
+<!-- EDIT35 SECTION "git: Unstable/Testing" [3035-] --></body>
</html>
diff --git a/docs/wiki/geda-installed_plugins.html b/docs/wiki/geda-installed_plugins.html
index 39ae539..e042f2d 100644
--- a/docs/wiki/geda-installed_plugins.html
+++ b/docs/wiki/geda-installed_plugins.html
@@ -11,22 +11,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>
+<h1 class="sectionedit71"><a name="installed_plugins" id="installed_plugins">Installed plugins</a></h1>
<div class="level1">
<p>
@@ -34,8 +20,8 @@ The following plugins have been installed, to give the gEDA Project Wiki additio
</p>
</div>
-<!-- SECTION "Installed plugins" [1-132] -->
-<h2><a name="hilited" id="hilited">hilited</a></h2>
+<!-- EDIT71 SECTION "Installed plugins" [1-132] -->
+<h2 class="sectionedit72"><a name="hilited" id="hilited">hilited</a></h2>
<div class="level2">
<p>
@@ -44,24 +30,28 @@ The â??hilitedâ?? plugin acts as a yellow highlighter. Surround the text you wan
<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.
+
+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>
+<!-- EDIT72 SECTION "hilited" [133-400] -->
+<h2 class="sectionedit73"><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:
+
+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>
@@ -73,8 +63,11 @@ The â??xtermâ?? plugin allows you to embed preformatted text.<br/>
</ul>
<p>
- Example:<br/>
- The following is indented from the current sectionâ??s left margin: <pre STYLE="background : LightGreen;
+
+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>
@@ -85,7 +78,7 @@ The following shows how the preformatted text will follow the <acronym title="Ex
<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;
+<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>
@@ -93,5 +86,5 @@ margin-left : 2em"><font size="+0">Indented test line 3.</font></pre></div>
</ul>
</div>
-<!-- SECTION "xterm" [401-] --></body>
+<!-- EDIT73 SECTION "xterm" [401-] --></body>
</html>
diff --git a/docs/wiki/geda-kig_howto.html b/docs/wiki/geda-kig_howto.html
index b857166..ec77c9a 100644
--- a/docs/wiki/geda-kig_howto.html
+++ b/docs/wiki/geda-kig_howto.html
@@ -11,41 +11,13 @@
</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>
+<h1 class="sectionedit117"><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>
+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>
@@ -53,27 +25,28 @@ by: Stefan Petersen, spe@xxxxxxxxxxxxx This document is released under <a href="
</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>
+<!-- EDIT117 SECTION "How To Setup Keymapping In gschem" [1-177] -->
+<h2 class="sectionedit118"><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.
+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>
+<!-- EDIT118 SECTION "About this document" [178-588] -->
+<h2 class="sectionedit119"><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.
+
+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>
+<!-- EDIT119 SECTION "Functionality" [589-1128] -->
+<h2 class="sectionedit120"><a name="keymaps" id="keymaps">Keymaps</a></h2>
<div class="level2">
<p>
@@ -81,8 +54,8 @@ The current implementation is built-up around â??keymapsâ??. A keymap is a list
</p>
</div>
-<!-- SECTION "Keymaps" [1129-1427] -->
-<h3><a name="an_example_on_keymaps" id="an_example_on_keymaps">An example on keymaps</a></h3>
+<!-- EDIT120 SECTION "Keymaps" [1129-1427] -->
+<h3 class="sectionedit121"><a name="an_example_on_keymaps" id="an_example_on_keymaps">An example on keymaps</a></h3>
<div class="level3">
<p>
@@ -97,7 +70,7 @@ 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).
+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)
@@ -109,36 +82,41 @@ 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.
+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>
+<!-- EDIT121 SECTION "An example on keymaps" [1428-2358] -->
+<h3 class="sectionedit122"><a name="description_of_keys" id="description_of_keys">Description of keys</a></h3>
<div class="level3">
<p>
-The key are described as:
+The keys are described as:
+
</p>
-<table class="inline">
- <tr>
- <td> For a </td><td> â??aâ?? </td>
+<div class="table sectionedit123"><table class="inline">
+ <tr class="row0">
+ <td class="col0"> For a </td><td class="col1"> â??aâ?? </td>
</tr>
- <tr>
- <td class="leftalign"> For Shift-A </td><td> â??Shift Aâ?? </td>
+ <tr class="row1">
+ <td class="col0 leftalign"> For Shift-A </td><td class="col1"> â??Shift Aâ?? </td>
</tr>
- <tr>
- <td> For Control-a </td><td> â??Control aâ?? </td>
+ <tr class="row2">
+ <td class="col0"> For Control-a </td><td class="col1"> â??Control aâ?? </td>
</tr>
- <tr>
- <td> For Alt-a </td><td> â??Alt aâ?? </td>
+ <tr class="row3">
+ <td class="col0"> For Alt-a </td><td class="col1"> â??Alt aâ?? </td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT123 TABLE [2417-2517] -->
<p>
- There are a few simple rules to follow when keys for a new keymap is defined:
+
+There are a few simple rules to follow when keys for a new keymap are defined:
</p>
<ul>
<li class="level1"><div class="li"> Everything is case sensitive</div>
@@ -152,28 +130,30 @@ The key are described as:
</ul>
</div>
-<!-- SECTION "Description of keys" [2358-2925] -->
-<h3><a name="actions" id="actions">Actions</a></h3>
+<!-- EDIT122 SECTION "Description of keys" [2359-2928] -->
+<h3 class="sectionedit124"><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.
+
+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>
+<!-- EDIT124 SECTION "Actions" [2929-3243] -->
+<h3 class="sectionedit125"><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.
+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>
+<!-- EDIT125 SECTION "Function calls" [3244-3677] -->
+<h3 class="sectionedit126"><a name="another_keymap" id="another_keymap">Another keymap</a></h3>
<div class="level3">
<p>
@@ -181,51 +161,55 @@ If the cdr-element is another keymap then that command is a multi-key command, i
</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>
+<!-- EDIT126 SECTION "Another keymap" [3678-4000] -->
+<h2 class="sectionedit127"><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
+
+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.
+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>
+<!-- EDIT127 SECTION "Where are the key mappings stored" [4001-4474] -->
+<h3 class="sectionedit128"><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>
+<div class="table sectionedit129"><table class="inline">
+ <tr class="row0">
+ <td class="col0"> <strong>function</strong> </td><td class="col1">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 class="row1">
+ <td class="col0"><strong>action</strong> </td><td class="col1">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 class="row2">
+ <td class="col0"><strong>list</strong> </td><td class="col1">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 class="row3">
+ <td class="col0"><strong>pair</strong> </td><td class="col1">(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 class="row4">
+ <td class="col0"><strong>car element</strong> </td><td class="col1">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 class="row5">
+ <td class="col0"><strong>cdr element</strong> </td><td class="col1">(pronounced cudr) The second element in a pair. In the list case it denotes the rest of list. </td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT129 TABLE [4510-5117] -->
</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>
+<!-- EDIT128 SECTION "Appendix A -- Dictionary" [4475-5119] -->
+<h2 class="sectionedit130"><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;
+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>
@@ -312,9 +296,10 @@ options-snap
options-show-log-window
options-show-coord-window
misc-misc
-cancel</font></pre>
+cancel</font></pre>
+
</p>
</div>
-<!-- SECTION "Appendix B -- Built-in actions in gschem" [5117-] --></body>
+<!-- EDIT130 SECTION "Appendix B -- Built-in actions in gschem" [5120-] --></body>
</html>
diff --git a/docs/wiki/geda-license.html b/docs/wiki/geda-license.html
new file mode 100644
index 0000000..85b5d40
--- /dev/null
+++ b/docs/wiki/geda-license.html
@@ -0,0 +1,121 @@
+<!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 class="sectionedit1408"><a name="geda_licensing" id="geda_licensing">gEDA Licensing</a></h1>
+<div class="level1">
+
+<p>
+
+All software components of gEDA/gaf are released under the
+<a href="http://www.gnu.org/licenses/old-licenses/gpl-2.0.html"; class="urlextern" title="http://www.gnu.org/licenses/old-licenses/gpl-2.0.html"; rel="nofollow"> GNU General Public
+License (GPL) version 2 or later</a>. However, some confusion exists about
+the schematic symbols. What license do they use? Will <acronym title="GNU General Public License">GPL</acronym> symbols
+â??infectâ?? your design, thereby requiring you to release your design to
+the public? If you modify the symbols, must you release the modified
+versions under the <acronym title="GNU General Public License">GPL</acronym>?
+</p>
+
+<p>
+The goal of the gEDA Project is to provide an open-source EDA Suite
+which may be used for non-commercial as well as commercial projects.
+Our tools are aimed for use by students, hobbyists, educators, consultants,
+ and â?? yes â?? corporate engineers. We are not interested
+in exerting any control over your designs, or forcing you to reveal
+proprietary information contained in your designs.
+</p>
+
+<p>
+Symbols are similar to the font files used in document
+processing software â?? they are graphical objects used to express your
+ideas. We want you to retain control of your own ideas (your design),
+while the gEDA Project retains a say in how you redistribute the
+symbols themselves.
+</p>
+
+<p>
+There are three ways a symbol might be distributed:
+
+</p>
+<ol>
+<li class="level1"><div class="li"> As part of a symbol library, or individually as a .sym file (i.e. as a symbol itself).</div>
+</li>
+<li class="level1"><div class="li"> Embedded in a .sch file (i.e. part of the soft, or editable copy of a design).</div>
+</li>
+<li class="level1"><div class="li"> The resulting graphical expression on a schematic diagram (i.e. as part of the hard, or non-editable copy of a design).</div>
+</li>
+</ol>
+
+<p>
+
+There is a distinction between cases 1 and (2, 3). In case 1, the
+object of interest is the symbol library (or individual symbol)
+itself. In case (2, 3), the object of interest is the design.
+Some label case 1 â??distributionâ??, and case (2, 3) â??useâ?? of the symbol.
+</p>
+
+<p>
+Our goals for the symbols are:
+
+</p>
+<ul>
+<li class="level1"><div class="li"> We wish to distribute the symbols under a licencing scheme which encourages that you give back to the community if you redistribute the the symbols themselves â?? whether modified or unmodified. This is case 1 distribution. The <acronym title="GNU General Public License">GPL</acronym> ensures this.</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> We wish to specifically prohibit anybody from building gEDA's symbols into their *software* products, and then place restrictions on how the resulting product may be used. If you bundle gEDA symbolsâ?? whether modified or unmodified â?? into your software and then distribute it, then you must allow for the software's (and symbols') continued redistribution under the <acronym title="GNU General Public License">GPL</acronym>. Again, this is case 1 distribution; the <acronym title="GNU General Public License">GPL</acronym> ensures this.</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> However, we do not wish to â??infectâ?? your *electronic* design, or force you to release your proprietary design information if you use or embed gEDA symbols in your design. This is case (2, 3) use.</div>
+</li>
+</ul>
+
+<p>
+
+The Free Software Foundation has recognized a possible conflict of
+the base <acronym title="GNU General Public License">GPL</acronym> with the use of fonts â?? and, by analogy, symbols used in
+case (2, 3). Their solution is to use an exemption clause in the <acronym title="GNU General Public License">GPL</acronym>
+which you explicitly insert for fonts. Read about it here:
+</p>
+
+<p>
+<a href="http://www.fsf.org/licensing/licenses/gpl-faq.html#FontException"; class="urlextern" title="http://www.fsf.org/licensing/licenses/gpl-faq.html#FontException"; rel="nofollow"> http://www.fsf.org/licensing/licenses/gpl-faq.html#FontException</a>
+</p>
+
+<p>
+Therefore, using this as a template, all symbols released with
+gEDA/gaf are covered under the <acronym title="GNU General Public License">GPL</acronym> with the following exception clause:
+
+</p>
+<pre class="code">As a special exception, if you create a design which uses this symbol,
+and embed this symbol or unaltered portions of this symbol into the
+design, this symbol does not by itself cause the resulting design to
+be covered by the GNU General Public License. This exception does not
+however invalidate any other reasons why the design itself might be
+covered by the GNU General Public License. If you modify this
+symbol, you may extend this exception to your version of the
+symbol, but you are not obligated to do so. If you do not
+wish to do so, delete this exception statement from your version.</pre>
+
+<p>
+
+The idea is that case 1 redistribution is covered under the <acronym title="GNU General Public License">GPL</acronym>, but
+distribution of your design (case (2, 3) is exempt from the <acronym title="GNU General Public License">GPL</acronym>.
+This is the scheme which the gEDA Project wishes to use for symbol
+distribution and use.
+</p>
+
+</div>
+<!-- EDIT1408 SECTION "gEDA Licensing" [2-] --></body>
+</html>
diff --git a/docs/wiki/geda-links.html b/docs/wiki/geda-links.html
new file mode 100644
index 0000000..4ef5909
--- /dev/null
+++ b/docs/wiki/geda-links.html
@@ -0,0 +1,545 @@
+<!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 class="sectionedit1409"><a name="geda_links" id="geda_links">gEDA Links</a></h1>
+<div class="level1">
+
+<p>
+The <a href="geda-start.html" class="wikilink1" title="geda-start.html"> gEDA project </a> has produced and continues
+working on a full <strong>G</strong>PL'd suite of <strong>E</strong>lectronic <strong>D</strong>esign
+<strong>A</strong>utomation tools. These tools are used for electrical circuit
+design, schematic capture, simulation, prototyping, and production.
+The gEDA project was started because of the lack of free EDA tools
+for UNIX. The tools are being developed mainly on GNU/Linux machines,
+but considerable effort is being made to make sure that gEDA runs on
+other UNIX variants. For a complete list of freely available tools
+please be sure to visit <a href="http://www.opencollector.org"; class="urlextern" title="http://www.opencollector.org"; rel="nofollow"> Open Collector </a>
+</p>
+
+<p>
+Please e-mail me (ahvezda AT seul.org) if you want your link/project
+added here.
+</p>
+
+</div>
+<!-- EDIT1409 SECTION "gEDA Links" [1-717] -->
+<h2 class="sectionedit1410"><a name="directly_related_links" id="directly_related_links">Directly related links</a></h2>
+<div class="level2">
+
+<p>
+
+<a href="http://www.opencollector.org"; class="urlextern" title="http://www.opencollector.org"; rel="nofollow">
+Open Collector -- The database for open hardware tools/designs </a>
+</p>
+
+<p>
+<a href="http://www.freeedaug.org/"; class="urlextern" title="http://www.freeedaug.org/"; rel="nofollow">
+Boston's Free Electronic Design Automation Users Group (FreeEDAUG) </a>
+</p>
+
+<p>
+<a href="http://www.gedasymbols.org/"; class="urlextern" title="http://www.gedasymbols.org/"; rel="nofollow">
+The gEDA project's symbol / footprint / tool upload and sharing site </a>
+</p>
+
+<p>
+<a href="http://www.brorson.com/gEDA/SPICE/"; class="urlextern" title="http://www.brorson.com/gEDA/SPICE/"; rel="nofollow">
+SDB's advanced SPICE netlister Homepage (now part of gEDA/gaf) </a>
+</p>
+
+<p>
+<a href="http://www.delorie.com/hobbyplat/edatools/"; class="urlextern" title="http://www.delorie.com/hobbyplat/edatools/"; rel="nofollow">
+DJ Delorie's HobbyPlatform EDA Tools page </a>
+</p>
+
+<p>
+<a href="http://www.luciani.org/geda/geda-index.html"; class="urlextern" title="http://www.luciani.org/geda/geda-index.html"; rel="nofollow">
+John Luciani's page on gEDA, gsch2pcb, PCB footprint creation and library </a>
+</p>
+
+<p>
+<a href="http://www.sp5pbe.waw.pl/~sp5smk/geda.html"; class="urlextern" title="http://www.sp5pbe.waw.pl/~sp5smk/geda.html"; rel="nofollow">
+RPMs for gEDA/gaf snapshots </a>
+</p>
+
+<p>
+<a href="http://www.sp5pbe.waw.pl/~sp5smk/pcb.html"; class="urlextern" title="http://www.sp5pbe.waw.pl/~sp5smk/pcb.html"; rel="nofollow">
+RPMs for PCB snapshots </a>
+</p>
+
+<p>
+<a href="http://jschneider.net/pcb-build.html"; class="urlextern" title="http://jschneider.net/pcb-build.html"; rel="nofollow">
+Building PCB on OSX (by Jon Schneider) </a>
+</p>
+
+<p>
+<a href="http://www.h-renrew.de/h/spicelib/doc/index.html"; class="urlextern" title="http://www.h-renrew.de/h/spicelib/doc/index.html"; rel="nofollow">
+Spicelib, which provides thousands of Gnucap and NGSpice compatible component models </a>
+</p>
+
+</div>
+<!-- EDIT1410 SECTION "Directly related links" [718-1774] -->
+<h2 class="sectionedit1411"><a name="projects_created_using_geda" id="projects_created_using_geda">Projects created using gEDA</a></h2>
+<div class="level2">
+
+<p>
+
+<a href="http://ronja.twibright.com/"; class="urlextern" title="http://ronja.twibright.com/"; rel="nofollow">
+Ronja (Reasonable Optical Near Joint Access) is an Open-Source project of optical point-to-point data link.</a>
+</p>
+
+<p>
+<a href="http://oap.sourceforge.net/"; class="urlextern" title="http://oap.sourceforge.net/"; rel="nofollow">
+The Open Automaton Project aims to develop an intelligent PC-based mobile robot </a>
+</p>
+
+<p>
+<a href="http://www.dlharmon.com/sbc.html"; class="urlextern" title="http://www.dlharmon.com/sbc.html"; rel="nofollow">
+Darrell Harmon's Single Board Computer Project </a>
+</p>
+
+<p>
+<a href="http://dlharmon.com/dspcard/index.html"; class="urlextern" title="http://dlharmon.com/dspcard/index.html"; rel="nofollow">
+Darrell Harmon's high speed digital signal processing board </a>
+</p>
+
+<p>
+<a href="http://www.tangentsoft.net/audio/mint/index.html"; class="urlextern" title="http://www.tangentsoft.net/audio/mint/index.html"; rel="nofollow">
+MINT : A Jung multiloop type amp circuit </a>
+</p>
+
+<p>
+<a href="http://linuxcar.sone.jp/"; class="urlextern" title="http://linuxcar.sone.jp/"; rel="nofollow">
+A Linux Car Project (SONE Takeshi) </a>
+</p>
+
+<p>
+<a href="http://www.delorie.com/house/furnace/"; class="urlextern" title="http://www.delorie.com/house/furnace/"; rel="nofollow">
+DJ Delorie's House Furnace project </a>
+</p>
+
+<p>
+<a href="http://www.araneus.fi/audsl"; class="urlextern" title="http://www.araneus.fi/audsl"; rel="nofollow">
+Audio Digital Subscriber Line </a>
+</p>
+
+<p>
+<a href="http://code.ettus.com/redmine/ettus/projects/public/documents"; class="urlextern" title="http://code.ettus.com/redmine/ettus/projects/public/documents"; rel="nofollow">
+The Universal Software Radio Peripheral (USRP) </a>
+</p>
+
+<p>
+<a href="http://oscar.dcarr.org/ssrp/index.php"; class="urlextern" title="http://oscar.dcarr.org/ssrp/index.php"; rel="nofollow">
+David Carr's simple software radio peripheral (SSRP) </a>
+</p>
+
+<p>
+<a href="http://www.h-renrew.de/h/avrclock/avrclock.html"; class="urlextern" title="http://www.h-renrew.de/h/avrclock/avrclock.html"; rel="nofollow">
+Werner Hoch's AVR 7-segment clock </a>
+</p>
+
+<p>
+<a href="http://www.h-renrew.de/h/avrterminal/avrterminal.html"; class="urlextern" title="http://www.h-renrew.de/h/avrterminal/avrterminal.html"; rel="nofollow">
+Werner Hoch's AVR LCD terminal for the serial port </a>
+</p>
+
+<p>
+<a href="http://kosmosisland.com/island/david/V2/index.php"; class="urlextern" title="http://kosmosisland.com/island/david/V2/index.php"; rel="nofollow">
+David Koski's "H-bridge" motor driver power booster </a>
+</p>
+
+<p>
+<a href="http://www.lecad.uni-lj.si/~leon/electronics/logger"; class="urlextern" title="http://www.lecad.uni-lj.si/~leon/electronics/logger"; rel="nofollow">
+Leon Kos' SmartMedia logging </a>
+</p>
+
+<p>
+<a href="http://www.lecad.uni-lj.si/~leon/electronics/portus/index.html"; class="urlextern" title="http://www.lecad.uni-lj.si/~leon/electronics/portus/index.html"; rel="nofollow">
+Leon Kos' Three door opener </a>
+</p>
+
+<p>
+<a href="http://www.ise.pw.edu.pl/~wzab/cygnal/index.html"; class="urlextern" title="http://www.ise.pw.edu.pl/~wzab/cygnal/index.html"; rel="nofollow">
+Simple evaluation board and Linux programmer for C8051F320 </a>
+</p>
+
+<p>
+<a href="http://ventoso.org/luca/vdr/index.html"; class="urlextern" title="http://ventoso.org/luca/vdr/index.html"; rel="nofollow">
+vdr actuator plugin </a>
+</p>
+
+<p>
+<a href="http://www.janw.dommel.be/pic2-e.html"; class="urlextern" title="http://www.janw.dommel.be/pic2-e.html"; rel="nofollow">
+Jan Wagemakers' 16F84 IR Receiver </a>
+</p>
+
+<p>
+<a href="http://www.janw.dommel.be/pic18f452-e.html"; class="urlextern" title="http://www.janw.dommel.be/pic18f452-e.html"; rel="nofollow">
+Jan Wagemakers' PIC18F452 and 3COM 3C509B Ethernet ISA card </a>
+</p>
+
+<p>
+<a href="http://www.makezine.com/extras/13.html"; class="urlextern" title="http://www.makezine.com/extras/13.html"; rel="nofollow">
+Make a Glowing, Wearable, EL-Wire, Blinky Light Using Open Source Tools </a>
+</p>
+
+<p>
+<a href="http://linuxfocus.org/English/June2005/article379.shtml"; class="urlextern" title="http://linuxfocus.org/English/June2005/article379.shtml"; rel="nofollow">
+A digital DC powersupply </a>
+</p>
+
+<p>
+<a href="http://hansmi.ch/hardware/wrap-powercontrol"; class="urlextern" title="http://hansmi.ch/hardware/wrap-powercontrol"; rel="nofollow">
+WRAP-Powercontrol -- PC power reset/control circuit </a>
+</p>
+
+<p>
+<a href="http://fabrizio.oasi.asti.it/files/projects/ds1624/"; class="urlextern" title="http://fabrizio.oasi.asti.it/files/projects/ds1624/"; rel="nofollow">
+DS1624 parallel port thermometer </a>
+</p>
+
+<p>
+<a href="http://www.rowetel.com/ucasterisk/hardware.html"; class="urlextern" title="http://www.rowetel.com/ucasterisk/hardware.html"; rel="nofollow">
+GPL Telephony Hardware </a>
+</p>
+
+<p>
+<a href="http://chezphil.org/slugterm/"; class="urlextern" title="http://chezphil.org/slugterm/"; rel="nofollow">
+SlugTerm - A Terminal for my Slug </a>
+</p>
+
+<p>
+<a href="http://makezine.com/04/strobe/"; class="urlextern" title="http://makezine.com/04/strobe/"; rel="nofollow">
+Homemade Strobe Photography </a>
+</p>
+
+<p>
+<a href="http://www.bootseg.com/?article=9"; class="urlextern" title="http://www.bootseg.com/?article=9"; rel="nofollow">
+Paintball Shot Counter </a>
+</p>
+
+<p>
+<a href="http://www.stappers.nl/gst/willeprom"; class="urlextern" title="http://www.stappers.nl/gst/willeprom"; rel="nofollow">
+Willeprom </a>
+</p>
+
+<p>
+<a href="http://web.interware.hu/lekovacs/reflow_oven/index.html"; class="urlextern" title="http://web.interware.hu/lekovacs/reflow_oven/index.html"; rel="nofollow">
+Kovacs Levente's How to turn your toaster into an IR reflow oven </a>
+</p>
+
+<p>
+<a href="http://web.interware.hu/lekovacs/xover/index.html"; class="urlextern" title="http://web.interware.hu/lekovacs/xover/index.html"; rel="nofollow">
+Kovacs Levente's Three way, two channel active crossover </a>
+</p>
+
+<p>
+<a href="http://www.ise.pw.edu.pl/~wzab/opiclab/"; class="urlextern" title="http://www.ise.pw.edu.pl/~wzab/opiclab/"; rel="nofollow">
+Open PIC Lab </a>
+</p>
+
+<p>
+<a href="http://blackfin.uclinux.org/projects/bf1/"; class="urlextern" title="http://blackfin.uclinux.org/projects/bf1/"; rel="nofollow">
+BlackfinOne is a new BF532 based board </a>
+</p>
+
+<p>
+<a href="http://www.lunkwill.org/gadgetboard/index.html"; class="urlextern" title="http://www.lunkwill.org/gadgetboard/index.html"; rel="nofollow">
+The Gadgetboard is a free, low cost, user friendly microcontroller experimentation board on steroids </a>
+</p>
+
+<p>
+<a href="http://www.ad7gd.net/xc9536/"; class="urlextern" title="http://www.ad7gd.net/xc9536/"; rel="nofollow">
+CPLD LED blinker based on XAPP078 </a>
+</p>
+
+<p>
+<a href="http://craigbot.blogspot.com/"; class="urlextern" title="http://craigbot.blogspot.com/"; rel="nofollow">
+Craig's Robot Blog </a>
+</p>
+
+<p>
+<a href="http://time.qnan.org/"; class="urlextern" title="http://time.qnan.org/"; rel="nofollow">
+Using a Garmin GPS 18 LVC as NTP stratum-0 on Linux 2.6 </a>
+</p>
+
+<p>
+<a href="http://www.xs4all.nl/~dicks/avr/index.html"; class="urlextern" title="http://www.xs4all.nl/~dicks/avr/index.html"; rel="nofollow">
+Atmel AVR Projects </a>
+</p>
+
+<p>
+<a href="http://computerchristmas.com/?link=how_to&HowToId=83"; class="urlextern" title="http://computerchristmas.com/?link=how_to&HowToId=83"; rel="nofollow">
+128 chan derivative of Hill's 320 design w/ PCB and Linux driver </a>
+</p>
+
+<p>
+<a href="http://www.ssalewski.de/AT90USB_board.html.en"; class="urlextern" title="http://www.ssalewski.de/AT90USB_board.html.en"; rel="nofollow">
+Experimentation board for the AT90USB </a>
+</p>
+
+<p>
+<a href="http://www.ssalewski.de/DAD.html.en"; class="urlextern" title="http://www.ssalewski.de/DAD.html.en"; rel="nofollow">
+Digital Storage Oscilloscope (DSO) </a>
+</p>
+
+<p>
+<a href="http://www.cyclerecorder.org/blog/20070609"; class="urlextern" title="http://www.cyclerecorder.org/blog/20070609"; rel="nofollow">
+CycleRecorder project </a>
+</p>
+
+<p>
+<a href="http://petertodd.ca/art/source-code/"; class="urlextern" title="http://petertodd.ca/art/source-code/"; rel="nofollow">
+Peter Todd's Open Source Hardware </a>
+</p>
+
+<p>
+<a href="http://www.delorie.com/electronics/alarmclock/"; class="urlextern" title="http://www.delorie.com/electronics/alarmclock/"; rel="nofollow">
+DJ's Streaming MP3 Alarm Clock </a>
+</p>
+
+<p>
+<a href="http://homepage.mac.com/kpreid/2007/timer/"; class="urlextern" title="http://homepage.mac.com/kpreid/2007/timer/"; rel="nofollow">
+Timer Project </a>
+</p>
+
+<p>
+<a href="http://www.evilmadscientist.com/article.php/card"; class="urlextern" title="http://www.evilmadscientist.com/article.php/card"; rel="nofollow">
+Tiny portable AVR projects: Business card breakout boards </a>
+</p>
+
+<p>
+<a href="http://cantankerous.quixotic.org.uk/Projects/IpDoorBell/"; class="urlextern" title="http://cantankerous.quixotic.org.uk/Projects/IpDoorBell/"; rel="nofollow">
+Ethernet and I/O board </a>
+</p>
+
+<p>
+<a href="http://www.evilmadscientist.com/article.php/peggy"; class="urlextern" title="http://www.evilmadscientist.com/article.php/peggy"; rel="nofollow">
+"Peggy," A Light Emitting Pegboard Display </a>
+</p>
+
+<p>
+<a href="http://bb.cactii.net/archives/000175.php"; class="urlextern" title="http://bb.cactii.net/archives/000175.php"; rel="nofollow">
+A Nixie tube clock </a>
+</p>
+
+<p>
+<a href="http://hw.cz/teorie-praxe/konstrukce/art2086-laboratorni-zdroj-rizeny-mikroprocesorem.html"; class="urlextern" title="http://hw.cz/teorie-praxe/konstrukce/art2086-laboratorni-zdroj-rizeny-mikroprocesorem.html"; rel="nofollow">
+Digital DC Power Supply (in Czech) </a>
+</p>
+
+<p>
+<a href="http://www.wand.net.nz/~rzw2/pcb/"; class="urlextern" title="http://www.wand.net.nz/~rzw2/pcb/"; rel="nofollow">
+GPS Interface and Time Synchronization </a>
+</p>
+
+<p>
+<a href="http://www.ieap.uni-kiel.de/et/msl/pictures/photos/rsh/FM/DE"; class="urlextern" title="http://www.ieap.uni-kiel.de/et/msl/pictures/photos/rsh/FM/DE"; rel="nofollow">
+The Mars Science Lab (NASA mission) with the Radiation Assessment Detector instrument on board. </a>
+</p>
+
+<p>
+<a href="http://openprog.altervista.org/OP_eng.html"; class="urlextern" title="http://openprog.altervista.org/OP_eng.html"; rel="nofollow">
+An open source USB programmer </a>
+</p>
+
+<p>
+<a href="http://www.altusmetrum.org/"; class="urlextern" title="http://www.altusmetrum.org/"; rel="nofollow">
+Open hardware and software designs for high powered model rocketry </a>
+</p>
+
+<p>
+<a href="http://www.gedanken.demon.co.uk/gps-sd-logger/"; class="urlextern" title="http://www.gedanken.demon.co.uk/gps-sd-logger/"; rel="nofollow">
+GPS to SD-Card Data Logger </a>
+</p>
+
+<p>
+<a href="http://hansmi.ch/hardware/twilight-switch"; class="urlextern" title="http://hansmi.ch/hardware/twilight-switch"; rel="nofollow">
+A twilight switch designed using the gEDA suite </a>
+</p>
+
+<p>
+<a href="http://www.evilmadscientist.com/article.php/meggyjr"; class="urlextern" title="http://www.evilmadscientist.com/article.php/meggyjr"; rel="nofollow">
+Meggy Jr RGB from the Evil Mad Scientist Laboratories </a>
+</p>
+
+<p>
+<a href="http://jeffrey.co.in/blog/2009/09/at90usb162-mini-development-board/"; class="urlextern" title="http://jeffrey.co.in/blog/2009/09/at90usb162-mini-development-board/"; rel="nofollow">
+AT90USB162 Mini Development Board </a>
+</p>
+
+<p>
+<a href="http://hobby-electrons.sourceforge.net/projects/terminal-keyboard/"; class="urlextern" title="http://hobby-electrons.sourceforge.net/projects/terminal-keyboard/"; rel="nofollow">
+Terminal Keyboard </a>
+</p>
+
+<p>
+<a href="http://starbase.globalpc.net/~ezekowitz/vanessa/hobbies/projects.html"; class="urlextern" title="http://starbase.globalpc.net/~ezekowitz/vanessa/hobbies/projects.html"; rel="nofollow">
+Vanessa's projects </a>
+</p>
+
+<p>
+<a href="http://www.mare.ee/indrek/timer/"; class="urlextern" title="http://www.mare.ee/indrek/timer/"; rel="nofollow">
+Let's make a timer </a>
+</p>
+
+<p>
+<a href="http://randomprojects.org/wiki/Usbflattiny"; class="urlextern" title="http://randomprojects.org/wiki/Usbflattiny"; rel="nofollow">
+A small Free Software and Free Hardware USB dongle for various purposes </a>
+</p>
+
+<p>
+<a href="http://www.kbdbabel.org/"; class="urlextern" title="http://www.kbdbabel.org/"; rel="nofollow">
+Open source keyboard protocol translator project </a>
+</p>
+
+<p>
+<a href="http://www.msarnoff.org/projects/alpha32/"; class="urlextern" title="http://www.msarnoff.org/projects/alpha32/"; rel="nofollow">
+32-character serial led display </a>
+</p>
+
+<p>
+<a href="http://www.dm.ufscar.br/~waldeck/pic/termometro"; class="urlextern" title="http://www.dm.ufscar.br/~waldeck/pic/termometro"; rel="nofollow">
+Termometro Digital com PIC16F818 e LM35 </a>
+</p>
+
+<p>
+<a href="http://blog.sindormir.net/blogs/index.php?blog=6"; class="urlextern" title="http://blog.sindormir.net/blogs/index.php?blog=6"; rel="nofollow">
+An automated, self-regulated and autonomous (computer-free) system for driving vehicle </a>
+</p>
+
+<p>
+<a href="http://www.gedanken.demon.co.uk/amb-pic-code/"; class="urlextern" title="http://www.gedanken.demon.co.uk/amb-pic-code/"; rel="nofollow">
+Lots of PIC projects </a>
+</p>
+
+<p>
+<a href="http://www.larsen-b.com/Article/241.html"; class="urlextern" title="http://www.larsen-b.com/Article/241.html"; rel="nofollow">
+IV-18 VFD vacuum Russian Clock </a>
+</p>
+
+<p>
+<a href="http://reality.sgiweb.org/overby/rockets/Alt7/index.html"; class="urlextern" title="http://reality.sgiweb.org/overby/rockets/Alt7/index.html"; rel="nofollow">
+An altimeter is based on an Atmel AVR microcontroller </a>
+</p>
+
+<p>
+<a href="http://home.earthlink.net/~david.schultz/altproject/take2.html"; class="urlextern" title="http://home.earthlink.net/~david.schultz/altproject/take2.html"; rel="nofollow">
+An altimeter based Texas on a Instruments MSP430F1232 microcontroller </a>
+</p>
+
+<p>
+<a href="http://www.dietfig.org/FpgaRadio"; class="urlextern" title="http://www.dietfig.org/FpgaRadio"; rel="nofollow">
+FM Software Radio Receiver </a>
+</p>
+
+<p>
+<a href="http://www.tuxgraphics.org/electronics/200606/article06061.shtml"; class="urlextern" title="http://www.tuxgraphics.org/electronics/200606/article06061.shtml"; rel="nofollow">
+An AVR microcontroller based Ethernet device </a>
+</p>
+
+<p>
+<a href="http://custard.restall.net/msf_receiver/index.php"; class="urlextern" title="http://custard.restall.net/msf_receiver/index.php"; rel="nofollow">
+MSF Radio Receiver </a>
+</p>
+
+<p>
+<a href="http://prosje.be/Projects/PulsTeller.html"; class="urlextern" title="http://prosje.be/Projects/PulsTeller.html"; rel="nofollow">
+PulsTeller </a>
+</p>
+
+<p>
+<a href="http://projects.nosomos.org/"; class="urlextern" title="http://projects.nosomos.org/"; rel="nofollow">
+Lots of projects created using the gEDA </a>
+</p>
+
+<p>
+<a href="http://www.xs4all.nl/~vzzbx/dds.html"; class="urlextern" title="http://www.xs4all.nl/~vzzbx/dds.html"; rel="nofollow">
+A signal generator based upon an AD5932 DDS and a AtMega8515 microcontroller </a>
+</p>
+
+<p>
+<a href="http://nuwiki.openwrt.org/oldwiki/OpenWrtDocs/Customizing/Hardware/I2C_RTC"; class="urlextern" title="http://nuwiki.openwrt.org/oldwiki/OpenWrtDocs/Customizing/Hardware/I2C_RTC"; rel="nofollow">
+An I2C bus and a Real-Time Clock to the Linksys WRT54GL router </a>
+</p>
+
+<p>
+<a href="http://code.google.com/p/xarias/"; class="urlextern" title="http://code.google.com/p/xarias/"; rel="nofollow">
+An embedded car computer system, based on ATMega32 MCU </a>
+</p>
+
+<p>
+<a href="http://members.cox.net/ebrombaugh1/synth/audiodac/index.html"; class="urlextern" title="http://members.cox.net/ebrombaugh1/synth/audiodac/index.html"; rel="nofollow">
+Digilent-Compatible I2S Audio DAC </a>
+</p>
+
+<p>
+<a href="http://ad7gd.net/tippy/"; class="urlextern" title="http://ad7gd.net/tippy/"; rel="nofollow">
+MMA2260 Accelerometer Demo </a>
+</p>
+
+<p>
+<a href="http://www.delorie.com/electronics/powermeter/"; class="urlextern" title="http://www.delorie.com/electronics/powermeter/"; rel="nofollow">
+Monitor power usage in common residential circuit breaker boxes </a>
+</p>
+
+<p>
+<a href="http://lowvoltagelabs.com/products/videooverlayshield/"; class="urlextern" title="http://lowvoltagelabs.com/products/videooverlayshield/"; rel="nofollow">
+Arduino compatible shield board overlays text on analog video </a>
+</p>
+
+</div>
+<!-- EDIT1411 SECTION "Projects created using gEDA" [1775-9641] -->
+<h2 class="sectionedit1412"><a name="various_press_that_geda_has_received" id="various_press_that_geda_has_received">Various press that gEDA has received</a></h2>
+<div class="level2">
+
+<p>
+
+<a href="http://www.linuxjournal.com/article/8438"; class="urlextern" title="http://www.linuxjournal.com/article/8438"; rel="nofollow">
+An article about gEDA (written by Stuart Brorson) was printed in Linux Journal </a>
+</p>
+
+<p>
+<a href="http://www.dtweed.com/circuitcellar/caj00176.htm"; class="urlextern" title="http://www.dtweed.com/circuitcellar/caj00176.htm"; rel="nofollow">
+An article about gEDA (written by a few gEDA developers) was printed in Circuit Cellar </a>
+</p>
+
+<p>
+<a href="http://www.eedesign.com/news/showArticle.jhtml?articleId=55301354"; class="urlextern" title="http://www.eedesign.com/news/showArticle.jhtml?articleId=55301354"; rel="nofollow">
+An interview with various people involved with gEDA in EEDesign/EETimes </a>
+</p>
+
+<p>
+<a href="http://developers.slashdot.org/article.pl?sid=04/12/14/2357224"; class="urlextern" title="http://developers.slashdot.org/article.pl?sid=04/12/14/2357224"; rel="nofollow">
+The above interview got posted to Slashdot </a>
+</p>
+
+<p>
+<a href="http://www.eetimes.com/story/OEG19981125S0022"; class="urlextern" title="http://www.eetimes.com/story/OEG19981125S0022"; rel="nofollow">
+An older interview that appeared in EETimes </a>
+</p>
+
+<p>
+<a href="http://linuxfocus.org/English/December2004/article355.shtml"; class="urlextern" title="http://linuxfocus.org/English/December2004/article355.shtml"; rel="nofollow">
+A story written by Iznogood appeared in LinuxFocus </a>
+</p>
+
+<p>
+<a href="http://ignite.oreilly.com/2009/02/ignite-boston-5-wrap-up-videos.html"; class="urlextern" title="http://ignite.oreilly.com/2009/02/ignite-boston-5-wrap-up-videos.html"; rel="nofollow">
+Ignite 5 video given by Stuart Brorson about "Hardware design and the gEDA Project </a>
+</p>
+
+</div>
+<!-- EDIT1412 SECTION "Various press that gEDA has received" [9642-] --></body>
+</html>
diff --git a/docs/wiki/geda-mailinglists.html b/docs/wiki/geda-mailinglists.html
new file mode 100644
index 0000000..9c72e9b
--- /dev/null
+++ b/docs/wiki/geda-mailinglists.html
@@ -0,0 +1,119 @@
+<!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 class="sectionedit1401"><a name="geda_mailing_lists" id="geda_mailing_lists">gEDA Mailing Lists</a></h1>
+<div class="level1">
+
+</div>
+<!-- EDIT1401 SECTION "gEDA Mailing Lists" [1-34] -->
+<h2 class="sectionedit1402"><a name="available_mailing_lists" id="available_mailing_lists">Available Mailing Lists</a></h2>
+<div class="level2">
+<div class="table sectionedit1403"><table class="inline">
+ <tr class="row0">
+ <th class="col0 leftalign"> List Name </th><th class="col1 leftalign"> Description </th><th class="col2 leftalign"> Posting address </th><th class="col3 leftalign"> Access </th><th class="col4 leftalign"> Archives </th>
+ </tr>
+ <tr class="row1">
+ <td class="col0"> geda-announce </td><td class="col1 leftalign"> Announcements </td><td class="col2"> geda-annouce@xxxxxxxx </td><td class="col3 leftalign"> <a href="http://www.seul.org/cgi-bin/mailman/listinfo/geda-announce"; class="urlextern" title="http://www.seul.org/cgi-bin/mailman/listinfo/geda-announce"; rel="nofollow"> web </a> </td><td class="col4 leftalign"> <a href="http://www.seul.org/pipermail/geda-announce/"; class="urlextern" title="http://www.seul.org/pipermail/geda-announce/"; rel="nofollow"> Monthly </a> </td>
+ </tr>
+ <tr class="row2">
+ <td class="col0"> geda-user </td><td class="col1"> User questions </td><td class="col2"> geda-user@xxxxxxxx </td><td class="col3 leftalign"> <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"> web </a> </td><td class="col4"> <a href="http://www.seul.org/archives/geda/user/"; class="urlextern" title="http://www.seul.org/archives/geda/user/"; rel="nofollow"> Monthly </a> <a href="http://www.seul.org/pipermail/geda-user/"; class="urlextern" title="http://www.seul.org/pipermail/geda-user/"; rel="nofollow"> Monthly </a> </td>
+ </tr>
+ <tr class="row3">
+ <td class="col0"> geda-dev </td><td class="col1"> Developer discussions </td><td class="col2"> By Invitation Only </td><td class="col3"> N/A </td><td class="col4"> <a href="http://www.seul.org/archives/geda/dev/"; class="urlextern" title="http://www.seul.org/archives/geda/dev/"; rel="nofollow"> Monthly </a> <a href="http://www.seul.org/pipermail/geda-dev/"; class="urlextern" title="http://www.seul.org/pipermail/geda-dev/"; rel="nofollow"> Monthly </a> </td>
+ </tr>
+ <tr class="row4">
+ <td class="col0"> geda-bug </td><td class="col1"> Bugs/Patches </td><td class="col2"> geda-bug@xxxxxxxx </td><td class="col3 leftalign"> <a href="http://www.seul.org/cgi-bin/mailman/listinfo/geda-bug"; class="urlextern" title="http://www.seul.org/cgi-bin/mailman/listinfo/geda-bug"; rel="nofollow"> web </a> </td><td class="col4"> <a href="http://www.seul.org/archives/geda/bug/"; class="urlextern" title="http://www.seul.org/archives/geda/bug/"; rel="nofollow"> Monthly </a> <a href="http://www.seul.org/pipermail/geda-bug/"; class="urlextern" title="http://www.seul.org/pipermail/geda-bug/"; rel="nofollow"> Monthly </a> </td>
+ </tr>
+ <tr class="row5">
+ <td class="col0"> geda-cvs </td><td class="col1"> Repository commits </td><td class="col2"> geda-cvs@xxxxxxxx </td><td class="col3 leftalign"> <a href="http://www.seul.org/cgi-bin/mailman/listinfo/geda-cvs"; class="urlextern" title="http://www.seul.org/cgi-bin/mailman/listinfo/geda-cvs"; rel="nofollow"> web </a> </td><td class="col4"> <a href="http://www.seul.org/archives/geda/cvs/"; class="urlextern" title="http://www.seul.org/archives/geda/cvs/"; rel="nofollow"> Monthly </a> <a href="http://www.seul.org/pipermail/geda-cvs/"; class="urlextern" title="http://www.seul.org/pipermail/geda-cvs/"; rel="nofollow"> Monthly </a> </td>
+ </tr>
+</table></div>
+<!-- EDIT1403 TABLE [72-1239] -->
+</div>
+<!-- EDIT1402 SECTION "Available Mailing Lists" [35-1241] -->
+<h2 class="sectionedit1404"><a name="notes" id="notes">Notes</a></h2>
+<div class="level2">
+
+</div>
+<!-- EDIT1404 SECTION "Notes" [1242-1260] -->
+<h3 class="sectionedit1405"><a name="be_sure_to_read_all_the_notes_before_subscribing" id="be_sure_to_read_all_the_notes_before_subscribing">Be sure to read all the notes before subscribing</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> You can only post using a subscribed e-mail address. If you do not subscribe and attempt to post to one of the above lists, your post will never make it to the lists.</div>
+</li>
+<li class="level1"><div class="li"> If you are having posting problems, make sure the address that you send e-mail to is the same address you subscribed with.</div>
+</li>
+<li class="level1"><div class="li"> Use the posting address to send email to the list.</div>
+</li>
+<li class="level1"><div class="li"> To unsubscribe follow the links obn the bottom of each message from the list. Do NOT send unsubscription requests to the mailing list.</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> Advertisemant of non-free commercial EDA is NOT welcome on any of the mailing lists.</div>
+</li>
+<li class="level1"><div class="li"> Do NOT send spam to or harvest e-mail address from any page on this site.</div>
+</li>
+<li class="level1"><div class="li"> Plain text only please! Do NOT send messages to any gEDA list in <acronym title="HyperText Markup Language">HTML</acronym>.</div>
+</li>
+<li class="level1"><div class="li"> Small binary attachments are okay as long as they are relevant to gEDA.</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> Click on the â??Monthlyâ?? archive links to get a little more info about each list.</div>
+</li>
+<li class="level1"><div class="li"> The â??Monthlyâ?? archive is always up-to-date, while the â??Chunksâ?? tend to be updated only once in a while.</div>
+</li>
+</ul>
+
+</div>
+<!-- EDIT1405 SECTION "Be sure to read all the notes before subscribing" [1261-2323] -->
+<h3 class="sectionedit1406"><a name="read_via_gmane" id="read_via_gmane">Read via gmane</a></h3>
+<div class="level3">
+
+<p>
+The mailing lists are mirrored by <a href="http://gmane.org"; class="urlextern" title="http://gmane.org"; rel="nofollow">gmane</a>. This free and open service provides the contents of the list in <a href="http://en.wikipedia.org/wiki/Usenet"; class="urlextern" title="http://en.wikipedia.org/wiki/Usenet"; rel="nofollow">usenet</a> format. The benefit of this format is that you can use dedicated usenet readers to read and write to the lists. These readers are known for their ability to gracefully handle high traffic discussions. You'll have to provide following login data to the usenet reader:
+</p>
+<ul>
+<li class="level1"><div class="li"> group name: <code>gmane.comp.cad.geda.$LIST</code> â?? Replace '$LIST' with one of 'announce', 'user', 'dev', 'bug', or 'cvs'.</div>
+</li>
+<li class="level1"><div class="li"> server name: <code>news.gmane.org</code></div>
+</li>
+<li class="level1"><div class="li"> port: 119</div>
+</li>
+<li class="level1"><div class="li"> the server does not require authentication</div>
+</li>
+<li class="level1"><div class="li"> email address: The email address you used when you subscribed to the mailing list with one of the links from the table below.</div>
+</li>
+</ul>
+
+</div>
+<!-- EDIT1406 SECTION "Read via gmane" [2324-3137] -->
+<h3 class="sectionedit1407"><a name="search_the_mailing_lists" id="search_the_mailing_lists">Search the mailing lists</a></h3>
+<div class="level3">
+
+<p>
+There is no local search tool for the archive of the mailing lists. However, you can use an external search engine to retrieve topics that have been dealt with before. Since the many geda terms like â??schematicâ?? and â??pcbâ?? are not very specific a general web search may be swamped by false hits. Two options to look in the archives only:
+</p>
+<ol>
+<li class="level1"><div class="li"> Use the <a href="http://search.gmane.org/?query=foobar&author=&group=gmane.comp.cad.geda.user&sort=relevance&DEFAULTOP=and&xP=kaimartin&xFILTERS=Gcomp.cad.geda.user---A"; class="urlextern" title="http://search.gmane.org/?query=foobar&author=&group=gmane.comp.cad.geda.user&sort=relevance&DEFAULTOP=and&xP=kaimartin&xFILTERS=Gcomp.cad.geda.user---A"; rel="nofollow">gmane search page</a></div>
+</li>
+<li class="level1"><div class="li"> Restrict a google search to www.seul.org: <a href="http://www.google.com/search?q=foobar+site%3Awww.seul.org&hl=en"; class="urlextern" title="http://www.google.com/search?q=foobar+site%3Awww.seul.org&hl=en"; rel="nofollow"> google advanced seach</a></div>
+</li>
+</ol>
+
+
+
+</div>
+<!-- EDIT1407 SECTION "Search the mailing lists" [3138-] --></body>
+</html>
diff --git a/docs/wiki/geda-master_attributes_list.html b/docs/wiki/geda-master_attributes_list.html
index 7287213..2049806 100644
--- a/docs/wiki/geda-master_attributes_list.html
+++ b/docs/wiki/geda-master_attributes_list.html
@@ -11,68 +11,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>
+<h1 class="sectionedit1210"><a name="geda_gaf_master_attribute_document" id="geda_gaf_master_attribute_document">gEDA/gaf Master Attribute Document</a></h1>
<div class="level1">
<p>
@@ -88,91 +28,106 @@ July 10th, 2007
</p>
</div>
-<!-- SECTION "gEDA/gaf Master Attribute Document" [1-185] -->
-<h2><a name="overview" id="overview">Overview</a></h2>
+<!-- EDIT1210 SECTION "gEDA/gaf Master Attribute Document" [1-185] -->
+<h2 class="sectionedit1211"><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.
+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>
+<!-- EDIT1211 SECTION "Overview" [186-652] -->
+<h2 class="sectionedit1212"><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.
+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>
+<!-- EDIT1212 SECTION "What are Attributes?" [653-1423] -->
+<h2 class="sectionedit1213"><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>
+<!-- EDIT1213 SECTION "Symbol only Attributes" [1424-1459] -->
+<h3 class="sectionedit1214"><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>
+<strong>device</strong>= is the device name of the symbol<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>
+<!-- EDIT1214 SECTION "device" [1460-2074] -->
+<h3 class="sectionedit1215"><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>
+
+<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>
+<!-- EDIT1215 SECTION "graphical" [2075-2489] -->
+<h3 class="sectionedit1216"><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>
+
+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>
+<!-- EDIT1216 SECTION "description" [2490-2680] -->
+<h3 class="sectionedit1217"><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>
+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>
+<!-- EDIT1217 SECTION "author" [2681-3277] -->
+<h3 class="sectionedit1218"><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>
+
+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>
+<!-- EDIT1218 SECTION "comment" [3278-3551] -->
+<h3 class="sectionedit1219"><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/>
+
+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>
@@ -181,14 +136,16 @@ This attribute replaces the obsolete <strong>pin#</strong>=# attribute.
</p>
</div>
-<!-- SECTION "pinseq" [3581-4273] -->
-<h3><a name="pinnumber" id="pinnumber">pinnumber</a></h3>
+<!-- EDIT1219 SECTION "pinseq" [3552-4244] -->
+<h3 class="sectionedit1220"><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/>
+
+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>
@@ -197,219 +154,275 @@ This attribute replaces the obsolete pin#=# attribute.
</p>
</div>
-<!-- SECTION "pinnumber" [4274-4696] -->
-<h3><a name="pintype" id="pintype">pintype</a></h3>
+<!-- EDIT1220 SECTION "pinnumber" [4245-4667] -->
+<h3 class="sectionedit1221"><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/>
-
+
+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>
+<div class="table sectionedit1222"><table class="inline">
+ <tr class="row0">
+ <td class="col0">in</td><td class="col1">Input</td>
</tr>
- <tr>
- <td>out</td><td>Output</td>
+ <tr class="row1">
+ <td class="col0">out</td><td class="col1">Output</td>
</tr>
- <tr>
- <td>io</td><td>Input/Output</td>
+ <tr class="row2">
+ <td class="col0">io</td><td class="col1">Input/Output</td>
</tr>
- <tr>
- <td>oc</td><td>Open collector</td>
+ <tr class="row3">
+ <td class="col0">oc</td><td class="col1">Open collector</td>
</tr>
- <tr>
- <td>oe</td><td>Open emitter</td>
+ <tr class="row4">
+ <td class="col0">oe</td><td class="col1">Open emitter</td>
</tr>
- <tr>
- <td>pas</td><td>Passive</td>
+ <tr class="row5">
+ <td class="col0">pas</td><td class="col1">Passive</td>
</tr>
- <tr>
- <td>tp</td><td>Totem pole</td>
+ <tr class="row6">
+ <td class="col0">tp</td><td class="col1">Totem pole</td>
</tr>
- <tr>
- <td>tri</td><td>Tristate (high impedance)</td>
+ <tr class="row7">
+ <td class="col0">tri</td><td class="col1">Tristate (high impedance)</td>
</tr>
- <tr>
- <td>clk</td><td>Clock</td>
+ <tr class="row8">
+ <td class="col0">clk</td><td class="col1">Clock</td>
</tr>
- <tr>
- <td>pwr</td><td>Power/Ground</td>
+ <tr class="row9">
+ <td class="col0">pwr</td><td class="col1">Power/Ground</td>
</tr>
- <tr>
- <td colspan="2">Table 1: pintype values</td>
+ <tr class="row10">
+ <td class="col0" colspan="2">Table 1: pintype values</td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT1222 TABLE [4986-5185] -->
</div>
-<!-- SECTION "pintype" [4697-5215] -->
-<h3><a name="pinlabel" id="pinlabel">pinlabel</a></h3>
+<!-- EDIT1221 SECTION "pintype" [4668-5186] -->
+<h3 class="sectionedit1223"><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/>
+
+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>
+<!-- EDIT1223 SECTION "pinlabel" [5187-5520] -->
+<h3 class="sectionedit1224"><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>
+
+Example: <code>numslots=4</code>
</p>
</div>
-<!-- SECTION "numslots" [5550-6013] -->
-<h3><a name="slotdef" id="slotdef">slotdef</a></h3>
+<!-- EDIT1224 SECTION "numslots" [5521-5984] -->
+<h3 class="sectionedit1225"><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.
+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>
+<!-- EDIT1225 SECTION "slotdef" [5985-6965] -->
+<h3 class="sectionedit1226"><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.
+
+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>
+<!-- EDIT1226 SECTION "footprint" [6966-7924] -->
+<h3 class="sectionedit1227"><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>
+
+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>
+<!-- EDIT1227 SECTION "documentation" [7925-8683] -->
+<h2 class="sectionedit1228"><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>
+<!-- EDIT1228 SECTION "Schematic only Attributes" [8684-8721] -->
+<h3 class="sectionedit1229"><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/>
+
+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>
+<!-- EDIT1229 SECTION "netname" [8722-9081] -->
+<h3 class="sectionedit1230"><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>
+
+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>
+<!-- EDIT1230 SECTION "source" [9082-9703] -->
+<h2 class="sectionedit1231"><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>
+<!-- EDIT1231 SECTION "Symbol and Schematic Attributes" [9704-9748] -->
+<h3 class="sectionedit1232"><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>):
+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/>
+
+</p>
+
+</div>
+
+<h4><a name="refdes_naming_restrictions" id="refdes_naming_restrictions">refdes naming restrictions</a></h4>
+<div class="level4">
+
+<p>
+Gschem will accept any string as a value for the refdes. However, some back-ends to gnetlist impose restrictions on the allowed syntax.
+</p>
+
+<p>
+Specifically, <a href="geda-faq-gsch2pcb.html" class="wikilink1" title="geda-faq-gsch2pcb.html">gsch2pcb</a> requires:
+</p>
+<ul>
+<li class="level1"><div class="li"> No spaces</div>
+</li>
+<li class="level1"><div class="li"> No hyphens. This might upset the M4 macro language potentially used to generate footprints. â??_â?? is ok.</div>
+</li>
+<li class="level1"><div class="li"> Any lower case suffix is ignored. This is so you can, place four discrete NAND gates on the schematic called U1a, U1b, U1c and U1d. They will netlist into a single footprint named U1.</div>
+</li>
+<li class="level1"><div class="li"> Non-<acronym title="American Standard Code for Information Interchange">ASCII</acronym> characters like like üöä� will not print in pcb</div>
+</li>
+</ul>
+
+</div>
+
+<h4><a name="refdes_naming_conventiions" id="refdes_naming_conventiions">refdes naming conventiions</a></h4>
+<div class="level4">
+
+<p>
+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>
+<div class="table sectionedit1233"><table class="inline">
+ <tr class="row0">
+ <th class="col0"> Prefix </th><th class="col1"> Component type</th>
</tr>
- <tr>
- <td class="leftalign"> R<n> </td><td>Resistor</td>
+ <tr class="row1">
+ <td class="col0 leftalign"> R<n> </td><td class="col1">Resistor</td>
</tr>
- <tr>
- <td class="leftalign"> RN<n> </td><td>Resistor Network</td>
+ <tr class="row2">
+ <td class="col0 leftalign"> RN<n> </td><td class="col1">Resistor Network</td>
</tr>
- <tr>
- <td class="leftalign"> FB<n> </td><td>Ferrite Bead</td>
+ <tr class="row3">
+ <td class="col0 leftalign"> FB<n> </td><td class="col1">Ferrite Bead</td>
</tr>
- <tr>
- <td class="leftalign"> L<n> </td><td>Inductor</td>
+ <tr class="row4">
+ <td class="col0 leftalign"> L<n> </td><td class="col1">Inductor</td>
</tr>
- <tr>
- <td class="leftalign"> C<n> </td><td>Capacitor</td>
+ <tr class="row5">
+ <td class="col0 leftalign"> C<n> </td><td class="col1">Capacitor</td>
</tr>
- <tr>
- <td class="leftalign"> B<n> </td><td>Battery </td>
+ <tr class="row6">
+ <td class="col0 leftalign"> B<n> </td><td class="col1">Battery </td>
</tr>
- <tr>
- <td class="leftalign"> F<n> </td><td class="leftalign">Fuse </td>
+ <tr class="row7">
+ <td class="col0 leftalign"> F<n> </td><td class="col1 leftalign">Fuse </td>
</tr>
- <tr>
- <td class="leftalign"> J<n> </td><td>Connector</td>
+ <tr class="row8">
+ <td class="col0 leftalign"> J<n> </td><td class="col1">Connector</td>
</tr>
- <tr>
- <td class="leftalign"> P<n> </td><td>Connector (usually plugs that mate with J<n>)</td>
+ <tr class="row9">
+ <td class="col0 leftalign"> P<n> </td><td class="col1">Connector (usually plugs that mate with J<n>)</td>
</tr>
- <tr>
- <td class="leftalign"> K<n> </td><td>Relay</td>
+ <tr class="row10">
+ <td class="col0 leftalign"> K<n> </td><td class="col1">Relay</td>
</tr>
- <tr>
- <td class="leftalign"> S<n> </td><td>Switch</td>
+ <tr class="row11">
+ <td class="col0 leftalign"> S<n> </td><td class="col1">Switch</td>
</tr>
- <tr>
- <td class="leftalign"> T<n> </td><td>Transformer</td>
+ <tr class="row12">
+ <td class="col0 leftalign"> T<n> </td><td class="col1">Transformer</td>
</tr>
- <tr>
- <td class="leftalign"> TP<n> </td><td>Testpoint</td>
+ <tr class="row13">
+ <td class="col0 leftalign"> TP<n> </td><td class="col1">Testpoint</td>
</tr>
- <tr>
- <td class="leftalign"> M<n> </td><td>Motor</td>
+ <tr class="row14">
+ <td class="col0 leftalign"> M<n> </td><td class="col1">Motor</td>
</tr>
- <tr>
- <td class="leftalign"> D<n> </td><td>Diode</td>
+ <tr class="row15">
+ <td class="col0 leftalign"> D<n> </td><td class="col1">Diode</td>
</tr>
- <tr>
- <td class="leftalign"> Q<n> </td><td>Transistor</td>
+ <tr class="row16">
+ <td class="col0 leftalign"> Q<n> </td><td class="col1">Transistor</td>
</tr>
- <tr>
- <td class="leftalign"> U<n> </td><td>IC</td>
+ <tr class="row17">
+ <td class="col0 leftalign"> U<n> </td><td class="col1">IC</td>
</tr>
- <tr>
- <td class="leftalign"> X<n> </td><td>Crystal</td>
+ <tr class="row18">
+ <td class="col0 leftalign"> X<n> </td><td class="col1">Crystal</td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT1233 TABLE [11074-11499] -->
</div>
-<!-- SECTION "refdes" [9778-10889] -->
-<h3><a name="slot" id="slot">slot</a></h3>
+<!-- EDIT1232 SECTION "refdes" [9749-11500] -->
+<h3 class="sectionedit1234"><a name="slot" id="slot">slot</a></h3>
<div class="level3">
<p>
@@ -417,8 +430,8 @@ This attribute is used to specify a slot for a slotted component. It should be a
</p>
</div>
-<!-- SECTION "slot" [10890-11187] -->
-<h3><a name="net" id="net">net</a></h3>
+<!-- EDIT1234 SECTION "slot" [11501-11798] -->
+<h3 class="sectionedit1235"><a name="net" id="net">net</a></h3>
<div class="level3">
<p>
@@ -426,64 +439,76 @@ The <strong>net</strong>= attribute is used to create power/ground and arbitrary
</p>
</div>
-<!-- SECTION "net" [11188-11591] -->
-<h3><a name="value" id="value">value</a></h3>
+<!-- EDIT1235 SECTION "net" [11799-12202] -->
+<h3 class="sectionedit1236"><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/>
+
+Examples: <code>value=1K value=10V</code><br/>
</p>
</div>
-<!-- SECTION "value" [11592-11807] -->
-<h3><a name="symversion" id="symversion">symversion</a></h3>
+<!-- EDIT1236 SECTION "value" [12203-12418] -->
+<h3 class="sectionedit1237"><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>
+
+<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/>
+
+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>
+<!-- EDIT1237 SECTION "symversion" [12419-14287] -->
+<h3 class="sectionedit1238"><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>
+
+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>
+<!-- EDIT1238 SECTION "dist-license" [14288-14768] -->
+<h3 class="sectionedit1239"><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.
+
+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>
+<!-- EDIT1239 SECTION "use-license" [14769-15068] -->
+<h2 class="sectionedit1240"><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>
+<!-- EDIT1240 SECTION "Obsolete Attributes" [15069-15100] -->
+<h3 class="sectionedit1241"><a name="uref" id="uref">uref</a></h3>
<div class="level3">
<p>
@@ -491,8 +516,8 @@ The uref= attribute is obsolete and cannot not be used. It was used to provide t
</p>
</div>
-<!-- SECTION "uref" [14490-14621] -->
-<h3><a name="name" id="name">name</a></h3>
+<!-- EDIT1241 SECTION "uref" [15101-15232] -->
+<h3 class="sectionedit1242"><a name="name" id="name">name</a></h3>
<div class="level3">
<p>
@@ -500,8 +525,8 @@ The <strong>name</strong>= attribute should not be attached or appear in any sym
</p>
</div>
-<!-- SECTION "name" [14622-14775] -->
-<h3><a name="label" id="label">label</a></h3>
+<!-- EDIT1242 SECTION "name" [15233-15386] -->
+<h3 class="sectionedit1243"><a name="label" id="label">label</a></h3>
<div class="level3">
<p>
@@ -509,8 +534,8 @@ The <strong>label</strong>= attribute is obsolete and cannot be used. It was use
</p>
</div>
-<!-- SECTION "label" [14776-14991] -->
-<h3><a name="pin" id="pin">pin#</a></h3>
+<!-- EDIT1243 SECTION "label" [15387-15602] -->
+<h3 class="sectionedit1244"><a name="pin" id="pin">pin#</a></h3>
<div class="level3">
<p>
@@ -518,8 +543,8 @@ The <strong>pin#</strong>=# attribute is obsolete and cannot be used. It was use
</p>
</div>
-<!-- SECTION "pin#" [14992-15200] -->
-<h3><a name="slot1" id="slot1">slot#</a></h3>
+<!-- EDIT1244 SECTION "pin#" [15603-15811] -->
+<h3 class="sectionedit1245"><a name="slot1" id="slot1">slot#</a></h3>
<div class="level3">
<p>
@@ -527,8 +552,8 @@ The <strong>slot#</strong>=# attribute is obsolete and cannot be used. It was us
</p>
</div>
-<!-- SECTION "slot#" [15201-15386] -->
-<h3><a name="type" id="type">type</a></h3>
+<!-- EDIT1245 SECTION "slot#" [15812-15997] -->
+<h3 class="sectionedit1246"><a name="type" id="type">type</a></h3>
<div class="level3">
<p>
@@ -536,8 +561,8 @@ The <strong>type</strong>= attribute is obsolete and cannot be used. It was used
</p>
</div>
-<!-- SECTION "type" [15387-15559] -->
-<h3><a name="email" id="email">email</a></h3>
+<!-- EDIT1246 SECTION "type" [15998-16170] -->
+<h3 class="sectionedit1247"><a name="email" id="email">email</a></h3>
<div class="level3">
<p>
@@ -545,39 +570,39 @@ The information in this attribute has been merged with <a href="#author" title="
</p>
</div>
-<!-- SECTION "email" [15560-15644] -->
-<h2><a name="document_revision_history" id="document_revision_history">Document Revision History</a></h2>
+<!-- EDIT1247 SECTION "email" [16171-16255] -->
+<h2 class="sectionedit1248"><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>
+<div class="table sectionedit1249"><table class="inline">
+ <tr class="row0">
+ <td class="col0">July 14th, 2002</td><td class="col1">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 class="row1">
+ <td class="col0">July 14th, 2002</td><td class="col1">Updated doc to be in sync with post-20020527.</td>
</tr>
- <tr>
- <td>August 25th, 2002</td><td>Added obsolete type= attribute.</td>
+ <tr class="row2">
+ <td class="col0">August 25th, 2002</td><td class="col1">Added obsolete type= attribute.</td>
</tr>
- <tr>
- <td>September 14, 2002</td><td>Added description= attribute. Minor xes</td>
+ <tr class="row3">
+ <td class="col0">September 14, 2002</td><td class="col1">Added description= attribute. Minor xes</td>
</tr>
- <tr>
- <td>October 7, 2002</td><td>Added doc= attribute; Egil Kvaleberg.</td>
+ <tr class="row4">
+ <td class="col0">October 7, 2002</td><td class="col1">Added doc= attribute; Egil Kvaleberg.</td>
</tr>
- <tr>
- <td>February 11, 2003</td><td>Added reference to footprint conventions.</td>
+ <tr class="row5">
+ <td class="col0">February 11, 2003</td><td class="col1">Added reference to footprint conventions.</td>
</tr>
- <tr>
- <td>February 23, 2003</td><td>Added author=, email=, and comment= attributes.</td>
+ <tr class="row6">
+ <td class="col0">February 23, 2003</td><td class="col1">Added author=, email=, and comment= attributes.</td>
</tr>
- <tr>
- <td>July 6th, 2004</td><td>Added symversion= attributes.</td>
+ <tr class="row7">
+ <td class="col0">July 6th, 2004</td><td class="col1">Added symversion= attributes.</td>
</tr>
- <tr>
- <td>July 10th, 2007</td><td>Added dist-license= and use-license= attributes.</td>
+ <tr class="row8">
+ <td class="col0">July 10th, 2007</td><td class="col1">Added dist-license= and use-license= attributes.</td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT1249 TABLE [16294-16833] -->
</div>
-<!-- SECTION "Document Revision History" [15645-] --></body>
+<!-- EDIT1248 SECTION "Document Revision History" [16256-] --></body>
</html>
diff --git a/docs/wiki/geda-mcalc_readme.html b/docs/wiki/geda-mcalc_readme.html
index ba58606..1e807df 100644
--- a/docs/wiki/geda-mcalc_readme.html
+++ b/docs/wiki/geda-mcalc_readme.html
@@ -12,9 +12,7 @@
<body>
-
-
-<h1><a name="mcalc_readme" id="mcalc_readme">mcalc README</a></h1>
+<h1 class="sectionedit132"><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 $
diff --git a/docs/wiki/geda-na_howto.html b/docs/wiki/geda-na_howto.html
index 3328309..efd3829 100644
--- a/docs/wiki/geda-na_howto.html
+++ b/docs/wiki/geda-na_howto.html
@@ -11,26 +11,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>
+<h1 class="sectionedit169"><a name="net_attribute_mini-howto" id="net_attribute_mini-howto">net= attribute mini-HOWTO</a></h1>
<div class="level1">
<p>
@@ -50,54 +32,62 @@ 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>
+<!-- EDIT169 SECTION "net= attribute mini-HOWTO" [1-216] -->
+<h2 class="sectionedit170"><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.
+
+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>
+<!-- EDIT170 SECTION "What is the net= attribute used for?" [217-1022] -->
+<h2 class="sectionedit171"><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:
+
+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>
+<div class="table sectionedit172"><table class="inline">
+ <tr class="row0">
+ <td class="col0"> <strong><code>net=</code></strong> </td><td class="col1"> 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 class="row1">
+ <td class="col0"> signalname </td><td class="col1"> 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 class="row2">
+ <td class="col0"> pinname </td><td class="col1"> The pin name (or number) which is assigned to this signal/net (or pin names/numbers) </td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT172 TABLE [1723-1961] -->
<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.
+
+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>
+<!-- EDIT171 SECTION "What is the format of the net= attribute?" [1023-2446] -->
+<h2 class="sectionedit173"><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:
+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>
@@ -107,19 +97,19 @@ You can place the <strong><code>net=</code></strong> attribute in several places
<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/>
+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.
+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>
+<!-- EDIT173 SECTION "How do you actually use the net= attribute?" [2447-4387] -->
+<h2 class="sectionedit174"><a name="caveats_bugs" id="caveats_bugs">Caveats / Bugs</a></h2>
<div class="level2">
<p>
@@ -137,20 +127,21 @@ The <strong><code>net=</code></strong> attribute/mechanism is fairly new, so the
</ul>
</div>
-<!-- SECTION "Caveats / Bugs" [4388-5599] -->
-<h2><a name="example" id="example">Example</a></h2>
+<!-- EDIT174 SECTION "Caveats / Bugs" [4388-5599] -->
+<h2 class="sectionedit175"><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/>
-
+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>
+<div class="table sectionedit176"><table class="inline">
+ <tr class="row0">
+ <td class="col0"> <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
+</table></div>
+<!-- EDIT176 TABLE [6220-6241] --><pre class="code">v 19991011
C 38700 58100 1 0 0 7400-1.sym
{
T 39000 59000 5 10 1 1 0
@@ -189,7 +180,8 @@ 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:
+<strong>gnetlist</strong> (using the geda netlist format) run using this sample schematic outputs this:
+
</p>
<pre class="code">START header
@@ -224,14 +216,16 @@ 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>
+<!-- EDIT175 SECTION "Example" [5600-7377] -->
+<h2 class="sectionedit177"><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]
+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>
+<!-- EDIT177 SECTION "Final notes" [7378-] --></body>
</html>
diff --git a/docs/wiki/geda-ngnutmeg_mp.html b/docs/wiki/geda-ngnutmeg_mp.html
index 93cec8c..7351162 100644
--- a/docs/wiki/geda-ngnutmeg_mp.html
+++ b/docs/wiki/geda-ngnutmeg_mp.html
@@ -12,9 +12,7 @@
<body>
-
-
-<h1><a name="ngnutmeg_man-page" id="ngnutmeg_man-page">ngnutmeg man-page</a></h1>
+<h1 class="sectionedit208"><a name="ngnutmeg_man-page" id="ngnutmeg_man-page">ngnutmeg man-page</a></h1>
<div class="level1">
<pre class="code">NUTMEG(1) NUTMEG(1)
@@ -904,8 +902,7 @@ CAVEATS
-4th Berkeley Distribution 27 April 1987 NUTMEG(1)
-</pre>
+4th Berkeley Distribution 27 April 1987 NUTMEG(1)</pre>
</div>
</body>
diff --git a/docs/wiki/geda-ngsconvert_mp.html b/docs/wiki/geda-ngsconvert_mp.html
index bf4030a..f1caa80 100644
--- a/docs/wiki/geda-ngsconvert_mp.html
+++ b/docs/wiki/geda-ngsconvert_mp.html
@@ -12,9 +12,7 @@
<body>
-
-
-<h1><a name="ngsconvert_man-page" id="ngsconvert_man-page">ngsconvert man-page</a></h1>
+<h1 class="sectionedit275"><a name="ngsconvert_man-page" id="ngsconvert_man-page">ngsconvert man-page</a></h1>
<div class="level1">
<pre class="code">SCONVERT(1) SCONVERT(1)
@@ -131,8 +129,7 @@ BUGS
-4th Berkeley Distribution 20 March 1986 SCONVERT(1)
-</pre>
+4th Berkeley Distribution 20 March 1986 SCONVERT(1)</pre>
</div>
</body>
diff --git a/docs/wiki/geda-ngspice_and_gschem.html b/docs/wiki/geda-ngspice_and_gschem.html
index 7cad960..fa7c3cb 100644
--- a/docs/wiki/geda-ngspice_and_gschem.html
+++ b/docs/wiki/geda-ngspice_and_gschem.html
@@ -11,25 +11,14 @@
</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>
+<h1 class="sectionedit1250"><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:
+
+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>
@@ -39,20 +28,24 @@
</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>
+
+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.
+
+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>
+<!-- EDIT1250 SECTION "Overview" [1-772] -->
+<h1 class="sectionedit1251"><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.
+
+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>
@@ -64,16 +57,18 @@ Use gschem to build up a schematic that looks like:
</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.
+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>
+<!-- EDIT1251 SECTION "Setup" [773-1613] -->
+<h1 class="sectionedit1252"><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:
+
+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>
@@ -81,7 +76,7 @@ Note that three named nets have been created, â??Vinâ??, â??Voutâ??, and â??Vbas
</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:
+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>
@@ -89,11 +84,11 @@ The input signal is added by choosing â??SPICE simulation elements→vac-1.sy
</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.
+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:
+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>
@@ -101,7 +96,7 @@ Vcc is set in basically the same way except we choose â??SPICE simulation elemen
</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:
+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 on the manufacturer's website or the part's datasheet, but it may need to be modified to work with your favorite simulator. The easiest way to get the model is from <a href="http://www.h-renrew.de/h/spicelib/doc/index.html"; class="urlextern" title="http://www.h-renrew.de/h/spicelib/doc/index.html"; rel="nofollow"> spicelib</a>. 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
@@ -111,7 +106,7 @@ The transistor setup is a bit more complicated. We must first have access to a S
* 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:
+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>
@@ -119,7 +114,8 @@ Make a sub-folder named â??modelsâ?? in our project folder â??simpleSPICEâ?? and
</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:
+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>
@@ -127,7 +123,8 @@ Now we also need to inform gschem of the model file we created. This is done by
</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:
+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>
@@ -143,12 +140,14 @@ 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>
+<!-- EDIT1252 SECTION "Adding some SPICE stuff" [1614-4457] -->
+<h1 class="sectionedit1253"><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:
+
+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
@@ -162,19 +161,23 @@ Which does one AC analysis while two lines for DC analysis are commented out. Th
</p>
<p>
-Now that we have described the simulation we want done, open a terminal, move to the â??simpleSPICEâ?? directory and type the command:
+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:
+
+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.
+
+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>
+<!-- EDIT1253 SECTION "Simulation" [4458-] --></body>
</html>
diff --git a/docs/wiki/geda-ngspice_mp.html b/docs/wiki/geda-ngspice_mp.html
index e2a68a9..87bf9ce 100644
--- a/docs/wiki/geda-ngspice_mp.html
+++ b/docs/wiki/geda-ngspice_mp.html
@@ -12,9 +12,7 @@
<body>
-
-
-<h1><a name="ngspice_man-page" id="ngspice_man-page">ngspice man-page</a></h1>
+<h1 class="sectionedit421"><a name="ngspice_man-page" id="ngspice_man-page">ngspice man-page</a></h1>
<div class="level1">
<pre class="code">SPICE(1) SPICE(1)
@@ -331,8 +329,7 @@ CAVEATS
-4th Berkeley Distribution 20 March 1986 SPICE(1)
-</pre>
+4th Berkeley Distribution 20 March 1986 SPICE(1)</pre>
</div>
</body>
diff --git a/docs/wiki/geda-olib_readme.html b/docs/wiki/geda-olib_readme.html
index 72f3264..55337b0 100644
--- a/docs/wiki/geda-olib_readme.html
+++ b/docs/wiki/geda-olib_readme.html
@@ -12,9 +12,7 @@
<body>
-
-
-<h1><a name="olib_orcad_tm_converter_readme" id="olib_orcad_tm_converter_readme">olib (OrCAD (TM) converter) README</a></h1>
+<h1 class="sectionedit451"><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
@@ -115,8 +113,7 @@ dump, to allow corrections or improvements.
Mario Pascucci
-<m.pas@xxxxxxxxx>
-</pre>
+<m.pas@xxxxxxxxx></pre>
</div>
</body>
diff --git a/docs/wiki/geda-pcb-quick_reference.fr.html b/docs/wiki/geda-pcb-quick_reference.fr.html
index 0bd7a4c..743cb79 100644
--- a/docs/wiki/geda-pcb-quick_reference.fr.html
+++ b/docs/wiki/geda-pcb-quick_reference.fr.html
@@ -11,270 +11,245 @@
</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>
+<h1 class="sectionedit1254"><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>
+<!-- EDIT1254 SECTION "PCB: Référence Rapide" [1-39] -->
+<h2 class="sectionedit1255"><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>
+<!-- EDIT1255 SECTION "Disposition des Touches" [40-76] -->
+<h3 class="sectionedit1256"><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>
+<div class="table sectionedit1257"><table class="inline">
+ <tr class="row0">
+ <th class="col0 centeralign"> TOUCHE </th><th class="col1 leftalign"> MNEMONIQUE </th><th class="col2 centeralign"> DESCRIPTION </th>
</tr>
- <tr>
- <td class="centeralign"> esc </td><td class="leftalign"> panner </td><td> enter panning mode </td>
+ <tr class="row1">
+ <td class="col0 centeralign"> esc </td><td class="col1 leftalign"> panner </td><td class="col2"> 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 class="row2">
+ <td class="col0 centeralign"> insert </td><td class="col1 leftalign"> insert point </td><td class="col2"> 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 class="row3">
+ <td class="col0 centeralign"> space </td><td class="col1 leftalign"> select </td><td class="col2 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 class="row4">
+ <td class="col0 centeralign"> tab </td><td class="col1 leftalign"> flip view </td><td class="col2 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 class="row5">
+ <td class="col0 centeralign"> shift-del </td><td class="col1 leftalign"> del-cu </td><td class="col2 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 class="row6">
+ <td class="col0 centeralign"> \ </td><td class="col1 leftalign"> thin-draw </td><td class="col2 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 class="row7">
+ <td class="col0 centeralign"> shift-alt-a </td><td class="col1 leftalign"> unselect </td><td class="col2 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 class="row8">
+ <td class="col0 centeralign"> b </td><td class="col1 leftalign"> to other side </td><td class="col2 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 class="row9">
+ <td class="col0 centeralign"> shift-b </td><td class="col1 leftalign"> flip view </td><td class="col2 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 class="row10">
+ <td class="col0 centeralign"> c </td><td class="col1 leftalign"> center </td><td class="col2 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 class="row11">
+ <td class="col0 centeralign"> ctrl-c </td><td class="col1"> copy to buffer</td><td class="col2 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 class="row12">
+ <td class="col0 centeralign"> d </td><td class="col1 leftalign"> display name </td><td class="col2 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 class="row13">
+ <td class="col0 centeralign"> shift-d </td><td class="col1 leftalign"> pinout dialog </td><td class="col2 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 class="row14">
+ <td class="col0 centeralign"> e </td><td class="col1"> eliminate rats</td><td class="col2 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 class="row15">
+ <td class="col0 centeralign"> shift-e </td><td class="col1 leftalign"> eliminate some rats </td><td class="col2 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 class="row16">
+ <td class="col0 centeralign"> f </td><td class="col1 leftalign"> find </td><td class="col2 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 class="row17">
+ <td class="col0 centeralign"> shift-f </td><td class="col1 leftalign"> un-find </td><td class="col2 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 class="row18">
+ <td class="col0 centeralign"> g </td><td class="col1 leftalign"> increase grid </td><td class="col2 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 class="row19">
+ <td class="col0 centeralign"> shift-g </td><td class="col1 leftalign"> decrease grid </td><td class="col2 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 class="row20">
+ <td class="col0 centeralign"> h </td><td class="col1 leftalign"> hide </td><td class="col2 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 class="row21">
+ <td class="col0 centeralign"> ctrl-h </td><td class="col1 leftalign"> holeplate </td><td class="col2 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 class="row22">
+ <td class="col0 centeralign"> k </td><td class="col1 leftalign"> klearance </td><td class="col2 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 class="row23">
+ <td class="col0 centeralign"> shift-k </td><td class="col1 leftalign"> klear (-) </td><td class="col2 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 class="row24">
+ <td class="col0 centeralign"> l </td><td class="col1 leftalign"> increase line </td><td class="col2 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 class="row25">
+ <td class="col0 centeralign"> shift-l </td><td class="col1 leftalign"> decrease line </td><td class="col2"> 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 class="row26">
+ <td class="col0 centeralign"> m </td><td class="col1 leftalign"> move to layer </td><td class="col2 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 class="row27">
+ <td class="col0 centeralign"> shift-m </td><td class="col1 leftalign"> move selection to layer </td><td class="col2 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 class="row28">
+ <td class="col0 centeralign"> ctrl-m </td><td class="col1 leftalign"> move origin </td><td class="col2"> 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 class="row29">
+ <td class="col0 centeralign"> n </td><td class="col1 leftalign"> name </td><td class="col2"> 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 class="row30">
+ <td class="col0 centeralign"> shift-n </td><td class="col1 leftalign"> next </td><td class="col2"> 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 class="row31">
+ <td class="col0 centeralign"> o </td><td class="col1 leftalign"> optimize rats </td><td class="col2"> 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 class="row32">
+ <td class="col0 centeralign"> shift-o </td><td class="col1 leftalign"> optimize some rats </td><td class="col2"> 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 class="row33">
+ <td class="col0 centeralign"> shift-p </td><td class="col1 leftalign"> polygon close </td><td class="col2 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 class="row34">
+ <td class="col0 centeralign"> q </td><td class="col1 leftalign"> square toggle </td><td class="col2 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 class="row35">
+ <td class="col0 centeralign"> ctrl-r </td><td class="col1 leftalign"> report </td><td class="col2 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 class="row36">
+ <td class="col0 centeralign"> s </td><td class="col1 leftalign"> size </td><td class="col2 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 class="row37">
+ <td class="col0 centeralign"> shift-s </td><td class="col1 leftalign"> size (-) </td><td class="col2 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 class="row38">
+ <td class="col0 centeralign"> alt-s </td><td class="col1 leftalign"> sizehole </td><td class="col2 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 class="row39">
+ <td class="col0 centeralign"> alt-shift-s </td><td class="col1 leftalign"> sizehole (-) </td><td class="col2 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 class="row40">
+ <td class="col0 centeralign"> ctrl-s </td><td class="col1 leftalign"> sizehole </td><td class="col2 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 class="row41">
+ <td class="col0 centeralign"> ctrl-shift-s </td><td class="col1 leftalign"> sizehole (-) </td><td class="col2 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 class="row42">
+ <td class="col0 centeralign"> v </td><td class="col1 leftalign"> view extents </td><td class="col2 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 class="row43">
+ <td class="col0 centeralign"> z </td><td class="col1 leftalign"> zoom </td><td class="col2 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 class="row44">
+ <td class="col0 centeralign"> shift-z </td><td class="col1 leftalign"> un-zoom </td><td class="col2 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 class="row45">
+ <td class="col0 centeralign"> F1 </td><td class="col1 leftalign"> via </td><td class="col2"> 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 class="row46">
+ <td class="col0 centeralign"> F2 </td><td class="col1 leftalign"> line </td><td class="col2 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 class="row47">
+ <td class="col0 centeralign"> F3 </td><td class="col1 leftalign"> arc </td><td class="col2"> 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 class="row48">
+ <td class="col0 centeralign"> F4 </td><td class="col1 leftalign"> text </td><td class="col2"> 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 class="row49">
+ <td class="col0 centeralign"> F5 </td><td class="col1 leftalign"> rectangle </td><td class="col2 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 class="row50">
+ <td class="col0 centeralign"> F6 </td><td class="col1 leftalign"> polygon </td><td class="col2 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 class="row51">
+ <td class="col0 centeralign"> F7 </td><td class="col1 leftalign"> buffer </td><td class="col2"> 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 class="row52">
+ <td class="col0 centeralign"> F8 </td><td class="col1 leftalign"> delete </td><td class="col2 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 class="row53">
+ <td class="col0 centeralign"> F9 </td><td class="col1 leftalign"> rotate </td><td class="col2 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 class="row54">
+ <td class="col0 centeralign"> F10 </td><td class="col1 leftalign"> file menu </td><td class="col2 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 class="row55">
+ <td class="col0 centeralign"> F11 </td><td class="col1 leftalign"> select </td><td class="col2 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 class="row56">
+ <td class="col0 centeralign"> F12 </td><td class="col1 leftalign"> lock </td><td class="col2"> entrer dans le mode lock </td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT1257 TABLE [110-3776] -->
</div>
-<!-- SECTION "Table des Touches PCB" [77-3777] -->
-<h2><a name="touches_de_visualisation" id="touches_de_visualisation">Touches de Visualisation</a></h2>
+<!-- EDIT1256 SECTION "Table des Touches PCB" [77-3777] -->
+<h2 class="sectionedit1258"><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>
+<div class="table sectionedit1259"><table class="inline">
+ <tr class="row0">
+ <th class="col0 centeralign"> TOUCHE </th><th class="col1 centeralign"> MNEMONIC </th><th class="col2 centeralign"> DESCRIPTION </th>
</tr>
- <tr>
- <td class="centeralign"> esc </td><td class="centeralign"> panner </td><td class="rightalign"> </td>
+ <tr class="row1">
+ <td class="col0 centeralign"> esc </td><td class="col1 centeralign"> panner </td><td class="col2 leftalign"> </td>
</tr>
- <tr>
- <td class="centeralign"> v </td><td class="centeralign"> view extents </td><td>vue globale de la zone de travail</td>
+ <tr class="row2">
+ <td class="col0 centeralign"> v </td><td class="col1 centeralign"> view extents </td><td class="col2">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 class="row3">
+ <td class="col0 centeralign"> c </td><td class="col1 centeralign"> center </td><td class="col2">centre la vue sur le curseur</td>
</tr>
- <tr>
- <td class="centeralign"> z </td><td class="centeralign"> zoom </td><td>agrandissement</td>
+ <tr class="row4">
+ <td class="col0 centeralign"> z </td><td class="col1 centeralign"> zoom </td><td class="col2">agrandissement</td>
</tr>
- <tr>
- <td class="centeralign"> shift-z </td><td class="centeralign"> un-zoom </td><td class="rightalign"> </td>
+ <tr class="row5">
+ <td class="col0 centeralign"> shift-z </td><td class="col1 centeralign"> un-zoom </td><td class="col2 leftalign"> </td>
</tr>
- <tr>
- <td class="centeralign"> \ </td><td class="centeralign"> thin-draw on/off </td><td>toggles thin draw mode</td>
+ <tr class="row6">
+ <td class="col0 centeralign"> \ </td><td class="col1 centeralign"> thin-draw on/off </td><td class="col2">toggles thin draw mode</td>
</tr>
- <tr>
- <td class="centeralign"> tab </td><td class="centeralign"> flip view </td><td>retournement carte</td>
+ <tr class="row7">
+ <td class="col0 centeralign"> tab </td><td class="col1 centeralign"> flip view </td><td class="col2">retournement carte</td>
</tr>
- <tr>
- <td class="centeralign"> shift-b </td><td class="centeralign"> flip view </td><td>retournement carte</td>
+ <tr class="row8">
+ <td class="col0 centeralign"> shift-b </td><td class="col1 centeralign"> flip view </td><td class="col2">retournement carte</td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT1259 TABLE [3816-4193] -->
</div>
-<!-- SECTION "Touches de Visualisation" [3778-4194] -->
-<h1><a name="reference_d_empreintes" id="reference_d_empreintes">Référence d'Empreintes</a></h1>
+<!-- EDIT1258 SECTION "Touches de Visualisation" [3778-4194] -->
+<h1 class="sectionedit1260"><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.
+
+Le document maître pour la création d'empreintes est le <a href="http://pcb.gpleda.org/index.html#dir"; class="urlextern" title="http://pcb.gpleda.org/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>
+<!-- EDIT1260 SECTION "Référence d'Empreintes" [4195-4498] -->
+<h2 class="sectionedit1261"><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:
+
+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>
@@ -292,140 +267,143 @@
</ul>
</div>
-<!-- SECTION "Syntaxe Générale" [4504-5144] -->
-<h2><a name="elements" id="elements">�léments</a></h2>
+<!-- EDIT1261 SECTION "Syntaxe Générale" [4499-5139] -->
+<h2 class="sectionedit1262"><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>
+<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>
+<div class="table sectionedit1263"><table class="inline">
+ <tr class="row0">
+ <th class="col0 centeralign"> item </th><th class="col1 centeralign"> allowed value </th><th class="col2 centeralign"> explanation </th><th class="col3 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 class="row1">
+ <td class="col0 centeralign"> element_flags </td><td class="col1 centeralign"> unsigned hex value </td><td class="col2 leftalign"> </td><td class="col3 leftalign"> </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 class="row2">
+ <td class="col0 centeralign"> description </td><td class="col1 centeralign"> string </td><td class="col2 centeralign"> text descriptif de l'empreinte </td><td class="col3 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 class="row3">
+ <td class="col0 centeralign"> pcb name </td><td class="col1 centeralign"> string </td><td class="col2 centeralign"> refdes utilisé pour ce pcb particulier </td><td class="col3 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 class="row4">
+ <td class="col0 centeralign"> value </td><td class="col1 centeralign"> string </td><td class="col2 centeralign"> valeur du composant sur ce pcb particulier </td><td class="col3 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 class="row5">
+ <td class="col0 centeralign"> mark_x </td><td class="col1 centeralign"> 1/100th mils </td><td class="col2 leftalign"> </td><td class="col3 leftalign"> </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 class="row6">
+ <td class="col0 centeralign"> mark_y </td><td class="col1 centeralign"> 1/100th mils </td><td class="col2 leftalign"> </td><td class="col3 leftalign"> </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 class="row7">
+ <td class="col0 centeralign"> text_x </td><td class="col1 centeralign"> 1/100th mils </td><td class="col2 leftalign"> </td><td class="col3 leftalign"> </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 class="row8">
+ <td class="col0 centeralign"> text_y </td><td class="col1 centeralign"> 1/100th mils </td><td class="col2 leftalign"> </td><td class="col3 leftalign"> </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 class="row9">
+ <td class="col0 centeralign"> text direction </td><td class="col1 centeralign"> decimal integer </td><td class="col2 centeralign"> 0=horiz; 1=ccw90; 2=180; 3=cw90 </td><td class="col3 leftalign"> </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 class="row10">
+ <td class="col0 centeralign"> text_scale </td><td class="col1 centeralign"> decimal integer </td><td class="col2 leftalign"> </td><td class="col3 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 class="row11">
+ <td class="col0 centeralign"> text_flags </td><td class="col1 centeralign"> unsigned hex </td><td class="col2 leftalign"> </td><td class="col3 leftalign"> </td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT1263 TABLE [5298-5975] -->
</div>
-<!-- SECTION "�léments" [5145-5981] -->
-<h2><a name="pastilles" id="pastilles">Pastilles</a></h2>
+<!-- EDIT1262 SECTION "�léments" [5140-5976] -->
+<h2 class="sectionedit1264"><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>
+<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>
+<div class="table sectionedit1265"><table class="inline">
+ <tr class="row0">
+ <th class="col0 centeralign"> Item </th><th class="col1 centeralign"> Allowed Value </th><th class="col2 centeralign"> Explanation </th><th class="col3 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 class="row1">
+ <td class="col0 centeralign"> x1 </td><td class="col1 centeralign"> 1/100th mils </td><td class="col2 centeralign"> x(1st point) </td><td class="col3 leftalign"> </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 class="row2">
+ <td class="col0 centeralign"> y1 </td><td class="col1 centeralign"> 1/100th mils </td><td class="col2 centeralign"> y(1st point) </td><td class="col3 leftalign"> </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 class="row3">
+ <td class="col0 centeralign"> x2 </td><td class="col1 centeralign"> 1/100th mils </td><td class="col2 centeralign"> x(2nd point) </td><td class="col3 leftalign"> </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 class="row4">
+ <td class="col0 centeralign"> y2 </td><td class="col1 centeralign"> 1/100th mils </td><td class="col2 centeralign"> y(2nd point) </td><td class="col3 leftalign"> </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 class="row5">
+ <td class="col0 centeralign"> thickness </td><td class="col1 centeralign"> 1/100 mils </td><td class="col2 centeralign"> épaisseur de métal entourant le segment de ligne </td><td class="col3 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 class="row6">
+ <td class="col0 centeralign"> clearance </td><td class="col1 centeralign"> 1/100 mils </td><td class="col2 centeralign"> distance vis à vis des autres zones de cuivre sur toutes les couches </td><td class="col3 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 class="row7">
+ <td class="col0 centeralign"> mask </td><td class="col1 centeralign"> 1/100th mils </td><td class="col2 centeralign"> width of mask relief </td><td class="col3 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 class="row8">
+ <td class="col0 centeralign"> name </td><td class="col1 centeralign"> string </td><td class="col2 centeralign"> name of pad (arb. string) </td><td class="col3 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 class="row9">
+ <td class="col0 centeralign"> pad_number </td><td class="col1 centeralign"> string </td><td class="col2 centeralign"> pad # </td><td class="col3 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 class="row10">
+ <td class="col0 centeralign"> flags </td><td class="col1 centeralign"> hex value </td><td class="col2 centeralign"> xxx </td><td class="col3 leftalign"> </td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT1265 TABLE [6072-6931] -->
</div>
-<!-- SECTION "Pastilles" [5982-6937] -->
-<h2><a name="broches" id="broches">Broches</a></h2>
+<!-- EDIT1264 SECTION "Pastilles" [5977-6932] -->
+<h2 class="sectionedit1266"><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>
+<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>
+<div class="table sectionedit1267"><table class="inline">
+ <tr class="row0">
+ <th class="col0 centeralign"> Item </th><th class="col1 leftalign"> Allowed Value </th><th class="col2 centeralign"> Explanation </th><th class="col3 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 class="row1">
+ <td class="col0 centeralign"> x </td><td class="col1 centeralign"> 1/100th mils </td><td class="col2 centeralign"> pin x coord. </td><td class="col3 leftalign"> </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 class="row2">
+ <td class="col0 centeralign"> y </td><td class="col1 centeralign"> 1/100th mils </td><td class="col2 centeralign"> pin y coord. </td><td class="col3 leftalign"> </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 class="row3">
+ <td class="col0 centeralign"> thickness </td><td class="col1 centeralign"> 1/100th mils </td><td class="col2 centeralign"> copper diameter </td><td class="col3 leftalign"> </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 class="row4">
+ <td class="col0 centeralign"> clearance </td><td class="col1 centeralign"> 1/100th mils </td><td class="col2 centeralign"> 2*(cu to cu clearance) </td><td class="col3 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 class="row5">
+ <td class="col0 centeralign"> mask </td><td class="col1 centeralign"> 1/100th mils </td><td class="col2 centeralign"> diameter of mask aperture </td><td class="col3 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 class="row6">
+ <td class="col0 centeralign"> drillholedia </td><td class="col1 centeralign"> 1/100th mils </td><td class="col2 centeralign"> dia. of hole </td><td class="col3 leftalign"> </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 class="row7">
+ <td class="col0 centeralign"> name </td><td class="col1 centeralign"> string </td><td class="col2 centeralign"> arb. pin name </td><td class="col3 leftalign"> </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 class="row8">
+ <td class="col0 centeralign"> number </td><td class="col1 centeralign"> decimal integer </td><td class="col2 centeralign"> pin number used by nets/rats </td><td class="col3 leftalign"> </td>
</tr>
- <tr>
- <td class="centeralign"> flags </td><td class="centeralign"> hex </td><td class="centeralign"> xxx </td><td class="rightalign"> </td>
+ <tr class="row9">
+ <td class="col0 centeralign"> flags </td><td class="col1 centeralign"> hex </td><td class="col2 centeralign"> xxx </td><td class="col3 leftalign"> </td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT1267 TABLE [7027-7633] -->
</div>
-<!-- SECTION "Broches" [6938-7639] -->
-<h2><a name="exemples" id="exemples">Exemples</a></h2>
+<!-- EDIT1266 SECTION "Broches" [6933-7634] -->
+<h2 class="sectionedit1268"><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>
@@ -443,5 +421,5 @@
</ul>
</div>
-<!-- SECTION "Exemples" [7640-] --></body>
+<!-- EDIT1268 SECTION "Exemples" [7635-] --></body>
</html>
diff --git a/docs/wiki/geda-pcb-quick_reference.html b/docs/wiki/geda-pcb-quick_reference.html
index 45ce5fd..a3ac41f 100644
--- a/docs/wiki/geda-pcb-quick_reference.html
+++ b/docs/wiki/geda-pcb-quick_reference.html
@@ -11,272 +11,308 @@
</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>
+<h1 class="sectionedit1269"><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>
+<!-- EDIT1269 SECTION "PCB: Quick Reference" [1-36] -->
+<h2 class="sectionedit1270"><a name="default_key_mapping" id="default_key_mapping">Default 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>
+<!-- EDIT1270 SECTION "Default Key Mapping" [37-69] -->
+<h3 class="sectionedit1271"><a name="all_keystrokes" id="all_keystrokes">All 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>
+<div class="table sectionedit1272"><table class="inline">
+ <tr class="row0">
+ <th class="col0 centeralign"> Key </th><th class="col1 leftalign"> Mnenonic </th><th class="col2 leftalign"> Description </th>
</tr>
- <tr>
- <td class="centeralign"> esc </td><td class="leftalign"> panner </td><td> enter panning mode </td>
+ <tr class="row1">
+ <td class="col0 centeralign"> esc </td><td class="col1 leftalign"> select </td><td class="col2 leftalign"> enter select mode (same as [space], or [F11]) </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 class="row2">
+ <td class="col0 centeralign"> esc </td><td class="col1 leftalign"> end of action </td><td class="col2 leftalign"> terminate the current action, e.g. stop drawing tracks </td>
</tr>
- <tr>
- <td class="centeralign"> space </td><td class="leftalign"> select </td><td class="leftalign"> enter select mode </td>
+ <tr class="row3">
+ <td class="col0 centeralign"> insert </td><td class="col1 leftalign"> insert point </td><td class="col2 leftalign"> enter insert point mode. Click and drag on track to insert a point </td>
</tr>
- <tr>
- <td class="centeralign"> tab </td><td class="leftalign"> flip view </td><td class="leftalign"> view: flip board </td>
+ <tr class="row4">
+ <td class="col0 centeralign"> return </td><td class="col1 leftalign"> click </td><td class="col2 leftalign"> same as a click on the left mouse button </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 class="row5">
+ <td class="col0 centeralign"> space </td><td class="col1 leftalign"> select </td><td class="col2 leftalign"> enter select mode (same as [exs], or [F11]) </td>
</tr>
- <tr>
- <td class="centeralign"> \ </td><td class="leftalign"> thin-draw </td><td class="leftalign"> toggles thin draw mode </td>
+ <tr class="row6">
+ <td class="col0 centeralign"> tab </td><td class="col1 leftalign"> flip up/down </td><td class="col2 leftalign"> view: vertical flip </td>
</tr>
- <tr>
- <td class="centeralign"> shift-alt-a </td><td class="leftalign"> unselect </td><td class="leftalign"> clear selection </td>
+ <tr class="row7">
+ <td class="col0 centeralign"> shift-tab </td><td class="col1 leftalign"> flip left/right </td><td class="col2 leftalign"> view: horizontal flip </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 class="row8">
+ <td class="col0 centeralign"> ctrl-shift-tab </td><td class="col1 leftalign"> far side </td><td class="col2 leftalign"> view: exchange the roles of front side and far side </td>
</tr>
- <tr>
- <td class="centeralign"> shift-b </td><td class="leftalign"> flip view </td><td class="leftalign"> view: flip board </td>
+ <tr class="row9">
+ <td class="col0 centeralign"> del </td><td class="col1 leftalign"> delete </td><td class="col2"> delete object under the mouse cursor </td>
</tr>
- <tr>
- <td class="centeralign"> c </td><td class="leftalign"> center </td><td class="leftalign"> view: center display at cursor position </td>
+ <tr class="row10">
+ <td class="col0 centeralign"> shift-del </td><td class="col1 leftalign"> del-sel </td><td class="col2"> delete objects in selection </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 class="row11">
+ <td class="col0 centeralign"> backspace </td><td class="col1 leftalign"> del-sel </td><td class="col2"> delete objects in selection </td>
</tr>
- <tr>
- <td class="centeralign"> d </td><td class="leftalign"> display name </td><td class="leftalign"> display pin or pad name </td>
+ <tr class="row12">
+ <td class="col0 centeralign"> shift-backspace </td><td class="col1 leftalign"> del-copper </td><td class="col2 leftalign"> deletes connected copper under the cursor. Rats are considered a connection. </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 class="row13">
+ <td class="col0 centeralign"> | </td><td class="col1 leftalign"> thin-draw </td><td class="col2 leftalign"> toggles thin draw mode </td>
</tr>
- <tr>
- <td class="centeralign"> e </td><td> eliminate rats</td><td class="leftalign"> delete all rats </td>
+ <tr class="row14">
+ <td class="col0 centeralign"> a </td><td class="col1 leftalign"> set same </td><td class="col2 leftalign"> read the parameters to use for new objects from the object below the cursor. </td>
</tr>
- <tr>
- <td class="centeralign"> shift-e </td><td class="leftalign"> eliminate some rats </td><td class="leftalign"> delete selected rats </td>
+ <tr class="row15">
+ <td class="col0 centeralign"> alt-a </td><td class="col1 leftalign"> select-all </td><td class="col2 leftalign"> select all objects on active layers. Deactivated layers are ignored. </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 class="row16">
+ <td class="col0 centeralign"> shift-alt-a </td><td class="col1 leftalign"> unselect </td><td class="col2 leftalign"> clear selection </td>
</tr>
- <tr>
- <td class="centeralign"> shift-f </td><td class="leftalign"> un-find </td><td class="leftalign"> un-highlight found connections </td>
+ <tr class="row17">
+ <td class="col0 centeralign"> b </td><td class="col1 leftalign"> to other side </td><td class="col2 leftalign"> flip object to the other side of the board </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 class="row18">
+ <td class="col0 centeralign"> c </td><td class="col1 leftalign"> center </td><td class="col2 leftalign"> view: center display at cursor position </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 class="row19">
+ <td class="col0 centeralign"> ctrl-c </td><td class="col1"> copy to buffer</td><td class="col2 leftalign"> copy selection to buffer and unselect </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 class="row20">
+ <td class="col0 centeralign"> d </td><td class="col1 leftalign"> display name </td><td class="col2 leftalign"> display pin or pad name </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 class="row21">
+ <td class="col0 centeralign"> shift-d </td><td class="col1 leftalign"> pinout dialog </td><td class="col2 leftalign"> open pinout window for element under mouse cursor </td>
</tr>
- <tr>
- <td class="centeralign"> j </td><td class="leftalign"> lineclear </td><td class="leftalign"> toggles line clears polygon </td>
+ <tr class="row22">
+ <td class="col0 centeralign"> e </td><td class="col1"> eliminate rats</td><td class="col2 leftalign"> delete all rats </td>
</tr>
- <tr>
- <td class="centeralign"> k </td><td class="leftalign"> klearance </td><td class="leftalign"> increment clearance (soldermask to copper edge) </td>
+ <tr class="row23">
+ <td class="col0 centeralign"> shift-e </td><td class="col1 leftalign"> eliminate some rats </td><td class="col2 leftalign"> delete selected rats </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 class="row24">
+ <td class="col0 centeralign"> f </td><td class="col1 leftalign"> find </td><td class="col2 leftalign"> highlight connections to object under mouse cursor </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 class="row25">
+ <td class="col0 centeralign"> shift-f </td><td class="col1 leftalign"> un-find </td><td class="col2 leftalign"> un-highlight found connections </td>
</tr>
- <tr>
- <td class="centeralign"> shift-l </td><td class="leftalign"> decrease line </td><td> reduce the current linewidth </td>
+ <tr class="row26">
+ <td class="col0 centeralign"> g </td><td class="col1 leftalign"> incr grid mil </td><td class="col2 leftalign"> increment grid by configured imperial increment </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 class="row27">
+ <td class="col0 centeralign"> shift-g </td><td class="col1 leftalign"> decr grid mil </td><td class="col2 leftalign"> decrement grid by configured imperial increment </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 class="row28">
+ <td class="col0 centeralign"> ctrl-g </td><td class="col1 leftalign"> incr grid mm </td><td class="col2 leftalign"> increment grid by configured metric increment </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 class="row29">
+ <td class="col0 centeralign"> ctrl-shift-g </td><td class="col1 leftalign"> decr grid mm </td><td class="col2 leftalign"> decrement grid by configured metric increment </td>
</tr>
- <tr>
- <td class="centeralign"> n </td><td class="leftalign"> name </td><td> show object refdes / pin number at mouse pointer </td>
+ <tr class="row30">
+ <td class="col0 centeralign"> h </td><td class="col1 leftalign"> hide </td><td class="col2"> toggle the visiblity of the refdes or value attached to the comonent under the cursor </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 class="row31">
+ <td class="col0 centeralign"> shift-h </td><td class="col1 leftalign"> hide sel </td><td class="col2 leftalign"> toggle the visiblity of the refdes or value attached to selected components </td>
</tr>
- <tr>
- <td class="centeralign"> o </td><td class="leftalign"> optimize rats </td><td> optimize and redraw all rats </td>
+ <tr class="row32">
+ <td class="col0 centeralign"> ctrl-h </td><td class="col1 leftalign"> holeplate </td><td class="col2 leftalign"> toggle plating of a via. Used to produce non metalized mounting holes </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 class="row33">
+ <td class="col0 centeralign"> j </td><td class="col1 leftalign"> lineclear </td><td class="col2 leftalign"> toggle the polygon clear flag of the line under the cursor </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 class="row34">
+ <td class="col0 centeralign"> shift-j </td><td class="col1 leftalign"> lineclear sel </td><td class="col2 leftalign"> toggle the polygon clear flag of selected lines </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 class="row35">
+ <td class="col0 centeralign"> k </td><td class="col1 leftalign"> klear </td><td class="col2 leftalign"> increment clearance (soldermask to copper edge) </td>
</tr>
- <tr>
- <td class="centeralign"> ctrl-r </td><td class="leftalign"> report </td><td class="leftalign"> show object report </td>
+ <tr class="row36">
+ <td class="col0 centeralign"> shift-k </td><td class="col1 leftalign"> klear (-) </td><td class="col2 leftalign"> decrement clearance (soldermask to copper edge (NOTE: can go negative!)) </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 class="row37">
+ <td class="col0 centeralign"> ctrl-k </td><td class="col1 leftalign"> klear sel </td><td class="col2 leftalign"> increment clearance of selected objects (soldermask to copper edge) </td>
</tr>
- <tr>
- <td class="centeralign"> s </td><td class="leftalign"> size </td><td class="leftalign"> increment size </td>
+ <tr class="row38">
+ <td class="col0 centeralign"> shift-ctrl-k </td><td class="col1 leftalign"> klear sel (-) </td><td class="col2 leftalign"> decrement clearance of selected objects (soldermask to copper edge) </td>
</tr>
- <tr>
- <td class="centeralign"> shift-s </td><td class="leftalign"> size (-) </td><td class="leftalign"> decrement size </td>
+ <tr class="row39">
+ <td class="col0 centeralign"> l </td><td class="col1 leftalign"> increase line </td><td class="col2 leftalign"> increment width of the line tool, adds to the settings of the current line style </td>
</tr>
- <tr>
- <td class="centeralign"> alt-s </td><td class="leftalign"> sizehole </td><td class="leftalign"> increase the hole size </td>
+ <tr class="row40">
+ <td class="col0 centeralign"> shift-l </td><td class="col1 leftalign"> decrease line </td><td class="col2"> reduce the current linewidth </td>
</tr>
- <tr>
- <td class="centeralign"> alt-shift-s </td><td class="leftalign"> sizehole (-) </td><td class="leftalign"> decrease the hole size </td>
+ <tr class="row41">
+ <td class="col0 centeralign"> m </td><td class="col1 leftalign"> move to layer </td><td class="col2 leftalign"> move the object under the cursor to the current layer </td>
</tr>
- <tr>
- <td class="centeralign"> ctrl-s </td><td class="leftalign"> sizehole </td><td class="leftalign"> increase the hole size </td>
+ <tr class="row42">
+ <td class="col0 centeralign"> shift-m </td><td class="col1 leftalign"> move selection to layer </td><td class="col2 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-shift-s </td><td class="leftalign"> sizehole (-) </td><td class="leftalign"> decrease the hole size </td>
+ <tr class="row43">
+ <td class="col0 centeralign"> ctrl-m </td><td class="col1 leftalign"> move origin </td><td class="col2"> set the origin to the current position of the mouse pointer </td>
</tr>
- <tr>
- <td class="centeralign"> v </td><td class="leftalign"> view extents </td><td class="leftalign"> global view of working area </td>
+ <tr class="row44">
+ <td class="col0 centeralign"> n </td><td class="col1 leftalign"> name </td><td class="col2"> show object refdes / pin number at mouse pointer </td>
</tr>
- <tr>
- <td class="centeralign"> z </td><td class="leftalign"> zoom </td><td class="leftalign"> view: zoom in </td>
+ <tr class="row45">
+ <td class="col0 centeralign"> shift-n </td><td class="col1 leftalign"> next </td><td class="col2"> Select the shortest unselected rat on the board </td>
</tr>
- <tr>
- <td class="centeralign"> shift-z </td><td class="leftalign"> un-zoom </td><td class="leftalign"> view: zoom out </td>
+ <tr class="row46">
+ <td class="col0 centeralign"> o </td><td class="col1 leftalign"> optimize rats </td><td class="col2"> optimize and redraw all rats </td>
</tr>
- <tr>
- <td class="centeralign"> F1 </td><td class="leftalign"> via </td><td> enter via tool </td>
+ <tr class="row47">
+ <td class="col0 centeralign"> shift-o </td><td class="col1 leftalign"> optimize some rats </td><td class="col2"> optimize and redraw selected nets only </td>
</tr>
- <tr>
- <td class="centeralign"> F2 </td><td class="leftalign"> line </td><td class="leftalign"> enter line tool </td>
+ <tr class="row48">
+ <td class="col0 centeralign"> ctrl-o </td><td class="col1 leftalign"> octagon </td><td class="col2 leftalign"> toggle the octagon flag of the object under the cursor </td>
</tr>
- <tr>
- <td class="centeralign"> F3 </td><td class="leftalign"> arc </td><td> enter arc tool </td>
+ <tr class="row49">
+ <td class="col0 centeralign"> shift-p </td><td class="col1 leftalign"> polygon close </td><td class="col2 leftalign"> connect the first point of a polygon with the last </td>
</tr>
- <tr>
- <td class="centeralign"> F4 </td><td class="leftalign"> text </td><td> enter text tool </td>
+ <tr class="row50">
+ <td class="col0 centeralign"> q </td><td class="col1 leftalign"> square toggle </td><td class="col2 leftalign"> toggle square/round corners on pads </td>
</tr>
- <tr>
- <td class="centeralign"> F5 </td><td class="leftalign"> rectangle </td><td> enter rectangle tool</td>
+ <tr class="row51">
+ <td class="col0 centeralign"> shift-r </td><td class="col1 leftalign"> redo </td><td class="col2 leftalign"> redo what was undone with undo </td>
</tr>
- <tr>
- <td class="centeralign"> F6 </td><td class="leftalign"> polygon </td><td> enter polygon tool </td>
+ <tr class="row52">
+ <td class="col0 centeralign"> ctrl-r </td><td class="col1 leftalign"> report </td><td class="col2 leftalign"> show object report </td>
</tr>
- <tr>
- <td class="centeralign"> F7 </td><td class="leftalign"> buffer </td><td> enter buffer mode </td>
+ <tr class="row53">
+ <td class="col0 centeralign"> s </td><td class="col1 leftalign"> size </td><td class="col2 leftalign"> increment size of the object under the cursor </td>
</tr>
- <tr>
- <td class="centeralign"> F8 </td><td class="leftalign"> delete </td><td> enter remove mode </td>
+ <tr class="row54">
+ <td class="col0 centeralign"> shift-s </td><td class="col1 leftalign"> size (-) </td><td class="col2 leftalign"> decrement size of the object under the cursor </td>
</tr>
- <tr>
- <td class="centeralign"> F9 </td><td class="leftalign"> rotate </td><td class="leftalign"> enter rotate mode </td>
+ <tr class="row55">
+ <td class="col0 centeralign"> alt-s </td><td class="col1 leftalign"> sizehole </td><td class="col2 leftalign"> increase the hole of the object under the cursor </td>
</tr>
- <tr>
- <td class="centeralign"> F10 </td><td class="leftalign"> file menu </td><td> file menu </td>
+ <tr class="row56">
+ <td class="col0 centeralign"> alt-shift-s </td><td class="col1 leftalign"> sizehole (-) </td><td class="col2 leftalign"> decrease the hole of the object under the cursor </td>
</tr>
- <tr>
- <td class="centeralign"> F11 </td><td class="leftalign"> select </td><td class="leftalign"> enter select mode (same as [space]) </td>
+ <tr class="row57">
+ <td class="col0 centeralign"> ctrl-s </td><td class="col1 leftalign"> sizehole </td><td class="col2 leftalign"> increase the hole of the object under the cursor </td>
</tr>
- <tr>
- <td class="centeralign"> F12 </td><td class="leftalign"> lock </td><td> enter lock mode </td>
+ <tr class="row58">
+ <td class="col0 centeralign"> ctrl-shift-s </td><td class="col1 leftalign"> sizehole (-) </td><td class="col2 leftalign"> decrease the hole size </td>
</tr>
-</table>
-
+ <tr class="row59">
+ <td class="col0 centeralign"> t </td><td class="col1"> text tool size </td><td class="col2 leftalign"> increase the size of new text by 10 mil </td>
+ </tr>
+ <tr class="row60">
+ <td class="col0 centeralign"> shift-t </td><td class="col1"> text tool size (-)</td><td class="col2 leftalign"> decrease the size of new text by 10 mil </td>
+ </tr>
+ <tr class="row61">
+ <td class="col0 centeralign"> v </td><td class="col1 leftalign"> view extents </td><td class="col2 leftalign"> global view of working area </td>
+ </tr>
+ <tr class="row62">
+ <td class="col0 centeralign"> shift-v </td><td class="col1 leftalign"> via tool dia </td><td class="col2 leftalign"> increase the diameter of new vias by 5 mil </td>
+ </tr>
+ <tr class="row63">
+ <td class="col0 centeralign"> ctrl-shift-v </td><td class="col1"> via tool dia (-)</td><td class="col2 leftalign"> decrease the diameter of new vias by 5 mil </td>
+ </tr>
+ <tr class="row64">
+ <td class="col0 centeralign"> alt-v </td><td class="col1 leftalign"> via tool drill </td><td class="col2 leftalign"> increase the drill diameter of new vias by 5 mil </td>
+ </tr>
+ <tr class="row65">
+ <td class="col0 centeralign"> alt-shift-v </td><td class="col1"> via tool drill (-) </td><td class="col2 leftalign"> decrease the drill diameter of new vias by 5 mil </td>
+ </tr>
+ <tr class="row66">
+ <td class="col0 centeralign"> z </td><td class="col1 leftalign"> zoom </td><td class="col2 leftalign"> view: zoom in </td>
+ </tr>
+ <tr class="row67">
+ <td class="col0 centeralign"> shift-z </td><td class="col1 leftalign"> un-zoom </td><td class="col2 leftalign"> view: zoom out </td>
+ </tr>
+ <tr class="row68">
+ <td class="col0 centeralign"> F1 </td><td class="col1 leftalign"> via </td><td class="col2"> enter via tool </td>
+ </tr>
+ <tr class="row69">
+ <td class="col0 centeralign"> F2 </td><td class="col1 leftalign"> line </td><td class="col2 leftalign"> enter line tool </td>
+ </tr>
+ <tr class="row70">
+ <td class="col0 centeralign"> F3 </td><td class="col1 leftalign"> arc </td><td class="col2"> enter arc tool </td>
+ </tr>
+ <tr class="row71">
+ <td class="col0 centeralign"> F4 </td><td class="col1 leftalign"> text </td><td class="col2"> enter text tool </td>
+ </tr>
+ <tr class="row72">
+ <td class="col0 centeralign"> F5 </td><td class="col1 leftalign"> rectangle </td><td class="col2"> enter rectangle tool</td>
+ </tr>
+ <tr class="row73">
+ <td class="col0 centeralign"> F6 </td><td class="col1 leftalign"> polygon </td><td class="col2"> enter polygon tool </td>
+ </tr>
+ <tr class="row74">
+ <td class="col0 centeralign"> F7 </td><td class="col1 leftalign"> buffer </td><td class="col2"> enter buffer mode </td>
+ </tr>
+ <tr class="row75">
+ <td class="col0 centeralign"> F8 </td><td class="col1 leftalign"> delete </td><td class="col2"> enter remove mode </td>
+ </tr>
+ <tr class="row76">
+ <td class="col0 centeralign"> F9 </td><td class="col1 leftalign"> rotate </td><td class="col2 leftalign"> enter rotate mode </td>
+ </tr>
+ <tr class="row77">
+ <td class="col0 centeralign"> F10 </td><td class="col1 leftalign"> file menu </td><td class="col2"> file menu </td>
+ </tr>
+ <tr class="row78">
+ <td class="col0 centeralign"> F11 </td><td class="col1 leftalign"> select </td><td class="col2 leftalign"> enter select mode (same as [space]) </td>
+ </tr>
+ <tr class="row79">
+ <td class="col0 centeralign"> F12 </td><td class="col1 leftalign"> lock </td><td class="col2"> enter lock mode </td>
+ </tr>
+</table></div>
+<!-- EDIT1272 TABLE [96-5643] -->
</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>
+<!-- EDIT1271 SECTION "All Keystrokes" [70-5644] -->
+<h3 class="sectionedit1273"><a name="viewport_keystrokes" id="viewport_keystrokes">Viewport Keystrokes</a></h3>
+<div class="level3">
+<div class="table sectionedit1274"><table class="inline">
+ <tr class="row0">
+ <th class="col0 centeralign"> Key </th><th class="col1 centeralign"> Mnenonic </th><th class="col2 leftalign"> Description </th>
</tr>
- <tr>
- <td class="centeralign"> esc </td><td class="centeralign"> panner </td><td class="rightalign"> </td>
+ <tr class="row1">
+ <td class="col0 centeralign"> v </td><td class="col1 leftalign"> view extents </td><td class="col2 leftalign"> global view of working area </td>
</tr>
- <tr>
- <td class="centeralign"> v </td><td class="centeralign"> view extents </td><td>global view of working area</td>
+ <tr class="row2">
+ <td class="col0 centeralign"> c </td><td class="col1 leftalign"> center </td><td class="col2 leftalign"> centers view on cursor </td>
</tr>
- <tr>
- <td class="centeralign"> c </td><td class="centeralign"> center </td><td>centers view on cursor</td>
+ <tr class="row3">
+ <td class="col0 centeralign"> z </td><td class="col1 leftalign"> zoom </td><td class="col2 leftalign"> zoom in </td>
</tr>
- <tr>
- <td class="centeralign"> z </td><td class="centeralign"> zoom </td><td>zoom in</td>
+ <tr class="row4">
+ <td class="col0 centeralign"> shift-z </td><td class="col1 leftalign"> un-zoom </td><td class="col2 leftalign"> zoom out </td>
</tr>
- <tr>
- <td class="centeralign"> shift-z </td><td class="centeralign"> un-zoom </td><td class="rightalign"> </td>
+ <tr class="row5">
+ <td class="col0 centeralign"> | </td><td class="col1 leftalign"> thin-draw </td><td class="col2 leftalign"> toggles thin draw mode </td>
</tr>
- <tr>
- <td class="centeralign"> \ </td><td class="centeralign"> thin-draw on/off </td><td>toggles thin draw mode</td>
+ <tr class="row6">
+ <td class="col0 centeralign"> tab </td><td class="col1 leftalign"> flip up/down </td><td class="col2 leftalign"> vertical flip </td>
</tr>
- <tr>
- <td class="centeralign"> tab </td><td class="centeralign"> flip view </td><td>flip board</td>
+ <tr class="row7">
+ <td class="col0 centeralign"> shift-tab </td><td class="col1 leftalign"> flip left/right </td><td class="col2 leftalign"> horizontal flip </td>
</tr>
- <tr>
- <td class="centeralign"> shift-b </td><td class="centeralign"> flip view </td><td>flip board</td>
+ <tr class="row8">
+ <td class="col0 centeralign"> ctrl-shift-tab </td><td class="col1 leftalign"> far side </td><td class="col2 leftalign"> exchange the roles of front and far side </td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT1274 TABLE [5676-6105] -->
</div>
-<!-- SECTION "Viewport Keystrokes" [3698-4071] -->
-<h1><a name="footprint_reference" id="footprint_reference">Footprint Reference</a></h1>
+<!-- EDIT1273 SECTION "Viewport Keystrokes" [5645-6106] -->
+<h1 class="sectionedit1275"><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>.
+The Master document for footprint creation is the <a href="http://pcb.gpleda.org/manual.html"; class="urlextern" title="http://pcb.gpleda.org/manual.html"; 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>
+<!-- EDIT1275 SECTION "Footprint Reference" [6107-6392] -->
+<h2 class="sectionedit1276"><a name="general_syntax" id="general_syntax">General syntax</a></h2>
<div class="level2">
<p>
@@ -298,140 +334,143 @@ A pcb footprint file may contain any of the following commands:
</ul>
</div>
-<!-- SECTION "General syntax" [4366-4978] -->
-<h2><a name="elements" id="elements">Elements</a></h2>
+<!-- EDIT1276 SECTION "General syntax" [6393-7005] -->
+<h2 class="sectionedit1277"><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>
+<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>
+<div class="table sectionedit1278"><table class="inline">
+ <tr class="row0">
+ <th class="col0 centeralign"> item </th><th class="col1 centeralign"> allowed value </th><th class="col2 centeralign"> explanation </th><th class="col3 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 class="row1">
+ <td class="col0 centeralign"> element_flags </td><td class="col1 centeralign"> unsigned hex value </td><td class="col2 leftalign"> </td><td class="col3 leftalign"> </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 class="row2">
+ <td class="col0 centeralign"> description </td><td class="col1 centeralign"> string </td><td class="col2 centeralign"> text description of footprint </td><td class="col3 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 class="row3">
+ <td class="col0 centeralign"> pcb name </td><td class="col1 centeralign"> string </td><td class="col2 centeralign"> refdes used on this particular pcb </td><td class="col3 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 class="row4">
+ <td class="col0 centeralign"> value </td><td class="col1 centeralign"> string </td><td class="col2 centeralign"> value of component on this particular pcb layout </td><td class="col3 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 class="row5">
+ <td class="col0 centeralign"> mark_x </td><td class="col1 centeralign"> 1/100th mils </td><td class="col2 leftalign"> </td><td class="col3 leftalign"> </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 class="row6">
+ <td class="col0 centeralign"> mark_y </td><td class="col1 centeralign"> 1/100th mils </td><td class="col2 leftalign"> </td><td class="col3 leftalign"> </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 class="row7">
+ <td class="col0 centeralign"> text_x </td><td class="col1 centeralign"> 1/100th mils </td><td class="col2 leftalign"> </td><td class="col3 leftalign"> </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 class="row8">
+ <td class="col0 centeralign"> text_y </td><td class="col1 centeralign"> 1/100th mils </td><td class="col2 leftalign"> </td><td class="col3 leftalign"> </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 class="row9">
+ <td class="col0 centeralign"> text direction </td><td class="col1 centeralign"> decimal integer </td><td class="col2 centeralign"> 0=horiz; 1=ccw90; 2=180; 3=cw90 </td><td class="col3 leftalign"> </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 class="row10">
+ <td class="col0 centeralign"> text_scale </td><td class="col1 centeralign"> decimal integer </td><td class="col2 leftalign"> </td><td class="col3 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 class="row11">
+ <td class="col0 centeralign"> text_flags </td><td class="col1 centeralign"> unsigned hex </td><td class="col2 leftalign"> </td><td class="col3 leftalign"> </td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT1278 TABLE [7162-7832] -->
</div>
-<!-- SECTION "Elements" [4979-5806] -->
-<h2><a name="pads" id="pads">Pads</a></h2>
+<!-- EDIT1277 SECTION "Elements" [7006-7833] -->
+<h2 class="sectionedit1279"><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>
+<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>
+<div class="table sectionedit1280"><table class="inline">
+ <tr class="row0">
+ <th class="col0 centeralign"> Item </th><th class="col1 centeralign"> Allowed Value </th><th class="col2 centeralign"> Explanation </th><th class="col3 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 class="row1">
+ <td class="col0 centeralign"> x1 </td><td class="col1 centeralign"> 1/100th mils </td><td class="col2 centeralign"> x(1st point) </td><td class="col3 leftalign"> </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 class="row2">
+ <td class="col0 centeralign"> y1 </td><td class="col1 centeralign"> 1/100th mils </td><td class="col2 centeralign"> y(1st point) </td><td class="col3 leftalign"> </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 class="row3">
+ <td class="col0 centeralign"> x2 </td><td class="col1 centeralign"> 1/100th mils </td><td class="col2 centeralign"> x(2nd point) </td><td class="col3 leftalign"> </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 class="row4">
+ <td class="col0 centeralign"> y2 </td><td class="col1 centeralign"> 1/100th mils </td><td class="col2 centeralign"> y(2nd point) </td><td class="col3 leftalign"> </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 class="row5">
+ <td class="col0 centeralign"> thickness </td><td class="col1 centeralign"> 1/100 mils </td><td class="col2 centeralign"> width of metal surrounding line segment </td><td class="col3 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 class="row6">
+ <td class="col0 centeralign"> clearance </td><td class="col1 centeralign"> 1/100 mils </td><td class="col2 centeralign"> distance to any other copper on any layer </td><td class="col3 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 class="row7">
+ <td class="col0 centeralign"> mask </td><td class="col1 centeralign"> 1/100th mils </td><td class="col2 centeralign"> width of mask relief </td><td class="col3 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 class="row8">
+ <td class="col0 centeralign"> name </td><td class="col1 centeralign"> string </td><td class="col2 centeralign"> name of pad (arb. string) </td><td class="col3 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 class="row9">
+ <td class="col0 centeralign"> pad_number </td><td class="col1 centeralign"> string </td><td class="col2 centeralign"> pad # </td><td class="col3 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 class="row10">
+ <td class="col0 centeralign"> flags </td><td class="col1 centeralign"> hex value </td><td class="col2 centeralign"> xxx </td><td class="col3 leftalign"> </td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT1280 TABLE [7924-8737] -->
</div>
-<!-- SECTION "Pads" [5807-6711] -->
-<h2><a name="pins" id="pins">Pins</a></h2>
+<!-- EDIT1279 SECTION "Pads" [7834-8738] -->
+<h2 class="sectionedit1281"><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>
+<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>
+<div class="table sectionedit1282"><table class="inline">
+ <tr class="row0">
+ <th class="col0 centeralign"> Item </th><th class="col1 leftalign"> Allowed Value </th><th class="col2 centeralign"> Explanation </th><th class="col3 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 class="row1">
+ <td class="col0 centeralign"> x </td><td class="col1 centeralign"> 1/100th mils </td><td class="col2 centeralign"> pin x coord. </td><td class="col3 leftalign"> </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 class="row2">
+ <td class="col0 centeralign"> y </td><td class="col1 centeralign"> 1/100th mils </td><td class="col2 centeralign"> pin y coord. </td><td class="col3 leftalign"> </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 class="row3">
+ <td class="col0 centeralign"> thickness </td><td class="col1 centeralign"> 1/100th mils </td><td class="col2 centeralign"> copper diameter </td><td class="col3 leftalign"> </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 class="row4">
+ <td class="col0 centeralign"> clearance </td><td class="col1 centeralign"> 1/100th mils </td><td class="col2 centeralign"> 2*(cu to cu clearance) </td><td class="col3 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 class="row5">
+ <td class="col0 centeralign"> mask </td><td class="col1 centeralign"> 1/100th mils </td><td class="col2 centeralign"> diameter of mask aperture </td><td class="col3 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 class="row6">
+ <td class="col0 centeralign"> drillholedia </td><td class="col1 centeralign"> 1/100th mils </td><td class="col2 centeralign"> dia. of hole </td><td class="col3 leftalign"> </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 class="row7">
+ <td class="col0 centeralign"> name </td><td class="col1 centeralign"> string </td><td class="col2 centeralign"> arb. pin name </td><td class="col3 leftalign"> </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 class="row8">
+ <td class="col0 centeralign"> number </td><td class="col1 centeralign"> decimal integer </td><td class="col2 centeralign"> pin number used by nets/rats </td><td class="col3 leftalign"> </td>
</tr>
- <tr>
- <td class="centeralign"> flags </td><td class="centeralign"> hex </td><td class="centeralign"> xxx </td><td class="rightalign"> </td>
+ <tr class="row9">
+ <td class="col0 centeralign"> flags </td><td class="col1 centeralign"> hex </td><td class="col2 centeralign"> xxx </td><td class="col3 leftalign"> </td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT1282 TABLE [8830-9436] -->
</div>
-<!-- SECTION "Pins" [6712-7410] -->
-<h2><a name="examples" id="examples">Examples</a></h2>
+<!-- EDIT1281 SECTION "Pins" [8739-9437] -->
+<h2 class="sectionedit1283"><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>
@@ -449,5 +488,47 @@ A pcb footprint file may contain any of the following commands:
</ul>
</div>
-<!-- SECTION "Examples" [7411-] --></body>
+<!-- EDIT1283 SECTION "Examples" [9438-9884] -->
+<h1 class="sectionedit1284"><a name="pcb_command_line_action_reference_abridged" id="pcb_command_line_action_reference_abridged">PCB Command Line Action Reference (abridged)</a></h1>
+<div class="level1">
+<div class="table sectionedit1285"><table class="inline">
+ <tr class="row0">
+ <td class="col0" colspan="2">:FreeRotateBuffer(degrees)</td><td class="col2">Rotate buffer arbitrarily </td>
+ </tr>
+ <tr class="row1">
+ <td class="col0" colspan="2">:MoveObject(x,y,unit) </td><td class="col2">Move Absolute (x,y,mil) or Relative(+x,-y,mil)</td>
+ </tr>
+ <tr class="row2">
+ <td class="col0" colspan="2">:ChangeClearSize(Selected,<amount>,<unit>)</td><td class="col2"> Clearance Size</td>
+ </tr>
+ <tr class="row3">
+ <td class="col0" colspan="2">:ChangeSize(SelectedPins, SIZE)</td><td class="col2"> Pin Size </td>
+ </tr>
+ <tr class="row4">
+ <td class="col0" colspan="2">:ChangeSize(SelectedLines,+N,mils)</td><td class="col2"> Line Size </td>
+ </tr>
+ <tr class="row5">
+ <td class="col0" colspan="2">:MinClearGap(Selected,<amount>,<unit>)</td><td class="col2"> Clearance Gap </td>
+ </tr>
+</table></div>
+<!-- EDIT1285 TABLE [9944-10289] --><ul>
+<li class="level1"><div class="li"> units can be specified as mm or mil.</div>
+</li>
+<li class="level1"><div class="li"> <a href="http://pcb.gpleda.org/pcb-20100929/pcb.html#Action-Reference"; class="urlextern" title="http://pcb.gpleda.org/pcb-20100929/pcb.html#Action-Reference"; rel="nofollow">Action Reference from the PCB Manual</a></div>
+</li>
+</ul>
+
+</div>
+<!-- EDIT1284 SECTION "PCB Command Line Action Reference (abridged)" [9885-10439] -->
+<h1 class="sectionedit1286"><a name="pcb_physical_layer_reference" id="pcb_physical_layer_reference">PCB Physical Layer Reference</a></h1>
+<div class="level1">
+<ul>
+<li class="level1"><div class="li"> ouline layer reference</div>
+</li>
+<li class="level1"><div class="li"> physical layer how-to (outline, direct (x,y) footprint placement, part insertion)</div>
+</li>
+</ul>
+
+</div>
+<!-- EDIT1286 SECTION "PCB Physical Layer Reference" [10440-] --></body>
</html>
diff --git a/docs/wiki/geda-pcb_footprint_naming_conventions.html b/docs/wiki/geda-pcb_footprint_naming_conventions.html
index 983826d..3232e23 100644
--- a/docs/wiki/geda-pcb_footprint_naming_conventions.html
+++ b/docs/wiki/geda-pcb_footprint_naming_conventions.html
@@ -1,4 +1,4 @@
-
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
<html>
<head>
@@ -11,41 +11,19 @@
</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="#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></ul>
-</li></ul>
-</div>
-</div>
-
-
-<h2><a name="footprint_naming_conventions" id="footprint_naming_conventions">Footprint naming conventions</a></h2>
+<h2 class="sectionedit1287"><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 PCB (and 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.
+
+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" [1-364] -->
-<h3><a name="notes" id="notes">Notes</a></h3>
+<!-- EDIT1287 SECTION "Footprint naming conventions" [1-364] -->
+<h3 class="sectionedit1288"><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>
@@ -61,8 +39,8 @@ This section describes the conventions for naming of footprints used in PCB (and
</ul>
</div>
-<!-- SECTION "Notes" [365-707] -->
-<h3><a name="integrated_circuit_packages" id="integrated_circuit_packages">Integrated circuit packages</a></h3>
+<!-- EDIT1288 SECTION "Notes" [365-707] -->
+<h3 class="sectionedit1289"><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>
@@ -86,8 +64,8 @@ This section describes the conventions for naming of footprints used in PCB (and
</ul>
</div>
-<!-- SECTION "Integrated circuit packages" [708-1576] -->
-<h3><a name="integrated_circuit_smt_packages" id="integrated_circuit_smt_packages">Integrated circuit SMT packages</a></h3>
+<!-- EDIT1289 SECTION "Integrated circuit packages" [708-1576] -->
+<h3 class="sectionedit1290"><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>
@@ -151,8 +129,8 @@ This section describes the conventions for naming of footprints used in PCB (and
</ul>
</div>
-<!-- SECTION "Integrated circuit SMT packages" [1577-4507] -->
-<h3><a name="basic_semiconductors" id="basic_semiconductors">Basic semiconductors</a></h3>
+<!-- EDIT1290 SECTION "Integrated circuit SMT packages" [1577-4507] -->
+<h3 class="sectionedit1291"><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>
@@ -164,8 +142,8 @@ This section describes the conventions for naming of footprints used in PCB (and
</ul>
</div>
-<!-- SECTION "Basic semiconductors" [4508-4910] -->
-<h3><a name="basic_smt_semiconductors" id="basic_smt_semiconductors">Basic SMT semiconductors</a></h3>
+<!-- EDIT1291 SECTION "Basic semiconductors" [4508-4910] -->
+<h3 class="sectionedit1292"><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>
@@ -179,8 +157,8 @@ This section describes the conventions for naming of footprints used in PCB (and
</ul>
</div>
-<!-- SECTION "Basic SMT semiconductors" [4911-5366] -->
-<h3><a name="passive_components" id="passive_components">Passive components</a></h3>
+<!-- EDIT1292 SECTION "Basic SMT semiconductors" [4911-5366] -->
+<h3 class="sectionedit1293"><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>
@@ -214,8 +192,8 @@ This section describes the conventions for naming of footprints used in PCB (and
</ul>
</div>
-<!-- SECTION "Passive components" [5367-6488] -->
-<h3><a name="passive_smt_components" id="passive_smt_components">Passive SMT components</a></h3>
+<!-- EDIT1293 SECTION "Passive components" [5367-6488] -->
+<h3 class="sectionedit1294"><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>
@@ -227,5 +205,5 @@ This section describes the conventions for naming of footprints used in PCB (and
</ul>
</div>
-<!-- SECTION "Passive SMT components" [6489-] --></body>
+<!-- EDIT1294 SECTION "Passive SMT components" [6489-] --></body>
</html>
diff --git a/docs/wiki/geda-pcb_footprints.html b/docs/wiki/geda-pcb_footprints.html
index 85352ff..ea1d00c 100644
--- a/docs/wiki/geda-pcb_footprints.html
+++ b/docs/wiki/geda-pcb_footprints.html
@@ -11,39 +11,25 @@
</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="clear">
-
-<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>
+<h1 class="sectionedit466"><a name="pcb_footprint_guide" id="pcb_footprint_guide">PCB Footprint Guide</a></h1>
<div class="level1">
<ul>
-<li class="level1"><div class="li"> The PCB <acronym title="Frequently Asked Questions">FAQ</acronym>: <a href="geda-pcb_tips.html" class="wikilink1" title="geda-pcb_tips.html">pcb_tips</a>. </div>
+<li class="level1"><div class="li"> Stuart Brorson's footprint <a href="http://www.brorson.com/gEDA/land_patterns_20070805.pdf"; class="urlextern" title="http://www.brorson.com/gEDA/land_patterns_20070805.pdf"; rel="nofollow">footprint guide</a></div>
+</li>
+<li class="level1"><div class="li"> <a href="http://pcb.gpleda.org/pcb-cvs/pcb.html"; class="urlextern" title="http://pcb.gpleda.org/pcb-cvs/pcb.html"; rel="nofollow">PCB manual</a></div>
+</li>
+<li class="level1"><div class="li"> The PCB <acronym title="Frequently Asked Questions">FAQ</acronym>: <a href="geda-pcb_tips.html" class="wikilink1" title="geda-pcb_tips.html">pcb_tips</a>.</div>
+</li>
+<li class="level1"><div class="li"> The PCB Quick-Reference has info on <a href="geda-pcb-quick_reference.html#footprint_reference" class="wikilink1" title="geda-pcb-quick_reference.html">footprints</a></div>
</li>
<li class="level1"><div class="li"> <a href="geda-pcb_footprint_naming_conventions.html" class="wikilink1" title="geda-pcb_footprint_naming_conventions.html">PCB Footprint Naming Conventions</a> : read this to learn how to <em>name</em> your footprint files.</div>
</li>
</ul>
</div>
-<!-- SECTION "PCB Footprint Guide" [4-183] -->
-<h3><a name="footprint_basics" id="footprint_basics">Footprint basics</a></h3>
+<!-- EDIT466 SECTION "PCB Footprint Guide" [4-445] -->
+<h3 class="sectionedit467"><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>
@@ -52,7 +38,7 @@
</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 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>
@@ -61,8 +47,8 @@
</ul>
</div>
-<!-- SECTION "Footprint basics" [184-713] -->
-<h3><a name="pcb_footprint_faq" id="pcb_footprint_faq">PCB Footprint FAQ</a></h3>
+<!-- EDIT467 SECTION "Footprint basics" [446-975] -->
+<h3 class="sectionedit468"><a name="pcb_footprint_faq" id="pcb_footprint_faq">PCB Footprint FAQ</a></h3>
<div class="level3">
</div>
@@ -76,7 +62,7 @@
<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."
+â??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>
@@ -94,7 +80,7 @@ Simply add a pad on top of your pin and give them the same pin-number. If the s
<div class="level4">
<p>
-â??Odd as it sounds, this can be necessary for some edge connectors. … but how do you do it???"
+â??Odd as it sounds, this can be necessary for some edge connectors. â?¦ but how do you do it???â??
</p>
</div>
@@ -126,12 +112,13 @@ Simply add a pad on top of your pin and give them the same pin-number. If the s
</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!
+
+<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" [714-2011] -->
-<h2><a name="sharing_pcb_footprints" id="sharing_pcb_footprints">Sharing PCB Footprints</a></h2>
+<!-- EDIT468 SECTION "PCB Footprint FAQ" [976-2273] -->
+<h2 class="sectionedit469"><a name="sharing_pcb_footprints" id="sharing_pcb_footprints">Sharing PCB Footprints</a></h2>
<div class="level2">
</div>
@@ -140,11 +127,12 @@ Simply add a pad on top of your pin and give them the same pin-number. If the s
<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>
+
+* 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>
+* 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>
@@ -152,5 +140,5 @@ Simply add a pad on top of your pin and give them the same pin-number. If the s
</p>
</div>
-<!-- SECTION "Sharing PCB Footprints" [2012-] --></body>
+<!-- EDIT469 SECTION "Sharing PCB Footprints" [2274-] --></body>
</html>
diff --git a/docs/wiki/geda-pcb_funding_sow-fwdann_ideas.html b/docs/wiki/geda-pcb_funding_sow-fwdann_ideas.html
index f0072a4..59dc390 100644
--- a/docs/wiki/geda-pcb_funding_sow-fwdann_ideas.html
+++ b/docs/wiki/geda-pcb_funding_sow-fwdann_ideas.html
@@ -12,52 +12,69 @@
<body>
-
-<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>
+<h1 class="sectionedit1"><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>
+
+<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>
+<!-- EDIT1 SECTION "PCB SoW: Forward Annotation: Ideas, commentary, and examples from users" [1-337] -->
+<h2 class="sectionedit2"><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:
+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.
+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 ;).
+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.
+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.
+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.
+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.
+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.
+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>
+<!-- EDIT2 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
index 326c2b3..62ed20a 100644
--- a/docs/wiki/geda-pcb_funding_sow-gui_ideas.html
+++ b/docs/wiki/geda-pcb_funding_sow-gui_ideas.html
@@ -12,17 +12,21 @@
<body>
-
-<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>
+<h1 class="sectionedit3"><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>
+
+<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.
+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>
diff --git a/docs/wiki/geda-pcb_funding_sow.html b/docs/wiki/geda-pcb_funding_sow.html
index 8e933ee..28d1de9 100644
--- a/docs/wiki/geda-pcb_funding_sow.html
+++ b/docs/wiki/geda-pcb_funding_sow.html
@@ -11,51 +11,39 @@
</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>
+<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>
+<h2 class="sectionedit485"><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.
+The open-source layout tool <a href="http://pcb.gpleda.org/"; class="urlextern" title="http://pcb.gpleda.org/"; 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:
+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>
+<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>
@@ -65,7 +53,7 @@ For a variety of reasons, many electronics designers find PCBâ??s user interface
</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 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>
@@ -84,14 +72,19 @@ For a variety of reasons, many electronics designers find PCBâ??s user interface
</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:
+
+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 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>
@@ -100,22 +93,27 @@ For a variety of reasons, many electronics designers find PCBâ??s user interface
</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.
+
+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>
+<!-- EDIT485 SECTION "Background and motivation" [86-4745] -->
+<h2 class="sectionedit486"><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.
+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>
+<!-- EDIT486 SECTION "Statement of work" [4746-5135] -->
+<h3 class="sectionedit487"><a name="general_guidelines" id="general_guidelines">General guidelines</a></h3>
<div class="level3">
</div>
@@ -124,7 +122,8 @@ This section provides descriptions of what work is desired in each area of PCB
<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.
+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>
@@ -171,17 +170,20 @@ Hooks for support on Windows systems are outside the scope of this project. How
<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).
+.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>
+<!-- EDIT487 SECTION "General guidelines" [5136-7257] -->
+<h3 class="sectionedit488"><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>
+
+<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>
@@ -190,7 +192,11 @@ Hooks for support on Windows systems are outside the scope of this project. How
<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:
+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>
@@ -210,23 +216,43 @@ The goal of forward annotation is to read the design information output from e.g
</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.
+
+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.
+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.)
+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.)
+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.
+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>
@@ -248,11 +274,11 @@ Once the forward annotation changes are complete, the following use cases should
</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 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 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 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>
@@ -260,12 +286,13 @@ Once the forward annotation changes are complete, the following use cases should
</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 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>
+
+<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>
@@ -274,7 +301,7 @@ Once the forward annotation changes are complete, the following use cases should
</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 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>
@@ -305,14 +332,15 @@ Once the forward annotation changes are complete, the following use cases should
<div class="level4">
<p>
-Some of the support for forward annotation already exists. Specifically, many actions are already supported. Therefore, this project involves:
+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 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>
@@ -320,19 +348,23 @@ Some of the support for forward annotation already exists. Specifically, many a
<hr />
</div>
-<!-- SECTION "Forward annotation upgrade" [7263-12536] -->
-<h3><a name="gui_modernization" id="gui_modernization">GUI modernization</a></h3>
+<!-- EDIT488 SECTION "Forward annotation upgrade" [7258-12531] -->
+<h3 class="sectionedit489"><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>
+
+<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:
+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 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>
@@ -344,12 +376,13 @@ The basic goal is to make the upgraded PCB behave exactly as an inexperienced us
</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 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.
+
+If the descriptions in this specification are ambiguous or unclear, use the behaviors implemented in gschem as the preferred example.
</p>
</div>
@@ -358,7 +391,13 @@ The basic goal is to make the upgraded PCB behave exactly as an inexperienced us
<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.
+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>
@@ -394,9 +433,9 @@ The following actions should be modified to support a â??noun/verbâ?? actions, i
</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>
+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>
@@ -452,12 +491,15 @@ This project involves:
<hr />
</div>
-<!-- SECTION "GUI modernization" [12537-18472] -->
-<h3><a name="footprint_editor_implementation" id="footprint_editor_implementation">Footprint editor implementation</a></h3>
+<!-- EDIT489 SECTION "GUI modernization" [12532-18467] -->
+<h3 class="sectionedit490"><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:
+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>
@@ -476,17 +518,18 @@ Optionally, features involving editing footprints via the buffer will be removed
<div class="level4">
<p>
-There are two ways to invoke the footprint editor:
+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 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 class="level2"><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.
+
+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>
@@ -499,7 +542,8 @@ As a fourth possibility, allow a mode similar to gschem, where a library browser
<div class="level4">
<p>
-The footprint editor should be a graphical drawing environment similar to that presented by PCB for layout editing.
+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>
@@ -511,7 +555,8 @@ The footprint editor should be a graphical drawing environment similar to that p
</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.
+
+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>
@@ -520,11 +565,19 @@ The footprint editor should be a graphical drawing environment similar to that p
<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.
+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.
+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>
@@ -533,7 +586,11 @@ Therefore, when the user is done editing his footprint, there should be only one
<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.
+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>
@@ -542,12 +599,14 @@ Once the footprint editing session is done, the user may leave the editor and re
<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:
+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 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>
@@ -580,8 +639,8 @@ This project involves:
<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>
+<!-- EDIT490 SECTION "Footprint editor implementation" [18468-24056] -->
+<h3 class="sectionedit491"><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>
@@ -590,7 +649,13 @@ This project involves:
<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:
+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>
@@ -605,7 +670,7 @@ Currently, PCBâ??s internal data structures only â??knowâ?? about metal and silk
</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 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>
@@ -636,8 +701,8 @@ This project involves:
<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>
+<!-- EDIT491 SECTION "Upgrade of layer and design objects" [24057-26082] -->
+<h3 class="sectionedit492"><a name="design_rule_checking_upgrade" id="design_rule_checking_upgrade">Design Rule Checking Upgrade</a></h3>
<div class="level3">
</div>
@@ -646,23 +711,41 @@ This project involves:
<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
+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.
+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.
+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.
+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.
+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>
@@ -685,7 +768,8 @@ Similarly, weâ??d need to ensure that removing or changing objects on the board
</ol>
<p>
- <strong>Automatic DRC</strong>
+
+<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>
@@ -723,12 +807,17 @@ This project involves:
<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>
+<!-- EDIT492 SECTION "Design Rule Checking Upgrade" [26083-29268] -->
+<h3 class="sectionedit493"><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
+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>
@@ -747,14 +836,15 @@ validate these estimations and negotiate his own billing rate before he agrees t
</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 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
+Total duration: 16 days = 128 hours.
+Cost: $6400
</p>
</div>
@@ -777,7 +867,8 @@ Total duration: 16 days = 128 hours. Cost: $6400
</ol>
<p>
-Total duration: 26 days = 208 hours Cost: $10400
+Total duration: 26 days = 208 hours
+Cost: $10400
</p>
</div>
@@ -796,7 +887,8 @@ Total duration: 26 days = 208 hours Cost: $10400
</ol>
<p>
-Total duration: 14 days = 112 hours. Cost: $5600
+Total duration: 14 days = 112 hours.
+Cost: $5600
</p>
</div>
@@ -817,7 +909,8 @@ Total duration: 14 days = 112 hours. Cost: $5600
</ol>
<p>
-Total duration: 20 days = 160 hours. Cost: $8000
+Total duration: 20 days = 160 hours.
+Cost: $8000
</p>
</div>
@@ -836,9 +929,11 @@ Total duration: 20 days = 160 hours. Cost: $8000
</ol>
<p>
-Total duration: 10 days = 80 hours. Cost: $4000
+Total duration: 10 days = 80 hours.
+Cost: $4000
+
</p>
</div>
-<!-- SECTION "Project milestones, duration, and budget estimates" [29274-] --></body>
+<!-- EDIT493 SECTION "Project milestones, duration, and budget estimates" [29269-] --></body>
</html>
diff --git a/docs/wiki/geda-pcb_mp.html b/docs/wiki/geda-pcb_mp.html
index ed86825..71d69f7 100644
--- a/docs/wiki/geda-pcb_mp.html
+++ b/docs/wiki/geda-pcb_mp.html
@@ -12,9 +12,7 @@
<body>
-
-
-<h1><a name="pcb_man-page" id="pcb_man-page">PCB man-page</a></h1>
+<h1 class="sectionedit502"><a name="pcb_man-page" id="pcb_man-page">PCB man-page</a></h1>
<div class="level1">
<pre class="code">PCB(1) PCB(1)
diff --git a/docs/wiki/geda-pcb_tips.fr.html b/docs/wiki/geda-pcb_tips.fr.html
index a1ba425..ed306ba 100644
--- a/docs/wiki/geda-pcb_tips.fr.html
+++ b/docs/wiki/geda-pcb_tips.fr.html
@@ -11,215 +11,124 @@
</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>
+<h1 class="sectionedit506"><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>
+<!-- EDIT506 SECTION "Outils PCB" [1-26] -->
+<h2 class="sectionedit507"><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>)
+Le <a href="http://pcb.gpleda.org/pcb-cvs/pcb.html"; class="urlextern" title="http://pcb.gpleda.org/pcb-cvs/pcb.html"; rel="nofollow">manuel de pcb</a> contient une description concise de l'interface utilisateur dans la section <a href="http://pcb.gpleda.org/pcb-cvs/pcb.html#Getting-Started"; class="urlextern" title="http://pcb.gpleda.org/pcb-cvs/pcb.html#Getting-Started"; rel="nofollow">«·Getting Started·» </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>
+<!-- EDIT507 SECTION "Où puis-je lire les bases sur l'utilisation de pcb?" [27-313] -->
+<h2 class="sectionedit508"><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 class="level1"><div class="li"> Débutez en lisant <a href="http://pcb.gpleda.org/bugs.html"; class="urlextern" title="http://pcb.gpleda.org/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 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 class="level1"><div class="li"> Vérifiez si le problème est déjà répertorié dans le <a href="http://launchpad.net/pcb/+bugs"; class="urlextern" title="http://launchpad.net/pcb/+bugs"; rel="nofollow">bug tracking system de pcb</a>. Si ce n'est pas le cas; <a href="http://launchpad.net/pcb/+filebug"; class="urlextern" title="http://launchpad.net/pcb/+filebug"; rel="nofollow">émettez un rapport de bogue</a>. 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 class="level1"><div class="li"> Finallement, avec tous les projets open source ouverts, vous pourriez muscler vos muscles de phrogrammation 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://launchpad.net/pcb/+bugs"; class="urlextern" title="http://launchpad.net/pcb/+bugs"; 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>
+<!-- EDIT508 SECTION "J'ai trouvé un bogue·! Que puis-je y faire·?" [314-1564] -->
+<h2 class="sectionedit509"><a name="comment_configurer_les_regles_du_fabricant_a_utiliser_ie_diametres_de_percage_specification_des_largeurs_espacements_des_pistes" id="comment_configurer_les_regles_du_fabricant_a_utiliser_ie_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>.
+Ce sujet est couvert dans la documentation disponible sur <a href="http://pcb.gpleda.org/manual.html"; class="urlextern" title="http://pcb.gpleda.org/manual.html"; 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>
+<!-- EDIT509 SECTION "Comment configurer les règles du fabricant à utiliser (i.e. diamètres de perçage, spécification des largeurs/espacements des pistes)?" [1565-1826] -->
+<h1 class="sectionedit510"><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>
+<!-- EDIT510 SECTION "Ã? propos des empreintes" [1827-1866] -->
+<h2 class="sectionedit511"><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 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 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·»).
+
+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.gpleda.org/manual.html"; class="urlextern" title="http://pcb.gpleda.org/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>
+<!-- EDIT511 SECTION "Comment fonctionne le système d'empreintes de PCB?" [1867-3415] -->
+<h2 class="sectionedit512"><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.
+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>
+<!-- EDIT512 SECTION "Où puis-je obtenir des empreintes pré-dessinées pour PCB?" [3416-4228] -->
+<h2 class="sectionedit513"><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).
+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>
+<!-- EDIT513 SECTION "Je veux utiliser PCB pour faire le placement. Comment connaitre la valeur à utiliser pour l'attribut d'empreinte?" [4229-4963] -->
+<h3 class="sectionedit514"><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.
+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·:
+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 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 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 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>
+<!-- EDIT514 SECTION "Newlib" [4964-7438] -->
+<h3 class="sectionedit515"><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>.
+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·:
+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>
@@ -241,16 +150,17 @@ Les bibliothèques m4 suivantes ont reçu plus dâ??attention et dâ??amélioratio
</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.
+
+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.
+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>
+<!-- EDIT515 SECTION "Bibliothèque M4" [7439-9698] -->
+<h2 class="sectionedit516"><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>
@@ -258,40 +168,40 @@ Par exemple, un ampli op peut être DIP8 ou SO8. Une résistance peut être 0603
</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.
+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.
+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>
+<!-- EDIT516 SECTION "Quelle est la manière recommandée pour traiter les différentes empreintes pour le même type de composant?" [9699-10894] -->
+<h2 class="sectionedit517"><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.
+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.
+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.
+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>
+<!-- EDIT517 SECTION "Comment je dessine une nouvelle une empreinte?" [10895-12010] -->
+<h2 class="sectionedit518"><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 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>
@@ -309,78 +219,79 @@ Vous pouvez convertir une empreinte de circuit, éditer les éléments et les re
</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 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 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.
+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>
+<!-- EDIT518 SECTION "Comment j'édite/change une empreinte existante?" [12011-13155] -->
+<h2 class="sectionedit519"><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).
+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>
+<!-- EDIT519 SECTION "Comment j'ajoute une bibliothèque d'empreintes à PCB?" [13156-13674] -->
+<h2 class="sectionedit520"><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>.
+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>
+<!-- EDIT520 SECTION "PCB ne trouve par mes empreintes. Pourquoi?" [13675-14074] -->
+<h2 class="sectionedit521"><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·».
+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.
+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:
+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>
+<pre class="code">#!/bin/bash
+gsch2pcb --elements-dir FOOTPRINT_DIR $@</pre>
<p>
-Ou une autre version utilisateur:
+Ou une autre version utilisateur:
+
</p>
-<pre class="code">
-#!/bin/bash
+<pre class="code">#!/bin/bash
#this script was written by John Luciani
-gsch2pcb --elements-dir /home/user/pcb/footprints/user --use-files $@
-</pre>
+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>
+<!-- EDIT521 SECTION "Maintenant que j'ai toutes ces empreintes, où dois-je les placer?" [14075-15262] -->
+<h1 class="sectionedit522"><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>
+<!-- EDIT522 SECTION "Placement de composants" [15263-15301] -->
+<h2 class="sectionedit523"><a name="comment_je_pivote_une_selection_ie_pour_plus_d_un_element" id="comment_je_pivote_une_selection_ie_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>
@@ -394,23 +305,24 @@ gsch2pcb --elements-dir /home/user/pcb/footprints/user --use-files $@
</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>
+<!-- EDIT523 SECTION "Comment je pivote une sélection (i.e. pour plus d'un élément)?" [15302-15608] -->
+<h2 class="sectionedit524"><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 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 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>.
+
+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>
+<!-- EDIT524 SECTION "Comment je change la taille de l'objet graphique (comme du texte, des lignes de masque texte, etc)?" [15609-16094] -->
+<h2 class="sectionedit525"><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>
@@ -419,49 +331,50 @@ Il y a deux manières de le faire:
<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 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>
+<!-- EDIT525 SECTION "Comment placer les composants sur les deux faces de PCB?" [16095-16605] -->
+<h2 class="sectionedit526"><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.
+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>
+<!-- EDIT526 SECTION "Comment je place l'origine dans pcb?" [16606-17316] -->
+<h2 class="sectionedit527"><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>].
+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>
+<!-- EDIT527 SECTION "Comment je mesure les distances et les dimensions des composants?" [17317-17747] -->
+<h1 class="sectionedit528"><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>
+<!-- EDIT528 SECTION "Routage" [17748-17769] -->
+<h2 class="sectionedit529"><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.
+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>
+<!-- EDIT529 SECTION "Comment router une connexion depuis le côté soudure vers le côté composant et inversement?" [17770-18069] -->
+<h2 class="sectionedit530"><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:
+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>
@@ -475,43 +388,43 @@ Il existe un jeu de tailles de routage prédéfinies. Le jeu porte des noms sugg
</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.
+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>
+<!-- EDIT530 SECTION "Comment je change le style de routage?" [18070-19106] -->
+<h2 class="sectionedit531"><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.
+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>
+<!-- EDIT531 SECTION "J'ai merdé! Comment je reviens en arrière?" [19107-19428] -->
+<h2 class="sectionedit532"><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 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 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>
+<!-- EDIT532 SECTION "Comment je déplace un jeu de piste d'une couche à l'autre?" [19429-19947] -->
+<h2 class="sectionedit533"><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>].
+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>
+<!-- EDIT533 SECTION "Comment je change les soldermask clearance autour d'un trou/via?" [19948-20241] -->
+<h2 class="sectionedit534"><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>
@@ -520,67 +433,68 @@ Il existe plusieurs manières de changer la taille de piste déjà placées:
<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 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 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>
+<!-- EDIT534 SECTION "Comment changer la taille des pistes?" [20242-21299] -->
+<h2 class="sectionedit535"><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 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 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 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 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 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>
+<!-- EDIT535 SECTION "Comment je pilote un via pour connecter une piste à un plan de masse sur une couche différente?" [21300-21910] -->
+<h2 class="sectionedit536"><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 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 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 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 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>
+<!-- EDIT536 SECTION "Je veux dessiner une piste entre deux segments sur le même net mais PCB ne me laisse pas faire! Pourquoi?" [21911-23458] -->
+<h2 class="sectionedit537"><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.
+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>
+<!-- EDIT537 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?" [23459-24216] -->
+<h2 class="sectionedit538"><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>
@@ -588,17 +502,17 @@ Vous pouvez configurer la couleur des rats dans <code>File - Preference - Colors
</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>.
+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>
+<!-- EDIT538 SECTION "Comment je peux configurer la couleur et l'épaisseur des rats nests?" [24217-24654] -->
+<h1 class="sectionedit539"><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>
+<!-- EDIT539 SECTION "Au delà des pistes et des empreintes" [24655-24707] -->
+<h2 class="sectionedit540"><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>
@@ -606,16 +520,16 @@ Voyez la page <a href="http://www.delorie.com/pcb/bg-image.html"; class="urlexter
</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.
+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.
+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>
+<!-- EDIT540 SECTION "Comment je trace un dessin, une impression ou un autre PCB?" [24708-25667] -->
+<h2 class="sectionedit541"><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>
@@ -627,20 +541,20 @@ 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).
+â??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!?!?!?
+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.
+<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>
+<!-- EDIT541 SECTION "Je ne peux pas copier des pastilles dans un circuit. Comment je fais?" [25668-26441] -->
+<h2 class="sectionedit542"><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>
@@ -648,72 +562,72 @@ Utilisez les plans rectangle et polygone. Ces objets éviteront toujours les via
</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>
+<!-- EDIT542 SECTION "Comment je remplis les zones avec cuivre?" [26442-26737] -->
+<h2 class="sectionedit543"><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>].
+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>
+<!-- EDIT543 SECTION "Les polygones mettent mes pistes à la masse! Que puis-je y faire?" [26738-27161] -->
+<h2 class="sectionedit544"><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)·».
+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.
+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>
+<!-- EDIT544 SECTION "Comment je change le polygon clearance?" [27162-27716] -->
+<h2 class="sectionedit545"><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.
+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>
+<!-- EDIT545 SECTION "Comment je cache les polygones lorsque j'édite le placement?" [27717-28224] -->
+<h2 class="sectionedit546"><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.
+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!)
+(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>
+<!-- EDIT546 SECTION "Comment éditer les polygones?" [28225-29658] -->
+<h2 class="sectionedit547"><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·:
+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.
+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.
+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.
+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.
+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>
@@ -721,17 +635,17 @@ Vous pouvez aussi ajouter un autre polygone par dessus le polygone sur lequel vo
</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>
+<!-- EDIT547 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?" [29659-32002] -->
+<h2 class="sectionedit548"><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.
+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>
+<!-- EDIT548 SECTION "Les polygones peuvent-ils être un-masqués? (Un polygone peut-il être de cuivre sans masque de soudure?)" [32003-32688] -->
+<h2 class="sectionedit549"><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>
@@ -739,92 +653,93 @@ 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.
+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.
+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>.
+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>
+<!-- EDIT549 SECTION "Comment je place des trous de montage (mounting hole)?" [32689-33457] -->
+<h2 class="sectionedit550"><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.
+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>
+<!-- EDIT550 SECTION "Pourquoi est-il possible de réaliser des ponts thermiques pour les broches mais pas pour une pastille?" [33458-34257] -->
+<h2 class="sectionedit551"><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 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 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.
+
+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>
+<!-- EDIT551 SECTION "PCB peut-il être utilisé pour réaliser des cartes à simple couche?" [34258-35224] -->
+<h2 class="sectionedit552"><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:
+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 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>
+<!-- EDIT552 SECTION "Quelles ressources existent pour traiter les fichiers PCB en utilisant les scripts?" [35225-36425] -->
+<h2 class="sectionedit553"><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.
+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.
+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>
+<!-- EDIT553 SECTION "Comment j'importe des graphiques vectoriels externe?" [36426-37752] -->
+<h2 class="sectionedit554"><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.
+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>
+<!-- EDIT554 SECTION "Comment j'attache un nom à mon circuit?" [37753-38046] -->
+<h1 class="sectionedit555"><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>
+<!-- EDIT555 SECTION "Autorouteur" [38047-38072] -->
+<h2 class="sectionedit556"><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>
@@ -832,35 +747,35 @@ Désactivez juste les couches dont vous ne voulez pas (habituellement vertes et
</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>
+<!-- EDIT556 SECTION "Comment je force l'autorouteur à ne placer des pistes que sur une couche particulière?" [38073-38322] -->
+<h2 class="sectionedit557"><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.
+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>
+<!-- EDIT557 SECTION "Commennt forcer l'autorouteur à router seulement dans les limites des contours du pcb?" [38323-38858] -->
+<h2 class="sectionedit558"><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.
+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>
+<!-- EDIT558 SECTION "Comment je route les plans d'alimentation et de masse avec l'autorouteur?" [38859-39229] -->
+<h2 class="sectionedit559"><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.
+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>
+<!-- EDIT559 SECTION "Le circuit produit par l'autorouteur est inefficace!" [39230-39423] -->
+<h2 class="sectionedit560"><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>
@@ -868,13 +783,13 @@ 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>
+<!-- EDIT560 SECTION "Le circuit produit par l'autorouteur est moche!" [39424-39560] -->
+<h1 class="sectionedit561"><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>
+<!-- EDIT561 SECTION "Génération Gerber et production de fichiers I/O" [39561-39625] -->
+<h2 class="sectionedit562"><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>
@@ -882,11 +797,12 @@ Vous pouvez ajouter une couche de contour pour vos projets pcb. PCB interprète
</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.
+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:
+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")
(
@@ -898,11 +814,11 @@ Il est aussi possible dâ??éditer le format de fichier natif .pcb de votre circu
)</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>
+<!-- EDIT562 SECTION "Comment je réalise des contours de carte pour proposer mes gerbers vers le fabricant de carte?" [39626-40609] -->
+<h2 class="sectionedit563"><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 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>
@@ -914,37 +830,40 @@ avant de lancer le contrôleur de DRC, il est essentiel de contrôler vos fichie
</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 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 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 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 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 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 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>
+<!-- EDIT563 SECTION "J'ai fini mon placement. Comment je le contrôle?" [40610-43294] -->
+<h1 class="sectionedit564"><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>
+
+<a href="http://geda.seul.org/wiki/geda:faq-pcb"; class="urlextern" title="http://geda.seul.org/wiki/geda:faq-pcb"; rel="nofollow">http://geda.seul.org/wiki/geda:faq-pcb</a><br/>
+
+<a href="http://pcb.gpleda.org/manual.html"; class="urlextern" title="http://pcb.gpleda.org/manual.html"; rel="nofollow">http://pcb.gpleda.org/manual.html</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>
+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>
+<!-- EDIT564 SECTION "Vous n'avez pas répondu à mes questions. Où puis-je trouver d'autres informations sur PCB?" [43295-] --></body>
</html>
diff --git a/docs/wiki/geda-pcb_tips.html b/docs/wiki/geda-pcb_tips.html
index 998095a..295019c 100644
--- a/docs/wiki/geda-pcb_tips.html
+++ b/docs/wiki/geda-pcb_tips.html
@@ -11,147 +11,17 @@
</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="#pcb_does_not_save_silk_when_i_try_to_make_a_footprint" class="toc">pcb does not save silk when I try to make a 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>
+<h1 class="sectionedit568"><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.
+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>
+<!-- EDIT568 SECTION "About PCB layout and routing" [1-214] -->
+<h2 class="sectionedit569"><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>
@@ -159,8 +29,8 @@ You can find a glossary of terms <a href="http://geda.seul.org/wiki/geda:glossar
</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>
+<!-- EDIT569 SECTION "What's a footprint? What's a via? What's a track?" [215-360] -->
+<h1 class="sectionedit570"><a name="pcb_tools" id="pcb_tools">PCB Tools</a></h1>
<div class="level1">
<p>
@@ -168,20 +38,33 @@ 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>
+<!-- EDIT570 SECTION "PCB Tools" [361-467] -->
+<h2 class="sectionedit571"><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>)
+The pcb manual contains a concise description of the user interface in the section <a href="http://pcb.gpleda.org/pcb-cvs/pcb.html#Getting%20Started"; class="urlextern" title="http://pcb.gpleda.org/pcb-cvs/pcb.html#Getting%20Started"; rel="nofollow">â??Getting Startedâ??</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>
+<!-- EDIT571 SECTION "Where can I read about the basics of using pcb?" [468-695] -->
+<h2 class="sectionedit572"><a name="is_there_a_way_to_save_the_file_as_an_older_version" id="is_there_a_way_to_save_the_file_as_an_older_version">Is there a way to save the file as an older version?</a></h2>
+<div class="level2">
+
+<p>
+As new features are added to the file format, older versions of pcb might choke on portions of the layout using the bright new features. To prevent this kind of misbehavior, the pcb file contains a note on the minimum version string for the binary. Older versions of pcb refuse to load a layout saved by a newer pcb binary. This was the case for the addition of holes in polygons in 2010. You need a pcb that was compiled from source later than june 2010 to open these layouts.
+</p>
+
+<p>
+Unfortunately, there is no way to save the layout in a way that allows older versions of pcb to read the file. However, if don't use the holes in polygon features, you can just hand-edit the file version header back to 20070407 and open the file with the older pcb binary.
+</p>
+
+</div>
+<!-- EDIT572 SECTION "Is there a way to save the file as an older version?" [696-1514] -->
+<h2 class="sectionedit573"><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 class="level1"><div class="li"> Start by reading <a href="http://pcb.gpleda.org/bugs.html"; class="urlextern" title="http://pcb.gpleda.org/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>
@@ -194,22 +77,22 @@ The <a href="http://pcb.sourceforge.net/manual.html"; class="urlextern" title="ht
</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>
+<!-- EDIT573 SECTION "I found a bug! What can I do about it?" [1515-2572] -->
+<h2 class="sectionedit574"><a name="how_can_i_set_the_manufacturing_rules_to_use_ie_drill_diameters_trace_width_space_specs" id="how_can_i_set_the_manufacturing_rules_to_use_ie_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>.
+This topic is covered <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">in the manual</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>
+<!-- EDIT574 SECTION "How can I set the manufacturing rules to use (i.e. drill diameters, trace width/space specs)?" [2573-2780] -->
+<h1 class="sectionedit575"><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>
+<!-- EDIT575 SECTION "Non-obvious aspects of the GUI" [2781-2826] -->
+<h2 class="sectionedit576"><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>
@@ -221,8 +104,8 @@ This topic is covered <a href="http://pcb.sourceforge.net/pcb-20060422/pcb.html#
</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>
+<!-- EDIT576 SECTION "Auto-pan bugs me. What can I do about it?" [2827-3134] -->
+<h2 class="sectionedit577"><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>
@@ -238,26 +121,30 @@ Note, for versions younger than summer 2007 this issue is resolved. The delete k
</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>
+<!-- EDIT577 SECTION "The delete key sometimes refuses to delete" [3135-3815] -->
+<h2 class="sectionedit578"><a name="i_try_to_move_an_object_but_pcb_won_t_let_me" id="i_try_to_move_an_object_but_pcb_won_t_let_me">I try to move an object, but pcb won't let me!</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.
+Most probably the object is locked. Locked objects won't highlight. To see, whether it indeed is, select-all-connected-objects from the select menu. Locked footprints are shown with a little L at their diamond shaped insertion mark. 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. Afterward, an 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 instances of the string <code>lock</code> in the *.pcb file with your favorite ascii editor.
</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.
+A different reason for numb objects is â??Only Namesâ?? in the settings menu. When checked, the selection tool will exclusively act on text. This is useful with crammed layouts. There is a complementary setting â??Lock Namesâ??, too.
</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>
+<!-- EDIT578 SECTION "I try to move an object, but pcb won't let me!" [3816-4706] -->
+<h1 class="sectionedit579"><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>
+<!-- EDIT579 SECTION "Footprint issues" [4707-4738] -->
+<h2 class="sectionedit580"><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>
@@ -271,12 +158,13 @@ PCB supports two entirely separate footprint library mechanisms:
</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â??).
+
+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>
+<!-- EDIT580 SECTION "How do PCB's footprints work?" [4739-6443] -->
+<h2 class="sectionedit581"><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>
@@ -284,8 +172,8 @@ Currently, the best place to get footprints (besides in the PCB distribution) is
</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>
+<!-- EDIT581 SECTION "Where can I get pre-drawn footprints for PCB?" [6444-7182] -->
+<h2 class="sectionedit582"><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>
@@ -293,8 +181,8 @@ This question is a common one amongst new gEDA users. Indeed, helping newbies de
</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>
+<!-- EDIT582 SECTION "I want to use PCB to do layout. How do I know what value to use for the footprint attribute?" [7183-7806] -->
+<h3 class="sectionedit583"><a name="newlib" id="newlib">Newlib</a></h3>
<div class="level3">
<p>
@@ -308,18 +196,18 @@ There are several ways to determine the newlib footprint names to use:
<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>
+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>
+<!-- EDIT583 SECTION "Newlib" [7807-9961] -->
+<h3 class="sectionedit584"><a name="m4_library" id="m4_library">M4 library</a></h3>
<div class="level3">
<p>
@@ -349,7 +237,8 @@ The following m4 libraries have received more attention and improvements than th
</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.
+
+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>
@@ -357,8 +246,8 @@ Also, once you generate Gerber files, make sure you <a href="geda-pcb_tips.html#
</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>
+<!-- EDIT584 SECTION "M4 library" [9962-11871] -->
+<h2 class="sectionedit585"><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>
@@ -374,12 +263,13 @@ As far as managing the footprint choices (and indeed the large number of compone
</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>
+<!-- EDIT585 SECTION "What is the recommended way to deal with different footprints for the same sort of device?" [11872-12953] -->
+<h2 class="sectionedit586"><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.
+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>
@@ -390,46 +280,50 @@ Everybody does this a little differently. Some people draw the footprint entirel
</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 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-13167] -->
-<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>
+<!-- EDIT586 SECTION "How do I draw a new footprint?" [12954-14152] -->
+<h2 class="sectionedit587"><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.
+You can convert a footprint into an 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 class="level1"><div class="li"> Copy selection to buffer ([ctrl-c]). </div>
</li>
-<li class="level1"><div class="li"> <code>Break buffer into pieces</code></div>
+<li class="level1"><div class="li"> <code>Break buffer into pieces</code>. Pins become vias and pads become tracks. Unfortunately, some information is lost during the process. Namely, the square flag names of pins and pads. You have to regenerate this information later.</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 class="level1"><div class="li"> Do the desired changes. Note, that only vias, tracks and rectangles are allowed. No text, no arcs, no general polygons. </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 class="level1"><div class="li"> Copy selection to buffer ([ctrl-c]). The position of the crosshair will determine the origin of the resulting footprint.</div>
</li>
-<li class="level1"><div class="li"> <code>Convert buffer to element</code></div>
+<li class="level1"><div class="li"> <code>Convert buffer to element</code>. This converts vias to pins. Tracks and rectangles get SMD pads. </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 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"> Place the mouse somewhere where there is no pad or pin and give a name to the symbol.</div>
+</li>
+<li class="level1"><div class="li"> Move the name to the place where you want the refdes or the value to appear. </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 class="level1"><div class="li"> <code>Save buffer as elements to file</code>. </div>
</li>
</ol>
@@ -438,8 +332,8 @@ Alternatively, you can use your favorite text editor and edit the source code of
</p>
</div>
-<!-- SECTION "How do I edit/change an existing footprint?" [13168-14135] -->
-<h2><a name="pcb_does_not_save_silk_when_i_try_to_make_a_footprint" id="pcb_does_not_save_silk_when_i_try_to_make_a_footprint">pcb does not save silk when I try to make a footprint</a></h2>
+<!-- EDIT587 SECTION "How do I edit/change an existing footprint?" [14153-15697] -->
+<h2 class="sectionedit588"><a name="pcb_does_not_save_silk_when_i_try_to_make_a_footprint" id="pcb_does_not_save_silk_when_i_try_to_make_a_footprint">pcb does not save silk when I try to make a footprint</a></h2>
<div class="level2">
<p>
@@ -447,17 +341,19 @@ The silk of footprints can only deal with lines and arcs. All the other objects
</p>
</div>
-<!-- SECTION "pcb does not save silk when I try to make a footprint" [14136-14465] -->
-<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>
+<!-- EDIT588 SECTION "pcb does not save silk when I try to make a footprint" [15698-16027] -->
+<h2 class="sectionedit589"><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:
+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>
+
+<code>Pad[-40000 -7000 -40000 3000 2700 2400 3000 â??A1â?? â??A1â?? â??square,onsolderâ??]</code>
</p>
<p>
@@ -465,29 +361,43 @@ If you draw the footprint with pcb-<acronym title="Graphical User Interface">GUI
</p>
</div>
-<!-- SECTION "What is the proper way to make a double-sided footprint?" [14466-15035] -->
-<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>
+<!-- EDIT589 SECTION "What is the proper way to make a double-sided footprint?" [16028-16597] -->
+<h2 class="sectionedit590"><a name="how_can_i_achieve_pads_without_paste" id="how_can_i_achieve_pads_without_paste">How can I achieve pads without paste?</a></h2>
+<div class="level2">
+
+<p>
+Sometimes, exposed copper should not receive solder paste. A common example is the pads of an edge connector. This can be achieved with the <code>nopaste</code> <a href="geda-glossary.html#flag" class="wikilink1" title="geda-glossary.html">flag</a>. Currently, there is no <acronym title="Graphical User Interface">GUI</acronym> way to set the flag. Use a text editor to add this flag to the pads of a footprint.
+
+</p>
+
+</div>
+<!-- EDIT590 SECTION "How can I achieve pads without paste?" [16598-16939] -->
+<h2 class="sectionedit591"><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).
+
+<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?" [15036-15541] -->
-<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>
+<!-- EDIT591 SECTION "How do I add a footprint library to PCB?" [16940-17445] -->
+<h2 class="sectionedit592"><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.
+
+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?" [15542-16264] -->
-<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>
+<!-- EDIT592 SECTION "How do I update a footprint in my layout?" [17446-18168] -->
+<h2 class="sectionedit593"><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>
@@ -495,8 +405,8 @@ The footprint path that PCB uses is defined using the <strong><code>Pcb.elementP
</p>
</div>
-<!-- SECTION "PCB is not finding my footprints. Why?" [16265-16613] -->
-<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>
+<!-- EDIT593 SECTION "PCB is not finding my footprints. Why?" [18169-18517] -->
+<h2 class="sectionedit594"><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>
@@ -508,64 +418,43 @@ Rather than change configuration files to get gsch2pcb to find the footprints I
</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:
+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>
+<pre class="code">#!/bin/bash
+gsch2pcb --elements-dir FOOTPRINT_DIR $@</pre>
<p>
-Or another userâ??s version:
+Or another user's version:
+
</p>
-<pre class="code">
-#!/bin/bash
+<pre class="code">#!/bin/bash
#this script was written by John Luciani
-gsch2pcb --elements-dir /home/user/pcb/footprints/user --use-files $@
-</pre>
+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:
+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
+<pre class="code">schematics myschematic.sch myschematic2.sch
elements-dir /myfootprintdir
output-name mypcb
-skip-m4
-</pre>
+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?" [16614-18161] -->
-<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>
+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>
-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>
+<pre class="code">gsch2pcb myproject</pre>
</div>
-<!-- SECTION "What's this business about flashed pads?" [18162-19821] -->
-<h1><a name="component_placement" id="component_placement">Component placement</a></h1>
+<!-- EDIT594 SECTION "Now that I have all of these footprints where do I put them?" [18518-20066] -->
+<h1 class="sectionedit595"><a name="component_placement" id="component_placement">Component placement</a></h1>
<div class="level1">
</div>
-<!-- SECTION "Component placement" [19822-19856] -->
-<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>
+<!-- EDIT595 SECTION "Component placement" [20067-20101] -->
+<h2 class="sectionedit596"><a name="how_do_i_rotate_a_selection_ie_of_more_than_one_item" id="how_do_i_rotate_a_selection_ie_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>
@@ -579,55 +468,57 @@ Now the plotters I believe are all laser plotters and the concept of flashed vs
</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.
+
+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)?" [19857-20300] -->
-<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>
+<!-- EDIT596 SECTION "How do I rotate a selection (i.e. of more than one item)?" [20102-20545] -->
+<h2 class="sectionedit597"><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 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.
+
+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?" [20301-20713] -->
-<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>
+<!-- EDIT597 SECTION "How do I rotate objects by an arbitrary angle?" [20546-20958] -->
+<h2 class="sectionedit598"><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 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.
+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?" [20714-21155] -->
-<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>
+<!-- EDIT598 SECTION "How do I move objects by an arbitrary distance?" [20959-21400] -->
+<h2 class="sectionedit599"><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.
+Use the command â??MoveObject()â?? as described above.
</p>
</div>
-<!-- SECTION "How do I move objects to an absolute location?" [21156-21266] -->
-<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>
+<!-- EDIT599 SECTION "How do I move objects to an absolute location?" [21401-21511] -->
+<h2 class="sectionedit600"><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>
@@ -637,12 +528,13 @@ Use the command â??MoveObject()" as described above.
</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.
+
+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)?" [21267-21718] -->
-<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>
+<!-- EDIT600 SECTION "How do I change the size of a graphical object (such as text, silkscreen lines, etc)?" [21512-21963] -->
+<h2 class="sectionedit601"><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>
@@ -656,19 +548,19 @@ There are two ways to do it:
</ul>
</div>
-<!-- SECTION "How do I put components on both faces in PCB?" [21719-22187] -->
-<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>
+<!-- EDIT601 SECTION "How do I put components on both faces in PCB?" [21964-22432] -->
+<h2 class="sectionedit602"><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:
+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>
+<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.
+
+Be sure, to remove any route-style line in ~/.pcb/preferences . Else, the line in settings will be ignored.
</p>
<p>
@@ -690,8 +582,13 @@ The way to access these modes differs among the <acronym title="Graphical User I
</p>
</div>
-<!-- SECTION "I cant't move the components on the other side of the board!" [22188-27860] -->
-<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>
+<!-- EDIT602 SECTION "I cant't move the components on the other side of the board!" [22433-28105] -->
+<h1 class="sectionedit603"><a name="routing_issues" id="routing_issues">Routing Issues</a></h1>
+<div class="level1">
+
+</div>
+<!-- EDIT603 SECTION "Routing Issues" [28106-28136] -->
+<h2 class="sectionedit604"><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>
@@ -699,8 +596,8 @@ The universal undo key [<strong><code>U</code></strong>] works even while in the
</p>
</div>
-<!-- SECTION "I got stuck! How do I go back?" [27861-28133] -->
-<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>
+<!-- EDIT604 SECTION "I got stuck! How do I go back?" [28137-28409] -->
+<h2 class="sectionedit605"><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>
@@ -712,8 +609,8 @@ The universal undo key [<strong><code>U</code></strong>] works even while in the
</ol>
</div>
-<!-- SECTION "How do I move one set of layer tracks to a different layer?" [28134-28574] -->
-<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>
+<!-- EDIT605 SECTION "How do I move one set of layer tracks to a different layer?" [28410-28850] -->
+<h2 class="sectionedit606"><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>
@@ -733,7 +630,8 @@ For individual vias:
</ol>
<p>
- For groups of vias:
+
+For groups of vias:
</p>
<ol>
<li class="level1"><div class="li"> Turn on the solder mask layer.</div>
@@ -745,17 +643,18 @@ For individual vias:
</ol>
<p>
- The command interface provides more control over the actual size of the clearance. Type ":" to get the command line window, then type:
+
+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>.
+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" [28575-30350] -->
-<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>
+<!-- EDIT606 SECTION "How do I achieve open vias clear of soldermask" [28851-30626] -->
+<h2 class="sectionedit607"><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>
@@ -763,8 +662,8 @@ By default holes and pads will be cleared by an amount given in the correspondin
</p>
</div>
-<!-- SECTION "How do I change the soldermask clearance around a hole/pad?" [30351-30877] -->
-<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>
+<!-- EDIT607 SECTION "How do I change the soldermask clearance around a hole/pad?" [30627-31153] -->
+<h2 class="sectionedit608"><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>
@@ -780,8 +679,8 @@ There are a number of ways to change the size of already laid down tracks:
</ol>
</div>
-<!-- SECTION "How do I change the size of my tracks?" [30878-31815] -->
-<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>
+<!-- EDIT608 SECTION "How do I change the size of my tracks?" [31154-32091] -->
+<h2 class="sectionedit609"><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>
@@ -803,27 +702,27 @@ There are a number of ways to change the size of already laid down tracks:
</ol>
</div>
-<!-- SECTION "How do I drive a via to connect a track to a ground plane on a different layer?" [31816-32301] -->
-<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>
+<!-- EDIT609 SECTION "How do I drive a via to connect a track to a ground plane on a different layer?" [32092-32577] -->
+<h2 class="sectionedit610"><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.
+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 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?" [32302-33079] -->
-<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>
+<!-- EDIT610 SECTION "What is the easiest way to create a thermal via?" [32578-33355] -->
+<h2 class="sectionedit611"><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>
@@ -836,23 +735,61 @@ You are likely drawing tracks with auto-DRC on. To connect the two segments, her
</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 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?" [33080-34398] -->
-<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>
+<!-- EDIT611 SECTION "I want to draw a track between two segments on the same net, but PCB won't let me! Why?" [33356-34674] -->
+<h2 class="sectionedit612"><a name="pcb_won_t_let_me_connect_to_copper_that_is_not_connected_to_anything" id="pcb_won_t_let_me_connect_to_copper_that_is_not_connected_to_anything">PCB won't let me connect to copper that is not connected to anything!</a></h2>
+<div class="level2">
+
+<p>
+This is a known weakness of the Auto-enforce-DRC mode. In this mode, the line tool will only allow you to connect to copper with the same net as the place where the track started.
+</p>
+
+<p>
+There are two ways to connect to unconnected copper, anyway: Obviously, you can temporarily deactivate Auto-enforce-DRC-clearance in the settings menu. A second way uses the fact that auto-DRC relies on the found flag:
+</p>
+<ol>
+<li class="level1"><div class="li"> enter the â??lineâ?? mode ([<strong><code>F2</code></strong>]).</div>
+</li>
+<li class="level1"><div class="li"> hover the mouse cursor over the unconnected copper.</div>
+</li>
+<li class="level1"><div class="li"> press [<strong><code>f</code></strong>] to mark it as â??foundâ??.</div>
+</li>
+<li class="level1"><div class="li"> start the line from somwhere else. Both should now be marked with the â??foundâ?? color and should be connectable.</div>
+</li>
+</ol>
+
+</div>
+<!-- EDIT612 SECTION "PCB won't let me connect to copper that is not connected to anything!" [34675-35416] -->
+<h2 class="sectionedit613"><a name="i_want_to_draw_two_vias_very_close_to_each_other_but_pcb_won_t_let_me" id="i_want_to_draw_two_vias_very_close_to_each_other_but_pcb_won_t_let_me">I want to draw two vias very close to each other, but PCB won't let me!</a></h2>
+<div class="level2">
+
+<p>
+Unfortunately, older versions of PCB not only prevent you from placing overlapping vias but drop them on load. In december 2010 this overly cautions behavior was fixed. If you really need overlapping vias, you have to install a version of pcb younger than that.
+</p>
+
+<p>
+The 2011 version of PCB still won't allow you to place vias so close that their holes overlap. However, it won't complain if you mangaged to work-around this restriction. E.g. place tiny vias and increase their size afterwards.
+
+</p>
+
+</div>
+<!-- EDIT613 SECTION "I want to draw two vias very close to each other, but PCB won't let me!" [35417-35991] -->
+<h2 class="sectionedit614"><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.
+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?" [34399-35037] -->
-<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>
+<!-- EDIT614 SECTION "PCB seems to munge my components names and complains that it can't find proper nets for the pins! How come?" [35992-36630] -->
+<h2 class="sectionedit615"><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>
@@ -868,8 +805,8 @@ Values 0..19 are fixed width in screen pixels. Anything larger means PCB units (
</p>
</div>
-<!-- SECTION "How can I set color and thickness of the rats nests?" [35038-35542] -->
-<h2><a name="where_is_that_last_remaining_rat" id="where_is_that_last_remaining_rat">Where is that last remaining rat?</a></h2>
+<!-- EDIT615 SECTION "How can I set color and thickness of the rats nests?" [36631-37135] -->
+<h2 class="sectionedit616"><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>
@@ -877,30 +814,30 @@ Sometimes remaining rats are hard to see, because they have zero length. This wi
</p>
</div>
-<!-- SECTION "Where is that last remaining rat?" [35543-35870] -->
-<h1><a name="beyond_tracks_and_footprints" id="beyond_tracks_and_footprints">Beyond tracks and footprints</a></h1>
+<!-- EDIT616 SECTION "Where is that last remaining rat?" [37136-37463] -->
+<h1 class="sectionedit617"><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" [35871-35913] -->
-<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>
+<!-- EDIT617 SECTION "Beyond tracks and footprints" [37464-37506] -->
+<h2 class="sectionedit618"><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.
+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.
+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.
+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?" [35914-36754] -->
-<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>
+<!-- EDIT618 SECTION "How do I trace a drawing, a print, or another PCB?" [37507-38347] -->
+<h2 class="sectionedit619"><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>
@@ -912,20 +849,24 @@ I can select the existing area. Everything turns pretty blue.
</p>
<p>
-â??Bufferâ??–>â??Copy Selection To Bufferâ?? seems to succeed (no complaints).
+â??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!?!?!?
+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.
+<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?" [36755-37409] -->
-<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>
+<!-- EDIT619 SECTION "I can't copy component pads in a layout. What gives?" [38348-39002] -->
+<h2 class="sectionedit620"><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>
@@ -933,24 +874,24 @@ Use rectangles and polygon planes. These items will always avoid vias, pads and
</p>
</div>
-<!-- SECTION "How do I fill areas with copper?" [37410-37773] -->
-<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>
+<!-- EDIT620 SECTION "How do I fill areas with copper?" [39003-39366] -->
+<h2 class="sectionedit621"><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.
+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?" [37774-38076] -->
-<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>
+<!-- EDIT621 SECTION "How can I assign my polygon to a net?" [39367-39669] -->
+<h2 class="sectionedit622"><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 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>
@@ -961,30 +902,43 @@ There are different ways to adequately connect different types of objects to a p
</ul>
</div>
-<!-- SECTION "How can I connect tracks, pads, or vias to my polygon?" [38077-38963] -->
-<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>
+<!-- EDIT622 SECTION "How can I connect tracks, pads, or vias to my polygon?" [39670-40556] -->
+<h2 class="sectionedit623"><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.
+You didnâ??t have â??Enable_new_lines_clear_polygonsâ?? checked in the settings menu when you layed down the tracks. Enter <code>changejoin(selected)</code> 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 <code>SetFlag(selected, join)</code> and <code>ClrFlag(selected, join)</code>. See the SetFlag description in the <a href="http://pcb.gpleda.org/pcb-cvs/pcb.html#SetFlag-Action"; class="urlextern" title="http://pcb.gpleda.org/pcb-cvs/pcb.html#SetFlag-Action"; 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?" [38964-39613] -->
-<h2><a name="how_do_i_change_polygon_clearance" id="how_do_i_change_polygon_clearance">How do I change polygon clearance?</a></h2>
+<!-- EDIT623 SECTION "The polygons are shorting my tracks! What can I do about it?" [40557-41219] -->
+<h2 class="sectionedit624"><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)â??.
+In pcb, the polygon itself has no built-in clearance. It is the tracks, pads and pins that bear this property. This means, you can adjust the clearance individually:
+</p>
+
+<p>
+Make sure, the soldermask layer is not active. Else the following will apply to the soldermask rather than to the polygon. Press [<code>k</code>] to increase the clearance of the object under the cursor. Use [<code>ctrl-k</code>] to increase the clearence of selected objects. Add the [<code>shift</code>] modifier to decrease the clearence. To change a whole track press [<code>f</code>] to find all segments that are connected to the object under the cursor and apply the action <code>select(connection)</code>.
+</p>
+
+<p>
+The amount of the increment can be configured in the dialog <code>File/Preference/Increments</code>.
+</p>
+
+<p>
+The above only applies to one object at a time. You can manipulate the clearance of all selected objects with the action <code>ChangeClearSize(Selected,<amount>,<unit>)</code>. The parameter <code><amount></code> should be a number. A prefixed sign means increment, or decrement. A prefixed <code>=</code> sets the clearance to the following value. The parameter can be <code>mil</code> or <code>mm</code>. If not specified the units will default to the internal unit of 0.01 mil.
</p>
<p>
-The amount of the increment can be configured in the dialog File/Preference/Increments.
+In addition, there is a special action that acts only on objects with clearance below a given minimum: <code>MinClearGap(Selected,<amount>,<unit>)</code>.
</p>
</div>
-<!-- SECTION "How do I change polygon clearance?" [39614-40115] -->
-<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>
+<!-- EDIT624 SECTION "How do I change polygon clearance?" [41220-42580] -->
+<h2 class="sectionedit625"><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>
@@ -992,8 +946,8 @@ Put the polygons (and rectangles) on a separate layer. Use the preference to mak
</p>
</div>
-<!-- SECTION "How do I hide the polygons while I edit the layout?" [40116-40700] -->
-<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>
+<!-- EDIT625 SECTION "How do I hide the polygons while I edit the layout?" [42581-43165] -->
+<h2 class="sectionedit626"><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>
@@ -1004,13 +958,13 @@ Parts of the polygon that are not connected to some net are automatically elimin
</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 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?" [40701-41744] -->
-<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>
+<!-- EDIT626 SECTION "Polygons are making the GUI sluggish. What I can do about it?" [43166-44209] -->
+<h2 class="sectionedit627"><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>
@@ -1018,8 +972,8 @@ Polygon calculation is potentially an expensive operation in terms of processor
</p>
</div>
-<!-- SECTION "After I defined those ground planes, pcb takes ages to load. How come?" [41745-42165] -->
-<h2><a name="how_do_i_edit_polygons" id="how_do_i_edit_polygons">How do I edit polygons?</a></h2>
+<!-- EDIT627 SECTION "After I defined those ground planes, pcb takes ages to load. How come?" [44210-44630] -->
+<h2 class="sectionedit628"><a name="how_do_i_edit_polygons" id="how_do_i_edit_polygons">How do I edit polygons?</a></h2>
<div class="level2">
<p>
@@ -1031,8 +985,8 @@ There are four basic ways to edit polygon outlines. You can move and delete vert
</p>
</div>
-<!-- SECTION "How do I edit polygons?" [42166-43351] -->
-<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>
+<!-- EDIT628 SECTION "How do I edit polygons?" [44631-45816] -->
+<h2 class="sectionedit629"><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>
@@ -1060,12 +1014,12 @@ You can also add another polygon on-top of the polygon to which you want to conn
</p>
</div>
-<!-- SECTION "How do I place vias that connect to a polygon for full thermal dissipation or full shielding integrity?" [43352-45273] -->
-<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>
+<!-- EDIT629 SECTION "How do I place vias that connect to a polygon for full thermal dissipation or full shielding integrity?" [45817-47739] -->
+<h2 class="sectionedit630"><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.
+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>
@@ -1087,8 +1041,43 @@ 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?)" [45274-46023] -->
-<h2><a name="how_do_i_place_mounting_holes" id="how_do_i_place_mounting_holes">How do I place mounting holes?</a></h2>
+<!-- EDIT630 SECTION "Can polygons be un-masked? (Can a polygon be made bare-copper with no solder mask?)" [47740-48489] -->
+<h2 class="sectionedit631"><a name="how_can_i_increase_the_size_of_all_pins" id="how_can_i_increase_the_size_of_all_pins">How can I increase the size of all pins?</a></h2>
+<div class="level2">
+
+<p>
+This is a two step process. First select the objects you want to manipulate. Then act on the selection:
+</p>
+<ol>
+<li class="level1"><div class="li"> select all components. You may shut of all layers except silk so the select tool doesn't catch tracks.</div>
+</li>
+<li class="level1"><div class="li"> from the menu chose selectâ??change_size_of_selected_objectsâ??Pins_+10_mil</div>
+</li>
+</ol>
+
+<p>
+You may rip off the sub menu at the dashed line to make it stay on the screen for convenient repeated application.
+</p>
+
+<p>
+Alternatively, issue the ChangeSize action with the command tool:
+</p>
+<ul>
+<li class="level1"><div class="li"> Type a colon to open the command line. </div>
+</li>
+<li class="level1"><div class="li"> In the command line type<br> </div>
+</li>
+</ul>
+<pre class="code">ChangeSize(SelectedPins, SIZE)</pre>
+
+<p>
+
+Replace SIZE with the desired size, given in 1/100 mil. 1mm = 3937. If SIZE is prefixed by â??-â?? the size is decreased. If the prefix is â??+â??, the size is increased. If there is no sign, it is interpreted as an absolute value. Refer to the <a href="http://pcb.gpleda.org/pcb-cvs/pcb.html#ChangeSize-Action"; class="urlextern" title="http://pcb.gpleda.org/pcb-cvs/pcb.html#ChangeSize-Action"; rel="nofollow">pcb manual</a> for the syntax of the ChangeSize action.
+</p>
+
+</div>
+<!-- EDIT631 SECTION "How can I increase the size of all pins?" [48490-49494] -->
+<h2 class="sectionedit632"><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>
@@ -1108,8 +1097,8 @@ For footprint examples see <a href="http://www.luciani.org/geda/pcb/pcb-footprin
</p>
</div>
-<!-- SECTION "How do I place mounting holes?" [46024-46688] -->
-<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>
+<!-- EDIT632 SECTION "How do I place mounting holes?" [49495-50159] -->
+<h2 class="sectionedit633"><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>
@@ -1117,33 +1106,45 @@ The reason is that pins usually have sufficient spacing that the plane surroundi
</p>
</div>
-<!-- SECTION "Why is it possible to make a thermal for pin, but not for a pad?" [46689-47320] -->
-<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>
+<!-- EDIT633 SECTION "Why is it possible to make a thermal for pin, but not for a pad?" [50160-50791] -->
+<h2 class="sectionedit634"><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.
+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.
+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.
+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.
+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?" [47321-48546] -->
-<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>
+<!-- EDIT634 SECTION "Can PCB be used to make single layer boards?" [50792-52017] -->
+<h2 class="sectionedit635"><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:
+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>
@@ -1157,12 +1158,12 @@ One of PCBâ??s great features is that it uses an easily understood <acronym titl
</ol>
</div>
-<!-- SECTION "What resources exist to process PCB files using scripts?" [48547-49832] -->
-<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>
+<!-- EDIT635 SECTION "What resources exist to process PCB files using scripts?" [52018-53303] -->
+<h2 class="sectionedit636"><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.
+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>
@@ -1170,8 +1171,8 @@ Import of external vector graphics is usefull if an irregular shape of the pcb i
</p>
</div>
-<!-- SECTION "How do I import external vector graphics?" [49833-50912] -->
-<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>
+<!-- EDIT636 SECTION "How do I import external vector graphics?" [53304-54383] -->
+<h2 class="sectionedit637"><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>
@@ -1179,22 +1180,24 @@ There is no import filter to directly load a DXF file to pcb. However, the open
</p>
</div>
-<!-- SECTION "Is there a way to import a DXF drawing from mechanical CAD applications?" [50913-51267] -->
-<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>
+<!-- EDIT637 SECTION "Is there a way to import a DXF drawing from mechanical CAD applications?" [54384-54738] -->
+<h2 class="sectionedit638"><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:
+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 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:
+
+Convert to pcb format:
</p>
<ul>
<li class="level1"><div class="li"> pstoedit -f pcb > footprint.pcb</div>
@@ -1202,7 +1205,8 @@ Sometimes footprints call for shapes that are difficult to achieve with the rest
</ul>
<p>
- In pcb do:
+
+In pcb do:
</p>
<ul>
<li class="level1"><div class="li"> File - load-layout-data-to-buffer</div>
@@ -1220,7 +1224,8 @@ Sometimes footprints call for shapes that are difficult to achieve with the rest
</ul>
<p>
- In a text editor:
+
+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>
@@ -1230,8 +1235,8 @@ Sometimes footprints call for shapes that are difficult to achieve with the rest
</ul>
</div>
-<!-- SECTION "What is the best way to do weird footprints?" [51268-52129] -->
-<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>
+<!-- EDIT638 SECTION "What is the best way to do weird footprints?" [54739-55600] -->
+<h2 class="sectionedit639"><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>
@@ -1239,12 +1244,12 @@ You can set the name of the current pcb with <code>Menu Edit - Edit name of - la
</p>
</div>
-<!-- SECTION "How Do I attach a name to my layout?" [52130-52402] -->
-<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>
+<!-- EDIT639 SECTION "How Do I attach a name to my layout?" [55601-55873] -->
+<h2 class="sectionedit640"><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.
+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>
@@ -1252,22 +1257,23 @@ John Luciani wrote a pair of perl scripts that can do better than that. The scri
</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.
+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?" [52403-53510] -->
-<h1><a name="auto_router" id="auto_router">Auto Router</a></h1>
+<!-- EDIT640 SECTION "Is there a way to do multiple instances of a subcircuits?" [55874-56981] -->
+<h1 class="sectionedit641"><a name="auto_router" id="auto_router">Auto Router</a></h1>
<div class="level1">
</div>
-<!-- SECTION "Auto Router" [53511-53540] -->
-<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>
+<!-- EDIT641 SECTION "Auto Router" [56982-57011] -->
+<h2 class="sectionedit642"><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 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 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>
@@ -1279,27 +1285,29 @@ The pair of scripts was written a few years ago and is not used regularily. They
</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 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 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 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.
+
+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.
+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?" [53541-55308] -->
-<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>
+<!-- EDIT642 SECTION "How do I make the most of the auto router?" [57012-58779] -->
+<h2 class="sectionedit643"><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>
@@ -1307,8 +1315,8 @@ Just unselect the layers you donâ??t want (usually green and blue) by clicking o
</p>
</div>
-<!-- SECTION "How do I force the autorouter to only put traces on a particular layer?" [55309-55520] -->
-<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>
+<!-- EDIT643 SECTION "How do I force the autorouter to only put traces on a particular layer?" [58780-58991] -->
+<h2 class="sectionedit644"><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>
@@ -1316,8 +1324,8 @@ Open up the netlist window. It has options for including or excluding nets from
</p>
</div>
-<!-- SECTION "How do I make autorouter leave particular nets alone?" [55521-55845] -->
-<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>
+<!-- EDIT644 SECTION "How do I make autorouter leave particular nets alone?" [58992-59316] -->
+<h2 class="sectionedit645"><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>
@@ -1325,8 +1333,8 @@ You can have the autorouter work only within a given area by drawing a copper po
</p>
</div>
-<!-- SECTION "How do I force the autorouter to route only within my pcb outline?" [55846-56277] -->
-<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>
+<!-- EDIT645 SECTION "How do I force the autorouter to route only within my pcb outline?" [59317-59748] -->
+<h2 class="sectionedit646"><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>
@@ -1334,8 +1342,8 @@ Connect the polygon that will become your power planes to a net and the autorout
</p>
</div>
-<!-- SECTION "How do I route power and ground planes with the autorouter?" [56278-56559] -->
-<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>
+<!-- EDIT646 SECTION "How do I route power and ground planes with the autorouter?" [59749-60030] -->
+<h2 class="sectionedit647"><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>
@@ -1343,22 +1351,22 @@ This is a technological limitation of the current auto router. It is gridless an
</p>
</div>
-<!-- SECTION "The layout produced by the autorouter is inefficient!" [56560-56740] -->
-<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>
+<!-- EDIT647 SECTION "The layout produced by the autorouter is inefficient!" [60031-60211] -->
+<h2 class="sectionedit648"><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?
+Have you tried the various clean-up tools under connectsâ??>optimize routed tracks?
</p>
</div>
-<!-- SECTION "The layout produced by the autorouter is ugly!" [56741-56884] -->
-<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>
+<!-- EDIT648 SECTION "The layout produced by the autorouter is ugly!" [60212-60355] -->
+<h1 class="sectionedit649"><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" [56885-56941] -->
-<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>
+<!-- EDIT649 SECTION "Gerber files, prints and other I/O issues" [60356-60412] -->
+<h2 class="sectionedit650"><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>
@@ -1366,37 +1374,80 @@ Yes, you can tell pcb on the command line to do an export. All the parameters se
</p>
<p>
-Gerber files:
+Gerber files:
+
</p>
-<pre class="code">
-pcb -x gerber --gerberfile BOARD BOARD.pcb
-</pre>
+<pre class="code">pcb -x gerber --gerberfile BOARD BOARD.pcb</pre>
<p>
-Postscript formated print:
+Encapsulated Postscript:
+
</p>
-<pre class="code">
-pcb -x ps --psfile BOARD.ps BOARD.pcb
-</pre>
+<pre class="code">pcb -x eps --eps-file BOARD.eps</pre>
<p>
-<acronym title="Portable Network Graphics">PNG</acronym> format:
+Multi page formated Postscript 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>
+<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?" [56942-57543] -->
-<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>
+<!-- EDIT650 SECTION "Is is possible to produce output without GUI intervention?" [60413-61098] -->
+<h2 class="sectionedit651"><a name="how_can_i_print_specific_layers_only" id="how_can_i_print_specific_layers_only">How can I print specific layers only?</a></h2>
+<div class="level2">
+
+<p>
+In the <acronym title="Graphical User Interface">GUI</acronym>:
+</p>
+<pre class="code"># deactivate all layers you don't want to print
+# choose file -> export_layout... -> eps
+# check as-shown</pre>
+
+<p>
+
+From the command line:
+
+</p>
+<pre class="code">pcb -x eps \
+ --layer-stack "outline,top,silk" \
+ --as-shown \
+ --eps-file "foobar.eps" BOARD.pcb</pre>
+
+<p>
+
+The layer-stack string can contain a comma separated list of the layers used in the <acronym title="Graphical User Interface">GUI</acronym>. You have to give the option â??â??as-shownâ??. Else, a default layer stack file will be used. In addition there are a number of tokens that are technically no layers like â??pinsâ??, or â??invisibleâ??. If you put an unknown token in the layer-stack string, pcb responds with a list of known layer names.
+</p>
+
+</div>
+<!-- EDIT651 SECTION "How can I print specific layers only?" [61099-61797] -->
+<h2 class="sectionedit652"><a name="how_can_i_print_the_bottom_side_of_the_board" id="how_can_i_print_the_bottom_side_of_the_board">How can I print the bottom side of the board?</a></h2>
+<div class="level2">
+
+<p>
+From the command line: Add â??soldersideâ?? to the layer-stack string of the print command. Example:
+
+</p>
+<pre class="code"> pcb -x eps --layer-stack "silk,solderside" \
+ --as-shown \
+ --eps-file "/tmp/foobar.eps" BOARD.pcb</pre>
+
+</div>
+<!-- EDIT652 SECTION "How can I print the bottom side of the board?" [61798-62077] -->
+<h2 class="sectionedit653"><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.
+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. Note, that the name of this layer is case sensitive.
</p>
<p>
@@ -1404,7 +1455,8 @@ You can enter your outline layer thru PCBâ??s <acronym title="Graphical User Int
</p>
<p>
-Itâ??s also possible to edit the native .pcb file format of your layout. I usually use Layer 8 for outlines:
+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")
(
@@ -1416,17 +1468,8 @@ Itâ??s also possible to edit the native .pcb file format of your layout. I usual
)</pre>
</div>
-<!-- SECTION "How do I make a board outline to go with my gerbers to the board maker?" [57544-58392] -->
-<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?" [58393-58845] -->
-<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>
+<!-- EDIT653 SECTION "How do I make a board outline to go with my gerbers to the board maker?" [62078-62980] -->
+<h2 class="sectionedit654"><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>
@@ -1442,11 +1485,11 @@ On load, pcb will substitute drill sizes so that the layout conforms to the list
</p>
</div>
-<!-- SECTION "How do I make sure, that the design contains only certain hole sizes?" [58846-59817] -->
-<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>
+<!-- EDIT654 SECTION "How do I make sure, that the design contains only certain hole sizes?" [62981-63952] -->
+<h2 class="sectionedit655"><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 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>
@@ -1475,13 +1518,13 @@ Besides running the DRC checker, it is essential to check your Gerber files. The
</ul>
</div>
-<!-- SECTION "I'm done with my layout. How should I check my design?" [59818-62037] -->
-<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>
+<!-- EDIT655 SECTION "I'm done with my layout. How should I check my design?" [63953-66172] -->
+<h1 class="sectionedit656"><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" [62038-62097] -->
-<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>
+<!-- EDIT656 SECTION "Exporting Other Formats: Raster and PS Files" [66173-66232] -->
+<h2 class="sectionedit657"><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>
@@ -1489,46 +1532,114 @@ It limits the size of the image to NxN pixels, but maintains the aspect ratio.
</p>
</div>
-<!-- SECTION "What is xy-max in the PNG export dialog box?" [62098-62368] -->
-<h1><a name="customization" id="customization">Customization</a></h1>
+<!-- EDIT657 SECTION "What is xy-max in the PNG export dialog box?" [66233-66503] -->
+<h1 class="sectionedit658"><a name="customization" id="customization">Customization</a></h1>
<div class="level1">
</div>
-<!-- SECTION "Customization" [62369-62397] -->
-<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>
+<!-- EDIT658 SECTION "Customization" [66504-66532] -->
+<h2 class="sectionedit659"><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>
+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?" [62398-62852] -->
-<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>
+<!-- EDIT659 SECTION "I don't like that old-style black background. How can I get a light canvas?" [66533-66987] -->
+<h2 class="sectionedit660"><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:
+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?" [62853-63291] -->
-<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">
+<!-- EDIT660 SECTION "How do I set the default values of the postscript dialog?" [66988-67426] -->
+<h2 class="sectionedit661"><a name="how_do_i_customize_the_mouse_behavior" id="how_do_i_customize_the_mouse_behavior">How do I customize the mouse behavior?</a></h2>
+<div class="level2">
+
+<p>
+There is no <acronym title="Graphical User Interface">GUI</acronym> way to modify the mouse behavior. However, you can adapt it to your needs without recompiling. This is how:
+</p>
+<ol>
+<li class="level1"><div class="li"> locate the file <code>gpcb-menu.res</code> on your box. For lesstif there is a similar file called <code>pcb-menu.res</code> </div>
+</li>
+<li class="level1"><div class="li"> copy the file to <code>$HOME/.pcb</code></div>
+</li>
+<li class="level1"><div class="li"> edit to your needs, save</div>
+</li>
+<li class="level1"><div class="li"> on start-up, pcb will read this localised copy. This will overwrite whatever settings were made by the system gpcb-menu.res</div>
+</li>
+</ol>
+
+</div>
+<!-- EDIT661 SECTION "How do I customize the mouse behavior?" [67427-67907] -->
+<h2 class="sectionedit662"><a name="how_do_i_temporarily_change_keyboard_shortcuts" id="how_do_i_temporarily_change_keyboard_shortcuts">How do I temporarily change keyboard shortcuts?</a></h2>
+<div class="level2">
+
+<p>
+The GTK version of pcb includes a neat way to change shortcuts on the fly:
+</p>
+<ul>
+<li class="level1"><div class="li"> go to the menu and let the mouse hover over the item to be configured. Don't press any mouse button.</div>
+</li>
+<li class="level1"><div class="li"> type whatever shortcut you'd like to assign to the item under the mouse.</div>
+</li>
+<li class="level1"><div class="li"> the shortcut will be working immediately. Conflicts with other shortcuts will be resolved by removing the shortcut of the conflicting definition.</div>
+</li>
+</ul>
+
+<p>
+This setting will be reset at the next session of pcb.
+</p>
+
+</div>
+<!-- EDIT662 SECTION "How do I temporarily change keyboard shortcuts?" [67908-68431] -->
+<h2 class="sectionedit663"><a name="how_do_i_permanently_change_keyboard_shortcuts" id="how_do_i_permanently_change_keyboard_shortcuts">How do I permanently change keyboard shortcuts?</a></h2>
+<div class="level2">
+
+<p>
+Default keyboard shortcuts are defined in files called <code>gpcb-menu.res</code> if you use the default GTK interface. On start-up pcb reads the configuration from a system path, e.g. <code>/usr/local/share</code> or <code>/usr/share/</code>. For permanent change of keyboard shortcuts you can copy the system file to <code>$HOME/.pcb/gpcb-menu.res</code> and edit to your needs. Settings in this file will overwrite the system configuration.
+</p>
+
+<p>
+The lesstif interface reads <code>pcb-menu.res</code> files instead.
+</p>
+
+</div>
+<!-- EDIT663 SECTION "How do I permanently change keyboard shortcuts?" [68432-68960] -->
+<h2 class="sectionedit664"><a name="can_i_customize_the_menu" id="can_i_customize_the_menu">Can I customize the menu?</a></h2>
+<div class="level2">
<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>
+The menu is defined in <code>gpcb-menu.res</code> for the GTK-UI. You can place a localized copy in <code>$HOME/.pcb/</code>. See the notes above on configuration of keyboard shortcuts and mouse behavior.
</p>
+</div>
+<!-- EDIT664 SECTION "Can I customize the menu?" [68961-69187] -->
+<h1 class="sectionedit665"><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">
+<ul>
+<li class="level1"><div class="li"> <a href="http://pcb.gpleda.org/pcb-cvs/pcb.html"; class="urlextern" title="http://pcb.gpleda.org/pcb-cvs/pcb.html"; rel="nofollow">the pcb manual</a></div>
+</li>
+<li class="level1"><div class="li"> <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></div>
+</li>
+<li class="level1"><div class="li"> <a href="http://pcb.gpleda.org/faq.html"; class="urlextern" title="http://pcb.gpleda.org/faq.html"; rel="nofollow">http://pcb.gpleda.org/faq.html</a></div>
+</li>
+</ul>
+
<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>
+
+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?" [63292-] --></body>
+<!-- EDIT665 SECTION "You didn't answer my question. What other resources exist for PCB information?" [69188-] --></body>
</html>
diff --git a/docs/wiki/geda-release_engineering.html b/docs/wiki/geda-release_engineering.html
index bde39e2..aff5905 100644
--- a/docs/wiki/geda-release_engineering.html
+++ b/docs/wiki/geda-release_engineering.html
@@ -12,74 +12,100 @@
<body>
-
-
-<h1><a name="geda_s_release_engineering" id="geda_s_release_engineering">gEDA's Release Engineering</a></h1>
+<h1 class="sectionedit1295"><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-47] -->
-<h2><a name="geda_gaf_release_creation_checklist" id="geda_gaf_release_creation_checklist">gEDA/gaf Release Creation Checklist</a></h2>
+<!-- EDIT1295 SECTION "gEDA's Release Engineering" [1-49] -->
+<h2 class="sectionedit1296"><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:
+
+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"> 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 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>
+<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, grenum.1)</div>
</li>
<li class="level1"><div class="li"> Go into the wiki pages and update the â??gEDA/gaf File Format Documentâ?? and add the release date to the version field.</div>
</li>
-<li class="level1"><div class="li"> Update the wiki documentation (this is far far far too manual)</div>
+<li class="level1"><div class="li"> Update the wiki documentation snapshot (which is shipped with the release) by doing the following steps:</div>
+<ol>
+<li class="level2"><div class="li"> Get the wiki source files. (For now you have to ask Ales to get them from the SEUL.org server; eventually this should be changed so they are available without asking anybody). Put these files in some directory called â??wikisrcâ??. Also make an output directory called â??htmloutputâ??</div>
+</li>
+<li class="level2"><div class="li"> Download a handy php-based package called â??offline-dokuâ??. Latest version seems to be v0.1.1 and it was last seen at: <a href="http://sourceforge.net/projects/limb/files/"; class="urlextern" title="http://sourceforge.net/projects/limb/files/"; rel="nofollow"> offline-doku </a>.</div>
+</li>
+<li class="level2"><div class="li"> You might need to tweak/add the following line in offline-doku/make.php to make sure it has enough memory to operate: <pre class="code"> ini_set('memory_limit','256M');</pre>
+</div>
+</li>
+<li class="level2"><div class="li"> Now run offline-doku like this: <pre class="code"> cd offline-doku-0.1.1; php make.php --verbose /path/to/wikisrc /path/to/htmloutput</pre>
+
+<p>
+ This should processes all the dokuwiki source files and convert them into html files.
+</p>
+</div>
+</li>
+<li class="level2"><div class="li"> Tar/copy the htmloutput directory into the gaf git directory docs/</div>
+</li>
+<li class="level2"><div class="li"> Move aside (do not delete yet) the current wiki directory to something like â??wikioldâ??. Rename the new htmloutput directory to â??wikiâ??</div>
+</li>
+<li class="level2"><div class="li"> Run: <pre class="code"> cp -f wikiold/design.css wiki </pre>
+</div>
+</li>
+<li class="level2"><div class="li"> Run: <pre class="code"> scripts/copygitignores.sh </pre>
+
+<p>
+ You will need to verify that the .gitignore files were copied correctly.
+</p>
+</div>
+</li>
+<li class="level2"><div class="li"> Run: <pre class="code"> cd wiki; scripts/populatemkfiles.sh </pre>
+
+<p>
+ You will have to tweak the hardcoded paths in this script. You need to verify all of the generated Makefile.am files (easiest to compare them with the files in wikiold) to make sure they got generated correctly. This script is known to break in the media and images directories (by outputing incorrect paths).
+</p>
+</div>
+</li>
+<li class="level2"><div class="li"> Check to see what has changed using git status and git diff. Go through and add any new files to git using git add.</div>
+</li>
+<li class="level2"><div class="li"> Check to see what has changed between wikiold and wiki using: <pre class="code"> diff -r -q wikiold wiki </pre>
+
+<p>
+ Fix anything is incorrect.
+</p>
+</div>
+</li>
+<li class="level2"><div class="li"> Go through all the html files and remove the contents of the line (but don't delete the empty line): <pre class="code"> <a href=.>start</a></br></pre>
+
+<p>
+. Eventually this should be automated or somehow fixed. Removing this start link will make the html pages look better and reduce the number of unnecessary file changes (in git).
+</p>
+</div>
+</li>
+<li class="level2"><div class="li"> Finally commit all the changes/files.</div>
+</li>
+</ol>
</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>
+<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).
@@ -90,9 +116,7 @@ and make sure it completes without any errors. After this is complete you will
<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>
+<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>
@@ -101,23 +125,17 @@ and make sure it completes without any errors. After this is complete you will
<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>
+<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>
+<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>
+<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>
@@ -134,5 +152,5 @@ and make sure it completes without any errors. After this is complete you will
</ul>
</div>
-<!-- SECTION "gEDA/gaf Release Creation Checklist" [48-] --></body>
+<!-- EDIT1296 SECTION "gEDA/gaf Release Creation Checklist" [50-] --></body>
</html>
diff --git a/docs/wiki/geda-scg.fr.html b/docs/wiki/geda-scg.fr.html
index dae7f3d..61b6519 100644
--- a/docs/wiki/geda-scg.fr.html
+++ b/docs/wiki/geda-scg.fr.html
@@ -11,46 +11,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>
+<h1 class="sectionedit669"><a name="geda_gaf_symbol_creation_document" id="geda_gaf_symbol_creation_document">gEDA/gaf Symbol Creation Document</a></h1>
<div class="level1">
<p>
@@ -66,8 +28,8 @@ This document is released under the <a href="geda-gfdl.html" class="wikilink1" t
</p>
</div>
-<!-- SECTION "gEDA/gaf Symbol Creation Document" [1-264] -->
-<h2><a name="overview" id="overview">Overview</a></h2>
+<!-- EDIT669 SECTION "gEDA/gaf Symbol Creation Document" [1-264] -->
+<h2 class="sectionedit670"><a name="overview" id="overview">Overview</a></h2>
<div class="level2">
<p>
@@ -75,15 +37,18 @@ This document describes the creation of component symbols, including style conve
</p>
</div>
-<!-- SECTION "Overview" [265-462] -->
-<h2><a name="component_symbol_creation" id="component_symbol_creation">Component symbol creation</a></h2>
+<!-- EDIT670 SECTION "Overview" [265-462] -->
+<h2 class="sectionedit671"><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/>
+
+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>
@@ -93,7 +58,7 @@ Component symbols (from here on known as â??symbolsâ??) are drawn using gschem j
</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 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>
@@ -105,7 +70,8 @@ Translating the symbol to the origin is a required step. To translate a symbol e
</p>
<p>
-4. Save the symbol using Save or SaveAs… Here are some symbol naming conventions:<br/>
+4. Save the symbol using Save or SaveAsâ?¦ Here are some symbol naming
+conventions:<br/>
</p>
<ul>
@@ -122,23 +88,32 @@ Translating the symbol to the origin is a required step. To translate a symbol e
</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.
+
+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>
+<!-- EDIT671 SECTION "Component symbol creation" [463-2082] -->
+<h2 class="sectionedit672"><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.
+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 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>
@@ -150,7 +125,7 @@ This section describes the various requirements which must be met in order to cr
</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 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>
@@ -167,8 +142,8 @@ This section describes the various requirements which must be met in order to cr
</ul>
</div>
-<!-- SECTION "Requirements" [2083-6223] -->
-<h2><a name="style" id="style">Style</a></h2>
+<!-- EDIT672 SECTION "Requirements" [2083-6223] -->
+<h2 class="sectionedit673"><a name="style" id="style">Style</a></h2>
<div class="level2">
<p>
@@ -176,8 +151,8 @@ This section describes the style in which is used in the standard gEDA/gaf symbo
</p>
</div>
-<!-- SECTION "Style" [6224-6333] -->
-<h3><a name="text" id="text">Text</a></h3>
+<!-- EDIT673 SECTION "Style" [6224-6333] -->
+<h3 class="sectionedit674"><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>
@@ -187,8 +162,8 @@ This section describes the style in which is used in the standard gEDA/gaf symbo
</ul>
</div>
-<!-- SECTION "Text" [6334-6472] -->
-<h3><a name="attributes" id="attributes">Attributes</a></h3>
+<!-- EDIT674 SECTION "Text" [6334-6472] -->
+<h3 class="sectionedit675"><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>
@@ -206,8 +181,8 @@ This section describes the style in which is used in the standard gEDA/gaf symbo
</ul>
</div>
-<!-- SECTION "Attributes" [6473-7569] -->
-<h3><a name="graphics" id="graphics">Graphics</a></h3>
+<!-- EDIT675 SECTION "Attributes" [6473-7569] -->
+<h3 class="sectionedit676"><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>
@@ -219,8 +194,8 @@ This section describes the style in which is used in the standard gEDA/gaf symbo
</ul>
</div>
-<!-- SECTION "Graphics" [7570-7920] -->
-<h3><a name="pins" id="pins">Pins</a></h3>
+<!-- EDIT676 SECTION "Graphics" [7570-7920] -->
+<h3 class="sectionedit677"><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>
@@ -250,8 +225,8 @@ This section describes the style in which is used in the standard gEDA/gaf symbo
</ul>
</div>
-<!-- SECTION "Pins" [7921-9876] -->
-<h3><a name="electrical" id="electrical">Electrical</a></h3>
+<!-- EDIT677 SECTION "Pins" [7921-9876] -->
+<h3 class="sectionedit678"><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>
@@ -265,18 +240,19 @@ This section describes the style in which is used in the standard gEDA/gaf symbo
</ul>
</div>
-<!-- SECTION "Electrical" [9877-10499] -->
-<h2><a name="footprint_naming_conventions" id="footprint_naming_conventions">Footprint naming conventions</a></h2>
+<!-- EDIT678 SECTION "Electrical" [9877-10499] -->
+<h2 class="sectionedit679"><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.
+
+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>
+<!-- EDIT679 SECTION "Footprint naming conventions" [10500-10853] -->
+<h3 class="sectionedit680"><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>
@@ -292,8 +268,8 @@ This section describes the conventions for naming of footprints used in gEDA/gaf
</ul>
</div>
-<!-- SECTION "Notes" [10854-11196] -->
-<h3><a name="integrated_circuit_packages" id="integrated_circuit_packages">Integrated circuit packages</a></h3>
+<!-- EDIT680 SECTION "Notes" [10854-11196] -->
+<h3 class="sectionedit681"><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>
@@ -317,8 +293,8 @@ This section describes the conventions for naming of footprints used in gEDA/gaf
</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>
+<!-- EDIT681 SECTION "Integrated circuit packages" [11197-12065] -->
+<h3 class="sectionedit682"><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>
@@ -382,8 +358,8 @@ This section describes the conventions for naming of footprints used in gEDA/gaf
</ul>
</div>
-<!-- SECTION "Integrated circuit SMT packages" [12066-14996] -->
-<h3><a name="basic_semiconductors" id="basic_semiconductors">Basic semiconductors</a></h3>
+<!-- EDIT682 SECTION "Integrated circuit SMT packages" [12066-14996] -->
+<h3 class="sectionedit683"><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>
@@ -395,8 +371,8 @@ This section describes the conventions for naming of footprints used in gEDA/gaf
</ul>
</div>
-<!-- SECTION "Basic semiconductors" [14997-15399] -->
-<h3><a name="basic_smt_semiconductors" id="basic_smt_semiconductors">Basic SMT semiconductors</a></h3>
+<!-- EDIT683 SECTION "Basic semiconductors" [14997-15399] -->
+<h3 class="sectionedit684"><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>
@@ -410,8 +386,8 @@ This section describes the conventions for naming of footprints used in gEDA/gaf
</ul>
</div>
-<!-- SECTION "Basic SMT semiconductors" [15400-15855] -->
-<h3><a name="passive_components" id="passive_components">Passive components</a></h3>
+<!-- EDIT684 SECTION "Basic SMT semiconductors" [15400-15855] -->
+<h3 class="sectionedit685"><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>
@@ -445,8 +421,8 @@ This section describes the conventions for naming of footprints used in gEDA/gaf
</ul>
</div>
-<!-- SECTION "Passive components" [15856-16977] -->
-<h3><a name="passive_smt_components" id="passive_smt_components">Passive SMT components</a></h3>
+<!-- EDIT685 SECTION "Passive components" [15856-16977] -->
+<h3 class="sectionedit686"><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>
@@ -458,34 +434,35 @@ This section describes the conventions for naming of footprints used in gEDA/gaf
</ul>
</div>
-<!-- SECTION "Passive SMT components" [16978-17330] -->
-<h2><a name="hints_and_tips" id="hints_and_tips">Hints and Tips</a></h2>
+<!-- EDIT686 SECTION "Passive SMT components" [16978-17330] -->
+<h2 class="sectionedit687"><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/>
+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 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 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 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>
+<!-- EDIT687 SECTION "Hints and Tips" [17331-18726] -->
+<h2 class="sectionedit688"><a name="example" id="example">Example</a></h2>
<div class="level2">
<p>
@@ -561,48 +538,26 @@ 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>
+documentation=http:<em>www-s.ti.com/sc/ds/sn74hc00.pdf
+</xterm>
-<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>
+===== Document Revision History =====
+| September 14th, 2002|Created symbol.tex from symbols.html |
+| October 31st, 2002|Fixed bad example symbol |
+| February 11th, 2003|Footprint naming conventions added |
+| September 27th, 2003|Applied Dan McMahill's QFP and QFN patch |
+| July 6th, 2004|Added a bunch more details/hints to the pin section |
+
+</p>
</div>
-<!-- SECTION "Document Revision History" [20444-] --></body>
+<!-- EDIT688 SECTION "Example" [18727-] --></body>
</html>
diff --git a/docs/wiki/geda-scg.html b/docs/wiki/geda-scg.html
index 3da3c56..0b3d406 100644
--- a/docs/wiki/geda-scg.html
+++ b/docs/wiki/geda-scg.html
@@ -12,19 +12,19 @@
<body>
-
-
-<h1><a name="geda_gaf_symbol_creation_document" id="geda_gaf_symbol_creation_document">gEDA/gaf Symbol Creation Document</a></h1>
+<h1 class="sectionedit781"><a name="geda_gaf_symbol_creation_document" id="geda_gaf_symbol_creation_document">gEDA/gaf Symbol Creation Document</a></h1>
<div class="level1">
<p>
- This page has MOVED to:
+
+This page has MOVED to:
</p>
<p>
-<a href="http://geda.seul.org/wiki/geda:gschem_symbol_creation"; class="urlextern" title="http://geda.seul.org/wiki/geda:gschem_symbol_creation"; rel="nofollow">http://geda.seul.org/wiki/geda:gschem_symbol_creation</a>
+<a href="http://geda.seul.org/wiki/geda:gschem_symbol_creation"; class="urlextern" title="http://geda.seul.org/wiki/geda:gschem_symbol_creation"; rel="nofollow">http://geda.seul.org/wiki/geda:gschem_symbol_creation</a>
+
</p>
</div>
-<!-- SECTION "gEDA/gaf Symbol Creation Document" [2-] --></body>
+<!-- EDIT781 SECTION "gEDA/gaf Symbol Creation Document" [2-] --></body>
</html>
diff --git a/docs/wiki/geda-scm.html b/docs/wiki/geda-scm.html
index 840db3e..b2bde2f 100644
--- a/docs/wiki/geda-scm.html
+++ b/docs/wiki/geda-scm.html
@@ -11,50 +11,14 @@
</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>
+<h1 class="sectionedit785"><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.
+
+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>
@@ -66,16 +30,19 @@
</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>.
+
+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>
+<!-- EDIT785 SECTION "gEDA/gaf's Source Control Management" [1-494] -->
+<h2 class="sectionedit786"><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:
+
+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>
@@ -85,35 +52,43 @@
</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.
+
+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
+Debian-based
+
</p>
<pre class="code">apt-get install git-core git-doc gitk stgit</pre>
<p>
- you may also want:
+
+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.
+
+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
+
+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>
+<!-- EDIT786 SECTION "Installing git & related tools" [495-1330] -->
+<h2 class="sectionedit787"><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:
+
+The toplevel documentation for git can be found at:
</p>
<p>
@@ -121,7 +96,7 @@ Debian-based
</p>
<p>
-The userâ??s manual for git can be found at:
+The user's manual for git can be found at:
</p>
<p>
@@ -142,7 +117,8 @@ Other nice tutorials/webpages:
<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://git.or.cz/course/index.html"; class="urlextern" title="http://git.or.cz/course/index.html"; rel="nofollow">git Crash Courses</a><br/>
</p>
@@ -151,83 +127,81 @@ Keep in mind that some of these tutorials are a little dated and may not cover c
</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>
+<!-- EDIT787 SECTION "Learning to use git" [1331-2001] -->
+<h2 class="sectionedit788"><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:
+
+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
+
+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>.
+
+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>
+<!-- EDIT788 SECTION "Accessing the repository anonymously" [2002-2375] -->
+<h2 class="sectionedit789"><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:
+
+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>
+<pre class="code">git clone ssh://git@xxxxxxxxxxxxxx/gaf.git</pre>
<p>
or
</p>
-<pre class="code">git clone ssh://<username>@git.gpleda.org/home/git/pcb.git</pre>
+<pre class="code">git clone ssh://git@xxxxxxxxxxxxxx/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">
+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>
- 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>
+<pre class="code">Host git.gpleda.org
+Port 5022</pre>
</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>
+<!-- EDIT789 SECTION "Accessing the repository with write permission" [2376-2863] -->
+<h2 class="sectionedit790"><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>
+<!-- EDIT790 SECTION "Making and committing changes" [2864-2908] -->
+<h3 class="sectionedit791"><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.
+
+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>
+<!-- EDIT791 SECTION "Setting up user information" [2909-3167] -->
+<h3 class="sectionedit792"><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.
+
+If you apply a patch from someone else (e.g. from a launchpad 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>
@@ -236,28 +210,34 @@ First of all, check a few things:
<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 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 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).
+
+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):
+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:
+
+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.
+
+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>
@@ -265,44 +245,52 @@ Note: <em>This is easy to miss accidentally if your editor introduces tabs. Plea
</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:
+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:
+
+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.
+
+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
+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.
+
+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:
+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
+
+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>
+<!-- EDIT792 SECTION "Committing patches from other contributors" [3168-5096] -->
+<h3 class="sectionedit793"><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.
+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>
@@ -316,22 +304,21 @@ The one-line summary is used for generating e-mail subject lines, and for the gi
<p>
Example:
</p>
-<pre class="code">
-Added new GedaList class derived from GObject
+<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>
+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>
+<!-- EDIT793 SECTION "Writing good commit message" [5097-6078] -->
+<h3 class="sectionedit794"><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>
+
+<strong>Warning: pushing changes to the remote repository is destructive</strong>
</p>
<p>
@@ -339,108 +326,127 @@ Unlike <acronym title="Concurrent Versions System">CVS</acronym>, it is not the
</p>
</div>
-<!-- SECTION "Push is Destructive" [6444-6797] -->
-<h2><a name="how_do_i" id="how_do_i">How Do I ... ?</a></h2>
+<!-- EDIT794 SECTION "Push is Destructive" [6079-6432] -->
+<h2 class="sectionedit795"><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>.
+
+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>
+<!-- EDIT795 SECTION "How Do I ... ?" [6433-6556] -->
+<h3 class="sectionedit796"><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:
+
+For anonymous read-only access:
+
</p>
<pre class="code">$ git clone git://git.gpleda.org/gaf</pre>
<p>
- For developers with read/write access:
+
+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>
+<!-- EDIT796 SECTION "... get a copy of gEDA/gaf git repository?" [6557-6776] -->
+<h3 class="sectionedit797"><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:
+
+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:
+
+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>
+<!-- EDIT797 SECTION "... keep my local copy current?" [6777-7191] -->
+<h3 class="sectionedit798"><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.
+
+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:
+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>
+<!-- EDIT798 SECTION "... commit my changes to the local git repository?" [7192-7747] -->
+<h3 class="sectionedit799"><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.
+
+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:
+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:
+
+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>
+<!-- EDIT799 SECTION "... undo any uncommitted local changes?" [7748-8124] -->
+<h3 class="sectionedit800"><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.
+
+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>
+<!-- EDIT800 SECTION "... fix/change my last commit?" [8125-8333] -->
+<h3 class="sectionedit801"><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.
+
+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>
+<!-- EDIT801 SECTION "... track a branch?" [8334-8517] -->
+<h3 class="sectionedit802"><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):
+
+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
@@ -448,36 +454,45 @@ $ git commit --amend filename1..filenameN </pre>
$ git commit -a </pre>
<p>
- To publish this branch in the central repository (requires write access to the central repository):
+
+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>
+<!-- EDIT802 SECTION "... create a branch (starting at a tag)?" [8518-8886] -->
+<h3 class="sectionedit803"><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.
+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.
+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:
+
+<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.
+
+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>
+<!-- EDIT803 SECTION "... fetch a development branch from other people?" [8887-9659] -->
+<h3 class="sectionedit804"><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>
@@ -486,7 +501,8 @@ The simplest possible way:
<pre class="code">$ git diff > name_of_patchfile</pre>
<p>
- A more complicated way:
+
+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
@@ -498,16 +514,18 @@ This will output a filename which contains the patch. Be sure to look at the do
</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>
+<!-- EDIT804 SECTION "... format a patch to send to the developers?" [9660-10281] -->
+<h3 class="sectionedit805"><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.
+
+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:
+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
@@ -517,9 +535,10 @@ Second, the command that will really save your bacon is git-reflog. Using it wo
$ 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.
+
+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>
+<!-- EDIT805 SECTION "... recover from a really messed up local repository?" [10282-] --></body>
</html>
diff --git a/docs/wiki/geda-screenshots.html b/docs/wiki/geda-screenshots.html
new file mode 100644
index 0000000..e956ba2
--- /dev/null
+++ b/docs/wiki/geda-screenshots.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 class="sectionedit1419"><a name="screenshots" id="screenshots">Screenshots</a></h1>
+<div class="level1">
+
+</div>
+
+<h5><a name="gschem" id="gschem">gschem</a></h5>
+<div class="level5">
+
+<p>
+<a href="http://geda.seul.org/wiki/_media/geda:screenshot_gschem.png"; class="media" title="http://geda.seul.org/wiki/_media/geda:screenshot_gschem.png"; rel="nofollow"><img src="media/geda/screenshot_gschem_thumb.png" class="media" title="gschem (click for full size)" alt="gschem (click for full size)" /></a>
+</p>
+
+</div>
+
+<h5><a name="pcb" id="pcb">pcb</a></h5>
+<div class="level5">
+
+<p>
+<a href="http://geda.seul.org/wiki/_media/geda:screenshot_pcb.png"; class="media" title="http://geda.seul.org/wiki/_media/geda:screenshot_pcb.png"; rel="nofollow"><img src="media/geda/screenshot_pcb_thumb.png" class="media" title="pcb (click for full size)" alt="pcb (click for full size)" /></a>
+</p>
+
+</div>
+
+<h5><a name="gerbv" id="gerbv">gerbv</a></h5>
+<div class="level5">
+
+<p>
+<a href="http://geda.seul.org/wiki/_media/geda:screenshot_gerbv.png"; class="media" title="http://geda.seul.org/wiki/_media/geda:screenshot_gerbv.png"; rel="nofollow"><img src="media/geda/screenshot_gerbv_thumb.png" class="media" title="gerbv (click for full size)" alt="gerbv (click for full size)" /></a>
+</p>
+
+</div>
+
+<h5><a name="gschem_running_on_mac_osx" id="gschem_running_on_mac_osx">gschem running on Mac OSX</a></h5>
+<div class="level5">
+
+<p>
+<a href="http://geda.seul.org/wiki/_media/geda:screenshot_gschem_osx.png"; class="media" title="http://geda.seul.org/wiki/_media/geda:screenshot_gschem_osx.png"; rel="nofollow"><img src="media/geda/screenshot_gschem_osx_thumb.png" class="media" title="gschem on Mac (click for full size)" alt="gschem on Mac (click for full size)" /></a>
+</p>
+
+</div>
+
+<h5><a name="pcb_running_on_mac_osx" id="pcb_running_on_mac_osx">pcb running on Mac OSX</a></h5>
+<div class="level5">
+
+<p>
+<a href="http://geda.seul.org/wiki/_media/geda:screenshot_pcb_osx.png"; class="media" title="http://geda.seul.org/wiki/_media/geda:screenshot_pcb_osx.png"; rel="nofollow"><img src="media/geda/screenshot_pcb_osx_thumb.png" class="media" title="pcb on Mac (click for full size)" alt="pcb on Mac (click for full size)" /></a>
+</p>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-sdb_howto.html b/docs/wiki/geda-sdb_howto.html
index 0cf4f90..a4118b6 100644
--- a/docs/wiki/geda-sdb_howto.html
+++ b/docs/wiki/geda-sdb_howto.html
@@ -11,69 +11,22 @@
</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>
+<h1 class="sectionedit811"><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>
+<!-- EDIT811 SECTION "SPICE on gEDA HOWTO" [1-34] -->
+<h2 class="sectionedit812"><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.
+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>
+<!-- EDIT812 SECTION "Introduction" [35-708] -->
+<h3 class="sectionedit813"><a name="overview" id="overview">Overview</a></h3>
<div class="level3">
<p>
@@ -91,7 +44,8 @@ From the top level, SPICE simulation in gEDA proceeds via the following steps:
</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:
+
+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>
@@ -101,28 +55,29 @@ From the top level, SPICE simulation in gEDA proceeds via the following steps:
</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.
+
+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>
+<!-- EDIT813 SECTION "Overview" [709-1877] -->
+<h3 class="sectionedit814"><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.
+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>
+<!-- EDIT814 SECTION "Spice-sdb netlister installation and configuration" [1878-2744] -->
+<h3 class="sectionedit815"><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 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>
@@ -141,38 +96,42 @@ The detailed steps required to create a circuit and simulate it with gEDA look l
</ol>
<p>
- The purpose of this HOWTO is to provide the detailed understanding necessary to successfully navigate this process.
+
+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>
+<!-- EDIT815 SECTION "Design/simulation flow summary" [2745-3673] -->
+<h2 class="sectionedit816"><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>
+<!-- EDIT816 SECTION "Preliminary notes about symbols and SPICE model files" [3674-3739] -->
+<h3 class="sectionedit817"><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 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 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.
+
+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>
+<!-- EDIT817 SECTION "Symbol creation for SPICE netlisting." [3740-5819] -->
+<h3 class="sectionedit818"><a name="spice_file_configuration" id="spice_file_configuration">SPICE file configuration</a></h3>
<div class="level3">
<p>
@@ -181,24 +140,24 @@ Files holding complicated SPICE models or other SPICE code may be incorporated i
<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 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>
+<!-- EDIT818 SECTION "SPICE file configuration" [5820-6689] -->
+<h2 class="sectionedit819"><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.
+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>
+<!-- EDIT819 SECTION "Schematic capture" [6690-7282] -->
+<h3 class="sectionedit820"><a name="gschem_attributes_for_spice_netlisting" id="gschem_attributes_for_spice_netlisting">Gschem attributes for spice netlisting</a></h3>
<div class="level3">
<p>
@@ -211,29 +170,30 @@ There are several ways that spice attributes may be associated with a component
<div class="level4">
<p>
-The following attributes are meaningful for SPICE netlisting, and may be attached from within gschem:
+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>
+<div class="table sectionedit821"><table class="inline">
+ <tr class="row0">
+ <td class="col0"><strong><code>refdes</code></strong></td><td class="col1">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 class="row1">
+ <td class="col0"><strong><code>value</code></strong></td><td class="col1">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 class="row2">
+ <td class="col0"><strong><code>model</code></strong></td><td class="col1">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 class="row3">
+ <td class="col0"><strong><code>file</code></strong></td><td class="col1">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 class="row4">
+ <td class="col0"><strong><code>model-name</code></strong></td><td class="col1">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 class="row5">
+ <td class="col0"><strong><code>type</code></strong></td><td class="col1">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>
-
+</table></div>
+<!-- EDIT821 TABLE [7706-8827] -->
</div>
<h4><a name="refdes_conventions" id="refdes_conventions">refdes conventions</a></h4>
@@ -241,7 +201,8 @@ The following attributes are meaningful for SPICE netlisting, and may be attache
<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>.
+
+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>
@@ -255,20 +216,24 @@ As a prerequisite to handling SPICE-related attributes, the SPICE netlister requ
<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:
+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>
+<div class="table sectionedit822"><table class="inline">
+ <tr class="row0">
+ <td class="col0"><strong><code>refdes</code></strong></td><td class="col1">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 class="row1">
+ <td class="col0"><strong><code>value</code></strong></td><td class="col1">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>
-
+</table></div>
+<!-- EDIT822 TABLE [9558-9873] -->
<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:
+
+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
@@ -276,7 +241,9 @@ 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:
+
+Example capacitor:
+
</p>
<pre class="code">refdes = C22
value = 1UF
@@ -288,23 +255,27 @@ SPICE line generated: C22 4 23 1UF</pre>
<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:
+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>
+<div class="table sectionedit823"><table class="inline">
+ <tr class="row0">
+ <td class="col0"><strong><code>refdes</code></strong></td><td class="col1">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 class="row1">
+ <td class="col0"><strong><code>value</code></strong></td><td class="col1">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 class="row2">
+ <td class="col0"><strong><code>model</code></strong></td><td class="col1">One line string holding additional parameters, formatted as a valid SPICE string.</td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT823 TABLE [10744-10946] -->
<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:
+
+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
@@ -317,7 +288,7 @@ SPICE line generated: R2 0 4 220 TC=0.001,0.015</pre>
<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:
+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>
@@ -326,25 +297,28 @@ Transistors and diodes are generally accompanied by a device-specific model &nda
<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:
+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>
+<div class="table sectionedit824"><table class="inline">
+ <tr class="row0">
+ <td class="col0"><strong><code>refdes</code></strong></td><td class="col1">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 class="row1">
+ <td class="col0"><strong><code>value</code></strong></td><td class="col1">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 class="row2">
+ <td class="col0"><strong><code>model-name</code></strong></td><td class="col1">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 class="row3">
+ <td class="col0"><strong><code>model</code></strong></td><td class="col1">One line string holding additional parameters. Do not place the model parameters in parentheses â?? gnetlist will do this for you.</td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT824 TABLE [12117-12596] -->
<p>
- Example diode:
+
+Example diode:
+
</p>
<pre class="code">refdes = D5
model-name = 1N1004
@@ -359,25 +333,27 @@ MODEL 1N1004 D (IS=0.5UA RS=6 BV=5.20)</pre>
<div class="level5">
<p>
-To incorporate a file-full of SPICE parameters into the netlist, the following attributes must be attached to the component:
+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>
+<div class="table sectionedit825"><table class="inline">
+ <tr class="row0">
+ <td class="col0"><strong><code>refdes</code></strong></td><td class="col1">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 class="row1">
+ <td class="col0"><strong><code>value</code></strong></td><td class="col1">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 class="row2">
+ <td class="col0"><strong><code>model-name</code></strong></td><td class="col1">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 class="row3">
+ <td class="col0"><strong><code>file</code></strong></td><td class="col1">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>
-
+</table></div>
+<!-- EDIT825 TABLE [12914-13520] -->
<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.
+
+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>
@@ -395,46 +371,48 @@ Integrated circuits are incorporated into the netlist similarly to transistors a
<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:
+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>
+<div class="table sectionedit826"><table class="inline">
+ <tr class="row0">
+ <td class="col0"><strong><code>refdes</code></strong></td><td class="col1">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 class="row1">
+ <td class="col0"><strong><code>value</code></strong></td><td class="col1">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 class="row2">
+ <td class="col0"><strong><code>model-name</code></strong></td><td class="col1">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 class="row3">
+ <td class="col0"><strong><code>model</code></strong></td><td class="col1">One line string holding additional parameters. Do not place the model parameters in parentheses â?? gnetlist will do this for you.</td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT826 TABLE [14257-14736] -->
</div>
-<h5><a name="spice_.model_or_.subckt_file" id="spice_.model_or_.subckt_file">SPICE .MODEL or .SUBCKT file</a></h5>
+<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:
+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>
+<div class="table sectionedit827"><table class="inline">
+ <tr class="row0">
+ <td class="col0"><strong><code>refdes</code></strong></td><td class="col1">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 class="row1">
+ <td class="col0"><strong><code>value</code></strong></td><td class="col1">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 class="row2">
+ <td class="col0"><strong><code>model-name</code></strong></td><td class="col1">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 class="row3">
+ <td class="col0"><strong><code>file</code></strong></td><td class="col1">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>
-
+</table></div>
+<!-- EDIT827 TABLE [14899-15792] -->
</div>
<h4><a name="independent_sources" id="independent_sources">Independent sources</a></h4>
@@ -444,7 +422,7 @@ To incorporate a file-full of SPICE parameters into the netlist, the following a
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 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>
@@ -485,7 +463,7 @@ In certain situations, you may wish to embed a spice model block directly into y
<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 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>
@@ -503,7 +481,7 @@ In certain situations, you may wish to embed a spice model block directly into y
</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 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>
@@ -528,7 +506,7 @@ In certain situations, you may wish to embed a spice model block directly into y
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 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>
@@ -558,10 +536,11 @@ Placing a SPICE directive block into your schematic creates an arbitrary block o
</ul>
<p>
- To place a SPICE directive on your schematic, do the following:
+
+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 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>
@@ -574,30 +553,31 @@ Placing a SPICE directive block into your schematic creates an arbitrary block o
</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>
+<!-- EDIT820 SECTION "Gschem attributes for spice netlisting" [7283-18697] -->
+<h3 class="sectionedit828"><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:
+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>
+<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>
+<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>
@@ -607,18 +587,18 @@ In SPICE modeling, there are often situations where you wish to create a schemat
</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 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>
+<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>
@@ -631,7 +611,8 @@ In SPICE modeling, there are often situations where you wish to create a schemat
</ol>
<p>
- Once the netlist is created, you may simulate your design using any SPICE simulator desired.<br/>
+
+Once the netlist is created, you may simulate your design using any SPICE simulator desired.<br/>
</p>
@@ -640,8 +621,8 @@ One final note: The netlister writes the contents of the lower level .SUBCKT fil
</p>
</div>
-<!-- SECTION "Handling hierarchical models" [18698-23545] -->
-<h2><a name="spice_netlist_generation" id="spice_netlist_generation">SPICE netlist generation</a></h2>
+<!-- EDIT828 SECTION "Handling hierarchical models" [18698-23545] -->
+<h2 class="sectionedit829"><a name="spice_netlist_generation" id="spice_netlist_generation">SPICE netlist generation</a></h2>
<div class="level2">
<p>
@@ -649,8 +630,8 @@ Once the schematic is captured, a SPICE netlist can be generated running the gED
</p>
</div>
-<!-- SECTION "SPICE netlist generation" [23546-24039] -->
-<h2><a name="creating_the_netlist" id="creating_the_netlist">Creating the netlist</a></h2>
+<!-- EDIT829 SECTION "SPICE netlist generation" [23546-24039] -->
+<h2 class="sectionedit830"><a name="creating_the_netlist" id="creating_the_netlist">Creating the netlist</a></h2>
<div class="level2">
<p>
@@ -659,19 +640,19 @@ Creating a netlist from a schematic is easy. To generate a SPICE netlist, just d
<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 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>
+<!-- EDIT830 SECTION "Creating the netlist" [24040-24765] -->
+<h2 class="sectionedit831"><a name="common_netlisting_problems" id="common_netlisting_problems">Common netlisting problems</a></h2>
<div class="level2">
<p>
@@ -683,8 +664,8 @@ It is important to manually inspect your SPICE netlist prior to using it in simu
</ul>
</div>
-<!-- SECTION "Common netlisting problems" [24766-25301] -->
-<h2><a name="spice_simulation" id="spice_simulation">SPICE simulation</a></h2>
+<!-- EDIT831 SECTION "Common netlisting problems" [24766-25301] -->
+<h2 class="sectionedit832"><a name="spice_simulation" id="spice_simulation">SPICE simulation</a></h2>
<div class="level2">
<p>
@@ -700,17 +681,19 @@ There are several options for doing SPICE simulations under Linux; I will highli
</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.
+
+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>
+<!-- EDIT832 SECTION "SPICE simulation" [25302-26547] -->
+<h3 class="sectionedit833"><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.
+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>
@@ -739,7 +722,7 @@ To install and configure LTSpice, do the following:
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 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>
@@ -751,41 +734,43 @@ LTSpice can read a file holding a gEDA SPICE netlist. I have had success doing L
</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 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 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.
+
+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>
+<!-- EDIT833 SECTION "LTSpice" [26548-29363] -->
+<h3 class="sectionedit834"><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.
+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 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 class="level1"><div class="li"> I got the <a href="geda-spice_polys.html" class="wikilink1" title="geda-spice_polys.html">POLY</a> 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.
+
+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>
@@ -801,21 +786,21 @@ To install ngspice and tclspice, do the following:
</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 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 <a href="geda-spice_polys.html" class="wikilink1" title="geda-spice_polys.html">POLYs</a> (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 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 <a href="geda-spice_polys.html" class="wikilink1" title="geda-spice_polys.html">POLY</a> 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>
+<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 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>
@@ -824,7 +809,8 @@ To install ngspice and tclspice, do the following:
</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.
+
+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>
@@ -834,8 +820,10 @@ To install ngspice and tclspice, do the following:
<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.
+
+To make use of the SPICE2 <a href="geda-spice_polys.html" class="wikilink1" title="geda-spice_polys.html">POLY</a> codemodel, you need to load it into ngspice <strong>before</strong> you load your netlist. (If you load it after loading your netlist, <a href="geda-spice_polys.html" class="wikilink1" title="geda-spice_polys.html">POLYs</a> 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>
@@ -845,7 +833,9 @@ Running ngspice is very simple. Just issue the command â??ngspice filename.net
<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:
+
+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
@@ -858,9 +848,12 @@ 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:
+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
@@ -887,181 +880,187 @@ while {1} {
}</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.
+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>
+<!-- EDIT834 SECTION "Ngspice and tclspice" [29364-40473] -->
+<h2 class="sectionedit835"><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>
+<!-- EDIT835 SECTION "Appendix" [40474-40495] -->
+<h3 class="sectionedit836"><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.
+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>
+<div class="table sectionedit837"><table class="inline">
+ <tr class="row0">
+ <th class="col0"><strong><code>device</code></strong></th><th class="col1"><strong><code>refdes</code></strong></th><th class="col2"><strong><code>value</code></strong></th><th class="col3"><strong><code>model</code></strong></th><th class="col4"><strong><code>file</code></strong></th><th class="col5"><strong><code>model-name</code></strong></th><th class="col6"><strong><code>type</code></strong></th><th class="col7">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 class="row1">
+ <td class="col0"><strong>RESISTOR</strong></td><td class="col1"><strong>R?</strong></td><td class="col2"><strong>Numeric comp. value</strong></td><td class="col3">One line of spice model parameters (e.g. TC)</td><td class="col4"> </td><td class="col5">Name of model.</td><td class="col6"> </td><td class="col7">â??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 class="row2">
+ <td class="col0"><strong>CAPACITOR</strong></td><td class="col1"><strong>C?</strong></td><td class="col2"><strong>Numeric comp. value</strong></td><td class="col3">One line of spice model parameters (e.g. IC, POLY, etc.)</td><td class="col4"> </td><td class="col5">Name of model.</td><td class="col6"> </td><td class="col7">â??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 class="row3">
+ <td class="col0"><strong>POLARIZED_CAPACITOR</strong></td><td class="col1"><strong>C?</strong></td><td class="col2"><strong>Numeric comp. value</strong></td><td class="col3">One line of spice model parameters (e.g. IC, POLY, etc.)</td><td class="col4"> </td><td class="col5">Name of model.</td><td class="col6"> </td><td class="col7">â??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 class="row4">
+ <td class="col0"><strong>INDUCTOR</strong></td><td class="col1"><strong>L?</strong></td><td class="col2"><strong>Numeric comp. value</strong></td><td class="col3">One line of spice model parameters (e.g. IC, POLY, etc.)</td><td class="col4"> </td><td class="col5">Name of model.</td><td class="col6"> </td><td class="col7">â??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 class="row5">
+ <td class="col0"><strong>SPICE-ccvs</strong></td><td class="col1"><strong>H?</strong></td><td class="col2"><strong>String describing source behavior</strong></td><td class="col3"> </td><td class="col4"> </td><td class="col5"> </td><td class="col6"> </td><td class="col7"> </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 class="row6">
+ <td class="col0"><strong>SPICE-cccs</strong></td><td class="col1"><strong>F?</strong></td><td class="col2"><strong>String describing source behavior</strong></td><td class="col3"> </td><td class="col4"> </td><td class="col5"> </td><td class="col6"> </td><td class="col7"> </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 class="row7">
+ <td class="col0"><strong>SPICE-vcvs</strong></td><td class="col1"><strong>E?</strong></td><td class="col2"><strong>String describing source behavior</strong></td><td class="col3"> </td><td class="col4"> </td><td class="col5"> </td><td class="col6"> </td><td class="col7"> </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 class="row8">
+ <td class="col0"><strong>SPICE-vccs</strong></td><td class="col1"><strong>G?</strong></td><td class="col2"><strong>String describing source behavior</strong></td><td class="col3"> </td><td class="col4"> </td><td class="col5"> </td><td class="col6"> </td><td class="col7"> </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 class="row9">
+ <td class="col0"><strong>SPICE-nullor</strong></td><td class="col1"><strong>E?</strong></td><td class="col2"><strong>String describing source behavior</strong></td><td class="col3"> </td><td class="col4"> </td><td class="col5"> </td><td class="col6"> </td><td class="col7"> </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 class="row10">
+ <td class="col0"><strong>DIODE</strong></td><td class="col1"><strong>D?</strong></td><td class="col2">Part number</td><td class="col3">One line SPICE model.</td><td class="col4">Model file name.</td><td class="col5"><strong>Name of model.</strong></td><td class="col6"> </td><td class="col7">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 class="row11">
+ <td class="col0"><strong>PMOS_TRANSISTOR</strong></td><td class="col1"><strong>M?</strong></td><td class="col2">Part number</td><td class="col3">One line SPICE model.</td><td class="col4">Model file name.</td><td class="col5"><strong>Name of model.</strong></td><td class="col6"> </td><td class="col7">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 class="row12">
+ <td class="col0"><strong>NMOS_TRANSISTOR</strong></td><td class="col1"><strong>M?</strong></td><td class="col2">Part number</td><td class="col3">One line SPICE model.</td><td class="col4">Model file name.</td><td class="col5"><strong>Name of model.</strong></td><td class="col6"> </td><td class="col7">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 class="row13">
+ <td class="col0"><strong>PNP_TRANSISTOR</strong></td><td class="col1"><strong>Q?</strong></td><td class="col2">Part number</td><td class="col3">One line SPICE model.</td><td class="col4">Model file name.</td><td class="col5"><strong>Name of model.</strong></td><td class="col6"> </td><td class="col7">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 class="row14">
+ <td class="col0"><strong>NPN_TRANSISTOR</strong></td><td class="col1"><strong>Q?</strong></td><td class="col2">Part number</td><td class="col3">One line SPICE model.</td><td class="col4">Model file name.</td><td class="col5"><strong>Name of model.</strong></td><td class="col6"> </td><td class="col7">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 class="row15">
+ <td class="col0"><strong>PFET_TRANSISTOR (JFET)</strong></td><td class="col1"><strong>J?</strong></td><td class="col2">Part number</td><td class="col3">One line SPICE model.</td><td class="col4">Model file name.</td><td class="col5"><strong>Name of model.</strong></td><td class="col6"> </td><td class="col7">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 class="row16">
+ <td class="col0"><strong>NFET_TRANSISTOR (JFET)</strong></td><td class="col1"><strong>J?</strong></td><td class="col2">Part number</td><td class="col3">One line SPICE model.</td><td class="col4">Model file name.</td><td class="col5"><strong>Name of model.</strong></td><td class="col6"> </td><td class="col7">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 class="row17">
+ <td class="col0"><strong>MESFET_TRANSISTOR</strong></td><td class="col1"><strong>B?</strong></td><td class="col2">Part number</td><td class="col3">One line SPICE model.</td><td class="col4">Model file name.</td><td class="col5"><strong>Name of model.</strong></td><td class="col6"> </td><td class="col7">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 class="row18">
+ <td class="col0"><strong>IC</strong></td><td class="col1"><strong>U?</strong></td><td class="col2">Part number</td><td class="col3">One line SPICE model.</td><td class="col4">Model file name.</td><td class="col5"><strong>Name of model.</strong></td><td class="col6"> </td><td class="col7">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 class="row19">
+ <td class="col0"><strong>IC</strong></td><td class="col1"><strong>X?</strong></td><td class="col2">Part number</td><td class="col3"> </td><td class="col4">Model file name.</td><td class="col5"><strong>Name of model.</strong></td><td class="col6"> </td><td class="col7">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 class="row20">
+ <td class="col0"><strong>model</strong></td><td class="col1" colspan="2"><strong>A?</strong></td><td class="col3">One line spice model</td><td class="col4">Model file name.</td><td class="col5"><strong>Name of model pointed to by other components.</strong></td><td class="col6"><strong>Corresponding SPICE model type (valid types given below)</strong>.</td><td class="col7">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 class="row21">
+ <td class="col0"><strong>include</strong></td><td class="col1"><strong>A?</strong></td><td class="col2"> </td><td class="col3"> </td><td class="col4"><strong>Include file name.</strong></td><td class="col5"> </td><td class="col6"> </td><td class="col7">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 class="row22">
+ <td class="col0"><strong>options</strong></td><td class="col1"><strong>A?</strong></td><td class="col2"><strong>Line of options to include.</strong></td><td class="col3"> </td><td class="col4"> </td><td class="col5"> </td><td class="col6"> </td><td class="col7">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 class="row23">
+ <td class="col0"><strong>directive</strong></td><td class="col1"><strong>A?</strong></td><td class="col2"><strong>One line string holding SPICE statements for inclusion in netlist.</strong></td><td class="col3"> </td><td class="col4"> </td><td class="col5"> </td><td class="col6"> </td><td class="col7">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 class="row24">
+ <td class="col0"><strong>VOLTAGE_SOURCE</strong></td><td class="col1"><strong>V?</strong></td><td class="col2"><strong>One line string holding voltage source behavior.</strong></td><td class="col3"> </td><td class="col4"> </td><td class="col5"> </td><td class="col6"> </td><td class="col7">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 class="row25">
+ <td class="col0"><strong>CURRENT_SOURCE</strong></td><td class="col1"><strong>I?</strong></td><td class="col2"><strong>One line string holding current source behavior.</strong></td><td class="col3"> </td><td class="col4"> </td><td class="col5"> </td><td class="col6"> </td><td class="col7">Independent current source</td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT837 TABLE [40882-44432] -->
<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.
+
+â??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>
+<!-- EDIT836 SECTION "Component attribute summary" [40496-45264] -->
+<h3 class="sectionedit838"><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:
+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>
+<div class="table sectionedit839"><table class="inline">
+ <tr class="row0">
+ <th class="col0">Component</th><th class="col1">â??typeâ??</th><th class="col2">Comment</th>
</tr>
- <tr>
- <td>RESISTOR</td><td>RES</td><td> </td>
+ <tr class="row1">
+ <td class="col0">RESISTOR</td><td class="col1">RES</td><td class="col2"> </td>
</tr>
- <tr>
- <td>CAPACITOR</td><td>CAP</td><td> </td>
+ <tr class="row2">
+ <td class="col0">CAPACITOR</td><td class="col1">CAP</td><td class="col2"> </td>
</tr>
- <tr>
- <td>POLARIZED_CAPACITOR</td><td>CAP</td><td> </td>
+ <tr class="row3">
+ <td class="col0">POLARIZED_CAPACITOR</td><td class="col1">CAP</td><td class="col2"> </td>
</tr>
- <tr>
- <td>INDUCTOR</td><td>IND</td><td> </td>
+ <tr class="row4">
+ <td class="col0">INDUCTOR</td><td class="col1">IND</td><td class="col2"> </td>
</tr>
- <tr>
- <td>DIODE</td><td>D</td><td> </td>
+ <tr class="row5">
+ <td class="col0">DIODE</td><td class="col1">D</td><td class="col2"> </td>
</tr>
- <tr>
- <td>PMOS_TRANSISTOR</td><td>PMOS</td><td> </td>
+ <tr class="row6">
+ <td class="col0">PMOS_TRANSISTOR</td><td class="col1">PMOS</td><td class="col2"> </td>
</tr>
- <tr>
- <td>NMOS_TRANSISTOR</td><td>NMOS</td><td> </td>
+ <tr class="row7">
+ <td class="col0">NMOS_TRANSISTOR</td><td class="col1">NMOS</td><td class="col2"> </td>
</tr>
- <tr>
- <td>PNP_TRANSISTOR</td><td>PNP</td><td> </td>
+ <tr class="row8">
+ <td class="col0">PNP_TRANSISTOR</td><td class="col1">PNP</td><td class="col2"> </td>
</tr>
- <tr>
- <td>NPN_TRANSISTOR</td><td>NPN</td><td> </td>
+ <tr class="row9">
+ <td class="col0">NPN_TRANSISTOR</td><td class="col1">NPN</td><td class="col2"> </td>
</tr>
- <tr>
- <td>PFET_TRANSISTOR</td><td>PJF</td><td> </td>
+ <tr class="row10">
+ <td class="col0">PFET_TRANSISTOR</td><td class="col1">PJF</td><td class="col2"> </td>
</tr>
- <tr>
- <td>NFET_TRANSISTOR</td><td>NJF</td><td> </td>
+ <tr class="row11">
+ <td class="col0">NFET_TRANSISTOR</td><td class="col1">NJF</td><td class="col2"> </td>
</tr>
- <tr>
- <td>MESFET_TRANSISTOR</td><td> </td><td> </td>
+ <tr class="row12">
+ <td class="col0">MESFET_TRANSISTOR</td><td class="col1"> </td><td class="col2"> </td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT839 TABLE [45496-45782] -->
</div>
-<!-- SECTION "Valid type values" [45185-45703] -->
-<h2><a name="document_history" id="document_history">Document History</a></h2>
+<!-- EDIT838 SECTION "Valid type values" [45265-45783] -->
+<h2 class="sectionedit840"><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>
+<div class="table sectionedit841"><table class="inline">
+ <tr class="row0">
+ <td class="col0">Revision 1.0</td><td class="col1">3.10.2003</td><td class="col2">SDB</td><td class="col3">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 class="row1">
+ <td class="col0">Revision 1.1</td><td class="col1">3.19.2003</td><td class="col2">SDB</td><td class="col3">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 class="row2">
+ <td class="col0">Revision 1.2</td><td class="col1">3.31.2003</td><td class="col2">SDB</td><td class="col3">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 class="row3">
+ <td class="col0">Revision 2.0</td><td class="col1">7.23.2003</td><td class="col2">SDB</td><td class="col3">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>
-
+</table></div>
+<!-- EDIT841 TABLE [45813-46320] -->
<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>
+
+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>
+<!-- EDIT840 SECTION "Document History" [45784-] --></body>
</html>
diff --git a/docs/wiki/geda-sn_readme.html b/docs/wiki/geda-sn_readme.html
index 039f97c..dc3013d 100644
--- a/docs/wiki/geda-sn_readme.html
+++ b/docs/wiki/geda-sn_readme.html
@@ -12,9 +12,7 @@
<body>
-
-
-<h1><a name="switcap_netlister_readme" id="switcap_netlister_readme">Switcap netlister README</a></h1>
+<h1 class="sectionedit1009"><a name="switcap_netlister_readme" id="switcap_netlister_readme">Switcap netlister README</a></h1>
<div class="level1">
<pre class="code">-----------------------------------------------------------------
I. What is this?
@@ -151,7 +149,6 @@ manually type the file names each time.
Refer to the SWITCAP manual for more details.
-
</pre>
</div>
diff --git a/docs/wiki/geda-spice_improvements.html b/docs/wiki/geda-spice_improvements.html
index 8451e13..b602fec 100644
--- a/docs/wiki/geda-spice_improvements.html
+++ b/docs/wiki/geda-spice_improvements.html
@@ -12,13 +12,13 @@
<body>
-
-
-<h1><a name="spice_simulation_improvements_in_gschem" id="spice_simulation_improvements_in_gschem">Spice simulation improvements in gschem</a></h1>
+<h1 class="sectionedit1299"><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>
+
+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>
diff --git a/docs/wiki/geda-spice_polys.html b/docs/wiki/geda-spice_polys.html
new file mode 100644
index 0000000..7bdb750
--- /dev/null
+++ b/docs/wiki/geda-spice_polys.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 class="sectionedit1442"><a name="spice_poly_constructs" id="spice_poly_constructs">Spice POLY Constructs</a></h1>
+<div class="level1">
+
+<p>
+
+This is a draft of what I've learned about POLYs. I'm not sure
+it's completely accurate, so anyone should feel free to make corrections.
+</p>
+
+<p>
+Different versions of spice use different methods of modeling non-linear
+dependent sources, Eg. ASRC, Bxxxx, Exxxx, Gxxxx, Fxxxx, Hxxxx, etcâ?¦
+</p>
+
+<p>
+Some like NGspice use arbitrary expressions with conditionals, others like GNUcap use polynomials and curve fitting. The POLY function seems to be the least common denominator of these, though Spice3 doesn't support them. Polynomials were the first tool used to approximate non-linear relationships because they are well behaved functions, and spice can easily find the derivative at a point which is used in the numerical solutions. The down side is you have to do some extra work with other tools to get the coefficients for your polynomial description.
+</p>
+
+<p>
+Some common problems with polynomial approximations are:
+
+</p>
+<ol>
+<li class="level1"><div class="li"> They rapidly become useless outside a limited domain. BSIM models are indeed prone to unphysical behavior at operating points outside the domain of their approximations because they use polynomial adjustments for some computations.</div>
+</li>
+<li class="level1"><div class="li"> It takes a lot of terms to do a decent approximation of a function whose shape isn't very â??polynomial likeâ??.</div>
+</li>
+</ol>
+
+<p>
+
+The other method is to use an arbitrary expression with something like if-then-else functionality or the piece wise linear functions. They are simpler to formulate but incur the risk of discontinuities which can cause serious convergence problems. However they are much more convenient for hacking something together.
+</p>
+
+<p>
+A lot of effort has gone into having the best of both worlds. The PWL functions often use small curves to smooth the transition from one derivative to the next. and the expressions using the if-then-else
+functions are forced to make gradual transitions between different values. In general the libraries use polynomial approximations where they can and constrain them to areas where they are useful. Examples of this in Gnucap are the fit and table statements.
+</p>
+
+<p>
+However, if you want to try out your models in other spice versions you'll probably want to do the extra work to describe their behavior in terms of the POLY statement which unfortunately (as of this writing) is not documented very well in Ngspice or Gnucap. Here is one place it is:
+</p>
+
+<p>
+<a href="http://newton.ex.ac.uk/teaching/CDHW/Electronics2/userguide/secC.html"; class="urlextern" title="http://newton.ex.ac.uk/teaching/CDHW/Electronics2/userguide/secC.html"; rel="nofollow">http://newton.ex.ac.uk/teaching/CDHW/Electronics2/userguide/secC.html</a>
+</p>
+
+<p>
+To do the curve fitting I suppose you could use tools like <a href="http://www.gnuplot.info"; class="urlextern" title="http://www.gnuplot.info"; rel="nofollow">Gnuplot</a>, <a href="http://plasma-gate.weizmann.ac.il/Grace"; class="urlextern" title="http://plasma-gate.weizmann.ac.il/Grace"; rel="nofollow">Grace</a>, or <a href="http://www.simfit.man.ac.uk"; class="urlextern" title="http://www.simfit.man.ac.uk"; rel="nofollow">Simfit</a>.
+</p>
+
+<p>
+Note that for Ngspice to support POLYs you need to set that compile time option see:
+<a href="http://www.brorson.com/gEDA/SPICE/x496.html"; class="urlextern" title="http://www.brorson.com/gEDA/SPICE/x496.html"; rel="nofollow">http://www.brorson.com/gEDA/SPICE/x496.html</a>
+</p>
+
+<p>
+
+ â?? <em><a href="mailto:clif@eugeneweb.com"; class="mail JSnocheck" title="clif@eugeneweb.com">Clif Eugene</a> 2010/11/23 01:31</em>
+
+</p>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-ssan.html b/docs/wiki/geda-ssan.html
index a7e6246..7b5f68c 100644
--- a/docs/wiki/geda-ssan.html
+++ b/docs/wiki/geda-ssan.html
@@ -11,55 +11,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>
+<h1 class="sectionedit1181"><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>
@@ -75,13 +28,14 @@ April 13th, 2003
</p>
</div>
-<!-- SECTION "gEDA/gaf Switcap Symbols and Netlister" [1-168] -->
-<h2><a name="overview" id="overview">Overview</a></h2>
+<!-- EDIT1181 SECTION "gEDA/gaf Switcap Symbols and Netlister" [1-168] -->
+<h2 class="sectionedit1182"><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:
+
+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>
@@ -99,8 +53,8 @@ This document describes the symbol library and gnetlist backend which supports d
</ol>
</div>
-<!-- SECTION "Overview" [169-924] -->
-<h2><a name="requirements" id="requirements">Requirements</a></h2>
+<!-- EDIT1182 SECTION "Overview" [169-924] -->
+<h2 class="sectionedit1183"><a name="requirements" id="requirements">Requirements</a></h2>
<div class="level2">
<p>
@@ -126,17 +80,18 @@ You will need the following programs to be installed:
</ol>
</div>
-<!-- SECTION "Requirements" [925-2127] -->
-<h2><a name="creating_schematics" id="creating_schematics">Creating Schematics</a></h2>
+<!-- EDIT1183 SECTION "Requirements" [925-2127] -->
+<h2 class="sectionedit1184"><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>
+<!-- EDIT1184 SECTION "Creating Schematics" [2128-2159] -->
+<h3 class="sectionedit1185"><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:
+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>
@@ -148,8 +103,8 @@ This section assumes you are familiar with using gschem to create and edit schem
</ol>
</div>
-<!-- SECTION "Required Symbols" [2160-3152] -->
-<h3><a name="optional_symbols" id="optional_symbols">Optional Symbols</a></h3>
+<!-- EDIT1185 SECTION "Required Symbols" [2160-3152] -->
+<h3 class="sectionedit1186"><a name="optional_symbols" id="optional_symbols">Optional Symbols</a></h3>
<div class="level3">
<p>
@@ -163,8 +118,8 @@ You can also optionally add the following SWITCAP special symbols to your schema
</ol>
</div>
-<!-- SECTION "Optional Symbols" [3153-3574] -->
-<h3><a name="net_names" id="net_names">Net Names</a></h3>
+<!-- EDIT1186 SECTION "Optional Symbols" [3153-3574] -->
+<h3 class="sectionedit1187"><a name="net_names" id="net_names">Net Names</a></h3>
<div class="level3">
<p>
@@ -172,8 +127,8 @@ When creating schematics to drive SWITCAP, you should name all nets that you wis
</p>
</div>
-<!-- SECTION "Net Names" [3575-3983] -->
-<h3><a name="switches" id="switches">Switches</a></h3>
+<!-- EDIT1187 SECTION "Net Names" [3575-3983] -->
+<h3 class="sectionedit1188"><a name="switches" id="switches">Switches</a></h3>
<div class="level3">
<p>
@@ -181,17 +136,19 @@ When placing switches on your schematic, you will need to define which clock the
</p>
</div>
-<!-- SECTION "Switches" [3984-4230] -->
-<h2><a name="extracting_the_switcap_netlist" id="extracting_the_switcap_netlist">Extracting the SWITCAP Netlist</a></h2>
+<!-- EDIT1188 SECTION "Switches" [3984-4230] -->
+<h2 class="sectionedit1189"><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:
+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:
+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>
@@ -200,28 +157,30 @@ 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>
+<!-- EDIT1189 SECTION "Extracting the SWITCAP Netlist" [4231-4570] -->
+<h2 class="sectionedit1190"><a name="running_switcap" id="running_switcap">Running SWITCAP</a></h2>
<div class="level2">
<p>
-I typically use something like:
+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.
+
+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>
+<!-- EDIT1190 SECTION "Running SWITCAP" [4571-4838] -->
+<h2 class="sectionedit1191"><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>
+<!-- EDIT1191 SECTION "Appendix A -- Symbols in the Library" [4839-4887] -->
+<h3 class="sectionedit1192"><a name="capacitors_switcap-capacitor" id="capacitors_switcap-capacitor">Capacitors (switcap-capacitor)</a></h3>
<div class="level3">
<p>
@@ -235,8 +194,8 @@ Ideal capacitor. Attributes:
</ul>
</div>
-<!-- SECTION "Capacitors (switcap-capacitor)" [4888-5108] -->
-<h3><a name="switches_switcap-switch" id="switches_switcap-switch">Switches (switcap-switch)</a></h3>
+<!-- EDIT1192 SECTION "Capacitors (switcap-capacitor)" [4888-5108] -->
+<h3 class="sectionedit1193"><a name="switches_switcap-switch" id="switches_switcap-switch">Switches (switcap-switch)</a></h3>
<div class="level3">
<p>
@@ -250,8 +209,8 @@ Ideal switch. Attributes:
</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>
+<!-- EDIT1193 SECTION "Switches (switcap-switch)" [5109-5340] -->
+<h3 class="sectionedit1194"><a name="independent_voltage_sources_switcap-vsrc" id="independent_voltage_sources_switcap-vsrc">Independent Voltage Sources (switcap-vsrc)</a></h3>
<div class="level3">
<p>
@@ -263,8 +222,8 @@ Attributes:
</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>
+<!-- EDIT1194 SECTION "Independent Voltage Sources (switcap-vsrc)" [5341-5488] -->
+<h3 class="sectionedit1195"><a name="dependent_voltage_sources_switcap-vcvs" id="dependent_voltage_sources_switcap-vcvs">Dependent Voltage Sources (switcap-vcvs)</a></h3>
<div class="level3">
<p>
@@ -278,8 +237,8 @@ Attributes:
</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>
+<!-- EDIT1195 SECTION "Dependent Voltage Sources (switcap-vcvs)" [5489-5708] -->
+<h3 class="sectionedit1196"><a name="clock_specification_switcap-clock" id="clock_specification_switcap-clock">Clock Specification (switcap-clock)</a></h3>
<div class="level3">
<p>
@@ -297,8 +256,8 @@ Attributes:
</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>
+<!-- EDIT1196 SECTION "Clock Specification (switcap-clock)" [5709-6302] -->
+<h3 class="sectionedit1197"><a name="master_timing_specification_switcap-timing" id="master_timing_specification_switcap-timing">Master Timing Specification (switcap-timing)</a></h3>
<div class="level3">
<p>
@@ -310,12 +269,13 @@ Attributes:
</ul>
<p>
- Only a single instance of this symbol is allowed.
+
+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>
+<!-- EDIT1197 SECTION "Master Timing Specification (switcap-timing)" [6303-6509] -->
+<h3 class="sectionedit1198"><a name="analysis_file_include_switcap-analysis" id="analysis_file_include_switcap-analysis">Analysis File Include (switcap-analysis)</a></h3>
<div class="level3">
<p>
@@ -327,8 +287,8 @@ This symbol will cause a specified file containing SWITCAP analysis commands to
</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>
+<!-- EDIT1198 SECTION "Analysis File Include (switcap-analysis)" [6510-6756] -->
+<h3 class="sectionedit1199"><a name="simulation_title_specification_switcap-title" id="simulation_title_specification_switcap-title">Simulation Title Specification (switcap-title)</a></h3>
<div class="level3">
<p>
@@ -340,12 +300,13 @@ Attributes:
</ul>
<p>
- Only a single instance of this symbol is allowed.
+
+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>
+<!-- EDIT1199 SECTION "Simulation Title Specification (switcap-title)" [6757-6966] -->
+<h3 class="sectionedit1200"><a name="simulation_options_specification_switcap-options" id="simulation_options_specification_switcap-options">Simulation Options Specification (switcap-options)</a></h3>
<div class="level3">
<p>
@@ -357,102 +318,112 @@ Attributes:
</ul>
<p>
- Only a single instance of this symbol is allowed.
+
+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>
+<!-- EDIT1200 SECTION "Simulation Options Specification (switcap-options)" [6967-7229] -->
+<h2 class="sectionedit1201"><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.
+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>
+<div class="table sectionedit1202"><table class="inline">
+ <tr class="row0">
+ <td class="col0"> <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 class="row1">
+ <td class="col0"> <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 class="row2">
+ <td class="col0"> <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 class="row3">
+ <td class="col0"> <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>
-
+</table></div>
+<!-- EDIT1202 TABLE [7417-7552] -->
<p>
- Figure 5/6: Simulation Results - Transient MISSING
+
+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>
+<!-- EDIT1201 SECTION "Example" [7230-7605] -->
+<h3 class="sectionedit1203"><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.
+
+<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>
+<!-- EDIT1203 SECTION "Example Schematics" [7606-8677] -->
+<h3 class="sectionedit1204"><a name="netlist_the_design" id="netlist_the_design">Netlist the Design</a></h3>
<div class="level3">
<p>
-To netlist the design, run:
+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>
+<!-- EDIT1204 SECTION "Netlist the Design" [8678-8815] -->
+<h3 class="sectionedit1205"><a name="run_the_simulation" id="run_the_simulation">Run the Simulation</a></h3>
<div class="level3">
<p>
-Run the simulation with:
+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>
+<!-- EDIT1205 SECTION "Run the Simulation" [8816-8924] -->
+<h3 class="sectionedit1206"><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:
+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>
+<!-- EDIT1206 SECTION "Process the Results" [8925-9059] -->
+<h3 class="sectionedit1207"><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:
+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:
+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>
+<!-- EDIT1207 SECTION "Plot the Results" [9060-9446] -->
+<h2 class="sectionedit1208"><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>
+<div class="table sectionedit1209"><table class="inline">
+ <tr class="row0">
+ <td class="col0"> April 13th, 2003 </td><td class="col1"> Created switcap.tex </td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT1209 TABLE [9485-9527] -->
</div>
-<!-- SECTION "Document Revision History" [9447-] --></body>
+<!-- EDIT1208 SECTION "Document Revision History" [9447-] --></body>
</html>
diff --git a/docs/wiki/geda-start.html b/docs/wiki/geda-start.html
index 483bd45..5f91f6c 100644
--- a/docs/wiki/geda-start.html
+++ b/docs/wiki/geda-start.html
@@ -13,11 +13,13 @@
<p>
- This is just a placeholder page.
+
+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>
+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
index 37b05b7..789d35d 100644
--- a/docs/wiki/geda-style_guide.html
+++ b/docs/wiki/geda-style_guide.html
@@ -11,63 +11,56 @@
</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>
+<h1 class="sectionedit76"><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/>
+
+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>
+<!-- EDIT76 SECTION "Style Guide" [1-472] -->
+<h2 class="sectionedit77"><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.
+
+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>
+<!-- EDIT77 SECTION "Downloading/Installing pavuk" [473-1190] -->
+<h2 class="sectionedit78"><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.
+
+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>
+<!-- EDIT78 SECTION "Downloading/Installing HTMLDOC" [1191-2172] -->
+<h2 class="sectionedit79"><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>
@@ -76,81 +69,57 @@ The following are meant to stimulate discussion on document style:
<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 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 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 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"
+<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:<em>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>
+% htmldoc {page-name}.iconv -t pdf14 â??webpage â??no-title â??linkstyle underline â??size letter â??left 1.00in <br/>
-<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>
+ â??right 0.50in â??top 0.50in â??bottom 0.50in â??header .t. â??footer . â??nup 1 â??tocheader .t. â??tocfooter ..i <br/>
-<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>
+ â??portrait â??color â??no-pscommands â??no-xrxcomments â??compression=1 â??jpeg=0 â??fontsize 11.0 â??fontspacing 1.2 <br/>
-<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>
+ â??headingfont Helvetica â??bodyfont Times â??headfootsize 11.0 â??headfootfont Helvetica â??charset iso-8859-1 <br/>
-</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">
+ â??links â??no-embedfonts â??pagemode document â??pagelayout single â??firstpage p1 â??pageeffect none <br/>
-<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>
+ â??pageduration 10 â??effectduration 1.0 â??no-encryption â??permissions all â??owner-password â??â??
+ â??user-password â??â?? â??browserwidth 680 -f {page-name}.pdf</xterm> <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>
-<!-- SECTION "For new documents:" [5273-6383] -->
-<h2><a name="for_existing_documents" id="for_existing_documents">For existing documents:</a></h2>
-<div class="level2">
+For example, you would replace {page-name} above with the following for the related wiki-page:
+ * 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>.
+ * 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>.
+ * 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>
-<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.
+
+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>.
+
+===== For new documents: =====
The following are meant to stimulate discussion on document style:
-</p>
-<ol>
-<li class="level1"><div class="li"> </div>
+ - 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.
+ - <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.
+ - 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).
+
+===== For existing documents: =====
+The following are meant to stimulate discussion on document style:
+ -
+</div>
+</li>
+</ul>
</li>
</ol>
</div>
-<!-- SECTION "For existing documents:" [6384-] --></body>
+<!-- EDIT79 SECTION "For both existing and new documents" [2173-] --></body>
</html>
diff --git a/docs/wiki/geda-suse_10.0.html b/docs/wiki/geda-suse_10.0.html
index 8559155..cfbc10f 100644
--- a/docs/wiki/geda-suse_10.0.html
+++ b/docs/wiki/geda-suse_10.0.html
@@ -12,14 +12,12 @@
<body>
-
-
-<h1><a name="suse_10.0_install_notes" id="suse_10.0_install_notes">Suse 10.0 install notes</a></h1>
+<h1 class="sectionedit103"><a name="suse_100_install_notes" id="suse_100_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>
+<!-- EDIT103 SECTION "Suse 10.0 install notes" [1-39] -->
+<h2 class="sectionedit104"><a name="prerequisites" id="prerequisites">Prerequisites:</a></h2>
<div class="level2">
<p>
@@ -31,7 +29,7 @@ Secondly, if you are installing gEDA onto a pre-existing SuSE system, make sure
</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.
+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>
@@ -51,7 +49,8 @@ When installing SuSE-10.0 using YaST, click on the â??changeâ?? button when YaST
</ul>
<p>
- Then change the filter to search for and install the following packages:
+
+Then change the filter to search for and install the following packages:
</p>
<ul>
<li class="level1"><div class="li"> Gtk-devel</div>
@@ -65,9 +64,11 @@ When installing SuSE-10.0 using YaST, click on the â??changeâ?? button when YaST
</ul>
<p>
- Once these packages are installed, the installer should run to completion.
+
+Once these packages are installed, the installer should run to completion.
+
</p>
</div>
-<!-- SECTION "Prerequisites:" [40-] --></body>
+<!-- EDIT104 SECTION "Prerequisites:" [40-] --></body>
</html>
diff --git a/docs/wiki/geda-suse_10.1.html b/docs/wiki/geda-suse_10.1.html
index 7605d8a..ca0dc73 100644
--- a/docs/wiki/geda-suse_10.1.html
+++ b/docs/wiki/geda-suse_10.1.html
@@ -12,9 +12,7 @@
<body>
-
-
-<h1><a name="suse_10.1_install_notes" id="suse_10.1_install_notes">Suse 10.1 install notes</a></h1>
+<h1 class="sectionedit187"><a name="suse_101_install_notes" id="suse_101_install_notes">Suse 10.1 install notes</a></h1>
<div class="level1">
<p>
@@ -22,8 +20,8 @@ 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>
+<!-- EDIT187 SECTION "Suse 10.1 install notes" [1-101] -->
+<h2 class="sectionedit188"><a name="prerequisites" id="prerequisites">Prerequisites:</a></h2>
<div class="level2">
<p>
@@ -41,9 +39,10 @@ When installing SuSE-10.1, click on the â??changeâ?? button when YaST shows you
</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.
+
+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>
+<!-- EDIT188 SECTION "Prerequisites:" [102-] --></body>
</html>
diff --git a/docs/wiki/geda-suse_9.3.html b/docs/wiki/geda-suse_9.3.html
index c0c8ce8..1d9f311 100644
--- a/docs/wiki/geda-suse_9.3.html
+++ b/docs/wiki/geda-suse_9.3.html
@@ -12,14 +12,12 @@
<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>
+<h1 class="sectionedit1297"><a name="installer_2005080x_on_suse_93_install_notes" id="installer_2005080x_on_suse_93_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>
+<!-- EDIT1297 SECTION "Installer 2005080X on Suse 9.3 install notes" [1-59] -->
+<h2 class="sectionedit1298"><a name="prerequisites" id="prerequisites">Prerequisites:</a></h2>
<div class="level2">
<p>
@@ -39,7 +37,8 @@ When installing SuSE using YaST, click on the â??changeâ?? button when YaST show
</ul>
<p>
- Then change the filter to search for and install the following packages:
+
+Then change the filter to search for and install the following packages:
</p>
<ul>
<li class="level1"><div class="li"> Gtk-devel</div>
@@ -53,7 +52,8 @@ When installing SuSE using YaST, click on the â??changeâ?? button when YaST show
</ul>
<p>
- Once these packages are installed, the installer should run to completion.
+
+Once these packages are installed, the installer should run to completion.
</p>
<p>
@@ -61,5 +61,5 @@ When installing SuSE using YaST, click on the â??changeâ?? button when YaST show
</p>
</div>
-<!-- SECTION "Prerequisites:" [60-] --></body>
+<!-- EDIT1298 SECTION "Prerequisites:" [60-] --></body>
</html>
diff --git a/docs/wiki/geda-suse_rpm_installation.html b/docs/wiki/geda-suse_rpm_installation.html
index 09f0df5..51fa953 100644
--- a/docs/wiki/geda-suse_rpm_installation.html
+++ b/docs/wiki/geda-suse_rpm_installation.html
@@ -11,74 +11,46 @@
</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>
+<h1 class="sectionedit1300"><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>
+<!-- EDIT1300 SECTION "Installing gEDA rpm packages on SuSE" [1-54] -->
+<h2 class="sectionedit1301"><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 class="level1"><div class="li"> geda (1.6.1)</div>
</li>
-<li class="level1"><div class="li"> gerbv (2.2.0)</div>
+<li class="level1"><div class="li"> gerbv (2.3.0)</div>
</li>
-<li class="level1"><div class="li"> pcb (20081128)</div>
+<li class="level1"><div class="li"> pcb (20091103)</div>
</li>
-<li class="level1"><div class="li"> ng-spice-rework (18)</div>
+<li class="level1"><div class="li"> ng-spice-rework (20)</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 class="level1"><div class="li"> gspiceui (0.9.98)</div>
</li>
-<li class="level1"><div class="li"> gwave (20090114)</div>
+<li class="level1"><div class="li"> gwave (20090213)</div>
</li>
-<li class="level1"><div class="li"> gtkwave (3.1.10)</div>
+<li class="level1"><div class="li"> gtkwave (3.3.3)</div>
</li>
-<li class="level1"><div class="li"> dinotrace (9.3f)</div>
+<li class="level1"><div class="li"> dinotrace (9.4a)</div>
</li>
-<li class="level1"><div class="li"> verilog (0.8.7)</div>
+<li class="level1"><div class="li"> verilog (0.9.1)</div>
</li>
-<li class="level1"><div class="li"> wcalc (1.0)</div>
+<li class="level1"><div class="li"> wcalc (1.1)</div>
</li>
-<li class="level1"><div class="li"> xgsch2pcb (0.1.2)</div>
+<li class="level1"><div class="li"> xgsch2pcb (0.1.3)</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>
+<!-- EDIT1301 SECTION "Available rpm packages" [55-359] -->
+<h2 class="sectionedit1302"><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>
@@ -94,7 +66,7 @@
</ol>
<p>
- (Choose the directory for your distribution)
+ (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>
@@ -104,63 +76,61 @@
</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>
+
+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>.
+You can also browse through repositories first:
+<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>.
+<a href="http://software.opensuse.org/download/science/openSUSE_11.2/repodata/"; class="urlextern" title="http://software.opensuse.org/download/science/openSUSE_11.2/repodata/"; rel="nofollow"> openSUSE_11.2 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>
+<!-- EDIT1302 SECTION "Installing Packages from the SuSE Build Service" [360-1361] -->
+<h2 class="sectionedit1303"><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.
+
+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>
+<!-- EDIT1303 SECTION "Distribution specific notes" [1362-1479] -->
+<h3 class="sectionedit1304"><a name="opensuse_110" id="opensuse_110">openSUSE 11.0</a></h3>
<div class="level3">
<ul>
-<li class="level1"><div class="li"> no longer available</div>
+<li class="level1"><div class="li"> â?¦</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>
+<!-- EDIT1304 SECTION "openSUSE 11.0" [1480-1512] -->
+<h3 class="sectionedit1305"><a name="opensuse_111" id="opensuse_111">openSUSE 11.1</a></h3>
<div class="level3">
<ul>
-<li class="level1"><div class="li"> …</div>
+<li class="level1"><div class="li"> currently no electronics menu, all programs show up in the Educationâ??Science menu</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 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>
+<!-- EDIT1305 SECTION "openSUSE 11.1" [1513-1632] -->
+<h3 class="sectionedit1306"><a name="opensuse_112" id="opensuse_112">openSUSE 11.2</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 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 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>
+<!-- EDIT1306 SECTION "openSUSE 11.2" [1633-1752] -->
+<h2 class="sectionedit1307"><a name="desktop_integration" id="desktop_integration">Desktop Integration</a></h2>
<div class="level2">
<p>
@@ -168,12 +138,14 @@ This is a summary how the gEDA and other electronic packages are integrated into
</p>
</div>
-<!-- SECTION "Desktop Integration" [1716-1855] -->
-<h3><a name="electronics_menu" id="electronics_menu">Electronics Menu</a></h3>
+<!-- EDIT1307 SECTION "Desktop Integration" [1753-1892] -->
+<h3 class="sectionedit1308"><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.
+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>
@@ -185,16 +157,19 @@ If it is installed, it looks like this in KDE (manually combined with gimp):
</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>
+<!-- EDIT1308 SECTION "Electronics Menu" [1893-2393] -->
+<h3 class="sectionedit1309"><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.
+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.
+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>
@@ -208,7 +183,11 @@ if test -f %{_bindir}/update-mime-database ; then
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
+
+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
@@ -220,35 +199,45 @@ if test %{_datadir} != $kdemimedir ; then
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>
+<!-- EDIT1309 SECTION "Notes about rpm spec file" [2394-3783] -->
+<h3 class="sectionedit1310"><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
+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
+
+or call only the two required subconfiguration tools
+
</p>
<pre class="code">/sbin/conf.d/SuSEconfig.desktop-file-utils </pre>
<p>
- which calls
+
+which calls
+
</p>
<pre class="code">/usr/bin/update-desktop-database</pre>
<p>
- and
+
+and
+
</p>
<pre class="code">/sbin/conf.d/SuSEconfig.gtk2</pre>
<p>
- which calls
+
+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>
+<!-- EDIT1310 SECTION "Installing rpm packages manually" [3784-] --></body>
</html>
diff --git a/docs/wiki/geda-syntax_features.html b/docs/wiki/geda-syntax_features.html
index 8cdb288..ef4912e 100644
--- a/docs/wiki/geda-syntax_features.html
+++ b/docs/wiki/geda-syntax_features.html
@@ -12,9 +12,7 @@
<body>
-
-
-<h1><a name="syntax_features" id="syntax_features">Syntax features</a></h1>
+<h1 class="sectionedit1311"><a name="syntax_features" id="syntax_features">Syntax features</a></h1>
<div class="level1">
<p>
@@ -41,16 +39,16 @@ The new gEDA Project Wiki pages are hosted using Dokuwiki version 09 March 2006.
</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 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 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 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>
diff --git a/docs/wiki/geda-systemc_netlister_readme.html b/docs/wiki/geda-systemc_netlister_readme.html
index a1ed4d4..4ee0c50 100644
--- a/docs/wiki/geda-systemc_netlister_readme.html
+++ b/docs/wiki/geda-systemc_netlister_readme.html
@@ -12,9 +12,7 @@
<body>
-
-
-<h1><a name="systemc_netlister_readme" id="systemc_netlister_readme">SystemC netlister README</a></h1>
+<h1 class="sectionedit1312"><a name="systemc_netlister_readme" id="systemc_netlister_readme">SystemC netlister README</a></h1>
<div class="level1">
<pre class="code">TITLE:
@@ -100,7 +98,6 @@ EXAMPLE:
alg1.OUT(b);
}
};
-
</pre>
</div>
diff --git a/docs/wiki/geda-tasks.html b/docs/wiki/geda-tasks.html
index 1bbaec6..132f4b1 100644
--- a/docs/wiki/geda-tasks.html
+++ b/docs/wiki/geda-tasks.html
@@ -11,79 +11,68 @@
</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>
+<h1 class="sectionedit1313"><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.
+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>
+<!-- EDIT1313 SECTION "gEDA Tasks" [1-137] -->
+<h2 class="sectionedit1314"><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>
+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>
+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>
+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>
+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>
+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>
+<!-- EDIT1314 SECTION "Important tasks for normal volunteers" [138-2142] -->
+<h2 class="sectionedit1315"><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>
+
+<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>
+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>
+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>
+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>
+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>
+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>
+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>
+<!-- EDIT1315 SECTION "Tasks for programmers" [2143-] --></body>
</html>
diff --git a/docs/wiki/geda-todos.html b/docs/wiki/geda-todos.html
index ae00cd4..8758d79 100644
--- a/docs/wiki/geda-todos.html
+++ b/docs/wiki/geda-todos.html
@@ -11,30 +11,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="#stable" class="toc">1.6.1 (stable)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#stable1" class="toc">1.6.2 (stable)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#stable2" 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>
+<h1 class="sectionedit1316"><a name="todos" id="todos">Todos</a></h1>
<div class="level1">
<p>
@@ -45,13 +23,19 @@ These lists are meant to provide the developers a reminder of undone projects. I
See <a href="geda-tasks.html" class="wikilink1" title="geda-tasks.html">tasks</a> for non-programmer tasks.
</p>
+<p>
+
+The <a href="pcb-roadmap.html" class="wikilink1" title="pcb-roadmap.html"> PCB Roadmap</a> is on a separate page.
+</p>
+
</div>
-<!-- SECTION "Todos" [1-304] -->
-<h2><a name="release_roadmap" id="release_roadmap">Release roadmap</a></h2>
+<!-- EDIT1316 SECTION "Todos" [1-361] -->
+<h2 class="sectionedit1317"><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.
+
+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>
@@ -59,152 +43,163 @@ Todos for past releases can be seen on the <a href="geda-todos_historical.html"
</p>
</div>
-<!-- SECTION "Release roadmap" [305-709] -->
-<h3><a name="stable" id="stable">1.6.1 (stable)</a></h3>
+<!-- EDIT1317 SECTION "Release roadmap" [362-766] -->
+<h3 class="sectionedit1318"><a name="stable" id="stable">1.6.1 (stable)</a></h3>
<div class="level3">
<p>
- Target release date: <strong>February 2010</strong> <br/>
- Actual release date: <strong>TBD</strong>
+
+Target release date: <strong>February 2010</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>
+<div class="table sectionedit1319"><table class="inline">
+ <tr class="row0">
+ <th class="col0 leftalign"> Description </th><th class="col1 leftalign"> SF bug </th><th class="col2 leftalign"> Developer(s) </th><th class="col3 leftalign"> Status </th>
</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 class="row1">
+ <td class="col0"> Screenshots of release version for a publicity revamp of gEDA website. </td><td class="col1 centeralign"> n/a </td><td class="col2"> Peter C </td><td class="col3"> </td>
</tr>
- <tr>
- <td> Merge translations from Launchpad upstream. </td><td class="centeralign"> n/a </td><td class="leftalign"> Peter C </td><td> Ongoing sync </td>
+ <tr class="row2">
+ <td class="col0"> Merge translations from Launchpad upstream. </td><td class="col1 centeralign"> n/a </td><td class="col2 leftalign"> Peter C </td><td class="col3"> Ongoing sync </td>
</tr>
- <tr>
- <td class="leftalign"> Check copyright headers are up-to-date </td><td class="centeralign"> n/a </td><td> Ales H </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=bd34cfde2450790b357e574281f9562adce64303"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=bd34cfde2450790b357e574281f9562adce64303"; rel="nofollow"> Done </a> </td>
+ <tr class="row3">
+ <td class="col0 leftalign"> Check copyright headers are up-to-date </td><td class="col1 centeralign"> n/a </td><td class="col2"> Ales H </td><td class="col3"> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=bd34cfde2450790b357e574281f9562adce64303"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=bd34cfde2450790b357e574281f9562adce64303"; rel="nofollow"> Done </a> </td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT1319 TABLE [866-1320] -->
</div>
-<!-- SECTION "1.6.1 (stable)" [710-1264] -->
-<h3><a name="stable1" id="stable1">1.6.2 (stable)</a></h3>
+<!-- EDIT1318 SECTION "1.6.1 (stable)" [767-1321] -->
+<h3 class="sectionedit1320"><a name="stable1" id="stable1">1.6.2 (stable)</a></h3>
<div class="level3">
<p>
- Target release date: <strong>Unknown</strong> <br/>
- Actual release date: <strong>TBD</strong>
+
+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>
+<div class="table sectionedit1321"><table class="inline">
+ <tr class="row0">
+ <th class="col0 leftalign"> Description </th><th class="col1 leftalign"> SF bug </th><th class="col2 leftalign"> Developer(s) </th><th class="col3 leftalign"> Status </th>
</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 class="row1">
+ <td class="col0"> Screenshots of release version for a publicity revamp of gEDA website. </td><td class="col1 centeralign"> n/a </td><td class="col2"> Peter C </td><td class="col3"> </td>
</tr>
- <tr>
- <td> Merge translations from Launchpad upstream. </td><td class="centeralign"> n/a </td><td class="leftalign"> Peter C </td><td> </td>
+ <tr class="row2">
+ <td class="col0"> Merge translations from Launchpad upstream. </td><td class="col1 centeralign"> n/a </td><td class="col2 leftalign"> Peter C </td><td class="col3"> </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 class="row3">
+ <td class="col0 leftalign"> Check copyright headers are up-to-date </td><td class="col1 centeralign"> n/a </td><td class="col2 leftalign"> </td><td class="col3 leftalign"> </td>
</tr>
- <tr>
- <td> UTF-8 / system / filesystem encoding bugs </td><td> <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> </td><td> </td><td> </td>
+ <tr class="row4">
+ <td class="col0"> UTF-8 / system / filesystem encoding bugs </td><td class="col1"> <a href="https://bugs.launchpad.net/geda/+bug/sf-1868072"; class="urlextern" title="https://bugs.launchpad.net/geda/+bug/sf-1868072"; rel="nofollow"> 1868072</a> </td><td class="col2"> </td><td class="col3"> </td>
</tr>
- <tr>
- <td> Prettify symbols (e.g. gates) using paths </td><td class="centeralign"> n/a </td><td class="rightalign"> </td><td class="rightalign"> </td>
+ <tr class="row5">
+ <td class="col0"> Prettify symbols (e.g. gates) using paths </td><td class="col1 centeralign"> n/a </td><td class="col2 leftalign"> </td><td class="col3 leftalign"> </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 class="row6">
+ <td class="col0"> Cure all: â??warning : ignoring return value of â??â?¦â??, declared with attribute warn_unused_resultâ?? compiling with recent GCC versions </td><td class="col1"> </td><td class="col2"> </td><td class="col3"> </td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT1321 TABLE [1415-2084] -->
</div>
-<!-- SECTION "1.6.2 (stable)" [1265-2066] -->
-<h3><a name="stable2" id="stable2">1.8 (stable)</a></h3>
+<!-- EDIT1320 SECTION "1.6.2 (stable)" [1322-2086] -->
+<h3 class="sectionedit1322"><a name="stable2" id="stable2">1.8 (stable)</a></h3>
<div class="level3">
<p>
- Target release date: <strong>Unknown</strong> <br/>
- Actual release date: <strong>TBD</strong>
+
+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>
+<div class="table sectionedit1323"><table class="inline">
+ <tr class="row0">
+ <th class="col0 leftalign"> Description </th><th class="col1 leftalign"> SF bug </th><th class="col2 leftalign"> Developer(s) </th><th class="col3 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 class="row1">
+ <td class="col0 leftalign"> TinyScheme instead of Guile </td><td class="col1 leftalign"> </td><td class="col2 leftalign"> Peter B </td><td class="col3 leftalign"> </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 class="row2">
+ <td class="col0 leftalign"> Per-page netlisting in libgeda </td><td class="col1 leftalign"> </td><td class="col2 leftalign"> Peter C </td><td class="col3 leftalign"> </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 class="row3">
+ <td class="col0 leftalign"> Refactor / improve gnetlist </td><td class="col1 leftalign"> </td><td class="col2 leftalign"> Peter C </td><td class="col3 leftalign"> </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 class="row4">
+ <td class="col0 leftalign"> gnetlist support for buses </td><td class="col1 leftalign"> </td><td class="col2 leftalign"> Peter C </td><td class="col3 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 class="row5">
+ <td class="col0 leftalign"> Avoid direct use of /tmp/ for undo schemaics </td><td class="col1 leftalign"> </td><td class="col2 leftalign"> </td><td class="col3 leftalign"> </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 class="row6">
+ <td class="col0"> New config mechanism to support non-turing complete config </td><td class="col1 leftalign"> </td><td class="col2 leftalign"> Peter B </td><td class="col3 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 class="row7">
+ <td class="col0"> Config <acronym title="Graphical User Interface">GUI</acronym> for gschem (and gattrib?) </td><td class="col1 leftalign"> </td><td class="col2 leftalign"> Peter B </td><td class="col3 leftalign"> </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 class="row8">
+ <td class="col0"> More non-modal dialog boxes in gschem </td><td class="col1 leftalign"> </td><td class="col2 leftalign"> Ed (?) </td><td class="col3 leftalign"> </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 class="row9">
+ <td class="col0"> Refactor gschem's action state machine and event dispatching code </td><td class="col1 leftalign"> </td><td class="col2 leftalign"> Ed </td><td class="col3 leftalign"> </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 class="row10">
+ <td class="col0"> Where possible, ensure gEDA compiles with deprecated GTK / GLib APIs disabled </td><td class="col1 leftalign"> </td><td class="col2 leftalign"> </td><td class="col3 leftalign"> </td>
</tr>
- <tr>
- <td class="leftalign"> Edit embedded symbols </td><td class="rightalign"> </td><td class="leftalign"> Werner (?) </td><td class="rightalign"> </td>
+ <tr class="row11">
+ <td class="col0 leftalign"> Edit embedded symbols </td><td class="col1 leftalign"> </td><td class="col2 leftalign"> Werner (?) </td><td class="col3 leftalign"> </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 class="row12">
+ <td class="col0"> Per project symbol storage to make the schematics independant from the symbol library </td><td class="col1 leftalign"> </td><td class="col2 leftalign"> Werner (?) </td><td class="col3 leftalign"> </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 class="row13">
+ <td class="col0"> <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="col1 leftalign"> </td><td class="col2"> Peter C (?) </td><td class="col3 leftalign"> </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 class="row14">
+ <td class="col0"> <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 class="col1"> </td><td class="col2"> Peter C (?) </td><td class="col3 leftalign"> </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 class="row15">
+ <td class="col0 leftalign"> Refactor rendering code to allow its use outside of gschem </td><td class="col1 leftalign"> </td><td class="col2 leftalign"> Peter C </td><td class="col3 leftalign"> </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 class="row16">
+ <td class="col0 leftalign"> Refactor preview widget to make it available outside gschem </td><td class="col1 leftalign"> </td><td class="col2 leftalign"> Peter C </td><td class="col3 leftalign"> </td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT1323 TABLE [2177-4138] -->
<p>
- Wishlist
+
+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>
+<div class="table sectionedit1324"><table class="inline">
+ <tr class="row0">
+ <th class="col0 leftalign"> Description </th><th class="col1 leftalign"> SF bug </th><th class="col2 leftalign"> Developer(s) </th><th class="col3 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 class="row1">
+ <td class="col0"> Printing improvements (Arbitrary UTF8 postscript) - print with cairo </td><td class="col1 centeralign"> n/a </td><td class="col2 leftalign"> Peter B, Peter C </td><td class="col3"> 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 class="row2">
+ <td class="col0"> gschem: interface for creating paths and inserting / deleting nodes </td><td class="col1 centeralign"> n/a </td><td class="col2 leftalign"> </td><td class="col3"> </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 class="row3">
+ <td class="col0"> Bitmap export options: allow specifying DPI rather than / as well as absolute page size </td><td class="col1"> <a href="https://bugs.launchpad.net/geda/+bug/sf-2226522"; class="urlextern" title="https://bugs.launchpad.net/geda/+bug/sf-2226522"; rel="nofollow"> 2226522 </a> </td><td class="col2"> </td><td class="col3"> </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 class="row4">
+ <td class="col0"> Set print border size </td><td class="col1"> <a href="https://bugs.launchpad.net/geda/+bug/sf-2243238"; class="urlextern" title="https://bugs.launchpad.net/geda/+bug/sf-2243238"; rel="nofollow"> 2243238 </a> </td><td class="col2"> Werner </td><td class="col3"> </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 class="row5">
+ <td class="col0"> Allow setting gschem on-screen border </td><td class="col1"> <a href="https://bugs.launchpad.net/geda/+bug/sf-2243238"; class="urlextern" title="https://bugs.launchpad.net/geda/+bug/sf-2243238"; rel="nofollow"> 2243238 </a> </td><td class="col2"> </td><td class="col3"> </td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT1324 TABLE [4152-4851] -->
</div>
-<!-- SECTION "1.8 (stable)" [2067-4963] -->
-<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>
+<!-- EDIT1322 SECTION "1.8 (stable)" [2087-4854] -->
+<h2 class="sectionedit1325"><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>
@@ -239,11 +234,11 @@ Todos for past releases can be seen on the <a href="geda-todos_historical.html"
</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 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 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>
@@ -267,7 +262,7 @@ Todos for past releases can be seen on the <a href="geda-todos_historical.html"
</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 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>
@@ -281,7 +276,7 @@ Todos for past releases can be seen on the <a href="geda-todos_historical.html"
<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 class="level2"><div class="li"> Make the new CD Installer install Ales's binary distribution. (Bounty)</div>
</li>
</ul>
</li>
@@ -297,25 +292,17 @@ Todos for past releases can be seen on the <a href="geda-todos_historical.html"
</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 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>
-</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 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>
</ul>
</li>
</ul>
</div>
-<!-- SECTION "Longer term upgrades desired for specific tools" [4964-8693] -->
-<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>
+<!-- EDIT1325 SECTION "Longer term upgrades desired for specific tools" [4855-8081] -->
+<h2 class="sectionedit1326"><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>
@@ -324,13 +311,11 @@ Todos for past releases can be seen on the <a href="geda-todos_historical.html"
</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" [8694-9260] -->
-<h2><a name="code_cleanup_and_refactoring" id="code_cleanup_and_refactoring">Code cleanup and refactoring</a></h2>
+<!-- EDIT1326 SECTION "Ideas for new tools or gEDA Suite-wide enhancements" [8082-8554] -->
+<h2 class="sectionedit1327"><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>
@@ -339,14 +324,14 @@ Todos for past releases can be seen on the <a href="geda-todos_historical.html"
</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 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 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" [9261-] --></body>
+<!-- EDIT1327 SECTION "Code cleanup and refactoring" [8555-] --></body>
</html>
diff --git a/docs/wiki/geda-todos_historical.html b/docs/wiki/geda-todos_historical.html
index 967cb5b..5f0533f 100644
--- a/docs/wiki/geda-todos_historical.html
+++ b/docs/wiki/geda-todos_historical.html
@@ -11,319 +11,317 @@
</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">
+<h1 class="sectionedit1328"><a name="past_releases" id="past_releases">Past Releases</a></h1>
+<div class="level1">
-<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>
-<li class="level3"><div class="li"><span class="li"><a href="#unstable2" class="toc">1.5.3/1.5.4 (unstable)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#stable2" class="toc">1.6.0 (stable)</a></span></div></li></ul>
-</li></ul>
-</li></ul>
-</div>
</div>
+<!-- EDIT1328 SECTION "Past Releases" [1-29] -->
+<h3 class="sectionedit1329"><a name="stable" id="stable">1.4.2 (stable)</a></h3>
+<div class="level3">
+<p>
+Target release date: <strong>November 2008</strong> <br/>
-<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">
+Actual release date: <strong>December 20th 2008</strong>
+</p>
<p>
- Target release date: <strong>November 2008</strong> <br/>
- Actual release date: <strong>December 20th 2008</strong>
+
+^ Description ^ SF bug ^ GIT Commit (to cherrypick) ^ Developer(s) ^ Status ^
</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>
+<div class="table sectionedit1330"><table class="inline">
+ <tr class="row0">
+ <td class="col0"> Bump libgeda.so micro / minor version </td><td class="col1 centeralign"> n/a </td><td class="col2 centeralign"> n/a </td><td class="col3"> Ales </td><td class="col4 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 class="row1">
+ <td class="col0"> Backport fix for gattrib crash with graphical attribute </td><td class="col1"> <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 class="col2"> <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 class="col3"> Peter B </td><td class="col4"> 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 class="row2">
+ <td class="col0"> Backport fix for crash / ghost connections copying embedded symbols </td><td class="col1"> <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 class="col2"> <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 class="col3"> Peter B </td><td class="col4"> 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 class="row3">
+ <td class="col0"> Backport fix for recomputing bounds of copied embedded symbol </td><td class="col1"> <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 class="col2"> <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 class="col3"> Peter B </td><td class="col4"> 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 class="row4">
+ <td class="col0"> Backport security fix insecure /tmp usage in sch2eaglepos.sh </td><td class="col1 centeralign"> n/a </td><td class="col2"> <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 class="col3"> Peter B </td><td class="col4"> Done </td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT1330 TABLE [274-1934] -->
</div>
-<!-- SECTION "1.4.2 (stable)" [30-1936] -->
-<h3><a name="stable1" id="stable1">1.4.3 (stable)</a></h3>
+<!-- EDIT1329 SECTION "1.4.2 (stable)" [30-1936] -->
+<h3 class="sectionedit1331"><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>
+
+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>
+<div class="table sectionedit1332"><table class="inline">
+ <tr class="row0">
+ <th class="col0 leftalign"> Description </th><th class="col1 leftalign"> SF bug </th><th class="col2 leftalign"> GIT Commit (to cherrypick) </th><th class="col3 leftalign"> Developer(s) </th><th class="col4 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 class="row1">
+ <td class="col0"> Backport â??Enable promotion of attributes when adding a component from guile.â?? </td><td class="col1"> <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 class="col2"> <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 class="col3"> Peter C </td><td class="col4"> <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 class="row2">
+ <td class="col0"> Backport crash fix for rubberbanded nets </td><td class="col1"> <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 class="col2"> <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 class="col3"> Peter C </td><td class="col4"> <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 class="row3">
+ <td class="col0"> Backport crash fix for coincident pins </td><td class="col1"> <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 class="col2"> <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 class="col3"> Peter C </td><td class="col4"> <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 class="row4">
+ <td class="col0"> Backport crash fix invalid attributes </td><td class="col1"> <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 class="col2"> <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="col3 leftalign"> Peter C </td><td class="col4"> <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 class="row5">
+ <td class="col0"> Backport â??Validate calls to scm_c_eval_string(). [2105219]â?? </td><td class="col1"> <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 class="col2"> <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="col3 leftalign"> Peter B </td><td class="col4"> <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 class="row6">
+ <td class="col0"> Backport â??Fix the â??systemcâ?? gnetlist backendâ?? </td><td class="col1 centeralign"> n/a </td><td class="col2"> <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 class="col3"> Peter C </td><td class="col4"> <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 class="row7">
+ <td class="col0"> Fix invalidation of text origin and â??Iâ?? markers </td><td class="col1 centeralign"> n/a </td><td class="col2 centeralign"> n/a </td><td class="col3"> Peter C </td><td class="col4"> <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 class="row8">
+ <td class="col0"> Backport redraw empty preview on configure events </td><td class="col1"> <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 class="col2"> <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 class="col3"> Peter C </td><td class="col4"> <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 class="row9">
+ <td class="col0"> Backport â??gschlas: Fix segfault opening fileâ?? </td><td class="col1 centeralign"> n/a </td><td class="col2"> <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="col3 leftalign"> Peter C </td><td class="col4"> <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>
-
+</table></div>
+<!-- EDIT1332 TABLE [2050-6061] -->
</div>
-<!-- SECTION "1.4.3 (stable)" [1937-6063] -->
-<h3><a name="unstable" id="unstable">1.5.1 (unstable)</a></h3>
+<!-- EDIT1331 SECTION "1.4.3 (stable)" [1937-6063] -->
+<h3 class="sectionedit1333"><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>
+
+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>
+<div class="table sectionedit1334"><table class="inline">
+ <tr class="row0">
+ <th class="col0 leftalign"> Description </th><th class="col1 leftalign"> SF bug </th><th class="col2 leftalign"> Developer(s) </th><th class="col3 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 class="row1">
+ <td class="col0 leftalign"> Selection of filled objects </td><td class="col1"> <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 class="col2"> Ed Hennessy, Peter C </td><td class="col3"> <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 class="row2">
+ <td class="col0 leftalign"> Selection mechanism tweaks </td><td class="col1 centeralign"> n/a </td><td class="col2 leftalign"> Ed Hennessy </td><td class="col3"> <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 class="row3">
+ <td class="col0 leftalign"> Finalize polygon file format </td><td class="col1 centeralign"> n/a </td><td class="col2 leftalign"> Peter C </td><td class="col3"> <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 class="row4">
+ <td class="col0 leftalign"> Update file format docs </td><td class="col1 centeralign"> n/a </td><td class="col2 leftalign"> Peter C </td><td class="col3"> <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 class="row5">
+ <td class="col0 leftalign"> Bump file format version </td><td class="col1 centeralign"> n/a </td><td class="col2 leftalign"> Peter C </td><td class="col3"> <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 class="row6">
+ <td class="col0 leftalign"> Check on BOM2 performance </td><td class="col1 centeralign"> n/a </td><td class="col2 leftalign"> Peter B </td><td class="col3 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 class="row7">
+ <td class="col0"> gschem: Segmentation fault (another one) </td><td class="col1"> <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 class="col2"> Peter B </td><td class="col3"> <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 class="row8">
+ <td class="col0"> CRASH: Crash in multiattrib editor with unusal attribute </td><td class="col1"> <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 class="col2"> Peter C </td><td class="col3"> <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 class="row9">
+ <td class="col0"> gschem segfaults when stretching net segments </td><td class="col1"> <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 class="col2"> Peter C </td><td class="col3"> <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 class="row10">
+ <td class="col0"> Crash removing symbol with coincident pins </td><td class="col1"> <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 class="col2"> Peter C </td><td class="col3"> <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 class="row11">
+ <td class="col0"> Fix breakage with Patrick's re-written f_normalize_filename on mingw32 </td><td class="col1 centeralign"> n/a </td><td class="col2"> Peter C </td><td class="col3"> <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 class="row12">
+ <td class="col0"> Fix the â??systemcâ?? gnetlist backend </td><td class="col1 centeralign"> n/a </td><td class="col2"> Peter C </td><td class="col3"> <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 class="row13">
+ <td class="col0"> Re-add â??spiceâ?? backend to common tests in gnetlist </td><td class="col1 centeralign"> n/a </td><td class="col2"> Peter C </td><td class="col3"> <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 class="row14">
+ <td class="col0"> Add LiquidPCB backend to common tests in gnetlist </td><td class="col1 centeralign"> n/a </td><td class="col2"> Peter C </td><td class="col3"> <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 class="row15">
+ <td class="col0"> Verify gnetlist test-suite passes </td><td class="col1 centeralign"> n/a </td><td class="col2"> Peter C </td><td class="col3"> <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 class="row16">
+ <td class="col0 leftalign"> Renderer improvements (invalidate / expose model) </td><td class="col1 centeralign"> n/a </td><td class="col2"> Peter C </td><td class="col3"> <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>
-
+</table></div>
+<!-- EDIT1334 TABLE [6181-10168] -->
</div>
-<!-- SECTION "1.5.1 (unstable)" [6064-10170] -->
-<h3><a name="unstable1" id="unstable1">1.5.2 (unstable)</a></h3>
+<!-- EDIT1333 SECTION "1.5.1 (unstable)" [6064-10170] -->
+<h3 class="sectionedit1335"><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>
+
+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>
+<div class="table sectionedit1336"><table class="inline">
+ <tr class="row0">
+ <th class="col0 leftalign"> Description </th><th class="col1 leftalign"> SF bug </th><th class="col2 leftalign"> Developer(s) </th><th class="col3 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 class="row1">
+ <td class="col0 leftalign"> Simplified color maps </td><td class="col1 centeralign"> n/a </td><td class="col2 leftalign"> Peter B </td><td class="col3"> <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 class="row2">
+ <td class="col0 leftalign"> Renderer improvements (cairo for static drawing) </td><td class="col1 centeralign"> n/a </td><td class="col2 leftalign"> Peter C </td><td class="col3"> <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 class="row3">
+ <td class="col0"> Renderer improvements (cairo for rubberband drawing) </td><td class="col1 centeralign"> n/a </td><td class="col2 leftalign"> Peter C </td><td class="col3"> <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 class="row4">
+ <td class="col0 leftalign"> Renderer improvements (pango text on screen) </td><td class="col1 leftalign"> </td><td class="col2 leftalign"> Peter C </td><td class="col3"> 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 class="row5">
+ <td class="col0"> Renderer improvements (get text bounds from gschem, not libgeda) </td><td class="col1 leftalign"> </td><td class="col2 leftalign"> Peter B, Peter C </td><td class="col3 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 class="row6">
+ <td class="col0 leftalign"> Embedding pin label colors </td><td class="col1"> <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 class="col2"> Peter C </td><td class="col3"> <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 class="row7">
+ <td class="col0 leftalign"> Selection from inside closed paths </td><td class="col1 centeralign"> n/a </td><td class="col2"> Ed Hennessy, Peter C </td><td class="col3"> <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 class="row8">
+ <td class="col0"> Refactored object hatching (leading to hatched polygons) </td><td class="col1 centeralign"> n/a </td><td class="col2"> Ed Hennessy, Peter C </td><td class="col3"> <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 class="row9">
+ <td class="col0"> gschem: redraw overlapping objects </td><td class="col1"> <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 class="col2"> Peter C </td><td class="col3"> <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 class="row10">
+ <td class="col0"> gschem: Add undo point when editing fill and line styles </td><td class="col1"> <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="col2 leftalign"> Peter B </td><td class="col3"> <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 class="row11">
+ <td class="col0"> Fix redraw of incidentally selected objects when rubberbanding </td><td class="col1"> <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="col2 leftalign"> Peter C </td><td class="col3"> <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 class="row12">
+ <td class="col0"> Fix hit-detection of mirrored arcs (negative sweep) </td><td class="col1 centeralign"> n/a </td><td class="col2 leftalign"> Peter C </td><td class="col3"> <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 class="row13">
+ <td class="col0"> Fix rubberbanding of mirrored arcs (negative sweep) </td><td class="col1 centeralign"> n/a </td><td class="col2 leftalign"> Peter C </td><td class="col3"> <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 class="row14">
+ <td class="col0"> Fix mistakenly changed sizes of circular joint cues </td><td class="col1 centeralign"> n/a </td><td class="col2 leftalign"> Peter C </td><td class="col3"> <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 class="row15">
+ <td class="col0 leftalign"> Ensure gnetlist doesn't netlist buses / bus pins </td><td class="col1 centeralign"> n/a </td><td class="col2 leftalign"> Peter C </td><td class="col3"> <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 class="row16">
+ <td class="col0 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="col1 leftalign"> </td><td class="col2 leftalign"> Peter B </td><td class="col3"> <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>
-
+</table></div>
+<!-- EDIT1336 TABLE [10299-14177] -->
</div>
-<!-- SECTION "1.5.2 (unstable)" [10171-14178] -->
-<h3><a name="unstable2" id="unstable2">1.5.3/1.5.4 (unstable)</a></h3>
+<!-- EDIT1335 SECTION "1.5.2 (unstable)" [10171-14178] -->
+<h3 class="sectionedit1337"><a name="unstable2" id="unstable2">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/>
-
+
+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>
+<div class="table sectionedit1338"><table class="inline">
+ <tr class="row0">
+ <th class="col0 leftalign"> Description </th><th class="col1 leftalign"> SF bug </th><th class="col2 leftalign"> Developer(s) </th><th class="col3 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 class="row1">
+ <td class="col0 leftalign"> Renderer improvements (pango text on screen) </td><td class="col1 leftalign"> </td><td class="col2 leftalign"> Peter C </td><td class="col3"> <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 class="row2">
+ <td class="col0"> Embeded symbol contents different depending on how embedded </td><td class="col1"> <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="col2 leftalign"> Peter B </td><td class="col3"> 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 class="row3">
+ <td class="col0"> <del>gattrib: Fix fileâ??load to do something useful</del> </td><td class="col1 centeralign"> <del>n/a</del> </td><td class="col2"> </td><td class="col3"> 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 class="row4">
+ <td class="col0"> gschem: Preselect current setting when editing fill and line styles </td><td class="col1"> <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="col2 leftalign"> Werner </td><td class="col3"> <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 class="row5">
+ <td class="col0"> Dangerous button focus in â??Save changesâ?? dialog at quit </td><td class="col1"> <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="col2 leftalign"> Peter C </td><td class="col3"> <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 class="row6">
+ <td class="col0"> Fix zooming with (warp-cursor â??disabledâ??) </td><td class="col1"> <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 class="col2"> Werner </td><td class="col3"> <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 class="row7">
+ <td class="col0"> Fix drawing artifact sometimes left after cancelling net mode </td><td class="col1"> <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="col2 leftalign"> Peter C </td><td class="col3"> <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 class="row8">
+ <td class="col0"> Deselecting component doesn't deselect hidden attrib </td><td class="col1"> <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="col2 leftalign"> Peter C </td><td class="col3 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 class="row9">
+ <td class="col0"> Fix gnetlist ordering / test-suite against recent GLib </td><td class="col1"> <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 class="col2"> Peter C </td><td class="col3"> <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 class="row10">
+ <td class="col0 leftalign"> Unified build system </td><td class="col1"> <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="col2 leftalign"> Peter B </td><td class="col3 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 class="row11">
+ <td class="col0"> Get rid of all obsolete auto* macros </td><td class="col1 centeralign"> n/a </td><td class="col2 leftalign"> Peter B </td><td class="col3 leftalign"> Done </td>
</tr>
-</table>
-
+</table></div>
+<!-- EDIT1338 TABLE [14411-17506] -->
</div>
-<!-- SECTION "1.5.3/1.5.4 (unstable)" [14179-17508] -->
-<h3><a name="stable2" id="stable2">1.6.0 (stable)</a></h3>
+<!-- EDIT1337 SECTION "1.5.3/1.5.4 (unstable)" [14179-17508] -->
+<h3 class="sectionedit1339"><a name="stable2" id="stable2">1.6.0 (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>October 4th, 2009</strong>
+
+Target release date: <strong>September 2009 (soon after 1.5.4 is complete) </strong> <br/>
+
+Actual release date: <strong>October 4th, 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>
+<div class="table sectionedit1340"><table class="inline">
+ <tr class="row0">
+ <th class="col0 leftalign"> Description </th><th class="col1 leftalign"> SF bug </th><th class="col2 leftalign"> Developer(s) </th><th class="col3 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 class="row1">
+ <td class="col0 leftalign"> Fix gattrib build with recent GTK+ </td><td class="col1 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="col2 leftalign"> Peter C </td><td class="col3 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="leftalign"> Done </td>
+ <tr class="row2">
+ <td class="col0 leftalign"> Update documentation from wiki </td><td class="col1 leftalign"> </td><td class="col2 leftalign"> Ales </td><td class="col3 leftalign"> Done </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> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=5ca5b9768cf70f3d0f905d784d0896c6b442c34f"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=5ca5b9768cf70f3d0f905d784d0896c6b442c34f"; rel="nofollow"> Done </a> </td>
+ <tr class="row3">
+ <td class="col0 leftalign"> Portability patches for mingw32 landed in some form or other. </td><td class="col1"> </td><td class="col2"> Cesar S, Peter C </td><td class="col3"> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=5ca5b9768cf70f3d0f905d784d0896c6b442c34f"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=5ca5b9768cf70f3d0f905d784d0896c6b442c34f"; rel="nofollow"> Done </a> </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 class="row4">
+ <td class="col0"> Cure all: â??warning: format not a string literal and no format argumentsâ?? compiling with recent GCC versions </td><td class="col1"> </td><td class="col2"> </td><td class="col3"> Fixed </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 class="row5">
+ <td class="col0"> gattrib: Remove all deliberately-non-functioning menu options / buttons </td><td class="col1 centeralign"> n/a </td><td class="col2"> Peter C </td><td class="col3"> <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> 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 class="row6">
+ <td class="col0"> Fix symbols using explicit lines for overbars </td><td class="col1 centeralign"> n/a </td><td class="col2"> Bert T, Werner </td><td class="col3"> <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 class="row7">
+ <td class="col0"> utils: Teach gsch2pcb to detect and avoid the common â??footprint saved as PCB fileâ?? mistake </td><td class="col1 centeralign"> n/a </td><td class="col2"> Peter B </td><td class="col3"> <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 class="row8">
+ <td class="col0"> gschem: Fix broken net consolidation for certain scenarios </td><td class="col1 centeralign"> n/a </td><td class="col2 leftalign"> Peter C </td><td class="col3"> <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>
-
+</table></div>
+<!-- EDIT1340 TABLE [17655-19458] -->
</div>
-<!-- SECTION "1.6.0 (stable)" [17509-] --></body>
+<!-- EDIT1339 SECTION "1.6.0 (stable)" [17509-] --></body>
</html>
diff --git a/docs/wiki/geda-tools.html b/docs/wiki/geda-tools.html
new file mode 100644
index 0000000..cc72b4a
--- /dev/null
+++ b/docs/wiki/geda-tools.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 class="sectionedit1420"><a name="geda_tools" id="geda_tools">gEDA Tools</a></h1>
+<div class="level1">
+
+<p>
+
+Under construction
+
+</p>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-tragesym_readme.html b/docs/wiki/geda-tragesym_readme.html
index 1d8087c..3877d22 100644
--- a/docs/wiki/geda-tragesym_readme.html
+++ b/docs/wiki/geda-tragesym_readme.html
@@ -12,9 +12,7 @@
<body>
-
-
-<h1><a name="tragesym_symbol_generator_readme" id="tragesym_symbol_generator_readme">tragesym (symbol generator) README</a></h1>
+<h1 class="sectionedit1341"><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.
@@ -38,8 +36,7 @@ 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>
+Send it to Werner Hoch (werner.ho@xxxxxx)</pre>
</div>
</body>
diff --git a/docs/wiki/geda-tragesym_tutorial.fr.html b/docs/wiki/geda-tragesym_tutorial.fr.html
index d5dfb24..996f7d7 100644
--- a/docs/wiki/geda-tragesym_tutorial.fr.html
+++ b/docs/wiki/geda-tragesym_tutorial.fr.html
@@ -11,39 +11,18 @@
</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>
+<h1 class="sectionedit1342"><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).
+
+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>
+<!-- EDIT1342 SECTION "Créer des symboles gschem rapidement et facilement en utilisant tragesym et un tableur" [1-532] -->
+<h2 class="sectionedit1343"><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>
@@ -63,21 +42,26 @@
</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>
+<!-- EDIT1343 SECTION "�tapes nécessaires" [533-1094] -->
+<h2 class="sectionedit1344"><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).
+
+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>
+<!-- EDIT1344 SECTION "Ã?tape 1: Ouvrir un fichier de formulaire tragesym" [1095-1958] -->
+<h2 class="sectionedit1345"><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·:
+
+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>
@@ -85,16 +69,17 @@
</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.
+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>
+<!-- EDIT1345 SECTION "�tape 2: Télécharger le fichier technique du composant et trouver la liste des broches" [1959-2906] -->
+<h2 class="sectionedit1346"><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.
+
+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>
@@ -106,7 +91,7 @@ Dans la feuille de calcul, la liste des broches peut être seulement présente d
</p>
<p>
-Lâ??image ci-dessus illustre les étapes·:
+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>
@@ -119,7 +104,7 @@ Lâ??image ci-dessus illustre les étapes·:
</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 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>
@@ -130,12 +115,13 @@ Lâ??image ci-dessus illustre les étapes·:
</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>
+<!-- EDIT1346 SECTION "�tape 3: Copier la liste des broches dans un éditeur et la préparer" [2907-4587] -->
+<h2 class="sectionedit1347"><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.
+
+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>
@@ -143,7 +129,8 @@ Lâ??image ci-dessus illustre les étapes·:
</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:
+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>
@@ -151,21 +138,22 @@ Remplissez les colonens de type, de style et de position aux valeurs les plus ha
</p>
<p>
-Selon ce tableau, nous changeons les éléments suivants (voir le résultat ci-dessus):
+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 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 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 «·\\·».
+
+<strong>Note:</strong> Si une de vos étiquettes contient un backslash «·\·», vous devez le remplacer par sa séquence d'échapement «·\\·».
</p>
<p>
@@ -181,21 +169,23 @@ Avant de configurer les attributs et les options aux valeurs appropriées.
</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>
+<!-- EDIT1347 SECTION "�tape 4: Insérer toutes les données manquantes dans la feuille de calcul" [4588-6061] -->
+<h2 class="sectionedit1348"><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.
+
+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>
+<!-- EDIT1348 SECTION "�tape 5: Exporter la feuille de calcul dans un fichier texte avec séparation par tabulation" [6062-6409] -->
+<h2 class="sectionedit1349"><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:
+
+Utilisez un shell et exécutez tragesym:
</p>
<p>
@@ -203,24 +193,25 @@ Avant de configurer les attributs et les options aux valeurs appropriées.
</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é.
+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>
+<!-- EDIT1349 SECTION "�tape 6: Lancer tragesym et créer le symbole" [6410-6771] -->
+<h2 class="sectionedit1350"><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
+
+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>
+<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.
+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>
@@ -228,31 +219,35 @@ En validant le texte caché («·en·», Edit→Show/Hide Inv Text), vous pou
</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.
+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>
+<!-- EDIT1350 SECTION "�tape 7: Contrôler le résultat avec gschem et peaufiner le symbole" [6772-7503] -->
+<h2 class="sectionedit1351"><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.).
+
+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>
+<!-- EDIT1351 SECTION "Conclusion" [7504-7673] -->
+<h2 class="sectionedit1352"><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)
+
+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>
+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>
+<!-- EDIT1352 SECTION "Crédits" [7674-] --></body>
</html>
diff --git a/docs/wiki/geda-tragesym_tutorial.html b/docs/wiki/geda-tragesym_tutorial.html
index c8563b8..5432667 100644
--- a/docs/wiki/geda-tragesym_tutorial.html
+++ b/docs/wiki/geda-tragesym_tutorial.html
@@ -11,39 +11,18 @@
</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>
+<h1 class="sectionedit1353"><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).
+
+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>
+<!-- EDIT1353 SECTION "Creating gschem symbols quickly and easily using tragesym and a spreadsheet programm" [1-450] -->
+<h2 class="sectionedit1354"><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>
@@ -63,21 +42,24 @@
</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>
+<!-- EDIT1354 SECTION "Required Steps" [451-873] -->
+<h2 class="sectionedit1355"><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).
+
+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>
+<!-- EDIT1355 SECTION "Step1: Open a tragesym template file" [874-1673] -->
+<h2 class="sectionedit1356"><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:
+
+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>
@@ -89,8 +71,8 @@ Inside the datasheet the pin list may only be in the drawing of the pin configur
</p>
</div>
-<!-- SECTION "Step2: Download the part data sheet and find the pin list" [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>
+<!-- EDIT1356 SECTION "Step2: Download the part data sheet and find the pin list" [1674-2447] -->
+<h2 class="sectionedit1357"><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>
@@ -106,7 +88,7 @@ Select the pin list and copy it into a text editor. This intermediate step is re
</p>
<p>
-The pictures above illustrate the steps:
+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>
@@ -119,7 +101,7 @@ The pictures above illustrate the steps:
</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 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>
@@ -130,12 +112,13 @@ The pictures above illustrate the steps:
</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>
+<!-- EDIT1357 SECTION "Step3: Copy the pin list into an editor and prepare it" [2448-3823] -->
+<h2 class="sectionedit1358"><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.
+
+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>
@@ -155,7 +138,7 @@ Now you want to change some fo the values. Take a look at the pin description ta
</p>
<p>
-Regarding to that table we change the following things (see result below):
+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>
@@ -169,7 +152,8 @@ Regarding to that table we change the following things (see result below):
</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 â??\\â??.
+
+<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>
@@ -185,17 +169,18 @@ Before going on set the attributes and the options to appropriate values.
</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>
+<!-- EDIT1358 SECTION "Step4: Insert all missing data into the spreadsheet" [3824-5032] -->
+<h2 class="sectionedit1359"><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.
+
+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>
+<!-- EDIT1359 SECTION "Step5: Export the spreadsheet into a tab seperated text file" [5033-5297] -->
+<h2 class="sectionedit1360"><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>
@@ -207,24 +192,25 @@ Use a shell and execute tragesym:
</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.
+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>
+<!-- EDIT1360 SECTION "Step6: execute tragesym and create the symbol" [5298-5618] -->
+<h2 class="sectionedit1361"><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
+
+Now open the generated symbol with gschem and check the result
</p>
<p>
-<code>werner@werner-amd64:~/Desktop/tragesym_tutorial> gschem pca555.sch</code>
+<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.
+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>
@@ -236,8 +222,8 @@ Now we have a complete symbol. You can copy the symbol to your local symbol libr
</p>
</div>
-<!-- SECTION "Step7: check the result with gschem and do some artwork" [5619-6260] -->
-<h2><a name="conclusion" id="conclusion">Conclusion</a></h2>
+<!-- EDIT1361 SECTION "Step7: check the result with gschem and do some artwork" [5619-6260] -->
+<h2 class="sectionedit1362"><a name="conclusion" id="conclusion">Conclusion</a></h2>
<div class="level2">
<p>
@@ -245,14 +231,16 @@ This was a simple example with a small pincount, but this method really pays off
</p>
</div>
-<!-- SECTION "Conclusion" [6261-6425] -->
-<h2><a name="credits" id="credits">Credits</a></h2>
+<!-- EDIT1362 SECTION "Conclusion" [6261-6425] -->
+<h2 class="sectionedit1363"><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>
+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>
+<!-- EDIT1363 SECTION "Credits" [6426-] --></body>
</html>
diff --git a/docs/wiki/geda-transistor_guide.html b/docs/wiki/geda-transistor_guide.html
index 03e2480..ddbdaa0 100644
--- a/docs/wiki/geda-transistor_guide.html
+++ b/docs/wiki/geda-transistor_guide.html
@@ -11,56 +11,45 @@
</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>
+<h1 class="sectionedit1364"><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.
+
+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>
+<!-- EDIT1364 SECTION "gschem Symbol and PCB Element Transistor Guide" [1-531] -->
+<h2 class="sectionedit1365"><a name="gschem_symbols" id="gschem_symbols">gschem symbols</a></h2>
<div class="level2">
<p>
- There are a couple of ways to consider:
+
+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 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.
+
+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>
+<!-- EDIT1365 SECTION "gschem symbols" [532-2551] -->
+<h2 class="sectionedit1366"><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.
+
+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>
@@ -68,28 +57,31 @@ However, most TO packages do conform to a standard pin numbering convention and
</p>
<p>
-Hereâ??s a description of what seems to be the most common transistor outline configurations:
+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 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 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 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>
+<!-- EDIT1366 SECTION "PCB Elements" [2552-6414] -->
+<h2 class="sectionedit1367"><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):
+
+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>
@@ -103,13 +95,13 @@ Hereâ??s a description of what seems to be the most common transistor outline co
</ol>
</div>
-<!-- SECTION "General Procedure" [6415-7541] -->
-<h2><a name="special_cases" id="special_cases">Special Cases</a></h2>
+<!-- EDIT1367 SECTION "General Procedure" [6415-7541] -->
+<h2 class="sectionedit1368"><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 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>
@@ -119,9 +111,10 @@ Hereâ??s a description of what seems to be the most common transistor outline co
<hr />
<p>
-tutorial by Bill Wilson (bill–at–gkrellm.net)
+tutorial by Bill Wilson (billâ??atâ??gkrellm.net)
+
</p>
</div>
-<!-- SECTION "Special Cases" [7542-] --></body>
+<!-- EDIT1368 SECTION "Special Cases" [7542-] --></body>
</html>
diff --git a/docs/wiki/geda-ubuntu.html b/docs/wiki/geda-ubuntu.html
index f2fc7dd..dd0b1a2 100644
--- a/docs/wiki/geda-ubuntu.html
+++ b/docs/wiki/geda-ubuntu.html
@@ -13,23 +13,28 @@
<p>
- <strong>Ubuntu Install Notes</strong>
+
+<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>.
+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.
+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.
+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)
+<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
index 0a2eead..6c664a9 100644
--- a/docs/wiki/geda-usage.fr.html
+++ b/docs/wiki/geda-usage.fr.html
@@ -11,29 +11,12 @@
</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>
+<h1 class="sectionedit1369"><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.
+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>
@@ -41,12 +24,12 @@ Allez aussi voir les autres <a href="http://geda.seul.org/docs"; class="urlextern
</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!
+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>
+<!-- EDIT1369 SECTION "Quelle est la meilleure manière d'apprendre à utiliser gEDA?" [1-690] -->
+<h2 class="sectionedit1370"><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>
@@ -67,7 +50,7 @@ Mis en mots, le flux de conception pour un PCB simple se fait de la manière sui
</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 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>
@@ -78,7 +61,8 @@ Mis en mots, le flux de conception pour un PCB simple se fait de la manière sui
</ol>
<p>
- Si vous faites des changements ou des ajouts à votre schéma ou des attributs, mettez votre fichier PCB comme ceci:
+
+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>
@@ -94,33 +78,34 @@ Mis en mots, le flux de conception pour un PCB simple se fait de la manière sui
</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é.
+
+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>
+<!-- EDIT1370 SECTION "Ã? quoi ressemble de le flux de conception de gEDA?" [691-2693] -->
+<h2 class="sectionedit1371"><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!
+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 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 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 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>
+<!-- EDIT1371 SECTION "Quelles sont les limitations pour les outils gEDA?" [2694-4952] -->
+<h2 class="sectionedit1372"><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>
@@ -131,36 +116,38 @@ Une conception typique de PCB nécessite les fichiers de config suivants dans vo
</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 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.
+
+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>
+<!-- EDIT1372 SECTION "Quels fichiers de configuration locaux sont utilisés pour un projet?" [4953-6122] -->
+<h2 class="sectionedit1373"><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 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 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 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:
+
+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>
+<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>
@@ -176,7 +163,7 @@ Les diverses applications gEDA/gaf (gschem, gattrib, gnetlist, etc.) utilisent u
</li>
</ul>
</li>
-<li class="level1"><div class="li"> Dans le répertoire <strong><code>${HOME}</code></strong> de lâ??utilisateur:</div>
+<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>
@@ -191,11 +178,12 @@ Les diverses applications gEDA/gaf (gschem, gattrib, gnetlist, etc.) utilisent u
</ul>
<p>
- Les définitions de couleurs gschem-darkbg ou gschem-lightbg sont aussi chargées par le system-gschemrc.
+
+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:
+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>
@@ -213,22 +201,24 @@ Finalement, notez que les applications gEDA/gaf recherchent jusquâ??Ã six fichi
</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.
+
+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>
+<!-- EDIT1373 SECTION "Quels sont les noms et les emplacements des fichiers RC utilisés avec les applications gEDA/gaf?" [6123-10078] -->
+<h2 class="sectionedit1374"><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.
+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!
+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>
+<!-- EDIT1374 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
index 1ff47dc..95316d2 100644
--- a/docs/wiki/geda-usage.html
+++ b/docs/wiki/geda-usage.html
@@ -11,24 +11,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>
+<h1 class="sectionedit1375"><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>
@@ -36,7 +20,7 @@ The first thing to do is to read and understand Bill Wilsonâ??s excellent <a hre
</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.
+Also be sure to check out the other <a href="http://geda.seul.org/wiki/geda:documentation"; class="urlextern" title="http://geda.seul.org/wiki/geda:documentation"; rel="nofollow">gEDA documentation</a> available on this website.
</p>
<p>
@@ -44,8 +28,8 @@ However, the best way to learn the gEDA Suite is to download it and try it out y
</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>
+<!-- EDIT1375 SECTION "What's the best way to learn to use gEDA?" [1-646] -->
+<h1 class="sectionedit1376"><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>
@@ -77,7 +61,8 @@ In words, the design flow for a simple PCB proceeds as follows:
</ol>
<p>
- If you make changes, or add to your schematic or attributes while in layout, update your board file like this:
+
+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>
@@ -93,12 +78,13 @@ In words, the design flow for a simple PCB proceeds as follows:
</ol>
<p>
- Usually, users invoke the individual tools from the command line. A project manager (â??gedaâ??) exists, but needs improvement.
+
+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>
+<!-- EDIT1376 SECTION "What does the design flow in gEDA look like?" [647-2322] -->
+<h1 class="sectionedit1377"><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>
@@ -118,8 +104,8 @@ The most important thing to keep in mind about gEDAâ??s limitations is this: GED
</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>
+<!-- EDIT1377 SECTION "What limitations exist for the gEDA tools?" [2323-4138] -->
+<h1 class="sectionedit1378"><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>
@@ -135,12 +121,13 @@ A typical PCB design requires the following config files in your local directory
</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.
+
+Further detailed information about each configuration file is provided in the <a href="http://geda.seul.org/wiki/geda:documentation"; class="urlextern" title="http://geda.seul.org/wiki/geda:documentation"; 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>
+<!-- EDIT1378 SECTION "What local configuration files are used for a project?" [4139-5103] -->
+<h1 class="sectionedit1379"><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>
@@ -156,7 +143,8 @@ The various gEDA/gaf applications (gschem, gattrib, gnetlist, etc.) use a set of
</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:
+
+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>
@@ -190,7 +178,8 @@ The various gEDA/gaf applications (gschem, gattrib, gnetlist, etc.) use a set of
</ul>
<p>
- Also loaded by the system-gschemrc is the gschem-darkbg or gschem-lightbg color definitions.
+
+Also loaded by the system-gschemrc is the gschem-darkbg or gschem-lightbg color definitions.
</p>
<p>
@@ -212,12 +201,13 @@ Finally, note that gEDA/gaf applications will look for up to six configuration f
</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.
+
+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>
+<!-- EDIT1379 SECTION "What are the names and locations of the RC files used with gEDA/gaf applications?" [5104-8482] -->
+<h1 class="sectionedit1380"><a name="what_about_a_project_manager" id="what_about_a_project_manager">What about a project manager?</a></h1>
<div class="level1">
<p>
@@ -229,8 +219,8 @@ Unfortunately, development of â??gedaâ?? has not kept up with the rest of gEDA/g
</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>
+<!-- EDIT1380 SECTION "What about a project manager?" [8483-9518] -->
+<h1 class="sectionedit1381"><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>
@@ -238,25 +228,26 @@ We have a recurrent debate about <acronym title="Extensible Markup Language">XML
</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:
+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 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 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 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 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 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 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>
+<!-- EDIT1381 SECTION "Can we change gEDA to use an XML file format?" [9519-] --></body>
</html>
diff --git a/docs/wiki/geda-vams_netlister_readme.html b/docs/wiki/geda-vams_netlister_readme.html
index 8505d6c..f8d6caa 100644
--- a/docs/wiki/geda-vams_netlister_readme.html
+++ b/docs/wiki/geda-vams_netlister_readme.html
@@ -11,28 +11,13 @@
</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>
+<h1 class="sectionedit1382"><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>
+<!-- EDIT1382 SECTION "VAMS netlister README" [1-36] -->
+<h2 class="sectionedit1383"><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
@@ -646,12 +631,11 @@ CONTENT:
}
- (6) compile your changed c-code newly
-</pre>
+ (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>
+<!-- EDIT1383 SECTION "VAMS netlister" [37-20220] -->
+<h2 class="sectionedit1384"><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
@@ -664,12 +648,11 @@ BEGIN
{; <set-generic=> <generic-value>})]
PORT MAP ( <pin-name> => <subnet-name>{; <.. => ..>});}
-END ARCHITECTURE <architecture-identifier>;
-</pre>
+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>
+<!-- EDIT1384 SECTION "VAMS netlister syntax architecture" [20221-20667] -->
+<h2 class="sectionedit1385"><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>};
@@ -679,9 +662,8 @@ ENTITY <entity-identifier> IS
{;<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>
+END ENTITY;</pre>
</div>
-<!-- SECTION "VAMS netlister syntax entity" [20668-] --></body>
+<!-- EDIT1385 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
index b55b04b..ecfbd19 100644
--- a/docs/wiki/geda-verilog_netlister_readme.html
+++ b/docs/wiki/geda-verilog_netlister_readme.html
@@ -12,9 +12,7 @@
<body>
-
-
-<h1><a name="verilog_netlister_readme" id="verilog_netlister_readme">Verilog netlister README</a></h1>
+<h1 class="sectionedit1386"><a name="verilog_netlister_readme" id="verilog_netlister_readme">Verilog netlister README</a></h1>
<div class="level1">
<pre class="code">Verilog netlister readme.
@@ -433,8 +431,7 @@ The mechanics:
You will have to manually trace back to find the error.
- Mike Jarabek
-</pre>
+ Mike Jarabek</pre>
</div>
</body>
diff --git a/docs/wiki/geda-version_control_migration.html b/docs/wiki/geda-version_control_migration.html
index 2d96277..2a4c271 100644
--- a/docs/wiki/geda-version_control_migration.html
+++ b/docs/wiki/geda-version_control_migration.html
@@ -11,46 +11,34 @@
</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>
+<h1 class="sectionedit1387"><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>
+<!-- EDIT1387 SECTION "Version Control Migration" [1-41] -->
+<h2 class="sectionedit1388"><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.
+
+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:
+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 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 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 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>
@@ -58,21 +46,23 @@ Unfortunately, <acronym title="Concurrent Versions System">CVS</acronym> has a n
</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 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>
+<!-- EDIT1388 SECTION "Status Quo" [42-1144] -->
+<h2 class="sectionedit1389"><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.
+
+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:
+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>
@@ -92,11 +82,13 @@ The following features would be deemed desirable in a version control system:
</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.
+
+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:
+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>
@@ -106,5 +98,5 @@ A number of factors militate in favour of using git:
</ul>
</div>
-<!-- SECTION "What We Need" [1145-] --></body>
+<!-- EDIT1389 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
index 90f1291..d0dcf03 100644
--- a/docs/wiki/geda-vhdl_netlister_readme.html
+++ b/docs/wiki/geda-vhdl_netlister_readme.html
@@ -12,9 +12,7 @@
<body>
-
-
-<h1><a name="vhdl_netlister_readme" id="vhdl_netlister_readme">VHDL netlister README</a></h1>
+<h1 class="sectionedit1390"><a name="vhdl_netlister_readme" id="vhdl_netlister_readme">VHDL netlister README</a></h1>
<div class="level1">
<pre class="code">The VHDL backend
@@ -33,8 +31,7 @@ A few things you have to care about:
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>
+ first!</pre>
</div>
</body>
diff --git a/docs/wiki/geda-wcalc_mp.html b/docs/wiki/geda-wcalc_mp.html
index 5e24064..3907f9d 100644
--- a/docs/wiki/geda-wcalc_mp.html
+++ b/docs/wiki/geda-wcalc_mp.html
@@ -12,9 +12,7 @@
<body>
-
-
-<h1><a name="wcalc_man-page" id="wcalc_man-page">Wcalc man-page</a></h1>
+<h1 class="sectionedit1391"><a name="wcalc_man-page" id="wcalc_man-page">Wcalc man-page</a></h1>
<div class="level1">
<pre class="code">WCALC(1) WCALC(1)
diff --git a/docs/wiki/geda-wcalc_readme.html b/docs/wiki/geda-wcalc_readme.html
index 548b9f9..b924338 100644
--- a/docs/wiki/geda-wcalc_readme.html
+++ b/docs/wiki/geda-wcalc_readme.html
@@ -12,9 +12,7 @@
<body>
-
-
-<h1><a name="wcalc_readme" id="wcalc_readme">Wcalc README</a></h1>
+<h1 class="sectionedit1392"><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 $
diff --git a/docs/wiki/geda-wcalc_stdio_mp.html b/docs/wiki/geda-wcalc_stdio_mp.html
index 43fb47e..9a0502d 100644
--- a/docs/wiki/geda-wcalc_stdio_mp.html
+++ b/docs/wiki/geda-wcalc_stdio_mp.html
@@ -12,9 +12,7 @@
<body>
-
-
-<h1><a name="stdio_wcalc_man-page" id="stdio_wcalc_man-page">stdio Wcalc man-page</a></h1>
+<h1 class="sectionedit1393"><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)
diff --git a/docs/wiki/geda-wip-clipboard.html b/docs/wiki/geda-wip-clipboard.html
index 9881d11..28a9c8a 100644
--- a/docs/wiki/geda-wip-clipboard.html
+++ b/docs/wiki/geda-wip-clipboard.html
@@ -11,47 +11,28 @@
</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>
+<h1 class="sectionedit4"><a name="clipboard_support" id="clipboard_support">Clipboard Support</a></h1>
<div class="level1">
<p>
- Targetted for release in gEDA 1.8.0.
+
+Targetted for release in gEDA 1.8.0.
</p>
</div>
-<!-- SECTION "Clipboard Support" [1-71] -->
-<h3><a name="introduction" id="introduction">Introduction</a></h3>
+<!-- EDIT4 SECTION "Clipboard Support" [1-71] -->
+<h3 class="sectionedit5"><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.
+
+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:
+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>
@@ -63,26 +44,30 @@ It would be nice to be able to:
</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."
+
+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>
+<!-- EDIT5 SECTION "Introduction" [72-930] -->
+<h3 class="sectionedit6"><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:
+
+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 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.
+
+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>
@@ -90,34 +75,38 @@ Due to the primarily non-textual nature of schematic or symbol data, gschem shou
</p>
</div>
-<!-- SECTION "The X clipboard" [931-1845] -->
-<h3><a name="the_windows_clipboard" id="the_windows_clipboard">The Windows clipboard</a></h3>
+<!-- EDIT6 SECTION "The X clipboard" [931-1845] -->
+<h3 class="sectionedit7"><a name="the_windows_clipboard" id="the_windows_clipboard">The Windows clipboard</a></h3>
<div class="level3">
<p>
- Research needed.
+
+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>
+<!-- EDIT7 SECTION "The Windows clipboard" [1846-1896] -->
+<h3 class="sectionedit8"><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.
+
+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>
+<!-- EDIT8 SECTION "GTK clipboard API" [1897-2290] -->
+<h3 class="sectionedit9"><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.
+
+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â??:
+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>
@@ -127,7 +116,9 @@ When a set of selected items is â??copiedâ??:
</ol>
<p>
- When a set of selected items is â??cutâ??:
+
+When a set of selected items is â??cutâ??:
+
</p>
<ol>
<li class="level1"><div class="li"> The copying procedure is followed.</div>
@@ -137,16 +128,18 @@ When a set of selected items is â??copiedâ??:
</ol>
<p>
- When a set of selected items is â??pastedâ??:
+
+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 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>
+<!-- EDIT9 SECTION "Buffers in gschem" [2291-2910] -->
+<h3 class="sectionedit10"><a name="clipboard_data_types" id="clipboard_data_types">Clipboard data types</a></h3>
<div class="level3">
</div>
@@ -155,11 +148,12 @@ When a set of selected items is â??copiedâ??:
<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>.
+
+<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.
+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>
@@ -171,9 +165,10 @@ To simplify the implementation, the first schematic data buffer is currently use
</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.
+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>
+<!-- EDIT10 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
index 3669f04..c531971 100644
--- a/docs/wiki/geda-xml_file_formats.html
+++ b/docs/wiki/geda-xml_file_formats.html
@@ -12,9 +12,7 @@
<body>
-
-
-<h1><a name="xml_file_formats" id="xml_file_formats">XML File Formats</a></h1>
+<h1 class="sectionedit1394"><a name="xml_file_formats" id="xml_file_formats">XML File Formats</a></h1>
<div class="level1">
<p>
@@ -30,7 +28,8 @@ Another main goal is to start addressing the Symbol Library Hacker task discusse
</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.
+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>
@@ -50,11 +49,13 @@ An initial git repository is at <a href="http://github.com/oblivian/geda-xml/tre
</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.
+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.
+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>
diff --git a/docs/wiki/gerbv-projects.html b/docs/wiki/gerbv-projects.html
index 71c9684..7c75431 100644
--- a/docs/wiki/gerbv-projects.html
+++ b/docs/wiki/gerbv-projects.html
@@ -12,9 +12,7 @@
<body>
-
-
-<h3><a name="gerbv" id="gerbv">Gerbv</a></h3>
+<h3 class="sectionedit1492"><a name="gerbv" id="gerbv">Gerbv</a></h3>
<div class="level3">
</div>
@@ -23,7 +21,8 @@
<div class="level5">
<p>
- Gerbv is gEDAâ??s Gerber file viewer. However, it has the potential to become more than a viewer – it can become a complete CAM tool, allowing (simple) editing of Gerbers, like moving or deleting tracks, changing drill hole diameters, changing pad or ring diameters, and so on.
+
+Gerbv is gEDA's Gerber file viewer. However, it has the potential to become more than a viewer â?? it can become a complete CAM tool, allowing (simple) editing of Gerbers, like moving or deleting tracks, changing drill hole diameters, changing pad or ring diameters, and so on.
</p>
<p>
@@ -36,7 +35,14 @@ Difficulty = 4
<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.
+
+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>
@@ -49,7 +55,8 @@ Difficulty: 5
<div class="level5">
<p>
- This project involves writing code which will allow gerbv to autoidentify footprints via some type of pattern matching (e.g. 2D correlation with known footprints). Then, gerbv would store the (X, Y) coordinates of each identified footprintâ??s centroid. The idea is to produce a pick-place file for automated board stuffing using only the information contained in a set of Gerber files. This would make a good project for somebody with some AI and/or machine vision background.
+
+This project involves writing code which will allow gerbv to autoidentify footprints via some type of pattern matching (e.g. 2D correlation with known footprints). Then, gerbv would store the (X, Y) coordinates of each identified footprint's centroid. The idea is to produce a pick-place file for automated board stuffing using only the information contained in a set of Gerber files. This would make a good project for somebody with some AI and/or machine vision background.
</p>
<p>
@@ -58,15 +65,16 @@ Difficulty = 5
</div>
-<h5><a name="gerber_to_.pcb_file_exporter" id="gerber_to_.pcb_file_exporter">Gerber to .pcb file exporter</a></h5>
+<h5><a name="gerber_to_pcb_file_exporter" id="gerber_to_pcb_file_exporter">Gerber to .pcb file exporter</a></h5>
<div class="level5">
<p>
- In this project, the student would implement a feature in which gerbv would read in a gerber, and then export a file which could be read by gEDA/PCB. The .pcb file generated wouldnâ??t need to be much more than the individual graphical elements held in the Gerber since a Gerber file doesnâ??t have the concept of e.g. footprints or text on the silkscreen layer. However, the ability to create .pcb files would be very useful, since the one could use the full power of PCB when editing legacy Gerbers.
+
+In this project, the student would implement a feature in which gerbv would read in a gerber, and then export a file which could be read by gEDA/PCB. The .pcb file generated wouldn't need to be much more than the individual graphical elements held in the Gerber since a Gerber file doesn't have the concept of e.g. footprints or text on the silkscreen layer. However, the ability to create .pcb files would be very useful, since the one could use the full power of PCB when editing legacy Gerbers.
</p>
<p>
-Difficulty = 3
+Difficulty = 3
</p>
</div>
diff --git a/docs/wiki/glue-projects.html b/docs/wiki/glue-projects.html
index ed144ed..fc00763 100644
--- a/docs/wiki/glue-projects.html
+++ b/docs/wiki/glue-projects.html
@@ -12,13 +12,12 @@
<body>
-
-
-<h3><a name="general_glue_and_related_gaf_projects" id="general_glue_and_related_gaf_projects">General, "glue" and related gaf projects</a></h3>
+<h3 class="sectionedit1493"><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>
- These projects make the others work together as a system.
+
+These projects make the others work together as a system.
</p>
</div>
@@ -27,7 +26,8 @@
<div class="level5">
<p>
- 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.
+
+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>
<p>
@@ -40,7 +40,8 @@ Difficulty: 2
<div class="level5">
<p>
- This project encompasses the functionality of the entire gEDA PCB design flow. You would develop a test framework for as much of these tools as possible. This likely means creating a large regression test suite. Some examples are sets of layouts (using PCB) that just barely pass and just barely fail each of the different DRC checks, generate BOMâ??s, x-y files, generate gerbers and maybe use gerbv to do a graphical xor against a â??goldenâ?? file. For gnetlist, reference netlists that have been placed into some canonical form should be generated from gschem schematics (.sch files).
+
+This project encompasses the functionality of the entire gEDA PCB design flow. You would develop a test framework for as much of these tools as possible. This likely means creating a large regression test suite. Some examples are sets of layouts (using PCB) that just barely pass and just barely fail each of the different DRC checks, generate BOM's, x-y files, generate gerbers and maybe use gerbv to do a graphical xor against a â??goldenâ?? file. For gnetlist, reference netlists that have been placed into some canonical form should be generated from gschem schematics (.sch files).
</p>
<p>
@@ -57,11 +58,13 @@ Difficulty = 3
<div class="level5">
<p>
- Ngspice and Gnucap are the gEDA Projectâ??s analog circuit simulators. They are both command-line tools, meaning that you type commands into a shell-like program at a prompt. However, some popular commercial simulators support easy simulation and analysis directly from within a schematic capture <acronym title="Graphical User Interface">GUI</acronym>. This method of working is particularly well suited to newbies.
+
+Ngspice and Gnucap are the gEDA Project's analog circuit simulators. They are both command-line tools, meaning that you type commands into a shell-like program at a prompt. However, some popular commercial simulators support easy simulation and analysis directly from within a schematic capture <acronym title="Graphical User Interface">GUI</acronym>. This method of working is particularly well suited to newbies.
</p>
<p>
-A new user would like to do the following things inside gschem:
+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>
@@ -73,11 +76,12 @@ 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="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>).
+
+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>
-This project involves tightening the link between gschem and the back-end simulation programs. This might be done using some type of IPC, such as DBUS. Indeed, a preliminary DBUS implementation for gschem ↔ PCB already exists; the student might leverage the DBUS work for this project.
+This project involves tightening the link between gschem and the back-end simulation programs. This might be done using some type of IPC, such as DBUS. Indeed, a preliminary DBUS implementation for gschem â?? PCB already exists; the student might leverage the DBUS work for this project.
</p>
<p>
@@ -90,7 +94,8 @@ Difficulty = 3
<div class="level5">
<p>
- In this project, you would create a parts manager that takes a graphical symbol and a physical footprint, and marries the two to produce a heavy part. In addition, this tool should be able to support multiple backend flows. By this I mean that the parts manager should be able to also indicate how the symbol should be netlisted for spice, gnucap, or other backends. If possible it would be nice to integrate this into gschem in a way that allowed symbols to be placed and the footprint attribute to come up with a list of choices.
+
+In this project, you would create a parts manager that takes a graphical symbol and a physical footprint, and marries the two to produce a heavy part. In addition, this tool should be able to support multiple backend flows. By this I mean that the parts manager should be able to also indicate how the symbol should be netlisted for spice, gnucap, or other backends. If possible it would be nice to integrate this into gschem in a way that allowed symbols to be placed and the footprint attribute to come up with a list of choices.
</p>
<p>
@@ -107,7 +112,8 @@ Difficulty = 4
<div class="level5">
<p>
- The goal of this project is to create a scalable, professional-grade netlister. The project might involve re-writing gnetlist to enable hierarchical designs, or might involve upgrading â??gnetmanâ?? to incorporate scripted back-ends. The upgrade would be done with an eye towards scalability. Ideally, highly capable and efficient internal data structures and methods for accessing the netlist database should be used. Then a scheme/guile <acronym title="Application Programming Interface">API</acronym> provided for an external script engine. (It may be beneficial to use swig to allow easy interfacing to multiple scripting languages.) The idea is to produce a netlister capable of handling large, hierarchical designs while still allowing users to write their own netlisters for their favorite netlist format (as gnetlist does now).
+
+The goal of this project is to create a scalable, professional-grade netlister. The project might involve re-writing gnetlist to enable hierarchical designs, or might involve upgrading â??gnetmanâ?? to incorporate scripted back-ends. The upgrade would be done with an eye towards scalability. Ideally, highly capable and efficient internal data structures and methods for accessing the netlist database should be used. Then a scheme/guile <acronym title="Application Programming Interface">API</acronym> provided for an external script engine. (It may be beneficial to use swig to allow easy interfacing to multiple scripting languages.) The idea is to produce a netlister capable of handling large, hierarchical designs while still allowing users to write their own netlisters for their favorite netlist format (as gnetlist does now).
</p>
<p>
@@ -124,7 +130,8 @@ Difficulty = 3
<div class="level5">
<p>
- The goal of this project is to write a driver file format translation, particularly for import and export of foreign formats. A start already exists with gnucap language plugins. It would be sort of like the existing â??gnetlistâ?? but be universal and able to translate in both directions.
+
+The goal of this project is to write a driver file format translation, particularly for import and export of foreign formats. A start already exists with gnucap language plugins. It would be sort of like the existing â??gnetlistâ?? but be universal and able to translate in both directions.
</p>
<p>
@@ -141,7 +148,8 @@ Difficulty = 1
<div class="level5">
<p>
- After we have the â??translator main programâ??, above, we need plugins for the formats to import and export. Gnucap already has support for Spice, Spectre, and Verilog, as plugins. These plugins can be used with the system, and as examples of how others can be written. The plugin needs to translate in both directions.
+
+After we have the â??translator main programâ??, above, we need plugins for the formats to import and export. Gnucap already has support for Spice, Spectre, and Verilog, as plugins. These plugins can be used with the system, and as examples of how others can be written. The plugin needs to translate in both directions.
</p>
<p>
@@ -149,7 +157,7 @@ Obvious formats needed by the gEDA system are gschem, PCB, and Gerber.
</p>
<p>
-Foreign formats needed, to provide a migration path between gEDA and other flows, include kicad, oregano, orcad, QUCS, LTspice, ….
+Foreign formats needed, to provide a migration path between gEDA and other flows, include kicad, oregano, orcad, QUCS, LTspice, â?¦.
</p>
<p>
diff --git a/docs/wiki/gschem-projects.html b/docs/wiki/gschem-projects.html
index 1e26b36..77659ee 100644
--- a/docs/wiki/gschem-projects.html
+++ b/docs/wiki/gschem-projects.html
@@ -12,9 +12,7 @@
<body>
-
-
-<h3><a name="gschem_schematic_capture_tool" id="gschem_schematic_capture_tool">Gschem schematic capture tool</a></h3>
+<h3 class="sectionedit1494"><a name="gschem_schematic_capture_tool" id="gschem_schematic_capture_tool">Gschem schematic capture tool</a></h3>
<div class="level3">
</div>
@@ -23,7 +21,8 @@
<div class="level5">
<p>
- In this project, you would expand libgeda (if needed) to provide a complete enough guile interface to be able to do more complex database manipulations. One use would be to have a back annotation tool that used libgeda instead of relying on perl. The problem with perl is that youâ??ve involved Yet Another Gschem Parser. This actually may be combined with the previous project about rewriting the gnetlist internals.
+
+In this project, you would expand libgeda (if needed) to provide a complete enough guile interface to be able to do more complex database manipulations. One use would be to have a back annotation tool that used libgeda instead of relying on perl. The problem with perl is that you've involved Yet Another Gschem Parser. This actually may be combined with the previous project about rewriting the gnetlist internals.
</p>
<p>
@@ -36,7 +35,8 @@ Difficulty = 3
<div class="level5">
<p>
- In gschem, please add a why to show hidden text for just one symbol only. Currently [en] will show all the hidden text for all symbols and that makes a real visual mess. Implement this by just showing the hidden text for the currently selected symbols.
+
+In gschem, please add a why to show hidden text for just one symbol only. Currently [en] will show all the hidden text for all symbols and that makes a real visual mess. Implement this by just showing the hidden text for the currently selected symbols.
</p>
<p>
@@ -49,7 +49,8 @@ Difficulty = 1
<div class="level5">
<p>
- In gschem, the size of the handles for lines, nets, and objects scale with increasing zoom. Thus for small lines the handles overlap, and if I zoom in closely, it becomes very hard to pick the right object to manipulate. Please let the size of the handles be constant, regardless of the zoom factor. This is virtually how all vector graphics applications work.
+
+In gschem, the size of the handles for lines, nets, and objects scale with increasing zoom. Thus for small lines the handles overlap, and if I zoom in closely, it becomes very hard to pick the right object to manipulate. Please let the size of the handles be constant, regardless of the zoom factor. This is virtually how all vector graphics applications work.
</p>
<p>
@@ -62,7 +63,8 @@ Difficulty = 1
<div class="level5">
<p>
- In gschem, implement a mechanism that would (when turned enabled) automatically fill in proper global attributes for the design. These attributes could be the date of the last modification, name of the project, author, number of sheets, etc…
+
+In gschem, implement a mechanism that would (when turned enabled) automatically fill in proper global attributes for the design. These attributes could be the date of the last modification, name of the project, author, number of sheets, etcâ?¦
</p>
<p>
@@ -75,7 +77,8 @@ Difficulty = 1 to 2
<div class="level5">
<p>
- Improve error messages in gschem when a rc file doesnâ??t load correctly. Currently the error messages are cryptic and not useful at all. There are several other places in gschem where the error messages could be vastly improved.
+
+Improve error messages in gschem when a rc file doesn't load correctly. Currently the error messages are cryptic and not useful at all. There are several other places in gschem where the error messages could be vastly improved.
</p>
<p>
@@ -88,7 +91,8 @@ Difficulty = 1
<div class="level5">
<p>
- Add a dialog box that lets you do a global search and replace. Currently you can do a find for a specific attribute, but several users have asked if gschem could also provide a way of doing a replace operation as well.
+
+Add a dialog box that lets you do a global search and replace. Currently you can do a find for a specific attribute, but several users have asked if gschem could also provide a way of doing a replace operation as well.
</p>
<p>
@@ -101,7 +105,8 @@ Difficulty = 1 to 2
<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.
+
+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>
@@ -114,7 +119,8 @@ Difficulty = 3
<div class="level5">
<p>
- In gschem, add some sort of visual feedback to tell the user which attribute is attached to which component. This would be useful since sometimes you move attributes/components around and things get a little bit separated distance wise.
+
+In gschem, add some sort of visual feedback to tell the user which attribute is attached to which component. This would be useful since sometimes you move attributes/components around and things get a little bit separated distance wise.
</p>
<p>
@@ -127,7 +133,8 @@ Difficulty = 1 to 2
<div class="level5">
<p>
- Add schematic and symbol modes to gschem. Right now users can do invalid things like add a net or bus inside a symbol and gschem allows this quite happily. If there was a symbol mode that disallowed certain actions, then users will not be able to hurt themselves so easily when creating symbols. Like wise a schematic mode wouldnâ??t allow certain operations (such as adding a pin).
+
+Add schematic and symbol modes to gschem. Right now users can do invalid things like add a net or bus inside a symbol and gschem allows this quite happily. If there was a symbol mode that disallowed certain actions, then users will not be able to hurt themselves so easily when creating symbols. Like wise a schematic mode wouldn't allow certain operations (such as adding a pin).
</p>
<p>
@@ -140,7 +147,8 @@ Difficulty = 2 to 3
<div class="level5">
<p>
- Add the ability to move the origin of a symbol in gschem. Right now the origin is always at 0,0 and users have to translate the symbol to the origin. It would be nice if the origin was movable so that you wouldnâ??t have to translate the symbol manually anymore. This would also allow the user to pick the insert point of the symbol when adding components to a schematic.
+
+Add the ability to move the origin of a symbol in gschem. Right now the origin is always at 0,0 and users have to translate the symbol to the origin. It would be nice if the origin was movable so that you wouldn't have to translate the symbol manually anymore. This would also allow the user to pick the insert point of the symbol when adding components to a schematic.
</p>
<p>
@@ -153,7 +161,8 @@ Difficulty = 2 to 3
<div class="level5">
<p>
- Add the ability to move pins/attributes/whatever on instantiated components in a schematic. This one is quite tricky, but it would allow for various things that people have been requesting (this might be a good foundation for a greatly improved back annotation mechanism from PCB).
+
+Add the ability to move pins/attributes/whatever on instantiated components in a schematic. This one is quite tricky, but it would allow for various things that people have been requesting (this might be a good foundation for a greatly improved back annotation mechanism from PCB).
</p>
<p>
@@ -166,7 +175,8 @@ Difficulty = 3 to 4
<div class="level5">
<p>
- In gschem, add a finer grid when moving attributes or text around.
+
+In gschem, add a finer grid when moving attributes or text around.
</p>
<p>
@@ -179,7 +189,9 @@ Difficulty = 2
<div class="level5">
<p>
- Adding some more useful buttons to the gschem toolbar. Typical functionalities that gschem does not have on the toolbar:
+
+Adding some more useful buttons to the gschem toolbar. Typical functionalities that gschem does not have on the toolbar:
+
</p>
<ul>
<li class="level1"><div class="li"> Up/down schematic/symbol</div>
@@ -199,7 +211,8 @@ Difficulty = 2
</ul>
<p>
- It would be really nice if the toolbar buttons were configurable either on the fly or through an rc file.
+
+It would be really nice if the toolbar buttons were configurable either on the fly or through an rc file.
</p>
<p>
@@ -212,11 +225,12 @@ Difficulty = 2 to 3
<div class="level5">
<p>
- In gschem hierarchical design is accomplished by symbols in the top sheet that represent sub sheets. Currently these sub sheet symbols and the sub sheet itself have to be created manually. The purpose of this project is to design and implement an interactive generator of such symbols and sub sheets. It should work both strategies of hierachical design, bottom-up and top-down. Top-down refers to the case where the parent sheet is designed first and diverts into sub sheets. With bottom-up the sub sheets are designed first. The generator should accept user input on the number and the name of input and output signals. The generator may present a list of named net on the current sheet and let the user pick those that should link to the sub sheet. Power nets to be available on the sub sheet may be specified too. In case of a top-down approach the generator should additionally create a draft of the sub sheet with symbols for the in and out signals placed at some default position. The generator should integrate into the main <acronym title="Graphical User Interface">GUI</acronym> of gschem.
+
+In gschem hierarchical design is accomplished by symbols in the top sheet that represent sub sheets. Currently these sub sheet symbols and the sub sheet itself have to be created manually. The purpose of this project is to design and implement an interactive generator of such symbols and sub sheets. It should work both strategies of hierachical design, bottom-up and top-down. Top-down refers to the case where the parent sheet is designed first and diverts into sub sheets. With bottom-up the sub sheets are designed first. The generator should accept user input on the number and the name of input and output signals. The generator may present a list of named net on the current sheet and let the user pick those that should link to the sub sheet. Power nets to be available on the sub sheet may be specified too. In case of a top-down approach the generator should additionally create a draft of the sub sheet with symbols for the in and out signals placed at some default position. The generator should integrate into the main <acronym title="Graphical User Interface">GUI</acronym> of gschem.
</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="https://bugs.launchpad.net/geda/+bug/698670"; class="urlextern" title="https://bugs.launchpad.net/geda/+bug/698670"; rel="nofollow">the bash script geda_sch2sym</a> in the bug tracker. This may be used as a starting point. However, a restart from scratch would be welcome too.
</p>
<p>
diff --git a/docs/wiki/gsoc2007.html b/docs/wiki/gsoc2007.html
index 8ece0bd..67e71e0 100644
--- a/docs/wiki/gsoc2007.html
+++ b/docs/wiki/gsoc2007.html
@@ -11,36 +11,14 @@
</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="#announcement_of_participation_in_google_s_summer_of_code" class="toc">Announcement of participation in Google's Summer of Code</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#google_application_information" class="toc">Google application information.</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#project_timeline_and_commitment_level" class="toc">Project timeline and commitment level</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#project_integration" class="toc">Project Integration</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#student_information" class="toc">Student Information</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="#mentors" class="toc">Mentors</a></span></div></li></ul>
-</li></ul>
-</li></ul>
-</div>
-</div>
-
-
-<h3><a name="announcement_of_participation_in_google_s_summer_of_code" id="announcement_of_participation_in_google_s_summer_of_code">Announcement of participation in Google's Summer of Code</a></h3>
+<h3 class="sectionedit1495"><a name="announcement_of_participation_in_google_s_summer_of_code" id="announcement_of_participation_in_google_s_summer_of_code">Announcement of participation in Google's Summer of Code</a></h3>
<div class="level3">
<p>
- Good news! The gEDA Project has been accepted as a mentoring organization by Googleâ??s Summer of Code program! The alphabetized list of all projects participating in Googleâ??s SoC is presented here:
+
+Good news! The gEDA Project has been accepted as a mentoring organization by Google's Summer of Code program! The alphabetized list of all projects participating in Google's SoC is presented here:
+
</p>
<ul>
<li class="level1"><div class="li"> <a href="http://code.google.com/soc/"; class="urlextern" title="http://code.google.com/soc/"; rel="nofollow">http://code.google.com/soc/</a> </div>
@@ -48,7 +26,8 @@
</ul>
<p>
- gEDA is listed as â??The gEDA Projectâ??. We are very pleased to be recognized as a participant in the Summer of Code project!
+
+gEDA is listed as â??The gEDA Projectâ??. We are very pleased to be recognized as a participant in the Summer of Code project!
</p>
<p>
@@ -56,7 +35,8 @@ Now is the time for interested students to get their applications ready. Note th
</p>
<p>
-After that, you must apply directly to Google through this web page:
+After that, you must apply directly to Google through this web page:
+
</p>
<ul>
<li class="level1"><div class="li"> <a href="http://code.google.com/soc/"; class="urlextern" title="http://code.google.com/soc/"; rel="nofollow">http://code.google.com/soc/</a> </div>
@@ -64,16 +44,18 @@ After that, you must apply directly to Google through this web page:
</ul>
<p>
- Good luck with your application, and we look forward to working with you!
+
+Good luck with your application, and we look forward to working with you!
</p>
</div>
-<!-- SECTION "Announcement of participation in Google's Summer of Code" [1-1358] -->
-<h3><a name="google_application_information" id="google_application_information">Google application information.</a></h3>
+<!-- EDIT1495 SECTION "Announcement of participation in Google's Summer of Code" [1-1358] -->
+<h3 class="sectionedit1496"><a name="google_application_information" id="google_application_information">Google application information.</a></h3>
<div class="level3">
<p>
- The gEDA Project invites students to work with us under the auspices of Googleâ??s Summer of Code program! We are a group of professional hardware and software engineers with an interest in developing CAD tools for electronic design under Linux (and other unix flavors). The project is over eight years old, and has matured to the point where our design tools are suitable for use by students, professionals, educators, hobbyists, consultants, and anybody who needs a set of quality EDA tools for Linux. Becoming involved in the gEDA Project is a great way to learn about both software engineering and electronics!
+
+The gEDA Project invites students to work with us under the auspices of Google's Summer of Code program! We are a group of professional hardware and software engineers with an interest in developing CAD tools for electronic design under Linux (and other unix flavors). The project is over eight years old, and has matured to the point where our design tools are suitable for use by students, professionals, educators, hobbyists, consultants, and anybody who needs a set of quality EDA tools for Linux. Becoming involved in the gEDA Project is a great way to learn about both software engineering and electronics!
</p>
<p>
@@ -81,19 +63,22 @@ Details for student applications to Google can be found in the Google SOC Studen
</p>
</div>
-<!-- SECTION "Google application information." [1359-2569] -->
-<h3><a name="project_timeline_and_commitment_level" id="project_timeline_and_commitment_level">Project timeline and commitment level</a></h3>
+<!-- EDIT1496 SECTION "Google application information." [1359-2569] -->
+<h3 class="sectionedit1497"><a name="project_timeline_and_commitment_level" id="project_timeline_and_commitment_level">Project timeline and commitment level</a></h3>
<div class="level3">
<p>
- A Google Summer of Code project should be considered a full time job and will require that level of time commitment. In addition, there must be some working code committed in time for the midterm evaluation for a good review. Project Details
+
+A Google Summer of Code project should be considered a full time job and will require that level of time commitment. In addition, there must be some working code committed in time for the midterm evaluation for a good review.
+Project Details
</p>
<p>
-When submitting an application or project proposal, please include the following details about the project:
+When submitting an application or project proposal, please include the following details about the project:
+
</p>
<ul>
-<li class="level1"><div class="li"> Summary of the project including the end goal. This should be a couple of paragraphs – enough to fully explain what you have in mind. Writing a couple of use-cases will help if you are creating a new program (as opposed to upgrading an existing one).</div>
+<li class="level1"><div class="li"> Summary of the project including the end goal. This should be a couple of paragraphs â?? enough to fully explain what you have in mind. Writing a couple of use-cases will help if you are creating a new program (as opposed to upgrading an existing one).</div>
</li>
<li class="level2"><div class="li"> Detail the scope of the project. What do you intend on delivering and what do you not intend on delivering. In best case, this will be a list of features/behaviors your program will possess.</div>
</li>
@@ -101,17 +86,18 @@ When submitting an application or project proposal, please include the following
</li>
<li class="level2"><div class="li"> Is this a rewrite/upgrade of existing software or is it a â??from scratchâ?? project.</div>
</li>
-<li class="level2"><div class="li"> Who is the mentor for your project? Ideally, your mentor will be one of the current gEDA developers, or will be a professor or professional EE familiar with the gEDA project. If you donâ??t know who should mentor your project, then we can help choose somebody for you based upon the project you have chosen.</div>
+<li class="level2"><div class="li"> Who is the mentor for your project? Ideally, your mentor will be one of the current gEDA developers, or will be a professor or professional EE familiar with the gEDA project. If you don't know who should mentor your project, then we can help choose somebody for you based upon the project you have chosen.</div>
</li>
</ul>
</div>
-<!-- SECTION "Project timeline and commitment level" [2570-3936] -->
-<h3><a name="project_integration" id="project_integration">Project Integration</a></h3>
+<!-- EDIT1497 SECTION "Project timeline and commitment level" [2570-3936] -->
+<h3 class="sectionedit1498"><a name="project_integration" id="project_integration">Project Integration</a></h3>
<div class="level3">
<p>
-It is important for us to understand how your project will fit into the rest of gEDA. To help us understand this, also include the following information:
+It is important for us to understand how your project will fit into the rest of gEDA. To help us understand this, also include the following information:
+
</p>
<ul>
<li class="level1"><div class="li"> Which components of gEDA will be affected and require code changes? Examples are â??only PCBâ?? or â??libgeda, gnetlist, gschem, and PCBâ??.</div>
@@ -125,12 +111,14 @@ It is important for us to understand how your project will fit into the rest of
</ul>
</div>
-<!-- SECTION "Project Integration" [3937-4724] -->
-<h3><a name="student_information" id="student_information">Student Information</a></h3>
+<!-- EDIT1498 SECTION "Project Integration" [3937-4724] -->
+<h3 class="sectionedit1499"><a name="student_information" id="student_information">Student Information</a></h3>
<div class="level3">
<p>
- Tell us a little about yourself in your application.
+
+Tell us a little about yourself in your application.
+
</p>
<ul>
<li class="level1"><div class="li"> What programming experience do you have? Please list languages you have used, classwork you have completed, and projects you have completed.</div>
@@ -152,21 +140,24 @@ It is important for us to understand how your project will fit into the rest of
</ul>
</div>
-<!-- SECTION "Student Information" [4725-5792] -->
-<h3><a name="suggested_projects" id="suggested_projects">Suggested Projects</a></h3>
+<!-- EDIT1499 SECTION "Student Information" [4725-5792] -->
+<h3 class="sectionedit1500"><a name="suggested_projects" id="suggested_projects">Suggested Projects</a></h3>
<div class="level3">
<p>
- The list of suggested projects is available <a href="gsoc2007_projects.html" class="wikilink1" title="gsoc2007_projects.html">here</a>
+
+The list of suggested projects is available <a href="gsoc2007_projects.html" class="wikilink1" title="gsoc2007_projects.html">here</a>
</p>
</div>
-<!-- SECTION "Suggested Projects" [5793-5894] -->
-<h3><a name="mentors" id="mentors">Mentors</a></h3>
+<!-- EDIT1500 SECTION "Suggested Projects" [5793-5894] -->
+<h3 class="sectionedit1501"><a name="mentors" id="mentors">Mentors</a></h3>
<div class="level3">
<p>
- Here is a list of mentors for the gEDA Projectâ??s GSoC. Please feel free to contact us with any questions you may have.
+
+Here is a list of mentors for the gEDA Project's GSoC. Please feel free to contact us with any questions you may have.
+
</p>
<ul>
<li class="level1"><div class="li"> Dan McMahill (danATmcmahill.net)- Primary GSoC admin, PCB developer, gEDA/gaf developer</div>
@@ -182,5 +173,5 @@ It is important for us to understand how your project will fit into the rest of
</ul>
</div>
-<!-- SECTION "Mentors" [5895-] --></body>
+<!-- EDIT1501 SECTION "Mentors" [5895-] --></body>
</html>
diff --git a/docs/wiki/gsoc2007_projects.html b/docs/wiki/gsoc2007_projects.html
index c2b847c..75171d0 100644
--- a/docs/wiki/gsoc2007_projects.html
+++ b/docs/wiki/gsoc2007_projects.html
@@ -11,67 +11,17 @@
</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_project_ideas" class="toc">gEDA GSoC Project Ideas</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#project_manager" class="toc">Project manager</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#improve_handling_of_non-copper_layers_in_pcb" class="toc">Improve handling of non-copper layers in pcb</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#gerber_to_pcb_converter" class="toc">Gerber to PCB converter</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#usability_improvements_for_ngspice_gnucap" class="toc">Usability improvements for ngspice/Gnucap</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#parts_manager" class="toc">Parts manager</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#gnetlist_gnetman_support_for_hierarchy" class="toc">Gnetlist/gnetman support for hierarchy</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#libgeda_api_formalization" class="toc">Libgeda API formalization</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#recently_loaded_file_list_for_gschem_and_or_pcb" class="toc">Recently loaded file list for gschem and/or pcb</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#remember_dialog_size_and_positions" class="toc">Remember dialog size and positions</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#show_hidden_attributes_for_selected_components" class="toc">Show hidden attributes for selected components</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#constant_sized_handles_grips" class="toc">Constant sized handles/grips</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#automatically_fill_in_global_attributes_in_gschem" class="toc">Automatically fill in global attributes in gschem</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#visual_feedback_when_pressing_keyboard_accelerators" class="toc">Visual feedback when pressing keyboard accelerators</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#improve_error_messages_in_gschem" class="toc">Improve error messages in gschem</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#global_search_and_replace" class="toc">Global search and replace</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#visual_feedback_for_attached_attributes" class="toc">Visual feedback for attached attributes</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#schematic_and_symbol_modes" class="toc">Schematic and symbol modes</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#movable_symbol_origin" class="toc">Movable symbol origin</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#modify_instantiated_symbols_in_a_schematic" class="toc">Modify instantiated symbols in a schematic</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#finer_grid_when_moving_attributes" class="toc">Finer grid when moving attributes</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#frequently_used_symbols_sidebar" class="toc">Frequently used symbols sidebar</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#add_more_toolbar_buttons" class="toc">Add more toolbar buttons</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#filled_polygon_object" class="toc">Filled polygon object</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#fix_geda_gaf_bugs_and_or_implement_feature_requests" class="toc">Fix gEDA/gaf bugs and/or implement feature requests</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#make_gsch2pcb_use_same_search_paths_as_pcb" class="toc">Make gsch2pcb use same search paths as PCB</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#verilog_vhdl_code_generator_s_for_icarus_verilog" class="toc">Verilog/VHDL code generator[s] for Icarus Verilog</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#create_comprehensive_test_suite_for_entire_geda_suite" class="toc">Create comprehensive test suite for entire gEDA Suite</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#revive_tclspice_add_return_code_to_analysis" class="toc">Revive TCLSpice, add return code to analysis</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#pcb_drc_interface_improvements" class="toc">PCB DRC interface improvements</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#add_enhancements_to_gerbv" class="toc">Add enhancements to gerbv.</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#pcb_autorouter" class="toc">PCB Autorouter</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#improved_and_formalized_mechanism_for_forward_backward_annotation" class="toc">Improved and formalized mechanism for forward/backward annotation</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#ipc_footprint_calculator" class="toc">IPC Footprint Calculator</a></span></div></li></ul>
-</li></ul>
-</li></ul>
-</div>
-</div>
-
-
-
-<h3><a name="geda_gsoc_project_ideas" id="geda_gsoc_project_ideas">gEDA GSoC Project Ideas</a></h3>
+<h3 class="sectionedit1502"><a name="geda_gsoc_project_ideas" id="geda_gsoc_project_ideas">gEDA GSoC Project Ideas</a></h3>
<div class="level3">
<p>
- This page contains various ideas for projects. 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!
+
+This page contains various ideas for projects. 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>
<p>
-Note that some of these projects are too small by themselves to be stand-alone projects. The Summer of Code program is a 3 month program, and youâ??re supposed to treat your project as a full-time job. Applicants should keep that in mind and possibly combine ideas from different projects if one suggested project is too small. To help you, I have graded each project on a scale of 1 to 5, where 1 = too small for a full summer, 3 = roughly enough for a full summer, and 5 = way too large for a full summer. Of course, what takes one programmer one week might take another six months, so any judgement is subjective. However, you can use these ratings to help you figure out which project is the right one for you.
+Note that some of these projects are too small by themselves to be stand-alone projects. The Summer of Code program is a 3 month program, and you're supposed to treat your project as a full-time job. Applicants should keep that in mind and possibly combine ideas from different projects if one suggested project is too small. To help you, I have graded each project on a scale of 1 to 5, where 1 = too small for a full summer, 3 = roughly enough for a full summer, and 5 = way too large for a full summer. Of course, what takes one programmer one week might take another six months, so any judgement is subjective. However, you can use these ratings to help you figure out which project is the right one for you.
</p>
<p>
@@ -79,30 +29,32 @@ The vast majority of gEDA Suite programs are written in either C or C++. However
</p>
<p>
-Please visit the gEDA Projectâ??s main GSoC page for more info (including contact information).
+Please visit the gEDA Project's main GSoC page for more info (including contact information).
</p>
</div>
-<!-- SECTION "gEDA GSoC Project Ideas" [1-1671] -->
-<h3><a name="project_manager" id="project_manager">Project manager</a></h3>
+<!-- EDIT1502 SECTION "gEDA GSoC Project Ideas" [1-1671] -->
+<h3 class="sectionedit1503"><a name="project_manager" id="project_manager">Project manager</a></h3>
<div class="level3">
<p>
-gEDA needs a new, top-level project manager. Using this tool, A user would type â??gedaâ?? at the command line (or push a button on his desktop manager), and this program would start a <acronym title="Graphical User Interface">GUI</acronym> which would provide easy, user-friendly access to all design tools. The project manager would implement (at least) the following functionalities:
+gEDA needs a new, top-level project manager. Using this tool, A user would type â??gedaâ?? at the command line (or push a button on his desktop manager), and this program would start a <acronym title="Graphical User Interface">GUI</acronym> which would provide easy, user-friendly access to all design tools. The project manager would implement (at least) the following functionalities:
+
</p>
<ul>
<li class="level1"><div class="li"> Menu items or buttons to run various gEDA programs like gschem, gattrib, gsch2pcb, PCB, gerbv, ngspice, Gnucap, etc.</div>
</li>
<li class="level2"><div class="li"> Manage resource files (i.e. the project manager allows you to edit and write gafrc, gsch2pcb project file, spinit, etc.</div>
</li>
-<li class="level2"><div class="li"> Enable creation of project archives – i.e. using garchive, but using an intelligent method to gather & archive the symbols & footprints used in the project.</div>
+<li class="level2"><div class="li"> Enable creation of project archives â?? i.e. using garchive, but using an intelligent method to gather & archive the symbols & footprints used in the project.</div>
</li>
<li class="level2"><div class="li"> Perhaps implement some type of lockfiles, or at least some enforcement of the design flow (good for newbies).</div>
</li>
</ul>
<p>
- Since the project manager is the first program seen by many new users, this program needs a high degree of polish, and should enforce good design practice without getting in the userâ??s way too much.
+
+Since the project manager is the first program seen by many new users, this program needs a high degree of polish, and should enforce good design practice without getting in the user's way too much.
</p>
<p>
@@ -110,12 +62,13 @@ Difficulty = 4
</p>
</div>
-<!-- SECTION "Project manager" [1672-2777] -->
-<h3><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></h3>
+<!-- EDIT1503 SECTION "Project manager" [1672-2777] -->
+<h3 class="sectionedit1504"><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></h3>
<div class="level3">
<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
+
+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>
@@ -123,12 +76,13 @@ Difficulty = 2
</p>
</div>
-<!-- SECTION "Improve handling of non-copper layers in pcb" [2778-3234] -->
-<h3><a name="gerber_to_pcb_converter" id="gerber_to_pcb_converter">Gerber to PCB converter</a></h3>
+<!-- EDIT1504 SECTION "Improve handling of non-copper layers in pcb" [2778-3234] -->
+<h3 class="sectionedit1505"><a name="gerber_to_pcb_converter" id="gerber_to_pcb_converter">Gerber to PCB converter</a></h3>
<div class="level3">
<p>
- In this project, the student would create a program which reads a Gerber file, and creates an output file which is a metal layer or footprint editable by PCB. This might be a <acronym title="Practical Extraction and Report Language">Perl</acronym> or Python script. Such a program is very desirable since it gives users the ability to edit legacy designs – i.e. those for which they only have Gerbers.
+
+In this project, the student would create a program which reads a Gerber file, and creates an output file which is a metal layer or footprint editable by PCB. This might be a <acronym title="Practical Extraction and Report Language">Perl</acronym> or Python script. Such a program is very desirable since it gives users the ability to edit legacy designs â?? i.e. those for which they only have Gerbers.
</p>
<p>
@@ -136,16 +90,18 @@ Difficulty = 3
</p>
</div>
-<!-- SECTION "Gerber to PCB converter" [3235-3621] -->
-<h3><a name="usability_improvements_for_ngspice_gnucap" id="usability_improvements_for_ngspice_gnucap">Usability improvements for ngspice/Gnucap</a></h3>
+<!-- EDIT1505 SECTION "Gerber to PCB converter" [3235-3621] -->
+<h3 class="sectionedit1506"><a name="usability_improvements_for_ngspice_gnucap" id="usability_improvements_for_ngspice_gnucap">Usability improvements for ngspice/Gnucap</a></h3>
<div class="level3">
<p>
- Ngspice and Gnucap are the gEDA Projectâ??s analog circuit simulators. They are both command-line tools, meaning that you type commands into a shell-like program at a prompt. However, some popular commercial simulators support easy simulation and analysis directly from within a schematic capture <acronym title="Graphical User Interface">GUI</acronym>. This method of working is particularly well suited to newbies.
+
+Ngspice and Gnucap are the gEDA Project's analog circuit simulators. They are both command-line tools, meaning that you type commands into a shell-like program at a prompt. However, some popular commercial simulators support easy simulation and analysis directly from within a schematic capture <acronym title="Graphical User Interface">GUI</acronym>. This method of working is particularly well suited to newbies.
</p>
<p>
-A new user would like to do the following things inside gschem:
+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>
@@ -157,11 +113,12 @@ 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.
+
+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.
</p>
<p>
-This project involves tightening the link between gschem and the back-end simulation programs. This might be done using some type of IPC, such as DBUS. Indeed, a preliminary DBUS implementation for gschem ↔ PCB already exists; the student might leverage the DBUS work for this project.
+This project involves tightening the link between gschem and the back-end simulation programs. This might be done using some type of IPC, such as DBUS. Indeed, a preliminary DBUS implementation for gschem â?? PCB already exists; the student might leverage the DBUS work for this project.
</p>
<p>
@@ -169,12 +126,13 @@ Difficulty = 3
</p>
</div>
-<!-- SECTION "Usability improvements for ngspice/Gnucap" [3622-4730] -->
-<h3><a name="parts_manager" id="parts_manager">Parts manager</a></h3>
+<!-- EDIT1506 SECTION "Usability improvements for ngspice/Gnucap" [3622-4730] -->
+<h3 class="sectionedit1507"><a name="parts_manager" id="parts_manager">Parts manager</a></h3>
<div class="level3">
<p>
- In this project, you would create a parts manager that takes a graphical symbol and a physical footprint, and marries the two to produce a heavy part. In addition, this tool should be able to support multiple backend flows. By this I mean that the parts manager should be able to also indicate how the symbol should be netlisted for spice, gnucap, or other backends. If possible it would be nice to integrate this into gschem in a way that allowed symbols to be placed and the footprint attribute to come up with a list of choices.
+
+In this project, you would create a parts manager that takes a graphical symbol and a physical footprint, and marries the two to produce a heavy part. In addition, this tool should be able to support multiple backend flows. By this I mean that the parts manager should be able to also indicate how the symbol should be netlisted for spice, gnucap, or other backends. If possible it would be nice to integrate this into gschem in a way that allowed symbols to be placed and the footprint attribute to come up with a list of choices.
</p>
<p>
@@ -186,12 +144,13 @@ Difficulty = 4
</p>
</div>
-<!-- SECTION "Parts manager" [4731-5730] -->
-<h3><a name="gnetlist_gnetman_support_for_hierarchy" id="gnetlist_gnetman_support_for_hierarchy">Gnetlist/gnetman support for hierarchy</a></h3>
+<!-- EDIT1507 SECTION "Parts manager" [4731-5730] -->
+<h3 class="sectionedit1508"><a name="gnetlist_gnetman_support_for_hierarchy" id="gnetlist_gnetman_support_for_hierarchy">Gnetlist/gnetman support for hierarchy</a></h3>
<div class="level3">
<p>
- The goal of this project is to create a scalable, professional-grade netlister. The project might involve re-writing gnetlist to enable hierarchical designs, or might involve upgrading â??gnetmanâ?? to incorporate scripted back-ends. The upgrade would be done with an eye towards scalability. Ideally, highly capable and efficient internal data structures and methods for accessing the netlist database should be used. Then a scheme/guile <acronym title="Application Programming Interface">API</acronym> provided for an external script engine. (It may be beneficial to use swig to allow easy interfacing to multiple scripting languages.) The idea is to produce a netlister capable of handling large, hierarchical designs while still allowing users to write their own netlisters for their favorite netlist format (as gnetlist does now).
+
+The goal of this project is to create a scalable, professional-grade netlister. The project might involve re-writing gnetlist to enable hierarchical designs, or might involve upgrading â??gnetmanâ?? to incorporate scripted back-ends. The upgrade would be done with an eye towards scalability. Ideally, highly capable and efficient internal data structures and methods for accessing the netlist database should be used. Then a scheme/guile <acronym title="Application Programming Interface">API</acronym> provided for an external script engine. (It may be beneficial to use swig to allow easy interfacing to multiple scripting languages.) The idea is to produce a netlister capable of handling large, hierarchical designs while still allowing users to write their own netlisters for their favorite netlist format (as gnetlist does now).
</p>
<p>
@@ -203,12 +162,13 @@ Difficulty = 3
</p>
</div>
-<!-- SECTION "Gnetlist/gnetman support for hierarchy" [5731-7097] -->
-<h3><a name="libgeda_api_formalization" id="libgeda_api_formalization">Libgeda API formalization</a></h3>
+<!-- EDIT1508 SECTION "Gnetlist/gnetman support for hierarchy" [5731-7097] -->
+<h3 class="sectionedit1509"><a name="libgeda_api_formalization" id="libgeda_api_formalization">Libgeda API formalization</a></h3>
<div class="level3">
<p>
- In this project, you would expand libgeda (if needed) to provide a complete enough guile interface to be able to do more complex database manipulations. One use would be to have a back annotation tool that used libgeda instead of relying on perl. The problem with perl is that youâ??ve involved Yet Another Gschem Parser. This actually may be combined with the previous project about rewriting the gnetlist internals.
+
+In this project, you would expand libgeda (if needed) to provide a complete enough guile interface to be able to do more complex database manipulations. One use would be to have a back annotation tool that used libgeda instead of relying on perl. The problem with perl is that you've involved Yet Another Gschem Parser. This actually may be combined with the previous project about rewriting the gnetlist internals.
</p>
<p>
@@ -216,12 +176,13 @@ Difficulty = 3
</p>
</div>
-<!-- SECTION "Libgeda API formalization" [7098-7567] -->
-<h3><a name="recently_loaded_file_list_for_gschem_and_or_pcb" id="recently_loaded_file_list_for_gschem_and_or_pcb">Recently loaded file list for gschem and/or pcb</a></h3>
+<!-- EDIT1509 SECTION "Libgeda API formalization" [7098-7567] -->
+<h3 class="sectionedit1510"><a name="recently_loaded_file_list_for_gschem_and_or_pcb" id="recently_loaded_file_list_for_gschem_and_or_pcb">Recently loaded file list for gschem and/or pcb</a></h3>
<div class="level3">
<p>
- Presently gschem and pcb do not present a list of recently loaded files in the file menu. It would be nice if gschem and/or pcb kept track of the last few files a user loaded. This is a common feature found in other programs.
+
+Presently gschem and pcb do not present a list of recently loaded files in the file menu. It would be nice if gschem and/or pcb kept track of the last few files a user loaded. This is a common feature found in other programs.
</p>
<p>
@@ -229,12 +190,13 @@ Difficulty = 1
</p>
</div>
-<!-- SECTION "Recently loaded file list for gschem and/or pcb" [7568-7869] -->
-<h3><a name="remember_dialog_size_and_positions" id="remember_dialog_size_and_positions">Remember dialog size and positions</a></h3>
+<!-- EDIT1510 SECTION "Recently loaded file list for gschem and/or pcb" [7568-7869] -->
+<h3 class="sectionedit1511"><a name="remember_dialog_size_and_positions" id="remember_dialog_size_and_positions">Remember dialog size and positions</a></h3>
<div class="level3">
<p>
- gschem and pcb dialogs should remember their size and position. Currently they do not remember anything about their position and size and several users have complained since they have to reposition and/or resize the dialog boxes every time they are opened..
+
+gschem and pcb dialogs should remember their size and position. Currently they do not remember anything about their position and size and several users have complained since they have to reposition and/or resize the dialog boxes every time they are opened..
</p>
<p>
@@ -242,12 +204,13 @@ Difficulty = 1
</p>
</div>
-<!-- SECTION "Remember dialog size and positions" [7870-8190] -->
-<h3><a name="show_hidden_attributes_for_selected_components" id="show_hidden_attributes_for_selected_components">Show hidden attributes for selected components</a></h3>
+<!-- EDIT1511 SECTION "Remember dialog size and positions" [7870-8190] -->
+<h3 class="sectionedit1512"><a name="show_hidden_attributes_for_selected_components" id="show_hidden_attributes_for_selected_components">Show hidden attributes for selected components</a></h3>
<div class="level3">
<p>
- In gschem, please add a why to show hidden text for just one symbol only. Currently [en] will show all the hidden text for all symbols and that makes a real visual mess. Implement this by just showing the hidden text for the currently selected symbols.
+
+In gschem, please add a why to show hidden text for just one symbol only. Currently [en] will show all the hidden text for all symbols and that makes a real visual mess. Implement this by just showing the hidden text for the currently selected symbols.
</p>
<p>
@@ -255,12 +218,13 @@ Difficulty = 1
</p>
</div>
-<!-- SECTION "Show hidden attributes for selected components" [8191-8518] -->
-<h3><a name="constant_sized_handles_grips" id="constant_sized_handles_grips">Constant sized handles/grips</a></h3>
+<!-- EDIT1512 SECTION "Show hidden attributes for selected components" [8191-8518] -->
+<h3 class="sectionedit1513"><a name="constant_sized_handles_grips" id="constant_sized_handles_grips">Constant sized handles/grips</a></h3>
<div class="level3">
<p>
- In gschem, the size of the handles for lines, nets, and objects scale with increasing zoom. Thus for small lines the handles overlap, and if I zoom in closely, it becomes very hard to pick the right object to manipulate. Please let the size of the handles be constant, regardless of the zoom factor. This is virtually how all vector graphics applications work.
+
+In gschem, the size of the handles for lines, nets, and objects scale with increasing zoom. Thus for small lines the handles overlap, and if I zoom in closely, it becomes very hard to pick the right object to manipulate. Please let the size of the handles be constant, regardless of the zoom factor. This is virtually how all vector graphics applications work.
</p>
<p>
@@ -268,12 +232,13 @@ Difficulty = 1
</p>
</div>
-<!-- SECTION "Constant sized handles/grips" [8519-8936] -->
-<h3><a name="automatically_fill_in_global_attributes_in_gschem" id="automatically_fill_in_global_attributes_in_gschem">Automatically fill in global attributes in gschem</a></h3>
+<!-- EDIT1513 SECTION "Constant sized handles/grips" [8519-8936] -->
+<h3 class="sectionedit1514"><a name="automatically_fill_in_global_attributes_in_gschem" id="automatically_fill_in_global_attributes_in_gschem">Automatically fill in global attributes in gschem</a></h3>
<div class="level3">
<p>
- In gschem, implement a mechanism that would (when turned enabled) automatically fill in proper global attributes for the design. These attributes could be the date of the last modification, name of the project, author, number of sheets, etc…
+
+In gschem, implement a mechanism that would (when turned enabled) automatically fill in proper global attributes for the design. These attributes could be the date of the last modification, name of the project, author, number of sheets, etcâ?¦
</p>
<p>
@@ -281,12 +246,13 @@ Difficulty = 1 to 2
</p>
</div>
-<!-- SECTION "Automatically fill in global attributes in gschem" [8937-9263] -->
-<h3><a name="visual_feedback_when_pressing_keyboard_accelerators" id="visual_feedback_when_pressing_keyboard_accelerators">Visual feedback when pressing keyboard accelerators</a></h3>
+<!-- EDIT1514 SECTION "Automatically fill in global attributes in gschem" [8937-9263] -->
+<h3 class="sectionedit1515"><a name="visual_feedback_when_pressing_keyboard_accelerators" id="visual_feedback_when_pressing_keyboard_accelerators">Visual feedback when pressing keyboard accelerators</a></h3>
<div class="level3">
<p>
- In gschem, please give some feedback when a user presses one of the keyboard accelerator keys. Currently gschem allows for multiple key presses to represent a single command. Sometimes it is hard to remember which one you have pressed. Maybe a little area in the status bar can output this information.
+
+In gschem, please give some feedback when a user presses one of the keyboard accelerator keys. Currently gschem allows for multiple key presses to represent a single command. Sometimes it is hard to remember which one you have pressed. Maybe a little area in the status bar can output this information.
</p>
<p>
@@ -294,12 +260,13 @@ Difficulty = 1
</p>
</div>
-<!-- SECTION "Visual feedback when pressing keyboard accelerators" [9264-9646] -->
-<h3><a name="improve_error_messages_in_gschem" id="improve_error_messages_in_gschem">Improve error messages in gschem</a></h3>
+<!-- EDIT1515 SECTION "Visual feedback when pressing keyboard accelerators" [9264-9646] -->
+<h3 class="sectionedit1516"><a name="improve_error_messages_in_gschem" id="improve_error_messages_in_gschem">Improve error messages in gschem</a></h3>
<div class="level3">
<p>
- Improve error messages in gschem when a rc file doesnâ??t load correctly. Currently the error messages are cryptic and not useful at all. There are several other places in gschem where the error messages could be vastly improved.
+
+Improve error messages in gschem when a rc file doesn't load correctly. Currently the error messages are cryptic and not useful at all. There are several other places in gschem where the error messages could be vastly improved.
</p>
<p>
@@ -307,12 +274,13 @@ Difficulty = 1
</p>
</div>
-<!-- SECTION "Improve error messages in gschem" [9647-9935] -->
-<h3><a name="global_search_and_replace" id="global_search_and_replace">Global search and replace</a></h3>
+<!-- EDIT1516 SECTION "Improve error messages in gschem" [9647-9935] -->
+<h3 class="sectionedit1517"><a name="global_search_and_replace" id="global_search_and_replace">Global search and replace</a></h3>
<div class="level3">
<p>
- Add a dialog box that lets you do a global search and replace. Currently you can do a find for a specific attribute, but several users have asked if gschem could also provide a way of doing a replace operation as well.
+
+Add a dialog box that lets you do a global search and replace. Currently you can do a find for a specific attribute, but several users have asked if gschem could also provide a way of doing a replace operation as well.
</p>
<p>
@@ -320,12 +288,13 @@ Difficulty = 1 to 2
</p>
</div>
-<!-- SECTION "Global search and replace" [9936-10213] -->
-<h3><a name="visual_feedback_for_attached_attributes" id="visual_feedback_for_attached_attributes">Visual feedback for attached attributes</a></h3>
+<!-- EDIT1517 SECTION "Global search and replace" [9936-10213] -->
+<h3 class="sectionedit1518"><a name="visual_feedback_for_attached_attributes" id="visual_feedback_for_attached_attributes">Visual feedback for attached attributes</a></h3>
<div class="level3">
<p>
- In gschem, add some sort of visual feedback to tell the user which attribute is attached to which component. This would be useful since sometimes you move attributes/components around and things get a little bit separated distance wise.
+
+In gschem, add some sort of visual feedback to tell the user which attribute is attached to which component. This would be useful since sometimes you move attributes/components around and things get a little bit separated distance wise.
</p>
<p>
@@ -333,12 +302,13 @@ Difficulty = 1 to 2
</p>
</div>
-<!-- SECTION "Visual feedback for attached attributes" [10214-10523] -->
-<h3><a name="schematic_and_symbol_modes" id="schematic_and_symbol_modes">Schematic and symbol modes</a></h3>
+<!-- EDIT1518 SECTION "Visual feedback for attached attributes" [10214-10523] -->
+<h3 class="sectionedit1519"><a name="schematic_and_symbol_modes" id="schematic_and_symbol_modes">Schematic and symbol modes</a></h3>
<div class="level3">
<p>
- Add schematic and symbol modes to gschem. Right now users can do invalid things like add a net or bus inside a symbol and gschem allows this quite happily. If there was a symbol mode that disallowed certain actions, then users will not be able to hurt themselves so easily when creating symbols. Like wise a schematic mode wouldnâ??t allow certain operations (such as adding a pin).
+
+Add schematic and symbol modes to gschem. Right now users can do invalid things like add a net or bus inside a symbol and gschem allows this quite happily. If there was a symbol mode that disallowed certain actions, then users will not be able to hurt themselves so easily when creating symbols. Like wise a schematic mode wouldn't allow certain operations (such as adding a pin).
</p>
<p>
@@ -346,12 +316,13 @@ Difficulty = 2 to 3
</p>
</div>
-<!-- SECTION "Schematic and symbol modes" [10524-10964] -->
-<h3><a name="movable_symbol_origin" id="movable_symbol_origin">Movable symbol origin</a></h3>
+<!-- EDIT1519 SECTION "Schematic and symbol modes" [10524-10964] -->
+<h3 class="sectionedit1520"><a name="movable_symbol_origin" id="movable_symbol_origin">Movable symbol origin</a></h3>
<div class="level3">
<p>
- Add the ability to move the origin of a symbol in gschem. Right now the origin is always at 0,0 and users have to translate the symbol to the origin. It would be nice if the origin was movable so that you wouldnâ??t have to translate the symbol manually anymore. This would also allow the user to pick the insert point of the symbol when adding components to a schematic.
+
+Add the ability to move the origin of a symbol in gschem. Right now the origin is always at 0,0 and users have to translate the symbol to the origin. It would be nice if the origin was movable so that you wouldn't have to translate the symbol manually anymore. This would also allow the user to pick the insert point of the symbol when adding components to a schematic.
</p>
<p>
@@ -359,12 +330,13 @@ Difficulty = 2 to 3
</p>
</div>
-<!-- SECTION "Movable symbol origin" [10965-11389] -->
-<h3><a name="modify_instantiated_symbols_in_a_schematic" id="modify_instantiated_symbols_in_a_schematic">Modify instantiated symbols in a schematic</a></h3>
+<!-- EDIT1520 SECTION "Movable symbol origin" [10965-11389] -->
+<h3 class="sectionedit1521"><a name="modify_instantiated_symbols_in_a_schematic" id="modify_instantiated_symbols_in_a_schematic">Modify instantiated symbols in a schematic</a></h3>
<div class="level3">
<p>
- Add the ability to move pins/attributes/whatever on instantiated components in a schematic. This one is quite tricky, but it would allow for various things that people have been requesting (this might be a good foundation for a greatly improved back annotation mechanism from PCB).
+
+Add the ability to move pins/attributes/whatever on instantiated components in a schematic. This one is quite tricky, but it would allow for various things that people have been requesting (this might be a good foundation for a greatly improved back annotation mechanism from PCB).
</p>
<p>
@@ -372,12 +344,13 @@ Difficulty = 3 to 4
</p>
</div>
-<!-- SECTION "Modify instantiated symbols in a schematic" [11390-11747] -->
-<h3><a name="finer_grid_when_moving_attributes" id="finer_grid_when_moving_attributes">Finer grid when moving attributes</a></h3>
+<!-- EDIT1521 SECTION "Modify instantiated symbols in a schematic" [11390-11747] -->
+<h3 class="sectionedit1522"><a name="finer_grid_when_moving_attributes" id="finer_grid_when_moving_attributes">Finer grid when moving attributes</a></h3>
<div class="level3">
<p>
- In gschem, add a finer grid when moving attributes or text around.
+
+In gschem, add a finer grid when moving attributes or text around.
</p>
<p>
@@ -385,12 +358,13 @@ Difficulty = 2
</p>
</div>
-<!-- SECTION "Finer grid when moving attributes" [11748-11876] -->
-<h3><a name="frequently_used_symbols_sidebar" id="frequently_used_symbols_sidebar">Frequently used symbols sidebar</a></h3>
+<!-- EDIT1522 SECTION "Finer grid when moving attributes" [11748-11876] -->
+<h3 class="sectionedit1523"><a name="frequently_used_symbols_sidebar" id="frequently_used_symbols_sidebar">Frequently used symbols sidebar</a></h3>
<div class="level3">
<p>
- Add a frequently used symbols sidebar to gschem that is dynamically loaded and/or can be preloaded from an rc file. Several people have asked for this since using the component selection dialog box can be time consuming for recently used/needed components. This is a <acronym title="Graphical User Interface">GUI</acronym> heavy project idea.
+
+Add a frequently used symbols sidebar to gschem that is dynamically loaded and/or can be preloaded from an rc file. Several people have asked for this since using the component selection dialog box can be time consuming for recently used/needed components. This is a <acronym title="Graphical User Interface">GUI</acronym> heavy project idea.
</p>
<p>
@@ -398,12 +372,14 @@ Difficulty = 3
</p>
</div>
-<!-- SECTION "Frequently used symbols sidebar" [11877-12227] -->
-<h3><a name="add_more_toolbar_buttons" id="add_more_toolbar_buttons">Add more toolbar buttons</a></h3>
+<!-- EDIT1523 SECTION "Frequently used symbols sidebar" [11877-12227] -->
+<h3 class="sectionedit1524"><a name="add_more_toolbar_buttons" id="add_more_toolbar_buttons">Add more toolbar buttons</a></h3>
<div class="level3">
<p>
- Adding some more useful buttons to the gschem toolbar. Typical functionalities that gschem does not have on the toolbar:
+
+Adding some more useful buttons to the gschem toolbar. Typical functionalities that gschem does not have on the toolbar:
+
</p>
<ul>
<li class="level1"><div class="li"> Up/down schematic/symbol</div>
@@ -423,7 +399,8 @@ Difficulty = 3
</ul>
<p>
- It would be really nice if the toolbar buttons were configurable either on the fly or through an rc file.
+
+It would be really nice if the toolbar buttons were configurable either on the fly or through an rc file.
</p>
<p>
@@ -431,12 +408,13 @@ Difficulty = 2 to 3
</p>
</div>
-<!-- SECTION "Add more toolbar buttons" [12228-12763] -->
-<h3><a name="filled_polygon_object" id="filled_polygon_object">Filled polygon object</a></h3>
+<!-- EDIT1524 SECTION "Add more toolbar buttons" [12228-12763] -->
+<h3 class="sectionedit1525"><a name="filled_polygon_object" id="filled_polygon_object">Filled polygon object</a></h3>
<div class="level3">
<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.
+
+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>
@@ -444,12 +422,13 @@ Difficulty = 2 to 3
</p>
</div>
-<!-- SECTION "Filled polygon object" [12764-13032] -->
-<h3><a name="fix_geda_gaf_bugs_and_or_implement_feature_requests" id="fix_geda_gaf_bugs_and_or_implement_feature_requests">Fix gEDA/gaf bugs and/or implement feature requests</a></h3>
+<!-- EDIT1525 SECTION "Filled polygon object" [12764-13032] -->
+<h3 class="sectionedit1526"><a name="fix_geda_gaf_bugs_and_or_implement_feature_requests" id="fix_geda_gaf_bugs_and_or_implement_feature_requests">Fix gEDA/gaf bugs and/or implement feature requests</a></h3>
<div class="level3">
<p>
- There are several bugs listed at the gEDA/gaf bug tracker and feature request at the gEDA/gaf feature request tracker that could potentially make good student projects. Some of the bugs/feature requests are quite feasible to finish in one summer, while others are way beyond what is possible to finish in one summer. However some of the bugs/feature requests are trivial to implement, so several might need to be combined together to fill up the entire summer.
+
+There are several bugs listed at the gEDA/gaf bug tracker and feature request at the gEDA/gaf feature request tracker that could potentially make good student projects. Some of the bugs/feature requests are quite feasible to finish in one summer, while others are way beyond what is possible to finish in one summer. However some of the bugs/feature requests are trivial to implement, so several might need to be combined together to fill up the entire summer.
</p>
<p>
@@ -461,16 +440,17 @@ Difficulty = various
</p>
</div>
-<!-- SECTION "Fix gEDA/gaf bugs and/or implement feature requests" [13033-13938] -->
-<h3><a name="make_gsch2pcb_use_same_search_paths_as_pcb" id="make_gsch2pcb_use_same_search_paths_as_pcb">Make gsch2pcb use same search paths as PCB</a></h3>
+<!-- EDIT1526 SECTION "Fix gEDA/gaf bugs and/or implement feature requests" [13033-13938] -->
+<h3 class="sectionedit1527"><a name="make_gsch2pcb_use_same_search_paths_as_pcb" id="make_gsch2pcb_use_same_search_paths_as_pcb">Make gsch2pcb use same search paths as PCB</a></h3>
<div class="level3">
<p>
- Gsch2pcb is a key program in the gEDA Suite. It made it relatively easy to take a schematic drawn using gschem and prepare it for layout using PCB. It has played an important role in popularizing gEDA for PCB design amongst students and hobbyists. However, it has a flaw: It uses footprint search paths which can be different from those in PCB. Users are sometimes perplexed that they can see footprints in PCB, but gsch2pcb claims it canâ??t find them. Or gsch2pcb gives them footprints different from the ones they expect to see based upon a footprint search using PCB. In addition, gsch2pcb needs to be able to parse the PCB .pcb files directly. This means many file format changes trigger a required update to gsch2pcb.
+
+Gsch2pcb is a key program in the gEDA Suite. It made it relatively easy to take a schematic drawn using gschem and prepare it for layout using PCB. It has played an important role in popularizing gEDA for PCB design amongst students and hobbyists. However, it has a flaw: It uses footprint search paths which can be different from those in PCB. Users are sometimes perplexed that they can see footprints in PCB, but gsch2pcb claims it can't find them. Or gsch2pcb gives them footprints different from the ones they expect to see based upon a footprint search using PCB. In addition, gsch2pcb needs to be able to parse the PCB .pcb files directly. This means many file format changes trigger a required update to gsch2pcb.
</p>
<p>
-It would be more preferable for gsch2pcb to be able to query PCB through a well defined and stable <acronym title="Application Programming Interface">API</acronym> to find out the information it needs. In addition, rather than trying to duplicate PCBâ??s mechanism for creating a new board and locating footprints, gsch2pcb should simply instruct PCB to peform these operations. The goal is to provide a stable interface between the tools and impose appropriate abstraction barriers in between.
+It would be more preferable for gsch2pcb to be able to query PCB through a well defined and stable <acronym title="Application Programming Interface">API</acronym> to find out the information it needs. In addition, rather than trying to duplicate PCB's mechanism for creating a new board and locating footprints, gsch2pcb should simply instruct PCB to peform these operations. The goal is to provide a stable interface between the tools and impose appropriate abstraction barriers in between.
</p>
<p>
@@ -478,12 +458,13 @@ Difficulty = 2
</p>
</div>
-<!-- SECTION "Make gsch2pcb use same search paths as PCB" [13939-15164] -->
-<h3><a name="verilog_vhdl_code_generator_s_for_icarus_verilog" id="verilog_vhdl_code_generator_s_for_icarus_verilog">Verilog/VHDL code generator[s] for Icarus Verilog</a></h3>
+<!-- EDIT1527 SECTION "Make gsch2pcb use same search paths as PCB" [13939-15164] -->
+<h3 class="sectionedit1528"><a name="verilog_vhdl_code_generator_s_for_icarus_verilog" id="verilog_vhdl_code_generator_s_for_icarus_verilog">Verilog/VHDL code generator[s] for Icarus Verilog</a></h3>
<div class="level3">
<p>
- A Verilog code generator targets to emit simplified Verilog code. This has use as a Verilog â??reducerâ?? (or obfuscator) to translate verilog to more simplified forms. It can also be used to support other Verilog run time engines.
+
+A Verilog code generator targets to emit simplified Verilog code. This has use as a Verilog â??reducerâ?? (or obfuscator) to translate verilog to more simplified forms. It can also be used to support other Verilog run time engines.
</p>
<p>
@@ -491,7 +472,8 @@ A variant of this is to generate VHDL, and thus get a VHDL translation from the
</p>
<p>
-This task remains pretty clear of the core Icarus Verilog compiler and just works with loadable code generators. SDF Parser/Annotator for Icarus Verilog
+This task remains pretty clear of the core Icarus Verilog compiler and just works with loadable code generators.
+SDF Parser/Annotator for Icarus Verilog
</p>
<p>
@@ -503,22 +485,25 @@ The specify paths are now available in the vvp run time, some work is needed to
</p>
<p>
-This task can mostly be done in C and loaded as a VPI module. There is some work needed in the vvp run time engine to make the paths available to VPI modules, though. Macros with Arguments
+This task can mostly be done in C and loaded as a VPI module. There is some work needed in the vvp run time engine to make the paths available to VPI modules, though.
+Macros with Arguments
</p>
<p>
-The Icarus Verilog preprocessor currently does not support macros with arguments. A good task would be to add support for arguments. This task would work entirely within the ivlpp program that does the preprocessing for the ivl core. It is written in C and bison and would be a good task for someone not an expert in Verilog or EE in general. Upgrading/resurrecting the analog waveform viewer â??gwaveâ??
+The Icarus Verilog preprocessor currently does not support macros with arguments. A good task would be to add support for arguments. This task would work entirely within the ivlpp program that does the preprocessing for the ivl core. It is written in C and bison and would be a good task for someone not an expert in Verilog or EE in general.
+Upgrading/resurrecting the analog waveform viewer â??gwaveâ??
</p>
<p>
-In this project, you would work on improving and modernizing the analog waveform viewer â??gwaveâ??. Several improvements are desirable, including (but not limited to):
+In this project, you would work on improving and modernizing the analog waveform viewer â??gwaveâ??. Several improvements are desirable, including (but not limited to):
+
</p>
<ul>
<li class="level1"><div class="li"> Remove requirement for guile-gtk (which is basically dead I as far as I can tell).</div>
</li>
<li class="level2"><div class="li"> Adding support for hdf5 (as a way to help move towards a better than ascii format that is non proprietary).</div>
</li>
-<li class="level2"><div class="li"> Add a waveform calculator that lets you do things like add waveforms, do fftâ??s, etc.</div>
+<li class="level2"><div class="li"> Add a waveform calculator that lets you do things like add waveforms, do fft's, etc.</div>
</li>
<li class="level2"><div class="li"> Provide a way for the tool to be easily extensible by the user. Some examples are custom grid lines (smith, nichols, polar, etc), custom cursor functions (smith, nichols, etc), and complex measurement and waveform processing functions.</div>
</li>
@@ -527,7 +512,8 @@ In this project, you would work on improving and modernizing the analog waveform
</ul>
<p>
- Note that the gEDA Project needs a gwave mentor.
+
+Note that the gEDA Project needs a gwave mentor.
</p>
<p>
@@ -535,12 +521,13 @@ Difficulty = 3
</p>
</div>
-<!-- SECTION "Verilog/VHDL code generator[s] for Icarus Verilog" [15165-17735] -->
-<h3><a name="create_comprehensive_test_suite_for_entire_geda_suite" id="create_comprehensive_test_suite_for_entire_geda_suite">Create comprehensive test suite for entire gEDA Suite</a></h3>
+<!-- EDIT1528 SECTION "Verilog/VHDL code generator[s] for Icarus Verilog" [15165-17735] -->
+<h3 class="sectionedit1529"><a name="create_comprehensive_test_suite_for_entire_geda_suite" id="create_comprehensive_test_suite_for_entire_geda_suite">Create comprehensive test suite for entire gEDA Suite</a></h3>
<div class="level3">
<p>
- This project encompasses the functionality of the entire gEDA PCB design flow. You would develop a test framework for as much of these tools as possible. This likely means creating a large regression test suite. Some examples are sets of layouts (using PCB) that just barely pass and just barely fail each of the different DRC checks, generate BOMâ??s, x-y files, generate gerbers and maybe use gerbv to do a graphical xor against a â??goldenâ?? file. For gnetlist, reference netlists that have been placed into some canonical form should be generated from gschem schematics (.sch files).
+
+This project encompasses the functionality of the entire gEDA PCB design flow. You would develop a test framework for as much of these tools as possible. This likely means creating a large regression test suite. Some examples are sets of layouts (using PCB) that just barely pass and just barely fail each of the different DRC checks, generate BOM's, x-y files, generate gerbers and maybe use gerbv to do a graphical xor against a â??goldenâ?? file. For gnetlist, reference netlists that have been placed into some canonical form should be generated from gschem schematics (.sch files).
</p>
<p>
@@ -552,12 +539,13 @@ Difficulty = 3
</p>
</div>
-<!-- SECTION "Create comprehensive test suite for entire gEDA Suite" [17736-18599] -->
-<h3><a name="revive_tclspice_add_return_code_to_analysis" id="revive_tclspice_add_return_code_to_analysis">Revive TCLSpice, add return code to analysis</a></h3>
+<!-- EDIT1529 SECTION "Create comprehensive test suite for entire gEDA Suite" [17736-18599] -->
+<h3 class="sectionedit1530"><a name="revive_tclspice_add_return_code_to_analysis" id="revive_tclspice_add_return_code_to_analysis">Revive TCLSpice, add return code to analysis</a></h3>
<div class="level3">
<p>
- TCLSpice is a version of ngspice (the classic analog simulation program) in which the SPICE commands and cards have been exported to TCL. The idea is that you can then write a scripted SPICE analysis using TCL, a feature which is extremely valuable for performing circuit optimizations, repeated circuit simulations for Monte Carlo or corner-case evaluation, and so on.
+
+TCLSpice is a version of ngspice (the classic analog simulation program) in which the SPICE commands and cards have been exported to TCL. The idea is that you can then write a scripted SPICE analysis using TCL, a feature which is extremely valuable for performing circuit optimizations, repeated circuit simulations for Monte Carlo or corner-case evaluation, and so on.
</p>
<p>
@@ -569,12 +557,13 @@ Difficulty = 4
</p>
</div>
-<!-- SECTION "Revive TCLSpice, add return code to analysis" [18600-19345] -->
-<h3><a name="pcb_drc_interface_improvements" id="pcb_drc_interface_improvements">PCB DRC interface improvements</a></h3>
+<!-- EDIT1530 SECTION "Revive TCLSpice, add return code to analysis" [18600-19345] -->
+<h3 class="sectionedit1531"><a name="pcb_drc_interface_improvements" id="pcb_drc_interface_improvements">PCB DRC interface improvements</a></h3>
<div class="level3">
<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.
+
+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>
@@ -582,12 +571,13 @@ Difficulty = 2
</p>
</div>
-<!-- SECTION "PCB DRC interface improvements" [19346-19687] -->
-<h3><a name="add_enhancements_to_gerbv" id="add_enhancements_to_gerbv">Add enhancements to gerbv.</a></h3>
+<!-- EDIT1531 SECTION "PCB DRC interface improvements" [19346-19687] -->
+<h3 class="sectionedit1532"><a name="add_enhancements_to_gerbv" id="add_enhancements_to_gerbv">Add enhancements to gerbv.</a></h3>
<div class="level3">
<p>
- Gerbv is gEDAâ??s Gerber viewer. It is a good tool for inspecting Gerbers. Adding a different pop-up box displaying the properties of objects you click on (i.e. round pad diameters, track widths, etc.) would be invaluable.
+
+Gerbv is gEDA's Gerber viewer. It is a good tool for inspecting Gerbers. Adding a different pop-up box displaying the properties of objects you click on (i.e. round pad diameters, track widths, etc.) would be invaluable.
</p>
<p>
@@ -595,12 +585,13 @@ Difficulty = ?
</p>
</div>
-<!-- SECTION "Add enhancements to gerbv." [19688-19963] -->
-<h3><a name="pcb_autorouter" id="pcb_autorouter">PCB Autorouter</a></h3>
+<!-- EDIT1532 SECTION "Add enhancements to gerbv." [19688-19963] -->
+<h3 class="sectionedit1533"><a name="pcb_autorouter" id="pcb_autorouter">PCB Autorouter</a></h3>
<div class="level3">
<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.
+
+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>
@@ -608,12 +599,13 @@ Difficulty = 5
</p>
</div>
-<!-- SECTION "PCB Autorouter" [19964-20246] -->
-<h3><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></h3>
+<!-- EDIT1533 SECTION "PCB Autorouter" [19964-20246] -->
+<h3 class="sectionedit1534"><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></h3>
<div class="level3">
<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.
+
+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>
@@ -621,12 +613,13 @@ Difficulty = 3
</p>
</div>
-<!-- SECTION "Improved and formalized mechanism for forward/backward annotation" [20247-20650] -->
-<h3><a name="ipc_footprint_calculator" id="ipc_footprint_calculator">IPC Footprint Calculator</a></h3>
+<!-- EDIT1534 SECTION "Improved and formalized mechanism for forward/backward annotation" [20247-20650] -->
+<h3 class="sectionedit1535"><a name="ipc_footprint_calculator" id="ipc_footprint_calculator">IPC Footprint Calculator</a></h3>
<div class="level3">
<p>
- Build a footprint calculator that can take the IPC rules and produce a pcb footprint. Preferably write this in a way where the core program is independent of a gui so that you can script it for generating entire large families of footprints or hook it up to a <acronym title="Graphical User Interface">GUI</acronym> of choice (lesstif, gtk, maybe even cgi). Would require the purchase of IPC-7351 (approximately U.S.A. $100)and verifying that one is allowed to produce such a calculator.
+
+Build a footprint calculator that can take the IPC rules and produce a pcb footprint. Preferably write this in a way where the core program is independent of a gui so that you can script it for generating entire large families of footprints or hook it up to a <acronym title="Graphical User Interface">GUI</acronym> of choice (lesstif, gtk, maybe even cgi). Would require the purchase of IPC-7351 (approximately U.S.A. $100)and verifying that one is allowed to produce such a calculator.
</p>
<p>
@@ -634,5 +627,5 @@ Difficulty = 2
</p>
</div>
-<!-- SECTION "IPC Footprint Calculator" [20651-] --></body>
+<!-- EDIT1535 SECTION "IPC Footprint Calculator" [20651-] --></body>
</html>
diff --git a/docs/wiki/gsoc2008.html b/docs/wiki/gsoc2008.html
index 04e07a2..aecec65 100644
--- a/docs/wiki/gsoc2008.html
+++ b/docs/wiki/gsoc2008.html
@@ -11,61 +11,49 @@
</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_2008" class="toc">Google Summer of Code 2008</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="#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_2008" id="google_summer_of_code_2008">Google Summer of Code 2008</a></h3>
+<h3 class="sectionedit1536"><a name="google_summer_of_code_2008" id="google_summer_of_code_2008">Google Summer of Code 2008</a></h3>
<div class="level3">
<p>
-The gEDA Project has been accepted into the <a href="http://code.google.com/soc/2008/"; class="urlextern" title="http://code.google.com/soc/2008/"; rel="nofollow">Google's Summer of Code</a> 2008 program! The gEDA project is excited to have this opportunity again (second 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 2008 activities.
+The gEDA Project has been accepted into the <a href="http://code.google.com/soc/2008/"; class="urlextern" title="http://code.google.com/soc/2008/"; rel="nofollow">Google's Summer of Code</a> 2008 program!
+The gEDA project is excited to have this opportunity again (second 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 2008 activities.
</p>
</div>
-<!-- SECTION "Google Summer of Code 2008" [1-386] -->
-<h3><a name="suggested_projects" id="suggested_projects">Suggested Projects</a></h3>
+<!-- EDIT1536 SECTION "Google Summer of Code 2008" [1-386] -->
+<h3 class="sectionedit1537"><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="gsoc2008_projects.html" class="wikilink1" title="gsoc2008_projects.html">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>
-<!-- SECTION "Suggested Projects" [387-546] -->
-<h3><a name="what_we_ask_from_students" id="what_we_ask_from_students">What we ask from Students</a></h3>
+<!-- EDIT1537 SECTION "Suggested Projects" [387-546] -->
+<h3 class="sectionedit1538"><a name="what_we_ask_from_students" id="what_we_ask_from_students">What we ask from Students</a></h3>
<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.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>)
+
+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>
</div>
-<!-- SECTION "What we ask from Students" [547-989] -->
-<h3><a name="mentors_and_administrators" id="mentors_and_administrators">Mentors and Administrators</a></h3>
+<!-- EDIT1538 SECTION "What we ask from Students" [547-989] -->
+<h3 class="sectionedit1539"><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 2008. Please feel free to contact any of us with any questions you may have.
+
+Here is a list of mentors and administrators for the gEDA Project's GSoC in 2008. Please feel free to contact any of us with any questions you may have.
</p>
</div>
@@ -107,5 +95,5 @@ students</a> to help make the GSoC experience a success for everybody. (<a href=
</ul>
</div>
-<!-- SECTION "Mentors and Administrators" [990-] --></body>
+<!-- EDIT1539 SECTION "Mentors and Administrators" [990-] --></body>
</html>
diff --git a/docs/wiki/gsoc2008_projects.html b/docs/wiki/gsoc2008_projects.html
index 22c3f3a..059082b 100644
--- a/docs/wiki/gsoc2008_projects.html
+++ b/docs/wiki/gsoc2008_projects.html
@@ -11,102 +11,86 @@
</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_2008_project_ideas" class="toc">gEDA GSoC 2008 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="#pcb_layout_editor" class="toc">PCB Layout Editor</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="#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="#gerbv" class="toc">Gerbv</a></span></div></li></ul>
-</li></ul>
-</li></ul>
-</div>
-</div>
-
-
-<h3><a name="geda_gsoc_2008_project_ideas" id="geda_gsoc_2008_project_ideas">gEDA GSoC 2008 Project Ideas</a></h3>
+<h3 class="sectionedit1540"><a name="geda_gsoc_2008_project_ideas" id="geda_gsoc_2008_project_ideas">gEDA GSoC 2008 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!
+
+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 2008 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>
+<!-- EDIT1540 SECTION "gEDA GSoC 2008 Project Ideas" [1-320] -->
+<h3 class="sectionedit1541"><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>
+
+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-458] -->
-<h3><a name="gnucap_circuit_simulation_analysis_program" id="gnucap_circuit_simulation_analysis_program">Gnucap circuit simulation/analysis program</a></h3>
+<!-- EDIT1541 SECTION "General, glue and related gaf projects" [321-458] -->
+<h3 class="sectionedit1542"><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>
+
+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" [459-624] -->
-<h3><a name="pcb_layout_editor" id="pcb_layout_editor">PCB Layout Editor</a></h3>
+<!-- EDIT1542 SECTION "Gnucap circuit simulation/analysis program" [459-624] -->
+<h3 class="sectionedit1543"><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>
+
+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" [625-715] -->
-<h3><a name="gwave_--_analog_waveform_viewer" id="gwave_--_analog_waveform_viewer">Gwave -- analog waveform viewer</a></h3>
+<!-- EDIT1543 SECTION "PCB Layout Editor" [625-715] -->
+<h3 class="sectionedit1544"><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>
+
+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" [716-824] -->
-<h3><a name="gschem_schematic_capture_tool" id="gschem_schematic_capture_tool">Gschem schematic capture tool</a></h3>
+<!-- EDIT1544 SECTION "Gwave -- analog waveform viewer" [716-824] -->
+<h3 class="sectionedit1545"><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>
+
+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-934] -->
-<h3><a name="icarus_verilog" id="icarus_verilog">Icarus Verilog</a></h3>
+<!-- EDIT1545 SECTION "Gschem schematic capture tool" [825-934] -->
+<h3 class="sectionedit1546"><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>
+
+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" [935-1060] -->
-<h3><a name="gerbv" id="gerbv">Gerbv</a></h3>
+<!-- EDIT1546 SECTION "Icarus Verilog" [935-1060] -->
+<h3 class="sectionedit1547"><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>
+
+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-] --></body>
+<!-- EDIT1547 SECTION "Gerbv" [1061-] --></body>
</html>
diff --git a/docs/wiki/gsoc2009.html b/docs/wiki/gsoc2009.html
index f9bf230..63635a2 100644
--- a/docs/wiki/gsoc2009.html
+++ b/docs/wiki/gsoc2009.html
@@ -11,30 +11,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>
+<h3 class="sectionedit1548"><a name="google_summer_of_code_2009" id="google_summer_of_code_2009">Google Summer of Code 2009</a></h3>
<div class="level3">
<p>
@@ -42,26 +20,32 @@ The gEDA Project has (not yet!!!) been accepted into the <a href="http://code.go
</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.
+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>
+<!-- EDIT1548 SECTION "Google Summer of Code 2009" [1-538] -->
+<h3 class="sectionedit1549"><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>.
+
+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>
+<!-- EDIT1549 SECTION "Suggested Projects" [539-704] -->
+<h3 class="sectionedit1550"><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!
+
+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>
@@ -70,8 +54,8 @@ 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>
+<!-- EDIT1550 SECTION "What we ask from Students" [705-1486] -->
+<h3 class="sectionedit1551"><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>
@@ -81,12 +65,13 @@ students</a> to help make the GSoC experience a success for everybody.
</ul>
</div>
-<!-- SECTION "Archived project info" [1487-1706] -->
-<h3><a name="mentors_and_administrators" id="mentors_and_administrators">Mentors and Administrators</a></h3>
+<!-- EDIT1551 SECTION "Archived project info" [1487-1706] -->
+<h3 class="sectionedit1552"><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.
+
+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>
@@ -130,5 +115,5 @@ students</a> to help make the GSoC experience a success for everybody.
</ul>
</div>
-<!-- SECTION "Mentors and Administrators" [1707-] --></body>
+<!-- EDIT1552 SECTION "Mentors and Administrators" [1707-] --></body>
</html>
diff --git a/docs/wiki/gsoc2009_projects.html b/docs/wiki/gsoc2009_projects.html
index e3157dd..3e04c12 100644
--- a/docs/wiki/gsoc2009_projects.html
+++ b/docs/wiki/gsoc2009_projects.html
@@ -11,112 +11,96 @@
</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>
+<h3 class="sectionedit1553"><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!
+
+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>
+<!-- EDIT1553 SECTION "gEDA GSoC 2009 Project Ideas" [1-320] -->
+<h3 class="sectionedit1554"><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>
+
+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>
+<!-- EDIT1554 SECTION "General, glue and related gaf projects" [321-457] -->
+<h3 class="sectionedit1555"><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>
+
+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>
+<!-- EDIT1555 SECTION "Gnucap circuit simulation/analysis program" [458-623] -->
+<h3 class="sectionedit1556"><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>
+
+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>
+<!-- EDIT1556 SECTION "Gwave analog waveform viewer" [624-732] -->
+<h3 class="sectionedit1557"><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>
+
+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>
+<!-- EDIT1557 SECTION "PCB Layout Editor" [733-824] -->
+<h3 class="sectionedit1558"><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>
+
+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>
+<!-- EDIT1558 SECTION "Gschem schematic capture tool" [825-935] -->
+<h3 class="sectionedit1559"><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>
+
+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>
+<!-- EDIT1559 SECTION "Icarus Verilog" [936-1062] -->
+<h3 class="sectionedit1560"><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>
+
+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>
+<!-- EDIT1560 SECTION "GTKWave" [1063-1159] -->
+<h3 class="sectionedit1561"><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>
+
+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>
+<!-- EDIT1561 SECTION "Gerbv" [1160-] --></body>
</html>
diff --git a/docs/wiki/gsoc2010.html b/docs/wiki/gsoc2010.html
new file mode 100644
index 0000000..3728373
--- /dev/null
+++ b/docs/wiki/gsoc2010.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>
+
+
+<h3 class="sectionedit1602"><a name="google_summer_of_code_2010" id="google_summer_of_code_2010">Google Summer of Code 2010</a></h3>
+<div class="level3">
+
+<p>
+The gEDA Project is going to apply for the <a href="http://code.google.com/soc/"; class="urlextern" title="http://code.google.com/soc/"; rel="nofollow">Google's Summer of Code</a> 2010 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 2010.
+</p>
+
+<p>
+The gEDA project is excited to have this opportunity again and thanks Google for investing in and organizing the GSoC program. This wiki page will develop as we plan our GSoC 2010 activities.
+</p>
+
+</div>
+<!-- EDIT1602 SECTION "Google Summer of Code 2010" [1-487] -->
+<h3 class="sectionedit1603"><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="gsoc2010_projects.html" class="wikilink1" title="gsoc2010_projects.html">list of suggested projects</a>.
+</p>
+
+</div>
+<!-- EDIT1603 SECTION "Suggested Projects" [488-647] -->
+<h3 class="sectionedit1604"><a name="what_we_ask_from_students" id="what_we_ask_from_students">What we ask from Students</a></h3>
+<div class="level3">
+
+<p>
+
+2010 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>
+<!-- EDIT1604 SECTION "What we ask from Students" [648-1429] -->
+<h3 class="sectionedit1605"><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>
+<!-- EDIT1605 SECTION "Archived project info" [1430-1649] -->
+<h3 class="sectionedit1606"><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 2010. 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"> Peter Brett (peter (AT) peter-b (DOT) co (DOT) uk) - <strong>gEDA/gaf</strong></div>
+</li>
+<li class="level2"><div class="li"> Harry Eaton (bumpelo (AT) gmail (DOT) com) - <strong>PCB</strong></div>
+</li>
+<li class="level2"><div class="li"> DJ Delorie (dj (AT) delorie (DOT) com) - <strong>PCB</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"> Al Davis (ad252 (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>
+</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) - <strong>Primary GSoC admin</strong></div>
+</li>
+<li class="level2"><div class="li"> Ales Hvezda (ahvezda (AT) moria (DOT) seul (DOT) org) - <strong>Back-up GSoC admin</strong></div>
+</li>
+</ul>
+
+</div>
+<!-- EDIT1606 SECTION "Mentors and Administrators" [1650-] --></body>
+</html>
diff --git a/docs/wiki/gsoc2010_projects.html b/docs/wiki/gsoc2010_projects.html
new file mode 100644
index 0000000..016dd8e
--- /dev/null
+++ b/docs/wiki/gsoc2010_projects.html
@@ -0,0 +1,85 @@
+<!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 class="sectionedit1607"><a name="geda_gsoc_2010_project_ideas" id="geda_gsoc_2010_project_ideas">gEDA GSoC 2010 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>
+<!-- EDIT1607 SECTION "gEDA GSoC 2010 Project Ideas" [1-320] -->
+<h3 class="sectionedit1608"><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>
+<!-- EDIT1608 SECTION "General, glue and related gaf projects" [321-456] -->
+<h3 class="sectionedit1609"><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>
+<!-- EDIT1609 SECTION "Gschem schematic capture tool" [457-566] -->
+<h3 class="sectionedit1610"><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>
+<!-- EDIT1610 SECTION "PCB Layout Editor" [567-657] -->
+<h3 class="sectionedit1611"><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>
+<!-- EDIT1611 SECTION "Gnucap circuit simulation/analysis program" [658-823] -->
+<h3 class="sectionedit1612"><a name="gerbv_gerber_viewer" id="gerbv_gerber_viewer">Gerbv Gerber viewer</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>
+<!-- EDIT1612 SECTION "Gerbv Gerber viewer" [824-920] -->
+<h3 class="sectionedit1613"><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>
+<!-- EDIT1613 SECTION "Gwave analog waveform viewer" [921-] --></body>
+</html>
diff --git a/docs/wiki/gtkwave-projects.html b/docs/wiki/gtkwave-projects.html
index 74ba1d3..24693e5 100644
--- a/docs/wiki/gtkwave-projects.html
+++ b/docs/wiki/gtkwave-projects.html
@@ -12,12 +12,10 @@
<body>
-
-
-<h3><a name="gtkwave_projects" id="gtkwave_projects">GTKWave projects</a></h3>
+<h3 class="sectionedit1562"><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 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>
@@ -29,7 +27,7 @@
</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 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>
diff --git a/docs/wiki/gwave-projects.html b/docs/wiki/gwave-projects.html
index 78d0530..59438fe 100644
--- a/docs/wiki/gwave-projects.html
+++ b/docs/wiki/gwave-projects.html
@@ -12,13 +12,12 @@
<body>
-
-
-<h3><a name="gwave_--_analog_waveform_viewer" id="gwave_--_analog_waveform_viewer">Gwave -- analog waveform viewer</a></h3>
+<h3 class="sectionedit1563"><a name="gwave_--_analog_waveform_viewer" id="gwave_--_analog_waveform_viewer">Gwave -- analog waveform viewer</a></h3>
<div class="level3">
<p>
- Gwave is an analog waveform viewer which is used to view the output files produced by ngspice or gnucap. Here are some feature suggestions. You might choose a large handful of features to implement as your GSoC project.
+
+Gwave is an analog waveform viewer which is used to view the output files produced by ngspice or gnucap. Here are some feature suggestions. You might choose a large handful of features to implement as your GSoC project.
</p>
</div>
@@ -27,16 +26,21 @@
<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.
+
+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>
+<h5><a name="developing_unit_tests_for_gtk_-20" id="developing_unit_tests_for_gtk_-20">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.
+
+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>
diff --git a/docs/wiki/images/Makefile.am b/docs/wiki/images/Makefile.am
index c971ff5..b8db727 100644
--- a/docs/wiki/images/Makefile.am
+++ b/docs/wiki/images/Makefile.am
@@ -3,9 +3,9 @@
docname=wiki
docsdir = $(docdir)/$(docname)/images
-SUBDIRS = interwiki smileys
+SUBDIRS = smileys interwiki
-docs_DATA = interwiki.png link_icon.gif button-dw.png open.gif button-php.gif windows.gif button-rss.png bullet.gif button-donate.gif mail_icon.gif button-cc.gif tocdot2.gif closed.gif button-css.png button-xhtml.png
+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)
diff --git a/docs/wiki/images/interwiki/Makefile.am b/docs/wiki/images/interwiki/Makefile.am
index 0723035..a294f2c 100644
--- a/docs/wiki/images/interwiki/Makefile.am
+++ b/docs/wiki/images/interwiki/Makefile.am
@@ -3,7 +3,7 @@
docname=wiki
docsdir = $(docdir)/$(docname)/images/interwiki
-docs_DATA = wiki.gif wpde.gif google.gif phpfn.gif amazon.de.gif meatball.gif wpmeta.gif amazon.uk.gif sb.gif wp.gif amazon.gif coral.gif bug.gif doku.gif
+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)
diff --git a/docs/wiki/images/smileys/Makefile.am b/docs/wiki/images/smileys/Makefile.am
index 77e5024..2e01243 100644
--- a/docs/wiki/images/smileys/Makefile.am
+++ b/docs/wiki/images/smileys/Makefile.am
@@ -3,7 +3,7 @@
docname=wiki
docsdir = $(docdir)/$(docname)/images/smileys
-docs_DATA = icon_arrow.gif icon_biggrin.gif fixme.gif delete.gif icon_idea.gif icon_cry.gif icon_lol.gif icon_evil.gif icon_question.gif icon_mrgreen.gif icon_confused.gif icon_smile2.gif icon_silenced.gif icon_smile.gif icon_twisted.gif icon_redface.gif icon_sad.gif icon_wink.gif icon_fun.gif icon_kaddi.gif icon_exclaim.gif icon_surprised.gif icon_doubt.gif icon_doubt2.gif icon_razz.gif icon_frown.gif icon_cool.gif icon_eek.gif icon_neutral.gif icon_rolleyes.gif
+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)
diff --git a/docs/wiki/index.html b/docs/wiki/index.html
index 19d0714..b68edad 100644
--- a/docs/wiki/index.html
+++ b/docs/wiki/index.html
@@ -11,55 +11,36 @@
</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_quick_reference" class="toc">FAQs & Quick Reference</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>
+<h1 class="sectionedit1582"><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>
+<!-- EDIT1582 SECTION "gEDA Project Wiki" [2-34] -->
+<h2 class="sectionedit1583"><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.
+
+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.
+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>.
+All of the software in the gEDA suite can be found on the <a href="geda-download.html" class="wikilink1" title="geda-download.html">download</a> page.
</p>
</div>
-<!-- SECTION "What is gEDA?" [36-1176] -->
-<h2><a name="official_project_documentation" id="official_project_documentation">Official Project documentation</a></h2>
+<!-- EDIT1583 SECTION "What is gEDA?" [35-1144] -->
+<h2 class="sectionedit1584"><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.
+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> : Contains links to tutorials, manuals, HOWTOs and format specifications of the gEDA suite. </div>
@@ -67,12 +48,13 @@ These are the official project docs. They have been converted from LaTeX and <a
</ul>
</div>
-<!-- SECTION "Official Project documentation" [1177-1516] -->
-<h2><a name="faqs_quick_reference" id="faqs_quick_reference">FAQs & Quick Reference</a></h2>
+<!-- EDIT1584 SECTION "Official Project documentation" [1145-1484] -->
+<h2 class="sectionedit1585"><a name="faqs_quick_reference" id="faqs_quick_reference">FAQs & Quick Reference</a></h2>
<div class="level2">
<p>
-These are informal 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.
+These are informal 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>
@@ -81,7 +63,9 @@ These are informal FAQs, HOWTOs, and tips/tricks to help you with the practical
</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 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-howto_report_bugs.html" class="wikilink1" title="geda-howto_report_bugs.html">Howto report bugs</a></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>
@@ -93,13 +77,13 @@ These are informal FAQs, HOWTOs, and tips/tricks to help you with the practical
</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_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-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 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-gschem_symbol_creation.html" class="wikilink1" title="geda-gschem_symbol_creation.html">gschem Symbol Creation</a> : gschem symbol creation guide.</div>
</li>
@@ -108,55 +92,59 @@ These are informal FAQs, HOWTOs, and tips/tricks to help you with the practical
</ul>
</div>
-<!-- SECTION "FAQs & Quick Reference" [1517-3035] -->
-<h2><a name="developer_documentation" id="developer_documentation">Developer Documentation</a></h2>
+<!-- EDIT1585 SECTION "FAQs & Quick Reference" [1485-3037] -->
+<h2 class="sectionedit1586"><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:
+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 class="level1"><div class="li"> <a href="geda-developer.html" class="wikilink1" title="geda-developer.html"> developer </a> : Code repository, developer mailing list and building information.</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 class="level1"><div class="li"> <a href="geda-todos.html" class="wikilink1" title="geda-todos.html">Todos</a> : 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 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 class="level1"><div class="li"> <a href="geda-devel-tips.html" class="wikilink1" title="geda-devel-tips.html">devel-tips</a> : Various tips and tricks when doing gEDA development.</div>
</li>
</ul>
<p>
- The following pages are work-in-progress discussions and/or brainstorming:
+
+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 class="level1"><div class="li"> <a href="libgeda3.html" class="wikilink1" title="libgeda3.html">libgeda3</a> : 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 class="level1"><div class="li"> <a href="geda-circuit_simulation_improvements.html" class="wikilink1" title="geda-circuit_simulation_improvements.html">Circuit Simulation Improvements</a> : 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 class="level1"><div class="li"> <a href="geda-data_plotting_improvements.html" class="wikilink1" title="geda-data_plotting_improvements.html">Data Plotting Improvements</a> : 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 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> : 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>
-<li class="level1"><div class="li"> <a href="geda-gparts_dd.html" class="wikilink1" title="geda-gparts_dd.html">Parts Manager</a> : A working document for a gEDA parts manager</div>
+<li class="level1"><div class="li"> <a href="geda-gparts_tc.html" class="wikilink1" title="geda-gparts_tc.html">Parts Manager</a> : A working document for a gEDA parts manager</div>
</li>
</ul>
</div>
-<!-- SECTION "Developer Documentation" [3036-4598] -->
-<h2><a name="talks" id="talks">Talks</a></h2>
+<!-- EDIT1586 SECTION "Developer Documentation" [3038-4443] -->
+<h2 class="sectionedit1587"><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.
+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>
@@ -164,35 +152,33 @@ These are slides of presentations done about gEDA. They provide a good top-leve
</ul>
</div>
-<!-- SECTION "Talks" [4599-4839] -->
-<h2><a name="google_summer_of_code" id="google_summer_of_code">Google Summer of Code</a></h2>
+<!-- EDIT1587 SECTION "Talks" [4444-4686] -->
+<h2 class="sectionedit1588"><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:
+The gEDA project has participated in the Google Summer of Code.
</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:
+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>
+<li class="level1"><div class="li"> <a href="gsoc2009.html" class="wikilink1" title="gsoc2009.html">2009</a> (gEDA did not participate in 2009)</div>
+</li>
+<li class="level1"><div class="li"> <a href="gsoc2010.html" class="wikilink1" title="gsoc2010.html">2010</a> (gEDA did not participate in 2010)</div>
+</li>
</ul>
</div>
-<!-- SECTION "Google Summer of Code" [4840-5219] -->
-<h2><a name="translations" id="translations">Translations</a></h2>
+<!-- EDIT1588 SECTION "Google Summer of Code" [4687-5015] -->
+<h2 class="sectionedit1589"><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>
@@ -202,12 +188,12 @@ Here is this yearâ??s Google Summer of Code page:
</ul>
</div>
-<!-- SECTION "Translations" [5220-5336] -->
-<h2><a name="geda_users" id="geda_users">gEDA Users</a></h2>
+<!-- EDIT1589 SECTION "Translations" [5016-5133] -->
+<h2 class="sectionedit1590"><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>.
+Users may discuss development, help, installation, and working tips through the <a href="geda-mailinglists.html" class="wikilink1" title="geda-mailinglists.html">mailinglists</a>.
</p>
<p>
@@ -219,8 +205,8 @@ The so-called â??Free Dogâ?? organization ( <a href="http://freeedaug.org/"; clas
</p>
</div>
-<!-- SECTION "gEDA Users" [5337-5869] -->
-<h2><a name="about_this_wiki" id="about_this_wiki">About this Wiki</a></h2>
+<!-- EDIT1590 SECTION "gEDA Users" [5134-5632] -->
+<h2 class="sectionedit1591"><a name="about_this_wiki" id="about_this_wiki">About this Wiki</a></h2>
<div class="level2">
<p>
@@ -228,9 +214,10 @@ 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" [5870-] --></body>
+<!-- EDIT1591 SECTION "About this Wiki" [5633-] --></body>
</html>
diff --git a/docs/wiki/libgeda3.html b/docs/wiki/libgeda3.html
index 094f657..c74a2fe 100644
--- a/docs/wiki/libgeda3.html
+++ b/docs/wiki/libgeda3.html
@@ -11,48 +11,22 @@
</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_library_v3_specification" class="toc">gEDA Library v3 Specification</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="#requirements" class="toc">Requirements</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#core" class="toc">Core</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#secondary" class="toc">Secondary</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#coordinate_system" class="toc">Coordinate System</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#configuration" class="toc">Configuration</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#dependencies" class="toc">Dependencies</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#glib" class="toc">glib</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#gobject" class="toc">gobject</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#references" class="toc">References</a></span></div></li></ul>
-</li></ul>
-</div>
-</div>
-
-
-<h1><a name="geda_library_v3_specification" id="geda_library_v3_specification">gEDA Library v3 Specification</a></h1>
+<h1 class="sectionedit1564"><a name="geda_library_v3_specification" id="geda_library_v3_specification">gEDA Library v3 Specification</a></h1>
<div class="level1">
</div>
-<!-- SECTION "gEDA Library v3 Specification" [1-45] -->
-<h2><a name="rationale" id="rationale">Rationale</a></h2>
+<!-- EDIT1564 SECTION "gEDA Library v3 Specification" [1-45] -->
+<h2 class="sectionedit1565"><a name="rationale" id="rationale">Rationale</a></h2>
<div class="level2">
<p>
- The current version (2.x) of the libgeda shared library has a number of defects:
+
+The current version (2.x) of the libgeda shared library has a number of defects:
+
</p>
<ul>
-<li class="level1"><div class="li"> Poor separation between public interface and internals, which leads to…</div>
+<li class="level1"><div class="li"> Poor separation between public interface and internals, which leads toâ?¦</div>
</li>
<li class="level1"><div class="li"> Frequent changes to the <acronym title="Application Programming Interface">API</acronym></div>
</li>
@@ -61,7 +35,9 @@
</ul>
<p>
- This page is an attempt to itemise in detail what is required of libgeda, and what the interface to it should look like. This will enable:
+
+This page is an attempt to itemise in detail what is required of libgeda, and what the interface to it should look like. This will enable:
+
</p>
<ul>
<li class="level1"><div class="li"> More rigorous testing of library functions</div>
@@ -73,13 +49,13 @@
</ul>
</div>
-<!-- SECTION "Rationale" [46-643] -->
-<h2><a name="requirements" id="requirements">Requirements</a></h2>
+<!-- EDIT1565 SECTION "Rationale" [46-643] -->
+<h2 class="sectionedit1566"><a name="requirements" id="requirements">Requirements</a></h2>
<div class="level2">
</div>
-<!-- SECTION "Requirements" [644-669] -->
-<h3><a name="core" id="core">Core</a></h3>
+<!-- EDIT1566 SECTION "Requirements" [644-669] -->
+<h3 class="sectionedit1567"><a name="core" id="core">Core</a></h3>
<div class="level3">
<ol>
<li class="level1"><div class="li"> Define data structures for representing schematics</div>
@@ -90,13 +66,13 @@
</li>
<li class="level1"><div class="li"> Provide access to detailed data on errors and exceptions</div>
</li>
-<li class="level1"><div class="li"> Provide a simple interface for configuring libgedaâ??s behaviour</div>
+<li class="level1"><div class="li"> Provide a simple interface for configuring libgeda's behaviour</div>
</li>
</ol>
</div>
-<!-- SECTION "Core" [670-1013] -->
-<h3><a name="secondary" id="secondary">Secondary</a></h3>
+<!-- EDIT1567 SECTION "Core" [670-1013] -->
+<h3 class="sectionedit1568"><a name="secondary" id="secondary">Secondary</a></h3>
<div class="level3">
<ol>
<li class="level1"><div class="li"> Make no assumptions about applications which will use the library</div>
@@ -112,25 +88,28 @@
</ol>
</div>
-<!-- SECTION "Secondary" [1014-1367] -->
-<h2><a name="coordinate_system" id="coordinate_system">Coordinate System</a></h2>
+<!-- EDIT1568 SECTION "Secondary" [1014-1367] -->
+<h2 class="sectionedit1569"><a name="coordinate_system" id="coordinate_system">Coordinate System</a></h2>
<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.html">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>
-<!-- SECTION "Coordinate System" [1368-1659] -->
-<h2><a name="configuration" id="configuration">Configuration</a></h2>
+<!-- EDIT1569 SECTION "Coordinate System" [1368-1659] -->
+<h2 class="sectionedit1570"><a name="configuration" id="configuration">Configuration</a></h2>
<div class="level2">
<p>
- Currently, libgeda relies on an embedded Scheme interpreter (<a href="http://www.gnu.org/software/guile/"; class="urlextern" title="http://www.gnu.org/software/guile/"; rel="nofollow">Guile</a>) for configuring settings such as library search paths. This has a number of pros and cons:
+
+Currently, libgeda relies on an embedded Scheme interpreter (<a href="http://www.gnu.org/software/guile/"; class="urlextern" title="http://www.gnu.org/software/guile/"; rel="nofollow">Guile</a>) for configuring settings such as library search paths. This has a number of pros and cons:
</p>
<p>
-Pros:
+Pros:
+
</p>
<ul>
<li class="level1"><div class="li"> All applications which access libgeda can automatically use the same settings</div>
@@ -140,12 +119,14 @@ Pros:
</ul>
<p>
- Cons:
+
+Cons:
+
</p>
<ul>
<li class="level1"><div class="li"> Large & complex dependency</div>
</li>
-<li class="level1"><div class="li"> Doesnâ??t integrate nicely into applications which use e.g. the GNOME or KDE configuration mechanisms</div>
+<li class="level1"><div class="li"> Doesn't integrate nicely into applications which use e.g. the GNOME or KDE configuration mechanisms</div>
</li>
<li class="level1"><div class="li"> Substantially complicates the creation of graphical user interfaces for configuring library settings</div>
</li>
@@ -154,42 +135,47 @@ Pros:
</ul>
<p>
- It might, therefore, make more sense to provide a complete <acronym title="Application Programming Interface">API</acronym> for configuring libgeda, and rely on the application to handle the storage and loading of the configuration.
+
+It might, therefore, make more sense to provide a complete <acronym title="Application Programming Interface">API</acronym> for configuring libgeda, and rely on the application to handle the storage and loading of the configuration.
</p>
</div>
-<!-- SECTION "Configuration" [1660-2523] -->
-<h2><a name="dependencies" id="dependencies">Dependencies</a></h2>
+<!-- EDIT1570 SECTION "Configuration" [1660-2523] -->
+<h2 class="sectionedit1571"><a name="dependencies" id="dependencies">Dependencies</a></h2>
<div class="level2">
</div>
-<!-- SECTION "Dependencies" [2524-2549] -->
-<h3><a name="glib" id="glib">glib</a></h3>
+<!-- EDIT1571 SECTION "Dependencies" [2524-2549] -->
+<h3 class="sectionedit1572"><a name="glib" id="glib">glib</a></h3>
<div class="level3">
<p>
- <a href="http://developer.gnome.org/doc/API/glib/"; class="urlextern" title="http://developer.gnome.org/doc/API/glib/"; rel="nofollow">glib</a> provides a very large number of useful features that would make writing and maintaining libgeda easier. These include:
+
+<a href="http://developer.gnome.org/doc/API/glib/"; class="urlextern" title="http://developer.gnome.org/doc/API/glib/"; rel="nofollow">glib</a> provides a very large number of useful features that would make writing and maintaining libgeda easier. These include:
+
</p>
<ul>
<li class="level1"><div class="li"> Portable definitions of basic types (although <code>intptr.h</code> does this too, and would probably be preferable)</div>
</li>
<li class="level1"><div class="li"> Doubly- and singly-linked lists, and many other data structures</div>
</li>
-<li class="level1"><div class="li"> Plugin loading, memory allocation, threading, IO abstraction, …</div>
+<li class="level1"><div class="li"> Plugin loading, memory allocation, threading, IO abstraction, â?¦</div>
</li>
</ul>
<p>
- Not having to reinvent the wheel – and letting a much larger project be responsible for optimising and maintaining these features – would make the libgeda code smaller and easier to understand and maintain. libgeda already uses glib to a certain extent, but using it more extensively in future versions of libgeda does not immediately seem to be a bad idea.
+
+Not having to reinvent the wheel â?? and letting a much larger project be responsible for optimising and maintaining these features â?? would make the libgeda code smaller and easier to understand and maintain. libgeda already uses glib to a certain extent, but using it more extensively in future versions of libgeda does not immediately seem to be a bad idea.
</p>
</div>
-<!-- SECTION "glib" [2550-3350] -->
-<h3><a name="gobject" id="gobject">gobject</a></h3>
+<!-- EDIT1572 SECTION "glib" [2550-3350] -->
+<h3 class="sectionedit1573"><a name="gobject" id="gobject">gobject</a></h3>
<div class="level3">
<p>
- <a href="http://developer.gnome.org/doc/API/2.0/gobject/"; class="urlextern" title="http://developer.gnome.org/doc/API/2.0/gobject/"; rel="nofollow">gobject</a> is an object-oriented programming system in C. It is used extensively in the GTK+ user interface toolkit. In addition to class-like structures, it provides a signalling system that allows objects to emit, listen for and respond to events. It is designed to be compatible with the object systems of other languages, and this is one of the chief reasons that so many bindings of GTK+ are available (Python, <acronym title="Practical Extraction and Report Language">Perl</acronym>, .NET, Java, C++, etc).
+
+<a href="http://developer.gnome.org/doc/API/2.0/gobject/"; class="urlextern" title="http://developer.gnome.org/doc/API/2.0/gobject/"; rel="nofollow">gobject</a> is an object-oriented programming system in C. It is used extensively in the GTK+ user interface toolkit. In addition to class-like structures, it provides a signalling system that allows objects to emit, listen for and respond to events. It is designed to be compatible with the object systems of other languages, and this is one of the chief reasons that so many bindings of GTK+ are available (Python, <acronym title="Practical Extraction and Report Language">Perl</acronym>, .NET, Java, C++, etc).
</p>
<p>
@@ -201,8 +187,8 @@ GObject is currently used in libgeda for the GedaList class which wrapps a GList
</p>
</div>
-<!-- SECTION "gobject" [3351-4335] -->
-<h2><a name="references" id="references">References</a></h2>
+<!-- EDIT1573 SECTION "gobject" [3351-4335] -->
+<h2 class="sectionedit1574"><a name="references" id="references">References</a></h2>
<div class="level2">
<ul>
<li class="level1"><div class="li"> <a href="http://www.unet.univie.ac.at/aix/aixprggd/genprogc/writing_reentrant_thread_safe_code.htm"; class="urlextern" title="http://www.unet.univie.ac.at/aix/aixprggd/genprogc/writing_reentrant_thread_safe_code.htm"; rel="nofollow">Writing Reentrant and Thread-Safe Code</a></div>
@@ -210,5 +196,5 @@ GObject is currently used in libgeda for the GedaList class which wrapps a GList
</ul>
</div>
-<!-- SECTION "References" [4336-] --></body>
+<!-- EDIT1574 SECTION "References" [4336-] --></body>
</html>
diff --git a/docs/wiki/libgeda3_object_based_design.html b/docs/wiki/libgeda3_object_based_design.html
index 161d4a2..fad33c7 100644
--- a/docs/wiki/libgeda3_object_based_design.html
+++ b/docs/wiki/libgeda3_object_based_design.html
@@ -11,23 +11,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>
+<h1 class="sectionedit1575"><a name="overview" id="overview">Overview</a></h1>
<div class="level1">
<p>
@@ -35,12 +20,13 @@ As stated in <a href="libgeda3.html" class="wikilink1" title="libgeda3.html">lib
</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>
+<!-- EDIT1575 SECTION "Overview" [1-296] -->
+<h1 class="sectionedit1576"><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.
+
+Schematics and PCB (or IC) designs are, by nature, a graphical representation of objects, with interconnections between them.
</p>
<p>
@@ -62,7 +48,8 @@ The basic primitives used in the graphical artwork are:
</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.
+
+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>
@@ -82,16 +69,18 @@ An electrical or electronic CAD must be able to draw components (composed object
</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.
+
+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,…).
+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>
+<!-- EDIT1576 SECTION "Description of the needs in an Electrical CAD system" [297-2701] -->
+<h1 class="sectionedit1577"><a name="object_based_design" id="object_based_design">Object based design</a></h1>
<div class="level1">
<p>
@@ -103,15 +92,16 @@ It is a known fact that all schematics are graphical representations of componen
</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.
+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â??.
+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!.
+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>
@@ -126,9 +116,9 @@ Basically what it provides is:
</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 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 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>
@@ -141,64 +131,75 @@ Basically what it provides is:
</ul>
<p>
- The advantage is clear: all the basic drawing primitives and operations are already done.
+
+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.
+
+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>
+<!-- EDIT1577 SECTION "Object based design" [2702-5463] -->
+<h1 class="sectionedit1578"><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:
+
+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
+ <span class="kw4">int</span> GedaType<span class="sy0">;</span>
+ GList <span class="sy0">*</span>views<span class="sy0">;</span> <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>;
+ GooCanvasItem <span class="sy0">*</span>current_view<span class="sy0">;</span>
+<span class="br0">}</span><span class="sy0">;</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>
+ <span class="kw4">int</span> GedaType<span class="sy0">;</span>
+ GooCanvasItem group<span class="sy0">;</span> <span class="coMULTI">/* There is also an item for groups of objects */</span>
+<span class="br0">}</span><span class="sy0">;</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):
+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>
+ GedaType<span class="sy0">;</span>
+ GooCanvasItem <span class="sy0">*</span>name<span class="sy0">;</span>
+ GooCanvasItem <span class="sy0">*</span>value<span class="sy0">;</span>
+<span class="br0">}</span><span class="sy0">;</span></pre>
+
<p>
-and another one for connectivity items:
+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">int</span> GedaType<span class="sy0">;</span>
+ GooCanvasItem <span class="sy0">*</span>graphic<span class="sy0">;</span>
+ GedaObject <span class="sy0">*</span>connected_object<span class="sy0">;</span>
+<span class="br0">}</span><span class="sy0">;</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">int</span> GedaType<span class="sy0">;</span>
+ GooCanvasItem <span class="sy0">*</span>graphic<span class="sy0">;</span>
+ GList <span class="sy0">*</span>connected_objects<span class="sy0">;</span>
+<span class="br0">}</span><span class="sy0">;</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>
+ <span class="kw4">int</span> GedaType<span class="sy0">;</span>
+ GooCanvasItem <span class="sy0">*</span>graphic<span class="sy0">;</span>
+ GList <span class="sy0">*</span>connected_objects<span class="sy0">;</span>
+<span class="br0">}</span><span class="sy0">;</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).
+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>
@@ -206,25 +207,25 @@ No object naming is required, although it is already supported by default: you c
</p>
<p>
-Example: a 7400 symbol, with a footprint attribute â??DIP-16â??, and reference designator â??U1â?? would look as:
+Example: a 7400 symbol, with a footprint attribute â??DIP-16â??, and reference designator â??U1â?? would look as:
+
</p>
-<pre class="code">
-GedaObject
+<pre class="code">GedaObject
|- views
| |- GedaObjectGroup
| | |- GedaObjectGroup /* the graphic representation */
| | |- GedaObjectProperty /* name = "refdes", value="U1" */
| | |- GedaObjectProperty /* name = "footprint", value="DIP-16" */
- v v
-</pre>
+ 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>
+<!-- EDIT1578 SECTION "geda objects" [5464-7610] -->
+<h1 class="sectionedit1579"><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.
+
+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>
@@ -232,12 +233,13 @@ All canvas specific code can be hidden by a common interface or a runtime plugin
</p>
</div>
-<!-- SECTION "Integration with current code" [7611-7959] -->
-<h1><a name="comments" id="comments">Comments?</a></h1>
+<!-- EDIT1579 SECTION "Integration with current code" [7611-7959] -->
+<h1 class="sectionedit1580"><a name="comments" id="comments">Comments?</a></h1>
<div class="level1">
<p>
- Leave your comment here!
+
+Leave your comment here!
</p>
<p>
@@ -245,7 +247,7 @@ All canvas specific code can be hidden by a common interface or a runtime plugin
</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.
+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>
@@ -253,7 +255,7 @@ We can write a wrapper between libgeda and the canvas for actual rendering. It l
</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.
+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>
@@ -261,5 +263,5 @@ I think some of the important design decisions to make now involve defining the
</p>
</div>
-<!-- SECTION "Comments?" [7960-] --></body>
+<!-- EDIT1580 SECTION "Comments?" [7960-] --></body>
</html>
diff --git a/docs/wiki/media/Makefile.am b/docs/wiki/media/Makefile.am
index 943c93a..2d837ea 100644
--- a/docs/wiki/media/Makefile.am
+++ b/docs/wiki/media/Makefile.am
@@ -3,7 +3,7 @@
docname=wiki
docsdir = $(docdir)/$(docname)/media
-SUBDIRS = devel_tips wiki tragesym geda
+SUBDIRS = geda wiki tragesym devel_tips
docs_DATA =
diff --git a/docs/wiki/media/geda/Makefile.am b/docs/wiki/media/geda/Makefile.am
index 64ae657..7a5dfdc 100644
--- a/docs/wiki/media/geda/Makefile.am
+++ b/docs/wiki/media/geda/Makefile.am
@@ -3,7 +3,7 @@
docname=wiki
docsdir = $(docdir)/$(docname)/media/geda
-docs_DATA = dialogvac.png gparts-ss-parts-2.png warmup_gschem01.png symbol_7400-1_hidden.png two-sch-2.png gparts-ss-devices.png gschem-sym-3.png gparts-ss-packages.png pcb-el-2.png one-sch-1.png switcap_figure1.jpg gschem-sym-1.png board-4.png status_screenshot.jpg coordinatespace.jpg gparts-ss-footprints.png board-1.png dialoginclude.png dialogtrans.png board-3.png symbol_7400-1.png geda_flow.png nets.jpg warmup_add_component.png ambiguous1_fixed.png net.jpg rf_cascade_figure1.jpg gparts-flow-2.png rf_cascade_figure2.jpg gparts-ss-symbols-2.png gparts-ss-symbols.png schematicfinished2.png board-2.png dialogmodel.png switcap_figure3.jpg gparts-ss-companies.png paper1.gif pcb-el-1.png one-sch-3.png ambiguous1.png faq_attrib.jpg dialogvdc1.png two-sch-1.png board-5.png gparts_erd_main.png gparts-ss-parts.png board-6.png switcap_figure2.jpg terminal_screenshot_001.jpg path_example_and_gate-smaller.png warmup_gschem03.png gschem_screenshot_001.jpg path_example_and_gate.png simple1.png gparts_flow.png design_flow.jpg dialogdirective.png gparts-ss-documentation.png fileformat_textgraphic.jpg one-sch-2.png gschem-sym-2.png warmup_gschem02.png schematicfinished.png gschem_workflow_01.jpg switcap_figure4.jpg suse_electronics_menu.png
+docs_DATA = gparts-ss-symbols.png gparts-ss-connect-types.png gparts_erd_main.png gparts-ss-footprints.png board-5.png symbol_7400-1_hidden.png dialogvdc1.png pcb-el-2.png warmup_add_component.png gparts-ss-devices.png screenshot_pcb.png ambiguous1.png schematicfinished2.png gparts-ss-companies.png net.jpg gparts-ss-symbols-2.png board-3.png one-sch-1.png switcap_figure4.jpg screenshot_gschem_osx.png gparts_flow.png gparts-ss-parts.png gparts-ss-documentation.png gschem-sym-1.png dialogdirective.png screenshot_pcb_osx_thumb.png faq_attrib.jpg two-sch-1.png board-4.png symbol_7400-1.png dialogmodel.png gschem-sym-2.png gparts_pkg_2.png gparts-bulk-import.png gparts_pkg_sch.png geda_flow.png screenshot_gerbv_thumb.png gparts-ss-parts-4b.png gparts-flow-2.png dialoginclude.png gparts_pkg_geom.png status_screenshot.jpg ambiguous1_fixed.png board-1.png gparts_pkg.png screenshot_pcb_thumb.png gschem_workflow_01.jpg schematicfinished.png nets.jpg gschem_screenshot_001.jpg screenshot_gschem_osx_thumb.png 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 gparts-ss-packages.png coordinatespace.jpg one-sch-2.png terminal_screenshot_001.jpg suse_electronics_menu.png switcap_figure3.jpg warmup_gschem01.png dialogtrans.png screenshot_gerbv.png gparts-ss-parts-2.png fileformat_textgraphic.jpg screenshot_pcb_osx.png screenshot_gschem_thumb.png warmup_gschem02.png screenshot_gschem.png gschem-sym-3.png rf_cascade_figure1.jpg gparts-ss-parts-4.png paper1.gif one-sch-3.png rf_cascade_figure2.jpg two-sch-2.png gparts-ss-parts-3.png
EXTRA_DIST = $(docs_DATA)
diff --git a/docs/wiki/media/geda/gparts-bulk-import.png b/docs/wiki/media/geda/gparts-bulk-import.png
new file mode 100644
index 0000000..b80df8d
Binary files /dev/null and b/docs/wiki/media/geda/gparts-bulk-import.png differ
diff --git a/docs/wiki/media/geda/gparts-ss-connect-types.png b/docs/wiki/media/geda/gparts-ss-connect-types.png
new file mode 100644
index 0000000..c72f543
Binary files /dev/null and b/docs/wiki/media/geda/gparts-ss-connect-types.png differ
diff --git a/docs/wiki/media/geda/gparts-ss-parts-3.png b/docs/wiki/media/geda/gparts-ss-parts-3.png
new file mode 100644
index 0000000..97b5919
Binary files /dev/null and b/docs/wiki/media/geda/gparts-ss-parts-3.png differ
diff --git a/docs/wiki/media/geda/gparts-ss-parts-4.png b/docs/wiki/media/geda/gparts-ss-parts-4.png
new file mode 100644
index 0000000..531a0e7
Binary files /dev/null and b/docs/wiki/media/geda/gparts-ss-parts-4.png differ
diff --git a/docs/wiki/media/geda/gparts-ss-parts-4b.png b/docs/wiki/media/geda/gparts-ss-parts-4b.png
new file mode 100644
index 0000000..73aef60
Binary files /dev/null and b/docs/wiki/media/geda/gparts-ss-parts-4b.png differ
diff --git a/docs/wiki/media/geda/gparts_pkg.png b/docs/wiki/media/geda/gparts_pkg.png
new file mode 100644
index 0000000..de9c94a
Binary files /dev/null and b/docs/wiki/media/geda/gparts_pkg.png differ
diff --git a/docs/wiki/media/geda/gparts_pkg_2.png b/docs/wiki/media/geda/gparts_pkg_2.png
new file mode 100644
index 0000000..bcd5a5a
Binary files /dev/null and b/docs/wiki/media/geda/gparts_pkg_2.png differ
diff --git a/docs/wiki/media/geda/gparts_pkg_geom.png b/docs/wiki/media/geda/gparts_pkg_geom.png
new file mode 100644
index 0000000..8af8819
Binary files /dev/null and b/docs/wiki/media/geda/gparts_pkg_geom.png differ
diff --git a/docs/wiki/media/geda/gparts_pkg_sch.png b/docs/wiki/media/geda/gparts_pkg_sch.png
new file mode 100644
index 0000000..4f20c77
Binary files /dev/null and b/docs/wiki/media/geda/gparts_pkg_sch.png differ
diff --git a/docs/wiki/media/geda/screenshot_gerbv.png b/docs/wiki/media/geda/screenshot_gerbv.png
new file mode 100644
index 0000000..ce72032
Binary files /dev/null and b/docs/wiki/media/geda/screenshot_gerbv.png differ
diff --git a/docs/wiki/media/geda/screenshot_gerbv_thumb.png b/docs/wiki/media/geda/screenshot_gerbv_thumb.png
new file mode 100644
index 0000000..70da8e9
Binary files /dev/null and b/docs/wiki/media/geda/screenshot_gerbv_thumb.png differ
diff --git a/docs/wiki/media/geda/screenshot_gschem.png b/docs/wiki/media/geda/screenshot_gschem.png
new file mode 100644
index 0000000..6dffb58
Binary files /dev/null and b/docs/wiki/media/geda/screenshot_gschem.png differ
diff --git a/docs/wiki/media/geda/screenshot_gschem_osx.png b/docs/wiki/media/geda/screenshot_gschem_osx.png
new file mode 100644
index 0000000..30af0bd
Binary files /dev/null and b/docs/wiki/media/geda/screenshot_gschem_osx.png differ
diff --git a/docs/wiki/media/geda/screenshot_gschem_osx_thumb.png b/docs/wiki/media/geda/screenshot_gschem_osx_thumb.png
new file mode 100644
index 0000000..94eb0d4
Binary files /dev/null and b/docs/wiki/media/geda/screenshot_gschem_osx_thumb.png differ
diff --git a/docs/wiki/media/geda/screenshot_gschem_thumb.png b/docs/wiki/media/geda/screenshot_gschem_thumb.png
new file mode 100644
index 0000000..6b4344e
Binary files /dev/null and b/docs/wiki/media/geda/screenshot_gschem_thumb.png differ
diff --git a/docs/wiki/media/geda/screenshot_pcb.png b/docs/wiki/media/geda/screenshot_pcb.png
new file mode 100644
index 0000000..dc0e15f
Binary files /dev/null and b/docs/wiki/media/geda/screenshot_pcb.png differ
diff --git a/docs/wiki/media/geda/screenshot_pcb_osx.png b/docs/wiki/media/geda/screenshot_pcb_osx.png
new file mode 100644
index 0000000..118fd94
Binary files /dev/null and b/docs/wiki/media/geda/screenshot_pcb_osx.png differ
diff --git a/docs/wiki/media/geda/screenshot_pcb_osx_thumb.png b/docs/wiki/media/geda/screenshot_pcb_osx_thumb.png
new file mode 100644
index 0000000..6b2e8a6
Binary files /dev/null and b/docs/wiki/media/geda/screenshot_pcb_osx_thumb.png differ
diff --git a/docs/wiki/media/geda/screenshot_pcb_thumb.png b/docs/wiki/media/geda/screenshot_pcb_thumb.png
new file mode 100644
index 0000000..271ecbb
Binary files /dev/null and b/docs/wiki/media/geda/screenshot_pcb_thumb.png differ
diff --git a/docs/wiki/media/tragesym/Makefile.am b/docs/wiki/media/tragesym/Makefile.am
index fd88f56..857988c 100644
--- a/docs/wiki/media/tragesym/Makefile.am
+++ b/docs/wiki/media/tragesym/Makefile.am
@@ -5,7 +5,7 @@ docsdir = $(docdir)/$(docname)/media/tragesym
SUBDIRS = tragesym
-docs_DATA = kpdf_pinconfiguration.png ooo_changedpins.png xemacs_modifiedselection.png gschem_showhidden.png ooo_attributes.png template.ods ooo_rearanged.png xemacs_rawselection.png kpdf_pindescription.png acroread_selectiontable.png template.txt template2.ods template2.txt.src gschem_finished.png ooo_selection.png
+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)
diff --git a/docs/wiki/media/wiki/Makefile.am b/docs/wiki/media/wiki/Makefile.am
index 5b6761f..e048a23 100644
--- a/docs/wiki/media/wiki/Makefile.am
+++ b/docs/wiki/media/wiki/Makefile.am
@@ -1,4 +1,5 @@
+
docname=wiki
docsdir = $(docdir)/$(docname)/media/wiki
diff --git a/docs/wiki/pcb-projects.html b/docs/wiki/pcb-projects.html
index f546a40..65a2956 100644
--- a/docs/wiki/pcb-projects.html
+++ b/docs/wiki/pcb-projects.html
@@ -12,57 +12,142 @@
<body>
+<h3 class="sectionedit1581"><a name="pcb_layout_editor" id="pcb_layout_editor">PCB Layout Editor</a></h3>
+<div class="level3">
+</div>
-<h3><a name="pcb_layout_editor" id="pcb_layout_editor">PCB Layout Editor</a></h3>
-<div class="level3">
+<h5><a name="plow_feature" id="plow_feature">Plow feature</a></h5>
+<div class="level5">
+
+<p>
+
+A â??plowâ?? feature where the line tool shoves existing traces aside
+preserving the design rules when possible.
+</p>
+
+<p>
+Difficulty = 4-5
+</p>
</div>
-<h5><a name="ipc_footprint_calculator" id="ipc_footprint_calculator">IPC Footprint Calculator</a></h5>
+<h5><a name="fast_snap_rounding_algorithm" id="fast_snap_rounding_algorithm">Fast snap rounding Algorithm</a></h5>
<div class="level5">
<p>
- Build a footprint calculator that can take the IPC rules and produce a pcb footprint. Preferably write this in a way where the core program is independent of a gui so that you can script it for generating entire large families of footprints or hook it up to a <acronym title="Graphical User Interface">GUI</acronym> of choice (lesstif, gtk, maybe even cgi). Would require the purchase of IPC-7351 (approximately U.S.A. $100)and verifying that one is allowed to produce such a calculator.
+
+Implement a fast snap rounding algorithm and resolve the case where
+inserted point cause self-intersection.
+</p>
+
+<p>
+PCB uses an integer coordinate system for all of its objects. The polygon
+clipping code computes all points of intersection between two
+non-self-intersecting contours, (among many other things it does) but these
+points of intersection must also have integer coordinates.
</p>
<p>
-Difficulty = 2
+A snap-rounding algorithm replaces two segments that intersect at other than
+their end points with four segments where each has an end point on an
+integer coordinate near the original (non-integer) intersection. Because
+this rounding operation on the point of intersection can change the slopes
+of the four segments compare to that of the original two, it raises the
+possibility that new intersections between the replacement segments and
+other segments of the contours occur that did not exist with the original
+segments. The snap rounding algorithm needs to produce a collection of
+segments where all intersections occur at segment end points having integer
+coordinates. The existing code in pcb does this already, but it uses a
+theoretically slow algorithm, compared to others that are known, such as:
+</p>
+
+<p>
+ â??Improved output-sensitive snap rounding,â?? John Hershberger, Proceedings of
+the 22nd annual symposium on Computational geomerty, 2006, pp 357-366.
+ <a href="http://doi.acm.org/10.1145/1137856.1137909"; class="urlextern" title="http://doi.acm.org/10.1145/1137856.1137909"; rel="nofollow">http://doi.acm.org/10.1145/1137856.1137909</a>
+</p>
+
+<p>
+Algorithms described by de Berg, or Goodrich or Halperin, or Hobby would
+probably also be better than what we currently have implemented.
+</p>
+
+<p>
+In addition, there are rare-but-real degenerate situations where the snap
+rounding results in one (or both) contourss having a self-intersection that
+did not exist before. This self-intersection is fatal to our polygon
+clipping core. We do not know if the snap rounding algorithms in the
+literature deal with this issue or not, but if they do not, we need to
+develop a variant algorithm that does, whether done by judicious choice of
+the rounding points that are created, or a post-processing step that
+eliminates the self-intersection with minimal geometric distortion to the
+original contours.
+</p>
+
+<p>
+Difficulty = 4-5
</p>
</div>
-<h5><a name="export_ipc-356" id="export_ipc-356">Export IPC-356</a></h5>
+<h5><a name="auto-routed_drawing_tool" id="auto-routed_drawing_tool">Auto-routed drawing tool</a></h5>
<div class="level5">
<p>
- IPC-D-356 is a specification for a netlist output format used for manufacturing test of PCBs. It specifies both connectivity as well as pad position information, thereby facilitating the use of automated testing after PCB manufacture. In this project, you would implement an exporter which would write an IPC-D-356 compliant file from within PCB. The IPC-D-356 <acronym title="specification">spec</acronym> is available at: <a href="http://www.solidigm.com/downloads/ipc356.pdf"; class="urlextern" title="http://www.solidigm.com/downloads/ipc356.pdf"; rel="nofollow">http://www.solidigm.com/downloads/ipc356.pdf</a>
+
+Basically with this tool, you would click on a starting point, then drag the
+crosshair to some other (typically intermediate point), possibly on another
+layer and an auto-routing tool would show a prospective path to that point
+(meeting design rules and style requirements). If you didn't like the
+offered path, you could hit a key to see a more expensive candidate, or a
+different key to (back up) to a less expensive candidate. The prospective
+route would dynamically change to reach the crosshair end-point as the
+crosshair is moved. It would disappear if no path could be found. Clicking
+would place the prospective path as copper and anchor a new starting point
+for the tool (much like the line tool does now).
</p>
<p>
-Difficulty = 3
+Difficulty = 5
</p>
</div>
-<h5><a name="recently_loaded_file_list" id="recently_loaded_file_list">Recently loaded file list</a></h5>
+<h5><a name="ipc_footprint_calculator" id="ipc_footprint_calculator">IPC Footprint Calculator</a></h5>
<div class="level5">
<p>
- Presently pcb does not present a list of recently loaded files in the file menu. It would be nice if pcb kept track of the last few files a user loaded. This is a common feature found in other programs.
+
+Build a footprint calculator that can take the IPC rules and produce a pcb footprint. Preferably write this in a way where the core program is independent of a gui so that you can script it for generating entire large families of footprints or hook it up to a <acronym title="Graphical User Interface">GUI</acronym> of choice (lesstif, gtk, maybe even cgi). Would require the purchase of IPC-7351 (approximately U.S.A. $100)and verifying that one is allowed to produce such a calculator.
</p>
<p>
-Difficulty = 1
+Difficulty = 2
+</p>
+
+</div>
+
+<h5><a name="export_ipc-356" id="export_ipc-356">Export IPC-356</a></h5>
+<div class="level5">
+
+<p>
+
+IPC-D-356 is a specification for a netlist output format used for manufacturing test of PCBs. It specifies both connectivity as well as pad position information, thereby facilitating the use of automated testing after PCB manufacture. In this project, you would implement an exporter which would write an IPC-D-356 compliant file from within PCB. The IPC-D-356 <acronym title="specification">spec</acronym> is available at: <a href="http://www.solidigm.com/downloads/ipc356.pdf"; class="urlextern" title="http://www.solidigm.com/downloads/ipc356.pdf"; rel="nofollow">http://www.solidigm.com/downloads/ipc356.pdf</a>
+</p>
+
+<p>
+Difficulty = 3
</p>
</div>
-<h5><a name="remember_dialog_size_and_positions" id="remember_dialog_size_and_positions">Remember dialog size and positions</a></h5>
+<h5><a name="recently_loaded_file_list" id="recently_loaded_file_list">Recently loaded file list</a></h5>
<div class="level5">
<p>
- pcb dialogs should remember their size and position. Some of pcbâ??s dialogs remember their size, but this isnâ??t universal. Several users have complained since they have to reposition and/or resize the dialog boxes every time they are opened.
+
+Presently pcb does not present a list of recently loaded files in the file menu. It would be nice if pcb kept track of the last few files a user loaded. This is a common feature found in other programs.
</p>
<p>
diff --git a/docs/wiki/pcb-roadmap.html b/docs/wiki/pcb-roadmap.html
new file mode 100644
index 0000000..547a224
--- /dev/null
+++ b/docs/wiki/pcb-roadmap.html
@@ -0,0 +1,323 @@
+<!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 class="sectionedit1614"><a name="pcb_roadmap" id="pcb_roadmap">PCB Roadmap</a></h1>
+<div class="level1">
+
+<p>
+
+This is a guide to the future direction of the PCB layout editor.
+
+</p>
+<ul>
+<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"> gEDA roadmap</a> has some PCB items.</div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-todos.html" class="wikilink1" title="geda-todos.html"> gEDA To-Dos</a> also has some PCB items.</div>
+</li>
+<li class="level1"><div class="li"> <a href="pcb-projects.html" class="wikilink1" title="pcb-projects.html"> PCB Projects</a> lists some wish-list items.</div>
+</li>
+</ul>
+
+</div>
+<!-- EDIT1614 SECTION "PCB Roadmap" [1-302] -->
+<h2 class="sectionedit1615"><a name="general_guidelines_for_releases" id="general_guidelines_for_releases">General Guidelines for Releases</a></h2>
+<div class="level2">
+
+<p>
+
+In general, there are three types of changes that go into PCB - bug
+fixes, new features, and incompatible changes. A <em>bug fix</em> is when
+PCB doesn't do what it's supposed to do - this includes documentation
+bugs as well as code problems. A <em>new feature</em> is something that
+adds functionality to PCB but doesn't change any existing
+functionality. An <em>incompatible change</em> is anything that causes
+(intentional) compatibility issues with older versions of PCB, and
+usually means a large design change. Note that a new feature that
+adds a backwards-incompatible change to the file format <em>when it's
+used</em> is not in this category.
+</p>
+
+<p>
+The current plans are as follows:
+
+</p>
+<ul>
+<li class="level1"><div class="li"> Bug fix releases every two months or so until we clear the backlog.</div>
+</li>
+</ul>
+<ul>
+<li class="level1"><div class="li"> Start on a PCB 4.0 release that folds in some large design changes we've been talking about for years.</div>
+</li>
+</ul>
+
+<p>
+
+At the moment, bugfix releases will be of the form <code>pcb-YYYYMMDD</code>.
+Once 4.0 is released, the major.minor.bugfix numbers will correspond
+to the three categories listed above: bugfixes cause a *.*.N release,
+new features cause a *.N release, major changes cause a N.0 release.
+The <code>YYYYMMDD</code> release numbers will then be used for regular
+non-release snapshots.
+</p>
+
+<p>
+The remainder of this page will list the various changes that are
+planned (or at least hoped for) for upcoming and future releases.
+</p>
+
+<p>
+Bugs, patches, and feature requests should be added to the
+<a href="https://bugs.launchpad.net/pcb"; class="urlextern" title="https://bugs.launchpad.net/pcb"; rel="nofollow">Launchpad
+trackers</a>. The default status <strong>undecided</strong>. Requests with that
+priority will be considered â??unreviewedâ??.
+
+</p>
+
+</div>
+<!-- EDIT1615 SECTION "General Guidelines for Releases" [303-1908] -->
+<h2 class="sectionedit1616"><a name="next_bug_release" id="next_bug_release">Next Bug Release</a></h2>
+<div class="level2">
+
+<p>
+
+This is a list of fixes that <em>must</em> be fixed before the next bug
+release, in addition to any â??next bug releaseâ?? artifacts in the bug tracker.
+</p>
+
+</div>
+<!-- EDIT1616 SECTION "Next Bug Release" [1909-2083] -->
+<h2 class="sectionedit1617"><a name="future_bug_releases" id="future_bug_releases">Future Bug Releases</a></h2>
+<div class="level2">
+
+<p>
+
+This is a list of fixes that should be fixed eventually.
+</p>
+
+</div>
+<!-- EDIT1617 SECTION "Future Bug Releases" [2084-2175] -->
+<h2 class="sectionedit1618"><a name="next_feature_release" id="next_feature_release">Next Feature Release</a></h2>
+<div class="level2">
+
+<p>
+
+This is a list of new features that will be added before the next
+feature release (or, perhaps the next bug release, if time permits).
+</p>
+
+<p>
+Make the code C++ compatible.
+</p>
+
+<p>
+Allow via annulii to overlap each other.
+</p>
+
+<p>
+More route styles.
+</p>
+
+<p>
+Nanometer resolution - this is the â??metric unitsâ?? change we've talked
+about many times.
+</p>
+
+<p>
+Real layer types. Silks, keepouts, mask docs at least. Maybe
+anti-draw or paste.
+</p>
+
+</div>
+<!-- EDIT1618 SECTION "Next Feature Release" [2176-2611] -->
+<h2 class="sectionedit1619"><a name="future_feature_releases" id="future_feature_releases">Future Feature Releases</a></h2>
+<div class="level2">
+
+<p>
+
+Other features that should be added eventually.
+</p>
+
+</div>
+<!-- EDIT1619 SECTION "Future Feature Releases" [2612-2697] -->
+<h2 class="sectionedit1620"><a name="next_incompatible_release" id="next_incompatible_release">Next Incompatible Release</a></h2>
+<div class="level2">
+
+<p>
+
+This is a list of major changes that we think are desirable to include
+in PCB, and wish to put effort into.
+</p>
+
+</div>
+<!-- EDIT1620 SECTION "Next Incompatible Release" [2698-2845] -->
+<h2 class="sectionedit1621"><a name="future_incompatible_releases" id="future_incompatible_releases">Future Incompatible Releases</a></h2>
+<div class="level2">
+
+<p>
+
+This is a list of other major changes that we think are desirable to
+include in PCB, but so far have not committed any effort to.
+</p>
+
+</div>
+<!-- EDIT1621 SECTION "Future Incompatible Releases" [2846-3018] -->
+<h2 class="sectionedit1622"><a name="wish_list" id="wish_list">Wish List</a></h2>
+<div class="level2">
+
+<p>
+
+This section lists possible projects for future releases, which either
+haven't been agreed on, or haven't been scheduled. If you'd like to
+work on one of these, go ahead <img src="images/smileys/icon_smile.gif" align="middle" alt=":-)" />
+</p>
+
+<p>
+
+Other <acronym title="Graphical User Interface">GUI</acronym> cleanups. Gtk upgraded to â??best practicesâ??. Importer config.
+</p>
+
+<p>
+â??New layoutâ?? templates and wizards. (instead of defaulting to 4×4 8-layer)
+</p>
+
+<p>
+import/wizard plugins (as well as exports)
+</p>
+
+<p>
+DRC cleanups/rewrite
+</p>
+
+<p>
+CAM engine? (i.e. ability to say â??draw outline on top soldermaskâ?? via script/config)
+</p>
+
+<p>
+Ability to hook into layer exporters (i.e. thindraw as a HID)
+</p>
+
+<p>
+New file format we've been discussing.
+</p>
+
+<p>
+Variable-angle arcs. 90 degrees is extremely limiting.
+</p>
+
+<p>
+Filled circles, sans kludge. Currently, to get a filled circle you
+create a zero-length trace of the right width.
+</p>
+
+<p>
+Having all shapes that are supported for traces supported for
+footprint copper (arcs, polygons, circles, etcetera).
+</p>
+
+<p>
+Unification of shortcuts in gschem and PCB, or at least an easy option
+for PCB to mimic gschem's shortcuts.
+</p>
+
+<p>
+Better support for free-rotated components: assert that pads at funky
+angles are rendered correctly, fix autorouter for components at weird
+angles (the latest git version has a tendency to either ignore the route
+command or to segfault, depending on the specifics), add rotation to the
+ctrl-R report, etcetera.
+</p>
+
+<p>
+Ability to copy a footprint's name from the library dialogue (so it
+can be pasted into gschem's attribute list).
+</p>
+
+<p>
+Ability to edit netlist in-situ (possibly by drawing on the rat lines
+layer) - e.g, when you want to add a heatsink soldered to ground, it
+will always show up as shorted until the netlist is edited to
+incorporate it.
+</p>
+
+<p>
+Last but not least, blind and buried vias. It's big, reasonably
+important, and has been on people's wish lists for years.
+</p>
+
+<p>
+Trace impedance calculator, with automatic adjustment capability (fill
+in thickness, stray capacitance and desired impedance, and the width is
+adjusted to satisfy the conditions).
+</p>
+
+<p>
+Integrated footprint lookup and fetch from gedasymbols.org.
+</p>
+
+<p>
+Heirarchical pcb model - subcells, footprints-as-pcb, etc.
+</p>
+
+<p>
+A shape I've often wanted on a pad is circle with the sides cut off.
+This is slightly different than an oval. Something like Inkscape's
+boolean operations would be excellent.
+</p>
+
+<p>
+How about text at not-90 degree angles? Or support for rotated square
+pads (I know, the file format doesn't support those two.)
+</p>
+
+<p>
+Editing on the grid has got to go! Counting grid points is the worst
+possible way to enter positional information into a computer.
+</p>
+
+<p>
+Make every field in object reports editable.
+</p>
+
+<p>
+Allow direct entry of offsets and absolute positions when editing.
+</p>
+
+<p>
+Add â??offsetâ?? and â??trimâ?? feature à la 2D CAD programs.
+</p>
+
+<p>
+Add â??point to tangentâ?? and â??tangent to tangentâ?? line drawing feature
+Ã la 2D CAD programs.
+</p>
+
+<p>
+Also, trim polygons against â??outlineâ?? layer. Fix polygons in general.
+</p>
+
+<p>
+square/rectangular holes (e.g. mounting tabs)
+</p>
+
+<p>
+Automatic least version required file saving. Set the file format
+version based on features used, not the version of PCB This will
+become valuable as we add features like blind vias, custom pad stacks
+etcâ?¦.
+
+</p>
+
+</div>
+<!-- EDIT1622 SECTION "Wish List" [3019-] --></body>
+</html>
diff --git a/docs/wiki/start.html b/docs/wiki/start.html
index 19d0714..b68edad 100644
--- a/docs/wiki/start.html
+++ b/docs/wiki/start.html
@@ -11,55 +11,36 @@
</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_quick_reference" class="toc">FAQs & Quick Reference</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>
+<h1 class="sectionedit1582"><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>
+<!-- EDIT1582 SECTION "gEDA Project Wiki" [2-34] -->
+<h2 class="sectionedit1583"><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.
+
+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.
+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>.
+All of the software in the gEDA suite can be found on the <a href="geda-download.html" class="wikilink1" title="geda-download.html">download</a> page.
</p>
</div>
-<!-- SECTION "What is gEDA?" [36-1176] -->
-<h2><a name="official_project_documentation" id="official_project_documentation">Official Project documentation</a></h2>
+<!-- EDIT1583 SECTION "What is gEDA?" [35-1144] -->
+<h2 class="sectionedit1584"><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.
+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> : Contains links to tutorials, manuals, HOWTOs and format specifications of the gEDA suite. </div>
@@ -67,12 +48,13 @@ These are the official project docs. They have been converted from LaTeX and <a
</ul>
</div>
-<!-- SECTION "Official Project documentation" [1177-1516] -->
-<h2><a name="faqs_quick_reference" id="faqs_quick_reference">FAQs & Quick Reference</a></h2>
+<!-- EDIT1584 SECTION "Official Project documentation" [1145-1484] -->
+<h2 class="sectionedit1585"><a name="faqs_quick_reference" id="faqs_quick_reference">FAQs & Quick Reference</a></h2>
<div class="level2">
<p>
-These are informal 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.
+These are informal 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>
@@ -81,7 +63,9 @@ These are informal FAQs, HOWTOs, and tips/tricks to help you with the practical
</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 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-howto_report_bugs.html" class="wikilink1" title="geda-howto_report_bugs.html">Howto report bugs</a></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>
@@ -93,13 +77,13 @@ These are informal FAQs, HOWTOs, and tips/tricks to help you with the practical
</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_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-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 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-gschem_symbol_creation.html" class="wikilink1" title="geda-gschem_symbol_creation.html">gschem Symbol Creation</a> : gschem symbol creation guide.</div>
</li>
@@ -108,55 +92,59 @@ These are informal FAQs, HOWTOs, and tips/tricks to help you with the practical
</ul>
</div>
-<!-- SECTION "FAQs & Quick Reference" [1517-3035] -->
-<h2><a name="developer_documentation" id="developer_documentation">Developer Documentation</a></h2>
+<!-- EDIT1585 SECTION "FAQs & Quick Reference" [1485-3037] -->
+<h2 class="sectionedit1586"><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:
+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 class="level1"><div class="li"> <a href="geda-developer.html" class="wikilink1" title="geda-developer.html"> developer </a> : Code repository, developer mailing list and building information.</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 class="level1"><div class="li"> <a href="geda-todos.html" class="wikilink1" title="geda-todos.html">Todos</a> : 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 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 class="level1"><div class="li"> <a href="geda-devel-tips.html" class="wikilink1" title="geda-devel-tips.html">devel-tips</a> : Various tips and tricks when doing gEDA development.</div>
</li>
</ul>
<p>
- The following pages are work-in-progress discussions and/or brainstorming:
+
+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 class="level1"><div class="li"> <a href="libgeda3.html" class="wikilink1" title="libgeda3.html">libgeda3</a> : 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 class="level1"><div class="li"> <a href="geda-circuit_simulation_improvements.html" class="wikilink1" title="geda-circuit_simulation_improvements.html">Circuit Simulation Improvements</a> : 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 class="level1"><div class="li"> <a href="geda-data_plotting_improvements.html" class="wikilink1" title="geda-data_plotting_improvements.html">Data Plotting Improvements</a> : 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 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> : 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>
-<li class="level1"><div class="li"> <a href="geda-gparts_dd.html" class="wikilink1" title="geda-gparts_dd.html">Parts Manager</a> : A working document for a gEDA parts manager</div>
+<li class="level1"><div class="li"> <a href="geda-gparts_tc.html" class="wikilink1" title="geda-gparts_tc.html">Parts Manager</a> : A working document for a gEDA parts manager</div>
</li>
</ul>
</div>
-<!-- SECTION "Developer Documentation" [3036-4598] -->
-<h2><a name="talks" id="talks">Talks</a></h2>
+<!-- EDIT1586 SECTION "Developer Documentation" [3038-4443] -->
+<h2 class="sectionedit1587"><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.
+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>
@@ -164,35 +152,33 @@ These are slides of presentations done about gEDA. They provide a good top-leve
</ul>
</div>
-<!-- SECTION "Talks" [4599-4839] -->
-<h2><a name="google_summer_of_code" id="google_summer_of_code">Google Summer of Code</a></h2>
+<!-- EDIT1587 SECTION "Talks" [4444-4686] -->
+<h2 class="sectionedit1588"><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:
+The gEDA project has participated in the Google Summer of Code.
</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:
+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>
+<li class="level1"><div class="li"> <a href="gsoc2009.html" class="wikilink1" title="gsoc2009.html">2009</a> (gEDA did not participate in 2009)</div>
+</li>
+<li class="level1"><div class="li"> <a href="gsoc2010.html" class="wikilink1" title="gsoc2010.html">2010</a> (gEDA did not participate in 2010)</div>
+</li>
</ul>
</div>
-<!-- SECTION "Google Summer of Code" [4840-5219] -->
-<h2><a name="translations" id="translations">Translations</a></h2>
+<!-- EDIT1588 SECTION "Google Summer of Code" [4687-5015] -->
+<h2 class="sectionedit1589"><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>
@@ -202,12 +188,12 @@ Here is this yearâ??s Google Summer of Code page:
</ul>
</div>
-<!-- SECTION "Translations" [5220-5336] -->
-<h2><a name="geda_users" id="geda_users">gEDA Users</a></h2>
+<!-- EDIT1589 SECTION "Translations" [5016-5133] -->
+<h2 class="sectionedit1590"><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>.
+Users may discuss development, help, installation, and working tips through the <a href="geda-mailinglists.html" class="wikilink1" title="geda-mailinglists.html">mailinglists</a>.
</p>
<p>
@@ -219,8 +205,8 @@ The so-called â??Free Dogâ?? organization ( <a href="http://freeedaug.org/"; clas
</p>
</div>
-<!-- SECTION "gEDA Users" [5337-5869] -->
-<h2><a name="about_this_wiki" id="about_this_wiki">About this Wiki</a></h2>
+<!-- EDIT1590 SECTION "gEDA Users" [5134-5632] -->
+<h2 class="sectionedit1591"><a name="about_this_wiki" id="about_this_wiki">About this Wiki</a></h2>
<div class="level2">
<p>
@@ -228,9 +214,10 @@ 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" [5870-] --></body>
+<!-- EDIT1591 SECTION "About this Wiki" [5633-] --></body>
</html>
diff --git a/docs/wiki/start_es.html b/docs/wiki/start_es.html
index 4408be8..69a5df9 100644
--- a/docs/wiki/start_es.html
+++ b/docs/wiki/start_es.html
@@ -11,41 +11,28 @@
</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="#enlaces_a_documentacion_en_espanol" class="toc">Enlaces a documentación en español</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#traducciones" class="toc">Traducciones</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#tutoriales" class="toc">Tutoriales</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#otros" class="toc">Otros</a></span></div></li></ul>
-</li></ul>
-</div>
-</div>
-
-
-<h1><a name="enlaces_a_documentacion_en_espanol" id="enlaces_a_documentacion_en_espanol">Enlaces a documentación en español</a></h1>
+<h1 class="sectionedit1592"><a name="enlaces_a_documentacion_en_espanol" id="enlaces_a_documentacion_en_espanol">Enlaces a documentación en español</a></h1>
<div class="level1">
</div>
-<!-- SECTION "Enlaces a documentación en español" [1-52] -->
-<h2><a name="traducciones" id="traducciones">Traducciones</a></h2>
+<!-- EDIT1592 SECTION "Enlaces a documentación en español" [1-52] -->
+<h2 class="sectionedit1593"><a name="traducciones" id="traducciones">Traducciones</a></h2>
<div class="level2">
<p>
- <a href="http://www.jcoppens.com/soft/howto/geda-spice"; class="urlextern" title="http://www.jcoppens.com/soft/howto/geda-spice"; rel="nofollow"> Simulación de circuitos con gEDA y SPICE</a>
+
+<a href="http://www.jcoppens.com/soft/howto/geda-spice"; class="urlextern" title="http://www.jcoppens.com/soft/howto/geda-spice"; rel="nofollow"> Simulación de circuitos con gEDA y SPICE</a>
</p>
</div>
-<!-- SECTION "Traducciones" [53-174] -->
-<h2><a name="tutoriales" id="tutoriales">Tutoriales</a></h2>
+<!-- EDIT1593 SECTION "Traducciones" [53-174] -->
+<h2 class="sectionedit1594"><a name="tutoriales" id="tutoriales">Tutoriales</a></h2>
<div class="level2">
<p>
- <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>
+
+<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>
@@ -53,12 +40,13 @@
</p>
</div>
-<!-- SECTION "Tutoriales" [175-359] -->
-<h2><a name="otros" id="otros">Otros</a></h2>
+<!-- EDIT1594 SECTION "Tutoriales" [175-359] -->
+<h2 class="sectionedit1595"><a name="otros" id="otros">Otros</a></h2>
<div class="level2">
<p>
- <a href="http://glud.udistrital.edu.co/fileadmin/Archivo/Documentacion/Manuales/impvl/out/index.html"; class="urlextern" title="http://glud.udistrital.edu.co/fileadmin/Archivo/Documentacion/Manuales/impvl/out/index.html"; rel="nofollow"> Verilog con Software Libre</a>
+
+<a href="http://glud.udistrital.edu.co/fileadmin/Archivo/Documentacion/Manuales/impvl/out/index.html"; class="urlextern" title="http://glud.udistrital.edu.co/fileadmin/Archivo/Documentacion/Manuales/impvl/out/index.html"; rel="nofollow"> Verilog con Software Libre</a>
</p>
<p>
@@ -70,9 +58,10 @@
</p>
<p>
-<a href="http://migueldemalaga.blogspot.es/img/Geda-gschem-.pdf"; class="urlextern" title="http://migueldemalaga.blogspot.es/img/Geda-gschem-.pdf"; rel="nofollow"> gEDA - gschem</a>
+<a href="http://migueldemalaga.blogspot.es/img/Geda-gschem-.pdf"; class="urlextern" title="http://migueldemalaga.blogspot.es/img/Geda-gschem-.pdf"; rel="nofollow"> gEDA - gschem</a>
+
</p>
</div>
-<!-- SECTION "Otros" [360-] --></body>
+<!-- EDIT1595 SECTION "Otros" [360-] --></body>
</html>
diff --git a/docs/wiki/start_fr.html b/docs/wiki/start_fr.html
index b629fc9..700398c 100644
--- a/docs/wiki/start_fr.html
+++ b/docs/wiki/start_fr.html
@@ -11,38 +11,22 @@
</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="#wiki_du_projet_geda" class="toc">Wiki du Projet gEDA</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#qu_est_ce_que_geda" class="toc">Qu'est ce que gEDA?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#documentation_du_projet_officiel" class="toc">Documentation du Projet Officiel</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#faq_et_documentations_officielles_du_projet" class="toc">FAQ et Documentations officielles du Projet</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#presentations" class="toc">Présentations</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#a_propos_du_wiki" class="toc">Ã? propos du Wiki</a></span></div></li></ul>
-</li></ul>
-</div>
-</div>
-
-
-<h1><a name="wiki_du_projet_geda" id="wiki_du_projet_geda">Wiki du Projet gEDA</a></h1>
+<h1 class="sectionedit1596"><a name="wiki_du_projet_geda" id="wiki_du_projet_geda">Wiki du Projet gEDA</a></h1>
<div class="level1">
</div>
-<!-- SECTION "Wiki du Projet gEDA" [1-35] -->
-<h2><a name="qu_est_ce_que_geda" id="qu_est_ce_que_geda">Qu'est ce que gEDA?</a></h2>
+<!-- EDIT1596 SECTION "Wiki du Projet gEDA" [1-35] -->
+<h2 class="sectionedit1597"><a name="qu_est_ce_que_geda" id="qu_est_ce_que_geda">Qu'est ce que gEDA?</a></h2>
<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>
-Les outils placés dans la Suite vous permettent de concevoir des systèmes de complexité basse à moyenne, de qualité professionnelle. En utilisant les outils gEDA, vous pouvez créer des PCB jusquâ??à 8 couches (bientôt plus) avec un nombre illimité de composants et de pistes. Les outils sont adaptés à une utilisation par les étudiants, les éducateurs, les passionnés, les consultants, les petites séries et même les grandes corporations où un ingénieur peut avoir besoin de réaliser une carte rapidement (i.e. pour un test manuel), dans lâ??urgence.
+Les outils placés dans la Suite vous permettent de concevoir des systèmes de complexité basse à moyenne, de qualité professionnelle. En utilisant les outils gEDA, vous pouvez créer des PCB jusqu'à 8 couches (bientôt plus) avec un nombre illimité de composants et de pistes. Les outils sont adaptés à une utilisation par les étudiants, les éducateurs, les passionnés, les consultants, les petites séries et même les grandes corporations où un ingénieur peut avoir besoin de réaliser une carte rapidement (i.e. pour un test manuel), dans l'urgence.
</p>
<p>
@@ -50,64 +34,67 @@ Tous les logiciels de la suite gEDA peuvent être trouvés sur la <a href="http:
</p>
</div>
-<!-- SECTION "Qu'est ce que gEDA?" [36-1427] -->
-<h2><a name="documentation_du_projet_officiel" id="documentation_du_projet_officiel">Documentation du Projet Officiel</a></h2>
+<!-- EDIT1597 SECTION "Qu'est ce que gEDA?" [36-1427] -->
+<h2 class="sectionedit1598"><a name="documentation_du_projet_officiel" id="documentation_du_projet_officiel">Documentation du Projet Officiel</a></h2>
<div class="level2">
<p>
-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.
+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="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 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>
</div>
-<!-- SECTION "Documentation du Projet Officiel" [1428-1781] -->
-<h2><a name="faq_et_documentations_officielles_du_projet" id="faq_et_documentations_officielles_du_projet">FAQ et Documentations officielles du Projet</a></h2>
+<!-- EDIT1598 SECTION "Documentation du Projet Officiel" [1428-1781] -->
+<h2 class="sectionedit1599"><a name="faq_et_documentations_officielles_du_projet" id="faq_et_documentations_officielles_du_projet">FAQ et Documentations officielles du Projet</a></h2>
<div class="level2">
<p>
-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.
+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="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="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 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.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="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 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="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 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="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 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="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 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="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="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="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 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="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="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 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="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 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="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>
</div>
-<!-- SECTION "FAQ et Documentations officielles du Projet" [1782-3579] -->
-<h2><a name="presentations" id="presentations">Présentations</a></h2>
+<!-- EDIT1599 SECTION "FAQ et Documentations officielles du Projet" [1782-3579] -->
+<h2 class="sectionedit1600"><a name="presentations" id="presentations">Présentations</a></h2>
<div class="level2">
<p>
-Ce sont les transparents de présentations effectués sur gEDA. Ils fournissent un bon survol pointu du projet pour ceux qui sont intéressés.
+Ce sont les transparents de présentations effectués sur gEDA. Ils fournissent un bon survol pointu du projet pour ceux qui sont intéressés.
+
</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">présentations</a>: Plusieurs discours et présentations à propos de gEDA.</div>
@@ -115,18 +102,19 @@ Ce sont les transparents de présentations effectués sur gEDA. Ils fournissent
</ul>
</div>
-<!-- SECTION "Présentations" [3580-3860] -->
-<h2><a name="a_propos_du_wiki" id="a_propos_du_wiki">Ã? propos du Wiki</a></h2>
+<!-- EDIT1600 SECTION "Présentations" [3580-3860] -->
+<h2 class="sectionedit1601"><a name="a_propos_du_wiki" id="a_propos_du_wiki">Ã? propos du Wiki</a></h2>
<div class="level2">
<p>
-Cette section du site gEDA est dédiée à la documentation fournie par plusieurs auteurs, y compris des utilisateurs. En particulier, il doit devenir une source dâ??information pour ceux qui débutent juste avec les outils.
+Cette section du site gEDA est dédiée à la documentation fournie par plusieurs auteurs, y compris des utilisateurs. En particulier, il doit devenir une source d'information pour ceux qui débutent juste avec les outils.
</p>
<p>
-Toutes les contributions sont les bienvenues. Mais contrairement à wikipedia, il nâ??y a pas de bouton pour créer un login seul. La raison est que personne de gEDA nâ??a les nerfs suffisamment solides pour traiter le vandalisme anonyme. Par conséquent, vous devez écrire un courriel à lâ??admin du site (ahvezda AT geda.seul.org) pour obtenir un accès. Il vous enverra un accès avec plaisir.
+Toutes les contributions sont les bienvenues. Mais contrairement à wikipedia, il n'y a pas de bouton pour créer un login seul. La raison est que personne de gEDA n'a les nerfs suffisamment solides pour traiter le vandalisme anonyme. Par conséquent, vous devez écrire un courriel à l'admin du site (ahvezda AT geda.seul.org) pour obtenir un accès. Il vous enverra un accès avec plaisir.
+
</p>
</div>
-<!-- SECTION "Ã? propos du Wiki" [3861-] --></body>
+<!-- EDIT1601 SECTION "Ã? propos du Wiki" [3861-] --></body>
</html>
diff --git a/docs/wiki/wiki-dokuwiki.html b/docs/wiki/wiki-dokuwiki.html
deleted file mode 100644
index aac904c..0000000
--- a/docs/wiki/wiki-dokuwiki.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>
-<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
deleted file mode 100644
index 156e0c2..0000000
--- a/docs/wiki/wiki-syntax.html
+++ /dev/null
@@ -1,666 +0,0 @@
-<!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: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><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: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: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></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>
commit cb0eaabe02c154e6fe95ac49dd638fd6057e9883
Author: Ales Hvezda <ahvezda@xxxxxxxx>
Commit: Ales Hvezda <ahvezda@xxxxxxxx>
Updated copyright data in gschem's about box
diff --git a/gschem/src/x_dialog.c b/gschem/src/x_dialog.c
index 4cd4c62..3b2b4be 100644
--- a/gschem/src/x_dialog.c
+++ b/gschem/src/x_dialog.c
@@ -2143,9 +2143,9 @@ void about_dialog (GSCHEM_TOPLEVEL *w_current)
"logo", logo,
"title", _("About gschem"),
"comments", _("gEDA: GPL Electronic Design Automation"),
- "copyright", _("Copyright © 1998-2009 Ales Hvezda"
+ "copyright", _("Copyright © 1998-2011 Ales Hvezda"
" <ahvezda@xxxxxxxxxxxxx>\n"
- "Copyright © 1998-2009 gEDA Contributors"
+ "Copyright © 1998-2011 gEDA Contributors"
" (see ChangeLog for details)"),
"website", "http://www.gpleda.org/";,
NULL);
commit 799d67452921ed1447e8b030ee268fe8c34c5785
Author: Ales Hvezda <ahvezda@xxxxxxxx>
Commit: Ales Hvezda <ahvezda@xxxxxxxx>
Updated version strings in all man pages
diff --git a/gattrib/docs/gattrib.1 b/gattrib/docs/gattrib.1
index 6096e1c..20ec6cf 100644
--- a/gattrib/docs/gattrib.1
+++ b/gattrib/docs/gattrib.1
@@ -1,4 +1,4 @@
-.TH gattrib 1 "January 5th, 2011" "gEDA Project" 1.6.1.20100214
+.TH gattrib 1 "January 16th, 2011" "gEDA Project" 1.7.0.20110116
.SH NAME
gattrib - gEDA/gaf Schematic Attribute Editor
.SH SYNOPSIS
diff --git a/gnetlist/docs/gnetlist.1 b/gnetlist/docs/gnetlist.1
index a20edb1..601d1f5 100644
--- a/gnetlist/docs/gnetlist.1
+++ b/gnetlist/docs/gnetlist.1
@@ -1,4 +1,4 @@
-.TH gnetlist 1 "January 5th, 2011" "gEDA Project" 1.6.1.20100214
+.TH gnetlist 1 "January 16th, 2011" "gEDA Project" 1.7.0.20110116
.SH NAME
gnetlist - gEDA/gaf Netlist Extraction and Generation
.SH SYNOPSIS
diff --git a/gschem/docs/gschem.1 b/gschem/docs/gschem.1
index 153b884..f198fa4 100644
--- a/gschem/docs/gschem.1
+++ b/gschem/docs/gschem.1
@@ -1,4 +1,4 @@
-.TH gschem 1 "January 5th, 2010" "gEDA Project" 1.6.1.20100214
+.TH gschem 1 "January 16th, 2011" "gEDA Project" 1.7.0.20110116
.SH NAME
gschem - gEDA/gaf Schematic Capture
.SH SYNOPSIS
diff --git a/gsymcheck/docs/gsymcheck.1 b/gsymcheck/docs/gsymcheck.1
index 9a0985a..e855b33 100644
--- a/gsymcheck/docs/gsymcheck.1
+++ b/gsymcheck/docs/gsymcheck.1
@@ -1,4 +1,4 @@
-.TH gsymcheck 1 "February 14th, 2010" Version 1.6.1.20100214
+.TH gsymcheck 1 "January 16th, 2011" "gEDA Project" 1.7.0.20110116
.SH NAME
gsymcheck - gEDA/gaf Symbol Checker
.SH SYNOPSIS
diff --git a/utils/docs/grenum.1 b/utils/docs/grenum.1
index 4bc1652..075c4ab 100644
--- a/utils/docs/grenum.1
+++ b/utils/docs/grenum.1
@@ -1,4 +1,4 @@
-.TH grenum 1 "February 14th, 2010" Version 1.6.1.20100214
+.TH grenum 1 "January 16th, 2011" "gEDA Project" 1.7.0.20110116
.SH NAME
.B grenum
diff --git a/utils/docs/gsch2pcb.1 b/utils/docs/gsch2pcb.1
index 9013896..8d90676 100644
--- a/utils/docs/gsch2pcb.1
+++ b/utils/docs/gsch2pcb.1
@@ -1,4 +1,4 @@
-.TH gsch2pcb 1 "January 5th, 2011" "gEDA Project" 1.6.1.20100214
+.TH gsch2pcb 1 "January 16th, 2011" "gEDA Project" 1.7.0.20110116
.SH NAME
gsch2pcb - Update PCB layouts from gEDA/gaf schematics
.SH SYNOPSIS
commit 2e2e2bf53458d6fea7e4c8dd7736818470fde248
Author: Ales Hvezda <ahvezda@xxxxxxxx>
Commit: Ales Hvezda <ahvezda@xxxxxxxx>
Manually ran make update-po in order to prep for the make distcheck
diff --git a/gattrib/po/ar.po b/gattrib/po/ar.po
index 6b8260c..9330bc8 100644
--- a/gattrib/po/ar.po
+++ b/gattrib/po/ar.po
@@ -6,7 +6,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2010-11-07 10:52+0000\n"
+"POT-Creation-Date: 2011-01-16 00:12-0500\n"
"PO-Revision-Date: 2010-02-08 18:58+0000\n"
"Last-Translator: عبداÙ?Ù?Ù? Ø´Ù?Ù? (Abdellah Chelli) <Unknown>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
diff --git a/gattrib/po/bg.po b/gattrib/po/bg.po
index 4f3aae9..5497432 100644
--- a/gattrib/po/bg.po
+++ b/gattrib/po/bg.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2010-11-07 10:52+0000\n"
+"POT-Creation-Date: 2011-01-16 00:12-0500\n"
"PO-Revision-Date: 2010-02-06 22:09+0000\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
diff --git a/gattrib/po/de.po b/gattrib/po/de.po
index 07f4773..933002f 100644
--- a/gattrib/po/de.po
+++ b/gattrib/po/de.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2010-11-07 10:52+0000\n"
+"POT-Creation-Date: 2011-01-16 00:12-0500\n"
"PO-Revision-Date: 2010-01-29 16:46+0000\n"
"Last-Translator: Werner Hoch <werner.ho@xxxxxx>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
diff --git a/gattrib/po/es.po b/gattrib/po/es.po
index 717665f..d5199b4 100644
--- a/gattrib/po/es.po
+++ b/gattrib/po/es.po
@@ -9,7 +9,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2010-11-07 10:52+0000\n"
+"POT-Creation-Date: 2011-01-16 00:12-0500\n"
"PO-Revision-Date: 2010-01-29 16:49+0000\n"
"Last-Translator: Carlos Nieves Ã?nega <Unknown>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
diff --git a/gattrib/po/fr.po b/gattrib/po/fr.po
index 0acdf84..acdc17f 100644
--- a/gattrib/po/fr.po
+++ b/gattrib/po/fr.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2010-11-07 10:52+0000\n"
+"POT-Creation-Date: 2011-01-16 00:12-0500\n"
"PO-Revision-Date: 2010-02-06 22:09+0000\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
diff --git a/gattrib/po/hu.po b/gattrib/po/hu.po
index 0e028b7..f6de63f 100644
--- a/gattrib/po/hu.po
+++ b/gattrib/po/hu.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2010-11-07 10:52+0000\n"
+"POT-Creation-Date: 2011-01-16 00:12-0500\n"
"PO-Revision-Date: 2010-02-06 22:10+0000\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
diff --git a/gattrib/po/it.po b/gattrib/po/it.po
index 25b3374..4204129 100644
--- a/gattrib/po/it.po
+++ b/gattrib/po/it.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2010-11-07 10:52+0000\n"
+"POT-Creation-Date: 2011-01-16 00:12-0500\n"
"PO-Revision-Date: 2010-02-06 22:09+0000\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
diff --git a/gattrib/po/ml.po b/gattrib/po/ml.po
index 9ff5c2d..955f78e 100644
--- a/gattrib/po/ml.po
+++ b/gattrib/po/ml.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2010-11-07 10:52+0000\n"
+"POT-Creation-Date: 2011-01-16 00:12-0500\n"
"PO-Revision-Date: 2010-02-06 22:10+0000\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
diff --git a/gattrib/po/nl.po b/gattrib/po/nl.po
index 01a858b..19802dd 100644
--- a/gattrib/po/nl.po
+++ b/gattrib/po/nl.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2010-11-07 10:52+0000\n"
+"POT-Creation-Date: 2011-01-16 00:12-0500\n"
"PO-Revision-Date: 2010-01-29 16:51+0000\n"
"Last-Translator: lambert63 <bert.timmerman@xxxxxxxxx>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
diff --git a/gattrib/po/pl.po b/gattrib/po/pl.po
index ff54c62..5520537 100644
--- a/gattrib/po/pl.po
+++ b/gattrib/po/pl.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2010-11-07 10:52+0000\n"
+"POT-Creation-Date: 2011-01-16 00:12-0500\n"
"PO-Revision-Date: 2010-02-06 22:09+0000\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
diff --git a/gattrib/po/pt.po b/gattrib/po/pt.po
index 019bd25..fe54074 100644
--- a/gattrib/po/pt.po
+++ b/gattrib/po/pt.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2010-11-07 10:52+0000\n"
+"POT-Creation-Date: 2011-01-16 00:12-0500\n"
"PO-Revision-Date: 2010-02-06 22:10+0000\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
diff --git a/gattrib/po/pt_BR.po b/gattrib/po/pt_BR.po
index a7c8ce0..72d64ce 100644
--- a/gattrib/po/pt_BR.po
+++ b/gattrib/po/pt_BR.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2010-11-07 10:52+0000\n"
+"POT-Creation-Date: 2011-01-16 00:12-0500\n"
"PO-Revision-Date: 2010-02-06 22:10+0000\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
diff --git a/gattrib/po/ru.po b/gattrib/po/ru.po
index 8f0e7da..3b8aa10 100644
--- a/gattrib/po/ru.po
+++ b/gattrib/po/ru.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2010-11-07 10:52+0000\n"
+"POT-Creation-Date: 2011-01-16 00:12-0500\n"
"PO-Revision-Date: 2010-01-29 15:51+0000\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
diff --git a/gattrib/po/tr.po b/gattrib/po/tr.po
index b7d4b37..e4ac29c 100644
--- a/gattrib/po/tr.po
+++ b/gattrib/po/tr.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2010-11-07 10:52+0000\n"
+"POT-Creation-Date: 2011-01-16 00:12-0500\n"
"PO-Revision-Date: 2010-02-06 22:09+0000\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
diff --git a/gattrib/po/zh_CN.po b/gattrib/po/zh_CN.po
index 28700a1..d1875a9 100644
--- a/gattrib/po/zh_CN.po
+++ b/gattrib/po/zh_CN.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2010-11-07 10:52+0000\n"
+"POT-Creation-Date: 2011-01-16 00:12-0500\n"
"PO-Revision-Date: 2010-02-06 22:10+0000\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
diff --git a/gattrib/po/zh_TW.po b/gattrib/po/zh_TW.po
index 5c10844..bdb511a 100644
--- a/gattrib/po/zh_TW.po
+++ b/gattrib/po/zh_TW.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2010-11-07 10:52+0000\n"
+"POT-Creation-Date: 2011-01-16 00:12-0500\n"
"PO-Revision-Date: 2010-02-06 22:10+0000\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
diff --git a/gschem/po/af.po b/gschem/po/af.po
index 5c14ad5..344fd37 100644
--- a/gschem/po/af.po
+++ b/gschem/po/af.po
@@ -6,7 +6,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda-gschem\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2010-11-07 13:37+0000\n"
+"POT-Creation-Date: 2011-01-16 00:11-0500\n"
"PO-Revision-Date: 2010-02-14 01:03+0000\n"
"Last-Translator: Bernd Jendrissek <Unknown>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -21,17 +21,17 @@ msgstr ""
msgid "Zoom too small! Cannot zoom further.\n"
msgstr "Zoem is te klein! Kan nie verder zoem nie.\n"
-#: gschem/src/g_funcs.c:339 gschem/src/i_callbacks.c:68
+#: gschem/src/g_funcs.c:347 gschem/src/i_callbacks.c:68
#, c-format
msgid "Could not fork\n"
msgstr "Kon nie vertak nie\n"
-#: gschem/src/g_funcs.c:355 gschem/src/i_callbacks.c:78
+#: gschem/src/g_funcs.c:363 gschem/src/i_callbacks.c:78
#, c-format
msgid "Could not invoke %s\n"
msgstr "Kon nie %s oproep nie\n"
-#: gschem/src/g_funcs.c:361 gschem/src/i_callbacks.c:82
+#: gschem/src/g_funcs.c:369 gschem/src/i_callbacks.c:82
msgid "Documentation commands not supported under MinGW.\n"
msgstr "Dokumentasieopdragte werk nie onder MinGW nie.\n"
@@ -120,13 +120,13 @@ msgstr "Ongeldige versterking [%d] gegee aan zoom-gain\n"
msgid "Invalid number of steps [%d] scrollpan-steps\n"
msgstr ""
-#: gschem/src/gschem.c:184
+#: gschem/src/gschem.c:188
#, c-format
msgid "gEDA/gschem version %s%s.%s\n"
msgstr "gEDA/gschem uitgawe %s%s.%s\n"
# FIXME: Best to get a real lawyer to translate this into Afrikaans legalese.
-#: gschem/src/gschem.c:187
+#: gschem/src/gschem.c:191
msgid ""
"gEDA/gschem comes with ABSOLUTELY NO WARRANTY; see COPYING for more "
"details.\n"
@@ -134,28 +134,28 @@ msgstr ""
"gEDA/gschem comes with ABSOLUTELY NO WARRANTY; see COPYING for more "
"details.\n"
-#: gschem/src/gschem.c:189
+#: gschem/src/gschem.c:193
msgid ""
"This is free software, and you are welcome to redistribute it under certain\n"
msgstr ""
-#: gschem/src/gschem.c:191
+#: gschem/src/gschem.c:195
msgid ""
"conditions; please see the COPYING file for more details.\n"
"\n"
msgstr ""
-#: gschem/src/gschem.c:194
+#: gschem/src/gschem.c:198
#, c-format
msgid "This is the MINGW32 port.\n"
msgstr ""
-#: gschem/src/gschem.c:198
+#: gschem/src/gschem.c:202
#, c-format
msgid "Current locale settings: %s\n"
msgstr ""
-#: gschem/src/gschem.c:213
+#: gschem/src/gschem.c:218
msgid ""
"You must set the GEDADATA environment variable!\n"
"\n"
@@ -163,31 +163,21 @@ msgid ""
"environment variable to point to the correct location.\n"
msgstr ""
-#: gschem/src/gschem.c:248
+#: gschem/src/gschem.c:256
#, c-format
msgid "Couldn't find init scm file [%s]\n"
msgstr ""
-#: gschem/src/gschem.c:252
+#: gschem/src/gschem.c:260
#, c-format
msgid "Read init scm file [%s]\n"
msgstr "Het scm-aanvangslêer [%s] gelees\n"
-#: gschem/src/gschem.c:256
+#: gschem/src/gschem.c:264
#, c-format
msgid "Failed to read init scm file [%s]\n"
msgstr "Het misluk of scm-aanvangslêer [%s] te lees\n"
-#: gschem/src/gschem.c:317
-#, c-format
-msgid "Scheme directory NOT set!\n"
-msgstr "Scheme-gids is NIE gestel nie!\n"
-
-#: gschem/src/gschem.c:324 gschem/src/x_script.c:66
-#, c-format
-msgid "Executing guile script [%s]\n"
-msgstr "Voer guile script [%s] uit\n"
-
#: gschem/src/gschem_cairo.c:310
#, c-format
msgid "Unknown end for line (%d)\n"
@@ -211,11 +201,11 @@ msgstr "Komponentmodus"
msgid "Text Mode"
msgstr "Teksmodues"
-#: gschem/src/i_basic.c:84 gschem/lib/system-gschemrc.scm:1409
+#: gschem/src/i_basic.c:84 gschem/lib/system-gschemrc.scm:1411
msgid "Copy Mode"
msgstr "Kopieermodus"
-#: gschem/src/i_basic.c:87 gschem/lib/system-gschemrc.scm:1411
+#: gschem/src/i_basic.c:87 gschem/lib/system-gschemrc.scm:1413
msgid "Move Mode"
msgstr "Skuifmodus"
@@ -223,7 +213,7 @@ msgstr "Skuifmodus"
msgid "Rotate Mode"
msgstr "Roteermodus"
-#: gschem/src/i_basic.c:91 gschem/lib/system-gschemrc.scm:1413
+#: gschem/src/i_basic.c:91 gschem/lib/system-gschemrc.scm:1415
msgid "Mirror Mode"
msgstr "Weerkaatsmodus"
@@ -276,22 +266,22 @@ msgstr "Boogmodus"
msgid "Pin Mode"
msgstr "Penmodus"
-#: gschem/src/i_basic.c:135 gschem/src/i_callbacks.c:544
-#: gschem/src/i_callbacks.c:568
+#: gschem/src/i_basic.c:135 gschem/src/i_callbacks.c:576
+#: gschem/src/i_callbacks.c:600
msgid "Copy"
msgstr "Kopieer"
-#: gschem/src/i_basic.c:137 gschem/src/i_callbacks.c:634
-#: gschem/src/i_callbacks.c:658
+#: gschem/src/i_basic.c:137 gschem/src/i_callbacks.c:666
+#: gschem/src/i_callbacks.c:690
msgid "Move"
msgstr "Beweeg"
-#: gschem/src/i_basic.c:139 gschem/src/i_callbacks.c:589
-#: gschem/src/i_callbacks.c:613
+#: gschem/src/i_basic.c:139 gschem/src/i_callbacks.c:621
+#: gschem/src/i_callbacks.c:645
msgid "Multiple Copy"
msgstr "Veelvoudige Kopieer"
-#: gschem/src/i_basic.c:142 gschem/lib/system-gschemrc.scm:1410
+#: gschem/src/i_basic.c:142 gschem/lib/system-gschemrc.scm:1412
msgid "Multiple Copy Mode"
msgstr "Meervoudige Kopieermodus"
@@ -311,7 +301,7 @@ msgstr ""
msgid "Action"
msgstr "Handeling"
-#: gschem/src/i_basic.c:260 gschem/src/x_dialog.c:2312
+#: gschem/src/i_basic.c:260 gschem/src/x_dialog.c:2316
#: gschem/src/x_window.c:491
msgid "Stroke"
msgstr "Wyserslag"
@@ -342,7 +332,7 @@ msgstr "Rooster(%s, %s)"
msgid "Documentation for [%s,%s,%s,%s]\n"
msgstr "Documentasie vir [%s,%s,%s,%s]\n"
-#: gschem/src/i_callbacks.c:123 gschem/src/i_callbacks.c:1699
+#: gschem/src/i_callbacks.c:123 gschem/src/i_callbacks.c:1706
#, c-format
msgid "New page created [%s]\n"
msgstr "Nuwe bladsy geskep [%s]\n"
@@ -364,246 +354,242 @@ msgstr "Alles Bewaar"
msgid "Closing Window\n"
msgstr "Sluit Venster\n"
-#: gschem/src/i_callbacks.c:549 gschem/src/i_callbacks.c:594
-#: gschem/src/i_callbacks.c:639
+#: gschem/src/i_callbacks.c:581 gschem/src/i_callbacks.c:626
+#: gschem/src/i_callbacks.c:671
msgid "Select objs first"
msgstr "Kies eers voorwerpe"
-#: gschem/src/i_callbacks.c:678 gschem/src/x_multiattrib.c:1491
+#: gschem/src/i_callbacks.c:710 gschem/src/x_multiattrib.c:1503
msgid "Delete"
msgstr "Verwyder"
-#: gschem/src/i_callbacks.c:703
+#: gschem/src/i_callbacks.c:735
msgid "Edit"
msgstr "Bewerk"
-#: gschem/src/i_callbacks.c:718
+#: gschem/src/i_callbacks.c:750
msgid "Edit pin type"
msgstr ""
-#: gschem/src/i_callbacks.c:737
+#: gschem/src/i_callbacks.c:769
msgid "Edit Text"
msgstr "Bewerk Teks"
-#: gschem/src/i_callbacks.c:760
+#: gschem/src/i_callbacks.c:792
msgid "Slot"
msgstr "Gleuf"
-#: gschem/src/i_callbacks.c:777
+#: gschem/src/i_callbacks.c:809
msgid "Color"
msgstr "Kleur"
-#: gschem/src/i_callbacks.c:814 gschem/src/i_callbacks.c:859
+#: gschem/src/i_callbacks.c:846 gschem/src/i_callbacks.c:891
msgid "Rotate"
msgstr "Roteer"
-#: gschem/src/i_callbacks.c:882 gschem/src/i_callbacks.c:907
+#: gschem/src/i_callbacks.c:913 gschem/src/i_callbacks.c:938
msgid "Mirror"
msgstr "Weerkaats"
-#: gschem/src/i_callbacks.c:928 gschem/src/x_dialog.c:2315
-#: gschem/lib/system-gschemrc.scm:1422
+#: gschem/src/i_callbacks.c:959 gschem/src/x_dialog.c:2319
+#: gschem/lib/system-gschemrc.scm:1424
msgid "Lock"
msgstr "Sluit"
-#: gschem/src/i_callbacks.c:946 gschem/lib/system-gschemrc.scm:1423
+#: gschem/src/i_callbacks.c:977 gschem/lib/system-gschemrc.scm:1425
msgid "Unlock"
msgstr "Ontsluit"
-#: gschem/src/i_callbacks.c:964 gschem/src/x_dialog.c:1734
+#: gschem/src/i_callbacks.c:995 gschem/src/x_dialog.c:1737
msgid "Translate"
msgstr "Verskuif"
-#: gschem/src/i_callbacks.c:967
+#: gschem/src/i_callbacks.c:998
msgid "WARNING: Do not translate with snap off!\n"
msgstr ""
-#: gschem/src/i_callbacks.c:968
+#: gschem/src/i_callbacks.c:999
msgid "WARNING: Turning snap on and continuing with translate.\n"
msgstr ""
-#: gschem/src/i_callbacks.c:975
+#: gschem/src/i_callbacks.c:1006
msgid "WARNING: Snap grid size is not equal to 100!\n"
msgstr ""
-#: gschem/src/i_callbacks.c:977
+#: gschem/src/i_callbacks.c:1008
msgid ""
"WARNING: If you are translating a symbol to the origin, the snap grid size "
"should be set to 100\n"
msgstr ""
-#: gschem/src/i_callbacks.c:1008
+#: gschem/src/i_callbacks.c:1039
msgid "Embed"
msgstr "Lê In"
# FIXME: too klunky!
-#: gschem/src/i_callbacks.c:1047
+#: gschem/src/i_callbacks.c:1078
msgid "Unembed"
msgstr "Ont-lê In"
-#: gschem/src/i_callbacks.c:1089
+#: gschem/src/i_callbacks.c:1120
msgid "Update"
msgstr ""
-#: gschem/src/i_callbacks.c:1136
+#: gschem/src/i_callbacks.c:1167
msgid "ShowHidden"
msgstr "ToonVerskuil"
-#: gschem/src/i_callbacks.c:1160
-msgid "MakeVisible"
-msgstr "MaakSigbaar"
-
-#: gschem/src/i_callbacks.c:1466 gschem/src/i_callbacks.c:1538
+#: gschem/src/i_callbacks.c:1473 gschem/src/i_callbacks.c:1545
msgid "Pan"
msgstr "Skuif Aansig"
-#: gschem/src/i_callbacks.c:1743
+#: gschem/src/i_callbacks.c:1750
msgid "Really revert page?"
msgstr ""
-#: gschem/src/i_callbacks.c:1813
+#: gschem/src/i_callbacks.c:1820
msgid "Copy to clipboard"
msgstr ""
-#: gschem/src/i_callbacks.c:1831
+#: gschem/src/i_callbacks.c:1838
msgid "Cut to clipboard"
msgstr ""
-#: gschem/src/i_callbacks.c:1849
+#: gschem/src/i_callbacks.c:1856
msgid "Paste from clipboard"
msgstr ""
-#: gschem/src/i_callbacks.c:1861 gschem/src/i_callbacks.c:2100
-#: gschem/src/i_callbacks.c:2122 gschem/src/i_callbacks.c:2144
-#: gschem/src/i_callbacks.c:2166 gschem/src/i_callbacks.c:2188
+#: gschem/src/i_callbacks.c:1868 gschem/src/i_callbacks.c:2107
+#: gschem/src/i_callbacks.c:2129 gschem/src/i_callbacks.c:2151
+#: gschem/src/i_callbacks.c:2173 gschem/src/i_callbacks.c:2195
msgid "Empty buffer"
msgstr "Maak buffer leeg"
-#: gschem/src/i_callbacks.c:1906
+#: gschem/src/i_callbacks.c:1913
msgid "Copy 1"
msgstr "Kopieer 1"
-#: gschem/src/i_callbacks.c:1925
+#: gschem/src/i_callbacks.c:1932
msgid "Copy 2"
msgstr "Kopieer 2"
-#: gschem/src/i_callbacks.c:1944
+#: gschem/src/i_callbacks.c:1951
msgid "Copy 3"
msgstr "Kopieer 3"
-#: gschem/src/i_callbacks.c:1963
+#: gschem/src/i_callbacks.c:1970
msgid "Copy 4"
msgstr "Kopieer 4"
-#: gschem/src/i_callbacks.c:1982
+#: gschem/src/i_callbacks.c:1989
msgid "Copy 5"
msgstr "Kopieer 5"
-#: gschem/src/i_callbacks.c:2001
+#: gschem/src/i_callbacks.c:2008
msgid "Cut 1"
msgstr "Sny 1"
-#: gschem/src/i_callbacks.c:2020
+#: gschem/src/i_callbacks.c:2027
msgid "Cut 2"
msgstr "Sny 2"
-#: gschem/src/i_callbacks.c:2039
+#: gschem/src/i_callbacks.c:2046
msgid "Cut 3"
msgstr "Sny 3"
-#: gschem/src/i_callbacks.c:2058
+#: gschem/src/i_callbacks.c:2065
msgid "Cut 4"
msgstr "Sny 4"
-#: gschem/src/i_callbacks.c:2077
+#: gschem/src/i_callbacks.c:2084
msgid "Cut 5"
msgstr "Sny 5"
-#: gschem/src/i_callbacks.c:2093
+#: gschem/src/i_callbacks.c:2100
msgid "Paste 1"
msgstr "Plak 1"
-#: gschem/src/i_callbacks.c:2115
+#: gschem/src/i_callbacks.c:2122
msgid "Paste 2"
msgstr "Plak 2"
-#: gschem/src/i_callbacks.c:2137
+#: gschem/src/i_callbacks.c:2144
msgid "Paste 3"
msgstr "Plak 3"
-#: gschem/src/i_callbacks.c:2159
+#: gschem/src/i_callbacks.c:2166
msgid "Paste 4"
msgstr "Plak 4"
-#: gschem/src/i_callbacks.c:2181
+#: gschem/src/i_callbacks.c:2188
msgid "Paste 5"
msgstr "Plak 5"
-#: gschem/src/i_callbacks.c:2318 gschem/src/x_window.c:355
+#: gschem/src/i_callbacks.c:2325 gschem/src/x_window.c:355
msgid "Component"
msgstr "Komponent"
-#: gschem/src/i_callbacks.c:2354 gschem/src/i_callbacks.c:2373
-#: gschem/src/x_dialog.c:2285
+#: gschem/src/i_callbacks.c:2361 gschem/src/i_callbacks.c:2380
+#: gschem/src/x_dialog.c:2289
msgid "Attribute"
msgstr "Eienskap"
-#: gschem/src/i_callbacks.c:2395 gschem/src/i_callbacks.c:2422
-#: gschem/src/x_dialog.c:2282
+#: gschem/src/i_callbacks.c:2402 gschem/src/i_callbacks.c:2429
+#: gschem/src/x_dialog.c:2286
msgid "Net"
msgstr "Skakeling"
-#: gschem/src/i_callbacks.c:2466 gschem/src/i_callbacks.c:2493
-#: gschem/src/x_dialog.c:2300 gschem/src/x_window.c:375
+#: gschem/src/i_callbacks.c:2473 gschem/src/i_callbacks.c:2500
+#: gschem/src/x_dialog.c:2304 gschem/src/x_window.c:375
msgid "Bus"
msgstr "Bus"
-#: gschem/src/i_callbacks.c:2574 gschem/src/i_callbacks.c:2597
+#: gschem/src/i_callbacks.c:2581 gschem/src/i_callbacks.c:2604
msgid "Line"
msgstr "Lyn"
-#: gschem/src/i_callbacks.c:2619 gschem/src/i_callbacks.c:2642
+#: gschem/src/i_callbacks.c:2626 gschem/src/i_callbacks.c:2649
msgid "Box"
msgstr "Reghoek"
-#: gschem/src/i_callbacks.c:2698 gschem/src/i_callbacks.c:2722
+#: gschem/src/i_callbacks.c:2705 gschem/src/i_callbacks.c:2729
msgid "Circle"
msgstr "Sirkel"
-#: gschem/src/i_callbacks.c:2744 gschem/src/i_callbacks.c:2767
+#: gschem/src/i_callbacks.c:2751 gschem/src/i_callbacks.c:2774
msgid "Arc"
msgstr "Boog"
-#: gschem/src/i_callbacks.c:2789 gschem/src/i_callbacks.c:2812
-#: gschem/src/x_dialog.c:2273
+#: gschem/src/i_callbacks.c:2796 gschem/src/i_callbacks.c:2819
+#: gschem/src/x_dialog.c:2277
msgid "Pin"
msgstr "Pen"
-#: gschem/src/i_callbacks.c:2871
+#: gschem/src/i_callbacks.c:2878
#, c-format
msgid "Searching for source [%s]\n"
msgstr "Soek vir bron [%s]\n"
-#: gschem/src/i_callbacks.c:2895
+#: gschem/src/i_callbacks.c:2902
#, c-format
msgid "Cannot find source [%s]\n"
msgstr "Kan nie bron [%s] vind nie\n"
-#: gschem/src/i_callbacks.c:2964
+#: gschem/src/i_callbacks.c:2965
#, c-format
msgid "Searching for symbol [%s]\n"
msgstr "Soek vir simbool [%s]\n"
-#: gschem/src/i_callbacks.c:2970
+#: gschem/src/i_callbacks.c:2971
msgid "Symbol is not a real file. Symbol cannot be loaded.\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3001
+#: gschem/src/i_callbacks.c:3002
msgid "Cannot find any schematics above the current one!\n"
msgstr ""
# FIXME: "aangeduide".
-#: gschem/src/i_callbacks.c:3055
+#: gschem/src/i_callbacks.c:3056
msgid ""
"This command retrieves the component documentation from the web, but there "
"is no component selected"
@@ -611,84 +597,84 @@ msgstr ""
"Hierdie opdrag haal die komponentdokumentasie van die web, maar daar is geen "
"aangeduide komponent nie"
-#: gschem/src/i_callbacks.c:3083
+#: gschem/src/i_callbacks.c:3084
msgid "Attach"
msgstr "Heg aan"
-#: gschem/src/i_callbacks.c:3130
+#: gschem/src/i_callbacks.c:3131
msgid "Detach"
msgstr "Heg af"
-#: gschem/src/i_callbacks.c:3165
+#: gschem/src/i_callbacks.c:3166
msgid "ShowN"
msgstr "ToonN"
-#: gschem/src/i_callbacks.c:3201
+#: gschem/src/i_callbacks.c:3202
msgid "ShowV"
msgstr "ToonW"
-#: gschem/src/i_callbacks.c:3237
+#: gschem/src/i_callbacks.c:3238
msgid "ShowB"
msgstr "ToonB"
-#: gschem/src/i_callbacks.c:3274
+#: gschem/src/i_callbacks.c:3275
msgid "VisToggle"
msgstr "SigSkakel"
-#: gschem/src/i_callbacks.c:3304
+#: gschem/src/i_callbacks.c:3305
#, c-format
msgid "Sorry but this is a non-functioning menu option\n"
msgstr "Jammer, maar hierdie opsie werk nie\n"
-#: gschem/src/i_callbacks.c:3394
+#: gschem/src/i_callbacks.c:3395
msgid "Action feedback mode set to OUTLINE\n"
msgstr "Handelingsterugvoermodus na SKETS gestel\n"
-#: gschem/src/i_callbacks.c:3397
+#: gschem/src/i_callbacks.c:3398
msgid "Action feedback mode set to BOUNDINGBOX\n"
msgstr "Handelingsterugvoermodus na OMTREKREGHOEK\n"
-#: gschem/src/i_callbacks.c:3422
+#: gschem/src/i_callbacks.c:3423
msgid "Grid OFF\n"
msgstr "Rooster AF\n"
-#: gschem/src/i_callbacks.c:3423
+#: gschem/src/i_callbacks.c:3424
msgid "Dot grid selected\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3424
+#: gschem/src/i_callbacks.c:3425
msgid "Mesh grid selected\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3445
+#: gschem/src/i_callbacks.c:3446
msgid "Snap OFF (CAUTION!)\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3448
+#: gschem/src/i_callbacks.c:3449
msgid "Snap ON\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3451
+#: gschem/src/i_callbacks.c:3452
msgid "Snap back to the grid (CAUTION!)\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3477
+#: gschem/src/i_callbacks.c:3478
msgid "Rubber band OFF \n"
msgstr "Rubberband AF \n"
-#: gschem/src/i_callbacks.c:3480
+#: gschem/src/i_callbacks.c:3481
msgid "Rubber band ON\n"
msgstr "Rubberband AAN\n"
-#: gschem/src/i_callbacks.c:3495
+#: gschem/src/i_callbacks.c:3496
msgid "magnetic net mode: ON\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3498
+#: gschem/src/i_callbacks.c:3499
msgid "magnetic net mode: OFF\n"
msgstr ""
-#: gschem/src/o_box.c:153
+#: gschem/src/o_box.c:149
#, c-format
msgid "Unknown type for box (fill)!\n"
msgstr "Onbekende tipe vir reghoek (vul)!\n"
@@ -708,17 +694,17 @@ msgstr ""
msgid "Got an invalid buffer_number [o_buffer_paste_start]\n"
msgstr "Het 'n ongeldige buffer_number gekry [o_buffer_paste_start]\n"
-#: gschem/src/o_bus.c:118
+#: gschem/src/o_bus.c:117
#, c-format
msgid "Got an invalid which one in o_bus_draw_stretch\n"
msgstr "Het 'n ongeldige whichone in o_bus_draw_stretch gekry\n"
-#: gschem/src/o_circle.c:134
+#: gschem/src/o_circle.c:130
#, c-format
msgid "Unknown type for circle (fill)!\n"
msgstr "Onbekende tipe vir sirkel (vul)!\n"
-#: gschem/src/o_complex.c:243 gschem/src/o_complex.c:247
+#: gschem/src/o_complex.c:237 gschem/src/o_complex.c:241
#, c-format
msgid "Translating schematic [%d %d]\n"
msgstr "Verskuif stroombaandiagram [%d %d]\n"
@@ -736,35 +722,35 @@ msgstr "Voorwerp klaar gesluit\n"
msgid "Object already unlocked\n"
msgstr "Voorwerp klaar ontsluit\n"
-#: gschem/src/o_misc.c:413
+#: gschem/src/o_misc.c:409
msgid "Hidden text is now visible\n"
msgstr "Verskuilde teks is nou sigbaar\n"
-#: gschem/src/o_misc.c:415
+#: gschem/src/o_misc.c:411
msgid "Hidden text is now invisible\n"
msgstr "Verskuilde teks is nou onsigbaar\n"
-#: gschem/src/o_misc.c:668
+#: gschem/src/o_misc.c:636
#, c-format
msgid "Could not find symbol [%s] in library. Update failed.\n"
msgstr ""
-#: gschem/src/o_misc.c:783
+#: gschem/src/o_misc.c:751
#, c-format
msgid "o_autosave_backups: Can't get the real filename of %s."
msgstr "o_autosave_backups: Kan nie die egte lêernaam van %s kry nie."
-#: gschem/src/o_misc.c:827
+#: gschem/src/o_misc.c:795
#, c-format
msgid "Could NOT set previous backup file [%s] read-write\n"
msgstr "Kon NIE vorige bestandlêer [%s] lees-skryf stel nie\n"
-#: gschem/src/o_misc.c:845
+#: gschem/src/o_misc.c:815
#, c-format
msgid "Could NOT set backup file [%s] readonly\n"
msgstr "Kon NIE bestandlêer [%s] lees-slegs stel nie\n"
-#: gschem/src/o_misc.c:850
+#: gschem/src/o_misc.c:820
#, c-format
msgid "Could NOT save backup file [%s]\n"
msgstr "Kon NIE bestandlêer [%s] bewaar nie\n"
@@ -786,37 +772,37 @@ msgstr ""
msgid "Got a non line object in o_move_check_endpoint\n"
msgstr "Het 'n voorwerp wat nie 'n lyn is nie in o_move_check_endpoint gekry\n"
-#: gschem/src/o_net.c:159
+#: gschem/src/o_net.c:158
#, c-format
msgid "Got an invalid which one in o_net_draw_stretch\n"
msgstr "Het 'n ongeldige whichone in o_net_draw_stretch gekry\n"
-#: gschem/src/o_net.c:538
+#: gschem/src/o_net.c:537
msgid "Warning: Starting net at off grid coordinate\n"
msgstr ""
-#: gschem/src/o_net.c:600
+#: gschem/src/o_net.c:599
msgid "Warning: Ending net at off grid coordinate\n"
msgstr ""
-#: gschem/src/o_net.c:932 gschem/src/o_net.c:969 gschem/src/o_net.c:1040
-#: gschem/src/o_net.c:1076
+#: gschem/src/o_net.c:931 gschem/src/o_net.c:968 gschem/src/o_net.c:1039
+#: gschem/src/o_net.c:1075
#, c-format
msgid "Tried to add more than two bus rippers. Internal gschem error.\n"
msgstr ""
"Het probeer om meer as twee busrippers bytevoeg. Interne gschem fout.\n"
-#: gschem/src/o_net.c:1144
+#: gschem/src/o_net.c:1143
#, c-format
msgid "Bus ripper symbol [%s] was not found in any component library\n"
msgstr "Busrippersimbool [%s] is nie in enige komponentbiblioteek gevind nie\n"
-#: gschem/src/o_path.c:352
+#: gschem/src/o_path.c:348
#, c-format
msgid "Unknown type for path (fill)!\n"
msgstr ""
-#: gschem/src/o_picture.c:163 gschem/src/o_picture.c:539
+#: gschem/src/o_picture.c:163 gschem/src/o_picture.c:537
#, c-format
msgid "Failed to load picture: %s"
msgstr "Kon nie afbeelding laai nie: %s"
@@ -825,7 +811,7 @@ msgstr "Kon nie afbeelding laai nie: %s"
msgid "Picture"
msgstr "Afbeelding"
-#: gschem/src/o_picture.c:447 gschem/src/x_attribedit.c:141
+#: gschem/src/o_picture.c:445 gschem/src/x_attribedit.c:141
#, c-format
msgid "ERROR: NULL object!\n"
msgstr "FOUT: NULL voorwerp!\n"
@@ -846,23 +832,45 @@ msgstr "Gleuwe is nie toegelaat vir hierdie komponent nie\n"
msgid "New slot number out of range\n"
msgstr "Nuwe gleufnommer buite bereik\n"
-#: gschem/src/o_undo.c:304
+#: gschem/src/o_undo.c:303
msgid "Undo/Redo disabled in rc file\n"
msgstr ""
-#: gschem/src/parsecmd.c:47
+#: gschem/src/parsecmd.c:81
#, c-format
msgid ""
-"Usage: %s [OPTIONS] schematic_filename1 ... schematic_filenameN\n"
-" -q Quiet mode\n"
-" -v Verbose mode on\n"
-" -r filename Rc filename\n"
-" -s filename Script (guile) filename\n"
-" -o filename Output filename (for printing)\n"
-" -p Automatically place the window\n"
-" -t Print stroke information\n"
-" -h Help; this message\n"
+"Usage: %s [OPTION ...] [--] [FILE ...]\n"
+"\n"
+"Interactively edit gEDA schematics or symbols. If one or more FILEs\n"
+"are specified, open them for editing; otherwise, create a new, empty\n"
+"schematic.\n"
"\n"
+"Options:\n"
+" -q, --quiet Quiet mode.\n"
+" -v, --verbose Verbose mode.\n"
+" -r, --config-file=FILE Additional configuration file to load.\n"
+" -L DIR Add DIR to Scheme search path.\n"
+" -c EXPR Scheme expression to run at startup.\n"
+" -s FILE Scheme script to run at startup.\n"
+" -o, --output=FILE Output filename (for printing).\n"
+" -p Automatically place the window.\n"
+" -V, --version Show version information.\n"
+" -h, --help Help; this message.\n"
+" -- Treat all remaining arguments as filenames.\n"
+"\n"
+"Report bugs to <geda-bug@xxxxxxxx>\n"
+"gEDA/gaf homepage: <http://gpleda.org>\n"
+msgstr ""
+
+#: gschem/src/parsecmd.c:115
+#, c-format
+msgid ""
+"gEDA %s (g%.7s)\n"
+"Copyright (C) 1998-2011 gEDA developers\n"
+"This is free software, and you are welcome to redistribute it under\n"
+"certain conditions. For details, see the file `COPYING', which is\n"
+"included in the gEDA distribution.\n"
+"There is NO WARRANTY, to the extent permitted by law.\n"
msgstr ""
#: gschem/src/x_attribedit.c:127
@@ -874,57 +882,57 @@ msgstr ""
msgid "Single Attribute Editor"
msgstr "Enkeleienskap-Bewerker"
-#: gschem/src/x_attribedit.c:358
+#: gschem/src/x_attribedit.c:359
msgid "<b>Edit Attribute</b>"
msgstr "<b>Bewerk Eienskap</b>"
-#: gschem/src/x_attribedit.c:360
+#: gschem/src/x_attribedit.c:361
msgid "<b>Add Attribute</b>"
msgstr "<b>Voeg Eienskap By</b>"
-#: gschem/src/x_attribedit.c:376 gschem/src/x_multiattrib.c:1916
+#: gschem/src/x_attribedit.c:377 gschem/src/x_multiattrib.c:1927
msgid "Name:"
msgstr "Naam:"
-#: gschem/src/x_attribedit.c:393 gschem/src/x_multiattrib.c:1935
+#: gschem/src/x_attribedit.c:394 gschem/src/x_multiattrib.c:1946
msgid "Value:"
msgstr "Waarde:"
-#: gschem/src/x_attribedit.c:409 gschem/src/x_multiattrib.c:1978
+#: gschem/src/x_attribedit.c:410 gschem/src/x_multiattrib.c:1989
msgid "Visible"
msgstr "Sigbaar"
-#: gschem/src/x_attribedit.c:429
+#: gschem/src/x_attribedit.c:430
msgid "Show Value Only"
msgstr "Toon Slegs Waarde"
-#: gschem/src/x_attribedit.c:431
+#: gschem/src/x_attribedit.c:432
msgid "Show Name Only"
msgstr "Toon Slegs Naam"
-#: gschem/src/x_attribedit.c:433 gschem/src/x_multiattrib.c:1454
+#: gschem/src/x_attribedit.c:434 gschem/src/x_multiattrib.c:1466
msgid "Show Name & Value"
msgstr "Toon Naam & Waarde"
-#: gschem/src/x_attribedit.c:440
+#: gschem/src/x_attribedit.c:441
msgid "<b>Attach Options</b>"
msgstr "<b>AAnhegopsies</b>"
-#: gschem/src/x_attribedit.c:455
+#: gschem/src/x_attribedit.c:456
msgid "All"
msgstr "Alles"
-#: gschem/src/x_attribedit.c:463 gschem/src/x_compselect.c:896
-#: gschem/src/x_compselect.c:1010
+#: gschem/src/x_attribedit.c:464 gschem/src/x_compselect.c:904
+#: gschem/src/x_compselect.c:1018
msgid "Components"
msgstr "Komponente"
# FIXME: "Nette"
-#: gschem/src/x_attribedit.c:471 gschem/src/x_window.c:365
+#: gschem/src/x_attribedit.c:472 gschem/src/x_window.c:365
msgid "Nets"
msgstr "Nette"
-#: gschem/src/x_attribedit.c:479
+#: gschem/src/x_attribedit.c:480
msgid "Replace existing attributes"
msgstr "Vervang bestaande eienskappe"
@@ -941,91 +949,91 @@ msgid ""
msgstr ""
"duplikaatgleuf mag probleme veroorsaak: [symbolname=%s, number=%d, slot=%d]\n"
-#: gschem/src/x_autonumber.c:673
+#: gschem/src/x_autonumber.c:675
msgid "No searchstring given in autonumber text.\n"
msgstr ""
-#: gschem/src/x_autonumber.c:725
+#: gschem/src/x_autonumber.c:727
msgid "No '*' or '?' given at the end of the autonumber text.\n"
msgstr ""
-#: gschem/src/x_autonumber.c:860
+#: gschem/src/x_autonumber.c:862
msgid "Diagonal"
msgstr "Diagonaal"
-#: gschem/src/x_autonumber.c:861
+#: gschem/src/x_autonumber.c:863
msgid "Top to bottom"
msgstr "Bo to onder"
-#: gschem/src/x_autonumber.c:861
+#: gschem/src/x_autonumber.c:863
msgid "Bottom to top"
msgstr "Onder tot bo"
-#: gschem/src/x_autonumber.c:862
+#: gschem/src/x_autonumber.c:864
msgid "Left to right"
msgstr "Links tot regs"
-#: gschem/src/x_autonumber.c:862
+#: gschem/src/x_autonumber.c:864
msgid "Right to left"
msgstr "Regs tot links"
-#: gschem/src/x_autonumber.c:863
+#: gschem/src/x_autonumber.c:865
msgid "File order"
msgstr "Lêerorde"
-#: gschem/src/x_autonumber.c:1199
+#: gschem/src/x_autonumber.c:1201
msgid "Autonumber text"
msgstr ""
-#: gschem/src/x_autonumber.c:1223
+#: gschem/src/x_autonumber.c:1225
msgid "<b>Scope</b>"
msgstr "<b>Bestek</b>"
-#: gschem/src/x_autonumber.c:1245
+#: gschem/src/x_autonumber.c:1247
msgid "Search for:"
msgstr "Soek vir:"
-#: gschem/src/x_autonumber.c:1259
+#: gschem/src/x_autonumber.c:1261
msgid "Autonumber text in:"
msgstr ""
-#: gschem/src/x_autonumber.c:1266
+#: gschem/src/x_autonumber.c:1268
msgid "Skip numbers found in:"
msgstr "Slaan nommers oor in:"
-#: gschem/src/x_autonumber.c:1278 gschem/src/x_autonumber.c:1287
+#: gschem/src/x_autonumber.c:1280 gschem/src/x_autonumber.c:1289
msgid "Selected objects"
msgstr ""
-#: gschem/src/x_autonumber.c:1279 gschem/src/x_autonumber.c:1288
+#: gschem/src/x_autonumber.c:1281 gschem/src/x_autonumber.c:1290
msgid "Current page"
msgstr "Lopende bladsy"
-#: gschem/src/x_autonumber.c:1280 gschem/src/x_autonumber.c:1289
+#: gschem/src/x_autonumber.c:1282 gschem/src/x_autonumber.c:1291
msgid "Whole hierarchy"
msgstr "Hele hierargie"
-#: gschem/src/x_autonumber.c:1291
+#: gschem/src/x_autonumber.c:1293
msgid "Overwrite existing numbers"
msgstr "Vervang bestaande nommers"
-#: gschem/src/x_autonumber.c:1296
+#: gschem/src/x_autonumber.c:1298
msgid "<b>Options</b>"
msgstr "<b>Opsies</b>"
-#: gschem/src/x_autonumber.c:1318
+#: gschem/src/x_autonumber.c:1320
msgid "Starting number:"
msgstr "Begin by nommer:"
-#: gschem/src/x_autonumber.c:1325
+#: gschem/src/x_autonumber.c:1327
msgid "Sort order:"
msgstr "Rangskikkingsorde:"
-#: gschem/src/x_autonumber.c:1346
+#: gschem/src/x_autonumber.c:1348
msgid "Remove numbers"
msgstr "Verwyder syfers"
-#: gschem/src/x_autonumber.c:1350
+#: gschem/src/x_autonumber.c:1352
msgid "Automatic slotting"
msgstr "Outomatiese begleuwing"
@@ -1062,48 +1070,48 @@ msgstr "Het probeer om 'n ongeldige kleur te kry: %d\n"
msgid "Tried to get an invalid outline color: %d\n"
msgstr ""
-#: gschem/src/x_compselect.c:1040
+#: gschem/src/x_compselect.c:1048
msgid "Filter:"
msgstr "Deursyfer:"
-#: gschem/src/x_compselect.c:1143 gschem/src/x_dialog.c:3663
-#: gschem/src/x_multiattrib.c:1782
+#: gschem/src/x_compselect.c:1151 gschem/src/x_dialog.c:3667
+#: gschem/src/x_multiattrib.c:1793
msgid "Name"
msgstr "Naam"
-#: gschem/src/x_compselect.c:1152 gschem/src/x_multiattrib.c:1806
+#: gschem/src/x_compselect.c:1160 gschem/src/x_multiattrib.c:1817
msgid "Value"
msgstr "Waarde"
-#: gschem/src/x_compselect.c:1191
+#: gschem/src/x_compselect.c:1199
msgid "Default behavior - reference component"
msgstr "Verstekgedrag - verwys na komponent"
-#: gschem/src/x_compselect.c:1194
+#: gschem/src/x_compselect.c:1202
msgid "Embed component in schematic"
msgstr "Lê komponent in stroombaandiagram in"
-#: gschem/src/x_compselect.c:1197
+#: gschem/src/x_compselect.c:1205
msgid "Include component as individual objects"
msgstr "Sluit komponent as afsonderlike voorwerpe in"
-#: gschem/src/x_compselect.c:1354
+#: gschem/src/x_compselect.c:1362
msgid "Select Component..."
msgstr "Kies Komponent..."
-#: gschem/src/x_compselect.c:1377
+#: gschem/src/x_compselect.c:1385
msgid "In Use"
msgstr "In Gebruik"
-#: gschem/src/x_compselect.c:1381
+#: gschem/src/x_compselect.c:1389
msgid "Libraries"
msgstr "Biblioteke"
-#: gschem/src/x_compselect.c:1390 gschem/src/x_fileselect.c:122
+#: gschem/src/x_compselect.c:1398 gschem/src/x_fileselect.c:122
msgid "Preview"
msgstr "Voorskou"
-#: gschem/src/x_compselect.c:1418
+#: gschem/src/x_compselect.c:1426
msgid "Attributes"
msgstr "Eienskappe"
@@ -1158,139 +1166,139 @@ msgstr "Regs Onder"
msgid "Edit Text Properties"
msgstr "Bewerk Tekseienskappe"
-#: gschem/src/x_dialog.c:471
+#: gschem/src/x_dialog.c:472
msgid "<b>Text Content</b>"
msgstr "<b>Teksinhoud</b>"
-#: gschem/src/x_dialog.c:507
+#: gschem/src/x_dialog.c:508
msgid "<b>Text Properties</b>"
msgstr "<b>Tekseienskappe</b>"
-#: gschem/src/x_dialog.c:522
+#: gschem/src/x_dialog.c:523
msgid "Color:"
msgstr "Kleur:"
-#: gschem/src/x_dialog.c:529
+#: gschem/src/x_dialog.c:530
msgid "Size:"
msgstr "Grootte:"
-#: gschem/src/x_dialog.c:538
+#: gschem/src/x_dialog.c:539
msgid "Alignment:"
msgstr "Sporing:"
-#: gschem/src/x_dialog.c:587
+#: gschem/src/x_dialog.c:588
msgid "Solid"
msgstr "Solied"
-#: gschem/src/x_dialog.c:588
+#: gschem/src/x_dialog.c:589
msgid "Dotted"
msgstr "Gestippeld"
-#: gschem/src/x_dialog.c:589
+#: gschem/src/x_dialog.c:590
msgid "Dashed"
msgstr "Gebroke"
-#: gschem/src/x_dialog.c:590
+#: gschem/src/x_dialog.c:591
msgid "Center"
msgstr "Sentreer"
-#: gschem/src/x_dialog.c:591
+#: gschem/src/x_dialog.c:592
msgid "Phantom"
msgstr "Spook"
-#: gschem/src/x_dialog.c:592 gschem/src/x_dialog.c:689
-#: gschem/src/x_dialog.c:698 gschem/src/x_dialog.c:707
-#: gschem/src/x_dialog.c:808 gschem/src/x_dialog.c:810
-#: gschem/src/x_dialog.c:812 gschem/src/x_dialog.c:1038
-#: gschem/src/x_dialog.c:1141 gschem/src/x_dialog.c:1150
-#: gschem/src/x_dialog.c:1159 gschem/src/x_dialog.c:1168
-#: gschem/src/x_dialog.c:1177 gschem/src/x_dialog.c:1290
-#: gschem/src/x_dialog.c:1292 gschem/src/x_dialog.c:1294
-#: gschem/src/x_dialog.c:1296 gschem/src/x_dialog.c:1298
+#: gschem/src/x_dialog.c:593 gschem/src/x_dialog.c:690
+#: gschem/src/x_dialog.c:699 gschem/src/x_dialog.c:708
+#: gschem/src/x_dialog.c:809 gschem/src/x_dialog.c:811
+#: gschem/src/x_dialog.c:813 gschem/src/x_dialog.c:1039
+#: gschem/src/x_dialog.c:1142 gschem/src/x_dialog.c:1151
+#: gschem/src/x_dialog.c:1160 gschem/src/x_dialog.c:1169
+#: gschem/src/x_dialog.c:1178 gschem/src/x_dialog.c:1291
+#: gschem/src/x_dialog.c:1293 gschem/src/x_dialog.c:1295
+#: gschem/src/x_dialog.c:1297 gschem/src/x_dialog.c:1299
msgid "*unchanged*"
msgstr "*onveranderd*"
-#: gschem/src/x_dialog.c:916
+#: gschem/src/x_dialog.c:917
msgid "Edit Line Width & Type"
msgstr "Bewerk Lynwyddte & -styl"
-#: gschem/src/x_dialog.c:955 gschem/src/x_print.c:307
+#: gschem/src/x_dialog.c:956 gschem/src/x_print.c:307
msgid "Type:"
msgstr "Styl:"
-#: gschem/src/x_dialog.c:959
+#: gschem/src/x_dialog.c:960
msgid "Width:"
msgstr "Wydte:"
-#: gschem/src/x_dialog.c:963
+#: gschem/src/x_dialog.c:964
msgid "Dash Length:"
msgstr "Streeplengte"
-#: gschem/src/x_dialog.c:967
+#: gschem/src/x_dialog.c:968
msgid "Dash Space:"
msgstr "Streepspasie"
-#: gschem/src/x_dialog.c:1034
+#: gschem/src/x_dialog.c:1035
msgid "Hollow"
msgstr "Hol"
-#: gschem/src/x_dialog.c:1035
+#: gschem/src/x_dialog.c:1036
msgid "Filled"
msgstr "Gevul"
-#: gschem/src/x_dialog.c:1036
+#: gschem/src/x_dialog.c:1037
msgid "Mesh"
msgstr "Rooster"
-#: gschem/src/x_dialog.c:1037
+#: gschem/src/x_dialog.c:1038
msgid "Hatch"
msgstr "Arseer"
-#: gschem/src/x_dialog.c:1406
+#: gschem/src/x_dialog.c:1407
msgid "Edit Fill Type"
msgstr "Bewerk Vultipe"
-#: gschem/src/x_dialog.c:1444
+#: gschem/src/x_dialog.c:1446
msgid "Fill Type:"
msgstr "Vultipe:"
-#: gschem/src/x_dialog.c:1448
+#: gschem/src/x_dialog.c:1450
msgid "Line Width:"
msgstr "Lynwydte:"
-#: gschem/src/x_dialog.c:1452
+#: gschem/src/x_dialog.c:1454
msgid "Angle 1:"
msgstr "Hoek 1:"
-#: gschem/src/x_dialog.c:1456
+#: gschem/src/x_dialog.c:1458
msgid "Pitch 1:"
msgstr "Steek 1:"
-#: gschem/src/x_dialog.c:1460
+#: gschem/src/x_dialog.c:1462
msgid "Angle 2:"
msgstr "Hoek 2:"
-#: gschem/src/x_dialog.c:1464
+#: gschem/src/x_dialog.c:1466
msgid "Pitch 2:"
msgstr "Steek 2:"
-#: gschem/src/x_dialog.c:1591
+#: gschem/src/x_dialog.c:1593
msgid "Arc Params"
msgstr "Boogparameters"
-#: gschem/src/x_dialog.c:1631
+#: gschem/src/x_dialog.c:1634
msgid "Arc Radius:"
msgstr ""
-#: gschem/src/x_dialog.c:1639
+#: gschem/src/x_dialog.c:1642
msgid "Start Angle:"
msgstr "Beginhoek:"
-#: gschem/src/x_dialog.c:1647
+#: gschem/src/x_dialog.c:1650
msgid "Degrees of Sweep:"
msgstr "Grade van Kromming:"
-#: gschem/src/x_dialog.c:1764
+#: gschem/src/x_dialog.c:1768
msgid ""
"Offset to translate?\n"
"(0 for origin)"
@@ -1298,186 +1306,186 @@ msgstr ""
"Afwyking om te verskuif?\n"
"(0 vir oorsprong)"
-#: gschem/src/x_dialog.c:1832
+#: gschem/src/x_dialog.c:1836
msgid "Text Size"
msgstr "Teksgrootte"
-#: gschem/src/x_dialog.c:1862
+#: gschem/src/x_dialog.c:1866
msgid "Enter new text size:"
msgstr "Gee nuwe teksgrootte aan:"
-#: gschem/src/x_dialog.c:1938
+#: gschem/src/x_dialog.c:1942
msgid "Snap Size"
msgstr ""
-#: gschem/src/x_dialog.c:1968
+#: gschem/src/x_dialog.c:1972
msgid "Enter new snap grid spacing:"
msgstr ""
-#: gschem/src/x_dialog.c:2045
+#: gschem/src/x_dialog.c:2049
msgid "Edit slot number"
msgstr "Bewerk gleufnommer"
-#: gschem/src/x_dialog.c:2076
+#: gschem/src/x_dialog.c:2080
msgid "Edit slot number:"
msgstr "Bewerk gleufnommer:"
-#: gschem/src/x_dialog.c:2117
+#: gschem/src/x_dialog.c:2121
#, c-format
msgid "%s%s (%s)"
msgstr ""
-#: gschem/src/x_dialog.c:2140
+#: gschem/src/x_dialog.c:2144
msgid "About gschem"
msgstr "Oor gschem"
-#: gschem/src/x_dialog.c:2141
+#: gschem/src/x_dialog.c:2145
msgid "gEDA: GPL Electronic Design Automation"
msgstr "gEDA: GPL Elektroniese Ontwerp Outomatisering"
-#: gschem/src/x_dialog.c:2142
+#: gschem/src/x_dialog.c:2146
msgid ""
"Copyright © 1998-2009 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
"Copyright © 1998-2009 gEDA Contributors (see ChangeLog for details)"
msgstr ""
# FIXME: May need to have a deëlteken on second 'o'.
-#: gschem/src/x_dialog.c:2201
+#: gschem/src/x_dialog.c:2205
msgid "Coords"
msgstr "Koordinate"
-#: gschem/src/x_dialog.c:2222
+#: gschem/src/x_dialog.c:2226
msgid "Screen"
msgstr "Skerm"
-#: gschem/src/x_dialog.c:2231
+#: gschem/src/x_dialog.c:2235
msgid "World"
msgstr "Wêreld"
-#: gschem/src/x_dialog.c:2270
+#: gschem/src/x_dialog.c:2274
msgid "Background"
msgstr ""
-#: gschem/src/x_dialog.c:2276
+#: gschem/src/x_dialog.c:2280
msgid "Net endpoint"
msgstr ""
-#: gschem/src/x_dialog.c:2279
+#: gschem/src/x_dialog.c:2283
msgid "Graphic"
msgstr ""
-#: gschem/src/x_dialog.c:2288
+#: gschem/src/x_dialog.c:2292
msgid "Logic bubble"
msgstr ""
-#: gschem/src/x_dialog.c:2291
+#: gschem/src/x_dialog.c:2295
msgid "Grid point"
msgstr ""
-#: gschem/src/x_dialog.c:2294
+#: gschem/src/x_dialog.c:2298
msgid "Detached attribute"
msgstr ""
-#: gschem/src/x_dialog.c:2297 gschem/src/x_window.c:383
+#: gschem/src/x_dialog.c:2301 gschem/src/x_window.c:383
msgid "Text"
msgstr "Teks"
-#: gschem/src/x_dialog.c:2303
+#: gschem/src/x_dialog.c:2307
msgid "Selection"
msgstr ""
-#: gschem/src/x_dialog.c:2306
+#: gschem/src/x_dialog.c:2310
msgid "Bounding box"
msgstr ""
-#: gschem/src/x_dialog.c:2309
+#: gschem/src/x_dialog.c:2313
msgid "Zoom box"
msgstr "Zoem Reghoek"
-#: gschem/src/x_dialog.c:2318
+#: gschem/src/x_dialog.c:2322
msgid "Output background"
msgstr ""
-#: gschem/src/x_dialog.c:2321
+#: gschem/src/x_dialog.c:2325
msgid "Net junction"
msgstr ""
-#: gschem/src/x_dialog.c:2324
+#: gschem/src/x_dialog.c:2328
msgid "Mesh grid major"
msgstr ""
-#: gschem/src/x_dialog.c:2327
+#: gschem/src/x_dialog.c:2331
msgid "Mesh grid minor"
msgstr ""
-#: gschem/src/x_dialog.c:2330
+#: gschem/src/x_dialog.c:2334
msgid "Unknown"
msgstr ""
-#: gschem/src/x_dialog.c:2481
+#: gschem/src/x_dialog.c:2485
#, c-format
msgid "ERROR: NULL object in color_edit_dialog_apply!\n"
msgstr "FOUT: NULL voorwerp in color_edit_dialog_apply!\n"
-#: gschem/src/x_dialog.c:2525
+#: gschem/src/x_dialog.c:2529
msgid "Color Edit"
msgstr "Kleurbewerking"
-#: gschem/src/x_dialog.c:2556
+#: gschem/src/x_dialog.c:2560
msgid "Object color:"
msgstr "Voorwerpkleur:"
-#: gschem/src/x_dialog.c:2614
+#: gschem/src/x_dialog.c:2618
msgid "Hotkeys"
msgstr ""
-#: gschem/src/x_dialog.c:2678
+#: gschem/src/x_dialog.c:2682
msgid "Function"
msgstr "Funksie"
-#: gschem/src/x_dialog.c:2685
+#: gschem/src/x_dialog.c:2689
msgid "Keystroke(s)"
msgstr "Sleutelslae"
-#: gschem/src/x_dialog.c:2991
+#: gschem/src/x_dialog.c:2995
msgid "Find Text"
msgstr "Vind Teks"
-#: gschem/src/x_dialog.c:3022
+#: gschem/src/x_dialog.c:3026
msgid "Text to find:"
msgstr "Teks om te vind:"
-#: gschem/src/x_dialog.c:3032
+#: gschem/src/x_dialog.c:3036
msgid "descend into hierarchy"
msgstr "daal in hierargie af"
-#: gschem/src/x_dialog.c:3097
+#: gschem/src/x_dialog.c:3101
msgid "Hide Text"
msgstr "Verskuil Teks"
-#: gschem/src/x_dialog.c:3128
+#: gschem/src/x_dialog.c:3132
msgid "Hide text starting with:"
msgstr "Verskuil teks beginnende met:"
-#: gschem/src/x_dialog.c:3197
+#: gschem/src/x_dialog.c:3201
msgid "Show Text"
msgstr "Toon Teks"
-#: gschem/src/x_dialog.c:3228
+#: gschem/src/x_dialog.c:3232
msgid "Show text starting with:"
msgstr "Toon Teks beginnende met:"
-#: gschem/src/x_dialog.c:3685
+#: gschem/src/x_dialog.c:3689
msgid "S_elect the schematics you want to save:"
msgstr "Kies die stroombaandiagramme wat jy wil bewaar:"
-#: gschem/src/x_dialog.c:3779
+#: gschem/src/x_dialog.c:3784
#, c-format
msgid "Save the changes to schematic \"%s\" before closing?"
msgstr ""
"Wil jy veranderinge aan stroombaandiagram \"%s\" bewaar voor jy afsluit?"
-#: gschem/src/x_dialog.c:3785
+#: gschem/src/x_dialog.c:3790
#, c-format
msgid ""
"There are %d schematics with unsaved changes. Save changes before closing?"
@@ -1485,15 +1493,15 @@ msgstr ""
"Daar is %d stroombaandiagramme met onbewaarde veranderinge. Wil jy die "
"veranderinge bewaar voor jy afsluit?"
-#: gschem/src/x_dialog.c:3814
+#: gschem/src/x_dialog.c:3819
msgid "If you don't save, all your changes will be permanently lost."
msgstr "As jy nie bewaar nie, sal al jou veranderinge permanent verloregaan."
-#: gschem/src/x_dialog.c:3834
+#: gschem/src/x_dialog.c:3839
msgid "_Close without saving"
msgstr "Sluit sonder om te bewaar"
-#: gschem/src/x_dialog.c:4170
+#: gschem/src/x_dialog.c:4175
#, c-format
msgid ""
"<span weight=\"bold\" size=\"larger\">The input attribute \"%s\" is invalid\n"
@@ -1511,19 +1519,19 @@ msgstr ""
"Die naam mag nie met 'n spasie eindig nie.\n"
"Die waarde mag nie met 'n spasie begin nie."
-#: gschem/src/x_dialog.c:4172
+#: gschem/src/x_dialog.c:4177
msgid "Invalid Attribute"
msgstr "Ongeldige Eienskap"
-#: gschem/src/x_dialog.c:4208
+#: gschem/src/x_dialog.c:4213
msgid "Pin type"
msgstr ""
-#: gschem/src/x_dialog.c:4232
+#: gschem/src/x_dialog.c:4237
msgid "Net pin"
msgstr ""
-#: gschem/src/x_dialog.c:4234
+#: gschem/src/x_dialog.c:4239
msgid "Bus pin (graphical)"
msgstr ""
@@ -1620,11 +1628,11 @@ msgstr "Afbeeldingsoort"
msgid "Write image..."
msgstr "Skryf afbeelding..."
-#: gschem/src/x_log.c:188
+#: gschem/src/x_log.c:209
msgid "** Invalid UTF-8 in log message. See stderr or gschem.log.\n"
msgstr ""
-#: gschem/src/x_log.c:256
+#: gschem/src/x_log.c:288
msgid "Status"
msgstr "Stand"
@@ -1700,69 +1708,60 @@ msgstr "/Simbool Af"
msgid "/Up"
msgstr "/Op"
-#: gschem/src/x_menus.c:321
+#: gschem/src/x_menus.c:323
#, c-format
msgid "Tried to set the sensitivity on non-existent menu item '%s'\n"
msgstr "Het probeer om gevoeligheid op nie-bestaande menu-artikel '%s'\n"
-#: gschem/src/x_menus.c:345
+#: gschem/src/x_menus.c:347
msgid "Popup_menu_item_factory doesn't exist!\n"
msgstr "popup_menu artikelfabriek bestaan nie!\n"
-#: gschem/src/x_menus.c:358
+#: gschem/src/x_menus.c:360
msgid "Tried to set the sensitivity on a non-existent popup menu_item\n"
msgstr ""
-#: gschem/src/x_menus.c:438
-#, c-format
-msgid "Couldn't open file %s\n"
-msgstr "Kon nie lêer %s oopmaak nie\n"
-
-#: gschem/src/x_menus.c:495
-msgid "Clear"
-msgstr "Maak Skoon"
-
-#: gschem/src/x_multiattrib.c:911
+#: gschem/src/x_multiattrib.c:915
msgid "Attributes with empty name are not allowed. Please set a name."
msgstr "Eienskappe met 'n leë naam word verbied. Kies asseblief 'n naam."
-#: gschem/src/x_multiattrib.c:1456
+#: gschem/src/x_multiattrib.c:1468
msgid "Show Value only"
msgstr "Toon slegs waarde"
-#: gschem/src/x_multiattrib.c:1458
+#: gschem/src/x_multiattrib.c:1470
msgid "Show Name only"
msgstr "Toon slegs naam"
-#: gschem/src/x_multiattrib.c:1486
+#: gschem/src/x_multiattrib.c:1498
msgid "Promote"
msgstr ""
-#: gschem/src/x_multiattrib.c:1490
+#: gschem/src/x_multiattrib.c:1502
msgid "Duplicate"
msgstr "Dupliseer"
-#: gschem/src/x_multiattrib.c:1708
+#: gschem/src/x_multiattrib.c:1719
msgid "Edit Attributes"
msgstr "Bewerk Eienskappe"
-#: gschem/src/x_multiattrib.c:1826
+#: gschem/src/x_multiattrib.c:1837
msgid "Vis?"
msgstr "Sig?"
-#: gschem/src/x_multiattrib.c:1844
+#: gschem/src/x_multiattrib.c:1855
msgid "N"
msgstr "N"
-#: gschem/src/x_multiattrib.c:1862
+#: gschem/src/x_multiattrib.c:1873
msgid "V"
msgstr "W"
-#: gschem/src/x_multiattrib.c:1884
+#: gschem/src/x_multiattrib.c:1895
msgid "Show inherited attributes"
msgstr ""
-#: gschem/src/x_multiattrib.c:1900
+#: gschem/src/x_multiattrib.c:1911
msgid "Add Attribute"
msgstr "Voeg Eienskap By"
@@ -1786,23 +1785,23 @@ msgstr "Sluit Bladsy"
msgid "Discard Page"
msgstr "Werp Bladsy Weg"
-#: gschem/src/x_pagesel.c:376
+#: gschem/src/x_pagesel.c:375
msgid "Page Manager"
msgstr "Bladsybestuurder"
-#: gschem/src/x_pagesel.c:432
+#: gschem/src/x_pagesel.c:431
msgid "Filename"
msgstr "Lêernaam"
-#: gschem/src/x_pagesel.c:448
+#: gschem/src/x_pagesel.c:447
msgid "Changed"
msgstr "Veranderd"
-#: gschem/src/x_pagesel.c:468
+#: gschem/src/x_pagesel.c:467
msgid "Right click on the filename for more options..."
msgstr "Regs-klik op die lêernaam vir meer opsies..."
-#: gschem/src/x_preview.c:234
+#: gschem/src/x_preview.c:233
msgid "Preview Buffer"
msgstr ""
@@ -1858,16 +1857,16 @@ msgstr "Lêer:"
msgid "Command:"
msgstr "Opdrag:"
-#: gschem/src/x_print.c:741
+#: gschem/src/x_print.c:745
msgid "No print destination specified\n"
msgstr "Geen drukbestemming aangegee nie\n"
-#: gschem/src/x_print.c:748
+#: gschem/src/x_print.c:752
#, c-format
msgid "Cannot print current schematic to [%s]\n"
msgstr "Kan nie huidige stroombaandiagram na [%s] druk nie\n"
-#: gschem/src/x_print.c:757
+#: gschem/src/x_print.c:761
#, c-format
msgid ""
"Error printing to file '%s'\n"
@@ -1876,7 +1875,7 @@ msgstr ""
"Fout gedurende lêerdruk na '%s'\n"
"Ondersoek die log-venster vir meer inligting"
-#: gschem/src/x_print.c:764
+#: gschem/src/x_print.c:768
#, c-format
msgid "Printed current schematic to [%s]\n"
msgstr "Het lopende stroombaandiagram na [%s] gedruk\n"
@@ -1885,6 +1884,11 @@ msgstr "Het lopende stroombaandiagram na [%s] gedruk\n"
msgid "Execute Script..."
msgstr "Voer Script Uit..."
+#: gschem/src/x_script.c:66
+#, c-format
+msgid "Executing guile script [%s]\n"
+msgstr "Voer guile script [%s] uit\n"
+
#: gschem/src/x_window.c:81
#, c-format
msgid "Couldn't allocate gc\n"
@@ -1992,35 +1996,35 @@ msgstr "Misluk om lêer te laai"
msgid "New file [%s]\n"
msgstr "Nuwe lêer [%s]\n"
-#: gschem/src/x_window.c:857
+#: gschem/src/x_window.c:855
#, c-format
msgid "Could NOT save page [%s]\n"
msgstr "Kon nie bladsy [%s] bewaar nie\n"
-#: gschem/src/x_window.c:858
+#: gschem/src/x_window.c:856
msgid "Error while trying to save"
msgstr "Fout gedurende poging om te bewaar"
-#: gschem/src/x_window.c:867
+#: gschem/src/x_window.c:865
#, c-format
msgid "Saved as [%s]\n"
msgstr "Bewaar as [%s]\n"
-#: gschem/src/x_window.c:869
+#: gschem/src/x_window.c:867
#, c-format
msgid "Saved [%s]\n"
msgstr "Bewaar [%s]\n"
-#: gschem/src/x_window.c:871
+#: gschem/src/x_window.c:869
msgid "Saved"
msgstr "Bewaar"
-#: gschem/src/x_window.c:945
+#: gschem/src/x_window.c:943
#, c-format
msgid "Discarding page [%s]\n"
msgstr "Werp bladsy [%s] weg\n"
-#: gschem/src/x_window.c:945
+#: gschem/src/x_window.c:943
#, c-format
msgid "Closing [%s]\n"
msgstr "Sluit [%s]\n"
@@ -2061,7 +2065,7 @@ msgstr ""
msgid "Save All"
msgstr "Bewaar Alles"
-#: gschem/lib/system-gschemrc.scm:1386 gschem/lib/system-gschemrc.scm:1477
+#: gschem/lib/system-gschemrc.scm:1386 gschem/lib/system-gschemrc.scm:1478
msgid "_Revert"
msgstr ""
@@ -2073,7 +2077,7 @@ msgstr ""
msgid "Write _image..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1393 gschem/lib/system-gschemrc.scm:1478
+#: gschem/lib/system-gschemrc.scm:1393 gschem/lib/system-gschemrc.scm:1479
msgid "_Close"
msgstr ""
@@ -2105,391 +2109,412 @@ msgstr ""
msgid "_Delete"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1412
+#: gschem/lib/system-gschemrc.scm:1409
+#, fuzzy
+msgid "Select All"
+msgstr "Kies"
+
+#: gschem/lib/system-gschemrc.scm:1410
+#, fuzzy
+msgid "Deselect"
+msgstr "Kies"
+
+#: gschem/lib/system-gschemrc.scm:1414
msgid "Rotate 90 Mode"
msgstr "Roteer-90-modus"
-#: gschem/lib/system-gschemrc.scm:1415
+#: gschem/lib/system-gschemrc.scm:1417
msgid "Edit..."
msgstr "Bewerk..."
-#: gschem/lib/system-gschemrc.scm:1416
+#: gschem/lib/system-gschemrc.scm:1418
msgid "Edit Text..."
msgstr "Bewerk Teks..."
-#: gschem/lib/system-gschemrc.scm:1417
+#: gschem/lib/system-gschemrc.scm:1419
msgid "Slot..."
msgstr "Gleuf..."
-#: gschem/lib/system-gschemrc.scm:1418
+#: gschem/lib/system-gschemrc.scm:1420
msgid "Color..."
msgstr "Kleur..."
-#: gschem/lib/system-gschemrc.scm:1419
+#: gschem/lib/system-gschemrc.scm:1421
msgid "Line Width & Type..."
msgstr "Lynwydte en -tipe..."
-#: gschem/lib/system-gschemrc.scm:1420
+#: gschem/lib/system-gschemrc.scm:1422
msgid "Fill Type..."
msgstr "Vultipe"
-#: gschem/lib/system-gschemrc.scm:1421
+#: gschem/lib/system-gschemrc.scm:1423
msgid "Symbol Translate..."
msgstr "Simboolverskuiwing..."
-#: gschem/lib/system-gschemrc.scm:1425
+#: gschem/lib/system-gschemrc.scm:1427
msgid "Invoke Macro"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1426
+#: gschem/lib/system-gschemrc.scm:1428
msgid "Embed Component/Picture"
msgstr "Lê Komponent/Afbeelding In"
# FIXME: too klunky!
-#: gschem/lib/system-gschemrc.scm:1427
+#: gschem/lib/system-gschemrc.scm:1429
msgid "Unembed Component/Picture"
msgstr "Ont-lê Komponent/Afbeelding In"
-#: gschem/lib/system-gschemrc.scm:1428
+#: gschem/lib/system-gschemrc.scm:1430
msgid "Update Component"
msgstr "Vernuwe Komponent"
-#: gschem/lib/system-gschemrc.scm:1429
+#: gschem/lib/system-gschemrc.scm:1431
msgid "Show/Hide Inv Text"
msgstr "Toon/Verberg Onsigbare Teks"
-#: gschem/lib/system-gschemrc.scm:1430
-msgid "Make Inv Text Vis"
-msgstr "Maak Onsigbare Teks Sigbaar"
-
-#: gschem/lib/system-gschemrc.scm:1436
+#: gschem/lib/system-gschemrc.scm:1437
msgid "Copy into 1"
msgstr "Kopieer in 1 in"
-#: gschem/lib/system-gschemrc.scm:1437
+#: gschem/lib/system-gschemrc.scm:1438
msgid "Copy into 2"
msgstr "Kopieer in 2 in"
-#: gschem/lib/system-gschemrc.scm:1438
+#: gschem/lib/system-gschemrc.scm:1439
msgid "Copy into 3"
msgstr "Kopieer in 3 in"
-#: gschem/lib/system-gschemrc.scm:1439
+#: gschem/lib/system-gschemrc.scm:1440
msgid "Copy into 4"
msgstr "Kopieer in 4 in"
-#: gschem/lib/system-gschemrc.scm:1440
+#: gschem/lib/system-gschemrc.scm:1441
msgid "Copy into 5"
msgstr "Kopieer in 5 in"
-#: gschem/lib/system-gschemrc.scm:1441
+#: gschem/lib/system-gschemrc.scm:1442
msgid "Cut into 1"
msgstr "Sny in 1 in"
-#: gschem/lib/system-gschemrc.scm:1442
+#: gschem/lib/system-gschemrc.scm:1443
msgid "Cut into 2"
msgstr "Sny in 2 in"
-#: gschem/lib/system-gschemrc.scm:1443
+#: gschem/lib/system-gschemrc.scm:1444
msgid "Cut into 3"
msgstr "Sny in 3 in"
-#: gschem/lib/system-gschemrc.scm:1444
+#: gschem/lib/system-gschemrc.scm:1445
msgid "Cut into 4"
msgstr "Sny in 4 in"
-#: gschem/lib/system-gschemrc.scm:1445
+#: gschem/lib/system-gschemrc.scm:1446
msgid "Cut into 5"
msgstr "Sny in 5 in"
-#: gschem/lib/system-gschemrc.scm:1446
+#: gschem/lib/system-gschemrc.scm:1447
msgid "Paste from 1"
msgstr "Plak vanuit 1"
-#: gschem/lib/system-gschemrc.scm:1447
+#: gschem/lib/system-gschemrc.scm:1448
msgid "Paste from 2"
msgstr "Plak vanuit 2"
-#: gschem/lib/system-gschemrc.scm:1448
+#: gschem/lib/system-gschemrc.scm:1449
msgid "Paste from 3"
msgstr "Plak vanuit 3"
-#: gschem/lib/system-gschemrc.scm:1449
+#: gschem/lib/system-gschemrc.scm:1450
msgid "Paste from 4"
msgstr "Plak vanuit 4"
-#: gschem/lib/system-gschemrc.scm:1450
+#: gschem/lib/system-gschemrc.scm:1451
msgid "Paste from 5"
msgstr "Plak vanuit 5"
-#: gschem/lib/system-gschemrc.scm:1456
+#: gschem/lib/system-gschemrc.scm:1457
msgid "_Redraw"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1457
+#: gschem/lib/system-gschemrc.scm:1458
msgid "_Pan"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1458
+#: gschem/lib/system-gschemrc.scm:1459
msgid "Zoom _Box"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1459
+#: gschem/lib/system-gschemrc.scm:1460
msgid "Zoom _Extents"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1460
+#: gschem/lib/system-gschemrc.scm:1461
msgid "Zoom _In"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1461
+#: gschem/lib/system-gschemrc.scm:1462
msgid "Zoom _Out"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1462
+#: gschem/lib/system-gschemrc.scm:1463
msgid "Zoom _Full"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1464
+#: gschem/lib/system-gschemrc.scm:1465
msgid "_Dark color scheme"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1465
+#: gschem/lib/system-gschemrc.scm:1466
msgid "_Light color scheme"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1466
+#: gschem/lib/system-gschemrc.scm:1467
msgid "B_W color scheme"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1473
+#: gschem/lib/system-gschemrc.scm:1474
msgid "_Manager..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1474
+#: gschem/lib/system-gschemrc.scm:1475
msgid "_Previous"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1475
+#: gschem/lib/system-gschemrc.scm:1476
msgid "_Next"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1476
+#: gschem/lib/system-gschemrc.scm:1477
msgid "Ne_w"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1480
+#: gschem/lib/system-gschemrc.scm:1481
msgid "_Discard"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1486
+#: gschem/lib/system-gschemrc.scm:1487
msgid "_Component..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1487
+#: gschem/lib/system-gschemrc.scm:1488
msgid "_Net"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1488
+#: gschem/lib/system-gschemrc.scm:1489
msgid "B_us"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1489
+#: gschem/lib/system-gschemrc.scm:1490
msgid "_Attribute..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1490
+#: gschem/lib/system-gschemrc.scm:1491
msgid "_Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1492
+#: gschem/lib/system-gschemrc.scm:1493
msgid "_Line"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1493
+#: gschem/lib/system-gschemrc.scm:1494
msgid "_Box"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1494
+#: gschem/lib/system-gschemrc.scm:1495
msgid "C_ircle"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1495
+#: gschem/lib/system-gschemrc.scm:1496
msgid "A_rc"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1496
+#: gschem/lib/system-gschemrc.scm:1497
msgid "_Pin"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1497
+#: gschem/lib/system-gschemrc.scm:1498
msgid "Pictu_re..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1503
+#: gschem/lib/system-gschemrc.scm:1504
msgid "_Down Schematic"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1504
+#: gschem/lib/system-gschemrc.scm:1505
msgid "Down _Symbol"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1505
+#: gschem/lib/system-gschemrc.scm:1506
msgid "_Up"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1506
+#: gschem/lib/system-gschemrc.scm:1507
msgid "D_ocumentation..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1512
+#: gschem/lib/system-gschemrc.scm:1513
msgid "_Attach"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1513
+#: gschem/lib/system-gschemrc.scm:1514
msgid "_Detach"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1514
+#: gschem/lib/system-gschemrc.scm:1515
msgid "Show _Value"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1515
+#: gschem/lib/system-gschemrc.scm:1516
msgid "Show _Name"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1516
+#: gschem/lib/system-gschemrc.scm:1517
msgid "Show _Both"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1517
+#: gschem/lib/system-gschemrc.scm:1518
msgid "_Toggle Visibility"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1519
+#: gschem/lib/system-gschemrc.scm:1520
msgid "_Find Specific Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1520
+#: gschem/lib/system-gschemrc.scm:1521
msgid "_Hide Specific Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1521
+#: gschem/lib/system-gschemrc.scm:1522
msgid "_Show Specific Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1522
+#: gschem/lib/system-gschemrc.scm:1523
msgid "A_utonumber Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1528
+#: gschem/lib/system-gschemrc.scm:1529
msgid "_Text Size..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1529
+#: gschem/lib/system-gschemrc.scm:1530
msgid "Cycle _grid styles"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1530
+#: gschem/lib/system-gschemrc.scm:1531
msgid "Toggle _Snap On/Off"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1531
+#: gschem/lib/system-gschemrc.scm:1532
msgid "Snap Grid S_pacing..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1532
+#: gschem/lib/system-gschemrc.scm:1533
msgid "Scale _up Grid Spacing"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1534
+#: gschem/lib/system-gschemrc.scm:1535
msgid "Scale _down Grid Spacing"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1536
+#: gschem/lib/system-gschemrc.scm:1537
msgid "Toggle _Outline/Box"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1538
+#: gschem/lib/system-gschemrc.scm:1539
msgid "Toggle Net _Rubberband"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1539
+#: gschem/lib/system-gschemrc.scm:1540
msgid "Toggle _Magnetic Net"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1540
+#: gschem/lib/system-gschemrc.scm:1541
msgid "Show _Log Window..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1542
+#: gschem/lib/system-gschemrc.scm:1543
msgid "Show _Coord Window..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1558
+#: gschem/lib/system-gschemrc.scm:1559
msgid "gEDA Docu_mentation..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1559
+#: gschem/lib/system-gschemrc.scm:1560
msgid "gschem _FAQ..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1560
+#: gschem/lib/system-gschemrc.scm:1561
msgid "gEDA _Wiki..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1561
+#: gschem/lib/system-gschemrc.scm:1562
msgid "Component D_ocumentation..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1563
+#: gschem/lib/system-gschemrc.scm:1564
msgid "_Hotkeys..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1564
+#: gschem/lib/system-gschemrc.scm:1565
msgid "_About..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1570
+#: gschem/lib/system-gschemrc.scm:1571
msgid "_File"
msgstr "Lêer"
-#: gschem/lib/system-gschemrc.scm:1571
+#: gschem/lib/system-gschemrc.scm:1572
msgid "_Edit"
msgstr "Bewerk"
-#: gschem/lib/system-gschemrc.scm:1572
+#: gschem/lib/system-gschemrc.scm:1573
msgid "_Buffer"
msgstr "Buffer"
-#: gschem/lib/system-gschemrc.scm:1573
+#: gschem/lib/system-gschemrc.scm:1574
msgid "_View"
msgstr "Aansig"
-#: gschem/lib/system-gschemrc.scm:1574
+#: gschem/lib/system-gschemrc.scm:1575
msgid "_Page"
msgstr "Bladsy"
-#: gschem/lib/system-gschemrc.scm:1575
+#: gschem/lib/system-gschemrc.scm:1576
msgid "_Add"
msgstr "Voeg By"
-#: gschem/lib/system-gschemrc.scm:1576
+#: gschem/lib/system-gschemrc.scm:1577
msgid "Hie_rarchy"
msgstr "Hierargie"
-#: gschem/lib/system-gschemrc.scm:1577
+#: gschem/lib/system-gschemrc.scm:1578
msgid "A_ttributes"
msgstr "Eienskappe"
-#: gschem/lib/system-gschemrc.scm:1578
+#: gschem/lib/system-gschemrc.scm:1579
msgid "_Options"
msgstr "Opsies"
-#: gschem/lib/system-gschemrc.scm:1579
+#: gschem/lib/system-gschemrc.scm:1580
msgid "_Help"
msgstr "Help"
+#~ msgid "Scheme directory NOT set!\n"
+#~ msgstr "Scheme-gids is NIE gestel nie!\n"
+
+#~ msgid "MakeVisible"
+#~ msgstr "MaakSigbaar"
+
+#~ msgid "Couldn't open file %s\n"
+#~ msgstr "Kon nie lêer %s oopmaak nie\n"
+
+#~ msgid "Clear"
+#~ msgstr "Maak Skoon"
+
+#~ msgid "Make Inv Text Vis"
+#~ msgstr "Maak Onsigbare Teks Sigbaar"
+
#~ msgid "About..."
#~ msgstr "Omtrent..."
diff --git a/gschem/po/ar.po b/gschem/po/ar.po
index 41f2910..f65be7d 100644
--- a/gschem/po/ar.po
+++ b/gschem/po/ar.po
@@ -6,7 +6,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2010-11-07 13:37+0000\n"
+"POT-Creation-Date: 2011-01-16 00:11-0500\n"
"PO-Revision-Date: 2010-02-14 06:08+0000\n"
"Last-Translator: عبداÙ?Ù?Ù? Ø´Ù?Ù? (Abdellah Chelli) <Unknown>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -23,17 +23,17 @@ msgstr ""
msgid "Zoom too small! Cannot zoom further.\n"
msgstr "اÙ?تبعÙ?د Ù?بÙ?ر جدا! Ù?ا Ù?Ù?Ù?Ù? اÙ?تبعÙ?د Ø£Ù?ثر.\n"
-#: gschem/src/g_funcs.c:339 gschem/src/i_callbacks.c:68
+#: gschem/src/g_funcs.c:347 gschem/src/i_callbacks.c:68
#, c-format
msgid "Could not fork\n"
msgstr "تعذÙ?ر اÙ?تشعÙ?ب\n"
-#: gschem/src/g_funcs.c:355 gschem/src/i_callbacks.c:78
+#: gschem/src/g_funcs.c:363 gschem/src/i_callbacks.c:78
#, c-format
msgid "Could not invoke %s\n"
msgstr "تعذÙ?ر استØضار %s\n"
-#: gschem/src/g_funcs.c:361 gschem/src/i_callbacks.c:82
+#: gschem/src/g_funcs.c:369 gschem/src/i_callbacks.c:82
msgid "Documentation commands not supported under MinGW.\n"
msgstr "Ø£Ù?اÙ?ر اÙ?تÙ?Ø«Ù?Ù? غÙ?ر Ù?دعÙ?Ù?Ø© تØت MinGW.\n"
@@ -127,23 +127,23 @@ msgstr "Ù?رÙ?ر Ù?عاÙ?Ù? Ø±Ø¨Ø ØºÙ?ر صاÙ?Ø [%d] Ø¥Ù?Ù? 'Ù?عاÙ?Ù? رب
msgid "Invalid number of steps [%d] scrollpan-steps\n"
msgstr "Ù?رÙ?ر عدد خطÙ?ات غÙ?ر صاÙ?Ø [%d] Ø¥Ù?Ù? 'خطÙ?ات شرÙ?Ø· اÙ?تÙ?رÙ?ر'\n"
-#: gschem/src/gschem.c:184
+#: gschem/src/gschem.c:188
#, c-format
msgid "gEDA/gschem version %s%s.%s\n"
msgstr "إصدار gEDA/gschem� %s%s.%s\n"
-#: gschem/src/gschem.c:187
+#: gschem/src/gschem.c:191
msgid ""
"gEDA/gschem comes with ABSOLUTELY NO WARRANTY; see COPYING for more "
"details.\n"
msgstr "Ù?Ù?دÙ? gEDA/gschem بÙ?ا Ø£Ù? ضÙ?اÙ?Ø? راجع COPYING Ù?تÙ?اصÙ?Ù? Ø£Ù?ثر.\n"
-#: gschem/src/gschem.c:189
+#: gschem/src/gschem.c:193
msgid ""
"This is free software, and you are welcome to redistribute it under certain\n"
msgstr "Ù?ذا برÙ?اÙ?ج ØرØ? Ù?رØب بإعادة تÙ?زÙ?عÙ? Ù?ع بعض اÙ?شرÙ?Ø·Ø?\n"
-#: gschem/src/gschem.c:191
+#: gschem/src/gschem.c:195
msgid ""
"conditions; please see the COPYING file for more details.\n"
"\n"
@@ -151,17 +151,17 @@ msgstr ""
"Ù?Ù? Ù?ضÙ?Ù? راجع اÙ?Ù?Ù?Ù? COPYING Ù?تÙ?اصÙ?Ù? Ø£Ù?ثر.\n"
"\n"
-#: gschem/src/gschem.c:194
+#: gschem/src/gschem.c:198
#, c-format
msgid "This is the MINGW32 port.\n"
msgstr "Ù?ذا Ù?Ù?Ù?(Port) عÙ? طرÙ?Ù? MINGW32.\n"
-#: gschem/src/gschem.c:198
+#: gschem/src/gschem.c:202
#, c-format
msgid "Current locale settings: %s\n"
msgstr "اÙ?إعدادات اÙ?Ù?ØÙ?Ù?Ø© اÙ?ØاÙ?Ù?Ø©: %s\n"
-#: gschem/src/gschem.c:213
+#: gschem/src/gschem.c:218
msgid ""
"You must set the GEDADATA environment variable!\n"
"\n"
@@ -173,31 +173,21 @@ msgstr ""
"Ù?ا Ù?Ù?Ù?Ù? Ù?Ù? gschem تØدÙ?د Ù?Ù?اÙ? Ù?Ù?Ù?ات اÙ?بÙ?اÙ?ات خاصتÙ?. Ù?جب Ø£Ù? تعÙ?Ù?Ù? Ù?تغÙ?Ù?ر اÙ?بÙ?ئة\n"
"â??GEDADATA Ù?Ù?Ø´Ù?ر Ø¥Ù?Ù? اÙ?Ù?Ù?اÙ? اÙ?صÙ?ØÙ?Ø.\n"
-#: gschem/src/gschem.c:248
+#: gschem/src/gschem.c:256
#, c-format
msgid "Couldn't find init scm file [%s]\n"
msgstr "تعذÙ?ر اÙ?عثÙ?ر عÙ?Ù? Ù?Ù?Ù? اÙ?استÙ?Ù?اÙ? [â??%sâ?¬]\n"
-#: gschem/src/gschem.c:252
+#: gschem/src/gschem.c:260
#, c-format
msgid "Read init scm file [%s]\n"
msgstr "Ù?راءة Ù?Ù?Ù? اÙ?استÙ?Ù?اÙ? [â??%sâ?¬]\n"
-#: gschem/src/gschem.c:256
+#: gschem/src/gschem.c:264
#, c-format
msgid "Failed to read init scm file [%s]\n"
msgstr "Ù?Ø´Ù? Ù?راءة Ù?Ù?Ù? اÙ?استÙ?Ù?اÙ? [â??%sâ?¬]\n"
-#: gschem/src/gschem.c:317
-#, c-format
-msgid "Scheme directory NOT set!\n"
-msgstr "دÙ?Ù?Ù? اÙ?Ù?خطط غÙ?ر Ù?عÙ?Ù?!\n"
-
-#: gschem/src/gschem.c:324 gschem/src/x_script.c:66
-#, c-format
-msgid "Executing guile script [%s]\n"
-msgstr "تÙ?Ù?Ù?Ø° Ù?خطÙ?Ø· guile [â??%sâ?¬]\n"
-
#: gschem/src/gschem_cairo.c:310
#, c-format
msgid "Unknown end for line (%d)\n"
@@ -221,11 +211,11 @@ msgstr "Ù?ضع اÙ?Ù?Ù?Ù?Ù?"
msgid "Text Mode"
msgstr "Ù?ضع اÙ?Ù?ص"
-#: gschem/src/i_basic.c:84 gschem/lib/system-gschemrc.scm:1409
+#: gschem/src/i_basic.c:84 gschem/lib/system-gschemrc.scm:1411
msgid "Copy Mode"
msgstr "Ù?ضع اÙ?Ù?سخ"
-#: gschem/src/i_basic.c:87 gschem/lib/system-gschemrc.scm:1411
+#: gschem/src/i_basic.c:87 gschem/lib/system-gschemrc.scm:1413
msgid "Move Mode"
msgstr "Ù?ضع اÙ?تÙ?ØرÙ?Ù?"
@@ -233,7 +223,7 @@ msgstr "Ù?ضع اÙ?تÙ?ØرÙ?Ù?"
msgid "Rotate Mode"
msgstr "Ù?ضع اÙ?إستدارة"
-#: gschem/src/i_basic.c:91 gschem/lib/system-gschemrc.scm:1413
+#: gschem/src/i_basic.c:91 gschem/lib/system-gschemrc.scm:1415
msgid "Mirror Mode"
msgstr "Ù?ضع اÙ?Ù?رآة"
@@ -286,22 +276,22 @@ msgstr "Ù?ضع اÙ?Ù?Ù?س"
msgid "Pin Mode"
msgstr "Ù?ضع اÙ?دبÙ?س"
-#: gschem/src/i_basic.c:135 gschem/src/i_callbacks.c:544
-#: gschem/src/i_callbacks.c:568
+#: gschem/src/i_basic.c:135 gschem/src/i_callbacks.c:576
+#: gschem/src/i_callbacks.c:600
msgid "Copy"
msgstr "اÙ?سخ"
-#: gschem/src/i_basic.c:137 gschem/src/i_callbacks.c:634
-#: gschem/src/i_callbacks.c:658
+#: gschem/src/i_basic.c:137 gschem/src/i_callbacks.c:666
+#: gschem/src/i_callbacks.c:690
msgid "Move"
msgstr "ØرÙ?Ù?"
-#: gschem/src/i_basic.c:139 gschem/src/i_callbacks.c:589
-#: gschem/src/i_callbacks.c:613
+#: gschem/src/i_basic.c:139 gschem/src/i_callbacks.c:621
+#: gschem/src/i_callbacks.c:645
msgid "Multiple Copy"
msgstr "Ù?سخ Ù?تعدد"
-#: gschem/src/i_basic.c:142 gschem/lib/system-gschemrc.scm:1410
+#: gschem/src/i_basic.c:142 gschem/lib/system-gschemrc.scm:1412
msgid "Multiple Copy Mode"
msgstr "Ù?ضع اÙ?Ù?سخ اÙ?Ù?تعدد"
@@ -321,7 +311,7 @@ msgstr "تÙ?عÙ?Ù? إعادة اÙ?جذب"
msgid "Action"
msgstr "إجراء"
-#: gschem/src/i_basic.c:260 gschem/src/x_dialog.c:2312
+#: gschem/src/i_basic.c:260 gschem/src/x_dialog.c:2316
#: gschem/src/x_window.c:491
msgid "Stroke"
msgstr "جرة (Stroke)"
@@ -352,7 +342,7 @@ msgstr "شبÙ?Ù?Ø©(%s, %s)"
msgid "Documentation for [%s,%s,%s,%s]\n"
msgstr "اÙ?تÙ?Ø«Ù?Ù? Ù?أجÙ? [%s,%s,%s,%s]\n"
-#: gschem/src/i_callbacks.c:123 gschem/src/i_callbacks.c:1699
+#: gschem/src/i_callbacks.c:123 gschem/src/i_callbacks.c:1706
#, c-format
msgid "New page created [%s]\n"
msgstr "Ø£Ù?شئت صÙ?ØØ© جدÙ?دة [â??%sâ?¬]\n"
@@ -374,328 +364,324 @@ msgstr "ØÙ?ظ اÙ?Ù?Ù?"
msgid "Closing Window\n"
msgstr "إغÙ?اÙ? اÙ?Ù?اÙ?ذة\n"
-#: gschem/src/i_callbacks.c:549 gschem/src/i_callbacks.c:594
-#: gschem/src/i_callbacks.c:639
+#: gschem/src/i_callbacks.c:581 gschem/src/i_callbacks.c:626
+#: gschem/src/i_callbacks.c:671
msgid "Select objs first"
msgstr "اÙ?تÙ? اÙ?Ù?ائÙ?ات Ø£Ù?Ù?ا"
-#: gschem/src/i_callbacks.c:678 gschem/src/x_multiattrib.c:1491
+#: gschem/src/i_callbacks.c:710 gschem/src/x_multiattrib.c:1503
msgid "Delete"
msgstr "اØØ°Ù?"
-#: gschem/src/i_callbacks.c:703
+#: gschem/src/i_callbacks.c:735
msgid "Edit"
msgstr "تØرÙ?ر"
-#: gschem/src/i_callbacks.c:718
+#: gschem/src/i_callbacks.c:750
msgid "Edit pin type"
msgstr "ØرÙ?ر Ù?Ù?ع اÙ?دبÙ?س"
-#: gschem/src/i_callbacks.c:737
+#: gschem/src/i_callbacks.c:769
msgid "Edit Text"
msgstr "ØرÙ?ر اÙ?Ù?ص"
-#: gschem/src/i_callbacks.c:760
+#: gschem/src/i_callbacks.c:792
msgid "Slot"
msgstr "Ø´Ù?Ù?"
-#: gschem/src/i_callbacks.c:777
+#: gschem/src/i_callbacks.c:809
msgid "Color"
msgstr "Ù?Ù?Ù?"
-#: gschem/src/i_callbacks.c:814 gschem/src/i_callbacks.c:859
+#: gschem/src/i_callbacks.c:846 gschem/src/i_callbacks.c:891
msgid "Rotate"
msgstr "أدر"
-#: gschem/src/i_callbacks.c:882 gschem/src/i_callbacks.c:907
+#: gschem/src/i_callbacks.c:913 gschem/src/i_callbacks.c:938
msgid "Mirror"
msgstr "Ù?رآة"
-#: gschem/src/i_callbacks.c:928 gschem/src/x_dialog.c:2315
-#: gschem/lib/system-gschemrc.scm:1422
+#: gschem/src/i_callbacks.c:959 gschem/src/x_dialog.c:2319
+#: gschem/lib/system-gschemrc.scm:1424
msgid "Lock"
msgstr "Ø£Ù?Ù?Ù?"
-#: gschem/src/i_callbacks.c:946 gschem/lib/system-gschemrc.scm:1423
+#: gschem/src/i_callbacks.c:977 gschem/lib/system-gschemrc.scm:1425
msgid "Unlock"
msgstr "Ù?Ù?Ù? اÙ?Ù?Ù?Ù?"
-#: gschem/src/i_callbacks.c:964 gschem/src/x_dialog.c:1734
+#: gschem/src/i_callbacks.c:995 gschem/src/x_dialog.c:1737
msgid "Translate"
msgstr "اسØب"
-#: gschem/src/i_callbacks.c:967
+#: gschem/src/i_callbacks.c:998
msgid "WARNING: Do not translate with snap off!\n"
msgstr "تØØ°Ù?ر: Ù?ا تسØب Ù?ع جذب Ù?Ù?Ù?Ù?!\n"
-#: gschem/src/i_callbacks.c:968
+#: gschem/src/i_callbacks.c:999
msgid "WARNING: Turning snap on and continuing with translate.\n"
msgstr "تØØ°Ù?ر: تشغÙ?Ù? اÙ?جذب Ù? اÙ?Ù?تابعة Ù?ع اÙ?سØب.\n"
-#: gschem/src/i_callbacks.c:975
+#: gschem/src/i_callbacks.c:1006
msgid "WARNING: Snap grid size is not equal to 100!\n"
msgstr "تØØ°Ù?ر: ØجÙ? شبÙ?Ù?Ø© اÙ?جذب Ù?ا Ù?ساÙ?Ù? 100!\n"
-#: gschem/src/i_callbacks.c:977
+#: gschem/src/i_callbacks.c:1008
msgid ""
"WARNING: If you are translating a symbol to the origin, the snap grid size "
"should be set to 100\n"
msgstr ""
"تØØ°Ù?ر: إذا Ù?Ù?ت تسØب رÙ?زا Ø¥Ù?Ù? اÙ?Ù?بدأØ? Ù?جب Ø£Ù? Ù?عÙ?Ù?Ù? ØجÙ? شبÙ?Ù?Ø© اÙ?جذب Ø¥Ù?Ù? 100\n"
-#: gschem/src/i_callbacks.c:1008
+#: gschem/src/i_callbacks.c:1039
msgid "Embed"
msgstr "ضÙ?Ù?Ù?"
-#: gschem/src/i_callbacks.c:1047
+#: gschem/src/i_callbacks.c:1078
msgid "Unembed"
msgstr "Ù?ا تضÙ?Ù?Ù?"
-#: gschem/src/i_callbacks.c:1089
+#: gschem/src/i_callbacks.c:1120
msgid "Update"
msgstr "ØدÙ?Ø«"
-#: gschem/src/i_callbacks.c:1136
+#: gschem/src/i_callbacks.c:1167
msgid "ShowHidden"
msgstr "أظÙ?ر اÙ?Ù?Ø®Ù?Ù?"
-#: gschem/src/i_callbacks.c:1160
-msgid "MakeVisible"
-msgstr "أظÙ?ر"
-
-#: gschem/src/i_callbacks.c:1466 gschem/src/i_callbacks.c:1538
+#: gschem/src/i_callbacks.c:1473 gschem/src/i_callbacks.c:1545
msgid "Pan"
msgstr "اÙ?تÙ?Ù?"
-#: gschem/src/i_callbacks.c:1743
+#: gschem/src/i_callbacks.c:1750
msgid "Really revert page?"
msgstr "ترÙ?د استعادة اÙ?صÙ?ØØ© ØÙ?اØ?"
-#: gschem/src/i_callbacks.c:1813
+#: gschem/src/i_callbacks.c:1820
msgid "Copy to clipboard"
msgstr "اÙ?سخ Ø¥Ù?Ù? اÙ?ØاÙ?ظة"
-#: gschem/src/i_callbacks.c:1831
+#: gschem/src/i_callbacks.c:1838
msgid "Cut to clipboard"
msgstr "Ù?صÙ? Ø¥Ù?Ù? اÙ?ØاÙ?ظة"
-#: gschem/src/i_callbacks.c:1849
+#: gschem/src/i_callbacks.c:1856
msgid "Paste from clipboard"
msgstr "Ø£Ù?صÙ? Ù?Ù? اÙ?ØاÙ?ظة"
-#: gschem/src/i_callbacks.c:1861 gschem/src/i_callbacks.c:2100
-#: gschem/src/i_callbacks.c:2122 gschem/src/i_callbacks.c:2144
-#: gschem/src/i_callbacks.c:2166 gschem/src/i_callbacks.c:2188
+#: gschem/src/i_callbacks.c:1868 gschem/src/i_callbacks.c:2107
+#: gschem/src/i_callbacks.c:2129 gschem/src/i_callbacks.c:2151
+#: gschem/src/i_callbacks.c:2173 gschem/src/i_callbacks.c:2195
msgid "Empty buffer"
msgstr "Ø£Ù?رغ اÙ?Ù?خزÙ?"
-#: gschem/src/i_callbacks.c:1906
+#: gschem/src/i_callbacks.c:1913
msgid "Copy 1"
msgstr "اÙ?سخ 1"
-#: gschem/src/i_callbacks.c:1925
+#: gschem/src/i_callbacks.c:1932
msgid "Copy 2"
msgstr "اÙ?سخ 2"
-#: gschem/src/i_callbacks.c:1944
+#: gschem/src/i_callbacks.c:1951
msgid "Copy 3"
msgstr "اÙ?سخ 3"
-#: gschem/src/i_callbacks.c:1963
+#: gschem/src/i_callbacks.c:1970
msgid "Copy 4"
msgstr "اÙ?سخ 4"
-#: gschem/src/i_callbacks.c:1982
+#: gschem/src/i_callbacks.c:1989
msgid "Copy 5"
msgstr "اÙ?سخ 5"
-#: gschem/src/i_callbacks.c:2001
+#: gschem/src/i_callbacks.c:2008
msgid "Cut 1"
msgstr "Ù?ص 1"
-#: gschem/src/i_callbacks.c:2020
+#: gschem/src/i_callbacks.c:2027
msgid "Cut 2"
msgstr "Ù?ص 2"
-#: gschem/src/i_callbacks.c:2039
+#: gschem/src/i_callbacks.c:2046
msgid "Cut 3"
msgstr "Ù?ص 3"
-#: gschem/src/i_callbacks.c:2058
+#: gschem/src/i_callbacks.c:2065
msgid "Cut 4"
msgstr "Ù?ص 4"
-#: gschem/src/i_callbacks.c:2077
+#: gschem/src/i_callbacks.c:2084
msgid "Cut 5"
msgstr "Ù?ص 5"
-#: gschem/src/i_callbacks.c:2093
+#: gschem/src/i_callbacks.c:2100
msgid "Paste 1"
msgstr "Ø£Ù?صÙ? 1"
-#: gschem/src/i_callbacks.c:2115
+#: gschem/src/i_callbacks.c:2122
msgid "Paste 2"
msgstr "Ø£Ù?صÙ? 2"
-#: gschem/src/i_callbacks.c:2137
+#: gschem/src/i_callbacks.c:2144
msgid "Paste 3"
msgstr "Ø£Ù?صÙ? 3"
-#: gschem/src/i_callbacks.c:2159
+#: gschem/src/i_callbacks.c:2166
msgid "Paste 4"
msgstr "Ø£Ù?صÙ? 4"
-#: gschem/src/i_callbacks.c:2181
+#: gschem/src/i_callbacks.c:2188
msgid "Paste 5"
msgstr "Ø£Ù?صÙ? 5"
-#: gschem/src/i_callbacks.c:2318 gschem/src/x_window.c:355
+#: gschem/src/i_callbacks.c:2325 gschem/src/x_window.c:355
msgid "Component"
msgstr "Ù?Ù?Ù?Ù?Ù?"
-#: gschem/src/i_callbacks.c:2354 gschem/src/i_callbacks.c:2373
-#: gschem/src/x_dialog.c:2285
+#: gschem/src/i_callbacks.c:2361 gschem/src/i_callbacks.c:2380
+#: gschem/src/x_dialog.c:2289
msgid "Attribute"
msgstr "سÙ?Ø©"
-#: gschem/src/i_callbacks.c:2395 gschem/src/i_callbacks.c:2422
-#: gschem/src/x_dialog.c:2282
+#: gschem/src/i_callbacks.c:2402 gschem/src/i_callbacks.c:2429
+#: gschem/src/x_dialog.c:2286
msgid "Net"
msgstr "شبÙ?Ø©"
-#: gschem/src/i_callbacks.c:2466 gschem/src/i_callbacks.c:2493
-#: gschem/src/x_dialog.c:2300 gschem/src/x_window.c:375
+#: gschem/src/i_callbacks.c:2473 gschem/src/i_callbacks.c:2500
+#: gschem/src/x_dialog.c:2304 gschem/src/x_window.c:375
msgid "Bus"
msgstr "Ù?اÙ?Ù?"
-#: gschem/src/i_callbacks.c:2574 gschem/src/i_callbacks.c:2597
+#: gschem/src/i_callbacks.c:2581 gschem/src/i_callbacks.c:2604
msgid "Line"
msgstr "خط"
-#: gschem/src/i_callbacks.c:2619 gschem/src/i_callbacks.c:2642
+#: gschem/src/i_callbacks.c:2626 gschem/src/i_callbacks.c:2649
msgid "Box"
msgstr "إطار"
-#: gschem/src/i_callbacks.c:2698 gschem/src/i_callbacks.c:2722
+#: gschem/src/i_callbacks.c:2705 gschem/src/i_callbacks.c:2729
msgid "Circle"
msgstr "دائرة"
-#: gschem/src/i_callbacks.c:2744 gschem/src/i_callbacks.c:2767
+#: gschem/src/i_callbacks.c:2751 gschem/src/i_callbacks.c:2774
msgid "Arc"
msgstr "Ù?Ù?س"
-#: gschem/src/i_callbacks.c:2789 gschem/src/i_callbacks.c:2812
-#: gschem/src/x_dialog.c:2273
+#: gschem/src/i_callbacks.c:2796 gschem/src/i_callbacks.c:2819
+#: gschem/src/x_dialog.c:2277
msgid "Pin"
msgstr "دبÙ?س"
-#: gschem/src/i_callbacks.c:2871
+#: gschem/src/i_callbacks.c:2878
#, c-format
msgid "Searching for source [%s]\n"
msgstr "اÙ?بØØ« عÙ? اÙ?Ù?Ù?بع [%s]\n"
-#: gschem/src/i_callbacks.c:2895
+#: gschem/src/i_callbacks.c:2902
#, c-format
msgid "Cannot find source [%s]\n"
msgstr "Ù?تعذر اÙ?عثÙ?ر عÙ?Ù? اÙ?Ù?Ù?بع [%s]\n"
-#: gschem/src/i_callbacks.c:2964
+#: gschem/src/i_callbacks.c:2965
#, c-format
msgid "Searching for symbol [%s]\n"
msgstr "اÙ?بØØ« عÙ? اÙ?رÙ?ز [%s]\n"
-#: gschem/src/i_callbacks.c:2970
+#: gschem/src/i_callbacks.c:2971
msgid "Symbol is not a real file. Symbol cannot be loaded.\n"
msgstr "اÙ?رÙ?ز Ù?Ù?س Ù?Ù?Ù?ا ØÙ?Ù?Ù?Ù?ا. Ù?تعذر تØÙ?Ù?Ù? اÙ?رÙ?ز.\n"
-#: gschem/src/i_callbacks.c:3001
+#: gschem/src/i_callbacks.c:3002
msgid "Cannot find any schematics above the current one!\n"
msgstr "Ù?تعذر Ø¥Ù?جاد Ø£Ù? Ù?خطط Ù?Ù?Ù? اÙ?ØاÙ?Ù?!\n"
-#: gschem/src/i_callbacks.c:3055
+#: gschem/src/i_callbacks.c:3056
msgid ""
"This command retrieves the component documentation from the web, but there "
"is no component selected"
msgstr "Ù?ذا اÙ?Ø£Ù?ر Ù?ستردÙ? تÙ?Ø«Ù?Ù? اÙ?Ù?Ù?Ù?Ù?Ù? Ù?Ù? اÙ?Ù?Ù?Ù?عØ? Ù?Ù?Ù? Ù?ا Ù?Ù?جد Ø£Ù? Ù?Ù?Ù?Ù?Ù? Ù?Ù?تÙ?Ù?"
-#: gschem/src/i_callbacks.c:3083
+#: gschem/src/i_callbacks.c:3084
msgid "Attach"
msgstr "أرÙ?Ù?"
-#: gschem/src/i_callbacks.c:3130
+#: gschem/src/i_callbacks.c:3131
msgid "Detach"
msgstr "اÙ?صÙ?"
-#: gschem/src/i_callbacks.c:3165
+#: gschem/src/i_callbacks.c:3166
msgid "ShowN"
msgstr "أظÙ?رN"
-#: gschem/src/i_callbacks.c:3201
+#: gschem/src/i_callbacks.c:3202
msgid "ShowV"
msgstr "أظÙ?رV"
-#: gschem/src/i_callbacks.c:3237
+#: gschem/src/i_callbacks.c:3238
msgid "ShowB"
msgstr "أظÙ?رB"
-#: gschem/src/i_callbacks.c:3274
+#: gschem/src/i_callbacks.c:3275
msgid "VisToggle"
msgstr "تبدÙ?Ù? اÙ?رؤÙ?Ø©"
-#: gschem/src/i_callbacks.c:3304
+#: gschem/src/i_callbacks.c:3305
#, c-format
msgid "Sorry but this is a non-functioning menu option\n"
msgstr "عذرا Ø®Ù?ار اÙ?Ù?ائÙ?Ø© Ù?ذا غÙ?ر Ù?عÙ?اÙ?\n"
-#: gschem/src/i_callbacks.c:3394
+#: gschem/src/i_callbacks.c:3395
msgid "Action feedback mode set to OUTLINE\n"
msgstr "Ù?ضع ردÙ?د اÙ?إجراء Ù?عÙ?Ù?Ù? Ø¥Ù?Ù? Øد اÙ?خارجÙ?\n"
-#: gschem/src/i_callbacks.c:3397
+#: gschem/src/i_callbacks.c:3398
msgid "Action feedback mode set to BOUNDINGBOX\n"
msgstr "Ù?ضع ردÙ?د اÙ?إجراء Ù?عÙ?Ù?Ù? Ø¥Ù?Ù? اÙ?إطار اÙ?Ù?ØÙ?Ø·\n"
-#: gschem/src/i_callbacks.c:3422
+#: gschem/src/i_callbacks.c:3423
msgid "Grid OFF\n"
msgstr "شبÙ?Ù?Ø© Ù?Ù?Ù?Ù?Ø©\n"
-#: gschem/src/i_callbacks.c:3423
+#: gschem/src/i_callbacks.c:3424
msgid "Dot grid selected\n"
msgstr "اÙ?تÙ?Ù?ت اÙ?شبÙ?Ù?Ø© اÙ?Ù?Ù?Ø·Ù?Ø©\n"
-#: gschem/src/i_callbacks.c:3424
+#: gschem/src/i_callbacks.c:3425
msgid "Mesh grid selected\n"
msgstr "اÙ?تÙ?Ù?ت شبÙ?Ù?Ø© اÙ?شرط\n"
-#: gschem/src/i_callbacks.c:3445
+#: gschem/src/i_callbacks.c:3446
msgid "Snap OFF (CAUTION!)\n"
msgstr "اÙ?جذب Ù?Ù?Ù?Ù? (تÙ?بÙ?Ù?)\n"
-#: gschem/src/i_callbacks.c:3448
+#: gschem/src/i_callbacks.c:3449
msgid "Snap ON\n"
msgstr "اÙ?جذب Ù?شغÙ?Ù?\n"
-#: gschem/src/i_callbacks.c:3451
+#: gschem/src/i_callbacks.c:3452
msgid "Snap back to the grid (CAUTION!)\n"
msgstr "جذب Ù?ØÙ? اÙ?شبÙ?Ù?Ø© (تÙ?بÙ?Ù?!)\n"
-#: gschem/src/i_callbacks.c:3477
+#: gschem/src/i_callbacks.c:3478
msgid "Rubber band OFF \n"
msgstr "اÙ?شرÙ?Ø· اÙ?Ù?طاطÙ? Ù?Ù?Ù?Ù? \n"
-#: gschem/src/i_callbacks.c:3480
+#: gschem/src/i_callbacks.c:3481
msgid "Rubber band ON\n"
msgstr "اÙ?شرÙ?Ø· اÙ?Ù?طاطÙ? Ù?شغÙ?\n"
-#: gschem/src/i_callbacks.c:3495
+#: gschem/src/i_callbacks.c:3496
msgid "magnetic net mode: ON\n"
msgstr "Ù?ضع اÙ?شبÙ?Ø© اÙ?Ù?غÙ?اطÙ?سÙ?Ø©: Ù?شغÙ?\n"
-#: gschem/src/i_callbacks.c:3498
+#: gschem/src/i_callbacks.c:3499
msgid "magnetic net mode: OFF\n"
msgstr "Ù?ضع اÙ?شبÙ?Ø© اÙ?Ù?غÙ?اطÙ?سÙ?Ø©: Ù?Ù?Ù?Ù?\n"
-#: gschem/src/o_box.c:153
+#: gschem/src/o_box.c:149
#, c-format
msgid "Unknown type for box (fill)!\n"
msgstr "Ù?Ù?ع Ù?جÙ?Ù?Ù? Ù?Ù?إطار (اÙ?Ù?Ù?Ø¡)!\n"
@@ -715,17 +701,17 @@ msgstr "â??o_buffer_cut: Ù?خزÙ?â?? %i غÙ?ر صاÙ?Ø\n"
msgid "Got an invalid buffer_number [o_buffer_paste_start]\n"
msgstr "ØصÙ?ت عÙ?Ù? buffer_number غÙ?ر صاÙ?Ø [o_buffer_paste_start]\n"
-#: gschem/src/o_bus.c:118
+#: gschem/src/o_bus.c:117
#, c-format
msgid "Got an invalid which one in o_bus_draw_stretch\n"
msgstr "ØصÙ?ت عÙ?Ù? Ø£Ù?Ù?-Ù?اØد غÙ?ر صاÙ?Ø Ù?Ù? o_bus_draw_stretch\n"
-#: gschem/src/o_circle.c:134
+#: gschem/src/o_circle.c:130
#, c-format
msgid "Unknown type for circle (fill)!\n"
msgstr "Ù?Ù?ع Ù?جÙ?Ù?Ù? Ù?Ù?دائرة (اÙ?Ù?Ù?Ø¡)!\n"
-#: gschem/src/o_complex.c:243 gschem/src/o_complex.c:247
+#: gschem/src/o_complex.c:237 gschem/src/o_complex.c:241
#, c-format
msgid "Translating schematic [%d %d]\n"
msgstr "سØب اÙ?Ù?خطط [%d %d]\n"
@@ -743,35 +729,35 @@ msgstr "تÙ? Ø¥Ù?Ù?اÙ? اÙ?Ù?ائÙ? Ù?سبÙ?ا\n"
msgid "Object already unlocked\n"
msgstr "تÙ? Ù?Ù? Ù?Ù?Ù? اÙ?Ù?ائÙ? Ù?سبÙ?ا\n"
-#: gschem/src/o_misc.c:413
+#: gschem/src/o_misc.c:409
msgid "Hidden text is now visible\n"
msgstr "Ø£ØµØ¨Ø Ø§Ù?Ø¢Ù? اÙ?Ù?ص اÙ?Ù?Ø®Ù?Ù? ظاÙ?را\n"
-#: gschem/src/o_misc.c:415
+#: gschem/src/o_misc.c:411
msgid "Hidden text is now invisible\n"
msgstr "Ø£ØµØ¨Ø Ø§Ù?Ø¢Ù? اÙ?Ù?ص اÙ?Ù?Ø®Ù?Ù? Ù?ستترا\n"
-#: gschem/src/o_misc.c:668
+#: gschem/src/o_misc.c:636
#, c-format
msgid "Could not find symbol [%s] in library. Update failed.\n"
msgstr "تعذر اÙ?عثÙ?ر عÙ?Ù? اÙ?رÙ?ز [%s] Ù?Ù? اÙ?Ù?Ù?تبة. Ù?Ø´Ù? اÙ?تØدÙ?Ø«.\n"
-#: gschem/src/o_misc.c:783
+#: gschem/src/o_misc.c:751
#, c-format
msgid "o_autosave_backups: Can't get the real filename of %s."
msgstr "â??o_autosave_backups: تعذر اÙ?ØصÙ?Ù? عÙ?Ù? اسÙ? اÙ?ØÙ?Ù?Ù?Ù? Ù?Ù?Ù?Ù?Ù? %s."
-#: gschem/src/o_misc.c:827
+#: gschem/src/o_misc.c:795
#, c-format
msgid "Could NOT set previous backup file [%s] read-write\n"
msgstr "تعذر تعÙ?Ù?Ù? اÙ?Ù?Ù?Ù? اÙ?اØتÙ?اطÙ? اÙ?سابÙ? [â??%sâ?¬] Ù?Ù?Ù?راءة Ù?اÙ?Ù?تابة\n"
-#: gschem/src/o_misc.c:845
+#: gschem/src/o_misc.c:815
#, c-format
msgid "Could NOT set backup file [%s] readonly\n"
msgstr "تعذر تعÙ?Ù?Ù? اÙ?Ù?Ù?Ù? اÙ?اØتÙ?اطÙ? [â??%sâ?¬] Ù?Ù?Ù?راءة Ù?Ù?Ø·\n"
-#: gschem/src/o_misc.c:850
+#: gschem/src/o_misc.c:820
#, c-format
msgid "Could NOT save backup file [%s]\n"
msgstr "تعذر ØÙ?ظ اÙ?Ù?Ù?Ù? اÙ?اØتÙ?اطÙ? [â??%sâ?¬]\n"
@@ -791,36 +777,36 @@ msgstr "عجبا! ØاÙ?Ù?ت اÙ?عثÙ?ر عÙ?Ù? Ø£Ù?Ù?-Ù?اØد Ù?Ù?Ù?Ù? Ù?Ù?
msgid "Got a non line object in o_move_check_endpoint\n"
msgstr "ØصÙ?ت عÙ?Ù? Ù?ائÙ? غÙ?ر Ù?Ø´Ù?Ù?Ù? Ù?Ù? خط Ù?Ù? o_move_check_endpoint\n"
-#: gschem/src/o_net.c:159
+#: gschem/src/o_net.c:158
#, c-format
msgid "Got an invalid which one in o_net_draw_stretch\n"
msgstr "ØصÙ?ت عÙ?Ù? Ø£Ù?Ù?-Ù?اØد غÙ?ر صاÙ?Ø Ù?Ù? o_net_draw_stretch\n"
-#: gschem/src/o_net.c:538
+#: gschem/src/o_net.c:537
msgid "Warning: Starting net at off grid coordinate\n"
msgstr "تØØ°Ù?ر: بدء اÙ?شبÙ?Ø© خارج Ø¥ØداثÙ?ات اÙ?شبÙ?Ù?Ø©\n"
-#: gschem/src/o_net.c:600
+#: gschem/src/o_net.c:599
msgid "Warning: Ending net at off grid coordinate\n"
msgstr "تØØ°Ù?ر: Ø¥Ù?Ù?اء اÙ?شبÙ?Ø© خارج Ø¥ØداثÙ?ات اÙ?شبÙ?Ù?Ø©\n"
-#: gschem/src/o_net.c:932 gschem/src/o_net.c:969 gschem/src/o_net.c:1040
-#: gschem/src/o_net.c:1076
+#: gschem/src/o_net.c:931 gschem/src/o_net.c:968 gschem/src/o_net.c:1039
+#: gschem/src/o_net.c:1075
#, c-format
msgid "Tried to add more than two bus rippers. Internal gschem error.\n"
msgstr "ØاÙ?Ù?ت إضاÙ?Ø© Ø£Ù?ثر Ù?Ù? اثÙ?Ù?Ù? Ù?Ù? Ù?سارات اÙ?Ù?اÙ?Ù?. خطأ داخÙ?Ù? Ù?â?? gschem.\n"
-#: gschem/src/o_net.c:1144
+#: gschem/src/o_net.c:1143
#, c-format
msgid "Bus ripper symbol [%s] was not found in any component library\n"
msgstr "Ù?Ù? Ù?تÙ? اÙ?عثÙ?ر عÙ?Ù? رÙ?ز Ù?سار اÙ?Ù?اÙ?Ù? [%s] Ù?Ù? Ø£Ù? Ù?Ù?تبة Ù?Ù?Ù?Ù?\n"
-#: gschem/src/o_path.c:352
+#: gschem/src/o_path.c:348
#, c-format
msgid "Unknown type for path (fill)!\n"
msgstr "Ù?Ù?ع Ù?جÙ?Ù?Ù? Ù?Ù?Ù?سار (Ù?Ù?Ø¡)!\n"
-#: gschem/src/o_picture.c:163 gschem/src/o_picture.c:539
+#: gschem/src/o_picture.c:163 gschem/src/o_picture.c:537
#, c-format
msgid "Failed to load picture: %s"
msgstr "Ù?Ø´Ù? تØÙ?Ù?Ù? اÙ?صÙ?رة: %s"
@@ -829,7 +815,7 @@ msgstr "Ù?Ø´Ù? تØÙ?Ù?Ù? اÙ?صÙ?رة: %s"
msgid "Picture"
msgstr "صÙ?رة"
-#: gschem/src/o_picture.c:447 gschem/src/x_attribedit.c:141
+#: gschem/src/o_picture.c:445 gschem/src/x_attribedit.c:141
#, c-format
msgid "ERROR: NULL object!\n"
msgstr "خطأ: Ù?ائÙ? Ù?ارغ (NULL)!\n"
@@ -850,34 +836,46 @@ msgstr "اÙ?تÙ?سÙ?Ù? (اÙ?Ø´Ù?Ù?) غÙ?ر Ù?سÙ?Ù?Ø Ù?Ù?ذا اÙ?Ù?Ù?Ù?Ù?\n"
msgid "New slot number out of range\n"
msgstr "عدد Ø´Ù? جدÙ?د خارج اÙ?Ù?طاÙ?\n"
-#: gschem/src/o_undo.c:304
+#: gschem/src/o_undo.c:303
msgid "Undo/Redo disabled in rc file\n"
msgstr "اÙ?تراجع/اÙ?إعادة Ù?عطÙ?Ù?Ù? Ù?Ù? اÙ?Ù?Ù?Ù? rc\n"
-#: gschem/src/parsecmd.c:47
+#: gschem/src/parsecmd.c:81
#, c-format
msgid ""
-"Usage: %s [OPTIONS] schematic_filename1 ... schematic_filenameN\n"
-" -q Quiet mode\n"
-" -v Verbose mode on\n"
-" -r filename Rc filename\n"
-" -s filename Script (guile) filename\n"
-" -o filename Output filename (for printing)\n"
-" -p Automatically place the window\n"
-" -t Print stroke information\n"
-" -h Help; this message\n"
+"Usage: %s [OPTION ...] [--] [FILE ...]\n"
"\n"
-msgstr ""
-"Usage: %s [OPTIONS] schematic_filename1 ... schematic_filenameN\n"
-" -q Quiet mode\n"
-" -v Verbose mode on\n"
-" -r filename Rc filename\n"
-" -s filename Script (guile) filename\n"
-" -o filename Output filename (for printing)\n"
-" -p Automatically place the window\n"
-" -t Print stroke information\n"
-" -h Help; this message\n"
+"Interactively edit gEDA schematics or symbols. If one or more FILEs\n"
+"are specified, open them for editing; otherwise, create a new, empty\n"
+"schematic.\n"
"\n"
+"Options:\n"
+" -q, --quiet Quiet mode.\n"
+" -v, --verbose Verbose mode.\n"
+" -r, --config-file=FILE Additional configuration file to load.\n"
+" -L DIR Add DIR to Scheme search path.\n"
+" -c EXPR Scheme expression to run at startup.\n"
+" -s FILE Scheme script to run at startup.\n"
+" -o, --output=FILE Output filename (for printing).\n"
+" -p Automatically place the window.\n"
+" -V, --version Show version information.\n"
+" -h, --help Help; this message.\n"
+" -- Treat all remaining arguments as filenames.\n"
+"\n"
+"Report bugs to <geda-bug@xxxxxxxx>\n"
+"gEDA/gaf homepage: <http://gpleda.org>\n"
+msgstr ""
+
+#: gschem/src/parsecmd.c:115
+#, c-format
+msgid ""
+"gEDA %s (g%.7s)\n"
+"Copyright (C) 1998-2011 gEDA developers\n"
+"This is free software, and you are welcome to redistribute it under\n"
+"certain conditions. For details, see the file `COPYING', which is\n"
+"included in the gEDA distribution.\n"
+"There is NO WARRANTY, to the extent permitted by law.\n"
+msgstr ""
#: gschem/src/x_attribedit.c:127
#, c-format
@@ -888,56 +886,56 @@ msgstr "ØصÙ?ت عÙ?Ù? Ø®Ù?ار عرض غÙ?ر صØÙ?Ø Ø?تعÙ?Ù?Ù? اÙ?اÙ?
msgid "Single Attribute Editor"
msgstr "Ù?ØرÙ?ر سÙ?Ø© Ù?Ù?Ù?ردة"
-#: gschem/src/x_attribedit.c:358
+#: gschem/src/x_attribedit.c:359
msgid "<b>Edit Attribute</b>"
msgstr "<b>ØرÙ?ر اÙ?سÙ?Ù?Ø©</b>"
-#: gschem/src/x_attribedit.c:360
+#: gschem/src/x_attribedit.c:361
msgid "<b>Add Attribute</b>"
msgstr "<b>أضÙ? سÙ?Ø©</b>"
-#: gschem/src/x_attribedit.c:376 gschem/src/x_multiattrib.c:1916
+#: gschem/src/x_attribedit.c:377 gschem/src/x_multiattrib.c:1927
msgid "Name:"
msgstr "اÙ?اسÙ?:"
-#: gschem/src/x_attribedit.c:393 gschem/src/x_multiattrib.c:1935
+#: gschem/src/x_attribedit.c:394 gschem/src/x_multiattrib.c:1946
msgid "Value:"
msgstr "اÙ?Ù?Ù?Ù?Ø©:"
-#: gschem/src/x_attribedit.c:409 gschem/src/x_multiattrib.c:1978
+#: gschem/src/x_attribedit.c:410 gschem/src/x_multiattrib.c:1989
msgid "Visible"
msgstr "Ù?رئÙ?"
-#: gschem/src/x_attribedit.c:429
+#: gschem/src/x_attribedit.c:430
msgid "Show Value Only"
msgstr "أظÙ?ر اÙ?Ù?Ù?Ù?Ø© Ù?Ù?Ø·"
-#: gschem/src/x_attribedit.c:431
+#: gschem/src/x_attribedit.c:432
msgid "Show Name Only"
msgstr "أظÙ?ر اÙ?اسÙ? Ù?Ù?Ø·"
-#: gschem/src/x_attribedit.c:433 gschem/src/x_multiattrib.c:1454
+#: gschem/src/x_attribedit.c:434 gschem/src/x_multiattrib.c:1466
msgid "Show Name & Value"
msgstr "أظÙ?ر اÙ?اسÙ? Ù? اÙ?Ù?Ù?Ù?Ø©"
-#: gschem/src/x_attribedit.c:440
+#: gschem/src/x_attribedit.c:441
msgid "<b>Attach Options</b>"
msgstr "<b>أرÙ?Ù? اÙ?Ø®Ù?ارات</b>"
-#: gschem/src/x_attribedit.c:455
+#: gschem/src/x_attribedit.c:456
msgid "All"
msgstr "اÙ?Ù?Ù?"
-#: gschem/src/x_attribedit.c:463 gschem/src/x_compselect.c:896
-#: gschem/src/x_compselect.c:1010
+#: gschem/src/x_attribedit.c:464 gschem/src/x_compselect.c:904
+#: gschem/src/x_compselect.c:1018
msgid "Components"
msgstr "Ù?Ù?Ù?Ù?ات"
-#: gschem/src/x_attribedit.c:471 gschem/src/x_window.c:365
+#: gschem/src/x_attribedit.c:472 gschem/src/x_window.c:365
msgid "Nets"
msgstr "شبÙ?ات"
-#: gschem/src/x_attribedit.c:479
+#: gschem/src/x_attribedit.c:480
msgid "Replace existing attributes"
msgstr "استبدÙ? اÙ?سÙ?ات اÙ?Ù?Ù?جÙ?دة"
@@ -954,91 +952,91 @@ msgid ""
"duplicate slot may cause problems: [symbolname=%s, number=%d, slot=%d]\n"
msgstr "شÙ?Ù? Ù?Ù?رر Ù?د Ù?سبب Ù?شاÙ?Ù?: [اسÙ?â??اÙ?رÙ?ز=%sØ? اÙ?عدد=%dØ? اÙ?Ø´Ù?Ù?=%d]\n"
-#: gschem/src/x_autonumber.c:673
+#: gschem/src/x_autonumber.c:675
msgid "No searchstring given in autonumber text.\n"
msgstr "Ù?ا Ù?Ù?جد Ù?ص بØØ« Ù?Ù? Ù?ص اÙ?ترÙ?Ù?Ù? اÙ?Ø¢Ù?Ù?.\n"
-#: gschem/src/x_autonumber.c:725
+#: gschem/src/x_autonumber.c:727
msgid "No '*' or '?' given at the end of the autonumber text.\n"
msgstr "Ù?ا تÙ?جد '*' Ù? Ù?ا 'Ø?' Ù?Ù? Ù?Ù?اÙ?Ø© Ù?ص اÙ?ترÙ?Ù?Ù? اÙ?Ø¢Ù?Ù?.\n"
-#: gschem/src/x_autonumber.c:860
+#: gschem/src/x_autonumber.c:862
msgid "Diagonal"
msgstr "Ù?طرÙ?"
-#: gschem/src/x_autonumber.c:861
+#: gschem/src/x_autonumber.c:863
msgid "Top to bottom"
msgstr "Ù?Ù? اÙ?أعÙ?Ù? Ù?Ù?أسÙ?Ù?"
-#: gschem/src/x_autonumber.c:861
+#: gschem/src/x_autonumber.c:863
msgid "Bottom to top"
msgstr "Ù?Ù? اÙ?أسÙ?Ù? Ù?Ù?أعÙ?Ù?"
-#: gschem/src/x_autonumber.c:862
+#: gschem/src/x_autonumber.c:864
msgid "Left to right"
msgstr "Ù?Ù? اÙ?Ù?سار Ù?Ù?Ù?Ù?Ù?Ù?"
-#: gschem/src/x_autonumber.c:862
+#: gschem/src/x_autonumber.c:864
msgid "Right to left"
msgstr "Ù?Ù? اÙ?Ù?Ù?Ù?Ù? Ù?Ù?Ù?سار"
-#: gschem/src/x_autonumber.c:863
+#: gschem/src/x_autonumber.c:865
msgid "File order"
msgstr "ترتÙ?ب اÙ?Ù?Ù?Ù?"
-#: gschem/src/x_autonumber.c:1199
+#: gschem/src/x_autonumber.c:1201
msgid "Autonumber text"
msgstr "Ù?ص تعداد Ø¢Ù?Ù?"
-#: gschem/src/x_autonumber.c:1223
+#: gschem/src/x_autonumber.c:1225
msgid "<b>Scope</b>"
msgstr "<b>اÙ?Ù?جاÙ?</b>"
-#: gschem/src/x_autonumber.c:1245
+#: gschem/src/x_autonumber.c:1247
msgid "Search for:"
msgstr "اÙ?بØØ« عÙ?:"
-#: gschem/src/x_autonumber.c:1259
+#: gschem/src/x_autonumber.c:1261
msgid "Autonumber text in:"
msgstr "Ù?ص تعداد Ø¢Ù?Ù? Ù?Ù?:"
-#: gschem/src/x_autonumber.c:1266
+#: gschem/src/x_autonumber.c:1268
msgid "Skip numbers found in:"
msgstr "تخطÙ? اÙ?أرÙ?اÙ? اÙ?Ù?Ù?جÙ?دة Ù?Ù?:"
-#: gschem/src/x_autonumber.c:1278 gschem/src/x_autonumber.c:1287
+#: gschem/src/x_autonumber.c:1280 gschem/src/x_autonumber.c:1289
msgid "Selected objects"
msgstr "اÙ?Ù?ائÙ?ات اÙ?Ù?Ù?تÙ?اة"
-#: gschem/src/x_autonumber.c:1279 gschem/src/x_autonumber.c:1288
+#: gschem/src/x_autonumber.c:1281 gschem/src/x_autonumber.c:1290
msgid "Current page"
msgstr "اÙ?صÙ?ØØ© اÙ?ØاÙ?Ù?Ø©"
-#: gschem/src/x_autonumber.c:1280 gschem/src/x_autonumber.c:1289
+#: gschem/src/x_autonumber.c:1282 gschem/src/x_autonumber.c:1291
msgid "Whole hierarchy"
msgstr "اÙ?تسÙ?سÙ? اÙ?Ù?رÙ?Ù? اÙ?Ù?اÙ?Ù?"
-#: gschem/src/x_autonumber.c:1291
+#: gschem/src/x_autonumber.c:1293
msgid "Overwrite existing numbers"
msgstr "Ø£Ù?تب Ù?Ù?Ù? اÙ?أرÙ?اÙ? اÙ?Ù?Ù?جÙ?دة"
-#: gschem/src/x_autonumber.c:1296
+#: gschem/src/x_autonumber.c:1298
msgid "<b>Options</b>"
msgstr "<b>اÙ?Ø®Ù?ارات</b>"
-#: gschem/src/x_autonumber.c:1318
+#: gschem/src/x_autonumber.c:1320
msgid "Starting number:"
msgstr "رÙ?Ù? اÙ?بدأ:"
-#: gschem/src/x_autonumber.c:1325
+#: gschem/src/x_autonumber.c:1327
msgid "Sort order:"
msgstr "اÙ?ترتÙ?ب:"
-#: gschem/src/x_autonumber.c:1346
+#: gschem/src/x_autonumber.c:1348
msgid "Remove numbers"
msgstr "أزÙ? اÙ?أعداد"
-#: gschem/src/x_autonumber.c:1350
+#: gschem/src/x_autonumber.c:1352
msgid "Automatic slotting"
msgstr "Ø´Ù?Ù? Ø¢Ù?Ù?"
@@ -1075,48 +1073,48 @@ msgstr "ØاÙ?Ù? اÙ?ØصÙ?Ù? عÙ?Ù? Ù?Ù?Ù? غÙ?ر صاÙ?Ø: %d\n"
msgid "Tried to get an invalid outline color: %d\n"
msgstr "ØاÙ?Ù? اÙ?ØصÙ?Ù? عÙ?Ù? Ù?Ù?Ù? خط خارجÙ? غÙ?ر صاÙ?Ø: %d\n"
-#: gschem/src/x_compselect.c:1040
+#: gschem/src/x_compselect.c:1048
msgid "Filter:"
msgstr "اÙ?Ù?رشØ:"
-#: gschem/src/x_compselect.c:1143 gschem/src/x_dialog.c:3663
-#: gschem/src/x_multiattrib.c:1782
+#: gschem/src/x_compselect.c:1151 gschem/src/x_dialog.c:3667
+#: gschem/src/x_multiattrib.c:1793
msgid "Name"
msgstr "اسÙ?"
-#: gschem/src/x_compselect.c:1152 gschem/src/x_multiattrib.c:1806
+#: gschem/src/x_compselect.c:1160 gschem/src/x_multiattrib.c:1817
msgid "Value"
msgstr "Ù?Ù?Ù?Ø©"
-#: gschem/src/x_compselect.c:1191
+#: gschem/src/x_compselect.c:1199
msgid "Default behavior - reference component"
msgstr "اÙ?سÙ?Ù?Ù? اÙ?اÙ?تراضÙ? - اÙ?عÙ?صر اÙ?Ù?رجعÙ?"
-#: gschem/src/x_compselect.c:1194
+#: gschem/src/x_compselect.c:1202
msgid "Embed component in schematic"
msgstr "ضÙ?Ù?Ù? اÙ?Ù?Ù?Ù?Ù? Ù?Ù? اÙ?Ù?خطط"
-#: gschem/src/x_compselect.c:1197
+#: gschem/src/x_compselect.c:1205
msgid "Include component as individual objects"
msgstr "ضÙ?Ù?Ù? اÙ?Ù?Ù?Ù?Ù? Ù?Ù?ائÙ?ات Ù?ردÙ?Ø©"
-#: gschem/src/x_compselect.c:1354
+#: gschem/src/x_compselect.c:1362
msgid "Select Component..."
msgstr "اÙ?تÙ? Ù?Ù?Ù?Ù?ا..."
-#: gschem/src/x_compselect.c:1377
+#: gschem/src/x_compselect.c:1385
msgid "In Use"
msgstr "Ù?Ù?د اÙ?استخداÙ?"
-#: gschem/src/x_compselect.c:1381
+#: gschem/src/x_compselect.c:1389
msgid "Libraries"
msgstr "Ù?Ù?تبات"
-#: gschem/src/x_compselect.c:1390 gschem/src/x_fileselect.c:122
+#: gschem/src/x_compselect.c:1398 gschem/src/x_fileselect.c:122
msgid "Preview"
msgstr "Ù?عاÙ?Ù?Ø©"
-#: gschem/src/x_compselect.c:1418
+#: gschem/src/x_compselect.c:1426
msgid "Attributes"
msgstr "سÙ?ات"
@@ -1174,139 +1172,139 @@ msgstr "اÙ?Ù?Ù?Ù?Ù? اÙ?سÙ?Ù?Ù?"
msgid "Edit Text Properties"
msgstr "ØرÙ?ر خصائص اÙ?Ù?ص"
-#: gschem/src/x_dialog.c:471
+#: gschem/src/x_dialog.c:472
msgid "<b>Text Content</b>"
msgstr "<b>Ù?ØتÙ?Ù? اÙ?Ù?ص</b>"
-#: gschem/src/x_dialog.c:507
+#: gschem/src/x_dialog.c:508
msgid "<b>Text Properties</b>"
msgstr "<b>خصائص اÙ?Ù?ص</b>"
-#: gschem/src/x_dialog.c:522
+#: gschem/src/x_dialog.c:523
msgid "Color:"
msgstr "اÙ?Ù?Ù?Ù?:"
-#: gschem/src/x_dialog.c:529
+#: gschem/src/x_dialog.c:530
msgid "Size:"
msgstr "اÙ?ØجÙ?:"
-#: gschem/src/x_dialog.c:538
+#: gschem/src/x_dialog.c:539
msgid "Alignment:"
msgstr "اÙ?Ù?Øاذاة:"
-#: gschem/src/x_dialog.c:587
+#: gschem/src/x_dialog.c:588
msgid "Solid"
msgstr "Ù?تÙ?اصÙ?"
-#: gschem/src/x_dialog.c:588
+#: gschem/src/x_dialog.c:589
msgid "Dotted"
msgstr "Ù?Ù?Ù?Ø·"
-#: gschem/src/x_dialog.c:589
+#: gschem/src/x_dialog.c:590
msgid "Dashed"
msgstr "Ø´Ù?رÙ?Ø·"
-#: gschem/src/x_dialog.c:590
+#: gschem/src/x_dialog.c:591
msgid "Center"
msgstr "Ù?سط"
-#: gschem/src/x_dialog.c:591
+#: gschem/src/x_dialog.c:592
msgid "Phantom"
msgstr "Ù?Ù?Ù?"
-#: gschem/src/x_dialog.c:592 gschem/src/x_dialog.c:689
-#: gschem/src/x_dialog.c:698 gschem/src/x_dialog.c:707
-#: gschem/src/x_dialog.c:808 gschem/src/x_dialog.c:810
-#: gschem/src/x_dialog.c:812 gschem/src/x_dialog.c:1038
-#: gschem/src/x_dialog.c:1141 gschem/src/x_dialog.c:1150
-#: gschem/src/x_dialog.c:1159 gschem/src/x_dialog.c:1168
-#: gschem/src/x_dialog.c:1177 gschem/src/x_dialog.c:1290
-#: gschem/src/x_dialog.c:1292 gschem/src/x_dialog.c:1294
-#: gschem/src/x_dialog.c:1296 gschem/src/x_dialog.c:1298
+#: gschem/src/x_dialog.c:593 gschem/src/x_dialog.c:690
+#: gschem/src/x_dialog.c:699 gschem/src/x_dialog.c:708
+#: gschem/src/x_dialog.c:809 gschem/src/x_dialog.c:811
+#: gschem/src/x_dialog.c:813 gschem/src/x_dialog.c:1039
+#: gschem/src/x_dialog.c:1142 gschem/src/x_dialog.c:1151
+#: gschem/src/x_dialog.c:1160 gschem/src/x_dialog.c:1169
+#: gschem/src/x_dialog.c:1178 gschem/src/x_dialog.c:1291
+#: gschem/src/x_dialog.c:1293 gschem/src/x_dialog.c:1295
+#: gschem/src/x_dialog.c:1297 gschem/src/x_dialog.c:1299
msgid "*unchanged*"
msgstr "*Ù?Ù? Ù?غÙ?Ù?ر*"
-#: gschem/src/x_dialog.c:916
+#: gschem/src/x_dialog.c:917
msgid "Edit Line Width & Type"
msgstr "ØرÙ?ر عرض Ù? Ù?Ù?ع اÙ?خط"
-#: gschem/src/x_dialog.c:955 gschem/src/x_print.c:307
+#: gschem/src/x_dialog.c:956 gschem/src/x_print.c:307
msgid "Type:"
msgstr "اÙ?Ù?Ù?Ù?ع:"
-#: gschem/src/x_dialog.c:959
+#: gschem/src/x_dialog.c:960
msgid "Width:"
msgstr "اÙ?عرض:"
-#: gschem/src/x_dialog.c:963
+#: gschem/src/x_dialog.c:964
msgid "Dash Length:"
msgstr "Ø·Ù?Ù? اÙ?شرطة:"
-#: gschem/src/x_dialog.c:967
+#: gschem/src/x_dialog.c:968
msgid "Dash Space:"
msgstr "Ù?راغ اÙ?شرطة:"
-#: gschem/src/x_dialog.c:1034
+#: gschem/src/x_dialog.c:1035
msgid "Hollow"
msgstr "Ù?جÙ?Ù?Ù?"
-#: gschem/src/x_dialog.c:1035
+#: gschem/src/x_dialog.c:1036
msgid "Filled"
msgstr "Ù?Ù?Ù?Ù?Ø¡"
-#: gschem/src/x_dialog.c:1036
+#: gschem/src/x_dialog.c:1037
msgid "Mesh"
msgstr "Ø®Ù?Ø· اÙ?شبÙ?Ø©"
-#: gschem/src/x_dialog.c:1037
+#: gschem/src/x_dialog.c:1038
msgid "Hatch"
msgstr "تÙ?Ø´Ù?ر"
-#: gschem/src/x_dialog.c:1406
+#: gschem/src/x_dialog.c:1407
msgid "Edit Fill Type"
msgstr "ØرÙ?ر Ù?Ù?ع اÙ?Ù?Ù?Ø¡"
-#: gschem/src/x_dialog.c:1444
+#: gschem/src/x_dialog.c:1446
msgid "Fill Type:"
msgstr "Ù?Ù?ع اÙ?Ù?Ù?Ø¡:"
-#: gschem/src/x_dialog.c:1448
+#: gschem/src/x_dialog.c:1450
msgid "Line Width:"
msgstr "عرض اÙ?خط:"
-#: gschem/src/x_dialog.c:1452
+#: gschem/src/x_dialog.c:1454
msgid "Angle 1:"
msgstr "اÙ?زاÙ?Ù?Ø© 1:"
-#: gschem/src/x_dialog.c:1456
+#: gschem/src/x_dialog.c:1458
msgid "Pitch 1:"
msgstr "اÙ?Ø¥Ù?Øدار 1:"
-#: gschem/src/x_dialog.c:1460
+#: gschem/src/x_dialog.c:1462
msgid "Angle 2:"
msgstr "اÙ?زاÙ?Ù?Ø© 2:"
-#: gschem/src/x_dialog.c:1464
+#: gschem/src/x_dialog.c:1466
msgid "Pitch 2:"
msgstr "اÙ?Ø¥Ù?Øدار 2:"
-#: gschem/src/x_dialog.c:1591
+#: gschem/src/x_dialog.c:1593
msgid "Arc Params"
msgstr "Ù?عاÙ?Ù?ات اÙ?Ù?Ù?س"
-#: gschem/src/x_dialog.c:1631
+#: gschem/src/x_dialog.c:1634
msgid "Arc Radius:"
msgstr "شعاع اÙ?Ù?Ù?س:"
-#: gschem/src/x_dialog.c:1639
+#: gschem/src/x_dialog.c:1642
msgid "Start Angle:"
msgstr "زاÙ?Ù?Ø© اÙ?بدأ:"
-#: gschem/src/x_dialog.c:1647
+#: gschem/src/x_dialog.c:1650
msgid "Degrees of Sweep:"
msgstr "درجات اÙ?اجتÙ?اØ:"
-#: gschem/src/x_dialog.c:1764
+#: gschem/src/x_dialog.c:1768
msgid ""
"Offset to translate?\n"
"(0 for origin)"
@@ -1314,198 +1312,198 @@ msgstr ""
"Ù?Ù?Ù?Ø© اÙ?إزاØØ© Ù?Ù? أجÙ? اÙ?سØبØ?\n"
"(0 Ù?Ù? أجÙ? اÙ?Ù?بدأ)"
-#: gschem/src/x_dialog.c:1832
+#: gschem/src/x_dialog.c:1836
msgid "Text Size"
msgstr "ØجÙ? اÙ?Ù?ص"
-#: gschem/src/x_dialog.c:1862
+#: gschem/src/x_dialog.c:1866
msgid "Enter new text size:"
msgstr "أدخÙ? ØجÙ? Ù?ص جدÙ?د:"
-#: gschem/src/x_dialog.c:1938
+#: gschem/src/x_dialog.c:1942
msgid "Snap Size"
msgstr "ØجÙ? اÙ?جذب"
-#: gschem/src/x_dialog.c:1968
+#: gschem/src/x_dialog.c:1972
msgid "Enter new snap grid spacing:"
msgstr "أدخÙ? تباعد جدÙ?د Ù?شبÙ?Ù?Ø© اÙ?جذب:"
-#: gschem/src/x_dialog.c:2045
+#: gschem/src/x_dialog.c:2049
msgid "Edit slot number"
msgstr "ØرÙ?ر عدد اÙ?Ø´Ù?Ù?"
-#: gschem/src/x_dialog.c:2076
+#: gschem/src/x_dialog.c:2080
msgid "Edit slot number:"
msgstr "تØرÙ?ر عدد اÙ?Ø´Ù?Ù?:"
-#: gschem/src/x_dialog.c:2117
+#: gschem/src/x_dialog.c:2121
#, c-format
msgid "%s%s (%s)"
msgstr ""
-#: gschem/src/x_dialog.c:2140
+#: gschem/src/x_dialog.c:2144
msgid "About gschem"
msgstr "عÙ? gschem"
-#: gschem/src/x_dialog.c:2141
+#: gschem/src/x_dialog.c:2145
msgid "gEDA: GPL Electronic Design Automation"
msgstr "gEDA: GPL Electronic Design Automation (أتÙ?تة اÙ?تصÙ?Ù?Ù? اÙ?Ø¥Ù?Ù?ترÙ?Ù?Ù?)"
-#: gschem/src/x_dialog.c:2142
+#: gschem/src/x_dialog.c:2146
msgid ""
"Copyright © 1998-2009 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
"Copyright © 1998-2009 gEDA Contributors (see ChangeLog for details)"
msgstr ""
-#: gschem/src/x_dialog.c:2201
+#: gschem/src/x_dialog.c:2205
msgid "Coords"
msgstr "Ø¥ØداثÙ?ات"
-#: gschem/src/x_dialog.c:2222
+#: gschem/src/x_dialog.c:2226
msgid "Screen"
msgstr "شاشة"
-#: gschem/src/x_dialog.c:2231
+#: gschem/src/x_dialog.c:2235
msgid "World"
msgstr "عاÙ?Ù?"
-#: gschem/src/x_dialog.c:2270
+#: gschem/src/x_dialog.c:2274
msgid "Background"
msgstr "Ø®Ù?Ù?Ù?Ù?Ø©"
-#: gschem/src/x_dialog.c:2276
+#: gschem/src/x_dialog.c:2280
msgid "Net endpoint"
msgstr "Ù?Ù?طة اÙ?Ù?Ù?اÙ?Ø© Ù?Ù?شبÙ?Ø©"
-#: gschem/src/x_dialog.c:2279
+#: gschem/src/x_dialog.c:2283
msgid "Graphic"
msgstr "رسÙ?"
-#: gschem/src/x_dialog.c:2288
+#: gschem/src/x_dialog.c:2292
msgid "Logic bubble"
msgstr "Ù?Ù?اعة اÙ?Ù?Ù?Ø·Ù?"
-#: gschem/src/x_dialog.c:2291
+#: gschem/src/x_dialog.c:2295
msgid "Grid point"
msgstr "Ù?Ù?طة شبÙ?Ù?Ø©"
-#: gschem/src/x_dialog.c:2294
+#: gschem/src/x_dialog.c:2298
msgid "Detached attribute"
msgstr "سÙ?Ø© Ù?Ù?صÙ?Ù?Ø©"
-#: gschem/src/x_dialog.c:2297 gschem/src/x_window.c:383
+#: gschem/src/x_dialog.c:2301 gschem/src/x_window.c:383
msgid "Text"
msgstr "Ù?ص"
-#: gschem/src/x_dialog.c:2303
+#: gschem/src/x_dialog.c:2307
msgid "Selection"
msgstr "Ù?Ù?تÙ?Ù?"
-#: gschem/src/x_dialog.c:2306
+#: gschem/src/x_dialog.c:2310
msgid "Bounding box"
msgstr "Ù?ربع Ø¥Øاطة"
-#: gschem/src/x_dialog.c:2309
+#: gschem/src/x_dialog.c:2313
msgid "Zoom box"
msgstr "Ù?رÙ?ب اÙ?Ù?ربع"
-#: gschem/src/x_dialog.c:2318
+#: gschem/src/x_dialog.c:2322
msgid "Output background"
msgstr "خÙ?Ù?Ù?Ø© اÙ?إخراج"
-#: gschem/src/x_dialog.c:2321
+#: gschem/src/x_dialog.c:2325
msgid "Net junction"
msgstr "Ù?صÙ?Ø© شبÙ?Ø©"
-#: gschem/src/x_dialog.c:2324
+#: gschem/src/x_dialog.c:2328
msgid "Mesh grid major"
msgstr "أساسÙ? - Ø®Ù?Ø· اÙ?شبÙ?Ù?Ø©"
-#: gschem/src/x_dialog.c:2327
+#: gschem/src/x_dialog.c:2331
msgid "Mesh grid minor"
msgstr "ثاÙ?Ù?Ù? - Ø®Ù?Ø· اÙ?شبÙ?Ù?Ø©"
-#: gschem/src/x_dialog.c:2330
+#: gschem/src/x_dialog.c:2334
msgid "Unknown"
msgstr "Ù?جÙ?Ù?Ù?"
-#: gschem/src/x_dialog.c:2481
+#: gschem/src/x_dialog.c:2485
#, c-format
msgid "ERROR: NULL object in color_edit_dialog_apply!\n"
msgstr "خطأ: Ù?ائÙ? Ù?ارغ (NULL) Ù?Ù? color_edit_dialog_apply!\n"
-#: gschem/src/x_dialog.c:2525
+#: gschem/src/x_dialog.c:2529
msgid "Color Edit"
msgstr "تØرÙ?ر اÙ?Ù?Ù?Ù?"
-#: gschem/src/x_dialog.c:2556
+#: gschem/src/x_dialog.c:2560
msgid "Object color:"
msgstr "Ù?Ù?Ù? اÙ?Ù?ائÙ?:"
-#: gschem/src/x_dialog.c:2614
+#: gschem/src/x_dialog.c:2618
msgid "Hotkeys"
msgstr "Ù?Ù?اتÙ?Ø Ø³Ø§Ø®Ù?Ø©"
-#: gschem/src/x_dialog.c:2678
+#: gschem/src/x_dialog.c:2682
msgid "Function"
msgstr "Ù?ظÙ?Ù?Ø©"
-#: gschem/src/x_dialog.c:2685
+#: gschem/src/x_dialog.c:2689
msgid "Keystroke(s)"
msgstr "ضغطة Ù?Ù?اتÙ?Ø"
-#: gschem/src/x_dialog.c:2991
+#: gschem/src/x_dialog.c:2995
msgid "Find Text"
msgstr "ابØØ« عÙ? Ù?ص"
-#: gschem/src/x_dialog.c:3022
+#: gschem/src/x_dialog.c:3026
msgid "Text to find:"
msgstr "اÙ?Ù?ص اÙ?Ù?Ø·Ù?Ù?ب:"
-#: gschem/src/x_dialog.c:3032
+#: gschem/src/x_dialog.c:3036
msgid "descend into hierarchy"
msgstr "اÙ?Øدر Ù?Ù? اÙ?تسÙ?سÙ? اÙ?Ù?رÙ?Ù?"
-#: gschem/src/x_dialog.c:3097
+#: gschem/src/x_dialog.c:3101
msgid "Hide Text"
msgstr "أخÙ? اÙ?Ù?ص"
-#: gschem/src/x_dialog.c:3128
+#: gschem/src/x_dialog.c:3132
msgid "Hide text starting with:"
msgstr "أخÙ? اÙ?Ù?ص اÙ?بادئ بÙ?:"
-#: gschem/src/x_dialog.c:3197
+#: gschem/src/x_dialog.c:3201
msgid "Show Text"
msgstr "أظÙ?ر اÙ?Ù?ص"
-#: gschem/src/x_dialog.c:3228
+#: gschem/src/x_dialog.c:3232
msgid "Show text starting with:"
msgstr "أظÙ?ر اÙ?Ù?ص اÙ?بادئ بÙ?:"
-#: gschem/src/x_dialog.c:3685
+#: gschem/src/x_dialog.c:3689
msgid "S_elect the schematics you want to save:"
msgstr "اÙ?تÙ? اÙ?Ù?خططات اÙ?تÙ? ترÙ?د ØÙ?ظÙ?ا:"
-#: gschem/src/x_dialog.c:3779
+#: gschem/src/x_dialog.c:3784
#, c-format
msgid "Save the changes to schematic \"%s\" before closing?"
msgstr "Ù?Ù? ترÙ?د ØÙ?ظ اÙ?تغÙ?Ù?رات Ø¥Ù?Ù? اÙ?Ù?خطط \"%s\" Ù?بÙ? اÙ?إغÙ?اÙ?Ø?"
-#: gschem/src/x_dialog.c:3785
+#: gschem/src/x_dialog.c:3790
#, c-format
msgid ""
"There are %d schematics with unsaved changes. Save changes before closing?"
msgstr "Ù?Ù?اÙ? %d Ù?خطط Ù?ع تغÙ?Ù?رات غÙ?ر Ù?ØÙ?Ù?ظة. Ù?Ù? ترÙ?د ØÙ?ظ اÙ?تغÙ?Ù?رات Ù?بÙ? اÙ?إغÙ?اÙ?Ø?"
-#: gschem/src/x_dialog.c:3814
+#: gschem/src/x_dialog.c:3819
msgid "If you don't save, all your changes will be permanently lost."
msgstr "ستضÙ?ع جÙ?Ù?ع اÙ?تÙ?غÙ?Ù?رات Ù?Ù?أبد إذا Ù?Ù? تØÙ?ظ."
-#: gschem/src/x_dialog.c:3834
+#: gschem/src/x_dialog.c:3839
msgid "_Close without saving"
msgstr "Ø£_غÙ?Ù? دÙ?Ù? ØÙ?ظ"
-#: gschem/src/x_dialog.c:4170
+#: gschem/src/x_dialog.c:4175
#, c-format
msgid ""
"<span weight=\"bold\" size=\"larger\">The input attribute \"%s\" is invalid\n"
@@ -1522,19 +1520,19 @@ msgstr ""
"Ù?ا Ù?Ù?Ù?Ù? Ø£Ù? Ù?Ù?تÙ?Ù? اÙ?اسÙ? بÙ?ساÙ?Ø©.\n"
"Ù?ا Ù?Ù?Ù?Ù? بدء اÙ?Ù?Ù?Ù?Ø© بÙ?ساÙ?Ø©."
-#: gschem/src/x_dialog.c:4172
+#: gschem/src/x_dialog.c:4177
msgid "Invalid Attribute"
msgstr "سÙ?Ø© غÙ?ر صاÙ?ØØ©"
-#: gschem/src/x_dialog.c:4208
+#: gschem/src/x_dialog.c:4213
msgid "Pin type"
msgstr "Ù?Ù?ع اÙ?دبÙ?س"
-#: gschem/src/x_dialog.c:4232
+#: gschem/src/x_dialog.c:4237
msgid "Net pin"
msgstr "دبÙ?س Ù?شبÙ?Ø©"
-#: gschem/src/x_dialog.c:4234
+#: gschem/src/x_dialog.c:4239
msgid "Bus pin (graphical)"
msgstr "دبÙ?س Ù?Ù?اÙ?Ù? (رسÙ?Ù?Ù?)"
@@ -1634,11 +1632,11 @@ msgstr "Ù?Ù?ع اÙ?صÙ?رة"
msgid "Write image..."
msgstr "Ø£Ù?تب صÙ?رة..."
-#: gschem/src/x_log.c:188
+#: gschem/src/x_log.c:209
msgid "** Invalid UTF-8 in log message. See stderr or gschem.log.\n"
msgstr "â??** UTF-8 غÙ?ر صاÙ?Ø Ù?Ù? رساÙ?Ø© سجÙ?. راجع stderr Ø£Ù? gschem.log.\n"
-#: gschem/src/x_log.c:256
+#: gschem/src/x_log.c:288
msgid "Status"
msgstr "اÙ?ØاÙ?Ø©"
@@ -1714,69 +1712,60 @@ msgstr "/اÙ?زÙ? Ø¥Ù?Ù? اÙ?رÙ?ز"
msgid "/Up"
msgstr "/اصعد"
-#: gschem/src/x_menus.c:321
+#: gschem/src/x_menus.c:323
#, c-format
msgid "Tried to set the sensitivity on non-existent menu item '%s'\n"
msgstr "Ù?ØاÙ?Ù?Ø© تعÙ?Ù?Ù? اÙ?ØساسÙ?Ø© عÙ?Ù? عÙ?صر Ù?ائÙ?Ø© غÙ?ر Ù?Ù?جÙ?د '%s'\n"
-#: gschem/src/x_menus.c:345
+#: gschem/src/x_menus.c:347
msgid "Popup_menu_item_factory doesn't exist!\n"
msgstr "Ù?صÙ?ع-عÙ?صر-اÙ?Ù?ائÙ?Ø©-اÙ?Ù?Ù?بثÙ?Ø© غÙ?ر Ù?Ù?جÙ?د!\n"
-#: gschem/src/x_menus.c:358
+#: gschem/src/x_menus.c:360
msgid "Tried to set the sensitivity on a non-existent popup menu_item\n"
msgstr "Ù?ØاÙ?Ù?Ø© تعÙ?Ù?Ù? اÙ?ØساسÙ?Ø© عÙ?Ù? عÙ?صر Ù?ائÙ?Ø© Ù?Ù?بثÙ?Ø© غÙ?ر Ù?Ù?جÙ?د '%s'\n"
-#: gschem/src/x_menus.c:438
-#, c-format
-msgid "Couldn't open file %s\n"
-msgstr "تعذر Ù?ØªØ Ø§Ù?Ù?Ù?Ù? %s\n"
-
-#: gschem/src/x_menus.c:495
-msgid "Clear"
-msgstr "اÙ?سØ"
-
-#: gschem/src/x_multiattrib.c:911
+#: gschem/src/x_multiattrib.c:915
msgid "Attributes with empty name are not allowed. Please set a name."
msgstr "غÙ?ر Ù?سÙ?Ù?Ø Ø¨Ø³Ù?ات Ù?ع اسÙ? Ù?ارغ. اÙ?رجاء تعÙ?Ù?Ù? اسÙ?."
-#: gschem/src/x_multiattrib.c:1456
+#: gschem/src/x_multiattrib.c:1468
msgid "Show Value only"
msgstr "أظÙ?ر اÙ?Ù?Ù?Ù?Ø© Ù?Ù?Ø·"
-#: gschem/src/x_multiattrib.c:1458
+#: gschem/src/x_multiattrib.c:1470
msgid "Show Name only"
msgstr "أظÙ?ر اÙ?اسÙ? Ù?Ù?Ø·"
-#: gschem/src/x_multiattrib.c:1486
+#: gschem/src/x_multiattrib.c:1498
msgid "Promote"
msgstr "رÙ?Ù?Ù?Ù?"
-#: gschem/src/x_multiattrib.c:1490
+#: gschem/src/x_multiattrib.c:1502
msgid "Duplicate"
msgstr "ضاعÙ?"
-#: gschem/src/x_multiattrib.c:1708
+#: gschem/src/x_multiattrib.c:1719
msgid "Edit Attributes"
msgstr "ØرÙ?ر اÙ?Ù?Ù?اصÙ?ات"
-#: gschem/src/x_multiattrib.c:1826
+#: gschem/src/x_multiattrib.c:1837
msgid "Vis?"
msgstr "ظاÙ?رØ?"
-#: gschem/src/x_multiattrib.c:1844
+#: gschem/src/x_multiattrib.c:1855
msgid "N"
msgstr "N"
-#: gschem/src/x_multiattrib.c:1862
+#: gschem/src/x_multiattrib.c:1873
msgid "V"
msgstr "V"
-#: gschem/src/x_multiattrib.c:1884
+#: gschem/src/x_multiattrib.c:1895
msgid "Show inherited attributes"
msgstr "أظÙ?ر اÙ?سÙ?ات اÙ?Ù?Ù?رÙ?ثة"
-#: gschem/src/x_multiattrib.c:1900
+#: gschem/src/x_multiattrib.c:1911
msgid "Add Attribute"
msgstr "أضÙ? سÙ?Ø©"
@@ -1800,23 +1789,23 @@ msgstr "أغÙ?Ù? اÙ?صÙ?ØØ©"
msgid "Discard Page"
msgstr "Ø£Ù?Ù?Ù? اÙ?صÙ?ØØ©"
-#: gschem/src/x_pagesel.c:376
+#: gschem/src/x_pagesel.c:375
msgid "Page Manager"
msgstr "Ù?دÙ?ر اÙ?صÙ?Øات"
-#: gschem/src/x_pagesel.c:432
+#: gschem/src/x_pagesel.c:431
msgid "Filename"
msgstr "اسÙ? اÙ?Ù?Ù?Ù?"
-#: gschem/src/x_pagesel.c:448
+#: gschem/src/x_pagesel.c:447
msgid "Changed"
msgstr "غÙ?Ù?Ù?ر"
-#: gschem/src/x_pagesel.c:468
+#: gschem/src/x_pagesel.c:467
msgid "Right click on the filename for more options..."
msgstr "Ù?Ù?رة Ù?Ù?Ù?Ù? Ù?Ù?Ù? اسÙ? اÙ?Ù?Ù?Ù? Ù?Ù?ØصÙ?Ù? عÙ?Ù? اÙ?Ù?زÙ?د Ù?Ù? اÙ?Ø®Ù?ارات..."
-#: gschem/src/x_preview.c:234
+#: gschem/src/x_preview.c:233
msgid "Preview Buffer"
msgstr "Ù?عاÙ?Ù?Ø© اÙ?Ù?خزÙ?"
@@ -1872,16 +1861,16 @@ msgstr "اÙ?Ù?Ù?Ù?:"
msgid "Command:"
msgstr "اÙ?Ø£Ù?ر:"
-#: gschem/src/x_print.c:741
+#: gschem/src/x_print.c:745
msgid "No print destination specified\n"
msgstr "Ù?Ù? تعÙ?Ù?Ù? Ù?جÙ?Ø© Ù?Ù?طباعة\n"
-#: gschem/src/x_print.c:748
+#: gschem/src/x_print.c:752
#, c-format
msgid "Cannot print current schematic to [%s]\n"
msgstr "Ù?ا Ù?Ù?Ù?Ù? طباعة اÙ?Ù?خطط اÙ?ØاÙ?Ù? Ø¥Ù?Ù? [â??%sâ?¬]\n"
-#: gschem/src/x_print.c:757
+#: gschem/src/x_print.c:761
#, c-format
msgid ""
"Error printing to file '%s'\n"
@@ -1890,7 +1879,7 @@ msgstr ""
"خطأ Ù?Ù? اÙ?طباعة Ø¥Ù?Ù? اÙ?Ù?Ù?Ù? '%s'\n"
"تØÙ?Ù? Ù?Ù? Ù?اÙ?ذة اÙ?سجÙ? Ù?Ù?Ù?زÙ?د Ù?Ù? اÙ?Ù?عÙ?Ù?Ù?ات"
-#: gschem/src/x_print.c:764
+#: gschem/src/x_print.c:768
#, c-format
msgid "Printed current schematic to [%s]\n"
msgstr "Ø·Ù?بع اÙ?Ù?خطط اÙ?ØاÙ?Ù? Ø¥Ù?Ù? [â??%sâ?¬]\n"
@@ -1899,6 +1888,11 @@ msgstr "Ø·Ù?بع اÙ?Ù?خطط اÙ?ØاÙ?Ù? Ø¥Ù?Ù? [â??%sâ?¬]\n"
msgid "Execute Script..."
msgstr "Ù?Ù?Ø° Ù?خطÙ?طا (سÙ?ربت)..."
+#: gschem/src/x_script.c:66
+#, c-format
+msgid "Executing guile script [%s]\n"
+msgstr "تÙ?Ù?Ù?Ø° Ù?خطÙ?Ø· guile [â??%sâ?¬]\n"
+
#: gschem/src/x_window.c:81
#, c-format
msgid "Couldn't allocate gc\n"
@@ -2014,35 +2008,35 @@ msgstr "Ù?Ø´Ù? تØÙ?Ù?Ù? اÙ?Ù?Ù?Ù?"
msgid "New file [%s]\n"
msgstr "Ù?Ù?Ù? جدÙ?د [â??%sâ?¬]\n"
-#: gschem/src/x_window.c:857
+#: gschem/src/x_window.c:855
#, c-format
msgid "Could NOT save page [%s]\n"
msgstr "تعذÙ?ر ØÙ?ظ اÙ?صÙ?ØØ© [â??%sâ?¬]\n"
-#: gschem/src/x_window.c:858
+#: gschem/src/x_window.c:856
msgid "Error while trying to save"
msgstr "خطا عÙ?د Ù?ØاÙ?Ù?Ø© اÙ?ØÙ?ظ"
-#: gschem/src/x_window.c:867
+#: gschem/src/x_window.c:865
#, c-format
msgid "Saved as [%s]\n"
msgstr "ØÙ?Ù?ظ Ù?Ù? [â??%sâ?¬]\n"
-#: gschem/src/x_window.c:869
+#: gschem/src/x_window.c:867
#, c-format
msgid "Saved [%s]\n"
msgstr "â??ØÙ?Ù?ظ [â??%sâ?¬]\n"
-#: gschem/src/x_window.c:871
+#: gschem/src/x_window.c:869
msgid "Saved"
msgstr "Ù?ØÙ?Ù?ظ"
-#: gschem/src/x_window.c:945
+#: gschem/src/x_window.c:943
#, c-format
msgid "Discarding page [%s]\n"
msgstr "Ø¥Ù?Ù?اÙ? اÙ?صÙ?ØØ© [â??%sâ?¬]\n"
-#: gschem/src/x_window.c:945
+#: gschem/src/x_window.c:943
#, c-format
msgid "Closing [%s]\n"
msgstr "غÙ?Ù? [â??%sâ?¬]\n"
@@ -2083,7 +2077,7 @@ msgstr "اØÙ?ظ _Ù?â??..."
msgid "Save All"
msgstr "اØÙ?ظ اÙ?Ù?Ù?"
-#: gschem/lib/system-gschemrc.scm:1386 gschem/lib/system-gschemrc.scm:1477
+#: gschem/lib/system-gschemrc.scm:1386 gschem/lib/system-gschemrc.scm:1478
msgid "_Revert"
msgstr "ت_راجع"
@@ -2095,7 +2089,7 @@ msgstr "ا_طبع..."
msgid "Write _image..."
msgstr "Ø£Ù?تب _صÙ?رة..."
-#: gschem/lib/system-gschemrc.scm:1393 gschem/lib/system-gschemrc.scm:1478
+#: gschem/lib/system-gschemrc.scm:1393 gschem/lib/system-gschemrc.scm:1479
msgid "_Close"
msgstr "Ø£_غÙ?Ù?"
@@ -2127,391 +2121,435 @@ msgstr "Ø£_Ù?صÙ?"
msgid "_Delete"
msgstr "ا_ØØ°Ù?"
-#: gschem/lib/system-gschemrc.scm:1412
+#: gschem/lib/system-gschemrc.scm:1409
+#, fuzzy
+msgid "Select All"
+msgstr "اÙ?تÙ?"
+
+#: gschem/lib/system-gschemrc.scm:1410
+#, fuzzy
+msgid "Deselect"
+msgstr "اÙ?تÙ?"
+
+#: gschem/lib/system-gschemrc.scm:1414
msgid "Rotate 90 Mode"
msgstr "Ù?ضع اÙ?استدارة 90"
-#: gschem/lib/system-gschemrc.scm:1415
+#: gschem/lib/system-gschemrc.scm:1417
msgid "Edit..."
msgstr "ØرÙ?ر..."
-#: gschem/lib/system-gschemrc.scm:1416
+#: gschem/lib/system-gschemrc.scm:1418
msgid "Edit Text..."
msgstr "ØرÙ?ر اÙ?Ù?ص..."
-#: gschem/lib/system-gschemrc.scm:1417
+#: gschem/lib/system-gschemrc.scm:1419
msgid "Slot..."
msgstr "Ø´Ù?Ù?..."
-#: gschem/lib/system-gschemrc.scm:1418
+#: gschem/lib/system-gschemrc.scm:1420
msgid "Color..."
msgstr "Ù?Ù?Ù?..."
-#: gschem/lib/system-gschemrc.scm:1419
+#: gschem/lib/system-gschemrc.scm:1421
msgid "Line Width & Type..."
msgstr "عرض Ù? Ù?Ù?ع اÙ?خط..."
-#: gschem/lib/system-gschemrc.scm:1420
+#: gschem/lib/system-gschemrc.scm:1422
msgid "Fill Type..."
msgstr "Ù?Ù?ع اÙ?Ù?Ù?Ø¡..."
-#: gschem/lib/system-gschemrc.scm:1421
+#: gschem/lib/system-gschemrc.scm:1423
msgid "Symbol Translate..."
msgstr "سØب اÙ?رÙ?ز..."
-#: gschem/lib/system-gschemrc.scm:1425
+#: gschem/lib/system-gschemrc.scm:1427
msgid "Invoke Macro"
msgstr "استدع Ù?اÙ?رÙ?"
-#: gschem/lib/system-gschemrc.scm:1426
+#: gschem/lib/system-gschemrc.scm:1428
msgid "Embed Component/Picture"
msgstr "ضÙ?Ù?Ù? اÙ?Ù?Ù?Ù?Ù?/اÙ?صÙ?رة"
-#: gschem/lib/system-gschemrc.scm:1427
+#: gschem/lib/system-gschemrc.scm:1429
msgid "Unembed Component/Picture"
msgstr "Ù?ا تضÙ?Ù?Ù? اÙ?Ù?Ù?Ù?Ù?/اÙ?صÙ?رة"
-#: gschem/lib/system-gschemrc.scm:1428
+#: gschem/lib/system-gschemrc.scm:1430
msgid "Update Component"
msgstr "ØدÙ?Ø« اÙ?Ù?Ù?Ù?Ù?"
-#: gschem/lib/system-gschemrc.scm:1429
+#: gschem/lib/system-gschemrc.scm:1431
msgid "Show/Hide Inv Text"
msgstr "أظÙ?ر/أخÙ? اÙ?Ù?ص اÙ?Ø®Ù?Ù?"
-#: gschem/lib/system-gschemrc.scm:1430
-msgid "Make Inv Text Vis"
-msgstr "إجعÙ? اÙ?Ù?ص اÙ?Ø®Ù?Ù? ظاÙ?را"
-
-#: gschem/lib/system-gschemrc.scm:1436
+#: gschem/lib/system-gschemrc.scm:1437
msgid "Copy into 1"
msgstr "اÙ?سخ Ø¥Ù?Ù? 1"
-#: gschem/lib/system-gschemrc.scm:1437
+#: gschem/lib/system-gschemrc.scm:1438
msgid "Copy into 2"
msgstr "اÙ?سخ Ø¥Ù?Ù? 2"
-#: gschem/lib/system-gschemrc.scm:1438
+#: gschem/lib/system-gschemrc.scm:1439
msgid "Copy into 3"
msgstr "اÙ?سخ Ø¥Ù?Ù? 3"
-#: gschem/lib/system-gschemrc.scm:1439
+#: gschem/lib/system-gschemrc.scm:1440
msgid "Copy into 4"
msgstr "اÙ?سخ Ø¥Ù?Ù? 4"
-#: gschem/lib/system-gschemrc.scm:1440
+#: gschem/lib/system-gschemrc.scm:1441
msgid "Copy into 5"
msgstr "اÙ?سخ Ø¥Ù?Ù? 5"
-#: gschem/lib/system-gschemrc.scm:1441
+#: gschem/lib/system-gschemrc.scm:1442
msgid "Cut into 1"
msgstr "Ù?ص Ø¥Ù?Ù? 1"
-#: gschem/lib/system-gschemrc.scm:1442
+#: gschem/lib/system-gschemrc.scm:1443
msgid "Cut into 2"
msgstr "Ù?ص Ø¥Ù?Ù? 2"
-#: gschem/lib/system-gschemrc.scm:1443
+#: gschem/lib/system-gschemrc.scm:1444
msgid "Cut into 3"
msgstr "Ù?ص Ø¥Ù?Ù? 3"
-#: gschem/lib/system-gschemrc.scm:1444
+#: gschem/lib/system-gschemrc.scm:1445
msgid "Cut into 4"
msgstr "Ù?ص Ø¥Ù?Ù? 4"
-#: gschem/lib/system-gschemrc.scm:1445
+#: gschem/lib/system-gschemrc.scm:1446
msgid "Cut into 5"
msgstr "Ù?ص Ø¥Ù?Ù? 5"
-#: gschem/lib/system-gschemrc.scm:1446
+#: gschem/lib/system-gschemrc.scm:1447
msgid "Paste from 1"
msgstr "Ø£Ù?صÙ? Ù?Ù? 1"
-#: gschem/lib/system-gschemrc.scm:1447
+#: gschem/lib/system-gschemrc.scm:1448
msgid "Paste from 2"
msgstr "Ø£Ù?صÙ? Ù?Ù? 2"
-#: gschem/lib/system-gschemrc.scm:1448
+#: gschem/lib/system-gschemrc.scm:1449
msgid "Paste from 3"
msgstr "Ø£Ù?صÙ? Ù?Ù? 3"
-#: gschem/lib/system-gschemrc.scm:1449
+#: gschem/lib/system-gschemrc.scm:1450
msgid "Paste from 4"
msgstr "Ø£Ù?صÙ? Ù?Ù? 4"
-#: gschem/lib/system-gschemrc.scm:1450
+#: gschem/lib/system-gschemrc.scm:1451
msgid "Paste from 5"
msgstr "Ø£Ù?صÙ? Ù?Ù? 5"
-#: gschem/lib/system-gschemrc.scm:1456
+#: gschem/lib/system-gschemrc.scm:1457
msgid "_Redraw"
msgstr "Ø£_عد اÙ?رسÙ?"
-#: gschem/lib/system-gschemrc.scm:1457
+#: gschem/lib/system-gschemrc.scm:1458
msgid "_Pan"
msgstr "ا_Ù?تÙ?Ù?"
-#: gschem/lib/system-gschemrc.scm:1458
+#: gschem/lib/system-gschemrc.scm:1459
msgid "Zoom _Box"
msgstr "Ù?رÙ?ب اÙ?Ù?_ربع"
-#: gschem/lib/system-gschemrc.scm:1459
+#: gschem/lib/system-gschemrc.scm:1460
msgid "Zoom _Extents"
msgstr "Ù?رÙ?ب Ù?ع Ø´Ù?Ù? اÙ?ا_Ù?تدادات"
-#: gschem/lib/system-gschemrc.scm:1460
+#: gschem/lib/system-gschemrc.scm:1461
msgid "Zoom _In"
msgstr "_Ù?رÙ?ب"
-#: gschem/lib/system-gschemrc.scm:1461
+#: gschem/lib/system-gschemrc.scm:1462
msgid "Zoom _Out"
msgstr "_بعÙ?د"
-#: gschem/lib/system-gschemrc.scm:1462
+#: gschem/lib/system-gschemrc.scm:1463
msgid "Zoom _Full"
msgstr "بعÙ?د Ù?Ù?_Øد اÙ?Ø£Ù?صÙ?"
-#: gschem/lib/system-gschemrc.scm:1464
+#: gschem/lib/system-gschemrc.scm:1465
msgid "_Dark color scheme"
msgstr "Ù?خطط Ø£Ù?Ù?اÙ? _داÙ?Ù?Ø©"
-#: gschem/lib/system-gschemrc.scm:1465
+#: gschem/lib/system-gschemrc.scm:1466
msgid "_Light color scheme"
msgstr "Ù?خطط Ø£Ù?Ù?اÙ? _Ù?اتØØ©"
-#: gschem/lib/system-gschemrc.scm:1466
+#: gschem/lib/system-gschemrc.scm:1467
#, fuzzy
msgid "B_W color scheme"
msgstr "Ù?خطط Ø£Ù?Ù?اÙ? _داÙ?Ù?Ø©"
-#: gschem/lib/system-gschemrc.scm:1473
+#: gschem/lib/system-gschemrc.scm:1474
msgid "_Manager..."
msgstr "Ù?_دÙ?ر..."
-#: gschem/lib/system-gschemrc.scm:1474
+#: gschem/lib/system-gschemrc.scm:1475
msgid "_Previous"
msgstr "اÙ?_سÙ?ابÙ?Ø©"
-#: gschem/lib/system-gschemrc.scm:1475
+#: gschem/lib/system-gschemrc.scm:1476
msgid "_Next"
msgstr "اÙ?_تÙ?اÙ?Ù?Ø©"
-#: gschem/lib/system-gschemrc.scm:1476
+#: gschem/lib/system-gschemrc.scm:1477
msgid "Ne_w"
msgstr "_جدÙ?دة"
-#: gschem/lib/system-gschemrc.scm:1480
+#: gschem/lib/system-gschemrc.scm:1481
msgid "_Discard"
msgstr "Ø£_Ù?Ù?Ù?"
-#: gschem/lib/system-gschemrc.scm:1486
+#: gschem/lib/system-gschemrc.scm:1487
msgid "_Component..."
msgstr "Ù?_Ù?Ù?Ù?..."
-#: gschem/lib/system-gschemrc.scm:1487
+#: gschem/lib/system-gschemrc.scm:1488
msgid "_Net"
msgstr "_شبÙ?Ø©"
-#: gschem/lib/system-gschemrc.scm:1488
+#: gschem/lib/system-gschemrc.scm:1489
msgid "B_us"
msgstr "Ù?ا_Ù?Ù?"
-#: gschem/lib/system-gschemrc.scm:1489
+#: gschem/lib/system-gschemrc.scm:1490
msgid "_Attribute..."
msgstr "_سÙ?Ø©..."
-#: gschem/lib/system-gschemrc.scm:1490
+#: gschem/lib/system-gschemrc.scm:1491
msgid "_Text..."
msgstr "_Ù?ص..."
-#: gschem/lib/system-gschemrc.scm:1492
+#: gschem/lib/system-gschemrc.scm:1493
msgid "_Line"
msgstr "_خط"
-#: gschem/lib/system-gschemrc.scm:1493
+#: gschem/lib/system-gschemrc.scm:1494
msgid "_Box"
msgstr "_إطار"
-#: gschem/lib/system-gschemrc.scm:1494
+#: gschem/lib/system-gschemrc.scm:1495
msgid "C_ircle"
msgstr "_دائرة"
-#: gschem/lib/system-gschemrc.scm:1495
+#: gschem/lib/system-gschemrc.scm:1496
msgid "A_rc"
msgstr "Ù?_Ù?س"
-#: gschem/lib/system-gschemrc.scm:1496
+#: gschem/lib/system-gschemrc.scm:1497
msgid "_Pin"
msgstr "د_بÙ?س"
-#: gschem/lib/system-gschemrc.scm:1497
+#: gschem/lib/system-gschemrc.scm:1498
msgid "Pictu_re..."
msgstr "_صÙ?رة..."
-#: gschem/lib/system-gschemrc.scm:1503
+#: gschem/lib/system-gschemrc.scm:1504
msgid "_Down Schematic"
msgstr "ا_Ù?زÙ? Ø¥Ù?Ù? اÙ?Ù?خطÙ?Ø·"
-#: gschem/lib/system-gschemrc.scm:1504
+#: gschem/lib/system-gschemrc.scm:1505
msgid "Down _Symbol"
msgstr "اÙ?زÙ? Ø¥Ù?Ù? اÙ?_رÙ?ز"
-#: gschem/lib/system-gschemrc.scm:1505
+#: gschem/lib/system-gschemrc.scm:1506
msgid "_Up"
msgstr "ا_صعد"
-#: gschem/lib/system-gschemrc.scm:1506
+#: gschem/lib/system-gschemrc.scm:1507
msgid "D_ocumentation..."
msgstr "ت_Ù?Ø«Ù?Ù?"
-#: gschem/lib/system-gschemrc.scm:1512
+#: gschem/lib/system-gschemrc.scm:1513
msgid "_Attach"
msgstr "Ø£_رÙ?Ù?"
-#: gschem/lib/system-gschemrc.scm:1513
+#: gschem/lib/system-gschemrc.scm:1514
msgid "_Detach"
msgstr "ا_Ù?صÙ?"
-#: gschem/lib/system-gschemrc.scm:1514
+#: gschem/lib/system-gschemrc.scm:1515
msgid "Show _Value"
msgstr "أظÙ?ر اÙ?_Ù?Ù?Ù?Ø©"
-#: gschem/lib/system-gschemrc.scm:1515
+#: gschem/lib/system-gschemrc.scm:1516
msgid "Show _Name"
msgstr "أظÙ?ر اÙ?_اسÙ?"
-#: gschem/lib/system-gschemrc.scm:1516
+#: gschem/lib/system-gschemrc.scm:1517
msgid "Show _Both"
msgstr "أظÙ?ر اÙ?Ø¥_Ø«Ù?Ù?Ù?"
-#: gschem/lib/system-gschemrc.scm:1517
+#: gschem/lib/system-gschemrc.scm:1518
msgid "_Toggle Visibility"
msgstr "_بدÙ? اÙ?رؤÙ?Ø©"
-#: gschem/lib/system-gschemrc.scm:1519
+#: gschem/lib/system-gschemrc.scm:1520
msgid "_Find Specific Text..."
msgstr "اب_ØØ« عÙ? Ù?ص Ù?عÙ?Ù?..."
-#: gschem/lib/system-gschemrc.scm:1520
+#: gschem/lib/system-gschemrc.scm:1521
msgid "_Hide Specific Text..."
msgstr "Ø£_Ø®Ù? Ù?صا Ù?عÙ?Ù?ا..."
-#: gschem/lib/system-gschemrc.scm:1521
+#: gschem/lib/system-gschemrc.scm:1522
msgid "_Show Specific Text..."
msgstr "Ø£_ظÙ?ر Ù?صا Ù?عÙ?Ù?ا..."
-#: gschem/lib/system-gschemrc.scm:1522
+#: gschem/lib/system-gschemrc.scm:1523
msgid "A_utonumber Text..."
msgstr "_Ù?ص اÙ?ترÙ?Ù?Ù? اÙ?Ø¢Ù?Ù?..."
-#: gschem/lib/system-gschemrc.scm:1528
+#: gschem/lib/system-gschemrc.scm:1529
msgid "_Text Size..."
msgstr "ØجÙ? اÙ?_Ù?ص..."
-#: gschem/lib/system-gschemrc.scm:1529
+#: gschem/lib/system-gschemrc.scm:1530
msgid "Cycle _grid styles"
msgstr "دÙ?Ù?ر Ø£Ù?Ù?اط اÙ?_شبÙ?Ù?Ø©"
-#: gschem/lib/system-gschemrc.scm:1530
+#: gschem/lib/system-gschemrc.scm:1531
msgid "Toggle _Snap On/Off"
msgstr "شغÙ?/Ø£Ù?Ù?Ù? اÙ?_جذب"
-#: gschem/lib/system-gschemrc.scm:1531
+#: gschem/lib/system-gschemrc.scm:1532
msgid "Snap Grid S_pacing..."
msgstr "ت_باعد شبÙ?Ù?Ø© اÙ?جذب..."
-#: gschem/lib/system-gschemrc.scm:1532
+#: gschem/lib/system-gschemrc.scm:1533
msgid "Scale _up Grid Spacing"
msgstr "_Ù?بÙ?ر تباعد اÙ?شبÙ?Ù?Ø©"
-#: gschem/lib/system-gschemrc.scm:1534
+#: gschem/lib/system-gschemrc.scm:1535
msgid "Scale _down Grid Spacing"
msgstr "_صغÙ?ر تباعد اÙ?شبÙ?Ù?Ø©"
-#: gschem/lib/system-gschemrc.scm:1536
+#: gschem/lib/system-gschemrc.scm:1537
msgid "Toggle _Outline/Box"
msgstr "بدÙ?Ù? اÙ?_Øد اÙ?خارجÙ?/اÙ?إطار"
-#: gschem/lib/system-gschemrc.scm:1538
+#: gschem/lib/system-gschemrc.scm:1539
msgid "Toggle Net _Rubberband"
msgstr "بدÙ?Ù? اÙ?شرÙ?Ø· اÙ?Ù?_طاطÙ? Ù?Ù?شبÙ?Ø©"
-#: gschem/lib/system-gschemrc.scm:1539
+#: gschem/lib/system-gschemrc.scm:1540
msgid "Toggle _Magnetic Net"
msgstr "Ù?ضع اÙ?شبÙ?Ø© اÙ?Ù?_غÙ?اطÙ?سÙ?Ø©"
-#: gschem/lib/system-gschemrc.scm:1540
+#: gschem/lib/system-gschemrc.scm:1541
msgid "Show _Log Window..."
msgstr "أظÙ?ر Ù?اÙ?ذة اÙ?_سجÙ?..."
-#: gschem/lib/system-gschemrc.scm:1542
+#: gschem/lib/system-gschemrc.scm:1543
msgid "Show _Coord Window..."
msgstr "أظÙ?ر Ù?اÙ?ذة اÙ?Ù?_عÙ?Ù?..."
-#: gschem/lib/system-gschemrc.scm:1558
+#: gschem/lib/system-gschemrc.scm:1559
msgid "gEDA Docu_mentation..."
msgstr "تÙ?_Ø«Ù?Ù? gEDA"
-#: gschem/lib/system-gschemrc.scm:1559
+#: gschem/lib/system-gschemrc.scm:1560
msgid "gschem _FAQ..."
msgstr "اÙ?Ø£_سئÙ?Ø© اÙ?Ø£Ù?ثر Ø´Ù?Ù?عا Ù?Ù? gschem"
-#: gschem/lib/system-gschemrc.scm:1560
+#: gschem/lib/system-gschemrc.scm:1561
msgid "gEDA _Wiki..."
msgstr "_Ù?Ù?Ù?Ù? gEDA..."
-#: gschem/lib/system-gschemrc.scm:1561
+#: gschem/lib/system-gschemrc.scm:1562
msgid "Component D_ocumentation..."
msgstr "تÙ?Ø«Ù?Ù? اÙ?Ù?_Ù?Ù?Ù?ات"
-#: gschem/lib/system-gschemrc.scm:1563
+#: gschem/lib/system-gschemrc.scm:1564
msgid "_Hotkeys..."
msgstr "Ù?Ù?اتÙ?Ø _ساخÙ?Ø©"
-#: gschem/lib/system-gschemrc.scm:1564
+#: gschem/lib/system-gschemrc.scm:1565
msgid "_About..."
msgstr "_عÙ?..."
-#: gschem/lib/system-gschemrc.scm:1570
+#: gschem/lib/system-gschemrc.scm:1571
msgid "_File"
msgstr "_Ù?Ù?Ù?"
-#: gschem/lib/system-gschemrc.scm:1571
+#: gschem/lib/system-gschemrc.scm:1572
msgid "_Edit"
msgstr "_تØرÙ?ر"
-#: gschem/lib/system-gschemrc.scm:1572
+#: gschem/lib/system-gschemrc.scm:1573
msgid "_Buffer"
msgstr "Ù?_خزÙ?"
-#: gschem/lib/system-gschemrc.scm:1573
+#: gschem/lib/system-gschemrc.scm:1574
msgid "_View"
msgstr "_عرض"
-#: gschem/lib/system-gschemrc.scm:1574
+#: gschem/lib/system-gschemrc.scm:1575
msgid "_Page"
msgstr "_صÙ?ØØ©"
-#: gschem/lib/system-gschemrc.scm:1575
+#: gschem/lib/system-gschemrc.scm:1576
msgid "_Add"
msgstr "_أضÙ?"
-#: gschem/lib/system-gschemrc.scm:1576
+#: gschem/lib/system-gschemrc.scm:1577
msgid "Hie_rarchy"
msgstr "تسÙ?سÙ?â??_Ù?رÙ?Ù?"
-#: gschem/lib/system-gschemrc.scm:1577
+#: gschem/lib/system-gschemrc.scm:1578
msgid "A_ttributes"
msgstr "_سÙ?ات"
-#: gschem/lib/system-gschemrc.scm:1578
+#: gschem/lib/system-gschemrc.scm:1579
msgid "_Options"
msgstr "_Ø®Ù?ارات"
-#: gschem/lib/system-gschemrc.scm:1579
+#: gschem/lib/system-gschemrc.scm:1580
msgid "_Help"
msgstr "Ù?ساع_دة"
+#~ msgid "Scheme directory NOT set!\n"
+#~ msgstr "دÙ?Ù?Ù? اÙ?Ù?خطط غÙ?ر Ù?عÙ?Ù?!\n"
+
+#~ msgid "MakeVisible"
+#~ msgstr "أظÙ?ر"
+
+#~ msgid ""
+#~ "Usage: %s [OPTIONS] schematic_filename1 ... schematic_filenameN\n"
+#~ " -q Quiet mode\n"
+#~ " -v Verbose mode on\n"
+#~ " -r filename Rc filename\n"
+#~ " -s filename Script (guile) filename\n"
+#~ " -o filename Output filename (for printing)\n"
+#~ " -p Automatically place the window\n"
+#~ " -t Print stroke information\n"
+#~ " -h Help; this message\n"
+#~ "\n"
+#~ msgstr ""
+#~ "Usage: %s [OPTIONS] schematic_filename1 ... schematic_filenameN\n"
+#~ " -q Quiet mode\n"
+#~ " -v Verbose mode on\n"
+#~ " -r filename Rc filename\n"
+#~ " -s filename Script (guile) filename\n"
+#~ " -o filename Output filename (for printing)\n"
+#~ " -p Automatically place the window\n"
+#~ " -t Print stroke information\n"
+#~ " -h Help; this message\n"
+#~ "\n"
+
+#~ msgid "Couldn't open file %s\n"
+#~ msgstr "تعذر Ù?ØªØ Ø§Ù?Ù?Ù?Ù? %s\n"
+
+#~ msgid "Clear"
+#~ msgstr "اÙ?سØ"
+
+#~ msgid "Make Inv Text Vis"
+#~ msgstr "إجعÙ? اÙ?Ù?ص اÙ?Ø®Ù?Ù? ظاÙ?را"
+
#~ msgid "Update Cues"
#~ msgstr "ØدÙ?Ø« اÙ?إشارات"
diff --git a/gschem/po/bg.po b/gschem/po/bg.po
index 1e19020..8a2ce11 100644
--- a/gschem/po/bg.po
+++ b/gschem/po/bg.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2010-11-07 13:37+0000\n"
+"POT-Creation-Date: 2011-01-16 00:11-0500\n"
"PO-Revision-Date: 2010-02-11 03:36+0000\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -22,17 +22,17 @@ msgstr ""
msgid "Zoom too small! Cannot zoom further.\n"
msgstr ""
-#: gschem/src/g_funcs.c:339 gschem/src/i_callbacks.c:68
+#: gschem/src/g_funcs.c:347 gschem/src/i_callbacks.c:68
#, c-format
msgid "Could not fork\n"
msgstr ""
-#: gschem/src/g_funcs.c:355 gschem/src/i_callbacks.c:78
+#: gschem/src/g_funcs.c:363 gschem/src/i_callbacks.c:78
#, c-format
msgid "Could not invoke %s\n"
msgstr ""
-#: gschem/src/g_funcs.c:361 gschem/src/i_callbacks.c:82
+#: gschem/src/g_funcs.c:369 gschem/src/i_callbacks.c:82
msgid "Documentation commands not supported under MinGW.\n"
msgstr ""
@@ -121,39 +121,39 @@ msgstr ""
msgid "Invalid number of steps [%d] scrollpan-steps\n"
msgstr ""
-#: gschem/src/gschem.c:184
+#: gschem/src/gschem.c:188
#, c-format
msgid "gEDA/gschem version %s%s.%s\n"
msgstr ""
-#: gschem/src/gschem.c:187
+#: gschem/src/gschem.c:191
msgid ""
"gEDA/gschem comes with ABSOLUTELY NO WARRANTY; see COPYING for more "
"details.\n"
msgstr ""
-#: gschem/src/gschem.c:189
+#: gschem/src/gschem.c:193
msgid ""
"This is free software, and you are welcome to redistribute it under certain\n"
msgstr ""
-#: gschem/src/gschem.c:191
+#: gschem/src/gschem.c:195
msgid ""
"conditions; please see the COPYING file for more details.\n"
"\n"
msgstr ""
-#: gschem/src/gschem.c:194
+#: gschem/src/gschem.c:198
#, c-format
msgid "This is the MINGW32 port.\n"
msgstr ""
-#: gschem/src/gschem.c:198
+#: gschem/src/gschem.c:202
#, c-format
msgid "Current locale settings: %s\n"
msgstr ""
-#: gschem/src/gschem.c:213
+#: gschem/src/gschem.c:218
msgid ""
"You must set the GEDADATA environment variable!\n"
"\n"
@@ -161,31 +161,21 @@ msgid ""
"environment variable to point to the correct location.\n"
msgstr ""
-#: gschem/src/gschem.c:248
+#: gschem/src/gschem.c:256
#, c-format
msgid "Couldn't find init scm file [%s]\n"
msgstr ""
-#: gschem/src/gschem.c:252
+#: gschem/src/gschem.c:260
#, c-format
msgid "Read init scm file [%s]\n"
msgstr ""
-#: gschem/src/gschem.c:256
+#: gschem/src/gschem.c:264
#, c-format
msgid "Failed to read init scm file [%s]\n"
msgstr ""
-#: gschem/src/gschem.c:317
-#, c-format
-msgid "Scheme directory NOT set!\n"
-msgstr ""
-
-#: gschem/src/gschem.c:324 gschem/src/x_script.c:66
-#, c-format
-msgid "Executing guile script [%s]\n"
-msgstr ""
-
#: gschem/src/gschem_cairo.c:310
#, c-format
msgid "Unknown end for line (%d)\n"
@@ -209,11 +199,11 @@ msgstr ""
msgid "Text Mode"
msgstr ""
-#: gschem/src/i_basic.c:84 gschem/lib/system-gschemrc.scm:1409
+#: gschem/src/i_basic.c:84 gschem/lib/system-gschemrc.scm:1411
msgid "Copy Mode"
msgstr "Ð?опиÑ?ен Режим"
-#: gschem/src/i_basic.c:87 gschem/lib/system-gschemrc.scm:1411
+#: gschem/src/i_basic.c:87 gschem/lib/system-gschemrc.scm:1413
msgid "Move Mode"
msgstr "Режим Ð?еÑ?Ñ?ене"
@@ -221,7 +211,7 @@ msgstr "Режим Ð?еÑ?Ñ?ене"
msgid "Rotate Mode"
msgstr ""
-#: gschem/src/i_basic.c:91 gschem/lib/system-gschemrc.scm:1413
+#: gschem/src/i_basic.c:91 gschem/lib/system-gschemrc.scm:1415
msgid "Mirror Mode"
msgstr "Ð?гледален Режим"
@@ -274,22 +264,22 @@ msgstr ""
msgid "Pin Mode"
msgstr ""
-#: gschem/src/i_basic.c:135 gschem/src/i_callbacks.c:544
-#: gschem/src/i_callbacks.c:568
+#: gschem/src/i_basic.c:135 gschem/src/i_callbacks.c:576
+#: gschem/src/i_callbacks.c:600
msgid "Copy"
msgstr ""
-#: gschem/src/i_basic.c:137 gschem/src/i_callbacks.c:634
-#: gschem/src/i_callbacks.c:658
+#: gschem/src/i_basic.c:137 gschem/src/i_callbacks.c:666
+#: gschem/src/i_callbacks.c:690
msgid "Move"
msgstr ""
-#: gschem/src/i_basic.c:139 gschem/src/i_callbacks.c:589
-#: gschem/src/i_callbacks.c:613
+#: gschem/src/i_basic.c:139 gschem/src/i_callbacks.c:621
+#: gschem/src/i_callbacks.c:645
msgid "Multiple Copy"
msgstr ""
-#: gschem/src/i_basic.c:142 gschem/lib/system-gschemrc.scm:1410
+#: gschem/src/i_basic.c:142 gschem/lib/system-gschemrc.scm:1412
msgid "Multiple Copy Mode"
msgstr "Ð?ногокопиÑ?ен Режим"
@@ -309,7 +299,7 @@ msgstr ""
msgid "Action"
msgstr ""
-#: gschem/src/i_basic.c:260 gschem/src/x_dialog.c:2312
+#: gschem/src/i_basic.c:260 gschem/src/x_dialog.c:2316
#: gschem/src/x_window.c:491
msgid "Stroke"
msgstr ""
@@ -340,7 +330,7 @@ msgstr ""
msgid "Documentation for [%s,%s,%s,%s]\n"
msgstr ""
-#: gschem/src/i_callbacks.c:123 gschem/src/i_callbacks.c:1699
+#: gschem/src/i_callbacks.c:123 gschem/src/i_callbacks.c:1706
#, c-format
msgid "New page created [%s]\n"
msgstr ""
@@ -362,327 +352,323 @@ msgstr ""
msgid "Closing Window\n"
msgstr ""
-#: gschem/src/i_callbacks.c:549 gschem/src/i_callbacks.c:594
-#: gschem/src/i_callbacks.c:639
+#: gschem/src/i_callbacks.c:581 gschem/src/i_callbacks.c:626
+#: gschem/src/i_callbacks.c:671
msgid "Select objs first"
msgstr ""
-#: gschem/src/i_callbacks.c:678 gschem/src/x_multiattrib.c:1491
+#: gschem/src/i_callbacks.c:710 gschem/src/x_multiattrib.c:1503
msgid "Delete"
msgstr "Ð?зÑ?Ñ?ий"
-#: gschem/src/i_callbacks.c:703
+#: gschem/src/i_callbacks.c:735
msgid "Edit"
msgstr "РедакÑ?иÑ?ай"
-#: gschem/src/i_callbacks.c:718
+#: gschem/src/i_callbacks.c:750
msgid "Edit pin type"
msgstr ""
-#: gschem/src/i_callbacks.c:737
+#: gschem/src/i_callbacks.c:769
msgid "Edit Text"
msgstr ""
-#: gschem/src/i_callbacks.c:760
+#: gschem/src/i_callbacks.c:792
msgid "Slot"
msgstr ""
-#: gschem/src/i_callbacks.c:777
+#: gschem/src/i_callbacks.c:809
msgid "Color"
msgstr ""
-#: gschem/src/i_callbacks.c:814 gschem/src/i_callbacks.c:859
+#: gschem/src/i_callbacks.c:846 gschem/src/i_callbacks.c:891
msgid "Rotate"
msgstr ""
-#: gschem/src/i_callbacks.c:882 gschem/src/i_callbacks.c:907
+#: gschem/src/i_callbacks.c:913 gschem/src/i_callbacks.c:938
msgid "Mirror"
msgstr ""
-#: gschem/src/i_callbacks.c:928 gschem/src/x_dialog.c:2315
-#: gschem/lib/system-gschemrc.scm:1422
+#: gschem/src/i_callbacks.c:959 gschem/src/x_dialog.c:2319
+#: gschem/lib/system-gschemrc.scm:1424
msgid "Lock"
msgstr "Ð?аклÑ?Ñ?ване"
-#: gschem/src/i_callbacks.c:946 gschem/lib/system-gschemrc.scm:1423
+#: gschem/src/i_callbacks.c:977 gschem/lib/system-gschemrc.scm:1425
msgid "Unlock"
msgstr "Ð?Ñ?клÑ?Ñ?ване"
-#: gschem/src/i_callbacks.c:964 gschem/src/x_dialog.c:1734
+#: gschem/src/i_callbacks.c:995 gschem/src/x_dialog.c:1737
msgid "Translate"
msgstr ""
-#: gschem/src/i_callbacks.c:967
+#: gschem/src/i_callbacks.c:998
msgid "WARNING: Do not translate with snap off!\n"
msgstr ""
-#: gschem/src/i_callbacks.c:968
+#: gschem/src/i_callbacks.c:999
msgid "WARNING: Turning snap on and continuing with translate.\n"
msgstr ""
-#: gschem/src/i_callbacks.c:975
+#: gschem/src/i_callbacks.c:1006
msgid "WARNING: Snap grid size is not equal to 100!\n"
msgstr ""
-#: gschem/src/i_callbacks.c:977
+#: gschem/src/i_callbacks.c:1008
msgid ""
"WARNING: If you are translating a symbol to the origin, the snap grid size "
"should be set to 100\n"
msgstr ""
-#: gschem/src/i_callbacks.c:1008
+#: gschem/src/i_callbacks.c:1039
msgid "Embed"
msgstr ""
-#: gschem/src/i_callbacks.c:1047
+#: gschem/src/i_callbacks.c:1078
msgid "Unembed"
msgstr ""
-#: gschem/src/i_callbacks.c:1089
+#: gschem/src/i_callbacks.c:1120
msgid "Update"
msgstr ""
-#: gschem/src/i_callbacks.c:1136
+#: gschem/src/i_callbacks.c:1167
msgid "ShowHidden"
msgstr ""
-#: gschem/src/i_callbacks.c:1160
-msgid "MakeVisible"
-msgstr ""
-
-#: gschem/src/i_callbacks.c:1466 gschem/src/i_callbacks.c:1538
+#: gschem/src/i_callbacks.c:1473 gschem/src/i_callbacks.c:1545
msgid "Pan"
msgstr ""
-#: gschem/src/i_callbacks.c:1743
+#: gschem/src/i_callbacks.c:1750
msgid "Really revert page?"
msgstr ""
-#: gschem/src/i_callbacks.c:1813
+#: gschem/src/i_callbacks.c:1820
msgid "Copy to clipboard"
msgstr ""
-#: gschem/src/i_callbacks.c:1831
+#: gschem/src/i_callbacks.c:1838
msgid "Cut to clipboard"
msgstr ""
-#: gschem/src/i_callbacks.c:1849
+#: gschem/src/i_callbacks.c:1856
msgid "Paste from clipboard"
msgstr ""
-#: gschem/src/i_callbacks.c:1861 gschem/src/i_callbacks.c:2100
-#: gschem/src/i_callbacks.c:2122 gschem/src/i_callbacks.c:2144
-#: gschem/src/i_callbacks.c:2166 gschem/src/i_callbacks.c:2188
+#: gschem/src/i_callbacks.c:1868 gschem/src/i_callbacks.c:2107
+#: gschem/src/i_callbacks.c:2129 gschem/src/i_callbacks.c:2151
+#: gschem/src/i_callbacks.c:2173 gschem/src/i_callbacks.c:2195
msgid "Empty buffer"
msgstr ""
-#: gschem/src/i_callbacks.c:1906
+#: gschem/src/i_callbacks.c:1913
msgid "Copy 1"
msgstr ""
-#: gschem/src/i_callbacks.c:1925
+#: gschem/src/i_callbacks.c:1932
msgid "Copy 2"
msgstr ""
-#: gschem/src/i_callbacks.c:1944
+#: gschem/src/i_callbacks.c:1951
msgid "Copy 3"
msgstr ""
-#: gschem/src/i_callbacks.c:1963
+#: gschem/src/i_callbacks.c:1970
msgid "Copy 4"
msgstr ""
-#: gschem/src/i_callbacks.c:1982
+#: gschem/src/i_callbacks.c:1989
msgid "Copy 5"
msgstr ""
-#: gschem/src/i_callbacks.c:2001
+#: gschem/src/i_callbacks.c:2008
msgid "Cut 1"
msgstr ""
-#: gschem/src/i_callbacks.c:2020
+#: gschem/src/i_callbacks.c:2027
msgid "Cut 2"
msgstr ""
-#: gschem/src/i_callbacks.c:2039
+#: gschem/src/i_callbacks.c:2046
msgid "Cut 3"
msgstr ""
-#: gschem/src/i_callbacks.c:2058
+#: gschem/src/i_callbacks.c:2065
msgid "Cut 4"
msgstr ""
-#: gschem/src/i_callbacks.c:2077
+#: gschem/src/i_callbacks.c:2084
msgid "Cut 5"
msgstr ""
-#: gschem/src/i_callbacks.c:2093
+#: gschem/src/i_callbacks.c:2100
msgid "Paste 1"
msgstr ""
-#: gschem/src/i_callbacks.c:2115
+#: gschem/src/i_callbacks.c:2122
msgid "Paste 2"
msgstr ""
-#: gschem/src/i_callbacks.c:2137
+#: gschem/src/i_callbacks.c:2144
msgid "Paste 3"
msgstr ""
-#: gschem/src/i_callbacks.c:2159
+#: gschem/src/i_callbacks.c:2166
msgid "Paste 4"
msgstr ""
-#: gschem/src/i_callbacks.c:2181
+#: gschem/src/i_callbacks.c:2188
msgid "Paste 5"
msgstr ""
-#: gschem/src/i_callbacks.c:2318 gschem/src/x_window.c:355
+#: gschem/src/i_callbacks.c:2325 gschem/src/x_window.c:355
msgid "Component"
msgstr ""
-#: gschem/src/i_callbacks.c:2354 gschem/src/i_callbacks.c:2373
-#: gschem/src/x_dialog.c:2285
+#: gschem/src/i_callbacks.c:2361 gschem/src/i_callbacks.c:2380
+#: gschem/src/x_dialog.c:2289
msgid "Attribute"
msgstr ""
-#: gschem/src/i_callbacks.c:2395 gschem/src/i_callbacks.c:2422
-#: gschem/src/x_dialog.c:2282
+#: gschem/src/i_callbacks.c:2402 gschem/src/i_callbacks.c:2429
+#: gschem/src/x_dialog.c:2286
msgid "Net"
msgstr ""
-#: gschem/src/i_callbacks.c:2466 gschem/src/i_callbacks.c:2493
-#: gschem/src/x_dialog.c:2300 gschem/src/x_window.c:375
+#: gschem/src/i_callbacks.c:2473 gschem/src/i_callbacks.c:2500
+#: gschem/src/x_dialog.c:2304 gschem/src/x_window.c:375
msgid "Bus"
msgstr ""
-#: gschem/src/i_callbacks.c:2574 gschem/src/i_callbacks.c:2597
+#: gschem/src/i_callbacks.c:2581 gschem/src/i_callbacks.c:2604
msgid "Line"
msgstr ""
-#: gschem/src/i_callbacks.c:2619 gschem/src/i_callbacks.c:2642
+#: gschem/src/i_callbacks.c:2626 gschem/src/i_callbacks.c:2649
msgid "Box"
msgstr ""
-#: gschem/src/i_callbacks.c:2698 gschem/src/i_callbacks.c:2722
+#: gschem/src/i_callbacks.c:2705 gschem/src/i_callbacks.c:2729
msgid "Circle"
msgstr ""
-#: gschem/src/i_callbacks.c:2744 gschem/src/i_callbacks.c:2767
+#: gschem/src/i_callbacks.c:2751 gschem/src/i_callbacks.c:2774
msgid "Arc"
msgstr ""
-#: gschem/src/i_callbacks.c:2789 gschem/src/i_callbacks.c:2812
-#: gschem/src/x_dialog.c:2273
+#: gschem/src/i_callbacks.c:2796 gschem/src/i_callbacks.c:2819
+#: gschem/src/x_dialog.c:2277
msgid "Pin"
msgstr ""
-#: gschem/src/i_callbacks.c:2871
+#: gschem/src/i_callbacks.c:2878
#, c-format
msgid "Searching for source [%s]\n"
msgstr ""
-#: gschem/src/i_callbacks.c:2895
+#: gschem/src/i_callbacks.c:2902
#, c-format
msgid "Cannot find source [%s]\n"
msgstr ""
-#: gschem/src/i_callbacks.c:2964
+#: gschem/src/i_callbacks.c:2965
#, c-format
msgid "Searching for symbol [%s]\n"
msgstr ""
-#: gschem/src/i_callbacks.c:2970
+#: gschem/src/i_callbacks.c:2971
msgid "Symbol is not a real file. Symbol cannot be loaded.\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3001
+#: gschem/src/i_callbacks.c:3002
msgid "Cannot find any schematics above the current one!\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3055
+#: gschem/src/i_callbacks.c:3056
msgid ""
"This command retrieves the component documentation from the web, but there "
"is no component selected"
msgstr ""
-#: gschem/src/i_callbacks.c:3083
+#: gschem/src/i_callbacks.c:3084
msgid "Attach"
msgstr ""
-#: gschem/src/i_callbacks.c:3130
+#: gschem/src/i_callbacks.c:3131
msgid "Detach"
msgstr ""
-#: gschem/src/i_callbacks.c:3165
+#: gschem/src/i_callbacks.c:3166
msgid "ShowN"
msgstr ""
-#: gschem/src/i_callbacks.c:3201
+#: gschem/src/i_callbacks.c:3202
msgid "ShowV"
msgstr ""
-#: gschem/src/i_callbacks.c:3237
+#: gschem/src/i_callbacks.c:3238
msgid "ShowB"
msgstr ""
-#: gschem/src/i_callbacks.c:3274
+#: gschem/src/i_callbacks.c:3275
msgid "VisToggle"
msgstr ""
-#: gschem/src/i_callbacks.c:3304
+#: gschem/src/i_callbacks.c:3305
#, c-format
msgid "Sorry but this is a non-functioning menu option\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3394
+#: gschem/src/i_callbacks.c:3395
msgid "Action feedback mode set to OUTLINE\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3397
+#: gschem/src/i_callbacks.c:3398
msgid "Action feedback mode set to BOUNDINGBOX\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3422
+#: gschem/src/i_callbacks.c:3423
msgid "Grid OFF\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3423
+#: gschem/src/i_callbacks.c:3424
msgid "Dot grid selected\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3424
+#: gschem/src/i_callbacks.c:3425
msgid "Mesh grid selected\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3445
+#: gschem/src/i_callbacks.c:3446
msgid "Snap OFF (CAUTION!)\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3448
+#: gschem/src/i_callbacks.c:3449
msgid "Snap ON\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3451
+#: gschem/src/i_callbacks.c:3452
msgid "Snap back to the grid (CAUTION!)\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3477
+#: gschem/src/i_callbacks.c:3478
msgid "Rubber band OFF \n"
msgstr ""
-#: gschem/src/i_callbacks.c:3480
+#: gschem/src/i_callbacks.c:3481
msgid "Rubber band ON\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3495
+#: gschem/src/i_callbacks.c:3496
msgid "magnetic net mode: ON\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3498
+#: gschem/src/i_callbacks.c:3499
msgid "magnetic net mode: OFF\n"
msgstr ""
-#: gschem/src/o_box.c:153
+#: gschem/src/o_box.c:149
#, c-format
msgid "Unknown type for box (fill)!\n"
msgstr ""
@@ -702,17 +688,17 @@ msgstr ""
msgid "Got an invalid buffer_number [o_buffer_paste_start]\n"
msgstr ""
-#: gschem/src/o_bus.c:118
+#: gschem/src/o_bus.c:117
#, c-format
msgid "Got an invalid which one in o_bus_draw_stretch\n"
msgstr ""
-#: gschem/src/o_circle.c:134
+#: gschem/src/o_circle.c:130
#, c-format
msgid "Unknown type for circle (fill)!\n"
msgstr ""
-#: gschem/src/o_complex.c:243 gschem/src/o_complex.c:247
+#: gschem/src/o_complex.c:237 gschem/src/o_complex.c:241
#, c-format
msgid "Translating schematic [%d %d]\n"
msgstr ""
@@ -730,35 +716,35 @@ msgstr ""
msgid "Object already unlocked\n"
msgstr ""
-#: gschem/src/o_misc.c:413
+#: gschem/src/o_misc.c:409
msgid "Hidden text is now visible\n"
msgstr ""
-#: gschem/src/o_misc.c:415
+#: gschem/src/o_misc.c:411
msgid "Hidden text is now invisible\n"
msgstr ""
-#: gschem/src/o_misc.c:668
+#: gschem/src/o_misc.c:636
#, c-format
msgid "Could not find symbol [%s] in library. Update failed.\n"
msgstr ""
-#: gschem/src/o_misc.c:783
+#: gschem/src/o_misc.c:751
#, c-format
msgid "o_autosave_backups: Can't get the real filename of %s."
msgstr ""
-#: gschem/src/o_misc.c:827
+#: gschem/src/o_misc.c:795
#, c-format
msgid "Could NOT set previous backup file [%s] read-write\n"
msgstr ""
-#: gschem/src/o_misc.c:845
+#: gschem/src/o_misc.c:815
#, c-format
msgid "Could NOT set backup file [%s] readonly\n"
msgstr ""
-#: gschem/src/o_misc.c:850
+#: gschem/src/o_misc.c:820
#, c-format
msgid "Could NOT save backup file [%s]\n"
msgstr ""
@@ -778,36 +764,36 @@ msgstr ""
msgid "Got a non line object in o_move_check_endpoint\n"
msgstr ""
-#: gschem/src/o_net.c:159
+#: gschem/src/o_net.c:158
#, c-format
msgid "Got an invalid which one in o_net_draw_stretch\n"
msgstr ""
-#: gschem/src/o_net.c:538
+#: gschem/src/o_net.c:537
msgid "Warning: Starting net at off grid coordinate\n"
msgstr ""
-#: gschem/src/o_net.c:600
+#: gschem/src/o_net.c:599
msgid "Warning: Ending net at off grid coordinate\n"
msgstr ""
-#: gschem/src/o_net.c:932 gschem/src/o_net.c:969 gschem/src/o_net.c:1040
-#: gschem/src/o_net.c:1076
+#: gschem/src/o_net.c:931 gschem/src/o_net.c:968 gschem/src/o_net.c:1039
+#: gschem/src/o_net.c:1075
#, c-format
msgid "Tried to add more than two bus rippers. Internal gschem error.\n"
msgstr ""
-#: gschem/src/o_net.c:1144
+#: gschem/src/o_net.c:1143
#, c-format
msgid "Bus ripper symbol [%s] was not found in any component library\n"
msgstr ""
-#: gschem/src/o_path.c:352
+#: gschem/src/o_path.c:348
#, c-format
msgid "Unknown type for path (fill)!\n"
msgstr ""
-#: gschem/src/o_picture.c:163 gschem/src/o_picture.c:539
+#: gschem/src/o_picture.c:163 gschem/src/o_picture.c:537
#, c-format
msgid "Failed to load picture: %s"
msgstr ""
@@ -816,7 +802,7 @@ msgstr ""
msgid "Picture"
msgstr ""
-#: gschem/src/o_picture.c:447 gschem/src/x_attribedit.c:141
+#: gschem/src/o_picture.c:445 gschem/src/x_attribedit.c:141
#, c-format
msgid "ERROR: NULL object!\n"
msgstr ""
@@ -837,23 +823,45 @@ msgstr ""
msgid "New slot number out of range\n"
msgstr ""
-#: gschem/src/o_undo.c:304
+#: gschem/src/o_undo.c:303
msgid "Undo/Redo disabled in rc file\n"
msgstr ""
-#: gschem/src/parsecmd.c:47
+#: gschem/src/parsecmd.c:81
#, c-format
msgid ""
-"Usage: %s [OPTIONS] schematic_filename1 ... schematic_filenameN\n"
-" -q Quiet mode\n"
-" -v Verbose mode on\n"
-" -r filename Rc filename\n"
-" -s filename Script (guile) filename\n"
-" -o filename Output filename (for printing)\n"
-" -p Automatically place the window\n"
-" -t Print stroke information\n"
-" -h Help; this message\n"
+"Usage: %s [OPTION ...] [--] [FILE ...]\n"
+"\n"
+"Interactively edit gEDA schematics or symbols. If one or more FILEs\n"
+"are specified, open them for editing; otherwise, create a new, empty\n"
+"schematic.\n"
+"\n"
+"Options:\n"
+" -q, --quiet Quiet mode.\n"
+" -v, --verbose Verbose mode.\n"
+" -r, --config-file=FILE Additional configuration file to load.\n"
+" -L DIR Add DIR to Scheme search path.\n"
+" -c EXPR Scheme expression to run at startup.\n"
+" -s FILE Scheme script to run at startup.\n"
+" -o, --output=FILE Output filename (for printing).\n"
+" -p Automatically place the window.\n"
+" -V, --version Show version information.\n"
+" -h, --help Help; this message.\n"
+" -- Treat all remaining arguments as filenames.\n"
"\n"
+"Report bugs to <geda-bug@xxxxxxxx>\n"
+"gEDA/gaf homepage: <http://gpleda.org>\n"
+msgstr ""
+
+#: gschem/src/parsecmd.c:115
+#, c-format
+msgid ""
+"gEDA %s (g%.7s)\n"
+"Copyright (C) 1998-2011 gEDA developers\n"
+"This is free software, and you are welcome to redistribute it under\n"
+"certain conditions. For details, see the file `COPYING', which is\n"
+"included in the gEDA distribution.\n"
+"There is NO WARRANTY, to the extent permitted by law.\n"
msgstr ""
#: gschem/src/x_attribedit.c:127
@@ -865,56 +873,56 @@ msgstr ""
msgid "Single Attribute Editor"
msgstr ""
-#: gschem/src/x_attribedit.c:358
+#: gschem/src/x_attribedit.c:359
msgid "<b>Edit Attribute</b>"
msgstr ""
-#: gschem/src/x_attribedit.c:360
+#: gschem/src/x_attribedit.c:361
msgid "<b>Add Attribute</b>"
msgstr ""
-#: gschem/src/x_attribedit.c:376 gschem/src/x_multiattrib.c:1916
+#: gschem/src/x_attribedit.c:377 gschem/src/x_multiattrib.c:1927
msgid "Name:"
msgstr ""
-#: gschem/src/x_attribedit.c:393 gschem/src/x_multiattrib.c:1935
+#: gschem/src/x_attribedit.c:394 gschem/src/x_multiattrib.c:1946
msgid "Value:"
msgstr ""
-#: gschem/src/x_attribedit.c:409 gschem/src/x_multiattrib.c:1978
+#: gschem/src/x_attribedit.c:410 gschem/src/x_multiattrib.c:1989
msgid "Visible"
msgstr ""
-#: gschem/src/x_attribedit.c:429
+#: gschem/src/x_attribedit.c:430
msgid "Show Value Only"
msgstr ""
-#: gschem/src/x_attribedit.c:431
+#: gschem/src/x_attribedit.c:432
msgid "Show Name Only"
msgstr ""
-#: gschem/src/x_attribedit.c:433 gschem/src/x_multiattrib.c:1454
+#: gschem/src/x_attribedit.c:434 gschem/src/x_multiattrib.c:1466
msgid "Show Name & Value"
msgstr ""
-#: gschem/src/x_attribedit.c:440
+#: gschem/src/x_attribedit.c:441
msgid "<b>Attach Options</b>"
msgstr ""
-#: gschem/src/x_attribedit.c:455
+#: gschem/src/x_attribedit.c:456
msgid "All"
msgstr ""
-#: gschem/src/x_attribedit.c:463 gschem/src/x_compselect.c:896
-#: gschem/src/x_compselect.c:1010
+#: gschem/src/x_attribedit.c:464 gschem/src/x_compselect.c:904
+#: gschem/src/x_compselect.c:1018
msgid "Components"
msgstr ""
-#: gschem/src/x_attribedit.c:471 gschem/src/x_window.c:365
+#: gschem/src/x_attribedit.c:472 gschem/src/x_window.c:365
msgid "Nets"
msgstr ""
-#: gschem/src/x_attribedit.c:479
+#: gschem/src/x_attribedit.c:480
msgid "Replace existing attributes"
msgstr ""
@@ -930,91 +938,91 @@ msgid ""
"duplicate slot may cause problems: [symbolname=%s, number=%d, slot=%d]\n"
msgstr ""
-#: gschem/src/x_autonumber.c:673
+#: gschem/src/x_autonumber.c:675
msgid "No searchstring given in autonumber text.\n"
msgstr ""
-#: gschem/src/x_autonumber.c:725
+#: gschem/src/x_autonumber.c:727
msgid "No '*' or '?' given at the end of the autonumber text.\n"
msgstr ""
-#: gschem/src/x_autonumber.c:860
+#: gschem/src/x_autonumber.c:862
msgid "Diagonal"
msgstr ""
-#: gschem/src/x_autonumber.c:861
+#: gschem/src/x_autonumber.c:863
msgid "Top to bottom"
msgstr ""
-#: gschem/src/x_autonumber.c:861
+#: gschem/src/x_autonumber.c:863
msgid "Bottom to top"
msgstr ""
-#: gschem/src/x_autonumber.c:862
+#: gschem/src/x_autonumber.c:864
msgid "Left to right"
msgstr ""
-#: gschem/src/x_autonumber.c:862
+#: gschem/src/x_autonumber.c:864
msgid "Right to left"
msgstr ""
-#: gschem/src/x_autonumber.c:863
+#: gschem/src/x_autonumber.c:865
msgid "File order"
msgstr ""
-#: gschem/src/x_autonumber.c:1199
+#: gschem/src/x_autonumber.c:1201
msgid "Autonumber text"
msgstr ""
-#: gschem/src/x_autonumber.c:1223
+#: gschem/src/x_autonumber.c:1225
msgid "<b>Scope</b>"
msgstr ""
-#: gschem/src/x_autonumber.c:1245
+#: gschem/src/x_autonumber.c:1247
msgid "Search for:"
msgstr ""
-#: gschem/src/x_autonumber.c:1259
+#: gschem/src/x_autonumber.c:1261
msgid "Autonumber text in:"
msgstr ""
-#: gschem/src/x_autonumber.c:1266
+#: gschem/src/x_autonumber.c:1268
msgid "Skip numbers found in:"
msgstr ""
-#: gschem/src/x_autonumber.c:1278 gschem/src/x_autonumber.c:1287
+#: gschem/src/x_autonumber.c:1280 gschem/src/x_autonumber.c:1289
msgid "Selected objects"
msgstr ""
-#: gschem/src/x_autonumber.c:1279 gschem/src/x_autonumber.c:1288
+#: gschem/src/x_autonumber.c:1281 gschem/src/x_autonumber.c:1290
msgid "Current page"
msgstr ""
-#: gschem/src/x_autonumber.c:1280 gschem/src/x_autonumber.c:1289
+#: gschem/src/x_autonumber.c:1282 gschem/src/x_autonumber.c:1291
msgid "Whole hierarchy"
msgstr ""
-#: gschem/src/x_autonumber.c:1291
+#: gschem/src/x_autonumber.c:1293
msgid "Overwrite existing numbers"
msgstr ""
-#: gschem/src/x_autonumber.c:1296
+#: gschem/src/x_autonumber.c:1298
msgid "<b>Options</b>"
msgstr ""
-#: gschem/src/x_autonumber.c:1318
+#: gschem/src/x_autonumber.c:1320
msgid "Starting number:"
msgstr ""
-#: gschem/src/x_autonumber.c:1325
+#: gschem/src/x_autonumber.c:1327
msgid "Sort order:"
msgstr ""
-#: gschem/src/x_autonumber.c:1346
+#: gschem/src/x_autonumber.c:1348
msgid "Remove numbers"
msgstr ""
-#: gschem/src/x_autonumber.c:1350
+#: gschem/src/x_autonumber.c:1352
msgid "Automatic slotting"
msgstr ""
@@ -1051,48 +1059,48 @@ msgstr ""
msgid "Tried to get an invalid outline color: %d\n"
msgstr ""
-#: gschem/src/x_compselect.c:1040
+#: gschem/src/x_compselect.c:1048
msgid "Filter:"
msgstr ""
-#: gschem/src/x_compselect.c:1143 gschem/src/x_dialog.c:3663
-#: gschem/src/x_multiattrib.c:1782
+#: gschem/src/x_compselect.c:1151 gschem/src/x_dialog.c:3667
+#: gschem/src/x_multiattrib.c:1793
msgid "Name"
msgstr ""
-#: gschem/src/x_compselect.c:1152 gschem/src/x_multiattrib.c:1806
+#: gschem/src/x_compselect.c:1160 gschem/src/x_multiattrib.c:1817
msgid "Value"
msgstr ""
-#: gschem/src/x_compselect.c:1191
+#: gschem/src/x_compselect.c:1199
msgid "Default behavior - reference component"
msgstr ""
-#: gschem/src/x_compselect.c:1194
+#: gschem/src/x_compselect.c:1202
msgid "Embed component in schematic"
msgstr ""
-#: gschem/src/x_compselect.c:1197
+#: gschem/src/x_compselect.c:1205
msgid "Include component as individual objects"
msgstr ""
-#: gschem/src/x_compselect.c:1354
+#: gschem/src/x_compselect.c:1362
msgid "Select Component..."
msgstr ""
-#: gschem/src/x_compselect.c:1377
+#: gschem/src/x_compselect.c:1385
msgid "In Use"
msgstr ""
-#: gschem/src/x_compselect.c:1381
+#: gschem/src/x_compselect.c:1389
msgid "Libraries"
msgstr ""
-#: gschem/src/x_compselect.c:1390 gschem/src/x_fileselect.c:122
+#: gschem/src/x_compselect.c:1398 gschem/src/x_fileselect.c:122
msgid "Preview"
msgstr ""
-#: gschem/src/x_compselect.c:1418
+#: gschem/src/x_compselect.c:1426
msgid "Attributes"
msgstr ""
@@ -1147,336 +1155,336 @@ msgstr ""
msgid "Edit Text Properties"
msgstr ""
-#: gschem/src/x_dialog.c:471
+#: gschem/src/x_dialog.c:472
msgid "<b>Text Content</b>"
msgstr ""
-#: gschem/src/x_dialog.c:507
+#: gschem/src/x_dialog.c:508
msgid "<b>Text Properties</b>"
msgstr ""
-#: gschem/src/x_dialog.c:522
+#: gschem/src/x_dialog.c:523
msgid "Color:"
msgstr ""
-#: gschem/src/x_dialog.c:529
+#: gschem/src/x_dialog.c:530
msgid "Size:"
msgstr ""
-#: gschem/src/x_dialog.c:538
+#: gschem/src/x_dialog.c:539
msgid "Alignment:"
msgstr ""
-#: gschem/src/x_dialog.c:587
+#: gschem/src/x_dialog.c:588
msgid "Solid"
msgstr ""
-#: gschem/src/x_dialog.c:588
+#: gschem/src/x_dialog.c:589
msgid "Dotted"
msgstr ""
-#: gschem/src/x_dialog.c:589
+#: gschem/src/x_dialog.c:590
msgid "Dashed"
msgstr ""
-#: gschem/src/x_dialog.c:590
+#: gschem/src/x_dialog.c:591
msgid "Center"
msgstr ""
-#: gschem/src/x_dialog.c:591
+#: gschem/src/x_dialog.c:592
msgid "Phantom"
msgstr ""
-#: gschem/src/x_dialog.c:592 gschem/src/x_dialog.c:689
-#: gschem/src/x_dialog.c:698 gschem/src/x_dialog.c:707
-#: gschem/src/x_dialog.c:808 gschem/src/x_dialog.c:810
-#: gschem/src/x_dialog.c:812 gschem/src/x_dialog.c:1038
-#: gschem/src/x_dialog.c:1141 gschem/src/x_dialog.c:1150
-#: gschem/src/x_dialog.c:1159 gschem/src/x_dialog.c:1168
-#: gschem/src/x_dialog.c:1177 gschem/src/x_dialog.c:1290
-#: gschem/src/x_dialog.c:1292 gschem/src/x_dialog.c:1294
-#: gschem/src/x_dialog.c:1296 gschem/src/x_dialog.c:1298
+#: gschem/src/x_dialog.c:593 gschem/src/x_dialog.c:690
+#: gschem/src/x_dialog.c:699 gschem/src/x_dialog.c:708
+#: gschem/src/x_dialog.c:809 gschem/src/x_dialog.c:811
+#: gschem/src/x_dialog.c:813 gschem/src/x_dialog.c:1039
+#: gschem/src/x_dialog.c:1142 gschem/src/x_dialog.c:1151
+#: gschem/src/x_dialog.c:1160 gschem/src/x_dialog.c:1169
+#: gschem/src/x_dialog.c:1178 gschem/src/x_dialog.c:1291
+#: gschem/src/x_dialog.c:1293 gschem/src/x_dialog.c:1295
+#: gschem/src/x_dialog.c:1297 gschem/src/x_dialog.c:1299
msgid "*unchanged*"
msgstr ""
-#: gschem/src/x_dialog.c:916
+#: gschem/src/x_dialog.c:917
msgid "Edit Line Width & Type"
msgstr ""
-#: gschem/src/x_dialog.c:955 gschem/src/x_print.c:307
+#: gschem/src/x_dialog.c:956 gschem/src/x_print.c:307
msgid "Type:"
msgstr ""
-#: gschem/src/x_dialog.c:959
+#: gschem/src/x_dialog.c:960
msgid "Width:"
msgstr ""
-#: gschem/src/x_dialog.c:963
+#: gschem/src/x_dialog.c:964
msgid "Dash Length:"
msgstr ""
-#: gschem/src/x_dialog.c:967
+#: gschem/src/x_dialog.c:968
msgid "Dash Space:"
msgstr ""
-#: gschem/src/x_dialog.c:1034
+#: gschem/src/x_dialog.c:1035
msgid "Hollow"
msgstr ""
-#: gschem/src/x_dialog.c:1035
+#: gschem/src/x_dialog.c:1036
msgid "Filled"
msgstr ""
-#: gschem/src/x_dialog.c:1036
+#: gschem/src/x_dialog.c:1037
msgid "Mesh"
msgstr ""
-#: gschem/src/x_dialog.c:1037
+#: gschem/src/x_dialog.c:1038
msgid "Hatch"
msgstr ""
-#: gschem/src/x_dialog.c:1406
+#: gschem/src/x_dialog.c:1407
msgid "Edit Fill Type"
msgstr ""
-#: gschem/src/x_dialog.c:1444
+#: gschem/src/x_dialog.c:1446
msgid "Fill Type:"
msgstr ""
-#: gschem/src/x_dialog.c:1448
+#: gschem/src/x_dialog.c:1450
msgid "Line Width:"
msgstr ""
-#: gschem/src/x_dialog.c:1452
+#: gschem/src/x_dialog.c:1454
msgid "Angle 1:"
msgstr ""
-#: gschem/src/x_dialog.c:1456
+#: gschem/src/x_dialog.c:1458
msgid "Pitch 1:"
msgstr ""
-#: gschem/src/x_dialog.c:1460
+#: gschem/src/x_dialog.c:1462
msgid "Angle 2:"
msgstr ""
-#: gschem/src/x_dialog.c:1464
+#: gschem/src/x_dialog.c:1466
msgid "Pitch 2:"
msgstr ""
-#: gschem/src/x_dialog.c:1591
+#: gschem/src/x_dialog.c:1593
msgid "Arc Params"
msgstr ""
-#: gschem/src/x_dialog.c:1631
+#: gschem/src/x_dialog.c:1634
msgid "Arc Radius:"
msgstr ""
-#: gschem/src/x_dialog.c:1639
+#: gschem/src/x_dialog.c:1642
msgid "Start Angle:"
msgstr ""
-#: gschem/src/x_dialog.c:1647
+#: gschem/src/x_dialog.c:1650
msgid "Degrees of Sweep:"
msgstr ""
-#: gschem/src/x_dialog.c:1764
+#: gschem/src/x_dialog.c:1768
msgid ""
"Offset to translate?\n"
"(0 for origin)"
msgstr ""
-#: gschem/src/x_dialog.c:1832
+#: gschem/src/x_dialog.c:1836
msgid "Text Size"
msgstr ""
-#: gschem/src/x_dialog.c:1862
+#: gschem/src/x_dialog.c:1866
msgid "Enter new text size:"
msgstr ""
-#: gschem/src/x_dialog.c:1938
+#: gschem/src/x_dialog.c:1942
msgid "Snap Size"
msgstr ""
-#: gschem/src/x_dialog.c:1968
+#: gschem/src/x_dialog.c:1972
msgid "Enter new snap grid spacing:"
msgstr ""
-#: gschem/src/x_dialog.c:2045
+#: gschem/src/x_dialog.c:2049
msgid "Edit slot number"
msgstr ""
-#: gschem/src/x_dialog.c:2076
+#: gschem/src/x_dialog.c:2080
msgid "Edit slot number:"
msgstr ""
-#: gschem/src/x_dialog.c:2117
+#: gschem/src/x_dialog.c:2121
#, c-format
msgid "%s%s (%s)"
msgstr ""
-#: gschem/src/x_dialog.c:2140
+#: gschem/src/x_dialog.c:2144
msgid "About gschem"
msgstr ""
-#: gschem/src/x_dialog.c:2141
+#: gschem/src/x_dialog.c:2145
msgid "gEDA: GPL Electronic Design Automation"
msgstr ""
-#: gschem/src/x_dialog.c:2142
+#: gschem/src/x_dialog.c:2146
msgid ""
"Copyright © 1998-2009 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
"Copyright © 1998-2009 gEDA Contributors (see ChangeLog for details)"
msgstr ""
-#: gschem/src/x_dialog.c:2201
+#: gschem/src/x_dialog.c:2205
msgid "Coords"
msgstr ""
-#: gschem/src/x_dialog.c:2222
+#: gschem/src/x_dialog.c:2226
msgid "Screen"
msgstr ""
-#: gschem/src/x_dialog.c:2231
+#: gschem/src/x_dialog.c:2235
msgid "World"
msgstr ""
-#: gschem/src/x_dialog.c:2270
+#: gschem/src/x_dialog.c:2274
msgid "Background"
msgstr ""
-#: gschem/src/x_dialog.c:2276
+#: gschem/src/x_dialog.c:2280
msgid "Net endpoint"
msgstr ""
-#: gschem/src/x_dialog.c:2279
+#: gschem/src/x_dialog.c:2283
msgid "Graphic"
msgstr ""
-#: gschem/src/x_dialog.c:2288
+#: gschem/src/x_dialog.c:2292
msgid "Logic bubble"
msgstr ""
-#: gschem/src/x_dialog.c:2291
+#: gschem/src/x_dialog.c:2295
msgid "Grid point"
msgstr ""
-#: gschem/src/x_dialog.c:2294
+#: gschem/src/x_dialog.c:2298
msgid "Detached attribute"
msgstr ""
-#: gschem/src/x_dialog.c:2297 gschem/src/x_window.c:383
+#: gschem/src/x_dialog.c:2301 gschem/src/x_window.c:383
msgid "Text"
msgstr ""
-#: gschem/src/x_dialog.c:2303
+#: gschem/src/x_dialog.c:2307
msgid "Selection"
msgstr ""
-#: gschem/src/x_dialog.c:2306
+#: gschem/src/x_dialog.c:2310
msgid "Bounding box"
msgstr ""
-#: gschem/src/x_dialog.c:2309
+#: gschem/src/x_dialog.c:2313
msgid "Zoom box"
msgstr ""
-#: gschem/src/x_dialog.c:2318
+#: gschem/src/x_dialog.c:2322
msgid "Output background"
msgstr ""
-#: gschem/src/x_dialog.c:2321
+#: gschem/src/x_dialog.c:2325
msgid "Net junction"
msgstr ""
-#: gschem/src/x_dialog.c:2324
+#: gschem/src/x_dialog.c:2328
msgid "Mesh grid major"
msgstr ""
-#: gschem/src/x_dialog.c:2327
+#: gschem/src/x_dialog.c:2331
msgid "Mesh grid minor"
msgstr ""
-#: gschem/src/x_dialog.c:2330
+#: gschem/src/x_dialog.c:2334
msgid "Unknown"
msgstr ""
-#: gschem/src/x_dialog.c:2481
+#: gschem/src/x_dialog.c:2485
#, c-format
msgid "ERROR: NULL object in color_edit_dialog_apply!\n"
msgstr ""
-#: gschem/src/x_dialog.c:2525
+#: gschem/src/x_dialog.c:2529
msgid "Color Edit"
msgstr ""
-#: gschem/src/x_dialog.c:2556
+#: gschem/src/x_dialog.c:2560
msgid "Object color:"
msgstr ""
-#: gschem/src/x_dialog.c:2614
+#: gschem/src/x_dialog.c:2618
msgid "Hotkeys"
msgstr ""
-#: gschem/src/x_dialog.c:2678
+#: gschem/src/x_dialog.c:2682
msgid "Function"
msgstr ""
-#: gschem/src/x_dialog.c:2685
+#: gschem/src/x_dialog.c:2689
msgid "Keystroke(s)"
msgstr ""
-#: gschem/src/x_dialog.c:2991
+#: gschem/src/x_dialog.c:2995
msgid "Find Text"
msgstr ""
-#: gschem/src/x_dialog.c:3022
+#: gschem/src/x_dialog.c:3026
msgid "Text to find:"
msgstr ""
-#: gschem/src/x_dialog.c:3032
+#: gschem/src/x_dialog.c:3036
msgid "descend into hierarchy"
msgstr ""
-#: gschem/src/x_dialog.c:3097
+#: gschem/src/x_dialog.c:3101
msgid "Hide Text"
msgstr ""
-#: gschem/src/x_dialog.c:3128
+#: gschem/src/x_dialog.c:3132
msgid "Hide text starting with:"
msgstr ""
-#: gschem/src/x_dialog.c:3197
+#: gschem/src/x_dialog.c:3201
msgid "Show Text"
msgstr ""
-#: gschem/src/x_dialog.c:3228
+#: gschem/src/x_dialog.c:3232
msgid "Show text starting with:"
msgstr ""
-#: gschem/src/x_dialog.c:3685
+#: gschem/src/x_dialog.c:3689
msgid "S_elect the schematics you want to save:"
msgstr ""
-#: gschem/src/x_dialog.c:3779
+#: gschem/src/x_dialog.c:3784
#, c-format
msgid "Save the changes to schematic \"%s\" before closing?"
msgstr ""
-#: gschem/src/x_dialog.c:3785
+#: gschem/src/x_dialog.c:3790
#, c-format
msgid ""
"There are %d schematics with unsaved changes. Save changes before closing?"
msgstr ""
-#: gschem/src/x_dialog.c:3814
+#: gschem/src/x_dialog.c:3819
msgid "If you don't save, all your changes will be permanently lost."
msgstr ""
-#: gschem/src/x_dialog.c:3834
+#: gschem/src/x_dialog.c:3839
msgid "_Close without saving"
msgstr ""
-#: gschem/src/x_dialog.c:4170
+#: gschem/src/x_dialog.c:4175
#, c-format
msgid ""
"<span weight=\"bold\" size=\"larger\">The input attribute \"%s\" is invalid\n"
@@ -1487,19 +1495,19 @@ msgid ""
"The value cannot start with a space."
msgstr ""
-#: gschem/src/x_dialog.c:4172
+#: gschem/src/x_dialog.c:4177
msgid "Invalid Attribute"
msgstr ""
-#: gschem/src/x_dialog.c:4208
+#: gschem/src/x_dialog.c:4213
msgid "Pin type"
msgstr ""
-#: gschem/src/x_dialog.c:4232
+#: gschem/src/x_dialog.c:4237
msgid "Net pin"
msgstr ""
-#: gschem/src/x_dialog.c:4234
+#: gschem/src/x_dialog.c:4239
msgid "Bus pin (graphical)"
msgstr ""
@@ -1592,11 +1600,11 @@ msgstr ""
msgid "Write image..."
msgstr "Ð?апиÑ?и СнимкаÑ?а..."
-#: gschem/src/x_log.c:188
+#: gschem/src/x_log.c:209
msgid "** Invalid UTF-8 in log message. See stderr or gschem.log.\n"
msgstr ""
-#: gschem/src/x_log.c:256
+#: gschem/src/x_log.c:288
msgid "Status"
msgstr ""
@@ -1672,69 +1680,60 @@ msgstr ""
msgid "/Up"
msgstr ""
-#: gschem/src/x_menus.c:321
+#: gschem/src/x_menus.c:323
#, c-format
msgid "Tried to set the sensitivity on non-existent menu item '%s'\n"
msgstr ""
-#: gschem/src/x_menus.c:345
+#: gschem/src/x_menus.c:347
msgid "Popup_menu_item_factory doesn't exist!\n"
msgstr ""
-#: gschem/src/x_menus.c:358
+#: gschem/src/x_menus.c:360
msgid "Tried to set the sensitivity on a non-existent popup menu_item\n"
msgstr ""
-#: gschem/src/x_menus.c:438
-#, c-format
-msgid "Couldn't open file %s\n"
-msgstr ""
-
-#: gschem/src/x_menus.c:495
-msgid "Clear"
-msgstr ""
-
-#: gschem/src/x_multiattrib.c:911
+#: gschem/src/x_multiattrib.c:915
msgid "Attributes with empty name are not allowed. Please set a name."
msgstr ""
-#: gschem/src/x_multiattrib.c:1456
+#: gschem/src/x_multiattrib.c:1468
msgid "Show Value only"
msgstr ""
-#: gschem/src/x_multiattrib.c:1458
+#: gschem/src/x_multiattrib.c:1470
msgid "Show Name only"
msgstr ""
-#: gschem/src/x_multiattrib.c:1486
+#: gschem/src/x_multiattrib.c:1498
msgid "Promote"
msgstr ""
-#: gschem/src/x_multiattrib.c:1490
+#: gschem/src/x_multiattrib.c:1502
msgid "Duplicate"
msgstr ""
-#: gschem/src/x_multiattrib.c:1708
+#: gschem/src/x_multiattrib.c:1719
msgid "Edit Attributes"
msgstr ""
-#: gschem/src/x_multiattrib.c:1826
+#: gschem/src/x_multiattrib.c:1837
msgid "Vis?"
msgstr ""
-#: gschem/src/x_multiattrib.c:1844
+#: gschem/src/x_multiattrib.c:1855
msgid "N"
msgstr ""
-#: gschem/src/x_multiattrib.c:1862
+#: gschem/src/x_multiattrib.c:1873
msgid "V"
msgstr ""
-#: gschem/src/x_multiattrib.c:1884
+#: gschem/src/x_multiattrib.c:1895
msgid "Show inherited attributes"
msgstr ""
-#: gschem/src/x_multiattrib.c:1900
+#: gschem/src/x_multiattrib.c:1911
msgid "Add Attribute"
msgstr ""
@@ -1758,23 +1757,23 @@ msgstr "Ð?аÑ?воÑ?и СÑ?Ñ?аниÑ?аÑ?а"
msgid "Discard Page"
msgstr ""
-#: gschem/src/x_pagesel.c:376
+#: gschem/src/x_pagesel.c:375
msgid "Page Manager"
msgstr ""
-#: gschem/src/x_pagesel.c:432
+#: gschem/src/x_pagesel.c:431
msgid "Filename"
msgstr ""
-#: gschem/src/x_pagesel.c:448
+#: gschem/src/x_pagesel.c:447
msgid "Changed"
msgstr ""
-#: gschem/src/x_pagesel.c:468
+#: gschem/src/x_pagesel.c:467
msgid "Right click on the filename for more options..."
msgstr ""
-#: gschem/src/x_preview.c:234
+#: gschem/src/x_preview.c:233
msgid "Preview Buffer"
msgstr ""
@@ -1830,23 +1829,23 @@ msgstr ""
msgid "Command:"
msgstr ""
-#: gschem/src/x_print.c:741
+#: gschem/src/x_print.c:745
msgid "No print destination specified\n"
msgstr ""
-#: gschem/src/x_print.c:748
+#: gschem/src/x_print.c:752
#, c-format
msgid "Cannot print current schematic to [%s]\n"
msgstr ""
-#: gschem/src/x_print.c:757
+#: gschem/src/x_print.c:761
#, c-format
msgid ""
"Error printing to file '%s'\n"
"Check the log window for more information"
msgstr ""
-#: gschem/src/x_print.c:764
+#: gschem/src/x_print.c:768
#, c-format
msgid "Printed current schematic to [%s]\n"
msgstr ""
@@ -1855,6 +1854,11 @@ msgstr ""
msgid "Execute Script..."
msgstr "Ð?зпÑ?лни СкÑ?ипÑ?"
+#: gschem/src/x_script.c:66
+#, c-format
+msgid "Executing guile script [%s]\n"
+msgstr ""
+
#: gschem/src/x_window.c:81
#, c-format
msgid "Couldn't allocate gc\n"
@@ -1962,35 +1966,35 @@ msgstr ""
msgid "New file [%s]\n"
msgstr ""
-#: gschem/src/x_window.c:857
+#: gschem/src/x_window.c:855
#, c-format
msgid "Could NOT save page [%s]\n"
msgstr ""
-#: gschem/src/x_window.c:858
+#: gschem/src/x_window.c:856
msgid "Error while trying to save"
msgstr ""
-#: gschem/src/x_window.c:867
+#: gschem/src/x_window.c:865
#, c-format
msgid "Saved as [%s]\n"
msgstr ""
-#: gschem/src/x_window.c:869
+#: gschem/src/x_window.c:867
#, c-format
msgid "Saved [%s]\n"
msgstr ""
-#: gschem/src/x_window.c:871
+#: gschem/src/x_window.c:869
msgid "Saved"
msgstr ""
-#: gschem/src/x_window.c:945
+#: gschem/src/x_window.c:943
#, c-format
msgid "Discarding page [%s]\n"
msgstr ""
-#: gschem/src/x_window.c:945
+#: gschem/src/x_window.c:943
#, c-format
msgid "Closing [%s]\n"
msgstr ""
@@ -2031,7 +2035,7 @@ msgstr ""
msgid "Save All"
msgstr "СÑ?Ñ?Ñ?ани Ð?Ñ?иÑ?ко"
-#: gschem/lib/system-gschemrc.scm:1386 gschem/lib/system-gschemrc.scm:1477
+#: gschem/lib/system-gschemrc.scm:1386 gschem/lib/system-gschemrc.scm:1478
msgid "_Revert"
msgstr ""
@@ -2043,7 +2047,7 @@ msgstr ""
msgid "Write _image..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1393 gschem/lib/system-gschemrc.scm:1478
+#: gschem/lib/system-gschemrc.scm:1393 gschem/lib/system-gschemrc.scm:1479
msgid "_Close"
msgstr ""
@@ -2075,387 +2079,392 @@ msgstr ""
msgid "_Delete"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1412
+#: gschem/lib/system-gschemrc.scm:1409
+#, fuzzy
+msgid "Select All"
+msgstr "Ð?збеÑ?и Ñ?ежим"
+
+#: gschem/lib/system-gschemrc.scm:1410
+msgid "Deselect"
+msgstr ""
+
+#: gschem/lib/system-gschemrc.scm:1414
msgid "Rotate 90 Mode"
msgstr "Ð?авÑ?Ñ?Ñ?и 90 Режим"
-#: gschem/lib/system-gschemrc.scm:1415
+#: gschem/lib/system-gschemrc.scm:1417
msgid "Edit..."
msgstr "РедакÑ?иÑ?ай..."
-#: gschem/lib/system-gschemrc.scm:1416
+#: gschem/lib/system-gschemrc.scm:1418
msgid "Edit Text..."
msgstr "РедакÑ?иÑ?ай ТекÑ?Ñ?..."
-#: gschem/lib/system-gschemrc.scm:1417
+#: gschem/lib/system-gschemrc.scm:1419
msgid "Slot..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1418
+#: gschem/lib/system-gschemrc.scm:1420
msgid "Color..."
msgstr "ЦвÑ?Ñ?..."
-#: gschem/lib/system-gschemrc.scm:1419
+#: gschem/lib/system-gschemrc.scm:1421
msgid "Line Width & Type..."
msgstr "ШиÑ?оÑ?ина на Ð?иниÑ?Ñ?а & Тип"
-#: gschem/lib/system-gschemrc.scm:1420
+#: gschem/lib/system-gschemrc.scm:1422
msgid "Fill Type..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1421
+#: gschem/lib/system-gschemrc.scm:1423
msgid "Symbol Translate..."
msgstr "Ð?Ñ?евеждане на Символ"
-#: gschem/lib/system-gschemrc.scm:1425
+#: gschem/lib/system-gschemrc.scm:1427
msgid "Invoke Macro"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1426
+#: gschem/lib/system-gschemrc.scm:1428
msgid "Embed Component/Picture"
msgstr "Ð?гÑ?аден Ð?омпоненÑ?/Ð?аÑ?Ñ?ина"
-#: gschem/lib/system-gschemrc.scm:1427
+#: gschem/lib/system-gschemrc.scm:1429
msgid "Unembed Component/Picture"
msgstr "Ð?евгÑ?аден Ð?омпоненÑ?/Ð?аÑ?Ñ?ина"
-#: gschem/lib/system-gschemrc.scm:1428
+#: gschem/lib/system-gschemrc.scm:1430
msgid "Update Component"
msgstr "Ð?бнови Ð?омпоненÑ?"
-#: gschem/lib/system-gschemrc.scm:1429
+#: gschem/lib/system-gschemrc.scm:1431
msgid "Show/Hide Inv Text"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1430
-msgid "Make Inv Text Vis"
-msgstr ""
-
-#: gschem/lib/system-gschemrc.scm:1436
+#: gschem/lib/system-gschemrc.scm:1437
msgid "Copy into 1"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1437
+#: gschem/lib/system-gschemrc.scm:1438
msgid "Copy into 2"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1438
+#: gschem/lib/system-gschemrc.scm:1439
msgid "Copy into 3"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1439
+#: gschem/lib/system-gschemrc.scm:1440
msgid "Copy into 4"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1440
+#: gschem/lib/system-gschemrc.scm:1441
msgid "Copy into 5"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1441
+#: gschem/lib/system-gschemrc.scm:1442
msgid "Cut into 1"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1442
+#: gschem/lib/system-gschemrc.scm:1443
msgid "Cut into 2"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1443
+#: gschem/lib/system-gschemrc.scm:1444
msgid "Cut into 3"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1444
+#: gschem/lib/system-gschemrc.scm:1445
msgid "Cut into 4"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1445
+#: gschem/lib/system-gschemrc.scm:1446
msgid "Cut into 5"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1446
+#: gschem/lib/system-gschemrc.scm:1447
msgid "Paste from 1"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1447
+#: gschem/lib/system-gschemrc.scm:1448
msgid "Paste from 2"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1448
+#: gschem/lib/system-gschemrc.scm:1449
msgid "Paste from 3"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1449
+#: gschem/lib/system-gschemrc.scm:1450
msgid "Paste from 4"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1450
+#: gschem/lib/system-gschemrc.scm:1451
msgid "Paste from 5"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1456
+#: gschem/lib/system-gschemrc.scm:1457
msgid "_Redraw"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1457
+#: gschem/lib/system-gschemrc.scm:1458
msgid "_Pan"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1458
+#: gschem/lib/system-gschemrc.scm:1459
msgid "Zoom _Box"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1459
+#: gschem/lib/system-gschemrc.scm:1460
msgid "Zoom _Extents"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1460
+#: gschem/lib/system-gschemrc.scm:1461
msgid "Zoom _In"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1461
+#: gschem/lib/system-gschemrc.scm:1462
msgid "Zoom _Out"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1462
+#: gschem/lib/system-gschemrc.scm:1463
msgid "Zoom _Full"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1464
+#: gschem/lib/system-gschemrc.scm:1465
msgid "_Dark color scheme"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1465
+#: gschem/lib/system-gschemrc.scm:1466
msgid "_Light color scheme"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1466
+#: gschem/lib/system-gschemrc.scm:1467
msgid "B_W color scheme"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1473
+#: gschem/lib/system-gschemrc.scm:1474
msgid "_Manager..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1474
+#: gschem/lib/system-gschemrc.scm:1475
msgid "_Previous"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1475
+#: gschem/lib/system-gschemrc.scm:1476
msgid "_Next"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1476
+#: gschem/lib/system-gschemrc.scm:1477
msgid "Ne_w"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1480
+#: gschem/lib/system-gschemrc.scm:1481
msgid "_Discard"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1486
+#: gschem/lib/system-gschemrc.scm:1487
msgid "_Component..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1487
+#: gschem/lib/system-gschemrc.scm:1488
msgid "_Net"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1488
+#: gschem/lib/system-gschemrc.scm:1489
msgid "B_us"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1489
+#: gschem/lib/system-gschemrc.scm:1490
msgid "_Attribute..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1490
+#: gschem/lib/system-gschemrc.scm:1491
msgid "_Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1492
+#: gschem/lib/system-gschemrc.scm:1493
msgid "_Line"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1493
+#: gschem/lib/system-gschemrc.scm:1494
msgid "_Box"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1494
+#: gschem/lib/system-gschemrc.scm:1495
msgid "C_ircle"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1495
+#: gschem/lib/system-gschemrc.scm:1496
msgid "A_rc"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1496
+#: gschem/lib/system-gschemrc.scm:1497
msgid "_Pin"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1497
+#: gschem/lib/system-gschemrc.scm:1498
msgid "Pictu_re..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1503
+#: gschem/lib/system-gschemrc.scm:1504
msgid "_Down Schematic"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1504
+#: gschem/lib/system-gschemrc.scm:1505
msgid "Down _Symbol"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1505
+#: gschem/lib/system-gschemrc.scm:1506
msgid "_Up"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1506
+#: gschem/lib/system-gschemrc.scm:1507
msgid "D_ocumentation..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1512
+#: gschem/lib/system-gschemrc.scm:1513
msgid "_Attach"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1513
+#: gschem/lib/system-gschemrc.scm:1514
msgid "_Detach"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1514
+#: gschem/lib/system-gschemrc.scm:1515
msgid "Show _Value"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1515
+#: gschem/lib/system-gschemrc.scm:1516
msgid "Show _Name"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1516
+#: gschem/lib/system-gschemrc.scm:1517
msgid "Show _Both"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1517
+#: gschem/lib/system-gschemrc.scm:1518
msgid "_Toggle Visibility"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1519
+#: gschem/lib/system-gschemrc.scm:1520
msgid "_Find Specific Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1520
+#: gschem/lib/system-gschemrc.scm:1521
msgid "_Hide Specific Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1521
+#: gschem/lib/system-gschemrc.scm:1522
msgid "_Show Specific Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1522
+#: gschem/lib/system-gschemrc.scm:1523
msgid "A_utonumber Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1528
+#: gschem/lib/system-gschemrc.scm:1529
msgid "_Text Size..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1529
+#: gschem/lib/system-gschemrc.scm:1530
msgid "Cycle _grid styles"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1530
+#: gschem/lib/system-gschemrc.scm:1531
msgid "Toggle _Snap On/Off"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1531
+#: gschem/lib/system-gschemrc.scm:1532
msgid "Snap Grid S_pacing..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1532
+#: gschem/lib/system-gschemrc.scm:1533
msgid "Scale _up Grid Spacing"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1534
+#: gschem/lib/system-gschemrc.scm:1535
msgid "Scale _down Grid Spacing"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1536
+#: gschem/lib/system-gschemrc.scm:1537
msgid "Toggle _Outline/Box"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1538
+#: gschem/lib/system-gschemrc.scm:1539
msgid "Toggle Net _Rubberband"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1539
+#: gschem/lib/system-gschemrc.scm:1540
msgid "Toggle _Magnetic Net"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1540
+#: gschem/lib/system-gschemrc.scm:1541
msgid "Show _Log Window..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1542
+#: gschem/lib/system-gschemrc.scm:1543
msgid "Show _Coord Window..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1558
+#: gschem/lib/system-gschemrc.scm:1559
msgid "gEDA Docu_mentation..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1559
+#: gschem/lib/system-gschemrc.scm:1560
msgid "gschem _FAQ..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1560
+#: gschem/lib/system-gschemrc.scm:1561
msgid "gEDA _Wiki..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1561
+#: gschem/lib/system-gschemrc.scm:1562
msgid "Component D_ocumentation..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1563
+#: gschem/lib/system-gschemrc.scm:1564
msgid "_Hotkeys..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1564
+#: gschem/lib/system-gschemrc.scm:1565
msgid "_About..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1570
+#: gschem/lib/system-gschemrc.scm:1571
msgid "_File"
msgstr "Файл"
-#: gschem/lib/system-gschemrc.scm:1571
+#: gschem/lib/system-gschemrc.scm:1572
msgid "_Edit"
msgstr "РедакÑ?иÑ?ай"
-#: gschem/lib/system-gschemrc.scm:1572
+#: gschem/lib/system-gschemrc.scm:1573
msgid "_Buffer"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1573
+#: gschem/lib/system-gschemrc.scm:1574
msgid "_View"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1574
+#: gschem/lib/system-gschemrc.scm:1575
msgid "_Page"
msgstr "Ð?ова СÑ?Ñ?аниÑ?а"
-#: gschem/lib/system-gschemrc.scm:1575
+#: gschem/lib/system-gschemrc.scm:1576
msgid "_Add"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1576
+#: gschem/lib/system-gschemrc.scm:1577
msgid "Hie_rarchy"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1577
+#: gschem/lib/system-gschemrc.scm:1578
msgid "A_ttributes"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1578
+#: gschem/lib/system-gschemrc.scm:1579
msgid "_Options"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1579
+#: gschem/lib/system-gschemrc.scm:1580
msgid "_Help"
msgstr ""
diff --git a/gschem/po/de.po b/gschem/po/de.po
index 3c12062..a451abc 100644
--- a/gschem/po/de.po
+++ b/gschem/po/de.po
@@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2010-11-07 13:37+0000\n"
+"POT-Creation-Date: 2011-01-16 00:11-0500\n"
"PO-Revision-Date: 2010-02-14 01:05+0000\n"
"Last-Translator: Werner Hoch <werner.ho@xxxxxx>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -23,17 +23,17 @@ msgstr ""
msgid "Zoom too small! Cannot zoom further.\n"
msgstr "Bereich zu klein! Eine weitere Vergrö�erung ist nicht möglich.\n"
-#: gschem/src/g_funcs.c:339 gschem/src/i_callbacks.c:68
+#: gschem/src/g_funcs.c:347 gschem/src/i_callbacks.c:68
#, c-format
msgid "Could not fork\n"
msgstr "fork fehlgeschlagen!\n"
-#: gschem/src/g_funcs.c:355 gschem/src/i_callbacks.c:78
+#: gschem/src/g_funcs.c:363 gschem/src/i_callbacks.c:78
#, c-format
msgid "Could not invoke %s\n"
msgstr "Konnte %s nicht aufrufen\n"
-#: gschem/src/g_funcs.c:361 gschem/src/i_callbacks.c:82
+#: gschem/src/g_funcs.c:369 gschem/src/i_callbacks.c:82
msgid "Documentation commands not supported under MinGW.\n"
msgstr "Die Funktion \"Dokumentation\" wird unter MinGW nicht unterstützt.\n"
@@ -137,12 +137,12 @@ msgstr ""
"Eine unzulässige Anzahl von Schritten [%d] wurde an scrollpan-steps "
"übergeben\n"
-#: gschem/src/gschem.c:184
+#: gschem/src/gschem.c:188
#, c-format
msgid "gEDA/gschem version %s%s.%s\n"
msgstr "gEDA/gschem Version %s%s.%s\n"
-#: gschem/src/gschem.c:187
+#: gschem/src/gschem.c:191
msgid ""
"gEDA/gschem comes with ABSOLUTELY NO WARRANTY; see COPYING for more "
"details.\n"
@@ -150,14 +150,14 @@ msgstr ""
"gEDA/gschem kommt OHNE JEGLICHE GARANTIE. Bitte lies die Datei COPYING "
"fürnähere Informationen.\n"
-#: gschem/src/gschem.c:189
+#: gschem/src/gschem.c:193
msgid ""
"This is free software, and you are welcome to redistribute it under certain\n"
msgstr ""
"Dies ist Freie Software. Sie darf gerne weitergegeben werden. Bitte lies "
"die\n"
-#: gschem/src/gschem.c:191
+#: gschem/src/gschem.c:195
msgid ""
"conditions; please see the COPYING file for more details.\n"
"\n"
@@ -165,17 +165,17 @@ msgstr ""
"Lizenzbestimmungen in der Datei COPYING für nähere Informationen.\n"
"\n"
-#: gschem/src/gschem.c:194
+#: gschem/src/gschem.c:198
#, c-format
msgid "This is the MINGW32 port.\n"
msgstr "Dies ist die MINGW32 Portierung.\n"
-#: gschem/src/gschem.c:198
+#: gschem/src/gschem.c:202
#, c-format
msgid "Current locale settings: %s\n"
msgstr "Aktuelle Spracheinstellungen: %s\n"
-#: gschem/src/gschem.c:213
+#: gschem/src/gschem.c:218
msgid ""
"You must set the GEDADATA environment variable!\n"
"\n"
@@ -187,31 +187,21 @@ msgstr ""
"gschem kann seine Datendateien nicht finden.\n"
"GEDADATA muss auf das richtige Verzeichnis zeigen.\n"
-#: gschem/src/gschem.c:248
+#: gschem/src/gschem.c:256
#, c-format
msgid "Couldn't find init scm file [%s]\n"
msgstr "Die init scm Datei wurde nicht gefunden [%s]\n"
-#: gschem/src/gschem.c:252
+#: gschem/src/gschem.c:260
#, c-format
msgid "Read init scm file [%s]\n"
msgstr "Lese init scm Datei [%s]\n"
-#: gschem/src/gschem.c:256
+#: gschem/src/gschem.c:264
#, c-format
msgid "Failed to read init scm file [%s]\n"
msgstr "Die Datei init scm [%s] konnte nicht gelesen werden.\n"
-#: gschem/src/gschem.c:317
-#, c-format
-msgid "Scheme directory NOT set!\n"
-msgstr "Das scheme Verzeichnis wurde nicht definiert!\n"
-
-#: gschem/src/gschem.c:324 gschem/src/x_script.c:66
-#, c-format
-msgid "Executing guile script [%s]\n"
-msgstr "Führe guile scipt aus [%s]\n"
-
#: gschem/src/gschem_cairo.c:310
#, c-format
msgid "Unknown end for line (%d)\n"
@@ -235,11 +225,11 @@ msgstr "Bauteil Modus"
msgid "Text Mode"
msgstr "Text Modus"
-#: gschem/src/i_basic.c:84 gschem/lib/system-gschemrc.scm:1409
+#: gschem/src/i_basic.c:84 gschem/lib/system-gschemrc.scm:1411
msgid "Copy Mode"
msgstr "Kopier Modus"
-#: gschem/src/i_basic.c:87 gschem/lib/system-gschemrc.scm:1411
+#: gschem/src/i_basic.c:87 gschem/lib/system-gschemrc.scm:1413
msgid "Move Mode"
msgstr "Verschiebe Modus"
@@ -247,7 +237,7 @@ msgstr "Verschiebe Modus"
msgid "Rotate Mode"
msgstr "Dreh Modus"
-#: gschem/src/i_basic.c:91 gschem/lib/system-gschemrc.scm:1413
+#: gschem/src/i_basic.c:91 gschem/lib/system-gschemrc.scm:1415
msgid "Mirror Mode"
msgstr "Spiegel Modus"
@@ -300,22 +290,22 @@ msgstr "Bogen Modus"
msgid "Pin Mode"
msgstr "AnschluÃ? Modus"
-#: gschem/src/i_basic.c:135 gschem/src/i_callbacks.c:544
-#: gschem/src/i_callbacks.c:568
+#: gschem/src/i_basic.c:135 gschem/src/i_callbacks.c:576
+#: gschem/src/i_callbacks.c:600
msgid "Copy"
msgstr "Kopieren"
-#: gschem/src/i_basic.c:137 gschem/src/i_callbacks.c:634
-#: gschem/src/i_callbacks.c:658
+#: gschem/src/i_basic.c:137 gschem/src/i_callbacks.c:666
+#: gschem/src/i_callbacks.c:690
msgid "Move"
msgstr "Verschieben"
-#: gschem/src/i_basic.c:139 gschem/src/i_callbacks.c:589
-#: gschem/src/i_callbacks.c:613
+#: gschem/src/i_basic.c:139 gschem/src/i_callbacks.c:621
+#: gschem/src/i_callbacks.c:645
msgid "Multiple Copy"
msgstr "Mehrfaches Kopieren"
-#: gschem/src/i_basic.c:142 gschem/lib/system-gschemrc.scm:1410
+#: gschem/src/i_basic.c:142 gschem/lib/system-gschemrc.scm:1412
msgid "Multiple Copy Mode"
msgstr "Mehrfach Kopier Modus"
@@ -335,7 +325,7 @@ msgstr "Neu Ausrichen"
msgid "Action"
msgstr "Aktion"
-#: gschem/src/i_basic.c:260 gschem/src/x_dialog.c:2312
+#: gschem/src/i_basic.c:260 gschem/src/x_dialog.c:2316
#: gschem/src/x_window.c:491
msgid "Stroke"
msgstr "Taste"
@@ -366,7 +356,7 @@ msgstr "Raster(%s, %s)"
msgid "Documentation for [%s,%s,%s,%s]\n"
msgstr "Dokumentation von [%s,%s,%s,%s]\n"
-#: gschem/src/i_callbacks.c:123 gschem/src/i_callbacks.c:1699
+#: gschem/src/i_callbacks.c:123 gschem/src/i_callbacks.c:1706
#, c-format
msgid "New page created [%s]\n"
msgstr "Neue Seite erzeugt [%s]\n"
@@ -388,72 +378,72 @@ msgstr "Alles gespeichert"
msgid "Closing Window\n"
msgstr "SchlieÃ?e Fenster\n"
-#: gschem/src/i_callbacks.c:549 gschem/src/i_callbacks.c:594
-#: gschem/src/i_callbacks.c:639
+#: gschem/src/i_callbacks.c:581 gschem/src/i_callbacks.c:626
+#: gschem/src/i_callbacks.c:671
msgid "Select objs first"
msgstr "Wähle erst Objekte aus"
-#: gschem/src/i_callbacks.c:678 gschem/src/x_multiattrib.c:1491
+#: gschem/src/i_callbacks.c:710 gschem/src/x_multiattrib.c:1503
msgid "Delete"
msgstr "Löschen"
-#: gschem/src/i_callbacks.c:703
+#: gschem/src/i_callbacks.c:735
msgid "Edit"
msgstr "Bearbeiten"
-#: gschem/src/i_callbacks.c:718
+#: gschem/src/i_callbacks.c:750
msgid "Edit pin type"
msgstr "Editiere Pinart"
-#: gschem/src/i_callbacks.c:737
+#: gschem/src/i_callbacks.c:769
msgid "Edit Text"
msgstr "Text bearbeiten"
-#: gschem/src/i_callbacks.c:760
+#: gschem/src/i_callbacks.c:792
msgid "Slot"
msgstr "Slot"
-#: gschem/src/i_callbacks.c:777
+#: gschem/src/i_callbacks.c:809
msgid "Color"
msgstr "Farbe"
-#: gschem/src/i_callbacks.c:814 gschem/src/i_callbacks.c:859
+#: gschem/src/i_callbacks.c:846 gschem/src/i_callbacks.c:891
msgid "Rotate"
msgstr "Drehen"
-#: gschem/src/i_callbacks.c:882 gschem/src/i_callbacks.c:907
+#: gschem/src/i_callbacks.c:913 gschem/src/i_callbacks.c:938
msgid "Mirror"
msgstr "Spiegeln"
-#: gschem/src/i_callbacks.c:928 gschem/src/x_dialog.c:2315
-#: gschem/lib/system-gschemrc.scm:1422
+#: gschem/src/i_callbacks.c:959 gschem/src/x_dialog.c:2319
+#: gschem/lib/system-gschemrc.scm:1424
msgid "Lock"
msgstr "Sperren"
-#: gschem/src/i_callbacks.c:946 gschem/lib/system-gschemrc.scm:1423
+#: gschem/src/i_callbacks.c:977 gschem/lib/system-gschemrc.scm:1425
msgid "Unlock"
msgstr "Entsperren"
-#: gschem/src/i_callbacks.c:964 gschem/src/x_dialog.c:1734
+#: gschem/src/i_callbacks.c:995 gschem/src/x_dialog.c:1737
msgid "Translate"
msgstr "Verschieben nach"
-#: gschem/src/i_callbacks.c:967
+#: gschem/src/i_callbacks.c:998
msgid "WARNING: Do not translate with snap off!\n"
msgstr ""
"ACHTUNG: Keine Transformation mit ausgeschalteter Ausrichtung am Raster!\n"
-#: gschem/src/i_callbacks.c:968
+#: gschem/src/i_callbacks.c:999
msgid "WARNING: Turning snap on and continuing with translate.\n"
msgstr ""
"ACHTUNG:\"am Raster ausrichten\" wird aktiviert und mit der Transformation "
"fortgefahren.\n"
-#: gschem/src/i_callbacks.c:975
+#: gschem/src/i_callbacks.c:1006
msgid "WARNING: Snap grid size is not equal to 100!\n"
msgstr "ACHTUNG: Das Raster ist ungleich 100!\n"
-#: gschem/src/i_callbacks.c:977
+#: gschem/src/i_callbacks.c:1008
msgid ""
"WARNING: If you are translating a symbol to the origin, the snap grid size "
"should be set to 100\n"
@@ -461,176 +451,172 @@ msgstr ""
"ACHTUNG: Wenn ein Symbol transformiert wird, sollte das Raster auf 100 "
"gesetzt sein.\n"
-#: gschem/src/i_callbacks.c:1008
+#: gschem/src/i_callbacks.c:1039
msgid "Embed"
msgstr "Einbetten"
-#: gschem/src/i_callbacks.c:1047
+#: gschem/src/i_callbacks.c:1078
msgid "Unembed"
msgstr "Ausbetten"
-#: gschem/src/i_callbacks.c:1089
+#: gschem/src/i_callbacks.c:1120
msgid "Update"
msgstr "Aktualisieren"
-#: gschem/src/i_callbacks.c:1136
+#: gschem/src/i_callbacks.c:1167
msgid "ShowHidden"
msgstr "Zeige Unsichbares"
-#: gschem/src/i_callbacks.c:1160
-msgid "MakeVisible"
-msgstr "Sichbar Machen"
-
-#: gschem/src/i_callbacks.c:1466 gschem/src/i_callbacks.c:1538
+#: gschem/src/i_callbacks.c:1473 gschem/src/i_callbacks.c:1545
msgid "Pan"
msgstr "Ausschnitt verschieben"
-#: gschem/src/i_callbacks.c:1743
+#: gschem/src/i_callbacks.c:1750
msgid "Really revert page?"
msgstr "Seite wirklich wiederherstellen?"
-#: gschem/src/i_callbacks.c:1813
+#: gschem/src/i_callbacks.c:1820
msgid "Copy to clipboard"
msgstr "Kopieren"
-#: gschem/src/i_callbacks.c:1831
+#: gschem/src/i_callbacks.c:1838
msgid "Cut to clipboard"
msgstr "Einfügen"
-#: gschem/src/i_callbacks.c:1849
+#: gschem/src/i_callbacks.c:1856
msgid "Paste from clipboard"
msgstr "Einfügen"
-#: gschem/src/i_callbacks.c:1861 gschem/src/i_callbacks.c:2100
-#: gschem/src/i_callbacks.c:2122 gschem/src/i_callbacks.c:2144
-#: gschem/src/i_callbacks.c:2166 gschem/src/i_callbacks.c:2188
+#: gschem/src/i_callbacks.c:1868 gschem/src/i_callbacks.c:2107
+#: gschem/src/i_callbacks.c:2129 gschem/src/i_callbacks.c:2151
+#: gschem/src/i_callbacks.c:2173 gschem/src/i_callbacks.c:2195
msgid "Empty buffer"
msgstr "Leerer Zwischenspeicher"
-#: gschem/src/i_callbacks.c:1906
+#: gschem/src/i_callbacks.c:1913
msgid "Copy 1"
msgstr "Kopie 1"
-#: gschem/src/i_callbacks.c:1925
+#: gschem/src/i_callbacks.c:1932
msgid "Copy 2"
msgstr "Kopie 2"
-#: gschem/src/i_callbacks.c:1944
+#: gschem/src/i_callbacks.c:1951
msgid "Copy 3"
msgstr "Kopie 3"
-#: gschem/src/i_callbacks.c:1963
+#: gschem/src/i_callbacks.c:1970
msgid "Copy 4"
msgstr "Kopie 4"
-#: gschem/src/i_callbacks.c:1982
+#: gschem/src/i_callbacks.c:1989
msgid "Copy 5"
msgstr "Kopie 5"
-#: gschem/src/i_callbacks.c:2001
+#: gschem/src/i_callbacks.c:2008
msgid "Cut 1"
msgstr "Ausschneiden 1"
-#: gschem/src/i_callbacks.c:2020
+#: gschem/src/i_callbacks.c:2027
msgid "Cut 2"
msgstr "Ausschneiden 2"
-#: gschem/src/i_callbacks.c:2039
+#: gschem/src/i_callbacks.c:2046
msgid "Cut 3"
msgstr "Ausschneiden 3"
-#: gschem/src/i_callbacks.c:2058
+#: gschem/src/i_callbacks.c:2065
msgid "Cut 4"
msgstr "Ausschneiden 4"
-#: gschem/src/i_callbacks.c:2077
+#: gschem/src/i_callbacks.c:2084
msgid "Cut 5"
msgstr "Ausschneiden 5"
-#: gschem/src/i_callbacks.c:2093
+#: gschem/src/i_callbacks.c:2100
msgid "Paste 1"
msgstr "Einfügen 1"
-#: gschem/src/i_callbacks.c:2115
+#: gschem/src/i_callbacks.c:2122
msgid "Paste 2"
msgstr "Einfügen 2"
-#: gschem/src/i_callbacks.c:2137
+#: gschem/src/i_callbacks.c:2144
msgid "Paste 3"
msgstr "Einfügen 3"
-#: gschem/src/i_callbacks.c:2159
+#: gschem/src/i_callbacks.c:2166
msgid "Paste 4"
msgstr "Einfügen 4"
-#: gschem/src/i_callbacks.c:2181
+#: gschem/src/i_callbacks.c:2188
msgid "Paste 5"
msgstr "Einfügen 5"
-#: gschem/src/i_callbacks.c:2318 gschem/src/x_window.c:355
+#: gschem/src/i_callbacks.c:2325 gschem/src/x_window.c:355
msgid "Component"
msgstr "Bauteil"
-#: gschem/src/i_callbacks.c:2354 gschem/src/i_callbacks.c:2373
-#: gschem/src/x_dialog.c:2285
+#: gschem/src/i_callbacks.c:2361 gschem/src/i_callbacks.c:2380
+#: gschem/src/x_dialog.c:2289
msgid "Attribute"
msgstr "Attribut"
-#: gschem/src/i_callbacks.c:2395 gschem/src/i_callbacks.c:2422
-#: gschem/src/x_dialog.c:2282
+#: gschem/src/i_callbacks.c:2402 gschem/src/i_callbacks.c:2429
+#: gschem/src/x_dialog.c:2286
msgid "Net"
msgstr "Netz"
-#: gschem/src/i_callbacks.c:2466 gschem/src/i_callbacks.c:2493
-#: gschem/src/x_dialog.c:2300 gschem/src/x_window.c:375
+#: gschem/src/i_callbacks.c:2473 gschem/src/i_callbacks.c:2500
+#: gschem/src/x_dialog.c:2304 gschem/src/x_window.c:375
msgid "Bus"
msgstr "Bus"
-#: gschem/src/i_callbacks.c:2574 gschem/src/i_callbacks.c:2597
+#: gschem/src/i_callbacks.c:2581 gschem/src/i_callbacks.c:2604
msgid "Line"
msgstr "Linie"
-#: gschem/src/i_callbacks.c:2619 gschem/src/i_callbacks.c:2642
+#: gschem/src/i_callbacks.c:2626 gschem/src/i_callbacks.c:2649
msgid "Box"
msgstr "Rechteck"
-#: gschem/src/i_callbacks.c:2698 gschem/src/i_callbacks.c:2722
+#: gschem/src/i_callbacks.c:2705 gschem/src/i_callbacks.c:2729
msgid "Circle"
msgstr "Kreis"
-#: gschem/src/i_callbacks.c:2744 gschem/src/i_callbacks.c:2767
+#: gschem/src/i_callbacks.c:2751 gschem/src/i_callbacks.c:2774
msgid "Arc"
msgstr "Bogen"
-#: gschem/src/i_callbacks.c:2789 gschem/src/i_callbacks.c:2812
-#: gschem/src/x_dialog.c:2273
+#: gschem/src/i_callbacks.c:2796 gschem/src/i_callbacks.c:2819
+#: gschem/src/x_dialog.c:2277
msgid "Pin"
msgstr "AnschluÃ?"
-#: gschem/src/i_callbacks.c:2871
+#: gschem/src/i_callbacks.c:2878
#, c-format
msgid "Searching for source [%s]\n"
msgstr "Suche nach der Quelle [%s]\n"
-#: gschem/src/i_callbacks.c:2895
+#: gschem/src/i_callbacks.c:2902
#, c-format
msgid "Cannot find source [%s]\n"
msgstr "Die Quelle [%s] konnte nicht gefunden werden.\n"
-#: gschem/src/i_callbacks.c:2964
+#: gschem/src/i_callbacks.c:2965
#, c-format
msgid "Searching for symbol [%s]\n"
msgstr "Suche nach dem Symbol [%s]\n"
-#: gschem/src/i_callbacks.c:2970
+#: gschem/src/i_callbacks.c:2971
msgid "Symbol is not a real file. Symbol cannot be loaded.\n"
msgstr "Das Symbol ist keine reale Datei. Symbol kann nicht geöffnet werden.\n"
-#: gschem/src/i_callbacks.c:3001
+#: gschem/src/i_callbacks.c:3002
msgid "Cannot find any schematics above the current one!\n"
msgstr "Konnte keinen übergeordneten Schaltplan finden!\n"
-#: gschem/src/i_callbacks.c:3055
+#: gschem/src/i_callbacks.c:3056
msgid ""
"This command retrieves the component documentation from the web, but there "
"is no component selected"
@@ -638,84 +624,84 @@ msgstr ""
"Dieser Befehl sucht die Dokumentation eines Bauteils im Internet, aber es "
"wurde kein Bauteil ausgewählt"
-#: gschem/src/i_callbacks.c:3083
+#: gschem/src/i_callbacks.c:3084
msgid "Attach"
msgstr "Anbringen"
-#: gschem/src/i_callbacks.c:3130
+#: gschem/src/i_callbacks.c:3131
msgid "Detach"
msgstr "Ablösen"
-#: gschem/src/i_callbacks.c:3165
+#: gschem/src/i_callbacks.c:3166
msgid "ShowN"
msgstr "ShowN"
-#: gschem/src/i_callbacks.c:3201
+#: gschem/src/i_callbacks.c:3202
msgid "ShowV"
msgstr "ShowV"
-#: gschem/src/i_callbacks.c:3237
+#: gschem/src/i_callbacks.c:3238
msgid "ShowB"
msgstr "ShowB"
-#: gschem/src/i_callbacks.c:3274
+#: gschem/src/i_callbacks.c:3275
msgid "VisToggle"
msgstr "VisToggle"
-#: gschem/src/i_callbacks.c:3304
+#: gschem/src/i_callbacks.c:3305
#, c-format
msgid "Sorry but this is a non-functioning menu option\n"
msgstr "Dieser Menupunkt funktioniert nicht. Sorry.\n"
-#: gschem/src/i_callbacks.c:3394
+#: gschem/src/i_callbacks.c:3395
msgid "Action feedback mode set to OUTLINE\n"
msgstr "Aktions-Rückmelde-Modus wurde auf OUTLINE gesetzt.\n"
-#: gschem/src/i_callbacks.c:3397
+#: gschem/src/i_callbacks.c:3398
msgid "Action feedback mode set to BOUNDINGBOX\n"
msgstr "Aktions-Rückmelde-Modus wurde auf BOUNDINGBOX gesetzt.\n"
-#: gschem/src/i_callbacks.c:3422
+#: gschem/src/i_callbacks.c:3423
msgid "Grid OFF\n"
msgstr "Raster AUS\n"
-#: gschem/src/i_callbacks.c:3423
+#: gschem/src/i_callbacks.c:3424
msgid "Dot grid selected\n"
msgstr "Punktraster ausgewählt\n"
-#: gschem/src/i_callbacks.c:3424
+#: gschem/src/i_callbacks.c:3425
msgid "Mesh grid selected\n"
msgstr "Linienraster ausgewählt\n"
-#: gschem/src/i_callbacks.c:3445
+#: gschem/src/i_callbacks.c:3446
msgid "Snap OFF (CAUTION!)\n"
msgstr "Freihandmodus (ACHTUNG! Ausrichten am Raster abgeschaltet)\n"
-#: gschem/src/i_callbacks.c:3448
+#: gschem/src/i_callbacks.c:3449
msgid "Snap ON\n"
msgstr "Am Raster ausrichten\n"
-#: gschem/src/i_callbacks.c:3451
+#: gschem/src/i_callbacks.c:3452
msgid "Snap back to the grid (CAUTION!)\n"
msgstr "Objekte neu am Raster ausrichten (Achtung!)\n"
-#: gschem/src/i_callbacks.c:3477
+#: gschem/src/i_callbacks.c:3478
msgid "Rubber band OFF \n"
msgstr "Gummifäden AUS \n"
-#: gschem/src/i_callbacks.c:3480
+#: gschem/src/i_callbacks.c:3481
msgid "Rubber band ON\n"
msgstr "Gummifäden EIN\n"
-#: gschem/src/i_callbacks.c:3495
+#: gschem/src/i_callbacks.c:3496
msgid "magnetic net mode: ON\n"
msgstr "magnetischer Netz Modus: Ein\n"
-#: gschem/src/i_callbacks.c:3498
+#: gschem/src/i_callbacks.c:3499
msgid "magnetic net mode: OFF\n"
msgstr "magnetischer Netz Modus: Aus\n"
-#: gschem/src/o_box.c:153
+#: gschem/src/o_box.c:149
#, c-format
msgid "Unknown type for box (fill)!\n"
msgstr "Undefinierter Typ für das Rechteck (Füllung)!\n"
@@ -737,17 +723,17 @@ msgstr ""
"Eine ungültige Zwischenspeichernummer wurde übergeben "
"[o_buffer_paste_start]\n"
-#: gschem/src/o_bus.c:118
+#: gschem/src/o_bus.c:117
#, c-format
msgid "Got an invalid which one in o_bus_draw_stretch\n"
msgstr "Ungültiger Wert für das Pinende in der Funktion o_bus_draw_stretch\n"
-#: gschem/src/o_circle.c:134
+#: gschem/src/o_circle.c:130
#, c-format
msgid "Unknown type for circle (fill)!\n"
msgstr "Undefinierter Typ für einen Kreis (Füllung).\n"
-#: gschem/src/o_complex.c:243 gschem/src/o_complex.c:247
+#: gschem/src/o_complex.c:237 gschem/src/o_complex.c:241
#, c-format
msgid "Translating schematic [%d %d]\n"
msgstr "Verschiebe Schaltplan [%d %d]\n"
@@ -765,40 +751,40 @@ msgstr "Objekt bereits gesperrt\n"
msgid "Object already unlocked\n"
msgstr "Objekt bereits entsperrt\n"
-#: gschem/src/o_misc.c:413
+#: gschem/src/o_misc.c:409
msgid "Hidden text is now visible\n"
msgstr "Verborgener Text ist jetzt sichtbar.\n"
-#: gschem/src/o_misc.c:415
+#: gschem/src/o_misc.c:411
msgid "Hidden text is now invisible\n"
msgstr "Verborgener Text ist jetzt unsichbar.\n"
-#: gschem/src/o_misc.c:668
+#: gschem/src/o_misc.c:636
#, c-format
msgid "Could not find symbol [%s] in library. Update failed.\n"
msgstr ""
"Das Symbol [%s] konnte nicht gefunden werden. Aktualisierung "
"fehlgeschlagen.\n"
-#: gschem/src/o_misc.c:783
+#: gschem/src/o_misc.c:751
#, c-format
msgid "o_autosave_backups: Can't get the real filename of %s."
msgstr ""
"o_autosave_backups: Konnte den tatsächlichen Dateinamen von %s nicht "
"ermitteln."
-#: gschem/src/o_misc.c:827
+#: gschem/src/o_misc.c:795
#, c-format
msgid "Could NOT set previous backup file [%s] read-write\n"
msgstr ""
"Die vorherige Backup-Datei [%s] konnte nicht auf read-write gesetzt werden.\n"
-#: gschem/src/o_misc.c:845
+#: gschem/src/o_misc.c:815
#, c-format
msgid "Could NOT set backup file [%s] readonly\n"
msgstr "Die Backup-Datei [%s] konnte nicht auf readonly gesetzt werden.\n"
-#: gschem/src/o_misc.c:850
+#: gschem/src/o_misc.c:820
#, c-format
msgid "Could NOT save backup file [%s]\n"
msgstr "Die Backup-Datei [%s] konnte nicht gespeichert werden.\n"
@@ -820,39 +806,39 @@ msgstr ""
msgid "Got a non line object in o_move_check_endpoint\n"
msgstr "Da ist ein Objekt in o_move_check_endpoint, welches keine Linie ist.\n"
-#: gschem/src/o_net.c:159
+#: gschem/src/o_net.c:158
#, c-format
msgid "Got an invalid which one in o_net_draw_stretch\n"
msgstr "Ungültiger Wert für das Pinende in der Funktion o_net_draw_stretch\n"
-#: gschem/src/o_net.c:538
+#: gschem/src/o_net.c:537
msgid "Warning: Starting net at off grid coordinate\n"
msgstr ""
"Achtung: Der Startpunkt des Netzes befindet sich nicht auf dem Raster\n"
-#: gschem/src/o_net.c:600
+#: gschem/src/o_net.c:599
msgid "Warning: Ending net at off grid coordinate\n"
msgstr "Achtung: Das Ende des Netzes befindet sich nicht auf dem Raster\n"
-#: gschem/src/o_net.c:932 gschem/src/o_net.c:969 gschem/src/o_net.c:1040
-#: gschem/src/o_net.c:1076
+#: gschem/src/o_net.c:931 gschem/src/o_net.c:968 gschem/src/o_net.c:1039
+#: gschem/src/o_net.c:1075
#, c-format
msgid "Tried to add more than two bus rippers. Internal gschem error.\n"
msgstr ""
"Interner gschem Fehler: Versuchte mehr als zwei Bus Abzweigungen "
"hinzuzufügen\n"
-#: gschem/src/o_net.c:1144
+#: gschem/src/o_net.c:1143
#, c-format
msgid "Bus ripper symbol [%s] was not found in any component library\n"
msgstr "Das Busripper Symbol [%s] wurde in keiner Bauteilbibliothek gefunden\n"
-#: gschem/src/o_path.c:352
+#: gschem/src/o_path.c:348
#, c-format
msgid "Unknown type for path (fill)!\n"
msgstr "Unbekannte Füllart einer Pfad-Definition!\n"
-#: gschem/src/o_picture.c:163 gschem/src/o_picture.c:539
+#: gschem/src/o_picture.c:163 gschem/src/o_picture.c:537
#, c-format
msgid "Failed to load picture: %s"
msgstr "Das Bild [%s] konnte nicht geladen werden"
@@ -861,7 +847,7 @@ msgstr "Das Bild [%s] konnte nicht geladen werden"
msgid "Picture"
msgstr "Bild"
-#: gschem/src/o_picture.c:447 gschem/src/x_attribedit.c:141
+#: gschem/src/o_picture.c:445 gschem/src/x_attribedit.c:141
#, c-format
msgid "ERROR: NULL object!\n"
msgstr "FEHLER: NULL Objekt!\n"
@@ -882,34 +868,46 @@ msgstr "Bei diesem Bauteil ist nur ein slot erlaubt.\n"
msgid "New slot number out of range\n"
msgstr "Neue slot Nummer au�erhalb des gültigen Wertebereichs\n"
-#: gschem/src/o_undo.c:304
+#: gschem/src/o_undo.c:303
msgid "Undo/Redo disabled in rc file\n"
msgstr "Rückgängig/Wiederherstellen wurde in der rc Datei deaktiviert.\n"
-#: gschem/src/parsecmd.c:47
+#: gschem/src/parsecmd.c:81
#, c-format
msgid ""
-"Usage: %s [OPTIONS] schematic_filename1 ... schematic_filenameN\n"
-" -q Quiet mode\n"
-" -v Verbose mode on\n"
-" -r filename Rc filename\n"
-" -s filename Script (guile) filename\n"
-" -o filename Output filename (for printing)\n"
-" -p Automatically place the window\n"
-" -t Print stroke information\n"
-" -h Help; this message\n"
+"Usage: %s [OPTION ...] [--] [FILE ...]\n"
"\n"
-msgstr ""
-"Aufruf: %s [Optionen] Schaltplan_Datei1 ... Schaltplan_DateiN\n"
-" -q keine Standardausgabe\n"
-" -v viele Standardausgaben\n"
-" -r Dateiname Rc Dateiname\n"
-" -s Dateiname Skript (guile) Dateiname\n"
-" -o Dateiname Ausgabe Dateiname (für den Ausdruck)\n"
-" -p Fenster automatisch platzieren\n"
-" -t Tastaturkürzel ausgeben\n"
-" -h Hilfe (diese Ausgabe)\n"
+"Interactively edit gEDA schematics or symbols. If one or more FILEs\n"
+"are specified, open them for editing; otherwise, create a new, empty\n"
+"schematic.\n"
"\n"
+"Options:\n"
+" -q, --quiet Quiet mode.\n"
+" -v, --verbose Verbose mode.\n"
+" -r, --config-file=FILE Additional configuration file to load.\n"
+" -L DIR Add DIR to Scheme search path.\n"
+" -c EXPR Scheme expression to run at startup.\n"
+" -s FILE Scheme script to run at startup.\n"
+" -o, --output=FILE Output filename (for printing).\n"
+" -p Automatically place the window.\n"
+" -V, --version Show version information.\n"
+" -h, --help Help; this message.\n"
+" -- Treat all remaining arguments as filenames.\n"
+"\n"
+"Report bugs to <geda-bug@xxxxxxxx>\n"
+"gEDA/gaf homepage: <http://gpleda.org>\n"
+msgstr ""
+
+#: gschem/src/parsecmd.c:115
+#, c-format
+msgid ""
+"gEDA %s (g%.7s)\n"
+"Copyright (C) 1998-2011 gEDA developers\n"
+"This is free software, and you are welcome to redistribute it under\n"
+"certain conditions. For details, see the file `COPYING', which is\n"
+"included in the gEDA distribution.\n"
+"There is NO WARRANTY, to the extent permitted by law.\n"
+msgstr ""
#: gschem/src/x_attribedit.c:127
#, c-format
@@ -920,56 +918,56 @@ msgstr "Ungültige Anzeigeoption, zeige beide als Voreinstellung\n"
msgid "Single Attribute Editor"
msgstr "Editor für ein Attribut"
-#: gschem/src/x_attribedit.c:358
+#: gschem/src/x_attribedit.c:359
msgid "<b>Edit Attribute</b>"
msgstr "<b>Attribut bearbeiten</b>"
-#: gschem/src/x_attribedit.c:360
+#: gschem/src/x_attribedit.c:361
msgid "<b>Add Attribute</b>"
msgstr "<b>Attribut hinzufügen</b>"
-#: gschem/src/x_attribedit.c:376 gschem/src/x_multiattrib.c:1916
+#: gschem/src/x_attribedit.c:377 gschem/src/x_multiattrib.c:1927
msgid "Name:"
msgstr "Name:"
-#: gschem/src/x_attribedit.c:393 gschem/src/x_multiattrib.c:1935
+#: gschem/src/x_attribedit.c:394 gschem/src/x_multiattrib.c:1946
msgid "Value:"
msgstr "Wert:"
-#: gschem/src/x_attribedit.c:409 gschem/src/x_multiattrib.c:1978
+#: gschem/src/x_attribedit.c:410 gschem/src/x_multiattrib.c:1989
msgid "Visible"
msgstr "Sichtbar"
-#: gschem/src/x_attribedit.c:429
+#: gschem/src/x_attribedit.c:430
msgid "Show Value Only"
msgstr "Nur Wert anzeigen"
-#: gschem/src/x_attribedit.c:431
+#: gschem/src/x_attribedit.c:432
msgid "Show Name Only"
msgstr "Nur Name anzeigen"
-#: gschem/src/x_attribedit.c:433 gschem/src/x_multiattrib.c:1454
+#: gschem/src/x_attribedit.c:434 gschem/src/x_multiattrib.c:1466
msgid "Show Name & Value"
msgstr "Zeige Name & Wert"
-#: gschem/src/x_attribedit.c:440
+#: gschem/src/x_attribedit.c:441
msgid "<b>Attach Options</b>"
msgstr "<b>Optionen</b>"
-#: gschem/src/x_attribedit.c:455
+#: gschem/src/x_attribedit.c:456
msgid "All"
msgstr "Alle"
-#: gschem/src/x_attribedit.c:463 gschem/src/x_compselect.c:896
-#: gschem/src/x_compselect.c:1010
+#: gschem/src/x_attribedit.c:464 gschem/src/x_compselect.c:904
+#: gschem/src/x_compselect.c:1018
msgid "Components"
msgstr "Bauteile"
-#: gschem/src/x_attribedit.c:471 gschem/src/x_window.c:365
+#: gschem/src/x_attribedit.c:472 gschem/src/x_window.c:365
msgid "Nets"
msgstr "Netz"
-#: gschem/src/x_attribedit.c:479
+#: gschem/src/x_attribedit.c:480
msgid "Replace existing attributes"
msgstr "Vorhandene Attribute ersetzen"
@@ -989,91 +987,91 @@ msgstr ""
"Doppelt vergebener slot kann Probleme verursachen: [Symbolname=%s, Number="
"%d, slot=%d]\n"
-#: gschem/src/x_autonumber.c:673
+#: gschem/src/x_autonumber.c:675
msgid "No searchstring given in autonumber text.\n"
msgstr "Es wurde kein Suchstring im Dialog eingegeben.\n"
-#: gschem/src/x_autonumber.c:725
+#: gschem/src/x_autonumber.c:727
msgid "No '*' or '?' given at the end of the autonumber text.\n"
msgstr "Am Ende des Suchstrings fehlt ein '*' oder ein '?'.\n"
-#: gschem/src/x_autonumber.c:860
+#: gschem/src/x_autonumber.c:862
msgid "Diagonal"
msgstr "Diagonal"
-#: gschem/src/x_autonumber.c:861
+#: gschem/src/x_autonumber.c:863
msgid "Top to bottom"
msgstr "Von oben nach unten"
-#: gschem/src/x_autonumber.c:861
+#: gschem/src/x_autonumber.c:863
msgid "Bottom to top"
msgstr "Von unten nach oben"
-#: gschem/src/x_autonumber.c:862
+#: gschem/src/x_autonumber.c:864
msgid "Left to right"
msgstr "Von links nach rechts"
-#: gschem/src/x_autonumber.c:862
+#: gschem/src/x_autonumber.c:864
msgid "Right to left"
msgstr "Von rechts nach links"
-#: gschem/src/x_autonumber.c:863
+#: gschem/src/x_autonumber.c:865
msgid "File order"
msgstr "Dateireihenfolge"
-#: gschem/src/x_autonumber.c:1199
+#: gschem/src/x_autonumber.c:1201
msgid "Autonumber text"
msgstr "Nummeriere Text automatisch"
-#: gschem/src/x_autonumber.c:1223
+#: gschem/src/x_autonumber.c:1225
msgid "<b>Scope</b>"
msgstr "<b>Suchbereich</b>"
-#: gschem/src/x_autonumber.c:1245
+#: gschem/src/x_autonumber.c:1247
msgid "Search for:"
msgstr "Suchen nach:"
-#: gschem/src/x_autonumber.c:1259
+#: gschem/src/x_autonumber.c:1261
msgid "Autonumber text in:"
msgstr "Nummeriere Text in:"
-#: gschem/src/x_autonumber.c:1266
+#: gschem/src/x_autonumber.c:1268
msgid "Skip numbers found in:"
msgstr "Ã?berspringe Nummern:"
-#: gschem/src/x_autonumber.c:1278 gschem/src/x_autonumber.c:1287
+#: gschem/src/x_autonumber.c:1280 gschem/src/x_autonumber.c:1289
msgid "Selected objects"
msgstr "Ausgewählte Objekte"
-#: gschem/src/x_autonumber.c:1279 gschem/src/x_autonumber.c:1288
+#: gschem/src/x_autonumber.c:1281 gschem/src/x_autonumber.c:1290
msgid "Current page"
msgstr "Aktuelle Seite"
-#: gschem/src/x_autonumber.c:1280 gschem/src/x_autonumber.c:1289
+#: gschem/src/x_autonumber.c:1282 gschem/src/x_autonumber.c:1291
msgid "Whole hierarchy"
msgstr "Gesamte Hierarchie"
-#: gschem/src/x_autonumber.c:1291
+#: gschem/src/x_autonumber.c:1293
msgid "Overwrite existing numbers"
msgstr "Vorhandene Nummern überschreiben"
-#: gschem/src/x_autonumber.c:1296
+#: gschem/src/x_autonumber.c:1298
msgid "<b>Options</b>"
msgstr "<b>Optionen</b>"
-#: gschem/src/x_autonumber.c:1318
+#: gschem/src/x_autonumber.c:1320
msgid "Starting number:"
msgstr "Startnummer:"
-#: gschem/src/x_autonumber.c:1325
+#: gschem/src/x_autonumber.c:1327
msgid "Sort order:"
msgstr "Sortierung:"
-#: gschem/src/x_autonumber.c:1346
+#: gschem/src/x_autonumber.c:1348
msgid "Remove numbers"
msgstr "Nummern entfernen"
-#: gschem/src/x_autonumber.c:1350
+#: gschem/src/x_autonumber.c:1352
msgid "Automatic slotting"
msgstr "Automatische Nummerierung von Slots"
@@ -1110,48 +1108,48 @@ msgstr "Versuchte eine ungültige Farbe zuzuteilen: %d\n"
msgid "Tried to get an invalid outline color: %d\n"
msgstr "Versuchte eine ungültige Farbe zu holen: %d\n"
-#: gschem/src/x_compselect.c:1040
+#: gschem/src/x_compselect.c:1048
msgid "Filter:"
msgstr "Filter:"
-#: gschem/src/x_compselect.c:1143 gschem/src/x_dialog.c:3663
-#: gschem/src/x_multiattrib.c:1782
+#: gschem/src/x_compselect.c:1151 gschem/src/x_dialog.c:3667
+#: gschem/src/x_multiattrib.c:1793
msgid "Name"
msgstr "Name"
-#: gschem/src/x_compselect.c:1152 gschem/src/x_multiattrib.c:1806
+#: gschem/src/x_compselect.c:1160 gschem/src/x_multiattrib.c:1817
msgid "Value"
msgstr "Wert"
-#: gschem/src/x_compselect.c:1191
+#: gschem/src/x_compselect.c:1199
msgid "Default behavior - reference component"
msgstr "Bauteil referenzieren (Voreinstellung)"
-#: gschem/src/x_compselect.c:1194
+#: gschem/src/x_compselect.c:1202
msgid "Embed component in schematic"
msgstr "Bauteil in den Schaltplan einbetten"
-#: gschem/src/x_compselect.c:1197
+#: gschem/src/x_compselect.c:1205
msgid "Include component as individual objects"
msgstr "Bauteil als Einzelkomponenten einfügen"
-#: gschem/src/x_compselect.c:1354
+#: gschem/src/x_compselect.c:1362
msgid "Select Component..."
msgstr "Bauteil auswählen..."
-#: gschem/src/x_compselect.c:1377
+#: gschem/src/x_compselect.c:1385
msgid "In Use"
msgstr "In Verwendung"
-#: gschem/src/x_compselect.c:1381
+#: gschem/src/x_compselect.c:1389
msgid "Libraries"
msgstr "Bibliotheken"
-#: gschem/src/x_compselect.c:1390 gschem/src/x_fileselect.c:122
+#: gschem/src/x_compselect.c:1398 gschem/src/x_fileselect.c:122
msgid "Preview"
msgstr "Vorschau"
-#: gschem/src/x_compselect.c:1418
+#: gschem/src/x_compselect.c:1426
msgid "Attributes"
msgstr "Attribut"
@@ -1209,139 +1207,139 @@ msgstr "Unten Rechts"
msgid "Edit Text Properties"
msgstr "Text Eigenschaften bearbeiten"
-#: gschem/src/x_dialog.c:471
+#: gschem/src/x_dialog.c:472
msgid "<b>Text Content</b>"
msgstr "<b>Textinhalt</b>"
-#: gschem/src/x_dialog.c:507
+#: gschem/src/x_dialog.c:508
msgid "<b>Text Properties</b>"
msgstr "<b>Texteigenschaften</b>"
-#: gschem/src/x_dialog.c:522
+#: gschem/src/x_dialog.c:523
msgid "Color:"
msgstr "Farbe:"
-#: gschem/src/x_dialog.c:529
+#: gschem/src/x_dialog.c:530
msgid "Size:"
msgstr "Grö�e:"
-#: gschem/src/x_dialog.c:538
+#: gschem/src/x_dialog.c:539
msgid "Alignment:"
msgstr "Ausrichtung:"
-#: gschem/src/x_dialog.c:587
+#: gschem/src/x_dialog.c:588
msgid "Solid"
msgstr "Durchgehend"
-#: gschem/src/x_dialog.c:588
+#: gschem/src/x_dialog.c:589
msgid "Dotted"
msgstr "Gepunktet"
-#: gschem/src/x_dialog.c:589
+#: gschem/src/x_dialog.c:590
msgid "Dashed"
msgstr "Gestrichelt"
-#: gschem/src/x_dialog.c:590
+#: gschem/src/x_dialog.c:591
msgid "Center"
msgstr "StrichPunkt"
-#: gschem/src/x_dialog.c:591
+#: gschem/src/x_dialog.c:592
msgid "Phantom"
msgstr "StrichZweiPunkt"
-#: gschem/src/x_dialog.c:592 gschem/src/x_dialog.c:689
-#: gschem/src/x_dialog.c:698 gschem/src/x_dialog.c:707
-#: gschem/src/x_dialog.c:808 gschem/src/x_dialog.c:810
-#: gschem/src/x_dialog.c:812 gschem/src/x_dialog.c:1038
-#: gschem/src/x_dialog.c:1141 gschem/src/x_dialog.c:1150
-#: gschem/src/x_dialog.c:1159 gschem/src/x_dialog.c:1168
-#: gschem/src/x_dialog.c:1177 gschem/src/x_dialog.c:1290
-#: gschem/src/x_dialog.c:1292 gschem/src/x_dialog.c:1294
-#: gschem/src/x_dialog.c:1296 gschem/src/x_dialog.c:1298
+#: gschem/src/x_dialog.c:593 gschem/src/x_dialog.c:690
+#: gschem/src/x_dialog.c:699 gschem/src/x_dialog.c:708
+#: gschem/src/x_dialog.c:809 gschem/src/x_dialog.c:811
+#: gschem/src/x_dialog.c:813 gschem/src/x_dialog.c:1039
+#: gschem/src/x_dialog.c:1142 gschem/src/x_dialog.c:1151
+#: gschem/src/x_dialog.c:1160 gschem/src/x_dialog.c:1169
+#: gschem/src/x_dialog.c:1178 gschem/src/x_dialog.c:1291
+#: gschem/src/x_dialog.c:1293 gschem/src/x_dialog.c:1295
+#: gschem/src/x_dialog.c:1297 gschem/src/x_dialog.c:1299
msgid "*unchanged*"
msgstr "*unverändert*"
-#: gschem/src/x_dialog.c:916
+#: gschem/src/x_dialog.c:917
msgid "Edit Line Width & Type"
msgstr "Linieneigenschaften bearbeiten"
-#: gschem/src/x_dialog.c:955 gschem/src/x_print.c:307
+#: gschem/src/x_dialog.c:956 gschem/src/x_print.c:307
msgid "Type:"
msgstr "Typ:"
-#: gschem/src/x_dialog.c:959
+#: gschem/src/x_dialog.c:960
msgid "Width:"
msgstr "Breite:"
-#: gschem/src/x_dialog.c:963
+#: gschem/src/x_dialog.c:964
msgid "Dash Length:"
msgstr "Linienlänge:"
-#: gschem/src/x_dialog.c:967
+#: gschem/src/x_dialog.c:968
msgid "Dash Space:"
msgstr "Linienlücke:"
-#: gschem/src/x_dialog.c:1034
+#: gschem/src/x_dialog.c:1035
msgid "Hollow"
msgstr "Leer"
-#: gschem/src/x_dialog.c:1035
+#: gschem/src/x_dialog.c:1036
msgid "Filled"
msgstr "Gefüllt"
-#: gschem/src/x_dialog.c:1036
+#: gschem/src/x_dialog.c:1037
msgid "Mesh"
msgstr "Gitter"
-#: gschem/src/x_dialog.c:1037
+#: gschem/src/x_dialog.c:1038
msgid "Hatch"
msgstr "Schraffiert"
-#: gschem/src/x_dialog.c:1406
+#: gschem/src/x_dialog.c:1407
msgid "Edit Fill Type"
msgstr "Editiere Füllmuster"
-#: gschem/src/x_dialog.c:1444
+#: gschem/src/x_dialog.c:1446
msgid "Fill Type:"
msgstr "Füllmuster:"
-#: gschem/src/x_dialog.c:1448
+#: gschem/src/x_dialog.c:1450
msgid "Line Width:"
msgstr "Linienbreite:"
-#: gschem/src/x_dialog.c:1452
+#: gschem/src/x_dialog.c:1454
msgid "Angle 1:"
msgstr "Winkel 1:"
-#: gschem/src/x_dialog.c:1456
+#: gschem/src/x_dialog.c:1458
msgid "Pitch 1:"
msgstr "Abstand 1:"
-#: gschem/src/x_dialog.c:1460
+#: gschem/src/x_dialog.c:1462
msgid "Angle 2:"
msgstr "Winkel 2:"
-#: gschem/src/x_dialog.c:1464
+#: gschem/src/x_dialog.c:1466
msgid "Pitch 2:"
msgstr "Abstand 2:"
-#: gschem/src/x_dialog.c:1591
+#: gschem/src/x_dialog.c:1593
msgid "Arc Params"
msgstr "Bogen Parameter"
-#: gschem/src/x_dialog.c:1631
+#: gschem/src/x_dialog.c:1634
msgid "Arc Radius:"
msgstr "Bogen Radius:"
-#: gschem/src/x_dialog.c:1639
+#: gschem/src/x_dialog.c:1642
msgid "Start Angle:"
msgstr "Start Winkel:"
-#: gschem/src/x_dialog.c:1647
+#: gschem/src/x_dialog.c:1650
msgid "Degrees of Sweep:"
msgstr "Ã?ffnungswinkel:"
-#: gschem/src/x_dialog.c:1764
+#: gschem/src/x_dialog.c:1768
msgid ""
"Offset to translate?\n"
"(0 for origin)"
@@ -1349,186 +1347,186 @@ msgstr ""
"Wie weit soll verschoben werden?\n"
"(0 verschiebt zum Ursprung)"
-#: gschem/src/x_dialog.c:1832
+#: gschem/src/x_dialog.c:1836
msgid "Text Size"
msgstr "Text Grö�e"
-#: gschem/src/x_dialog.c:1862
+#: gschem/src/x_dialog.c:1866
msgid "Enter new text size:"
msgstr "Neue Textgrö�e eingeben:"
-#: gschem/src/x_dialog.c:1938
+#: gschem/src/x_dialog.c:1942
msgid "Snap Size"
msgstr "Rasterabstand"
-#: gschem/src/x_dialog.c:1968
+#: gschem/src/x_dialog.c:1972
msgid "Enter new snap grid spacing:"
msgstr "Neuen Rasterabstand eingeben"
-#: gschem/src/x_dialog.c:2045
+#: gschem/src/x_dialog.c:2049
msgid "Edit slot number"
msgstr "Editiere slot Nummer"
-#: gschem/src/x_dialog.c:2076
+#: gschem/src/x_dialog.c:2080
msgid "Edit slot number:"
msgstr "Editiere slot Nummer:"
-#: gschem/src/x_dialog.c:2117
+#: gschem/src/x_dialog.c:2121
#, c-format
msgid "%s%s (%s)"
msgstr ""
-#: gschem/src/x_dialog.c:2140
+#: gschem/src/x_dialog.c:2144
msgid "About gschem"
msgstr "Ã?ber gschem"
-#: gschem/src/x_dialog.c:2141
+#: gschem/src/x_dialog.c:2145
msgid "gEDA: GPL Electronic Design Automation"
msgstr ""
-#: gschem/src/x_dialog.c:2142
+#: gschem/src/x_dialog.c:2146
msgid ""
"Copyright © 1998-2009 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
"Copyright © 1998-2009 gEDA Contributors (see ChangeLog for details)"
msgstr ""
-#: gschem/src/x_dialog.c:2201
+#: gschem/src/x_dialog.c:2205
msgid "Coords"
msgstr "Koordinaten"
-#: gschem/src/x_dialog.c:2222
+#: gschem/src/x_dialog.c:2226
msgid "Screen"
msgstr "Bildschirm (Pixel)"
-#: gschem/src/x_dialog.c:2231
+#: gschem/src/x_dialog.c:2235
msgid "World"
msgstr "Global (0.001\")"
-#: gschem/src/x_dialog.c:2270
+#: gschem/src/x_dialog.c:2274
msgid "Background"
msgstr "Hintergrund"
-#: gschem/src/x_dialog.c:2276
+#: gschem/src/x_dialog.c:2280
msgid "Net endpoint"
msgstr "Netz-Endemarkierung"
-#: gschem/src/x_dialog.c:2279
+#: gschem/src/x_dialog.c:2283
msgid "Graphic"
msgstr "Graphik"
-#: gschem/src/x_dialog.c:2288
+#: gschem/src/x_dialog.c:2292
msgid "Logic bubble"
msgstr "Logik Markierung"
-#: gschem/src/x_dialog.c:2291
+#: gschem/src/x_dialog.c:2295
msgid "Grid point"
msgstr "Rasterpunkt"
-#: gschem/src/x_dialog.c:2294
+#: gschem/src/x_dialog.c:2298
msgid "Detached attribute"
msgstr "Attribut ablösen"
-#: gschem/src/x_dialog.c:2297 gschem/src/x_window.c:383
+#: gschem/src/x_dialog.c:2301 gschem/src/x_window.c:383
msgid "Text"
msgstr "Text"
-#: gschem/src/x_dialog.c:2303
+#: gschem/src/x_dialog.c:2307
msgid "Selection"
msgstr "Auswahl"
-#: gschem/src/x_dialog.c:2306
+#: gschem/src/x_dialog.c:2310
msgid "Bounding box"
msgstr "Randmarkierung"
-#: gschem/src/x_dialog.c:2309
+#: gschem/src/x_dialog.c:2313
msgid "Zoom box"
msgstr "Ausschnitt wählen"
-#: gschem/src/x_dialog.c:2318
+#: gschem/src/x_dialog.c:2322
msgid "Output background"
msgstr "Ausgabehintergrund"
-#: gschem/src/x_dialog.c:2321
+#: gschem/src/x_dialog.c:2325
msgid "Net junction"
msgstr "Netzverbindung"
-#: gschem/src/x_dialog.c:2324
+#: gschem/src/x_dialog.c:2328
msgid "Mesh grid major"
msgstr "Grobes Gitternetz"
-#: gschem/src/x_dialog.c:2327
+#: gschem/src/x_dialog.c:2331
msgid "Mesh grid minor"
msgstr "Feines Gitternetz"
-#: gschem/src/x_dialog.c:2330
+#: gschem/src/x_dialog.c:2334
msgid "Unknown"
msgstr "Unbekannt"
-#: gschem/src/x_dialog.c:2481
+#: gschem/src/x_dialog.c:2485
#, c-format
msgid "ERROR: NULL object in color_edit_dialog_apply!\n"
msgstr "FEHLER: NULL Objekt innerhalb von color_edit_dialog_apply!\n"
-#: gschem/src/x_dialog.c:2525
+#: gschem/src/x_dialog.c:2529
msgid "Color Edit"
msgstr "Farbe bearbeiten"
-#: gschem/src/x_dialog.c:2556
+#: gschem/src/x_dialog.c:2560
msgid "Object color:"
msgstr "Objekt Farbe:"
-#: gschem/src/x_dialog.c:2614
+#: gschem/src/x_dialog.c:2618
msgid "Hotkeys"
msgstr "Tastenkürzel"
-#: gschem/src/x_dialog.c:2678
+#: gschem/src/x_dialog.c:2682
msgid "Function"
msgstr "Funktion"
-#: gschem/src/x_dialog.c:2685
+#: gschem/src/x_dialog.c:2689
msgid "Keystroke(s)"
msgstr "Tastenkürzel"
-#: gschem/src/x_dialog.c:2991
+#: gschem/src/x_dialog.c:2995
msgid "Find Text"
msgstr "Suche Text"
-#: gschem/src/x_dialog.c:3022
+#: gschem/src/x_dialog.c:3026
msgid "Text to find:"
msgstr "Zu suchender Text:"
-#: gschem/src/x_dialog.c:3032
+#: gschem/src/x_dialog.c:3036
msgid "descend into hierarchy"
msgstr "In der Hierachie hinabsteigen"
-#: gschem/src/x_dialog.c:3097
+#: gschem/src/x_dialog.c:3101
msgid "Hide Text"
msgstr "Verberge Text"
-#: gschem/src/x_dialog.c:3128
+#: gschem/src/x_dialog.c:3132
msgid "Hide text starting with:"
msgstr "Verberge Text, der beginnt mit:"
-#: gschem/src/x_dialog.c:3197
+#: gschem/src/x_dialog.c:3201
msgid "Show Text"
msgstr "Zeige Text"
-#: gschem/src/x_dialog.c:3228
+#: gschem/src/x_dialog.c:3232
msgid "Show text starting with:"
msgstr "Zeige Text, der beginnt mit:"
-#: gschem/src/x_dialog.c:3685
+#: gschem/src/x_dialog.c:3689
msgid "S_elect the schematics you want to save:"
msgstr "_Wählen Sie die zu speichernden Seiten:"
-#: gschem/src/x_dialog.c:3779
+#: gschem/src/x_dialog.c:3784
#, c-format
msgid "Save the changes to schematic \"%s\" before closing?"
msgstr ""
"Sollen die Ã?nderungen am Schaltplan \"%s\" vor dem SchlieÃ?en gespeichert "
"werden?"
-#: gschem/src/x_dialog.c:3785
+#: gschem/src/x_dialog.c:3790
#, c-format
msgid ""
"There are %d schematics with unsaved changes. Save changes before closing?"
@@ -1536,15 +1534,15 @@ msgstr ""
"Es gibt %d ungesicherte Schaltpläne. Sollen die �nderungen vor dem Schlie�en "
"gespeichert werden?"
-#: gschem/src/x_dialog.c:3814
+#: gschem/src/x_dialog.c:3819
msgid "If you don't save, all your changes will be permanently lost."
msgstr "Wenn Sie nicht speichern, werden Sie alle Ã?nderungen verlieren."
-#: gschem/src/x_dialog.c:3834
+#: gschem/src/x_dialog.c:3839
msgid "_Close without saving"
msgstr "SchlieÃ?en _ohne Speichern"
-#: gschem/src/x_dialog.c:4170
+#: gschem/src/x_dialog.c:4175
#, c-format
msgid ""
"<span weight=\"bold\" size=\"larger\">The input attribute \"%s\" is invalid\n"
@@ -1562,19 +1560,19 @@ msgstr ""
"Der Name darf nicht mit einem Leerzeichen enden.\n"
"Der Wert darf nicht mit einem Leerzeichen beginnen."
-#: gschem/src/x_dialog.c:4172
+#: gschem/src/x_dialog.c:4177
msgid "Invalid Attribute"
msgstr "Fehlerhaftes Attribut"
-#: gschem/src/x_dialog.c:4208
+#: gschem/src/x_dialog.c:4213
msgid "Pin type"
msgstr "Pin Typ"
-#: gschem/src/x_dialog.c:4232
+#: gschem/src/x_dialog.c:4237
msgid "Net pin"
msgstr "Netz Pin"
-#: gschem/src/x_dialog.c:4234
+#: gschem/src/x_dialog.c:4239
msgid "Bus pin (graphical)"
msgstr "Bus Pin (graphisch)"
@@ -1674,13 +1672,13 @@ msgstr "Bild Format"
msgid "Write image..."
msgstr "Speichere Bild..."
-#: gschem/src/x_log.c:188
+#: gschem/src/x_log.c:209
msgid "** Invalid UTF-8 in log message. See stderr or gschem.log.\n"
msgstr ""
"** Diese Fehlermeldung enthält eine ungültige UTF-8 Kodierung. Siehe gschem."
"log und stderr.\n"
-#: gschem/src/x_log.c:256
+#: gschem/src/x_log.c:288
msgid "Status"
msgstr "Status"
@@ -1756,74 +1754,65 @@ msgstr "/zum Symbol hinab"
msgid "/Up"
msgstr "/Hinauf"
-#: gschem/src/x_menus.c:321
+#: gschem/src/x_menus.c:323
#, c-format
msgid "Tried to set the sensitivity on non-existent menu item '%s'\n"
msgstr ""
"Es wurde versucht die Empfindlichkeit des nicht existenten Menueintrags '%s' "
"zu setzen\n"
-#: gschem/src/x_menus.c:345
+#: gschem/src/x_menus.c:347
msgid "Popup_menu_item_factory doesn't exist!\n"
msgstr "Popup_menu_item_factory existiert nicht\n"
-#: gschem/src/x_menus.c:358
+#: gschem/src/x_menus.c:360
msgid "Tried to set the sensitivity on a non-existent popup menu_item\n"
msgstr ""
"Es wurde versucht die Sensibilität für einen nichtexistierenden Menueintrag "
"zu setzen\n"
-#: gschem/src/x_menus.c:438
-#, c-format
-msgid "Couldn't open file %s\n"
-msgstr "Konnte Datei %s nicht öffnen\n"
-
-#: gschem/src/x_menus.c:495
-msgid "Clear"
-msgstr "Entfernen"
-
-#: gschem/src/x_multiattrib.c:911
+#: gschem/src/x_multiattrib.c:915
msgid "Attributes with empty name are not allowed. Please set a name."
msgstr ""
"Attribute mit leerem Namen sind nicht erlaubt. Gib bitte einen Namen ein."
-#: gschem/src/x_multiattrib.c:1456
+#: gschem/src/x_multiattrib.c:1468
msgid "Show Value only"
msgstr "Nur Wert anzeigen"
-#: gschem/src/x_multiattrib.c:1458
+#: gschem/src/x_multiattrib.c:1470
msgid "Show Name only"
msgstr "Nur Name anzeigen"
-#: gschem/src/x_multiattrib.c:1486
+#: gschem/src/x_multiattrib.c:1498
msgid "Promote"
msgstr "Einsetzen"
-#: gschem/src/x_multiattrib.c:1490
+#: gschem/src/x_multiattrib.c:1502
msgid "Duplicate"
msgstr "Duplizieren"
-#: gschem/src/x_multiattrib.c:1708
+#: gschem/src/x_multiattrib.c:1719
msgid "Edit Attributes"
msgstr "Attribute bearbeiten"
-#: gschem/src/x_multiattrib.c:1826
+#: gschem/src/x_multiattrib.c:1837
msgid "Vis?"
msgstr "Sichtbar?"
-#: gschem/src/x_multiattrib.c:1844
+#: gschem/src/x_multiattrib.c:1855
msgid "N"
msgstr "Name"
-#: gschem/src/x_multiattrib.c:1862
+#: gschem/src/x_multiattrib.c:1873
msgid "V"
msgstr "Wert"
-#: gschem/src/x_multiattrib.c:1884
+#: gschem/src/x_multiattrib.c:1895
msgid "Show inherited attributes"
msgstr "geerbte Attribute anzeigen"
-#: gschem/src/x_multiattrib.c:1900
+#: gschem/src/x_multiattrib.c:1911
msgid "Add Attribute"
msgstr "Attribut hinzufügen"
@@ -1847,23 +1836,23 @@ msgstr "Seite schlieÃ?en"
msgid "Discard Page"
msgstr "Seite ablegen"
-#: gschem/src/x_pagesel.c:376
+#: gschem/src/x_pagesel.c:375
msgid "Page Manager"
msgstr "Seiten Manager"
-#: gschem/src/x_pagesel.c:432
+#: gschem/src/x_pagesel.c:431
msgid "Filename"
msgstr "Dateiname"
-#: gschem/src/x_pagesel.c:448
+#: gschem/src/x_pagesel.c:447
msgid "Changed"
msgstr "Geändert"
-#: gschem/src/x_pagesel.c:468
+#: gschem/src/x_pagesel.c:467
msgid "Right click on the filename for more options..."
msgstr "Rechtsklick auf den Dateinamen für mehr Optionen..."
-#: gschem/src/x_preview.c:234
+#: gschem/src/x_preview.c:233
msgid "Preview Buffer"
msgstr "Vorschau"
@@ -1919,16 +1908,16 @@ msgstr "Datei:"
msgid "Command:"
msgstr "Befehl:"
-#: gschem/src/x_print.c:741
+#: gschem/src/x_print.c:745
msgid "No print destination specified\n"
msgstr "Das Ziel für den Ausdruck fehlt\n"
-#: gschem/src/x_print.c:748
+#: gschem/src/x_print.c:752
#, c-format
msgid "Cannot print current schematic to [%s]\n"
msgstr "Aktueller Schaltplan kann nicht in [%s] gedruckt werden.\n"
-#: gschem/src/x_print.c:757
+#: gschem/src/x_print.c:761
#, c-format
msgid ""
"Error printing to file '%s'\n"
@@ -1937,7 +1926,7 @@ msgstr ""
"Fehler beim Drucken in die Datei '%s'\n"
"Nähere Informationen sind im Log-Fenster."
-#: gschem/src/x_print.c:764
+#: gschem/src/x_print.c:768
#, c-format
msgid "Printed current schematic to [%s]\n"
msgstr "Aktueller Schalplan in [%s] ausgedruckt\n"
@@ -1946,6 +1935,11 @@ msgstr "Aktueller Schalplan in [%s] ausgedruckt\n"
msgid "Execute Script..."
msgstr "S_kript ausführen..."
+#: gschem/src/x_script.c:66
+#, c-format
+msgid "Executing guile script [%s]\n"
+msgstr "Führe guile scipt aus [%s]\n"
+
#: gschem/src/x_window.c:81
#, c-format
msgid "Couldn't allocate gc\n"
@@ -2061,35 +2055,35 @@ msgstr "Eine Datei konnte nicht geladen werden"
msgid "New file [%s]\n"
msgstr "Neue Datei [%s]\n"
-#: gschem/src/x_window.c:857
+#: gschem/src/x_window.c:855
#, c-format
msgid "Could NOT save page [%s]\n"
msgstr "Die Seite [%s] konnte nicht gespeichert werden.\n"
-#: gschem/src/x_window.c:858
+#: gschem/src/x_window.c:856
msgid "Error while trying to save"
msgstr "Fehler während des Speicherns"
-#: gschem/src/x_window.c:867
+#: gschem/src/x_window.c:865
#, c-format
msgid "Saved as [%s]\n"
msgstr "Gespeichert unter [%s]\n"
-#: gschem/src/x_window.c:869
+#: gschem/src/x_window.c:867
#, c-format
msgid "Saved [%s]\n"
msgstr "Gespeichert [%s]\n"
-#: gschem/src/x_window.c:871
+#: gschem/src/x_window.c:869
msgid "Saved"
msgstr "Gespeichert"
-#: gschem/src/x_window.c:945
+#: gschem/src/x_window.c:943
#, c-format
msgid "Discarding page [%s]\n"
msgstr "SchlieÃ?e Schaltplan [%s]\n"
-#: gschem/src/x_window.c:945
+#: gschem/src/x_window.c:943
#, c-format
msgid "Closing [%s]\n"
msgstr "SchlieÃ?e [%s]\n"
@@ -2132,7 +2126,7 @@ msgstr "Speichern _unter"
msgid "Save All"
msgstr "_Alles speichern"
-#: gschem/lib/system-gschemrc.scm:1386 gschem/lib/system-gschemrc.scm:1477
+#: gschem/lib/system-gschemrc.scm:1386 gschem/lib/system-gschemrc.scm:1478
msgid "_Revert"
msgstr "Neu _laden"
@@ -2144,7 +2138,7 @@ msgstr "_Drucken"
msgid "Write _image..."
msgstr "Bild e_xportieren..."
-#: gschem/lib/system-gschemrc.scm:1393 gschem/lib/system-gschemrc.scm:1478
+#: gschem/lib/system-gschemrc.scm:1393 gschem/lib/system-gschemrc.scm:1479
msgid "_Close"
msgstr "S_chlieÃ?en"
@@ -2176,391 +2170,435 @@ msgstr "_Einfügen"
msgid "_Delete"
msgstr "_Löschen"
-#: gschem/lib/system-gschemrc.scm:1412
+#: gschem/lib/system-gschemrc.scm:1409
+#, fuzzy
+msgid "Select All"
+msgstr "Auswählen"
+
+#: gschem/lib/system-gschemrc.scm:1410
+#, fuzzy
+msgid "Deselect"
+msgstr "Auswählen"
+
+#: gschem/lib/system-gschemrc.scm:1414
msgid "Rotate 90 Mode"
msgstr "Dreh Modus (90°)"
-#: gschem/lib/system-gschemrc.scm:1415
+#: gschem/lib/system-gschemrc.scm:1417
msgid "Edit..."
msgstr "Bearbeiten..."
-#: gschem/lib/system-gschemrc.scm:1416
+#: gschem/lib/system-gschemrc.scm:1418
msgid "Edit Text..."
msgstr "Text bearbeiten..."
-#: gschem/lib/system-gschemrc.scm:1417
+#: gschem/lib/system-gschemrc.scm:1419
msgid "Slot..."
msgstr "Slot..."
-#: gschem/lib/system-gschemrc.scm:1418
+#: gschem/lib/system-gschemrc.scm:1420
msgid "Color..."
msgstr "Farbe..."
-#: gschem/lib/system-gschemrc.scm:1419
+#: gschem/lib/system-gschemrc.scm:1421
msgid "Line Width & Type..."
msgstr "Linieneigenschaften..."
-#: gschem/lib/system-gschemrc.scm:1420
+#: gschem/lib/system-gschemrc.scm:1422
msgid "Fill Type..."
msgstr "Füllung..."
-#: gschem/lib/system-gschemrc.scm:1421
+#: gschem/lib/system-gschemrc.scm:1423
msgid "Symbol Translate..."
msgstr "Symbol transferieren..."
-#: gschem/lib/system-gschemrc.scm:1425
+#: gschem/lib/system-gschemrc.scm:1427
msgid "Invoke Macro"
msgstr "Makro ausführen"
-#: gschem/lib/system-gschemrc.scm:1426
+#: gschem/lib/system-gschemrc.scm:1428
msgid "Embed Component/Picture"
msgstr "Bauteil/Bild einbetten"
-#: gschem/lib/system-gschemrc.scm:1427
+#: gschem/lib/system-gschemrc.scm:1429
msgid "Unembed Component/Picture"
msgstr "Bauteil/Bild ausbetten"
-#: gschem/lib/system-gschemrc.scm:1428
+#: gschem/lib/system-gschemrc.scm:1430
msgid "Update Component"
msgstr "Bauteil aktualisieren"
-#: gschem/lib/system-gschemrc.scm:1429
+#: gschem/lib/system-gschemrc.scm:1431
msgid "Show/Hide Inv Text"
msgstr "Zeige/Verberge unsichtbaren Text"
-#: gschem/lib/system-gschemrc.scm:1430
-msgid "Make Inv Text Vis"
-msgstr "Text sichtbar machen"
-
-#: gschem/lib/system-gschemrc.scm:1436
+#: gschem/lib/system-gschemrc.scm:1437
msgid "Copy into 1"
msgstr "Kopiere in 1"
-#: gschem/lib/system-gschemrc.scm:1437
+#: gschem/lib/system-gschemrc.scm:1438
msgid "Copy into 2"
msgstr "Kopiere in 2"
-#: gschem/lib/system-gschemrc.scm:1438
+#: gschem/lib/system-gschemrc.scm:1439
msgid "Copy into 3"
msgstr "Kopiere in 3"
-#: gschem/lib/system-gschemrc.scm:1439
+#: gschem/lib/system-gschemrc.scm:1440
msgid "Copy into 4"
msgstr "Kopiere in 4"
-#: gschem/lib/system-gschemrc.scm:1440
+#: gschem/lib/system-gschemrc.scm:1441
msgid "Copy into 5"
msgstr "Kopiere in 5"
-#: gschem/lib/system-gschemrc.scm:1441
+#: gschem/lib/system-gschemrc.scm:1442
msgid "Cut into 1"
msgstr "Ausschneiden in 1"
-#: gschem/lib/system-gschemrc.scm:1442
+#: gschem/lib/system-gschemrc.scm:1443
msgid "Cut into 2"
msgstr "Ausschneiden in 2"
-#: gschem/lib/system-gschemrc.scm:1443
+#: gschem/lib/system-gschemrc.scm:1444
msgid "Cut into 3"
msgstr "Ausschneiden in 3"
-#: gschem/lib/system-gschemrc.scm:1444
+#: gschem/lib/system-gschemrc.scm:1445
msgid "Cut into 4"
msgstr "Ausschneiden in 4"
-#: gschem/lib/system-gschemrc.scm:1445
+#: gschem/lib/system-gschemrc.scm:1446
msgid "Cut into 5"
msgstr "Ausschneiden in 5"
-#: gschem/lib/system-gschemrc.scm:1446
+#: gschem/lib/system-gschemrc.scm:1447
msgid "Paste from 1"
msgstr "Einfügen aus 1"
-#: gschem/lib/system-gschemrc.scm:1447
+#: gschem/lib/system-gschemrc.scm:1448
msgid "Paste from 2"
msgstr "Einfügen aus 2"
-#: gschem/lib/system-gschemrc.scm:1448
+#: gschem/lib/system-gschemrc.scm:1449
msgid "Paste from 3"
msgstr "Einfügen aus 3"
-#: gschem/lib/system-gschemrc.scm:1449
+#: gschem/lib/system-gschemrc.scm:1450
msgid "Paste from 4"
msgstr "Einfügen aus 4"
-#: gschem/lib/system-gschemrc.scm:1450
+#: gschem/lib/system-gschemrc.scm:1451
msgid "Paste from 5"
msgstr "Einfügen aus 5"
-#: gschem/lib/system-gschemrc.scm:1456
+#: gschem/lib/system-gschemrc.scm:1457
msgid "_Redraw"
msgstr "_Neu Zeichnen"
-#: gschem/lib/system-gschemrc.scm:1457
+#: gschem/lib/system-gschemrc.scm:1458
msgid "_Pan"
msgstr "Ausschnitt _wechseln"
-#: gschem/lib/system-gschemrc.scm:1458
+#: gschem/lib/system-gschemrc.scm:1459
msgid "Zoom _Box"
msgstr "_Rechteck auswählen"
-#: gschem/lib/system-gschemrc.scm:1459
+#: gschem/lib/system-gschemrc.scm:1460
msgid "Zoom _Extents"
msgstr "_Alles anzeigen"
-#: gschem/lib/system-gschemrc.scm:1460
+#: gschem/lib/system-gschemrc.scm:1461
msgid "Zoom _In"
msgstr "Ver_grö�ern"
-#: gschem/lib/system-gschemrc.scm:1461
+#: gschem/lib/system-gschemrc.scm:1462
msgid "Zoom _Out"
msgstr "Ver_kleinern"
-#: gschem/lib/system-gschemrc.scm:1462
+#: gschem/lib/system-gschemrc.scm:1463
msgid "Zoom _Full"
msgstr "Gesamte _Zeichenfläche"
-#: gschem/lib/system-gschemrc.scm:1464
+#: gschem/lib/system-gschemrc.scm:1465
msgid "_Dark color scheme"
msgstr "_Dunkles Farbschema"
-#: gschem/lib/system-gschemrc.scm:1465
+#: gschem/lib/system-gschemrc.scm:1466
msgid "_Light color scheme"
msgstr "_Helles Farbschema"
-#: gschem/lib/system-gschemrc.scm:1466
+#: gschem/lib/system-gschemrc.scm:1467
#, fuzzy
msgid "B_W color scheme"
msgstr "_Dunkles Farbschema"
-#: gschem/lib/system-gschemrc.scm:1473
+#: gschem/lib/system-gschemrc.scm:1474
msgid "_Manager..."
msgstr "_Manager..."
-#: gschem/lib/system-gschemrc.scm:1474
+#: gschem/lib/system-gschemrc.scm:1475
msgid "_Previous"
msgstr "_Vorherige"
-#: gschem/lib/system-gschemrc.scm:1475
+#: gschem/lib/system-gschemrc.scm:1476
msgid "_Next"
msgstr "_Nächste"
-#: gschem/lib/system-gschemrc.scm:1476
+#: gschem/lib/system-gschemrc.scm:1477
msgid "Ne_w"
msgstr "N_eu"
-#: gschem/lib/system-gschemrc.scm:1480
+#: gschem/lib/system-gschemrc.scm:1481
msgid "_Discard"
msgstr "_Ablegen"
-#: gschem/lib/system-gschemrc.scm:1486
+#: gschem/lib/system-gschemrc.scm:1487
msgid "_Component..."
msgstr "_Bauteil..."
-#: gschem/lib/system-gschemrc.scm:1487
+#: gschem/lib/system-gschemrc.scm:1488
msgid "_Net"
msgstr "_Netz"
-#: gschem/lib/system-gschemrc.scm:1488
+#: gschem/lib/system-gschemrc.scm:1489
msgid "B_us"
msgstr "B_us"
-#: gschem/lib/system-gschemrc.scm:1489
+#: gschem/lib/system-gschemrc.scm:1490
msgid "_Attribute..."
msgstr "_Attribut"
-#: gschem/lib/system-gschemrc.scm:1490
+#: gschem/lib/system-gschemrc.scm:1491
msgid "_Text..."
msgstr "_Text"
-#: gschem/lib/system-gschemrc.scm:1492
+#: gschem/lib/system-gschemrc.scm:1493
msgid "_Line"
msgstr "_Linie"
-#: gschem/lib/system-gschemrc.scm:1493
+#: gschem/lib/system-gschemrc.scm:1494
msgid "_Box"
msgstr "_Rechteck"
-#: gschem/lib/system-gschemrc.scm:1494
+#: gschem/lib/system-gschemrc.scm:1495
msgid "C_ircle"
msgstr "_Kreis"
-#: gschem/lib/system-gschemrc.scm:1495
+#: gschem/lib/system-gschemrc.scm:1496
msgid "A_rc"
msgstr "Kreisb_ogen"
-#: gschem/lib/system-gschemrc.scm:1496
+#: gschem/lib/system-gschemrc.scm:1497
msgid "_Pin"
msgstr "_Pin"
-#: gschem/lib/system-gschemrc.scm:1497
+#: gschem/lib/system-gschemrc.scm:1498
msgid "Pictu_re..."
msgstr "B_ild..."
-#: gschem/lib/system-gschemrc.scm:1503
+#: gschem/lib/system-gschemrc.scm:1504
msgid "_Down Schematic"
msgstr "Hinab zum _Schaltplan"
-#: gschem/lib/system-gschemrc.scm:1504
+#: gschem/lib/system-gschemrc.scm:1505
msgid "Down _Symbol"
msgstr "Hinab zum S_ymbol"
-#: gschem/lib/system-gschemrc.scm:1505
+#: gschem/lib/system-gschemrc.scm:1506
msgid "_Up"
msgstr "_Hinauf"
-#: gschem/lib/system-gschemrc.scm:1506
+#: gschem/lib/system-gschemrc.scm:1507
msgid "D_ocumentation..."
msgstr "_Dokumentation"
-#: gschem/lib/system-gschemrc.scm:1512
+#: gschem/lib/system-gschemrc.scm:1513
msgid "_Attach"
msgstr "_Anbringen"
-#: gschem/lib/system-gschemrc.scm:1513
+#: gschem/lib/system-gschemrc.scm:1514
msgid "_Detach"
msgstr "_Loslösen"
-#: gschem/lib/system-gschemrc.scm:1514
+#: gschem/lib/system-gschemrc.scm:1515
msgid "Show _Value"
msgstr "_Wert anzeigen"
-#: gschem/lib/system-gschemrc.scm:1515
+#: gschem/lib/system-gschemrc.scm:1516
msgid "Show _Name"
msgstr "_Name anzeigen"
-#: gschem/lib/system-gschemrc.scm:1516
+#: gschem/lib/system-gschemrc.scm:1517
msgid "Show _Both"
msgstr "_Beide anzeigen"
-#: gschem/lib/system-gschemrc.scm:1517
+#: gschem/lib/system-gschemrc.scm:1518
msgid "_Toggle Visibility"
msgstr "Sichtbarkeit _umschalten"
-#: gschem/lib/system-gschemrc.scm:1519
+#: gschem/lib/system-gschemrc.scm:1520
msgid "_Find Specific Text..."
msgstr "Text _suchen..."
-#: gschem/lib/system-gschemrc.scm:1520
+#: gschem/lib/system-gschemrc.scm:1521
msgid "_Hide Specific Text..."
msgstr "Text _verbergen..."
-#: gschem/lib/system-gschemrc.scm:1521
+#: gschem/lib/system-gschemrc.scm:1522
msgid "_Show Specific Text..."
msgstr "Text an_zeigen..."
-#: gschem/lib/system-gschemrc.scm:1522
+#: gschem/lib/system-gschemrc.scm:1523
msgid "A_utonumber Text..."
msgstr "Text _durchnummerieren"
-#: gschem/lib/system-gschemrc.scm:1528
+#: gschem/lib/system-gschemrc.scm:1529
msgid "_Text Size..."
msgstr "_Textgrö�e"
-#: gschem/lib/system-gschemrc.scm:1529
+#: gschem/lib/system-gschemrc.scm:1530
msgid "Cycle _grid styles"
msgstr "G_itterstil wechseln"
-#: gschem/lib/system-gschemrc.scm:1530
+#: gschem/lib/system-gschemrc.scm:1531
msgid "Toggle _Snap On/Off"
msgstr "_Raster umschalten"
-#: gschem/lib/system-gschemrc.scm:1531
+#: gschem/lib/system-gschemrc.scm:1532
msgid "Snap Grid S_pacing..."
msgstr "Raster_abstand..."
-#: gschem/lib/system-gschemrc.scm:1532
+#: gschem/lib/system-gschemrc.scm:1533
msgid "Scale _up Grid Spacing"
msgstr "Rasterabstand ver_grö�ern"
-#: gschem/lib/system-gschemrc.scm:1534
+#: gschem/lib/system-gschemrc.scm:1535
msgid "Scale _down Grid Spacing"
msgstr "Rasterabstand ver_kleinern"
-#: gschem/lib/system-gschemrc.scm:1536
+#: gschem/lib/system-gschemrc.scm:1537
msgid "Toggle _Outline/Box"
msgstr "_Umrissanzeige umschalten"
-#: gschem/lib/system-gschemrc.scm:1538
+#: gschem/lib/system-gschemrc.scm:1539
msgid "Toggle Net _Rubberband"
msgstr "_Netzgummifäden umschalten"
-#: gschem/lib/system-gschemrc.scm:1539
+#: gschem/lib/system-gschemrc.scm:1540
msgid "Toggle _Magnetic Net"
msgstr "_magnetischen Netzmodus umschalten"
-#: gschem/lib/system-gschemrc.scm:1540
+#: gschem/lib/system-gschemrc.scm:1541
msgid "Show _Log Window..."
msgstr "_Logfenster anzeigen"
-#: gschem/lib/system-gschemrc.scm:1542
+#: gschem/lib/system-gschemrc.scm:1543
msgid "Show _Coord Window..."
msgstr "K_oordinatenfenster..."
-#: gschem/lib/system-gschemrc.scm:1558
+#: gschem/lib/system-gschemrc.scm:1559
msgid "gEDA Docu_mentation..."
msgstr "gEDA _Dokumentation..."
-#: gschem/lib/system-gschemrc.scm:1559
+#: gschem/lib/system-gschemrc.scm:1560
msgid "gschem _FAQ..."
msgstr "gschem _FAQ..."
-#: gschem/lib/system-gschemrc.scm:1560
+#: gschem/lib/system-gschemrc.scm:1561
msgid "gEDA _Wiki..."
msgstr "gEDA _Wiki..."
-#: gschem/lib/system-gschemrc.scm:1561
+#: gschem/lib/system-gschemrc.scm:1562
msgid "Component D_ocumentation..."
msgstr "_Bauteil Dokumentation"
-#: gschem/lib/system-gschemrc.scm:1563
+#: gschem/lib/system-gschemrc.scm:1564
msgid "_Hotkeys..."
msgstr "_Tastenkürzel..."
-#: gschem/lib/system-gschemrc.scm:1564
+#: gschem/lib/system-gschemrc.scm:1565
msgid "_About..."
msgstr "_Info..."
-#: gschem/lib/system-gschemrc.scm:1570
+#: gschem/lib/system-gschemrc.scm:1571
msgid "_File"
msgstr "_Datei"
-#: gschem/lib/system-gschemrc.scm:1571
+#: gschem/lib/system-gschemrc.scm:1572
msgid "_Edit"
msgstr "_Bearbeiten"
-#: gschem/lib/system-gschemrc.scm:1572
+#: gschem/lib/system-gschemrc.scm:1573
msgid "_Buffer"
msgstr "_Puffer"
-#: gschem/lib/system-gschemrc.scm:1573
+#: gschem/lib/system-gschemrc.scm:1574
msgid "_View"
msgstr "_Ansicht"
-#: gschem/lib/system-gschemrc.scm:1574
+#: gschem/lib/system-gschemrc.scm:1575
msgid "_Page"
msgstr "_Seite"
-#: gschem/lib/system-gschemrc.scm:1575
+#: gschem/lib/system-gschemrc.scm:1576
msgid "_Add"
msgstr "_Einfügen"
-#: gschem/lib/system-gschemrc.scm:1576
+#: gschem/lib/system-gschemrc.scm:1577
msgid "Hie_rarchy"
msgstr "Hie_rarchie"
-#: gschem/lib/system-gschemrc.scm:1577
+#: gschem/lib/system-gschemrc.scm:1578
msgid "A_ttributes"
msgstr "A_ttribut"
-#: gschem/lib/system-gschemrc.scm:1578
+#: gschem/lib/system-gschemrc.scm:1579
msgid "_Options"
msgstr "_Optionen"
-#: gschem/lib/system-gschemrc.scm:1579
+#: gschem/lib/system-gschemrc.scm:1580
msgid "_Help"
msgstr "_Hilfe"
+#~ msgid "Scheme directory NOT set!\n"
+#~ msgstr "Das scheme Verzeichnis wurde nicht definiert!\n"
+
+#~ msgid "MakeVisible"
+#~ msgstr "Sichbar Machen"
+
+#~ msgid ""
+#~ "Usage: %s [OPTIONS] schematic_filename1 ... schematic_filenameN\n"
+#~ " -q Quiet mode\n"
+#~ " -v Verbose mode on\n"
+#~ " -r filename Rc filename\n"
+#~ " -s filename Script (guile) filename\n"
+#~ " -o filename Output filename (for printing)\n"
+#~ " -p Automatically place the window\n"
+#~ " -t Print stroke information\n"
+#~ " -h Help; this message\n"
+#~ "\n"
+#~ msgstr ""
+#~ "Aufruf: %s [Optionen] Schaltplan_Datei1 ... Schaltplan_DateiN\n"
+#~ " -q keine Standardausgabe\n"
+#~ " -v viele Standardausgaben\n"
+#~ " -r Dateiname Rc Dateiname\n"
+#~ " -s Dateiname Skript (guile) Dateiname\n"
+#~ " -o Dateiname Ausgabe Dateiname (für den Ausdruck)\n"
+#~ " -p Fenster automatisch platzieren\n"
+#~ " -t Tastaturkürzel ausgeben\n"
+#~ " -h Hilfe (diese Ausgabe)\n"
+#~ "\n"
+
+#~ msgid "Couldn't open file %s\n"
+#~ msgstr "Konnte Datei %s nicht öffnen\n"
+
+#~ msgid "Clear"
+#~ msgstr "Entfernen"
+
+#~ msgid "Make Inv Text Vis"
+#~ msgstr "Text sichtbar machen"
+
#~ msgid "Update Cues"
#~ msgstr "Ansicht aktualisieren (update cues)"
diff --git a/gschem/po/en_GB.po b/gschem/po/en_GB.po
index b2278b2..8d9a2f7 100644
--- a/gschem/po/en_GB.po
+++ b/gschem/po/en_GB.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2010-11-07 13:37+0000\n"
+"POT-Creation-Date: 2011-01-16 00:11-0500\n"
"PO-Revision-Date: 2010-02-11 03:01+0000\n"
"Last-Translator: Peter Clifton <pcjc2@xxxxxxxxx>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -22,17 +22,17 @@ msgstr ""
msgid "Zoom too small! Cannot zoom further.\n"
msgstr "Zoom too small! Cannot zoom further.\n"
-#: gschem/src/g_funcs.c:339 gschem/src/i_callbacks.c:68
+#: gschem/src/g_funcs.c:347 gschem/src/i_callbacks.c:68
#, c-format
msgid "Could not fork\n"
msgstr "Could not fork\n"
-#: gschem/src/g_funcs.c:355 gschem/src/i_callbacks.c:78
+#: gschem/src/g_funcs.c:363 gschem/src/i_callbacks.c:78
#, c-format
msgid "Could not invoke %s\n"
msgstr "Could not invoke %s\n"
-#: gschem/src/g_funcs.c:361 gschem/src/i_callbacks.c:82
+#: gschem/src/g_funcs.c:369 gschem/src/i_callbacks.c:82
msgid "Documentation commands not supported under MinGW.\n"
msgstr "Documentation commands not supported under MinGW.\n"
@@ -127,12 +127,12 @@ msgstr "Invalid gain [%d] passed to zoom-gain\n"
msgid "Invalid number of steps [%d] scrollpan-steps\n"
msgstr "Invalid number of steps [%d] scrollpan-steps\n"
-#: gschem/src/gschem.c:184
+#: gschem/src/gschem.c:188
#, c-format
msgid "gEDA/gschem version %s%s.%s\n"
msgstr "gEDA/gschem version %s%s.%s\n"
-#: gschem/src/gschem.c:187
+#: gschem/src/gschem.c:191
msgid ""
"gEDA/gschem comes with ABSOLUTELY NO WARRANTY; see COPYING for more "
"details.\n"
@@ -140,13 +140,13 @@ msgstr ""
"gEDA/gschem comes with ABSOLUTELY NO WARRANTY; see COPYING for more "
"details.\n"
-#: gschem/src/gschem.c:189
+#: gschem/src/gschem.c:193
msgid ""
"This is free software, and you are welcome to redistribute it under certain\n"
msgstr ""
"This is free software, and you are welcome to redistribute it under certain\n"
-#: gschem/src/gschem.c:191
+#: gschem/src/gschem.c:195
msgid ""
"conditions; please see the COPYING file for more details.\n"
"\n"
@@ -154,17 +154,17 @@ msgstr ""
"conditions; please see the COPYING file for more details.\n"
"\n"
-#: gschem/src/gschem.c:194
+#: gschem/src/gschem.c:198
#, c-format
msgid "This is the MINGW32 port.\n"
msgstr "This is the MINGW32 port.\n"
-#: gschem/src/gschem.c:198
+#: gschem/src/gschem.c:202
#, c-format
msgid "Current locale settings: %s\n"
msgstr "Current locale settings: %s\n"
-#: gschem/src/gschem.c:213
+#: gschem/src/gschem.c:218
msgid ""
"You must set the GEDADATA environment variable!\n"
"\n"
@@ -176,31 +176,21 @@ msgstr ""
"gschem cannot locate its data files. You must set the GEDADATA\n"
"environment variable to point to the correct location.\n"
-#: gschem/src/gschem.c:248
+#: gschem/src/gschem.c:256
#, c-format
msgid "Couldn't find init scm file [%s]\n"
msgstr "Couldn't find init scm file [%s]\n"
-#: gschem/src/gschem.c:252
+#: gschem/src/gschem.c:260
#, c-format
msgid "Read init scm file [%s]\n"
msgstr "Read init scm file [%s]\n"
-#: gschem/src/gschem.c:256
+#: gschem/src/gschem.c:264
#, c-format
msgid "Failed to read init scm file [%s]\n"
msgstr "Failed to read init scm file [%s]\n"
-#: gschem/src/gschem.c:317
-#, c-format
-msgid "Scheme directory NOT set!\n"
-msgstr "Scheme directory NOT set!\n"
-
-#: gschem/src/gschem.c:324 gschem/src/x_script.c:66
-#, c-format
-msgid "Executing guile script [%s]\n"
-msgstr "Executing guile script [%s]\n"
-
#: gschem/src/gschem_cairo.c:310
#, c-format
msgid "Unknown end for line (%d)\n"
@@ -224,11 +214,11 @@ msgstr "Component Mode"
msgid "Text Mode"
msgstr "Text Mode"
-#: gschem/src/i_basic.c:84 gschem/lib/system-gschemrc.scm:1409
+#: gschem/src/i_basic.c:84 gschem/lib/system-gschemrc.scm:1411
msgid "Copy Mode"
msgstr "Copy Mode"
-#: gschem/src/i_basic.c:87 gschem/lib/system-gschemrc.scm:1411
+#: gschem/src/i_basic.c:87 gschem/lib/system-gschemrc.scm:1413
msgid "Move Mode"
msgstr "Move Mode"
@@ -236,7 +226,7 @@ msgstr "Move Mode"
msgid "Rotate Mode"
msgstr "Rotate Mode"
-#: gschem/src/i_basic.c:91 gschem/lib/system-gschemrc.scm:1413
+#: gschem/src/i_basic.c:91 gschem/lib/system-gschemrc.scm:1415
msgid "Mirror Mode"
msgstr "Mirror Mode"
@@ -289,22 +279,22 @@ msgstr "Arc Mode"
msgid "Pin Mode"
msgstr "Pin Mode"
-#: gschem/src/i_basic.c:135 gschem/src/i_callbacks.c:544
-#: gschem/src/i_callbacks.c:568
+#: gschem/src/i_basic.c:135 gschem/src/i_callbacks.c:576
+#: gschem/src/i_callbacks.c:600
msgid "Copy"
msgstr "Copy"
-#: gschem/src/i_basic.c:137 gschem/src/i_callbacks.c:634
-#: gschem/src/i_callbacks.c:658
+#: gschem/src/i_basic.c:137 gschem/src/i_callbacks.c:666
+#: gschem/src/i_callbacks.c:690
msgid "Move"
msgstr "Move"
-#: gschem/src/i_basic.c:139 gschem/src/i_callbacks.c:589
-#: gschem/src/i_callbacks.c:613
+#: gschem/src/i_basic.c:139 gschem/src/i_callbacks.c:621
+#: gschem/src/i_callbacks.c:645
msgid "Multiple Copy"
msgstr "Multiple Copy"
-#: gschem/src/i_basic.c:142 gschem/lib/system-gschemrc.scm:1410
+#: gschem/src/i_basic.c:142 gschem/lib/system-gschemrc.scm:1412
msgid "Multiple Copy Mode"
msgstr "Multiple Copy Mode"
@@ -324,7 +314,7 @@ msgstr "Resnap Active"
msgid "Action"
msgstr "Action"
-#: gschem/src/i_basic.c:260 gschem/src/x_dialog.c:2312
+#: gschem/src/i_basic.c:260 gschem/src/x_dialog.c:2316
#: gschem/src/x_window.c:491
msgid "Stroke"
msgstr "Stroke"
@@ -355,7 +345,7 @@ msgstr "Grid(%s, %s)"
msgid "Documentation for [%s,%s,%s,%s]\n"
msgstr "Documentation for [%s,%s,%s,%s]\n"
-#: gschem/src/i_callbacks.c:123 gschem/src/i_callbacks.c:1699
+#: gschem/src/i_callbacks.c:123 gschem/src/i_callbacks.c:1706
#, c-format
msgid "New page created [%s]\n"
msgstr "New page created [%s]\n"
@@ -377,69 +367,69 @@ msgstr "Saved All"
msgid "Closing Window\n"
msgstr "Closing Window\n"
-#: gschem/src/i_callbacks.c:549 gschem/src/i_callbacks.c:594
-#: gschem/src/i_callbacks.c:639
+#: gschem/src/i_callbacks.c:581 gschem/src/i_callbacks.c:626
+#: gschem/src/i_callbacks.c:671
msgid "Select objs first"
msgstr "Select objs first"
-#: gschem/src/i_callbacks.c:678 gschem/src/x_multiattrib.c:1491
+#: gschem/src/i_callbacks.c:710 gschem/src/x_multiattrib.c:1503
msgid "Delete"
msgstr "Delete"
-#: gschem/src/i_callbacks.c:703
+#: gschem/src/i_callbacks.c:735
msgid "Edit"
msgstr "Edit"
-#: gschem/src/i_callbacks.c:718
+#: gschem/src/i_callbacks.c:750
msgid "Edit pin type"
msgstr "Edit pin type"
-#: gschem/src/i_callbacks.c:737
+#: gschem/src/i_callbacks.c:769
msgid "Edit Text"
msgstr "Edit Text"
-#: gschem/src/i_callbacks.c:760
+#: gschem/src/i_callbacks.c:792
msgid "Slot"
msgstr "Slot"
-#: gschem/src/i_callbacks.c:777
+#: gschem/src/i_callbacks.c:809
msgid "Color"
msgstr "Colour"
-#: gschem/src/i_callbacks.c:814 gschem/src/i_callbacks.c:859
+#: gschem/src/i_callbacks.c:846 gschem/src/i_callbacks.c:891
msgid "Rotate"
msgstr "Rotate"
-#: gschem/src/i_callbacks.c:882 gschem/src/i_callbacks.c:907
+#: gschem/src/i_callbacks.c:913 gschem/src/i_callbacks.c:938
msgid "Mirror"
msgstr "Mirror"
-#: gschem/src/i_callbacks.c:928 gschem/src/x_dialog.c:2315
-#: gschem/lib/system-gschemrc.scm:1422
+#: gschem/src/i_callbacks.c:959 gschem/src/x_dialog.c:2319
+#: gschem/lib/system-gschemrc.scm:1424
msgid "Lock"
msgstr "Lock"
-#: gschem/src/i_callbacks.c:946 gschem/lib/system-gschemrc.scm:1423
+#: gschem/src/i_callbacks.c:977 gschem/lib/system-gschemrc.scm:1425
msgid "Unlock"
msgstr "Unlock"
-#: gschem/src/i_callbacks.c:964 gschem/src/x_dialog.c:1734
+#: gschem/src/i_callbacks.c:995 gschem/src/x_dialog.c:1737
msgid "Translate"
msgstr "Translate"
-#: gschem/src/i_callbacks.c:967
+#: gschem/src/i_callbacks.c:998
msgid "WARNING: Do not translate with snap off!\n"
msgstr "WARNING: Do not translate with snap off!\n"
-#: gschem/src/i_callbacks.c:968
+#: gschem/src/i_callbacks.c:999
msgid "WARNING: Turning snap on and continuing with translate.\n"
msgstr "WARNING: Turning snap on and continuing with translate.\n"
-#: gschem/src/i_callbacks.c:975
+#: gschem/src/i_callbacks.c:1006
msgid "WARNING: Snap grid size is not equal to 100!\n"
msgstr "WARNING: Snap grid size is not equal to 100!\n"
-#: gschem/src/i_callbacks.c:977
+#: gschem/src/i_callbacks.c:1008
msgid ""
"WARNING: If you are translating a symbol to the origin, the snap grid size "
"should be set to 100\n"
@@ -447,176 +437,172 @@ msgstr ""
"WARNING: If you are translating a symbol to the origin, the snap grid size "
"should be set to 100\n"
-#: gschem/src/i_callbacks.c:1008
+#: gschem/src/i_callbacks.c:1039
msgid "Embed"
msgstr "Embed"
-#: gschem/src/i_callbacks.c:1047
+#: gschem/src/i_callbacks.c:1078
msgid "Unembed"
msgstr "Unembed"
-#: gschem/src/i_callbacks.c:1089
+#: gschem/src/i_callbacks.c:1120
msgid "Update"
msgstr "Update"
-#: gschem/src/i_callbacks.c:1136
+#: gschem/src/i_callbacks.c:1167
msgid "ShowHidden"
msgstr "ShowHidden"
-#: gschem/src/i_callbacks.c:1160
-msgid "MakeVisible"
-msgstr "MakeVisible"
-
-#: gschem/src/i_callbacks.c:1466 gschem/src/i_callbacks.c:1538
+#: gschem/src/i_callbacks.c:1473 gschem/src/i_callbacks.c:1545
msgid "Pan"
msgstr "Pan"
-#: gschem/src/i_callbacks.c:1743
+#: gschem/src/i_callbacks.c:1750
msgid "Really revert page?"
msgstr "Really revert page?"
-#: gschem/src/i_callbacks.c:1813
+#: gschem/src/i_callbacks.c:1820
msgid "Copy to clipboard"
msgstr "Copy to clipboard"
-#: gschem/src/i_callbacks.c:1831
+#: gschem/src/i_callbacks.c:1838
msgid "Cut to clipboard"
msgstr "Cut to clipboard"
-#: gschem/src/i_callbacks.c:1849
+#: gschem/src/i_callbacks.c:1856
msgid "Paste from clipboard"
msgstr "Paste from clipboard"
-#: gschem/src/i_callbacks.c:1861 gschem/src/i_callbacks.c:2100
-#: gschem/src/i_callbacks.c:2122 gschem/src/i_callbacks.c:2144
-#: gschem/src/i_callbacks.c:2166 gschem/src/i_callbacks.c:2188
+#: gschem/src/i_callbacks.c:1868 gschem/src/i_callbacks.c:2107
+#: gschem/src/i_callbacks.c:2129 gschem/src/i_callbacks.c:2151
+#: gschem/src/i_callbacks.c:2173 gschem/src/i_callbacks.c:2195
msgid "Empty buffer"
msgstr "Empty buffer"
-#: gschem/src/i_callbacks.c:1906
+#: gschem/src/i_callbacks.c:1913
msgid "Copy 1"
msgstr "Copy 1"
-#: gschem/src/i_callbacks.c:1925
+#: gschem/src/i_callbacks.c:1932
msgid "Copy 2"
msgstr "Copy 2"
-#: gschem/src/i_callbacks.c:1944
+#: gschem/src/i_callbacks.c:1951
msgid "Copy 3"
msgstr "Copy 3"
-#: gschem/src/i_callbacks.c:1963
+#: gschem/src/i_callbacks.c:1970
msgid "Copy 4"
msgstr "Copy 4"
-#: gschem/src/i_callbacks.c:1982
+#: gschem/src/i_callbacks.c:1989
msgid "Copy 5"
msgstr "Copy 5"
-#: gschem/src/i_callbacks.c:2001
+#: gschem/src/i_callbacks.c:2008
msgid "Cut 1"
msgstr "Cut 1"
-#: gschem/src/i_callbacks.c:2020
+#: gschem/src/i_callbacks.c:2027
msgid "Cut 2"
msgstr "Cut 2"
-#: gschem/src/i_callbacks.c:2039
+#: gschem/src/i_callbacks.c:2046
msgid "Cut 3"
msgstr "Cut 3"
-#: gschem/src/i_callbacks.c:2058
+#: gschem/src/i_callbacks.c:2065
msgid "Cut 4"
msgstr "Cut 4"
-#: gschem/src/i_callbacks.c:2077
+#: gschem/src/i_callbacks.c:2084
msgid "Cut 5"
msgstr "Cut 5"
-#: gschem/src/i_callbacks.c:2093
+#: gschem/src/i_callbacks.c:2100
msgid "Paste 1"
msgstr "Paste 1"
-#: gschem/src/i_callbacks.c:2115
+#: gschem/src/i_callbacks.c:2122
msgid "Paste 2"
msgstr "Paste 2"
-#: gschem/src/i_callbacks.c:2137
+#: gschem/src/i_callbacks.c:2144
msgid "Paste 3"
msgstr "Paste 3"
-#: gschem/src/i_callbacks.c:2159
+#: gschem/src/i_callbacks.c:2166
msgid "Paste 4"
msgstr "Paste 4"
-#: gschem/src/i_callbacks.c:2181
+#: gschem/src/i_callbacks.c:2188
msgid "Paste 5"
msgstr "Paste 5"
-#: gschem/src/i_callbacks.c:2318 gschem/src/x_window.c:355
+#: gschem/src/i_callbacks.c:2325 gschem/src/x_window.c:355
msgid "Component"
msgstr "Component"
-#: gschem/src/i_callbacks.c:2354 gschem/src/i_callbacks.c:2373
-#: gschem/src/x_dialog.c:2285
+#: gschem/src/i_callbacks.c:2361 gschem/src/i_callbacks.c:2380
+#: gschem/src/x_dialog.c:2289
msgid "Attribute"
msgstr "Attribute"
-#: gschem/src/i_callbacks.c:2395 gschem/src/i_callbacks.c:2422
-#: gschem/src/x_dialog.c:2282
+#: gschem/src/i_callbacks.c:2402 gschem/src/i_callbacks.c:2429
+#: gschem/src/x_dialog.c:2286
msgid "Net"
msgstr "Net"
-#: gschem/src/i_callbacks.c:2466 gschem/src/i_callbacks.c:2493
-#: gschem/src/x_dialog.c:2300 gschem/src/x_window.c:375
+#: gschem/src/i_callbacks.c:2473 gschem/src/i_callbacks.c:2500
+#: gschem/src/x_dialog.c:2304 gschem/src/x_window.c:375
msgid "Bus"
msgstr "Bus"
-#: gschem/src/i_callbacks.c:2574 gschem/src/i_callbacks.c:2597
+#: gschem/src/i_callbacks.c:2581 gschem/src/i_callbacks.c:2604
msgid "Line"
msgstr "Line"
-#: gschem/src/i_callbacks.c:2619 gschem/src/i_callbacks.c:2642
+#: gschem/src/i_callbacks.c:2626 gschem/src/i_callbacks.c:2649
msgid "Box"
msgstr "Box"
-#: gschem/src/i_callbacks.c:2698 gschem/src/i_callbacks.c:2722
+#: gschem/src/i_callbacks.c:2705 gschem/src/i_callbacks.c:2729
msgid "Circle"
msgstr "Circle"
-#: gschem/src/i_callbacks.c:2744 gschem/src/i_callbacks.c:2767
+#: gschem/src/i_callbacks.c:2751 gschem/src/i_callbacks.c:2774
msgid "Arc"
msgstr "Arc"
-#: gschem/src/i_callbacks.c:2789 gschem/src/i_callbacks.c:2812
-#: gschem/src/x_dialog.c:2273
+#: gschem/src/i_callbacks.c:2796 gschem/src/i_callbacks.c:2819
+#: gschem/src/x_dialog.c:2277
msgid "Pin"
msgstr "Pin"
-#: gschem/src/i_callbacks.c:2871
+#: gschem/src/i_callbacks.c:2878
#, c-format
msgid "Searching for source [%s]\n"
msgstr "Searching for source [%s]\n"
-#: gschem/src/i_callbacks.c:2895
+#: gschem/src/i_callbacks.c:2902
#, c-format
msgid "Cannot find source [%s]\n"
msgstr "Cannot find source [%s]\n"
-#: gschem/src/i_callbacks.c:2964
+#: gschem/src/i_callbacks.c:2965
#, c-format
msgid "Searching for symbol [%s]\n"
msgstr "Searching for symbol [%s]\n"
-#: gschem/src/i_callbacks.c:2970
+#: gschem/src/i_callbacks.c:2971
msgid "Symbol is not a real file. Symbol cannot be loaded.\n"
msgstr "Symbol is not a real file. Symbol cannot be loaded.\n"
-#: gschem/src/i_callbacks.c:3001
+#: gschem/src/i_callbacks.c:3002
msgid "Cannot find any schematics above the current one!\n"
msgstr "Cannot find any schematics above the current one!\n"
-#: gschem/src/i_callbacks.c:3055
+#: gschem/src/i_callbacks.c:3056
msgid ""
"This command retrieves the component documentation from the web, but there "
"is no component selected"
@@ -624,84 +610,84 @@ msgstr ""
"This command retrieves the component documentation from the web, but there "
"is no component selected"
-#: gschem/src/i_callbacks.c:3083
+#: gschem/src/i_callbacks.c:3084
msgid "Attach"
msgstr "Attach"
-#: gschem/src/i_callbacks.c:3130
+#: gschem/src/i_callbacks.c:3131
msgid "Detach"
msgstr "Detach"
-#: gschem/src/i_callbacks.c:3165
+#: gschem/src/i_callbacks.c:3166
msgid "ShowN"
msgstr "ShowN"
-#: gschem/src/i_callbacks.c:3201
+#: gschem/src/i_callbacks.c:3202
msgid "ShowV"
msgstr "ShowV"
-#: gschem/src/i_callbacks.c:3237
+#: gschem/src/i_callbacks.c:3238
msgid "ShowB"
msgstr "ShowB"
-#: gschem/src/i_callbacks.c:3274
+#: gschem/src/i_callbacks.c:3275
msgid "VisToggle"
msgstr "VisToggle"
-#: gschem/src/i_callbacks.c:3304
+#: gschem/src/i_callbacks.c:3305
#, c-format
msgid "Sorry but this is a non-functioning menu option\n"
msgstr "Sorry but this is a non-functioning menu option\n"
-#: gschem/src/i_callbacks.c:3394
+#: gschem/src/i_callbacks.c:3395
msgid "Action feedback mode set to OUTLINE\n"
msgstr "Action feedback mode set to OUTLINE\n"
-#: gschem/src/i_callbacks.c:3397
+#: gschem/src/i_callbacks.c:3398
msgid "Action feedback mode set to BOUNDINGBOX\n"
msgstr "Action feedback mode set to BOUNDINGBOX\n"
-#: gschem/src/i_callbacks.c:3422
+#: gschem/src/i_callbacks.c:3423
msgid "Grid OFF\n"
msgstr "Grid OFF\n"
-#: gschem/src/i_callbacks.c:3423
+#: gschem/src/i_callbacks.c:3424
msgid "Dot grid selected\n"
msgstr "Dot grid selected\n"
-#: gschem/src/i_callbacks.c:3424
+#: gschem/src/i_callbacks.c:3425
msgid "Mesh grid selected\n"
msgstr "Mesh grid selected\n"
-#: gschem/src/i_callbacks.c:3445
+#: gschem/src/i_callbacks.c:3446
msgid "Snap OFF (CAUTION!)\n"
msgstr "Snap OFF (CAUTION!)\n"
-#: gschem/src/i_callbacks.c:3448
+#: gschem/src/i_callbacks.c:3449
msgid "Snap ON\n"
msgstr "Snap ON\n"
-#: gschem/src/i_callbacks.c:3451
+#: gschem/src/i_callbacks.c:3452
msgid "Snap back to the grid (CAUTION!)\n"
msgstr "Snap back to the grid (CAUTION!)\n"
-#: gschem/src/i_callbacks.c:3477
+#: gschem/src/i_callbacks.c:3478
msgid "Rubber band OFF \n"
msgstr "Rubber band OFF \n"
-#: gschem/src/i_callbacks.c:3480
+#: gschem/src/i_callbacks.c:3481
msgid "Rubber band ON\n"
msgstr "Rubber band ON\n"
-#: gschem/src/i_callbacks.c:3495
+#: gschem/src/i_callbacks.c:3496
msgid "magnetic net mode: ON\n"
msgstr "magnetic net mode: ON\n"
-#: gschem/src/i_callbacks.c:3498
+#: gschem/src/i_callbacks.c:3499
msgid "magnetic net mode: OFF\n"
msgstr "magnetic net mode: OFF\n"
-#: gschem/src/o_box.c:153
+#: gschem/src/o_box.c:149
#, c-format
msgid "Unknown type for box (fill)!\n"
msgstr "Unknown type for box (fill)!\n"
@@ -721,17 +707,17 @@ msgstr "o_buffer_cut: Invalid buffer %i\n"
msgid "Got an invalid buffer_number [o_buffer_paste_start]\n"
msgstr "Got an invalid buffer_number [o_buffer_paste_start]\n"
-#: gschem/src/o_bus.c:118
+#: gschem/src/o_bus.c:117
#, c-format
msgid "Got an invalid which one in o_bus_draw_stretch\n"
msgstr "Got an invalid which one in o_bus_draw_stretch\n"
-#: gschem/src/o_circle.c:134
+#: gschem/src/o_circle.c:130
#, c-format
msgid "Unknown type for circle (fill)!\n"
msgstr "Unknown type for circle (fill)!\n"
-#: gschem/src/o_complex.c:243 gschem/src/o_complex.c:247
+#: gschem/src/o_complex.c:237 gschem/src/o_complex.c:241
#, c-format
msgid "Translating schematic [%d %d]\n"
msgstr "Translating schematic [%d %d]\n"
@@ -749,35 +735,35 @@ msgstr "Object already locked\n"
msgid "Object already unlocked\n"
msgstr "Object already unlocked\n"
-#: gschem/src/o_misc.c:413
+#: gschem/src/o_misc.c:409
msgid "Hidden text is now visible\n"
msgstr "Hidden text is now visible\n"
-#: gschem/src/o_misc.c:415
+#: gschem/src/o_misc.c:411
msgid "Hidden text is now invisible\n"
msgstr "Hidden text is now invisible\n"
-#: gschem/src/o_misc.c:668
+#: gschem/src/o_misc.c:636
#, c-format
msgid "Could not find symbol [%s] in library. Update failed.\n"
msgstr "Could not find symbol [%s] in library. Update failed.\n"
-#: gschem/src/o_misc.c:783
+#: gschem/src/o_misc.c:751
#, c-format
msgid "o_autosave_backups: Can't get the real filename of %s."
msgstr "o_autosave_backups: Can't get the real filename of %s."
-#: gschem/src/o_misc.c:827
+#: gschem/src/o_misc.c:795
#, c-format
msgid "Could NOT set previous backup file [%s] read-write\n"
msgstr "Could NOT set previous backup file [%s] read-write\n"
-#: gschem/src/o_misc.c:845
+#: gschem/src/o_misc.c:815
#, c-format
msgid "Could NOT set backup file [%s] readonly\n"
msgstr "Could NOT set backup file [%s] readonly\n"
-#: gschem/src/o_misc.c:850
+#: gschem/src/o_misc.c:820
#, c-format
msgid "Could NOT save backup file [%s]\n"
msgstr "Could NOT save backup file [%s]\n"
@@ -797,36 +783,36 @@ msgstr "DOH! tried to find the whichone, but didn't find it!\n"
msgid "Got a non line object in o_move_check_endpoint\n"
msgstr "Got a non line object in o_move_check_endpoint\n"
-#: gschem/src/o_net.c:159
+#: gschem/src/o_net.c:158
#, c-format
msgid "Got an invalid which one in o_net_draw_stretch\n"
msgstr "Got an invalid which one in o_net_draw_stretch\n"
-#: gschem/src/o_net.c:538
+#: gschem/src/o_net.c:537
msgid "Warning: Starting net at off grid coordinate\n"
msgstr "Warning: Starting net at off grid coordinate\n"
-#: gschem/src/o_net.c:600
+#: gschem/src/o_net.c:599
msgid "Warning: Ending net at off grid coordinate\n"
msgstr "Warning: Ending net at off grid coordinate\n"
-#: gschem/src/o_net.c:932 gschem/src/o_net.c:969 gschem/src/o_net.c:1040
-#: gschem/src/o_net.c:1076
+#: gschem/src/o_net.c:931 gschem/src/o_net.c:968 gschem/src/o_net.c:1039
+#: gschem/src/o_net.c:1075
#, c-format
msgid "Tried to add more than two bus rippers. Internal gschem error.\n"
msgstr "Tried to add more than two bus rippers. Internal gschem error.\n"
-#: gschem/src/o_net.c:1144
+#: gschem/src/o_net.c:1143
#, c-format
msgid "Bus ripper symbol [%s] was not found in any component library\n"
msgstr "Bus ripper symbol [%s] was not found in any component library\n"
-#: gschem/src/o_path.c:352
+#: gschem/src/o_path.c:348
#, c-format
msgid "Unknown type for path (fill)!\n"
msgstr "Unknown type for path (fill)!\n"
-#: gschem/src/o_picture.c:163 gschem/src/o_picture.c:539
+#: gschem/src/o_picture.c:163 gschem/src/o_picture.c:537
#, c-format
msgid "Failed to load picture: %s"
msgstr "Failed to load picture: %s"
@@ -835,7 +821,7 @@ msgstr "Failed to load picture: %s"
msgid "Picture"
msgstr "Picture"
-#: gschem/src/o_picture.c:447 gschem/src/x_attribedit.c:141
+#: gschem/src/o_picture.c:445 gschem/src/x_attribedit.c:141
#, c-format
msgid "ERROR: NULL object!\n"
msgstr "ERROR: NULL object!\n"
@@ -856,34 +842,46 @@ msgstr "Slotting not allowed for this component\n"
msgid "New slot number out of range\n"
msgstr "New slot number out of range\n"
-#: gschem/src/o_undo.c:304
+#: gschem/src/o_undo.c:303
msgid "Undo/Redo disabled in rc file\n"
msgstr "Undo/Redo disabled in rc file\n"
-#: gschem/src/parsecmd.c:47
+#: gschem/src/parsecmd.c:81
#, c-format
msgid ""
-"Usage: %s [OPTIONS] schematic_filename1 ... schematic_filenameN\n"
-" -q Quiet mode\n"
-" -v Verbose mode on\n"
-" -r filename Rc filename\n"
-" -s filename Script (guile) filename\n"
-" -o filename Output filename (for printing)\n"
-" -p Automatically place the window\n"
-" -t Print stroke information\n"
-" -h Help; this message\n"
+"Usage: %s [OPTION ...] [--] [FILE ...]\n"
"\n"
-msgstr ""
-"Usage: %s [OPTIONS] schematic_filename1 ... schematic_filenameN\n"
-" -q Quiet mode\n"
-" -v Verbose mode on\n"
-" -r filename Rc filename\n"
-" -s filename Script (guile) filename\n"
-" -o filename Output filename (for printing)\n"
-" -p Automatically place the window\n"
-" -t Print stroke information\n"
-" -h Help; this message\n"
+"Interactively edit gEDA schematics or symbols. If one or more FILEs\n"
+"are specified, open them for editing; otherwise, create a new, empty\n"
+"schematic.\n"
"\n"
+"Options:\n"
+" -q, --quiet Quiet mode.\n"
+" -v, --verbose Verbose mode.\n"
+" -r, --config-file=FILE Additional configuration file to load.\n"
+" -L DIR Add DIR to Scheme search path.\n"
+" -c EXPR Scheme expression to run at startup.\n"
+" -s FILE Scheme script to run at startup.\n"
+" -o, --output=FILE Output filename (for printing).\n"
+" -p Automatically place the window.\n"
+" -V, --version Show version information.\n"
+" -h, --help Help; this message.\n"
+" -- Treat all remaining arguments as filenames.\n"
+"\n"
+"Report bugs to <geda-bug@xxxxxxxx>\n"
+"gEDA/gaf homepage: <http://gpleda.org>\n"
+msgstr ""
+
+#: gschem/src/parsecmd.c:115
+#, c-format
+msgid ""
+"gEDA %s (g%.7s)\n"
+"Copyright (C) 1998-2011 gEDA developers\n"
+"This is free software, and you are welcome to redistribute it under\n"
+"certain conditions. For details, see the file `COPYING', which is\n"
+"included in the gEDA distribution.\n"
+"There is NO WARRANTY, to the extent permitted by law.\n"
+msgstr ""
#: gschem/src/x_attribedit.c:127
#, c-format
@@ -894,56 +892,56 @@ msgstr "Got invalid show option; defaulting to show both\n"
msgid "Single Attribute Editor"
msgstr "Single Attribute Editor"
-#: gschem/src/x_attribedit.c:358
+#: gschem/src/x_attribedit.c:359
msgid "<b>Edit Attribute</b>"
msgstr "<b>Edit Attribute</b>"
-#: gschem/src/x_attribedit.c:360
+#: gschem/src/x_attribedit.c:361
msgid "<b>Add Attribute</b>"
msgstr "<b>Add Attribute</b>"
-#: gschem/src/x_attribedit.c:376 gschem/src/x_multiattrib.c:1916
+#: gschem/src/x_attribedit.c:377 gschem/src/x_multiattrib.c:1927
msgid "Name:"
msgstr "Name:"
-#: gschem/src/x_attribedit.c:393 gschem/src/x_multiattrib.c:1935
+#: gschem/src/x_attribedit.c:394 gschem/src/x_multiattrib.c:1946
msgid "Value:"
msgstr "Value:"
-#: gschem/src/x_attribedit.c:409 gschem/src/x_multiattrib.c:1978
+#: gschem/src/x_attribedit.c:410 gschem/src/x_multiattrib.c:1989
msgid "Visible"
msgstr "Visible"
-#: gschem/src/x_attribedit.c:429
+#: gschem/src/x_attribedit.c:430
msgid "Show Value Only"
msgstr "Show Value Only"
-#: gschem/src/x_attribedit.c:431
+#: gschem/src/x_attribedit.c:432
msgid "Show Name Only"
msgstr "Show Name Only"
-#: gschem/src/x_attribedit.c:433 gschem/src/x_multiattrib.c:1454
+#: gschem/src/x_attribedit.c:434 gschem/src/x_multiattrib.c:1466
msgid "Show Name & Value"
msgstr "Show Name & Value"
-#: gschem/src/x_attribedit.c:440
+#: gschem/src/x_attribedit.c:441
msgid "<b>Attach Options</b>"
msgstr "<b>Attach Options</b>"
-#: gschem/src/x_attribedit.c:455
+#: gschem/src/x_attribedit.c:456
msgid "All"
msgstr "All"
-#: gschem/src/x_attribedit.c:463 gschem/src/x_compselect.c:896
-#: gschem/src/x_compselect.c:1010
+#: gschem/src/x_attribedit.c:464 gschem/src/x_compselect.c:904
+#: gschem/src/x_compselect.c:1018
msgid "Components"
msgstr "Components"
-#: gschem/src/x_attribedit.c:471 gschem/src/x_window.c:365
+#: gschem/src/x_attribedit.c:472 gschem/src/x_window.c:365
msgid "Nets"
msgstr "Nets"
-#: gschem/src/x_attribedit.c:479
+#: gschem/src/x_attribedit.c:480
msgid "Replace existing attributes"
msgstr "Replace existing attributes"
@@ -962,91 +960,91 @@ msgid ""
msgstr ""
"duplicate slot may cause problems: [symbolname=%s, number=%d, slot=%d]\n"
-#: gschem/src/x_autonumber.c:673
+#: gschem/src/x_autonumber.c:675
msgid "No searchstring given in autonumber text.\n"
msgstr "No searchstring given in autonumber text.\n"
-#: gschem/src/x_autonumber.c:725
+#: gschem/src/x_autonumber.c:727
msgid "No '*' or '?' given at the end of the autonumber text.\n"
msgstr "No '*' or '?' given at the end of the autonumber text.\n"
-#: gschem/src/x_autonumber.c:860
+#: gschem/src/x_autonumber.c:862
msgid "Diagonal"
msgstr "Diagonal"
-#: gschem/src/x_autonumber.c:861
+#: gschem/src/x_autonumber.c:863
msgid "Top to bottom"
msgstr "Top to bottom"
-#: gschem/src/x_autonumber.c:861
+#: gschem/src/x_autonumber.c:863
msgid "Bottom to top"
msgstr "Bottom to top"
-#: gschem/src/x_autonumber.c:862
+#: gschem/src/x_autonumber.c:864
msgid "Left to right"
msgstr "Left to right"
-#: gschem/src/x_autonumber.c:862
+#: gschem/src/x_autonumber.c:864
msgid "Right to left"
msgstr "Right to left"
-#: gschem/src/x_autonumber.c:863
+#: gschem/src/x_autonumber.c:865
msgid "File order"
msgstr "File order"
-#: gschem/src/x_autonumber.c:1199
+#: gschem/src/x_autonumber.c:1201
msgid "Autonumber text"
msgstr "Autonumber text"
-#: gschem/src/x_autonumber.c:1223
+#: gschem/src/x_autonumber.c:1225
msgid "<b>Scope</b>"
msgstr "<b>Scope</b>"
-#: gschem/src/x_autonumber.c:1245
+#: gschem/src/x_autonumber.c:1247
msgid "Search for:"
msgstr "Search for:"
-#: gschem/src/x_autonumber.c:1259
+#: gschem/src/x_autonumber.c:1261
msgid "Autonumber text in:"
msgstr "Autonumber text in:"
-#: gschem/src/x_autonumber.c:1266
+#: gschem/src/x_autonumber.c:1268
msgid "Skip numbers found in:"
msgstr "Skip numbers found in:"
-#: gschem/src/x_autonumber.c:1278 gschem/src/x_autonumber.c:1287
+#: gschem/src/x_autonumber.c:1280 gschem/src/x_autonumber.c:1289
msgid "Selected objects"
msgstr "Selected objects"
-#: gschem/src/x_autonumber.c:1279 gschem/src/x_autonumber.c:1288
+#: gschem/src/x_autonumber.c:1281 gschem/src/x_autonumber.c:1290
msgid "Current page"
msgstr "Current page"
-#: gschem/src/x_autonumber.c:1280 gschem/src/x_autonumber.c:1289
+#: gschem/src/x_autonumber.c:1282 gschem/src/x_autonumber.c:1291
msgid "Whole hierarchy"
msgstr "Whole hierarchy"
-#: gschem/src/x_autonumber.c:1291
+#: gschem/src/x_autonumber.c:1293
msgid "Overwrite existing numbers"
msgstr "Overwrite existing numbers"
-#: gschem/src/x_autonumber.c:1296
+#: gschem/src/x_autonumber.c:1298
msgid "<b>Options</b>"
msgstr "<b>Options</b>"
-#: gschem/src/x_autonumber.c:1318
+#: gschem/src/x_autonumber.c:1320
msgid "Starting number:"
msgstr "Starting number:"
-#: gschem/src/x_autonumber.c:1325
+#: gschem/src/x_autonumber.c:1327
msgid "Sort order:"
msgstr "Sort order:"
-#: gschem/src/x_autonumber.c:1346
+#: gschem/src/x_autonumber.c:1348
msgid "Remove numbers"
msgstr "Remove numbers"
-#: gschem/src/x_autonumber.c:1350
+#: gschem/src/x_autonumber.c:1352
msgid "Automatic slotting"
msgstr "Automatic slotting"
@@ -1083,48 +1081,48 @@ msgstr "Tried to get an invalid colour: %d\n"
msgid "Tried to get an invalid outline color: %d\n"
msgstr "Tried to get an invalid outline colour: %d\n"
-#: gschem/src/x_compselect.c:1040
+#: gschem/src/x_compselect.c:1048
msgid "Filter:"
msgstr "Filter:"
-#: gschem/src/x_compselect.c:1143 gschem/src/x_dialog.c:3663
-#: gschem/src/x_multiattrib.c:1782
+#: gschem/src/x_compselect.c:1151 gschem/src/x_dialog.c:3667
+#: gschem/src/x_multiattrib.c:1793
msgid "Name"
msgstr "Name"
-#: gschem/src/x_compselect.c:1152 gschem/src/x_multiattrib.c:1806
+#: gschem/src/x_compselect.c:1160 gschem/src/x_multiattrib.c:1817
msgid "Value"
msgstr "Value"
-#: gschem/src/x_compselect.c:1191
+#: gschem/src/x_compselect.c:1199
msgid "Default behavior - reference component"
msgstr "Default behavior - reference component"
-#: gschem/src/x_compselect.c:1194
+#: gschem/src/x_compselect.c:1202
msgid "Embed component in schematic"
msgstr "Embed component in schematic"
-#: gschem/src/x_compselect.c:1197
+#: gschem/src/x_compselect.c:1205
msgid "Include component as individual objects"
msgstr "Include component as individual objects"
-#: gschem/src/x_compselect.c:1354
+#: gschem/src/x_compselect.c:1362
msgid "Select Component..."
msgstr "Select Component..."
-#: gschem/src/x_compselect.c:1377
+#: gschem/src/x_compselect.c:1385
msgid "In Use"
msgstr "In Use"
-#: gschem/src/x_compselect.c:1381
+#: gschem/src/x_compselect.c:1389
msgid "Libraries"
msgstr "Libraries"
-#: gschem/src/x_compselect.c:1390 gschem/src/x_fileselect.c:122
+#: gschem/src/x_compselect.c:1398 gschem/src/x_fileselect.c:122
msgid "Preview"
msgstr "Preview"
-#: gschem/src/x_compselect.c:1418
+#: gschem/src/x_compselect.c:1426
msgid "Attributes"
msgstr "Attributes"
@@ -1182,139 +1180,139 @@ msgstr "Lower Right"
msgid "Edit Text Properties"
msgstr "Edit Text Properties"
-#: gschem/src/x_dialog.c:471
+#: gschem/src/x_dialog.c:472
msgid "<b>Text Content</b>"
msgstr "<b>Text Content</b>"
-#: gschem/src/x_dialog.c:507
+#: gschem/src/x_dialog.c:508
msgid "<b>Text Properties</b>"
msgstr "<b>Text Properties</b>"
-#: gschem/src/x_dialog.c:522
+#: gschem/src/x_dialog.c:523
msgid "Color:"
msgstr "Colour:"
-#: gschem/src/x_dialog.c:529
+#: gschem/src/x_dialog.c:530
msgid "Size:"
msgstr "Size:"
-#: gschem/src/x_dialog.c:538
+#: gschem/src/x_dialog.c:539
msgid "Alignment:"
msgstr "Alignment:"
-#: gschem/src/x_dialog.c:587
+#: gschem/src/x_dialog.c:588
msgid "Solid"
msgstr "Solid"
-#: gschem/src/x_dialog.c:588
+#: gschem/src/x_dialog.c:589
msgid "Dotted"
msgstr "Dotted"
-#: gschem/src/x_dialog.c:589
+#: gschem/src/x_dialog.c:590
msgid "Dashed"
msgstr "Dashed"
-#: gschem/src/x_dialog.c:590
+#: gschem/src/x_dialog.c:591
msgid "Center"
msgstr "Center"
-#: gschem/src/x_dialog.c:591
+#: gschem/src/x_dialog.c:592
msgid "Phantom"
msgstr "Phantom"
-#: gschem/src/x_dialog.c:592 gschem/src/x_dialog.c:689
-#: gschem/src/x_dialog.c:698 gschem/src/x_dialog.c:707
-#: gschem/src/x_dialog.c:808 gschem/src/x_dialog.c:810
-#: gschem/src/x_dialog.c:812 gschem/src/x_dialog.c:1038
-#: gschem/src/x_dialog.c:1141 gschem/src/x_dialog.c:1150
-#: gschem/src/x_dialog.c:1159 gschem/src/x_dialog.c:1168
-#: gschem/src/x_dialog.c:1177 gschem/src/x_dialog.c:1290
-#: gschem/src/x_dialog.c:1292 gschem/src/x_dialog.c:1294
-#: gschem/src/x_dialog.c:1296 gschem/src/x_dialog.c:1298
+#: gschem/src/x_dialog.c:593 gschem/src/x_dialog.c:690
+#: gschem/src/x_dialog.c:699 gschem/src/x_dialog.c:708
+#: gschem/src/x_dialog.c:809 gschem/src/x_dialog.c:811
+#: gschem/src/x_dialog.c:813 gschem/src/x_dialog.c:1039
+#: gschem/src/x_dialog.c:1142 gschem/src/x_dialog.c:1151
+#: gschem/src/x_dialog.c:1160 gschem/src/x_dialog.c:1169
+#: gschem/src/x_dialog.c:1178 gschem/src/x_dialog.c:1291
+#: gschem/src/x_dialog.c:1293 gschem/src/x_dialog.c:1295
+#: gschem/src/x_dialog.c:1297 gschem/src/x_dialog.c:1299
msgid "*unchanged*"
msgstr "*unchanged*"
-#: gschem/src/x_dialog.c:916
+#: gschem/src/x_dialog.c:917
msgid "Edit Line Width & Type"
msgstr "Edit Line Width & Type"
-#: gschem/src/x_dialog.c:955 gschem/src/x_print.c:307
+#: gschem/src/x_dialog.c:956 gschem/src/x_print.c:307
msgid "Type:"
msgstr "Type:"
-#: gschem/src/x_dialog.c:959
+#: gschem/src/x_dialog.c:960
msgid "Width:"
msgstr "Width:"
-#: gschem/src/x_dialog.c:963
+#: gschem/src/x_dialog.c:964
msgid "Dash Length:"
msgstr "Dash Length:"
-#: gschem/src/x_dialog.c:967
+#: gschem/src/x_dialog.c:968
msgid "Dash Space:"
msgstr "Dash Space:"
-#: gschem/src/x_dialog.c:1034
+#: gschem/src/x_dialog.c:1035
msgid "Hollow"
msgstr "Hollow"
-#: gschem/src/x_dialog.c:1035
+#: gschem/src/x_dialog.c:1036
msgid "Filled"
msgstr "Filled"
-#: gschem/src/x_dialog.c:1036
+#: gschem/src/x_dialog.c:1037
msgid "Mesh"
msgstr "Mesh"
-#: gschem/src/x_dialog.c:1037
+#: gschem/src/x_dialog.c:1038
msgid "Hatch"
msgstr "Hatch"
-#: gschem/src/x_dialog.c:1406
+#: gschem/src/x_dialog.c:1407
msgid "Edit Fill Type"
msgstr "Edit Fill Type"
-#: gschem/src/x_dialog.c:1444
+#: gschem/src/x_dialog.c:1446
msgid "Fill Type:"
msgstr "Fill Type:"
-#: gschem/src/x_dialog.c:1448
+#: gschem/src/x_dialog.c:1450
msgid "Line Width:"
msgstr "Line Width:"
-#: gschem/src/x_dialog.c:1452
+#: gschem/src/x_dialog.c:1454
msgid "Angle 1:"
msgstr "Angle 1:"
-#: gschem/src/x_dialog.c:1456
+#: gschem/src/x_dialog.c:1458
msgid "Pitch 1:"
msgstr "Pitch 1:"
-#: gschem/src/x_dialog.c:1460
+#: gschem/src/x_dialog.c:1462
msgid "Angle 2:"
msgstr "Angle 2:"
-#: gschem/src/x_dialog.c:1464
+#: gschem/src/x_dialog.c:1466
msgid "Pitch 2:"
msgstr "Pitch 2:"
-#: gschem/src/x_dialog.c:1591
+#: gschem/src/x_dialog.c:1593
msgid "Arc Params"
msgstr "Arc Params"
-#: gschem/src/x_dialog.c:1631
+#: gschem/src/x_dialog.c:1634
msgid "Arc Radius:"
msgstr "Arc Radius:"
-#: gschem/src/x_dialog.c:1639
+#: gschem/src/x_dialog.c:1642
msgid "Start Angle:"
msgstr "Start Angle:"
-#: gschem/src/x_dialog.c:1647
+#: gschem/src/x_dialog.c:1650
msgid "Degrees of Sweep:"
msgstr "Degrees of Sweep:"
-#: gschem/src/x_dialog.c:1764
+#: gschem/src/x_dialog.c:1768
msgid ""
"Offset to translate?\n"
"(0 for origin)"
@@ -1322,199 +1320,199 @@ msgstr ""
"Offset to translate?\n"
"(0 for origin)"
-#: gschem/src/x_dialog.c:1832
+#: gschem/src/x_dialog.c:1836
msgid "Text Size"
msgstr "Text Size"
-#: gschem/src/x_dialog.c:1862
+#: gschem/src/x_dialog.c:1866
msgid "Enter new text size:"
msgstr "Enter new text size:"
-#: gschem/src/x_dialog.c:1938
+#: gschem/src/x_dialog.c:1942
msgid "Snap Size"
msgstr "Snap Size"
-#: gschem/src/x_dialog.c:1968
+#: gschem/src/x_dialog.c:1972
msgid "Enter new snap grid spacing:"
msgstr "Enter new snap grid spacing:"
-#: gschem/src/x_dialog.c:2045
+#: gschem/src/x_dialog.c:2049
msgid "Edit slot number"
msgstr "Edit slot number"
-#: gschem/src/x_dialog.c:2076
+#: gschem/src/x_dialog.c:2080
msgid "Edit slot number:"
msgstr "Edit slot number:"
-#: gschem/src/x_dialog.c:2117
+#: gschem/src/x_dialog.c:2121
#, c-format
msgid "%s%s (%s)"
msgstr ""
-#: gschem/src/x_dialog.c:2140
+#: gschem/src/x_dialog.c:2144
msgid "About gschem"
msgstr "About gschem"
-#: gschem/src/x_dialog.c:2141
+#: gschem/src/x_dialog.c:2145
msgid "gEDA: GPL Electronic Design Automation"
msgstr "gEDA: GPL Electronic Design Automation"
-#: gschem/src/x_dialog.c:2142
+#: gschem/src/x_dialog.c:2146
msgid ""
"Copyright © 1998-2009 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
"Copyright © 1998-2009 gEDA Contributors (see ChangeLog for details)"
msgstr ""
-#: gschem/src/x_dialog.c:2201
+#: gschem/src/x_dialog.c:2205
msgid "Coords"
msgstr "Coords"
-#: gschem/src/x_dialog.c:2222
+#: gschem/src/x_dialog.c:2226
msgid "Screen"
msgstr "Screen"
-#: gschem/src/x_dialog.c:2231
+#: gschem/src/x_dialog.c:2235
msgid "World"
msgstr "World"
-#: gschem/src/x_dialog.c:2270
+#: gschem/src/x_dialog.c:2274
msgid "Background"
msgstr "Background"
-#: gschem/src/x_dialog.c:2276
+#: gschem/src/x_dialog.c:2280
msgid "Net endpoint"
msgstr "Net endpoint"
-#: gschem/src/x_dialog.c:2279
+#: gschem/src/x_dialog.c:2283
msgid "Graphic"
msgstr "Graphic"
-#: gschem/src/x_dialog.c:2288
+#: gschem/src/x_dialog.c:2292
msgid "Logic bubble"
msgstr "Logic bubble"
-#: gschem/src/x_dialog.c:2291
+#: gschem/src/x_dialog.c:2295
msgid "Grid point"
msgstr "Grid point"
-#: gschem/src/x_dialog.c:2294
+#: gschem/src/x_dialog.c:2298
msgid "Detached attribute"
msgstr "Detached attribute"
-#: gschem/src/x_dialog.c:2297 gschem/src/x_window.c:383
+#: gschem/src/x_dialog.c:2301 gschem/src/x_window.c:383
msgid "Text"
msgstr "Text"
-#: gschem/src/x_dialog.c:2303
+#: gschem/src/x_dialog.c:2307
msgid "Selection"
msgstr "Selection"
-#: gschem/src/x_dialog.c:2306
+#: gschem/src/x_dialog.c:2310
msgid "Bounding box"
msgstr "Bounding box"
-#: gschem/src/x_dialog.c:2309
+#: gschem/src/x_dialog.c:2313
msgid "Zoom box"
msgstr "Zoom box"
-#: gschem/src/x_dialog.c:2318
+#: gschem/src/x_dialog.c:2322
msgid "Output background"
msgstr "Output background"
-#: gschem/src/x_dialog.c:2321
+#: gschem/src/x_dialog.c:2325
msgid "Net junction"
msgstr "Net junction"
-#: gschem/src/x_dialog.c:2324
+#: gschem/src/x_dialog.c:2328
msgid "Mesh grid major"
msgstr "Mesh grid major"
-#: gschem/src/x_dialog.c:2327
+#: gschem/src/x_dialog.c:2331
msgid "Mesh grid minor"
msgstr "Mesh grid minor"
-#: gschem/src/x_dialog.c:2330
+#: gschem/src/x_dialog.c:2334
msgid "Unknown"
msgstr "Unknown"
-#: gschem/src/x_dialog.c:2481
+#: gschem/src/x_dialog.c:2485
#, c-format
msgid "ERROR: NULL object in color_edit_dialog_apply!\n"
msgstr "ERROR: NULL object in color_edit_dialog_apply!\n"
-#: gschem/src/x_dialog.c:2525
+#: gschem/src/x_dialog.c:2529
msgid "Color Edit"
msgstr "Colour Edit"
-#: gschem/src/x_dialog.c:2556
+#: gschem/src/x_dialog.c:2560
msgid "Object color:"
msgstr "Object colour:"
-#: gschem/src/x_dialog.c:2614
+#: gschem/src/x_dialog.c:2618
msgid "Hotkeys"
msgstr "Hotkeys"
-#: gschem/src/x_dialog.c:2678
+#: gschem/src/x_dialog.c:2682
msgid "Function"
msgstr "Function"
-#: gschem/src/x_dialog.c:2685
+#: gschem/src/x_dialog.c:2689
msgid "Keystroke(s)"
msgstr "Keystroke(s)"
-#: gschem/src/x_dialog.c:2991
+#: gschem/src/x_dialog.c:2995
msgid "Find Text"
msgstr "Find Text"
-#: gschem/src/x_dialog.c:3022
+#: gschem/src/x_dialog.c:3026
msgid "Text to find:"
msgstr "Text to find:"
-#: gschem/src/x_dialog.c:3032
+#: gschem/src/x_dialog.c:3036
msgid "descend into hierarchy"
msgstr "descend into hierarchy"
-#: gschem/src/x_dialog.c:3097
+#: gschem/src/x_dialog.c:3101
msgid "Hide Text"
msgstr "Hide Text"
-#: gschem/src/x_dialog.c:3128
+#: gschem/src/x_dialog.c:3132
msgid "Hide text starting with:"
msgstr "Hide text starting with:"
-#: gschem/src/x_dialog.c:3197
+#: gschem/src/x_dialog.c:3201
msgid "Show Text"
msgstr "Show Text"
-#: gschem/src/x_dialog.c:3228
+#: gschem/src/x_dialog.c:3232
msgid "Show text starting with:"
msgstr "Show text starting with:"
-#: gschem/src/x_dialog.c:3685
+#: gschem/src/x_dialog.c:3689
msgid "S_elect the schematics you want to save:"
msgstr "S_elect the schematics you want to save:"
-#: gschem/src/x_dialog.c:3779
+#: gschem/src/x_dialog.c:3784
#, c-format
msgid "Save the changes to schematic \"%s\" before closing?"
msgstr "Save the changes to schematic \"%s\" before closing?"
-#: gschem/src/x_dialog.c:3785
+#: gschem/src/x_dialog.c:3790
#, c-format
msgid ""
"There are %d schematics with unsaved changes. Save changes before closing?"
msgstr ""
"There are %d schematics with unsaved changes. Save changes before closing?"
-#: gschem/src/x_dialog.c:3814
+#: gschem/src/x_dialog.c:3819
msgid "If you don't save, all your changes will be permanently lost."
msgstr "If you don't save, all your changes will be permanently lost."
-#: gschem/src/x_dialog.c:3834
+#: gschem/src/x_dialog.c:3839
msgid "_Close without saving"
msgstr "_Close without saving"
-#: gschem/src/x_dialog.c:4170
+#: gschem/src/x_dialog.c:4175
#, c-format
msgid ""
"<span weight=\"bold\" size=\"larger\">The input attribute \"%s\" is invalid\n"
@@ -1531,19 +1529,19 @@ msgstr ""
"The name cannot end with a space.\n"
"The value cannot start with a space."
-#: gschem/src/x_dialog.c:4172
+#: gschem/src/x_dialog.c:4177
msgid "Invalid Attribute"
msgstr "Invalid Attribute"
-#: gschem/src/x_dialog.c:4208
+#: gschem/src/x_dialog.c:4213
msgid "Pin type"
msgstr "Pin type"
-#: gschem/src/x_dialog.c:4232
+#: gschem/src/x_dialog.c:4237
msgid "Net pin"
msgstr "Net pin"
-#: gschem/src/x_dialog.c:4234
+#: gschem/src/x_dialog.c:4239
msgid "Bus pin (graphical)"
msgstr "Bus pin (graphical)"
@@ -1643,11 +1641,11 @@ msgstr "Image type"
msgid "Write image..."
msgstr "Write image..."
-#: gschem/src/x_log.c:188
+#: gschem/src/x_log.c:209
msgid "** Invalid UTF-8 in log message. See stderr or gschem.log.\n"
msgstr "** Invalid UTF-8 in log message. See stderr or gschem.log.\n"
-#: gschem/src/x_log.c:256
+#: gschem/src/x_log.c:288
msgid "Status"
msgstr "Status"
@@ -1723,69 +1721,60 @@ msgstr "/Down Symbol"
msgid "/Up"
msgstr "/Up"
-#: gschem/src/x_menus.c:321
+#: gschem/src/x_menus.c:323
#, c-format
msgid "Tried to set the sensitivity on non-existent menu item '%s'\n"
msgstr "Tried to set the sensitivity on non-existent menu item '%s'\n"
-#: gschem/src/x_menus.c:345
+#: gschem/src/x_menus.c:347
msgid "Popup_menu_item_factory doesn't exist!\n"
msgstr "Popup_menu_item_factory doesn't exist!\n"
-#: gschem/src/x_menus.c:358
+#: gschem/src/x_menus.c:360
msgid "Tried to set the sensitivity on a non-existent popup menu_item\n"
msgstr "Tried to set the sensitivity on a non-existent popup menu_item\n"
-#: gschem/src/x_menus.c:438
-#, c-format
-msgid "Couldn't open file %s\n"
-msgstr "Couldn't open file %s\n"
-
-#: gschem/src/x_menus.c:495
-msgid "Clear"
-msgstr "Clear"
-
-#: gschem/src/x_multiattrib.c:911
+#: gschem/src/x_multiattrib.c:915
msgid "Attributes with empty name are not allowed. Please set a name."
msgstr "Attributes with empty name are not allowed. Please set a name."
-#: gschem/src/x_multiattrib.c:1456
+#: gschem/src/x_multiattrib.c:1468
msgid "Show Value only"
msgstr "Show Value only"
-#: gschem/src/x_multiattrib.c:1458
+#: gschem/src/x_multiattrib.c:1470
msgid "Show Name only"
msgstr "Show Name only"
-#: gschem/src/x_multiattrib.c:1486
+#: gschem/src/x_multiattrib.c:1498
msgid "Promote"
msgstr "Promote"
-#: gschem/src/x_multiattrib.c:1490
+#: gschem/src/x_multiattrib.c:1502
msgid "Duplicate"
msgstr "Duplicate"
-#: gschem/src/x_multiattrib.c:1708
+#: gschem/src/x_multiattrib.c:1719
msgid "Edit Attributes"
msgstr "Edit Attributes"
-#: gschem/src/x_multiattrib.c:1826
+#: gschem/src/x_multiattrib.c:1837
msgid "Vis?"
msgstr "Vis?"
-#: gschem/src/x_multiattrib.c:1844
+#: gschem/src/x_multiattrib.c:1855
msgid "N"
msgstr "N"
-#: gschem/src/x_multiattrib.c:1862
+#: gschem/src/x_multiattrib.c:1873
msgid "V"
msgstr "V"
-#: gschem/src/x_multiattrib.c:1884
+#: gschem/src/x_multiattrib.c:1895
msgid "Show inherited attributes"
msgstr "Show inherited attributes"
-#: gschem/src/x_multiattrib.c:1900
+#: gschem/src/x_multiattrib.c:1911
msgid "Add Attribute"
msgstr "Add Attribute"
@@ -1809,23 +1798,23 @@ msgstr "Close Page"
msgid "Discard Page"
msgstr "Discard Page"
-#: gschem/src/x_pagesel.c:376
+#: gschem/src/x_pagesel.c:375
msgid "Page Manager"
msgstr "Page Manager"
-#: gschem/src/x_pagesel.c:432
+#: gschem/src/x_pagesel.c:431
msgid "Filename"
msgstr "Filename"
-#: gschem/src/x_pagesel.c:448
+#: gschem/src/x_pagesel.c:447
msgid "Changed"
msgstr "Changed"
-#: gschem/src/x_pagesel.c:468
+#: gschem/src/x_pagesel.c:467
msgid "Right click on the filename for more options..."
msgstr "Right click on the filename for more options..."
-#: gschem/src/x_preview.c:234
+#: gschem/src/x_preview.c:233
msgid "Preview Buffer"
msgstr "Preview Buffer"
@@ -1881,16 +1870,16 @@ msgstr "File:"
msgid "Command:"
msgstr "Command:"
-#: gschem/src/x_print.c:741
+#: gschem/src/x_print.c:745
msgid "No print destination specified\n"
msgstr "No print destination specified\n"
-#: gschem/src/x_print.c:748
+#: gschem/src/x_print.c:752
#, c-format
msgid "Cannot print current schematic to [%s]\n"
msgstr "Cannot print current schematic to [%s]\n"
-#: gschem/src/x_print.c:757
+#: gschem/src/x_print.c:761
#, c-format
msgid ""
"Error printing to file '%s'\n"
@@ -1899,7 +1888,7 @@ msgstr ""
"Error printing to file '%s'\n"
"Check the log window for more information"
-#: gschem/src/x_print.c:764
+#: gschem/src/x_print.c:768
#, c-format
msgid "Printed current schematic to [%s]\n"
msgstr "Printed current schematic to [%s]\n"
@@ -1908,6 +1897,11 @@ msgstr "Printed current schematic to [%s]\n"
msgid "Execute Script..."
msgstr "Execute Script..."
+#: gschem/src/x_script.c:66
+#, c-format
+msgid "Executing guile script [%s]\n"
+msgstr "Executing guile script [%s]\n"
+
#: gschem/src/x_window.c:81
#, c-format
msgid "Couldn't allocate gc\n"
@@ -2023,35 +2017,35 @@ msgstr "Failed to load file"
msgid "New file [%s]\n"
msgstr "New file [%s]\n"
-#: gschem/src/x_window.c:857
+#: gschem/src/x_window.c:855
#, c-format
msgid "Could NOT save page [%s]\n"
msgstr "Could NOT save page [%s]\n"
-#: gschem/src/x_window.c:858
+#: gschem/src/x_window.c:856
msgid "Error while trying to save"
msgstr "Error while trying to save"
-#: gschem/src/x_window.c:867
+#: gschem/src/x_window.c:865
#, c-format
msgid "Saved as [%s]\n"
msgstr "Saved as [%s]\n"
-#: gschem/src/x_window.c:869
+#: gschem/src/x_window.c:867
#, c-format
msgid "Saved [%s]\n"
msgstr "Saved [%s]\n"
-#: gschem/src/x_window.c:871
+#: gschem/src/x_window.c:869
msgid "Saved"
msgstr "Saved"
-#: gschem/src/x_window.c:945
+#: gschem/src/x_window.c:943
#, c-format
msgid "Discarding page [%s]\n"
msgstr "Discarding page [%s]\n"
-#: gschem/src/x_window.c:945
+#: gschem/src/x_window.c:943
#, c-format
msgid "Closing [%s]\n"
msgstr "Closing [%s]\n"
@@ -2092,7 +2086,7 @@ msgstr "Save _As..."
msgid "Save All"
msgstr "Save All"
-#: gschem/lib/system-gschemrc.scm:1386 gschem/lib/system-gschemrc.scm:1477
+#: gschem/lib/system-gschemrc.scm:1386 gschem/lib/system-gschemrc.scm:1478
msgid "_Revert"
msgstr "_Revert"
@@ -2104,7 +2098,7 @@ msgstr "_Print..."
msgid "Write _image..."
msgstr "Write _image..."
-#: gschem/lib/system-gschemrc.scm:1393 gschem/lib/system-gschemrc.scm:1478
+#: gschem/lib/system-gschemrc.scm:1393 gschem/lib/system-gschemrc.scm:1479
msgid "_Close"
msgstr "_Close"
@@ -2136,390 +2130,434 @@ msgstr "_Paste"
msgid "_Delete"
msgstr "_Delete"
-#: gschem/lib/system-gschemrc.scm:1412
+#: gschem/lib/system-gschemrc.scm:1409
+#, fuzzy
+msgid "Select All"
+msgstr "Select"
+
+#: gschem/lib/system-gschemrc.scm:1410
+#, fuzzy
+msgid "Deselect"
+msgstr "Select"
+
+#: gschem/lib/system-gschemrc.scm:1414
msgid "Rotate 90 Mode"
msgstr "Rotate 90 Mode"
-#: gschem/lib/system-gschemrc.scm:1415
+#: gschem/lib/system-gschemrc.scm:1417
msgid "Edit..."
msgstr "Edit..."
-#: gschem/lib/system-gschemrc.scm:1416
+#: gschem/lib/system-gschemrc.scm:1418
msgid "Edit Text..."
msgstr "Edit Text..."
-#: gschem/lib/system-gschemrc.scm:1417
+#: gschem/lib/system-gschemrc.scm:1419
msgid "Slot..."
msgstr "Slot..."
-#: gschem/lib/system-gschemrc.scm:1418
+#: gschem/lib/system-gschemrc.scm:1420
msgid "Color..."
msgstr "Colour..."
-#: gschem/lib/system-gschemrc.scm:1419
+#: gschem/lib/system-gschemrc.scm:1421
msgid "Line Width & Type..."
msgstr "Line Width & Type..."
-#: gschem/lib/system-gschemrc.scm:1420
+#: gschem/lib/system-gschemrc.scm:1422
msgid "Fill Type..."
msgstr "Fill Type..."
-#: gschem/lib/system-gschemrc.scm:1421
+#: gschem/lib/system-gschemrc.scm:1423
msgid "Symbol Translate..."
msgstr "Symbol Translate..."
-#: gschem/lib/system-gschemrc.scm:1425
+#: gschem/lib/system-gschemrc.scm:1427
msgid "Invoke Macro"
msgstr "Invoke Macro"
-#: gschem/lib/system-gschemrc.scm:1426
+#: gschem/lib/system-gschemrc.scm:1428
msgid "Embed Component/Picture"
msgstr "Embed Component/Picture"
-#: gschem/lib/system-gschemrc.scm:1427
+#: gschem/lib/system-gschemrc.scm:1429
msgid "Unembed Component/Picture"
msgstr "Unembed Component/Picture"
-#: gschem/lib/system-gschemrc.scm:1428
+#: gschem/lib/system-gschemrc.scm:1430
msgid "Update Component"
msgstr "Update Component"
-#: gschem/lib/system-gschemrc.scm:1429
+#: gschem/lib/system-gschemrc.scm:1431
msgid "Show/Hide Inv Text"
msgstr "Show/Hide Inv Text"
-#: gschem/lib/system-gschemrc.scm:1430
-msgid "Make Inv Text Vis"
-msgstr "Make Inv Text Vis"
-
-#: gschem/lib/system-gschemrc.scm:1436
+#: gschem/lib/system-gschemrc.scm:1437
msgid "Copy into 1"
msgstr "Copy into 1"
-#: gschem/lib/system-gschemrc.scm:1437
+#: gschem/lib/system-gschemrc.scm:1438
msgid "Copy into 2"
msgstr "Copy into 2"
-#: gschem/lib/system-gschemrc.scm:1438
+#: gschem/lib/system-gschemrc.scm:1439
msgid "Copy into 3"
msgstr "Copy into 3"
-#: gschem/lib/system-gschemrc.scm:1439
+#: gschem/lib/system-gschemrc.scm:1440
msgid "Copy into 4"
msgstr "Copy into 4"
-#: gschem/lib/system-gschemrc.scm:1440
+#: gschem/lib/system-gschemrc.scm:1441
msgid "Copy into 5"
msgstr "Copy into 5"
-#: gschem/lib/system-gschemrc.scm:1441
+#: gschem/lib/system-gschemrc.scm:1442
msgid "Cut into 1"
msgstr "Cut into 1"
-#: gschem/lib/system-gschemrc.scm:1442
+#: gschem/lib/system-gschemrc.scm:1443
msgid "Cut into 2"
msgstr "Cut into 2"
-#: gschem/lib/system-gschemrc.scm:1443
+#: gschem/lib/system-gschemrc.scm:1444
msgid "Cut into 3"
msgstr "Cut into 3"
-#: gschem/lib/system-gschemrc.scm:1444
+#: gschem/lib/system-gschemrc.scm:1445
msgid "Cut into 4"
msgstr "Cut into 4"
-#: gschem/lib/system-gschemrc.scm:1445
+#: gschem/lib/system-gschemrc.scm:1446
msgid "Cut into 5"
msgstr "Cut into 5"
-#: gschem/lib/system-gschemrc.scm:1446
+#: gschem/lib/system-gschemrc.scm:1447
msgid "Paste from 1"
msgstr "Paste from 1"
-#: gschem/lib/system-gschemrc.scm:1447
+#: gschem/lib/system-gschemrc.scm:1448
msgid "Paste from 2"
msgstr "Paste from 2"
-#: gschem/lib/system-gschemrc.scm:1448
+#: gschem/lib/system-gschemrc.scm:1449
msgid "Paste from 3"
msgstr "Paste from 3"
-#: gschem/lib/system-gschemrc.scm:1449
+#: gschem/lib/system-gschemrc.scm:1450
msgid "Paste from 4"
msgstr "Paste from 4"
-#: gschem/lib/system-gschemrc.scm:1450
+#: gschem/lib/system-gschemrc.scm:1451
msgid "Paste from 5"
msgstr "Paste from 5"
-#: gschem/lib/system-gschemrc.scm:1456
+#: gschem/lib/system-gschemrc.scm:1457
msgid "_Redraw"
msgstr "_Redraw"
-#: gschem/lib/system-gschemrc.scm:1457
+#: gschem/lib/system-gschemrc.scm:1458
msgid "_Pan"
msgstr "_Pan"
-#: gschem/lib/system-gschemrc.scm:1458
+#: gschem/lib/system-gschemrc.scm:1459
msgid "Zoom _Box"
msgstr "Zoom _Box"
-#: gschem/lib/system-gschemrc.scm:1459
+#: gschem/lib/system-gschemrc.scm:1460
msgid "Zoom _Extents"
msgstr "Zoom _Extents"
-#: gschem/lib/system-gschemrc.scm:1460
+#: gschem/lib/system-gschemrc.scm:1461
msgid "Zoom _In"
msgstr "Zoom _In"
-#: gschem/lib/system-gschemrc.scm:1461
+#: gschem/lib/system-gschemrc.scm:1462
msgid "Zoom _Out"
msgstr "Zoom _Out"
-#: gschem/lib/system-gschemrc.scm:1462
+#: gschem/lib/system-gschemrc.scm:1463
msgid "Zoom _Full"
msgstr "Zoom _Full"
-#: gschem/lib/system-gschemrc.scm:1464
+#: gschem/lib/system-gschemrc.scm:1465
msgid "_Dark color scheme"
msgstr "_Dark colour scheme"
-#: gschem/lib/system-gschemrc.scm:1465
+#: gschem/lib/system-gschemrc.scm:1466
msgid "_Light color scheme"
msgstr "_Light colour scheme"
-#: gschem/lib/system-gschemrc.scm:1466
+#: gschem/lib/system-gschemrc.scm:1467
#, fuzzy
msgid "B_W color scheme"
msgstr "_Dark colour scheme"
-#: gschem/lib/system-gschemrc.scm:1473
+#: gschem/lib/system-gschemrc.scm:1474
msgid "_Manager..."
msgstr "_Manager..."
-#: gschem/lib/system-gschemrc.scm:1474
+#: gschem/lib/system-gschemrc.scm:1475
msgid "_Previous"
msgstr "_Previous"
-#: gschem/lib/system-gschemrc.scm:1475
+#: gschem/lib/system-gschemrc.scm:1476
msgid "_Next"
msgstr "_Next"
-#: gschem/lib/system-gschemrc.scm:1476
+#: gschem/lib/system-gschemrc.scm:1477
msgid "Ne_w"
msgstr "Ne_w"
-#: gschem/lib/system-gschemrc.scm:1480
+#: gschem/lib/system-gschemrc.scm:1481
msgid "_Discard"
msgstr "_Discard"
-#: gschem/lib/system-gschemrc.scm:1486
+#: gschem/lib/system-gschemrc.scm:1487
msgid "_Component..."
msgstr "_Component..."
-#: gschem/lib/system-gschemrc.scm:1487
+#: gschem/lib/system-gschemrc.scm:1488
msgid "_Net"
msgstr "_Net"
-#: gschem/lib/system-gschemrc.scm:1488
+#: gschem/lib/system-gschemrc.scm:1489
msgid "B_us"
msgstr "B_us"
-#: gschem/lib/system-gschemrc.scm:1489
+#: gschem/lib/system-gschemrc.scm:1490
msgid "_Attribute..."
msgstr "_Attribute..."
-#: gschem/lib/system-gschemrc.scm:1490
+#: gschem/lib/system-gschemrc.scm:1491
msgid "_Text..."
msgstr "_Text..."
-#: gschem/lib/system-gschemrc.scm:1492
+#: gschem/lib/system-gschemrc.scm:1493
msgid "_Line"
msgstr "_Line"
-#: gschem/lib/system-gschemrc.scm:1493
+#: gschem/lib/system-gschemrc.scm:1494
msgid "_Box"
msgstr "_Box"
-#: gschem/lib/system-gschemrc.scm:1494
+#: gschem/lib/system-gschemrc.scm:1495
msgid "C_ircle"
msgstr "C_ircle"
-#: gschem/lib/system-gschemrc.scm:1495
+#: gschem/lib/system-gschemrc.scm:1496
msgid "A_rc"
msgstr "A_rc"
-#: gschem/lib/system-gschemrc.scm:1496
+#: gschem/lib/system-gschemrc.scm:1497
msgid "_Pin"
msgstr "_Pin"
-#: gschem/lib/system-gschemrc.scm:1497
+#: gschem/lib/system-gschemrc.scm:1498
msgid "Pictu_re..."
msgstr "Pictu_re..."
-#: gschem/lib/system-gschemrc.scm:1503
+#: gschem/lib/system-gschemrc.scm:1504
msgid "_Down Schematic"
msgstr "_Down Schematic"
-#: gschem/lib/system-gschemrc.scm:1504
+#: gschem/lib/system-gschemrc.scm:1505
msgid "Down _Symbol"
msgstr "Down _Symbol"
-#: gschem/lib/system-gschemrc.scm:1505
+#: gschem/lib/system-gschemrc.scm:1506
msgid "_Up"
msgstr "_Up"
-#: gschem/lib/system-gschemrc.scm:1506
+#: gschem/lib/system-gschemrc.scm:1507
msgid "D_ocumentation..."
msgstr "D_ocumentation"
-#: gschem/lib/system-gschemrc.scm:1512
+#: gschem/lib/system-gschemrc.scm:1513
msgid "_Attach"
msgstr "_Attach"
-#: gschem/lib/system-gschemrc.scm:1513
+#: gschem/lib/system-gschemrc.scm:1514
msgid "_Detach"
msgstr "_Detach"
-#: gschem/lib/system-gschemrc.scm:1514
+#: gschem/lib/system-gschemrc.scm:1515
msgid "Show _Value"
msgstr "Show _Value"
-#: gschem/lib/system-gschemrc.scm:1515
+#: gschem/lib/system-gschemrc.scm:1516
msgid "Show _Name"
msgstr "Show _Name"
-#: gschem/lib/system-gschemrc.scm:1516
+#: gschem/lib/system-gschemrc.scm:1517
msgid "Show _Both"
msgstr "Show _Both"
-#: gschem/lib/system-gschemrc.scm:1517
+#: gschem/lib/system-gschemrc.scm:1518
msgid "_Toggle Visibility"
msgstr "_Toggle Visibility"
-#: gschem/lib/system-gschemrc.scm:1519
+#: gschem/lib/system-gschemrc.scm:1520
msgid "_Find Specific Text..."
msgstr "_Find Specific Text..."
-#: gschem/lib/system-gschemrc.scm:1520
+#: gschem/lib/system-gschemrc.scm:1521
msgid "_Hide Specific Text..."
msgstr "_Hide Specific Text..."
-#: gschem/lib/system-gschemrc.scm:1521
+#: gschem/lib/system-gschemrc.scm:1522
msgid "_Show Specific Text..."
msgstr "_Show Specific Text..."
-#: gschem/lib/system-gschemrc.scm:1522
+#: gschem/lib/system-gschemrc.scm:1523
msgid "A_utonumber Text..."
msgstr "A_utonumber Text..."
-#: gschem/lib/system-gschemrc.scm:1528
+#: gschem/lib/system-gschemrc.scm:1529
msgid "_Text Size..."
msgstr "_Text Size..."
-#: gschem/lib/system-gschemrc.scm:1529
+#: gschem/lib/system-gschemrc.scm:1530
msgid "Cycle _grid styles"
msgstr "Cycle _grid styles"
-#: gschem/lib/system-gschemrc.scm:1530
+#: gschem/lib/system-gschemrc.scm:1531
msgid "Toggle _Snap On/Off"
msgstr "Toggle _Snap On/Off"
-#: gschem/lib/system-gschemrc.scm:1531
+#: gschem/lib/system-gschemrc.scm:1532
msgid "Snap Grid S_pacing..."
msgstr "Snap Grid S_pacing..."
-#: gschem/lib/system-gschemrc.scm:1532
+#: gschem/lib/system-gschemrc.scm:1533
msgid "Scale _up Grid Spacing"
msgstr "Scale _up Grid Spacing"
-#: gschem/lib/system-gschemrc.scm:1534
+#: gschem/lib/system-gschemrc.scm:1535
msgid "Scale _down Grid Spacing"
msgstr "Scale _down Grid Spacing"
-#: gschem/lib/system-gschemrc.scm:1536
+#: gschem/lib/system-gschemrc.scm:1537
msgid "Toggle _Outline/Box"
msgstr "Toggle _Outline/Box"
-#: gschem/lib/system-gschemrc.scm:1538
+#: gschem/lib/system-gschemrc.scm:1539
msgid "Toggle Net _Rubberband"
msgstr "Toggle Net _Rubberband"
-#: gschem/lib/system-gschemrc.scm:1539
+#: gschem/lib/system-gschemrc.scm:1540
msgid "Toggle _Magnetic Net"
msgstr "Toggle _Magnetic Net"
-#: gschem/lib/system-gschemrc.scm:1540
+#: gschem/lib/system-gschemrc.scm:1541
msgid "Show _Log Window..."
msgstr "Show _Log Window..."
-#: gschem/lib/system-gschemrc.scm:1542
+#: gschem/lib/system-gschemrc.scm:1543
msgid "Show _Coord Window..."
msgstr "Show _Coord Window..."
-#: gschem/lib/system-gschemrc.scm:1558
+#: gschem/lib/system-gschemrc.scm:1559
msgid "gEDA Docu_mentation..."
msgstr "gEDA Docu_mentation"
-#: gschem/lib/system-gschemrc.scm:1559
+#: gschem/lib/system-gschemrc.scm:1560
msgid "gschem _FAQ..."
msgstr "gschem _FAQ"
-#: gschem/lib/system-gschemrc.scm:1560
+#: gschem/lib/system-gschemrc.scm:1561
msgid "gEDA _Wiki..."
msgstr "gEDA _Wiki..."
-#: gschem/lib/system-gschemrc.scm:1561
+#: gschem/lib/system-gschemrc.scm:1562
msgid "Component D_ocumentation..."
msgstr "Component D_ocumentation"
-#: gschem/lib/system-gschemrc.scm:1563
+#: gschem/lib/system-gschemrc.scm:1564
msgid "_Hotkeys..."
msgstr "_Hotkeys"
-#: gschem/lib/system-gschemrc.scm:1564
+#: gschem/lib/system-gschemrc.scm:1565
msgid "_About..."
msgstr "_About..."
-#: gschem/lib/system-gschemrc.scm:1570
+#: gschem/lib/system-gschemrc.scm:1571
msgid "_File"
msgstr "_File"
-#: gschem/lib/system-gschemrc.scm:1571
+#: gschem/lib/system-gschemrc.scm:1572
msgid "_Edit"
msgstr "_Edit"
-#: gschem/lib/system-gschemrc.scm:1572
+#: gschem/lib/system-gschemrc.scm:1573
msgid "_Buffer"
msgstr "_Buffer"
-#: gschem/lib/system-gschemrc.scm:1573
+#: gschem/lib/system-gschemrc.scm:1574
msgid "_View"
msgstr "_View"
-#: gschem/lib/system-gschemrc.scm:1574
+#: gschem/lib/system-gschemrc.scm:1575
msgid "_Page"
msgstr "_Page"
-#: gschem/lib/system-gschemrc.scm:1575
+#: gschem/lib/system-gschemrc.scm:1576
msgid "_Add"
msgstr "_Add"
-#: gschem/lib/system-gschemrc.scm:1576
+#: gschem/lib/system-gschemrc.scm:1577
msgid "Hie_rarchy"
msgstr "Hie_rarchy"
-#: gschem/lib/system-gschemrc.scm:1577
+#: gschem/lib/system-gschemrc.scm:1578
msgid "A_ttributes"
msgstr "A_ttributes"
-#: gschem/lib/system-gschemrc.scm:1578
+#: gschem/lib/system-gschemrc.scm:1579
msgid "_Options"
msgstr "_Options"
-#: gschem/lib/system-gschemrc.scm:1579
+#: gschem/lib/system-gschemrc.scm:1580
msgid "_Help"
msgstr "_Help"
+#~ msgid "Scheme directory NOT set!\n"
+#~ msgstr "Scheme directory NOT set!\n"
+
+#~ msgid "MakeVisible"
+#~ msgstr "MakeVisible"
+
+#~ msgid ""
+#~ "Usage: %s [OPTIONS] schematic_filename1 ... schematic_filenameN\n"
+#~ " -q Quiet mode\n"
+#~ " -v Verbose mode on\n"
+#~ " -r filename Rc filename\n"
+#~ " -s filename Script (guile) filename\n"
+#~ " -o filename Output filename (for printing)\n"
+#~ " -p Automatically place the window\n"
+#~ " -t Print stroke information\n"
+#~ " -h Help; this message\n"
+#~ "\n"
+#~ msgstr ""
+#~ "Usage: %s [OPTIONS] schematic_filename1 ... schematic_filenameN\n"
+#~ " -q Quiet mode\n"
+#~ " -v Verbose mode on\n"
+#~ " -r filename Rc filename\n"
+#~ " -s filename Script (guile) filename\n"
+#~ " -o filename Output filename (for printing)\n"
+#~ " -p Automatically place the window\n"
+#~ " -t Print stroke information\n"
+#~ " -h Help; this message\n"
+#~ "\n"
+
+#~ msgid "Couldn't open file %s\n"
+#~ msgstr "Couldn't open file %s\n"
+
+#~ msgid "Clear"
+#~ msgstr "Clear"
+
+#~ msgid "Make Inv Text Vis"
+#~ msgstr "Make Inv Text Vis"
+
#~ msgid "Update Cues"
#~ msgstr "Update Cues"
diff --git a/gschem/po/es.po b/gschem/po/es.po
index 6c4967b..0777568 100644
--- a/gschem/po/es.po
+++ b/gschem/po/es.po
@@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: gschem VERSION\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2010-11-07 13:37+0000\n"
+"POT-Creation-Date: 2011-01-16 00:11-0500\n"
"PO-Revision-Date: 2010-02-14 01:04+0000\n"
"Last-Translator: Carlos Nieves Ã?nega <Unknown>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -23,17 +23,17 @@ msgstr ""
msgid "Zoom too small! Cannot zoom further.\n"
msgstr "¡Vista demasiado ampliada! No se puede ampliar más.\n"
-#: gschem/src/g_funcs.c:339 gschem/src/i_callbacks.c:68
+#: gschem/src/g_funcs.c:347 gschem/src/i_callbacks.c:68
#, c-format
msgid "Could not fork\n"
msgstr "No se ha podido crear un proceso hijo\n"
-#: gschem/src/g_funcs.c:355 gschem/src/i_callbacks.c:78
+#: gschem/src/g_funcs.c:363 gschem/src/i_callbacks.c:78
#, c-format
msgid "Could not invoke %s\n"
msgstr "No se ha podido llamar a %s\n"
-#: gschem/src/g_funcs.c:361 gschem/src/i_callbacks.c:82
+#: gschem/src/g_funcs.c:369 gschem/src/i_callbacks.c:82
msgid "Documentation commands not supported under MinGW.\n"
msgstr "No se pueden utilizar los comandos de documentación bajo MinGW.\n"
@@ -146,12 +146,12 @@ msgstr ""
"Se ha llamado a la función scrollpan-steps con un número de pasos no válido "
"[%d]\n"
-#: gschem/src/gschem.c:184
+#: gschem/src/gschem.c:188
#, c-format
msgid "gEDA/gschem version %s%s.%s\n"
msgstr "Versión de gEDA/gschem %s%s.%s\n"
-#: gschem/src/gschem.c:187
+#: gschem/src/gschem.c:191
msgid ""
"gEDA/gschem comes with ABSOLUTELY NO WARRANTY; see COPYING for more "
"details.\n"
@@ -159,12 +159,12 @@ msgstr ""
"gEDA/gschem no incluye NINGUNA GARANT�A; véase el fichero COPYING para más "
"detalles.\n"
-#: gschem/src/gschem.c:189
+#: gschem/src/gschem.c:193
msgid ""
"This is free software, and you are welcome to redistribute it under certain\n"
msgstr "Esto es software libre, y puede redistribuirlo bajo ciertas\n"
-#: gschem/src/gschem.c:191
+#: gschem/src/gschem.c:195
msgid ""
"conditions; please see the COPYING file for more details.\n"
"\n"
@@ -172,17 +172,17 @@ msgstr ""
"condiciones; por favor vea el fichero COPYING para más detalles.\n"
"\n"
-#: gschem/src/gschem.c:194
+#: gschem/src/gschem.c:198
#, c-format
msgid "This is the MINGW32 port.\n"
msgstr "�sta es la adaptación MINGW32.\n"
-#: gschem/src/gschem.c:198
+#: gschem/src/gschem.c:202
#, c-format
msgid "Current locale settings: %s\n"
msgstr "Entorno actual de locale: %s\n"
-#: gschem/src/gschem.c:213
+#: gschem/src/gschem.c:218
msgid ""
"You must set the GEDADATA environment variable!\n"
"\n"
@@ -194,31 +194,21 @@ msgstr ""
"gschem no puede encontrar sus archivos de datos. Debe configurar la variable "
"de entorno GEDADATA con el camino adecuado.\n"
-#: gschem/src/gschem.c:248
+#: gschem/src/gschem.c:256
#, c-format
msgid "Couldn't find init scm file [%s]\n"
msgstr "No se ha podido encontrar el fichero de inicialización scm [%s]\n"
-#: gschem/src/gschem.c:252
+#: gschem/src/gschem.c:260
#, c-format
msgid "Read init scm file [%s]\n"
msgstr "LeÃdo fichero de inicialización scm [%s]\n"
-#: gschem/src/gschem.c:256
+#: gschem/src/gschem.c:264
#, c-format
msgid "Failed to read init scm file [%s]\n"
msgstr "Fallo al leer fichero de inicialización scm [%s]\n"
-#: gschem/src/gschem.c:317
-#, c-format
-msgid "Scheme directory NOT set!\n"
-msgstr "¡Directorio de Scheme no especificado!\n"
-
-#: gschem/src/gschem.c:324 gschem/src/x_script.c:66
-#, c-format
-msgid "Executing guile script [%s]\n"
-msgstr "Ejecutando programa de guile [%s]\n"
-
#: gschem/src/gschem_cairo.c:310
#, c-format
msgid "Unknown end for line (%d)\n"
@@ -242,11 +232,11 @@ msgstr "Modo Componentes"
msgid "Text Mode"
msgstr "Modo Texto"
-#: gschem/src/i_basic.c:84 gschem/lib/system-gschemrc.scm:1409
+#: gschem/src/i_basic.c:84 gschem/lib/system-gschemrc.scm:1411
msgid "Copy Mode"
msgstr "Copiar"
-#: gschem/src/i_basic.c:87 gschem/lib/system-gschemrc.scm:1411
+#: gschem/src/i_basic.c:87 gschem/lib/system-gschemrc.scm:1413
msgid "Move Mode"
msgstr "Mover"
@@ -254,7 +244,7 @@ msgstr "Mover"
msgid "Rotate Mode"
msgstr "Rotar"
-#: gschem/src/i_basic.c:91 gschem/lib/system-gschemrc.scm:1413
+#: gschem/src/i_basic.c:91 gschem/lib/system-gschemrc.scm:1415
msgid "Mirror Mode"
msgstr "Voltear"
@@ -307,22 +297,22 @@ msgstr "Modo Arco"
msgid "Pin Mode"
msgstr "Modo Pin"
-#: gschem/src/i_basic.c:135 gschem/src/i_callbacks.c:544
-#: gschem/src/i_callbacks.c:568
+#: gschem/src/i_basic.c:135 gschem/src/i_callbacks.c:576
+#: gschem/src/i_callbacks.c:600
msgid "Copy"
msgstr "Copiar"
-#: gschem/src/i_basic.c:137 gschem/src/i_callbacks.c:634
-#: gschem/src/i_callbacks.c:658
+#: gschem/src/i_basic.c:137 gschem/src/i_callbacks.c:666
+#: gschem/src/i_callbacks.c:690
msgid "Move"
msgstr "Mover"
-#: gschem/src/i_basic.c:139 gschem/src/i_callbacks.c:589
-#: gschem/src/i_callbacks.c:613
+#: gschem/src/i_basic.c:139 gschem/src/i_callbacks.c:621
+#: gschem/src/i_callbacks.c:645
msgid "Multiple Copy"
msgstr "Copia múltiple"
-#: gschem/src/i_basic.c:142 gschem/lib/system-gschemrc.scm:1410
+#: gschem/src/i_basic.c:142 gschem/lib/system-gschemrc.scm:1412
msgid "Multiple Copy Mode"
msgstr "Modo de copia múltiple"
@@ -342,7 +332,7 @@ msgstr "Reajuste a la rejilla activado"
msgid "Action"
msgstr "Acción"
-#: gschem/src/i_basic.c:260 gschem/src/x_dialog.c:2312
+#: gschem/src/i_basic.c:260 gschem/src/x_dialog.c:2316
#: gschem/src/x_window.c:491
msgid "Stroke"
msgstr "Gesto"
@@ -373,7 +363,7 @@ msgstr "Rejilla(%s, %s)"
msgid "Documentation for [%s,%s,%s,%s]\n"
msgstr "Documentación de [%s, %s, %s, %s]\n"
-#: gschem/src/i_callbacks.c:123 gschem/src/i_callbacks.c:1699
+#: gschem/src/i_callbacks.c:123 gschem/src/i_callbacks.c:1706
#, c-format
msgid "New page created [%s]\n"
msgstr "Se ha creado una página nueva [%s]\n"
@@ -395,72 +385,72 @@ msgstr "Guardado todo"
msgid "Closing Window\n"
msgstr "Cerrando ventana\n"
-#: gschem/src/i_callbacks.c:549 gschem/src/i_callbacks.c:594
-#: gschem/src/i_callbacks.c:639
+#: gschem/src/i_callbacks.c:581 gschem/src/i_callbacks.c:626
+#: gschem/src/i_callbacks.c:671
msgid "Select objs first"
msgstr "Antes seleccione objetos"
-#: gschem/src/i_callbacks.c:678 gschem/src/x_multiattrib.c:1491
+#: gschem/src/i_callbacks.c:710 gschem/src/x_multiattrib.c:1503
msgid "Delete"
msgstr "Borrar"
-#: gschem/src/i_callbacks.c:703
+#: gschem/src/i_callbacks.c:735
msgid "Edit"
msgstr "Editar"
-#: gschem/src/i_callbacks.c:718
+#: gschem/src/i_callbacks.c:750
msgid "Edit pin type"
msgstr "Editar tipo de pin"
-#: gschem/src/i_callbacks.c:737
+#: gschem/src/i_callbacks.c:769
msgid "Edit Text"
msgstr "Editar texto"
-#: gschem/src/i_callbacks.c:760
+#: gschem/src/i_callbacks.c:792
msgid "Slot"
msgstr "Elemento"
-#: gschem/src/i_callbacks.c:777
+#: gschem/src/i_callbacks.c:809
msgid "Color"
msgstr "Color"
-#: gschem/src/i_callbacks.c:814 gschem/src/i_callbacks.c:859
+#: gschem/src/i_callbacks.c:846 gschem/src/i_callbacks.c:891
msgid "Rotate"
msgstr "Rotar"
-#: gschem/src/i_callbacks.c:882 gschem/src/i_callbacks.c:907
+#: gschem/src/i_callbacks.c:913 gschem/src/i_callbacks.c:938
msgid "Mirror"
msgstr "Voltear"
-#: gschem/src/i_callbacks.c:928 gschem/src/x_dialog.c:2315
-#: gschem/lib/system-gschemrc.scm:1422
+#: gschem/src/i_callbacks.c:959 gschem/src/x_dialog.c:2319
+#: gschem/lib/system-gschemrc.scm:1424
msgid "Lock"
msgstr "Fijar"
-#: gschem/src/i_callbacks.c:946 gschem/lib/system-gschemrc.scm:1423
+#: gschem/src/i_callbacks.c:977 gschem/lib/system-gschemrc.scm:1425
msgid "Unlock"
msgstr "Desfijar"
-#: gschem/src/i_callbacks.c:964 gschem/src/x_dialog.c:1734
+#: gschem/src/i_callbacks.c:995 gschem/src/x_dialog.c:1737
msgid "Translate"
msgstr "Mover"
-#: gschem/src/i_callbacks.c:967
+#: gschem/src/i_callbacks.c:998
msgid "WARNING: Do not translate with snap off!\n"
msgstr ""
"ADVERTENCIA: ¡No mueva objetos con el ajuste a la rejilla desactivado!\n"
-#: gschem/src/i_callbacks.c:968
+#: gschem/src/i_callbacks.c:999
msgid "WARNING: Turning snap on and continuing with translate.\n"
msgstr ""
"ADVERTENCIA: Activando el ajuste a la rejilla y continuando con el "
"movimiento.\n"
-#: gschem/src/i_callbacks.c:975
+#: gschem/src/i_callbacks.c:1006
msgid "WARNING: Snap grid size is not equal to 100!\n"
msgstr "ADVERTENCIA: ¡El tamaño de la rejilla no es 100!\n"
-#: gschem/src/i_callbacks.c:977
+#: gschem/src/i_callbacks.c:1008
msgid ""
"WARNING: If you are translating a symbol to the origin, the snap grid size "
"should be set to 100\n"
@@ -468,176 +458,172 @@ msgstr ""
"ADVERTENCIA: Si está moviendo un sÃmbolo al origen, el tamaño de la "
"rejilladebe ser de 100\n"
-#: gschem/src/i_callbacks.c:1008
+#: gschem/src/i_callbacks.c:1039
msgid "Embed"
msgstr "Incrustar"
-#: gschem/src/i_callbacks.c:1047
+#: gschem/src/i_callbacks.c:1078
msgid "Unembed"
msgstr "Desincrustar"
-#: gschem/src/i_callbacks.c:1089
+#: gschem/src/i_callbacks.c:1120
msgid "Update"
msgstr "Actualizar"
-#: gschem/src/i_callbacks.c:1136
+#: gschem/src/i_callbacks.c:1167
msgid "ShowHidden"
msgstr "Mostrar ocultos"
-#: gschem/src/i_callbacks.c:1160
-msgid "MakeVisible"
-msgstr "Hacer visible"
-
-#: gschem/src/i_callbacks.c:1466 gschem/src/i_callbacks.c:1538
+#: gschem/src/i_callbacks.c:1473 gschem/src/i_callbacks.c:1545
msgid "Pan"
msgstr "Centrar respecto al cursor"
-#: gschem/src/i_callbacks.c:1743
+#: gschem/src/i_callbacks.c:1750
msgid "Really revert page?"
msgstr "¿Seguro que quiere recargar la página?"
-#: gschem/src/i_callbacks.c:1813
+#: gschem/src/i_callbacks.c:1820
msgid "Copy to clipboard"
msgstr "Copiar al portapapeles"
-#: gschem/src/i_callbacks.c:1831
+#: gschem/src/i_callbacks.c:1838
msgid "Cut to clipboard"
msgstr "Cortar al portapapeles"
-#: gschem/src/i_callbacks.c:1849
+#: gschem/src/i_callbacks.c:1856
msgid "Paste from clipboard"
msgstr "Pegar desde el portapapeles"
-#: gschem/src/i_callbacks.c:1861 gschem/src/i_callbacks.c:2100
-#: gschem/src/i_callbacks.c:2122 gschem/src/i_callbacks.c:2144
-#: gschem/src/i_callbacks.c:2166 gschem/src/i_callbacks.c:2188
+#: gschem/src/i_callbacks.c:1868 gschem/src/i_callbacks.c:2107
+#: gschem/src/i_callbacks.c:2129 gschem/src/i_callbacks.c:2151
+#: gschem/src/i_callbacks.c:2173 gschem/src/i_callbacks.c:2195
msgid "Empty buffer"
msgstr "Buffer vacÃo"
-#: gschem/src/i_callbacks.c:1906
+#: gschem/src/i_callbacks.c:1913
msgid "Copy 1"
msgstr "Copiar 1"
-#: gschem/src/i_callbacks.c:1925
+#: gschem/src/i_callbacks.c:1932
msgid "Copy 2"
msgstr "Copiar 2"
-#: gschem/src/i_callbacks.c:1944
+#: gschem/src/i_callbacks.c:1951
msgid "Copy 3"
msgstr "Copiar 3"
-#: gschem/src/i_callbacks.c:1963
+#: gschem/src/i_callbacks.c:1970
msgid "Copy 4"
msgstr "Copiar 4"
-#: gschem/src/i_callbacks.c:1982
+#: gschem/src/i_callbacks.c:1989
msgid "Copy 5"
msgstr "Copiar 5"
-#: gschem/src/i_callbacks.c:2001
+#: gschem/src/i_callbacks.c:2008
msgid "Cut 1"
msgstr "Cortar 1"
-#: gschem/src/i_callbacks.c:2020
+#: gschem/src/i_callbacks.c:2027
msgid "Cut 2"
msgstr "Cortar 2"
-#: gschem/src/i_callbacks.c:2039
+#: gschem/src/i_callbacks.c:2046
msgid "Cut 3"
msgstr "Cortar 3"
-#: gschem/src/i_callbacks.c:2058
+#: gschem/src/i_callbacks.c:2065
msgid "Cut 4"
msgstr "Cortar 4"
-#: gschem/src/i_callbacks.c:2077
+#: gschem/src/i_callbacks.c:2084
msgid "Cut 5"
msgstr "Cortar 5"
-#: gschem/src/i_callbacks.c:2093
+#: gschem/src/i_callbacks.c:2100
msgid "Paste 1"
msgstr "Pegar 1"
-#: gschem/src/i_callbacks.c:2115
+#: gschem/src/i_callbacks.c:2122
msgid "Paste 2"
msgstr "Pegar 2"
-#: gschem/src/i_callbacks.c:2137
+#: gschem/src/i_callbacks.c:2144
msgid "Paste 3"
msgstr "Pegar 3"
-#: gschem/src/i_callbacks.c:2159
+#: gschem/src/i_callbacks.c:2166
msgid "Paste 4"
msgstr "Pegar 4"
-#: gschem/src/i_callbacks.c:2181
+#: gschem/src/i_callbacks.c:2188
msgid "Paste 5"
msgstr "Pegar 5"
-#: gschem/src/i_callbacks.c:2318 gschem/src/x_window.c:355
+#: gschem/src/i_callbacks.c:2325 gschem/src/x_window.c:355
msgid "Component"
msgstr "Componente"
-#: gschem/src/i_callbacks.c:2354 gschem/src/i_callbacks.c:2373
-#: gschem/src/x_dialog.c:2285
+#: gschem/src/i_callbacks.c:2361 gschem/src/i_callbacks.c:2380
+#: gschem/src/x_dialog.c:2289
msgid "Attribute"
msgstr "Propiedad"
-#: gschem/src/i_callbacks.c:2395 gschem/src/i_callbacks.c:2422
-#: gschem/src/x_dialog.c:2282
+#: gschem/src/i_callbacks.c:2402 gschem/src/i_callbacks.c:2429
+#: gschem/src/x_dialog.c:2286
msgid "Net"
msgstr "Conexión"
-#: gschem/src/i_callbacks.c:2466 gschem/src/i_callbacks.c:2493
-#: gschem/src/x_dialog.c:2300 gschem/src/x_window.c:375
+#: gschem/src/i_callbacks.c:2473 gschem/src/i_callbacks.c:2500
+#: gschem/src/x_dialog.c:2304 gschem/src/x_window.c:375
msgid "Bus"
msgstr "Bus"
-#: gschem/src/i_callbacks.c:2574 gschem/src/i_callbacks.c:2597
+#: gschem/src/i_callbacks.c:2581 gschem/src/i_callbacks.c:2604
msgid "Line"
msgstr "LÃnea"
-#: gschem/src/i_callbacks.c:2619 gschem/src/i_callbacks.c:2642
+#: gschem/src/i_callbacks.c:2626 gschem/src/i_callbacks.c:2649
msgid "Box"
msgstr "Rectángulo"
-#: gschem/src/i_callbacks.c:2698 gschem/src/i_callbacks.c:2722
+#: gschem/src/i_callbacks.c:2705 gschem/src/i_callbacks.c:2729
msgid "Circle"
msgstr "CÃrculo"
-#: gschem/src/i_callbacks.c:2744 gschem/src/i_callbacks.c:2767
+#: gschem/src/i_callbacks.c:2751 gschem/src/i_callbacks.c:2774
msgid "Arc"
msgstr "Arco"
-#: gschem/src/i_callbacks.c:2789 gschem/src/i_callbacks.c:2812
-#: gschem/src/x_dialog.c:2273
+#: gschem/src/i_callbacks.c:2796 gschem/src/i_callbacks.c:2819
+#: gschem/src/x_dialog.c:2277
msgid "Pin"
msgstr "Pin"
-#: gschem/src/i_callbacks.c:2871
+#: gschem/src/i_callbacks.c:2878
#, c-format
msgid "Searching for source [%s]\n"
msgstr "Buscando origen [%s]\n"
-#: gschem/src/i_callbacks.c:2895
+#: gschem/src/i_callbacks.c:2902
#, c-format
msgid "Cannot find source [%s]\n"
msgstr "No se ha podido encontrar la fuente [%s]\n"
-#: gschem/src/i_callbacks.c:2964
+#: gschem/src/i_callbacks.c:2965
#, c-format
msgid "Searching for symbol [%s]\n"
msgstr "Buscando sÃmbolo [%s]\n"
-#: gschem/src/i_callbacks.c:2970
+#: gschem/src/i_callbacks.c:2971
msgid "Symbol is not a real file. Symbol cannot be loaded.\n"
msgstr "El sÃmbolo no es un archivo fÃsico. No se puede cargar el sÃmbolo.\n"
-#: gschem/src/i_callbacks.c:3001
+#: gschem/src/i_callbacks.c:3002
msgid "Cannot find any schematics above the current one!\n"
msgstr "¡No se ha podido encontrar ningún esquema jerárquico superior!\n"
-#: gschem/src/i_callbacks.c:3055
+#: gschem/src/i_callbacks.c:3056
msgid ""
"This command retrieves the component documentation from the web, but there "
"is no component selected"
@@ -645,84 +631,84 @@ msgstr ""
"Este comando consigue la información del componente de internet, pero no hay "
"ningún componente seleccionado"
-#: gschem/src/i_callbacks.c:3083
+#: gschem/src/i_callbacks.c:3084
msgid "Attach"
msgstr "Adjuntar"
-#: gschem/src/i_callbacks.c:3130
+#: gschem/src/i_callbacks.c:3131
msgid "Detach"
msgstr "No adjuntar"
-#: gschem/src/i_callbacks.c:3165
+#: gschem/src/i_callbacks.c:3166
msgid "ShowN"
msgstr "Mostrar nombre"
-#: gschem/src/i_callbacks.c:3201
+#: gschem/src/i_callbacks.c:3202
msgid "ShowV"
msgstr "Mostrar valor"
-#: gschem/src/i_callbacks.c:3237
+#: gschem/src/i_callbacks.c:3238
msgid "ShowB"
msgstr "Mostrar ambos"
-#: gschem/src/i_callbacks.c:3274
+#: gschem/src/i_callbacks.c:3275
msgid "VisToggle"
msgstr "Cambiar visibilidad"
-#: gschem/src/i_callbacks.c:3304
+#: gschem/src/i_callbacks.c:3305
#, c-format
msgid "Sorry but this is a non-functioning menu option\n"
msgstr "Disculpe. Esta opción del menú no funciona\n"
-#: gschem/src/i_callbacks.c:3394
+#: gschem/src/i_callbacks.c:3395
msgid "Action feedback mode set to OUTLINE\n"
msgstr "Modo de realimentación seleccionado: SILUETA\n"
-#: gschem/src/i_callbacks.c:3397
+#: gschem/src/i_callbacks.c:3398
msgid "Action feedback mode set to BOUNDINGBOX\n"
msgstr "Modo de realimentación seleccionado: CONTENEDOR\n"
-#: gschem/src/i_callbacks.c:3422
+#: gschem/src/i_callbacks.c:3423
msgid "Grid OFF\n"
msgstr "Rejilla DESACTIVADA\n"
-#: gschem/src/i_callbacks.c:3423
+#: gschem/src/i_callbacks.c:3424
msgid "Dot grid selected\n"
msgstr "Seleccionada rejilla de puntos\n"
-#: gschem/src/i_callbacks.c:3424
+#: gschem/src/i_callbacks.c:3425
msgid "Mesh grid selected\n"
msgstr "Seleccionada rejilla de malla\n"
-#: gschem/src/i_callbacks.c:3445
+#: gschem/src/i_callbacks.c:3446
msgid "Snap OFF (CAUTION!)\n"
msgstr "¡PRECAUCI�N!: Ajuste a la rejilla DESACTIVADO\n"
-#: gschem/src/i_callbacks.c:3448
+#: gschem/src/i_callbacks.c:3449
msgid "Snap ON\n"
msgstr "Ajuste a la rejilla ACTIVADO\n"
-#: gschem/src/i_callbacks.c:3451
+#: gschem/src/i_callbacks.c:3452
msgid "Snap back to the grid (CAUTION!)\n"
msgstr "Reajuste a la rejilla (¡PRECAUCI�N!)\n"
-#: gschem/src/i_callbacks.c:3477
+#: gschem/src/i_callbacks.c:3478
msgid "Rubber band OFF \n"
msgstr "Goma de borrar DESACT \n"
-#: gschem/src/i_callbacks.c:3480
+#: gschem/src/i_callbacks.c:3481
msgid "Rubber band ON\n"
msgstr "Goma de borrar ACT\n"
-#: gschem/src/i_callbacks.c:3495
+#: gschem/src/i_callbacks.c:3496
msgid "magnetic net mode: ON\n"
msgstr "Modo de Ayuda a la conexión: ACTIVADO\n"
-#: gschem/src/i_callbacks.c:3498
+#: gschem/src/i_callbacks.c:3499
msgid "magnetic net mode: OFF\n"
msgstr "Modo de Ayuda a la conexión: DESACTIVADO\n"
-#: gschem/src/o_box.c:153
+#: gschem/src/o_box.c:149
#, c-format
msgid "Unknown type for box (fill)!\n"
msgstr "¡Tipo de relleno de rectángulo desconocido!\n"
@@ -744,19 +730,19 @@ msgstr ""
"Se ha recibido un número de memoria intermedia no válida en la función "
"o_buffer_paste_start\n"
-#: gschem/src/o_bus.c:118
+#: gschem/src/o_bus.c:117
#, c-format
msgid "Got an invalid which one in o_bus_draw_stretch\n"
msgstr ""
"Se ha recibido un parámetro no válido (\"whichone\") en la función "
"o_bus_draw_stretch\n"
-#: gschem/src/o_circle.c:134
+#: gschem/src/o_circle.c:130
#, c-format
msgid "Unknown type for circle (fill)!\n"
msgstr "¡Tipo de relleno de cÃrculo desconocido!\n"
-#: gschem/src/o_complex.c:243 gschem/src/o_complex.c:247
+#: gschem/src/o_complex.c:237 gschem/src/o_complex.c:241
#, c-format
msgid "Translating schematic [%d %d]\n"
msgstr "Convirtiendo esquema [%d %d]\n"
@@ -774,41 +760,41 @@ msgstr "Objeto previamente fijado\n"
msgid "Object already unlocked\n"
msgstr "El objeto no estaba fijado\n"
-#: gschem/src/o_misc.c:413
+#: gschem/src/o_misc.c:409
msgid "Hidden text is now visible\n"
msgstr "El texto oculto es ahora visible\n"
-#: gschem/src/o_misc.c:415
+#: gschem/src/o_misc.c:411
msgid "Hidden text is now invisible\n"
msgstr "El texto oculto es ahora invisible\n"
-#: gschem/src/o_misc.c:668
+#: gschem/src/o_misc.c:636
#, c-format
msgid "Could not find symbol [%s] in library. Update failed.\n"
msgstr ""
"No se pudo encontrar el sÃmbolo [%s] en la librerÃa. Error al actualizar.\n"
-#: gschem/src/o_misc.c:783
+#: gschem/src/o_misc.c:751
#, c-format
msgid "o_autosave_backups: Can't get the real filename of %s."
msgstr ""
"o_autosave_backups: Imposible averiguar el nombre de archivo real de %s."
-#: gschem/src/o_misc.c:827
+#: gschem/src/o_misc.c:795
#, c-format
msgid "Could NOT set previous backup file [%s] read-write\n"
msgstr ""
"NO se han podido cambiar los permisos de la copia de seguridad anterior [%s] "
"a lectura-escritura\n"
-#: gschem/src/o_misc.c:845
+#: gschem/src/o_misc.c:815
#, c-format
msgid "Could NOT set backup file [%s] readonly\n"
msgstr ""
"NO se han podido cambiar los permisos de la copia de seguridad anterior [%s] "
"a sólo lectura\n"
-#: gschem/src/o_misc.c:850
+#: gschem/src/o_misc.c:820
#, c-format
msgid "Could NOT save backup file [%s]\n"
msgstr "NO se ha podido guardar la copia de seguridad [%s]\n"
@@ -832,44 +818,44 @@ msgstr ""
"Se ha recibido un objeto que no es una lÃnea en la función "
"o_move_check_endpoint\n"
-#: gschem/src/o_net.c:159
+#: gschem/src/o_net.c:158
#, c-format
msgid "Got an invalid which one in o_net_draw_stretch\n"
msgstr ""
"Se ha recibido un parámetro no válido (\"whichone\") en la función "
"o_net_draw_stretch\n"
-#: gschem/src/o_net.c:538
+#: gschem/src/o_net.c:537
msgid "Warning: Starting net at off grid coordinate\n"
msgstr ""
"Advertencia: se ha iniciado la conexión en una coordenada fuera de la "
"rejilla\n"
-#: gschem/src/o_net.c:600
+#: gschem/src/o_net.c:599
msgid "Warning: Ending net at off grid coordinate\n"
msgstr ""
"Advertencia: se ha finalizado la conexión en una coordenada fuera de la "
"rejilla\n"
-#: gschem/src/o_net.c:932 gschem/src/o_net.c:969 gschem/src/o_net.c:1040
-#: gschem/src/o_net.c:1076
+#: gschem/src/o_net.c:931 gschem/src/o_net.c:968 gschem/src/o_net.c:1039
+#: gschem/src/o_net.c:1075
#, c-format
msgid "Tried to add more than two bus rippers. Internal gschem error.\n"
msgstr ""
"Se ha intentado añadir más de dos conexiones a bus. Error interno de "
"gschem.\n"
-#: gschem/src/o_net.c:1144
+#: gschem/src/o_net.c:1143
#, c-format
msgid "Bus ripper symbol [%s] was not found in any component library\n"
msgstr "No se ha encontrado el sÃmbolo %s en ninguna librerÃa de componentes\n"
-#: gschem/src/o_path.c:352
+#: gschem/src/o_path.c:348
#, c-format
msgid "Unknown type for path (fill)!\n"
msgstr "¡Tipo de camino (relleno) desconocido!\n"
-#: gschem/src/o_picture.c:163 gschem/src/o_picture.c:539
+#: gschem/src/o_picture.c:163 gschem/src/o_picture.c:537
#, c-format
msgid "Failed to load picture: %s"
msgstr "Fallo al cargar la imagen: %s"
@@ -878,7 +864,7 @@ msgstr "Fallo al cargar la imagen: %s"
msgid "Picture"
msgstr "Imagen"
-#: gschem/src/o_picture.c:447 gschem/src/x_attribedit.c:141
+#: gschem/src/o_picture.c:445 gschem/src/x_attribedit.c:141
#, c-format
msgid "ERROR: NULL object!\n"
msgstr "ERROR: ¡objeto vacÃo (NULL)!\n"
@@ -899,33 +885,46 @@ msgstr "No se permiten múltiples elementos para este componente\n"
msgid "New slot number out of range\n"
msgstr "El nuevo número de elemento está fuera de rango\n"
-#: gschem/src/o_undo.c:304
+#: gschem/src/o_undo.c:303
msgid "Undo/Redo disabled in rc file\n"
msgstr "¡Deshacer/Rehacer deshabilitado en el fichero rc!\n"
-#: gschem/src/parsecmd.c:47
+#: gschem/src/parsecmd.c:81
#, c-format
msgid ""
-"Usage: %s [OPTIONS] schematic_filename1 ... schematic_filenameN\n"
-" -q Quiet mode\n"
-" -v Verbose mode on\n"
-" -r filename Rc filename\n"
-" -s filename Script (guile) filename\n"
-" -o filename Output filename (for printing)\n"
-" -p Automatically place the window\n"
-" -t Print stroke information\n"
-" -h Help; this message\n"
+"Usage: %s [OPTION ...] [--] [FILE ...]\n"
"\n"
-msgstr ""
-"Modo de uso: %s [OPCIONES] nombre_de_esquema_1·...·nombre_de_esquema_N\n"
-" -q No mostrar mensajes adicionales\n"
-" -v Mostrar mensajes adicionales\n"
-" -r archivo Usar archivo Rc\n"
-" -s archivo Ejecutar fichero (guile)\n"
-" -o archivo Fichero de salida (para impresión)\n"
-" -p Posicionar automáticamente la ventana\n"
-" -h Ayuda; éste mensaje\n"
+"Interactively edit gEDA schematics or symbols. If one or more FILEs\n"
+"are specified, open them for editing; otherwise, create a new, empty\n"
+"schematic.\n"
"\n"
+"Options:\n"
+" -q, --quiet Quiet mode.\n"
+" -v, --verbose Verbose mode.\n"
+" -r, --config-file=FILE Additional configuration file to load.\n"
+" -L DIR Add DIR to Scheme search path.\n"
+" -c EXPR Scheme expression to run at startup.\n"
+" -s FILE Scheme script to run at startup.\n"
+" -o, --output=FILE Output filename (for printing).\n"
+" -p Automatically place the window.\n"
+" -V, --version Show version information.\n"
+" -h, --help Help; this message.\n"
+" -- Treat all remaining arguments as filenames.\n"
+"\n"
+"Report bugs to <geda-bug@xxxxxxxx>\n"
+"gEDA/gaf homepage: <http://gpleda.org>\n"
+msgstr ""
+
+#: gschem/src/parsecmd.c:115
+#, c-format
+msgid ""
+"gEDA %s (g%.7s)\n"
+"Copyright (C) 1998-2011 gEDA developers\n"
+"This is free software, and you are welcome to redistribute it under\n"
+"certain conditions. For details, see the file `COPYING', which is\n"
+"included in the gEDA distribution.\n"
+"There is NO WARRANTY, to the extent permitted by law.\n"
+msgstr ""
#: gschem/src/x_attribedit.c:127
#, c-format
@@ -937,56 +936,56 @@ msgstr ""
msgid "Single Attribute Editor"
msgstr "Editor de una única propiedad"
-#: gschem/src/x_attribedit.c:358
+#: gschem/src/x_attribedit.c:359
msgid "<b>Edit Attribute</b>"
msgstr "<b>Editar propiedades</b>"
-#: gschem/src/x_attribedit.c:360
+#: gschem/src/x_attribedit.c:361
msgid "<b>Add Attribute</b>"
msgstr "<b>Añadir propiedad</b>"
-#: gschem/src/x_attribedit.c:376 gschem/src/x_multiattrib.c:1916
+#: gschem/src/x_attribedit.c:377 gschem/src/x_multiattrib.c:1927
msgid "Name:"
msgstr "Nombre:"
-#: gschem/src/x_attribedit.c:393 gschem/src/x_multiattrib.c:1935
+#: gschem/src/x_attribedit.c:394 gschem/src/x_multiattrib.c:1946
msgid "Value:"
msgstr "Valor:"
-#: gschem/src/x_attribedit.c:409 gschem/src/x_multiattrib.c:1978
+#: gschem/src/x_attribedit.c:410 gschem/src/x_multiattrib.c:1989
msgid "Visible"
msgstr "Visible"
-#: gschem/src/x_attribedit.c:429
+#: gschem/src/x_attribedit.c:430
msgid "Show Value Only"
msgstr "Mostrar sólo valor"
-#: gschem/src/x_attribedit.c:431
+#: gschem/src/x_attribedit.c:432
msgid "Show Name Only"
msgstr "Mostrar sólo nombre"
-#: gschem/src/x_attribedit.c:433 gschem/src/x_multiattrib.c:1454
+#: gschem/src/x_attribedit.c:434 gschem/src/x_multiattrib.c:1466
msgid "Show Name & Value"
msgstr "Mostrar nombre y valor"
-#: gschem/src/x_attribedit.c:440
+#: gschem/src/x_attribedit.c:441
msgid "<b>Attach Options</b>"
msgstr "<b>Opciones de asociación</b>"
-#: gschem/src/x_attribedit.c:455
+#: gschem/src/x_attribedit.c:456
msgid "All"
msgstr "Todo"
-#: gschem/src/x_attribedit.c:463 gschem/src/x_compselect.c:896
-#: gschem/src/x_compselect.c:1010
+#: gschem/src/x_attribedit.c:464 gschem/src/x_compselect.c:904
+#: gschem/src/x_compselect.c:1018
msgid "Components"
msgstr "Componentes"
-#: gschem/src/x_attribedit.c:471 gschem/src/x_window.c:365
+#: gschem/src/x_attribedit.c:472 gschem/src/x_window.c:365
msgid "Nets"
msgstr "Conexiones"
-#: gschem/src/x_attribedit.c:479
+#: gschem/src/x_attribedit.c:480
msgid "Replace existing attributes"
msgstr "Reemplazar las propiedades existentes"
@@ -1006,91 +1005,91 @@ msgstr ""
"La duplicidad de la propiedad 'slot' puede causar problemas: [nombre del "
"sÃmbolo=%s, número=%d, slot=%d]\n"
-#: gschem/src/x_autonumber.c:673
+#: gschem/src/x_autonumber.c:675
msgid "No searchstring given in autonumber text.\n"
msgstr "No se ha especificado una cadena de búsqueda para autonumerar texto.\n"
-#: gschem/src/x_autonumber.c:725
+#: gschem/src/x_autonumber.c:727
msgid "No '*' or '?' given at the end of the autonumber text.\n"
msgstr "No se ha especificado '*' o '?' al final del texto a autonumerar.\n"
-#: gschem/src/x_autonumber.c:860
+#: gschem/src/x_autonumber.c:862
msgid "Diagonal"
msgstr "Diagonal"
-#: gschem/src/x_autonumber.c:861
+#: gschem/src/x_autonumber.c:863
msgid "Top to bottom"
msgstr "De arriba hacia abajo"
-#: gschem/src/x_autonumber.c:861
+#: gschem/src/x_autonumber.c:863
msgid "Bottom to top"
msgstr "De abajo hacia arriba"
-#: gschem/src/x_autonumber.c:862
+#: gschem/src/x_autonumber.c:864
msgid "Left to right"
msgstr "De izquierda hacia derecha"
-#: gschem/src/x_autonumber.c:862
+#: gschem/src/x_autonumber.c:864
msgid "Right to left"
msgstr "De derecha hacia izquierda"
-#: gschem/src/x_autonumber.c:863
+#: gschem/src/x_autonumber.c:865
msgid "File order"
msgstr "Orden de archivos:"
-#: gschem/src/x_autonumber.c:1199
+#: gschem/src/x_autonumber.c:1201
msgid "Autonumber text"
msgstr "Autoenumerar texto"
-#: gschem/src/x_autonumber.c:1223
+#: gschem/src/x_autonumber.c:1225
msgid "<b>Scope</b>"
msgstr "<b>Ã?mbito</b>"
-#: gschem/src/x_autonumber.c:1245
+#: gschem/src/x_autonumber.c:1247
msgid "Search for:"
msgstr "Buscar:"
-#: gschem/src/x_autonumber.c:1259
+#: gschem/src/x_autonumber.c:1261
msgid "Autonumber text in:"
msgstr "Autoenumerar texto en:"
-#: gschem/src/x_autonumber.c:1266
+#: gschem/src/x_autonumber.c:1268
msgid "Skip numbers found in:"
msgstr "Ignorar números encontrados en:"
-#: gschem/src/x_autonumber.c:1278 gschem/src/x_autonumber.c:1287
+#: gschem/src/x_autonumber.c:1280 gschem/src/x_autonumber.c:1289
msgid "Selected objects"
msgstr "Objetos seleccionados"
-#: gschem/src/x_autonumber.c:1279 gschem/src/x_autonumber.c:1288
+#: gschem/src/x_autonumber.c:1281 gschem/src/x_autonumber.c:1290
msgid "Current page"
msgstr "Hoja actual"
-#: gschem/src/x_autonumber.c:1280 gschem/src/x_autonumber.c:1289
+#: gschem/src/x_autonumber.c:1282 gschem/src/x_autonumber.c:1291
msgid "Whole hierarchy"
msgstr "JerarquÃa completa"
-#: gschem/src/x_autonumber.c:1291
+#: gschem/src/x_autonumber.c:1293
msgid "Overwrite existing numbers"
msgstr "Sobreescribir los números existentes"
-#: gschem/src/x_autonumber.c:1296
+#: gschem/src/x_autonumber.c:1298
msgid "<b>Options</b>"
msgstr "<b>Opciones</b>"
-#: gschem/src/x_autonumber.c:1318
+#: gschem/src/x_autonumber.c:1320
msgid "Starting number:"
msgstr "Número inicial:"
-#: gschem/src/x_autonumber.c:1325
+#: gschem/src/x_autonumber.c:1327
msgid "Sort order:"
msgstr "Método de ordenación:"
-#: gschem/src/x_autonumber.c:1346
+#: gschem/src/x_autonumber.c:1348
msgid "Remove numbers"
msgstr "Borrar los números"
-#: gschem/src/x_autonumber.c:1350
+#: gschem/src/x_autonumber.c:1352
msgid "Automatic slotting"
msgstr "Asignar números de elemento automáticamente"
@@ -1127,48 +1126,48 @@ msgstr "Se ha intentado obtener un color no válido: %d\n"
msgid "Tried to get an invalid outline color: %d\n"
msgstr "Se ha intentado obtener un color para el contorno no válido: %d\n"
-#: gschem/src/x_compselect.c:1040
+#: gschem/src/x_compselect.c:1048
msgid "Filter:"
msgstr "Filtro:"
-#: gschem/src/x_compselect.c:1143 gschem/src/x_dialog.c:3663
-#: gschem/src/x_multiattrib.c:1782
+#: gschem/src/x_compselect.c:1151 gschem/src/x_dialog.c:3667
+#: gschem/src/x_multiattrib.c:1793
msgid "Name"
msgstr "Nombre"
-#: gschem/src/x_compselect.c:1152 gschem/src/x_multiattrib.c:1806
+#: gschem/src/x_compselect.c:1160 gschem/src/x_multiattrib.c:1817
msgid "Value"
msgstr "Valor"
-#: gschem/src/x_compselect.c:1191
+#: gschem/src/x_compselect.c:1199
msgid "Default behavior - reference component"
msgstr "Comportamiento por defecto - designar componente"
-#: gschem/src/x_compselect.c:1194
+#: gschem/src/x_compselect.c:1202
msgid "Embed component in schematic"
msgstr "Incrustar componente en el esquema"
-#: gschem/src/x_compselect.c:1197
+#: gschem/src/x_compselect.c:1205
msgid "Include component as individual objects"
msgstr "Incluir componentes como objetos individuales"
-#: gschem/src/x_compselect.c:1354
+#: gschem/src/x_compselect.c:1362
msgid "Select Component..."
msgstr "Seleccionar componente..."
-#: gschem/src/x_compselect.c:1377
+#: gschem/src/x_compselect.c:1385
msgid "In Use"
msgstr "En uso"
-#: gschem/src/x_compselect.c:1381
+#: gschem/src/x_compselect.c:1389
msgid "Libraries"
msgstr "LibrerÃas"
-#: gschem/src/x_compselect.c:1390 gschem/src/x_fileselect.c:122
+#: gschem/src/x_compselect.c:1398 gschem/src/x_fileselect.c:122
msgid "Preview"
msgstr "Vista preliminar"
-#: gschem/src/x_compselect.c:1418
+#: gschem/src/x_compselect.c:1426
msgid "Attributes"
msgstr "Propiedades"
@@ -1227,139 +1226,139 @@ msgstr "Abajo a la derecha"
msgid "Edit Text Properties"
msgstr "Editar las propiedades del texto"
-#: gschem/src/x_dialog.c:471
+#: gschem/src/x_dialog.c:472
msgid "<b>Text Content</b>"
msgstr "<b>Contenido del texto</b>"
-#: gschem/src/x_dialog.c:507
+#: gschem/src/x_dialog.c:508
msgid "<b>Text Properties</b>"
msgstr "<b>Propiedades del texto</b>"
-#: gschem/src/x_dialog.c:522
+#: gschem/src/x_dialog.c:523
msgid "Color:"
msgstr "Color:"
-#: gschem/src/x_dialog.c:529
+#: gschem/src/x_dialog.c:530
msgid "Size:"
msgstr "Tamaño:"
-#: gschem/src/x_dialog.c:538
+#: gschem/src/x_dialog.c:539
msgid "Alignment:"
msgstr "Alineación:"
-#: gschem/src/x_dialog.c:587
+#: gschem/src/x_dialog.c:588
msgid "Solid"
msgstr "Sólido"
-#: gschem/src/x_dialog.c:588
+#: gschem/src/x_dialog.c:589
msgid "Dotted"
msgstr "Punteado"
-#: gschem/src/x_dialog.c:589
+#: gschem/src/x_dialog.c:590
msgid "Dashed"
msgstr "Guión"
-#: gschem/src/x_dialog.c:590
+#: gschem/src/x_dialog.c:591
msgid "Center"
msgstr "Centrar"
-#: gschem/src/x_dialog.c:591
+#: gschem/src/x_dialog.c:592
msgid "Phantom"
msgstr "Fantasma"
-#: gschem/src/x_dialog.c:592 gschem/src/x_dialog.c:689
-#: gschem/src/x_dialog.c:698 gschem/src/x_dialog.c:707
-#: gschem/src/x_dialog.c:808 gschem/src/x_dialog.c:810
-#: gschem/src/x_dialog.c:812 gschem/src/x_dialog.c:1038
-#: gschem/src/x_dialog.c:1141 gschem/src/x_dialog.c:1150
-#: gschem/src/x_dialog.c:1159 gschem/src/x_dialog.c:1168
-#: gschem/src/x_dialog.c:1177 gschem/src/x_dialog.c:1290
-#: gschem/src/x_dialog.c:1292 gschem/src/x_dialog.c:1294
-#: gschem/src/x_dialog.c:1296 gschem/src/x_dialog.c:1298
+#: gschem/src/x_dialog.c:593 gschem/src/x_dialog.c:690
+#: gschem/src/x_dialog.c:699 gschem/src/x_dialog.c:708
+#: gschem/src/x_dialog.c:809 gschem/src/x_dialog.c:811
+#: gschem/src/x_dialog.c:813 gschem/src/x_dialog.c:1039
+#: gschem/src/x_dialog.c:1142 gschem/src/x_dialog.c:1151
+#: gschem/src/x_dialog.c:1160 gschem/src/x_dialog.c:1169
+#: gschem/src/x_dialog.c:1178 gschem/src/x_dialog.c:1291
+#: gschem/src/x_dialog.c:1293 gschem/src/x_dialog.c:1295
+#: gschem/src/x_dialog.c:1297 gschem/src/x_dialog.c:1299
msgid "*unchanged*"
msgstr "*sin modificar*"
-#: gschem/src/x_dialog.c:916
+#: gschem/src/x_dialog.c:917
msgid "Edit Line Width & Type"
msgstr "Editar ancho y tipo de lÃnea"
-#: gschem/src/x_dialog.c:955 gschem/src/x_print.c:307
+#: gschem/src/x_dialog.c:956 gschem/src/x_print.c:307
msgid "Type:"
msgstr "Tipo:"
-#: gschem/src/x_dialog.c:959
+#: gschem/src/x_dialog.c:960
msgid "Width:"
msgstr "Ancho:"
-#: gschem/src/x_dialog.c:963
+#: gschem/src/x_dialog.c:964
msgid "Dash Length:"
msgstr "Longitud de la lÃnea en la discontinuidad:"
-#: gschem/src/x_dialog.c:967
+#: gschem/src/x_dialog.c:968
msgid "Dash Space:"
msgstr "Espaciado de la discontinuidad:"
-#: gschem/src/x_dialog.c:1034
+#: gschem/src/x_dialog.c:1035
msgid "Hollow"
msgstr "Hueco"
-#: gschem/src/x_dialog.c:1035
+#: gschem/src/x_dialog.c:1036
msgid "Filled"
msgstr "Relleno"
-#: gschem/src/x_dialog.c:1036
+#: gschem/src/x_dialog.c:1037
msgid "Mesh"
msgstr "Malla"
-#: gschem/src/x_dialog.c:1037
+#: gschem/src/x_dialog.c:1038
msgid "Hatch"
msgstr "Trama"
-#: gschem/src/x_dialog.c:1406
+#: gschem/src/x_dialog.c:1407
msgid "Edit Fill Type"
msgstr "Editar tipo de relleno"
-#: gschem/src/x_dialog.c:1444
+#: gschem/src/x_dialog.c:1446
msgid "Fill Type:"
msgstr "Tipo de relleno:"
-#: gschem/src/x_dialog.c:1448
+#: gschem/src/x_dialog.c:1450
msgid "Line Width:"
msgstr "Ancho de lÃnea:"
-#: gschem/src/x_dialog.c:1452
+#: gschem/src/x_dialog.c:1454
msgid "Angle 1:"
msgstr "Ã?ngulo 1:"
-#: gschem/src/x_dialog.c:1456
+#: gschem/src/x_dialog.c:1458
msgid "Pitch 1:"
msgstr "Separación 1:"
-#: gschem/src/x_dialog.c:1460
+#: gschem/src/x_dialog.c:1462
msgid "Angle 2:"
msgstr "Ã?ngulo 2:"
-#: gschem/src/x_dialog.c:1464
+#: gschem/src/x_dialog.c:1466
msgid "Pitch 2:"
msgstr "Separación 2:"
-#: gschem/src/x_dialog.c:1591
+#: gschem/src/x_dialog.c:1593
msgid "Arc Params"
msgstr "Parámetros de arco"
-#: gschem/src/x_dialog.c:1631
+#: gschem/src/x_dialog.c:1634
msgid "Arc Radius:"
msgstr "Radio de arco:"
-#: gschem/src/x_dialog.c:1639
+#: gschem/src/x_dialog.c:1642
msgid "Start Angle:"
msgstr "Ã?ngulo de comienzo:"
-#: gschem/src/x_dialog.c:1647
+#: gschem/src/x_dialog.c:1650
msgid "Degrees of Sweep:"
msgstr "Grados de barrido:"
-#: gschem/src/x_dialog.c:1764
+#: gschem/src/x_dialog.c:1768
msgid ""
"Offset to translate?\n"
"(0 for origin)"
@@ -1367,44 +1366,44 @@ msgstr ""
"¿Desplazamiento del movimiento?\n"
"(0 para el origen)"
-#: gschem/src/x_dialog.c:1832
+#: gschem/src/x_dialog.c:1836
msgid "Text Size"
msgstr "Tamaño de texto"
-#: gschem/src/x_dialog.c:1862
+#: gschem/src/x_dialog.c:1866
msgid "Enter new text size:"
msgstr "Introduzca nuevo tamaño de texto:"
-#: gschem/src/x_dialog.c:1938
+#: gschem/src/x_dialog.c:1942
msgid "Snap Size"
msgstr "Tamaño de la rejilla"
-#: gschem/src/x_dialog.c:1968
+#: gschem/src/x_dialog.c:1972
msgid "Enter new snap grid spacing:"
msgstr "Introduzca el nuevo espaciado de la rejilla:"
-#: gschem/src/x_dialog.c:2045
+#: gschem/src/x_dialog.c:2049
msgid "Edit slot number"
msgstr "Editar número de elemento"
-#: gschem/src/x_dialog.c:2076
+#: gschem/src/x_dialog.c:2080
msgid "Edit slot number:"
msgstr "Editar número de elemento:"
-#: gschem/src/x_dialog.c:2117
+#: gschem/src/x_dialog.c:2121
#, c-format
msgid "%s%s (%s)"
msgstr "%s%s (%s)"
-#: gschem/src/x_dialog.c:2140
+#: gschem/src/x_dialog.c:2144
msgid "About gschem"
msgstr "Acerca de gschem"
-#: gschem/src/x_dialog.c:2141
+#: gschem/src/x_dialog.c:2145
msgid "gEDA: GPL Electronic Design Automation"
msgstr "gEDA: Automatización de Diseño Electrónico GPL"
-#: gschem/src/x_dialog.c:2142
+#: gschem/src/x_dialog.c:2146
msgid ""
"Copyright © 1998-2009 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
"Copyright © 1998-2009 gEDA Contributors (see ChangeLog for details)"
@@ -1413,156 +1412,156 @@ msgstr ""
"Copyright © 1998-2009 gEDA Contributors (véase fichero ChangeLog para más "
"detalles)"
-#: gschem/src/x_dialog.c:2201
+#: gschem/src/x_dialog.c:2205
msgid "Coords"
msgstr "Coordenadas"
-#: gschem/src/x_dialog.c:2222
+#: gschem/src/x_dialog.c:2226
msgid "Screen"
msgstr "Pantalla"
-#: gschem/src/x_dialog.c:2231
+#: gschem/src/x_dialog.c:2235
msgid "World"
msgstr "Mundo"
-#: gschem/src/x_dialog.c:2270
+#: gschem/src/x_dialog.c:2274
msgid "Background"
msgstr "Fondo"
-#: gschem/src/x_dialog.c:2276
+#: gschem/src/x_dialog.c:2280
msgid "Net endpoint"
msgstr "Punto final de conexión"
-#: gschem/src/x_dialog.c:2279
+#: gschem/src/x_dialog.c:2283
msgid "Graphic"
msgstr "Gráfico"
-#: gschem/src/x_dialog.c:2288
+#: gschem/src/x_dialog.c:2292
msgid "Logic bubble"
msgstr "Negación lógica"
-#: gschem/src/x_dialog.c:2291
+#: gschem/src/x_dialog.c:2295
msgid "Grid point"
msgstr "Punto de rejilla"
-#: gschem/src/x_dialog.c:2294
+#: gschem/src/x_dialog.c:2298
msgid "Detached attribute"
msgstr "Desvincular propiedad"
-#: gschem/src/x_dialog.c:2297 gschem/src/x_window.c:383
+#: gschem/src/x_dialog.c:2301 gschem/src/x_window.c:383
msgid "Text"
msgstr "Texto"
-#: gschem/src/x_dialog.c:2303
+#: gschem/src/x_dialog.c:2307
msgid "Selection"
msgstr "Selección"
-#: gschem/src/x_dialog.c:2306
+#: gschem/src/x_dialog.c:2310
msgid "Bounding box"
msgstr "Envolvente"
-#: gschem/src/x_dialog.c:2309
+#: gschem/src/x_dialog.c:2313
msgid "Zoom box"
msgstr "Ventana de ampliado"
-#: gschem/src/x_dialog.c:2318
+#: gschem/src/x_dialog.c:2322
msgid "Output background"
msgstr "Fondo de salida"
-#: gschem/src/x_dialog.c:2321
+#: gschem/src/x_dialog.c:2325
msgid "Net junction"
msgstr "Unión de conexiones"
-#: gschem/src/x_dialog.c:2324
+#: gschem/src/x_dialog.c:2328
msgid "Mesh grid major"
msgstr "Rejilla de malla mayor"
-#: gschem/src/x_dialog.c:2327
+#: gschem/src/x_dialog.c:2331
msgid "Mesh grid minor"
msgstr "Rejilla de malla menor"
-#: gschem/src/x_dialog.c:2330
+#: gschem/src/x_dialog.c:2334
msgid "Unknown"
msgstr "Desconocido"
-#: gschem/src/x_dialog.c:2481
+#: gschem/src/x_dialog.c:2485
#, c-format
msgid "ERROR: NULL object in color_edit_dialog_apply!\n"
msgstr "ERROR: ¡objeto vacÃo (NULL) en la función color_edit_dialog_apply!\n"
-#: gschem/src/x_dialog.c:2525
+#: gschem/src/x_dialog.c:2529
msgid "Color Edit"
msgstr "Editar color"
-#: gschem/src/x_dialog.c:2556
+#: gschem/src/x_dialog.c:2560
msgid "Object color:"
msgstr "Color del componente:"
-#: gschem/src/x_dialog.c:2614
+#: gschem/src/x_dialog.c:2618
msgid "Hotkeys"
msgstr "Teclas rápidas"
-#: gschem/src/x_dialog.c:2678
+#: gschem/src/x_dialog.c:2682
msgid "Function"
msgstr "Función"
-#: gschem/src/x_dialog.c:2685
+#: gschem/src/x_dialog.c:2689
msgid "Keystroke(s)"
msgstr "Pulsación(es)"
-#: gschem/src/x_dialog.c:2991
+#: gschem/src/x_dialog.c:2995
msgid "Find Text"
msgstr "Encontrar texto:"
-#: gschem/src/x_dialog.c:3022
+#: gschem/src/x_dialog.c:3026
msgid "Text to find:"
msgstr "Texto a encontrar:"
-#: gschem/src/x_dialog.c:3032
+#: gschem/src/x_dialog.c:3036
msgid "descend into hierarchy"
msgstr "Descender en la jerarquÃa"
-#: gschem/src/x_dialog.c:3097
+#: gschem/src/x_dialog.c:3101
msgid "Hide Text"
msgstr "Ocultar texto:"
-#: gschem/src/x_dialog.c:3128
+#: gschem/src/x_dialog.c:3132
msgid "Hide text starting with:"
msgstr "Ocultar texto que comienza por:"
-#: gschem/src/x_dialog.c:3197
+#: gschem/src/x_dialog.c:3201
msgid "Show Text"
msgstr "Mostrar texto"
-#: gschem/src/x_dialog.c:3228
+#: gschem/src/x_dialog.c:3232
msgid "Show text starting with:"
msgstr "Mostrar texto que comienza por:"
-#: gschem/src/x_dialog.c:3685
+#: gschem/src/x_dialog.c:3689
msgid "S_elect the schematics you want to save:"
msgstr "S_eleccione los esquemas que quiere guardar:"
-#: gschem/src/x_dialog.c:3779
+#: gschem/src/x_dialog.c:3784
#, c-format
msgid "Save the changes to schematic \"%s\" before closing?"
msgstr "¿Guardar cambios del esquema \"%s\" antes de salir?"
-#: gschem/src/x_dialog.c:3785
+#: gschem/src/x_dialog.c:3790
#, c-format
msgid ""
"There are %d schematics with unsaved changes. Save changes before closing?"
msgstr ""
"Hay %d esquemas con cambios sin guardar. ¿Guardar cambios antes de cerrar?"
-#: gschem/src/x_dialog.c:3814
+#: gschem/src/x_dialog.c:3819
msgid "If you don't save, all your changes will be permanently lost."
msgstr "Si no los guarda, todos los cambios se perderán definitivamente."
-#: gschem/src/x_dialog.c:3834
+#: gschem/src/x_dialog.c:3839
msgid "_Close without saving"
msgstr "_Cerrar sin guardar"
-#: gschem/src/x_dialog.c:4170
+#: gschem/src/x_dialog.c:4175
#, c-format
msgid ""
"<span weight=\"bold\" size=\"larger\">The input attribute \"%s\" is invalid\n"
@@ -1580,19 +1579,19 @@ msgstr ""
"El nombre no puede finalizar en un espacio.\n"
"El valor no puede empezar con un espacio."
-#: gschem/src/x_dialog.c:4172
+#: gschem/src/x_dialog.c:4177
msgid "Invalid Attribute"
msgstr "Propiedad incorrecta"
-#: gschem/src/x_dialog.c:4208
+#: gschem/src/x_dialog.c:4213
msgid "Pin type"
msgstr "Tipo de Pin"
-#: gschem/src/x_dialog.c:4232
+#: gschem/src/x_dialog.c:4237
msgid "Net pin"
msgstr "Pin para conexión simple"
-#: gschem/src/x_dialog.c:4234
+#: gschem/src/x_dialog.c:4239
msgid "Bus pin (graphical)"
msgstr "Pin para conexión a bus (gráfico)"
@@ -1692,13 +1691,13 @@ msgstr "Tipo de imagen"
msgid "Write image..."
msgstr "Guardar imagen..."
-#: gschem/src/x_log.c:188
+#: gschem/src/x_log.c:209
msgid "** Invalid UTF-8 in log message. See stderr or gschem.log.\n"
msgstr ""
"** mensaje sin codificación UTF-8 en la ventana de registro. Véase la "
"ventana de registro de gschem o la salida de errores.\n"
-#: gschem/src/x_log.c:256
+#: gschem/src/x_log.c:288
msgid "Status"
msgstr "Estado"
@@ -1774,74 +1773,65 @@ msgstr "/Descender en sÃmbolo"
msgid "/Up"
msgstr "/Arriba"
-#: gschem/src/x_menus.c:321
+#: gschem/src/x_menus.c:323
#, c-format
msgid "Tried to set the sensitivity on non-existent menu item '%s'\n"
msgstr ""
"Se ha intentado modificar la sensibilidad de una opción de menú que no "
"existe '%s'\n"
-#: gschem/src/x_menus.c:345
+#: gschem/src/x_menus.c:347
msgid "Popup_menu_item_factory doesn't exist!\n"
msgstr "¡No existen menúes contextuales!\n"
-#: gschem/src/x_menus.c:358
+#: gschem/src/x_menus.c:360
msgid "Tried to set the sensitivity on a non-existent popup menu_item\n"
msgstr ""
"Se ha intentado modificar la sensibilidad de una opción de menú que no "
"existe\n"
-#: gschem/src/x_menus.c:438
-#, c-format
-msgid "Couldn't open file %s\n"
-msgstr "No se ha podido abrir el archivo %s\n"
-
-#: gschem/src/x_menus.c:495
-msgid "Clear"
-msgstr "Borrar"
-
-#: gschem/src/x_multiattrib.c:911
+#: gschem/src/x_multiattrib.c:915
msgid "Attributes with empty name are not allowed. Please set a name."
msgstr ""
"No se permiten las propiedades sin nombre. Por favor, introduzca un nombre."
-#: gschem/src/x_multiattrib.c:1456
+#: gschem/src/x_multiattrib.c:1468
msgid "Show Value only"
msgstr "Mostrar sólo valor"
-#: gschem/src/x_multiattrib.c:1458
+#: gschem/src/x_multiattrib.c:1470
msgid "Show Name only"
msgstr "Mostrar sólo nombre"
-#: gschem/src/x_multiattrib.c:1486
+#: gschem/src/x_multiattrib.c:1498
msgid "Promote"
msgstr "Promocionar"
-#: gschem/src/x_multiattrib.c:1490
+#: gschem/src/x_multiattrib.c:1502
msgid "Duplicate"
msgstr "Duplicar"
-#: gschem/src/x_multiattrib.c:1708
+#: gschem/src/x_multiattrib.c:1719
msgid "Edit Attributes"
msgstr "Editar propiedades"
-#: gschem/src/x_multiattrib.c:1826
+#: gschem/src/x_multiattrib.c:1837
msgid "Vis?"
msgstr "Visible?"
-#: gschem/src/x_multiattrib.c:1844
+#: gschem/src/x_multiattrib.c:1855
msgid "N"
msgstr "N"
-#: gschem/src/x_multiattrib.c:1862
+#: gschem/src/x_multiattrib.c:1873
msgid "V"
msgstr "V"
-#: gschem/src/x_multiattrib.c:1884
+#: gschem/src/x_multiattrib.c:1895
msgid "Show inherited attributes"
msgstr "Mostrar propiedades heredadas"
-#: gschem/src/x_multiattrib.c:1900
+#: gschem/src/x_multiattrib.c:1911
msgid "Add Attribute"
msgstr "Añadir propiedad"
@@ -1865,23 +1855,23 @@ msgstr "Cerrar página"
msgid "Discard Page"
msgstr "Descartar página"
-#: gschem/src/x_pagesel.c:376
+#: gschem/src/x_pagesel.c:375
msgid "Page Manager"
msgstr "Administrador de páginas"
-#: gschem/src/x_pagesel.c:432
+#: gschem/src/x_pagesel.c:431
msgid "Filename"
msgstr "Nombre de archivo"
-#: gschem/src/x_pagesel.c:448
+#: gschem/src/x_pagesel.c:447
msgid "Changed"
msgstr "Modificado"
-#: gschem/src/x_pagesel.c:468
+#: gschem/src/x_pagesel.c:467
msgid "Right click on the filename for more options..."
msgstr "Pulse con el botón derecho para ver más opciones..."
-#: gschem/src/x_preview.c:234
+#: gschem/src/x_preview.c:233
msgid "Preview Buffer"
msgstr "Previsualizar memoria intermedia"
@@ -1937,16 +1927,16 @@ msgstr "Archivo:"
msgid "Command:"
msgstr "Comando:"
-#: gschem/src/x_print.c:741
+#: gschem/src/x_print.c:745
msgid "No print destination specified\n"
msgstr "No se ha especificado el destino de impresión\n"
-#: gschem/src/x_print.c:748
+#: gschem/src/x_print.c:752
#, c-format
msgid "Cannot print current schematic to [%s]\n"
msgstr "No se puede imprimir el esquema actual a [%s]\n"
-#: gschem/src/x_print.c:757
+#: gschem/src/x_print.c:761
#, c-format
msgid ""
"Error printing to file '%s'\n"
@@ -1955,7 +1945,7 @@ msgstr ""
"Error al imprimir al fichero '%s'\n"
"Vea la ventana de registro para más información"
-#: gschem/src/x_print.c:764
+#: gschem/src/x_print.c:768
#, c-format
msgid "Printed current schematic to [%s]\n"
msgstr "Se ha imprimido el esquema actual a [%s]\n"
@@ -1964,6 +1954,11 @@ msgstr "Se ha imprimido el esquema actual a [%s]\n"
msgid "Execute Script..."
msgstr "Ejecutar subprograma..."
+#: gschem/src/x_script.c:66
+#, c-format
+msgid "Executing guile script [%s]\n"
+msgstr "Ejecutando programa de guile [%s]\n"
+
#: gschem/src/x_window.c:81
#, c-format
msgid "Couldn't allocate gc\n"
@@ -2079,35 +2074,35 @@ msgstr "Fallo al cargar el archivo"
msgid "New file [%s]\n"
msgstr "Nuevo archivo [%s]\n"
-#: gschem/src/x_window.c:857
+#: gschem/src/x_window.c:855
#, c-format
msgid "Could NOT save page [%s]\n"
msgstr "NO se ha podido guardar la página [%s]\n"
-#: gschem/src/x_window.c:858
+#: gschem/src/x_window.c:856
msgid "Error while trying to save"
msgstr "Error al intentar guardar"
-#: gschem/src/x_window.c:867
+#: gschem/src/x_window.c:865
#, c-format
msgid "Saved as [%s]\n"
msgstr "Guardado como [%s]\n"
-#: gschem/src/x_window.c:869
+#: gschem/src/x_window.c:867
#, c-format
msgid "Saved [%s]\n"
msgstr "Guardado [%s]\n"
-#: gschem/src/x_window.c:871
+#: gschem/src/x_window.c:869
msgid "Saved"
msgstr "Guardado"
-#: gschem/src/x_window.c:945
+#: gschem/src/x_window.c:943
#, c-format
msgid "Discarding page [%s]\n"
msgstr "Descartando página [%s]\n"
-#: gschem/src/x_window.c:945
+#: gschem/src/x_window.c:943
#, c-format
msgid "Closing [%s]\n"
msgstr "Cerrando [%s]\n"
@@ -2148,7 +2143,7 @@ msgstr "Guardar _como..."
msgid "Save All"
msgstr "Guardar todo"
-#: gschem/lib/system-gschemrc.scm:1386 gschem/lib/system-gschemrc.scm:1477
+#: gschem/lib/system-gschemrc.scm:1386 gschem/lib/system-gschemrc.scm:1478
msgid "_Revert"
msgstr "_Recargar"
@@ -2160,7 +2155,7 @@ msgstr "Im_primir..."
msgid "Write _image..."
msgstr "Guardar _imagen..."
-#: gschem/lib/system-gschemrc.scm:1393 gschem/lib/system-gschemrc.scm:1478
+#: gschem/lib/system-gschemrc.scm:1393 gschem/lib/system-gschemrc.scm:1479
msgid "_Close"
msgstr "C_errar"
@@ -2192,391 +2187,434 @@ msgstr "_Pegar"
msgid "_Delete"
msgstr "_Borrar"
-#: gschem/lib/system-gschemrc.scm:1412
+#: gschem/lib/system-gschemrc.scm:1409
+#, fuzzy
+msgid "Select All"
+msgstr "Seleccionar"
+
+#: gschem/lib/system-gschemrc.scm:1410
+#, fuzzy
+msgid "Deselect"
+msgstr "Seleccionar"
+
+#: gschem/lib/system-gschemrc.scm:1414
msgid "Rotate 90 Mode"
msgstr "Rotar 90º"
-#: gschem/lib/system-gschemrc.scm:1415
+#: gschem/lib/system-gschemrc.scm:1417
msgid "Edit..."
msgstr "Editar..."
-#: gschem/lib/system-gschemrc.scm:1416
+#: gschem/lib/system-gschemrc.scm:1418
msgid "Edit Text..."
msgstr "Editar texto..."
-#: gschem/lib/system-gschemrc.scm:1417
+#: gschem/lib/system-gschemrc.scm:1419
msgid "Slot..."
msgstr "Elemento..."
-#: gschem/lib/system-gschemrc.scm:1418
+#: gschem/lib/system-gschemrc.scm:1420
msgid "Color..."
msgstr "Color..."
-#: gschem/lib/system-gschemrc.scm:1419
+#: gschem/lib/system-gschemrc.scm:1421
msgid "Line Width & Type..."
msgstr "Anchura y tipo de lÃnea"
-#: gschem/lib/system-gschemrc.scm:1420
+#: gschem/lib/system-gschemrc.scm:1422
msgid "Fill Type..."
msgstr "Tipo de relleno"
-#: gschem/lib/system-gschemrc.scm:1421
+#: gschem/lib/system-gschemrc.scm:1423
msgid "Symbol Translate..."
msgstr "Mover sÃmbolo..."
-#: gschem/lib/system-gschemrc.scm:1425
+#: gschem/lib/system-gschemrc.scm:1427
msgid "Invoke Macro"
msgstr "Ejecutar macro"
-#: gschem/lib/system-gschemrc.scm:1426
+#: gschem/lib/system-gschemrc.scm:1428
msgid "Embed Component/Picture"
msgstr "Incrustar componente/imagen"
-#: gschem/lib/system-gschemrc.scm:1427
+#: gschem/lib/system-gschemrc.scm:1429
msgid "Unembed Component/Picture"
msgstr "Desincrustar componente/imagen"
-#: gschem/lib/system-gschemrc.scm:1428
+#: gschem/lib/system-gschemrc.scm:1430
msgid "Update Component"
msgstr "Actualizar componente"
-#: gschem/lib/system-gschemrc.scm:1429
+#: gschem/lib/system-gschemrc.scm:1431
msgid "Show/Hide Inv Text"
msgstr "Mostrar/Ocultar texto oculto"
-#: gschem/lib/system-gschemrc.scm:1430
-msgid "Make Inv Text Vis"
-msgstr "Hacer visible el texto oculto"
-
-#: gschem/lib/system-gschemrc.scm:1436
+#: gschem/lib/system-gschemrc.scm:1437
msgid "Copy into 1"
msgstr "Copiar en memoria intermedia 1"
-#: gschem/lib/system-gschemrc.scm:1437
+#: gschem/lib/system-gschemrc.scm:1438
msgid "Copy into 2"
msgstr "Copiar en memoria intermedia 2"
-#: gschem/lib/system-gschemrc.scm:1438
+#: gschem/lib/system-gschemrc.scm:1439
msgid "Copy into 3"
msgstr "Copiar en memoria intermedia 3"
-#: gschem/lib/system-gschemrc.scm:1439
+#: gschem/lib/system-gschemrc.scm:1440
msgid "Copy into 4"
msgstr "Copiar en memoria intermedia 4"
-#: gschem/lib/system-gschemrc.scm:1440
+#: gschem/lib/system-gschemrc.scm:1441
msgid "Copy into 5"
msgstr "Copiar en memoria intermedia 5"
-#: gschem/lib/system-gschemrc.scm:1441
+#: gschem/lib/system-gschemrc.scm:1442
msgid "Cut into 1"
msgstr "Cortar en memoria intermedia 1"
-#: gschem/lib/system-gschemrc.scm:1442
+#: gschem/lib/system-gschemrc.scm:1443
msgid "Cut into 2"
msgstr "Cortar en memoria intermedia 2"
-#: gschem/lib/system-gschemrc.scm:1443
+#: gschem/lib/system-gschemrc.scm:1444
msgid "Cut into 3"
msgstr "Cortar en memoria intermedia 3"
-#: gschem/lib/system-gschemrc.scm:1444
+#: gschem/lib/system-gschemrc.scm:1445
msgid "Cut into 4"
msgstr "Cortar en memoria intermedia 4"
-#: gschem/lib/system-gschemrc.scm:1445
+#: gschem/lib/system-gschemrc.scm:1446
msgid "Cut into 5"
msgstr "Cortar en memoria intermedia 5"
-#: gschem/lib/system-gschemrc.scm:1446
+#: gschem/lib/system-gschemrc.scm:1447
msgid "Paste from 1"
msgstr "Pegar memoria intermedia 1"
-#: gschem/lib/system-gschemrc.scm:1447
+#: gschem/lib/system-gschemrc.scm:1448
msgid "Paste from 2"
msgstr "Pegar memoria intermedia 2"
-#: gschem/lib/system-gschemrc.scm:1448
+#: gschem/lib/system-gschemrc.scm:1449
msgid "Paste from 3"
msgstr "Pegar memoria intermedia 3"
-#: gschem/lib/system-gschemrc.scm:1449
+#: gschem/lib/system-gschemrc.scm:1450
msgid "Paste from 4"
msgstr "Pegar memoria intermedia 4"
-#: gschem/lib/system-gschemrc.scm:1450
+#: gschem/lib/system-gschemrc.scm:1451
msgid "Paste from 5"
msgstr "Pegar memoria intermedia 5"
-#: gschem/lib/system-gschemrc.scm:1456
+#: gschem/lib/system-gschemrc.scm:1457
msgid "_Redraw"
msgstr "_Redibujar"
-#: gschem/lib/system-gschemrc.scm:1457
+#: gschem/lib/system-gschemrc.scm:1458
msgid "_Pan"
msgstr "Centrar res_pecto al cursor"
-#: gschem/lib/system-gschemrc.scm:1458
+#: gschem/lib/system-gschemrc.scm:1459
msgid "Zoom _Box"
msgstr "Ampliar z_ona"
-#: gschem/lib/system-gschemrc.scm:1459
+#: gschem/lib/system-gschemrc.scm:1460
msgid "Zoom _Extents"
msgstr "Mostrar _todo"
-#: gschem/lib/system-gschemrc.scm:1460
+#: gschem/lib/system-gschemrc.scm:1461
msgid "Zoom _In"
msgstr "_Aumentar ampliación"
-#: gschem/lib/system-gschemrc.scm:1461
+#: gschem/lib/system-gschemrc.scm:1462
msgid "Zoom _Out"
msgstr "_Disminuir ampliación"
-#: gschem/lib/system-gschemrc.scm:1462
+#: gschem/lib/system-gschemrc.scm:1463
msgid "Zoom _Full"
msgstr "Vista co_mpleta"
-#: gschem/lib/system-gschemrc.scm:1464
+#: gschem/lib/system-gschemrc.scm:1465
msgid "_Dark color scheme"
msgstr "Configuración de colores os_curos"
-#: gschem/lib/system-gschemrc.scm:1465
+#: gschem/lib/system-gschemrc.scm:1466
msgid "_Light color scheme"
msgstr "Configuración de co_lores claros"
-#: gschem/lib/system-gschemrc.scm:1466
+#: gschem/lib/system-gschemrc.scm:1467
#, fuzzy
msgid "B_W color scheme"
msgstr "Configuración de colores os_curos"
-#: gschem/lib/system-gschemrc.scm:1473
+#: gschem/lib/system-gschemrc.scm:1474
msgid "_Manager..."
msgstr "Ad_ministrador..."
-#: gschem/lib/system-gschemrc.scm:1474
+#: gschem/lib/system-gschemrc.scm:1475
msgid "_Previous"
msgstr "_Anterior"
-#: gschem/lib/system-gschemrc.scm:1475
+#: gschem/lib/system-gschemrc.scm:1476
msgid "_Next"
msgstr "_Siguiente"
-#: gschem/lib/system-gschemrc.scm:1476
+#: gschem/lib/system-gschemrc.scm:1477
msgid "Ne_w"
msgstr "_Nuevo"
-#: gschem/lib/system-gschemrc.scm:1480
+#: gschem/lib/system-gschemrc.scm:1481
msgid "_Discard"
msgstr "_Descartar"
-#: gschem/lib/system-gschemrc.scm:1486
+#: gschem/lib/system-gschemrc.scm:1487
msgid "_Component..."
msgstr "_Componente..."
-#: gschem/lib/system-gschemrc.scm:1487
+#: gschem/lib/system-gschemrc.scm:1488
msgid "_Net"
msgstr "Co_nexión"
-#: gschem/lib/system-gschemrc.scm:1488
+#: gschem/lib/system-gschemrc.scm:1489
msgid "B_us"
msgstr "B_us"
-#: gschem/lib/system-gschemrc.scm:1489
+#: gschem/lib/system-gschemrc.scm:1490
msgid "_Attribute..."
msgstr "Propied_ad..."
-#: gschem/lib/system-gschemrc.scm:1490
+#: gschem/lib/system-gschemrc.scm:1491
msgid "_Text..."
msgstr "_Texto..."
-#: gschem/lib/system-gschemrc.scm:1492
+#: gschem/lib/system-gschemrc.scm:1493
msgid "_Line"
msgstr "_LÃnea"
-#: gschem/lib/system-gschemrc.scm:1493
+#: gschem/lib/system-gschemrc.scm:1494
msgid "_Box"
msgstr "Rectán_gulo"
-#: gschem/lib/system-gschemrc.scm:1494
+#: gschem/lib/system-gschemrc.scm:1495
msgid "C_ircle"
msgstr "CÃrcul_o"
-#: gschem/lib/system-gschemrc.scm:1495
+#: gschem/lib/system-gschemrc.scm:1496
msgid "A_rc"
msgstr "A_rco"
-#: gschem/lib/system-gschemrc.scm:1496
+#: gschem/lib/system-gschemrc.scm:1497
msgid "_Pin"
msgstr "_Pin"
-#: gschem/lib/system-gschemrc.scm:1497
+#: gschem/lib/system-gschemrc.scm:1498
msgid "Pictu_re..."
msgstr "I_magen..."
-#: gschem/lib/system-gschemrc.scm:1503
+#: gschem/lib/system-gschemrc.scm:1504
msgid "_Down Schematic"
msgstr "_Descender en esquema"
-#: gschem/lib/system-gschemrc.scm:1504
+#: gschem/lib/system-gschemrc.scm:1505
msgid "Down _Symbol"
msgstr "Descender en _sÃmbolo"
-#: gschem/lib/system-gschemrc.scm:1505
+#: gschem/lib/system-gschemrc.scm:1506
msgid "_Up"
msgstr "A_rriba"
-#: gschem/lib/system-gschemrc.scm:1506
+#: gschem/lib/system-gschemrc.scm:1507
msgid "D_ocumentation..."
msgstr "D_ocumentación"
-#: gschem/lib/system-gschemrc.scm:1512
+#: gschem/lib/system-gschemrc.scm:1513
msgid "_Attach"
msgstr "_Adjuntar"
-#: gschem/lib/system-gschemrc.scm:1513
+#: gschem/lib/system-gschemrc.scm:1514
msgid "_Detach"
msgstr "No a_djuntar"
-#: gschem/lib/system-gschemrc.scm:1514
+#: gschem/lib/system-gschemrc.scm:1515
msgid "Show _Value"
msgstr "Mostrar _valor"
-#: gschem/lib/system-gschemrc.scm:1515
+#: gschem/lib/system-gschemrc.scm:1516
msgid "Show _Name"
msgstr "Mostrar _nombre"
-#: gschem/lib/system-gschemrc.scm:1516
+#: gschem/lib/system-gschemrc.scm:1517
msgid "Show _Both"
msgstr "Mostrar am_bos"
-#: gschem/lib/system-gschemrc.scm:1517
+#: gschem/lib/system-gschemrc.scm:1518
msgid "_Toggle Visibility"
msgstr "Cambiar v_isibilidad"
-#: gschem/lib/system-gschemrc.scm:1519
+#: gschem/lib/system-gschemrc.scm:1520
msgid "_Find Specific Text..."
msgstr "_Encontrar texto especÃfico..."
-#: gschem/lib/system-gschemrc.scm:1520
+#: gschem/lib/system-gschemrc.scm:1521
msgid "_Hide Specific Text..."
msgstr "_Ocultar texto especÃfico..."
-#: gschem/lib/system-gschemrc.scm:1521
+#: gschem/lib/system-gschemrc.scm:1522
msgid "_Show Specific Text..."
msgstr "Mo_strar texto especÃfico..."
-#: gschem/lib/system-gschemrc.scm:1522
+#: gschem/lib/system-gschemrc.scm:1523
msgid "A_utonumber Text..."
msgstr "A_utonumerar texto..."
-#: gschem/lib/system-gschemrc.scm:1528
+#: gschem/lib/system-gschemrc.scm:1529
msgid "_Text Size..."
msgstr "_Tamaño de texto..."
-#: gschem/lib/system-gschemrc.scm:1529
+#: gschem/lib/system-gschemrc.scm:1530
msgid "Cycle _grid styles"
msgstr "Cambiar estilos de re_jilla"
-#: gschem/lib/system-gschemrc.scm:1530
+#: gschem/lib/system-gschemrc.scm:1531
msgid "Toggle _Snap On/Off"
msgstr "Act/Desact aju_ste a la rejilla"
-#: gschem/lib/system-gschemrc.scm:1531
+#: gschem/lib/system-gschemrc.scm:1532
msgid "Snap Grid S_pacing..."
msgstr "Es_paciado de la rejilla..."
-#: gschem/lib/system-gschemrc.scm:1532
+#: gschem/lib/system-gschemrc.scm:1533
msgid "Scale _up Grid Spacing"
msgstr "A_umentar espaciado de la rejilla..."
-#: gschem/lib/system-gschemrc.scm:1534
+#: gschem/lib/system-gschemrc.scm:1535
msgid "Scale _down Grid Spacing"
msgstr "_Disminuir espaciado de la rejilla..."
-#: gschem/lib/system-gschemrc.scm:1536
+#: gschem/lib/system-gschemrc.scm:1537
msgid "Toggle _Outline/Box"
msgstr "Cambiar Silueta/Rectángul_o"
-#: gschem/lib/system-gschemrc.scm:1538
+#: gschem/lib/system-gschemrc.scm:1539
msgid "Toggle Net _Rubberband"
msgstr "Act/Desact conserva_r conexiones"
-#: gschem/lib/system-gschemrc.scm:1539
+#: gschem/lib/system-gschemrc.scm:1540
msgid "Toggle _Magnetic Net"
msgstr "Modo ayuda _magnética a la conexión"
-#: gschem/lib/system-gschemrc.scm:1540
+#: gschem/lib/system-gschemrc.scm:1541
msgid "Show _Log Window..."
msgstr "Mostrar ventana de re_gistro..."
-#: gschem/lib/system-gschemrc.scm:1542
+#: gschem/lib/system-gschemrc.scm:1543
msgid "Show _Coord Window..."
msgstr "Mostrar ventana de _coordenadas..."
-#: gschem/lib/system-gschemrc.scm:1558
+#: gschem/lib/system-gschemrc.scm:1559
msgid "gEDA Docu_mentation..."
msgstr "Docu_mentación de gEDA"
-#: gschem/lib/system-gschemrc.scm:1559
+#: gschem/lib/system-gschemrc.scm:1560
msgid "gschem _FAQ..."
msgstr "PU_F de gschem"
-#: gschem/lib/system-gschemrc.scm:1560
+#: gschem/lib/system-gschemrc.scm:1561
msgid "gEDA _Wiki..."
msgstr "_Wiki de gEDA..."
-#: gschem/lib/system-gschemrc.scm:1561
+#: gschem/lib/system-gschemrc.scm:1562
msgid "Component D_ocumentation..."
msgstr "D_ocumentación del componente..."
-#: gschem/lib/system-gschemrc.scm:1563
+#: gschem/lib/system-gschemrc.scm:1564
msgid "_Hotkeys..."
msgstr "_Teclas rápidas"
-#: gschem/lib/system-gschemrc.scm:1564
+#: gschem/lib/system-gschemrc.scm:1565
msgid "_About..."
msgstr "_Acerca de..."
-#: gschem/lib/system-gschemrc.scm:1570
+#: gschem/lib/system-gschemrc.scm:1571
msgid "_File"
msgstr "_Archivo"
-#: gschem/lib/system-gschemrc.scm:1571
+#: gschem/lib/system-gschemrc.scm:1572
msgid "_Edit"
msgstr "_Editar"
-#: gschem/lib/system-gschemrc.scm:1572
+#: gschem/lib/system-gschemrc.scm:1573
msgid "_Buffer"
msgstr "Me_moria intermedia"
-#: gschem/lib/system-gschemrc.scm:1573
+#: gschem/lib/system-gschemrc.scm:1574
msgid "_View"
msgstr "_Ver"
-#: gschem/lib/system-gschemrc.scm:1574
+#: gschem/lib/system-gschemrc.scm:1575
msgid "_Page"
msgstr "_Página"
-#: gschem/lib/system-gschemrc.scm:1575
+#: gschem/lib/system-gschemrc.scm:1576
msgid "_Add"
msgstr "Aña_dir"
-#: gschem/lib/system-gschemrc.scm:1576
+#: gschem/lib/system-gschemrc.scm:1577
msgid "Hie_rarchy"
msgstr "Je_rarquÃa"
-#: gschem/lib/system-gschemrc.scm:1577
+#: gschem/lib/system-gschemrc.scm:1578
msgid "A_ttributes"
msgstr "Prop_iedades"
-#: gschem/lib/system-gschemrc.scm:1578
+#: gschem/lib/system-gschemrc.scm:1579
msgid "_Options"
msgstr "_Opciones"
-#: gschem/lib/system-gschemrc.scm:1579
+#: gschem/lib/system-gschemrc.scm:1580
msgid "_Help"
msgstr "Ay_uda"
+#~ msgid "Scheme directory NOT set!\n"
+#~ msgstr "¡Directorio de Scheme no especificado!\n"
+
+#~ msgid "MakeVisible"
+#~ msgstr "Hacer visible"
+
+#~ msgid ""
+#~ "Usage: %s [OPTIONS] schematic_filename1 ... schematic_filenameN\n"
+#~ " -q Quiet mode\n"
+#~ " -v Verbose mode on\n"
+#~ " -r filename Rc filename\n"
+#~ " -s filename Script (guile) filename\n"
+#~ " -o filename Output filename (for printing)\n"
+#~ " -p Automatically place the window\n"
+#~ " -t Print stroke information\n"
+#~ " -h Help; this message\n"
+#~ "\n"
+#~ msgstr ""
+#~ "Modo de uso: %s [OPCIONES] nombre_de_esquema_1·...·nombre_de_esquema_N\n"
+#~ " -q No mostrar mensajes adicionales\n"
+#~ " -v Mostrar mensajes adicionales\n"
+#~ " -r archivo Usar archivo Rc\n"
+#~ " -s archivo Ejecutar fichero (guile)\n"
+#~ " -o archivo Fichero de salida (para impresión)\n"
+#~ " -p Posicionar automáticamente la ventana\n"
+#~ " -h Ayuda; éste mensaje\n"
+#~ "\n"
+
+#~ msgid "Couldn't open file %s\n"
+#~ msgstr "No se ha podido abrir el archivo %s\n"
+
+#~ msgid "Clear"
+#~ msgstr "Borrar"
+
+#~ msgid "Make Inv Text Vis"
+#~ msgstr "Hacer visible el texto oculto"
+
#~ msgid "Update Cues"
#~ msgstr "Actualizar entradas"
diff --git a/gschem/po/fa.po b/gschem/po/fa.po
index 3918f72..0fe1f19 100644
--- a/gschem/po/fa.po
+++ b/gschem/po/fa.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2010-11-07 13:37+0000\n"
+"POT-Creation-Date: 2011-01-16 00:11-0500\n"
"PO-Revision-Date: 2010-01-31 15:45+0000\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -22,17 +22,17 @@ msgstr ""
msgid "Zoom too small! Cannot zoom further.\n"
msgstr ""
-#: gschem/src/g_funcs.c:339 gschem/src/i_callbacks.c:68
+#: gschem/src/g_funcs.c:347 gschem/src/i_callbacks.c:68
#, c-format
msgid "Could not fork\n"
msgstr ""
-#: gschem/src/g_funcs.c:355 gschem/src/i_callbacks.c:78
+#: gschem/src/g_funcs.c:363 gschem/src/i_callbacks.c:78
#, c-format
msgid "Could not invoke %s\n"
msgstr ""
-#: gschem/src/g_funcs.c:361 gschem/src/i_callbacks.c:82
+#: gschem/src/g_funcs.c:369 gschem/src/i_callbacks.c:82
msgid "Documentation commands not supported under MinGW.\n"
msgstr ""
@@ -121,39 +121,39 @@ msgstr ""
msgid "Invalid number of steps [%d] scrollpan-steps\n"
msgstr ""
-#: gschem/src/gschem.c:184
+#: gschem/src/gschem.c:188
#, c-format
msgid "gEDA/gschem version %s%s.%s\n"
msgstr ""
-#: gschem/src/gschem.c:187
+#: gschem/src/gschem.c:191
msgid ""
"gEDA/gschem comes with ABSOLUTELY NO WARRANTY; see COPYING for more "
"details.\n"
msgstr ""
-#: gschem/src/gschem.c:189
+#: gschem/src/gschem.c:193
msgid ""
"This is free software, and you are welcome to redistribute it under certain\n"
msgstr ""
-#: gschem/src/gschem.c:191
+#: gschem/src/gschem.c:195
msgid ""
"conditions; please see the COPYING file for more details.\n"
"\n"
msgstr ""
-#: gschem/src/gschem.c:194
+#: gschem/src/gschem.c:198
#, c-format
msgid "This is the MINGW32 port.\n"
msgstr ""
-#: gschem/src/gschem.c:198
+#: gschem/src/gschem.c:202
#, c-format
msgid "Current locale settings: %s\n"
msgstr ""
-#: gschem/src/gschem.c:213
+#: gschem/src/gschem.c:218
msgid ""
"You must set the GEDADATA environment variable!\n"
"\n"
@@ -161,31 +161,21 @@ msgid ""
"environment variable to point to the correct location.\n"
msgstr ""
-#: gschem/src/gschem.c:248
+#: gschem/src/gschem.c:256
#, c-format
msgid "Couldn't find init scm file [%s]\n"
msgstr ""
-#: gschem/src/gschem.c:252
+#: gschem/src/gschem.c:260
#, c-format
msgid "Read init scm file [%s]\n"
msgstr ""
-#: gschem/src/gschem.c:256
+#: gschem/src/gschem.c:264
#, c-format
msgid "Failed to read init scm file [%s]\n"
msgstr ""
-#: gschem/src/gschem.c:317
-#, c-format
-msgid "Scheme directory NOT set!\n"
-msgstr ""
-
-#: gschem/src/gschem.c:324 gschem/src/x_script.c:66
-#, c-format
-msgid "Executing guile script [%s]\n"
-msgstr ""
-
#: gschem/src/gschem_cairo.c:310
#, c-format
msgid "Unknown end for line (%d)\n"
@@ -209,11 +199,11 @@ msgstr ""
msgid "Text Mode"
msgstr ""
-#: gschem/src/i_basic.c:84 gschem/lib/system-gschemrc.scm:1409
+#: gschem/src/i_basic.c:84 gschem/lib/system-gschemrc.scm:1411
msgid "Copy Mode"
msgstr "Copy Mode"
-#: gschem/src/i_basic.c:87 gschem/lib/system-gschemrc.scm:1411
+#: gschem/src/i_basic.c:87 gschem/lib/system-gschemrc.scm:1413
msgid "Move Mode"
msgstr "Move Mode"
@@ -221,7 +211,7 @@ msgstr "Move Mode"
msgid "Rotate Mode"
msgstr ""
-#: gschem/src/i_basic.c:91 gschem/lib/system-gschemrc.scm:1413
+#: gschem/src/i_basic.c:91 gschem/lib/system-gschemrc.scm:1415
msgid "Mirror Mode"
msgstr "Mirror Mode"
@@ -274,22 +264,22 @@ msgstr ""
msgid "Pin Mode"
msgstr ""
-#: gschem/src/i_basic.c:135 gschem/src/i_callbacks.c:544
-#: gschem/src/i_callbacks.c:568
+#: gschem/src/i_basic.c:135 gschem/src/i_callbacks.c:576
+#: gschem/src/i_callbacks.c:600
msgid "Copy"
msgstr ""
-#: gschem/src/i_basic.c:137 gschem/src/i_callbacks.c:634
-#: gschem/src/i_callbacks.c:658
+#: gschem/src/i_basic.c:137 gschem/src/i_callbacks.c:666
+#: gschem/src/i_callbacks.c:690
msgid "Move"
msgstr ""
-#: gschem/src/i_basic.c:139 gschem/src/i_callbacks.c:589
-#: gschem/src/i_callbacks.c:613
+#: gschem/src/i_basic.c:139 gschem/src/i_callbacks.c:621
+#: gschem/src/i_callbacks.c:645
msgid "Multiple Copy"
msgstr ""
-#: gschem/src/i_basic.c:142 gschem/lib/system-gschemrc.scm:1410
+#: gschem/src/i_basic.c:142 gschem/lib/system-gschemrc.scm:1412
msgid "Multiple Copy Mode"
msgstr "Multiple Copy Mode"
@@ -309,7 +299,7 @@ msgstr ""
msgid "Action"
msgstr ""
-#: gschem/src/i_basic.c:260 gschem/src/x_dialog.c:2312
+#: gschem/src/i_basic.c:260 gschem/src/x_dialog.c:2316
#: gschem/src/x_window.c:491
msgid "Stroke"
msgstr ""
@@ -340,7 +330,7 @@ msgstr ""
msgid "Documentation for [%s,%s,%s,%s]\n"
msgstr ""
-#: gschem/src/i_callbacks.c:123 gschem/src/i_callbacks.c:1699
+#: gschem/src/i_callbacks.c:123 gschem/src/i_callbacks.c:1706
#, c-format
msgid "New page created [%s]\n"
msgstr ""
@@ -362,327 +352,323 @@ msgstr ""
msgid "Closing Window\n"
msgstr ""
-#: gschem/src/i_callbacks.c:549 gschem/src/i_callbacks.c:594
-#: gschem/src/i_callbacks.c:639
+#: gschem/src/i_callbacks.c:581 gschem/src/i_callbacks.c:626
+#: gschem/src/i_callbacks.c:671
msgid "Select objs first"
msgstr ""
-#: gschem/src/i_callbacks.c:678 gschem/src/x_multiattrib.c:1491
+#: gschem/src/i_callbacks.c:710 gschem/src/x_multiattrib.c:1503
msgid "Delete"
msgstr "Delete"
-#: gschem/src/i_callbacks.c:703
+#: gschem/src/i_callbacks.c:735
msgid "Edit"
msgstr "Edit"
-#: gschem/src/i_callbacks.c:718
+#: gschem/src/i_callbacks.c:750
msgid "Edit pin type"
msgstr ""
-#: gschem/src/i_callbacks.c:737
+#: gschem/src/i_callbacks.c:769
msgid "Edit Text"
msgstr ""
-#: gschem/src/i_callbacks.c:760
+#: gschem/src/i_callbacks.c:792
msgid "Slot"
msgstr ""
-#: gschem/src/i_callbacks.c:777
+#: gschem/src/i_callbacks.c:809
msgid "Color"
msgstr ""
-#: gschem/src/i_callbacks.c:814 gschem/src/i_callbacks.c:859
+#: gschem/src/i_callbacks.c:846 gschem/src/i_callbacks.c:891
msgid "Rotate"
msgstr ""
-#: gschem/src/i_callbacks.c:882 gschem/src/i_callbacks.c:907
+#: gschem/src/i_callbacks.c:913 gschem/src/i_callbacks.c:938
msgid "Mirror"
msgstr ""
-#: gschem/src/i_callbacks.c:928 gschem/src/x_dialog.c:2315
-#: gschem/lib/system-gschemrc.scm:1422
+#: gschem/src/i_callbacks.c:959 gschem/src/x_dialog.c:2319
+#: gschem/lib/system-gschemrc.scm:1424
msgid "Lock"
msgstr "Lock"
-#: gschem/src/i_callbacks.c:946 gschem/lib/system-gschemrc.scm:1423
+#: gschem/src/i_callbacks.c:977 gschem/lib/system-gschemrc.scm:1425
msgid "Unlock"
msgstr "Unlock"
-#: gschem/src/i_callbacks.c:964 gschem/src/x_dialog.c:1734
+#: gschem/src/i_callbacks.c:995 gschem/src/x_dialog.c:1737
msgid "Translate"
msgstr ""
-#: gschem/src/i_callbacks.c:967
+#: gschem/src/i_callbacks.c:998
msgid "WARNING: Do not translate with snap off!\n"
msgstr ""
-#: gschem/src/i_callbacks.c:968
+#: gschem/src/i_callbacks.c:999
msgid "WARNING: Turning snap on and continuing with translate.\n"
msgstr ""
-#: gschem/src/i_callbacks.c:975
+#: gschem/src/i_callbacks.c:1006
msgid "WARNING: Snap grid size is not equal to 100!\n"
msgstr ""
-#: gschem/src/i_callbacks.c:977
+#: gschem/src/i_callbacks.c:1008
msgid ""
"WARNING: If you are translating a symbol to the origin, the snap grid size "
"should be set to 100\n"
msgstr ""
-#: gschem/src/i_callbacks.c:1008
+#: gschem/src/i_callbacks.c:1039
msgid "Embed"
msgstr ""
-#: gschem/src/i_callbacks.c:1047
+#: gschem/src/i_callbacks.c:1078
msgid "Unembed"
msgstr ""
-#: gschem/src/i_callbacks.c:1089
+#: gschem/src/i_callbacks.c:1120
msgid "Update"
msgstr ""
-#: gschem/src/i_callbacks.c:1136
+#: gschem/src/i_callbacks.c:1167
msgid "ShowHidden"
msgstr ""
-#: gschem/src/i_callbacks.c:1160
-msgid "MakeVisible"
-msgstr ""
-
-#: gschem/src/i_callbacks.c:1466 gschem/src/i_callbacks.c:1538
+#: gschem/src/i_callbacks.c:1473 gschem/src/i_callbacks.c:1545
msgid "Pan"
msgstr "Pan"
-#: gschem/src/i_callbacks.c:1743
+#: gschem/src/i_callbacks.c:1750
msgid "Really revert page?"
msgstr ""
-#: gschem/src/i_callbacks.c:1813
+#: gschem/src/i_callbacks.c:1820
msgid "Copy to clipboard"
msgstr ""
-#: gschem/src/i_callbacks.c:1831
+#: gschem/src/i_callbacks.c:1838
msgid "Cut to clipboard"
msgstr ""
-#: gschem/src/i_callbacks.c:1849
+#: gschem/src/i_callbacks.c:1856
msgid "Paste from clipboard"
msgstr ""
-#: gschem/src/i_callbacks.c:1861 gschem/src/i_callbacks.c:2100
-#: gschem/src/i_callbacks.c:2122 gschem/src/i_callbacks.c:2144
-#: gschem/src/i_callbacks.c:2166 gschem/src/i_callbacks.c:2188
+#: gschem/src/i_callbacks.c:1868 gschem/src/i_callbacks.c:2107
+#: gschem/src/i_callbacks.c:2129 gschem/src/i_callbacks.c:2151
+#: gschem/src/i_callbacks.c:2173 gschem/src/i_callbacks.c:2195
msgid "Empty buffer"
msgstr ""
-#: gschem/src/i_callbacks.c:1906
+#: gschem/src/i_callbacks.c:1913
msgid "Copy 1"
msgstr ""
-#: gschem/src/i_callbacks.c:1925
+#: gschem/src/i_callbacks.c:1932
msgid "Copy 2"
msgstr ""
-#: gschem/src/i_callbacks.c:1944
+#: gschem/src/i_callbacks.c:1951
msgid "Copy 3"
msgstr ""
-#: gschem/src/i_callbacks.c:1963
+#: gschem/src/i_callbacks.c:1970
msgid "Copy 4"
msgstr ""
-#: gschem/src/i_callbacks.c:1982
+#: gschem/src/i_callbacks.c:1989
msgid "Copy 5"
msgstr ""
-#: gschem/src/i_callbacks.c:2001
+#: gschem/src/i_callbacks.c:2008
msgid "Cut 1"
msgstr ""
-#: gschem/src/i_callbacks.c:2020
+#: gschem/src/i_callbacks.c:2027
msgid "Cut 2"
msgstr ""
-#: gschem/src/i_callbacks.c:2039
+#: gschem/src/i_callbacks.c:2046
msgid "Cut 3"
msgstr ""
-#: gschem/src/i_callbacks.c:2058
+#: gschem/src/i_callbacks.c:2065
msgid "Cut 4"
msgstr ""
-#: gschem/src/i_callbacks.c:2077
+#: gschem/src/i_callbacks.c:2084
msgid "Cut 5"
msgstr ""
-#: gschem/src/i_callbacks.c:2093
+#: gschem/src/i_callbacks.c:2100
msgid "Paste 1"
msgstr ""
-#: gschem/src/i_callbacks.c:2115
+#: gschem/src/i_callbacks.c:2122
msgid "Paste 2"
msgstr ""
-#: gschem/src/i_callbacks.c:2137
+#: gschem/src/i_callbacks.c:2144
msgid "Paste 3"
msgstr ""
-#: gschem/src/i_callbacks.c:2159
+#: gschem/src/i_callbacks.c:2166
msgid "Paste 4"
msgstr ""
-#: gschem/src/i_callbacks.c:2181
+#: gschem/src/i_callbacks.c:2188
msgid "Paste 5"
msgstr ""
-#: gschem/src/i_callbacks.c:2318 gschem/src/x_window.c:355
+#: gschem/src/i_callbacks.c:2325 gschem/src/x_window.c:355
msgid "Component"
msgstr ""
-#: gschem/src/i_callbacks.c:2354 gschem/src/i_callbacks.c:2373
-#: gschem/src/x_dialog.c:2285
+#: gschem/src/i_callbacks.c:2361 gschem/src/i_callbacks.c:2380
+#: gschem/src/x_dialog.c:2289
msgid "Attribute"
msgstr ""
-#: gschem/src/i_callbacks.c:2395 gschem/src/i_callbacks.c:2422
-#: gschem/src/x_dialog.c:2282
+#: gschem/src/i_callbacks.c:2402 gschem/src/i_callbacks.c:2429
+#: gschem/src/x_dialog.c:2286
msgid "Net"
msgstr "Net"
-#: gschem/src/i_callbacks.c:2466 gschem/src/i_callbacks.c:2493
-#: gschem/src/x_dialog.c:2300 gschem/src/x_window.c:375
+#: gschem/src/i_callbacks.c:2473 gschem/src/i_callbacks.c:2500
+#: gschem/src/x_dialog.c:2304 gschem/src/x_window.c:375
msgid "Bus"
msgstr "Bus"
-#: gschem/src/i_callbacks.c:2574 gschem/src/i_callbacks.c:2597
+#: gschem/src/i_callbacks.c:2581 gschem/src/i_callbacks.c:2604
msgid "Line"
msgstr "Line"
-#: gschem/src/i_callbacks.c:2619 gschem/src/i_callbacks.c:2642
+#: gschem/src/i_callbacks.c:2626 gschem/src/i_callbacks.c:2649
msgid "Box"
msgstr "Box"
-#: gschem/src/i_callbacks.c:2698 gschem/src/i_callbacks.c:2722
+#: gschem/src/i_callbacks.c:2705 gschem/src/i_callbacks.c:2729
msgid "Circle"
msgstr "Circle"
-#: gschem/src/i_callbacks.c:2744 gschem/src/i_callbacks.c:2767
+#: gschem/src/i_callbacks.c:2751 gschem/src/i_callbacks.c:2774
msgid "Arc"
msgstr "Arc"
-#: gschem/src/i_callbacks.c:2789 gschem/src/i_callbacks.c:2812
-#: gschem/src/x_dialog.c:2273
+#: gschem/src/i_callbacks.c:2796 gschem/src/i_callbacks.c:2819
+#: gschem/src/x_dialog.c:2277
msgid "Pin"
msgstr "Pin"
-#: gschem/src/i_callbacks.c:2871
+#: gschem/src/i_callbacks.c:2878
#, c-format
msgid "Searching for source [%s]\n"
msgstr ""
-#: gschem/src/i_callbacks.c:2895
+#: gschem/src/i_callbacks.c:2902
#, c-format
msgid "Cannot find source [%s]\n"
msgstr ""
-#: gschem/src/i_callbacks.c:2964
+#: gschem/src/i_callbacks.c:2965
#, c-format
msgid "Searching for symbol [%s]\n"
msgstr ""
-#: gschem/src/i_callbacks.c:2970
+#: gschem/src/i_callbacks.c:2971
msgid "Symbol is not a real file. Symbol cannot be loaded.\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3001
+#: gschem/src/i_callbacks.c:3002
msgid "Cannot find any schematics above the current one!\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3055
+#: gschem/src/i_callbacks.c:3056
msgid ""
"This command retrieves the component documentation from the web, but there "
"is no component selected"
msgstr ""
-#: gschem/src/i_callbacks.c:3083
+#: gschem/src/i_callbacks.c:3084
msgid "Attach"
msgstr "Attach"
-#: gschem/src/i_callbacks.c:3130
+#: gschem/src/i_callbacks.c:3131
msgid "Detach"
msgstr "Detach"
-#: gschem/src/i_callbacks.c:3165
+#: gschem/src/i_callbacks.c:3166
msgid "ShowN"
msgstr ""
-#: gschem/src/i_callbacks.c:3201
+#: gschem/src/i_callbacks.c:3202
msgid "ShowV"
msgstr ""
-#: gschem/src/i_callbacks.c:3237
+#: gschem/src/i_callbacks.c:3238
msgid "ShowB"
msgstr ""
-#: gschem/src/i_callbacks.c:3274
+#: gschem/src/i_callbacks.c:3275
msgid "VisToggle"
msgstr ""
-#: gschem/src/i_callbacks.c:3304
+#: gschem/src/i_callbacks.c:3305
#, c-format
msgid "Sorry but this is a non-functioning menu option\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3394
+#: gschem/src/i_callbacks.c:3395
msgid "Action feedback mode set to OUTLINE\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3397
+#: gschem/src/i_callbacks.c:3398
msgid "Action feedback mode set to BOUNDINGBOX\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3422
+#: gschem/src/i_callbacks.c:3423
msgid "Grid OFF\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3423
+#: gschem/src/i_callbacks.c:3424
msgid "Dot grid selected\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3424
+#: gschem/src/i_callbacks.c:3425
msgid "Mesh grid selected\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3445
+#: gschem/src/i_callbacks.c:3446
msgid "Snap OFF (CAUTION!)\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3448
+#: gschem/src/i_callbacks.c:3449
msgid "Snap ON\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3451
+#: gschem/src/i_callbacks.c:3452
msgid "Snap back to the grid (CAUTION!)\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3477
+#: gschem/src/i_callbacks.c:3478
msgid "Rubber band OFF \n"
msgstr ""
-#: gschem/src/i_callbacks.c:3480
+#: gschem/src/i_callbacks.c:3481
msgid "Rubber band ON\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3495
+#: gschem/src/i_callbacks.c:3496
msgid "magnetic net mode: ON\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3498
+#: gschem/src/i_callbacks.c:3499
msgid "magnetic net mode: OFF\n"
msgstr ""
-#: gschem/src/o_box.c:153
+#: gschem/src/o_box.c:149
#, c-format
msgid "Unknown type for box (fill)!\n"
msgstr ""
@@ -702,17 +688,17 @@ msgstr ""
msgid "Got an invalid buffer_number [o_buffer_paste_start]\n"
msgstr ""
-#: gschem/src/o_bus.c:118
+#: gschem/src/o_bus.c:117
#, c-format
msgid "Got an invalid which one in o_bus_draw_stretch\n"
msgstr ""
-#: gschem/src/o_circle.c:134
+#: gschem/src/o_circle.c:130
#, c-format
msgid "Unknown type for circle (fill)!\n"
msgstr ""
-#: gschem/src/o_complex.c:243 gschem/src/o_complex.c:247
+#: gschem/src/o_complex.c:237 gschem/src/o_complex.c:241
#, c-format
msgid "Translating schematic [%d %d]\n"
msgstr ""
@@ -730,35 +716,35 @@ msgstr ""
msgid "Object already unlocked\n"
msgstr ""
-#: gschem/src/o_misc.c:413
+#: gschem/src/o_misc.c:409
msgid "Hidden text is now visible\n"
msgstr ""
-#: gschem/src/o_misc.c:415
+#: gschem/src/o_misc.c:411
msgid "Hidden text is now invisible\n"
msgstr ""
-#: gschem/src/o_misc.c:668
+#: gschem/src/o_misc.c:636
#, c-format
msgid "Could not find symbol [%s] in library. Update failed.\n"
msgstr ""
-#: gschem/src/o_misc.c:783
+#: gschem/src/o_misc.c:751
#, c-format
msgid "o_autosave_backups: Can't get the real filename of %s."
msgstr ""
-#: gschem/src/o_misc.c:827
+#: gschem/src/o_misc.c:795
#, c-format
msgid "Could NOT set previous backup file [%s] read-write\n"
msgstr ""
-#: gschem/src/o_misc.c:845
+#: gschem/src/o_misc.c:815
#, c-format
msgid "Could NOT set backup file [%s] readonly\n"
msgstr ""
-#: gschem/src/o_misc.c:850
+#: gschem/src/o_misc.c:820
#, c-format
msgid "Could NOT save backup file [%s]\n"
msgstr ""
@@ -778,36 +764,36 @@ msgstr ""
msgid "Got a non line object in o_move_check_endpoint\n"
msgstr ""
-#: gschem/src/o_net.c:159
+#: gschem/src/o_net.c:158
#, c-format
msgid "Got an invalid which one in o_net_draw_stretch\n"
msgstr ""
-#: gschem/src/o_net.c:538
+#: gschem/src/o_net.c:537
msgid "Warning: Starting net at off grid coordinate\n"
msgstr ""
-#: gschem/src/o_net.c:600
+#: gschem/src/o_net.c:599
msgid "Warning: Ending net at off grid coordinate\n"
msgstr ""
-#: gschem/src/o_net.c:932 gschem/src/o_net.c:969 gschem/src/o_net.c:1040
-#: gschem/src/o_net.c:1076
+#: gschem/src/o_net.c:931 gschem/src/o_net.c:968 gschem/src/o_net.c:1039
+#: gschem/src/o_net.c:1075
#, c-format
msgid "Tried to add more than two bus rippers. Internal gschem error.\n"
msgstr ""
-#: gschem/src/o_net.c:1144
+#: gschem/src/o_net.c:1143
#, c-format
msgid "Bus ripper symbol [%s] was not found in any component library\n"
msgstr ""
-#: gschem/src/o_path.c:352
+#: gschem/src/o_path.c:348
#, c-format
msgid "Unknown type for path (fill)!\n"
msgstr ""
-#: gschem/src/o_picture.c:163 gschem/src/o_picture.c:539
+#: gschem/src/o_picture.c:163 gschem/src/o_picture.c:537
#, c-format
msgid "Failed to load picture: %s"
msgstr ""
@@ -816,7 +802,7 @@ msgstr ""
msgid "Picture"
msgstr ""
-#: gschem/src/o_picture.c:447 gschem/src/x_attribedit.c:141
+#: gschem/src/o_picture.c:445 gschem/src/x_attribedit.c:141
#, c-format
msgid "ERROR: NULL object!\n"
msgstr ""
@@ -837,23 +823,45 @@ msgstr ""
msgid "New slot number out of range\n"
msgstr ""
-#: gschem/src/o_undo.c:304
+#: gschem/src/o_undo.c:303
msgid "Undo/Redo disabled in rc file\n"
msgstr ""
-#: gschem/src/parsecmd.c:47
+#: gschem/src/parsecmd.c:81
#, c-format
msgid ""
-"Usage: %s [OPTIONS] schematic_filename1 ... schematic_filenameN\n"
-" -q Quiet mode\n"
-" -v Verbose mode on\n"
-" -r filename Rc filename\n"
-" -s filename Script (guile) filename\n"
-" -o filename Output filename (for printing)\n"
-" -p Automatically place the window\n"
-" -t Print stroke information\n"
-" -h Help; this message\n"
+"Usage: %s [OPTION ...] [--] [FILE ...]\n"
+"\n"
+"Interactively edit gEDA schematics or symbols. If one or more FILEs\n"
+"are specified, open them for editing; otherwise, create a new, empty\n"
+"schematic.\n"
+"\n"
+"Options:\n"
+" -q, --quiet Quiet mode.\n"
+" -v, --verbose Verbose mode.\n"
+" -r, --config-file=FILE Additional configuration file to load.\n"
+" -L DIR Add DIR to Scheme search path.\n"
+" -c EXPR Scheme expression to run at startup.\n"
+" -s FILE Scheme script to run at startup.\n"
+" -o, --output=FILE Output filename (for printing).\n"
+" -p Automatically place the window.\n"
+" -V, --version Show version information.\n"
+" -h, --help Help; this message.\n"
+" -- Treat all remaining arguments as filenames.\n"
"\n"
+"Report bugs to <geda-bug@xxxxxxxx>\n"
+"gEDA/gaf homepage: <http://gpleda.org>\n"
+msgstr ""
+
+#: gschem/src/parsecmd.c:115
+#, c-format
+msgid ""
+"gEDA %s (g%.7s)\n"
+"Copyright (C) 1998-2011 gEDA developers\n"
+"This is free software, and you are welcome to redistribute it under\n"
+"certain conditions. For details, see the file `COPYING', which is\n"
+"included in the gEDA distribution.\n"
+"There is NO WARRANTY, to the extent permitted by law.\n"
msgstr ""
#: gschem/src/x_attribedit.c:127
@@ -865,56 +873,56 @@ msgstr ""
msgid "Single Attribute Editor"
msgstr ""
-#: gschem/src/x_attribedit.c:358
+#: gschem/src/x_attribedit.c:359
msgid "<b>Edit Attribute</b>"
msgstr ""
-#: gschem/src/x_attribedit.c:360
+#: gschem/src/x_attribedit.c:361
msgid "<b>Add Attribute</b>"
msgstr ""
-#: gschem/src/x_attribedit.c:376 gschem/src/x_multiattrib.c:1916
+#: gschem/src/x_attribedit.c:377 gschem/src/x_multiattrib.c:1927
msgid "Name:"
msgstr ""
-#: gschem/src/x_attribedit.c:393 gschem/src/x_multiattrib.c:1935
+#: gschem/src/x_attribedit.c:394 gschem/src/x_multiattrib.c:1946
msgid "Value:"
msgstr ""
-#: gschem/src/x_attribedit.c:409 gschem/src/x_multiattrib.c:1978
+#: gschem/src/x_attribedit.c:410 gschem/src/x_multiattrib.c:1989
msgid "Visible"
msgstr ""
-#: gschem/src/x_attribedit.c:429
+#: gschem/src/x_attribedit.c:430
msgid "Show Value Only"
msgstr ""
-#: gschem/src/x_attribedit.c:431
+#: gschem/src/x_attribedit.c:432
msgid "Show Name Only"
msgstr ""
-#: gschem/src/x_attribedit.c:433 gschem/src/x_multiattrib.c:1454
+#: gschem/src/x_attribedit.c:434 gschem/src/x_multiattrib.c:1466
msgid "Show Name & Value"
msgstr ""
-#: gschem/src/x_attribedit.c:440
+#: gschem/src/x_attribedit.c:441
msgid "<b>Attach Options</b>"
msgstr ""
-#: gschem/src/x_attribedit.c:455
+#: gschem/src/x_attribedit.c:456
msgid "All"
msgstr ""
-#: gschem/src/x_attribedit.c:463 gschem/src/x_compselect.c:896
-#: gschem/src/x_compselect.c:1010
+#: gschem/src/x_attribedit.c:464 gschem/src/x_compselect.c:904
+#: gschem/src/x_compselect.c:1018
msgid "Components"
msgstr ""
-#: gschem/src/x_attribedit.c:471 gschem/src/x_window.c:365
+#: gschem/src/x_attribedit.c:472 gschem/src/x_window.c:365
msgid "Nets"
msgstr ""
-#: gschem/src/x_attribedit.c:479
+#: gschem/src/x_attribedit.c:480
msgid "Replace existing attributes"
msgstr ""
@@ -930,91 +938,91 @@ msgid ""
"duplicate slot may cause problems: [symbolname=%s, number=%d, slot=%d]\n"
msgstr ""
-#: gschem/src/x_autonumber.c:673
+#: gschem/src/x_autonumber.c:675
msgid "No searchstring given in autonumber text.\n"
msgstr ""
-#: gschem/src/x_autonumber.c:725
+#: gschem/src/x_autonumber.c:727
msgid "No '*' or '?' given at the end of the autonumber text.\n"
msgstr ""
-#: gschem/src/x_autonumber.c:860
+#: gschem/src/x_autonumber.c:862
msgid "Diagonal"
msgstr ""
-#: gschem/src/x_autonumber.c:861
+#: gschem/src/x_autonumber.c:863
msgid "Top to bottom"
msgstr ""
-#: gschem/src/x_autonumber.c:861
+#: gschem/src/x_autonumber.c:863
msgid "Bottom to top"
msgstr ""
-#: gschem/src/x_autonumber.c:862
+#: gschem/src/x_autonumber.c:864
msgid "Left to right"
msgstr ""
-#: gschem/src/x_autonumber.c:862
+#: gschem/src/x_autonumber.c:864
msgid "Right to left"
msgstr ""
-#: gschem/src/x_autonumber.c:863
+#: gschem/src/x_autonumber.c:865
msgid "File order"
msgstr ""
-#: gschem/src/x_autonumber.c:1199
+#: gschem/src/x_autonumber.c:1201
msgid "Autonumber text"
msgstr ""
-#: gschem/src/x_autonumber.c:1223
+#: gschem/src/x_autonumber.c:1225
msgid "<b>Scope</b>"
msgstr ""
-#: gschem/src/x_autonumber.c:1245
+#: gschem/src/x_autonumber.c:1247
msgid "Search for:"
msgstr ""
-#: gschem/src/x_autonumber.c:1259
+#: gschem/src/x_autonumber.c:1261
msgid "Autonumber text in:"
msgstr ""
-#: gschem/src/x_autonumber.c:1266
+#: gschem/src/x_autonumber.c:1268
msgid "Skip numbers found in:"
msgstr ""
-#: gschem/src/x_autonumber.c:1278 gschem/src/x_autonumber.c:1287
+#: gschem/src/x_autonumber.c:1280 gschem/src/x_autonumber.c:1289
msgid "Selected objects"
msgstr ""
-#: gschem/src/x_autonumber.c:1279 gschem/src/x_autonumber.c:1288
+#: gschem/src/x_autonumber.c:1281 gschem/src/x_autonumber.c:1290
msgid "Current page"
msgstr ""
-#: gschem/src/x_autonumber.c:1280 gschem/src/x_autonumber.c:1289
+#: gschem/src/x_autonumber.c:1282 gschem/src/x_autonumber.c:1291
msgid "Whole hierarchy"
msgstr ""
-#: gschem/src/x_autonumber.c:1291
+#: gschem/src/x_autonumber.c:1293
msgid "Overwrite existing numbers"
msgstr ""
-#: gschem/src/x_autonumber.c:1296
+#: gschem/src/x_autonumber.c:1298
msgid "<b>Options</b>"
msgstr ""
-#: gschem/src/x_autonumber.c:1318
+#: gschem/src/x_autonumber.c:1320
msgid "Starting number:"
msgstr ""
-#: gschem/src/x_autonumber.c:1325
+#: gschem/src/x_autonumber.c:1327
msgid "Sort order:"
msgstr ""
-#: gschem/src/x_autonumber.c:1346
+#: gschem/src/x_autonumber.c:1348
msgid "Remove numbers"
msgstr ""
-#: gschem/src/x_autonumber.c:1350
+#: gschem/src/x_autonumber.c:1352
msgid "Automatic slotting"
msgstr ""
@@ -1051,48 +1059,48 @@ msgstr ""
msgid "Tried to get an invalid outline color: %d\n"
msgstr ""
-#: gschem/src/x_compselect.c:1040
+#: gschem/src/x_compselect.c:1048
msgid "Filter:"
msgstr ""
-#: gschem/src/x_compselect.c:1143 gschem/src/x_dialog.c:3663
-#: gschem/src/x_multiattrib.c:1782
+#: gschem/src/x_compselect.c:1151 gschem/src/x_dialog.c:3667
+#: gschem/src/x_multiattrib.c:1793
msgid "Name"
msgstr ""
-#: gschem/src/x_compselect.c:1152 gschem/src/x_multiattrib.c:1806
+#: gschem/src/x_compselect.c:1160 gschem/src/x_multiattrib.c:1817
msgid "Value"
msgstr ""
-#: gschem/src/x_compselect.c:1191
+#: gschem/src/x_compselect.c:1199
msgid "Default behavior - reference component"
msgstr ""
-#: gschem/src/x_compselect.c:1194
+#: gschem/src/x_compselect.c:1202
msgid "Embed component in schematic"
msgstr ""
-#: gschem/src/x_compselect.c:1197
+#: gschem/src/x_compselect.c:1205
msgid "Include component as individual objects"
msgstr ""
-#: gschem/src/x_compselect.c:1354
+#: gschem/src/x_compselect.c:1362
msgid "Select Component..."
msgstr ""
-#: gschem/src/x_compselect.c:1377
+#: gschem/src/x_compselect.c:1385
msgid "In Use"
msgstr ""
-#: gschem/src/x_compselect.c:1381
+#: gschem/src/x_compselect.c:1389
msgid "Libraries"
msgstr ""
-#: gschem/src/x_compselect.c:1390 gschem/src/x_fileselect.c:122
+#: gschem/src/x_compselect.c:1398 gschem/src/x_fileselect.c:122
msgid "Preview"
msgstr ""
-#: gschem/src/x_compselect.c:1418
+#: gschem/src/x_compselect.c:1426
msgid "Attributes"
msgstr "Attributes"
@@ -1147,336 +1155,336 @@ msgstr ""
msgid "Edit Text Properties"
msgstr ""
-#: gschem/src/x_dialog.c:471
+#: gschem/src/x_dialog.c:472
msgid "<b>Text Content</b>"
msgstr ""
-#: gschem/src/x_dialog.c:507
+#: gschem/src/x_dialog.c:508
msgid "<b>Text Properties</b>"
msgstr ""
-#: gschem/src/x_dialog.c:522
+#: gschem/src/x_dialog.c:523
msgid "Color:"
msgstr ""
-#: gschem/src/x_dialog.c:529
+#: gschem/src/x_dialog.c:530
msgid "Size:"
msgstr ""
-#: gschem/src/x_dialog.c:538
+#: gschem/src/x_dialog.c:539
msgid "Alignment:"
msgstr ""
-#: gschem/src/x_dialog.c:587
+#: gschem/src/x_dialog.c:588
msgid "Solid"
msgstr ""
-#: gschem/src/x_dialog.c:588
+#: gschem/src/x_dialog.c:589
msgid "Dotted"
msgstr ""
-#: gschem/src/x_dialog.c:589
+#: gschem/src/x_dialog.c:590
msgid "Dashed"
msgstr ""
-#: gschem/src/x_dialog.c:590
+#: gschem/src/x_dialog.c:591
msgid "Center"
msgstr ""
-#: gschem/src/x_dialog.c:591
+#: gschem/src/x_dialog.c:592
msgid "Phantom"
msgstr ""
-#: gschem/src/x_dialog.c:592 gschem/src/x_dialog.c:689
-#: gschem/src/x_dialog.c:698 gschem/src/x_dialog.c:707
-#: gschem/src/x_dialog.c:808 gschem/src/x_dialog.c:810
-#: gschem/src/x_dialog.c:812 gschem/src/x_dialog.c:1038
-#: gschem/src/x_dialog.c:1141 gschem/src/x_dialog.c:1150
-#: gschem/src/x_dialog.c:1159 gschem/src/x_dialog.c:1168
-#: gschem/src/x_dialog.c:1177 gschem/src/x_dialog.c:1290
-#: gschem/src/x_dialog.c:1292 gschem/src/x_dialog.c:1294
-#: gschem/src/x_dialog.c:1296 gschem/src/x_dialog.c:1298
+#: gschem/src/x_dialog.c:593 gschem/src/x_dialog.c:690
+#: gschem/src/x_dialog.c:699 gschem/src/x_dialog.c:708
+#: gschem/src/x_dialog.c:809 gschem/src/x_dialog.c:811
+#: gschem/src/x_dialog.c:813 gschem/src/x_dialog.c:1039
+#: gschem/src/x_dialog.c:1142 gschem/src/x_dialog.c:1151
+#: gschem/src/x_dialog.c:1160 gschem/src/x_dialog.c:1169
+#: gschem/src/x_dialog.c:1178 gschem/src/x_dialog.c:1291
+#: gschem/src/x_dialog.c:1293 gschem/src/x_dialog.c:1295
+#: gschem/src/x_dialog.c:1297 gschem/src/x_dialog.c:1299
msgid "*unchanged*"
msgstr ""
-#: gschem/src/x_dialog.c:916
+#: gschem/src/x_dialog.c:917
msgid "Edit Line Width & Type"
msgstr ""
-#: gschem/src/x_dialog.c:955 gschem/src/x_print.c:307
+#: gschem/src/x_dialog.c:956 gschem/src/x_print.c:307
msgid "Type:"
msgstr ""
-#: gschem/src/x_dialog.c:959
+#: gschem/src/x_dialog.c:960
msgid "Width:"
msgstr ""
-#: gschem/src/x_dialog.c:963
+#: gschem/src/x_dialog.c:964
msgid "Dash Length:"
msgstr ""
-#: gschem/src/x_dialog.c:967
+#: gschem/src/x_dialog.c:968
msgid "Dash Space:"
msgstr ""
-#: gschem/src/x_dialog.c:1034
+#: gschem/src/x_dialog.c:1035
msgid "Hollow"
msgstr ""
-#: gschem/src/x_dialog.c:1035
+#: gschem/src/x_dialog.c:1036
msgid "Filled"
msgstr ""
-#: gschem/src/x_dialog.c:1036
+#: gschem/src/x_dialog.c:1037
msgid "Mesh"
msgstr ""
-#: gschem/src/x_dialog.c:1037
+#: gschem/src/x_dialog.c:1038
msgid "Hatch"
msgstr ""
-#: gschem/src/x_dialog.c:1406
+#: gschem/src/x_dialog.c:1407
msgid "Edit Fill Type"
msgstr ""
-#: gschem/src/x_dialog.c:1444
+#: gschem/src/x_dialog.c:1446
msgid "Fill Type:"
msgstr ""
-#: gschem/src/x_dialog.c:1448
+#: gschem/src/x_dialog.c:1450
msgid "Line Width:"
msgstr ""
-#: gschem/src/x_dialog.c:1452
+#: gschem/src/x_dialog.c:1454
msgid "Angle 1:"
msgstr ""
-#: gschem/src/x_dialog.c:1456
+#: gschem/src/x_dialog.c:1458
msgid "Pitch 1:"
msgstr ""
-#: gschem/src/x_dialog.c:1460
+#: gschem/src/x_dialog.c:1462
msgid "Angle 2:"
msgstr ""
-#: gschem/src/x_dialog.c:1464
+#: gschem/src/x_dialog.c:1466
msgid "Pitch 2:"
msgstr ""
-#: gschem/src/x_dialog.c:1591
+#: gschem/src/x_dialog.c:1593
msgid "Arc Params"
msgstr ""
-#: gschem/src/x_dialog.c:1631
+#: gschem/src/x_dialog.c:1634
msgid "Arc Radius:"
msgstr ""
-#: gschem/src/x_dialog.c:1639
+#: gschem/src/x_dialog.c:1642
msgid "Start Angle:"
msgstr ""
-#: gschem/src/x_dialog.c:1647
+#: gschem/src/x_dialog.c:1650
msgid "Degrees of Sweep:"
msgstr ""
-#: gschem/src/x_dialog.c:1764
+#: gschem/src/x_dialog.c:1768
msgid ""
"Offset to translate?\n"
"(0 for origin)"
msgstr ""
-#: gschem/src/x_dialog.c:1832
+#: gschem/src/x_dialog.c:1836
msgid "Text Size"
msgstr ""
-#: gschem/src/x_dialog.c:1862
+#: gschem/src/x_dialog.c:1866
msgid "Enter new text size:"
msgstr ""
-#: gschem/src/x_dialog.c:1938
+#: gschem/src/x_dialog.c:1942
msgid "Snap Size"
msgstr ""
-#: gschem/src/x_dialog.c:1968
+#: gschem/src/x_dialog.c:1972
msgid "Enter new snap grid spacing:"
msgstr ""
-#: gschem/src/x_dialog.c:2045
+#: gschem/src/x_dialog.c:2049
msgid "Edit slot number"
msgstr ""
-#: gschem/src/x_dialog.c:2076
+#: gschem/src/x_dialog.c:2080
msgid "Edit slot number:"
msgstr ""
-#: gschem/src/x_dialog.c:2117
+#: gschem/src/x_dialog.c:2121
#, c-format
msgid "%s%s (%s)"
msgstr ""
-#: gschem/src/x_dialog.c:2140
+#: gschem/src/x_dialog.c:2144
msgid "About gschem"
msgstr "About gschem"
-#: gschem/src/x_dialog.c:2141
+#: gschem/src/x_dialog.c:2145
msgid "gEDA: GPL Electronic Design Automation"
msgstr ""
-#: gschem/src/x_dialog.c:2142
+#: gschem/src/x_dialog.c:2146
msgid ""
"Copyright © 1998-2009 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
"Copyright © 1998-2009 gEDA Contributors (see ChangeLog for details)"
msgstr ""
-#: gschem/src/x_dialog.c:2201
+#: gschem/src/x_dialog.c:2205
msgid "Coords"
msgstr ""
-#: gschem/src/x_dialog.c:2222
+#: gschem/src/x_dialog.c:2226
msgid "Screen"
msgstr ""
-#: gschem/src/x_dialog.c:2231
+#: gschem/src/x_dialog.c:2235
msgid "World"
msgstr ""
-#: gschem/src/x_dialog.c:2270
+#: gschem/src/x_dialog.c:2274
msgid "Background"
msgstr ""
-#: gschem/src/x_dialog.c:2276
+#: gschem/src/x_dialog.c:2280
msgid "Net endpoint"
msgstr ""
-#: gschem/src/x_dialog.c:2279
+#: gschem/src/x_dialog.c:2283
msgid "Graphic"
msgstr ""
-#: gschem/src/x_dialog.c:2288
+#: gschem/src/x_dialog.c:2292
msgid "Logic bubble"
msgstr ""
-#: gschem/src/x_dialog.c:2291
+#: gschem/src/x_dialog.c:2295
msgid "Grid point"
msgstr ""
-#: gschem/src/x_dialog.c:2294
+#: gschem/src/x_dialog.c:2298
msgid "Detached attribute"
msgstr ""
-#: gschem/src/x_dialog.c:2297 gschem/src/x_window.c:383
+#: gschem/src/x_dialog.c:2301 gschem/src/x_window.c:383
msgid "Text"
msgstr ""
-#: gschem/src/x_dialog.c:2303
+#: gschem/src/x_dialog.c:2307
msgid "Selection"
msgstr ""
-#: gschem/src/x_dialog.c:2306
+#: gschem/src/x_dialog.c:2310
msgid "Bounding box"
msgstr ""
-#: gschem/src/x_dialog.c:2309
+#: gschem/src/x_dialog.c:2313
msgid "Zoom box"
msgstr ""
-#: gschem/src/x_dialog.c:2318
+#: gschem/src/x_dialog.c:2322
msgid "Output background"
msgstr ""
-#: gschem/src/x_dialog.c:2321
+#: gschem/src/x_dialog.c:2325
msgid "Net junction"
msgstr ""
-#: gschem/src/x_dialog.c:2324
+#: gschem/src/x_dialog.c:2328
msgid "Mesh grid major"
msgstr ""
-#: gschem/src/x_dialog.c:2327
+#: gschem/src/x_dialog.c:2331
msgid "Mesh grid minor"
msgstr ""
-#: gschem/src/x_dialog.c:2330
+#: gschem/src/x_dialog.c:2334
msgid "Unknown"
msgstr ""
-#: gschem/src/x_dialog.c:2481
+#: gschem/src/x_dialog.c:2485
#, c-format
msgid "ERROR: NULL object in color_edit_dialog_apply!\n"
msgstr ""
-#: gschem/src/x_dialog.c:2525
+#: gschem/src/x_dialog.c:2529
msgid "Color Edit"
msgstr ""
-#: gschem/src/x_dialog.c:2556
+#: gschem/src/x_dialog.c:2560
msgid "Object color:"
msgstr ""
-#: gschem/src/x_dialog.c:2614
+#: gschem/src/x_dialog.c:2618
msgid "Hotkeys"
msgstr "Hotkeys"
-#: gschem/src/x_dialog.c:2678
+#: gschem/src/x_dialog.c:2682
msgid "Function"
msgstr ""
-#: gschem/src/x_dialog.c:2685
+#: gschem/src/x_dialog.c:2689
msgid "Keystroke(s)"
msgstr ""
-#: gschem/src/x_dialog.c:2991
+#: gschem/src/x_dialog.c:2995
msgid "Find Text"
msgstr ""
-#: gschem/src/x_dialog.c:3022
+#: gschem/src/x_dialog.c:3026
msgid "Text to find:"
msgstr ""
-#: gschem/src/x_dialog.c:3032
+#: gschem/src/x_dialog.c:3036
msgid "descend into hierarchy"
msgstr ""
-#: gschem/src/x_dialog.c:3097
+#: gschem/src/x_dialog.c:3101
msgid "Hide Text"
msgstr ""
-#: gschem/src/x_dialog.c:3128
+#: gschem/src/x_dialog.c:3132
msgid "Hide text starting with:"
msgstr ""
-#: gschem/src/x_dialog.c:3197
+#: gschem/src/x_dialog.c:3201
msgid "Show Text"
msgstr ""
-#: gschem/src/x_dialog.c:3228
+#: gschem/src/x_dialog.c:3232
msgid "Show text starting with:"
msgstr ""
-#: gschem/src/x_dialog.c:3685
+#: gschem/src/x_dialog.c:3689
msgid "S_elect the schematics you want to save:"
msgstr ""
-#: gschem/src/x_dialog.c:3779
+#: gschem/src/x_dialog.c:3784
#, c-format
msgid "Save the changes to schematic \"%s\" before closing?"
msgstr ""
-#: gschem/src/x_dialog.c:3785
+#: gschem/src/x_dialog.c:3790
#, c-format
msgid ""
"There are %d schematics with unsaved changes. Save changes before closing?"
msgstr ""
-#: gschem/src/x_dialog.c:3814
+#: gschem/src/x_dialog.c:3819
msgid "If you don't save, all your changes will be permanently lost."
msgstr ""
-#: gschem/src/x_dialog.c:3834
+#: gschem/src/x_dialog.c:3839
msgid "_Close without saving"
msgstr ""
-#: gschem/src/x_dialog.c:4170
+#: gschem/src/x_dialog.c:4175
#, c-format
msgid ""
"<span weight=\"bold\" size=\"larger\">The input attribute \"%s\" is invalid\n"
@@ -1487,19 +1495,19 @@ msgid ""
"The value cannot start with a space."
msgstr ""
-#: gschem/src/x_dialog.c:4172
+#: gschem/src/x_dialog.c:4177
msgid "Invalid Attribute"
msgstr ""
-#: gschem/src/x_dialog.c:4208
+#: gschem/src/x_dialog.c:4213
msgid "Pin type"
msgstr ""
-#: gschem/src/x_dialog.c:4232
+#: gschem/src/x_dialog.c:4237
msgid "Net pin"
msgstr ""
-#: gschem/src/x_dialog.c:4234
+#: gschem/src/x_dialog.c:4239
msgid "Bus pin (graphical)"
msgstr ""
@@ -1592,11 +1600,11 @@ msgstr ""
msgid "Write image..."
msgstr "Write image..."
-#: gschem/src/x_log.c:188
+#: gschem/src/x_log.c:209
msgid "** Invalid UTF-8 in log message. See stderr or gschem.log.\n"
msgstr ""
-#: gschem/src/x_log.c:256
+#: gschem/src/x_log.c:288
msgid "Status"
msgstr ""
@@ -1672,69 +1680,60 @@ msgstr ""
msgid "/Up"
msgstr ""
-#: gschem/src/x_menus.c:321
+#: gschem/src/x_menus.c:323
#, c-format
msgid "Tried to set the sensitivity on non-existent menu item '%s'\n"
msgstr ""
-#: gschem/src/x_menus.c:345
+#: gschem/src/x_menus.c:347
msgid "Popup_menu_item_factory doesn't exist!\n"
msgstr ""
-#: gschem/src/x_menus.c:358
+#: gschem/src/x_menus.c:360
msgid "Tried to set the sensitivity on a non-existent popup menu_item\n"
msgstr ""
-#: gschem/src/x_menus.c:438
-#, c-format
-msgid "Couldn't open file %s\n"
-msgstr ""
-
-#: gschem/src/x_menus.c:495
-msgid "Clear"
-msgstr ""
-
-#: gschem/src/x_multiattrib.c:911
+#: gschem/src/x_multiattrib.c:915
msgid "Attributes with empty name are not allowed. Please set a name."
msgstr ""
-#: gschem/src/x_multiattrib.c:1456
+#: gschem/src/x_multiattrib.c:1468
msgid "Show Value only"
msgstr ""
-#: gschem/src/x_multiattrib.c:1458
+#: gschem/src/x_multiattrib.c:1470
msgid "Show Name only"
msgstr ""
-#: gschem/src/x_multiattrib.c:1486
+#: gschem/src/x_multiattrib.c:1498
msgid "Promote"
msgstr ""
-#: gschem/src/x_multiattrib.c:1490
+#: gschem/src/x_multiattrib.c:1502
msgid "Duplicate"
msgstr ""
-#: gschem/src/x_multiattrib.c:1708
+#: gschem/src/x_multiattrib.c:1719
msgid "Edit Attributes"
msgstr ""
-#: gschem/src/x_multiattrib.c:1826
+#: gschem/src/x_multiattrib.c:1837
msgid "Vis?"
msgstr ""
-#: gschem/src/x_multiattrib.c:1844
+#: gschem/src/x_multiattrib.c:1855
msgid "N"
msgstr ""
-#: gschem/src/x_multiattrib.c:1862
+#: gschem/src/x_multiattrib.c:1873
msgid "V"
msgstr ""
-#: gschem/src/x_multiattrib.c:1884
+#: gschem/src/x_multiattrib.c:1895
msgid "Show inherited attributes"
msgstr ""
-#: gschem/src/x_multiattrib.c:1900
+#: gschem/src/x_multiattrib.c:1911
msgid "Add Attribute"
msgstr ""
@@ -1758,23 +1757,23 @@ msgstr "Close Page"
msgid "Discard Page"
msgstr ""
-#: gschem/src/x_pagesel.c:376
+#: gschem/src/x_pagesel.c:375
msgid "Page Manager"
msgstr ""
-#: gschem/src/x_pagesel.c:432
+#: gschem/src/x_pagesel.c:431
msgid "Filename"
msgstr ""
-#: gschem/src/x_pagesel.c:448
+#: gschem/src/x_pagesel.c:447
msgid "Changed"
msgstr ""
-#: gschem/src/x_pagesel.c:468
+#: gschem/src/x_pagesel.c:467
msgid "Right click on the filename for more options..."
msgstr ""
-#: gschem/src/x_preview.c:234
+#: gschem/src/x_preview.c:233
msgid "Preview Buffer"
msgstr ""
@@ -1830,23 +1829,23 @@ msgstr ""
msgid "Command:"
msgstr ""
-#: gschem/src/x_print.c:741
+#: gschem/src/x_print.c:745
msgid "No print destination specified\n"
msgstr ""
-#: gschem/src/x_print.c:748
+#: gschem/src/x_print.c:752
#, c-format
msgid "Cannot print current schematic to [%s]\n"
msgstr ""
-#: gschem/src/x_print.c:757
+#: gschem/src/x_print.c:761
#, c-format
msgid ""
"Error printing to file '%s'\n"
"Check the log window for more information"
msgstr ""
-#: gschem/src/x_print.c:764
+#: gschem/src/x_print.c:768
#, c-format
msgid "Printed current schematic to [%s]\n"
msgstr ""
@@ -1855,6 +1854,11 @@ msgstr ""
msgid "Execute Script..."
msgstr "Execute Script..."
+#: gschem/src/x_script.c:66
+#, c-format
+msgid "Executing guile script [%s]\n"
+msgstr ""
+
#: gschem/src/x_window.c:81
#, c-format
msgid "Couldn't allocate gc\n"
@@ -1962,35 +1966,35 @@ msgstr ""
msgid "New file [%s]\n"
msgstr ""
-#: gschem/src/x_window.c:857
+#: gschem/src/x_window.c:855
#, c-format
msgid "Could NOT save page [%s]\n"
msgstr ""
-#: gschem/src/x_window.c:858
+#: gschem/src/x_window.c:856
msgid "Error while trying to save"
msgstr ""
-#: gschem/src/x_window.c:867
+#: gschem/src/x_window.c:865
#, c-format
msgid "Saved as [%s]\n"
msgstr ""
-#: gschem/src/x_window.c:869
+#: gschem/src/x_window.c:867
#, c-format
msgid "Saved [%s]\n"
msgstr ""
-#: gschem/src/x_window.c:871
+#: gschem/src/x_window.c:869
msgid "Saved"
msgstr ""
-#: gschem/src/x_window.c:945
+#: gschem/src/x_window.c:943
#, c-format
msgid "Discarding page [%s]\n"
msgstr ""
-#: gschem/src/x_window.c:945
+#: gschem/src/x_window.c:943
#, c-format
msgid "Closing [%s]\n"
msgstr ""
@@ -2031,7 +2035,7 @@ msgstr ""
msgid "Save All"
msgstr "Save All"
-#: gschem/lib/system-gschemrc.scm:1386 gschem/lib/system-gschemrc.scm:1477
+#: gschem/lib/system-gschemrc.scm:1386 gschem/lib/system-gschemrc.scm:1478
msgid "_Revert"
msgstr ""
@@ -2043,7 +2047,7 @@ msgstr ""
msgid "Write _image..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1393 gschem/lib/system-gschemrc.scm:1478
+#: gschem/lib/system-gschemrc.scm:1393 gschem/lib/system-gschemrc.scm:1479
msgid "_Close"
msgstr ""
@@ -2075,390 +2079,398 @@ msgstr ""
msgid "_Delete"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1412
+#: gschem/lib/system-gschemrc.scm:1409
+#, fuzzy
+msgid "Select All"
+msgstr "Select Mode"
+
+#: gschem/lib/system-gschemrc.scm:1410
+msgid "Deselect"
+msgstr ""
+
+#: gschem/lib/system-gschemrc.scm:1414
msgid "Rotate 90 Mode"
msgstr "Rotate 90 Mode"
-#: gschem/lib/system-gschemrc.scm:1415
+#: gschem/lib/system-gschemrc.scm:1417
msgid "Edit..."
msgstr "Edit..."
-#: gschem/lib/system-gschemrc.scm:1416
+#: gschem/lib/system-gschemrc.scm:1418
msgid "Edit Text..."
msgstr "Edit Text..."
-#: gschem/lib/system-gschemrc.scm:1417
+#: gschem/lib/system-gschemrc.scm:1419
msgid "Slot..."
msgstr "Slot..."
-#: gschem/lib/system-gschemrc.scm:1418
+#: gschem/lib/system-gschemrc.scm:1420
msgid "Color..."
msgstr "Color..."
-#: gschem/lib/system-gschemrc.scm:1419
+#: gschem/lib/system-gschemrc.scm:1421
msgid "Line Width & Type..."
msgstr "Line Width & Type..."
-#: gschem/lib/system-gschemrc.scm:1420
+#: gschem/lib/system-gschemrc.scm:1422
msgid "Fill Type..."
msgstr "Fill Type..."
-#: gschem/lib/system-gschemrc.scm:1421
+#: gschem/lib/system-gschemrc.scm:1423
msgid "Symbol Translate..."
msgstr "Symbol Translate..."
-#: gschem/lib/system-gschemrc.scm:1425
+#: gschem/lib/system-gschemrc.scm:1427
msgid "Invoke Macro"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1426
+#: gschem/lib/system-gschemrc.scm:1428
msgid "Embed Component/Picture"
msgstr "Embed Component/Picture"
-#: gschem/lib/system-gschemrc.scm:1427
+#: gschem/lib/system-gschemrc.scm:1429
msgid "Unembed Component/Picture"
msgstr "Unembed Component/Picture"
-#: gschem/lib/system-gschemrc.scm:1428
+#: gschem/lib/system-gschemrc.scm:1430
msgid "Update Component"
msgstr "Update Component"
-#: gschem/lib/system-gschemrc.scm:1429
+#: gschem/lib/system-gschemrc.scm:1431
msgid "Show/Hide Inv Text"
msgstr "Show/Hide Inv Text"
-#: gschem/lib/system-gschemrc.scm:1430
-msgid "Make Inv Text Vis"
-msgstr "Make Inv Text Vis"
-
-#: gschem/lib/system-gschemrc.scm:1436
+#: gschem/lib/system-gschemrc.scm:1437
msgid "Copy into 1"
msgstr "Copy into 1"
-#: gschem/lib/system-gschemrc.scm:1437
+#: gschem/lib/system-gschemrc.scm:1438
msgid "Copy into 2"
msgstr "Copy into 2"
-#: gschem/lib/system-gschemrc.scm:1438
+#: gschem/lib/system-gschemrc.scm:1439
msgid "Copy into 3"
msgstr "Copy into 3"
-#: gschem/lib/system-gschemrc.scm:1439
+#: gschem/lib/system-gschemrc.scm:1440
msgid "Copy into 4"
msgstr "Copy into 4"
-#: gschem/lib/system-gschemrc.scm:1440
+#: gschem/lib/system-gschemrc.scm:1441
msgid "Copy into 5"
msgstr "Copy into 5"
-#: gschem/lib/system-gschemrc.scm:1441
+#: gschem/lib/system-gschemrc.scm:1442
msgid "Cut into 1"
msgstr "Cut into 1"
-#: gschem/lib/system-gschemrc.scm:1442
+#: gschem/lib/system-gschemrc.scm:1443
msgid "Cut into 2"
msgstr "Cut into 2"
-#: gschem/lib/system-gschemrc.scm:1443
+#: gschem/lib/system-gschemrc.scm:1444
msgid "Cut into 3"
msgstr "Cut into 3"
-#: gschem/lib/system-gschemrc.scm:1444
+#: gschem/lib/system-gschemrc.scm:1445
msgid "Cut into 4"
msgstr "Cut into 4"
-#: gschem/lib/system-gschemrc.scm:1445
+#: gschem/lib/system-gschemrc.scm:1446
msgid "Cut into 5"
msgstr "Cut into 5"
-#: gschem/lib/system-gschemrc.scm:1446
+#: gschem/lib/system-gschemrc.scm:1447
msgid "Paste from 1"
msgstr "Paste from 1"
-#: gschem/lib/system-gschemrc.scm:1447
+#: gschem/lib/system-gschemrc.scm:1448
msgid "Paste from 2"
msgstr "Paste from 2"
-#: gschem/lib/system-gschemrc.scm:1448
+#: gschem/lib/system-gschemrc.scm:1449
msgid "Paste from 3"
msgstr "Paste from 3"
-#: gschem/lib/system-gschemrc.scm:1449
+#: gschem/lib/system-gschemrc.scm:1450
msgid "Paste from 4"
msgstr "Paste from 4"
-#: gschem/lib/system-gschemrc.scm:1450
+#: gschem/lib/system-gschemrc.scm:1451
msgid "Paste from 5"
msgstr "Paste from 5"
-#: gschem/lib/system-gschemrc.scm:1456
+#: gschem/lib/system-gschemrc.scm:1457
msgid "_Redraw"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1457
+#: gschem/lib/system-gschemrc.scm:1458
msgid "_Pan"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1458
+#: gschem/lib/system-gschemrc.scm:1459
msgid "Zoom _Box"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1459
+#: gschem/lib/system-gschemrc.scm:1460
msgid "Zoom _Extents"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1460
+#: gschem/lib/system-gschemrc.scm:1461
msgid "Zoom _In"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1461
+#: gschem/lib/system-gschemrc.scm:1462
msgid "Zoom _Out"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1462
+#: gschem/lib/system-gschemrc.scm:1463
msgid "Zoom _Full"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1464
+#: gschem/lib/system-gschemrc.scm:1465
msgid "_Dark color scheme"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1465
+#: gschem/lib/system-gschemrc.scm:1466
msgid "_Light color scheme"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1466
+#: gschem/lib/system-gschemrc.scm:1467
msgid "B_W color scheme"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1473
+#: gschem/lib/system-gschemrc.scm:1474
msgid "_Manager..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1474
+#: gschem/lib/system-gschemrc.scm:1475
msgid "_Previous"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1475
+#: gschem/lib/system-gschemrc.scm:1476
msgid "_Next"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1476
+#: gschem/lib/system-gschemrc.scm:1477
msgid "Ne_w"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1480
+#: gschem/lib/system-gschemrc.scm:1481
msgid "_Discard"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1486
+#: gschem/lib/system-gschemrc.scm:1487
msgid "_Component..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1487
+#: gschem/lib/system-gschemrc.scm:1488
msgid "_Net"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1488
+#: gschem/lib/system-gschemrc.scm:1489
msgid "B_us"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1489
+#: gschem/lib/system-gschemrc.scm:1490
msgid "_Attribute..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1490
+#: gschem/lib/system-gschemrc.scm:1491
msgid "_Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1492
+#: gschem/lib/system-gschemrc.scm:1493
msgid "_Line"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1493
+#: gschem/lib/system-gschemrc.scm:1494
msgid "_Box"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1494
+#: gschem/lib/system-gschemrc.scm:1495
msgid "C_ircle"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1495
+#: gschem/lib/system-gschemrc.scm:1496
msgid "A_rc"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1496
+#: gschem/lib/system-gschemrc.scm:1497
msgid "_Pin"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1497
+#: gschem/lib/system-gschemrc.scm:1498
msgid "Pictu_re..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1503
+#: gschem/lib/system-gschemrc.scm:1504
msgid "_Down Schematic"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1504
+#: gschem/lib/system-gschemrc.scm:1505
msgid "Down _Symbol"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1505
+#: gschem/lib/system-gschemrc.scm:1506
msgid "_Up"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1506
+#: gschem/lib/system-gschemrc.scm:1507
msgid "D_ocumentation..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1512
+#: gschem/lib/system-gschemrc.scm:1513
msgid "_Attach"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1513
+#: gschem/lib/system-gschemrc.scm:1514
msgid "_Detach"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1514
+#: gschem/lib/system-gschemrc.scm:1515
msgid "Show _Value"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1515
+#: gschem/lib/system-gschemrc.scm:1516
msgid "Show _Name"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1516
+#: gschem/lib/system-gschemrc.scm:1517
msgid "Show _Both"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1517
+#: gschem/lib/system-gschemrc.scm:1518
msgid "_Toggle Visibility"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1519
+#: gschem/lib/system-gschemrc.scm:1520
msgid "_Find Specific Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1520
+#: gschem/lib/system-gschemrc.scm:1521
msgid "_Hide Specific Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1521
+#: gschem/lib/system-gschemrc.scm:1522
msgid "_Show Specific Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1522
+#: gschem/lib/system-gschemrc.scm:1523
msgid "A_utonumber Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1528
+#: gschem/lib/system-gschemrc.scm:1529
msgid "_Text Size..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1529
+#: gschem/lib/system-gschemrc.scm:1530
msgid "Cycle _grid styles"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1530
+#: gschem/lib/system-gschemrc.scm:1531
msgid "Toggle _Snap On/Off"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1531
+#: gschem/lib/system-gschemrc.scm:1532
msgid "Snap Grid S_pacing..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1532
+#: gschem/lib/system-gschemrc.scm:1533
msgid "Scale _up Grid Spacing"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1534
+#: gschem/lib/system-gschemrc.scm:1535
msgid "Scale _down Grid Spacing"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1536
+#: gschem/lib/system-gschemrc.scm:1537
msgid "Toggle _Outline/Box"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1538
+#: gschem/lib/system-gschemrc.scm:1539
msgid "Toggle Net _Rubberband"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1539
+#: gschem/lib/system-gschemrc.scm:1540
msgid "Toggle _Magnetic Net"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1540
+#: gschem/lib/system-gschemrc.scm:1541
msgid "Show _Log Window..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1542
+#: gschem/lib/system-gschemrc.scm:1543
msgid "Show _Coord Window..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1558
+#: gschem/lib/system-gschemrc.scm:1559
msgid "gEDA Docu_mentation..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1559
+#: gschem/lib/system-gschemrc.scm:1560
msgid "gschem _FAQ..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1560
+#: gschem/lib/system-gschemrc.scm:1561
msgid "gEDA _Wiki..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1561
+#: gschem/lib/system-gschemrc.scm:1562
msgid "Component D_ocumentation..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1563
+#: gschem/lib/system-gschemrc.scm:1564
msgid "_Hotkeys..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1564
+#: gschem/lib/system-gschemrc.scm:1565
msgid "_About..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1570
+#: gschem/lib/system-gschemrc.scm:1571
msgid "_File"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1571
+#: gschem/lib/system-gschemrc.scm:1572
msgid "_Edit"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1572
+#: gschem/lib/system-gschemrc.scm:1573
msgid "_Buffer"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1573
+#: gschem/lib/system-gschemrc.scm:1574
msgid "_View"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1574
+#: gschem/lib/system-gschemrc.scm:1575
msgid "_Page"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1575
+#: gschem/lib/system-gschemrc.scm:1576
msgid "_Add"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1576
+#: gschem/lib/system-gschemrc.scm:1577
msgid "Hie_rarchy"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1577
+#: gschem/lib/system-gschemrc.scm:1578
msgid "A_ttributes"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1578
+#: gschem/lib/system-gschemrc.scm:1579
msgid "_Options"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1579
+#: gschem/lib/system-gschemrc.scm:1580
msgid "_Help"
msgstr ""
+#~ msgid "Make Inv Text Vis"
+#~ msgstr "Make Inv Text Vis"
+
#~ msgid "File"
#~ msgstr "File"
diff --git a/gschem/po/fr.po b/gschem/po/fr.po
index 5466d5b..95e0b48 100644
--- a/gschem/po/fr.po
+++ b/gschem/po/fr.po
@@ -10,7 +10,7 @@ msgid ""
msgstr ""
"Project-Id-Version: fr_FR\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2010-11-07 13:37+0000\n"
+"POT-Creation-Date: 2011-01-16 00:11-0500\n"
"PO-Revision-Date: 2010-02-14 01:03+0000\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -25,17 +25,17 @@ msgstr ""
msgid "Zoom too small! Cannot zoom further.\n"
msgstr "Agrandissement maximum ! Impossible d'agrandir plus.\n"
-#: gschem/src/g_funcs.c:339 gschem/src/i_callbacks.c:68
+#: gschem/src/g_funcs.c:347 gschem/src/i_callbacks.c:68
#, c-format
msgid "Could not fork\n"
msgstr "Impossible de créer un processus fils\n"
-#: gschem/src/g_funcs.c:355 gschem/src/i_callbacks.c:78
+#: gschem/src/g_funcs.c:363 gschem/src/i_callbacks.c:78
#, c-format
msgid "Could not invoke %s\n"
msgstr "Impossible de lancer %s\n"
-#: gschem/src/g_funcs.c:361 gschem/src/i_callbacks.c:82
+#: gschem/src/g_funcs.c:369 gschem/src/i_callbacks.c:82
msgid "Documentation commands not supported under MinGW.\n"
msgstr "Commandes de documentation non supportées sous MinGW.\n"
@@ -125,25 +125,25 @@ msgstr "Gain [%d] invalide passé à zoom-gain\n"
msgid "Invalid number of steps [%d] scrollpan-steps\n"
msgstr "Nombre d'étapes [%d] scrollpan-steps invalide\n"
-#: gschem/src/gschem.c:184
+#: gschem/src/gschem.c:188
#, c-format
msgid "gEDA/gschem version %s%s.%s\n"
msgstr "gEDA/gschem version %s%s.%s\n"
-#: gschem/src/gschem.c:187
+#: gschem/src/gschem.c:191
msgid ""
"gEDA/gschem comes with ABSOLUTELY NO WARRANTY; see COPYING for more "
"details.\n"
msgstr "gEDA/gschem n'est accompagné d'ABSOLUMENT AUCUNE GARANTIE.\n"
-#: gschem/src/gschem.c:189
+#: gschem/src/gschem.c:193
msgid ""
"This is free software, and you are welcome to redistribute it under certain\n"
msgstr ""
"Ceci est un logiciel libre et vous êtes invité à le redistribuer en "
"respectant\n"
-#: gschem/src/gschem.c:191
+#: gschem/src/gschem.c:195
msgid ""
"conditions; please see the COPYING file for more details.\n"
"\n"
@@ -152,17 +152,17 @@ msgstr ""
"COPYING.\n"
"\n"
-#: gschem/src/gschem.c:194
+#: gschem/src/gschem.c:198
#, c-format
msgid "This is the MINGW32 port.\n"
msgstr "Ceci est le portage sous MINGW32\n"
-#: gschem/src/gschem.c:198
+#: gschem/src/gschem.c:202
#, c-format
msgid "Current locale settings: %s\n"
msgstr "Locale en cours : %s\n"
-#: gschem/src/gschem.c:213
+#: gschem/src/gschem.c:218
msgid ""
"You must set the GEDADATA environment variable!\n"
"\n"
@@ -170,31 +170,21 @@ msgid ""
"environment variable to point to the correct location.\n"
msgstr "Vous devez positionner la variable d'environnement GEDADATA!\n"
-#: gschem/src/gschem.c:248
+#: gschem/src/gschem.c:256
#, c-format
msgid "Couldn't find init scm file [%s]\n"
msgstr "Impossible de trouver le fichier scm d'init [%s]\n"
-#: gschem/src/gschem.c:252
+#: gschem/src/gschem.c:260
#, c-format
msgid "Read init scm file [%s]\n"
msgstr "Lecture du fichier scm de démarrage [%s]\n"
-#: gschem/src/gschem.c:256
+#: gschem/src/gschem.c:264
#, c-format
msgid "Failed to read init scm file [%s]\n"
msgstr "�chec de la lecture du fichier scm de démarrage [%s]\n"
-#: gschem/src/gschem.c:317
-#, c-format
-msgid "Scheme directory NOT set!\n"
-msgstr "Répertoire Scheme NON initialisé !\n"
-
-#: gschem/src/gschem.c:324 gschem/src/x_script.c:66
-#, c-format
-msgid "Executing guile script [%s]\n"
-msgstr "Exécution du script guile [%s]\n"
-
#: gschem/src/gschem_cairo.c:310
#, c-format
msgid "Unknown end for line (%d)\n"
@@ -218,11 +208,11 @@ msgstr "Mode Composant"
msgid "Text Mode"
msgstr "Mode Texte"
-#: gschem/src/i_basic.c:84 gschem/lib/system-gschemrc.scm:1409
+#: gschem/src/i_basic.c:84 gschem/lib/system-gschemrc.scm:1411
msgid "Copy Mode"
msgstr "Mode Copie"
-#: gschem/src/i_basic.c:87 gschem/lib/system-gschemrc.scm:1411
+#: gschem/src/i_basic.c:87 gschem/lib/system-gschemrc.scm:1413
msgid "Move Mode"
msgstr "Mode Déplacement"
@@ -230,7 +220,7 @@ msgstr "Mode Déplacement"
msgid "Rotate Mode"
msgstr "Mode Rotation"
-#: gschem/src/i_basic.c:91 gschem/lib/system-gschemrc.scm:1413
+#: gschem/src/i_basic.c:91 gschem/lib/system-gschemrc.scm:1415
msgid "Mirror Mode"
msgstr "Mode Miroir"
@@ -283,22 +273,22 @@ msgstr "Mode Arc"
msgid "Pin Mode"
msgstr "Mode Broche"
-#: gschem/src/i_basic.c:135 gschem/src/i_callbacks.c:544
-#: gschem/src/i_callbacks.c:568
+#: gschem/src/i_basic.c:135 gschem/src/i_callbacks.c:576
+#: gschem/src/i_callbacks.c:600
msgid "Copy"
msgstr "Copier"
-#: gschem/src/i_basic.c:137 gschem/src/i_callbacks.c:634
-#: gschem/src/i_callbacks.c:658
+#: gschem/src/i_basic.c:137 gschem/src/i_callbacks.c:666
+#: gschem/src/i_callbacks.c:690
msgid "Move"
msgstr "Déplacer"
-#: gschem/src/i_basic.c:139 gschem/src/i_callbacks.c:589
-#: gschem/src/i_callbacks.c:613
+#: gschem/src/i_basic.c:139 gschem/src/i_callbacks.c:621
+#: gschem/src/i_callbacks.c:645
msgid "Multiple Copy"
msgstr "Copie Multiple"
-#: gschem/src/i_basic.c:142 gschem/lib/system-gschemrc.scm:1410
+#: gschem/src/i_basic.c:142 gschem/lib/system-gschemrc.scm:1412
msgid "Multiple Copy Mode"
msgstr "Mode Copie Multiple"
@@ -318,7 +308,7 @@ msgstr ""
msgid "Action"
msgstr "Action"
-#: gschem/src/i_basic.c:260 gschem/src/x_dialog.c:2312
+#: gschem/src/i_basic.c:260 gschem/src/x_dialog.c:2316
#: gschem/src/x_window.c:491
msgid "Stroke"
msgstr ""
@@ -349,7 +339,7 @@ msgstr "Grille(%s,%s)"
msgid "Documentation for [%s,%s,%s,%s]\n"
msgstr "Documentation pour [%s,%s,%s,%s]\n"
-#: gschem/src/i_callbacks.c:123 gschem/src/i_callbacks.c:1699
+#: gschem/src/i_callbacks.c:123 gschem/src/i_callbacks.c:1706
#, c-format
msgid "New page created [%s]\n"
msgstr "Nouvelle page [%s] créée\n"
@@ -371,69 +361,69 @@ msgstr "Toutes les pages enregistrées"
msgid "Closing Window\n"
msgstr "Fermeture de la fenêtre\n"
-#: gschem/src/i_callbacks.c:549 gschem/src/i_callbacks.c:594
-#: gschem/src/i_callbacks.c:639
+#: gschem/src/i_callbacks.c:581 gschem/src/i_callbacks.c:626
+#: gschem/src/i_callbacks.c:671
msgid "Select objs first"
msgstr "Sélectionnez d'abord des objets"
-#: gschem/src/i_callbacks.c:678 gschem/src/x_multiattrib.c:1491
+#: gschem/src/i_callbacks.c:710 gschem/src/x_multiattrib.c:1503
msgid "Delete"
msgstr "Supprimer"
-#: gschem/src/i_callbacks.c:703
+#: gschem/src/i_callbacks.c:735
msgid "Edit"
msgstr "Ã?dition"
-#: gschem/src/i_callbacks.c:718
+#: gschem/src/i_callbacks.c:750
msgid "Edit pin type"
msgstr "Ã?dition du type de broche"
-#: gschem/src/i_callbacks.c:737
+#: gschem/src/i_callbacks.c:769
msgid "Edit Text"
msgstr "Ã?diter le texte"
-#: gschem/src/i_callbacks.c:760
+#: gschem/src/i_callbacks.c:792
msgid "Slot"
msgstr "Slot"
-#: gschem/src/i_callbacks.c:777
+#: gschem/src/i_callbacks.c:809
msgid "Color"
msgstr "Couleur"
-#: gschem/src/i_callbacks.c:814 gschem/src/i_callbacks.c:859
+#: gschem/src/i_callbacks.c:846 gschem/src/i_callbacks.c:891
msgid "Rotate"
msgstr "Pivoter"
-#: gschem/src/i_callbacks.c:882 gschem/src/i_callbacks.c:907
+#: gschem/src/i_callbacks.c:913 gschem/src/i_callbacks.c:938
msgid "Mirror"
msgstr "Miroir"
-#: gschem/src/i_callbacks.c:928 gschem/src/x_dialog.c:2315
-#: gschem/lib/system-gschemrc.scm:1422
+#: gschem/src/i_callbacks.c:959 gschem/src/x_dialog.c:2319
+#: gschem/lib/system-gschemrc.scm:1424
msgid "Lock"
msgstr "Verrouiller"
-#: gschem/src/i_callbacks.c:946 gschem/lib/system-gschemrc.scm:1423
+#: gschem/src/i_callbacks.c:977 gschem/lib/system-gschemrc.scm:1425
msgid "Unlock"
msgstr "Déverrouiller"
-#: gschem/src/i_callbacks.c:964 gschem/src/x_dialog.c:1734
+#: gschem/src/i_callbacks.c:995 gschem/src/x_dialog.c:1737
msgid "Translate"
msgstr "Translater"
-#: gschem/src/i_callbacks.c:967
+#: gschem/src/i_callbacks.c:998
msgid "WARNING: Do not translate with snap off!\n"
msgstr "ATTENTION : ne translatez pas quand le snap est désactivé !\n"
-#: gschem/src/i_callbacks.c:968
+#: gschem/src/i_callbacks.c:999
msgid "WARNING: Turning snap on and continuing with translate.\n"
msgstr "ATTENTION : activation du snap et poursuite de la translation.\n"
-#: gschem/src/i_callbacks.c:975
+#: gschem/src/i_callbacks.c:1006
msgid "WARNING: Snap grid size is not equal to 100!\n"
msgstr "ATTENTION : la taille du snap sur la grille n'est pas égale à 100 !\n"
-#: gschem/src/i_callbacks.c:977
+#: gschem/src/i_callbacks.c:1008
msgid ""
"WARNING: If you are translating a symbol to the origin, the snap grid size "
"should be set to 100\n"
@@ -441,176 +431,172 @@ msgstr ""
"ATTENTION : si vous déplacez un symbole à l'origine, la taille de snap de la "
"grille devrait être de 100 !\n"
-#: gschem/src/i_callbacks.c:1008
+#: gschem/src/i_callbacks.c:1039
msgid "Embed"
msgstr "Embarquer"
-#: gschem/src/i_callbacks.c:1047
+#: gschem/src/i_callbacks.c:1078
msgid "Unembed"
msgstr "Débarquer"
-#: gschem/src/i_callbacks.c:1089
+#: gschem/src/i_callbacks.c:1120
msgid "Update"
msgstr "Mettre à jour"
-#: gschem/src/i_callbacks.c:1136
+#: gschem/src/i_callbacks.c:1167
msgid "ShowHidden"
msgstr "AfficheCaché"
-#: gschem/src/i_callbacks.c:1160
-msgid "MakeVisible"
-msgstr "RendVisible"
-
-#: gschem/src/i_callbacks.c:1466 gschem/src/i_callbacks.c:1538
+#: gschem/src/i_callbacks.c:1473 gschem/src/i_callbacks.c:1545
msgid "Pan"
msgstr "Panoramique"
-#: gschem/src/i_callbacks.c:1743
+#: gschem/src/i_callbacks.c:1750
msgid "Really revert page?"
msgstr "Abandonner les modifications ?"
-#: gschem/src/i_callbacks.c:1813
+#: gschem/src/i_callbacks.c:1820
msgid "Copy to clipboard"
msgstr "Copier vers le presse-papier"
-#: gschem/src/i_callbacks.c:1831
+#: gschem/src/i_callbacks.c:1838
msgid "Cut to clipboard"
msgstr "Coupe la sélection dans le presse-papier"
-#: gschem/src/i_callbacks.c:1849
+#: gschem/src/i_callbacks.c:1856
msgid "Paste from clipboard"
msgstr "Coller depuis le presse-papiers"
-#: gschem/src/i_callbacks.c:1861 gschem/src/i_callbacks.c:2100
-#: gschem/src/i_callbacks.c:2122 gschem/src/i_callbacks.c:2144
-#: gschem/src/i_callbacks.c:2166 gschem/src/i_callbacks.c:2188
+#: gschem/src/i_callbacks.c:1868 gschem/src/i_callbacks.c:2107
+#: gschem/src/i_callbacks.c:2129 gschem/src/i_callbacks.c:2151
+#: gschem/src/i_callbacks.c:2173 gschem/src/i_callbacks.c:2195
msgid "Empty buffer"
msgstr "Tampon vide"
-#: gschem/src/i_callbacks.c:1906
+#: gschem/src/i_callbacks.c:1913
msgid "Copy 1"
msgstr "Copier 1"
-#: gschem/src/i_callbacks.c:1925
+#: gschem/src/i_callbacks.c:1932
msgid "Copy 2"
msgstr "Copier 2"
-#: gschem/src/i_callbacks.c:1944
+#: gschem/src/i_callbacks.c:1951
msgid "Copy 3"
msgstr "Copier 3"
-#: gschem/src/i_callbacks.c:1963
+#: gschem/src/i_callbacks.c:1970
msgid "Copy 4"
msgstr "Copier 4"
-#: gschem/src/i_callbacks.c:1982
+#: gschem/src/i_callbacks.c:1989
msgid "Copy 5"
msgstr "Copier 5"
-#: gschem/src/i_callbacks.c:2001
+#: gschem/src/i_callbacks.c:2008
msgid "Cut 1"
msgstr "Couper 1"
-#: gschem/src/i_callbacks.c:2020
+#: gschem/src/i_callbacks.c:2027
msgid "Cut 2"
msgstr "Couper 2"
-#: gschem/src/i_callbacks.c:2039
+#: gschem/src/i_callbacks.c:2046
msgid "Cut 3"
msgstr "Couper 3"
-#: gschem/src/i_callbacks.c:2058
+#: gschem/src/i_callbacks.c:2065
msgid "Cut 4"
msgstr "Couper 4"
-#: gschem/src/i_callbacks.c:2077
+#: gschem/src/i_callbacks.c:2084
msgid "Cut 5"
msgstr "Couper 5"
-#: gschem/src/i_callbacks.c:2093
+#: gschem/src/i_callbacks.c:2100
msgid "Paste 1"
msgstr "Coller 1"
-#: gschem/src/i_callbacks.c:2115
+#: gschem/src/i_callbacks.c:2122
msgid "Paste 2"
msgstr "Coller 2"
-#: gschem/src/i_callbacks.c:2137
+#: gschem/src/i_callbacks.c:2144
msgid "Paste 3"
msgstr "Coller 3"
-#: gschem/src/i_callbacks.c:2159
+#: gschem/src/i_callbacks.c:2166
msgid "Paste 4"
msgstr "Coller 4"
-#: gschem/src/i_callbacks.c:2181
+#: gschem/src/i_callbacks.c:2188
msgid "Paste 5"
msgstr "Coller 5"
-#: gschem/src/i_callbacks.c:2318 gschem/src/x_window.c:355
+#: gschem/src/i_callbacks.c:2325 gschem/src/x_window.c:355
msgid "Component"
msgstr "Composant"
-#: gschem/src/i_callbacks.c:2354 gschem/src/i_callbacks.c:2373
-#: gschem/src/x_dialog.c:2285
+#: gschem/src/i_callbacks.c:2361 gschem/src/i_callbacks.c:2380
+#: gschem/src/x_dialog.c:2289
msgid "Attribute"
msgstr "Attribut"
-#: gschem/src/i_callbacks.c:2395 gschem/src/i_callbacks.c:2422
-#: gschem/src/x_dialog.c:2282
+#: gschem/src/i_callbacks.c:2402 gschem/src/i_callbacks.c:2429
+#: gschem/src/x_dialog.c:2286
msgid "Net"
msgstr "Piste"
-#: gschem/src/i_callbacks.c:2466 gschem/src/i_callbacks.c:2493
-#: gschem/src/x_dialog.c:2300 gschem/src/x_window.c:375
+#: gschem/src/i_callbacks.c:2473 gschem/src/i_callbacks.c:2500
+#: gschem/src/x_dialog.c:2304 gschem/src/x_window.c:375
msgid "Bus"
msgstr "Bus"
-#: gschem/src/i_callbacks.c:2574 gschem/src/i_callbacks.c:2597
+#: gschem/src/i_callbacks.c:2581 gschem/src/i_callbacks.c:2604
msgid "Line"
msgstr "Ligne"
-#: gschem/src/i_callbacks.c:2619 gschem/src/i_callbacks.c:2642
+#: gschem/src/i_callbacks.c:2626 gschem/src/i_callbacks.c:2649
msgid "Box"
msgstr "Boîte"
-#: gschem/src/i_callbacks.c:2698 gschem/src/i_callbacks.c:2722
+#: gschem/src/i_callbacks.c:2705 gschem/src/i_callbacks.c:2729
msgid "Circle"
msgstr "Cercle"
-#: gschem/src/i_callbacks.c:2744 gschem/src/i_callbacks.c:2767
+#: gschem/src/i_callbacks.c:2751 gschem/src/i_callbacks.c:2774
msgid "Arc"
msgstr "Arc"
-#: gschem/src/i_callbacks.c:2789 gschem/src/i_callbacks.c:2812
-#: gschem/src/x_dialog.c:2273
+#: gschem/src/i_callbacks.c:2796 gschem/src/i_callbacks.c:2819
+#: gschem/src/x_dialog.c:2277
msgid "Pin"
msgstr "Broche"
-#: gschem/src/i_callbacks.c:2871
+#: gschem/src/i_callbacks.c:2878
#, c-format
msgid "Searching for source [%s]\n"
msgstr "Recherche de source [%s]\n"
-#: gschem/src/i_callbacks.c:2895
+#: gschem/src/i_callbacks.c:2902
#, c-format
msgid "Cannot find source [%s]\n"
msgstr "Impossible de trouver source [%s]\n"
-#: gschem/src/i_callbacks.c:2964
+#: gschem/src/i_callbacks.c:2965
#, c-format
msgid "Searching for symbol [%s]\n"
msgstr "Recherche du symbole [%s]\n"
-#: gschem/src/i_callbacks.c:2970
+#: gschem/src/i_callbacks.c:2971
msgid "Symbol is not a real file. Symbol cannot be loaded.\n"
msgstr "Le symbole n'est pas un fichier réel. Il ne peut pas être chargé.\n"
-#: gschem/src/i_callbacks.c:3001
+#: gschem/src/i_callbacks.c:3002
msgid "Cannot find any schematics above the current one!\n"
msgstr "Impossible de trouver des schémas au-dessus de celui-ci!\n"
-#: gschem/src/i_callbacks.c:3055
+#: gschem/src/i_callbacks.c:3056
msgid ""
"This command retrieves the component documentation from the web, but there "
"is no component selected"
@@ -618,84 +604,84 @@ msgstr ""
"Cette commande retrouve la documentation du composant depuis le web mais "
"aucun composant n'est sélectionné"
-#: gschem/src/i_callbacks.c:3083
+#: gschem/src/i_callbacks.c:3084
msgid "Attach"
msgstr "Attacher"
-#: gschem/src/i_callbacks.c:3130
+#: gschem/src/i_callbacks.c:3131
msgid "Detach"
msgstr "Détacher"
-#: gschem/src/i_callbacks.c:3165
+#: gschem/src/i_callbacks.c:3166
msgid "ShowN"
msgstr "MontrerN"
-#: gschem/src/i_callbacks.c:3201
+#: gschem/src/i_callbacks.c:3202
msgid "ShowV"
msgstr "MontrerV"
-#: gschem/src/i_callbacks.c:3237
+#: gschem/src/i_callbacks.c:3238
msgid "ShowB"
msgstr "MontrerNV"
-#: gschem/src/i_callbacks.c:3274
+#: gschem/src/i_callbacks.c:3275
msgid "VisToggle"
msgstr ""
-#: gschem/src/i_callbacks.c:3304
+#: gschem/src/i_callbacks.c:3305
#, c-format
msgid "Sorry but this is a non-functioning menu option\n"
msgstr "Désolé mais c'est une option de menu non fonctionnelle\n"
-#: gschem/src/i_callbacks.c:3394
+#: gschem/src/i_callbacks.c:3395
msgid "Action feedback mode set to OUTLINE\n"
msgstr "Mode de retour utilisateur positionné à OUTLINE\n"
-#: gschem/src/i_callbacks.c:3397
+#: gschem/src/i_callbacks.c:3398
msgid "Action feedback mode set to BOUNDINGBOX\n"
msgstr "Mode de retour utilisateur positionné à BOUNDINGBOX\n"
-#: gschem/src/i_callbacks.c:3422
+#: gschem/src/i_callbacks.c:3423
msgid "Grid OFF\n"
msgstr "Grille OFF\n"
-#: gschem/src/i_callbacks.c:3423
+#: gschem/src/i_callbacks.c:3424
msgid "Dot grid selected\n"
msgstr "Grille à points sélectionnée\n"
-#: gschem/src/i_callbacks.c:3424
+#: gschem/src/i_callbacks.c:3425
msgid "Mesh grid selected\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3445
+#: gschem/src/i_callbacks.c:3446
msgid "Snap OFF (CAUTION!)\n"
msgstr "Snap OFF (ATTENTION)\n"
-#: gschem/src/i_callbacks.c:3448
+#: gschem/src/i_callbacks.c:3449
msgid "Snap ON\n"
msgstr "Snap ON\n"
-#: gschem/src/i_callbacks.c:3451
+#: gschem/src/i_callbacks.c:3452
msgid "Snap back to the grid (CAUTION!)\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3477
+#: gschem/src/i_callbacks.c:3478
msgid "Rubber band OFF \n"
msgstr ""
-#: gschem/src/i_callbacks.c:3480
+#: gschem/src/i_callbacks.c:3481
msgid "Rubber band ON\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3495
+#: gschem/src/i_callbacks.c:3496
msgid "magnetic net mode: ON\n"
msgstr "Mode Filet Magnétique : Allumé\n"
-#: gschem/src/i_callbacks.c:3498
+#: gschem/src/i_callbacks.c:3499
msgid "magnetic net mode: OFF\n"
msgstr ""
-#: gschem/src/o_box.c:153
+#: gschem/src/o_box.c:149
#, c-format
msgid "Unknown type for box (fill)!\n"
msgstr "Type de remplissage de boîte inconnu !\n"
@@ -715,17 +701,17 @@ msgstr "o_buffer_cut: Tampon buffer %i invalide\n"
msgid "Got an invalid buffer_number [o_buffer_paste_start]\n"
msgstr "Valeur de buffer_number incorrecte [o_buffer_paste_start]\n"
-#: gschem/src/o_bus.c:118
+#: gschem/src/o_bus.c:117
#, c-format
msgid "Got an invalid which one in o_bus_draw_stretch\n"
msgstr ""
-#: gschem/src/o_circle.c:134
+#: gschem/src/o_circle.c:130
#, c-format
msgid "Unknown type for circle (fill)!\n"
msgstr "Type de remplissage pour cercle inconnu !\n"
-#: gschem/src/o_complex.c:243 gschem/src/o_complex.c:247
+#: gschem/src/o_complex.c:237 gschem/src/o_complex.c:241
#, c-format
msgid "Translating schematic [%d %d]\n"
msgstr "Translation du schéma [%d %d]\n"
@@ -743,41 +729,41 @@ msgstr "Objet déjà verrouillé\n"
msgid "Object already unlocked\n"
msgstr "Objet déjà déverrouillé\n"
-#: gschem/src/o_misc.c:413
+#: gschem/src/o_misc.c:409
msgid "Hidden text is now visible\n"
msgstr "Le texte normalement caché est maintenant visible\n"
-#: gschem/src/o_misc.c:415
+#: gschem/src/o_misc.c:411
msgid "Hidden text is now invisible\n"
msgstr "Le texte normalement caché est maintenant invisible\n"
-#: gschem/src/o_misc.c:668
+#: gschem/src/o_misc.c:636
#, c-format
msgid "Could not find symbol [%s] in library. Update failed.\n"
msgstr ""
"Impossible de trouver le symbole [%s] dans la bibliothèque. �chec de la mise "
"Ã jour.\n"
-#: gschem/src/o_misc.c:783
+#: gschem/src/o_misc.c:751
#, c-format
msgid "o_autosave_backups: Can't get the real filename of %s."
msgstr ""
"o_autosave_backups() : Impossible de récupérer le véritable nom du fichier %s"
-#: gschem/src/o_misc.c:827
+#: gschem/src/o_misc.c:795
#, c-format
msgid "Could NOT set previous backup file [%s] read-write\n"
msgstr ""
"Impossible de passer le fichier copie de sauvegarde [%s] en lecture/"
"écriture\n"
-#: gschem/src/o_misc.c:845
+#: gschem/src/o_misc.c:815
#, c-format
msgid "Could NOT set backup file [%s] readonly\n"
msgstr ""
"Impossible de passer le fichier copie de sauvegarde [%s] en lecture seule\n"
-#: gschem/src/o_misc.c:850
+#: gschem/src/o_misc.c:820
#, c-format
msgid "Could NOT save backup file [%s]\n"
msgstr "�chec lors de la création de la copie de sauvegarde [%s]\n"
@@ -797,39 +783,39 @@ msgstr "Incapable de déterminer le whichone de l'object !\n"
msgid "Got a non line object in o_move_check_endpoint\n"
msgstr "L'objet passé n'est pas une ligne dans o_move_check_endpoint\n"
-#: gschem/src/o_net.c:159
+#: gschem/src/o_net.c:158
#, c-format
msgid "Got an invalid which one in o_net_draw_stretch\n"
msgstr ""
-#: gschem/src/o_net.c:538
+#: gschem/src/o_net.c:537
msgid "Warning: Starting net at off grid coordinate\n"
msgstr ""
"Attention; Démarrage d'une liaison en-dehors des coordonnées de la grille\n"
-#: gschem/src/o_net.c:600
+#: gschem/src/o_net.c:599
msgid "Warning: Ending net at off grid coordinate\n"
msgstr ""
"Attention; Arrêt d'une liaison en-dehors des coordonnées de la grille\n"
-#: gschem/src/o_net.c:932 gschem/src/o_net.c:969 gschem/src/o_net.c:1040
-#: gschem/src/o_net.c:1076
+#: gschem/src/o_net.c:931 gschem/src/o_net.c:968 gschem/src/o_net.c:1039
+#: gschem/src/o_net.c:1075
#, c-format
msgid "Tried to add more than two bus rippers. Internal gschem error.\n"
msgstr ""
"Tentative d'ajout de plus de deux jonctions de bus. Erreur interne gschem.\n"
-#: gschem/src/o_net.c:1144
+#: gschem/src/o_net.c:1143
#, c-format
msgid "Bus ripper symbol [%s] was not found in any component library\n"
msgstr ""
-#: gschem/src/o_path.c:352
+#: gschem/src/o_path.c:348
#, c-format
msgid "Unknown type for path (fill)!\n"
msgstr "Type de chemin inconnu (Ã remplir)!\n"
-#: gschem/src/o_picture.c:163 gschem/src/o_picture.c:539
+#: gschem/src/o_picture.c:163 gschem/src/o_picture.c:537
#, c-format
msgid "Failed to load picture: %s"
msgstr "Ã?chec lors du chargement de l'image : %s"
@@ -838,7 +824,7 @@ msgstr "Ã?chec lors du chargement de l'image : %s"
msgid "Picture"
msgstr "Image"
-#: gschem/src/o_picture.c:447 gschem/src/x_attribedit.c:141
+#: gschem/src/o_picture.c:445 gschem/src/x_attribedit.c:141
#, c-format
msgid "ERROR: NULL object!\n"
msgstr "ERREUR : object==NULL !\n"
@@ -859,34 +845,46 @@ msgstr "Le slotting n'est pas supporté par ce composant\n"
msgid "New slot number out of range\n"
msgstr "Nouvelle valeur de slot hors plage\n"
-#: gschem/src/o_undo.c:304
+#: gschem/src/o_undo.c:303
msgid "Undo/Redo disabled in rc file\n"
msgstr "Opérations Défaire/Refaire désactivées dans fichier rc\n"
-#: gschem/src/parsecmd.c:47
+#: gschem/src/parsecmd.c:81
#, c-format
msgid ""
-"Usage: %s [OPTIONS] schematic_filename1 ... schematic_filenameN\n"
-" -q Quiet mode\n"
-" -v Verbose mode on\n"
-" -r filename Rc filename\n"
-" -s filename Script (guile) filename\n"
-" -o filename Output filename (for printing)\n"
-" -p Automatically place the window\n"
-" -t Print stroke information\n"
-" -h Help; this message\n"
+"Usage: %s [OPTION ...] [--] [FILE ...]\n"
"\n"
-msgstr ""
-"Usage:·%s·[OPTIONS]·schematic_filename1·...·schematic_filenameN\n"
-" -q Mode silencieux\n"
-" -v Activation mode bavard\n"
-" -r filename Nom fichier rc\n"
-" -s filename Nom fichier de script (guile)\n"
-" -o·filename Nom fichier de sortie (pour impression)\n"
-" -p Placement automatique de la fenêtre\n"
-" -t Affichage information stroke\n"
-" -h Aide, affichage de ce message\n"
+"Interactively edit gEDA schematics or symbols. If one or more FILEs\n"
+"are specified, open them for editing; otherwise, create a new, empty\n"
+"schematic.\n"
"\n"
+"Options:\n"
+" -q, --quiet Quiet mode.\n"
+" -v, --verbose Verbose mode.\n"
+" -r, --config-file=FILE Additional configuration file to load.\n"
+" -L DIR Add DIR to Scheme search path.\n"
+" -c EXPR Scheme expression to run at startup.\n"
+" -s FILE Scheme script to run at startup.\n"
+" -o, --output=FILE Output filename (for printing).\n"
+" -p Automatically place the window.\n"
+" -V, --version Show version information.\n"
+" -h, --help Help; this message.\n"
+" -- Treat all remaining arguments as filenames.\n"
+"\n"
+"Report bugs to <geda-bug@xxxxxxxx>\n"
+"gEDA/gaf homepage: <http://gpleda.org>\n"
+msgstr ""
+
+#: gschem/src/parsecmd.c:115
+#, c-format
+msgid ""
+"gEDA %s (g%.7s)\n"
+"Copyright (C) 1998-2011 gEDA developers\n"
+"This is free software, and you are welcome to redistribute it under\n"
+"certain conditions. For details, see the file `COPYING', which is\n"
+"included in the gEDA distribution.\n"
+"There is NO WARRANTY, to the extent permitted by law.\n"
+msgstr ""
#: gschem/src/x_attribedit.c:127
#, c-format
@@ -899,56 +897,56 @@ msgstr ""
msgid "Single Attribute Editor"
msgstr "Ã?diteur d'attribut"
-#: gschem/src/x_attribedit.c:358
+#: gschem/src/x_attribedit.c:359
msgid "<b>Edit Attribute</b>"
msgstr "<b>Ã?diter un attribut</b>"
-#: gschem/src/x_attribedit.c:360
+#: gschem/src/x_attribedit.c:361
msgid "<b>Add Attribute</b>"
msgstr "<b>Ajouter un attribut</b>"
-#: gschem/src/x_attribedit.c:376 gschem/src/x_multiattrib.c:1916
+#: gschem/src/x_attribedit.c:377 gschem/src/x_multiattrib.c:1927
msgid "Name:"
msgstr "Nom :"
-#: gschem/src/x_attribedit.c:393 gschem/src/x_multiattrib.c:1935
+#: gschem/src/x_attribedit.c:394 gschem/src/x_multiattrib.c:1946
msgid "Value:"
msgstr "Valeur :"
-#: gschem/src/x_attribedit.c:409 gschem/src/x_multiattrib.c:1978
+#: gschem/src/x_attribedit.c:410 gschem/src/x_multiattrib.c:1989
msgid "Visible"
msgstr "Visible"
-#: gschem/src/x_attribedit.c:429
+#: gschem/src/x_attribedit.c:430
msgid "Show Value Only"
msgstr "Montrer seulement la valeur"
-#: gschem/src/x_attribedit.c:431
+#: gschem/src/x_attribedit.c:432
msgid "Show Name Only"
msgstr "Montrer seulement le nom"
-#: gschem/src/x_attribedit.c:433 gschem/src/x_multiattrib.c:1454
+#: gschem/src/x_attribedit.c:434 gschem/src/x_multiattrib.c:1466
msgid "Show Name & Value"
msgstr "Montrer le nom et la valeur"
-#: gschem/src/x_attribedit.c:440
+#: gschem/src/x_attribedit.c:441
msgid "<b>Attach Options</b>"
msgstr "<b>Options d'attache</b>"
-#: gschem/src/x_attribedit.c:455
+#: gschem/src/x_attribedit.c:456
msgid "All"
msgstr "Tous"
-#: gschem/src/x_attribedit.c:463 gschem/src/x_compselect.c:896
-#: gschem/src/x_compselect.c:1010
+#: gschem/src/x_attribedit.c:464 gschem/src/x_compselect.c:904
+#: gschem/src/x_compselect.c:1018
msgid "Components"
msgstr "Composants"
-#: gschem/src/x_attribedit.c:471 gschem/src/x_window.c:365
+#: gschem/src/x_attribedit.c:472 gschem/src/x_window.c:365
msgid "Nets"
msgstr "Pistes"
-#: gschem/src/x_attribedit.c:479
+#: gschem/src/x_attribedit.c:480
msgid "Replace existing attributes"
msgstr "Remplacer les attributs existants"
@@ -968,93 +966,93 @@ msgstr ""
"Les slots dupliqués sont susceptibles de créer des problèmes : [symbolname="
"%s, number=%d, slot=%d]\n"
-#: gschem/src/x_autonumber.c:673
+#: gschem/src/x_autonumber.c:675
msgid "No searchstring given in autonumber text.\n"
msgstr "Pas de motif de recherche fourni pour l'annotation automatique.\n"
-#: gschem/src/x_autonumber.c:725
+#: gschem/src/x_autonumber.c:727
msgid "No '*' or '?' given at the end of the autonumber text.\n"
msgstr ""
"Pas de caractère '*' ou '?' à la fin du motif de recherche pour annotation "
"automatique.\n"
-#: gschem/src/x_autonumber.c:860
+#: gschem/src/x_autonumber.c:862
msgid "Diagonal"
msgstr "en diagonal"
-#: gschem/src/x_autonumber.c:861
+#: gschem/src/x_autonumber.c:863
msgid "Top to bottom"
msgstr "de haut en bas"
-#: gschem/src/x_autonumber.c:861
+#: gschem/src/x_autonumber.c:863
msgid "Bottom to top"
msgstr "de bas en haut"
-#: gschem/src/x_autonumber.c:862
+#: gschem/src/x_autonumber.c:864
msgid "Left to right"
msgstr "de gauche à droite"
-#: gschem/src/x_autonumber.c:862
+#: gschem/src/x_autonumber.c:864
msgid "Right to left"
msgstr "de droite à gauche"
-#: gschem/src/x_autonumber.c:863
+#: gschem/src/x_autonumber.c:865
msgid "File order"
msgstr "dans ordre des éléments du fichier"
-#: gschem/src/x_autonumber.c:1199
+#: gschem/src/x_autonumber.c:1201
msgid "Autonumber text"
msgstr "Annotation automatique"
-#: gschem/src/x_autonumber.c:1223
+#: gschem/src/x_autonumber.c:1225
msgid "<b>Scope</b>"
msgstr "<b>Portée</b>"
-#: gschem/src/x_autonumber.c:1245
+#: gschem/src/x_autonumber.c:1247
msgid "Search for:"
msgstr "Motif de recherche :"
-#: gschem/src/x_autonumber.c:1259
+#: gschem/src/x_autonumber.c:1261
msgid "Autonumber text in:"
msgstr "Annoter automatiquement :"
-#: gschem/src/x_autonumber.c:1266
+#: gschem/src/x_autonumber.c:1268
msgid "Skip numbers found in:"
msgstr "Passer les nombres trouvés dans :"
-#: gschem/src/x_autonumber.c:1278 gschem/src/x_autonumber.c:1287
+#: gschem/src/x_autonumber.c:1280 gschem/src/x_autonumber.c:1289
msgid "Selected objects"
msgstr "les objets sélectionnés"
-#: gschem/src/x_autonumber.c:1279 gschem/src/x_autonumber.c:1288
+#: gschem/src/x_autonumber.c:1281 gschem/src/x_autonumber.c:1290
msgid "Current page"
msgstr "la page en cours"
-#: gschem/src/x_autonumber.c:1280 gschem/src/x_autonumber.c:1289
+#: gschem/src/x_autonumber.c:1282 gschem/src/x_autonumber.c:1291
msgid "Whole hierarchy"
msgstr "la hiérarchie complète"
-#: gschem/src/x_autonumber.c:1291
+#: gschem/src/x_autonumber.c:1293
msgid "Overwrite existing numbers"
msgstr "Remplacer les annotations existantes"
-#: gschem/src/x_autonumber.c:1296
+#: gschem/src/x_autonumber.c:1298
msgid "<b>Options</b>"
msgstr "<b>Options</b>"
-#: gschem/src/x_autonumber.c:1318
+#: gschem/src/x_autonumber.c:1320
msgid "Starting number:"
msgstr "Indice de départ :"
-#: gschem/src/x_autonumber.c:1325
+#: gschem/src/x_autonumber.c:1327
msgid "Sort order:"
msgstr "Ordre :"
-#: gschem/src/x_autonumber.c:1346
+#: gschem/src/x_autonumber.c:1348
msgid "Remove numbers"
msgstr "Supprimer les annotations"
-#: gschem/src/x_autonumber.c:1350
+#: gschem/src/x_autonumber.c:1352
msgid "Automatic slotting"
msgstr "Slotting automatique"
@@ -1091,48 +1089,48 @@ msgstr "Tentative d'obtention d'une couleur invalide : %d\n"
msgid "Tried to get an invalid outline color: %d\n"
msgstr "Essai d'un couleur de bordure invalide: %d\n"
-#: gschem/src/x_compselect.c:1040
+#: gschem/src/x_compselect.c:1048
msgid "Filter:"
msgstr "Filtre:"
-#: gschem/src/x_compselect.c:1143 gschem/src/x_dialog.c:3663
-#: gschem/src/x_multiattrib.c:1782
+#: gschem/src/x_compselect.c:1151 gschem/src/x_dialog.c:3667
+#: gschem/src/x_multiattrib.c:1793
msgid "Name"
msgstr "Nom"
-#: gschem/src/x_compselect.c:1152 gschem/src/x_multiattrib.c:1806
+#: gschem/src/x_compselect.c:1160 gschem/src/x_multiattrib.c:1817
msgid "Value"
msgstr "Valeur"
-#: gschem/src/x_compselect.c:1191
+#: gschem/src/x_compselect.c:1199
msgid "Default behavior - reference component"
msgstr "Comportement par défaut - référencer le composant"
-#: gschem/src/x_compselect.c:1194
+#: gschem/src/x_compselect.c:1202
msgid "Embed component in schematic"
msgstr "Embarquer le composant dans le schéma"
-#: gschem/src/x_compselect.c:1197
+#: gschem/src/x_compselect.c:1205
msgid "Include component as individual objects"
msgstr "Ã?clater le composant en objets individuels"
-#: gschem/src/x_compselect.c:1354
+#: gschem/src/x_compselect.c:1362
msgid "Select Component..."
msgstr "Sélecteur de composant..."
-#: gschem/src/x_compselect.c:1377
+#: gschem/src/x_compselect.c:1385
msgid "In Use"
msgstr "En cours d'utilisation"
-#: gschem/src/x_compselect.c:1381
+#: gschem/src/x_compselect.c:1389
msgid "Libraries"
msgstr "Bibliothèques"
-#: gschem/src/x_compselect.c:1390 gschem/src/x_fileselect.c:122
+#: gschem/src/x_compselect.c:1398 gschem/src/x_fileselect.c:122
msgid "Preview"
msgstr "Prévisualisation"
-#: gschem/src/x_compselect.c:1418
+#: gschem/src/x_compselect.c:1426
msgid "Attributes"
msgstr "Attributs"
@@ -1190,139 +1188,139 @@ msgstr "En bas à droite"
msgid "Edit Text Properties"
msgstr "Editer les propriétés du texte"
-#: gschem/src/x_dialog.c:471
+#: gschem/src/x_dialog.c:472
msgid "<b>Text Content</b>"
msgstr "<b>Texte</b>"
-#: gschem/src/x_dialog.c:507
+#: gschem/src/x_dialog.c:508
msgid "<b>Text Properties</b>"
msgstr "<b>Propriétés du texte</b>"
-#: gschem/src/x_dialog.c:522
+#: gschem/src/x_dialog.c:523
msgid "Color:"
msgstr "Couleur :"
-#: gschem/src/x_dialog.c:529
+#: gschem/src/x_dialog.c:530
msgid "Size:"
msgstr "Taille :"
-#: gschem/src/x_dialog.c:538
+#: gschem/src/x_dialog.c:539
msgid "Alignment:"
msgstr "Alignement du texte :"
-#: gschem/src/x_dialog.c:587
+#: gschem/src/x_dialog.c:588
msgid "Solid"
msgstr "Continu"
-#: gschem/src/x_dialog.c:588
+#: gschem/src/x_dialog.c:589
msgid "Dotted"
msgstr "Pointillés"
-#: gschem/src/x_dialog.c:589
+#: gschem/src/x_dialog.c:590
msgid "Dashed"
msgstr "Tirets"
-#: gschem/src/x_dialog.c:590
+#: gschem/src/x_dialog.c:591
msgid "Center"
msgstr "Centré"
-#: gschem/src/x_dialog.c:591
+#: gschem/src/x_dialog.c:592
msgid "Phantom"
msgstr "Fantôme"
-#: gschem/src/x_dialog.c:592 gschem/src/x_dialog.c:689
-#: gschem/src/x_dialog.c:698 gschem/src/x_dialog.c:707
-#: gschem/src/x_dialog.c:808 gschem/src/x_dialog.c:810
-#: gschem/src/x_dialog.c:812 gschem/src/x_dialog.c:1038
-#: gschem/src/x_dialog.c:1141 gschem/src/x_dialog.c:1150
-#: gschem/src/x_dialog.c:1159 gschem/src/x_dialog.c:1168
-#: gschem/src/x_dialog.c:1177 gschem/src/x_dialog.c:1290
-#: gschem/src/x_dialog.c:1292 gschem/src/x_dialog.c:1294
-#: gschem/src/x_dialog.c:1296 gschem/src/x_dialog.c:1298
+#: gschem/src/x_dialog.c:593 gschem/src/x_dialog.c:690
+#: gschem/src/x_dialog.c:699 gschem/src/x_dialog.c:708
+#: gschem/src/x_dialog.c:809 gschem/src/x_dialog.c:811
+#: gschem/src/x_dialog.c:813 gschem/src/x_dialog.c:1039
+#: gschem/src/x_dialog.c:1142 gschem/src/x_dialog.c:1151
+#: gschem/src/x_dialog.c:1160 gschem/src/x_dialog.c:1169
+#: gschem/src/x_dialog.c:1178 gschem/src/x_dialog.c:1291
+#: gschem/src/x_dialog.c:1293 gschem/src/x_dialog.c:1295
+#: gschem/src/x_dialog.c:1297 gschem/src/x_dialog.c:1299
msgid "*unchanged*"
msgstr "*inchangé*"
-#: gschem/src/x_dialog.c:916
+#: gschem/src/x_dialog.c:917
msgid "Edit Line Width & Type"
msgstr "Ã?paisseur et type de ligne"
-#: gschem/src/x_dialog.c:955 gschem/src/x_print.c:307
+#: gschem/src/x_dialog.c:956 gschem/src/x_print.c:307
msgid "Type:"
msgstr "Type :"
-#: gschem/src/x_dialog.c:959
+#: gschem/src/x_dialog.c:960
msgid "Width:"
msgstr "Largeur :"
-#: gschem/src/x_dialog.c:963
+#: gschem/src/x_dialog.c:964
msgid "Dash Length:"
msgstr "Longueur du tiret :"
-#: gschem/src/x_dialog.c:967
+#: gschem/src/x_dialog.c:968
msgid "Dash Space:"
msgstr "Espace entre tirets :"
-#: gschem/src/x_dialog.c:1034
+#: gschem/src/x_dialog.c:1035
msgid "Hollow"
msgstr "Vide"
-#: gschem/src/x_dialog.c:1035
+#: gschem/src/x_dialog.c:1036
msgid "Filled"
msgstr "Plein"
-#: gschem/src/x_dialog.c:1036
+#: gschem/src/x_dialog.c:1037
msgid "Mesh"
msgstr "Quadrillage"
-#: gschem/src/x_dialog.c:1037
+#: gschem/src/x_dialog.c:1038
msgid "Hatch"
msgstr "Rayures"
-#: gschem/src/x_dialog.c:1406
+#: gschem/src/x_dialog.c:1407
msgid "Edit Fill Type"
msgstr "Ã?diter le type de remplissage"
-#: gschem/src/x_dialog.c:1444
+#: gschem/src/x_dialog.c:1446
msgid "Fill Type:"
msgstr "Type de remplissage :"
-#: gschem/src/x_dialog.c:1448
+#: gschem/src/x_dialog.c:1450
msgid "Line Width:"
msgstr "Ã?paisseur :"
-#: gschem/src/x_dialog.c:1452
+#: gschem/src/x_dialog.c:1454
msgid "Angle 1:"
msgstr "Angle1 :"
-#: gschem/src/x_dialog.c:1456
+#: gschem/src/x_dialog.c:1458
msgid "Pitch 1:"
msgstr "Ã?cart1 :"
-#: gschem/src/x_dialog.c:1460
+#: gschem/src/x_dialog.c:1462
msgid "Angle 2:"
msgstr "Angle2 :"
-#: gschem/src/x_dialog.c:1464
+#: gschem/src/x_dialog.c:1466
msgid "Pitch 2:"
msgstr "Ã?cart2 :"
-#: gschem/src/x_dialog.c:1591
+#: gschem/src/x_dialog.c:1593
msgid "Arc Params"
msgstr "Paramètres d'arc"
-#: gschem/src/x_dialog.c:1631
+#: gschem/src/x_dialog.c:1634
msgid "Arc Radius:"
msgstr "Rayon de l'Arc:"
-#: gschem/src/x_dialog.c:1639
+#: gschem/src/x_dialog.c:1642
msgid "Start Angle:"
msgstr "Angle de départ :"
-#: gschem/src/x_dialog.c:1647
+#: gschem/src/x_dialog.c:1650
msgid "Degrees of Sweep:"
msgstr "Balayage :"
-#: gschem/src/x_dialog.c:1764
+#: gschem/src/x_dialog.c:1768
msgid ""
"Offset to translate?\n"
"(0 for origin)"
@@ -1330,186 +1328,186 @@ msgstr ""
"Cible pour translation ?\n"
"(0 pour translation à l'origine)"
-#: gschem/src/x_dialog.c:1832
+#: gschem/src/x_dialog.c:1836
msgid "Text Size"
msgstr "Taille de texte :"
-#: gschem/src/x_dialog.c:1862
+#: gschem/src/x_dialog.c:1866
msgid "Enter new text size:"
msgstr "Entrez la nouvelle taille de texte :"
-#: gschem/src/x_dialog.c:1938
+#: gschem/src/x_dialog.c:1942
msgid "Snap Size"
msgstr "Grille de snap"
-#: gschem/src/x_dialog.c:1968
+#: gschem/src/x_dialog.c:1972
msgid "Enter new snap grid spacing:"
msgstr "Entrez le nouvel espacement de la grille de snap :"
-#: gschem/src/x_dialog.c:2045
+#: gschem/src/x_dialog.c:2049
msgid "Edit slot number"
msgstr "Numéro de slot"
-#: gschem/src/x_dialog.c:2076
+#: gschem/src/x_dialog.c:2080
msgid "Edit slot number:"
msgstr "Numéro de slot :"
-#: gschem/src/x_dialog.c:2117
+#: gschem/src/x_dialog.c:2121
#, c-format
msgid "%s%s (%s)"
msgstr ""
-#: gschem/src/x_dialog.c:2140
+#: gschem/src/x_dialog.c:2144
msgid "About gschem"
msgstr "Ã? propos de gschem"
-#: gschem/src/x_dialog.c:2141
+#: gschem/src/x_dialog.c:2145
msgid "gEDA: GPL Electronic Design Automation"
msgstr ""
-#: gschem/src/x_dialog.c:2142
+#: gschem/src/x_dialog.c:2146
msgid ""
"Copyright © 1998-2009 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
"Copyright © 1998-2009 gEDA Contributors (see ChangeLog for details)"
msgstr ""
-#: gschem/src/x_dialog.c:2201
+#: gschem/src/x_dialog.c:2205
msgid "Coords"
msgstr "Coords"
-#: gschem/src/x_dialog.c:2222
+#: gschem/src/x_dialog.c:2226
msgid "Screen"
msgstr "Ã?cran"
-#: gschem/src/x_dialog.c:2231
+#: gschem/src/x_dialog.c:2235
msgid "World"
msgstr "Monde"
-#: gschem/src/x_dialog.c:2270
+#: gschem/src/x_dialog.c:2274
msgid "Background"
msgstr "Arrière-plan"
-#: gschem/src/x_dialog.c:2276
+#: gschem/src/x_dialog.c:2280
msgid "Net endpoint"
msgstr "Point d'arrêt de la liaison"
-#: gschem/src/x_dialog.c:2279
+#: gschem/src/x_dialog.c:2283
msgid "Graphic"
msgstr "Graphique"
-#: gschem/src/x_dialog.c:2288
+#: gschem/src/x_dialog.c:2292
msgid "Logic bubble"
msgstr "Bulle logique"
-#: gschem/src/x_dialog.c:2291
+#: gschem/src/x_dialog.c:2295
msgid "Grid point"
msgstr "Point de grille"
-#: gschem/src/x_dialog.c:2294
+#: gschem/src/x_dialog.c:2298
msgid "Detached attribute"
msgstr "Attribut détaché"
-#: gschem/src/x_dialog.c:2297 gschem/src/x_window.c:383
+#: gschem/src/x_dialog.c:2301 gschem/src/x_window.c:383
msgid "Text"
msgstr "Texte"
-#: gschem/src/x_dialog.c:2303
+#: gschem/src/x_dialog.c:2307
msgid "Selection"
msgstr "Sélection"
-#: gschem/src/x_dialog.c:2306
+#: gschem/src/x_dialog.c:2310
msgid "Bounding box"
msgstr "Boîte englobante"
-#: gschem/src/x_dialog.c:2309
+#: gschem/src/x_dialog.c:2313
msgid "Zoom box"
msgstr "Boîte d'agrandissement"
-#: gschem/src/x_dialog.c:2318
+#: gschem/src/x_dialog.c:2322
msgid "Output background"
msgstr "Arrière-plan de sortie"
-#: gschem/src/x_dialog.c:2321
+#: gschem/src/x_dialog.c:2325
msgid "Net junction"
msgstr "Jonction de liaison"
-#: gschem/src/x_dialog.c:2324
+#: gschem/src/x_dialog.c:2328
msgid "Mesh grid major"
msgstr ""
-#: gschem/src/x_dialog.c:2327
+#: gschem/src/x_dialog.c:2331
msgid "Mesh grid minor"
msgstr ""
-#: gschem/src/x_dialog.c:2330
+#: gschem/src/x_dialog.c:2334
msgid "Unknown"
msgstr "Inconnu"
-#: gschem/src/x_dialog.c:2481
+#: gschem/src/x_dialog.c:2485
#, c-format
msgid "ERROR: NULL object in color_edit_dialog_apply!\n"
msgstr "ERREUR : object==NULL dans color_edit_dialog_apply !\n"
-#: gschem/src/x_dialog.c:2525
+#: gschem/src/x_dialog.c:2529
msgid "Color Edit"
msgstr "Sélecteur de couleur"
-#: gschem/src/x_dialog.c:2556
+#: gschem/src/x_dialog.c:2560
msgid "Object color:"
msgstr "Couleur de l'objet :"
-#: gschem/src/x_dialog.c:2614
+#: gschem/src/x_dialog.c:2618
msgid "Hotkeys"
msgstr "Raccourcis"
-#: gschem/src/x_dialog.c:2678
+#: gschem/src/x_dialog.c:2682
msgid "Function"
msgstr "Fonction"
-#: gschem/src/x_dialog.c:2685
+#: gschem/src/x_dialog.c:2689
msgid "Keystroke(s)"
msgstr ""
-#: gschem/src/x_dialog.c:2991
+#: gschem/src/x_dialog.c:2995
msgid "Find Text"
msgstr "Recherche de texte"
-#: gschem/src/x_dialog.c:3022
+#: gschem/src/x_dialog.c:3026
msgid "Text to find:"
msgstr "Texte à rechercher :"
-#: gschem/src/x_dialog.c:3032
+#: gschem/src/x_dialog.c:3036
msgid "descend into hierarchy"
msgstr "descendre dans la hiérarchie"
-#: gschem/src/x_dialog.c:3097
+#: gschem/src/x_dialog.c:3101
msgid "Hide Text"
msgstr "Cacher le texte"
-#: gschem/src/x_dialog.c:3128
+#: gschem/src/x_dialog.c:3132
msgid "Hide text starting with:"
msgstr "Cacher le texte commençant par :"
-#: gschem/src/x_dialog.c:3197
+#: gschem/src/x_dialog.c:3201
msgid "Show Text"
msgstr "Montrer le texte"
-#: gschem/src/x_dialog.c:3228
+#: gschem/src/x_dialog.c:3232
msgid "Show text starting with:"
msgstr "Montrer le texte commençant par :"
-#: gschem/src/x_dialog.c:3685
+#: gschem/src/x_dialog.c:3689
msgid "S_elect the schematics you want to save:"
msgstr "_Sélectionnez les schémas que vous souhaitez enregistrer :"
-#: gschem/src/x_dialog.c:3779
+#: gschem/src/x_dialog.c:3784
#, c-format
msgid "Save the changes to schematic \"%s\" before closing?"
msgstr ""
"Voulez-vous enregistrer les modifications dans le schéma \"%s\" avant de le "
"fermer ?"
-#: gschem/src/x_dialog.c:3785
+#: gschem/src/x_dialog.c:3790
#, c-format
msgid ""
"There are %d schematics with unsaved changes. Save changes before closing?"
@@ -1517,17 +1515,17 @@ msgstr ""
"Il y a %d schémas avec des modifications non sauvegardées. Les sauvegarder "
"avant de fermer?"
-#: gschem/src/x_dialog.c:3814
+#: gschem/src/x_dialog.c:3819
msgid "If you don't save, all your changes will be permanently lost."
msgstr ""
"Si vous n'enregistrez pas, les modifications effectuées seront "
"définitivement perdues."
-#: gschem/src/x_dialog.c:3834
+#: gschem/src/x_dialog.c:3839
msgid "_Close without saving"
msgstr "Fermer sans sa_uvegarder"
-#: gschem/src/x_dialog.c:4170
+#: gschem/src/x_dialog.c:4175
#, c-format
msgid ""
"<span weight=\"bold\" size=\"larger\">The input attribute \"%s\" is invalid\n"
@@ -1545,19 +1543,19 @@ msgstr ""
"Le nom ne peut se terminer par un espace.\n"
"La valeur ne peut débuter avec un espace."
-#: gschem/src/x_dialog.c:4172
+#: gschem/src/x_dialog.c:4177
msgid "Invalid Attribute"
msgstr "Attribut invalide"
-#: gschem/src/x_dialog.c:4208
+#: gschem/src/x_dialog.c:4213
msgid "Pin type"
msgstr "Type de broche"
-#: gschem/src/x_dialog.c:4232
+#: gschem/src/x_dialog.c:4237
msgid "Net pin"
msgstr "Broche de liaison"
-#: gschem/src/x_dialog.c:4234
+#: gschem/src/x_dialog.c:4239
msgid "Bus pin (graphical)"
msgstr "Broche de bus (graphique)"
@@ -1662,12 +1660,12 @@ msgstr "Type d'image"
msgid "Write image..."
msgstr "Ã?crire l'image..."
-#: gschem/src/x_log.c:188
+#: gschem/src/x_log.c:209
msgid "** Invalid UTF-8 in log message. See stderr or gschem.log.\n"
msgstr ""
"** UTF-8 invalide dans le message de log. Regardez stderr ou gschem.log.\n"
-#: gschem/src/x_log.c:256
+#: gschem/src/x_log.c:288
msgid "Status"
msgstr "Messages"
@@ -1743,71 +1741,62 @@ msgstr "/Descendre dans le symbole"
msgid "/Up"
msgstr "/Remonter"
-#: gschem/src/x_menus.c:321
+#: gschem/src/x_menus.c:323
#, c-format
msgid "Tried to set the sensitivity on non-existent menu item '%s'\n"
msgstr ""
"Tentative de valider la sensibilité ou un menu inexistant d'un objet '%s'\n"
-#: gschem/src/x_menus.c:345
+#: gschem/src/x_menus.c:347
msgid "Popup_menu_item_factory doesn't exist!\n"
msgstr "Popup_menu_item_factory n'existe pas !\n"
-#: gschem/src/x_menus.c:358
+#: gschem/src/x_menus.c:360
msgid "Tried to set the sensitivity on a non-existent popup menu_item\n"
msgstr ""
"Tentative de rendre sensible un élément de menu contextuel inexistant\n"
-#: gschem/src/x_menus.c:438
-#, c-format
-msgid "Couldn't open file %s\n"
-msgstr "Impossible d'ouvrir le fichier %s\n"
-
-#: gschem/src/x_menus.c:495
-msgid "Clear"
-msgstr "Effacer"
-
-#: gschem/src/x_multiattrib.c:911
+#: gschem/src/x_multiattrib.c:915
msgid "Attributes with empty name are not allowed. Please set a name."
msgstr "Les attributs sans nom sont interdits. Donnez un nom."
-#: gschem/src/x_multiattrib.c:1456
+#: gschem/src/x_multiattrib.c:1468
msgid "Show Value only"
msgstr "Montrer seulement la valeur"
-#: gschem/src/x_multiattrib.c:1458
+#: gschem/src/x_multiattrib.c:1470
msgid "Show Name only"
msgstr "Montrer seulement le nom"
-#: gschem/src/x_multiattrib.c:1486
+#: gschem/src/x_multiattrib.c:1498
msgid "Promote"
msgstr ""
-#: gschem/src/x_multiattrib.c:1490
+#: gschem/src/x_multiattrib.c:1502
msgid "Duplicate"
msgstr "Cloner"
-#: gschem/src/x_multiattrib.c:1708
+#: gschem/src/x_multiattrib.c:1719
msgid "Edit Attributes"
msgstr "Ã?diteur d'attributs"
-#: gschem/src/x_multiattrib.c:1826
+#: gschem/src/x_multiattrib.c:1837
msgid "Vis?"
msgstr "Vis?"
-#: gschem/src/x_multiattrib.c:1844
+#: gschem/src/x_multiattrib.c:1855
msgid "N"
msgstr "N"
-#: gschem/src/x_multiattrib.c:1862
+#: gschem/src/x_multiattrib.c:1873
msgid "V"
msgstr "V"
-#: gschem/src/x_multiattrib.c:1884
+#: gschem/src/x_multiattrib.c:1895
msgid "Show inherited attributes"
msgstr "Montrer les attributs hérités"
-#: gschem/src/x_multiattrib.c:1900
+#: gschem/src/x_multiattrib.c:1911
msgid "Add Attribute"
msgstr "Ajouter un attribut"
@@ -1831,23 +1820,23 @@ msgstr "Fermer la page"
msgid "Discard Page"
msgstr "Abandonner la page"
-#: gschem/src/x_pagesel.c:376
+#: gschem/src/x_pagesel.c:375
msgid "Page Manager"
msgstr "Gestionnaire de pages"
-#: gschem/src/x_pagesel.c:432
+#: gschem/src/x_pagesel.c:431
msgid "Filename"
msgstr "Nom de fichier"
-#: gschem/src/x_pagesel.c:448
+#: gschem/src/x_pagesel.c:447
msgid "Changed"
msgstr "Modifié"
-#: gschem/src/x_pagesel.c:468
+#: gschem/src/x_pagesel.c:467
msgid "Right click on the filename for more options..."
msgstr "Utilisez le clic droit sur le nom de fichier pour plus d'options..."
-#: gschem/src/x_preview.c:234
+#: gschem/src/x_preview.c:233
msgid "Preview Buffer"
msgstr "Prévisualisation du tampon"
@@ -1903,16 +1892,16 @@ msgstr "Fichier :"
msgid "Command:"
msgstr "Commande :"
-#: gschem/src/x_print.c:741
+#: gschem/src/x_print.c:745
msgid "No print destination specified\n"
msgstr "Destination pour l'impression non spécifiée\n"
-#: gschem/src/x_print.c:748
+#: gschem/src/x_print.c:752
#, c-format
msgid "Cannot print current schematic to [%s]\n"
msgstr "Impossible d'imprimer le schéma en cours dans [%s]\n"
-#: gschem/src/x_print.c:757
+#: gschem/src/x_print.c:761
#, c-format
msgid ""
"Error printing to file '%s'\n"
@@ -1921,7 +1910,7 @@ msgstr ""
"Erreur pendant l'impression du fichier '%s'\n"
"Reportez-vous à la fenêtre des messages pour plus de détails"
-#: gschem/src/x_print.c:764
+#: gschem/src/x_print.c:768
#, c-format
msgid "Printed current schematic to [%s]\n"
msgstr "Schéma en cours imprimé dans fichier [%s]\n"
@@ -1930,6 +1919,11 @@ msgstr "Schéma en cours imprimé dans fichier [%s]\n"
msgid "Execute Script..."
msgstr "Exécuter le script..."
+#: gschem/src/x_script.c:66
+#, c-format
+msgid "Executing guile script [%s]\n"
+msgstr "Exécution du script guile [%s]\n"
+
#: gschem/src/x_window.c:81
#, c-format
msgid "Couldn't allocate gc\n"
@@ -2045,35 +2039,35 @@ msgstr "Ã?chec lors du chargement du fichier"
msgid "New file [%s]\n"
msgstr "Nouveau fichier [%s]\n"
-#: gschem/src/x_window.c:857
+#: gschem/src/x_window.c:855
#, c-format
msgid "Could NOT save page [%s]\n"
msgstr "Ã?chec sauvegarde de la page [%s]\n"
-#: gschem/src/x_window.c:858
+#: gschem/src/x_window.c:856
msgid "Error while trying to save"
msgstr "Erreur lors de la tentative de sauvegarde"
-#: gschem/src/x_window.c:867
+#: gschem/src/x_window.c:865
#, c-format
msgid "Saved as [%s]\n"
msgstr "Enregistré sous [%s]\n"
-#: gschem/src/x_window.c:869
+#: gschem/src/x_window.c:867
#, c-format
msgid "Saved [%s]\n"
msgstr "Sauvegarder [%s]\n"
-#: gschem/src/x_window.c:871
+#: gschem/src/x_window.c:869
msgid "Saved"
msgstr "Sauvegarder"
-#: gschem/src/x_window.c:945
+#: gschem/src/x_window.c:943
#, c-format
msgid "Discarding page [%s]\n"
msgstr "Abandonne page [%s]\n"
-#: gschem/src/x_window.c:945
+#: gschem/src/x_window.c:943
#, c-format
msgid "Closing [%s]\n"
msgstr "Ferme [%s]\n"
@@ -2114,7 +2108,7 @@ msgstr ""
msgid "Save All"
msgstr "Enregistrer toutes les pages"
-#: gschem/lib/system-gschemrc.scm:1386 gschem/lib/system-gschemrc.scm:1477
+#: gschem/lib/system-gschemrc.scm:1386 gschem/lib/system-gschemrc.scm:1478
msgid "_Revert"
msgstr ""
@@ -2126,7 +2120,7 @@ msgstr ""
msgid "Write _image..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1393 gschem/lib/system-gschemrc.scm:1478
+#: gschem/lib/system-gschemrc.scm:1393 gschem/lib/system-gschemrc.scm:1479
msgid "_Close"
msgstr ""
@@ -2158,390 +2152,434 @@ msgstr ""
msgid "_Delete"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1412
+#: gschem/lib/system-gschemrc.scm:1409
+#, fuzzy
+msgid "Select All"
+msgstr "Sélectionner"
+
+#: gschem/lib/system-gschemrc.scm:1410
+#, fuzzy
+msgid "Deselect"
+msgstr "Sélectionner"
+
+#: gschem/lib/system-gschemrc.scm:1414
msgid "Rotate 90 Mode"
msgstr "Mode Rotation 90"
-#: gschem/lib/system-gschemrc.scm:1415
+#: gschem/lib/system-gschemrc.scm:1417
msgid "Edit..."
msgstr "Ã?diter"
-#: gschem/lib/system-gschemrc.scm:1416
+#: gschem/lib/system-gschemrc.scm:1418
msgid "Edit Text..."
msgstr "Ã?diter le texte..."
-#: gschem/lib/system-gschemrc.scm:1417
+#: gschem/lib/system-gschemrc.scm:1419
msgid "Slot..."
msgstr "Slot..."
-#: gschem/lib/system-gschemrc.scm:1418
+#: gschem/lib/system-gschemrc.scm:1420
msgid "Color..."
msgstr "Couleur..."
-#: gschem/lib/system-gschemrc.scm:1419
+#: gschem/lib/system-gschemrc.scm:1421
msgid "Line Width & Type..."
msgstr "Ã?paisseur & type de ligne..."
-#: gschem/lib/system-gschemrc.scm:1420
+#: gschem/lib/system-gschemrc.scm:1422
msgid "Fill Type..."
msgstr "Type de remplissage..."
-#: gschem/lib/system-gschemrc.scm:1421
+#: gschem/lib/system-gschemrc.scm:1423
msgid "Symbol Translate..."
msgstr "Translater le symbole..."
-#: gschem/lib/system-gschemrc.scm:1425
+#: gschem/lib/system-gschemrc.scm:1427
msgid "Invoke Macro"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1426
+#: gschem/lib/system-gschemrc.scm:1428
msgid "Embed Component/Picture"
msgstr "Embarquer le composant/l'image"
-#: gschem/lib/system-gschemrc.scm:1427
+#: gschem/lib/system-gschemrc.scm:1429
msgid "Unembed Component/Picture"
msgstr "Débarquer le composant/l'image"
-#: gschem/lib/system-gschemrc.scm:1428
+#: gschem/lib/system-gschemrc.scm:1430
msgid "Update Component"
msgstr "Mise à jour du composant"
-#: gschem/lib/system-gschemrc.scm:1429
+#: gschem/lib/system-gschemrc.scm:1431
msgid "Show/Hide Inv Text"
msgstr "Afficher/Cacher le texte invisible"
-#: gschem/lib/system-gschemrc.scm:1430
-msgid "Make Inv Text Vis"
-msgstr "Rendre le texte invisible visible"
-
-#: gschem/lib/system-gschemrc.scm:1436
+#: gschem/lib/system-gschemrc.scm:1437
msgid "Copy into 1"
msgstr "Copier dans 1"
-#: gschem/lib/system-gschemrc.scm:1437
+#: gschem/lib/system-gschemrc.scm:1438
msgid "Copy into 2"
msgstr "Copier dans 2"
-#: gschem/lib/system-gschemrc.scm:1438
+#: gschem/lib/system-gschemrc.scm:1439
msgid "Copy into 3"
msgstr "Copier dans 3"
-#: gschem/lib/system-gschemrc.scm:1439
+#: gschem/lib/system-gschemrc.scm:1440
msgid "Copy into 4"
msgstr "Copier dans 4"
-#: gschem/lib/system-gschemrc.scm:1440
+#: gschem/lib/system-gschemrc.scm:1441
msgid "Copy into 5"
msgstr "Copier dans 5"
-#: gschem/lib/system-gschemrc.scm:1441
+#: gschem/lib/system-gschemrc.scm:1442
msgid "Cut into 1"
msgstr "Couper dans 1"
-#: gschem/lib/system-gschemrc.scm:1442
+#: gschem/lib/system-gschemrc.scm:1443
msgid "Cut into 2"
msgstr "Couper dans 2"
-#: gschem/lib/system-gschemrc.scm:1443
+#: gschem/lib/system-gschemrc.scm:1444
msgid "Cut into 3"
msgstr "Couper dans 3"
-#: gschem/lib/system-gschemrc.scm:1444
+#: gschem/lib/system-gschemrc.scm:1445
msgid "Cut into 4"
msgstr "Couper dans 4"
-#: gschem/lib/system-gschemrc.scm:1445
+#: gschem/lib/system-gschemrc.scm:1446
msgid "Cut into 5"
msgstr "Couper dans 5"
-#: gschem/lib/system-gschemrc.scm:1446
+#: gschem/lib/system-gschemrc.scm:1447
msgid "Paste from 1"
msgstr "Coller depuis 1"
-#: gschem/lib/system-gschemrc.scm:1447
+#: gschem/lib/system-gschemrc.scm:1448
msgid "Paste from 2"
msgstr "Coller depuis 2"
-#: gschem/lib/system-gschemrc.scm:1448
+#: gschem/lib/system-gschemrc.scm:1449
msgid "Paste from 3"
msgstr "Coller depuis 3"
-#: gschem/lib/system-gschemrc.scm:1449
+#: gschem/lib/system-gschemrc.scm:1450
msgid "Paste from 4"
msgstr "Coller depuis 4"
-#: gschem/lib/system-gschemrc.scm:1450
+#: gschem/lib/system-gschemrc.scm:1451
msgid "Paste from 5"
msgstr "Coller depuis 5"
-#: gschem/lib/system-gschemrc.scm:1456
+#: gschem/lib/system-gschemrc.scm:1457
msgid "_Redraw"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1457
+#: gschem/lib/system-gschemrc.scm:1458
msgid "_Pan"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1458
+#: gschem/lib/system-gschemrc.scm:1459
msgid "Zoom _Box"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1459
+#: gschem/lib/system-gschemrc.scm:1460
msgid "Zoom _Extents"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1460
+#: gschem/lib/system-gschemrc.scm:1461
msgid "Zoom _In"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1461
+#: gschem/lib/system-gschemrc.scm:1462
msgid "Zoom _Out"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1462
+#: gschem/lib/system-gschemrc.scm:1463
msgid "Zoom _Full"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1464
+#: gschem/lib/system-gschemrc.scm:1465
msgid "_Dark color scheme"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1465
+#: gschem/lib/system-gschemrc.scm:1466
msgid "_Light color scheme"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1466
+#: gschem/lib/system-gschemrc.scm:1467
msgid "B_W color scheme"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1473
+#: gschem/lib/system-gschemrc.scm:1474
msgid "_Manager..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1474
+#: gschem/lib/system-gschemrc.scm:1475
msgid "_Previous"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1475
+#: gschem/lib/system-gschemrc.scm:1476
msgid "_Next"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1476
+#: gschem/lib/system-gschemrc.scm:1477
msgid "Ne_w"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1480
+#: gschem/lib/system-gschemrc.scm:1481
msgid "_Discard"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1486
+#: gschem/lib/system-gschemrc.scm:1487
msgid "_Component..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1487
+#: gschem/lib/system-gschemrc.scm:1488
msgid "_Net"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1488
+#: gschem/lib/system-gschemrc.scm:1489
msgid "B_us"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1489
+#: gschem/lib/system-gschemrc.scm:1490
msgid "_Attribute..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1490
+#: gschem/lib/system-gschemrc.scm:1491
msgid "_Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1492
+#: gschem/lib/system-gschemrc.scm:1493
msgid "_Line"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1493
+#: gschem/lib/system-gschemrc.scm:1494
msgid "_Box"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1494
+#: gschem/lib/system-gschemrc.scm:1495
msgid "C_ircle"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1495
+#: gschem/lib/system-gschemrc.scm:1496
msgid "A_rc"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1496
+#: gschem/lib/system-gschemrc.scm:1497
msgid "_Pin"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1497
+#: gschem/lib/system-gschemrc.scm:1498
msgid "Pictu_re..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1503
+#: gschem/lib/system-gschemrc.scm:1504
msgid "_Down Schematic"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1504
+#: gschem/lib/system-gschemrc.scm:1505
msgid "Down _Symbol"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1505
+#: gschem/lib/system-gschemrc.scm:1506
msgid "_Up"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1506
+#: gschem/lib/system-gschemrc.scm:1507
msgid "D_ocumentation..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1512
+#: gschem/lib/system-gschemrc.scm:1513
msgid "_Attach"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1513
+#: gschem/lib/system-gschemrc.scm:1514
msgid "_Detach"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1514
+#: gschem/lib/system-gschemrc.scm:1515
msgid "Show _Value"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1515
+#: gschem/lib/system-gschemrc.scm:1516
msgid "Show _Name"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1516
+#: gschem/lib/system-gschemrc.scm:1517
msgid "Show _Both"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1517
+#: gschem/lib/system-gschemrc.scm:1518
msgid "_Toggle Visibility"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1519
+#: gschem/lib/system-gschemrc.scm:1520
msgid "_Find Specific Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1520
+#: gschem/lib/system-gschemrc.scm:1521
msgid "_Hide Specific Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1521
+#: gschem/lib/system-gschemrc.scm:1522
msgid "_Show Specific Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1522
+#: gschem/lib/system-gschemrc.scm:1523
msgid "A_utonumber Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1528
+#: gschem/lib/system-gschemrc.scm:1529
msgid "_Text Size..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1529
+#: gschem/lib/system-gschemrc.scm:1530
msgid "Cycle _grid styles"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1530
+#: gschem/lib/system-gschemrc.scm:1531
msgid "Toggle _Snap On/Off"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1531
+#: gschem/lib/system-gschemrc.scm:1532
msgid "Snap Grid S_pacing..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1532
+#: gschem/lib/system-gschemrc.scm:1533
msgid "Scale _up Grid Spacing"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1534
+#: gschem/lib/system-gschemrc.scm:1535
msgid "Scale _down Grid Spacing"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1536
+#: gschem/lib/system-gschemrc.scm:1537
msgid "Toggle _Outline/Box"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1538
+#: gschem/lib/system-gschemrc.scm:1539
msgid "Toggle Net _Rubberband"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1539
+#: gschem/lib/system-gschemrc.scm:1540
msgid "Toggle _Magnetic Net"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1540
+#: gschem/lib/system-gschemrc.scm:1541
msgid "Show _Log Window..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1542
+#: gschem/lib/system-gschemrc.scm:1543
msgid "Show _Coord Window..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1558
+#: gschem/lib/system-gschemrc.scm:1559
msgid "gEDA Docu_mentation..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1559
+#: gschem/lib/system-gschemrc.scm:1560
msgid "gschem _FAQ..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1560
+#: gschem/lib/system-gschemrc.scm:1561
msgid "gEDA _Wiki..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1561
+#: gschem/lib/system-gschemrc.scm:1562
msgid "Component D_ocumentation..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1563
+#: gschem/lib/system-gschemrc.scm:1564
msgid "_Hotkeys..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1564
+#: gschem/lib/system-gschemrc.scm:1565
msgid "_About..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1570
+#: gschem/lib/system-gschemrc.scm:1571
msgid "_File"
msgstr "_Fichier"
-#: gschem/lib/system-gschemrc.scm:1571
+#: gschem/lib/system-gschemrc.scm:1572
msgid "_Edit"
msgstr "Ã?dition"
-#: gschem/lib/system-gschemrc.scm:1572
+#: gschem/lib/system-gschemrc.scm:1573
msgid "_Buffer"
msgstr "Tampon"
-#: gschem/lib/system-gschemrc.scm:1573
+#: gschem/lib/system-gschemrc.scm:1574
msgid "_View"
msgstr "Affichage"
-#: gschem/lib/system-gschemrc.scm:1574
+#: gschem/lib/system-gschemrc.scm:1575
msgid "_Page"
msgstr "_Page"
-#: gschem/lib/system-gschemrc.scm:1575
+#: gschem/lib/system-gschemrc.scm:1576
msgid "_Add"
msgstr "_Ajouter"
-#: gschem/lib/system-gschemrc.scm:1576
+#: gschem/lib/system-gschemrc.scm:1577
msgid "Hie_rarchy"
msgstr "Hié_rarchie"
-#: gschem/lib/system-gschemrc.scm:1577
+#: gschem/lib/system-gschemrc.scm:1578
msgid "A_ttributes"
msgstr "A_ttributs"
-#: gschem/lib/system-gschemrc.scm:1578
+#: gschem/lib/system-gschemrc.scm:1579
msgid "_Options"
msgstr "_Options"
-#: gschem/lib/system-gschemrc.scm:1579
+#: gschem/lib/system-gschemrc.scm:1580
msgid "_Help"
msgstr "Aide"
+#~ msgid "Scheme directory NOT set!\n"
+#~ msgstr "Répertoire Scheme NON initialisé !\n"
+
+#~ msgid "MakeVisible"
+#~ msgstr "RendVisible"
+
+#~ msgid ""
+#~ "Usage: %s [OPTIONS] schematic_filename1 ... schematic_filenameN\n"
+#~ " -q Quiet mode\n"
+#~ " -v Verbose mode on\n"
+#~ " -r filename Rc filename\n"
+#~ " -s filename Script (guile) filename\n"
+#~ " -o filename Output filename (for printing)\n"
+#~ " -p Automatically place the window\n"
+#~ " -t Print stroke information\n"
+#~ " -h Help; this message\n"
+#~ "\n"
+#~ msgstr ""
+#~ "Usage:·%s·[OPTIONS]·schematic_filename1·...·schematic_filenameN\n"
+#~ " -q Mode silencieux\n"
+#~ " -v Activation mode bavard\n"
+#~ " -r filename Nom fichier rc\n"
+#~ " -s filename Nom fichier de script (guile)\n"
+#~ " -o·filename Nom fichier de sortie (pour impression)\n"
+#~ " -p Placement automatique de la fenêtre\n"
+#~ " -t Affichage information stroke\n"
+#~ " -h Aide, affichage de ce message\n"
+#~ "\n"
+
+#~ msgid "Couldn't open file %s\n"
+#~ msgstr "Impossible d'ouvrir le fichier %s\n"
+
+#~ msgid "Clear"
+#~ msgstr "Effacer"
+
+#~ msgid "Make Inv Text Vis"
+#~ msgstr "Rendre le texte invisible visible"
+
#~ msgid "Update Cues"
#~ msgstr "Met à jour les extrémités"
diff --git a/gschem/po/he.po b/gschem/po/he.po
index a3e8427..6289517 100644
--- a/gschem/po/he.po
+++ b/gschem/po/he.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2010-11-07 13:37+0000\n"
+"POT-Creation-Date: 2011-01-16 00:11-0500\n"
"PO-Revision-Date: 2010-02-11 03:50+0000\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -22,17 +22,17 @@ msgstr ""
msgid "Zoom too small! Cannot zoom further.\n"
msgstr ""
-#: gschem/src/g_funcs.c:339 gschem/src/i_callbacks.c:68
+#: gschem/src/g_funcs.c:347 gschem/src/i_callbacks.c:68
#, c-format
msgid "Could not fork\n"
msgstr ""
-#: gschem/src/g_funcs.c:355 gschem/src/i_callbacks.c:78
+#: gschem/src/g_funcs.c:363 gschem/src/i_callbacks.c:78
#, c-format
msgid "Could not invoke %s\n"
msgstr ""
-#: gschem/src/g_funcs.c:361 gschem/src/i_callbacks.c:82
+#: gschem/src/g_funcs.c:369 gschem/src/i_callbacks.c:82
msgid "Documentation commands not supported under MinGW.\n"
msgstr ""
@@ -121,39 +121,39 @@ msgstr ""
msgid "Invalid number of steps [%d] scrollpan-steps\n"
msgstr ""
-#: gschem/src/gschem.c:184
+#: gschem/src/gschem.c:188
#, c-format
msgid "gEDA/gschem version %s%s.%s\n"
msgstr ""
-#: gschem/src/gschem.c:187
+#: gschem/src/gschem.c:191
msgid ""
"gEDA/gschem comes with ABSOLUTELY NO WARRANTY; see COPYING for more "
"details.\n"
msgstr ""
-#: gschem/src/gschem.c:189
+#: gschem/src/gschem.c:193
msgid ""
"This is free software, and you are welcome to redistribute it under certain\n"
msgstr ""
-#: gschem/src/gschem.c:191
+#: gschem/src/gschem.c:195
msgid ""
"conditions; please see the COPYING file for more details.\n"
"\n"
msgstr ""
-#: gschem/src/gschem.c:194
+#: gschem/src/gschem.c:198
#, c-format
msgid "This is the MINGW32 port.\n"
msgstr ""
-#: gschem/src/gschem.c:198
+#: gschem/src/gschem.c:202
#, c-format
msgid "Current locale settings: %s\n"
msgstr ""
-#: gschem/src/gschem.c:213
+#: gschem/src/gschem.c:218
msgid ""
"You must set the GEDADATA environment variable!\n"
"\n"
@@ -161,31 +161,21 @@ msgid ""
"environment variable to point to the correct location.\n"
msgstr ""
-#: gschem/src/gschem.c:248
+#: gschem/src/gschem.c:256
#, c-format
msgid "Couldn't find init scm file [%s]\n"
msgstr ""
-#: gschem/src/gschem.c:252
+#: gschem/src/gschem.c:260
#, c-format
msgid "Read init scm file [%s]\n"
msgstr ""
-#: gschem/src/gschem.c:256
+#: gschem/src/gschem.c:264
#, c-format
msgid "Failed to read init scm file [%s]\n"
msgstr ""
-#: gschem/src/gschem.c:317
-#, c-format
-msgid "Scheme directory NOT set!\n"
-msgstr ""
-
-#: gschem/src/gschem.c:324 gschem/src/x_script.c:66
-#, c-format
-msgid "Executing guile script [%s]\n"
-msgstr ""
-
#: gschem/src/gschem_cairo.c:310
#, c-format
msgid "Unknown end for line (%d)\n"
@@ -209,11 +199,11 @@ msgstr ""
msgid "Text Mode"
msgstr ""
-#: gschem/src/i_basic.c:84 gschem/lib/system-gschemrc.scm:1409
+#: gschem/src/i_basic.c:84 gschem/lib/system-gschemrc.scm:1411
msgid "Copy Mode"
msgstr "×?צ×? ×?עתק×?"
-#: gschem/src/i_basic.c:87 gschem/lib/system-gschemrc.scm:1411
+#: gschem/src/i_basic.c:87 gschem/lib/system-gschemrc.scm:1413
msgid "Move Mode"
msgstr "×?צ×? ×?×?×?×?"
@@ -221,7 +211,7 @@ msgstr "×?צ×? ×?×?×?×?"
msgid "Rotate Mode"
msgstr ""
-#: gschem/src/i_basic.c:91 gschem/lib/system-gschemrc.scm:1413
+#: gschem/src/i_basic.c:91 gschem/lib/system-gschemrc.scm:1415
msgid "Mirror Mode"
msgstr "×?צ×? ר×?×?"
@@ -274,22 +264,22 @@ msgstr ""
msgid "Pin Mode"
msgstr ""
-#: gschem/src/i_basic.c:135 gschem/src/i_callbacks.c:544
-#: gschem/src/i_callbacks.c:568
+#: gschem/src/i_basic.c:135 gschem/src/i_callbacks.c:576
+#: gschem/src/i_callbacks.c:600
msgid "Copy"
msgstr ""
-#: gschem/src/i_basic.c:137 gschem/src/i_callbacks.c:634
-#: gschem/src/i_callbacks.c:658
+#: gschem/src/i_basic.c:137 gschem/src/i_callbacks.c:666
+#: gschem/src/i_callbacks.c:690
msgid "Move"
msgstr ""
-#: gschem/src/i_basic.c:139 gschem/src/i_callbacks.c:589
-#: gschem/src/i_callbacks.c:613
+#: gschem/src/i_basic.c:139 gschem/src/i_callbacks.c:621
+#: gschem/src/i_callbacks.c:645
msgid "Multiple Copy"
msgstr ""
-#: gschem/src/i_basic.c:142 gschem/lib/system-gschemrc.scm:1410
+#: gschem/src/i_basic.c:142 gschem/lib/system-gschemrc.scm:1412
msgid "Multiple Copy Mode"
msgstr "×?צ×? ×?עתק×? ×?ר×?×?×?"
@@ -309,7 +299,7 @@ msgstr ""
msgid "Action"
msgstr ""
-#: gschem/src/i_basic.c:260 gschem/src/x_dialog.c:2312
+#: gschem/src/i_basic.c:260 gschem/src/x_dialog.c:2316
#: gschem/src/x_window.c:491
msgid "Stroke"
msgstr ""
@@ -340,7 +330,7 @@ msgstr ""
msgid "Documentation for [%s,%s,%s,%s]\n"
msgstr ""
-#: gschem/src/i_callbacks.c:123 gschem/src/i_callbacks.c:1699
+#: gschem/src/i_callbacks.c:123 gschem/src/i_callbacks.c:1706
#, c-format
msgid "New page created [%s]\n"
msgstr ""
@@ -362,327 +352,323 @@ msgstr ""
msgid "Closing Window\n"
msgstr ""
-#: gschem/src/i_callbacks.c:549 gschem/src/i_callbacks.c:594
-#: gschem/src/i_callbacks.c:639
+#: gschem/src/i_callbacks.c:581 gschem/src/i_callbacks.c:626
+#: gschem/src/i_callbacks.c:671
msgid "Select objs first"
msgstr ""
-#: gschem/src/i_callbacks.c:678 gschem/src/x_multiattrib.c:1491
+#: gschem/src/i_callbacks.c:710 gschem/src/x_multiattrib.c:1503
msgid "Delete"
msgstr "×?×?ק"
-#: gschem/src/i_callbacks.c:703
+#: gschem/src/i_callbacks.c:735
msgid "Edit"
msgstr "ער×?×?×?"
-#: gschem/src/i_callbacks.c:718
+#: gschem/src/i_callbacks.c:750
msgid "Edit pin type"
msgstr ""
-#: gschem/src/i_callbacks.c:737
+#: gschem/src/i_callbacks.c:769
msgid "Edit Text"
msgstr ""
-#: gschem/src/i_callbacks.c:760
+#: gschem/src/i_callbacks.c:792
msgid "Slot"
msgstr ""
-#: gschem/src/i_callbacks.c:777
+#: gschem/src/i_callbacks.c:809
msgid "Color"
msgstr ""
-#: gschem/src/i_callbacks.c:814 gschem/src/i_callbacks.c:859
+#: gschem/src/i_callbacks.c:846 gschem/src/i_callbacks.c:891
msgid "Rotate"
msgstr ""
-#: gschem/src/i_callbacks.c:882 gschem/src/i_callbacks.c:907
+#: gschem/src/i_callbacks.c:913 gschem/src/i_callbacks.c:938
msgid "Mirror"
msgstr ""
-#: gschem/src/i_callbacks.c:928 gschem/src/x_dialog.c:2315
-#: gschem/lib/system-gschemrc.scm:1422
+#: gschem/src/i_callbacks.c:959 gschem/src/x_dialog.c:2319
+#: gschem/lib/system-gschemrc.scm:1424
msgid "Lock"
msgstr "× ×¢×?×?×?"
-#: gschem/src/i_callbacks.c:946 gschem/lib/system-gschemrc.scm:1423
+#: gschem/src/i_callbacks.c:977 gschem/lib/system-gschemrc.scm:1425
msgid "Unlock"
msgstr "ש×?רר × ×¢×?×?×?"
-#: gschem/src/i_callbacks.c:964 gschem/src/x_dialog.c:1734
+#: gschem/src/i_callbacks.c:995 gschem/src/x_dialog.c:1737
msgid "Translate"
msgstr ""
-#: gschem/src/i_callbacks.c:967
+#: gschem/src/i_callbacks.c:998
msgid "WARNING: Do not translate with snap off!\n"
msgstr ""
-#: gschem/src/i_callbacks.c:968
+#: gschem/src/i_callbacks.c:999
msgid "WARNING: Turning snap on and continuing with translate.\n"
msgstr ""
-#: gschem/src/i_callbacks.c:975
+#: gschem/src/i_callbacks.c:1006
msgid "WARNING: Snap grid size is not equal to 100!\n"
msgstr ""
-#: gschem/src/i_callbacks.c:977
+#: gschem/src/i_callbacks.c:1008
msgid ""
"WARNING: If you are translating a symbol to the origin, the snap grid size "
"should be set to 100\n"
msgstr ""
-#: gschem/src/i_callbacks.c:1008
+#: gschem/src/i_callbacks.c:1039
msgid "Embed"
msgstr ""
-#: gschem/src/i_callbacks.c:1047
+#: gschem/src/i_callbacks.c:1078
msgid "Unembed"
msgstr ""
-#: gschem/src/i_callbacks.c:1089
+#: gschem/src/i_callbacks.c:1120
msgid "Update"
msgstr ""
-#: gschem/src/i_callbacks.c:1136
+#: gschem/src/i_callbacks.c:1167
msgid "ShowHidden"
msgstr ""
-#: gschem/src/i_callbacks.c:1160
-msgid "MakeVisible"
-msgstr ""
-
-#: gschem/src/i_callbacks.c:1466 gschem/src/i_callbacks.c:1538
+#: gschem/src/i_callbacks.c:1473 gschem/src/i_callbacks.c:1545
msgid "Pan"
msgstr "×¢×?×?ר"
-#: gschem/src/i_callbacks.c:1743
+#: gschem/src/i_callbacks.c:1750
msgid "Really revert page?"
msgstr ""
-#: gschem/src/i_callbacks.c:1813
+#: gschem/src/i_callbacks.c:1820
msgid "Copy to clipboard"
msgstr ""
-#: gschem/src/i_callbacks.c:1831
+#: gschem/src/i_callbacks.c:1838
msgid "Cut to clipboard"
msgstr ""
-#: gschem/src/i_callbacks.c:1849
+#: gschem/src/i_callbacks.c:1856
msgid "Paste from clipboard"
msgstr ""
-#: gschem/src/i_callbacks.c:1861 gschem/src/i_callbacks.c:2100
-#: gschem/src/i_callbacks.c:2122 gschem/src/i_callbacks.c:2144
-#: gschem/src/i_callbacks.c:2166 gschem/src/i_callbacks.c:2188
+#: gschem/src/i_callbacks.c:1868 gschem/src/i_callbacks.c:2107
+#: gschem/src/i_callbacks.c:2129 gschem/src/i_callbacks.c:2151
+#: gschem/src/i_callbacks.c:2173 gschem/src/i_callbacks.c:2195
msgid "Empty buffer"
msgstr ""
-#: gschem/src/i_callbacks.c:1906
+#: gschem/src/i_callbacks.c:1913
msgid "Copy 1"
msgstr ""
-#: gschem/src/i_callbacks.c:1925
+#: gschem/src/i_callbacks.c:1932
msgid "Copy 2"
msgstr ""
-#: gschem/src/i_callbacks.c:1944
+#: gschem/src/i_callbacks.c:1951
msgid "Copy 3"
msgstr ""
-#: gschem/src/i_callbacks.c:1963
+#: gschem/src/i_callbacks.c:1970
msgid "Copy 4"
msgstr ""
-#: gschem/src/i_callbacks.c:1982
+#: gschem/src/i_callbacks.c:1989
msgid "Copy 5"
msgstr ""
-#: gschem/src/i_callbacks.c:2001
+#: gschem/src/i_callbacks.c:2008
msgid "Cut 1"
msgstr ""
-#: gschem/src/i_callbacks.c:2020
+#: gschem/src/i_callbacks.c:2027
msgid "Cut 2"
msgstr ""
-#: gschem/src/i_callbacks.c:2039
+#: gschem/src/i_callbacks.c:2046
msgid "Cut 3"
msgstr ""
-#: gschem/src/i_callbacks.c:2058
+#: gschem/src/i_callbacks.c:2065
msgid "Cut 4"
msgstr ""
-#: gschem/src/i_callbacks.c:2077
+#: gschem/src/i_callbacks.c:2084
msgid "Cut 5"
msgstr ""
-#: gschem/src/i_callbacks.c:2093
+#: gschem/src/i_callbacks.c:2100
msgid "Paste 1"
msgstr ""
-#: gschem/src/i_callbacks.c:2115
+#: gschem/src/i_callbacks.c:2122
msgid "Paste 2"
msgstr ""
-#: gschem/src/i_callbacks.c:2137
+#: gschem/src/i_callbacks.c:2144
msgid "Paste 3"
msgstr ""
-#: gschem/src/i_callbacks.c:2159
+#: gschem/src/i_callbacks.c:2166
msgid "Paste 4"
msgstr ""
-#: gschem/src/i_callbacks.c:2181
+#: gschem/src/i_callbacks.c:2188
msgid "Paste 5"
msgstr ""
-#: gschem/src/i_callbacks.c:2318 gschem/src/x_window.c:355
+#: gschem/src/i_callbacks.c:2325 gschem/src/x_window.c:355
msgid "Component"
msgstr ""
-#: gschem/src/i_callbacks.c:2354 gschem/src/i_callbacks.c:2373
-#: gschem/src/x_dialog.c:2285
+#: gschem/src/i_callbacks.c:2361 gschem/src/i_callbacks.c:2380
+#: gschem/src/x_dialog.c:2289
msgid "Attribute"
msgstr ""
-#: gschem/src/i_callbacks.c:2395 gschem/src/i_callbacks.c:2422
-#: gschem/src/x_dialog.c:2282
+#: gschem/src/i_callbacks.c:2402 gschem/src/i_callbacks.c:2429
+#: gschem/src/x_dialog.c:2286
msgid "Net"
msgstr "×?×?×?×?ר"
-#: gschem/src/i_callbacks.c:2466 gschem/src/i_callbacks.c:2493
-#: gschem/src/x_dialog.c:2300 gschem/src/x_window.c:375
+#: gschem/src/i_callbacks.c:2473 gschem/src/i_callbacks.c:2500
+#: gschem/src/x_dialog.c:2304 gschem/src/x_window.c:375
msgid "Bus"
msgstr "×?פ×?ק"
-#: gschem/src/i_callbacks.c:2574 gschem/src/i_callbacks.c:2597
+#: gschem/src/i_callbacks.c:2581 gschem/src/i_callbacks.c:2604
msgid "Line"
msgstr "ק×?"
-#: gschem/src/i_callbacks.c:2619 gschem/src/i_callbacks.c:2642
+#: gschem/src/i_callbacks.c:2626 gschem/src/i_callbacks.c:2649
msgid "Box"
msgstr "×?ר×?×?×¢"
-#: gschem/src/i_callbacks.c:2698 gschem/src/i_callbacks.c:2722
+#: gschem/src/i_callbacks.c:2705 gschem/src/i_callbacks.c:2729
msgid "Circle"
msgstr "×?×¢×?×?"
-#: gschem/src/i_callbacks.c:2744 gschem/src/i_callbacks.c:2767
+#: gschem/src/i_callbacks.c:2751 gschem/src/i_callbacks.c:2774
msgid "Arc"
msgstr "קשת"
-#: gschem/src/i_callbacks.c:2789 gschem/src/i_callbacks.c:2812
-#: gschem/src/x_dialog.c:2273
+#: gschem/src/i_callbacks.c:2796 gschem/src/i_callbacks.c:2819
+#: gschem/src/x_dialog.c:2277
msgid "Pin"
msgstr "פ×?×?"
-#: gschem/src/i_callbacks.c:2871
+#: gschem/src/i_callbacks.c:2878
#, c-format
msgid "Searching for source [%s]\n"
msgstr ""
-#: gschem/src/i_callbacks.c:2895
+#: gschem/src/i_callbacks.c:2902
#, c-format
msgid "Cannot find source [%s]\n"
msgstr ""
-#: gschem/src/i_callbacks.c:2964
+#: gschem/src/i_callbacks.c:2965
#, c-format
msgid "Searching for symbol [%s]\n"
msgstr ""
-#: gschem/src/i_callbacks.c:2970
+#: gschem/src/i_callbacks.c:2971
msgid "Symbol is not a real file. Symbol cannot be loaded.\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3001
+#: gschem/src/i_callbacks.c:3002
msgid "Cannot find any schematics above the current one!\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3055
+#: gschem/src/i_callbacks.c:3056
msgid ""
"This command retrieves the component documentation from the web, but there "
"is no component selected"
msgstr ""
-#: gschem/src/i_callbacks.c:3083
+#: gschem/src/i_callbacks.c:3084
msgid "Attach"
msgstr "צרף"
-#: gschem/src/i_callbacks.c:3130
+#: gschem/src/i_callbacks.c:3131
msgid "Detach"
msgstr "× ×ª×§"
-#: gschem/src/i_callbacks.c:3165
+#: gschem/src/i_callbacks.c:3166
msgid "ShowN"
msgstr ""
-#: gschem/src/i_callbacks.c:3201
+#: gschem/src/i_callbacks.c:3202
msgid "ShowV"
msgstr ""
-#: gschem/src/i_callbacks.c:3237
+#: gschem/src/i_callbacks.c:3238
msgid "ShowB"
msgstr ""
-#: gschem/src/i_callbacks.c:3274
+#: gschem/src/i_callbacks.c:3275
msgid "VisToggle"
msgstr ""
-#: gschem/src/i_callbacks.c:3304
+#: gschem/src/i_callbacks.c:3305
#, c-format
msgid "Sorry but this is a non-functioning menu option\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3394
+#: gschem/src/i_callbacks.c:3395
msgid "Action feedback mode set to OUTLINE\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3397
+#: gschem/src/i_callbacks.c:3398
msgid "Action feedback mode set to BOUNDINGBOX\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3422
+#: gschem/src/i_callbacks.c:3423
msgid "Grid OFF\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3423
+#: gschem/src/i_callbacks.c:3424
msgid "Dot grid selected\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3424
+#: gschem/src/i_callbacks.c:3425
msgid "Mesh grid selected\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3445
+#: gschem/src/i_callbacks.c:3446
msgid "Snap OFF (CAUTION!)\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3448
+#: gschem/src/i_callbacks.c:3449
msgid "Snap ON\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3451
+#: gschem/src/i_callbacks.c:3452
msgid "Snap back to the grid (CAUTION!)\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3477
+#: gschem/src/i_callbacks.c:3478
msgid "Rubber band OFF \n"
msgstr ""
-#: gschem/src/i_callbacks.c:3480
+#: gschem/src/i_callbacks.c:3481
msgid "Rubber band ON\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3495
+#: gschem/src/i_callbacks.c:3496
msgid "magnetic net mode: ON\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3498
+#: gschem/src/i_callbacks.c:3499
msgid "magnetic net mode: OFF\n"
msgstr ""
-#: gschem/src/o_box.c:153
+#: gschem/src/o_box.c:149
#, c-format
msgid "Unknown type for box (fill)!\n"
msgstr ""
@@ -702,17 +688,17 @@ msgstr ""
msgid "Got an invalid buffer_number [o_buffer_paste_start]\n"
msgstr ""
-#: gschem/src/o_bus.c:118
+#: gschem/src/o_bus.c:117
#, c-format
msgid "Got an invalid which one in o_bus_draw_stretch\n"
msgstr ""
-#: gschem/src/o_circle.c:134
+#: gschem/src/o_circle.c:130
#, c-format
msgid "Unknown type for circle (fill)!\n"
msgstr ""
-#: gschem/src/o_complex.c:243 gschem/src/o_complex.c:247
+#: gschem/src/o_complex.c:237 gschem/src/o_complex.c:241
#, c-format
msgid "Translating schematic [%d %d]\n"
msgstr ""
@@ -730,35 +716,35 @@ msgstr ""
msgid "Object already unlocked\n"
msgstr ""
-#: gschem/src/o_misc.c:413
+#: gschem/src/o_misc.c:409
msgid "Hidden text is now visible\n"
msgstr ""
-#: gschem/src/o_misc.c:415
+#: gschem/src/o_misc.c:411
msgid "Hidden text is now invisible\n"
msgstr ""
-#: gschem/src/o_misc.c:668
+#: gschem/src/o_misc.c:636
#, c-format
msgid "Could not find symbol [%s] in library. Update failed.\n"
msgstr ""
-#: gschem/src/o_misc.c:783
+#: gschem/src/o_misc.c:751
#, c-format
msgid "o_autosave_backups: Can't get the real filename of %s."
msgstr ""
-#: gschem/src/o_misc.c:827
+#: gschem/src/o_misc.c:795
#, c-format
msgid "Could NOT set previous backup file [%s] read-write\n"
msgstr ""
-#: gschem/src/o_misc.c:845
+#: gschem/src/o_misc.c:815
#, c-format
msgid "Could NOT set backup file [%s] readonly\n"
msgstr ""
-#: gschem/src/o_misc.c:850
+#: gschem/src/o_misc.c:820
#, c-format
msgid "Could NOT save backup file [%s]\n"
msgstr ""
@@ -778,36 +764,36 @@ msgstr ""
msgid "Got a non line object in o_move_check_endpoint\n"
msgstr ""
-#: gschem/src/o_net.c:159
+#: gschem/src/o_net.c:158
#, c-format
msgid "Got an invalid which one in o_net_draw_stretch\n"
msgstr ""
-#: gschem/src/o_net.c:538
+#: gschem/src/o_net.c:537
msgid "Warning: Starting net at off grid coordinate\n"
msgstr ""
-#: gschem/src/o_net.c:600
+#: gschem/src/o_net.c:599
msgid "Warning: Ending net at off grid coordinate\n"
msgstr ""
-#: gschem/src/o_net.c:932 gschem/src/o_net.c:969 gschem/src/o_net.c:1040
-#: gschem/src/o_net.c:1076
+#: gschem/src/o_net.c:931 gschem/src/o_net.c:968 gschem/src/o_net.c:1039
+#: gschem/src/o_net.c:1075
#, c-format
msgid "Tried to add more than two bus rippers. Internal gschem error.\n"
msgstr ""
-#: gschem/src/o_net.c:1144
+#: gschem/src/o_net.c:1143
#, c-format
msgid "Bus ripper symbol [%s] was not found in any component library\n"
msgstr ""
-#: gschem/src/o_path.c:352
+#: gschem/src/o_path.c:348
#, c-format
msgid "Unknown type for path (fill)!\n"
msgstr ""
-#: gschem/src/o_picture.c:163 gschem/src/o_picture.c:539
+#: gschem/src/o_picture.c:163 gschem/src/o_picture.c:537
#, c-format
msgid "Failed to load picture: %s"
msgstr ""
@@ -816,7 +802,7 @@ msgstr ""
msgid "Picture"
msgstr ""
-#: gschem/src/o_picture.c:447 gschem/src/x_attribedit.c:141
+#: gschem/src/o_picture.c:445 gschem/src/x_attribedit.c:141
#, c-format
msgid "ERROR: NULL object!\n"
msgstr ""
@@ -837,23 +823,45 @@ msgstr ""
msgid "New slot number out of range\n"
msgstr ""
-#: gschem/src/o_undo.c:304
+#: gschem/src/o_undo.c:303
msgid "Undo/Redo disabled in rc file\n"
msgstr ""
-#: gschem/src/parsecmd.c:47
+#: gschem/src/parsecmd.c:81
#, c-format
msgid ""
-"Usage: %s [OPTIONS] schematic_filename1 ... schematic_filenameN\n"
-" -q Quiet mode\n"
-" -v Verbose mode on\n"
-" -r filename Rc filename\n"
-" -s filename Script (guile) filename\n"
-" -o filename Output filename (for printing)\n"
-" -p Automatically place the window\n"
-" -t Print stroke information\n"
-" -h Help; this message\n"
+"Usage: %s [OPTION ...] [--] [FILE ...]\n"
+"\n"
+"Interactively edit gEDA schematics or symbols. If one or more FILEs\n"
+"are specified, open them for editing; otherwise, create a new, empty\n"
+"schematic.\n"
+"\n"
+"Options:\n"
+" -q, --quiet Quiet mode.\n"
+" -v, --verbose Verbose mode.\n"
+" -r, --config-file=FILE Additional configuration file to load.\n"
+" -L DIR Add DIR to Scheme search path.\n"
+" -c EXPR Scheme expression to run at startup.\n"
+" -s FILE Scheme script to run at startup.\n"
+" -o, --output=FILE Output filename (for printing).\n"
+" -p Automatically place the window.\n"
+" -V, --version Show version information.\n"
+" -h, --help Help; this message.\n"
+" -- Treat all remaining arguments as filenames.\n"
"\n"
+"Report bugs to <geda-bug@xxxxxxxx>\n"
+"gEDA/gaf homepage: <http://gpleda.org>\n"
+msgstr ""
+
+#: gschem/src/parsecmd.c:115
+#, c-format
+msgid ""
+"gEDA %s (g%.7s)\n"
+"Copyright (C) 1998-2011 gEDA developers\n"
+"This is free software, and you are welcome to redistribute it under\n"
+"certain conditions. For details, see the file `COPYING', which is\n"
+"included in the gEDA distribution.\n"
+"There is NO WARRANTY, to the extent permitted by law.\n"
msgstr ""
#: gschem/src/x_attribedit.c:127
@@ -865,56 +873,56 @@ msgstr ""
msgid "Single Attribute Editor"
msgstr ""
-#: gschem/src/x_attribedit.c:358
+#: gschem/src/x_attribedit.c:359
msgid "<b>Edit Attribute</b>"
msgstr ""
-#: gschem/src/x_attribedit.c:360
+#: gschem/src/x_attribedit.c:361
msgid "<b>Add Attribute</b>"
msgstr ""
-#: gschem/src/x_attribedit.c:376 gschem/src/x_multiattrib.c:1916
+#: gschem/src/x_attribedit.c:377 gschem/src/x_multiattrib.c:1927
msgid "Name:"
msgstr ""
-#: gschem/src/x_attribedit.c:393 gschem/src/x_multiattrib.c:1935
+#: gschem/src/x_attribedit.c:394 gschem/src/x_multiattrib.c:1946
msgid "Value:"
msgstr ""
-#: gschem/src/x_attribedit.c:409 gschem/src/x_multiattrib.c:1978
+#: gschem/src/x_attribedit.c:410 gschem/src/x_multiattrib.c:1989
msgid "Visible"
msgstr ""
-#: gschem/src/x_attribedit.c:429
+#: gschem/src/x_attribedit.c:430
msgid "Show Value Only"
msgstr ""
-#: gschem/src/x_attribedit.c:431
+#: gschem/src/x_attribedit.c:432
msgid "Show Name Only"
msgstr ""
-#: gschem/src/x_attribedit.c:433 gschem/src/x_multiattrib.c:1454
+#: gschem/src/x_attribedit.c:434 gschem/src/x_multiattrib.c:1466
msgid "Show Name & Value"
msgstr ""
-#: gschem/src/x_attribedit.c:440
+#: gschem/src/x_attribedit.c:441
msgid "<b>Attach Options</b>"
msgstr ""
-#: gschem/src/x_attribedit.c:455
+#: gschem/src/x_attribedit.c:456
msgid "All"
msgstr ""
-#: gschem/src/x_attribedit.c:463 gschem/src/x_compselect.c:896
-#: gschem/src/x_compselect.c:1010
+#: gschem/src/x_attribedit.c:464 gschem/src/x_compselect.c:904
+#: gschem/src/x_compselect.c:1018
msgid "Components"
msgstr ""
-#: gschem/src/x_attribedit.c:471 gschem/src/x_window.c:365
+#: gschem/src/x_attribedit.c:472 gschem/src/x_window.c:365
msgid "Nets"
msgstr ""
-#: gschem/src/x_attribedit.c:479
+#: gschem/src/x_attribedit.c:480
msgid "Replace existing attributes"
msgstr ""
@@ -930,91 +938,91 @@ msgid ""
"duplicate slot may cause problems: [symbolname=%s, number=%d, slot=%d]\n"
msgstr ""
-#: gschem/src/x_autonumber.c:673
+#: gschem/src/x_autonumber.c:675
msgid "No searchstring given in autonumber text.\n"
msgstr ""
-#: gschem/src/x_autonumber.c:725
+#: gschem/src/x_autonumber.c:727
msgid "No '*' or '?' given at the end of the autonumber text.\n"
msgstr ""
-#: gschem/src/x_autonumber.c:860
+#: gschem/src/x_autonumber.c:862
msgid "Diagonal"
msgstr ""
-#: gschem/src/x_autonumber.c:861
+#: gschem/src/x_autonumber.c:863
msgid "Top to bottom"
msgstr ""
-#: gschem/src/x_autonumber.c:861
+#: gschem/src/x_autonumber.c:863
msgid "Bottom to top"
msgstr ""
-#: gschem/src/x_autonumber.c:862
+#: gschem/src/x_autonumber.c:864
msgid "Left to right"
msgstr ""
-#: gschem/src/x_autonumber.c:862
+#: gschem/src/x_autonumber.c:864
msgid "Right to left"
msgstr ""
-#: gschem/src/x_autonumber.c:863
+#: gschem/src/x_autonumber.c:865
msgid "File order"
msgstr ""
-#: gschem/src/x_autonumber.c:1199
+#: gschem/src/x_autonumber.c:1201
msgid "Autonumber text"
msgstr ""
-#: gschem/src/x_autonumber.c:1223
+#: gschem/src/x_autonumber.c:1225
msgid "<b>Scope</b>"
msgstr ""
-#: gschem/src/x_autonumber.c:1245
+#: gschem/src/x_autonumber.c:1247
msgid "Search for:"
msgstr ""
-#: gschem/src/x_autonumber.c:1259
+#: gschem/src/x_autonumber.c:1261
msgid "Autonumber text in:"
msgstr ""
-#: gschem/src/x_autonumber.c:1266
+#: gschem/src/x_autonumber.c:1268
msgid "Skip numbers found in:"
msgstr ""
-#: gschem/src/x_autonumber.c:1278 gschem/src/x_autonumber.c:1287
+#: gschem/src/x_autonumber.c:1280 gschem/src/x_autonumber.c:1289
msgid "Selected objects"
msgstr ""
-#: gschem/src/x_autonumber.c:1279 gschem/src/x_autonumber.c:1288
+#: gschem/src/x_autonumber.c:1281 gschem/src/x_autonumber.c:1290
msgid "Current page"
msgstr ""
-#: gschem/src/x_autonumber.c:1280 gschem/src/x_autonumber.c:1289
+#: gschem/src/x_autonumber.c:1282 gschem/src/x_autonumber.c:1291
msgid "Whole hierarchy"
msgstr ""
-#: gschem/src/x_autonumber.c:1291
+#: gschem/src/x_autonumber.c:1293
msgid "Overwrite existing numbers"
msgstr ""
-#: gschem/src/x_autonumber.c:1296
+#: gschem/src/x_autonumber.c:1298
msgid "<b>Options</b>"
msgstr ""
-#: gschem/src/x_autonumber.c:1318
+#: gschem/src/x_autonumber.c:1320
msgid "Starting number:"
msgstr ""
-#: gschem/src/x_autonumber.c:1325
+#: gschem/src/x_autonumber.c:1327
msgid "Sort order:"
msgstr ""
-#: gschem/src/x_autonumber.c:1346
+#: gschem/src/x_autonumber.c:1348
msgid "Remove numbers"
msgstr ""
-#: gschem/src/x_autonumber.c:1350
+#: gschem/src/x_autonumber.c:1352
msgid "Automatic slotting"
msgstr ""
@@ -1051,48 +1059,48 @@ msgstr ""
msgid "Tried to get an invalid outline color: %d\n"
msgstr ""
-#: gschem/src/x_compselect.c:1040
+#: gschem/src/x_compselect.c:1048
msgid "Filter:"
msgstr ""
-#: gschem/src/x_compselect.c:1143 gschem/src/x_dialog.c:3663
-#: gschem/src/x_multiattrib.c:1782
+#: gschem/src/x_compselect.c:1151 gschem/src/x_dialog.c:3667
+#: gschem/src/x_multiattrib.c:1793
msgid "Name"
msgstr ""
-#: gschem/src/x_compselect.c:1152 gschem/src/x_multiattrib.c:1806
+#: gschem/src/x_compselect.c:1160 gschem/src/x_multiattrib.c:1817
msgid "Value"
msgstr ""
-#: gschem/src/x_compselect.c:1191
+#: gschem/src/x_compselect.c:1199
msgid "Default behavior - reference component"
msgstr ""
-#: gschem/src/x_compselect.c:1194
+#: gschem/src/x_compselect.c:1202
msgid "Embed component in schematic"
msgstr ""
-#: gschem/src/x_compselect.c:1197
+#: gschem/src/x_compselect.c:1205
msgid "Include component as individual objects"
msgstr ""
-#: gschem/src/x_compselect.c:1354
+#: gschem/src/x_compselect.c:1362
msgid "Select Component..."
msgstr ""
-#: gschem/src/x_compselect.c:1377
+#: gschem/src/x_compselect.c:1385
msgid "In Use"
msgstr ""
-#: gschem/src/x_compselect.c:1381
+#: gschem/src/x_compselect.c:1389
msgid "Libraries"
msgstr ""
-#: gschem/src/x_compselect.c:1390 gschem/src/x_fileselect.c:122
+#: gschem/src/x_compselect.c:1398 gschem/src/x_fileselect.c:122
msgid "Preview"
msgstr ""
-#: gschem/src/x_compselect.c:1418
+#: gschem/src/x_compselect.c:1426
msgid "Attributes"
msgstr "×?×?פ×?×?× ×?×?"
@@ -1147,336 +1155,336 @@ msgstr ""
msgid "Edit Text Properties"
msgstr ""
-#: gschem/src/x_dialog.c:471
+#: gschem/src/x_dialog.c:472
msgid "<b>Text Content</b>"
msgstr ""
-#: gschem/src/x_dialog.c:507
+#: gschem/src/x_dialog.c:508
msgid "<b>Text Properties</b>"
msgstr ""
-#: gschem/src/x_dialog.c:522
+#: gschem/src/x_dialog.c:523
msgid "Color:"
msgstr ""
-#: gschem/src/x_dialog.c:529
+#: gschem/src/x_dialog.c:530
msgid "Size:"
msgstr ""
-#: gschem/src/x_dialog.c:538
+#: gschem/src/x_dialog.c:539
msgid "Alignment:"
msgstr ""
-#: gschem/src/x_dialog.c:587
+#: gschem/src/x_dialog.c:588
msgid "Solid"
msgstr ""
-#: gschem/src/x_dialog.c:588
+#: gschem/src/x_dialog.c:589
msgid "Dotted"
msgstr ""
-#: gschem/src/x_dialog.c:589
+#: gschem/src/x_dialog.c:590
msgid "Dashed"
msgstr ""
-#: gschem/src/x_dialog.c:590
+#: gschem/src/x_dialog.c:591
msgid "Center"
msgstr ""
-#: gschem/src/x_dialog.c:591
+#: gschem/src/x_dialog.c:592
msgid "Phantom"
msgstr ""
-#: gschem/src/x_dialog.c:592 gschem/src/x_dialog.c:689
-#: gschem/src/x_dialog.c:698 gschem/src/x_dialog.c:707
-#: gschem/src/x_dialog.c:808 gschem/src/x_dialog.c:810
-#: gschem/src/x_dialog.c:812 gschem/src/x_dialog.c:1038
-#: gschem/src/x_dialog.c:1141 gschem/src/x_dialog.c:1150
-#: gschem/src/x_dialog.c:1159 gschem/src/x_dialog.c:1168
-#: gschem/src/x_dialog.c:1177 gschem/src/x_dialog.c:1290
-#: gschem/src/x_dialog.c:1292 gschem/src/x_dialog.c:1294
-#: gschem/src/x_dialog.c:1296 gschem/src/x_dialog.c:1298
+#: gschem/src/x_dialog.c:593 gschem/src/x_dialog.c:690
+#: gschem/src/x_dialog.c:699 gschem/src/x_dialog.c:708
+#: gschem/src/x_dialog.c:809 gschem/src/x_dialog.c:811
+#: gschem/src/x_dialog.c:813 gschem/src/x_dialog.c:1039
+#: gschem/src/x_dialog.c:1142 gschem/src/x_dialog.c:1151
+#: gschem/src/x_dialog.c:1160 gschem/src/x_dialog.c:1169
+#: gschem/src/x_dialog.c:1178 gschem/src/x_dialog.c:1291
+#: gschem/src/x_dialog.c:1293 gschem/src/x_dialog.c:1295
+#: gschem/src/x_dialog.c:1297 gschem/src/x_dialog.c:1299
msgid "*unchanged*"
msgstr ""
-#: gschem/src/x_dialog.c:916
+#: gschem/src/x_dialog.c:917
msgid "Edit Line Width & Type"
msgstr ""
-#: gschem/src/x_dialog.c:955 gschem/src/x_print.c:307
+#: gschem/src/x_dialog.c:956 gschem/src/x_print.c:307
msgid "Type:"
msgstr ""
-#: gschem/src/x_dialog.c:959
+#: gschem/src/x_dialog.c:960
msgid "Width:"
msgstr ""
-#: gschem/src/x_dialog.c:963
+#: gschem/src/x_dialog.c:964
msgid "Dash Length:"
msgstr ""
-#: gschem/src/x_dialog.c:967
+#: gschem/src/x_dialog.c:968
msgid "Dash Space:"
msgstr ""
-#: gschem/src/x_dialog.c:1034
+#: gschem/src/x_dialog.c:1035
msgid "Hollow"
msgstr ""
-#: gschem/src/x_dialog.c:1035
+#: gschem/src/x_dialog.c:1036
msgid "Filled"
msgstr ""
-#: gschem/src/x_dialog.c:1036
+#: gschem/src/x_dialog.c:1037
msgid "Mesh"
msgstr ""
-#: gschem/src/x_dialog.c:1037
+#: gschem/src/x_dialog.c:1038
msgid "Hatch"
msgstr ""
-#: gschem/src/x_dialog.c:1406
+#: gschem/src/x_dialog.c:1407
msgid "Edit Fill Type"
msgstr ""
-#: gschem/src/x_dialog.c:1444
+#: gschem/src/x_dialog.c:1446
msgid "Fill Type:"
msgstr ""
-#: gschem/src/x_dialog.c:1448
+#: gschem/src/x_dialog.c:1450
msgid "Line Width:"
msgstr ""
-#: gschem/src/x_dialog.c:1452
+#: gschem/src/x_dialog.c:1454
msgid "Angle 1:"
msgstr ""
-#: gschem/src/x_dialog.c:1456
+#: gschem/src/x_dialog.c:1458
msgid "Pitch 1:"
msgstr ""
-#: gschem/src/x_dialog.c:1460
+#: gschem/src/x_dialog.c:1462
msgid "Angle 2:"
msgstr ""
-#: gschem/src/x_dialog.c:1464
+#: gschem/src/x_dialog.c:1466
msgid "Pitch 2:"
msgstr ""
-#: gschem/src/x_dialog.c:1591
+#: gschem/src/x_dialog.c:1593
msgid "Arc Params"
msgstr ""
-#: gschem/src/x_dialog.c:1631
+#: gschem/src/x_dialog.c:1634
msgid "Arc Radius:"
msgstr ""
-#: gschem/src/x_dialog.c:1639
+#: gschem/src/x_dialog.c:1642
msgid "Start Angle:"
msgstr ""
-#: gschem/src/x_dialog.c:1647
+#: gschem/src/x_dialog.c:1650
msgid "Degrees of Sweep:"
msgstr ""
-#: gschem/src/x_dialog.c:1764
+#: gschem/src/x_dialog.c:1768
msgid ""
"Offset to translate?\n"
"(0 for origin)"
msgstr ""
-#: gschem/src/x_dialog.c:1832
+#: gschem/src/x_dialog.c:1836
msgid "Text Size"
msgstr ""
-#: gschem/src/x_dialog.c:1862
+#: gschem/src/x_dialog.c:1866
msgid "Enter new text size:"
msgstr ""
-#: gschem/src/x_dialog.c:1938
+#: gschem/src/x_dialog.c:1942
msgid "Snap Size"
msgstr ""
-#: gschem/src/x_dialog.c:1968
+#: gschem/src/x_dialog.c:1972
msgid "Enter new snap grid spacing:"
msgstr ""
-#: gschem/src/x_dialog.c:2045
+#: gschem/src/x_dialog.c:2049
msgid "Edit slot number"
msgstr ""
-#: gschem/src/x_dialog.c:2076
+#: gschem/src/x_dialog.c:2080
msgid "Edit slot number:"
msgstr ""
-#: gschem/src/x_dialog.c:2117
+#: gschem/src/x_dialog.c:2121
#, c-format
msgid "%s%s (%s)"
msgstr ""
-#: gschem/src/x_dialog.c:2140
+#: gschem/src/x_dialog.c:2144
msgid "About gschem"
msgstr ""
-#: gschem/src/x_dialog.c:2141
+#: gschem/src/x_dialog.c:2145
msgid "gEDA: GPL Electronic Design Automation"
msgstr ""
-#: gschem/src/x_dialog.c:2142
+#: gschem/src/x_dialog.c:2146
msgid ""
"Copyright © 1998-2009 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
"Copyright © 1998-2009 gEDA Contributors (see ChangeLog for details)"
msgstr ""
-#: gschem/src/x_dialog.c:2201
+#: gschem/src/x_dialog.c:2205
msgid "Coords"
msgstr ""
-#: gschem/src/x_dialog.c:2222
+#: gschem/src/x_dialog.c:2226
msgid "Screen"
msgstr ""
-#: gschem/src/x_dialog.c:2231
+#: gschem/src/x_dialog.c:2235
msgid "World"
msgstr ""
-#: gschem/src/x_dialog.c:2270
+#: gschem/src/x_dialog.c:2274
msgid "Background"
msgstr ""
-#: gschem/src/x_dialog.c:2276
+#: gschem/src/x_dialog.c:2280
msgid "Net endpoint"
msgstr ""
-#: gschem/src/x_dialog.c:2279
+#: gschem/src/x_dialog.c:2283
msgid "Graphic"
msgstr ""
-#: gschem/src/x_dialog.c:2288
+#: gschem/src/x_dialog.c:2292
msgid "Logic bubble"
msgstr ""
-#: gschem/src/x_dialog.c:2291
+#: gschem/src/x_dialog.c:2295
msgid "Grid point"
msgstr ""
-#: gschem/src/x_dialog.c:2294
+#: gschem/src/x_dialog.c:2298
msgid "Detached attribute"
msgstr ""
-#: gschem/src/x_dialog.c:2297 gschem/src/x_window.c:383
+#: gschem/src/x_dialog.c:2301 gschem/src/x_window.c:383
msgid "Text"
msgstr ""
-#: gschem/src/x_dialog.c:2303
+#: gschem/src/x_dialog.c:2307
msgid "Selection"
msgstr ""
-#: gschem/src/x_dialog.c:2306
+#: gschem/src/x_dialog.c:2310
msgid "Bounding box"
msgstr ""
-#: gschem/src/x_dialog.c:2309
+#: gschem/src/x_dialog.c:2313
msgid "Zoom box"
msgstr ""
-#: gschem/src/x_dialog.c:2318
+#: gschem/src/x_dialog.c:2322
msgid "Output background"
msgstr ""
-#: gschem/src/x_dialog.c:2321
+#: gschem/src/x_dialog.c:2325
msgid "Net junction"
msgstr ""
-#: gschem/src/x_dialog.c:2324
+#: gschem/src/x_dialog.c:2328
msgid "Mesh grid major"
msgstr ""
-#: gschem/src/x_dialog.c:2327
+#: gschem/src/x_dialog.c:2331
msgid "Mesh grid minor"
msgstr ""
-#: gschem/src/x_dialog.c:2330
+#: gschem/src/x_dialog.c:2334
msgid "Unknown"
msgstr ""
-#: gschem/src/x_dialog.c:2481
+#: gschem/src/x_dialog.c:2485
#, c-format
msgid "ERROR: NULL object in color_edit_dialog_apply!\n"
msgstr ""
-#: gschem/src/x_dialog.c:2525
+#: gschem/src/x_dialog.c:2529
msgid "Color Edit"
msgstr ""
-#: gschem/src/x_dialog.c:2556
+#: gschem/src/x_dialog.c:2560
msgid "Object color:"
msgstr ""
-#: gschem/src/x_dialog.c:2614
+#: gschem/src/x_dialog.c:2618
msgid "Hotkeys"
msgstr ""
-#: gschem/src/x_dialog.c:2678
+#: gschem/src/x_dialog.c:2682
msgid "Function"
msgstr ""
-#: gschem/src/x_dialog.c:2685
+#: gschem/src/x_dialog.c:2689
msgid "Keystroke(s)"
msgstr ""
-#: gschem/src/x_dialog.c:2991
+#: gschem/src/x_dialog.c:2995
msgid "Find Text"
msgstr ""
-#: gschem/src/x_dialog.c:3022
+#: gschem/src/x_dialog.c:3026
msgid "Text to find:"
msgstr ""
-#: gschem/src/x_dialog.c:3032
+#: gschem/src/x_dialog.c:3036
msgid "descend into hierarchy"
msgstr ""
-#: gschem/src/x_dialog.c:3097
+#: gschem/src/x_dialog.c:3101
msgid "Hide Text"
msgstr ""
-#: gschem/src/x_dialog.c:3128
+#: gschem/src/x_dialog.c:3132
msgid "Hide text starting with:"
msgstr ""
-#: gschem/src/x_dialog.c:3197
+#: gschem/src/x_dialog.c:3201
msgid "Show Text"
msgstr ""
-#: gschem/src/x_dialog.c:3228
+#: gschem/src/x_dialog.c:3232
msgid "Show text starting with:"
msgstr ""
-#: gschem/src/x_dialog.c:3685
+#: gschem/src/x_dialog.c:3689
msgid "S_elect the schematics you want to save:"
msgstr ""
-#: gschem/src/x_dialog.c:3779
+#: gschem/src/x_dialog.c:3784
#, c-format
msgid "Save the changes to schematic \"%s\" before closing?"
msgstr ""
-#: gschem/src/x_dialog.c:3785
+#: gschem/src/x_dialog.c:3790
#, c-format
msgid ""
"There are %d schematics with unsaved changes. Save changes before closing?"
msgstr ""
-#: gschem/src/x_dialog.c:3814
+#: gschem/src/x_dialog.c:3819
msgid "If you don't save, all your changes will be permanently lost."
msgstr ""
-#: gschem/src/x_dialog.c:3834
+#: gschem/src/x_dialog.c:3839
msgid "_Close without saving"
msgstr ""
-#: gschem/src/x_dialog.c:4170
+#: gschem/src/x_dialog.c:4175
#, c-format
msgid ""
"<span weight=\"bold\" size=\"larger\">The input attribute \"%s\" is invalid\n"
@@ -1487,19 +1495,19 @@ msgid ""
"The value cannot start with a space."
msgstr ""
-#: gschem/src/x_dialog.c:4172
+#: gschem/src/x_dialog.c:4177
msgid "Invalid Attribute"
msgstr ""
-#: gschem/src/x_dialog.c:4208
+#: gschem/src/x_dialog.c:4213
msgid "Pin type"
msgstr ""
-#: gschem/src/x_dialog.c:4232
+#: gschem/src/x_dialog.c:4237
msgid "Net pin"
msgstr ""
-#: gschem/src/x_dialog.c:4234
+#: gschem/src/x_dialog.c:4239
msgid "Bus pin (graphical)"
msgstr ""
@@ -1592,11 +1600,11 @@ msgstr ""
msgid "Write image..."
msgstr "×?ת×?×? ת×?×?× ×?..."
-#: gschem/src/x_log.c:188
+#: gschem/src/x_log.c:209
msgid "** Invalid UTF-8 in log message. See stderr or gschem.log.\n"
msgstr ""
-#: gschem/src/x_log.c:256
+#: gschem/src/x_log.c:288
msgid "Status"
msgstr ""
@@ -1672,69 +1680,60 @@ msgstr ""
msgid "/Up"
msgstr ""
-#: gschem/src/x_menus.c:321
+#: gschem/src/x_menus.c:323
#, c-format
msgid "Tried to set the sensitivity on non-existent menu item '%s'\n"
msgstr ""
-#: gschem/src/x_menus.c:345
+#: gschem/src/x_menus.c:347
msgid "Popup_menu_item_factory doesn't exist!\n"
msgstr ""
-#: gschem/src/x_menus.c:358
+#: gschem/src/x_menus.c:360
msgid "Tried to set the sensitivity on a non-existent popup menu_item\n"
msgstr ""
-#: gschem/src/x_menus.c:438
-#, c-format
-msgid "Couldn't open file %s\n"
-msgstr ""
-
-#: gschem/src/x_menus.c:495
-msgid "Clear"
-msgstr ""
-
-#: gschem/src/x_multiattrib.c:911
+#: gschem/src/x_multiattrib.c:915
msgid "Attributes with empty name are not allowed. Please set a name."
msgstr ""
-#: gschem/src/x_multiattrib.c:1456
+#: gschem/src/x_multiattrib.c:1468
msgid "Show Value only"
msgstr ""
-#: gschem/src/x_multiattrib.c:1458
+#: gschem/src/x_multiattrib.c:1470
msgid "Show Name only"
msgstr ""
-#: gschem/src/x_multiattrib.c:1486
+#: gschem/src/x_multiattrib.c:1498
msgid "Promote"
msgstr ""
-#: gschem/src/x_multiattrib.c:1490
+#: gschem/src/x_multiattrib.c:1502
msgid "Duplicate"
msgstr ""
-#: gschem/src/x_multiattrib.c:1708
+#: gschem/src/x_multiattrib.c:1719
msgid "Edit Attributes"
msgstr ""
-#: gschem/src/x_multiattrib.c:1826
+#: gschem/src/x_multiattrib.c:1837
msgid "Vis?"
msgstr ""
-#: gschem/src/x_multiattrib.c:1844
+#: gschem/src/x_multiattrib.c:1855
msgid "N"
msgstr ""
-#: gschem/src/x_multiattrib.c:1862
+#: gschem/src/x_multiattrib.c:1873
msgid "V"
msgstr ""
-#: gschem/src/x_multiattrib.c:1884
+#: gschem/src/x_multiattrib.c:1895
msgid "Show inherited attributes"
msgstr ""
-#: gschem/src/x_multiattrib.c:1900
+#: gschem/src/x_multiattrib.c:1911
msgid "Add Attribute"
msgstr ""
@@ -1758,23 +1757,23 @@ msgstr "ס×?×?ר ×?×£"
msgid "Discard Page"
msgstr ""
-#: gschem/src/x_pagesel.c:376
+#: gschem/src/x_pagesel.c:375
msgid "Page Manager"
msgstr ""
-#: gschem/src/x_pagesel.c:432
+#: gschem/src/x_pagesel.c:431
msgid "Filename"
msgstr ""
-#: gschem/src/x_pagesel.c:448
+#: gschem/src/x_pagesel.c:447
msgid "Changed"
msgstr ""
-#: gschem/src/x_pagesel.c:468
+#: gschem/src/x_pagesel.c:467
msgid "Right click on the filename for more options..."
msgstr ""
-#: gschem/src/x_preview.c:234
+#: gschem/src/x_preview.c:233
msgid "Preview Buffer"
msgstr ""
@@ -1830,23 +1829,23 @@ msgstr ""
msgid "Command:"
msgstr ""
-#: gschem/src/x_print.c:741
+#: gschem/src/x_print.c:745
msgid "No print destination specified\n"
msgstr ""
-#: gschem/src/x_print.c:748
+#: gschem/src/x_print.c:752
#, c-format
msgid "Cannot print current schematic to [%s]\n"
msgstr ""
-#: gschem/src/x_print.c:757
+#: gschem/src/x_print.c:761
#, c-format
msgid ""
"Error printing to file '%s'\n"
"Check the log window for more information"
msgstr ""
-#: gschem/src/x_print.c:764
+#: gschem/src/x_print.c:768
#, c-format
msgid "Printed current schematic to [%s]\n"
msgstr ""
@@ -1855,6 +1854,11 @@ msgstr ""
msgid "Execute Script..."
msgstr "×?צע תסר×?×?..."
+#: gschem/src/x_script.c:66
+#, c-format
+msgid "Executing guile script [%s]\n"
+msgstr ""
+
#: gschem/src/x_window.c:81
#, c-format
msgid "Couldn't allocate gc\n"
@@ -1962,35 +1966,35 @@ msgstr ""
msgid "New file [%s]\n"
msgstr ""
-#: gschem/src/x_window.c:857
+#: gschem/src/x_window.c:855
#, c-format
msgid "Could NOT save page [%s]\n"
msgstr ""
-#: gschem/src/x_window.c:858
+#: gschem/src/x_window.c:856
msgid "Error while trying to save"
msgstr ""
-#: gschem/src/x_window.c:867
+#: gschem/src/x_window.c:865
#, c-format
msgid "Saved as [%s]\n"
msgstr ""
-#: gschem/src/x_window.c:869
+#: gschem/src/x_window.c:867
#, c-format
msgid "Saved [%s]\n"
msgstr ""
-#: gschem/src/x_window.c:871
+#: gschem/src/x_window.c:869
msgid "Saved"
msgstr ""
-#: gschem/src/x_window.c:945
+#: gschem/src/x_window.c:943
#, c-format
msgid "Discarding page [%s]\n"
msgstr ""
-#: gschem/src/x_window.c:945
+#: gschem/src/x_window.c:943
#, c-format
msgid "Closing [%s]\n"
msgstr ""
@@ -2031,7 +2035,7 @@ msgstr ""
msgid "Save All"
msgstr "ש×?×?ר ×?×?×?"
-#: gschem/lib/system-gschemrc.scm:1386 gschem/lib/system-gschemrc.scm:1477
+#: gschem/lib/system-gschemrc.scm:1386 gschem/lib/system-gschemrc.scm:1478
msgid "_Revert"
msgstr ""
@@ -2043,7 +2047,7 @@ msgstr ""
msgid "Write _image..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1393 gschem/lib/system-gschemrc.scm:1478
+#: gschem/lib/system-gschemrc.scm:1393 gschem/lib/system-gschemrc.scm:1479
msgid "_Close"
msgstr ""
@@ -2075,390 +2079,398 @@ msgstr ""
msgid "_Delete"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1412
+#: gschem/lib/system-gschemrc.scm:1409
+#, fuzzy
+msgid "Select All"
+msgstr "×?צ×? ×?×?×?ר×?"
+
+#: gschem/lib/system-gschemrc.scm:1410
+msgid "Deselect"
+msgstr ""
+
+#: gschem/lib/system-gschemrc.scm:1414
msgid "Rotate 90 Mode"
msgstr "×?צ×? ס×?×?×?×? 90"
-#: gschem/lib/system-gschemrc.scm:1415
+#: gschem/lib/system-gschemrc.scm:1417
msgid "Edit..."
msgstr "ער×?×?..."
-#: gschem/lib/system-gschemrc.scm:1416
+#: gschem/lib/system-gschemrc.scm:1418
msgid "Edit Text..."
msgstr "ער×?×? ×?קס×?"
-#: gschem/lib/system-gschemrc.scm:1417
+#: gschem/lib/system-gschemrc.scm:1419
msgid "Slot..."
msgstr "×?ר×?×¥..."
-#: gschem/lib/system-gschemrc.scm:1418
+#: gschem/lib/system-gschemrc.scm:1420
msgid "Color..."
msgstr "צ×?×¢..."
-#: gschem/lib/system-gschemrc.scm:1419
+#: gschem/lib/system-gschemrc.scm:1421
msgid "Line Width & Type..."
msgstr "ס×?×? ×?ר×?×?×? ק×?..."
-#: gschem/lib/system-gschemrc.scm:1420
+#: gschem/lib/system-gschemrc.scm:1422
msgid "Fill Type..."
msgstr "צ×?רת ×?×?×?×?×?..."
-#: gschem/lib/system-gschemrc.scm:1421
+#: gschem/lib/system-gschemrc.scm:1423
msgid "Symbol Translate..."
msgstr "תר×?×? ס×?×?..."
-#: gschem/lib/system-gschemrc.scm:1425
+#: gschem/lib/system-gschemrc.scm:1427
msgid "Invoke Macro"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1426
+#: gschem/lib/system-gschemrc.scm:1428
msgid "Embed Component/Picture"
msgstr "ש×?×¥ ר×?×?×?/ת×?×?× ×?"
-#: gschem/lib/system-gschemrc.scm:1427
+#: gschem/lib/system-gschemrc.scm:1429
msgid "Unembed Component/Picture"
msgstr "ש×?רר ×?ש×?×?×?×¥ ר×?×?×?/ת×?×?× ×?"
-#: gschem/lib/system-gschemrc.scm:1428
+#: gschem/lib/system-gschemrc.scm:1430
msgid "Update Component"
msgstr "×¢×?×?×? ר×?×?×?"
-#: gschem/lib/system-gschemrc.scm:1429
+#: gschem/lib/system-gschemrc.scm:1431
msgid "Show/Hide Inv Text"
msgstr "×?ר×?×?/×?סתר ×?קס×? ×?×?×?×?"
-#: gschem/lib/system-gschemrc.scm:1430
-msgid "Make Inv Text Vis"
-msgstr "×?פ×?×? ×?קס×? ×?×?סתר ×?×?×?×?×?"
-
-#: gschem/lib/system-gschemrc.scm:1436
+#: gschem/lib/system-gschemrc.scm:1437
msgid "Copy into 1"
msgstr "×?עתק ×?×? 1"
-#: gschem/lib/system-gschemrc.scm:1437
+#: gschem/lib/system-gschemrc.scm:1438
msgid "Copy into 2"
msgstr "×?עתק ×?×? 2"
-#: gschem/lib/system-gschemrc.scm:1438
+#: gschem/lib/system-gschemrc.scm:1439
msgid "Copy into 3"
msgstr "×?עתק ×?×? 3"
-#: gschem/lib/system-gschemrc.scm:1439
+#: gschem/lib/system-gschemrc.scm:1440
msgid "Copy into 4"
msgstr "×?עתק ×?×? 4"
-#: gschem/lib/system-gschemrc.scm:1440
+#: gschem/lib/system-gschemrc.scm:1441
msgid "Copy into 5"
msgstr "×?עתק ×?×? 5"
-#: gschem/lib/system-gschemrc.scm:1441
+#: gschem/lib/system-gschemrc.scm:1442
msgid "Cut into 1"
msgstr "×?×?×?ר ×?×? 1"
-#: gschem/lib/system-gschemrc.scm:1442
+#: gschem/lib/system-gschemrc.scm:1443
msgid "Cut into 2"
msgstr "×?×?×?ר ×?×? 2"
-#: gschem/lib/system-gschemrc.scm:1443
+#: gschem/lib/system-gschemrc.scm:1444
msgid "Cut into 3"
msgstr "×?×?×?ר ×?×? 3"
-#: gschem/lib/system-gschemrc.scm:1444
+#: gschem/lib/system-gschemrc.scm:1445
msgid "Cut into 4"
msgstr "×?×?×?ר ×?×? 4"
-#: gschem/lib/system-gschemrc.scm:1445
+#: gschem/lib/system-gschemrc.scm:1446
msgid "Cut into 5"
msgstr "×?×?×?ר ×?×? 5"
-#: gschem/lib/system-gschemrc.scm:1446
+#: gschem/lib/system-gschemrc.scm:1447
msgid "Paste from 1"
msgstr "×?×?×?ק ×?-1"
-#: gschem/lib/system-gschemrc.scm:1447
+#: gschem/lib/system-gschemrc.scm:1448
msgid "Paste from 2"
msgstr "×?×?×?ק ×?-2"
-#: gschem/lib/system-gschemrc.scm:1448
+#: gschem/lib/system-gschemrc.scm:1449
msgid "Paste from 3"
msgstr "×?×?×?ק ×?-3"
-#: gschem/lib/system-gschemrc.scm:1449
+#: gschem/lib/system-gschemrc.scm:1450
msgid "Paste from 4"
msgstr "×?×?×?ק ×?-4"
-#: gschem/lib/system-gschemrc.scm:1450
+#: gschem/lib/system-gschemrc.scm:1451
msgid "Paste from 5"
msgstr "×?×?×?ק ×?-5"
-#: gschem/lib/system-gschemrc.scm:1456
+#: gschem/lib/system-gschemrc.scm:1457
msgid "_Redraw"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1457
+#: gschem/lib/system-gschemrc.scm:1458
msgid "_Pan"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1458
+#: gschem/lib/system-gschemrc.scm:1459
msgid "Zoom _Box"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1459
+#: gschem/lib/system-gschemrc.scm:1460
msgid "Zoom _Extents"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1460
+#: gschem/lib/system-gschemrc.scm:1461
msgid "Zoom _In"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1461
+#: gschem/lib/system-gschemrc.scm:1462
msgid "Zoom _Out"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1462
+#: gschem/lib/system-gschemrc.scm:1463
msgid "Zoom _Full"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1464
+#: gschem/lib/system-gschemrc.scm:1465
msgid "_Dark color scheme"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1465
+#: gschem/lib/system-gschemrc.scm:1466
msgid "_Light color scheme"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1466
+#: gschem/lib/system-gschemrc.scm:1467
msgid "B_W color scheme"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1473
+#: gschem/lib/system-gschemrc.scm:1474
msgid "_Manager..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1474
+#: gschem/lib/system-gschemrc.scm:1475
msgid "_Previous"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1475
+#: gschem/lib/system-gschemrc.scm:1476
msgid "_Next"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1476
+#: gschem/lib/system-gschemrc.scm:1477
msgid "Ne_w"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1480
+#: gschem/lib/system-gschemrc.scm:1481
msgid "_Discard"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1486
+#: gschem/lib/system-gschemrc.scm:1487
msgid "_Component..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1487
+#: gschem/lib/system-gschemrc.scm:1488
msgid "_Net"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1488
+#: gschem/lib/system-gschemrc.scm:1489
msgid "B_us"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1489
+#: gschem/lib/system-gschemrc.scm:1490
msgid "_Attribute..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1490
+#: gschem/lib/system-gschemrc.scm:1491
msgid "_Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1492
+#: gschem/lib/system-gschemrc.scm:1493
msgid "_Line"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1493
+#: gschem/lib/system-gschemrc.scm:1494
msgid "_Box"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1494
+#: gschem/lib/system-gschemrc.scm:1495
msgid "C_ircle"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1495
+#: gschem/lib/system-gschemrc.scm:1496
msgid "A_rc"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1496
+#: gschem/lib/system-gschemrc.scm:1497
msgid "_Pin"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1497
+#: gschem/lib/system-gschemrc.scm:1498
msgid "Pictu_re..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1503
+#: gschem/lib/system-gschemrc.scm:1504
msgid "_Down Schematic"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1504
+#: gschem/lib/system-gschemrc.scm:1505
msgid "Down _Symbol"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1505
+#: gschem/lib/system-gschemrc.scm:1506
msgid "_Up"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1506
+#: gschem/lib/system-gschemrc.scm:1507
msgid "D_ocumentation..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1512
+#: gschem/lib/system-gschemrc.scm:1513
msgid "_Attach"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1513
+#: gschem/lib/system-gschemrc.scm:1514
msgid "_Detach"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1514
+#: gschem/lib/system-gschemrc.scm:1515
msgid "Show _Value"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1515
+#: gschem/lib/system-gschemrc.scm:1516
msgid "Show _Name"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1516
+#: gschem/lib/system-gschemrc.scm:1517
msgid "Show _Both"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1517
+#: gschem/lib/system-gschemrc.scm:1518
msgid "_Toggle Visibility"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1519
+#: gschem/lib/system-gschemrc.scm:1520
msgid "_Find Specific Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1520
+#: gschem/lib/system-gschemrc.scm:1521
msgid "_Hide Specific Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1521
+#: gschem/lib/system-gschemrc.scm:1522
msgid "_Show Specific Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1522
+#: gschem/lib/system-gschemrc.scm:1523
msgid "A_utonumber Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1528
+#: gschem/lib/system-gschemrc.scm:1529
msgid "_Text Size..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1529
+#: gschem/lib/system-gschemrc.scm:1530
msgid "Cycle _grid styles"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1530
+#: gschem/lib/system-gschemrc.scm:1531
msgid "Toggle _Snap On/Off"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1531
+#: gschem/lib/system-gschemrc.scm:1532
msgid "Snap Grid S_pacing..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1532
+#: gschem/lib/system-gschemrc.scm:1533
msgid "Scale _up Grid Spacing"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1534
+#: gschem/lib/system-gschemrc.scm:1535
msgid "Scale _down Grid Spacing"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1536
+#: gschem/lib/system-gschemrc.scm:1537
msgid "Toggle _Outline/Box"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1538
+#: gschem/lib/system-gschemrc.scm:1539
msgid "Toggle Net _Rubberband"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1539
+#: gschem/lib/system-gschemrc.scm:1540
msgid "Toggle _Magnetic Net"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1540
+#: gschem/lib/system-gschemrc.scm:1541
msgid "Show _Log Window..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1542
+#: gschem/lib/system-gschemrc.scm:1543
msgid "Show _Coord Window..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1558
+#: gschem/lib/system-gschemrc.scm:1559
msgid "gEDA Docu_mentation..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1559
+#: gschem/lib/system-gschemrc.scm:1560
msgid "gschem _FAQ..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1560
+#: gschem/lib/system-gschemrc.scm:1561
msgid "gEDA _Wiki..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1561
+#: gschem/lib/system-gschemrc.scm:1562
msgid "Component D_ocumentation..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1563
+#: gschem/lib/system-gschemrc.scm:1564
msgid "_Hotkeys..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1564
+#: gschem/lib/system-gschemrc.scm:1565
msgid "_About..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1570
+#: gschem/lib/system-gschemrc.scm:1571
msgid "_File"
msgstr "ק×?×?×¥"
-#: gschem/lib/system-gschemrc.scm:1571
+#: gschem/lib/system-gschemrc.scm:1572
msgid "_Edit"
msgstr "ער×?×?×?"
-#: gschem/lib/system-gschemrc.scm:1572
+#: gschem/lib/system-gschemrc.scm:1573
msgid "_Buffer"
msgstr "×?×?צץ"
-#: gschem/lib/system-gschemrc.scm:1573
+#: gschem/lib/system-gschemrc.scm:1574
msgid "_View"
msgstr "×?צ×?"
-#: gschem/lib/system-gschemrc.scm:1574
+#: gschem/lib/system-gschemrc.scm:1575
msgid "_Page"
msgstr "×?×£"
-#: gschem/lib/system-gschemrc.scm:1575
+#: gschem/lib/system-gschemrc.scm:1576
msgid "_Add"
msgstr "×?×?סף"
-#: gschem/lib/system-gschemrc.scm:1576
+#: gschem/lib/system-gschemrc.scm:1577
msgid "Hie_rarchy"
msgstr "×?×?רר×?×?×?"
-#: gschem/lib/system-gschemrc.scm:1577
+#: gschem/lib/system-gschemrc.scm:1578
msgid "A_ttributes"
msgstr "×?×?פ×?×?× ×?×?"
-#: gschem/lib/system-gschemrc.scm:1578
+#: gschem/lib/system-gschemrc.scm:1579
msgid "_Options"
msgstr "×?×?×?ר×?ת"
-#: gschem/lib/system-gschemrc.scm:1579
+#: gschem/lib/system-gschemrc.scm:1580
msgid "_Help"
msgstr ""
+#~ msgid "Make Inv Text Vis"
+#~ msgstr "×?פ×?×? ×?קס×? ×?×?סתר ×?×?×?×?×?"
+
#~ msgid "Recent files"
#~ msgstr "ק×?צ×?×? ×?×?ר×?× ×?×?"
diff --git a/gschem/po/hu.po b/gschem/po/hu.po
index e84e9fa..a02dbc4 100644
--- a/gschem/po/hu.po
+++ b/gschem/po/hu.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2010-11-07 13:37+0000\n"
+"POT-Creation-Date: 2011-01-16 00:11-0500\n"
"PO-Revision-Date: 2010-02-13 10:43+0000\n"
"Last-Translator: kop <Unknown>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -22,17 +22,17 @@ msgstr ""
msgid "Zoom too small! Cannot zoom further.\n"
msgstr "Túl nagy nagyÃtás! Nem tudok tovább nagyÃtani.\n"
-#: gschem/src/g_funcs.c:339 gschem/src/i_callbacks.c:68
+#: gschem/src/g_funcs.c:347 gschem/src/i_callbacks.c:68
#, c-format
msgid "Could not fork\n"
msgstr "Az elágazás sikertelen.\n"
-#: gschem/src/g_funcs.c:355 gschem/src/i_callbacks.c:78
+#: gschem/src/g_funcs.c:363 gschem/src/i_callbacks.c:78
#, c-format
msgid "Could not invoke %s\n"
msgstr "Nem tudom elindÃtani a(z) %s-t.\n"
-#: gschem/src/g_funcs.c:361 gschem/src/i_callbacks.c:82
+#: gschem/src/g_funcs.c:369 gschem/src/i_callbacks.c:82
msgid "Documentation commands not supported under MinGW.\n"
msgstr "Dokumentációs parancsok nem működnek MinGW alatt.\n"
@@ -121,12 +121,12 @@ msgstr ""
msgid "Invalid number of steps [%d] scrollpan-steps\n"
msgstr ""
-#: gschem/src/gschem.c:184
+#: gschem/src/gschem.c:188
#, c-format
msgid "gEDA/gschem version %s%s.%s\n"
msgstr "gEDA/gschem verzió %s%s.%s\n"
-#: gschem/src/gschem.c:187
+#: gschem/src/gschem.c:191
msgid ""
"gEDA/gschem comes with ABSOLUTELY NO WARRANTY; see COPYING for more "
"details.\n"
@@ -134,12 +134,12 @@ msgstr ""
"A gEDA/gschem NEM RENDELKEZIK SEMMIFÃ?LE GARANCIÃ?VAL; olvasd el a COPYING "
"fájlt további részletekért\n"
-#: gschem/src/gschem.c:189
+#: gschem/src/gschem.c:193
msgid ""
"This is free software, and you are welcome to redistribute it under certain\n"
msgstr "Ez egy szabad program, bizonyos feltételek mellett szabadon\n"
-#: gschem/src/gschem.c:191
+#: gschem/src/gschem.c:195
msgid ""
"conditions; please see the COPYING file for more details.\n"
"\n"
@@ -147,17 +147,17 @@ msgstr ""
"terjeszthetÅ?, olvasd el a COPYING fájt további információkért.\n"
"\n"
-#: gschem/src/gschem.c:194
+#: gschem/src/gschem.c:198
#, c-format
msgid "This is the MINGW32 port.\n"
msgstr "Ez a MinGW32 port.\n"
-#: gschem/src/gschem.c:198
+#: gschem/src/gschem.c:202
#, c-format
msgid "Current locale settings: %s\n"
msgstr "Jelenlegi területi beállÃtás: %s\n"
-#: gschem/src/gschem.c:213
+#: gschem/src/gschem.c:218
msgid ""
"You must set the GEDADATA environment variable!\n"
"\n"
@@ -165,31 +165,21 @@ msgid ""
"environment variable to point to the correct location.\n"
msgstr ""
-#: gschem/src/gschem.c:248
+#: gschem/src/gschem.c:256
#, c-format
msgid "Couldn't find init scm file [%s]\n"
msgstr ""
-#: gschem/src/gschem.c:252
+#: gschem/src/gschem.c:260
#, c-format
msgid "Read init scm file [%s]\n"
msgstr "[%s] init scm fájl olvasása.\n"
-#: gschem/src/gschem.c:256
+#: gschem/src/gschem.c:264
#, c-format
msgid "Failed to read init scm file [%s]\n"
msgstr "[%s] init scm fájl olvasása sikertelen.\n"
-#: gschem/src/gschem.c:317
-#, c-format
-msgid "Scheme directory NOT set!\n"
-msgstr "A scheme könyvtár nincs beállÃtva!\n"
-
-#: gschem/src/gschem.c:324 gschem/src/x_script.c:66
-#, c-format
-msgid "Executing guile script [%s]\n"
-msgstr "[%s] guile szkript végrehajtása.\n"
-
#: gschem/src/gschem_cairo.c:310
#, c-format
msgid "Unknown end for line (%d)\n"
@@ -213,11 +203,11 @@ msgstr "Alkatrész mód"
msgid "Text Mode"
msgstr "Szövegbeviteli üzemmód"
-#: gschem/src/i_basic.c:84 gschem/lib/system-gschemrc.scm:1409
+#: gschem/src/i_basic.c:84 gschem/lib/system-gschemrc.scm:1411
msgid "Copy Mode"
msgstr "Másolási mód"
-#: gschem/src/i_basic.c:87 gschem/lib/system-gschemrc.scm:1411
+#: gschem/src/i_basic.c:87 gschem/lib/system-gschemrc.scm:1413
msgid "Move Mode"
msgstr "Mozgatási mód"
@@ -225,7 +215,7 @@ msgstr "Mozgatási mód"
msgid "Rotate Mode"
msgstr "Forgatás üzemmód"
-#: gschem/src/i_basic.c:91 gschem/lib/system-gschemrc.scm:1413
+#: gschem/src/i_basic.c:91 gschem/lib/system-gschemrc.scm:1415
msgid "Mirror Mode"
msgstr "Tükrözés"
@@ -278,22 +268,22 @@ msgstr "�v üzemmód"
msgid "Pin Mode"
msgstr "Alkatrészláb üzemmód"
-#: gschem/src/i_basic.c:135 gschem/src/i_callbacks.c:544
-#: gschem/src/i_callbacks.c:568
+#: gschem/src/i_basic.c:135 gschem/src/i_callbacks.c:576
+#: gschem/src/i_callbacks.c:600
msgid "Copy"
msgstr "Másolás"
-#: gschem/src/i_basic.c:137 gschem/src/i_callbacks.c:634
-#: gschem/src/i_callbacks.c:658
+#: gschem/src/i_basic.c:137 gschem/src/i_callbacks.c:666
+#: gschem/src/i_callbacks.c:690
msgid "Move"
msgstr "Mozgatás"
-#: gschem/src/i_basic.c:139 gschem/src/i_callbacks.c:589
-#: gschem/src/i_callbacks.c:613
+#: gschem/src/i_basic.c:139 gschem/src/i_callbacks.c:621
+#: gschem/src/i_callbacks.c:645
msgid "Multiple Copy"
msgstr "Többszörös másolás"
-#: gschem/src/i_basic.c:142 gschem/lib/system-gschemrc.scm:1410
+#: gschem/src/i_basic.c:142 gschem/lib/system-gschemrc.scm:1412
msgid "Multiple Copy Mode"
msgstr "Többszörös másolás mód"
@@ -313,7 +303,7 @@ msgstr ""
msgid "Action"
msgstr "Művelet"
-#: gschem/src/i_basic.c:260 gschem/src/x_dialog.c:2312
+#: gschem/src/i_basic.c:260 gschem/src/x_dialog.c:2316
#: gschem/src/x_window.c:491
msgid "Stroke"
msgstr ""
@@ -344,7 +334,7 @@ msgstr "Háló (%s, %s)"
msgid "Documentation for [%s,%s,%s,%s]\n"
msgstr "Dokumentáció [%s,%s,%s,%s]-hoz\n"
-#: gschem/src/i_callbacks.c:123 gschem/src/i_callbacks.c:1699
+#: gschem/src/i_callbacks.c:123 gschem/src/i_callbacks.c:1706
#, c-format
msgid "New page created [%s]\n"
msgstr "[%s] oldal létrehozva.\n"
@@ -366,69 +356,69 @@ msgstr "Minden oldal elmentve."
msgid "Closing Window\n"
msgstr "Ablak bezárása\n"
-#: gschem/src/i_callbacks.c:549 gschem/src/i_callbacks.c:594
-#: gschem/src/i_callbacks.c:639
+#: gschem/src/i_callbacks.c:581 gschem/src/i_callbacks.c:626
+#: gschem/src/i_callbacks.c:671
msgid "Select objs first"
msgstr "ElÅ?ször válassz objektumokat"
-#: gschem/src/i_callbacks.c:678 gschem/src/x_multiattrib.c:1491
+#: gschem/src/i_callbacks.c:710 gschem/src/x_multiattrib.c:1503
msgid "Delete"
msgstr "Törlés"
-#: gschem/src/i_callbacks.c:703
+#: gschem/src/i_callbacks.c:735
msgid "Edit"
msgstr "Szerkesztés"
-#: gschem/src/i_callbacks.c:718
+#: gschem/src/i_callbacks.c:750
msgid "Edit pin type"
msgstr ""
-#: gschem/src/i_callbacks.c:737
+#: gschem/src/i_callbacks.c:769
msgid "Edit Text"
msgstr "Szöveg szerkesztése"
-#: gschem/src/i_callbacks.c:760
+#: gschem/src/i_callbacks.c:792
msgid "Slot"
msgstr ""
-#: gschem/src/i_callbacks.c:777
+#: gschem/src/i_callbacks.c:809
msgid "Color"
msgstr "SzÃn"
-#: gschem/src/i_callbacks.c:814 gschem/src/i_callbacks.c:859
+#: gschem/src/i_callbacks.c:846 gschem/src/i_callbacks.c:891
msgid "Rotate"
msgstr "Forgatás"
-#: gschem/src/i_callbacks.c:882 gschem/src/i_callbacks.c:907
+#: gschem/src/i_callbacks.c:913 gschem/src/i_callbacks.c:938
msgid "Mirror"
msgstr "Tükrözés"
-#: gschem/src/i_callbacks.c:928 gschem/src/x_dialog.c:2315
-#: gschem/lib/system-gschemrc.scm:1422
+#: gschem/src/i_callbacks.c:959 gschem/src/x_dialog.c:2319
+#: gschem/lib/system-gschemrc.scm:1424
msgid "Lock"
msgstr "Zárolás"
-#: gschem/src/i_callbacks.c:946 gschem/lib/system-gschemrc.scm:1423
+#: gschem/src/i_callbacks.c:977 gschem/lib/system-gschemrc.scm:1425
msgid "Unlock"
msgstr "Zárolás feloldása"
-#: gschem/src/i_callbacks.c:964 gschem/src/x_dialog.c:1734
+#: gschem/src/i_callbacks.c:995 gschem/src/x_dialog.c:1737
msgid "Translate"
msgstr "Eltolás"
-#: gschem/src/i_callbacks.c:967
+#: gschem/src/i_callbacks.c:998
msgid "WARNING: Do not translate with snap off!\n"
msgstr ""
-#: gschem/src/i_callbacks.c:968
+#: gschem/src/i_callbacks.c:999
msgid "WARNING: Turning snap on and continuing with translate.\n"
msgstr ""
-#: gschem/src/i_callbacks.c:975
+#: gschem/src/i_callbacks.c:1006
msgid "WARNING: Snap grid size is not equal to 100!\n"
msgstr "Vigyázat, a hálószemméret nem 100!\n"
-#: gschem/src/i_callbacks.c:977
+#: gschem/src/i_callbacks.c:1008
msgid ""
"WARNING: If you are translating a symbol to the origin, the snap grid size "
"should be set to 100\n"
@@ -436,176 +426,172 @@ msgstr ""
"Vigyázat, az alkatrész kezdÅ?ponthoz való tolásához a hálószemméretnek 100-"
"nak kell lennie!\n"
-#: gschem/src/i_callbacks.c:1008
+#: gschem/src/i_callbacks.c:1039
msgid "Embed"
msgstr "Beágyazás"
-#: gschem/src/i_callbacks.c:1047
+#: gschem/src/i_callbacks.c:1078
msgid "Unembed"
msgstr "Beágyazás megszüntetése"
-#: gschem/src/i_callbacks.c:1089
+#: gschem/src/i_callbacks.c:1120
msgid "Update"
msgstr "FrissÃtés"
-#: gschem/src/i_callbacks.c:1136
+#: gschem/src/i_callbacks.c:1167
msgid "ShowHidden"
msgstr "Rejtettek megjelenÃtése"
-#: gschem/src/i_callbacks.c:1160
-msgid "MakeVisible"
-msgstr "Láthatóvá tétel"
-
-#: gschem/src/i_callbacks.c:1466 gschem/src/i_callbacks.c:1538
+#: gschem/src/i_callbacks.c:1473 gschem/src/i_callbacks.c:1545
msgid "Pan"
msgstr "Középre"
-#: gschem/src/i_callbacks.c:1743
+#: gschem/src/i_callbacks.c:1750
msgid "Really revert page?"
msgstr "Biztosan újratöltsem az oldalt?"
-#: gschem/src/i_callbacks.c:1813
+#: gschem/src/i_callbacks.c:1820
msgid "Copy to clipboard"
msgstr ""
-#: gschem/src/i_callbacks.c:1831
+#: gschem/src/i_callbacks.c:1838
msgid "Cut to clipboard"
msgstr "Kivágás a vágólapra"
-#: gschem/src/i_callbacks.c:1849
+#: gschem/src/i_callbacks.c:1856
msgid "Paste from clipboard"
msgstr "Beillesztés a vágólapról"
-#: gschem/src/i_callbacks.c:1861 gschem/src/i_callbacks.c:2100
-#: gschem/src/i_callbacks.c:2122 gschem/src/i_callbacks.c:2144
-#: gschem/src/i_callbacks.c:2166 gschem/src/i_callbacks.c:2188
+#: gschem/src/i_callbacks.c:1868 gschem/src/i_callbacks.c:2107
+#: gschem/src/i_callbacks.c:2129 gschem/src/i_callbacks.c:2151
+#: gschem/src/i_callbacks.c:2173 gschem/src/i_callbacks.c:2195
msgid "Empty buffer"
msgstr "Ã?res buffer"
-#: gschem/src/i_callbacks.c:1906
+#: gschem/src/i_callbacks.c:1913
msgid "Copy 1"
msgstr "Másolás az 1-be"
-#: gschem/src/i_callbacks.c:1925
+#: gschem/src/i_callbacks.c:1932
msgid "Copy 2"
msgstr "Másolás a 2-be"
-#: gschem/src/i_callbacks.c:1944
+#: gschem/src/i_callbacks.c:1951
msgid "Copy 3"
msgstr "Másolás a 3-ba"
-#: gschem/src/i_callbacks.c:1963
+#: gschem/src/i_callbacks.c:1970
msgid "Copy 4"
msgstr "Másolás a 4-be"
-#: gschem/src/i_callbacks.c:1982
+#: gschem/src/i_callbacks.c:1989
msgid "Copy 5"
msgstr "Másolás az 5-be"
-#: gschem/src/i_callbacks.c:2001
+#: gschem/src/i_callbacks.c:2008
msgid "Cut 1"
msgstr "Kivágás az 1-be"
-#: gschem/src/i_callbacks.c:2020
+#: gschem/src/i_callbacks.c:2027
msgid "Cut 2"
msgstr "Kivágás a 2-be"
-#: gschem/src/i_callbacks.c:2039
+#: gschem/src/i_callbacks.c:2046
msgid "Cut 3"
msgstr "Kivágás a 3-ba"
-#: gschem/src/i_callbacks.c:2058
+#: gschem/src/i_callbacks.c:2065
msgid "Cut 4"
msgstr "Kivágás a 4-be"
-#: gschem/src/i_callbacks.c:2077
+#: gschem/src/i_callbacks.c:2084
msgid "Cut 5"
msgstr "Kivágás az 5-be"
-#: gschem/src/i_callbacks.c:2093
+#: gschem/src/i_callbacks.c:2100
msgid "Paste 1"
msgstr "Beillesztés az 1-bÅ?l"
-#: gschem/src/i_callbacks.c:2115
+#: gschem/src/i_callbacks.c:2122
msgid "Paste 2"
msgstr "Beillesztés a 2-bÅ?l"
-#: gschem/src/i_callbacks.c:2137
+#: gschem/src/i_callbacks.c:2144
msgid "Paste 3"
msgstr "Beillesztés a 3-ból"
-#: gschem/src/i_callbacks.c:2159
+#: gschem/src/i_callbacks.c:2166
msgid "Paste 4"
msgstr "Beillesztés a 4-bÅ?l"
-#: gschem/src/i_callbacks.c:2181
+#: gschem/src/i_callbacks.c:2188
msgid "Paste 5"
msgstr "Beillesztés az 5-bÅ?l"
-#: gschem/src/i_callbacks.c:2318 gschem/src/x_window.c:355
+#: gschem/src/i_callbacks.c:2325 gschem/src/x_window.c:355
msgid "Component"
msgstr "Alkatrész"
-#: gschem/src/i_callbacks.c:2354 gschem/src/i_callbacks.c:2373
-#: gschem/src/x_dialog.c:2285
+#: gschem/src/i_callbacks.c:2361 gschem/src/i_callbacks.c:2380
+#: gschem/src/x_dialog.c:2289
msgid "Attribute"
msgstr "Attribútum"
-#: gschem/src/i_callbacks.c:2395 gschem/src/i_callbacks.c:2422
-#: gschem/src/x_dialog.c:2282
+#: gschem/src/i_callbacks.c:2402 gschem/src/i_callbacks.c:2429
+#: gschem/src/x_dialog.c:2286
msgid "Net"
msgstr "Net"
-#: gschem/src/i_callbacks.c:2466 gschem/src/i_callbacks.c:2493
-#: gschem/src/x_dialog.c:2300 gschem/src/x_window.c:375
+#: gschem/src/i_callbacks.c:2473 gschem/src/i_callbacks.c:2500
+#: gschem/src/x_dialog.c:2304 gschem/src/x_window.c:375
msgid "Bus"
msgstr "Busz"
-#: gschem/src/i_callbacks.c:2574 gschem/src/i_callbacks.c:2597
+#: gschem/src/i_callbacks.c:2581 gschem/src/i_callbacks.c:2604
msgid "Line"
msgstr "Vonal"
-#: gschem/src/i_callbacks.c:2619 gschem/src/i_callbacks.c:2642
+#: gschem/src/i_callbacks.c:2626 gschem/src/i_callbacks.c:2649
msgid "Box"
msgstr "Téglalap"
-#: gschem/src/i_callbacks.c:2698 gschem/src/i_callbacks.c:2722
+#: gschem/src/i_callbacks.c:2705 gschem/src/i_callbacks.c:2729
msgid "Circle"
msgstr "Kör"
-#: gschem/src/i_callbacks.c:2744 gschem/src/i_callbacks.c:2767
+#: gschem/src/i_callbacks.c:2751 gschem/src/i_callbacks.c:2774
msgid "Arc"
msgstr "Ã?v"
-#: gschem/src/i_callbacks.c:2789 gschem/src/i_callbacks.c:2812
-#: gschem/src/x_dialog.c:2273
+#: gschem/src/i_callbacks.c:2796 gschem/src/i_callbacks.c:2819
+#: gschem/src/x_dialog.c:2277
msgid "Pin"
msgstr "Alkatrészláb"
-#: gschem/src/i_callbacks.c:2871
+#: gschem/src/i_callbacks.c:2878
#, c-format
msgid "Searching for source [%s]\n"
msgstr "[%s] forrás keresése\n"
-#: gschem/src/i_callbacks.c:2895
+#: gschem/src/i_callbacks.c:2902
#, c-format
msgid "Cannot find source [%s]\n"
msgstr "Nem találom a(z) [%s] forrást.\n"
-#: gschem/src/i_callbacks.c:2964
+#: gschem/src/i_callbacks.c:2965
#, c-format
msgid "Searching for symbol [%s]\n"
msgstr "[%s] szimbólum keresése\n"
-#: gschem/src/i_callbacks.c:2970
+#: gschem/src/i_callbacks.c:2971
msgid "Symbol is not a real file. Symbol cannot be loaded.\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3001
+#: gschem/src/i_callbacks.c:3002
msgid "Cannot find any schematics above the current one!\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3055
+#: gschem/src/i_callbacks.c:3056
msgid ""
"This command retrieves the component documentation from the web, but there "
"is no component selected"
@@ -613,84 +599,84 @@ msgstr ""
"Ez a parancs letölti az alkatrész dokumentációját az internetrÅ?l, de nincs "
"kiválasztott alkatrész."
-#: gschem/src/i_callbacks.c:3083
+#: gschem/src/i_callbacks.c:3084
msgid "Attach"
msgstr "Csatolás"
-#: gschem/src/i_callbacks.c:3130
+#: gschem/src/i_callbacks.c:3131
msgid "Detach"
msgstr "Leválasztás"
-#: gschem/src/i_callbacks.c:3165
+#: gschem/src/i_callbacks.c:3166
msgid "ShowN"
msgstr ""
-#: gschem/src/i_callbacks.c:3201
+#: gschem/src/i_callbacks.c:3202
msgid "ShowV"
msgstr ""
-#: gschem/src/i_callbacks.c:3237
+#: gschem/src/i_callbacks.c:3238
msgid "ShowB"
msgstr ""
-#: gschem/src/i_callbacks.c:3274
+#: gschem/src/i_callbacks.c:3275
msgid "VisToggle"
msgstr "Láthatóság be/ki"
-#: gschem/src/i_callbacks.c:3304
+#: gschem/src/i_callbacks.c:3305
#, c-format
msgid "Sorry but this is a non-functioning menu option\n"
msgstr "Elnézést, ez egy nem működÅ? menüpont.\n"
-#: gschem/src/i_callbacks.c:3394
+#: gschem/src/i_callbacks.c:3395
msgid "Action feedback mode set to OUTLINE\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3397
+#: gschem/src/i_callbacks.c:3398
msgid "Action feedback mode set to BOUNDINGBOX\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3422
+#: gschem/src/i_callbacks.c:3423
msgid "Grid OFF\n"
msgstr "Háló ki\n"
-#: gschem/src/i_callbacks.c:3423
+#: gschem/src/i_callbacks.c:3424
msgid "Dot grid selected\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3424
+#: gschem/src/i_callbacks.c:3425
msgid "Mesh grid selected\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3445
+#: gschem/src/i_callbacks.c:3446
msgid "Snap OFF (CAUTION!)\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3448
+#: gschem/src/i_callbacks.c:3449
msgid "Snap ON\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3451
+#: gschem/src/i_callbacks.c:3452
msgid "Snap back to the grid (CAUTION!)\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3477
+#: gschem/src/i_callbacks.c:3478
msgid "Rubber band OFF \n"
msgstr ""
-#: gschem/src/i_callbacks.c:3480
+#: gschem/src/i_callbacks.c:3481
msgid "Rubber band ON\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3495
+#: gschem/src/i_callbacks.c:3496
msgid "magnetic net mode: ON\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3498
+#: gschem/src/i_callbacks.c:3499
msgid "magnetic net mode: OFF\n"
msgstr ""
-#: gschem/src/o_box.c:153
+#: gschem/src/o_box.c:149
#, c-format
msgid "Unknown type for box (fill)!\n"
msgstr ""
@@ -710,17 +696,17 @@ msgstr ""
msgid "Got an invalid buffer_number [o_buffer_paste_start]\n"
msgstr ""
-#: gschem/src/o_bus.c:118
+#: gschem/src/o_bus.c:117
#, c-format
msgid "Got an invalid which one in o_bus_draw_stretch\n"
msgstr ""
-#: gschem/src/o_circle.c:134
+#: gschem/src/o_circle.c:130
#, c-format
msgid "Unknown type for circle (fill)!\n"
msgstr ""
-#: gschem/src/o_complex.c:243 gschem/src/o_complex.c:247
+#: gschem/src/o_complex.c:237 gschem/src/o_complex.c:241
#, c-format
msgid "Translating schematic [%d %d]\n"
msgstr ""
@@ -738,35 +724,35 @@ msgstr "Az objektum már zárolva van.\n"
msgid "Object already unlocked\n"
msgstr ""
-#: gschem/src/o_misc.c:413
+#: gschem/src/o_misc.c:409
msgid "Hidden text is now visible\n"
msgstr ""
-#: gschem/src/o_misc.c:415
+#: gschem/src/o_misc.c:411
msgid "Hidden text is now invisible\n"
msgstr ""
-#: gschem/src/o_misc.c:668
+#: gschem/src/o_misc.c:636
#, c-format
msgid "Could not find symbol [%s] in library. Update failed.\n"
msgstr "Nem találom a(z) [%s] szimbólumot. A frissÃtés nem sikerült.\n"
-#: gschem/src/o_misc.c:783
+#: gschem/src/o_misc.c:751
#, c-format
msgid "o_autosave_backups: Can't get the real filename of %s."
msgstr ""
-#: gschem/src/o_misc.c:827
+#: gschem/src/o_misc.c:795
#, c-format
msgid "Could NOT set previous backup file [%s] read-write\n"
msgstr ""
-#: gschem/src/o_misc.c:845
+#: gschem/src/o_misc.c:815
#, c-format
msgid "Could NOT set backup file [%s] readonly\n"
msgstr ""
-#: gschem/src/o_misc.c:850
+#: gschem/src/o_misc.c:820
#, c-format
msgid "Could NOT save backup file [%s]\n"
msgstr ""
@@ -786,36 +772,36 @@ msgstr ""
msgid "Got a non line object in o_move_check_endpoint\n"
msgstr ""
-#: gschem/src/o_net.c:159
+#: gschem/src/o_net.c:158
#, c-format
msgid "Got an invalid which one in o_net_draw_stretch\n"
msgstr ""
-#: gschem/src/o_net.c:538
+#: gschem/src/o_net.c:537
msgid "Warning: Starting net at off grid coordinate\n"
msgstr ""
-#: gschem/src/o_net.c:600
+#: gschem/src/o_net.c:599
msgid "Warning: Ending net at off grid coordinate\n"
msgstr ""
-#: gschem/src/o_net.c:932 gschem/src/o_net.c:969 gschem/src/o_net.c:1040
-#: gschem/src/o_net.c:1076
+#: gschem/src/o_net.c:931 gschem/src/o_net.c:968 gschem/src/o_net.c:1039
+#: gschem/src/o_net.c:1075
#, c-format
msgid "Tried to add more than two bus rippers. Internal gschem error.\n"
msgstr ""
-#: gschem/src/o_net.c:1144
+#: gschem/src/o_net.c:1143
#, c-format
msgid "Bus ripper symbol [%s] was not found in any component library\n"
msgstr ""
-#: gschem/src/o_path.c:352
+#: gschem/src/o_path.c:348
#, c-format
msgid "Unknown type for path (fill)!\n"
msgstr ""
-#: gschem/src/o_picture.c:163 gschem/src/o_picture.c:539
+#: gschem/src/o_picture.c:163 gschem/src/o_picture.c:537
#, c-format
msgid "Failed to load picture: %s"
msgstr "Sikertelen a(z) %s kép betöltése"
@@ -824,7 +810,7 @@ msgstr "Sikertelen a(z) %s kép betöltése"
msgid "Picture"
msgstr "Kép"
-#: gschem/src/o_picture.c:447 gschem/src/x_attribedit.c:141
+#: gschem/src/o_picture.c:445 gschem/src/x_attribedit.c:141
#, c-format
msgid "ERROR: NULL object!\n"
msgstr ""
@@ -845,34 +831,46 @@ msgstr ""
msgid "New slot number out of range\n"
msgstr ""
-#: gschem/src/o_undo.c:304
+#: gschem/src/o_undo.c:303
msgid "Undo/Redo disabled in rc file\n"
msgstr "A visszavonás/újra művelet nem használható rc fájlban.\n"
-#: gschem/src/parsecmd.c:47
+#: gschem/src/parsecmd.c:81
#, c-format
msgid ""
-"Usage: %s [OPTIONS] schematic_filename1 ... schematic_filenameN\n"
-" -q Quiet mode\n"
-" -v Verbose mode on\n"
-" -r filename Rc filename\n"
-" -s filename Script (guile) filename\n"
-" -o filename Output filename (for printing)\n"
-" -p Automatically place the window\n"
-" -t Print stroke information\n"
-" -h Help; this message\n"
+"Usage: %s [OPTION ...] [--] [FILE ...]\n"
"\n"
-msgstr ""
-"Használat: %s [OPCI�K] rajz_fájlnév1 ... rajz_fájlnévN\n"
-" -q csendes mód\n"
-" -v közlékeny mód\n"
-" -r fájlnév rc fájlnév\n"
-" -s fájlnév (guile) szkript végrehajtása\n"
-" -o fájlnév kimeneti fájl neve nyomtatáshoz\n"
-" -p ablak automatikus elhelyezése\n"
-" -t Print stroke information\n"
-" -h segÃtség, ez az üzenet\n"
+"Interactively edit gEDA schematics or symbols. If one or more FILEs\n"
+"are specified, open them for editing; otherwise, create a new, empty\n"
+"schematic.\n"
"\n"
+"Options:\n"
+" -q, --quiet Quiet mode.\n"
+" -v, --verbose Verbose mode.\n"
+" -r, --config-file=FILE Additional configuration file to load.\n"
+" -L DIR Add DIR to Scheme search path.\n"
+" -c EXPR Scheme expression to run at startup.\n"
+" -s FILE Scheme script to run at startup.\n"
+" -o, --output=FILE Output filename (for printing).\n"
+" -p Automatically place the window.\n"
+" -V, --version Show version information.\n"
+" -h, --help Help; this message.\n"
+" -- Treat all remaining arguments as filenames.\n"
+"\n"
+"Report bugs to <geda-bug@xxxxxxxx>\n"
+"gEDA/gaf homepage: <http://gpleda.org>\n"
+msgstr ""
+
+#: gschem/src/parsecmd.c:115
+#, c-format
+msgid ""
+"gEDA %s (g%.7s)\n"
+"Copyright (C) 1998-2011 gEDA developers\n"
+"This is free software, and you are welcome to redistribute it under\n"
+"certain conditions. For details, see the file `COPYING', which is\n"
+"included in the gEDA distribution.\n"
+"There is NO WARRANTY, to the extent permitted by law.\n"
+msgstr ""
#: gschem/src/x_attribedit.c:127
#, c-format
@@ -883,56 +881,56 @@ msgstr ""
msgid "Single Attribute Editor"
msgstr ""
-#: gschem/src/x_attribedit.c:358
+#: gschem/src/x_attribedit.c:359
msgid "<b>Edit Attribute</b>"
msgstr "<b>Attribútum szerkesztése</b>"
-#: gschem/src/x_attribedit.c:360
+#: gschem/src/x_attribedit.c:361
msgid "<b>Add Attribute</b>"
msgstr "<b>Attribútum hozzáadása</b>"
-#: gschem/src/x_attribedit.c:376 gschem/src/x_multiattrib.c:1916
+#: gschem/src/x_attribedit.c:377 gschem/src/x_multiattrib.c:1927
msgid "Name:"
msgstr "Név:"
-#: gschem/src/x_attribedit.c:393 gschem/src/x_multiattrib.c:1935
+#: gschem/src/x_attribedit.c:394 gschem/src/x_multiattrib.c:1946
msgid "Value:"
msgstr "�rték:"
-#: gschem/src/x_attribedit.c:409 gschem/src/x_multiattrib.c:1978
+#: gschem/src/x_attribedit.c:410 gschem/src/x_multiattrib.c:1989
msgid "Visible"
msgstr "Látható"
-#: gschem/src/x_attribedit.c:429
+#: gschem/src/x_attribedit.c:430
msgid "Show Value Only"
msgstr "Csak az érték mutatása"
-#: gschem/src/x_attribedit.c:431
+#: gschem/src/x_attribedit.c:432
msgid "Show Name Only"
msgstr "Csak a név mutatása"
-#: gschem/src/x_attribedit.c:433 gschem/src/x_multiattrib.c:1454
+#: gschem/src/x_attribedit.c:434 gschem/src/x_multiattrib.c:1466
msgid "Show Name & Value"
msgstr "Név és érték mutatása"
-#: gschem/src/x_attribedit.c:440
+#: gschem/src/x_attribedit.c:441
msgid "<b>Attach Options</b>"
msgstr ""
-#: gschem/src/x_attribedit.c:455
+#: gschem/src/x_attribedit.c:456
msgid "All"
msgstr "Mind"
-#: gschem/src/x_attribedit.c:463 gschem/src/x_compselect.c:896
-#: gschem/src/x_compselect.c:1010
+#: gschem/src/x_attribedit.c:464 gschem/src/x_compselect.c:904
+#: gschem/src/x_compselect.c:1018
msgid "Components"
msgstr "Alkatrészek"
-#: gschem/src/x_attribedit.c:471 gschem/src/x_window.c:365
+#: gschem/src/x_attribedit.c:472 gschem/src/x_window.c:365
msgid "Nets"
msgstr "�sszeköttetések"
-#: gschem/src/x_attribedit.c:479
+#: gschem/src/x_attribedit.c:480
msgid "Replace existing attributes"
msgstr "MeglevÅ? attribútumok cseréje"
@@ -948,91 +946,91 @@ msgid ""
"duplicate slot may cause problems: [symbolname=%s, number=%d, slot=%d]\n"
msgstr ""
-#: gschem/src/x_autonumber.c:673
+#: gschem/src/x_autonumber.c:675
msgid "No searchstring given in autonumber text.\n"
msgstr "Nincs keresÅ?szöveg megadva az újraszámozáshoz.\n"
-#: gschem/src/x_autonumber.c:725
+#: gschem/src/x_autonumber.c:727
msgid "No '*' or '?' given at the end of the autonumber text.\n"
msgstr "Hiányzik a '*' vagy '?' a szöveg végérÅ?l.\n"
-#: gschem/src/x_autonumber.c:860
+#: gschem/src/x_autonumber.c:862
msgid "Diagonal"
msgstr "�tlós"
-#: gschem/src/x_autonumber.c:861
+#: gschem/src/x_autonumber.c:863
msgid "Top to bottom"
msgstr "FentrÅ?l lefelé"
-#: gschem/src/x_autonumber.c:861
+#: gschem/src/x_autonumber.c:863
msgid "Bottom to top"
msgstr "LentrÅ?l felfelé"
-#: gschem/src/x_autonumber.c:862
+#: gschem/src/x_autonumber.c:864
msgid "Left to right"
msgstr "Balról jobbra"
-#: gschem/src/x_autonumber.c:862
+#: gschem/src/x_autonumber.c:864
msgid "Right to left"
msgstr "Jobbról balra"
-#: gschem/src/x_autonumber.c:863
+#: gschem/src/x_autonumber.c:865
msgid "File order"
msgstr "Fáljsorrend"
-#: gschem/src/x_autonumber.c:1199
+#: gschem/src/x_autonumber.c:1201
msgid "Autonumber text"
msgstr "Automatikus számozás"
-#: gschem/src/x_autonumber.c:1223
+#: gschem/src/x_autonumber.c:1225
msgid "<b>Scope</b>"
msgstr "<b>Hatáskör</b>"
-#: gschem/src/x_autonumber.c:1245
+#: gschem/src/x_autonumber.c:1247
msgid "Search for:"
msgstr "Keresés:"
-#: gschem/src/x_autonumber.c:1259
+#: gschem/src/x_autonumber.c:1261
msgid "Autonumber text in:"
msgstr ""
-#: gschem/src/x_autonumber.c:1266
+#: gschem/src/x_autonumber.c:1268
msgid "Skip numbers found in:"
msgstr ""
-#: gschem/src/x_autonumber.c:1278 gschem/src/x_autonumber.c:1287
+#: gschem/src/x_autonumber.c:1280 gschem/src/x_autonumber.c:1289
msgid "Selected objects"
msgstr "Kiválasztott objektumok"
-#: gschem/src/x_autonumber.c:1279 gschem/src/x_autonumber.c:1288
+#: gschem/src/x_autonumber.c:1281 gschem/src/x_autonumber.c:1290
msgid "Current page"
msgstr "Jelenlegi oldal"
-#: gschem/src/x_autonumber.c:1280 gschem/src/x_autonumber.c:1289
+#: gschem/src/x_autonumber.c:1282 gschem/src/x_autonumber.c:1291
msgid "Whole hierarchy"
msgstr "Teljes hierarchia"
-#: gschem/src/x_autonumber.c:1291
+#: gschem/src/x_autonumber.c:1293
msgid "Overwrite existing numbers"
msgstr "MeglevÅ? számok felülÃrása"
-#: gschem/src/x_autonumber.c:1296
+#: gschem/src/x_autonumber.c:1298
msgid "<b>Options</b>"
msgstr "<b>Opciók</b>"
-#: gschem/src/x_autonumber.c:1318
+#: gschem/src/x_autonumber.c:1320
msgid "Starting number:"
msgstr "KezdÅ?szám:"
-#: gschem/src/x_autonumber.c:1325
+#: gschem/src/x_autonumber.c:1327
msgid "Sort order:"
msgstr "Rendezési sorrend:"
-#: gschem/src/x_autonumber.c:1346
+#: gschem/src/x_autonumber.c:1348
msgid "Remove numbers"
msgstr "Számok törlése"
-#: gschem/src/x_autonumber.c:1350
+#: gschem/src/x_autonumber.c:1352
msgid "Automatic slotting"
msgstr "Automatikus slot-kiválasztás"
@@ -1069,48 +1067,48 @@ msgstr ""
msgid "Tried to get an invalid outline color: %d\n"
msgstr ""
-#: gschem/src/x_compselect.c:1040
+#: gschem/src/x_compselect.c:1048
msgid "Filter:"
msgstr "SzűrÅ?:"
-#: gschem/src/x_compselect.c:1143 gschem/src/x_dialog.c:3663
-#: gschem/src/x_multiattrib.c:1782
+#: gschem/src/x_compselect.c:1151 gschem/src/x_dialog.c:3667
+#: gschem/src/x_multiattrib.c:1793
msgid "Name"
msgstr "Név"
-#: gschem/src/x_compselect.c:1152 gschem/src/x_multiattrib.c:1806
+#: gschem/src/x_compselect.c:1160 gschem/src/x_multiattrib.c:1817
msgid "Value"
msgstr "�rték"
-#: gschem/src/x_compselect.c:1191
+#: gschem/src/x_compselect.c:1199
msgid "Default behavior - reference component"
msgstr "Alapviselkedés - mutató az alkatrészre"
-#: gschem/src/x_compselect.c:1194
+#: gschem/src/x_compselect.c:1202
msgid "Embed component in schematic"
msgstr "Alkatrész beágyazása a rajzba"
-#: gschem/src/x_compselect.c:1197
+#: gschem/src/x_compselect.c:1205
msgid "Include component as individual objects"
msgstr "Alkatrész hozzáadása mint független objektum"
-#: gschem/src/x_compselect.c:1354
+#: gschem/src/x_compselect.c:1362
msgid "Select Component..."
msgstr "Alkatrész kiválasztása..."
-#: gschem/src/x_compselect.c:1377
+#: gschem/src/x_compselect.c:1385
msgid "In Use"
msgstr "Használatban"
-#: gschem/src/x_compselect.c:1381
+#: gschem/src/x_compselect.c:1389
msgid "Libraries"
msgstr "Könyvtárak"
-#: gschem/src/x_compselect.c:1390 gschem/src/x_fileselect.c:122
+#: gschem/src/x_compselect.c:1398 gschem/src/x_fileselect.c:122
msgid "Preview"
msgstr "ElÅ?nézet"
-#: gschem/src/x_compselect.c:1418
+#: gschem/src/x_compselect.c:1426
msgid "Attributes"
msgstr "Attribútumok"
@@ -1169,139 +1167,139 @@ msgstr "Jobb alsó"
msgid "Edit Text Properties"
msgstr "Szövegtulajdonságok szerkesztése"
-#: gschem/src/x_dialog.c:471
+#: gschem/src/x_dialog.c:472
msgid "<b>Text Content</b>"
msgstr ""
-#: gschem/src/x_dialog.c:507
+#: gschem/src/x_dialog.c:508
msgid "<b>Text Properties</b>"
msgstr "<b>Szöveg tulajdonságai</b>"
-#: gschem/src/x_dialog.c:522
+#: gschem/src/x_dialog.c:523
msgid "Color:"
msgstr "SzÃn:"
-#: gschem/src/x_dialog.c:529
+#: gschem/src/x_dialog.c:530
msgid "Size:"
msgstr "Méret:"
-#: gschem/src/x_dialog.c:538
+#: gschem/src/x_dialog.c:539
msgid "Alignment:"
msgstr "IgazÃtás:"
-#: gschem/src/x_dialog.c:587
+#: gschem/src/x_dialog.c:588
msgid "Solid"
msgstr "Folytonos"
-#: gschem/src/x_dialog.c:588
+#: gschem/src/x_dialog.c:589
msgid "Dotted"
msgstr "Pontvonal"
-#: gschem/src/x_dialog.c:589
+#: gschem/src/x_dialog.c:590
msgid "Dashed"
msgstr "Szaggatott"
-#: gschem/src/x_dialog.c:590
+#: gschem/src/x_dialog.c:591
msgid "Center"
msgstr "Középre"
-#: gschem/src/x_dialog.c:591
+#: gschem/src/x_dialog.c:592
msgid "Phantom"
msgstr ""
-#: gschem/src/x_dialog.c:592 gschem/src/x_dialog.c:689
-#: gschem/src/x_dialog.c:698 gschem/src/x_dialog.c:707
-#: gschem/src/x_dialog.c:808 gschem/src/x_dialog.c:810
-#: gschem/src/x_dialog.c:812 gschem/src/x_dialog.c:1038
-#: gschem/src/x_dialog.c:1141 gschem/src/x_dialog.c:1150
-#: gschem/src/x_dialog.c:1159 gschem/src/x_dialog.c:1168
-#: gschem/src/x_dialog.c:1177 gschem/src/x_dialog.c:1290
-#: gschem/src/x_dialog.c:1292 gschem/src/x_dialog.c:1294
-#: gschem/src/x_dialog.c:1296 gschem/src/x_dialog.c:1298
+#: gschem/src/x_dialog.c:593 gschem/src/x_dialog.c:690
+#: gschem/src/x_dialog.c:699 gschem/src/x_dialog.c:708
+#: gschem/src/x_dialog.c:809 gschem/src/x_dialog.c:811
+#: gschem/src/x_dialog.c:813 gschem/src/x_dialog.c:1039
+#: gschem/src/x_dialog.c:1142 gschem/src/x_dialog.c:1151
+#: gschem/src/x_dialog.c:1160 gschem/src/x_dialog.c:1169
+#: gschem/src/x_dialog.c:1178 gschem/src/x_dialog.c:1291
+#: gschem/src/x_dialog.c:1293 gschem/src/x_dialog.c:1295
+#: gschem/src/x_dialog.c:1297 gschem/src/x_dialog.c:1299
msgid "*unchanged*"
msgstr "*változatlan*"
-#: gschem/src/x_dialog.c:916
+#: gschem/src/x_dialog.c:917
msgid "Edit Line Width & Type"
msgstr "Vonalvastagság és tÃpus szerkesztése"
-#: gschem/src/x_dialog.c:955 gschem/src/x_print.c:307
+#: gschem/src/x_dialog.c:956 gschem/src/x_print.c:307
msgid "Type:"
msgstr "TÃpus:"
-#: gschem/src/x_dialog.c:959
+#: gschem/src/x_dialog.c:960
msgid "Width:"
msgstr "Vastagság:"
-#: gschem/src/x_dialog.c:963
+#: gschem/src/x_dialog.c:964
msgid "Dash Length:"
msgstr "Vonalszakasz hossza:"
-#: gschem/src/x_dialog.c:967
+#: gschem/src/x_dialog.c:968
msgid "Dash Space:"
msgstr "Kihagyás hossza:"
-#: gschem/src/x_dialog.c:1034
+#: gschem/src/x_dialog.c:1035
msgid "Hollow"
msgstr "Ã?res"
-#: gschem/src/x_dialog.c:1035
+#: gschem/src/x_dialog.c:1036
msgid "Filled"
msgstr "Kitöltött"
-#: gschem/src/x_dialog.c:1036
+#: gschem/src/x_dialog.c:1037
msgid "Mesh"
msgstr "Háló"
-#: gschem/src/x_dialog.c:1037
+#: gschem/src/x_dialog.c:1038
msgid "Hatch"
msgstr "Sraffozott"
-#: gschem/src/x_dialog.c:1406
+#: gschem/src/x_dialog.c:1407
msgid "Edit Fill Type"
msgstr "Kitöltés szerkesztése"
-#: gschem/src/x_dialog.c:1444
+#: gschem/src/x_dialog.c:1446
msgid "Fill Type:"
msgstr "Kitöltés tÃpusa:"
-#: gschem/src/x_dialog.c:1448
+#: gschem/src/x_dialog.c:1450
msgid "Line Width:"
msgstr "Vonalvastagság:"
-#: gschem/src/x_dialog.c:1452
+#: gschem/src/x_dialog.c:1454
msgid "Angle 1:"
msgstr ""
-#: gschem/src/x_dialog.c:1456
+#: gschem/src/x_dialog.c:1458
msgid "Pitch 1:"
msgstr ""
-#: gschem/src/x_dialog.c:1460
+#: gschem/src/x_dialog.c:1462
msgid "Angle 2:"
msgstr ""
-#: gschem/src/x_dialog.c:1464
+#: gschem/src/x_dialog.c:1466
msgid "Pitch 2:"
msgstr ""
-#: gschem/src/x_dialog.c:1591
+#: gschem/src/x_dialog.c:1593
msgid "Arc Params"
msgstr "�vparaméterek"
-#: gschem/src/x_dialog.c:1631
+#: gschem/src/x_dialog.c:1634
msgid "Arc Radius:"
msgstr ""
-#: gschem/src/x_dialog.c:1639
+#: gschem/src/x_dialog.c:1642
msgid "Start Angle:"
msgstr "KezdÅ?szög:"
-#: gschem/src/x_dialog.c:1647
+#: gschem/src/x_dialog.c:1650
msgid "Degrees of Sweep:"
msgstr "�v szöge:"
-#: gschem/src/x_dialog.c:1764
+#: gschem/src/x_dialog.c:1768
msgid ""
"Offset to translate?\n"
"(0 for origin)"
@@ -1309,199 +1307,199 @@ msgstr ""
"Offszet az eltoláshoz?\n"
"(0 az origóhoz)"
-#: gschem/src/x_dialog.c:1832
+#: gschem/src/x_dialog.c:1836
msgid "Text Size"
msgstr "Betűméret"
-#: gschem/src/x_dialog.c:1862
+#: gschem/src/x_dialog.c:1866
msgid "Enter new text size:"
msgstr "�j betűméret:"
-#: gschem/src/x_dialog.c:1938
+#: gschem/src/x_dialog.c:1942
msgid "Snap Size"
msgstr ""
-#: gschem/src/x_dialog.c:1968
+#: gschem/src/x_dialog.c:1972
msgid "Enter new snap grid spacing:"
msgstr "�j hálóméret:"
-#: gschem/src/x_dialog.c:2045
+#: gschem/src/x_dialog.c:2049
msgid "Edit slot number"
msgstr ""
-#: gschem/src/x_dialog.c:2076
+#: gschem/src/x_dialog.c:2080
msgid "Edit slot number:"
msgstr ""
-#: gschem/src/x_dialog.c:2117
+#: gschem/src/x_dialog.c:2121
#, c-format
msgid "%s%s (%s)"
msgstr ""
-#: gschem/src/x_dialog.c:2140
+#: gschem/src/x_dialog.c:2144
msgid "About gschem"
msgstr "Névjegy"
-#: gschem/src/x_dialog.c:2141
+#: gschem/src/x_dialog.c:2145
msgid "gEDA: GPL Electronic Design Automation"
msgstr ""
-#: gschem/src/x_dialog.c:2142
+#: gschem/src/x_dialog.c:2146
msgid ""
"Copyright © 1998-2009 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
"Copyright © 1998-2009 gEDA Contributors (see ChangeLog for details)"
msgstr ""
-#: gschem/src/x_dialog.c:2201
+#: gschem/src/x_dialog.c:2205
msgid "Coords"
msgstr "Koordináták"
-#: gschem/src/x_dialog.c:2222
+#: gschem/src/x_dialog.c:2226
msgid "Screen"
msgstr "KépernyÅ?"
-#: gschem/src/x_dialog.c:2231
+#: gschem/src/x_dialog.c:2235
msgid "World"
msgstr "Világ"
-#: gschem/src/x_dialog.c:2270
+#: gschem/src/x_dialog.c:2274
msgid "Background"
msgstr ""
-#: gschem/src/x_dialog.c:2276
+#: gschem/src/x_dialog.c:2280
msgid "Net endpoint"
msgstr ""
-#: gschem/src/x_dialog.c:2279
+#: gschem/src/x_dialog.c:2283
msgid "Graphic"
msgstr ""
-#: gschem/src/x_dialog.c:2288
+#: gschem/src/x_dialog.c:2292
msgid "Logic bubble"
msgstr ""
-#: gschem/src/x_dialog.c:2291
+#: gschem/src/x_dialog.c:2295
msgid "Grid point"
msgstr ""
-#: gschem/src/x_dialog.c:2294
+#: gschem/src/x_dialog.c:2298
msgid "Detached attribute"
msgstr ""
-#: gschem/src/x_dialog.c:2297 gschem/src/x_window.c:383
+#: gschem/src/x_dialog.c:2301 gschem/src/x_window.c:383
msgid "Text"
msgstr "Szöveg"
-#: gschem/src/x_dialog.c:2303
+#: gschem/src/x_dialog.c:2307
msgid "Selection"
msgstr ""
-#: gschem/src/x_dialog.c:2306
+#: gschem/src/x_dialog.c:2310
msgid "Bounding box"
msgstr ""
-#: gschem/src/x_dialog.c:2309
+#: gschem/src/x_dialog.c:2313
msgid "Zoom box"
msgstr ""
-#: gschem/src/x_dialog.c:2318
+#: gschem/src/x_dialog.c:2322
msgid "Output background"
msgstr ""
-#: gschem/src/x_dialog.c:2321
+#: gschem/src/x_dialog.c:2325
msgid "Net junction"
msgstr ""
-#: gschem/src/x_dialog.c:2324
+#: gschem/src/x_dialog.c:2328
msgid "Mesh grid major"
msgstr ""
-#: gschem/src/x_dialog.c:2327
+#: gschem/src/x_dialog.c:2331
msgid "Mesh grid minor"
msgstr ""
-#: gschem/src/x_dialog.c:2330
+#: gschem/src/x_dialog.c:2334
msgid "Unknown"
msgstr ""
-#: gschem/src/x_dialog.c:2481
+#: gschem/src/x_dialog.c:2485
#, c-format
msgid "ERROR: NULL object in color_edit_dialog_apply!\n"
msgstr ""
-#: gschem/src/x_dialog.c:2525
+#: gschem/src/x_dialog.c:2529
msgid "Color Edit"
msgstr "SzÃn szerkesztése"
-#: gschem/src/x_dialog.c:2556
+#: gschem/src/x_dialog.c:2560
msgid "Object color:"
msgstr "Objektum szÃne:"
-#: gschem/src/x_dialog.c:2614
+#: gschem/src/x_dialog.c:2618
msgid "Hotkeys"
msgstr "Gyorsbillentyűk"
-#: gschem/src/x_dialog.c:2678
+#: gschem/src/x_dialog.c:2682
msgid "Function"
msgstr "Funkció"
-#: gschem/src/x_dialog.c:2685
+#: gschem/src/x_dialog.c:2689
msgid "Keystroke(s)"
msgstr ""
-#: gschem/src/x_dialog.c:2991
+#: gschem/src/x_dialog.c:2995
msgid "Find Text"
msgstr "Szöveg keresése"
-#: gschem/src/x_dialog.c:3022
+#: gschem/src/x_dialog.c:3026
msgid "Text to find:"
msgstr "KeresendÅ? szöveg:"
-#: gschem/src/x_dialog.c:3032
+#: gschem/src/x_dialog.c:3036
msgid "descend into hierarchy"
msgstr ""
-#: gschem/src/x_dialog.c:3097
+#: gschem/src/x_dialog.c:3101
msgid "Hide Text"
msgstr "Szöveg elrejtése"
-#: gschem/src/x_dialog.c:3128
+#: gschem/src/x_dialog.c:3132
msgid "Hide text starting with:"
msgstr "A következÅ?vel kezdÅ?dÅ? szöveg elrejtése:"
-#: gschem/src/x_dialog.c:3197
+#: gschem/src/x_dialog.c:3201
msgid "Show Text"
msgstr "Szöveg mutatása"
-#: gschem/src/x_dialog.c:3228
+#: gschem/src/x_dialog.c:3232
msgid "Show text starting with:"
msgstr "A következÅ?vel kezdÅ?dÅ? szöveg mutatása:"
-#: gschem/src/x_dialog.c:3685
+#: gschem/src/x_dialog.c:3689
msgid "S_elect the schematics you want to save:"
msgstr "Válaszd ki a menteni kÃvánt rajzot:"
-#: gschem/src/x_dialog.c:3779
+#: gschem/src/x_dialog.c:3784
#, c-format
msgid "Save the changes to schematic \"%s\" before closing?"
msgstr "Elmentsem a(z) \"%s\" rajz változásait bezárás elÅ?tt?"
-#: gschem/src/x_dialog.c:3785
+#: gschem/src/x_dialog.c:3790
#, c-format
msgid ""
"There are %d schematics with unsaved changes. Save changes before closing?"
msgstr ""
"%d megváltoztatott rajz van még megnyitva. Elmentsem Å?ket kilépés elÅ?tt?"
-#: gschem/src/x_dialog.c:3814
+#: gschem/src/x_dialog.c:3819
msgid "If you don't save, all your changes will be permanently lost."
msgstr "Ha nem menti, akkor az összes változás véglegesen elveszik."
-#: gschem/src/x_dialog.c:3834
+#: gschem/src/x_dialog.c:3839
msgid "_Close without saving"
msgstr "_Bezárás mentés nélkül"
-#: gschem/src/x_dialog.c:4170
+#: gschem/src/x_dialog.c:4175
#, c-format
msgid ""
"<span weight=\"bold\" size=\"larger\">The input attribute \"%s\" is invalid\n"
@@ -1512,19 +1510,19 @@ msgid ""
"The value cannot start with a space."
msgstr ""
-#: gschem/src/x_dialog.c:4172
+#: gschem/src/x_dialog.c:4177
msgid "Invalid Attribute"
msgstr "Hibás attribútum"
-#: gschem/src/x_dialog.c:4208
+#: gschem/src/x_dialog.c:4213
msgid "Pin type"
msgstr ""
-#: gschem/src/x_dialog.c:4232
+#: gschem/src/x_dialog.c:4237
msgid "Net pin"
msgstr ""
-#: gschem/src/x_dialog.c:4234
+#: gschem/src/x_dialog.c:4239
msgid "Bus pin (graphical)"
msgstr ""
@@ -1624,12 +1622,12 @@ msgstr "KéptÃpus"
msgid "Write image..."
msgstr "Képfájl Ãrása..."
-#: gschem/src/x_log.c:188
+#: gschem/src/x_log.c:209
msgid "** Invalid UTF-8 in log message. See stderr or gschem.log.\n"
msgstr ""
"** hibás UTF-8 a log üzenetben. Nézd meg az stderr-t vagy a gschem.log-ot.\n"
-#: gschem/src/x_log.c:256
+#: gschem/src/x_log.c:288
msgid "Status"
msgstr "Ã?llapot."
@@ -1705,71 +1703,62 @@ msgstr "/Szimbólum szerkesztése"
msgid "/Up"
msgstr "/Fel"
-#: gschem/src/x_menus.c:321
+#: gschem/src/x_menus.c:323
#, c-format
msgid "Tried to set the sensitivity on non-existent menu item '%s'\n"
msgstr ""
-#: gschem/src/x_menus.c:345
+#: gschem/src/x_menus.c:347
msgid "Popup_menu_item_factory doesn't exist!\n"
msgstr ""
-#: gschem/src/x_menus.c:358
+#: gschem/src/x_menus.c:360
msgid "Tried to set the sensitivity on a non-existent popup menu_item\n"
msgstr ""
-#: gschem/src/x_menus.c:438
-#, c-format
-msgid "Couldn't open file %s\n"
-msgstr "Nem tudom megnyitni a(z) %s fájlt.\n"
-
-#: gschem/src/x_menus.c:495
-msgid "Clear"
-msgstr "Törlés"
-
-#: gschem/src/x_multiattrib.c:911
+#: gschem/src/x_multiattrib.c:915
msgid "Attributes with empty name are not allowed. Please set a name."
msgstr ""
"Név nélküli attribútumok nem használhatóak. Kérlek adj nevet az "
"attribútumnak!"
-#: gschem/src/x_multiattrib.c:1456
+#: gschem/src/x_multiattrib.c:1468
msgid "Show Value only"
msgstr "Csak az érték mutatása"
-#: gschem/src/x_multiattrib.c:1458
+#: gschem/src/x_multiattrib.c:1470
msgid "Show Name only"
msgstr "Csak a név mutatása"
-#: gschem/src/x_multiattrib.c:1486
+#: gschem/src/x_multiattrib.c:1498
msgid "Promote"
msgstr ""
-#: gschem/src/x_multiattrib.c:1490
+#: gschem/src/x_multiattrib.c:1502
msgid "Duplicate"
msgstr "MegkettÅ?zés"
-#: gschem/src/x_multiattrib.c:1708
+#: gschem/src/x_multiattrib.c:1719
msgid "Edit Attributes"
msgstr "Attribútumok szerkesztése"
-#: gschem/src/x_multiattrib.c:1826
+#: gschem/src/x_multiattrib.c:1837
msgid "Vis?"
msgstr "Látható?"
-#: gschem/src/x_multiattrib.c:1844
+#: gschem/src/x_multiattrib.c:1855
msgid "N"
msgstr "N"
-#: gschem/src/x_multiattrib.c:1862
+#: gschem/src/x_multiattrib.c:1873
msgid "V"
msgstr "Ã?"
-#: gschem/src/x_multiattrib.c:1884
+#: gschem/src/x_multiattrib.c:1895
msgid "Show inherited attributes"
msgstr ""
-#: gschem/src/x_multiattrib.c:1900
+#: gschem/src/x_multiattrib.c:1911
msgid "Add Attribute"
msgstr "Attribútum hozzáadása"
@@ -1793,23 +1782,23 @@ msgstr "Lap bezárása"
msgid "Discard Page"
msgstr "Rajz eldobása"
-#: gschem/src/x_pagesel.c:376
+#: gschem/src/x_pagesel.c:375
msgid "Page Manager"
msgstr "Oldalkiválasztó"
-#: gschem/src/x_pagesel.c:432
+#: gschem/src/x_pagesel.c:431
msgid "Filename"
msgstr "Fájlnév"
-#: gschem/src/x_pagesel.c:448
+#: gschem/src/x_pagesel.c:447
msgid "Changed"
msgstr "MódosÃtva"
-#: gschem/src/x_pagesel.c:468
+#: gschem/src/x_pagesel.c:467
msgid "Right click on the filename for more options..."
msgstr "Kattints a jobb egérgombbal a fájlnével a további opciókért..."
-#: gschem/src/x_preview.c:234
+#: gschem/src/x_preview.c:233
msgid "Preview Buffer"
msgstr ""
@@ -1865,16 +1854,16 @@ msgstr "Fájl:"
msgid "Command:"
msgstr "Parancs:"
-#: gschem/src/x_print.c:741
+#: gschem/src/x_print.c:745
msgid "No print destination specified\n"
msgstr "Nincs megadva a nyomtatási cél!\n"
-#: gschem/src/x_print.c:748
+#: gschem/src/x_print.c:752
#, c-format
msgid "Cannot print current schematic to [%s]\n"
msgstr "Nem tudom [%s]-ba nyomtatni a rajzot\n"
-#: gschem/src/x_print.c:757
+#: gschem/src/x_print.c:761
#, c-format
msgid ""
"Error printing to file '%s'\n"
@@ -1883,7 +1872,7 @@ msgstr ""
"Hiba a(z) '%s' fájlba történÅ? nyomtatás közben.\n"
"Olvasd el a log ablakban leÃrtakat a további információkért."
-#: gschem/src/x_print.c:764
+#: gschem/src/x_print.c:768
#, c-format
msgid "Printed current schematic to [%s]\n"
msgstr "A rajz kinyomtatva a(z) [%s] fájlba.\n"
@@ -1892,6 +1881,11 @@ msgstr "A rajz kinyomtatva a(z) [%s] fájlba.\n"
msgid "Execute Script..."
msgstr "Szkript végrehajtása"
+#: gschem/src/x_script.c:66
+#, c-format
+msgid "Executing guile script [%s]\n"
+msgstr "[%s] guile szkript végrehajtása.\n"
+
#: gschem/src/x_window.c:81
#, c-format
msgid "Couldn't allocate gc\n"
@@ -2002,35 +1996,35 @@ msgstr "A fájl betöltése nem sikerült."
msgid "New file [%s]\n"
msgstr "�j fájl: [%s]\n"
-#: gschem/src/x_window.c:857
+#: gschem/src/x_window.c:855
#, c-format
msgid "Could NOT save page [%s]\n"
msgstr "A [%s] rajz mentése nem sikerült.\n"
-#: gschem/src/x_window.c:858
+#: gschem/src/x_window.c:856
msgid "Error while trying to save"
msgstr "Hiba mentés közben"
-#: gschem/src/x_window.c:867
+#: gschem/src/x_window.c:865
#, c-format
msgid "Saved as [%s]\n"
msgstr "[%s]-ként elmentve.\n"
-#: gschem/src/x_window.c:869
+#: gschem/src/x_window.c:867
#, c-format
msgid "Saved [%s]\n"
msgstr "[%s] elmentve.\n"
-#: gschem/src/x_window.c:871
+#: gschem/src/x_window.c:869
msgid "Saved"
msgstr "Elmentve"
-#: gschem/src/x_window.c:945
+#: gschem/src/x_window.c:943
#, c-format
msgid "Discarding page [%s]\n"
msgstr "A(z) [%s] rajz eldobása\n"
-#: gschem/src/x_window.c:945
+#: gschem/src/x_window.c:943
#, c-format
msgid "Closing [%s]\n"
msgstr "[%s] bezárása\n"
@@ -2073,7 +2067,7 @@ msgstr "Mentés másként"
msgid "Save All"
msgstr "Mind mentése"
-#: gschem/lib/system-gschemrc.scm:1386 gschem/lib/system-gschemrc.scm:1477
+#: gschem/lib/system-gschemrc.scm:1386 gschem/lib/system-gschemrc.scm:1478
msgid "_Revert"
msgstr "_VisszaállÃtás"
@@ -2085,7 +2079,7 @@ msgstr "_Nyomtatás�"
msgid "Write _image..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1393 gschem/lib/system-gschemrc.scm:1478
+#: gschem/lib/system-gschemrc.scm:1393 gschem/lib/system-gschemrc.scm:1479
msgid "_Close"
msgstr "_Bezárás"
@@ -2117,391 +2111,435 @@ msgstr "Beillesztés (_P)"
msgid "_Delete"
msgstr "Törlés (_D)"
-#: gschem/lib/system-gschemrc.scm:1412
+#: gschem/lib/system-gschemrc.scm:1409
+#, fuzzy
+msgid "Select All"
+msgstr "Kiválasztás"
+
+#: gschem/lib/system-gschemrc.scm:1410
+#, fuzzy
+msgid "Deselect"
+msgstr "Kiválasztás"
+
+#: gschem/lib/system-gschemrc.scm:1414
msgid "Rotate 90 Mode"
msgstr "Elforgatás 90 fokkal"
-#: gschem/lib/system-gschemrc.scm:1415
+#: gschem/lib/system-gschemrc.scm:1417
msgid "Edit..."
msgstr "Szerkesztés..."
-#: gschem/lib/system-gschemrc.scm:1416
+#: gschem/lib/system-gschemrc.scm:1418
msgid "Edit Text..."
msgstr "Szöveg szerkesztése..."
-#: gschem/lib/system-gschemrc.scm:1417
+#: gschem/lib/system-gschemrc.scm:1419
msgid "Slot..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1418
+#: gschem/lib/system-gschemrc.scm:1420
msgid "Color..."
msgstr "SzÃn..."
-#: gschem/lib/system-gschemrc.scm:1419
+#: gschem/lib/system-gschemrc.scm:1421
msgid "Line Width & Type..."
msgstr "Vonalszélesség és tÃpus"
-#: gschem/lib/system-gschemrc.scm:1420
+#: gschem/lib/system-gschemrc.scm:1422
msgid "Fill Type..."
msgstr "Kitöltés tÃpusa"
-#: gschem/lib/system-gschemrc.scm:1421
+#: gschem/lib/system-gschemrc.scm:1423
msgid "Symbol Translate..."
msgstr "Szimbólum áthelyezése"
-#: gschem/lib/system-gschemrc.scm:1425
+#: gschem/lib/system-gschemrc.scm:1427
msgid "Invoke Macro"
msgstr "Makró végrehajtása"
-#: gschem/lib/system-gschemrc.scm:1426
+#: gschem/lib/system-gschemrc.scm:1428
msgid "Embed Component/Picture"
msgstr "Alkatrész/kép beágyazása"
-#: gschem/lib/system-gschemrc.scm:1427
+#: gschem/lib/system-gschemrc.scm:1429
msgid "Unembed Component/Picture"
msgstr "Alkatrész/kép beágyazásának megszüntetése"
-#: gschem/lib/system-gschemrc.scm:1428
+#: gschem/lib/system-gschemrc.scm:1430
msgid "Update Component"
msgstr "Alkatrész frissÃtése"
-#: gschem/lib/system-gschemrc.scm:1429
+#: gschem/lib/system-gschemrc.scm:1431
msgid "Show/Hide Inv Text"
msgstr "Láthatatlan szöveg mutatása/elrejtése"
-#: gschem/lib/system-gschemrc.scm:1430
-msgid "Make Inv Text Vis"
-msgstr "Láthatatlan szöveg láthatóvá tétele"
-
-#: gschem/lib/system-gschemrc.scm:1436
+#: gschem/lib/system-gschemrc.scm:1437
msgid "Copy into 1"
msgstr "Másolás 1-be"
-#: gschem/lib/system-gschemrc.scm:1437
+#: gschem/lib/system-gschemrc.scm:1438
msgid "Copy into 2"
msgstr "Másolás 2-be"
-#: gschem/lib/system-gschemrc.scm:1438
+#: gschem/lib/system-gschemrc.scm:1439
msgid "Copy into 3"
msgstr "Másolás 3-ba"
-#: gschem/lib/system-gschemrc.scm:1439
+#: gschem/lib/system-gschemrc.scm:1440
msgid "Copy into 4"
msgstr "Másolás 4-be"
-#: gschem/lib/system-gschemrc.scm:1440
+#: gschem/lib/system-gschemrc.scm:1441
msgid "Copy into 5"
msgstr "Másolás 5-be"
-#: gschem/lib/system-gschemrc.scm:1441
+#: gschem/lib/system-gschemrc.scm:1442
msgid "Cut into 1"
msgstr "Kivágás 1-be"
-#: gschem/lib/system-gschemrc.scm:1442
+#: gschem/lib/system-gschemrc.scm:1443
msgid "Cut into 2"
msgstr "Kivágás 2-be"
-#: gschem/lib/system-gschemrc.scm:1443
+#: gschem/lib/system-gschemrc.scm:1444
msgid "Cut into 3"
msgstr "Kivágás 3-ba"
-#: gschem/lib/system-gschemrc.scm:1444
+#: gschem/lib/system-gschemrc.scm:1445
msgid "Cut into 4"
msgstr "Kivágás 4-be"
-#: gschem/lib/system-gschemrc.scm:1445
+#: gschem/lib/system-gschemrc.scm:1446
msgid "Cut into 5"
msgstr "Kivágás 5-be"
-#: gschem/lib/system-gschemrc.scm:1446
+#: gschem/lib/system-gschemrc.scm:1447
msgid "Paste from 1"
msgstr "Beillesztés 1-bÅ?l"
-#: gschem/lib/system-gschemrc.scm:1447
+#: gschem/lib/system-gschemrc.scm:1448
msgid "Paste from 2"
msgstr "Beillesztés 2-bÅ?l"
-#: gschem/lib/system-gschemrc.scm:1448
+#: gschem/lib/system-gschemrc.scm:1449
msgid "Paste from 3"
msgstr "Beillesztés 3-ból"
-#: gschem/lib/system-gschemrc.scm:1449
+#: gschem/lib/system-gschemrc.scm:1450
msgid "Paste from 4"
msgstr "Beillesztés 4-bÅ?l"
-#: gschem/lib/system-gschemrc.scm:1450
+#: gschem/lib/system-gschemrc.scm:1451
msgid "Paste from 5"
msgstr "Beillesztés 5-bÅ?l"
-#: gschem/lib/system-gschemrc.scm:1456
+#: gschem/lib/system-gschemrc.scm:1457
msgid "_Redraw"
msgstr "�jrarajzolás"
-#: gschem/lib/system-gschemrc.scm:1457
+#: gschem/lib/system-gschemrc.scm:1458
msgid "_Pan"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1458
+#: gschem/lib/system-gschemrc.scm:1459
msgid "Zoom _Box"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1459
+#: gschem/lib/system-gschemrc.scm:1460
msgid "Zoom _Extents"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1460
+#: gschem/lib/system-gschemrc.scm:1461
msgid "Zoom _In"
msgstr "NagyÃtás"
-#: gschem/lib/system-gschemrc.scm:1461
+#: gschem/lib/system-gschemrc.scm:1462
msgid "Zoom _Out"
msgstr "KicsinyÃtés"
-#: gschem/lib/system-gschemrc.scm:1462
+#: gschem/lib/system-gschemrc.scm:1463
msgid "Zoom _Full"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1464
+#: gschem/lib/system-gschemrc.scm:1465
msgid "_Dark color scheme"
msgstr "Sötét szÃnséma"
-#: gschem/lib/system-gschemrc.scm:1465
+#: gschem/lib/system-gschemrc.scm:1466
msgid "_Light color scheme"
msgstr "Világos szÃnséma"
-#: gschem/lib/system-gschemrc.scm:1466
+#: gschem/lib/system-gschemrc.scm:1467
#, fuzzy
msgid "B_W color scheme"
msgstr "Sötét szÃnséma"
-#: gschem/lib/system-gschemrc.scm:1473
+#: gschem/lib/system-gschemrc.scm:1474
msgid "_Manager..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1474
+#: gschem/lib/system-gschemrc.scm:1475
msgid "_Previous"
msgstr "ElÅ?zÅ?"
-#: gschem/lib/system-gschemrc.scm:1475
+#: gschem/lib/system-gschemrc.scm:1476
msgid "_Next"
msgstr "KövetkezÅ?"
-#: gschem/lib/system-gschemrc.scm:1476
+#: gschem/lib/system-gschemrc.scm:1477
msgid "Ne_w"
msgstr "Ã?j"
-#: gschem/lib/system-gschemrc.scm:1480
+#: gschem/lib/system-gschemrc.scm:1481
msgid "_Discard"
msgstr "El_dobás"
-#: gschem/lib/system-gschemrc.scm:1486
+#: gschem/lib/system-gschemrc.scm:1487
msgid "_Component..."
msgstr "Alkatrész"
-#: gschem/lib/system-gschemrc.scm:1487
+#: gschem/lib/system-gschemrc.scm:1488
msgid "_Net"
msgstr "_Net"
-#: gschem/lib/system-gschemrc.scm:1488
+#: gschem/lib/system-gschemrc.scm:1489
msgid "B_us"
msgstr "B_usz"
-#: gschem/lib/system-gschemrc.scm:1489
+#: gschem/lib/system-gschemrc.scm:1490
msgid "_Attribute..."
msgstr "_Attribútum"
-#: gschem/lib/system-gschemrc.scm:1490
+#: gschem/lib/system-gschemrc.scm:1491
msgid "_Text..."
msgstr "Szöveg"
-#: gschem/lib/system-gschemrc.scm:1492
+#: gschem/lib/system-gschemrc.scm:1493
msgid "_Line"
msgstr "Vona_l"
-#: gschem/lib/system-gschemrc.scm:1493
+#: gschem/lib/system-gschemrc.scm:1494
msgid "_Box"
msgstr "Do_boz"
-#: gschem/lib/system-gschemrc.scm:1494
+#: gschem/lib/system-gschemrc.scm:1495
msgid "C_ircle"
msgstr "Kör"
-#: gschem/lib/system-gschemrc.scm:1495
+#: gschem/lib/system-gschemrc.scm:1496
msgid "A_rc"
msgstr "Kö_rÃv"
-#: gschem/lib/system-gschemrc.scm:1496
+#: gschem/lib/system-gschemrc.scm:1497
msgid "_Pin"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1497
+#: gschem/lib/system-gschemrc.scm:1498
msgid "Pictu_re..."
msgstr "Kép"
-#: gschem/lib/system-gschemrc.scm:1503
+#: gschem/lib/system-gschemrc.scm:1504
msgid "_Down Schematic"
msgstr "Kapcsolási rajz szerkesztése"
-#: gschem/lib/system-gschemrc.scm:1504
+#: gschem/lib/system-gschemrc.scm:1505
msgid "Down _Symbol"
msgstr "Szimbólum szerkesztése"
-#: gschem/lib/system-gschemrc.scm:1505
+#: gschem/lib/system-gschemrc.scm:1506
msgid "_Up"
msgstr "Vissza a rajzhoz"
-#: gschem/lib/system-gschemrc.scm:1506
+#: gschem/lib/system-gschemrc.scm:1507
msgid "D_ocumentation..."
msgstr "D_okumentáció"
-#: gschem/lib/system-gschemrc.scm:1512
+#: gschem/lib/system-gschemrc.scm:1513
msgid "_Attach"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1513
+#: gschem/lib/system-gschemrc.scm:1514
msgid "_Detach"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1514
+#: gschem/lib/system-gschemrc.scm:1515
msgid "Show _Value"
msgstr "�rték mutatása"
-#: gschem/lib/system-gschemrc.scm:1515
+#: gschem/lib/system-gschemrc.scm:1516
msgid "Show _Name"
msgstr "Név mutatása"
-#: gschem/lib/system-gschemrc.scm:1516
+#: gschem/lib/system-gschemrc.scm:1517
msgid "Show _Both"
msgstr "MindkettÅ? mutatása"
-#: gschem/lib/system-gschemrc.scm:1517
+#: gschem/lib/system-gschemrc.scm:1518
msgid "_Toggle Visibility"
msgstr "Lá_thatóság váltása"
-#: gschem/lib/system-gschemrc.scm:1519
+#: gschem/lib/system-gschemrc.scm:1520
msgid "_Find Specific Text..."
msgstr "Szöveg keresése"
-#: gschem/lib/system-gschemrc.scm:1520
+#: gschem/lib/system-gschemrc.scm:1521
msgid "_Hide Specific Text..."
msgstr "Szöveg elrejtése"
-#: gschem/lib/system-gschemrc.scm:1521
+#: gschem/lib/system-gschemrc.scm:1522
msgid "_Show Specific Text..."
msgstr "Szöveg mutatása"
-#: gschem/lib/system-gschemrc.scm:1522
+#: gschem/lib/system-gschemrc.scm:1523
msgid "A_utonumber Text..."
msgstr "Szöveg automatikus számozása"
-#: gschem/lib/system-gschemrc.scm:1528
+#: gschem/lib/system-gschemrc.scm:1529
msgid "_Text Size..."
msgstr "Szöveg mére_te"
-#: gschem/lib/system-gschemrc.scm:1529
+#: gschem/lib/system-gschemrc.scm:1530
msgid "Cycle _grid styles"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1530
+#: gschem/lib/system-gschemrc.scm:1531
msgid "Toggle _Snap On/Off"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1531
+#: gschem/lib/system-gschemrc.scm:1532
msgid "Snap Grid S_pacing..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1532
+#: gschem/lib/system-gschemrc.scm:1533
msgid "Scale _up Grid Spacing"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1534
+#: gschem/lib/system-gschemrc.scm:1535
msgid "Scale _down Grid Spacing"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1536
+#: gschem/lib/system-gschemrc.scm:1537
msgid "Toggle _Outline/Box"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1538
+#: gschem/lib/system-gschemrc.scm:1539
msgid "Toggle Net _Rubberband"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1539
+#: gschem/lib/system-gschemrc.scm:1540
msgid "Toggle _Magnetic Net"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1540
+#: gschem/lib/system-gschemrc.scm:1541
msgid "Show _Log Window..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1542
+#: gschem/lib/system-gschemrc.scm:1543
msgid "Show _Coord Window..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1558
+#: gschem/lib/system-gschemrc.scm:1559
msgid "gEDA Docu_mentation..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1559
+#: gschem/lib/system-gschemrc.scm:1560
msgid "gschem _FAQ..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1560
+#: gschem/lib/system-gschemrc.scm:1561
msgid "gEDA _Wiki..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1561
+#: gschem/lib/system-gschemrc.scm:1562
msgid "Component D_ocumentation..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1563
+#: gschem/lib/system-gschemrc.scm:1564
msgid "_Hotkeys..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1564
+#: gschem/lib/system-gschemrc.scm:1565
msgid "_About..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1570
+#: gschem/lib/system-gschemrc.scm:1571
msgid "_File"
msgstr "_Fájl"
-#: gschem/lib/system-gschemrc.scm:1571
+#: gschem/lib/system-gschemrc.scm:1572
msgid "_Edit"
msgstr "Szerkesztés"
-#: gschem/lib/system-gschemrc.scm:1572
+#: gschem/lib/system-gschemrc.scm:1573
msgid "_Buffer"
msgstr "_Buffer"
-#: gschem/lib/system-gschemrc.scm:1573
+#: gschem/lib/system-gschemrc.scm:1574
msgid "_View"
msgstr "Nézet"
-#: gschem/lib/system-gschemrc.scm:1574
+#: gschem/lib/system-gschemrc.scm:1575
msgid "_Page"
msgstr "Oldal"
-#: gschem/lib/system-gschemrc.scm:1575
+#: gschem/lib/system-gschemrc.scm:1576
msgid "_Add"
msgstr "Hozzá_adás"
-#: gschem/lib/system-gschemrc.scm:1576
+#: gschem/lib/system-gschemrc.scm:1577
msgid "Hie_rarchy"
msgstr "Hie_rarchia"
-#: gschem/lib/system-gschemrc.scm:1577
+#: gschem/lib/system-gschemrc.scm:1578
msgid "A_ttributes"
msgstr "A_ttribútumok"
-#: gschem/lib/system-gschemrc.scm:1578
+#: gschem/lib/system-gschemrc.scm:1579
msgid "_Options"
msgstr "BeállÃtás_ok"
-#: gschem/lib/system-gschemrc.scm:1579
+#: gschem/lib/system-gschemrc.scm:1580
msgid "_Help"
msgstr "SegÃtség"
+#~ msgid "Scheme directory NOT set!\n"
+#~ msgstr "A scheme könyvtár nincs beállÃtva!\n"
+
+#~ msgid "MakeVisible"
+#~ msgstr "Láthatóvá tétel"
+
+#~ msgid ""
+#~ "Usage: %s [OPTIONS] schematic_filename1 ... schematic_filenameN\n"
+#~ " -q Quiet mode\n"
+#~ " -v Verbose mode on\n"
+#~ " -r filename Rc filename\n"
+#~ " -s filename Script (guile) filename\n"
+#~ " -o filename Output filename (for printing)\n"
+#~ " -p Automatically place the window\n"
+#~ " -t Print stroke information\n"
+#~ " -h Help; this message\n"
+#~ "\n"
+#~ msgstr ""
+#~ "Használat: %s [OPCI�K] rajz_fájlnév1 ... rajz_fájlnévN\n"
+#~ " -q csendes mód\n"
+#~ " -v közlékeny mód\n"
+#~ " -r fájlnév rc fájlnév\n"
+#~ " -s fájlnév (guile) szkript végrehajtása\n"
+#~ " -o fájlnév kimeneti fájl neve nyomtatáshoz\n"
+#~ " -p ablak automatikus elhelyezése\n"
+#~ " -t Print stroke information\n"
+#~ " -h segÃtség, ez az üzenet\n"
+#~ "\n"
+
+#~ msgid "Couldn't open file %s\n"
+#~ msgstr "Nem tudom megnyitni a(z) %s fájlt.\n"
+
+#~ msgid "Clear"
+#~ msgstr "Törlés"
+
+#~ msgid "Make Inv Text Vis"
+#~ msgstr "Láthatatlan szöveg láthatóvá tétele"
+
#~ msgid "About..."
#~ msgstr "Névjegy�"
diff --git a/gschem/po/it.po b/gschem/po/it.po
index d0fea1e..bfae2b6 100644
--- a/gschem/po/it.po
+++ b/gschem/po/it.po
@@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2010-11-07 13:37+0000\n"
+"POT-Creation-Date: 2011-01-16 00:11-0500\n"
"PO-Revision-Date: 2010-02-14 01:07+0000\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -24,17 +24,17 @@ msgid "Zoom too small! Cannot zoom further.\n"
msgstr ""
"Eccessiva riduzione dell'immagine! Non è possibile ridurla ulteriormente.\n"
-#: gschem/src/g_funcs.c:339 gschem/src/i_callbacks.c:68
+#: gschem/src/g_funcs.c:347 gschem/src/i_callbacks.c:68
#, c-format
msgid "Could not fork\n"
msgstr "Impossibile creare un nuovo processo\n"
-#: gschem/src/g_funcs.c:355 gschem/src/i_callbacks.c:78
+#: gschem/src/g_funcs.c:363 gschem/src/i_callbacks.c:78
#, c-format
msgid "Could not invoke %s\n"
msgstr "Non è possibile invocare %s\n"
-#: gschem/src/g_funcs.c:361 gschem/src/i_callbacks.c:82
+#: gschem/src/g_funcs.c:369 gschem/src/i_callbacks.c:82
msgid "Documentation commands not supported under MinGW.\n"
msgstr "Comandi documentazione non supportati sotto MinGW.\n"
@@ -132,12 +132,12 @@ msgstr "Guadagno non valido [%d] passato a zoom-gain\n"
msgid "Invalid number of steps [%d] scrollpan-steps\n"
msgstr "Numero passi non valido [%d] scrollpan-steps\n"
-#: gschem/src/gschem.c:184
+#: gschem/src/gschem.c:188
#, c-format
msgid "gEDA/gschem version %s%s.%s\n"
msgstr "gEDA/gschem versione %s%s.%s\n"
-#: gschem/src/gschem.c:187
+#: gschem/src/gschem.c:191
msgid ""
"gEDA/gschem comes with ABSOLUTELY NO WARRANTY; see COPYING for more "
"details.\n"
@@ -145,14 +145,14 @@ msgstr ""
"gEDA/gschem viene rilasciato SENZA GARANZIA ALCUNA A CAUSA DEL SUO SVILUPPO "
"IN FASE ALFA; leggere il file COPYING per ulteriori informazioni.\n"
-#: gschem/src/gschem.c:189
+#: gschem/src/gschem.c:193
msgid ""
"This is free software, and you are welcome to redistribute it under certain\n"
msgstr ""
"Questo software è rilasciato sotto licenza GPL e può essere ridistribuito "
"sotto determinate\n"
-#: gschem/src/gschem.c:191
+#: gschem/src/gschem.c:195
msgid ""
"conditions; please see the COPYING file for more details.\n"
"\n"
@@ -160,17 +160,17 @@ msgstr ""
"condizioni; per favore leggi il file COPYNG per ulteriori dettagli.\n"
"\n"
-#: gschem/src/gschem.c:194
+#: gschem/src/gschem.c:198
#, c-format
msgid "This is the MINGW32 port.\n"
msgstr "Port per MINGW32.\n"
-#: gschem/src/gschem.c:198
+#: gschem/src/gschem.c:202
#, c-format
msgid "Current locale settings: %s\n"
msgstr "Impostazioni locali correnti: %s\n"
-#: gschem/src/gschem.c:213
+#: gschem/src/gschem.c:218
msgid ""
"You must set the GEDADATA environment variable!\n"
"\n"
@@ -183,31 +183,21 @@ msgstr ""
"d'ambiente \n"
"GEDADATA in modo che punti alla locazione corretta.\n"
-#: gschem/src/gschem.c:248
+#: gschem/src/gschem.c:256
#, c-format
msgid "Couldn't find init scm file [%s]\n"
msgstr "Impossibile trovare il file di inizializzazione scm [%s]\n"
-#: gschem/src/gschem.c:252
+#: gschem/src/gschem.c:260
#, c-format
msgid "Read init scm file [%s]\n"
msgstr "Lettura del file init scm [%s]\n"
-#: gschem/src/gschem.c:256
+#: gschem/src/gschem.c:264
#, c-format
msgid "Failed to read init scm file [%s]\n"
msgstr "Fallita la lettura del file init scm [%s]\n"
-#: gschem/src/gschem.c:317
-#, c-format
-msgid "Scheme directory NOT set!\n"
-msgstr "Cartelle degli schemi non impostata!\n"
-
-#: gschem/src/gschem.c:324 gschem/src/x_script.c:66
-#, c-format
-msgid "Executing guile script [%s]\n"
-msgstr "Esecuzione dello script guile [%s]\n"
-
#: gschem/src/gschem_cairo.c:310
#, c-format
msgid "Unknown end for line (%d)\n"
@@ -231,11 +221,11 @@ msgstr "Scelta Componente"
msgid "Text Mode"
msgstr "Modalità Testo"
-#: gschem/src/i_basic.c:84 gschem/lib/system-gschemrc.scm:1409
+#: gschem/src/i_basic.c:84 gschem/lib/system-gschemrc.scm:1411
msgid "Copy Mode"
msgstr "Modalità copia"
-#: gschem/src/i_basic.c:87 gschem/lib/system-gschemrc.scm:1411
+#: gschem/src/i_basic.c:87 gschem/lib/system-gschemrc.scm:1413
msgid "Move Mode"
msgstr "Modalità spostamento"
@@ -243,7 +233,7 @@ msgstr "Modalità spostamento"
msgid "Rotate Mode"
msgstr "Modalità Rotazione"
-#: gschem/src/i_basic.c:91 gschem/lib/system-gschemrc.scm:1413
+#: gschem/src/i_basic.c:91 gschem/lib/system-gschemrc.scm:1415
msgid "Mirror Mode"
msgstr "Modalità specchio"
@@ -296,22 +286,22 @@ msgstr "Modalità Arco"
msgid "Pin Mode"
msgstr "Modalità Pin"
-#: gschem/src/i_basic.c:135 gschem/src/i_callbacks.c:544
-#: gschem/src/i_callbacks.c:568
+#: gschem/src/i_basic.c:135 gschem/src/i_callbacks.c:576
+#: gschem/src/i_callbacks.c:600
msgid "Copy"
msgstr "Copia"
-#: gschem/src/i_basic.c:137 gschem/src/i_callbacks.c:634
-#: gschem/src/i_callbacks.c:658
+#: gschem/src/i_basic.c:137 gschem/src/i_callbacks.c:666
+#: gschem/src/i_callbacks.c:690
msgid "Move"
msgstr "Sposta"
-#: gschem/src/i_basic.c:139 gschem/src/i_callbacks.c:589
-#: gschem/src/i_callbacks.c:613
+#: gschem/src/i_basic.c:139 gschem/src/i_callbacks.c:621
+#: gschem/src/i_callbacks.c:645
msgid "Multiple Copy"
msgstr "Copia Multipla"
-#: gschem/src/i_basic.c:142 gschem/lib/system-gschemrc.scm:1410
+#: gschem/src/i_basic.c:142 gschem/lib/system-gschemrc.scm:1412
msgid "Multiple Copy Mode"
msgstr "Modalità di copiatura multipla"
@@ -331,7 +321,7 @@ msgstr "Resnap Attivo"
msgid "Action"
msgstr "Azione"
-#: gschem/src/i_basic.c:260 gschem/src/x_dialog.c:2312
+#: gschem/src/i_basic.c:260 gschem/src/x_dialog.c:2316
#: gschem/src/x_window.c:491
msgid "Stroke"
msgstr "Tratto"
@@ -362,7 +352,7 @@ msgstr "Griglia(%s, %s)"
msgid "Documentation for [%s,%s,%s,%s]\n"
msgstr "Documentazione per [%s,%s,%s,%s]\n"
-#: gschem/src/i_callbacks.c:123 gschem/src/i_callbacks.c:1699
+#: gschem/src/i_callbacks.c:123 gschem/src/i_callbacks.c:1706
#, c-format
msgid "New page created [%s]\n"
msgstr "Nuova Pagina Creata [%s]\n"
@@ -384,71 +374,71 @@ msgstr "Salvato Tutto"
msgid "Closing Window\n"
msgstr "Chiusura Finestra\n"
-#: gschem/src/i_callbacks.c:549 gschem/src/i_callbacks.c:594
-#: gschem/src/i_callbacks.c:639
+#: gschem/src/i_callbacks.c:581 gschem/src/i_callbacks.c:626
+#: gschem/src/i_callbacks.c:671
msgid "Select objs first"
msgstr "Seleziona prima un oggetto"
-#: gschem/src/i_callbacks.c:678 gschem/src/x_multiattrib.c:1491
+#: gschem/src/i_callbacks.c:710 gschem/src/x_multiattrib.c:1503
msgid "Delete"
msgstr "Cancella"
-#: gschem/src/i_callbacks.c:703
+#: gschem/src/i_callbacks.c:735
msgid "Edit"
msgstr "Modifica"
-#: gschem/src/i_callbacks.c:718
+#: gschem/src/i_callbacks.c:750
msgid "Edit pin type"
msgstr "Modifica tipo di pin"
-#: gschem/src/i_callbacks.c:737
+#: gschem/src/i_callbacks.c:769
msgid "Edit Text"
msgstr "Modifica Testo"
-#: gschem/src/i_callbacks.c:760
+#: gschem/src/i_callbacks.c:792
msgid "Slot"
msgstr "Slot"
-#: gschem/src/i_callbacks.c:777
+#: gschem/src/i_callbacks.c:809
msgid "Color"
msgstr "Colore"
-#: gschem/src/i_callbacks.c:814 gschem/src/i_callbacks.c:859
+#: gschem/src/i_callbacks.c:846 gschem/src/i_callbacks.c:891
msgid "Rotate"
msgstr "Ruota"
-#: gschem/src/i_callbacks.c:882 gschem/src/i_callbacks.c:907
+#: gschem/src/i_callbacks.c:913 gschem/src/i_callbacks.c:938
msgid "Mirror"
msgstr "Specchio"
-#: gschem/src/i_callbacks.c:928 gschem/src/x_dialog.c:2315
-#: gschem/lib/system-gschemrc.scm:1422
+#: gschem/src/i_callbacks.c:959 gschem/src/x_dialog.c:2319
+#: gschem/lib/system-gschemrc.scm:1424
msgid "Lock"
msgstr "Blocca"
-#: gschem/src/i_callbacks.c:946 gschem/lib/system-gschemrc.scm:1423
+#: gschem/src/i_callbacks.c:977 gschem/lib/system-gschemrc.scm:1425
msgid "Unlock"
msgstr "Sblocca"
-#: gschem/src/i_callbacks.c:964 gschem/src/x_dialog.c:1734
+#: gschem/src/i_callbacks.c:995 gschem/src/x_dialog.c:1737
msgid "Translate"
msgstr "Converti"
-#: gschem/src/i_callbacks.c:967
+#: gschem/src/i_callbacks.c:998
msgid "WARNING: Do not translate with snap off!\n"
msgstr "ATTENZIONE: Non effettuare la conversione in modalità snap off!\n"
-#: gschem/src/i_callbacks.c:968
+#: gschem/src/i_callbacks.c:999
msgid "WARNING: Turning snap on and continuing with translate.\n"
msgstr ""
"ATTENZIONE: Sei in modalità snap off; passa prima in modalità snap on e poi "
"continua con la conversione.\n"
-#: gschem/src/i_callbacks.c:975
+#: gschem/src/i_callbacks.c:1006
msgid "WARNING: Snap grid size is not equal to 100!\n"
msgstr "ATTENZIONE: L'ampiezza snap gride non è uguale a 100!\n"
-#: gschem/src/i_callbacks.c:977
+#: gschem/src/i_callbacks.c:1008
msgid ""
"WARNING: If you are translating a symbol to the origin, the snap grid size "
"should be set to 100\n"
@@ -456,176 +446,172 @@ msgstr ""
"ATTENZIONE: se stai convertendo un simbolo dalla sua origine, è opportuno "
"che l'ampiezza snap gride venga impostata a 100\n"
-#: gschem/src/i_callbacks.c:1008
+#: gschem/src/i_callbacks.c:1039
msgid "Embed"
msgstr "Incorpora"
-#: gschem/src/i_callbacks.c:1047
+#: gschem/src/i_callbacks.c:1078
msgid "Unembed"
msgstr "Scorpora"
-#: gschem/src/i_callbacks.c:1089
+#: gschem/src/i_callbacks.c:1120
msgid "Update"
msgstr "Aggiorna"
-#: gschem/src/i_callbacks.c:1136
+#: gschem/src/i_callbacks.c:1167
msgid "ShowHidden"
msgstr "Mostra Nascosto"
-#: gschem/src/i_callbacks.c:1160
-msgid "MakeVisible"
-msgstr "Rendi Visibile"
-
-#: gschem/src/i_callbacks.c:1466 gschem/src/i_callbacks.c:1538
+#: gschem/src/i_callbacks.c:1473 gschem/src/i_callbacks.c:1545
msgid "Pan"
msgstr "Pan"
-#: gschem/src/i_callbacks.c:1743
+#: gschem/src/i_callbacks.c:1750
msgid "Really revert page?"
msgstr "Vuoi veramente ritornare alla pagina precedente?"
-#: gschem/src/i_callbacks.c:1813
+#: gschem/src/i_callbacks.c:1820
msgid "Copy to clipboard"
msgstr "Copia negli appunti"
-#: gschem/src/i_callbacks.c:1831
+#: gschem/src/i_callbacks.c:1838
msgid "Cut to clipboard"
msgstr "Taglia negli appunti"
-#: gschem/src/i_callbacks.c:1849
+#: gschem/src/i_callbacks.c:1856
msgid "Paste from clipboard"
msgstr "Incolla dagli appunti"
-#: gschem/src/i_callbacks.c:1861 gschem/src/i_callbacks.c:2100
-#: gschem/src/i_callbacks.c:2122 gschem/src/i_callbacks.c:2144
-#: gschem/src/i_callbacks.c:2166 gschem/src/i_callbacks.c:2188
+#: gschem/src/i_callbacks.c:1868 gschem/src/i_callbacks.c:2107
+#: gschem/src/i_callbacks.c:2129 gschem/src/i_callbacks.c:2151
+#: gschem/src/i_callbacks.c:2173 gschem/src/i_callbacks.c:2195
msgid "Empty buffer"
msgstr "Buffer vuoto"
-#: gschem/src/i_callbacks.c:1906
+#: gschem/src/i_callbacks.c:1913
msgid "Copy 1"
msgstr "Copia 1"
-#: gschem/src/i_callbacks.c:1925
+#: gschem/src/i_callbacks.c:1932
msgid "Copy 2"
msgstr "Copia 2"
-#: gschem/src/i_callbacks.c:1944
+#: gschem/src/i_callbacks.c:1951
msgid "Copy 3"
msgstr "Copia 3"
-#: gschem/src/i_callbacks.c:1963
+#: gschem/src/i_callbacks.c:1970
msgid "Copy 4"
msgstr "Copia 4"
-#: gschem/src/i_callbacks.c:1982
+#: gschem/src/i_callbacks.c:1989
msgid "Copy 5"
msgstr "Copia 5"
-#: gschem/src/i_callbacks.c:2001
+#: gschem/src/i_callbacks.c:2008
msgid "Cut 1"
msgstr "Taglia 1"
-#: gschem/src/i_callbacks.c:2020
+#: gschem/src/i_callbacks.c:2027
msgid "Cut 2"
msgstr "Taglia 2"
-#: gschem/src/i_callbacks.c:2039
+#: gschem/src/i_callbacks.c:2046
msgid "Cut 3"
msgstr "Taglia 3"
-#: gschem/src/i_callbacks.c:2058
+#: gschem/src/i_callbacks.c:2065
msgid "Cut 4"
msgstr "Taglia 4"
-#: gschem/src/i_callbacks.c:2077
+#: gschem/src/i_callbacks.c:2084
msgid "Cut 5"
msgstr "Taglia 5"
-#: gschem/src/i_callbacks.c:2093
+#: gschem/src/i_callbacks.c:2100
msgid "Paste 1"
msgstr "Incolla 1"
-#: gschem/src/i_callbacks.c:2115
+#: gschem/src/i_callbacks.c:2122
msgid "Paste 2"
msgstr "Incolla 2"
-#: gschem/src/i_callbacks.c:2137
+#: gschem/src/i_callbacks.c:2144
msgid "Paste 3"
msgstr "Incolla 3"
-#: gschem/src/i_callbacks.c:2159
+#: gschem/src/i_callbacks.c:2166
msgid "Paste 4"
msgstr "Incolla 4"
-#: gschem/src/i_callbacks.c:2181
+#: gschem/src/i_callbacks.c:2188
msgid "Paste 5"
msgstr "Incolla 5"
-#: gschem/src/i_callbacks.c:2318 gschem/src/x_window.c:355
+#: gschem/src/i_callbacks.c:2325 gschem/src/x_window.c:355
msgid "Component"
msgstr "Componente"
-#: gschem/src/i_callbacks.c:2354 gschem/src/i_callbacks.c:2373
-#: gschem/src/x_dialog.c:2285
+#: gschem/src/i_callbacks.c:2361 gschem/src/i_callbacks.c:2380
+#: gschem/src/x_dialog.c:2289
msgid "Attribute"
msgstr "Attributo"
-#: gschem/src/i_callbacks.c:2395 gschem/src/i_callbacks.c:2422
-#: gschem/src/x_dialog.c:2282
+#: gschem/src/i_callbacks.c:2402 gschem/src/i_callbacks.c:2429
+#: gschem/src/x_dialog.c:2286
msgid "Net"
msgstr "Collegamento"
-#: gschem/src/i_callbacks.c:2466 gschem/src/i_callbacks.c:2493
-#: gschem/src/x_dialog.c:2300 gschem/src/x_window.c:375
+#: gschem/src/i_callbacks.c:2473 gschem/src/i_callbacks.c:2500
+#: gschem/src/x_dialog.c:2304 gschem/src/x_window.c:375
msgid "Bus"
msgstr "Bus"
-#: gschem/src/i_callbacks.c:2574 gschem/src/i_callbacks.c:2597
+#: gschem/src/i_callbacks.c:2581 gschem/src/i_callbacks.c:2604
msgid "Line"
msgstr "Linea"
-#: gschem/src/i_callbacks.c:2619 gschem/src/i_callbacks.c:2642
+#: gschem/src/i_callbacks.c:2626 gschem/src/i_callbacks.c:2649
msgid "Box"
msgstr "Rettangolo"
-#: gschem/src/i_callbacks.c:2698 gschem/src/i_callbacks.c:2722
+#: gschem/src/i_callbacks.c:2705 gschem/src/i_callbacks.c:2729
msgid "Circle"
msgstr "Cerchio"
-#: gschem/src/i_callbacks.c:2744 gschem/src/i_callbacks.c:2767
+#: gschem/src/i_callbacks.c:2751 gschem/src/i_callbacks.c:2774
msgid "Arc"
msgstr "Arco"
-#: gschem/src/i_callbacks.c:2789 gschem/src/i_callbacks.c:2812
-#: gschem/src/x_dialog.c:2273
+#: gschem/src/i_callbacks.c:2796 gschem/src/i_callbacks.c:2819
+#: gschem/src/x_dialog.c:2277
msgid "Pin"
msgstr "Pin"
-#: gschem/src/i_callbacks.c:2871
+#: gschem/src/i_callbacks.c:2878
#, c-format
msgid "Searching for source [%s]\n"
msgstr "Ricerca del sorgente [%s]\n"
-#: gschem/src/i_callbacks.c:2895
+#: gschem/src/i_callbacks.c:2902
#, c-format
msgid "Cannot find source [%s]\n"
msgstr "Impossibile trovare il sorgente [%s]\n"
-#: gschem/src/i_callbacks.c:2964
+#: gschem/src/i_callbacks.c:2965
#, c-format
msgid "Searching for symbol [%s]\n"
msgstr "Ricerca del simbolo [%s]\n"
-#: gschem/src/i_callbacks.c:2970
+#: gschem/src/i_callbacks.c:2971
msgid "Symbol is not a real file. Symbol cannot be loaded.\n"
msgstr "Il simolo non è un file reale, impossibile caricarlo.\n"
-#: gschem/src/i_callbacks.c:3001
+#: gschem/src/i_callbacks.c:3002
msgid "Cannot find any schematics above the current one!\n"
msgstr "Impossibile trovare uno schema a livello più alto di questo!\n"
-#: gschem/src/i_callbacks.c:3055
+#: gschem/src/i_callbacks.c:3056
msgid ""
"This command retrieves the component documentation from the web, but there "
"is no component selected"
@@ -633,84 +619,84 @@ msgstr ""
"Questo comando reperisce la documentazione del componente da Internet, ma "
"non hai selezionato nessun componente da cercare."
-#: gschem/src/i_callbacks.c:3083
+#: gschem/src/i_callbacks.c:3084
msgid "Attach"
msgstr "Collega"
-#: gschem/src/i_callbacks.c:3130
+#: gschem/src/i_callbacks.c:3131
msgid "Detach"
msgstr "Scollega"
-#: gschem/src/i_callbacks.c:3165
+#: gschem/src/i_callbacks.c:3166
msgid "ShowN"
msgstr "MostraN"
-#: gschem/src/i_callbacks.c:3201
+#: gschem/src/i_callbacks.c:3202
msgid "ShowV"
msgstr "MostraV"
-#: gschem/src/i_callbacks.c:3237
+#: gschem/src/i_callbacks.c:3238
msgid "ShowB"
msgstr "MostraB"
-#: gschem/src/i_callbacks.c:3274
+#: gschem/src/i_callbacks.c:3275
msgid "VisToggle"
msgstr "Visibilità Strumenti"
-#: gschem/src/i_callbacks.c:3304
+#: gschem/src/i_callbacks.c:3305
#, c-format
msgid "Sorry but this is a non-functioning menu option\n"
msgstr "Spiacente, ma questa non è una funzione del menù opzioni\n"
-#: gschem/src/i_callbacks.c:3394
+#: gschem/src/i_callbacks.c:3395
msgid "Action feedback mode set to OUTLINE\n"
msgstr "Controllo azioni in modalità CONTORNO\n"
-#: gschem/src/i_callbacks.c:3397
+#: gschem/src/i_callbacks.c:3398
msgid "Action feedback mode set to BOUNDINGBOX\n"
msgstr "Controllo azioni in modalità PERIMETRO\n"
-#: gschem/src/i_callbacks.c:3422
+#: gschem/src/i_callbacks.c:3423
msgid "Grid OFF\n"
msgstr "Griglia NON ATTIVA\n"
-#: gschem/src/i_callbacks.c:3423
+#: gschem/src/i_callbacks.c:3424
msgid "Dot grid selected\n"
msgstr "Selezionata griglia a punti\n"
-#: gschem/src/i_callbacks.c:3424
+#: gschem/src/i_callbacks.c:3425
msgid "Mesh grid selected\n"
msgstr "Selezionata griglia a maglie\n"
-#: gschem/src/i_callbacks.c:3445
+#: gschem/src/i_callbacks.c:3446
msgid "Snap OFF (CAUTION!)\n"
msgstr "Snap OFF (ATTENZIONE!)\n"
-#: gschem/src/i_callbacks.c:3448
+#: gschem/src/i_callbacks.c:3449
msgid "Snap ON\n"
msgstr "Snap ON\n"
-#: gschem/src/i_callbacks.c:3451
+#: gschem/src/i_callbacks.c:3452
msgid "Snap back to the grid (CAUTION!)\n"
msgstr "Snap alla griglia (ATTENZIONE)!\n"
-#: gschem/src/i_callbacks.c:3477
+#: gschem/src/i_callbacks.c:3478
msgid "Rubber band OFF \n"
msgstr "Rubber band OFF \n"
-#: gschem/src/i_callbacks.c:3480
+#: gschem/src/i_callbacks.c:3481
msgid "Rubber band ON\n"
msgstr "Rubber band ON\n"
-#: gschem/src/i_callbacks.c:3495
+#: gschem/src/i_callbacks.c:3496
msgid "magnetic net mode: ON\n"
msgstr "modalià net magnetiche: ON\n"
-#: gschem/src/i_callbacks.c:3498
+#: gschem/src/i_callbacks.c:3499
msgid "magnetic net mode: OFF\n"
msgstr "modalià net magnetiche: OFF\n"
-#: gschem/src/o_box.c:153
+#: gschem/src/o_box.c:149
#, c-format
msgid "Unknown type for box (fill)!\n"
msgstr "Sconosciuto tipo per il riquadro (riempimento)!\n"
@@ -730,17 +716,17 @@ msgstr "o_buffer_cut: buffer non valido %i\n"
msgid "Got an invalid buffer_number [o_buffer_paste_start]\n"
msgstr "Ottenuto un non valido buffer_number [o_buffer_paste_start]\n"
-#: gschem/src/o_bus.c:118
+#: gschem/src/o_bus.c:117
#, c-format
msgid "Got an invalid which one in o_bus_draw_stretch\n"
msgstr "Ottenuto un non valido which one in o_bus_draw_stretch\n"
-#: gschem/src/o_circle.c:134
+#: gschem/src/o_circle.c:130
#, c-format
msgid "Unknown type for circle (fill)!\n"
msgstr "Tipo sconosciuto per il cerchio (riempimento)!\n"
-#: gschem/src/o_complex.c:243 gschem/src/o_complex.c:247
+#: gschem/src/o_complex.c:237 gschem/src/o_complex.c:241
#, c-format
msgid "Translating schematic [%d %d]\n"
msgstr "Spostamento schema [%d %d]\n"
@@ -758,41 +744,41 @@ msgstr "Oggetto già bloccato\n"
msgid "Object already unlocked\n"
msgstr "Oggetto già sbloccato\n"
-#: gschem/src/o_misc.c:413
+#: gschem/src/o_misc.c:409
msgid "Hidden text is now visible\n"
msgstr "Il testo nascosto è ora visibile\n"
-#: gschem/src/o_misc.c:415
+#: gschem/src/o_misc.c:411
msgid "Hidden text is now invisible\n"
msgstr "Il testo ora è non visibile\n"
-#: gschem/src/o_misc.c:668
+#: gschem/src/o_misc.c:636
#, c-format
msgid "Could not find symbol [%s] in library. Update failed.\n"
msgstr ""
"Non è possibile trovare il simbolo [%s] nella libreria. Aggiornamento "
"fallito.\n"
-#: gschem/src/o_misc.c:783
+#: gschem/src/o_misc.c:751
#, c-format
msgid "o_autosave_backups: Can't get the real filename of %s."
msgstr "o_autosave_backups: Non è possibile ottenere il vero nome del file %s."
-#: gschem/src/o_misc.c:827
+#: gschem/src/o_misc.c:795
#, c-format
msgid "Could NOT set previous backup file [%s] read-write\n"
msgstr ""
"NOn è possibile impostare il precedente file di ripristino [%s] in lettura-"
"scrittura\n"
-#: gschem/src/o_misc.c:845
+#: gschem/src/o_misc.c:815
#, c-format
msgid "Could NOT set backup file [%s] readonly\n"
msgstr ""
"Non è possibile impostare il precedente file di ripristino [%s] in sola "
"lettura\n"
-#: gschem/src/o_misc.c:850
+#: gschem/src/o_misc.c:820
#, c-format
msgid "Could NOT save backup file [%s]\n"
msgstr "Non è possibile salvare il file di ripristino [%s]\n"
@@ -812,37 +798,37 @@ msgstr "ACC! Ho cercato whichone ma non l'ho trovato!\n"
msgid "Got a non line object in o_move_check_endpoint\n"
msgstr "Ottenuto un oggetto non in linea in o_move_check_endpoint\n"
-#: gschem/src/o_net.c:159
+#: gschem/src/o_net.c:158
#, c-format
msgid "Got an invalid which one in o_net_draw_stretch\n"
msgstr "Ottenuto un non valido which one in o_net_draw_stretch\n"
-#: gschem/src/o_net.c:538
+#: gschem/src/o_net.c:537
msgid "Warning: Starting net at off grid coordinate\n"
msgstr "Attenzione: una net inizia in un punto fuori griglia\n"
-#: gschem/src/o_net.c:600
+#: gschem/src/o_net.c:599
msgid "Warning: Ending net at off grid coordinate\n"
msgstr "Attenzione: una net finisce in un punto fuori griglia\n"
-#: gschem/src/o_net.c:932 gschem/src/o_net.c:969 gschem/src/o_net.c:1040
-#: gschem/src/o_net.c:1076
+#: gschem/src/o_net.c:931 gschem/src/o_net.c:968 gschem/src/o_net.c:1039
+#: gschem/src/o_net.c:1075
#, c-format
msgid "Tried to add more than two bus rippers. Internal gschem error.\n"
msgstr ""
"Tentato di aggiungere più di due bus ripper. Errore interno di gschem.\n"
-#: gschem/src/o_net.c:1144
+#: gschem/src/o_net.c:1143
#, c-format
msgid "Bus ripper symbol [%s] was not found in any component library\n"
msgstr "Simbolo bus ripper [%s] non trovato in alcuna libreria\n"
-#: gschem/src/o_path.c:352
+#: gschem/src/o_path.c:348
#, c-format
msgid "Unknown type for path (fill)!\n"
msgstr "Tipo sconosciuto di percorso (fill)!\n"
-#: gschem/src/o_picture.c:163 gschem/src/o_picture.c:539
+#: gschem/src/o_picture.c:163 gschem/src/o_picture.c:537
#, c-format
msgid "Failed to load picture: %s"
msgstr "Fallito il caricamento dell'immagine: [%s]"
@@ -851,7 +837,7 @@ msgstr "Fallito il caricamento dell'immagine: [%s]"
msgid "Picture"
msgstr "Immagine"
-#: gschem/src/o_picture.c:447 gschem/src/x_attribedit.c:141
+#: gschem/src/o_picture.c:445 gschem/src/x_attribedit.c:141
#, c-format
msgid "ERROR: NULL object!\n"
msgstr "ERRORE: oggetto NULLO!\n"
@@ -872,34 +858,46 @@ msgstr "Slot non ammesso per questo componente\n"
msgid "New slot number out of range\n"
msgstr "Numero del nuovo slot fuori dal limite\n"
-#: gschem/src/o_undo.c:304
+#: gschem/src/o_undo.c:303
msgid "Undo/Redo disabled in rc file\n"
msgstr "Cancella/Ripristina disabilitato nel file rc\n"
-#: gschem/src/parsecmd.c:47
+#: gschem/src/parsecmd.c:81
#, c-format
msgid ""
-"Usage: %s [OPTIONS] schematic_filename1 ... schematic_filenameN\n"
-" -q Quiet mode\n"
-" -v Verbose mode on\n"
-" -r filename Rc filename\n"
-" -s filename Script (guile) filename\n"
-" -o filename Output filename (for printing)\n"
-" -p Automatically place the window\n"
-" -t Print stroke information\n"
-" -h Help; this message\n"
+"Usage: %s [OPTION ...] [--] [FILE ...]\n"
"\n"
-msgstr ""
-"Utilizzo: %s [OPZIONI] nomefile_schema1 ... nomefile_schemaN\n"
-" -q Quiet mode\n"
-" -v Verbose mode on\n"
-" -r filename Rc filename\n"
-" -s filename Script (guile) filename\n"
-" -o filename Output filename (for printing)\n"
-" -p Automatically place the window\n"
-" -t Print stroke information\n"
-" -h Help; this message\n"
+"Interactively edit gEDA schematics or symbols. If one or more FILEs\n"
+"are specified, open them for editing; otherwise, create a new, empty\n"
+"schematic.\n"
"\n"
+"Options:\n"
+" -q, --quiet Quiet mode.\n"
+" -v, --verbose Verbose mode.\n"
+" -r, --config-file=FILE Additional configuration file to load.\n"
+" -L DIR Add DIR to Scheme search path.\n"
+" -c EXPR Scheme expression to run at startup.\n"
+" -s FILE Scheme script to run at startup.\n"
+" -o, --output=FILE Output filename (for printing).\n"
+" -p Automatically place the window.\n"
+" -V, --version Show version information.\n"
+" -h, --help Help; this message.\n"
+" -- Treat all remaining arguments as filenames.\n"
+"\n"
+"Report bugs to <geda-bug@xxxxxxxx>\n"
+"gEDA/gaf homepage: <http://gpleda.org>\n"
+msgstr ""
+
+#: gschem/src/parsecmd.c:115
+#, c-format
+msgid ""
+"gEDA %s (g%.7s)\n"
+"Copyright (C) 1998-2011 gEDA developers\n"
+"This is free software, and you are welcome to redistribute it under\n"
+"certain conditions. For details, see the file `COPYING', which is\n"
+"included in the gEDA distribution.\n"
+"There is NO WARRANTY, to the extent permitted by law.\n"
+msgstr ""
#: gschem/src/x_attribedit.c:127
#, c-format
@@ -910,56 +908,56 @@ msgstr "Ottenuta opzione mostra non valida; ritorno a mostra entrambi\n"
msgid "Single Attribute Editor"
msgstr "Editor Singola Caratteristica"
-#: gschem/src/x_attribedit.c:358
+#: gschem/src/x_attribedit.c:359
msgid "<b>Edit Attribute</b>"
msgstr "<b>Modifica Caratteristiche</b>"
-#: gschem/src/x_attribedit.c:360
+#: gschem/src/x_attribedit.c:361
msgid "<b>Add Attribute</b>"
msgstr "<b>Aggiungi Caratteristiche</b>"
-#: gschem/src/x_attribedit.c:376 gschem/src/x_multiattrib.c:1916
+#: gschem/src/x_attribedit.c:377 gschem/src/x_multiattrib.c:1927
msgid "Name:"
msgstr "Nome:"
-#: gschem/src/x_attribedit.c:393 gschem/src/x_multiattrib.c:1935
+#: gschem/src/x_attribedit.c:394 gschem/src/x_multiattrib.c:1946
msgid "Value:"
msgstr "Valore:"
-#: gschem/src/x_attribedit.c:409 gschem/src/x_multiattrib.c:1978
+#: gschem/src/x_attribedit.c:410 gschem/src/x_multiattrib.c:1989
msgid "Visible"
msgstr "Visibile"
-#: gschem/src/x_attribedit.c:429
+#: gschem/src/x_attribedit.c:430
msgid "Show Value Only"
msgstr "Mostra Solo il Valore"
-#: gschem/src/x_attribedit.c:431
+#: gschem/src/x_attribedit.c:432
msgid "Show Name Only"
msgstr "Mostra Solo il Nome"
-#: gschem/src/x_attribedit.c:433 gschem/src/x_multiattrib.c:1454
+#: gschem/src/x_attribedit.c:434 gschem/src/x_multiattrib.c:1466
msgid "Show Name & Value"
msgstr "Mostra Nome & Valore"
-#: gschem/src/x_attribedit.c:440
+#: gschem/src/x_attribedit.c:441
msgid "<b>Attach Options</b>"
msgstr "<b>Aggiungi Opzioni</b>"
-#: gschem/src/x_attribedit.c:455
+#: gschem/src/x_attribedit.c:456
msgid "All"
msgstr "Tutto"
-#: gschem/src/x_attribedit.c:463 gschem/src/x_compselect.c:896
-#: gschem/src/x_compselect.c:1010
+#: gschem/src/x_attribedit.c:464 gschem/src/x_compselect.c:904
+#: gschem/src/x_compselect.c:1018
msgid "Components"
msgstr "Componenti"
-#: gschem/src/x_attribedit.c:471 gschem/src/x_window.c:365
+#: gschem/src/x_attribedit.c:472 gschem/src/x_window.c:365
msgid "Nets"
msgstr "Collegamenti"
-#: gschem/src/x_attribedit.c:479
+#: gschem/src/x_attribedit.c:480
msgid "Replace existing attributes"
msgstr "Ridefinisci le caratteristiche esistenti"
@@ -979,91 +977,91 @@ msgstr ""
"uno slot duplicato potrebbe causare problemi: [nome simbolo=%s, numero=%d, "
"slot=%d]\n"
-#: gschem/src/x_autonumber.c:673
+#: gschem/src/x_autonumber.c:675
msgid "No searchstring given in autonumber text.\n"
msgstr "Nessuna stringa di ricerca nel testo di autonumerazione.\n"
-#: gschem/src/x_autonumber.c:725
+#: gschem/src/x_autonumber.c:727
msgid "No '*' or '?' given at the end of the autonumber text.\n"
msgstr "Nessun '*' o '?' alla fine del testo di autonumerazione.\n"
-#: gschem/src/x_autonumber.c:860
+#: gschem/src/x_autonumber.c:862
msgid "Diagonal"
msgstr "Diagonale"
-#: gschem/src/x_autonumber.c:861
+#: gschem/src/x_autonumber.c:863
msgid "Top to bottom"
msgstr "Dall'alto verso il basso"
-#: gschem/src/x_autonumber.c:861
+#: gschem/src/x_autonumber.c:863
msgid "Bottom to top"
msgstr "Dal basso verso l'alto"
-#: gschem/src/x_autonumber.c:862
+#: gschem/src/x_autonumber.c:864
msgid "Left to right"
msgstr "Da sinistra a destra"
-#: gschem/src/x_autonumber.c:862
+#: gschem/src/x_autonumber.c:864
msgid "Right to left"
msgstr "Da destra a sinistra"
-#: gschem/src/x_autonumber.c:863
+#: gschem/src/x_autonumber.c:865
msgid "File order"
msgstr "Sequenza dei file"
-#: gschem/src/x_autonumber.c:1199
+#: gschem/src/x_autonumber.c:1201
msgid "Autonumber text"
msgstr "Testo di autonumerazione"
-#: gschem/src/x_autonumber.c:1223
+#: gschem/src/x_autonumber.c:1225
msgid "<b>Scope</b>"
msgstr "<b>Visibilità </b>"
-#: gschem/src/x_autonumber.c:1245
+#: gschem/src/x_autonumber.c:1247
msgid "Search for:"
msgstr "Ricerca di:"
-#: gschem/src/x_autonumber.c:1259
+#: gschem/src/x_autonumber.c:1261
msgid "Autonumber text in:"
msgstr "Testo di autonumerazione in:"
-#: gschem/src/x_autonumber.c:1266
+#: gschem/src/x_autonumber.c:1268
msgid "Skip numbers found in:"
msgstr "Trovati numeri mancanti in:"
-#: gschem/src/x_autonumber.c:1278 gschem/src/x_autonumber.c:1287
+#: gschem/src/x_autonumber.c:1280 gschem/src/x_autonumber.c:1289
msgid "Selected objects"
msgstr "Oggetti selezionati"
-#: gschem/src/x_autonumber.c:1279 gschem/src/x_autonumber.c:1288
+#: gschem/src/x_autonumber.c:1281 gschem/src/x_autonumber.c:1290
msgid "Current page"
msgstr "Pagina corrente"
-#: gschem/src/x_autonumber.c:1280 gschem/src/x_autonumber.c:1289
+#: gschem/src/x_autonumber.c:1282 gschem/src/x_autonumber.c:1291
msgid "Whole hierarchy"
msgstr "Intera gerarchia"
-#: gschem/src/x_autonumber.c:1291
+#: gschem/src/x_autonumber.c:1293
msgid "Overwrite existing numbers"
msgstr "Sovrascrivi i numeri esistenti"
-#: gschem/src/x_autonumber.c:1296
+#: gschem/src/x_autonumber.c:1298
msgid "<b>Options</b>"
msgstr "<b>Opzioni</b>"
-#: gschem/src/x_autonumber.c:1318
+#: gschem/src/x_autonumber.c:1320
msgid "Starting number:"
msgstr "Numero iniziale:"
-#: gschem/src/x_autonumber.c:1325
+#: gschem/src/x_autonumber.c:1327
msgid "Sort order:"
msgstr "Ordinamento:"
-#: gschem/src/x_autonumber.c:1346
+#: gschem/src/x_autonumber.c:1348
msgid "Remove numbers"
msgstr "Rimuovi numeri"
-#: gschem/src/x_autonumber.c:1350
+#: gschem/src/x_autonumber.c:1352
msgid "Automatic slotting"
msgstr "Slot automatico"
@@ -1100,48 +1098,48 @@ msgstr "Provato a ottenere un colore non valido: %d\n"
msgid "Tried to get an invalid outline color: %d\n"
msgstr "Provato a ottenere un colore outline non valido: %d\n"
-#: gschem/src/x_compselect.c:1040
+#: gschem/src/x_compselect.c:1048
msgid "Filter:"
msgstr "Filtro:"
-#: gschem/src/x_compselect.c:1143 gschem/src/x_dialog.c:3663
-#: gschem/src/x_multiattrib.c:1782
+#: gschem/src/x_compselect.c:1151 gschem/src/x_dialog.c:3667
+#: gschem/src/x_multiattrib.c:1793
msgid "Name"
msgstr "Nome"
-#: gschem/src/x_compselect.c:1152 gschem/src/x_multiattrib.c:1806
+#: gschem/src/x_compselect.c:1160 gschem/src/x_multiattrib.c:1817
msgid "Value"
msgstr "Valore"
-#: gschem/src/x_compselect.c:1191
+#: gschem/src/x_compselect.c:1199
msgid "Default behavior - reference component"
msgstr "Comportamento predefinito - Consultazione componente"
-#: gschem/src/x_compselect.c:1194
+#: gschem/src/x_compselect.c:1202
msgid "Embed component in schematic"
msgstr "Incorpora il componente nello schema"
-#: gschem/src/x_compselect.c:1197
+#: gschem/src/x_compselect.c:1205
msgid "Include component as individual objects"
msgstr "Includi componente come oggetto individuale"
-#: gschem/src/x_compselect.c:1354
+#: gschem/src/x_compselect.c:1362
msgid "Select Component..."
msgstr "Seleziona Componente..."
-#: gschem/src/x_compselect.c:1377
+#: gschem/src/x_compselect.c:1385
msgid "In Use"
msgstr "In uso"
-#: gschem/src/x_compselect.c:1381
+#: gschem/src/x_compselect.c:1389
msgid "Libraries"
msgstr "Librerie"
-#: gschem/src/x_compselect.c:1390 gschem/src/x_fileselect.c:122
+#: gschem/src/x_compselect.c:1398 gschem/src/x_fileselect.c:122
msgid "Preview"
msgstr "Anteprima"
-#: gschem/src/x_compselect.c:1418
+#: gschem/src/x_compselect.c:1426
msgid "Attributes"
msgstr "Attributi"
@@ -1200,139 +1198,139 @@ msgstr "In basso a destra"
msgid "Edit Text Properties"
msgstr "Modifica proprietà del testo"
-#: gschem/src/x_dialog.c:471
+#: gschem/src/x_dialog.c:472
msgid "<b>Text Content</b>"
msgstr "<b>Contenuto Testo</b>"
-#: gschem/src/x_dialog.c:507
+#: gschem/src/x_dialog.c:508
msgid "<b>Text Properties</b>"
msgstr "<b>Proprietà del testo</b>"
-#: gschem/src/x_dialog.c:522
+#: gschem/src/x_dialog.c:523
msgid "Color:"
msgstr "Colore:"
-#: gschem/src/x_dialog.c:529
+#: gschem/src/x_dialog.c:530
msgid "Size:"
msgstr "Ampiezza:"
-#: gschem/src/x_dialog.c:538
+#: gschem/src/x_dialog.c:539
msgid "Alignment:"
msgstr "Allineamento:"
-#: gschem/src/x_dialog.c:587
+#: gschem/src/x_dialog.c:588
msgid "Solid"
msgstr "Continua"
-#: gschem/src/x_dialog.c:588
+#: gschem/src/x_dialog.c:589
msgid "Dotted"
msgstr "Punteggiata"
-#: gschem/src/x_dialog.c:589
+#: gschem/src/x_dialog.c:590
msgid "Dashed"
msgstr "Tratteggiata"
-#: gschem/src/x_dialog.c:590
+#: gschem/src/x_dialog.c:591
msgid "Center"
msgstr "Centro"
-#: gschem/src/x_dialog.c:591
+#: gschem/src/x_dialog.c:592
msgid "Phantom"
msgstr "Fantasma"
-#: gschem/src/x_dialog.c:592 gschem/src/x_dialog.c:689
-#: gschem/src/x_dialog.c:698 gschem/src/x_dialog.c:707
-#: gschem/src/x_dialog.c:808 gschem/src/x_dialog.c:810
-#: gschem/src/x_dialog.c:812 gschem/src/x_dialog.c:1038
-#: gschem/src/x_dialog.c:1141 gschem/src/x_dialog.c:1150
-#: gschem/src/x_dialog.c:1159 gschem/src/x_dialog.c:1168
-#: gschem/src/x_dialog.c:1177 gschem/src/x_dialog.c:1290
-#: gschem/src/x_dialog.c:1292 gschem/src/x_dialog.c:1294
-#: gschem/src/x_dialog.c:1296 gschem/src/x_dialog.c:1298
+#: gschem/src/x_dialog.c:593 gschem/src/x_dialog.c:690
+#: gschem/src/x_dialog.c:699 gschem/src/x_dialog.c:708
+#: gschem/src/x_dialog.c:809 gschem/src/x_dialog.c:811
+#: gschem/src/x_dialog.c:813 gschem/src/x_dialog.c:1039
+#: gschem/src/x_dialog.c:1142 gschem/src/x_dialog.c:1151
+#: gschem/src/x_dialog.c:1160 gschem/src/x_dialog.c:1169
+#: gschem/src/x_dialog.c:1178 gschem/src/x_dialog.c:1291
+#: gschem/src/x_dialog.c:1293 gschem/src/x_dialog.c:1295
+#: gschem/src/x_dialog.c:1297 gschem/src/x_dialog.c:1299
msgid "*unchanged*"
msgstr "*non cambiato*"
-#: gschem/src/x_dialog.c:916
+#: gschem/src/x_dialog.c:917
msgid "Edit Line Width & Type"
msgstr "Modifica Larghezza & Tipo di Linea"
-#: gschem/src/x_dialog.c:955 gschem/src/x_print.c:307
+#: gschem/src/x_dialog.c:956 gschem/src/x_print.c:307
msgid "Type:"
msgstr "Tipo:"
-#: gschem/src/x_dialog.c:959
+#: gschem/src/x_dialog.c:960
msgid "Width:"
msgstr "Larghezza:"
-#: gschem/src/x_dialog.c:963
+#: gschem/src/x_dialog.c:964
msgid "Dash Length:"
msgstr "Lunghezza linea tratteggiata:"
-#: gschem/src/x_dialog.c:967
+#: gschem/src/x_dialog.c:968
msgid "Dash Space:"
msgstr "Spazio linea tratteggiata:"
-#: gschem/src/x_dialog.c:1034
+#: gschem/src/x_dialog.c:1035
msgid "Hollow"
msgstr "Vuoto"
-#: gschem/src/x_dialog.c:1035
+#: gschem/src/x_dialog.c:1036
msgid "Filled"
msgstr "Riempito"
-#: gschem/src/x_dialog.c:1036
+#: gschem/src/x_dialog.c:1037
msgid "Mesh"
msgstr "Rete"
-#: gschem/src/x_dialog.c:1037
+#: gschem/src/x_dialog.c:1038
msgid "Hatch"
msgstr "Tratteggio"
-#: gschem/src/x_dialog.c:1406
+#: gschem/src/x_dialog.c:1407
msgid "Edit Fill Type"
msgstr "Modifica il Tipo di Riempimento"
-#: gschem/src/x_dialog.c:1444
+#: gschem/src/x_dialog.c:1446
msgid "Fill Type:"
msgstr "Tipo di riempimento:"
-#: gschem/src/x_dialog.c:1448
+#: gschem/src/x_dialog.c:1450
msgid "Line Width:"
msgstr "Larghezza linea:"
-#: gschem/src/x_dialog.c:1452
+#: gschem/src/x_dialog.c:1454
msgid "Angle 1:"
msgstr "Angolo 1:"
-#: gschem/src/x_dialog.c:1456
+#: gschem/src/x_dialog.c:1458
msgid "Pitch 1:"
msgstr "Livello 1:"
-#: gschem/src/x_dialog.c:1460
+#: gschem/src/x_dialog.c:1462
msgid "Angle 2:"
msgstr "Angolo 2:"
-#: gschem/src/x_dialog.c:1464
+#: gschem/src/x_dialog.c:1466
msgid "Pitch 2:"
msgstr "Livello 2:"
-#: gschem/src/x_dialog.c:1591
+#: gschem/src/x_dialog.c:1593
msgid "Arc Params"
msgstr "Parametri Arco"
-#: gschem/src/x_dialog.c:1631
+#: gschem/src/x_dialog.c:1634
msgid "Arc Radius:"
msgstr "Raggio Arco:"
-#: gschem/src/x_dialog.c:1639
+#: gschem/src/x_dialog.c:1642
msgid "Start Angle:"
msgstr "Angolo di Attacco:"
-#: gschem/src/x_dialog.c:1647
+#: gschem/src/x_dialog.c:1650
msgid "Degrees of Sweep:"
msgstr "Gradi di sviluppo dell'arco:"
-#: gschem/src/x_dialog.c:1764
+#: gschem/src/x_dialog.c:1768
msgid ""
"Offset to translate?\n"
"(0 for origin)"
@@ -1340,184 +1338,184 @@ msgstr ""
"Spostamento per conversione?\n"
"(0 per l'origine)"
-#: gschem/src/x_dialog.c:1832
+#: gschem/src/x_dialog.c:1836
msgid "Text Size"
msgstr "Dimensione Testo"
-#: gschem/src/x_dialog.c:1862
+#: gschem/src/x_dialog.c:1866
msgid "Enter new text size:"
msgstr "Inserisci nuova ampiezza del testo:"
-#: gschem/src/x_dialog.c:1938
+#: gschem/src/x_dialog.c:1942
msgid "Snap Size"
msgstr "Dimensione Snap"
-#: gschem/src/x_dialog.c:1968
+#: gschem/src/x_dialog.c:1972
msgid "Enter new snap grid spacing:"
msgstr "Inserisci la nuova spaziatura griglia snap:"
-#: gschem/src/x_dialog.c:2045
+#: gschem/src/x_dialog.c:2049
msgid "Edit slot number"
msgstr "Modifica numero slot"
-#: gschem/src/x_dialog.c:2076
+#: gschem/src/x_dialog.c:2080
msgid "Edit slot number:"
msgstr "Modifica numero slot:"
-#: gschem/src/x_dialog.c:2117
+#: gschem/src/x_dialog.c:2121
#, c-format
msgid "%s%s (%s)"
msgstr ""
-#: gschem/src/x_dialog.c:2140
+#: gschem/src/x_dialog.c:2144
msgid "About gschem"
msgstr "Informazioni su gschem"
-#: gschem/src/x_dialog.c:2141
+#: gschem/src/x_dialog.c:2145
msgid "gEDA: GPL Electronic Design Automation"
msgstr ""
-#: gschem/src/x_dialog.c:2142
+#: gschem/src/x_dialog.c:2146
msgid ""
"Copyright © 1998-2009 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
"Copyright © 1998-2009 gEDA Contributors (see ChangeLog for details)"
msgstr ""
-#: gschem/src/x_dialog.c:2201
+#: gschem/src/x_dialog.c:2205
msgid "Coords"
msgstr "Coordinate"
-#: gschem/src/x_dialog.c:2222
+#: gschem/src/x_dialog.c:2226
msgid "Screen"
msgstr "Schermo"
-#: gschem/src/x_dialog.c:2231
+#: gschem/src/x_dialog.c:2235
msgid "World"
msgstr "Mondo"
-#: gschem/src/x_dialog.c:2270
+#: gschem/src/x_dialog.c:2274
msgid "Background"
msgstr "Sfondo"
-#: gschem/src/x_dialog.c:2276
+#: gschem/src/x_dialog.c:2280
msgid "Net endpoint"
msgstr "Fine net"
-#: gschem/src/x_dialog.c:2279
+#: gschem/src/x_dialog.c:2283
msgid "Graphic"
msgstr "Grafico"
-#: gschem/src/x_dialog.c:2288
+#: gschem/src/x_dialog.c:2292
msgid "Logic bubble"
msgstr "Bolla logica"
-#: gschem/src/x_dialog.c:2291
+#: gschem/src/x_dialog.c:2295
msgid "Grid point"
msgstr "Punto della griglia"
-#: gschem/src/x_dialog.c:2294
+#: gschem/src/x_dialog.c:2298
msgid "Detached attribute"
msgstr "Attributo staccato"
-#: gschem/src/x_dialog.c:2297 gschem/src/x_window.c:383
+#: gschem/src/x_dialog.c:2301 gschem/src/x_window.c:383
msgid "Text"
msgstr "Testo"
-#: gschem/src/x_dialog.c:2303
+#: gschem/src/x_dialog.c:2307
msgid "Selection"
msgstr "Selezione"
-#: gschem/src/x_dialog.c:2306
+#: gschem/src/x_dialog.c:2310
msgid "Bounding box"
msgstr "Riquadro di selezione"
-#: gschem/src/x_dialog.c:2309
+#: gschem/src/x_dialog.c:2313
msgid "Zoom box"
msgstr "Riquadro di Zoom"
-#: gschem/src/x_dialog.c:2318
+#: gschem/src/x_dialog.c:2322
msgid "Output background"
msgstr "Sfondo uscita"
-#: gschem/src/x_dialog.c:2321
+#: gschem/src/x_dialog.c:2325
msgid "Net junction"
msgstr "Giunzione di traccia"
-#: gschem/src/x_dialog.c:2324
+#: gschem/src/x_dialog.c:2328
msgid "Mesh grid major"
msgstr "Griglia a maglie grandi"
-#: gschem/src/x_dialog.c:2327
+#: gschem/src/x_dialog.c:2331
msgid "Mesh grid minor"
msgstr "Griglia a maglie piccole"
-#: gschem/src/x_dialog.c:2330
+#: gschem/src/x_dialog.c:2334
msgid "Unknown"
msgstr "Sconosciuto"
-#: gschem/src/x_dialog.c:2481
+#: gschem/src/x_dialog.c:2485
#, c-format
msgid "ERROR: NULL object in color_edit_dialog_apply!\n"
msgstr "ERRORE: oggetto NULLO in color_edit_dialog_apply!\n"
-#: gschem/src/x_dialog.c:2525
+#: gschem/src/x_dialog.c:2529
msgid "Color Edit"
msgstr "Modifica Colore"
-#: gschem/src/x_dialog.c:2556
+#: gschem/src/x_dialog.c:2560
msgid "Object color:"
msgstr "Colore dell'oggetto:"
-#: gschem/src/x_dialog.c:2614
+#: gschem/src/x_dialog.c:2618
msgid "Hotkeys"
msgstr "Tasti scelta rapida"
-#: gschem/src/x_dialog.c:2678
+#: gschem/src/x_dialog.c:2682
msgid "Function"
msgstr "Funzione"
-#: gschem/src/x_dialog.c:2685
+#: gschem/src/x_dialog.c:2689
msgid "Keystroke(s)"
msgstr "Tasto(i)"
-#: gschem/src/x_dialog.c:2991
+#: gschem/src/x_dialog.c:2995
msgid "Find Text"
msgstr "Trova testo"
-#: gschem/src/x_dialog.c:3022
+#: gschem/src/x_dialog.c:3026
msgid "Text to find:"
msgstr "Testo da trovare:"
-#: gschem/src/x_dialog.c:3032
+#: gschem/src/x_dialog.c:3036
msgid "descend into hierarchy"
msgstr "discende nella gerarchia"
-#: gschem/src/x_dialog.c:3097
+#: gschem/src/x_dialog.c:3101
msgid "Hide Text"
msgstr "Nascondi testo"
-#: gschem/src/x_dialog.c:3128
+#: gschem/src/x_dialog.c:3132
msgid "Hide text starting with:"
msgstr "Nascondi il testo iniziando con:"
-#: gschem/src/x_dialog.c:3197
+#: gschem/src/x_dialog.c:3201
msgid "Show Text"
msgstr "Mostra testo"
-#: gschem/src/x_dialog.c:3228
+#: gschem/src/x_dialog.c:3232
msgid "Show text starting with:"
msgstr "Mostra il testo iniziando con:"
-#: gschem/src/x_dialog.c:3685
+#: gschem/src/x_dialog.c:3689
msgid "S_elect the schematics you want to save:"
msgstr "S_eleziona lo schema che vuoi salvare:"
-#: gschem/src/x_dialog.c:3779
+#: gschem/src/x_dialog.c:3784
#, c-format
msgid "Save the changes to schematic \"%s\" before closing?"
msgstr "Salvare i cambi allo schema \"%s\" prima di chiudere?"
-#: gschem/src/x_dialog.c:3785
+#: gschem/src/x_dialog.c:3790
#, c-format
msgid ""
"There are %d schematics with unsaved changes. Save changes before closing?"
@@ -1525,15 +1523,15 @@ msgstr ""
"Ci sono %d schemi che presentano cambi non salvati. Salvare i cambi prima di "
"chiudere?"
-#: gschem/src/x_dialog.c:3814
+#: gschem/src/x_dialog.c:3819
msgid "If you don't save, all your changes will be permanently lost."
msgstr "Se non salvi, tutte le modifiche saranno perse definitivamente."
-#: gschem/src/x_dialog.c:3834
+#: gschem/src/x_dialog.c:3839
msgid "_Close without saving"
msgstr "_Chiudi senza salvare"
-#: gschem/src/x_dialog.c:4170
+#: gschem/src/x_dialog.c:4175
#, c-format
msgid ""
"<span weight=\"bold\" size=\"larger\">The input attribute \"%s\" is invalid\n"
@@ -1551,19 +1549,19 @@ msgstr ""
"Il nome non deve terminare con uno spazio.\n"
"Il valore non deve iniziare con uno spazio."
-#: gschem/src/x_dialog.c:4172
+#: gschem/src/x_dialog.c:4177
msgid "Invalid Attribute"
msgstr "Attributo non valido"
-#: gschem/src/x_dialog.c:4208
+#: gschem/src/x_dialog.c:4213
msgid "Pin type"
msgstr "Tipo di pin"
-#: gschem/src/x_dialog.c:4232
+#: gschem/src/x_dialog.c:4237
msgid "Net pin"
msgstr "Net pin"
-#: gschem/src/x_dialog.c:4234
+#: gschem/src/x_dialog.c:4239
msgid "Bus pin (graphical)"
msgstr "Bus pin (grafico)"
@@ -1665,13 +1663,13 @@ msgstr "Tipo di immagine"
msgid "Write image..."
msgstr "Scrivi immagine..."
-#: gschem/src/x_log.c:188
+#: gschem/src/x_log.c:209
msgid "** Invalid UTF-8 in log message. See stderr or gschem.log.\n"
msgstr ""
"** UTF-8 non valido in messaggio del log. Verificare in stderr o gschem."
"log.\n"
-#: gschem/src/x_log.c:256
+#: gschem/src/x_log.c:288
msgid "Status"
msgstr "Stato"
@@ -1747,73 +1745,64 @@ msgstr "/Modifica simbolo"
msgid "/Up"
msgstr "/Torna su"
-#: gschem/src/x_menus.c:321
+#: gschem/src/x_menus.c:323
#, c-format
msgid "Tried to set the sensitivity on non-existent menu item '%s'\n"
msgstr ""
"Si è tentato di regolare la sensitività su un oggetto di menu inesistente "
"%s\n"
-#: gschem/src/x_menus.c:345
+#: gschem/src/x_menus.c:347
msgid "Popup_menu_item_factory doesn't exist!\n"
msgstr "La voce Popup_menu_item_factory non esiste!\n"
-#: gschem/src/x_menus.c:358
+#: gschem/src/x_menus.c:360
msgid "Tried to set the sensitivity on a non-existent popup menu_item\n"
msgstr ""
"Provato a impostare la sensibilità su una finestra di popup menu_itemi\n"
-#: gschem/src/x_menus.c:438
-#, c-format
-msgid "Couldn't open file %s\n"
-msgstr "Non è possibile aprire il file %s\n"
-
-#: gschem/src/x_menus.c:495
-msgid "Clear"
-msgstr "Pulisci"
-
-#: gschem/src/x_multiattrib.c:911
+#: gschem/src/x_multiattrib.c:915
msgid "Attributes with empty name are not allowed. Please set a name."
msgstr ""
"Attributi con il nome vuoto non sono permessi. Per favore inserisci un nome."
-#: gschem/src/x_multiattrib.c:1456
+#: gschem/src/x_multiattrib.c:1468
msgid "Show Value only"
msgstr "Mostra solo il Valore"
-#: gschem/src/x_multiattrib.c:1458
+#: gschem/src/x_multiattrib.c:1470
msgid "Show Name only"
msgstr "Mostra solo il Nome"
-#: gschem/src/x_multiattrib.c:1486
+#: gschem/src/x_multiattrib.c:1498
msgid "Promote"
msgstr "Promuovi"
-#: gschem/src/x_multiattrib.c:1490
+#: gschem/src/x_multiattrib.c:1502
msgid "Duplicate"
msgstr "Duplicare"
-#: gschem/src/x_multiattrib.c:1708
+#: gschem/src/x_multiattrib.c:1719
msgid "Edit Attributes"
msgstr "Modifica attributi"
-#: gschem/src/x_multiattrib.c:1826
+#: gschem/src/x_multiattrib.c:1837
msgid "Vis?"
msgstr "Vis?"
-#: gschem/src/x_multiattrib.c:1844
+#: gschem/src/x_multiattrib.c:1855
msgid "N"
msgstr "N"
-#: gschem/src/x_multiattrib.c:1862
+#: gschem/src/x_multiattrib.c:1873
msgid "V"
msgstr "V"
-#: gschem/src/x_multiattrib.c:1884
+#: gschem/src/x_multiattrib.c:1895
msgid "Show inherited attributes"
msgstr "Mostra gli attributi ereditati"
-#: gschem/src/x_multiattrib.c:1900
+#: gschem/src/x_multiattrib.c:1911
msgid "Add Attribute"
msgstr "Aggiungi Attributo"
@@ -1837,25 +1826,25 @@ msgstr "Chiudi pagina"
msgid "Discard Page"
msgstr "Abbandona la pagina"
-#: gschem/src/x_pagesel.c:376
+#: gschem/src/x_pagesel.c:375
msgid "Page Manager"
msgstr "Gestore Pagina"
-#: gschem/src/x_pagesel.c:432
+#: gschem/src/x_pagesel.c:431
msgid "Filename"
msgstr "Nome file"
-#: gschem/src/x_pagesel.c:448
+#: gschem/src/x_pagesel.c:447
msgid "Changed"
msgstr "Cambiato"
-#: gschem/src/x_pagesel.c:468
+#: gschem/src/x_pagesel.c:467
msgid "Right click on the filename for more options..."
msgstr ""
"Clicca con il tasto destro del mouse sul nome del file per ulteriori "
"opzioni..."
-#: gschem/src/x_preview.c:234
+#: gschem/src/x_preview.c:233
msgid "Preview Buffer"
msgstr "Buffer di anteprima"
@@ -1911,16 +1900,16 @@ msgstr "File:"
msgid "Command:"
msgstr "Comando:"
-#: gschem/src/x_print.c:741
+#: gschem/src/x_print.c:745
msgid "No print destination specified\n"
msgstr "Non è stata specificata nessuna stampante\n"
-#: gschem/src/x_print.c:748
+#: gschem/src/x_print.c:752
#, c-format
msgid "Cannot print current schematic to [%s]\n"
msgstr "Non è possibile stampare lo schema corrente in [%s]\n"
-#: gschem/src/x_print.c:757
+#: gschem/src/x_print.c:761
#, c-format
msgid ""
"Error printing to file '%s'\n"
@@ -1929,7 +1918,7 @@ msgstr ""
"Errore nella stampa del file '%s'\n"
"Verifica la finestra di stato per maggiori informazioni"
-#: gschem/src/x_print.c:764
+#: gschem/src/x_print.c:768
#, c-format
msgid "Printed current schematic to [%s]\n"
msgstr "Lo schema corrente è stato stampato in [%s]\n"
@@ -1938,6 +1927,11 @@ msgstr "Lo schema corrente è stato stampato in [%s]\n"
msgid "Execute Script..."
msgstr "Esegui Script..."
+#: gschem/src/x_script.c:66
+#, c-format
+msgid "Executing guile script [%s]\n"
+msgstr "Esecuzione dello script guile [%s]\n"
+
#: gschem/src/x_window.c:81
#, c-format
msgid "Couldn't allocate gc\n"
@@ -2057,35 +2051,35 @@ msgstr "Impossibile caricare il file"
msgid "New file [%s]\n"
msgstr "Nuovo file [%s]\n"
-#: gschem/src/x_window.c:857
+#: gschem/src/x_window.c:855
#, c-format
msgid "Could NOT save page [%s]\n"
msgstr "Non è possibile salvare la pagina [%s]\n"
-#: gschem/src/x_window.c:858
+#: gschem/src/x_window.c:856
msgid "Error while trying to save"
msgstr "Errore durante il salvataggio"
-#: gschem/src/x_window.c:867
+#: gschem/src/x_window.c:865
#, c-format
msgid "Saved as [%s]\n"
msgstr "Salvato con il nome [%s]\n"
-#: gschem/src/x_window.c:869
+#: gschem/src/x_window.c:867
#, c-format
msgid "Saved [%s]\n"
msgstr "Salvato [%s]\n"
-#: gschem/src/x_window.c:871
+#: gschem/src/x_window.c:869
msgid "Saved"
msgstr "Salvato"
-#: gschem/src/x_window.c:945
+#: gschem/src/x_window.c:943
#, c-format
msgid "Discarding page [%s]\n"
msgstr "Annulla pagina [%s]\n"
-#: gschem/src/x_window.c:945
+#: gschem/src/x_window.c:943
#, c-format
msgid "Closing [%s]\n"
msgstr "Chiusura [%s]\n"
@@ -2126,7 +2120,7 @@ msgstr "Salva _come..."
msgid "Save All"
msgstr "Salva tutto"
-#: gschem/lib/system-gschemrc.scm:1386 gschem/lib/system-gschemrc.scm:1477
+#: gschem/lib/system-gschemrc.scm:1386 gschem/lib/system-gschemrc.scm:1478
msgid "_Revert"
msgstr "_Ripristina"
@@ -2138,7 +2132,7 @@ msgstr "_Stampa..."
msgid "Write _image..."
msgstr "Salva _immagine"
-#: gschem/lib/system-gschemrc.scm:1393 gschem/lib/system-gschemrc.scm:1478
+#: gschem/lib/system-gschemrc.scm:1393 gschem/lib/system-gschemrc.scm:1479
msgid "_Close"
msgstr "_Chiudi"
@@ -2170,391 +2164,435 @@ msgstr "_Incolla"
msgid "_Delete"
msgstr "_Elimina"
-#: gschem/lib/system-gschemrc.scm:1412
+#: gschem/lib/system-gschemrc.scm:1409
+#, fuzzy
+msgid "Select All"
+msgstr "Seleziona"
+
+#: gschem/lib/system-gschemrc.scm:1410
+#, fuzzy
+msgid "Deselect"
+msgstr "Seleziona"
+
+#: gschem/lib/system-gschemrc.scm:1414
msgid "Rotate 90 Mode"
msgstr "Ruota di 90 gradi"
-#: gschem/lib/system-gschemrc.scm:1415
+#: gschem/lib/system-gschemrc.scm:1417
msgid "Edit..."
msgstr "Modifica..."
-#: gschem/lib/system-gschemrc.scm:1416
+#: gschem/lib/system-gschemrc.scm:1418
msgid "Edit Text..."
msgstr "Modifica il testo..."
-#: gschem/lib/system-gschemrc.scm:1417
+#: gschem/lib/system-gschemrc.scm:1419
msgid "Slot..."
msgstr "Slot..."
-#: gschem/lib/system-gschemrc.scm:1418
+#: gschem/lib/system-gschemrc.scm:1420
msgid "Color..."
msgstr "Colore..."
-#: gschem/lib/system-gschemrc.scm:1419
+#: gschem/lib/system-gschemrc.scm:1421
msgid "Line Width & Type..."
msgstr "Tipo & Larghezza della linea..."
-#: gschem/lib/system-gschemrc.scm:1420
+#: gschem/lib/system-gschemrc.scm:1422
msgid "Fill Type..."
msgstr "Riempimento..."
-#: gschem/lib/system-gschemrc.scm:1421
+#: gschem/lib/system-gschemrc.scm:1423
msgid "Symbol Translate..."
msgstr "Converti simbolo..."
-#: gschem/lib/system-gschemrc.scm:1425
+#: gschem/lib/system-gschemrc.scm:1427
msgid "Invoke Macro"
msgstr "Esegui macro"
-#: gschem/lib/system-gschemrc.scm:1426
+#: gschem/lib/system-gschemrc.scm:1428
msgid "Embed Component/Picture"
msgstr "Componente/Immagine fissato/a"
-#: gschem/lib/system-gschemrc.scm:1427
+#: gschem/lib/system-gschemrc.scm:1429
msgid "Unembed Component/Picture"
msgstr "Componente/immagine non fissato/a"
-#: gschem/lib/system-gschemrc.scm:1428
+#: gschem/lib/system-gschemrc.scm:1430
msgid "Update Component"
msgstr "Aggiorna Componente"
-#: gschem/lib/system-gschemrc.scm:1429
+#: gschem/lib/system-gschemrc.scm:1431
msgid "Show/Hide Inv Text"
msgstr "Mostra/Nascondi Testo Invisibile"
-#: gschem/lib/system-gschemrc.scm:1430
-msgid "Make Inv Text Vis"
-msgstr "Rendi Invisibile Testo Visibile"
-
-#: gschem/lib/system-gschemrc.scm:1436
+#: gschem/lib/system-gschemrc.scm:1437
msgid "Copy into 1"
msgstr "Copia in 1"
-#: gschem/lib/system-gschemrc.scm:1437
+#: gschem/lib/system-gschemrc.scm:1438
msgid "Copy into 2"
msgstr "Copia in 2"
-#: gschem/lib/system-gschemrc.scm:1438
+#: gschem/lib/system-gschemrc.scm:1439
msgid "Copy into 3"
msgstr "Copia in 3"
-#: gschem/lib/system-gschemrc.scm:1439
+#: gschem/lib/system-gschemrc.scm:1440
msgid "Copy into 4"
msgstr "Copia in 4"
-#: gschem/lib/system-gschemrc.scm:1440
+#: gschem/lib/system-gschemrc.scm:1441
msgid "Copy into 5"
msgstr "Copia in 5"
-#: gschem/lib/system-gschemrc.scm:1441
+#: gschem/lib/system-gschemrc.scm:1442
msgid "Cut into 1"
msgstr "Taglia in 1"
-#: gschem/lib/system-gschemrc.scm:1442
+#: gschem/lib/system-gschemrc.scm:1443
msgid "Cut into 2"
msgstr "Taglia in 2"
-#: gschem/lib/system-gschemrc.scm:1443
+#: gschem/lib/system-gschemrc.scm:1444
msgid "Cut into 3"
msgstr "Taglia in 3"
-#: gschem/lib/system-gschemrc.scm:1444
+#: gschem/lib/system-gschemrc.scm:1445
msgid "Cut into 4"
msgstr "Taglia in 4"
-#: gschem/lib/system-gschemrc.scm:1445
+#: gschem/lib/system-gschemrc.scm:1446
msgid "Cut into 5"
msgstr "Taglia in 5"
-#: gschem/lib/system-gschemrc.scm:1446
+#: gschem/lib/system-gschemrc.scm:1447
msgid "Paste from 1"
msgstr "Incolla da 1"
-#: gschem/lib/system-gschemrc.scm:1447
+#: gschem/lib/system-gschemrc.scm:1448
msgid "Paste from 2"
msgstr "Incolla da 2"
-#: gschem/lib/system-gschemrc.scm:1448
+#: gschem/lib/system-gschemrc.scm:1449
msgid "Paste from 3"
msgstr "Incolla da 3"
-#: gschem/lib/system-gschemrc.scm:1449
+#: gschem/lib/system-gschemrc.scm:1450
msgid "Paste from 4"
msgstr "Incolla da 4"
-#: gschem/lib/system-gschemrc.scm:1450
+#: gschem/lib/system-gschemrc.scm:1451
msgid "Paste from 5"
msgstr "Incolla da 5"
-#: gschem/lib/system-gschemrc.scm:1456
+#: gschem/lib/system-gschemrc.scm:1457
msgid "_Redraw"
msgstr "_Ridisegna"
-#: gschem/lib/system-gschemrc.scm:1457
+#: gschem/lib/system-gschemrc.scm:1458
msgid "_Pan"
msgstr "_Scorri"
-#: gschem/lib/system-gschemrc.scm:1458
+#: gschem/lib/system-gschemrc.scm:1459
msgid "Zoom _Box"
msgstr "Ingrandisci _Riquadro"
-#: gschem/lib/system-gschemrc.scm:1459
+#: gschem/lib/system-gschemrc.scm:1460
msgid "Zoom _Extents"
msgstr "Adatta al _contenuto"
-#: gschem/lib/system-gschemrc.scm:1460
+#: gschem/lib/system-gschemrc.scm:1461
msgid "Zoom _In"
msgstr "Aum_enta ingrandimento"
-#: gschem/lib/system-gschemrc.scm:1461
+#: gschem/lib/system-gschemrc.scm:1462
msgid "Zoom _Out"
msgstr "Rid_uci ingrandimento"
-#: gschem/lib/system-gschemrc.scm:1462
+#: gschem/lib/system-gschemrc.scm:1463
msgid "Zoom _Full"
msgstr "Visualizza _tutto"
-#: gschem/lib/system-gschemrc.scm:1464
+#: gschem/lib/system-gschemrc.scm:1465
msgid "_Dark color scheme"
msgstr "_Schema colori scuri"
-#: gschem/lib/system-gschemrc.scm:1465
+#: gschem/lib/system-gschemrc.scm:1466
msgid "_Light color scheme"
msgstr "_Schema colori chiari"
-#: gschem/lib/system-gschemrc.scm:1466
+#: gschem/lib/system-gschemrc.scm:1467
#, fuzzy
msgid "B_W color scheme"
msgstr "_Schema colori scuri"
-#: gschem/lib/system-gschemrc.scm:1473
+#: gschem/lib/system-gschemrc.scm:1474
msgid "_Manager..."
msgstr "_Elenco"
-#: gschem/lib/system-gschemrc.scm:1474
+#: gschem/lib/system-gschemrc.scm:1475
msgid "_Previous"
msgstr "Pr_ecedente"
-#: gschem/lib/system-gschemrc.scm:1475
+#: gschem/lib/system-gschemrc.scm:1476
msgid "_Next"
msgstr "_Successivo"
-#: gschem/lib/system-gschemrc.scm:1476
+#: gschem/lib/system-gschemrc.scm:1477
msgid "Ne_w"
msgstr "N_uovo"
-#: gschem/lib/system-gschemrc.scm:1480
+#: gschem/lib/system-gschemrc.scm:1481
msgid "_Discard"
msgstr "_Scarta"
-#: gschem/lib/system-gschemrc.scm:1486
+#: gschem/lib/system-gschemrc.scm:1487
msgid "_Component..."
msgstr "_Componente"
-#: gschem/lib/system-gschemrc.scm:1487
+#: gschem/lib/system-gschemrc.scm:1488
msgid "_Net"
msgstr "_Net"
-#: gschem/lib/system-gschemrc.scm:1488
+#: gschem/lib/system-gschemrc.scm:1489
msgid "B_us"
msgstr "B_us"
-#: gschem/lib/system-gschemrc.scm:1489
+#: gschem/lib/system-gschemrc.scm:1490
msgid "_Attribute..."
msgstr "_Attributo"
-#: gschem/lib/system-gschemrc.scm:1490
+#: gschem/lib/system-gschemrc.scm:1491
msgid "_Text..."
msgstr "_Testo..."
-#: gschem/lib/system-gschemrc.scm:1492
+#: gschem/lib/system-gschemrc.scm:1493
msgid "_Line"
msgstr "_Linea"
-#: gschem/lib/system-gschemrc.scm:1493
+#: gschem/lib/system-gschemrc.scm:1494
msgid "_Box"
msgstr "_Rettangolo"
-#: gschem/lib/system-gschemrc.scm:1494
+#: gschem/lib/system-gschemrc.scm:1495
msgid "C_ircle"
msgstr "Cerch_io"
-#: gschem/lib/system-gschemrc.scm:1495
+#: gschem/lib/system-gschemrc.scm:1496
msgid "A_rc"
msgstr "A_rco"
-#: gschem/lib/system-gschemrc.scm:1496
+#: gschem/lib/system-gschemrc.scm:1497
msgid "_Pin"
msgstr "_Pin"
-#: gschem/lib/system-gschemrc.scm:1497
+#: gschem/lib/system-gschemrc.scm:1498
msgid "Pictu_re..."
msgstr "Imm_agine"
-#: gschem/lib/system-gschemrc.scm:1503
+#: gschem/lib/system-gschemrc.scm:1504
msgid "_Down Schematic"
msgstr "_Apri Schema"
-#: gschem/lib/system-gschemrc.scm:1504
+#: gschem/lib/system-gschemrc.scm:1505
msgid "Down _Symbol"
msgstr "Apri _Simbolo"
-#: gschem/lib/system-gschemrc.scm:1505
+#: gschem/lib/system-gschemrc.scm:1506
msgid "_Up"
msgstr "_Torna su"
-#: gschem/lib/system-gschemrc.scm:1506
+#: gschem/lib/system-gschemrc.scm:1507
msgid "D_ocumentation..."
msgstr "D_ocumentazione"
-#: gschem/lib/system-gschemrc.scm:1512
+#: gschem/lib/system-gschemrc.scm:1513
msgid "_Attach"
msgstr "_Collega"
-#: gschem/lib/system-gschemrc.scm:1513
+#: gschem/lib/system-gschemrc.scm:1514
msgid "_Detach"
msgstr "_Scollega"
-#: gschem/lib/system-gschemrc.scm:1514
+#: gschem/lib/system-gschemrc.scm:1515
msgid "Show _Value"
msgstr "Mostra _Valore"
-#: gschem/lib/system-gschemrc.scm:1515
+#: gschem/lib/system-gschemrc.scm:1516
msgid "Show _Name"
msgstr "Mostra _Nome"
-#: gschem/lib/system-gschemrc.scm:1516
+#: gschem/lib/system-gschemrc.scm:1517
msgid "Show _Both"
msgstr "Mostra _entrambi"
-#: gschem/lib/system-gschemrc.scm:1517
+#: gschem/lib/system-gschemrc.scm:1518
msgid "_Toggle Visibility"
msgstr "Commu_ta Visibilità "
-#: gschem/lib/system-gschemrc.scm:1519
+#: gschem/lib/system-gschemrc.scm:1520
msgid "_Find Specific Text..."
msgstr "_Trova testo specifico..."
-#: gschem/lib/system-gschemrc.scm:1520
+#: gschem/lib/system-gschemrc.scm:1521
msgid "_Hide Specific Text..."
msgstr "_Nascondi testo specifico..."
-#: gschem/lib/system-gschemrc.scm:1521
+#: gschem/lib/system-gschemrc.scm:1522
msgid "_Show Specific Text..."
msgstr "_Mostra testo specifico"
-#: gschem/lib/system-gschemrc.scm:1522
+#: gschem/lib/system-gschemrc.scm:1523
msgid "A_utonumber Text..."
msgstr "Testo di Autonimerazione"
-#: gschem/lib/system-gschemrc.scm:1528
+#: gschem/lib/system-gschemrc.scm:1529
msgid "_Text Size..."
msgstr "Dimensione _Testo"
-#: gschem/lib/system-gschemrc.scm:1529
+#: gschem/lib/system-gschemrc.scm:1530
msgid "Cycle _grid styles"
msgstr "Scorri stili _griglia"
-#: gschem/lib/system-gschemrc.scm:1530
+#: gschem/lib/system-gschemrc.scm:1531
msgid "Toggle _Snap On/Off"
msgstr "_Commuta aggancio automatico"
-#: gschem/lib/system-gschemrc.scm:1531
+#: gschem/lib/system-gschemrc.scm:1532
msgid "Snap Grid S_pacing..."
msgstr "S_paziatura griglia di aggancio"
-#: gschem/lib/system-gschemrc.scm:1532
+#: gschem/lib/system-gschemrc.scm:1533
msgid "Scale _up Grid Spacing"
msgstr "A_umenta spaziatura griglia"
-#: gschem/lib/system-gschemrc.scm:1534
+#: gschem/lib/system-gschemrc.scm:1535
msgid "Scale _down Grid Spacing"
msgstr "_Diminuisci spaziatura griglia"
-#: gschem/lib/system-gschemrc.scm:1536
+#: gschem/lib/system-gschemrc.scm:1537
msgid "Toggle _Outline/Box"
msgstr "C_ommuta disegno elementi/perimetro"
-#: gschem/lib/system-gschemrc.scm:1538
+#: gschem/lib/system-gschemrc.scm:1539
msgid "Toggle Net _Rubberband"
msgstr "Commuta Net _Elastiche"
-#: gschem/lib/system-gschemrc.scm:1539
+#: gschem/lib/system-gschemrc.scm:1540
msgid "Toggle _Magnetic Net"
msgstr "Commuta Net _Magnetiche"
-#: gschem/lib/system-gschemrc.scm:1540
+#: gschem/lib/system-gschemrc.scm:1541
msgid "Show _Log Window..."
msgstr "Visualizza finestra _Registro..."
-#: gschem/lib/system-gschemrc.scm:1542
+#: gschem/lib/system-gschemrc.scm:1543
msgid "Show _Coord Window..."
msgstr "Visualizza finestra _Coordinate..."
-#: gschem/lib/system-gschemrc.scm:1558
+#: gschem/lib/system-gschemrc.scm:1559
msgid "gEDA Docu_mentation..."
msgstr "Docu_mentazione di gEDA..."
-#: gschem/lib/system-gschemrc.scm:1559
+#: gschem/lib/system-gschemrc.scm:1560
msgid "gschem _FAQ..."
msgstr "_FAQ di gschem..."
-#: gschem/lib/system-gschemrc.scm:1560
+#: gschem/lib/system-gschemrc.scm:1561
msgid "gEDA _Wiki..."
msgstr "_Wiki di gEDA..."
-#: gschem/lib/system-gschemrc.scm:1561
+#: gschem/lib/system-gschemrc.scm:1562
msgid "Component D_ocumentation..."
msgstr "D_ocumentazione Componente..."
-#: gschem/lib/system-gschemrc.scm:1563
+#: gschem/lib/system-gschemrc.scm:1564
msgid "_Hotkeys..."
msgstr "Combina_zioni tasti..."
-#: gschem/lib/system-gschemrc.scm:1564
+#: gschem/lib/system-gschemrc.scm:1565
msgid "_About..."
msgstr "_Info su..."
-#: gschem/lib/system-gschemrc.scm:1570
+#: gschem/lib/system-gschemrc.scm:1571
msgid "_File"
msgstr "_File"
-#: gschem/lib/system-gschemrc.scm:1571
+#: gschem/lib/system-gschemrc.scm:1572
msgid "_Edit"
msgstr "Modifica"
-#: gschem/lib/system-gschemrc.scm:1572
+#: gschem/lib/system-gschemrc.scm:1573
msgid "_Buffer"
msgstr "_Buffer"
-#: gschem/lib/system-gschemrc.scm:1573
+#: gschem/lib/system-gschemrc.scm:1574
msgid "_View"
msgstr "_Vista"
-#: gschem/lib/system-gschemrc.scm:1574
+#: gschem/lib/system-gschemrc.scm:1575
msgid "_Page"
msgstr "_Pagina"
-#: gschem/lib/system-gschemrc.scm:1575
+#: gschem/lib/system-gschemrc.scm:1576
msgid "_Add"
msgstr "_Aggiungi"
-#: gschem/lib/system-gschemrc.scm:1576
+#: gschem/lib/system-gschemrc.scm:1577
msgid "Hie_rarchy"
msgstr "Ge_rarchia"
-#: gschem/lib/system-gschemrc.scm:1577
+#: gschem/lib/system-gschemrc.scm:1578
msgid "A_ttributes"
msgstr "A_ttributi"
-#: gschem/lib/system-gschemrc.scm:1578
+#: gschem/lib/system-gschemrc.scm:1579
msgid "_Options"
msgstr "_Opzioni"
-#: gschem/lib/system-gschemrc.scm:1579
+#: gschem/lib/system-gschemrc.scm:1580
msgid "_Help"
msgstr "Aiuto"
+#~ msgid "Scheme directory NOT set!\n"
+#~ msgstr "Cartelle degli schemi non impostata!\n"
+
+#~ msgid "MakeVisible"
+#~ msgstr "Rendi Visibile"
+
+#~ msgid ""
+#~ "Usage: %s [OPTIONS] schematic_filename1 ... schematic_filenameN\n"
+#~ " -q Quiet mode\n"
+#~ " -v Verbose mode on\n"
+#~ " -r filename Rc filename\n"
+#~ " -s filename Script (guile) filename\n"
+#~ " -o filename Output filename (for printing)\n"
+#~ " -p Automatically place the window\n"
+#~ " -t Print stroke information\n"
+#~ " -h Help; this message\n"
+#~ "\n"
+#~ msgstr ""
+#~ "Utilizzo: %s [OPZIONI] nomefile_schema1 ... nomefile_schemaN\n"
+#~ " -q Quiet mode\n"
+#~ " -v Verbose mode on\n"
+#~ " -r filename Rc filename\n"
+#~ " -s filename Script (guile) filename\n"
+#~ " -o filename Output filename (for printing)\n"
+#~ " -p Automatically place the window\n"
+#~ " -t Print stroke information\n"
+#~ " -h Help; this message\n"
+#~ "\n"
+
+#~ msgid "Couldn't open file %s\n"
+#~ msgstr "Non è possibile aprire il file %s\n"
+
+#~ msgid "Clear"
+#~ msgstr "Pulisci"
+
+#~ msgid "Make Inv Text Vis"
+#~ msgstr "Rendi Invisibile Testo Visibile"
+
#~ msgid "Update Cues"
#~ msgstr "Aggiorna intersezioni"
diff --git a/gschem/po/ja.po b/gschem/po/ja.po
index 7a6debb..37b6a0a 100644
--- a/gschem/po/ja.po
+++ b/gschem/po/ja.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2010-11-07 13:37+0000\n"
+"POT-Creation-Date: 2011-01-16 00:11-0500\n"
"PO-Revision-Date: 2010-02-14 01:03+0000\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -22,17 +22,17 @@ msgstr ""
msgid "Zoom too small! Cannot zoom further.\n"
msgstr "ã??ã??以ä¸?ã?ºã?¼ã? ã?§ã??ã?¾ã??ã??ã??\n"
-#: gschem/src/g_funcs.c:339 gschem/src/i_callbacks.c:68
+#: gschem/src/g_funcs.c:347 gschem/src/i_callbacks.c:68
#, c-format
msgid "Could not fork\n"
msgstr ""
-#: gschem/src/g_funcs.c:355 gschem/src/i_callbacks.c:78
+#: gschem/src/g_funcs.c:363 gschem/src/i_callbacks.c:78
#, c-format
msgid "Could not invoke %s\n"
msgstr ""
-#: gschem/src/g_funcs.c:361 gschem/src/i_callbacks.c:82
+#: gschem/src/g_funcs.c:369 gschem/src/i_callbacks.c:82
msgid "Documentation commands not supported under MinGW.\n"
msgstr ""
@@ -121,12 +121,12 @@ msgstr ""
msgid "Invalid number of steps [%d] scrollpan-steps\n"
msgstr ""
-#: gschem/src/gschem.c:184
+#: gschem/src/gschem.c:188
#, c-format
msgid "gEDA/gschem version %s%s.%s\n"
msgstr ""
-#: gschem/src/gschem.c:187
+#: gschem/src/gschem.c:191
msgid ""
"gEDA/gschem comes with ABSOLUTELY NO WARRANTY; see COPYING for more "
"details.\n"
@@ -134,14 +134,14 @@ msgstr ""
"gEDA/gschemã?¯å®?å?¨ã?«ç?¡ä¿?証ã?§æ??ä¾?ã??ã??ã?¾ã??ã??詳ã??ã??ã?¯COPYINGã??ã?¡ã?¤ã?«ã??ã??覧ã??ã? ã??"
"ã??ã??\n"
-#: gschem/src/gschem.c:189
+#: gschem/src/gschem.c:193
msgid ""
"This is free software, and you are welcome to redistribute it under certain\n"
msgstr ""
"ã??ã??ã?¯ã??ã?ªã?¼ã?½ã??ã??ã?¦ã?§ã?¢ã?§ã??ã??ã??ã??ã??æ?¡ä»¶ã?®ä¸?ã?§å??é ?å¸?ã??ã??ã??ã?¨ã??奨å?±ã??ã??ã?¦ã??ã?¾"
"ã??ã??\n"
-#: gschem/src/gschem.c:191
+#: gschem/src/gschem.c:195
msgid ""
"conditions; please see the COPYING file for more details.\n"
"\n"
@@ -149,17 +149,17 @@ msgstr ""
"詳ã??ã??ã?¯COPYINGã??ã?¡ã?¤ã?«ã??ã??覧ã??ã? ã??ã??ã??\n"
"\n"
-#: gschem/src/gschem.c:194
+#: gschem/src/gschem.c:198
#, c-format
msgid "This is the MINGW32 port.\n"
msgstr "MIGW32ç??ã?§ã??ã??\n"
-#: gschem/src/gschem.c:198
+#: gschem/src/gschem.c:202
#, c-format
msgid "Current locale settings: %s\n"
msgstr ""
-#: gschem/src/gschem.c:213
+#: gschem/src/gschem.c:218
msgid ""
"You must set the GEDADATA environment variable!\n"
"\n"
@@ -167,31 +167,21 @@ msgid ""
"environment variable to point to the correct location.\n"
msgstr ""
-#: gschem/src/gschem.c:248
+#: gschem/src/gschem.c:256
#, c-format
msgid "Couldn't find init scm file [%s]\n"
msgstr ""
-#: gschem/src/gschem.c:252
+#: gschem/src/gschem.c:260
#, c-format
msgid "Read init scm file [%s]\n"
msgstr "å??æ??å??scmã??ã?¡ã?¤ã?«ã??èªã?¿è¾¼ã??ã?§ã??ã?¾ã??ã??[%s]\n"
-#: gschem/src/gschem.c:256
+#: gschem/src/gschem.c:264
#, c-format
msgid "Failed to read init scm file [%s]\n"
msgstr "å??æ??å??scmã??ã?¡ã?¤ã?«ã?®èªã?¿è¾¼ã?¿ã?«å¤±æ??ã??[%s]\n"
-#: gschem/src/gschem.c:317
-#, c-format
-msgid "Scheme directory NOT set!\n"
-msgstr "schemeã??ã?£ã?¬ã?¯ã??ã?ªã??è¨å®?ã??ã??ã?¦ã??ã?¾ã??ã??!\n"
-
-#: gschem/src/gschem.c:324 gschem/src/x_script.c:66
-#, c-format
-msgid "Executing guile script [%s]\n"
-msgstr "guileã?¹ã?¯ã?ªã??ã??ã??å®?è¡?ã??ã?¦ã??ã?¾ã??ã??[%s]\n"
-
#: gschem/src/gschem_cairo.c:310
#, c-format
msgid "Unknown end for line (%d)\n"
@@ -215,11 +205,11 @@ msgstr "é?¨å??ã?¢ã?¼ã??"
msgid "Text Mode"
msgstr "ã??ã??ã??ã?¢ã?¼ã??"
-#: gschem/src/i_basic.c:84 gschem/lib/system-gschemrc.scm:1409
+#: gschem/src/i_basic.c:84 gschem/lib/system-gschemrc.scm:1411
msgid "Copy Mode"
msgstr "ã?³ã??ã?¼ã?¢ã?¼ã??"
-#: gschem/src/i_basic.c:87 gschem/lib/system-gschemrc.scm:1411
+#: gschem/src/i_basic.c:87 gschem/lib/system-gschemrc.scm:1413
msgid "Move Mode"
msgstr "移å??ã?¢ã?¼ã??"
@@ -227,7 +217,7 @@ msgstr "移å??ã?¢ã?¼ã??"
msgid "Rotate Mode"
msgstr "å??転ã?¢ã?¼ã??"
-#: gschem/src/i_basic.c:91 gschem/lib/system-gschemrc.scm:1413
+#: gschem/src/i_basic.c:91 gschem/lib/system-gschemrc.scm:1415
msgid "Mirror Mode"
msgstr "å??転ã?¢ã?¼ã??"
@@ -280,22 +270,22 @@ msgstr "å??弧ã?¢ã?¼ã??"
msgid "Pin Mode"
msgstr "ã??ã?³ã?¢ã?¼ã??"
-#: gschem/src/i_basic.c:135 gschem/src/i_callbacks.c:544
-#: gschem/src/i_callbacks.c:568
+#: gschem/src/i_basic.c:135 gschem/src/i_callbacks.c:576
+#: gschem/src/i_callbacks.c:600
msgid "Copy"
msgstr "ã?³ã??ã?¼"
-#: gschem/src/i_basic.c:137 gschem/src/i_callbacks.c:634
-#: gschem/src/i_callbacks.c:658
+#: gschem/src/i_basic.c:137 gschem/src/i_callbacks.c:666
+#: gschem/src/i_callbacks.c:690
msgid "Move"
msgstr "移å??"
-#: gschem/src/i_basic.c:139 gschem/src/i_callbacks.c:589
-#: gschem/src/i_callbacks.c:613
+#: gschem/src/i_basic.c:139 gschem/src/i_callbacks.c:621
+#: gschem/src/i_callbacks.c:645
msgid "Multiple Copy"
msgstr ""
-#: gschem/src/i_basic.c:142 gschem/lib/system-gschemrc.scm:1410
+#: gschem/src/i_basic.c:142 gschem/lib/system-gschemrc.scm:1412
msgid "Multiple Copy Mode"
msgstr ""
@@ -315,7 +305,7 @@ msgstr ""
msgid "Action"
msgstr "�����"
-#: gschem/src/i_basic.c:260 gschem/src/x_dialog.c:2312
+#: gschem/src/i_basic.c:260 gschem/src/x_dialog.c:2316
#: gschem/src/x_window.c:491
msgid "Stroke"
msgstr "ã?¹ã??ã?ã?¼ã?¯"
@@ -346,7 +336,7 @@ msgstr ""
msgid "Documentation for [%s,%s,%s,%s]\n"
msgstr ""
-#: gschem/src/i_callbacks.c:123 gschem/src/i_callbacks.c:1699
+#: gschem/src/i_callbacks.c:123 gschem/src/i_callbacks.c:1706
#, c-format
msgid "New page created [%s]\n"
msgstr ""
@@ -368,69 +358,69 @@ msgstr "ã??ã?¹ã?¦ä¿?å?"
msgid "Closing Window\n"
msgstr "ã?¦ã?£ã?³ã??ã?¦ã??é??ã??ã?¦ã??ã?¾ã??ã??\n"
-#: gschem/src/i_callbacks.c:549 gschem/src/i_callbacks.c:594
-#: gschem/src/i_callbacks.c:639
+#: gschem/src/i_callbacks.c:581 gschem/src/i_callbacks.c:626
+#: gschem/src/i_callbacks.c:671
msgid "Select objs first"
msgstr "ã?¾ã??ã?ªã??ã?¸ã?§ã?¯ã??ã??é?¸æ??ã??ã?¦ã??ã? ã??ã??ã??"
-#: gschem/src/i_callbacks.c:678 gschem/src/x_multiattrib.c:1491
+#: gschem/src/i_callbacks.c:710 gschem/src/x_multiattrib.c:1503
msgid "Delete"
msgstr "å??é?¤"
-#: gschem/src/i_callbacks.c:703
+#: gschem/src/i_callbacks.c:735
msgid "Edit"
msgstr "ç·¨é??"
-#: gschem/src/i_callbacks.c:718
+#: gschem/src/i_callbacks.c:750
msgid "Edit pin type"
msgstr ""
-#: gschem/src/i_callbacks.c:737
+#: gschem/src/i_callbacks.c:769
msgid "Edit Text"
msgstr "ã??ã?ã?¹ã??ç·¨é??"
-#: gschem/src/i_callbacks.c:760
+#: gschem/src/i_callbacks.c:792
msgid "Slot"
msgstr "ã?¹ã?ã??ã??"
-#: gschem/src/i_callbacks.c:777
+#: gschem/src/i_callbacks.c:809
msgid "Color"
msgstr "è?²"
-#: gschem/src/i_callbacks.c:814 gschem/src/i_callbacks.c:859
+#: gschem/src/i_callbacks.c:846 gschem/src/i_callbacks.c:891
msgid "Rotate"
msgstr "å??転"
-#: gschem/src/i_callbacks.c:882 gschem/src/i_callbacks.c:907
+#: gschem/src/i_callbacks.c:913 gschem/src/i_callbacks.c:938
msgid "Mirror"
msgstr "å??転"
-#: gschem/src/i_callbacks.c:928 gschem/src/x_dialog.c:2315
-#: gschem/lib/system-gschemrc.scm:1422
+#: gschem/src/i_callbacks.c:959 gschem/src/x_dialog.c:2319
+#: gschem/lib/system-gschemrc.scm:1424
msgid "Lock"
msgstr "ã?ã??ã?¯"
-#: gschem/src/i_callbacks.c:946 gschem/lib/system-gschemrc.scm:1423
+#: gschem/src/i_callbacks.c:977 gschem/lib/system-gschemrc.scm:1425
msgid "Unlock"
msgstr "ã?ã??ã?¯è§£é?¤"
-#: gschem/src/i_callbacks.c:964 gschem/src/x_dialog.c:1734
+#: gschem/src/i_callbacks.c:995 gschem/src/x_dialog.c:1737
msgid "Translate"
msgstr "転é??"
-#: gschem/src/i_callbacks.c:967
+#: gschem/src/i_callbacks.c:998
msgid "WARNING: Do not translate with snap off!\n"
msgstr "è¦å??:ã?¹ã??ã??ã??ã?»ã?ªã??ã?§è»¢é??ã??ã?ªã??ã?§ã??ã? ã??ã??!\n"
-#: gschem/src/i_callbacks.c:968
+#: gschem/src/i_callbacks.c:999
msgid "WARNING: Turning snap on and continuing with translate.\n"
msgstr "è¦å??:ã?¹ã??ã??ã??ã??ã?ªã?³ã??ã?¦ã??ã??転é??ã??ã?¦ã??ã? ã??ã??ã??\n"
-#: gschem/src/i_callbacks.c:975
+#: gschem/src/i_callbacks.c:1006
msgid "WARNING: Snap grid size is not equal to 100!\n"
msgstr "è¦å??:ã?°ã?ªã??ã??ã?µã?¤ã?ºã??100ã?§ã?¯ã??ã??ã?¾ã??ã??!\n"
-#: gschem/src/i_callbacks.c:977
+#: gschem/src/i_callbacks.c:1008
msgid ""
"WARNING: If you are translating a symbol to the origin, the snap grid size "
"should be set to 100\n"
@@ -438,259 +428,255 @@ msgstr ""
"è¦å??:å??ç?¹ã?¸è»¢é??ã??ã??ã?¨ã??ã?¯ã?¹ã??ã??ã??ã?®ã?°ã?ªã??ã??ã?µã?¤ã?ºã??\n"
"100ã?«è¨å®?ã??ã?¦ã??ã? ã??ã??ã??\n"
-#: gschem/src/i_callbacks.c:1008
+#: gschem/src/i_callbacks.c:1039
msgid "Embed"
msgstr "��込�"
-#: gschem/src/i_callbacks.c:1047
+#: gschem/src/i_callbacks.c:1078
msgid "Unembed"
msgstr "��込�解�"
-#: gschem/src/i_callbacks.c:1089
+#: gschem/src/i_callbacks.c:1120
msgid "Update"
msgstr "æ?´æ?°"
-#: gschem/src/i_callbacks.c:1136
+#: gschem/src/i_callbacks.c:1167
msgid "ShowHidden"
msgstr "é? ã??ã??ã?ã?¹ã??表示"
-#: gschem/src/i_callbacks.c:1160
-msgid "MakeVisible"
-msgstr "表示ã??ã??"
-
-#: gschem/src/i_callbacks.c:1466 gschem/src/i_callbacks.c:1538
+#: gschem/src/i_callbacks.c:1473 gschem/src/i_callbacks.c:1545
msgid "Pan"
msgstr "ã??ã?³"
-#: gschem/src/i_callbacks.c:1743
+#: gschem/src/i_callbacks.c:1750
msgid "Really revert page?"
msgstr ""
-#: gschem/src/i_callbacks.c:1813
+#: gschem/src/i_callbacks.c:1820
msgid "Copy to clipboard"
msgstr ""
-#: gschem/src/i_callbacks.c:1831
+#: gschem/src/i_callbacks.c:1838
msgid "Cut to clipboard"
msgstr ""
-#: gschem/src/i_callbacks.c:1849
+#: gschem/src/i_callbacks.c:1856
msgid "Paste from clipboard"
msgstr ""
-#: gschem/src/i_callbacks.c:1861 gschem/src/i_callbacks.c:2100
-#: gschem/src/i_callbacks.c:2122 gschem/src/i_callbacks.c:2144
-#: gschem/src/i_callbacks.c:2166 gschem/src/i_callbacks.c:2188
+#: gschem/src/i_callbacks.c:1868 gschem/src/i_callbacks.c:2107
+#: gschem/src/i_callbacks.c:2129 gschem/src/i_callbacks.c:2151
+#: gschem/src/i_callbacks.c:2173 gschem/src/i_callbacks.c:2195
msgid "Empty buffer"
msgstr "ã??ã??ã??ã?¡ã??空ã?§ã??ã??"
-#: gschem/src/i_callbacks.c:1906
+#: gschem/src/i_callbacks.c:1913
msgid "Copy 1"
msgstr "ã?³ã??ã?¼1"
-#: gschem/src/i_callbacks.c:1925
+#: gschem/src/i_callbacks.c:1932
msgid "Copy 2"
msgstr "ã?³ã??ã?¼2"
-#: gschem/src/i_callbacks.c:1944
+#: gschem/src/i_callbacks.c:1951
msgid "Copy 3"
msgstr "ã?³ã??ã?¼3"
-#: gschem/src/i_callbacks.c:1963
+#: gschem/src/i_callbacks.c:1970
msgid "Copy 4"
msgstr "ã?³ã??ã?¼4"
-#: gschem/src/i_callbacks.c:1982
+#: gschem/src/i_callbacks.c:1989
msgid "Copy 5"
msgstr "ã?³ã??ã?¼5"
-#: gschem/src/i_callbacks.c:2001
+#: gschem/src/i_callbacks.c:2008
msgid "Cut 1"
msgstr "ã?«ã??ã??1"
-#: gschem/src/i_callbacks.c:2020
+#: gschem/src/i_callbacks.c:2027
msgid "Cut 2"
msgstr "ã?«ã??ã??2"
-#: gschem/src/i_callbacks.c:2039
+#: gschem/src/i_callbacks.c:2046
msgid "Cut 3"
msgstr "ã?«ã??ã??3"
-#: gschem/src/i_callbacks.c:2058
+#: gschem/src/i_callbacks.c:2065
msgid "Cut 4"
msgstr "ã?«ã??ã??4"
-#: gschem/src/i_callbacks.c:2077
+#: gschem/src/i_callbacks.c:2084
msgid "Cut 5"
msgstr "ã?«ã??ã??5"
-#: gschem/src/i_callbacks.c:2093
+#: gschem/src/i_callbacks.c:2100
msgid "Paste 1"
msgstr "ã??ã?¼ã?¹ã??1"
-#: gschem/src/i_callbacks.c:2115
+#: gschem/src/i_callbacks.c:2122
msgid "Paste 2"
msgstr "ã??ã?¼ã?¹ã?? 2"
-#: gschem/src/i_callbacks.c:2137
+#: gschem/src/i_callbacks.c:2144
msgid "Paste 3"
msgstr "ã??ã?¼ã?¹ã?? 3"
-#: gschem/src/i_callbacks.c:2159
+#: gschem/src/i_callbacks.c:2166
msgid "Paste 4"
msgstr "ã??ã?¼ã?¹ã?? 4"
-#: gschem/src/i_callbacks.c:2181
+#: gschem/src/i_callbacks.c:2188
msgid "Paste 5"
msgstr "ã??ã?¼ã?¹ã?? 5"
-#: gschem/src/i_callbacks.c:2318 gschem/src/x_window.c:355
+#: gschem/src/i_callbacks.c:2325 gschem/src/x_window.c:355
msgid "Component"
msgstr "é?¨å??"
-#: gschem/src/i_callbacks.c:2354 gschem/src/i_callbacks.c:2373
-#: gschem/src/x_dialog.c:2285
+#: gschem/src/i_callbacks.c:2361 gschem/src/i_callbacks.c:2380
+#: gschem/src/x_dialog.c:2289
msgid "Attribute"
msgstr "ã?¢ã??ã?ªã??ã?¥ã?¼ã??"
-#: gschem/src/i_callbacks.c:2395 gschem/src/i_callbacks.c:2422
-#: gschem/src/x_dialog.c:2282
+#: gschem/src/i_callbacks.c:2402 gschem/src/i_callbacks.c:2429
+#: gschem/src/x_dialog.c:2286
msgid "Net"
msgstr "ã??ã??ã??"
-#: gschem/src/i_callbacks.c:2466 gschem/src/i_callbacks.c:2493
-#: gschem/src/x_dialog.c:2300 gschem/src/x_window.c:375
+#: gschem/src/i_callbacks.c:2473 gschem/src/i_callbacks.c:2500
+#: gschem/src/x_dialog.c:2304 gschem/src/x_window.c:375
msgid "Bus"
msgstr "ã??ã?¹"
-#: gschem/src/i_callbacks.c:2574 gschem/src/i_callbacks.c:2597
+#: gschem/src/i_callbacks.c:2581 gschem/src/i_callbacks.c:2604
msgid "Line"
msgstr "ç·?"
-#: gschem/src/i_callbacks.c:2619 gschem/src/i_callbacks.c:2642
+#: gschem/src/i_callbacks.c:2626 gschem/src/i_callbacks.c:2649
msgid "Box"
msgstr "ã??ã??ã?¯ã?¹"
-#: gschem/src/i_callbacks.c:2698 gschem/src/i_callbacks.c:2722
+#: gschem/src/i_callbacks.c:2705 gschem/src/i_callbacks.c:2729
msgid "Circle"
msgstr "å??"
-#: gschem/src/i_callbacks.c:2744 gschem/src/i_callbacks.c:2767
+#: gschem/src/i_callbacks.c:2751 gschem/src/i_callbacks.c:2774
msgid "Arc"
msgstr "å??弧"
-#: gschem/src/i_callbacks.c:2789 gschem/src/i_callbacks.c:2812
-#: gschem/src/x_dialog.c:2273
+#: gschem/src/i_callbacks.c:2796 gschem/src/i_callbacks.c:2819
+#: gschem/src/x_dialog.c:2277
msgid "Pin"
msgstr "ã??ã?³"
-#: gschem/src/i_callbacks.c:2871
+#: gschem/src/i_callbacks.c:2878
#, c-format
msgid "Searching for source [%s]\n"
msgstr "ã?½ã?¼ã?¹æ¤?ç´¢ä¸[%s]\n"
-#: gschem/src/i_callbacks.c:2895
+#: gschem/src/i_callbacks.c:2902
#, c-format
msgid "Cannot find source [%s]\n"
msgstr "ã?½ã?¼ã?¹ã??è¦?ä»?ã??ã??ã?¾ã??ã??ã??[%s]\n"
-#: gschem/src/i_callbacks.c:2964
+#: gschem/src/i_callbacks.c:2965
#, c-format
msgid "Searching for symbol [%s]\n"
msgstr "ã?·ã?³ã??ã?«æ¤?ç´¢ä¸[%s]\n"
-#: gschem/src/i_callbacks.c:2970
+#: gschem/src/i_callbacks.c:2971
msgid "Symbol is not a real file. Symbol cannot be loaded.\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3001
+#: gschem/src/i_callbacks.c:3002
msgid "Cannot find any schematics above the current one!\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3055
+#: gschem/src/i_callbacks.c:3056
msgid ""
"This command retrieves the component documentation from the web, but there "
"is no component selected"
msgstr ""
-#: gschem/src/i_callbacks.c:3083
+#: gschem/src/i_callbacks.c:3084
msgid "Attach"
msgstr "ã?¢ã?¿ã??ã??"
-#: gschem/src/i_callbacks.c:3130
+#: gschem/src/i_callbacks.c:3131
msgid "Detach"
msgstr "ã?¢ã?¿ã??ã??解é?¤"
-#: gschem/src/i_callbacks.c:3165
+#: gschem/src/i_callbacks.c:3166
msgid "ShowN"
msgstr "N表示"
-#: gschem/src/i_callbacks.c:3201
+#: gschem/src/i_callbacks.c:3202
msgid "ShowV"
msgstr "表示V"
-#: gschem/src/i_callbacks.c:3237
+#: gschem/src/i_callbacks.c:3238
msgid "ShowB"
msgstr "表示B"
-#: gschem/src/i_callbacks.c:3274
+#: gschem/src/i_callbacks.c:3275
msgid "VisToggle"
msgstr "表示å??æ?¿ã??"
-#: gschem/src/i_callbacks.c:3304
+#: gschem/src/i_callbacks.c:3305
#, c-format
msgid "Sorry but this is a non-functioning menu option\n"
msgstr "æ©?è?½ã??ã?ªã??ã?¡ã??ã?¥ã?¼ã?ªã??ã?·ã?§ã?³ã?§ã??ã??\n"
-#: gschem/src/i_callbacks.c:3394
+#: gschem/src/i_callbacks.c:3395
msgid "Action feedback mode set to OUTLINE\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3397
+#: gschem/src/i_callbacks.c:3398
msgid "Action feedback mode set to BOUNDINGBOX\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3422
+#: gschem/src/i_callbacks.c:3423
msgid "Grid OFF\n"
msgstr "ã?°ã?ªã??ã??ã?»ã?ªã??\n"
-#: gschem/src/i_callbacks.c:3423
+#: gschem/src/i_callbacks.c:3424
msgid "Dot grid selected\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3424
+#: gschem/src/i_callbacks.c:3425
msgid "Mesh grid selected\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3445
+#: gschem/src/i_callbacks.c:3446
msgid "Snap OFF (CAUTION!)\n"
msgstr "ã?¹ã??ã??ã??ã?»ã?ªã??(注æ??!)\n"
-#: gschem/src/i_callbacks.c:3448
+#: gschem/src/i_callbacks.c:3449
msgid "Snap ON\n"
msgstr "ã?¹ã??ã??ã??ã?»ã?ªã?³\n"
-#: gschem/src/i_callbacks.c:3451
+#: gschem/src/i_callbacks.c:3452
msgid "Snap back to the grid (CAUTION!)\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3477
+#: gschem/src/i_callbacks.c:3478
msgid "Rubber band OFF \n"
msgstr "ã?©ã??ã?¼ã??ã?³ã??ã?»ã?ªã?? \n"
-#: gschem/src/i_callbacks.c:3480
+#: gschem/src/i_callbacks.c:3481
msgid "Rubber band ON\n"
msgstr "ã?©ã??ã?¼ã??ã?³ã??ã?»ã?ªã?³\n"
-#: gschem/src/i_callbacks.c:3495
+#: gschem/src/i_callbacks.c:3496
msgid "magnetic net mode: ON\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3498
+#: gschem/src/i_callbacks.c:3499
msgid "magnetic net mode: OFF\n"
msgstr ""
-#: gschem/src/o_box.c:153
+#: gschem/src/o_box.c:149
#, c-format
msgid "Unknown type for box (fill)!\n"
msgstr "ä¸?æ??ã?ªã??ã??ã?¯ã?¹ã?®ç¨®é¡?(å¡?ã??ã?¤ã?¶ã??)!\n"
@@ -710,17 +696,17 @@ msgstr ""
msgid "Got an invalid buffer_number [o_buffer_paste_start]\n"
msgstr ""
-#: gschem/src/o_bus.c:118
+#: gschem/src/o_bus.c:117
#, c-format
msgid "Got an invalid which one in o_bus_draw_stretch\n"
msgstr ""
-#: gschem/src/o_circle.c:134
+#: gschem/src/o_circle.c:130
#, c-format
msgid "Unknown type for circle (fill)!\n"
msgstr "ä¸?æ??ã?ªå??ã?®ç¨®é¡?(å¡?ã??ã?¤ã?¶ã??)!\n"
-#: gschem/src/o_complex.c:243 gschem/src/o_complex.c:247
+#: gschem/src/o_complex.c:237 gschem/src/o_complex.c:241
#, c-format
msgid "Translating schematic [%d %d]\n"
msgstr "ã?¹ã?±ã??ã??ã??ã?¯ã??転é??ã??ã?¦ã??ã?¾ã??ã??[%d %d]\n"
@@ -738,35 +724,35 @@ msgstr ""
msgid "Object already unlocked\n"
msgstr ""
-#: gschem/src/o_misc.c:413
+#: gschem/src/o_misc.c:409
msgid "Hidden text is now visible\n"
msgstr "é? ã??ã??ã?ã?¹ã??ã??表示ã??ã??ã?¾ã??ã??ã??\n"
-#: gschem/src/o_misc.c:415
+#: gschem/src/o_misc.c:411
msgid "Hidden text is now invisible\n"
msgstr "é? ã??ã??ã?ã?¹ã??ã??é??表示ã?«ã?ªã??ã?¾ã??ã??ã??\n"
-#: gschem/src/o_misc.c:668
+#: gschem/src/o_misc.c:636
#, c-format
msgid "Could not find symbol [%s] in library. Update failed.\n"
msgstr ""
-#: gschem/src/o_misc.c:783
+#: gschem/src/o_misc.c:751
#, c-format
msgid "o_autosave_backups: Can't get the real filename of %s."
msgstr ""
-#: gschem/src/o_misc.c:827
+#: gschem/src/o_misc.c:795
#, c-format
msgid "Could NOT set previous backup file [%s] read-write\n"
msgstr ""
-#: gschem/src/o_misc.c:845
+#: gschem/src/o_misc.c:815
#, c-format
msgid "Could NOT set backup file [%s] readonly\n"
msgstr ""
-#: gschem/src/o_misc.c:850
+#: gschem/src/o_misc.c:820
#, c-format
msgid "Could NOT save backup file [%s]\n"
msgstr ""
@@ -786,36 +772,36 @@ msgstr ""
msgid "Got a non line object in o_move_check_endpoint\n"
msgstr ""
-#: gschem/src/o_net.c:159
+#: gschem/src/o_net.c:158
#, c-format
msgid "Got an invalid which one in o_net_draw_stretch\n"
msgstr ""
-#: gschem/src/o_net.c:538
+#: gschem/src/o_net.c:537
msgid "Warning: Starting net at off grid coordinate\n"
msgstr ""
-#: gschem/src/o_net.c:600
+#: gschem/src/o_net.c:599
msgid "Warning: Ending net at off grid coordinate\n"
msgstr ""
-#: gschem/src/o_net.c:932 gschem/src/o_net.c:969 gschem/src/o_net.c:1040
-#: gschem/src/o_net.c:1076
+#: gschem/src/o_net.c:931 gschem/src/o_net.c:968 gschem/src/o_net.c:1039
+#: gschem/src/o_net.c:1075
#, c-format
msgid "Tried to add more than two bus rippers. Internal gschem error.\n"
msgstr ""
-#: gschem/src/o_net.c:1144
+#: gschem/src/o_net.c:1143
#, c-format
msgid "Bus ripper symbol [%s] was not found in any component library\n"
msgstr ""
-#: gschem/src/o_path.c:352
+#: gschem/src/o_path.c:348
#, c-format
msgid "Unknown type for path (fill)!\n"
msgstr ""
-#: gschem/src/o_picture.c:163 gschem/src/o_picture.c:539
+#: gschem/src/o_picture.c:163 gschem/src/o_picture.c:537
#, c-format
msgid "Failed to load picture: %s"
msgstr ""
@@ -824,7 +810,7 @@ msgstr ""
msgid "Picture"
msgstr ""
-#: gschem/src/o_picture.c:447 gschem/src/x_attribedit.c:141
+#: gschem/src/o_picture.c:445 gschem/src/x_attribedit.c:141
#, c-format
msgid "ERROR: NULL object!\n"
msgstr ""
@@ -845,23 +831,45 @@ msgstr "ã??ã?®é?¨å??ã?«ã?¹ã?ã??ã??ã?¯è¨±å?¯ã??ã??ã?¦ã??ã?¾ã??ã??ã??\n"
msgid "New slot number out of range\n"
msgstr "ã?¹ã?ã??ã??ç?ªå?·ã??ç¯?å?²ã??è¶?ã??ã?¦ã??ã?¾ã??ã??\n"
-#: gschem/src/o_undo.c:304
+#: gschem/src/o_undo.c:303
msgid "Undo/Redo disabled in rc file\n"
msgstr "ã?¢ã?³ã??ã?¥/ã?ªã??ã?¥ã?¯rcã??ã?¡ã?¤ã?«ã?§ç?¡å?¹ã?«è¨å®?ã??ã??ã?¦ã??ã?¾ã??ã??\n"
-#: gschem/src/parsecmd.c:47
+#: gschem/src/parsecmd.c:81
#, c-format
msgid ""
-"Usage: %s [OPTIONS] schematic_filename1 ... schematic_filenameN\n"
-" -q Quiet mode\n"
-" -v Verbose mode on\n"
-" -r filename Rc filename\n"
-" -s filename Script (guile) filename\n"
-" -o filename Output filename (for printing)\n"
-" -p Automatically place the window\n"
-" -t Print stroke information\n"
-" -h Help; this message\n"
+"Usage: %s [OPTION ...] [--] [FILE ...]\n"
+"\n"
+"Interactively edit gEDA schematics or symbols. If one or more FILEs\n"
+"are specified, open them for editing; otherwise, create a new, empty\n"
+"schematic.\n"
"\n"
+"Options:\n"
+" -q, --quiet Quiet mode.\n"
+" -v, --verbose Verbose mode.\n"
+" -r, --config-file=FILE Additional configuration file to load.\n"
+" -L DIR Add DIR to Scheme search path.\n"
+" -c EXPR Scheme expression to run at startup.\n"
+" -s FILE Scheme script to run at startup.\n"
+" -o, --output=FILE Output filename (for printing).\n"
+" -p Automatically place the window.\n"
+" -V, --version Show version information.\n"
+" -h, --help Help; this message.\n"
+" -- Treat all remaining arguments as filenames.\n"
+"\n"
+"Report bugs to <geda-bug@xxxxxxxx>\n"
+"gEDA/gaf homepage: <http://gpleda.org>\n"
+msgstr ""
+
+#: gschem/src/parsecmd.c:115
+#, c-format
+msgid ""
+"gEDA %s (g%.7s)\n"
+"Copyright (C) 1998-2011 gEDA developers\n"
+"This is free software, and you are welcome to redistribute it under\n"
+"certain conditions. For details, see the file `COPYING', which is\n"
+"included in the gEDA distribution.\n"
+"There is NO WARRANTY, to the extent permitted by law.\n"
msgstr ""
#: gschem/src/x_attribedit.c:127
@@ -873,56 +881,56 @@ msgstr ""
msgid "Single Attribute Editor"
msgstr "ã?·ã?³ã?°ã?«ã?¢ã??ã?«ã??ã?¥ã?¼ã??ã?¨ã??ã?£ã?¿"
-#: gschem/src/x_attribedit.c:358
+#: gschem/src/x_attribedit.c:359
msgid "<b>Edit Attribute</b>"
msgstr ""
-#: gschem/src/x_attribedit.c:360
+#: gschem/src/x_attribedit.c:361
msgid "<b>Add Attribute</b>"
msgstr ""
-#: gschem/src/x_attribedit.c:376 gschem/src/x_multiattrib.c:1916
+#: gschem/src/x_attribedit.c:377 gschem/src/x_multiattrib.c:1927
msgid "Name:"
msgstr "å??å??:"
-#: gschem/src/x_attribedit.c:393 gschem/src/x_multiattrib.c:1935
+#: gschem/src/x_attribedit.c:394 gschem/src/x_multiattrib.c:1946
msgid "Value:"
msgstr "å?¤:"
-#: gschem/src/x_attribedit.c:409 gschem/src/x_multiattrib.c:1978
+#: gschem/src/x_attribedit.c:410 gschem/src/x_multiattrib.c:1989
msgid "Visible"
msgstr "表示"
-#: gschem/src/x_attribedit.c:429
+#: gschem/src/x_attribedit.c:430
msgid "Show Value Only"
msgstr "���表示"
-#: gschem/src/x_attribedit.c:431
+#: gschem/src/x_attribedit.c:432
msgid "Show Name Only"
msgstr "å??å??ã?®ã?¿è¡¨ç¤º"
-#: gschem/src/x_attribedit.c:433 gschem/src/x_multiattrib.c:1454
+#: gschem/src/x_attribedit.c:434 gschem/src/x_multiattrib.c:1466
msgid "Show Name & Value"
msgstr "å??å??ã?¨å?¤ã??表示"
-#: gschem/src/x_attribedit.c:440
+#: gschem/src/x_attribedit.c:441
msgid "<b>Attach Options</b>"
msgstr ""
-#: gschem/src/x_attribedit.c:455
+#: gschem/src/x_attribedit.c:456
msgid "All"
msgstr "ã??ã?¹ã?¦"
-#: gschem/src/x_attribedit.c:463 gschem/src/x_compselect.c:896
-#: gschem/src/x_compselect.c:1010
+#: gschem/src/x_attribedit.c:464 gschem/src/x_compselect.c:904
+#: gschem/src/x_compselect.c:1018
msgid "Components"
msgstr "é?¨å??"
-#: gschem/src/x_attribedit.c:471 gschem/src/x_window.c:365
+#: gschem/src/x_attribedit.c:472 gschem/src/x_window.c:365
msgid "Nets"
msgstr "ã??ã??ã??"
-#: gschem/src/x_attribedit.c:479
+#: gschem/src/x_attribedit.c:480
msgid "Replace existing attributes"
msgstr ""
@@ -938,91 +946,91 @@ msgid ""
"duplicate slot may cause problems: [symbolname=%s, number=%d, slot=%d]\n"
msgstr ""
-#: gschem/src/x_autonumber.c:673
+#: gschem/src/x_autonumber.c:675
msgid "No searchstring given in autonumber text.\n"
msgstr ""
-#: gschem/src/x_autonumber.c:725
+#: gschem/src/x_autonumber.c:727
msgid "No '*' or '?' given at the end of the autonumber text.\n"
msgstr ""
-#: gschem/src/x_autonumber.c:860
+#: gschem/src/x_autonumber.c:862
msgid "Diagonal"
msgstr ""
-#: gschem/src/x_autonumber.c:861
+#: gschem/src/x_autonumber.c:863
msgid "Top to bottom"
msgstr ""
-#: gschem/src/x_autonumber.c:861
+#: gschem/src/x_autonumber.c:863
msgid "Bottom to top"
msgstr ""
-#: gschem/src/x_autonumber.c:862
+#: gschem/src/x_autonumber.c:864
msgid "Left to right"
msgstr ""
-#: gschem/src/x_autonumber.c:862
+#: gschem/src/x_autonumber.c:864
msgid "Right to left"
msgstr ""
-#: gschem/src/x_autonumber.c:863
+#: gschem/src/x_autonumber.c:865
msgid "File order"
msgstr ""
-#: gschem/src/x_autonumber.c:1199
+#: gschem/src/x_autonumber.c:1201
msgid "Autonumber text"
msgstr "ã?ªã?¼ã??ã??ã?³ã??ã?¼ã??ã?ã?¹ã??"
-#: gschem/src/x_autonumber.c:1223
+#: gschem/src/x_autonumber.c:1225
msgid "<b>Scope</b>"
msgstr ""
-#: gschem/src/x_autonumber.c:1245
+#: gschem/src/x_autonumber.c:1247
msgid "Search for:"
msgstr ""
-#: gschem/src/x_autonumber.c:1259
+#: gschem/src/x_autonumber.c:1261
msgid "Autonumber text in:"
msgstr ""
-#: gschem/src/x_autonumber.c:1266
+#: gschem/src/x_autonumber.c:1268
msgid "Skip numbers found in:"
msgstr ""
-#: gschem/src/x_autonumber.c:1278 gschem/src/x_autonumber.c:1287
+#: gschem/src/x_autonumber.c:1280 gschem/src/x_autonumber.c:1289
msgid "Selected objects"
msgstr ""
-#: gschem/src/x_autonumber.c:1279 gschem/src/x_autonumber.c:1288
+#: gschem/src/x_autonumber.c:1281 gschem/src/x_autonumber.c:1290
msgid "Current page"
msgstr ""
-#: gschem/src/x_autonumber.c:1280 gschem/src/x_autonumber.c:1289
+#: gschem/src/x_autonumber.c:1282 gschem/src/x_autonumber.c:1291
msgid "Whole hierarchy"
msgstr ""
-#: gschem/src/x_autonumber.c:1291
+#: gschem/src/x_autonumber.c:1293
msgid "Overwrite existing numbers"
msgstr ""
-#: gschem/src/x_autonumber.c:1296
+#: gschem/src/x_autonumber.c:1298
msgid "<b>Options</b>"
msgstr ""
-#: gschem/src/x_autonumber.c:1318
+#: gschem/src/x_autonumber.c:1320
msgid "Starting number:"
msgstr ""
-#: gschem/src/x_autonumber.c:1325
+#: gschem/src/x_autonumber.c:1327
msgid "Sort order:"
msgstr ""
-#: gschem/src/x_autonumber.c:1346
+#: gschem/src/x_autonumber.c:1348
msgid "Remove numbers"
msgstr ""
-#: gschem/src/x_autonumber.c:1350
+#: gschem/src/x_autonumber.c:1352
msgid "Automatic slotting"
msgstr ""
@@ -1059,48 +1067,48 @@ msgstr "ç?¡å?¹ã?ªè?²ã?®æ??å®?ã?§ã??ã?? : %d\n"
msgid "Tried to get an invalid outline color: %d\n"
msgstr ""
-#: gschem/src/x_compselect.c:1040
+#: gschem/src/x_compselect.c:1048
msgid "Filter:"
msgstr ""
-#: gschem/src/x_compselect.c:1143 gschem/src/x_dialog.c:3663
-#: gschem/src/x_multiattrib.c:1782
+#: gschem/src/x_compselect.c:1151 gschem/src/x_dialog.c:3667
+#: gschem/src/x_multiattrib.c:1793
msgid "Name"
msgstr "å??å??"
-#: gschem/src/x_compselect.c:1152 gschem/src/x_multiattrib.c:1806
+#: gschem/src/x_compselect.c:1160 gschem/src/x_multiattrib.c:1817
msgid "Value"
msgstr "å?¤"
-#: gschem/src/x_compselect.c:1191
+#: gschem/src/x_compselect.c:1199
msgid "Default behavior - reference component"
msgstr ""
-#: gschem/src/x_compselect.c:1194
+#: gschem/src/x_compselect.c:1202
msgid "Embed component in schematic"
msgstr ""
-#: gschem/src/x_compselect.c:1197
+#: gschem/src/x_compselect.c:1205
msgid "Include component as individual objects"
msgstr ""
-#: gschem/src/x_compselect.c:1354
+#: gschem/src/x_compselect.c:1362
msgid "Select Component..."
msgstr "é?¨å??é?¸æ??..."
-#: gschem/src/x_compselect.c:1377
+#: gschem/src/x_compselect.c:1385
msgid "In Use"
msgstr ""
-#: gschem/src/x_compselect.c:1381
+#: gschem/src/x_compselect.c:1389
msgid "Libraries"
msgstr "ã?©ã?¤ã??ã?©ã?ª"
-#: gschem/src/x_compselect.c:1390 gschem/src/x_fileselect.c:122
+#: gschem/src/x_compselect.c:1398 gschem/src/x_fileselect.c:122
msgid "Preview"
msgstr "ã??ã?¬ã??ã?¥ã?¼"
-#: gschem/src/x_compselect.c:1418
+#: gschem/src/x_compselect.c:1426
msgid "Attributes"
msgstr "ã?¢ã??ã?ªã??ã?¥ã?¼ã??"
@@ -1158,139 +1166,139 @@ msgstr "� �"
msgid "Edit Text Properties"
msgstr ""
-#: gschem/src/x_dialog.c:471
+#: gschem/src/x_dialog.c:472
msgid "<b>Text Content</b>"
msgstr ""
-#: gschem/src/x_dialog.c:507
+#: gschem/src/x_dialog.c:508
msgid "<b>Text Properties</b>"
msgstr ""
-#: gschem/src/x_dialog.c:522
+#: gschem/src/x_dialog.c:523
msgid "Color:"
msgstr ""
-#: gschem/src/x_dialog.c:529
+#: gschem/src/x_dialog.c:530
msgid "Size:"
msgstr ""
-#: gschem/src/x_dialog.c:538
+#: gschem/src/x_dialog.c:539
msgid "Alignment:"
msgstr ""
-#: gschem/src/x_dialog.c:587
+#: gschem/src/x_dialog.c:588
msgid "Solid"
msgstr "å®?ç·?"
-#: gschem/src/x_dialog.c:588
+#: gschem/src/x_dialog.c:589
msgid "Dotted"
msgstr "��"
-#: gschem/src/x_dialog.c:589
+#: gschem/src/x_dialog.c:590
msgid "Dashed"
msgstr "ç ´ç·?"
-#: gschem/src/x_dialog.c:590
+#: gschem/src/x_dialog.c:591
msgid "Center"
msgstr "ä¸å¤®"
-#: gschem/src/x_dialog.c:591
+#: gschem/src/x_dialog.c:592
msgid "Phantom"
msgstr "ã??ã?¡ã?³ã??ã? "
-#: gschem/src/x_dialog.c:592 gschem/src/x_dialog.c:689
-#: gschem/src/x_dialog.c:698 gschem/src/x_dialog.c:707
-#: gschem/src/x_dialog.c:808 gschem/src/x_dialog.c:810
-#: gschem/src/x_dialog.c:812 gschem/src/x_dialog.c:1038
-#: gschem/src/x_dialog.c:1141 gschem/src/x_dialog.c:1150
-#: gschem/src/x_dialog.c:1159 gschem/src/x_dialog.c:1168
-#: gschem/src/x_dialog.c:1177 gschem/src/x_dialog.c:1290
-#: gschem/src/x_dialog.c:1292 gschem/src/x_dialog.c:1294
-#: gschem/src/x_dialog.c:1296 gschem/src/x_dialog.c:1298
+#: gschem/src/x_dialog.c:593 gschem/src/x_dialog.c:690
+#: gschem/src/x_dialog.c:699 gschem/src/x_dialog.c:708
+#: gschem/src/x_dialog.c:809 gschem/src/x_dialog.c:811
+#: gschem/src/x_dialog.c:813 gschem/src/x_dialog.c:1039
+#: gschem/src/x_dialog.c:1142 gschem/src/x_dialog.c:1151
+#: gschem/src/x_dialog.c:1160 gschem/src/x_dialog.c:1169
+#: gschem/src/x_dialog.c:1178 gschem/src/x_dialog.c:1291
+#: gschem/src/x_dialog.c:1293 gschem/src/x_dialog.c:1295
+#: gschem/src/x_dialog.c:1297 gschem/src/x_dialog.c:1299
msgid "*unchanged*"
msgstr ""
-#: gschem/src/x_dialog.c:916
+#: gschem/src/x_dialog.c:917
msgid "Edit Line Width & Type"
msgstr "ç·?種ã?¨å¹?ç·¨é??"
-#: gschem/src/x_dialog.c:955 gschem/src/x_print.c:307
+#: gschem/src/x_dialog.c:956 gschem/src/x_print.c:307
msgid "Type:"
msgstr ""
-#: gschem/src/x_dialog.c:959
+#: gschem/src/x_dialog.c:960
msgid "Width:"
msgstr ""
-#: gschem/src/x_dialog.c:963
+#: gschem/src/x_dialog.c:964
msgid "Dash Length:"
msgstr ""
-#: gschem/src/x_dialog.c:967
+#: gschem/src/x_dialog.c:968
msgid "Dash Space:"
msgstr ""
-#: gschem/src/x_dialog.c:1034
+#: gschem/src/x_dialog.c:1035
msgid "Hollow"
msgstr "空�"
-#: gschem/src/x_dialog.c:1035
+#: gschem/src/x_dialog.c:1036
msgid "Filled"
msgstr "å¡?ã??ã?¤ã?¶ã??"
-#: gschem/src/x_dialog.c:1036
+#: gschem/src/x_dialog.c:1037
msgid "Mesh"
msgstr "ã?¡ã??ã?·ã?¥"
-#: gschem/src/x_dialog.c:1037
+#: gschem/src/x_dialog.c:1038
msgid "Hatch"
msgstr "ã??ã??ã??"
-#: gschem/src/x_dialog.c:1406
+#: gschem/src/x_dialog.c:1407
msgid "Edit Fill Type"
msgstr "å¡?ã??ã?¤ã?¶ã??ã??ç·¨é??"
-#: gschem/src/x_dialog.c:1444
+#: gschem/src/x_dialog.c:1446
msgid "Fill Type:"
msgstr ""
-#: gschem/src/x_dialog.c:1448
+#: gschem/src/x_dialog.c:1450
msgid "Line Width:"
msgstr ""
-#: gschem/src/x_dialog.c:1452
+#: gschem/src/x_dialog.c:1454
msgid "Angle 1:"
msgstr ""
-#: gschem/src/x_dialog.c:1456
+#: gschem/src/x_dialog.c:1458
msgid "Pitch 1:"
msgstr ""
-#: gschem/src/x_dialog.c:1460
+#: gschem/src/x_dialog.c:1462
msgid "Angle 2:"
msgstr ""
-#: gschem/src/x_dialog.c:1464
+#: gschem/src/x_dialog.c:1466
msgid "Pitch 2:"
msgstr ""
-#: gschem/src/x_dialog.c:1591
+#: gschem/src/x_dialog.c:1593
msgid "Arc Params"
msgstr "å??弧ã??ã?©ã?¡ã?¼ã?¿"
-#: gschem/src/x_dialog.c:1631
+#: gschem/src/x_dialog.c:1634
msgid "Arc Radius:"
msgstr ""
-#: gschem/src/x_dialog.c:1639
+#: gschem/src/x_dialog.c:1642
msgid "Start Angle:"
msgstr ""
-#: gschem/src/x_dialog.c:1647
+#: gschem/src/x_dialog.c:1650
msgid "Degrees of Sweep:"
msgstr ""
-#: gschem/src/x_dialog.c:1764
+#: gschem/src/x_dialog.c:1768
msgid ""
"Offset to translate?\n"
"(0 for origin)"
@@ -1298,198 +1306,198 @@ msgstr ""
"転é??ã??ã?¾ã??ã???\n"
"(0ã?§å??ç?¹)"
-#: gschem/src/x_dialog.c:1832
+#: gschem/src/x_dialog.c:1836
msgid "Text Size"
msgstr "ã??ã?ã?¹ã??ã?µã?¤ã?º"
-#: gschem/src/x_dialog.c:1862
+#: gschem/src/x_dialog.c:1866
msgid "Enter new text size:"
msgstr ""
-#: gschem/src/x_dialog.c:1938
+#: gschem/src/x_dialog.c:1942
msgid "Snap Size"
msgstr ""
-#: gschem/src/x_dialog.c:1968
+#: gschem/src/x_dialog.c:1972
msgid "Enter new snap grid spacing:"
msgstr ""
-#: gschem/src/x_dialog.c:2045
+#: gschem/src/x_dialog.c:2049
msgid "Edit slot number"
msgstr "ã?¹ã?ã??ã??ç?ªå?·ç·¨é??"
-#: gschem/src/x_dialog.c:2076
+#: gschem/src/x_dialog.c:2080
msgid "Edit slot number:"
msgstr ""
-#: gschem/src/x_dialog.c:2117
+#: gschem/src/x_dialog.c:2121
#, c-format
msgid "%s%s (%s)"
msgstr ""
-#: gschem/src/x_dialog.c:2140
+#: gschem/src/x_dialog.c:2144
msgid "About gschem"
msgstr ""
-#: gschem/src/x_dialog.c:2141
+#: gschem/src/x_dialog.c:2145
msgid "gEDA: GPL Electronic Design Automation"
msgstr ""
-#: gschem/src/x_dialog.c:2142
+#: gschem/src/x_dialog.c:2146
msgid ""
"Copyright © 1998-2009 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
"Copyright © 1998-2009 gEDA Contributors (see ChangeLog for details)"
msgstr ""
-#: gschem/src/x_dialog.c:2201
+#: gschem/src/x_dialog.c:2205
msgid "Coords"
msgstr "座�"
-#: gschem/src/x_dialog.c:2222
+#: gschem/src/x_dialog.c:2226
msgid "Screen"
msgstr "�����"
-#: gschem/src/x_dialog.c:2231
+#: gschem/src/x_dialog.c:2235
msgid "World"
msgstr "ã?¯ã?¼ã?«ã??"
-#: gschem/src/x_dialog.c:2270
+#: gschem/src/x_dialog.c:2274
msgid "Background"
msgstr ""
-#: gschem/src/x_dialog.c:2276
+#: gschem/src/x_dialog.c:2280
msgid "Net endpoint"
msgstr ""
-#: gschem/src/x_dialog.c:2279
+#: gschem/src/x_dialog.c:2283
msgid "Graphic"
msgstr ""
-#: gschem/src/x_dialog.c:2288
+#: gschem/src/x_dialog.c:2292
msgid "Logic bubble"
msgstr ""
-#: gschem/src/x_dialog.c:2291
+#: gschem/src/x_dialog.c:2295
msgid "Grid point"
msgstr ""
-#: gschem/src/x_dialog.c:2294
+#: gschem/src/x_dialog.c:2298
msgid "Detached attribute"
msgstr ""
-#: gschem/src/x_dialog.c:2297 gschem/src/x_window.c:383
+#: gschem/src/x_dialog.c:2301 gschem/src/x_window.c:383
msgid "Text"
msgstr "ã??ã?ã?¹ã??"
-#: gschem/src/x_dialog.c:2303
+#: gschem/src/x_dialog.c:2307
msgid "Selection"
msgstr ""
-#: gschem/src/x_dialog.c:2306
+#: gschem/src/x_dialog.c:2310
msgid "Bounding box"
msgstr ""
-#: gschem/src/x_dialog.c:2309
+#: gschem/src/x_dialog.c:2313
msgid "Zoom box"
msgstr ""
-#: gschem/src/x_dialog.c:2318
+#: gschem/src/x_dialog.c:2322
msgid "Output background"
msgstr ""
-#: gschem/src/x_dialog.c:2321
+#: gschem/src/x_dialog.c:2325
msgid "Net junction"
msgstr ""
-#: gschem/src/x_dialog.c:2324
+#: gschem/src/x_dialog.c:2328
msgid "Mesh grid major"
msgstr ""
-#: gschem/src/x_dialog.c:2327
+#: gschem/src/x_dialog.c:2331
msgid "Mesh grid minor"
msgstr ""
-#: gschem/src/x_dialog.c:2330
+#: gschem/src/x_dialog.c:2334
msgid "Unknown"
msgstr ""
-#: gschem/src/x_dialog.c:2481
+#: gschem/src/x_dialog.c:2485
#, c-format
msgid "ERROR: NULL object in color_edit_dialog_apply!\n"
msgstr ""
-#: gschem/src/x_dialog.c:2525
+#: gschem/src/x_dialog.c:2529
msgid "Color Edit"
msgstr "è?²ç·¨é??"
-#: gschem/src/x_dialog.c:2556
+#: gschem/src/x_dialog.c:2560
msgid "Object color:"
msgstr ""
-#: gschem/src/x_dialog.c:2614
+#: gschem/src/x_dialog.c:2618
msgid "Hotkeys"
msgstr ""
-#: gschem/src/x_dialog.c:2678
+#: gschem/src/x_dialog.c:2682
msgid "Function"
msgstr ""
-#: gschem/src/x_dialog.c:2685
+#: gschem/src/x_dialog.c:2689
msgid "Keystroke(s)"
msgstr ""
-#: gschem/src/x_dialog.c:2991
+#: gschem/src/x_dialog.c:2995
msgid "Find Text"
msgstr ""
-#: gschem/src/x_dialog.c:3022
+#: gschem/src/x_dialog.c:3026
msgid "Text to find:"
msgstr "æ¤?ç´¢ã??ã?ã?¹ã??"
-#: gschem/src/x_dialog.c:3032
+#: gschem/src/x_dialog.c:3036
msgid "descend into hierarchy"
msgstr "ä¸?ã?®é??層ã??æ¤?ç´¢"
-#: gschem/src/x_dialog.c:3097
+#: gschem/src/x_dialog.c:3101
msgid "Hide Text"
msgstr ""
-#: gschem/src/x_dialog.c:3128
+#: gschem/src/x_dialog.c:3132
msgid "Hide text starting with:"
msgstr "é? ã??ã??ã?ã?¹ã??"
-#: gschem/src/x_dialog.c:3197
+#: gschem/src/x_dialog.c:3201
msgid "Show Text"
msgstr ""
-#: gschem/src/x_dialog.c:3228
+#: gschem/src/x_dialog.c:3232
msgid "Show text starting with:"
msgstr "ã??ã?ã?¹ã??"
-#: gschem/src/x_dialog.c:3685
+#: gschem/src/x_dialog.c:3689
msgid "S_elect the schematics you want to save:"
msgstr ""
-#: gschem/src/x_dialog.c:3779
+#: gschem/src/x_dialog.c:3784
#, c-format
msgid "Save the changes to schematic \"%s\" before closing?"
msgstr ""
-#: gschem/src/x_dialog.c:3785
+#: gschem/src/x_dialog.c:3790
#, c-format
msgid ""
"There are %d schematics with unsaved changes. Save changes before closing?"
msgstr ""
-#: gschem/src/x_dialog.c:3814
+#: gschem/src/x_dialog.c:3819
msgid "If you don't save, all your changes will be permanently lost."
msgstr ""
-#: gschem/src/x_dialog.c:3834
+#: gschem/src/x_dialog.c:3839
msgid "_Close without saving"
msgstr ""
-#: gschem/src/x_dialog.c:4170
+#: gschem/src/x_dialog.c:4175
#, c-format
msgid ""
"<span weight=\"bold\" size=\"larger\">The input attribute \"%s\" is invalid\n"
@@ -1500,19 +1508,19 @@ msgid ""
"The value cannot start with a space."
msgstr ""
-#: gschem/src/x_dialog.c:4172
+#: gschem/src/x_dialog.c:4177
msgid "Invalid Attribute"
msgstr ""
-#: gschem/src/x_dialog.c:4208
+#: gschem/src/x_dialog.c:4213
msgid "Pin type"
msgstr ""
-#: gschem/src/x_dialog.c:4232
+#: gschem/src/x_dialog.c:4237
msgid "Net pin"
msgstr ""
-#: gschem/src/x_dialog.c:4234
+#: gschem/src/x_dialog.c:4239
msgid "Bus pin (graphical)"
msgstr ""
@@ -1605,11 +1613,11 @@ msgstr ""
msgid "Write image..."
msgstr ""
-#: gschem/src/x_log.c:188
+#: gschem/src/x_log.c:209
msgid "** Invalid UTF-8 in log message. See stderr or gschem.log.\n"
msgstr ""
-#: gschem/src/x_log.c:256
+#: gschem/src/x_log.c:288
msgid "Status"
msgstr "ã?¹ã??ã?¼ã?¿ã?¹"
@@ -1685,69 +1693,60 @@ msgstr ""
msgid "/Up"
msgstr ""
-#: gschem/src/x_menus.c:321
+#: gschem/src/x_menus.c:323
#, c-format
msgid "Tried to set the sensitivity on non-existent menu item '%s'\n"
msgstr ""
-#: gschem/src/x_menus.c:345
+#: gschem/src/x_menus.c:347
msgid "Popup_menu_item_factory doesn't exist!\n"
msgstr ""
-#: gschem/src/x_menus.c:358
+#: gschem/src/x_menus.c:360
msgid "Tried to set the sensitivity on a non-existent popup menu_item\n"
msgstr ""
-#: gschem/src/x_menus.c:438
-#, c-format
-msgid "Couldn't open file %s\n"
-msgstr ""
-
-#: gschem/src/x_menus.c:495
-msgid "Clear"
-msgstr "���"
-
-#: gschem/src/x_multiattrib.c:911
+#: gschem/src/x_multiattrib.c:915
msgid "Attributes with empty name are not allowed. Please set a name."
msgstr ""
-#: gschem/src/x_multiattrib.c:1456
+#: gschem/src/x_multiattrib.c:1468
msgid "Show Value only"
msgstr "���表示"
-#: gschem/src/x_multiattrib.c:1458
+#: gschem/src/x_multiattrib.c:1470
msgid "Show Name only"
msgstr "å??å??ã?®ã?¿è¡¨ç¤º"
-#: gschem/src/x_multiattrib.c:1486
+#: gschem/src/x_multiattrib.c:1498
msgid "Promote"
msgstr ""
-#: gschem/src/x_multiattrib.c:1490
+#: gschem/src/x_multiattrib.c:1502
msgid "Duplicate"
msgstr ""
-#: gschem/src/x_multiattrib.c:1708
+#: gschem/src/x_multiattrib.c:1719
msgid "Edit Attributes"
msgstr "ã?¢ã??ã?ªã??ã?¥ã?¼ã??ç·¨é??"
-#: gschem/src/x_multiattrib.c:1826
+#: gschem/src/x_multiattrib.c:1837
msgid "Vis?"
msgstr "表示"
-#: gschem/src/x_multiattrib.c:1844
+#: gschem/src/x_multiattrib.c:1855
msgid "N"
msgstr "å??å??"
-#: gschem/src/x_multiattrib.c:1862
+#: gschem/src/x_multiattrib.c:1873
msgid "V"
msgstr "å?¤"
-#: gschem/src/x_multiattrib.c:1884
+#: gschem/src/x_multiattrib.c:1895
msgid "Show inherited attributes"
msgstr ""
-#: gschem/src/x_multiattrib.c:1900
+#: gschem/src/x_multiattrib.c:1911
msgid "Add Attribute"
msgstr ""
@@ -1771,23 +1770,23 @@ msgstr "é??ã??ã??"
msgid "Discard Page"
msgstr "ç ´æ£?"
-#: gschem/src/x_pagesel.c:376
+#: gschem/src/x_pagesel.c:375
msgid "Page Manager"
msgstr "ã??ã?¼ã?¸ã??ã??ã?¼ã?¸ã?£"
-#: gschem/src/x_pagesel.c:432
+#: gschem/src/x_pagesel.c:431
msgid "Filename"
msgstr "ã??ã?¡ã?¤ã?«å??"
-#: gschem/src/x_pagesel.c:448
+#: gschem/src/x_pagesel.c:447
msgid "Changed"
msgstr ""
-#: gschem/src/x_pagesel.c:468
+#: gschem/src/x_pagesel.c:467
msgid "Right click on the filename for more options..."
msgstr ""
-#: gschem/src/x_preview.c:234
+#: gschem/src/x_preview.c:233
msgid "Preview Buffer"
msgstr ""
@@ -1843,23 +1842,23 @@ msgstr ""
msgid "Command:"
msgstr ""
-#: gschem/src/x_print.c:741
+#: gschem/src/x_print.c:745
msgid "No print destination specified\n"
msgstr ""
-#: gschem/src/x_print.c:748
+#: gschem/src/x_print.c:752
#, c-format
msgid "Cannot print current schematic to [%s]\n"
msgstr "ç?¾å?¨ã?®ã?¹ã?±ã??ã??ã??ã?¯ã??å?°å?·ã?§ã??ã?¾ã??ã??ã??[%s]\n"
-#: gschem/src/x_print.c:757
+#: gschem/src/x_print.c:761
#, c-format
msgid ""
"Error printing to file '%s'\n"
"Check the log window for more information"
msgstr ""
-#: gschem/src/x_print.c:764
+#: gschem/src/x_print.c:768
#, c-format
msgid "Printed current schematic to [%s]\n"
msgstr "ç?¾å?¨ã?®ã?¹ã?±ã??ã??ã??ã?¯ã??å?°å?·ã??ã?¾ã??ã??ã??[%s]\n"
@@ -1868,6 +1867,11 @@ msgstr "ç?¾å?¨ã?®ã?¹ã?±ã??ã??ã??ã?¯ã??å?°å?·ã??ã?¾ã??ã??ã??[%s]\n"
msgid "Execute Script..."
msgstr "ã?¹ã?¯ã?ªã??ã??å®?è¡?..."
+#: gschem/src/x_script.c:66
+#, c-format
+msgid "Executing guile script [%s]\n"
+msgstr "guileã?¹ã?¯ã?ªã??ã??ã??å®?è¡?ã??ã?¦ã??ã?¾ã??ã??[%s]\n"
+
#: gschem/src/x_window.c:81
#, c-format
msgid "Couldn't allocate gc\n"
@@ -1983,35 +1987,35 @@ msgstr ""
msgid "New file [%s]\n"
msgstr ""
-#: gschem/src/x_window.c:857
+#: gschem/src/x_window.c:855
#, c-format
msgid "Could NOT save page [%s]\n"
msgstr ""
-#: gschem/src/x_window.c:858
+#: gschem/src/x_window.c:856
msgid "Error while trying to save"
msgstr "ä¿?å?ä¸ã?«ã?¨ã?©ã?¼ç?ºç??"
-#: gschem/src/x_window.c:867
+#: gschem/src/x_window.c:865
#, c-format
msgid "Saved as [%s]\n"
msgstr ""
-#: gschem/src/x_window.c:869
+#: gschem/src/x_window.c:867
#, c-format
msgid "Saved [%s]\n"
msgstr "ä¿?å?ã??ã?¾ã??ã??ã??[%s]\n"
-#: gschem/src/x_window.c:871
+#: gschem/src/x_window.c:869
msgid "Saved"
msgstr "ä¿?å?ã??ã?¾ã??ã??ã??"
-#: gschem/src/x_window.c:945
+#: gschem/src/x_window.c:943
#, c-format
msgid "Discarding page [%s]\n"
msgstr "ã??ã?¼ã?¸ã??ç ´æ£?ã??ã?¦ã??ã?¾ã??ã??[%s]\n"
-#: gschem/src/x_window.c:945
+#: gschem/src/x_window.c:943
#, c-format
msgid "Closing [%s]\n"
msgstr "é??ã??ã?¦ã??ã?¾ã??ã??[%s]\n"
@@ -2052,7 +2056,7 @@ msgstr ""
msgid "Save All"
msgstr "ã??ã?¹ã?¦ä¿?å?"
-#: gschem/lib/system-gschemrc.scm:1386 gschem/lib/system-gschemrc.scm:1477
+#: gschem/lib/system-gschemrc.scm:1386 gschem/lib/system-gschemrc.scm:1478
msgid "_Revert"
msgstr ""
@@ -2064,7 +2068,7 @@ msgstr ""
msgid "Write _image..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1393 gschem/lib/system-gschemrc.scm:1478
+#: gschem/lib/system-gschemrc.scm:1393 gschem/lib/system-gschemrc.scm:1479
msgid "_Close"
msgstr ""
@@ -2096,390 +2100,408 @@ msgstr ""
msgid "_Delete"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1412
+#: gschem/lib/system-gschemrc.scm:1409
+#, fuzzy
+msgid "Select All"
+msgstr "é?¸æ??"
+
+#: gschem/lib/system-gschemrc.scm:1410
+#, fuzzy
+msgid "Deselect"
+msgstr "é?¸æ??"
+
+#: gschem/lib/system-gschemrc.scm:1414
msgid "Rotate 90 Mode"
msgstr "90度å??転ã?¢ã?¼ã??"
-#: gschem/lib/system-gschemrc.scm:1415
+#: gschem/lib/system-gschemrc.scm:1417
msgid "Edit..."
msgstr "ç·¨é??..."
-#: gschem/lib/system-gschemrc.scm:1416
+#: gschem/lib/system-gschemrc.scm:1418
msgid "Edit Text..."
msgstr "ã??ã?ã?¹ã??ç·¨é??..."
-#: gschem/lib/system-gschemrc.scm:1417
+#: gschem/lib/system-gschemrc.scm:1419
msgid "Slot..."
msgstr "ã?¹ã?ã??ã??..."
-#: gschem/lib/system-gschemrc.scm:1418
+#: gschem/lib/system-gschemrc.scm:1420
msgid "Color..."
msgstr "è?²..."
-#: gschem/lib/system-gschemrc.scm:1419
+#: gschem/lib/system-gschemrc.scm:1421
msgid "Line Width & Type..."
msgstr "�種��..."
-#: gschem/lib/system-gschemrc.scm:1420
+#: gschem/lib/system-gschemrc.scm:1422
msgid "Fill Type..."
msgstr "å¡?ã??ã?¤ã?¶ã??種é¡?..."
-#: gschem/lib/system-gschemrc.scm:1421
+#: gschem/lib/system-gschemrc.scm:1423
msgid "Symbol Translate..."
msgstr "ã?·ã?³ã??ã?«è»¢é??..."
-#: gschem/lib/system-gschemrc.scm:1425
+#: gschem/lib/system-gschemrc.scm:1427
msgid "Invoke Macro"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1426
+#: gschem/lib/system-gschemrc.scm:1428
msgid "Embed Component/Picture"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1427
+#: gschem/lib/system-gschemrc.scm:1429
msgid "Unembed Component/Picture"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1428
+#: gschem/lib/system-gschemrc.scm:1430
msgid "Update Component"
msgstr "é?¨å??æ?´æ?°"
-#: gschem/lib/system-gschemrc.scm:1429
+#: gschem/lib/system-gschemrc.scm:1431
msgid "Show/Hide Inv Text"
msgstr "ã??ã?ã?¹ã??表示/é??表示"
-#: gschem/lib/system-gschemrc.scm:1430
-msgid "Make Inv Text Vis"
-msgstr "é? ã??ã??ã?ã?¹ã??表示"
-
-#: gschem/lib/system-gschemrc.scm:1436
+#: gschem/lib/system-gschemrc.scm:1437
msgid "Copy into 1"
msgstr "ã?³ã??ã?¼1"
-#: gschem/lib/system-gschemrc.scm:1437
+#: gschem/lib/system-gschemrc.scm:1438
msgid "Copy into 2"
msgstr "ã?³ã??ã?¼2"
-#: gschem/lib/system-gschemrc.scm:1438
+#: gschem/lib/system-gschemrc.scm:1439
msgid "Copy into 3"
msgstr "ã?³ã??ã?¼3"
-#: gschem/lib/system-gschemrc.scm:1439
+#: gschem/lib/system-gschemrc.scm:1440
msgid "Copy into 4"
msgstr "ã?³ã??ã?¼4"
-#: gschem/lib/system-gschemrc.scm:1440
+#: gschem/lib/system-gschemrc.scm:1441
msgid "Copy into 5"
msgstr "ã?³ã??ã?¼5"
-#: gschem/lib/system-gschemrc.scm:1441
+#: gschem/lib/system-gschemrc.scm:1442
msgid "Cut into 1"
msgstr "ã?«ã??ã??1"
-#: gschem/lib/system-gschemrc.scm:1442
+#: gschem/lib/system-gschemrc.scm:1443
msgid "Cut into 2"
msgstr "ã?«ã??ã??2"
-#: gschem/lib/system-gschemrc.scm:1443
+#: gschem/lib/system-gschemrc.scm:1444
msgid "Cut into 3"
msgstr "ã?«ã??ã??3"
-#: gschem/lib/system-gschemrc.scm:1444
+#: gschem/lib/system-gschemrc.scm:1445
msgid "Cut into 4"
msgstr "ã?«ã??ã??4"
-#: gschem/lib/system-gschemrc.scm:1445
+#: gschem/lib/system-gschemrc.scm:1446
msgid "Cut into 5"
msgstr "ã?«ã??ã??5"
-#: gschem/lib/system-gschemrc.scm:1446
+#: gschem/lib/system-gschemrc.scm:1447
msgid "Paste from 1"
msgstr "ã??ã?¼ã?¹ã??1"
-#: gschem/lib/system-gschemrc.scm:1447
+#: gschem/lib/system-gschemrc.scm:1448
msgid "Paste from 2"
msgstr "ã??ã?¼ã?¹ã??2"
-#: gschem/lib/system-gschemrc.scm:1448
+#: gschem/lib/system-gschemrc.scm:1449
msgid "Paste from 3"
msgstr "ã??ã?¼ã?¹ã??3"
-#: gschem/lib/system-gschemrc.scm:1449
+#: gschem/lib/system-gschemrc.scm:1450
msgid "Paste from 4"
msgstr "ã??ã?¼ã?¹ã??4"
-#: gschem/lib/system-gschemrc.scm:1450
+#: gschem/lib/system-gschemrc.scm:1451
msgid "Paste from 5"
msgstr "ã??ã?¼ã?¹ã??5"
-#: gschem/lib/system-gschemrc.scm:1456
+#: gschem/lib/system-gschemrc.scm:1457
msgid "_Redraw"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1457
+#: gschem/lib/system-gschemrc.scm:1458
msgid "_Pan"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1458
+#: gschem/lib/system-gschemrc.scm:1459
msgid "Zoom _Box"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1459
+#: gschem/lib/system-gschemrc.scm:1460
msgid "Zoom _Extents"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1460
+#: gschem/lib/system-gschemrc.scm:1461
msgid "Zoom _In"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1461
+#: gschem/lib/system-gschemrc.scm:1462
msgid "Zoom _Out"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1462
+#: gschem/lib/system-gschemrc.scm:1463
msgid "Zoom _Full"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1464
+#: gschem/lib/system-gschemrc.scm:1465
msgid "_Dark color scheme"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1465
+#: gschem/lib/system-gschemrc.scm:1466
msgid "_Light color scheme"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1466
+#: gschem/lib/system-gschemrc.scm:1467
msgid "B_W color scheme"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1473
+#: gschem/lib/system-gschemrc.scm:1474
msgid "_Manager..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1474
+#: gschem/lib/system-gschemrc.scm:1475
msgid "_Previous"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1475
+#: gschem/lib/system-gschemrc.scm:1476
msgid "_Next"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1476
+#: gschem/lib/system-gschemrc.scm:1477
msgid "Ne_w"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1480
+#: gschem/lib/system-gschemrc.scm:1481
msgid "_Discard"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1486
+#: gschem/lib/system-gschemrc.scm:1487
msgid "_Component..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1487
+#: gschem/lib/system-gschemrc.scm:1488
msgid "_Net"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1488
+#: gschem/lib/system-gschemrc.scm:1489
msgid "B_us"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1489
+#: gschem/lib/system-gschemrc.scm:1490
msgid "_Attribute..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1490
+#: gschem/lib/system-gschemrc.scm:1491
msgid "_Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1492
+#: gschem/lib/system-gschemrc.scm:1493
msgid "_Line"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1493
+#: gschem/lib/system-gschemrc.scm:1494
msgid "_Box"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1494
+#: gschem/lib/system-gschemrc.scm:1495
msgid "C_ircle"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1495
+#: gschem/lib/system-gschemrc.scm:1496
msgid "A_rc"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1496
+#: gschem/lib/system-gschemrc.scm:1497
msgid "_Pin"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1497
+#: gschem/lib/system-gschemrc.scm:1498
msgid "Pictu_re..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1503
+#: gschem/lib/system-gschemrc.scm:1504
msgid "_Down Schematic"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1504
+#: gschem/lib/system-gschemrc.scm:1505
msgid "Down _Symbol"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1505
+#: gschem/lib/system-gschemrc.scm:1506
msgid "_Up"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1506
+#: gschem/lib/system-gschemrc.scm:1507
msgid "D_ocumentation..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1512
+#: gschem/lib/system-gschemrc.scm:1513
msgid "_Attach"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1513
+#: gschem/lib/system-gschemrc.scm:1514
msgid "_Detach"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1514
+#: gschem/lib/system-gschemrc.scm:1515
msgid "Show _Value"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1515
+#: gschem/lib/system-gschemrc.scm:1516
msgid "Show _Name"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1516
+#: gschem/lib/system-gschemrc.scm:1517
msgid "Show _Both"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1517
+#: gschem/lib/system-gschemrc.scm:1518
msgid "_Toggle Visibility"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1519
+#: gschem/lib/system-gschemrc.scm:1520
msgid "_Find Specific Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1520
+#: gschem/lib/system-gschemrc.scm:1521
msgid "_Hide Specific Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1521
+#: gschem/lib/system-gschemrc.scm:1522
msgid "_Show Specific Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1522
+#: gschem/lib/system-gschemrc.scm:1523
msgid "A_utonumber Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1528
+#: gschem/lib/system-gschemrc.scm:1529
msgid "_Text Size..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1529
+#: gschem/lib/system-gschemrc.scm:1530
msgid "Cycle _grid styles"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1530
+#: gschem/lib/system-gschemrc.scm:1531
msgid "Toggle _Snap On/Off"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1531
+#: gschem/lib/system-gschemrc.scm:1532
msgid "Snap Grid S_pacing..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1532
+#: gschem/lib/system-gschemrc.scm:1533
msgid "Scale _up Grid Spacing"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1534
+#: gschem/lib/system-gschemrc.scm:1535
msgid "Scale _down Grid Spacing"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1536
+#: gschem/lib/system-gschemrc.scm:1537
msgid "Toggle _Outline/Box"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1538
+#: gschem/lib/system-gschemrc.scm:1539
msgid "Toggle Net _Rubberband"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1539
+#: gschem/lib/system-gschemrc.scm:1540
msgid "Toggle _Magnetic Net"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1540
+#: gschem/lib/system-gschemrc.scm:1541
msgid "Show _Log Window..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1542
+#: gschem/lib/system-gschemrc.scm:1543
msgid "Show _Coord Window..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1558
+#: gschem/lib/system-gschemrc.scm:1559
msgid "gEDA Docu_mentation..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1559
+#: gschem/lib/system-gschemrc.scm:1560
msgid "gschem _FAQ..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1560
+#: gschem/lib/system-gschemrc.scm:1561
msgid "gEDA _Wiki..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1561
+#: gschem/lib/system-gschemrc.scm:1562
msgid "Component D_ocumentation..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1563
+#: gschem/lib/system-gschemrc.scm:1564
msgid "_Hotkeys..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1564
+#: gschem/lib/system-gschemrc.scm:1565
msgid "_About..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1570
+#: gschem/lib/system-gschemrc.scm:1571
msgid "_File"
msgstr "ã??ã?¡ã?¤ã?«"
-#: gschem/lib/system-gschemrc.scm:1571
+#: gschem/lib/system-gschemrc.scm:1572
msgid "_Edit"
msgstr "ç·¨é??"
-#: gschem/lib/system-gschemrc.scm:1572
+#: gschem/lib/system-gschemrc.scm:1573
msgid "_Buffer"
msgstr "ã??ã??ã??ã?¡"
-#: gschem/lib/system-gschemrc.scm:1573
+#: gschem/lib/system-gschemrc.scm:1574
msgid "_View"
msgstr "表示"
-#: gschem/lib/system-gschemrc.scm:1574
+#: gschem/lib/system-gschemrc.scm:1575
msgid "_Page"
msgstr "ã??ã?¼ã?¸"
-#: gschem/lib/system-gschemrc.scm:1575
+#: gschem/lib/system-gschemrc.scm:1576
msgid "_Add"
msgstr "追å? "
-#: gschem/lib/system-gschemrc.scm:1576
+#: gschem/lib/system-gschemrc.scm:1577
msgid "Hie_rarchy"
msgstr "é??層"
-#: gschem/lib/system-gschemrc.scm:1577
+#: gschem/lib/system-gschemrc.scm:1578
msgid "A_ttributes"
msgstr "ã?¢ã??ã?ªã??ã?¥ã?¼ã??"
-#: gschem/lib/system-gschemrc.scm:1578
+#: gschem/lib/system-gschemrc.scm:1579
msgid "_Options"
msgstr "ã?ªã??ã?·ã?§ã?³"
-#: gschem/lib/system-gschemrc.scm:1579
+#: gschem/lib/system-gschemrc.scm:1580
msgid "_Help"
msgstr "ã??ã?«ã??"
+#~ msgid "Scheme directory NOT set!\n"
+#~ msgstr "schemeã??ã?£ã?¬ã?¯ã??ã?ªã??è¨å®?ã??ã??ã?¦ã??ã?¾ã??ã??!\n"
+
+#~ msgid "MakeVisible"
+#~ msgstr "表示ã??ã??"
+
+#~ msgid "Clear"
+#~ msgstr "���"
+
+#~ msgid "Make Inv Text Vis"
+#~ msgstr "é? ã??ã??ã?ã?¹ã??表示"
+
#~ msgid "Update Cues"
#~ msgstr "ã?ã?¥ã?¼æ?´æ?°"
diff --git a/gschem/po/ml.po b/gschem/po/ml.po
index b9b39bc..bece1f2 100644
--- a/gschem/po/ml.po
+++ b/gschem/po/ml.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2010-11-07 13:37+0000\n"
+"POT-Creation-Date: 2011-01-16 00:11-0500\n"
"PO-Revision-Date: 2010-02-11 03:33+0000\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -22,17 +22,17 @@ msgstr ""
msgid "Zoom too small! Cannot zoom further.\n"
msgstr ""
-#: gschem/src/g_funcs.c:339 gschem/src/i_callbacks.c:68
+#: gschem/src/g_funcs.c:347 gschem/src/i_callbacks.c:68
#, c-format
msgid "Could not fork\n"
msgstr ""
-#: gschem/src/g_funcs.c:355 gschem/src/i_callbacks.c:78
+#: gschem/src/g_funcs.c:363 gschem/src/i_callbacks.c:78
#, c-format
msgid "Could not invoke %s\n"
msgstr ""
-#: gschem/src/g_funcs.c:361 gschem/src/i_callbacks.c:82
+#: gschem/src/g_funcs.c:369 gschem/src/i_callbacks.c:82
msgid "Documentation commands not supported under MinGW.\n"
msgstr ""
@@ -121,39 +121,39 @@ msgstr ""
msgid "Invalid number of steps [%d] scrollpan-steps\n"
msgstr ""
-#: gschem/src/gschem.c:184
+#: gschem/src/gschem.c:188
#, c-format
msgid "gEDA/gschem version %s%s.%s\n"
msgstr ""
-#: gschem/src/gschem.c:187
+#: gschem/src/gschem.c:191
msgid ""
"gEDA/gschem comes with ABSOLUTELY NO WARRANTY; see COPYING for more "
"details.\n"
msgstr ""
-#: gschem/src/gschem.c:189
+#: gschem/src/gschem.c:193
msgid ""
"This is free software, and you are welcome to redistribute it under certain\n"
msgstr ""
-#: gschem/src/gschem.c:191
+#: gschem/src/gschem.c:195
msgid ""
"conditions; please see the COPYING file for more details.\n"
"\n"
msgstr ""
-#: gschem/src/gschem.c:194
+#: gschem/src/gschem.c:198
#, c-format
msgid "This is the MINGW32 port.\n"
msgstr ""
-#: gschem/src/gschem.c:198
+#: gschem/src/gschem.c:202
#, c-format
msgid "Current locale settings: %s\n"
msgstr ""
-#: gschem/src/gschem.c:213
+#: gschem/src/gschem.c:218
msgid ""
"You must set the GEDADATA environment variable!\n"
"\n"
@@ -161,31 +161,21 @@ msgid ""
"environment variable to point to the correct location.\n"
msgstr ""
-#: gschem/src/gschem.c:248
+#: gschem/src/gschem.c:256
#, c-format
msgid "Couldn't find init scm file [%s]\n"
msgstr ""
-#: gschem/src/gschem.c:252
+#: gschem/src/gschem.c:260
#, c-format
msgid "Read init scm file [%s]\n"
msgstr ""
-#: gschem/src/gschem.c:256
+#: gschem/src/gschem.c:264
#, c-format
msgid "Failed to read init scm file [%s]\n"
msgstr ""
-#: gschem/src/gschem.c:317
-#, c-format
-msgid "Scheme directory NOT set!\n"
-msgstr ""
-
-#: gschem/src/gschem.c:324 gschem/src/x_script.c:66
-#, c-format
-msgid "Executing guile script [%s]\n"
-msgstr ""
-
#: gschem/src/gschem_cairo.c:310
#, c-format
msgid "Unknown end for line (%d)\n"
@@ -209,11 +199,11 @@ msgstr ""
msgid "Text Mode"
msgstr ""
-#: gschem/src/i_basic.c:84 gschem/lib/system-gschemrc.scm:1409
+#: gschem/src/i_basic.c:84 gschem/lib/system-gschemrc.scm:1411
msgid "Copy Mode"
msgstr ""
-#: gschem/src/i_basic.c:87 gschem/lib/system-gschemrc.scm:1411
+#: gschem/src/i_basic.c:87 gschem/lib/system-gschemrc.scm:1413
msgid "Move Mode"
msgstr ""
@@ -221,7 +211,7 @@ msgstr ""
msgid "Rotate Mode"
msgstr ""
-#: gschem/src/i_basic.c:91 gschem/lib/system-gschemrc.scm:1413
+#: gschem/src/i_basic.c:91 gschem/lib/system-gschemrc.scm:1415
msgid "Mirror Mode"
msgstr ""
@@ -274,22 +264,22 @@ msgstr ""
msgid "Pin Mode"
msgstr ""
-#: gschem/src/i_basic.c:135 gschem/src/i_callbacks.c:544
-#: gschem/src/i_callbacks.c:568
+#: gschem/src/i_basic.c:135 gschem/src/i_callbacks.c:576
+#: gschem/src/i_callbacks.c:600
msgid "Copy"
msgstr ""
-#: gschem/src/i_basic.c:137 gschem/src/i_callbacks.c:634
-#: gschem/src/i_callbacks.c:658
+#: gschem/src/i_basic.c:137 gschem/src/i_callbacks.c:666
+#: gschem/src/i_callbacks.c:690
msgid "Move"
msgstr ""
-#: gschem/src/i_basic.c:139 gschem/src/i_callbacks.c:589
-#: gschem/src/i_callbacks.c:613
+#: gschem/src/i_basic.c:139 gschem/src/i_callbacks.c:621
+#: gschem/src/i_callbacks.c:645
msgid "Multiple Copy"
msgstr ""
-#: gschem/src/i_basic.c:142 gschem/lib/system-gschemrc.scm:1410
+#: gschem/src/i_basic.c:142 gschem/lib/system-gschemrc.scm:1412
msgid "Multiple Copy Mode"
msgstr ""
@@ -309,7 +299,7 @@ msgstr ""
msgid "Action"
msgstr ""
-#: gschem/src/i_basic.c:260 gschem/src/x_dialog.c:2312
+#: gschem/src/i_basic.c:260 gschem/src/x_dialog.c:2316
#: gschem/src/x_window.c:491
msgid "Stroke"
msgstr ""
@@ -340,7 +330,7 @@ msgstr ""
msgid "Documentation for [%s,%s,%s,%s]\n"
msgstr ""
-#: gschem/src/i_callbacks.c:123 gschem/src/i_callbacks.c:1699
+#: gschem/src/i_callbacks.c:123 gschem/src/i_callbacks.c:1706
#, c-format
msgid "New page created [%s]\n"
msgstr ""
@@ -362,327 +352,323 @@ msgstr ""
msgid "Closing Window\n"
msgstr ""
-#: gschem/src/i_callbacks.c:549 gschem/src/i_callbacks.c:594
-#: gschem/src/i_callbacks.c:639
+#: gschem/src/i_callbacks.c:581 gschem/src/i_callbacks.c:626
+#: gschem/src/i_callbacks.c:671
msgid "Select objs first"
msgstr ""
-#: gschem/src/i_callbacks.c:678 gschem/src/x_multiattrib.c:1491
+#: gschem/src/i_callbacks.c:710 gschem/src/x_multiattrib.c:1503
msgid "Delete"
msgstr "മായ������"
-#: gschem/src/i_callbacks.c:703
+#: gschem/src/i_callbacks.c:735
msgid "Edit"
msgstr "തിര�ത�തിയ�ഴ�ത�� (Edit)"
-#: gschem/src/i_callbacks.c:718
+#: gschem/src/i_callbacks.c:750
msgid "Edit pin type"
msgstr ""
-#: gschem/src/i_callbacks.c:737
+#: gschem/src/i_callbacks.c:769
msgid "Edit Text"
msgstr ""
-#: gschem/src/i_callbacks.c:760
+#: gschem/src/i_callbacks.c:792
msgid "Slot"
msgstr ""
-#: gschem/src/i_callbacks.c:777
+#: gschem/src/i_callbacks.c:809
msgid "Color"
msgstr ""
-#: gschem/src/i_callbacks.c:814 gschem/src/i_callbacks.c:859
+#: gschem/src/i_callbacks.c:846 gschem/src/i_callbacks.c:891
msgid "Rotate"
msgstr ""
-#: gschem/src/i_callbacks.c:882 gschem/src/i_callbacks.c:907
+#: gschem/src/i_callbacks.c:913 gschem/src/i_callbacks.c:938
msgid "Mirror"
msgstr ""
-#: gschem/src/i_callbacks.c:928 gschem/src/x_dialog.c:2315
-#: gschem/lib/system-gschemrc.scm:1422
+#: gschem/src/i_callbacks.c:959 gschem/src/x_dialog.c:2319
+#: gschem/lib/system-gschemrc.scm:1424
msgid "Lock"
msgstr "പ������"
-#: gschem/src/i_callbacks.c:946 gschem/lib/system-gschemrc.scm:1423
+#: gschem/src/i_callbacks.c:977 gschem/lib/system-gschemrc.scm:1425
msgid "Unlock"
msgstr "പ����� ത�റ�����"
-#: gschem/src/i_callbacks.c:964 gschem/src/x_dialog.c:1734
+#: gschem/src/i_callbacks.c:995 gschem/src/x_dialog.c:1737
msgid "Translate"
msgstr ""
-#: gschem/src/i_callbacks.c:967
+#: gschem/src/i_callbacks.c:998
msgid "WARNING: Do not translate with snap off!\n"
msgstr ""
-#: gschem/src/i_callbacks.c:968
+#: gschem/src/i_callbacks.c:999
msgid "WARNING: Turning snap on and continuing with translate.\n"
msgstr ""
-#: gschem/src/i_callbacks.c:975
+#: gschem/src/i_callbacks.c:1006
msgid "WARNING: Snap grid size is not equal to 100!\n"
msgstr ""
-#: gschem/src/i_callbacks.c:977
+#: gschem/src/i_callbacks.c:1008
msgid ""
"WARNING: If you are translating a symbol to the origin, the snap grid size "
"should be set to 100\n"
msgstr ""
-#: gschem/src/i_callbacks.c:1008
+#: gschem/src/i_callbacks.c:1039
msgid "Embed"
msgstr ""
-#: gschem/src/i_callbacks.c:1047
+#: gschem/src/i_callbacks.c:1078
msgid "Unembed"
msgstr ""
-#: gschem/src/i_callbacks.c:1089
+#: gschem/src/i_callbacks.c:1120
msgid "Update"
msgstr ""
-#: gschem/src/i_callbacks.c:1136
+#: gschem/src/i_callbacks.c:1167
msgid "ShowHidden"
msgstr ""
-#: gschem/src/i_callbacks.c:1160
-msgid "MakeVisible"
-msgstr ""
-
-#: gschem/src/i_callbacks.c:1466 gschem/src/i_callbacks.c:1538
+#: gschem/src/i_callbacks.c:1473 gschem/src/i_callbacks.c:1545
msgid "Pan"
msgstr ""
-#: gschem/src/i_callbacks.c:1743
+#: gschem/src/i_callbacks.c:1750
msgid "Really revert page?"
msgstr ""
-#: gschem/src/i_callbacks.c:1813
+#: gschem/src/i_callbacks.c:1820
msgid "Copy to clipboard"
msgstr ""
-#: gschem/src/i_callbacks.c:1831
+#: gschem/src/i_callbacks.c:1838
msgid "Cut to clipboard"
msgstr ""
-#: gschem/src/i_callbacks.c:1849
+#: gschem/src/i_callbacks.c:1856
msgid "Paste from clipboard"
msgstr ""
-#: gschem/src/i_callbacks.c:1861 gschem/src/i_callbacks.c:2100
-#: gschem/src/i_callbacks.c:2122 gschem/src/i_callbacks.c:2144
-#: gschem/src/i_callbacks.c:2166 gschem/src/i_callbacks.c:2188
+#: gschem/src/i_callbacks.c:1868 gschem/src/i_callbacks.c:2107
+#: gschem/src/i_callbacks.c:2129 gschem/src/i_callbacks.c:2151
+#: gschem/src/i_callbacks.c:2173 gschem/src/i_callbacks.c:2195
msgid "Empty buffer"
msgstr ""
-#: gschem/src/i_callbacks.c:1906
+#: gschem/src/i_callbacks.c:1913
msgid "Copy 1"
msgstr ""
-#: gschem/src/i_callbacks.c:1925
+#: gschem/src/i_callbacks.c:1932
msgid "Copy 2"
msgstr ""
-#: gschem/src/i_callbacks.c:1944
+#: gschem/src/i_callbacks.c:1951
msgid "Copy 3"
msgstr ""
-#: gschem/src/i_callbacks.c:1963
+#: gschem/src/i_callbacks.c:1970
msgid "Copy 4"
msgstr ""
-#: gschem/src/i_callbacks.c:1982
+#: gschem/src/i_callbacks.c:1989
msgid "Copy 5"
msgstr ""
-#: gschem/src/i_callbacks.c:2001
+#: gschem/src/i_callbacks.c:2008
msgid "Cut 1"
msgstr ""
-#: gschem/src/i_callbacks.c:2020
+#: gschem/src/i_callbacks.c:2027
msgid "Cut 2"
msgstr ""
-#: gschem/src/i_callbacks.c:2039
+#: gschem/src/i_callbacks.c:2046
msgid "Cut 3"
msgstr ""
-#: gschem/src/i_callbacks.c:2058
+#: gschem/src/i_callbacks.c:2065
msgid "Cut 4"
msgstr ""
-#: gschem/src/i_callbacks.c:2077
+#: gschem/src/i_callbacks.c:2084
msgid "Cut 5"
msgstr ""
-#: gschem/src/i_callbacks.c:2093
+#: gschem/src/i_callbacks.c:2100
msgid "Paste 1"
msgstr ""
-#: gschem/src/i_callbacks.c:2115
+#: gschem/src/i_callbacks.c:2122
msgid "Paste 2"
msgstr ""
-#: gschem/src/i_callbacks.c:2137
+#: gschem/src/i_callbacks.c:2144
msgid "Paste 3"
msgstr ""
-#: gschem/src/i_callbacks.c:2159
+#: gschem/src/i_callbacks.c:2166
msgid "Paste 4"
msgstr ""
-#: gschem/src/i_callbacks.c:2181
+#: gschem/src/i_callbacks.c:2188
msgid "Paste 5"
msgstr ""
-#: gschem/src/i_callbacks.c:2318 gschem/src/x_window.c:355
+#: gschem/src/i_callbacks.c:2325 gschem/src/x_window.c:355
msgid "Component"
msgstr ""
-#: gschem/src/i_callbacks.c:2354 gschem/src/i_callbacks.c:2373
-#: gschem/src/x_dialog.c:2285
+#: gschem/src/i_callbacks.c:2361 gschem/src/i_callbacks.c:2380
+#: gschem/src/x_dialog.c:2289
msgid "Attribute"
msgstr ""
-#: gschem/src/i_callbacks.c:2395 gschem/src/i_callbacks.c:2422
-#: gschem/src/x_dialog.c:2282
+#: gschem/src/i_callbacks.c:2402 gschem/src/i_callbacks.c:2429
+#: gschem/src/x_dialog.c:2286
msgid "Net"
msgstr "ന�റ�റ�"
-#: gschem/src/i_callbacks.c:2466 gschem/src/i_callbacks.c:2493
-#: gschem/src/x_dialog.c:2300 gschem/src/x_window.c:375
+#: gschem/src/i_callbacks.c:2473 gschem/src/i_callbacks.c:2500
+#: gschem/src/x_dialog.c:2304 gschem/src/x_window.c:375
msgid "Bus"
msgstr "ബസ�"
-#: gschem/src/i_callbacks.c:2574 gschem/src/i_callbacks.c:2597
+#: gschem/src/i_callbacks.c:2581 gschem/src/i_callbacks.c:2604
msgid "Line"
msgstr "ര��"
-#: gschem/src/i_callbacks.c:2619 gschem/src/i_callbacks.c:2642
+#: gschem/src/i_callbacks.c:2626 gschem/src/i_callbacks.c:2649
msgid "Box"
msgstr "ബ���സ�"
-#: gschem/src/i_callbacks.c:2698 gschem/src/i_callbacks.c:2722
+#: gschem/src/i_callbacks.c:2705 gschem/src/i_callbacks.c:2729
msgid "Circle"
msgstr "വ�ത�ത�"
-#: gschem/src/i_callbacks.c:2744 gschem/src/i_callbacks.c:2767
+#: gschem/src/i_callbacks.c:2751 gschem/src/i_callbacks.c:2774
msgid "Arc"
msgstr "�ര�ദ�ധവ�ത�ത�"
-#: gschem/src/i_callbacks.c:2789 gschem/src/i_callbacks.c:2812
-#: gschem/src/x_dialog.c:2273
+#: gschem/src/i_callbacks.c:2796 gschem/src/i_callbacks.c:2819
+#: gschem/src/x_dialog.c:2277
msgid "Pin"
msgstr "പിനàµ?â??"
-#: gschem/src/i_callbacks.c:2871
+#: gschem/src/i_callbacks.c:2878
#, c-format
msgid "Searching for source [%s]\n"
msgstr ""
-#: gschem/src/i_callbacks.c:2895
+#: gschem/src/i_callbacks.c:2902
#, c-format
msgid "Cannot find source [%s]\n"
msgstr ""
-#: gschem/src/i_callbacks.c:2964
+#: gschem/src/i_callbacks.c:2965
#, c-format
msgid "Searching for symbol [%s]\n"
msgstr ""
-#: gschem/src/i_callbacks.c:2970
+#: gschem/src/i_callbacks.c:2971
msgid "Symbol is not a real file. Symbol cannot be loaded.\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3001
+#: gschem/src/i_callbacks.c:3002
msgid "Cannot find any schematics above the current one!\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3055
+#: gschem/src/i_callbacks.c:3056
msgid ""
"This command retrieves the component documentation from the web, but there "
"is no component selected"
msgstr ""
-#: gschem/src/i_callbacks.c:3083
+#: gschem/src/i_callbacks.c:3084
msgid "Attach"
msgstr ""
-#: gschem/src/i_callbacks.c:3130
+#: gschem/src/i_callbacks.c:3131
msgid "Detach"
msgstr ""
-#: gschem/src/i_callbacks.c:3165
+#: gschem/src/i_callbacks.c:3166
msgid "ShowN"
msgstr ""
-#: gschem/src/i_callbacks.c:3201
+#: gschem/src/i_callbacks.c:3202
msgid "ShowV"
msgstr ""
-#: gschem/src/i_callbacks.c:3237
+#: gschem/src/i_callbacks.c:3238
msgid "ShowB"
msgstr ""
-#: gschem/src/i_callbacks.c:3274
+#: gschem/src/i_callbacks.c:3275
msgid "VisToggle"
msgstr ""
-#: gschem/src/i_callbacks.c:3304
+#: gschem/src/i_callbacks.c:3305
#, c-format
msgid "Sorry but this is a non-functioning menu option\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3394
+#: gschem/src/i_callbacks.c:3395
msgid "Action feedback mode set to OUTLINE\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3397
+#: gschem/src/i_callbacks.c:3398
msgid "Action feedback mode set to BOUNDINGBOX\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3422
+#: gschem/src/i_callbacks.c:3423
msgid "Grid OFF\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3423
+#: gschem/src/i_callbacks.c:3424
msgid "Dot grid selected\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3424
+#: gschem/src/i_callbacks.c:3425
msgid "Mesh grid selected\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3445
+#: gschem/src/i_callbacks.c:3446
msgid "Snap OFF (CAUTION!)\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3448
+#: gschem/src/i_callbacks.c:3449
msgid "Snap ON\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3451
+#: gschem/src/i_callbacks.c:3452
msgid "Snap back to the grid (CAUTION!)\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3477
+#: gschem/src/i_callbacks.c:3478
msgid "Rubber band OFF \n"
msgstr ""
-#: gschem/src/i_callbacks.c:3480
+#: gschem/src/i_callbacks.c:3481
msgid "Rubber band ON\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3495
+#: gschem/src/i_callbacks.c:3496
msgid "magnetic net mode: ON\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3498
+#: gschem/src/i_callbacks.c:3499
msgid "magnetic net mode: OFF\n"
msgstr ""
-#: gschem/src/o_box.c:153
+#: gschem/src/o_box.c:149
#, c-format
msgid "Unknown type for box (fill)!\n"
msgstr ""
@@ -702,17 +688,17 @@ msgstr ""
msgid "Got an invalid buffer_number [o_buffer_paste_start]\n"
msgstr ""
-#: gschem/src/o_bus.c:118
+#: gschem/src/o_bus.c:117
#, c-format
msgid "Got an invalid which one in o_bus_draw_stretch\n"
msgstr ""
-#: gschem/src/o_circle.c:134
+#: gschem/src/o_circle.c:130
#, c-format
msgid "Unknown type for circle (fill)!\n"
msgstr ""
-#: gschem/src/o_complex.c:243 gschem/src/o_complex.c:247
+#: gschem/src/o_complex.c:237 gschem/src/o_complex.c:241
#, c-format
msgid "Translating schematic [%d %d]\n"
msgstr ""
@@ -730,35 +716,35 @@ msgstr ""
msgid "Object already unlocked\n"
msgstr ""
-#: gschem/src/o_misc.c:413
+#: gschem/src/o_misc.c:409
msgid "Hidden text is now visible\n"
msgstr ""
-#: gschem/src/o_misc.c:415
+#: gschem/src/o_misc.c:411
msgid "Hidden text is now invisible\n"
msgstr ""
-#: gschem/src/o_misc.c:668
+#: gschem/src/o_misc.c:636
#, c-format
msgid "Could not find symbol [%s] in library. Update failed.\n"
msgstr ""
-#: gschem/src/o_misc.c:783
+#: gschem/src/o_misc.c:751
#, c-format
msgid "o_autosave_backups: Can't get the real filename of %s."
msgstr ""
-#: gschem/src/o_misc.c:827
+#: gschem/src/o_misc.c:795
#, c-format
msgid "Could NOT set previous backup file [%s] read-write\n"
msgstr ""
-#: gschem/src/o_misc.c:845
+#: gschem/src/o_misc.c:815
#, c-format
msgid "Could NOT set backup file [%s] readonly\n"
msgstr ""
-#: gschem/src/o_misc.c:850
+#: gschem/src/o_misc.c:820
#, c-format
msgid "Could NOT save backup file [%s]\n"
msgstr ""
@@ -778,36 +764,36 @@ msgstr ""
msgid "Got a non line object in o_move_check_endpoint\n"
msgstr ""
-#: gschem/src/o_net.c:159
+#: gschem/src/o_net.c:158
#, c-format
msgid "Got an invalid which one in o_net_draw_stretch\n"
msgstr ""
-#: gschem/src/o_net.c:538
+#: gschem/src/o_net.c:537
msgid "Warning: Starting net at off grid coordinate\n"
msgstr ""
-#: gschem/src/o_net.c:600
+#: gschem/src/o_net.c:599
msgid "Warning: Ending net at off grid coordinate\n"
msgstr ""
-#: gschem/src/o_net.c:932 gschem/src/o_net.c:969 gschem/src/o_net.c:1040
-#: gschem/src/o_net.c:1076
+#: gschem/src/o_net.c:931 gschem/src/o_net.c:968 gschem/src/o_net.c:1039
+#: gschem/src/o_net.c:1075
#, c-format
msgid "Tried to add more than two bus rippers. Internal gschem error.\n"
msgstr ""
-#: gschem/src/o_net.c:1144
+#: gschem/src/o_net.c:1143
#, c-format
msgid "Bus ripper symbol [%s] was not found in any component library\n"
msgstr ""
-#: gschem/src/o_path.c:352
+#: gschem/src/o_path.c:348
#, c-format
msgid "Unknown type for path (fill)!\n"
msgstr ""
-#: gschem/src/o_picture.c:163 gschem/src/o_picture.c:539
+#: gschem/src/o_picture.c:163 gschem/src/o_picture.c:537
#, c-format
msgid "Failed to load picture: %s"
msgstr ""
@@ -816,7 +802,7 @@ msgstr ""
msgid "Picture"
msgstr ""
-#: gschem/src/o_picture.c:447 gschem/src/x_attribedit.c:141
+#: gschem/src/o_picture.c:445 gschem/src/x_attribedit.c:141
#, c-format
msgid "ERROR: NULL object!\n"
msgstr ""
@@ -837,23 +823,45 @@ msgstr ""
msgid "New slot number out of range\n"
msgstr ""
-#: gschem/src/o_undo.c:304
+#: gschem/src/o_undo.c:303
msgid "Undo/Redo disabled in rc file\n"
msgstr ""
-#: gschem/src/parsecmd.c:47
+#: gschem/src/parsecmd.c:81
#, c-format
msgid ""
-"Usage: %s [OPTIONS] schematic_filename1 ... schematic_filenameN\n"
-" -q Quiet mode\n"
-" -v Verbose mode on\n"
-" -r filename Rc filename\n"
-" -s filename Script (guile) filename\n"
-" -o filename Output filename (for printing)\n"
-" -p Automatically place the window\n"
-" -t Print stroke information\n"
-" -h Help; this message\n"
+"Usage: %s [OPTION ...] [--] [FILE ...]\n"
+"\n"
+"Interactively edit gEDA schematics or symbols. If one or more FILEs\n"
+"are specified, open them for editing; otherwise, create a new, empty\n"
+"schematic.\n"
+"\n"
+"Options:\n"
+" -q, --quiet Quiet mode.\n"
+" -v, --verbose Verbose mode.\n"
+" -r, --config-file=FILE Additional configuration file to load.\n"
+" -L DIR Add DIR to Scheme search path.\n"
+" -c EXPR Scheme expression to run at startup.\n"
+" -s FILE Scheme script to run at startup.\n"
+" -o, --output=FILE Output filename (for printing).\n"
+" -p Automatically place the window.\n"
+" -V, --version Show version information.\n"
+" -h, --help Help; this message.\n"
+" -- Treat all remaining arguments as filenames.\n"
"\n"
+"Report bugs to <geda-bug@xxxxxxxx>\n"
+"gEDA/gaf homepage: <http://gpleda.org>\n"
+msgstr ""
+
+#: gschem/src/parsecmd.c:115
+#, c-format
+msgid ""
+"gEDA %s (g%.7s)\n"
+"Copyright (C) 1998-2011 gEDA developers\n"
+"This is free software, and you are welcome to redistribute it under\n"
+"certain conditions. For details, see the file `COPYING', which is\n"
+"included in the gEDA distribution.\n"
+"There is NO WARRANTY, to the extent permitted by law.\n"
msgstr ""
#: gschem/src/x_attribedit.c:127
@@ -865,56 +873,56 @@ msgstr ""
msgid "Single Attribute Editor"
msgstr ""
-#: gschem/src/x_attribedit.c:358
+#: gschem/src/x_attribedit.c:359
msgid "<b>Edit Attribute</b>"
msgstr ""
-#: gschem/src/x_attribedit.c:360
+#: gschem/src/x_attribedit.c:361
msgid "<b>Add Attribute</b>"
msgstr ""
-#: gschem/src/x_attribedit.c:376 gschem/src/x_multiattrib.c:1916
+#: gschem/src/x_attribedit.c:377 gschem/src/x_multiattrib.c:1927
msgid "Name:"
msgstr ""
-#: gschem/src/x_attribedit.c:393 gschem/src/x_multiattrib.c:1935
+#: gschem/src/x_attribedit.c:394 gschem/src/x_multiattrib.c:1946
msgid "Value:"
msgstr ""
-#: gschem/src/x_attribedit.c:409 gschem/src/x_multiattrib.c:1978
+#: gschem/src/x_attribedit.c:410 gschem/src/x_multiattrib.c:1989
msgid "Visible"
msgstr ""
-#: gschem/src/x_attribedit.c:429
+#: gschem/src/x_attribedit.c:430
msgid "Show Value Only"
msgstr ""
-#: gschem/src/x_attribedit.c:431
+#: gschem/src/x_attribedit.c:432
msgid "Show Name Only"
msgstr ""
-#: gschem/src/x_attribedit.c:433 gschem/src/x_multiattrib.c:1454
+#: gschem/src/x_attribedit.c:434 gschem/src/x_multiattrib.c:1466
msgid "Show Name & Value"
msgstr ""
-#: gschem/src/x_attribedit.c:440
+#: gschem/src/x_attribedit.c:441
msgid "<b>Attach Options</b>"
msgstr ""
-#: gschem/src/x_attribedit.c:455
+#: gschem/src/x_attribedit.c:456
msgid "All"
msgstr ""
-#: gschem/src/x_attribedit.c:463 gschem/src/x_compselect.c:896
-#: gschem/src/x_compselect.c:1010
+#: gschem/src/x_attribedit.c:464 gschem/src/x_compselect.c:904
+#: gschem/src/x_compselect.c:1018
msgid "Components"
msgstr ""
-#: gschem/src/x_attribedit.c:471 gschem/src/x_window.c:365
+#: gschem/src/x_attribedit.c:472 gschem/src/x_window.c:365
msgid "Nets"
msgstr ""
-#: gschem/src/x_attribedit.c:479
+#: gschem/src/x_attribedit.c:480
msgid "Replace existing attributes"
msgstr ""
@@ -930,91 +938,91 @@ msgid ""
"duplicate slot may cause problems: [symbolname=%s, number=%d, slot=%d]\n"
msgstr ""
-#: gschem/src/x_autonumber.c:673
+#: gschem/src/x_autonumber.c:675
msgid "No searchstring given in autonumber text.\n"
msgstr ""
-#: gschem/src/x_autonumber.c:725
+#: gschem/src/x_autonumber.c:727
msgid "No '*' or '?' given at the end of the autonumber text.\n"
msgstr ""
-#: gschem/src/x_autonumber.c:860
+#: gschem/src/x_autonumber.c:862
msgid "Diagonal"
msgstr ""
-#: gschem/src/x_autonumber.c:861
+#: gschem/src/x_autonumber.c:863
msgid "Top to bottom"
msgstr ""
-#: gschem/src/x_autonumber.c:861
+#: gschem/src/x_autonumber.c:863
msgid "Bottom to top"
msgstr ""
-#: gschem/src/x_autonumber.c:862
+#: gschem/src/x_autonumber.c:864
msgid "Left to right"
msgstr ""
-#: gschem/src/x_autonumber.c:862
+#: gschem/src/x_autonumber.c:864
msgid "Right to left"
msgstr ""
-#: gschem/src/x_autonumber.c:863
+#: gschem/src/x_autonumber.c:865
msgid "File order"
msgstr ""
-#: gschem/src/x_autonumber.c:1199
+#: gschem/src/x_autonumber.c:1201
msgid "Autonumber text"
msgstr ""
-#: gschem/src/x_autonumber.c:1223
+#: gschem/src/x_autonumber.c:1225
msgid "<b>Scope</b>"
msgstr ""
-#: gschem/src/x_autonumber.c:1245
+#: gschem/src/x_autonumber.c:1247
msgid "Search for:"
msgstr ""
-#: gschem/src/x_autonumber.c:1259
+#: gschem/src/x_autonumber.c:1261
msgid "Autonumber text in:"
msgstr ""
-#: gschem/src/x_autonumber.c:1266
+#: gschem/src/x_autonumber.c:1268
msgid "Skip numbers found in:"
msgstr ""
-#: gschem/src/x_autonumber.c:1278 gschem/src/x_autonumber.c:1287
+#: gschem/src/x_autonumber.c:1280 gschem/src/x_autonumber.c:1289
msgid "Selected objects"
msgstr ""
-#: gschem/src/x_autonumber.c:1279 gschem/src/x_autonumber.c:1288
+#: gschem/src/x_autonumber.c:1281 gschem/src/x_autonumber.c:1290
msgid "Current page"
msgstr ""
-#: gschem/src/x_autonumber.c:1280 gschem/src/x_autonumber.c:1289
+#: gschem/src/x_autonumber.c:1282 gschem/src/x_autonumber.c:1291
msgid "Whole hierarchy"
msgstr ""
-#: gschem/src/x_autonumber.c:1291
+#: gschem/src/x_autonumber.c:1293
msgid "Overwrite existing numbers"
msgstr ""
-#: gschem/src/x_autonumber.c:1296
+#: gschem/src/x_autonumber.c:1298
msgid "<b>Options</b>"
msgstr ""
-#: gschem/src/x_autonumber.c:1318
+#: gschem/src/x_autonumber.c:1320
msgid "Starting number:"
msgstr ""
-#: gschem/src/x_autonumber.c:1325
+#: gschem/src/x_autonumber.c:1327
msgid "Sort order:"
msgstr ""
-#: gschem/src/x_autonumber.c:1346
+#: gschem/src/x_autonumber.c:1348
msgid "Remove numbers"
msgstr ""
-#: gschem/src/x_autonumber.c:1350
+#: gschem/src/x_autonumber.c:1352
msgid "Automatic slotting"
msgstr ""
@@ -1051,48 +1059,48 @@ msgstr ""
msgid "Tried to get an invalid outline color: %d\n"
msgstr ""
-#: gschem/src/x_compselect.c:1040
+#: gschem/src/x_compselect.c:1048
msgid "Filter:"
msgstr ""
-#: gschem/src/x_compselect.c:1143 gschem/src/x_dialog.c:3663
-#: gschem/src/x_multiattrib.c:1782
+#: gschem/src/x_compselect.c:1151 gschem/src/x_dialog.c:3667
+#: gschem/src/x_multiattrib.c:1793
msgid "Name"
msgstr ""
-#: gschem/src/x_compselect.c:1152 gschem/src/x_multiattrib.c:1806
+#: gschem/src/x_compselect.c:1160 gschem/src/x_multiattrib.c:1817
msgid "Value"
msgstr ""
-#: gschem/src/x_compselect.c:1191
+#: gschem/src/x_compselect.c:1199
msgid "Default behavior - reference component"
msgstr ""
-#: gschem/src/x_compselect.c:1194
+#: gschem/src/x_compselect.c:1202
msgid "Embed component in schematic"
msgstr ""
-#: gschem/src/x_compselect.c:1197
+#: gschem/src/x_compselect.c:1205
msgid "Include component as individual objects"
msgstr ""
-#: gschem/src/x_compselect.c:1354
+#: gschem/src/x_compselect.c:1362
msgid "Select Component..."
msgstr ""
-#: gschem/src/x_compselect.c:1377
+#: gschem/src/x_compselect.c:1385
msgid "In Use"
msgstr ""
-#: gschem/src/x_compselect.c:1381
+#: gschem/src/x_compselect.c:1389
msgid "Libraries"
msgstr ""
-#: gschem/src/x_compselect.c:1390 gschem/src/x_fileselect.c:122
+#: gschem/src/x_compselect.c:1398 gschem/src/x_fileselect.c:122
msgid "Preview"
msgstr ""
-#: gschem/src/x_compselect.c:1418
+#: gschem/src/x_compselect.c:1426
msgid "Attributes"
msgstr ""
@@ -1147,336 +1155,336 @@ msgstr ""
msgid "Edit Text Properties"
msgstr ""
-#: gschem/src/x_dialog.c:471
+#: gschem/src/x_dialog.c:472
msgid "<b>Text Content</b>"
msgstr ""
-#: gschem/src/x_dialog.c:507
+#: gschem/src/x_dialog.c:508
msgid "<b>Text Properties</b>"
msgstr ""
-#: gschem/src/x_dialog.c:522
+#: gschem/src/x_dialog.c:523
msgid "Color:"
msgstr ""
-#: gschem/src/x_dialog.c:529
+#: gschem/src/x_dialog.c:530
msgid "Size:"
msgstr ""
-#: gschem/src/x_dialog.c:538
+#: gschem/src/x_dialog.c:539
msgid "Alignment:"
msgstr ""
-#: gschem/src/x_dialog.c:587
+#: gschem/src/x_dialog.c:588
msgid "Solid"
msgstr ""
-#: gschem/src/x_dialog.c:588
+#: gschem/src/x_dialog.c:589
msgid "Dotted"
msgstr ""
-#: gschem/src/x_dialog.c:589
+#: gschem/src/x_dialog.c:590
msgid "Dashed"
msgstr ""
-#: gschem/src/x_dialog.c:590
+#: gschem/src/x_dialog.c:591
msgid "Center"
msgstr ""
-#: gschem/src/x_dialog.c:591
+#: gschem/src/x_dialog.c:592
msgid "Phantom"
msgstr ""
-#: gschem/src/x_dialog.c:592 gschem/src/x_dialog.c:689
-#: gschem/src/x_dialog.c:698 gschem/src/x_dialog.c:707
-#: gschem/src/x_dialog.c:808 gschem/src/x_dialog.c:810
-#: gschem/src/x_dialog.c:812 gschem/src/x_dialog.c:1038
-#: gschem/src/x_dialog.c:1141 gschem/src/x_dialog.c:1150
-#: gschem/src/x_dialog.c:1159 gschem/src/x_dialog.c:1168
-#: gschem/src/x_dialog.c:1177 gschem/src/x_dialog.c:1290
-#: gschem/src/x_dialog.c:1292 gschem/src/x_dialog.c:1294
-#: gschem/src/x_dialog.c:1296 gschem/src/x_dialog.c:1298
+#: gschem/src/x_dialog.c:593 gschem/src/x_dialog.c:690
+#: gschem/src/x_dialog.c:699 gschem/src/x_dialog.c:708
+#: gschem/src/x_dialog.c:809 gschem/src/x_dialog.c:811
+#: gschem/src/x_dialog.c:813 gschem/src/x_dialog.c:1039
+#: gschem/src/x_dialog.c:1142 gschem/src/x_dialog.c:1151
+#: gschem/src/x_dialog.c:1160 gschem/src/x_dialog.c:1169
+#: gschem/src/x_dialog.c:1178 gschem/src/x_dialog.c:1291
+#: gschem/src/x_dialog.c:1293 gschem/src/x_dialog.c:1295
+#: gschem/src/x_dialog.c:1297 gschem/src/x_dialog.c:1299
msgid "*unchanged*"
msgstr ""
-#: gschem/src/x_dialog.c:916
+#: gschem/src/x_dialog.c:917
msgid "Edit Line Width & Type"
msgstr ""
-#: gschem/src/x_dialog.c:955 gschem/src/x_print.c:307
+#: gschem/src/x_dialog.c:956 gschem/src/x_print.c:307
msgid "Type:"
msgstr ""
-#: gschem/src/x_dialog.c:959
+#: gschem/src/x_dialog.c:960
msgid "Width:"
msgstr ""
-#: gschem/src/x_dialog.c:963
+#: gschem/src/x_dialog.c:964
msgid "Dash Length:"
msgstr ""
-#: gschem/src/x_dialog.c:967
+#: gschem/src/x_dialog.c:968
msgid "Dash Space:"
msgstr ""
-#: gschem/src/x_dialog.c:1034
+#: gschem/src/x_dialog.c:1035
msgid "Hollow"
msgstr ""
-#: gschem/src/x_dialog.c:1035
+#: gschem/src/x_dialog.c:1036
msgid "Filled"
msgstr ""
-#: gschem/src/x_dialog.c:1036
+#: gschem/src/x_dialog.c:1037
msgid "Mesh"
msgstr ""
-#: gschem/src/x_dialog.c:1037
+#: gschem/src/x_dialog.c:1038
msgid "Hatch"
msgstr ""
-#: gschem/src/x_dialog.c:1406
+#: gschem/src/x_dialog.c:1407
msgid "Edit Fill Type"
msgstr ""
-#: gschem/src/x_dialog.c:1444
+#: gschem/src/x_dialog.c:1446
msgid "Fill Type:"
msgstr ""
-#: gschem/src/x_dialog.c:1448
+#: gschem/src/x_dialog.c:1450
msgid "Line Width:"
msgstr ""
-#: gschem/src/x_dialog.c:1452
+#: gschem/src/x_dialog.c:1454
msgid "Angle 1:"
msgstr ""
-#: gschem/src/x_dialog.c:1456
+#: gschem/src/x_dialog.c:1458
msgid "Pitch 1:"
msgstr ""
-#: gschem/src/x_dialog.c:1460
+#: gschem/src/x_dialog.c:1462
msgid "Angle 2:"
msgstr ""
-#: gschem/src/x_dialog.c:1464
+#: gschem/src/x_dialog.c:1466
msgid "Pitch 2:"
msgstr ""
-#: gschem/src/x_dialog.c:1591
+#: gschem/src/x_dialog.c:1593
msgid "Arc Params"
msgstr ""
-#: gschem/src/x_dialog.c:1631
+#: gschem/src/x_dialog.c:1634
msgid "Arc Radius:"
msgstr ""
-#: gschem/src/x_dialog.c:1639
+#: gschem/src/x_dialog.c:1642
msgid "Start Angle:"
msgstr ""
-#: gschem/src/x_dialog.c:1647
+#: gschem/src/x_dialog.c:1650
msgid "Degrees of Sweep:"
msgstr ""
-#: gschem/src/x_dialog.c:1764
+#: gschem/src/x_dialog.c:1768
msgid ""
"Offset to translate?\n"
"(0 for origin)"
msgstr ""
-#: gschem/src/x_dialog.c:1832
+#: gschem/src/x_dialog.c:1836
msgid "Text Size"
msgstr ""
-#: gschem/src/x_dialog.c:1862
+#: gschem/src/x_dialog.c:1866
msgid "Enter new text size:"
msgstr ""
-#: gschem/src/x_dialog.c:1938
+#: gschem/src/x_dialog.c:1942
msgid "Snap Size"
msgstr ""
-#: gschem/src/x_dialog.c:1968
+#: gschem/src/x_dialog.c:1972
msgid "Enter new snap grid spacing:"
msgstr ""
-#: gschem/src/x_dialog.c:2045
+#: gschem/src/x_dialog.c:2049
msgid "Edit slot number"
msgstr ""
-#: gschem/src/x_dialog.c:2076
+#: gschem/src/x_dialog.c:2080
msgid "Edit slot number:"
msgstr ""
-#: gschem/src/x_dialog.c:2117
+#: gschem/src/x_dialog.c:2121
#, c-format
msgid "%s%s (%s)"
msgstr ""
-#: gschem/src/x_dialog.c:2140
+#: gschem/src/x_dialog.c:2144
msgid "About gschem"
msgstr ""
-#: gschem/src/x_dialog.c:2141
+#: gschem/src/x_dialog.c:2145
msgid "gEDA: GPL Electronic Design Automation"
msgstr ""
-#: gschem/src/x_dialog.c:2142
+#: gschem/src/x_dialog.c:2146
msgid ""
"Copyright © 1998-2009 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
"Copyright © 1998-2009 gEDA Contributors (see ChangeLog for details)"
msgstr ""
-#: gschem/src/x_dialog.c:2201
+#: gschem/src/x_dialog.c:2205
msgid "Coords"
msgstr ""
-#: gschem/src/x_dialog.c:2222
+#: gschem/src/x_dialog.c:2226
msgid "Screen"
msgstr ""
-#: gschem/src/x_dialog.c:2231
+#: gschem/src/x_dialog.c:2235
msgid "World"
msgstr ""
-#: gschem/src/x_dialog.c:2270
+#: gschem/src/x_dialog.c:2274
msgid "Background"
msgstr ""
-#: gschem/src/x_dialog.c:2276
+#: gschem/src/x_dialog.c:2280
msgid "Net endpoint"
msgstr ""
-#: gschem/src/x_dialog.c:2279
+#: gschem/src/x_dialog.c:2283
msgid "Graphic"
msgstr ""
-#: gschem/src/x_dialog.c:2288
+#: gschem/src/x_dialog.c:2292
msgid "Logic bubble"
msgstr ""
-#: gschem/src/x_dialog.c:2291
+#: gschem/src/x_dialog.c:2295
msgid "Grid point"
msgstr ""
-#: gschem/src/x_dialog.c:2294
+#: gschem/src/x_dialog.c:2298
msgid "Detached attribute"
msgstr ""
-#: gschem/src/x_dialog.c:2297 gschem/src/x_window.c:383
+#: gschem/src/x_dialog.c:2301 gschem/src/x_window.c:383
msgid "Text"
msgstr ""
-#: gschem/src/x_dialog.c:2303
+#: gschem/src/x_dialog.c:2307
msgid "Selection"
msgstr ""
-#: gschem/src/x_dialog.c:2306
+#: gschem/src/x_dialog.c:2310
msgid "Bounding box"
msgstr ""
-#: gschem/src/x_dialog.c:2309
+#: gschem/src/x_dialog.c:2313
msgid "Zoom box"
msgstr ""
-#: gschem/src/x_dialog.c:2318
+#: gschem/src/x_dialog.c:2322
msgid "Output background"
msgstr ""
-#: gschem/src/x_dialog.c:2321
+#: gschem/src/x_dialog.c:2325
msgid "Net junction"
msgstr ""
-#: gschem/src/x_dialog.c:2324
+#: gschem/src/x_dialog.c:2328
msgid "Mesh grid major"
msgstr ""
-#: gschem/src/x_dialog.c:2327
+#: gschem/src/x_dialog.c:2331
msgid "Mesh grid minor"
msgstr ""
-#: gschem/src/x_dialog.c:2330
+#: gschem/src/x_dialog.c:2334
msgid "Unknown"
msgstr ""
-#: gschem/src/x_dialog.c:2481
+#: gschem/src/x_dialog.c:2485
#, c-format
msgid "ERROR: NULL object in color_edit_dialog_apply!\n"
msgstr ""
-#: gschem/src/x_dialog.c:2525
+#: gschem/src/x_dialog.c:2529
msgid "Color Edit"
msgstr ""
-#: gschem/src/x_dialog.c:2556
+#: gschem/src/x_dialog.c:2560
msgid "Object color:"
msgstr ""
-#: gschem/src/x_dialog.c:2614
+#: gschem/src/x_dialog.c:2618
msgid "Hotkeys"
msgstr ""
-#: gschem/src/x_dialog.c:2678
+#: gschem/src/x_dialog.c:2682
msgid "Function"
msgstr ""
-#: gschem/src/x_dialog.c:2685
+#: gschem/src/x_dialog.c:2689
msgid "Keystroke(s)"
msgstr ""
-#: gschem/src/x_dialog.c:2991
+#: gschem/src/x_dialog.c:2995
msgid "Find Text"
msgstr ""
-#: gschem/src/x_dialog.c:3022
+#: gschem/src/x_dialog.c:3026
msgid "Text to find:"
msgstr ""
-#: gschem/src/x_dialog.c:3032
+#: gschem/src/x_dialog.c:3036
msgid "descend into hierarchy"
msgstr ""
-#: gschem/src/x_dialog.c:3097
+#: gschem/src/x_dialog.c:3101
msgid "Hide Text"
msgstr ""
-#: gschem/src/x_dialog.c:3128
+#: gschem/src/x_dialog.c:3132
msgid "Hide text starting with:"
msgstr ""
-#: gschem/src/x_dialog.c:3197
+#: gschem/src/x_dialog.c:3201
msgid "Show Text"
msgstr ""
-#: gschem/src/x_dialog.c:3228
+#: gschem/src/x_dialog.c:3232
msgid "Show text starting with:"
msgstr ""
-#: gschem/src/x_dialog.c:3685
+#: gschem/src/x_dialog.c:3689
msgid "S_elect the schematics you want to save:"
msgstr ""
-#: gschem/src/x_dialog.c:3779
+#: gschem/src/x_dialog.c:3784
#, c-format
msgid "Save the changes to schematic \"%s\" before closing?"
msgstr ""
-#: gschem/src/x_dialog.c:3785
+#: gschem/src/x_dialog.c:3790
#, c-format
msgid ""
"There are %d schematics with unsaved changes. Save changes before closing?"
msgstr ""
-#: gschem/src/x_dialog.c:3814
+#: gschem/src/x_dialog.c:3819
msgid "If you don't save, all your changes will be permanently lost."
msgstr ""
-#: gschem/src/x_dialog.c:3834
+#: gschem/src/x_dialog.c:3839
msgid "_Close without saving"
msgstr ""
-#: gschem/src/x_dialog.c:4170
+#: gschem/src/x_dialog.c:4175
#, c-format
msgid ""
"<span weight=\"bold\" size=\"larger\">The input attribute \"%s\" is invalid\n"
@@ -1487,19 +1495,19 @@ msgid ""
"The value cannot start with a space."
msgstr ""
-#: gschem/src/x_dialog.c:4172
+#: gschem/src/x_dialog.c:4177
msgid "Invalid Attribute"
msgstr ""
-#: gschem/src/x_dialog.c:4208
+#: gschem/src/x_dialog.c:4213
msgid "Pin type"
msgstr ""
-#: gschem/src/x_dialog.c:4232
+#: gschem/src/x_dialog.c:4237
msgid "Net pin"
msgstr ""
-#: gschem/src/x_dialog.c:4234
+#: gschem/src/x_dialog.c:4239
msgid "Bus pin (graphical)"
msgstr ""
@@ -1592,11 +1600,11 @@ msgstr ""
msgid "Write image..."
msgstr ""
-#: gschem/src/x_log.c:188
+#: gschem/src/x_log.c:209
msgid "** Invalid UTF-8 in log message. See stderr or gschem.log.\n"
msgstr ""
-#: gschem/src/x_log.c:256
+#: gschem/src/x_log.c:288
msgid "Status"
msgstr ""
@@ -1672,69 +1680,60 @@ msgstr ""
msgid "/Up"
msgstr ""
-#: gschem/src/x_menus.c:321
+#: gschem/src/x_menus.c:323
#, c-format
msgid "Tried to set the sensitivity on non-existent menu item '%s'\n"
msgstr ""
-#: gschem/src/x_menus.c:345
+#: gschem/src/x_menus.c:347
msgid "Popup_menu_item_factory doesn't exist!\n"
msgstr ""
-#: gschem/src/x_menus.c:358
+#: gschem/src/x_menus.c:360
msgid "Tried to set the sensitivity on a non-existent popup menu_item\n"
msgstr ""
-#: gschem/src/x_menus.c:438
-#, c-format
-msgid "Couldn't open file %s\n"
-msgstr ""
-
-#: gschem/src/x_menus.c:495
-msgid "Clear"
-msgstr ""
-
-#: gschem/src/x_multiattrib.c:911
+#: gschem/src/x_multiattrib.c:915
msgid "Attributes with empty name are not allowed. Please set a name."
msgstr ""
-#: gschem/src/x_multiattrib.c:1456
+#: gschem/src/x_multiattrib.c:1468
msgid "Show Value only"
msgstr ""
-#: gschem/src/x_multiattrib.c:1458
+#: gschem/src/x_multiattrib.c:1470
msgid "Show Name only"
msgstr ""
-#: gschem/src/x_multiattrib.c:1486
+#: gschem/src/x_multiattrib.c:1498
msgid "Promote"
msgstr ""
-#: gschem/src/x_multiattrib.c:1490
+#: gschem/src/x_multiattrib.c:1502
msgid "Duplicate"
msgstr ""
-#: gschem/src/x_multiattrib.c:1708
+#: gschem/src/x_multiattrib.c:1719
msgid "Edit Attributes"
msgstr ""
-#: gschem/src/x_multiattrib.c:1826
+#: gschem/src/x_multiattrib.c:1837
msgid "Vis?"
msgstr ""
-#: gschem/src/x_multiattrib.c:1844
+#: gschem/src/x_multiattrib.c:1855
msgid "N"
msgstr ""
-#: gschem/src/x_multiattrib.c:1862
+#: gschem/src/x_multiattrib.c:1873
msgid "V"
msgstr ""
-#: gschem/src/x_multiattrib.c:1884
+#: gschem/src/x_multiattrib.c:1895
msgid "Show inherited attributes"
msgstr ""
-#: gschem/src/x_multiattrib.c:1900
+#: gschem/src/x_multiattrib.c:1911
msgid "Add Attribute"
msgstr ""
@@ -1758,23 +1757,23 @@ msgstr "പ��� ��യ������"
msgid "Discard Page"
msgstr ""
-#: gschem/src/x_pagesel.c:376
+#: gschem/src/x_pagesel.c:375
msgid "Page Manager"
msgstr ""
-#: gschem/src/x_pagesel.c:432
+#: gschem/src/x_pagesel.c:431
msgid "Filename"
msgstr ""
-#: gschem/src/x_pagesel.c:448
+#: gschem/src/x_pagesel.c:447
msgid "Changed"
msgstr ""
-#: gschem/src/x_pagesel.c:468
+#: gschem/src/x_pagesel.c:467
msgid "Right click on the filename for more options..."
msgstr ""
-#: gschem/src/x_preview.c:234
+#: gschem/src/x_preview.c:233
msgid "Preview Buffer"
msgstr ""
@@ -1830,23 +1829,23 @@ msgstr ""
msgid "Command:"
msgstr ""
-#: gschem/src/x_print.c:741
+#: gschem/src/x_print.c:745
msgid "No print destination specified\n"
msgstr ""
-#: gschem/src/x_print.c:748
+#: gschem/src/x_print.c:752
#, c-format
msgid "Cannot print current schematic to [%s]\n"
msgstr ""
-#: gschem/src/x_print.c:757
+#: gschem/src/x_print.c:761
#, c-format
msgid ""
"Error printing to file '%s'\n"
"Check the log window for more information"
msgstr ""
-#: gschem/src/x_print.c:764
+#: gschem/src/x_print.c:768
#, c-format
msgid "Printed current schematic to [%s]\n"
msgstr ""
@@ -1855,6 +1854,11 @@ msgstr ""
msgid "Execute Script..."
msgstr "à´¸àµ?à´?àµ?à´°à´¿à´ªàµ?à´±àµ?à´±àµ? à´ªàµ?രവരàµ?â??à´¤àµ?തിപàµ?പിà´?àµ?à´?àµ?à´?"
+#: gschem/src/x_script.c:66
+#, c-format
+msgid "Executing guile script [%s]\n"
+msgstr ""
+
#: gschem/src/x_window.c:81
#, c-format
msgid "Couldn't allocate gc\n"
@@ -1962,35 +1966,35 @@ msgstr ""
msgid "New file [%s]\n"
msgstr ""
-#: gschem/src/x_window.c:857
+#: gschem/src/x_window.c:855
#, c-format
msgid "Could NOT save page [%s]\n"
msgstr ""
-#: gschem/src/x_window.c:858
+#: gschem/src/x_window.c:856
msgid "Error while trying to save"
msgstr ""
-#: gschem/src/x_window.c:867
+#: gschem/src/x_window.c:865
#, c-format
msgid "Saved as [%s]\n"
msgstr ""
-#: gschem/src/x_window.c:869
+#: gschem/src/x_window.c:867
#, c-format
msgid "Saved [%s]\n"
msgstr ""
-#: gschem/src/x_window.c:871
+#: gschem/src/x_window.c:869
msgid "Saved"
msgstr ""
-#: gschem/src/x_window.c:945
+#: gschem/src/x_window.c:943
#, c-format
msgid "Discarding page [%s]\n"
msgstr ""
-#: gschem/src/x_window.c:945
+#: gschem/src/x_window.c:943
#, c-format
msgid "Closing [%s]\n"
msgstr ""
@@ -2031,7 +2035,7 @@ msgstr ""
msgid "Save All"
msgstr "�ല�ലാ� സ�വ� ��യ��"
-#: gschem/lib/system-gschemrc.scm:1386 gschem/lib/system-gschemrc.scm:1477
+#: gschem/lib/system-gschemrc.scm:1386 gschem/lib/system-gschemrc.scm:1478
msgid "_Revert"
msgstr ""
@@ -2043,7 +2047,7 @@ msgstr ""
msgid "Write _image..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1393 gschem/lib/system-gschemrc.scm:1478
+#: gschem/lib/system-gschemrc.scm:1393 gschem/lib/system-gschemrc.scm:1479
msgid "_Close"
msgstr ""
@@ -2075,387 +2079,392 @@ msgstr ""
msgid "_Delete"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1412
+#: gschem/lib/system-gschemrc.scm:1409
+#, fuzzy
+msgid "Select All"
+msgstr "à´ªàµ?രവരàµ?â??à´¤àµ?തന à´°àµ?തി നിരàµ?â??ണയിà´?àµ?à´?àµ?à´?"
+
+#: gschem/lib/system-gschemrc.scm:1410
+msgid "Deselect"
+msgstr ""
+
+#: gschem/lib/system-gschemrc.scm:1414
msgid "Rotate 90 Mode"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1415
+#: gschem/lib/system-gschemrc.scm:1417
msgid "Edit..."
msgstr "മാറ�റ� വര�ത�ത��..."
-#: gschem/lib/system-gschemrc.scm:1416
+#: gschem/lib/system-gschemrc.scm:1418
msgid "Edit Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1417
+#: gschem/lib/system-gschemrc.scm:1419
msgid "Slot..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1418
+#: gschem/lib/system-gschemrc.scm:1420
msgid "Color..."
msgstr "à´?ളരàµ?â??"
-#: gschem/lib/system-gschemrc.scm:1419
+#: gschem/lib/system-gschemrc.scm:1421
msgid "Line Width & Type..."
msgstr "à´²àµ?à´¨àµ?â?? à´µàµ?തിയàµ?à´? , തരവàµ?à´?"
-#: gschem/lib/system-gschemrc.scm:1420
+#: gschem/lib/system-gschemrc.scm:1422
msgid "Fill Type..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1421
+#: gschem/lib/system-gschemrc.scm:1423
msgid "Symbol Translate..."
msgstr "സിà´?ബലàµ?â?? വിവരàµ?â??à´¤àµ?തനà´?"
-#: gschem/lib/system-gschemrc.scm:1425
+#: gschem/lib/system-gschemrc.scm:1427
msgid "Invoke Macro"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1426
+#: gschem/lib/system-gschemrc.scm:1428
msgid "Embed Component/Picture"
msgstr "പ��/സാധന� �ള�ള����� ��യ��"
-#: gschem/lib/system-gschemrc.scm:1427
+#: gschem/lib/system-gschemrc.scm:1429
msgid "Unembed Component/Picture"
msgstr "പ��/സാധന� �ള�ള����� വ�ണ��യ�ന�ന� വ�യ������"
-#: gschem/lib/system-gschemrc.scm:1428
+#: gschem/lib/system-gschemrc.scm:1430
msgid "Update Component"
msgstr "സാധനതàµ?തിലàµ? മാറàµ?à´±à´?àµ?à´?à´³àµ?â?? à´¨à´?à´ªàµ?പിലàµ?â?? വരàµ?à´¤àµ?à´¤àµ?à´?"
-#: gschem/lib/system-gschemrc.scm:1429
+#: gschem/lib/system-gschemrc.scm:1431
msgid "Show/Hide Inv Text"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1430
-msgid "Make Inv Text Vis"
-msgstr ""
-
-#: gschem/lib/system-gschemrc.scm:1436
+#: gschem/lib/system-gschemrc.scm:1437
msgid "Copy into 1"
msgstr "à´ªà´?à´°àµ?â??à´¤àµ?à´¤àµ?à´? 1à´²àµ?à´?àµ?à´?àµ?"
-#: gschem/lib/system-gschemrc.scm:1437
+#: gschem/lib/system-gschemrc.scm:1438
msgid "Copy into 2"
msgstr "à´ªà´?à´°àµ?â??à´¤àµ?à´¤àµ?à´? 2à´²àµ?à´?àµ?à´?àµ?"
-#: gschem/lib/system-gschemrc.scm:1438
+#: gschem/lib/system-gschemrc.scm:1439
msgid "Copy into 3"
msgstr "à´ªà´?à´°àµ?â??à´¤àµ?à´¤àµ?à´? 3à´²àµ?à´?àµ?à´?àµ?"
-#: gschem/lib/system-gschemrc.scm:1439
+#: gschem/lib/system-gschemrc.scm:1440
msgid "Copy into 4"
msgstr "à´ªà´?à´°àµ?â??à´¤àµ?à´¤àµ?à´? 4à´²àµ?à´?àµ?à´?àµ?"
-#: gschem/lib/system-gschemrc.scm:1440
+#: gschem/lib/system-gschemrc.scm:1441
msgid "Copy into 5"
msgstr "à´ªà´?à´°àµ?â??à´¤àµ?à´¤àµ?à´? 5à´²àµ?à´?àµ?à´?àµ?"
-#: gschem/lib/system-gschemrc.scm:1441
+#: gschem/lib/system-gschemrc.scm:1442
msgid "Cut into 1"
msgstr "����� ��യ�� 1 ല�����"
-#: gschem/lib/system-gschemrc.scm:1442
+#: gschem/lib/system-gschemrc.scm:1443
msgid "Cut into 2"
msgstr "����� ��യ�� 2 ല�����"
-#: gschem/lib/system-gschemrc.scm:1443
+#: gschem/lib/system-gschemrc.scm:1444
msgid "Cut into 3"
msgstr "����� ��യ�� 3 ല�����"
-#: gschem/lib/system-gschemrc.scm:1444
+#: gschem/lib/system-gschemrc.scm:1445
msgid "Cut into 4"
msgstr "����� ��യ�� 4 ല�����"
-#: gschem/lib/system-gschemrc.scm:1445
+#: gschem/lib/system-gschemrc.scm:1446
msgid "Cut into 5"
msgstr "����� ��യ�� 5 ല�����"
-#: gschem/lib/system-gschemrc.scm:1446
+#: gschem/lib/system-gschemrc.scm:1447
msgid "Paste from 1"
msgstr "à´ªà´?à´°àµ?â??à´¤àµ?തി à´?à´?àµ?à´?àµ?à´?àµ?à´? 1 à´²àµ?â?? നിനàµ?à´¨àµ?à´?"
-#: gschem/lib/system-gschemrc.scm:1447
+#: gschem/lib/system-gschemrc.scm:1448
msgid "Paste from 2"
msgstr "à´ªà´?à´°àµ?â??à´¤àµ?തി à´?à´?àµ?à´?àµ?à´?àµ?à´? 2 à´²àµ?â?? നിനàµ?à´¨àµ?à´?"
-#: gschem/lib/system-gschemrc.scm:1448
+#: gschem/lib/system-gschemrc.scm:1449
msgid "Paste from 3"
msgstr "à´ªà´?à´°àµ?â??à´¤àµ?തി à´?à´?àµ?à´?àµ?à´?àµ?à´? 3à´²àµ?â?? നിനàµ?à´¨àµ?à´?"
-#: gschem/lib/system-gschemrc.scm:1449
+#: gschem/lib/system-gschemrc.scm:1450
msgid "Paste from 4"
msgstr "à´ªà´?à´°àµ?â??à´¤àµ?തി à´?à´?àµ?à´?àµ?à´?àµ?à´? 4à´²àµ?â?? നിനàµ?à´¨àµ?à´?"
-#: gschem/lib/system-gschemrc.scm:1450
+#: gschem/lib/system-gschemrc.scm:1451
msgid "Paste from 5"
msgstr "à´ªà´?à´°àµ?â??à´¤àµ?തി à´?à´?àµ?à´?àµ?à´?àµ?à´? 5 à´²àµ?â?? നിനàµ?à´¨àµ?à´?"
-#: gschem/lib/system-gschemrc.scm:1456
+#: gschem/lib/system-gschemrc.scm:1457
msgid "_Redraw"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1457
+#: gschem/lib/system-gschemrc.scm:1458
msgid "_Pan"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1458
+#: gschem/lib/system-gschemrc.scm:1459
msgid "Zoom _Box"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1459
+#: gschem/lib/system-gschemrc.scm:1460
msgid "Zoom _Extents"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1460
+#: gschem/lib/system-gschemrc.scm:1461
msgid "Zoom _In"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1461
+#: gschem/lib/system-gschemrc.scm:1462
msgid "Zoom _Out"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1462
+#: gschem/lib/system-gschemrc.scm:1463
msgid "Zoom _Full"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1464
+#: gschem/lib/system-gschemrc.scm:1465
msgid "_Dark color scheme"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1465
+#: gschem/lib/system-gschemrc.scm:1466
msgid "_Light color scheme"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1466
+#: gschem/lib/system-gschemrc.scm:1467
msgid "B_W color scheme"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1473
+#: gschem/lib/system-gschemrc.scm:1474
msgid "_Manager..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1474
+#: gschem/lib/system-gschemrc.scm:1475
msgid "_Previous"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1475
+#: gschem/lib/system-gschemrc.scm:1476
msgid "_Next"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1476
+#: gschem/lib/system-gschemrc.scm:1477
msgid "Ne_w"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1480
+#: gschem/lib/system-gschemrc.scm:1481
msgid "_Discard"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1486
+#: gschem/lib/system-gschemrc.scm:1487
msgid "_Component..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1487
+#: gschem/lib/system-gschemrc.scm:1488
msgid "_Net"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1488
+#: gschem/lib/system-gschemrc.scm:1489
msgid "B_us"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1489
+#: gschem/lib/system-gschemrc.scm:1490
msgid "_Attribute..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1490
+#: gschem/lib/system-gschemrc.scm:1491
msgid "_Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1492
+#: gschem/lib/system-gschemrc.scm:1493
msgid "_Line"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1493
+#: gschem/lib/system-gschemrc.scm:1494
msgid "_Box"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1494
+#: gschem/lib/system-gschemrc.scm:1495
msgid "C_ircle"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1495
+#: gschem/lib/system-gschemrc.scm:1496
msgid "A_rc"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1496
+#: gschem/lib/system-gschemrc.scm:1497
msgid "_Pin"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1497
+#: gschem/lib/system-gschemrc.scm:1498
msgid "Pictu_re..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1503
+#: gschem/lib/system-gschemrc.scm:1504
msgid "_Down Schematic"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1504
+#: gschem/lib/system-gschemrc.scm:1505
msgid "Down _Symbol"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1505
+#: gschem/lib/system-gschemrc.scm:1506
msgid "_Up"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1506
+#: gschem/lib/system-gschemrc.scm:1507
msgid "D_ocumentation..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1512
+#: gschem/lib/system-gschemrc.scm:1513
msgid "_Attach"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1513
+#: gschem/lib/system-gschemrc.scm:1514
msgid "_Detach"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1514
+#: gschem/lib/system-gschemrc.scm:1515
msgid "Show _Value"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1515
+#: gschem/lib/system-gschemrc.scm:1516
msgid "Show _Name"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1516
+#: gschem/lib/system-gschemrc.scm:1517
msgid "Show _Both"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1517
+#: gschem/lib/system-gschemrc.scm:1518
msgid "_Toggle Visibility"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1519
+#: gschem/lib/system-gschemrc.scm:1520
msgid "_Find Specific Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1520
+#: gschem/lib/system-gschemrc.scm:1521
msgid "_Hide Specific Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1521
+#: gschem/lib/system-gschemrc.scm:1522
msgid "_Show Specific Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1522
+#: gschem/lib/system-gschemrc.scm:1523
msgid "A_utonumber Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1528
+#: gschem/lib/system-gschemrc.scm:1529
msgid "_Text Size..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1529
+#: gschem/lib/system-gschemrc.scm:1530
msgid "Cycle _grid styles"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1530
+#: gschem/lib/system-gschemrc.scm:1531
msgid "Toggle _Snap On/Off"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1531
+#: gschem/lib/system-gschemrc.scm:1532
msgid "Snap Grid S_pacing..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1532
+#: gschem/lib/system-gschemrc.scm:1533
msgid "Scale _up Grid Spacing"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1534
+#: gschem/lib/system-gschemrc.scm:1535
msgid "Scale _down Grid Spacing"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1536
+#: gschem/lib/system-gschemrc.scm:1537
msgid "Toggle _Outline/Box"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1538
+#: gschem/lib/system-gschemrc.scm:1539
msgid "Toggle Net _Rubberband"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1539
+#: gschem/lib/system-gschemrc.scm:1540
msgid "Toggle _Magnetic Net"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1540
+#: gschem/lib/system-gschemrc.scm:1541
msgid "Show _Log Window..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1542
+#: gschem/lib/system-gschemrc.scm:1543
msgid "Show _Coord Window..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1558
+#: gschem/lib/system-gschemrc.scm:1559
msgid "gEDA Docu_mentation..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1559
+#: gschem/lib/system-gschemrc.scm:1560
msgid "gschem _FAQ..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1560
+#: gschem/lib/system-gschemrc.scm:1561
msgid "gEDA _Wiki..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1561
+#: gschem/lib/system-gschemrc.scm:1562
msgid "Component D_ocumentation..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1563
+#: gschem/lib/system-gschemrc.scm:1564
msgid "_Hotkeys..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1564
+#: gschem/lib/system-gschemrc.scm:1565
msgid "_About..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1570
+#: gschem/lib/system-gschemrc.scm:1571
msgid "_File"
msgstr "ഫയലàµ?â??"
-#: gschem/lib/system-gschemrc.scm:1571
+#: gschem/lib/system-gschemrc.scm:1572
msgid "_Edit"
msgstr "തിര�ത�തിയ�ഴ�ത�� (_Edit)"
-#: gschem/lib/system-gschemrc.scm:1572
+#: gschem/lib/system-gschemrc.scm:1573
msgid "_Buffer"
msgstr "ബഫരàµ?â??"
-#: gschem/lib/system-gschemrc.scm:1573
+#: gschem/lib/system-gschemrc.scm:1574
msgid "_View"
msgstr "വ���ഷണ�"
-#: gschem/lib/system-gschemrc.scm:1574
+#: gschem/lib/system-gschemrc.scm:1575
msgid "_Page"
msgstr "താള�"
-#: gschem/lib/system-gschemrc.scm:1575
+#: gschem/lib/system-gschemrc.scm:1576
msgid "_Add"
msgstr "à´?àµ?à´?àµ?à´?à´¿à´?àµ?à´?àµ?à´°àµ?â??à´?àµ?à´?àµ?à´?"
-#: gschem/lib/system-gschemrc.scm:1576
+#: gschem/lib/system-gschemrc.scm:1577
msgid "Hie_rarchy"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1577
+#: gschem/lib/system-gschemrc.scm:1578
msgid "A_ttributes"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1578
+#: gschem/lib/system-gschemrc.scm:1579
msgid "_Options"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1579
+#: gschem/lib/system-gschemrc.scm:1580
msgid "_Help"
msgstr ""
diff --git a/gschem/po/nl.po b/gschem/po/nl.po
index 98f931d..ad9b9a3 100644
--- a/gschem/po/nl.po
+++ b/gschem/po/nl.po
@@ -6,7 +6,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda-gschem\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2010-11-07 13:37+0000\n"
+"POT-Creation-Date: 2011-01-16 00:11-0500\n"
"PO-Revision-Date: 2010-02-14 01:04+0000\n"
"Last-Translator: Bert Timmerman <bert.timmerman@xxxxxxxxx>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -21,17 +21,17 @@ msgstr ""
msgid "Zoom too small! Cannot zoom further.\n"
msgstr "Vergroting te klein! Kan niet verder vergroten.\n"
-#: gschem/src/g_funcs.c:339 gschem/src/i_callbacks.c:68
+#: gschem/src/g_funcs.c:347 gschem/src/i_callbacks.c:68
#, c-format
msgid "Could not fork\n"
msgstr "Kan niet afsplitsen\n"
-#: gschem/src/g_funcs.c:355 gschem/src/i_callbacks.c:78
+#: gschem/src/g_funcs.c:363 gschem/src/i_callbacks.c:78
#, c-format
msgid "Could not invoke %s\n"
msgstr "Kan %s niet aanroepen\n"
-#: gschem/src/g_funcs.c:361 gschem/src/i_callbacks.c:82
+#: gschem/src/g_funcs.c:369 gschem/src/i_callbacks.c:82
msgid "Documentation commands not supported under MinGW.\n"
msgstr "Documentatie opdrachten niet ondersteund bij MinGW.\n"
@@ -130,12 +130,12 @@ msgstr "Ongeldige versterking [%d] overgedragen aan zoom-gain\n"
msgid "Invalid number of steps [%d] scrollpan-steps\n"
msgstr "Ongeldig aantal stappen [%d] scrollpan-steps\n"
-#: gschem/src/gschem.c:184
+#: gschem/src/gschem.c:188
#, c-format
msgid "gEDA/gschem version %s%s.%s\n"
msgstr "gEDA/gschem versie %s%s.%s\n"
-#: gschem/src/gschem.c:187
+#: gschem/src/gschem.c:191
msgid ""
"gEDA/gschem comes with ABSOLUTELY NO WARRANTY; see COPYING for more "
"details.\n"
@@ -143,14 +143,14 @@ msgstr ""
"gEDA/gschem komt ABSOLUUT ZONDER GARANTIE; zie het COPYING bestand voor meer "
"informatie.\n"
-#: gschem/src/gschem.c:189
+#: gschem/src/gschem.c:193
msgid ""
"This is free software, and you are welcome to redistribute it under certain\n"
msgstr ""
"Dit is vrije software, en je wordt aangemoedigt dit te herdistribueren onder "
"bepaalde\n"
-#: gschem/src/gschem.c:191
+#: gschem/src/gschem.c:195
msgid ""
"conditions; please see the COPYING file for more details.\n"
"\n"
@@ -158,17 +158,17 @@ msgstr ""
"condities; zie het COPYING bestand voor meer informatie.\n"
"\n"
-#: gschem/src/gschem.c:194
+#: gschem/src/gschem.c:198
#, c-format
msgid "This is the MINGW32 port.\n"
msgstr "Dit is de MINGW32 versie.\n"
-#: gschem/src/gschem.c:198
+#: gschem/src/gschem.c:202
#, c-format
msgid "Current locale settings: %s\n"
msgstr "Huidige locale instellingen: %s\n"
-#: gschem/src/gschem.c:213
+#: gschem/src/gschem.c:218
msgid ""
"You must set the GEDADATA environment variable!\n"
"\n"
@@ -180,31 +180,21 @@ msgstr ""
"gschem kan geen lokatie vinden van de data bestanden. Je moet de GEDADATA\n"
"omgevingsvariablele naar de juiste lokatie laten wijzen.\n"
-#: gschem/src/gschem.c:248
+#: gschem/src/gschem.c:256
#, c-format
msgid "Couldn't find init scm file [%s]\n"
msgstr "Kan init scm bestand [%s]niet vinden\n"
-#: gschem/src/gschem.c:252
+#: gschem/src/gschem.c:260
#, c-format
msgid "Read init scm file [%s]\n"
msgstr "Lees init scm bestand [%s]\n"
-#: gschem/src/gschem.c:256
+#: gschem/src/gschem.c:264
#, c-format
msgid "Failed to read init scm file [%s]\n"
msgstr "Fout bij het lezen van het init scm bestand [%s]\n"
-#: gschem/src/gschem.c:317
-#, c-format
-msgid "Scheme directory NOT set!\n"
-msgstr "Scheme bestandenmap is NIET ingesteld!\n"
-
-#: gschem/src/gschem.c:324 gschem/src/x_script.c:66
-#, c-format
-msgid "Executing guile script [%s]\n"
-msgstr "Bezig met uitvoeren van guile script [%s]\n"
-
#: gschem/src/gschem_cairo.c:310
#, c-format
msgid "Unknown end for line (%d)\n"
@@ -228,11 +218,11 @@ msgstr "Component Mode"
msgid "Text Mode"
msgstr "Tekst Mode"
-#: gschem/src/i_basic.c:84 gschem/lib/system-gschemrc.scm:1409
+#: gschem/src/i_basic.c:84 gschem/lib/system-gschemrc.scm:1411
msgid "Copy Mode"
msgstr "Kopieer Mode"
-#: gschem/src/i_basic.c:87 gschem/lib/system-gschemrc.scm:1411
+#: gschem/src/i_basic.c:87 gschem/lib/system-gschemrc.scm:1413
msgid "Move Mode"
msgstr "Verplaats Mode"
@@ -240,7 +230,7 @@ msgstr "Verplaats Mode"
msgid "Rotate Mode"
msgstr "Rotatie Mode"
-#: gschem/src/i_basic.c:91 gschem/lib/system-gschemrc.scm:1413
+#: gschem/src/i_basic.c:91 gschem/lib/system-gschemrc.scm:1415
msgid "Mirror Mode"
msgstr "Spiegel Mode"
@@ -293,22 +283,22 @@ msgstr "Boog Mode"
msgid "Pin Mode"
msgstr "Pen Mode"
-#: gschem/src/i_basic.c:135 gschem/src/i_callbacks.c:544
-#: gschem/src/i_callbacks.c:568
+#: gschem/src/i_basic.c:135 gschem/src/i_callbacks.c:576
+#: gschem/src/i_callbacks.c:600
msgid "Copy"
msgstr "Kopieer"
-#: gschem/src/i_basic.c:137 gschem/src/i_callbacks.c:634
-#: gschem/src/i_callbacks.c:658
+#: gschem/src/i_basic.c:137 gschem/src/i_callbacks.c:666
+#: gschem/src/i_callbacks.c:690
msgid "Move"
msgstr "Verplaats"
-#: gschem/src/i_basic.c:139 gschem/src/i_callbacks.c:589
-#: gschem/src/i_callbacks.c:613
+#: gschem/src/i_basic.c:139 gschem/src/i_callbacks.c:621
+#: gschem/src/i_callbacks.c:645
msgid "Multiple Copy"
msgstr "Meervoudig Kopieren"
-#: gschem/src/i_basic.c:142 gschem/lib/system-gschemrc.scm:1410
+#: gschem/src/i_basic.c:142 gschem/lib/system-gschemrc.scm:1412
msgid "Multiple Copy Mode"
msgstr "Meervoudige Kopieer Mode"
@@ -328,7 +318,7 @@ msgstr "Hersnappen Aktief"
msgid "Action"
msgstr "Aktie"
-#: gschem/src/i_basic.c:260 gschem/src/x_dialog.c:2312
+#: gschem/src/i_basic.c:260 gschem/src/x_dialog.c:2316
#: gschem/src/x_window.c:491
msgid "Stroke"
msgstr "Slag"
@@ -359,7 +349,7 @@ msgstr "Raster(%s, %s)"
msgid "Documentation for [%s,%s,%s,%s]\n"
msgstr "Documentatie voor [%s,%s,%s,%s]\n"
-#: gschem/src/i_callbacks.c:123 gschem/src/i_callbacks.c:1699
+#: gschem/src/i_callbacks.c:123 gschem/src/i_callbacks.c:1706
#, c-format
msgid "New page created [%s]\n"
msgstr "Nieuwe pagina gemaakt [%s]\n"
@@ -381,69 +371,69 @@ msgstr "Alles Opgeslagen"
msgid "Closing Window\n"
msgstr "Sluit Venster\n"
-#: gschem/src/i_callbacks.c:549 gschem/src/i_callbacks.c:594
-#: gschem/src/i_callbacks.c:639
+#: gschem/src/i_callbacks.c:581 gschem/src/i_callbacks.c:626
+#: gschem/src/i_callbacks.c:671
msgid "Select objs first"
msgstr "Selecteer voorwerpen eerst"
-#: gschem/src/i_callbacks.c:678 gschem/src/x_multiattrib.c:1491
+#: gschem/src/i_callbacks.c:710 gschem/src/x_multiattrib.c:1503
msgid "Delete"
msgstr "Verwijder"
-#: gschem/src/i_callbacks.c:703
+#: gschem/src/i_callbacks.c:735
msgid "Edit"
msgstr "Bewerk"
-#: gschem/src/i_callbacks.c:718
+#: gschem/src/i_callbacks.c:750
msgid "Edit pin type"
msgstr "Bewerk pen type"
-#: gschem/src/i_callbacks.c:737
+#: gschem/src/i_callbacks.c:769
msgid "Edit Text"
msgstr "Bewerk Tekst"
-#: gschem/src/i_callbacks.c:760
+#: gschem/src/i_callbacks.c:792
msgid "Slot"
msgstr "Slot"
-#: gschem/src/i_callbacks.c:777
+#: gschem/src/i_callbacks.c:809
msgid "Color"
msgstr "Kleur"
-#: gschem/src/i_callbacks.c:814 gschem/src/i_callbacks.c:859
+#: gschem/src/i_callbacks.c:846 gschem/src/i_callbacks.c:891
msgid "Rotate"
msgstr "Roteer"
-#: gschem/src/i_callbacks.c:882 gschem/src/i_callbacks.c:907
+#: gschem/src/i_callbacks.c:913 gschem/src/i_callbacks.c:938
msgid "Mirror"
msgstr "Spiegel"
-#: gschem/src/i_callbacks.c:928 gschem/src/x_dialog.c:2315
-#: gschem/lib/system-gschemrc.scm:1422
+#: gschem/src/i_callbacks.c:959 gschem/src/x_dialog.c:2319
+#: gschem/lib/system-gschemrc.scm:1424
msgid "Lock"
msgstr "Vergrendel"
-#: gschem/src/i_callbacks.c:946 gschem/lib/system-gschemrc.scm:1423
+#: gschem/src/i_callbacks.c:977 gschem/lib/system-gschemrc.scm:1425
msgid "Unlock"
msgstr "Ontgrendel"
-#: gschem/src/i_callbacks.c:964 gschem/src/x_dialog.c:1734
+#: gschem/src/i_callbacks.c:995 gschem/src/x_dialog.c:1737
msgid "Translate"
msgstr "Verplaats"
-#: gschem/src/i_callbacks.c:967
+#: gschem/src/i_callbacks.c:998
msgid "WARNING: Do not translate with snap off!\n"
msgstr "WAARSCHUWING: Niet verplaatsen met snap uit!\n"
-#: gschem/src/i_callbacks.c:968
+#: gschem/src/i_callbacks.c:999
msgid "WARNING: Turning snap on and continuing with translate.\n"
msgstr "WAARSCHUWING: Zet snap aan en vervolg de verplaatsing.\n"
-#: gschem/src/i_callbacks.c:975
+#: gschem/src/i_callbacks.c:1006
msgid "WARNING: Snap grid size is not equal to 100!\n"
msgstr "WAARSCHUWING: Snap grid waarde is niet gelijk aan 100!\n"
-#: gschem/src/i_callbacks.c:977
+#: gschem/src/i_callbacks.c:1008
msgid ""
"WARNING: If you are translating a symbol to the origin, the snap grid size "
"should be set to 100\n"
@@ -451,176 +441,172 @@ msgstr ""
"WAARSCHUWING: Als je een symbool naar de oorsprong verschuift, dan moet de "
"snap grip waarde op 100 gezet worden\n"
-#: gschem/src/i_callbacks.c:1008
+#: gschem/src/i_callbacks.c:1039
msgid "Embed"
msgstr "Insluiten"
-#: gschem/src/i_callbacks.c:1047
+#: gschem/src/i_callbacks.c:1078
msgid "Unembed"
msgstr "Uitsluiten"
-#: gschem/src/i_callbacks.c:1089
+#: gschem/src/i_callbacks.c:1120
msgid "Update"
msgstr "Vernieuw"
-#: gschem/src/i_callbacks.c:1136
+#: gschem/src/i_callbacks.c:1167
msgid "ShowHidden"
msgstr "ZichtbaarVerborgen"
-#: gschem/src/i_callbacks.c:1160
-msgid "MakeVisible"
-msgstr "MaakZichtbaar"
-
-#: gschem/src/i_callbacks.c:1466 gschem/src/i_callbacks.c:1538
+#: gschem/src/i_callbacks.c:1473 gschem/src/i_callbacks.c:1545
msgid "Pan"
msgstr "Schuif"
-#: gschem/src/i_callbacks.c:1743
+#: gschem/src/i_callbacks.c:1750
msgid "Really revert page?"
msgstr "Echt Terughalen pagina?"
-#: gschem/src/i_callbacks.c:1813
+#: gschem/src/i_callbacks.c:1820
msgid "Copy to clipboard"
msgstr "Kopieer naar klembord"
-#: gschem/src/i_callbacks.c:1831
+#: gschem/src/i_callbacks.c:1838
msgid "Cut to clipboard"
msgstr "Knip naar klembord"
-#: gschem/src/i_callbacks.c:1849
+#: gschem/src/i_callbacks.c:1856
msgid "Paste from clipboard"
msgstr "Plak van klembord"
-#: gschem/src/i_callbacks.c:1861 gschem/src/i_callbacks.c:2100
-#: gschem/src/i_callbacks.c:2122 gschem/src/i_callbacks.c:2144
-#: gschem/src/i_callbacks.c:2166 gschem/src/i_callbacks.c:2188
+#: gschem/src/i_callbacks.c:1868 gschem/src/i_callbacks.c:2107
+#: gschem/src/i_callbacks.c:2129 gschem/src/i_callbacks.c:2151
+#: gschem/src/i_callbacks.c:2173 gschem/src/i_callbacks.c:2195
msgid "Empty buffer"
msgstr "Maak buffer leeg"
-#: gschem/src/i_callbacks.c:1906
+#: gschem/src/i_callbacks.c:1913
msgid "Copy 1"
msgstr "Kopieer 1"
-#: gschem/src/i_callbacks.c:1925
+#: gschem/src/i_callbacks.c:1932
msgid "Copy 2"
msgstr "Kopieer 2"
-#: gschem/src/i_callbacks.c:1944
+#: gschem/src/i_callbacks.c:1951
msgid "Copy 3"
msgstr "Kopieer 3"
-#: gschem/src/i_callbacks.c:1963
+#: gschem/src/i_callbacks.c:1970
msgid "Copy 4"
msgstr "Kopieer 4"
-#: gschem/src/i_callbacks.c:1982
+#: gschem/src/i_callbacks.c:1989
msgid "Copy 5"
msgstr "Kopieer 5"
-#: gschem/src/i_callbacks.c:2001
+#: gschem/src/i_callbacks.c:2008
msgid "Cut 1"
msgstr "Knip 1"
-#: gschem/src/i_callbacks.c:2020
+#: gschem/src/i_callbacks.c:2027
msgid "Cut 2"
msgstr "Knip 2"
-#: gschem/src/i_callbacks.c:2039
+#: gschem/src/i_callbacks.c:2046
msgid "Cut 3"
msgstr "Knip 3"
-#: gschem/src/i_callbacks.c:2058
+#: gschem/src/i_callbacks.c:2065
msgid "Cut 4"
msgstr "Knip 4"
-#: gschem/src/i_callbacks.c:2077
+#: gschem/src/i_callbacks.c:2084
msgid "Cut 5"
msgstr "Knip 5"
-#: gschem/src/i_callbacks.c:2093
+#: gschem/src/i_callbacks.c:2100
msgid "Paste 1"
msgstr "Plak 1"
-#: gschem/src/i_callbacks.c:2115
+#: gschem/src/i_callbacks.c:2122
msgid "Paste 2"
msgstr "Plak 2"
-#: gschem/src/i_callbacks.c:2137
+#: gschem/src/i_callbacks.c:2144
msgid "Paste 3"
msgstr "Plak 3"
-#: gschem/src/i_callbacks.c:2159
+#: gschem/src/i_callbacks.c:2166
msgid "Paste 4"
msgstr "Plak 4"
-#: gschem/src/i_callbacks.c:2181
+#: gschem/src/i_callbacks.c:2188
msgid "Paste 5"
msgstr "Plak 5"
-#: gschem/src/i_callbacks.c:2318 gschem/src/x_window.c:355
+#: gschem/src/i_callbacks.c:2325 gschem/src/x_window.c:355
msgid "Component"
msgstr "Component"
-#: gschem/src/i_callbacks.c:2354 gschem/src/i_callbacks.c:2373
-#: gschem/src/x_dialog.c:2285
+#: gschem/src/i_callbacks.c:2361 gschem/src/i_callbacks.c:2380
+#: gschem/src/x_dialog.c:2289
msgid "Attribute"
msgstr "Attribuut"
-#: gschem/src/i_callbacks.c:2395 gschem/src/i_callbacks.c:2422
-#: gschem/src/x_dialog.c:2282
+#: gschem/src/i_callbacks.c:2402 gschem/src/i_callbacks.c:2429
+#: gschem/src/x_dialog.c:2286
msgid "Net"
msgstr "Draad"
-#: gschem/src/i_callbacks.c:2466 gschem/src/i_callbacks.c:2493
-#: gschem/src/x_dialog.c:2300 gschem/src/x_window.c:375
+#: gschem/src/i_callbacks.c:2473 gschem/src/i_callbacks.c:2500
+#: gschem/src/x_dialog.c:2304 gschem/src/x_window.c:375
msgid "Bus"
msgstr "Bus"
-#: gschem/src/i_callbacks.c:2574 gschem/src/i_callbacks.c:2597
+#: gschem/src/i_callbacks.c:2581 gschem/src/i_callbacks.c:2604
msgid "Line"
msgstr "Lijn"
-#: gschem/src/i_callbacks.c:2619 gschem/src/i_callbacks.c:2642
+#: gschem/src/i_callbacks.c:2626 gschem/src/i_callbacks.c:2649
msgid "Box"
msgstr "Rechthoek"
-#: gschem/src/i_callbacks.c:2698 gschem/src/i_callbacks.c:2722
+#: gschem/src/i_callbacks.c:2705 gschem/src/i_callbacks.c:2729
msgid "Circle"
msgstr "Cirkel"
-#: gschem/src/i_callbacks.c:2744 gschem/src/i_callbacks.c:2767
+#: gschem/src/i_callbacks.c:2751 gschem/src/i_callbacks.c:2774
msgid "Arc"
msgstr "Boog"
-#: gschem/src/i_callbacks.c:2789 gschem/src/i_callbacks.c:2812
-#: gschem/src/x_dialog.c:2273
+#: gschem/src/i_callbacks.c:2796 gschem/src/i_callbacks.c:2819
+#: gschem/src/x_dialog.c:2277
msgid "Pin"
msgstr "Pen"
-#: gschem/src/i_callbacks.c:2871
+#: gschem/src/i_callbacks.c:2878
#, c-format
msgid "Searching for source [%s]\n"
msgstr "Zoek naar bron [%s]\n"
-#: gschem/src/i_callbacks.c:2895
+#: gschem/src/i_callbacks.c:2902
#, c-format
msgid "Cannot find source [%s]\n"
msgstr "Kan bron [%s] niet vinden\n"
-#: gschem/src/i_callbacks.c:2964
+#: gschem/src/i_callbacks.c:2965
#, c-format
msgid "Searching for symbol [%s]\n"
msgstr "Zoek naar symbool [%s]\n"
-#: gschem/src/i_callbacks.c:2970
+#: gschem/src/i_callbacks.c:2971
msgid "Symbol is not a real file. Symbol cannot be loaded.\n"
msgstr "Symbool is geen werkelijk bestand. Symbool kan niet geladen worden.\n"
-#: gschem/src/i_callbacks.c:3001
+#: gschem/src/i_callbacks.c:3002
msgid "Cannot find any schematics above the current one!\n"
msgstr "Kan geen schema's vinden boven het huidige schema!\n"
-#: gschem/src/i_callbacks.c:3055
+#: gschem/src/i_callbacks.c:3056
msgid ""
"This command retrieves the component documentation from the web, but there "
"is no component selected"
@@ -628,84 +614,84 @@ msgstr ""
"Dit commando haalt de component documentatie van het web, maar er is geen "
"component geselecteerd"
-#: gschem/src/i_callbacks.c:3083
+#: gschem/src/i_callbacks.c:3084
msgid "Attach"
msgstr "Vastmaken"
-#: gschem/src/i_callbacks.c:3130
+#: gschem/src/i_callbacks.c:3131
msgid "Detach"
msgstr "Losmaken"
-#: gschem/src/i_callbacks.c:3165
+#: gschem/src/i_callbacks.c:3166
msgid "ShowN"
msgstr "ToonN"
-#: gschem/src/i_callbacks.c:3201
+#: gschem/src/i_callbacks.c:3202
msgid "ShowV"
msgstr "ToonW"
-#: gschem/src/i_callbacks.c:3237
+#: gschem/src/i_callbacks.c:3238
msgid "ShowB"
msgstr "ToonB"
-#: gschem/src/i_callbacks.c:3274
+#: gschem/src/i_callbacks.c:3275
msgid "VisToggle"
msgstr "SchakelZichtbaarheid"
-#: gschem/src/i_callbacks.c:3304
+#: gschem/src/i_callbacks.c:3305
#, c-format
msgid "Sorry but this is a non-functioning menu option\n"
msgstr "Sorry, maar dit is een niet werkende menu optie\n"
-#: gschem/src/i_callbacks.c:3394
+#: gschem/src/i_callbacks.c:3395
msgid "Action feedback mode set to OUTLINE\n"
msgstr "Aktie terugkoppel mode is ingesteld op OUTLINE\n"
-#: gschem/src/i_callbacks.c:3397
+#: gschem/src/i_callbacks.c:3398
msgid "Action feedback mode set to BOUNDINGBOX\n"
msgstr "Aktie terugkoppel mode is ingesteld op BOUNDINGBOX.\n"
-#: gschem/src/i_callbacks.c:3422
+#: gschem/src/i_callbacks.c:3423
msgid "Grid OFF\n"
msgstr "Raster UIT\n"
-#: gschem/src/i_callbacks.c:3423
+#: gschem/src/i_callbacks.c:3424
msgid "Dot grid selected\n"
msgstr "Punt raster geselecteerd\n"
-#: gschem/src/i_callbacks.c:3424
+#: gschem/src/i_callbacks.c:3425
msgid "Mesh grid selected\n"
msgstr "Maas raster geselecteerd\n"
-#: gschem/src/i_callbacks.c:3445
+#: gschem/src/i_callbacks.c:3446
msgid "Snap OFF (CAUTION!)\n"
msgstr "Snap UIT (PAS OP!)\n"
-#: gschem/src/i_callbacks.c:3448
+#: gschem/src/i_callbacks.c:3449
msgid "Snap ON\n"
msgstr "Snap AAN\n"
-#: gschem/src/i_callbacks.c:3451
+#: gschem/src/i_callbacks.c:3452
msgid "Snap back to the grid (CAUTION!)\n"
msgstr "Snap terug op raster (PAS OP!)\n"
-#: gschem/src/i_callbacks.c:3477
+#: gschem/src/i_callbacks.c:3478
msgid "Rubber band OFF \n"
msgstr "Elastiek band UIT \n"
-#: gschem/src/i_callbacks.c:3480
+#: gschem/src/i_callbacks.c:3481
msgid "Rubber band ON\n"
msgstr "Elastiek band AAN\n"
-#: gschem/src/i_callbacks.c:3495
+#: gschem/src/i_callbacks.c:3496
msgid "magnetic net mode: ON\n"
msgstr "magnetische draad mode: AAN\n"
-#: gschem/src/i_callbacks.c:3498
+#: gschem/src/i_callbacks.c:3499
msgid "magnetic net mode: OFF\n"
msgstr "magnetische draad mode: UIT\n"
-#: gschem/src/o_box.c:153
+#: gschem/src/o_box.c:149
#, c-format
msgid "Unknown type for box (fill)!\n"
msgstr "Onbekend type voor rechthoek (arcering)!\n"
@@ -725,17 +711,17 @@ msgstr "o_buffer_cut: Ongeldige buffer %i\n"
msgid "Got an invalid buffer_number [o_buffer_paste_start]\n"
msgstr "Ontving een ongeldig buffernummer [o_buffer_paste_start]\n"
-#: gschem/src/o_bus.c:118
+#: gschem/src/o_bus.c:117
#, c-format
msgid "Got an invalid which one in o_bus_draw_stretch\n"
msgstr "Ontving ereen die ongeldig is in o_bus_draw_stretch\n"
-#: gschem/src/o_circle.c:134
+#: gschem/src/o_circle.c:130
#, c-format
msgid "Unknown type for circle (fill)!\n"
msgstr "Onbekend type voor cirkel (arcering)!\n"
-#: gschem/src/o_complex.c:243 gschem/src/o_complex.c:247
+#: gschem/src/o_complex.c:237 gschem/src/o_complex.c:241
#, c-format
msgid "Translating schematic [%d %d]\n"
msgstr "Vertaal schema [%d %d]\n"
@@ -753,37 +739,37 @@ msgstr "Object reeds vergrendeld\n"
msgid "Object already unlocked\n"
msgstr "Object reeds ontgrendeld\n"
-#: gschem/src/o_misc.c:413
+#: gschem/src/o_misc.c:409
msgid "Hidden text is now visible\n"
msgstr "Verborgen tekst is nu zichtbaar\n"
-#: gschem/src/o_misc.c:415
+#: gschem/src/o_misc.c:411
msgid "Hidden text is now invisible\n"
msgstr "Verborgen tekst is nu onzichtbaar\n"
-#: gschem/src/o_misc.c:668
+#: gschem/src/o_misc.c:636
#, c-format
msgid "Could not find symbol [%s] in library. Update failed.\n"
msgstr "Kan symbool [%s] niet in bibliotheek vinden. Vernieuwen faalde.\n"
-#: gschem/src/o_misc.c:783
+#: gschem/src/o_misc.c:751
#, c-format
msgid "o_autosave_backups: Can't get the real filename of %s."
msgstr "o_autosave_backups: Kan de echte bestandsnaam van %s niet krijgen."
-#: gschem/src/o_misc.c:827
+#: gschem/src/o_misc.c:795
#, c-format
msgid "Could NOT set previous backup file [%s] read-write\n"
msgstr ""
"Voorgaande reserve bestand [%s] kan NIET op lezen-schrijven ingesteld "
"worden\n"
-#: gschem/src/o_misc.c:845
+#: gschem/src/o_misc.c:815
#, c-format
msgid "Could NOT set backup file [%s] readonly\n"
msgstr "Reserve bestand [%s] kan NIET op alleen-lezen ingesteld worden\n"
-#: gschem/src/o_misc.c:850
+#: gschem/src/o_misc.c:820
#, c-format
msgid "Could NOT save backup file [%s]\n"
msgstr "Reserve bestand [%s] kan NIET opgeslagen worden\n"
@@ -803,38 +789,38 @@ msgstr "OH! probeerde er een te vinden, maar heb 'em niet gevonden!\n"
msgid "Got a non line object in o_move_check_endpoint\n"
msgstr "Ontving een niet lijn object in o_move_check_endpoint\n"
-#: gschem/src/o_net.c:159
+#: gschem/src/o_net.c:158
#, c-format
msgid "Got an invalid which one in o_net_draw_stretch\n"
msgstr "Ontving er een die ongeldig is in o_net_draw_stretch\n"
-#: gschem/src/o_net.c:538
+#: gschem/src/o_net.c:537
msgid "Warning: Starting net at off grid coordinate\n"
msgstr "Waarschuwing: begin van draad niet op raster coordinaat\n"
-#: gschem/src/o_net.c:600
+#: gschem/src/o_net.c:599
msgid "Warning: Ending net at off grid coordinate\n"
msgstr "Waarschuwing: einde van draad niet op raster coordinaat\n"
-#: gschem/src/o_net.c:932 gschem/src/o_net.c:969 gschem/src/o_net.c:1040
-#: gschem/src/o_net.c:1076
+#: gschem/src/o_net.c:931 gschem/src/o_net.c:968 gschem/src/o_net.c:1039
+#: gschem/src/o_net.c:1075
#, c-format
msgid "Tried to add more than two bus rippers. Internal gschem error.\n"
msgstr ""
"Probeerde meer dan twee busrippers toe te voegen. Interne gschem fout.\n"
-#: gschem/src/o_net.c:1144
+#: gschem/src/o_net.c:1143
#, c-format
msgid "Bus ripper symbol [%s] was not found in any component library\n"
msgstr ""
"Bus ripper symbool [%s] niet gevonden in een van de component bibliotheken\n"
-#: gschem/src/o_path.c:352
+#: gschem/src/o_path.c:348
#, c-format
msgid "Unknown type for path (fill)!\n"
msgstr "Onbekend type voor pad (arcering)!\n"
-#: gschem/src/o_picture.c:163 gschem/src/o_picture.c:539
+#: gschem/src/o_picture.c:163 gschem/src/o_picture.c:537
#, c-format
msgid "Failed to load picture: %s"
msgstr "Fout bij het lezen van afbeelding: %s"
@@ -843,7 +829,7 @@ msgstr "Fout bij het lezen van afbeelding: %s"
msgid "Picture"
msgstr "Afbeelding"
-#: gschem/src/o_picture.c:447 gschem/src/x_attribedit.c:141
+#: gschem/src/o_picture.c:445 gschem/src/x_attribedit.c:141
#, c-format
msgid "ERROR: NULL object!\n"
msgstr "FOUT: NULL object!\n"
@@ -864,33 +850,46 @@ msgstr "Slots niet toegestaan voor deze component\n"
msgid "New slot number out of range\n"
msgstr "Nieuw slotnummer buiten het bereik\n"
-#: gschem/src/o_undo.c:304
+#: gschem/src/o_undo.c:303
msgid "Undo/Redo disabled in rc file\n"
msgstr "Ongedaan/Opnieuw doen uitgeschakeld in rc bestand\n"
-#: gschem/src/parsecmd.c:47
+#: gschem/src/parsecmd.c:81
#, c-format
msgid ""
-"Usage: %s [OPTIONS] schematic_filename1 ... schematic_filenameN\n"
-" -q Quiet mode\n"
-" -v Verbose mode on\n"
-" -r filename Rc filename\n"
-" -s filename Script (guile) filename\n"
-" -o filename Output filename (for printing)\n"
-" -p Automatically place the window\n"
-" -t Print stroke information\n"
-" -h Help; this message\n"
+"Usage: %s [OPTION ...] [--] [FILE ...]\n"
"\n"
-msgstr ""
-"Gebruik: %s [OPTIES] schema_bestandnaam1 ... schema_bestandnaamN\n"
-" -q Stille mode\n"
-" -v Breedsprakige modus aan\n"
-" -r filename Rc bestandnaam\n"
-" -s filename Script (guile) bestandnaam\n"
-" -o filename Uitvoer bestandnaam (voor afdrukken)\n"
-" -t Afdrukken stroke informatie\n"
-" -h Help; deze mededeling\n"
+"Interactively edit gEDA schematics or symbols. If one or more FILEs\n"
+"are specified, open them for editing; otherwise, create a new, empty\n"
+"schematic.\n"
"\n"
+"Options:\n"
+" -q, --quiet Quiet mode.\n"
+" -v, --verbose Verbose mode.\n"
+" -r, --config-file=FILE Additional configuration file to load.\n"
+" -L DIR Add DIR to Scheme search path.\n"
+" -c EXPR Scheme expression to run at startup.\n"
+" -s FILE Scheme script to run at startup.\n"
+" -o, --output=FILE Output filename (for printing).\n"
+" -p Automatically place the window.\n"
+" -V, --version Show version information.\n"
+" -h, --help Help; this message.\n"
+" -- Treat all remaining arguments as filenames.\n"
+"\n"
+"Report bugs to <geda-bug@xxxxxxxx>\n"
+"gEDA/gaf homepage: <http://gpleda.org>\n"
+msgstr ""
+
+#: gschem/src/parsecmd.c:115
+#, c-format
+msgid ""
+"gEDA %s (g%.7s)\n"
+"Copyright (C) 1998-2011 gEDA developers\n"
+"This is free software, and you are welcome to redistribute it under\n"
+"certain conditions. For details, see the file `COPYING', which is\n"
+"included in the gEDA distribution.\n"
+"There is NO WARRANTY, to the extent permitted by law.\n"
+msgstr ""
#: gschem/src/x_attribedit.c:127
#, c-format
@@ -901,56 +900,56 @@ msgstr "Kreeg ongeldige toon optie; standaardwaarde is toon beide\n"
msgid "Single Attribute Editor"
msgstr "Enkelvoudige Attribuut Bewerking"
-#: gschem/src/x_attribedit.c:358
+#: gschem/src/x_attribedit.c:359
msgid "<b>Edit Attribute</b>"
msgstr "<b>Bewerk Attribuut</b>"
-#: gschem/src/x_attribedit.c:360
+#: gschem/src/x_attribedit.c:361
msgid "<b>Add Attribute</b>"
msgstr "<b>Plaats Attribuut</b>"
-#: gschem/src/x_attribedit.c:376 gschem/src/x_multiattrib.c:1916
+#: gschem/src/x_attribedit.c:377 gschem/src/x_multiattrib.c:1927
msgid "Name:"
msgstr "Naam:"
-#: gschem/src/x_attribedit.c:393 gschem/src/x_multiattrib.c:1935
+#: gschem/src/x_attribedit.c:394 gschem/src/x_multiattrib.c:1946
msgid "Value:"
msgstr "Waarde:"
-#: gschem/src/x_attribedit.c:409 gschem/src/x_multiattrib.c:1978
+#: gschem/src/x_attribedit.c:410 gschem/src/x_multiattrib.c:1989
msgid "Visible"
msgstr "Zichtbaar"
-#: gschem/src/x_attribedit.c:429
+#: gschem/src/x_attribedit.c:430
msgid "Show Value Only"
msgstr "Toon Alleen Waarde"
-#: gschem/src/x_attribedit.c:431
+#: gschem/src/x_attribedit.c:432
msgid "Show Name Only"
msgstr "Toon Alleen Naam"
-#: gschem/src/x_attribedit.c:433 gschem/src/x_multiattrib.c:1454
+#: gschem/src/x_attribedit.c:434 gschem/src/x_multiattrib.c:1466
msgid "Show Name & Value"
msgstr "Toon Naam & Waarde"
-#: gschem/src/x_attribedit.c:440
+#: gschem/src/x_attribedit.c:441
msgid "<b>Attach Options</b>"
msgstr "<b>Opties Vastmaken</b>"
-#: gschem/src/x_attribedit.c:455
+#: gschem/src/x_attribedit.c:456
msgid "All"
msgstr "Alle"
-#: gschem/src/x_attribedit.c:463 gschem/src/x_compselect.c:896
-#: gschem/src/x_compselect.c:1010
+#: gschem/src/x_attribedit.c:464 gschem/src/x_compselect.c:904
+#: gschem/src/x_compselect.c:1018
msgid "Components"
msgstr "Componenten"
-#: gschem/src/x_attribedit.c:471 gschem/src/x_window.c:365
+#: gschem/src/x_attribedit.c:472 gschem/src/x_window.c:365
msgid "Nets"
msgstr "Draden"
-#: gschem/src/x_attribedit.c:479
+#: gschem/src/x_attribedit.c:480
msgid "Replace existing attributes"
msgstr "Vervang bestaande attributen"
@@ -969,92 +968,92 @@ msgid ""
msgstr ""
"een dubbel slot kan een probleem geven: [symbolname=%s, number=%d, slot=%d]\n"
-#: gschem/src/x_autonumber.c:673
+#: gschem/src/x_autonumber.c:675
msgid "No searchstring given in autonumber text.\n"
msgstr "Geen zoektekst gegeven in automatisch nummeren tekst.\n"
-#: gschem/src/x_autonumber.c:725
+#: gschem/src/x_autonumber.c:727
msgid "No '*' or '?' given at the end of the autonumber text.\n"
msgstr ""
"Geen '*' of '?' gegeven aan het einden van de automatisch nummeren tekst.\n"
-#: gschem/src/x_autonumber.c:860
+#: gschem/src/x_autonumber.c:862
msgid "Diagonal"
msgstr "Diagonaal"
-#: gschem/src/x_autonumber.c:861
+#: gschem/src/x_autonumber.c:863
msgid "Top to bottom"
msgstr "Van boven naar beneden"
-#: gschem/src/x_autonumber.c:861
+#: gschem/src/x_autonumber.c:863
msgid "Bottom to top"
msgstr "Van beneden naar boven"
-#: gschem/src/x_autonumber.c:862
+#: gschem/src/x_autonumber.c:864
msgid "Left to right"
msgstr "Van links naar rechts"
-#: gschem/src/x_autonumber.c:862
+#: gschem/src/x_autonumber.c:864
msgid "Right to left"
msgstr "Van rechts naar links"
-#: gschem/src/x_autonumber.c:863
+#: gschem/src/x_autonumber.c:865
msgid "File order"
msgstr "Bestand volgorde"
-#: gschem/src/x_autonumber.c:1199
+#: gschem/src/x_autonumber.c:1201
msgid "Autonumber text"
msgstr "Automatisch tekst nummeren"
-#: gschem/src/x_autonumber.c:1223
+#: gschem/src/x_autonumber.c:1225
msgid "<b>Scope</b>"
msgstr "<b>Omvang</b>"
-#: gschem/src/x_autonumber.c:1245
+#: gschem/src/x_autonumber.c:1247
msgid "Search for:"
msgstr "Zoek naar:"
-#: gschem/src/x_autonumber.c:1259
+#: gschem/src/x_autonumber.c:1261
msgid "Autonumber text in:"
msgstr "Automatisch tekst nummeren in:"
-#: gschem/src/x_autonumber.c:1266
+#: gschem/src/x_autonumber.c:1268
msgid "Skip numbers found in:"
msgstr "Sla nummers over gevonden in:"
-#: gschem/src/x_autonumber.c:1278 gschem/src/x_autonumber.c:1287
+#: gschem/src/x_autonumber.c:1280 gschem/src/x_autonumber.c:1289
msgid "Selected objects"
msgstr "Geselecteerde objecten"
-#: gschem/src/x_autonumber.c:1279 gschem/src/x_autonumber.c:1288
+#: gschem/src/x_autonumber.c:1281 gschem/src/x_autonumber.c:1290
msgid "Current page"
msgstr "Huidig blad"
-#: gschem/src/x_autonumber.c:1280 gschem/src/x_autonumber.c:1289
+#: gschem/src/x_autonumber.c:1282 gschem/src/x_autonumber.c:1291
msgid "Whole hierarchy"
msgstr "Hele hierarchie"
-#: gschem/src/x_autonumber.c:1291
+#: gschem/src/x_autonumber.c:1293
msgid "Overwrite existing numbers"
msgstr "Overschrijven van bestaande nummers"
-#: gschem/src/x_autonumber.c:1296
+#: gschem/src/x_autonumber.c:1298
msgid "<b>Options</b>"
msgstr "<b>Opties</b>"
-#: gschem/src/x_autonumber.c:1318
+#: gschem/src/x_autonumber.c:1320
msgid "Starting number:"
msgstr "Start nummer:"
-#: gschem/src/x_autonumber.c:1325
+#: gschem/src/x_autonumber.c:1327
msgid "Sort order:"
msgstr "Sorteer volgorde:"
-#: gschem/src/x_autonumber.c:1346
+#: gschem/src/x_autonumber.c:1348
msgid "Remove numbers"
msgstr "Verwijder nummers"
-#: gschem/src/x_autonumber.c:1350
+#: gschem/src/x_autonumber.c:1352
msgid "Automatic slotting"
msgstr "Automatisch slotten"
@@ -1091,48 +1090,48 @@ msgstr "Probeerde een ongeldige kleur te verkrijgen: %d\n"
msgid "Tried to get an invalid outline color: %d\n"
msgstr "Probeerde een ongeldige omlijning kleur te verkrijgen: %d\n"
-#: gschem/src/x_compselect.c:1040
+#: gschem/src/x_compselect.c:1048
msgid "Filter:"
msgstr "Filter:"
-#: gschem/src/x_compselect.c:1143 gschem/src/x_dialog.c:3663
-#: gschem/src/x_multiattrib.c:1782
+#: gschem/src/x_compselect.c:1151 gschem/src/x_dialog.c:3667
+#: gschem/src/x_multiattrib.c:1793
msgid "Name"
msgstr "Naam"
-#: gschem/src/x_compselect.c:1152 gschem/src/x_multiattrib.c:1806
+#: gschem/src/x_compselect.c:1160 gschem/src/x_multiattrib.c:1817
msgid "Value"
msgstr "Waarde"
-#: gschem/src/x_compselect.c:1191
+#: gschem/src/x_compselect.c:1199
msgid "Default behavior - reference component"
msgstr "Normaal gedrag - referentie component"
-#: gschem/src/x_compselect.c:1194
+#: gschem/src/x_compselect.c:1202
msgid "Embed component in schematic"
msgstr "Component insluiten in schema"
-#: gschem/src/x_compselect.c:1197
+#: gschem/src/x_compselect.c:1205
msgid "Include component as individual objects"
msgstr "Invoegen component als individuele objecten"
-#: gschem/src/x_compselect.c:1354
+#: gschem/src/x_compselect.c:1362
msgid "Select Component..."
msgstr "Selecteer Component..."
-#: gschem/src/x_compselect.c:1377
+#: gschem/src/x_compselect.c:1385
msgid "In Use"
msgstr "In gebruik"
-#: gschem/src/x_compselect.c:1381
+#: gschem/src/x_compselect.c:1389
msgid "Libraries"
msgstr "Bibliotheken"
-#: gschem/src/x_compselect.c:1390 gschem/src/x_fileselect.c:122
+#: gschem/src/x_compselect.c:1398 gschem/src/x_fileselect.c:122
msgid "Preview"
msgstr "Vooraf zien"
-#: gschem/src/x_compselect.c:1418
+#: gschem/src/x_compselect.c:1426
msgid "Attributes"
msgstr "Attributen"
@@ -1190,139 +1189,139 @@ msgstr "Onder Rechts"
msgid "Edit Text Properties"
msgstr "Bewerk Tekst Eigenschappen"
-#: gschem/src/x_dialog.c:471
+#: gschem/src/x_dialog.c:472
msgid "<b>Text Content</b>"
msgstr "<b>Tekst Inhoud</b>"
-#: gschem/src/x_dialog.c:507
+#: gschem/src/x_dialog.c:508
msgid "<b>Text Properties</b>"
msgstr "<b>Tekst Eigenschappen</b>"
-#: gschem/src/x_dialog.c:522
+#: gschem/src/x_dialog.c:523
msgid "Color:"
msgstr "Kleur:"
-#: gschem/src/x_dialog.c:529
+#: gschem/src/x_dialog.c:530
msgid "Size:"
msgstr "Grootte:"
-#: gschem/src/x_dialog.c:538
+#: gschem/src/x_dialog.c:539
msgid "Alignment:"
msgstr "Uitlijning:"
-#: gschem/src/x_dialog.c:587
+#: gschem/src/x_dialog.c:588
msgid "Solid"
msgstr "Getrokken lijn"
-#: gschem/src/x_dialog.c:588
+#: gschem/src/x_dialog.c:589
msgid "Dotted"
msgstr "Gestippeld"
-#: gschem/src/x_dialog.c:589
+#: gschem/src/x_dialog.c:590
msgid "Dashed"
msgstr "Gestreept"
-#: gschem/src/x_dialog.c:590
+#: gschem/src/x_dialog.c:591
msgid "Center"
msgstr "Hart"
-#: gschem/src/x_dialog.c:591
+#: gschem/src/x_dialog.c:592
msgid "Phantom"
msgstr "Begrenzing"
-#: gschem/src/x_dialog.c:592 gschem/src/x_dialog.c:689
-#: gschem/src/x_dialog.c:698 gschem/src/x_dialog.c:707
-#: gschem/src/x_dialog.c:808 gschem/src/x_dialog.c:810
-#: gschem/src/x_dialog.c:812 gschem/src/x_dialog.c:1038
-#: gschem/src/x_dialog.c:1141 gschem/src/x_dialog.c:1150
-#: gschem/src/x_dialog.c:1159 gschem/src/x_dialog.c:1168
-#: gschem/src/x_dialog.c:1177 gschem/src/x_dialog.c:1290
-#: gschem/src/x_dialog.c:1292 gschem/src/x_dialog.c:1294
-#: gschem/src/x_dialog.c:1296 gschem/src/x_dialog.c:1298
+#: gschem/src/x_dialog.c:593 gschem/src/x_dialog.c:690
+#: gschem/src/x_dialog.c:699 gschem/src/x_dialog.c:708
+#: gschem/src/x_dialog.c:809 gschem/src/x_dialog.c:811
+#: gschem/src/x_dialog.c:813 gschem/src/x_dialog.c:1039
+#: gschem/src/x_dialog.c:1142 gschem/src/x_dialog.c:1151
+#: gschem/src/x_dialog.c:1160 gschem/src/x_dialog.c:1169
+#: gschem/src/x_dialog.c:1178 gschem/src/x_dialog.c:1291
+#: gschem/src/x_dialog.c:1293 gschem/src/x_dialog.c:1295
+#: gschem/src/x_dialog.c:1297 gschem/src/x_dialog.c:1299
msgid "*unchanged*"
msgstr "*onveranderd*"
-#: gschem/src/x_dialog.c:916
+#: gschem/src/x_dialog.c:917
msgid "Edit Line Width & Type"
msgstr "Bewerk Lijn Dikte & Type"
-#: gschem/src/x_dialog.c:955 gschem/src/x_print.c:307
+#: gschem/src/x_dialog.c:956 gschem/src/x_print.c:307
msgid "Type:"
msgstr "Type:"
-#: gschem/src/x_dialog.c:959
+#: gschem/src/x_dialog.c:960
msgid "Width:"
msgstr "Breedte:"
-#: gschem/src/x_dialog.c:963
+#: gschem/src/x_dialog.c:964
msgid "Dash Length:"
msgstr "Lijn Streeplengte:"
-#: gschem/src/x_dialog.c:967
+#: gschem/src/x_dialog.c:968
msgid "Dash Space:"
msgstr "Lijn Tussenruimte:"
-#: gschem/src/x_dialog.c:1034
+#: gschem/src/x_dialog.c:1035
msgid "Hollow"
msgstr "Hol"
-#: gschem/src/x_dialog.c:1035
+#: gschem/src/x_dialog.c:1036
msgid "Filled"
msgstr "Gevuld"
-#: gschem/src/x_dialog.c:1036
+#: gschem/src/x_dialog.c:1037
msgid "Mesh"
msgstr "Maas"
-#: gschem/src/x_dialog.c:1037
+#: gschem/src/x_dialog.c:1038
msgid "Hatch"
msgstr "Arcering"
-#: gschem/src/x_dialog.c:1406
+#: gschem/src/x_dialog.c:1407
msgid "Edit Fill Type"
msgstr "Bewerk Arcering Type"
-#: gschem/src/x_dialog.c:1444
+#: gschem/src/x_dialog.c:1446
msgid "Fill Type:"
msgstr "Arcering Type:"
-#: gschem/src/x_dialog.c:1448
+#: gschem/src/x_dialog.c:1450
msgid "Line Width:"
msgstr "Lijn Dikte:"
-#: gschem/src/x_dialog.c:1452
+#: gschem/src/x_dialog.c:1454
msgid "Angle 1:"
msgstr "Hoek 1:"
-#: gschem/src/x_dialog.c:1456
+#: gschem/src/x_dialog.c:1458
msgid "Pitch 1:"
msgstr "Steek 1:"
-#: gschem/src/x_dialog.c:1460
+#: gschem/src/x_dialog.c:1462
msgid "Angle 2:"
msgstr "Hoek 2:"
-#: gschem/src/x_dialog.c:1464
+#: gschem/src/x_dialog.c:1466
msgid "Pitch 2:"
msgstr "Steek 2:"
-#: gschem/src/x_dialog.c:1591
+#: gschem/src/x_dialog.c:1593
msgid "Arc Params"
msgstr "Boog parameters"
-#: gschem/src/x_dialog.c:1631
+#: gschem/src/x_dialog.c:1634
msgid "Arc Radius:"
msgstr "Boog Straal:"
-#: gschem/src/x_dialog.c:1639
+#: gschem/src/x_dialog.c:1642
msgid "Start Angle:"
msgstr "Start Hoek:"
-#: gschem/src/x_dialog.c:1647
+#: gschem/src/x_dialog.c:1650
msgid "Degrees of Sweep:"
msgstr "Doorlopen Hoek:"
-#: gschem/src/x_dialog.c:1764
+#: gschem/src/x_dialog.c:1768
msgid ""
"Offset to translate?\n"
"(0 for origin)"
@@ -1330,44 +1329,44 @@ msgstr ""
"Offset van de verplaatsing?\n"
"(0 voor oorsprong)"
-#: gschem/src/x_dialog.c:1832
+#: gschem/src/x_dialog.c:1836
msgid "Text Size"
msgstr "Tekst Hoogte"
-#: gschem/src/x_dialog.c:1862
+#: gschem/src/x_dialog.c:1866
msgid "Enter new text size:"
msgstr "Voer nieuwe tekstgrootte in:"
-#: gschem/src/x_dialog.c:1938
+#: gschem/src/x_dialog.c:1942
msgid "Snap Size"
msgstr "Snap Grootte"
-#: gschem/src/x_dialog.c:1968
+#: gschem/src/x_dialog.c:1972
msgid "Enter new snap grid spacing:"
msgstr "Voer nieuwe snap raster waarde in:"
-#: gschem/src/x_dialog.c:2045
+#: gschem/src/x_dialog.c:2049
msgid "Edit slot number"
msgstr "Bewerk slot nummer"
-#: gschem/src/x_dialog.c:2076
+#: gschem/src/x_dialog.c:2080
msgid "Edit slot number:"
msgstr "Bewerk slot nummer:"
-#: gschem/src/x_dialog.c:2117
+#: gschem/src/x_dialog.c:2121
#, c-format
msgid "%s%s (%s)"
msgstr "%s%s (%s)"
-#: gschem/src/x_dialog.c:2140
+#: gschem/src/x_dialog.c:2144
msgid "About gschem"
msgstr "Over gschem"
-#: gschem/src/x_dialog.c:2141
+#: gschem/src/x_dialog.c:2145
msgid "gEDA: GPL Electronic Design Automation"
msgstr "gEDA: GPL Elektronische Ontwerp Automatisering"
-#: gschem/src/x_dialog.c:2142
+#: gschem/src/x_dialog.c:2146
msgid ""
"Copyright © 1998-2009 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
"Copyright © 1998-2009 gEDA Contributors (see ChangeLog for details)"
@@ -1376,156 +1375,156 @@ msgstr ""
"Copyright © 1998-2009 gEDA Contributors (zie het WijzigingsLogboek voor "
"details)"
-#: gschem/src/x_dialog.c:2201
+#: gschem/src/x_dialog.c:2205
msgid "Coords"
msgstr "Coord."
-#: gschem/src/x_dialog.c:2222
+#: gschem/src/x_dialog.c:2226
msgid "Screen"
msgstr "Scherm"
-#: gschem/src/x_dialog.c:2231
+#: gschem/src/x_dialog.c:2235
msgid "World"
msgstr "Wereld"
-#: gschem/src/x_dialog.c:2270
+#: gschem/src/x_dialog.c:2274
msgid "Background"
msgstr "Achtergrond"
-#: gschem/src/x_dialog.c:2276
+#: gschem/src/x_dialog.c:2280
msgid "Net endpoint"
msgstr "Draad eindpunt"
-#: gschem/src/x_dialog.c:2279
+#: gschem/src/x_dialog.c:2283
msgid "Graphic"
msgstr "Grafisch"
-#: gschem/src/x_dialog.c:2288
+#: gschem/src/x_dialog.c:2292
msgid "Logic bubble"
msgstr "Logische inverter"
-#: gschem/src/x_dialog.c:2291
+#: gschem/src/x_dialog.c:2295
msgid "Grid point"
msgstr "Rasterpunt"
-#: gschem/src/x_dialog.c:2294
+#: gschem/src/x_dialog.c:2298
msgid "Detached attribute"
msgstr "Losgemaakte attribuut"
-#: gschem/src/x_dialog.c:2297 gschem/src/x_window.c:383
+#: gschem/src/x_dialog.c:2301 gschem/src/x_window.c:383
msgid "Text"
msgstr "Tekst"
-#: gschem/src/x_dialog.c:2303
+#: gschem/src/x_dialog.c:2307
msgid "Selection"
msgstr "Selectie"
-#: gschem/src/x_dialog.c:2306
+#: gschem/src/x_dialog.c:2310
msgid "Bounding box"
msgstr "Omhullende rechthoek"
-#: gschem/src/x_dialog.c:2309
+#: gschem/src/x_dialog.c:2313
msgid "Zoom box"
msgstr "Vergroot venster"
-#: gschem/src/x_dialog.c:2318
+#: gschem/src/x_dialog.c:2322
msgid "Output background"
msgstr "Uitvoer achtergrond"
-#: gschem/src/x_dialog.c:2321
+#: gschem/src/x_dialog.c:2325
msgid "Net junction"
msgstr "Draad aftakking"
-#: gschem/src/x_dialog.c:2324
+#: gschem/src/x_dialog.c:2328
msgid "Mesh grid major"
msgstr "Maas raster groot"
-#: gschem/src/x_dialog.c:2327
+#: gschem/src/x_dialog.c:2331
msgid "Mesh grid minor"
msgstr "Maas raster klein"
-#: gschem/src/x_dialog.c:2330
+#: gschem/src/x_dialog.c:2334
msgid "Unknown"
msgstr "Onbekend"
-#: gschem/src/x_dialog.c:2481
+#: gschem/src/x_dialog.c:2485
#, c-format
msgid "ERROR: NULL object in color_edit_dialog_apply!\n"
msgstr "FOUT: NULL object in color_edit_dialog_apply!\n"
-#: gschem/src/x_dialog.c:2525
+#: gschem/src/x_dialog.c:2529
msgid "Color Edit"
msgstr "Kleur Bewerken"
-#: gschem/src/x_dialog.c:2556
+#: gschem/src/x_dialog.c:2560
msgid "Object color:"
msgstr "Object kleur:"
-#: gschem/src/x_dialog.c:2614
+#: gschem/src/x_dialog.c:2618
msgid "Hotkeys"
msgstr "Sneltoets"
-#: gschem/src/x_dialog.c:2678
+#: gschem/src/x_dialog.c:2682
msgid "Function"
msgstr "Funktie"
-#: gschem/src/x_dialog.c:2685
+#: gschem/src/x_dialog.c:2689
msgid "Keystroke(s)"
msgstr "Toetsaanslag(en)"
-#: gschem/src/x_dialog.c:2991
+#: gschem/src/x_dialog.c:2995
msgid "Find Text"
msgstr "Vind tekst"
-#: gschem/src/x_dialog.c:3022
+#: gschem/src/x_dialog.c:3026
msgid "Text to find:"
msgstr "Te vinden tekst:"
-#: gschem/src/x_dialog.c:3032
+#: gschem/src/x_dialog.c:3036
msgid "descend into hierarchy"
msgstr "afdalen in hierarchie"
-#: gschem/src/x_dialog.c:3097
+#: gschem/src/x_dialog.c:3101
msgid "Hide Text"
msgstr "Verberg tekst"
-#: gschem/src/x_dialog.c:3128
+#: gschem/src/x_dialog.c:3132
msgid "Hide text starting with:"
msgstr "Verberg tekst beginnend met:"
-#: gschem/src/x_dialog.c:3197
+#: gschem/src/x_dialog.c:3201
msgid "Show Text"
msgstr "Toon tekst"
-#: gschem/src/x_dialog.c:3228
+#: gschem/src/x_dialog.c:3232
msgid "Show text starting with:"
msgstr "Toon tekst beginnend met:"
-#: gschem/src/x_dialog.c:3685
+#: gschem/src/x_dialog.c:3689
msgid "S_elect the schematics you want to save:"
msgstr "S_electeer de schema's die je op wil slaan:"
-#: gschem/src/x_dialog.c:3779
+#: gschem/src/x_dialog.c:3784
#, c-format
msgid "Save the changes to schematic \"%s\" before closing?"
msgstr "Wijzigingen in schema \"%s\" opslaan voor het afsluiten?"
-#: gschem/src/x_dialog.c:3785
+#: gschem/src/x_dialog.c:3790
#, c-format
msgid ""
"There are %d schematics with unsaved changes. Save changes before closing?"
msgstr ""
"Er zijn %d schema's met wijzigingen. Wijzigingen opslaan voor het afsluiten?"
-#: gschem/src/x_dialog.c:3814
+#: gschem/src/x_dialog.c:3819
msgid "If you don't save, all your changes will be permanently lost."
msgstr "Als je niet opslaat, verlies je alle wijzigingen definitief."
-#: gschem/src/x_dialog.c:3834
+#: gschem/src/x_dialog.c:3839
msgid "_Close without saving"
msgstr "_Afsluiten zonder opslaan"
-#: gschem/src/x_dialog.c:4170
+#: gschem/src/x_dialog.c:4175
#, c-format
msgid ""
"<span weight=\"bold\" size=\"larger\">The input attribute \"%s\" is invalid\n"
@@ -1543,19 +1542,19 @@ msgstr ""
"De naam mag niet eindigen met een spatie.\n"
"De waarde mag niet met een spatie beginnen."
-#: gschem/src/x_dialog.c:4172
+#: gschem/src/x_dialog.c:4177
msgid "Invalid Attribute"
msgstr "Ongeldig Attribuut"
-#: gschem/src/x_dialog.c:4208
+#: gschem/src/x_dialog.c:4213
msgid "Pin type"
msgstr "Pen type"
-#: gschem/src/x_dialog.c:4232
+#: gschem/src/x_dialog.c:4237
msgid "Net pin"
msgstr "Draad pen"
-#: gschem/src/x_dialog.c:4234
+#: gschem/src/x_dialog.c:4239
msgid "Bus pin (graphical)"
msgstr "Bus pen (grafisch)"
@@ -1656,11 +1655,11 @@ msgstr "Afbeelding type"
msgid "Write image..."
msgstr "Schrijf afbeelding..."
-#: gschem/src/x_log.c:188
+#: gschem/src/x_log.c:209
msgid "** Invalid UTF-8 in log message. See stderr or gschem.log.\n"
msgstr "** Ongeldige UTF-8 in logboek bericht. Zie stderr of gschem.log.\n"
-#: gschem/src/x_log.c:256
+#: gschem/src/x_log.c:288
msgid "Status"
msgstr "Status"
@@ -1736,73 +1735,64 @@ msgstr "/Naar Symbool"
msgid "/Up"
msgstr "/Omhoog"
-#: gschem/src/x_menus.c:321
+#: gschem/src/x_menus.c:323
#, c-format
msgid "Tried to set the sensitivity on non-existent menu item '%s'\n"
msgstr ""
"Probeerde de gevoeligheid in te stellen op een niet bestaand menu_item '%s'\n"
-#: gschem/src/x_menus.c:345
+#: gschem/src/x_menus.c:347
msgid "Popup_menu_item_factory doesn't exist!\n"
msgstr "Popup_menu_item_factory bestaat niet!\n"
-#: gschem/src/x_menus.c:358
+#: gschem/src/x_menus.c:360
msgid "Tried to set the sensitivity on a non-existent popup menu_item\n"
msgstr ""
"Probeerde de gevoeligheid in te stellen op een niet bestaand popup "
"menu_item\n"
-#: gschem/src/x_menus.c:438
-#, c-format
-msgid "Couldn't open file %s\n"
-msgstr "Kan bestand %s niet openen\n"
-
-#: gschem/src/x_menus.c:495
-msgid "Clear"
-msgstr "Wis"
-
-#: gschem/src/x_multiattrib.c:911
+#: gschem/src/x_multiattrib.c:915
msgid "Attributes with empty name are not allowed. Please set a name."
msgstr "Attributen met een lege naam zijn niet toegestaan. Geef een naam."
-#: gschem/src/x_multiattrib.c:1456
+#: gschem/src/x_multiattrib.c:1468
msgid "Show Value only"
msgstr "Toon alleen Waarde"
-#: gschem/src/x_multiattrib.c:1458
+#: gschem/src/x_multiattrib.c:1470
msgid "Show Name only"
msgstr "Toon alleen Naam"
-#: gschem/src/x_multiattrib.c:1486
+#: gschem/src/x_multiattrib.c:1498
msgid "Promote"
msgstr "Promoot"
-#: gschem/src/x_multiattrib.c:1490
+#: gschem/src/x_multiattrib.c:1502
msgid "Duplicate"
msgstr "Dupliceer"
-#: gschem/src/x_multiattrib.c:1708
+#: gschem/src/x_multiattrib.c:1719
msgid "Edit Attributes"
msgstr "Bewerk Attribuut"
-#: gschem/src/x_multiattrib.c:1826
+#: gschem/src/x_multiattrib.c:1837
msgid "Vis?"
msgstr "Zichtbaar?"
-#: gschem/src/x_multiattrib.c:1844
+#: gschem/src/x_multiattrib.c:1855
msgid "N"
msgstr "N"
# GtkTreeViewColumn
-#: gschem/src/x_multiattrib.c:1862
+#: gschem/src/x_multiattrib.c:1873
msgid "V"
msgstr "W"
-#: gschem/src/x_multiattrib.c:1884
+#: gschem/src/x_multiattrib.c:1895
msgid "Show inherited attributes"
msgstr "Toon geerfde attributen"
-#: gschem/src/x_multiattrib.c:1900
+#: gschem/src/x_multiattrib.c:1911
msgid "Add Attribute"
msgstr "Plaats Attribuut"
@@ -1826,23 +1816,23 @@ msgstr "Sluit Pagina"
msgid "Discard Page"
msgstr "Pagina Wegdoen"
-#: gschem/src/x_pagesel.c:376
+#: gschem/src/x_pagesel.c:375
msgid "Page Manager"
msgstr "Pagina Manager"
-#: gschem/src/x_pagesel.c:432
+#: gschem/src/x_pagesel.c:431
msgid "Filename"
msgstr "Bestandsnaam"
-#: gschem/src/x_pagesel.c:448
+#: gschem/src/x_pagesel.c:447
msgid "Changed"
msgstr "Veranderd"
-#: gschem/src/x_pagesel.c:468
+#: gschem/src/x_pagesel.c:467
msgid "Right click on the filename for more options..."
msgstr "Klik met rechts op de bestandnaam voor meer opties..."
-#: gschem/src/x_preview.c:234
+#: gschem/src/x_preview.c:233
msgid "Preview Buffer"
msgstr "Vooraf zien Buffer"
@@ -1898,16 +1888,16 @@ msgstr "Bestand:"
msgid "Command:"
msgstr "Opdracht:"
-#: gschem/src/x_print.c:741
+#: gschem/src/x_print.c:745
msgid "No print destination specified\n"
msgstr "Geen afdruk bestemming opgegeven\n"
-#: gschem/src/x_print.c:748
+#: gschem/src/x_print.c:752
#, c-format
msgid "Cannot print current schematic to [%s]\n"
msgstr "Kan huidige schema niet afdrukken op [%s]\n"
-#: gschem/src/x_print.c:757
+#: gschem/src/x_print.c:761
#, c-format
msgid ""
"Error printing to file '%s'\n"
@@ -1916,7 +1906,7 @@ msgstr ""
"Fout bij afdrukken naar bestand '%s'\n"
"Controleer het log venster voor meer informatie"
-#: gschem/src/x_print.c:764
+#: gschem/src/x_print.c:768
#, c-format
msgid "Printed current schematic to [%s]\n"
msgstr "Huidig schema afgedrukt op [%s]\n"
@@ -1925,6 +1915,11 @@ msgstr "Huidig schema afgedrukt op [%s]\n"
msgid "Execute Script..."
msgstr "Script Uitvoeren..."
+#: gschem/src/x_script.c:66
+#, c-format
+msgid "Executing guile script [%s]\n"
+msgstr "Bezig met uitvoeren van guile script [%s]\n"
+
#: gschem/src/x_window.c:81
#, c-format
msgid "Couldn't allocate gc\n"
@@ -2040,35 +2035,35 @@ msgstr "Fout bij het lezen van bestand"
msgid "New file [%s]\n"
msgstr "Nieuw bestand [%s]\n"
-#: gschem/src/x_window.c:857
+#: gschem/src/x_window.c:855
#, c-format
msgid "Could NOT save page [%s]\n"
msgstr "Pagina [%s] kan NIET opgeslagen worden\n"
-#: gschem/src/x_window.c:858
+#: gschem/src/x_window.c:856
msgid "Error while trying to save"
msgstr "Fout tijdens het opslaan"
-#: gschem/src/x_window.c:867
+#: gschem/src/x_window.c:865
#, c-format
msgid "Saved as [%s]\n"
msgstr "Opgeslagen Als [%s]\n"
-#: gschem/src/x_window.c:869
+#: gschem/src/x_window.c:867
#, c-format
msgid "Saved [%s]\n"
msgstr "Opgeslagen [%s]\n"
-#: gschem/src/x_window.c:871
+#: gschem/src/x_window.c:869
msgid "Saved"
msgstr "Opgeslagen"
-#: gschem/src/x_window.c:945
+#: gschem/src/x_window.c:943
#, c-format
msgid "Discarding page [%s]\n"
msgstr "Pagina [%s] wegdoen\n"
-#: gschem/src/x_window.c:945
+#: gschem/src/x_window.c:943
#, c-format
msgid "Closing [%s]\n"
msgstr "Sluiten [%s]\n"
@@ -2109,7 +2104,7 @@ msgstr "Opslaan _Als..."
msgid "Save All"
msgstr "Alles Opslaan"
-#: gschem/lib/system-gschemrc.scm:1386 gschem/lib/system-gschemrc.scm:1477
+#: gschem/lib/system-gschemrc.scm:1386 gschem/lib/system-gschemrc.scm:1478
msgid "_Revert"
msgstr "Te_rughalen"
@@ -2121,7 +2116,7 @@ msgstr "Af_drukken..."
msgid "Write _image..."
msgstr "Schrijf afbeeld_ing..."
-#: gschem/lib/system-gschemrc.scm:1393 gschem/lib/system-gschemrc.scm:1478
+#: gschem/lib/system-gschemrc.scm:1393 gschem/lib/system-gschemrc.scm:1479
msgid "_Close"
msgstr "S_luit"
@@ -2153,391 +2148,434 @@ msgstr "_Plak"
msgid "_Delete"
msgstr "Verwij_der"
-#: gschem/lib/system-gschemrc.scm:1412
+#: gschem/lib/system-gschemrc.scm:1409
+#, fuzzy
+msgid "Select All"
+msgstr "Selecteer"
+
+#: gschem/lib/system-gschemrc.scm:1410
+#, fuzzy
+msgid "Deselect"
+msgstr "Selecteer"
+
+#: gschem/lib/system-gschemrc.scm:1414
msgid "Rotate 90 Mode"
msgstr "Rotatie 90 Mode"
-#: gschem/lib/system-gschemrc.scm:1415
+#: gschem/lib/system-gschemrc.scm:1417
msgid "Edit..."
msgstr "Bewerk..."
-#: gschem/lib/system-gschemrc.scm:1416
+#: gschem/lib/system-gschemrc.scm:1418
msgid "Edit Text..."
msgstr "Bewerk Tekst..."
-#: gschem/lib/system-gschemrc.scm:1417
+#: gschem/lib/system-gschemrc.scm:1419
msgid "Slot..."
msgstr "Slot..."
-#: gschem/lib/system-gschemrc.scm:1418
+#: gschem/lib/system-gschemrc.scm:1420
msgid "Color..."
msgstr "Kleur..."
-#: gschem/lib/system-gschemrc.scm:1419
+#: gschem/lib/system-gschemrc.scm:1421
msgid "Line Width & Type..."
msgstr "Lijn Dikte & Type..."
-#: gschem/lib/system-gschemrc.scm:1420
+#: gschem/lib/system-gschemrc.scm:1422
msgid "Fill Type..."
msgstr "Arcering Type..."
-#: gschem/lib/system-gschemrc.scm:1421
+#: gschem/lib/system-gschemrc.scm:1423
msgid "Symbol Translate..."
msgstr "Verplaats Symbool..."
-#: gschem/lib/system-gschemrc.scm:1425
+#: gschem/lib/system-gschemrc.scm:1427
msgid "Invoke Macro"
msgstr "Macro Aanroepen"
-#: gschem/lib/system-gschemrc.scm:1426
+#: gschem/lib/system-gschemrc.scm:1428
msgid "Embed Component/Picture"
msgstr "Component/Afbeelding Insluiten"
-#: gschem/lib/system-gschemrc.scm:1427
+#: gschem/lib/system-gschemrc.scm:1429
msgid "Unembed Component/Picture"
msgstr "Component/Afbeelding Uitsluiten"
-#: gschem/lib/system-gschemrc.scm:1428
+#: gschem/lib/system-gschemrc.scm:1430
msgid "Update Component"
msgstr "Hernieuw Component"
-#: gschem/lib/system-gschemrc.scm:1429
+#: gschem/lib/system-gschemrc.scm:1431
msgid "Show/Hide Inv Text"
msgstr "Zichtbaar/Verborgen Onzichtbare Tekst"
-#: gschem/lib/system-gschemrc.scm:1430
-msgid "Make Inv Text Vis"
-msgstr "Maak Onzichtbare Tekst Zichtbaar"
-
-#: gschem/lib/system-gschemrc.scm:1436
+#: gschem/lib/system-gschemrc.scm:1437
msgid "Copy into 1"
msgstr "Kopieer naar 1"
-#: gschem/lib/system-gschemrc.scm:1437
+#: gschem/lib/system-gschemrc.scm:1438
msgid "Copy into 2"
msgstr "Kopieer naar 2"
-#: gschem/lib/system-gschemrc.scm:1438
+#: gschem/lib/system-gschemrc.scm:1439
msgid "Copy into 3"
msgstr "Kopieer naar 3"
-#: gschem/lib/system-gschemrc.scm:1439
+#: gschem/lib/system-gschemrc.scm:1440
msgid "Copy into 4"
msgstr "Kopieer naar 4"
-#: gschem/lib/system-gschemrc.scm:1440
+#: gschem/lib/system-gschemrc.scm:1441
msgid "Copy into 5"
msgstr "Kopieer naar 5"
-#: gschem/lib/system-gschemrc.scm:1441
+#: gschem/lib/system-gschemrc.scm:1442
msgid "Cut into 1"
msgstr "Knip naar 1"
-#: gschem/lib/system-gschemrc.scm:1442
+#: gschem/lib/system-gschemrc.scm:1443
msgid "Cut into 2"
msgstr "Knip naar 2"
-#: gschem/lib/system-gschemrc.scm:1443
+#: gschem/lib/system-gschemrc.scm:1444
msgid "Cut into 3"
msgstr "Knip naar 3"
-#: gschem/lib/system-gschemrc.scm:1444
+#: gschem/lib/system-gschemrc.scm:1445
msgid "Cut into 4"
msgstr "Knip naar 4"
-#: gschem/lib/system-gschemrc.scm:1445
+#: gschem/lib/system-gschemrc.scm:1446
msgid "Cut into 5"
msgstr "Knip naar 5"
-#: gschem/lib/system-gschemrc.scm:1446
+#: gschem/lib/system-gschemrc.scm:1447
msgid "Paste from 1"
msgstr "Plak vanuit 1"
-#: gschem/lib/system-gschemrc.scm:1447
+#: gschem/lib/system-gschemrc.scm:1448
msgid "Paste from 2"
msgstr "Plak vanuit 2"
-#: gschem/lib/system-gschemrc.scm:1448
+#: gschem/lib/system-gschemrc.scm:1449
msgid "Paste from 3"
msgstr "Plak vanuit 3"
-#: gschem/lib/system-gschemrc.scm:1449
+#: gschem/lib/system-gschemrc.scm:1450
msgid "Paste from 4"
msgstr "Plak vanuit 4"
-#: gschem/lib/system-gschemrc.scm:1450
+#: gschem/lib/system-gschemrc.scm:1451
msgid "Paste from 5"
msgstr "Plak vanuit 5"
-#: gschem/lib/system-gschemrc.scm:1456
+#: gschem/lib/system-gschemrc.scm:1457
msgid "_Redraw"
msgstr "He_rtekenen"
-#: gschem/lib/system-gschemrc.scm:1457
+#: gschem/lib/system-gschemrc.scm:1458
msgid "_Pan"
msgstr "_Schuif"
-#: gschem/lib/system-gschemrc.scm:1458
+#: gschem/lib/system-gschemrc.scm:1459
msgid "Zoom _Box"
msgstr "_Vergroot Venster"
-#: gschem/lib/system-gschemrc.scm:1459
+#: gschem/lib/system-gschemrc.scm:1460
msgid "Zoom _Extents"
msgstr "Toon All_es"
-#: gschem/lib/system-gschemrc.scm:1460
+#: gschem/lib/system-gschemrc.scm:1461
msgid "Zoom _In"
msgstr "Ver_groot"
-#: gschem/lib/system-gschemrc.scm:1461
+#: gschem/lib/system-gschemrc.scm:1462
msgid "Zoom _Out"
msgstr "Ver_klein"
-#: gschem/lib/system-gschemrc.scm:1462
+#: gschem/lib/system-gschemrc.scm:1463
msgid "Zoom _Full"
msgstr "Toon _Maximaal"
-#: gschem/lib/system-gschemrc.scm:1464
+#: gschem/lib/system-gschemrc.scm:1465
msgid "_Dark color scheme"
msgstr "_Donker kleuren schema"
-#: gschem/lib/system-gschemrc.scm:1465
+#: gschem/lib/system-gschemrc.scm:1466
msgid "_Light color scheme"
msgstr "_Licht kleuren schema"
-#: gschem/lib/system-gschemrc.scm:1466
+#: gschem/lib/system-gschemrc.scm:1467
#, fuzzy
msgid "B_W color scheme"
msgstr "_Donker kleuren schema"
-#: gschem/lib/system-gschemrc.scm:1473
+#: gschem/lib/system-gschemrc.scm:1474
msgid "_Manager..."
msgstr "_Manager..."
-#: gschem/lib/system-gschemrc.scm:1474
+#: gschem/lib/system-gschemrc.scm:1475
msgid "_Previous"
msgstr "_Vorige"
-#: gschem/lib/system-gschemrc.scm:1475
+#: gschem/lib/system-gschemrc.scm:1476
msgid "_Next"
msgstr "Volge_nde"
-#: gschem/lib/system-gschemrc.scm:1476
+#: gschem/lib/system-gschemrc.scm:1477
msgid "Ne_w"
msgstr "Nieu_w"
-#: gschem/lib/system-gschemrc.scm:1480
+#: gschem/lib/system-gschemrc.scm:1481
msgid "_Discard"
msgstr "Weg_doen"
-#: gschem/lib/system-gschemrc.scm:1486
+#: gschem/lib/system-gschemrc.scm:1487
msgid "_Component..."
msgstr "_Component..."
-#: gschem/lib/system-gschemrc.scm:1487
+#: gschem/lib/system-gschemrc.scm:1488
msgid "_Net"
msgstr "_Draad"
-#: gschem/lib/system-gschemrc.scm:1488
+#: gschem/lib/system-gschemrc.scm:1489
msgid "B_us"
msgstr "B_us"
-#: gschem/lib/system-gschemrc.scm:1489
+#: gschem/lib/system-gschemrc.scm:1490
msgid "_Attribute..."
msgstr "_Attribuut..."
-#: gschem/lib/system-gschemrc.scm:1490
+#: gschem/lib/system-gschemrc.scm:1491
msgid "_Text..."
msgstr "_Tekst..."
-#: gschem/lib/system-gschemrc.scm:1492
+#: gschem/lib/system-gschemrc.scm:1493
msgid "_Line"
msgstr "_Lijn"
-#: gschem/lib/system-gschemrc.scm:1493
+#: gschem/lib/system-gschemrc.scm:1494
msgid "_Box"
msgstr "_Rechthoek"
-#: gschem/lib/system-gschemrc.scm:1494
+#: gschem/lib/system-gschemrc.scm:1495
msgid "C_ircle"
msgstr "C_irkel"
-#: gschem/lib/system-gschemrc.scm:1495
+#: gschem/lib/system-gschemrc.scm:1496
msgid "A_rc"
msgstr "_Boog"
-#: gschem/lib/system-gschemrc.scm:1496
+#: gschem/lib/system-gschemrc.scm:1497
msgid "_Pin"
msgstr "_Pen"
-#: gschem/lib/system-gschemrc.scm:1497
+#: gschem/lib/system-gschemrc.scm:1498
msgid "Pictu_re..."
msgstr "A_fbeelding..."
-#: gschem/lib/system-gschemrc.scm:1503
+#: gschem/lib/system-gschemrc.scm:1504
msgid "_Down Schematic"
msgstr "_Naar Schema"
-#: gschem/lib/system-gschemrc.scm:1504
+#: gschem/lib/system-gschemrc.scm:1505
msgid "Down _Symbol"
msgstr "Naar _Symbool"
-#: gschem/lib/system-gschemrc.scm:1505
+#: gschem/lib/system-gschemrc.scm:1506
msgid "_Up"
msgstr "O_mhoog"
-#: gschem/lib/system-gschemrc.scm:1506
+#: gschem/lib/system-gschemrc.scm:1507
msgid "D_ocumentation..."
msgstr "D_ocumentatie..."
-#: gschem/lib/system-gschemrc.scm:1512
+#: gschem/lib/system-gschemrc.scm:1513
msgid "_Attach"
msgstr "V_astmaken"
-#: gschem/lib/system-gschemrc.scm:1513
+#: gschem/lib/system-gschemrc.scm:1514
msgid "_Detach"
msgstr "_Losmaken"
-#: gschem/lib/system-gschemrc.scm:1514
+#: gschem/lib/system-gschemrc.scm:1515
msgid "Show _Value"
msgstr "Toon _Waarde"
-#: gschem/lib/system-gschemrc.scm:1515
+#: gschem/lib/system-gschemrc.scm:1516
msgid "Show _Name"
msgstr "Toon _Naam"
-#: gschem/lib/system-gschemrc.scm:1516
+#: gschem/lib/system-gschemrc.scm:1517
msgid "Show _Both"
msgstr "Toon _Beide"
-#: gschem/lib/system-gschemrc.scm:1517
+#: gschem/lib/system-gschemrc.scm:1518
msgid "_Toggle Visibility"
msgstr "Schakel Zich_tbaarheid"
-#: gschem/lib/system-gschemrc.scm:1519
+#: gschem/lib/system-gschemrc.scm:1520
msgid "_Find Specific Text..."
msgstr "Vind Speci_fieke Tekst..."
-#: gschem/lib/system-gschemrc.scm:1520
+#: gschem/lib/system-gschemrc.scm:1521
msgid "_Hide Specific Text..."
msgstr "Verberg Specifieke Tekst..."
-#: gschem/lib/system-gschemrc.scm:1521
+#: gschem/lib/system-gschemrc.scm:1522
msgid "_Show Specific Text..."
msgstr "Toon _Specifieke Tekst..."
-#: gschem/lib/system-gschemrc.scm:1522
+#: gschem/lib/system-gschemrc.scm:1523
msgid "A_utonumber Text..."
msgstr "A_utomatisch Tekst Nummeren..."
-#: gschem/lib/system-gschemrc.scm:1528
+#: gschem/lib/system-gschemrc.scm:1529
msgid "_Text Size..."
msgstr "_Tekst Hoogte..."
-#: gschem/lib/system-gschemrc.scm:1529
+#: gschem/lib/system-gschemrc.scm:1530
msgid "Cycle _grid styles"
msgstr "Schakel r_aster stijlen"
-#: gschem/lib/system-gschemrc.scm:1530
+#: gschem/lib/system-gschemrc.scm:1531
msgid "Toggle _Snap On/Off"
msgstr "Schakel _Snap Aan/Uit"
-#: gschem/lib/system-gschemrc.scm:1531
+#: gschem/lib/system-gschemrc.scm:1532
msgid "Snap Grid S_pacing..."
msgstr "Sna_p Raster Afstand..."
-#: gschem/lib/system-gschemrc.scm:1532
+#: gschem/lib/system-gschemrc.scm:1533
msgid "Scale _up Grid Spacing"
msgstr "Omhoog schalen Raster A_fstand"
-#: gschem/lib/system-gschemrc.scm:1534
+#: gschem/lib/system-gschemrc.scm:1535
msgid "Scale _down Grid Spacing"
msgstr "Omlaag schalen Snap Raster Afstan_d"
-#: gschem/lib/system-gschemrc.scm:1536
+#: gschem/lib/system-gschemrc.scm:1537
msgid "Toggle _Outline/Box"
msgstr "Schakel C_ontour/Rechthoek"
-#: gschem/lib/system-gschemrc.scm:1538
+#: gschem/lib/system-gschemrc.scm:1539
msgid "Toggle Net _Rubberband"
msgstr "Schakel D_raad Elastiekband"
-#: gschem/lib/system-gschemrc.scm:1539
+#: gschem/lib/system-gschemrc.scm:1540
msgid "Toggle _Magnetic Net"
msgstr "Schakel _Magnetische Draad Mode"
-#: gschem/lib/system-gschemrc.scm:1540
+#: gschem/lib/system-gschemrc.scm:1541
msgid "Show _Log Window..."
msgstr "Toon _Logboek venster..."
-#: gschem/lib/system-gschemrc.scm:1542
+#: gschem/lib/system-gschemrc.scm:1543
msgid "Show _Coord Window..."
msgstr "Toon _Coordinaten venster..."
-#: gschem/lib/system-gschemrc.scm:1558
+#: gschem/lib/system-gschemrc.scm:1559
msgid "gEDA Docu_mentation..."
msgstr "gEDA Docu_mentatie..."
-#: gschem/lib/system-gschemrc.scm:1559
+#: gschem/lib/system-gschemrc.scm:1560
msgid "gschem _FAQ..."
msgstr "gschem _FAQ..."
-#: gschem/lib/system-gschemrc.scm:1560
+#: gschem/lib/system-gschemrc.scm:1561
msgid "gEDA _Wiki..."
msgstr "gEDA _Wiki..."
-#: gschem/lib/system-gschemrc.scm:1561
+#: gschem/lib/system-gschemrc.scm:1562
msgid "Component D_ocumentation..."
msgstr "Component D_ocumentatie..."
-#: gschem/lib/system-gschemrc.scm:1563
+#: gschem/lib/system-gschemrc.scm:1564
msgid "_Hotkeys..."
msgstr "_Sneltoets..."
-#: gschem/lib/system-gschemrc.scm:1564
+#: gschem/lib/system-gschemrc.scm:1565
msgid "_About..."
msgstr "Om_trent..."
-#: gschem/lib/system-gschemrc.scm:1570
+#: gschem/lib/system-gschemrc.scm:1571
msgid "_File"
msgstr "_Bestand"
-#: gschem/lib/system-gschemrc.scm:1571
+#: gschem/lib/system-gschemrc.scm:1572
msgid "_Edit"
msgstr "B_ewerk"
-#: gschem/lib/system-gschemrc.scm:1572
+#: gschem/lib/system-gschemrc.scm:1573
msgid "_Buffer"
msgstr "B_uffer"
-#: gschem/lib/system-gschemrc.scm:1573
+#: gschem/lib/system-gschemrc.scm:1574
msgid "_View"
msgstr "_Toon"
-#: gschem/lib/system-gschemrc.scm:1574
+#: gschem/lib/system-gschemrc.scm:1575
msgid "_Page"
msgstr "_Pagina"
-#: gschem/lib/system-gschemrc.scm:1575
+#: gschem/lib/system-gschemrc.scm:1576
msgid "_Add"
msgstr "Toe_voegen"
-#: gschem/lib/system-gschemrc.scm:1576
+#: gschem/lib/system-gschemrc.scm:1577
msgid "Hie_rarchy"
msgstr "Hie_rarchie"
-#: gschem/lib/system-gschemrc.scm:1577
+#: gschem/lib/system-gschemrc.scm:1578
msgid "A_ttributes"
msgstr "_Attributen"
-#: gschem/lib/system-gschemrc.scm:1578
+#: gschem/lib/system-gschemrc.scm:1579
msgid "_Options"
msgstr "_Opties"
-#: gschem/lib/system-gschemrc.scm:1579
+#: gschem/lib/system-gschemrc.scm:1580
msgid "_Help"
msgstr "_Help"
+#~ msgid "Scheme directory NOT set!\n"
+#~ msgstr "Scheme bestandenmap is NIET ingesteld!\n"
+
+#~ msgid "MakeVisible"
+#~ msgstr "MaakZichtbaar"
+
+#~ msgid ""
+#~ "Usage: %s [OPTIONS] schematic_filename1 ... schematic_filenameN\n"
+#~ " -q Quiet mode\n"
+#~ " -v Verbose mode on\n"
+#~ " -r filename Rc filename\n"
+#~ " -s filename Script (guile) filename\n"
+#~ " -o filename Output filename (for printing)\n"
+#~ " -p Automatically place the window\n"
+#~ " -t Print stroke information\n"
+#~ " -h Help; this message\n"
+#~ "\n"
+#~ msgstr ""
+#~ "Gebruik: %s [OPTIES] schema_bestandnaam1 ... schema_bestandnaamN\n"
+#~ " -q Stille mode\n"
+#~ " -v Breedsprakige modus aan\n"
+#~ " -r filename Rc bestandnaam\n"
+#~ " -s filename Script (guile) bestandnaam\n"
+#~ " -o filename Uitvoer bestandnaam (voor afdrukken)\n"
+#~ " -t Afdrukken stroke informatie\n"
+#~ " -h Help; deze mededeling\n"
+#~ "\n"
+
+#~ msgid "Couldn't open file %s\n"
+#~ msgstr "Kan bestand %s niet openen\n"
+
+#~ msgid "Clear"
+#~ msgstr "Wis"
+
+#~ msgid "Make Inv Text Vis"
+#~ msgstr "Maak Onzichtbare Tekst Zichtbaar"
+
#~ msgid "Update Cues"
#~ msgstr "Vernieuw aanwijzing"
diff --git a/gschem/po/pl.po b/gschem/po/pl.po
index e31f16f..c7d713e 100644
--- a/gschem/po/pl.po
+++ b/gschem/po/pl.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2010-11-07 13:37+0000\n"
+"POT-Creation-Date: 2011-01-16 00:11-0500\n"
"PO-Revision-Date: 2010-02-12 13:16+0000\n"
"Last-Translator: Krzysztof KoÅ?ciuszkiewicz <k.kosciuszkiewicz@xxxxxxxxx>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -22,17 +22,17 @@ msgstr ""
msgid "Zoom too small! Cannot zoom further.\n"
msgstr "Zbyt maÅ?y obszar! OsiÄ?gniÄ?to maksymalny stopieÅ? powiÄ?kszenia.\n"
-#: gschem/src/g_funcs.c:339 gschem/src/i_callbacks.c:68
+#: gschem/src/g_funcs.c:347 gschem/src/i_callbacks.c:68
#, c-format
msgid "Could not fork\n"
msgstr "Utworzenie podprocesu nie powiodÅ?o siÄ?\n"
-#: gschem/src/g_funcs.c:355 gschem/src/i_callbacks.c:78
+#: gschem/src/g_funcs.c:363 gschem/src/i_callbacks.c:78
#, c-format
msgid "Could not invoke %s\n"
msgstr "Wykonanie programu '%s' nie powiodÅ?o siÄ?\n"
-#: gschem/src/g_funcs.c:361 gschem/src/i_callbacks.c:82
+#: gschem/src/g_funcs.c:369 gschem/src/i_callbacks.c:82
msgid "Documentation commands not supported under MinGW.\n"
msgstr "Polecenia wyÅ?wietlajÄ?ce dokumentacjÄ? nie sÄ? dostÄ?pne.\n"
@@ -123,12 +123,12 @@ msgstr ""
msgid "Invalid number of steps [%d] scrollpan-steps\n"
msgstr "Niepoprawna liczba kroków [%d] w funkcji scrollpan-steps\n"
-#: gschem/src/gschem.c:184
+#: gschem/src/gschem.c:188
#, c-format
msgid "gEDA/gschem version %s%s.%s\n"
msgstr "gEDA/gschem, wersja %s%s.%s\n"
-#: gschem/src/gschem.c:187
+#: gschem/src/gschem.c:191
msgid ""
"gEDA/gschem comes with ABSOLUTELY NO WARRANTY; see COPYING for more "
"details.\n"
@@ -136,13 +136,13 @@ msgstr ""
"Autorzy gEDA/gschem nie dajÄ? Å»ADNYCH gwarancji; szczegóÅ?y w pliku o nazwie "
"COPYING.\n"
-#: gschem/src/gschem.c:189
+#: gschem/src/gschem.c:193
msgid ""
"This is free software, and you are welcome to redistribute it under certain\n"
msgstr ""
"Ten program jest dostÄ?pny jako wolne oprogramowanie, można go rozprowadzaÄ?\n"
-#: gschem/src/gschem.c:191
+#: gschem/src/gschem.c:195
msgid ""
"conditions; please see the COPYING file for more details.\n"
"\n"
@@ -150,17 +150,17 @@ msgstr ""
"pod pewnymi warunkami. SzczegóÅ?y znajdujÄ? siÄ? w pliku COPYING.\n"
"\n"
-#: gschem/src/gschem.c:194
+#: gschem/src/gschem.c:198
#, c-format
msgid "This is the MINGW32 port.\n"
msgstr "Ta wersja programu zostaÅ?a skompilowana na platformÄ? MINGW32.\n"
-#: gschem/src/gschem.c:198
+#: gschem/src/gschem.c:202
#, c-format
msgid "Current locale settings: %s\n"
msgstr "BieżÄ?ce ustawienia lokalizacji: %s\n"
-#: gschem/src/gschem.c:213
+#: gschem/src/gschem.c:218
msgid ""
"You must set the GEDADATA environment variable!\n"
"\n"
@@ -168,31 +168,21 @@ msgid ""
"environment variable to point to the correct location.\n"
msgstr ""
-#: gschem/src/gschem.c:248
+#: gschem/src/gschem.c:256
#, c-format
msgid "Couldn't find init scm file [%s]\n"
msgstr "Nie znaleziono pliku inicjalizacyjnego scm [%s]\n"
-#: gschem/src/gschem.c:252
+#: gschem/src/gschem.c:260
#, c-format
msgid "Read init scm file [%s]\n"
msgstr "Wczytano plik inicjalizacji scm [%s]\n"
-#: gschem/src/gschem.c:256
+#: gschem/src/gschem.c:264
#, c-format
msgid "Failed to read init scm file [%s]\n"
msgstr "BÅ?Ä?d podczas wczytywania pliku inicjalizacji scm [%s]\n"
-#: gschem/src/gschem.c:317
-#, c-format
-msgid "Scheme directory NOT set!\n"
-msgstr "Nie podano katalogu programu Scheme!\n"
-
-#: gschem/src/gschem.c:324 gschem/src/x_script.c:66
-#, c-format
-msgid "Executing guile script [%s]\n"
-msgstr "Wykonywanie skryptu guile [%s]\n"
-
#: gschem/src/gschem_cairo.c:310
#, c-format
msgid "Unknown end for line (%d)\n"
@@ -216,11 +206,11 @@ msgstr "Tryb elementów"
msgid "Text Mode"
msgstr "Tryb tekstu"
-#: gschem/src/i_basic.c:84 gschem/lib/system-gschemrc.scm:1409
+#: gschem/src/i_basic.c:84 gschem/lib/system-gschemrc.scm:1411
msgid "Copy Mode"
msgstr "Duplikuj"
-#: gschem/src/i_basic.c:87 gschem/lib/system-gschemrc.scm:1411
+#: gschem/src/i_basic.c:87 gschem/lib/system-gschemrc.scm:1413
msgid "Move Mode"
msgstr "PrzesuÅ?"
@@ -228,7 +218,7 @@ msgstr "PrzesuÅ?"
msgid "Rotate Mode"
msgstr "Tryb obrotu"
-#: gschem/src/i_basic.c:91 gschem/lib/system-gschemrc.scm:1413
+#: gschem/src/i_basic.c:91 gschem/lib/system-gschemrc.scm:1415
msgid "Mirror Mode"
msgstr "Lustrzane odbicie"
@@ -281,22 +271,22 @@ msgstr "Tryb Å?uków"
msgid "Pin Mode"
msgstr "Tryb pinów"
-#: gschem/src/i_basic.c:135 gschem/src/i_callbacks.c:544
-#: gschem/src/i_callbacks.c:568
+#: gschem/src/i_basic.c:135 gschem/src/i_callbacks.c:576
+#: gschem/src/i_callbacks.c:600
msgid "Copy"
msgstr "Kopiuj"
-#: gschem/src/i_basic.c:137 gschem/src/i_callbacks.c:634
-#: gschem/src/i_callbacks.c:658
+#: gschem/src/i_basic.c:137 gschem/src/i_callbacks.c:666
+#: gschem/src/i_callbacks.c:690
msgid "Move"
msgstr "PrzesuÅ?"
-#: gschem/src/i_basic.c:139 gschem/src/i_callbacks.c:589
-#: gschem/src/i_callbacks.c:613
+#: gschem/src/i_basic.c:139 gschem/src/i_callbacks.c:621
+#: gschem/src/i_callbacks.c:645
msgid "Multiple Copy"
msgstr "Kopiuj wielokrotnie"
-#: gschem/src/i_basic.c:142 gschem/lib/system-gschemrc.scm:1410
+#: gschem/src/i_basic.c:142 gschem/lib/system-gschemrc.scm:1412
msgid "Multiple Copy Mode"
msgstr "Duplikuj wielokrotnie"
@@ -316,7 +306,7 @@ msgstr ""
msgid "Action"
msgstr "CzynnoÅ?Ä?"
-#: gschem/src/i_basic.c:260 gschem/src/x_dialog.c:2312
+#: gschem/src/i_basic.c:260 gschem/src/x_dialog.c:2316
#: gschem/src/x_window.c:491
msgid "Stroke"
msgstr "Gest"
@@ -347,7 +337,7 @@ msgstr "Siatka(%s, %s)"
msgid "Documentation for [%s,%s,%s,%s]\n"
msgstr "Dokumentacja dla [%s,%s,%s,%s]\n"
-#: gschem/src/i_callbacks.c:123 gschem/src/i_callbacks.c:1699
+#: gschem/src/i_callbacks.c:123 gschem/src/i_callbacks.c:1706
#, c-format
msgid "New page created [%s]\n"
msgstr "Utworzono nowy arkusz [%s]\n"
@@ -369,244 +359,240 @@ msgstr "Zapisano wszystkie dokumenty"
msgid "Closing Window\n"
msgstr "Zamykanie okna\n"
-#: gschem/src/i_callbacks.c:549 gschem/src/i_callbacks.c:594
-#: gschem/src/i_callbacks.c:639
+#: gschem/src/i_callbacks.c:581 gschem/src/i_callbacks.c:626
+#: gschem/src/i_callbacks.c:671
msgid "Select objs first"
msgstr "Wpierw wybierz obiekty"
-#: gschem/src/i_callbacks.c:678 gschem/src/x_multiattrib.c:1491
+#: gschem/src/i_callbacks.c:710 gschem/src/x_multiattrib.c:1503
msgid "Delete"
msgstr "UsuÅ?"
-#: gschem/src/i_callbacks.c:703
+#: gschem/src/i_callbacks.c:735
msgid "Edit"
msgstr "Edycja"
-#: gschem/src/i_callbacks.c:718
+#: gschem/src/i_callbacks.c:750
msgid "Edit pin type"
msgstr "Edytuj rodzaj pinu"
-#: gschem/src/i_callbacks.c:737
+#: gschem/src/i_callbacks.c:769
msgid "Edit Text"
msgstr "Edytuj tekst"
-#: gschem/src/i_callbacks.c:760
+#: gschem/src/i_callbacks.c:792
msgid "Slot"
msgstr ""
-#: gschem/src/i_callbacks.c:777
+#: gschem/src/i_callbacks.c:809
msgid "Color"
msgstr "Kolor"
-#: gschem/src/i_callbacks.c:814 gschem/src/i_callbacks.c:859
+#: gschem/src/i_callbacks.c:846 gschem/src/i_callbacks.c:891
msgid "Rotate"
msgstr "ObróÄ?"
-#: gschem/src/i_callbacks.c:882 gschem/src/i_callbacks.c:907
+#: gschem/src/i_callbacks.c:913 gschem/src/i_callbacks.c:938
msgid "Mirror"
msgstr "Lustrzane odbicie"
-#: gschem/src/i_callbacks.c:928 gschem/src/x_dialog.c:2315
-#: gschem/lib/system-gschemrc.scm:1422
+#: gschem/src/i_callbacks.c:959 gschem/src/x_dialog.c:2319
+#: gschem/lib/system-gschemrc.scm:1424
msgid "Lock"
msgstr "Zablokuj"
-#: gschem/src/i_callbacks.c:946 gschem/lib/system-gschemrc.scm:1423
+#: gschem/src/i_callbacks.c:977 gschem/lib/system-gschemrc.scm:1425
msgid "Unlock"
msgstr "Odblokuj"
-#: gschem/src/i_callbacks.c:964 gschem/src/x_dialog.c:1734
+#: gschem/src/i_callbacks.c:995 gschem/src/x_dialog.c:1737
msgid "Translate"
msgstr ""
-#: gschem/src/i_callbacks.c:967
+#: gschem/src/i_callbacks.c:998
msgid "WARNING: Do not translate with snap off!\n"
msgstr ""
-#: gschem/src/i_callbacks.c:968
+#: gschem/src/i_callbacks.c:999
msgid "WARNING: Turning snap on and continuing with translate.\n"
msgstr ""
-#: gschem/src/i_callbacks.c:975
+#: gschem/src/i_callbacks.c:1006
msgid "WARNING: Snap grid size is not equal to 100!\n"
msgstr ""
-#: gschem/src/i_callbacks.c:977
+#: gschem/src/i_callbacks.c:1008
msgid ""
"WARNING: If you are translating a symbol to the origin, the snap grid size "
"should be set to 100\n"
msgstr ""
-#: gschem/src/i_callbacks.c:1008
+#: gschem/src/i_callbacks.c:1039
msgid "Embed"
msgstr "Osadź"
-#: gschem/src/i_callbacks.c:1047
+#: gschem/src/i_callbacks.c:1078
msgid "Unembed"
msgstr "Cofnij osadzanie"
-#: gschem/src/i_callbacks.c:1089
+#: gschem/src/i_callbacks.c:1120
msgid "Update"
msgstr "Aktualizuj"
-#: gschem/src/i_callbacks.c:1136
+#: gschem/src/i_callbacks.c:1167
msgid "ShowHidden"
msgstr "WyÅ?w. ukryte"
-#: gschem/src/i_callbacks.c:1160
-msgid "MakeVisible"
-msgstr "Ustaw jako widoczne"
-
-#: gschem/src/i_callbacks.c:1466 gschem/src/i_callbacks.c:1538
+#: gschem/src/i_callbacks.c:1473 gschem/src/i_callbacks.c:1545
msgid "Pan"
msgstr "PrzesuÅ? widok"
-#: gschem/src/i_callbacks.c:1743
+#: gschem/src/i_callbacks.c:1750
msgid "Really revert page?"
msgstr "Czy na pewno przywróciÄ? arkusz?"
-#: gschem/src/i_callbacks.c:1813
+#: gschem/src/i_callbacks.c:1820
msgid "Copy to clipboard"
msgstr "Kopiuj do schowka"
-#: gschem/src/i_callbacks.c:1831
+#: gschem/src/i_callbacks.c:1838
msgid "Cut to clipboard"
msgstr "Wytnij do schowka"
-#: gschem/src/i_callbacks.c:1849
+#: gschem/src/i_callbacks.c:1856
msgid "Paste from clipboard"
msgstr "Wklej ze schowka"
-#: gschem/src/i_callbacks.c:1861 gschem/src/i_callbacks.c:2100
-#: gschem/src/i_callbacks.c:2122 gschem/src/i_callbacks.c:2144
-#: gschem/src/i_callbacks.c:2166 gschem/src/i_callbacks.c:2188
+#: gschem/src/i_callbacks.c:1868 gschem/src/i_callbacks.c:2107
+#: gschem/src/i_callbacks.c:2129 gschem/src/i_callbacks.c:2151
+#: gschem/src/i_callbacks.c:2173 gschem/src/i_callbacks.c:2195
msgid "Empty buffer"
msgstr "Schowek jest pusty"
-#: gschem/src/i_callbacks.c:1906
+#: gschem/src/i_callbacks.c:1913
msgid "Copy 1"
msgstr "Kopiuj do 1"
-#: gschem/src/i_callbacks.c:1925
+#: gschem/src/i_callbacks.c:1932
msgid "Copy 2"
msgstr "Kopiuj do 2"
-#: gschem/src/i_callbacks.c:1944
+#: gschem/src/i_callbacks.c:1951
msgid "Copy 3"
msgstr "Kopiuj do 3"
-#: gschem/src/i_callbacks.c:1963
+#: gschem/src/i_callbacks.c:1970
msgid "Copy 4"
msgstr "Kopiuj do 4"
-#: gschem/src/i_callbacks.c:1982
+#: gschem/src/i_callbacks.c:1989
msgid "Copy 5"
msgstr "Kopiuj do 5"
-#: gschem/src/i_callbacks.c:2001
+#: gschem/src/i_callbacks.c:2008
msgid "Cut 1"
msgstr "Wytnij do 1"
-#: gschem/src/i_callbacks.c:2020
+#: gschem/src/i_callbacks.c:2027
msgid "Cut 2"
msgstr "Wytnij do 2"
-#: gschem/src/i_callbacks.c:2039
+#: gschem/src/i_callbacks.c:2046
msgid "Cut 3"
msgstr "Wytnij do 3"
-#: gschem/src/i_callbacks.c:2058
+#: gschem/src/i_callbacks.c:2065
msgid "Cut 4"
msgstr "Wytnij do 4"
-#: gschem/src/i_callbacks.c:2077
+#: gschem/src/i_callbacks.c:2084
msgid "Cut 5"
msgstr "Wytnij do 5"
-#: gschem/src/i_callbacks.c:2093
+#: gschem/src/i_callbacks.c:2100
msgid "Paste 1"
msgstr "Wklej z 1"
-#: gschem/src/i_callbacks.c:2115
+#: gschem/src/i_callbacks.c:2122
msgid "Paste 2"
msgstr "Wklej z 2"
-#: gschem/src/i_callbacks.c:2137
+#: gschem/src/i_callbacks.c:2144
msgid "Paste 3"
msgstr "Wklej z 3"
-#: gschem/src/i_callbacks.c:2159
+#: gschem/src/i_callbacks.c:2166
msgid "Paste 4"
msgstr "Wklej z 4"
-#: gschem/src/i_callbacks.c:2181
+#: gschem/src/i_callbacks.c:2188
msgid "Paste 5"
msgstr "Wklej z 5"
-#: gschem/src/i_callbacks.c:2318 gschem/src/x_window.c:355
+#: gschem/src/i_callbacks.c:2325 gschem/src/x_window.c:355
msgid "Component"
msgstr "Element"
-#: gschem/src/i_callbacks.c:2354 gschem/src/i_callbacks.c:2373
-#: gschem/src/x_dialog.c:2285
+#: gschem/src/i_callbacks.c:2361 gschem/src/i_callbacks.c:2380
+#: gschem/src/x_dialog.c:2289
msgid "Attribute"
msgstr "Atrybut"
-#: gschem/src/i_callbacks.c:2395 gschem/src/i_callbacks.c:2422
-#: gschem/src/x_dialog.c:2282
+#: gschem/src/i_callbacks.c:2402 gschem/src/i_callbacks.c:2429
+#: gschem/src/x_dialog.c:2286
msgid "Net"
msgstr "PoÅ?Ä?czenie"
-#: gschem/src/i_callbacks.c:2466 gschem/src/i_callbacks.c:2493
-#: gschem/src/x_dialog.c:2300 gschem/src/x_window.c:375
+#: gschem/src/i_callbacks.c:2473 gschem/src/i_callbacks.c:2500
+#: gschem/src/x_dialog.c:2304 gschem/src/x_window.c:375
msgid "Bus"
msgstr "MagistralÄ?"
-#: gschem/src/i_callbacks.c:2574 gschem/src/i_callbacks.c:2597
+#: gschem/src/i_callbacks.c:2581 gschem/src/i_callbacks.c:2604
msgid "Line"
msgstr "LiniÄ?"
-#: gschem/src/i_callbacks.c:2619 gschem/src/i_callbacks.c:2642
+#: gschem/src/i_callbacks.c:2626 gschem/src/i_callbacks.c:2649
msgid "Box"
msgstr "ProstokÄ?t"
-#: gschem/src/i_callbacks.c:2698 gschem/src/i_callbacks.c:2722
+#: gschem/src/i_callbacks.c:2705 gschem/src/i_callbacks.c:2729
msgid "Circle"
msgstr "OkrÄ?g"
-#: gschem/src/i_callbacks.c:2744 gschem/src/i_callbacks.c:2767
+#: gschem/src/i_callbacks.c:2751 gschem/src/i_callbacks.c:2774
msgid "Arc"
msgstr "Å?uk"
-#: gschem/src/i_callbacks.c:2789 gschem/src/i_callbacks.c:2812
-#: gschem/src/x_dialog.c:2273
+#: gschem/src/i_callbacks.c:2796 gschem/src/i_callbacks.c:2819
+#: gschem/src/x_dialog.c:2277
msgid "Pin"
msgstr ""
-#: gschem/src/i_callbacks.c:2871
+#: gschem/src/i_callbacks.c:2878
#, c-format
msgid "Searching for source [%s]\n"
msgstr "Szukam źródÅ?a [%s]\n"
-#: gschem/src/i_callbacks.c:2895
+#: gschem/src/i_callbacks.c:2902
#, c-format
msgid "Cannot find source [%s]\n"
msgstr "Nie można odnaleźÄ? źródÅ?a [%s]\n"
-#: gschem/src/i_callbacks.c:2964
+#: gschem/src/i_callbacks.c:2965
#, c-format
msgid "Searching for symbol [%s]\n"
msgstr "Szukam symbolu [%s]\n"
-#: gschem/src/i_callbacks.c:2970
+#: gschem/src/i_callbacks.c:2971
msgid "Symbol is not a real file. Symbol cannot be loaded.\n"
msgstr "Symbol nie jest plikiem. Nie można wczytaÄ? symbolu.\n"
-#: gschem/src/i_callbacks.c:3001
+#: gschem/src/i_callbacks.c:3002
msgid "Cannot find any schematics above the current one!\n"
msgstr "Nie znaleziono żadnego schematu wyżej w hierarchii!\n"
-#: gschem/src/i_callbacks.c:3055
+#: gschem/src/i_callbacks.c:3056
msgid ""
"This command retrieves the component documentation from the web, but there "
"is no component selected"
@@ -614,84 +600,84 @@ msgstr ""
"To polecenie pobiera dokumentacjÄ? elementu z internetu, ale nie wybrano "
"żadnego elementu"
-#: gschem/src/i_callbacks.c:3083
+#: gschem/src/i_callbacks.c:3084
msgid "Attach"
msgstr "DoÅ?Ä?cz"
-#: gschem/src/i_callbacks.c:3130
+#: gschem/src/i_callbacks.c:3131
msgid "Detach"
msgstr "OdÅ?Ä?cz"
-#: gschem/src/i_callbacks.c:3165
+#: gschem/src/i_callbacks.c:3166
msgid "ShowN"
msgstr "WyÅ?w. nazwÄ?"
-#: gschem/src/i_callbacks.c:3201
+#: gschem/src/i_callbacks.c:3202
msgid "ShowV"
msgstr "WyÅ?w. wartoÅ?Ä?"
-#: gschem/src/i_callbacks.c:3237
+#: gschem/src/i_callbacks.c:3238
msgid "ShowB"
msgstr "WyÅ?w. oba"
-#: gschem/src/i_callbacks.c:3274
+#: gschem/src/i_callbacks.c:3275
msgid "VisToggle"
msgstr "PrzeÅ?. widocznoÅ?Ä?"
-#: gschem/src/i_callbacks.c:3304
+#: gschem/src/i_callbacks.c:3305
#, c-format
msgid "Sorry but this is a non-functioning menu option\n"
msgstr "Niestety to polecenie jeszcze nie dziaÅ?a\n"
-#: gschem/src/i_callbacks.c:3394
+#: gschem/src/i_callbacks.c:3395
msgid "Action feedback mode set to OUTLINE\n"
msgstr "Tryb wyÅ?wietlania przemieszczanych elementów\n"
-#: gschem/src/i_callbacks.c:3397
+#: gschem/src/i_callbacks.c:3398
msgid "Action feedback mode set to BOUNDINGBOX\n"
msgstr "Tryb wyÅ?wietlania obwiedni przemieszczanych elementów\n"
-#: gschem/src/i_callbacks.c:3422
+#: gschem/src/i_callbacks.c:3423
msgid "Grid OFF\n"
msgstr "Siatka: wÅ?Ä?czona\n"
-#: gschem/src/i_callbacks.c:3423
+#: gschem/src/i_callbacks.c:3424
msgid "Dot grid selected\n"
msgstr "Siatka kropkowana\n"
-#: gschem/src/i_callbacks.c:3424
+#: gschem/src/i_callbacks.c:3425
msgid "Mesh grid selected\n"
msgstr "Siatka z linii\n"
-#: gschem/src/i_callbacks.c:3445
+#: gschem/src/i_callbacks.c:3446
msgid "Snap OFF (CAUTION!)\n"
msgstr "PrzyciÄ?ganie do siatki: wyÅ?Ä?czone (OSTROÅ»NIE!)\n"
-#: gschem/src/i_callbacks.c:3448
+#: gschem/src/i_callbacks.c:3449
msgid "Snap ON\n"
msgstr "PrzyciÄ?ganie do siatki: wÅ?Ä?czone\n"
-#: gschem/src/i_callbacks.c:3451
+#: gschem/src/i_callbacks.c:3452
msgid "Snap back to the grid (CAUTION!)\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3477
+#: gschem/src/i_callbacks.c:3478
msgid "Rubber band OFF \n"
msgstr "UzupeÅ?nianie poÅ?Ä?czeÅ? przy przesuwaniu: wÅ?Ä?czone \n"
-#: gschem/src/i_callbacks.c:3480
+#: gschem/src/i_callbacks.c:3481
msgid "Rubber band ON\n"
msgstr "UzupeÅ?nianie poÅ?Ä?czeÅ? przy przesuwaniu: wyÅ?Ä?czone\n"
-#: gschem/src/i_callbacks.c:3495
+#: gschem/src/i_callbacks.c:3496
msgid "magnetic net mode: ON\n"
msgstr "tryb \"magnesu\": wÅ?Ä?czony\n"
-#: gschem/src/i_callbacks.c:3498
+#: gschem/src/i_callbacks.c:3499
msgid "magnetic net mode: OFF\n"
msgstr "tryb \"magnesu\": wyÅ?Ä?czony\n"
-#: gschem/src/o_box.c:153
+#: gschem/src/o_box.c:149
#, c-format
msgid "Unknown type for box (fill)!\n"
msgstr "Nieznany typ dla prostokÄ?ta (wypeÅ?nienie)!\n"
@@ -713,17 +699,17 @@ msgstr ""
"NieprawidÅ?owy parametr buffer_number przekazany do funkcji "
"o_buffer_paste_start\n"
-#: gschem/src/o_bus.c:118
+#: gschem/src/o_bus.c:117
#, c-format
msgid "Got an invalid which one in o_bus_draw_stretch\n"
msgstr ""
-#: gschem/src/o_circle.c:134
+#: gschem/src/o_circle.c:130
#, c-format
msgid "Unknown type for circle (fill)!\n"
msgstr "Nieznany typ dla okrÄ?gu (wypeÅ?nienie)!\n"
-#: gschem/src/o_complex.c:243 gschem/src/o_complex.c:247
+#: gschem/src/o_complex.c:237 gschem/src/o_complex.c:241
#, c-format
msgid "Translating schematic [%d %d]\n"
msgstr ""
@@ -741,37 +727,37 @@ msgstr "Obiekt jest już zablokowany\n"
msgid "Object already unlocked\n"
msgstr "Obiekt jest już odblokowany\n"
-#: gschem/src/o_misc.c:413
+#: gschem/src/o_misc.c:409
msgid "Hidden text is now visible\n"
msgstr "Ukryty tekst jest teraz widoczny\n"
-#: gschem/src/o_misc.c:415
+#: gschem/src/o_misc.c:411
msgid "Hidden text is now invisible\n"
msgstr "Ukryty tekst jest teraz niewidoczny\n"
-#: gschem/src/o_misc.c:668
+#: gschem/src/o_misc.c:636
#, c-format
msgid "Could not find symbol [%s] in library. Update failed.\n"
msgstr ""
"Nie odnaleziono symbolu [%s] w bibliotece. Aktualizacja nie powiodÅ?a siÄ?.\n"
-#: gschem/src/o_misc.c:783
+#: gschem/src/o_misc.c:751
#, c-format
msgid "o_autosave_backups: Can't get the real filename of %s."
msgstr ""
"o_autosave_backups: Nie można okreÅ?liÄ? rzeczywistej nazwy pliku dla %s."
-#: gschem/src/o_misc.c:827
+#: gschem/src/o_misc.c:795
#, c-format
msgid "Could NOT set previous backup file [%s] read-write\n"
msgstr ""
-#: gschem/src/o_misc.c:845
+#: gschem/src/o_misc.c:815
#, c-format
msgid "Could NOT set backup file [%s] readonly\n"
msgstr ""
-#: gschem/src/o_misc.c:850
+#: gschem/src/o_misc.c:820
#, c-format
msgid "Could NOT save backup file [%s]\n"
msgstr "Zapisywanie kopii zapasowej [%s] nie powiodÅ?o siÄ?\n"
@@ -792,36 +778,36 @@ msgid "Got a non line object in o_move_check_endpoint\n"
msgstr ""
"Obiekt który nie jest liniÄ? przekazany do funkcji o_move_check_endpoint\n"
-#: gschem/src/o_net.c:159
+#: gschem/src/o_net.c:158
#, c-format
msgid "Got an invalid which one in o_net_draw_stretch\n"
msgstr ""
-#: gschem/src/o_net.c:538
+#: gschem/src/o_net.c:537
msgid "Warning: Starting net at off grid coordinate\n"
msgstr "Uwaga: PoczÄ?tek poÅ?Ä?czenia jest poza siatkÄ?\n"
-#: gschem/src/o_net.c:600
+#: gschem/src/o_net.c:599
msgid "Warning: Ending net at off grid coordinate\n"
msgstr "Uwaga: Koniec poÅ?Ä?czenia jest poza siatkÄ?\n"
-#: gschem/src/o_net.c:932 gschem/src/o_net.c:969 gschem/src/o_net.c:1040
-#: gschem/src/o_net.c:1076
+#: gschem/src/o_net.c:931 gschem/src/o_net.c:968 gschem/src/o_net.c:1039
+#: gschem/src/o_net.c:1075
#, c-format
msgid "Tried to add more than two bus rippers. Internal gschem error.\n"
msgstr ""
-#: gschem/src/o_net.c:1144
+#: gschem/src/o_net.c:1143
#, c-format
msgid "Bus ripper symbol [%s] was not found in any component library\n"
msgstr ""
-#: gschem/src/o_path.c:352
+#: gschem/src/o_path.c:348
#, c-format
msgid "Unknown type for path (fill)!\n"
msgstr ""
-#: gschem/src/o_picture.c:163 gschem/src/o_picture.c:539
+#: gschem/src/o_picture.c:163 gschem/src/o_picture.c:537
#, c-format
msgid "Failed to load picture: %s"
msgstr "Wczytanie obrazu %s nie powiodÅ?o siÄ?"
@@ -830,7 +816,7 @@ msgstr "Wczytanie obrazu %s nie powiodÅ?o siÄ?"
msgid "Picture"
msgstr "Obraz"
-#: gschem/src/o_picture.c:447 gschem/src/x_attribedit.c:141
+#: gschem/src/o_picture.c:445 gschem/src/x_attribedit.c:141
#, c-format
msgid "ERROR: NULL object!\n"
msgstr "BÅ?Ä?D: obiekt NULL!\n"
@@ -851,35 +837,47 @@ msgstr ""
msgid "New slot number out of range\n"
msgstr ""
-#: gschem/src/o_undo.c:304
+#: gschem/src/o_undo.c:303
msgid "Undo/Redo disabled in rc file\n"
msgstr ""
"FunkcjonalnoÅ?Ä? Cofnij/Powtórz zostaÅ?y wyÅ?Ä?czone w pliku konfiguracyjnym\n"
-#: gschem/src/parsecmd.c:47
+#: gschem/src/parsecmd.c:81
#, c-format
msgid ""
-"Usage: %s [OPTIONS] schematic_filename1 ... schematic_filenameN\n"
-" -q Quiet mode\n"
-" -v Verbose mode on\n"
-" -r filename Rc filename\n"
-" -s filename Script (guile) filename\n"
-" -o filename Output filename (for printing)\n"
-" -p Automatically place the window\n"
-" -t Print stroke information\n"
-" -h Help; this message\n"
+"Usage: %s [OPTION ...] [--] [FILE ...]\n"
"\n"
-msgstr ""
-"SkÅ?adnia: %s [OPCJE] plik_schematu1 ... plik_schematuN\n"
-" -q Tryb cichy\n"
-" -v Tryb gadatliwy\n"
-" -r plik Plik konfiguracji\n"
-" -s plik Plik skryptu (guile)\n"
-" -o plik Plik do zapisu wyników wydruku\n"
-" -p Automatyczne rozmieszczanie okien\n"
-" -t Wypisuj informacje o stylach linii\n"
-" -h Pomoc; ten komunikat\n"
+"Interactively edit gEDA schematics or symbols. If one or more FILEs\n"
+"are specified, open them for editing; otherwise, create a new, empty\n"
+"schematic.\n"
"\n"
+"Options:\n"
+" -q, --quiet Quiet mode.\n"
+" -v, --verbose Verbose mode.\n"
+" -r, --config-file=FILE Additional configuration file to load.\n"
+" -L DIR Add DIR to Scheme search path.\n"
+" -c EXPR Scheme expression to run at startup.\n"
+" -s FILE Scheme script to run at startup.\n"
+" -o, --output=FILE Output filename (for printing).\n"
+" -p Automatically place the window.\n"
+" -V, --version Show version information.\n"
+" -h, --help Help; this message.\n"
+" -- Treat all remaining arguments as filenames.\n"
+"\n"
+"Report bugs to <geda-bug@xxxxxxxx>\n"
+"gEDA/gaf homepage: <http://gpleda.org>\n"
+msgstr ""
+
+#: gschem/src/parsecmd.c:115
+#, c-format
+msgid ""
+"gEDA %s (g%.7s)\n"
+"Copyright (C) 1998-2011 gEDA developers\n"
+"This is free software, and you are welcome to redistribute it under\n"
+"certain conditions. For details, see the file `COPYING', which is\n"
+"included in the gEDA distribution.\n"
+"There is NO WARRANTY, to the extent permitted by law.\n"
+msgstr ""
#: gschem/src/x_attribedit.c:127
#, c-format
@@ -892,56 +890,56 @@ msgstr ""
msgid "Single Attribute Editor"
msgstr "Edycja pojedyÅ?czego atrybutu"
-#: gschem/src/x_attribedit.c:358
+#: gschem/src/x_attribedit.c:359
msgid "<b>Edit Attribute</b>"
msgstr "<b>Edytuj atrybut</b>"
-#: gschem/src/x_attribedit.c:360
+#: gschem/src/x_attribedit.c:361
msgid "<b>Add Attribute</b>"
msgstr "<b>Dodaj atrybut</b>"
-#: gschem/src/x_attribedit.c:376 gschem/src/x_multiattrib.c:1916
+#: gschem/src/x_attribedit.c:377 gschem/src/x_multiattrib.c:1927
msgid "Name:"
msgstr "Nazwa:"
-#: gschem/src/x_attribedit.c:393 gschem/src/x_multiattrib.c:1935
+#: gschem/src/x_attribedit.c:394 gschem/src/x_multiattrib.c:1946
msgid "Value:"
msgstr "WartoÅ?Ä?:"
-#: gschem/src/x_attribedit.c:409 gschem/src/x_multiattrib.c:1978
+#: gschem/src/x_attribedit.c:410 gschem/src/x_multiattrib.c:1989
msgid "Visible"
msgstr "Widoczny"
-#: gschem/src/x_attribedit.c:429
+#: gschem/src/x_attribedit.c:430
msgid "Show Value Only"
msgstr "WyÅ?wietlaj wartoÅ?Ä?"
-#: gschem/src/x_attribedit.c:431
+#: gschem/src/x_attribedit.c:432
msgid "Show Name Only"
msgstr "WyÅ?wietlaj nazwÄ?"
-#: gschem/src/x_attribedit.c:433 gschem/src/x_multiattrib.c:1454
+#: gschem/src/x_attribedit.c:434 gschem/src/x_multiattrib.c:1466
msgid "Show Name & Value"
msgstr "WyÅ?wietlaj nazwÄ? i wartoÅ?Ä?"
-#: gschem/src/x_attribedit.c:440
+#: gschem/src/x_attribedit.c:441
msgid "<b>Attach Options</b>"
msgstr "<b>Opcje doÅ?Ä?czenia</b>"
-#: gschem/src/x_attribedit.c:455
+#: gschem/src/x_attribedit.c:456
msgid "All"
msgstr "Wszystko"
-#: gschem/src/x_attribedit.c:463 gschem/src/x_compselect.c:896
-#: gschem/src/x_compselect.c:1010
+#: gschem/src/x_attribedit.c:464 gschem/src/x_compselect.c:904
+#: gschem/src/x_compselect.c:1018
msgid "Components"
msgstr "Elementy"
-#: gschem/src/x_attribedit.c:471 gschem/src/x_window.c:365
+#: gschem/src/x_attribedit.c:472 gschem/src/x_window.c:365
msgid "Nets"
msgstr "PoÅ?Ä?czenia"
-#: gschem/src/x_attribedit.c:479
+#: gschem/src/x_attribedit.c:480
msgid "Replace existing attributes"
msgstr "ZastÄ?p istniejÄ?ce atrybuty"
@@ -957,91 +955,91 @@ msgid ""
"duplicate slot may cause problems: [symbolname=%s, number=%d, slot=%d]\n"
msgstr ""
-#: gschem/src/x_autonumber.c:673
+#: gschem/src/x_autonumber.c:675
msgid "No searchstring given in autonumber text.\n"
msgstr "Nie podano tekstu wyszukiwania.\n"
-#: gschem/src/x_autonumber.c:725
+#: gschem/src/x_autonumber.c:727
msgid "No '*' or '?' given at the end of the autonumber text.\n"
msgstr "Brak '*' lub '?' na koÅ?cu tekstu do automatycznej numeracji.\n"
-#: gschem/src/x_autonumber.c:860
+#: gschem/src/x_autonumber.c:862
msgid "Diagonal"
msgstr "Po przekÄ?tnej"
-#: gschem/src/x_autonumber.c:861
+#: gschem/src/x_autonumber.c:863
msgid "Top to bottom"
msgstr "Od góry do doÅ?u"
-#: gschem/src/x_autonumber.c:861
+#: gschem/src/x_autonumber.c:863
msgid "Bottom to top"
msgstr "Od doÅ?u do góry"
-#: gschem/src/x_autonumber.c:862
+#: gschem/src/x_autonumber.c:864
msgid "Left to right"
msgstr "Od lewej do prawej"
-#: gschem/src/x_autonumber.c:862
+#: gschem/src/x_autonumber.c:864
msgid "Right to left"
msgstr "Od prawej do lewej"
-#: gschem/src/x_autonumber.c:863
+#: gschem/src/x_autonumber.c:865
msgid "File order"
msgstr "KolejnoÅ?Ä? plików"
-#: gschem/src/x_autonumber.c:1199
+#: gschem/src/x_autonumber.c:1201
msgid "Autonumber text"
msgstr "Automatyczna numeracja"
-#: gschem/src/x_autonumber.c:1223
+#: gschem/src/x_autonumber.c:1225
msgid "<b>Scope</b>"
msgstr "<b>Zakres</b>"
-#: gschem/src/x_autonumber.c:1245
+#: gschem/src/x_autonumber.c:1247
msgid "Search for:"
msgstr "Wyszukiwany tekst:"
-#: gschem/src/x_autonumber.c:1259
+#: gschem/src/x_autonumber.c:1261
msgid "Autonumber text in:"
msgstr "Automatycznie numeruj w:"
-#: gschem/src/x_autonumber.c:1266
+#: gschem/src/x_autonumber.c:1268
msgid "Skip numbers found in:"
msgstr "PomiÅ? numery znalezione w:"
-#: gschem/src/x_autonumber.c:1278 gschem/src/x_autonumber.c:1287
+#: gschem/src/x_autonumber.c:1280 gschem/src/x_autonumber.c:1289
msgid "Selected objects"
msgstr "Zaznaczonych elementach"
-#: gschem/src/x_autonumber.c:1279 gschem/src/x_autonumber.c:1288
+#: gschem/src/x_autonumber.c:1281 gschem/src/x_autonumber.c:1290
msgid "Current page"
msgstr "BieżÄ?cej stronie"
-#: gschem/src/x_autonumber.c:1280 gschem/src/x_autonumber.c:1289
+#: gschem/src/x_autonumber.c:1282 gschem/src/x_autonumber.c:1291
msgid "Whole hierarchy"
msgstr "CaÅ?ej hierarchii"
-#: gschem/src/x_autonumber.c:1291
+#: gschem/src/x_autonumber.c:1293
msgid "Overwrite existing numbers"
msgstr "ZastÄ?puj istniejÄ?cÄ? numeracjÄ?"
-#: gschem/src/x_autonumber.c:1296
+#: gschem/src/x_autonumber.c:1298
msgid "<b>Options</b>"
msgstr "<b>Opcje</b>"
-#: gschem/src/x_autonumber.c:1318
+#: gschem/src/x_autonumber.c:1320
msgid "Starting number:"
msgstr "Numer poczÄ?tkowy"
-#: gschem/src/x_autonumber.c:1325
+#: gschem/src/x_autonumber.c:1327
msgid "Sort order:"
msgstr "KolejnoÅ?Ä?:"
-#: gschem/src/x_autonumber.c:1346
+#: gschem/src/x_autonumber.c:1348
msgid "Remove numbers"
msgstr "UsuÅ? numery"
-#: gschem/src/x_autonumber.c:1350
+#: gschem/src/x_autonumber.c:1352
msgid "Automatic slotting"
msgstr ""
@@ -1078,48 +1076,48 @@ msgstr "Próba użycia nieprawidÅ?owego koloru: %d\n"
msgid "Tried to get an invalid outline color: %d\n"
msgstr "Próba użycia nieprawidÅ?owego koloru obwiedni: %d\n"
-#: gschem/src/x_compselect.c:1040
+#: gschem/src/x_compselect.c:1048
msgid "Filter:"
msgstr "Filtr:"
-#: gschem/src/x_compselect.c:1143 gschem/src/x_dialog.c:3663
-#: gschem/src/x_multiattrib.c:1782
+#: gschem/src/x_compselect.c:1151 gschem/src/x_dialog.c:3667
+#: gschem/src/x_multiattrib.c:1793
msgid "Name"
msgstr "Nazwa"
-#: gschem/src/x_compselect.c:1152 gschem/src/x_multiattrib.c:1806
+#: gschem/src/x_compselect.c:1160 gschem/src/x_multiattrib.c:1817
msgid "Value"
msgstr "WartoÅ?Ä?"
-#: gschem/src/x_compselect.c:1191
+#: gschem/src/x_compselect.c:1199
msgid "Default behavior - reference component"
msgstr "DomyÅ?lnie - użyj odniesiena do pliku elementu"
-#: gschem/src/x_compselect.c:1194
+#: gschem/src/x_compselect.c:1202
msgid "Embed component in schematic"
msgstr "Osadź element w pliku schematu"
-#: gschem/src/x_compselect.c:1197
+#: gschem/src/x_compselect.c:1205
msgid "Include component as individual objects"
msgstr "Wstaw element jako indywidualne obiekty skÅ?adowe"
-#: gschem/src/x_compselect.c:1354
+#: gschem/src/x_compselect.c:1362
msgid "Select Component..."
msgstr "Wybierz element..."
-#: gschem/src/x_compselect.c:1377
+#: gschem/src/x_compselect.c:1385
msgid "In Use"
msgstr "W użyciu"
-#: gschem/src/x_compselect.c:1381
+#: gschem/src/x_compselect.c:1389
msgid "Libraries"
msgstr "Biblioteki"
-#: gschem/src/x_compselect.c:1390 gschem/src/x_fileselect.c:122
+#: gschem/src/x_compselect.c:1398 gschem/src/x_fileselect.c:122
msgid "Preview"
msgstr "PodglÄ?d"
-#: gschem/src/x_compselect.c:1418
+#: gschem/src/x_compselect.c:1426
msgid "Attributes"
msgstr "Atrybuty"
@@ -1177,336 +1175,336 @@ msgstr "Na dole po prawej"
msgid "Edit Text Properties"
msgstr "Edycja wÅ?aÅ?ciwoÅ?ci tekstu"
-#: gschem/src/x_dialog.c:471
+#: gschem/src/x_dialog.c:472
msgid "<b>Text Content</b>"
msgstr "<b>TreÅ?Ä? tekstu</b>"
-#: gschem/src/x_dialog.c:507
+#: gschem/src/x_dialog.c:508
msgid "<b>Text Properties</b>"
msgstr "<b>WÅ?aÅ?ciwoÅ?ci tekstu</b>"
-#: gschem/src/x_dialog.c:522
+#: gschem/src/x_dialog.c:523
msgid "Color:"
msgstr "Kolor:"
-#: gschem/src/x_dialog.c:529
+#: gschem/src/x_dialog.c:530
msgid "Size:"
msgstr "Rozmiar:"
-#: gschem/src/x_dialog.c:538
+#: gschem/src/x_dialog.c:539
msgid "Alignment:"
msgstr "Punkt odniesienia:"
-#: gschem/src/x_dialog.c:587
+#: gschem/src/x_dialog.c:588
msgid "Solid"
msgstr "Jednolita"
-#: gschem/src/x_dialog.c:588
+#: gschem/src/x_dialog.c:589
msgid "Dotted"
msgstr "Kropki"
-#: gschem/src/x_dialog.c:589
+#: gschem/src/x_dialog.c:590
msgid "Dashed"
msgstr "Kreski"
-#: gschem/src/x_dialog.c:590
+#: gschem/src/x_dialog.c:591
msgid "Center"
msgstr "Kropka-kreska"
-#: gschem/src/x_dialog.c:591
+#: gschem/src/x_dialog.c:592
msgid "Phantom"
msgstr "Kropka-kropka-kreska"
-#: gschem/src/x_dialog.c:592 gschem/src/x_dialog.c:689
-#: gschem/src/x_dialog.c:698 gschem/src/x_dialog.c:707
-#: gschem/src/x_dialog.c:808 gschem/src/x_dialog.c:810
-#: gschem/src/x_dialog.c:812 gschem/src/x_dialog.c:1038
-#: gschem/src/x_dialog.c:1141 gschem/src/x_dialog.c:1150
-#: gschem/src/x_dialog.c:1159 gschem/src/x_dialog.c:1168
-#: gschem/src/x_dialog.c:1177 gschem/src/x_dialog.c:1290
-#: gschem/src/x_dialog.c:1292 gschem/src/x_dialog.c:1294
-#: gschem/src/x_dialog.c:1296 gschem/src/x_dialog.c:1298
+#: gschem/src/x_dialog.c:593 gschem/src/x_dialog.c:690
+#: gschem/src/x_dialog.c:699 gschem/src/x_dialog.c:708
+#: gschem/src/x_dialog.c:809 gschem/src/x_dialog.c:811
+#: gschem/src/x_dialog.c:813 gschem/src/x_dialog.c:1039
+#: gschem/src/x_dialog.c:1142 gschem/src/x_dialog.c:1151
+#: gschem/src/x_dialog.c:1160 gschem/src/x_dialog.c:1169
+#: gschem/src/x_dialog.c:1178 gschem/src/x_dialog.c:1291
+#: gschem/src/x_dialog.c:1293 gschem/src/x_dialog.c:1295
+#: gschem/src/x_dialog.c:1297 gschem/src/x_dialog.c:1299
msgid "*unchanged*"
msgstr "*bez zmian*"
-#: gschem/src/x_dialog.c:916
+#: gschem/src/x_dialog.c:917
msgid "Edit Line Width & Type"
msgstr "Edycja stylu linii"
-#: gschem/src/x_dialog.c:955 gschem/src/x_print.c:307
+#: gschem/src/x_dialog.c:956 gschem/src/x_print.c:307
msgid "Type:"
msgstr "Rodzaj:"
-#: gschem/src/x_dialog.c:959
+#: gschem/src/x_dialog.c:960
msgid "Width:"
msgstr "SzerokoÅ?Ä?:"
-#: gschem/src/x_dialog.c:963
+#: gschem/src/x_dialog.c:964
msgid "Dash Length:"
msgstr "DÅ?ugoÅ?Ä? kreski"
-#: gschem/src/x_dialog.c:967
+#: gschem/src/x_dialog.c:968
msgid "Dash Space:"
msgstr "DÅ?ugoÅ?Ä? przerwy"
-#: gschem/src/x_dialog.c:1034
+#: gschem/src/x_dialog.c:1035
msgid "Hollow"
msgstr "Brak"
-#: gschem/src/x_dialog.c:1035
+#: gschem/src/x_dialog.c:1036
msgid "Filled"
msgstr "PeÅ?ne"
-#: gschem/src/x_dialog.c:1036
+#: gschem/src/x_dialog.c:1037
msgid "Mesh"
msgstr "Siatka"
-#: gschem/src/x_dialog.c:1037
+#: gschem/src/x_dialog.c:1038
msgid "Hatch"
msgstr "Kreskowanie"
-#: gschem/src/x_dialog.c:1406
+#: gschem/src/x_dialog.c:1407
msgid "Edit Fill Type"
msgstr "Edytuj typ wypeÅ?nienia"
-#: gschem/src/x_dialog.c:1444
+#: gschem/src/x_dialog.c:1446
msgid "Fill Type:"
msgstr "Typ wypeÅ?nienia:"
-#: gschem/src/x_dialog.c:1448
+#: gschem/src/x_dialog.c:1450
msgid "Line Width:"
msgstr "SzerokoÅ?Ä? linii:"
-#: gschem/src/x_dialog.c:1452
+#: gschem/src/x_dialog.c:1454
msgid "Angle 1:"
msgstr "KÄ?t linii 1:"
-#: gschem/src/x_dialog.c:1456
+#: gschem/src/x_dialog.c:1458
msgid "Pitch 1:"
msgstr "OdstÄ?p miÄ?dzy liniami 1:"
-#: gschem/src/x_dialog.c:1460
+#: gschem/src/x_dialog.c:1462
msgid "Angle 2:"
msgstr "KÄ?t linii 2:"
-#: gschem/src/x_dialog.c:1464
+#: gschem/src/x_dialog.c:1466
msgid "Pitch 2:"
msgstr "OdstÄ?p miÄ?dzy liniami 2:"
-#: gschem/src/x_dialog.c:1591
+#: gschem/src/x_dialog.c:1593
msgid "Arc Params"
msgstr "Parametry Å?uku"
-#: gschem/src/x_dialog.c:1631
+#: gschem/src/x_dialog.c:1634
msgid "Arc Radius:"
msgstr "PromieÅ? Å?uku:"
-#: gschem/src/x_dialog.c:1639
+#: gschem/src/x_dialog.c:1642
msgid "Start Angle:"
msgstr "KÄ?t poczÄ?tkowy:"
-#: gschem/src/x_dialog.c:1647
+#: gschem/src/x_dialog.c:1650
msgid "Degrees of Sweep:"
msgstr "KÄ?t rozwarcia"
-#: gschem/src/x_dialog.c:1764
+#: gschem/src/x_dialog.c:1768
msgid ""
"Offset to translate?\n"
"(0 for origin)"
msgstr ""
-#: gschem/src/x_dialog.c:1832
+#: gschem/src/x_dialog.c:1836
msgid "Text Size"
msgstr "Rozmiar czcionki"
-#: gschem/src/x_dialog.c:1862
+#: gschem/src/x_dialog.c:1866
msgid "Enter new text size:"
msgstr "Wprowadź nowy rozmiar czcionki:"
-#: gschem/src/x_dialog.c:1938
+#: gschem/src/x_dialog.c:1942
msgid "Snap Size"
msgstr "OdlegÅ?oÅ?Ä? przyciÄ?gania"
-#: gschem/src/x_dialog.c:1968
+#: gschem/src/x_dialog.c:1972
msgid "Enter new snap grid spacing:"
msgstr "Wprowadź nowÄ? odlegÅ?oÅ?Ä? przyciÄ?gania"
-#: gschem/src/x_dialog.c:2045
+#: gschem/src/x_dialog.c:2049
msgid "Edit slot number"
msgstr ""
-#: gschem/src/x_dialog.c:2076
+#: gschem/src/x_dialog.c:2080
msgid "Edit slot number:"
msgstr ""
-#: gschem/src/x_dialog.c:2117
+#: gschem/src/x_dialog.c:2121
#, c-format
msgid "%s%s (%s)"
msgstr ""
-#: gschem/src/x_dialog.c:2140
+#: gschem/src/x_dialog.c:2144
msgid "About gschem"
msgstr "O programie"
-#: gschem/src/x_dialog.c:2141
+#: gschem/src/x_dialog.c:2145
msgid "gEDA: GPL Electronic Design Automation"
msgstr ""
-#: gschem/src/x_dialog.c:2142
+#: gschem/src/x_dialog.c:2146
msgid ""
"Copyright © 1998-2009 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
"Copyright © 1998-2009 gEDA Contributors (see ChangeLog for details)"
msgstr ""
-#: gschem/src/x_dialog.c:2201
+#: gschem/src/x_dialog.c:2205
msgid "Coords"
msgstr "WspóÅ?rzÄ?dne"
-#: gschem/src/x_dialog.c:2222
+#: gschem/src/x_dialog.c:2226
msgid "Screen"
msgstr "Ekran"
-#: gschem/src/x_dialog.c:2231
+#: gschem/src/x_dialog.c:2235
msgid "World"
msgstr "Å?wiat"
-#: gschem/src/x_dialog.c:2270
+#: gschem/src/x_dialog.c:2274
msgid "Background"
msgstr "TÅ?o"
-#: gschem/src/x_dialog.c:2276
+#: gschem/src/x_dialog.c:2280
msgid "Net endpoint"
msgstr "Koniec poÅ?Ä?czeni"
-#: gschem/src/x_dialog.c:2279
+#: gschem/src/x_dialog.c:2283
msgid "Graphic"
msgstr "Graficzne"
-#: gschem/src/x_dialog.c:2288
+#: gschem/src/x_dialog.c:2292
msgid "Logic bubble"
msgstr "Negacja logiczna"
-#: gschem/src/x_dialog.c:2291
+#: gschem/src/x_dialog.c:2295
msgid "Grid point"
msgstr "Punkt siatki"
-#: gschem/src/x_dialog.c:2294
+#: gschem/src/x_dialog.c:2298
msgid "Detached attribute"
msgstr "OdÅ?Ä?czony atrybut"
-#: gschem/src/x_dialog.c:2297 gschem/src/x_window.c:383
+#: gschem/src/x_dialog.c:2301 gschem/src/x_window.c:383
msgid "Text"
msgstr "Tekst"
-#: gschem/src/x_dialog.c:2303
+#: gschem/src/x_dialog.c:2307
msgid "Selection"
msgstr "Zaznaczenie"
-#: gschem/src/x_dialog.c:2306
+#: gschem/src/x_dialog.c:2310
msgid "Bounding box"
msgstr "Obwiednia"
-#: gschem/src/x_dialog.c:2309
+#: gschem/src/x_dialog.c:2313
msgid "Zoom box"
msgstr "Obszar powiÄ?kszenia"
-#: gschem/src/x_dialog.c:2318
+#: gschem/src/x_dialog.c:2322
msgid "Output background"
msgstr "TÅ?o wydruku"
-#: gschem/src/x_dialog.c:2321
+#: gschem/src/x_dialog.c:2325
msgid "Net junction"
msgstr "PoÅ?Ä?czenie przewodów"
-#: gschem/src/x_dialog.c:2324
+#: gschem/src/x_dialog.c:2328
msgid "Mesh grid major"
msgstr "Siatka zgrubna"
-#: gschem/src/x_dialog.c:2327
+#: gschem/src/x_dialog.c:2331
msgid "Mesh grid minor"
msgstr "Siatka dokÅ?adna"
-#: gschem/src/x_dialog.c:2330
+#: gschem/src/x_dialog.c:2334
msgid "Unknown"
msgstr "Nieznane"
-#: gschem/src/x_dialog.c:2481
+#: gschem/src/x_dialog.c:2485
#, c-format
msgid "ERROR: NULL object in color_edit_dialog_apply!\n"
msgstr "BÅ?Ä?D: obiekt NULL w funkcji color_edit_dialog_apply!\n"
-#: gschem/src/x_dialog.c:2525
+#: gschem/src/x_dialog.c:2529
msgid "Color Edit"
msgstr "Edycja koloru"
-#: gschem/src/x_dialog.c:2556
+#: gschem/src/x_dialog.c:2560
msgid "Object color:"
msgstr "Kolor obiektu:"
-#: gschem/src/x_dialog.c:2614
+#: gschem/src/x_dialog.c:2618
msgid "Hotkeys"
msgstr "Klawisze skrótów"
-#: gschem/src/x_dialog.c:2678
+#: gschem/src/x_dialog.c:2682
msgid "Function"
msgstr "Funkcja"
-#: gschem/src/x_dialog.c:2685
+#: gschem/src/x_dialog.c:2689
msgid "Keystroke(s)"
msgstr "Klawisz(e)"
-#: gschem/src/x_dialog.c:2991
+#: gschem/src/x_dialog.c:2995
msgid "Find Text"
msgstr "Znajdź tekst"
-#: gschem/src/x_dialog.c:3022
+#: gschem/src/x_dialog.c:3026
msgid "Text to find:"
msgstr "Szukany tekst:"
-#: gschem/src/x_dialog.c:3032
+#: gschem/src/x_dialog.c:3036
msgid "descend into hierarchy"
msgstr "Szukaj również wewnÄ?trz elementów"
-#: gschem/src/x_dialog.c:3097
+#: gschem/src/x_dialog.c:3101
msgid "Hide Text"
msgstr "Ukryj tekst"
-#: gschem/src/x_dialog.c:3128
+#: gschem/src/x_dialog.c:3132
msgid "Hide text starting with:"
msgstr "Ukryj tekst zaczynajÄ?cy siÄ? od:"
-#: gschem/src/x_dialog.c:3197
+#: gschem/src/x_dialog.c:3201
msgid "Show Text"
msgstr "WyÅ?wietl tekst"
-#: gschem/src/x_dialog.c:3228
+#: gschem/src/x_dialog.c:3232
msgid "Show text starting with:"
msgstr "WyÅ?wietl tekst zaczynajÄ?cy siÄ? od:"
-#: gschem/src/x_dialog.c:3685
+#: gschem/src/x_dialog.c:3689
msgid "S_elect the schematics you want to save:"
msgstr "Wybi_erz schematy, które chcesz zapisaÄ?:"
-#: gschem/src/x_dialog.c:3779
+#: gschem/src/x_dialog.c:3784
#, c-format
msgid "Save the changes to schematic \"%s\" before closing?"
msgstr "ZapisaÄ? zmiany w schemacie \"%s\" przed wyjÅ?ciem?"
-#: gschem/src/x_dialog.c:3785
+#: gschem/src/x_dialog.c:3790
#, c-format
msgid ""
"There are %d schematics with unsaved changes. Save changes before closing?"
msgstr "Niezapisane zmiany w %d schematach. ZapisaÄ? zmiany przed wyjÅ?ciem?"
-#: gschem/src/x_dialog.c:3814
+#: gschem/src/x_dialog.c:3819
msgid "If you don't save, all your changes will be permanently lost."
msgstr "Jeżeli nie zapiszesz, wszystkie zmiany zostanÄ? bezpowrotnie utracone."
-#: gschem/src/x_dialog.c:3834
+#: gschem/src/x_dialog.c:3839
msgid "_Close without saving"
msgstr "_Zamknij bez zapisywania"
-#: gschem/src/x_dialog.c:4170
+#: gschem/src/x_dialog.c:4175
#, c-format
msgid ""
"<span weight=\"bold\" size=\"larger\">The input attribute \"%s\" is invalid\n"
@@ -1523,19 +1521,19 @@ msgstr ""
"Nazwa nie może zaczynaÄ? siÄ? od spacji.\n"
"WartoÅ?Ä? nie może zaczynaÄ? siÄ? od spacji."
-#: gschem/src/x_dialog.c:4172
+#: gschem/src/x_dialog.c:4177
msgid "Invalid Attribute"
msgstr "NieprawidÅ?owy atrybut"
-#: gschem/src/x_dialog.c:4208
+#: gschem/src/x_dialog.c:4213
msgid "Pin type"
msgstr ""
-#: gschem/src/x_dialog.c:4232
+#: gschem/src/x_dialog.c:4237
msgid "Net pin"
msgstr ""
-#: gschem/src/x_dialog.c:4234
+#: gschem/src/x_dialog.c:4239
msgid "Bus pin (graphical)"
msgstr ""
@@ -1635,13 +1633,13 @@ msgstr "Typ obrazu"
msgid "Write image..."
msgstr "Zapisz jako obraz..."
-#: gschem/src/x_log.c:188
+#: gschem/src/x_log.c:209
msgid "** Invalid UTF-8 in log message. See stderr or gschem.log.\n"
msgstr ""
"** NieprawidÅ?owy znak UTF-8 w komunikacie. Zobacz standardowe wyjÅ?cie bÅ?Ä?dów "
"lub plik gschem.log.\n"
-#: gschem/src/x_log.c:256
+#: gschem/src/x_log.c:288
msgid "Status"
msgstr "Stan"
@@ -1717,69 +1715,60 @@ msgstr "/WgÅ?Ä?b symbolu"
msgid "/Up"
msgstr "/Do góry"
-#: gschem/src/x_menus.c:321
+#: gschem/src/x_menus.c:323
#, c-format
msgid "Tried to set the sensitivity on non-existent menu item '%s'\n"
msgstr "Próba aktywacji nieistniejÄ?cego elementu menu '%s'\n"
-#: gschem/src/x_menus.c:345
+#: gschem/src/x_menus.c:347
msgid "Popup_menu_item_factory doesn't exist!\n"
msgstr "Popup_menu_item_factory nie istnieje!\n"
-#: gschem/src/x_menus.c:358
+#: gschem/src/x_menus.c:360
msgid "Tried to set the sensitivity on a non-existent popup menu_item\n"
msgstr "Próba aktywacji nieistniejÄ?cego elementu menu kontekstowego\n"
-#: gschem/src/x_menus.c:438
-#, c-format
-msgid "Couldn't open file %s\n"
-msgstr "Otwieranie pliku %s nie powiodÅ?o siÄ?\n"
-
-#: gschem/src/x_menus.c:495
-msgid "Clear"
-msgstr "WyczyÅ?Ä?"
-
-#: gschem/src/x_multiattrib.c:911
+#: gschem/src/x_multiattrib.c:915
msgid "Attributes with empty name are not allowed. Please set a name."
msgstr "Atrybuty bez nazwy nie sÄ? dozwolone. Podaj prawidÅ?owÄ? nazwÄ?."
-#: gschem/src/x_multiattrib.c:1456
+#: gschem/src/x_multiattrib.c:1468
msgid "Show Value only"
msgstr "WyÅ?wietlaj wartoÅ?Ä?"
-#: gschem/src/x_multiattrib.c:1458
+#: gschem/src/x_multiattrib.c:1470
msgid "Show Name only"
msgstr "WyÅ?wietlaj nazwÄ?"
-#: gschem/src/x_multiattrib.c:1486
+#: gschem/src/x_multiattrib.c:1498
msgid "Promote"
msgstr ""
-#: gschem/src/x_multiattrib.c:1490
+#: gschem/src/x_multiattrib.c:1502
msgid "Duplicate"
msgstr "Duplikuj"
-#: gschem/src/x_multiattrib.c:1708
+#: gschem/src/x_multiattrib.c:1719
msgid "Edit Attributes"
msgstr "Zmodyfikuj atrybuty"
-#: gschem/src/x_multiattrib.c:1826
+#: gschem/src/x_multiattrib.c:1837
msgid "Vis?"
msgstr "Widoczny?"
-#: gschem/src/x_multiattrib.c:1844
+#: gschem/src/x_multiattrib.c:1855
msgid "N"
msgstr "N"
-#: gschem/src/x_multiattrib.c:1862
+#: gschem/src/x_multiattrib.c:1873
msgid "V"
msgstr "W"
-#: gschem/src/x_multiattrib.c:1884
+#: gschem/src/x_multiattrib.c:1895
msgid "Show inherited attributes"
msgstr "Pokaż odziedziczone atrybuty"
-#: gschem/src/x_multiattrib.c:1900
+#: gschem/src/x_multiattrib.c:1911
msgid "Add Attribute"
msgstr "Dodaj atrybut"
@@ -1803,23 +1792,23 @@ msgstr "Zamknij arkusz"
msgid "Discard Page"
msgstr "PorzuÄ? arkusz"
-#: gschem/src/x_pagesel.c:376
+#: gschem/src/x_pagesel.c:375
msgid "Page Manager"
msgstr "ZarzÄ?dzanie arkuszami"
-#: gschem/src/x_pagesel.c:432
+#: gschem/src/x_pagesel.c:431
msgid "Filename"
msgstr "Nazwa pliku"
-#: gschem/src/x_pagesel.c:448
+#: gschem/src/x_pagesel.c:447
msgid "Changed"
msgstr "Zmieniono"
-#: gschem/src/x_pagesel.c:468
+#: gschem/src/x_pagesel.c:467
msgid "Right click on the filename for more options..."
msgstr "Kliknij prawym przyciskiem myszy na nazwie pliku aby zobaczyÄ? opcje..."
-#: gschem/src/x_preview.c:234
+#: gschem/src/x_preview.c:233
msgid "Preview Buffer"
msgstr ""
@@ -1875,16 +1864,16 @@ msgstr "Plik:"
msgid "Command:"
msgstr "Polecenie:"
-#: gschem/src/x_print.c:741
+#: gschem/src/x_print.c:745
msgid "No print destination specified\n"
msgstr "Nie podano lokalizacji docelowej wydruku\n"
-#: gschem/src/x_print.c:748
+#: gschem/src/x_print.c:752
#, c-format
msgid "Cannot print current schematic to [%s]\n"
msgstr "Nie można wydrukowaÄ? bieżÄ?cego arkusza do [%s]\n"
-#: gschem/src/x_print.c:757
+#: gschem/src/x_print.c:761
#, c-format
msgid ""
"Error printing to file '%s'\n"
@@ -1893,7 +1882,7 @@ msgstr ""
"BÅ?Ä?d wydruku do pliku '%s'\n"
"WiÄ?cej szczegóÅ?ów w oknie komunikatów"
-#: gschem/src/x_print.c:764
+#: gschem/src/x_print.c:768
#, c-format
msgid "Printed current schematic to [%s]\n"
msgstr "Wydrukowano bieżÄ?cy arkusz do [%s]\n"
@@ -1902,6 +1891,11 @@ msgstr "Wydrukowano bieżÄ?cy arkusz do [%s]\n"
msgid "Execute Script..."
msgstr "Wykonaj skrypt..."
+#: gschem/src/x_script.c:66
+#, c-format
+msgid "Executing guile script [%s]\n"
+msgstr "Wykonywanie skryptu guile [%s]\n"
+
#: gschem/src/x_window.c:81
#, c-format
msgid "Couldn't allocate gc\n"
@@ -2017,35 +2011,35 @@ msgstr "Otwarcie pliku nie powiodÅ?o siÄ?"
msgid "New file [%s]\n"
msgstr "Nowy plik [%s]\n"
-#: gschem/src/x_window.c:857
+#: gschem/src/x_window.c:855
#, c-format
msgid "Could NOT save page [%s]\n"
msgstr "Zapisanie arkusza [%s] nie powiodÅ?o siÄ?\n"
-#: gschem/src/x_window.c:858
+#: gschem/src/x_window.c:856
msgid "Error while trying to save"
msgstr "BÅ?Ä?d podczas próby zapisania"
-#: gschem/src/x_window.c:867
+#: gschem/src/x_window.c:865
#, c-format
msgid "Saved as [%s]\n"
msgstr "Zapisano jako [%s]\n"
-#: gschem/src/x_window.c:869
+#: gschem/src/x_window.c:867
#, c-format
msgid "Saved [%s]\n"
msgstr "Zapisano [%s]\n"
-#: gschem/src/x_window.c:871
+#: gschem/src/x_window.c:869
msgid "Saved"
msgstr "Zapisano"
-#: gschem/src/x_window.c:945
+#: gschem/src/x_window.c:943
#, c-format
msgid "Discarding page [%s]\n"
msgstr "Porzucanie arkusza [%s]\n"
-#: gschem/src/x_window.c:945
+#: gschem/src/x_window.c:943
#, c-format
msgid "Closing [%s]\n"
msgstr "Zamykanie [%s]\n"
@@ -2086,7 +2080,7 @@ msgstr "Zapisz j_ako..."
msgid "Save All"
msgstr "Zapisz _wszystkie"
-#: gschem/lib/system-gschemrc.scm:1386 gschem/lib/system-gschemrc.scm:1477
+#: gschem/lib/system-gschemrc.scm:1386 gschem/lib/system-gschemrc.scm:1478
msgid "_Revert"
msgstr "P_rzywróÄ?"
@@ -2098,7 +2092,7 @@ msgstr "_Drukuj..."
msgid "Write _image..."
msgstr "Zap_isz obraz..."
-#: gschem/lib/system-gschemrc.scm:1393 gschem/lib/system-gschemrc.scm:1478
+#: gschem/lib/system-gschemrc.scm:1393 gschem/lib/system-gschemrc.scm:1479
msgid "_Close"
msgstr "_Zamknij"
@@ -2130,391 +2124,435 @@ msgstr "_Wklej"
msgid "_Delete"
msgstr "_UsuÅ?"
-#: gschem/lib/system-gschemrc.scm:1412
+#: gschem/lib/system-gschemrc.scm:1409
+#, fuzzy
+msgid "Select All"
+msgstr "Zaznaczanie"
+
+#: gschem/lib/system-gschemrc.scm:1410
+#, fuzzy
+msgid "Deselect"
+msgstr "Zaznaczanie"
+
+#: gschem/lib/system-gschemrc.scm:1414
msgid "Rotate 90 Mode"
msgstr "ObróÄ? o 90 stopni"
-#: gschem/lib/system-gschemrc.scm:1415
+#: gschem/lib/system-gschemrc.scm:1417
msgid "Edit..."
msgstr "Edytuj..."
-#: gschem/lib/system-gschemrc.scm:1416
+#: gschem/lib/system-gschemrc.scm:1418
msgid "Edit Text..."
msgstr "Edytuj tekst..."
-#: gschem/lib/system-gschemrc.scm:1417
+#: gschem/lib/system-gschemrc.scm:1419
msgid "Slot..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1418
+#: gschem/lib/system-gschemrc.scm:1420
msgid "Color..."
msgstr "Kolor..."
-#: gschem/lib/system-gschemrc.scm:1419
+#: gschem/lib/system-gschemrc.scm:1421
msgid "Line Width & Type..."
msgstr "Styl linii..."
-#: gschem/lib/system-gschemrc.scm:1420
+#: gschem/lib/system-gschemrc.scm:1422
msgid "Fill Type..."
msgstr "Styl wypeÅ?nienia..."
-#: gschem/lib/system-gschemrc.scm:1421
+#: gschem/lib/system-gschemrc.scm:1423
msgid "Symbol Translate..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1425
+#: gschem/lib/system-gschemrc.scm:1427
msgid "Invoke Macro"
msgstr "Wykonaj makro"
-#: gschem/lib/system-gschemrc.scm:1426
+#: gschem/lib/system-gschemrc.scm:1428
msgid "Embed Component/Picture"
msgstr "Osadź element/obraz"
-#: gschem/lib/system-gschemrc.scm:1427
+#: gschem/lib/system-gschemrc.scm:1429
msgid "Unembed Component/Picture"
msgstr "Cofnij osadzanie elem./obr."
-#: gschem/lib/system-gschemrc.scm:1428
+#: gschem/lib/system-gschemrc.scm:1430
msgid "Update Component"
msgstr "Aktualizuj element"
-#: gschem/lib/system-gschemrc.scm:1429
+#: gschem/lib/system-gschemrc.scm:1431
msgid "Show/Hide Inv Text"
msgstr "WyÅ?wietlaj/ukryj niewidoczny tekst"
-#: gschem/lib/system-gschemrc.scm:1430
-msgid "Make Inv Text Vis"
-msgstr "Pokaż niewidoczne atrybuty"
-
-#: gschem/lib/system-gschemrc.scm:1436
+#: gschem/lib/system-gschemrc.scm:1437
msgid "Copy into 1"
msgstr "Kopiuj do 1"
-#: gschem/lib/system-gschemrc.scm:1437
+#: gschem/lib/system-gschemrc.scm:1438
msgid "Copy into 2"
msgstr "Kopiuj do 2"
-#: gschem/lib/system-gschemrc.scm:1438
+#: gschem/lib/system-gschemrc.scm:1439
msgid "Copy into 3"
msgstr "Kopiuj do 3"
-#: gschem/lib/system-gschemrc.scm:1439
+#: gschem/lib/system-gschemrc.scm:1440
msgid "Copy into 4"
msgstr "Kopiuj do 4"
-#: gschem/lib/system-gschemrc.scm:1440
+#: gschem/lib/system-gschemrc.scm:1441
msgid "Copy into 5"
msgstr "Kopiuj do 5"
-#: gschem/lib/system-gschemrc.scm:1441
+#: gschem/lib/system-gschemrc.scm:1442
msgid "Cut into 1"
msgstr "Wytnij do 1"
-#: gschem/lib/system-gschemrc.scm:1442
+#: gschem/lib/system-gschemrc.scm:1443
msgid "Cut into 2"
msgstr "Wytnij do 2"
-#: gschem/lib/system-gschemrc.scm:1443
+#: gschem/lib/system-gschemrc.scm:1444
msgid "Cut into 3"
msgstr "Wytnij do 3"
-#: gschem/lib/system-gschemrc.scm:1444
+#: gschem/lib/system-gschemrc.scm:1445
msgid "Cut into 4"
msgstr "Wytnij do 4"
-#: gschem/lib/system-gschemrc.scm:1445
+#: gschem/lib/system-gschemrc.scm:1446
msgid "Cut into 5"
msgstr "Wytnij do 5"
-#: gschem/lib/system-gschemrc.scm:1446
+#: gschem/lib/system-gschemrc.scm:1447
msgid "Paste from 1"
msgstr "Wklej z 1"
-#: gschem/lib/system-gschemrc.scm:1447
+#: gschem/lib/system-gschemrc.scm:1448
msgid "Paste from 2"
msgstr "Wklej z 2"
-#: gschem/lib/system-gschemrc.scm:1448
+#: gschem/lib/system-gschemrc.scm:1449
msgid "Paste from 3"
msgstr "Wklej z 3"
-#: gschem/lib/system-gschemrc.scm:1449
+#: gschem/lib/system-gschemrc.scm:1450
msgid "Paste from 4"
msgstr "Wklej z 4"
-#: gschem/lib/system-gschemrc.scm:1450
+#: gschem/lib/system-gschemrc.scm:1451
msgid "Paste from 5"
msgstr "Wklej z 5"
-#: gschem/lib/system-gschemrc.scm:1456
+#: gschem/lib/system-gschemrc.scm:1457
msgid "_Redraw"
msgstr "_Aktualizuj"
-#: gschem/lib/system-gschemrc.scm:1457
+#: gschem/lib/system-gschemrc.scm:1458
msgid "_Pan"
msgstr "_PrzesuÅ?"
-#: gschem/lib/system-gschemrc.scm:1458
+#: gschem/lib/system-gschemrc.scm:1459
msgid "Zoom _Box"
msgstr "PowiÄ?ksz _obszar"
-#: gschem/lib/system-gschemrc.scm:1459
+#: gschem/lib/system-gschemrc.scm:1460
msgid "Zoom _Extents"
msgstr "_Dopasuj widok"
-#: gschem/lib/system-gschemrc.scm:1460
+#: gschem/lib/system-gschemrc.scm:1461
msgid "Zoom _In"
msgstr "Pow_iÄ?ksz"
-#: gschem/lib/system-gschemrc.scm:1461
+#: gschem/lib/system-gschemrc.scm:1462
msgid "Zoom _Out"
msgstr "P_omniejsz"
-#: gschem/lib/system-gschemrc.scm:1462
+#: gschem/lib/system-gschemrc.scm:1463
msgid "Zoom _Full"
msgstr "Maksymalne pomniejszenie"
-#: gschem/lib/system-gschemrc.scm:1464
+#: gschem/lib/system-gschemrc.scm:1465
msgid "_Dark color scheme"
msgstr "_Ciemny zestaw kolorów"
-#: gschem/lib/system-gschemrc.scm:1465
+#: gschem/lib/system-gschemrc.scm:1466
msgid "_Light color scheme"
msgstr "_Jasny zestaw kolorów"
-#: gschem/lib/system-gschemrc.scm:1466
+#: gschem/lib/system-gschemrc.scm:1467
#, fuzzy
msgid "B_W color scheme"
msgstr "_Ciemny zestaw kolorów"
-#: gschem/lib/system-gschemrc.scm:1473
+#: gschem/lib/system-gschemrc.scm:1474
msgid "_Manager..."
msgstr "_ZarzÄ?dzaj..."
-#: gschem/lib/system-gschemrc.scm:1474
+#: gschem/lib/system-gschemrc.scm:1475
msgid "_Previous"
msgstr "_Poprzedni"
-#: gschem/lib/system-gschemrc.scm:1475
+#: gschem/lib/system-gschemrc.scm:1476
msgid "_Next"
msgstr "_NastÄ?pny"
-#: gschem/lib/system-gschemrc.scm:1476
+#: gschem/lib/system-gschemrc.scm:1477
msgid "Ne_w"
msgstr "No_wy"
-#: gschem/lib/system-gschemrc.scm:1480
+#: gschem/lib/system-gschemrc.scm:1481
msgid "_Discard"
msgstr "Po_rzuÄ?"
-#: gschem/lib/system-gschemrc.scm:1486
+#: gschem/lib/system-gschemrc.scm:1487
msgid "_Component..."
msgstr "_Element..."
-#: gschem/lib/system-gschemrc.scm:1487
+#: gschem/lib/system-gschemrc.scm:1488
msgid "_Net"
msgstr "_SieÄ?"
-#: gschem/lib/system-gschemrc.scm:1488
+#: gschem/lib/system-gschemrc.scm:1489
msgid "B_us"
msgstr "_Magistrala"
-#: gschem/lib/system-gschemrc.scm:1489
+#: gschem/lib/system-gschemrc.scm:1490
msgid "_Attribute..."
msgstr "_Atrybut..."
-#: gschem/lib/system-gschemrc.scm:1490
+#: gschem/lib/system-gschemrc.scm:1491
msgid "_Text..."
msgstr "_Tekst..."
-#: gschem/lib/system-gschemrc.scm:1492
+#: gschem/lib/system-gschemrc.scm:1493
msgid "_Line"
msgstr "_Linia"
-#: gschem/lib/system-gschemrc.scm:1493
+#: gschem/lib/system-gschemrc.scm:1494
msgid "_Box"
msgstr "Pros_tokÄ?t"
-#: gschem/lib/system-gschemrc.scm:1494
+#: gschem/lib/system-gschemrc.scm:1495
msgid "C_ircle"
msgstr "_OkrÄ?g"
-#: gschem/lib/system-gschemrc.scm:1495
+#: gschem/lib/system-gschemrc.scm:1496
msgid "A_rc"
msgstr "Å?_uk"
-#: gschem/lib/system-gschemrc.scm:1496
+#: gschem/lib/system-gschemrc.scm:1497
msgid "_Pin"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1497
+#: gschem/lib/system-gschemrc.scm:1498
msgid "Pictu_re..."
msgstr "Ob_raz..."
-#: gschem/lib/system-gschemrc.scm:1503
+#: gschem/lib/system-gschemrc.scm:1504
msgid "_Down Schematic"
msgstr "W gÅ?Ä?b _schematu"
-#: gschem/lib/system-gschemrc.scm:1504
+#: gschem/lib/system-gschemrc.scm:1505
msgid "Down _Symbol"
msgstr "W gÅ?Ä?b _elementu"
-#: gschem/lib/system-gschemrc.scm:1505
+#: gschem/lib/system-gschemrc.scm:1506
msgid "_Up"
msgstr "W _górÄ?"
-#: gschem/lib/system-gschemrc.scm:1506
+#: gschem/lib/system-gschemrc.scm:1507
msgid "D_ocumentation..."
msgstr "Do_kumentacja..."
-#: gschem/lib/system-gschemrc.scm:1512
+#: gschem/lib/system-gschemrc.scm:1513
msgid "_Attach"
msgstr "_DoÅ?Ä?cz"
-#: gschem/lib/system-gschemrc.scm:1513
+#: gschem/lib/system-gschemrc.scm:1514
msgid "_Detach"
msgstr "_OdÅ?Ä?cz"
-#: gschem/lib/system-gschemrc.scm:1514
+#: gschem/lib/system-gschemrc.scm:1515
msgid "Show _Value"
msgstr "Pokazuj _wartoÅ?Ä?"
-#: gschem/lib/system-gschemrc.scm:1515
+#: gschem/lib/system-gschemrc.scm:1516
msgid "Show _Name"
msgstr "Pokazuj _nazwÄ?"
-#: gschem/lib/system-gschemrc.scm:1516
+#: gschem/lib/system-gschemrc.scm:1517
msgid "Show _Both"
msgstr "Pokazuj o_bie"
-#: gschem/lib/system-gschemrc.scm:1517
+#: gschem/lib/system-gschemrc.scm:1518
msgid "_Toggle Visibility"
msgstr "PrzeÅ?Ä?cz _widocznoÅ?Ä?"
-#: gschem/lib/system-gschemrc.scm:1519
+#: gschem/lib/system-gschemrc.scm:1520
msgid "_Find Specific Text..."
msgstr "_Szukaj tekstu..."
-#: gschem/lib/system-gschemrc.scm:1520
+#: gschem/lib/system-gschemrc.scm:1521
msgid "_Hide Specific Text..."
msgstr "_Ukryj wybrany tekst..."
-#: gschem/lib/system-gschemrc.scm:1521
+#: gschem/lib/system-gschemrc.scm:1522
msgid "_Show Specific Text..."
msgstr "_Pokazuj wybrany tekst..."
-#: gschem/lib/system-gschemrc.scm:1522
+#: gschem/lib/system-gschemrc.scm:1523
msgid "A_utonumber Text..."
msgstr "A_utomatycznie numeruj..."
-#: gschem/lib/system-gschemrc.scm:1528
+#: gschem/lib/system-gschemrc.scm:1529
msgid "_Text Size..."
msgstr "Rozmiar _tekstu..."
-#: gschem/lib/system-gschemrc.scm:1529
+#: gschem/lib/system-gschemrc.scm:1530
msgid "Cycle _grid styles"
msgstr "PrzeÅ?Ä?cz styl _siatki"
-#: gschem/lib/system-gschemrc.scm:1530
+#: gschem/lib/system-gschemrc.scm:1531
msgid "Toggle _Snap On/Off"
msgstr "PrzeÅ?Ä?cz _przyciÄ?ganie"
-#: gschem/lib/system-gschemrc.scm:1531
+#: gschem/lib/system-gschemrc.scm:1532
msgid "Snap Grid S_pacing..."
msgstr "_OdstÄ?p przyciÄ?gania..."
-#: gschem/lib/system-gschemrc.scm:1532
+#: gschem/lib/system-gschemrc.scm:1533
msgid "Scale _up Grid Spacing"
msgstr "Z_mniejsz siatkÄ? przyciÄ?gania"
-#: gschem/lib/system-gschemrc.scm:1534
+#: gschem/lib/system-gschemrc.scm:1535
msgid "Scale _down Grid Spacing"
msgstr "Z_wiÄ?ksz siatkÄ? przyciÄ?gania"
-#: gschem/lib/system-gschemrc.scm:1536
+#: gschem/lib/system-gschemrc.scm:1537
msgid "Toggle _Outline/Box"
msgstr "PrzeÅ?Ä?cz wyÅ?wietlanie _konturów"
-#: gschem/lib/system-gschemrc.scm:1538
+#: gschem/lib/system-gschemrc.scm:1539
msgid "Toggle Net _Rubberband"
msgstr "PrzeÅ?Ä?cz _rozciÄ?ganie poÅ?Ä?czeÅ?"
-#: gschem/lib/system-gschemrc.scm:1539
+#: gschem/lib/system-gschemrc.scm:1540
msgid "Toggle _Magnetic Net"
msgstr "PrzeÅ?Ä?cz \"_magnes\" poÅ?Ä?czeÅ?"
-#: gschem/lib/system-gschemrc.scm:1540
+#: gschem/lib/system-gschemrc.scm:1541
msgid "Show _Log Window..."
msgstr "Pokaż okno komunikatów..."
-#: gschem/lib/system-gschemrc.scm:1542
+#: gschem/lib/system-gschemrc.scm:1543
msgid "Show _Coord Window..."
msgstr "Pokaż okno wspóÅ?rzÄ?dnych..."
-#: gschem/lib/system-gschemrc.scm:1558
+#: gschem/lib/system-gschemrc.scm:1559
msgid "gEDA Docu_mentation..."
msgstr "Doku_mentacja gEDA..."
-#: gschem/lib/system-gschemrc.scm:1559
+#: gschem/lib/system-gschemrc.scm:1560
msgid "gschem _FAQ..."
msgstr "_FAQ gschem..."
-#: gschem/lib/system-gschemrc.scm:1560
+#: gschem/lib/system-gschemrc.scm:1561
msgid "gEDA _Wiki..."
msgstr "_Wiki gEDA..."
-#: gschem/lib/system-gschemrc.scm:1561
+#: gschem/lib/system-gschemrc.scm:1562
msgid "Component D_ocumentation..."
msgstr "Dokumentacja _elementu..."
-#: gschem/lib/system-gschemrc.scm:1563
+#: gschem/lib/system-gschemrc.scm:1564
msgid "_Hotkeys..."
msgstr "Skróty _klawiszowe..."
-#: gschem/lib/system-gschemrc.scm:1564
+#: gschem/lib/system-gschemrc.scm:1565
msgid "_About..."
msgstr "_O programie..."
-#: gschem/lib/system-gschemrc.scm:1570
+#: gschem/lib/system-gschemrc.scm:1571
msgid "_File"
msgstr "_Plik"
-#: gschem/lib/system-gschemrc.scm:1571
+#: gschem/lib/system-gschemrc.scm:1572
msgid "_Edit"
msgstr "_Edycja"
-#: gschem/lib/system-gschemrc.scm:1572
+#: gschem/lib/system-gschemrc.scm:1573
msgid "_Buffer"
msgstr "_Schowek"
-#: gschem/lib/system-gschemrc.scm:1573
+#: gschem/lib/system-gschemrc.scm:1574
msgid "_View"
msgstr "_Widok"
-#: gschem/lib/system-gschemrc.scm:1574
+#: gschem/lib/system-gschemrc.scm:1575
msgid "_Page"
msgstr "_Arkusz"
-#: gschem/lib/system-gschemrc.scm:1575
+#: gschem/lib/system-gschemrc.scm:1576
msgid "_Add"
msgstr "_Dodaj"
-#: gschem/lib/system-gschemrc.scm:1576
+#: gschem/lib/system-gschemrc.scm:1577
msgid "Hie_rarchy"
msgstr "Hie_rarchia"
-#: gschem/lib/system-gschemrc.scm:1577
+#: gschem/lib/system-gschemrc.scm:1578
msgid "A_ttributes"
msgstr "A_trybuty"
-#: gschem/lib/system-gschemrc.scm:1578
+#: gschem/lib/system-gschemrc.scm:1579
msgid "_Options"
msgstr "_Ustawienia"
-#: gschem/lib/system-gschemrc.scm:1579
+#: gschem/lib/system-gschemrc.scm:1580
msgid "_Help"
msgstr "_Pomoc"
+#~ msgid "Scheme directory NOT set!\n"
+#~ msgstr "Nie podano katalogu programu Scheme!\n"
+
+#~ msgid "MakeVisible"
+#~ msgstr "Ustaw jako widoczne"
+
+#~ msgid ""
+#~ "Usage: %s [OPTIONS] schematic_filename1 ... schematic_filenameN\n"
+#~ " -q Quiet mode\n"
+#~ " -v Verbose mode on\n"
+#~ " -r filename Rc filename\n"
+#~ " -s filename Script (guile) filename\n"
+#~ " -o filename Output filename (for printing)\n"
+#~ " -p Automatically place the window\n"
+#~ " -t Print stroke information\n"
+#~ " -h Help; this message\n"
+#~ "\n"
+#~ msgstr ""
+#~ "SkÅ?adnia: %s [OPCJE] plik_schematu1 ... plik_schematuN\n"
+#~ " -q Tryb cichy\n"
+#~ " -v Tryb gadatliwy\n"
+#~ " -r plik Plik konfiguracji\n"
+#~ " -s plik Plik skryptu (guile)\n"
+#~ " -o plik Plik do zapisu wyników wydruku\n"
+#~ " -p Automatyczne rozmieszczanie okien\n"
+#~ " -t Wypisuj informacje o stylach linii\n"
+#~ " -h Pomoc; ten komunikat\n"
+#~ "\n"
+
+#~ msgid "Couldn't open file %s\n"
+#~ msgstr "Otwieranie pliku %s nie powiodÅ?o siÄ?\n"
+
+#~ msgid "Clear"
+#~ msgstr "WyczyÅ?Ä?"
+
+#~ msgid "Make Inv Text Vis"
+#~ msgstr "Pokaż niewidoczne atrybuty"
+
#~ msgid "About..."
#~ msgstr "O programie..."
diff --git a/gschem/po/pt.po b/gschem/po/pt.po
index e01018e..734e87c 100644
--- a/gschem/po/pt.po
+++ b/gschem/po/pt.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2010-11-07 13:37+0000\n"
+"POT-Creation-Date: 2011-01-16 00:11-0500\n"
"PO-Revision-Date: 2010-02-11 02:58+0000\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -22,17 +22,17 @@ msgstr ""
msgid "Zoom too small! Cannot zoom further.\n"
msgstr ""
-#: gschem/src/g_funcs.c:339 gschem/src/i_callbacks.c:68
+#: gschem/src/g_funcs.c:347 gschem/src/i_callbacks.c:68
#, c-format
msgid "Could not fork\n"
msgstr ""
-#: gschem/src/g_funcs.c:355 gschem/src/i_callbacks.c:78
+#: gschem/src/g_funcs.c:363 gschem/src/i_callbacks.c:78
#, c-format
msgid "Could not invoke %s\n"
msgstr ""
-#: gschem/src/g_funcs.c:361 gschem/src/i_callbacks.c:82
+#: gschem/src/g_funcs.c:369 gschem/src/i_callbacks.c:82
msgid "Documentation commands not supported under MinGW.\n"
msgstr ""
@@ -121,39 +121,39 @@ msgstr ""
msgid "Invalid number of steps [%d] scrollpan-steps\n"
msgstr ""
-#: gschem/src/gschem.c:184
+#: gschem/src/gschem.c:188
#, c-format
msgid "gEDA/gschem version %s%s.%s\n"
msgstr "gEDA/gschem versão %s%s.%s\n"
-#: gschem/src/gschem.c:187
+#: gschem/src/gschem.c:191
msgid ""
"gEDA/gschem comes with ABSOLUTELY NO WARRANTY; see COPYING for more "
"details.\n"
msgstr ""
-#: gschem/src/gschem.c:189
+#: gschem/src/gschem.c:193
msgid ""
"This is free software, and you are welcome to redistribute it under certain\n"
msgstr ""
-#: gschem/src/gschem.c:191
+#: gschem/src/gschem.c:195
msgid ""
"conditions; please see the COPYING file for more details.\n"
"\n"
msgstr ""
-#: gschem/src/gschem.c:194
+#: gschem/src/gschem.c:198
#, c-format
msgid "This is the MINGW32 port.\n"
msgstr ""
-#: gschem/src/gschem.c:198
+#: gschem/src/gschem.c:202
#, c-format
msgid "Current locale settings: %s\n"
msgstr ""
-#: gschem/src/gschem.c:213
+#: gschem/src/gschem.c:218
msgid ""
"You must set the GEDADATA environment variable!\n"
"\n"
@@ -161,31 +161,21 @@ msgid ""
"environment variable to point to the correct location.\n"
msgstr ""
-#: gschem/src/gschem.c:248
+#: gschem/src/gschem.c:256
#, c-format
msgid "Couldn't find init scm file [%s]\n"
msgstr ""
-#: gschem/src/gschem.c:252
+#: gschem/src/gschem.c:260
#, c-format
msgid "Read init scm file [%s]\n"
msgstr ""
-#: gschem/src/gschem.c:256
+#: gschem/src/gschem.c:264
#, c-format
msgid "Failed to read init scm file [%s]\n"
msgstr ""
-#: gschem/src/gschem.c:317
-#, c-format
-msgid "Scheme directory NOT set!\n"
-msgstr ""
-
-#: gschem/src/gschem.c:324 gschem/src/x_script.c:66
-#, c-format
-msgid "Executing guile script [%s]\n"
-msgstr ""
-
#: gschem/src/gschem_cairo.c:310
#, c-format
msgid "Unknown end for line (%d)\n"
@@ -209,11 +199,11 @@ msgstr ""
msgid "Text Mode"
msgstr "Modo de texto"
-#: gschem/src/i_basic.c:84 gschem/lib/system-gschemrc.scm:1409
+#: gschem/src/i_basic.c:84 gschem/lib/system-gschemrc.scm:1411
msgid "Copy Mode"
msgstr "Modo de Cópia"
-#: gschem/src/i_basic.c:87 gschem/lib/system-gschemrc.scm:1411
+#: gschem/src/i_basic.c:87 gschem/lib/system-gschemrc.scm:1413
msgid "Move Mode"
msgstr "Modo de Movimentação"
@@ -221,7 +211,7 @@ msgstr "Modo de Movimentação"
msgid "Rotate Mode"
msgstr "Modo de Rotação"
-#: gschem/src/i_basic.c:91 gschem/lib/system-gschemrc.scm:1413
+#: gschem/src/i_basic.c:91 gschem/lib/system-gschemrc.scm:1415
msgid "Mirror Mode"
msgstr ""
@@ -274,22 +264,22 @@ msgstr "Modo de Arco"
msgid "Pin Mode"
msgstr "Modo de Pino"
-#: gschem/src/i_basic.c:135 gschem/src/i_callbacks.c:544
-#: gschem/src/i_callbacks.c:568
+#: gschem/src/i_basic.c:135 gschem/src/i_callbacks.c:576
+#: gschem/src/i_callbacks.c:600
msgid "Copy"
msgstr "Copiar"
-#: gschem/src/i_basic.c:137 gschem/src/i_callbacks.c:634
-#: gschem/src/i_callbacks.c:658
+#: gschem/src/i_basic.c:137 gschem/src/i_callbacks.c:666
+#: gschem/src/i_callbacks.c:690
msgid "Move"
msgstr "Mover"
-#: gschem/src/i_basic.c:139 gschem/src/i_callbacks.c:589
-#: gschem/src/i_callbacks.c:613
+#: gschem/src/i_basic.c:139 gschem/src/i_callbacks.c:621
+#: gschem/src/i_callbacks.c:645
msgid "Multiple Copy"
msgstr "Cópia Múltipla"
-#: gschem/src/i_basic.c:142 gschem/lib/system-gschemrc.scm:1410
+#: gschem/src/i_basic.c:142 gschem/lib/system-gschemrc.scm:1412
msgid "Multiple Copy Mode"
msgstr "Modo de Cópia Múltiplo"
@@ -309,7 +299,7 @@ msgstr ""
msgid "Action"
msgstr "Acção"
-#: gschem/src/i_basic.c:260 gschem/src/x_dialog.c:2312
+#: gschem/src/i_basic.c:260 gschem/src/x_dialog.c:2316
#: gschem/src/x_window.c:491
msgid "Stroke"
msgstr ""
@@ -340,7 +330,7 @@ msgstr ""
msgid "Documentation for [%s,%s,%s,%s]\n"
msgstr ""
-#: gschem/src/i_callbacks.c:123 gschem/src/i_callbacks.c:1699
+#: gschem/src/i_callbacks.c:123 gschem/src/i_callbacks.c:1706
#, c-format
msgid "New page created [%s]\n"
msgstr ""
@@ -362,327 +352,323 @@ msgstr ""
msgid "Closing Window\n"
msgstr ""
-#: gschem/src/i_callbacks.c:549 gschem/src/i_callbacks.c:594
-#: gschem/src/i_callbacks.c:639
+#: gschem/src/i_callbacks.c:581 gschem/src/i_callbacks.c:626
+#: gschem/src/i_callbacks.c:671
msgid "Select objs first"
msgstr ""
-#: gschem/src/i_callbacks.c:678 gschem/src/x_multiattrib.c:1491
+#: gschem/src/i_callbacks.c:710 gschem/src/x_multiattrib.c:1503
msgid "Delete"
msgstr "Apagar"
-#: gschem/src/i_callbacks.c:703
+#: gschem/src/i_callbacks.c:735
msgid "Edit"
msgstr "Editar"
-#: gschem/src/i_callbacks.c:718
+#: gschem/src/i_callbacks.c:750
msgid "Edit pin type"
msgstr ""
-#: gschem/src/i_callbacks.c:737
+#: gschem/src/i_callbacks.c:769
msgid "Edit Text"
msgstr ""
-#: gschem/src/i_callbacks.c:760
+#: gschem/src/i_callbacks.c:792
msgid "Slot"
msgstr ""
-#: gschem/src/i_callbacks.c:777
+#: gschem/src/i_callbacks.c:809
msgid "Color"
msgstr ""
-#: gschem/src/i_callbacks.c:814 gschem/src/i_callbacks.c:859
+#: gschem/src/i_callbacks.c:846 gschem/src/i_callbacks.c:891
msgid "Rotate"
msgstr ""
-#: gschem/src/i_callbacks.c:882 gschem/src/i_callbacks.c:907
+#: gschem/src/i_callbacks.c:913 gschem/src/i_callbacks.c:938
msgid "Mirror"
msgstr ""
-#: gschem/src/i_callbacks.c:928 gschem/src/x_dialog.c:2315
-#: gschem/lib/system-gschemrc.scm:1422
+#: gschem/src/i_callbacks.c:959 gschem/src/x_dialog.c:2319
+#: gschem/lib/system-gschemrc.scm:1424
msgid "Lock"
msgstr "Trancar"
-#: gschem/src/i_callbacks.c:946 gschem/lib/system-gschemrc.scm:1423
+#: gschem/src/i_callbacks.c:977 gschem/lib/system-gschemrc.scm:1425
msgid "Unlock"
msgstr "Destrancar"
-#: gschem/src/i_callbacks.c:964 gschem/src/x_dialog.c:1734
+#: gschem/src/i_callbacks.c:995 gschem/src/x_dialog.c:1737
msgid "Translate"
msgstr ""
-#: gschem/src/i_callbacks.c:967
+#: gschem/src/i_callbacks.c:998
msgid "WARNING: Do not translate with snap off!\n"
msgstr ""
-#: gschem/src/i_callbacks.c:968
+#: gschem/src/i_callbacks.c:999
msgid "WARNING: Turning snap on and continuing with translate.\n"
msgstr ""
-#: gschem/src/i_callbacks.c:975
+#: gschem/src/i_callbacks.c:1006
msgid "WARNING: Snap grid size is not equal to 100!\n"
msgstr ""
-#: gschem/src/i_callbacks.c:977
+#: gschem/src/i_callbacks.c:1008
msgid ""
"WARNING: If you are translating a symbol to the origin, the snap grid size "
"should be set to 100\n"
msgstr ""
-#: gschem/src/i_callbacks.c:1008
+#: gschem/src/i_callbacks.c:1039
msgid "Embed"
msgstr ""
-#: gschem/src/i_callbacks.c:1047
+#: gschem/src/i_callbacks.c:1078
msgid "Unembed"
msgstr ""
-#: gschem/src/i_callbacks.c:1089
+#: gschem/src/i_callbacks.c:1120
msgid "Update"
msgstr ""
-#: gschem/src/i_callbacks.c:1136
+#: gschem/src/i_callbacks.c:1167
msgid "ShowHidden"
msgstr ""
-#: gschem/src/i_callbacks.c:1160
-msgid "MakeVisible"
-msgstr ""
-
-#: gschem/src/i_callbacks.c:1466 gschem/src/i_callbacks.c:1538
+#: gschem/src/i_callbacks.c:1473 gschem/src/i_callbacks.c:1545
msgid "Pan"
msgstr ""
-#: gschem/src/i_callbacks.c:1743
+#: gschem/src/i_callbacks.c:1750
msgid "Really revert page?"
msgstr ""
-#: gschem/src/i_callbacks.c:1813
+#: gschem/src/i_callbacks.c:1820
msgid "Copy to clipboard"
msgstr ""
-#: gschem/src/i_callbacks.c:1831
+#: gschem/src/i_callbacks.c:1838
msgid "Cut to clipboard"
msgstr ""
-#: gschem/src/i_callbacks.c:1849
+#: gschem/src/i_callbacks.c:1856
msgid "Paste from clipboard"
msgstr ""
-#: gschem/src/i_callbacks.c:1861 gschem/src/i_callbacks.c:2100
-#: gschem/src/i_callbacks.c:2122 gschem/src/i_callbacks.c:2144
-#: gschem/src/i_callbacks.c:2166 gschem/src/i_callbacks.c:2188
+#: gschem/src/i_callbacks.c:1868 gschem/src/i_callbacks.c:2107
+#: gschem/src/i_callbacks.c:2129 gschem/src/i_callbacks.c:2151
+#: gschem/src/i_callbacks.c:2173 gschem/src/i_callbacks.c:2195
msgid "Empty buffer"
msgstr ""
-#: gschem/src/i_callbacks.c:1906
+#: gschem/src/i_callbacks.c:1913
msgid "Copy 1"
msgstr ""
-#: gschem/src/i_callbacks.c:1925
+#: gschem/src/i_callbacks.c:1932
msgid "Copy 2"
msgstr ""
-#: gschem/src/i_callbacks.c:1944
+#: gschem/src/i_callbacks.c:1951
msgid "Copy 3"
msgstr ""
-#: gschem/src/i_callbacks.c:1963
+#: gschem/src/i_callbacks.c:1970
msgid "Copy 4"
msgstr ""
-#: gschem/src/i_callbacks.c:1982
+#: gschem/src/i_callbacks.c:1989
msgid "Copy 5"
msgstr ""
-#: gschem/src/i_callbacks.c:2001
+#: gschem/src/i_callbacks.c:2008
msgid "Cut 1"
msgstr ""
-#: gschem/src/i_callbacks.c:2020
+#: gschem/src/i_callbacks.c:2027
msgid "Cut 2"
msgstr ""
-#: gschem/src/i_callbacks.c:2039
+#: gschem/src/i_callbacks.c:2046
msgid "Cut 3"
msgstr ""
-#: gschem/src/i_callbacks.c:2058
+#: gschem/src/i_callbacks.c:2065
msgid "Cut 4"
msgstr ""
-#: gschem/src/i_callbacks.c:2077
+#: gschem/src/i_callbacks.c:2084
msgid "Cut 5"
msgstr ""
-#: gschem/src/i_callbacks.c:2093
+#: gschem/src/i_callbacks.c:2100
msgid "Paste 1"
msgstr ""
-#: gschem/src/i_callbacks.c:2115
+#: gschem/src/i_callbacks.c:2122
msgid "Paste 2"
msgstr ""
-#: gschem/src/i_callbacks.c:2137
+#: gschem/src/i_callbacks.c:2144
msgid "Paste 3"
msgstr ""
-#: gschem/src/i_callbacks.c:2159
+#: gschem/src/i_callbacks.c:2166
msgid "Paste 4"
msgstr ""
-#: gschem/src/i_callbacks.c:2181
+#: gschem/src/i_callbacks.c:2188
msgid "Paste 5"
msgstr ""
-#: gschem/src/i_callbacks.c:2318 gschem/src/x_window.c:355
+#: gschem/src/i_callbacks.c:2325 gschem/src/x_window.c:355
msgid "Component"
msgstr ""
-#: gschem/src/i_callbacks.c:2354 gschem/src/i_callbacks.c:2373
-#: gschem/src/x_dialog.c:2285
+#: gschem/src/i_callbacks.c:2361 gschem/src/i_callbacks.c:2380
+#: gschem/src/x_dialog.c:2289
msgid "Attribute"
msgstr ""
-#: gschem/src/i_callbacks.c:2395 gschem/src/i_callbacks.c:2422
-#: gschem/src/x_dialog.c:2282
+#: gschem/src/i_callbacks.c:2402 gschem/src/i_callbacks.c:2429
+#: gschem/src/x_dialog.c:2286
msgid "Net"
msgstr "Net"
-#: gschem/src/i_callbacks.c:2466 gschem/src/i_callbacks.c:2493
-#: gschem/src/x_dialog.c:2300 gschem/src/x_window.c:375
+#: gschem/src/i_callbacks.c:2473 gschem/src/i_callbacks.c:2500
+#: gschem/src/x_dialog.c:2304 gschem/src/x_window.c:375
msgid "Bus"
msgstr "Barramento"
-#: gschem/src/i_callbacks.c:2574 gschem/src/i_callbacks.c:2597
+#: gschem/src/i_callbacks.c:2581 gschem/src/i_callbacks.c:2604
msgid "Line"
msgstr "Linha"
-#: gschem/src/i_callbacks.c:2619 gschem/src/i_callbacks.c:2642
+#: gschem/src/i_callbacks.c:2626 gschem/src/i_callbacks.c:2649
msgid "Box"
msgstr "Caixa"
-#: gschem/src/i_callbacks.c:2698 gschem/src/i_callbacks.c:2722
+#: gschem/src/i_callbacks.c:2705 gschem/src/i_callbacks.c:2729
msgid "Circle"
msgstr "CÃrculo"
-#: gschem/src/i_callbacks.c:2744 gschem/src/i_callbacks.c:2767
+#: gschem/src/i_callbacks.c:2751 gschem/src/i_callbacks.c:2774
msgid "Arc"
msgstr "Arco"
-#: gschem/src/i_callbacks.c:2789 gschem/src/i_callbacks.c:2812
-#: gschem/src/x_dialog.c:2273
+#: gschem/src/i_callbacks.c:2796 gschem/src/i_callbacks.c:2819
+#: gschem/src/x_dialog.c:2277
msgid "Pin"
msgstr "Pino"
-#: gschem/src/i_callbacks.c:2871
+#: gschem/src/i_callbacks.c:2878
#, c-format
msgid "Searching for source [%s]\n"
msgstr ""
-#: gschem/src/i_callbacks.c:2895
+#: gschem/src/i_callbacks.c:2902
#, c-format
msgid "Cannot find source [%s]\n"
msgstr ""
-#: gschem/src/i_callbacks.c:2964
+#: gschem/src/i_callbacks.c:2965
#, c-format
msgid "Searching for symbol [%s]\n"
msgstr ""
-#: gschem/src/i_callbacks.c:2970
+#: gschem/src/i_callbacks.c:2971
msgid "Symbol is not a real file. Symbol cannot be loaded.\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3001
+#: gschem/src/i_callbacks.c:3002
msgid "Cannot find any schematics above the current one!\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3055
+#: gschem/src/i_callbacks.c:3056
msgid ""
"This command retrieves the component documentation from the web, but there "
"is no component selected"
msgstr ""
-#: gschem/src/i_callbacks.c:3083
+#: gschem/src/i_callbacks.c:3084
msgid "Attach"
msgstr "Anexar"
-#: gschem/src/i_callbacks.c:3130
+#: gschem/src/i_callbacks.c:3131
msgid "Detach"
msgstr "Desanexar"
-#: gschem/src/i_callbacks.c:3165
+#: gschem/src/i_callbacks.c:3166
msgid "ShowN"
msgstr ""
-#: gschem/src/i_callbacks.c:3201
+#: gschem/src/i_callbacks.c:3202
msgid "ShowV"
msgstr ""
-#: gschem/src/i_callbacks.c:3237
+#: gschem/src/i_callbacks.c:3238
msgid "ShowB"
msgstr ""
-#: gschem/src/i_callbacks.c:3274
+#: gschem/src/i_callbacks.c:3275
msgid "VisToggle"
msgstr ""
-#: gschem/src/i_callbacks.c:3304
+#: gschem/src/i_callbacks.c:3305
#, c-format
msgid "Sorry but this is a non-functioning menu option\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3394
+#: gschem/src/i_callbacks.c:3395
msgid "Action feedback mode set to OUTLINE\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3397
+#: gschem/src/i_callbacks.c:3398
msgid "Action feedback mode set to BOUNDINGBOX\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3422
+#: gschem/src/i_callbacks.c:3423
msgid "Grid OFF\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3423
+#: gschem/src/i_callbacks.c:3424
msgid "Dot grid selected\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3424
+#: gschem/src/i_callbacks.c:3425
msgid "Mesh grid selected\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3445
+#: gschem/src/i_callbacks.c:3446
msgid "Snap OFF (CAUTION!)\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3448
+#: gschem/src/i_callbacks.c:3449
msgid "Snap ON\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3451
+#: gschem/src/i_callbacks.c:3452
msgid "Snap back to the grid (CAUTION!)\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3477
+#: gschem/src/i_callbacks.c:3478
msgid "Rubber band OFF \n"
msgstr ""
-#: gschem/src/i_callbacks.c:3480
+#: gschem/src/i_callbacks.c:3481
msgid "Rubber band ON\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3495
+#: gschem/src/i_callbacks.c:3496
msgid "magnetic net mode: ON\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3498
+#: gschem/src/i_callbacks.c:3499
msgid "magnetic net mode: OFF\n"
msgstr ""
-#: gschem/src/o_box.c:153
+#: gschem/src/o_box.c:149
#, c-format
msgid "Unknown type for box (fill)!\n"
msgstr ""
@@ -702,17 +688,17 @@ msgstr ""
msgid "Got an invalid buffer_number [o_buffer_paste_start]\n"
msgstr ""
-#: gschem/src/o_bus.c:118
+#: gschem/src/o_bus.c:117
#, c-format
msgid "Got an invalid which one in o_bus_draw_stretch\n"
msgstr ""
-#: gschem/src/o_circle.c:134
+#: gschem/src/o_circle.c:130
#, c-format
msgid "Unknown type for circle (fill)!\n"
msgstr ""
-#: gschem/src/o_complex.c:243 gschem/src/o_complex.c:247
+#: gschem/src/o_complex.c:237 gschem/src/o_complex.c:241
#, c-format
msgid "Translating schematic [%d %d]\n"
msgstr ""
@@ -730,35 +716,35 @@ msgstr ""
msgid "Object already unlocked\n"
msgstr ""
-#: gschem/src/o_misc.c:413
+#: gschem/src/o_misc.c:409
msgid "Hidden text is now visible\n"
msgstr ""
-#: gschem/src/o_misc.c:415
+#: gschem/src/o_misc.c:411
msgid "Hidden text is now invisible\n"
msgstr ""
-#: gschem/src/o_misc.c:668
+#: gschem/src/o_misc.c:636
#, c-format
msgid "Could not find symbol [%s] in library. Update failed.\n"
msgstr ""
-#: gschem/src/o_misc.c:783
+#: gschem/src/o_misc.c:751
#, c-format
msgid "o_autosave_backups: Can't get the real filename of %s."
msgstr ""
-#: gschem/src/o_misc.c:827
+#: gschem/src/o_misc.c:795
#, c-format
msgid "Could NOT set previous backup file [%s] read-write\n"
msgstr ""
-#: gschem/src/o_misc.c:845
+#: gschem/src/o_misc.c:815
#, c-format
msgid "Could NOT set backup file [%s] readonly\n"
msgstr ""
-#: gschem/src/o_misc.c:850
+#: gschem/src/o_misc.c:820
#, c-format
msgid "Could NOT save backup file [%s]\n"
msgstr ""
@@ -778,36 +764,36 @@ msgstr ""
msgid "Got a non line object in o_move_check_endpoint\n"
msgstr ""
-#: gschem/src/o_net.c:159
+#: gschem/src/o_net.c:158
#, c-format
msgid "Got an invalid which one in o_net_draw_stretch\n"
msgstr ""
-#: gschem/src/o_net.c:538
+#: gschem/src/o_net.c:537
msgid "Warning: Starting net at off grid coordinate\n"
msgstr ""
-#: gschem/src/o_net.c:600
+#: gschem/src/o_net.c:599
msgid "Warning: Ending net at off grid coordinate\n"
msgstr ""
-#: gschem/src/o_net.c:932 gschem/src/o_net.c:969 gschem/src/o_net.c:1040
-#: gschem/src/o_net.c:1076
+#: gschem/src/o_net.c:931 gschem/src/o_net.c:968 gschem/src/o_net.c:1039
+#: gschem/src/o_net.c:1075
#, c-format
msgid "Tried to add more than two bus rippers. Internal gschem error.\n"
msgstr ""
-#: gschem/src/o_net.c:1144
+#: gschem/src/o_net.c:1143
#, c-format
msgid "Bus ripper symbol [%s] was not found in any component library\n"
msgstr ""
-#: gschem/src/o_path.c:352
+#: gschem/src/o_path.c:348
#, c-format
msgid "Unknown type for path (fill)!\n"
msgstr ""
-#: gschem/src/o_picture.c:163 gschem/src/o_picture.c:539
+#: gschem/src/o_picture.c:163 gschem/src/o_picture.c:537
#, c-format
msgid "Failed to load picture: %s"
msgstr ""
@@ -816,7 +802,7 @@ msgstr ""
msgid "Picture"
msgstr ""
-#: gschem/src/o_picture.c:447 gschem/src/x_attribedit.c:141
+#: gschem/src/o_picture.c:445 gschem/src/x_attribedit.c:141
#, c-format
msgid "ERROR: NULL object!\n"
msgstr ""
@@ -837,23 +823,45 @@ msgstr ""
msgid "New slot number out of range\n"
msgstr ""
-#: gschem/src/o_undo.c:304
+#: gschem/src/o_undo.c:303
msgid "Undo/Redo disabled in rc file\n"
msgstr ""
-#: gschem/src/parsecmd.c:47
+#: gschem/src/parsecmd.c:81
#, c-format
msgid ""
-"Usage: %s [OPTIONS] schematic_filename1 ... schematic_filenameN\n"
-" -q Quiet mode\n"
-" -v Verbose mode on\n"
-" -r filename Rc filename\n"
-" -s filename Script (guile) filename\n"
-" -o filename Output filename (for printing)\n"
-" -p Automatically place the window\n"
-" -t Print stroke information\n"
-" -h Help; this message\n"
+"Usage: %s [OPTION ...] [--] [FILE ...]\n"
+"\n"
+"Interactively edit gEDA schematics or symbols. If one or more FILEs\n"
+"are specified, open them for editing; otherwise, create a new, empty\n"
+"schematic.\n"
+"\n"
+"Options:\n"
+" -q, --quiet Quiet mode.\n"
+" -v, --verbose Verbose mode.\n"
+" -r, --config-file=FILE Additional configuration file to load.\n"
+" -L DIR Add DIR to Scheme search path.\n"
+" -c EXPR Scheme expression to run at startup.\n"
+" -s FILE Scheme script to run at startup.\n"
+" -o, --output=FILE Output filename (for printing).\n"
+" -p Automatically place the window.\n"
+" -V, --version Show version information.\n"
+" -h, --help Help; this message.\n"
+" -- Treat all remaining arguments as filenames.\n"
"\n"
+"Report bugs to <geda-bug@xxxxxxxx>\n"
+"gEDA/gaf homepage: <http://gpleda.org>\n"
+msgstr ""
+
+#: gschem/src/parsecmd.c:115
+#, c-format
+msgid ""
+"gEDA %s (g%.7s)\n"
+"Copyright (C) 1998-2011 gEDA developers\n"
+"This is free software, and you are welcome to redistribute it under\n"
+"certain conditions. For details, see the file `COPYING', which is\n"
+"included in the gEDA distribution.\n"
+"There is NO WARRANTY, to the extent permitted by law.\n"
msgstr ""
#: gschem/src/x_attribedit.c:127
@@ -865,56 +873,56 @@ msgstr ""
msgid "Single Attribute Editor"
msgstr ""
-#: gschem/src/x_attribedit.c:358
+#: gschem/src/x_attribedit.c:359
msgid "<b>Edit Attribute</b>"
msgstr ""
-#: gschem/src/x_attribedit.c:360
+#: gschem/src/x_attribedit.c:361
msgid "<b>Add Attribute</b>"
msgstr ""
-#: gschem/src/x_attribedit.c:376 gschem/src/x_multiattrib.c:1916
+#: gschem/src/x_attribedit.c:377 gschem/src/x_multiattrib.c:1927
msgid "Name:"
msgstr ""
-#: gschem/src/x_attribedit.c:393 gschem/src/x_multiattrib.c:1935
+#: gschem/src/x_attribedit.c:394 gschem/src/x_multiattrib.c:1946
msgid "Value:"
msgstr ""
-#: gschem/src/x_attribedit.c:409 gschem/src/x_multiattrib.c:1978
+#: gschem/src/x_attribedit.c:410 gschem/src/x_multiattrib.c:1989
msgid "Visible"
msgstr ""
-#: gschem/src/x_attribedit.c:429
+#: gschem/src/x_attribedit.c:430
msgid "Show Value Only"
msgstr ""
-#: gschem/src/x_attribedit.c:431
+#: gschem/src/x_attribedit.c:432
msgid "Show Name Only"
msgstr ""
-#: gschem/src/x_attribedit.c:433 gschem/src/x_multiattrib.c:1454
+#: gschem/src/x_attribedit.c:434 gschem/src/x_multiattrib.c:1466
msgid "Show Name & Value"
msgstr ""
-#: gschem/src/x_attribedit.c:440
+#: gschem/src/x_attribedit.c:441
msgid "<b>Attach Options</b>"
msgstr ""
-#: gschem/src/x_attribedit.c:455
+#: gschem/src/x_attribedit.c:456
msgid "All"
msgstr ""
-#: gschem/src/x_attribedit.c:463 gschem/src/x_compselect.c:896
-#: gschem/src/x_compselect.c:1010
+#: gschem/src/x_attribedit.c:464 gschem/src/x_compselect.c:904
+#: gschem/src/x_compselect.c:1018
msgid "Components"
msgstr ""
-#: gschem/src/x_attribedit.c:471 gschem/src/x_window.c:365
+#: gschem/src/x_attribedit.c:472 gschem/src/x_window.c:365
msgid "Nets"
msgstr ""
-#: gschem/src/x_attribedit.c:479
+#: gschem/src/x_attribedit.c:480
msgid "Replace existing attributes"
msgstr ""
@@ -930,91 +938,91 @@ msgid ""
"duplicate slot may cause problems: [symbolname=%s, number=%d, slot=%d]\n"
msgstr ""
-#: gschem/src/x_autonumber.c:673
+#: gschem/src/x_autonumber.c:675
msgid "No searchstring given in autonumber text.\n"
msgstr ""
-#: gschem/src/x_autonumber.c:725
+#: gschem/src/x_autonumber.c:727
msgid "No '*' or '?' given at the end of the autonumber text.\n"
msgstr ""
-#: gschem/src/x_autonumber.c:860
+#: gschem/src/x_autonumber.c:862
msgid "Diagonal"
msgstr ""
-#: gschem/src/x_autonumber.c:861
+#: gschem/src/x_autonumber.c:863
msgid "Top to bottom"
msgstr ""
-#: gschem/src/x_autonumber.c:861
+#: gschem/src/x_autonumber.c:863
msgid "Bottom to top"
msgstr ""
-#: gschem/src/x_autonumber.c:862
+#: gschem/src/x_autonumber.c:864
msgid "Left to right"
msgstr ""
-#: gschem/src/x_autonumber.c:862
+#: gschem/src/x_autonumber.c:864
msgid "Right to left"
msgstr ""
-#: gschem/src/x_autonumber.c:863
+#: gschem/src/x_autonumber.c:865
msgid "File order"
msgstr ""
-#: gschem/src/x_autonumber.c:1199
+#: gschem/src/x_autonumber.c:1201
msgid "Autonumber text"
msgstr ""
-#: gschem/src/x_autonumber.c:1223
+#: gschem/src/x_autonumber.c:1225
msgid "<b>Scope</b>"
msgstr ""
-#: gschem/src/x_autonumber.c:1245
+#: gschem/src/x_autonumber.c:1247
msgid "Search for:"
msgstr ""
-#: gschem/src/x_autonumber.c:1259
+#: gschem/src/x_autonumber.c:1261
msgid "Autonumber text in:"
msgstr ""
-#: gschem/src/x_autonumber.c:1266
+#: gschem/src/x_autonumber.c:1268
msgid "Skip numbers found in:"
msgstr ""
-#: gschem/src/x_autonumber.c:1278 gschem/src/x_autonumber.c:1287
+#: gschem/src/x_autonumber.c:1280 gschem/src/x_autonumber.c:1289
msgid "Selected objects"
msgstr ""
-#: gschem/src/x_autonumber.c:1279 gschem/src/x_autonumber.c:1288
+#: gschem/src/x_autonumber.c:1281 gschem/src/x_autonumber.c:1290
msgid "Current page"
msgstr ""
-#: gschem/src/x_autonumber.c:1280 gschem/src/x_autonumber.c:1289
+#: gschem/src/x_autonumber.c:1282 gschem/src/x_autonumber.c:1291
msgid "Whole hierarchy"
msgstr ""
-#: gschem/src/x_autonumber.c:1291
+#: gschem/src/x_autonumber.c:1293
msgid "Overwrite existing numbers"
msgstr ""
-#: gschem/src/x_autonumber.c:1296
+#: gschem/src/x_autonumber.c:1298
msgid "<b>Options</b>"
msgstr ""
-#: gschem/src/x_autonumber.c:1318
+#: gschem/src/x_autonumber.c:1320
msgid "Starting number:"
msgstr ""
-#: gschem/src/x_autonumber.c:1325
+#: gschem/src/x_autonumber.c:1327
msgid "Sort order:"
msgstr ""
-#: gschem/src/x_autonumber.c:1346
+#: gschem/src/x_autonumber.c:1348
msgid "Remove numbers"
msgstr ""
-#: gschem/src/x_autonumber.c:1350
+#: gschem/src/x_autonumber.c:1352
msgid "Automatic slotting"
msgstr ""
@@ -1051,48 +1059,48 @@ msgstr ""
msgid "Tried to get an invalid outline color: %d\n"
msgstr ""
-#: gschem/src/x_compselect.c:1040
+#: gschem/src/x_compselect.c:1048
msgid "Filter:"
msgstr ""
-#: gschem/src/x_compselect.c:1143 gschem/src/x_dialog.c:3663
-#: gschem/src/x_multiattrib.c:1782
+#: gschem/src/x_compselect.c:1151 gschem/src/x_dialog.c:3667
+#: gschem/src/x_multiattrib.c:1793
msgid "Name"
msgstr ""
-#: gschem/src/x_compselect.c:1152 gschem/src/x_multiattrib.c:1806
+#: gschem/src/x_compselect.c:1160 gschem/src/x_multiattrib.c:1817
msgid "Value"
msgstr ""
-#: gschem/src/x_compselect.c:1191
+#: gschem/src/x_compselect.c:1199
msgid "Default behavior - reference component"
msgstr ""
-#: gschem/src/x_compselect.c:1194
+#: gschem/src/x_compselect.c:1202
msgid "Embed component in schematic"
msgstr ""
-#: gschem/src/x_compselect.c:1197
+#: gschem/src/x_compselect.c:1205
msgid "Include component as individual objects"
msgstr ""
-#: gschem/src/x_compselect.c:1354
+#: gschem/src/x_compselect.c:1362
msgid "Select Component..."
msgstr ""
-#: gschem/src/x_compselect.c:1377
+#: gschem/src/x_compselect.c:1385
msgid "In Use"
msgstr ""
-#: gschem/src/x_compselect.c:1381
+#: gschem/src/x_compselect.c:1389
msgid "Libraries"
msgstr ""
-#: gschem/src/x_compselect.c:1390 gschem/src/x_fileselect.c:122
+#: gschem/src/x_compselect.c:1398 gschem/src/x_fileselect.c:122
msgid "Preview"
msgstr ""
-#: gschem/src/x_compselect.c:1418
+#: gschem/src/x_compselect.c:1426
msgid "Attributes"
msgstr "Atributos"
@@ -1147,336 +1155,336 @@ msgstr ""
msgid "Edit Text Properties"
msgstr ""
-#: gschem/src/x_dialog.c:471
+#: gschem/src/x_dialog.c:472
msgid "<b>Text Content</b>"
msgstr ""
-#: gschem/src/x_dialog.c:507
+#: gschem/src/x_dialog.c:508
msgid "<b>Text Properties</b>"
msgstr ""
-#: gschem/src/x_dialog.c:522
+#: gschem/src/x_dialog.c:523
msgid "Color:"
msgstr ""
-#: gschem/src/x_dialog.c:529
+#: gschem/src/x_dialog.c:530
msgid "Size:"
msgstr ""
-#: gschem/src/x_dialog.c:538
+#: gschem/src/x_dialog.c:539
msgid "Alignment:"
msgstr ""
-#: gschem/src/x_dialog.c:587
+#: gschem/src/x_dialog.c:588
msgid "Solid"
msgstr ""
-#: gschem/src/x_dialog.c:588
+#: gschem/src/x_dialog.c:589
msgid "Dotted"
msgstr ""
-#: gschem/src/x_dialog.c:589
+#: gschem/src/x_dialog.c:590
msgid "Dashed"
msgstr ""
-#: gschem/src/x_dialog.c:590
+#: gschem/src/x_dialog.c:591
msgid "Center"
msgstr ""
-#: gschem/src/x_dialog.c:591
+#: gschem/src/x_dialog.c:592
msgid "Phantom"
msgstr ""
-#: gschem/src/x_dialog.c:592 gschem/src/x_dialog.c:689
-#: gschem/src/x_dialog.c:698 gschem/src/x_dialog.c:707
-#: gschem/src/x_dialog.c:808 gschem/src/x_dialog.c:810
-#: gschem/src/x_dialog.c:812 gschem/src/x_dialog.c:1038
-#: gschem/src/x_dialog.c:1141 gschem/src/x_dialog.c:1150
-#: gschem/src/x_dialog.c:1159 gschem/src/x_dialog.c:1168
-#: gschem/src/x_dialog.c:1177 gschem/src/x_dialog.c:1290
-#: gschem/src/x_dialog.c:1292 gschem/src/x_dialog.c:1294
-#: gschem/src/x_dialog.c:1296 gschem/src/x_dialog.c:1298
+#: gschem/src/x_dialog.c:593 gschem/src/x_dialog.c:690
+#: gschem/src/x_dialog.c:699 gschem/src/x_dialog.c:708
+#: gschem/src/x_dialog.c:809 gschem/src/x_dialog.c:811
+#: gschem/src/x_dialog.c:813 gschem/src/x_dialog.c:1039
+#: gschem/src/x_dialog.c:1142 gschem/src/x_dialog.c:1151
+#: gschem/src/x_dialog.c:1160 gschem/src/x_dialog.c:1169
+#: gschem/src/x_dialog.c:1178 gschem/src/x_dialog.c:1291
+#: gschem/src/x_dialog.c:1293 gschem/src/x_dialog.c:1295
+#: gschem/src/x_dialog.c:1297 gschem/src/x_dialog.c:1299
msgid "*unchanged*"
msgstr ""
-#: gschem/src/x_dialog.c:916
+#: gschem/src/x_dialog.c:917
msgid "Edit Line Width & Type"
msgstr ""
-#: gschem/src/x_dialog.c:955 gschem/src/x_print.c:307
+#: gschem/src/x_dialog.c:956 gschem/src/x_print.c:307
msgid "Type:"
msgstr ""
-#: gschem/src/x_dialog.c:959
+#: gschem/src/x_dialog.c:960
msgid "Width:"
msgstr ""
-#: gschem/src/x_dialog.c:963
+#: gschem/src/x_dialog.c:964
msgid "Dash Length:"
msgstr ""
-#: gschem/src/x_dialog.c:967
+#: gschem/src/x_dialog.c:968
msgid "Dash Space:"
msgstr ""
-#: gschem/src/x_dialog.c:1034
+#: gschem/src/x_dialog.c:1035
msgid "Hollow"
msgstr ""
-#: gschem/src/x_dialog.c:1035
+#: gschem/src/x_dialog.c:1036
msgid "Filled"
msgstr ""
-#: gschem/src/x_dialog.c:1036
+#: gschem/src/x_dialog.c:1037
msgid "Mesh"
msgstr ""
-#: gschem/src/x_dialog.c:1037
+#: gschem/src/x_dialog.c:1038
msgid "Hatch"
msgstr ""
-#: gschem/src/x_dialog.c:1406
+#: gschem/src/x_dialog.c:1407
msgid "Edit Fill Type"
msgstr ""
-#: gschem/src/x_dialog.c:1444
+#: gschem/src/x_dialog.c:1446
msgid "Fill Type:"
msgstr ""
-#: gschem/src/x_dialog.c:1448
+#: gschem/src/x_dialog.c:1450
msgid "Line Width:"
msgstr ""
-#: gschem/src/x_dialog.c:1452
+#: gschem/src/x_dialog.c:1454
msgid "Angle 1:"
msgstr ""
-#: gschem/src/x_dialog.c:1456
+#: gschem/src/x_dialog.c:1458
msgid "Pitch 1:"
msgstr ""
-#: gschem/src/x_dialog.c:1460
+#: gschem/src/x_dialog.c:1462
msgid "Angle 2:"
msgstr ""
-#: gschem/src/x_dialog.c:1464
+#: gschem/src/x_dialog.c:1466
msgid "Pitch 2:"
msgstr ""
-#: gschem/src/x_dialog.c:1591
+#: gschem/src/x_dialog.c:1593
msgid "Arc Params"
msgstr ""
-#: gschem/src/x_dialog.c:1631
+#: gschem/src/x_dialog.c:1634
msgid "Arc Radius:"
msgstr ""
-#: gschem/src/x_dialog.c:1639
+#: gschem/src/x_dialog.c:1642
msgid "Start Angle:"
msgstr ""
-#: gschem/src/x_dialog.c:1647
+#: gschem/src/x_dialog.c:1650
msgid "Degrees of Sweep:"
msgstr ""
-#: gschem/src/x_dialog.c:1764
+#: gschem/src/x_dialog.c:1768
msgid ""
"Offset to translate?\n"
"(0 for origin)"
msgstr ""
-#: gschem/src/x_dialog.c:1832
+#: gschem/src/x_dialog.c:1836
msgid "Text Size"
msgstr ""
-#: gschem/src/x_dialog.c:1862
+#: gschem/src/x_dialog.c:1866
msgid "Enter new text size:"
msgstr ""
-#: gschem/src/x_dialog.c:1938
+#: gschem/src/x_dialog.c:1942
msgid "Snap Size"
msgstr ""
-#: gschem/src/x_dialog.c:1968
+#: gschem/src/x_dialog.c:1972
msgid "Enter new snap grid spacing:"
msgstr ""
-#: gschem/src/x_dialog.c:2045
+#: gschem/src/x_dialog.c:2049
msgid "Edit slot number"
msgstr ""
-#: gschem/src/x_dialog.c:2076
+#: gschem/src/x_dialog.c:2080
msgid "Edit slot number:"
msgstr ""
-#: gschem/src/x_dialog.c:2117
+#: gschem/src/x_dialog.c:2121
#, c-format
msgid "%s%s (%s)"
msgstr ""
-#: gschem/src/x_dialog.c:2140
+#: gschem/src/x_dialog.c:2144
msgid "About gschem"
msgstr "Sobre gschem"
-#: gschem/src/x_dialog.c:2141
+#: gschem/src/x_dialog.c:2145
msgid "gEDA: GPL Electronic Design Automation"
msgstr ""
-#: gschem/src/x_dialog.c:2142
+#: gschem/src/x_dialog.c:2146
msgid ""
"Copyright © 1998-2009 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
"Copyright © 1998-2009 gEDA Contributors (see ChangeLog for details)"
msgstr ""
-#: gschem/src/x_dialog.c:2201
+#: gschem/src/x_dialog.c:2205
msgid "Coords"
msgstr ""
-#: gschem/src/x_dialog.c:2222
+#: gschem/src/x_dialog.c:2226
msgid "Screen"
msgstr ""
-#: gschem/src/x_dialog.c:2231
+#: gschem/src/x_dialog.c:2235
msgid "World"
msgstr ""
-#: gschem/src/x_dialog.c:2270
+#: gschem/src/x_dialog.c:2274
msgid "Background"
msgstr ""
-#: gschem/src/x_dialog.c:2276
+#: gschem/src/x_dialog.c:2280
msgid "Net endpoint"
msgstr ""
-#: gschem/src/x_dialog.c:2279
+#: gschem/src/x_dialog.c:2283
msgid "Graphic"
msgstr ""
-#: gschem/src/x_dialog.c:2288
+#: gschem/src/x_dialog.c:2292
msgid "Logic bubble"
msgstr ""
-#: gschem/src/x_dialog.c:2291
+#: gschem/src/x_dialog.c:2295
msgid "Grid point"
msgstr ""
-#: gschem/src/x_dialog.c:2294
+#: gschem/src/x_dialog.c:2298
msgid "Detached attribute"
msgstr ""
-#: gschem/src/x_dialog.c:2297 gschem/src/x_window.c:383
+#: gschem/src/x_dialog.c:2301 gschem/src/x_window.c:383
msgid "Text"
msgstr ""
-#: gschem/src/x_dialog.c:2303
+#: gschem/src/x_dialog.c:2307
msgid "Selection"
msgstr ""
-#: gschem/src/x_dialog.c:2306
+#: gschem/src/x_dialog.c:2310
msgid "Bounding box"
msgstr ""
-#: gschem/src/x_dialog.c:2309
+#: gschem/src/x_dialog.c:2313
msgid "Zoom box"
msgstr ""
-#: gschem/src/x_dialog.c:2318
+#: gschem/src/x_dialog.c:2322
msgid "Output background"
msgstr ""
-#: gschem/src/x_dialog.c:2321
+#: gschem/src/x_dialog.c:2325
msgid "Net junction"
msgstr ""
-#: gschem/src/x_dialog.c:2324
+#: gschem/src/x_dialog.c:2328
msgid "Mesh grid major"
msgstr ""
-#: gschem/src/x_dialog.c:2327
+#: gschem/src/x_dialog.c:2331
msgid "Mesh grid minor"
msgstr ""
-#: gschem/src/x_dialog.c:2330
+#: gschem/src/x_dialog.c:2334
msgid "Unknown"
msgstr ""
-#: gschem/src/x_dialog.c:2481
+#: gschem/src/x_dialog.c:2485
#, c-format
msgid "ERROR: NULL object in color_edit_dialog_apply!\n"
msgstr ""
-#: gschem/src/x_dialog.c:2525
+#: gschem/src/x_dialog.c:2529
msgid "Color Edit"
msgstr ""
-#: gschem/src/x_dialog.c:2556
+#: gschem/src/x_dialog.c:2560
msgid "Object color:"
msgstr ""
-#: gschem/src/x_dialog.c:2614
+#: gschem/src/x_dialog.c:2618
msgid "Hotkeys"
msgstr "Teclas de Atalho"
-#: gschem/src/x_dialog.c:2678
+#: gschem/src/x_dialog.c:2682
msgid "Function"
msgstr ""
-#: gschem/src/x_dialog.c:2685
+#: gschem/src/x_dialog.c:2689
msgid "Keystroke(s)"
msgstr ""
-#: gschem/src/x_dialog.c:2991
+#: gschem/src/x_dialog.c:2995
msgid "Find Text"
msgstr ""
-#: gschem/src/x_dialog.c:3022
+#: gschem/src/x_dialog.c:3026
msgid "Text to find:"
msgstr ""
-#: gschem/src/x_dialog.c:3032
+#: gschem/src/x_dialog.c:3036
msgid "descend into hierarchy"
msgstr ""
-#: gschem/src/x_dialog.c:3097
+#: gschem/src/x_dialog.c:3101
msgid "Hide Text"
msgstr ""
-#: gschem/src/x_dialog.c:3128
+#: gschem/src/x_dialog.c:3132
msgid "Hide text starting with:"
msgstr ""
-#: gschem/src/x_dialog.c:3197
+#: gschem/src/x_dialog.c:3201
msgid "Show Text"
msgstr ""
-#: gschem/src/x_dialog.c:3228
+#: gschem/src/x_dialog.c:3232
msgid "Show text starting with:"
msgstr ""
-#: gschem/src/x_dialog.c:3685
+#: gschem/src/x_dialog.c:3689
msgid "S_elect the schematics you want to save:"
msgstr ""
-#: gschem/src/x_dialog.c:3779
+#: gschem/src/x_dialog.c:3784
#, c-format
msgid "Save the changes to schematic \"%s\" before closing?"
msgstr ""
-#: gschem/src/x_dialog.c:3785
+#: gschem/src/x_dialog.c:3790
#, c-format
msgid ""
"There are %d schematics with unsaved changes. Save changes before closing?"
msgstr ""
-#: gschem/src/x_dialog.c:3814
+#: gschem/src/x_dialog.c:3819
msgid "If you don't save, all your changes will be permanently lost."
msgstr ""
-#: gschem/src/x_dialog.c:3834
+#: gschem/src/x_dialog.c:3839
msgid "_Close without saving"
msgstr ""
-#: gschem/src/x_dialog.c:4170
+#: gschem/src/x_dialog.c:4175
#, c-format
msgid ""
"<span weight=\"bold\" size=\"larger\">The input attribute \"%s\" is invalid\n"
@@ -1487,19 +1495,19 @@ msgid ""
"The value cannot start with a space."
msgstr ""
-#: gschem/src/x_dialog.c:4172
+#: gschem/src/x_dialog.c:4177
msgid "Invalid Attribute"
msgstr ""
-#: gschem/src/x_dialog.c:4208
+#: gschem/src/x_dialog.c:4213
msgid "Pin type"
msgstr ""
-#: gschem/src/x_dialog.c:4232
+#: gschem/src/x_dialog.c:4237
msgid "Net pin"
msgstr ""
-#: gschem/src/x_dialog.c:4234
+#: gschem/src/x_dialog.c:4239
msgid "Bus pin (graphical)"
msgstr ""
@@ -1592,11 +1600,11 @@ msgstr ""
msgid "Write image..."
msgstr ""
-#: gschem/src/x_log.c:188
+#: gschem/src/x_log.c:209
msgid "** Invalid UTF-8 in log message. See stderr or gschem.log.\n"
msgstr ""
-#: gschem/src/x_log.c:256
+#: gschem/src/x_log.c:288
msgid "Status"
msgstr ""
@@ -1672,69 +1680,60 @@ msgstr ""
msgid "/Up"
msgstr ""
-#: gschem/src/x_menus.c:321
+#: gschem/src/x_menus.c:323
#, c-format
msgid "Tried to set the sensitivity on non-existent menu item '%s'\n"
msgstr ""
-#: gschem/src/x_menus.c:345
+#: gschem/src/x_menus.c:347
msgid "Popup_menu_item_factory doesn't exist!\n"
msgstr ""
-#: gschem/src/x_menus.c:358
+#: gschem/src/x_menus.c:360
msgid "Tried to set the sensitivity on a non-existent popup menu_item\n"
msgstr ""
-#: gschem/src/x_menus.c:438
-#, c-format
-msgid "Couldn't open file %s\n"
-msgstr ""
-
-#: gschem/src/x_menus.c:495
-msgid "Clear"
-msgstr ""
-
-#: gschem/src/x_multiattrib.c:911
+#: gschem/src/x_multiattrib.c:915
msgid "Attributes with empty name are not allowed. Please set a name."
msgstr ""
-#: gschem/src/x_multiattrib.c:1456
+#: gschem/src/x_multiattrib.c:1468
msgid "Show Value only"
msgstr ""
-#: gschem/src/x_multiattrib.c:1458
+#: gschem/src/x_multiattrib.c:1470
msgid "Show Name only"
msgstr ""
-#: gschem/src/x_multiattrib.c:1486
+#: gschem/src/x_multiattrib.c:1498
msgid "Promote"
msgstr ""
-#: gschem/src/x_multiattrib.c:1490
+#: gschem/src/x_multiattrib.c:1502
msgid "Duplicate"
msgstr ""
-#: gschem/src/x_multiattrib.c:1708
+#: gschem/src/x_multiattrib.c:1719
msgid "Edit Attributes"
msgstr ""
-#: gschem/src/x_multiattrib.c:1826
+#: gschem/src/x_multiattrib.c:1837
msgid "Vis?"
msgstr ""
-#: gschem/src/x_multiattrib.c:1844
+#: gschem/src/x_multiattrib.c:1855
msgid "N"
msgstr ""
-#: gschem/src/x_multiattrib.c:1862
+#: gschem/src/x_multiattrib.c:1873
msgid "V"
msgstr ""
-#: gschem/src/x_multiattrib.c:1884
+#: gschem/src/x_multiattrib.c:1895
msgid "Show inherited attributes"
msgstr ""
-#: gschem/src/x_multiattrib.c:1900
+#: gschem/src/x_multiattrib.c:1911
msgid "Add Attribute"
msgstr ""
@@ -1758,23 +1757,23 @@ msgstr "Fechar Página"
msgid "Discard Page"
msgstr ""
-#: gschem/src/x_pagesel.c:376
+#: gschem/src/x_pagesel.c:375
msgid "Page Manager"
msgstr ""
-#: gschem/src/x_pagesel.c:432
+#: gschem/src/x_pagesel.c:431
msgid "Filename"
msgstr ""
-#: gschem/src/x_pagesel.c:448
+#: gschem/src/x_pagesel.c:447
msgid "Changed"
msgstr ""
-#: gschem/src/x_pagesel.c:468
+#: gschem/src/x_pagesel.c:467
msgid "Right click on the filename for more options..."
msgstr ""
-#: gschem/src/x_preview.c:234
+#: gschem/src/x_preview.c:233
msgid "Preview Buffer"
msgstr ""
@@ -1830,23 +1829,23 @@ msgstr ""
msgid "Command:"
msgstr ""
-#: gschem/src/x_print.c:741
+#: gschem/src/x_print.c:745
msgid "No print destination specified\n"
msgstr ""
-#: gschem/src/x_print.c:748
+#: gschem/src/x_print.c:752
#, c-format
msgid "Cannot print current schematic to [%s]\n"
msgstr ""
-#: gschem/src/x_print.c:757
+#: gschem/src/x_print.c:761
#, c-format
msgid ""
"Error printing to file '%s'\n"
"Check the log window for more information"
msgstr ""
-#: gschem/src/x_print.c:764
+#: gschem/src/x_print.c:768
#, c-format
msgid "Printed current schematic to [%s]\n"
msgstr ""
@@ -1855,6 +1854,11 @@ msgstr ""
msgid "Execute Script..."
msgstr "Executar Script..."
+#: gschem/src/x_script.c:66
+#, c-format
+msgid "Executing guile script [%s]\n"
+msgstr ""
+
#: gschem/src/x_window.c:81
#, c-format
msgid "Couldn't allocate gc\n"
@@ -1962,35 +1966,35 @@ msgstr ""
msgid "New file [%s]\n"
msgstr ""
-#: gschem/src/x_window.c:857
+#: gschem/src/x_window.c:855
#, c-format
msgid "Could NOT save page [%s]\n"
msgstr ""
-#: gschem/src/x_window.c:858
+#: gschem/src/x_window.c:856
msgid "Error while trying to save"
msgstr ""
-#: gschem/src/x_window.c:867
+#: gschem/src/x_window.c:865
#, c-format
msgid "Saved as [%s]\n"
msgstr ""
-#: gschem/src/x_window.c:869
+#: gschem/src/x_window.c:867
#, c-format
msgid "Saved [%s]\n"
msgstr ""
-#: gschem/src/x_window.c:871
+#: gschem/src/x_window.c:869
msgid "Saved"
msgstr "Guardado"
-#: gschem/src/x_window.c:945
+#: gschem/src/x_window.c:943
#, c-format
msgid "Discarding page [%s]\n"
msgstr ""
-#: gschem/src/x_window.c:945
+#: gschem/src/x_window.c:943
#, c-format
msgid "Closing [%s]\n"
msgstr ""
@@ -2031,7 +2035,7 @@ msgstr ""
msgid "Save All"
msgstr "Guardar Tudo"
-#: gschem/lib/system-gschemrc.scm:1386 gschem/lib/system-gschemrc.scm:1477
+#: gschem/lib/system-gschemrc.scm:1386 gschem/lib/system-gschemrc.scm:1478
msgid "_Revert"
msgstr ""
@@ -2043,7 +2047,7 @@ msgstr ""
msgid "Write _image..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1393 gschem/lib/system-gschemrc.scm:1478
+#: gschem/lib/system-gschemrc.scm:1393 gschem/lib/system-gschemrc.scm:1479
msgid "_Close"
msgstr ""
@@ -2075,387 +2079,392 @@ msgstr ""
msgid "_Delete"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1412
+#: gschem/lib/system-gschemrc.scm:1409
+#, fuzzy
+msgid "Select All"
+msgstr "Modo de Selecção"
+
+#: gschem/lib/system-gschemrc.scm:1410
+msgid "Deselect"
+msgstr ""
+
+#: gschem/lib/system-gschemrc.scm:1414
msgid "Rotate 90 Mode"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1415
+#: gschem/lib/system-gschemrc.scm:1417
msgid "Edit..."
msgstr "Editar"
-#: gschem/lib/system-gschemrc.scm:1416
+#: gschem/lib/system-gschemrc.scm:1418
msgid "Edit Text..."
msgstr "Editar Texto..."
-#: gschem/lib/system-gschemrc.scm:1417
+#: gschem/lib/system-gschemrc.scm:1419
msgid "Slot..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1418
+#: gschem/lib/system-gschemrc.scm:1420
msgid "Color..."
msgstr "Cor..."
-#: gschem/lib/system-gschemrc.scm:1419
+#: gschem/lib/system-gschemrc.scm:1421
msgid "Line Width & Type..."
msgstr "Espessura e Tipo de Linha"
-#: gschem/lib/system-gschemrc.scm:1420
+#: gschem/lib/system-gschemrc.scm:1422
msgid "Fill Type..."
msgstr "Tipo de Enchimento"
-#: gschem/lib/system-gschemrc.scm:1421
+#: gschem/lib/system-gschemrc.scm:1423
msgid "Symbol Translate..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1425
+#: gschem/lib/system-gschemrc.scm:1427
msgid "Invoke Macro"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1426
+#: gschem/lib/system-gschemrc.scm:1428
msgid "Embed Component/Picture"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1427
+#: gschem/lib/system-gschemrc.scm:1429
msgid "Unembed Component/Picture"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1428
+#: gschem/lib/system-gschemrc.scm:1430
msgid "Update Component"
msgstr "Actualizar Componente"
-#: gschem/lib/system-gschemrc.scm:1429
+#: gschem/lib/system-gschemrc.scm:1431
msgid "Show/Hide Inv Text"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1430
-msgid "Make Inv Text Vis"
-msgstr ""
-
-#: gschem/lib/system-gschemrc.scm:1436
+#: gschem/lib/system-gschemrc.scm:1437
msgid "Copy into 1"
msgstr "Copiar para 1"
-#: gschem/lib/system-gschemrc.scm:1437
+#: gschem/lib/system-gschemrc.scm:1438
msgid "Copy into 2"
msgstr "Copiar para 2"
-#: gschem/lib/system-gschemrc.scm:1438
+#: gschem/lib/system-gschemrc.scm:1439
msgid "Copy into 3"
msgstr "Copiar para 3"
-#: gschem/lib/system-gschemrc.scm:1439
+#: gschem/lib/system-gschemrc.scm:1440
msgid "Copy into 4"
msgstr "Copiar para 4"
-#: gschem/lib/system-gschemrc.scm:1440
+#: gschem/lib/system-gschemrc.scm:1441
msgid "Copy into 5"
msgstr "Copiar para 5"
-#: gschem/lib/system-gschemrc.scm:1441
+#: gschem/lib/system-gschemrc.scm:1442
msgid "Cut into 1"
msgstr "Cortar para 1"
-#: gschem/lib/system-gschemrc.scm:1442
+#: gschem/lib/system-gschemrc.scm:1443
msgid "Cut into 2"
msgstr "Cortar para 2"
-#: gschem/lib/system-gschemrc.scm:1443
+#: gschem/lib/system-gschemrc.scm:1444
msgid "Cut into 3"
msgstr "Cortar para 3"
-#: gschem/lib/system-gschemrc.scm:1444
+#: gschem/lib/system-gschemrc.scm:1445
msgid "Cut into 4"
msgstr "Cortar para 4"
-#: gschem/lib/system-gschemrc.scm:1445
+#: gschem/lib/system-gschemrc.scm:1446
msgid "Cut into 5"
msgstr "Cortar para 5"
-#: gschem/lib/system-gschemrc.scm:1446
+#: gschem/lib/system-gschemrc.scm:1447
msgid "Paste from 1"
msgstr "Colar de 1"
-#: gschem/lib/system-gschemrc.scm:1447
+#: gschem/lib/system-gschemrc.scm:1448
msgid "Paste from 2"
msgstr "Colar de 2"
-#: gschem/lib/system-gschemrc.scm:1448
+#: gschem/lib/system-gschemrc.scm:1449
msgid "Paste from 3"
msgstr "Colar de 3"
-#: gschem/lib/system-gschemrc.scm:1449
+#: gschem/lib/system-gschemrc.scm:1450
msgid "Paste from 4"
msgstr "Colar de 4"
-#: gschem/lib/system-gschemrc.scm:1450
+#: gschem/lib/system-gschemrc.scm:1451
msgid "Paste from 5"
msgstr "Colar de 5"
-#: gschem/lib/system-gschemrc.scm:1456
+#: gschem/lib/system-gschemrc.scm:1457
msgid "_Redraw"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1457
+#: gschem/lib/system-gschemrc.scm:1458
msgid "_Pan"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1458
+#: gschem/lib/system-gschemrc.scm:1459
msgid "Zoom _Box"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1459
+#: gschem/lib/system-gschemrc.scm:1460
msgid "Zoom _Extents"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1460
+#: gschem/lib/system-gschemrc.scm:1461
msgid "Zoom _In"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1461
+#: gschem/lib/system-gschemrc.scm:1462
msgid "Zoom _Out"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1462
+#: gschem/lib/system-gschemrc.scm:1463
msgid "Zoom _Full"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1464
+#: gschem/lib/system-gschemrc.scm:1465
msgid "_Dark color scheme"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1465
+#: gschem/lib/system-gschemrc.scm:1466
msgid "_Light color scheme"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1466
+#: gschem/lib/system-gschemrc.scm:1467
msgid "B_W color scheme"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1473
+#: gschem/lib/system-gschemrc.scm:1474
msgid "_Manager..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1474
+#: gschem/lib/system-gschemrc.scm:1475
msgid "_Previous"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1475
+#: gschem/lib/system-gschemrc.scm:1476
msgid "_Next"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1476
+#: gschem/lib/system-gschemrc.scm:1477
msgid "Ne_w"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1480
+#: gschem/lib/system-gschemrc.scm:1481
msgid "_Discard"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1486
+#: gschem/lib/system-gschemrc.scm:1487
msgid "_Component..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1487
+#: gschem/lib/system-gschemrc.scm:1488
msgid "_Net"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1488
+#: gschem/lib/system-gschemrc.scm:1489
msgid "B_us"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1489
+#: gschem/lib/system-gschemrc.scm:1490
msgid "_Attribute..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1490
+#: gschem/lib/system-gschemrc.scm:1491
msgid "_Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1492
+#: gschem/lib/system-gschemrc.scm:1493
msgid "_Line"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1493
+#: gschem/lib/system-gschemrc.scm:1494
msgid "_Box"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1494
+#: gschem/lib/system-gschemrc.scm:1495
msgid "C_ircle"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1495
+#: gschem/lib/system-gschemrc.scm:1496
msgid "A_rc"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1496
+#: gschem/lib/system-gschemrc.scm:1497
msgid "_Pin"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1497
+#: gschem/lib/system-gschemrc.scm:1498
msgid "Pictu_re..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1503
+#: gschem/lib/system-gschemrc.scm:1504
msgid "_Down Schematic"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1504
+#: gschem/lib/system-gschemrc.scm:1505
msgid "Down _Symbol"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1505
+#: gschem/lib/system-gschemrc.scm:1506
msgid "_Up"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1506
+#: gschem/lib/system-gschemrc.scm:1507
msgid "D_ocumentation..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1512
+#: gschem/lib/system-gschemrc.scm:1513
msgid "_Attach"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1513
+#: gschem/lib/system-gschemrc.scm:1514
msgid "_Detach"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1514
+#: gschem/lib/system-gschemrc.scm:1515
msgid "Show _Value"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1515
+#: gschem/lib/system-gschemrc.scm:1516
msgid "Show _Name"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1516
+#: gschem/lib/system-gschemrc.scm:1517
msgid "Show _Both"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1517
+#: gschem/lib/system-gschemrc.scm:1518
msgid "_Toggle Visibility"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1519
+#: gschem/lib/system-gschemrc.scm:1520
msgid "_Find Specific Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1520
+#: gschem/lib/system-gschemrc.scm:1521
msgid "_Hide Specific Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1521
+#: gschem/lib/system-gschemrc.scm:1522
msgid "_Show Specific Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1522
+#: gschem/lib/system-gschemrc.scm:1523
msgid "A_utonumber Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1528
+#: gschem/lib/system-gschemrc.scm:1529
msgid "_Text Size..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1529
+#: gschem/lib/system-gschemrc.scm:1530
msgid "Cycle _grid styles"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1530
+#: gschem/lib/system-gschemrc.scm:1531
msgid "Toggle _Snap On/Off"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1531
+#: gschem/lib/system-gschemrc.scm:1532
msgid "Snap Grid S_pacing..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1532
+#: gschem/lib/system-gschemrc.scm:1533
msgid "Scale _up Grid Spacing"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1534
+#: gschem/lib/system-gschemrc.scm:1535
msgid "Scale _down Grid Spacing"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1536
+#: gschem/lib/system-gschemrc.scm:1537
msgid "Toggle _Outline/Box"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1538
+#: gschem/lib/system-gschemrc.scm:1539
msgid "Toggle Net _Rubberband"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1539
+#: gschem/lib/system-gschemrc.scm:1540
msgid "Toggle _Magnetic Net"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1540
+#: gschem/lib/system-gschemrc.scm:1541
msgid "Show _Log Window..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1542
+#: gschem/lib/system-gschemrc.scm:1543
msgid "Show _Coord Window..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1558
+#: gschem/lib/system-gschemrc.scm:1559
msgid "gEDA Docu_mentation..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1559
+#: gschem/lib/system-gschemrc.scm:1560
msgid "gschem _FAQ..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1560
+#: gschem/lib/system-gschemrc.scm:1561
msgid "gEDA _Wiki..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1561
+#: gschem/lib/system-gschemrc.scm:1562
msgid "Component D_ocumentation..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1563
+#: gschem/lib/system-gschemrc.scm:1564
msgid "_Hotkeys..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1564
+#: gschem/lib/system-gschemrc.scm:1565
msgid "_About..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1570
+#: gschem/lib/system-gschemrc.scm:1571
msgid "_File"
msgstr "_Ficheiro"
-#: gschem/lib/system-gschemrc.scm:1571
+#: gschem/lib/system-gschemrc.scm:1572
msgid "_Edit"
msgstr "_Editar"
-#: gschem/lib/system-gschemrc.scm:1572
+#: gschem/lib/system-gschemrc.scm:1573
msgid "_Buffer"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1573
+#: gschem/lib/system-gschemrc.scm:1574
msgid "_View"
msgstr "_Ver"
-#: gschem/lib/system-gschemrc.scm:1574
+#: gschem/lib/system-gschemrc.scm:1575
msgid "_Page"
msgstr "_Página"
-#: gschem/lib/system-gschemrc.scm:1575
+#: gschem/lib/system-gschemrc.scm:1576
msgid "_Add"
msgstr "_Adicionar"
-#: gschem/lib/system-gschemrc.scm:1576
+#: gschem/lib/system-gschemrc.scm:1577
msgid "Hie_rarchy"
msgstr "Hie_rarquia"
-#: gschem/lib/system-gschemrc.scm:1577
+#: gschem/lib/system-gschemrc.scm:1578
msgid "A_ttributes"
msgstr "A_tributos"
-#: gschem/lib/system-gschemrc.scm:1578
+#: gschem/lib/system-gschemrc.scm:1579
msgid "_Options"
msgstr "_Opções"
-#: gschem/lib/system-gschemrc.scm:1579
+#: gschem/lib/system-gschemrc.scm:1580
msgid "_Help"
msgstr "Ajuda"
diff --git a/gschem/po/pt_BR.po b/gschem/po/pt_BR.po
index 16ac716..5f41c80 100644
--- a/gschem/po/pt_BR.po
+++ b/gschem/po/pt_BR.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2010-11-07 13:37+0000\n"
+"POT-Creation-Date: 2011-01-16 00:11-0500\n"
"PO-Revision-Date: 2010-02-14 01:04+0000\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -22,17 +22,17 @@ msgstr ""
msgid "Zoom too small! Cannot zoom further.\n"
msgstr "Zoom muito pequeno! Não posso diminuir.\n"
-#: gschem/src/g_funcs.c:339 gschem/src/i_callbacks.c:68
+#: gschem/src/g_funcs.c:347 gschem/src/i_callbacks.c:68
#, c-format
msgid "Could not fork\n"
msgstr ""
-#: gschem/src/g_funcs.c:355 gschem/src/i_callbacks.c:78
+#: gschem/src/g_funcs.c:363 gschem/src/i_callbacks.c:78
#, c-format
msgid "Could not invoke %s\n"
msgstr "ImpossÃvel invocar %s!\n"
-#: gschem/src/g_funcs.c:361 gschem/src/i_callbacks.c:82
+#: gschem/src/g_funcs.c:369 gschem/src/i_callbacks.c:82
msgid "Documentation commands not supported under MinGW.\n"
msgstr "Documentação de comandos não é suportada no MinGW.\n"
@@ -122,12 +122,12 @@ msgstr ""
msgid "Invalid number of steps [%d] scrollpan-steps\n"
msgstr ""
-#: gschem/src/gschem.c:184
+#: gschem/src/gschem.c:188
#, c-format
msgid "gEDA/gschem version %s%s.%s\n"
msgstr "gEDA/gschem versão %s%s.%s\n"
-#: gschem/src/gschem.c:187
+#: gschem/src/gschem.c:191
msgid ""
"gEDA/gschem comes with ABSOLUTELY NO WARRANTY; see COPYING for more "
"details.\n"
@@ -135,14 +135,14 @@ msgstr ""
"gEDA/gschem vem com ABSOLUTAMENTE NENHUMA GARANTIA; leia o arquivo COPYING "
"para maiores detalhes.\n"
-#: gschem/src/gschem.c:189
+#: gschem/src/gschem.c:193
msgid ""
"This is free software, and you are welcome to redistribute it under certain\n"
msgstr ""
"Este programa é um software livre, e você é convidado a redistribui-lo sob "
"certas\n"
-#: gschem/src/gschem.c:191
+#: gschem/src/gschem.c:195
msgid ""
"conditions; please see the COPYING file for more details.\n"
"\n"
@@ -150,17 +150,17 @@ msgstr ""
"condições; Leia o arquivo COPYING para maiores detalhes.\n"
"\n"
-#: gschem/src/gschem.c:194
+#: gschem/src/gschem.c:198
#, c-format
msgid "This is the MINGW32 port.\n"
msgstr "Esta é a versão portada para MINGW32.\n"
-#: gschem/src/gschem.c:198
+#: gschem/src/gschem.c:202
#, c-format
msgid "Current locale settings: %s\n"
msgstr "Configuração para Localização: %s\n"
-#: gschem/src/gschem.c:213
+#: gschem/src/gschem.c:218
msgid ""
"You must set the GEDADATA environment variable!\n"
"\n"
@@ -168,31 +168,21 @@ msgid ""
"environment variable to point to the correct location.\n"
msgstr ""
-#: gschem/src/gschem.c:248
+#: gschem/src/gschem.c:256
#, c-format
msgid "Couldn't find init scm file [%s]\n"
msgstr ""
-#: gschem/src/gschem.c:252
+#: gschem/src/gschem.c:260
#, c-format
msgid "Read init scm file [%s]\n"
msgstr "Lendo o arquivo scm [%s]\n"
-#: gschem/src/gschem.c:256
+#: gschem/src/gschem.c:264
#, c-format
msgid "Failed to read init scm file [%s]\n"
msgstr "Falhou ao ler o arquivo scm [%s]\n"
-#: gschem/src/gschem.c:317
-#, c-format
-msgid "Scheme directory NOT set!\n"
-msgstr "Diretório Scheme N�O ajustado!\n"
-
-#: gschem/src/gschem.c:324 gschem/src/x_script.c:66
-#, c-format
-msgid "Executing guile script [%s]\n"
-msgstr "Executando script guile [%s]\n"
-
#: gschem/src/gschem_cairo.c:310
#, c-format
msgid "Unknown end for line (%d)\n"
@@ -216,11 +206,11 @@ msgstr "Modo de Componente"
msgid "Text Mode"
msgstr "Modo Texto"
-#: gschem/src/i_basic.c:84 gschem/lib/system-gschemrc.scm:1409
+#: gschem/src/i_basic.c:84 gschem/lib/system-gschemrc.scm:1411
msgid "Copy Mode"
msgstr "Modo de Cópia"
-#: gschem/src/i_basic.c:87 gschem/lib/system-gschemrc.scm:1411
+#: gschem/src/i_basic.c:87 gschem/lib/system-gschemrc.scm:1413
msgid "Move Mode"
msgstr "Modo de Movimentação"
@@ -228,7 +218,7 @@ msgstr "Modo de Movimentação"
msgid "Rotate Mode"
msgstr "Modo de Rotação"
-#: gschem/src/i_basic.c:91 gschem/lib/system-gschemrc.scm:1413
+#: gschem/src/i_basic.c:91 gschem/lib/system-gschemrc.scm:1415
msgid "Mirror Mode"
msgstr "Modo de espelho"
@@ -281,22 +271,22 @@ msgstr "Modo de Arco"
msgid "Pin Mode"
msgstr "Modo de Pino"
-#: gschem/src/i_basic.c:135 gschem/src/i_callbacks.c:544
-#: gschem/src/i_callbacks.c:568
+#: gschem/src/i_basic.c:135 gschem/src/i_callbacks.c:576
+#: gschem/src/i_callbacks.c:600
msgid "Copy"
msgstr "Copiar"
-#: gschem/src/i_basic.c:137 gschem/src/i_callbacks.c:634
-#: gschem/src/i_callbacks.c:658
+#: gschem/src/i_basic.c:137 gschem/src/i_callbacks.c:666
+#: gschem/src/i_callbacks.c:690
msgid "Move"
msgstr "Mover"
-#: gschem/src/i_basic.c:139 gschem/src/i_callbacks.c:589
-#: gschem/src/i_callbacks.c:613
+#: gschem/src/i_basic.c:139 gschem/src/i_callbacks.c:621
+#: gschem/src/i_callbacks.c:645
msgid "Multiple Copy"
msgstr "Multipla Cópia"
-#: gschem/src/i_basic.c:142 gschem/lib/system-gschemrc.scm:1410
+#: gschem/src/i_basic.c:142 gschem/lib/system-gschemrc.scm:1412
msgid "Multiple Copy Mode"
msgstr "Modo de Múltipla Cópia"
@@ -316,7 +306,7 @@ msgstr ""
msgid "Action"
msgstr "Ação"
-#: gschem/src/i_basic.c:260 gschem/src/x_dialog.c:2312
+#: gschem/src/i_basic.c:260 gschem/src/x_dialog.c:2316
#: gschem/src/x_window.c:491
msgid "Stroke"
msgstr "Stroke"
@@ -347,7 +337,7 @@ msgstr "Grid(%s, %s)"
msgid "Documentation for [%s,%s,%s,%s]\n"
msgstr "Documentação para [%s,%s,%s,%s]\n"
-#: gschem/src/i_callbacks.c:123 gschem/src/i_callbacks.c:1699
+#: gschem/src/i_callbacks.c:123 gschem/src/i_callbacks.c:1706
#, c-format
msgid "New page created [%s]\n"
msgstr "Criada Nova Página [%s]\n"
@@ -369,245 +359,241 @@ msgstr "Salvar Tudo"
msgid "Closing Window\n"
msgstr "Fechando Janela\n"
-#: gschem/src/i_callbacks.c:549 gschem/src/i_callbacks.c:594
-#: gschem/src/i_callbacks.c:639
+#: gschem/src/i_callbacks.c:581 gschem/src/i_callbacks.c:626
+#: gschem/src/i_callbacks.c:671
msgid "Select objs first"
msgstr "Selecione objetos antes"
-#: gschem/src/i_callbacks.c:678 gschem/src/x_multiattrib.c:1491
+#: gschem/src/i_callbacks.c:710 gschem/src/x_multiattrib.c:1503
msgid "Delete"
msgstr "Apagar"
-#: gschem/src/i_callbacks.c:703
+#: gschem/src/i_callbacks.c:735
msgid "Edit"
msgstr "Editar"
-#: gschem/src/i_callbacks.c:718
+#: gschem/src/i_callbacks.c:750
msgid "Edit pin type"
msgstr ""
-#: gschem/src/i_callbacks.c:737
+#: gschem/src/i_callbacks.c:769
msgid "Edit Text"
msgstr "Editar Texto"
-#: gschem/src/i_callbacks.c:760
+#: gschem/src/i_callbacks.c:792
msgid "Slot"
msgstr "Slot"
-#: gschem/src/i_callbacks.c:777
+#: gschem/src/i_callbacks.c:809
msgid "Color"
msgstr "Cor"
-#: gschem/src/i_callbacks.c:814 gschem/src/i_callbacks.c:859
+#: gschem/src/i_callbacks.c:846 gschem/src/i_callbacks.c:891
msgid "Rotate"
msgstr "Rotacionar"
-#: gschem/src/i_callbacks.c:882 gschem/src/i_callbacks.c:907
+#: gschem/src/i_callbacks.c:913 gschem/src/i_callbacks.c:938
msgid "Mirror"
msgstr "Espelhar"
-#: gschem/src/i_callbacks.c:928 gschem/src/x_dialog.c:2315
-#: gschem/lib/system-gschemrc.scm:1422
+#: gschem/src/i_callbacks.c:959 gschem/src/x_dialog.c:2319
+#: gschem/lib/system-gschemrc.scm:1424
msgid "Lock"
msgstr "Bloquear"
-#: gschem/src/i_callbacks.c:946 gschem/lib/system-gschemrc.scm:1423
+#: gschem/src/i_callbacks.c:977 gschem/lib/system-gschemrc.scm:1425
msgid "Unlock"
msgstr "Desbloquear"
-#: gschem/src/i_callbacks.c:964 gschem/src/x_dialog.c:1734
+#: gschem/src/i_callbacks.c:995 gschem/src/x_dialog.c:1737
msgid "Translate"
msgstr "Transladar"
-#: gschem/src/i_callbacks.c:967
+#: gschem/src/i_callbacks.c:998
msgid "WARNING: Do not translate with snap off!\n"
msgstr "ATEN��O: Não translade com o agarre (snap) desligado!\n"
-#: gschem/src/i_callbacks.c:968
+#: gschem/src/i_callbacks.c:999
msgid "WARNING: Turning snap on and continuing with translate.\n"
msgstr "ATENÃ?Ã?O: Ligando o agarre e continuando o translado.\n"
-#: gschem/src/i_callbacks.c:975
+#: gschem/src/i_callbacks.c:1006
msgid "WARNING: Snap grid size is not equal to 100!\n"
msgstr "ATEN��O: A grade de agarre não está em 100!\n"
-#: gschem/src/i_callbacks.c:977
+#: gschem/src/i_callbacks.c:1008
msgid ""
"WARNING: If you are translating a symbol to the origin, the snap grid size "
"should be set to 100\n"
msgstr ""
"ATENÃ?Ã?O: Se transladar um sÃmbolo para origem, a grade deve estar em 100\n"
-#: gschem/src/i_callbacks.c:1008
+#: gschem/src/i_callbacks.c:1039
msgid "Embed"
msgstr "Embutir"
-#: gschem/src/i_callbacks.c:1047
+#: gschem/src/i_callbacks.c:1078
msgid "Unembed"
msgstr "Desembutir"
-#: gschem/src/i_callbacks.c:1089
+#: gschem/src/i_callbacks.c:1120
msgid "Update"
msgstr "Atualizar"
-#: gschem/src/i_callbacks.c:1136
+#: gschem/src/i_callbacks.c:1167
msgid "ShowHidden"
msgstr "Mostrar Oculto"
-#: gschem/src/i_callbacks.c:1160
-msgid "MakeVisible"
-msgstr "Deixar VisÃvel"
-
-#: gschem/src/i_callbacks.c:1466 gschem/src/i_callbacks.c:1538
+#: gschem/src/i_callbacks.c:1473 gschem/src/i_callbacks.c:1545
msgid "Pan"
msgstr "Pan"
-#: gschem/src/i_callbacks.c:1743
+#: gschem/src/i_callbacks.c:1750
msgid "Really revert page?"
msgstr "Reverter Página?"
-#: gschem/src/i_callbacks.c:1813
+#: gschem/src/i_callbacks.c:1820
msgid "Copy to clipboard"
msgstr ""
-#: gschem/src/i_callbacks.c:1831
+#: gschem/src/i_callbacks.c:1838
msgid "Cut to clipboard"
msgstr ""
-#: gschem/src/i_callbacks.c:1849
+#: gschem/src/i_callbacks.c:1856
msgid "Paste from clipboard"
msgstr ""
-#: gschem/src/i_callbacks.c:1861 gschem/src/i_callbacks.c:2100
-#: gschem/src/i_callbacks.c:2122 gschem/src/i_callbacks.c:2144
-#: gschem/src/i_callbacks.c:2166 gschem/src/i_callbacks.c:2188
+#: gschem/src/i_callbacks.c:1868 gschem/src/i_callbacks.c:2107
+#: gschem/src/i_callbacks.c:2129 gschem/src/i_callbacks.c:2151
+#: gschem/src/i_callbacks.c:2173 gschem/src/i_callbacks.c:2195
msgid "Empty buffer"
msgstr "Buffer vazio"
-#: gschem/src/i_callbacks.c:1906
+#: gschem/src/i_callbacks.c:1913
msgid "Copy 1"
msgstr "Copiar para 1"
-#: gschem/src/i_callbacks.c:1925
+#: gschem/src/i_callbacks.c:1932
msgid "Copy 2"
msgstr "Copiar para 2"
-#: gschem/src/i_callbacks.c:1944
+#: gschem/src/i_callbacks.c:1951
msgid "Copy 3"
msgstr "Copiar para 3"
-#: gschem/src/i_callbacks.c:1963
+#: gschem/src/i_callbacks.c:1970
msgid "Copy 4"
msgstr "Copiar para 4"
-#: gschem/src/i_callbacks.c:1982
+#: gschem/src/i_callbacks.c:1989
msgid "Copy 5"
msgstr "Copiar para 5"
-#: gschem/src/i_callbacks.c:2001
+#: gschem/src/i_callbacks.c:2008
msgid "Cut 1"
msgstr "Cortar para 1"
-#: gschem/src/i_callbacks.c:2020
+#: gschem/src/i_callbacks.c:2027
msgid "Cut 2"
msgstr "Cortar para 2"
-#: gschem/src/i_callbacks.c:2039
+#: gschem/src/i_callbacks.c:2046
msgid "Cut 3"
msgstr "Cortar para 3"
-#: gschem/src/i_callbacks.c:2058
+#: gschem/src/i_callbacks.c:2065
msgid "Cut 4"
msgstr "Cortar para 4"
-#: gschem/src/i_callbacks.c:2077
+#: gschem/src/i_callbacks.c:2084
msgid "Cut 5"
msgstr "Cortar para 5"
-#: gschem/src/i_callbacks.c:2093
+#: gschem/src/i_callbacks.c:2100
msgid "Paste 1"
msgstr "Colar de 1"
-#: gschem/src/i_callbacks.c:2115
+#: gschem/src/i_callbacks.c:2122
msgid "Paste 2"
msgstr "Colar de 2"
-#: gschem/src/i_callbacks.c:2137
+#: gschem/src/i_callbacks.c:2144
msgid "Paste 3"
msgstr "Colar de 3"
-#: gschem/src/i_callbacks.c:2159
+#: gschem/src/i_callbacks.c:2166
msgid "Paste 4"
msgstr "Colar de 4"
-#: gschem/src/i_callbacks.c:2181
+#: gschem/src/i_callbacks.c:2188
msgid "Paste 5"
msgstr "Colar de 5"
-#: gschem/src/i_callbacks.c:2318 gschem/src/x_window.c:355
+#: gschem/src/i_callbacks.c:2325 gschem/src/x_window.c:355
msgid "Component"
msgstr "Componente"
-#: gschem/src/i_callbacks.c:2354 gschem/src/i_callbacks.c:2373
-#: gschem/src/x_dialog.c:2285
+#: gschem/src/i_callbacks.c:2361 gschem/src/i_callbacks.c:2380
+#: gschem/src/x_dialog.c:2289
msgid "Attribute"
msgstr "Atributo"
-#: gschem/src/i_callbacks.c:2395 gschem/src/i_callbacks.c:2422
-#: gschem/src/x_dialog.c:2282
+#: gschem/src/i_callbacks.c:2402 gschem/src/i_callbacks.c:2429
+#: gschem/src/x_dialog.c:2286
msgid "Net"
msgstr "Conexão"
-#: gschem/src/i_callbacks.c:2466 gschem/src/i_callbacks.c:2493
-#: gschem/src/x_dialog.c:2300 gschem/src/x_window.c:375
+#: gschem/src/i_callbacks.c:2473 gschem/src/i_callbacks.c:2500
+#: gschem/src/x_dialog.c:2304 gschem/src/x_window.c:375
msgid "Bus"
msgstr "Barramento"
-#: gschem/src/i_callbacks.c:2574 gschem/src/i_callbacks.c:2597
+#: gschem/src/i_callbacks.c:2581 gschem/src/i_callbacks.c:2604
msgid "Line"
msgstr "Linha"
-#: gschem/src/i_callbacks.c:2619 gschem/src/i_callbacks.c:2642
+#: gschem/src/i_callbacks.c:2626 gschem/src/i_callbacks.c:2649
msgid "Box"
msgstr "Caixa"
-#: gschem/src/i_callbacks.c:2698 gschem/src/i_callbacks.c:2722
+#: gschem/src/i_callbacks.c:2705 gschem/src/i_callbacks.c:2729
msgid "Circle"
msgstr "CÃrculo"
-#: gschem/src/i_callbacks.c:2744 gschem/src/i_callbacks.c:2767
+#: gschem/src/i_callbacks.c:2751 gschem/src/i_callbacks.c:2774
msgid "Arc"
msgstr "Arco"
-#: gschem/src/i_callbacks.c:2789 gschem/src/i_callbacks.c:2812
-#: gschem/src/x_dialog.c:2273
+#: gschem/src/i_callbacks.c:2796 gschem/src/i_callbacks.c:2819
+#: gschem/src/x_dialog.c:2277
msgid "Pin"
msgstr "Pino"
-#: gschem/src/i_callbacks.c:2871
+#: gschem/src/i_callbacks.c:2878
#, c-format
msgid "Searching for source [%s]\n"
msgstr "Procurando por origem [%s]\n"
-#: gschem/src/i_callbacks.c:2895
+#: gschem/src/i_callbacks.c:2902
#, c-format
msgid "Cannot find source [%s]\n"
msgstr "ImpossÃvel encontrar origem [%s]\n"
-#: gschem/src/i_callbacks.c:2964
+#: gschem/src/i_callbacks.c:2965
#, c-format
msgid "Searching for symbol [%s]\n"
msgstr "Procurando por sÃmbolo [%s]\n"
-#: gschem/src/i_callbacks.c:2970
+#: gschem/src/i_callbacks.c:2971
msgid "Symbol is not a real file. Symbol cannot be loaded.\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3001
+#: gschem/src/i_callbacks.c:3002
msgid "Cannot find any schematics above the current one!\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3055
+#: gschem/src/i_callbacks.c:3056
msgid ""
"This command retrieves the component documentation from the web, but there "
"is no component selected"
@@ -615,84 +601,84 @@ msgstr ""
"Este comando recupera a documentação do componente da web, mas não há nenhum "
"componente seleccionado"
-#: gschem/src/i_callbacks.c:3083
+#: gschem/src/i_callbacks.c:3084
msgid "Attach"
msgstr "Anexar"
-#: gschem/src/i_callbacks.c:3130
+#: gschem/src/i_callbacks.c:3131
msgid "Detach"
msgstr "Desanexar"
-#: gschem/src/i_callbacks.c:3165
+#: gschem/src/i_callbacks.c:3166
msgid "ShowN"
msgstr "Mostrar N"
-#: gschem/src/i_callbacks.c:3201
+#: gschem/src/i_callbacks.c:3202
msgid "ShowV"
msgstr "Mostrar V"
-#: gschem/src/i_callbacks.c:3237
+#: gschem/src/i_callbacks.c:3238
msgid "ShowB"
msgstr "Mostrar T"
-#: gschem/src/i_callbacks.c:3274
+#: gschem/src/i_callbacks.c:3275
msgid "VisToggle"
msgstr "Comuta Visibilidade"
-#: gschem/src/i_callbacks.c:3304
+#: gschem/src/i_callbacks.c:3305
#, c-format
msgid "Sorry but this is a non-functioning menu option\n"
msgstr "Desculpe, mas esta é uma opção de menu sem função\n"
-#: gschem/src/i_callbacks.c:3394
+#: gschem/src/i_callbacks.c:3395
msgid "Action feedback mode set to OUTLINE\n"
msgstr "Retorno de ação ajustado para silhueta\n"
-#: gschem/src/i_callbacks.c:3397
+#: gschem/src/i_callbacks.c:3398
msgid "Action feedback mode set to BOUNDINGBOX\n"
msgstr "Retorno de ação ajustado para caixa completa\n"
-#: gschem/src/i_callbacks.c:3422
+#: gschem/src/i_callbacks.c:3423
msgid "Grid OFF\n"
msgstr "Grade DESLIGADA\n"
-#: gschem/src/i_callbacks.c:3423
+#: gschem/src/i_callbacks.c:3424
msgid "Dot grid selected\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3424
+#: gschem/src/i_callbacks.c:3425
msgid "Mesh grid selected\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3445
+#: gschem/src/i_callbacks.c:3446
msgid "Snap OFF (CAUTION!)\n"
msgstr "Agarre desligado (CUIDADO!)\n"
-#: gschem/src/i_callbacks.c:3448
+#: gschem/src/i_callbacks.c:3449
msgid "Snap ON\n"
msgstr "Agarre ligado\n"
-#: gschem/src/i_callbacks.c:3451
+#: gschem/src/i_callbacks.c:3452
msgid "Snap back to the grid (CAUTION!)\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3477
+#: gschem/src/i_callbacks.c:3478
msgid "Rubber band OFF \n"
msgstr "Elástico desligado \n"
-#: gschem/src/i_callbacks.c:3480
+#: gschem/src/i_callbacks.c:3481
msgid "Rubber band ON\n"
msgstr "Elástico ligado\n"
-#: gschem/src/i_callbacks.c:3495
+#: gschem/src/i_callbacks.c:3496
msgid "magnetic net mode: ON\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3498
+#: gschem/src/i_callbacks.c:3499
msgid "magnetic net mode: OFF\n"
msgstr ""
-#: gschem/src/o_box.c:153
+#: gschem/src/o_box.c:149
#, c-format
msgid "Unknown type for box (fill)!\n"
msgstr "Tipo desconhecido para enchimento da caixa!\n"
@@ -712,17 +698,17 @@ msgstr ""
msgid "Got an invalid buffer_number [o_buffer_paste_start]\n"
msgstr "Tenho um buffer_number inválido [o_buffer_paste_start]\n"
-#: gschem/src/o_bus.c:118
+#: gschem/src/o_bus.c:117
#, c-format
msgid "Got an invalid which one in o_bus_draw_stretch\n"
msgstr ""
-#: gschem/src/o_circle.c:134
+#: gschem/src/o_circle.c:130
#, c-format
msgid "Unknown type for circle (fill)!\n"
msgstr "Tipo desconhecido para enchimento de arco!\n"
-#: gschem/src/o_complex.c:243 gschem/src/o_complex.c:247
+#: gschem/src/o_complex.c:237 gschem/src/o_complex.c:241
#, c-format
msgid "Translating schematic [%d %d]\n"
msgstr "Transladando diagrama [%d %d]\n"
@@ -740,37 +726,37 @@ msgstr "Objeto já travado\n"
msgid "Object already unlocked\n"
msgstr "Objeto já destravado\n"
-#: gschem/src/o_misc.c:413
+#: gschem/src/o_misc.c:409
msgid "Hidden text is now visible\n"
msgstr "Texto oculto agora está visÃvel\n"
-#: gschem/src/o_misc.c:415
+#: gschem/src/o_misc.c:411
msgid "Hidden text is now invisible\n"
msgstr "Texto oculto agora está invisÃvel\n"
-#: gschem/src/o_misc.c:668
+#: gschem/src/o_misc.c:636
#, c-format
msgid "Could not find symbol [%s] in library. Update failed.\n"
msgstr ""
"Não foi possÃvel encontrar o simbolo [%s] na biblioteca. Atualização falhou\n"
-#: gschem/src/o_misc.c:783
+#: gschem/src/o_misc.c:751
#, c-format
msgid "o_autosave_backups: Can't get the real filename of %s."
msgstr ""
"o_autosave_backups: Não foi possÃvel pegar o nome de arquivo real de %s"
-#: gschem/src/o_misc.c:827
+#: gschem/src/o_misc.c:795
#, c-format
msgid "Could NOT set previous backup file [%s] read-write\n"
msgstr "NÃ?O foi possÃvel deixar arquivo backup [%s] como leitura e gravação\n"
-#: gschem/src/o_misc.c:845
+#: gschem/src/o_misc.c:815
#, c-format
msgid "Could NOT set backup file [%s] readonly\n"
msgstr "NÃ?O foi possÃvel deixar arquivo backup [%s] apenas leitura!\n"
-#: gschem/src/o_misc.c:850
+#: gschem/src/o_misc.c:820
#, c-format
msgid "Could NOT save backup file [%s]\n"
msgstr "NÃ?O foi possÃvel salvar arquivo backup [%s] !\n"
@@ -790,36 +776,36 @@ msgstr ""
msgid "Got a non line object in o_move_check_endpoint\n"
msgstr "Encontrei um objeto que não é linha em o_move_check_endpoint\n"
-#: gschem/src/o_net.c:159
+#: gschem/src/o_net.c:158
#, c-format
msgid "Got an invalid which one in o_net_draw_stretch\n"
msgstr ""
-#: gschem/src/o_net.c:538
+#: gschem/src/o_net.c:537
msgid "Warning: Starting net at off grid coordinate\n"
msgstr ""
-#: gschem/src/o_net.c:600
+#: gschem/src/o_net.c:599
msgid "Warning: Ending net at off grid coordinate\n"
msgstr ""
-#: gschem/src/o_net.c:932 gschem/src/o_net.c:969 gschem/src/o_net.c:1040
-#: gschem/src/o_net.c:1076
+#: gschem/src/o_net.c:931 gschem/src/o_net.c:968 gschem/src/o_net.c:1039
+#: gschem/src/o_net.c:1075
#, c-format
msgid "Tried to add more than two bus rippers. Internal gschem error.\n"
msgstr ""
-#: gschem/src/o_net.c:1144
+#: gschem/src/o_net.c:1143
#, c-format
msgid "Bus ripper symbol [%s] was not found in any component library\n"
msgstr ""
-#: gschem/src/o_path.c:352
+#: gschem/src/o_path.c:348
#, c-format
msgid "Unknown type for path (fill)!\n"
msgstr ""
-#: gschem/src/o_picture.c:163 gschem/src/o_picture.c:539
+#: gschem/src/o_picture.c:163 gschem/src/o_picture.c:537
#, c-format
msgid "Failed to load picture: %s"
msgstr "Falhou ao ler imagem: %s"
@@ -828,7 +814,7 @@ msgstr "Falhou ao ler imagem: %s"
msgid "Picture"
msgstr "Imagem"
-#: gschem/src/o_picture.c:447 gschem/src/x_attribedit.c:141
+#: gschem/src/o_picture.c:445 gschem/src/x_attribedit.c:141
#, c-format
msgid "ERROR: NULL object!\n"
msgstr "ERRO: NENHUM objeto!\n"
@@ -849,34 +835,46 @@ msgstr "Slots não disponÃvel para este componente\n"
msgid "New slot number out of range\n"
msgstr "Número de slot fora dos limites\n"
-#: gschem/src/o_undo.c:304
+#: gschem/src/o_undo.c:303
msgid "Undo/Redo disabled in rc file\n"
msgstr "Desfaz e Refaz desabilitado no arquivo rc\n"
-#: gschem/src/parsecmd.c:47
+#: gschem/src/parsecmd.c:81
#, c-format
msgid ""
-"Usage: %s [OPTIONS] schematic_filename1 ... schematic_filenameN\n"
-" -q Quiet mode\n"
-" -v Verbose mode on\n"
-" -r filename Rc filename\n"
-" -s filename Script (guile) filename\n"
-" -o filename Output filename (for printing)\n"
-" -p Automatically place the window\n"
-" -t Print stroke information\n"
-" -h Help; this message\n"
+"Usage: %s [OPTION ...] [--] [FILE ...]\n"
"\n"
-msgstr ""
-"Uso: %s [OPTIONS] esquematico1 ... esquematicoN\n"
-" -q modo Quieto\n"
-" -v Modo Verbose\n"
-" -r filename Arquivo Rc\n"
-" -s filename Arquivo Script (guile)\n"
-" -o filename Arquivo de saÃda (impressão)\n"
-" -p Auto aloca janela\n"
-" -t Imprime informação de strokes\n"
-" -h Ajuda; esta mensagem\n"
+"Interactively edit gEDA schematics or symbols. If one or more FILEs\n"
+"are specified, open them for editing; otherwise, create a new, empty\n"
+"schematic.\n"
"\n"
+"Options:\n"
+" -q, --quiet Quiet mode.\n"
+" -v, --verbose Verbose mode.\n"
+" -r, --config-file=FILE Additional configuration file to load.\n"
+" -L DIR Add DIR to Scheme search path.\n"
+" -c EXPR Scheme expression to run at startup.\n"
+" -s FILE Scheme script to run at startup.\n"
+" -o, --output=FILE Output filename (for printing).\n"
+" -p Automatically place the window.\n"
+" -V, --version Show version information.\n"
+" -h, --help Help; this message.\n"
+" -- Treat all remaining arguments as filenames.\n"
+"\n"
+"Report bugs to <geda-bug@xxxxxxxx>\n"
+"gEDA/gaf homepage: <http://gpleda.org>\n"
+msgstr ""
+
+#: gschem/src/parsecmd.c:115
+#, c-format
+msgid ""
+"gEDA %s (g%.7s)\n"
+"Copyright (C) 1998-2011 gEDA developers\n"
+"This is free software, and you are welcome to redistribute it under\n"
+"certain conditions. For details, see the file `COPYING', which is\n"
+"included in the gEDA distribution.\n"
+"There is NO WARRANTY, to the extent permitted by law.\n"
+msgstr ""
#: gschem/src/x_attribedit.c:127
#, c-format
@@ -887,56 +885,56 @@ msgstr ""
msgid "Single Attribute Editor"
msgstr "Editor de um atributo"
-#: gschem/src/x_attribedit.c:358
+#: gschem/src/x_attribedit.c:359
msgid "<b>Edit Attribute</b>"
msgstr "<b>Editar Atributo</b>"
-#: gschem/src/x_attribedit.c:360
+#: gschem/src/x_attribedit.c:361
msgid "<b>Add Attribute</b>"
msgstr "<b>Adicionar Atributo</b>"
-#: gschem/src/x_attribedit.c:376 gschem/src/x_multiattrib.c:1916
+#: gschem/src/x_attribedit.c:377 gschem/src/x_multiattrib.c:1927
msgid "Name:"
msgstr "Nome:"
-#: gschem/src/x_attribedit.c:393 gschem/src/x_multiattrib.c:1935
+#: gschem/src/x_attribedit.c:394 gschem/src/x_multiattrib.c:1946
msgid "Value:"
msgstr "Valor:"
-#: gschem/src/x_attribedit.c:409 gschem/src/x_multiattrib.c:1978
+#: gschem/src/x_attribedit.c:410 gschem/src/x_multiattrib.c:1989
msgid "Visible"
msgstr "VisÃvel"
-#: gschem/src/x_attribedit.c:429
+#: gschem/src/x_attribedit.c:430
msgid "Show Value Only"
msgstr "Mostra apenas Valor"
-#: gschem/src/x_attribedit.c:431
+#: gschem/src/x_attribedit.c:432
msgid "Show Name Only"
msgstr "Mostra apenas Nome"
-#: gschem/src/x_attribedit.c:433 gschem/src/x_multiattrib.c:1454
+#: gschem/src/x_attribedit.c:434 gschem/src/x_multiattrib.c:1466
msgid "Show Name & Value"
msgstr "Mostra Nome e Valor"
-#: gschem/src/x_attribedit.c:440
+#: gschem/src/x_attribedit.c:441
msgid "<b>Attach Options</b>"
msgstr "<b>Anexar Opções</b>"
-#: gschem/src/x_attribedit.c:455
+#: gschem/src/x_attribedit.c:456
msgid "All"
msgstr "Todos"
-#: gschem/src/x_attribedit.c:463 gschem/src/x_compselect.c:896
-#: gschem/src/x_compselect.c:1010
+#: gschem/src/x_attribedit.c:464 gschem/src/x_compselect.c:904
+#: gschem/src/x_compselect.c:1018
msgid "Components"
msgstr "Componentes"
-#: gschem/src/x_attribedit.c:471 gschem/src/x_window.c:365
+#: gschem/src/x_attribedit.c:472 gschem/src/x_window.c:365
msgid "Nets"
msgstr "Conexões"
-#: gschem/src/x_attribedit.c:479
+#: gschem/src/x_attribedit.c:480
msgid "Replace existing attributes"
msgstr ""
@@ -952,91 +950,91 @@ msgid ""
"duplicate slot may cause problems: [symbolname=%s, number=%d, slot=%d]\n"
msgstr ""
-#: gschem/src/x_autonumber.c:673
+#: gschem/src/x_autonumber.c:675
msgid "No searchstring given in autonumber text.\n"
msgstr ""
-#: gschem/src/x_autonumber.c:725
+#: gschem/src/x_autonumber.c:727
msgid "No '*' or '?' given at the end of the autonumber text.\n"
msgstr ""
-#: gschem/src/x_autonumber.c:860
+#: gschem/src/x_autonumber.c:862
msgid "Diagonal"
msgstr "Diagonal"
-#: gschem/src/x_autonumber.c:861
+#: gschem/src/x_autonumber.c:863
msgid "Top to bottom"
msgstr "De cima para baixo"
-#: gschem/src/x_autonumber.c:861
+#: gschem/src/x_autonumber.c:863
msgid "Bottom to top"
msgstr "De baixo para cima"
-#: gschem/src/x_autonumber.c:862
+#: gschem/src/x_autonumber.c:864
msgid "Left to right"
msgstr "Da esquerda para direita"
-#: gschem/src/x_autonumber.c:862
+#: gschem/src/x_autonumber.c:864
msgid "Right to left"
msgstr "Da direita para a esquerda"
-#: gschem/src/x_autonumber.c:863
+#: gschem/src/x_autonumber.c:865
msgid "File order"
msgstr ""
-#: gschem/src/x_autonumber.c:1199
+#: gschem/src/x_autonumber.c:1201
msgid "Autonumber text"
msgstr "Autonumerar texto"
-#: gschem/src/x_autonumber.c:1223
+#: gschem/src/x_autonumber.c:1225
msgid "<b>Scope</b>"
msgstr "<b>Escopo</b>"
-#: gschem/src/x_autonumber.c:1245
+#: gschem/src/x_autonumber.c:1247
msgid "Search for:"
msgstr "Pesquisar por:"
-#: gschem/src/x_autonumber.c:1259
+#: gschem/src/x_autonumber.c:1261
msgid "Autonumber text in:"
msgstr "Auto numerar texto em:"
-#: gschem/src/x_autonumber.c:1266
+#: gschem/src/x_autonumber.c:1268
msgid "Skip numbers found in:"
msgstr ""
-#: gschem/src/x_autonumber.c:1278 gschem/src/x_autonumber.c:1287
+#: gschem/src/x_autonumber.c:1280 gschem/src/x_autonumber.c:1289
msgid "Selected objects"
msgstr "Selecionar Objetos"
-#: gschem/src/x_autonumber.c:1279 gschem/src/x_autonumber.c:1288
+#: gschem/src/x_autonumber.c:1281 gschem/src/x_autonumber.c:1290
msgid "Current page"
msgstr "Página Atual"
-#: gschem/src/x_autonumber.c:1280 gschem/src/x_autonumber.c:1289
+#: gschem/src/x_autonumber.c:1282 gschem/src/x_autonumber.c:1291
msgid "Whole hierarchy"
msgstr ""
-#: gschem/src/x_autonumber.c:1291
+#: gschem/src/x_autonumber.c:1293
msgid "Overwrite existing numbers"
msgstr ""
-#: gschem/src/x_autonumber.c:1296
+#: gschem/src/x_autonumber.c:1298
msgid "<b>Options</b>"
msgstr "<b>Opções</b>"
-#: gschem/src/x_autonumber.c:1318
+#: gschem/src/x_autonumber.c:1320
msgid "Starting number:"
msgstr ""
-#: gschem/src/x_autonumber.c:1325
+#: gschem/src/x_autonumber.c:1327
msgid "Sort order:"
msgstr ""
-#: gschem/src/x_autonumber.c:1346
+#: gschem/src/x_autonumber.c:1348
msgid "Remove numbers"
msgstr ""
-#: gschem/src/x_autonumber.c:1350
+#: gschem/src/x_autonumber.c:1352
msgid "Automatic slotting"
msgstr ""
@@ -1073,48 +1071,48 @@ msgstr "Tentou ter cor inválida: %d\n"
msgid "Tried to get an invalid outline color: %d\n"
msgstr ""
-#: gschem/src/x_compselect.c:1040
+#: gschem/src/x_compselect.c:1048
msgid "Filter:"
msgstr "Filtrar:"
-#: gschem/src/x_compselect.c:1143 gschem/src/x_dialog.c:3663
-#: gschem/src/x_multiattrib.c:1782
+#: gschem/src/x_compselect.c:1151 gschem/src/x_dialog.c:3667
+#: gschem/src/x_multiattrib.c:1793
msgid "Name"
msgstr "Nome"
-#: gschem/src/x_compselect.c:1152 gschem/src/x_multiattrib.c:1806
+#: gschem/src/x_compselect.c:1160 gschem/src/x_multiattrib.c:1817
msgid "Value"
msgstr "Valor"
-#: gschem/src/x_compselect.c:1191
+#: gschem/src/x_compselect.c:1199
msgid "Default behavior - reference component"
msgstr "Uso normal - referenciar componente"
-#: gschem/src/x_compselect.c:1194
+#: gschem/src/x_compselect.c:1202
msgid "Embed component in schematic"
msgstr "Embutir componente no diagrama"
-#: gschem/src/x_compselect.c:1197
+#: gschem/src/x_compselect.c:1205
msgid "Include component as individual objects"
msgstr "Incluir como objetos individuais"
-#: gschem/src/x_compselect.c:1354
+#: gschem/src/x_compselect.c:1362
msgid "Select Component..."
msgstr "Selecionar Componente"
-#: gschem/src/x_compselect.c:1377
+#: gschem/src/x_compselect.c:1385
msgid "In Use"
msgstr "Em Uso"
-#: gschem/src/x_compselect.c:1381
+#: gschem/src/x_compselect.c:1389
msgid "Libraries"
msgstr "Bibliotecas"
-#: gschem/src/x_compselect.c:1390 gschem/src/x_fileselect.c:122
+#: gschem/src/x_compselect.c:1398 gschem/src/x_fileselect.c:122
msgid "Preview"
msgstr "Prévia"
-#: gschem/src/x_compselect.c:1418
+#: gschem/src/x_compselect.c:1426
msgid "Attributes"
msgstr "Atributos"
@@ -1172,139 +1170,139 @@ msgstr "Dir Baixo"
msgid "Edit Text Properties"
msgstr "Editar Propriedades do Texto"
-#: gschem/src/x_dialog.c:471
+#: gschem/src/x_dialog.c:472
msgid "<b>Text Content</b>"
msgstr "<b>Conteúdo do Texto</b>"
-#: gschem/src/x_dialog.c:507
+#: gschem/src/x_dialog.c:508
msgid "<b>Text Properties</b>"
msgstr "<b>Propriedades do Texto</b>"
-#: gschem/src/x_dialog.c:522
+#: gschem/src/x_dialog.c:523
msgid "Color:"
msgstr "Cor:"
-#: gschem/src/x_dialog.c:529
+#: gschem/src/x_dialog.c:530
msgid "Size:"
msgstr "Tamanho:"
-#: gschem/src/x_dialog.c:538
+#: gschem/src/x_dialog.c:539
msgid "Alignment:"
msgstr "Alinhamento:"
-#: gschem/src/x_dialog.c:587
+#: gschem/src/x_dialog.c:588
msgid "Solid"
msgstr "Solido"
-#: gschem/src/x_dialog.c:588
+#: gschem/src/x_dialog.c:589
msgid "Dotted"
msgstr "Pontilhado"
-#: gschem/src/x_dialog.c:589
+#: gschem/src/x_dialog.c:590
msgid "Dashed"
msgstr "Tracejado"
-#: gschem/src/x_dialog.c:590
+#: gschem/src/x_dialog.c:591
msgid "Center"
msgstr "Centro"
-#: gschem/src/x_dialog.c:591
+#: gschem/src/x_dialog.c:592
msgid "Phantom"
msgstr "Fantasma"
-#: gschem/src/x_dialog.c:592 gschem/src/x_dialog.c:689
-#: gschem/src/x_dialog.c:698 gschem/src/x_dialog.c:707
-#: gschem/src/x_dialog.c:808 gschem/src/x_dialog.c:810
-#: gschem/src/x_dialog.c:812 gschem/src/x_dialog.c:1038
-#: gschem/src/x_dialog.c:1141 gschem/src/x_dialog.c:1150
-#: gschem/src/x_dialog.c:1159 gschem/src/x_dialog.c:1168
-#: gschem/src/x_dialog.c:1177 gschem/src/x_dialog.c:1290
-#: gschem/src/x_dialog.c:1292 gschem/src/x_dialog.c:1294
-#: gschem/src/x_dialog.c:1296 gschem/src/x_dialog.c:1298
+#: gschem/src/x_dialog.c:593 gschem/src/x_dialog.c:690
+#: gschem/src/x_dialog.c:699 gschem/src/x_dialog.c:708
+#: gschem/src/x_dialog.c:809 gschem/src/x_dialog.c:811
+#: gschem/src/x_dialog.c:813 gschem/src/x_dialog.c:1039
+#: gschem/src/x_dialog.c:1142 gschem/src/x_dialog.c:1151
+#: gschem/src/x_dialog.c:1160 gschem/src/x_dialog.c:1169
+#: gschem/src/x_dialog.c:1178 gschem/src/x_dialog.c:1291
+#: gschem/src/x_dialog.c:1293 gschem/src/x_dialog.c:1295
+#: gschem/src/x_dialog.c:1297 gschem/src/x_dialog.c:1299
msgid "*unchanged*"
msgstr "*inalterado*"
-#: gschem/src/x_dialog.c:916
+#: gschem/src/x_dialog.c:917
msgid "Edit Line Width & Type"
msgstr "Editar Largura e Tipo de Linha"
-#: gschem/src/x_dialog.c:955 gschem/src/x_print.c:307
+#: gschem/src/x_dialog.c:956 gschem/src/x_print.c:307
msgid "Type:"
msgstr "Tipo:"
-#: gschem/src/x_dialog.c:959
+#: gschem/src/x_dialog.c:960
msgid "Width:"
msgstr "Largura:"
-#: gschem/src/x_dialog.c:963
+#: gschem/src/x_dialog.c:964
msgid "Dash Length:"
msgstr ""
-#: gschem/src/x_dialog.c:967
+#: gschem/src/x_dialog.c:968
msgid "Dash Space:"
msgstr ""
-#: gschem/src/x_dialog.c:1034
+#: gschem/src/x_dialog.c:1035
msgid "Hollow"
msgstr "Vazio"
-#: gschem/src/x_dialog.c:1035
+#: gschem/src/x_dialog.c:1036
msgid "Filled"
msgstr "Preenchida"
-#: gschem/src/x_dialog.c:1036
+#: gschem/src/x_dialog.c:1037
msgid "Mesh"
msgstr "Malha"
-#: gschem/src/x_dialog.c:1037
+#: gschem/src/x_dialog.c:1038
msgid "Hatch"
msgstr "Linhas"
-#: gschem/src/x_dialog.c:1406
+#: gschem/src/x_dialog.c:1407
msgid "Edit Fill Type"
msgstr "Editar Preenchimento"
-#: gschem/src/x_dialog.c:1444
+#: gschem/src/x_dialog.c:1446
msgid "Fill Type:"
msgstr ""
-#: gschem/src/x_dialog.c:1448
+#: gschem/src/x_dialog.c:1450
msgid "Line Width:"
msgstr "Largura da Linha:"
-#: gschem/src/x_dialog.c:1452
+#: gschem/src/x_dialog.c:1454
msgid "Angle 1:"
msgstr ""
-#: gschem/src/x_dialog.c:1456
+#: gschem/src/x_dialog.c:1458
msgid "Pitch 1:"
msgstr ""
-#: gschem/src/x_dialog.c:1460
+#: gschem/src/x_dialog.c:1462
msgid "Angle 2:"
msgstr "Ã?ngulo 2:"
-#: gschem/src/x_dialog.c:1464
+#: gschem/src/x_dialog.c:1466
msgid "Pitch 2:"
msgstr ""
-#: gschem/src/x_dialog.c:1591
+#: gschem/src/x_dialog.c:1593
msgid "Arc Params"
msgstr "Parametros do Arco"
-#: gschem/src/x_dialog.c:1631
+#: gschem/src/x_dialog.c:1634
msgid "Arc Radius:"
msgstr ""
-#: gschem/src/x_dialog.c:1639
+#: gschem/src/x_dialog.c:1642
msgid "Start Angle:"
msgstr "Ã?ngulo Inicial:"
-#: gschem/src/x_dialog.c:1647
+#: gschem/src/x_dialog.c:1650
msgid "Degrees of Sweep:"
msgstr ""
-#: gschem/src/x_dialog.c:1764
+#: gschem/src/x_dialog.c:1768
msgid ""
"Offset to translate?\n"
"(0 for origin)"
@@ -1312,200 +1310,200 @@ msgstr ""
"Valor a transladar?\n"
"(0 para origem)"
-#: gschem/src/x_dialog.c:1832
+#: gschem/src/x_dialog.c:1836
msgid "Text Size"
msgstr "Tamanho do Texto"
-#: gschem/src/x_dialog.c:1862
+#: gschem/src/x_dialog.c:1866
msgid "Enter new text size:"
msgstr ""
-#: gschem/src/x_dialog.c:1938
+#: gschem/src/x_dialog.c:1942
msgid "Snap Size"
msgstr ""
-#: gschem/src/x_dialog.c:1968
+#: gschem/src/x_dialog.c:1972
msgid "Enter new snap grid spacing:"
msgstr ""
-#: gschem/src/x_dialog.c:2045
+#: gschem/src/x_dialog.c:2049
msgid "Edit slot number"
msgstr "Editar número de SLOT"
-#: gschem/src/x_dialog.c:2076
+#: gschem/src/x_dialog.c:2080
msgid "Edit slot number:"
msgstr ""
-#: gschem/src/x_dialog.c:2117
+#: gschem/src/x_dialog.c:2121
#, c-format
msgid "%s%s (%s)"
msgstr ""
-#: gschem/src/x_dialog.c:2140
+#: gschem/src/x_dialog.c:2144
msgid "About gschem"
msgstr "Sobre gschem"
-#: gschem/src/x_dialog.c:2141
+#: gschem/src/x_dialog.c:2145
msgid "gEDA: GPL Electronic Design Automation"
msgstr ""
-#: gschem/src/x_dialog.c:2142
+#: gschem/src/x_dialog.c:2146
msgid ""
"Copyright © 1998-2009 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
"Copyright © 1998-2009 gEDA Contributors (see ChangeLog for details)"
msgstr ""
-#: gschem/src/x_dialog.c:2201
+#: gschem/src/x_dialog.c:2205
msgid "Coords"
msgstr "Coordenadas"
-#: gschem/src/x_dialog.c:2222
+#: gschem/src/x_dialog.c:2226
msgid "Screen"
msgstr "Janela"
-#: gschem/src/x_dialog.c:2231
+#: gschem/src/x_dialog.c:2235
msgid "World"
msgstr "Universo"
-#: gschem/src/x_dialog.c:2270
+#: gschem/src/x_dialog.c:2274
msgid "Background"
msgstr ""
-#: gschem/src/x_dialog.c:2276
+#: gschem/src/x_dialog.c:2280
msgid "Net endpoint"
msgstr ""
-#: gschem/src/x_dialog.c:2279
+#: gschem/src/x_dialog.c:2283
msgid "Graphic"
msgstr ""
-#: gschem/src/x_dialog.c:2288
+#: gschem/src/x_dialog.c:2292
msgid "Logic bubble"
msgstr ""
-#: gschem/src/x_dialog.c:2291
+#: gschem/src/x_dialog.c:2295
msgid "Grid point"
msgstr ""
-#: gschem/src/x_dialog.c:2294
+#: gschem/src/x_dialog.c:2298
msgid "Detached attribute"
msgstr ""
-#: gschem/src/x_dialog.c:2297 gschem/src/x_window.c:383
+#: gschem/src/x_dialog.c:2301 gschem/src/x_window.c:383
msgid "Text"
msgstr "Texto"
-#: gschem/src/x_dialog.c:2303
+#: gschem/src/x_dialog.c:2307
msgid "Selection"
msgstr ""
-#: gschem/src/x_dialog.c:2306
+#: gschem/src/x_dialog.c:2310
msgid "Bounding box"
msgstr ""
-#: gschem/src/x_dialog.c:2309
+#: gschem/src/x_dialog.c:2313
msgid "Zoom box"
msgstr ""
-#: gschem/src/x_dialog.c:2318
+#: gschem/src/x_dialog.c:2322
msgid "Output background"
msgstr ""
-#: gschem/src/x_dialog.c:2321
+#: gschem/src/x_dialog.c:2325
msgid "Net junction"
msgstr ""
-#: gschem/src/x_dialog.c:2324
+#: gschem/src/x_dialog.c:2328
msgid "Mesh grid major"
msgstr ""
-#: gschem/src/x_dialog.c:2327
+#: gschem/src/x_dialog.c:2331
msgid "Mesh grid minor"
msgstr ""
-#: gschem/src/x_dialog.c:2330
+#: gschem/src/x_dialog.c:2334
msgid "Unknown"
msgstr ""
-#: gschem/src/x_dialog.c:2481
+#: gschem/src/x_dialog.c:2485
#, c-format
msgid "ERROR: NULL object in color_edit_dialog_apply!\n"
msgstr ""
-#: gschem/src/x_dialog.c:2525
+#: gschem/src/x_dialog.c:2529
msgid "Color Edit"
msgstr "Edição de Cor"
-#: gschem/src/x_dialog.c:2556
+#: gschem/src/x_dialog.c:2560
msgid "Object color:"
msgstr ""
-#: gschem/src/x_dialog.c:2614
+#: gschem/src/x_dialog.c:2618
msgid "Hotkeys"
msgstr "Teclas de atalho"
-#: gschem/src/x_dialog.c:2678
+#: gschem/src/x_dialog.c:2682
msgid "Function"
msgstr "Função"
-#: gschem/src/x_dialog.c:2685
+#: gschem/src/x_dialog.c:2689
msgid "Keystroke(s)"
msgstr "Pressionamentos de tecla"
-#: gschem/src/x_dialog.c:2991
+#: gschem/src/x_dialog.c:2995
msgid "Find Text"
msgstr "Localizar Texto"
-#: gschem/src/x_dialog.c:3022
+#: gschem/src/x_dialog.c:3026
msgid "Text to find:"
msgstr "Loc. Texto:"
-#: gschem/src/x_dialog.c:3032
+#: gschem/src/x_dialog.c:3036
msgid "descend into hierarchy"
msgstr "Desce à hierarquia"
-#: gschem/src/x_dialog.c:3097
+#: gschem/src/x_dialog.c:3101
msgid "Hide Text"
msgstr "Esconder Texto"
-#: gschem/src/x_dialog.c:3128
+#: gschem/src/x_dialog.c:3132
msgid "Hide text starting with:"
msgstr "Ocultar texto iniciado com:"
-#: gschem/src/x_dialog.c:3197
+#: gschem/src/x_dialog.c:3201
msgid "Show Text"
msgstr "Mostrar texto"
-#: gschem/src/x_dialog.c:3228
+#: gschem/src/x_dialog.c:3232
msgid "Show text starting with:"
msgstr "Mostrar texto iniciado com:"
-#: gschem/src/x_dialog.c:3685
+#: gschem/src/x_dialog.c:3689
msgid "S_elect the schematics you want to save:"
msgstr ""
-#: gschem/src/x_dialog.c:3779
+#: gschem/src/x_dialog.c:3784
#, c-format
msgid "Save the changes to schematic \"%s\" before closing?"
msgstr ""
-#: gschem/src/x_dialog.c:3785
+#: gschem/src/x_dialog.c:3790
#, c-format
msgid ""
"There are %d schematics with unsaved changes. Save changes before closing?"
msgstr ""
-#: gschem/src/x_dialog.c:3814
+#: gschem/src/x_dialog.c:3819
msgid "If you don't save, all your changes will be permanently lost."
msgstr ""
"Se você não salvar, todas as suas modificações serão permanentemente "
"perdidas."
-#: gschem/src/x_dialog.c:3834
+#: gschem/src/x_dialog.c:3839
msgid "_Close without saving"
msgstr "_Fechar sem salvar"
-#: gschem/src/x_dialog.c:4170
+#: gschem/src/x_dialog.c:4175
#, c-format
msgid ""
"<span weight=\"bold\" size=\"larger\">The input attribute \"%s\" is invalid\n"
@@ -1523,19 +1521,19 @@ msgstr ""
"O nome não pode acabar com espaço.\n"
"O valor não pode começar com espaço."
-#: gschem/src/x_dialog.c:4172
+#: gschem/src/x_dialog.c:4177
msgid "Invalid Attribute"
msgstr "Atributo Inválido"
-#: gschem/src/x_dialog.c:4208
+#: gschem/src/x_dialog.c:4213
msgid "Pin type"
msgstr ""
-#: gschem/src/x_dialog.c:4232
+#: gschem/src/x_dialog.c:4237
msgid "Net pin"
msgstr ""
-#: gschem/src/x_dialog.c:4234
+#: gschem/src/x_dialog.c:4239
msgid "Bus pin (graphical)"
msgstr ""
@@ -1628,11 +1626,11 @@ msgstr "Tipo de imagem"
msgid "Write image..."
msgstr "Gravar imagem..."
-#: gschem/src/x_log.c:188
+#: gschem/src/x_log.c:209
msgid "** Invalid UTF-8 in log message. See stderr or gschem.log.\n"
msgstr ""
-#: gschem/src/x_log.c:256
+#: gschem/src/x_log.c:288
msgid "Status"
msgstr "Status"
@@ -1708,69 +1706,60 @@ msgstr "/Descer ao SÃmbolo"
msgid "/Up"
msgstr "/Subir"
-#: gschem/src/x_menus.c:321
+#: gschem/src/x_menus.c:323
#, c-format
msgid "Tried to set the sensitivity on non-existent menu item '%s'\n"
msgstr ""
-#: gschem/src/x_menus.c:345
+#: gschem/src/x_menus.c:347
msgid "Popup_menu_item_factory doesn't exist!\n"
msgstr ""
-#: gschem/src/x_menus.c:358
+#: gschem/src/x_menus.c:360
msgid "Tried to set the sensitivity on a non-existent popup menu_item\n"
msgstr ""
-#: gschem/src/x_menus.c:438
-#, c-format
-msgid "Couldn't open file %s\n"
-msgstr ""
-
-#: gschem/src/x_menus.c:495
-msgid "Clear"
-msgstr "Limpar"
-
-#: gschem/src/x_multiattrib.c:911
+#: gschem/src/x_multiattrib.c:915
msgid "Attributes with empty name are not allowed. Please set a name."
msgstr "Atributos com nome vazio não permitidos. Defina um nome."
-#: gschem/src/x_multiattrib.c:1456
+#: gschem/src/x_multiattrib.c:1468
msgid "Show Value only"
msgstr "Mostra apenas Valor"
-#: gschem/src/x_multiattrib.c:1458
+#: gschem/src/x_multiattrib.c:1470
msgid "Show Name only"
msgstr "Mostra apenas Nome"
-#: gschem/src/x_multiattrib.c:1486
+#: gschem/src/x_multiattrib.c:1498
msgid "Promote"
msgstr ""
-#: gschem/src/x_multiattrib.c:1490
+#: gschem/src/x_multiattrib.c:1502
msgid "Duplicate"
msgstr "Duplicar"
-#: gschem/src/x_multiattrib.c:1708
+#: gschem/src/x_multiattrib.c:1719
msgid "Edit Attributes"
msgstr "Editar Atributos"
-#: gschem/src/x_multiattrib.c:1826
+#: gschem/src/x_multiattrib.c:1837
msgid "Vis?"
msgstr "Vis?"
-#: gschem/src/x_multiattrib.c:1844
+#: gschem/src/x_multiattrib.c:1855
msgid "N"
msgstr "N"
-#: gschem/src/x_multiattrib.c:1862
+#: gschem/src/x_multiattrib.c:1873
msgid "V"
msgstr "V"
-#: gschem/src/x_multiattrib.c:1884
+#: gschem/src/x_multiattrib.c:1895
msgid "Show inherited attributes"
msgstr ""
-#: gschem/src/x_multiattrib.c:1900
+#: gschem/src/x_multiattrib.c:1911
msgid "Add Attribute"
msgstr "Inserir Atributo"
@@ -1794,23 +1783,23 @@ msgstr "Fechar Página"
msgid "Discard Page"
msgstr "Descartar"
-#: gschem/src/x_pagesel.c:376
+#: gschem/src/x_pagesel.c:375
msgid "Page Manager"
msgstr "Gerenciador de Páginas"
-#: gschem/src/x_pagesel.c:432
+#: gschem/src/x_pagesel.c:431
msgid "Filename"
msgstr "Nome do arquivo"
-#: gschem/src/x_pagesel.c:448
+#: gschem/src/x_pagesel.c:447
msgid "Changed"
msgstr "Alterado"
-#: gschem/src/x_pagesel.c:468
+#: gschem/src/x_pagesel.c:467
msgid "Right click on the filename for more options..."
msgstr "Clique direito no arquivo para opções..."
-#: gschem/src/x_preview.c:234
+#: gschem/src/x_preview.c:233
msgid "Preview Buffer"
msgstr ""
@@ -1866,23 +1855,23 @@ msgstr "Arquivo:"
msgid "Command:"
msgstr "Comando:"
-#: gschem/src/x_print.c:741
+#: gschem/src/x_print.c:745
msgid "No print destination specified\n"
msgstr ""
-#: gschem/src/x_print.c:748
+#: gschem/src/x_print.c:752
#, c-format
msgid "Cannot print current schematic to [%s]\n"
msgstr "Não consigo imprimir para arquivo [%s]\n"
-#: gschem/src/x_print.c:757
+#: gschem/src/x_print.c:761
#, c-format
msgid ""
"Error printing to file '%s'\n"
"Check the log window for more information"
msgstr ""
-#: gschem/src/x_print.c:764
+#: gschem/src/x_print.c:768
#, c-format
msgid "Printed current schematic to [%s]\n"
msgstr "Diagrama atual impresso para [%s]\n"
@@ -1891,6 +1880,11 @@ msgstr "Diagrama atual impresso para [%s]\n"
msgid "Execute Script..."
msgstr "Script..."
+#: gschem/src/x_script.c:66
+#, c-format
+msgid "Executing guile script [%s]\n"
+msgstr "Executando script guile [%s]\n"
+
#: gschem/src/x_window.c:81
#, c-format
msgid "Couldn't allocate gc\n"
@@ -2006,35 +2000,35 @@ msgstr ""
msgid "New file [%s]\n"
msgstr ""
-#: gschem/src/x_window.c:857
+#: gschem/src/x_window.c:855
#, c-format
msgid "Could NOT save page [%s]\n"
msgstr ""
-#: gschem/src/x_window.c:858
+#: gschem/src/x_window.c:856
msgid "Error while trying to save"
msgstr "Erro tentando salvar"
-#: gschem/src/x_window.c:867
+#: gschem/src/x_window.c:865
#, c-format
msgid "Saved as [%s]\n"
msgstr "Salvar como [%s]\n"
-#: gschem/src/x_window.c:869
+#: gschem/src/x_window.c:867
#, c-format
msgid "Saved [%s]\n"
msgstr "Salvo [%s]\n"
-#: gschem/src/x_window.c:871
+#: gschem/src/x_window.c:869
msgid "Saved"
msgstr "Salvo"
-#: gschem/src/x_window.c:945
+#: gschem/src/x_window.c:943
#, c-format
msgid "Discarding page [%s]\n"
msgstr "Descartando página [%s]\n"
-#: gschem/src/x_window.c:945
+#: gschem/src/x_window.c:943
#, c-format
msgid "Closing [%s]\n"
msgstr "Fechando [%s]\n"
@@ -2075,7 +2069,7 @@ msgstr ""
msgid "Save All"
msgstr "Salvar Tudo"
-#: gschem/lib/system-gschemrc.scm:1386 gschem/lib/system-gschemrc.scm:1477
+#: gschem/lib/system-gschemrc.scm:1386 gschem/lib/system-gschemrc.scm:1478
msgid "_Revert"
msgstr ""
@@ -2087,7 +2081,7 @@ msgstr ""
msgid "Write _image..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1393 gschem/lib/system-gschemrc.scm:1478
+#: gschem/lib/system-gschemrc.scm:1393 gschem/lib/system-gschemrc.scm:1479
msgid "_Close"
msgstr ""
@@ -2119,390 +2113,431 @@ msgstr ""
msgid "_Delete"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1412
+#: gschem/lib/system-gschemrc.scm:1409
+#, fuzzy
+msgid "Select All"
+msgstr "Selecionar"
+
+#: gschem/lib/system-gschemrc.scm:1410
+#, fuzzy
+msgid "Deselect"
+msgstr "Selecionar"
+
+#: gschem/lib/system-gschemrc.scm:1414
msgid "Rotate 90 Mode"
msgstr "Modo de Rotação"
-#: gschem/lib/system-gschemrc.scm:1415
+#: gschem/lib/system-gschemrc.scm:1417
msgid "Edit..."
msgstr "Editar..."
-#: gschem/lib/system-gschemrc.scm:1416
+#: gschem/lib/system-gschemrc.scm:1418
msgid "Edit Text..."
msgstr "Editar Texto..."
-#: gschem/lib/system-gschemrc.scm:1417
+#: gschem/lib/system-gschemrc.scm:1419
msgid "Slot..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1418
+#: gschem/lib/system-gschemrc.scm:1420
msgid "Color..."
msgstr "Cor..."
-#: gschem/lib/system-gschemrc.scm:1419
+#: gschem/lib/system-gschemrc.scm:1421
msgid "Line Width & Type..."
msgstr "Largura/Tipo de Linha..."
-#: gschem/lib/system-gschemrc.scm:1420
+#: gschem/lib/system-gschemrc.scm:1422
msgid "Fill Type..."
msgstr "Preenchimento..."
-#: gschem/lib/system-gschemrc.scm:1421
+#: gschem/lib/system-gschemrc.scm:1423
msgid "Symbol Translate..."
msgstr "Transladar..."
-#: gschem/lib/system-gschemrc.scm:1425
+#: gschem/lib/system-gschemrc.scm:1427
msgid "Invoke Macro"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1426
+#: gschem/lib/system-gschemrc.scm:1428
msgid "Embed Component/Picture"
msgstr "Embutir Componente/Imagem"
-#: gschem/lib/system-gschemrc.scm:1427
+#: gschem/lib/system-gschemrc.scm:1429
msgid "Unembed Component/Picture"
msgstr "Desembutir Componente/Imagem"
-#: gschem/lib/system-gschemrc.scm:1428
+#: gschem/lib/system-gschemrc.scm:1430
msgid "Update Component"
msgstr "Atualizar Componente"
-#: gschem/lib/system-gschemrc.scm:1429
+#: gschem/lib/system-gschemrc.scm:1431
msgid "Show/Hide Inv Text"
msgstr "Exibir/Ocultar textos ocultos"
-#: gschem/lib/system-gschemrc.scm:1430
-msgid "Make Inv Text Vis"
-msgstr "Tornar todos textos visÃveis"
-
-#: gschem/lib/system-gschemrc.scm:1436
+#: gschem/lib/system-gschemrc.scm:1437
msgid "Copy into 1"
msgstr "Copiar para 1"
-#: gschem/lib/system-gschemrc.scm:1437
+#: gschem/lib/system-gschemrc.scm:1438
msgid "Copy into 2"
msgstr "Copiar para 2"
-#: gschem/lib/system-gschemrc.scm:1438
+#: gschem/lib/system-gschemrc.scm:1439
msgid "Copy into 3"
msgstr "Copiar para 3"
-#: gschem/lib/system-gschemrc.scm:1439
+#: gschem/lib/system-gschemrc.scm:1440
msgid "Copy into 4"
msgstr "Copiar para 4"
-#: gschem/lib/system-gschemrc.scm:1440
+#: gschem/lib/system-gschemrc.scm:1441
msgid "Copy into 5"
msgstr "Copiar para 5"
-#: gschem/lib/system-gschemrc.scm:1441
+#: gschem/lib/system-gschemrc.scm:1442
msgid "Cut into 1"
msgstr "Cortar para 1"
-#: gschem/lib/system-gschemrc.scm:1442
+#: gschem/lib/system-gschemrc.scm:1443
msgid "Cut into 2"
msgstr "Cortar para 2"
-#: gschem/lib/system-gschemrc.scm:1443
+#: gschem/lib/system-gschemrc.scm:1444
msgid "Cut into 3"
msgstr "Cortar para 3"
-#: gschem/lib/system-gschemrc.scm:1444
+#: gschem/lib/system-gschemrc.scm:1445
msgid "Cut into 4"
msgstr "Cortar para 4"
-#: gschem/lib/system-gschemrc.scm:1445
+#: gschem/lib/system-gschemrc.scm:1446
msgid "Cut into 5"
msgstr "Cortar para 5"
-#: gschem/lib/system-gschemrc.scm:1446
+#: gschem/lib/system-gschemrc.scm:1447
msgid "Paste from 1"
msgstr "Colar de 1"
-#: gschem/lib/system-gschemrc.scm:1447
+#: gschem/lib/system-gschemrc.scm:1448
msgid "Paste from 2"
msgstr "Colar de 2"
-#: gschem/lib/system-gschemrc.scm:1448
+#: gschem/lib/system-gschemrc.scm:1449
msgid "Paste from 3"
msgstr "Colar de 3"
-#: gschem/lib/system-gschemrc.scm:1449
+#: gschem/lib/system-gschemrc.scm:1450
msgid "Paste from 4"
msgstr "Colar de 4"
-#: gschem/lib/system-gschemrc.scm:1450
+#: gschem/lib/system-gschemrc.scm:1451
msgid "Paste from 5"
msgstr "Colar de 5"
-#: gschem/lib/system-gschemrc.scm:1456
+#: gschem/lib/system-gschemrc.scm:1457
msgid "_Redraw"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1457
+#: gschem/lib/system-gschemrc.scm:1458
msgid "_Pan"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1458
+#: gschem/lib/system-gschemrc.scm:1459
msgid "Zoom _Box"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1459
+#: gschem/lib/system-gschemrc.scm:1460
msgid "Zoom _Extents"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1460
+#: gschem/lib/system-gschemrc.scm:1461
msgid "Zoom _In"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1461
+#: gschem/lib/system-gschemrc.scm:1462
msgid "Zoom _Out"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1462
+#: gschem/lib/system-gschemrc.scm:1463
msgid "Zoom _Full"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1464
+#: gschem/lib/system-gschemrc.scm:1465
msgid "_Dark color scheme"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1465
+#: gschem/lib/system-gschemrc.scm:1466
msgid "_Light color scheme"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1466
+#: gschem/lib/system-gschemrc.scm:1467
msgid "B_W color scheme"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1473
+#: gschem/lib/system-gschemrc.scm:1474
msgid "_Manager..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1474
+#: gschem/lib/system-gschemrc.scm:1475
msgid "_Previous"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1475
+#: gschem/lib/system-gschemrc.scm:1476
msgid "_Next"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1476
+#: gschem/lib/system-gschemrc.scm:1477
msgid "Ne_w"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1480
+#: gschem/lib/system-gschemrc.scm:1481
msgid "_Discard"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1486
+#: gschem/lib/system-gschemrc.scm:1487
msgid "_Component..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1487
+#: gschem/lib/system-gschemrc.scm:1488
msgid "_Net"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1488
+#: gschem/lib/system-gschemrc.scm:1489
msgid "B_us"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1489
+#: gschem/lib/system-gschemrc.scm:1490
msgid "_Attribute..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1490
+#: gschem/lib/system-gschemrc.scm:1491
msgid "_Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1492
+#: gschem/lib/system-gschemrc.scm:1493
msgid "_Line"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1493
+#: gschem/lib/system-gschemrc.scm:1494
msgid "_Box"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1494
+#: gschem/lib/system-gschemrc.scm:1495
msgid "C_ircle"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1495
+#: gschem/lib/system-gschemrc.scm:1496
msgid "A_rc"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1496
+#: gschem/lib/system-gschemrc.scm:1497
msgid "_Pin"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1497
+#: gschem/lib/system-gschemrc.scm:1498
msgid "Pictu_re..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1503
+#: gschem/lib/system-gschemrc.scm:1504
msgid "_Down Schematic"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1504
+#: gschem/lib/system-gschemrc.scm:1505
msgid "Down _Symbol"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1505
+#: gschem/lib/system-gschemrc.scm:1506
msgid "_Up"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1506
+#: gschem/lib/system-gschemrc.scm:1507
msgid "D_ocumentation..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1512
+#: gschem/lib/system-gschemrc.scm:1513
msgid "_Attach"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1513
+#: gschem/lib/system-gschemrc.scm:1514
msgid "_Detach"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1514
+#: gschem/lib/system-gschemrc.scm:1515
msgid "Show _Value"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1515
+#: gschem/lib/system-gschemrc.scm:1516
msgid "Show _Name"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1516
+#: gschem/lib/system-gschemrc.scm:1517
msgid "Show _Both"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1517
+#: gschem/lib/system-gschemrc.scm:1518
msgid "_Toggle Visibility"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1519
+#: gschem/lib/system-gschemrc.scm:1520
msgid "_Find Specific Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1520
+#: gschem/lib/system-gschemrc.scm:1521
msgid "_Hide Specific Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1521
+#: gschem/lib/system-gschemrc.scm:1522
msgid "_Show Specific Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1522
+#: gschem/lib/system-gschemrc.scm:1523
msgid "A_utonumber Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1528
+#: gschem/lib/system-gschemrc.scm:1529
msgid "_Text Size..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1529
+#: gschem/lib/system-gschemrc.scm:1530
msgid "Cycle _grid styles"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1530
+#: gschem/lib/system-gschemrc.scm:1531
msgid "Toggle _Snap On/Off"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1531
+#: gschem/lib/system-gschemrc.scm:1532
msgid "Snap Grid S_pacing..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1532
+#: gschem/lib/system-gschemrc.scm:1533
msgid "Scale _up Grid Spacing"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1534
+#: gschem/lib/system-gschemrc.scm:1535
msgid "Scale _down Grid Spacing"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1536
+#: gschem/lib/system-gschemrc.scm:1537
msgid "Toggle _Outline/Box"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1538
+#: gschem/lib/system-gschemrc.scm:1539
msgid "Toggle Net _Rubberband"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1539
+#: gschem/lib/system-gschemrc.scm:1540
msgid "Toggle _Magnetic Net"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1540
+#: gschem/lib/system-gschemrc.scm:1541
msgid "Show _Log Window..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1542
+#: gschem/lib/system-gschemrc.scm:1543
msgid "Show _Coord Window..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1558
+#: gschem/lib/system-gschemrc.scm:1559
msgid "gEDA Docu_mentation..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1559
+#: gschem/lib/system-gschemrc.scm:1560
msgid "gschem _FAQ..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1560
+#: gschem/lib/system-gschemrc.scm:1561
msgid "gEDA _Wiki..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1561
+#: gschem/lib/system-gschemrc.scm:1562
msgid "Component D_ocumentation..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1563
+#: gschem/lib/system-gschemrc.scm:1564
msgid "_Hotkeys..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1564
+#: gschem/lib/system-gschemrc.scm:1565
msgid "_About..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1570
+#: gschem/lib/system-gschemrc.scm:1571
msgid "_File"
msgstr "Arquivo"
-#: gschem/lib/system-gschemrc.scm:1571
+#: gschem/lib/system-gschemrc.scm:1572
msgid "_Edit"
msgstr "_Editar"
-#: gschem/lib/system-gschemrc.scm:1572
+#: gschem/lib/system-gschemrc.scm:1573
msgid "_Buffer"
msgstr "_Buffer"
-#: gschem/lib/system-gschemrc.scm:1573
+#: gschem/lib/system-gschemrc.scm:1574
msgid "_View"
msgstr "Exibir"
-#: gschem/lib/system-gschemrc.scm:1574
+#: gschem/lib/system-gschemrc.scm:1575
msgid "_Page"
msgstr "_Página"
-#: gschem/lib/system-gschemrc.scm:1575
+#: gschem/lib/system-gschemrc.scm:1576
msgid "_Add"
msgstr "_Adicionar"
-#: gschem/lib/system-gschemrc.scm:1576
+#: gschem/lib/system-gschemrc.scm:1577
msgid "Hie_rarchy"
msgstr "Hie_rarquia"
-#: gschem/lib/system-gschemrc.scm:1577
+#: gschem/lib/system-gschemrc.scm:1578
msgid "A_ttributes"
msgstr "A_tributos"
-#: gschem/lib/system-gschemrc.scm:1578
+#: gschem/lib/system-gschemrc.scm:1579
msgid "_Options"
msgstr "_Opções"
-#: gschem/lib/system-gschemrc.scm:1579
+#: gschem/lib/system-gschemrc.scm:1580
msgid "_Help"
msgstr "Ajuda"
+#~ msgid "Scheme directory NOT set!\n"
+#~ msgstr "Diretório Scheme N�O ajustado!\n"
+
+#~ msgid "MakeVisible"
+#~ msgstr "Deixar VisÃvel"
+
+#~ msgid ""
+#~ "Usage: %s [OPTIONS] schematic_filename1 ... schematic_filenameN\n"
+#~ " -q Quiet mode\n"
+#~ " -v Verbose mode on\n"
+#~ " -r filename Rc filename\n"
+#~ " -s filename Script (guile) filename\n"
+#~ " -o filename Output filename (for printing)\n"
+#~ " -p Automatically place the window\n"
+#~ " -t Print stroke information\n"
+#~ " -h Help; this message\n"
+#~ "\n"
+#~ msgstr ""
+#~ "Uso: %s [OPTIONS] esquematico1 ... esquematicoN\n"
+#~ " -q modo Quieto\n"
+#~ " -v Modo Verbose\n"
+#~ " -r filename Arquivo Rc\n"
+#~ " -s filename Arquivo Script (guile)\n"
+#~ " -o filename Arquivo de saÃda (impressão)\n"
+#~ " -p Auto aloca janela\n"
+#~ " -t Imprime informação de strokes\n"
+#~ " -h Ajuda; esta mensagem\n"
+#~ "\n"
+
+#~ msgid "Clear"
+#~ msgstr "Limpar"
+
+#~ msgid "Make Inv Text Vis"
+#~ msgstr "Tornar todos textos visÃveis"
+
#~ msgid "Update Cues"
#~ msgstr "Atualiza dicas"
diff --git a/gschem/po/ru.po b/gschem/po/ru.po
index 9e2c71b..fcef772 100644
--- a/gschem/po/ru.po
+++ b/gschem/po/ru.po
@@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2010-11-07 13:37+0000\n"
+"POT-Creation-Date: 2011-01-16 00:11-0500\n"
"PO-Revision-Date: 2010-02-14 01:05+0000\n"
"Last-Translator: Sergey Alyoshin <alyoshin.s@xxxxxxxxx>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -23,17 +23,17 @@ msgstr ""
msgid "Zoom too small! Cannot zoom further.\n"
msgstr "Ð?аÑ?Ñ?Ñ?аб оÑ?енÑ? мал! Ð?евозможно далÑ?нейÑ?ее изменение.\n"
-#: gschem/src/g_funcs.c:339 gschem/src/i_callbacks.c:68
+#: gschem/src/g_funcs.c:347 gschem/src/i_callbacks.c:68
#, c-format
msgid "Could not fork\n"
msgstr "Ð?евозможно вÑ?полниÑ?Ñ? fork\n"
-#: gschem/src/g_funcs.c:355 gschem/src/i_callbacks.c:78
+#: gschem/src/g_funcs.c:363 gschem/src/i_callbacks.c:78
#, c-format
msgid "Could not invoke %s\n"
msgstr "Ð?евозможно вÑ?зваÑ?Ñ? %s\n"
-#: gschem/src/g_funcs.c:361 gschem/src/i_callbacks.c:82
+#: gschem/src/g_funcs.c:369 gschem/src/i_callbacks.c:82
msgid "Documentation commands not supported under MinGW.\n"
msgstr "Ð?омандÑ? докÑ?менÑ?аÑ?ии не поддеÑ?живаÑ?Ñ?Ñ?Ñ? в MinGW.\n"
@@ -128,12 +128,12 @@ msgstr "Ð?евеÑ?наÑ? добавка [%d] пеÑ?едана в zoom-gain\n"
msgid "Invalid number of steps [%d] scrollpan-steps\n"
msgstr "Ð?евеÑ?ное Ñ?иÑ?ло Ñ?агов [%d] scrollpan-steps\n"
-#: gschem/src/gschem.c:184
+#: gschem/src/gschem.c:188
#, c-format
msgid "gEDA/gschem version %s%s.%s\n"
msgstr "gEDA/gschem веÑ?Ñ?ии %s%s.%s\n"
-#: gschem/src/gschem.c:187
+#: gschem/src/gschem.c:191
msgid ""
"gEDA/gschem comes with ABSOLUTELY NO WARRANTY; see COPYING for more "
"details.\n"
@@ -141,14 +141,14 @@ msgstr ""
"gEDA/gschem поÑ?Ñ?авлÑ?еÑ?Ñ?Ñ? Ð?Ð?Ð? Ð?Ð?Ð?Ð?Ð¥-Ð?Ð?Ð?Ð? Ð?Ð?Ð Ð?Ð?ТÐ?Ð?; Ñ?м. Ñ?айл COPYING длÑ? "
"подÑ?обноÑ?Ñ?ей.\n"
-#: gschem/src/gschem.c:189
+#: gschem/src/gschem.c:193
msgid ""
"This is free software, and you are welcome to redistribute it under certain\n"
msgstr ""
"ÐÑ?о Ñ?вободное пÑ?огÑ?аммное обеÑ?пеÑ?ение и его можно Ñ?аÑ?пÑ?оÑ?Ñ?Ñ?анÑ?Ñ?Ñ? пÑ?и "
"опÑ?еделÑ?ннÑ?Ñ?\n"
-#: gschem/src/gschem.c:191
+#: gschem/src/gschem.c:195
msgid ""
"conditions; please see the COPYING file for more details.\n"
"\n"
@@ -156,17 +156,17 @@ msgstr ""
"Ñ?Ñ?ловиÑ?Ñ?. CмоÑ?Ñ?иÑ?е Ñ?айл COPYING длÑ? полÑ?Ñ?ениÑ? далÑ?нейÑ?ей инÑ?оÑ?маÑ?ии.\n"
"\n"
-#: gschem/src/gschem.c:194
+#: gschem/src/gschem.c:198
#, c-format
msgid "This is the MINGW32 port.\n"
msgstr "ÐÑ?о MINGW32 веÑ?Ñ?иÑ?.\n"
-#: gschem/src/gschem.c:198
+#: gschem/src/gschem.c:202
#, c-format
msgid "Current locale settings: %s\n"
msgstr "ТекÑ?Ñ?ие Ñ?Ñ?Ñ?ановки локализаÑ?ии: %s\n"
-#: gschem/src/gschem.c:213
+#: gschem/src/gschem.c:218
msgid ""
"You must set the GEDADATA environment variable!\n"
"\n"
@@ -178,31 +178,21 @@ msgstr ""
"gschem не можеÑ? найÑ?и Ñ?вои Ñ?айлÑ? даннÑ?Ñ?. Ð?Ñ? должнÑ? задаÑ?Ñ?\n"
"пеÑ?еменной окÑ?Ñ?жениÑ? GEDADATA иÑ? Ñ?аÑ?положение.\n"
-#: gschem/src/gschem.c:248
+#: gschem/src/gschem.c:256
#, c-format
msgid "Couldn't find init scm file [%s]\n"
msgstr "Ð?евозможно найÑ?и наÑ?алÑ?нÑ?й scm-Ñ?айл [%s]\n"
-#: gschem/src/gschem.c:252
+#: gschem/src/gschem.c:260
#, c-format
msgid "Read init scm file [%s]\n"
msgstr "ЧÑ?ение наÑ?алÑ?ного scm-Ñ?айла [%s]\n"
-#: gschem/src/gschem.c:256
+#: gschem/src/gschem.c:264
#, c-format
msgid "Failed to read init scm file [%s]\n"
msgstr "Ð?евозможно пÑ?оÑ?иÑ?аÑ?Ñ? наÑ?алÑ?нÑ?й scm-Ñ?айл [%s]\n"
-#: gschem/src/gschem.c:317
-#, c-format
-msgid "Scheme directory NOT set!\n"
-msgstr "Ð?аÑ?алог Ñ?Ñ?ем Ð?Ð? Ñ?Ñ?Ñ?ановлен!\n"
-
-#: gschem/src/gschem.c:324 gschem/src/x_script.c:66
-#, c-format
-msgid "Executing guile script [%s]\n"
-msgstr "Ð?апÑ?Ñ?каеÑ?Ñ?Ñ? guile-Ñ?кÑ?ипÑ? [%s]\n"
-
#: gschem/src/gschem_cairo.c:310
#, c-format
msgid "Unknown end for line (%d)\n"
@@ -226,11 +216,11 @@ msgstr "Режим Ñ?леменÑ?ов"
msgid "Text Mode"
msgstr "Режим Ñ?екÑ?Ñ?а"
-#: gschem/src/i_basic.c:84 gschem/lib/system-gschemrc.scm:1409
+#: gschem/src/i_basic.c:84 gschem/lib/system-gschemrc.scm:1411
msgid "Copy Mode"
msgstr "Режим копиÑ?ованиÑ?"
-#: gschem/src/i_basic.c:87 gschem/lib/system-gschemrc.scm:1411
+#: gschem/src/i_basic.c:87 gschem/lib/system-gschemrc.scm:1413
msgid "Move Mode"
msgstr "Режим пеÑ?емеÑ?ениÑ?"
@@ -238,7 +228,7 @@ msgstr "Режим пеÑ?емеÑ?ениÑ?"
msgid "Rotate Mode"
msgstr "Режим вÑ?аÑ?ениÑ?"
-#: gschem/src/i_basic.c:91 gschem/lib/system-gschemrc.scm:1413
+#: gschem/src/i_basic.c:91 gschem/lib/system-gschemrc.scm:1415
msgid "Mirror Mode"
msgstr "Режим зеÑ?калиÑ?ованиÑ?"
@@ -291,22 +281,22 @@ msgstr "ЧеÑ?Ñ?ение дÑ?г"
msgid "Pin Mode"
msgstr "Ð?обавление вÑ?водов"
-#: gschem/src/i_basic.c:135 gschem/src/i_callbacks.c:544
-#: gschem/src/i_callbacks.c:568
+#: gschem/src/i_basic.c:135 gschem/src/i_callbacks.c:576
+#: gschem/src/i_callbacks.c:600
msgid "Copy"
msgstr "Ð?опиÑ?оваÑ?Ñ?"
-#: gschem/src/i_basic.c:137 gschem/src/i_callbacks.c:634
-#: gschem/src/i_callbacks.c:658
+#: gschem/src/i_basic.c:137 gschem/src/i_callbacks.c:666
+#: gschem/src/i_callbacks.c:690
msgid "Move"
msgstr "Ð?еÑ?емеÑ?Ñ?иÑ?Ñ?"
-#: gschem/src/i_basic.c:139 gschem/src/i_callbacks.c:589
-#: gschem/src/i_callbacks.c:613
+#: gschem/src/i_basic.c:139 gschem/src/i_callbacks.c:621
+#: gschem/src/i_callbacks.c:645
msgid "Multiple Copy"
msgstr "Ð?ножеÑ?Ñ?венное копиÑ?ование"
-#: gschem/src/i_basic.c:142 gschem/lib/system-gschemrc.scm:1410
+#: gschem/src/i_basic.c:142 gschem/lib/system-gschemrc.scm:1412
msgid "Multiple Copy Mode"
msgstr "Режим множеÑ?Ñ?венного копиÑ?ованиÑ?"
@@ -326,7 +316,7 @@ msgstr "Ð?еÑ?епÑ?ивÑ?зка акÑ?ивна"
msgid "Action"
msgstr "Ð?ейÑ?Ñ?вие"
-#: gschem/src/i_basic.c:260 gschem/src/x_dialog.c:2312
+#: gschem/src/i_basic.c:260 gschem/src/x_dialog.c:2316
#: gschem/src/x_window.c:491
msgid "Stroke"
msgstr "Ð?еÑ?Ñ?"
@@ -357,7 +347,7 @@ msgstr "СеÑ?ка (%s, %s)"
msgid "Documentation for [%s,%s,%s,%s]\n"
msgstr "Ð?окÑ?менÑ?аÑ?иÑ? длÑ? [%s, %s, %s, %s]\n"
-#: gschem/src/i_callbacks.c:123 gschem/src/i_callbacks.c:1699
+#: gschem/src/i_callbacks.c:123 gschem/src/i_callbacks.c:1706
#, c-format
msgid "New page created [%s]\n"
msgstr "Создана новаÑ? Ñ?Ñ?Ñ?аниÑ?а [%s]\n"
@@ -379,69 +369,69 @@ msgstr "Ð?Ñ?Ñ? Ñ?оÑ?Ñ?анено"
msgid "Closing Window\n"
msgstr "Ð?акÑ?Ñ?Ñ?ие окна\n"
-#: gschem/src/i_callbacks.c:549 gschem/src/i_callbacks.c:594
-#: gschem/src/i_callbacks.c:639
+#: gschem/src/i_callbacks.c:581 gschem/src/i_callbacks.c:626
+#: gschem/src/i_callbacks.c:671
msgid "Select objs first"
msgstr "СнаÑ?ала нÑ?жно вÑ?делиÑ?Ñ? Ñ?Ñ?о-либо"
-#: gschem/src/i_callbacks.c:678 gschem/src/x_multiattrib.c:1491
+#: gschem/src/i_callbacks.c:710 gschem/src/x_multiattrib.c:1503
msgid "Delete"
msgstr "УдалиÑ?Ñ?"
-#: gschem/src/i_callbacks.c:703
+#: gschem/src/i_callbacks.c:735
msgid "Edit"
msgstr "Ð?Ñ?авка"
-#: gschem/src/i_callbacks.c:718
+#: gschem/src/i_callbacks.c:750
msgid "Edit pin type"
msgstr "Ð?Ñ?авка Ñ?ипа вÑ?вода"
-#: gschem/src/i_callbacks.c:737
+#: gschem/src/i_callbacks.c:769
msgid "Edit Text"
msgstr "Ð?Ñ?авка Ñ?екÑ?Ñ?а"
-#: gschem/src/i_callbacks.c:760
+#: gschem/src/i_callbacks.c:792
msgid "Slot"
msgstr "СлоÑ?"
-#: gschem/src/i_callbacks.c:777
+#: gschem/src/i_callbacks.c:809
msgid "Color"
msgstr "ЦвеÑ?"
-#: gschem/src/i_callbacks.c:814 gschem/src/i_callbacks.c:859
+#: gschem/src/i_callbacks.c:846 gschem/src/i_callbacks.c:891
msgid "Rotate"
msgstr "Ð?Ñ?аÑ?аÑ?Ñ?"
-#: gschem/src/i_callbacks.c:882 gschem/src/i_callbacks.c:907
+#: gschem/src/i_callbacks.c:913 gschem/src/i_callbacks.c:938
msgid "Mirror"
msgstr "Ð?еÑ?калиÑ?оваÑ?Ñ?"
-#: gschem/src/i_callbacks.c:928 gschem/src/x_dialog.c:2315
-#: gschem/lib/system-gschemrc.scm:1422
+#: gschem/src/i_callbacks.c:959 gschem/src/x_dialog.c:2319
+#: gschem/lib/system-gschemrc.scm:1424
msgid "Lock"
msgstr "Ð?локиÑ?оваÑ?Ñ?"
-#: gschem/src/i_callbacks.c:946 gschem/lib/system-gschemrc.scm:1423
+#: gschem/src/i_callbacks.c:977 gschem/lib/system-gschemrc.scm:1425
msgid "Unlock"
msgstr "РазблокиÑ?оваÑ?Ñ?"
-#: gschem/src/i_callbacks.c:964 gschem/src/x_dialog.c:1734
+#: gschem/src/i_callbacks.c:995 gschem/src/x_dialog.c:1737
msgid "Translate"
msgstr "Ð?еÑ?емеÑ?ение"
-#: gschem/src/i_callbacks.c:967
+#: gschem/src/i_callbacks.c:998
msgid "WARNING: Do not translate with snap off!\n"
msgstr "Ð?Ð?Ð?Ð?Ð?Ð?Ð?Ð?! не пеÑ?емеÑ?айÑ?е Ñ? вÑ?клÑ?Ñ?енной пÑ?ивÑ?зкой!\n"
-#: gschem/src/i_callbacks.c:968
+#: gschem/src/i_callbacks.c:999
msgid "WARNING: Turning snap on and continuing with translate.\n"
msgstr "Ð?Ð?Ð?Ð?Ð?Ð?Ð?Ð?! Ð?клÑ?Ñ?иÑ?е пÑ?ивÑ?зкÑ? пÑ?одолжиÑ?е пеÑ?емеÑ?ение.\n"
-#: gschem/src/i_callbacks.c:975
+#: gschem/src/i_callbacks.c:1006
msgid "WARNING: Snap grid size is not equal to 100!\n"
msgstr "Ð?Ð?Ð?Ð?Ð?Ð?Ð?Ð?! Ñ?азмеÑ? Ñ?еÑ?ки пÑ?ивÑ?зки не Ñ?авен 100!\n"
-#: gschem/src/i_callbacks.c:977
+#: gschem/src/i_callbacks.c:1008
msgid ""
"WARNING: If you are translating a symbol to the origin, the snap grid size "
"should be set to 100\n"
@@ -449,176 +439,172 @@ msgstr ""
"Ð?Ð?Ð?Ð?Ð?Ð?Ð?Ð?! Ð?Ñ?ли пеÑ?емеÑ?аеÑ?Ñ?Ñ? Ñ?имвол к наÑ?алÑ? оÑ?Ñ?Ñ?Ñ?Ñ?а, Ñ?азмеÑ? Ñ?еÑ?ки пÑ?ивÑ?зки "
"должен бÑ?Ñ?Ñ? Ñ?Ñ?Ñ?ановлен в 100\n"
-#: gschem/src/i_callbacks.c:1008
+#: gschem/src/i_callbacks.c:1039
msgid "Embed"
msgstr "Ð?недÑ?иÑ?Ñ?"
-#: gschem/src/i_callbacks.c:1047
+#: gschem/src/i_callbacks.c:1078
msgid "Unembed"
msgstr "Ð?Ñ?клÑ?Ñ?иÑ?Ñ?"
-#: gschem/src/i_callbacks.c:1089
+#: gschem/src/i_callbacks.c:1120
msgid "Update"
msgstr "Ð?бновиÑ?Ñ?"
-#: gschem/src/i_callbacks.c:1136
+#: gschem/src/i_callbacks.c:1167
msgid "ShowHidden"
msgstr "Ð?оказаÑ?Ñ? Ñ?кÑ?Ñ?Ñ?Ñ?е"
-#: gschem/src/i_callbacks.c:1160
-msgid "MakeVisible"
-msgstr "СделаÑ?Ñ? видимÑ?м"
-
-#: gschem/src/i_callbacks.c:1466 gschem/src/i_callbacks.c:1538
+#: gschem/src/i_callbacks.c:1473 gschem/src/i_callbacks.c:1545
msgid "Pan"
msgstr "ЦенÑ?Ñ?иÑ?оваÑ?Ñ?"
-#: gschem/src/i_callbacks.c:1743
+#: gschem/src/i_callbacks.c:1750
msgid "Really revert page?"
msgstr "Ð?ейÑ?Ñ?виÑ?елÑ?но веÑ?нÑ?Ñ?Ñ? Ñ?оÑ?Ñ?анÑ?ннÑ?Ñ? Ñ?Ñ?Ñ?аниÑ?Ñ??"
-#: gschem/src/i_callbacks.c:1813
+#: gschem/src/i_callbacks.c:1820
msgid "Copy to clipboard"
msgstr "Ð?опиÑ?оваÑ?Ñ? в бÑ?Ñ?еÑ?"
-#: gschem/src/i_callbacks.c:1831
+#: gschem/src/i_callbacks.c:1838
msgid "Cut to clipboard"
msgstr "Ð?Ñ?Ñ?езаÑ?Ñ? в бÑ?Ñ?еÑ?"
-#: gschem/src/i_callbacks.c:1849
+#: gschem/src/i_callbacks.c:1856
msgid "Paste from clipboard"
msgstr "Ð?Ñ?Ñ?авиÑ?Ñ? из бÑ?Ñ?еÑ?а"
-#: gschem/src/i_callbacks.c:1861 gschem/src/i_callbacks.c:2100
-#: gschem/src/i_callbacks.c:2122 gschem/src/i_callbacks.c:2144
-#: gschem/src/i_callbacks.c:2166 gschem/src/i_callbacks.c:2188
+#: gschem/src/i_callbacks.c:1868 gschem/src/i_callbacks.c:2107
+#: gschem/src/i_callbacks.c:2129 gschem/src/i_callbacks.c:2151
+#: gschem/src/i_callbacks.c:2173 gschem/src/i_callbacks.c:2195
msgid "Empty buffer"
msgstr "Ð?Ñ?иÑ?Ñ?иÑ?Ñ? бÑ?Ñ?еÑ?"
-#: gschem/src/i_callbacks.c:1906
+#: gschem/src/i_callbacks.c:1913
msgid "Copy 1"
msgstr "Ð?опиÑ?оваÑ?Ñ? в 1"
-#: gschem/src/i_callbacks.c:1925
+#: gschem/src/i_callbacks.c:1932
msgid "Copy 2"
msgstr "Ð?опиÑ?оваÑ?Ñ? в 2"
-#: gschem/src/i_callbacks.c:1944
+#: gschem/src/i_callbacks.c:1951
msgid "Copy 3"
msgstr "Ð?опиÑ?оваÑ?Ñ? в 3"
-#: gschem/src/i_callbacks.c:1963
+#: gschem/src/i_callbacks.c:1970
msgid "Copy 4"
msgstr "Ð?опиÑ?оваÑ?Ñ? в 4"
-#: gschem/src/i_callbacks.c:1982
+#: gschem/src/i_callbacks.c:1989
msgid "Copy 5"
msgstr "Ð?опиÑ?оваÑ?Ñ? в 5"
-#: gschem/src/i_callbacks.c:2001
+#: gschem/src/i_callbacks.c:2008
msgid "Cut 1"
msgstr "Ð?Ñ?Ñ?езаÑ?Ñ? в 1"
-#: gschem/src/i_callbacks.c:2020
+#: gschem/src/i_callbacks.c:2027
msgid "Cut 2"
msgstr "Ð?Ñ?Ñ?езаÑ?Ñ? в 2"
-#: gschem/src/i_callbacks.c:2039
+#: gschem/src/i_callbacks.c:2046
msgid "Cut 3"
msgstr "Ð?Ñ?Ñ?езаÑ?Ñ? в 3"
-#: gschem/src/i_callbacks.c:2058
+#: gschem/src/i_callbacks.c:2065
msgid "Cut 4"
msgstr "Ð?Ñ?Ñ?езаÑ?Ñ? в 4"
-#: gschem/src/i_callbacks.c:2077
+#: gschem/src/i_callbacks.c:2084
msgid "Cut 5"
msgstr "Ð?Ñ?Ñ?езаÑ?Ñ? в 5"
-#: gschem/src/i_callbacks.c:2093
+#: gschem/src/i_callbacks.c:2100
msgid "Paste 1"
msgstr "Ð?Ñ?Ñ?авиÑ?Ñ? из 1"
-#: gschem/src/i_callbacks.c:2115
+#: gschem/src/i_callbacks.c:2122
msgid "Paste 2"
msgstr "Ð?Ñ?Ñ?авиÑ?Ñ? из 2"
-#: gschem/src/i_callbacks.c:2137
+#: gschem/src/i_callbacks.c:2144
msgid "Paste 3"
msgstr "Ð?Ñ?Ñ?авиÑ?Ñ? из 3"
-#: gschem/src/i_callbacks.c:2159
+#: gschem/src/i_callbacks.c:2166
msgid "Paste 4"
msgstr "Ð?Ñ?Ñ?авиÑ?Ñ? из 4"
-#: gschem/src/i_callbacks.c:2181
+#: gschem/src/i_callbacks.c:2188
msgid "Paste 5"
msgstr "Ð?Ñ?Ñ?авиÑ?Ñ? из 5"
-#: gschem/src/i_callbacks.c:2318 gschem/src/x_window.c:355
+#: gschem/src/i_callbacks.c:2325 gschem/src/x_window.c:355
msgid "Component"
msgstr "ÐлеменÑ?"
-#: gschem/src/i_callbacks.c:2354 gschem/src/i_callbacks.c:2373
-#: gschem/src/x_dialog.c:2285
+#: gschem/src/i_callbacks.c:2361 gschem/src/i_callbacks.c:2380
+#: gschem/src/x_dialog.c:2289
msgid "Attribute"
msgstr "Ð?Ñ?Ñ?ибÑ?Ñ?"
-#: gschem/src/i_callbacks.c:2395 gschem/src/i_callbacks.c:2422
-#: gschem/src/x_dialog.c:2282
+#: gschem/src/i_callbacks.c:2402 gschem/src/i_callbacks.c:2429
+#: gschem/src/x_dialog.c:2286
msgid "Net"
msgstr "Соединение"
-#: gschem/src/i_callbacks.c:2466 gschem/src/i_callbacks.c:2493
-#: gschem/src/x_dialog.c:2300 gschem/src/x_window.c:375
+#: gschem/src/i_callbacks.c:2473 gschem/src/i_callbacks.c:2500
+#: gschem/src/x_dialog.c:2304 gschem/src/x_window.c:375
msgid "Bus"
msgstr "ШинÑ?"
-#: gschem/src/i_callbacks.c:2574 gschem/src/i_callbacks.c:2597
+#: gschem/src/i_callbacks.c:2581 gschem/src/i_callbacks.c:2604
msgid "Line"
msgstr "Ð?Ñ?Ñ?езок"
-#: gschem/src/i_callbacks.c:2619 gschem/src/i_callbacks.c:2642
+#: gschem/src/i_callbacks.c:2626 gschem/src/i_callbacks.c:2649
msgid "Box"
msgstr "Ð?Ñ?Ñ?моÑ?голÑ?ник"
-#: gschem/src/i_callbacks.c:2698 gschem/src/i_callbacks.c:2722
+#: gschem/src/i_callbacks.c:2705 gschem/src/i_callbacks.c:2729
msgid "Circle"
msgstr "Ð?кÑ?Ñ?жноÑ?Ñ?Ñ?"
-#: gschem/src/i_callbacks.c:2744 gschem/src/i_callbacks.c:2767
+#: gschem/src/i_callbacks.c:2751 gschem/src/i_callbacks.c:2774
msgid "Arc"
msgstr "Ð?Ñ?гÑ?"
-#: gschem/src/i_callbacks.c:2789 gschem/src/i_callbacks.c:2812
-#: gschem/src/x_dialog.c:2273
+#: gschem/src/i_callbacks.c:2796 gschem/src/i_callbacks.c:2819
+#: gschem/src/x_dialog.c:2277
msgid "Pin"
msgstr "Ð?Ñ?вод"
-#: gschem/src/i_callbacks.c:2871
+#: gschem/src/i_callbacks.c:2878
#, c-format
msgid "Searching for source [%s]\n"
msgstr "Ð?оиÑ?к иÑ?Ñ?оÑ?ника [%s]\n"
-#: gschem/src/i_callbacks.c:2895
+#: gschem/src/i_callbacks.c:2902
#, c-format
msgid "Cannot find source [%s]\n"
msgstr "Ð?евозможно найÑ?и иÑ?Ñ?оÑ?ник [%s]\n"
-#: gschem/src/i_callbacks.c:2964
+#: gschem/src/i_callbacks.c:2965
#, c-format
msgid "Searching for symbol [%s]\n"
msgstr "Ð?оиÑ?к Ñ?имвола [%s]\n"
-#: gschem/src/i_callbacks.c:2970
+#: gschem/src/i_callbacks.c:2971
msgid "Symbol is not a real file. Symbol cannot be loaded.\n"
msgstr "Символ не Ñ?влÑ?еÑ?Ñ?Ñ? Ñ?айлом. Символ не можеÑ? бÑ?Ñ?Ñ? загÑ?Ñ?жен.\n"
-#: gschem/src/i_callbacks.c:3001
+#: gschem/src/i_callbacks.c:3002
msgid "Cannot find any schematics above the current one!\n"
msgstr "Ð?евозможно найÑ?и какÑ?Ñ?-либо Ñ?Ñ?емÑ? над Ñ?екÑ?Ñ?ей!\n"
-#: gschem/src/i_callbacks.c:3055
+#: gschem/src/i_callbacks.c:3056
msgid ""
"This command retrieves the component documentation from the web, but there "
"is no component selected"
@@ -626,84 +612,84 @@ msgstr ""
"ÐÑ?а команда иÑ?полÑ?зÑ?еÑ?Ñ?Ñ? длÑ? поиÑ?ка докÑ?менÑ?аÑ?ии по компоненÑ?Ñ? в Ð?нÑ?еÑ?неÑ?, "
"но ни один компоненÑ? не вÑ?бÑ?ан"
-#: gschem/src/i_callbacks.c:3083
+#: gschem/src/i_callbacks.c:3084
msgid "Attach"
msgstr "Ð?Ñ?иÑ?оединиÑ?Ñ?"
-#: gschem/src/i_callbacks.c:3130
+#: gschem/src/i_callbacks.c:3131
msgid "Detach"
msgstr "Ð?Ñ?Ñ?оединиÑ?Ñ?"
-#: gschem/src/i_callbacks.c:3165
+#: gschem/src/i_callbacks.c:3166
msgid "ShowN"
msgstr "Ð?оказаÑ?Ñ? Ð?"
-#: gschem/src/i_callbacks.c:3201
+#: gschem/src/i_callbacks.c:3202
msgid "ShowV"
msgstr "Ð?оказаÑ?Ñ? Ð?"
-#: gschem/src/i_callbacks.c:3237
+#: gschem/src/i_callbacks.c:3238
msgid "ShowB"
msgstr "Ð?оказаÑ?Ñ? Ð? Ð?"
-#: gschem/src/i_callbacks.c:3274
+#: gschem/src/i_callbacks.c:3275
msgid "VisToggle"
msgstr "Ð?еÑ?екл. видимоÑ?Ñ?и"
-#: gschem/src/i_callbacks.c:3304
+#: gschem/src/i_callbacks.c:3305
#, c-format
msgid "Sorry but this is a non-functioning menu option\n"
msgstr "Ð?звиниÑ?е, но Ñ?Ñ?о Ñ?Ñ?оÑ? пÑ?нкÑ? менÑ? не Ñ?абоÑ?аеÑ?\n"
-#: gschem/src/i_callbacks.c:3394
+#: gschem/src/i_callbacks.c:3395
msgid "Action feedback mode set to OUTLINE\n"
msgstr "Ð?бÑ?аÑ?наÑ? Ñ?вÑ?зÑ? Ñ?Ñ?Ñ?ановлена по Ð?Ð?Ð?ТУРУ\n"
-#: gschem/src/i_callbacks.c:3397
+#: gschem/src/i_callbacks.c:3398
msgid "Action feedback mode set to BOUNDINGBOX\n"
msgstr "Ð?бÑ?аÑ?наÑ? Ñ?вÑ?зÑ? Ñ?Ñ?Ñ?ановлена по Ð?Ð?Ð Ð?Ð?Ð?Ч. Ð?РЯÐ?Ð?УÐ?Ð?Ð?ЬÐ?Ð?Ð?У\n"
-#: gschem/src/i_callbacks.c:3422
+#: gschem/src/i_callbacks.c:3423
msgid "Grid OFF\n"
msgstr "СеÑ?ка Ð?ЫÐ?Ð?\n"
-#: gschem/src/i_callbacks.c:3423
+#: gschem/src/i_callbacks.c:3424
msgid "Dot grid selected\n"
msgstr "Ð?Ñ?бÑ?ана Ñ?еÑ?ка из Ñ?оÑ?ек\n"
-#: gschem/src/i_callbacks.c:3424
+#: gschem/src/i_callbacks.c:3425
msgid "Mesh grid selected\n"
msgstr "Ð?Ñ?бÑ?ана Ñ?еÑ?ка из линий\n"
-#: gschem/src/i_callbacks.c:3445
+#: gschem/src/i_callbacks.c:3446
msgid "Snap OFF (CAUTION!)\n"
msgstr "Ð?Ñ?ивÑ?зка Ð?ЫÐ?Ð? (Ð?СТÐ?Ð Ð?Ð?Ð?Ð?!)\n"
-#: gschem/src/i_callbacks.c:3448
+#: gschem/src/i_callbacks.c:3449
msgid "Snap ON\n"
msgstr "Ð?Ñ?ивÑ?зка Ð?Ð?Ð?\n"
-#: gschem/src/i_callbacks.c:3451
+#: gschem/src/i_callbacks.c:3452
msgid "Snap back to the grid (CAUTION!)\n"
msgstr "Ð?клÑ?Ñ?иÑ?е пÑ?ивÑ?зкÑ? к Ñ?еÑ?ке (Ð?Ð?Ð?Ð?Ð?Ð?Ð?Ð?!)\n"
-#: gschem/src/i_callbacks.c:3477
+#: gschem/src/i_callbacks.c:3478
msgid "Rubber band OFF \n"
msgstr "РезиноваÑ? ленÑ?а Ð?ЫÐ?Ð? \n"
-#: gschem/src/i_callbacks.c:3480
+#: gschem/src/i_callbacks.c:3481
msgid "Rubber band ON\n"
msgstr "РезиноваÑ? ленÑ?а Ð?Ð?Ð?\n"
-#: gschem/src/i_callbacks.c:3495
+#: gschem/src/i_callbacks.c:3496
msgid "magnetic net mode: ON\n"
msgstr "Ñ?ежим магниÑ?ного Ñ?оединениÑ?: Ð?Ð?Ð?\n"
-#: gschem/src/i_callbacks.c:3498
+#: gschem/src/i_callbacks.c:3499
msgid "magnetic net mode: OFF\n"
msgstr "Ñ?ежим магниÑ?ного Ñ?оединениÑ?: Ð?ЫÐ?Ð?\n"
-#: gschem/src/o_box.c:153
+#: gschem/src/o_box.c:149
#, c-format
msgid "Unknown type for box (fill)!\n"
msgstr "Ð?еизвеÑ?Ñ?нÑ?й Ñ?ип длÑ? пÑ?Ñ?моÑ?голÑ?ника (Ñ? заливкой)!\n"
@@ -723,17 +709,17 @@ msgstr "o_buffer_cut: невеÑ?нÑ?й бÑ?Ñ?еÑ? %i\n"
msgid "Got an invalid buffer_number [o_buffer_paste_start]\n"
msgstr "Ð?олÑ?Ñ?ен невеÑ?нÑ?й buffer_number [o_buffer_paste_start]\n"
-#: gschem/src/o_bus.c:118
+#: gschem/src/o_bus.c:117
#, c-format
msgid "Got an invalid which one in o_bus_draw_stretch\n"
msgstr "Ð?олÑ?Ñ?ен невеÑ?нÑ?й паÑ?амеÑ?Ñ? в o_bus_draw_stretch\n"
-#: gschem/src/o_circle.c:134
+#: gschem/src/o_circle.c:130
#, c-format
msgid "Unknown type for circle (fill)!\n"
msgstr "Ð?еизвеÑ?Ñ?нÑ?й Ñ?ип длÑ? окÑ?Ñ?жноÑ?Ñ?и (заливки)!\n"
-#: gschem/src/o_complex.c:243 gschem/src/o_complex.c:247
+#: gschem/src/o_complex.c:237 gschem/src/o_complex.c:241
#, c-format
msgid "Translating schematic [%d %d]\n"
msgstr "Ð?еÑ?емеÑ?ение Ñ?Ñ?емÑ? [%d %d]\n"
@@ -751,37 +737,37 @@ msgstr "Ð?бÑ?екÑ? Ñ?же заблокиÑ?ован\n"
msgid "Object already unlocked\n"
msgstr "Ð?бÑ?екÑ? Ñ?же Ñ?азблокиÑ?ован\n"
-#: gschem/src/o_misc.c:413
+#: gschem/src/o_misc.c:409
msgid "Hidden text is now visible\n"
msgstr "СкÑ?Ñ?Ñ?Ñ?й Ñ?екÑ?Ñ? Ñ?Ñ?ал видим\n"
-#: gschem/src/o_misc.c:415
+#: gschem/src/o_misc.c:411
msgid "Hidden text is now invisible\n"
msgstr "СкÑ?Ñ?Ñ?Ñ?й Ñ?екÑ?Ñ? Ñ?Ñ?ал невидим\n"
-#: gschem/src/o_misc.c:668
+#: gschem/src/o_misc.c:636
#, c-format
msgid "Could not find symbol [%s] in library. Update failed.\n"
msgstr "Ð?е найден Ñ?имвол [%s] в библиоÑ?еке. Ð?бновление не вÑ?полнено.\n"
-#: gschem/src/o_misc.c:783
+#: gschem/src/o_misc.c:751
#, c-format
msgid "o_autosave_backups: Can't get the real filename of %s."
msgstr "o_autosave_backups: невозможно полÑ?Ñ?иÑ?Ñ? Ñ?еалÑ?но имÑ? Ñ?айла длÑ? %s."
-#: gschem/src/o_misc.c:827
+#: gschem/src/o_misc.c:795
#, c-format
msgid "Could NOT set previous backup file [%s] read-write\n"
msgstr ""
"Ð?евозможно Ñ?Ñ?Ñ?ановиÑ?Ñ? Ñ?ежим Ñ?Ñ?ениÑ?-запиÑ?и длÑ? пÑ?едÑ?дÑ?Ñ?ей Ñ?езеÑ?вной копии "
"Ñ?айла [%s]\n"
-#: gschem/src/o_misc.c:845
+#: gschem/src/o_misc.c:815
#, c-format
msgid "Could NOT set backup file [%s] readonly\n"
msgstr "Ð?евозможно Ñ?Ñ?Ñ?ановиÑ?Ñ? Ñ?ежим Ñ?олÑ?ко длÑ? Ñ?Ñ?ениÑ? Ñ?езеÑ?вного Ñ?айла [%s]\n"
-#: gschem/src/o_misc.c:850
+#: gschem/src/o_misc.c:820
#, c-format
msgid "Could NOT save backup file [%s]\n"
msgstr "Ð?евозможно Ñ?оÑ?Ñ?аниÑ?Ñ? Ñ?езеÑ?внÑ?й Ñ?айл [%s]\n"
@@ -801,38 +787,38 @@ msgstr "Ð?Ñ?! Ð?опÑ?Ñ?ка найÑ?и Ñ?Ñ?о-либо, но ниÑ?его не
msgid "Got a non line object in o_move_check_endpoint\n"
msgstr "Ð?олÑ?Ñ?ен обÑ?екÑ? не линиÑ? в o_move_check_endpoint\n"
-#: gschem/src/o_net.c:159
+#: gschem/src/o_net.c:158
#, c-format
msgid "Got an invalid which one in o_net_draw_stretch\n"
msgstr "Ð?олÑ?Ñ?ен невеÑ?нÑ?й паÑ?амеÑ?Ñ? в o_net_draw_stretche\n"
-#: gschem/src/o_net.c:538
+#: gschem/src/o_net.c:537
msgid "Warning: Starting net at off grid coordinate\n"
msgstr "Ð?нимание: наÑ?алÑ?наÑ? кооÑ?динаÑ?а Ñ?оединениÑ? не Ñ?аÑ?положена по Ñ?еÑ?ке\n"
-#: gschem/src/o_net.c:600
+#: gschem/src/o_net.c:599
msgid "Warning: Ending net at off grid coordinate\n"
msgstr "Ð?нимание: конеÑ?наÑ? кооÑ?динаÑ?а Ñ?оединениÑ? не Ñ?аÑ?положена по Ñ?еÑ?ке\n"
-#: gschem/src/o_net.c:932 gschem/src/o_net.c:969 gschem/src/o_net.c:1040
-#: gschem/src/o_net.c:1076
+#: gschem/src/o_net.c:931 gschem/src/o_net.c:968 gschem/src/o_net.c:1039
+#: gschem/src/o_net.c:1075
#, c-format
msgid "Tried to add more than two bus rippers. Internal gschem error.\n"
msgstr "Ð?опÑ?Ñ?ка добавиÑ?Ñ? более двÑ?Ñ? Ñ?азÑ?Ñ?вов Ñ?инÑ?. Ð?нÑ?Ñ?Ñ?еннÑ?Ñ? оÑ?ибка gschem.\n"
-#: gschem/src/o_net.c:1144
+#: gschem/src/o_net.c:1143
#, c-format
msgid "Bus ripper symbol [%s] was not found in any component library\n"
msgstr ""
"Ð?евозможно найÑ?и Ñ?имвол Ñ?азÑ?Ñ?ва Ñ?инÑ? [%s] ни в одной из библиоÑ?ек "
"компоненÑ?ов\n"
-#: gschem/src/o_path.c:352
+#: gschem/src/o_path.c:348
#, c-format
msgid "Unknown type for path (fill)!\n"
msgstr "Ð?еизвеÑ?Ñ?нÑ?й Ñ?ип длÑ? конÑ?Ñ?Ñ?а (Ñ? заливкой)!\n"
-#: gschem/src/o_picture.c:163 gschem/src/o_picture.c:539
+#: gschem/src/o_picture.c:163 gschem/src/o_picture.c:537
#, c-format
msgid "Failed to load picture: %s"
msgstr "Ð?евозможно загÑ?Ñ?зиÑ?Ñ? изобÑ?ажение: [%s]"
@@ -841,7 +827,7 @@ msgstr "Ð?евозможно загÑ?Ñ?зиÑ?Ñ? изобÑ?ажение: [%s]"
msgid "Picture"
msgstr "Ð?зобÑ?ажение"
-#: gschem/src/o_picture.c:447 gschem/src/x_attribedit.c:141
+#: gschem/src/o_picture.c:445 gschem/src/x_attribedit.c:141
#, c-format
msgid "ERROR: NULL object!\n"
msgstr "Ð?ШÐ?Ð?Ð?Ð?: обÑ?екÑ? NULL!\n"
@@ -862,34 +848,46 @@ msgstr "СлоÑ?иÑ?ование не допÑ?Ñ?Ñ?имо длÑ? Ñ?Ñ?ого ко
msgid "New slot number out of range\n"
msgstr "Ð?омеÑ? нового Ñ?лоÑ?а вÑ?Ñ?одиÑ? за пÑ?еделÑ?\n"
-#: gschem/src/o_undo.c:304
+#: gschem/src/o_undo.c:303
msgid "Undo/Redo disabled in rc file\n"
msgstr "Ð?Ñ?мена/повÑ?оÑ? вÑ?клÑ?Ñ?енÑ? в rc-Ñ?айле\n"
-#: gschem/src/parsecmd.c:47
+#: gschem/src/parsecmd.c:81
#, c-format
msgid ""
-"Usage: %s [OPTIONS] schematic_filename1 ... schematic_filenameN\n"
-" -q Quiet mode\n"
-" -v Verbose mode on\n"
-" -r filename Rc filename\n"
-" -s filename Script (guile) filename\n"
-" -o filename Output filename (for printing)\n"
-" -p Automatically place the window\n"
-" -t Print stroke information\n"
-" -h Help; this message\n"
+"Usage: %s [OPTION ...] [--] [FILE ...]\n"
"\n"
-msgstr ""
-"Ð?Ñ?полÑ?зование: %s [Ð?Ð?ЦÐ?Ð?] Ñ?айл_Ñ?Ñ?емÑ?1 ... Ñ?айл_Ñ?Ñ?емÑ?N\n"
-" -q Ð?иÑ?его не вÑ?водиÑ?Ñ?\n"
-" -v Режим оÑ?ладоÑ?нÑ?Ñ? Ñ?ообÑ?ений\n"
-" -r ФÐ?Ð?Ð? Ð?Ñ?полÑ?зоваÑ?Ñ? в каÑ?еÑ?Ñ?ве конÑ?игÑ?Ñ?аÑ?ионного Ñ?айл ФÐ?Ð?Ð?\n"
-" -s ФÐ?Ð?Ð? Ð?мÑ? ФÐ?Ð?Ð?а Ñ?кÑ?ипÑ?а (guile)\n"
-" -o ФÐ?Ð?Ð? Ð?мÑ? вÑ?Ñ?одного ФÐ?Ð?Ð?а (длÑ? пеÑ?аÑ?и)\n"
-" -p Ð?вÑ?омаÑ?иÑ?еÑ?ки Ñ?аÑ?положиÑ?Ñ? окно\n"
-" -t Ð?еÑ?аÑ?аÑ?Ñ? Ñ?Ñ?Ñ?иÑ?овÑ?Ñ? инÑ?оÑ?маÑ?иÑ?\n"
-" -h Ð?омоÑ?Ñ?; Ñ?Ñ?о Ñ?ообÑ?ение\n"
+"Interactively edit gEDA schematics or symbols. If one or more FILEs\n"
+"are specified, open them for editing; otherwise, create a new, empty\n"
+"schematic.\n"
"\n"
+"Options:\n"
+" -q, --quiet Quiet mode.\n"
+" -v, --verbose Verbose mode.\n"
+" -r, --config-file=FILE Additional configuration file to load.\n"
+" -L DIR Add DIR to Scheme search path.\n"
+" -c EXPR Scheme expression to run at startup.\n"
+" -s FILE Scheme script to run at startup.\n"
+" -o, --output=FILE Output filename (for printing).\n"
+" -p Automatically place the window.\n"
+" -V, --version Show version information.\n"
+" -h, --help Help; this message.\n"
+" -- Treat all remaining arguments as filenames.\n"
+"\n"
+"Report bugs to <geda-bug@xxxxxxxx>\n"
+"gEDA/gaf homepage: <http://gpleda.org>\n"
+msgstr ""
+
+#: gschem/src/parsecmd.c:115
+#, c-format
+msgid ""
+"gEDA %s (g%.7s)\n"
+"Copyright (C) 1998-2011 gEDA developers\n"
+"This is free software, and you are welcome to redistribute it under\n"
+"certain conditions. For details, see the file `COPYING', which is\n"
+"included in the gEDA distribution.\n"
+"There is NO WARRANTY, to the extent permitted by law.\n"
+msgstr ""
#: gschem/src/x_attribedit.c:127
#, c-format
@@ -900,56 +898,56 @@ msgstr "Ð?олÑ?Ñ?ена невеÑ?наÑ? опÑ?иÑ? пÑ?оÑ?моÑ?Ñ?а, Ñ?Ñ?Ñ?
msgid "Single Attribute Editor"
msgstr "РедакÑ?оÑ? аÑ?Ñ?ибÑ?Ñ?а"
-#: gschem/src/x_attribedit.c:358
+#: gschem/src/x_attribedit.c:359
msgid "<b>Edit Attribute</b>"
msgstr "<b>РедакÑ?иÑ?оваÑ?Ñ? аÑ?Ñ?ибÑ?Ñ?</b>"
-#: gschem/src/x_attribedit.c:360
+#: gschem/src/x_attribedit.c:361
msgid "<b>Add Attribute</b>"
msgstr "<b>Ð?обавиÑ?Ñ? аÑ?Ñ?ибÑ?Ñ?</b>"
-#: gschem/src/x_attribedit.c:376 gschem/src/x_multiattrib.c:1916
+#: gschem/src/x_attribedit.c:377 gschem/src/x_multiattrib.c:1927
msgid "Name:"
msgstr "Ð?мÑ?:"
-#: gschem/src/x_attribedit.c:393 gschem/src/x_multiattrib.c:1935
+#: gschem/src/x_attribedit.c:394 gschem/src/x_multiattrib.c:1946
msgid "Value:"
msgstr "Ð?наÑ?ение:"
-#: gschem/src/x_attribedit.c:409 gschem/src/x_multiattrib.c:1978
+#: gschem/src/x_attribedit.c:410 gschem/src/x_multiattrib.c:1989
msgid "Visible"
msgstr "Ð?идимÑ?й"
-#: gschem/src/x_attribedit.c:429
+#: gschem/src/x_attribedit.c:430
msgid "Show Value Only"
msgstr "Ð?оказаÑ?Ñ? знаÑ?ение"
-#: gschem/src/x_attribedit.c:431
+#: gschem/src/x_attribedit.c:432
msgid "Show Name Only"
msgstr "Ð?оказаÑ?Ñ? имÑ?"
-#: gschem/src/x_attribedit.c:433 gschem/src/x_multiattrib.c:1454
+#: gschem/src/x_attribedit.c:434 gschem/src/x_multiattrib.c:1466
msgid "Show Name & Value"
msgstr "Ð?оказаÑ?Ñ? имÑ? и знаÑ?ение"
-#: gschem/src/x_attribedit.c:440
+#: gschem/src/x_attribedit.c:441
msgid "<b>Attach Options</b>"
msgstr "<b>Ð?Ñ?иÑ?оединÑ?ннÑ?е паÑ?амеÑ?Ñ?Ñ?</b>"
-#: gschem/src/x_attribedit.c:455
+#: gschem/src/x_attribedit.c:456
msgid "All"
msgstr "Ð?Ñ?Ñ?"
-#: gschem/src/x_attribedit.c:463 gschem/src/x_compselect.c:896
-#: gschem/src/x_compselect.c:1010
+#: gschem/src/x_attribedit.c:464 gschem/src/x_compselect.c:904
+#: gschem/src/x_compselect.c:1018
msgid "Components"
msgstr "Ð?омпоненÑ?Ñ?"
-#: gschem/src/x_attribedit.c:471 gschem/src/x_window.c:365
+#: gschem/src/x_attribedit.c:472 gschem/src/x_window.c:365
msgid "Nets"
msgstr "СоединениÑ?"
-#: gschem/src/x_attribedit.c:479
+#: gschem/src/x_attribedit.c:480
msgid "Replace existing attributes"
msgstr "Ð?амеÑ?Ñ?иÑ?Ñ? Ñ?Ñ?Ñ?еÑ?Ñ?вÑ?Ñ?Ñ?ие аÑ?Ñ?ибÑ?Ñ?Ñ?"
@@ -969,91 +967,91 @@ msgstr ""
"повÑ?оÑ?Ñ?Ñ?Ñ?ийÑ?Ñ? Ñ?лоÑ? можеÑ? бÑ?Ñ?Ñ? пÑ?иÑ?иной пÑ?облемÑ?: [symbolname=%s, number=%d, "
"slot=%d]\n"
-#: gschem/src/x_autonumber.c:673
+#: gschem/src/x_autonumber.c:675
msgid "No searchstring given in autonumber text.\n"
msgstr "Ð?е задана Ñ?Ñ?Ñ?ока длÑ? поиÑ?ка в Ñ?екÑ?Ñ?е авÑ?онÑ?меÑ?аÑ?ии.\n"
-#: gschem/src/x_autonumber.c:725
+#: gschem/src/x_autonumber.c:727
msgid "No '*' or '?' given at the end of the autonumber text.\n"
msgstr "Ð?е задан Ñ?имвол '*' или '?' в конÑ?е Ñ?екÑ?Ñ?а авÑ?онÑ?меÑ?аÑ?ии.\n"
-#: gschem/src/x_autonumber.c:860
+#: gschem/src/x_autonumber.c:862
msgid "Diagonal"
msgstr "Ð?о диагонали"
-#: gschem/src/x_autonumber.c:861
+#: gschem/src/x_autonumber.c:863
msgid "Top to bottom"
msgstr "СвеÑ?Ñ?Ñ? вниз"
-#: gschem/src/x_autonumber.c:861
+#: gschem/src/x_autonumber.c:863
msgid "Bottom to top"
msgstr "СнизÑ? ввеÑ?Ñ?"
-#: gschem/src/x_autonumber.c:862
+#: gschem/src/x_autonumber.c:864
msgid "Left to right"
msgstr "Слева на пÑ?аво"
-#: gschem/src/x_autonumber.c:862
+#: gschem/src/x_autonumber.c:864
msgid "Right to left"
msgstr "СпÑ?ава налево"
-#: gschem/src/x_autonumber.c:863
+#: gschem/src/x_autonumber.c:865
msgid "File order"
msgstr "Ð?оÑ?Ñ?док Ñ?айлов"
-#: gschem/src/x_autonumber.c:1199
+#: gschem/src/x_autonumber.c:1201
msgid "Autonumber text"
msgstr "Ð?вÑ?онÑ?меÑ?оваÑ?Ñ? Ñ?екÑ?Ñ?"
-#: gschem/src/x_autonumber.c:1223
+#: gschem/src/x_autonumber.c:1225
msgid "<b>Scope</b>"
msgstr "<b>Ð?блаÑ?Ñ?Ñ?</b>"
-#: gschem/src/x_autonumber.c:1245
+#: gschem/src/x_autonumber.c:1247
msgid "Search for:"
msgstr "Ð?Ñ?каÑ?Ñ?:"
-#: gschem/src/x_autonumber.c:1259
+#: gschem/src/x_autonumber.c:1261
msgid "Autonumber text in:"
msgstr "Ð?вÑ?онÑ?меÑ?аÑ?иÑ? Ñ?екÑ?Ñ?а в:"
-#: gschem/src/x_autonumber.c:1266
+#: gschem/src/x_autonumber.c:1268
msgid "Skip numbers found in:"
msgstr "Ð?Ñ?опÑ?Ñ?Ñ?иÑ?Ñ? номеÑ?а найденнÑ?е в:"
-#: gschem/src/x_autonumber.c:1278 gschem/src/x_autonumber.c:1287
+#: gschem/src/x_autonumber.c:1280 gschem/src/x_autonumber.c:1289
msgid "Selected objects"
msgstr "Ð?Ñ?бÑ?аннÑ?е обÑ?екÑ?Ñ?"
-#: gschem/src/x_autonumber.c:1279 gschem/src/x_autonumber.c:1288
+#: gschem/src/x_autonumber.c:1281 gschem/src/x_autonumber.c:1290
msgid "Current page"
msgstr "ТекÑ?Ñ?аÑ? Ñ?Ñ?Ñ?аниÑ?а"
-#: gschem/src/x_autonumber.c:1280 gschem/src/x_autonumber.c:1289
+#: gschem/src/x_autonumber.c:1282 gschem/src/x_autonumber.c:1291
msgid "Whole hierarchy"
msgstr "Ð?Ñ?Ñ? иеÑ?аÑ?Ñ?иÑ?"
-#: gschem/src/x_autonumber.c:1291
+#: gschem/src/x_autonumber.c:1293
msgid "Overwrite existing numbers"
msgstr "Ð?амениÑ?Ñ? Ñ?Ñ?Ñ?еÑ?Ñ?вÑ?Ñ?Ñ?ие номеÑ?а"
-#: gschem/src/x_autonumber.c:1296
+#: gschem/src/x_autonumber.c:1298
msgid "<b>Options</b>"
msgstr "<b>Ð?аÑ?Ñ?Ñ?ойки</b>"
-#: gschem/src/x_autonumber.c:1318
+#: gschem/src/x_autonumber.c:1320
msgid "Starting number:"
msgstr "Ð?аÑ?алÑ?нÑ?й номеÑ?:"
-#: gschem/src/x_autonumber.c:1325
+#: gschem/src/x_autonumber.c:1327
msgid "Sort order:"
msgstr "Ð?оÑ?Ñ?док Ñ?оÑ?Ñ?иÑ?овки:"
-#: gschem/src/x_autonumber.c:1346
+#: gschem/src/x_autonumber.c:1348
msgid "Remove numbers"
msgstr "УдалиÑ?Ñ? номеÑ?а"
-#: gschem/src/x_autonumber.c:1350
+#: gschem/src/x_autonumber.c:1352
msgid "Automatic slotting"
msgstr "Ð?вÑ?омаÑ?иÑ?еÑ?кое Ñ?лоÑ?иÑ?ование"
@@ -1090,48 +1088,48 @@ msgstr "Ð?опÑ?Ñ?ка полÑ?Ñ?ениÑ? невеÑ?ного Ñ?веÑ?а: %d\n"
msgid "Tried to get an invalid outline color: %d\n"
msgstr "Ð?опÑ?Ñ?ка полÑ?Ñ?ениÑ? невеÑ?ного Ñ?веÑ?а конÑ?Ñ?Ñ?а: %d\n"
-#: gschem/src/x_compselect.c:1040
+#: gschem/src/x_compselect.c:1048
msgid "Filter:"
msgstr "ФилÑ?Ñ?Ñ?:"
-#: gschem/src/x_compselect.c:1143 gschem/src/x_dialog.c:3663
-#: gschem/src/x_multiattrib.c:1782
+#: gschem/src/x_compselect.c:1151 gschem/src/x_dialog.c:3667
+#: gschem/src/x_multiattrib.c:1793
msgid "Name"
msgstr "Ð?мÑ?"
-#: gschem/src/x_compselect.c:1152 gschem/src/x_multiattrib.c:1806
+#: gschem/src/x_compselect.c:1160 gschem/src/x_multiattrib.c:1817
msgid "Value"
msgstr "Ð?наÑ?ение"
-#: gschem/src/x_compselect.c:1191
+#: gschem/src/x_compselect.c:1199
msgid "Default behavior - reference component"
msgstr "Ð?оÑ?малÑ?ное поведение â?? Ñ?Ñ?Ñ?лка на компоненÑ?"
-#: gschem/src/x_compselect.c:1194
+#: gschem/src/x_compselect.c:1202
msgid "Embed component in schematic"
msgstr "Ð?недÑ?иÑ?Ñ? компоненÑ? в Ñ?Ñ?емÑ?"
-#: gschem/src/x_compselect.c:1197
+#: gschem/src/x_compselect.c:1205
msgid "Include component as individual objects"
msgstr "Ð?клÑ?Ñ?иÑ?Ñ? компоненÑ? как индивидÑ?алÑ?нÑ?й обÑ?екÑ?"
-#: gschem/src/x_compselect.c:1354
+#: gschem/src/x_compselect.c:1362
msgid "Select Component..."
msgstr "Ð?Ñ?боÑ? компоненÑ?а"
-#: gschem/src/x_compselect.c:1377
+#: gschem/src/x_compselect.c:1385
msgid "In Use"
msgstr "Ð?Ñ?полÑ?зÑ?емÑ?е"
-#: gschem/src/x_compselect.c:1381
+#: gschem/src/x_compselect.c:1389
msgid "Libraries"
msgstr "Ð?иблиоÑ?еки"
-#: gschem/src/x_compselect.c:1390 gschem/src/x_fileselect.c:122
+#: gschem/src/x_compselect.c:1398 gschem/src/x_fileselect.c:122
msgid "Preview"
msgstr "Ð?Ñ?едваÑ?иÑ?елÑ?нÑ?й пÑ?оÑ?моÑ?Ñ?"
-#: gschem/src/x_compselect.c:1418
+#: gschem/src/x_compselect.c:1426
msgid "Attributes"
msgstr "Ð?Ñ?Ñ?ибÑ?Ñ?Ñ?"
@@ -1189,139 +1187,139 @@ msgstr "Ñ?пÑ?ава внизÑ?"
msgid "Edit Text Properties"
msgstr "Ð?змениÑ?Ñ? Ñ?войÑ?Ñ?ва Ñ?екÑ?Ñ?а"
-#: gschem/src/x_dialog.c:471
+#: gschem/src/x_dialog.c:472
msgid "<b>Text Content</b>"
msgstr "<b>ТекÑ?Ñ?овое Ñ?одеÑ?жимое</b>"
-#: gschem/src/x_dialog.c:507
+#: gschem/src/x_dialog.c:508
msgid "<b>Text Properties</b>"
msgstr "<b>СвойÑ?Ñ?ва Ñ?екÑ?Ñ?а</b>"
-#: gschem/src/x_dialog.c:522
+#: gschem/src/x_dialog.c:523
msgid "Color:"
msgstr "ЦвеÑ?:"
-#: gschem/src/x_dialog.c:529
+#: gschem/src/x_dialog.c:530
msgid "Size:"
msgstr "РазмеÑ?:"
-#: gschem/src/x_dialog.c:538
+#: gschem/src/x_dialog.c:539
msgid "Alignment:"
msgstr "Ð?Ñ?Ñ?авнивание:"
-#: gschem/src/x_dialog.c:587
+#: gschem/src/x_dialog.c:588
msgid "Solid"
msgstr "Ñ?плоÑ?наÑ?"
-#: gschem/src/x_dialog.c:588
+#: gschem/src/x_dialog.c:589
msgid "Dotted"
msgstr "пÑ?нкÑ?иÑ?наÑ?"
-#: gschem/src/x_dialog.c:589
+#: gschem/src/x_dialog.c:590
msgid "Dashed"
msgstr "Ñ?Ñ?Ñ?иÑ?оваÑ?"
-#: gschem/src/x_dialog.c:590
+#: gschem/src/x_dialog.c:591
msgid "Center"
msgstr "Ñ?Ñ?Ñ?иÑ?пÑ?нкÑ?иÑ?наÑ?"
-#: gschem/src/x_dialog.c:591
+#: gschem/src/x_dialog.c:592
msgid "Phantom"
msgstr "Ñ?анÑ?омнаÑ?"
-#: gschem/src/x_dialog.c:592 gschem/src/x_dialog.c:689
-#: gschem/src/x_dialog.c:698 gschem/src/x_dialog.c:707
-#: gschem/src/x_dialog.c:808 gschem/src/x_dialog.c:810
-#: gschem/src/x_dialog.c:812 gschem/src/x_dialog.c:1038
-#: gschem/src/x_dialog.c:1141 gschem/src/x_dialog.c:1150
-#: gschem/src/x_dialog.c:1159 gschem/src/x_dialog.c:1168
-#: gschem/src/x_dialog.c:1177 gschem/src/x_dialog.c:1290
-#: gschem/src/x_dialog.c:1292 gschem/src/x_dialog.c:1294
-#: gschem/src/x_dialog.c:1296 gschem/src/x_dialog.c:1298
+#: gschem/src/x_dialog.c:593 gschem/src/x_dialog.c:690
+#: gschem/src/x_dialog.c:699 gschem/src/x_dialog.c:708
+#: gschem/src/x_dialog.c:809 gschem/src/x_dialog.c:811
+#: gschem/src/x_dialog.c:813 gschem/src/x_dialog.c:1039
+#: gschem/src/x_dialog.c:1142 gschem/src/x_dialog.c:1151
+#: gschem/src/x_dialog.c:1160 gschem/src/x_dialog.c:1169
+#: gschem/src/x_dialog.c:1178 gschem/src/x_dialog.c:1291
+#: gschem/src/x_dialog.c:1293 gschem/src/x_dialog.c:1295
+#: gschem/src/x_dialog.c:1297 gschem/src/x_dialog.c:1299
msgid "*unchanged*"
msgstr "*неизменно*"
-#: gschem/src/x_dialog.c:916
+#: gschem/src/x_dialog.c:917
msgid "Edit Line Width & Type"
msgstr "Ð?зменение Ñ?иÑ?инÑ? и Ñ?ипа линии"
-#: gschem/src/x_dialog.c:955 gschem/src/x_print.c:307
+#: gschem/src/x_dialog.c:956 gschem/src/x_print.c:307
msgid "Type:"
msgstr "Ð?ид:"
-#: gschem/src/x_dialog.c:959
+#: gschem/src/x_dialog.c:960
msgid "Width:"
msgstr "ТолÑ?ина:"
-#: gschem/src/x_dialog.c:963
+#: gschem/src/x_dialog.c:964
msgid "Dash Length:"
msgstr "Ð?лина Ñ?Ñ?Ñ?иÑ?а:"
-#: gschem/src/x_dialog.c:967
+#: gschem/src/x_dialog.c:968
msgid "Dash Space:"
msgstr "Ð?нÑ?еÑ?вал:"
-#: gschem/src/x_dialog.c:1034
+#: gschem/src/x_dialog.c:1035
msgid "Hollow"
msgstr "неÑ?"
-#: gschem/src/x_dialog.c:1035
+#: gschem/src/x_dialog.c:1036
msgid "Filled"
msgstr "Ñ?лоÑ?ное"
-#: gschem/src/x_dialog.c:1036
+#: gschem/src/x_dialog.c:1037
msgid "Mesh"
msgstr "в клеÑ?кÑ?"
-#: gschem/src/x_dialog.c:1037
+#: gschem/src/x_dialog.c:1038
msgid "Hatch"
msgstr "в линейкÑ?"
-#: gschem/src/x_dialog.c:1406
+#: gschem/src/x_dialog.c:1407
msgid "Edit Fill Type"
msgstr "Ð?зменение заполнениÑ?"
-#: gschem/src/x_dialog.c:1444
+#: gschem/src/x_dialog.c:1446
msgid "Fill Type:"
msgstr "Тип заполнениÑ?:"
-#: gschem/src/x_dialog.c:1448
+#: gschem/src/x_dialog.c:1450
msgid "Line Width:"
msgstr "ТолÑ?ина линии:"
-#: gschem/src/x_dialog.c:1452
+#: gschem/src/x_dialog.c:1454
msgid "Angle 1:"
msgstr "Угол 1:"
-#: gschem/src/x_dialog.c:1456
+#: gschem/src/x_dialog.c:1458
msgid "Pitch 1:"
msgstr "Шаг 1:"
-#: gschem/src/x_dialog.c:1460
+#: gschem/src/x_dialog.c:1462
msgid "Angle 2:"
msgstr "Угол 2:"
-#: gschem/src/x_dialog.c:1464
+#: gschem/src/x_dialog.c:1466
msgid "Pitch 2:"
msgstr "Шаг 2:"
-#: gschem/src/x_dialog.c:1591
+#: gschem/src/x_dialog.c:1593
msgid "Arc Params"
msgstr "Ð?аÑ?амеÑ?Ñ?Ñ? дÑ?ги"
-#: gschem/src/x_dialog.c:1631
+#: gschem/src/x_dialog.c:1634
msgid "Arc Radius:"
msgstr "РадиÑ?Ñ? дÑ?ги:"
-#: gschem/src/x_dialog.c:1639
+#: gschem/src/x_dialog.c:1642
msgid "Start Angle:"
msgstr "Ð?аÑ?алÑ?нÑ?й Ñ?гол:"
-#: gschem/src/x_dialog.c:1647
+#: gschem/src/x_dialog.c:1650
msgid "Degrees of Sweep:"
msgstr "Угол замеÑ?аниÑ?:"
-#: gschem/src/x_dialog.c:1764
+#: gschem/src/x_dialog.c:1768
msgid ""
"Offset to translate?\n"
"(0 for origin)"
@@ -1329,200 +1327,200 @@ msgstr ""
"СмеÑ?ение?\n"
"(0 длÑ? наÑ?ала оÑ?Ñ?Ñ?Ñ?Ñ?а)"
-#: gschem/src/x_dialog.c:1832
+#: gschem/src/x_dialog.c:1836
msgid "Text Size"
msgstr "РазмеÑ? Ñ?екÑ?Ñ?а"
-#: gschem/src/x_dialog.c:1862
+#: gschem/src/x_dialog.c:1866
msgid "Enter new text size:"
msgstr "Ð?ведиÑ?е новÑ?й Ñ?азмеÑ? Ñ?екÑ?Ñ?а:"
-#: gschem/src/x_dialog.c:1938
+#: gschem/src/x_dialog.c:1942
msgid "Snap Size"
msgstr "Шаг пÑ?ивÑ?зки"
-#: gschem/src/x_dialog.c:1968
+#: gschem/src/x_dialog.c:1972
msgid "Enter new snap grid spacing:"
msgstr "Ð?ведиÑ?е новÑ?й Ñ?аг пÑ?ивÑ?зки к Ñ?еÑ?ке:"
-#: gschem/src/x_dialog.c:2045
+#: gschem/src/x_dialog.c:2049
msgid "Edit slot number"
msgstr "Ð?Ñ?авка номеÑ?а Ñ?лоÑ?а"
-#: gschem/src/x_dialog.c:2076
+#: gschem/src/x_dialog.c:2080
msgid "Edit slot number:"
msgstr "Ð?Ñ?авка номеÑ?а Ñ?лоÑ?а:"
-#: gschem/src/x_dialog.c:2117
+#: gschem/src/x_dialog.c:2121
#, c-format
msgid "%s%s (%s)"
msgstr ""
-#: gschem/src/x_dialog.c:2140
+#: gschem/src/x_dialog.c:2144
msgid "About gschem"
msgstr "Ð? gschem"
-#: gschem/src/x_dialog.c:2141
+#: gschem/src/x_dialog.c:2145
msgid "gEDA: GPL Electronic Design Automation"
msgstr ""
"gEDA: СиÑ?Ñ?ема авÑ?омаÑ?изиÑ?ованного пÑ?оекÑ?иÑ?ованиÑ? Ñ?лекÑ?Ñ?оннÑ?Ñ? Ñ?Ñ?ем (GPL)"
-#: gschem/src/x_dialog.c:2142
+#: gschem/src/x_dialog.c:2146
msgid ""
"Copyright © 1998-2009 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
"Copyright © 1998-2009 gEDA Contributors (see ChangeLog for details)"
msgstr ""
-#: gschem/src/x_dialog.c:2201
+#: gschem/src/x_dialog.c:2205
msgid "Coords"
msgstr "Ð?ооÑ?динаÑ?Ñ?"
-#: gschem/src/x_dialog.c:2222
+#: gschem/src/x_dialog.c:2226
msgid "Screen"
msgstr "ÐкÑ?ан"
-#: gschem/src/x_dialog.c:2231
+#: gschem/src/x_dialog.c:2235
msgid "World"
msgstr "Ð?оле"
-#: gschem/src/x_dialog.c:2270
+#: gschem/src/x_dialog.c:2274
msgid "Background"
msgstr "Фон"
-#: gschem/src/x_dialog.c:2276
+#: gschem/src/x_dialog.c:2280
msgid "Net endpoint"
msgstr "Ð?конÑ?ание Ñ?оединениÑ?"
-#: gschem/src/x_dialog.c:2279
+#: gschem/src/x_dialog.c:2283
msgid "Graphic"
msgstr "Ð?зобÑ?ажение"
-#: gschem/src/x_dialog.c:2288
+#: gschem/src/x_dialog.c:2292
msgid "Logic bubble"
msgstr "Ð?огиÑ?еÑ?каÑ? инвеÑ?Ñ?иÑ?"
-#: gschem/src/x_dialog.c:2291
+#: gschem/src/x_dialog.c:2295
msgid "Grid point"
msgstr "ТоÑ?ка Ñ?еÑ?ки"
-#: gschem/src/x_dialog.c:2294
+#: gschem/src/x_dialog.c:2298
msgid "Detached attribute"
msgstr "Ð?Ñ?Ñ?оединÑ?ннÑ?й аÑ?Ñ?ибÑ?Ñ?"
-#: gschem/src/x_dialog.c:2297 gschem/src/x_window.c:383
+#: gschem/src/x_dialog.c:2301 gschem/src/x_window.c:383
msgid "Text"
msgstr "ТекÑ?Ñ?"
-#: gschem/src/x_dialog.c:2303
+#: gschem/src/x_dialog.c:2307
msgid "Selection"
msgstr "Ð?Ñ?боÑ?"
-#: gschem/src/x_dialog.c:2306
+#: gschem/src/x_dialog.c:2310
msgid "Bounding box"
msgstr "Ð?гÑ?аниÑ?иваÑ?Ñ?ий пÑ?Ñ?моÑ?голÑ?ник"
-#: gschem/src/x_dialog.c:2309
+#: gschem/src/x_dialog.c:2313
msgid "Zoom box"
msgstr "Ð?аÑ?Ñ?Ñ?аб облаÑ?Ñ?и"
-#: gschem/src/x_dialog.c:2318
+#: gschem/src/x_dialog.c:2322
msgid "Output background"
msgstr "Фон пÑ?и вÑ?воде"
-#: gschem/src/x_dialog.c:2321
+#: gschem/src/x_dialog.c:2325
msgid "Net junction"
msgstr "СоединиÑ?елÑ?нÑ?й Ñ?зел"
-#: gschem/src/x_dialog.c:2324
+#: gschem/src/x_dialog.c:2328
msgid "Mesh grid major"
msgstr "Ð?Ñ?новнаÑ? Ñ?еÑ?ка из линий"
-#: gschem/src/x_dialog.c:2327
+#: gschem/src/x_dialog.c:2331
msgid "Mesh grid minor"
msgstr "Ð?еÑ?алÑ?наÑ? Ñ?еÑ?ка из линий"
-#: gschem/src/x_dialog.c:2330
+#: gschem/src/x_dialog.c:2334
msgid "Unknown"
msgstr "Ð?еизвеÑ?Ñ?но"
-#: gschem/src/x_dialog.c:2481
+#: gschem/src/x_dialog.c:2485
#, c-format
msgid "ERROR: NULL object in color_edit_dialog_apply!\n"
msgstr "Ð?ШÐ?Ð?Ð?Ð?: обÑ?екÑ? NULL в color_edit_dialog_apply!\n"
-#: gschem/src/x_dialog.c:2525
+#: gschem/src/x_dialog.c:2529
msgid "Color Edit"
msgstr "Ð?Ñ?авка Ñ?веÑ?а"
-#: gschem/src/x_dialog.c:2556
+#: gschem/src/x_dialog.c:2560
msgid "Object color:"
msgstr "ЦвеÑ? обÑ?екÑ?а:"
-#: gschem/src/x_dialog.c:2614
+#: gschem/src/x_dialog.c:2618
msgid "Hotkeys"
msgstr "Ð?оÑ?Ñ?Ñ?ие клавиÑ?и"
-#: gschem/src/x_dialog.c:2678
+#: gschem/src/x_dialog.c:2682
msgid "Function"
msgstr "ФÑ?нкÑ?ии"
-#: gschem/src/x_dialog.c:2685
+#: gschem/src/x_dialog.c:2689
msgid "Keystroke(s)"
msgstr "Ð?омбинаÑ?ии клавиÑ?"
-#: gschem/src/x_dialog.c:2991
+#: gschem/src/x_dialog.c:2995
msgid "Find Text"
msgstr "Ð?айÑ?и Ñ?екÑ?Ñ?"
-#: gschem/src/x_dialog.c:3022
+#: gschem/src/x_dialog.c:3026
msgid "Text to find:"
msgstr "ТекÑ?Ñ? длÑ? поиÑ?ка:"
-#: gschem/src/x_dialog.c:3032
+#: gschem/src/x_dialog.c:3036
msgid "descend into hierarchy"
msgstr "Ð?низ по иеÑ?аÑ?Ñ?ии"
-#: gschem/src/x_dialog.c:3097
+#: gschem/src/x_dialog.c:3101
msgid "Hide Text"
msgstr "СкÑ?Ñ?Ñ?Ñ? Ñ?екÑ?Ñ?"
-#: gschem/src/x_dialog.c:3128
+#: gschem/src/x_dialog.c:3132
msgid "Hide text starting with:"
msgstr "СкÑ?Ñ?Ñ?Ñ? Ñ?екÑ?Ñ?, наÑ?инаÑ?Ñ?ийÑ?Ñ? Ñ?:"
-#: gschem/src/x_dialog.c:3197
+#: gschem/src/x_dialog.c:3201
msgid "Show Text"
msgstr "Ð?оказаÑ?Ñ? Ñ?екÑ?Ñ?"
-#: gschem/src/x_dialog.c:3228
+#: gschem/src/x_dialog.c:3232
msgid "Show text starting with:"
msgstr "Ð?оказаÑ?Ñ? Ñ?екÑ?Ñ?, наÑ?инаÑ?Ñ?ийÑ?Ñ? Ñ?:"
-#: gschem/src/x_dialog.c:3685
+#: gschem/src/x_dialog.c:3689
msgid "S_elect the schematics you want to save:"
msgstr "_Ð?Ñ?беÑ?иÑ?е Ñ?Ñ?емÑ? длÑ? Ñ?оÑ?Ñ?анениÑ?:"
-#: gschem/src/x_dialog.c:3779
+#: gschem/src/x_dialog.c:3784
#, c-format
msgid "Save the changes to schematic \"%s\" before closing?"
msgstr "СоÑ?Ñ?аниÑ?Ñ? изменениÑ? в Ñ?Ñ?еме \"%s\" пеÑ?ед закÑ?Ñ?Ñ?ием?"
-#: gschem/src/x_dialog.c:3785
+#: gschem/src/x_dialog.c:3790
#, c-format
msgid ""
"There are %d schematics with unsaved changes. Save changes before closing?"
msgstr ""
"Ð? Ñ?Ñ?емаÑ? еÑ?Ñ?Ñ? неÑ?оÑ?Ñ?анÑ?ннÑ?е изменениÑ? (%d). СоÑ?Ñ?аниÑ?Ñ? иÑ? пеÑ?ед закÑ?Ñ?Ñ?ием?"
-#: gschem/src/x_dialog.c:3814
+#: gschem/src/x_dialog.c:3819
msgid "If you don't save, all your changes will be permanently lost."
msgstr "Ð?Ñ?ли вÑ? не Ñ?оÑ?Ñ?аниÑ?е, вÑ?е изменениÑ? бÑ?дÑ?Ñ? безвозвÑ?аÑ?но Ñ?Ñ?еÑ?Ñ?нÑ?."
-#: gschem/src/x_dialog.c:3834
+#: gschem/src/x_dialog.c:3839
msgid "_Close without saving"
msgstr "_Ð?акÑ?Ñ?Ñ?Ñ? без Ñ?оÑ?Ñ?анениÑ?"
-#: gschem/src/x_dialog.c:4170
+#: gschem/src/x_dialog.c:4175
#, c-format
msgid ""
"<span weight=\"bold\" size=\"larger\">The input attribute \"%s\" is invalid\n"
@@ -1539,19 +1537,19 @@ msgstr ""
"Ð?мÑ? не можеÑ? заканÑ?иваÑ?Ñ?Ñ?Ñ? пÑ?обелом.\n"
"Ð?наÑ?ение не можеÑ? наÑ?инаÑ?Ñ?Ñ?Ñ? Ñ? пÑ?обела."
-#: gschem/src/x_dialog.c:4172
+#: gschem/src/x_dialog.c:4177
msgid "Invalid Attribute"
msgstr "Ð?евеÑ?нÑ?й аÑ?Ñ?ибÑ?Ñ?"
-#: gschem/src/x_dialog.c:4208
+#: gschem/src/x_dialog.c:4213
msgid "Pin type"
msgstr "Тип вÑ?вода"
-#: gschem/src/x_dialog.c:4232
+#: gschem/src/x_dialog.c:4237
msgid "Net pin"
msgstr "Ð?Ñ?вод Ñ?оединениÑ?"
-#: gschem/src/x_dialog.c:4234
+#: gschem/src/x_dialog.c:4239
msgid "Bus pin (graphical)"
msgstr "Ð?Ñ?вод Ñ?инÑ? (гÑ?аÑ?иÑ?еÑ?кий)"
@@ -1651,11 +1649,11 @@ msgstr "Тип изобÑ?ажениÑ?"
msgid "Write image..."
msgstr "СоÑ?Ñ?аниÑ?Ñ? изобÑ?ажение..."
-#: gschem/src/x_log.c:188
+#: gschem/src/x_log.c:209
msgid "** Invalid UTF-8 in log message. See stderr or gschem.log.\n"
msgstr "** Ð?евеÑ?нÑ?й Ñ?имвол UTF-8 в окне Ñ?Ñ?аÑ?Ñ?Ñ?а. См. stderr или gschem.log.\n"
-#: gschem/src/x_log.c:256
+#: gschem/src/x_log.c:288
msgid "Status"
msgstr "СÑ?аÑ?Ñ?Ñ?"
@@ -1731,72 +1729,63 @@ msgstr "/Ð?глÑ?бÑ? Ñ?имвола"
msgid "/Up"
msgstr "/Ð?авеÑ?Ñ?"
-#: gschem/src/x_menus.c:321
+#: gschem/src/x_menus.c:323
#, c-format
msgid "Tried to set the sensitivity on non-existent menu item '%s'\n"
msgstr ""
"Ð?опÑ?Ñ?ка Ñ?Ñ?Ñ?ановиÑ?Ñ? Ñ?Ñ?вÑ?Ñ?виÑ?елÑ?ноÑ?Ñ?Ñ? длÑ? неÑ?Ñ?Ñ?еÑ?Ñ?вÑ?Ñ?Ñ?его Ñ?леменÑ?а менÑ? '%s'\n"
-#: gschem/src/x_menus.c:345
+#: gschem/src/x_menus.c:347
msgid "Popup_menu_item_factory doesn't exist!\n"
msgstr "Popup_menu_item_factory не Ñ?Ñ?Ñ?еÑ?Ñ?вÑ?еÑ?!\n"
-#: gschem/src/x_menus.c:358
+#: gschem/src/x_menus.c:360
msgid "Tried to set the sensitivity on a non-existent popup menu_item\n"
msgstr ""
"Ð?опÑ?Ñ?ка Ñ?Ñ?Ñ?ановки Ñ?Ñ?вÑ?Ñ?виÑ?елÑ?ноÑ?Ñ?и длÑ? неÑ?Ñ?Ñ?еÑ?Ñ?вÑ?Ñ?Ñ?его вÑ?Ñ?какиваÑ?Ñ?его "
"menu_item\n"
-#: gschem/src/x_menus.c:438
-#, c-format
-msgid "Couldn't open file %s\n"
-msgstr "Ð?е Ñ?далоÑ?Ñ? оÑ?кÑ?Ñ?Ñ?Ñ? Ñ?айл %s\n"
-
-#: gschem/src/x_menus.c:495
-msgid "Clear"
-msgstr "Ð?Ñ?иÑ?Ñ?иÑ?Ñ?"
-
-#: gschem/src/x_multiattrib.c:911
+#: gschem/src/x_multiattrib.c:915
msgid "Attributes with empty name are not allowed. Please set a name."
msgstr "Ð?Ñ?Ñ?ибÑ?Ñ?Ñ? Ñ? пÑ?Ñ?Ñ?Ñ?м именем недопÑ?Ñ?Ñ?имÑ?. Ð?ожалÑ?йÑ?Ñ?а, введиÑ?е имÑ?."
-#: gschem/src/x_multiattrib.c:1456
+#: gschem/src/x_multiattrib.c:1468
msgid "Show Value only"
msgstr "Ð?оказаÑ?Ñ? знаÑ?ение"
-#: gschem/src/x_multiattrib.c:1458
+#: gschem/src/x_multiattrib.c:1470
msgid "Show Name only"
msgstr "Ð?оказаÑ?Ñ? имÑ?"
-#: gschem/src/x_multiattrib.c:1486
+#: gschem/src/x_multiattrib.c:1498
msgid "Promote"
msgstr "Ð?овÑ?Ñ?иÑ?Ñ?"
-#: gschem/src/x_multiattrib.c:1490
+#: gschem/src/x_multiattrib.c:1502
msgid "Duplicate"
msgstr "Ð?Ñ?блиÑ?оваÑ?Ñ?"
-#: gschem/src/x_multiattrib.c:1708
+#: gschem/src/x_multiattrib.c:1719
msgid "Edit Attributes"
msgstr "РедакÑ?иÑ?оваÑ?Ñ? аÑ?Ñ?ибÑ?Ñ?Ñ?"
-#: gschem/src/x_multiattrib.c:1826
+#: gschem/src/x_multiattrib.c:1837
msgid "Vis?"
msgstr "Ð?идимÑ?й"
-#: gschem/src/x_multiattrib.c:1844
+#: gschem/src/x_multiattrib.c:1855
msgid "N"
msgstr "Ð?"
-#: gschem/src/x_multiattrib.c:1862
+#: gschem/src/x_multiattrib.c:1873
msgid "V"
msgstr "Ð?"
-#: gschem/src/x_multiattrib.c:1884
+#: gschem/src/x_multiattrib.c:1895
msgid "Show inherited attributes"
msgstr "Ð?оказаÑ?Ñ? Ñ?наÑ?ледованнÑ?е аÑ?Ñ?ибÑ?Ñ?Ñ?"
-#: gschem/src/x_multiattrib.c:1900
+#: gschem/src/x_multiattrib.c:1911
msgid "Add Attribute"
msgstr "Ð?обавиÑ?Ñ? аÑ?Ñ?ибÑ?Ñ?"
@@ -1820,24 +1809,24 @@ msgstr "Ð?акÑ?Ñ?Ñ?Ñ? Ñ?Ñ?Ñ?аниÑ?Ñ?"
msgid "Discard Page"
msgstr "Ð?Ñ?веÑ?гнÑ?Ñ?Ñ? Ñ?Ñ?Ñ?аниÑ?Ñ?"
-#: gschem/src/x_pagesel.c:376
+#: gschem/src/x_pagesel.c:375
msgid "Page Manager"
msgstr "УпÑ?авление Ñ?Ñ?Ñ?аниÑ?ами"
-#: gschem/src/x_pagesel.c:432
+#: gschem/src/x_pagesel.c:431
msgid "Filename"
msgstr "Ð?мÑ? Ñ?айла"
-#: gschem/src/x_pagesel.c:448
+#: gschem/src/x_pagesel.c:447
msgid "Changed"
msgstr "Ð?зменено"
-#: gschem/src/x_pagesel.c:468
+#: gschem/src/x_pagesel.c:467
msgid "Right click on the filename for more options..."
msgstr ""
"ЩÑ?лÑ?ок пÑ?авой кнопкой на имени Ñ?айла даÑ?Ñ? дополниÑ?елÑ?нÑ?Ñ? возможноÑ?Ñ?и..."
-#: gschem/src/x_preview.c:234
+#: gschem/src/x_preview.c:233
msgid "Preview Buffer"
msgstr "Ð?Ñ?Ñ?еÑ? пÑ?едпÑ?оÑ?моÑ?Ñ?а"
@@ -1893,16 +1882,16 @@ msgstr "Файл:"
msgid "Command:"
msgstr "Ð?оманда:"
-#: gschem/src/x_print.c:741
+#: gschem/src/x_print.c:745
msgid "No print destination specified\n"
msgstr "Ð?е Ñ?казано назнаÑ?ение длÑ? пеÑ?аÑ?и\n"
-#: gschem/src/x_print.c:748
+#: gschem/src/x_print.c:752
#, c-format
msgid "Cannot print current schematic to [%s]\n"
msgstr "Ð?евозможно Ñ?аÑ?пеÑ?аÑ?аÑ?Ñ? Ñ?екÑ?Ñ?Ñ?Ñ? Ñ?Ñ?емÑ? на [%s]\n"
-#: gschem/src/x_print.c:757
+#: gschem/src/x_print.c:761
#, c-format
msgid ""
"Error printing to file '%s'\n"
@@ -1911,7 +1900,7 @@ msgstr ""
"Ð?Ñ?ибка пÑ?и пеÑ?аÑ?и в Ñ?айл '%s'\n"
"Ð?лÑ? далÑ?нейÑ?ей инÑ?оÑ?маÑ?ии Ñ?м. окно Ñ?Ñ?аÑ?Ñ?Ñ?а"
-#: gschem/src/x_print.c:764
+#: gschem/src/x_print.c:768
#, c-format
msgid "Printed current schematic to [%s]\n"
msgstr "ТекÑ?Ñ?аÑ? Ñ?Ñ?ема Ñ?аÑ?пеÑ?аÑ?ана на [%s]\n"
@@ -1920,6 +1909,11 @@ msgstr "ТекÑ?Ñ?аÑ? Ñ?Ñ?ема Ñ?аÑ?пеÑ?аÑ?ана на [%s]\n"
msgid "Execute Script..."
msgstr "Ð?Ñ?полниÑ?Ñ? Ñ?кÑ?ипÑ?..."
+#: gschem/src/x_script.c:66
+#, c-format
+msgid "Executing guile script [%s]\n"
+msgstr "Ð?апÑ?Ñ?каеÑ?Ñ?Ñ? guile-Ñ?кÑ?ипÑ? [%s]\n"
+
#: gschem/src/x_window.c:81
#, c-format
msgid "Couldn't allocate gc\n"
@@ -2035,35 +2029,35 @@ msgstr "Ð?Ñ?ибка пÑ?и загÑ?Ñ?зке Ñ?айла"
msgid "New file [%s]\n"
msgstr "Ð?овÑ?й Ñ?айл [%s]\n"
-#: gschem/src/x_window.c:857
+#: gschem/src/x_window.c:855
#, c-format
msgid "Could NOT save page [%s]\n"
msgstr "Ð?е Ñ?далоÑ?Ñ? Ñ?оÑ?Ñ?аниÑ?Ñ? Ñ?Ñ?Ñ?аниÑ?Ñ? [%s]\n"
-#: gschem/src/x_window.c:858
+#: gschem/src/x_window.c:856
msgid "Error while trying to save"
msgstr "Ð?Ñ?ибка пÑ?и попÑ?Ñ?ке Ñ?оÑ?Ñ?анениÑ?"
-#: gschem/src/x_window.c:867
+#: gschem/src/x_window.c:865
#, c-format
msgid "Saved as [%s]\n"
msgstr "СоÑ?Ñ?анено как [%s]\n"
-#: gschem/src/x_window.c:869
+#: gschem/src/x_window.c:867
#, c-format
msgid "Saved [%s]\n"
msgstr "СоÑ?Ñ?анено [%s]\n"
-#: gschem/src/x_window.c:871
+#: gschem/src/x_window.c:869
msgid "Saved"
msgstr "СоÑ?Ñ?анено"
-#: gschem/src/x_window.c:945
+#: gschem/src/x_window.c:943
#, c-format
msgid "Discarding page [%s]\n"
msgstr "Ð?Ñ?веÑ?жение Ñ?Ñ?Ñ?аниÑ?Ñ? [%s]\n"
-#: gschem/src/x_window.c:945
+#: gschem/src/x_window.c:943
#, c-format
msgid "Closing [%s]\n"
msgstr "Ð?акÑ?Ñ?Ñ?ие [%s]\n"
@@ -2104,7 +2098,7 @@ msgstr "СоÑ?Ñ?аниÑ?Ñ? _как..."
msgid "Save All"
msgstr "СоÑ?Ñ?аниÑ?Ñ? вÑ?е"
-#: gschem/lib/system-gschemrc.scm:1386 gschem/lib/system-gschemrc.scm:1477
+#: gschem/lib/system-gschemrc.scm:1386 gschem/lib/system-gschemrc.scm:1478
msgid "_Revert"
msgstr "_Ð?озвÑ?аÑ?иÑ?Ñ?"
@@ -2116,7 +2110,7 @@ msgstr "_Ð?еÑ?аÑ?Ñ?..."
msgid "Write _image..."
msgstr "СоÑ?Ñ?аниÑ?Ñ? _изобÑ?ажение..."
-#: gschem/lib/system-gschemrc.scm:1393 gschem/lib/system-gschemrc.scm:1478
+#: gschem/lib/system-gschemrc.scm:1393 gschem/lib/system-gschemrc.scm:1479
msgid "_Close"
msgstr "_Ð?акÑ?Ñ?Ñ?Ñ?"
@@ -2148,391 +2142,435 @@ msgstr "Ð?_Ñ?Ñ?авиÑ?Ñ?"
msgid "_Delete"
msgstr "_УдалиÑ?Ñ?"
-#: gschem/lib/system-gschemrc.scm:1412
+#: gschem/lib/system-gschemrc.scm:1409
+#, fuzzy
+msgid "Select All"
+msgstr "Ð?Ñ?бÑ?аÑ?Ñ?"
+
+#: gschem/lib/system-gschemrc.scm:1410
+#, fuzzy
+msgid "Deselect"
+msgstr "Ð?Ñ?бÑ?аÑ?Ñ?"
+
+#: gschem/lib/system-gschemrc.scm:1414
msgid "Rotate 90 Mode"
msgstr "Режим вÑ?аÑ?ениÑ? на 90°"
-#: gschem/lib/system-gschemrc.scm:1415
+#: gschem/lib/system-gschemrc.scm:1417
msgid "Edit..."
msgstr "Ð?Ñ?авка..."
-#: gschem/lib/system-gschemrc.scm:1416
+#: gschem/lib/system-gschemrc.scm:1418
msgid "Edit Text..."
msgstr "Ð?Ñ?авка Ñ?екÑ?Ñ?а..."
-#: gschem/lib/system-gschemrc.scm:1417
+#: gschem/lib/system-gschemrc.scm:1419
msgid "Slot..."
msgstr "СлоÑ?..."
-#: gschem/lib/system-gschemrc.scm:1418
+#: gschem/lib/system-gschemrc.scm:1420
msgid "Color..."
msgstr "ЦвеÑ?..."
-#: gschem/lib/system-gschemrc.scm:1419
+#: gschem/lib/system-gschemrc.scm:1421
msgid "Line Width & Type..."
msgstr "Тип и Ñ?иÑ?ина линии..."
-#: gschem/lib/system-gschemrc.scm:1420
+#: gschem/lib/system-gschemrc.scm:1422
msgid "Fill Type..."
msgstr "Тип заливки..."
-#: gschem/lib/system-gschemrc.scm:1421
+#: gschem/lib/system-gschemrc.scm:1423
msgid "Symbol Translate..."
msgstr "Ð?еÑ?еноÑ? кооÑ?динаÑ? Ñ?имвола..."
-#: gschem/lib/system-gschemrc.scm:1425
+#: gschem/lib/system-gschemrc.scm:1427
msgid "Invoke Macro"
msgstr "Ð?Ñ?полниÑ?Ñ? макÑ?оÑ?"
-#: gschem/lib/system-gschemrc.scm:1426
+#: gschem/lib/system-gschemrc.scm:1428
msgid "Embed Component/Picture"
msgstr "Ð?недÑ?иÑ?Ñ? компоненÑ? / изобÑ?ажение"
-#: gschem/lib/system-gschemrc.scm:1427
+#: gschem/lib/system-gschemrc.scm:1429
msgid "Unembed Component/Picture"
msgstr "Ð?Ñ?клÑ?Ñ?иÑ?Ñ? компоненÑ? / изобÑ?ажение"
-#: gschem/lib/system-gschemrc.scm:1428
+#: gschem/lib/system-gschemrc.scm:1430
msgid "Update Component"
msgstr "Ð?бновиÑ?Ñ? компоненÑ?"
-#: gschem/lib/system-gschemrc.scm:1429
+#: gschem/lib/system-gschemrc.scm:1431
msgid "Show/Hide Inv Text"
msgstr "Ð?оказаÑ?Ñ? / cкÑ?Ñ?Ñ?Ñ? невидимÑ?й Ñ?екÑ?Ñ?"
-#: gschem/lib/system-gschemrc.scm:1430
-msgid "Make Inv Text Vis"
-msgstr "СделаÑ?Ñ? невидимÑ?й Ñ?екÑ?Ñ? видимÑ?м"
-
-#: gschem/lib/system-gschemrc.scm:1436
+#: gschem/lib/system-gschemrc.scm:1437
msgid "Copy into 1"
msgstr "Ð?опиÑ?оваÑ?Ñ? в 1"
-#: gschem/lib/system-gschemrc.scm:1437
+#: gschem/lib/system-gschemrc.scm:1438
msgid "Copy into 2"
msgstr "Ð?опиÑ?оваÑ?Ñ? в 2"
-#: gschem/lib/system-gschemrc.scm:1438
+#: gschem/lib/system-gschemrc.scm:1439
msgid "Copy into 3"
msgstr "Ð?опиÑ?оваÑ?Ñ? в 3"
-#: gschem/lib/system-gschemrc.scm:1439
+#: gschem/lib/system-gschemrc.scm:1440
msgid "Copy into 4"
msgstr "Ð?опиÑ?оваÑ?Ñ? в 4"
-#: gschem/lib/system-gschemrc.scm:1440
+#: gschem/lib/system-gschemrc.scm:1441
msgid "Copy into 5"
msgstr "Ð?опиÑ?оваÑ?Ñ? в 5"
-#: gschem/lib/system-gschemrc.scm:1441
+#: gschem/lib/system-gschemrc.scm:1442
msgid "Cut into 1"
msgstr "Ð?Ñ?Ñ?езаÑ?Ñ? в 1"
-#: gschem/lib/system-gschemrc.scm:1442
+#: gschem/lib/system-gschemrc.scm:1443
msgid "Cut into 2"
msgstr "Ð?Ñ?Ñ?езаÑ?Ñ? в 2"
-#: gschem/lib/system-gschemrc.scm:1443
+#: gschem/lib/system-gschemrc.scm:1444
msgid "Cut into 3"
msgstr "Ð?Ñ?Ñ?езаÑ?Ñ? в 3"
-#: gschem/lib/system-gschemrc.scm:1444
+#: gschem/lib/system-gschemrc.scm:1445
msgid "Cut into 4"
msgstr "Ð?Ñ?Ñ?езаÑ?Ñ? в 4"
-#: gschem/lib/system-gschemrc.scm:1445
+#: gschem/lib/system-gschemrc.scm:1446
msgid "Cut into 5"
msgstr "Ð?Ñ?Ñ?езаÑ?Ñ? в 5"
-#: gschem/lib/system-gschemrc.scm:1446
+#: gschem/lib/system-gschemrc.scm:1447
msgid "Paste from 1"
msgstr "Ð?Ñ?Ñ?авиÑ?Ñ? из 1"
-#: gschem/lib/system-gschemrc.scm:1447
+#: gschem/lib/system-gschemrc.scm:1448
msgid "Paste from 2"
msgstr "Ð?Ñ?Ñ?авиÑ?Ñ? из 2"
-#: gschem/lib/system-gschemrc.scm:1448
+#: gschem/lib/system-gschemrc.scm:1449
msgid "Paste from 3"
msgstr "Ð?Ñ?Ñ?авиÑ?Ñ? из 3"
-#: gschem/lib/system-gschemrc.scm:1449
+#: gschem/lib/system-gschemrc.scm:1450
msgid "Paste from 4"
msgstr "Ð?Ñ?Ñ?авиÑ?Ñ? из 4"
-#: gschem/lib/system-gschemrc.scm:1450
+#: gschem/lib/system-gschemrc.scm:1451
msgid "Paste from 5"
msgstr "Ð?Ñ?Ñ?авиÑ?Ñ? из 5"
-#: gschem/lib/system-gschemrc.scm:1456
+#: gschem/lib/system-gschemrc.scm:1457
msgid "_Redraw"
msgstr "Ð?е_Ñ?еÑ?иÑ?оваÑ?Ñ?"
-#: gschem/lib/system-gschemrc.scm:1457
+#: gschem/lib/system-gschemrc.scm:1458
msgid "_Pan"
msgstr "_ЦенÑ?Ñ?иÑ?оваÑ?Ñ?"
-#: gschem/lib/system-gschemrc.scm:1458
+#: gschem/lib/system-gschemrc.scm:1459
msgid "Zoom _Box"
msgstr "Ð?бла_Ñ?Ñ?Ñ? маÑ?Ñ?Ñ?абиÑ?ованиÑ?"
-#: gschem/lib/system-gschemrc.scm:1459
+#: gschem/lib/system-gschemrc.scm:1460
msgid "Zoom _Extents"
msgstr "Ð?_аÑ?Ñ?Ñ?аб на Ñ?кÑ?ан"
-#: gschem/lib/system-gschemrc.scm:1460
+#: gschem/lib/system-gschemrc.scm:1461
msgid "Zoom _In"
msgstr "У_велиÑ?иÑ?Ñ?"
-#: gschem/lib/system-gschemrc.scm:1461
+#: gschem/lib/system-gschemrc.scm:1462
msgid "Zoom _Out"
msgstr "У_менÑ?Ñ?иÑ?Ñ?"
-#: gschem/lib/system-gschemrc.scm:1462
+#: gschem/lib/system-gschemrc.scm:1463
msgid "Zoom _Full"
msgstr "Це_ликом"
-#: gschem/lib/system-gschemrc.scm:1464
+#: gschem/lib/system-gschemrc.scm:1465
msgid "_Dark color scheme"
msgstr "_ТÑ?мнаÑ? Ñ?веÑ?оваÑ? Ñ?Ñ?ема"
-#: gschem/lib/system-gschemrc.scm:1465
+#: gschem/lib/system-gschemrc.scm:1466
msgid "_Light color scheme"
msgstr "_СвеÑ?лаÑ? Ñ?веÑ?оваÑ? Ñ?Ñ?ема"
-#: gschem/lib/system-gschemrc.scm:1466
+#: gschem/lib/system-gschemrc.scm:1467
#, fuzzy
msgid "B_W color scheme"
msgstr "_ТÑ?мнаÑ? Ñ?веÑ?оваÑ? Ñ?Ñ?ема"
-#: gschem/lib/system-gschemrc.scm:1473
+#: gschem/lib/system-gschemrc.scm:1474
msgid "_Manager..."
msgstr "_Ð?енеджеÑ?..."
-#: gschem/lib/system-gschemrc.scm:1474
+#: gschem/lib/system-gschemrc.scm:1475
msgid "_Previous"
msgstr "_Ð?Ñ?едÑ?дÑ?Ñ?аÑ?"
-#: gschem/lib/system-gschemrc.scm:1475
+#: gschem/lib/system-gschemrc.scm:1476
msgid "_Next"
msgstr "_СледÑ?Ñ?Ñ?аÑ?"
-#: gschem/lib/system-gschemrc.scm:1476
+#: gschem/lib/system-gschemrc.scm:1477
msgid "Ne_w"
msgstr "_Ð?оваÑ?"
-#: gschem/lib/system-gschemrc.scm:1480
+#: gschem/lib/system-gschemrc.scm:1481
msgid "_Discard"
msgstr "_Ð?Ñ?веÑ?гнÑ?Ñ?Ñ?"
-#: gschem/lib/system-gschemrc.scm:1486
+#: gschem/lib/system-gschemrc.scm:1487
msgid "_Component..."
msgstr "_Ð?омпоненÑ?..."
-#: gschem/lib/system-gschemrc.scm:1487
+#: gschem/lib/system-gschemrc.scm:1488
msgid "_Net"
msgstr "_Соединение"
-#: gschem/lib/system-gschemrc.scm:1488
+#: gschem/lib/system-gschemrc.scm:1489
msgid "B_us"
msgstr "_Шина"
-#: gschem/lib/system-gschemrc.scm:1489
+#: gschem/lib/system-gschemrc.scm:1490
msgid "_Attribute..."
msgstr "_Ð?Ñ?Ñ?ибÑ?Ñ?..."
-#: gschem/lib/system-gschemrc.scm:1490
+#: gschem/lib/system-gschemrc.scm:1491
msgid "_Text..."
msgstr "_ТекÑ?Ñ?..."
-#: gschem/lib/system-gschemrc.scm:1492
+#: gschem/lib/system-gschemrc.scm:1493
msgid "_Line"
msgstr "_Ð?иниÑ?"
-#: gschem/lib/system-gschemrc.scm:1493
+#: gschem/lib/system-gschemrc.scm:1494
msgid "_Box"
msgstr "_Ð?Ñ?Ñ?моÑ?голÑ?ник"
-#: gschem/lib/system-gschemrc.scm:1494
+#: gschem/lib/system-gschemrc.scm:1495
msgid "C_ircle"
msgstr "_Ð?кÑ?Ñ?жноÑ?Ñ?Ñ?"
-#: gschem/lib/system-gschemrc.scm:1495
+#: gschem/lib/system-gschemrc.scm:1496
msgid "A_rc"
msgstr "_Ð?Ñ?га"
-#: gschem/lib/system-gschemrc.scm:1496
+#: gschem/lib/system-gschemrc.scm:1497
msgid "_Pin"
msgstr "_Ð?Ñ?вод"
-#: gschem/lib/system-gschemrc.scm:1497
+#: gschem/lib/system-gschemrc.scm:1498
msgid "Pictu_re..."
msgstr "_Ð?зобÑ?ажение..."
-#: gschem/lib/system-gschemrc.scm:1503
+#: gschem/lib/system-gschemrc.scm:1504
msgid "_Down Schematic"
msgstr "Ð?_глÑ?бÑ? Ñ?Ñ?емÑ?"
-#: gschem/lib/system-gschemrc.scm:1504
+#: gschem/lib/system-gschemrc.scm:1505
msgid "Down _Symbol"
msgstr "Ð?г_лÑ?бÑ? Ñ?имвола"
-#: gschem/lib/system-gschemrc.scm:1505
+#: gschem/lib/system-gschemrc.scm:1506
msgid "_Up"
msgstr "Ð?а_веÑ?Ñ?"
-#: gschem/lib/system-gschemrc.scm:1506
+#: gschem/lib/system-gschemrc.scm:1507
msgid "D_ocumentation..."
msgstr "_Ð?окÑ?менÑ?аÑ?иÑ?"
-#: gschem/lib/system-gschemrc.scm:1512
+#: gschem/lib/system-gschemrc.scm:1513
msgid "_Attach"
msgstr "Ð?Ñ?и_Ñ?оединиÑ?Ñ?"
-#: gschem/lib/system-gschemrc.scm:1513
+#: gschem/lib/system-gschemrc.scm:1514
msgid "_Detach"
msgstr "Ð?Ñ?Ñ?ое_диниÑ?Ñ?"
-#: gschem/lib/system-gschemrc.scm:1514
+#: gschem/lib/system-gschemrc.scm:1515
msgid "Show _Value"
msgstr "Ð?оказаÑ?Ñ? _знаÑ?ение"
-#: gschem/lib/system-gschemrc.scm:1515
+#: gschem/lib/system-gschemrc.scm:1516
msgid "Show _Name"
msgstr "Ð?оказаÑ?Ñ? _имÑ?"
-#: gschem/lib/system-gschemrc.scm:1516
+#: gschem/lib/system-gschemrc.scm:1517
msgid "Show _Both"
msgstr "Ð?_оказаÑ?Ñ? имÑ? и знаÑ?ение"
-#: gschem/lib/system-gschemrc.scm:1517
+#: gschem/lib/system-gschemrc.scm:1518
msgid "_Toggle Visibility"
msgstr "Ð?е_Ñ?еклÑ?Ñ?иÑ?Ñ? показаннÑ?е"
-#: gschem/lib/system-gschemrc.scm:1519
+#: gschem/lib/system-gschemrc.scm:1520
msgid "_Find Specific Text..."
msgstr "Ð?айÑ?и _Ñ?екÑ?Ñ?..."
-#: gschem/lib/system-gschemrc.scm:1520
+#: gschem/lib/system-gschemrc.scm:1521
msgid "_Hide Specific Text..."
msgstr "С_кÑ?Ñ?Ñ?Ñ? Ñ?екÑ?Ñ?..."
-#: gschem/lib/system-gschemrc.scm:1521
+#: gschem/lib/system-gschemrc.scm:1522
msgid "_Show Specific Text..."
msgstr "_Ð?оказаÑ?Ñ? Ñ?екÑ?Ñ?..."
-#: gschem/lib/system-gschemrc.scm:1522
+#: gschem/lib/system-gschemrc.scm:1523
msgid "A_utonumber Text..."
msgstr "Ð?вÑ?о_нÑ?меÑ?оваÑ?Ñ? Ñ?екÑ?Ñ?..."
-#: gschem/lib/system-gschemrc.scm:1528
+#: gschem/lib/system-gschemrc.scm:1529
msgid "_Text Size..."
msgstr "_РазмеÑ? Ñ?екÑ?Ñ?а..."
-#: gschem/lib/system-gschemrc.scm:1529
+#: gschem/lib/system-gschemrc.scm:1530
msgid "Cycle _grid styles"
msgstr "Ð?еÑ?еклÑ?Ñ?иÑ?Ñ? Ñ?Ñ?илÑ? Ñ?_еÑ?ки"
-#: gschem/lib/system-gschemrc.scm:1530
+#: gschem/lib/system-gschemrc.scm:1531
msgid "Toggle _Snap On/Off"
msgstr "Ð?клÑ?Ñ?иÑ?Ñ?/вÑ?клÑ?Ñ?иÑ?Ñ? пÑ?и_вÑ?зкÑ?"
-#: gschem/lib/system-gschemrc.scm:1531
+#: gschem/lib/system-gschemrc.scm:1532
msgid "Snap Grid S_pacing..."
msgstr "Ша_г пÑ?ивÑ?зки к Ñ?еÑ?ке..."
-#: gschem/lib/system-gschemrc.scm:1532
+#: gschem/lib/system-gschemrc.scm:1533
msgid "Scale _up Grid Spacing"
msgstr "Уве_лиÑ?иÑ?Ñ? Ñ?еÑ?кÑ?"
-#: gschem/lib/system-gschemrc.scm:1534
+#: gschem/lib/system-gschemrc.scm:1535
msgid "Scale _down Grid Spacing"
msgstr "Уме_нÑ?Ñ?иÑ?Ñ? Ñ?еÑ?кÑ?"
-#: gschem/lib/system-gschemrc.scm:1536
+#: gschem/lib/system-gschemrc.scm:1537
msgid "Toggle _Outline/Box"
msgstr "Ð?еÑ?еклÑ?Ñ?иÑ?Ñ? внеÑ?ний _конÑ?Ñ?Ñ?/бокÑ?"
-#: gschem/lib/system-gschemrc.scm:1538
+#: gschem/lib/system-gschemrc.scm:1539
msgid "Toggle Net _Rubberband"
msgstr "Ð?еÑ?еклÑ?Ñ?иÑ?Ñ? Ñ?е_зиновое Ñ?оединение"
-#: gschem/lib/system-gschemrc.scm:1539
+#: gschem/lib/system-gschemrc.scm:1540
msgid "Toggle _Magnetic Net"
msgstr "Ð?еÑ?еклÑ?Ñ?иÑ?Ñ? _магниÑ?ное Ñ?оединение"
-#: gschem/lib/system-gschemrc.scm:1540
+#: gschem/lib/system-gschemrc.scm:1541
msgid "Show _Log Window..."
msgstr "Ð?оказаÑ?Ñ? окно Ñ?_Ñ?аÑ?Ñ?Ñ?а..."
-#: gschem/lib/system-gschemrc.scm:1542
+#: gschem/lib/system-gschemrc.scm:1543
msgid "Show _Coord Window..."
msgstr "Ð?оказаÑ?Ñ? окно кооÑ?_динаÑ?..."
-#: gschem/lib/system-gschemrc.scm:1558
+#: gschem/lib/system-gschemrc.scm:1559
msgid "gEDA Docu_mentation..."
msgstr "Ð?окÑ?_менÑ?аÑ?иÑ? gEDA"
-#: gschem/lib/system-gschemrc.scm:1559
+#: gschem/lib/system-gschemrc.scm:1560
msgid "gschem _FAQ..."
msgstr "gschem _FAQ"
-#: gschem/lib/system-gschemrc.scm:1560
+#: gschem/lib/system-gschemrc.scm:1561
msgid "gEDA _Wiki..."
msgstr "gEDA _Wiki..."
-#: gschem/lib/system-gschemrc.scm:1561
+#: gschem/lib/system-gschemrc.scm:1562
msgid "Component D_ocumentation..."
msgstr "Ð?окÑ?менÑ?аÑ?иÑ? на _компоненÑ?"
-#: gschem/lib/system-gschemrc.scm:1563
+#: gschem/lib/system-gschemrc.scm:1564
msgid "_Hotkeys..."
msgstr "_Ð?оÑ?Ñ?Ñ?ие клавиÑ?и"
-#: gschem/lib/system-gschemrc.scm:1564
+#: gschem/lib/system-gschemrc.scm:1565
msgid "_About..."
msgstr "Ð? _пÑ?огÑ?амме..."
-#: gschem/lib/system-gschemrc.scm:1570
+#: gschem/lib/system-gschemrc.scm:1571
msgid "_File"
msgstr "Файл"
-#: gschem/lib/system-gschemrc.scm:1571
+#: gschem/lib/system-gschemrc.scm:1572
msgid "_Edit"
msgstr "Ð?Ñ?авка"
-#: gschem/lib/system-gschemrc.scm:1572
+#: gschem/lib/system-gschemrc.scm:1573
msgid "_Buffer"
msgstr "Ð?Ñ?Ñ?еÑ?"
-#: gschem/lib/system-gschemrc.scm:1573
+#: gschem/lib/system-gschemrc.scm:1574
msgid "_View"
msgstr "Ð?ид"
-#: gschem/lib/system-gschemrc.scm:1574
+#: gschem/lib/system-gschemrc.scm:1575
msgid "_Page"
msgstr "СÑ?Ñ?аниÑ?а"
-#: gschem/lib/system-gschemrc.scm:1575
+#: gschem/lib/system-gschemrc.scm:1576
msgid "_Add"
msgstr "Ð?обавиÑ?Ñ?"
-#: gschem/lib/system-gschemrc.scm:1576
+#: gschem/lib/system-gschemrc.scm:1577
msgid "Hie_rarchy"
msgstr "Ð?еÑ?аÑ?Ñ?иÑ?"
-#: gschem/lib/system-gschemrc.scm:1577
+#: gschem/lib/system-gschemrc.scm:1578
msgid "A_ttributes"
msgstr "Ð?Ñ?Ñ?ибÑ?Ñ?Ñ?"
-#: gschem/lib/system-gschemrc.scm:1578
+#: gschem/lib/system-gschemrc.scm:1579
msgid "_Options"
msgstr "Ð?аÑ?Ñ?Ñ?ойки"
-#: gschem/lib/system-gschemrc.scm:1579
+#: gschem/lib/system-gschemrc.scm:1580
msgid "_Help"
msgstr "Ð?омоÑ?Ñ?"
+#~ msgid "Scheme directory NOT set!\n"
+#~ msgstr "Ð?аÑ?алог Ñ?Ñ?ем Ð?Ð? Ñ?Ñ?Ñ?ановлен!\n"
+
+#~ msgid "MakeVisible"
+#~ msgstr "СделаÑ?Ñ? видимÑ?м"
+
+#~ msgid ""
+#~ "Usage: %s [OPTIONS] schematic_filename1 ... schematic_filenameN\n"
+#~ " -q Quiet mode\n"
+#~ " -v Verbose mode on\n"
+#~ " -r filename Rc filename\n"
+#~ " -s filename Script (guile) filename\n"
+#~ " -o filename Output filename (for printing)\n"
+#~ " -p Automatically place the window\n"
+#~ " -t Print stroke information\n"
+#~ " -h Help; this message\n"
+#~ "\n"
+#~ msgstr ""
+#~ "Ð?Ñ?полÑ?зование: %s [Ð?Ð?ЦÐ?Ð?] Ñ?айл_Ñ?Ñ?емÑ?1 ... Ñ?айл_Ñ?Ñ?емÑ?N\n"
+#~ " -q Ð?иÑ?его не вÑ?водиÑ?Ñ?\n"
+#~ " -v Режим оÑ?ладоÑ?нÑ?Ñ? Ñ?ообÑ?ений\n"
+#~ " -r ФÐ?Ð?Ð? Ð?Ñ?полÑ?зоваÑ?Ñ? в каÑ?еÑ?Ñ?ве конÑ?игÑ?Ñ?аÑ?ионного Ñ?айл ФÐ?Ð?Ð?\n"
+#~ " -s ФÐ?Ð?Ð? Ð?мÑ? ФÐ?Ð?Ð?а Ñ?кÑ?ипÑ?а (guile)\n"
+#~ " -o ФÐ?Ð?Ð? Ð?мÑ? вÑ?Ñ?одного ФÐ?Ð?Ð?а (длÑ? пеÑ?аÑ?и)\n"
+#~ " -p Ð?вÑ?омаÑ?иÑ?еÑ?ки Ñ?аÑ?положиÑ?Ñ? окно\n"
+#~ " -t Ð?еÑ?аÑ?аÑ?Ñ? Ñ?Ñ?Ñ?иÑ?овÑ?Ñ? инÑ?оÑ?маÑ?иÑ?\n"
+#~ " -h Ð?омоÑ?Ñ?; Ñ?Ñ?о Ñ?ообÑ?ение\n"
+#~ "\n"
+
+#~ msgid "Couldn't open file %s\n"
+#~ msgstr "Ð?е Ñ?далоÑ?Ñ? оÑ?кÑ?Ñ?Ñ?Ñ? Ñ?айл %s\n"
+
+#~ msgid "Clear"
+#~ msgstr "Ð?Ñ?иÑ?Ñ?иÑ?Ñ?"
+
+#~ msgid "Make Inv Text Vis"
+#~ msgstr "СделаÑ?Ñ? невидимÑ?й Ñ?екÑ?Ñ? видимÑ?м"
+
#~ msgid "Update Cues"
#~ msgstr "Ð?бновиÑ?Ñ? Ñ?игналÑ?"
diff --git a/gschem/po/tr.po b/gschem/po/tr.po
index 7fe046b..816201f 100644
--- a/gschem/po/tr.po
+++ b/gschem/po/tr.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2010-11-07 13:37+0000\n"
+"POT-Creation-Date: 2011-01-16 00:11-0500\n"
"PO-Revision-Date: 2010-02-11 03:48+0000\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -22,17 +22,17 @@ msgstr ""
msgid "Zoom too small! Cannot zoom further.\n"
msgstr ""
-#: gschem/src/g_funcs.c:339 gschem/src/i_callbacks.c:68
+#: gschem/src/g_funcs.c:347 gschem/src/i_callbacks.c:68
#, c-format
msgid "Could not fork\n"
msgstr ""
-#: gschem/src/g_funcs.c:355 gschem/src/i_callbacks.c:78
+#: gschem/src/g_funcs.c:363 gschem/src/i_callbacks.c:78
#, c-format
msgid "Could not invoke %s\n"
msgstr ""
-#: gschem/src/g_funcs.c:361 gschem/src/i_callbacks.c:82
+#: gschem/src/g_funcs.c:369 gschem/src/i_callbacks.c:82
msgid "Documentation commands not supported under MinGW.\n"
msgstr "Dokümantasyon komutları MinGW altında desteklenmemektedir.\n"
@@ -121,39 +121,39 @@ msgstr ""
msgid "Invalid number of steps [%d] scrollpan-steps\n"
msgstr ""
-#: gschem/src/gschem.c:184
+#: gschem/src/gschem.c:188
#, c-format
msgid "gEDA/gschem version %s%s.%s\n"
msgstr ""
-#: gschem/src/gschem.c:187
+#: gschem/src/gschem.c:191
msgid ""
"gEDA/gschem comes with ABSOLUTELY NO WARRANTY; see COPYING for more "
"details.\n"
msgstr ""
-#: gschem/src/gschem.c:189
+#: gschem/src/gschem.c:193
msgid ""
"This is free software, and you are welcome to redistribute it under certain\n"
msgstr ""
-#: gschem/src/gschem.c:191
+#: gschem/src/gschem.c:195
msgid ""
"conditions; please see the COPYING file for more details.\n"
"\n"
msgstr ""
-#: gschem/src/gschem.c:194
+#: gschem/src/gschem.c:198
#, c-format
msgid "This is the MINGW32 port.\n"
msgstr ""
-#: gschem/src/gschem.c:198
+#: gschem/src/gschem.c:202
#, c-format
msgid "Current locale settings: %s\n"
msgstr "Å?u andaki yerel ayarlar: %s\n"
-#: gschem/src/gschem.c:213
+#: gschem/src/gschem.c:218
msgid ""
"You must set the GEDADATA environment variable!\n"
"\n"
@@ -161,31 +161,21 @@ msgid ""
"environment variable to point to the correct location.\n"
msgstr ""
-#: gschem/src/gschem.c:248
+#: gschem/src/gschem.c:256
#, c-format
msgid "Couldn't find init scm file [%s]\n"
msgstr ""
-#: gschem/src/gschem.c:252
+#: gschem/src/gschem.c:260
#, c-format
msgid "Read init scm file [%s]\n"
msgstr ""
-#: gschem/src/gschem.c:256
+#: gschem/src/gschem.c:264
#, c-format
msgid "Failed to read init scm file [%s]\n"
msgstr ""
-#: gschem/src/gschem.c:317
-#, c-format
-msgid "Scheme directory NOT set!\n"
-msgstr "Å?ema dizini ayarlanmamıÅ?!\n"
-
-#: gschem/src/gschem.c:324 gschem/src/x_script.c:66
-#, c-format
-msgid "Executing guile script [%s]\n"
-msgstr ""
-
#: gschem/src/gschem_cairo.c:310
#, c-format
msgid "Unknown end for line (%d)\n"
@@ -209,11 +199,11 @@ msgstr ""
msgid "Text Mode"
msgstr "Metin kipi"
-#: gschem/src/i_basic.c:84 gschem/lib/system-gschemrc.scm:1409
+#: gschem/src/i_basic.c:84 gschem/lib/system-gschemrc.scm:1411
msgid "Copy Mode"
msgstr "Kopyalama Kipi"
-#: gschem/src/i_basic.c:87 gschem/lib/system-gschemrc.scm:1411
+#: gschem/src/i_basic.c:87 gschem/lib/system-gschemrc.scm:1413
msgid "Move Mode"
msgstr "TaÅ?ıma Kipi"
@@ -221,7 +211,7 @@ msgstr "TaÅ?ıma Kipi"
msgid "Rotate Mode"
msgstr "Döndürme kipi"
-#: gschem/src/i_basic.c:91 gschem/lib/system-gschemrc.scm:1413
+#: gschem/src/i_basic.c:91 gschem/lib/system-gschemrc.scm:1415
msgid "Mirror Mode"
msgstr "Ayna modu"
@@ -274,22 +264,22 @@ msgstr ""
msgid "Pin Mode"
msgstr ""
-#: gschem/src/i_basic.c:135 gschem/src/i_callbacks.c:544
-#: gschem/src/i_callbacks.c:568
+#: gschem/src/i_basic.c:135 gschem/src/i_callbacks.c:576
+#: gschem/src/i_callbacks.c:600
msgid "Copy"
msgstr "Kopyala"
-#: gschem/src/i_basic.c:137 gschem/src/i_callbacks.c:634
-#: gschem/src/i_callbacks.c:658
+#: gschem/src/i_basic.c:137 gschem/src/i_callbacks.c:666
+#: gschem/src/i_callbacks.c:690
msgid "Move"
msgstr "TaÅ?ı"
-#: gschem/src/i_basic.c:139 gschem/src/i_callbacks.c:589
-#: gschem/src/i_callbacks.c:613
+#: gschem/src/i_basic.c:139 gschem/src/i_callbacks.c:621
+#: gschem/src/i_callbacks.c:645
msgid "Multiple Copy"
msgstr "Ã?oklu kopyala"
-#: gschem/src/i_basic.c:142 gschem/lib/system-gschemrc.scm:1410
+#: gschem/src/i_basic.c:142 gschem/lib/system-gschemrc.scm:1412
msgid "Multiple Copy Mode"
msgstr "Ã?oklu Kopyalama Kipi"
@@ -309,7 +299,7 @@ msgstr ""
msgid "Action"
msgstr ""
-#: gschem/src/i_basic.c:260 gschem/src/x_dialog.c:2312
+#: gschem/src/i_basic.c:260 gschem/src/x_dialog.c:2316
#: gschem/src/x_window.c:491
msgid "Stroke"
msgstr ""
@@ -340,7 +330,7 @@ msgstr ""
msgid "Documentation for [%s,%s,%s,%s]\n"
msgstr ""
-#: gschem/src/i_callbacks.c:123 gschem/src/i_callbacks.c:1699
+#: gschem/src/i_callbacks.c:123 gschem/src/i_callbacks.c:1706
#, c-format
msgid "New page created [%s]\n"
msgstr "Yeni sayfa oluÅ?turuldu [%s]\n"
@@ -362,327 +352,323 @@ msgstr "Hepsi kaydedildi"
msgid "Closing Window\n"
msgstr "Pencere kapatılıyor\n"
-#: gschem/src/i_callbacks.c:549 gschem/src/i_callbacks.c:594
-#: gschem/src/i_callbacks.c:639
+#: gschem/src/i_callbacks.c:581 gschem/src/i_callbacks.c:626
+#: gschem/src/i_callbacks.c:671
msgid "Select objs first"
msgstr ""
-#: gschem/src/i_callbacks.c:678 gschem/src/x_multiattrib.c:1491
+#: gschem/src/i_callbacks.c:710 gschem/src/x_multiattrib.c:1503
msgid "Delete"
msgstr "Sil"
-#: gschem/src/i_callbacks.c:703
+#: gschem/src/i_callbacks.c:735
msgid "Edit"
msgstr "Düzenle"
-#: gschem/src/i_callbacks.c:718
+#: gschem/src/i_callbacks.c:750
msgid "Edit pin type"
msgstr ""
-#: gschem/src/i_callbacks.c:737
+#: gschem/src/i_callbacks.c:769
msgid "Edit Text"
msgstr "Metni Düzenle"
-#: gschem/src/i_callbacks.c:760
+#: gschem/src/i_callbacks.c:792
msgid "Slot"
msgstr "Slot"
-#: gschem/src/i_callbacks.c:777
+#: gschem/src/i_callbacks.c:809
msgid "Color"
msgstr "Renk"
-#: gschem/src/i_callbacks.c:814 gschem/src/i_callbacks.c:859
+#: gschem/src/i_callbacks.c:846 gschem/src/i_callbacks.c:891
msgid "Rotate"
msgstr "Döndür"
-#: gschem/src/i_callbacks.c:882 gschem/src/i_callbacks.c:907
+#: gschem/src/i_callbacks.c:913 gschem/src/i_callbacks.c:938
msgid "Mirror"
msgstr ""
-#: gschem/src/i_callbacks.c:928 gschem/src/x_dialog.c:2315
-#: gschem/lib/system-gschemrc.scm:1422
+#: gschem/src/i_callbacks.c:959 gschem/src/x_dialog.c:2319
+#: gschem/lib/system-gschemrc.scm:1424
msgid "Lock"
msgstr "Kilitle"
-#: gschem/src/i_callbacks.c:946 gschem/lib/system-gschemrc.scm:1423
+#: gschem/src/i_callbacks.c:977 gschem/lib/system-gschemrc.scm:1425
msgid "Unlock"
msgstr "Kilidi Aç"
-#: gschem/src/i_callbacks.c:964 gschem/src/x_dialog.c:1734
+#: gschem/src/i_callbacks.c:995 gschem/src/x_dialog.c:1737
msgid "Translate"
msgstr "Ã?evir"
-#: gschem/src/i_callbacks.c:967
+#: gschem/src/i_callbacks.c:998
msgid "WARNING: Do not translate with snap off!\n"
msgstr ""
-#: gschem/src/i_callbacks.c:968
+#: gschem/src/i_callbacks.c:999
msgid "WARNING: Turning snap on and continuing with translate.\n"
msgstr ""
-#: gschem/src/i_callbacks.c:975
+#: gschem/src/i_callbacks.c:1006
msgid "WARNING: Snap grid size is not equal to 100!\n"
msgstr ""
-#: gschem/src/i_callbacks.c:977
+#: gschem/src/i_callbacks.c:1008
msgid ""
"WARNING: If you are translating a symbol to the origin, the snap grid size "
"should be set to 100\n"
msgstr ""
-#: gschem/src/i_callbacks.c:1008
+#: gschem/src/i_callbacks.c:1039
msgid "Embed"
msgstr ""
-#: gschem/src/i_callbacks.c:1047
+#: gschem/src/i_callbacks.c:1078
msgid "Unembed"
msgstr ""
-#: gschem/src/i_callbacks.c:1089
+#: gschem/src/i_callbacks.c:1120
msgid "Update"
msgstr "Güncelle"
-#: gschem/src/i_callbacks.c:1136
+#: gschem/src/i_callbacks.c:1167
msgid "ShowHidden"
msgstr ""
-#: gschem/src/i_callbacks.c:1160
-msgid "MakeVisible"
-msgstr ""
-
-#: gschem/src/i_callbacks.c:1466 gschem/src/i_callbacks.c:1538
+#: gschem/src/i_callbacks.c:1473 gschem/src/i_callbacks.c:1545
msgid "Pan"
msgstr "Kaydırma"
-#: gschem/src/i_callbacks.c:1743
+#: gschem/src/i_callbacks.c:1750
msgid "Really revert page?"
msgstr ""
-#: gschem/src/i_callbacks.c:1813
+#: gschem/src/i_callbacks.c:1820
msgid "Copy to clipboard"
msgstr ""
-#: gschem/src/i_callbacks.c:1831
+#: gschem/src/i_callbacks.c:1838
msgid "Cut to clipboard"
msgstr ""
-#: gschem/src/i_callbacks.c:1849
+#: gschem/src/i_callbacks.c:1856
msgid "Paste from clipboard"
msgstr ""
-#: gschem/src/i_callbacks.c:1861 gschem/src/i_callbacks.c:2100
-#: gschem/src/i_callbacks.c:2122 gschem/src/i_callbacks.c:2144
-#: gschem/src/i_callbacks.c:2166 gschem/src/i_callbacks.c:2188
+#: gschem/src/i_callbacks.c:1868 gschem/src/i_callbacks.c:2107
+#: gschem/src/i_callbacks.c:2129 gschem/src/i_callbacks.c:2151
+#: gschem/src/i_callbacks.c:2173 gschem/src/i_callbacks.c:2195
msgid "Empty buffer"
msgstr ""
-#: gschem/src/i_callbacks.c:1906
+#: gschem/src/i_callbacks.c:1913
msgid "Copy 1"
msgstr ""
-#: gschem/src/i_callbacks.c:1925
+#: gschem/src/i_callbacks.c:1932
msgid "Copy 2"
msgstr ""
-#: gschem/src/i_callbacks.c:1944
+#: gschem/src/i_callbacks.c:1951
msgid "Copy 3"
msgstr ""
-#: gschem/src/i_callbacks.c:1963
+#: gschem/src/i_callbacks.c:1970
msgid "Copy 4"
msgstr ""
-#: gschem/src/i_callbacks.c:1982
+#: gschem/src/i_callbacks.c:1989
msgid "Copy 5"
msgstr ""
-#: gschem/src/i_callbacks.c:2001
+#: gschem/src/i_callbacks.c:2008
msgid "Cut 1"
msgstr ""
-#: gschem/src/i_callbacks.c:2020
+#: gschem/src/i_callbacks.c:2027
msgid "Cut 2"
msgstr ""
-#: gschem/src/i_callbacks.c:2039
+#: gschem/src/i_callbacks.c:2046
msgid "Cut 3"
msgstr ""
-#: gschem/src/i_callbacks.c:2058
+#: gschem/src/i_callbacks.c:2065
msgid "Cut 4"
msgstr ""
-#: gschem/src/i_callbacks.c:2077
+#: gschem/src/i_callbacks.c:2084
msgid "Cut 5"
msgstr ""
-#: gschem/src/i_callbacks.c:2093
+#: gschem/src/i_callbacks.c:2100
msgid "Paste 1"
msgstr ""
-#: gschem/src/i_callbacks.c:2115
+#: gschem/src/i_callbacks.c:2122
msgid "Paste 2"
msgstr ""
-#: gschem/src/i_callbacks.c:2137
+#: gschem/src/i_callbacks.c:2144
msgid "Paste 3"
msgstr ""
-#: gschem/src/i_callbacks.c:2159
+#: gschem/src/i_callbacks.c:2166
msgid "Paste 4"
msgstr ""
-#: gschem/src/i_callbacks.c:2181
+#: gschem/src/i_callbacks.c:2188
msgid "Paste 5"
msgstr ""
-#: gschem/src/i_callbacks.c:2318 gschem/src/x_window.c:355
+#: gschem/src/i_callbacks.c:2325 gschem/src/x_window.c:355
msgid "Component"
msgstr ""
-#: gschem/src/i_callbacks.c:2354 gschem/src/i_callbacks.c:2373
-#: gschem/src/x_dialog.c:2285
+#: gschem/src/i_callbacks.c:2361 gschem/src/i_callbacks.c:2380
+#: gschem/src/x_dialog.c:2289
msgid "Attribute"
msgstr ""
-#: gschem/src/i_callbacks.c:2395 gschem/src/i_callbacks.c:2422
-#: gschem/src/x_dialog.c:2282
+#: gschem/src/i_callbacks.c:2402 gschem/src/i_callbacks.c:2429
+#: gschem/src/x_dialog.c:2286
msgid "Net"
msgstr "AÄ?"
-#: gschem/src/i_callbacks.c:2466 gschem/src/i_callbacks.c:2493
-#: gschem/src/x_dialog.c:2300 gschem/src/x_window.c:375
+#: gschem/src/i_callbacks.c:2473 gschem/src/i_callbacks.c:2500
+#: gschem/src/x_dialog.c:2304 gschem/src/x_window.c:375
msgid "Bus"
msgstr "Veriyolu"
-#: gschem/src/i_callbacks.c:2574 gschem/src/i_callbacks.c:2597
+#: gschem/src/i_callbacks.c:2581 gschem/src/i_callbacks.c:2604
msgid "Line"
msgstr "Satır"
-#: gschem/src/i_callbacks.c:2619 gschem/src/i_callbacks.c:2642
+#: gschem/src/i_callbacks.c:2626 gschem/src/i_callbacks.c:2649
msgid "Box"
msgstr "Kutu"
-#: gschem/src/i_callbacks.c:2698 gschem/src/i_callbacks.c:2722
+#: gschem/src/i_callbacks.c:2705 gschem/src/i_callbacks.c:2729
msgid "Circle"
msgstr "Daire"
-#: gschem/src/i_callbacks.c:2744 gschem/src/i_callbacks.c:2767
+#: gschem/src/i_callbacks.c:2751 gschem/src/i_callbacks.c:2774
msgid "Arc"
msgstr "EÄ?ri"
-#: gschem/src/i_callbacks.c:2789 gschem/src/i_callbacks.c:2812
-#: gschem/src/x_dialog.c:2273
+#: gschem/src/i_callbacks.c:2796 gschem/src/i_callbacks.c:2819
+#: gschem/src/x_dialog.c:2277
msgid "Pin"
msgstr ""
-#: gschem/src/i_callbacks.c:2871
+#: gschem/src/i_callbacks.c:2878
#, c-format
msgid "Searching for source [%s]\n"
msgstr ""
-#: gschem/src/i_callbacks.c:2895
+#: gschem/src/i_callbacks.c:2902
#, c-format
msgid "Cannot find source [%s]\n"
msgstr ""
-#: gschem/src/i_callbacks.c:2964
+#: gschem/src/i_callbacks.c:2965
#, c-format
msgid "Searching for symbol [%s]\n"
msgstr ""
-#: gschem/src/i_callbacks.c:2970
+#: gschem/src/i_callbacks.c:2971
msgid "Symbol is not a real file. Symbol cannot be loaded.\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3001
+#: gschem/src/i_callbacks.c:3002
msgid "Cannot find any schematics above the current one!\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3055
+#: gschem/src/i_callbacks.c:3056
msgid ""
"This command retrieves the component documentation from the web, but there "
"is no component selected"
msgstr ""
-#: gschem/src/i_callbacks.c:3083
+#: gschem/src/i_callbacks.c:3084
msgid "Attach"
msgstr "Ekle"
-#: gschem/src/i_callbacks.c:3130
+#: gschem/src/i_callbacks.c:3131
msgid "Detach"
msgstr "Ayır"
-#: gschem/src/i_callbacks.c:3165
+#: gschem/src/i_callbacks.c:3166
msgid "ShowN"
msgstr ""
-#: gschem/src/i_callbacks.c:3201
+#: gschem/src/i_callbacks.c:3202
msgid "ShowV"
msgstr ""
-#: gschem/src/i_callbacks.c:3237
+#: gschem/src/i_callbacks.c:3238
msgid "ShowB"
msgstr ""
-#: gschem/src/i_callbacks.c:3274
+#: gschem/src/i_callbacks.c:3275
msgid "VisToggle"
msgstr ""
-#: gschem/src/i_callbacks.c:3304
+#: gschem/src/i_callbacks.c:3305
#, c-format
msgid "Sorry but this is a non-functioning menu option\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3394
+#: gschem/src/i_callbacks.c:3395
msgid "Action feedback mode set to OUTLINE\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3397
+#: gschem/src/i_callbacks.c:3398
msgid "Action feedback mode set to BOUNDINGBOX\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3422
+#: gschem/src/i_callbacks.c:3423
msgid "Grid OFF\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3423
+#: gschem/src/i_callbacks.c:3424
msgid "Dot grid selected\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3424
+#: gschem/src/i_callbacks.c:3425
msgid "Mesh grid selected\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3445
+#: gschem/src/i_callbacks.c:3446
msgid "Snap OFF (CAUTION!)\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3448
+#: gschem/src/i_callbacks.c:3449
msgid "Snap ON\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3451
+#: gschem/src/i_callbacks.c:3452
msgid "Snap back to the grid (CAUTION!)\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3477
+#: gschem/src/i_callbacks.c:3478
msgid "Rubber band OFF \n"
msgstr ""
-#: gschem/src/i_callbacks.c:3480
+#: gschem/src/i_callbacks.c:3481
msgid "Rubber band ON\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3495
+#: gschem/src/i_callbacks.c:3496
msgid "magnetic net mode: ON\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3498
+#: gschem/src/i_callbacks.c:3499
msgid "magnetic net mode: OFF\n"
msgstr ""
-#: gschem/src/o_box.c:153
+#: gschem/src/o_box.c:149
#, c-format
msgid "Unknown type for box (fill)!\n"
msgstr ""
@@ -702,17 +688,17 @@ msgstr ""
msgid "Got an invalid buffer_number [o_buffer_paste_start]\n"
msgstr ""
-#: gschem/src/o_bus.c:118
+#: gschem/src/o_bus.c:117
#, c-format
msgid "Got an invalid which one in o_bus_draw_stretch\n"
msgstr ""
-#: gschem/src/o_circle.c:134
+#: gschem/src/o_circle.c:130
#, c-format
msgid "Unknown type for circle (fill)!\n"
msgstr ""
-#: gschem/src/o_complex.c:243 gschem/src/o_complex.c:247
+#: gschem/src/o_complex.c:237 gschem/src/o_complex.c:241
#, c-format
msgid "Translating schematic [%d %d]\n"
msgstr ""
@@ -730,35 +716,35 @@ msgstr ""
msgid "Object already unlocked\n"
msgstr ""
-#: gschem/src/o_misc.c:413
+#: gschem/src/o_misc.c:409
msgid "Hidden text is now visible\n"
msgstr ""
-#: gschem/src/o_misc.c:415
+#: gschem/src/o_misc.c:411
msgid "Hidden text is now invisible\n"
msgstr ""
-#: gschem/src/o_misc.c:668
+#: gschem/src/o_misc.c:636
#, c-format
msgid "Could not find symbol [%s] in library. Update failed.\n"
msgstr ""
-#: gschem/src/o_misc.c:783
+#: gschem/src/o_misc.c:751
#, c-format
msgid "o_autosave_backups: Can't get the real filename of %s."
msgstr ""
-#: gschem/src/o_misc.c:827
+#: gschem/src/o_misc.c:795
#, c-format
msgid "Could NOT set previous backup file [%s] read-write\n"
msgstr ""
-#: gschem/src/o_misc.c:845
+#: gschem/src/o_misc.c:815
#, c-format
msgid "Could NOT set backup file [%s] readonly\n"
msgstr ""
-#: gschem/src/o_misc.c:850
+#: gschem/src/o_misc.c:820
#, c-format
msgid "Could NOT save backup file [%s]\n"
msgstr ""
@@ -778,36 +764,36 @@ msgstr ""
msgid "Got a non line object in o_move_check_endpoint\n"
msgstr ""
-#: gschem/src/o_net.c:159
+#: gschem/src/o_net.c:158
#, c-format
msgid "Got an invalid which one in o_net_draw_stretch\n"
msgstr ""
-#: gschem/src/o_net.c:538
+#: gschem/src/o_net.c:537
msgid "Warning: Starting net at off grid coordinate\n"
msgstr ""
-#: gschem/src/o_net.c:600
+#: gschem/src/o_net.c:599
msgid "Warning: Ending net at off grid coordinate\n"
msgstr ""
-#: gschem/src/o_net.c:932 gschem/src/o_net.c:969 gschem/src/o_net.c:1040
-#: gschem/src/o_net.c:1076
+#: gschem/src/o_net.c:931 gschem/src/o_net.c:968 gschem/src/o_net.c:1039
+#: gschem/src/o_net.c:1075
#, c-format
msgid "Tried to add more than two bus rippers. Internal gschem error.\n"
msgstr ""
-#: gschem/src/o_net.c:1144
+#: gschem/src/o_net.c:1143
#, c-format
msgid "Bus ripper symbol [%s] was not found in any component library\n"
msgstr ""
-#: gschem/src/o_path.c:352
+#: gschem/src/o_path.c:348
#, c-format
msgid "Unknown type for path (fill)!\n"
msgstr ""
-#: gschem/src/o_picture.c:163 gschem/src/o_picture.c:539
+#: gschem/src/o_picture.c:163 gschem/src/o_picture.c:537
#, c-format
msgid "Failed to load picture: %s"
msgstr ""
@@ -816,7 +802,7 @@ msgstr ""
msgid "Picture"
msgstr ""
-#: gschem/src/o_picture.c:447 gschem/src/x_attribedit.c:141
+#: gschem/src/o_picture.c:445 gschem/src/x_attribedit.c:141
#, c-format
msgid "ERROR: NULL object!\n"
msgstr ""
@@ -837,23 +823,45 @@ msgstr ""
msgid "New slot number out of range\n"
msgstr ""
-#: gschem/src/o_undo.c:304
+#: gschem/src/o_undo.c:303
msgid "Undo/Redo disabled in rc file\n"
msgstr ""
-#: gschem/src/parsecmd.c:47
+#: gschem/src/parsecmd.c:81
#, c-format
msgid ""
-"Usage: %s [OPTIONS] schematic_filename1 ... schematic_filenameN\n"
-" -q Quiet mode\n"
-" -v Verbose mode on\n"
-" -r filename Rc filename\n"
-" -s filename Script (guile) filename\n"
-" -o filename Output filename (for printing)\n"
-" -p Automatically place the window\n"
-" -t Print stroke information\n"
-" -h Help; this message\n"
+"Usage: %s [OPTION ...] [--] [FILE ...]\n"
"\n"
+"Interactively edit gEDA schematics or symbols. If one or more FILEs\n"
+"are specified, open them for editing; otherwise, create a new, empty\n"
+"schematic.\n"
+"\n"
+"Options:\n"
+" -q, --quiet Quiet mode.\n"
+" -v, --verbose Verbose mode.\n"
+" -r, --config-file=FILE Additional configuration file to load.\n"
+" -L DIR Add DIR to Scheme search path.\n"
+" -c EXPR Scheme expression to run at startup.\n"
+" -s FILE Scheme script to run at startup.\n"
+" -o, --output=FILE Output filename (for printing).\n"
+" -p Automatically place the window.\n"
+" -V, --version Show version information.\n"
+" -h, --help Help; this message.\n"
+" -- Treat all remaining arguments as filenames.\n"
+"\n"
+"Report bugs to <geda-bug@xxxxxxxx>\n"
+"gEDA/gaf homepage: <http://gpleda.org>\n"
+msgstr ""
+
+#: gschem/src/parsecmd.c:115
+#, c-format
+msgid ""
+"gEDA %s (g%.7s)\n"
+"Copyright (C) 1998-2011 gEDA developers\n"
+"This is free software, and you are welcome to redistribute it under\n"
+"certain conditions. For details, see the file `COPYING', which is\n"
+"included in the gEDA distribution.\n"
+"There is NO WARRANTY, to the extent permitted by law.\n"
msgstr ""
#: gschem/src/x_attribedit.c:127
@@ -865,56 +873,56 @@ msgstr ""
msgid "Single Attribute Editor"
msgstr ""
-#: gschem/src/x_attribedit.c:358
+#: gschem/src/x_attribedit.c:359
msgid "<b>Edit Attribute</b>"
msgstr ""
-#: gschem/src/x_attribedit.c:360
+#: gschem/src/x_attribedit.c:361
msgid "<b>Add Attribute</b>"
msgstr ""
-#: gschem/src/x_attribedit.c:376 gschem/src/x_multiattrib.c:1916
+#: gschem/src/x_attribedit.c:377 gschem/src/x_multiattrib.c:1927
msgid "Name:"
msgstr ""
-#: gschem/src/x_attribedit.c:393 gschem/src/x_multiattrib.c:1935
+#: gschem/src/x_attribedit.c:394 gschem/src/x_multiattrib.c:1946
msgid "Value:"
msgstr ""
-#: gschem/src/x_attribedit.c:409 gschem/src/x_multiattrib.c:1978
+#: gschem/src/x_attribedit.c:410 gschem/src/x_multiattrib.c:1989
msgid "Visible"
msgstr ""
-#: gschem/src/x_attribedit.c:429
+#: gschem/src/x_attribedit.c:430
msgid "Show Value Only"
msgstr ""
-#: gschem/src/x_attribedit.c:431
+#: gschem/src/x_attribedit.c:432
msgid "Show Name Only"
msgstr ""
-#: gschem/src/x_attribedit.c:433 gschem/src/x_multiattrib.c:1454
+#: gschem/src/x_attribedit.c:434 gschem/src/x_multiattrib.c:1466
msgid "Show Name & Value"
msgstr ""
-#: gschem/src/x_attribedit.c:440
+#: gschem/src/x_attribedit.c:441
msgid "<b>Attach Options</b>"
msgstr ""
-#: gschem/src/x_attribedit.c:455
+#: gschem/src/x_attribedit.c:456
msgid "All"
msgstr ""
-#: gschem/src/x_attribedit.c:463 gschem/src/x_compselect.c:896
-#: gschem/src/x_compselect.c:1010
+#: gschem/src/x_attribedit.c:464 gschem/src/x_compselect.c:904
+#: gschem/src/x_compselect.c:1018
msgid "Components"
msgstr ""
-#: gschem/src/x_attribedit.c:471 gschem/src/x_window.c:365
+#: gschem/src/x_attribedit.c:472 gschem/src/x_window.c:365
msgid "Nets"
msgstr ""
-#: gschem/src/x_attribedit.c:479
+#: gschem/src/x_attribedit.c:480
msgid "Replace existing attributes"
msgstr ""
@@ -930,91 +938,91 @@ msgid ""
"duplicate slot may cause problems: [symbolname=%s, number=%d, slot=%d]\n"
msgstr ""
-#: gschem/src/x_autonumber.c:673
+#: gschem/src/x_autonumber.c:675
msgid "No searchstring given in autonumber text.\n"
msgstr ""
-#: gschem/src/x_autonumber.c:725
+#: gschem/src/x_autonumber.c:727
msgid "No '*' or '?' given at the end of the autonumber text.\n"
msgstr ""
-#: gschem/src/x_autonumber.c:860
+#: gschem/src/x_autonumber.c:862
msgid "Diagonal"
msgstr ""
-#: gschem/src/x_autonumber.c:861
+#: gschem/src/x_autonumber.c:863
msgid "Top to bottom"
msgstr ""
-#: gschem/src/x_autonumber.c:861
+#: gschem/src/x_autonumber.c:863
msgid "Bottom to top"
msgstr ""
-#: gschem/src/x_autonumber.c:862
+#: gschem/src/x_autonumber.c:864
msgid "Left to right"
msgstr ""
-#: gschem/src/x_autonumber.c:862
+#: gschem/src/x_autonumber.c:864
msgid "Right to left"
msgstr ""
-#: gschem/src/x_autonumber.c:863
+#: gschem/src/x_autonumber.c:865
msgid "File order"
msgstr ""
-#: gschem/src/x_autonumber.c:1199
+#: gschem/src/x_autonumber.c:1201
msgid "Autonumber text"
msgstr ""
-#: gschem/src/x_autonumber.c:1223
+#: gschem/src/x_autonumber.c:1225
msgid "<b>Scope</b>"
msgstr ""
-#: gschem/src/x_autonumber.c:1245
+#: gschem/src/x_autonumber.c:1247
msgid "Search for:"
msgstr ""
-#: gschem/src/x_autonumber.c:1259
+#: gschem/src/x_autonumber.c:1261
msgid "Autonumber text in:"
msgstr ""
-#: gschem/src/x_autonumber.c:1266
+#: gschem/src/x_autonumber.c:1268
msgid "Skip numbers found in:"
msgstr ""
-#: gschem/src/x_autonumber.c:1278 gschem/src/x_autonumber.c:1287
+#: gschem/src/x_autonumber.c:1280 gschem/src/x_autonumber.c:1289
msgid "Selected objects"
msgstr ""
-#: gschem/src/x_autonumber.c:1279 gschem/src/x_autonumber.c:1288
+#: gschem/src/x_autonumber.c:1281 gschem/src/x_autonumber.c:1290
msgid "Current page"
msgstr ""
-#: gschem/src/x_autonumber.c:1280 gschem/src/x_autonumber.c:1289
+#: gschem/src/x_autonumber.c:1282 gschem/src/x_autonumber.c:1291
msgid "Whole hierarchy"
msgstr ""
-#: gschem/src/x_autonumber.c:1291
+#: gschem/src/x_autonumber.c:1293
msgid "Overwrite existing numbers"
msgstr ""
-#: gschem/src/x_autonumber.c:1296
+#: gschem/src/x_autonumber.c:1298
msgid "<b>Options</b>"
msgstr ""
-#: gschem/src/x_autonumber.c:1318
+#: gschem/src/x_autonumber.c:1320
msgid "Starting number:"
msgstr ""
-#: gschem/src/x_autonumber.c:1325
+#: gschem/src/x_autonumber.c:1327
msgid "Sort order:"
msgstr ""
-#: gschem/src/x_autonumber.c:1346
+#: gschem/src/x_autonumber.c:1348
msgid "Remove numbers"
msgstr ""
-#: gschem/src/x_autonumber.c:1350
+#: gschem/src/x_autonumber.c:1352
msgid "Automatic slotting"
msgstr ""
@@ -1051,48 +1059,48 @@ msgstr ""
msgid "Tried to get an invalid outline color: %d\n"
msgstr ""
-#: gschem/src/x_compselect.c:1040
+#: gschem/src/x_compselect.c:1048
msgid "Filter:"
msgstr ""
-#: gschem/src/x_compselect.c:1143 gschem/src/x_dialog.c:3663
-#: gschem/src/x_multiattrib.c:1782
+#: gschem/src/x_compselect.c:1151 gschem/src/x_dialog.c:3667
+#: gschem/src/x_multiattrib.c:1793
msgid "Name"
msgstr ""
-#: gschem/src/x_compselect.c:1152 gschem/src/x_multiattrib.c:1806
+#: gschem/src/x_compselect.c:1160 gschem/src/x_multiattrib.c:1817
msgid "Value"
msgstr ""
-#: gschem/src/x_compselect.c:1191
+#: gschem/src/x_compselect.c:1199
msgid "Default behavior - reference component"
msgstr ""
-#: gschem/src/x_compselect.c:1194
+#: gschem/src/x_compselect.c:1202
msgid "Embed component in schematic"
msgstr ""
-#: gschem/src/x_compselect.c:1197
+#: gschem/src/x_compselect.c:1205
msgid "Include component as individual objects"
msgstr ""
-#: gschem/src/x_compselect.c:1354
+#: gschem/src/x_compselect.c:1362
msgid "Select Component..."
msgstr ""
-#: gschem/src/x_compselect.c:1377
+#: gschem/src/x_compselect.c:1385
msgid "In Use"
msgstr ""
-#: gschem/src/x_compselect.c:1381
+#: gschem/src/x_compselect.c:1389
msgid "Libraries"
msgstr ""
-#: gschem/src/x_compselect.c:1390 gschem/src/x_fileselect.c:122
+#: gschem/src/x_compselect.c:1398 gschem/src/x_fileselect.c:122
msgid "Preview"
msgstr ""
-#: gschem/src/x_compselect.c:1418
+#: gschem/src/x_compselect.c:1426
msgid "Attributes"
msgstr "Ã?znitelikler"
@@ -1147,336 +1155,336 @@ msgstr ""
msgid "Edit Text Properties"
msgstr ""
-#: gschem/src/x_dialog.c:471
+#: gschem/src/x_dialog.c:472
msgid "<b>Text Content</b>"
msgstr ""
-#: gschem/src/x_dialog.c:507
+#: gschem/src/x_dialog.c:508
msgid "<b>Text Properties</b>"
msgstr ""
-#: gschem/src/x_dialog.c:522
+#: gschem/src/x_dialog.c:523
msgid "Color:"
msgstr ""
-#: gschem/src/x_dialog.c:529
+#: gschem/src/x_dialog.c:530
msgid "Size:"
msgstr ""
-#: gschem/src/x_dialog.c:538
+#: gschem/src/x_dialog.c:539
msgid "Alignment:"
msgstr ""
-#: gschem/src/x_dialog.c:587
+#: gschem/src/x_dialog.c:588
msgid "Solid"
msgstr ""
-#: gschem/src/x_dialog.c:588
+#: gschem/src/x_dialog.c:589
msgid "Dotted"
msgstr ""
-#: gschem/src/x_dialog.c:589
+#: gschem/src/x_dialog.c:590
msgid "Dashed"
msgstr ""
-#: gschem/src/x_dialog.c:590
+#: gschem/src/x_dialog.c:591
msgid "Center"
msgstr ""
-#: gschem/src/x_dialog.c:591
+#: gschem/src/x_dialog.c:592
msgid "Phantom"
msgstr ""
-#: gschem/src/x_dialog.c:592 gschem/src/x_dialog.c:689
-#: gschem/src/x_dialog.c:698 gschem/src/x_dialog.c:707
-#: gschem/src/x_dialog.c:808 gschem/src/x_dialog.c:810
-#: gschem/src/x_dialog.c:812 gschem/src/x_dialog.c:1038
-#: gschem/src/x_dialog.c:1141 gschem/src/x_dialog.c:1150
-#: gschem/src/x_dialog.c:1159 gschem/src/x_dialog.c:1168
-#: gschem/src/x_dialog.c:1177 gschem/src/x_dialog.c:1290
-#: gschem/src/x_dialog.c:1292 gschem/src/x_dialog.c:1294
-#: gschem/src/x_dialog.c:1296 gschem/src/x_dialog.c:1298
+#: gschem/src/x_dialog.c:593 gschem/src/x_dialog.c:690
+#: gschem/src/x_dialog.c:699 gschem/src/x_dialog.c:708
+#: gschem/src/x_dialog.c:809 gschem/src/x_dialog.c:811
+#: gschem/src/x_dialog.c:813 gschem/src/x_dialog.c:1039
+#: gschem/src/x_dialog.c:1142 gschem/src/x_dialog.c:1151
+#: gschem/src/x_dialog.c:1160 gschem/src/x_dialog.c:1169
+#: gschem/src/x_dialog.c:1178 gschem/src/x_dialog.c:1291
+#: gschem/src/x_dialog.c:1293 gschem/src/x_dialog.c:1295
+#: gschem/src/x_dialog.c:1297 gschem/src/x_dialog.c:1299
msgid "*unchanged*"
msgstr ""
-#: gschem/src/x_dialog.c:916
+#: gschem/src/x_dialog.c:917
msgid "Edit Line Width & Type"
msgstr ""
-#: gschem/src/x_dialog.c:955 gschem/src/x_print.c:307
+#: gschem/src/x_dialog.c:956 gschem/src/x_print.c:307
msgid "Type:"
msgstr ""
-#: gschem/src/x_dialog.c:959
+#: gschem/src/x_dialog.c:960
msgid "Width:"
msgstr ""
-#: gschem/src/x_dialog.c:963
+#: gschem/src/x_dialog.c:964
msgid "Dash Length:"
msgstr ""
-#: gschem/src/x_dialog.c:967
+#: gschem/src/x_dialog.c:968
msgid "Dash Space:"
msgstr ""
-#: gschem/src/x_dialog.c:1034
+#: gschem/src/x_dialog.c:1035
msgid "Hollow"
msgstr ""
-#: gschem/src/x_dialog.c:1035
+#: gschem/src/x_dialog.c:1036
msgid "Filled"
msgstr ""
-#: gschem/src/x_dialog.c:1036
+#: gschem/src/x_dialog.c:1037
msgid "Mesh"
msgstr ""
-#: gschem/src/x_dialog.c:1037
+#: gschem/src/x_dialog.c:1038
msgid "Hatch"
msgstr ""
-#: gschem/src/x_dialog.c:1406
+#: gschem/src/x_dialog.c:1407
msgid "Edit Fill Type"
msgstr ""
-#: gschem/src/x_dialog.c:1444
+#: gschem/src/x_dialog.c:1446
msgid "Fill Type:"
msgstr ""
-#: gschem/src/x_dialog.c:1448
+#: gschem/src/x_dialog.c:1450
msgid "Line Width:"
msgstr ""
-#: gschem/src/x_dialog.c:1452
+#: gschem/src/x_dialog.c:1454
msgid "Angle 1:"
msgstr ""
-#: gschem/src/x_dialog.c:1456
+#: gschem/src/x_dialog.c:1458
msgid "Pitch 1:"
msgstr ""
-#: gschem/src/x_dialog.c:1460
+#: gschem/src/x_dialog.c:1462
msgid "Angle 2:"
msgstr ""
-#: gschem/src/x_dialog.c:1464
+#: gschem/src/x_dialog.c:1466
msgid "Pitch 2:"
msgstr ""
-#: gschem/src/x_dialog.c:1591
+#: gschem/src/x_dialog.c:1593
msgid "Arc Params"
msgstr ""
-#: gschem/src/x_dialog.c:1631
+#: gschem/src/x_dialog.c:1634
msgid "Arc Radius:"
msgstr ""
-#: gschem/src/x_dialog.c:1639
+#: gschem/src/x_dialog.c:1642
msgid "Start Angle:"
msgstr ""
-#: gschem/src/x_dialog.c:1647
+#: gschem/src/x_dialog.c:1650
msgid "Degrees of Sweep:"
msgstr ""
-#: gschem/src/x_dialog.c:1764
+#: gschem/src/x_dialog.c:1768
msgid ""
"Offset to translate?\n"
"(0 for origin)"
msgstr ""
-#: gschem/src/x_dialog.c:1832
+#: gschem/src/x_dialog.c:1836
msgid "Text Size"
msgstr ""
-#: gschem/src/x_dialog.c:1862
+#: gschem/src/x_dialog.c:1866
msgid "Enter new text size:"
msgstr ""
-#: gschem/src/x_dialog.c:1938
+#: gschem/src/x_dialog.c:1942
msgid "Snap Size"
msgstr ""
-#: gschem/src/x_dialog.c:1968
+#: gschem/src/x_dialog.c:1972
msgid "Enter new snap grid spacing:"
msgstr ""
-#: gschem/src/x_dialog.c:2045
+#: gschem/src/x_dialog.c:2049
msgid "Edit slot number"
msgstr ""
-#: gschem/src/x_dialog.c:2076
+#: gschem/src/x_dialog.c:2080
msgid "Edit slot number:"
msgstr ""
-#: gschem/src/x_dialog.c:2117
+#: gschem/src/x_dialog.c:2121
#, c-format
msgid "%s%s (%s)"
msgstr ""
-#: gschem/src/x_dialog.c:2140
+#: gschem/src/x_dialog.c:2144
msgid "About gschem"
msgstr "gschem Hakkında"
-#: gschem/src/x_dialog.c:2141
+#: gschem/src/x_dialog.c:2145
msgid "gEDA: GPL Electronic Design Automation"
msgstr ""
-#: gschem/src/x_dialog.c:2142
+#: gschem/src/x_dialog.c:2146
msgid ""
"Copyright © 1998-2009 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
"Copyright © 1998-2009 gEDA Contributors (see ChangeLog for details)"
msgstr ""
-#: gschem/src/x_dialog.c:2201
+#: gschem/src/x_dialog.c:2205
msgid "Coords"
msgstr ""
-#: gschem/src/x_dialog.c:2222
+#: gschem/src/x_dialog.c:2226
msgid "Screen"
msgstr ""
-#: gschem/src/x_dialog.c:2231
+#: gschem/src/x_dialog.c:2235
msgid "World"
msgstr ""
-#: gschem/src/x_dialog.c:2270
+#: gschem/src/x_dialog.c:2274
msgid "Background"
msgstr ""
-#: gschem/src/x_dialog.c:2276
+#: gschem/src/x_dialog.c:2280
msgid "Net endpoint"
msgstr ""
-#: gschem/src/x_dialog.c:2279
+#: gschem/src/x_dialog.c:2283
msgid "Graphic"
msgstr ""
-#: gschem/src/x_dialog.c:2288
+#: gschem/src/x_dialog.c:2292
msgid "Logic bubble"
msgstr ""
-#: gschem/src/x_dialog.c:2291
+#: gschem/src/x_dialog.c:2295
msgid "Grid point"
msgstr ""
-#: gschem/src/x_dialog.c:2294
+#: gschem/src/x_dialog.c:2298
msgid "Detached attribute"
msgstr ""
-#: gschem/src/x_dialog.c:2297 gschem/src/x_window.c:383
+#: gschem/src/x_dialog.c:2301 gschem/src/x_window.c:383
msgid "Text"
msgstr ""
-#: gschem/src/x_dialog.c:2303
+#: gschem/src/x_dialog.c:2307
msgid "Selection"
msgstr ""
-#: gschem/src/x_dialog.c:2306
+#: gschem/src/x_dialog.c:2310
msgid "Bounding box"
msgstr ""
-#: gschem/src/x_dialog.c:2309
+#: gschem/src/x_dialog.c:2313
msgid "Zoom box"
msgstr ""
-#: gschem/src/x_dialog.c:2318
+#: gschem/src/x_dialog.c:2322
msgid "Output background"
msgstr ""
-#: gschem/src/x_dialog.c:2321
+#: gschem/src/x_dialog.c:2325
msgid "Net junction"
msgstr ""
-#: gschem/src/x_dialog.c:2324
+#: gschem/src/x_dialog.c:2328
msgid "Mesh grid major"
msgstr ""
-#: gschem/src/x_dialog.c:2327
+#: gschem/src/x_dialog.c:2331
msgid "Mesh grid minor"
msgstr ""
-#: gschem/src/x_dialog.c:2330
+#: gschem/src/x_dialog.c:2334
msgid "Unknown"
msgstr ""
-#: gschem/src/x_dialog.c:2481
+#: gschem/src/x_dialog.c:2485
#, c-format
msgid "ERROR: NULL object in color_edit_dialog_apply!\n"
msgstr ""
-#: gschem/src/x_dialog.c:2525
+#: gschem/src/x_dialog.c:2529
msgid "Color Edit"
msgstr ""
-#: gschem/src/x_dialog.c:2556
+#: gschem/src/x_dialog.c:2560
msgid "Object color:"
msgstr ""
-#: gschem/src/x_dialog.c:2614
+#: gschem/src/x_dialog.c:2618
msgid "Hotkeys"
msgstr "Kısayollar"
-#: gschem/src/x_dialog.c:2678
+#: gschem/src/x_dialog.c:2682
msgid "Function"
msgstr ""
-#: gschem/src/x_dialog.c:2685
+#: gschem/src/x_dialog.c:2689
msgid "Keystroke(s)"
msgstr ""
-#: gschem/src/x_dialog.c:2991
+#: gschem/src/x_dialog.c:2995
msgid "Find Text"
msgstr ""
-#: gschem/src/x_dialog.c:3022
+#: gschem/src/x_dialog.c:3026
msgid "Text to find:"
msgstr ""
-#: gschem/src/x_dialog.c:3032
+#: gschem/src/x_dialog.c:3036
msgid "descend into hierarchy"
msgstr ""
-#: gschem/src/x_dialog.c:3097
+#: gschem/src/x_dialog.c:3101
msgid "Hide Text"
msgstr ""
-#: gschem/src/x_dialog.c:3128
+#: gschem/src/x_dialog.c:3132
msgid "Hide text starting with:"
msgstr ""
-#: gschem/src/x_dialog.c:3197
+#: gschem/src/x_dialog.c:3201
msgid "Show Text"
msgstr ""
-#: gschem/src/x_dialog.c:3228
+#: gschem/src/x_dialog.c:3232
msgid "Show text starting with:"
msgstr ""
-#: gschem/src/x_dialog.c:3685
+#: gschem/src/x_dialog.c:3689
msgid "S_elect the schematics you want to save:"
msgstr ""
-#: gschem/src/x_dialog.c:3779
+#: gschem/src/x_dialog.c:3784
#, c-format
msgid "Save the changes to schematic \"%s\" before closing?"
msgstr ""
-#: gschem/src/x_dialog.c:3785
+#: gschem/src/x_dialog.c:3790
#, c-format
msgid ""
"There are %d schematics with unsaved changes. Save changes before closing?"
msgstr ""
-#: gschem/src/x_dialog.c:3814
+#: gschem/src/x_dialog.c:3819
msgid "If you don't save, all your changes will be permanently lost."
msgstr ""
-#: gschem/src/x_dialog.c:3834
+#: gschem/src/x_dialog.c:3839
msgid "_Close without saving"
msgstr ""
-#: gschem/src/x_dialog.c:4170
+#: gschem/src/x_dialog.c:4175
#, c-format
msgid ""
"<span weight=\"bold\" size=\"larger\">The input attribute \"%s\" is invalid\n"
@@ -1487,19 +1495,19 @@ msgid ""
"The value cannot start with a space."
msgstr ""
-#: gschem/src/x_dialog.c:4172
+#: gschem/src/x_dialog.c:4177
msgid "Invalid Attribute"
msgstr ""
-#: gschem/src/x_dialog.c:4208
+#: gschem/src/x_dialog.c:4213
msgid "Pin type"
msgstr ""
-#: gschem/src/x_dialog.c:4232
+#: gschem/src/x_dialog.c:4237
msgid "Net pin"
msgstr ""
-#: gschem/src/x_dialog.c:4234
+#: gschem/src/x_dialog.c:4239
msgid "Bus pin (graphical)"
msgstr ""
@@ -1592,11 +1600,11 @@ msgstr ""
msgid "Write image..."
msgstr "imaj olarak yaz"
-#: gschem/src/x_log.c:188
+#: gschem/src/x_log.c:209
msgid "** Invalid UTF-8 in log message. See stderr or gschem.log.\n"
msgstr ""
-#: gschem/src/x_log.c:256
+#: gschem/src/x_log.c:288
msgid "Status"
msgstr ""
@@ -1672,69 +1680,60 @@ msgstr ""
msgid "/Up"
msgstr ""
-#: gschem/src/x_menus.c:321
+#: gschem/src/x_menus.c:323
#, c-format
msgid "Tried to set the sensitivity on non-existent menu item '%s'\n"
msgstr ""
-#: gschem/src/x_menus.c:345
+#: gschem/src/x_menus.c:347
msgid "Popup_menu_item_factory doesn't exist!\n"
msgstr ""
-#: gschem/src/x_menus.c:358
+#: gschem/src/x_menus.c:360
msgid "Tried to set the sensitivity on a non-existent popup menu_item\n"
msgstr ""
-#: gschem/src/x_menus.c:438
-#, c-format
-msgid "Couldn't open file %s\n"
-msgstr ""
-
-#: gschem/src/x_menus.c:495
-msgid "Clear"
-msgstr ""
-
-#: gschem/src/x_multiattrib.c:911
+#: gschem/src/x_multiattrib.c:915
msgid "Attributes with empty name are not allowed. Please set a name."
msgstr ""
-#: gschem/src/x_multiattrib.c:1456
+#: gschem/src/x_multiattrib.c:1468
msgid "Show Value only"
msgstr ""
-#: gschem/src/x_multiattrib.c:1458
+#: gschem/src/x_multiattrib.c:1470
msgid "Show Name only"
msgstr ""
-#: gschem/src/x_multiattrib.c:1486
+#: gschem/src/x_multiattrib.c:1498
msgid "Promote"
msgstr ""
-#: gschem/src/x_multiattrib.c:1490
+#: gschem/src/x_multiattrib.c:1502
msgid "Duplicate"
msgstr ""
-#: gschem/src/x_multiattrib.c:1708
+#: gschem/src/x_multiattrib.c:1719
msgid "Edit Attributes"
msgstr ""
-#: gschem/src/x_multiattrib.c:1826
+#: gschem/src/x_multiattrib.c:1837
msgid "Vis?"
msgstr ""
-#: gschem/src/x_multiattrib.c:1844
+#: gschem/src/x_multiattrib.c:1855
msgid "N"
msgstr ""
-#: gschem/src/x_multiattrib.c:1862
+#: gschem/src/x_multiattrib.c:1873
msgid "V"
msgstr ""
-#: gschem/src/x_multiattrib.c:1884
+#: gschem/src/x_multiattrib.c:1895
msgid "Show inherited attributes"
msgstr ""
-#: gschem/src/x_multiattrib.c:1900
+#: gschem/src/x_multiattrib.c:1911
msgid "Add Attribute"
msgstr ""
@@ -1758,23 +1757,23 @@ msgstr "Sayfayı Kapat"
msgid "Discard Page"
msgstr ""
-#: gschem/src/x_pagesel.c:376
+#: gschem/src/x_pagesel.c:375
msgid "Page Manager"
msgstr ""
-#: gschem/src/x_pagesel.c:432
+#: gschem/src/x_pagesel.c:431
msgid "Filename"
msgstr ""
-#: gschem/src/x_pagesel.c:448
+#: gschem/src/x_pagesel.c:447
msgid "Changed"
msgstr ""
-#: gschem/src/x_pagesel.c:468
+#: gschem/src/x_pagesel.c:467
msgid "Right click on the filename for more options..."
msgstr ""
-#: gschem/src/x_preview.c:234
+#: gschem/src/x_preview.c:233
msgid "Preview Buffer"
msgstr ""
@@ -1830,23 +1829,23 @@ msgstr ""
msgid "Command:"
msgstr ""
-#: gschem/src/x_print.c:741
+#: gschem/src/x_print.c:745
msgid "No print destination specified\n"
msgstr ""
-#: gschem/src/x_print.c:748
+#: gschem/src/x_print.c:752
#, c-format
msgid "Cannot print current schematic to [%s]\n"
msgstr ""
-#: gschem/src/x_print.c:757
+#: gschem/src/x_print.c:761
#, c-format
msgid ""
"Error printing to file '%s'\n"
"Check the log window for more information"
msgstr ""
-#: gschem/src/x_print.c:764
+#: gschem/src/x_print.c:768
#, c-format
msgid "Printed current schematic to [%s]\n"
msgstr ""
@@ -1855,6 +1854,11 @@ msgstr ""
msgid "Execute Script..."
msgstr "Betik Ã?alıÅ?tır..."
+#: gschem/src/x_script.c:66
+#, c-format
+msgid "Executing guile script [%s]\n"
+msgstr ""
+
#: gschem/src/x_window.c:81
#, c-format
msgid "Couldn't allocate gc\n"
@@ -1962,35 +1966,35 @@ msgstr ""
msgid "New file [%s]\n"
msgstr ""
-#: gschem/src/x_window.c:857
+#: gschem/src/x_window.c:855
#, c-format
msgid "Could NOT save page [%s]\n"
msgstr ""
-#: gschem/src/x_window.c:858
+#: gschem/src/x_window.c:856
msgid "Error while trying to save"
msgstr ""
-#: gschem/src/x_window.c:867
+#: gschem/src/x_window.c:865
#, c-format
msgid "Saved as [%s]\n"
msgstr ""
-#: gschem/src/x_window.c:869
+#: gschem/src/x_window.c:867
#, c-format
msgid "Saved [%s]\n"
msgstr ""
-#: gschem/src/x_window.c:871
+#: gschem/src/x_window.c:869
msgid "Saved"
msgstr ""
-#: gschem/src/x_window.c:945
+#: gschem/src/x_window.c:943
#, c-format
msgid "Discarding page [%s]\n"
msgstr ""
-#: gschem/src/x_window.c:945
+#: gschem/src/x_window.c:943
#, c-format
msgid "Closing [%s]\n"
msgstr ""
@@ -2031,7 +2035,7 @@ msgstr ""
msgid "Save All"
msgstr "Tümünü kaydet"
-#: gschem/lib/system-gschemrc.scm:1386 gschem/lib/system-gschemrc.scm:1477
+#: gschem/lib/system-gschemrc.scm:1386 gschem/lib/system-gschemrc.scm:1478
msgid "_Revert"
msgstr ""
@@ -2043,7 +2047,7 @@ msgstr ""
msgid "Write _image..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1393 gschem/lib/system-gschemrc.scm:1478
+#: gschem/lib/system-gschemrc.scm:1393 gschem/lib/system-gschemrc.scm:1479
msgid "_Close"
msgstr ""
@@ -2075,390 +2079,401 @@ msgstr ""
msgid "_Delete"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1412
+#: gschem/lib/system-gschemrc.scm:1409
+#, fuzzy
+msgid "Select All"
+msgstr "Seçim Kipi"
+
+#: gschem/lib/system-gschemrc.scm:1410
+msgid "Deselect"
+msgstr ""
+
+#: gschem/lib/system-gschemrc.scm:1414
msgid "Rotate 90 Mode"
msgstr "90 derece döndür kipi"
-#: gschem/lib/system-gschemrc.scm:1415
+#: gschem/lib/system-gschemrc.scm:1417
msgid "Edit..."
msgstr "Düzenle..."
-#: gschem/lib/system-gschemrc.scm:1416
+#: gschem/lib/system-gschemrc.scm:1418
msgid "Edit Text..."
msgstr "Metin Düzenle..."
-#: gschem/lib/system-gschemrc.scm:1417
+#: gschem/lib/system-gschemrc.scm:1419
msgid "Slot..."
msgstr "Yuva..."
-#: gschem/lib/system-gschemrc.scm:1418
+#: gschem/lib/system-gschemrc.scm:1420
msgid "Color..."
msgstr "Renk..."
-#: gschem/lib/system-gschemrc.scm:1419
+#: gschem/lib/system-gschemrc.scm:1421
msgid "Line Width & Type..."
msgstr "Ã?izgi KalınlıÄ?ı & Tipi"
-#: gschem/lib/system-gschemrc.scm:1420
+#: gschem/lib/system-gschemrc.scm:1422
msgid "Fill Type..."
msgstr "doldurma tipi.."
-#: gschem/lib/system-gschemrc.scm:1421
+#: gschem/lib/system-gschemrc.scm:1423
msgid "Symbol Translate..."
msgstr "Sembölü çevir.."
-#: gschem/lib/system-gschemrc.scm:1425
+#: gschem/lib/system-gschemrc.scm:1427
msgid "Invoke Macro"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1426
+#: gschem/lib/system-gschemrc.scm:1428
msgid "Embed Component/Picture"
msgstr "BileÅ?en/Resim göm"
-#: gschem/lib/system-gschemrc.scm:1427
+#: gschem/lib/system-gschemrc.scm:1429
msgid "Unembed Component/Picture"
msgstr "BileÅ?en/resim gömme"
-#: gschem/lib/system-gschemrc.scm:1428
+#: gschem/lib/system-gschemrc.scm:1430
msgid "Update Component"
msgstr "BileÅ?en Güncelle"
-#: gschem/lib/system-gschemrc.scm:1429
+#: gschem/lib/system-gschemrc.scm:1431
msgid "Show/Hide Inv Text"
msgstr "Metni Göster/Gizle"
-#: gschem/lib/system-gschemrc.scm:1430
-msgid "Make Inv Text Vis"
-msgstr "Metni Görünür Yap"
-
-#: gschem/lib/system-gschemrc.scm:1436
+#: gschem/lib/system-gschemrc.scm:1437
msgid "Copy into 1"
msgstr "1'e kopyala"
-#: gschem/lib/system-gschemrc.scm:1437
+#: gschem/lib/system-gschemrc.scm:1438
msgid "Copy into 2"
msgstr "2'ye kopyala"
-#: gschem/lib/system-gschemrc.scm:1438
+#: gschem/lib/system-gschemrc.scm:1439
msgid "Copy into 3"
msgstr "3'e kopyala"
-#: gschem/lib/system-gschemrc.scm:1439
+#: gschem/lib/system-gschemrc.scm:1440
msgid "Copy into 4"
msgstr "4'e kopyala"
-#: gschem/lib/system-gschemrc.scm:1440
+#: gschem/lib/system-gschemrc.scm:1441
msgid "Copy into 5"
msgstr "5'e kopyala"
-#: gschem/lib/system-gschemrc.scm:1441
+#: gschem/lib/system-gschemrc.scm:1442
msgid "Cut into 1"
msgstr "1'e Kes"
-#: gschem/lib/system-gschemrc.scm:1442
+#: gschem/lib/system-gschemrc.scm:1443
msgid "Cut into 2"
msgstr "2'ye Kes"
-#: gschem/lib/system-gschemrc.scm:1443
+#: gschem/lib/system-gschemrc.scm:1444
msgid "Cut into 3"
msgstr "3'e Kes"
-#: gschem/lib/system-gschemrc.scm:1444
+#: gschem/lib/system-gschemrc.scm:1445
msgid "Cut into 4"
msgstr "4'e Kes"
-#: gschem/lib/system-gschemrc.scm:1445
+#: gschem/lib/system-gschemrc.scm:1446
msgid "Cut into 5"
msgstr "5'e Kes"
-#: gschem/lib/system-gschemrc.scm:1446
+#: gschem/lib/system-gschemrc.scm:1447
msgid "Paste from 1"
msgstr "1'den yapıÅ?tır"
-#: gschem/lib/system-gschemrc.scm:1447
+#: gschem/lib/system-gschemrc.scm:1448
msgid "Paste from 2"
msgstr "2'den yapıÅ?tır"
-#: gschem/lib/system-gschemrc.scm:1448
+#: gschem/lib/system-gschemrc.scm:1449
msgid "Paste from 3"
msgstr "3'ten yapıÅ?tır"
-#: gschem/lib/system-gschemrc.scm:1449
+#: gschem/lib/system-gschemrc.scm:1450
msgid "Paste from 4"
msgstr "4'ten yapıÅ?tır"
-#: gschem/lib/system-gschemrc.scm:1450
+#: gschem/lib/system-gschemrc.scm:1451
msgid "Paste from 5"
msgstr "5'ten yapıÅ?tır"
-#: gschem/lib/system-gschemrc.scm:1456
+#: gschem/lib/system-gschemrc.scm:1457
msgid "_Redraw"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1457
+#: gschem/lib/system-gschemrc.scm:1458
msgid "_Pan"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1458
+#: gschem/lib/system-gschemrc.scm:1459
msgid "Zoom _Box"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1459
+#: gschem/lib/system-gschemrc.scm:1460
msgid "Zoom _Extents"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1460
+#: gschem/lib/system-gschemrc.scm:1461
msgid "Zoom _In"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1461
+#: gschem/lib/system-gschemrc.scm:1462
msgid "Zoom _Out"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1462
+#: gschem/lib/system-gschemrc.scm:1463
msgid "Zoom _Full"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1464
+#: gschem/lib/system-gschemrc.scm:1465
msgid "_Dark color scheme"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1465
+#: gschem/lib/system-gschemrc.scm:1466
msgid "_Light color scheme"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1466
+#: gschem/lib/system-gschemrc.scm:1467
msgid "B_W color scheme"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1473
+#: gschem/lib/system-gschemrc.scm:1474
msgid "_Manager..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1474
+#: gschem/lib/system-gschemrc.scm:1475
msgid "_Previous"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1475
+#: gschem/lib/system-gschemrc.scm:1476
msgid "_Next"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1476
+#: gschem/lib/system-gschemrc.scm:1477
msgid "Ne_w"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1480
+#: gschem/lib/system-gschemrc.scm:1481
msgid "_Discard"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1486
+#: gschem/lib/system-gschemrc.scm:1487
msgid "_Component..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1487
+#: gschem/lib/system-gschemrc.scm:1488
msgid "_Net"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1488
+#: gschem/lib/system-gschemrc.scm:1489
msgid "B_us"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1489
+#: gschem/lib/system-gschemrc.scm:1490
msgid "_Attribute..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1490
+#: gschem/lib/system-gschemrc.scm:1491
msgid "_Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1492
+#: gschem/lib/system-gschemrc.scm:1493
msgid "_Line"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1493
+#: gschem/lib/system-gschemrc.scm:1494
msgid "_Box"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1494
+#: gschem/lib/system-gschemrc.scm:1495
msgid "C_ircle"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1495
+#: gschem/lib/system-gschemrc.scm:1496
msgid "A_rc"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1496
+#: gschem/lib/system-gschemrc.scm:1497
msgid "_Pin"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1497
+#: gschem/lib/system-gschemrc.scm:1498
msgid "Pictu_re..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1503
+#: gschem/lib/system-gschemrc.scm:1504
msgid "_Down Schematic"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1504
+#: gschem/lib/system-gschemrc.scm:1505
msgid "Down _Symbol"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1505
+#: gschem/lib/system-gschemrc.scm:1506
msgid "_Up"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1506
+#: gschem/lib/system-gschemrc.scm:1507
msgid "D_ocumentation..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1512
+#: gschem/lib/system-gschemrc.scm:1513
msgid "_Attach"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1513
+#: gschem/lib/system-gschemrc.scm:1514
msgid "_Detach"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1514
+#: gschem/lib/system-gschemrc.scm:1515
msgid "Show _Value"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1515
+#: gschem/lib/system-gschemrc.scm:1516
msgid "Show _Name"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1516
+#: gschem/lib/system-gschemrc.scm:1517
msgid "Show _Both"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1517
+#: gschem/lib/system-gschemrc.scm:1518
msgid "_Toggle Visibility"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1519
+#: gschem/lib/system-gschemrc.scm:1520
msgid "_Find Specific Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1520
+#: gschem/lib/system-gschemrc.scm:1521
msgid "_Hide Specific Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1521
+#: gschem/lib/system-gschemrc.scm:1522
msgid "_Show Specific Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1522
+#: gschem/lib/system-gschemrc.scm:1523
msgid "A_utonumber Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1528
+#: gschem/lib/system-gschemrc.scm:1529
msgid "_Text Size..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1529
+#: gschem/lib/system-gschemrc.scm:1530
msgid "Cycle _grid styles"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1530
+#: gschem/lib/system-gschemrc.scm:1531
msgid "Toggle _Snap On/Off"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1531
+#: gschem/lib/system-gschemrc.scm:1532
msgid "Snap Grid S_pacing..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1532
+#: gschem/lib/system-gschemrc.scm:1533
msgid "Scale _up Grid Spacing"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1534
+#: gschem/lib/system-gschemrc.scm:1535
msgid "Scale _down Grid Spacing"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1536
+#: gschem/lib/system-gschemrc.scm:1537
msgid "Toggle _Outline/Box"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1538
+#: gschem/lib/system-gschemrc.scm:1539
msgid "Toggle Net _Rubberband"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1539
+#: gschem/lib/system-gschemrc.scm:1540
msgid "Toggle _Magnetic Net"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1540
+#: gschem/lib/system-gschemrc.scm:1541
msgid "Show _Log Window..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1542
+#: gschem/lib/system-gschemrc.scm:1543
msgid "Show _Coord Window..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1558
+#: gschem/lib/system-gschemrc.scm:1559
msgid "gEDA Docu_mentation..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1559
+#: gschem/lib/system-gschemrc.scm:1560
msgid "gschem _FAQ..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1560
+#: gschem/lib/system-gschemrc.scm:1561
msgid "gEDA _Wiki..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1561
+#: gschem/lib/system-gschemrc.scm:1562
msgid "Component D_ocumentation..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1563
+#: gschem/lib/system-gschemrc.scm:1564
msgid "_Hotkeys..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1564
+#: gschem/lib/system-gschemrc.scm:1565
msgid "_About..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1570
+#: gschem/lib/system-gschemrc.scm:1571
msgid "_File"
msgstr "Dosya"
-#: gschem/lib/system-gschemrc.scm:1571
+#: gschem/lib/system-gschemrc.scm:1572
msgid "_Edit"
msgstr "Düzenle"
-#: gschem/lib/system-gschemrc.scm:1572
+#: gschem/lib/system-gschemrc.scm:1573
msgid "_Buffer"
msgstr "Tampon"
-#: gschem/lib/system-gschemrc.scm:1573
+#: gschem/lib/system-gschemrc.scm:1574
msgid "_View"
msgstr "Görüntüle"
-#: gschem/lib/system-gschemrc.scm:1574
+#: gschem/lib/system-gschemrc.scm:1575
msgid "_Page"
msgstr "Sayfa"
-#: gschem/lib/system-gschemrc.scm:1575
+#: gschem/lib/system-gschemrc.scm:1576
msgid "_Add"
msgstr "Ekle"
-#: gschem/lib/system-gschemrc.scm:1576
+#: gschem/lib/system-gschemrc.scm:1577
msgid "Hie_rarchy"
msgstr "HiyerarÅ?i"
-#: gschem/lib/system-gschemrc.scm:1577
+#: gschem/lib/system-gschemrc.scm:1578
msgid "A_ttributes"
msgstr "Ã?znitelikler"
-#: gschem/lib/system-gschemrc.scm:1578
+#: gschem/lib/system-gschemrc.scm:1579
msgid "_Options"
msgstr "Seçenekler"
-#: gschem/lib/system-gschemrc.scm:1579
+#: gschem/lib/system-gschemrc.scm:1580
msgid "_Help"
msgstr "Yardım"
+#~ msgid "Scheme directory NOT set!\n"
+#~ msgstr "Å?ema dizini ayarlanmamıÅ?!\n"
+
+#~ msgid "Make Inv Text Vis"
+#~ msgstr "Metni Görünür Yap"
+
#~ msgid "Recent files"
#~ msgstr "Son dosyalar"
diff --git a/gschem/po/zh_CN.po b/gschem/po/zh_CN.po
index b5c5a1a..9ef4f27 100644
--- a/gschem/po/zh_CN.po
+++ b/gschem/po/zh_CN.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2010-11-07 13:37+0000\n"
+"POT-Creation-Date: 2011-01-16 00:11-0500\n"
"PO-Revision-Date: 2010-02-11 03:18+0000\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -22,17 +22,17 @@ msgstr ""
msgid "Zoom too small! Cannot zoom further.\n"
msgstr ""
-#: gschem/src/g_funcs.c:339 gschem/src/i_callbacks.c:68
+#: gschem/src/g_funcs.c:347 gschem/src/i_callbacks.c:68
#, c-format
msgid "Could not fork\n"
msgstr ""
-#: gschem/src/g_funcs.c:355 gschem/src/i_callbacks.c:78
+#: gschem/src/g_funcs.c:363 gschem/src/i_callbacks.c:78
#, c-format
msgid "Could not invoke %s\n"
msgstr ""
-#: gschem/src/g_funcs.c:361 gschem/src/i_callbacks.c:82
+#: gschem/src/g_funcs.c:369 gschem/src/i_callbacks.c:82
msgid "Documentation commands not supported under MinGW.\n"
msgstr ""
@@ -121,39 +121,39 @@ msgstr ""
msgid "Invalid number of steps [%d] scrollpan-steps\n"
msgstr ""
-#: gschem/src/gschem.c:184
+#: gschem/src/gschem.c:188
#, c-format
msgid "gEDA/gschem version %s%s.%s\n"
msgstr ""
-#: gschem/src/gschem.c:187
+#: gschem/src/gschem.c:191
msgid ""
"gEDA/gschem comes with ABSOLUTELY NO WARRANTY; see COPYING for more "
"details.\n"
msgstr ""
-#: gschem/src/gschem.c:189
+#: gschem/src/gschem.c:193
msgid ""
"This is free software, and you are welcome to redistribute it under certain\n"
msgstr ""
-#: gschem/src/gschem.c:191
+#: gschem/src/gschem.c:195
msgid ""
"conditions; please see the COPYING file for more details.\n"
"\n"
msgstr ""
-#: gschem/src/gschem.c:194
+#: gschem/src/gschem.c:198
#, c-format
msgid "This is the MINGW32 port.\n"
msgstr ""
-#: gschem/src/gschem.c:198
+#: gschem/src/gschem.c:202
#, c-format
msgid "Current locale settings: %s\n"
msgstr ""
-#: gschem/src/gschem.c:213
+#: gschem/src/gschem.c:218
msgid ""
"You must set the GEDADATA environment variable!\n"
"\n"
@@ -161,31 +161,21 @@ msgid ""
"environment variable to point to the correct location.\n"
msgstr ""
-#: gschem/src/gschem.c:248
+#: gschem/src/gschem.c:256
#, c-format
msgid "Couldn't find init scm file [%s]\n"
msgstr ""
-#: gschem/src/gschem.c:252
+#: gschem/src/gschem.c:260
#, c-format
msgid "Read init scm file [%s]\n"
msgstr ""
-#: gschem/src/gschem.c:256
+#: gschem/src/gschem.c:264
#, c-format
msgid "Failed to read init scm file [%s]\n"
msgstr ""
-#: gschem/src/gschem.c:317
-#, c-format
-msgid "Scheme directory NOT set!\n"
-msgstr ""
-
-#: gschem/src/gschem.c:324 gschem/src/x_script.c:66
-#, c-format
-msgid "Executing guile script [%s]\n"
-msgstr ""
-
#: gschem/src/gschem_cairo.c:310
#, c-format
msgid "Unknown end for line (%d)\n"
@@ -209,11 +199,11 @@ msgstr ""
msgid "Text Mode"
msgstr ""
-#: gschem/src/i_basic.c:84 gschem/lib/system-gschemrc.scm:1409
+#: gschem/src/i_basic.c:84 gschem/lib/system-gschemrc.scm:1411
msgid "Copy Mode"
msgstr "��模�"
-#: gschem/src/i_basic.c:87 gschem/lib/system-gschemrc.scm:1411
+#: gschem/src/i_basic.c:87 gschem/lib/system-gschemrc.scm:1413
msgid "Move Mode"
msgstr "移�模�"
@@ -221,7 +211,7 @@ msgstr "移�模�"
msgid "Rotate Mode"
msgstr ""
-#: gschem/src/i_basic.c:91 gschem/lib/system-gschemrc.scm:1413
+#: gschem/src/i_basic.c:91 gschem/lib/system-gschemrc.scm:1415
msgid "Mirror Mode"
msgstr "é??å??模å¼?"
@@ -274,22 +264,22 @@ msgstr ""
msgid "Pin Mode"
msgstr ""
-#: gschem/src/i_basic.c:135 gschem/src/i_callbacks.c:544
-#: gschem/src/i_callbacks.c:568
+#: gschem/src/i_basic.c:135 gschem/src/i_callbacks.c:576
+#: gschem/src/i_callbacks.c:600
msgid "Copy"
msgstr "��"
-#: gschem/src/i_basic.c:137 gschem/src/i_callbacks.c:634
-#: gschem/src/i_callbacks.c:658
+#: gschem/src/i_basic.c:137 gschem/src/i_callbacks.c:666
+#: gschem/src/i_callbacks.c:690
msgid "Move"
msgstr ""
-#: gschem/src/i_basic.c:139 gschem/src/i_callbacks.c:589
-#: gschem/src/i_callbacks.c:613
+#: gschem/src/i_basic.c:139 gschem/src/i_callbacks.c:621
+#: gschem/src/i_callbacks.c:645
msgid "Multiple Copy"
msgstr ""
-#: gschem/src/i_basic.c:142 gschem/lib/system-gschemrc.scm:1410
+#: gschem/src/i_basic.c:142 gschem/lib/system-gschemrc.scm:1412
msgid "Multiple Copy Mode"
msgstr "å¤?é??å¤?å?¶æ¨¡å¼?"
@@ -309,7 +299,7 @@ msgstr ""
msgid "Action"
msgstr ""
-#: gschem/src/i_basic.c:260 gschem/src/x_dialog.c:2312
+#: gschem/src/i_basic.c:260 gschem/src/x_dialog.c:2316
#: gschem/src/x_window.c:491
msgid "Stroke"
msgstr ""
@@ -340,7 +330,7 @@ msgstr ""
msgid "Documentation for [%s,%s,%s,%s]\n"
msgstr ""
-#: gschem/src/i_callbacks.c:123 gschem/src/i_callbacks.c:1699
+#: gschem/src/i_callbacks.c:123 gschem/src/i_callbacks.c:1706
#, c-format
msgid "New page created [%s]\n"
msgstr ""
@@ -362,327 +352,323 @@ msgstr ""
msgid "Closing Window\n"
msgstr ""
-#: gschem/src/i_callbacks.c:549 gschem/src/i_callbacks.c:594
-#: gschem/src/i_callbacks.c:639
+#: gschem/src/i_callbacks.c:581 gschem/src/i_callbacks.c:626
+#: gschem/src/i_callbacks.c:671
msgid "Select objs first"
msgstr ""
-#: gschem/src/i_callbacks.c:678 gschem/src/x_multiattrib.c:1491
+#: gschem/src/i_callbacks.c:710 gschem/src/x_multiattrib.c:1503
msgid "Delete"
msgstr "å? é?¤"
-#: gschem/src/i_callbacks.c:703
+#: gschem/src/i_callbacks.c:735
msgid "Edit"
msgstr "ç¼?è¾?"
-#: gschem/src/i_callbacks.c:718
+#: gschem/src/i_callbacks.c:750
msgid "Edit pin type"
msgstr ""
-#: gschem/src/i_callbacks.c:737
+#: gschem/src/i_callbacks.c:769
msgid "Edit Text"
msgstr ""
-#: gschem/src/i_callbacks.c:760
+#: gschem/src/i_callbacks.c:792
msgid "Slot"
msgstr ""
-#: gschem/src/i_callbacks.c:777
+#: gschem/src/i_callbacks.c:809
msgid "Color"
msgstr ""
-#: gschem/src/i_callbacks.c:814 gschem/src/i_callbacks.c:859
+#: gschem/src/i_callbacks.c:846 gschem/src/i_callbacks.c:891
msgid "Rotate"
msgstr ""
-#: gschem/src/i_callbacks.c:882 gschem/src/i_callbacks.c:907
+#: gschem/src/i_callbacks.c:913 gschem/src/i_callbacks.c:938
msgid "Mirror"
msgstr ""
-#: gschem/src/i_callbacks.c:928 gschem/src/x_dialog.c:2315
-#: gschem/lib/system-gschemrc.scm:1422
+#: gschem/src/i_callbacks.c:959 gschem/src/x_dialog.c:2319
+#: gschem/lib/system-gschemrc.scm:1424
msgid "Lock"
msgstr "é??å®?"
-#: gschem/src/i_callbacks.c:946 gschem/lib/system-gschemrc.scm:1423
+#: gschem/src/i_callbacks.c:977 gschem/lib/system-gschemrc.scm:1425
msgid "Unlock"
msgstr "解é??"
-#: gschem/src/i_callbacks.c:964 gschem/src/x_dialog.c:1734
+#: gschem/src/i_callbacks.c:995 gschem/src/x_dialog.c:1737
msgid "Translate"
msgstr ""
-#: gschem/src/i_callbacks.c:967
+#: gschem/src/i_callbacks.c:998
msgid "WARNING: Do not translate with snap off!\n"
msgstr ""
-#: gschem/src/i_callbacks.c:968
+#: gschem/src/i_callbacks.c:999
msgid "WARNING: Turning snap on and continuing with translate.\n"
msgstr ""
-#: gschem/src/i_callbacks.c:975
+#: gschem/src/i_callbacks.c:1006
msgid "WARNING: Snap grid size is not equal to 100!\n"
msgstr ""
-#: gschem/src/i_callbacks.c:977
+#: gschem/src/i_callbacks.c:1008
msgid ""
"WARNING: If you are translating a symbol to the origin, the snap grid size "
"should be set to 100\n"
msgstr ""
-#: gschem/src/i_callbacks.c:1008
+#: gschem/src/i_callbacks.c:1039
msgid "Embed"
msgstr ""
-#: gschem/src/i_callbacks.c:1047
+#: gschem/src/i_callbacks.c:1078
msgid "Unembed"
msgstr ""
-#: gschem/src/i_callbacks.c:1089
+#: gschem/src/i_callbacks.c:1120
msgid "Update"
msgstr ""
-#: gschem/src/i_callbacks.c:1136
+#: gschem/src/i_callbacks.c:1167
msgid "ShowHidden"
msgstr ""
-#: gschem/src/i_callbacks.c:1160
-msgid "MakeVisible"
-msgstr ""
-
-#: gschem/src/i_callbacks.c:1466 gschem/src/i_callbacks.c:1538
+#: gschem/src/i_callbacks.c:1473 gschem/src/i_callbacks.c:1545
msgid "Pan"
msgstr ""
-#: gschem/src/i_callbacks.c:1743
+#: gschem/src/i_callbacks.c:1750
msgid "Really revert page?"
msgstr ""
-#: gschem/src/i_callbacks.c:1813
+#: gschem/src/i_callbacks.c:1820
msgid "Copy to clipboard"
msgstr ""
-#: gschem/src/i_callbacks.c:1831
+#: gschem/src/i_callbacks.c:1838
msgid "Cut to clipboard"
msgstr ""
-#: gschem/src/i_callbacks.c:1849
+#: gschem/src/i_callbacks.c:1856
msgid "Paste from clipboard"
msgstr ""
-#: gschem/src/i_callbacks.c:1861 gschem/src/i_callbacks.c:2100
-#: gschem/src/i_callbacks.c:2122 gschem/src/i_callbacks.c:2144
-#: gschem/src/i_callbacks.c:2166 gschem/src/i_callbacks.c:2188
+#: gschem/src/i_callbacks.c:1868 gschem/src/i_callbacks.c:2107
+#: gschem/src/i_callbacks.c:2129 gschem/src/i_callbacks.c:2151
+#: gschem/src/i_callbacks.c:2173 gschem/src/i_callbacks.c:2195
msgid "Empty buffer"
msgstr ""
-#: gschem/src/i_callbacks.c:1906
+#: gschem/src/i_callbacks.c:1913
msgid "Copy 1"
msgstr ""
-#: gschem/src/i_callbacks.c:1925
+#: gschem/src/i_callbacks.c:1932
msgid "Copy 2"
msgstr ""
-#: gschem/src/i_callbacks.c:1944
+#: gschem/src/i_callbacks.c:1951
msgid "Copy 3"
msgstr ""
-#: gschem/src/i_callbacks.c:1963
+#: gschem/src/i_callbacks.c:1970
msgid "Copy 4"
msgstr ""
-#: gschem/src/i_callbacks.c:1982
+#: gschem/src/i_callbacks.c:1989
msgid "Copy 5"
msgstr ""
-#: gschem/src/i_callbacks.c:2001
+#: gschem/src/i_callbacks.c:2008
msgid "Cut 1"
msgstr ""
-#: gschem/src/i_callbacks.c:2020
+#: gschem/src/i_callbacks.c:2027
msgid "Cut 2"
msgstr ""
-#: gschem/src/i_callbacks.c:2039
+#: gschem/src/i_callbacks.c:2046
msgid "Cut 3"
msgstr ""
-#: gschem/src/i_callbacks.c:2058
+#: gschem/src/i_callbacks.c:2065
msgid "Cut 4"
msgstr ""
-#: gschem/src/i_callbacks.c:2077
+#: gschem/src/i_callbacks.c:2084
msgid "Cut 5"
msgstr ""
-#: gschem/src/i_callbacks.c:2093
+#: gschem/src/i_callbacks.c:2100
msgid "Paste 1"
msgstr ""
-#: gschem/src/i_callbacks.c:2115
+#: gschem/src/i_callbacks.c:2122
msgid "Paste 2"
msgstr ""
-#: gschem/src/i_callbacks.c:2137
+#: gschem/src/i_callbacks.c:2144
msgid "Paste 3"
msgstr ""
-#: gschem/src/i_callbacks.c:2159
+#: gschem/src/i_callbacks.c:2166
msgid "Paste 4"
msgstr ""
-#: gschem/src/i_callbacks.c:2181
+#: gschem/src/i_callbacks.c:2188
msgid "Paste 5"
msgstr ""
-#: gschem/src/i_callbacks.c:2318 gschem/src/x_window.c:355
+#: gschem/src/i_callbacks.c:2325 gschem/src/x_window.c:355
msgid "Component"
msgstr ""
-#: gschem/src/i_callbacks.c:2354 gschem/src/i_callbacks.c:2373
-#: gschem/src/x_dialog.c:2285
+#: gschem/src/i_callbacks.c:2361 gschem/src/i_callbacks.c:2380
+#: gschem/src/x_dialog.c:2289
msgid "Attribute"
msgstr ""
-#: gschem/src/i_callbacks.c:2395 gschem/src/i_callbacks.c:2422
-#: gschem/src/x_dialog.c:2282
+#: gschem/src/i_callbacks.c:2402 gschem/src/i_callbacks.c:2429
+#: gschem/src/x_dialog.c:2286
msgid "Net"
msgstr ""
-#: gschem/src/i_callbacks.c:2466 gschem/src/i_callbacks.c:2493
-#: gschem/src/x_dialog.c:2300 gschem/src/x_window.c:375
+#: gschem/src/i_callbacks.c:2473 gschem/src/i_callbacks.c:2500
+#: gschem/src/x_dialog.c:2304 gschem/src/x_window.c:375
msgid "Bus"
msgstr "�线"
-#: gschem/src/i_callbacks.c:2574 gschem/src/i_callbacks.c:2597
+#: gschem/src/i_callbacks.c:2581 gschem/src/i_callbacks.c:2604
msgid "Line"
msgstr ""
-#: gschem/src/i_callbacks.c:2619 gschem/src/i_callbacks.c:2642
+#: gschem/src/i_callbacks.c:2626 gschem/src/i_callbacks.c:2649
msgid "Box"
msgstr ""
-#: gschem/src/i_callbacks.c:2698 gschem/src/i_callbacks.c:2722
+#: gschem/src/i_callbacks.c:2705 gschem/src/i_callbacks.c:2729
msgid "Circle"
msgstr "å??"
-#: gschem/src/i_callbacks.c:2744 gschem/src/i_callbacks.c:2767
+#: gschem/src/i_callbacks.c:2751 gschem/src/i_callbacks.c:2774
msgid "Arc"
msgstr "弧线"
-#: gschem/src/i_callbacks.c:2789 gschem/src/i_callbacks.c:2812
-#: gschem/src/x_dialog.c:2273
+#: gschem/src/i_callbacks.c:2796 gschem/src/i_callbacks.c:2819
+#: gschem/src/x_dialog.c:2277
msgid "Pin"
msgstr ""
-#: gschem/src/i_callbacks.c:2871
+#: gschem/src/i_callbacks.c:2878
#, c-format
msgid "Searching for source [%s]\n"
msgstr ""
-#: gschem/src/i_callbacks.c:2895
+#: gschem/src/i_callbacks.c:2902
#, c-format
msgid "Cannot find source [%s]\n"
msgstr ""
-#: gschem/src/i_callbacks.c:2964
+#: gschem/src/i_callbacks.c:2965
#, c-format
msgid "Searching for symbol [%s]\n"
msgstr ""
-#: gschem/src/i_callbacks.c:2970
+#: gschem/src/i_callbacks.c:2971
msgid "Symbol is not a real file. Symbol cannot be loaded.\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3001
+#: gschem/src/i_callbacks.c:3002
msgid "Cannot find any schematics above the current one!\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3055
+#: gschem/src/i_callbacks.c:3056
msgid ""
"This command retrieves the component documentation from the web, but there "
"is no component selected"
msgstr ""
-#: gschem/src/i_callbacks.c:3083
+#: gschem/src/i_callbacks.c:3084
msgid "Attach"
msgstr "è¿?æ?¥"
-#: gschem/src/i_callbacks.c:3130
+#: gschem/src/i_callbacks.c:3131
msgid "Detach"
msgstr "�离"
-#: gschem/src/i_callbacks.c:3165
+#: gschem/src/i_callbacks.c:3166
msgid "ShowN"
msgstr ""
-#: gschem/src/i_callbacks.c:3201
+#: gschem/src/i_callbacks.c:3202
msgid "ShowV"
msgstr ""
-#: gschem/src/i_callbacks.c:3237
+#: gschem/src/i_callbacks.c:3238
msgid "ShowB"
msgstr ""
-#: gschem/src/i_callbacks.c:3274
+#: gschem/src/i_callbacks.c:3275
msgid "VisToggle"
msgstr ""
-#: gschem/src/i_callbacks.c:3304
+#: gschem/src/i_callbacks.c:3305
#, c-format
msgid "Sorry but this is a non-functioning menu option\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3394
+#: gschem/src/i_callbacks.c:3395
msgid "Action feedback mode set to OUTLINE\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3397
+#: gschem/src/i_callbacks.c:3398
msgid "Action feedback mode set to BOUNDINGBOX\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3422
+#: gschem/src/i_callbacks.c:3423
msgid "Grid OFF\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3423
+#: gschem/src/i_callbacks.c:3424
msgid "Dot grid selected\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3424
+#: gschem/src/i_callbacks.c:3425
msgid "Mesh grid selected\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3445
+#: gschem/src/i_callbacks.c:3446
msgid "Snap OFF (CAUTION!)\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3448
+#: gschem/src/i_callbacks.c:3449
msgid "Snap ON\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3451
+#: gschem/src/i_callbacks.c:3452
msgid "Snap back to the grid (CAUTION!)\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3477
+#: gschem/src/i_callbacks.c:3478
msgid "Rubber band OFF \n"
msgstr ""
-#: gschem/src/i_callbacks.c:3480
+#: gschem/src/i_callbacks.c:3481
msgid "Rubber band ON\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3495
+#: gschem/src/i_callbacks.c:3496
msgid "magnetic net mode: ON\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3498
+#: gschem/src/i_callbacks.c:3499
msgid "magnetic net mode: OFF\n"
msgstr ""
-#: gschem/src/o_box.c:153
+#: gschem/src/o_box.c:149
#, c-format
msgid "Unknown type for box (fill)!\n"
msgstr ""
@@ -702,17 +688,17 @@ msgstr ""
msgid "Got an invalid buffer_number [o_buffer_paste_start]\n"
msgstr ""
-#: gschem/src/o_bus.c:118
+#: gschem/src/o_bus.c:117
#, c-format
msgid "Got an invalid which one in o_bus_draw_stretch\n"
msgstr ""
-#: gschem/src/o_circle.c:134
+#: gschem/src/o_circle.c:130
#, c-format
msgid "Unknown type for circle (fill)!\n"
msgstr ""
-#: gschem/src/o_complex.c:243 gschem/src/o_complex.c:247
+#: gschem/src/o_complex.c:237 gschem/src/o_complex.c:241
#, c-format
msgid "Translating schematic [%d %d]\n"
msgstr ""
@@ -730,35 +716,35 @@ msgstr ""
msgid "Object already unlocked\n"
msgstr ""
-#: gschem/src/o_misc.c:413
+#: gschem/src/o_misc.c:409
msgid "Hidden text is now visible\n"
msgstr ""
-#: gschem/src/o_misc.c:415
+#: gschem/src/o_misc.c:411
msgid "Hidden text is now invisible\n"
msgstr ""
-#: gschem/src/o_misc.c:668
+#: gschem/src/o_misc.c:636
#, c-format
msgid "Could not find symbol [%s] in library. Update failed.\n"
msgstr ""
-#: gschem/src/o_misc.c:783
+#: gschem/src/o_misc.c:751
#, c-format
msgid "o_autosave_backups: Can't get the real filename of %s."
msgstr ""
-#: gschem/src/o_misc.c:827
+#: gschem/src/o_misc.c:795
#, c-format
msgid "Could NOT set previous backup file [%s] read-write\n"
msgstr ""
-#: gschem/src/o_misc.c:845
+#: gschem/src/o_misc.c:815
#, c-format
msgid "Could NOT set backup file [%s] readonly\n"
msgstr ""
-#: gschem/src/o_misc.c:850
+#: gschem/src/o_misc.c:820
#, c-format
msgid "Could NOT save backup file [%s]\n"
msgstr ""
@@ -778,36 +764,36 @@ msgstr ""
msgid "Got a non line object in o_move_check_endpoint\n"
msgstr ""
-#: gschem/src/o_net.c:159
+#: gschem/src/o_net.c:158
#, c-format
msgid "Got an invalid which one in o_net_draw_stretch\n"
msgstr ""
-#: gschem/src/o_net.c:538
+#: gschem/src/o_net.c:537
msgid "Warning: Starting net at off grid coordinate\n"
msgstr ""
-#: gschem/src/o_net.c:600
+#: gschem/src/o_net.c:599
msgid "Warning: Ending net at off grid coordinate\n"
msgstr ""
-#: gschem/src/o_net.c:932 gschem/src/o_net.c:969 gschem/src/o_net.c:1040
-#: gschem/src/o_net.c:1076
+#: gschem/src/o_net.c:931 gschem/src/o_net.c:968 gschem/src/o_net.c:1039
+#: gschem/src/o_net.c:1075
#, c-format
msgid "Tried to add more than two bus rippers. Internal gschem error.\n"
msgstr ""
-#: gschem/src/o_net.c:1144
+#: gschem/src/o_net.c:1143
#, c-format
msgid "Bus ripper symbol [%s] was not found in any component library\n"
msgstr ""
-#: gschem/src/o_path.c:352
+#: gschem/src/o_path.c:348
#, c-format
msgid "Unknown type for path (fill)!\n"
msgstr ""
-#: gschem/src/o_picture.c:163 gschem/src/o_picture.c:539
+#: gschem/src/o_picture.c:163 gschem/src/o_picture.c:537
#, c-format
msgid "Failed to load picture: %s"
msgstr ""
@@ -816,7 +802,7 @@ msgstr ""
msgid "Picture"
msgstr ""
-#: gschem/src/o_picture.c:447 gschem/src/x_attribedit.c:141
+#: gschem/src/o_picture.c:445 gschem/src/x_attribedit.c:141
#, c-format
msgid "ERROR: NULL object!\n"
msgstr ""
@@ -837,23 +823,45 @@ msgstr ""
msgid "New slot number out of range\n"
msgstr ""
-#: gschem/src/o_undo.c:304
+#: gschem/src/o_undo.c:303
msgid "Undo/Redo disabled in rc file\n"
msgstr ""
-#: gschem/src/parsecmd.c:47
+#: gschem/src/parsecmd.c:81
#, c-format
msgid ""
-"Usage: %s [OPTIONS] schematic_filename1 ... schematic_filenameN\n"
-" -q Quiet mode\n"
-" -v Verbose mode on\n"
-" -r filename Rc filename\n"
-" -s filename Script (guile) filename\n"
-" -o filename Output filename (for printing)\n"
-" -p Automatically place the window\n"
-" -t Print stroke information\n"
-" -h Help; this message\n"
+"Usage: %s [OPTION ...] [--] [FILE ...]\n"
+"\n"
+"Interactively edit gEDA schematics or symbols. If one or more FILEs\n"
+"are specified, open them for editing; otherwise, create a new, empty\n"
+"schematic.\n"
"\n"
+"Options:\n"
+" -q, --quiet Quiet mode.\n"
+" -v, --verbose Verbose mode.\n"
+" -r, --config-file=FILE Additional configuration file to load.\n"
+" -L DIR Add DIR to Scheme search path.\n"
+" -c EXPR Scheme expression to run at startup.\n"
+" -s FILE Scheme script to run at startup.\n"
+" -o, --output=FILE Output filename (for printing).\n"
+" -p Automatically place the window.\n"
+" -V, --version Show version information.\n"
+" -h, --help Help; this message.\n"
+" -- Treat all remaining arguments as filenames.\n"
+"\n"
+"Report bugs to <geda-bug@xxxxxxxx>\n"
+"gEDA/gaf homepage: <http://gpleda.org>\n"
+msgstr ""
+
+#: gschem/src/parsecmd.c:115
+#, c-format
+msgid ""
+"gEDA %s (g%.7s)\n"
+"Copyright (C) 1998-2011 gEDA developers\n"
+"This is free software, and you are welcome to redistribute it under\n"
+"certain conditions. For details, see the file `COPYING', which is\n"
+"included in the gEDA distribution.\n"
+"There is NO WARRANTY, to the extent permitted by law.\n"
msgstr ""
#: gschem/src/x_attribedit.c:127
@@ -865,56 +873,56 @@ msgstr ""
msgid "Single Attribute Editor"
msgstr ""
-#: gschem/src/x_attribedit.c:358
+#: gschem/src/x_attribedit.c:359
msgid "<b>Edit Attribute</b>"
msgstr ""
-#: gschem/src/x_attribedit.c:360
+#: gschem/src/x_attribedit.c:361
msgid "<b>Add Attribute</b>"
msgstr ""
-#: gschem/src/x_attribedit.c:376 gschem/src/x_multiattrib.c:1916
+#: gschem/src/x_attribedit.c:377 gschem/src/x_multiattrib.c:1927
msgid "Name:"
msgstr ""
-#: gschem/src/x_attribedit.c:393 gschem/src/x_multiattrib.c:1935
+#: gschem/src/x_attribedit.c:394 gschem/src/x_multiattrib.c:1946
msgid "Value:"
msgstr ""
-#: gschem/src/x_attribedit.c:409 gschem/src/x_multiattrib.c:1978
+#: gschem/src/x_attribedit.c:410 gschem/src/x_multiattrib.c:1989
msgid "Visible"
msgstr ""
-#: gschem/src/x_attribedit.c:429
+#: gschem/src/x_attribedit.c:430
msgid "Show Value Only"
msgstr ""
-#: gschem/src/x_attribedit.c:431
+#: gschem/src/x_attribedit.c:432
msgid "Show Name Only"
msgstr ""
-#: gschem/src/x_attribedit.c:433 gschem/src/x_multiattrib.c:1454
+#: gschem/src/x_attribedit.c:434 gschem/src/x_multiattrib.c:1466
msgid "Show Name & Value"
msgstr ""
-#: gschem/src/x_attribedit.c:440
+#: gschem/src/x_attribedit.c:441
msgid "<b>Attach Options</b>"
msgstr ""
-#: gschem/src/x_attribedit.c:455
+#: gschem/src/x_attribedit.c:456
msgid "All"
msgstr ""
-#: gschem/src/x_attribedit.c:463 gschem/src/x_compselect.c:896
-#: gschem/src/x_compselect.c:1010
+#: gschem/src/x_attribedit.c:464 gschem/src/x_compselect.c:904
+#: gschem/src/x_compselect.c:1018
msgid "Components"
msgstr ""
-#: gschem/src/x_attribedit.c:471 gschem/src/x_window.c:365
+#: gschem/src/x_attribedit.c:472 gschem/src/x_window.c:365
msgid "Nets"
msgstr ""
-#: gschem/src/x_attribedit.c:479
+#: gschem/src/x_attribedit.c:480
msgid "Replace existing attributes"
msgstr ""
@@ -930,91 +938,91 @@ msgid ""
"duplicate slot may cause problems: [symbolname=%s, number=%d, slot=%d]\n"
msgstr ""
-#: gschem/src/x_autonumber.c:673
+#: gschem/src/x_autonumber.c:675
msgid "No searchstring given in autonumber text.\n"
msgstr ""
-#: gschem/src/x_autonumber.c:725
+#: gschem/src/x_autonumber.c:727
msgid "No '*' or '?' given at the end of the autonumber text.\n"
msgstr ""
-#: gschem/src/x_autonumber.c:860
+#: gschem/src/x_autonumber.c:862
msgid "Diagonal"
msgstr ""
-#: gschem/src/x_autonumber.c:861
+#: gschem/src/x_autonumber.c:863
msgid "Top to bottom"
msgstr ""
-#: gschem/src/x_autonumber.c:861
+#: gschem/src/x_autonumber.c:863
msgid "Bottom to top"
msgstr ""
-#: gschem/src/x_autonumber.c:862
+#: gschem/src/x_autonumber.c:864
msgid "Left to right"
msgstr ""
-#: gschem/src/x_autonumber.c:862
+#: gschem/src/x_autonumber.c:864
msgid "Right to left"
msgstr ""
-#: gschem/src/x_autonumber.c:863
+#: gschem/src/x_autonumber.c:865
msgid "File order"
msgstr ""
-#: gschem/src/x_autonumber.c:1199
+#: gschem/src/x_autonumber.c:1201
msgid "Autonumber text"
msgstr ""
-#: gschem/src/x_autonumber.c:1223
+#: gschem/src/x_autonumber.c:1225
msgid "<b>Scope</b>"
msgstr ""
-#: gschem/src/x_autonumber.c:1245
+#: gschem/src/x_autonumber.c:1247
msgid "Search for:"
msgstr ""
-#: gschem/src/x_autonumber.c:1259
+#: gschem/src/x_autonumber.c:1261
msgid "Autonumber text in:"
msgstr ""
-#: gschem/src/x_autonumber.c:1266
+#: gschem/src/x_autonumber.c:1268
msgid "Skip numbers found in:"
msgstr ""
-#: gschem/src/x_autonumber.c:1278 gschem/src/x_autonumber.c:1287
+#: gschem/src/x_autonumber.c:1280 gschem/src/x_autonumber.c:1289
msgid "Selected objects"
msgstr ""
-#: gschem/src/x_autonumber.c:1279 gschem/src/x_autonumber.c:1288
+#: gschem/src/x_autonumber.c:1281 gschem/src/x_autonumber.c:1290
msgid "Current page"
msgstr ""
-#: gschem/src/x_autonumber.c:1280 gschem/src/x_autonumber.c:1289
+#: gschem/src/x_autonumber.c:1282 gschem/src/x_autonumber.c:1291
msgid "Whole hierarchy"
msgstr ""
-#: gschem/src/x_autonumber.c:1291
+#: gschem/src/x_autonumber.c:1293
msgid "Overwrite existing numbers"
msgstr ""
-#: gschem/src/x_autonumber.c:1296
+#: gschem/src/x_autonumber.c:1298
msgid "<b>Options</b>"
msgstr ""
-#: gschem/src/x_autonumber.c:1318
+#: gschem/src/x_autonumber.c:1320
msgid "Starting number:"
msgstr ""
-#: gschem/src/x_autonumber.c:1325
+#: gschem/src/x_autonumber.c:1327
msgid "Sort order:"
msgstr ""
-#: gschem/src/x_autonumber.c:1346
+#: gschem/src/x_autonumber.c:1348
msgid "Remove numbers"
msgstr ""
-#: gschem/src/x_autonumber.c:1350
+#: gschem/src/x_autonumber.c:1352
msgid "Automatic slotting"
msgstr ""
@@ -1051,48 +1059,48 @@ msgstr ""
msgid "Tried to get an invalid outline color: %d\n"
msgstr ""
-#: gschem/src/x_compselect.c:1040
+#: gschem/src/x_compselect.c:1048
msgid "Filter:"
msgstr ""
-#: gschem/src/x_compselect.c:1143 gschem/src/x_dialog.c:3663
-#: gschem/src/x_multiattrib.c:1782
+#: gschem/src/x_compselect.c:1151 gschem/src/x_dialog.c:3667
+#: gschem/src/x_multiattrib.c:1793
msgid "Name"
msgstr ""
-#: gschem/src/x_compselect.c:1152 gschem/src/x_multiattrib.c:1806
+#: gschem/src/x_compselect.c:1160 gschem/src/x_multiattrib.c:1817
msgid "Value"
msgstr ""
-#: gschem/src/x_compselect.c:1191
+#: gschem/src/x_compselect.c:1199
msgid "Default behavior - reference component"
msgstr ""
-#: gschem/src/x_compselect.c:1194
+#: gschem/src/x_compselect.c:1202
msgid "Embed component in schematic"
msgstr ""
-#: gschem/src/x_compselect.c:1197
+#: gschem/src/x_compselect.c:1205
msgid "Include component as individual objects"
msgstr ""
-#: gschem/src/x_compselect.c:1354
+#: gschem/src/x_compselect.c:1362
msgid "Select Component..."
msgstr ""
-#: gschem/src/x_compselect.c:1377
+#: gschem/src/x_compselect.c:1385
msgid "In Use"
msgstr ""
-#: gschem/src/x_compselect.c:1381
+#: gschem/src/x_compselect.c:1389
msgid "Libraries"
msgstr ""
-#: gschem/src/x_compselect.c:1390 gschem/src/x_fileselect.c:122
+#: gschem/src/x_compselect.c:1398 gschem/src/x_fileselect.c:122
msgid "Preview"
msgstr ""
-#: gschem/src/x_compselect.c:1418
+#: gschem/src/x_compselect.c:1426
msgid "Attributes"
msgstr "å±?æ?§"
@@ -1147,336 +1155,336 @@ msgstr ""
msgid "Edit Text Properties"
msgstr ""
-#: gschem/src/x_dialog.c:471
+#: gschem/src/x_dialog.c:472
msgid "<b>Text Content</b>"
msgstr ""
-#: gschem/src/x_dialog.c:507
+#: gschem/src/x_dialog.c:508
msgid "<b>Text Properties</b>"
msgstr ""
-#: gschem/src/x_dialog.c:522
+#: gschem/src/x_dialog.c:523
msgid "Color:"
msgstr ""
-#: gschem/src/x_dialog.c:529
+#: gschem/src/x_dialog.c:530
msgid "Size:"
msgstr ""
-#: gschem/src/x_dialog.c:538
+#: gschem/src/x_dialog.c:539
msgid "Alignment:"
msgstr ""
-#: gschem/src/x_dialog.c:587
+#: gschem/src/x_dialog.c:588
msgid "Solid"
msgstr ""
-#: gschem/src/x_dialog.c:588
+#: gschem/src/x_dialog.c:589
msgid "Dotted"
msgstr ""
-#: gschem/src/x_dialog.c:589
+#: gschem/src/x_dialog.c:590
msgid "Dashed"
msgstr ""
-#: gschem/src/x_dialog.c:590
+#: gschem/src/x_dialog.c:591
msgid "Center"
msgstr ""
-#: gschem/src/x_dialog.c:591
+#: gschem/src/x_dialog.c:592
msgid "Phantom"
msgstr ""
-#: gschem/src/x_dialog.c:592 gschem/src/x_dialog.c:689
-#: gschem/src/x_dialog.c:698 gschem/src/x_dialog.c:707
-#: gschem/src/x_dialog.c:808 gschem/src/x_dialog.c:810
-#: gschem/src/x_dialog.c:812 gschem/src/x_dialog.c:1038
-#: gschem/src/x_dialog.c:1141 gschem/src/x_dialog.c:1150
-#: gschem/src/x_dialog.c:1159 gschem/src/x_dialog.c:1168
-#: gschem/src/x_dialog.c:1177 gschem/src/x_dialog.c:1290
-#: gschem/src/x_dialog.c:1292 gschem/src/x_dialog.c:1294
-#: gschem/src/x_dialog.c:1296 gschem/src/x_dialog.c:1298
+#: gschem/src/x_dialog.c:593 gschem/src/x_dialog.c:690
+#: gschem/src/x_dialog.c:699 gschem/src/x_dialog.c:708
+#: gschem/src/x_dialog.c:809 gschem/src/x_dialog.c:811
+#: gschem/src/x_dialog.c:813 gschem/src/x_dialog.c:1039
+#: gschem/src/x_dialog.c:1142 gschem/src/x_dialog.c:1151
+#: gschem/src/x_dialog.c:1160 gschem/src/x_dialog.c:1169
+#: gschem/src/x_dialog.c:1178 gschem/src/x_dialog.c:1291
+#: gschem/src/x_dialog.c:1293 gschem/src/x_dialog.c:1295
+#: gschem/src/x_dialog.c:1297 gschem/src/x_dialog.c:1299
msgid "*unchanged*"
msgstr ""
-#: gschem/src/x_dialog.c:916
+#: gschem/src/x_dialog.c:917
msgid "Edit Line Width & Type"
msgstr ""
-#: gschem/src/x_dialog.c:955 gschem/src/x_print.c:307
+#: gschem/src/x_dialog.c:956 gschem/src/x_print.c:307
msgid "Type:"
msgstr ""
-#: gschem/src/x_dialog.c:959
+#: gschem/src/x_dialog.c:960
msgid "Width:"
msgstr ""
-#: gschem/src/x_dialog.c:963
+#: gschem/src/x_dialog.c:964
msgid "Dash Length:"
msgstr ""
-#: gschem/src/x_dialog.c:967
+#: gschem/src/x_dialog.c:968
msgid "Dash Space:"
msgstr ""
-#: gschem/src/x_dialog.c:1034
+#: gschem/src/x_dialog.c:1035
msgid "Hollow"
msgstr ""
-#: gschem/src/x_dialog.c:1035
+#: gschem/src/x_dialog.c:1036
msgid "Filled"
msgstr ""
-#: gschem/src/x_dialog.c:1036
+#: gschem/src/x_dialog.c:1037
msgid "Mesh"
msgstr ""
-#: gschem/src/x_dialog.c:1037
+#: gschem/src/x_dialog.c:1038
msgid "Hatch"
msgstr ""
-#: gschem/src/x_dialog.c:1406
+#: gschem/src/x_dialog.c:1407
msgid "Edit Fill Type"
msgstr ""
-#: gschem/src/x_dialog.c:1444
+#: gschem/src/x_dialog.c:1446
msgid "Fill Type:"
msgstr ""
-#: gschem/src/x_dialog.c:1448
+#: gschem/src/x_dialog.c:1450
msgid "Line Width:"
msgstr ""
-#: gschem/src/x_dialog.c:1452
+#: gschem/src/x_dialog.c:1454
msgid "Angle 1:"
msgstr ""
-#: gschem/src/x_dialog.c:1456
+#: gschem/src/x_dialog.c:1458
msgid "Pitch 1:"
msgstr ""
-#: gschem/src/x_dialog.c:1460
+#: gschem/src/x_dialog.c:1462
msgid "Angle 2:"
msgstr ""
-#: gschem/src/x_dialog.c:1464
+#: gschem/src/x_dialog.c:1466
msgid "Pitch 2:"
msgstr ""
-#: gschem/src/x_dialog.c:1591
+#: gschem/src/x_dialog.c:1593
msgid "Arc Params"
msgstr ""
-#: gschem/src/x_dialog.c:1631
+#: gschem/src/x_dialog.c:1634
msgid "Arc Radius:"
msgstr ""
-#: gschem/src/x_dialog.c:1639
+#: gschem/src/x_dialog.c:1642
msgid "Start Angle:"
msgstr ""
-#: gschem/src/x_dialog.c:1647
+#: gschem/src/x_dialog.c:1650
msgid "Degrees of Sweep:"
msgstr ""
-#: gschem/src/x_dialog.c:1764
+#: gschem/src/x_dialog.c:1768
msgid ""
"Offset to translate?\n"
"(0 for origin)"
msgstr ""
-#: gschem/src/x_dialog.c:1832
+#: gschem/src/x_dialog.c:1836
msgid "Text Size"
msgstr ""
-#: gschem/src/x_dialog.c:1862
+#: gschem/src/x_dialog.c:1866
msgid "Enter new text size:"
msgstr ""
-#: gschem/src/x_dialog.c:1938
+#: gschem/src/x_dialog.c:1942
msgid "Snap Size"
msgstr ""
-#: gschem/src/x_dialog.c:1968
+#: gschem/src/x_dialog.c:1972
msgid "Enter new snap grid spacing:"
msgstr ""
-#: gschem/src/x_dialog.c:2045
+#: gschem/src/x_dialog.c:2049
msgid "Edit slot number"
msgstr ""
-#: gschem/src/x_dialog.c:2076
+#: gschem/src/x_dialog.c:2080
msgid "Edit slot number:"
msgstr ""
-#: gschem/src/x_dialog.c:2117
+#: gschem/src/x_dialog.c:2121
#, c-format
msgid "%s%s (%s)"
msgstr ""
-#: gschem/src/x_dialog.c:2140
+#: gschem/src/x_dialog.c:2144
msgid "About gschem"
msgstr ""
-#: gschem/src/x_dialog.c:2141
+#: gschem/src/x_dialog.c:2145
msgid "gEDA: GPL Electronic Design Automation"
msgstr ""
-#: gschem/src/x_dialog.c:2142
+#: gschem/src/x_dialog.c:2146
msgid ""
"Copyright © 1998-2009 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
"Copyright © 1998-2009 gEDA Contributors (see ChangeLog for details)"
msgstr ""
-#: gschem/src/x_dialog.c:2201
+#: gschem/src/x_dialog.c:2205
msgid "Coords"
msgstr ""
-#: gschem/src/x_dialog.c:2222
+#: gschem/src/x_dialog.c:2226
msgid "Screen"
msgstr ""
-#: gschem/src/x_dialog.c:2231
+#: gschem/src/x_dialog.c:2235
msgid "World"
msgstr ""
-#: gschem/src/x_dialog.c:2270
+#: gschem/src/x_dialog.c:2274
msgid "Background"
msgstr ""
-#: gschem/src/x_dialog.c:2276
+#: gschem/src/x_dialog.c:2280
msgid "Net endpoint"
msgstr ""
-#: gschem/src/x_dialog.c:2279
+#: gschem/src/x_dialog.c:2283
msgid "Graphic"
msgstr ""
-#: gschem/src/x_dialog.c:2288
+#: gschem/src/x_dialog.c:2292
msgid "Logic bubble"
msgstr ""
-#: gschem/src/x_dialog.c:2291
+#: gschem/src/x_dialog.c:2295
msgid "Grid point"
msgstr ""
-#: gschem/src/x_dialog.c:2294
+#: gschem/src/x_dialog.c:2298
msgid "Detached attribute"
msgstr ""
-#: gschem/src/x_dialog.c:2297 gschem/src/x_window.c:383
+#: gschem/src/x_dialog.c:2301 gschem/src/x_window.c:383
msgid "Text"
msgstr ""
-#: gschem/src/x_dialog.c:2303
+#: gschem/src/x_dialog.c:2307
msgid "Selection"
msgstr ""
-#: gschem/src/x_dialog.c:2306
+#: gschem/src/x_dialog.c:2310
msgid "Bounding box"
msgstr ""
-#: gschem/src/x_dialog.c:2309
+#: gschem/src/x_dialog.c:2313
msgid "Zoom box"
msgstr ""
-#: gschem/src/x_dialog.c:2318
+#: gschem/src/x_dialog.c:2322
msgid "Output background"
msgstr ""
-#: gschem/src/x_dialog.c:2321
+#: gschem/src/x_dialog.c:2325
msgid "Net junction"
msgstr ""
-#: gschem/src/x_dialog.c:2324
+#: gschem/src/x_dialog.c:2328
msgid "Mesh grid major"
msgstr ""
-#: gschem/src/x_dialog.c:2327
+#: gschem/src/x_dialog.c:2331
msgid "Mesh grid minor"
msgstr ""
-#: gschem/src/x_dialog.c:2330
+#: gschem/src/x_dialog.c:2334
msgid "Unknown"
msgstr ""
-#: gschem/src/x_dialog.c:2481
+#: gschem/src/x_dialog.c:2485
#, c-format
msgid "ERROR: NULL object in color_edit_dialog_apply!\n"
msgstr ""
-#: gschem/src/x_dialog.c:2525
+#: gschem/src/x_dialog.c:2529
msgid "Color Edit"
msgstr ""
-#: gschem/src/x_dialog.c:2556
+#: gschem/src/x_dialog.c:2560
msgid "Object color:"
msgstr ""
-#: gschem/src/x_dialog.c:2614
+#: gschem/src/x_dialog.c:2618
msgid "Hotkeys"
msgstr ""
-#: gschem/src/x_dialog.c:2678
+#: gschem/src/x_dialog.c:2682
msgid "Function"
msgstr ""
-#: gschem/src/x_dialog.c:2685
+#: gschem/src/x_dialog.c:2689
msgid "Keystroke(s)"
msgstr ""
-#: gschem/src/x_dialog.c:2991
+#: gschem/src/x_dialog.c:2995
msgid "Find Text"
msgstr ""
-#: gschem/src/x_dialog.c:3022
+#: gschem/src/x_dialog.c:3026
msgid "Text to find:"
msgstr ""
-#: gschem/src/x_dialog.c:3032
+#: gschem/src/x_dialog.c:3036
msgid "descend into hierarchy"
msgstr ""
-#: gschem/src/x_dialog.c:3097
+#: gschem/src/x_dialog.c:3101
msgid "Hide Text"
msgstr ""
-#: gschem/src/x_dialog.c:3128
+#: gschem/src/x_dialog.c:3132
msgid "Hide text starting with:"
msgstr ""
-#: gschem/src/x_dialog.c:3197
+#: gschem/src/x_dialog.c:3201
msgid "Show Text"
msgstr ""
-#: gschem/src/x_dialog.c:3228
+#: gschem/src/x_dialog.c:3232
msgid "Show text starting with:"
msgstr ""
-#: gschem/src/x_dialog.c:3685
+#: gschem/src/x_dialog.c:3689
msgid "S_elect the schematics you want to save:"
msgstr ""
-#: gschem/src/x_dialog.c:3779
+#: gschem/src/x_dialog.c:3784
#, c-format
msgid "Save the changes to schematic \"%s\" before closing?"
msgstr ""
-#: gschem/src/x_dialog.c:3785
+#: gschem/src/x_dialog.c:3790
#, c-format
msgid ""
"There are %d schematics with unsaved changes. Save changes before closing?"
msgstr ""
-#: gschem/src/x_dialog.c:3814
+#: gschem/src/x_dialog.c:3819
msgid "If you don't save, all your changes will be permanently lost."
msgstr ""
-#: gschem/src/x_dialog.c:3834
+#: gschem/src/x_dialog.c:3839
msgid "_Close without saving"
msgstr ""
-#: gschem/src/x_dialog.c:4170
+#: gschem/src/x_dialog.c:4175
#, c-format
msgid ""
"<span weight=\"bold\" size=\"larger\">The input attribute \"%s\" is invalid\n"
@@ -1487,19 +1495,19 @@ msgid ""
"The value cannot start with a space."
msgstr ""
-#: gschem/src/x_dialog.c:4172
+#: gschem/src/x_dialog.c:4177
msgid "Invalid Attribute"
msgstr ""
-#: gschem/src/x_dialog.c:4208
+#: gschem/src/x_dialog.c:4213
msgid "Pin type"
msgstr ""
-#: gschem/src/x_dialog.c:4232
+#: gschem/src/x_dialog.c:4237
msgid "Net pin"
msgstr ""
-#: gschem/src/x_dialog.c:4234
+#: gschem/src/x_dialog.c:4239
msgid "Bus pin (graphical)"
msgstr ""
@@ -1592,11 +1600,11 @@ msgstr ""
msgid "Write image..."
msgstr "å??å?¥å?¾ç??..."
-#: gschem/src/x_log.c:188
+#: gschem/src/x_log.c:209
msgid "** Invalid UTF-8 in log message. See stderr or gschem.log.\n"
msgstr ""
-#: gschem/src/x_log.c:256
+#: gschem/src/x_log.c:288
msgid "Status"
msgstr ""
@@ -1672,69 +1680,60 @@ msgstr ""
msgid "/Up"
msgstr ""
-#: gschem/src/x_menus.c:321
+#: gschem/src/x_menus.c:323
#, c-format
msgid "Tried to set the sensitivity on non-existent menu item '%s'\n"
msgstr ""
-#: gschem/src/x_menus.c:345
+#: gschem/src/x_menus.c:347
msgid "Popup_menu_item_factory doesn't exist!\n"
msgstr ""
-#: gschem/src/x_menus.c:358
+#: gschem/src/x_menus.c:360
msgid "Tried to set the sensitivity on a non-existent popup menu_item\n"
msgstr ""
-#: gschem/src/x_menus.c:438
-#, c-format
-msgid "Couldn't open file %s\n"
-msgstr ""
-
-#: gschem/src/x_menus.c:495
-msgid "Clear"
-msgstr ""
-
-#: gschem/src/x_multiattrib.c:911
+#: gschem/src/x_multiattrib.c:915
msgid "Attributes with empty name are not allowed. Please set a name."
msgstr ""
-#: gschem/src/x_multiattrib.c:1456
+#: gschem/src/x_multiattrib.c:1468
msgid "Show Value only"
msgstr ""
-#: gschem/src/x_multiattrib.c:1458
+#: gschem/src/x_multiattrib.c:1470
msgid "Show Name only"
msgstr ""
-#: gschem/src/x_multiattrib.c:1486
+#: gschem/src/x_multiattrib.c:1498
msgid "Promote"
msgstr ""
-#: gschem/src/x_multiattrib.c:1490
+#: gschem/src/x_multiattrib.c:1502
msgid "Duplicate"
msgstr ""
-#: gschem/src/x_multiattrib.c:1708
+#: gschem/src/x_multiattrib.c:1719
msgid "Edit Attributes"
msgstr ""
-#: gschem/src/x_multiattrib.c:1826
+#: gschem/src/x_multiattrib.c:1837
msgid "Vis?"
msgstr ""
-#: gschem/src/x_multiattrib.c:1844
+#: gschem/src/x_multiattrib.c:1855
msgid "N"
msgstr ""
-#: gschem/src/x_multiattrib.c:1862
+#: gschem/src/x_multiattrib.c:1873
msgid "V"
msgstr ""
-#: gschem/src/x_multiattrib.c:1884
+#: gschem/src/x_multiattrib.c:1895
msgid "Show inherited attributes"
msgstr ""
-#: gschem/src/x_multiattrib.c:1900
+#: gschem/src/x_multiattrib.c:1911
msgid "Add Attribute"
msgstr ""
@@ -1758,23 +1757,23 @@ msgstr "å?³é?页é?¢"
msgid "Discard Page"
msgstr ""
-#: gschem/src/x_pagesel.c:376
+#: gschem/src/x_pagesel.c:375
msgid "Page Manager"
msgstr ""
-#: gschem/src/x_pagesel.c:432
+#: gschem/src/x_pagesel.c:431
msgid "Filename"
msgstr ""
-#: gschem/src/x_pagesel.c:448
+#: gschem/src/x_pagesel.c:447
msgid "Changed"
msgstr ""
-#: gschem/src/x_pagesel.c:468
+#: gschem/src/x_pagesel.c:467
msgid "Right click on the filename for more options..."
msgstr ""
-#: gschem/src/x_preview.c:234
+#: gschem/src/x_preview.c:233
msgid "Preview Buffer"
msgstr ""
@@ -1830,23 +1829,23 @@ msgstr ""
msgid "Command:"
msgstr ""
-#: gschem/src/x_print.c:741
+#: gschem/src/x_print.c:745
msgid "No print destination specified\n"
msgstr ""
-#: gschem/src/x_print.c:748
+#: gschem/src/x_print.c:752
#, c-format
msgid "Cannot print current schematic to [%s]\n"
msgstr ""
-#: gschem/src/x_print.c:757
+#: gschem/src/x_print.c:761
#, c-format
msgid ""
"Error printing to file '%s'\n"
"Check the log window for more information"
msgstr ""
-#: gschem/src/x_print.c:764
+#: gschem/src/x_print.c:768
#, c-format
msgid "Printed current schematic to [%s]\n"
msgstr ""
@@ -1855,6 +1854,11 @@ msgstr ""
msgid "Execute Script..."
msgstr "æ?§è¡?è??æ?¬..."
+#: gschem/src/x_script.c:66
+#, c-format
+msgid "Executing guile script [%s]\n"
+msgstr ""
+
#: gschem/src/x_window.c:81
#, c-format
msgid "Couldn't allocate gc\n"
@@ -1962,35 +1966,35 @@ msgstr ""
msgid "New file [%s]\n"
msgstr ""
-#: gschem/src/x_window.c:857
+#: gschem/src/x_window.c:855
#, c-format
msgid "Could NOT save page [%s]\n"
msgstr ""
-#: gschem/src/x_window.c:858
+#: gschem/src/x_window.c:856
msgid "Error while trying to save"
msgstr ""
-#: gschem/src/x_window.c:867
+#: gschem/src/x_window.c:865
#, c-format
msgid "Saved as [%s]\n"
msgstr ""
-#: gschem/src/x_window.c:869
+#: gschem/src/x_window.c:867
#, c-format
msgid "Saved [%s]\n"
msgstr ""
-#: gschem/src/x_window.c:871
+#: gschem/src/x_window.c:869
msgid "Saved"
msgstr ""
-#: gschem/src/x_window.c:945
+#: gschem/src/x_window.c:943
#, c-format
msgid "Discarding page [%s]\n"
msgstr ""
-#: gschem/src/x_window.c:945
+#: gschem/src/x_window.c:943
#, c-format
msgid "Closing [%s]\n"
msgstr ""
@@ -2035,7 +2039,7 @@ msgstr "页é?¢ä¿?å?为..."
msgid "Save All"
msgstr "å?¨é?¨ä¿?å?"
-#: gschem/lib/system-gschemrc.scm:1386 gschem/lib/system-gschemrc.scm:1477
+#: gschem/lib/system-gschemrc.scm:1386 gschem/lib/system-gschemrc.scm:1478
#, fuzzy
msgid "_Revert"
msgstr "翻转页�"
@@ -2050,7 +2054,7 @@ msgstr "æ??å?°..."
msgid "Write _image..."
msgstr "å??å?¥å?¾ç??..."
-#: gschem/lib/system-gschemrc.scm:1393 gschem/lib/system-gschemrc.scm:1478
+#: gschem/lib/system-gschemrc.scm:1393 gschem/lib/system-gschemrc.scm:1479
#, fuzzy
msgid "_Close"
msgstr "å?³é?"
@@ -2090,425 +2094,430 @@ msgstr "ç²?è´´"
msgid "_Delete"
msgstr "å? é?¤"
-#: gschem/lib/system-gschemrc.scm:1412
+#: gschem/lib/system-gschemrc.scm:1409
+#, fuzzy
+msgid "Select All"
+msgstr "é??æ?©æ¨¡å¼?"
+
+#: gschem/lib/system-gschemrc.scm:1410
+msgid "Deselect"
+msgstr ""
+
+#: gschem/lib/system-gschemrc.scm:1414
msgid "Rotate 90 Mode"
msgstr "æ??转 90 度"
-#: gschem/lib/system-gschemrc.scm:1415
+#: gschem/lib/system-gschemrc.scm:1417
msgid "Edit..."
msgstr "ç¼?è¾?..."
-#: gschem/lib/system-gschemrc.scm:1416
+#: gschem/lib/system-gschemrc.scm:1418
msgid "Edit Text..."
msgstr "ç¼?è¾?æ??æ?¬..."
-#: gschem/lib/system-gschemrc.scm:1417
+#: gschem/lib/system-gschemrc.scm:1419
msgid "Slot..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1418
+#: gschem/lib/system-gschemrc.scm:1420
msgid "Color..."
msgstr "��..."
-#: gschem/lib/system-gschemrc.scm:1419
+#: gschem/lib/system-gschemrc.scm:1421
msgid "Line Width & Type..."
msgstr "线宽å??线å??..."
-#: gschem/lib/system-gschemrc.scm:1420
+#: gschem/lib/system-gschemrc.scm:1422
msgid "Fill Type..."
msgstr "å¡«å??ç±»å??..."
-#: gschem/lib/system-gschemrc.scm:1421
+#: gschem/lib/system-gschemrc.scm:1423
msgid "Symbol Translate..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1425
+#: gschem/lib/system-gschemrc.scm:1427
msgid "Invoke Macro"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1426
+#: gschem/lib/system-gschemrc.scm:1428
msgid "Embed Component/Picture"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1427
+#: gschem/lib/system-gschemrc.scm:1429
msgid "Unembed Component/Picture"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1428
+#: gschem/lib/system-gschemrc.scm:1430
msgid "Update Component"
msgstr "���件"
-#: gschem/lib/system-gschemrc.scm:1429
+#: gschem/lib/system-gschemrc.scm:1431
msgid "Show/Hide Inv Text"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1430
-msgid "Make Inv Text Vis"
-msgstr ""
-
-#: gschem/lib/system-gschemrc.scm:1436
+#: gschem/lib/system-gschemrc.scm:1437
msgid "Copy into 1"
msgstr "��� 1"
-#: gschem/lib/system-gschemrc.scm:1437
+#: gschem/lib/system-gschemrc.scm:1438
msgid "Copy into 2"
msgstr "��� 2"
-#: gschem/lib/system-gschemrc.scm:1438
+#: gschem/lib/system-gschemrc.scm:1439
msgid "Copy into 3"
msgstr "��� 3"
-#: gschem/lib/system-gschemrc.scm:1439
+#: gschem/lib/system-gschemrc.scm:1440
msgid "Copy into 4"
msgstr "��� 4"
-#: gschem/lib/system-gschemrc.scm:1440
+#: gschem/lib/system-gschemrc.scm:1441
msgid "Copy into 5"
msgstr "��� 5"
-#: gschem/lib/system-gschemrc.scm:1441
+#: gschem/lib/system-gschemrc.scm:1442
msgid "Cut into 1"
msgstr "å?ªå??å?° 1"
-#: gschem/lib/system-gschemrc.scm:1442
+#: gschem/lib/system-gschemrc.scm:1443
msgid "Cut into 2"
msgstr "å?ªå??å?° 2"
-#: gschem/lib/system-gschemrc.scm:1443
+#: gschem/lib/system-gschemrc.scm:1444
msgid "Cut into 3"
msgstr "å?ªå??å?° 3"
-#: gschem/lib/system-gschemrc.scm:1444
+#: gschem/lib/system-gschemrc.scm:1445
msgid "Cut into 4"
msgstr "å?ªå??å?° 4"
-#: gschem/lib/system-gschemrc.scm:1445
+#: gschem/lib/system-gschemrc.scm:1446
msgid "Cut into 5"
msgstr "å?ªå??å?° 5"
-#: gschem/lib/system-gschemrc.scm:1446
+#: gschem/lib/system-gschemrc.scm:1447
msgid "Paste from 1"
msgstr "ç²?è´´è?ª 1"
-#: gschem/lib/system-gschemrc.scm:1447
+#: gschem/lib/system-gschemrc.scm:1448
msgid "Paste from 2"
msgstr "ç²?è´´è?ª 2"
-#: gschem/lib/system-gschemrc.scm:1448
+#: gschem/lib/system-gschemrc.scm:1449
msgid "Paste from 3"
msgstr "ç²?è´´è?ª 3"
-#: gschem/lib/system-gschemrc.scm:1449
+#: gschem/lib/system-gschemrc.scm:1450
msgid "Paste from 4"
msgstr "ç²?è´´è?ª 4"
-#: gschem/lib/system-gschemrc.scm:1450
+#: gschem/lib/system-gschemrc.scm:1451
msgid "Paste from 5"
msgstr "ç²?è´´è?ª 5"
-#: gschem/lib/system-gschemrc.scm:1456
+#: gschem/lib/system-gschemrc.scm:1457
#, fuzzy
msgid "_Redraw"
msgstr "é??ç?»"
-#: gschem/lib/system-gschemrc.scm:1457
+#: gschem/lib/system-gschemrc.scm:1458
msgid "_Pan"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1458
+#: gschem/lib/system-gschemrc.scm:1459
#, fuzzy
msgid "Zoom _Box"
msgstr "�大"
-#: gschem/lib/system-gschemrc.scm:1459
+#: gschem/lib/system-gschemrc.scm:1460
#, fuzzy
msgid "Zoom _Extents"
msgstr "�大"
-#: gschem/lib/system-gschemrc.scm:1460
+#: gschem/lib/system-gschemrc.scm:1461
#, fuzzy
msgid "Zoom _In"
msgstr "�大"
-#: gschem/lib/system-gschemrc.scm:1461
+#: gschem/lib/system-gschemrc.scm:1462
#, fuzzy
msgid "Zoom _Out"
msgstr "缩�"
-#: gschem/lib/system-gschemrc.scm:1462
+#: gschem/lib/system-gschemrc.scm:1463
#, fuzzy
msgid "Zoom _Full"
msgstr "缩�"
-#: gschem/lib/system-gschemrc.scm:1464
+#: gschem/lib/system-gschemrc.scm:1465
msgid "_Dark color scheme"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1465
+#: gschem/lib/system-gschemrc.scm:1466
msgid "_Light color scheme"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1466
+#: gschem/lib/system-gschemrc.scm:1467
msgid "B_W color scheme"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1473
+#: gschem/lib/system-gschemrc.scm:1474
#, fuzzy
msgid "_Manager..."
msgstr "æ??å¼?页é?¢..."
-#: gschem/lib/system-gschemrc.scm:1474
+#: gschem/lib/system-gschemrc.scm:1475
#, fuzzy
msgid "_Previous"
msgstr "��个"
-#: gschem/lib/system-gschemrc.scm:1475
+#: gschem/lib/system-gschemrc.scm:1476
#, fuzzy
msgid "_Next"
msgstr "��个"
-#: gschem/lib/system-gschemrc.scm:1476
+#: gschem/lib/system-gschemrc.scm:1477
#, fuzzy
msgid "Ne_w"
msgstr "�建"
-#: gschem/lib/system-gschemrc.scm:1480
+#: gschem/lib/system-gschemrc.scm:1481
#, fuzzy
msgid "_Discard"
msgstr "丢�"
-#: gschem/lib/system-gschemrc.scm:1486
+#: gschem/lib/system-gschemrc.scm:1487
#, fuzzy
msgid "_Component..."
msgstr "�件..."
-#: gschem/lib/system-gschemrc.scm:1487
+#: gschem/lib/system-gschemrc.scm:1488
#, fuzzy
msgid "_Net"
msgstr "��个"
-#: gschem/lib/system-gschemrc.scm:1488
+#: gschem/lib/system-gschemrc.scm:1489
#, fuzzy
msgid "B_us"
msgstr "�线"
-#: gschem/lib/system-gschemrc.scm:1489
+#: gschem/lib/system-gschemrc.scm:1490
#, fuzzy
msgid "_Attribute..."
msgstr "å±?æ?§..."
-#: gschem/lib/system-gschemrc.scm:1490
+#: gschem/lib/system-gschemrc.scm:1491
#, fuzzy
msgid "_Text..."
msgstr "æ??æ?¬..."
-#: gschem/lib/system-gschemrc.scm:1492
+#: gschem/lib/system-gschemrc.scm:1493
msgid "_Line"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1493
+#: gschem/lib/system-gschemrc.scm:1494
msgid "_Box"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1494
+#: gschem/lib/system-gschemrc.scm:1495
#, fuzzy
msgid "C_ircle"
msgstr "å??"
-#: gschem/lib/system-gschemrc.scm:1495
+#: gschem/lib/system-gschemrc.scm:1496
#, fuzzy
msgid "A_rc"
msgstr "弧线"
-#: gschem/lib/system-gschemrc.scm:1496
+#: gschem/lib/system-gschemrc.scm:1497
msgid "_Pin"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1497
+#: gschem/lib/system-gschemrc.scm:1498
#, fuzzy
msgid "Pictu_re..."
msgstr "å?¾ç??..."
-#: gschem/lib/system-gschemrc.scm:1503
+#: gschem/lib/system-gschemrc.scm:1504
msgid "_Down Schematic"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1504
+#: gschem/lib/system-gschemrc.scm:1505
msgid "Down _Symbol"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1505
+#: gschem/lib/system-gschemrc.scm:1506
msgid "_Up"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1506
+#: gschem/lib/system-gschemrc.scm:1507
#, fuzzy
msgid "D_ocumentation..."
msgstr "æ??æ¡£"
-#: gschem/lib/system-gschemrc.scm:1512
+#: gschem/lib/system-gschemrc.scm:1513
#, fuzzy
msgid "_Attach"
msgstr "è¿?æ?¥"
-#: gschem/lib/system-gschemrc.scm:1513
+#: gschem/lib/system-gschemrc.scm:1514
#, fuzzy
msgid "_Detach"
msgstr "�离"
-#: gschem/lib/system-gschemrc.scm:1514
+#: gschem/lib/system-gschemrc.scm:1515
#, fuzzy
msgid "Show _Value"
msgstr "�示��"
-#: gschem/lib/system-gschemrc.scm:1515
+#: gschem/lib/system-gschemrc.scm:1516
#, fuzzy
msgid "Show _Name"
msgstr "æ?¾ç¤ºå??称"
-#: gschem/lib/system-gschemrc.scm:1516
+#: gschem/lib/system-gschemrc.scm:1517
#, fuzzy
msgid "Show _Both"
msgstr "��示"
-#: gschem/lib/system-gschemrc.scm:1517
+#: gschem/lib/system-gschemrc.scm:1518
#, fuzzy
msgid "_Toggle Visibility"
msgstr "å??æ?¢å?¯è§?æ?§"
-#: gschem/lib/system-gschemrc.scm:1519
+#: gschem/lib/system-gschemrc.scm:1520
msgid "_Find Specific Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1520
+#: gschem/lib/system-gschemrc.scm:1521
msgid "_Hide Specific Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1521
+#: gschem/lib/system-gschemrc.scm:1522
msgid "_Show Specific Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1522
+#: gschem/lib/system-gschemrc.scm:1523
msgid "A_utonumber Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1528
+#: gschem/lib/system-gschemrc.scm:1529
#, fuzzy
msgid "_Text Size..."
msgstr "æ??æ?¬..."
-#: gschem/lib/system-gschemrc.scm:1529
+#: gschem/lib/system-gschemrc.scm:1530
msgid "Cycle _grid styles"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1530
+#: gschem/lib/system-gschemrc.scm:1531
msgid "Toggle _Snap On/Off"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1531
+#: gschem/lib/system-gschemrc.scm:1532
msgid "Snap Grid S_pacing..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1532
+#: gschem/lib/system-gschemrc.scm:1533
msgid "Scale _up Grid Spacing"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1534
+#: gschem/lib/system-gschemrc.scm:1535
msgid "Scale _down Grid Spacing"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1536
+#: gschem/lib/system-gschemrc.scm:1537
msgid "Toggle _Outline/Box"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1538
+#: gschem/lib/system-gschemrc.scm:1539
msgid "Toggle Net _Rubberband"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1539
+#: gschem/lib/system-gschemrc.scm:1540
msgid "Toggle _Magnetic Net"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1540
+#: gschem/lib/system-gschemrc.scm:1541
msgid "Show _Log Window..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1542
+#: gschem/lib/system-gschemrc.scm:1543
msgid "Show _Coord Window..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1558
+#: gschem/lib/system-gschemrc.scm:1559
#, fuzzy
msgid "gEDA Docu_mentation..."
msgstr "æ??æ¡£"
-#: gschem/lib/system-gschemrc.scm:1559
+#: gschem/lib/system-gschemrc.scm:1560
msgid "gschem _FAQ..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1560
+#: gschem/lib/system-gschemrc.scm:1561
msgid "gEDA _Wiki..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1561
+#: gschem/lib/system-gschemrc.scm:1562
#, fuzzy
msgid "Component D_ocumentation..."
msgstr "æ??æ¡£"
-#: gschem/lib/system-gschemrc.scm:1563
+#: gschem/lib/system-gschemrc.scm:1564
msgid "_Hotkeys..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1564
+#: gschem/lib/system-gschemrc.scm:1565
#, fuzzy
msgid "_About..."
msgstr "å±?æ?§..."
-#: gschem/lib/system-gschemrc.scm:1570
+#: gschem/lib/system-gschemrc.scm:1571
#, fuzzy
msgid "_File"
msgstr "æ??件"
-#: gschem/lib/system-gschemrc.scm:1571
+#: gschem/lib/system-gschemrc.scm:1572
#, fuzzy
msgid "_Edit"
msgstr "ç¼?è¾?"
-#: gschem/lib/system-gschemrc.scm:1572
+#: gschem/lib/system-gschemrc.scm:1573
#, fuzzy
msgid "_Buffer"
msgstr "���"
-#: gschem/lib/system-gschemrc.scm:1573
+#: gschem/lib/system-gschemrc.scm:1574
#, fuzzy
msgid "_View"
msgstr "æ?¥ç??"
-#: gschem/lib/system-gschemrc.scm:1574
+#: gschem/lib/system-gschemrc.scm:1575
#, fuzzy
msgid "_Page"
msgstr "页�"
-#: gschem/lib/system-gschemrc.scm:1575
+#: gschem/lib/system-gschemrc.scm:1576
#, fuzzy
msgid "_Add"
msgstr "æ·»å? "
-#: gschem/lib/system-gschemrc.scm:1576
+#: gschem/lib/system-gschemrc.scm:1577
#, fuzzy
msgid "Hie_rarchy"
msgstr "�次"
-#: gschem/lib/system-gschemrc.scm:1577
+#: gschem/lib/system-gschemrc.scm:1578
#, fuzzy
msgid "A_ttributes"
msgstr "å±?æ?§"
-#: gschem/lib/system-gschemrc.scm:1578
+#: gschem/lib/system-gschemrc.scm:1579
msgid "_Options"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1579
+#: gschem/lib/system-gschemrc.scm:1580
msgid "_Help"
msgstr ""
diff --git a/gschem/po/zh_TW.po b/gschem/po/zh_TW.po
index 1f916e2..0c5be66 100644
--- a/gschem/po/zh_TW.po
+++ b/gschem/po/zh_TW.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2010-11-07 13:37+0000\n"
+"POT-Creation-Date: 2011-01-16 00:11-0500\n"
"PO-Revision-Date: 2010-02-11 03:31+0000\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -22,17 +22,17 @@ msgstr ""
msgid "Zoom too small! Cannot zoom further.\n"
msgstr "å·²ç¶?縮å?°æ??å°?äº?ï¼?ç?¡æ³?å??縮å°?å??ï¼?\n"
-#: gschem/src/g_funcs.c:339 gschem/src/i_callbacks.c:68
+#: gschem/src/g_funcs.c:347 gschem/src/i_callbacks.c:68
#, c-format
msgid "Could not fork\n"
msgstr ""
-#: gschem/src/g_funcs.c:355 gschem/src/i_callbacks.c:78
+#: gschem/src/g_funcs.c:363 gschem/src/i_callbacks.c:78
#, c-format
msgid "Could not invoke %s\n"
msgstr ""
-#: gschem/src/g_funcs.c:361 gschem/src/i_callbacks.c:82
+#: gschem/src/g_funcs.c:369 gschem/src/i_callbacks.c:82
msgid "Documentation commands not supported under MinGW.\n"
msgstr ""
@@ -121,39 +121,39 @@ msgstr ""
msgid "Invalid number of steps [%d] scrollpan-steps\n"
msgstr ""
-#: gschem/src/gschem.c:184
+#: gschem/src/gschem.c:188
#, c-format
msgid "gEDA/gschem version %s%s.%s\n"
msgstr ""
-#: gschem/src/gschem.c:187
+#: gschem/src/gschem.c:191
msgid ""
"gEDA/gschem comes with ABSOLUTELY NO WARRANTY; see COPYING for more "
"details.\n"
msgstr ""
-#: gschem/src/gschem.c:189
+#: gschem/src/gschem.c:193
msgid ""
"This is free software, and you are welcome to redistribute it under certain\n"
msgstr ""
-#: gschem/src/gschem.c:191
+#: gschem/src/gschem.c:195
msgid ""
"conditions; please see the COPYING file for more details.\n"
"\n"
msgstr ""
-#: gschem/src/gschem.c:194
+#: gschem/src/gschem.c:198
#, c-format
msgid "This is the MINGW32 port.\n"
msgstr ""
-#: gschem/src/gschem.c:198
+#: gschem/src/gschem.c:202
#, c-format
msgid "Current locale settings: %s\n"
msgstr "ç?®å??ç??èª?ç³»è¨å®?: %s\n"
-#: gschem/src/gschem.c:213
+#: gschem/src/gschem.c:218
msgid ""
"You must set the GEDADATA environment variable!\n"
"\n"
@@ -161,31 +161,21 @@ msgid ""
"environment variable to point to the correct location.\n"
msgstr ""
-#: gschem/src/gschem.c:248
+#: gschem/src/gschem.c:256
#, c-format
msgid "Couldn't find init scm file [%s]\n"
msgstr ""
-#: gschem/src/gschem.c:252
+#: gschem/src/gschem.c:260
#, c-format
msgid "Read init scm file [%s]\n"
msgstr ""
-#: gschem/src/gschem.c:256
+#: gschem/src/gschem.c:264
#, c-format
msgid "Failed to read init scm file [%s]\n"
msgstr ""
-#: gschem/src/gschem.c:317
-#, c-format
-msgid "Scheme directory NOT set!\n"
-msgstr ""
-
-#: gschem/src/gschem.c:324 gschem/src/x_script.c:66
-#, c-format
-msgid "Executing guile script [%s]\n"
-msgstr "æ£å?¨å?·è¡?guileè?³æ?¬ [%s]\n"
-
#: gschem/src/gschem_cairo.c:310
#, c-format
msgid "Unknown end for line (%d)\n"
@@ -209,11 +199,11 @@ msgstr "å??件模å¼?"
msgid "Text Mode"
msgstr "æ??å?模å¼?"
-#: gschem/src/i_basic.c:84 gschem/lib/system-gschemrc.scm:1409
+#: gschem/src/i_basic.c:84 gschem/lib/system-gschemrc.scm:1411
msgid "Copy Mode"
msgstr "�製模�"
-#: gschem/src/i_basic.c:87 gschem/lib/system-gschemrc.scm:1411
+#: gschem/src/i_basic.c:87 gschem/lib/system-gschemrc.scm:1413
msgid "Move Mode"
msgstr "移å??å??件"
@@ -221,7 +211,7 @@ msgstr "移å??å??件"
msgid "Rotate Mode"
msgstr "æ??è½?模å¼?"
-#: gschem/src/i_basic.c:91 gschem/lib/system-gschemrc.scm:1413
+#: gschem/src/i_basic.c:91 gschem/lib/system-gschemrc.scm:1415
msgid "Mirror Mode"
msgstr "水平��"
@@ -274,22 +264,22 @@ msgstr "弧�模�"
msgid "Pin Mode"
msgstr ""
-#: gschem/src/i_basic.c:135 gschem/src/i_callbacks.c:544
-#: gschem/src/i_callbacks.c:568
+#: gschem/src/i_basic.c:135 gschem/src/i_callbacks.c:576
+#: gschem/src/i_callbacks.c:600
msgid "Copy"
msgstr "�製"
-#: gschem/src/i_basic.c:137 gschem/src/i_callbacks.c:634
-#: gschem/src/i_callbacks.c:658
+#: gschem/src/i_basic.c:137 gschem/src/i_callbacks.c:666
+#: gschem/src/i_callbacks.c:690
msgid "Move"
msgstr "�移"
-#: gschem/src/i_basic.c:139 gschem/src/i_callbacks.c:589
-#: gschem/src/i_callbacks.c:613
+#: gschem/src/i_basic.c:139 gschem/src/i_callbacks.c:621
+#: gschem/src/i_callbacks.c:645
msgid "Multiple Copy"
msgstr "å¤?é??è¤?製"
-#: gschem/src/i_basic.c:142 gschem/lib/system-gschemrc.scm:1410
+#: gschem/src/i_basic.c:142 gschem/lib/system-gschemrc.scm:1412
msgid "Multiple Copy Mode"
msgstr "å¤?é??è¤?製模å¼?"
@@ -309,7 +299,7 @@ msgstr ""
msgid "Action"
msgstr ""
-#: gschem/src/i_basic.c:260 gschem/src/x_dialog.c:2312
+#: gschem/src/i_basic.c:260 gschem/src/x_dialog.c:2316
#: gschem/src/x_window.c:491
msgid "Stroke"
msgstr ""
@@ -340,7 +330,7 @@ msgstr "ç¶²æ ¼(%s, %s)"
msgid "Documentation for [%s,%s,%s,%s]\n"
msgstr ""
-#: gschem/src/i_callbacks.c:123 gschem/src/i_callbacks.c:1699
+#: gschem/src/i_callbacks.c:123 gschem/src/i_callbacks.c:1706
#, c-format
msgid "New page created [%s]\n"
msgstr ""
@@ -362,327 +352,323 @@ msgstr "å?²å?å?¨é?¨"
msgid "Closing Window\n"
msgstr ""
-#: gschem/src/i_callbacks.c:549 gschem/src/i_callbacks.c:594
-#: gschem/src/i_callbacks.c:639
+#: gschem/src/i_callbacks.c:581 gschem/src/i_callbacks.c:626
+#: gschem/src/i_callbacks.c:671
msgid "Select objs first"
msgstr "è«?å??é?¸æ??ç?©ä»¶"
-#: gschem/src/i_callbacks.c:678 gschem/src/x_multiattrib.c:1491
+#: gschem/src/i_callbacks.c:710 gschem/src/x_multiattrib.c:1503
msgid "Delete"
msgstr "��"
-#: gschem/src/i_callbacks.c:703
+#: gschem/src/i_callbacks.c:735
msgid "Edit"
msgstr "編輯"
-#: gschem/src/i_callbacks.c:718
+#: gschem/src/i_callbacks.c:750
msgid "Edit pin type"
msgstr ""
-#: gschem/src/i_callbacks.c:737
+#: gschem/src/i_callbacks.c:769
msgid "Edit Text"
msgstr "編輯æ??å?"
-#: gschem/src/i_callbacks.c:760
+#: gschem/src/i_callbacks.c:792
msgid "Slot"
msgstr ""
-#: gschem/src/i_callbacks.c:777
+#: gschem/src/i_callbacks.c:809
msgid "Color"
msgstr ""
-#: gschem/src/i_callbacks.c:814 gschem/src/i_callbacks.c:859
+#: gschem/src/i_callbacks.c:846 gschem/src/i_callbacks.c:891
msgid "Rotate"
msgstr "æ??è½?"
-#: gschem/src/i_callbacks.c:882 gschem/src/i_callbacks.c:907
+#: gschem/src/i_callbacks.c:913 gschem/src/i_callbacks.c:938
msgid "Mirror"
msgstr ""
-#: gschem/src/i_callbacks.c:928 gschem/src/x_dialog.c:2315
-#: gschem/lib/system-gschemrc.scm:1422
+#: gschem/src/i_callbacks.c:959 gschem/src/x_dialog.c:2319
+#: gschem/lib/system-gschemrc.scm:1424
msgid "Lock"
msgstr "��"
-#: gschem/src/i_callbacks.c:946 gschem/lib/system-gschemrc.scm:1423
+#: gschem/src/i_callbacks.c:977 gschem/lib/system-gschemrc.scm:1425
msgid "Unlock"
msgstr "解���"
-#: gschem/src/i_callbacks.c:964 gschem/src/x_dialog.c:1734
+#: gschem/src/i_callbacks.c:995 gschem/src/x_dialog.c:1737
msgid "Translate"
msgstr ""
-#: gschem/src/i_callbacks.c:967
+#: gschem/src/i_callbacks.c:998
msgid "WARNING: Do not translate with snap off!\n"
msgstr ""
-#: gschem/src/i_callbacks.c:968
+#: gschem/src/i_callbacks.c:999
msgid "WARNING: Turning snap on and continuing with translate.\n"
msgstr ""
-#: gschem/src/i_callbacks.c:975
+#: gschem/src/i_callbacks.c:1006
msgid "WARNING: Snap grid size is not equal to 100!\n"
msgstr ""
-#: gschem/src/i_callbacks.c:977
+#: gschem/src/i_callbacks.c:1008
msgid ""
"WARNING: If you are translating a symbol to the origin, the snap grid size "
"should be set to 100\n"
msgstr ""
-#: gschem/src/i_callbacks.c:1008
+#: gschem/src/i_callbacks.c:1039
msgid "Embed"
msgstr ""
-#: gschem/src/i_callbacks.c:1047
+#: gschem/src/i_callbacks.c:1078
msgid "Unembed"
msgstr ""
-#: gschem/src/i_callbacks.c:1089
+#: gschem/src/i_callbacks.c:1120
msgid "Update"
msgstr ""
-#: gschem/src/i_callbacks.c:1136
+#: gschem/src/i_callbacks.c:1167
msgid "ShowHidden"
msgstr ""
-#: gschem/src/i_callbacks.c:1160
-msgid "MakeVisible"
-msgstr ""
-
-#: gschem/src/i_callbacks.c:1466 gschem/src/i_callbacks.c:1538
+#: gschem/src/i_callbacks.c:1473 gschem/src/i_callbacks.c:1545
msgid "Pan"
msgstr ""
-#: gschem/src/i_callbacks.c:1743
+#: gschem/src/i_callbacks.c:1750
msgid "Really revert page?"
msgstr ""
-#: gschem/src/i_callbacks.c:1813
+#: gschem/src/i_callbacks.c:1820
msgid "Copy to clipboard"
msgstr ""
-#: gschem/src/i_callbacks.c:1831
+#: gschem/src/i_callbacks.c:1838
msgid "Cut to clipboard"
msgstr ""
-#: gschem/src/i_callbacks.c:1849
+#: gschem/src/i_callbacks.c:1856
msgid "Paste from clipboard"
msgstr ""
-#: gschem/src/i_callbacks.c:1861 gschem/src/i_callbacks.c:2100
-#: gschem/src/i_callbacks.c:2122 gschem/src/i_callbacks.c:2144
-#: gschem/src/i_callbacks.c:2166 gschem/src/i_callbacks.c:2188
+#: gschem/src/i_callbacks.c:1868 gschem/src/i_callbacks.c:2107
+#: gschem/src/i_callbacks.c:2129 gschem/src/i_callbacks.c:2151
+#: gschem/src/i_callbacks.c:2173 gschem/src/i_callbacks.c:2195
msgid "Empty buffer"
msgstr ""
-#: gschem/src/i_callbacks.c:1906
+#: gschem/src/i_callbacks.c:1913
msgid "Copy 1"
msgstr ""
-#: gschem/src/i_callbacks.c:1925
+#: gschem/src/i_callbacks.c:1932
msgid "Copy 2"
msgstr ""
-#: gschem/src/i_callbacks.c:1944
+#: gschem/src/i_callbacks.c:1951
msgid "Copy 3"
msgstr ""
-#: gschem/src/i_callbacks.c:1963
+#: gschem/src/i_callbacks.c:1970
msgid "Copy 4"
msgstr ""
-#: gschem/src/i_callbacks.c:1982
+#: gschem/src/i_callbacks.c:1989
msgid "Copy 5"
msgstr ""
-#: gschem/src/i_callbacks.c:2001
+#: gschem/src/i_callbacks.c:2008
msgid "Cut 1"
msgstr ""
-#: gschem/src/i_callbacks.c:2020
+#: gschem/src/i_callbacks.c:2027
msgid "Cut 2"
msgstr ""
-#: gschem/src/i_callbacks.c:2039
+#: gschem/src/i_callbacks.c:2046
msgid "Cut 3"
msgstr ""
-#: gschem/src/i_callbacks.c:2058
+#: gschem/src/i_callbacks.c:2065
msgid "Cut 4"
msgstr ""
-#: gschem/src/i_callbacks.c:2077
+#: gschem/src/i_callbacks.c:2084
msgid "Cut 5"
msgstr ""
-#: gschem/src/i_callbacks.c:2093
+#: gschem/src/i_callbacks.c:2100
msgid "Paste 1"
msgstr ""
-#: gschem/src/i_callbacks.c:2115
+#: gschem/src/i_callbacks.c:2122
msgid "Paste 2"
msgstr ""
-#: gschem/src/i_callbacks.c:2137
+#: gschem/src/i_callbacks.c:2144
msgid "Paste 3"
msgstr ""
-#: gschem/src/i_callbacks.c:2159
+#: gschem/src/i_callbacks.c:2166
msgid "Paste 4"
msgstr ""
-#: gschem/src/i_callbacks.c:2181
+#: gschem/src/i_callbacks.c:2188
msgid "Paste 5"
msgstr ""
-#: gschem/src/i_callbacks.c:2318 gschem/src/x_window.c:355
+#: gschem/src/i_callbacks.c:2325 gschem/src/x_window.c:355
msgid "Component"
msgstr "å??件"
-#: gschem/src/i_callbacks.c:2354 gschem/src/i_callbacks.c:2373
-#: gschem/src/x_dialog.c:2285
+#: gschem/src/i_callbacks.c:2361 gschem/src/i_callbacks.c:2380
+#: gschem/src/x_dialog.c:2289
msgid "Attribute"
msgstr "屬�"
-#: gschem/src/i_callbacks.c:2395 gschem/src/i_callbacks.c:2422
-#: gschem/src/x_dialog.c:2282
+#: gschem/src/i_callbacks.c:2402 gschem/src/i_callbacks.c:2429
+#: gschem/src/x_dialog.c:2286
msgid "Net"
msgstr ""
-#: gschem/src/i_callbacks.c:2466 gschem/src/i_callbacks.c:2493
-#: gschem/src/x_dialog.c:2300 gschem/src/x_window.c:375
+#: gschem/src/i_callbacks.c:2473 gschem/src/i_callbacks.c:2500
+#: gschem/src/x_dialog.c:2304 gschem/src/x_window.c:375
msgid "Bus"
msgstr ""
-#: gschem/src/i_callbacks.c:2574 gschem/src/i_callbacks.c:2597
+#: gschem/src/i_callbacks.c:2581 gschem/src/i_callbacks.c:2604
msgid "Line"
msgstr "ç?´ç·?"
-#: gschem/src/i_callbacks.c:2619 gschem/src/i_callbacks.c:2642
+#: gschem/src/i_callbacks.c:2626 gschem/src/i_callbacks.c:2649
msgid "Box"
msgstr "ç?©å½¢"
-#: gschem/src/i_callbacks.c:2698 gschem/src/i_callbacks.c:2722
+#: gschem/src/i_callbacks.c:2705 gschem/src/i_callbacks.c:2729
msgid "Circle"
msgstr "å??å½¢"
-#: gschem/src/i_callbacks.c:2744 gschem/src/i_callbacks.c:2767
+#: gschem/src/i_callbacks.c:2751 gschem/src/i_callbacks.c:2774
msgid "Arc"
msgstr "弧�"
-#: gschem/src/i_callbacks.c:2789 gschem/src/i_callbacks.c:2812
-#: gschem/src/x_dialog.c:2273
+#: gschem/src/i_callbacks.c:2796 gschem/src/i_callbacks.c:2819
+#: gschem/src/x_dialog.c:2277
msgid "Pin"
msgstr ""
-#: gschem/src/i_callbacks.c:2871
+#: gschem/src/i_callbacks.c:2878
#, c-format
msgid "Searching for source [%s]\n"
msgstr ""
-#: gschem/src/i_callbacks.c:2895
+#: gschem/src/i_callbacks.c:2902
#, c-format
msgid "Cannot find source [%s]\n"
msgstr ""
-#: gschem/src/i_callbacks.c:2964
+#: gschem/src/i_callbacks.c:2965
#, c-format
msgid "Searching for symbol [%s]\n"
msgstr ""
-#: gschem/src/i_callbacks.c:2970
+#: gschem/src/i_callbacks.c:2971
msgid "Symbol is not a real file. Symbol cannot be loaded.\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3001
+#: gschem/src/i_callbacks.c:3002
msgid "Cannot find any schematics above the current one!\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3055
+#: gschem/src/i_callbacks.c:3056
msgid ""
"This command retrieves the component documentation from the web, but there "
"is no component selected"
msgstr ""
-#: gschem/src/i_callbacks.c:3083
+#: gschem/src/i_callbacks.c:3084
msgid "Attach"
msgstr ""
-#: gschem/src/i_callbacks.c:3130
+#: gschem/src/i_callbacks.c:3131
msgid "Detach"
msgstr ""
-#: gschem/src/i_callbacks.c:3165
+#: gschem/src/i_callbacks.c:3166
msgid "ShowN"
msgstr ""
-#: gschem/src/i_callbacks.c:3201
+#: gschem/src/i_callbacks.c:3202
msgid "ShowV"
msgstr ""
-#: gschem/src/i_callbacks.c:3237
+#: gschem/src/i_callbacks.c:3238
msgid "ShowB"
msgstr ""
-#: gschem/src/i_callbacks.c:3274
+#: gschem/src/i_callbacks.c:3275
msgid "VisToggle"
msgstr ""
-#: gschem/src/i_callbacks.c:3304
+#: gschem/src/i_callbacks.c:3305
#, c-format
msgid "Sorry but this is a non-functioning menu option\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3394
+#: gschem/src/i_callbacks.c:3395
msgid "Action feedback mode set to OUTLINE\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3397
+#: gschem/src/i_callbacks.c:3398
msgid "Action feedback mode set to BOUNDINGBOX\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3422
+#: gschem/src/i_callbacks.c:3423
msgid "Grid OFF\n"
msgstr "é??é??ç¶²æ ¼\n"
-#: gschem/src/i_callbacks.c:3423
+#: gschem/src/i_callbacks.c:3424
msgid "Dot grid selected\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3424
+#: gschem/src/i_callbacks.c:3425
msgid "Mesh grid selected\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3445
+#: gschem/src/i_callbacks.c:3446
msgid "Snap OFF (CAUTION!)\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3448
+#: gschem/src/i_callbacks.c:3449
msgid "Snap ON\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3451
+#: gschem/src/i_callbacks.c:3452
msgid "Snap back to the grid (CAUTION!)\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3477
+#: gschem/src/i_callbacks.c:3478
msgid "Rubber band OFF \n"
msgstr ""
-#: gschem/src/i_callbacks.c:3480
+#: gschem/src/i_callbacks.c:3481
msgid "Rubber band ON\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3495
+#: gschem/src/i_callbacks.c:3496
msgid "magnetic net mode: ON\n"
msgstr ""
-#: gschem/src/i_callbacks.c:3498
+#: gschem/src/i_callbacks.c:3499
msgid "magnetic net mode: OFF\n"
msgstr ""
-#: gschem/src/o_box.c:153
+#: gschem/src/o_box.c:149
#, c-format
msgid "Unknown type for box (fill)!\n"
msgstr ""
@@ -702,17 +688,17 @@ msgstr ""
msgid "Got an invalid buffer_number [o_buffer_paste_start]\n"
msgstr ""
-#: gschem/src/o_bus.c:118
+#: gschem/src/o_bus.c:117
#, c-format
msgid "Got an invalid which one in o_bus_draw_stretch\n"
msgstr ""
-#: gschem/src/o_circle.c:134
+#: gschem/src/o_circle.c:130
#, c-format
msgid "Unknown type for circle (fill)!\n"
msgstr ""
-#: gschem/src/o_complex.c:243 gschem/src/o_complex.c:247
+#: gschem/src/o_complex.c:237 gschem/src/o_complex.c:241
#, c-format
msgid "Translating schematic [%d %d]\n"
msgstr ""
@@ -730,35 +716,35 @@ msgstr "�件已�被����\n"
msgid "Object already unlocked\n"
msgstr "�件已�被解����\n"
-#: gschem/src/o_misc.c:413
+#: gschem/src/o_misc.c:409
msgid "Hidden text is now visible\n"
msgstr "é?±è??ç??æ??å?ç?¾å?¨å·²ç¶?å?¯ä»¥ç??è¦?\n"
-#: gschem/src/o_misc.c:415
+#: gschem/src/o_misc.c:411
msgid "Hidden text is now invisible\n"
msgstr "é?±è??ç??æ??å?ç?¾å?¨ç?¡æ³?ç??è¦?\n"
-#: gschem/src/o_misc.c:668
+#: gschem/src/o_misc.c:636
#, c-format
msgid "Could not find symbol [%s] in library. Update failed.\n"
msgstr ""
-#: gschem/src/o_misc.c:783
+#: gschem/src/o_misc.c:751
#, c-format
msgid "o_autosave_backups: Can't get the real filename of %s."
msgstr ""
-#: gschem/src/o_misc.c:827
+#: gschem/src/o_misc.c:795
#, c-format
msgid "Could NOT set previous backup file [%s] read-write\n"
msgstr ""
-#: gschem/src/o_misc.c:845
+#: gschem/src/o_misc.c:815
#, c-format
msgid "Could NOT set backup file [%s] readonly\n"
msgstr ""
-#: gschem/src/o_misc.c:850
+#: gschem/src/o_misc.c:820
#, c-format
msgid "Could NOT save backup file [%s]\n"
msgstr ""
@@ -778,36 +764,36 @@ msgstr ""
msgid "Got a non line object in o_move_check_endpoint\n"
msgstr ""
-#: gschem/src/o_net.c:159
+#: gschem/src/o_net.c:158
#, c-format
msgid "Got an invalid which one in o_net_draw_stretch\n"
msgstr ""
-#: gschem/src/o_net.c:538
+#: gschem/src/o_net.c:537
msgid "Warning: Starting net at off grid coordinate\n"
msgstr ""
-#: gschem/src/o_net.c:600
+#: gschem/src/o_net.c:599
msgid "Warning: Ending net at off grid coordinate\n"
msgstr ""
-#: gschem/src/o_net.c:932 gschem/src/o_net.c:969 gschem/src/o_net.c:1040
-#: gschem/src/o_net.c:1076
+#: gschem/src/o_net.c:931 gschem/src/o_net.c:968 gschem/src/o_net.c:1039
+#: gschem/src/o_net.c:1075
#, c-format
msgid "Tried to add more than two bus rippers. Internal gschem error.\n"
msgstr ""
-#: gschem/src/o_net.c:1144
+#: gschem/src/o_net.c:1143
#, c-format
msgid "Bus ripper symbol [%s] was not found in any component library\n"
msgstr ""
-#: gschem/src/o_path.c:352
+#: gschem/src/o_path.c:348
#, c-format
msgid "Unknown type for path (fill)!\n"
msgstr ""
-#: gschem/src/o_picture.c:163 gschem/src/o_picture.c:539
+#: gschem/src/o_picture.c:163 gschem/src/o_picture.c:537
#, c-format
msgid "Failed to load picture: %s"
msgstr "ç?¡æ³?è®?å??å??ç??: %s"
@@ -816,7 +802,7 @@ msgstr "ç?¡æ³?è®?å??å??ç??: %s"
msgid "Picture"
msgstr "å??ç??"
-#: gschem/src/o_picture.c:447 gschem/src/x_attribedit.c:141
+#: gschem/src/o_picture.c:445 gschem/src/x_attribedit.c:141
#, c-format
msgid "ERROR: NULL object!\n"
msgstr ""
@@ -837,23 +823,45 @@ msgstr ""
msgid "New slot number out of range\n"
msgstr ""
-#: gschem/src/o_undo.c:304
+#: gschem/src/o_undo.c:303
msgid "Undo/Redo disabled in rc file\n"
msgstr ""
-#: gschem/src/parsecmd.c:47
+#: gschem/src/parsecmd.c:81
#, c-format
msgid ""
-"Usage: %s [OPTIONS] schematic_filename1 ... schematic_filenameN\n"
-" -q Quiet mode\n"
-" -v Verbose mode on\n"
-" -r filename Rc filename\n"
-" -s filename Script (guile) filename\n"
-" -o filename Output filename (for printing)\n"
-" -p Automatically place the window\n"
-" -t Print stroke information\n"
-" -h Help; this message\n"
+"Usage: %s [OPTION ...] [--] [FILE ...]\n"
+"\n"
+"Interactively edit gEDA schematics or symbols. If one or more FILEs\n"
+"are specified, open them for editing; otherwise, create a new, empty\n"
+"schematic.\n"
+"\n"
+"Options:\n"
+" -q, --quiet Quiet mode.\n"
+" -v, --verbose Verbose mode.\n"
+" -r, --config-file=FILE Additional configuration file to load.\n"
+" -L DIR Add DIR to Scheme search path.\n"
+" -c EXPR Scheme expression to run at startup.\n"
+" -s FILE Scheme script to run at startup.\n"
+" -o, --output=FILE Output filename (for printing).\n"
+" -p Automatically place the window.\n"
+" -V, --version Show version information.\n"
+" -h, --help Help; this message.\n"
+" -- Treat all remaining arguments as filenames.\n"
"\n"
+"Report bugs to <geda-bug@xxxxxxxx>\n"
+"gEDA/gaf homepage: <http://gpleda.org>\n"
+msgstr ""
+
+#: gschem/src/parsecmd.c:115
+#, c-format
+msgid ""
+"gEDA %s (g%.7s)\n"
+"Copyright (C) 1998-2011 gEDA developers\n"
+"This is free software, and you are welcome to redistribute it under\n"
+"certain conditions. For details, see the file `COPYING', which is\n"
+"included in the gEDA distribution.\n"
+"There is NO WARRANTY, to the extent permitted by law.\n"
msgstr ""
#: gschem/src/x_attribedit.c:127
@@ -865,56 +873,56 @@ msgstr ""
msgid "Single Attribute Editor"
msgstr ""
-#: gschem/src/x_attribedit.c:358
+#: gschem/src/x_attribedit.c:359
msgid "<b>Edit Attribute</b>"
msgstr "<b>編輯屬�</b>"
-#: gschem/src/x_attribedit.c:360
+#: gschem/src/x_attribedit.c:361
msgid "<b>Add Attribute</b>"
msgstr "<b>å¢?å? 屬æ?§</b>"
-#: gschem/src/x_attribedit.c:376 gschem/src/x_multiattrib.c:1916
+#: gschem/src/x_attribedit.c:377 gschem/src/x_multiattrib.c:1927
msgid "Name:"
msgstr "å??稱ï¼?"
-#: gschem/src/x_attribedit.c:393 gschem/src/x_multiattrib.c:1935
+#: gschem/src/x_attribedit.c:394 gschem/src/x_multiattrib.c:1946
msgid "Value:"
msgstr "���"
-#: gschem/src/x_attribedit.c:409 gschem/src/x_multiattrib.c:1978
+#: gschem/src/x_attribedit.c:410 gschem/src/x_multiattrib.c:1989
msgid "Visible"
msgstr ""
-#: gschem/src/x_attribedit.c:429
+#: gschem/src/x_attribedit.c:430
msgid "Show Value Only"
msgstr "å??顯示æ?¸å?¼"
-#: gschem/src/x_attribedit.c:431
+#: gschem/src/x_attribedit.c:432
msgid "Show Name Only"
msgstr "å??顯示å??稱"
-#: gschem/src/x_attribedit.c:433 gschem/src/x_multiattrib.c:1454
+#: gschem/src/x_attribedit.c:434 gschem/src/x_multiattrib.c:1466
msgid "Show Name & Value"
msgstr "顯示å??稱è??æ?¸å?¼"
-#: gschem/src/x_attribedit.c:440
+#: gschem/src/x_attribedit.c:441
msgid "<b>Attach Options</b>"
msgstr ""
-#: gschem/src/x_attribedit.c:455
+#: gschem/src/x_attribedit.c:456
msgid "All"
msgstr ""
-#: gschem/src/x_attribedit.c:463 gschem/src/x_compselect.c:896
-#: gschem/src/x_compselect.c:1010
+#: gschem/src/x_attribedit.c:464 gschem/src/x_compselect.c:904
+#: gschem/src/x_compselect.c:1018
msgid "Components"
msgstr "å??件"
-#: gschem/src/x_attribedit.c:471 gschem/src/x_window.c:365
+#: gschem/src/x_attribedit.c:472 gschem/src/x_window.c:365
msgid "Nets"
msgstr ""
-#: gschem/src/x_attribedit.c:479
+#: gschem/src/x_attribedit.c:480
msgid "Replace existing attributes"
msgstr ""
@@ -930,91 +938,91 @@ msgid ""
"duplicate slot may cause problems: [symbolname=%s, number=%d, slot=%d]\n"
msgstr ""
-#: gschem/src/x_autonumber.c:673
+#: gschem/src/x_autonumber.c:675
msgid "No searchstring given in autonumber text.\n"
msgstr ""
-#: gschem/src/x_autonumber.c:725
+#: gschem/src/x_autonumber.c:727
msgid "No '*' or '?' given at the end of the autonumber text.\n"
msgstr ""
-#: gschem/src/x_autonumber.c:860
+#: gschem/src/x_autonumber.c:862
msgid "Diagonal"
msgstr ""
-#: gschem/src/x_autonumber.c:861
+#: gschem/src/x_autonumber.c:863
msgid "Top to bottom"
msgstr ""
-#: gschem/src/x_autonumber.c:861
+#: gschem/src/x_autonumber.c:863
msgid "Bottom to top"
msgstr ""
-#: gschem/src/x_autonumber.c:862
+#: gschem/src/x_autonumber.c:864
msgid "Left to right"
msgstr ""
-#: gschem/src/x_autonumber.c:862
+#: gschem/src/x_autonumber.c:864
msgid "Right to left"
msgstr ""
-#: gschem/src/x_autonumber.c:863
+#: gschem/src/x_autonumber.c:865
msgid "File order"
msgstr ""
-#: gschem/src/x_autonumber.c:1199
+#: gschem/src/x_autonumber.c:1201
msgid "Autonumber text"
msgstr ""
-#: gschem/src/x_autonumber.c:1223
+#: gschem/src/x_autonumber.c:1225
msgid "<b>Scope</b>"
msgstr ""
-#: gschem/src/x_autonumber.c:1245
+#: gschem/src/x_autonumber.c:1247
msgid "Search for:"
msgstr ""
-#: gschem/src/x_autonumber.c:1259
+#: gschem/src/x_autonumber.c:1261
msgid "Autonumber text in:"
msgstr ""
-#: gschem/src/x_autonumber.c:1266
+#: gschem/src/x_autonumber.c:1268
msgid "Skip numbers found in:"
msgstr ""
-#: gschem/src/x_autonumber.c:1278 gschem/src/x_autonumber.c:1287
+#: gschem/src/x_autonumber.c:1280 gschem/src/x_autonumber.c:1289
msgid "Selected objects"
msgstr "é?¸æ??ç?©ä»¶"
-#: gschem/src/x_autonumber.c:1279 gschem/src/x_autonumber.c:1288
+#: gschem/src/x_autonumber.c:1281 gschem/src/x_autonumber.c:1290
msgid "Current page"
msgstr ""
-#: gschem/src/x_autonumber.c:1280 gschem/src/x_autonumber.c:1289
+#: gschem/src/x_autonumber.c:1282 gschem/src/x_autonumber.c:1291
msgid "Whole hierarchy"
msgstr ""
-#: gschem/src/x_autonumber.c:1291
+#: gschem/src/x_autonumber.c:1293
msgid "Overwrite existing numbers"
msgstr ""
-#: gschem/src/x_autonumber.c:1296
+#: gschem/src/x_autonumber.c:1298
msgid "<b>Options</b>"
msgstr "<b>é?¸é ?</b>"
-#: gschem/src/x_autonumber.c:1318
+#: gschem/src/x_autonumber.c:1320
msgid "Starting number:"
msgstr ""
-#: gschem/src/x_autonumber.c:1325
+#: gschem/src/x_autonumber.c:1327
msgid "Sort order:"
msgstr ""
-#: gschem/src/x_autonumber.c:1346
+#: gschem/src/x_autonumber.c:1348
msgid "Remove numbers"
msgstr ""
-#: gschem/src/x_autonumber.c:1350
+#: gschem/src/x_autonumber.c:1352
msgid "Automatic slotting"
msgstr ""
@@ -1051,48 +1059,48 @@ msgstr ""
msgid "Tried to get an invalid outline color: %d\n"
msgstr ""
-#: gschem/src/x_compselect.c:1040
+#: gschem/src/x_compselect.c:1048
msgid "Filter:"
msgstr ""
-#: gschem/src/x_compselect.c:1143 gschem/src/x_dialog.c:3663
-#: gschem/src/x_multiattrib.c:1782
+#: gschem/src/x_compselect.c:1151 gschem/src/x_dialog.c:3667
+#: gschem/src/x_multiattrib.c:1793
msgid "Name"
msgstr ""
-#: gschem/src/x_compselect.c:1152 gschem/src/x_multiattrib.c:1806
+#: gschem/src/x_compselect.c:1160 gschem/src/x_multiattrib.c:1817
msgid "Value"
msgstr ""
-#: gschem/src/x_compselect.c:1191
+#: gschem/src/x_compselect.c:1199
msgid "Default behavior - reference component"
msgstr ""
-#: gschem/src/x_compselect.c:1194
+#: gschem/src/x_compselect.c:1202
msgid "Embed component in schematic"
msgstr ""
-#: gschem/src/x_compselect.c:1197
+#: gschem/src/x_compselect.c:1205
msgid "Include component as individual objects"
msgstr ""
-#: gschem/src/x_compselect.c:1354
+#: gschem/src/x_compselect.c:1362
msgid "Select Component..."
msgstr ""
-#: gschem/src/x_compselect.c:1377
+#: gschem/src/x_compselect.c:1385
msgid "In Use"
msgstr ""
-#: gschem/src/x_compselect.c:1381
+#: gschem/src/x_compselect.c:1389
msgid "Libraries"
msgstr ""
-#: gschem/src/x_compselect.c:1390 gschem/src/x_fileselect.c:122
+#: gschem/src/x_compselect.c:1398 gschem/src/x_fileselect.c:122
msgid "Preview"
msgstr "é ?覽"
-#: gschem/src/x_compselect.c:1418
+#: gschem/src/x_compselect.c:1426
msgid "Attributes"
msgstr "屬�"
@@ -1147,336 +1155,336 @@ msgstr ""
msgid "Edit Text Properties"
msgstr ""
-#: gschem/src/x_dialog.c:471
+#: gschem/src/x_dialog.c:472
msgid "<b>Text Content</b>"
msgstr ""
-#: gschem/src/x_dialog.c:507
+#: gschem/src/x_dialog.c:508
msgid "<b>Text Properties</b>"
msgstr ""
-#: gschem/src/x_dialog.c:522
+#: gschem/src/x_dialog.c:523
msgid "Color:"
msgstr ""
-#: gschem/src/x_dialog.c:529
+#: gschem/src/x_dialog.c:530
msgid "Size:"
msgstr ""
-#: gschem/src/x_dialog.c:538
+#: gschem/src/x_dialog.c:539
msgid "Alignment:"
msgstr ""
-#: gschem/src/x_dialog.c:587
+#: gschem/src/x_dialog.c:588
msgid "Solid"
msgstr ""
-#: gschem/src/x_dialog.c:588
+#: gschem/src/x_dialog.c:589
msgid "Dotted"
msgstr ""
-#: gschem/src/x_dialog.c:589
+#: gschem/src/x_dialog.c:590
msgid "Dashed"
msgstr ""
-#: gschem/src/x_dialog.c:590
+#: gschem/src/x_dialog.c:591
msgid "Center"
msgstr ""
-#: gschem/src/x_dialog.c:591
+#: gschem/src/x_dialog.c:592
msgid "Phantom"
msgstr ""
-#: gschem/src/x_dialog.c:592 gschem/src/x_dialog.c:689
-#: gschem/src/x_dialog.c:698 gschem/src/x_dialog.c:707
-#: gschem/src/x_dialog.c:808 gschem/src/x_dialog.c:810
-#: gschem/src/x_dialog.c:812 gschem/src/x_dialog.c:1038
-#: gschem/src/x_dialog.c:1141 gschem/src/x_dialog.c:1150
-#: gschem/src/x_dialog.c:1159 gschem/src/x_dialog.c:1168
-#: gschem/src/x_dialog.c:1177 gschem/src/x_dialog.c:1290
-#: gschem/src/x_dialog.c:1292 gschem/src/x_dialog.c:1294
-#: gschem/src/x_dialog.c:1296 gschem/src/x_dialog.c:1298
+#: gschem/src/x_dialog.c:593 gschem/src/x_dialog.c:690
+#: gschem/src/x_dialog.c:699 gschem/src/x_dialog.c:708
+#: gschem/src/x_dialog.c:809 gschem/src/x_dialog.c:811
+#: gschem/src/x_dialog.c:813 gschem/src/x_dialog.c:1039
+#: gschem/src/x_dialog.c:1142 gschem/src/x_dialog.c:1151
+#: gschem/src/x_dialog.c:1160 gschem/src/x_dialog.c:1169
+#: gschem/src/x_dialog.c:1178 gschem/src/x_dialog.c:1291
+#: gschem/src/x_dialog.c:1293 gschem/src/x_dialog.c:1295
+#: gschem/src/x_dialog.c:1297 gschem/src/x_dialog.c:1299
msgid "*unchanged*"
msgstr ""
-#: gschem/src/x_dialog.c:916
+#: gschem/src/x_dialog.c:917
msgid "Edit Line Width & Type"
msgstr ""
-#: gschem/src/x_dialog.c:955 gschem/src/x_print.c:307
+#: gschem/src/x_dialog.c:956 gschem/src/x_print.c:307
msgid "Type:"
msgstr ""
-#: gschem/src/x_dialog.c:959
+#: gschem/src/x_dialog.c:960
msgid "Width:"
msgstr ""
-#: gschem/src/x_dialog.c:963
+#: gschem/src/x_dialog.c:964
msgid "Dash Length:"
msgstr ""
-#: gschem/src/x_dialog.c:967
+#: gschem/src/x_dialog.c:968
msgid "Dash Space:"
msgstr ""
-#: gschem/src/x_dialog.c:1034
+#: gschem/src/x_dialog.c:1035
msgid "Hollow"
msgstr ""
-#: gschem/src/x_dialog.c:1035
+#: gschem/src/x_dialog.c:1036
msgid "Filled"
msgstr ""
-#: gschem/src/x_dialog.c:1036
+#: gschem/src/x_dialog.c:1037
msgid "Mesh"
msgstr ""
-#: gschem/src/x_dialog.c:1037
+#: gschem/src/x_dialog.c:1038
msgid "Hatch"
msgstr ""
-#: gschem/src/x_dialog.c:1406
+#: gschem/src/x_dialog.c:1407
msgid "Edit Fill Type"
msgstr ""
-#: gschem/src/x_dialog.c:1444
+#: gschem/src/x_dialog.c:1446
msgid "Fill Type:"
msgstr ""
-#: gschem/src/x_dialog.c:1448
+#: gschem/src/x_dialog.c:1450
msgid "Line Width:"
msgstr ""
-#: gschem/src/x_dialog.c:1452
+#: gschem/src/x_dialog.c:1454
msgid "Angle 1:"
msgstr ""
-#: gschem/src/x_dialog.c:1456
+#: gschem/src/x_dialog.c:1458
msgid "Pitch 1:"
msgstr ""
-#: gschem/src/x_dialog.c:1460
+#: gschem/src/x_dialog.c:1462
msgid "Angle 2:"
msgstr ""
-#: gschem/src/x_dialog.c:1464
+#: gschem/src/x_dialog.c:1466
msgid "Pitch 2:"
msgstr ""
-#: gschem/src/x_dialog.c:1591
+#: gschem/src/x_dialog.c:1593
msgid "Arc Params"
msgstr ""
-#: gschem/src/x_dialog.c:1631
+#: gschem/src/x_dialog.c:1634
msgid "Arc Radius:"
msgstr ""
-#: gschem/src/x_dialog.c:1639
+#: gschem/src/x_dialog.c:1642
msgid "Start Angle:"
msgstr ""
-#: gschem/src/x_dialog.c:1647
+#: gschem/src/x_dialog.c:1650
msgid "Degrees of Sweep:"
msgstr ""
-#: gschem/src/x_dialog.c:1764
+#: gschem/src/x_dialog.c:1768
msgid ""
"Offset to translate?\n"
"(0 for origin)"
msgstr ""
-#: gschem/src/x_dialog.c:1832
+#: gschem/src/x_dialog.c:1836
msgid "Text Size"
msgstr ""
-#: gschem/src/x_dialog.c:1862
+#: gschem/src/x_dialog.c:1866
msgid "Enter new text size:"
msgstr ""
-#: gschem/src/x_dialog.c:1938
+#: gschem/src/x_dialog.c:1942
msgid "Snap Size"
msgstr ""
-#: gschem/src/x_dialog.c:1968
+#: gschem/src/x_dialog.c:1972
msgid "Enter new snap grid spacing:"
msgstr ""
-#: gschem/src/x_dialog.c:2045
+#: gschem/src/x_dialog.c:2049
msgid "Edit slot number"
msgstr ""
-#: gschem/src/x_dialog.c:2076
+#: gschem/src/x_dialog.c:2080
msgid "Edit slot number:"
msgstr ""
-#: gschem/src/x_dialog.c:2117
+#: gschem/src/x_dialog.c:2121
#, c-format
msgid "%s%s (%s)"
msgstr ""
-#: gschem/src/x_dialog.c:2140
+#: gschem/src/x_dialog.c:2144
msgid "About gschem"
msgstr "é??æ?¼ gschem"
-#: gschem/src/x_dialog.c:2141
+#: gschem/src/x_dialog.c:2145
msgid "gEDA: GPL Electronic Design Automation"
msgstr ""
-#: gschem/src/x_dialog.c:2142
+#: gschem/src/x_dialog.c:2146
msgid ""
"Copyright © 1998-2009 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>\n"
"Copyright © 1998-2009 gEDA Contributors (see ChangeLog for details)"
msgstr ""
-#: gschem/src/x_dialog.c:2201
+#: gschem/src/x_dialog.c:2205
msgid "Coords"
msgstr ""
-#: gschem/src/x_dialog.c:2222
+#: gschem/src/x_dialog.c:2226
msgid "Screen"
msgstr ""
-#: gschem/src/x_dialog.c:2231
+#: gschem/src/x_dialog.c:2235
msgid "World"
msgstr ""
-#: gschem/src/x_dialog.c:2270
+#: gschem/src/x_dialog.c:2274
msgid "Background"
msgstr ""
-#: gschem/src/x_dialog.c:2276
+#: gschem/src/x_dialog.c:2280
msgid "Net endpoint"
msgstr ""
-#: gschem/src/x_dialog.c:2279
+#: gschem/src/x_dialog.c:2283
msgid "Graphic"
msgstr ""
-#: gschem/src/x_dialog.c:2288
+#: gschem/src/x_dialog.c:2292
msgid "Logic bubble"
msgstr ""
-#: gschem/src/x_dialog.c:2291
+#: gschem/src/x_dialog.c:2295
msgid "Grid point"
msgstr ""
-#: gschem/src/x_dialog.c:2294
+#: gschem/src/x_dialog.c:2298
msgid "Detached attribute"
msgstr ""
-#: gschem/src/x_dialog.c:2297 gschem/src/x_window.c:383
+#: gschem/src/x_dialog.c:2301 gschem/src/x_window.c:383
msgid "Text"
msgstr ""
-#: gschem/src/x_dialog.c:2303
+#: gschem/src/x_dialog.c:2307
msgid "Selection"
msgstr ""
-#: gschem/src/x_dialog.c:2306
+#: gschem/src/x_dialog.c:2310
msgid "Bounding box"
msgstr ""
-#: gschem/src/x_dialog.c:2309
+#: gschem/src/x_dialog.c:2313
msgid "Zoom box"
msgstr ""
-#: gschem/src/x_dialog.c:2318
+#: gschem/src/x_dialog.c:2322
msgid "Output background"
msgstr ""
-#: gschem/src/x_dialog.c:2321
+#: gschem/src/x_dialog.c:2325
msgid "Net junction"
msgstr ""
-#: gschem/src/x_dialog.c:2324
+#: gschem/src/x_dialog.c:2328
msgid "Mesh grid major"
msgstr ""
-#: gschem/src/x_dialog.c:2327
+#: gschem/src/x_dialog.c:2331
msgid "Mesh grid minor"
msgstr ""
-#: gschem/src/x_dialog.c:2330
+#: gschem/src/x_dialog.c:2334
msgid "Unknown"
msgstr ""
-#: gschem/src/x_dialog.c:2481
+#: gschem/src/x_dialog.c:2485
#, c-format
msgid "ERROR: NULL object in color_edit_dialog_apply!\n"
msgstr ""
-#: gschem/src/x_dialog.c:2525
+#: gschem/src/x_dialog.c:2529
msgid "Color Edit"
msgstr ""
-#: gschem/src/x_dialog.c:2556
+#: gschem/src/x_dialog.c:2560
msgid "Object color:"
msgstr ""
-#: gschem/src/x_dialog.c:2614
+#: gschem/src/x_dialog.c:2618
msgid "Hotkeys"
msgstr "��"
-#: gschem/src/x_dialog.c:2678
+#: gschem/src/x_dialog.c:2682
msgid "Function"
msgstr ""
-#: gschem/src/x_dialog.c:2685
+#: gschem/src/x_dialog.c:2689
msgid "Keystroke(s)"
msgstr ""
-#: gschem/src/x_dialog.c:2991
+#: gschem/src/x_dialog.c:2995
msgid "Find Text"
msgstr ""
-#: gschem/src/x_dialog.c:3022
+#: gschem/src/x_dialog.c:3026
msgid "Text to find:"
msgstr ""
-#: gschem/src/x_dialog.c:3032
+#: gschem/src/x_dialog.c:3036
msgid "descend into hierarchy"
msgstr ""
-#: gschem/src/x_dialog.c:3097
+#: gschem/src/x_dialog.c:3101
msgid "Hide Text"
msgstr ""
-#: gschem/src/x_dialog.c:3128
+#: gschem/src/x_dialog.c:3132
msgid "Hide text starting with:"
msgstr ""
-#: gschem/src/x_dialog.c:3197
+#: gschem/src/x_dialog.c:3201
msgid "Show Text"
msgstr ""
-#: gschem/src/x_dialog.c:3228
+#: gschem/src/x_dialog.c:3232
msgid "Show text starting with:"
msgstr ""
-#: gschem/src/x_dialog.c:3685
+#: gschem/src/x_dialog.c:3689
msgid "S_elect the schematics you want to save:"
msgstr ""
-#: gschem/src/x_dialog.c:3779
+#: gschem/src/x_dialog.c:3784
#, c-format
msgid "Save the changes to schematic \"%s\" before closing?"
msgstr ""
-#: gschem/src/x_dialog.c:3785
+#: gschem/src/x_dialog.c:3790
#, c-format
msgid ""
"There are %d schematics with unsaved changes. Save changes before closing?"
msgstr ""
-#: gschem/src/x_dialog.c:3814
+#: gschem/src/x_dialog.c:3819
msgid "If you don't save, all your changes will be permanently lost."
msgstr ""
-#: gschem/src/x_dialog.c:3834
+#: gschem/src/x_dialog.c:3839
msgid "_Close without saving"
msgstr ""
-#: gschem/src/x_dialog.c:4170
+#: gschem/src/x_dialog.c:4175
#, c-format
msgid ""
"<span weight=\"bold\" size=\"larger\">The input attribute \"%s\" is invalid\n"
@@ -1487,19 +1495,19 @@ msgid ""
"The value cannot start with a space."
msgstr ""
-#: gschem/src/x_dialog.c:4172
+#: gschem/src/x_dialog.c:4177
msgid "Invalid Attribute"
msgstr ""
-#: gschem/src/x_dialog.c:4208
+#: gschem/src/x_dialog.c:4213
msgid "Pin type"
msgstr ""
-#: gschem/src/x_dialog.c:4232
+#: gschem/src/x_dialog.c:4237
msgid "Net pin"
msgstr ""
-#: gschem/src/x_dialog.c:4234
+#: gschem/src/x_dialog.c:4239
msgid "Bus pin (graphical)"
msgstr ""
@@ -1592,11 +1600,11 @@ msgstr "å??ç??æ ¼å¼?"
msgid "Write image..."
msgstr "å?¯å?ºæ??å??ç??"
-#: gschem/src/x_log.c:188
+#: gschem/src/x_log.c:209
msgid "** Invalid UTF-8 in log message. See stderr or gschem.log.\n"
msgstr ""
-#: gschem/src/x_log.c:256
+#: gschem/src/x_log.c:288
msgid "Status"
msgstr ""
@@ -1672,69 +1680,60 @@ msgstr ""
msgid "/Up"
msgstr ""
-#: gschem/src/x_menus.c:321
+#: gschem/src/x_menus.c:323
#, c-format
msgid "Tried to set the sensitivity on non-existent menu item '%s'\n"
msgstr ""
-#: gschem/src/x_menus.c:345
+#: gschem/src/x_menus.c:347
msgid "Popup_menu_item_factory doesn't exist!\n"
msgstr ""
-#: gschem/src/x_menus.c:358
+#: gschem/src/x_menus.c:360
msgid "Tried to set the sensitivity on a non-existent popup menu_item\n"
msgstr ""
-#: gschem/src/x_menus.c:438
-#, c-format
-msgid "Couldn't open file %s\n"
-msgstr ""
-
-#: gschem/src/x_menus.c:495
-msgid "Clear"
-msgstr ""
-
-#: gschem/src/x_multiattrib.c:911
+#: gschem/src/x_multiattrib.c:915
msgid "Attributes with empty name are not allowed. Please set a name."
msgstr ""
-#: gschem/src/x_multiattrib.c:1456
+#: gschem/src/x_multiattrib.c:1468
msgid "Show Value only"
msgstr ""
-#: gschem/src/x_multiattrib.c:1458
+#: gschem/src/x_multiattrib.c:1470
msgid "Show Name only"
msgstr ""
-#: gschem/src/x_multiattrib.c:1486
+#: gschem/src/x_multiattrib.c:1498
msgid "Promote"
msgstr ""
-#: gschem/src/x_multiattrib.c:1490
+#: gschem/src/x_multiattrib.c:1502
msgid "Duplicate"
msgstr ""
-#: gschem/src/x_multiattrib.c:1708
+#: gschem/src/x_multiattrib.c:1719
msgid "Edit Attributes"
msgstr ""
-#: gschem/src/x_multiattrib.c:1826
+#: gschem/src/x_multiattrib.c:1837
msgid "Vis?"
msgstr ""
-#: gschem/src/x_multiattrib.c:1844
+#: gschem/src/x_multiattrib.c:1855
msgid "N"
msgstr ""
-#: gschem/src/x_multiattrib.c:1862
+#: gschem/src/x_multiattrib.c:1873
msgid "V"
msgstr ""
-#: gschem/src/x_multiattrib.c:1884
+#: gschem/src/x_multiattrib.c:1895
msgid "Show inherited attributes"
msgstr ""
-#: gschem/src/x_multiattrib.c:1900
+#: gschem/src/x_multiattrib.c:1911
msgid "Add Attribute"
msgstr ""
@@ -1758,23 +1757,23 @@ msgstr "é??é??æª?æ¡?"
msgid "Discard Page"
msgstr ""
-#: gschem/src/x_pagesel.c:376
+#: gschem/src/x_pagesel.c:375
msgid "Page Manager"
msgstr ""
-#: gschem/src/x_pagesel.c:432
+#: gschem/src/x_pagesel.c:431
msgid "Filename"
msgstr ""
-#: gschem/src/x_pagesel.c:448
+#: gschem/src/x_pagesel.c:447
msgid "Changed"
msgstr ""
-#: gschem/src/x_pagesel.c:468
+#: gschem/src/x_pagesel.c:467
msgid "Right click on the filename for more options..."
msgstr ""
-#: gschem/src/x_preview.c:234
+#: gschem/src/x_preview.c:233
msgid "Preview Buffer"
msgstr ""
@@ -1830,23 +1829,23 @@ msgstr ""
msgid "Command:"
msgstr ""
-#: gschem/src/x_print.c:741
+#: gschem/src/x_print.c:745
msgid "No print destination specified\n"
msgstr ""
-#: gschem/src/x_print.c:748
+#: gschem/src/x_print.c:752
#, c-format
msgid "Cannot print current schematic to [%s]\n"
msgstr ""
-#: gschem/src/x_print.c:757
+#: gschem/src/x_print.c:761
#, c-format
msgid ""
"Error printing to file '%s'\n"
"Check the log window for more information"
msgstr ""
-#: gschem/src/x_print.c:764
+#: gschem/src/x_print.c:768
#, c-format
msgid "Printed current schematic to [%s]\n"
msgstr ""
@@ -1855,6 +1854,11 @@ msgstr ""
msgid "Execute Script..."
msgstr "����"
+#: gschem/src/x_script.c:66
+#, c-format
+msgid "Executing guile script [%s]\n"
+msgstr "æ£å?¨å?·è¡?guileè?³æ?¬ [%s]\n"
+
#: gschem/src/x_window.c:81
#, c-format
msgid "Couldn't allocate gc\n"
@@ -1962,35 +1966,35 @@ msgstr "ç?¡æ³?è®?å??æª?æ¡?"
msgid "New file [%s]\n"
msgstr ""
-#: gschem/src/x_window.c:857
+#: gschem/src/x_window.c:855
#, c-format
msgid "Could NOT save page [%s]\n"
msgstr ""
-#: gschem/src/x_window.c:858
+#: gschem/src/x_window.c:856
msgid "Error while trying to save"
msgstr "æ?¼å?²å?æª?æ¡?æ??ç?¼ç??é?¯èª¤"
-#: gschem/src/x_window.c:867
+#: gschem/src/x_window.c:865
#, c-format
msgid "Saved as [%s]\n"
msgstr "å?¦å?ç?º [%s]\n"
-#: gschem/src/x_window.c:869
+#: gschem/src/x_window.c:867
#, c-format
msgid "Saved [%s]\n"
msgstr "å?²å? [%s]\n"
-#: gschem/src/x_window.c:871
+#: gschem/src/x_window.c:869
msgid "Saved"
msgstr "å?²å?"
-#: gschem/src/x_window.c:945
+#: gschem/src/x_window.c:943
#, c-format
msgid "Discarding page [%s]\n"
msgstr ""
-#: gschem/src/x_window.c:945
+#: gschem/src/x_window.c:943
#, c-format
msgid "Closing [%s]\n"
msgstr "é??é?? [%s]\n"
@@ -2031,7 +2035,7 @@ msgstr ""
msgid "Save All"
msgstr "å?¨é?¨å?²å?"
-#: gschem/lib/system-gschemrc.scm:1386 gschem/lib/system-gschemrc.scm:1477
+#: gschem/lib/system-gschemrc.scm:1386 gschem/lib/system-gschemrc.scm:1478
msgid "_Revert"
msgstr ""
@@ -2043,7 +2047,7 @@ msgstr ""
msgid "Write _image..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1393 gschem/lib/system-gschemrc.scm:1478
+#: gschem/lib/system-gschemrc.scm:1393 gschem/lib/system-gschemrc.scm:1479
msgid "_Close"
msgstr ""
@@ -2075,387 +2079,393 @@ msgstr ""
msgid "_Delete"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1412
+#: gschem/lib/system-gschemrc.scm:1409
+#, fuzzy
+msgid "Select All"
+msgstr "é?¸æ??"
+
+#: gschem/lib/system-gschemrc.scm:1410
+#, fuzzy
+msgid "Deselect"
+msgstr "é?¸æ??"
+
+#: gschem/lib/system-gschemrc.scm:1414
msgid "Rotate 90 Mode"
msgstr "é??æ??é??æ??è½?90度"
-#: gschem/lib/system-gschemrc.scm:1415
+#: gschem/lib/system-gschemrc.scm:1417
msgid "Edit..."
msgstr "編輯"
-#: gschem/lib/system-gschemrc.scm:1416
+#: gschem/lib/system-gschemrc.scm:1418
msgid "Edit Text..."
msgstr "編輯æ??å?"
-#: gschem/lib/system-gschemrc.scm:1417
+#: gschem/lib/system-gschemrc.scm:1419
msgid "Slot..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1418
+#: gschem/lib/system-gschemrc.scm:1420
msgid "Color..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1419
+#: gschem/lib/system-gschemrc.scm:1421
msgid "Line Width & Type..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1420
+#: gschem/lib/system-gschemrc.scm:1422
msgid "Fill Type..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1421
+#: gschem/lib/system-gschemrc.scm:1423
msgid "Symbol Translate..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1425
+#: gschem/lib/system-gschemrc.scm:1427
msgid "Invoke Macro"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1426
+#: gschem/lib/system-gschemrc.scm:1428
msgid "Embed Component/Picture"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1427
+#: gschem/lib/system-gschemrc.scm:1429
msgid "Unembed Component/Picture"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1428
+#: gschem/lib/system-gschemrc.scm:1430
msgid "Update Component"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1429
+#: gschem/lib/system-gschemrc.scm:1431
msgid "Show/Hide Inv Text"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1430
-msgid "Make Inv Text Vis"
-msgstr ""
-
-#: gschem/lib/system-gschemrc.scm:1436
+#: gschem/lib/system-gschemrc.scm:1437
msgid "Copy into 1"
msgstr "�製� 1"
-#: gschem/lib/system-gschemrc.scm:1437
+#: gschem/lib/system-gschemrc.scm:1438
msgid "Copy into 2"
msgstr "�製� 2"
-#: gschem/lib/system-gschemrc.scm:1438
+#: gschem/lib/system-gschemrc.scm:1439
msgid "Copy into 3"
msgstr "�製� 3"
-#: gschem/lib/system-gschemrc.scm:1439
+#: gschem/lib/system-gschemrc.scm:1440
msgid "Copy into 4"
msgstr "�製� 4"
-#: gschem/lib/system-gschemrc.scm:1440
+#: gschem/lib/system-gschemrc.scm:1441
msgid "Copy into 5"
msgstr "�製� 5"
-#: gschem/lib/system-gschemrc.scm:1441
+#: gschem/lib/system-gschemrc.scm:1442
msgid "Cut into 1"
msgstr "å?ªä¸?è?³ ç·©è¡?å??1"
-#: gschem/lib/system-gschemrc.scm:1442
+#: gschem/lib/system-gschemrc.scm:1443
msgid "Cut into 2"
msgstr "å?ªä¸?è?³ ç·©è¡?å??2"
-#: gschem/lib/system-gschemrc.scm:1443
+#: gschem/lib/system-gschemrc.scm:1444
msgid "Cut into 3"
msgstr "å?ªä¸?è?³ ç·©è¡?å??3"
-#: gschem/lib/system-gschemrc.scm:1444
+#: gschem/lib/system-gschemrc.scm:1445
msgid "Cut into 4"
msgstr "å?ªä¸?è?³ ç·©è¡?å??4"
-#: gschem/lib/system-gschemrc.scm:1445
+#: gschem/lib/system-gschemrc.scm:1446
msgid "Cut into 5"
msgstr "å?ªä¸?è?³ ç·©è¡?å??5"
-#: gschem/lib/system-gschemrc.scm:1446
+#: gschem/lib/system-gschemrc.scm:1447
msgid "Paste from 1"
msgstr "è?ª ç·©è¡?å??1 è²¼ä¸?"
-#: gschem/lib/system-gschemrc.scm:1447
+#: gschem/lib/system-gschemrc.scm:1448
msgid "Paste from 2"
msgstr "è?ª ç·©è¡?å??2 è²¼ä¸?"
-#: gschem/lib/system-gschemrc.scm:1448
+#: gschem/lib/system-gschemrc.scm:1449
msgid "Paste from 3"
msgstr "è?ª ç·©è¡?å??3 è²¼ä¸?"
-#: gschem/lib/system-gschemrc.scm:1449
+#: gschem/lib/system-gschemrc.scm:1450
msgid "Paste from 4"
msgstr "è?ª ç·©è¡?å??4 è²¼ä¸?"
-#: gschem/lib/system-gschemrc.scm:1450
+#: gschem/lib/system-gschemrc.scm:1451
msgid "Paste from 5"
msgstr "è?ª ç·©è¡?å??5 è²¼ä¸?"
-#: gschem/lib/system-gschemrc.scm:1456
+#: gschem/lib/system-gschemrc.scm:1457
msgid "_Redraw"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1457
+#: gschem/lib/system-gschemrc.scm:1458
msgid "_Pan"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1458
+#: gschem/lib/system-gschemrc.scm:1459
msgid "Zoom _Box"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1459
+#: gschem/lib/system-gschemrc.scm:1460
msgid "Zoom _Extents"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1460
+#: gschem/lib/system-gschemrc.scm:1461
msgid "Zoom _In"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1461
+#: gschem/lib/system-gschemrc.scm:1462
msgid "Zoom _Out"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1462
+#: gschem/lib/system-gschemrc.scm:1463
msgid "Zoom _Full"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1464
+#: gschem/lib/system-gschemrc.scm:1465
msgid "_Dark color scheme"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1465
+#: gschem/lib/system-gschemrc.scm:1466
msgid "_Light color scheme"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1466
+#: gschem/lib/system-gschemrc.scm:1467
msgid "B_W color scheme"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1473
+#: gschem/lib/system-gschemrc.scm:1474
msgid "_Manager..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1474
+#: gschem/lib/system-gschemrc.scm:1475
msgid "_Previous"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1475
+#: gschem/lib/system-gschemrc.scm:1476
msgid "_Next"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1476
+#: gschem/lib/system-gschemrc.scm:1477
msgid "Ne_w"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1480
+#: gschem/lib/system-gschemrc.scm:1481
msgid "_Discard"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1486
+#: gschem/lib/system-gschemrc.scm:1487
msgid "_Component..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1487
+#: gschem/lib/system-gschemrc.scm:1488
msgid "_Net"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1488
+#: gschem/lib/system-gschemrc.scm:1489
msgid "B_us"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1489
+#: gschem/lib/system-gschemrc.scm:1490
msgid "_Attribute..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1490
+#: gschem/lib/system-gschemrc.scm:1491
msgid "_Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1492
+#: gschem/lib/system-gschemrc.scm:1493
msgid "_Line"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1493
+#: gschem/lib/system-gschemrc.scm:1494
msgid "_Box"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1494
+#: gschem/lib/system-gschemrc.scm:1495
msgid "C_ircle"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1495
+#: gschem/lib/system-gschemrc.scm:1496
msgid "A_rc"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1496
+#: gschem/lib/system-gschemrc.scm:1497
msgid "_Pin"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1497
+#: gschem/lib/system-gschemrc.scm:1498
msgid "Pictu_re..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1503
+#: gschem/lib/system-gschemrc.scm:1504
msgid "_Down Schematic"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1504
+#: gschem/lib/system-gschemrc.scm:1505
msgid "Down _Symbol"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1505
+#: gschem/lib/system-gschemrc.scm:1506
msgid "_Up"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1506
+#: gschem/lib/system-gschemrc.scm:1507
msgid "D_ocumentation..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1512
+#: gschem/lib/system-gschemrc.scm:1513
msgid "_Attach"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1513
+#: gschem/lib/system-gschemrc.scm:1514
msgid "_Detach"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1514
+#: gschem/lib/system-gschemrc.scm:1515
msgid "Show _Value"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1515
+#: gschem/lib/system-gschemrc.scm:1516
msgid "Show _Name"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1516
+#: gschem/lib/system-gschemrc.scm:1517
msgid "Show _Both"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1517
+#: gschem/lib/system-gschemrc.scm:1518
msgid "_Toggle Visibility"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1519
+#: gschem/lib/system-gschemrc.scm:1520
msgid "_Find Specific Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1520
+#: gschem/lib/system-gschemrc.scm:1521
msgid "_Hide Specific Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1521
+#: gschem/lib/system-gschemrc.scm:1522
msgid "_Show Specific Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1522
+#: gschem/lib/system-gschemrc.scm:1523
msgid "A_utonumber Text..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1528
+#: gschem/lib/system-gschemrc.scm:1529
msgid "_Text Size..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1529
+#: gschem/lib/system-gschemrc.scm:1530
msgid "Cycle _grid styles"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1530
+#: gschem/lib/system-gschemrc.scm:1531
msgid "Toggle _Snap On/Off"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1531
+#: gschem/lib/system-gschemrc.scm:1532
msgid "Snap Grid S_pacing..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1532
+#: gschem/lib/system-gschemrc.scm:1533
msgid "Scale _up Grid Spacing"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1534
+#: gschem/lib/system-gschemrc.scm:1535
msgid "Scale _down Grid Spacing"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1536
+#: gschem/lib/system-gschemrc.scm:1537
msgid "Toggle _Outline/Box"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1538
+#: gschem/lib/system-gschemrc.scm:1539
msgid "Toggle Net _Rubberband"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1539
+#: gschem/lib/system-gschemrc.scm:1540
msgid "Toggle _Magnetic Net"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1540
+#: gschem/lib/system-gschemrc.scm:1541
msgid "Show _Log Window..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1542
+#: gschem/lib/system-gschemrc.scm:1543
msgid "Show _Coord Window..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1558
+#: gschem/lib/system-gschemrc.scm:1559
msgid "gEDA Docu_mentation..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1559
+#: gschem/lib/system-gschemrc.scm:1560
msgid "gschem _FAQ..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1560
+#: gschem/lib/system-gschemrc.scm:1561
msgid "gEDA _Wiki..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1561
+#: gschem/lib/system-gschemrc.scm:1562
msgid "Component D_ocumentation..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1563
+#: gschem/lib/system-gschemrc.scm:1564
msgid "_Hotkeys..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1564
+#: gschem/lib/system-gschemrc.scm:1565
msgid "_About..."
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1570
+#: gschem/lib/system-gschemrc.scm:1571
msgid "_File"
msgstr "��"
-#: gschem/lib/system-gschemrc.scm:1571
+#: gschem/lib/system-gschemrc.scm:1572
msgid "_Edit"
msgstr "編輯"
-#: gschem/lib/system-gschemrc.scm:1572
+#: gschem/lib/system-gschemrc.scm:1573
msgid "_Buffer"
msgstr "ç·©è¡?å??"
-#: gschem/lib/system-gschemrc.scm:1573
+#: gschem/lib/system-gschemrc.scm:1574
msgid "_View"
msgstr "顯示"
-#: gschem/lib/system-gschemrc.scm:1574
+#: gschem/lib/system-gschemrc.scm:1575
msgid "_Page"
msgstr "å??é ?"
-#: gschem/lib/system-gschemrc.scm:1575
+#: gschem/lib/system-gschemrc.scm:1576
msgid "_Add"
msgstr "��"
-#: gschem/lib/system-gschemrc.scm:1576
+#: gschem/lib/system-gschemrc.scm:1577
msgid "Hie_rarchy"
msgstr ""
-#: gschem/lib/system-gschemrc.scm:1577
+#: gschem/lib/system-gschemrc.scm:1578
msgid "A_ttributes"
msgstr "屬�"
-#: gschem/lib/system-gschemrc.scm:1578
+#: gschem/lib/system-gschemrc.scm:1579
msgid "_Options"
msgstr "é?¸é ?"
-#: gschem/lib/system-gschemrc.scm:1579
+#: gschem/lib/system-gschemrc.scm:1580
msgid "_Help"
msgstr "幫�"
diff --git a/libgeda/po/ar.po b/libgeda/po/ar.po
index 8741629..d060821 100644
--- a/libgeda/po/ar.po
+++ b/libgeda/po/ar.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2010-11-07 10:51+0000\n"
+"POT-Creation-Date: 2011-01-15 23:36-0500\n"
"PO-Revision-Date: 2010-02-06 22:09+0000\n"
"Last-Translator: عبداÙ?Ù?Ù? Ø´Ù?Ù? (Abdellah Chelli) <Unknown>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -42,12 +42,12 @@ msgstr "Ù?خطط دارة gEDA"
msgid "gEDA Schematic Symbol"
msgstr "رÙ?ز Ù?خطط gEDA"
-#: libgeda/src/a_basic.c:181
+#: libgeda/src/a_basic.c:182
#, c-format
msgid "o_save_objects: object %p has unknown type '%c'\n"
msgstr ""
-#: libgeda/src/a_basic.c:429
+#: libgeda/src/a_basic.c:417
#, c-format
msgid ""
"Read unexpected embedded symbol start marker in [%s] :\n"
@@ -55,7 +55,7 @@ msgid ""
"%s<<\n"
msgstr ""
-#: libgeda/src/a_basic.c:458
+#: libgeda/src/a_basic.c:446
#, c-format
msgid ""
"Read unexpected embedded symbol end marker in [%s] :\n"
@@ -63,7 +63,7 @@ msgid ""
"%s<<\n"
msgstr ""
-#: libgeda/src/a_basic.c:487
+#: libgeda/src/a_basic.c:475
#, c-format
msgid ""
"Read an old format sym/sch file!\n"
@@ -71,7 +71,7 @@ msgid ""
"[%s]\n"
msgstr ""
-#: libgeda/src/a_basic.c:493
+#: libgeda/src/a_basic.c:481
#, c-format
msgid ""
"Read garbage in [%s] :\n"
@@ -84,12 +84,12 @@ msgstr ""
msgid "Failed to stat [%s]: %s"
msgstr ""
-#: libgeda/src/f_basic.c:219
+#: libgeda/src/f_basic.c:221
#, c-format
msgid "Cannot find file %s: %s"
msgstr ""
-#: libgeda/src/f_basic.c:257
+#: libgeda/src/f_basic.c:264
#, c-format
msgid ""
"\n"
@@ -98,23 +98,23 @@ msgid ""
"\n"
msgstr ""
-#: libgeda/src/f_basic.c:259
+#: libgeda/src/f_basic.c:266
msgid "I could not guess if it is newer, so you have to do it manually.\n"
msgstr ""
-#: libgeda/src/f_basic.c:261
+#: libgeda/src/f_basic.c:268
msgid ""
"The backup copy is newer than the schematic, so it seems you should load it "
"instead of the original file.\n"
msgstr ""
-#: libgeda/src/f_basic.c:263
+#: libgeda/src/f_basic.c:270
msgid ""
"Gschem usually makes backup copies automatically, and this situation happens "
"when it crashed or it was forced to exit abruptly.\n"
msgstr ""
-#: libgeda/src/f_basic.c:266
+#: libgeda/src/f_basic.c:273
msgid ""
"\n"
"Run gschem and correct the situation.\n"
@@ -124,143 +124,103 @@ msgstr ""
"شغÙ? gschem Ù? صØØ Ø§Ù?Ù?ضع.\n"
"\n"
-#: libgeda/src/f_basic.c:355
+#: libgeda/src/f_basic.c:362
#, c-format
msgid "Can't get the real filename of %s."
msgstr "Ù?ا Ù?Ù?Ù?Ù? اÙ?ØصÙ?Ù? عÙ?Ù? اÙ?اسÙ? اÙ?ØÙ?Ù?Ù?Ù? Ù?Ù?Ù?Ù?Ù? اÙ?خاص بÙ? %s."
-#: libgeda/src/f_basic.c:375
+#: libgeda/src/f_basic.c:382
#, c-format
msgid "Could NOT set previous backup file [%s] read-write\n"
msgstr ""
-#: libgeda/src/f_basic.c:381
+#: libgeda/src/f_basic.c:388
#, c-format
msgid "Can't save backup file: %s."
msgstr "Ù?ا Ù?Ù?Ù?Ù? ØÙ?ظ اÙ?Ù?Ù?Ù? اÙ?Ø¥ØتÙ?اطÙ?: %s."
-#: libgeda/src/f_basic.c:391
+#: libgeda/src/f_basic.c:398
#, c-format
msgid "Could NOT set backup file [%s] readonly\n"
msgstr ""
-#: libgeda/src/f_basic.c:680
+#: libgeda/src/f_basic.c:687
#, c-format
msgid "%s: %s"
msgstr "%s: %s"
-#: libgeda/src/f_print.c:118
+#: libgeda/src/f_print.c:119
msgid "Unable to get time of day in f_print_header()\n"
msgstr ""
-#: libgeda/src/f_print.c:160
+#: libgeda/src/f_print.c:161
#, c-format
msgid "Unable to open the prolog file `%s' for reading in f_print_header()\n"
msgstr ""
-#: libgeda/src/f_print.c:177
+#: libgeda/src/f_print.c:178
#, c-format
msgid "Error during reading of the prolog file `%s' in f_print_header()\n"
msgstr ""
-#: libgeda/src/f_print.c:183
+#: libgeda/src/f_print.c:184
msgid ""
"Error during writing of the output postscript file in f_print_header()\n"
msgstr ""
-#: libgeda/src/f_print.c:196
+#: libgeda/src/f_print.c:197
msgid "Giving up on printing\n"
msgstr ""
-#: libgeda/src/f_print.c:366
+#: libgeda/src/f_print.c:368
#, c-format
msgid "Could not open [%s] for printing\n"
msgstr ""
-#: libgeda/src/f_print.c:399
+#: libgeda/src/f_print.c:402
#, c-format
msgid "Could not execute command [%s] for printing\n"
msgstr ""
-#: libgeda/src/f_print.c:674
+#: libgeda/src/f_print.c:676
msgid "Too many UTF-8 characters, cannot print\n"
msgstr "رÙ?Ù?ز UTF-8 Ù?Ø«Ù?رة جداØ? Ù?ا Ù?Ù?Ù?Ù? اÙ?طباعة\n"
-#: libgeda/src/g_basic.c:101
-#, c-format
-msgid "%s:%i:%i: %s\n"
-msgstr "%s:%i:%i: %s\n"
-
-#: libgeda/src/g_basic.c:108
-#, c-format
-msgid "Unknown file: %s\n"
-msgstr "Ù?Ù?Ù? Ù?جÙ?Ù?Ù? : %s\n"
-
-#: libgeda/src/g_basic.c:114
-#, c-format
-msgid "Evaluation failed: %s\n"
-msgstr "Ù?Ø´Ù? اÙ?تÙ?Ù?Ù?Ù?: %s\n"
-
-#: libgeda/src/g_basic.c:115
-msgid "Enable debugging for more detailed information\n"
-msgstr "Ù?Ù?Ù? اÙ?تÙ?Ù?Ù?Ø Ù?Ù? أجÙ? تÙ?اصÙ?Ù? Ø£Ù?ثر\n"
-
-#: libgeda/src/g_basic.c:258
-#, c-format
-msgid "Could not find [%s] for interpretation\n"
-msgstr "Ù?Ù? Ù?عثر عÙ?Ù? [%s] Ù?Ù?تÙ?سÙ?ر\n"
-
-#: libgeda/src/g_rc.c:134
-#, c-format
-msgid "RC file [%s] already read in.\n"
-msgstr ""
-
-#: libgeda/src/g_rc.c:179
-#, c-format
-msgid "Read system config file [%%s]\n"
-msgstr "Ù?راءة Ù?Ù?Ù? تÙ?Ù?Ù?Ù? اÙ?Ù?ظاÙ? [%%s]\n"
-
-#: libgeda/src/g_rc.c:180
-#, c-format
-msgid "Did not find required system config file [%%s]\n"
-msgstr "Ù?Ù? Ù?عثر عÙ?Ù? Ù?Ù?Ù? Ù?Ø·Ù?Ù?ب Ù?تÙ?Ù?Ù?Ù? اÙ?Ù?ظاÙ? [%%s]\n"
-
-#: libgeda/src/g_rc.c:214
-#, c-format
-msgid "Read user config file [%%s]\n"
+#: libgeda/src/g_basic.c:257
+msgid ""
+"\n"
+"Backtrace:\n"
msgstr ""
-#: libgeda/src/g_rc.c:215
-#, c-format
-msgid "Did not find optional user config file [%%s]\n"
+#: libgeda/src/g_rc.c:225
+msgid "Config file already loaded"
msgstr ""
-#: libgeda/src/g_rc.c:246
-#, c-format
-msgid "Read local config file [%%s]\n"
-msgstr ""
+#: libgeda/src/g_rc.c:260
+#, fuzzy, c-format
+msgid "Parsed config from [%s]\n"
+msgstr "Ù?راءة Ù?Ù?Ù? تÙ?Ù?Ù?Ù? اÙ?Ù?ظاÙ? [%%s]\n"
-#: libgeda/src/g_rc.c:247
+#: libgeda/src/g_rc.c:273
#, c-format
-msgid "Did not find optional local config file [%%s]\n"
+msgid "Unable to parse config from [%s]: %s"
msgstr ""
-#: libgeda/src/g_rc.c:284
-#, c-format
-msgid "Read specified %s file [%%s]\n"
+#: libgeda/src/g_rc.c:290
+msgid "ERROR: An unknown error occurred while parsing configuration files."
msgstr ""
-#: libgeda/src/g_rc.c:286
+#: libgeda/src/g_rc.c:301 libgeda/src/g_rc.c:302
#, c-format
-msgid "Did not find specified %s file [%%s]\n"
+msgid "ERROR: %s\n"
msgstr ""
-#: libgeda/src/g_rc.c:336
+#: libgeda/src/g_rc.c:308
#, c-format
-msgid "Could not find any %s file!\n"
+msgid "ERROR: The %s log may contain more information.\n"
msgstr ""
-#: libgeda/src/g_rc.c:953
+#: libgeda/src/g_rc.c:1003
msgid ""
"WARNING: using a string for 'always-promote-attributes' is deprecated. Use a "
"list of strings instead\n"
@@ -275,7 +235,7 @@ msgstr ""
#: libgeda/src/o_bus_basic.c:182 libgeda/src/o_circle_basic.c:288
#: libgeda/src/o_line_basic.c:264 libgeda/src/o_net_basic.c:174
#: libgeda/src/o_path_basic.c:192 libgeda/src/o_pin_basic.c:187
-#: libgeda/src/o_text_basic.c:419
+#: libgeda/src/o_text_basic.c:420
#, c-format
msgid "Found an invalid color [ %s ]\n"
msgstr "عثر عÙ?Ù? Ù?Ù?Ù? غÙ?ر صاÙ?Ø [ %s ]\n"
@@ -284,7 +244,7 @@ msgstr "عثر عÙ?Ù? Ù?Ù?Ù? غÙ?ر صاÙ?Ø [ %s ]\n"
#: libgeda/src/o_bus_basic.c:183 libgeda/src/o_circle_basic.c:289
#: libgeda/src/o_line_basic.c:265 libgeda/src/o_net_basic.c:175
#: libgeda/src/o_path_basic.c:193 libgeda/src/o_pin_basic.c:188
-#: libgeda/src/o_text_basic.c:420
+#: libgeda/src/o_text_basic.c:421
msgid "Setting color to default color\n"
msgstr "تغÙ?Ù?ر اÙ?Ù?Ù?Ù? Ø¥Ù?Ù? اÙ?Ù?Ù?Ù? اÙ?Ø¥Ù?تراضÙ?\n"
@@ -333,46 +293,46 @@ msgstr ""
msgid "Found a zero radius circle [ %c %d %d %d %d ]\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:476
+#: libgeda/src/o_complex_basic.c:481
#, c-format
msgid ""
"Component not found:\n"
" %s"
msgstr ""
-#: libgeda/src/o_complex_basic.c:683
+#: libgeda/src/o_complex_basic.c:686
#, c-format
msgid "Found a component with an invalid rotation [ %c %d %d %d %d %d %s ]\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:695
+#: libgeda/src/o_complex_basic.c:698
#, c-format
msgid ""
"Found a component with an invalid mirror flag [ %c %d %d %d %d %d %s ]\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:1008
+#: libgeda/src/o_complex_basic.c:1014
#, c-format
msgid ""
"WARNING: Symbol version parse error on refdes %s:\n"
"\tCould not parse symbol file symversion=%s\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:1012
+#: libgeda/src/o_complex_basic.c:1018
#, c-format
msgid ""
"WARNING: Symbol version parse error on refdes %s:\n"
"\tCould not parse symbol file symversion=\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:1028
+#: libgeda/src/o_complex_basic.c:1034
#, c-format
msgid ""
"WARNING: Symbol version parse error on refdes %s:\n"
"\tCould not parse attached symversion=%s\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:1053
+#: libgeda/src/o_complex_basic.c:1059
#, c-format
msgid ""
"WARNING: Symbol version oddity on refdes %s:\n"
@@ -380,24 +340,24 @@ msgid ""
"symbol file\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:1067
+#: libgeda/src/o_complex_basic.c:1073
#, c-format
msgid ""
"WARNING: Symbol version mismatch on refdes %s (%s):\n"
"\tSymbol in library is newer than instantiated symbol\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:1095
+#: libgeda/src/o_complex_basic.c:1101
#, c-format
msgid "\tMAJOR VERSION CHANGE (file %.3f, instantiated %.3f, %s)!\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:1113
+#: libgeda/src/o_complex_basic.c:1119
#, c-format
msgid "\tMinor version change (file %.3f, instantiated %.3f)\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:1124
+#: libgeda/src/o_complex_basic.c:1130
#, c-format
msgid ""
"WARNING: Symbol version oddity on refdes %s:\n"
@@ -464,12 +424,12 @@ msgstr ""
msgid "Found an unsupported picture angle [ %d ]\n"
msgstr ""
-#: libgeda/src/o_picture.c:116 libgeda/src/o_text_basic.c:391
+#: libgeda/src/o_picture.c:116 libgeda/src/o_text_basic.c:392
msgid "Setting angle to 0\n"
msgstr ""
#: libgeda/src/o_picture.c:151 libgeda/src/o_picture.c:162
-#: libgeda/src/o_picture.c:913
+#: libgeda/src/o_picture.c:914
#, c-format
msgid "Failed to load image from embedded data [%s]: %s\n"
msgstr ""
@@ -479,12 +439,12 @@ msgid "Base64 decoding failed."
msgstr ""
#: libgeda/src/o_picture.c:153 libgeda/src/o_picture.c:164
-#: libgeda/src/o_picture.c:915
+#: libgeda/src/o_picture.c:916
msgid "Falling back to file loading. Picture unembedded.\n"
msgstr ""
-#: libgeda/src/o_picture.c:175 libgeda/src/o_picture.c:901
-#: libgeda/src/o_picture.c:950
+#: libgeda/src/o_picture.c:175 libgeda/src/o_picture.c:902
+#: libgeda/src/o_picture.c:951
#, c-format
msgid "Failed to load image from file [%s]: %s\n"
msgstr ""
@@ -498,16 +458,16 @@ msgstr ""
msgid "Error loading picture from file: %s.\n"
msgstr ""
-#: libgeda/src/o_picture.c:252
+#: libgeda/src/o_picture.c:253
msgid "ERROR: o_picture_save: unable to encode the picture.\n"
msgstr ""
-#: libgeda/src/o_picture.c:928
+#: libgeda/src/o_picture.c:929
#, c-format
msgid "Picture [%s] has been embedded\n"
msgstr ""
-#: libgeda/src/o_picture.c:968
+#: libgeda/src/o_picture.c:969
#, c-format
msgid "Picture [%s] has been unembedded\n"
msgstr ""
@@ -528,22 +488,22 @@ msgstr ""
msgid "Found a zero length pin: [ %s ]\n"
msgstr ""
-#: libgeda/src/o_text_basic.c:377
+#: libgeda/src/o_text_basic.c:378
#, c-format
msgid "Found a zero size text string [ %c %d %d %d %d %d %d %d %d ]\n"
msgstr ""
-#: libgeda/src/o_text_basic.c:389
+#: libgeda/src/o_text_basic.c:390
#, c-format
msgid "Found an unsupported text angle [ %c %d %d %d %d %d %d %d %d ]\n"
msgstr ""
-#: libgeda/src/o_text_basic.c:411
+#: libgeda/src/o_text_basic.c:412
#, c-format
msgid "Found an unsupported text alignment [ %c %d %d %d %d %d %d %d %d ]\n"
msgstr ""
-#: libgeda/src/o_text_basic.c:413
+#: libgeda/src/o_text_basic.c:414
msgid "Setting alignment to LOWER_LEFT\n"
msgstr ""
@@ -640,18 +600,18 @@ msgstr ""
msgid "Value in color map entry must be #f or a string"
msgstr ""
-#: libgeda/src/s_hierarchy.c:90
+#: libgeda/src/s_hierarchy.c:94
#, c-format
msgid ""
"hierarchy loop detected while visiting page:\n"
" \"%s\"\n"
msgstr ""
-#: libgeda/src/s_hierarchy.c:185
+#: libgeda/src/s_hierarchy.c:187
msgid "There are no schematics above the current one!\n"
msgstr ""
-#: libgeda/src/s_hierarchy.c:266
+#: libgeda/src/s_hierarchy.c:267
#, c-format
msgid "ERROR in s_hierarchy_traverse: schematic not found: %s\n"
msgstr ""
@@ -666,12 +626,12 @@ msgstr ""
msgid "s_page_delete: Unable to delete backup file %s."
msgstr ""
-#: libgeda/src/s_page.c:504
+#: libgeda/src/s_page.c:499
#, c-format
msgid "Saved [%s]\n"
msgstr "â??ØÙ?ظ [%s]\n"
-#: libgeda/src/s_page.c:510
+#: libgeda/src/s_page.c:505
#, c-format
msgid "Could NOT save [%s]\n"
msgstr ""
@@ -686,6 +646,24 @@ msgstr ""
msgid "Could not find [%s] in any SourceLibrary\n"
msgstr ""
+#~ msgid "%s:%i:%i: %s\n"
+#~ msgstr "%s:%i:%i: %s\n"
+
+#~ msgid "Unknown file: %s\n"
+#~ msgstr "Ù?Ù?Ù? Ù?جÙ?Ù?Ù? : %s\n"
+
+#~ msgid "Evaluation failed: %s\n"
+#~ msgstr "Ù?Ø´Ù? اÙ?تÙ?Ù?Ù?Ù?: %s\n"
+
+#~ msgid "Enable debugging for more detailed information\n"
+#~ msgstr "Ù?Ù?Ù? اÙ?تÙ?Ù?Ù?Ø Ù?Ù? أجÙ? تÙ?اصÙ?Ù? Ø£Ù?ثر\n"
+
+#~ msgid "Could not find [%s] for interpretation\n"
+#~ msgstr "Ù?Ù? Ù?عثر عÙ?Ù? [%s] Ù?Ù?تÙ?سÙ?ر\n"
+
+#~ msgid "Did not find required system config file [%%s]\n"
+#~ msgstr "Ù?Ù? Ù?عثر عÙ?Ù? Ù?Ù?Ù? Ù?Ø·Ù?Ù?ب Ù?تÙ?Ù?Ù?Ù? اÙ?Ù?ظاÙ? [%%s]\n"
+
#~ msgid "Could not read symbolic link information for %s"
#~ msgstr "Ù?Ù? Ù?Ù?Ù?Ù? Ù?راءة Ù?عÙ?Ù?Ù?ات اÙ?Ù?صÙ?Ø© اÙ?رÙ?زÙ?Ø© Ù?Ù? %s"
diff --git a/libgeda/po/de.po b/libgeda/po/de.po
index 08a2bc6..a5714d0 100644
--- a/libgeda/po/de.po
+++ b/libgeda/po/de.po
@@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2010-11-07 10:51+0000\n"
+"POT-Creation-Date: 2011-01-15 23:36-0500\n"
"PO-Revision-Date: 2010-01-31 13:00+0000\n"
"Last-Translator: Werner Hoch <werner.ho@xxxxxx>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -43,12 +43,12 @@ msgstr "gEDA Schaltplan"
msgid "gEDA Schematic Symbol"
msgstr "gEDA Schaltplansymbol"
-#: libgeda/src/a_basic.c:181
+#: libgeda/src/a_basic.c:182
#, c-format
msgid "o_save_objects: object %p has unknown type '%c'\n"
msgstr "o_save_objects: Das Objekt %p hat eine unbekannte Typangabe '%c'\n"
-#: libgeda/src/a_basic.c:429
+#: libgeda/src/a_basic.c:417
#, c-format
msgid ""
"Read unexpected embedded symbol start marker in [%s] :\n"
@@ -59,7 +59,7 @@ msgstr ""
">>\n"
"%s<<\n"
-#: libgeda/src/a_basic.c:458
+#: libgeda/src/a_basic.c:446
#, c-format
msgid ""
"Read unexpected embedded symbol end marker in [%s] :\n"
@@ -70,7 +70,7 @@ msgstr ""
">>\n"
"%s<<\n"
-#: libgeda/src/a_basic.c:487
+#: libgeda/src/a_basic.c:475
#, c-format
msgid ""
"Read an old format sym/sch file!\n"
@@ -81,7 +81,7 @@ msgstr ""
"Bitte aktualisiere die Datei mit g[sym|sch]update:\n"
"[%s]\n"
-#: libgeda/src/a_basic.c:493
+#: libgeda/src/a_basic.c:481
#, c-format
msgid ""
"Read garbage in [%s] :\n"
@@ -97,12 +97,12 @@ msgstr ""
msgid "Failed to stat [%s]: %s"
msgstr "Konnte Dateiinformation nicht ermitteln [%s]: %s"
-#: libgeda/src/f_basic.c:219
+#: libgeda/src/f_basic.c:221
#, c-format
msgid "Cannot find file %s: %s"
msgstr "Konnte Datei nicht finden %s: %s"
-#: libgeda/src/f_basic.c:257
+#: libgeda/src/f_basic.c:264
#, c-format
msgid ""
"\n"
@@ -115,13 +115,13 @@ msgstr ""
" %s.\n"
"\n"
-#: libgeda/src/f_basic.c:259
+#: libgeda/src/f_basic.c:266
msgid "I could not guess if it is newer, so you have to do it manually.\n"
msgstr ""
"Konnte nicht feststellen ob die Backupdatei neuer ist oder nicht. Dies muss "
"nun manuell durchgeführt werden.\n"
-#: libgeda/src/f_basic.c:261
+#: libgeda/src/f_basic.c:268
msgid ""
"The backup copy is newer than the schematic, so it seems you should load it "
"instead of the original file.\n"
@@ -129,7 +129,7 @@ msgstr ""
"Die Backupdatei ist neuer als die des Schaltplanes. Es sollte eventuell das "
"Backup anstatt der originalen Datei geladen werden.\n"
-#: libgeda/src/f_basic.c:263
+#: libgeda/src/f_basic.c:270
msgid ""
"Gschem usually makes backup copies automatically, and this situation happens "
"when it crashed or it was forced to exit abruptly.\n"
@@ -137,7 +137,7 @@ msgstr ""
"Gschem erstellt automatisch Backupdateien. Stürzt gschem ab oder wird es "
"absichtlich getötet, so ergibt sich diese Situation.\n"
-#: libgeda/src/f_basic.c:266
+#: libgeda/src/f_basic.c:273
msgid ""
"\n"
"Run gschem and correct the situation.\n"
@@ -147,146 +147,106 @@ msgstr ""
"Starte gschem und korrigiere diesen Zustand.\n"
"\n"
-#: libgeda/src/f_basic.c:355
+#: libgeda/src/f_basic.c:362
#, c-format
msgid "Can't get the real filename of %s."
msgstr "Konnte den wahren Dateinamen von %s nicht ermitteln."
-#: libgeda/src/f_basic.c:375
+#: libgeda/src/f_basic.c:382
#, c-format
msgid "Could NOT set previous backup file [%s] read-write\n"
msgstr ""
"Konnte die Rechte der alten Backupdatei [%s] nicht auf lesen+schreiben "
"setzen\n"
-#: libgeda/src/f_basic.c:381
+#: libgeda/src/f_basic.c:388
#, c-format
msgid "Can't save backup file: %s."
msgstr "Konnte Backupdatei nicht speichern: %s."
-#: libgeda/src/f_basic.c:391
+#: libgeda/src/f_basic.c:398
#, c-format
msgid "Could NOT set backup file [%s] readonly\n"
msgstr "Konnte die Rechte der Backupdatei [%s] nicht auf nurlesend setzen\n"
-#: libgeda/src/f_basic.c:680
+#: libgeda/src/f_basic.c:687
#, c-format
msgid "%s: %s"
msgstr "%s: %s"
-#: libgeda/src/f_print.c:118
+#: libgeda/src/f_print.c:119
msgid "Unable to get time of day in f_print_header()\n"
msgstr "f_print_header(): Konnte die aktuelle Zeit nicht ermitteln\n"
-#: libgeda/src/f_print.c:160
+#: libgeda/src/f_print.c:161
#, c-format
msgid "Unable to open the prolog file `%s' for reading in f_print_header()\n"
msgstr "f_print_header(): Konnte die Prologdatei '%s' nicht öffnen.\n"
-#: libgeda/src/f_print.c:177
+#: libgeda/src/f_print.c:178
#, c-format
msgid "Error during reading of the prolog file `%s' in f_print_header()\n"
msgstr "f_print_header(): Fehler beim Lesen der Prologdatei '%s'\n"
-#: libgeda/src/f_print.c:183
+#: libgeda/src/f_print.c:184
msgid ""
"Error during writing of the output postscript file in f_print_header()\n"
msgstr "f_print_header(): Fehler beim Schreiben der Postscript-Datei.\n"
-#: libgeda/src/f_print.c:196
+#: libgeda/src/f_print.c:197
msgid "Giving up on printing\n"
msgstr "Gebe das Ausdrucken auf\n"
-#: libgeda/src/f_print.c:366
+#: libgeda/src/f_print.c:368
#, c-format
msgid "Could not open [%s] for printing\n"
msgstr "Konnte die Datei [%s] nicht zum Drucken öffnen\n"
-#: libgeda/src/f_print.c:399
+#: libgeda/src/f_print.c:402
#, c-format
msgid "Could not execute command [%s] for printing\n"
msgstr "Konnte den Befehl [%s] zum Drucken nicht ausführen\n"
-#: libgeda/src/f_print.c:674
+#: libgeda/src/f_print.c:676
msgid "Too many UTF-8 characters, cannot print\n"
msgstr "Zu viele UTF-8 Zeichen. Es kann nicht gedruckt werden\n"
-#: libgeda/src/g_basic.c:101
-#, c-format
-msgid "%s:%i:%i: %s\n"
-msgstr "%s:%i:%i: %s\n"
-
-#: libgeda/src/g_basic.c:108
-#, c-format
-msgid "Unknown file: %s\n"
-msgstr "Unbekannte Datei: %s\n"
-
-#: libgeda/src/g_basic.c:114
-#, c-format
-msgid "Evaluation failed: %s\n"
-msgstr "Ausführung gescheitert: %s\n"
-
-#: libgeda/src/g_basic.c:115
-msgid "Enable debugging for more detailed information\n"
-msgstr "Aktiviere die Debugausgabe für genaure Informationen\n"
-
-#: libgeda/src/g_basic.c:258
-#, c-format
-msgid "Could not find [%s] for interpretation\n"
-msgstr "Konnte [%s] für die Auswertung nicht finden\n"
+#: libgeda/src/g_basic.c:257
+msgid ""
+"\n"
+"Backtrace:\n"
+msgstr ""
-#: libgeda/src/g_rc.c:134
-#, c-format
-msgid "RC file [%s] already read in.\n"
+#: libgeda/src/g_rc.c:225
+#, fuzzy
+msgid "Config file already loaded"
msgstr "Konfigurationsdatei [%s] wurde bereits gelesen.\n"
-#: libgeda/src/g_rc.c:179
-#, c-format
-msgid "Read system config file [%%s]\n"
-msgstr "Lese die Systemkonfigurationsdatei [%%s]\n"
-
-#: libgeda/src/g_rc.c:180
-#, c-format
-msgid "Did not find required system config file [%%s]\n"
-msgstr ""
-"Konnte die erforderliche Systemkonfigurationsdatei nicht finden [%%s]\n"
-
-#: libgeda/src/g_rc.c:214
-#, c-format
-msgid "Read user config file [%%s]\n"
+#: libgeda/src/g_rc.c:260
+#, fuzzy, c-format
+msgid "Parsed config from [%s]\n"
msgstr "Lese User-Konfigurationsdatei [%%s]\n"
-#: libgeda/src/g_rc.c:215
-#, c-format
-msgid "Did not find optional user config file [%%s]\n"
-msgstr "Die optionale User-Konfigurationsdatei [%%s] wurde nicht gefunden\n"
-
-#: libgeda/src/g_rc.c:246
-#, c-format
-msgid "Read local config file [%%s]\n"
-msgstr "Lese die lokale Konfigurationsdatei [%%s]\n"
-
-#: libgeda/src/g_rc.c:247
-#, c-format
-msgid "Did not find optional local config file [%%s]\n"
-msgstr "Die optionale lokale Konfigurationsdatei [%%s] wurde nicht gefunden\n"
+#: libgeda/src/g_rc.c:273
+#, fuzzy, c-format
+msgid "Unable to parse config from [%s]: %s"
+msgstr "Das Bild konnte nicht aus der Datei [%s] geladen werden: %s\n"
-#: libgeda/src/g_rc.c:284
-#, c-format
-msgid "Read specified %s file [%%s]\n"
-msgstr "Lese vorgegebene %s Datei [%%s]\n"
+#: libgeda/src/g_rc.c:290
+msgid "ERROR: An unknown error occurred while parsing configuration files."
+msgstr ""
-#: libgeda/src/g_rc.c:286
+#: libgeda/src/g_rc.c:301 libgeda/src/g_rc.c:302
#, c-format
-msgid "Did not find specified %s file [%%s]\n"
-msgstr "Konnte die angegebene %s-Datei [%%s] nicht finden\n"
+msgid "ERROR: %s\n"
+msgstr ""
-#: libgeda/src/g_rc.c:336
+#: libgeda/src/g_rc.c:308
#, c-format
-msgid "Could not find any %s file!\n"
-msgstr "Konnte keine %s-Dateien finden!\n"
+msgid "ERROR: The %s log may contain more information.\n"
+msgstr ""
-#: libgeda/src/g_rc.c:953
+#: libgeda/src/g_rc.c:1003
msgid ""
"WARNING: using a string for 'always-promote-attributes' is deprecated. Use a "
"list of strings instead\n"
@@ -304,7 +264,7 @@ msgstr "Kreisbogen mit Radius 0 entdeckt [%c %d, %d, %d, %d, %d, %d ]\n"
#: libgeda/src/o_bus_basic.c:182 libgeda/src/o_circle_basic.c:288
#: libgeda/src/o_line_basic.c:264 libgeda/src/o_net_basic.c:174
#: libgeda/src/o_path_basic.c:192 libgeda/src/o_pin_basic.c:187
-#: libgeda/src/o_text_basic.c:419
+#: libgeda/src/o_text_basic.c:420
#, c-format
msgid "Found an invalid color [ %s ]\n"
msgstr "Fehlerhafte Farbangabe entdeckt [%s]\n"
@@ -313,7 +273,7 @@ msgstr "Fehlerhafte Farbangabe entdeckt [%s]\n"
#: libgeda/src/o_bus_basic.c:183 libgeda/src/o_circle_basic.c:289
#: libgeda/src/o_line_basic.c:265 libgeda/src/o_net_basic.c:175
#: libgeda/src/o_path_basic.c:193 libgeda/src/o_pin_basic.c:188
-#: libgeda/src/o_text_basic.c:420
+#: libgeda/src/o_text_basic.c:421
msgid "Setting color to default color\n"
msgstr "Verwende die Default Farbe\n"
@@ -363,7 +323,7 @@ msgstr "Kreise mit dem Radius 0 sind nicht erlaubt\n"
msgid "Found a zero radius circle [ %c %d %d %d %d ]\n"
msgstr "Kreis mit dem Radius 0 entdeckt [ %c %d %d %d %d ]\n"
-#: libgeda/src/o_complex_basic.c:476
+#: libgeda/src/o_complex_basic.c:481
#, c-format
msgid ""
"Component not found:\n"
@@ -372,13 +332,13 @@ msgstr ""
"Bauteil wurde nicht gefunden:\n"
" %s"
-#: libgeda/src/o_complex_basic.c:683
+#: libgeda/src/o_complex_basic.c:686
#, c-format
msgid "Found a component with an invalid rotation [ %c %d %d %d %d %d %s ]\n"
msgstr ""
"Bauteil mit fehlerhafter Rotationsangabe entdeckt [ %c %d %d %d %d %d %s ]\n"
-#: libgeda/src/o_complex_basic.c:695
+#: libgeda/src/o_complex_basic.c:698
#, c-format
msgid ""
"Found a component with an invalid mirror flag [ %c %d %d %d %d %d %s ]\n"
@@ -386,7 +346,7 @@ msgstr ""
"Bauteil mit fehlerhafter Spiegelungsangabe entdeckt [ %c %d %d %d %d %d "
"%s ]\n"
-#: libgeda/src/o_complex_basic.c:1008
+#: libgeda/src/o_complex_basic.c:1014
#, c-format
msgid ""
"WARNING: Symbol version parse error on refdes %s:\n"
@@ -396,7 +356,7 @@ msgstr ""
"'%s':\n"
"\tKonnte das Attribut symversion=%s nicht zerlegen\n"
-#: libgeda/src/o_complex_basic.c:1012
+#: libgeda/src/o_complex_basic.c:1018
#, c-format
msgid ""
"WARNING: Symbol version parse error on refdes %s:\n"
@@ -406,7 +366,7 @@ msgstr ""
"'%s':\n"
"\tKonnte das Attribut symversion= nicht zerlegen\n"
-#: libgeda/src/o_complex_basic.c:1028
+#: libgeda/src/o_complex_basic.c:1034
#, c-format
msgid ""
"WARNING: Symbol version parse error on refdes %s:\n"
@@ -416,7 +376,7 @@ msgstr ""
"'%s':\n"
"\tKonnte das angehängte Attribut symversion=%s nicht zerlegen\n"
-#: libgeda/src/o_complex_basic.c:1053
+#: libgeda/src/o_complex_basic.c:1059
#, c-format
msgid ""
"WARNING: Symbol version oddity on refdes %s:\n"
@@ -428,7 +388,7 @@ msgstr ""
"\tsymversion=%s existiert bei dem Symbol im Schaltplan, fehlt aber innerhalb "
"der Schaltsymbol-Datei\n"
-#: libgeda/src/o_complex_basic.c:1067
+#: libgeda/src/o_complex_basic.c:1073
#, c-format
msgid ""
"WARNING: Symbol version mismatch on refdes %s (%s):\n"
@@ -438,20 +398,20 @@ msgstr ""
"(%s):\n"
"\tDas Symbol in der Bibliothek ist neuer als das Symbol im Schaltplan\n"
-#: libgeda/src/o_complex_basic.c:1095
+#: libgeda/src/o_complex_basic.c:1101
#, c-format
msgid "\tMAJOR VERSION CHANGE (file %.3f, instantiated %.3f, %s)!\n"
msgstr ""
"\tGROSSE VERSIONSÃ?NDERUNG (Symboldatei %.3f, Symbol im Schaltplan %.3f, "
"%s)!\n"
-#: libgeda/src/o_complex_basic.c:1113
+#: libgeda/src/o_complex_basic.c:1119
#, c-format
msgid "\tMinor version change (file %.3f, instantiated %.3f)\n"
msgstr ""
"\tKleine Versionsänderung (Symboldatei %.3f, Symbol im Schaltplan %.3f)!\n"
-#: libgeda/src/o_complex_basic.c:1124
+#: libgeda/src/o_complex_basic.c:1130
#, c-format
msgid ""
"WARNING: Symbol version oddity on refdes %s:\n"
@@ -522,12 +482,12 @@ msgstr "Setze die Einbettung auf 0\n"
msgid "Found an unsupported picture angle [ %d ]\n"
msgstr "Bild mit fehlerhafter Winkelangabe entdeckt [%d]\n"
-#: libgeda/src/o_picture.c:116 libgeda/src/o_text_basic.c:391
+#: libgeda/src/o_picture.c:116 libgeda/src/o_text_basic.c:392
msgid "Setting angle to 0\n"
msgstr "Setze die Winkelangabe auf 0\n"
#: libgeda/src/o_picture.c:151 libgeda/src/o_picture.c:162
-#: libgeda/src/o_picture.c:913
+#: libgeda/src/o_picture.c:914
#, c-format
msgid "Failed to load image from embedded data [%s]: %s\n"
msgstr "Fehler beim Laden der Daten eines eingebetteten Bildes [%s]: %s\n"
@@ -537,12 +497,12 @@ msgid "Base64 decoding failed."
msgstr "Base64 Dekodierung fehlgeschlagen."
#: libgeda/src/o_picture.c:153 libgeda/src/o_picture.c:164
-#: libgeda/src/o_picture.c:915
+#: libgeda/src/o_picture.c:916
msgid "Falling back to file loading. Picture unembedded.\n"
msgstr "Lade das Bild aus der Datei. Das Bild ist ausgebettet.\n"
-#: libgeda/src/o_picture.c:175 libgeda/src/o_picture.c:901
-#: libgeda/src/o_picture.c:950
+#: libgeda/src/o_picture.c:175 libgeda/src/o_picture.c:902
+#: libgeda/src/o_picture.c:951
#, c-format
msgid "Failed to load image from file [%s]: %s\n"
msgstr "Das Bild konnte nicht aus der Datei [%s] geladen werden: %s\n"
@@ -556,16 +516,16 @@ msgstr "Lade das Warnbild.\n"
msgid "Error loading picture from file: %s.\n"
msgstr "Fehler beim Laden des Bildes aus der Datei %s.\n"
-#: libgeda/src/o_picture.c:252
+#: libgeda/src/o_picture.c:253
msgid "ERROR: o_picture_save: unable to encode the picture.\n"
msgstr "FEHLER: o_picture_save: Kann das Bild nicht kodieren.\n"
-#: libgeda/src/o_picture.c:928
+#: libgeda/src/o_picture.c:929
#, c-format
msgid "Picture [%s] has been embedded\n"
msgstr "Das Bild [%s] wurde eingebettet\n"
-#: libgeda/src/o_picture.c:968
+#: libgeda/src/o_picture.c:969
#, c-format
msgid "Picture [%s] has been unembedded\n"
msgstr "Das Bild [%s] wurde ausgebettet\n"
@@ -590,27 +550,27 @@ msgstr ""
msgid "Found a zero length pin: [ %s ]\n"
msgstr "Pin mit der Länge 0 entdeckt: [ %s ]\n"
-#: libgeda/src/o_text_basic.c:377
+#: libgeda/src/o_text_basic.c:378
#, c-format
msgid "Found a zero size text string [ %c %d %d %d %d %d %d %d %d ]\n"
msgstr ""
"Textstring mit der Zeichengrö�e 0 entdeckt [ %c %d %d %d %d %d %d %d %d ]\n"
-#: libgeda/src/o_text_basic.c:389
+#: libgeda/src/o_text_basic.c:390
#, c-format
msgid "Found an unsupported text angle [ %c %d %d %d %d %d %d %d %d ]\n"
msgstr ""
"Text mit nicht unterstützer Winkelangabe entdeckt [ %c %d %d %d %d %d %d %d "
"%d ]\n"
-#: libgeda/src/o_text_basic.c:411
+#: libgeda/src/o_text_basic.c:412
#, c-format
msgid "Found an unsupported text alignment [ %c %d %d %d %d %d %d %d %d ]\n"
msgstr ""
"Text mit nicht unterstützer Ausrichtung entdeckt [ %c %d %d %d %d %d %d %d "
"%d ]\n"
-#: libgeda/src/o_text_basic.c:413
+#: libgeda/src/o_text_basic.c:414
msgid "Setting alignment to LOWER_LEFT\n"
msgstr "Verwende die Ausrichtung 'Links Unten'\n"
@@ -718,7 +678,7 @@ msgstr "Der Indexeintrag in der Farbtabelle muss ein Integerwert sein"
msgid "Value in color map entry must be #f or a string"
msgstr "Der Wert in der Farbtabelle muss '#f' oder ein String sein."
-#: libgeda/src/s_hierarchy.c:90
+#: libgeda/src/s_hierarchy.c:94
#, c-format
msgid ""
"hierarchy loop detected while visiting page:\n"
@@ -727,11 +687,11 @@ msgstr ""
"Zirkuläre Abhängigkeiten in der Hierarchie entdeckt. Schaltplan:\n"
" \"%s\"\n"
-#: libgeda/src/s_hierarchy.c:185
+#: libgeda/src/s_hierarchy.c:187
msgid "There are no schematics above the current one!\n"
msgstr "Ã?ber diesem Schaltplan gibt es keinen weiteren!\n"
-#: libgeda/src/s_hierarchy.c:266
+#: libgeda/src/s_hierarchy.c:267
#, c-format
msgid "ERROR in s_hierarchy_traverse: schematic not found: %s\n"
msgstr "ERROR: s_hierarchy_traverse: Schaltplan [%s] wurde nicht gefunden.\n"
@@ -747,12 +707,12 @@ msgstr ""
msgid "s_page_delete: Unable to delete backup file %s."
msgstr "s_page_delete: Kann die Backupdatei [%s] nicht löschen."
-#: libgeda/src/s_page.c:504
+#: libgeda/src/s_page.c:499
#, c-format
msgid "Saved [%s]\n"
msgstr "Gespeichert [%s]\n"
-#: libgeda/src/s_page.c:510
+#: libgeda/src/s_page.c:505
#, c-format
msgid "Could NOT save [%s]\n"
msgstr "ACHTUNG: Konnte Datei nicht speichern [%s]\n"
@@ -767,6 +727,47 @@ msgstr "[%s] gefunden\n"
msgid "Could not find [%s] in any SourceLibrary\n"
msgstr "Konnte [%s] in keiner Bibliothekenquelle finden\n"
+#~ msgid "%s:%i:%i: %s\n"
+#~ msgstr "%s:%i:%i: %s\n"
+
+#~ msgid "Unknown file: %s\n"
+#~ msgstr "Unbekannte Datei: %s\n"
+
+#~ msgid "Evaluation failed: %s\n"
+#~ msgstr "Ausführung gescheitert: %s\n"
+
+#~ msgid "Enable debugging for more detailed information\n"
+#~ msgstr "Aktiviere die Debugausgabe für genaure Informationen\n"
+
+#~ msgid "Could not find [%s] for interpretation\n"
+#~ msgstr "Konnte [%s] für die Auswertung nicht finden\n"
+
+#~ msgid "Read system config file [%%s]\n"
+#~ msgstr "Lese die Systemkonfigurationsdatei [%%s]\n"
+
+#~ msgid "Did not find required system config file [%%s]\n"
+#~ msgstr ""
+#~ "Konnte die erforderliche Systemkonfigurationsdatei nicht finden [%%s]\n"
+
+#~ msgid "Did not find optional user config file [%%s]\n"
+#~ msgstr "Die optionale User-Konfigurationsdatei [%%s] wurde nicht gefunden\n"
+
+#~ msgid "Read local config file [%%s]\n"
+#~ msgstr "Lese die lokale Konfigurationsdatei [%%s]\n"
+
+#~ msgid "Did not find optional local config file [%%s]\n"
+#~ msgstr ""
+#~ "Die optionale lokale Konfigurationsdatei [%%s] wurde nicht gefunden\n"
+
+#~ msgid "Read specified %s file [%%s]\n"
+#~ msgstr "Lese vorgegebene %s Datei [%%s]\n"
+
+#~ msgid "Did not find specified %s file [%%s]\n"
+#~ msgstr "Konnte die angegebene %s-Datei [%%s] nicht finden\n"
+
+#~ msgid "Could not find any %s file!\n"
+#~ msgstr "Konnte keine %s-Dateien finden!\n"
+
#~ msgid "o_save: Could not open [%s]\n"
#~ msgstr "o_save: Konnte Datei [%s] nicht öffnen\n"
diff --git a/libgeda/po/en_GB.po b/libgeda/po/en_GB.po
index 7f53502..27859ef 100644
--- a/libgeda/po/en_GB.po
+++ b/libgeda/po/en_GB.po
@@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2010-11-07 10:51+0000\n"
+"POT-Creation-Date: 2011-01-15 23:36-0500\n"
"PO-Revision-Date: 2010-01-31 13:00+0000\n"
"Last-Translator: Peter Clifton <pcjc2@xxxxxxxxx>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -43,12 +43,12 @@ msgstr "gEDA Circuit Schematic"
msgid "gEDA Schematic Symbol"
msgstr "gEDA Schematic Symbol"
-#: libgeda/src/a_basic.c:181
+#: libgeda/src/a_basic.c:182
#, c-format
msgid "o_save_objects: object %p has unknown type '%c'\n"
msgstr "o_save_objects: object %p has unknown type '%c'\n"
-#: libgeda/src/a_basic.c:429
+#: libgeda/src/a_basic.c:417
#, c-format
msgid ""
"Read unexpected embedded symbol start marker in [%s] :\n"
@@ -59,7 +59,7 @@ msgstr ""
">>\n"
"%s<<\n"
-#: libgeda/src/a_basic.c:458
+#: libgeda/src/a_basic.c:446
#, c-format
msgid ""
"Read unexpected embedded symbol end marker in [%s] :\n"
@@ -70,7 +70,7 @@ msgstr ""
">>\n"
"%s<<\n"
-#: libgeda/src/a_basic.c:487
+#: libgeda/src/a_basic.c:475
#, c-format
msgid ""
"Read an old format sym/sch file!\n"
@@ -81,7 +81,7 @@ msgstr ""
"Please run g[sym|sch]update on:\n"
"[%s]\n"
-#: libgeda/src/a_basic.c:493
+#: libgeda/src/a_basic.c:481
#, c-format
msgid ""
"Read garbage in [%s] :\n"
@@ -97,12 +97,12 @@ msgstr ""
msgid "Failed to stat [%s]: %s"
msgstr "Failed to stat [%s]: %s"
-#: libgeda/src/f_basic.c:219
+#: libgeda/src/f_basic.c:221
#, c-format
msgid "Cannot find file %s: %s"
msgstr "Cannot find file: %s: %s"
-#: libgeda/src/f_basic.c:257
+#: libgeda/src/f_basic.c:264
#, c-format
msgid ""
"\n"
@@ -115,11 +115,11 @@ msgstr ""
" %s.\n"
"\n"
-#: libgeda/src/f_basic.c:259
+#: libgeda/src/f_basic.c:266
msgid "I could not guess if it is newer, so you have to do it manually.\n"
msgstr "I could not guess if it is newer, so you have to do it manually.\n"
-#: libgeda/src/f_basic.c:261
+#: libgeda/src/f_basic.c:268
msgid ""
"The backup copy is newer than the schematic, so it seems you should load it "
"instead of the original file.\n"
@@ -127,7 +127,7 @@ msgstr ""
"The backup copy is newer than the schematic, so it seems you should load it "
"instead of the original file.\n"
-#: libgeda/src/f_basic.c:263
+#: libgeda/src/f_basic.c:270
msgid ""
"Gschem usually makes backup copies automatically, and this situation happens "
"when it crashed or it was forced to exit abruptly.\n"
@@ -135,7 +135,7 @@ msgstr ""
"Gschem usually makes backup copies automatically, and this situation happens "
"when it crashed or it was forced to exit abruptly.\n"
-#: libgeda/src/f_basic.c:266
+#: libgeda/src/f_basic.c:273
msgid ""
"\n"
"Run gschem and correct the situation.\n"
@@ -145,144 +145,105 @@ msgstr ""
"Run gschem and correct the situation.\n"
"\n"
-#: libgeda/src/f_basic.c:355
+#: libgeda/src/f_basic.c:362
#, c-format
msgid "Can't get the real filename of %s."
msgstr "Can't get the real filename of %s."
-#: libgeda/src/f_basic.c:375
+#: libgeda/src/f_basic.c:382
#, c-format
msgid "Could NOT set previous backup file [%s] read-write\n"
msgstr "Could NOT set previous backup file [%s] read-write\n"
-#: libgeda/src/f_basic.c:381
+#: libgeda/src/f_basic.c:388
#, c-format
msgid "Can't save backup file: %s."
msgstr "Can't save backup file: %s."
-#: libgeda/src/f_basic.c:391
+#: libgeda/src/f_basic.c:398
#, c-format
msgid "Could NOT set backup file [%s] readonly\n"
msgstr "Could NOT set backup file [%s] readonly\n"
-#: libgeda/src/f_basic.c:680
+#: libgeda/src/f_basic.c:687
#, c-format
msgid "%s: %s"
msgstr "%s: %s"
-#: libgeda/src/f_print.c:118
+#: libgeda/src/f_print.c:119
msgid "Unable to get time of day in f_print_header()\n"
msgstr "Unable to get time of day in f_print_header()\n"
-#: libgeda/src/f_print.c:160
+#: libgeda/src/f_print.c:161
#, c-format
msgid "Unable to open the prolog file `%s' for reading in f_print_header()\n"
msgstr "Unable to open the prolog file `%s' for reading in f_print_header()\n"
-#: libgeda/src/f_print.c:177
+#: libgeda/src/f_print.c:178
#, c-format
msgid "Error during reading of the prolog file `%s' in f_print_header()\n"
msgstr "Error during reading of the prolog file `%s' in f_print_header()\n"
-#: libgeda/src/f_print.c:183
+#: libgeda/src/f_print.c:184
msgid ""
"Error during writing of the output postscript file in f_print_header()\n"
msgstr ""
"Error during writing of the output postscript file in f_print_header()\n"
-#: libgeda/src/f_print.c:196
+#: libgeda/src/f_print.c:197
msgid "Giving up on printing\n"
msgstr "Giving up on printing\n"
-#: libgeda/src/f_print.c:366
+#: libgeda/src/f_print.c:368
#, c-format
msgid "Could not open [%s] for printing\n"
msgstr "Could not open [%s] for printing\n"
-#: libgeda/src/f_print.c:399
+#: libgeda/src/f_print.c:402
#, c-format
msgid "Could not execute command [%s] for printing\n"
msgstr "Could not execute command [%s] for printing\n"
-#: libgeda/src/f_print.c:674
+#: libgeda/src/f_print.c:676
msgid "Too many UTF-8 characters, cannot print\n"
msgstr "Too many UTF-8 characters, cannot print\n"
-#: libgeda/src/g_basic.c:101
-#, c-format
-msgid "%s:%i:%i: %s\n"
-msgstr "%s:%i:%i: %s\n"
-
-#: libgeda/src/g_basic.c:108
-#, c-format
-msgid "Unknown file: %s\n"
-msgstr "Unknown file: %s\n"
-
-#: libgeda/src/g_basic.c:114
-#, c-format
-msgid "Evaluation failed: %s\n"
-msgstr "Evaluation failed: %s\n"
-
-#: libgeda/src/g_basic.c:115
-msgid "Enable debugging for more detailed information\n"
-msgstr "Enable debugging for more detailed information\n"
-
-#: libgeda/src/g_basic.c:258
-#, c-format
-msgid "Could not find [%s] for interpretation\n"
-msgstr "Could not find [%s] for interpretation\n"
+#: libgeda/src/g_basic.c:257
+msgid ""
+"\n"
+"Backtrace:\n"
+msgstr ""
-#: libgeda/src/g_rc.c:134
-#, c-format
-msgid "RC file [%s] already read in.\n"
+#: libgeda/src/g_rc.c:225
+#, fuzzy
+msgid "Config file already loaded"
msgstr "RC file [%s] already read in.\n"
-#: libgeda/src/g_rc.c:179
-#, c-format
-msgid "Read system config file [%%s]\n"
-msgstr "Read system config file [%%s]\n"
-
-#: libgeda/src/g_rc.c:180
-#, c-format
-msgid "Did not find required system config file [%%s]\n"
-msgstr "Did not find required system config file [%%s]\n"
-
-#: libgeda/src/g_rc.c:214
-#, c-format
-msgid "Read user config file [%%s]\n"
+#: libgeda/src/g_rc.c:260
+#, fuzzy, c-format
+msgid "Parsed config from [%s]\n"
msgstr "Read user config file [%%s]\n"
-#: libgeda/src/g_rc.c:215
-#, c-format
-msgid "Did not find optional user config file [%%s]\n"
-msgstr "Did not find optional user config file [%%s]\n"
-
-#: libgeda/src/g_rc.c:246
-#, c-format
-msgid "Read local config file [%%s]\n"
-msgstr "Read local config file [%%s]\n"
-
-#: libgeda/src/g_rc.c:247
-#, c-format
-msgid "Did not find optional local config file [%%s]\n"
-msgstr "Did not find optional local config file [%%s]\n"
+#: libgeda/src/g_rc.c:273
+#, fuzzy, c-format
+msgid "Unable to parse config from [%s]: %s"
+msgstr "Failed to load image from file [%s]: %s\n"
-#: libgeda/src/g_rc.c:284
-#, c-format
-msgid "Read specified %s file [%%s]\n"
-msgstr "Read specified %s file [%%s]\n"
+#: libgeda/src/g_rc.c:290
+msgid "ERROR: An unknown error occurred while parsing configuration files."
+msgstr ""
-#: libgeda/src/g_rc.c:286
+#: libgeda/src/g_rc.c:301 libgeda/src/g_rc.c:302
#, c-format
-msgid "Did not find specified %s file [%%s]\n"
-msgstr "Did not find specified %s file [%%s]\n"
+msgid "ERROR: %s\n"
+msgstr ""
-#: libgeda/src/g_rc.c:336
+#: libgeda/src/g_rc.c:308
#, c-format
-msgid "Could not find any %s file!\n"
-msgstr "Could not find any %s file!\n"
+msgid "ERROR: The %s log may contain more information.\n"
+msgstr ""
-#: libgeda/src/g_rc.c:953
+#: libgeda/src/g_rc.c:1003
msgid ""
"WARNING: using a string for 'always-promote-attributes' is deprecated. Use a "
"list of strings instead\n"
@@ -299,7 +260,7 @@ msgstr "Found a zero radius arc [ %c %d, %d, %d, %d, %d, %d ]\n"
#: libgeda/src/o_bus_basic.c:182 libgeda/src/o_circle_basic.c:288
#: libgeda/src/o_line_basic.c:264 libgeda/src/o_net_basic.c:174
#: libgeda/src/o_path_basic.c:192 libgeda/src/o_pin_basic.c:187
-#: libgeda/src/o_text_basic.c:419
+#: libgeda/src/o_text_basic.c:420
#, c-format
msgid "Found an invalid color [ %s ]\n"
msgstr "Found an invalid colour [ %s ]\n"
@@ -308,7 +269,7 @@ msgstr "Found an invalid colour [ %s ]\n"
#: libgeda/src/o_bus_basic.c:183 libgeda/src/o_circle_basic.c:289
#: libgeda/src/o_line_basic.c:265 libgeda/src/o_net_basic.c:175
#: libgeda/src/o_path_basic.c:193 libgeda/src/o_pin_basic.c:188
-#: libgeda/src/o_text_basic.c:420
+#: libgeda/src/o_text_basic.c:421
msgid "Setting color to default color\n"
msgstr "Setting colour to default colour\n"
@@ -357,7 +318,7 @@ msgstr "Null radius circles are not allowed\n"
msgid "Found a zero radius circle [ %c %d %d %d %d ]\n"
msgstr "Found a zero radius circle [ %c %d %d %d %d ]\n"
-#: libgeda/src/o_complex_basic.c:476
+#: libgeda/src/o_complex_basic.c:481
#, c-format
msgid ""
"Component not found:\n"
@@ -366,19 +327,19 @@ msgstr ""
"Component not found:\n"
" %s"
-#: libgeda/src/o_complex_basic.c:683
+#: libgeda/src/o_complex_basic.c:686
#, c-format
msgid "Found a component with an invalid rotation [ %c %d %d %d %d %d %s ]\n"
msgstr "Found a component with an invalid rotation [ %c %d %d %d %d %d %s ]\n"
-#: libgeda/src/o_complex_basic.c:695
+#: libgeda/src/o_complex_basic.c:698
#, c-format
msgid ""
"Found a component with an invalid mirror flag [ %c %d %d %d %d %d %s ]\n"
msgstr ""
"Found a component with an invalid mirror flag [ %c %d %d %d %d %d %s ]\n"
-#: libgeda/src/o_complex_basic.c:1008
+#: libgeda/src/o_complex_basic.c:1014
#, c-format
msgid ""
"WARNING: Symbol version parse error on refdes %s:\n"
@@ -387,7 +348,7 @@ msgstr ""
"WARNING: Symbol version parse error on refdes %s:\n"
"\tCould not parse symbol file symversion=%s\n"
-#: libgeda/src/o_complex_basic.c:1012
+#: libgeda/src/o_complex_basic.c:1018
#, c-format
msgid ""
"WARNING: Symbol version parse error on refdes %s:\n"
@@ -396,7 +357,7 @@ msgstr ""
"WARNING: Symbol version parse error on refdes %s:\n"
"\tCould not parse symbol file symversion=\n"
-#: libgeda/src/o_complex_basic.c:1028
+#: libgeda/src/o_complex_basic.c:1034
#, c-format
msgid ""
"WARNING: Symbol version parse error on refdes %s:\n"
@@ -405,7 +366,7 @@ msgstr ""
"WARNING: Symbol version parse error on refdes %s:\n"
"\tCould not parse attached symversion=%s\n"
-#: libgeda/src/o_complex_basic.c:1053
+#: libgeda/src/o_complex_basic.c:1059
#, c-format
msgid ""
"WARNING: Symbol version oddity on refdes %s:\n"
@@ -416,7 +377,7 @@ msgstr ""
"\tsymversion=%s attached to instantiated symbol, but no symversion= inside "
"symbol file\n"
-#: libgeda/src/o_complex_basic.c:1067
+#: libgeda/src/o_complex_basic.c:1073
#, c-format
msgid ""
"WARNING: Symbol version mismatch on refdes %s (%s):\n"
@@ -425,17 +386,17 @@ msgstr ""
"WARNING: Symbol version mismatch on refdes %s (%s):\n"
"\tSymbol in library is newer than instantiated symbol\n"
-#: libgeda/src/o_complex_basic.c:1095
+#: libgeda/src/o_complex_basic.c:1101
#, c-format
msgid "\tMAJOR VERSION CHANGE (file %.3f, instantiated %.3f, %s)!\n"
msgstr "\tMAJOR VERSION CHANGE (file %.3f, instantiated %.3f, %s)!\n"
-#: libgeda/src/o_complex_basic.c:1113
+#: libgeda/src/o_complex_basic.c:1119
#, c-format
msgid "\tMinor version change (file %.3f, instantiated %.3f)\n"
msgstr "\tMinor version change (file %.3f, instantiated %.3f)\n"
-#: libgeda/src/o_complex_basic.c:1124
+#: libgeda/src/o_complex_basic.c:1130
#, c-format
msgid ""
"WARNING: Symbol version oddity on refdes %s:\n"
@@ -506,12 +467,12 @@ msgstr "Setting embedded to 0\n"
msgid "Found an unsupported picture angle [ %d ]\n"
msgstr "Found an unsupported picture angle [ %d ]\n"
-#: libgeda/src/o_picture.c:116 libgeda/src/o_text_basic.c:391
+#: libgeda/src/o_picture.c:116 libgeda/src/o_text_basic.c:392
msgid "Setting angle to 0\n"
msgstr "Setting angle to 0\n"
#: libgeda/src/o_picture.c:151 libgeda/src/o_picture.c:162
-#: libgeda/src/o_picture.c:913
+#: libgeda/src/o_picture.c:914
#, c-format
msgid "Failed to load image from embedded data [%s]: %s\n"
msgstr "Failed to load image from embedded data [%s]: %s\n"
@@ -521,12 +482,12 @@ msgid "Base64 decoding failed."
msgstr "Base64 decoding failed."
#: libgeda/src/o_picture.c:153 libgeda/src/o_picture.c:164
-#: libgeda/src/o_picture.c:915
+#: libgeda/src/o_picture.c:916
msgid "Falling back to file loading. Picture unembedded.\n"
msgstr "Falling back to file loading. Picture unembedded.\n"
-#: libgeda/src/o_picture.c:175 libgeda/src/o_picture.c:901
-#: libgeda/src/o_picture.c:950
+#: libgeda/src/o_picture.c:175 libgeda/src/o_picture.c:902
+#: libgeda/src/o_picture.c:951
#, c-format
msgid "Failed to load image from file [%s]: %s\n"
msgstr "Failed to load image from file [%s]: %s\n"
@@ -540,16 +501,16 @@ msgstr "Loading warning picture.\n"
msgid "Error loading picture from file: %s.\n"
msgstr "Error loading picture from file: %s.\n"
-#: libgeda/src/o_picture.c:252
+#: libgeda/src/o_picture.c:253
msgid "ERROR: o_picture_save: unable to encode the picture.\n"
msgstr "ERROR: o_picture_save: unable to encode the picture.\n"
-#: libgeda/src/o_picture.c:928
+#: libgeda/src/o_picture.c:929
#, c-format
msgid "Picture [%s] has been embedded\n"
msgstr "Picture [%s] has been embedded\n"
-#: libgeda/src/o_picture.c:968
+#: libgeda/src/o_picture.c:969
#, c-format
msgid "Picture [%s] has been unembedded\n"
msgstr "Picture [%s] has been unembedded\n"
@@ -572,22 +533,22 @@ msgstr "Found an invalid whichend on a pin (reseting to zero): %d\n"
msgid "Found a zero length pin: [ %s ]\n"
msgstr "Found a zero length pin: [ %s ]\n"
-#: libgeda/src/o_text_basic.c:377
+#: libgeda/src/o_text_basic.c:378
#, c-format
msgid "Found a zero size text string [ %c %d %d %d %d %d %d %d %d ]\n"
msgstr "Found a zero size text string [ %c %d %d %d %d %d %d %d %d ]\n"
-#: libgeda/src/o_text_basic.c:389
+#: libgeda/src/o_text_basic.c:390
#, c-format
msgid "Found an unsupported text angle [ %c %d %d %d %d %d %d %d %d ]\n"
msgstr "Found an unsupported text angle [ %c %d %d %d %d %d %d %d %d ]\n"
-#: libgeda/src/o_text_basic.c:411
+#: libgeda/src/o_text_basic.c:412
#, c-format
msgid "Found an unsupported text alignment [ %c %d %d %d %d %d %d %d %d ]\n"
msgstr "Found an unsupported text alignment [ %c %d %d %d %d %d %d %d %d ]\n"
-#: libgeda/src/o_text_basic.c:413
+#: libgeda/src/o_text_basic.c:414
msgid "Setting alignment to LOWER_LEFT\n"
msgstr "Setting alignment to LOWER_LEFT\n"
@@ -687,7 +648,7 @@ msgstr "Index in colour map entry must be an integer"
msgid "Value in color map entry must be #f or a string"
msgstr "Value in colour map entry must be #f or a string"
-#: libgeda/src/s_hierarchy.c:90
+#: libgeda/src/s_hierarchy.c:94
#, c-format
msgid ""
"hierarchy loop detected while visiting page:\n"
@@ -696,11 +657,11 @@ msgstr ""
"hierarchy loop detected while visiting page:\n"
" \"%s\"\n"
-#: libgeda/src/s_hierarchy.c:185
+#: libgeda/src/s_hierarchy.c:187
msgid "There are no schematics above the current one!\n"
msgstr "There are no schematics above the current one!\n"
-#: libgeda/src/s_hierarchy.c:266
+#: libgeda/src/s_hierarchy.c:267
#, c-format
msgid "ERROR in s_hierarchy_traverse: schematic not found: %s\n"
msgstr "ERROR in s_hierarchy_traverse: schematic not found: %s\n"
@@ -715,12 +676,12 @@ msgstr "s_page_delete: Can't get the real filename of %s."
msgid "s_page_delete: Unable to delete backup file %s."
msgstr "s_page_delete: Unable to delete backup file %s."
-#: libgeda/src/s_page.c:504
+#: libgeda/src/s_page.c:499
#, c-format
msgid "Saved [%s]\n"
msgstr "Saved [%s]\n"
-#: libgeda/src/s_page.c:510
+#: libgeda/src/s_page.c:505
#, c-format
msgid "Could NOT save [%s]\n"
msgstr "Could NOT save [%s]\n"
@@ -734,3 +695,42 @@ msgstr "Found [%s]\n"
#, c-format
msgid "Could not find [%s] in any SourceLibrary\n"
msgstr "Could not find [%s] in any SourceLibrary\n"
+
+#~ msgid "%s:%i:%i: %s\n"
+#~ msgstr "%s:%i:%i: %s\n"
+
+#~ msgid "Unknown file: %s\n"
+#~ msgstr "Unknown file: %s\n"
+
+#~ msgid "Evaluation failed: %s\n"
+#~ msgstr "Evaluation failed: %s\n"
+
+#~ msgid "Enable debugging for more detailed information\n"
+#~ msgstr "Enable debugging for more detailed information\n"
+
+#~ msgid "Could not find [%s] for interpretation\n"
+#~ msgstr "Could not find [%s] for interpretation\n"
+
+#~ msgid "Read system config file [%%s]\n"
+#~ msgstr "Read system config file [%%s]\n"
+
+#~ msgid "Did not find required system config file [%%s]\n"
+#~ msgstr "Did not find required system config file [%%s]\n"
+
+#~ msgid "Did not find optional user config file [%%s]\n"
+#~ msgstr "Did not find optional user config file [%%s]\n"
+
+#~ msgid "Read local config file [%%s]\n"
+#~ msgstr "Read local config file [%%s]\n"
+
+#~ msgid "Did not find optional local config file [%%s]\n"
+#~ msgstr "Did not find optional local config file [%%s]\n"
+
+#~ msgid "Read specified %s file [%%s]\n"
+#~ msgstr "Read specified %s file [%%s]\n"
+
+#~ msgid "Did not find specified %s file [%%s]\n"
+#~ msgstr "Did not find specified %s file [%%s]\n"
+
+#~ msgid "Could not find any %s file!\n"
+#~ msgstr "Could not find any %s file!\n"
diff --git a/libgeda/po/es.po b/libgeda/po/es.po
index 1265398..f9153e5 100644
--- a/libgeda/po/es.po
+++ b/libgeda/po/es.po
@@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2010-11-07 10:51+0000\n"
+"POT-Creation-Date: 2011-01-15 23:36-0500\n"
"PO-Revision-Date: 2010-02-06 22:11+0000\n"
"Last-Translator: Carlos Nieves Ã?nega <Unknown>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -43,12 +43,12 @@ msgstr "Esquema de circuito gEDA"
msgid "gEDA Schematic Symbol"
msgstr "SÃmbolo de esquema gEDA"
-#: libgeda/src/a_basic.c:181
+#: libgeda/src/a_basic.c:182
#, c-format
msgid "o_save_objects: object %p has unknown type '%c'\n"
msgstr "o_save_objects: el objeto %p tiene un tipo '%c' desconocido\n"
-#: libgeda/src/a_basic.c:429
+#: libgeda/src/a_basic.c:417
#, c-format
msgid ""
"Read unexpected embedded symbol start marker in [%s] :\n"
@@ -59,7 +59,7 @@ msgstr ""
">>\n"
"%s<<\n"
-#: libgeda/src/a_basic.c:458
+#: libgeda/src/a_basic.c:446
#, c-format
msgid ""
"Read unexpected embedded symbol end marker in [%s] :\n"
@@ -70,7 +70,7 @@ msgstr ""
">>\n"
"%s<<\n"
-#: libgeda/src/a_basic.c:487
+#: libgeda/src/a_basic.c:475
#, c-format
msgid ""
"Read an old format sym/sch file!\n"
@@ -81,7 +81,7 @@ msgstr ""
"Por favor ejecute: g[sym|sch]update en: \n"
"[%s]\n"
-#: libgeda/src/a_basic.c:493
+#: libgeda/src/a_basic.c:481
#, c-format
msgid ""
"Read garbage in [%s] :\n"
@@ -97,12 +97,12 @@ msgstr ""
msgid "Failed to stat [%s]: %s"
msgstr "No se ha podido determinar [%s]: %s"
-#: libgeda/src/f_basic.c:219
+#: libgeda/src/f_basic.c:221
#, c-format
msgid "Cannot find file %s: %s"
msgstr "No se puede encontrar el archivo %s: %s"
-#: libgeda/src/f_basic.c:257
+#: libgeda/src/f_basic.c:264
#, c-format
msgid ""
"\n"
@@ -115,13 +115,13 @@ msgstr ""
" %s.\n"
"\n"
-#: libgeda/src/f_basic.c:259
+#: libgeda/src/f_basic.c:266
msgid "I could not guess if it is newer, so you have to do it manually.\n"
msgstr ""
"No se ha podido averiguar si es más reciente, asà que lo tendrá que hacer "
"usted manualmente.\n"
-#: libgeda/src/f_basic.c:261
+#: libgeda/src/f_basic.c:268
msgid ""
"The backup copy is newer than the schematic, so it seems you should load it "
"instead of the original file.\n"
@@ -129,7 +129,7 @@ msgstr ""
"La copia de seguridad es más reciente que el esquema. Parece que deberÃa "
"cargar la copia de seguridad en vez del archivo original.\n"
-#: libgeda/src/f_basic.c:263
+#: libgeda/src/f_basic.c:270
msgid ""
"Gschem usually makes backup copies automatically, and this situation happens "
"when it crashed or it was forced to exit abruptly.\n"
@@ -137,7 +137,7 @@ msgstr ""
"Gschem normalmente realiza copias de seguridad automáticamente y esta "
"situaciónocurre cuando ha fallado o se ha forzado una salida abrupta.\n"
-#: libgeda/src/f_basic.c:266
+#: libgeda/src/f_basic.c:273
msgid ""
"\n"
"Run gschem and correct the situation.\n"
@@ -147,153 +147,110 @@ msgstr ""
"Ejecute gschem y corrija la situación.\n"
"\n"
-#: libgeda/src/f_basic.c:355
+#: libgeda/src/f_basic.c:362
#, c-format
msgid "Can't get the real filename of %s."
msgstr "No se puede averiguar el nombre real del archivo %s."
-#: libgeda/src/f_basic.c:375
+#: libgeda/src/f_basic.c:382
#, c-format
msgid "Could NOT set previous backup file [%s] read-write\n"
msgstr ""
"No se ha podido poner el archivo de copia de seguridad anterior [%s] en modo "
"de lectura-escritura\n"
-#: libgeda/src/f_basic.c:381
+#: libgeda/src/f_basic.c:388
#, c-format
msgid "Can't save backup file: %s."
msgstr "No se puede guardar la copia de seguridad: %s"
-#: libgeda/src/f_basic.c:391
+#: libgeda/src/f_basic.c:398
#, c-format
msgid "Could NOT set backup file [%s] readonly\n"
msgstr ""
"No se ha podido poner el archivo de copia de seguridad [%s] en modo de sólo "
"lectura\n"
-#: libgeda/src/f_basic.c:680
+#: libgeda/src/f_basic.c:687
#, c-format
msgid "%s: %s"
msgstr "%s: %s"
-#: libgeda/src/f_print.c:118
+#: libgeda/src/f_print.c:119
msgid "Unable to get time of day in f_print_header()\n"
msgstr "Imposible obtener la hora en f_print_header()\n"
-#: libgeda/src/f_print.c:160
+#: libgeda/src/f_print.c:161
#, c-format
msgid "Unable to open the prolog file `%s' for reading in f_print_header()\n"
msgstr ""
"Imposible abrir el archivo de prólogo '%s' para lectura en f_print_header()\n"
-#: libgeda/src/f_print.c:177
+#: libgeda/src/f_print.c:178
#, c-format
msgid "Error during reading of the prolog file `%s' in f_print_header()\n"
msgstr "Error al leer el archivo de prólogo '%s' en f_print_header()\n"
-#: libgeda/src/f_print.c:183
+#: libgeda/src/f_print.c:184
msgid ""
"Error during writing of the output postscript file in f_print_header()\n"
msgstr ""
"Error al escribir el archivo postscript de salida en f_print_header()\n"
-#: libgeda/src/f_print.c:196
+#: libgeda/src/f_print.c:197
msgid "Giving up on printing\n"
msgstr "Se desiste continuar con la impresión\n"
-#: libgeda/src/f_print.c:366
+#: libgeda/src/f_print.c:368
#, c-format
msgid "Could not open [%s] for printing\n"
msgstr "No se puede abrir [%s] para impresión\n"
-#: libgeda/src/f_print.c:399
+#: libgeda/src/f_print.c:402
#, c-format
msgid "Could not execute command [%s] for printing\n"
msgstr "No se puede ejecutar el comando [%s] para impresión\n"
-#: libgeda/src/f_print.c:674
+#: libgeda/src/f_print.c:676
msgid "Too many UTF-8 characters, cannot print\n"
msgstr "Demasiados caracteres UTF-8, no se puede imprimir\n"
-#: libgeda/src/g_basic.c:101
-#, c-format
-msgid "%s:%i:%i: %s\n"
-msgstr "%s:%i:%i: %s\n"
-
-#: libgeda/src/g_basic.c:108
-#, c-format
-msgid "Unknown file: %s\n"
-msgstr "Archivo desconocido: %s\n"
-
-#: libgeda/src/g_basic.c:114
-#, c-format
-msgid "Evaluation failed: %s\n"
-msgstr "Ha fallado la evaluación de: %s\n"
-
-#: libgeda/src/g_basic.c:115
-msgid "Enable debugging for more detailed information\n"
-msgstr "Habilitar la depuración para ver información más detallada\n"
-
-#: libgeda/src/g_basic.c:258
-#, c-format
-msgid "Could not find [%s] for interpretation\n"
-msgstr "No se puede encontrar [%s] para interpretar\n"
+#: libgeda/src/g_basic.c:257
+msgid ""
+"\n"
+"Backtrace:\n"
+msgstr ""
-#: libgeda/src/g_rc.c:134
-#, c-format
-msgid "RC file [%s] already read in.\n"
+#: libgeda/src/g_rc.c:225
+#, fuzzy
+msgid "Config file already loaded"
msgstr "El archivo RC [%s] ya ha sido leÃdo.\n"
-#: libgeda/src/g_rc.c:179
-#, c-format
-msgid "Read system config file [%%s]\n"
-msgstr "LeÃdo archivo de configuración de sistema [%%s]\n"
-
-#: libgeda/src/g_rc.c:180
-#, c-format
-msgid "Did not find required system config file [%%s]\n"
-msgstr ""
-"No se ha encontrado el archivo imprescindible de configuración de sistema "
-"[%%s]\n"
-
-#: libgeda/src/g_rc.c:214
-#, c-format
-msgid "Read user config file [%%s]\n"
+#: libgeda/src/g_rc.c:260
+#, fuzzy, c-format
+msgid "Parsed config from [%s]\n"
msgstr "LeÃdo el archivo de configuración de usuario [%%s]\n"
-#: libgeda/src/g_rc.c:215
-#, c-format
-msgid "Did not find optional user config file [%%s]\n"
-msgstr ""
-"No se ha podido encontrar el archivo opcional de configuración de usuario "
-"[%%s]\n"
-
-#: libgeda/src/g_rc.c:246
-#, c-format
-msgid "Read local config file [%%s]\n"
-msgstr "LeÃdo el archivo local de configuración [%%s]\n"
-
-#: libgeda/src/g_rc.c:247
-#, c-format
-msgid "Did not find optional local config file [%%s]\n"
-msgstr "No se ha podido encontrar el archivo local de configuración [%%s]\n"
+#: libgeda/src/g_rc.c:273
+#, fuzzy, c-format
+msgid "Unable to parse config from [%s]: %s"
+msgstr "Error al cargar imagen desde el archivo [%s]: %s\n"
-#: libgeda/src/g_rc.c:284
-#, c-format
-msgid "Read specified %s file [%%s]\n"
-msgstr "LeÃdo el archivo especificado %s [%%s]\n"
+#: libgeda/src/g_rc.c:290
+msgid "ERROR: An unknown error occurred while parsing configuration files."
+msgstr ""
-#: libgeda/src/g_rc.c:286
+#: libgeda/src/g_rc.c:301 libgeda/src/g_rc.c:302
#, c-format
-msgid "Did not find specified %s file [%%s]\n"
-msgstr "No se ha podido encontrar el archivo especificado %s [%%s]\n"
+msgid "ERROR: %s\n"
+msgstr ""
-#: libgeda/src/g_rc.c:336
+#: libgeda/src/g_rc.c:308
#, c-format
-msgid "Could not find any %s file!\n"
-msgstr "¡No se puede encontrar ningún archivo %s!\n"
+msgid "ERROR: The %s log may contain more information.\n"
+msgstr ""
-#: libgeda/src/g_rc.c:953
+#: libgeda/src/g_rc.c:1003
msgid ""
"WARNING: using a string for 'always-promote-attributes' is deprecated. Use a "
"list of strings instead\n"
@@ -311,7 +268,7 @@ msgstr ""
#: libgeda/src/o_bus_basic.c:182 libgeda/src/o_circle_basic.c:288
#: libgeda/src/o_line_basic.c:264 libgeda/src/o_net_basic.c:174
#: libgeda/src/o_path_basic.c:192 libgeda/src/o_pin_basic.c:187
-#: libgeda/src/o_text_basic.c:419
+#: libgeda/src/o_text_basic.c:420
#, c-format
msgid "Found an invalid color [ %s ]\n"
msgstr "Se ha encontrado un color no válido [%s]\n"
@@ -320,7 +277,7 @@ msgstr "Se ha encontrado un color no válido [%s]\n"
#: libgeda/src/o_bus_basic.c:183 libgeda/src/o_circle_basic.c:289
#: libgeda/src/o_line_basic.c:265 libgeda/src/o_net_basic.c:175
#: libgeda/src/o_path_basic.c:193 libgeda/src/o_pin_basic.c:188
-#: libgeda/src/o_text_basic.c:420
+#: libgeda/src/o_text_basic.c:421
msgid "Setting color to default color\n"
msgstr "Asignando el color por defecto al color\n"
@@ -373,7 +330,7 @@ msgstr "No se permiten cÃrculos con radio cero\n"
msgid "Found a zero radius circle [ %c %d %d %d %d ]\n"
msgstr "Se ha encontrado un cÃrculo con radio cero [ %c %d %d %d %d ]\n"
-#: libgeda/src/o_complex_basic.c:476
+#: libgeda/src/o_complex_basic.c:481
#, c-format
msgid ""
"Component not found:\n"
@@ -382,14 +339,14 @@ msgstr ""
"No se ha encontrado el componente:\n"
" %s"
-#: libgeda/src/o_complex_basic.c:683
+#: libgeda/src/o_complex_basic.c:686
#, c-format
msgid "Found a component with an invalid rotation [ %c %d %d %d %d %d %s ]\n"
msgstr ""
"Se ha encontrado un componente con un ángulo de rotación no válido [ %c %d "
"%d %d %d %d %s ]\n"
-#: libgeda/src/o_complex_basic.c:695
+#: libgeda/src/o_complex_basic.c:698
#, c-format
msgid ""
"Found a component with an invalid mirror flag [ %c %d %d %d %d %d %s ]\n"
@@ -397,7 +354,7 @@ msgstr ""
"Se ha encontrado un componente con un atributo de simetrÃa no válido [ %c %d "
"%d %d %d %d %s ]\n"
-#: libgeda/src/o_complex_basic.c:1008
+#: libgeda/src/o_complex_basic.c:1014
#, c-format
msgid ""
"WARNING: Symbol version parse error on refdes %s:\n"
@@ -406,7 +363,7 @@ msgstr ""
"ADVERTENCIA: Error al obtener la versión de sÃmbolo en la referencia %s:\n"
"\tNo se ha podido procesar el atributo de versión de archivo symversion=%s\n"
-#: libgeda/src/o_complex_basic.c:1012
+#: libgeda/src/o_complex_basic.c:1018
#, c-format
msgid ""
"WARNING: Symbol version parse error on refdes %s:\n"
@@ -415,7 +372,7 @@ msgstr ""
"ADVERTENCIA: Error al obtener la versión de sÃmbolo en la referencia %s:\n"
"\tNo se ha podido procesar el atributo de versión de archivo symversion=\n"
-#: libgeda/src/o_complex_basic.c:1028
+#: libgeda/src/o_complex_basic.c:1034
#, c-format
msgid ""
"WARNING: Symbol version parse error on refdes %s:\n"
@@ -424,7 +381,7 @@ msgstr ""
"ADVERTENCIA: Error al obtener la versión de sÃmbolo en la referencia %s:\n"
"\tNo se ha podido procesar el atributo añadido symversion=%s\n"
-#: libgeda/src/o_complex_basic.c:1053
+#: libgeda/src/o_complex_basic.c:1059
#, c-format
msgid ""
"WARNING: Symbol version oddity on refdes %s:\n"
@@ -436,7 +393,7 @@ msgstr ""
"\tse ha añadido el atributo symversion=%s a la instancia del sÃmbolo, pero "
"no hay ningún atributo symversion= dentro del archivo del sÃmbolo\n"
-#: libgeda/src/o_complex_basic.c:1067
+#: libgeda/src/o_complex_basic.c:1073
#, c-format
msgid ""
"WARNING: Symbol version mismatch on refdes %s (%s):\n"
@@ -447,18 +404,18 @@ msgstr ""
"\t El sÃmbolo en la librerÃa es más reciente que el instanciado en el "
"esquema\n"
-#: libgeda/src/o_complex_basic.c:1095
+#: libgeda/src/o_complex_basic.c:1101
#, c-format
msgid "\tMAJOR VERSION CHANGE (file %.3f, instantiated %.3f, %s)!\n"
msgstr ""
"\t¡CAMBIO DE VERSI�N IMPORTANTE (archivo %.3f, instanciado %.3f, %s)!\n"
-#: libgeda/src/o_complex_basic.c:1113
+#: libgeda/src/o_complex_basic.c:1119
#, c-format
msgid "\tMinor version change (file %.3f, instantiated %.3f)\n"
msgstr "\tCambio menor en la versión (archivo %.3f, instanciado %.3f)\n"
-#: libgeda/src/o_complex_basic.c:1124
+#: libgeda/src/o_complex_basic.c:1130
#, c-format
msgid ""
"WARNING: Symbol version oddity on refdes %s:\n"
@@ -535,12 +492,12 @@ msgid "Found an unsupported picture angle [ %d ]\n"
msgstr ""
"Se ha encontrado una imagen con un ángulo de rotación no válido [ %d ]\n"
-#: libgeda/src/o_picture.c:116 libgeda/src/o_text_basic.c:391
+#: libgeda/src/o_picture.c:116 libgeda/src/o_text_basic.c:392
msgid "Setting angle to 0\n"
msgstr "Cambiando el parámetro 'ángulo' a 0\n"
#: libgeda/src/o_picture.c:151 libgeda/src/o_picture.c:162
-#: libgeda/src/o_picture.c:913
+#: libgeda/src/o_picture.c:914
#, c-format
msgid "Failed to load image from embedded data [%s]: %s\n"
msgstr "Error al cargar imagen desde los datos embebidos [%s]: %s\n"
@@ -550,12 +507,12 @@ msgid "Base64 decoding failed."
msgstr "Ha fallado la decodificación Base64"
#: libgeda/src/o_picture.c:153 libgeda/src/o_picture.c:164
-#: libgeda/src/o_picture.c:915
+#: libgeda/src/o_picture.c:916
msgid "Falling back to file loading. Picture unembedded.\n"
msgstr "Volviendo al modo de carga de archivo. Imagen desincrustada.\n"
-#: libgeda/src/o_picture.c:175 libgeda/src/o_picture.c:901
-#: libgeda/src/o_picture.c:950
+#: libgeda/src/o_picture.c:175 libgeda/src/o_picture.c:902
+#: libgeda/src/o_picture.c:951
#, c-format
msgid "Failed to load image from file [%s]: %s\n"
msgstr "Error al cargar imagen desde el archivo [%s]: %s\n"
@@ -569,16 +526,16 @@ msgstr "Cargando imagen de advertencia.\n"
msgid "Error loading picture from file: %s.\n"
msgstr "Error al cargar la imagen desde el fichero: %s\n"
-#: libgeda/src/o_picture.c:252
+#: libgeda/src/o_picture.c:253
msgid "ERROR: o_picture_save: unable to encode the picture.\n"
msgstr "ERROR: o_picture_save: imposible codificar la imagen.\n"
-#: libgeda/src/o_picture.c:928
+#: libgeda/src/o_picture.c:929
#, c-format
msgid "Picture [%s] has been embedded\n"
msgstr "Se ha incrustado la imagen [%s]\n"
-#: libgeda/src/o_picture.c:968
+#: libgeda/src/o_picture.c:969
#, c-format
msgid "Picture [%s] has been unembedded\n"
msgstr "Se ha desincrustado la imagen [%s]\n"
@@ -602,27 +559,27 @@ msgstr ""
msgid "Found a zero length pin: [ %s ]\n"
msgstr "Se ha encontrado una pata con longitud cero [ %s ]\n"
-#: libgeda/src/o_text_basic.c:377
+#: libgeda/src/o_text_basic.c:378
#, c-format
msgid "Found a zero size text string [ %c %d %d %d %d %d %d %d %d ]\n"
msgstr ""
"Se ha encontrado un texto con tamaño cero [ %c %d %d %d %d %d %d %d %d ]\n"
-#: libgeda/src/o_text_basic.c:389
+#: libgeda/src/o_text_basic.c:390
#, c-format
msgid "Found an unsupported text angle [ %c %d %d %d %d %d %d %d %d ]\n"
msgstr ""
"Se ha encontrado un texto con ángulo no válido [ %c %d %d %d %d %d %d %d "
"%d ]\n"
-#: libgeda/src/o_text_basic.c:411
+#: libgeda/src/o_text_basic.c:412
#, c-format
msgid "Found an unsupported text alignment [ %c %d %d %d %d %d %d %d %d ]\n"
msgstr ""
"Se ha encontrado un texto con alineamiento no válido [ %c %d %d %d %d %d %d "
"%d %d ]\n"
-#: libgeda/src/o_text_basic.c:413
+#: libgeda/src/o_text_basic.c:414
msgid "Setting alignment to LOWER_LEFT\n"
msgstr "Cambiando el alineamiento a 'Abajo a la izquierda'\n"
@@ -730,7 +687,7 @@ msgstr "El Ãndice en la entrada del mapa de colores debe ser un número entero"
msgid "Value in color map entry must be #f or a string"
msgstr "El valor en la entrada del mapa de colores debe ser #f o una cadena"
-#: libgeda/src/s_hierarchy.c:90
+#: libgeda/src/s_hierarchy.c:94
#, c-format
msgid ""
"hierarchy loop detected while visiting page:\n"
@@ -739,11 +696,11 @@ msgstr ""
"Se ha detectado un bucle de jerarquÃa al cargar la página:\n"
" \"%s\"\n"
-#: libgeda/src/s_hierarchy.c:185
+#: libgeda/src/s_hierarchy.c:187
msgid "There are no schematics above the current one!\n"
msgstr "¡No hay más esquemas en un nivel de jerarquÃa superior al actual!\n"
-#: libgeda/src/s_hierarchy.c:266
+#: libgeda/src/s_hierarchy.c:267
#, c-format
msgid "ERROR in s_hierarchy_traverse: schematic not found: %s\n"
msgstr "ERROR: en s_hierarchy_traverse: no se encuentra el esquema %s\n"
@@ -759,12 +716,12 @@ msgid "s_page_delete: Unable to delete backup file %s."
msgstr ""
"s_page_delete: No se ha podido borrar el archivo de copia de seguridad %s."
-#: libgeda/src/s_page.c:504
+#: libgeda/src/s_page.c:499
#, c-format
msgid "Saved [%s]\n"
msgstr "Guardado [%s]\n"
-#: libgeda/src/s_page.c:510
+#: libgeda/src/s_page.c:505
#, c-format
msgid "Could NOT save [%s]\n"
msgstr "No se ha podido guardar [%s]\n"
@@ -779,6 +736,49 @@ msgstr "Encontrado [%s]\n"
msgid "Could not find [%s] in any SourceLibrary\n"
msgstr "No se ha podido encontrar [%s] en ninguna librerÃa fuente\n"
+#~ msgid "%s:%i:%i: %s\n"
+#~ msgstr "%s:%i:%i: %s\n"
+
+#~ msgid "Unknown file: %s\n"
+#~ msgstr "Archivo desconocido: %s\n"
+
+#~ msgid "Evaluation failed: %s\n"
+#~ msgstr "Ha fallado la evaluación de: %s\n"
+
+#~ msgid "Enable debugging for more detailed information\n"
+#~ msgstr "Habilitar la depuración para ver información más detallada\n"
+
+#~ msgid "Could not find [%s] for interpretation\n"
+#~ msgstr "No se puede encontrar [%s] para interpretar\n"
+
+#~ msgid "Read system config file [%%s]\n"
+#~ msgstr "LeÃdo archivo de configuración de sistema [%%s]\n"
+
+#~ msgid "Did not find required system config file [%%s]\n"
+#~ msgstr ""
+#~ "No se ha encontrado el archivo imprescindible de configuración de sistema "
+#~ "[%%s]\n"
+
+#~ msgid "Did not find optional user config file [%%s]\n"
+#~ msgstr ""
+#~ "No se ha podido encontrar el archivo opcional de configuración de usuario "
+#~ "[%%s]\n"
+
+#~ msgid "Read local config file [%%s]\n"
+#~ msgstr "LeÃdo el archivo local de configuración [%%s]\n"
+
+#~ msgid "Did not find optional local config file [%%s]\n"
+#~ msgstr "No se ha podido encontrar el archivo local de configuración [%%s]\n"
+
+#~ msgid "Read specified %s file [%%s]\n"
+#~ msgstr "LeÃdo el archivo especificado %s [%%s]\n"
+
+#~ msgid "Did not find specified %s file [%%s]\n"
+#~ msgstr "No se ha podido encontrar el archivo especificado %s [%%s]\n"
+
+#~ msgid "Could not find any %s file!\n"
+#~ msgstr "¡No se puede encontrar ningún archivo %s!\n"
+
#~ msgid "o_save: Could not open [%s]\n"
#~ msgstr "o_save: No se puede abrir [%s]\n"
diff --git a/libgeda/po/fr.po b/libgeda/po/fr.po
index 8c178c8..08ab32d 100644
--- a/libgeda/po/fr.po
+++ b/libgeda/po/fr.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2010-11-07 10:51+0000\n"
+"POT-Creation-Date: 2011-01-15 23:36-0500\n"
"PO-Revision-Date: 2010-02-06 22:09+0000\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -42,12 +42,12 @@ msgstr "Schéma de Circuit gEDA"
msgid "gEDA Schematic Symbol"
msgstr "Schéma de Symbole gEDA"
-#: libgeda/src/a_basic.c:181
+#: libgeda/src/a_basic.c:182
#, c-format
msgid "o_save_objects: object %p has unknown type '%c'\n"
msgstr "o_save_objects: l'objet %p a un type '%c' inconnu\n"
-#: libgeda/src/a_basic.c:429
+#: libgeda/src/a_basic.c:417
#, c-format
msgid ""
"Read unexpected embedded symbol start marker in [%s] :\n"
@@ -58,7 +58,7 @@ msgstr ""
">>\n"
"%s<<\n"
-#: libgeda/src/a_basic.c:458
+#: libgeda/src/a_basic.c:446
#, c-format
msgid ""
"Read unexpected embedded symbol end marker in [%s] :\n"
@@ -69,7 +69,7 @@ msgstr ""
">>\n"
"%s<<\n"
-#: libgeda/src/a_basic.c:487
+#: libgeda/src/a_basic.c:475
#, c-format
msgid ""
"Read an old format sym/sch file!\n"
@@ -80,7 +80,7 @@ msgstr ""
"Veuillez lancer g[sym|sch]update sur:\n"
"[%s]\n"
-#: libgeda/src/a_basic.c:493
+#: libgeda/src/a_basic.c:481
#, c-format
msgid ""
"Read garbage in [%s] :\n"
@@ -96,12 +96,12 @@ msgstr ""
msgid "Failed to stat [%s]: %s"
msgstr "Impossible d'évaluer [%s]: %s"
-#: libgeda/src/f_basic.c:219
+#: libgeda/src/f_basic.c:221
#, c-format
msgid "Cannot find file %s: %s"
msgstr "Impossible de trouver le fichier %s: %s"
-#: libgeda/src/f_basic.c:257
+#: libgeda/src/f_basic.c:264
#, c-format
msgid ""
"\n"
@@ -114,13 +114,13 @@ msgstr ""
" %s.\n"
"\n"
-#: libgeda/src/f_basic.c:259
+#: libgeda/src/f_basic.c:266
msgid "I could not guess if it is newer, so you have to do it manually.\n"
msgstr ""
"Je n'arrive pas à deviner s'il est plus récent, vous devez le faire "
"manuellement.\n"
-#: libgeda/src/f_basic.c:261
+#: libgeda/src/f_basic.c:268
msgid ""
"The backup copy is newer than the schematic, so it seems you should load it "
"instead of the original file.\n"
@@ -128,7 +128,7 @@ msgstr ""
"La copie de sauvegarde est plus récente que le schéma, vous devriez la "
"charge à la place du fichier originel.\n"
-#: libgeda/src/f_basic.c:263
+#: libgeda/src/f_basic.c:270
msgid ""
"Gschem usually makes backup copies automatically, and this situation happens "
"when it crashed or it was forced to exit abruptly.\n"
@@ -137,7 +137,7 @@ msgstr ""
"situation se produit lorsqu'il a crashé ou qu'il a été obligé de s'arrêter "
"brutalement.\n"
-#: libgeda/src/f_basic.c:266
+#: libgeda/src/f_basic.c:273
msgid ""
"\n"
"Run gschem and correct the situation.\n"
@@ -147,150 +147,111 @@ msgstr ""
"Lancez gschem et corrigez le problème.\n"
"\n"
-#: libgeda/src/f_basic.c:355
+#: libgeda/src/f_basic.c:362
#, c-format
msgid "Can't get the real filename of %s."
msgstr "Impossible d'avoir le nom de fichier réel de %s."
-#: libgeda/src/f_basic.c:375
+#: libgeda/src/f_basic.c:382
#, c-format
msgid "Could NOT set previous backup file [%s] read-write\n"
msgstr ""
"Impossible de passer le fichier copie de sauvegarde [%s] en lecture/"
"écriture\n"
-#: libgeda/src/f_basic.c:381
+#: libgeda/src/f_basic.c:388
#, c-format
msgid "Can't save backup file: %s."
msgstr "Impossible de sauvegarder le fichier de sauvegarde: %s."
-#: libgeda/src/f_basic.c:391
+#: libgeda/src/f_basic.c:398
#, c-format
msgid "Could NOT set backup file [%s] readonly\n"
msgstr ""
"Impossible de passer le fichier copie de sauvegarde [%s] en lecture seule\n"
-#: libgeda/src/f_basic.c:680
+#: libgeda/src/f_basic.c:687
#, c-format
msgid "%s: %s"
msgstr "%s: %s"
-#: libgeda/src/f_print.c:118
+#: libgeda/src/f_print.c:119
msgid "Unable to get time of day in f_print_header()\n"
msgstr "Impossible d'avoir l'heure du jour dans f_print_header()\n"
-#: libgeda/src/f_print.c:160
+#: libgeda/src/f_print.c:161
#, c-format
msgid "Unable to open the prolog file `%s' for reading in f_print_header()\n"
msgstr ""
"Impossible d'ouvrir le fichier prolog `%s' pour lire f_print_header()\n"
-#: libgeda/src/f_print.c:177
+#: libgeda/src/f_print.c:178
#, c-format
msgid "Error during reading of the prolog file `%s' in f_print_header()\n"
msgstr ""
"Erreur pendant la lecture du fichier prolog `%s' avec f_print_header()\n"
-#: libgeda/src/f_print.c:183
+#: libgeda/src/f_print.c:184
msgid ""
"Error during writing of the output postscript file in f_print_header()\n"
msgstr ""
"Erreur pendant l'écriture du fichier postscript de sortie dans f_print_header"
"()\n"
-#: libgeda/src/f_print.c:196
+#: libgeda/src/f_print.c:197
msgid "Giving up on printing\n"
msgstr "Abandon de l'impression\n"
-#: libgeda/src/f_print.c:366
+#: libgeda/src/f_print.c:368
#, c-format
msgid "Could not open [%s] for printing\n"
msgstr "Impossible d'ouvrir [%s] pour l'impression\n"
-#: libgeda/src/f_print.c:399
+#: libgeda/src/f_print.c:402
#, c-format
msgid "Could not execute command [%s] for printing\n"
msgstr "Impossible d'éxecuter la commande [%s] pour l'impression\n"
-#: libgeda/src/f_print.c:674
+#: libgeda/src/f_print.c:676
msgid "Too many UTF-8 characters, cannot print\n"
msgstr "Trop de caractères UTF-8, impossible d'imprimer\n"
-#: libgeda/src/g_basic.c:101
-#, c-format
-msgid "%s:%i:%i: %s\n"
-msgstr "%s:%i:%i: %s\n"
-
-#: libgeda/src/g_basic.c:108
-#, c-format
-msgid "Unknown file: %s\n"
-msgstr "Fichier inconnu: %s\n"
-
-#: libgeda/src/g_basic.c:114
-#, c-format
-msgid "Evaluation failed: %s\n"
-msgstr "�chec de l'évaluation: %s\n"
-
-#: libgeda/src/g_basic.c:115
-msgid "Enable debugging for more detailed information\n"
-msgstr "Validez le débogage pour des informations plus détaillées\n"
-
-#: libgeda/src/g_basic.c:258
-#, c-format
-msgid "Could not find [%s] for interpretation\n"
-msgstr "Impossible de trouver [%s] pour l'interprétation\n"
+#: libgeda/src/g_basic.c:257
+msgid ""
+"\n"
+"Backtrace:\n"
+msgstr ""
-#: libgeda/src/g_rc.c:134
-#, c-format
-msgid "RC file [%s] already read in.\n"
+#: libgeda/src/g_rc.c:225
+#, fuzzy
+msgid "Config file already loaded"
msgstr "Le fichier RC [%s] est déjà lu.\n"
-#: libgeda/src/g_rc.c:179
-#, c-format
-msgid "Read system config file [%%s]\n"
-msgstr "Lecture du fichier de configuration [%%s]\n"
-
-#: libgeda/src/g_rc.c:180
-#, c-format
-msgid "Did not find required system config file [%%s]\n"
-msgstr "Impossible de trouver le fichier de configuration [%%s] nécessaire\n"
-
-#: libgeda/src/g_rc.c:214
-#, c-format
-msgid "Read user config file [%%s]\n"
+#: libgeda/src/g_rc.c:260
+#, fuzzy, c-format
+msgid "Parsed config from [%s]\n"
msgstr "Lecture du fichier de configuration de l'utilisateur [%%s]\n"
-#: libgeda/src/g_rc.c:215
-#, c-format
-msgid "Did not find optional user config file [%%s]\n"
-msgstr "Impossible de trouver le fichier de configuration utiisateur [%%s]\n"
-
-#: libgeda/src/g_rc.c:246
-#, c-format
-msgid "Read local config file [%%s]\n"
-msgstr "Lecture du fichier de configuration local [%%s]\n"
-
-#: libgeda/src/g_rc.c:247
-#, c-format
-msgid "Did not find optional local config file [%%s]\n"
-msgstr "Fichier de configuration local optionnel non trouvé [%%s]\n"
+#: libgeda/src/g_rc.c:273
+#, fuzzy, c-format
+msgid "Unable to parse config from [%s]: %s"
+msgstr "Ã?chec du chargement de l'image depuis le fichier [%s]: %s\n"
-#: libgeda/src/g_rc.c:284
-#, c-format
-msgid "Read specified %s file [%%s]\n"
-msgstr "Lecture du fichier [%%s] spécifié %s\n"
+#: libgeda/src/g_rc.c:290
+msgid "ERROR: An unknown error occurred while parsing configuration files."
+msgstr ""
-#: libgeda/src/g_rc.c:286
+#: libgeda/src/g_rc.c:301 libgeda/src/g_rc.c:302
#, c-format
-msgid "Did not find specified %s file [%%s]\n"
-msgstr "Impossible de trouver le fichier [%%s] spécifié %s\n"
+msgid "ERROR: %s\n"
+msgstr ""
-#: libgeda/src/g_rc.c:336
+#: libgeda/src/g_rc.c:308
#, c-format
-msgid "Could not find any %s file!\n"
-msgstr "Impossible de trouver un seul %s fichier!\n"
+msgid "ERROR: The %s log may contain more information.\n"
+msgstr ""
-#: libgeda/src/g_rc.c:953
+#: libgeda/src/g_rc.c:1003
msgid ""
"WARNING: using a string for 'always-promote-attributes' is deprecated. Use a "
"list of strings instead\n"
@@ -307,7 +268,7 @@ msgstr "Trouvé un arc avec rayon nul [ %c %d, %d, %d, %d, %d, %d ]\n"
#: libgeda/src/o_bus_basic.c:182 libgeda/src/o_circle_basic.c:288
#: libgeda/src/o_line_basic.c:264 libgeda/src/o_net_basic.c:174
#: libgeda/src/o_path_basic.c:192 libgeda/src/o_pin_basic.c:187
-#: libgeda/src/o_text_basic.c:419
+#: libgeda/src/o_text_basic.c:420
#, c-format
msgid "Found an invalid color [ %s ]\n"
msgstr "Trouvé une couleur invalide [ %s ]\n"
@@ -316,7 +277,7 @@ msgstr "Trouvé une couleur invalide [ %s ]\n"
#: libgeda/src/o_bus_basic.c:183 libgeda/src/o_circle_basic.c:289
#: libgeda/src/o_line_basic.c:265 libgeda/src/o_net_basic.c:175
#: libgeda/src/o_path_basic.c:193 libgeda/src/o_pin_basic.c:188
-#: libgeda/src/o_text_basic.c:420
+#: libgeda/src/o_text_basic.c:421
msgid "Setting color to default color\n"
msgstr "Initialiser la couleur comme défaut\n"
@@ -366,7 +327,7 @@ msgstr "Les cercles de rayons nuls ne sont pas permis\n"
msgid "Found a zero radius circle [ %c %d %d %d %d ]\n"
msgstr "Trouvé un cercle de rayon nul [ %c %d %d %d %d ]\n"
-#: libgeda/src/o_complex_basic.c:476
+#: libgeda/src/o_complex_basic.c:481
#, c-format
msgid ""
"Component not found:\n"
@@ -375,13 +336,13 @@ msgstr ""
"Composant non trouvé\n"
" %s"
-#: libgeda/src/o_complex_basic.c:683
+#: libgeda/src/o_complex_basic.c:686
#, c-format
msgid "Found a component with an invalid rotation [ %c %d %d %d %d %d %s ]\n"
msgstr ""
"Trouvé un composant avec une mauvaise rotation [ %c %d %d %d %d %d %s ]\n"
-#: libgeda/src/o_complex_basic.c:695
+#: libgeda/src/o_complex_basic.c:698
#, c-format
msgid ""
"Found a component with an invalid mirror flag [ %c %d %d %d %d %d %s ]\n"
@@ -389,7 +350,7 @@ msgstr ""
"Trouvé un composant avec un marqueur de miroir invalide [ %c %d %d %d %d %d "
"%s ]\n"
-#: libgeda/src/o_complex_basic.c:1008
+#: libgeda/src/o_complex_basic.c:1014
#, c-format
msgid ""
"WARNING: Symbol version parse error on refdes %s:\n"
@@ -398,14 +359,14 @@ msgstr ""
"ATTENTION: erreur du traitement de la version du Symbole sur refdes %s:\n"
"\tImpossible de traiter la version du fichier de symbole symversion=%s\n"
-#: libgeda/src/o_complex_basic.c:1012
+#: libgeda/src/o_complex_basic.c:1018
#, c-format
msgid ""
"WARNING: Symbol version parse error on refdes %s:\n"
"\tCould not parse symbol file symversion=\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:1028
+#: libgeda/src/o_complex_basic.c:1034
#, c-format
msgid ""
"WARNING: Symbol version parse error on refdes %s:\n"
@@ -414,7 +375,7 @@ msgstr ""
"ATTENTION: erreur du traitement de la version du Symbole sur refdes %s:\n"
"\tImpossible de traiter symversion=%s attaché\n"
-#: libgeda/src/o_complex_basic.c:1053
+#: libgeda/src/o_complex_basic.c:1059
#, c-format
msgid ""
"WARNING: Symbol version oddity on refdes %s:\n"
@@ -422,25 +383,25 @@ msgid ""
"symbol file\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:1067
+#: libgeda/src/o_complex_basic.c:1073
#, c-format
msgid ""
"WARNING: Symbol version mismatch on refdes %s (%s):\n"
"\tSymbol in library is newer than instantiated symbol\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:1095
+#: libgeda/src/o_complex_basic.c:1101
#, c-format
msgid "\tMAJOR VERSION CHANGE (file %.3f, instantiated %.3f, %s)!\n"
msgstr ""
"\tCHANGEMENT MAJEUR DE VERSION (fichier %.3f, instantiation %.3f, %s)!\n"
-#: libgeda/src/o_complex_basic.c:1113
+#: libgeda/src/o_complex_basic.c:1119
#, c-format
msgid "\tMinor version change (file %.3f, instantiated %.3f)\n"
msgstr "\tChangement de version mineur (fichier %.3f, instantiation %.3f)\n"
-#: libgeda/src/o_complex_basic.c:1124
+#: libgeda/src/o_complex_basic.c:1130
#, c-format
msgid ""
"WARNING: Symbol version oddity on refdes %s:\n"
@@ -509,12 +470,12 @@ msgstr "Positionne l'embarqué à 0\n"
msgid "Found an unsupported picture angle [ %d ]\n"
msgstr "Trouvé un angle d'image non supporté [ %d ]\n"
-#: libgeda/src/o_picture.c:116 libgeda/src/o_text_basic.c:391
+#: libgeda/src/o_picture.c:116 libgeda/src/o_text_basic.c:392
msgid "Setting angle to 0\n"
msgstr "Initialisé l'angle à 0\n"
#: libgeda/src/o_picture.c:151 libgeda/src/o_picture.c:162
-#: libgeda/src/o_picture.c:913
+#: libgeda/src/o_picture.c:914
#, c-format
msgid "Failed to load image from embedded data [%s]: %s\n"
msgstr ""
@@ -525,12 +486,12 @@ msgid "Base64 decoding failed."
msgstr "�chec du décodage Base64."
#: libgeda/src/o_picture.c:153 libgeda/src/o_picture.c:164
-#: libgeda/src/o_picture.c:915
+#: libgeda/src/o_picture.c:916
msgid "Falling back to file loading. Picture unembedded.\n"
msgstr "�chec du chargement du fichier. Image enlevée.\n"
-#: libgeda/src/o_picture.c:175 libgeda/src/o_picture.c:901
-#: libgeda/src/o_picture.c:950
+#: libgeda/src/o_picture.c:175 libgeda/src/o_picture.c:902
+#: libgeda/src/o_picture.c:951
#, c-format
msgid "Failed to load image from file [%s]: %s\n"
msgstr "Ã?chec du chargement de l'image depuis le fichier [%s]: %s\n"
@@ -544,16 +505,16 @@ msgstr "Chargement de l'image d'avertissement.\n"
msgid "Error loading picture from file: %s.\n"
msgstr "Ã?chec de la lecture de l'image depuis le fichier: %s.\n"
-#: libgeda/src/o_picture.c:252
+#: libgeda/src/o_picture.c:253
msgid "ERROR: o_picture_save: unable to encode the picture.\n"
msgstr "ERROR: o_picture_save: impossible d'encoder l'image.\n"
-#: libgeda/src/o_picture.c:928
+#: libgeda/src/o_picture.c:929
#, c-format
msgid "Picture [%s] has been embedded\n"
msgstr "L'image [%s] a été embarquée\n"
-#: libgeda/src/o_picture.c:968
+#: libgeda/src/o_picture.c:969
#, c-format
msgid "Picture [%s] has been unembedded\n"
msgstr "L'image [%s] a été débarquée\n"
@@ -574,24 +535,24 @@ msgstr ""
msgid "Found a zero length pin: [ %s ]\n"
msgstr "Trouvé une broche à longueur nulle: [ %s ]\n"
-#: libgeda/src/o_text_basic.c:377
+#: libgeda/src/o_text_basic.c:378
#, c-format
msgid "Found a zero size text string [ %c %d %d %d %d %d %d %d %d ]\n"
msgstr ""
"Trouvé une chaîne de texte à longueur nulle [ %c %d %d %d %d %d %d %d %d ]\n"
-#: libgeda/src/o_text_basic.c:389
+#: libgeda/src/o_text_basic.c:390
#, c-format
msgid "Found an unsupported text angle [ %c %d %d %d %d %d %d %d %d ]\n"
msgstr "Trouvé un angle de texte non supporté [ %c %d %d %d %d %d %d %d %d ]\n"
-#: libgeda/src/o_text_basic.c:411
+#: libgeda/src/o_text_basic.c:412
#, c-format
msgid "Found an unsupported text alignment [ %c %d %d %d %d %d %d %d %d ]\n"
msgstr ""
"Trouvé un alignement de texte non supporté [ %c %d %d %d %d %d %d %d %d ]\n"
-#: libgeda/src/o_text_basic.c:413
+#: libgeda/src/o_text_basic.c:414
msgid "Setting alignment to LOWER_LEFT\n"
msgstr "Alignement positionné à LOWER_LEFT\n"
@@ -698,7 +659,7 @@ msgstr ""
"La valeur du champ dans la carte couleur doit être #f ou une chaîne de "
"caractères"
-#: libgeda/src/s_hierarchy.c:90
+#: libgeda/src/s_hierarchy.c:94
#, c-format
msgid ""
"hierarchy loop detected while visiting page:\n"
@@ -707,11 +668,11 @@ msgstr ""
"Boucle hiérarchique détectée lors de la visite de la page:\n"
" \"%s\"\n"
-#: libgeda/src/s_hierarchy.c:185
+#: libgeda/src/s_hierarchy.c:187
msgid "There are no schematics above the current one!\n"
msgstr "Il n'y a pas de schéma au-dessus de celui-ci!\n"
-#: libgeda/src/s_hierarchy.c:266
+#: libgeda/src/s_hierarchy.c:267
#, c-format
msgid "ERROR in s_hierarchy_traverse: schematic not found: %s\n"
msgstr "ERREUR dans s_hierarchy_traverse: schéma non trouvé: %s\n"
@@ -726,12 +687,12 @@ msgstr "s_page_delete: Impossible d'avoir le nom de fichier réel de %s."
msgid "s_page_delete: Unable to delete backup file %s."
msgstr "s_page_delete: Impossible d'effacer le fichier de sauvegarde %s."
-#: libgeda/src/s_page.c:504
+#: libgeda/src/s_page.c:499
#, c-format
msgid "Saved [%s]\n"
msgstr "Sauvegarder [%s]\n"
-#: libgeda/src/s_page.c:510
+#: libgeda/src/s_page.c:505
#, c-format
msgid "Could NOT save [%s]\n"
msgstr "Impossible de sauvegarder [%s]\n"
@@ -746,6 +707,47 @@ msgstr "Trouvé [%s]\n"
msgid "Could not find [%s] in any SourceLibrary\n"
msgstr "Impossible de trouver [%s] dans aucune SourceLibrary\n"
+#~ msgid "%s:%i:%i: %s\n"
+#~ msgstr "%s:%i:%i: %s\n"
+
+#~ msgid "Unknown file: %s\n"
+#~ msgstr "Fichier inconnu: %s\n"
+
+#~ msgid "Evaluation failed: %s\n"
+#~ msgstr "�chec de l'évaluation: %s\n"
+
+#~ msgid "Enable debugging for more detailed information\n"
+#~ msgstr "Validez le débogage pour des informations plus détaillées\n"
+
+#~ msgid "Could not find [%s] for interpretation\n"
+#~ msgstr "Impossible de trouver [%s] pour l'interprétation\n"
+
+#~ msgid "Read system config file [%%s]\n"
+#~ msgstr "Lecture du fichier de configuration [%%s]\n"
+
+#~ msgid "Did not find required system config file [%%s]\n"
+#~ msgstr ""
+#~ "Impossible de trouver le fichier de configuration [%%s] nécessaire\n"
+
+#~ msgid "Did not find optional user config file [%%s]\n"
+#~ msgstr ""
+#~ "Impossible de trouver le fichier de configuration utiisateur [%%s]\n"
+
+#~ msgid "Read local config file [%%s]\n"
+#~ msgstr "Lecture du fichier de configuration local [%%s]\n"
+
+#~ msgid "Did not find optional local config file [%%s]\n"
+#~ msgstr "Fichier de configuration local optionnel non trouvé [%%s]\n"
+
+#~ msgid "Read specified %s file [%%s]\n"
+#~ msgstr "Lecture du fichier [%%s] spécifié %s\n"
+
+#~ msgid "Did not find specified %s file [%%s]\n"
+#~ msgstr "Impossible de trouver le fichier [%%s] spécifié %s\n"
+
+#~ msgid "Could not find any %s file!\n"
+#~ msgstr "Impossible de trouver un seul %s fichier!\n"
+
#~ msgid "o_save: Could not open [%s]\n"
#~ msgstr "o_save: Impossible d'ouvrir [%s]\n"
diff --git a/libgeda/po/hu.po b/libgeda/po/hu.po
index 65b134b..3f2f642 100644
--- a/libgeda/po/hu.po
+++ b/libgeda/po/hu.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2010-11-07 10:51+0000\n"
+"POT-Creation-Date: 2011-01-15 23:36-0500\n"
"PO-Revision-Date: 2010-02-06 22:11+0000\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -42,12 +42,12 @@ msgstr "gEDA kapcsolási rajz"
msgid "gEDA Schematic Symbol"
msgstr "gEDA szimbólum"
-#: libgeda/src/a_basic.c:181
+#: libgeda/src/a_basic.c:182
#, c-format
msgid "o_save_objects: object %p has unknown type '%c'\n"
msgstr ""
-#: libgeda/src/a_basic.c:429
+#: libgeda/src/a_basic.c:417
#, c-format
msgid ""
"Read unexpected embedded symbol start marker in [%s] :\n"
@@ -55,7 +55,7 @@ msgid ""
"%s<<\n"
msgstr ""
-#: libgeda/src/a_basic.c:458
+#: libgeda/src/a_basic.c:446
#, c-format
msgid ""
"Read unexpected embedded symbol end marker in [%s] :\n"
@@ -63,7 +63,7 @@ msgid ""
"%s<<\n"
msgstr ""
-#: libgeda/src/a_basic.c:487
+#: libgeda/src/a_basic.c:475
#, c-format
msgid ""
"Read an old format sym/sch file!\n"
@@ -74,7 +74,7 @@ msgstr ""
"Kérlek frissÃtsd a [%s] fájlt a\n"
"g[sym|sch]update program segÃtségével!\n"
-#: libgeda/src/a_basic.c:493
+#: libgeda/src/a_basic.c:481
#, c-format
msgid ""
"Read garbage in [%s] :\n"
@@ -90,12 +90,12 @@ msgstr ""
msgid "Failed to stat [%s]: %s"
msgstr ""
-#: libgeda/src/f_basic.c:219
+#: libgeda/src/f_basic.c:221
#, c-format
msgid "Cannot find file %s: %s"
msgstr ""
-#: libgeda/src/f_basic.c:257
+#: libgeda/src/f_basic.c:264
#, c-format
msgid ""
"\n"
@@ -104,166 +104,126 @@ msgid ""
"\n"
msgstr ""
-#: libgeda/src/f_basic.c:259
+#: libgeda/src/f_basic.c:266
msgid "I could not guess if it is newer, so you have to do it manually.\n"
msgstr ""
-#: libgeda/src/f_basic.c:261
+#: libgeda/src/f_basic.c:268
msgid ""
"The backup copy is newer than the schematic, so it seems you should load it "
"instead of the original file.\n"
msgstr ""
-#: libgeda/src/f_basic.c:263
+#: libgeda/src/f_basic.c:270
msgid ""
"Gschem usually makes backup copies automatically, and this situation happens "
"when it crashed or it was forced to exit abruptly.\n"
msgstr ""
-#: libgeda/src/f_basic.c:266
+#: libgeda/src/f_basic.c:273
msgid ""
"\n"
"Run gschem and correct the situation.\n"
"\n"
msgstr ""
-#: libgeda/src/f_basic.c:355
+#: libgeda/src/f_basic.c:362
#, c-format
msgid "Can't get the real filename of %s."
msgstr ""
-#: libgeda/src/f_basic.c:375
+#: libgeda/src/f_basic.c:382
#, c-format
msgid "Could NOT set previous backup file [%s] read-write\n"
msgstr ""
-#: libgeda/src/f_basic.c:381
+#: libgeda/src/f_basic.c:388
#, c-format
msgid "Can't save backup file: %s."
msgstr ""
-#: libgeda/src/f_basic.c:391
+#: libgeda/src/f_basic.c:398
#, c-format
msgid "Could NOT set backup file [%s] readonly\n"
msgstr ""
-#: libgeda/src/f_basic.c:680
+#: libgeda/src/f_basic.c:687
#, c-format
msgid "%s: %s"
msgstr "%s: %s"
-#: libgeda/src/f_print.c:118
+#: libgeda/src/f_print.c:119
msgid "Unable to get time of day in f_print_header()\n"
msgstr ""
-#: libgeda/src/f_print.c:160
+#: libgeda/src/f_print.c:161
#, c-format
msgid "Unable to open the prolog file `%s' for reading in f_print_header()\n"
msgstr ""
-#: libgeda/src/f_print.c:177
+#: libgeda/src/f_print.c:178
#, c-format
msgid "Error during reading of the prolog file `%s' in f_print_header()\n"
msgstr ""
-#: libgeda/src/f_print.c:183
+#: libgeda/src/f_print.c:184
msgid ""
"Error during writing of the output postscript file in f_print_header()\n"
msgstr ""
-#: libgeda/src/f_print.c:196
+#: libgeda/src/f_print.c:197
msgid "Giving up on printing\n"
msgstr ""
-#: libgeda/src/f_print.c:366
+#: libgeda/src/f_print.c:368
#, c-format
msgid "Could not open [%s] for printing\n"
msgstr ""
-#: libgeda/src/f_print.c:399
+#: libgeda/src/f_print.c:402
#, c-format
msgid "Could not execute command [%s] for printing\n"
msgstr ""
-#: libgeda/src/f_print.c:674
+#: libgeda/src/f_print.c:676
msgid "Too many UTF-8 characters, cannot print\n"
msgstr "Túl sok UTF-8 karakter, nem tudom kinyomtatni\n"
-#: libgeda/src/g_basic.c:101
-#, c-format
-msgid "%s:%i:%i: %s\n"
-msgstr "%s:%i:%i: %s\n"
-
-#: libgeda/src/g_basic.c:108
-#, c-format
-msgid "Unknown file: %s\n"
-msgstr "Ismeretlen fájl: %s\n"
-
-#: libgeda/src/g_basic.c:114
-#, c-format
-msgid "Evaluation failed: %s\n"
-msgstr ""
-
-#: libgeda/src/g_basic.c:115
-msgid "Enable debugging for more detailed information\n"
-msgstr ""
-
-#: libgeda/src/g_basic.c:258
-#, c-format
-msgid "Could not find [%s] for interpretation\n"
-msgstr ""
-
-#: libgeda/src/g_rc.c:134
-#, c-format
-msgid "RC file [%s] already read in.\n"
-msgstr ""
-
-#: libgeda/src/g_rc.c:179
-#, c-format
-msgid "Read system config file [%%s]\n"
-msgstr ""
-
-#: libgeda/src/g_rc.c:180
-#, c-format
-msgid "Did not find required system config file [%%s]\n"
-msgstr ""
-
-#: libgeda/src/g_rc.c:214
-#, c-format
-msgid "Read user config file [%%s]\n"
+#: libgeda/src/g_basic.c:257
+msgid ""
+"\n"
+"Backtrace:\n"
msgstr ""
-#: libgeda/src/g_rc.c:215
-#, c-format
-msgid "Did not find optional user config file [%%s]\n"
+#: libgeda/src/g_rc.c:225
+msgid "Config file already loaded"
msgstr ""
-#: libgeda/src/g_rc.c:246
+#: libgeda/src/g_rc.c:260
#, c-format
-msgid "Read local config file [%%s]\n"
+msgid "Parsed config from [%s]\n"
msgstr ""
-#: libgeda/src/g_rc.c:247
+#: libgeda/src/g_rc.c:273
#, c-format
-msgid "Did not find optional local config file [%%s]\n"
+msgid "Unable to parse config from [%s]: %s"
msgstr ""
-#: libgeda/src/g_rc.c:284
-#, c-format
-msgid "Read specified %s file [%%s]\n"
+#: libgeda/src/g_rc.c:290
+msgid "ERROR: An unknown error occurred while parsing configuration files."
msgstr ""
-#: libgeda/src/g_rc.c:286
+#: libgeda/src/g_rc.c:301 libgeda/src/g_rc.c:302
#, c-format
-msgid "Did not find specified %s file [%%s]\n"
+msgid "ERROR: %s\n"
msgstr ""
-#: libgeda/src/g_rc.c:336
+#: libgeda/src/g_rc.c:308
#, c-format
-msgid "Could not find any %s file!\n"
+msgid "ERROR: The %s log may contain more information.\n"
msgstr ""
-#: libgeda/src/g_rc.c:953
+#: libgeda/src/g_rc.c:1003
msgid ""
"WARNING: using a string for 'always-promote-attributes' is deprecated. Use a "
"list of strings instead\n"
@@ -278,7 +238,7 @@ msgstr ""
#: libgeda/src/o_bus_basic.c:182 libgeda/src/o_circle_basic.c:288
#: libgeda/src/o_line_basic.c:264 libgeda/src/o_net_basic.c:174
#: libgeda/src/o_path_basic.c:192 libgeda/src/o_pin_basic.c:187
-#: libgeda/src/o_text_basic.c:419
+#: libgeda/src/o_text_basic.c:420
#, c-format
msgid "Found an invalid color [ %s ]\n"
msgstr ""
@@ -287,7 +247,7 @@ msgstr ""
#: libgeda/src/o_bus_basic.c:183 libgeda/src/o_circle_basic.c:289
#: libgeda/src/o_line_basic.c:265 libgeda/src/o_net_basic.c:175
#: libgeda/src/o_path_basic.c:193 libgeda/src/o_pin_basic.c:188
-#: libgeda/src/o_text_basic.c:420
+#: libgeda/src/o_text_basic.c:421
msgid "Setting color to default color\n"
msgstr ""
@@ -336,46 +296,46 @@ msgstr ""
msgid "Found a zero radius circle [ %c %d %d %d %d ]\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:476
+#: libgeda/src/o_complex_basic.c:481
#, c-format
msgid ""
"Component not found:\n"
" %s"
msgstr ""
-#: libgeda/src/o_complex_basic.c:683
+#: libgeda/src/o_complex_basic.c:686
#, c-format
msgid "Found a component with an invalid rotation [ %c %d %d %d %d %d %s ]\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:695
+#: libgeda/src/o_complex_basic.c:698
#, c-format
msgid ""
"Found a component with an invalid mirror flag [ %c %d %d %d %d %d %s ]\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:1008
+#: libgeda/src/o_complex_basic.c:1014
#, c-format
msgid ""
"WARNING: Symbol version parse error on refdes %s:\n"
"\tCould not parse symbol file symversion=%s\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:1012
+#: libgeda/src/o_complex_basic.c:1018
#, c-format
msgid ""
"WARNING: Symbol version parse error on refdes %s:\n"
"\tCould not parse symbol file symversion=\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:1028
+#: libgeda/src/o_complex_basic.c:1034
#, c-format
msgid ""
"WARNING: Symbol version parse error on refdes %s:\n"
"\tCould not parse attached symversion=%s\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:1053
+#: libgeda/src/o_complex_basic.c:1059
#, c-format
msgid ""
"WARNING: Symbol version oddity on refdes %s:\n"
@@ -383,24 +343,24 @@ msgid ""
"symbol file\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:1067
+#: libgeda/src/o_complex_basic.c:1073
#, c-format
msgid ""
"WARNING: Symbol version mismatch on refdes %s (%s):\n"
"\tSymbol in library is newer than instantiated symbol\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:1095
+#: libgeda/src/o_complex_basic.c:1101
#, c-format
msgid "\tMAJOR VERSION CHANGE (file %.3f, instantiated %.3f, %s)!\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:1113
+#: libgeda/src/o_complex_basic.c:1119
#, c-format
msgid "\tMinor version change (file %.3f, instantiated %.3f)\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:1124
+#: libgeda/src/o_complex_basic.c:1130
#, c-format
msgid ""
"WARNING: Symbol version oddity on refdes %s:\n"
@@ -467,12 +427,12 @@ msgstr ""
msgid "Found an unsupported picture angle [ %d ]\n"
msgstr ""
-#: libgeda/src/o_picture.c:116 libgeda/src/o_text_basic.c:391
+#: libgeda/src/o_picture.c:116 libgeda/src/o_text_basic.c:392
msgid "Setting angle to 0\n"
msgstr ""
#: libgeda/src/o_picture.c:151 libgeda/src/o_picture.c:162
-#: libgeda/src/o_picture.c:913
+#: libgeda/src/o_picture.c:914
#, c-format
msgid "Failed to load image from embedded data [%s]: %s\n"
msgstr ""
@@ -482,12 +442,12 @@ msgid "Base64 decoding failed."
msgstr ""
#: libgeda/src/o_picture.c:153 libgeda/src/o_picture.c:164
-#: libgeda/src/o_picture.c:915
+#: libgeda/src/o_picture.c:916
msgid "Falling back to file loading. Picture unembedded.\n"
msgstr ""
-#: libgeda/src/o_picture.c:175 libgeda/src/o_picture.c:901
-#: libgeda/src/o_picture.c:950
+#: libgeda/src/o_picture.c:175 libgeda/src/o_picture.c:902
+#: libgeda/src/o_picture.c:951
#, c-format
msgid "Failed to load image from file [%s]: %s\n"
msgstr ""
@@ -501,16 +461,16 @@ msgstr ""
msgid "Error loading picture from file: %s.\n"
msgstr ""
-#: libgeda/src/o_picture.c:252
+#: libgeda/src/o_picture.c:253
msgid "ERROR: o_picture_save: unable to encode the picture.\n"
msgstr ""
-#: libgeda/src/o_picture.c:928
+#: libgeda/src/o_picture.c:929
#, c-format
msgid "Picture [%s] has been embedded\n"
msgstr ""
-#: libgeda/src/o_picture.c:968
+#: libgeda/src/o_picture.c:969
#, c-format
msgid "Picture [%s] has been unembedded\n"
msgstr ""
@@ -531,22 +491,22 @@ msgstr ""
msgid "Found a zero length pin: [ %s ]\n"
msgstr ""
-#: libgeda/src/o_text_basic.c:377
+#: libgeda/src/o_text_basic.c:378
#, c-format
msgid "Found a zero size text string [ %c %d %d %d %d %d %d %d %d ]\n"
msgstr ""
-#: libgeda/src/o_text_basic.c:389
+#: libgeda/src/o_text_basic.c:390
#, c-format
msgid "Found an unsupported text angle [ %c %d %d %d %d %d %d %d %d ]\n"
msgstr ""
-#: libgeda/src/o_text_basic.c:411
+#: libgeda/src/o_text_basic.c:412
#, c-format
msgid "Found an unsupported text alignment [ %c %d %d %d %d %d %d %d %d ]\n"
msgstr ""
-#: libgeda/src/o_text_basic.c:413
+#: libgeda/src/o_text_basic.c:414
msgid "Setting alignment to LOWER_LEFT\n"
msgstr ""
@@ -643,18 +603,18 @@ msgstr ""
msgid "Value in color map entry must be #f or a string"
msgstr ""
-#: libgeda/src/s_hierarchy.c:90
+#: libgeda/src/s_hierarchy.c:94
#, c-format
msgid ""
"hierarchy loop detected while visiting page:\n"
" \"%s\"\n"
msgstr ""
-#: libgeda/src/s_hierarchy.c:185
+#: libgeda/src/s_hierarchy.c:187
msgid "There are no schematics above the current one!\n"
msgstr ""
-#: libgeda/src/s_hierarchy.c:266
+#: libgeda/src/s_hierarchy.c:267
#, c-format
msgid "ERROR in s_hierarchy_traverse: schematic not found: %s\n"
msgstr ""
@@ -669,12 +629,12 @@ msgstr ""
msgid "s_page_delete: Unable to delete backup file %s."
msgstr ""
-#: libgeda/src/s_page.c:504
+#: libgeda/src/s_page.c:499
#, c-format
msgid "Saved [%s]\n"
msgstr ""
-#: libgeda/src/s_page.c:510
+#: libgeda/src/s_page.c:505
#, c-format
msgid "Could NOT save [%s]\n"
msgstr ""
@@ -689,6 +649,12 @@ msgstr ""
msgid "Could not find [%s] in any SourceLibrary\n"
msgstr ""
+#~ msgid "%s:%i:%i: %s\n"
+#~ msgstr "%s:%i:%i: %s\n"
+
+#~ msgid "Unknown file: %s\n"
+#~ msgstr "Ismeretlen fájl: %s\n"
+
#~ msgid "Could not read symbolic link information for %s"
#~ msgstr "%s szimbolikus link adatai nem olvashatóak"
diff --git a/libgeda/po/it.po b/libgeda/po/it.po
index 321a2f2..1a28e05 100644
--- a/libgeda/po/it.po
+++ b/libgeda/po/it.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2010-11-07 10:51+0000\n"
+"POT-Creation-Date: 2011-01-15 23:36-0500\n"
"PO-Revision-Date: 2010-02-06 22:09+0000\n"
"Last-Translator: Plinio Gatto <plinio.gatto@xxxxxxxxx>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -42,12 +42,12 @@ msgstr "gEDA Schema Circuitale"
msgid "gEDA Schematic Symbol"
msgstr "gEDA Simbolo di Circuito"
-#: libgeda/src/a_basic.c:181
+#: libgeda/src/a_basic.c:182
#, c-format
msgid "o_save_objects: object %p has unknown type '%c'\n"
msgstr "o_save_objects: l'oggetto %p ha il tipo sconosciuto '%c'\n"
-#: libgeda/src/a_basic.c:429
+#: libgeda/src/a_basic.c:417
#, c-format
msgid ""
"Read unexpected embedded symbol start marker in [%s] :\n"
@@ -55,7 +55,7 @@ msgid ""
"%s<<\n"
msgstr ""
-#: libgeda/src/a_basic.c:458
+#: libgeda/src/a_basic.c:446
#, c-format
msgid ""
"Read unexpected embedded symbol end marker in [%s] :\n"
@@ -63,7 +63,7 @@ msgid ""
"%s<<\n"
msgstr ""
-#: libgeda/src/a_basic.c:487
+#: libgeda/src/a_basic.c:475
#, c-format
msgid ""
"Read an old format sym/sch file!\n"
@@ -74,7 +74,7 @@ msgstr ""
"Esegui g[sym|sch]update su:\n"
"[%s]\n"
-#: libgeda/src/a_basic.c:493
+#: libgeda/src/a_basic.c:481
#, c-format
msgid ""
"Read garbage in [%s] :\n"
@@ -90,12 +90,12 @@ msgstr ""
msgid "Failed to stat [%s]: %s"
msgstr ""
-#: libgeda/src/f_basic.c:219
+#: libgeda/src/f_basic.c:221
#, c-format
msgid "Cannot find file %s: %s"
msgstr ""
-#: libgeda/src/f_basic.c:257
+#: libgeda/src/f_basic.c:264
#, c-format
msgid ""
"\n"
@@ -108,11 +108,11 @@ msgstr ""
" %s.\n"
"\n"
-#: libgeda/src/f_basic.c:259
+#: libgeda/src/f_basic.c:266
msgid "I could not guess if it is newer, so you have to do it manually.\n"
msgstr "Impossibile stabilire se è nuovo, quindi devi farlo manualmente.\n"
-#: libgeda/src/f_basic.c:261
+#: libgeda/src/f_basic.c:268
msgid ""
"The backup copy is newer than the schematic, so it seems you should load it "
"instead of the original file.\n"
@@ -120,7 +120,7 @@ msgstr ""
"La copia di backup è più recente dello schema, quindi dovrebbe essere "
"utilizzata al posto del file originale.\n"
-#: libgeda/src/f_basic.c:263
+#: libgeda/src/f_basic.c:270
msgid ""
"Gschem usually makes backup copies automatically, and this situation happens "
"when it crashed or it was forced to exit abruptly.\n"
@@ -129,7 +129,7 @@ msgstr ""
"situazione capita in caso di suoi errori gravi o quando viene interrotto "
"forzatamente.\n"
-#: libgeda/src/f_basic.c:266
+#: libgeda/src/f_basic.c:273
msgid ""
"\n"
"Run gschem and correct the situation.\n"
@@ -139,148 +139,109 @@ msgstr ""
"Esegui gschem e correggi la situazione.\n"
"\n"
-#: libgeda/src/f_basic.c:355
+#: libgeda/src/f_basic.c:362
#, c-format
msgid "Can't get the real filename of %s."
msgstr "Impossibile trovare il nomefile reale di %s."
-#: libgeda/src/f_basic.c:375
+#: libgeda/src/f_basic.c:382
#, c-format
msgid "Could NOT set previous backup file [%s] read-write\n"
msgstr ""
"Non è possibile impostare il precedente file di ripristino [%s] in lettura-"
"scrittura\n"
-#: libgeda/src/f_basic.c:381
+#: libgeda/src/f_basic.c:388
#, c-format
msgid "Can't save backup file: %s."
msgstr "Impossibile salvare il file di backup: %s."
-#: libgeda/src/f_basic.c:391
+#: libgeda/src/f_basic.c:398
#, c-format
msgid "Could NOT set backup file [%s] readonly\n"
msgstr "Impossibile impostare il file di backup [%s] in sola lettura.\n"
-#: libgeda/src/f_basic.c:680
+#: libgeda/src/f_basic.c:687
#, c-format
msgid "%s: %s"
msgstr ""
-#: libgeda/src/f_print.c:118
+#: libgeda/src/f_print.c:119
msgid "Unable to get time of day in f_print_header()\n"
msgstr "Non riesco a ottenere l'ora del giorno in f_print_header()\n"
-#: libgeda/src/f_print.c:160
+#: libgeda/src/f_print.c:161
#, c-format
msgid "Unable to open the prolog file `%s' for reading in f_print_header()\n"
msgstr ""
"Non riesco ad aprire il prolog file '%s' in lettura in f_print_header()\n"
-#: libgeda/src/f_print.c:177
+#: libgeda/src/f_print.c:178
#, c-format
msgid "Error during reading of the prolog file `%s' in f_print_header()\n"
msgstr "Errore durante la lettura del file prolog '%s' in f_print_header()\n"
-#: libgeda/src/f_print.c:183
+#: libgeda/src/f_print.c:184
msgid ""
"Error during writing of the output postscript file in f_print_header()\n"
msgstr ""
"Errore durante la scrittura del file postscript di output in f_print_header"
"()\n"
-#: libgeda/src/f_print.c:196
+#: libgeda/src/f_print.c:197
msgid "Giving up on printing\n"
msgstr "Rinunciare alla stampa\n"
-#: libgeda/src/f_print.c:366
+#: libgeda/src/f_print.c:368
#, c-format
msgid "Could not open [%s] for printing\n"
msgstr "Impossibile aprire [%s] per la stampa\n"
-#: libgeda/src/f_print.c:399
+#: libgeda/src/f_print.c:402
#, c-format
msgid "Could not execute command [%s] for printing\n"
msgstr "Impossibile eseguire il comando [%s] per la stampa\n"
-#: libgeda/src/f_print.c:674
+#: libgeda/src/f_print.c:676
msgid "Too many UTF-8 characters, cannot print\n"
msgstr "Troppi caratteri UTF-8, impossibile stampare\n"
-#: libgeda/src/g_basic.c:101
-#, c-format
-msgid "%s:%i:%i: %s\n"
-msgstr "%s:%i:%i: %s\n"
-
-#: libgeda/src/g_basic.c:108
-#, c-format
-msgid "Unknown file: %s\n"
-msgstr "File sconosciuto: %s\n"
-
-#: libgeda/src/g_basic.c:114
-#, c-format
-msgid "Evaluation failed: %s\n"
-msgstr "Prova fallita: %s\n"
-
-#: libgeda/src/g_basic.c:115
-msgid "Enable debugging for more detailed information\n"
-msgstr "Abilita il debugging per informazioni più dettagliate\n"
-
-#: libgeda/src/g_basic.c:258
-#, c-format
-msgid "Could not find [%s] for interpretation\n"
-msgstr "Non trovo [%s] per l'interpretazione\n"
-
-#: libgeda/src/g_rc.c:134
-#, c-format
-msgid "RC file [%s] already read in.\n"
-msgstr "Il file RC [%s] è stato già letto.\n"
-
-#: libgeda/src/g_rc.c:179
-#, c-format
-msgid "Read system config file [%%s]\n"
-msgstr ""
-
-#: libgeda/src/g_rc.c:180
-#, c-format
-msgid "Did not find required system config file [%%s]\n"
+#: libgeda/src/g_basic.c:257
+msgid ""
+"\n"
+"Backtrace:\n"
msgstr ""
-#: libgeda/src/g_rc.c:214
-#, c-format
-msgid "Read user config file [%%s]\n"
-msgstr ""
+#: libgeda/src/g_rc.c:225
+#, fuzzy
+msgid "Config file already loaded"
+msgstr "Il file RC [%s] è stato già letto.\n"
-#: libgeda/src/g_rc.c:215
+#: libgeda/src/g_rc.c:260
#, c-format
-msgid "Did not find optional user config file [%%s]\n"
+msgid "Parsed config from [%s]\n"
msgstr ""
-#: libgeda/src/g_rc.c:246
+#: libgeda/src/g_rc.c:273
#, c-format
-msgid "Read local config file [%%s]\n"
+msgid "Unable to parse config from [%s]: %s"
msgstr ""
-#: libgeda/src/g_rc.c:247
-#, c-format
-msgid "Did not find optional local config file [%%s]\n"
+#: libgeda/src/g_rc.c:290
+msgid "ERROR: An unknown error occurred while parsing configuration files."
msgstr ""
-#: libgeda/src/g_rc.c:284
+#: libgeda/src/g_rc.c:301 libgeda/src/g_rc.c:302
#, c-format
-msgid "Read specified %s file [%%s]\n"
+msgid "ERROR: %s\n"
msgstr ""
-#: libgeda/src/g_rc.c:286
+#: libgeda/src/g_rc.c:308
#, c-format
-msgid "Did not find specified %s file [%%s]\n"
+msgid "ERROR: The %s log may contain more information.\n"
msgstr ""
-#: libgeda/src/g_rc.c:336
-#, c-format
-msgid "Could not find any %s file!\n"
-msgstr "Non trovo alcun %s file!\n"
-
-#: libgeda/src/g_rc.c:953
+#: libgeda/src/g_rc.c:1003
msgid ""
"WARNING: using a string for 'always-promote-attributes' is deprecated. Use a "
"list of strings instead\n"
@@ -295,7 +256,7 @@ msgstr ""
#: libgeda/src/o_bus_basic.c:182 libgeda/src/o_circle_basic.c:288
#: libgeda/src/o_line_basic.c:264 libgeda/src/o_net_basic.c:174
#: libgeda/src/o_path_basic.c:192 libgeda/src/o_pin_basic.c:187
-#: libgeda/src/o_text_basic.c:419
+#: libgeda/src/o_text_basic.c:420
#, c-format
msgid "Found an invalid color [ %s ]\n"
msgstr "Trovato un colore non valido [%s]\n"
@@ -304,7 +265,7 @@ msgstr "Trovato un colore non valido [%s]\n"
#: libgeda/src/o_bus_basic.c:183 libgeda/src/o_circle_basic.c:289
#: libgeda/src/o_line_basic.c:265 libgeda/src/o_net_basic.c:175
#: libgeda/src/o_path_basic.c:193 libgeda/src/o_pin_basic.c:188
-#: libgeda/src/o_text_basic.c:420
+#: libgeda/src/o_text_basic.c:421
msgid "Setting color to default color\n"
msgstr ""
@@ -353,7 +314,7 @@ msgstr ""
msgid "Found a zero radius circle [ %c %d %d %d %d ]\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:476
+#: libgeda/src/o_complex_basic.c:481
#, c-format
msgid ""
"Component not found:\n"
@@ -362,39 +323,39 @@ msgstr ""
"Componente non trovato:\n"
" %s"
-#: libgeda/src/o_complex_basic.c:683
+#: libgeda/src/o_complex_basic.c:686
#, c-format
msgid "Found a component with an invalid rotation [ %c %d %d %d %d %d %s ]\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:695
+#: libgeda/src/o_complex_basic.c:698
#, c-format
msgid ""
"Found a component with an invalid mirror flag [ %c %d %d %d %d %d %s ]\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:1008
+#: libgeda/src/o_complex_basic.c:1014
#, c-format
msgid ""
"WARNING: Symbol version parse error on refdes %s:\n"
"\tCould not parse symbol file symversion=%s\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:1012
+#: libgeda/src/o_complex_basic.c:1018
#, c-format
msgid ""
"WARNING: Symbol version parse error on refdes %s:\n"
"\tCould not parse symbol file symversion=\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:1028
+#: libgeda/src/o_complex_basic.c:1034
#, c-format
msgid ""
"WARNING: Symbol version parse error on refdes %s:\n"
"\tCould not parse attached symversion=%s\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:1053
+#: libgeda/src/o_complex_basic.c:1059
#, c-format
msgid ""
"WARNING: Symbol version oddity on refdes %s:\n"
@@ -402,24 +363,24 @@ msgid ""
"symbol file\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:1067
+#: libgeda/src/o_complex_basic.c:1073
#, c-format
msgid ""
"WARNING: Symbol version mismatch on refdes %s (%s):\n"
"\tSymbol in library is newer than instantiated symbol\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:1095
+#: libgeda/src/o_complex_basic.c:1101
#, c-format
msgid "\tMAJOR VERSION CHANGE (file %.3f, instantiated %.3f, %s)!\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:1113
+#: libgeda/src/o_complex_basic.c:1119
#, c-format
msgid "\tMinor version change (file %.3f, instantiated %.3f)\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:1124
+#: libgeda/src/o_complex_basic.c:1130
#, c-format
msgid ""
"WARNING: Symbol version oddity on refdes %s:\n"
@@ -486,12 +447,12 @@ msgstr ""
msgid "Found an unsupported picture angle [ %d ]\n"
msgstr ""
-#: libgeda/src/o_picture.c:116 libgeda/src/o_text_basic.c:391
+#: libgeda/src/o_picture.c:116 libgeda/src/o_text_basic.c:392
msgid "Setting angle to 0\n"
msgstr ""
#: libgeda/src/o_picture.c:151 libgeda/src/o_picture.c:162
-#: libgeda/src/o_picture.c:913
+#: libgeda/src/o_picture.c:914
#, c-format
msgid "Failed to load image from embedded data [%s]: %s\n"
msgstr ""
@@ -501,12 +462,12 @@ msgid "Base64 decoding failed."
msgstr ""
#: libgeda/src/o_picture.c:153 libgeda/src/o_picture.c:164
-#: libgeda/src/o_picture.c:915
+#: libgeda/src/o_picture.c:916
msgid "Falling back to file loading. Picture unembedded.\n"
msgstr ""
-#: libgeda/src/o_picture.c:175 libgeda/src/o_picture.c:901
-#: libgeda/src/o_picture.c:950
+#: libgeda/src/o_picture.c:175 libgeda/src/o_picture.c:902
+#: libgeda/src/o_picture.c:951
#, c-format
msgid "Failed to load image from file [%s]: %s\n"
msgstr ""
@@ -520,16 +481,16 @@ msgstr ""
msgid "Error loading picture from file: %s.\n"
msgstr ""
-#: libgeda/src/o_picture.c:252
+#: libgeda/src/o_picture.c:253
msgid "ERROR: o_picture_save: unable to encode the picture.\n"
msgstr ""
-#: libgeda/src/o_picture.c:928
+#: libgeda/src/o_picture.c:929
#, c-format
msgid "Picture [%s] has been embedded\n"
msgstr ""
-#: libgeda/src/o_picture.c:968
+#: libgeda/src/o_picture.c:969
#, c-format
msgid "Picture [%s] has been unembedded\n"
msgstr ""
@@ -550,22 +511,22 @@ msgstr ""
msgid "Found a zero length pin: [ %s ]\n"
msgstr ""
-#: libgeda/src/o_text_basic.c:377
+#: libgeda/src/o_text_basic.c:378
#, c-format
msgid "Found a zero size text string [ %c %d %d %d %d %d %d %d %d ]\n"
msgstr ""
-#: libgeda/src/o_text_basic.c:389
+#: libgeda/src/o_text_basic.c:390
#, c-format
msgid "Found an unsupported text angle [ %c %d %d %d %d %d %d %d %d ]\n"
msgstr ""
-#: libgeda/src/o_text_basic.c:411
+#: libgeda/src/o_text_basic.c:412
#, c-format
msgid "Found an unsupported text alignment [ %c %d %d %d %d %d %d %d %d ]\n"
msgstr ""
-#: libgeda/src/o_text_basic.c:413
+#: libgeda/src/o_text_basic.c:414
msgid "Setting alignment to LOWER_LEFT\n"
msgstr ""
@@ -662,18 +623,18 @@ msgstr ""
msgid "Value in color map entry must be #f or a string"
msgstr ""
-#: libgeda/src/s_hierarchy.c:90
+#: libgeda/src/s_hierarchy.c:94
#, c-format
msgid ""
"hierarchy loop detected while visiting page:\n"
" \"%s\"\n"
msgstr ""
-#: libgeda/src/s_hierarchy.c:185
+#: libgeda/src/s_hierarchy.c:187
msgid "There are no schematics above the current one!\n"
msgstr ""
-#: libgeda/src/s_hierarchy.c:266
+#: libgeda/src/s_hierarchy.c:267
#, c-format
msgid "ERROR in s_hierarchy_traverse: schematic not found: %s\n"
msgstr ""
@@ -688,12 +649,12 @@ msgstr ""
msgid "s_page_delete: Unable to delete backup file %s."
msgstr ""
-#: libgeda/src/s_page.c:504
+#: libgeda/src/s_page.c:499
#, c-format
msgid "Saved [%s]\n"
msgstr ""
-#: libgeda/src/s_page.c:510
+#: libgeda/src/s_page.c:505
#, c-format
msgid "Could NOT save [%s]\n"
msgstr ""
@@ -708,6 +669,24 @@ msgstr ""
msgid "Could not find [%s] in any SourceLibrary\n"
msgstr ""
+#~ msgid "%s:%i:%i: %s\n"
+#~ msgstr "%s:%i:%i: %s\n"
+
+#~ msgid "Unknown file: %s\n"
+#~ msgstr "File sconosciuto: %s\n"
+
+#~ msgid "Evaluation failed: %s\n"
+#~ msgstr "Prova fallita: %s\n"
+
+#~ msgid "Enable debugging for more detailed information\n"
+#~ msgstr "Abilita il debugging per informazioni più dettagliate\n"
+
+#~ msgid "Could not find [%s] for interpretation\n"
+#~ msgstr "Non trovo [%s] per l'interpretazione\n"
+
+#~ msgid "Could not find any %s file!\n"
+#~ msgstr "Non trovo alcun %s file!\n"
+
#~ msgid "o_save: Could not open [%s]\n"
#~ msgstr "o_save: Impossibile aprire [%s]\n"
diff --git a/libgeda/po/nl.po b/libgeda/po/nl.po
index 405a147..8cbe316 100644
--- a/libgeda/po/nl.po
+++ b/libgeda/po/nl.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2010-11-07 10:51+0000\n"
+"POT-Creation-Date: 2011-01-15 23:36-0500\n"
"PO-Revision-Date: 2010-01-31 13:00+0000\n"
"Last-Translator: lambert63 <bert.timmerman@xxxxxxxxx>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -45,12 +45,12 @@ msgid "gEDA Schematic Symbol"
msgstr "gEDA Schema Symbool"
# ! \todo Misschien kunnen wij doorgaan in plaats van compleet falen? In elk geval, gracieus falen is beter dan het programma om zeep helpen, wat gewoonlijk gebeurt zou zijn...
-#: libgeda/src/a_basic.c:181
+#: libgeda/src/a_basic.c:182
#, c-format
msgid "o_save_objects: object %p has unknown type '%c'\n"
msgstr "o_save_objects: object %p heeft een onbekend type '%c'\n"
-#: libgeda/src/a_basic.c:429
+#: libgeda/src/a_basic.c:417
#, c-format
msgid ""
"Read unexpected embedded symbol start marker in [%s] :\n"
@@ -61,7 +61,7 @@ msgstr ""
">>\n"
"%s<<\n"
-#: libgeda/src/a_basic.c:458
+#: libgeda/src/a_basic.c:446
#, c-format
msgid ""
"Read unexpected embedded symbol end marker in [%s] :\n"
@@ -72,7 +72,7 @@ msgstr ""
">>\n"
"%s<<\n"
-#: libgeda/src/a_basic.c:487
+#: libgeda/src/a_basic.c:475
#, c-format
msgid ""
"Read an old format sym/sch file!\n"
@@ -83,7 +83,7 @@ msgstr ""
"Voer g[sym|sch]update uit op:\n"
"[%s]\n"
-#: libgeda/src/a_basic.c:493
+#: libgeda/src/a_basic.c:481
#, c-format
msgid ""
"Read garbage in [%s] :\n"
@@ -99,12 +99,12 @@ msgstr ""
msgid "Failed to stat [%s]: %s"
msgstr "Status niet gelukt [%s]: %s"
-#: libgeda/src/f_basic.c:219
+#: libgeda/src/f_basic.c:221
#, c-format
msgid "Cannot find file %s: %s"
msgstr "Kan bestand %s niet vinden: %s"
-#: libgeda/src/f_basic.c:257
+#: libgeda/src/f_basic.c:264
#, c-format
msgid ""
"\n"
@@ -117,11 +117,11 @@ msgstr ""
" %s.\n"
"\n"
-#: libgeda/src/f_basic.c:259
+#: libgeda/src/f_basic.c:266
msgid "I could not guess if it is newer, so you have to do it manually.\n"
msgstr "Ik kan niet raden of het nieuwer is, je moet het dus handmatig doen.\n"
-#: libgeda/src/f_basic.c:261
+#: libgeda/src/f_basic.c:268
msgid ""
"The backup copy is newer than the schematic, so it seems you should load it "
"instead of the original file.\n"
@@ -129,7 +129,7 @@ msgstr ""
"De reservekopie is nieuwer dan het schema, het lijkt erop dat je deze zou "
"moeten laden in plaats van het orginele bestand.\n"
-#: libgeda/src/f_basic.c:263
+#: libgeda/src/f_basic.c:270
msgid ""
"Gschem usually makes backup copies automatically, and this situation happens "
"when it crashed or it was forced to exit abruptly.\n"
@@ -138,7 +138,7 @@ msgstr ""
"voor wanneer er een crash is of wanneer er een abrupte gedwongen beeindiging "
"was.\n"
-#: libgeda/src/f_basic.c:266
+#: libgeda/src/f_basic.c:273
msgid ""
"\n"
"Run gschem and correct the situation.\n"
@@ -148,149 +148,108 @@ msgstr ""
"Voer gschem uit en corrigeer de situatie.\n"
"\n"
-#: libgeda/src/f_basic.c:355
+#: libgeda/src/f_basic.c:362
#, c-format
msgid "Can't get the real filename of %s."
msgstr "Kan de werkelijke bestandsnaam van %s niet krijgen."
-#: libgeda/src/f_basic.c:375
+#: libgeda/src/f_basic.c:382
#, c-format
msgid "Could NOT set previous backup file [%s] read-write\n"
msgstr "Kan vorige reservekopie [%s] NIET op lezen-schrijven instellen\n"
-#: libgeda/src/f_basic.c:381
+#: libgeda/src/f_basic.c:388
#, c-format
msgid "Can't save backup file: %s."
msgstr "Kan reservekopie niet opslaan: %s."
-#: libgeda/src/f_basic.c:391
+#: libgeda/src/f_basic.c:398
#, c-format
msgid "Could NOT set backup file [%s] readonly\n"
msgstr "Kan reservekopie [%s] NIET op alleen-lezen instellen\n"
-#: libgeda/src/f_basic.c:680
+#: libgeda/src/f_basic.c:687
#, c-format
msgid "%s: %s"
msgstr "%s: %s"
-#: libgeda/src/f_print.c:118
+#: libgeda/src/f_print.c:119
msgid "Unable to get time of day in f_print_header()\n"
msgstr "Kan geen tijd van de dag krijgen in f_print_header()\n"
-#: libgeda/src/f_print.c:160
+#: libgeda/src/f_print.c:161
#, c-format
msgid "Unable to open the prolog file `%s' for reading in f_print_header()\n"
msgstr ""
"Kan het prolog bestand `%s' niet openen tijdens lezen in f_print_header()\n"
-#: libgeda/src/f_print.c:177
+#: libgeda/src/f_print.c:178
#, c-format
msgid "Error during reading of the prolog file `%s' in f_print_header()\n"
msgstr "Fout tijdens het lezen van prolog bestand `%s' in f_print_header()\n"
-#: libgeda/src/f_print.c:183
+#: libgeda/src/f_print.c:184
msgid ""
"Error during writing of the output postscript file in f_print_header()\n"
msgstr ""
"Fout tijdens het schrijven van het postscript uitvoerbestand in "
"f_print_header()\n"
-#: libgeda/src/f_print.c:196
+#: libgeda/src/f_print.c:197
msgid "Giving up on printing\n"
msgstr "Geef het afdrukken op\n"
-#: libgeda/src/f_print.c:366
+#: libgeda/src/f_print.c:368
#, c-format
msgid "Could not open [%s] for printing\n"
msgstr "Kan [%s] niet openen voor afdrukken\n"
-#: libgeda/src/f_print.c:399
+#: libgeda/src/f_print.c:402
#, c-format
msgid "Could not execute command [%s] for printing\n"
msgstr "Kan opdracht [%s] niet uitvoeren voor afdrukken\n"
-#: libgeda/src/f_print.c:674
+#: libgeda/src/f_print.c:676
msgid "Too many UTF-8 characters, cannot print\n"
msgstr "Te veel UTF-8 karakters, kan niet afdrukken\n"
-#: libgeda/src/g_basic.c:101
-#, c-format
-msgid "%s:%i:%i: %s\n"
-msgstr "%s:%i:%i: %s\n"
-
-#: libgeda/src/g_basic.c:108
-#, c-format
-msgid "Unknown file: %s\n"
-msgstr "Onbekend bestand: %s\n"
-
-# Geen stapel, kan geen fout informatie laten zien
-#: libgeda/src/g_basic.c:114
-#, c-format
-msgid "Evaluation failed: %s\n"
-msgstr "Evaluatie faalt: %s\n"
-
-#: libgeda/src/g_basic.c:115
-msgid "Enable debugging for more detailed information\n"
-msgstr "Schakel foutzoeken in voor meer gedetaileerde informatie\n"
-
-#: libgeda/src/g_basic.c:258
-#, c-format
-msgid "Could not find [%s] for interpretation\n"
-msgstr "Kan [%s] niet vinden voor interpretatie\n"
+#: libgeda/src/g_basic.c:257
+msgid ""
+"\n"
+"Backtrace:\n"
+msgstr ""
# We hebben deze al ingelezen.
-#: libgeda/src/g_rc.c:134
-#, c-format
-msgid "RC file [%s] already read in.\n"
+#: libgeda/src/g_rc.c:225
+#, fuzzy
+msgid "Config file already loaded"
msgstr "RC bestand [%s] is reeds ingelezen.\n"
-#: libgeda/src/g_rc.c:179
-#, c-format
-msgid "Read system config file [%%s]\n"
-msgstr "Lees systeem configuratie bestand [%%s]\n"
-
-#: libgeda/src/g_rc.c:180
-#, c-format
-msgid "Did not find required system config file [%%s]\n"
-msgstr "Benodigde systeem configuratie bestand is niet gevonden [%%s]\n"
-
-#: libgeda/src/g_rc.c:214
-#, c-format
-msgid "Read user config file [%%s]\n"
+#: libgeda/src/g_rc.c:260
+#, fuzzy, c-format
+msgid "Parsed config from [%s]\n"
msgstr "Lees gebruiker configuratie bestand [%%s]\n"
-#: libgeda/src/g_rc.c:215
-#, c-format
-msgid "Did not find optional user config file [%%s]\n"
-msgstr "Kan geen optioneel gebruiker configuratie bestand [%%s] vinden\n"
-
-#: libgeda/src/g_rc.c:246
-#, c-format
-msgid "Read local config file [%%s]\n"
-msgstr "Lees plaatselijk configuratie bestand [%%s]\n"
-
-#: libgeda/src/g_rc.c:247
-#, c-format
-msgid "Did not find optional local config file [%%s]\n"
-msgstr "Kan geen optioneel plaatselijk configuratie bestand [%%s] vinden\n"
+#: libgeda/src/g_rc.c:273
+#, fuzzy, c-format
+msgid "Unable to parse config from [%s]: %s"
+msgstr "Laden van afbeelding uit bestand faalde [%s]: %s\n"
-#: libgeda/src/g_rc.c:284
-#, c-format
-msgid "Read specified %s file [%%s]\n"
-msgstr "Lees gespecificeerd %s bestand [%%s]\n"
+#: libgeda/src/g_rc.c:290
+msgid "ERROR: An unknown error occurred while parsing configuration files."
+msgstr ""
-#: libgeda/src/g_rc.c:286
+#: libgeda/src/g_rc.c:301 libgeda/src/g_rc.c:302
#, c-format
-msgid "Did not find specified %s file [%%s]\n"
-msgstr "Kan geen gespecificeerd %s bestand [%%s] vinden\n"
+msgid "ERROR: %s\n"
+msgstr ""
-# ! \todo deze twee zijn eigenlijk het zelfde. inefficient!
-#: libgeda/src/g_rc.c:336
+#: libgeda/src/g_rc.c:308
#, c-format
-msgid "Could not find any %s file!\n"
-msgstr "Kan geen enkel %s bestand vinden!\n"
+msgid "ERROR: The %s log may contain more information.\n"
+msgstr ""
-#: libgeda/src/g_rc.c:953
+#: libgeda/src/g_rc.c:1003
msgid ""
"WARNING: using a string for 'always-promote-attributes' is deprecated. Use a "
"list of strings instead\n"
@@ -307,7 +266,7 @@ msgstr "Boog met een straal van nul gevonden [ %c %d, %d, %d, %d, %d, %d ]\n"
#: libgeda/src/o_bus_basic.c:182 libgeda/src/o_circle_basic.c:288
#: libgeda/src/o_line_basic.c:264 libgeda/src/o_net_basic.c:174
#: libgeda/src/o_path_basic.c:192 libgeda/src/o_pin_basic.c:187
-#: libgeda/src/o_text_basic.c:419
+#: libgeda/src/o_text_basic.c:420
#, c-format
msgid "Found an invalid color [ %s ]\n"
msgstr "Ongeldige kleur [ %s ] gevonden\n"
@@ -316,7 +275,7 @@ msgstr "Ongeldige kleur [ %s ] gevonden\n"
#: libgeda/src/o_bus_basic.c:183 libgeda/src/o_circle_basic.c:289
#: libgeda/src/o_line_basic.c:265 libgeda/src/o_net_basic.c:175
#: libgeda/src/o_path_basic.c:193 libgeda/src/o_pin_basic.c:188
-#: libgeda/src/o_text_basic.c:420
+#: libgeda/src/o_text_basic.c:421
msgid "Setting color to default color\n"
msgstr "Stel de kleur in op standaard kleur\n"
@@ -366,7 +325,7 @@ msgstr "Cirkels met een radius van nul zijn niet toegestaan\n"
msgid "Found a zero radius circle [ %c %d %d %d %d ]\n"
msgstr "Een cirkel met een radius van nul gevonden [ %c %d %d %d %d ]\n"
-#: libgeda/src/o_complex_basic.c:476
+#: libgeda/src/o_complex_basic.c:481
#, c-format
msgid ""
"Component not found:\n"
@@ -375,13 +334,13 @@ msgstr ""
"Komponent niet gevonden:\n"
" %s"
-#: libgeda/src/o_complex_basic.c:683
+#: libgeda/src/o_complex_basic.c:686
#, c-format
msgid "Found a component with an invalid rotation [ %c %d %d %d %d %d %s ]\n"
msgstr ""
"Een komponent met een ongeldige rotatie gevonden [ %c %d %d %d %d %d %s ]\n"
-#: libgeda/src/o_complex_basic.c:695
+#: libgeda/src/o_complex_basic.c:698
#, c-format
msgid ""
"Found a component with an invalid mirror flag [ %c %d %d %d %d %d %s ]\n"
@@ -389,7 +348,7 @@ msgstr ""
"Een komponent met een ongeldige spiegel vlag gevonden [ %c %d %d %d %d %d "
"%s ]\n"
-#: libgeda/src/o_complex_basic.c:1008
+#: libgeda/src/o_complex_basic.c:1014
#, c-format
msgid ""
"WARNING: Symbol version parse error on refdes %s:\n"
@@ -398,7 +357,7 @@ msgstr ""
"WAARSCHUWING: Symbool versie zoek fout bij refdes %s:\n"
"\tKan symboolbestand niet doorzoeken symversion=%s\n"
-#: libgeda/src/o_complex_basic.c:1012
+#: libgeda/src/o_complex_basic.c:1018
#, c-format
msgid ""
"WARNING: Symbol version parse error on refdes %s:\n"
@@ -407,7 +366,7 @@ msgstr ""
"WAARSCHUWING: Symbool versie zoek fout bij refdes %s:\n"
"\tKan symboolbestand niet doorzoeken symversion=\n"
-#: libgeda/src/o_complex_basic.c:1028
+#: libgeda/src/o_complex_basic.c:1034
#, c-format
msgid ""
"WARNING: Symbol version parse error on refdes %s:\n"
@@ -416,7 +375,7 @@ msgstr ""
"WAARSCHUWING: Symbool versie zoek fout bij refdes %s:\n"
"\tKan bijgevoegd symboolbestand niet doorzoeken symversion=%s\n"
-#: libgeda/src/o_complex_basic.c:1053
+#: libgeda/src/o_complex_basic.c:1059
#, c-format
msgid ""
"WARNING: Symbol version oddity on refdes %s:\n"
@@ -427,7 +386,7 @@ msgstr ""
"\tsymversion=%s bijgevoegd aan bedoelde symbool, maar geen symversion= in "
"het symbool bestand\n"
-#: libgeda/src/o_complex_basic.c:1067
+#: libgeda/src/o_complex_basic.c:1073
#, c-format
msgid ""
"WARNING: Symbol version mismatch on refdes %s (%s):\n"
@@ -436,17 +395,17 @@ msgstr ""
"WAARSCHUWING: Symbool versie fout bij refdes %s (%s):\n"
"\tSymbool in bibliotheek is nieuwer dan bedoelde symbool\n"
-#: libgeda/src/o_complex_basic.c:1095
+#: libgeda/src/o_complex_basic.c:1101
#, c-format
msgid "\tMAJOR VERSION CHANGE (file %.3f, instantiated %.3f, %s)!\n"
msgstr "\tGROTE VERSIE VERANDERING (bestand %.3f, bedoeld %.3f, %s)!\n"
-#: libgeda/src/o_complex_basic.c:1113
+#: libgeda/src/o_complex_basic.c:1119
#, c-format
msgid "\tMinor version change (file %.3f, instantiated %.3f)\n"
msgstr "\tKleine versie verandering (bestand %.3f, bedoeld %.3f)!\n"
-#: libgeda/src/o_complex_basic.c:1124
+#: libgeda/src/o_complex_basic.c:1130
#, c-format
msgid ""
"WARNING: Symbol version oddity on refdes %s:\n"
@@ -519,12 +478,12 @@ msgstr "Invoegen op 0 ingesteld\n"
msgid "Found an unsupported picture angle [ %d ]\n"
msgstr "Niet ondersteunde afbeelding hoek [ %d ] gevonden\n"
-#: libgeda/src/o_picture.c:116 libgeda/src/o_text_basic.c:391
+#: libgeda/src/o_picture.c:116 libgeda/src/o_text_basic.c:392
msgid "Setting angle to 0\n"
msgstr "Hoek op 0 ingesteld\n"
#: libgeda/src/o_picture.c:151 libgeda/src/o_picture.c:162
-#: libgeda/src/o_picture.c:913
+#: libgeda/src/o_picture.c:914
#, c-format
msgid "Failed to load image from embedded data [%s]: %s\n"
msgstr "Laden van afbeelding uit ingesloten data faalde [%s]: %s\n"
@@ -534,12 +493,12 @@ msgid "Base64 decoding failed."
msgstr "Base64 decodering faalde."
#: libgeda/src/o_picture.c:153 libgeda/src/o_picture.c:164
-#: libgeda/src/o_picture.c:915
+#: libgeda/src/o_picture.c:916
msgid "Falling back to file loading. Picture unembedded.\n"
msgstr "Val terug op het laden van bestand. Afbeelding uitgevoegd.\n"
-#: libgeda/src/o_picture.c:175 libgeda/src/o_picture.c:901
-#: libgeda/src/o_picture.c:950
+#: libgeda/src/o_picture.c:175 libgeda/src/o_picture.c:902
+#: libgeda/src/o_picture.c:951
#, c-format
msgid "Failed to load image from file [%s]: %s\n"
msgstr "Laden van afbeelding uit bestand faalde [%s]: %s\n"
@@ -553,16 +512,16 @@ msgstr "Laad de waarschuwing afbeelding.\n"
msgid "Error loading picture from file: %s.\n"
msgstr "Fout bij het laden van een afbeelding uit een bestand: %s.\n"
-#: libgeda/src/o_picture.c:252
+#: libgeda/src/o_picture.c:253
msgid "ERROR: o_picture_save: unable to encode the picture.\n"
msgstr "FOUT: o_picture_save: kan de afbeelding niet coderen.\n"
-#: libgeda/src/o_picture.c:928
+#: libgeda/src/o_picture.c:929
#, c-format
msgid "Picture [%s] has been embedded\n"
msgstr "Afbeelding [%s] is ingevoegd\n"
-#: libgeda/src/o_picture.c:968
+#: libgeda/src/o_picture.c:969
#, c-format
msgid "Picture [%s] has been unembedded\n"
msgstr "Afbeelding [%s] is uitgevoegd\n"
@@ -585,25 +544,25 @@ msgstr "Pen met een ongeldige whichend gevonden (instellen op nul): %d\n"
msgid "Found a zero length pin: [ %s ]\n"
msgstr "Pen met een lengte van nul gevonden: [ %s ]\n"
-#: libgeda/src/o_text_basic.c:377
+#: libgeda/src/o_text_basic.c:378
#, c-format
msgid "Found a zero size text string [ %c %d %d %d %d %d %d %d %d ]\n"
msgstr ""
"Tekst string met een afmeting van nul gevonden [ %c %d %d %d %d %d %d %d "
"%d ]\n"
-#: libgeda/src/o_text_basic.c:389
+#: libgeda/src/o_text_basic.c:390
#, c-format
msgid "Found an unsupported text angle [ %c %d %d %d %d %d %d %d %d ]\n"
msgstr "Niet ondersteunde teksthoek gevonden [ %c %d %d %d %d %d %d %d %d ]\n"
-#: libgeda/src/o_text_basic.c:411
+#: libgeda/src/o_text_basic.c:412
#, c-format
msgid "Found an unsupported text alignment [ %c %d %d %d %d %d %d %d %d ]\n"
msgstr ""
"Niet ondersteunde tekst uitlijning gevonden [ %c %d %d %d %d %d %d %d %d ]\n"
-#: libgeda/src/o_text_basic.c:413
+#: libgeda/src/o_text_basic.c:414
msgid "Setting alignment to LOWER_LEFT\n"
msgstr "Uitlijning op LINKS_ONDER ingesteld\n"
@@ -710,7 +669,7 @@ msgstr "Index in kleuren map invoer moet een integer zijn"
msgid "Value in color map entry must be #f or a string"
msgstr "Waarde in kleuren map invoer moet een #f of een string zijn"
-#: libgeda/src/s_hierarchy.c:90
+#: libgeda/src/s_hierarchy.c:94
#, c-format
msgid ""
"hierarchy loop detected while visiting page:\n"
@@ -719,11 +678,11 @@ msgstr ""
"hierarchie lus gedetecteerd tijdens het bezoeken van pagina:\n"
" \"%s\"\n"
-#: libgeda/src/s_hierarchy.c:185
+#: libgeda/src/s_hierarchy.c:187
msgid "There are no schematics above the current one!\n"
msgstr "Er zijn geen schema's boven de huidige!\n"
-#: libgeda/src/s_hierarchy.c:266
+#: libgeda/src/s_hierarchy.c:267
#, c-format
msgid "ERROR in s_hierarchy_traverse: schematic not found: %s\n"
msgstr "FOUT in s_hierarchy_traverse: schema niet gevonden: %s\n"
@@ -738,12 +697,12 @@ msgstr "s_page_delete: Kan de echte bestandsnaam van %s niet krijgen."
msgid "s_page_delete: Unable to delete backup file %s."
msgstr "s_page_delete: Niet mogelijk om reservekopie %s te verwijderen."
-#: libgeda/src/s_page.c:504
+#: libgeda/src/s_page.c:499
#, c-format
msgid "Saved [%s]\n"
msgstr "[%s] opgeslagen\n"
-#: libgeda/src/s_page.c:510
+#: libgeda/src/s_page.c:505
#, c-format
msgid "Could NOT save [%s]\n"
msgstr "Kan [%s] NIET opslaan\n"
@@ -758,6 +717,47 @@ msgstr "[%s] gevonden\n"
msgid "Could not find [%s] in any SourceLibrary\n"
msgstr "Kan geen [%s] vinden in welke BronBibliotheek dan ook!\n"
+#~ msgid "%s:%i:%i: %s\n"
+#~ msgstr "%s:%i:%i: %s\n"
+
+#~ msgid "Unknown file: %s\n"
+#~ msgstr "Onbekend bestand: %s\n"
+
+# Geen stapel, kan geen fout informatie laten zien
+#~ msgid "Evaluation failed: %s\n"
+#~ msgstr "Evaluatie faalt: %s\n"
+
+#~ msgid "Enable debugging for more detailed information\n"
+#~ msgstr "Schakel foutzoeken in voor meer gedetaileerde informatie\n"
+
+#~ msgid "Could not find [%s] for interpretation\n"
+#~ msgstr "Kan [%s] niet vinden voor interpretatie\n"
+
+#~ msgid "Read system config file [%%s]\n"
+#~ msgstr "Lees systeem configuratie bestand [%%s]\n"
+
+#~ msgid "Did not find required system config file [%%s]\n"
+#~ msgstr "Benodigde systeem configuratie bestand is niet gevonden [%%s]\n"
+
+#~ msgid "Did not find optional user config file [%%s]\n"
+#~ msgstr "Kan geen optioneel gebruiker configuratie bestand [%%s] vinden\n"
+
+#~ msgid "Read local config file [%%s]\n"
+#~ msgstr "Lees plaatselijk configuratie bestand [%%s]\n"
+
+#~ msgid "Did not find optional local config file [%%s]\n"
+#~ msgstr "Kan geen optioneel plaatselijk configuratie bestand [%%s] vinden\n"
+
+#~ msgid "Read specified %s file [%%s]\n"
+#~ msgstr "Lees gespecificeerd %s bestand [%%s]\n"
+
+#~ msgid "Did not find specified %s file [%%s]\n"
+#~ msgstr "Kan geen gespecificeerd %s bestand [%%s] vinden\n"
+
+# ! \todo deze twee zijn eigenlijk het zelfde. inefficient!
+#~ msgid "Could not find any %s file!\n"
+#~ msgstr "Kan geen enkel %s bestand vinden!\n"
+
#~ msgid "o_save: Could not open [%s]\n"
#~ msgstr "o_save: Kan [%s] niet openen\n"
diff --git a/libgeda/po/pl.po b/libgeda/po/pl.po
index a5e166d..f939f2f 100644
--- a/libgeda/po/pl.po
+++ b/libgeda/po/pl.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2010-11-07 10:51+0000\n"
+"POT-Creation-Date: 2011-01-15 23:36-0500\n"
"PO-Revision-Date: 2010-02-06 22:09+0000\n"
"Last-Translator: JarosÅ?aw Ogrodnik <nobodythere@xxxxxxxxx>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -42,12 +42,12 @@ msgstr "Schemat Obwodu gEDA"
msgid "gEDA Schematic Symbol"
msgstr "Element Schematu gEDA"
-#: libgeda/src/a_basic.c:181
+#: libgeda/src/a_basic.c:182
#, c-format
msgid "o_save_objects: object %p has unknown type '%c'\n"
msgstr "o_save_objects: objekt %p jest nieznanego typu '%c'\n"
-#: libgeda/src/a_basic.c:429
+#: libgeda/src/a_basic.c:417
#, c-format
msgid ""
"Read unexpected embedded symbol start marker in [%s] :\n"
@@ -58,7 +58,7 @@ msgstr ""
">>\n"
"%s<<\n"
-#: libgeda/src/a_basic.c:458
+#: libgeda/src/a_basic.c:446
#, c-format
msgid ""
"Read unexpected embedded symbol end marker in [%s] :\n"
@@ -69,7 +69,7 @@ msgstr ""
">>\n"
"%s<<\n"
-#: libgeda/src/a_basic.c:487
+#: libgeda/src/a_basic.c:475
#, c-format
msgid ""
"Read an old format sym/sch file!\n"
@@ -80,7 +80,7 @@ msgstr ""
"Uruchom program gsymupdate/gschemupdate na pliku:\n"
"[%s]\n"
-#: libgeda/src/a_basic.c:493
+#: libgeda/src/a_basic.c:481
#, c-format
msgid ""
"Read garbage in [%s] :\n"
@@ -96,12 +96,12 @@ msgstr ""
msgid "Failed to stat [%s]: %s"
msgstr "BÅ?Ä?d odczytu atrybutów [%s]: %s"
-#: libgeda/src/f_basic.c:219
+#: libgeda/src/f_basic.c:221
#, c-format
msgid "Cannot find file %s: %s"
msgstr "Nie odnaleziono pliku %s: %s"
-#: libgeda/src/f_basic.c:257
+#: libgeda/src/f_basic.c:264
#, c-format
msgid ""
"\n"
@@ -114,12 +114,12 @@ msgstr ""
" %s.\n"
"\n"
-#: libgeda/src/f_basic.c:259
+#: libgeda/src/f_basic.c:266
msgid "I could not guess if it is newer, so you have to do it manually.\n"
msgstr ""
"Nie można stwierdziÄ?, czy kopia jest nowsza - musisz sprawdziÄ? to rÄ?cznie.\n"
-#: libgeda/src/f_basic.c:261
+#: libgeda/src/f_basic.c:268
msgid ""
"The backup copy is newer than the schematic, so it seems you should load it "
"instead of the original file.\n"
@@ -127,7 +127,7 @@ msgstr ""
"Kopia zapasowa jest nowsza niż plik schematu, a wiÄ?c powinieneÅ? otworzyÄ? "
"kopiÄ? zamiast oryginalnego pliku.\n"
-#: libgeda/src/f_basic.c:263
+#: libgeda/src/f_basic.c:270
msgid ""
"Gschem usually makes backup copies automatically, and this situation happens "
"when it crashed or it was forced to exit abruptly.\n"
@@ -135,7 +135,7 @@ msgstr ""
"Gschem tworzy kopie zapasowe automatycznie, a ta sytuacja może byÄ? wynikiem "
"niepoprawnego zamkniÄ?cia programu, np. z powodu bÅ?Ä?du.\n"
-#: libgeda/src/f_basic.c:266
+#: libgeda/src/f_basic.c:273
msgid ""
"\n"
"Run gschem and correct the situation.\n"
@@ -145,145 +145,106 @@ msgstr ""
"Uruchom gschem i napraw plik rÄ?cznie.\n"
"\n"
-#: libgeda/src/f_basic.c:355
+#: libgeda/src/f_basic.c:362
#, c-format
msgid "Can't get the real filename of %s."
msgstr "Nie można odczytaÄ? rzeczywistej nazwy %s."
-#: libgeda/src/f_basic.c:375
+#: libgeda/src/f_basic.c:382
#, c-format
msgid "Could NOT set previous backup file [%s] read-write\n"
msgstr "Nie można ustawiÄ? pliku kopii zapasowej w tryb zapisu i odczytu [%s]\n"
-#: libgeda/src/f_basic.c:381
+#: libgeda/src/f_basic.c:388
#, c-format
msgid "Can't save backup file: %s."
msgstr "Nie można zapisaÄ? kopii zapasowej: %s."
-#: libgeda/src/f_basic.c:391
+#: libgeda/src/f_basic.c:398
#, c-format
msgid "Could NOT set backup file [%s] readonly\n"
msgstr ""
"Nie można ustawiÄ? pliku kopii zapasowej w tryb tylko do odczytu [%s].\n"
-#: libgeda/src/f_basic.c:680
+#: libgeda/src/f_basic.c:687
#, c-format
msgid "%s: %s"
msgstr "%s: %s"
-#: libgeda/src/f_print.c:118
+#: libgeda/src/f_print.c:119
msgid "Unable to get time of day in f_print_header()\n"
msgstr "BÅ?Ä?d odczytu pory dnia w f_print_header()\n"
-#: libgeda/src/f_print.c:160
+#: libgeda/src/f_print.c:161
#, c-format
msgid "Unable to open the prolog file `%s' for reading in f_print_header()\n"
msgstr "Nie można otworzyÄ? pliku nagÅ?ówka `%s' do odczytu w f_print_header()\n"
-#: libgeda/src/f_print.c:177
+#: libgeda/src/f_print.c:178
#, c-format
msgid "Error during reading of the prolog file `%s' in f_print_header()\n"
msgstr "BÅ?Ä?d odczytu pliku nagÅ?ówka `%s' w f_print_header()\n"
-#: libgeda/src/f_print.c:183
+#: libgeda/src/f_print.c:184
msgid ""
"Error during writing of the output postscript file in f_print_header()\n"
msgstr ""
"BÅ?Ä?d w trakcie zapisu pliku wyjÅ?ciowego postscript w f_print_header()\n"
-#: libgeda/src/f_print.c:196
+#: libgeda/src/f_print.c:197
msgid "Giving up on printing\n"
msgstr "Drukowanie nie powiodÅ?o siÄ?\n"
-#: libgeda/src/f_print.c:366
+#: libgeda/src/f_print.c:368
#, c-format
msgid "Could not open [%s] for printing\n"
msgstr "Nie można otworzyÄ? [%s] do wydruku\n"
-#: libgeda/src/f_print.c:399
+#: libgeda/src/f_print.c:402
#, c-format
msgid "Could not execute command [%s] for printing\n"
msgstr "Nie można wykonaÄ? komendy [%s] do wydruku\n"
-#: libgeda/src/f_print.c:674
+#: libgeda/src/f_print.c:676
msgid "Too many UTF-8 characters, cannot print\n"
msgstr "BÅ?Ä?d drukowania: zbyt wiele znaków w kodowaniu UTF-8\n"
-#: libgeda/src/g_basic.c:101
-#, c-format
-msgid "%s:%i:%i: %s\n"
-msgstr "%s:%i:%i: %s\n"
-
-#: libgeda/src/g_basic.c:108
-#, c-format
-msgid "Unknown file: %s\n"
-msgstr "Nieznany plik: %s\n"
-
-#: libgeda/src/g_basic.c:114
-#, c-format
-msgid "Evaluation failed: %s\n"
-msgstr "Interpretacja nie powiodÅ?a siÄ?: %s\n"
-
-#: libgeda/src/g_basic.c:115
-msgid "Enable debugging for more detailed information\n"
-msgstr "WÅ?Ä?cz tryb debugowania aby uzyskaÄ? wiÄ?cej informacji\n"
-
-#: libgeda/src/g_basic.c:258
-#, c-format
-msgid "Could not find [%s] for interpretation\n"
-msgstr "Nie odnaleziono [%s] do interpretacji\n"
+#: libgeda/src/g_basic.c:257
+msgid ""
+"\n"
+"Backtrace:\n"
+msgstr ""
-#: libgeda/src/g_rc.c:134
-#, c-format
-msgid "RC file [%s] already read in.\n"
+#: libgeda/src/g_rc.c:225
+#, fuzzy
+msgid "Config file already loaded"
msgstr "plik RC [%s] zostaÅ? już wczytany.\n"
-#: libgeda/src/g_rc.c:179
-#, c-format
-msgid "Read system config file [%%s]\n"
-msgstr "Wczytano globalny plik konfiguracji [%%s]\n"
-
-#: libgeda/src/g_rc.c:180
-#, c-format
-msgid "Did not find required system config file [%%s]\n"
-msgstr "Nie odnaleziono wymaganego globalnego pliku konfiguracji [%%s]\n"
-
-#: libgeda/src/g_rc.c:214
-#, c-format
-msgid "Read user config file [%%s]\n"
+#: libgeda/src/g_rc.c:260
+#, fuzzy, c-format
+msgid "Parsed config from [%s]\n"
msgstr "Wczytano plik konfiguracji użytkownika [%%s]\n"
-#: libgeda/src/g_rc.c:215
-#, c-format
-msgid "Did not find optional user config file [%%s]\n"
-msgstr "Nie znaleziono opcjonalnego pliku konfiguracji użytkownika [%%s]\n"
-
-#: libgeda/src/g_rc.c:246
-#, c-format
-msgid "Read local config file [%%s]\n"
-msgstr "Wczytano lokalny plik konfiguracji [%%s]\n"
-
-#: libgeda/src/g_rc.c:247
-#, c-format
-msgid "Did not find optional local config file [%%s]\n"
-msgstr "Nie znaleziono opcjonalnego pliku lokalnej konfiguracji [%%s]\n"
+#: libgeda/src/g_rc.c:273
+#, fuzzy, c-format
+msgid "Unable to parse config from [%s]: %s"
+msgstr "BÅ?Ä?d odczytu obrazka z pliku [%s]: %s\n"
-#: libgeda/src/g_rc.c:284
-#, c-format
-msgid "Read specified %s file [%%s]\n"
-msgstr "Wczytano podany plik %s [%%s]\n"
+#: libgeda/src/g_rc.c:290
+msgid "ERROR: An unknown error occurred while parsing configuration files."
+msgstr ""
-#: libgeda/src/g_rc.c:286
+#: libgeda/src/g_rc.c:301 libgeda/src/g_rc.c:302
#, c-format
-msgid "Did not find specified %s file [%%s]\n"
-msgstr "Nie odnaleziono podanego pliku %s [%%s]\n"
+msgid "ERROR: %s\n"
+msgstr ""
-#: libgeda/src/g_rc.c:336
+#: libgeda/src/g_rc.c:308
#, c-format
-msgid "Could not find any %s file!\n"
-msgstr "Nie odnaleziono żadnego pliku %s!\n"
+msgid "ERROR: The %s log may contain more information.\n"
+msgstr ""
-#: libgeda/src/g_rc.c:953
+#: libgeda/src/g_rc.c:1003
msgid ""
"WARNING: using a string for 'always-promote-attributes' is deprecated. Use a "
"list of strings instead\n"
@@ -300,7 +261,7 @@ msgstr "Napotkano Å?uk o zerowym promieniu [ %c %d, %d, %d, %d, %d, %d ]\n"
#: libgeda/src/o_bus_basic.c:182 libgeda/src/o_circle_basic.c:288
#: libgeda/src/o_line_basic.c:264 libgeda/src/o_net_basic.c:174
#: libgeda/src/o_path_basic.c:192 libgeda/src/o_pin_basic.c:187
-#: libgeda/src/o_text_basic.c:419
+#: libgeda/src/o_text_basic.c:420
#, c-format
msgid "Found an invalid color [ %s ]\n"
msgstr "Napotkano niepoprawny kolor [ %s ]\n"
@@ -309,7 +270,7 @@ msgstr "Napotkano niepoprawny kolor [ %s ]\n"
#: libgeda/src/o_bus_basic.c:183 libgeda/src/o_circle_basic.c:289
#: libgeda/src/o_line_basic.c:265 libgeda/src/o_net_basic.c:175
#: libgeda/src/o_path_basic.c:193 libgeda/src/o_pin_basic.c:188
-#: libgeda/src/o_text_basic.c:420
+#: libgeda/src/o_text_basic.c:421
msgid "Setting color to default color\n"
msgstr "UżyjÄ? domyÅ?lnego koloru\n"
@@ -359,7 +320,7 @@ msgstr "KoÅ?a o zerowym promieniu sÄ? niedozwolone\n"
msgid "Found a zero radius circle [ %c %d %d %d %d ]\n"
msgstr "Napotkano koÅ?o o zerowym promieniu [ %c %d %d %d %d ]\n"
-#: libgeda/src/o_complex_basic.c:476
+#: libgeda/src/o_complex_basic.c:481
#, c-format
msgid ""
"Component not found:\n"
@@ -368,13 +329,13 @@ msgstr ""
"Nie odnaleziono komponentu:\n"
" %s"
-#: libgeda/src/o_complex_basic.c:683
+#: libgeda/src/o_complex_basic.c:686
#, c-format
msgid "Found a component with an invalid rotation [ %c %d %d %d %d %d %s ]\n"
msgstr ""
"Napotkano komponent o bÅ?Ä?dnej specyfikacji rotacji [ %c %d %d %d %d %d %s ]\n"
-#: libgeda/src/o_complex_basic.c:695
+#: libgeda/src/o_complex_basic.c:698
#, c-format
msgid ""
"Found a component with an invalid mirror flag [ %c %d %d %d %d %d %s ]\n"
@@ -382,7 +343,7 @@ msgstr ""
"Napotkano komponent z nieprawidÅ?owÄ? wartoÅ?ciÄ? flagi odbicia lustrzanego [ %c "
"%d %d %d %d %d %s ]\n"
-#: libgeda/src/o_complex_basic.c:1008
+#: libgeda/src/o_complex_basic.c:1014
#, c-format
msgid ""
"WARNING: Symbol version parse error on refdes %s:\n"
@@ -391,7 +352,7 @@ msgstr ""
"UWAGA: BÅ?Ä?d parsowania wersji symbolu o identyfikatorze %s:\n"
"\tNiepowodzenie podczas parsowania pliku symbolu symversion=%s\n"
-#: libgeda/src/o_complex_basic.c:1012
+#: libgeda/src/o_complex_basic.c:1018
#, c-format
msgid ""
"WARNING: Symbol version parse error on refdes %s:\n"
@@ -400,7 +361,7 @@ msgstr ""
"UWAGA: BÅ?Ä?d parsowania wersji symbolu o identyfikatorze %s:\n"
"\tNiepowodzenie podczas parsowania pliku symbolu symversion=\n"
-#: libgeda/src/o_complex_basic.c:1028
+#: libgeda/src/o_complex_basic.c:1034
#, c-format
msgid ""
"WARNING: Symbol version parse error on refdes %s:\n"
@@ -409,7 +370,7 @@ msgstr ""
"UWAGA: BÅ?Ä?d parsowania wersji symbolu o identyfikatorze %s:\n"
"\tNiepowodzenie podczas parsowania doÅ?Ä?czonego atrybutu symversion=%s\n"
-#: libgeda/src/o_complex_basic.c:1053
+#: libgeda/src/o_complex_basic.c:1059
#, c-format
msgid ""
"WARNING: Symbol version oddity on refdes %s:\n"
@@ -420,7 +381,7 @@ msgstr ""
"\tAtrybut symversion=%s doÅ?Ä?czony do symbolu, ale brak atrybutu symversion= "
"w pliku symbolu\n"
-#: libgeda/src/o_complex_basic.c:1067
+#: libgeda/src/o_complex_basic.c:1073
#, c-format
msgid ""
"WARNING: Symbol version mismatch on refdes %s (%s):\n"
@@ -429,17 +390,17 @@ msgstr ""
"UWAGA: NiezgodnoÅ?Ä? wersji symbolu o identyfikatorze %s (%s):\n"
"\tWersja symbolu w bibliotece jest nowsza niż wersja tej instancji symbolu\n"
-#: libgeda/src/o_complex_basic.c:1095
+#: libgeda/src/o_complex_basic.c:1101
#, c-format
msgid "\tMAJOR VERSION CHANGE (file %.3f, instantiated %.3f, %s)!\n"
msgstr "\tZNACZÄ?CA ZMIANA WERSJI (plik %.3f, użyto %.3f, %s)!\n"
-#: libgeda/src/o_complex_basic.c:1113
+#: libgeda/src/o_complex_basic.c:1119
#, c-format
msgid "\tMinor version change (file %.3f, instantiated %.3f)\n"
msgstr "\tPomniejsza zmiana wersji (plik %.3f, użyto %.3f)\n"
-#: libgeda/src/o_complex_basic.c:1124
+#: libgeda/src/o_complex_basic.c:1130
#, c-format
msgid ""
"WARNING: Symbol version oddity on refdes %s:\n"
@@ -510,12 +471,12 @@ msgstr "PrzyjmujÄ? 'osadzony' równe 0\n"
msgid "Found an unsupported picture angle [ %d ]\n"
msgstr "Napotkano obrazek z nieprawidÅ?owÄ? wartoÅ?ciÄ? nachylenia [ %d ]\n"
-#: libgeda/src/o_picture.c:116 libgeda/src/o_text_basic.c:391
+#: libgeda/src/o_picture.c:116 libgeda/src/o_text_basic.c:392
msgid "Setting angle to 0\n"
msgstr "UżyjÄ? nachylenia równego 0\n"
#: libgeda/src/o_picture.c:151 libgeda/src/o_picture.c:162
-#: libgeda/src/o_picture.c:913
+#: libgeda/src/o_picture.c:914
#, c-format
msgid "Failed to load image from embedded data [%s]: %s\n"
msgstr "BÅ?Ä?d odczytu obrazka z osadzonych danych [%s]: %s\n"
@@ -525,12 +486,12 @@ msgid "Base64 decoding failed."
msgstr "BÅ?Ä?d dekodowania Base64."
#: libgeda/src/o_picture.c:153 libgeda/src/o_picture.c:164
-#: libgeda/src/o_picture.c:915
+#: libgeda/src/o_picture.c:916
msgid "Falling back to file loading. Picture unembedded.\n"
msgstr "SpróbujÄ? odczytaÄ? obrazek z pliku. Obrazek nie bÄ?dzie osadzony.\n"
-#: libgeda/src/o_picture.c:175 libgeda/src/o_picture.c:901
-#: libgeda/src/o_picture.c:950
+#: libgeda/src/o_picture.c:175 libgeda/src/o_picture.c:902
+#: libgeda/src/o_picture.c:951
#, c-format
msgid "Failed to load image from file [%s]: %s\n"
msgstr "BÅ?Ä?d odczytu obrazka z pliku [%s]: %s\n"
@@ -544,16 +505,16 @@ msgstr "Å?adujÄ? ostrzegawcze zdjÄ?cie.\n"
msgid "Error loading picture from file: %s.\n"
msgstr "BÅ?Ä?d odczytu obrazka z pliku: %s.\n"
-#: libgeda/src/o_picture.c:252
+#: libgeda/src/o_picture.c:253
msgid "ERROR: o_picture_save: unable to encode the picture.\n"
msgstr "BÅ?Ä?D: o_picture_save: nie można zapisaÄ? obrazka.\n"
-#: libgeda/src/o_picture.c:928
+#: libgeda/src/o_picture.c:929
#, c-format
msgid "Picture [%s] has been embedded\n"
msgstr "Obrazek [%s] zostaÅ? osadzony\n"
-#: libgeda/src/o_picture.c:968
+#: libgeda/src/o_picture.c:969
#, c-format
msgid "Picture [%s] has been unembedded\n"
msgstr "Obrazek [%s] nie jest już osadzony\n"
@@ -578,25 +539,25 @@ msgstr ""
msgid "Found a zero length pin: [ %s ]\n"
msgstr "Napotkano pin o zerowej dÅ?ugoÅ?ci: [ %s ]\n"
-#: libgeda/src/o_text_basic.c:377
+#: libgeda/src/o_text_basic.c:378
#, c-format
msgid "Found a zero size text string [ %c %d %d %d %d %d %d %d %d ]\n"
msgstr "Napotkano napis o zerowych wymiarach [ %c %d %d %d %d %d %d %d %d ]\n"
-#: libgeda/src/o_text_basic.c:389
+#: libgeda/src/o_text_basic.c:390
#, c-format
msgid "Found an unsupported text angle [ %c %d %d %d %d %d %d %d %d ]\n"
msgstr ""
"Napotkano napis z nieprawidÅ?owym nachyleniem [ %c %d %d %d %d %d %d %d %d ]\n"
-#: libgeda/src/o_text_basic.c:411
+#: libgeda/src/o_text_basic.c:412
#, c-format
msgid "Found an unsupported text alignment [ %c %d %d %d %d %d %d %d %d ]\n"
msgstr ""
"Napotkano napis z nieprawidÅ?owym wyrównaniem tekstu [ %c %d %d %d %d %d %d "
"%d %d ]\n"
-#: libgeda/src/o_text_basic.c:413
+#: libgeda/src/o_text_basic.c:414
msgid "Setting alignment to LOWER_LEFT\n"
msgstr "UżyjÄ? wyrównania do dolnego lewego rogu\n"
@@ -698,7 +659,7 @@ msgstr "Indeks koloru musi byÄ? liczbÄ? caÅ?kowitÄ?"
msgid "Value in color map entry must be #f or a string"
msgstr "Wpis w mapie kolorów musi byÄ? wartoÅ?ciÄ? #f lub napisem"
-#: libgeda/src/s_hierarchy.c:90
+#: libgeda/src/s_hierarchy.c:94
#, c-format
msgid ""
"hierarchy loop detected while visiting page:\n"
@@ -707,11 +668,11 @@ msgstr ""
"wykryto cykl w hierarchii podczas odczytu strony:\n"
" \"%s\"\n"
-#: libgeda/src/s_hierarchy.c:185
+#: libgeda/src/s_hierarchy.c:187
msgid "There are no schematics above the current one!\n"
msgstr "JesteÅ? już na szczycie hierarchii schematów!\n"
-#: libgeda/src/s_hierarchy.c:266
+#: libgeda/src/s_hierarchy.c:267
#, c-format
msgid "ERROR in s_hierarchy_traverse: schematic not found: %s\n"
msgstr "BÅ?Ä?D w s_hierarchy_traverse: nie odnaleziono schematu: %s\n"
@@ -726,12 +687,12 @@ msgstr "s_page_delete: nie można uzyskaÄ? rzeczywistej nazwy pliku %s."
msgid "s_page_delete: Unable to delete backup file %s."
msgstr "s_page_delete: Nie można skasowaÄ? kopii zapasowej %s."
-#: libgeda/src/s_page.c:504
+#: libgeda/src/s_page.c:499
#, c-format
msgid "Saved [%s]\n"
msgstr "Zapisano [%s]\n"
-#: libgeda/src/s_page.c:510
+#: libgeda/src/s_page.c:505
#, c-format
msgid "Could NOT save [%s]\n"
msgstr "Nie można zapisaÄ? [%s]\n"
@@ -746,6 +707,45 @@ msgstr "Odnaleziono [%s]\n"
msgid "Could not find [%s] in any SourceLibrary\n"
msgstr "Nie odnaleziono [%s] in w żadnej bibliotece\n"
+#~ msgid "%s:%i:%i: %s\n"
+#~ msgstr "%s:%i:%i: %s\n"
+
+#~ msgid "Unknown file: %s\n"
+#~ msgstr "Nieznany plik: %s\n"
+
+#~ msgid "Evaluation failed: %s\n"
+#~ msgstr "Interpretacja nie powiodÅ?a siÄ?: %s\n"
+
+#~ msgid "Enable debugging for more detailed information\n"
+#~ msgstr "WÅ?Ä?cz tryb debugowania aby uzyskaÄ? wiÄ?cej informacji\n"
+
+#~ msgid "Could not find [%s] for interpretation\n"
+#~ msgstr "Nie odnaleziono [%s] do interpretacji\n"
+
+#~ msgid "Read system config file [%%s]\n"
+#~ msgstr "Wczytano globalny plik konfiguracji [%%s]\n"
+
+#~ msgid "Did not find required system config file [%%s]\n"
+#~ msgstr "Nie odnaleziono wymaganego globalnego pliku konfiguracji [%%s]\n"
+
+#~ msgid "Did not find optional user config file [%%s]\n"
+#~ msgstr "Nie znaleziono opcjonalnego pliku konfiguracji użytkownika [%%s]\n"
+
+#~ msgid "Read local config file [%%s]\n"
+#~ msgstr "Wczytano lokalny plik konfiguracji [%%s]\n"
+
+#~ msgid "Did not find optional local config file [%%s]\n"
+#~ msgstr "Nie znaleziono opcjonalnego pliku lokalnej konfiguracji [%%s]\n"
+
+#~ msgid "Read specified %s file [%%s]\n"
+#~ msgstr "Wczytano podany plik %s [%%s]\n"
+
+#~ msgid "Did not find specified %s file [%%s]\n"
+#~ msgstr "Nie odnaleziono podanego pliku %s [%%s]\n"
+
+#~ msgid "Could not find any %s file!\n"
+#~ msgstr "Nie odnaleziono żadnego pliku %s!\n"
+
#~ msgid "o_save: Could not open [%s]\n"
#~ msgstr "o_save: nie można otworzyÄ? [%s]\n"
diff --git a/libgeda/po/ru.po b/libgeda/po/ru.po
index 4da7e8b..253247d 100644
--- a/libgeda/po/ru.po
+++ b/libgeda/po/ru.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2010-11-07 10:51+0000\n"
+"POT-Creation-Date: 2011-01-15 23:36-0500\n"
"PO-Revision-Date: 2010-02-06 22:10+0000\n"
"Last-Translator: Sergey Alyoshin <alyoshin.s@xxxxxxxxx>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -42,12 +42,12 @@ msgstr "gEDA Ñ?лекÑ?Ñ?иÑ?еÑ?каÑ? Ñ?Ñ?ема"
msgid "gEDA Schematic Symbol"
msgstr "gEDA Ñ?лекÑ?Ñ?иÑ?еÑ?кий Ñ?имвол"
-#: libgeda/src/a_basic.c:181
+#: libgeda/src/a_basic.c:182
#, c-format
msgid "o_save_objects: object %p has unknown type '%c'\n"
msgstr "o_save_objects: обÑ?екÑ? %p неизвеÑ?Ñ?ного Ñ?ипа '%c'\n"
-#: libgeda/src/a_basic.c:429
+#: libgeda/src/a_basic.c:417
#, c-format
msgid ""
"Read unexpected embedded symbol start marker in [%s] :\n"
@@ -58,7 +58,7 @@ msgstr ""
">>\n"
"%s<<\n"
-#: libgeda/src/a_basic.c:458
+#: libgeda/src/a_basic.c:446
#, c-format
msgid ""
"Read unexpected embedded symbol end marker in [%s] :\n"
@@ -69,7 +69,7 @@ msgstr ""
">>\n"
"%s<<\n"
-#: libgeda/src/a_basic.c:487
+#: libgeda/src/a_basic.c:475
#, c-format
msgid ""
"Read an old format sym/sch file!\n"
@@ -80,7 +80,7 @@ msgstr ""
"Ð?Ñ?полниÑ?е g[sym|sch]update длÑ?:\n"
"[%s]\n"
-#: libgeda/src/a_basic.c:493
+#: libgeda/src/a_basic.c:481
#, c-format
msgid ""
"Read garbage in [%s] :\n"
@@ -96,12 +96,12 @@ msgstr ""
msgid "Failed to stat [%s]: %s"
msgstr "Ð?Ñ?ибка Ñ?Ñ?ениÑ? Ñ?Ñ?аÑ?Ñ?Ñ?а [%s]: %s"
-#: libgeda/src/f_basic.c:219
+#: libgeda/src/f_basic.c:221
#, c-format
msgid "Cannot find file %s: %s"
msgstr "Ð?евозможно найÑ?и Ñ?айл %s: %s"
-#: libgeda/src/f_basic.c:257
+#: libgeda/src/f_basic.c:264
#, c-format
msgid ""
"\n"
@@ -114,11 +114,11 @@ msgstr ""
" %s.\n"
"\n"
-#: libgeda/src/f_basic.c:259
+#: libgeda/src/f_basic.c:266
msgid "I could not guess if it is newer, so you have to do it manually.\n"
msgstr "Ð?евозможно пÑ?едположиÑ?Ñ? новее ли он, вÑ?беÑ?иÑ?е Ñ?амоÑ?Ñ?оÑ?Ñ?елÑ?но.\n"
-#: libgeda/src/f_basic.c:261
+#: libgeda/src/f_basic.c:268
msgid ""
"The backup copy is newer than the schematic, so it seems you should load it "
"instead of the original file.\n"
@@ -126,7 +126,7 @@ msgstr ""
"РезеÑ?внаÑ? копиÑ? новее Ñ?Ñ?емÑ?, поÑ?Ñ?омÑ?, видимо, Ñ?ледÑ?еÑ? загÑ?Ñ?зиÑ?Ñ? еÑ? вмеÑ?Ñ?о "
"оÑ?игиналÑ?ного Ñ?айла.\n"
-#: libgeda/src/f_basic.c:263
+#: libgeda/src/f_basic.c:270
msgid ""
"Gschem usually makes backup copies automatically, and this situation happens "
"when it crashed or it was forced to exit abruptly.\n"
@@ -134,7 +134,7 @@ msgstr ""
"Ð?бÑ?Ñ?но Gschem авÑ?омаÑ?иÑ?еÑ?ки Ñ?оздаÑ?Ñ? Ñ?езеÑ?внÑ?е копии и Ñ?Ñ?а Ñ?иÑ?Ñ?аÑ?иÑ? Ñ?лÑ?Ñ?аеÑ?Ñ?Ñ? "
"пÑ?и кÑ?Ñ?Ñ?ении Gschem или внезапном завеÑ?Ñ?ении.\n"
-#: libgeda/src/f_basic.c:266
+#: libgeda/src/f_basic.c:273
msgid ""
"\n"
"Run gschem and correct the situation.\n"
@@ -144,146 +144,107 @@ msgstr ""
"Ð?апÑ?Ñ?Ñ?иÑ?е gschem и иÑ?пÑ?авÑ?Ñ?е пÑ?облемÑ?.\n"
"\n"
-#: libgeda/src/f_basic.c:355
+#: libgeda/src/f_basic.c:362
#, c-format
msgid "Can't get the real filename of %s."
msgstr "Ð?евозможно полÑ?Ñ?иÑ?Ñ? Ñ?еалÑ?ное имÑ? Ñ?айла длÑ? %s."
-#: libgeda/src/f_basic.c:375
+#: libgeda/src/f_basic.c:382
#, c-format
msgid "Could NOT set previous backup file [%s] read-write\n"
msgstr ""
"Ð?евозможно Ñ?Ñ?Ñ?ановиÑ?Ñ? Ñ?ежим Ñ?Ñ?ениÑ?-запиÑ?и длÑ? пÑ?едÑ?дÑ?Ñ?ей Ñ?езеÑ?вной копии "
"Ñ?айла [%s]\n"
-#: libgeda/src/f_basic.c:381
+#: libgeda/src/f_basic.c:388
#, c-format
msgid "Can't save backup file: %s."
msgstr "Ð?евозможно Ñ?оÑ?Ñ?аниÑ?Ñ? Ñ?езеÑ?внÑ?Ñ? копиÑ? Ñ?айла: %s."
-#: libgeda/src/f_basic.c:391
+#: libgeda/src/f_basic.c:398
#, c-format
msgid "Could NOT set backup file [%s] readonly\n"
msgstr ""
"Ð?евозможно Ñ?Ñ?Ñ?ановиÑ?Ñ? Ñ?ежим Ñ?олÑ?ко длÑ? Ñ?Ñ?ениÑ? Ñ?езеÑ?вной копии Ñ?айла [%s]\n"
-#: libgeda/src/f_basic.c:680
+#: libgeda/src/f_basic.c:687
#, c-format
msgid "%s: %s"
msgstr "%s: %s"
-#: libgeda/src/f_print.c:118
+#: libgeda/src/f_print.c:119
msgid "Unable to get time of day in f_print_header()\n"
msgstr "Ð?евозможно полÑ?Ñ?иÑ?Ñ? вÑ?емÑ? в f_print_header()\n"
-#: libgeda/src/f_print.c:160
+#: libgeda/src/f_print.c:161
#, c-format
msgid "Unable to open the prolog file `%s' for reading in f_print_header()\n"
msgstr "Ð?евозможно оÑ?кÑ?Ñ?Ñ?Ñ? длÑ? Ñ?Ñ?ениÑ? Ñ?айл пÑ?олога `%s' в f_print_header()\n"
-#: libgeda/src/f_print.c:177
+#: libgeda/src/f_print.c:178
#, c-format
msgid "Error during reading of the prolog file `%s' in f_print_header()\n"
msgstr "Ð?Ñ?ибка пÑ?и Ñ?Ñ?ении Ñ?айла пÑ?олога `%s' в f_print_header()\n"
-#: libgeda/src/f_print.c:183
+#: libgeda/src/f_print.c:184
msgid ""
"Error during writing of the output postscript file in f_print_header()\n"
msgstr "Ð?Ñ?ибка запиÑ?и postscript-Ñ?айла в f_print_header()\n"
-#: libgeda/src/f_print.c:196
+#: libgeda/src/f_print.c:197
msgid "Giving up on printing\n"
msgstr "Ð?Ñ?екÑ?аÑ?ение попÑ?Ñ?ки пеÑ?аÑ?и\n"
-#: libgeda/src/f_print.c:366
+#: libgeda/src/f_print.c:368
#, c-format
msgid "Could not open [%s] for printing\n"
msgstr "Ð?евозможно оÑ?кÑ?Ñ?Ñ?Ñ? [%s] длÑ? пеÑ?аÑ?и\n"
-#: libgeda/src/f_print.c:399
+#: libgeda/src/f_print.c:402
#, c-format
msgid "Could not execute command [%s] for printing\n"
msgstr "Ð?евозможно вÑ?полниÑ?Ñ? командÑ? [%s] длÑ? пеÑ?аÑ?и\n"
-#: libgeda/src/f_print.c:674
+#: libgeda/src/f_print.c:676
msgid "Too many UTF-8 characters, cannot print\n"
msgstr "СлиÑ?ком много Ñ?имволов UTF-8, невозможно пеÑ?аÑ?аÑ?Ñ?\n"
-#: libgeda/src/g_basic.c:101
-#, c-format
-msgid "%s:%i:%i: %s\n"
-msgstr "%s:%i:%i: %s\n"
-
-#: libgeda/src/g_basic.c:108
-#, c-format
-msgid "Unknown file: %s\n"
-msgstr "Ð?еизвеÑ?Ñ?нÑ?й Ñ?айл: %s\n"
-
-#: libgeda/src/g_basic.c:114
-#, c-format
-msgid "Evaluation failed: %s\n"
-msgstr "Ð?Ñ?енка не вÑ?полнена: %s\n"
-
-#: libgeda/src/g_basic.c:115
-msgid "Enable debugging for more detailed information\n"
-msgstr "Ð?клÑ?Ñ?иÑ?е оÑ?ладкÑ? длÑ? более деÑ?алÑ?ной инÑ?оÑ?маÑ?ии\n"
-
-#: libgeda/src/g_basic.c:258
-#, c-format
-msgid "Could not find [%s] for interpretation\n"
-msgstr "Ð?евозможно найÑ?и [%s] длÑ? инÑ?еÑ?пÑ?еÑ?аÑ?ии\n"
+#: libgeda/src/g_basic.c:257
+msgid ""
+"\n"
+"Backtrace:\n"
+msgstr ""
-#: libgeda/src/g_rc.c:134
-#, c-format
-msgid "RC file [%s] already read in.\n"
+#: libgeda/src/g_rc.c:225
+#, fuzzy
+msgid "Config file already loaded"
msgstr "RC-Ñ?айл [%s] Ñ?же пÑ?оÑ?иÑ?ан.\n"
-#: libgeda/src/g_rc.c:179
-#, c-format
-msgid "Read system config file [%%s]\n"
-msgstr "ЧÑ?ение Ñ?айла Ñ?иÑ?Ñ?емной конÑ?игÑ?Ñ?аÑ?ии [%%s]\n"
-
-#: libgeda/src/g_rc.c:180
-#, c-format
-msgid "Did not find required system config file [%%s]\n"
-msgstr "Ð?е найден обÑ?заÑ?елÑ?нÑ?й Ñ?айл Ñ?иÑ?Ñ?емной конÑ?игÑ?Ñ?аÑ?ии [%%s]\n"
-
-#: libgeda/src/g_rc.c:214
-#, c-format
-msgid "Read user config file [%%s]\n"
+#: libgeda/src/g_rc.c:260
+#, fuzzy, c-format
+msgid "Parsed config from [%s]\n"
msgstr "ЧÑ?ение Ñ?айла полÑ?зоваÑ?елÑ?Ñ?кой конÑ?игÑ?Ñ?аÑ?ии [%%s]\n"
-#: libgeda/src/g_rc.c:215
-#, c-format
-msgid "Did not find optional user config file [%%s]\n"
-msgstr "Ð?е найден необÑ?заÑ?елÑ?нÑ?й Ñ?айл полÑ?зоваÑ?елÑ?Ñ?кой конÑ?игÑ?Ñ?аÑ?ии [%%s]\n"
-
-#: libgeda/src/g_rc.c:246
-#, c-format
-msgid "Read local config file [%%s]\n"
-msgstr "ЧÑ?ение локалÑ?ного Ñ?айла конÑ?игÑ?Ñ?аÑ?ии [%%s]\n"
-
-#: libgeda/src/g_rc.c:247
-#, c-format
-msgid "Did not find optional local config file [%%s]\n"
-msgstr "Ð?е найден необÑ?заÑ?елÑ?нÑ?й Ñ?айл локалÑ?ной конÑ?игÑ?Ñ?аÑ?ии [%%s]\n"
+#: libgeda/src/g_rc.c:273
+#, fuzzy, c-format
+msgid "Unable to parse config from [%s]: %s"
+msgstr "Ð?евозможно загÑ?Ñ?зиÑ?Ñ? изобÑ?ажение из Ñ?айла [%s]: %s\n"
-#: libgeda/src/g_rc.c:284
-#, c-format
-msgid "Read specified %s file [%%s]\n"
-msgstr "ЧÑ?ение Ñ?казанного Ñ?айла %s [%%s]\n"
+#: libgeda/src/g_rc.c:290
+msgid "ERROR: An unknown error occurred while parsing configuration files."
+msgstr ""
-#: libgeda/src/g_rc.c:286
+#: libgeda/src/g_rc.c:301 libgeda/src/g_rc.c:302
#, c-format
-msgid "Did not find specified %s file [%%s]\n"
-msgstr "Ð?е найден Ñ?казаннÑ?й Ñ?айл %s [%%s]\n"
+msgid "ERROR: %s\n"
+msgstr ""
-#: libgeda/src/g_rc.c:336
+#: libgeda/src/g_rc.c:308
#, c-format
-msgid "Could not find any %s file!\n"
-msgstr "Ð?евозможно найÑ?и какой-либо Ñ?айл %s!\n"
+msgid "ERROR: The %s log may contain more information.\n"
+msgstr ""
-#: libgeda/src/g_rc.c:953
+#: libgeda/src/g_rc.c:1003
msgid ""
"WARNING: using a string for 'always-promote-attributes' is deprecated. Use a "
"list of strings instead\n"
@@ -300,7 +261,7 @@ msgstr "Ð?айдена дÑ?га нÑ?левого Ñ?адиÑ?Ñ?а [ %c %d, %d, %d,
#: libgeda/src/o_bus_basic.c:182 libgeda/src/o_circle_basic.c:288
#: libgeda/src/o_line_basic.c:264 libgeda/src/o_net_basic.c:174
#: libgeda/src/o_path_basic.c:192 libgeda/src/o_pin_basic.c:187
-#: libgeda/src/o_text_basic.c:419
+#: libgeda/src/o_text_basic.c:420
#, c-format
msgid "Found an invalid color [ %s ]\n"
msgstr "Ð?айден невеÑ?нÑ?й Ñ?веÑ? [ %s ]\n"
@@ -309,7 +270,7 @@ msgstr "Ð?айден невеÑ?нÑ?й Ñ?веÑ? [ %s ]\n"
#: libgeda/src/o_bus_basic.c:183 libgeda/src/o_circle_basic.c:289
#: libgeda/src/o_line_basic.c:265 libgeda/src/o_net_basic.c:175
#: libgeda/src/o_path_basic.c:193 libgeda/src/o_pin_basic.c:188
-#: libgeda/src/o_text_basic.c:420
+#: libgeda/src/o_text_basic.c:421
msgid "Setting color to default color\n"
msgstr "УÑ?Ñ?ановка Ñ?веÑ?а по Ñ?молÑ?аниÑ?\n"
@@ -358,7 +319,7 @@ msgstr "Ð?е допÑ?Ñ?Ñ?имÑ? окÑ?Ñ?жноÑ?Ñ?и нÑ?левого Ñ?адиÑ?
msgid "Found a zero radius circle [ %c %d %d %d %d ]\n"
msgstr "Ð?айдена окÑ?Ñ?жноÑ?Ñ?Ñ? нÑ?левого Ñ?адиÑ?Ñ?а [ %c %d %d %d %d ]\n"
-#: libgeda/src/o_complex_basic.c:476
+#: libgeda/src/o_complex_basic.c:481
#, c-format
msgid ""
"Component not found:\n"
@@ -367,19 +328,19 @@ msgstr ""
"Ð?омпоненÑ? не найден:\n"
" %s"
-#: libgeda/src/o_complex_basic.c:683
+#: libgeda/src/o_complex_basic.c:686
#, c-format
msgid "Found a component with an invalid rotation [ %c %d %d %d %d %d %s ]\n"
msgstr "Ð?айден компоненÑ? Ñ? невеÑ?нÑ?м повоÑ?оÑ?ом [ %c %d %d %d %d %d %s ]\n"
-#: libgeda/src/o_complex_basic.c:695
+#: libgeda/src/o_complex_basic.c:698
#, c-format
msgid ""
"Found a component with an invalid mirror flag [ %c %d %d %d %d %d %s ]\n"
msgstr ""
"Ð?айден компоненÑ? Ñ? невеÑ?нÑ?м Ñ?лагом зеÑ?калиÑ?ованиÑ? [ %c %d %d %d %d %d %s ]\n"
-#: libgeda/src/o_complex_basic.c:1008
+#: libgeda/src/o_complex_basic.c:1014
#, c-format
msgid ""
"WARNING: Symbol version parse error on refdes %s:\n"
@@ -388,7 +349,7 @@ msgstr ""
"Ð?Ð?Ð?Ð?Ð?Ð?Ð?Ð?: оÑ?ибка Ñ?азбоÑ?а веÑ?Ñ?ии Ñ?имвола длÑ? refdes %s:\n"
"\tÐ?евозможно Ñ?азобÑ?аÑ?Ñ? Ñ?айл Ñ?имвола symversion=%s\n"
-#: libgeda/src/o_complex_basic.c:1012
+#: libgeda/src/o_complex_basic.c:1018
#, c-format
msgid ""
"WARNING: Symbol version parse error on refdes %s:\n"
@@ -397,7 +358,7 @@ msgstr ""
"Ð?Ð?Ð?Ð?Ð?Ð?Ð?Ð?: оÑ?ибка Ñ?азбоÑ?а веÑ?Ñ?ии Ñ?имвола длÑ? refdes %s:\n"
"\tÐ?евозможно Ñ?азобÑ?аÑ?Ñ? Ñ?айл Ñ?имвола symversion=\n"
-#: libgeda/src/o_complex_basic.c:1028
+#: libgeda/src/o_complex_basic.c:1034
#, c-format
msgid ""
"WARNING: Symbol version parse error on refdes %s:\n"
@@ -406,7 +367,7 @@ msgstr ""
"Ð?Ð?Ð?Ð?Ð?Ð?Ð?Ð?: оÑ?ибка Ñ?азбоÑ?а веÑ?Ñ?ии Ñ?имвола длÑ? refdes %s:\n"
"\tÐ?евозможно Ñ?азобÑ?аÑ?Ñ? пÑ?иÑ?оединÑ?ннÑ?й symversion=%s\n"
-#: libgeda/src/o_complex_basic.c:1053
+#: libgeda/src/o_complex_basic.c:1059
#, c-format
msgid ""
"WARNING: Symbol version oddity on refdes %s:\n"
@@ -417,7 +378,7 @@ msgstr ""
"\tsymversion=%s пÑ?иÑ?оединÑ?н к иÑ?полÑ?зÑ?емомÑ? Ñ?имволÑ?, но symversion= "
"оÑ?Ñ?Ñ?Ñ?Ñ?Ñ?вÑ?еÑ? в Ñ?айле Ñ?имвола\n"
-#: libgeda/src/o_complex_basic.c:1067
+#: libgeda/src/o_complex_basic.c:1073
#, c-format
msgid ""
"WARNING: Symbol version mismatch on refdes %s (%s):\n"
@@ -426,17 +387,17 @@ msgstr ""
"Ð?Ð?Ð?Ð?Ð?Ð?Ð?Ð?: веÑ?Ñ?иÑ? Ñ?имвола не подÑ?одиÑ? длÑ? поз. обознаÑ?ениÑ? %s (%s):\n"
"\tСимвол в библиоÑ?еке новее Ñ?ем иÑ?полÑ?зÑ?емÑ?й Ñ?имвол\n"
-#: libgeda/src/o_complex_basic.c:1095
+#: libgeda/src/o_complex_basic.c:1101
#, c-format
msgid "\tMAJOR VERSION CHANGE (file %.3f, instantiated %.3f, %s)!\n"
msgstr "\tÐ?Ð?Ð?Ð?Ð?Ð?Ð? СТÐ?РШÐ?Ð? Ð?Ð?Ð?Ð?Ð Ð?Ð?РСÐ?Ð? (Ñ?айл %.3f, иÑ?полÑ?зÑ?емÑ?й %.3f, %s)!\n"
-#: libgeda/src/o_complex_basic.c:1113
+#: libgeda/src/o_complex_basic.c:1119
#, c-format
msgid "\tMinor version change (file %.3f, instantiated %.3f)\n"
msgstr "\tÐ?зменÑ?н младÑ?ий номеÑ? веÑ?Ñ?ии (Ñ?айл %.3f, иÑ?полÑ?зÑ?емÑ?й %.3f)\n"
-#: libgeda/src/o_complex_basic.c:1124
+#: libgeda/src/o_complex_basic.c:1130
#, c-format
msgid ""
"WARNING: Symbol version oddity on refdes %s:\n"
@@ -506,12 +467,12 @@ msgstr "УÑ?Ñ?ановка паÑ?амеÑ?Ñ?а 'внедÑ?Ñ?н' в 0\n"
msgid "Found an unsupported picture angle [ %d ]\n"
msgstr "Ð?айдено изобÑ?ажение Ñ? неподдеÑ?живаемÑ?м Ñ?глом [ %d ]\n"
-#: libgeda/src/o_picture.c:116 libgeda/src/o_text_basic.c:391
+#: libgeda/src/o_picture.c:116 libgeda/src/o_text_basic.c:392
msgid "Setting angle to 0\n"
msgstr "УÑ?Ñ?ановка Ñ?гла в 0\n"
#: libgeda/src/o_picture.c:151 libgeda/src/o_picture.c:162
-#: libgeda/src/o_picture.c:913
+#: libgeda/src/o_picture.c:914
#, c-format
msgid "Failed to load image from embedded data [%s]: %s\n"
msgstr "Ð?евозможно загÑ?Ñ?зиÑ?Ñ? изобÑ?ажение из вÑ?Ñ?Ñ?оеннÑ?Ñ? даннÑ?Ñ? [%s]: %s\n"
@@ -521,12 +482,12 @@ msgid "Base64 decoding failed."
msgstr "Ð?евозможно декодиÑ?оваÑ?Ñ? base64."
#: libgeda/src/o_picture.c:153 libgeda/src/o_picture.c:164
-#: libgeda/src/o_picture.c:915
+#: libgeda/src/o_picture.c:916
msgid "Falling back to file loading. Picture unembedded.\n"
msgstr "Ð?озвÑ?аÑ?ение к загÑ?Ñ?зке Ñ?айла. Ð?зобÑ?ажение иÑ?клÑ?Ñ?ено.\n"
-#: libgeda/src/o_picture.c:175 libgeda/src/o_picture.c:901
-#: libgeda/src/o_picture.c:950
+#: libgeda/src/o_picture.c:175 libgeda/src/o_picture.c:902
+#: libgeda/src/o_picture.c:951
#, c-format
msgid "Failed to load image from file [%s]: %s\n"
msgstr "Ð?евозможно загÑ?Ñ?зиÑ?Ñ? изобÑ?ажение из Ñ?айла [%s]: %s\n"
@@ -540,16 +501,16 @@ msgstr "Ð?агÑ?Ñ?зка изобÑ?ажениÑ? Ñ?имвола пÑ?едÑ?пÑ?е
msgid "Error loading picture from file: %s.\n"
msgstr "Ð?Ñ?ибка пÑ?и загÑ?Ñ?зке изобÑ?ажение из Ñ?айла: %s.\n"
-#: libgeda/src/o_picture.c:252
+#: libgeda/src/o_picture.c:253
msgid "ERROR: o_picture_save: unable to encode the picture.\n"
msgstr "Ð?ШÐ?Ð?Ð?Ð?: o_picture_save: невозможно кодиÑ?оваÑ?Ñ? изобÑ?ажение.\n"
-#: libgeda/src/o_picture.c:928
+#: libgeda/src/o_picture.c:929
#, c-format
msgid "Picture [%s] has been embedded\n"
msgstr "Ð?зобÑ?ажение [%s] вÑ?Ñ?Ñ?оено\n"
-#: libgeda/src/o_picture.c:968
+#: libgeda/src/o_picture.c:969
#, c-format
msgid "Picture [%s] has been unembedded\n"
msgstr "Ð?зобÑ?ажение [%s] иÑ?клÑ?Ñ?ено\n"
@@ -572,25 +533,25 @@ msgstr "Ð?айдено невеÑ?ное Ñ?оединÑ?емое оконÑ?ани
msgid "Found a zero length pin: [ %s ]\n"
msgstr "Ð?айден вÑ?вод нÑ?левой длинÑ?: [ %s ]\n"
-#: libgeda/src/o_text_basic.c:377
+#: libgeda/src/o_text_basic.c:378
#, c-format
msgid "Found a zero size text string [ %c %d %d %d %d %d %d %d %d ]\n"
msgstr ""
"Ð?айдена Ñ?екÑ?Ñ?оваÑ? Ñ?Ñ?Ñ?ока нÑ?левого Ñ?азмеÑ?а [ %c %d %d %d %d %d %d %d %d ]\n"
-#: libgeda/src/o_text_basic.c:389
+#: libgeda/src/o_text_basic.c:390
#, c-format
msgid "Found an unsupported text angle [ %c %d %d %d %d %d %d %d %d ]\n"
msgstr ""
"Ð?айден неподдеÑ?живаемÑ?й Ñ?гол наклона Ñ?екÑ?Ñ?а [ %c %d %d %d %d %d %d %d %d ]\n"
-#: libgeda/src/o_text_basic.c:411
+#: libgeda/src/o_text_basic.c:412
#, c-format
msgid "Found an unsupported text alignment [ %c %d %d %d %d %d %d %d %d ]\n"
msgstr ""
"Ð?айдено неподдеÑ?живаемое вÑ?Ñ?авнивание Ñ?екÑ?Ñ?а [ %c %d %d %d %d %d %d %d %d ]\n"
-#: libgeda/src/o_text_basic.c:413
+#: libgeda/src/o_text_basic.c:414
msgid "Setting alignment to LOWER_LEFT\n"
msgstr "УÑ?Ñ?ановка вÑ?Ñ?авниваниÑ? в нижнее левое (LOWER_LEFT)\n"
@@ -696,7 +657,7 @@ msgstr "Ð?ндекÑ? Ñ?леменÑ?а в каÑ?Ñ?е Ñ?веÑ?ов должен б
msgid "Value in color map entry must be #f or a string"
msgstr "Ð?наÑ?ение Ñ?леменÑ?а в каÑ?Ñ?е Ñ?веÑ?ов должно бÑ?Ñ?Ñ? #f или Ñ?Ñ?Ñ?ока"
-#: libgeda/src/s_hierarchy.c:90
+#: libgeda/src/s_hierarchy.c:94
#, c-format
msgid ""
"hierarchy loop detected while visiting page:\n"
@@ -705,11 +666,11 @@ msgstr ""
"обнаÑ?Ñ?жено заÑ?икливание иеÑ?аÑ?Ñ?ии пÑ?и пеÑ?еÑ?оде к Ñ?Ñ?Ñ?аниÑ?е:\n"
" \"%s\"\n"
-#: libgeda/src/s_hierarchy.c:185
+#: libgeda/src/s_hierarchy.c:187
msgid "There are no schematics above the current one!\n"
msgstr "Ð?еÑ? Ñ?Ñ?ем над Ñ?екÑ?Ñ?ей!\n"
-#: libgeda/src/s_hierarchy.c:266
+#: libgeda/src/s_hierarchy.c:267
#, c-format
msgid "ERROR in s_hierarchy_traverse: schematic not found: %s\n"
msgstr "Ð?ШÐ?Ð?Ð?Ð? в s_hierarchy_traverse: не найдена Ñ?Ñ?ема: %s\n"
@@ -724,12 +685,12 @@ msgstr "s_page_delete: невозможно полÑ?Ñ?иÑ?Ñ? Ñ?еалÑ?ное и
msgid "s_page_delete: Unable to delete backup file %s."
msgstr "s_page_delete: невозможно Ñ?далиÑ?Ñ? Ñ?айл Ñ?езеÑ?вной копии %s."
-#: libgeda/src/s_page.c:504
+#: libgeda/src/s_page.c:499
#, c-format
msgid "Saved [%s]\n"
msgstr "СоÑ?Ñ?анено [%s]\n"
-#: libgeda/src/s_page.c:510
+#: libgeda/src/s_page.c:505
#, c-format
msgid "Could NOT save [%s]\n"
msgstr "Ð?евозможно Ñ?оÑ?Ñ?аниÑ?Ñ? [%s]\n"
@@ -744,6 +705,45 @@ msgstr "Ð?айден [%s]\n"
msgid "Could not find [%s] in any SourceLibrary\n"
msgstr "Ð?евозможно найÑ?и [%s] в иÑ?Ñ?однÑ?Ñ? библиоÑ?екаÑ?\n"
+#~ msgid "%s:%i:%i: %s\n"
+#~ msgstr "%s:%i:%i: %s\n"
+
+#~ msgid "Unknown file: %s\n"
+#~ msgstr "Ð?еизвеÑ?Ñ?нÑ?й Ñ?айл: %s\n"
+
+#~ msgid "Evaluation failed: %s\n"
+#~ msgstr "Ð?Ñ?енка не вÑ?полнена: %s\n"
+
+#~ msgid "Enable debugging for more detailed information\n"
+#~ msgstr "Ð?клÑ?Ñ?иÑ?е оÑ?ладкÑ? длÑ? более деÑ?алÑ?ной инÑ?оÑ?маÑ?ии\n"
+
+#~ msgid "Could not find [%s] for interpretation\n"
+#~ msgstr "Ð?евозможно найÑ?и [%s] длÑ? инÑ?еÑ?пÑ?еÑ?аÑ?ии\n"
+
+#~ msgid "Read system config file [%%s]\n"
+#~ msgstr "ЧÑ?ение Ñ?айла Ñ?иÑ?Ñ?емной конÑ?игÑ?Ñ?аÑ?ии [%%s]\n"
+
+#~ msgid "Did not find required system config file [%%s]\n"
+#~ msgstr "Ð?е найден обÑ?заÑ?елÑ?нÑ?й Ñ?айл Ñ?иÑ?Ñ?емной конÑ?игÑ?Ñ?аÑ?ии [%%s]\n"
+
+#~ msgid "Did not find optional user config file [%%s]\n"
+#~ msgstr "Ð?е найден необÑ?заÑ?елÑ?нÑ?й Ñ?айл полÑ?зоваÑ?елÑ?Ñ?кой конÑ?игÑ?Ñ?аÑ?ии [%%s]\n"
+
+#~ msgid "Read local config file [%%s]\n"
+#~ msgstr "ЧÑ?ение локалÑ?ного Ñ?айла конÑ?игÑ?Ñ?аÑ?ии [%%s]\n"
+
+#~ msgid "Did not find optional local config file [%%s]\n"
+#~ msgstr "Ð?е найден необÑ?заÑ?елÑ?нÑ?й Ñ?айл локалÑ?ной конÑ?игÑ?Ñ?аÑ?ии [%%s]\n"
+
+#~ msgid "Read specified %s file [%%s]\n"
+#~ msgstr "ЧÑ?ение Ñ?казанного Ñ?айла %s [%%s]\n"
+
+#~ msgid "Did not find specified %s file [%%s]\n"
+#~ msgstr "Ð?е найден Ñ?казаннÑ?й Ñ?айл %s [%%s]\n"
+
+#~ msgid "Could not find any %s file!\n"
+#~ msgstr "Ð?евозможно найÑ?и какой-либо Ñ?айл %s!\n"
+
#~ msgid "o_save: Could not open [%s]\n"
#~ msgstr "o_save: невозможно оÑ?кÑ?Ñ?Ñ?Ñ? [%s]\n"
diff --git a/libgeda/po/tr.po b/libgeda/po/tr.po
index 9948e2e..0d29927 100644
--- a/libgeda/po/tr.po
+++ b/libgeda/po/tr.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2010-11-07 10:51+0000\n"
+"POT-Creation-Date: 2011-01-15 23:36-0500\n"
"PO-Revision-Date: 2010-02-06 22:09+0000\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -42,12 +42,12 @@ msgstr ""
msgid "gEDA Schematic Symbol"
msgstr "gEDA Å?ematik sembol"
-#: libgeda/src/a_basic.c:181
+#: libgeda/src/a_basic.c:182
#, c-format
msgid "o_save_objects: object %p has unknown type '%c'\n"
msgstr "o_save_objects: %p nesnesi bilinmeyen tip '%c'\n"
-#: libgeda/src/a_basic.c:429
+#: libgeda/src/a_basic.c:417
#, c-format
msgid ""
"Read unexpected embedded symbol start marker in [%s] :\n"
@@ -55,7 +55,7 @@ msgid ""
"%s<<\n"
msgstr ""
-#: libgeda/src/a_basic.c:458
+#: libgeda/src/a_basic.c:446
#, c-format
msgid ""
"Read unexpected embedded symbol end marker in [%s] :\n"
@@ -63,7 +63,7 @@ msgid ""
"%s<<\n"
msgstr ""
-#: libgeda/src/a_basic.c:487
+#: libgeda/src/a_basic.c:475
#, c-format
msgid ""
"Read an old format sym/sch file!\n"
@@ -71,7 +71,7 @@ msgid ""
"[%s]\n"
msgstr ""
-#: libgeda/src/a_basic.c:493
+#: libgeda/src/a_basic.c:481
#, c-format
msgid ""
"Read garbage in [%s] :\n"
@@ -84,12 +84,12 @@ msgstr ""
msgid "Failed to stat [%s]: %s"
msgstr ""
-#: libgeda/src/f_basic.c:219
+#: libgeda/src/f_basic.c:221
#, c-format
msgid "Cannot find file %s: %s"
msgstr ""
-#: libgeda/src/f_basic.c:257
+#: libgeda/src/f_basic.c:264
#, c-format
msgid ""
"\n"
@@ -102,11 +102,11 @@ msgstr ""
" %s.\n"
"\n"
-#: libgeda/src/f_basic.c:259
+#: libgeda/src/f_basic.c:266
msgid "I could not guess if it is newer, so you have to do it manually.\n"
msgstr "Yeniyse tahmin edemiyorum, bunu elle yapın.\n"
-#: libgeda/src/f_basic.c:261
+#: libgeda/src/f_basic.c:268
msgid ""
"The backup copy is newer than the schematic, so it seems you should load it "
"instead of the original file.\n"
@@ -114,13 +114,13 @@ msgstr ""
"Yedek kopyası Å?ematikten yeni bu nedenle asıl dosya yerine onu yükleyeceÄ?iz "
"gözküyor.\n"
-#: libgeda/src/f_basic.c:263
+#: libgeda/src/f_basic.c:270
msgid ""
"Gschem usually makes backup copies automatically, and this situation happens "
"when it crashed or it was forced to exit abruptly.\n"
msgstr ""
-#: libgeda/src/f_basic.c:266
+#: libgeda/src/f_basic.c:273
msgid ""
"\n"
"Run gschem and correct the situation.\n"
@@ -130,143 +130,103 @@ msgstr ""
"gschem'i çalıÅ?tırın ve bu durumu düzeltin\n"
"\n"
-#: libgeda/src/f_basic.c:355
+#: libgeda/src/f_basic.c:362
#, c-format
msgid "Can't get the real filename of %s."
msgstr "%s için asıl dosya adı bulunamadı"
-#: libgeda/src/f_basic.c:375
+#: libgeda/src/f_basic.c:382
#, c-format
msgid "Could NOT set previous backup file [%s] read-write\n"
msgstr ""
-#: libgeda/src/f_basic.c:381
+#: libgeda/src/f_basic.c:388
#, c-format
msgid "Can't save backup file: %s."
msgstr ""
-#: libgeda/src/f_basic.c:391
+#: libgeda/src/f_basic.c:398
#, c-format
msgid "Could NOT set backup file [%s] readonly\n"
msgstr ""
-#: libgeda/src/f_basic.c:680
+#: libgeda/src/f_basic.c:687
#, c-format
msgid "%s: %s"
msgstr ""
-#: libgeda/src/f_print.c:118
+#: libgeda/src/f_print.c:119
msgid "Unable to get time of day in f_print_header()\n"
msgstr ""
-#: libgeda/src/f_print.c:160
+#: libgeda/src/f_print.c:161
#, c-format
msgid "Unable to open the prolog file `%s' for reading in f_print_header()\n"
msgstr ""
-#: libgeda/src/f_print.c:177
+#: libgeda/src/f_print.c:178
#, c-format
msgid "Error during reading of the prolog file `%s' in f_print_header()\n"
msgstr ""
-#: libgeda/src/f_print.c:183
+#: libgeda/src/f_print.c:184
msgid ""
"Error during writing of the output postscript file in f_print_header()\n"
msgstr ""
-#: libgeda/src/f_print.c:196
+#: libgeda/src/f_print.c:197
msgid "Giving up on printing\n"
msgstr ""
-#: libgeda/src/f_print.c:366
+#: libgeda/src/f_print.c:368
#, c-format
msgid "Could not open [%s] for printing\n"
msgstr "[%s] yazdırma iÅ?lemi için açılamıyor\n"
-#: libgeda/src/f_print.c:399
+#: libgeda/src/f_print.c:402
#, c-format
msgid "Could not execute command [%s] for printing\n"
msgstr ""
-#: libgeda/src/f_print.c:674
+#: libgeda/src/f_print.c:676
msgid "Too many UTF-8 characters, cannot print\n"
msgstr "çok fazla UTF-8 karakteri var, yazdırılamaz\n"
-#: libgeda/src/g_basic.c:101
-#, c-format
-msgid "%s:%i:%i: %s\n"
-msgstr "%s:%i:%i: %s\n"
-
-#: libgeda/src/g_basic.c:108
-#, c-format
-msgid "Unknown file: %s\n"
-msgstr ""
-
-#: libgeda/src/g_basic.c:114
-#, c-format
-msgid "Evaluation failed: %s\n"
-msgstr ""
-
-#: libgeda/src/g_basic.c:115
-msgid "Enable debugging for more detailed information\n"
-msgstr ""
-
-#: libgeda/src/g_basic.c:258
-#, c-format
-msgid "Could not find [%s] for interpretation\n"
-msgstr ""
-
-#: libgeda/src/g_rc.c:134
-#, c-format
-msgid "RC file [%s] already read in.\n"
-msgstr ""
-
-#: libgeda/src/g_rc.c:179
-#, c-format
-msgid "Read system config file [%%s]\n"
-msgstr ""
-
-#: libgeda/src/g_rc.c:180
-#, c-format
-msgid "Did not find required system config file [%%s]\n"
-msgstr ""
-
-#: libgeda/src/g_rc.c:214
-#, c-format
-msgid "Read user config file [%%s]\n"
+#: libgeda/src/g_basic.c:257
+msgid ""
+"\n"
+"Backtrace:\n"
msgstr ""
-#: libgeda/src/g_rc.c:215
-#, c-format
-msgid "Did not find optional user config file [%%s]\n"
+#: libgeda/src/g_rc.c:225
+msgid "Config file already loaded"
msgstr ""
-#: libgeda/src/g_rc.c:246
+#: libgeda/src/g_rc.c:260
#, c-format
-msgid "Read local config file [%%s]\n"
+msgid "Parsed config from [%s]\n"
msgstr ""
-#: libgeda/src/g_rc.c:247
+#: libgeda/src/g_rc.c:273
#, c-format
-msgid "Did not find optional local config file [%%s]\n"
+msgid "Unable to parse config from [%s]: %s"
msgstr ""
-#: libgeda/src/g_rc.c:284
-#, c-format
-msgid "Read specified %s file [%%s]\n"
+#: libgeda/src/g_rc.c:290
+msgid "ERROR: An unknown error occurred while parsing configuration files."
msgstr ""
-#: libgeda/src/g_rc.c:286
+#: libgeda/src/g_rc.c:301 libgeda/src/g_rc.c:302
#, c-format
-msgid "Did not find specified %s file [%%s]\n"
+msgid "ERROR: %s\n"
msgstr ""
-#: libgeda/src/g_rc.c:336
+#: libgeda/src/g_rc.c:308
#, c-format
-msgid "Could not find any %s file!\n"
+msgid "ERROR: The %s log may contain more information.\n"
msgstr ""
-#: libgeda/src/g_rc.c:953
+#: libgeda/src/g_rc.c:1003
msgid ""
"WARNING: using a string for 'always-promote-attributes' is deprecated. Use a "
"list of strings instead\n"
@@ -281,7 +241,7 @@ msgstr ""
#: libgeda/src/o_bus_basic.c:182 libgeda/src/o_circle_basic.c:288
#: libgeda/src/o_line_basic.c:264 libgeda/src/o_net_basic.c:174
#: libgeda/src/o_path_basic.c:192 libgeda/src/o_pin_basic.c:187
-#: libgeda/src/o_text_basic.c:419
+#: libgeda/src/o_text_basic.c:420
#, c-format
msgid "Found an invalid color [ %s ]\n"
msgstr ""
@@ -290,7 +250,7 @@ msgstr ""
#: libgeda/src/o_bus_basic.c:183 libgeda/src/o_circle_basic.c:289
#: libgeda/src/o_line_basic.c:265 libgeda/src/o_net_basic.c:175
#: libgeda/src/o_path_basic.c:193 libgeda/src/o_pin_basic.c:188
-#: libgeda/src/o_text_basic.c:420
+#: libgeda/src/o_text_basic.c:421
msgid "Setting color to default color\n"
msgstr ""
@@ -339,7 +299,7 @@ msgstr ""
msgid "Found a zero radius circle [ %c %d %d %d %d ]\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:476
+#: libgeda/src/o_complex_basic.c:481
#, c-format
msgid ""
"Component not found:\n"
@@ -348,39 +308,39 @@ msgstr ""
"bileÅ?en bulanamadı:\n"
" %s"
-#: libgeda/src/o_complex_basic.c:683
+#: libgeda/src/o_complex_basic.c:686
#, c-format
msgid "Found a component with an invalid rotation [ %c %d %d %d %d %d %s ]\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:695
+#: libgeda/src/o_complex_basic.c:698
#, c-format
msgid ""
"Found a component with an invalid mirror flag [ %c %d %d %d %d %d %s ]\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:1008
+#: libgeda/src/o_complex_basic.c:1014
#, c-format
msgid ""
"WARNING: Symbol version parse error on refdes %s:\n"
"\tCould not parse symbol file symversion=%s\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:1012
+#: libgeda/src/o_complex_basic.c:1018
#, c-format
msgid ""
"WARNING: Symbol version parse error on refdes %s:\n"
"\tCould not parse symbol file symversion=\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:1028
+#: libgeda/src/o_complex_basic.c:1034
#, c-format
msgid ""
"WARNING: Symbol version parse error on refdes %s:\n"
"\tCould not parse attached symversion=%s\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:1053
+#: libgeda/src/o_complex_basic.c:1059
#, c-format
msgid ""
"WARNING: Symbol version oddity on refdes %s:\n"
@@ -388,24 +348,24 @@ msgid ""
"symbol file\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:1067
+#: libgeda/src/o_complex_basic.c:1073
#, c-format
msgid ""
"WARNING: Symbol version mismatch on refdes %s (%s):\n"
"\tSymbol in library is newer than instantiated symbol\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:1095
+#: libgeda/src/o_complex_basic.c:1101
#, c-format
msgid "\tMAJOR VERSION CHANGE (file %.3f, instantiated %.3f, %s)!\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:1113
+#: libgeda/src/o_complex_basic.c:1119
#, c-format
msgid "\tMinor version change (file %.3f, instantiated %.3f)\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:1124
+#: libgeda/src/o_complex_basic.c:1130
#, c-format
msgid ""
"WARNING: Symbol version oddity on refdes %s:\n"
@@ -472,12 +432,12 @@ msgstr ""
msgid "Found an unsupported picture angle [ %d ]\n"
msgstr ""
-#: libgeda/src/o_picture.c:116 libgeda/src/o_text_basic.c:391
+#: libgeda/src/o_picture.c:116 libgeda/src/o_text_basic.c:392
msgid "Setting angle to 0\n"
msgstr ""
#: libgeda/src/o_picture.c:151 libgeda/src/o_picture.c:162
-#: libgeda/src/o_picture.c:913
+#: libgeda/src/o_picture.c:914
#, c-format
msgid "Failed to load image from embedded data [%s]: %s\n"
msgstr ""
@@ -487,12 +447,12 @@ msgid "Base64 decoding failed."
msgstr ""
#: libgeda/src/o_picture.c:153 libgeda/src/o_picture.c:164
-#: libgeda/src/o_picture.c:915
+#: libgeda/src/o_picture.c:916
msgid "Falling back to file loading. Picture unembedded.\n"
msgstr ""
-#: libgeda/src/o_picture.c:175 libgeda/src/o_picture.c:901
-#: libgeda/src/o_picture.c:950
+#: libgeda/src/o_picture.c:175 libgeda/src/o_picture.c:902
+#: libgeda/src/o_picture.c:951
#, c-format
msgid "Failed to load image from file [%s]: %s\n"
msgstr ""
@@ -506,16 +466,16 @@ msgstr ""
msgid "Error loading picture from file: %s.\n"
msgstr ""
-#: libgeda/src/o_picture.c:252
+#: libgeda/src/o_picture.c:253
msgid "ERROR: o_picture_save: unable to encode the picture.\n"
msgstr ""
-#: libgeda/src/o_picture.c:928
+#: libgeda/src/o_picture.c:929
#, c-format
msgid "Picture [%s] has been embedded\n"
msgstr ""
-#: libgeda/src/o_picture.c:968
+#: libgeda/src/o_picture.c:969
#, c-format
msgid "Picture [%s] has been unembedded\n"
msgstr ""
@@ -536,23 +496,23 @@ msgstr ""
msgid "Found a zero length pin: [ %s ]\n"
msgstr ""
-#: libgeda/src/o_text_basic.c:377
+#: libgeda/src/o_text_basic.c:378
#, c-format
msgid "Found a zero size text string [ %c %d %d %d %d %d %d %d %d ]\n"
msgstr ""
-#: libgeda/src/o_text_basic.c:389
+#: libgeda/src/o_text_basic.c:390
#, c-format
msgid "Found an unsupported text angle [ %c %d %d %d %d %d %d %d %d ]\n"
msgstr "Desteklenmeyen yazı açısı bulundu [ %c %d %d %d %d %d %d %d %d ]\n"
-#: libgeda/src/o_text_basic.c:411
+#: libgeda/src/o_text_basic.c:412
#, c-format
msgid "Found an unsupported text alignment [ %c %d %d %d %d %d %d %d %d ]\n"
msgstr ""
"Desteklenmeyen yazı hizlanması bulundu [ %c %d %d %d %d %d %d %d %d ]\n"
-#: libgeda/src/o_text_basic.c:413
+#: libgeda/src/o_text_basic.c:414
msgid "Setting alignment to LOWER_LEFT\n"
msgstr ""
@@ -649,18 +609,18 @@ msgstr ""
msgid "Value in color map entry must be #f or a string"
msgstr ""
-#: libgeda/src/s_hierarchy.c:90
+#: libgeda/src/s_hierarchy.c:94
#, c-format
msgid ""
"hierarchy loop detected while visiting page:\n"
" \"%s\"\n"
msgstr ""
-#: libgeda/src/s_hierarchy.c:185
+#: libgeda/src/s_hierarchy.c:187
msgid "There are no schematics above the current one!\n"
msgstr ""
-#: libgeda/src/s_hierarchy.c:266
+#: libgeda/src/s_hierarchy.c:267
#, c-format
msgid "ERROR in s_hierarchy_traverse: schematic not found: %s\n"
msgstr ""
@@ -675,12 +635,12 @@ msgstr ""
msgid "s_page_delete: Unable to delete backup file %s."
msgstr ""
-#: libgeda/src/s_page.c:504
+#: libgeda/src/s_page.c:499
#, c-format
msgid "Saved [%s]\n"
msgstr "[%s] kaydedildi\n"
-#: libgeda/src/s_page.c:510
+#: libgeda/src/s_page.c:505
#, c-format
msgid "Could NOT save [%s]\n"
msgstr "[%s] kaydedilemedi.\n"
@@ -695,6 +655,9 @@ msgstr ""
msgid "Could not find [%s] in any SourceLibrary\n"
msgstr ""
+#~ msgid "%s:%i:%i: %s\n"
+#~ msgstr "%s:%i:%i: %s\n"
+
#~ msgid "o_save: Could not open [%s]\n"
#~ msgstr "o_save: açılamadı [%s]\n"
diff --git a/libgeda/po/zh_CN.po b/libgeda/po/zh_CN.po
index 01d863a..c626b52 100644
--- a/libgeda/po/zh_CN.po
+++ b/libgeda/po/zh_CN.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2010-11-07 10:51+0000\n"
+"POT-Creation-Date: 2011-01-15 23:36-0500\n"
"PO-Revision-Date: 2010-02-06 22:10+0000\n"
"Last-Translator: �� <rainofchaos@xxxxxxxxx>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -42,12 +42,12 @@ msgstr "gEDA �路�"
msgid "gEDA Schematic Symbol"
msgstr "gEDA �表符�"
-#: libgeda/src/a_basic.c:181
+#: libgeda/src/a_basic.c:182
#, c-format
msgid "o_save_objects: object %p has unknown type '%c'\n"
msgstr "o_save_objects: ç?©ä½? %p å??å?«æ?ªç?¥ç±»å?? '%c'\n"
-#: libgeda/src/a_basic.c:429
+#: libgeda/src/a_basic.c:417
#, c-format
msgid ""
"Read unexpected embedded symbol start marker in [%s] :\n"
@@ -55,7 +55,7 @@ msgid ""
"%s<<\n"
msgstr ""
-#: libgeda/src/a_basic.c:458
+#: libgeda/src/a_basic.c:446
#, c-format
msgid ""
"Read unexpected embedded symbol end marker in [%s] :\n"
@@ -63,7 +63,7 @@ msgid ""
"%s<<\n"
msgstr ""
-#: libgeda/src/a_basic.c:487
+#: libgeda/src/a_basic.c:475
#, c-format
msgid ""
"Read an old format sym/sch file!\n"
@@ -71,7 +71,7 @@ msgid ""
"[%s]\n"
msgstr ""
-#: libgeda/src/a_basic.c:493
+#: libgeda/src/a_basic.c:481
#, c-format
msgid ""
"Read garbage in [%s] :\n"
@@ -84,12 +84,12 @@ msgstr ""
msgid "Failed to stat [%s]: %s"
msgstr ""
-#: libgeda/src/f_basic.c:219
+#: libgeda/src/f_basic.c:221
#, c-format
msgid "Cannot find file %s: %s"
msgstr ""
-#: libgeda/src/f_basic.c:257
+#: libgeda/src/f_basic.c:264
#, c-format
msgid ""
"\n"
@@ -98,166 +98,126 @@ msgid ""
"\n"
msgstr ""
-#: libgeda/src/f_basic.c:259
+#: libgeda/src/f_basic.c:266
msgid "I could not guess if it is newer, so you have to do it manually.\n"
msgstr ""
-#: libgeda/src/f_basic.c:261
+#: libgeda/src/f_basic.c:268
msgid ""
"The backup copy is newer than the schematic, so it seems you should load it "
"instead of the original file.\n"
msgstr ""
-#: libgeda/src/f_basic.c:263
+#: libgeda/src/f_basic.c:270
msgid ""
"Gschem usually makes backup copies automatically, and this situation happens "
"when it crashed or it was forced to exit abruptly.\n"
msgstr ""
-#: libgeda/src/f_basic.c:266
+#: libgeda/src/f_basic.c:273
msgid ""
"\n"
"Run gschem and correct the situation.\n"
"\n"
msgstr ""
-#: libgeda/src/f_basic.c:355
+#: libgeda/src/f_basic.c:362
#, c-format
msgid "Can't get the real filename of %s."
msgstr ""
-#: libgeda/src/f_basic.c:375
+#: libgeda/src/f_basic.c:382
#, c-format
msgid "Could NOT set previous backup file [%s] read-write\n"
msgstr ""
-#: libgeda/src/f_basic.c:381
+#: libgeda/src/f_basic.c:388
#, c-format
msgid "Can't save backup file: %s."
msgstr ""
-#: libgeda/src/f_basic.c:391
+#: libgeda/src/f_basic.c:398
#, c-format
msgid "Could NOT set backup file [%s] readonly\n"
msgstr ""
-#: libgeda/src/f_basic.c:680
+#: libgeda/src/f_basic.c:687
#, c-format
msgid "%s: %s"
msgstr ""
-#: libgeda/src/f_print.c:118
+#: libgeda/src/f_print.c:119
msgid "Unable to get time of day in f_print_header()\n"
msgstr ""
-#: libgeda/src/f_print.c:160
+#: libgeda/src/f_print.c:161
#, c-format
msgid "Unable to open the prolog file `%s' for reading in f_print_header()\n"
msgstr ""
-#: libgeda/src/f_print.c:177
+#: libgeda/src/f_print.c:178
#, c-format
msgid "Error during reading of the prolog file `%s' in f_print_header()\n"
msgstr ""
-#: libgeda/src/f_print.c:183
+#: libgeda/src/f_print.c:184
msgid ""
"Error during writing of the output postscript file in f_print_header()\n"
msgstr ""
-#: libgeda/src/f_print.c:196
+#: libgeda/src/f_print.c:197
msgid "Giving up on printing\n"
msgstr ""
-#: libgeda/src/f_print.c:366
+#: libgeda/src/f_print.c:368
#, c-format
msgid "Could not open [%s] for printing\n"
msgstr ""
-#: libgeda/src/f_print.c:399
+#: libgeda/src/f_print.c:402
#, c-format
msgid "Could not execute command [%s] for printing\n"
msgstr ""
-#: libgeda/src/f_print.c:674
+#: libgeda/src/f_print.c:676
msgid "Too many UTF-8 characters, cannot print\n"
msgstr ""
-#: libgeda/src/g_basic.c:101
-#, c-format
-msgid "%s:%i:%i: %s\n"
-msgstr ""
-
-#: libgeda/src/g_basic.c:108
-#, c-format
-msgid "Unknown file: %s\n"
-msgstr ""
-
-#: libgeda/src/g_basic.c:114
-#, c-format
-msgid "Evaluation failed: %s\n"
-msgstr ""
-
-#: libgeda/src/g_basic.c:115
-msgid "Enable debugging for more detailed information\n"
-msgstr ""
-
-#: libgeda/src/g_basic.c:258
-#, c-format
-msgid "Could not find [%s] for interpretation\n"
-msgstr ""
-
-#: libgeda/src/g_rc.c:134
-#, c-format
-msgid "RC file [%s] already read in.\n"
-msgstr ""
-
-#: libgeda/src/g_rc.c:179
-#, c-format
-msgid "Read system config file [%%s]\n"
-msgstr ""
-
-#: libgeda/src/g_rc.c:180
-#, c-format
-msgid "Did not find required system config file [%%s]\n"
-msgstr ""
-
-#: libgeda/src/g_rc.c:214
-#, c-format
-msgid "Read user config file [%%s]\n"
+#: libgeda/src/g_basic.c:257
+msgid ""
+"\n"
+"Backtrace:\n"
msgstr ""
-#: libgeda/src/g_rc.c:215
-#, c-format
-msgid "Did not find optional user config file [%%s]\n"
+#: libgeda/src/g_rc.c:225
+msgid "Config file already loaded"
msgstr ""
-#: libgeda/src/g_rc.c:246
+#: libgeda/src/g_rc.c:260
#, c-format
-msgid "Read local config file [%%s]\n"
+msgid "Parsed config from [%s]\n"
msgstr ""
-#: libgeda/src/g_rc.c:247
+#: libgeda/src/g_rc.c:273
#, c-format
-msgid "Did not find optional local config file [%%s]\n"
+msgid "Unable to parse config from [%s]: %s"
msgstr ""
-#: libgeda/src/g_rc.c:284
-#, c-format
-msgid "Read specified %s file [%%s]\n"
+#: libgeda/src/g_rc.c:290
+msgid "ERROR: An unknown error occurred while parsing configuration files."
msgstr ""
-#: libgeda/src/g_rc.c:286
+#: libgeda/src/g_rc.c:301 libgeda/src/g_rc.c:302
#, c-format
-msgid "Did not find specified %s file [%%s]\n"
+msgid "ERROR: %s\n"
msgstr ""
-#: libgeda/src/g_rc.c:336
+#: libgeda/src/g_rc.c:308
#, c-format
-msgid "Could not find any %s file!\n"
+msgid "ERROR: The %s log may contain more information.\n"
msgstr ""
-#: libgeda/src/g_rc.c:953
+#: libgeda/src/g_rc.c:1003
msgid ""
"WARNING: using a string for 'always-promote-attributes' is deprecated. Use a "
"list of strings instead\n"
@@ -272,7 +232,7 @@ msgstr ""
#: libgeda/src/o_bus_basic.c:182 libgeda/src/o_circle_basic.c:288
#: libgeda/src/o_line_basic.c:264 libgeda/src/o_net_basic.c:174
#: libgeda/src/o_path_basic.c:192 libgeda/src/o_pin_basic.c:187
-#: libgeda/src/o_text_basic.c:419
+#: libgeda/src/o_text_basic.c:420
#, c-format
msgid "Found an invalid color [ %s ]\n"
msgstr ""
@@ -281,7 +241,7 @@ msgstr ""
#: libgeda/src/o_bus_basic.c:183 libgeda/src/o_circle_basic.c:289
#: libgeda/src/o_line_basic.c:265 libgeda/src/o_net_basic.c:175
#: libgeda/src/o_path_basic.c:193 libgeda/src/o_pin_basic.c:188
-#: libgeda/src/o_text_basic.c:420
+#: libgeda/src/o_text_basic.c:421
msgid "Setting color to default color\n"
msgstr ""
@@ -330,46 +290,46 @@ msgstr ""
msgid "Found a zero radius circle [ %c %d %d %d %d ]\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:476
+#: libgeda/src/o_complex_basic.c:481
#, c-format
msgid ""
"Component not found:\n"
" %s"
msgstr ""
-#: libgeda/src/o_complex_basic.c:683
+#: libgeda/src/o_complex_basic.c:686
#, c-format
msgid "Found a component with an invalid rotation [ %c %d %d %d %d %d %s ]\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:695
+#: libgeda/src/o_complex_basic.c:698
#, c-format
msgid ""
"Found a component with an invalid mirror flag [ %c %d %d %d %d %d %s ]\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:1008
+#: libgeda/src/o_complex_basic.c:1014
#, c-format
msgid ""
"WARNING: Symbol version parse error on refdes %s:\n"
"\tCould not parse symbol file symversion=%s\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:1012
+#: libgeda/src/o_complex_basic.c:1018
#, c-format
msgid ""
"WARNING: Symbol version parse error on refdes %s:\n"
"\tCould not parse symbol file symversion=\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:1028
+#: libgeda/src/o_complex_basic.c:1034
#, c-format
msgid ""
"WARNING: Symbol version parse error on refdes %s:\n"
"\tCould not parse attached symversion=%s\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:1053
+#: libgeda/src/o_complex_basic.c:1059
#, c-format
msgid ""
"WARNING: Symbol version oddity on refdes %s:\n"
@@ -377,24 +337,24 @@ msgid ""
"symbol file\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:1067
+#: libgeda/src/o_complex_basic.c:1073
#, c-format
msgid ""
"WARNING: Symbol version mismatch on refdes %s (%s):\n"
"\tSymbol in library is newer than instantiated symbol\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:1095
+#: libgeda/src/o_complex_basic.c:1101
#, c-format
msgid "\tMAJOR VERSION CHANGE (file %.3f, instantiated %.3f, %s)!\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:1113
+#: libgeda/src/o_complex_basic.c:1119
#, c-format
msgid "\tMinor version change (file %.3f, instantiated %.3f)\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:1124
+#: libgeda/src/o_complex_basic.c:1130
#, c-format
msgid ""
"WARNING: Symbol version oddity on refdes %s:\n"
@@ -461,12 +421,12 @@ msgstr ""
msgid "Found an unsupported picture angle [ %d ]\n"
msgstr ""
-#: libgeda/src/o_picture.c:116 libgeda/src/o_text_basic.c:391
+#: libgeda/src/o_picture.c:116 libgeda/src/o_text_basic.c:392
msgid "Setting angle to 0\n"
msgstr ""
#: libgeda/src/o_picture.c:151 libgeda/src/o_picture.c:162
-#: libgeda/src/o_picture.c:913
+#: libgeda/src/o_picture.c:914
#, c-format
msgid "Failed to load image from embedded data [%s]: %s\n"
msgstr ""
@@ -476,12 +436,12 @@ msgid "Base64 decoding failed."
msgstr ""
#: libgeda/src/o_picture.c:153 libgeda/src/o_picture.c:164
-#: libgeda/src/o_picture.c:915
+#: libgeda/src/o_picture.c:916
msgid "Falling back to file loading. Picture unembedded.\n"
msgstr ""
-#: libgeda/src/o_picture.c:175 libgeda/src/o_picture.c:901
-#: libgeda/src/o_picture.c:950
+#: libgeda/src/o_picture.c:175 libgeda/src/o_picture.c:902
+#: libgeda/src/o_picture.c:951
#, c-format
msgid "Failed to load image from file [%s]: %s\n"
msgstr ""
@@ -495,16 +455,16 @@ msgstr ""
msgid "Error loading picture from file: %s.\n"
msgstr ""
-#: libgeda/src/o_picture.c:252
+#: libgeda/src/o_picture.c:253
msgid "ERROR: o_picture_save: unable to encode the picture.\n"
msgstr ""
-#: libgeda/src/o_picture.c:928
+#: libgeda/src/o_picture.c:929
#, c-format
msgid "Picture [%s] has been embedded\n"
msgstr ""
-#: libgeda/src/o_picture.c:968
+#: libgeda/src/o_picture.c:969
#, c-format
msgid "Picture [%s] has been unembedded\n"
msgstr ""
@@ -525,22 +485,22 @@ msgstr ""
msgid "Found a zero length pin: [ %s ]\n"
msgstr ""
-#: libgeda/src/o_text_basic.c:377
+#: libgeda/src/o_text_basic.c:378
#, c-format
msgid "Found a zero size text string [ %c %d %d %d %d %d %d %d %d ]\n"
msgstr ""
-#: libgeda/src/o_text_basic.c:389
+#: libgeda/src/o_text_basic.c:390
#, c-format
msgid "Found an unsupported text angle [ %c %d %d %d %d %d %d %d %d ]\n"
msgstr ""
-#: libgeda/src/o_text_basic.c:411
+#: libgeda/src/o_text_basic.c:412
#, c-format
msgid "Found an unsupported text alignment [ %c %d %d %d %d %d %d %d %d ]\n"
msgstr ""
-#: libgeda/src/o_text_basic.c:413
+#: libgeda/src/o_text_basic.c:414
msgid "Setting alignment to LOWER_LEFT\n"
msgstr ""
@@ -637,18 +597,18 @@ msgstr ""
msgid "Value in color map entry must be #f or a string"
msgstr ""
-#: libgeda/src/s_hierarchy.c:90
+#: libgeda/src/s_hierarchy.c:94
#, c-format
msgid ""
"hierarchy loop detected while visiting page:\n"
" \"%s\"\n"
msgstr ""
-#: libgeda/src/s_hierarchy.c:185
+#: libgeda/src/s_hierarchy.c:187
msgid "There are no schematics above the current one!\n"
msgstr ""
-#: libgeda/src/s_hierarchy.c:266
+#: libgeda/src/s_hierarchy.c:267
#, c-format
msgid "ERROR in s_hierarchy_traverse: schematic not found: %s\n"
msgstr ""
@@ -663,12 +623,12 @@ msgstr ""
msgid "s_page_delete: Unable to delete backup file %s."
msgstr ""
-#: libgeda/src/s_page.c:504
+#: libgeda/src/s_page.c:499
#, c-format
msgid "Saved [%s]\n"
msgstr ""
-#: libgeda/src/s_page.c:510
+#: libgeda/src/s_page.c:505
#, c-format
msgid "Could NOT save [%s]\n"
msgstr ""
diff --git a/libgeda/po/zh_TW.po b/libgeda/po/zh_TW.po
index de460c5..4d25861 100644
--- a/libgeda/po/zh_TW.po
+++ b/libgeda/po/zh_TW.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: geda\n"
"Report-Msgid-Bugs-To: geda-bug@xxxxxxxx\n"
-"POT-Creation-Date: 2010-11-07 10:51+0000\n"
+"POT-Creation-Date: 2011-01-15 23:36-0500\n"
"PO-Revision-Date: 2010-02-06 22:10+0000\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: gEDA developers <geda-dev@xxxxxxxx>\n"
@@ -42,12 +42,12 @@ msgstr ""
msgid "gEDA Schematic Symbol"
msgstr ""
-#: libgeda/src/a_basic.c:181
+#: libgeda/src/a_basic.c:182
#, c-format
msgid "o_save_objects: object %p has unknown type '%c'\n"
msgstr ""
-#: libgeda/src/a_basic.c:429
+#: libgeda/src/a_basic.c:417
#, c-format
msgid ""
"Read unexpected embedded symbol start marker in [%s] :\n"
@@ -55,7 +55,7 @@ msgid ""
"%s<<\n"
msgstr ""
-#: libgeda/src/a_basic.c:458
+#: libgeda/src/a_basic.c:446
#, c-format
msgid ""
"Read unexpected embedded symbol end marker in [%s] :\n"
@@ -63,7 +63,7 @@ msgid ""
"%s<<\n"
msgstr ""
-#: libgeda/src/a_basic.c:487
+#: libgeda/src/a_basic.c:475
#, c-format
msgid ""
"Read an old format sym/sch file!\n"
@@ -71,7 +71,7 @@ msgid ""
"[%s]\n"
msgstr ""
-#: libgeda/src/a_basic.c:493
+#: libgeda/src/a_basic.c:481
#, c-format
msgid ""
"Read garbage in [%s] :\n"
@@ -84,12 +84,12 @@ msgstr ""
msgid "Failed to stat [%s]: %s"
msgstr ""
-#: libgeda/src/f_basic.c:219
+#: libgeda/src/f_basic.c:221
#, c-format
msgid "Cannot find file %s: %s"
msgstr "������ %s: %s"
-#: libgeda/src/f_basic.c:257
+#: libgeda/src/f_basic.c:264
#, c-format
msgid ""
"\n"
@@ -98,166 +98,126 @@ msgid ""
"\n"
msgstr ""
-#: libgeda/src/f_basic.c:259
+#: libgeda/src/f_basic.c:266
msgid "I could not guess if it is newer, so you have to do it manually.\n"
msgstr ""
-#: libgeda/src/f_basic.c:261
+#: libgeda/src/f_basic.c:268
msgid ""
"The backup copy is newer than the schematic, so it seems you should load it "
"instead of the original file.\n"
msgstr ""
-#: libgeda/src/f_basic.c:263
+#: libgeda/src/f_basic.c:270
msgid ""
"Gschem usually makes backup copies automatically, and this situation happens "
"when it crashed or it was forced to exit abruptly.\n"
msgstr ""
-#: libgeda/src/f_basic.c:266
+#: libgeda/src/f_basic.c:273
msgid ""
"\n"
"Run gschem and correct the situation.\n"
"\n"
msgstr ""
-#: libgeda/src/f_basic.c:355
+#: libgeda/src/f_basic.c:362
#, c-format
msgid "Can't get the real filename of %s."
msgstr ""
-#: libgeda/src/f_basic.c:375
+#: libgeda/src/f_basic.c:382
#, c-format
msgid "Could NOT set previous backup file [%s] read-write\n"
msgstr ""
-#: libgeda/src/f_basic.c:381
+#: libgeda/src/f_basic.c:388
#, c-format
msgid "Can't save backup file: %s."
msgstr ""
-#: libgeda/src/f_basic.c:391
+#: libgeda/src/f_basic.c:398
#, c-format
msgid "Could NOT set backup file [%s] readonly\n"
msgstr ""
-#: libgeda/src/f_basic.c:680
+#: libgeda/src/f_basic.c:687
#, c-format
msgid "%s: %s"
msgstr "%s: %s"
-#: libgeda/src/f_print.c:118
+#: libgeda/src/f_print.c:119
msgid "Unable to get time of day in f_print_header()\n"
msgstr ""
-#: libgeda/src/f_print.c:160
+#: libgeda/src/f_print.c:161
#, c-format
msgid "Unable to open the prolog file `%s' for reading in f_print_header()\n"
msgstr ""
-#: libgeda/src/f_print.c:177
+#: libgeda/src/f_print.c:178
#, c-format
msgid "Error during reading of the prolog file `%s' in f_print_header()\n"
msgstr ""
-#: libgeda/src/f_print.c:183
+#: libgeda/src/f_print.c:184
msgid ""
"Error during writing of the output postscript file in f_print_header()\n"
msgstr ""
-#: libgeda/src/f_print.c:196
+#: libgeda/src/f_print.c:197
msgid "Giving up on printing\n"
msgstr ""
-#: libgeda/src/f_print.c:366
+#: libgeda/src/f_print.c:368
#, c-format
msgid "Could not open [%s] for printing\n"
msgstr ""
-#: libgeda/src/f_print.c:399
+#: libgeda/src/f_print.c:402
#, c-format
msgid "Could not execute command [%s] for printing\n"
msgstr ""
-#: libgeda/src/f_print.c:674
+#: libgeda/src/f_print.c:676
msgid "Too many UTF-8 characters, cannot print\n"
msgstr ""
-#: libgeda/src/g_basic.c:101
-#, c-format
-msgid "%s:%i:%i: %s\n"
-msgstr ""
-
-#: libgeda/src/g_basic.c:108
-#, c-format
-msgid "Unknown file: %s\n"
-msgstr ""
-
-#: libgeda/src/g_basic.c:114
-#, c-format
-msgid "Evaluation failed: %s\n"
-msgstr ""
-
-#: libgeda/src/g_basic.c:115
-msgid "Enable debugging for more detailed information\n"
-msgstr ""
-
-#: libgeda/src/g_basic.c:258
-#, c-format
-msgid "Could not find [%s] for interpretation\n"
-msgstr ""
-
-#: libgeda/src/g_rc.c:134
-#, c-format
-msgid "RC file [%s] already read in.\n"
-msgstr ""
-
-#: libgeda/src/g_rc.c:179
-#, c-format
-msgid "Read system config file [%%s]\n"
-msgstr ""
-
-#: libgeda/src/g_rc.c:180
-#, c-format
-msgid "Did not find required system config file [%%s]\n"
-msgstr ""
-
-#: libgeda/src/g_rc.c:214
-#, c-format
-msgid "Read user config file [%%s]\n"
+#: libgeda/src/g_basic.c:257
+msgid ""
+"\n"
+"Backtrace:\n"
msgstr ""
-#: libgeda/src/g_rc.c:215
-#, c-format
-msgid "Did not find optional user config file [%%s]\n"
+#: libgeda/src/g_rc.c:225
+msgid "Config file already loaded"
msgstr ""
-#: libgeda/src/g_rc.c:246
+#: libgeda/src/g_rc.c:260
#, c-format
-msgid "Read local config file [%%s]\n"
+msgid "Parsed config from [%s]\n"
msgstr ""
-#: libgeda/src/g_rc.c:247
+#: libgeda/src/g_rc.c:273
#, c-format
-msgid "Did not find optional local config file [%%s]\n"
+msgid "Unable to parse config from [%s]: %s"
msgstr ""
-#: libgeda/src/g_rc.c:284
-#, c-format
-msgid "Read specified %s file [%%s]\n"
+#: libgeda/src/g_rc.c:290
+msgid "ERROR: An unknown error occurred while parsing configuration files."
msgstr ""
-#: libgeda/src/g_rc.c:286
+#: libgeda/src/g_rc.c:301 libgeda/src/g_rc.c:302
#, c-format
-msgid "Did not find specified %s file [%%s]\n"
+msgid "ERROR: %s\n"
msgstr ""
-#: libgeda/src/g_rc.c:336
+#: libgeda/src/g_rc.c:308
#, c-format
-msgid "Could not find any %s file!\n"
+msgid "ERROR: The %s log may contain more information.\n"
msgstr ""
-#: libgeda/src/g_rc.c:953
+#: libgeda/src/g_rc.c:1003
msgid ""
"WARNING: using a string for 'always-promote-attributes' is deprecated. Use a "
"list of strings instead\n"
@@ -272,7 +232,7 @@ msgstr ""
#: libgeda/src/o_bus_basic.c:182 libgeda/src/o_circle_basic.c:288
#: libgeda/src/o_line_basic.c:264 libgeda/src/o_net_basic.c:174
#: libgeda/src/o_path_basic.c:192 libgeda/src/o_pin_basic.c:187
-#: libgeda/src/o_text_basic.c:419
+#: libgeda/src/o_text_basic.c:420
#, c-format
msgid "Found an invalid color [ %s ]\n"
msgstr ""
@@ -281,7 +241,7 @@ msgstr ""
#: libgeda/src/o_bus_basic.c:183 libgeda/src/o_circle_basic.c:289
#: libgeda/src/o_line_basic.c:265 libgeda/src/o_net_basic.c:175
#: libgeda/src/o_path_basic.c:193 libgeda/src/o_pin_basic.c:188
-#: libgeda/src/o_text_basic.c:420
+#: libgeda/src/o_text_basic.c:421
msgid "Setting color to default color\n"
msgstr ""
@@ -330,46 +290,46 @@ msgstr ""
msgid "Found a zero radius circle [ %c %d %d %d %d ]\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:476
+#: libgeda/src/o_complex_basic.c:481
#, c-format
msgid ""
"Component not found:\n"
" %s"
msgstr ""
-#: libgeda/src/o_complex_basic.c:683
+#: libgeda/src/o_complex_basic.c:686
#, c-format
msgid "Found a component with an invalid rotation [ %c %d %d %d %d %d %s ]\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:695
+#: libgeda/src/o_complex_basic.c:698
#, c-format
msgid ""
"Found a component with an invalid mirror flag [ %c %d %d %d %d %d %s ]\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:1008
+#: libgeda/src/o_complex_basic.c:1014
#, c-format
msgid ""
"WARNING: Symbol version parse error on refdes %s:\n"
"\tCould not parse symbol file symversion=%s\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:1012
+#: libgeda/src/o_complex_basic.c:1018
#, c-format
msgid ""
"WARNING: Symbol version parse error on refdes %s:\n"
"\tCould not parse symbol file symversion=\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:1028
+#: libgeda/src/o_complex_basic.c:1034
#, c-format
msgid ""
"WARNING: Symbol version parse error on refdes %s:\n"
"\tCould not parse attached symversion=%s\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:1053
+#: libgeda/src/o_complex_basic.c:1059
#, c-format
msgid ""
"WARNING: Symbol version oddity on refdes %s:\n"
@@ -377,24 +337,24 @@ msgid ""
"symbol file\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:1067
+#: libgeda/src/o_complex_basic.c:1073
#, c-format
msgid ""
"WARNING: Symbol version mismatch on refdes %s (%s):\n"
"\tSymbol in library is newer than instantiated symbol\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:1095
+#: libgeda/src/o_complex_basic.c:1101
#, c-format
msgid "\tMAJOR VERSION CHANGE (file %.3f, instantiated %.3f, %s)!\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:1113
+#: libgeda/src/o_complex_basic.c:1119
#, c-format
msgid "\tMinor version change (file %.3f, instantiated %.3f)\n"
msgstr ""
-#: libgeda/src/o_complex_basic.c:1124
+#: libgeda/src/o_complex_basic.c:1130
#, c-format
msgid ""
"WARNING: Symbol version oddity on refdes %s:\n"
@@ -461,12 +421,12 @@ msgstr ""
msgid "Found an unsupported picture angle [ %d ]\n"
msgstr ""
-#: libgeda/src/o_picture.c:116 libgeda/src/o_text_basic.c:391
+#: libgeda/src/o_picture.c:116 libgeda/src/o_text_basic.c:392
msgid "Setting angle to 0\n"
msgstr ""
#: libgeda/src/o_picture.c:151 libgeda/src/o_picture.c:162
-#: libgeda/src/o_picture.c:913
+#: libgeda/src/o_picture.c:914
#, c-format
msgid "Failed to load image from embedded data [%s]: %s\n"
msgstr ""
@@ -476,12 +436,12 @@ msgid "Base64 decoding failed."
msgstr ""
#: libgeda/src/o_picture.c:153 libgeda/src/o_picture.c:164
-#: libgeda/src/o_picture.c:915
+#: libgeda/src/o_picture.c:916
msgid "Falling back to file loading. Picture unembedded.\n"
msgstr ""
-#: libgeda/src/o_picture.c:175 libgeda/src/o_picture.c:901
-#: libgeda/src/o_picture.c:950
+#: libgeda/src/o_picture.c:175 libgeda/src/o_picture.c:902
+#: libgeda/src/o_picture.c:951
#, c-format
msgid "Failed to load image from file [%s]: %s\n"
msgstr ""
@@ -495,16 +455,16 @@ msgstr ""
msgid "Error loading picture from file: %s.\n"
msgstr ""
-#: libgeda/src/o_picture.c:252
+#: libgeda/src/o_picture.c:253
msgid "ERROR: o_picture_save: unable to encode the picture.\n"
msgstr ""
-#: libgeda/src/o_picture.c:928
+#: libgeda/src/o_picture.c:929
#, c-format
msgid "Picture [%s] has been embedded\n"
msgstr ""
-#: libgeda/src/o_picture.c:968
+#: libgeda/src/o_picture.c:969
#, c-format
msgid "Picture [%s] has been unembedded\n"
msgstr ""
@@ -525,22 +485,22 @@ msgstr ""
msgid "Found a zero length pin: [ %s ]\n"
msgstr ""
-#: libgeda/src/o_text_basic.c:377
+#: libgeda/src/o_text_basic.c:378
#, c-format
msgid "Found a zero size text string [ %c %d %d %d %d %d %d %d %d ]\n"
msgstr ""
-#: libgeda/src/o_text_basic.c:389
+#: libgeda/src/o_text_basic.c:390
#, c-format
msgid "Found an unsupported text angle [ %c %d %d %d %d %d %d %d %d ]\n"
msgstr ""
-#: libgeda/src/o_text_basic.c:411
+#: libgeda/src/o_text_basic.c:412
#, c-format
msgid "Found an unsupported text alignment [ %c %d %d %d %d %d %d %d %d ]\n"
msgstr ""
-#: libgeda/src/o_text_basic.c:413
+#: libgeda/src/o_text_basic.c:414
msgid "Setting alignment to LOWER_LEFT\n"
msgstr ""
@@ -637,18 +597,18 @@ msgstr ""
msgid "Value in color map entry must be #f or a string"
msgstr ""
-#: libgeda/src/s_hierarchy.c:90
+#: libgeda/src/s_hierarchy.c:94
#, c-format
msgid ""
"hierarchy loop detected while visiting page:\n"
" \"%s\"\n"
msgstr ""
-#: libgeda/src/s_hierarchy.c:185
+#: libgeda/src/s_hierarchy.c:187
msgid "There are no schematics above the current one!\n"
msgstr ""
-#: libgeda/src/s_hierarchy.c:266
+#: libgeda/src/s_hierarchy.c:267
#, c-format
msgid "ERROR in s_hierarchy_traverse: schematic not found: %s\n"
msgstr ""
@@ -663,12 +623,12 @@ msgstr ""
msgid "s_page_delete: Unable to delete backup file %s."
msgstr ""
-#: libgeda/src/s_page.c:504
+#: libgeda/src/s_page.c:499
#, c-format
msgid "Saved [%s]\n"
msgstr ""
-#: libgeda/src/s_page.c:510
+#: libgeda/src/s_page.c:505
#, c-format
msgid "Could NOT save [%s]\n"
msgstr ""
commit 5093ab820cdee5c2a41a4106567bbc87570f2e04
Author: Ales Hvezda <ahvezda@xxxxxxxx>
Commit: Ales Hvezda <ahvezda@xxxxxxxx>
Updated package version, release date, and libgeda revision for 1.7.0
diff --git a/configure.ac b/configure.ac
index 69a5c5a..bb6f33a 100644
--- a/configure.ac
+++ b/configure.ac
@@ -8,7 +8,7 @@ dnl directory.
# Set up configuration system
#####################################################################
-AC_INIT([gEDA/gaf], [1.6.1], [geda-bug@xxxxxxxx], [geda-gaf])
+AC_INIT([gEDA/gaf], [1.7.0], [geda-bug@xxxxxxxx], [geda-gaf])
AC_PREREQ([2.60])
AC_CONFIG_SRCDIR([libgeda/src/libgeda.c])
@@ -24,7 +24,7 @@ AC_GNU_SOURCE # FIXME for some reason this is needed?
# Do version number magic
#####################################################################
-AX_GIT_VERSION([20100214])
+AX_GIT_VERSION([20110116])
# This is used for keeping the ChangeLog files up-to-date
AC_SUBST([CHANGELOG_BASE], [1.0-20070526])
@@ -159,7 +159,7 @@ AX_DATA_DIRS
# Where should PCB footprints be searched for?
AX_PCB_DIRS
# Set up libgeda with the correct ld version number
-AX_LIBGEDA([38:1:0])
+AX_LIBGEDA([39:0:0])
#####################################################################
# Generate output
_______________________________________________
geda-cvs mailing list
geda-cvs@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-cvs