On Sun, Nov 16, 2008 at 05:30, Hans Hagen wrote:

Jeff Smith wrote:

...

Hi all!

The \setcharacterspacing[frenchpunctuation] stuff I saw discussed recently on this list does not work. Is it because I still use MKII+Xetex? I get the usual error when there is an unknown command:

! Undefined control sequence. l.6 \setcharacterspacing

indeed, only mkiv

Ok, thought as much. So, what do I do? Is there a way to update/adapt the older hacks that don't work anymore? While I follow the developments of luatex with interest, I'm not interested in switching yet if I can help it. Thanks! Jeff

Oh, alright, sorry, I thought that with the error messages given in my first post it might have been enough. I'm really sorry... I attach an example document with the minimum required. There seems to an incompatibility betwen the first part: \def\activateSomeCharacters{% \defineactivecharacter ! {\,\string!}% \defineactivecharacter ? {\,\string?}% \defineactivecharacter : {\,\string:}% \defineactivecharacter ; {\,\string;}} \activateSomeCharacters \appendtoks\activateSomeCharacters\to\everystarttext ... and my typescript definition. The problem I see here is that you guys may or may not have the font I used (Garamond Pro). Anyway, what I can say is that in a simple document with no typescript definition, activeSomeCharacters work. But as it is in my sample document, it does not. I will paste again the relevant part in the log: ! Missing \endcsname inserted. <to be read again> \kern \textormathspace ...fmmode \mskip #1#2\else \kern #1\hspaceamount \empty {#3... <argument> name\textormathspace +\thinmuskip 1 :Garamond Premier Pro \dodotruefontname ...\ifcsname \??ff \fontclass #1 \endcsname \@EA \redotruef... \dotruefontname ... \??ff \fontclass #1\endcsname *#2#3\fi \else \ifcsname \... \dotruefontname ... \??ff \fontclass #1\endcsname \else \@EA \redotruefontna... ... l.35 \setupbodyfont[bodytext,12pt,rm] ? Thanks for any help! Jeff

On Sun, Nov 16 2008, Jeff Smith wrote:

Ok, thought as much. So, what do I do? Is there a way to update/adapt the older hacks that don't work anymore? While I follow the developments of luatex with interest, I'm not interested in switching yet if I can help it.

A small example that shows the problem would help. Or just downgrade, you can keep different ConTeXt versions on the same hard-disk in parallel. Cheers, Peter -- http://pmrb.free.fr/contact/

Ah. I now understand the subtlety of "active" characters. Both solutions worked, but also broke elsewhere first: with every colon in my reference keys for the \cite command with BibTeX. I guess I shouldn't do that, so I changed my keys and now everything runs perfect. Thanks a lot! Jeff On Sun, Nov 16, 2008 at 15:05, Hans Hagen wrote:

\useencoding[ffr]

best not mess around with active colons in an other way since there are precausions takne for this kind of hackery all over context (you don't want to know where active colons can play havoc)