Re: LyX without classes

[Joel Kulesza]

On Wed, Sep 27, 2017 at 9:12 PM, Carlos Knauer 
wrote:

> I had to install LyX 2.2.3 on my notebook and classes dont come . Why ?
>

Are you using a Mac?  If so, I wonder if this could be the issue:
https://www.lyx.org/trac/ticket/10671

- Joel

LyX without classes

[Carlos Knauer]

I had to install LyX 2.2.3 on my notebook and classes dont come . Why ?

Re: scrltr2 logo issues resolved; new issues generated [FIXED]

[Rich Shepard]

On Wed, 27 Sep 2017, Rich Shepard wrote:


I just checked by loading letters from 2011 and 2013. In both cases when I
tried to display them error messages were presented. In one case, it did
not like the ERT of \newpage. Told me it was undefined.


  Found and fixed: the line spacing was changed from single to custom.
Changing it back fixed the line spacing issue and now it displays correctly
on screen, in preview, and compiled as a PDF.

  Whew! I certainly learned a lot from this. Thanks to everyone, especially
Jean-Marie.

Rich

Re: scrltr2 logo issues resolved; new issues generated

[Rich Shepard]

On Wed, 27 Sep 2017, Rich Shepard wrote:


I think I know why these issues have appeared this week when all previous
letters (and documents using the other KOMA-Script classes) worked as
expected: over the weekend I upgraded TeXLive from 2015 to 2017. There are
likely changes in there that are incompatible with the settings I used to
use. Possible?


  I just checked by loading letters from 2011 and 2013. In both cases when I
tried to display them error messages were presented. In one case, it did not
like the ERT of \newpage. Told me it was undefined.

Rich

Re: Setting LyX font size [FIXED]

[Rich Shepard]

On Mon, 25 Sep 2017, Rich Shepard wrote:


Now, the LyX frame and menu font size has shrunk. The document display
font remains the same, it's the application frame and menus that have
changed.

 Is there a place where I can change this?


  Found the solution in the wiki: qtconfig is the tool to use.

  The LyX menu font size had shrunk to ~6pt. I reset it to 9pt and it's once
again readable.

Rich

Re: scrltr2 logo issues resolved; new issues generated

[Rich Shepard]

On Wed, 27 Sep 2017, Rich Shepard wrote:


It's not that simple. I commented out the second line (above) in the
preamble and the screen display as well as the preview has drastically
changed. Lines are displayed on top of each other and the signature
environment is not behaving as before.


  I think I know why these issues have appeared this week when all previous
letters (and documents using the other KOMA-Script classes) worked as
expected: over the weekend I upgraded TeXLive from 2015 to 2017. There are
likely changes in there that are incompatible with the settings I used to
use. Possible?

Rich

Re: scrltr2 logo issues resolved; new issues generated

[Rich Shepard]

On Wed, 27 Sep 2017, Jean-Marie Pacquet wrote:


It seems to me that you don't need the lco file: I created it to put all
your settings in it. Since you still have these settings after the call to
the lco, they are duplicated and I don't think it's a good idea.

Just remove these 2 lines:
%% Load an *.lco style file (see KOMA documentation)
\LoadLetterOption{Rich}%


Jean-Marie,

  It's not that simple. I commented out the second line (above) in the
preamble and the screen display as well as the preview has drastically
changed. Lines are displayed on top of each other and the signature
environment is not behaving as before.

  I'll need to look more closely at this this evening unless I can send you
the entire .lyx file off the mail list as it's proprietary business
information.

Thanks,

Rich

Re: scrltr2 logo issues resolved; new issues generated

[Jean-Marie Pacquet]

Le 27/09/2017 à 19:19, Rich Shepard a écrit :
>   Modifying the preamble and top of the body section in the .lyx file to
> properly display the logo, and matching the preamble to that of a document
> that has the proper letter element spacing has produced some new errors;
> see
> attached screenshot.
> 
>   When I open the file I get a message box with an error and some of the
> text at the top of the letter has incorrect line spacing so two lines are
> overlaid.
> 
>   Do I look in the .lco file, the preamble, or the .lyx file for what I
> broke?

Rich,

It seems to me that you don't need the lco file: I created it to put all
your settings in it. Since you still have these settings after the call
to the lco, they are duplicated and I don't think it's a good idea.

Just remove these 2 lines:
%% Load an *.lco style file (see KOMA documentation)
\LoadLetterOption{Rich}%

-- 
Jean-Marie

Re: Backtick in LyX's "LyX-Code" mode

[Bruce Momjian]

On Wed, Sep 27, 2017 at 12:41:27PM -0400, Scott Kostyshak wrote:
> On Mon, Sep 25, 2017 at 10:24:47PM +, Bruce Momjian wrote:
> > I am using LyX 2.1.2 on Ubuntu 14.04.
> > 
> > If I enter this:
> > 
> >  ab'c de`f
> > 
> > in "Standard" mode I get PDF output with proper left/right single
> > quotes.  However, if I switch to LyX-Code mode for that text, I get as
> > PDF output:
> > 
> > ab'c de'f
> 
> Testing on 2.1.0 and on 2.3.0dev, I get the following as PDF output:
> 
>   ab’c de‘f
> 
> which is different from what you get, but also not what you want.

