Re: Branch names with spaces

2011-10-14 Thread Jürgen Spitzmüller 
Dominik Waßenhoven wrote:
> Which is a shame. (c;

Says an Historian!

Jürgen

how to wrap the Title in classicthesis-preamble.sty

2011-10-14 Thread Gian Maria Niccolò Benucci 
Hi again,

I am using ClassicThesis style by Andrè Miede and I have a problem with
title length in the classicthesis-preamble.sty.
The title of my Thesis is a bit long and would be better to wrap it. How to
wrap the Title?
I tried with \\ or \endline but nothing...

Thank you to everyone,

Gian

Re: Fwd: Move from d:drive to c:drive

2011-10-14 Thread David L. Johnson 

On 10/14/2011 02:17 PM, Sølvi wrote:

ANYONE??

-- Forwarded message --
From: *Sølvi* mailto:s.n.mi...@gmail.com>>
Date: 2011/10/11
Subject: Move from d:drive to c:drive
To: lyx-users@lists.lyx.org 


Hi,

I'm currently using Windows XP with LyX v.2.0.0

I have a huge document, it's a master with several child documents 
included which then again have documents/figures etc inserted (it's 
like a christmas tree). I have been working on the d: drive on a pc 
but now I have to work on a pc that only have a c: drive and I 
probably have to move it all back to the pc with the d: drive later.


Is there any easy way to do this or do I have to "rebuild" the entire 
document? It's a big document with lots of files incorporated.



I'm sorry, but I don't really know how Windows file management works.  
Isn't there a way you can archive all of that into a file (.zip or 
.tar), starting from withing the d:drive so the archive is relative.  
Then, unarchive it in the c:drive and I would think that it should 
work.  Or. maybe you can set up a recursive copy command to copy it all 
over.  But I am shooting in the dark.


--

David L. Johnson

Let's be straight here.  If we find something we can't understand we
like to call it something you can't understand, or indeed even
pronounce.
-- Douglas Adams

Re: Move from d:drive to c:drive

2011-10-14 Thread Christopher Menzel 
On Oct 14, 2011, at 8:17 PM, Sølvi wrote:

> ANYONE??
> 
> -- Forwarded message --
> From: Sølvi 
> Date: 2011/10/11
> Subject: Move from d:drive to c:drive
> To: lyx-users@lists.lyx.org
> 
> Hi,
> 
> I'm currently using Windows XP with LyX v.2.0.0
> 
> I have a huge document, it's a master with several child documents included 
> which then again have documents/figures etc inserted (it's like a christmas 
> tree). I have been working on the d: drive on a pc but now I have to work on 
> a pc that only have a c: drive and I probably have to move it all back to the 
> pc with the d: drive later.
> 
> Is there any easy way to do this or do I have to "rebuild" the entire 
> document? It's a big document with lots of files incorporated. 


Are you saying that all of your \include statements use absolute paths of the 
form:

\include{c:\dir1\dir1\...\filename.tex} ?

I don't know much about windows but it seems to me that you could drop the 
drive letter in all of those statements and, as long as all the documents 
reside on the same drive, when you call your top-level file the \include 
statements will all default to the drive that file is on.

Chris Menzel

Re: Move from d:drive to c:drive

2011-10-14 Thread Stephan Witt 
Am 14.10.2011 um 20:17 schrieb Sølvi:

> ANYONE??

Did you read the message from Julien?

Stephan

> -- Forwarded message --
> From: Sølvi 
> Date: 2011/10/11
> Subject: Move from d:drive to c:drive
> To: lyx-users@lists.lyx.org
> 
> 
> Hi,
> 
> I'm currently using Windows XP with LyX v.2.0.0
> 
> I have a huge document, it's a master with several child documents included 
> which then again have documents/figures etc inserted (it's like a christmas 
> tree). I have been working on the d: drive on a pc but now I have to work on 
> a pc that only have a c: drive and I probably have to move it all back to the 
> pc with the d: drive later.
> 
> Is there any easy way to do this or do I have to "rebuild" the entire 
> document? It's a big document with lots of files incorporated.
> 
> Regards,
> Solvi
>

Re: Branch names with spaces

2011-10-14 Thread Dominik Waßenhoven 
Jürgen Spitzmüller wrote:

