Am Montag, 7. November 2016 um 15:47:28, schrieb Guenter Milde 
<mi...@users.sf.net>
> On 2016-11-07, Kornel Benko wrote:
> > Am Montag, 7. November 2016 um 15:10:09, schrieb Kornel Benko 
> > <kor...@lyx.org>
> >> Am Montag, 7. November 2016 um 13:44:17, schrieb Guenter Milde 
> >> <mi...@users.sf.net>
> 
> Dear Kornel,
> 
> ...
> 
> >> > I'd like an "expansion" of
> >> > export/latex/Unicode-characters/084-misc-symbols.lyx into
> >> > 
> >> >  export/export/latex/Unicode-characters/084-misc-symbols_pdf2
> >> >  export/export/latex/Unicode-characters/084-misc-symbols_pdf2_utf8
> >> >  export/export/latex/Unicode-characters/084-misc-symbols_pdf2_armscii
> >> >  export/export/latex/Unicode-characters/084-misc-symbols_pdf2_latin1
> >> >  ...
> >> >  export/export/latex/Unicode-characters/084-misc-symbols_pdf2_tis620-0
> >> >  export/export/latex/Unicode-characters/084-misc-symbols_pdf2_utf8-plain
> >> >  export/export/latex/Unicode-characters/084-misc-symbols_pdf2_ascii
> >> >  
> >> > Would this be feasible?
> 
> >> Yes, it is. New parameter for useSystemFonts.pl. But I'd prefer to use
> >> it only for files in a special directory.
> 
> So do I: please limit the "expansion" with *all* encodings to the
> directory "autotests/export/latex/Unicode-characters" (maybe renaming it
> to "autotests/export/latex/test_lib_unicodesymbols/" first). With the
> "inputenc expansion", I would remove the "*utf8.lyx" samples, of course.
> 
> (OTOH, I still suggest testing "utf8" and "ascii" input encodings with all
> samples and pdf2.)
> 
> >> Do you want to test also combinations like  084-misc-symbols_pdf4_utf8 ?
> > Ouch .. I see you already want it ...
> >> Looks like overkill ...
> 
> One export route suffices. This is why I set the "default output format"
> to pdf2 in the sample files.

Do you(we) want all encoding tests for 084-misc-symbols_pdf2* be contained in 
one test, or
do you prefer them be separate?

> Thanks,
> 
> Günter 

        Kornel

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to