Actually, that would be fine output, as long as they look different.

> > This is a problem for text of shell scripts.  I the want backticks
> > because backtick means 'execute' in the shell.
> > 
> > What I have done instead to get literal backticks output is to use a
> > TeX Code URT (Ugly Red Text) block inside the "LyX-Code mode" block and
> > used \char18, which properly outputs the backtick.
> > 
> > Is this expected behavior?  Is that the recommended solution for this?
> 
> I have not seen a report of this, but I haven't seen an indication that
> a lot of people are using LyX-Code, so I'm not sure if is known.

OK, not sure what could be the cause then.  I am using ps2pdf to produce
the PDF.

What I have done as a work-around is to warn in my Makefile if a
backquote is used in the LyX document.

-- 
  Bruce Momjian  http://momjian.us
  EnterpriseDB http://enterprisedb.com

+ As you are, so once was I.  As I am, so you will be. +
+  Ancient Roman grave inscription +

Re: Backtick in LyX's "LyX-Code" mode

[Scott Kostyshak]

On Mon, Sep 25, 2017 at 10:24:47PM +, Bruce Momjian wrote:
> I am using LyX 2.1.2 on Ubuntu 14.04.
> 
> If I enter this:
> 
>ab'c de`f
> 
> in "Standard" mode I get PDF output with proper left/right single
> quotes.  However, if I switch to LyX-Code mode for that text, I get as
> PDF output:
> 
>   ab'c de'f

Testing on 2.1.0 and on 2.3.0dev, I get the following as PDF output:

  ab’c de‘f

which is different from what you get, but also not what you want.

> This is a problem for text of shell scripts.  I the want backticks
> because backtick means 'execute' in the shell.
> 
> What I have done instead to get literal backticks output is to use a
> TeX Code URT (Ugly Red Text) block inside the "LyX-Code mode" block and
> used \char18, which properly outputs the backtick.
> 
> Is this expected behavior?  Is that the recommended solution for this?

I have not seen a report of this, but I haven't seen an indication that
a lot of people are using LyX-Code, so I'm not sure if is known.

Scott


signature.asc
Description: PGP signature

Re: KOMA-letter-2: logo disappeared [RESOLVED]

[Rich Shepard]

On Wed, 27 Sep 2017, Jean-Marie Pacquet wrote:


Just remove this line from your settings:
\firsthead{\centering\usekomavar{fromlogo}\hspace*{8cm}}


Jean-Marie,

  Yes, I should have seen that. You mentioned it in your last message.
Perhaps I need another mug of coffee?

  It's interesting that when I open mwe.lyx I get an error message about an
unknown 'default default' in the header, yet when I search for that double
string I find nothing. I'll ignore it for now.

Thanks again for your help and lessons,

Rich

Re: KOMA-letter-2: logo disappeared

[Jean-Marie Pacquet]

Le 27/09/2017 à 17:22, Rich Shepard a écrit :
>   I have a minimal non-working example file called mwe.lyx (copy attached,
> with llc-letterhead.pdf). I thought that I modified it to match your
> rich.lyx example (using two columns in emacs to compare files), yet the
> logo
> still displays too large on the lyx screen and does not appear when I
> preview the document. I have a larger preamble which formats the pages as
> I've used them for years. But, I am not seeing what I've missed that
> prevents the logo from displaying in the preview, or what is present that
> interferes with it.
> 
>   Please show me what I've missed.

Rich,

Just remove this line from your settings:

\firsthead{\centering\usekomavar{fromlogo}\hspace*{8cm}}

-- 
Jean-Marie

Re: KOMA-letter-2: logo disappeared

[Persio Barros]

Rich,


I can see in your .tex file in the the line 56, the command:


\includegraphics[bb=80bp 100bp 520bp 
240bp,clip,width=0.8\textwidth]{0_home_rshepard_documents_templates_llc-letterhead.eps}


The problem here is the "bb" option. The latest version of pdftex.def doesn't 
handle this option and leaves an empty box where the picture was supposed to be 
inserted.

This bug have been reported in this list some days ago.


I have managed to overcome this bug by inserting the following lines in the 
document preamble:


\def\GPT@warn{\@PackageWarning{pdftex.def}}%

\def\GPT@disable#1{%

\GPT@warn{%

Option `#1' is not supported, use\MessageBreak

option `viewport' instead%

}%

}

\def\GPT@fix{%

\begingroup\expandafter\expandafter\expandafter\endgroup

\expandafter\ifx\csname define@key\endcsname\relax

\else

\def\KV@Gin@bb{%

\GPT@warn{%

Option `bb' does not make sense,\MessageBreak

using `viewport' instead%

}%

\KV@Gin@viewport

}%

\define@key{Gin}{bbllx}{\GPT@disable{bbllx}}%

\define@key{Gin}{bblly}{\GPT@disable{bblly}}%

\define@key{Gin}{bburx}{\GPT@disable{bburx}}%

\define@key{Gin}{bbury}{\GPT@disable{bbury}}%

\define@key{Gin}{natwidth}{\GPT@disable{natwidth}}%

\define@key{Gin}{natheight}{\GPT@disable{natheight}}%

\fi

}

\AtBeginDocument{\GPT@fix}


Persio