Am Donnerstag, den 16.02.2017, 16:19 +0100 schrieb Kornel Benko:
> > I'd probably use \providecommand. But you'd need to check whether
> the
> > output is identical (see below). And alternative is using \def or
> > \@ifundefined{strong}{\newcommand...}{\renewcommand...}
>
> OK. Any solution is
Am Donnerstag, den 16.02.2017, 17:06 +0100 schrieb Kornel Benko:
> Isn't that the meaning of 'solution'?
You have a point.
Jürgen
signature.asc
Description: This is a digitally signed message part
Am Donnerstag, 16. Februar 2017 um 16:47:43, schrieb Jürgen Spitzmüller
> Am Donnerstag, den 16.02.2017, 16:19 +0100 schrieb Kornel Benko:
> > OK. Any solution is better than what we have now.
>
> No, not any. Only one that does not break other documents. What we have
> now only
Am Donnerstag, den 16.02.2017, 16:19 +0100 schrieb Kornel Benko:
> OK. Any solution is better than what we have now.
No, not any. Only one that does not break other documents. What we have
now only breaks with Non-TeX fonts, and only with a very recent
fontspec.
Jürgen
signature.asc
Am Donnerstag, 16. Februar 2017 um 15:08:24, schrieb Jürgen Spitzmüller
> Am Donnerstag, den 16.02.2017, 11:15 +0100 schrieb Kornel Benko:
> > Hi,
> > the attached patch fixes it for me.
>
> This will fail for all cases were strong is not defined.
>
> I'd probably use
Am Donnerstag, den 16.02.2017, 11:15 +0100 schrieb Kornel Benko:
> Hi,
> the attached patch fixes it for me.
This will fail for all cases were strong is not defined.
I'd probably use \providecommand. But you'd need to check whether the
output is identical (see below). And alternative is using
Hi,
the attached patch fixes it for me. 16 testcases are affected.
E.g. export/doc/Additional_pdf4_systemF:
Desc: LaTeX Error: Command \strong already defined.
Text: \newcommand{\strong}[1]{\textbf{#1}}
Your command was ignored.
Type Ito replace it with