On Wed, Jul 25, 2012 at 12:55 AM, Wolfgang Schuster wrote:

\definehighlight[smallcaps][style=\setff{smallcaps}]

Hello and thanks for your help but even if I copy-paste your example into TeXWorks and typeset it (remember, I'm using ConTeXT with XeTeX) I get the error: Undefined control sequence. l.1 \definehighlight [smallcaps][style=\setff{smallcaps}] -- Shriramana Sharma

On Tue, Jul 24, 2012 at 11:21:22PM +0200, Hans Hagen wrote:

On 24-7-2012 21:29, Shriramana Sharma wrote:

...

On Wed, Jul 25, 2012 at 12:55 AM, Wolfgang Schuster wrote:

...

\definehighlight[smallcaps][style=\setff{smallcaps}]

Hello and thanks for your help but even if I copy-paste your example into TeXWorks and typeset it (remember, I'm using ConTeXT with XeTeX) I get the error:

Undefined control sequence. l.1 \definehighlight [smallcaps][style=\setff{smallcaps}]

you probably run an ancient mkiv .. this command has been around for a while

He is using XeTeX, no MkIV for him. Regards, Khaled

Thanks to all who replied. On Wed, Jul 25, 2012 at 1:04 AM, Marco wrote:

My guess is that DejaVu Sans Condensed has no small caps. That's why you get the unexpected result. LibO might fake the small caps, which should usually be avoided, since it often leads to typographically bad results. If you need caps, select a font which provides them.

Hi -- is there absolutely no way for obtaining these "fake small caps" in ConTeXT? The thread http://www.tug.org/pipermail/xetex/2008-July/010325.html seems to contain some hints but they are fotr for LaTeX. I don't want to switch to LaTeX just for this. Basically I'm trying to move away from wordprocessors, and while I'm not looking for meaningless effects like "walking ants" (from MS Word) to be provided by TeX macro packages, faux smallcaps (and oblique and bold) is not an unreasonable thing to expect IMO. Not everyone is a typographer to produce the appropriate fine-typography glyphs for their favourite font to cater to a particular style. Why should the system impose "super-duper" typography on users when they are willing to settle for less? -- Shriramana Sharma

Hello Aditya and thanks for your help. However, the following file still does not my particular selected font to be shown in faux small caps: \def\fakesmallcaps{\let\processword\dofakesmallcapped\processwords} \def\dofakesmallcapped#1{\dostartfakesmallcapped#1\dostopfakesmallcapped} \def\dostartfakesmallcapped#1#2\dostopfakesmallcapped{\cap{#1\cap{#2}}} \font\fontlatin = "Gentium Basic" at 12 pt \font\fontlatintwo = "DejaVu Sans Condensed" at 16 pt \starttext \fontlatin \fakesmallcaps{Testing This} \fontlatintwo \fakesmallcaps{Testing This} \stoptext -- Shriramana Sharma

On Wed, Jul 25, 2012 at 10:29 AM, Rogers, Michael K wrote:

Here's a hack, which sort of works, definitely doesn't handle <return> -- there must be a better way. I hope you don't mind my using your text as text. :-)

Hi thanks for your help. Sorry to keep returning with errors (but as I said I'm a noob): loading : ConTeXt User Module / Simplefonts ! Undefined control sequence. l.144 \ctxloadluafile {t-simplefonts}{} I checked and the package context-modules is installed on my system. -- Shriramana Sharma

On Wed, Jul 25, 2012 at 9:04 AM, Marco wrote:

On 2012-07-25 Shriramana Sharma wrote:

Hi Shriramana,

...

Hi thanks for your help. Sorry to keep returning with errors (but as I said I'm a noob):

loading : ConTeXt User Module / Simplefonts ! Undefined control sequence. l.144 \ctxloadluafile {t-simplefonts}{}

simplefonts is a MkIV module, you are using MkII. If you don't have a particular reason to use MkII with XeTeX

He does. He just explained that he wants to use Indic scripts and unless someone writes support for them ... However this means that t-simplefonts are not an option either. Btw: shouldn't the module check that it's running MKIV and complain if it doesn't (with a clear error message as opposed to "undefined command")? Mojca

On Jul 25, 2012, at 1:06 AM, Shriramana Sharma wrote:

On Wed, Jul 25, 2012 at 10:29 AM, Rogers, Michael K wrote:

...

Here's a hack, which sort of works, definitely doesn't handle <return> -- there must be a better way. I hope you don't mind my using your text as text. :-)

Hi thanks for your help. Sorry to keep returning with errors (but as I said I'm a noob):

loading : ConTeXt User Module / Simplefonts ! Undefined control sequence. l.144 \ctxloadluafile {t-simplefonts}{}

I checked and the package context-modules is installed on my system.

Sorry about that. You should load your font in your usual way. As has been pointed out, this is not a robust solution. % load your favorite font here \def\smallcaps{\begingroup\let\par=\space\obeylines\obeyspaces\let\myspace=\space\dosmallcaps} \def\dosmallcaps#1{\dosc#1\end\endgroup} \def\dosc#1{% assumes #1 is a sequence of characters \ifx#1\end \let\next=\relax \else\if#1\space \myspace\let\myspace=\relax% skip repeated spaces \else\ifnum\lccode`#1=`#1{\tfx \uppercase{#1}}% change \tfx to your desired size \else #1\fi \let\myspace=\space \fi \let\next=\dosc \fi\next} \starttext Basically I'm trying to move away from wordprocessors, and while I'm not looking for meaningless effects like "walking ants" \smallcaps{(from MS Word)} to be provided by \TeX\ macro packages, faux smallcaps (and oblique and bold) is not an unreasonable thing to expect IMO. Not everyone is a typographer to produce the appropriate fine-typography glyphs for their favourite font to cater to a particular style. Why should the system impose \smallcaps{"super-duper" Typography} on users when they are willing to settle for less? \smallcaps{Look, returns now work} %\smallcaps{but \TeX\ and other control sequences do not.} \stoptext ________________________________ This e-mail message (including any attachments) is for the sole use of the intended recipient(s) and may contain confidential and privileged information. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message (including any attachments) is strictly prohibited. If you have received this message in error, please contact the sender by reply e-mail message and destroy all copies of the original message (including attachments).

On Wed, Jul 25, 2012 at 9:35 AM, Hans Hagen wrote:

On 25-7-2012 04:33, Shriramana Sharma wrote:

...

Basically I'm trying to move away from wordprocessors, and while I'm not looking for meaningless effects like "walking ants" (from MS Word) to be provided by TeX macro packages, faux smallcaps (and oblique and bold) is not an unreasonable thing to expect IMO. Not everyone is a typographer to produce the appropriate fine-typography glyphs for their favourite font to cater to a particular style. Why should the system impose "super-duper" typography on users when they are willing to settle for less?

Sure, but one problem with a mkii fake approach is that it is fragile when something else than 8 bit characters shows up in the content stream.

Is that also true for XeTeX? (What is an 8-bit character when talking of XeTeX?) As far as I remember converting uppercase into lowercase or vice versa should work out of the box in XeTeX (all the lccodes and uccodes are properly set already). [But I have no idea how that black magic with \Words & \Caps and their zillions of variants works.]

In mkiv that's less an issues as there completely different solutions are used.

But it lacks Indic scripts, so it's not an option for him, at least not yet. Mojca

Hi thanks everyone for their responses. On Wed, Jul 25, 2012 at 1:23 PM, Hans Hagen wrote:

...

But it lacks Indic scripts, so it's not an option for him, at least not yet.

Indic scripts will be supported in mkiv some day soon (at the ntg meeting there has been a presentation about devanagari etc using the context font machinery and that will be integrated once it's stable).

Hi -- I'm curious to know about your future plans for Indic. Are you going to use HarfBuzz? Even in Indic, I have specific minority orthography requirements due to which I'm using Graphite-enabled fonts. HarfBuzz (new one, not old one) supports Graphite and so my requirements would be met if that is used, but if you are going to develop yet another rendering system (please don't tell me it's so) it would be quite difficult... -- Shriramana Sharma

On 25-7-2012 10:16, Shriramana Sharma wrote:

Hi thanks everyone for their responses.

On Wed, Jul 25, 2012 at 1:23 PM, Hans Hagen wrote:

...

...

But it lacks Indic scripts, so it's not an option for him, at least not yet.

Indic scripts will be supported in mkiv some day soon (at the ntg meeting there has been a presentation about devanagari etc using the context font machinery and that will be integrated once it's stable).

Hi -- I'm curious to know about your future plans for Indic. Are you going to use HarfBuzz? Even in Indic, I have specific minority orthography requirements due to which I'm using Graphite-enabled fonts. HarfBuzz (new one, not old one) supports Graphite and so my requirements would be met if that is used, but if you are going to develop yet another rendering system (please don't tell me it's so) it would be quite difficult...

luatex does not use specific libraries but assumes all to be done in lua .. the otf machinery in mkiv is lua based (independent, extensible) and support for indic runs on top of that (the additional code is written by some dutchies who need it for high end academic publishing) ... I don't know about specific monorities but demos of several variants were shown Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------