Re: r39133 - www-user/trunk/farm/cookbook/LyX

[Uwe Stöhr]

Am 18.06.2011 14:59, schrieb rgh...@lyx.org:


-$lyx_version = "2.0.1svn";
+$lyx_version = "2.1.0svn";


This is incorrect. The list should reflect the translations of branch, so 
2.0.1svn was correct.

regards Uwe

Re: Springer layout files

[Marcus Kriele]

Hi Uwe,

thanks for the work you are putting in to improve my changes!

On 2011-6-17 24:35 , Uwe Stöhr wrote:
I had a look and fixed this. (You forgot to define the counters.) I 
created now a new file which contains all theorem environments of 
classes which already define them, like the sv*** classes.

Thanks!
- defining the column and side number in svcommon is no good idea 
since a book might have 2 columns and 2 sides, while an article is 
only 1-sided. Some articles have 1, some 2 columns. I therefore 
removed this definition
I agree that my implementation was not elegant.  However, I have tested 
all classes, including 1 and 2-column text for articles.  According to 
my testing there were no problems with my original implementation.
- Definitions like "LeftMargin "TOC title:xxx"" are problematic. The 
strings will be translatd. Assume that for "TOC" there is e.g. no 
corresponding abbreviation in German and it will therefore be 
translated to "Inhaltsverzeichnis" which is much longer.


Thanks for pointing this out.  I completely ignored localization.  If 
you have a better naming idea, could you please change the files 
accordingly?
- for titlerunning and authorrunning the InTitle flag was missing. 
This is necessary that LyX don't end the title when these commands are 
inserted

Thanks. I did not notice this issue.
- svcommons contained Style Sol and Style Solution_(theorem-like). 
From its definition both lead to the same LaTeX/PDF output. So we only 
need one of them. The same was for Style Problem. I therefore removed 
the doubled Styles.
Springer is very inconsistent with its classes and they managed to use 
different names for identical environments in different classes. In 
addition, they use the same name for different environments.  So you 
will see that some environments have been redefined in the class 
specific layout files.  I have actually searched the .cls files to find 
out what names they have used in every instance.   Could you please 
revert your deletions  so that the LyX classes are consistent with the 
corresponding LaTeX classes?

I committed my changes to SVN trunk:
http://www.lyx.org/trac/changeset/39126
and also adapted the svjour3.lyx template file according to the latest 
version of the official svjour3 example LaTeX-file. Please test.
Sorry, I am not a developer and do not know how SVN & changesets work.  
Could you send me the files via email? I would then do some testing if 
you would find this helpful.
I did not yet have a look at svmono and svmult. I will do this the 
next days. 
Please see the *testfile*.lyx files that I had uploaded to the bug 
report 7301
Our template files for these classes are of course still compilable 
after my changes but I guess they need to be adapted for the latest 
versions of the official LaTeX example files. Do you want to do this?
Perhaps my test files could serve as template files.  The advantage 
would be that they use all features.

regards Uwe

Re: Springer layout files

[Marcus Kriele]

Please see the class specific test files that I had uploaded to bug 
report #7301.  They should contain every feature that is supported.  
Hopefully this reduced the amount of time necessary for further 
testing.  I had also uploaded updated template files.


Regards, Marcus



On 2011-6-17 9:43 , Uwe Stöhr wrote:

Am 17.06.2011 14:18, schrieb Richard Heck:


Thanks, Uwe, for having a close look at these. I guess this stuff should
be ported to branch, but probably not until 2.0.2,


Yes, we need more testing before this can go to branch. svcommon is 
used for 3 different classes and I only reviewed 1 in detail.


regards Uwe

RFE: find&replace excluding insets

[Jack Tanner]

I wonder if this is on somebody's to-do list: it'd be nice to be able to find
and replace but only inside (outside) certain kinds of insets, e.g., only in
program listings, or e.g., everywhere except in notes.

Re: Unwanted indent in Bibliography

[Enrico Forestieri]

On Sat, Jun 18, 2011 at 09:41:18AM -0400, Richard Heck wrote:

> Hmm. The LaTeX code is exactly what one would expect

Not at all. The argument of thebibliography environment should be a piece
of text the same width as (or slightly larger than) the widest item label,
while LyX produces

\begin{thebibliography}{References}

and "References" is much larger than any item label. Generally one uses

\begin{thebibliography}{99}

as "99" is at least as wide as a two-digit number.

-- 
Enrico

Re: #7637: Lyx to Tex to Lyx

[John McDermott]

Done. Thanks. I think it has to do with the BibTex bibliography. I use BibDesk 
with a Mac.

John


On Jun 18, 2011, at 6:12 AM, LyX Ticket Tracker wrote:

> #7637: Lyx to Tex to Lyx
> ---+
> Reporter:  FordMadox  |   Owner:  lasgouttes
> Type:  defect |  Status:  new   
> Priority:  normal |   Milestone:
> Component:  general| Version:  2.0.0 
> Severity:  normal |Keywords:
> ---+
> Changes (by stwitt):
> 
> * cc: stwitt (added)
> 
> 
> Comment:
> 
> Please, can you produce a small .lyx file to demonstrate the problem and
> attach it to the ticket?
> 
> -- 
> Ticket URL: 
> The LyX Project 
> LyX -- The Document Processor

John McDermott
pro...@me.com
http://web.me.com/proust/mcdermott/index.html

Re: Unwanted indent in Bibliography

[Richard Heck]

