There are currently two ways of specifying that a symbol has an underlying schematic or schematics:
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)
Once the symbol is open, the user can edit it and save it.
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.
The job is handed over to "gschemdoc", which makes a best-effort attempt of finding relevant documentation.
The documention would normally be in PDF, HTML, text or image format, but gschemdoc tries to be as transparent as possible on this account.
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 URL.
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.
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".
Failing that, the file name for the symbol itself will be used as basis for the search.
Ales Hvezda 2006-01-23