On 07/01/2013 1:35 AM, Jürgen Spitzmüller wrote:
Julien Rioux wrote:
Users of a legacy apacite.sty might disagree, since it is a relatively
recently added option. Also, there is no way to provide numerical
citation with \usepackage[natbibapa]{apacite}; for this I need
\usepackage{apacite}
\usepa
>
> Julien Rioux wrote:
> > Users of a legacy apacite.sty might disagree, since it is a relatively
> > recently added option. Also, there is no way to provide numerical
> > citation with \usepackage[natbibapa]{apacite}; for this I need
> > \usepackage{apacite}
> > \usepackage[numbers]{natbib}
>
Wh
Julien Rioux wrote:
> Users of a legacy apacite.sty might disagree, since it is a relatively
> recently added option. Also, there is no way to provide numerical
> citation with \usepackage[natbibapa]{apacite}; for this I need
> \usepackage{apacite}
> \usepackage[numbers]{natbib}
OK, so we are le
Julien Rioux wrote:
> LyX should handle package ordering for us, e.g., that apacite should be
> loaded before we load natbib.
But we have no control if a style file uses hooks (such as \AtBeginDocument).
> > And here's why it is important to pass "authoryear" explicitly: Style
> > files
> > can
On 06/01/2013 10:01 AM, Jürgen Spitzmüller wrote:
Julien Rioux wrote:
Do you have an example? I cannot find an example that supports your claim.
You can easily reproduce the error by putting
\usepackage{natbib}
\usepackage[authoryear]{natbib} in the preamble:
The package natbib has already be
On 06/01/2013 7:20 AM, Jürgen Spitzmüller wrote:
Julien Rioux wrote:
But if you select "natbib" from the Document settings dialog, the class
loads apacite/natbibapa. No module required. The only drawback I see is
that "plain" natbib (without apacite) is not possible with that class.
And using
Julien Rioux wrote:
> Do you have an example? I cannot find an example that supports your claim.
You can easily reproduce the error by putting
\usepackage{natbib}
\usepackage[authoryear]{natbib} in the preamble:
The package natbib has already been loaded with options:
[]
There has now been an a
On 06/01/2013 7:23 AM, Jürgen Spitzmüller wrote:
Julien Rioux wrote:
We pass [authoryear] to natbib, causing conflict. But this option is the
default, so we don't need to pass it. The following patch for trunk
fixes it (eventually we might want to handle the [numbers] option
differently to avoid
Julien Rioux wrote:
> We pass [authoryear] to natbib, causing conflict. But this option is the
> default, so we don't need to pass it. The following patch for trunk
> fixes it (eventually we might want to handle the [numbers] option
> differently to avoid other potential conflicts; putting it in
Julien Rioux wrote:
> > But if you select "natbib" from the Document settings dialog, the class
> > loads apacite/natbibapa. No module required. The only drawback I see is
> > that "plain" natbib (without apacite) is not possible with that class.
>
> And using apacite with natbib but without the n
On 06/01/2013 5:01 AM, Jürgen Spitzmüller wrote:
But if you select "natbib" from the Document settings dialog, the class loads
apacite/natbibapa. No module required. The only drawback I see is that "plain"
natbib (without apacite) is not possible with that class.
And using apacite with natbib b
On 05/01/2013 5:48 PM, Jacob Bishop wrote:
Whatever the solution, it would be ideal if it were possible to pass natbib
as either a package option, or to include natbib and/or apacite with
customizable options, such as in the preamble. One solution to this would
be to provide a checkbox where natb
On 05/01/2013 5:48 PM, Jacob Bishop wrote:
So, how do we get natbib working with apacite? This is the reason I
initially wrote the natbibapa module. There currently seems to be no other
way to get natbib working together with the apacite package. In particular,
when we try to load natbib with dif
On 05/01/2013 5:48 PM, Jacob Bishop wrote:
I really appreciate that you guys are thinking about this, and giving
feedback on the module/layout I worked on. It is my opinion that we always
need to be able to provide sensible defaults that work right out of the
box. Technically, apacite does not ne
On 05/01/2013 7:18 AM, Jürgen Spitzmüller wrote:
Julien Rioux wrote:
No need. Usual "LyX" way to pass option to packages: put them as
documentclass option.
This does not help in this case, since the option should only be passed when
natbib is requested, and natbib should be suppressed in this
On Sun, Jan 6, 2013 at 3:01 AM, Jürgen Spitzmüller wrote:
> Jacob Bishop wrote:
> > However, it is still not clear to me how to properly allow for
> > the natbibapa or apacite options to be supported. Julien has mentioned
> the
> > Requires parameter, but it is not clear to me from reading the
>
Jacob Bishop wrote:
> As I mentioned, apacite is not required by the apa6 document class (it was
> for the apa document class). It is only required if the apacite option or
> natbibapa option is passed to the document class. So, I think this means
> apacite should be removed from the #\DeclareLaTeX
I really appreciate that you guys are thinking about this, and giving
feedback on the module/layout I worked on. It is my opinion that we always
need to be able to provide sensible defaults that work right out of the
box. Technically, apacite does not need to be loaded to use apa6. You can
actually
Julien Rioux wrote:
> No need. Usual "LyX" way to pass option to packages: put them as
> documentclass option.
This does not help in this case, since the option should only be passed when
natbib is requested, and natbib should be suppressed in this case. Also,
apacite should only be requested w
On 05/01/2013 6:29 AM, Jürgen Spitzmüller wrote:
Jürgen Spitzmüller wrote:
A possibility for native support without this additional module would be a
line
Requires natbibapa 1
which causes LyX to load apacite with natbibapa option instead of natbib
itself (and plain apacite) if natbib is requi
Jürgen Spitzmüller wrote:
> A possibility for native support without this additional module would be a
> line
>
> Requires natbibapa 1
>
> which causes LyX to load apacite with natbibapa option instead of natbib
> itself (and plain apacite) if natbib is required.
Such as the attached.
Jürgend
Jürgen Spitzmüller wrote:
> > in the relevant layout files (seems like this was started by
> > apa6.layout, which already requires apacite.sty in the declaration line).
>
> The reason for the module, AFAIR, was that apa6 can be used wit natbib (or
> "natbibapa", for that matter), but just option
Julien Rioux wrote:
> That LyX loads the required packages in the required order for us. After
> http://www.lyx.org/trac/changeset/2e72a0af48023956ae6ce3285b47168c2fed5099/l
> yxgit it should be sufficient to have
>
> Requires apacite
>
> in the relevant layout files (seems like this was starte
On 03/01/2013 4:47 AM, Jürgen Spitzmüller wrote:
Julien Rioux wrote:
I missed the commit that added this module.
http://www.lyx.org/trac/changeset/824b0313b/lyxgit
http://www.lyx.org/trac/changeset/fcb49729/lyxgit
I think such module should
be on the wiki only, while in our source tree we im
Julien Rioux wrote:
> I missed the commit that added this module.
http://www.lyx.org/trac/changeset/824b0313b/lyxgit
http://www.lyx.org/trac/changeset/fcb49729/lyxgit
> I think such module should
> be on the wiki only, while in our source tree we implement proper
> support.
How would "proper su
On Sat, Dec 29, 2012 at 10:55 AM, Juergen Spitzmueller wrote:
> The branch, master, has been updated.
>
> - Log -
>
> commit d0b5728d2e4f6d33212639784b8ec3fa9d957ae4
> Author: Juergen Spitzmueller
> Date: Sat Dec 29 16:55:32 2012 +
26 matches
Mail list logo
