Re: Hyperref support

[Jürgen Spitzmüller via lyx-users]

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

[Jürgen Spitzmüller via lyx-users]

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 support

[Pavel Sanda]

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

[Richard Kimberly Heck]

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

[Pavel Sanda]

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

[Richard Kimberly Heck]

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

[Pavel Sanda]

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

[Richard Kimberly Heck]

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

[Steve Hnizdur]

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

[Daniel]

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

[Richard Kimberly Heck]

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

[Daniel]

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

[Steve Hnizdur]

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: hyperref support and babel-spanish commands conflict

[Ignacio García]

2009/3/7, Uwe Stöhr uwesto...@web.de:
 Ignacio García schrieb:

 When I check the hyperref support in LyX document setting, the
 spanish.ldf user options don't work. babel is loaded before.

 However, if I insert manually hyperref in the LyX latex preamble,
 spanish user commands work now. babel is loaded after.

 This doesn't work for me, see below. Can you send me please an example LyX
 file?

You are right. Here it compiles because there was my stupid error: I
have loaded hyperref but I had not used it in the document. Inserting
a simple hyperlink, KO. (But this method works in 1.5.5)

 The problem is that hyperref has to be loaded _after_ babel. Unfortunately
 Spanish support is a bit
 different that any other babel language support.

Oh yes, I know very well! :-)

 I think I read recently that the Spanish babel
 maintainer will change this or perhaps has already changed it in the latest
 babel release.

I have the last version... As the author has just opened a new forum,
there I shall raise this issue.


 Here is the relevant latex output in both cases:

 Hyperref loaded in LyX document setting:

  \documentclass[spanish]{article}
  \usepackage[T1]{fontenc}
  \usepackage[latin9]{inputenc}
  \usepackage{babel}

  \usepackage[unicode=true, pdfusetitle,
   bookmarks=true,bookmarksnumbered=false,bookmarksopen=false,
   breaklinks=false,pdfborder={0 0 1},backref=false,colorlinks=false]
   {hyperref}

  %% User specified LaTeX commands.
  \def\spanishoptions{es-minimal}

  \begin{document}

 Hmm, that woks/compiles here.

 Hyperref loaded in LyX latex preamble:

Yes, it works/compiles for me too, but {es-minimal} doesn't work. (see
sample please)


  \documentclass[spanish]{article}
  \usepackage[T1]{fontenc}
  \usepackage[latin9]{inputenc}

  %% User specified LaTeX commands.
  \def\spanishoptions{es-minimal}
  \usepackage[unicode=true, pdfusetitle,
   bookmarks=true,bookmarksnumbered=false,bookmarksopen=false,
   breaklinks=false,pdfborder={0 0 1},backref=false,colorlinks=false]
   {hyperref}

  \usepackage{babel}

  \begin{document}

 This doesn't compile here, because babel must be loaded _before_
 \def\spanishoptions{es-minimal},
 because otherwise \spanishoptions is not defined.

Is that related with the order in tex file? See you please sample.lyx file.

Thanks a lot!
Regards
 Ignacio

Re: hyperref support and babel-spanish commands conflict

[Ignacio García]

2009/3/8, Ignacio García ignacio.gmora...@gmail.com:

 See you please sample.lyx file.

Where is it!?
Sorry
Regards
Ignacio


sample.lyx
Description: application/lyx

Re: hyperref support and babel-spanish commands conflict

[Ignacio García]

2009/3/7, Uwe Stöhr uwesto...@web.de:
 Ignacio García schrieb:

 When I check the hyperref support in LyX document setting, the
 spanish.ldf user options don't work. babel is loaded before.

 However, if I insert manually hyperref in the LyX latex preamble,
 spanish user commands work now. babel is loaded after.

 This doesn't work for me, see below. Can you send me please an example LyX
 file?

You are right. Here it compiles because there was my stupid error: I
have loaded hyperref but I had not used it in the document. Inserting
a simple hyperlink, KO. (But this method works in 1.5.5)

 The problem is that hyperref has to be loaded _after_ babel. Unfortunately
 Spanish support is a bit
 different that any other babel language support.

