On 08/03/2010 12:13 PM, Jean-Pierre Chrétien wrote:
Richard Heckrgheckat comcast.net writes:
On 07/16/2010 09:41 AM, Uwe Stöhr wrote:
So let's remove \Nameref support then.
Done.
The reference to Textual reference pluspage is still there today,
and creates an
On 08/03/2010 12:13 PM, Jean-Pierre Chrétien wrote:
Richard Heck writes:
On 07/16/2010 09:41 AM, Uwe Stöhr wrote:
So let's remove \Nameref support then.
Done.
The reference to "Textual reference plus" is still there today,
and creates an error:
Richard Heck rgheck at comcast.net writes:
On 07/16/2010 09:41 AM, Uwe Stöhr wrote:
So let's remove \Nameref support then.
Done.
The reference to Textual reference plus page is still there today,
and creates an error:
insets/InsetCommandParams.cpp(256): InsetCommand: Incompatible
Richard Heck comcast.net> writes:
>
> On 07/16/2010 09:41 AM, Uwe Stöhr wrote:
> >
> > So let's remove \Nameref support then.
> >
> Done.
The reference to "Textual reference plus " is still there today,
and creates an error:
insets/InsetCommandParams.cpp(256): InsetCommand: Incompatible
Am 16.07.2010 05:28, schrieb Richard Heck:
I'm starting to think that maybe \Nameref isn't worth supporting and we
should just support \nameref.
I agree. It is impossible to support \Nameref for all languages. As it
is, the output is only correct for (British) English documents and
cannot
On 07/16/2010 09:41 AM, Uwe Stöhr wrote:
So let's remove \Nameref support then.
Done.
rh
Am 16.07.2010 05:28, schrieb Richard Heck:
I'm starting to think that maybe \Nameref isn't worth supporting and we
should just support \nameref.
I agree. It is impossible to support \Nameref for all languages. As it
is, the output is only correct for (British) English documents and
cannot
On 07/16/2010 09:41 AM, Uwe Stöhr wrote:
So let's remove \Nameref support then.
Done.
rh
Jean-Pierre Chrétien jeanpierre.chretien at free.fr writes:
This will use all variants of varioref page handling.
Rather {\nameref{#1} \vpageref{#1}}, the unbrealkable space is not necessary
here (nor with \reftextfaraway in fact, page~xxx can be on the nest line).
And to be cosnisten
Why not
{\nameref{#1}~\vpageref{#1}}
This will use all variants of varioref page handling.
Rather {\nameref{#1} \vpageref{#1}}, the unbrealkable space is not necessary
here (nor with \reftextfaraway in fact, page~xxx can be on the nest line).
Yes, this is the better solution.
On 07/15/2010 09:26 PM, Uwe Stöhr wrote:
Yes, we should omit the single quotes as single quotes are in many
languages only allowed within double quotes. Quotes are also often
only allowed for quotations, citations and proper names. There is
moreover no reason why the name of the referenced
Jean-Pierre Chrétien free.fr> writes:
>
> > This will use all variants of varioref page handling.
>
> Rather {\nameref{#1} \vpageref{#1}}, the unbrealkable space is not necessary
> here (nor with \reftextfaraway in fact, page~xxx can be on the nest line).
>
And to be cosnisten wit the
>> Why not
>>
>> {\nameref{#1}~\vpageref{#1}}
>>
>> This will use all variants of varioref page handling.
>
> Rather {\nameref{#1} \vpageref{#1}}, the unbrealkable space is not necessary
> here (nor with \reftextfaraway in fact, page~xxx can be on the nest line).
Yes, this is the better
On 07/15/2010 09:26 PM, Uwe Stöhr wrote:
Yes, we should omit the single quotes as single quotes are in many
languages only allowed within double quotes. Quotes are also often
only allowed for quotations, citations and proper names. There is
moreover no reason why the name of the referenced
Uwe Stöhr uwestoehr at web.de writes:
There is another issue: The text on page is not yet translated to the
document language.
One manually has to add this preamble code:
\renewcommand*\Nameref[1]{`\nameref{#1}' auf Seite~\pageref{#1}}
auf Seite is hereby the German translation of on
Jean-Pierre Chrétien jeanpierre.chretien at free.fr writes:
Why not
{\nameref{#1}~\vpageref{#1}}
This will use all variants of varioref page handling.
Rather {\nameref{#1} \vpageref{#1}}, the unbrealkable space is not necessary
here (nor with \reftextfaraway in fact, page~xxx
Am 13.07.2010 23:10, schrieb Richard Heck:
So now we just have to figure out the translation issue. Are you sure the
nameref folks have no
interest in fixing this?
Yes, because I asked them to add this feature some time ago when i met the hyperref developer
personally. But it is OK that the
On 07/14/2010 04:05 PM, Uwe Stöhr wrote:
p.s. sorry for my harsh words in my previous email
No problem, Uwe. I know you get over-animated sometimes. But you do owe
me a beer.
rh
ps thanks for the apology, anyway.
Am 14.07.2010 22:41, schrieb Richard Heck:
p.s. sorry for my harsh words in my previous email
No problem, Uwe. I know you get over-animated sometimes. But you do owe me a
beer.
What, what, what?
You do the mistakes, I correct them, I'm the brave one speaking out the truth, fix all
Uwe Stöhr web.de> writes:
>
> There is another issue: The text "on page" is not yet translated to the
document language.
> One manually has to add this preamble code:
>
> \renewcommand*\Nameref[1]{`\nameref{#1}' auf Seite~\pageref{#1}}
>
> "auf Seite" is hereby the German translation of "on
Jean-Pierre Chrétien free.fr> writes:
>
> Why not
>
> {\nameref{#1}~\vpageref{#1}}
>
> This will use all variants of varioref page handling.
Rather {\nameref{#1} \vpageref{#1}}, the unbrealkable space is not necessary
here (nor with \reftextfaraway in fact, page~xxx can be on the
Am 13.07.2010 23:10, schrieb Richard Heck:
So now we just have to figure out the translation issue. Are you sure the
nameref folks have no
interest in fixing this?
Yes, because I asked them to add this feature some time ago when i met the hyperref developer
personally. But it is OK that the
On 07/14/2010 04:05 PM, Uwe Stöhr wrote:
p.s. sorry for my harsh words in my previous email
No problem, Uwe. I know you get over-animated sometimes. But you do owe
me a beer.
rh
ps thanks for the apology, anyway.
Am 14.07.2010 22:41, schrieb Richard Heck:
p.s. sorry for my harsh words in my previous email
No problem, Uwe. I know you get over-animated sometimes. But you do owe me a
beer.
What, what, what?
You do the mistakes, I correct them, I'm the brave one speaking out the truth, fix all
Am 13.07.2010 05:13, schrieb Richard Heck:
I did some test and your implementation works fine for me except of
these:
1. insert a reference, select the style Textual reference and press
APPLY (don't close the dialog)
2. change the style to e.g. Textual reference plus page
Result: the apply
Am 13.07.2010 05:23, schrieb Richard Heck:
There is another issue: The text on page is not yet translated to
the document language.
One manually has to add this preamble code:
\renewcommand*\Nameref[1]{`\nameref{#1}' auf Seite~\pageref{#1}}
auf Seite is hereby the German translation of on
Am 13.07.2010 13:59, schrieb Uwe Stöhr:
We can easily convert this to:
\begin_inset ERT
status collapsed
\begin_layout Plain Layout
\backslash
vref{
\end_layout
\end_inset
sec:dsf
\begin_inset ERT
status collapsed
\begin_layout Plain Layout
}
\end_layout
\end_inset
Sorry, I meant to convert
On 07/13/2010 08:11 AM, Uwe Stöhr wrote:
Am 13.07.2010 13:59, schrieb Uwe Stöhr:
We can easily convert this to:
\begin_inset ERT
status collapsed
\begin_layout Plain Layout
\backslash
vref{
\end_layout
\end_inset
sec:dsf
\begin_inset ERT
status collapsed
\begin_layout Plain Layout
}
On 07/13/2010 08:06 AM, Uwe Stöhr wrote:
Am 13.07.2010 05:23, schrieb Richard Heck:
There is another issue: The text on page is not yet translated to
the document language.
One manually has to add this preamble code:
\renewcommand*\Nameref[1]{`\nameref{#1}' auf Seite~\pageref{#1}}
auf Seite
Am 13.07.2010 15:47, schrieb Richard Heck:
Again, this isn't the issue. What I do has the same effect,
No, it has not, the suer gets a number instead of the name of the reference.
is simpler,
and doesn't use ERT: I just convert the command from \nameref to \ref or
\Nameref to \vref. The
Am 13.07.2010 15:50, schrieb Richard Heck:
There's no lyx2lyx issue,
There is, see my previous mail! OK, I'll change the lyx2lyx routine so
that the result gives the same output for the user.
and the translation issue can be addressed
independently. You're welcome to add your code if you
Uwe Stöhr wrote:
is simpler,
and doesn't use ERT: I just convert the command from \nameref to \ref or
\Nameref to \vref. The point is that this does not produce the same
output as \nameref does and there is no reasonable way to do this.
But this is the reason why this is no option. lyx2lyx
Uwe Stöhr wrote:
Sorry, but I have the feeling that you are a bit lazy with your patch. If
we are not able to translate the reference text, the new feature turns into
a bug as it then only works for English documents. I therefore wanted to
solve this issue before applying.
Could you
On 07/13/2010 12:13 PM, Pavel Sanda wrote:
disclaimer first - i know nothing about the subtleties of varisous XXXref
commands... anyway tend to agree here with Richard to consider this as nameref
bug. if nameref devs do not plan to fix/advance their work its question whether
our dependency on
On 07/13/2010 11:30 AM, Uwe Stöhr wrote:
Am 13.07.2010 15:47, schrieb Richard Heck:
Again, this isn't the issue. What I do has the same effect,
No, it has not, the suer gets a number instead of the name of the
reference.
Sorry, I missed the difference between your first proposal and your
Am 13.07.2010 05:13, schrieb Richard Heck:
I did some test and your implementation works fine for me except of
these:
1. insert a reference, select the style "Textual reference" and press
APPLY (don't close the dialog)
2. change the style to e.g. "Textual reference plus "
Result: the apply
Am 13.07.2010 05:23, schrieb Richard Heck:
There is another issue: The text "on page" is not yet translated to
the document language.
One manually has to add this preamble code:
\renewcommand*\Nameref[1]{`\nameref{#1}' auf Seite~\pageref{#1}}
"auf Seite" is hereby the German translation of
Am 13.07.2010 13:59, schrieb Uwe Stöhr:
We can easily convert this to:
\begin_inset ERT
status collapsed
\begin_layout Plain Layout
\backslash
vref{
\end_layout
\end_inset
sec:dsf
\begin_inset ERT
status collapsed
\begin_layout Plain Layout
}
\end_layout
\end_inset
Sorry, I meant to convert
On 07/13/2010 08:11 AM, Uwe Stöhr wrote:
Am 13.07.2010 13:59, schrieb Uwe Stöhr:
We can easily convert this to:
\begin_inset ERT
status collapsed
\begin_layout Plain Layout
\backslash
vref{
\end_layout
\end_inset
sec:dsf
\begin_inset ERT
status collapsed
\begin_layout Plain Layout
}
On 07/13/2010 08:06 AM, Uwe Stöhr wrote:
Am 13.07.2010 05:23, schrieb Richard Heck:
There is another issue: The text "on page" is not yet translated to
the document language.
One manually has to add this preamble code:
\renewcommand*\Nameref[1]{`\nameref{#1}' auf Seite~\pageref{#1}}
"auf
Am 13.07.2010 15:47, schrieb Richard Heck:
Again, this isn't the issue. What I do has the same effect,
No, it has not, the suer gets a number instead of the name of the reference.
is simpler,
and doesn't use ERT: I just convert the command from \nameref to \ref or
\Nameref to \vref. The
Am 13.07.2010 15:50, schrieb Richard Heck:
There's no lyx2lyx issue,
There is, see my previous mail! OK, I'll change the lyx2lyx routine so
that the result gives the same output for the user.
and the translation issue can be addressed
independently. You're welcome to add your code if you
Uwe Stöhr wrote:
>> is simpler,
>> and doesn't use ERT: I just convert the command from \nameref to \ref or
>> \Nameref to \vref. The point is that this does not produce the same
>> output as \nameref does and there is no reasonable way to do this.
>
> But this is the reason why this is no option.
Uwe Stöhr wrote:
> Sorry, but I have the feeling that you are a bit lazy with your patch. If
> we are not able to translate the reference text, the new feature turns into
> a bug as it then only works for English documents. I therefore wanted to
> solve this issue before applying.
>
>>
On 07/13/2010 12:13 PM, Pavel Sanda wrote:
disclaimer first - i know nothing about the subtleties of varisous XXXref
commands... anyway tend to agree here with Richard to consider this as nameref
bug. if nameref devs do not plan to fix/advance their work its question whether
our dependency on
On 07/13/2010 11:30 AM, Uwe Stöhr wrote:
Am 13.07.2010 15:47, schrieb Richard Heck:
Again, this isn't the issue. What I do has the same effect,
No, it has not, the suer gets a number instead of the name of the
reference.
Sorry, I missed the difference between your first proposal and your
The attached patch implements nameref support in cross-references. The
only thing I'm not sure about, which Uwe mentioned in the bug, is the
precise loading order of packages. If we're loading hyperref anyway,
then there's no issue, since it loads nameref. But if we aren't, then
maybe
On 07/12/2010 06:00 PM, Richard Heck wrote:
The attached patch implements nameref support in cross-references. The
only thing I'm not sure about, which Uwe mentioned in the bug, is the
precise loading order of packages. If we're loading hyperref anyway,
then there's no issue, since it loads
The only thing I'm not sure about, which Uwe mentioned in the bug, is the
precise loading order
of packages.
This doesn't seem to be an issue with the new nameref version because the former conflicts with
memoir and varioref are resolved. I did some test and your implementation works fine
There is another issue: The text on page is not yet translated to the
document language.
One manually has to add this preamble code:
\renewcommand*\Nameref[1]{`\nameref{#1}' auf Seite~\pageref{#1}}
auf Seite is hereby the German translation of on page.
As this is no solution for us I propose
On 07/12/2010 10:04 PM, Uwe Stöhr wrote:
The only thing I'm not sure about, which Uwe mentioned in the bug,
is the precise loading order of packages.
This doesn't seem to be an issue with the new nameref version because
the former conflicts with memoir and varioref are resolved.
OK, good.
On 07/12/2010 10:51 PM, Uwe Stöhr wrote:
There is another issue: The text on page is not yet translated to
the document language.
One manually has to add this preamble code:
\renewcommand*\Nameref[1]{`\nameref{#1}' auf Seite~\pageref{#1}}
auf Seite is hereby the German translation of on page.
The attached patch implements nameref support in cross-references. The
only thing I'm not sure about, which Uwe mentioned in the bug, is the
precise loading order of packages. If we're loading hyperref anyway,
then there's no issue, since it loads nameref. But if we aren't, then
maybe
On 07/12/2010 06:00 PM, Richard Heck wrote:
The attached patch implements nameref support in cross-references. The
only thing I'm not sure about, which Uwe mentioned in the bug, is the
precise loading order of packages. If we're loading hyperref anyway,
then there's no issue, since it loads
> The only thing I'm not sure about, which Uwe mentioned in the bug, is the
precise loading order
> of packages.
This doesn't seem to be an issue with the new nameref version because the former conflicts with
memoir and varioref are resolved. I did some test and your implementation works fine
There is another issue: The text "on page" is not yet translated to the
document language.
One manually has to add this preamble code:
\renewcommand*\Nameref[1]{`\nameref{#1}' auf Seite~\pageref{#1}}
"auf Seite" is hereby the German translation of "on page".
As this is no solution for us I
On 07/12/2010 10:04 PM, Uwe Stöhr wrote:
> The only thing I'm not sure about, which Uwe mentioned in the bug,
is the precise loading order of packages.
This doesn't seem to be an issue with the new nameref version because
the former conflicts with memoir and varioref are resolved.
OK,
On 07/12/2010 10:51 PM, Uwe Stöhr wrote:
There is another issue: The text "on page" is not yet translated to
the document language.
One manually has to add this preamble code:
\renewcommand*\Nameref[1]{`\nameref{#1}' auf Seite~\pageref{#1}}
"auf Seite" is hereby the German translation of "on
58 matches
Mail list logo
