Uwe Stöhr wrote:
> > Can we set a "Provide hyperref 1" in the layout file (and handle that
> > correctly in source)?
>
> This doesn't help. You can still enable hyperref in the document style
> dialog. When you do this LyX wouldn't load hyperref in the preamble with
> \usepackage{hyperref} bu
Uwe Stöhr wrote:
> >>> Can we set a "Provide hyperref 1" in the layout file (and handle that
> >>> correctly in source)?
> >>>
> >> This doesn't help. You can still enable hyperref in the document style
> >> dialog. When you do this LyX wouldn't load hyperref in the preamble with
> >> \usepackage{h
I wrote schrieb:
I now only cleaned up the tufte-handout.layout since it is exactly the
same as the tufte-book.layout, with the only difference that
article.layout is loaded.
Jürgen, I hope it was OK to do this also directly in branch.
It was not. I think I forgot to mark part and part* as N
>>> Can we set a "Provide hyperref 1" in the layout file (and handle that
>>> correctly in source)?
>>>
>> This doesn't help. You can still enable hyperref in the document style
>> dialog. When you do this LyX wouldn't load hyperref in the preamble with
>> \usepackage{hyperref} but the \hypersetup
Uwe Stöhr schrieb:
I now only cleaned up the tufte-handout.layout since it is exactly the
same as the tufte-book.layout, with the only difference that
article.layout is loaded.
Jürgen, I hope it was OK to do this also directly in branch.
It was not. I think I forgot to mark part and part* as
Jürgen Spitzmüller writes:
> Uwe Stöhr wrote:
>
>> This doesn't help. You can still enable hyperref in the document style
>> dialog. When you do this LyX wouldn't load hyperref in the preamble with
>> \usepackage{hyperref} but the \hypersetup remains and effects the options
>> for tufte's interna
Uwe Stöhr wrote:
> This doesn't help. You can still enable hyperref in the document style
> dialog. When you do this LyX wouldn't load hyperref in the preamble with
> \usepackage{hyperref} but the \hypersetup remains and effects the options
> for tufte's internal hyperref loading. I don't know how
> Can we set a "Provide hyperref 1" in the layout file (and handle that
> correctly in source)?
This doesn't help. You can still enable hyperref in the document style dialog. When you do this LyX
wouldn't load hyperref in the preamble with \usepackage{hyperref} but the \hypersetup remains and
e
> Can we set a "Provide hyperref 1" in the layout file (and handle that
> correctly in source)?
Yes, I'll do this.
Joachim verified here:
http://www.mail-archive.com/lyx-us...@lists.lyx.org/msg77317.html
that the version I submitted works.
regards Uwe
Uwe Stöhr wrote:
> > His problems are no layout but LaTeX problems. I got similar ones when
> > processing the tufte-book.tex example file. This file use many packages
> > and also at my up to date LaTeX system I get a huge list with errors due
> > to package conflicts redefinitions.
I noticed th
Uwe Stöhr writes:
> The tufte classes for example inherit parts of the hyperref package.
> It therefore fails when you are using hyperref via LyX because the
> hyperref version of my MiKTeX is newer than the inherited one. Both
> example files therefore contain a note about this.
Can we set a "Pr
>> Can it also go to branch?
>
> Yes.
It's in.
> We should try to sort out the remaining issues, though (the problems reported
by Joachim on
> lyx-users).
His problems are no layout but LaTeX problems. I got similar ones when processing the tufte-book.tex
example file. This file use many pa
Uwe Stöhr wrote:
> OK, I will wait for Jason Waskiewicz' email where he declare his license
> permission and put it in. (I already contacted him in this regard.)
> Can it also go to branch?
Yes. We should try to sort out the remaining issues, though (the problems
reported by Joachim on lyx-us
> I think it works well. I don't use it myself and I just tested the base
> functionality. I have set it up per user request, and AFAIR the user was happy
> with the result. So I think we could include both tufte classes.
OK, I will wait for Jason Waskiewicz' email where he declare his license pe
Uwe Stöhr wrote:
> tufte-latex also contains another document class named tufte-handout. We
> also have a layout file for this class:
> http://wiki.lyx.org/Layouts/Tufte-handout
> but I haven't yet found the time for a closer look. Jürgen, you are listed
> as author if this layout. What's its s
> I didn't test it, but have no objection, if it works for you and Jason. Note
that if you do want
> to commit it, we'll need a GPL statement from Jason.
I'm aware of this.
> Can you tell me what the tufte-book class is?
http://tug.ctan.org/tex-archive/help/Catalogue/entries/tufte-latex.html
On 10/25/2009 05:30 PM, Uwe Stöhr wrote:
Attached is a layout file for the tufte-book document class. It is a
collaborative work with Jason Waskiewicz.
(http://wiki.lyx.org/Layouts/Tufte-book)
Jason tested the layout carefully and reported my today that it works
for all his testcases.
I would l
Attached is a layout file for the tufte-book document class. It is a collaborative work with Jason
Waskiewicz. (http://wiki.lyx.org/Layouts/Tufte-book)
Jason tested the layout carefully and reported my today that it works for all
his testcases.
I would like to include the layout file to LyX toge
18 matches
Mail list logo
