## LATEX-L@LISTSERV.UNI-HEIDELBERG.DE

 Options: Use Classic View Use Monospaced Font Show Text Part by Default Show All Mail Headers Topic: [<< First] [< Prev] [Next >] [Last >>]

 Re: Case changing operations Joseph Wright <[log in to unmask]> Tue, 1 Jul 2014 14:16:02 +0100 text/plain (31 lines) On 01/07/2014 14:00, Joseph Wright wrote: >> does anyone know what context do? is there scope for joint work on a >> common module? > > Reading e.g. http://wiki.contextgarden.net/Titles, the ConTeXt approach > (as I'd guess) has more than one part. The primitives tend to be more > 'encouraged' in ConTeXt than is likely to be the case for any > stand-alone LaTeX2, and indeed than is often the case for LaTeX2e. Thus > they have some examples using \uppercase, which is (in the version of > ConTeXt I have installed) the primitive unaltered (I did not check for > any callback here). There is also e.g. \WORD, which in MkIV uses > LuaTeX's \attribute system to effect the change at the font level. The > latter is therefore able to e.g. convert "ß" to "SS". (In my tests I did > not find another example of a 1 -> many situation which is covered by > the standard fonts.) Thus they have somewhat different > requirements/aims. (Testing here suggests that e.g. \Word will pick up > "." but does not handle for example quotations.) > > (Note: That page says \WORD will mess up \em, which may be correct for > MkII but is wrong for MkIV. I've not checked what MkII does here.) > > (See also http://wiki.contextgarden.net/Command/setcharactercasing for > the more general case, which works on a per-paragraph basis, again using > attributes to achieve this.) What of course is notable here is that they've not felt the need to actually convert stored input (easily) into different cases: nether the primitive nor attribute approach are expandable. -- Joseph Wright