Wiki Export, Discontinuous Numbering... (was: small update)

[Alexandre Enkerli]

Tim Pritlove said:
> I would be most interested in a flexible way to exchange outlines with 
> Wiki pages.
That's a really good one!! Of course, WikiPages are really easy to 
edit, but using OO to move stuff around would really help.

> or using the "#" character creating a numbered list
I think this is an important feature. Most editing systems that allow 
for outline hierarchies (say, Word, LaTeX, Wiki) have a clear 
difference between numbered and unnumbered lists. OO2 does too, 
internally, but it needs to be available in exported files too. That's 
one reason why the LaTeX export should allow for enumerate as well as 
itemize.
Of course, outlines in OO2 are set up as continuous lists. If I a 
single OOutline file looks more or less like a single list in Word, 
LaTeX, or Wiki. But as you all know, we do a lot more with our OO 
documents. So there could/should be a way in OO3 to specify numbering 
preferences for any item of a single level, and these preferences 
should carry over to exported files.
IOW, I should be able to have this in a single OO file:

Unnumbered first level
	Unnumbered second level
	Unnumbered second level
1. Numbered first level
1.1. Numbered second level
1.2. Numbered second level
2. Numbered first level
Unnumbered first level
	Unnumbered second level
		Unnumbered third level
1. Numbered first level
2. Numbered first level
3. Numbered first level

And have it export to:
*Unnumbered first level
**Unnumbered second level
**Unnumbered second level
#Numbered first level
##Numbered second level
##Numbered second level
#Numbered first level
*Unnumbered first level
**Unnumbered second level
***Unnumbered third level
#Numbered first level
#Numbered first level
#Numbered first level

With the equivalent in LaTeX, etc.

My solution for LaTeX so far has been to have a column with a choice of 
"description," "itemize," or "enumerate" that the XSL uses to build 
LaTeX lists. It's not robust at all and requires some manual 
post-processing, but it's a *great* help.

Thanks!