On 2016-09-07, Scott Kostyshak wrote:
> [-- Type: text/plain, Encoding: quoted-printable --]
> On Tue, Sep 06, 2016 at 03:56:08PM +, Guenter Milde wrote:
>> Dear LyX developers,
>> the ukrainean splash has preamble code loading russian babel
>> in the preamble.
...
On Tue, Sep 06, 2016 at 03:56:08PM +, Guenter Milde wrote:
> Dear LyX developers,
>
> the ukrainean splash has preamble code loading russian babel
> in the preamble.
Good find.
> Is this intended? Why?
>
> Can we remove the LaTeX preamble code?
>
> effects: U
Dear LyX developers,
the ukrainean splash has preamble code loading russian babel
in the preamble.
Is this intended? Why?
Can we remove the LaTeX preamble code?
effects: Ukrainean instead of Russian date, different hyphenation.
This also fixes some ctests tests:
The following tests fail to
Le 15/07/2016 à 17:54, Richard Heck a écrit :
On 07/15/2016 12:51 PM, Guillaume Munch wrote:
commit 10f6eb2e7eeffc757b7f54059524441e90008240
Author: Guillaume Munch
Date: Fri Jul 15 17:45:47 2016 +0100
LaTeX highlighter: make at a letter in the user preamble
Syntax highlighting now
ter: make at a letter in the user preamble
> >
> > Syntax highlighting now provides the appropriate cue that the user
> > preamble is
> > inside \makeatletter…\makeatother.
How can we see it?
I see the command \makeatletter, but the font above it is the same as bel
On 07/15/2016 12:51 PM, Guillaume Munch wrote:
> commit 10f6eb2e7eeffc757b7f54059524441e90008240
> Author: Guillaume Munch
> Date: Fri Jul 15 17:45:47 2016 +0100
>
> LaTeX highlighter: make at a letter in the user preamble
>
> Syntax highlighting now provide
On 06/07/2016 04:38 PM, Georg Baum wrote:
> Richard Heck wrote:
>
>> diff --git a/lib/templates/koma-letter2.lyx
>> b/lib/templates/koma-letter2.lyx index 43cbdb0..7251ff3 100644
>> --- a/lib/templates/koma-letter2.lyx
>> +++ b/lib/templates/koma-letter2.lyx
>> @@ -1,5 +1,5 @@
>> #LyX 2.2 created
Richard Heck wrote:
> diff --git a/lib/templates/koma-letter2.lyx
> b/lib/templates/koma-letter2.lyx index 43cbdb0..7251ff3 100644
> --- a/lib/templates/koma-letter2.lyx
> +++ b/lib/templates/koma-letter2.lyx
> @@ -1,5 +1,5 @@
> #LyX 2.2 created this file. For more info see http://www.lyx.org/
>
Am 15.04.2016 um 11:06 schrieb Scott Kostyshak :
>
> On Fri, Apr 15, 2016 at 10:36:59AM +0200, Stephan Witt wrote:
>> Am 15.04.2016 um 09:51 schrieb Scott Kostyshak :
>>>
>>> On Thu, Apr 14, 2016 at 08:53:24PM +0200, Stephan Witt wrote:
Am 14.04.2016 um 20:16 schrieb Guillaume Munch :
>
On Fri, Apr 15, 2016 at 10:36:59AM +0200, Stephan Witt wrote:
> Am 15.04.2016 um 09:51 schrieb Scott Kostyshak :
> >
> > On Thu, Apr 14, 2016 at 08:53:24PM +0200, Stephan Witt wrote:
> >> Am 14.04.2016 um 20:16 schrieb Guillaume Munch :
> >>>
> >>> Le 14/04/2016 19:05, Stephan Witt a écrit :
> >>
s of
hardcoding, if I understand correctly. Why is it only needed here?
Scott
On windows there has been a noticeable reduction in font size in the
preamble window. In the attached file, the one on the left is 2.1.4, the
one on the right rc1.
Andrew
---
This email has been checked for viruses by
On Thu, Apr 14, 2016 at 08:53:24PM +0200, Stephan Witt wrote:
> Am 14.04.2016 um 20:16 schrieb Guillaume Munch :
> >
> > Le 14/04/2016 19:05, Stephan Witt a écrit :
> >>
> >> Yes, it’s attached. Thanks for testing.
> >>
> >
> >
> > Works well on Linux+qt{4,5}.
> >
> > Two remarks:
> >
> > *
Le 14/04/2016 19:53, Stephan Witt a écrit :
Am 14.04.2016 um 20:16 schrieb Guillaume Munch :
Le 14/04/2016 19:05, Stephan Witt a écrit :
Yes, it’s attached. Thanks for testing.
Works well on Linux+qt{4,5}.
Two remarks:
* isFixedPitch() would be in an anonymous namespace by what I know o
Am 14.04.2016 um 20:16 schrieb Guillaume Munch :
>
> Le 14/04/2016 19:05, Stephan Witt a écrit :
>>
>> Yes, it’s attached. Thanks for testing.
>>
>
>
> Works well on Linux+qt{4,5}.
>
> Two remarks:
>
> * isFixedPitch() would be in an anonymous namespace by what I know of LyX's
> code style.
Le 14/04/2016 19:05, Stephan Witt a écrit :
Yes, it’s attached. Thanks for testing.
Works well on Linux+qt{4,5}.
Two remarks:
* isFixedPitch() would be in an anonymous namespace by what I know of
LyX's code style.
* In my patch I compute typewriterFontName() from typewriterSystemFont.
Wo
Am 14.04.2016 um 19:46 schrieb Guillaume Munch :
>
> Le 14/04/2016 18:41, Stephan Witt a écrit :
>> Am 14.04.2016 um 19:28 schrieb Guillaume Munch :
>>>
>>> Le 14/04/2016 18:10, Stephan Witt a écrit :
Am 14.04.2016 um 18:18 schrieb Joel Kulesza
:
>
> On Thu, Apr 14, 2016 at 10:
Le 14/04/2016 18:41, Stephan Witt a écrit :
Am 14.04.2016 um 19:28 schrieb Guillaume Munch :
Le 14/04/2016 18:10, Stephan Witt a écrit :
Am 14.04.2016 um 18:18 schrieb Joel Kulesza
:
On Thu, Apr 14, 2016 at 10:24 AM, Guillaume Munch
wrote:
Can you please try the attached patch?
That patch
Am 14.04.2016 um 19:28 schrieb Guillaume Munch :
>
> Le 14/04/2016 18:10, Stephan Witt a écrit :
>> Am 14.04.2016 um 18:18 schrieb Joel Kulesza :
>>>
>>> On Thu, Apr 14, 2016 at 10:24 AM, Guillaume Munch
>>> wrote:
>>>
>>> Can you please try the attached patch?
>>>
>>> That patch seemed to wor
Le 14/04/2016 18:10, Stephan Witt a écrit :
Am 14.04.2016 um 18:18 schrieb Joel Kulesza :
On Thu, Apr 14, 2016 at 10:24 AM, Guillaume Munch
wrote:
Can you please try the attached patch?
That patch seemed to work to correct the issue in both places (see
attached). The font seems small (I'm no
Am 14.04.2016 um 18:18 schrieb Joel Kulesza :
>
> On Thu, Apr 14, 2016 at 10:24 AM, Guillaume Munch wrote:
>
> Can you please try the attached patch?
>
> That patch seemed to work to correct the issue in both places (see attached).
> The font seems small (I'm not sure if that's perception or r
please try it?
>From 959d6fc0a945f09fc383f86d915b2f29e5002117 Mon Sep 17 00:00:00 2001
From: Guillaume Munch
Date: Thu, 14 Apr 2016 15:22:26 +0100
Subject: [PATCH] Fix monospace fonts in the source panel and preamble on Mac
http://mid.gmane.org/caagogw97a-j9zxy6sdrj-g_-zewdz+fstkgudsso3udx3tp...@mail.gmail.com
---
src/front
What font
do you see on the source panel?
There is no apparent change; see attached.
Sorry for spam, I had an email misfire. See attached for both screenshots.
There is no apparent change. The preamble appears consistent with the
source pane. I would not have knowingly c
Le 14/04/2016 12:13, Joel Kulesza a écrit :
On Wed, Feb 17, 2016 at 10:39 PM, Scott Kostyshak mailto:skost...@lyx.org>> wrote:
On Wed, Feb 17, 2016 at 10:11:27PM -0500, Richard Heck wrote:
> Seems to me a change better for 2.2.0, if Scott is all right with it.
Yes go ahead. And thank
On Wed, Feb 17, 2016 at 10:39 PM, Scott Kostyshak wrote:
> On Wed, Feb 17, 2016 at 10:11:27PM -0500, Richard Heck wrote:
> > Seems to me a change better for 2.2.0, if Scott is all right with it.
> Yes go ahead. And thanks for the patch.
> Scott
>
Is this a feature that would have been included i
On Wed, Feb 17, 2016 at 10:11:27PM -0500, Richard Heck wrote:
> On 02/17/2016 09:09 PM, Guillaume Munch wrote:
> > Le 18/02/2016 01:58, Richard Heck a écrit :
> >> On 02/17/2016 05:11 PM, Pavel Sanda wrote:
> >>> Guillaume Munch wrote:
> The attached patch copies code from the source panel, so
On 02/17/2016 09:09 PM, Guillaume Munch wrote:
> Le 18/02/2016 01:58, Richard Heck a écrit :
>> On 02/17/2016 05:11 PM, Pavel Sanda wrote:
>>> Guillaume Munch wrote:
The attached patch copies code from the source panel, so it is safe.
>>> I don't know what is the current beta policy, if Scott
Le 18/02/2016 01:58, Richard Heck a écrit :
On 02/17/2016 05:11 PM, Pavel Sanda wrote:
Guillaume Munch wrote:
The attached patch copies code from the source panel, so it is safe.
I don't know what is the current beta policy, if Scott is fine with that it has
my +1.
Tested? If so, has my +1,
On 02/17/2016 05:11 PM, Pavel Sanda wrote:
> Guillaume Munch wrote:
>> The attached patch copies code from the source panel, so it is safe.
> I don't know what is the current beta policy, if Scott is fine with that it
> has my +1.
Tested? If so, has my +1, too. (No time myself right now.)
rh
Guillaume Munch wrote:
> The attached patch copies code from the source panel, so it is safe.
I don't know what is the current beta policy, if Scott is fine with that
it has my +1.
Pavel
On 2016-02-17, Guillaume Munch wrote:
> [-- Type: text/plain, Encoding: 8bit --]
> Le 17/02/2016 19:10, Pavel Sanda a écrit :
>> Joel Kulesza wrote:
>>> My suggestion is to change the default font of the Settings->Preamble text
>>> box to a fixed-width font b
Le 17/02/2016 19:10, Pavel Sanda a écrit :
Joel Kulesza wrote:
My suggestion is to change the default font of the Settings->Preamble text
box to a fixed-width font because the content is effectively code. This
change should improve readability for those that make extensive use of the
pream
Joel Kulesza wrote:
> My suggestion is to change the default font of the Settings->Preamble text
> box to a fixed-width font because the content is effectively code. This
> change should improve readability for those that make extensive use of the
> preamble.
>
> Going a
LyX Developers,
I recently submitted an enhancement request through the bug tracker and it
was suggested I post here to initiate discussion on it. The TRAC ticket
number is #9966 <http://www.lyx.org/trac/ticket/9966>.
My suggestion is to change the default font of the Settings->Prea
Am 07.12.2015 um 15:57 schrieb Guenter Milde:
Uwe, would you agree that we store non-TeX fonts in the documentation files
wherever Latin Modern OTF fonts fail (Greek, Russian, CJK, ...)?
Yes. Please go ahead.
After this change the doc files will be frozen to give the translators a
chance to
On 2015-12-06, Kornel Benko wrote:
> Am Sonntag, 6. Dezember 2015 um 05:25:35, schrieb Uwe Stöhr
>
>> Am 04.12.2015 um 09:58 schrieb Guenter Milde:
...
>> For the compilation with system fonts we should do nothing since we
>> cannot know the system status of the user. If someones desperately ne
Am Sonntag, 6. Dezember 2015 um 05:25:35, schrieb Uwe Stöhr
> Am 04.12.2015 um 09:58 schrieb Guenter Milde:
>
> >> If I understand correctly, you want all tests with
> >>doc/.*/.*systemF
> >> being ignored.
> >
> >> If that should be so, than OK.
> >> If not, please help the docs be in good c
Am 04.12.2015 um 09:58 schrieb Guenter Milde:
If I understand correctly, you want all tests with
doc/.*/.*systemF
being ignored.
If that should be so, than OK.
If not, please help the docs be in good compilable shape.
I see it a bit different:
* The main purpose of the manuals is u
On 2015-12-04, Kornel Benko wrote:
> Am Freitag, 4. Dezember 2015 um 15:46:34, schrieb Guenter Milde
>
>> > Not here. Exporting by hand fails. Same reason as for lualatex.
>> Try with the upstream version, please.
> What do you mean by 'upstream version'?
Just for the record: I meant the versi
Am Freitag, 4. Dezember 2015 um 17:54:47, schrieb Kornel Benko
> Am Freitag, 4. Dezember 2015 um 15:46:34, schrieb Guenter Milde
>
> > > Not here. Exporting by hand fails. Same reason as for lualatex.
> >
> > Try with the upstream version, please.
>
> What do you mean by 'upstream version'? I
Am Freitag, 4. Dezember 2015 um 15:46:34, schrieb Guenter Milde
> > Not here. Exporting by hand fails. Same reason as for lualatex.
>
> Try with the upstream version, please.
What do you mean by 'upstream version'? I almost always use the newest
lyx-master.
And my TL is also not that old.
>
759b371d1e8fa2ad56
>> >> Author: Uwe Stöhr
>> >> Date: Fri Dec 4 01:48:14 2015 +0100
>> >> Spanish Tutorial.lyx: preamble code proposed by Günther
>> ...
>> > After this change:
>> ...
>> > nothing compiles, not only systemF
&g
bda2b7c3a86a0ae7eb759b371d1e8fa2ad56
> >> Author: Uwe Stöhr
> >> Date: Fri Dec 4 01:48:14 2015 +0100
>
> >> Spanish Tutorial.lyx: preamble code proposed by Günther
> ...
> > After this change:
> ...
>
> > You see, nothing compiles, not o
2015 +0100
>> Spanish Tutorial.lyx: preamble code proposed by Günther
...
> After this change:
...
> You see, nothing compiles, not only systemF
>
> e.g. from error log
> LaTeX Error: Missing \begin{document}.
> See the LaTeX m
On 2015-12-04, Kornel Benko wrote:
> Am 4. Dezember 2015 um 01:48:21, schrieb Uwe Stöhr
>> commit 0311bda2b7c3a86a0ae7eb759b371d1e8fa2ad56
>> Author: Uwe Stöhr
>> Date: Fri Dec 4 01:48:14 2015 +0100
>> Spanish Tutorial.lyx: preamble code proposed by Günther
&
Am Freitag, 4. Dezember 2015 um 01:48:21, schrieb Uwe Stöhr
> commit 0311bda2b7c3a86a0ae7eb759b371d1e8fa2ad56
> Author: Uwe Stöhr
> Date: Fri Dec 4 01:48:14 2015 +0100
>
> Spanish Tutorial.lyx: preamble code proposed by Günther
>
> - please don't re
Am Freitag, 4. Dezember 2015 um 01:48:21, schrieb Uwe Stöhr
> commit 0311bda2b7c3a86a0ae7eb759b371d1e8fa2ad56
> Author: Uwe Stöhr
> Date: Fri Dec 4 01:48:14 2015 +0100
>
> Spanish Tutorial.lyx: preamble code proposed by Günther
>
> - please don't re
s for
> LaTeX this is one representation of the given "character entity".
I understood. However, I still think the preamble content should not be
changed whatsoever. If a user enters invalid content, inform him.
Jürgen
_not_ to use unicodesymbols replacements for the user
> >> preamble?
> >
> > I consider the preamble to be "literate", just like ERT is. Thus, I
> > think no auto-replacements should be performed.
No, I mean "literal" as in: pass to LaTeX as is.
Jürgen
On 2015-07-05, Jürgen Spitzmüller wrote:
> Am Sonntag 05 Juli 2015, 14:12:55 schrieb Georg Baum:
>> The attached patch fixes that and even simplifies the code. Does anybody
>> know of any reason _not_ to use unicodesymbols replacements for the user
>> preamble?
> I con
Le 06/07/2015 17:17, Richard Heck a écrit :
I'm slightly confused. Is the idea that this inset can go anywhere you
like in the document, but its contents end up in the premable? If not,
then why do we need insets to do this? Why not just have some sort of
paragraph layout that does this? of which
On 07/05/2015 10:46 AM, Scott Kostyshak wrote:
On Sun, Jul 5, 2015 at 10:35 AM, Guenter Milde wrote:
On 2015-07-05, Jean-Marc Lasgouttes wrote:
In the preamble, there is no way to make a "LyX-only" comment. :-(
If we implemented InPreamble for insets, then one could create an
ERT-
On Sun, Jul 5, 2015 at 10:35 AM, Guenter Milde wrote:
> On 2015-07-05, Jean-Marc Lasgouttes wrote:
>>>> In the preamble, there is no way to make a "LyX-only" comment. :-(
>
>> If we implemented InPreamble for insets, then one could create an
>> ERT-like i
he comment into a LyX-note.
>>> Fine.
>>> In the preamble, there is no way to make a "LyX-only" comment. :-(
> If we implemented InPreamble for insets, then one could create an
> ERT-like inset that goes in preamble.
This may be an idea...
> Actually, we could
Le 05/07/2015 14:12, Georg Baum a écrit :
Guenter Milde wrote:
I want a concise comment in the LyX file, in order to explain what the
code is about.
In the document, I have the option to change the comment into a LyX-note.
Fine.
In the preamble, there is no way to make a "LyX-only&quo
Am Sonntag 05 Juli 2015, 14:12:55 schrieb Georg Baum:
> The attached patch fixes that and even simplifies the code. Does anybody
> know of any reason _not_ to use unicodesymbols replacements for the user
> preamble?
I consider the preamble to be "literate", just like ERT i
Guenter Milde wrote:
> I want a concise comment in the LyX file, in order to explain what the
> code is about.
>
> In the document, I have the option to change the comment into a LyX-note.
> Fine.
>
> In the preamble, there is no way to make a "LyX-only"
t;> processed by TeX, because comments are not decoded at all.
> This does not matter. If the user enters a comment (remember that this is
> either in the preamble or in ERT) we must assume that he did that on purpose
> and wants the comment to be preserved. We should not silently throw
2015-06-29 13:26 GMT+02:00 Guenter Milde :
> Similarily, all text parts in a comment are uncritical if the file is
> processed by TeX, because comments are not decoded at all.
>
But LyX cannot convert this to the target encoding and thus fails. Silently
removing the glyphs without giving a warnin
cs can display this file correctly.
> With TeX, there is no problem, as the German text part is read using a
> different encoding.
Yes.
> Similarily, all text parts in a comment are uncritical if the file is
> processed by TeX, because comments are not decoded at all.
This does n
W (or some other unambiguous ASCII representation
of the to-be-tested letter Ș) in the LaTeX preamble of my LyX file to
be able to use LyX "unicodesymbols" export conversions.
In my view, LyX is overly restrictive here and the new feature stands in the
way.
Günter
PS: A glyph is a g
2015-06-26 16:44 GMT+02:00 Guenter Milde :
> Dear LyX developers,
>
> trying the testfile for the comma-accent feature, I came across an
> annoyance:
>
> With every compilation attempt, a pop up window tells me, that there
> are unencodable characters in the pream
Dear LyX developers,
trying the testfile for the comma-accent feature, I came across an annoyance:
With every compilation attempt, a pop up window tells me, that there
are unencodable characters in the preamble.
However, the "offending" characters are in a comment:
% Romani
2015-06-15 20:46 GMT+02:00 Georg Baum :
> Looks good. Ideally I'd prefer to unify the handling of uncodable symbols a
> bit more (currently we have several copies of similar code), but this does
> not seem to be easy, so I'd say put it in.
>
I'll do so. Unifiying is certainly a good idea (for aft
Jürgen Spitzmüller wrote:
> The attached patch checks for uncodable glyphs in the user preamble and
> issues a warning if such glyphs are found (like we do in many other
> situations).
>
> Comments?
Looks good. Ideally I'd prefer to unify the handling of uncodable symbols a
The attached patch checks for uncodable glyphs in the user preamble and
issues a warning if such glyphs are found (like we do in many other
situations).
Comments?
Jürgen
diff --git a/src/BufferParams.cpp b/src/BufferParams.cpp
index 269c74c..f42211b 100644
--- a/src/BufferParams.cpp
+++ b/src
Jean-Marc Lasgouttes wrote:
> Hi,
>
> Is there a reason why I should not commit this patch. Georg, Uwe, I
> think the question is directed to you.
>
> JMarc
The defaults in tex2lyx do not need to match the LyX defaults IMHO. They
were designed so that the .tex->.lyx->.tex roundtrip generates a
ter defaults for preamble settings
This patch matches the default values of the h_* variables of tex2lyx with the initial values in BufferParams. This is intended to reduce noise in lyx>tex>lyx roundtrip.
There is also some code to omit \spacing when it is default. With this, the only remaining
On Wed, Jun 01, 2011 at 02:32:10PM +0200, Michal wrote:
> On Wed, 1 Jun 2011 03:31:05 +0200
> Enrico Forestieri wrote:
>
> > [...]
> > I assume that this may happen if the "long" name stem has less then 8
> > chars. Indeed:
> >
> > $ cygpath -d 'a b.tex'
> > AB2E6D~1.TEX
> Also remember tha
On Wed, Jun 01, 2011 at 07:01:30PM +0200, Michal wrote:
> On Wed, 1 Jun 2011 03:17:53 +0200
> Enrico Forestieri wrote:
>
> > [...] I would like that you test the attached patch (to be applied on
> > top of the previous one) and report back whether it works for you.
> Also, before I forget: i
On Wed, Jun 01, 2011 at 02:31:06PM +0200, Michal wrote:
> Not knowing whether to apply only your second patch or to apply both
> of them, I tried both approaches. Both seems correct now (although with
> the last patch no longer see the point of invoking GetShortPathNameW),
The point is that i
On Wed, 1 Jun 2011 03:17:53 +0200
Enrico Forestieri wrote:
> [...] I would like that you test the attached patch (to be applied on
> top of the previous one) and report back whether it works for you.
Also, before I forget: is there any reason of not using the LATEX
variable instead of the har
On Wed, 1 Jun 2011 03:31:05 +0200
Enrico Forestieri wrote:
> [...]
> I assume that this may happen if the "long" name stem has less then 8
> chars. Indeed:
>
> $ cygpath -d 'a b.tex'
> AB2E6D~1.TEX
Also remember that %TEMP% can also contain any user-preferred path,
like 'C:\a b\c d\e f' ...
On Wed, 1 Jun 2011 03:17:53 +0200
Enrico Forestieri wrote:
> [...]
> I managed to actually find a file system that does not provide for
> short filenames and reproduced the problem you are reporting.
For reference (in case of any further problems), reproducing my
'conditions' is relatively ea
On Tue, May 31, 2011 at 02:23:28PM +0200, Michal wrote:
> From http://msdn.microsoft.com/en-us/library/aa364989%28v=vs.85%29.aspx
> "The short form can be longer than the specified path."
>
> (so using len(longname)+1 as the length of the output buffer could
> end badly)
I assume that th
On Mon, May 30, 2011 at 06:58:11PM +0200, Michal wrote:
> On Sat, 28 May 2011 18:12:13 +0200
> Michal wrote:
>
> > Recently I've reinstalled both MiKTeX and LyX from scratch
> > using official installers for both, and my documents are not
> > compilable anymore, instead I get the following messs
On Sat, 28 May 2011 18:12:13 +0200
Michal wrote:
> Recently I've reinstalled both MiKTeX and LyX from scratch
> using official installers for both, and my documents are not
> compilable anymore, instead I get the following messsage:
>
> ! LaTeX Error: File `preambles/common.sty' not found.
I have the following in most of my documents written in the
preamble:
\input{preambles/common.sty}
It has always worked for me, dating back to LyX 1.4.x, and up to LyX
2.0rc2. Recently I've reinstalled both MiKTeX and LyX from scratch
using official installers for both, a
LyX 1.6.9 has no such option. Maybe I'd better just wait for the
release of LyX 2.0's Windows installer.
On Tue, Apr 5, 2011 at 1:10 AM, venom00 wrote:
>> Whenever the preamble contains "usepackage{xeCJK}" or xunicode,
>> instant preview will stop working. LyX 1.6
> Whenever the preamble contains "usepackage{xeCJK}" or xunicode,
> instant preview will stop working. LyX 1.6.9 on Windows XP SP3,
> TeXlive/MikTeX both tested.
> It was not a problem before version 1.6.9.
Under LyX 2.0.0svn works fine with xeCJK and xunicode but y
> Whenever the preamble contains "usepackage{xeCJK}" or xunicode,
> instant preview will stop working. LyX 1.6.9 on Windows XP SP3,
> TeXlive/MikTeX both tested.
> It was not a problem before version 1.6.9.
I'll try it under LyX 2 and check differences between 1.6.9
Marc J. Driftmeyer wrote:
> Can you test against Luatex from TeXLive 2009?
No.
> Debian is still on
> TeXLlive 2009 and they will not implement tlmgr as it would require a
> custom design for Debian.
I'm afraid I don't think LuaTeX on TeXLive 2009 is mature enough for
production work. In any
stefano franchi wrote:
> Here it is. On my installation, View>Pdf(LuaTex) fails with:
>
> Undefined control sequence
>
> \ProcessOptions*
works for me. Must be a problem with your LuaTeX or luainputenc version. I
have latest TeXLive 2010, freshly updated via tlmgr.
Anyway, I'll add the option
On 02/12/2010 22:45, Richard Heck wrote:
On 12/01/2010 07:45 AM, Abdelrazak Younes wrote:
Why not simply add a preamble editor in the branches dialog? LyX will
then collect the preamble for each branches. I guess this would be a
format change but it strikes me as the correct solution
On 12/01/2010 07:45 AM, Abdelrazak Younes wrote:
Why not simply add a preamble editor in the branches dialog? LyX will
then collect the preamble for each branches. I guess this would be a
format change but it strikes me as the correct solution...
Kind of crowded already, but perhaps a combo
> Why not simply add a preamble editor in the branches dialog? LyX will
> then collect the preamble for each branches. I guess this would be a
> format change but it strikes me as the correct solution...
This is similar to my first 'solution', which I've sugges
he beta
phase.
This looks too confusing to me. We'd have insets, which could appear
anywhere in the document, whose sole purpose was to add things to the
preamble?
To me, this is not more confusing than to have a Paragraph adding
things to the preamble.
The preamble style looks to me like a hack
mple to add this support - even in the beta
>> phase.
> This looks too confusing to me. We'd have insets, which could appear
> anywhere in the document, whose sole purpose was to add things to the
> preamble?
To me, this is not more confusing than to have a Paragraph adding
ar
anywhere in the document,
whose sole purpose was to add things to the preamble? The preamble style
looks to me like a hack
anyway.
The original issue was branch-specific preamble code. A better way to
implement this, it seems to
me, would be to have LyX declare a condition for each branc
On 2010-11-29, Michal wrote:
>> > [...] After that, I think the only remaining thing is
>> > to change the look of it to be more like ERT (typewriter font,
>> > changing color to red, etc.)
>> This can all be done in a *.module file in your personal LYXDIR. See
>> the "Help>Customization" document
> > [...] After that, I think the only remaining thing is
> > to change the look of it to be more like ERT (typewriter font,
> > changing color to red, etc.)
>
> This can all be done in a *.module file in your personal LYXDIR. See
> the "Help>Customization" documentation.
That is exactly what
sume that each branch contains the same text, but in
different language. It seems natural, that the user would like to have a
'title' field in the PDF (metadata) translated according to the active
branch. The "Preamble" env would be both simple and elegant solution for
this and si
sion, if there is enough interest.
> Another thing that came to me today is that maybe just adding a
> simple option for an ERT inset to add the code to the preamble instead
> would be a simplier solution? Technically, the code in the preamble is
> also a 'TeX code'... a
On 11/28/2010 10:25 PM, Michal wrote:
I've fixed this, in the sense that you can now use "LaTeXType
paragraph". Try this:
[...]
Thank you for your help! I guess I'll have to wait until the next
beta comes out then. After that, I think the only remaining thing is to
change the look of it to
upport this 'mini-module' in LyX?
I mean, to include it in sources and to treat any misbehavior of LyX
wrt it as a bug? I assure you, I'd be the first one to notice anything
like that :)
Another thing that came to me today is that maybe just adding a
simple option for an E
On 11/28/2010 01:21 AM, Michal Skrzypek wrote:
I think this may be quite easy to do already, though it is a bit of a
hack. LyX 2.0's layouts have an "InPreamble" tag, intended primarily
for use with document classes that want, say, \title to be in the
preamble. It should be possi
> I think this may be quite easy to do already, though it is a bit of a
> hack. LyX 2.0's layouts have an "InPreamble" tag, intended primarily
> for use with document classes that want, say, \title to be in the
> preamble. It should be possible to create a "Preamble
now I have some idea which, as I suppose, would be far
easier to implement.
The idea is to use the "preamble inset", which will look just like
the ERT, but instead of inserting the TeX code inside the document, it
will append this code to the end of the preamble (preferably with a
new
would be far
easier to implement.
The idea is to use the "preamble inset", which will look just like
the ERT, but instead of inserting the TeX code inside the document, it
will append this code to the end of the preamble (preferably with a
newline at the end). That way the goal of mul
> As trivial as the attached?
Yes, I think so.
> rh
rgheck wrote:
> >>> change these params in the document dialog from within each child.
> >>>
> >>>
> >
> > I would prefer that too.
> >
> >
>
> I think I'm confused about what's meant by "input" and "output".
I mean the LyX workarea. If you select spaced paragraphs in the master and
101 - 200 of 520 matches
Mail list logo
