Am Dienstag, den 05.07.2016, 13:14 + schrieb JürgenSpitzmüller:
> FWIW I have a patch for covington.sty ready which fixes the issue
> properly,
> and I have contacted the former maintainers of the package, proposing
> to take
> over maintainership.
I have just submitted a new version of
2016-07-05 15:14 GMT+02:00 JürgenSpitzmüller:
> Scott Kostyshak lyx.org> writes:
> FWIW I have a patch for covington.sty ready which fixes the issue properly,
> and I have contacted the former maintainers of the package, proposing to
> take
> over maintainership.
>
Patch is attached, for the
Scott Kostyshak lyx.org> writes:
> Great, thanks for helping out with this. I think that many users will
> run into this issue so hopefully they can fix it.
FWIW I have a patch for covington.sty ready which fixes the issue properly,
and I have contacted the former maintainers of the package,
On Fri, Jul 01, 2016 at 08:12:17AM +0200, Michael Berger wrote:
>
>
> On 07/01/2016 02:03 AM, Scott Kostyshak wrote:
> > On Thu, Jun 30, 2016 at 09:40:45AM -0400, Richard Heck wrote:
> > > On 06/30/2016 04:14 AM, Michael Berger wrote:
> > > > Should I go on with that workaround (because this one
On 07/01/2016 02:03 AM, Scott Kostyshak wrote:
On Thu, Jun 30, 2016 at 09:40:45AM -0400, Richard Heck wrote:
On 06/30/2016 04:14 AM, Michael Berger wrote:
Should I go on with that workaround (because this one too is an already
deprecated class option) or is there anything else to be done?
On Thu, Jun 30, 2016 at 09:40:45AM -0400, Richard Heck wrote:
> On 06/30/2016 04:14 AM, Michael Berger wrote:
> > Should I go on with that workaround (because this one too is an already
> > deprecated class option) or is there anything else to be done?
>
> It'd be worth reporting the error. It
On 06/30/2016 04:14 AM, Michael Berger wrote:
On 06/30/2016 09:36 AM, Scott Kostyshak wrote:
On Thu, Jun 30, 2016 at 09:20:27AM +0200, Michael Berger wrote:
Hi Scott, Richard, thanks,
of course, I did read the complete error message several times - and
got
even more confused.
OK. A good
On 06/30/2016 10:14 AM, Michael Berger wrote:
On 06/30/2016 09:36 AM, Scott Kostyshak wrote:
On Thu, Jun 30, 2016 at 09:20:27AM +0200, Michael Berger wrote:
Hi Scott, Richard, thanks,
of course, I did read the complete error message several times - and
got
even more confused.
OK. A
On 06/30/2016 09:36 AM, Scott Kostyshak wrote:
On Thu, Jun 30, 2016 at 09:20:27AM +0200, Michael Berger wrote:
Hi Scott, Richard, thanks,
of course, I did read the complete error message several times - and got
even more confused.
OK. A good strategy is to read the error message and then at
On Thu, Jun 30, 2016 at 09:20:27AM +0200, Michael Berger wrote:
> Hi Scott, Richard, thanks,
> of course, I did read the complete error message several times - and got
> even more confused.
OK. A good strategy is to read the error message and then at the very
first part you get confused (this
On 06/30/2016 12:59 AM, Richard Heck wrote:
On 06/29/2016 06:14 PM, Scott Kostyshak wrote:
On Wed, Jun 29, 2016 at 02:23:43PM +0200, Michael Berger wrote:
Dear Lyx users,
texlive2016, GUI (manually installed as user)
Ly- some documents with glosses work in LyX as should while some
generate
On 06/29/2016 06:14 PM, Scott Kostyshak wrote:
On Wed, Jun 29, 2016 at 02:23:43PM +0200, Michael Berger wrote:
Dear Lyx users,
texlive2016, GUI (manually installed as user)
Ly
Hi Michael,
Thanks for sending a minimal example!
This is a case (I admit they are rare) where the error is
12 matches
Mail list logo
