On 2015-11-20, Kornel Benko wrote:
> Am 18. November 2015 um 18:56:59, schrieb Guenter Milde <mi...@users.sf.net>

>> Generally, I don't think it is a good idea to "massage" the documents
>> shipping with lyx in the test machinery until the tests pass.

>> * If the document can be made more robust (i.e. working with more than the
>>   default output format) without the changes standing in the way for its
>>   main purpose (documentation, templates, examples for LyX users), then this
>>   should be changes in the document itself.

> +1

>> * If the document has special needs (packages, ERT, preamble code ...)
>>   that make it uncompilable with some export formats, invert the test or
>>   ignore it - with appropriate comment. There remain enough files to
>>   test. 

> +1

>>   If some document in lib/... is important for testing a special
>>   feature/combination/... but fails for another reason, please don't 
>>   modify it in the test machinery, but instead convert it to a 
>>   *minimal working example* and put in a dedicated export test document
>>   folder. 

> Someone has to start ...

And we have to agree on a directory structure and naming.

>>   This is far more easy to handle for other developers than test
>>   passing/failing for reasons that cannot be reproduced when compiling the
>>   same documents "by hand"!

> If you compile "by hand", you already change the document. 

Currently, yes. But only for cases where I know what is to do.

> You set for instance "use non TeX font",

This is such a generic case that I think it does not merit separate documents.
(At least for now. With the proposed "auto" setting for useNonTeXFonts, this
would change.)

>  "use math for non tex fonts", 

I never changed this, nor do I know which tests would require this change.

> set probably also some valid serif,sans,mono font.

This is a case where now (i.e. since we can configure both, TeX and nonTeX
fonts) it is better to set the required font(s) in the document:

  * if it is not in the way - in the original lib/*.lyx that ships with LyX 
  
  * if the original should not contain this change: in a copy in test/*.lyx

> That said, +1

In this case, this should/could go to lib/doc/Development.lyx and then be
implemented (removing the specialcasing and "massaging" from the machinery).

Günter

Reply via email to