Oh yes, I know very well! :-)

 I think I read recently that the Spanish babel
 maintainer will change this or perhaps has already changed it in the latest
 babel release.

I have the last version... As the author has just opened a new forum,
there I shall raise this issue.


 Here is the relevant latex output in both cases:

 Hyperref loaded in LyX document setting:

  \documentclass[spanish]{article}
  \usepackage[T1]{fontenc}
  \usepackage[latin9]{inputenc}
  \usepackage{babel}

  \usepackage[unicode=true, pdfusetitle,
   bookmarks=true,bookmarksnumbered=false,bookmarksopen=false,
   breaklinks=false,pdfborder={0 0 1},backref=false,colorlinks=false]
   {hyperref}

  %% User specified LaTeX commands.
  \def\spanishoptions{es-minimal}

  \begin{document}

 Hmm, that woks/compiles here.

 Hyperref loaded in LyX latex preamble:

Yes, it works/compiles for me too, but {es-minimal} doesn't work. (see
sample please)


  \documentclass[spanish]{article}
  \usepackage[T1]{fontenc}
  \usepackage[latin9]{inputenc}

  %% User specified LaTeX commands.
  \def\spanishoptions{es-minimal}
  \usepackage[unicode=true, pdfusetitle,
   bookmarks=true,bookmarksnumbered=false,bookmarksopen=false,
   breaklinks=false,pdfborder={0 0 1},backref=false,colorlinks=false]
   {hyperref}

  \usepackage{babel}

  \begin{document}

 This doesn't compile here, because babel must be loaded _before_
 \def\spanishoptions{es-minimal},
 because otherwise \spanishoptions is not defined.

Is that related with the order in tex file? See you please sample.lyx file.

Thanks a lot!
Regards
 Ignacio

Re: hyperref support and babel-spanish commands conflict

[Ignacio García]

2009/3/8, Ignacio García ignacio.gmora...@gmail.com:

 See you please sample.lyx file.

Where is it!?
Sorry
Regards
Ignacio


sample.lyx
Description: application/lyx

Re: hyperref support and babel-spanish commands conflict

[Ignacio García]

2009/3/7, Uwe Stöhr <uwesto...@web.de>:
> Ignacio García schrieb:
>
>> When I check the hyperref support in LyX document setting, the
>> spanish.ldf user options don't work. babel is loaded before.
>>
>> However, if I insert manually hyperref in the LyX latex preamble,
>> spanish user commands work now. babel is loaded after.
>
> This doesn't work for me, see below. Can you send me please an example LyX
> file?

You are right. Here it compiles because there was my stupid error: I
have loaded hyperref but I had not used it in the document. Inserting
a simple hyperlink, KO. (But this method works in 1.5.5)

> The problem is that hyperref has to be loaded _after_ babel. Unfortunately
> Spanish support is a bit
> different that any other babel language support.

Oh yes, I know very well! :-)

> I think I read recently that the Spanish babel
> maintainer will change this or perhaps has already changed it in the latest
> babel release.

I have the last version... As the author has just opened a new forum,
there I shall raise this issue.

>
>> Here is the relevant latex output in both cases:
>>
>> Hyperref loaded in LyX document setting:
>>
>>  \documentclass[spanish]{article}
>>  \usepackage[T1]{fontenc}
>>  \usepackage[latin9]{inputenc}
>>  \usepackage{babel}
>>
>>  \usepackage[unicode=true, pdfusetitle,
>>   bookmarks=true,bookmarksnumbered=false,bookmarksopen=false,
>>   breaklinks=false,pdfborder={0 0 1},backref=false,colorlinks=false]
>>   {hyperref}
>>
>>  %% User specified LaTeX commands.
>>  \def\spanishoptions{es-minimal}
>>
>>  \begin{document}
>
> Hmm, that woks/compiles here.
>
>> Hyperref loaded in LyX latex preamble:

