📄 faq.xml
字号:
<?xml version="1.0"?><!DOCTYPE faq SYSTEM "faq.dtd" ><!-- $Id: faq.xml,v 1.5 2002/12/13 17:20:25 edg Exp $ --><!--A quick note on the syntax of this file ========================================This XML file is based on the DTD specified in "faq.dtd". See "faq.dtd" fora rigourous definition; a simple overview is given here, to help in makingquick additions and modifications.The FAQ is composed of two parts : a <head> and a <body>. The <head>contains the title (in our case, "NEdit Frequently Asked Questions"), thelist of <maintainers>, a <summary> which gets displayed ahead of allquestions, a section showing how to download the FAQ (<download>) andother, less important stuff.The <body> part is composed of many FAQ <section>s. A section has a titleand groups several FAQ entries. A particular section exists, called<about-section>, which contains the description of the FAQ itself.A section is generally composed of several "Question 'N' Answer" entries(<qna>). A <qna> contains a question (<q>) and the answer to that question(<a>). An identifier must be given to each <qna>, via the attribute "id". Alonger version of the question may be specified via <long-q> as anotherelement of <qna>; in this case, the <q> is displayed in a table ofquestions, while the longer and more complete version, <long-q>, isdisplayed along with the answer.The <long-q> and <a> elements contain text paragraphs. The <q> doesn'tcontain paragraphs and behaves like a single paragraph itself.A text paragraph is indicated by one of the elements <p>, <blockquote>,<ul>, <ol> and <pre> (which, in the DTD, are collectively referred to as%paragraph-styles;). The <p> denotes a basic paragraph and contains text. The <blockquote> indicates an indent, and it contains other paragraphs inside. A nested <blockquote> will indent relative to the previous one. The <ul> and <ol> indicate respectively an unnumbered and a numbered list. Both <ul> and <ol> contain one or many <li> elements. A <li> element contains text. The <pre> indicates a preformatted piece of text, which will be output with no further modifications.Paragraphs of type <p> and <li>, as well as <q> and a few other elements ofthe <head>, contain text. Text is composed of free text and style elements.The style elements are the following : <email> indicates an e-mail address. <img> indicates an image. It has a required attribute "src" which must be a URL referring to the image, and a "alt" attribute containing alternate text, used for non-image-capable formats. <site> indicates a web site. The text between <site> and </site> must be a URL. <link> indicates a HTTP hyperlink. Its required attribute "href" must be the URL to link to. An attribute "alt" may contain alternate text. <em> stands for emphasized text. <strong> stands for strong text. <tt> is used for terminal output and for the contents of configuration files. <code> is used for command names, when included inline within text. Generally, <pre> paragraphs are used for several lines of code.The distinction between <tt> and <code> and furthermore <pre> is not soclear. A clearer and better definition is needed.======================================== --><faq><head><title>NEdit Frequently Asked Questions</title><version>2001/10/01</version><maintainers><!-- several maintainers can be added --><maintainer> <name>Florian Xhumari</name> <email>Florian.Xhumari@free.fr</email> <subject>NEdit FAQ</subject></maintainer></maintainers><summary><p>NEdit is a popular GUI-style text editor for Unix and VMS systems.These are answers to the most frequently asked questions todiscuss@nedit.org. This information is also available from:</p><blockquote> <p><site>ftp://ftp.nedit.org/pub/</site><current>/FAQ,</p></blockquote><p>and from the NEdit web page at:</p><blockquote> <p><site>http://nedit.org</site>.</p></blockquote></summary><download> <p>The FAQ is available for download in a variety of formats.</p> <ul> <li>HTML pages: <site>faq.tar.gz</site> or <site>faq.zip</site>.</li> <li>Plain text: <site>faq.txt</site>.</li> <li>XML source: <site>faq.xml</site> as well as its DTD <site>faq.dtd</site>.</li> </ul> </download></head><body> <about-section id="about"> <title>About the NEdit FAQ</title> <p>This FAQ is written in XML and translated to HTML using an XSL stylesheet. The XML source is processed using <link href="http://www.jclark.com/">James Clark's</link> XSLT processor <link href="http://www.jclark.com/xml/xt.html">XT</link> and XML parser <link href="http://www.jclark.com/xml/xp">XP</link>. </p> <p>The XSL stylesheet used to generate the HTML version is <link href="faq.xsl">here</link>.</p> <p>The text version is generated in three steps: first, <link href="faq-txt.xsl">an XSL stylesheet</link> is used to generate a simple HTML. Then, <link href="faq-txt-pass2.xsl">a second XSL stylesheet</link> transforms the HTML into plain text. <link href="faq-txt.awk">An awk script</link> then performs the word wrapping.</p> <p>For any questions about or contributions to the FAQ, please send a mail to the <link href="mailto:Florian.Xhumari@free.fr">maintainers</link>. </p></about-section><section id="sect_information"><title>Where to get information</title><qna id="first-info"><q>Where can I get information about NEdit?</q><a><p>The NEdit web page is at:</p><blockquote><p><site>http://nedit.org</site></p></blockquote><p>and it is mirrored in Australia at:</p><blockquote><p><site>http://www.au.nedit.org/</site></p></blockquote><p>The primary ftp site for NEdit is:</p><blockquote><p><site>ftp://ftp.nedit.org/pub</site></p></blockquote><p>which has a mirror in The Netherlands:</p><blockquote><p><site>ftp://ftp.nl.nedit.org/pub/mirror/NEdit</site></p></blockquote><p>The NEdit ftp site has executables for most Unix and VMSsystems, sources, documentation, and contributed software.</p><p>The first and easiest place to look for help with NEdit is the NEdit Helpmenu. The bottom item in the menu (Problems/Bugs) has answers to the mostcommonly asked questions about NEdit, which are not duplicated here. Alsocheck the platform specific information in the README file packaged inthe NEdit distribution kits.</p><p>If you have a problem that you really can't figure out, send mailto <email>discuss@nedit.org</email>, and see if anyone else might behaving the same trouble. The nedit developers also subscribe to thislist, and hopefully someone will be able to answer your question.If you are a Silicon Graphics user and NEditcame bundled on your system, you can also contact SGI's technical support.</p></a></qna><qna id="mailing-lists"><q>Are there any mailing lists for NEdit users?</q><a><p>There are two separate mailing lists for nedit users, and one fordevelopers. Users may post to the developer mailing list to reportbugs and communicate with the nedit developers.</p><p>The lists are:</p><ul><li><email>discuss@nedit.org</email>: general discussion, questions andanswers among nedit users and developers.</li><li><email>develop@nedit.org</email>: communication among and withnedit developers. Developers should also subscribe to the discusslist.</li><li><email>announce@nedit.org</email>: a low-volume mailing list forannouncing new versions.</li></ul><p>Please note that only subscribers can send mail to the list. </p><p>The nedit developers subscribe to both<email>discuss@nedit.org</email> and <email>develop@nedit.org</email>,either of which may be used for reporting bugs. If you're not sure,or you think the report might be of interest to the general nedituser community, send the report to <email>discuss@nedit.org</email>. If it'ssomething obvious and boring, like we misspelled "anemometer" in theon-line help, send it to <email>develop@nedit.org</email>.</p><p>Please do not cross post to both lists!</p><p>In order to subscribe to a list, send mail to <email>majordomo@nedit.org</email>with one or more of the following in the body of the message:</p><pre> subscribe announce subscribe discuss subscribe develop</pre><p>To unsubscribe do the same with the keyword <strong>unsubscribe</strong>.</p><pre> unsubscribe announce unsubscribe discuss unsubscribe develop</pre><p>After subscribing, you will receive copies of all of the emailsubmitted to the lists. You may submit mail to the discussion list bysending it to the appropriate list: <email>discuss@nedit.org</email>,<email>develop@nedit.org</email> or<email>announce@nedit.org</email>.</p><p>The archives of the old mailing lists (nedit_discuss@fnal_gov andnedit_announce@fnal.gov) can be found on egroups.com:</p><blockquote> <ul> <li><site>http://www.egroups.com/group/nedit_discuss/</site></li> <li><site>http://www.egroups.com/group/nedit_announce/</site></li> </ul></blockquote><p>For more information about the mailing lists, refer to the <linkhref="http://nedit.org/community/mailing.shtml">mailing listssection</link> in the NEdit site.</p></a></qna><qna id="N44"><q>Where can I get binaries / executables for machines other thanthose available at NEdit site?</q><a><p>In past versions, we separated "supported" and "unsupported" executablesand divided them between the binary and contrib directories. With moresupported systems, you're less likely to find executables in the contribdirectory, but it's worth a peek, anyhow. If you can't find anythingappropriate, you can try asking in a usenet news group appropriate to yoursystem. Other places to try are, the<email>discuss@nedit.org</email> mailing list, or<site>news:comp.windows.x.apps</site>or <site>news:comp.editors</site>.</p></a></qna><qna id="info_contrib"><q>What can I contribute?</q><a><p>If you use and enjoy NEdit, and feel like giving somethingback to the NEdit user community, contact<email>develop@nedit.org</email>. If you have ported NEdit to a newmachine, written a useful set of macros, or would like to contributeto an ongoing development project, we'd love to hear from you.</p></a></qna></section><section id="sect_reporting"><title>Diagnosing and reporting problems</title><qna id="N124"><q>How do I report problems I've encountered using NEdit ?</q><a><p>If you have a problem which is not covered in the on-line help, in this FAQ,or in the README file specific to your system, you can report it to<email>discuss@nedit.org</email> (usage questions) or,<email>develop@nedit.org</email> (error reports). Note that these lists onlyallow members to post, and if you are not a member, your post will probably dedelayed in reaching the list. Alternatively you can use the bug tracker onSourceforge (<site>http://sourceforge.net/projects/nedit/</site>) to reportbugs and make feature requests. Below are some suggestions for information youcan provide to help in diagnosing your problem.</p><p>Because NEdit runs on a large number of different platforms and environments,many problems are platform-specific. It's always helpful to know what kind ofsystem it's being run on. Sometimes, strange behavior can also be traced tothe X server software or window manager, so you may want to include informationon these as well.</p><p>The origin of the NEdit executable is often important, particularly, whetherit came from the NEdit site (<site>http://www.nedit.org</site>), was builtlocally, or came from some other ftp server or freeware distribution CD. Despite the fact that Motif appears on almost all Unix platforms, the Motiflibraries still vary from one machine to another. Be sure to mention whetheryou're using Lesstif or Motif. As of version 5.2 a summary with buildinformation is present under 'Version' in the Help menu.</p><p>If you are having configuration or appearance problems, you should probablylook at the output from the command:</p><pre> appres NEdit nedit</pre><p>The <code>appres</code> command will show you the resources thatNEdit actually sees when it runs, including "stray" resourcesintended for other programs but not properly qualified by the programname. It will also give you a final objective check as to whetherresource settings that you have made are actually readable byNEdit.</p></a></qna></section><section id="sect_building">⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -