Jean-Marc Lasgouttes wrote:

> The patch looks good for 1.4. One thing I do not like is
> 
>  \Format docbook    sgml    DocBook                B  ""      "%%"
>  \Format docbook-xml xml   "Docbook (XML)"         "" ""      "%%"
>  \Format literate   nw      NoWeb                  N  ""      "%%"
> -\Format latex      tex     LaTeX                  L  ""      "%%"
> +\Format latex      tex    "TeX (latex)"           l  ""      "%%"
>  \Format linuxdoc   sgml    LinuxDoc               x  ""      "%%"
> +\Format pdflatex   tex    "TeX (pdflatex)"        "" ""      "%%"
>  \Format text       txt    "Plain text"            a  ""      "%%"
>  \Format textparagraph txt "Plain text (paragraphs)"    "" "" "%%"''' ])
> 
> I think we should not confuse people by use TeX instead of LaTeX. What
> about names like
>   LaTeX
>   LaTeX (for pdflatex)
> or
>   LaTeX (plain)
>   LaTeX (pdflatex)

I would prefer the latter. I'll first change this in trunk an then put the
combined patch in 1.4

> There is also a bug about the fact that the format names cannot be
> translated. Would you have an idea on the subject? Maybe gettext can
> find translatable strings in python files...

Yes: http://docs.python.org/lib/module-gettext.html (although I did not use
it, but I am sure it could be made to work).

> Finally, another thought for later: instead of adding hardcoded output
> formats like we do, wouldn't it be better to add converters LyX->foo
> and mark them 'internal'? I think it would remove hardcoding in the
> export code. And it would probably allow to add external lyx->bar
> converters that work on the .lyx file.

Why would you make "internal" a property of the converter? I proposed a
patch some days ago that introduces a "noexport" flag for formats. IMHO the
decision whether a format should be listed as exportable or not depends on
the format, not on the used converters.
I don't understand how converters that work on the .lyx file could be
affected. Could you explain, please?


Georg

Reply via email to