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 <skost...@lyx.org> 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 <skost...@lyx.org> 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 <landr...@lyx.org> 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
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
Re: pdfx and hyperref
Am Mittwoch, 2. Dezember 2015 um 11:59:43, schrieb Scott Kostyshak <skost...@lyx.org> > 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
Am Mittwoch, 2. Dezember 2015, 18:28:49 schrieb Kornel Benko: > Am Mittwoch, 2. Dezember 2015 um 11:59:43, schrieb Scott Kostyshak > <skost...@lyx.org> > > 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
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
It Works! Thanks so much Scott
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
alberto.esc...@itc.uji.es 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
Re: Hyperref color links
On Mon, Sep 29, 2014 at 2:18 AM, Alberto Escrig Vidal
alberto.esc...@itc.uji.es 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
Re: Hyperref color links
On Mon, Sep 29, 2014 at 2:18 AM, Alberto Escrig Vidal
<alberto.esc...@itc.uji.es> 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?
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?
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 फ्रेड्रिक नोरोन्या
*فريدريك نورونيا fredericknoro...@gmail.com 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: Turning hyperref off in table of contents
On 25 March 2013 05:20, Frederick FN Noronha फ्रेड्रिक नोरोन्या
*فريدريك نورونيا fredericknoro...@gmail.com 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: Turning hyperref off in table of contents
On 25 March 2013 05:20, Frederick FN Noronha फ्रेड्रिक नोरोन्या
*فريدريك نورونيا <fredericknoro...@gmail.com> 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 sl...@troubleshooters.com 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?
Hi Steve,
Thanks for your reply.
On 15 December 2012 17:51, Steve Litt sl...@troubleshooters.com 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?
Hi Steve,
Thanks for your reply.
On 15 December 2012 17:51, Steve Litt <sl...@troubleshooters.com> 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
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.
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.
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.
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: 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
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 DocumentSettingsPDF-... and load/configure hyperref in the LaTeX preamble. Günter
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: 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
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 DocumentSettingsPDF-... and load/configure hyperref in the LaTeX preamble. Günter
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: 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
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: hyperref and TOC
Csikos Bela bcsikos...@freemail.hu í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: hyperref and TOC
Csikos Bela bcsikos...@freemail.hu í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: hyperref and TOC
Csikos Bela <bcsikos...@freemail.hu> í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 SOLVED
On Thursday 24 March 2011 17:28:57 Jacob Bishop wrote: On Thu, Mar 24, 2011 at 3:10 PM, Steve Litt sl...@troubleshooters.comwrote: 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 SOLVED
On Thursday 24 March 2011 17:28:57 Jacob Bishop wrote: On Thu, Mar 24, 2011 at 3:10 PM, Steve Litt sl...@troubleshooters.comwrote: 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 Thursday 24 March 2011 17:28:57 Jacob Bishop wrote: > On Thu, Mar 24, 2011 at 3:10 PM, Steve Litt <sl...@troubleshooters.com>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
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
Re: More hyperref bogosity
On Thu, Mar 24, 2011 at 3:10 PM, Steve Litt sl...@troubleshooters.comwrote: 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
Re: More hyperref bogosity
On Thu, Mar 24, 2011 at 3:10 PM, Steve Litt sl...@troubleshooters.comwrote: 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
Re: More hyperref bogosity
On Thu, Mar 24, 2011 at 3:10 PM, Steve Litt <sl...@troubleshooters.com>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
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)
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)
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)
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.
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:///path You might try inserting the forward slashes after file:. /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:///path 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: 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: 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.
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.
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:///path You might try inserting the forward slashes after file:. /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:///path 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: 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: 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.
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.
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
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: 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: 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.