Yes, it works/compiles for me too, but {es-minimal} doesn't work. (see
sample please)

>>
>>  \documentclass[spanish]{article}
>>  \usepackage[T1]{fontenc}
>>  \usepackage[latin9]{inputenc}
>>
>>  %% User specified LaTeX commands.
>>  \def\spanishoptions{es-minimal}
>>  \usepackage[unicode=true, pdfusetitle,
>>   bookmarks=true,bookmarksnumbered=false,bookmarksopen=false,
>>   breaklinks=false,pdfborder={0 0 1},backref=false,colorlinks=false]
>>   {hyperref}
>>
>>  \usepackage{babel}
>>
>>  \begin{document}
>
> This doesn't compile here, because babel must be loaded _before_
> \def\spanishoptions{es-minimal},
> because otherwise \spanishoptions is not defined.

Is that related with the order in tex file? See you please sample.lyx file.

Thanks a lot!
Regards
 Ignacio

Re: hyperref support and babel-spanish commands conflict

[Ignacio García]

2009/3/8, Ignacio García :

> See you please sample.lyx file.

Where is it!?
Sorry
Regards
Ignacio


sample.lyx
Description: application/lyx

hyperref support and babel-spanish commands conflict

[Ignacio García]

Spanish style of babel system provides some user options for fine
settings or special conflicts prevention.

When I check the hyperref support in LyX document setting, the
spanish.ldf user options don't work. babel is loaded before.

However, if I insert manually hyperref in the LyX latex preamble,
spanish user commands work now. babel is loaded after.

Do you think that is right? Is there any mistake in either of the
packages or in LyX?

Thanks in advance
Ignacio García

Here is the relevant latex output in both cases:

Hyperref loaded in LyX document setting:

 \documentclass[spanish]{article}
 \usepackage[T1]{fontenc}
 \usepackage[latin9]{inputenc}
 \usepackage{babel}

 \usepackage[unicode=true, pdfusetitle,
  bookmarks=true,bookmarksnumbered=false,bookmarksopen=false,
  breaklinks=false,pdfborder={0 0 1},backref=false,colorlinks=false]
  {hyperref}

 %% User specified LaTeX commands.
 \def\spanishoptions{es-minimal}

 \begin{document}

Hyperref loaded in LyX latex preamble:

 \documentclass[spanish]{article}
 \usepackage[T1]{fontenc}
 \usepackage[latin9]{inputenc}

 %% User specified LaTeX commands.
 \def\spanishoptions{es-minimal}
 \usepackage[unicode=true, pdfusetitle,
  bookmarks=true,bookmarksnumbered=false,bookmarksopen=false,
  breaklinks=false,pdfborder={0 0 1},backref=false,colorlinks=false]
  {hyperref}

 \usepackage{babel}

 \begin{document}

Re: hyperref support and babel-spanish commands conflict

[Uwe Stöhr]

Ignacio García schrieb:


When I check the hyperref support in LyX document setting, the
spanish.ldf user options don't work. babel is loaded before.

However, if I insert manually hyperref in the LyX latex preamble,
spanish user commands work now. babel is loaded after.


This doesn't work for me, see below. Can you send me please an example LyX file?

The problem is that hyperref has to be loaded _after_ babel. Unfortunately Spanish support is a bit 
different that any other babel language support. I think I read recently that the Spanish babel 
maintainer will change this or perhaps has already changed it in the latest babel release.



Here is the relevant latex output in both cases:

Hyperref loaded in LyX document setting:

 \documentclass[spanish]{article}
 \usepackage[T1]{fontenc}
 \usepackage[latin9]{inputenc}
 \usepackage{babel}

 \usepackage[unicode=true, pdfusetitle,
  bookmarks=true,bookmarksnumbered=false,bookmarksopen=false,
  breaklinks=false,pdfborder={0 0 1},backref=false,colorlinks=false]
  {hyperref}

 %% User specified LaTeX commands.
 \def\spanishoptions{es-minimal}

 \begin{document}


