> > > documentation language, mdoc(7), at all, neither for input nor for
> > > output, already makes me raise an eyebrow or two
> Vim has many useful HTML plugins (or write your own)
yes ... but why should i bother with an uggly distracting format when
i can have a format that is close visually to the idea i have in mind
(a list). also i made other points that aren't adressed by vim plugins.
> The above list require two keystrokes and a number of list items wanted
> in one plugin I have barely started to use.
yet another plugin to install, maintain and learn when i can rely on
external commands i can use in other contexts;
> A print CSS file can do a tremendous amount of formatting useful for
> printed documents.
what if you want to use music cheets, chemical structures, good looking
math formula or other material. latex comes with tikz, beamer, qtree,
all those things that makes good looking printed documents much easier
to produce ...
html is when i need interactivity or animation but it's always a
painful process to me. but the point of using markdown remains:
* brian
* ken
* doug
is easier to write, read and edit than
\begin{itemize}
\tightlist
\item
brian
\item
ken
\item
doug
\end{itemize}
or
<ul>
<li>brian</li>
<li>ken</li>
<li>doug</li>
</ul>
> I detest Libreoffice. I have never yet gotten it to do anything I
> needed.
so do i: i was interested by arguments against markdown.
> But to each their own. Overall, this thread has been very enlightening
> for me. I do need to learn some other methods. TeX and LaTeX keep coming
> up everywhere I look.
i have to admit i started using both html and latex at the same time and
prefered html at the begining. but with time, latex is much more
rewarding when it comes to printed docs.
the only format that made me really unhappy for the moment is troff but
i still hope i'll have fun with it at some point.
regards
marc
