On Sat, Apr 05, 2025 at 01:51:57PM +0200, Jürgen Spitzmüller wrote:
> Am Samstag, dem 05.04.2025 um 11:49 +0200 schrieb Scott Kostyshak:
> > On one of my documents I get the following warning:
> >
> > Package biblatex Warning: 'babel/polyglossia' dete
Am Samstag, dem 05.04.2025 um 11:49 +0200 schrieb Scott Kostyshak:
> On one of my documents I get the following warning:
>
> Package biblatex Warning: 'babel/polyglossia' detected but
> 'csquotes' missing.
>
> Should we load csquotes whenever using bibl
On one of my documents I get the following warning:
Package biblatex Warning: 'babel/polyglossia' detected but 'csquotes' missing.
Should we load csquotes whenever using biblatex and either babel or
polyglossia?
I can make a minimal example in case it would be useful.
S
with
> > Welcome.lyx), a few lines keep being added. e.g., after a few
> > roundtrips
> > we get the following:
> >
> > Provides natbib 1
> > ### End of insertion by lyx2lyx (biblatex emulation) ###
> > ### Inserted by lyx2lyx (biblatex emulation) #
ps
> we get the following:
>
> Provides natbib 1
> ### End of insertion by lyx2lyx (biblatex emulation) ###
> ### Inserted by lyx2lyx (biblatex emulation) ###
Fixed.
--
Jürgen
signature.asc
Description: This is a digitally signed message part
--
lyx-devel mailing lis
On Tue, Jul 09, 2024 at 01:19:14PM GMT, Juergen Spitzmueller wrote:
> commit 8941b05774b1891ca9566eab3cefba17e0f2bbe4
> Author: Juergen Spitzmueller
> Date: Tue Jul 9 15:18:06 2024 +0200
>
> Add support for biblatex-chicago (#12240)
>
> File format change
Am Sonntag, dem 19.02.2023 um 09:51 -0300 schrieb Hernán Gustavo
Solari:
> CASE:
> I wanted to change the wrong translation of "et al." into "y Col."
> that biblatex makes (et al. stands for "et alter" which is not
> English
> but Latin and should
preamble of
commands defined in the other menus.
CASE:
I wanted to change the wrong translation of "et al." into "y Col."
that biblatex makes (et al. stands for "et alter" which is not English
but Latin and should not be translated, it should be used in La
Am Mittwoch, dem 31.08.2022 um 13:56 +0100 schrieb madmurphy:
> I wanted to use the biblatex-chicago package instead of the plain
> biblatex, but it appeared harder to do than I thought. After digging
> around a bit I found out that three years ago someone wanted to do
> the sam
Thank you, Jürgen.
It really needs a closer look. I just took the biblatex-natbib.citeengine
file, made a few hacks for loading the right package (biblatex-chicago) and
that's it – that's all I needed for my document. But it is definitely a
must-have feature for LyX.
--madmurphy
On
Am Mittwoch, dem 31.08.2022 um 13:56 +0100 schrieb madmurphy:
> I wanted to use the biblatex-chicago package instead of the plain
> biblatex, but it appeared harder to do than I thought. After digging
> around a bit I found out that three years ago someone wanted to do
> the sam
I wanted to use the biblatex-chicago package instead of the plain biblatex,
but it appeared harder to do than I thought. After digging around a bit I
found out that three years ago someone wanted to do the same
<https://www.mail-archive.com/lyx-cvs@lists.lyx.org/msg19452.html>. So I
have c
to appear. Rich was using
biblatex. After copies trial and error, Rich got the report to work,
but with no explanation why.
I was beating on a copy of it (which I am not at liberty to share) and
discovered that if made any non-fatal change to the preamble, the
bibliography would show up. In partic
On Mon, Jun 01, 2020 at 05:12:24PM +0200, Jürgen Spitzmüller wrote:
> Am Montag, den 01.06.2020, 09:07 -0400 schrieb Scott Kostyshak:
> > Ah indeed. Would it be reasonable for me to open a feature request at
> > Biblatex to only give the warning when it is necessary to run Biber?
Am Montag, den 01.06.2020, 09:07 -0400 schrieb Scott Kostyshak:
> Ah indeed. Would it be reasonable for me to open a feature request at
> Biblatex to only give the warning when it is necessary to run Biber?
Or write a bcf file only if necessary.
Jürgen
>
> Scott
signature.asc
On Mon, Jun 01, 2020 at 08:44:12AM +0200, Jürgen Spitzmüller wrote:
> Am Sonntag, den 31.05.2020, 10:09 -0400 schrieb Scott Kostyshak:
> > I just noticed the following message:
> >
> > Package biblatex Warning: Please (re)run Biber on the file:
> > (bib
Am Sonntag, den 31.05.2020, 10:09 -0400 schrieb Scott Kostyshak:
> I just noticed the following message:
>
> Package biblatex Warning: Please (re)run Biber on the file:
> (biblatex) paper
> (biblatex)and rerun LaTeX afterwards.
>
> Whe
018 and Jürgen's answer
> > (https://marc.info/?l=lyx-devel&m=153899371502800&w=2) contained the extra
> > wrinkle:
> >
> > Currently, we run biber whenever a *.bcf file exists in the tmp dir.
> > This is apparently also the case if there are no citations.
On Fri, May 29, 2020 at 10:10:12PM +1200, Andrew Parsloe wrote:
> On 29/05/2020 5:54 pm, Jürgen Spitzmüller wrote:
> > Am Donnerstag, den 28.05.2020, 23:10 -0400 schrieb Scott Kostyshak:
> > > I don't know if this is expected or not. Is the bibliography
> > > generator
> > > still run because there
On 29/05/2020 5:54 pm, Jürgen Spitzmüller wrote:
Am Donnerstag, den 28.05.2020, 23:10 -0400 schrieb Scott Kostyshak:
I don't know if this is expected or not. Is the bibliography
generator
still run because there might be references in the .tex file itself
(i.e., not in an external file)? If that
Am Donnerstag, den 28.05.2020, 23:10 -0400 schrieb Scott Kostyshak:
> I don't know if this is expected or not. Is the bibliography
> generator
> still run because there might be references in the .tex file itself
> (i.e., not in an external file)? If that is the case, would it make
> sense to condi
a new document.
2. Type "abc".
3. Change Document > Settings > Bibliography > Style format to "Biblatex".
4. Click "OK".
5. View with PDF (pdflatex).
I get the following in the terminal:
This is pdfTeX, Version 3.14159265-2.6-1.40.20 (TeX Live 2019) (preloaded
for
t;>> Author: Juergen Spitzmueller
> >>> Date: Tue May 7 14:48:39 2019 +0200
> >>>
> >>> Enable optional \cite* arguments in biblatex-natbib
> >> This is a candidate for stable, Riki.
> > Riki? I think this is safe enough for 2.3.3.
>
> OK then.
>
Thanks, done.
Jürgen
>
> Riki
>
>
>
>> Enable optional \cite* arguments in biblatex-natbib
>> This is a candidate for stable, Riki.
> Riki? I think this is safe enough for 2.3.3.
OK then.
Riki
Am Dienstag, den 07.05.2019, 14:51 +0200 schrieb Jürgen Spitzmüller:
> > commit 6a4199ed233e5a9fe7fa0fbfd0266cd29560951b
> > Author: Juergen Spitzmueller
> > Date: Tue May 7 14:48:39 2019 +0200
> >
> > Enable optional \cite* arguments in biblatex-natbib
>
> commit 6a4199ed233e5a9fe7fa0fbfd0266cd29560951b
> Author: Juergen Spitzmueller
> Date: Tue May 7 14:48:39 2019 +0200
>
> Enable optional \cite* arguments in biblatex-natbib
>
This is a candidate for stable, Riki.
Jürgen
> ---
> lib/citeengines/biblatex-
Am Mi., 31. Okt. 2018 um 08:42 Uhr schrieb Yevgeny Bar Lev <
ykrivola...@gmail.com>:
> Hi spitz,
> I think you misunderstood me. It's a bit hard to provide a minimal
> example, since the bug is a bit erratic and hard to reproduce.
>
> I have noted that some of the multicites are compressed [1-3] a
and indeed solves the issue.
If I had to guess the bug has something to do with the citation insertion
dialog in LyX.
Hope it helps.
On Wed, Oct 31, 2018, 8:40 AM LyX Ticket Tracker #11357: Biblatex inserts posttext command on multiple citation
> --+---
On Fri, May 11, 2018 at 10:09 PM, Richard Kimberly Heck
wrote:
> On 05/11/2018 11:44 PM, Joel Kulesza wrote:
>
> LyX Developers,
>
> As I'm writing my dissertation, I've been using LyX 2.2.3 but today
> decided to try migrating it to 2.3.0. Upon doing so, I encountered what
> appears to be a reg
On 05/11/2018 11:44 PM, Joel Kulesza wrote:
> LyX Developers,
>
> As I'm writing my dissertation, I've been using LyX 2.2.3 but today
> decided to try migrating it to 2.3.0. Upon doing so, I encountered
> what appears to be a regression (or else I've been doing something
> invalid all along that 2
On Thu, Apr 05, 2018 at 07:16:41AM +, R H van der Gaag wrote:
> Hi, I’ll be glad to, but what would qualify as an ‘example file’?
> H.
In this case, it would be a minimal .lyx file and a .bib file (if
necessary), along with steps to reproduce (e.g. 1. compile, 2. go to
Document > Settings > Bi
at simply switching from natbib to biblatex or
> > biblatex (natbib style) doesn’t work out of the box. Parsing errors
> > abound.
>
> Please provide an example file for those errors.
R H, can you provide an example file for what you mentioned above?
Thanks,
Scott
On Sun, Mar 18, 2018 at 02:53:22PM +, Jürgen Spitzmüller wrote:
> Am Sonntag, den 18.03.2018, 14:47 +0100 schrieb R H van der Gaag:
> > Also, I found that simply switching from natbib to biblatex or
> > biblatex (natbib style) doesn’t work out of the box. Parsing er
s > Edit >
Sortcits; the respective funtions are quote-insert and quote-insert
inner)
> Also, I found that simply switching from natbib to biblatex or
> biblatex (natbib style) doesn’t work out of the box. Parsing errors
> abound.
Please provide an example file for those errors.
On 2018-03-18, R H van der Gaag wrote:
> Hi, Thanks a lot for the new version! It’s very much appreciated.
> I find that o pening single quotation marks are not converted to their
> curly version (UK English default).
How do you insert them?
> The closing ones are, and the double opening and
hit
` like in the old days.
Also, I found that simply switching from natbib to biblatex or biblatex (natbib
style) doesn’t work out of the box. Parsing errors abound.
Kind regards, R H van der Gaag
2018-03-06 13:52 GMT+01:00 Uwe Stöhr :
> commit 150fb89e22742dcf1f61500b498bc9e7e2a7702c
> Author: Uwe Stöhr
> Date: Tue Mar 6 13:52:42 2018 +0100
>
> status.23x: mention the new biblatex support in tex2lyx
>
I actually added an note (further down). There is no need
On 03/05/2018 07:03 AM, Pavel Sanda wrote:
> Jean-Marc Lasgouttes wrote:
>> I thought 2.3.1 was supposed to be either for urgent stuff or just be
>> merged with 2.3.2. No I do not know...
> My understanding was similar, i.e. 2.3.2-staging will be actually merged
> into 2.3.1 if there is no immedia
On 03/05/2018 03:37 AM, Jürgen Spitzmüller wrote:
> Am Montag, den 05.03.2018, 09:32 +0100 schrieb Jean-Marc Lasgouttes:
>> I thought 2.3.1 was supposed to be either for urgent stuff or just
>> be
>> merged with 2.3.2. No I do not know...
> I thought, since 2.3.1-staging does not contains really u
support qualified citation lists (biblatex)
> This one's rather 2.3.2 stuff.
OK.
r
2lyx: refsection and bibbysection support (biblatex)
> Candidate for 2.3.1.
OK.
rh
Jean-Marc Lasgouttes wrote:
> I thought 2.3.1 was supposed to be either for urgent stuff or just be
> merged with 2.3.2. No I do not know...
My understanding was similar, i.e. 2.3.2-staging will be actually merged
into 2.3.1 if there is no immediate 2.3.1 release fixing some urgent problem...
Pa
Am Montag, den 05.03.2018, 09:32 +0100 schrieb Jean-Marc Lasgouttes:
> I thought 2.3.1 was supposed to be either for urgent stuff or just
> be
> merged with 2.3.2. No I do not know...
I thought, since 2.3.1-staging does not contains really urgent stuff,
that 2.3.1 is released with urgent fixes (b
Le 05/03/2018 à 07:48, Jürgen Spitzmüller a écrit :
Am Sonntag, den 04.03.2018, 21:02 +0100 schrieb Jean-Marc Lasgouttes:
Why not 2.3.1?
Jürgen
It is supposed to be for urgent matters.
But 2.3.1-staging contains many non-urgent matters already. I think it
tex2lyx support for the most antic
Am Sonntag, den 04.03.2018, 21:02 +0100 schrieb Jean-Marc Lasgouttes:
> > Why not 2.3.1?
> >
> > Jürgen
> >
>
> It is supposed to be for urgent matters.
But 2.3.1-staging contains many non-urgent matters already. I think it
tex2lyx support for the most anticipated new feature of 2.3.x is
import
Le 4 mars 2018 19:44:23 GMT+01:00, "Jürgen Spitzmüller" a écrit
:
>Am Sonntag, den 04.03.2018, 18:52 +0100 schrieb Jean-Marc Lasgouttes:
>> > Candidate for 2.3.1.
>>
>> Why not 2.3.2?
>
>Why not 2.3.1?
>
>Jürgen
It is supposed to be for urgent matters.
JMarc
Am Sonntag, den 04.03.2018, 20:12 +0100 schrieb Juergen Spitzmueller:
> commit 0915e814814ab26732b6dd13fc1740cfbf64b5b4
> Author: Juergen Spitzmueller
> Date: Sun Mar 4 20:12:27 2018 +0100
>
> tex2lyx: support qualified citation lists (biblatex)
This one's rather
Am Sonntag, den 04.03.2018, 18:52 +0100 schrieb Jean-Marc Lasgouttes:
> > Candidate for 2.3.1.
>
> Why not 2.3.2?
Why not 2.3.1?
Jürgen
signature.asc
Description: This is a digitally signed message part
Le 04/03/2018 à 16:51, Jürgen Spitzmüller a écrit :
Am Sonntag, den 04.03.2018, 16:48 +0100 schrieb Juergen Spitzmueller:
commit f22213a04fe53dd128f11db9b228623b3fc3dda7
Author: Juergen Spitzmueller
Date: Sun Mar 4 16:46:31 2018 +0100
tex2lyx: support biblatex
(qualified
Am Sonntag, den 04.03.2018, 17:30 +0100 schrieb Juergen Spitzmueller:
> commit 1a3dbbf07ad837a685af93bf3d1d1a784e0d27ae
> Author: Juergen Spitzmueller
> Date: Sun Mar 4 17:29:59 2018 +0100
>
> tex2lyx: refsection and bibbysection support (biblatex)
Candidate for
Am Sonntag, den 04.03.2018, 16:48 +0100 schrieb Juergen Spitzmueller:
> commit f22213a04fe53dd128f11db9b228623b3fc3dda7
> Author: Juergen Spitzmueller
> Date: Sun Mar 4 16:46:31 2018 +0100
>
> tex2lyx: support biblatex
>
> (qualified citation lists and multi
On Sun, Feb 11, 2018 at 04:06:27PM +, Jürgen Spitzmüller wrote:
> Am Sonntag, den 11.02.2018, 16:45 +0100 schrieb Juergen Spitzmueller:
> > commit 6c455707fe39a28edab8631d6ff973969b368bb1
> > Author: Juergen Spitzmueller
> > Date: Sun Feb 11 16:43:14 2018 +0100
Am Sonntag, den 11.02.2018, 16:45 +0100 schrieb Juergen Spitzmueller:
> commit 6c455707fe39a28edab8631d6ff973969b368bb1
> Author: Juergen Spitzmueller
> Date: Sun Feb 11 16:43:14 2018 +0100
>
> biblatex-natbib.citeengine: Remove erroneous blank
Scott, I took the liberty
On Tue, Dec 26, 2017 at 10:13:57AM +, Jürgen Spitzmüller wrote:
> OK, but this is due to the switch from simple (numerical) BibTeX that
> produces \cite references. These are defined differently in Natbib and
> Biblatex, and it is impossible to solve this without change in one
ment Settings, change to "Natbib (BibTeX)" (leave as
> Author-Year). Press OK.
>
> Notice that the first citation in the LyX display is "Bringhurst
> (2005)".
>
> 4. In Document Settings, change to "Biblatex", or "Biblatex (Natbib
> mode)&
On Sun, Dec 24, 2017 at 11:19:49AM +, Jürgen Spitzmüller wrote:
> Am Sonntag, den 24.12.2017, 00:16 -0500 schrieb Scott Kostyshak:
> > If I copy a citation of the form "author (year)" from a .lyx file
> > that
> > uses BibTeX to a .lyx file that uses Biblatex,
On 12/24/2017 06:19 AM, Jürgen Spitzmüller wrote:
> Am Sonntag, den 24.12.2017, 00:16 -0500 schrieb Scott Kostyshak:
>> If I copy a citation of the form "author (year)" from a .lyx file
>> that
>> uses BibTeX to a .lyx file that uses Biblatex, it shows up as &quo
Am Sonntag, den 24.12.2017, 00:16 -0500 schrieb Scott Kostyshak:
> If I copy a citation of the form "author (year)" from a .lyx file
> that
> uses BibTeX to a .lyx file that uses Biblatex, it shows up as "author
> year". Should we improve this or would the compl
If I copy a citation of the form "author (year)" from a .lyx file that
uses BibTeX to a .lyx file that uses Biblatex, it shows up as "author
year". Should we improve this or would the complication not be worth it?
Scott
signature.asc
Description: PGP signature
Am Mittwoch, den 20.12.2017, 16:05 -0500 schrieb Scott Kostyshak:
> OK let me know if you want me to work on that.
Don't hold your breath.
>
> > OTOH we only support Biblatex officially as of 2.3. So I think it's
> > OK
> > if reversion is not perfect.
>
> is to leave things as they are.
>
> As said I doubt we have access to lyxrc from lyx2lyx. In any case, we
> cannot provide a 100% failsafe reversion.
Agreed.
> Most probably assuming biber
> when the buffer param is default is the most expectable case.
OK let me know if you w
iber
when the buffer param is default is the most expectable case.
OTOH we only support Biblatex officially as of 2.3. So I think it's OK
if reversion is not perfect.
Jürgen
> Thanks,
>
> Scott
>
>
> [1]
> https://www.mail-archive.com/search?l=mid&q=20170601200718.uhrruumcnq
> ppkhai%40steph
signature.asc
Description: This is a digitally signed message part
On Wed, Dec 20, 2017 at 09:44:13AM +, Jürgen Spitzmüller wrote:
> Am Dienstag, den 19.12.2017, 23:13 -0500 schrieb Scott Kostyshak:
> > When using Biblatex and exporting to 2.2.x, I think we need to set
> > the
> > bibliography processor to biber, right?
>
> Not unc
Am Dienstag, den 19.12.2017, 23:13 -0500 schrieb Scott Kostyshak:
> When using Biblatex and exporting to 2.2.x, I think we need to set
> the
> bibliography processor to biber, right?
Not uncoditionally. Biblatex still also runs with backend=bibtex and
backend=bibtex8.
We should not
On Wed, Dec 20, 2017 at 04:41:18AM +, Richard Heck wrote:
> On 12/19/2017 11:13 PM, Scott Kostyshak wrote:
> > When using Biblatex and exporting to 2.2.x, I think we need to set the
> > bibliography processor to biber, right?
> >
> > I'm guessing this wasn&
On 12/19/2017 11:13 PM, Scott Kostyshak wrote:
> When using Biblatex and exporting to 2.2.x, I think we need to set the
> bibliography processor to biber, right?
>
> I'm guessing this wasn't caught before because a lot of testers have
> biber set in preferences.
>
>
When using Biblatex and exporting to 2.2.x, I think we need to set the
bibliography processor to biber, right?
I'm guessing this wasn't caught before because a lot of testers have
biber set in preferences.
Attached is a patch. It works well for me, but I am not very familiar
with lyx2l
> is the default.
> >>
> >> Do we want to eventually change this to use Biblatex by default?
> >
> > I would not do that (even though I am personally using nothing else).
> > It is easy to switch it on, and I think it makes sense to have
> > something that do
Jürgen Spitzmüller wrote:
> Am Dienstag, den 19.12.2017, 01:26 -0500 schrieb Scott Kostyshak:
>> When the user goes to Document > Settings > Bibliography, Basic
>> (BibTeX)
>> is the default.
>>
>> Do we want to eventually change this to use Biblatex by
Am Dienstag, den 19.12.2017, 01:26 -0500 schrieb Scott Kostyshak:
> When the user goes to Document > Settings > Bibliography, Basic
> (BibTeX)
> is the default.
>
> Do we want to eventually change this to use Biblatex by default?
I would not do that (even though I am per
When the user goes to Document > Settings > Bibliography, Basic (BibTeX)
is the default.
Do we want to eventually change this to use Biblatex by default?
I know close to nothing bout Biblatex, but from what I've read it is
more extensible and under more active development.
To be cle
LyX Developers:
I installed 2.3.0a1 for testing and am having a problem with Biblatex that
appears to be driven by it being a recent, but not latest, version. This
older version is served by MacPorts with no newer version apparently
available.
See https://www.lyx.org/trac/ticket/10654.
If you
2017-01-16 15:57 GMT+01:00 PhilipPirrip :
> Oh, I see. This should be in Tools>Preferences I guess since it's not
> document-specific (is it being saved with the document?)
> LyX could even remember the last value chosen for the bibtex inset.
>
No, it's document specific, since it depends on the
On 01/15/2017 09:14 AM, Jürgen Spitzmüller wrote:
This is an old feature. If you enter "default" in the bibliography
style widget (in the BibTeX dialog), then this is replaced with this
"Default bibtex style".
I did not change this behavior, although I think the UI is sub-optimal.
Oh, I see.
Am Sonntag, den 15.01.2017, 20:53 +0100 schrieb Jean-Marc Lasgouttes:
> Ditto. Do you have a pointer on propaganda for biblatex vs bibtex ?
The CTAN catalogue entry is telling enough:
http://www.ctan.org/pkg/biblatex
But of course it all depends on what features one needs.
Here's
> On Monday, 16 January 2017, 2:53, Jean-Marc Lasgouttes
> wrote:
> > Ditto. Do you have a pointer on propaganda for biblatex vs bibtex ?
>
> JMarc
Reading the section called "User Guide" p. 43 ff in the actual Biblatex
documentation will convey the sense of
On Sunday, 8 January 2017, 16:14, Jürgen Spitzmüller wrote:
>
>Biblatex support is ready over at the features/biblatex2 branch.
>
Great news! Thank you to all developers for the continual effort. This new
feature will certainly be a highlight.
Best wishes,
Sam
Ditto. Do you have a pointer on propaganda for biblatex vs bibtex ?
JMarc
Le 15 janvier 2017 20:06:45 GMT+01:00, Scott Kostyshak a
écrit :
>Another thank you from me. I have actually delayed learning biblatex
>since LyX hasn't supported it. Now I'm excited to eventually lear
> Thank you both. It caused me quite some headache, so I'm glad it works
> out.
Another thank you from me. I have actually delayed learning biblatex
since LyX hasn't supported it. Now I'm excited to eventually learn about
it and use it since it seems it is unambigiously the
Am Sonntag, den 15.01.2017, 08:29 -0500 schrieb PhilipPirrip:
> So this is yet another thing: what does "Default bibtex style" in
> Document Settings, Bibliography do? I don't see any change in latex
> code.
This is an old feature. If you enter "default" in the bibliography
style widget (in the B
Am Sonntag, den 15.01.2017, 07:49 -0500 schrieb PhilipPirrip:
> Next:
> open my childTwo.lyx alone. It's been set to use Natbib (BibTeX),
> and
> LaTeX code reflects that. But the "xxx generated bibliography" has
> xxx=Biblatex, and it's impossible to change
On 01/15/2017 08:16 AM, Kornel Benko wrote:
> Which dialog? I don't see problems in Document->Settings->bibliography
The dialog where you (normally/only) set the bibliography style: press
the "Biblatex generated bibliography" button. The field "Style" is
mis
Am Sonntag, 15. Januar 2017 um 07:49:41, schrieb PhilipPirrip
> Next:
> open my childTwo.lyx alone. It's been set to use Natbib (BibTeX), and
> LaTeX code reflects that. But the "xxx generated bibliography" has
> xxx=Biblatex, and it's impossible to change it to
Next:
open my childTwo.lyx alone. It's been set to use Natbib (BibTeX), and
LaTeX code reflects that. But the "xxx generated bibliography" has
xxx=Biblatex, and it's impossible to change it to what it's supposed to
be, xxx=Bibtex.
That also prevents one from changin
Am Sonntag, den 15.01.2017, 11:13 +0100 schrieb Kornel Benko:
> > This is exciting, Juergen!
> > Pavel
>
> I am playing with it now. It is amazing, very nice work.
> ++1
Thank you both. It caused me quite some headache, so I'm glad it works
out.
Jürgen
> Kornel
signature.asc
Description:
ent from, say, natbib to biblatex and
> > (to a limited degree, since the feature set is larger) back.
>
> This is exciting, Juergen!
> Pavel
I am playing with it now. It is amazing, very nice work.
++1
Kornel
signature.asc
Description: This is a digitally signed message part.
Am Samstag, den 14.01.2017, 07:39 -0500 schrieb PhilipPirrip:
> On 01/14/2017 05:39 AM, Jürgen Spitzmüller wrote:
> > I prefer to get them without jumping through such hoops.
>
> I'm sorry, I was switching from t'bird to some other news readdder.
> Attaching the files again.
Thanks! Should be fix
On 01/14/2017 05:39 AM, Jürgen Spitzmüller wrote:
I prefer to get them without jumping through such hoops.
I'm sorry, I was switching from t'bird to some other news readdder.
Attaching the files again.
childOne.lyx
Description: application/lyx
childTwo.lyx
Description: application/lyx
mas
Am Samstag, den 14.01.2017, 10:45 +0100 schrieb Kornel Benko:
> They did. How to get the data:
> 1.) save the mail to a file, e.g. /tmp/childOne.lyx
> 2.) use uudeview on that file (in another directory)
> ==> you get the undecoded childOne.lyx
I prefer to get them without jumping through su
Am Samstag, 14. Januar 2017 um 10:15:29, schrieb Jürgen Spitzmüller
> Am Freitag, den 13.01.2017, 20:17 + schrieb PhilipPirrip:
> > I'm reporting that the master document won't compile with a child
> > document containing some commands specific to natbib.
> > In the attached examples, it wil
Am Freitag, den 13.01.2017, 20:17 + schrieb PhilipPirrip:
> I'm reporting that the master document won't compile with a child
> document containing some commands specific to natbib.
> In the attached examples, it will be because of a citation command
> in
> childOne.lyx.
> Can this be transl
Am Freitag, den 13.01.2017, 19:32 + schrieb PhilipPirrip:
> Hope you don't mind if I report other findings here. Reporting on
> lyx.org
> bug tracker takes too much time:
No, that's perfect.
> New document. Choose biblatex in Document Settings. Insert an
> opt
Jürgen Spitzmüller wrote:
> I have put most energy into a design that enables portability between
> the diverse citation engines as much as possible, so it should be very
> easy to switch an existing document from, say, natbib to biblatex and
> (to a limited degree, since the feature s
if the child does not use biblatex
and its code contains bibtex commands \bibliographystyle and
\bibliography those won't be used when compiling the master document. All
good.
I'm reporting that the master document won't compile with a child
document containing some commands
=ybegin line=128 size=1856 name=childOne.lyx
Mv��J\X]J���JJXJp��JJJ���JdYY���X���X���Y4��J_]Z4���4�4�
�J4���J���4��J���4J4���J��X���4��
=ybegin line=128 size=1919 name=childTwo.lyx
Mv��J\X]J���JJXJp��JJJ���JdYY���X���X���Y4��J_]Z4���4�4�
�J4���J���4��J���4J4���J��X���4��
=ybegin line=128 size=2094 name=master.lyx
Mv��J\X]J���JJXJp��JJJ���JdYY���X���X���Y4��J_]Z4���4�4�
�J4���J���4��J���4J4�J�4�J�
o much time:
New document. Choose biblatex in Document Settings. Insert an option,
Apply. Delete the option - it remains in the arguments to biblatex call,
and it's back there when reopening the document.
Am Freitag, den 13.01.2017, 17:40 + schrieb PhilipPirrip:
> The biblatex settings dialog enters some undefined state when one
> - chooses Style engine Biblatex
> - changes, for example, Biblatex bibliography style field to some
> other
> value
> - presses either of the tw
Am Freitag, den 13.01.2017, 12:32 -0500 schrieb Richard Heck:
> On 01/13/2017 12:29 PM, PhilipPirrip wrote:
> > This is probably more of a general issue: when *master* is set to
> > use
> > biblatex, and a child hasn't been changed to use biblatex as well
> > bu
1 - 100 of 229 matches
Mail list logo
