mirror of https://github.com/tLDP/LDP
Added a part about compiling vim, can't help you with the screenshots I'm afraid.
Sorted out some more tags (<application></application> was left out a bit too often).
This commit is contained in:
parent
6213ffcd8e
commit
9c8944b9d9
|
@ -40,7 +40,7 @@
|
|||
<ulink url="http://www.vim.org">http://www.vim.org</ulink>
|
||||
</para>
|
||||
<para>
|
||||
No mention of <application>Emacs</application> is complete
|
||||
No mention of text editors is complete
|
||||
without talking about <application>vi</application>.
|
||||
The <application>VIM</application> (Vi IMproved)
|
||||
editor has the functionality of
|
||||
|
@ -61,9 +61,11 @@
|
|||
Debian users will want the following package: vim.
|
||||
For an X interface (including <acronym>GUI</acronym> menus and
|
||||
mouse control) users will want
|
||||
<application>gvim</application>. The g in gvim is for
|
||||
<application>gvim</application>. The <quote>g</quote> in gvim is for
|
||||
<quote>Graphical</quote>.
|
||||
</para>
|
||||
<para><application>VIM</application> compiles very easy should you need to build your own. Both <command>vim</command> and <command>gvim</command> are built by default. Syntax highlighting is included but not enabled by default if you have to start from scratch; use the <command>:syntax enable</command> command in <application>VIM</application> to turn this feature on.
|
||||
</para>
|
||||
</section>
|
||||
|
||||
<section id="vim-new-file">
|
||||
|
@ -139,7 +141,7 @@
|
|||
</screen>
|
||||
|
||||
<para>
|
||||
You'll also have to convert the dbhelper.vim file to unix formatting:
|
||||
You'll also have to convert the <filename>dbhelper.vim</filename> file to unix formatting:
|
||||
</para>
|
||||
|
||||
<screen>
|
||||
|
@ -176,9 +178,9 @@
|
|||
</para>
|
||||
|
||||
<para>
|
||||
The epcEdit program allows you to edit XML files.
|
||||
It has the advantages of not needing to know Emacs or
|
||||
vi before starting, and is cross-platform, working in both
|
||||
The <application>epcEdit</application> program allows you to edit XML files.
|
||||
It has the advantages of not needing to know <application>Emacs</application> or
|
||||
<application>vi</application> before starting, and is cross-platform, working in both
|
||||
Windows and Linux. This is a commercial application, and
|
||||
pricing can be found at
|
||||
<ulink url="http://www.tksgml.de/pricing.html">
|
||||
|
@ -205,7 +207,7 @@
|
|||
<imagedata format="JPG" fileref="sgeditscreenshot.jpg"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>The screen shot of the epcEdit program shows a
|
||||
<phrase>The screen shot of the <application>epcEdit program shows a
|
||||
tree on the left side that has the document in a
|
||||
hierarchy, while the right side shows the document.
|
||||
Tags are shown with a gray background.</phrase>
|
||||
|
@ -227,11 +229,11 @@
|
|||
</para>
|
||||
|
||||
<para>
|
||||
To be fair, nedit is more
|
||||
To be fair, <application>nedit</application> is more
|
||||
for programmers, so it might seem a bit of overkill for new
|
||||
users and especially non-programmers. All that aside, it's
|
||||
extremely powerful, allowing for syntax highlighting. Unlike
|
||||
epcEdit, nedit doesn't allow you to automatically insert tags
|
||||
<application>epcEdit</application>, <application>nedit</application> doesn't allow you to automatically insert tags
|
||||
or automatically validate your code. However, it does allow
|
||||
for shell commands to be run against the contents of the
|
||||
window (as opposed to saving the file, then checking).
|
||||
|
@ -252,7 +254,7 @@ XML file instead of an SGML file -->
|
|||
<imagedata fileref="neditscreenshot.jpg" format="JPG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>The nedit program can provide line numbers
|
||||
<phrase>The <application>nedit</application> program can provide line numbers
|
||||
across the left side of the screen, handy for when
|
||||
<command>nsgmls</command> complains of errors</phrase>
|
||||
</textobject>
|
||||
|
@ -262,7 +264,7 @@ XML file instead of an SGML file -->
|
|||
|
||||
<section id="usingnedit">
|
||||
<title>Using nedit</title>
|
||||
<para>When you open your DocBook file nedit should already
|
||||
<para>When you open your DocBook file, <application>nedit</application> should already
|
||||
have syntax highlighting enabled. If it does not you can
|
||||
turn it on explicitly using:
|
||||
<menuchoice>
|
||||
|
@ -398,17 +400,17 @@ turn it on explicitly using:
|
|||
This is a commercial application which is currently
|
||||
available for free (with an optional user registration).
|
||||
It is written in Java, allowing it to run on any platform
|
||||
that has a JVM (that is, works in both
|
||||
that has a Java Virtual Machine (that is, works in both
|
||||
Windows and Linux).
|
||||
</para>
|
||||
<para>
|
||||
On the plus sides of XMLEditor is the left side of the
|
||||
On the plus sides of <application>XMLEditor</application> is the left side of the
|
||||
screen shows the hierarchy of the document (starting with Book
|
||||
and so on). Selecting an item in the list brings you to that
|
||||
part of the document so you can edit it. The right part of the
|
||||
screen shows the text without any markup or tags being shown.
|
||||
If you have external files as ELEMENTS (as the LDP Author Guide
|
||||
does), XMLEditor will follow the links and load the files, so
|
||||
does), <application>XMLEditor</application> will follow the links and load the files, so
|
||||
you always work on the entire work. On the minus side of this,
|
||||
you will get errors if a file is missing.
|
||||
</para>
|
||||
|
@ -428,7 +430,7 @@ turn it on explicitly using:
|
|||
</para>
|
||||
|
||||
<blockquote><para>
|
||||
I am a big fan of XMLMind's XXE editor and XFC FO converter.
|
||||
I am a big fan of XMLMind's <application>XXE</application> editor and <application>XFC</application> FO converter.
|
||||
It is <quote>free as in beer,</quote> but not necessarily
|
||||
<quote>free as in speech.</quote> Very liberal license for personal use
|
||||
however. It's Java-based so it works on all sorts of OS's.
|
||||
|
|
Loading…
Reference in New Issue