Hmm, that woks/compiles here.


Hyperref loaded in LyX latex preamble:

 \documentclass[spanish]{article}
 \usepackage[T1]{fontenc}
 \usepackage[latin9]{inputenc}

 %% User specified LaTeX commands.
 \def\spanishoptions{es-minimal}
 \usepackage[unicode=true, pdfusetitle,
  bookmarks=true,bookmarksnumbered=false,bookmarksopen=false,
  breaklinks=false,pdfborder={0 0 1},backref=false,colorlinks=false]
  {hyperref}

 \usepackage{babel}

 \begin{document}


This doesn't compile here, because babel must be loaded _before_ \def\spanishoptions{es-minimal}, 
because otherwise \spanishoptions is not defined.


regards Uwe

hyperref support and babel-spanish commands conflict

[Ignacio García]

Spanish style of babel system provides some user options for fine
settings or special conflicts prevention.

When I check the hyperref support in LyX document setting, the
spanish.ldf user options don't work. babel is loaded before.

However, if I insert manually hyperref in the LyX latex preamble,
spanish user commands work now. babel is loaded after.

Do you think that is right? Is there any mistake in either of the
packages or in LyX?

Thanks in advance
Ignacio García

Here is the relevant latex output in both cases:

Hyperref loaded in LyX document setting:

 \documentclass[spanish]{article}
 \usepackage[T1]{fontenc}
 \usepackage[latin9]{inputenc}
 \usepackage{babel}

 \usepackage[unicode=true, pdfusetitle,
  bookmarks=true,bookmarksnumbered=false,bookmarksopen=false,
  breaklinks=false,pdfborder={0 0 1},backref=false,colorlinks=false]
  {hyperref}

 %% User specified LaTeX commands.
 \def\spanishoptions{es-minimal}

 \begin{document}

Hyperref loaded in LyX latex preamble:

 \documentclass[spanish]{article}
 \usepackage[T1]{fontenc}
 \usepackage[latin9]{inputenc}

 %% User specified LaTeX commands.
 \def\spanishoptions{es-minimal}
 \usepackage[unicode=true, pdfusetitle,
  bookmarks=true,bookmarksnumbered=false,bookmarksopen=false,
  breaklinks=false,pdfborder={0 0 1},backref=false,colorlinks=false]
  {hyperref}

 \usepackage{babel}

 \begin{document}

Re: hyperref support and babel-spanish commands conflict

[Uwe Stöhr]

Ignacio García schrieb:


When I check the hyperref support in LyX document setting, the
spanish.ldf user options don't work. babel is loaded before.

However, if I insert manually hyperref in the LyX latex preamble,
spanish user commands work now. babel is loaded after.


This doesn't work for me, see below. Can you send me please an example LyX file?

The problem is that hyperref has to be loaded _after_ babel. Unfortunately Spanish support is a bit 
different that any other babel language support. I think I read recently that the Spanish babel 
maintainer will change this or perhaps has already changed it in the latest babel release.



Here is the relevant latex output in both cases:

Hyperref loaded in LyX document setting:

 \documentclass[spanish]{article}
 \usepackage[T1]{fontenc}
 \usepackage[latin9]{inputenc}
 \usepackage{babel}

 \usepackage[unicode=true, pdfusetitle,
  bookmarks=true,bookmarksnumbered=false,bookmarksopen=false,
  breaklinks=false,pdfborder={0 0 1},backref=false,colorlinks=false]
  {hyperref}

 %% User specified LaTeX commands.
 \def\spanishoptions{es-minimal}

 \begin{document}


Hmm, that woks/compiles here.


Hyperref loaded in LyX latex preamble:

 \documentclass[spanish]{article}
 \usepackage[T1]{fontenc}
 \usepackage[latin9]{inputenc}

 %% User specified LaTeX commands.
 \def\spanishoptions{es-minimal}
 \usepackage[unicode=true, pdfusetitle,
  bookmarks=true,bookmarksnumbered=false,bookmarksopen=false,
  breaklinks=false,pdfborder={0 0 1},backref=false,colorlinks=false]
  {hyperref}

 \usepackage{babel}

 \begin{document}


