PageRenderTime 53ms CodeModel.GetById 16ms RepoModel.GetById 0ms app.codeStats 0ms

/jEdit/tags/jedit-4-2-pre4/doc/FAQ/faq-general.xml

#
XML | 647 lines | 621 code | 20 blank | 6 comment | 0 complexity | 1d2d326f9c0c850a526d23ddde9c8f75 MD5 | raw file
Possible License(s): BSD-3-Clause, AGPL-1.0, Apache-2.0, LGPL-2.0, LGPL-3.0, GPL-2.0, CC-BY-SA-3.0, LGPL-2.1, GPL-3.0, MPL-2.0-no-copyleft-exception, IPL-1.0
  1. <!-- jEdit buffer-local properties: -->
  2. <!-- :indentSize=4:noTabs=false:maxLineLen=72:tabSize=4: -->
  3. <!-- :xml.root=faq.xml: -->
  4. <!-- jEdit FAQ -->
  5. <!-- Copyright (C) 2003 John Gellene, Kris Kopicki -->
  6. <sect1 id="general"><title>General Questions</title>
  7. <para>
  8. This section deals with some background information, how to obtain the
  9. latest version of jEdit and how to obtain further information/help.
  10. </para>
  11. <qandaset defaultlabel="qanda">
  12. <qandadiv id="about">
  13. <title>About jEdit</title>
  14. <qandaentry>
  15. <question id="whatis"><para>
  16. What is jEdit?
  17. </para></question>
  18. <answer><para>
  19. jEdit is a programmer's text editor written in Java, being
  20. developed by Slava Pestov and others. It has an easy to use
  21. interface that resembles that of many other Windows and MacOS
  22. text editors. It is also highly customizable, and contains a
  23. <quote>plugin</quote> architecture that allows its features to
  24. be extended by additional programs.
  25. </para></answer>
  26. </qandaentry>
  27. <qandaentry>
  28. <question id="difftext"><para>
  29. What is the difference between a text editor and a word
  30. processor?
  31. </para></question>
  32. <answer><para>
  33. These categories are not absolute but refer to the primary
  34. purpose of an editing program and the focus of its features.
  35. </para>
  36. <para>
  37. A text editor is an application that edits files containing plain text
  38. without automatically formatting the text for printing or other publication.
  39. Typically the contents of such a file consists of data used by another
  40. application - for example, source code that a compiler will process or
  41. markup text that a web browser will display. A word processor deals with
  42. the preparation of documents for printing or similar publication.
  43. Besides editing text, a modern word processor allows the user to choose
  44. multiple fonts, margin sizes, line spacing, indentation, and a variety
  45. of other details that affect the appearance of the document being
  46. edited. In a text editor, these features are present, if at all, only in
  47. a basic form, and for the limited purpose of helping the user compose
  48. and organize the text. In place of word processing features, a text
  49. editor contains many features that allow the user to prepare and work with
  50. text quickly and efficiently.
  51. </para>
  52. <para>
  53. The jEdit application is a text editor, not a word processor. It
  54. contains a large assortment of features for manipulating source code,
  55. markup text, and other text files. As a programmer's text editor, it
  56. also has many features to help programmers manage their projects and
  57. work with other programming tools.
  58. </para></answer>
  59. </qandaentry>
  60. <qandaentry>
  61. <question id="features"><para>
  62. What features does jEdit have?
  63. </para></question>
  64. <answer><para>
  65. The short answer is, too many to list here. There is a detailed
  66. list available on the <ulink
  67. url="http://www.jedit.org/index.php?page=features">jEdit web
  68. site</ulink>, but here are some of the major features:
  69. </para>
  70. <itemizedlist>
  71. <listitem><para>
  72. Comprehensive online help
  73. </para></listitem>
  74. <listitem><para>
  75. Multiple editor windows and split editing panes within a single
  76. editing window
  77. </para></listitem>
  78. <listitem><para>
  79. Unlimited undo/redo
  80. </para></listitem>
  81. <listitem><para>
  82. Copy and paste with an unlimited number of clipboards
  83. (known as <quote>registers</quote>)
  84. </para></listitem>
  85. <listitem><para>
  86. <quote>Markers</quote> for remembering positions
  87. in files to return to later
  88. </para></listitem>
  89. <listitem><para>
  90. Rectangular selection
  91. </para></listitem>
  92. <listitem><para>
  93. Multiple selection for manipulating several chunks of text at once
  94. </para></listitem>
  95. <listitem><para>
  96. Syntax highlighting for more than 80 file types
  97. </para></listitem>
  98. <listitem><para>
  99. Intelligent bracket matching that skips quoted literals
  100. and comments
  101. </para></listitem>
  102. <listitem><para>
  103. Auto indent and word wrap
  104. </para></listitem>
  105. <listitem><para>
  106. Abbreviations
  107. </para></listitem>
  108. <listitem><para>
  109. <quote>Folding</quote> display mode that hides levels of
  110. indented text specified by the user
  111. </para></listitem>
  112. <listitem><para>
  113. Search and replace using both literal text and regular expressions
  114. </para></listitem>
  115. <listitem><para>
  116. <quote>HyperSearch</quote> option to show all found
  117. matches in a list
  118. </para></listitem>
  119. <listitem><para>
  120. File management functions available from within jEdit, including
  121. deleting and renaming files and creating new directories
  122. </para></listitem>
  123. <listitem><para>
  124. Choice of character encoding for loading and saving files
  125. </para></listitem>
  126. <listitem><para>
  127. Automatic compression and decompression of GZipped (.gz) files
  128. </para></listitem>
  129. <listitem><para>
  130. Plugin support for loading files from ZIP and TAR archives
  131. </para></listitem>
  132. <listitem><para>
  133. Plugin support for loading and saving files on FTP servers
  134. </para></listitem>
  135. <listitem><para>
  136. Fully customizable keyboard shortcuts, tool bar and right-click
  137. context menu
  138. </para></listitem>
  139. <listitem><para>
  140. Macro system permitting recording and writing of macros in the
  141. BeanShell scripting language
  142. </para></listitem>
  143. <listitem><para>
  144. An internal <quote>plugin manager</quote> that downloads and installs
  145. new and updated plugins from within jEdit
  146. </para></listitem>
  147. </itemizedlist>
  148. </answer>
  149. </qandaentry>
  150. <qandaentry>
  151. <question id="what-plugin"><para>
  152. What is a jEdit <quote>plugin</quote>?
  153. </para></question>
  154. <answer><para>
  155. A plugin is an application that is designed to work with jEdit
  156. by providing additional features that can be used from within
  157. the main program. Often the plugin will provide a visible user
  158. interface in a window that can be docked to jEdit's main view
  159. window.
  160. </para>
  161. <para>
  162. There are currently over 60 publicly available plugins that
  163. provide such services as a Java source code browser, a
  164. command-line shell, templated text insertion, and source code
  165. project management. They can be downloaded, installed, and kept
  166. current from within jEdit's <quote>Plugin Manager</quote>.
  167. There is also a section of the jEdit web site called <ulink
  168. url="http://plugins.jedit.org/">Plugin Central</ulink> that
  169. maintains a descriptive index and download links for all publicly
  170. available plugins.
  171. </para>
  172. <para>
  173. Additional questions and answers regarding plugins may be found
  174. in the section of this document entitled <quote>Working with
  175. Plugins</quote>.
  176. </para></answer>
  177. </qandaentry>
  178. <qandaentry>
  179. <question id="get-doc"><para>
  180. How do I get documentation on jEdit?
  181. </para></question>
  182. <answer><para>
  183. There is a comprehensive User's Guide available from within the program
  184. using the <guimenu>Help</guimenu> menu. The User's Guide can also
  185. be downloaded from the <ulink
  186. url="http://www.jedit.org/index.php?page=download&amp;platform=source">
  187. jEdit web site</ulink> in Portable Document Format (PDF), suitable for
  188. online display or printing.
  189. </para></answer>
  190. </qandaentry>
  191. <qandaentry>
  192. <question id="is-newsgroup"><para>
  193. Is there a newsgroup or mailing list devoted to jEdit?
  194. </para></question>
  195. <answer><para>
  196. Currently there is no newsgroup devoted to jEdit. There are three
  197. active mailing lists that are freely available by subscription:
  198. </para>
  199. <itemizedlist>
  200. <listitem><para>
  201. The <ulink url=
  202. "http://lists.sourceforge.net/lists/listinfo/jedit-users">
  203. jedit-users list</ulink>, for comments and questions about
  204. using jEdit and its features
  205. </para></listitem>
  206. <listitem><para>
  207. The <ulink url=
  208. "http://lists.sourceforge.net/lists/listinfo/jedit-devel">
  209. jedit-devel list</ulink>, for discussion of development issues by
  210. members of the developer team and other interested persons
  211. </para></listitem>
  212. <listitem><para>
  213. The <ulink url=
  214. "http://lists.sourceforge.net/lists/listinfo/jedit-announce">
  215. jedit-announce list</ulink>, a low-volume list used for announcing
  216. new releases of jEdit and plugins
  217. </para></listitem>
  218. </itemizedlist>
  219. <para>
  220. Each of these lists can be obtained on a full-text message or a daily
  221. digest basis. The daily digest bundles groups of postings in a single
  222. email message.
  223. </para>
  224. <para>
  225. If you are only interested in version announcements and plugin updates,
  226. <ulink url="http://lists.sourceforge.net/lists/listinfo/jedit-announce">
  227. subscribe to the jedit-announce list</ulink>. If you would like to participate
  228. in discussion or ask questions regarding jEdit, <ulink url=
  229. "http://lists.sourceforge.net/lists/listinfo/jedit-users">subscribe to the
  230. jedit-users list</ulink>. If you are interested in jEdit's development or want
  231. to write plugins, <ulink
  232. url="http://lists.sourceforge.net/lists/listinfo/jedit-devel">
  233. subscribe to jedit-devel</ulink>.
  234. </para>
  235. <para>
  236. Do not cross-post to both lists. All jEdit developers are
  237. subscribed to both the jedit-users and jedit-devel lists, so a post to
  238. jedit-users will be seen by most members of both lists. Also, keep in
  239. mind that both jEdit-users and
  240. jEdit-devel are high-traffic lists, and can fill up your mailbox unless
  241. you check your email regularly.
  242. </para>
  243. </answer>
  244. </qandaentry>
  245. <qandaentry>
  246. <question id="is-website"><para>
  247. Is there a web site devoted to jEdit?
  248. </para></question>
  249. <answer><para>
  250. There are several. The official <ulink url="http://www.jedit.org">jEdit
  251. web site</ulink> contains extensive information on all things having to
  252. do with jEdit. There are also resources available for those interested
  253. in jEdit development on the <ulink url=
  254. "http://sourceforge.net/projects/jedit">jEdit project page</ulink> of
  255. the <ulink url="http://sourceforge.net">SourceForge web site</ulink>.
  256. </para>
  257. <para>
  258. The <ulink url="http://community.jedit.org">jEdit Community</ulink> web
  259. site has articles on jEdit and related topics, user-submitted macros and
  260. other download resources, and listings of web links of interest to jEdit
  261. users. It has a message board system to allow users to ask
  262. questions and provide feedback on the project without having to subscribe
  263. to jEdit's mailing lists. Because the message boards have relatively low
  264. volume, using the mailing lists will often be a more effective
  265. approach.
  266. </para>
  267. <para>
  268. The jEdit Community site also has an <quote>Interactive FAQ</quote>
  269. facility that allows you to post questions to be answered by
  270. other users, and a screenshot gallery containing images
  271. submitted by users.
  272. </para></answer>
  273. </qandaentry>
  274. <qandaentry>
  275. <question id="copyright"><para>
  276. Are there copyright restrictions on the use of jEdit?
  277. </para></question>
  278. <answer><para>
  279. The jEdit application is free, <quote>Open Source</quote> software released
  280. under the <ulink url="http://www.gnu.org/licenses/licenses.html#GPL">
  281. GNU General Public License</ulink>. This ensures that jEdit and its source
  282. code remains freely available for use and distribution by the public.
  283. For specific copyright questions, you should review the General Public
  284. License and seek appropriate advice. Broadly speaking, there are no
  285. restrictions on the use of the program as a text editor, and its source
  286. code can be copied or modified for use in another program that is
  287. governed by the General Public License.
  288. </para>
  289. <para>
  290. Plugin application that are available using jEdit's Plugin Manager
  291. facility, as well as plugins available through the <ulink
  292. url="http://plugins.jedit.org">Plugin Central</ulink> web site or
  293. <ulink url="http://community.jedit.org">jEdit Community</ulink>, are
  294. governed either by the General Public License or another commonly
  295. recognized <quote>Open Source</quote> software license. This means
  296. that use of the application, including use for commercial purposes,
  297. is unrestricted without any requirement of royalty or license fee payments.
  298. To incorporate source code or an application or plugin as a whole in another
  299. application, you must consult the specific license terms to determine
  300. whether and on what basis you are permitted to do so.
  301. </para>
  302. </answer>
  303. </qandaentry>
  304. <qandaentry>
  305. <question id="java-only"><para>
  306. Is jEdit only useful for programming in Java?
  307. </para></question>
  308. <answer><para>
  309. Absolutely not. Many of the jEdit's plugin applications, and a few of
  310. the macros distributed with the program, target the Java language or
  311. integrate tools used in Java development. However, the core application
  312. is designed to work with any programming or markup language. Included
  313. with jEdit are packages providing syntax highlighting,
  314. abbreviations and other programming support for over 60 programming
  315. languages and file types, including C, C++, C#,
  316. Cobol, HTML, Java, Javascript, Lisp, Pascal, Perl, PHP, Python,
  317. TCL, Visual Basic and XML. The full list can be found on the
  318. <ulink url="http://www.jedit.org/index.php?page=features">jEdit web
  319. site</ulink>.
  320. </para></answer>
  321. </qandaentry>
  322. <qandaentry>
  323. <question id="knowing-java"><para>
  324. Do I need to know Java to use jEdit?
  325. </para></question>
  326. <answer><para>
  327. No. In fact, you do not need to know any specific programming language
  328. other than the ones with which you work.
  329. </para>
  330. <para>
  331. At some point in your use of jEdit, you will no doubt want to write your
  332. own macros to execute long or complex routines with a single command or
  333. keyboard shortcut. Macros in jEdit are written in a simplified dialect
  334. of Java called <ulink url="http://www.beanshell.org"> BeanShell</ulink>.
  335. Its syntax will be familiar to users of Java, C++ and other
  336. object-oriented languages, and it is not hard to learn even if you have
  337. no experience with those languages. The User's Guide provided
  338. with jEdit contains an extensive tutorial on writing macros.
  339. </para></answer>
  340. </qandaentry>
  341. <qandaentry>
  342. <question id="needed-software"><para>
  343. What software do I need to install and run jEdit?
  344. </para></question>
  345. <answer><para>
  346. Since jEdit runs on a Java platform, at a minimum you will need a Java
  347. Runtime Environment (JRE) package. If you are planning to use jEdit to
  348. program in Java, you will need a full Java Development Kit (JDK) package.
  349. We recommend obtaining a JDK package.
  350. </para>
  351. <para>
  352. The current version of jEdit, version 4.1, requires a Java runtime
  353. environment having a release version of 1.3 or greater. It will
  354. not run on versions 1.1 or 1.2. The <ulink
  355. url="http://www.jedit.org/index.php?page=compatibility">jEdit web
  356. site</ulink> contains a detailed discussion on the compatibility of
  357. various publicly available JDK's for the major operating systems.
  358. </para></answer>
  359. </qandaentry>
  360. <qandaentry>
  361. <question id="just-learning"><para>
  362. I've just started to learn programming. Is jEdit a good choice for my
  363. first text editor?
  364. </para></question>
  365. <answer><para>
  366. It is an excellent choice. Its basic features are extremely easy to use,
  367. and you will find things like abbreviations, keyboard shortcuts and
  368. macros to be great time-savers. It has built-in packages called
  369. <quote>edit modes</quote> that automatically display keywords, tags, and
  370. other program elements in different colors, making it easier to view and
  371. organize your code. It works well with many Open Source and proprietary
  372. programming tools. Because of its extensive customization features, it
  373. can adapt to your preferences and work patterns as you become more
  374. experienced. Finally, it's free, so you can buy a lot of programming texts
  375. with the money you will save.
  376. </para></answer>
  377. </qandaentry>
  378. </qandadiv>
  379. <!--******************************************************** Answers -->
  380. <qandadiv id="get-answers-div">
  381. <title>Getting answers</title>
  382. <qandaentry>
  383. <question id="get-answers"><para>
  384. How do I get answers to my questions about jEdit?
  385. </para></question>
  386. <answer>
  387. <para>
  388. You should look for answers in the following places:
  389. </para>
  390. <itemizedlist>
  391. <listitem><para>
  392. The User's Guide available from the application's
  393. <guimenu>Help</guimenu> menu.
  394. </para></listitem>
  395. <listitem><para>
  396. This FAQ document.
  397. </para></listitem>
  398. <listitem><para>
  399. The archives of jEdit's mailing lists. Archives for both the
  400. <ulink url="http://www.geocrawler.com/redir-sf.php3?list=jedit-users">
  401. jedit-users list</ulink> and the
  402. <ulink url="http://www.geocrawler.com/redir-sf.php3?list=jedit-devel">
  403. jedit-devel list</ulink> are available.
  404. </para></listitem>
  405. </itemizedlist>
  406. <para>
  407. If you cannot find help using those resources, post your question to the
  408. <ulink url="mailto:jedit-users@lists.sourceforge.net"> jedit-users
  409. list</ulink>. You will have to <ulink
  410. url="http://lists.sourceforge.net/lists/listinfo/jedit-users">
  411. subscribe to the mailing list</ulink> in order to
  412. post, but it is well worth it, and you can elect to have daily bundles
  413. of messages sent to you to keep email traffic down. Many questions
  414. are answered on the mailing list within 24 hours. The developers who
  415. respond to user questions generally do not send direct replies, so you
  416. will need to monitor messages from the mailing list is order to
  417. obtain an answer.
  418. </para>
  419. </answer>
  420. </qandaentry>
  421. <qandaentry>
  422. <question id="interactive-help"><para>
  423. Where can I get interactive help for jEdit?
  424. </para></question>
  425. <answer><para>
  426. There is an IRC channel, <filename>#jedit</filename>, available
  427. on the irc.freenode.net server that is dedicated to jEdit support
  428. and discussion among developers. You can reach it using
  429. any IRC client (including Chatzilla), as well as the IRC plugin
  430. for jEdit.
  431. </para>
  432. <para>
  433. There is almost always someone from the developer team
  434. signed on the channel. Just say hello and describe your problem.
  435. </para></answer>
  436. </qandaentry>
  437. </qandadiv>
  438. <qandadiv id="bugs">
  439. <title>Reporting bugs</title>
  440. <qandaentry>
  441. <question id="report-bugs"><para>
  442. How do I report a bug I have found in jEdit?
  443. </para></question>
  444. <answer><para>
  445. To be as helpful as possible to the jEdit developer team and other
  446. users, you should use the <ulink
  447. url="http://sourceforge.net/tracker/index.php?group_id=588&amp;atid=100588">
  448. bug tracker database</ulink> that the jEdit project maintains on the
  449. <ulink url="http://sourceforge.net/">SourceForge web site</ulink>. You
  450. do not need to be a SourceForge member to post a bug report.
  451. </para>
  452. <para>
  453. Before posting a bug report, spend a few moments searching the bug
  454. database to see if a similar report has already been made. The bug
  455. tracker has a search facility that will let search for bug reports using
  456. a variety of criteria. If you find a similar bug report, and you
  457. have additional information to contribute, post a comment
  458. to the report. If you do not find a similar bug report, submit a new
  459. report.
  460. </para></answer>
  461. </qandaentry>
  462. <qandaentry>
  463. <question id="bug-report"><para>
  464. What information should I include in a bug report?
  465. </para></question>
  466. <answer><para>
  467. The form in the bug tracker report provides several fields for
  468. submitting information. If you are unsure about a particular
  469. item, leave it at the default setting provided in the form.
  470. </para>
  471. <para>
  472. The more important fields are <quote>Category</quote>,
  473. <quote>Summary</quote> and the <quote>Initial comment</quote>.
  474. When you write your initial comment describing the bug, you
  475. should specify the versions of jEdit, the Java platform and
  476. operating system you are using, because bugs often arise that
  477. are specific to particular versions. Sometimes the bug
  478. arises from the Java runtime environment or even the
  479. operating system, and knowing these details helps the
  480. developer team design testing and other debugging strategies.
  481. </para>
  482. <para>
  483. One of the macros installed with jEdit is called <guimenuitem>Make Bug
  484. Report</guimenuitem>. You will it find under the
  485. <guimenuitem>Misc</guimenuitem> category of the <guimenu>Macros
  486. </guimenu> menu. This macro extracts information regarding your jEdit
  487. installation and a stack trace from the last error recorded by jEdit's
  488. Activity Log and places it in a new text buffer. In many cases, the
  489. information furnished by the macro is all that is necessary to provide a
  490. helpful description of a bug. You can simply cut and paste the
  491. output of the macro into the <quote>Initial comment</quote> field of the
  492. bug report form.
  493. </para></answer>
  494. </qandaentry>
  495. <qandaentry>
  496. <question id="bug-track">
  497. <para>
  498. How do I track the status of a jEdit bug report?
  499. </para>
  500. </question>
  501. <answer>
  502. <para>
  503. If you know the bug report number, go to this web address:
  504. <userinput>http://sourceforge.net/tracker/index.php?func=detail&amp;aid=######&amp;group_id=588&amp;atid=100588</userinput>,
  505. where <userinput>######</userinput> is the bug report number. If you don't know the bug report number,
  506. you can browse and search the <ulink
  507. url="http://sourceforge.net/tracker/index.php?group_id=588&amp;atid=100588">
  508. bug database</ulink> to find the problem in which you are interested.
  509. </para>
  510. </answer>
  511. </qandaentry>
  512. </qandadiv>
  513. <qandadiv id="contact">
  514. <title>Contacting jEdit developers</title>
  515. <qandaentry>
  516. <question id="contact-team"><para>
  517. How do I contact members of the jEdit developer team?
  518. </para></question>
  519. <answer><para>
  520. If you want to ask a question, make a feature request or offer other
  521. general comments, the easiest way is to join and post a message to the
  522. <ulink url="mailto:jedit-users@lists.sourceforge.net">
  523. jedit-users mailing list</ulink>. All developers are members. If you are
  524. interested in working on jEdit or writing a plugin for it, use the
  525. <ulink url="mailto:jedit-users@lists.sourceforge.net">
  526. jedit-devel list</ulink>. Email addresses for individual developers
  527. can be found on the <ulink
  528. url="http://sourceforge.net/project/memberlist.php?group_id=588">
  529. SourceForge web site</ulink>.
  530. </para></answer>
  531. </qandaentry>
  532. </qandadiv>
  533. <qandadiv id="latest-version">
  534. <title>Getting the latest version</title>
  535. <qandaentry>
  536. <question id="get-latest-version"><para>
  537. How do I obtain the latest version of jEdit?
  538. </para></question>
  539. <answer><para>
  540. The program is in a continuing state of evolution. It is usually
  541. available in two versions, a <quote>stable</quote> version and a
  542. <quote>development</quote> version. A stable version represents a
  543. release of jEdit that is considered to be free of serious bugs or
  544. performance problems and suitable for general use. A
  545. <quote>development</quote> version includes new features or new elements
  546. of program design that require testing and possible further refinement.
  547. A development version contains the token <quote>pre</quote> in its
  548. version number, as in <literal>4.1pre5</literal>.
  549. </para>
  550. <para>
  551. The latest stable and development versions of jEdit are always
  552. available from the <ulink url="http://www.jedit.org">jEdit
  553. web site</ulink> and from the <ulink url="http://sourceforge.net/
  554. projects/jedit">jEdit project page</ulink> of the
  555. <ulink url="http://sourceforge.net">SourceForge web site</ulink>,
  556. which hosts jEdit's development resources.
  557. </para>
  558. <para>
  559. In addition, a plugin named <application>Check jEdit
  560. Version</application> can be run from within jEdit by selecting
  561. <guimenuitem>Check jEdit Version</guimenuitem> from the application's
  562. <guimenu>Plugins</guimenu> menu. It queries the jEdit web site, compares
  563. version information with the version of the currently running
  564. instance of jEdit, and reports the result to the user in a message box.
  565. It will tell you if you do not have the latest version of jEdit, regardless
  566. of whether that version is in <quote>stable</quote> or
  567. <quote>development</quote> form.
  568. </para>
  569. <para>
  570. Finally, if you subscribe to the <ulink
  571. url="http://lists.sourceforge.net/lists/listinfo/jedit-announce">
  572. jedit-announce</ulink> or <ulink
  573. url="http://lists.sourceforge.net/lists/listinfo/jedit-users">
  574. jedit-users</ulink> mailing lists, you will receive a email whenever
  575. a new release of jEdit becomes available.
  576. </para></answer>
  577. </qandaentry>
  578. <qandaentry>
  579. <question id="get-source"><para>
  580. How do I obtain a copy of the jEdit source code?
  581. </para></question>
  582. <answer><para>
  583. The latest version of jEdit's source code is available from the
  584. <ulink url="http://www.jedit.org/index.php?page=download&amp;platform=source">
  585. jEdit web site</ulink> or the <ulink url=
  586. "http://sourceforge.net/project/showfiles.php?group_id=588">
  587. SourceForge web site</ulink>. The web site provides the source code for the
  588. latest stable and development version, while the SourceForge site has
  589. a more extensive archive covering earlier versions.
  590. </para>
  591. <para>
  592. If you are interested in testing the absolutely latest changes to jEdit,
  593. and you are familiar with compiling your own Java programs and working
  594. with CVS, you can download the current code maintained in the <ulink
  595. url="http://sourceforge.net/cvs/?group_id=588">SourceForge
  596. CVS repository</ulink>.
  597. </para></answer>
  598. </qandaentry>
  599. <qandaentry>
  600. <question id="get-latest-faq"><para>
  601. Where can I get the latest version of this document?</para>
  602. </question><answer>
  603. <para>
  604. The latest release of this document is available at the
  605. <ulink
  606. url="http://jedit-community.sourceforge.net/modules.php?op=modload&amp;name=Include_Pages&amp;file=index&amp;req=viewarticle&amp;artid=5">
  607. jEdit Community web site</ulink>.
  608. </para>
  609. </answer>
  610. </qandaentry>
  611. <qandaentry>
  612. <question id="jedit-compile">
  613. <para>
  614. How do you set the classpath and compile the Java files in jEdit?
  615. </para>
  616. </question>
  617. <answer>
  618. <para>
  619. Consult an article on the <ulink url="http://community.jedit.org">jEdit
  620. Community</ulink> web site entitled <quote>Build jEdit yourself: the 'Open'
  621. in Open Source</quote>.
  622. </para>
  623. </answer>
  624. </qandaentry>
  625. </qandadiv>
  626. </qandaset>
  627. </sect1>