On 06/18/2011 09:00 AM, Donato Capitella wrote:
> Sure... here it is.
>
> On Sat, Jun 18, 2011 at 1:57 PM, Richard Heck  wrote:
>> On 06/18/2011 07:28 AM, Donato Capitella wrote:
>>> Dear all,
>>> I've been using Lyx for a year or so. However, I've been having an
>>> annoying problem since I switched to version 2.0.
>>> Basically, when I use the article class, my bibliography items under
>>> the References heading are all indented and they should not be and
>>> have never been in previous versions. As a result, when I need to
>>> regenerate my old documents, I get this weired indented bibliography
>>> and of course this applies also to new documents.
>>>
>>> Is there a fix?
>>>
>> Can you please post a small example file?
>>
Hmm. The LaTeX code is exactly what one would expect, but I do see the
indentation. This seems to be something on the LaTeX end. Anyone else
have any ideas?

Richard



sample.lyx
Description: application/lyx

Re: Exporting & importing underlined text

[Richard Heck]

On 06/18/2011 08:02 AM, Pavel Sanda wrote:
> Andrew Parsloe wrote:
>> I reported a problem about importing underlined text on the users' list a 
>> week or so ago without getting a bite. In LyX 2.0 in the View Source 
>> window, underline is shown as \uline{text}, whereas \underbar{text} was 
>> used in LyX 1.6. If the document is exported as Latex (from LyX 2.0) 
>> \uline{text} is how it appears in the Latex document. If this Latex 
>> document is now imported into LyX, the underline is treated as ERT and not 
>> interpreted as underlined text.
> this is kind of regression, indeed. the \underbar -> \uline was fileformat
> change. i'm not sure tex2lyx is finally able to cope with newer fileformat
> changes with last help from Georg.
>
This was at 357. tex2lyx is up to 345.

rh

Re: Enabling https acces to LyX svn?

[Richard Heck]

On 06/18/2011 06:53 AM, Jean-Marc Lasgouttes wrote:
> Le 17/06/11 21:07, Vincent van Ravesteijn a écrit :
>> I have to say I'm not thrilled about this.
>>
>> - Branch doesn't evolve interestingly enough from day to day to let
>> there be a need for regular builds.
>
> I think having more people following branch day-to-day is great. This
> means that users who are not computer savvy enough to apply patches
> can still give us feedback about the fixes we apply.
>
I agree: Feedback about current branch is really important. Daily builds
might not be critical, but weekly ones would be great, and if we get
daily, that's fine.

Richard

Re: Exporting & importing underlined text

[Pavel Sanda]

Andrew Parsloe wrote:
> I reported a problem about importing underlined text on the users' list a 
> week or so ago without getting a bite. In LyX 2.0 in the View Source 
> window, underline is shown as \uline{text}, whereas \underbar{text} was 
> used in LyX 1.6. If the document is exported as Latex (from LyX 2.0) 
> \uline{text} is how it appears in the Latex document. If this Latex 
> document is now imported into LyX, the underline is treated as ERT and not 
> interpreted as underlined text.

this is kind of regression, indeed. the \underbar -> \uline was fileformat
change. i'm not sure tex2lyx is finally able to cope with newer fileformat
changes with last help from Georg.

add this problem to bugzilla please.
pavel

> I poked around in the source code and found in text.cpp in the tex2lyx 
> folder this code:
>
> else if (t.cs() == "underbar") {
>   // Do NOT handle \underline.
>   // \underbar cuts through y, g, q, p etc.,
>   // \underline does not.
>   context.check_layout(os);
>   os << "\n\\bar under\n";
>   parse_text_snippet(p, os, FLAG_ITEM, outer, context);
>   context.check_layout(os);
>   os << "\n\\bar default\n";
>
> Because of the "underbar" here, I wondered if the Latex document would 
> import correctly to LyX 2.0 if \uline{text} were replaced by 
> \underbar{text}. I changed the document in a text editor and it does import 
> correctly.
>
> Either LyX 2.0 should export \underbar{text} or, what I imagine may have 
> happened, "underbar" in this piece of code has been overlooked and should 
> be "uline". However, I haven't the means to check this.
>
> Andrew

Re: Enabling https acces to LyX svn?

[Jean-Marc Lasgouttes]

Le 17/06/11 21:07, Vincent van Ravesteijn a écrit :

I have to say I'm not thrilled about this.

- Branch doesn't evolve interestingly enough from day to day to let
there be a need for regular builds.


I think having more people following branch day-to-day is great. This 
means that users who are not computer savvy enough to apply patches can 
still give us feedback about the fixes we apply.


JMarc

Exporting & importing underlined text

[Andrew Parsloe]

I reported a problem about importing underlined text on the users' list 
a week or so ago without getting a bite. In LyX 2.0 in the View Source 
window, underline is shown as \uline{text}, whereas \underbar{text} was 
used in LyX 1.6. If the document is exported as Latex (from LyX 2.0) 
\uline{text} is how it appears in the Latex document. If this Latex 
document is now imported into LyX, the underline is treated as ERT and 
not interpreted as underlined text.


I poked around in the source code and found in text.cpp in the tex2lyx 
folder this code:


else if (t.cs() == "underbar") {
// Do NOT handle \underline.
// \underbar cuts through y, g, q, p etc.,
// \underline does not.
context.check_layout(os);
os << "\n\\bar under\n";
parse_text_snippet(p, os, FLAG_ITEM, outer, context);
context.check_layout(os);
os << "\n\\bar default\n";

Because of the "underbar" here, I wondered if the Latex document would 
import correctly to LyX 2.0 if \uline{text} were replaced by 
\underbar{text}. I changed the document in a text editor and it does 
import correctly.


Either LyX 2.0 should export \underbar{text} or, what I imagine may have 
happened, "underbar" in this piece of code has been overlooked and 
should be "uline". However, I haven't the means to check this.


Andrew