>>>>> On Wed, 22 Feb 2006 11:36:13 +0100, Karsten Heymann <[EMAIL PROTECTED]> 
>>>>> said:



Karsten> Hi Stephen, (your OE does strange quoting, please fix it,

Karsten> it's difficult to see who'se written what. thanks. Maybe the

Karsten> following link ist interesting too:

Karsten> http://home.in.tum.de/~jain/software/oe-quotefix/)



Karsten> Stephen Harris schrieb:

>> Though the syntax of \DeclareRobustCommand is probably older than

>> \providecommand?



Karsten> You're reaching the borders of my LaTeX knowledge, but

Karsten> fortunately there is google groups :)



Karsten> Maybe



Karsten> http://groups.google.com/group/comp.text.tex/browse_thread/thread/

Karsten> 1f502a2d05d09f67/ba2e854e2274491f



Karsten> or



Karsten> http://groups.google.com/group/comp.text.tex/browse_thread/thread/

Karsten> 43979d37f901cb5e/395907c6db8808ec



Karsten> (one line each) will help. Have a look at usrguide.dvi/pdf

Karsten> too.



Karsten> Yours, Karsten



Stephen Harris replied:



I've noticed two logo styles, texnames.sty and texlogos.sty.

Since texlogos.sty uses \DeclareRobustCommand rather than

\providecommand, I wondered which was best or most current,

because the documentation seems to favor

 \DeclareRobustCommand

but in any event supports your advice to use Latex commands.



-------------------------------------------------------



From clsguide.pdf, the only entry mentioning \providecommand

1.

"Thus, instead of using \def... we recommend using one of 

\newcommand, \renewcommand or \providecommand; \CheckCommand 

is also useful. Doing  this makes it less likely that you 

will inadvertently redefine a command, giving unexpected 

results."

-------------------------------------------------------



clsguide.pdf, three of six entries re: \DeclareRobustCommand

1.

"This command takes the same arguments as \newcommand but 

it declares a robust command, even if some code within the 

definition is fragile. You can use this command to define 

new robust commands, or to redefine existing commands and 

make them robust." 



------------------

2.

"Because LATEX2e supports different encodings, definitions 

of commands for producing symbols, accents, composite glyphs, 

etc. must be defined using the commands provided for this 

purpose and described in LATEX2" Font Selection. This part 

of the system is still under development so such tasks 

should be undertaken with great caution.



Also, \DeclareRobustCommand should be used for 

encoding-independent commands of this type."



--------------------------------------------

3.

LATEX 2.09 used several commands beginning with \p in 

order to provide `protected'commands. For example, \LaTeX 

was defined to be \protect\pLaTeX, and \pLaTeX was defined 

to produce the LATEX logo. This made \LaTeX robust, even 

though \pLaTeX was not. These commands have now been 

reimplemented using \DeclareRobustCommand (described in 

Section 4.10). If your package redefined one of the 

\p-commands then you must remove the redefinition and use 

\DeclareRobustCommand to redefine the non-\p command."



-----------------------------------------------------



Xemacs Supercite regards,

Stephen




Reply via email to