Re: LaTeX warning explanation needed

2021-10-13 Thread Rich Shepard

On Wed, 13 Oct 2021, Paul A. Rubin wrote:


The line numbers refer to lines in the .tex file being compiled, not lines
in the .lyx file. The .tex file will be hiding in the temp directory LyX
is using.


Paul,

Well, that makes sense. The .tex file and it's other files seem to have
vanished when I closed lyx. There's nothing in /tmp/.

More investigation tomorrow.

Thanks,

Rich
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: LaTeX warning explanation needed

2021-10-13 Thread Paul A. Rubin

On 10/13/21 6:47 PM, Rich Shepard wrote:

The document now compiles without error using TeXLive2021 (and the 2020
version of texlive-extra), but the bibliography still does not print 
in the

PDF.

The latex.log has these warnings:
LaTeX Warning: Citation 'Groot1991' on page 4 undefined on input line 
151.
LaTeX Warning: Citation 'Marcoe2018' on page 4 undefined on input line 
167.


Lines 149-151 in the .lyx file are:
\begin_layout Standard
\begin_inset ERT
status open

and lines 163-167 are:
\begin_inset CommandInset toc
LatexCommand tableofcontents

\end_inset

There are other warnings at the top of the (attached) latex.log file 
and I

need help understanding what the warnings mean.

TIA,

Rich


Rich,

The line numbers refer to lines in the .tex file being compiled, not 
lines in the .lyx file. The .tex file will be hiding in the temp 
directory LyX is using.


Paul

-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


LaTeX warning explanation needed

2021-10-13 Thread Rich Shepard

The document now compiles without error using TeXLive2021 (and the 2020
version of texlive-extra), but the bibliography still does not print in the
PDF.

The latex.log has these warnings:
LaTeX Warning: Citation 'Groot1991' on page 4 undefined on input line 151.
LaTeX Warning: Citation 'Marcoe2018' on page 4 undefined on input line 167.

Lines 149-151 in the .lyx file are:
\begin_layout Standard
\begin_inset ERT
status open

and lines 163-167 are:
\begin_inset CommandInset toc
LatexCommand tableofcontents

\end_inset

There are other warnings at the top of the (attached) latex.log file and I
need help understanding what the warnings mean.

TIA,

Rich
This is pdfTeX, Version 3.141592653-2.6-1.40.22 (TeX Live 2021 on Slint) 
(preloaded format=pdflatex 2021.10.13)  13 OCT 2021 15:36
entering extended mode
 restricted \write18 enabled.
 %&-line parsing enabled.
