Re: Export child document to pdf2 from command line
On 8/23/19 4:32 PM, Rudi Gaelzer wrote: > > Is putting each of your child documents in a separate branch a > possibility? That way you could use the solution you found. I'm not > aware of a different approach (maybe someone else knows though). > > Yes, I thought of trying that, although some people reported > difficulties exporting branches. > I've found another solution where the guy edited the .lyx file with > sed first and then exported to PDF. > > I just wanted to know if there is a simpler way... Not at the moment, but it's a reasonable request. We'd need something like "child-in(ex)clude FILE.lyx" as an LFUN. Riki
Re: Export child document to pdf2 from command line
> > Is putting each of your child documents in a separate branch a > possibility? That way you could use the solution you found. I'm not > aware of a different approach (maybe someone else knows though). > > Yes, I thought of trying that, although some people reported difficulties exporting branches. I've found another solution where the guy edited the .lyx file with sed first and then exported to PDF. I just wanted to know if there is a simpler way... -- Rudi Gaelzer Institute of Physics Federal University of Rio Grande do Sul BRAZIL Registered linux user # 153741
Re: Export child document to pdf2 from command line
On Fri, Aug 23, 2019 at 05:10:44PM -0300, Rudi Gaelzer wrote: > I have a multi-part document with chapters that are included as child > documents. I can successfully export the whole document to PDF in a > terminal using the standard way given in the ImportExport FAQ in WikiLyX: > > lyx --export pdf2 master.lyx > > Now, if I want to export only some of the childs to PDF, is there a > standard way to accomplish this? > The only other relevant instruction in the FAQ is related to branches: > > lyx -x "command-sequence branch-activate b1; branch-deactivate b2" -E pdf2 > outfile.pdf infile.lyx > > but I don't think it applies to my case. Is putting each of your child documents in a separate branch a possibility? That way you could use the solution you found. I'm not aware of a different approach (maybe someone else knows though). Best, Scott signature.asc Description: PGP signature
Export child document to pdf2 from command line
I have a multi-part document with chapters that are included as child documents. I can successfully export the whole document to PDF in a terminal using the standard way given in the ImportExport FAQ in WikiLyX: lyx --export pdf2 master.lyx Now, if I want to export only some of the childs to PDF, is there a standard way to accomplish this? The only other relevant instruction in the FAQ is related to branches: lyx -x "command-sequence branch-activate b1; branch-deactivate b2" -E pdf2 outfile.pdf infile.lyx but I don't think it applies to my case. -- Rudi Gaelzer Institute of Physics Federal University of Rio Grande do Sul BRAZIL Registered linux user # 153741
Re: KOMA-Script report: old font issue with bibtex
On Fri, 23 Aug 2019, Johannes Böttcher wrote: KOMA-Script got rid of the old font commands. Use the document option "enabledeprecatedfontcommands" (from memory) Johannes, I had that as a class type option, but it broke other things. Because this appeared only after I added a citation/reference pair from JabRef, and the LaTeX error shows those deprecated font commands associated with the reference's author and volumn values I believe it's how JabRef presents it to LyX/LaTeX. I don't see those codes in the reference database. The JabRef export formats seem to be different from how the application presents the reference to the document so I suspect it's JabRef related. Thanks for your suggestion, Rich
Re: KOMA-Script report: old font issue with bibtex
KOMA-Script got rid of the old font commands. Use the document option "enabledeprecatedfontcommands" (from memory) This is not a LyX nor a JabRef question. On Fri, 23 Aug 2019, 19:05 Rich Shepard, wrote: > On Fri, 23 Aug 2019, Rich Shepard wrote: > > > It's either LaTeX or JabRef changing how it presents the bibtex entry to > > lyx. > > This is most likely a JabRef issue so I've posted a question on their web > forum about this and other changes. > > Regards, > > Rich >
Re: KOMA-Script report: old font issue with bibtex
On Fri, 23 Aug 2019, Rich Shepard wrote: It's either LaTeX or JabRef changing how it presents the bibtex entry to lyx. This is most likely a JabRef issue so I've posted a question on their web forum about this and other changes. Regards, Rich
Re: KOMA-Script report: old font issue with bibtex
On Fri, 23 Aug 2019, Dr Eberhard Lisse wrote:
It's a LaTeX one, or rather a BST one and you need to look at the BST what
it shows there.
Eberhard,
It's either LaTeX or JabRef changing how it presents the bibtex entry to
lyx.
Look for something like (from another style):
FUNCTION {emphasize}
{ duplicate$ empty$
{ pop$ "" }
{ "\emph{" swap$ * "}" * }
if$
}
It's not the emphasis as nothing in the document is emphasized; the error
appeared only after I added that one citation and the reference was added to
the bibliography.
but search for the old ones, of course, ie \bf, \sc and so on...
I grep'd the .lyx file for those strings and found none.
Thanks,
Rich
Re: Missing lyxeditor.cmd?
I can not confirm this. I am a long time LyX user in production (I seem to have switched from OpenOffice to LyX in 2005 according to what I can find in my operating reports directory), regularly updating LyX and MacOs, and on an number of different boxes (from iMini via the trashcan MacPro to a 5k iMac) and laptops (12 and 13 inch airs). The only issue I am having sometimes is LuaLaTeX being 3 times slower than pdfLaTeX but of course it is the future :-)-O and there are many ways around some of it. Is there a way of measuring the startup time of a Mac application? greetings, el On 22/08/2019 19:08, Chris Menzel wrote: [...] > I'm not really a Windows user either, but I got so irked with recent > Mac laptops that I bought the (quite lovely) Dell in a fit of pique. > I have to say that, once you get it set up right, LyX under Windows > (and Linux) works rather better than it does under macOS. It loads > *much *faster and just seems snappier all around; forward/inverse > searching in particular is faster and more accurate. (Both startup > and forward search on macOS have been glacial under the last few > iterations, though they're improved in 2.3.3.) [...] -- Dr. Eberhard W. Lisse / Obstetrician & Gynaecologist (Saar) e...@lisse.na/ * | Telephone: +264 81 124 6733 (cell) PO Box 8421 / Bachbrecht, Namibia ;/
Re: KOMA-Script report: old font issue with bibtex
Rich,
this is not a MWE, it requires gensymb.sty and a BST which I didn't have.
This is not a LyX issue
It's a LaTeX one, or rather a BST one and you need to look at the BST what
it shows there.
Look for something like (from another style):
FUNCTION {emphasize}
{ duplicate$ empty$
{ pop$ "" }
{ "\emph{" swap$ * "}" * }
if$
}
but search for the old ones, of course, ie \bf, \sc and so on...
el
On 22/08/2019 23:16, Rich Shepard wrote:
> Strange situation here and I do not see where to fix it.
>
> I use JabRef-4.3.1 for my references. I've created a new KOMA-Script report
> and used the JabRef -> LyX icon to insert a reference and bibliography
> reference. As a test I tried to preview the document only to have lyx tell
> me there are deprecated font types, e.g., \sc, in the bibtex entry.
>
> Looking at the bibtex entry in JabRef I see expected ASCII text in bibtex
> format. I tried exporting that entry but did not find a format that printed
> in plain ASCII text. Sigh.
>
> Here's the last few lines from lyx error log:
>
> ! Class scrreprt Error: undefined old font command `\bf'.
>
> See the scrreprt class documentation for explanation.
> Type H for immediate help.
> ...
>
> l.7 ...l of Fisheries and Aquatic Sciencess}, {\bf
> 37},
>
> The entire log is attached; so is a MWE. If I need to send the actual JabRef
> entry I'll figure out how to provide that in a useful format.
>
> In LyX the citation type is authordate3.
>
> Looking at the document's .lyx file I don't see the bibiographic entry at
> all.
>
> Rich
