On Thu, Sep 07, 2000 at 04:24:21PM +0200, Lars Gullik Bjønnes wrote:
> Jose Abilio Oliveira Matos <[EMAIL PROTECTED]> writes:
>
>
> | I understand that every format should have a tag, what I find is that
> | the file extension is too restrictive. Why not to associate with every format
> | a label and an extension? That solves this case and future cases.
> |
> | Format |Label |extension
> | ----------------+---------------+----------
> | latex |tex |tex
> | linuxdoc |linuxdoc |sgml
> | docbook |docbook |sgml
> | website |website |xml
>
> website?
That is a dtd derived from docbook. It was created by Norman Walsh
www.nwalsh.com and he uses it in is site.
With a simple extension to lyx, needed to deal with the different
docbook versions available (3.0;3.1;3.1.1;4.0;4.0.1;4.1;4.1.1). This
extension only outputs a different header to each version of the doctype.
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook V3.1//EN"> is hardcoded for the
moment.
During the last 4 mounths I have used this combination with success to
build my web site, using lyx. There is some ERT but I have beeen reducing
it...
> I also don't see how a label solve anything
> (were is this label supposed to be put?)
The same as it is know for buffer extension:
string const Exporter::BufferExtension(Buffer const * buffer)
{
if (buffer->isLinuxDoc())
return "sgml";
else
return "tex";
}
> Espesially since it would be nice to have export and import use the
> same terminoloigy and framework...
I agree. But where does this label disallows that?
The tag is only a string associated to each document type (latex,
linuxdoc, docbook, ...)
> Lgb
>
--
José