This doesn't compile here, because babel must be loaded _before_ \def\spanishoptions{es-minimal}, 
because otherwise \spanishoptions is not defined.


regards Uwe

hyperref support and babel-spanish commands conflict

[Ignacio García]

Spanish style of babel system provides some user options for fine
settings or special conflicts prevention.

When I check the hyperref support in LyX document setting, the
spanish.ldf user options don't work. babel is loaded before.

However, if I insert manually hyperref in the LyX latex preamble,
spanish user commands work now. babel is loaded after.

Do you think that is right? Is there any mistake in either of the
packages or in LyX?

Thanks in advance
Ignacio García

Here is the relevant latex output in both cases:

Hyperref loaded in LyX document setting:

 \documentclass[spanish]{article}
 \usepackage[T1]{fontenc}
 \usepackage[latin9]{inputenc}
 \usepackage{babel}

 \usepackage[unicode=true, pdfusetitle,
  bookmarks=true,bookmarksnumbered=false,bookmarksopen=false,
  breaklinks=false,pdfborder={0 0 1},backref=false,colorlinks=false]
  {hyperref}

 %% User specified LaTeX commands.
 \def\spanishoptions{es-minimal}

 \begin{document}

Hyperref loaded in LyX latex preamble:

 \documentclass[spanish]{article}
 \usepackage[T1]{fontenc}
 \usepackage[latin9]{inputenc}

 %% User specified LaTeX commands.
 \def\spanishoptions{es-minimal}
 \usepackage[unicode=true, pdfusetitle,
  bookmarks=true,bookmarksnumbered=false,bookmarksopen=false,
  breaklinks=false,pdfborder={0 0 1},backref=false,colorlinks=false]
  {hyperref}

 \usepackage{babel}

 \begin{document}

Re: hyperref support and babel-spanish commands conflict

[Uwe Stöhr]

Ignacio García schrieb:


When I check the hyperref support in LyX document setting, the
spanish.ldf user options don't work. babel is loaded before.

However, if I insert manually hyperref in the LyX latex preamble,
spanish user commands work now. babel is loaded after.


This doesn't work for me, see below. Can you send me please an example LyX file?

The problem is that hyperref has to be loaded _after_ babel. Unfortunately Spanish support is a bit 
different that any other babel language support. I think I read recently that the Spanish babel 
maintainer will change this or perhaps has already changed it in the latest babel release.



Here is the relevant latex output in both cases:

Hyperref loaded in LyX document setting:

 \documentclass[spanish]{article}
 \usepackage[T1]{fontenc}
 \usepackage[latin9]{inputenc}
 \usepackage{babel}

 \usepackage[unicode=true, pdfusetitle,
  bookmarks=true,bookmarksnumbered=false,bookmarksopen=false,
  breaklinks=false,pdfborder={0 0 1},backref=false,colorlinks=false]
  {hyperref}

 %% User specified LaTeX commands.
 \def\spanishoptions{es-minimal}

 \begin{document}


Hmm, that woks/compiles here.


Hyperref loaded in LyX latex preamble:

 \documentclass[spanish]{article}
 \usepackage[T1]{fontenc}
 \usepackage[latin9]{inputenc}

 %% User specified LaTeX commands.
 \def\spanishoptions{es-minimal}
 \usepackage[unicode=true, pdfusetitle,
  bookmarks=true,bookmarksnumbered=false,bookmarksopen=false,
  breaklinks=false,pdfborder={0 0 1},backref=false,colorlinks=false]
  {hyperref}

 \usepackage{babel}

 \begin{document}


This doesn't compile here, because babel must be loaded _before_ \def\spanishoptions{es-minimal}, 
because otherwise \spanishoptions is not defined.


regards Uwe