Re: New RefStyle Patch

Helge Hafting wrote: Compatibility meaning: the document still compiles and output still looks good or identical printout to within 1/100 of a mm or bitwise identical pdf file? The first one is good enough for me, but maybe not for everybody? Compatibility means (here): the content of the

Re: New RefStyle Patch

Helge Hafting wrote: > Compatibility meaning: > "the document still compiles and output still looks good" > or "identical printout to within 1/100 of a mm" > or "bitwise identical pdf file"? > > The first one is good enough for me, but maybe not for everybody? Compatibility means (here): the

Re: New RefStyle Patch

Jürgen Spitzmüller wrote: rgheck wrote: Anything seems better to me than allowing the use of both prettyref and refstyle. We'd have to support both in 2.0, and I don't see any nice way to do that. If we are not able to provide full compatibility, we must IMHO. Compatibility meaning: the

Re: New RefStyle Patch

Jürgen Spitzmüller wrote: rgheck wrote: Anything seems better to me than allowing the use of both prettyref and refstyle. We'd have to support both in 2.0, and I don't see any nice way to do that. If we are not able to provide full compatibility, we must IMHO. Compatibility meaning:

Re: New RefStyle Patch

Jürgen Spitzmüller juer...@... writes: Hm. I have in one of my class files this: % Prettyref: \RequirePackage{prettyref} \newrefformat{cha}{Kapitel~\ref{#1}} \newrefformat{sec}{Abschnitt~\ref{#1}} \newrefformat{sub}{Abschnitt~\ref{#1}} \newrefformat{anm}{Anm.~\ref{#1}}

Re: New RefStyle Patch

Jürgen Spitzmüller writes: > > Hm. I have in one of my class files this: > > % Prettyref: > \RequirePackage{prettyref} > \newrefformat{cha}{Kapitel~\ref{#1}} > \newrefformat{sec}{Abschnitt~\ref{#1}} > \newrefformat{sub}{Abschnitt~\ref{#1}} > \newrefformat{anm}{Anm.~\ref{#1}} >

Re: New RefStyle Patch

On 03/21/2010 05:48 AM, Jean-Pierre Chrétien wrote: I think I found an error: - open a new document, - set the document class to report - type in a new chapter named Test and label it: the label reads cha:Test instead of chap:Test Then a formatted reference to the chapter fails. A label

Re: New RefStyle Patch

On 03/21/2010 09:29 AM, Jürgen Spitzmüller wrote: rgheck wrote: So I'll go ahead and commit this if it seems good to Jurgen. I'd like his opinion, too. I didn't have time to test it. I'm fine with it as long as it is guaranteed that old (prettyref and prettyref/varioref combined)

Re: New RefStyle Patch

On 03/21/2010 05:26 AM, Jean-Pierre Chrétien wrote: What should I do on the bugtracker ? Open a fresh bug about varioref targeted to 1.6.6 ? Inserting \usepackage{nameref} (which is just an early loading of the nameref and refcount packages) should not raise issues, unless it needs a format

Re: New RefStyle Patch

rgheck wrote: I'm not sure if we can guarantee that they will be identical, only very close. This is because the default format for refstyle isn't always (and hasn't always) been exactly the same as prettyref's. So you may get slightly different text in certain cases. That's bad. In this

Re: New RefStyle Patch

On 03/22/2010 08:13 AM, Jürgen Spitzmüller wrote: rgheck wrote: I'm not sure if we can guarantee that they will be identical, only very close. This is because the default format for refstyle isn't always (and hasn't always) been exactly the same as prettyref's. So you may get slightly

Re: New RefStyle Patch

rgheck wrote: Anything seems better to me than allowing the use of both prettyref and refstyle. We'd have to support both in 2.0, and I don't see any nice way to do that. If we are not able to provide full compatibility, we must IMHO. I've looked into this, and there are two major

Re: New RefStyle Patch

On 03/22/2010 09:08 AM, Jürgen Spitzmüller wrote: Hm. I have in one of my class files this: % Prettyref: \RequirePackage{prettyref} \newrefformat{cha}{Kapitel~\ref{#1}} \newrefformat{sec}{Abschnitt~\ref{#1}} \newrefformat{sub}{Abschnitt~\ref{#1}} \newrefformat{anm}{Anm.~\ref{#1}}

Re: New RefStyle Patch

Richard Heck wrote: Ultimately, refstyle has much better and more flexible support for this sort of thing. Thus, one can write in LaTeX: \Tabref[vref]{tab:foo} and then you get: table 3 on the previous page Yes, I know. However, I prefer to customize this globally. If I decide (or

Re: New RefStyle Patch

On 03/22/2010 11:59 AM, Jürgen Spitzmüller wrote: Richard Heck wrote: or whatever. So we could support that sort of thing directly in LyX. And refstyle will do other things, too, like plurals and ranges, e.g., sections 3 to 5. Looks promising. I'm eager to see if this can handle

Re: New RefStyle Patch

On 03/21/2010 05:48 AM, Jean-Pierre Chrétien wrote: I think I found an error: - open a new document, - set the document class to report - type in a new chapter named Test and label it: the label reads cha:Test instead of chap:Test Then a formatted reference to the chapter fails. A label

Re: New RefStyle Patch

On 03/21/2010 09:29 AM, Jürgen Spitzmüller wrote: rgheck wrote: So I'll go ahead and commit this if it seems good to Jurgen. I'd like his opinion, too. I didn't have time to test it. I'm fine with it as long as it is guaranteed that old (prettyref and prettyref/varioref combined)

Re: New RefStyle Patch

On 03/21/2010 05:26 AM, Jean-Pierre Chrétien wrote: What should I do on the bugtracker ? Open a fresh bug about varioref targeted to 1.6.6 ? Inserting \usepackage{nameref} (which is just an early loading of the nameref and refcount packages) should not raise issues, unless it needs a format

Re: New RefStyle Patch

rgheck wrote: > I'm not sure if we can guarantee that they will be identical, only very > close. This is because the default format for refstyle isn't always (and > hasn't always) been exactly the same as prettyref's. So you may get > slightly different text in certain cases. That's bad. In

Re: New RefStyle Patch

On 03/22/2010 08:13 AM, Jürgen Spitzmüller wrote: rgheck wrote: I'm not sure if we can guarantee that they will be identical, only very close. This is because the default format for refstyle isn't always (and hasn't always) been exactly the same as prettyref's. So you may get slightly

Re: New RefStyle Patch

rgheck wrote: > Anything seems better to me than allowing the use of both prettyref and > refstyle. We'd have to support both in 2.0, and I don't see any nice way > to do that. If we are not able to provide full compatibility, we must IMHO. > I've looked into this, and there are two major

Re: New RefStyle Patch

On 03/22/2010 09:08 AM, Jürgen Spitzmüller wrote: Hm. I have in one of my class files this: % Prettyref: \RequirePackage{prettyref} \newrefformat{cha}{Kapitel~\ref{#1}} \newrefformat{sec}{Abschnitt~\ref{#1}} \newrefformat{sub}{Abschnitt~\ref{#1}} \newrefformat{anm}{Anm.~\ref{#1}}

Re: New RefStyle Patch

Richard Heck wrote: > Ultimately, refstyle has much better and more flexible support for this > sort of thing. Thus, one can write in LaTeX: > \Tabref[vref]{tab:foo} > and then you get: > table 3 on the previous page Yes, I know. However, I prefer to customize this globally. If I

Re: New RefStyle Patch

On 03/22/2010 11:59 AM, Jürgen Spitzmüller wrote: Richard Heck wrote: or whatever. So we could support that sort of thing directly in LyX. And refstyle will do other things, too, like plurals and ranges, e.g., "sections 3 to 5". Looks promising. I'm eager to see if this can handle

Re: New RefStyle Patch

rgheck rgh...@... writes: On 03/20/2010 04:54 AM, Jean-Pierre Chrétien wrote: rgheckrgh...@... writes: Then all problems due to : being active in French vanish, either coming from the use of varioref or from the use of formatted references. As refstyle make the sensitivity to active

Re: New RefStyle Patch

Jean-Pierre Chrétien jeanpierre.chret...@... writes: rgheck rgh...@... writes: Here's a patch updated to current trunk, since I incremented the format for another reason. There is still a typo which prevents successful conversion: there should be a closing after vreference in

Re: New RefStyle Patch

rgheck wrote: So I'll go ahead and commit this if it seems good to Jurgen. I'd like his opinion, too. I didn't have time to test it. I'm fine with it as long as it is guaranteed that old (prettyref and prettyref/varioref combined) documents come out identical, at least if people do not use

Re: New RefStyle Patch

rgheck writes: > > On 03/20/2010 04:54 AM, Jean-Pierre Chrétien wrote: > > rgheck writes: > > Then all problems due to : being active in French vanish, either coming from the > > use of varioref or from the use of formatted references. > > As refstyle make the

Re: New RefStyle Patch

Jean-Pierre Chrétien writes: > > rgheck writes: > > > > > > > Here's a patch updated to current trunk, since I incremented the format > > for another reason. > > There is still a typo which prevents successful conversion: there should be a > closing "

Re: New RefStyle Patch

rgheck wrote: > So I'll go ahead and commit this if it seems good to Jurgen. I'd like > his opinion, too. I didn't have time to test it. I'm fine with it as long as it is guaranteed that old (prettyref and prettyref/varioref combined) documents come out identical, at least if people do not use

Re: New RefStyle Patch

rgheck rgh...@... writes: Here's a patch updated to current trunk, since I incremented the format for another reason. There is still a typo which prevents successful conversion: there should be a closing after vreference in line: +document.body[k] = reference + \ + prefix +

Re: New RefStyle Patch

On 03/20/2010 04:54 AM, Jean-Pierre Chrétien wrote: rgheckrgh...@... writes: Here's a patch updated to current trunk, since I incremented the format for another reason. There is still a typo which prevents successful conversion: there should be a closing after vreference in line:

Re: New RefStyle Patch

rgheck writes: > > > Here's a patch updated to current trunk, since I incremented the format > for another reason. There is still a typo which prevents successful conversion: there should be a closing " after vreference in line: +document.body[k] = "reference + " \""

Re: New RefStyle Patch

On 03/20/2010 04:54 AM, Jean-Pierre Chrétien wrote: rgheck writes: Here's a patch updated to current trunk, since I incremented the format for another reason. There is still a typo which prevents successful conversion: there should be a closing " after vreference in

New RefStyle Patch

Here's a patch updated to current trunk, since I incremented the format for another reason. There are a couple conceptual issues. (1) refstyle does not know about theorems and lemmas by default. What mechanism should we use for declaring the reference styles? One possibility is to include

Re: New RefStyle Patch

rgheck rgh...@... writes: Here's a patch updated to current trunk, since I incremented the format for another reason. There are a couple conceptual issues. (1) refstyle does not know about theorems and lemmas by default. What mechanism should we use for declaring the reference styles?

Re: New RefStyle Patch

On 03/18/2010 06:36 PM, Julien Rioux wrote: (1) refstyle does not know about theorems and lemmas by default. What mechanism should we use for declaring the reference styles? Seems to me that this should be fixed upstream, in the refstyle package. That's a good idea. I'll write the

New RefStyle Patch

Here's a patch updated to current trunk, since I incremented the format for another reason. There are a couple conceptual issues. (1) refstyle does not know about theorems and lemmas by default. What mechanism should we use for declaring the reference styles? One possibility is to include

Re: New RefStyle Patch

rgheck writes: > > Here's a patch updated to current trunk, since I incremented the format > for another reason. > > There are a couple conceptual issues. > > (1) refstyle does not know about theorems and lemmas by default. What > mechanism should we use for declaring the

Re: New RefStyle Patch

On 03/18/2010 06:36 PM, Julien Rioux wrote: (1) refstyle does not know about theorems and lemmas by default. What mechanism should we use for declaring the reference styles? Seems to me that this should be fixed upstream, in the refstyle package. That's a good idea. I'll write the