This will be in 2.4.0.
On 12/25/22 11:41, Richard Kimberly Heck wrote:
On 12/23/22 13:14, tush via lyx-users wrote:
This is a follow up to a question on Latex.org:
https://latex.org/forum/viewtopic.php?t=26966
I want to create a phone call link in my pdf, so the latex code would be
On 12/23/22 13:14, tush via lyx-users wrote:
This is a follow up to a question on Latex.org:
https://latex.org/forum/viewtopic.php?t=26966
I want to create a phone call link in my pdf, so the latex code would be
\href{tel:+1202999}{+1--202--999--}
But when I use the hyperlink inset
On 02/16/2012 04:29 PM, Csikos Bela wrote:
Hello:
I would like to include URL fields of the bibtex file in the bibliography as
real clickable links. How can I do it? Currently the content of the URL fields
looks like regular text.
You need to use the \hyperlink command, I'd assume.
Richard
On 02/16/2012 04:29 PM, Csikos Bela wrote:
Hello:
I would like to include URL fields of the bibtex file in the bibliography as
real clickable links. How can I do it? Currently the content of the URL fields
looks like regular text.
You need to use the \hyperlink command, I'd assume.
Richard
On 02/16/2012 04:29 PM, Csikos Bela wrote:
Hello:
I would like to include URL fields of the bibtex file in the bibliography as
real clickable links. How can I do it? Currently the content of the URL fields
looks like regular text.
You need to use the \hyperlink command, I'd assume.
Richard
On 25/05/2011 10:42 AM, Patrick Dupre wrote:
Hello,
Can I create an hyperlink to another lyx file ?
Thank.
Currently LyX does not do that for you.
You can do this in latex following the instructions here:
http://www.tex.ac.uk/cgi-bin/texfaq2html?label=extref
You will need to use TeX code
On 25/05/2011 10:42 AM, Patrick Dupre wrote:
Hello,
Can I create an hyperlink to another lyx file ?
Thank.
Currently LyX does not do that for you.
You can do this in latex following the instructions here:
http://www.tex.ac.uk/cgi-bin/texfaq2html?label=extref
You will need to use TeX code
On 25/05/2011 10:42 AM, Patrick Dupre wrote:
Hello,
Can I create an hyperlink to another lyx file ?
Thank.
Currently LyX does not do that for you.
You can do this in latex following the instructions here:
http://www.tex.ac.uk/cgi-bin/texfaq2html?label=extref
You will need to use TeX code
Sam Lewis stroboscopicallyconfluent at yahoo.co.uk writes:
What is the purpose of right clicking on a hyperlink *inside* LyX?
None.
Reproduce: [Insert] [Hyperlink]; add a link; right click on inserted
hyperlink
icon and the following pop up message appears: No action defined!
What
icon and the following pop up message appears: No action defined!
What can I define where?
Absent your modifying the source code, I suspect you cannot define any
actions.
I see, this is just some kind of place holder in the source. Why not use this
for opening the defined link? Might be
Sam Lewis stroboscopicallyconfluent at yahoo.co.uk writes:
Why not use this
for opening the defined link? Might be useful to improve the
writing-reading-writing flow.
Not unreasonable. You might want to enter a Trac ticket for it as an
enhancement (after checking to be sure there isn't
Sam Lewis stroboscopicallyconfluent at yahoo.co.uk writes:
What is the purpose of right clicking on a hyperlink *inside* LyX?
None.
Reproduce: [Insert] [Hyperlink]; add a link; right click on inserted
hyperlink
icon and the following pop up message appears: No action defined!
What
icon and the following pop up message appears: No action defined!
What can I define where?
Absent your modifying the source code, I suspect you cannot define any
actions.
I see, this is just some kind of place holder in the source. Why not use this
for opening the defined link? Might be
Sam Lewis stroboscopicallyconfluent at yahoo.co.uk writes:
Why not use this
for opening the defined link? Might be useful to improve the
writing-reading-writing flow.
Not unreasonable. You might want to enter a Trac ticket for it as an
enhancement (after checking to be sure there isn't
Sam Lewis yahoo.co.uk> writes:
>
> What is the purpose of right clicking on a hyperlink *inside* LyX?
None.
>
> Reproduce: [Insert] > [Hyperlink]; add a link; right click on inserted
> hyperlink
> icon and the following pop up message appears: "No action defined!"
>
> What can I define
> > icon and the following pop up message appears: "No action defined!"
> > What can I define where?
> Absent your modifying the source code, I suspect you cannot define any
> actions.
I see, this is just some kind of place holder in the source. Why not use this
for opening the defined link?
Sam Lewis yahoo.co.uk> writes:
>
> Why not use this
> for opening the defined link? Might be useful to improve the
> writing-reading-writing flow.
>
Not unreasonable. You might want to enter a Trac ticket for it as an
enhancement (after checking to be sure there isn't already such a ticket
2010/6/29 Guenter Milde mi...@users.berlios.de:
On 2010-06-28, Manveru wrote:
To all it may concern not reading Trac - I've just added following comment:
I would like to enhance this idea with an option to display an small
icon before the text, like WikiMedia does on its pages.
This method
2010/6/29 Guenter Milde mi...@users.berlios.de:
On 2010-06-28, Manveru wrote:
To all it may concern not reading Trac - I've just added following comment:
I would like to enhance this idea with an option to display an small
icon before the text, like WikiMedia does on its pages.
This method
2010/6/29 Guenter Milde :
> On 2010-06-28, Manveru wrote:
>> To all it may concern not reading Trac - I've just added following comment:
>
>> I would like to enhance this idea with an option to display an small
>> icon before the text, like WikiMedia does on its pages.
>
>>
To all it may concern not reading Trac - I've just added following comment:
I would like to enhance this idea with an option to display an small
icon before the text, like WikiMedia does on its pages.
This method my apply to all other small insets, like footnote, label,
etc. Icons may contain
On 2010-06-28, Manveru wrote:
To all it may concern not reading Trac - I've just added following comment:
I would like to enhance this idea with an option to display an small
icon before the text, like WikiMedia does on its pages.
This method my apply to all other small insets, like
To all it may concern not reading Trac - I've just added following comment:
I would like to enhance this idea with an option to display an small
icon before the text, like WikiMedia does on its pages.
This method my apply to all other small insets, like footnote, label,
etc. Icons may contain
On 2010-06-28, Manveru wrote:
To all it may concern not reading Trac - I've just added following comment:
I would like to enhance this idea with an option to display an small
icon before the text, like WikiMedia does on its pages.
This method my apply to all other small insets, like
To all it may concern not reading Trac - I've just added following comment:
I would like to enhance this idea with an option to display an small
icon before the text, like WikiMedia does on its pages.
This method my apply to all other small insets, like footnote, label,
etc. Icons may contain
On 2010-06-28, Manveru wrote:
> To all it may concern not reading Trac - I've just added following comment:
> I would like to enhance this idea with an option to display an small
> icon before the text, like WikiMedia does on its pages.
> This method my apply to all other small insets, like
On 2010-06-24, Vincent van Ravesteijn wrote:
Hi,
The current hyperlink display (at least in the doc classes I've tried) is as
follows:
[hyperlink: text limited in width]
Would it be possible to have a more conventional display, eg not having the
word hyperlink preceeding the text, not having
I've added an enhancement request:
http://www.lyx.org/trac/ticket/6788
Best,
-Jose
Jose Quesada, PhD.
Max Planck Institute,
Center for Adaptive Behavior and Cognition,
Berlin
http://www.josequesada.name/
http://twitter.com/Quesada
On Fri, Jun 25, 2010 at 10:05 AM, Guenter Milde
On 2010-06-24, Vincent van Ravesteijn wrote:
Hi,
The current hyperlink display (at least in the doc classes I've tried) is as
follows:
[hyperlink: text limited in width]
Would it be possible to have a more conventional display, eg not having the
word hyperlink preceeding the text, not having
I've added an enhancement request:
http://www.lyx.org/trac/ticket/6788
Best,
-Jose
Jose Quesada, PhD.
Max Planck Institute,
Center for Adaptive Behavior and Cognition,
Berlin
http://www.josequesada.name/
http://twitter.com/Quesada
On Fri, Jun 25, 2010 at 10:05 AM, Guenter Milde
On 2010-06-24, Vincent van Ravesteijn wrote:
>> Hi,
>> The current hyperlink display (at least in the doc classes I've tried) is as
>> follows:
>> [hyperlink: text limited in width]
>> Would it be possible to have a more conventional display, eg not having the
>> word hyperlink preceeding the
I've added an enhancement request:
http://www.lyx.org/trac/ticket/6788
Best,
-Jose
Jose Quesada, PhD.
Max Planck Institute,
Center for Adaptive Behavior and Cognition,
Berlin
http://www.josequesada.name/
http://twitter.com/Quesada
On Fri, Jun 25, 2010 at 10:05 AM, Guenter Milde
On 6/24/2010 1:27 AM, Jacob Heimark wrote:
I am a newb to LyX and LaTeX. I apologize if this is (a) not the right
forum/locale to ask my question in
and (b) the answer to this question is somewhere on the website and I
am just too stupid to find it (I spent
several hours searching - at least I
Hi,
The current hyperlink display (at least in the doc classes I've tried) is as
follows:
[hyperlink: text limited in width]
Would it be possible to have a more conventional display, eg not having the
word hyperlink preceeding the text, not having the limited width, and say
having it format
On 6/24/2010 1:27 AM, Jacob Heimark wrote:
I am a newb to LyX and LaTeX. I apologize if this is (a) not the right
forum/locale to ask my question in
and (b) the answer to this question is somewhere on the website and I
am just too stupid to find it (I spent
several hours searching - at least I
Hi,
The current hyperlink display (at least in the doc classes I've tried) is as
follows:
[hyperlink: text limited in width]
Would it be possible to have a more conventional display, eg not having the
word hyperlink preceeding the text, not having the limited width, and say
having it format
On 6/24/2010 1:27 AM, Jacob Heimark wrote:
I am a newb to LyX and LaTeX. I apologize if this is (a) not the right
forum/locale to ask my question in
and (b) the answer to this question is somewhere on the website and I
am just too stupid to find it (I spent
several hours searching - at least I
> Hi,
> The current hyperlink display (at least in the doc classes I've tried) is as
> follows:
> [hyperlink: text limited in width]
> Would it be possible to have a more conventional display, eg not having the
> word hyperlink preceeding the text, not having the limited width, and say
> having it
Uwe Stöhr wrote:
Michael Wojcik schrieb:
As said this is a bug in LyX I will fix soon. The LyX will automatically
translate \ to / etc.
I don't see how that's a LyX bug.
It is a bug, because \ is not allowed as argument of \href and therefore
you get LaTeX errors.
Ah, I see. Thanks for
Uwe Stöhr wrote:
Michael Wojcik schrieb:
As said this is a bug in LyX I will fix soon. The LyX will automatically
translate \ to / etc.
I don't see how that's a LyX bug.
It is a bug, because \ is not allowed as argument of \href and therefore
you get LaTeX errors.
Ah, I see. Thanks for
Uwe Stöhr wrote:
> Michael Wojcik schrieb:
>>> As said this is a bug in LyX I will fix soon. The LyX will automatically
>>> translate "\" to "/" etc.
>>
>> I don't see how that's a LyX bug.
>
> It is a bug, because \ is not allowed as argument of \href and therefore
> you get LaTeX errors.
Ah, I
Hubert Christiaen wrote:
An URL is composed of
- a protocol part ended with ':' ftp:' 'http:' or 'file:'
This is the URI scheme. It doesn't necessarily name a protocol.
- an address of the server starting with '//' and ending in '/'
if the server is the localmachine, one can put
Tao Cumplido wrote:
[I wrote:]
Is that a bug? file:C:\file.txt is not a valid URL. It should be
file:///c:/file.txt. (Actually, even that isn't strictly valid; the
c: ought to be c|. But everyone uses and supports c:.)
Ok that kind of works.
But how am I supposed to know that the directory
Uwe Stöhr wrote:
As said this is a bug in LyX I will fix soon. The LyX will automatically
translate \ to / etc.
I don't see how that's a LyX bug. Maybe it's a nice feature, though it
seems a bit arbitrary. LyX can't also escape reserved characters in
the URL, for example, because it can't
Michael Wojcik schrieb:
As said this is a bug in LyX I will fix soon. The LyX will automatically
translate \ to / etc.
I don't see how that's a LyX bug.
It is a bug, because \ is not allowed as argument of \href and therefore you
get LaTeX errors.
regards Uwe
Tao Cumplido schrieb:
I tried to call a simple text file from C:\file.txt but got the following error:
Text\href{file:C:\file.txt}
{file-link}
The control sequence at the end of the top line
of your error message was never \def'ed.
I fixed this now for the
Hubert Christiaen wrote:
An URL is composed of
- a protocol part ended with ':' ftp:' 'http:' or 'file:'
This is the URI scheme. It doesn't necessarily name a protocol.
- an address of the server starting with '//' and ending in '/'
if the server is the localmachine, one can put
Tao Cumplido wrote:
[I wrote:]
Is that a bug? file:C:\file.txt is not a valid URL. It should be
file:///c:/file.txt. (Actually, even that isn't strictly valid; the
c: ought to be c|. But everyone uses and supports c:.)
Ok that kind of works.
But how am I supposed to know that the directory
Uwe Stöhr wrote:
As said this is a bug in LyX I will fix soon. The LyX will automatically
translate \ to / etc.
I don't see how that's a LyX bug. Maybe it's a nice feature, though it
seems a bit arbitrary. LyX can't also escape reserved characters in
the URL, for example, because it can't
Michael Wojcik schrieb:
As said this is a bug in LyX I will fix soon. The LyX will automatically
translate \ to / etc.
I don't see how that's a LyX bug.
It is a bug, because \ is not allowed as argument of \href and therefore you
get LaTeX errors.
regards Uwe
Tao Cumplido schrieb:
I tried to call a simple text file from C:\file.txt but got the following error:
Text\href{file:C:\file.txt}
{file-link}
The control sequence at the end of the top line
of your error message was never \def'ed.
I fixed this now for the
Hubert Christiaen wrote:
> An URL is composed of
> - a protocol part ended with ':' ftp:' 'http:' or 'file:'
This is the URI scheme. It doesn't necessarily name a "protocol".
> - an address of the server starting with '//' and ending in '/'
> if the server is the localmachine, one can put
Tao Cumplido wrote:
>[I wrote:]
>> Is that a bug? "file:C:\file.txt" is not a valid URL. It should be
>> "file:///c:/file.txt". (Actually, even that isn't strictly valid; the
>> "c:" ought to be "c|". But everyone uses and supports "c:".)
>
> Ok that kind of works.
> But how am I supposed to know
Uwe Stöhr wrote:
>
> As said this is a bug in LyX I will fix soon. The LyX will automatically
> translate "\" to "/" etc.
I don't see how that's a LyX bug. Maybe it's a nice feature, though it
seems a bit arbitrary. LyX can't also escape reserved characters in
the URL, for example, because it
Michael Wojcik schrieb:
As said this is a bug in LyX I will fix soon. The LyX will automatically
translate "\" to "/" etc.
I don't see how that's a LyX bug.
It is a bug, because \ is not allowed as argument of \href and therefore you
get LaTeX errors.
regards Uwe
Tao Cumplido schrieb:
I tried to call a simple text file from C:\file.txt but got the following error:
Text\href{file:C:\file.txt}
{file-link}
The control sequence at the end of the top line
of your error message was never \def'ed.
I fixed this now for the
Uwe Stöhr wrote:
Tao Cumplido schrieb:
I tried to call a simple text file from C:\file.txt but got the
following error:
Text\href{file:C:\file.txt}
{file-link}
The control sequence at the end of the top line
of your error message was never \def'ed.
You
On maandag 12 januari 2009, Tao Cumplido wrote:
file:///c:/file.txt. (Actually, even that isn't strictly valid; the
c: ought to be c|. But everyone uses and supports c:.)
Ok that kind of works.
But how am I supposed to know that the directory has to be written like
this? There's no mention
Tao Cumplido schrieb:
But how am I supposed to know that the directory has to be written like this?
There's no mention about this in the Hyperlink-chapter of the manual.
As said this is a bug in LyX I will fix soon. The LyX will automatically translate \ to / etc.
Have you reported it at
Uwe Stöhr wrote:
Tao Cumplido schrieb:
I tried to call a simple text file from C:\file.txt but got the
following error:
Text\href{file:C:\file.txt}
{file-link}
The control sequence at the end of the top line
of your error message was never \def'ed.
You
On maandag 12 januari 2009, Tao Cumplido wrote:
file:///c:/file.txt. (Actually, even that isn't strictly valid; the
c: ought to be c|. But everyone uses and supports c:.)
Ok that kind of works.
But how am I supposed to know that the directory has to be written like
this? There's no mention
Tao Cumplido schrieb:
But how am I supposed to know that the directory has to be written like this?
There's no mention about this in the Hyperlink-chapter of the manual.
As said this is a bug in LyX I will fix soon. The LyX will automatically translate \ to / etc.
Have you reported it at
>Uwe Stöhr wrote:
>> Tao Cumplido schrieb:
>>
>>> I tried to call a simple text file from C:\file.txt but got the
>>> following error:
>>>
>>> Text\href{file:C:\file.txt}
{file-link}
>>> The control sequence at the end of the top line
>>> of your error
On maandag 12 januari 2009, Tao Cumplido wrote:
> "file:///c:/file.txt". (Actually, even that isn't strictly valid; the
>
> >"c:" ought to be "c|". But everyone uses and supports "c:".)
>
> Ok that kind of works.
> But how am I supposed to know that the directory has to be written like
> this?
Tao Cumplido schrieb:
But how am I supposed to know that the directory has to be written like this?
There's no mention about this in the Hyperlink-chapter of the manual.
As said this is a bug in LyX I will fix soon. The LyX will automatically translate "\" to "/" etc.
Have you reported it at
I include the link this way ...
\href{file:///c:/index.htm}{Click Here: For Index.htm File}
--- On Sun, 1/11/09, Tao Cumplido taocumpl...@gmx.net wrote:
From: Tao Cumplido taocumpl...@gmx.net
Subject: Hyperlink question
To: lyx-users@lists.lyx.org
Date: Sunday, January 11, 2009, 8:21 AM
Tao Cumplido schrieb:
I tried to call a simple text file from C:\file.txt but got the following error:
Text\href{file:C:\file.txt}
{file-link}
The control sequence at the end of the top line
of your error message was never \def'ed.
You found a bug. Can you
Uwe Stöhr wrote:
Tao Cumplido schrieb:
I tried to call a simple text file from C:\file.txt but got the
following error:
Text\href{file:C:\file.txt}
{file-link}
The control sequence at the end of the top line
of your error message was never \def'ed.
You
I include the link this way ...
\href{file:///c:/index.htm}{Click Here: For Index.htm File}
--- On Sun, 1/11/09, Tao Cumplido taocumpl...@gmx.net wrote:
From: Tao Cumplido taocumpl...@gmx.net
Subject: Hyperlink question
To: lyx-users@lists.lyx.org
Date: Sunday, January 11, 2009, 8:21 AM
Tao Cumplido schrieb:
I tried to call a simple text file from C:\file.txt but got the following error:
Text\href{file:C:\file.txt}
{file-link}
The control sequence at the end of the top line
of your error message was never \def'ed.
You found a bug. Can you
Uwe Stöhr wrote:
Tao Cumplido schrieb:
I tried to call a simple text file from C:\file.txt but got the
following error:
Text\href{file:C:\file.txt}
{file-link}
The control sequence at the end of the top line
of your error message was never \def'ed.
You
I include the link this way ...
\href{file:///c:/index.htm}{Click Here: For Index.htm File}
--- On Sun, 1/11/09, Tao Cumplido wrote:
> From: Tao Cumplido
> Subject: Hyperlink question
> To: lyx-users@lists.lyx.org
> Date: Sunday, January 11, 2009,
Tao Cumplido schrieb:
I tried to call a simple text file from C:\file.txt but got the following error:
Text\href{file:C:\file.txt}
{file-link}
The control sequence at the end of the top line
of your error message was never \def'ed.
You found a bug. Can you
Uwe Stöhr wrote:
> Tao Cumplido schrieb:
>
>> I tried to call a simple text file from C:\file.txt but got the
>> following error:
>>
>> Text\href{file:C:\file.txt}
>> {file-link}
>> The control sequence at the end of the top line
>> of your error message was never
With pdflatex still use latin modern fonts (package lmodern)
or the cm-super (needs a lot of memory). There is no need to
use ps2pdf.
Yes, I played around with these a couple weeks ago and I can't remember
why but I decided that the output from ps2pdf with cm-super was the
best... will try again
Nirmal Govind schrieb:
With pdflatex still use latin modern fonts (package lmodern)
or the cm-super (needs a lot of memory). There is no need to
use ps2pdf.
Yes, I played around with these a couple weeks ago and I can't remember
why but I decided that the output from ps2pdf with cm-super was
I prefer latin modern ... ;-) and build my PDF's in general
with VTeX/Free.
I tried out all the combinations again.. the ps2pdf output with cm-super
looked marginally better than ps2pdf with lmodern when viewed on screen
here.. pdflatex with lmodern does look great.. the reason I didn't use
Nirmal Govind schrieb:
I prefer latin modern ... ;-) and build my PDF's in general
with VTeX/Free.
I tried out all the combinations again.. the ps2pdf output with cm-super
looked marginally better than ps2pdf with lmodern when viewed on screen
here.. pdflatex with lmodern does look great.. the
did you ever try the sequence eps2eps and then epstopdf?
Yes, I did the last time when Angus suggested it.. it gave me an error
then (not sure if it was eps2eps or epstopdf) but now eps2eps converts
to eps and then the epstopdf works... (may be cos I'm trying different
figures) ... but the
With pdflatex still use latin modern fonts (package lmodern)
or the cm-super (needs a lot of memory). There is no need to
use ps2pdf.
Yes, I played around with these a couple weeks ago and I can't remember
why but I decided that the output from ps2pdf with cm-super was the
best... will try again
Nirmal Govind schrieb:
With pdflatex still use latin modern fonts (package lmodern)
or the cm-super (needs a lot of memory). There is no need to
use ps2pdf.
Yes, I played around with these a couple weeks ago and I can't remember
why but I decided that the output from ps2pdf with cm-super was
I prefer latin modern ... ;-) and build my PDF's in general
with VTeX/Free.
I tried out all the combinations again.. the ps2pdf output with cm-super
looked marginally better than ps2pdf with lmodern when viewed on screen
here.. pdflatex with lmodern does look great.. the reason I didn't use
Nirmal Govind schrieb:
I prefer latin modern ... ;-) and build my PDF's in general
with VTeX/Free.
I tried out all the combinations again.. the ps2pdf output with cm-super
looked marginally better than ps2pdf with lmodern when viewed on screen
here.. pdflatex with lmodern does look great.. the
did you ever try the sequence eps2eps and then epstopdf?
Yes, I did the last time when Angus suggested it.. it gave me an error
then (not sure if it was eps2eps or epstopdf) but now eps2eps converts
to eps and then the epstopdf works... (may be cos I'm trying different
figures) ... but the
With pdflatex still use latin modern fonts (package lmodern)
or the cm-super (needs a lot of memory). There is no need to
use ps2pdf.
Yes, I played around with these a couple weeks ago and I can't remember
why but I decided that the output from ps2pdf with cm-super was the
best... will try again
Nirmal Govind schrieb:
With pdflatex still use latin modern fonts (package lmodern)
or the cm-super (needs a lot of memory). There is no need to
use ps2pdf.
Yes, I played around with these a couple weeks ago and I can't remember
why but I decided that the output from ps2pdf with cm-super was
I prefer latin modern ... ;-) and build my PDF's in general
with VTeX/Free.
I tried out all the combinations again.. the ps2pdf output with cm-super
looked marginally better than ps2pdf with lmodern when viewed on screen
here.. pdflatex with lmodern does look great.. the reason I didn't use
Nirmal Govind schrieb:
I prefer latin modern ... ;-) and build my PDF's in general
with VTeX/Free.
I tried out all the combinations again.. the ps2pdf output with cm-super
looked marginally better than ps2pdf with lmodern when viewed on screen
here.. pdflatex with lmodern does look great.. the
did you ever try the sequence eps2eps and then epstopdf?
Yes, I did the last time when Angus suggested it.. it gave me an error
then (not sure if it was eps2eps or epstopdf) but now eps2eps converts
to eps and then the epstopdf works... (may be cos I'm trying different
figures) ... but the
Hi.. I didn't get any response to this question so I'm rephrasing it..
:-) (actually, I found out what the *real* problem is)
The problem is actually not with hyperlinks, the problem is that when a
citation occurs near the end of the line, the citation will extend
beyond the margin if it
Fredag 14. november 2003 15:50, skreiv Nirmal Govind:
Hi.. I didn't get any response to this question so I'm rephrasing it..
:-) (actually, I found out what the *real* problem is)
The problem is actually not with hyperlinks, the problem is that when a
citation occurs near the end of the
Have you tried adding \sloppy to your preamble ?
This will make latex break the line before long words.
Yes, I did try that but sloppy only justifies words on a line, and it
still treats the long citation as a compound word. So although, it does
alleviate the problem, it doesn't completely solve
Alle 16:00, venerdì 14 novembre 2003, Ingar Pareliussen ha scritto:
Fredag 14. november 2003 15:50, skreiv Nirmal Govind:
Hi.. I didn't get any response to this question so I'm rephrasing it..
:-) (actually, I found out what the *real* problem is)
The problem is actually not with
On Fri, Nov 14, 2003 at 09:50:43AM -0500, Nirmal Govind wrote:
The problem is actually not with hyperlinks, the problem is that when a
citation occurs near the end of the line, the citation will extend
beyond the margin if it doesn't fit on that line the problem is
severe when I cite
Nirmal Govind schrieb:
Hi.. I'm using hyperref to generate links in my pdf document.. however,
some of these links extend beyond the margin.. any option that I can set
to avoid this?
did you run ps2pdf or pdflatex?
Herbert
This problem depends on your bibliography style or extra packages you use.
Normally (when using natbib), long citation are broken into lines.
I do use natbib.. I changed the style from asa (Amer. Stat. Assn.) to
plainnat and apalike and it still persists.
did you run ps2pdf or pdflatex?
Nirmal Govind schrieb:
This problem depends on your bibliography style or extra packages you
use.
Normally (when using natbib), long citation are broken into lines.
I do use natbib.. I changed the style from asa (Amer. Stat. Assn.) to
plainnat and apalike and it still persists.
did you
Hi.. I didn't get any response to this question so I'm rephrasing it..
:-) (actually, I found out what the *real* problem is)
The problem is actually not with hyperlinks, the problem is that when a
citation occurs near the end of the line, the citation will extend
beyond the margin if it
Fredag 14. november 2003 15:50, skreiv Nirmal Govind:
Hi.. I didn't get any response to this question so I'm rephrasing it..
:-) (actually, I found out what the *real* problem is)
The problem is actually not with hyperlinks, the problem is that when a
citation occurs near the end of the
Have you tried adding \sloppy to your preamble ?
This will make latex break the line before long words.
Yes, I did try that but sloppy only justifies words on a line, and it
still treats the long citation as a compound word. So although, it does
alleviate the problem, it doesn't completely solve
1 - 100 of 131 matches
Mail list logo