Re: RefStyle Patch

Richard Heck a écrit : I thought about something like this: RefCommand prop RefStyle \def...@proptxt{proposition}\newref{prop}{refcmd={\rs@proptxt \ref{#1}} Rather \RSaddto{\RSenglish}{% \def...@proptxt{proposition}% }% \newref{prop}{refcmd={...@proptxt \ref{#1}} or you kill the

Re: RefStyle Patch

On 11/11/2010 03:35 AM, Jean-Pierre Chrétien wrote: Richard Heck a écrit : I thought about something like this: RefCommand prop RefStyle \def...@proptxt{proposition}\newref{prop}{refcmd={\rs@proptxt \ref{#1}} Rather \RSaddto{\RSenglish}{% \def...@proptxt{proposition}% }%

Re: RefStyle Patch

Richard Heck a écrit : I thought about something like this: RefCommand prop RefStyle \def...@proptxt{proposition}\newref{prop}{refcmd={\rs@proptxt \ref{#1}} Rather \RSaddto{\RSenglish}{% \def...@proptxt{proposition}% }% \newref{prop}{refcmd={...@proptxt \ref{#1}} or you kill the

Re: RefStyle Patch

On 11/11/2010 03:35 AM, Jean-Pierre Chrétien wrote: Richard Heck a écrit : I thought about something like this: RefCommand prop RefStyle \def...@proptxt{proposition}\newref{prop}{refcmd={\rs@proptxt \ref{#1}} Rather \RSaddto{\RSenglish}{% \def...@proptxt{proposition}% }%

Re: RefStyle Patch

On 11/08/2010 02:52 PM, Jean-Pierre Chrétien wrote: Richard Heckrgheckat comcast.net writes: The problem, as you say, is that refstyle and prettyref do not use the same prefix for chapters, and refstyle actually uses part for parts. So whichever we choose seems as if it will cause problems

Re: RefStyle Patch

Jean-Marc Lasgouttes lasgouttes at lyx.org writes: Le 28 oct. 10 à 18:24, Jean-Pierre Chrétien a écrit : Is there some way we could provide translatability (in LyX's po files) of theorem here? For the time being, we need a restricted set of declarations and translations in LyX

Re: RefStyle Patch

Richard Heck rgheck at comcast.net writes: I think part and chap are the way to go, but I think we can actually do it without any lyx2lyx and so avoid breaking customized prettyref stuff, such as Jurgen has. New labels will be chap by default, but we can do this: \let\pr at chap=\pr

Re: RefStyle Patch

On 11/10/2010 11:08 AM, Jean-Pierre Chrétien wrote: Richard Heckrgheckat comcast.net writes: I think part and chap are the way to go, but I think we can actually do it without any lyx2lyx and so avoid breaking customized prettyref stuff, such as Jurgen has. New labels will be chap by

Re: RefStyle Patch

On 11/08/2010 02:52 PM, Jean-Pierre Chrétien wrote: Richard Heck writes: The problem, as you say, is that refstyle and prettyref do not use the same prefix for chapters, and refstyle actually uses "part" for parts. So whichever we choose seems as if it will cause problems

Re: RefStyle Patch

Jean-Marc Lasgouttes lyx.org> writes: > > Le 28 oct. 10 à 18:24, Jean-Pierre Chrétien a écrit : > >> Is there some way we could provide translatability (in LyX's po > >> files) of "theorem" here? > > > > For the time being, we need a restricted set of declarations and > > translations > >

Re: RefStyle Patch

Richard Heck comcast.net> writes: > I think "part" and "chap" are the way to go, but I think we can actually > do it without any lyx2lyx and so avoid breaking customized prettyref > stuff, such as Jurgen has. New labels will be "chap" by default, but we > can do this: > \let\pr

Re: RefStyle Patch

On 11/10/2010 11:08 AM, Jean-Pierre Chrétien wrote: Richard Heck writes: I think "part" and "chap" are the way to go, but I think we can actually do it without any lyx2lyx and so avoid breaking customized prettyref stuff, such as Jurgen has. New labels will be "chap" by

Re: RefStyle Patch

On 11/04/2010 08:52 AM, Jean-Pierre Chrétien wrote: Richard Heck a écrit : On 11/03/2010 01:28 PM, Jean-Pierre Chrétien wrote: I forgot to mention that I could make convert_prettyref.patch work. So what is the idea behind this one? It seems to have a few different parts. I know there is a

Re: RefStyle Patch

Richard Heck rgheck at comcast.net writes: Starting with lyx-2.0, with a new document, labels are chap:, but remain as par: (I guess for compatibility with prettyref), so that checking Use refstyle with a reference to a chapter results in a ?? (unknown reference to cha:xxx). OK,

Re: RefStyle Patch

On 11/04/2010 08:52 AM, Jean-Pierre Chrétien wrote: Richard Heck a écrit : On 11/03/2010 01:28 PM, Jean-Pierre Chrétien wrote: I forgot to mention that I could make convert_prettyref.patch work. So what is the idea behind this one? It seems to have a few different parts. I know there is a

Re: RefStyle Patch

Richard Heck comcast.net> writes: > > Starting with lyx-2.0, with a new document, labels are chap:, but > > remain as par: > > (I guess for compatibility with prettyref), so that checking "Use > > refstyle" with a reference to a chapter results in a ?? (unknown > > reference to cha:xxx). > >

Re: RefStyle Patch

Jean-Pierre Chrétien a écrit : Jean-Pierre Chrétien a écrit : Richard Heck a écrit : On 11/02/2010 02:01 PM, Jean-Pierre Chrétien wrote: Jean-Pierre Chrétien a écrit : Oops, LyX should redefine \newrefformat is refstyle is selected (in case of user-defined \newrefformat). The simplest

Re: RefStyle Patch

On 11/03/2010 01:28 PM, Jean-Pierre Chrétien wrote: And the string next to the refstyle checkbox in Document-Settings-Document class remains unstranslated (as well as the string for date in fact). Lots of new strings in 2.0 are untranslated still. People don't really get to work until

Re: RefStyle Patch

On 11/03/2010 01:28 PM, Jean-Pierre Chrétien wrote: I forgot to mention that I could make convert_prettyref.patch work. So what is the idea behind this one? It seems to have a few different parts. I know there is a part/par chap/cha issue here somewhere. But I'm not sure if lyx2lyx is the

Re: RefStyle Patch

with prettyref), so that checking Use refstyle with a reference to a chapter results in a ?? (unknown reference to cha:xxx). Last march, the first refstyle patch (which wiped out completely prettyref) that you proposed used convert_prettyref to subsitute all cha: and par: as chap: and part:. I just

Re: RefStyle Patch

Jean-Pierre Chrétien a écrit : Jean-Pierre Chrétien a écrit : Richard Heck a écrit : On 11/02/2010 02:01 PM, Jean-Pierre Chrétien wrote: Jean-Pierre Chrétien a écrit : Oops, LyX should redefine \newrefformat is refstyle is selected (in case of user-defined \newrefformat). The simplest

Re: RefStyle Patch

On 11/03/2010 01:28 PM, Jean-Pierre Chrétien wrote: And the string next to the refstyle checkbox in Document->Settings->Document class remains unstranslated (as well as the string for date in fact). Lots of new strings in 2.0 are untranslated still. People don't really get to work until

Re: RefStyle Patch

On 11/03/2010 01:28 PM, Jean-Pierre Chrétien wrote: I forgot to mention that I could make convert_prettyref.patch work. So what is the idea behind this one? It seems to have a few different parts. I know there is a part/par chap/cha issue here somewhere. But I'm not sure if lyx2lyx is the

Re: RefStyle Patch

with prettyref), so that checking "Use refstyle" with a reference to a chapter results in a ?? (unknown reference to cha:xxx). Last march, the first refstyle patch (which wiped out completely prettyref) that you proposed used convert_prettyref to subsitute all cha: and par: as chap: and part:

Re: RefStyle Patch

Richard Heck a écrit : On 11/02/2010 02:01 PM, Jean-Pierre Chrétien wrote: Jean-Pierre Chrétien a écrit : OK, so, for the time being, anyway, we think refstyle support is complete? Or am I misremembering some other issue? Extra \makeatother/\makeatletter in LaTeXFeatures.cpp and problem

Re: RefStyle Patch

Jean-Pierre Chrétien a écrit : Richard Heck a écrit : On 11/02/2010 02:01 PM, Jean-Pierre Chrétien wrote: Jean-Pierre Chrétien a écrit : OK, so, for the time being, anyway, we think refstyle support is complete? Or am I misremembering some other issue? Extra \makeatother/\makeatletter

Re: RefStyle Patch

Richard Heck a écrit : On 11/02/2010 02:01 PM, Jean-Pierre Chrétien wrote: Jean-Pierre Chrétien a écrit : OK, so, for the time being, anyway, we think refstyle support is complete? Or am I misremembering some other issue? Extra \makeatother/\makeatletter in LaTeXFeatures.cpp and problem

Re: RefStyle Patch

Jean-Pierre Chrétien a écrit : Richard Heck a écrit : On 11/02/2010 02:01 PM, Jean-Pierre Chrétien wrote: Jean-Pierre Chrétien a écrit : OK, so, for the time being, anyway, we think refstyle support is complete? Or am I misremembering some other issue? Extra \makeatother/\makeatletter

Re: RefStyle Patch

Richard Heck a écrit : On 10/31/2010 06:38 AM, Jean-Pierre Chrétien wrote: Jean-Pierre Chrétien a écrit : So do we have an extra \makeatletter somewhere? Yes, exporting my example file in LaTeX reads: cite \makeatletter %% LyX specific LaTeX commands.

Re: RefStyle Patch

Jean-Pierre Chrétien a écrit : Richard Heck a écrit : On 10/31/2010 06:38 AM, Jean-Pierre Chrétien wrote: Jean-Pierre Chrétien a écrit : I got an anwer from Danie, I was mistaken about the multilingual feature of refstyle: it works all right (as \def commands are encapsulated in

Re: RefStyle Patch

On 11/02/2010 02:01 PM, Jean-Pierre Chrétien wrote: Jean-Pierre Chrétien a écrit : I got an anwer from Danie, I was mistaken about the multilingual feature of refstyle: it works all right (as \def commands are encapsulated in \extraslang commands) if refstyle is loaded *after* babel. Is

Re: RefStyle Patch

Richard Heck a écrit : On 10/31/2010 06:38 AM, Jean-Pierre Chrétien wrote: Jean-Pierre Chrétien a écrit : So do we have an extra \makeatletter somewhere? Yes, exporting my example file in LaTeX reads: \makeatletter %% LyX specific LaTeX commands.

Re: RefStyle Patch

Jean-Pierre Chrétien a écrit : Richard Heck a écrit : On 10/31/2010 06:38 AM, Jean-Pierre Chrétien wrote: Jean-Pierre Chrétien a écrit : I got an anwer from Danie, I was mistaken about the multilingual feature of refstyle: it works all right (as \def commands are encapsulated in \extras

Re: RefStyle Patch

On 11/02/2010 02:01 PM, Jean-Pierre Chrétien wrote: Jean-Pierre Chrétien a écrit : I got an anwer from Danie, I was mistaken about the multilingual feature of refstyle: it works all right (as \def commands are encapsulated in \extras commands) if refstyle is loaded *after* babel. Is it

Re: RefStyle Patch

Uwe Stöhr a écrit : I haven't followed this thread, but have you seen that the new version 0.4 of refstyle supports now French: http://article.gmane.org/gmane.comp.tex.ctan.announce/8109 Sure, this follows a private mail exchange with Danie Els. -- Jean-Pierre

Re: RefStyle Patch

Uwe Stöhr a écrit : I haven't followed this thread, but have you seen that the new version 0.4 of refstyle supports now French: http://article.gmane.org/gmane.comp.tex.ctan.announce/8109 Sure, this follows a private mail exchange with Danie Els. -- Jean-Pierre

Re: RefStyle Patch

Jean-Pierre Chrétien a écrit : I'll post a tentative file with bug #6609 to illustrate the idea (tentative because it's not working right now). I performed some tests to make this file work and I corrected some typos in the file. However, the current version does not work with LyX for

Re: RefStyle Patch

I haven't followed this thread, but have you seen that the new version 0.4 of refstyle supports now French: http://article.gmane.org/gmane.comp.tex.ctan.announce/8109 regards Uwe

Re: RefStyle Patch

On 10/31/2010 06:38 AM, Jean-Pierre Chrétien wrote: Jean-Pierre Chrétien a écrit : I'll post a tentative file with bug #6609 to illustrate the idea (tentative because it's not working right now). I performed some tests to make this file work and I corrected some typos in the file.

Re: RefStyle Patch

Jean-Pierre Chrétien a écrit : I'll post a tentative file with bug #6609 to illustrate the idea (tentative because it's not working right now). I performed some tests to make this file work and I corrected some typos in the file. However, the current version does not work with LyX for

Re: RefStyle Patch

I haven't followed this thread, but have you seen that the new version 0.4 of refstyle supports now French: http://article.gmane.org/gmane.comp.tex.ctan.announce/8109 regards Uwe

Re: RefStyle Patch

On 10/31/2010 06:38 AM, Jean-Pierre Chrétien wrote: Jean-Pierre Chrétien a écrit : I'll post a tentative file with bug #6609 to illustrate the idea (tentative because it's not working right now). I performed some tests to make this file work and I corrected some typos in the file.

Re: RefStyle Patch

Richard Heck a écrit : On 10/28/2010 12:24 PM, Jean-Pierre Chrétien wrote: Perhaps we can do this: (i) Try to get translations from our own translators of theorem and lemma, if that covers everything prettyref does, that we can hardcode into LaTeXFeatures.cpp, so that we at least do as

Re: RefStyle Patch

Jean-Pierre Chrétien a écrit : Richard Heck a écrit : Are there other things besides theorems we should define that aren't in refstyle.cfg? To be prettyref-coherent, lemmas. Lemmas and theorems are OK now (but untranslated), thanks. -- Jean-Pierre

Re: RefStyle Patch

Richard Heck a écrit : On 10/28/2010 12:24 PM, Jean-Pierre Chrétien wrote: Perhaps we can do this: (i) Try to get translations from our own translators of theorem and lemma, if that covers everything prettyref does, that we can hardcode into LaTeXFeatures.cpp, so that we at least do as

Re: RefStyle Patch

Jean-Pierre Chrétien a écrit : Richard Heck a écrit : Are there other things besides theorems we should define that aren't in refstyle.cfg? To be prettyref-coherent, lemmas. Lemmas and theorems are OK now (but untranslated), thanks. -- Jean-Pierre

Re: RefStyle Patch

Jean-Pierre Chrétien a écrit : Richard Heck a écrit : On 10/27/2010 04:17 AM, Jean-Pierre Chrétien wrote: When I look at the exported latex file test_french_refstyle.tex, I see this: \...@ifundefined{ hmref} {\def\RSthmtxt{theorem~}\newref{thm}{name = \RSthmtxt}} which creates the

Re: RefStyle Patch

On 10/28/2010 05:36 AM, Jean-Pierre Chrétien wrote: Jean-Pierre Chrétien a écrit : Richard Heck a écrit : On 10/27/2010 04:17 AM, Jean-Pierre Chrétien wrote: When I look at the exported latex file test_french_refstyle.tex, I see this: \...@ifundefined{hmref}

Re: RefStyle Patch

I'm not seeing the difference Anyway, I'm going to do the other thing I suggested, I think. Richard

Re: RefStyle Patch

Richard Heck a écrit : I'm not seeing the difference Anyway, I'm going to do the other thing I suggested, I think. The problem with : has vanished, but theorems are now unknown: ?? is returned in my bug #6609 example. -- Jean-Pierre

Re: RefStyle Patch

On 10/28/2010 11:55 AM, Jean-Pierre Chrétien wrote: Richard Heck a écrit : I'm not seeing the difference Anyway, I'm going to do the other thing I suggested, I think. The problem with : has vanished, but theorems are now unknown: ?? is returned in my bug #6609 example. Took out too

Re: RefStyle Patch

Am Donnerstag 28 Oktober 2010 schrieb Richard Heck: On 10/28/2010 05:36 AM, Jean-Pierre Chrétien wrote: Jean-Pierre Chrétien a écrit : Richard Heck a écrit : On 10/27/2010 04:17 AM, Jean-Pierre Chrétien wrote: When I look at the exported latex file test_french_refstyle.tex, I see this:

Re: RefStyle Patch

Richard Heck a écrit : Are there other things besides theorems we should define that aren't in refstyle.cfg? To be prettyref-coherent, lemmas. Is there some way we could provide translatability (in LyX's po files) of theorem here? For the time being, we need a restricted set of

Re: RefStyle Patch

On 10/28/2010 12:16 PM, Kornel Benko wrote: The diff is in the first line ...fundefined{thmref}... vs ...fundefined{\thmref}... Oh, right, I see. rh

Re: RefStyle Patch

On 10/28/2010 12:24 PM, Jean-Pierre Chrétien wrote: Richard Heck a écrit : Are there other things besides theorems we should define that aren't in refstyle.cfg? To be prettyref-coherent, lemmas. Is there some way we could provide translatability (in LyX's po files) of theorem here?

Re: RefStyle Patch

Le 28 oct. 10 à 18:24, Jean-Pierre Chrétien a écrit : Is there some way we could provide translatability (in LyX's po files) of theorem here? For the time being, we need a restricted set of declarations and translations in LyX (no plurals, no capitalization). If you declare all refstyle

Re: RefStyle Patch

Jean-Pierre Chrétien a écrit : Richard Heck a écrit : On 10/27/2010 04:17 AM, Jean-Pierre Chrétien wrote: When I look at the exported latex file test_french_refstyle.tex, I see this: \...@ifundefined{ hmref} {\def\RSthmtxt{theorem~}\newref{thm}{name = \RSthmtxt}} which creates the

Re: RefStyle Patch

On 10/28/2010 05:36 AM, Jean-Pierre Chrétien wrote: Jean-Pierre Chrétien a écrit : Richard Heck a écrit : On 10/27/2010 04:17 AM, Jean-Pierre Chrétien wrote: When I look at the exported latex file test_french_refstyle.tex, I see this: \...@ifundefined{hmref}

Re: RefStyle Patch

I'm not seeing the difference Anyway, I'm going to do the other thing I suggested, I think. Richard

Re: RefStyle Patch

Richard Heck a écrit : I'm not seeing the difference Anyway, I'm going to do the other thing I suggested, I think. The problem with ":" has vanished, but theorems are now unknown: ?? is returned in my bug #6609 example. -- Jean-Pierre

Re: RefStyle Patch

On 10/28/2010 11:55 AM, Jean-Pierre Chrétien wrote: Richard Heck a écrit : I'm not seeing the difference Anyway, I'm going to do the other thing I suggested, I think. The problem with ":" has vanished, but theorems are now unknown: ?? is returned in my bug #6609 example. Took out

Re: RefStyle Patch

Am Donnerstag 28 Oktober 2010 schrieb Richard Heck: > On 10/28/2010 05:36 AM, Jean-Pierre Chrétien wrote: > > Jean-Pierre Chrétien a écrit : > >> Richard Heck a écrit : > >>> On 10/27/2010 04:17 AM, Jean-Pierre Chrétien wrote: > > When I look at the exported latex file test_french_refstyle.tex, I

Re: RefStyle Patch

Richard Heck a écrit : Are there other things besides theorems we should define that aren't in refstyle.cfg? To be prettyref-coherent, lemmas. Is there some way we could provide translatability (in LyX's po files) of "theorem" here? For the time being, we need a restricted set of

Re: RefStyle Patch

On 10/28/2010 12:16 PM, Kornel Benko wrote: The diff is in the first line ...fundefined{thmref}... vs ...fundefined{\thmref}... Oh, right, I see. rh

Re: RefStyle Patch

On 10/28/2010 12:24 PM, Jean-Pierre Chrétien wrote: Richard Heck a écrit : Are there other things besides theorems we should define that aren't in refstyle.cfg? To be prettyref-coherent, lemmas. Is there some way we could provide translatability (in LyX's po files) of "theorem" here?

Re: RefStyle Patch

Le 28 oct. 10 à 18:24, Jean-Pierre Chrétien a écrit : Is there some way we could provide translatability (in LyX's po files) of "theorem" here? For the time being, we need a restricted set of declarations and translations in LyX (no plurals, no capitalization). If you declare all refstyle

Re: RefStyle Patch

Jean-Pierre Chrétien jeanpierre.chretien at free.fr writes: Richard Heck rgheck at comcast.net writes: OK, one last try at a refstyle patch. Comments welcome. I'll investigate more with my examples. Tested with French. The \lyxref encapsulation does not work when

Re: RefStyle Patch

On 10/27/2010 04:17 AM, Jean-Pierre Chrétien wrote: Tested with French. The \lyxref encapsulation does not work when : is active. I'm trying to find a workaround, I'll keep you posted. OK. Please let me know. We may need some \catcode thing in there? Richard

Re: RefStyle Patch

Richard Heck a écrit : On 10/27/2010 04:17 AM, Jean-Pierre Chrétien wrote: Tested with French. The \lyxref encapsulation does not work when : is active. I'm trying to find a workaround, I'll keep you posted. OK. Please let me know. We may need some \catcode thing in there? Sure, that's

Re: RefStyle Patch

On 10/27/2010 12:36 PM, Jean-Marc Lasgouttes wrote: Le 27/10/2010 15:39, Richard Heck a écrit : On 10/27/2010 04:17 AM, Jean-Pierre Chrétien wrote: Tested with French. The \lyxref encapsulation does not work when : is active. I'm trying to find a workaround, I'll keep you posted. OK. Please

Re: RefStyle Patch

Jean-Pierre Chrétien free.fr> writes: > > Richard Heck comcast.net> writes: > > > > > > > OK, one last try at a refstyle patch. > > > > Comments welcome. > I'll investigate more with my examples. > Tested with French. The \lyxref

Re: RefStyle Patch

On 10/27/2010 04:17 AM, Jean-Pierre Chrétien wrote: Tested with French. The \lyxref encapsulation does not work when ":" is active. I'm trying to find a workaround, I'll keep you posted. OK. Please let me know. We may need some \catcode thing in there? Richard

Re: RefStyle Patch

Richard Heck a écrit : On 10/27/2010 04:17 AM, Jean-Pierre Chrétien wrote: Tested with French. The \lyxref encapsulation does not work when ":" is active. I'm trying to find a workaround, I'll keep you posted. OK. Please let me know. We may need some \catcode thing in there? Sure,

Re: RefStyle Patch

On 10/27/2010 12:36 PM, Jean-Marc Lasgouttes wrote: Le 27/10/2010 15:39, Richard Heck a écrit : On 10/27/2010 04:17 AM, Jean-Pierre Chrétien wrote: Tested with French. The \lyxref encapsulation does not work when ":" is active. I'm trying to find a workaround, I'll keep you posted. OK.

Re: RefStyle Patch

Richard Heck rgheck at comcast.net writes: OK, one last try at a refstyle patch. Comments welcome. Tried on a simple fresh document. Seems that package ifthen should be included, due to the tests in the preamble. I'll investigate more with my examples. -- Jean-Pierre

Re: RefStyle Patch

On 10/14/2010 07:47 AM, Jean-Pierre Chrétien wrote: Richard Heckrgheckat comcast.net writes: OK, one last try at a refstyle patch. Comments welcome. Tried on a simple fresh document. Seems that package ifthen should be included, due to the tests in the preamble. Thanks

Re: RefStyle Patch

Richard Heck comcast.net> writes: > > > OK, one last try at a refstyle patch. > > Comments welcome. Tried on a simple fresh document. Seems that package ifthen should be included, due to the tests in the preamble. I'll investigate more with my examples. -- Jean-Pierre

Re: RefStyle Patch

On 10/14/2010 07:47 AM, Jean-Pierre Chrétien wrote: Richard Heck<rgheck comcast.net> writes: OK, one last try at a refstyle patch. Comments welcome. Tried on a simple fresh document. Seems that package ifthen should be included, due to the tests in the preamble.

RefStyle Patch

OK, one last try at a refstyle patch. It introduces a document option to use refstyle or prettyref, the former being the default for new documents, the latter staying in place for old ones, though of course users can change this. This now works well enough for me, though there may be some

Re: RefStyle Patch

Richard Heck wrote: Comments welcome. cant comment on the latex part but otherwise looks good. FORMAT file... pavel

RefStyle Patch

OK, one last try at a refstyle patch. It introduces a document option to use refstyle or prettyref, the former being the default for new documents, the latter staying in place for old ones, though of course users can change this. This now works well enough for me, though there may be some

Re: RefStyle Patch

Richard Heck wrote: > Comments welcome. cant comment on the latex part but otherwise looks good. FORMAT file... pavel

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

  1   2   >