XML editors - Revision history

Buggy at 14:25, 29 December 2020

2020-12-29T14:25:27Z

Unhammer at 07:22, 4 September 2017

2017-09-04T07:22:25Z

Unhammer: /* See also */

2016-12-23T11:34:52Z

Unhammer at 09:31, 12 May 2015

2015-05-12T09:31:36Z

Unhammer at 08:46, 12 May 2015

2015-05-12T08:46:37Z

Unhammer at 08:42, 12 May 2015

2015-05-12T08:42:39Z

Unhammer at 08:42, 12 May 2015

2015-05-12T08:42:27Z

Unhammer at 08:41, 12 May 2015

2015-05-12T08:41:48Z

Unhammer at 12:19, 11 May 2015

2015-05-11T12:19:06Z

Unhammer at 10:43, 12 February 2015

2015-02-12T10:43:18Z

@@ Line 32: / Line 32: @@
 * [[Vim]] – a lightweight, modal editor
 ** Does syntax highlighting for XML out of the box if you have "syntax on" in your ~/.vimrc
-** See [[Vim]] for more infor
+** See [[Vim]] for more information
 * [[Emacs]] – a self-documenting, extensible lisp machine

@@ Line 11: / Line 11: @@
 ** Does real XML validation with no setup required
 ** Uses libxml2, so try to keep your validation errors below line 65535 :-)
-* [https://en.wikipedia.org/wiki/Gedit Gedit] – a simple GUI code editor (written in C/Python)
+* [[Gedit]] – a simple GUI code editor (written in C/Python)
 ** <code>sudo apt-get install gedit gedit-developer-plugins</code>
 ** There's an XML validation plugin at https://launchpad.net/gedit-xmltools but it only works with gedit2

@@ Line 60: / Line 60: @@
 * [[Easy dictionary maintenance]] – GUI for editing dictionaries
 * [[Dixtools: Enhance]] – interactive tool to add new words to a dictionary (asks you for a word that inflects the same, finds the paradigm for you)
+* [[Text Editors Compatible With Different Scripts]] about bidi/RTL
 [[Category:Writing dictionaries]]
 [[Category:Tools]]

@@ Line 4: / Line 4: @@
 * '''well-formedness''' errors are things like missing a " or end-tag; most editors are able to catch these or at least show you that you forgot a " by syntax highlighting;
 * '''validation''' errors require some knowledge of what a .dix or .t1x file should look like, and may tell you things like that "you've referred to a pardef that hasn't been defined". Not all editors are able to do full validation.
-** Of the editors that use libxml2/xmllint for validation, there's a [https://bugzilla.gnome.org/show_bug.cgi?id=325533 bug in libxml2] for files >65535 lines long. Programs like apertium-validate-dictionary are also affected.
+** Of the editors that use libxml2/xmllint for validation, there's a [https://sourceforge.net/p/apertium/tickets/69/ bug in libxml2] for files >65535 lines long. Programs like apertium-validate-dictionary are also affected.

@@ Line 4: / Line 4: @@
 * '''well-formedness''' errors are things like missing a " or end-tag; most editors are able to catch these or at least show you that you forgot a " by syntax highlighting;
 * '''validation''' errors require some knowledge of what a .dix or .t1x file should look like, and may tell you things like that "you've referred to a pardef that hasn't been defined". Not all editors are able to do full validation.
-** Of the editors that use xmllint for validation, there's a [https://bugzilla.gnome.org/show_bug.cgi?id=325533 bug in xmllint] for files >65535 lines long. Note: apertium-validate-dictionary is also affected.
+** Of the editors that use libxml2/xmllint for validation, there's a [https://bugzilla.gnome.org/show_bug.cgi?id=325533 bug in libxml2] for files >65535 lines long. Programs like apertium-validate-dictionary are also affected.
@@ Line 10: / Line 10: @@
 * [[Apertium-viewer]] – an apertium-specific GUI for testing sentences throughout the pipeline, and editing source files (written in Java)
 ** Does real XML validation with no setup required
-** Uses xmllint, so try to keep your validation errors below line 65535 :-)
+** Uses libxml2, so try to keep your validation errors below line 65535 :-)
 * [https://en.wikipedia.org/wiki/Gedit Gedit] – a simple GUI code editor (written in C/Python)
 ** <code>sudo apt-get install gedit gedit-developer-plugins</code>
@@ Line 19: / Line 19: @@
 ** XML Copy Editor will check well-formedness (that you have your brackets and quotes in place) out of the box
 ** To get validation you may have to click XML→Associate→System DTD and select dix.dtd from lttoolbox (typically in /usr/local/share/lttoolbox or /usr/share/lttoolbox). This will insert a DOCTYPE line in your xml, but that's fine.
+** Uses libxml2, so try to keep your validation errors below line 65535 :-)
-** There seems to be a bug that gives wrong line numbers on some validation errors.
 * [https://en.wikipedia.org/wiki/JEdit Jedit] – a "programmers" GUI editor (written in Java) with frillions of options and menus
 ** <code>sudo apt-get install jedit</code>
 ** Install the plugin named "XML" to get validation (you can put <nowiki><code><!DOCTYPE dictionary SYSTEM "/usr/share/lttoolbox/dix.dtd"></code></nowiki> before the &lt;document&gt; element to make it use the dtd automatically).
-** There seems to be a bug that gives wrong line numbers on some validation errors, as with XML Copy Editor
+** There seems to be a bug that gives wrong line numbers on some validation errors (don't know if this uses libxml2 or something else)
 * Kate – another "programmers" GUI editor (written in C++/Qt) from KDE