Re: Hyperref clarification
On 5/29/24 16:41, Brian Kneller via lyx-users wrote: Hi I am using book standard class and am installing chapters from MS Word and PDF graphics into LyX. I have hyperlinks generated between the figures list, TOC and Bibliography in the standard class without *hyperref *being available. The options I have tried in Docs>Settings> PDF Props seem to work and *hyperref *is made available**through the “Use hyperref Support” option. I have not installed any new document cross refs yet in LyX as they, and the Bibliography refs already exist for manual cross referencing. I would like to automate cross reference access using *hyperref* and the existing cross ref ID. I understand this is automatic when creating them in LyX, however I have been unable to find a feature to enable the document reader to return from an accessed cross reference back to the point of calling or have I missed the obvious? For citations, I think there is a backref option to hyperref. Check the hyperref manual. But I don't think there is a general setting for other kinds of cross-references. It might be that some PDF readers would do the right thing on "Back", but that would be up to the program. Separate issue: after generating a PDF from source I sometimes get errors and some of these quote a line number of large value which does not reference the source file, or is it the error log and in which case how can I enumerate the lines please? You should be able to click on the error message, and it will take you to the right place in the LyX file. But this is a bit tricky, and sometimes we're off by a few lines. Riki -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Hyperref clarification
Hi I am using book standard class and am installing chapters from MS Word and PDF graphics into LyX. I have hyperlinks generated between the figures list, TOC and Bibliography in the standard class without hyperref being available. The options I have tried in Docs>Settings> PDF Props seem to work and hyperref is made available through the “Use hyperref Support” option. I have not installed any new document cross refs yet in LyX as they, and the Bibliography refs already exist for manual cross referencing. I would like to automate cross reference access using hyperref and the existing cross ref ID. I understand this is automatic when creating them in LyX, however I have been unable to find a feature to enable the document reader to return from an accessed cross reference back to the point of calling or have I missed the obvious? Separate issue: after generating a PDF from source I sometimes get errors and some of these quote a line number of large value which does not reference the source file, or is it the error log and in which case how can I enumerate the lines please? Many Thanks Config: Mac Book Pro, Big Sur , LyX V 2.3.7 -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Hyperref support
Am Freitag, dem 11.02.2022 um 14:16 +0100 schrieb Jürgen Spitzmüller via lyx-users: > Sorry for the late response on this, but I just stumbled upon this > issue. As of hyperref 7.00g (2021-02-04), unicode is true by default > for all engines, so we can test for this version and omit the output > of this option in this case. This doesn't even need a file format > change. This is done for LyX 2.4. Jürgen signature.asc Description: This is a digitally signed message part -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Hyperref support
Am Donnerstag, dem 19.03.2020 um 09:42 -0400 schrieb Richard Kimberly Heck: > Well, the code is: > > // Since LyX uses unicode, also set the PDF strings to unicode > strings > // with the hyperref option "unicode". (With Xe/LuaTeX and pTeX, > // unicode=true is the default, with Japanese (platex), the > option > // leads to errors (even if the input encoding is UTF-8).) > if (!runparams.isFullUnicode() && !runparams.use_japanese) > opt += "unicode=true,"; > > That is: LyX outputs unicode itself in some cases, so setting > unicode=false could lead to errors. Still, it might be worth a > document > preference on this. Sorry for the late response on this, but I just stumbled upon this issue. As of hyperref 7.00g (2021-02-04), unicode is true by default for all engines, so we can test for this version and omit the output of this option in this case. This doesn't even need a file format change. Steve then needed to opt out via PackageOptions hyperref unicode=false in Document > Local Layout. Jürgen signature.asc Description: This is a digitally signed message part -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: hyperref package not shown in Code Preview
On 15/5/20 20:57, Paul A. Rubin wrote:
On 5/15/20 2:36 PM, Kornel Benko wrote:
Am Fri, 15 May 2020 11:28:52 -0400
schrieb "Paul A. Rubin" :
On 5/15/20 11:21 AM, Daniel wrote:
On 2020-05-15 16:50, Paul A. Rubin wrote:
On 5/15/20 9:26 AM, Daniel wrote:
Hi,
I think I am missing something. Shouldn't the hyperref package be
loaded in the attached document? But the Code Preview does not show
it. The output seems to use hyperref and the exported .tex file
shows the package though. This is with 2.3.4.
I guess I am missing something but I can't figure out what.
Best,
Daniel
It is being loaded. In Code Preview, it is loaded immediately before
\begin{document}. What might be throwing you off is that there are so
many options that "{hyperref}" is three lines after "\usepackage", at
least on my system.
Paul
Strange. I see the Code Preview as in the attachment. Not sure what
might be going on.
Daniel
That is odd. Here's a shot of what I see (also with LyX 2.3.4.2).
You are using hyperref support, while Daniel probably does not.
(Document->Settings…->PDF Properties->Use hyperref Support)
Kornel
That box was checked when I loaded his file (meaning I did not select it
myself), so I assumed that the setting was in Daniel's .lyx file. Is
that a local user preference rather than a file setting?
Paul
It is checked in my file settings (which are not local) and, as I
mentioned before, the output and .tex export have hyperref support. So,
I am still confused why it does not show up in the Code Preview.
Daniel
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users
Re: hyperref package not shown in Code Preview
On 5/15/20 2:36 PM, Kornel Benko wrote:
Am Fri, 15 May 2020 11:28:52 -0400
schrieb "Paul A. Rubin" :
On 5/15/20 11:21 AM, Daniel wrote:
On 2020-05-15 16:50, Paul A. Rubin wrote:
On 5/15/20 9:26 AM, Daniel wrote:
Hi,
I think I am missing something. Shouldn't the hyperref package be
loaded in the attached document? But the Code Preview does not show
it. The output seems to use hyperref and the exported .tex file
shows the package though. This is with 2.3.4.
I guess I am missing something but I can't figure out what.
Best,
Daniel
It is being loaded. In Code Preview, it is loaded immediately before
\begin{document}. What might be throwing you off is that there are so
many options that "{hyperref}" is three lines after "\usepackage", at
least on my system.
Paul
Strange. I see the Code Preview as in the attachment. Not sure what
might be going on.
Daniel
That is odd. Here's a shot of what I see (also with LyX 2.3.4.2).
You are using hyperref support, while Daniel probably does not.
(Document->Settings…->PDF Properties->Use hyperref Support)
Kornel
That box was checked when I loaded his file (meaning I did not select it
myself), so I assumed that the setting was in Daniel's .lyx file. Is
that a local user preference rather than a file setting?
Paul
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users
Re: hyperref package not shown in Code Preview
Am Fri, 15 May 2020 11:28:52 -0400
schrieb "Paul A. Rubin" :
> On 5/15/20 11:21 AM, Daniel wrote:
> > On 2020-05-15 16:50, Paul A. Rubin wrote:
> >> On 5/15/20 9:26 AM, Daniel wrote:
> >>> Hi,
> >>>
> >>> I think I am missing something. Shouldn't the hyperref package be
> >>> loaded in the attached document? But the Code Preview does not show
> >>> it. The output seems to use hyperref and the exported .tex file
> >>> shows the package though. This is with 2.3.4.
> >>>
> >>> I guess I am missing something but I can't figure out what.
> >>>
> >>> Best,
> >>> Daniel
> >>>
> >> It is being loaded. In Code Preview, it is loaded immediately before
> >> \begin{document}. What might be throwing you off is that there are so
> >> many options that "{hyperref}" is three lines after "\usepackage", at
> >> least on my system.
> >>
> >> Paul
> >>
> >>
> >
> > Strange. I see the Code Preview as in the attachment. Not sure what
> > might be going on.
> >
> > Daniel
> >
> That is odd. Here's a shot of what I see (also with LyX 2.3.4.2).
>
You are using hyperref support, while Daniel probably does not.
(Document->Settings…->PDF Properties->Use hyperref Support)
Kornel
pgpkkGmtrFmed.pgp
Description: Digitale Signatur von OpenPGP
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users
Re: hyperref package not shown in Code Preview
On 5/15/20 9:26 AM, Daniel wrote:
Hi,
I think I am missing something. Shouldn't the hyperref package be
loaded in the attached document? But the Code Preview does not show
it. The output seems to use hyperref and the exported .tex file shows
the package though. This is with 2.3.4.
I guess I am missing something but I can't figure out what.
Best,
Daniel
It is being loaded. In Code Preview, it is loaded immediately before
\begin{document}. What might be throwing you off is that there are so
many options that "{hyperref}" is three lines after "\usepackage", at
least on my system.
Paul
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users
hyperref package not shown in Code Preview
Hi, I think I am missing something. Shouldn't the hyperref package be loaded in the attached document? But the Code Preview does not show it. The output seems to use hyperref and the exported .tex file shows the package though. This is with 2.3.4. I guess I am missing something but I can't figure out what. Best, Daniel #LyX 2.3 created this file. For more info see http://www.lyx.org/ \lyxformat 544 \begin_document \begin_header \save_transient_properties true \origin unavailable \textclass article \use_default_options true \maintain_unincluded_children false \language english \language_package default \inputencoding auto \fontencoding global \font_roman "default" "default" \font_sans "default" "default" \font_typewriter "default" "default" \font_math "auto" "auto" \font_default_family default \use_non_tex_fonts false \font_sc false \font_osf false \font_sf_scale 100 100 \font_tt_scale 100 100 \use_microtype false \use_dash_ligatures true \graphics default \default_output_format default \output_sync 0 \bibtex_command default \index_command default \paperfontsize default \spacing single \use_hyperref true \pdf_bookmarks true \pdf_bookmarksnumbered false \pdf_bookmarksopen false \pdf_bookmarksopenlevel 1 \pdf_breaklinks true \pdf_pdfborder false \pdf_colorlinks false \pdf_backref false \pdf_pdfusetitle true \papersize default \use_geometry false \use_package amsmath 1 \use_package amssymb 1 \use_package cancel 1 \use_package esint 1 \use_package mathdots 1 \use_package mathtools 1 \use_package mhchem 1 \use_package stackrel 1 \use_package stmaryrd 1 \use_package undertilde 1 \cite_engine basic \cite_engine_type default \biblio_style plain \use_bibtopic false \use_indices false \paperorientation portrait \suppress_date false \justification true \use_refstyle 1 \use_minted 0 \index Index \shortcut idx \color #008000 \end_index \secnumdepth 3 \tocdepth 3 \paragraph_separation indent \paragraph_indentation default \is_math_indent 0 \math_numbering_side default \quotes_style english \dynamic_quotes 0 \papercolumns 1 \papersides 1 \paperpagestyle default \tracking_changes false \output_changes false \html_math_output 0 \html_css_as_file 0 \html_be_strict false \end_header \begin_body \begin_layout Section Test \begin_inset CommandInset label LatexCommand label name "sec:Test" \end_inset \end_layout \begin_layout Standard \begin_inset CommandInset ref LatexCommand nameref reference "sec:Test" plural "false" caps "false" noprefix "false" \end_inset \end_layout \end_body \end_document -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Hyperref support
On Thu, May 14, 2020 at 11:15:26PM -0400, Richard Kimberly Heck wrote:
> I am not that familiar with hyperref. How should this option interact
> with the ones currently given: runparams.isFullUnicode() and
> runparams.use_japanese? Say the new one is runparams.checkedUnicode.
> What is the correct test here:
>
> if (!runparams.isFullUnicode() && !runparams.use_japanese)
> opt += "unicode=true,";
Hmm... either having tristate check box automatic(default)/on/off or list with
these three options would solve it.
But when I am more thinking about it, the best option would probably be to do a
more generic change.
As noted we put additional settings into hypersetup instead directly into
options when declaring usepackage.
Maybe we should allow it to go directly to usepackage options (or create new
field for it, see also #10319).
In that case we would add one more check in the condition above ( &&
!hyperset.contains('unicode=') ).
Pavel
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Hyperref support
On 5/14/20 9:24 AM, Pavel Sanda wrote: > On Thu, Mar 26, 2020 at 11:04:28AM -0400, Richard Kimberly Heck wrote: >> On 3/26/20 10:31 AM, Pavel Sanda wrote: >>> On Thu, Mar 26, 2020 at 09:50:53AM -0400, Richard Kimberly Heck wrote: >>>>> Thank you for your responses. I can't say I fully understand why Lyx >>>>> needs to be as it is; I'm generally against hard coded parameters. >>>> We are as well, and I don't entirely know why it is done this way. It >>>> could be worth raising on lyx-devel. >>> Git points to 9b13535e778b9 >>> PDFOptions.cpp: add two hyperref options for better compatibility for >>> non-latin titles, etc. >>> >>> It might have been wrong to hardcode it this way, anyway we can't just drop >>> it >>> from compatibility reasons now. But adding new unicode option to the dialog >>> (by >>> default on) seems correct solution. >>> I don't have time to write the patch though. >> I can find the time, probably. >> >> Should we do something more general and allow custom options to be set? >> I.e., output no options ourselves in that case? >> >> Riki > I am not sure what more general case you have in mind. We already have > Additional options. If someone is super picky he can always write > exact commands in Preamble... I would just add unicode option set to > true by default. I am not that familiar with hyperref. How should this option interact with the ones currently given: runparams.isFullUnicode() and runparams.use_japanese? Say the new one is runparams.checkedUnicode. What is the correct test here: if (!runparams.isFullUnicode() && !runparams.use_japanese) opt += "unicode=true,"; ? Riki -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Hyperref support
On Thu, Mar 26, 2020 at 11:04:28AM -0400, Richard Kimberly Heck wrote: > On 3/26/20 10:31 AM, Pavel Sanda wrote: > > On Thu, Mar 26, 2020 at 09:50:53AM -0400, Richard Kimberly Heck wrote: > >>> Thank you for your responses. I can't say I fully understand why Lyx > >>> needs to be as it is; I'm generally against hard coded parameters. > >> We are as well, and I don't entirely know why it is done this way. It > >> could be worth raising on lyx-devel. > > Git points to 9b13535e778b9 > > PDFOptions.cpp: add two hyperref options for better compatibility for > > non-latin titles, etc. > > > > It might have been wrong to hardcode it this way, anyway we can't just drop > > it > > from compatibility reasons now. But adding new unicode option to the dialog > > (by > > default on) seems correct solution. > > I don't have time to write the patch though. > > I can find the time, probably. > > Should we do something more general and allow custom options to be set? > I.e., output no options ourselves in that case? > > Riki I am not sure what more general case you have in mind. We already have Additional options. If someone is super picky he can always write exact commands in Preamble... I would just add unicode option set to true by default. Pavel -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Hyperref support
On 3/26/20 10:31 AM, Pavel Sanda wrote: > On Thu, Mar 26, 2020 at 09:50:53AM -0400, Richard Kimberly Heck wrote: >>> Thank you for your responses. I can't say I fully understand why Lyx >>> needs to be as it is; I'm generally against hard coded parameters. >> We are as well, and I don't entirely know why it is done this way. It >> could be worth raising on lyx-devel. > Git points to 9b13535e778b9 > PDFOptions.cpp: add two hyperref options for better compatibility for > non-latin titles, etc. > > It might have been wrong to hardcode it this way, anyway we can't just drop it > from compatibility reasons now. But adding new unicode option to the dialog > (by > default on) seems correct solution. > I don't have time to write the patch though. I can find the time, probably. Should we do something more general and allow custom options to be set? I.e., output no options ourselves in that case? Riki -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Hyperref support
On Thu, Mar 26, 2020 at 09:50:53AM -0400, Richard Kimberly Heck wrote: > > Thank you for your responses. I can't say I fully understand why Lyx > > needs to be as it is; I'm generally against hard coded parameters. > > We are as well, and I don't entirely know why it is done this way. It > could be worth raising on lyx-devel. Git points to 9b13535e778b9 PDFOptions.cpp: add two hyperref options for better compatibility for non-latin titles, etc. It might have been wrong to hardcode it this way, anyway we can't just drop it from compatibility reasons now. But adding new unicode option to the dialog (by default on) seems correct solution. I don't have time to write the patch though. Pavel -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Hyperref support
On 3/26/20 4:05 AM, Steve Hnizdur wrote:
> On 19/03/2020 13:55, Daniel wrote:
>> On 2020-03-19 14:42, Richard Kimberly Heck wrote:
>>> On 3/19/20 3:01 AM, Daniel wrote:
>>>> On 2020-03-18 14:59, Steve Hnizdur wrote:
>>>>> Hi
>>>>>
>>>>> When "Use Hyperref Support" is checked in PDF properties Lyx
>>>>> automatically inserts
>>>>>
>>>>> \usepackage[unicode=true,
>>>>> bookmarks=false,
>>>>> breaklinks=false,pdfborder={0 0
>>>>> 1},backref=section,colorlinks=false]
>>>>> {hyperref}
>>>>>
>>>>> in the preamble. Any ideas where all these options come from? are
>>>>> they hard coded?
>>>>>
>>>>> Setting "unicode=false" in additional options doesn't seem to
>>>>> override the "unicode=true". So if unicode=true is causing a problem
>>>>> (in particular trying to redefine \C or \G) then this all has to
>>>>> added manually.
>>>>>
>>>>> MWE attached. Using Lyx 2.3.4.2 on Ubuntu 18.04
>>>>>
>>>>
>>>> Hi
>>>>
>>>> Yes, these options come from settings in the Hyperref dialog.
>>>>
>>>> "bookmarks=..." = "Generate bookmars (toc)"
>>>> "breaklinks=..." = "Break links over lines"
>>>> "pdfborder=..." = "No frames around links"
>>>> "colorlinks=..." = "Color links"
>>>> "backref=..." = "Backreferences"
>>>>
>>>> However, there seems to be no option for the "unicode=..." which seems
>>>> like an oversight. And the biggest problem is that according to the
>>>> manual:
>>>>
>>>> Note however that some options (for example unicode) can only be used
>>>> as packge options,and not in \hypersetup as the option settings are
>>>> processed as the package is read. (p. 6)
>>>>
>>>> So, unicode=false has no effect as an additional option.
>>>>
>>>> My guess is that this is a bug in LyX but others might know better.
>>>
>>> Well, the code is:
>>>
>>> // Since LyX uses unicode, also set the PDF strings to unicode
>>> strings
>>> // with the hyperref option "unicode". (With Xe/LuaTeX and pTeX,
>>> // unicode=true is the default, with Japanese (platex), the option
>>> // leads to errors (even if the input encoding is UTF-8).)
>>> if (!runparams.isFullUnicode() && !runparams.use_japanese)
>>> opt += "unicode=true,";
>>>
>>> That is: LyX outputs unicode itself in some cases, so setting
>>> unicode=false could lead to errors. Still, it might be worth a document
>>> preference on this.
>>>
>>> Riki
>>>
>>>
>>
>> An alternative might be to set the "Additional Options" via the
>> package options rather than hypersetup.
>>
>> Daniel
>>
>
> Thank you for your responses. I can't say I fully understand why Lyx
> needs to be as it is; I'm generally against hard coded parameters.
We are as well, and I don't entirely know why it is done this way. It
could be worth raising on lyx-devel.
Riki
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Hyperref support
On 19/03/2020 13:55, Daniel wrote:
On 2020-03-19 14:42, Richard Kimberly Heck wrote:
On 3/19/20 3:01 AM, Daniel wrote:
On 2020-03-18 14:59, Steve Hnizdur wrote:
Hi
When "Use Hyperref Support" is checked in PDF properties Lyx
automatically inserts
\usepackage[unicode=true,
bookmarks=false,
breaklinks=false,pdfborder={0 0 1},backref=section,colorlinks=false]
{hyperref}
in the preamble. Any ideas where all these options come from? are
they hard coded?
Setting "unicode=false" in additional options doesn't seem to
override the "unicode=true". So if unicode=true is causing a problem
(in particular trying to redefine \C or \G) then this all has to
added manually.
MWE attached. Using Lyx 2.3.4.2 on Ubuntu 18.04
Hi
Yes, these options come from settings in the Hyperref dialog.
"bookmarks=..." = "Generate bookmars (toc)"
"breaklinks=..." = "Break links over lines"
"pdfborder=..." = "No frames around links"
"colorlinks=..." = "Color links"
"backref=..." = "Backreferences"
However, there seems to be no option for the "unicode=..." which seems
like an oversight. And the biggest problem is that according to the
manual:
Note however that some options (for example unicode) can only be used
as packge options,and not in \hypersetup as the option settings are
processed as the package is read. (p. 6)
So, unicode=false has no effect as an additional option.
My guess is that this is a bug in LyX but others might know better.
Well, the code is:
// Since LyX uses unicode, also set the PDF strings to unicode
strings
// with the hyperref option "unicode". (With Xe/LuaTeX and pTeX,
// unicode=true is the default, with Japanese (platex), the option
// leads to errors (even if the input encoding is UTF-8).)
if (!runparams.isFullUnicode() && !runparams.use_japanese)
opt += "unicode=true,";
That is: LyX outputs unicode itself in some cases, so setting
unicode=false could lead to errors. Still, it might be worth a document
preference on this.
Riki
An alternative might be to set the "Additional Options" via the package
options rather than hypersetup.
Daniel
Thank you for your responses. I can't say I fully understand why Lyx
needs to be as it is; I'm generally against hard coded parameters.
I will work round by manually coding the preamble.
Cheers
--
Steve Hnizdur
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Hyperref support
On 2020-03-19 14:42, Richard Kimberly Heck wrote:
On 3/19/20 3:01 AM, Daniel wrote:
On 2020-03-18 14:59, Steve Hnizdur wrote:
Hi
When "Use Hyperref Support" is checked in PDF properties Lyx
automatically inserts
\usepackage[unicode=true,
bookmarks=false,
breaklinks=false,pdfborder={0 0 1},backref=section,colorlinks=false]
{hyperref}
in the preamble. Any ideas where all these options come from? are
they hard coded?
Setting "unicode=false" in additional options doesn't seem to
override the "unicode=true". So if unicode=true is causing a problem
(in particular trying to redefine \C or \G) then this all has to
added manually.
MWE attached. Using Lyx 2.3.4.2 on Ubuntu 18.04
Hi
Yes, these options come from settings in the Hyperref dialog.
"bookmarks=..." = "Generate bookmars (toc)"
"breaklinks=..." = "Break links over lines"
"pdfborder=..." = "No frames around links"
"colorlinks=..." = "Color links"
"backref=..." = "Backreferences"
However, there seems to be no option for the "unicode=..." which seems
like an oversight. And the biggest problem is that according to the
manual:
Note however that some options (for example unicode) can only be used
as packge options,and not in \hypersetup as the option settings are
processed as the package is read. (p. 6)
So, unicode=false has no effect as an additional option.
My guess is that this is a bug in LyX but others might know better.
Well, the code is:
// Since LyX uses unicode, also set the PDF strings to unicode strings
// with the hyperref option "unicode". (With Xe/LuaTeX and pTeX,
// unicode=true is the default, with Japanese (platex), the option
// leads to errors (even if the input encoding is UTF-8).)
if (!runparams.isFullUnicode() && !runparams.use_japanese)
opt += "unicode=true,";
That is: LyX outputs unicode itself in some cases, so setting
unicode=false could lead to errors. Still, it might be worth a document
preference on this.
Riki
An alternative might be to set the "Additional Options" via the package
options rather than hypersetup.
Daniel
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Hyperref support
On 3/19/20 3:01 AM, Daniel wrote:
> On 2020-03-18 14:59, Steve Hnizdur wrote:
>> Hi
>>
>> When "Use Hyperref Support" is checked in PDF properties Lyx
>> automatically inserts
>>
>> \usepackage[unicode=true,
>> bookmarks=false,
>> breaklinks=false,pdfborder={0 0 1},backref=section,colorlinks=false]
>> {hyperref}
>>
>> in the preamble. Any ideas where all these options come from? are
>> they hard coded?
>>
>> Setting "unicode=false" in additional options doesn't seem to
>> override the "unicode=true". So if unicode=true is causing a problem
>> (in particular trying to redefine \C or \G) then this all has to
>> added manually.
>>
>> MWE attached. Using Lyx 2.3.4.2 on Ubuntu 18.04
>>
>
> Hi
>
> Yes, these options come from settings in the Hyperref dialog.
>
> "bookmarks=..." = "Generate bookmars (toc)"
> "breaklinks=..." = "Break links over lines"
> "pdfborder=..." = "No frames around links"
> "colorlinks=..." = "Color links"
> "backref=..." = "Backreferences"
>
> However, there seems to be no option for the "unicode=..." which seems
> like an oversight. And the biggest problem is that according to the
> manual:
>
> Note however that some options (for example unicode) can only be used
> as packge options,and not in \hypersetup as the option settings are
> processed as the package is read. (p. 6)
>
> So, unicode=false has no effect as an additional option.
>
> My guess is that this is a bug in LyX but others might know better.
Well, the code is:
// Since LyX uses unicode, also set the PDF strings to unicode strings
// with the hyperref option "unicode". (With Xe/LuaTeX and pTeX,
// unicode=true is the default, with Japanese (platex), the option
// leads to errors (even if the input encoding is UTF-8).)
if (!runparams.isFullUnicode() && !runparams.use_japanese)
opt += "unicode=true,";
That is: LyX outputs unicode itself in some cases, so setting
unicode=false could lead to errors. Still, it might be worth a document
preference on this.
Riki
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Hyperref support
On 2020-03-18 14:59, Steve Hnizdur wrote:
Hi
When "Use Hyperref Support" is checked in PDF properties Lyx
automatically inserts
\usepackage[unicode=true,
bookmarks=false,
breaklinks=false,pdfborder={0 0 1},backref=section,colorlinks=false]
{hyperref}
in the preamble. Any ideas where all these options come from? are they
hard coded?
Setting "unicode=false" in additional options doesn't seem to override
the "unicode=true". So if unicode=true is causing a problem (in
particular trying to redefine \C or \G) then this all has to added
manually.
MWE attached. Using Lyx 2.3.4.2 on Ubuntu 18.04
Hi
Yes, these options come from settings in the Hyperref dialog.
"bookmarks=..." = "Generate bookmars (toc)"
"breaklinks=..." = "Break links over lines"
"pdfborder=..." = "No frames around links"
"colorlinks=..." = "Color links"
"backref=..." = "Backreferences"
However, there seems to be no option for the "unicode=..." which seems
like an oversight. And the biggest problem is that according to the manual:
Note however that some options (for example unicode) can only be used as
packge options,and not in \hypersetup as the option settings are
processed as the package is read. (p. 6)
So, unicode=false has no effect as an additional option.
My guess is that this is a bug in LyX but others might know better.
Daniel
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users
Hyperref support
Hi
When "Use Hyperref Support" is checked in PDF properties Lyx
automatically inserts
\usepackage[unicode=true,
bookmarks=false,
breaklinks=false,pdfborder={0 0 1},backref=section,colorlinks=false]
{hyperref}
in the preamble. Any ideas where all these options come from? are they
hard coded?
Setting "unicode=false" in additional options doesn't seem to override
the "unicode=true". So if unicode=true is causing a problem (in
particular trying to redefine \C or \G) then this all has to added manually.
MWE attached. Using Lyx 2.3.4.2 on Ubuntu 18.04
--
Steve Hnizdur
test.lyx
Description: application/lyx
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Bug in LyX regarding page format and hyperref
Am Montag, den 05.08.2019, 16:19 +0200 schrieb Jürgen Spitzmüller: > But still, if A4 is selected in LyX and memoir outputs US > letter, that's simply plain wrong. We can do better. This will be fixed in LyX 2.3.4. Jürgen signature.asc Description: This is a digitally signed message part
Re: Bug in LyX regarding page format and hyperref
Am Montag, den 05.08.2019, 08:22 -0500 schrieb Les: > I doubt if accounting for Memoir's idiosyncracies is practical. The > Memoir class allows fine tuning of numerous parameters that LyX > doesn't > even know about. I know. But still, if A4 is selected in LyX and memoir outputs US letter, that's simply plain wrong. We can do better. Jürgen signature.asc Description: This is a digitally signed message part
Re: Bug in LyX regarding page format and hyperref
On Mon, 05 Aug 2019 10:40:53 +0200
Jürgen Spitzmüller wrote:
> Yes, memoir overrides geometry (which is used for the custom margins).
> However, we could account for that in LyX. See
> https://www.lyx.org/trac/ticket/10970
I doubt if accounting for Memoir's idiosyncracies is practical. The
Memoir class allows fine tuning of numerous parameters that LyX doesn't
even know about. It's not just page format, its:
\setstocksize
\settrimmedsize
\settrims
\settypeblocksize
\setlrmargins
\setlength{\marginparwidth}
\pagestyle
\chapterstyle
and many other parameters I've never used.
If you're not prepared to read the 609 page Memoir manual (memman.pdf)
you really shouldn't try to use Memoir.
If you do read it, and understand it, you will view page layout in a
completely new way.
I have used memoir extensively for years, and I'm still learning how to
improve page layout. If you want good page layout that is nearly what
you need, use KOMA-script Book. If you want an exact page layout, use
Memoir, but be prepared to learn how to do it.
Les
--
Les Denham
Re: Bug in LyX regarding page format and hyperref
Am Samstag, den 27.07.2019, 11:06 -0400 schrieb Paul A. Rubin: > I don't have any experience with book classes, so I do not know the > peculiarities of the Memoir class. I suspect this is problem with > how > Memoir reacts to certain combinations of things, rather than a LyX > bug. Yes, memoir overrides geometry (which is used for the custom margins). However, we could account for that in LyX. See https://www.lyx.org/trac/ticket/10970 Jürgen signature.asc Description: This is a digitally signed message part
Re: Bug in LyX regarding page format and hyperref
On 27-Jul-19 9:32 AM, Marius Shekow wrote: > Hi again, > > I forgot to mention that you also need to set custom page margins. An > example file is attached. > > Best regards! > > Am 26.07.2019 um 20:14 schrieb Marius Shekow: >> Hi, >> >> I've noticed that the recent Lyx versions (2.3.x) generate a PDF that >> is of "US Letter" size, even though I've explicitly set up A4 in the >> document settings (Page Layout -> Format). This happens once I enable >> Hyperref support in the document settings. >> >> As suggested in >> https://tex.stackexchange.com/questions/356545/why-does-the-hyperref-package-change-the-paper-size >> >> >> it seems that adding "a4paper" as custom option to the documentclass >> seems to work. This is extreme expert knowledge that you should not >> expect your users to have. When a normal/novice user sets up A4, then >> the generated PDF should be A4 (and the same goes for any other page >> format). >> >> Is this something that you could fix? >> >> Best regards! >> Marius >> Hello Marius, As you may be aware of that LyX serves as a front-end for the LaTeX system. When you select a paper size in LyX, LyX -probably- simply adds that paper size as an option to the document class in the generated tex file. On the other hand, LaTeX is a sophisticated typesetting system, where many packages and classes are used. Sometimes, some of these packages and classes have conflicts and associated rules. When you try to use some specific packages for a given class, you may not be allowed to change some settings. As far as I observe, LyX developers are trying to identify these conflicts and implement LyX-based solutions for some of them. However, it is not always possible to follow every single one of these conflicts/rules since there are so many of these packages and classes. Further, LaTeX packages are being updated constantly and may result a conflict after an update, which makes it very difficult to track them. To put this in another way, if you are not using LyX, but using conventional text-based LaTeX typesetting, you will probably encounter these issues as well. If this issue is a well-known issue, LyX developers might have provided a solution in LyX. However, it is not always possible for LyX to have a solution. In this case, you are supposed to identify the issue and provide a solution by yourself, which we LyX-used do all the time. Best Regards, Baris -- ↓↓ Please bottom-post. Start your reply here:
Re: Bug in LyX regarding page format and hyperref
Hi, I was aware of https://wiki.lyx.org/LyX/UsingMemoirInLyX but at the same time that page seems outdated, as it explicitly mentions Lyx 1.5, which is dated. I saw that it also mentions section 6.3 of the "Additional Features" LyX help document (valid for LyX 2.x), but did not see this caveat (US Letter) being listed. It may still make sense for LyX to handle this specific case, but that's up to you. I'm content with the fix I found (which I mentioned in the original post). I've been using memoir simply out of habit. I don't think I'm using specific features that other book classes wouldn't offer. I'd say that I just liked the look of the generated PDF that came out of the box, in comparison to other book classes. I may look into scrbook for the next project, though. Best! Marius Am 27.07.2019 um 17:27 schrieb Axel Dessecker: Am Samstag, 27. Juli 2019, 08:32:33 CEST schrieb Marius Shekow: Hi again, I forgot to mention that you also need to set custom page margins. An example file is attached. Best regards! Am 26.07.2019 um 20:14 schrieb Marius Shekow: Hi, I've noticed that the recent Lyx versions (2.3.x) generate a PDF that is of "US Letter" size, even though I've explicitly set up A4 in the document settings (Page Layout -> Format). This happens once I enable Hyperref support in the document settings. As suggested in https://tex.stackexchange.com/questions/356545/why-does-the-hyperref-packa ge-change-the-paper-size it seems that adding "a4paper" as custom option to the documentclass seems to work. This is extreme expert knowledge that you should not expect your users to have. When a normal/novice user sets up A4, then the generated PDF should be A4 (and the same goes for any other page format). Is this something that you could fix? Best regards! Marius Marius, I can reproduce this behaviour, which seems to be associated with the memoir class. Very configurable but tricky, as announced at https://wiki.lyx.org/LyX/UsingMemoirInLyX . Is there a specific reason why you are not using scrbook? Axel
Re: Bug in LyX regarding page format and hyperref
Am Samstag, 27. Juli 2019, 08:32:33 CEST schrieb Marius Shekow: > Hi again, > > I forgot to mention that you also need to set custom page margins. An > example file is attached. > > Best regards! > > Am 26.07.2019 um 20:14 schrieb Marius Shekow: > > Hi, > > > > I've noticed that the recent Lyx versions (2.3.x) generate a PDF that > > is of "US Letter" size, even though I've explicitly set up A4 in the > > document settings (Page Layout -> Format). This happens once I enable > > Hyperref support in the document settings. > > > > As suggested in > > https://tex.stackexchange.com/questions/356545/why-does-the-hyperref-packa > > ge-change-the-paper-size it seems that adding "a4paper" as custom option > > to the documentclass seems to work. This is extreme expert knowledge that > > you should not expect your users to have. When a normal/novice user sets > > up A4, then the generated PDF should be A4 (and the same goes for any > > other page format). > > > > Is this something that you could fix? > > > > Best regards! > > Marius Marius, I can reproduce this behaviour, which seems to be associated with the memoir class. Very configurable but tricky, as announced at https://wiki.lyx.org/LyX/UsingMemoirInLyX . Is there a specific reason why you are not using scrbook? Axel
Re: Bug in LyX regarding page format and hyperref
On 7/27/19 2:32 AM, Marius Shekow wrote: Hi again, I forgot to mention that you also need to set custom page margins. An example file is attached. Best regards! Am 26.07.2019 um 20:14 schrieb Marius Shekow: Hi, I've noticed that the recent Lyx versions (2.3.x) generate a PDF that is of "US Letter" size, even though I've explicitly set up A4 in the document settings (Page Layout -> Format). This happens once I enable Hyperref support in the document settings. As suggested in https://tex.stackexchange.com/questions/356545/why-does-the-hyperref-package-change-the-paper-size it seems that adding "a4paper" as custom option to the documentclass seems to work. This is extreme expert knowledge that you should not expect your users to have. When a normal/novice user sets up A4, then the generated PDF should be A4 (and the same goes for any other page format). Is this something that you could fix? Best regards! Marius Please bottom post in messages to the forum. I can confirm your example compiles to US letter when it should compile to A4, but the trigger mechanism is more complex than hyperref + custom margins + A4 paper size. It only seems to happen with the Memoir class. I tried the basic book class, the AMS book class and also the basic article class, and they all compiled to A4. I don't have any experience with book classes, so I do not know the peculiarities of the Memoir class. I suspect this is problem with how Memoir reacts to certain combinations of things, rather than a LyX bug. Perhaps an experience Memoir user can weigh in. Paul
Re: Bug in LyX regarding page format and hyperref
Hi again, I forgot to mention that you also need to set custom page margins. An example file is attached. Best regards! Am 26.07.2019 um 20:14 schrieb Marius Shekow: Hi, I've noticed that the recent Lyx versions (2.3.x) generate a PDF that is of "US Letter" size, even though I've explicitly set up A4 in the document settings (Page Layout -> Format). This happens once I enable Hyperref support in the document settings. As suggested in https://tex.stackexchange.com/questions/356545/why-does-the-hyperref-package-change-the-paper-size it seems that adding "a4paper" as custom option to the documentclass seems to work. This is extreme expert knowledge that you should not expect your users to have. When a normal/novice user sets up A4, then the generated PDF should be A4 (and the same goes for any other page format). Is this something that you could fix? Best regards! Marius newfile2.lyx Description: application/lyx
Re: Bug in LyX regarding page format and hyperref
On 7/26/19 2:14 PM, Marius Shekow wrote: Hi, I've noticed that the recent Lyx versions (2.3.x) generate a PDF that is of "US Letter" size, even though I've explicitly set up A4 in the document settings (Page Layout -> Format). This happens once I enable Hyperref support in the document settings. As suggested in https://tex.stackexchange.com/questions/356545/why-does-the-hyperref-package-change-the-paper-size it seems that adding "a4paper" as custom option to the documentclass seems to work. This is extreme expert knowledge that you should not expect your users to have. When a normal/novice user sets up A4, then the generated PDF should be A4 (and the same goes for any other page format). Is this something that you could fix? Best regards! Marius I'm unable to reproduce that here. I switched a document from US Letter to A4 in the page layout settings, turned on hyperref in the PDF settings, viewed the document (using pdflatex), and the resulting file was A4 (confirmed by checking File > Properties in the PDF viewer). I also tried A2, which produces a visibly different result (many fewer pages). If you can reproduce the bug, please reply with a minimal working example of it. Paul
Bug in LyX regarding page format and hyperref
Hi, I've noticed that the recent Lyx versions (2.3.x) generate a PDF that is of "US Letter" size, even though I've explicitly set up A4 in the document settings (Page Layout -> Format). This happens once I enable Hyperref support in the document settings. As suggested in https://tex.stackexchange.com/questions/356545/why-does-the-hyperref-package-change-the-paper-size it seems that adding "a4paper" as custom option to the documentclass seems to work. This is extreme expert knowledge that you should not expect your users to have. When a normal/novice user sets up A4, then the generated PDF should be A4 (and the same goes for any other page format). Is this something that you could fix? Best regards! Marius
hyperref
Hi Using LyX 2.2.2 and biblatex/biber, the following occurs. When a citation is LyX provides a hyperref link around the When a citation is <(year)> there is no hyperref link at all! Any suggestions, please, about how to ensure the linkage for the second case? regards Frank Salter PS -- Are the mail archives being updated?
Re: how to load hyperref before titlesec to avoid off-sync links?
On Wed, Nov 9, 2016 at 10:04 AM, Scott Kostyshak wrote: > It seems there are many cases with hyperref. If this is confirmed by > others, I wonder if a checkbox in the PDF tab of "load hyperref at end > of preamble" would solve many cases. It might be better to come up with > a general solution though. My understanding is that in some cases hyperref should come before packages, and other times: after. See the discussion starting on page 17 of http://ftp.math.purdue.edu/mirrors/ctan.org/macros/latex/contrib/hyperref/README.pdf . Regards, Joel
Re: how to load hyperref before titlesec to avoid off-sync links?
On Wed, Nov 09, 2016 at 05:33:14PM +0100, Liviu Andronic wrote: > Do we document this (i.e. explicitly controlling the order of loaded > packages) somewhere? I've quickly searched the docs before firing the > email, but couldn't find something (I checked User's Guide B.21 and > 6.10.2). I don't know. I suppose it falls under customization since you load titlesec in the user preamble. In the customization manual we describe Provides but I don't think we talk about how it can be used to control the order of packages, which is a common issue that users run into. It seems there are many cases with hyperref. If this is confirmed by others, I wonder if a checkbox in the PDF tab of "load hyperref at end of preamble" would solve many cases. It might be better to come up with a general solution though. Scott signature.asc Description: PGP signature
Re: how to load hyperref before titlesec to avoid off-sync links?
On Wed, Nov 9, 2016 at 3:47 PM, Scott Kostyshak wrote: > On Wed, Nov 09, 2016 at 12:26:18PM +0100, Liviu Andronic wrote: > >> > The >> > solution it seems is to make sure that hyperref is loaded before >> > titlesec, but I'm at a loss as to how to achieve this. > > Do you mean load hyperref *after* titlesec? > Yes, precisely. > In local layout, put > > Provides hyperref > > Then load hyperref yourself in the LaTeX preamble. > Perfect, thank you. Do we document this (i.e. explicitly controlling the order of loaded packages) somewhere? I've quickly searched the docs before firing the email, but couldn't find something (I checked User's Guide B.21 and 6.10.2). Liviu > See the attached. > > Scott
Re: how to load hyperref before titlesec to avoid off-sync links?
On Wed, Nov 09, 2016 at 12:26:18PM +0100, Liviu Andronic wrote:
> > The
> > solution it seems is to make sure that hyperref is loaded before
> > titlesec, but I'm at a loss as to how to achieve this.
Do you mean load hyperref *after* titlesec?
In local layout, put
Provides hyperref
Then load hyperref yourself in the LaTeX preamble.
See the attached.
Scott
#LyX 2.2 created this file. For more info see http://www.lyx.org/
\lyxformat 508
\begin_document
\begin_header
\save_transient_properties true
\origin unavailable
\textclass article
\begin_preamble
\usepackage{titlesec}
\newcommand{\sectionbreak}{\clearpage}
\usepackage{hyperref}
\end_preamble
\use_default_options true
\maintain_unincluded_children false
\begin_local_layout
Provides hyperref
\end_local_layout
\language english
\language_package default
\inputencoding auto
\fontencoding global
\font_roman "default" "default"
\font_sans "default" "default"
\font_typewriter "default" "default"
\font_math "auto" "auto"
\font_default_family default
\use_non_tex_fonts false
\font_sc false
\font_osf false
\font_sf_scale 100 100
\font_tt_scale 100 100
\graphics default
\default_output_format default
\output_sync 0
\bibtex_command default
\index_command default
\paperfontsize default
\spacing single
\use_hyperref true
\pdf_bookmarks true
\pdf_bookmarksnumbered false
\pdf_bookmarksopen false
\pdf_bookmarksopenlevel 1
\pdf_breaklinks false
\pdf_pdfborder false
\pdf_colorlinks false
\pdf_backref false
\pdf_pdfusetitle true
\papersize default
\use_geometry false
\use_package amsmath 1
\use_package amssymb 1
\use_package cancel 1
\use_package esint 1
\use_package mathdots 1
\use_package mathtools 1
\use_package mhchem 1
\use_package stackrel 1
\use_package stmaryrd 1
\use_package undertilde 1
\cite_engine basic
\cite_engine_type default
\biblio_style plain
\use_bibtopic false
\use_indices false
\paperorientation portrait
\suppress_date false
\justification true
\use_refstyle 1
\index Index
\shortcut idx
\color #008000
\end_index
\secnumdepth 3
\tocdepth 3
\paragraph_separation indent
\paragraph_indentation default
\quotes_language english
\papercolumns 1
\papersides 1
\paperpagestyle default
\tracking_changes false
\output_changes false
\html_math_output 0
\html_css_as_file 0
\html_be_strict false
\end_header
\begin_body
\begin_layout Title
Title
\end_layout
\begin_layout Standard
\begin_inset CommandInset toc
LatexCommand tableofcontents
\end_inset
\end_layout
\begin_layout Standard
Text
\end_layout
\begin_layout Section
Section 1
\end_layout
\begin_layout Standard
Text
\end_layout
\begin_layout Section
Section 2
\end_layout
\begin_layout Standard
Text
\end_layout
\begin_layout Section
Section 3
\end_layout
\begin_layout Standard
Text
\end_layout
\begin_layout Section
Section 4
\end_layout
\begin_layout Standard
Text
\end_layout
\end_body
\end_document
signature.asc
Description: PGP signature
Re: how to load hyperref before titlesec to avoid off-sync links?
And of course a typo:
*how to load titlesec before hyperref to avoid off-sync links?
On Wed, Nov 9, 2016 at 12:22 PM, Liviu Andronic wrote:
> Dear all,
> In a document I want to start new page with each section, and follow
> this recipe for that:
> http://tex.stackexchange.com/questions/9497/start-new-page-with-each-section/9505?noredirect=1#comment829734_9505
>
> \usepackage{titlesec}
> \newcommand{\sectionbreak}{\clearpage}
>
> The problem arises because if you use hyperref and a ToC, the links
> get off-sync. For instance, clicking on Section 2 in the ToC will
> bring you to p3, whereas this section is on p4 (see attached). The
> solution it seems is to make sure that hyperref is loaded before
> titlesec, but I'm at a loss as to how to achieve this.
>
*to make sure that titlesec is loaded before hyperref...
Liviu
> I tried:
> \AtBeginDocument{
> \usepackage{titlesec}
> \newcommand{\sectionbreak}{\clearpage}
> }
>
> but it (as expected) doesn't improve things. Any ideas?
>
> I remember order of package loading in LyX has been discussed before,
> but I can't recall what's the current state of things...
>
> Regards,
> Liviu
how to load hyperref before titlesec to avoid off-sync links?
Dear all,
In a document I want to start new page with each section, and follow
this recipe for that:
http://tex.stackexchange.com/questions/9497/start-new-page-with-each-section/9505?noredirect=1#comment829734_9505
\usepackage{titlesec}
\newcommand{\sectionbreak}{\clearpage}
The problem arises because if you use hyperref and a ToC, the links
get off-sync. For instance, clicking on Section 2 in the ToC will
bring you to p3, whereas this section is on p4 (see attached). The
solution it seems is to make sure that hyperref is loaded before
titlesec, but I'm at a loss as to how to achieve this.
I tried:
\AtBeginDocument{
\usepackage{titlesec}
\newcommand{\sectionbreak}{\clearpage}
}
but it (as expected) doesn't improve things. Any ideas?
I remember order of package loading in LyX has been discussed before,
but I can't recall what's the current state of things...
Regards,
Liviu
lyx-titlesec-hyperref.lyx
Description: Binary data
lyx-titlesec-hyperref.pdf
Description: Adobe PDF document
Re: Load package after hyperref is loaded
On 04/26/2016 06:48 AM, racoon wrote:
> Hi!
>
> In general packages should be loaded *before* hyperref is loaded. So I
> guess that is what happens when "Use Hyperref Support" is activated in
> the Document Settings.
>
> However, there seem to be some exceptions, for example,
>
> \usepackage[all]{hypcap}.
The user preamble always comes after the LyX-generated premable. If you
put this in your own preamble, then, it will get loaded after hyperref.
The difficult case is when you need to load your own package before
hyperref.
Richard
Load package after hyperref is loaded
Hi!
In general packages should be loaded *before* hyperref is loaded. So I
guess that is what happens when "Use Hyperref Support" is activated in
the Document Settings.
However, there seem to be some exceptions, for example,
\usepackage[all]{hypcap}.
Is there a way to load this package *after* hyperref is loaded? Or will
I have to deactivate "Use Hyperref Support" and load it manually in the
preamble instead?
Thank you
how to make hyperref colors to page numbers identical
Dear all,
I am writing a document using classicthesis with the following parts:
In the /Table of Contents/ and in the /Index of Linguistic Terms / - the
referenced page numbers appear in _RoyalBlue_
In the /Index of Names/ and in the /Nomenclature/ - the referenced page
numbers appear in _black_
All my attempts to change the black referenced page numbers to RoyalBlue
(which is set in the Hyperreferences section of
classicthesis-config.tex) failed as well as all the various respective
entries I tried in the preamble.
If for instance I add to the preamble:
\usepackage{hyperref}
\hypersetup{colorlinks=true, linkcolor=blue} (or whatever other color)
the RoyalBlue will change to blue whereas the black is not effected.
Can somebody help, please!
Michael
Re: pdfx and hyperref
Am Mittwoch, 2. Dezember 2015, 18:28:49 schrieb Kornel Benko: > Am Mittwoch, 2. Dezember 2015 um 11:59:43, schrieb Scott Kostyshak > > > On Wed, Dec 02, 2015 at 10:54:29AM +0100, Egon Alter wrote: > > > Hi, > > > > > > I'm trying to produce a pdf/a conformant pdf which includes hyperref. > > > The > > > attached example fails with "option clash" (when you add a > > > sRGBIEC1966-2.1.icm). AFAIU, the reason is that hyperref is loaded twice > > > (by lyx with its own options and pdfx with options pdfa,pdftex) with > > > different options. Maybe the fix is to add "pdfa,pdftex" to the lyx > > > options, but I can't find a way to do this (not via hypersetup!) > > > > Hi Egon, > > > > Your document compiles for me without error. > > > > Scott > > But only with pdflatex here :( well, that wouldn't be a problem. I found that texlive 2014 (opensuse) ships pdfx version 1.2 from 2008, while the current version seems to be 1.5.3 from 2015! I replaced pdfx with its current version and now the example file works fine. However, my work file prints lots of unicode errors now, but that's likely something different. Thanks so far! Egon
Re: pdfx and hyperref
Am Mittwoch, 2. Dezember 2015 um 11:59:43, schrieb Scott Kostyshak > On Wed, Dec 02, 2015 at 10:54:29AM +0100, Egon Alter wrote: > > Hi, > > > > I'm trying to produce a pdf/a conformant pdf which includes hyperref. The > > attached example fails with "option clash" (when you add a > > sRGBIEC1966-2.1.icm). AFAIU, the reason is that hyperref is loaded twice > > (by > > lyx with its own options and pdfx with options pdfa,pdftex) with different > > options. Maybe the fix is to add "pdfa,pdftex" to the lyx options, but I > > can't > > find a way to do this (not via hypersetup!) > > Hi Egon, > > Your document compiles for me without error. > > Scott But only with pdflatex here :( Kornel signature.asc Description: This is a digitally signed message part.
Re: pdfx and hyperref
On Wed, Dec 02, 2015 at 10:54:29AM +0100, Egon Alter wrote: > Hi, > > I'm trying to produce a pdf/a conformant pdf which includes hyperref. The > attached example fails with "option clash" (when you add a > sRGBIEC1966-2.1.icm). AFAIU, the reason is that hyperref is loaded twice (by > lyx with its own options and pdfx with options pdfa,pdftex) with different > options. Maybe the fix is to add "pdfa,pdftex" to the lyx options, but I > can't > find a way to do this (not via hypersetup!) Hi Egon, Your document compiles for me without error. Scott signature.asc Description: PGP signature
pdfx and hyperref
Hi, I'm trying to produce a pdf/a conformant pdf which includes hyperref. The attached example fails with "option clash" (when you add a sRGBIEC1966-2.1.icm). AFAIU, the reason is that hyperref is loaded twice (by lyx with its own options and pdfx with options pdfa,pdftex) with different options. Maybe the fix is to add "pdfa,pdftex" to the lyx options, but I can't find a way to do this (not via hypersetup!) Thanks, Egon hyperref_clash.lyx Description: application/lyx
RE: Hyperref color links
It Works! Thanks so much Scott
Re: Hyperref color links
On Mon, Sep 29, 2014 at 2:18 AM, Alberto Escrig Vidal
wrote:
> When this option is selected, LyX automatically adds:
>
>
>
> \usepackage{color}
>
>
>
> before babel is loaded.
>
>
>
> If a multilingual Italian/Spanish document is involved (Spanish being the
> main language), this causes the document to fail to compile (with an updated
> MiKTeX distribution), such as the following minimal example:
>
>
>
> \documentclass[italian,spanish]{book}
>
>
>
> \usepackage{color}
>
> \usepackage{babel}
>
> \usepackage[colorlinks=true]{hyperref}
>
>
>
> \begin{document}
>
> foo
>
> \end{document}
>
>
>
> The problem is easily solved in LaTeX by loading color after babel is
> loaded. In LyX there is also a workaround: providing colorlinks=true as an
> additional hyperref option, which is not very elegant, because the LaTeX
> translate will look like:
>
>
>
> \usepackage[colorlinks=false,colorlinks=true]{hyperref}
>
>
>
> Is it possible to influence LyX to load color after babel being loaded?
Hi Alberto,
I don't know much about this, but you might be able to do something like
Provides color
in local layout.
See Help > Customization for more information.
Please let the list know if you try it and it works.
Best,
Scott
Hyperref color links
When this option is selected, LyX automatically adds:
\usepackage{color}
before babel is loaded.
If a multilingual Italian/Spanish document is involved (Spanish being
the main language), this causes the document to fail to compile (with an
updated MiKTeX distribution), such as the following minimal example:
\documentclass[italian,spanish]{book}
\usepackage{color}
\usepackage{babel}
\usepackage[colorlinks=true]{hyperref}
\begin{document}
foo
\end{document}
The problem is easily solved in LaTeX by loading color after babel is
loaded. In LyX there is also a workaround: providing colorlinks=true as
an additional hyperref option, which is not very elegant, because the
LaTeX translate will look like:
\usepackage[colorlinks=false,colorlinks=true]{hyperref}
Is it possible to influence LyX to load color after babel being loaded?
Re: Turning hyperref off in table of contents
On 25 March 2013 05:20, Frederick FN Noronha फ्रेड्रिक नोरोन्या
*فريدريك نورونيا wrote:
> Dear all: I'm getting the hyperref links ON in the table-of-contents, when I
> don't want it. Could you pls guide on how to remove the clickable blue marks
> around the chapter titles in TOC? Thanks, FN
Why not keep the links but remove the colour?
\begingroup
\hypersetup{linkcolor=black}
TOCHERE (or anything else you don't want coloured)
\endgroup
You also want "No frames around links", which is in the document
settings (PDF properties > hyperlinks).
--
GPG/PGP ID: C0711BF1
Re: LyX Interface to the \hyperref Command?
Hi Steve,
Thanks for your reply.
On 15 December 2012 17:51, Steve Litt wrote:
>
>
> I use hyperref in all my books. I just \usepackage{hyperref} in the
> layout file, as I remember.
>
>
I probably wasn't clear in the problem I described. LyX makes it very easy
to setup hyperref support so references actually links in the resulting pdf
document (you can just select in Document->Settings).
However, the hyperref package provides the \hyperref[labelname]{link text}
command (it's a command with the same name as the package). This command is
somewhat like the href command LyX support but instead of pointing at a URL
it points to a label in the current document. This is the command I'm
looking for an interface for.
Thanks,
Guy
Re: LyX Interface to the \hyperref Command?
On Sat, 15 Dec 2012 13:32:10 +0200
Guy Rutenberg wrote:
> Hi All,
>
> I want to add a link to a specific label in my document. This
> functionality is provided by the \hyperref command:
>
> \hyperref{name-of-label}{link text}
>
> Is there any interface in LyX to facilitate this?
>
> I could to it in ERT, but I prefer that LyX will be aware of the
> reference to the label, and update it if the label changes.
>
> Thanks,
>
> Guy
I use hyperref in all my books. I just \usepackage{hyperref} in the
layout file, as I remember.
DANGER WILL ROBINSON: hyperref and Memoir conflict. There are
documented ways to get around this, but I was unable to get them to
work. As a result I don't use Memoir, and in fact I always use my own
modifications on the Book document class.
SteveT
How to turn dynamic links (hyperref?) on for equations but off for references (literature)?
I'd like to have dynamic references in the document for equations (and be able to adjust their formatting, no boxes around equation numbers, set color, etc.) but at the same time turn off this feature for references (literature)? Thanks.
Re: How to load xr-hyper before hyperref?
On 2012-05-23, Rudi Gaelzer wrote: > I'd like to use the facilities of the xr-hyper package to > cross-reference equations (or other things) labelled in another doc > and at the same time create a pdf (using xetex) with the whole > hyper-ref stuff (using the hyperref package). > The problem is, the xr-hyper pack should be loaded on the preamble > BEFORE hyperref, otherwise errors such as "Paragraph ended before ... > was complete" can appear. > The only place I can order LyX to load xr-hyper is on the doc's local > preamble, but in this case, the package will be loaded always after > hyperref. > Is there any way I can circumvent this limitation? Just untick the "use hyperref" box in Document>Settings>PDF-... and load/configure hyperref in the LaTeX preamble. Günter
Re: How to load xr-hyper before hyperref?
On 05/23/2012 03:41 PM, Rudi Gaelzer wrote: I'd like to use the facilities of the xr-hyper package to cross-reference equations (or other things) labelled in another doc and at the same time create a pdf (using xetex) with the whole hyper-ref stuff (using the hyperref package). The problem is, the xr-hyper pack should be loaded on the preamble BEFORE hyperref, otherwise errors such as "Paragraph ended before ... was complete" can appear. The only place I can order LyX to load xr-hyper is on the doc's local preamble, but in this case, the package will be loaded always after hyperref. Is there any way I can circumvent this limitation? Prevent LyX loading hyperref by putting: Provides hyperrer 1 into Local Layout. Then load it yourself. rh
How to load xr-hyper before hyperref?
I'd like to use the facilities of the xr-hyper package to cross-reference equations (or other things) labelled in another doc and at the same time create a pdf (using xetex) with the whole hyper-ref stuff (using the hyperref package). The problem is, the xr-hyper pack should be loaded on the preamble BEFORE hyperref, otherwise errors such as "Paragraph ended before ... was complete" can appear. The only place I can order LyX to load xr-hyper is on the doc's local preamble, but in this case, the package will be loaded always after hyperref. Is there any way I can circumvent this limitation? Thanks. -- Rudi Gaelzer Registered Linux user # 153741
Re: hyperref and TOC
Csikos Bela írta:
>Hello lyx users:>
>
I tried to use hyperref package in my lyx document.>
It nicely creates the bookmarks/links in the pdf but does not include the TOC
itself. I am attaching a .lyx and a .pdf doc as an example.>
What I have in the bookmarks pane is:>
First section>
Subsection>
>
I would like to have 1) a bookmark for the TOC and also 2) one for the Title
page, like this:>
>
Title page>
Table of contents>
First section>
Subsection>
>
Clicking on the Title page would navigate to the Title page, and clicking to
the TOC would navigate to the TOC page.>
How can I achieve this?>
I found out myself:
I inserted in ERT
\pdfbookmark[1]{Title page}{titlepage}
just before TITLE PAGE
and
\pdfbookmark[1]{\contentsname}{toc}
just before the TOC.
bcsikos
Re: More hyperref bogosity
On Thursday 24 March 2011 17:28:57 Jacob Bishop wrote: > On Thu, Mar 24, 2011 at 3:10 PM, Steve Litt wrote: > > Hi all, > > > > I have an appendix listing the several processes in my book, with cross > > references pointing to the pages on which these processes are discussed, > > using > > a text:myprocess-discussion-start and text:myprocess-discussion-end > > labels within the book's text. All of the cross references print the > > correct page number, but several go to the wrong page (an earlier page) > > if you click them. > > However, many of the cross references go to the correct page when > > clicked. I > > see no distinction between the ones that screw up and the ones that work > > correctly. > > > > Before I take a half a day or more slowly deconstructing this 110,000 > > word book to form a small test case, does anyone have any ideas why some > > cross references would screw up? > > I really don't know all that much about this problem. All I know is that > when I did my thesis in LyX, I had some links going to wrong pages. To fix > it, I had to use some ERT with \phantomsection in certain places, if I > remember correctly. It's my understanding this has to do with how the marks > are set for hyperref to deal with them. I'm certain there are others who > know more, but this might help. > > Jacob Hi all, It was exactly what Jacob said, and it's actually a well known problem with a well known solution. Hyperref was never meant to go with just any old label. Hyperref was built to refer to the current chapter, section, subsection, subsubsection, etc, containing the label. It's also meant to refer to the inside of a float, but that's beyond the scope of the current discussion. Anyway, remember this: when you create a crossreference to a label, the page number is exactly that of the label, but hyperref jumps to the beginning of the smallest containing chapter, section, subsection etc containing that label. So the hyperref people made the \phantomsection command to make a little tiny fake section. Whenever you make a label that isn't at the front of a chapter, section etc and isn't in a float, if you're using hyperref you MUST put an ERT \phantomsection immediately before the label. This will cure the problem I mentioned. Remember, the \phantomsection goes before the *label*, not before the crossreference. Happy hyperreffing. SteveT Steve Litt Recession Relief Package http://www.recession-relief.US Twitter: http://www.twitter.com/stevelitt
Re: More hyperref bogosity
On Thu, Mar 24, 2011 at 3:10 PM, Steve Litt wrote: > Hi all, > > I have an appendix listing the several processes in my book, with cross > references pointing to the pages on which these processes are discussed, > using > a text:myprocess-discussion-start and text:myprocess-discussion-end labels > within the book's text. All of the cross references print the correct page > number, but several go to the wrong page (an earlier page) if you click > them. > However, many of the cross references go to the correct page when clicked. > I > see no distinction between the ones that screw up and the ones that work > correctly. > > Before I take a half a day or more slowly deconstructing this 110,000 word > book to form a small test case, does anyone have any ideas why some cross > references would screw up? > > I really don't know all that much about this problem. All I know is that when I did my thesis in LyX, I had some links going to wrong pages. To fix it, I had to use some ERT with \phantomsection in certain places, if I remember correctly. It's my understanding this has to do with how the marks are set for hyperref to deal with them. I'm certain there are others who know more, but this might help. Jacob
More hyperref bogosity
Hi all, I have an appendix listing the several processes in my book, with cross references pointing to the pages on which these processes are discussed, using a text:myprocess-discussion-start and text:myprocess-discussion-end labels within the book's text. All of the cross references print the correct page number, but several go to the wrong page (an earlier page) if you click them. However, many of the cross references go to the correct page when clicked. I see no distinction between the ones that screw up and the ones that work correctly. Before I take a half a day or more slowly deconstructing this 110,000 word book to form a small test case, does anyone have any ideas why some cross references would screw up? Thanks SteveT Steve Litt Recession Relief Package http://www.recession-relief.US Twitter: http://www.twitter.com/stevelitt
Disable HyperRef when Exporting to OpenDocument
Hi All, Hopefully this post saves somebody some hassle. If you are having problems exporting LyX to OpenDocument, try disabling HyperRef. I was having significant export problems until I discovered the HyperRef trick. Good luck, ~greg (Mac 10.5, LyX 2.0RC1, TexLive2010)
AW: AW: hyperref to pdf: path format?
Paul Rubin wrote: Try converting the backslashes to forward slashes. There's a relevant Wikipedia entry at https://secure.wikimedia.org/wikipedia/en/wiki/File_URI_scheme#Windows. Ahh, that is nice. This works. Thank you. Best wishes, J.
Re: AW: hyperref to pdf: path format?
Try converting the backslashes to forward slashes. There's a relevant Wikipedia entry at https://secure.wikimedia.org/wikipedia/en/wiki/File_URI_scheme#Windows. /Paul
AW: hyperref to pdf: path format?
Paul Rubin wrote: I'm not on a Windows machine at the moment, so I can't test this, but the correct format for file links in general is file:/// You might try inserting the forward slashes after "file:". I did, even with multiple slashes and backslashes. I suspect that it is not properly translated to texcode. It would be nice for any user, if the path could be entered into the menu - and everything is done. but I am curious to see how it can be done (with the current LyX beta version) Best wishes, J.
Re: hyperref to pdf: path format?
I'm not on a Windows machine at the moment, so I can't test this, but the correct format for file links in general is file:/// You might try inserting the forward slashes after "file:". /Paul
hyperref to pdf: path format?
Hi,
I want to use a hyperlink in a PDF output to a file on my hard drive.
Using the hyperlink menu in LyX , what path format should be used to
make that work?
Not working is the path, e.g., H:\folder\file.pdf - translated to
texcode this appears as
\footnote{\href{file:H:\%5Cfolder\%5Cfile.pdf}{H:\textbackslash{}folder\textbackslash{}file.pdf}%
}
Anything wrong with my path format as input?
Working with LyX2.0b1 on WinVista.
/J.
Hyperref, breaklinks & default driver?
Hello,
I get the following warning using hyperref with 'breaklings" on and as
default driver hdvips.
> * hyperref using default driver hdvips *
> (/usr/local/texlive/2010/texmf-dist/tex/latex/hyperref/hdvips.def
> File: hdvips.def 2010/06/18 v6.81g Hyperref driver for dvips
> (/usr/local/texlive/2010/texmf-dist/tex/latex/hyperref/pdfmark.def
> File: pdfmark.def 2010/06/18 v6.81g Hyperref definitions for pdfmark specials
>
> Package hyperref Warning: You have enabled option `breaklinks'.
> (hyperref)But driver `hdvips.def' does not suppport this.
> (hyperref)Expect trouble with the link areas of broken links.
But if I change hyperref.cfg with
\providecommand*{...@defaultdriver}{hypertex}
I got a lot of error messages with biblatex.
Should I ignore the warning and continue using hdvips? Or did I something
wrong?
Peter
A solution for PDF format issue with pdflatex & hyperref not producing A4 paper
Dear all, For those of you having problems generating PDF in A4 paper format, when pdflatex is used in conjunction with hyperref and despite having selected A4 in Page Layout under Documents Settings, here is next a simple solution. I'm working under LyX 1.6.7 with book (Memoir). In addition to selecting the A4 format in Page Layout, the generated LaTeK code must contain the \documentclass entry with the "a4paper" option included. By writing the custom command a4paper in the Document Settings, this solves the problem. Go to menu Documents -> Settings... -> Document Class -> Custom: and add "a4paper" (without the quotes). Sorry if this is no news for you, but I spent 2 days searching for FAQ /forums / blogs / web before finding. It does not require the use of tex2pdf (as suggested here http://max.home.subnet.at/tex/). Unfortunately, I had not detected this problem before printing all my thesis exemplaries :(((. As my PDF were output in Letter format, the printer driver of my university printing service applied a shrinkage to convert Letter into A4 without margin losses, screwing up my nice formatting :( I don't know if this was corrected in LyX 2.0, but I would suggest developpers to specifically add "a4paper" automatically in \documentclass when the option is selected in Page Layout. My 2 cents, Yannick
wrong equation spacing with hyperref - Was: PDF compile strange behavior
Am 19.08.2010 18:26, schrieb Uwe Stöhr: >> I am using Lyx 1.6.5 in WinXp. I found a strange behavior when Lyx >> converts documents into pdf files. I am using document style book >> (koma) with AMS math package. I have compiled one with PDF hyperref >> support enabled using Document->Settings->PDF Properties to produce >> document Example1.pdf (left side), and uncheck the hyperref support >> to produce Example2.pdf (right side). Every other setups are exactly >> the same. Strangely, Example1.pdf has extra space between equations >> like (2.5)-(2.6), (2.7)-(2.8), etc. You found a bug in the LaTeX-package hyperref or the package amsmath: This problem is known, see the file http://www.ctan.org/tex-archive/macros/latex/contrib/hyperref/README.pdf section 6 under "amsmath". As workaround you can add this to your document preamble: \let\equation\gather \let\endequation\endgather Note that this can cause other problems. If you get problems with this workaround, I would delete the document class option "fleqn". The equations are then centered but the other spacing should be correct. regards Uwe
incompatibility between lyx, hyperref and tth
I wrote to Ian Hutchinson (author of tth):
> Anyway, I wanted to alert you to a potential bug. When I use lyx's
> "hyperef" feature to make a hyperlink (as opposed to embedding a URL,
> where the text is the same as the href target), it generates a .tex
> file that contains a line like this:
>
> \usepackage[unicode=true, pdfusetitle,
> bookmarks=true,bookmarksnumbered=false,bookmarksopen=false,
> breaklinks=false,pdfborder={0 0 1},backref=false,colorlinks=false]
> {hyperref}
>
> When I run it through tth, it creates a tag of "hyperref".
He responds:
Hello. Thanks for this message. The problem is with the way Lyx is laying
out its \usepackage command. TtH knows nothing about \usepackage. It treats
it as an unknown command.
http://hutchinson.belmont.ma.us/tth/manual/sec9.html#commands+unknown93
explains that such commands ought to be laid out _without_ whitespace
between themselves and their arguments. Because Lyx is inserting whitespace
before {hyperref}, TtH scans it as if it is the start of the text.
The only way to fix this properly is for Lyx to avoid adding that extra
whitespace between ] and {. No space or newline is allowed. You could fix
it by hand in the .tex file yourself; but that's a bit annoying.
Typical results appear at top of this page:
http://www.subspacefield.org/~travis/web_generator/
--
A Weapon of Mass Construction
My emails do not have attachments; it's a digital signature that your mail
program doesn't understand. | http://www.subspacefield.org/~travis/
If you are a spammer, please email j...@subspacefield.org to get blacklisted.
pgpodldZNhEzV.pgp
Description: PGP signature
Re: Problem with hyperref
Am 31.01.2010 19:48, schrieb Arik Raffael Funke:
However, when I try to activate the hyperref option in the document
setting I get the error message below. - It stumbles over a section
definition line. The error seems to be repeated for any "heading"
definition that would appear in the TOC.
===
...}State of the art}{\re...@font\mtcsfont 3}}
I've run across a `}' that doesn't seem to match anything.
LaTeX tells you that you have a closing brace that doesn't match an opening brace. To fix the
problem, have a look at your document preamble and TeX-code insets that there is no superfluous "}".
If you cannot find it, provide a _small_ LyX example file and I'll have a look.
regards Uwe
Problem with hyperref
Hi,
I am working on a document using among others the packages:
- amsmath
- natbib
- minitoc
All of which are activated via the document settings except for the
minitoc which is activated by a preable and control sequences in the
body of the lyx document.
This is working very well so far.
However, when I try to activate the hyperref option in the document
setting I get the error message below. - It stumbles over a section
definition line. The error seems to be repeated for any "heading"
definition that would appear in the TOC.
Does anybody have any hints?
Many thanks,
Arik
===
...}State of the art}{\re...@font\mtcsfont 3}}
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
endnotes and hyperref
Dear Lyx-list,
I want to use endnotes with hyperref. Endnotes are produced by:
- Footnote function from Lyx
- insert ERT '\theendnotes' (where endnotes should appear) and in preamble
\usepackage{endnotes}
\let\footnote=\endnote
However, the number of the endnotes are not 'clickable' which means
there is no link present.
How can I change that so that endnote-numbers are clickable and link
directly to the endnotes at the end of the chapter?
thanks!
best wishes,
leo
Re: question regarding LyX's placement of hyperref
Venable schrieb:
I have a small question about the way LyX places hyperref among other
packages. From exporting LyX files to plain latex, it appears that LyX
does not place hyperref last among the packages, as recommended in the
hyperref manual. This is innocuous 99% of the time but has in my
experience caused problems for some more esoteric packages such as
bibentry or endfloat.
It is impossible to find a location for hyperref, so that it worjks in every case. So we've chosen
the place that should work in most cases.
A simple workaround is to hand-code \usepackage{hyperref} (with
whatever options) into the LaTeX preamble rather than using the PDF
Properties pulldown menu. However, since the pulldown menu is very
convenient, I'm wondering if there's a way to customize LyX to place
hyperref in the right place.
The feature to be able to customize the package placement is in planning.
regards Uwe
question regarding LyX's placement of hyperref
Dear LyX users,
I have a small question about the way LyX places hyperref among other
packages. From exporting LyX files to plain latex, it appears that LyX
does not place hyperref last among the packages, as recommended in the
hyperref manual. This is innocuous 99% of the time but has in my
experience caused problems for some more esoteric packages such as
bibentry or endfloat.
A simple workaround is to hand-code \usepackage{hyperref} (with
whatever options) into the LaTeX preamble rather than using the PDF
Properties pulldown menu. However, since the pulldown menu is very
convenient, I'm wondering if there's a way to customize LyX to place
hyperref in the right place.
Thanks.
Re: Option Clash with hyperref
Hi Uwe, Problem solved--my style file also called up hyperref and this was the source of the conflict. I think this problem could be classified as a complication due to importing from .tex. I wrote all my files in .tex and WinEdt and am now translating everything into LyX because of the extreme coolness of LyX. If there's any list of "things to look out for when importing .tex files into LyX" I would add "Check for redundant loading of packages in style files that will lead to options clashes" to the list. Thanks for your help. Rob
Re: Option Clash with hyperref
Rob schrieb: Here's the text of my file where I dropped the hyperref package call in the preamble and set the specifications in the pdf options. Can you please attach the LyX file itself to this mail. I cannot create a LyX file out of your text. regards Uwe
Re: Option Clash with hyperref
Uwe Stöhr writes:
Hi Uwe,
Here's the text of my file where I dropped the hyperref
package call in the preamble and set the specifications
in the pdf options.
Thanks.
Rob
#LyX 1.6.4 created this file. For more info see
http://www.lyx.org/
\lyxformat 345
\begin_document
\begin_header
\textclass report
\begin_preamble
\usepackage{uwmadison-rgw}
\usepackage{enumitem}
\usepackage{appendix}
\usepackage[nottoc,notlof,notlot]{tocbibind}
%\let\citep=\citet
\setcitestyle{aysep={}}
\singlespacing
\end_preamble
\use_default_options false
\language english
\inputencoding auto
\font_roman default
\font_sans default
\font_typewriter default
\font_default_family default
\font_sc false
\font_osf false
\font_sf_scale 100
\font_tt_scale 100
\graphics default
\paperfontsize 12
\spacing single
\use_hyperref true
\pdf_bookmarks true
\pdf_bookmarksnumbered true
\pdf_bookmarksopen true
\pdf_bookmarksopenlevel 3
\pdf_breaklinks false
\pdf_pdfborder false
\pdf_colorlinks true
\pdf_backref page
\pdf_pdfusetitle false
\papersize default
\use_geometry false
\use_amsmath 1
\use_esint 1
\cite_engine natbib_authoryear
\use_bibtopic false
\paperorientation portrait
\secnumdepth 3
\tocdepth 3
\paragraph_separation indent
\defskip medskip
\quotes_language english
\papercolumns 1
\papersides 1
\paperpagestyle default
\tracking_changes false
\output_changes false
\author ""
\author ""
\end_header
\begin_body
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "TitleLabel"
\end_inset
\end_layout
\begin_layout Standard
\begin_inset ERT
status open
\begin_layout Plain Layout
%**TITLE PAGE**
\end_layout
\begin_layout Plain Layout
\backslash
title{
\backslash
vspace{2em} Selected for Attainment:
\backslash
vspace{2em}
\backslash
\backslash
The Lasting Effects of Childhood Health}
\end_layout
\begin_layout Plain Layout
\backslash
author{Robert G.
White}
\end_layout
\begin_layout Plain Layout
\backslash
abstract{Here is the abstract.
Here is the abstract.
Here is the abstract.
Here is the abstract.
Here is the abstract.
Here is the abstract.
Here is the abstract.
Here is the abstract.
Here is the abstract.
Here is the abstract.
Here is the abstract.
Here is the abstract.
Here is the abstract.
Here is the abstract.
Here is the abstract.
Here is the abstract.
Here is the abstract.
Here is the abstract.
Here is the abstract.
Here is the abstract.
Here is the abstract.
Here is the abstract.
Here is the abstract.
Here is the abstract.
Here is the abstract.}
\end_layout
\begin_layout Plain Layout
\backslash
degree{Doctor of Philosophy}
\end_layout
\begin_layout Plain Layout
\backslash
college{College of Letters and Science}
\end_layout
\begin_layout Plain Layout
\backslash
dept{Sociology}
\backslash
directordept{Sociology}
\end_layout
\begin_layout Plain Layout
\backslash
secondreaderdept{Sociology}
\end_layout
\begin_layout Plain Layout
\backslash
thirdreaderdept{Sociology}
\end_layout
\begin_layout Plain Layout
\backslash
copyrightyear{2009}
\end_layout
\end_inset
\end_layout
\begin_layout Standard
\begin_inset ERT
status open
\begin_layout Plain Layout
\backslash
pdfbookmark[0]{Title}{TitleLabel}
\end_layout
\begin_layout Plain Layout
\backslash
makedissertationtitle
\end_layout
\begin_layout Plain Layout
\backslash
pagenumbering{roman}
\end_layout
\begin_layout Plain Layout
\backslash
prefacesection{Acknowledgments}
\end_layout
\begin_layout Plain Layout
\backslash
director{Alberto Palloni}
\end_layout
\begin_layout Plain Layout
\backslash
makeabstract
\end_layout
\begin_layout Plain Layout
\backslash
prefacesection{Preface}
\end_layout
\end_inset
\begin_inset CommandInset label
LatexCommand label
name "TableOfContentsLabel"
\end_inset
\begin_inset CommandInset toc
LatexCommand tableofcontents
\end_inset
\begin_inset ERT
status open
\begin_layout Plain Layout
\backslash
pdfbookmark[0]{Contents}{TableOfContentsLabel}
\end_layout
\begin_layout Plain Layout
\backslash
newpage
\end_layout
\begin_layout Plain Layout
\backslash
makelistoftables
\end_layout
\begin_layout Plain Layout
\backslash
makelistoffigures
\end_layout
\begin_layout Plain Layout
\backslash
pagenumbering{arabic}
\end_layout
\begin_layout Plain Layout
\backslash
doublespacing
\end_layout
\end_inset
\end_layout
\begin_layout Chapter
\paragraph_spacing single
Introduction
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "Chapter1_Introduction"
\end_inset
\begin_inset CommandInset include
LatexCommand input
filename "1 Intro/Chapter1_Introduction.lyx"
\end_inset
\end_layout
\begin_layout Chapter
\paragraph_spacing single
Health Selection in Socioeconomic Status Attainment
\end_layout
\begin_layout St
Re: Option Clash with hyperref
Rob schrieb:
My document class is report. Here's my preamble:
\usepackage{uwmadison-rgw}
\usepackage{enumitem}
\usepackage{appendix}
\usepackage[nottoc,notlof,notlot]{tocbibind}
\usepackage[pagebackref=true]{hyperref}
In this case, the error is:
LaTeX Error: Option clash for package hyperref.
The package hyperref has already been loaded with options:
[plainpages=false,pdfpagelabels]
LyX already loaded the hyperref package. hyperref must be set up in the document settings in the PDF
properties and not in the user preamble.
So I tried Document Settings->PDF Properties->Use Hyperref Support->Backref set
to page and then removed the \usepackage{hyperref}.
But then I get the following error:
LaTeX Error: Option clash for package hyperref.
The package hyperref has already been loaded with options:
[unicode=true,bookmarks=true,bookmarksnumbered=true,bookmarksopen=true,bookma
rksopenlevel=3,breaklinks=false,pdfborder={0 0 1},backref=page,colorlinks=true]
Can you please send a LyX example file to be able to reproduce this problem?
regards Uwe
Re: Option Clash with hyperref
Uwe Stöhr writes:
Hi Uwe,
My document class is report. Here's my preamble:
\usepackage{uwmadison-rgw}
\usepackage{enumitem}
\usepackage{appendix}
\usepackage[nottoc,notlof,notlot]{tocbibind}
\usepackage[pagebackref=true]{hyperref}
In this case, the error is:
LaTeX Error: Option clash for package hyperref.
The package hyperref has already been loaded with options:
[plainpages=false,pdfpagelabels]
There has now been an attempt to load it with options
[pagebackref=true]
Adding the global options:
plainpages=false,pdfpagelabels,pagebackref=true
to your \documentclass declaration may fix this.
Try typingto proceed.
So I tried this instead:
\usepackage{hyperref}
\hyperset{pagebackref=true}
In that case, I didn't receive an error, but there were no hyperlinks in my
references that take me back to the location of the citations in my text.
So I tried Document Settings->PDF Properties->Use Hyperref Support->Backref set
to page and then removed the \usepackage{hyperref}.
But then I get the following error:
LaTeX Error: Option clash for package hyperref.
The package hyperref has already been loaded with options:
[unicode=true,bookmarks=true,bookmarksnumbered=true,bookmarksopen=true,bookma
rksopenlevel=3,breaklinks=false,pdfborder={0 0 1},backref=page,colorlinks=true]
Do I need to somehow suppress the options?
Or do I need to change the pdf options?
Any suggestions are much appreciated.
Rob
Re: Option Clash with hyperref
On 10.09.2009, at 22:58, Rob wrote:
Hi,
I want to use backref, but I'm getting an options clash. I read in
a past post
that there is some mess when trying to specify the options in
hyperref since
they're already set but that a work around is to add a \hyperset
argument to the
preamble. In this case, I tried the following without any success:
\hyperset{pagebackref=yes}
AFAIK the backref options cannot be set by \hyperset, but have to be
passed when hyperref is loaded.
Daniel
Re: Option Clash with hyperref
Rob schrieb:
I want to use backref, but I'm getting an options clash.
What is the error message?
I read in a past post
that there is some mess when trying to specify the options in hyperref since
they're already set but that a work around is to add a \hyperset argument to the
preamble. In this case, I tried the following without any success:
\hyperset{pagebackref=yes}
You can also set this option in the document settings in the PDF properties.
When this doesn't work, can you please provide a _small_ example LyX file.
regards Uwe
Option Clash with hyperref
Hi,
I want to use backref, but I'm getting an options clash. I read in a past post
that there is some mess when trying to specify the options in hyperref since
they're already set but that a work around is to add a \hyperset argument to the
preamble. In this case, I tried the following without any success:
\hyperset{pagebackref=yes}
In this case, there is no error message, but backref doesn't work.
Any thoughts are much appreciated.
Rob
Re: Compilation error in French with varioref and hyperref
Jean-Pierre Chrétien a écrit : [...] Here is my record: Lyx version OS TeX distributionResult 1.6.4 Debian Lenny TeXLive 2007 Failure After downloading and installing TeXLive 2008, the new record is 1.6.4 Debian Lenny TeXLive 2008 Success -- Jean-Pierre
Re: Compilation error in French with varioref and hyperref
On Tuesday 01 September 2009 02:18:20 am Jean-Pierre Chrétien wrote:
> Hello,
>
> With my installation, I get an error when creating the pdf version of
> the UserGuide, that I narrowed down to the attached simple example.
>
> Before taking into consideration the solution that I proposed (the
> source code must be patched), the developers would like to understand
> why nobody ever posted about this bug.
>
> Would you be so kind to load the attached file in lyx and try to view it
> as PDF, then to feed back the result ?
>
> Here is my record:
> Lyx version OS TeX distributionResult
>1.6.4 Debian Lenny TeXLive 2007 Failure
>
> TIA for your answers.
Lyx Version OS Tex DistributionResult
1.6.4 KUbuntu 9.04 TexLive 2007 Failure
From Latex Log:
! Missing \endcsname inserted.
\penalty
l.20 ...agraphe, \vpageref{sec:Premier-paragraphe}
,
The control sequence marked should
not appear between \csname and \endcsname.
! Extra \endcsname.
\...@ifundefined ...dafter \ifx \csname #1\endcsname
\relax \expandafter
\...@firs...
l.20 ...agraphe, \vpageref{sec:Premier-paragraphe}
,
I'm ignoring this, since I wasn't doing a \csname.
! Missing \endcsname inserted.
\penalty
l.20 ...agraphe, \vpageref{sec:Premier-paragraphe}
,
The control sequence marked should
not appear between \csname and \endcsname.
! Missing \endcsname inserted.
\penalty
l.20 ...agraphe, \vpageref{sec:Premier-paragraphe}
,
The control sequence marked should
not appear between \csname and \endcsname.
[1
{/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map}] (./varioref_error.aux)
__
Stefano Franchi
Department of Philosophy Ph: (979) 862-2211
Texas A&M University Fax: (979) 845-0458
305B Bolton Hall fran...@philosophy.tamu.edu
College Station, TX 77843-4237
Re: Compilation error in French with varioref and hyperref
Am Tuesday 01 September 2009 09:18:20 schrieb Jean-Pierre Chrétien:
> Hello,
>
> With my installation, I get an error when creating the pdf version of
> the UserGuide, that I narrowed down to the attached simple example.
>
> Before taking into consideration the solution that I proposed (the
> source code must be patched), the developers would like to understand
> why nobody ever posted about this bug.
>
> Would you be so kind to load the attached file in lyx and try to view it
> as PDF, then to feed back the result ?
>
> Here is my record:
> Lyx version OS TeX distributionResult
>1.6.4 Debian Lenny TeXLive 2007 Failure
>
> TIA for your answers.
I tried it with 1.6.3 Debian Lenny:
! Missing \endcsname inserted.
\penalty
l.21 ...agraphe, \vpageref{sec:Premier-paragraphe}
,
The control sequence marked should
not appear between \csname and \endcsname.
! Extra \endcsname.
\...@ifundefined ...dafter \ifx \csname #1\endcsname
\relax \expandafter
\...@firs...
l.21 ...agraphe, \vpageref{sec:Premier-paragraphe}
,
I'm ignoring this, since I wasn't doing a \csname.
! Missing \endcsname inserted.
\penalty
l.21 ...agraphe, \vpageref{sec:Premier-paragraphe}
,
The control sequence marked should
not appear between \csname and \endcsname.
! Missing \endcsname inserted.
\penalty
l.21 ...agraphe, \vpageref{sec:Premier-paragraphe}
,
The control sequence marked should
not appear between \csname and \endcsname.
[1
{/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map}] (./varioref_error.aux)
LaTeX Warning: Label(s) may have changed. Rerun to get cross-references right.
)
(\end occurred when \ifdim on line 21 was incomplete)
(\end occurred when \ifhmode on line 21 was incomplete)
(\end occurred when \ifdim on line 21 was incomplete)
(\end occurred when \ifhmode on line 21 was incomplete)
Wolfgang
Re: Compilation error in French with varioref and hyperref
I have no problem compiling to PDF the UserGuide on LyX 1.6.4 System Windows XP pro, Alt Installer, MiKTeX 2.7 installed with LyX. ( this is the version of the UserGuide distributed with LyX, french version ). Siegfried.
Re: Compilation error in French with varioref and hyperref
Jean-Pierre Chrétien writes: > With my installation, I get an error when creating the pdf version of > the UserGuide, that I narrowed down to the attached simple example. > > Would you be so kind to load the attached file in lyx and try to view it > as PDF, then to feed back the result ? > > Here is my record: > Lyx version OS TeX distributionResult >1.6.4 Debian Lenny TeXLive 2007 Failure Both files /fr/UserGuide.lyx and varioref_error.lyx compile OK here: 1.6.4 Ubuntu 9.04TeXLive 2008 Ignacio
Re: Compilation error in French with varioref and hyperref
Works on Mac latest version of LyX and OS. /Anders On 1 sep 2009, at 09.18, Jean-Pierre Chrétien wrote: Hello, With my installation, I get an error when creating the pdf version of the UserGuide, that I narrowed down to the attached simple example. Before taking into consideration the solution that I proposed (the source code must be patched), the developers would like to understand why nobody ever posted about this bug. Would you be so kind to load the attached file in lyx and try to view it as PDF, then to feed back the result ? Here is my record: Lyx version OS TeX distributionResult 1.6.4 Debian Lenny TeXLive 2007 Failure TIA for your answers. -- Jean-Pierre
Re: Compilation error in French with varioref and hyperref
Jean-Pierre Chrétien wrote: > Would you be so kind to load the attached file in lyx and try to view it > as PDF, then to feed back the result ? Lyx version OS TeX distribution Result 1.6.4 openSuse 11.1 TeXLive 2008 No Failure Jürgen
Compilation error in French with varioref and hyperref
Hello, With my installation, I get an error when creating the pdf version of the UserGuide, that I narrowed down to the attached simple example. Before taking into consideration the solution that I proposed (the source code must be patched), the developers would like to understand why nobody ever posted about this bug. Would you be so kind to load the attached file in lyx and try to view it as PDF, then to feed back the result ? Here is my record: Lyx version OS TeX distributionResult 1.6.4 Debian Lenny TeXLive 2007 Failure TIA for your answers. -- Jean-Pierre varioref_error.lyx Description: application/lyx
Re: using hyperref with Hebrew documents
Hebrew+hyperref works well using XeTex and "bidi" package. Unfortunately,
LyX's stable version dose not support XeTeX.
I could not get any output for Hebrew and hyperref using LaTeX on Tex-Live.
Ronen.
On Mon, Jun 29, 2009 at 10:41 PM, Orgad Shaneh wrote:
> Hello,
>
> When I use hyperref in conjunction with babel, and the document
> language is defined as Hebrew, it doesn't compile.
>
> I tried both MiKTeX and TeXlive, The message I'm getting is:
> ! pdfTeX error (ext4): pdf_link_stack empty, \pdfendlink used without
> \pdfstart
> link?.
> \atbeg...@output ...ipout \box \AtBeginShipoutBox
> \fi \fi
> l.13 \pagebreak{
>}
> ! ==> Fatal error occurred, no output PDF file produced!
>
> Here's an example document. Parts of it are in Hebrew, codepage 1255.
>
> %% LyX 1.6.2 created this file. For more info, see http://www.lyx.org/.
> %% Do not edit unless you really know what you are doing.
> \documentclass[english,hebrew]{article}
> \usepackage[T1]{fontenc}
> \usepackage[latin9,cp1255]{inputenc}
> \setlength{\parskip}{\medskipamount}
> \setlength{\parindent}{0pt}
> \usepackage{babel}
>
> \usepackage[unicode=true,
> bookmarks=true,bookmarksnumbered=false,bookmarksopen=false,
> breaklinks=true,pdfborder={0 0 1},backref=false,colorlinks=false]
> {hyperref}
>
> \makeatletter
> %% Textclass specific LaTeX commands.
> \usepackage{theorem}
> \theorembodyfont{\upshape}
> \newtheorem{theorem}{\R{משפט}}[section]
> \atbegindocument{\m...@lr\thetheorem}
>
> \makeatother
>
> \begin{document}
>
> \title{בדיקה}
>
> \maketitle
> \tableofcontents{}
>
> \pagebreak{}
>
>
> \section{סעיף ראשון}
>
>
> \subsection{תת-סעיף ראשון}
>
> לה לה
>
> לי לי
>
> לו לו
>
> \pagebreak{}
>
>
> \section{סעיף שני}
>
>
> \subsection{תת-סעיף ראשון}
>
> לה לה
>
>
> \subsection{תת-סעיף שני}
>
> לי לי
> \end{document}
>
using hyperref with Hebrew documents
Hello,
When I use hyperref in conjunction with babel, and the document
language is defined as Hebrew, it doesn't compile.
I tried both MiKTeX and TeXlive, The message I'm getting is:
! pdfTeX error (ext4): pdf_link_stack empty, \pdfendlink used without \pdfstart
link?.
\atbeg...@output ...ipout \box \AtBeginShipoutBox
\fi \fi
l.13 \pagebreak{
}
! ==> Fatal error occurred, no output PDF file produced!
Here's an example document. Parts of it are in Hebrew, codepage 1255.
%% LyX 1.6.2 created this file. For more info, see http://www.lyx.org/.
%% Do not edit unless you really know what you are doing.
\documentclass[english,hebrew]{article}
\usepackage[T1]{fontenc}
\usepackage[latin9,cp1255]{inputenc}
\setlength{\parskip}{\medskipamount}
\setlength{\parindent}{0pt}
\usepackage{babel}
\usepackage[unicode=true,
bookmarks=true,bookmarksnumbered=false,bookmarksopen=false,
breaklinks=true,pdfborder={0 0 1},backref=false,colorlinks=false]
{hyperref}
\makeatletter
%% Textclass specific LaTeX commands.
\usepackage{theorem}
\theorembodyfont{\upshape}
\newtheorem{theorem}{\R{משפט}}[section]
\atbegindocument{\m...@lr\thetheorem}
\makeatother
\begin{document}
\title{בדיקה}
\maketitle
\tableofcontents{}
\pagebreak{}
\section{סעיף ראשון}
\subsection{תת-סעיף ראשון}
לה לה
לי לי
לו לו
\pagebreak{}
\section{סעיף שני}
\subsection{תת-סעיף ראשון}
לה לה
\subsection{תת-סעיף שני}
לי לי
\end{document}
Re: hyperref bug with parent/child documents?
Bug #5941 http://www.lyx.org/trac/ticket/5941 On May 11, 2009, at 1:24 PM, Pavel Sanda wrote: Jürgen Spitzmüller wrote: James C. Sutherland wrote: I think I found a LyX bug. LyX 1.6.2, Mac OSX 10.5.6 1. Create a parent document and turn off hyperref support (Document- Settings->PDF Properties, deselct hyperref) 2. Create a child document with hyperref support enabled. 3. Include the child in the parent. At this point, the LaTeX source code for the parent now has hyperref included in it. I thought that parent document settings override child document settings. Is this a bug? I'd say so, yes. Hyperref should only be loaded if either turned on in the master or if a master or a child requests it (e.g., when you use a href hyperlink). unfortunately this uncover more general bug in our latex generation of master/child documents. we are not able to distinguish child/master in validate() so things are added to latexparameters and returned back to master... i just checked few other parameters from document settings and it has the same problem (eg use true small caps or background color). i'm not sure about the solution. maybe to change validate prototype adding bool in_child. CC-ing devel list. Please check whether this is already reported, and if not, file a bug report. yes, please fill the bug report. pavel
Re: hyperref bug with parent/child documents?
Jürgen Spitzmüller wrote: > James C. Sutherland wrote: > > I think I found a LyX bug. LyX 1.6.2, Mac OSX 10.5.6 > > > > 1. Create a parent document and turn off hyperref support (Document- > > >Settings->PDF Properties, deselct hyperref) > > 2. Create a child document with hyperref support enabled. > > 3. Include the child in the parent. > > > > At this point, the LaTeX source code for the parent now has hyperref > > included in it. I thought that parent document settings override > > child document settings. Is this a bug? > > I'd say so, yes. Hyperref should only be loaded if either turned on in the > master or if a master or a child requests it (e.g., when you use a href > hyperlink). unfortunately this uncover more general bug in our latex generation of master/child documents. we are not able to distinguish child/master in validate() so things are added to latexparameters and returned back to master... i just checked few other parameters from document settings and it has the same problem (eg use true small caps or background color). i'm not sure about the solution. maybe to change validate prototype adding bool in_child. CC-ing devel list. > Please check whether this is already reported, and if not, file a bug report. yes, please fill the bug report. pavel
Re: hyperref bug with parent/child documents?
James C. Sutherland wrote: > I think I found a LyX bug. LyX 1.6.2, Mac OSX 10.5.6 > > 1. Create a parent document and turn off hyperref support (Document- > >Settings->PDF Properties, deselct hyperref) > 2. Create a child document with hyperref support enabled. > 3. Include the child in the parent. > > At this point, the LaTeX source code for the parent now has hyperref > included in it. I thought that parent document settings override > child document settings. Is this a bug? I'd say so, yes. Hyperref should only be loaded if either turned on in the master or if a master or a child requests it (e.g., when you use a href hyperlink). Please check whether this is already reported, and if not, file a bug report. Jürgen
hyperref bug with parent/child documents?
I think I found a LyX bug. LyX 1.6.2, Mac OSX 10.5.6 1. Create a parent document and turn off hyperref support (Document- >Settings->PDF Properties, deselct hyperref) 2. Create a child document with hyperref support enabled. 3. Include the child in the parent. At this point, the LaTeX source code for the parent now has hyperref included in it. I thought that parent document settings override child document settings. Is this a bug? See attached example files. The .tex files were generated by exporting the parent lyx file to LaTeX. James parent.lyx Description: Binary data child.lyx Description: Binary data child.tex Description: Binary data parent.tex Description: Binary data
Re: hyperref conflicts with cite package?
On Tue, Apr 28, 2009 at 11:10 AM, James C. Sutherland
wrote:
> If I turn on hyperref support, then the cite package breaks. Specifically,
> citations that would normally appear as [5-9] now appear as [5,6,7,8,9]. If
> I turn off hyperref then it works again.
>
> Is this a package conflict, or a bug in LyX?
>
> LyX 1.6.2, Mac OSX 10.5.6
>From the hyperref documentation:
cite
This is from Mike Shell:
> cite.sty cannot currently be used with hyperref.
> However, I can do a workaround via:
>
> \makeatletter
> \def\...@parse{\typeout{this is a fake Natbib command to fool Hyperref.}}
> \makeatother
>
> \usepackage[hypertex]{hyperref}
>
> so that hyperref will not redefine any of the biblabel stuff - so cite.sty
> will work as normal - although the citations will not be hyperlinked, of
> course (But this may not be an issue for many people).
Bennett
hyperref conflicts with cite package?
If I turn on hyperref support, then the cite package breaks. Specifically, citations that would normally appear as [5-9] now appear as [5,6,7,8,9]. If I turn off hyperref then it works again. Is this a package conflict, or a bug in LyX? LyX 1.6.2, Mac OSX 10.5.6
Re: hyperref support and babel-spanish commands conflict
2009/3/8, Ignacio García : > See you please sample.lyx file. Where is it!? Sorry Regards Ignacio sample.lyx Description: application/lyx
Re: hyperref support and babel-spanish commands conflict
2009/3/7, Uwe Stöhr :
> Ignacio García schrieb:
>
>> When I check the hyperref support in LyX document setting, the
>> spanish.ldf user options don't work. babel is loaded before.
>>
>> However, if I insert manually hyperref in the LyX latex preamble,
>> spanish user commands work now. babel is loaded after.
>
> This doesn't work for me, see below. Can you send me please an example LyX
> file?
You are right. Here it compiles because there was my stupid error: I
have loaded hyperref but I had not used it in the document. Inserting
a simple hyperlink, KO. (But this method works in 1.5.5)
> The problem is that hyperref has to be loaded _after_ babel. Unfortunately
> Spanish support is a bit
> different that any other babel language support.
Oh yes, I know very well! :-)
> I think I read recently that the Spanish babel
> maintainer will change this or perhaps has already changed it in the latest
> babel release.
I have the last version... As the author has just opened a new forum,
there I shall raise this issue.
>
>> Here is the relevant latex output in both cases:
>>
>> Hyperref loaded in LyX document setting:
>>
>> \documentclass[spanish]{article}
>> \usepackage[T1]{fontenc}
>> \usepackage[latin9]{inputenc}
>> \usepackage{babel}
>>
>> \usepackage[unicode=true, pdfusetitle,
>> bookmarks=true,bookmarksnumbered=false,bookmarksopen=false,
>> breaklinks=false,pdfborder={0 0 1},backref=false,colorlinks=false]
>> {hyperref}
>>
>> %%%%%% User specified LaTeX commands.
>> \def\spanishoptions{es-minimal}
>>
>> \begin{document}
>
> Hmm, that woks/compiles here.
>
>> Hyperref loaded in LyX latex preamble:
Yes, it works/compiles for me too, but {es-minimal} doesn't work. (see
sample please)
>>
>> \documentclass[spanish]{article}
>> \usepackage[T1]{fontenc}
>> \usepackage[latin9]{inputenc}
>>
>> %% User specified LaTeX commands.
>> \def\spanishoptions{es-minimal}
>> \usepackage[unicode=true, pdfusetitle,
>> bookmarks=true,bookmarksnumbered=false,bookmarksopen=false,
>> breaklinks=false,pdfborder={0 0 1},backref=false,colorlinks=false]
>> {hyperref}
>>
>> \usepackage{babel}
>>
>> \begin{document}
>
> This doesn't compile here, because babel must be loaded _before_
> \def\spanishoptions{es-minimal},
> because otherwise \spanishoptions is not defined.
Is that related with the order in tex file? See you please sample.lyx file.
Thanks a lot!
Regards
Ignacio