> Manveru wrote:
>>> This is now fixed in the development trunk and will be fixed in LyX
>>> 1.6.3 if I get green light for that.
>> 
>> I had the similar problem in 2.0.1 on Linux.
> 
> Of course I meant it will be fixed in 2.0.2. I cannot change the past, after 
> all.
> 
> Jürgen

Which is a shame. (c;

Dominik.-

Fwd: Move from d:drive to c:drive

2011-10-14 Thread Sølvi 
ANYONE??

-- Forwarded message --
From: Sølvi 
Date: 2011/10/11
Subject: Move from d:drive to c:drive
To: lyx-users@lists.lyx.org


Hi,

I'm currently using Windows XP with LyX v.2.0.0

I have a huge document, it's a master with several child documents included
which then again have documents/figures etc inserted (it's like a christmas
tree). I have been working on the d: drive on a pc but now I have to work on
a pc that only have a c: drive and I probably have to move it all back to
the pc with the d: drive later.

Is there any easy way to do this or do I have to "rebuild" the entire
document? It's a big document with lots of files incorporated.

Regards,
Solvi

Re: Branch names with spaces

2011-10-14 Thread Jürgen Spitzmüller 
Manveru wrote:
> > This is now fixed in the development trunk and will be fixed in LyX
> > 1.6.3 if I get green light for that.
> 
> I had the similar problem in 2.0.1 on Linux.

Of course I meant it will be fixed in 2.0.2. I cannot change the past, after 
all.

Jürgen

Re: Branch names with spaces

2011-10-14 Thread Manveru 
2011/10/14 Jürgen Spitzmüller :
> Graeme wrote:
>> According to ticket #5806 (http://www.lyx.org/trac/ticket/5806), the bug
>> preventing branch names with spaces was fixed in version 1.6.3, but it
>> is still present in 2.0 (on Windows at least).
>>
>> As the attached LyX file shows, Branches with spaces in the names can be
>> created, but after the LyX file has been closed and re-opened, such
>> branches do not display correctly on screen as the part of the name
>> after the space has been stripped off.
>>
>> Strangely, the full branch name, including the part after the space,
>> still appears in the Document Settings/Branches menu page.
>
> You found a bug. The branch list is parsed correctly (this was #5806), but the
> individual branches' name in the document was not.
>
> This is now fixed in the development trunk and will be fixed in LyX 1.6.3 if I
> get green light for that.
>

I had the similar problem in 2.0.1 on Linux.

-- 
Manveru
jabber: manv...@manveru.pl
     gg: 1624001
   http://www.manveru.pl

Re: Branch names with spaces

2011-10-14 Thread Jürgen Spitzmüller 
Graeme wrote:
> According to ticket #5806 (http://www.lyx.org/trac/ticket/5806), the bug
> preventing branch names with spaces was fixed in version 1.6.3, but it
> is still present in 2.0 (on Windows at least).
> 
> As the attached LyX file shows, Branches with spaces in the names can be
> created, but after the LyX file has been closed and re-opened, such
> branches do not display correctly on screen as the part of the name
> after the space has been stripped off.
> 
> Strangely, the full branch name, including the part after the space,
> still appears in the Document Settings/Branches menu page.

You found a bug. The branch list is parsed correctly (this was #5806), but the 
individual branches' name in the document was not.

This is now fixed in the development trunk and will be fixed in LyX 1.6.3 if I 
get green light for that.

Jürgen

> Graeme

Re: "language" settings inconsistent with the user's guide

2011-10-14 Thread Jürgen Spitzmüller 
Guenter Milde wrote:
> But maybe could be made more clear, like
> 
>   Default: Automatic selects the most suitable language package for the
>view/export format you will use.
>   
>Defaults to the package babel. 
>
>With "use non-TeX fonts" the package polyglossia will be used
>instead.

Actually, it is as follows:

Default: Uses the language package specified in Tools > Preferences

Automatic: Selects the most suitable language package for the view/export 
format you will use. This will use the newer polyglossia package whenever this 
is suitable (XeTeX backend, non-TeX fonts, all laguages covered by 
polyglossia)

Always Babel: Use babel even when polyglossia would be suitable.

The docs need to be corrected.

Jürgen

Re: Lyx, arXiv.org and \pdfoutput=1

2011-10-14 Thread Guenter Milde 
On 2011-10-11, Richard Heck wrote:
> On 10/11/2011 09:41 AM, Torquil Macdonald Sørensen wrote:
>> Hi!

>> In order to successfully submit an article that uses PDF figures to
>> the arXiv.org preprint server, it is necessary to have

>> \pdfoutput=1

>> within the top five lines of the document. This is necessary in order
>> to tell arXiv.org not to attempt any processing for generation of DVI
>> and PS, which will not work since the figures are in PDF format.

>> Is it possible make LyX include this in its LaTeX (pdflatex) export,
>> so I don't have to add it manually to the resulting tex-file?

> No. But you could have a simple script do it.

You can, of course, also file a feature request (or patch the LyX sources).

Günter

Re: "language" settings inconsistent with the user's guide

2011-10-14 Thread Guenter Milde 
On 2011-10-12, Olivier Ripoll wrote:
> Hi,

> I'm using Uwe's binary (LyX 2.0.1 on Win7 64bits, Miktex 2.9), so 
> perhaps it's the cause of this inconsistency.

> About the Document-> Settings-> Language, section B9 of the User's guide 
> states:
> ---
> Default is the package babel.

> Automatic selects the most suitable language package for the view/export 
> format you will use. For example for the XeTeX formats the package 
> polyglossia will be used instead of babel.
> ---

> However, when I use Default or Automatic, generating the pdf with XeTeX 
> result in failures, with an error message mentionning polyglossia(*).

> If I switch to "Always Babel", compilation works fine. So I have the 
> impression that either the documentation is wrong or that LyX does not 
> do as expected.

The documentation just tells this:
...
> polyglossia will be used instead of babel.

But maybe could be made more clear, like

  Default: Automatic selects the most suitable language package for the
   view/export format you will use.
  
   Defaults to the package babel. 
   
   With "use non-TeX fonts" the package polyglossia will be used
   instead.


> (*) It seems XeTeX and polyglossia have had issues in the past weeks, 
> but may have been fixed very recently. But that's besides the point.

Yes, there is a polyglossia bug (using a package without requiring it) that
was exposed with the latest update to fontspec. It has nothing to do with
XeTeX (except that polyglossia is for use with XeTeX/LuaTeX).

Günter

Re: Branches and document class

2011-10-14 Thread Guenter Milde 
On 2011-10-12, Torquil Macdonald Sørensen wrote:

> Is it possible to have two branches of the same lyx document, with different 
> document classes?

No. But you can include a document into a document with different document
class, as LyX strips the preamble of included documents. You will get a
warning, as there might be incompatibilities.

You can combine this with branches, creating the same branches in both
documents but activating just one ("global" vs "standalone", say) in
Document>Settings.

Günter

Re: replace upper case acronyms with small caps case

2011-10-14 Thread Guenter Milde 
On 2011-10-12, e-letter wrote:
> On 12/10/2011, e-letter  wrote:
>> On 12/10/2011, Liviu Andronic  wrote:
>>> On Wed, Oct 12, 2011 at 10:36 PM, e-letter  wrote:
 Readers,

 Is it possible to select an acronym e.g. ABC and replace all copies in
 a document with the latex code \textsc{abc}?

>>> It should be possible. Look into advanced search & replace. Otherwise,
>>> use regexp and a text editor.

>> Tried to use advanced find and replace; the result was \textsc{abc} in
>> the pdf document!

>> Then tried to open the lyx file using a text editor and replaced using
>> the editor. The result was that the entire acronym disappeared!

> I have now noticed that not only the acronym disappears but a random
> small quantity of words after the acronym (seems about 3-5 words) also
> disappear! Very bad!

The *.lyx file is not a *.tex file but in LyX's internal, non-documented
format. Editing with a text editor is a powerful means but requires caution.

For a regexp replace like the above:

* Change one occurence "manually" in the LyX GUI and remember its position.

* make a backup

* Open the file in a text editor,

* search the LyX code for the new construct (!! May be several lines
  instead of a single word if there is a format change or ERT box!! -- if
  unsure, make a diff to the *.lyx~ file (assuming one save before and
  one after the intended change).)
  
* search the LyX code for the old construct

* do the regexp replace now you know (or copied) the "from" and "to" strings

* save

* in LyX, do "Revert to saved"

* Check whether it is working before doing more work on the document.
  

Günter

replace not working in short title?

2011-10-14 Thread Wolfgang Engelmann 
Is it correct that replace is not working in a short title of a legend?
I am using Lyx 2.0.1

Wolfgang