Hi Devin,
I don't think there is going to be an easy way to number paragraphs the
way you want. It's something that people often want to do and yet nobody
AFAIK has ever come up with a satisfactory way to do it that doesn't
mess up LaTeX for anything other than really simple documents.
As you've already noticed, sections/subsections/subsubsections can be
easily numbered. To avoid having to change the font sizes every time try
including the following in your latex preamble (layout->preamble):
\renewcommand\subsection{\@startsection{subsection}{2}{\z@}%
{-3.5ex\@plus -1ex \@minus -.2ex}%
{2.3ex \@plus .2ex}%
{\hskip0.25in\normalfont}}
\renewcommand\subsubsection{\@startsection{subsubsection}{3}{\z@}%
{-3.5ex\@plus -1ex \@minus -.2ex}%
{2.3ex \@plus .2ex}%
{\hskip0.5in\normalfont}}
The \hskipXin bits indent the paragraphs, you can change them if you
don't like that bit. So now all you have to do is work out how to get
LyX to automatically convert all your paragraphs into subsections and
subsubsections. I have no idea how you are going to do that but it can't
possibly be any harder than getting LaTeX to number your paragraphs!
James
--------------------------------------------
I've been trying to figure out a way in lyx to produce the following
paragraph numbering format for technical documents:
1 section title
1.1 paragraph
1.2 paragraph
1.2.1 subpara
1.2.1.1 subsubpara
1.2.2 subpara
1.3 paragraph
2 section title
2.1 paragraph
The only thing way so far that I've been able to do this is, after
writing the text, to switch the paragraphs from "standard" to "subsection"
"subsubsection", and so forth. However not only is this onerous, but
it also (in some cases) requires font size changes, boldface to normal
typeface changes, etc.
Does anyone have suggestions on automating this process? I'd like
to create a template or configuration such that other technical writers
could just use it rather than having to do all these changes for every
single paragraph.
I suspect somebody has done this in the past (in latex if not in lyx).
Pointers would be appreciated. I perused CTAN for a bit, but didn't
have luck in finding what I was after.
--
Devin Reade <[EMAIL PROTECTED]>
