> as far as I know. Beamer loads hyperref internally automaticaly, so the
> best to avoid option clashes in this case is to deactivate our hyperref
> support when beamer is used.
deactivation is superflous here, these problems are just small and the few
options are at worst ignored.
> Sorry for
Pavel Sanda schrieb:
and new nuisance is that unicode characters in title/name etc are in case of
beamer ignored
too, probably because ignoring unicode option we give to hyperref.
Uwe don't you have some idea what can be done?
No. The time we implemented hyperref supprt I contacted a few tim
> > > > with this patch both article and beamer works. comments?
> > >
> > > Yes, this is what I had in mind. One thing: The hyperref manual states
> > > that
> > > some options must be given in the optionl argument, not in \hyperset (but
> > > it does not list which ones). Did you check that?
>
> I thought about something like the attached (untested, not even compiled)
> patch, on top of your patch.
i fixed the patch so it outputs correct tex, but anyway it seems that beamer
simply ignores things in \documentclass options (tested on fullscreen and
pdfusetitle). if you'd like to play mor
Pavel Sanda wrote:
> it will be like the patch below (more or less, really want to go sleep
> now;) which i propose to put into trunk for the time beeing. if you can be
> more verbose how the 'global document options' solution looks in latex i
> may try something later. opinions?
I thought about
> > > ouch. e.g. pdfusetitle stops working via \hypersetup.
> >
> > What we can do in these cases is to pass those options as global document
> > options (if hyperref is provided by the class).
>
> dont know how to do.
>
> > (however, conflicts can not be avoided in general probably, since we do
> > ouch. e.g. pdfusetitle stops working via \hypersetup.
>
> What we can do in these cases is to pass those options as global document
> options (if hyperref is provided by the class).
dont know how to do.
> (however, conflicts can not be avoided in general probably, since we do not
> know what
Pavel Sanda wrote:
> ouch. e.g. pdfusetitle stops working via \hypersetup.
What we can do in these cases is to pass those options as global document
options (if hyperref is provided by the class).
(however, conflicts can not be avoided in general probably, since we do not
know what options the cl
> > > with this patch both article and beamer works. comments?
> >
> > Yes, this is what I had in mind. One thing: The hyperref manual states that
> > some options must be given in the optionl argument, not in \hyperset (but
> > it does not list which ones). Did you check that?
>
> not only that
> > with this patch both article and beamer works. comments?
>
> Yes, this is what I had in mind. One thing: The hyperref manual states that
> some options must be given in the optionl argument, not in \hyperset (but
> it does not list which ones). Did you check that?
not only that it does not li
Pavel Sanda wrote:
> with this patch both article and beamer works. comments?
Yes, this is what I had in mind. One thing: The hyperref manual states that
some options must be given in the optionl argument, not in \hyperset (but
it does not list which ones). Did you check that?
Jürgen
> > ok and what classes induce this problem (so i can test it)?
>
> beamer, moderncv, powerdot, prosper are some examples.
with this patch both article and beamer works. comments?
pavel
diff --git a/src/BufferParams.cpp b/src/BufferParams.cpp
index 5e884e6..c03c93f 100644
--- a/src/BufferParams.c
Pavel Sanda wrote:
> ok and what classes induce this problem (so i can test it)?
beamer, moderncv, powerdot, prosper are some examples.
Jürgen
> > > + /** FIXME: If the textclass provides hyperref, the GUI is
> > > + non-functional.
> >
> > hmm, in which cases (how often) this happens?
>
> I don't have any statistics, but we should support this as we do for any
> other
> supported package.
ok and what classes induce this p
Pavel Sanda wrote:
> > + /** FIXME: If the textclass provides hyperref, the GUI is
> > + non-functional.
>
> hmm, in which cases (how often) this happens?
I don't have any statistics, but we should support this as we do for any other
supported package.
Jürgen
> Author: spitz
> Date: Sat Jan 19 12:17:12 2008
> New Revision: 22629
>
> URL: http://www.lyx.org/trac/changeset/22629
> Log:
> Fix hyperref-soul conflict and sanitize hyperref management
...
> + /** FIXME: If the textclass provides hyperref, the GUI is
> + non-functional.
hmm, in w
16 matches
Mail list logo