**biological-evaluation.tex
(./biological-evaluation.tex
LaTeX2e <2020-10-01> patch level 4
L3 programming layer <2021-02-18>
(/usr/share/texmf-dist/tex/latex/koma-script/scrreprt.cls
Document Class: scrreprt 2021/03/17 v3.33 KOMA-Script document class (report)
(/usr/share/texmf-dist/tex/latex/koma-script/scrkbase.sty
Package: scrkbase 2021/03/17 v3.33 KOMA-Script package (KOMA-Script-dependent b
asics and keyval usage)
(/usr/share/texmf-dist/tex/latex/koma-script/scrbase.sty
Package: scrbase 2021/03/17 v3.33 KOMA-Script package (KOMA-Script-independent 
basics and keyval usage)
(/usr/share/texmf-dist/tex/latex/koma-script/scrlfile.sty
Package: scrlfile 2021/03/17 v3.33 KOMA-Script package (file load hooks)
(/usr/share/texmf-dist/tex/latex/koma-script/scrlfile-hook.sty
Package: scrlfile-hook 2021/03/17 v3.33 KOMA-Script package (using LaTeX hooks)


LaTeX3 Info: Defining command \BeforeFile with sig. 'm' on line 61.


LaTeX3 Info: Defining command \AfterFile with sig. 'm' on line 65.


LaTeX3 Info: Defining command \BeforeClass with sig. 'm' on line 69.


LaTeX3 Info: Defining command \BeforePackage with sig. 'm' on line 73.


LaTeX3 Info: Defining command \AfterAtEndOfClass with sig. 'smo+m' on line 83.


LaTeX3 Info: Defining command \AfterAtEndOfPackage with sig. 'smo+m' on line
(LaTeX3) 93.


LaTeX3 Info: Defining command \scrlfile@AfterClass with sig. 'smo+m' on line
(LaTeX3) 173.


LaTeX3 Info: Defining command \AfterClass with sig. '' on line 174.


LaTeX3 Info: Defining command \scrlfile@AfterPackage with sig. 'smo+m' on line
(LaTeX3) 191.


LaTeX3 Info: Defining command \AfterPackage with sig. '' on line 192.


LaTeX3 Info: Defining command \ReplaceInput with sig. '' on line 193.


LaTeX3 Info: Defining command \ReplaceClass with sig. 'mm' on line 196.


LaTeX3 Info: Defining command \ReplacePackage with sig. 'mm' on line 199.


LaTeX3 Info: Defining command \UnReplaceInput with sig. '' on line 200.


LaTeX3 Info: Defining command \UnReplaceClass with sig. 'm' on line 203.


LaTeX3 Info: Defining command \UnReplacePackage with sig. 'mm' on line 206.


LaTeX3 Info: Defining command \PreventPackageFromLoading with sig. 's+om' on
(LaTeX3) line 234.


LaTeX3 Info: Defining command \StorePreventPackageFromLoading with sig. 'm' on
(LaTeX3) line 242.


LaTeX3 Info: Defining command \ResetPreventPackageFromLoading with sig. '' on
(LaTeX3) line 247.


LaTeX3 Info: Defining command \UnPreventPackageFromLoading with sig. 'sm' on
(LaTeX3) line 261.


LaTeX3 Info: Defining command \BeforeClosingMainAux with sig. 'om' on line
(LaTeX3) 274.


LaTeX3 Info: Defining command \AfterReadingMainAux with sig. 'om' on line 287.


LaTeX3 Info: Defining command \protected@immediate@write with sig. 'm+m+m' on
(LaTeX3) line 298.

(/usr/share/texmf-dist/tex/latex/koma-script/scrlogo.sty
Package: scrlogo 2021/03/17 v3.33 KOMA-Script package (logo)
))) (/usr/share/texmf-dist/tex/latex/graphics/keyval.sty
Package: keyval 2014/10/28 v1.15 key=value parser (DPC)
\KV@toks@=\toks15
)
Skipping: [2021/05/01] Usage of raw option list on input line 252.
Applying: [/00/00] compatibility for LaTeX before 2021/05/01 on input line 
337.
)) (/usr/share/texmf-dist/tex/latex/koma-script/tocbasic.sty
Package: tocbasic 2021/03/17 v3.33 KOMA-Script package (handling toc-files)
\scr@dte@tocline@numberwidth=\skip47
\scr@dte@tocline@numbox=\box47
)
Package tocbasic Info: babel extension for `toc' omitted
(tocbasic) because of missing \bbl@set@language on input line 137.
Class scrreprt Info: File `scrsize11pt.clo' used instead of
(scrreprt)   file `scrsize11.clo' to setup font sizes on input line 245
1.
(/usr/share/texmf-dist/tex/latex/koma-script/scrsize11pt.clo
File: scrsize11pt.clo 2021/03/17 v3.33 KOMA-Script font size class option (11pt
)
) (/usr/share/texmf-dist/tex/latex/koma-script/typearea.sty
Package: typearea 2021/03/17 v3.33 KOMA-Script package (type area)
\ta@bcor=\skip48
\ta@div=\count179
\ta@hblk=\skip49
\ta@vblk=\skip50
\ta@temp=\skip51
\footheight=\skip52
Package typearea Info: These are the values describing the 

PDF Page Size

2021-10-13 Thread Ken Kopelson
Hello all,
I am really hoping that one of you brilliant people can answer this
question concerning page size for PDFs.

First, this is concerning the latest LyX (2.3.6.1), along with the latest
MiKTeK (21.6/7) on Windows 10.  I use LyX on both MacOS, and on Windows.
It is the Windows version that fails to do the right thing.

When I set a page size using the MacOS LyX, (using the
document->settings->Page Layout) to something like 9 inches height x 6
inches width, and then export the document to PDF, it produces a document
that is the dimensions I requested, and all PDF viewers show it correctly.

Then, if I do the exact same thing in the Windows version, and export the
document to PDF, it produces a document that is Letter Size (8.5" x 11"),
regardless of the settings in the Page Layout.

This creates quite a problem, and makes it impossible to make an eBook
PDF.  Am I doing something wrong, or is this a bug that needs to be fixed?

Many thanks for your time in answering my question.
Ken Kopelson
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Compile error

2021-10-13 Thread Rich Shepard

On Wed, 13 Oct 2021, Dr Eberhard Lisse wrote:


BibTeX does not like Apostropes "'" in the label names.


el,

With more research on stackexchange I see that you're correct. My apologies.


The issue is with biblatex, too. But, it's supposed to have been fixed:

"This has been addressed in the recent update to biblatex and Biber (version
3.1 and 2.2 respectively).

"With \DeclareNolabel we can now choose exactly those characters to be
dropped from label creation, the default is \p{P}\p{S}\p{C}. In order to
preserve apostrophes you can use

"\DeclareNolabel{
  \nolabel{\regexp{[\p{S}\p{Z}\p{C}]+}}
}"

I don't know how to find the biblatex and Biber versions.

Placing the DeclareNoLabel in Settings -> Bibliography -> Citation Style ->
Options or in the preamble have no effect.

Rich
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: compile error not found in document or bibliographic database [RESOLVED]

2021-10-13 Thread Rich Shepard

On Wed, 13 Oct 2021, Rich Shepard wrote:


I think it's related to a biblatex style, but otherwise I've no idea where
that string is located.


Sure enough. I don't know if it was the citation or bibliography style
variant that caused the error. Regardless, setting both styles to authoryear
(after carefully reading the biblatex.pdf) removed that error when the
compiling the document.

However, I still have the issue of no bibliography in the PDF. The
bibliography is located after the last chapter and before the appendix.
(Removing the empty appendix makes no difference.)

Where should I look for the reason the bibliography isn't in the PDF?

Rich
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


compile error not found in document or bibliographic database

2021-10-13 Thread Rich Shepard

Compiling the document displays an error message box containing this excerpt
from the latex.log:
\tabbedlabeldatewidth=\skip92
! TeX capacity exceeded, sorry [input stack size=5000].
 \UseTextSymbol
  {TS1}
l.2949 \edef\blxarch@style@niedersachsen{Archä
   ologische Kommission für Nie...
If you really absolutely need more capacity,
you can ask a wizard to enlarge me.

When I search the document for 'Kommission' it's not found. Same with
searching the bibliographic database.

I think it's related to a biblatex style, but otherwise I've no idea where
that string is located.

The latex.log is attached. Really!!

I would like suggestions for finding where this originates.

TIA,

RichThis is pdfTeX, Version 3.14159265-2.6-1.40.21 (TeX Live 2020 on Slackware 
(SlackBuilds.org)) (preloaded format=pdflatex 2021.2.17)  13 OCT 2021 05:56
entering extended mode
 restricted \write18 enabled.
 %&-line parsing enabled.
**biological-evaluation.tex
(./biological-evaluation.tex
LaTeX2e <2020-02-02> patch level 5
L3 programming layer <2020-06-03>
(/usr/share/texmf-dist/tex/latex/koma-script/scrreprt.cls
Document Class: scrreprt 2020/04/19 v3.30 KOMA-Script document class (report)
(/usr/share/texmf-dist/tex/latex/koma-script/scrkbase.sty
Package: scrkbase 2020/04/19 v3.30 KOMA-Script package (KOMA-Script-dependent b
asics and keyval usage)
(/usr/share/texmf-dist/tex/latex/koma-script/scrbase.sty
Package: scrbase 2020/04/19 v3.30 KOMA-Script package (KOMA-Script-independent 
basics and keyval usage)
(/usr/share/texmf-dist/tex/latex/graphics/keyval.sty
Package: keyval 2014/10/28 v1.15 key=value parser (DPC)
\KV@toks@=\toks15
) (/usr/share/texmf-dist/tex/latex/koma-script/scrlfile.sty
Package: scrlfile 2020/04/19 v3.30 KOMA-Script package (loading files)
))) (/usr/share/texmf-dist/tex/latex/koma-script/tocbasic.sty
Package: tocbasic 2020/04/19 v3.30 KOMA-Script package (handling toc-files)
\scr@dte@tocline@numberwidth=\skip47
\scr@dte@tocline@numbox=\box45
)
Package tocbasic Info: babel extension for `toc' omitted
(tocbasic) because of missing \bbl@set@language on input line 137.
Class scrreprt Info: File `scrsize11pt.clo' used instead of
(scrreprt)   file `scrsize11.clo' to setup font sizes on input line 242
4.
(/usr/share/texmf-dist/tex/latex/koma-script/scrsize11pt.clo
File: scrsize11pt.clo 2020/04/19 v3.30 KOMA-Script font size class option (11pt
)
) (/usr/share/texmf-dist/tex/latex/koma-script/typearea.sty
Package: typearea 2020/04/19 v3.30 KOMA-Script package (type area)
\ta@bcor=\skip48
\ta@div=\count167
\ta@hblk=\skip49
\ta@vblk=\skip50
\ta@temp=\skip51
\footheight=\skip52
Package typearea Info: These are the values describing the layout:
(typearea) DIV  = 10
(typearea) BCOR = 0.0pt
(typearea) \paperwidth  = 597.50793pt
(typearea)  \textwidth  = 418.2pt
(typearea)  DIV departure   = -6%
(typearea)  \evensidemargin = 47.2316pt
(typearea)  \oddsidemargin  = -12.5192pt
(typearea) \paperheight = 845.04694pt
(typearea)  \textheight = 514.20023pt
(typearea)  \topmargin  = 12.2347pt
(typearea)  \headheight = 17.0pt
(typearea)  \headsep= 20.40001pt
(typearea)  \topskip= 11.0pt
(typearea)  \footskip   = 47.6pt
(typearea)  \baselineskip   = 13.6pt
(typearea)  on input line 1738.
)
\c@part=\count168
\c@chapter=\count169
\c@section=\count170
\c@subsection=\count171
\c@subsubsection=\count172
\c@paragraph=\count173
\c@subparagraph=\count174
\scr@dte@chapter@maxnumwidth=\skip53
Class scrreprt Info: using compatibility default `afterindent=bysign'
(scrreprt)   for `\chapter on input line 5588.
\scr@dte@section@maxnumwidth=\skip54
Class scrreprt Info: using compatibility default `runin=bysign'
(scrreprt)   for `\section on input line 5598.
Class scrreprt Info: using compatibility default `afterindent=bysign'
(scrreprt)   for `\section on input line 5598.
\scr@dte@part@maxnumwidth=\skip55
Class scrreprt Info: using compatibility default `afterindent=true'
(scrreprt)   for `\part on input line 5607.
\scr@dte@subsection@maxnumwidth=\skip56
Class scrreprt Info: using compatibility default `runin=bysign'
(scrreprt)   for `\subsection on input line 5617.
Class scrreprt Info: using compatibility default `afterindent=bysign'
(scrreprt)   for `\subsection on input line 5617.
\scr@dte@subsubsection@maxnumwidth=\skip57
Class scrreprt Info: using compatibility default `runin=bysign'
(scrreprt)   for `\subsubsection on input line 5627.
Class scrreprt Info: using compatibility default `afterindent=bysign'
(scrreprt)   for `\subsubsection on input line 5627.
\scr@dte@paragraph@maxnumwidth=\skip58
Class scrreprt Info: using compatibility default `runin=bysign'

Re: END-OF-FRAME, once again..

2021-10-13 Thread Scott Kostyshak
On Wed, Oct 13, 2021 at 07:59:16AM -0700, Rich Shepard wrote:
> On Wed, 13 Oct 2021, Scott Kostyshak wrote:
> 
> > I think the workflow you're suggesting makes the not-always-true
> > assumption that the user does not use the "frame" layout for the *content*
> > of the frame, and only uses nested layouts (e.g., itemize or standard).
> > Did I understand right?
> > 
> > What abut making it so that if the user changes the layout to "frame
> > title", then a *new* frame is started (i.e., LyX realizes "oh this frame
> > already has a frame title so the user must want a new frame)?
> 
> Scott,
> 
> I don't recall the exact keystrokes, but if the cursor is at the end of the
> last line in a frame and one presses (IIRC), shift-ctrl-enter, then an
> end-of-frame and new frame below that magically appears. That does the job,
> but takes two hands and a couple of fingers. :-)

Thanks, Rich. That's what I do also and it is the recommended approach.

Scott


signature.asc
Description: PGP signature
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Compile error [FIXED]

2021-10-13 Thread Rich Shepard

On Wed, 13 Oct 2021, Dr Eberhard Lisse wrote:


the author field is not the same as the label field.


Of course not.


Perhaps it is enclosed by curly braces by default. In which case, the
label field should thus also be, by default).


If you look at a bib(la)tex entry it begins with '@{'

That's followed by the label; that line ends with a comma. The closing curly
brace for the entire entry is at the end. In the meantime, the label field
has no closing curly brace so apostrophes, accents, etc. are not explicitly
displayed. Curly braces around the label field itself solve the problem


But it does make sense not to put Apostrophes into the labels.


Tell Irish authors that. :-)

Rich
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Bibliography styles

2021-10-13 Thread Rich Shepard

On Wed, 13 Oct 2021, Dr Eberhard Lisse wrote:


Because it is in the "label" (\cite key?)  field whereas (I assume without
having seen a MWE) the others are elsewhere ("author" field for example).


Yep.

And I sent a MWE with my first post but you thought it too long.

Rich
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: END-OF-FRAME, once again..

2021-10-13 Thread Rich Shepard

On Wed, 13 Oct 2021, Scott Kostyshak wrote:


I think the workflow you're suggesting makes the not-always-true
assumption that the user does not use the "frame" layout for the *content*
of the frame, and only uses nested layouts (e.g., itemize or standard).
Did I understand right?

What abut making it so that if the user changes the layout to "frame
title", then a *new* frame is started (i.e., LyX realizes "oh this frame
already has a frame title so the user must want a new frame)?


Scott,

I don't recall the exact keystrokes, but if the cursor is at the end of the
last line in a frame and one presses (IIRC), shift-ctrl-enter, then an
end-of-frame and new frame below that magically appears. That does the job,
but takes two hands and a couple of fingers. :-)

Regards,

Rich
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: END-OF-FRAME, once again..

2021-10-13 Thread Scott Kostyshak
On Wed, Oct 13, 2021 at 12:13:30PM +0200, Daniel wrote:
> On 13/10/2021 00:32, UD K wrote:
> > On 10/12/21 7:49 PM, Steve Litt wrote:
> > > UD K said on Mon, 11 Oct 2021 17:47:46 +0200
> > > 
> > > > I SHOULD know this, because it came up in the (distant) past, but
> > > > either I forgot, or Lyx has changed-- probably a little of both.
> > > >     I wanted to cut a frame from a lyx/beamer presentation and put it
> > > > in
> > > > another place in the presentation. Control-X, and Control-V failed. So
> > > > I tried to insert a new frame, but that came without an end-of-frame,
> > > I like LyX as much as the next guy --- I'm selling about 9 books
> > > authored in LyX. But when it comes to putting together a slide
> > > presentation with Beamer, I think LyX adds more complexity than it
> > > removes. When I use Beamer at all, I just edit the LaTeX in an editor.
> > > Doing that would be the kiss of death writing a book, but Beamer/LaTeX
> > > uses only a small subset of LaTeX.
> > > 
> > > SteveT
> > > 
> > > Steve Litt
> > > Spring 2021 featured book: Troubleshooting Techniques of the Successful
> > > Technologisthttp://www.troubleshooters.com/techniques
> > Steve-- I TOTALLY agree with you about the Lyx/Beamer combo being a
> > killjoy experience.  To make matters worse, I use this combination only
> > rarely, and in between, pandemics, Former-Presidents and other plagues
> > brush away what I knew about using it, so the experience is usually like
> > a root-canal: painful, frustrating and disappointing. It is harder to
> > use than the much maligned Impress of the even-more-maligned
> > LibreOffice, but of course the output, if I ever get to that stage, is
> > MUCH better looking.  Whether that improved look is worth the pain
> > depends on your pain threshold ;-)
> > 
> > -- 
> > Ehud Kaplan, Ph.D.
> 
> Hi,
> 
> It's always great to get feedback on LyX.

+1 especially *constructive* feedback :)

> Something that I thought while using beamer with LyX was that it seems that
> it would be easier if Frames would not "hang together". I mean: right now,
> if you press enter at the end or beginning of a frame, you get a new line
> that is extending the same frame. Wouldn't it be easier if you get a new
> frame this way and instead would just nest stuff in order to get it onto a
> specific frame? So, no need for separators either. There may be issues with
> this suggestion that I have not thought careful enough about but on the face
> of it, it seems like a good idea to me and to solve the issues you
> mentioned. What do you think?

I think the workflow you're suggesting makes the not-always-true assumption 
that the user does not use the "frame" layout for the *content* of the frame, 
and only uses nested layouts (e.g., itemize or standard). Did I understand 
right?

What abut making it so that if the user changes the layout to "frame title", 
then a *new* frame is started (i.e., LyX realizes "oh this frame already has a 
frame title so the user must want a new frame)?

Scott


signature.asc
Description: PGP signature
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Bibliography styles

2021-10-13 Thread Dr Eberhard Lisse

Because it is in the "label" (\cite key?)  field whereas (I assume
without having seen a MWE) the others are elsewhere ("author" field for
example).

From

 https://bibdesk.sourceforge.io/manual/BibDeskHelp_2.html

 Citation Keys

 A cite key is a unique identifier for a given reference.  BibTeX
 scans your document for occurrences of a cite command with a cite
 key embedded in it, and translates it into a properly formatted
 reference.  Several patterns are common in choosing cite keys, from
 simple ones such as "lastnameYEAR" to more complicated abbreviations
 of journal names and author names.  BibDesk will automatically
 generate cite keys for you (See section Citation Keys), or you can
 enter your own in the editor.

-->
 BibDesk takes a fairly strict interpretation of the valid characters
 for cite keys, and the characters " "@',\#}{~%" (including the space
 character) are never allowed, while you will be warned if you use
 one of "&$^" in a cite key.
<--

 Cite keys are essentially TeX commands, so you should avoid
 using underscores, for instance, if you ever need to print the
 actual cite key itself.

el

On 13/10/2021 14:54, Rich Shepard wrote:

On Wed, 13 Oct 2021, Dr Eberhard Lisse wrote:


IT. IS. THE. APOSTROPHE!


1. Then why is it only this one entry and not any of the other 9?

2. Why has this not been an issue before now? Is it biblatex-related and not
seen by bibtex?

3. If you're correct then how does one enter an apostrophy in an author's
name so it's properly written in both citation and bibliography?

You keep pointing out the source of the problem so I assume you have the
solution to it. I'd greatly appreciate learning that solution.

Rich


--
To email me replace 'nospam' with 'el'

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Compile error [FIXED]

2021-10-13 Thread Dr Eberhard Lisse

Rich,

the author field is not the same as the label field.

Perhaps it is enclosed by curly braces by default.  In which case, the
label field should thus also be, by default).

But it does make sense not to put Apostrophes into the labels.

greetings, el

On 13/10/2021 15:10, Rich Shepard wrote:

On Wed, 13 Oct 2021, Dr Eberhard Lisse wrote:

[...]

Actually, neither bibtex nor biblatex object to apostrophes or other
accents and umlauts, etc.  It's how they're entered and I had
completely forgotten how to do it properly until this morning and
recent caffinization.

The solution is to enclose the string in curly braces: {}.

Doing so for @article{{O'Connor2019}, removed that error (and revealed
a totally different complaint I'll deal with).  But, there were no
errors generated with these strings:

author = {Brooks, R.P. and O'Connell, T.J. and Wardrop, D.H. and Jackson, L.E.},
author = {O'Hagan, M.},

and the other seven apostrophes because the entire string in which it
occurs were enclosed in curly braces.

The initial entry name string had an opening curly brace but not a
closing one.

Being bright-eyed and bushy-tailed upon awakening, and having consumed
my first mug of coffee, allowed me to remember this.

Regards,

Rich


--
To email me replace 'nospam' with 'el'

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: END-OF-FRAME, once again..

2021-10-13 Thread Dr Eberhard Lisse

Neal,

thanks.

I am however now quite used to the LyX way and I hate ERT so I don't
think I'll change my template just yet.

For those who are interested it sits on

 https://github.com/gadmm/beamer-flex

greetings, el

On 13/10/2021 15:21, Neal Becker wrote:

I've found the LyX UI for beamer somewhat confusing.  At one time,
someone (I've forgotten who to credit here, sorry) contributed this
beamer-flx inset (attached).  I've been using it ever since.
Generally I find it more to my liking.  The only thing missing is it
lacks a direct way to add frame options.

[...]
--
To email me replace 'nospam' with 'el'

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: END-OF-FRAME, once again..

2021-10-13 Thread Neal Becker
I've found the LyX UI for beamer somewhat confusing.  At one time,
someone (I've forgotten who to credit here, sorry) contributed this
beamer-flx inset (attached).  I've been using it ever since.
Generally I find it more to my liking.  The only thing missing is it
lacks a direct way to add frame options.

On Wed, Oct 13, 2021 at 7:35 AM Dr Eberhard Lisse  wrote:
>
> I totally disagree :-)-O
>
> but then I have written recently about having a template and using that
> for presentations.
>
> greetings, el
>
> On 13/10/2021 00:32, UD K wrote:
> > On 10/12/21 7:49 PM, Steve Litt wrote:
> >> UD K said on Mon, 11 Oct 2021 17:47:46 +0200
> [...]
> >> I like LyX as much as the next guy --- I'm selling about 9 books
> >> authored in LyX. But when it comes to putting together a slide
> >> presentation with Beamer, I think LyX adds more complexity than it
> >> removes.  When I use Beamer at all, I just edit the LaTeX in an
> >> editor.  Doing that would be the kiss of death writing a book, but
> >> Beamer/LaTeX uses only a small subset of LaTeX.
> [...]
> > Steve-- I TOTALLY agree with you about the Lyx/Beamer combo being a
> > killjoy experience.  To make matters worse, I use this combination
> > only rarely, and in between, pandemics, Former-Presidents and other
> > plagues brush away what I knew about using it, so the experience is
> > usually like a root-canal: painful, frustrating and disappointing.  It
> > is harder to use than the much maligned Impress of the
> > even-more-maligned LibreOffice, but of course the output, if I ever
> > get to that stage, is MUCH better looking.  Whether that improved look
> > is worth the pain depends on your pain threshold ;-)
> [...]
>
> --
> To email me replace 'nospam' with 'el'
>
> --
> lyx-users mailing list
> lyx-users@lists.lyx.org
> http://lists.lyx.org/mailman/listinfo/lyx-users



-- 
Those who don't understand recursion are doomed to repeat it


beamer-flex.lyx
Description: application/lyx
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Compile error [FIXED]

2021-10-13 Thread Rich Shepard

On Wed, 13 Oct 2021, Dr Eberhard Lisse wrote:


Which part of 'change the label from "O'Connor" to "OConnor"' do you not
understand? Never mind the Minimal Working Example...

BibTeX does not like Apostropes "'" in the label names.


el,

Actually, neither bibtex nor biblatex object to apostrophes or other accents
and umlauts, etc. It's how they're entered and I had completely forgotten
how to do it properly until this morning and recent caffinization.

The solution is to enclose the string in curly braces: {}.

Doing so for @article{{O'Connor2019}, removed that error (and revealed a
totally different complaint I'll deal with). But, there were no errors
generated with these strings:
author = {Brooks, R.P. and O'Connell, T.J. and Wardrop, D.H. and Jackson, L.E.},
author = {O'Hagan, M.},
and the other seven apostrophes because the entire string in which it occurs
were enclosed in curly braces.

The initial entry name string had an opening curly brace but not a closing
one.

Being bright-eyed and bushy-tailed upon awakening, and having consumed my
first mug of coffee, allowed me to remember this.

Regards,

Rich
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Bibliography styles

2021-10-13 Thread Rich Shepard

On Wed, 13 Oct 2021, Dr Eberhard Lisse wrote:


IT. IS. THE. APOSTROPHE!


1. Then why is it only this one entry and not any of the other 9?

2. Why has this not been an issue before now? Is it biblatex-related and not
seen by bibtex?

3. If you're correct then how does one enter an apostrophy in an author's
name so it's properly written in both citation and bibliography?

You keep pointing out the source of the problem so I assume you have the
solution to it. I'd greatly appreciate learning that solution.

Rich
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Bibliography styles

2021-10-13 Thread Dr Eberhard Lisse

IT. IS. THE. APOSTROPHE!


On 12/10/2021 17:10, Rich Shepard wrote:

On Tue, 12 Oct 2021, Dr Eberhard Lisse wrote:


Change the label/reference to OConnor2019 :-)-O
BibDesk does not allow me to even enter a "'"


el,

$ grep -c -e "O'" documents/jabrefdb.bib 10

There are 10 entries begining with "O'" and none has before been an
issue.

Rich


--
To email me replace 'nospam' with 'el'

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: JabRef entry warning

2021-10-13 Thread Dr Eberhard Lisse

Paul,

this is why I am getting irritated at the (ie his) persistent lack of
sending in MWEs.  Having to go through this (and every time) borders on
the rude, and frustrates people like you (and me) who want to help.

A small file such as your dummy file, producing the error with the
required files allows anyone to just run the sucker and see where the
issue comes from.  Then one can also open the BIB file with another tool
(I like BibDesk on the Mac) and see what errors this flags.

I also find, when I have such an issue myself, reducing the file to
nothing else but the error producing text often makes me find the error
:-)-O

Never mind (him) sending in stuff with typos.

el

 12/10/2021 20:56, Paul A. Rubin wrote:
[...]

I turned your entry into a .bib file, cited it in a dummy document,
and compiled with biblatex.  It specifically flagged the first entry
that ended with a comma.  I think the "name" in the error message is
because it thinks that, after that last comma, there will be another
name = value pair in the field that it never finds (due to the closing
brace).  Not the ideal error message in my opinion, but deleting the
surplus comma did fix it.

I spotted the "and and" Maria flagged, but in my test that did not
cause an error message, it just mucked up the printed citation.

[...]

--
To email me replace 'nospam' with 'el'

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: END-OF-FRAME, once again..

2021-10-13 Thread Dr Eberhard Lisse

I totally disagree :-)-O

but then I have written recently about having a template and using that
for presentations.

greetings, el

On 13/10/2021 00:32, UD K wrote:

On 10/12/21 7:49 PM, Steve Litt wrote:

UD K said on Mon, 11 Oct 2021 17:47:46 +0200

[...]

I like LyX as much as the next guy --- I'm selling about 9 books
authored in LyX. But when it comes to putting together a slide
presentation with Beamer, I think LyX adds more complexity than it
removes.  When I use Beamer at all, I just edit the LaTeX in an
editor.  Doing that would be the kiss of death writing a book, but
Beamer/LaTeX uses only a small subset of LaTeX.

[...]

Steve-- I TOTALLY agree with you about the Lyx/Beamer combo being a
killjoy experience.  To make matters worse, I use this combination
only rarely, and in between, pandemics, Former-Presidents and other
plagues brush away what I knew about using it, so the experience is
usually like a root-canal: painful, frustrating and disappointing.  It
is harder to use than the much maligned Impress of the
even-more-maligned LibreOffice, but of course the output, if I ever
get to that stage, is MUCH better looking.  Whether that improved look
is worth the pain depends on your pain threshold ;-)

[...]

--
To email me replace 'nospam' with 'el'

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Compile error

2021-10-13 Thread Dr Eberhard Lisse

Rich,

Which part of 'change the label from "O'Connor" to "OConnor"' do you not
understand? Never mind the Minimal Working Example...

BibTeX does not like Apostropes "'" in the label names.

el

On 12/10/2021 21:41, Rich Shepard wrote:
[...]


Now I still have biber complaining about the O'Conner article in the .bib
file, That's a warning and doesn't prevent the file from compiling ...
maybe ... but there's still no bibiolgraphy in the complied PDF. That needs
fixing.

[...]


--
To email me replace 'nospam' with 'el'

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: END-OF-FRAME, once again..

2021-10-13 Thread Dr Eberhard Lisse

Ehud,

the best thing is to have both current.

I work on Macs and do a daily update (of MacTeX, Homebrew (which will
get me the latest LyX, Perl, Python, R and RStudio), pip (package
installer for Python :-)-O), CPAN and R (modules)) by way of a rather
hefty function in my (bash) aliases file :-)-O

greetings, el

On 13/10/2021 00:42, UD K wrote:



On 10/12/21 4:54 PM, Dr Eberhard Lisse wrote:

Ehud,

 https://www.google.com/search?q=%22MX+Linux%22+latex

returns 89 results of which the first one

 https://forum.mxlinux.org/viewtopic.php?t=59086

gives a hint at how to get a TexLive installed.

As it is Debian based, there are dummy packages for TexLive somewhere.

el

On 11/10/2021 21:50, UD K wrote:
[...]

This is punishment for using something called MX Linux, which has
only that antiquated version, without this needed feature.

[...]

EL-- My problem with MX Linux was installing a more recent version of
Lyx, not TexLive, which I have installed and used.



--
To email me replace 'nospam' with 'el'

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: END-OF-FRAME, once again..

2021-10-13 Thread Daniel

On 13/10/2021 00:32, UD K wrote:

On 10/12/21 7:49 PM, Steve Litt wrote:

UD K said on Mon, 11 Oct 2021 17:47:46 +0200


I SHOULD know this, because it came up in the (distant) past, but
either I forgot, or Lyx has changed-- probably a little of both.
    I wanted to cut a frame from a lyx/beamer presentation and put it
in
another place in the presentation. Control-X, and Control-V failed. So
I tried to insert a new frame, but that came without an end-of-frame,

I like LyX as much as the next guy --- I'm selling about 9 books
authored in LyX. But when it comes to putting together a slide
presentation with Beamer, I think LyX adds more complexity than it
removes. When I use Beamer at all, I just edit the LaTeX in an editor.
Doing that would be the kiss of death writing a book, but Beamer/LaTeX
uses only a small subset of LaTeX.

SteveT

Steve Litt
Spring 2021 featured book: Troubleshooting Techniques of the Successful
Technologisthttp://www.troubleshooters.com/techniques
Steve-- I TOTALLY agree with you about the Lyx/Beamer combo being a 
killjoy experience.  To make matters worse, I use this combination only 
rarely, and in between, pandemics, Former-Presidents and other plagues 
brush away what I knew about using it, so the experience is usually like 
a root-canal: painful, frustrating and disappointing. It is harder to 
use than the much maligned Impress of the even-more-maligned 
LibreOffice, but of course the output, if I ever get to that stage, is 
MUCH better looking.  Whether that improved look is worth the pain 
depends on your pain threshold ;-)


--
Ehud Kaplan, Ph.D.


Hi,

It's always great to get feedback on LyX.

Something that I thought while using beamer with LyX was that it seems 
that it would be easier if Frames would not "hang together". I mean: 
right now, if you press enter at the end or beginning of a frame, you 
get a new line that is extending the same frame. Wouldn't it be easier 
if you get a new frame this way and instead would just nest stuff in 
order to get it onto a specific frame? So, no need for separators 
either. There may be issues with this suggestion that I have not thought 
careful enough about but on the face of it, it seems like a good idea to 
me and to solve the issues you mentioned. What do you think?


Best,
Daniel

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: END-OF-FRAME, once again..

2021-10-13 Thread Wolfgang Engelmann



Am 13.10.21 um 01:12 schrieb Rich Shepard:

On Wed, 13 Oct 2021, UD K wrote:


Steve-- I TOTALLY agree with you about the Lyx/Beamer combo being a
killjoy experience.  To make matters worse, I use this combination only
rarely, and in between, pandemics, Former-Presidents and other plagues
brush away what I knew about using it, so the experience is usually 
like a

root-canal: painful, frustrating and disappointing. It is harder to use
than the much maligned Impress of the even-more-maligned LibreOffice, but
of course the output, if I ever get to that stage, is MUCH better
looking.  Whether that improved look is worth the pain depends on your
pain threshold ;-)


Ehud,

There are other LaTeX presentation tools. But, I do is copy an existing
beamer-class .lyx file to a new presentation's name then modify the new
file. I'll remove frames, enter new titles and contents, and use the same
Settings that worked in the past.

May not be pretty but it works.


Same with me. I copy/paste a frame using the mouse and insert it 
wherever I need a similar frame, e.g. a graphic. The label of the figure 
will be changed to xx-1, which I alter with a new adequate label. 
Exchanging the graphic and the legend will do it.

Wolfgang



Rich

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users