On Fri, Apr 12, 2013 at 6:31 PM, José Matos wrote:
> On Wednesday 10 April 2013 22:05:09 Scott Kostyshak wrote:
> The patch attached fixes the first problem you describe the "DUMMY"
> references (pun intended). :-D
>
> I will try to chase and fix the others.
Hi José, here are some more errors fo
On Thu, Apr 25, 2013 at 10:18 AM, LyX Ticket Tracker wrote:
> #2757: bibtex errors not reported
> I wonder if this wasn't implemented because it doesn't fit exactly with
> the purpose of ErrorListUi because the BibTeX errors are not associated
> with lines in the LyX file. It seems like that wo
On Mon, Apr 8, 2013 at 12:35 AM, Scott Kostyshak wrote:
> On Mon, Feb 18, 2013 at 2:33 AM, Scott Kostyshak wrote:
>> On Sun, Feb 17, 2013 at 8:57 AM, Jürgen Spitzmüller wrote:
>>> Scott Kostyshak wrote:
listerrors.lyx
ps2pdf works well
pdflatex and luatex fail (lots of undefined c
On Sun, Apr 14, 2013 at 3:39 AM, Scott Kostyshak wrote:
> I get utf-8 and utf8x errors.
>
> Is there a fix for this while preserving export with pdflatex and latex?
Any ideas?
Scott
The AEA template has the following instructions:
Choose LaTeX font encoding to "None (no fontenc)" in menu
Document=>Settings=>Fonts
This gets rid of an error that I get if I do not do that
(<>)
but now I get the following error:
! LaTeX Error: Command \textquotedbl unavailable in encoding OT1.
On Sun, Apr 14, 2013 at 3:38 AM, Scott Kostyshak wrote:
> Exporting via ps2pdf works fine, but pdflatex and luatex fail. I think
> pdflatex fails because of converting the eps to pdf.
>
> I thought I had fixed a similar error before with the following:
>
> epstool --copy --bbox platypus.eps --outp
2013/4/16 Uwe Stöhr :
> The branch, master, has been updated.
>
> - Log -
>
> commit 458b3bad107a988db4c0f963dde4576a3ae337d9
> Author: Uwe Stöhr
> Date: Wed Apr 17 01:13:49 2013 +0200
>
> UserGuide.lyx: first step of revision
>
On Fri, May 17, 2013 at 10:24 AM, Jürgen Spitzmüller wrote:
> a.) the default is what the classes does (i.e., "always center content" is an
> opt-in, not an opt-out)
>
Yes.
> b.) this stuff is not physically hardcoded, but globally settable (for
> instance, as I have proposed, via \lyxtablesetti
On Sun, Apr 28, 2013 at 3:50 PM, Vincent van Ravesteijn wrote:
> The branch, master, has been updated.
>
> - Log -
>
> commit 361995459068a5e53b597f1195f7f29522714ec4
> Author: Vincent van Ravesteijn
> Date: Sun Apr 28 21:47:37 201
On Thu, May 16, 2013 at 11:00 PM, Vincent van Ravesteijn wrote:
> I'm afraid this will be too late for 2.1. This will probably light up some
> discussion, and it will take time to figure out what we're going to do
> exactly.
>
Agreed. I don't think there is anything near a consensus on whether or
Op 17-5-2013 10:28, Jürgen Spitzmüller schreef:
Vincent van Ravesteijn wrote:
Hmm.. A document setting that doesn't say anything about the document,
but just how LyX interacts with it.
Huh? What about font sizes, margins, line height and all this stuff?
Huh ? If I change the font size, the marg
Le mar. 14 mai 2013 18:35:56 CEST, Pavel Sanda a écrit :
Jean-Marc Lasgouttes wrote:
+In order to test your translation you need to obtain the LyX sources
+(from the SVN repository) and replace the existing .po with yours.
svn repository...
Well spotted, but this appears in many more files,
15/05/2013 01:05, Uwe Stöhr:
Am 06.05.2013 11:52, schrieb Jean-Marc Lasgouttes:
As in Milano, I applied your patches and it works now for \mbox, but now
minipages and parboxes are broken:
- insert a new box via the toolbar button
- open its box dialog and delete there the width number and press
Vincent van Ravesteijn wrote:
> Hmm.. A document setting that doesn't say anything about the document,
> but just how LyX interacts with it.
Huh? What about font sizes, margins, line height and all this stuff?
> That doesn't feel right. I think the
> change tracking setting is already annoying e
On Fri, May 17, 2013 at 3:42 AM, Vincent van Ravesteijn wrote:
>> > A separate thing is that we might want to merge in such a change. That
>> > would
>> > cause the master branch to have much fewer commits (if you use
>> > --first-parent-only).
>>
>> OK, I would like to start doing this because it
Uwe Stöhr wrote:
> Dear colleagues,
>
> we often discussed in the past about the default paragraph alignment for new
> floats. We had the discussion in Milano as well because this is one of the
> most annoying things for many users. We voted to do something. The question
> is now how. Here is my p
> > A separate thing is that we might want to merge in such a change. That
> would
> > cause the master branch to have much fewer commits (if you use
> > --first-parent-only).
>
> OK, I would like to start doing this because it is the most
> informative of how the development happened. In addition
-- Forwarded message --
From: Vincent van Ravesteijn
Date: Fri, May 17, 2013 at 7:47 AM
Subject: Re: LyX convention for squash vs. merge/rebase?
To: Scott Kostyshak
On Fri, May 17, 2013 at 5:11 AM, Scott Kostyshak wrote:
> On Thu, May 16, 2013 at 8:34 PM, Cyrille Artho wrote
18 matches
Mail list logo
