T <T@invalid.invalid> writes:
I have been using Kompozer to edit html pages. It is a bit awkward
and buggy. I am going to be doing a lot more editing in the future.
Does anyone have a favorite html editor? A better Kompozer?
As already suggested, it doesn't actually make much sense to use
a "visual" ("WYSIWYG") editor to edit decidedly /non/-visual
medium, such as HTML.
This is contrary to, say, W3C-standard SVG,
or ISO-standard PDF, which /are/ visual, and which it /does/ make
sense to author "visually" (such as with Inkscape, SVG-edit,
Scribus, or many other such tools.)
Marko Rauhamaa <marko@pacujo.net> writes:
Ivan Shmakov <ivan@siamics.net>:
As already suggested, it doesn't actually make much sense to use a
"visual" ("WYSIWYG") editor to edit decidedly /non/-visual medium,
such as HTML.
Or such as plain text.
HTML is just one kind of markup language. But apart from Usenet
postings, there is barely any text that doesn't require markup.
In fact, even Usenet postings employ markup. GNUS displays
*emphasized* words in boldface
and turns :-) into a happy face image.
This is contrary to, say, W3C-standard SVG, or ISO-standard PDF,
which /are/ visual, and which it /does/ make sense to author
"visually" (such as with Inkscape, SVG-edit, Scribus, or many other
such tools.)
I wonder. You need the markup/metainfo to edit any of those formats meaningfully.
Even Gimp prefers to store images in the XCF format to preserve some
of the needed metainformation.
Marko Rauhamaa <marko@pacujo.net> writes:
Ivan Shmakov <ivan@siamics.net>:
Marko Rauhamaa <marko@pacujo.net> writes:
Even Gimp prefers to store images in the XCF format to preserve
some of the needed metainformation.
AIUI, Gimp uses XCF mainly for its losslessness and the support for
multiple layers. (And their respective metadata, right.)
Layers *are* metadata. IOW, you can't derive layers from the visual
output.
So even Gimp prefers not to be fully WYSIWYG.
Even Gimp prefers to store images in the XCF format to preserve someMarko Rauhamaa <marko@pacujo.net> writes:
of the needed metainformation.
AIUI, Gimp uses XCF mainly for its losslessness and the support
for multiple layers. (And their respective metadata, right.)
T <T@invalid.invalid> writes:
I have been using Kompozer to edit html pages. It is a bit awkward
and buggy. I am going to be doing a lot more editing in the future.
Does anyone have a favorite html editor? A better Kompozer?
As already suggested, it doesn't actually make much sense to use
a "visual" ("WYSIWYG") editor to edit decidedly /non/-visual
medium, such as HTML.
Ivan Shmakov <ivan@siamics.net>:for
Even Gimp prefers to store images in the XCF format to preserve someMarko Rauhamaa <marko@pacujo.net> writes:
of the needed metainformation.
AIUI, Gimp uses XCF mainly for its losslessness and the support
multiple layers. (And their respective metadata, right.)
Layers *are* metadata. IOW, you can't derive layers from the visual
output. So even Gimp prefers not to be fully WYSIWYG.
Marko
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 285 |
Nodes: | 16 (2 / 14) |
Uptime: | 77:58:42 |
Calls: | 6,489 |
Files: | 12,096 |
Messages: | 5,276,459 |