Am Freitag, 11. Dezember 2015 um 21:51:41, schrieb Guenter Milde <mi...@users.sf.net> > On 2015-12-11, Kornel Benko wrote: > > Am Freitag, 11. Dezember 2015 um 12:53:41, schrieb Uwe Stöhr > > <uwesto...@web.de> > > > It is not, that I am criticizing that the docs are designed for > > pdflatex. (Which itself is not valid for japanese docs). > > It is only the removal from the test suite. > > Problem: the "right thing" (marking the intended output format in the > files) had the wrong side-effect of no longer testing other formats: > > * up to now, the manuals were designed for pdflatex (except for the > japanese), but this was not documented (besides some posts to the > devel-list). > > The tests with other formats highlighted this omission and let to > improvement of the documentation: the intended "design format" is now > indicated in the documents »the LyX way«" -- specifying the default > output format. > > This does not prevent export to other formats, it only controls the > binding of the "view" and "update" buttons and menu entries. > > * the test suite seems to create tests > > - for a set of output formats, if there is no explicit default output > format of the to-be-tested document > > - only for the default output format, if it is set. >
Yes, and this was done by intend. We wanted to have default output format only
if
really necessary. And in this case we 'knew', that other formats are not
working.
Now, all docs are marked this way.
>
> >> To test other things like LuaTeX etc. please feel free to create a new
> >> folder, copy the doc files there and modify and test them as you are. If
> >> you find there bugs we can backport changes to the docs folder after the
> >> possible bugs in LyX have been fixed.
>
> > I know.
> > But if a new or changed document in doc gets some error, we would never
> > find out, because we do not test.
>
> This is why I propose to keep the "dual use". Test the documentation also
> with non-default output formats. Try to make it robust (compilable with
> other formats) but only with consent from the documentation maintainer
> (especially when a new release is imminent).
We have to distinguish somehow if some formats are not allowed (because for
example
the file is written specifically for creating html) or only not desired.
I don’t know how.
The best (for the test suite) would be a format change, describing available
output formats.
ATM, we have to guess.
> Thanks,
>
> Günter
Kornel
signature.asc
Description: This is a digitally signed message part.
