March 2010 - ntg-context - NTG Mailing Lists

typescripts
by Michael Saunders 18 Mar '10

18 Mar '10

I'm trying to follow the examples and getting surprising results: \definefontfeature[default][mode=node,language=dflt,script=latn,kern=yes,liga=yes,tlig=yes,trep=yes] \definefontfeature[body][default][onum=yes,pnum=yes,protrusion=quality,expansion=quality] \definefontfeature[smallcaps][body][smcp=yes, onum=yes] %I understood this to mean that "body" would inherit "default" and "smallcaps" would inherit "body". \starttypescript [sans] [gillLT] \definefontsynonym[Gill-Light][name:gillsansmtprolight][features=body] \definefontsynonym[Gill-Light-Italic][name:gillsansmtprolightitalic][features=body] \stoptypescript \starttypescript [sans] [gillLT] \definefontsynonym[Sans][Gill-Light][features=body] \definefontsynonym[SansItalic][Gill-Light-Italic][features=body] \stoptypescript \starttypescript [gill] \definetypeface [gillLT] [ss] [sans] [gillLT] [default] [features=body,script=latn,script=grek] \stoptypescript \setupalign[hanging,hz] \setupbodyfont[gillLT,12pt] \ss 1: 1234567890 fi fl ffi ffl \addff{smallcaps} test smallcaps 2: \addff{body} 1234567890 fi fl ffi ffl \addff{smallcaps} test smallcaps In both 1 & 2, ligatures and small caps fail (though the glyphs are in the font). In 1, oldstyle fails.

1 0

including movies broken?
by Michail Vidiassov 18 Mar '10

18 Mar '10

Dear All, it seems including movies does not work: \starttext \placefigure[here]{none}{\externalfigure[demo.mov][width=0.7\textwidth, height=.7\textwidth, label=demo]} \stoptext processed with "context test_mov.tex" results in ! LuaTeX error ...text/tex/texmf-context/tex/context/base/grph-inc.lua:810: bad argument #4 to 'format' (string expected, got nil) under latest Minimals (Mac OS X 10.6). Did end-user interface change or we are (as so often) are in the middle of some integral migration from "used to work somehow" to "it is done the right way finally" via "the best way to test is to release"? Sincerely, Michail

1 0

Re: [NTG-context] ntg-context Digest, Vol 69, Issue 95
by Michael Saunders 18 Mar '10

18 Mar '10

Wolfgang Schuster: > \setupbodyfont[pagella] > > \definefontfeature[smcp][smcp=yes] > \definefontfeature[frac][frac=yes] > > \setuphead[chapter][textstyle=\addfs{frac}\addfs{smcp}] ... This is just an example, but what I think you mean to say by it is that the new command \addfs{} has the behavior I describe, but only for otf features and not for things like switching to semibold or to condensed (and, presumably, even if I'm able to define my own commands for things like semibold, something like: \sb ABC \it DEF would set the DEF at regular weight). Since I've never seen anyone talk about \addfs{}, but only give examples, I'm guessing (but just guessing) that there exists somewhere a list of what otf features are active at any given point, and that this command can add to that list. That's great. I might not need it anytime soon, but I'm just curious---are there other commands of this kind? Maybe something to clear the list? That leaves me the problem of installing sets with more than two weights, more than one width and several design sizes, as we spoke about earlier. It's late in the day here, but I hope to try that out tomorrow. Just to make sure I understand the example you and Mojca gave me: > \definebodyfont [default] [rm] > [tf=Serif sa 1, > bf=SerifBold sa 1, > it=SerifItalic sa 1, > sl=SerifSlanted sa 1, > bi=SerifBoldItalic sa 1, > bs=SerifBoldSlanted sa 1, > sc=SerifCaps sa 1] > > You could add your > in=SerifYourFontVariantName sa 1, > bd=SerifYourOtherFontVariantName sa 1, I think I can add this block to the top of my own typescript, duplicate the existing definitions as shown, and, when making up my own, I think I'm free to define font switches with more than two characters, so, e.g.: sbexit=SansSemiboldExtendedItalic sa 1 so, I won't be able to switch variants of this kind independently, but at least I can get them installed. After that, I'll move on to the optical examples and see what I can do about that (I'm hoping they provide for automatic switching of design size). Thank you, -- m

3 3

Footnotes and interaction again
by Philipp Gesang 18 Mar '10

18 Mar '10

Hi again, I just ran into the footnote problem again, this time when referring to labels inside footnotes. As in the earlier thread the issue occurs with mkiv only. Example: ---8<-------------------------------------------------------------------------- \setupinteraction[state=start,focus=standard] \starttext \startfootnote A label \reference[label:1]{} we will refer to. \stopfootnote \page[yes] \goto{Here}[label:1] we refer somewhere. It all happens on Page \ref[p][label:1]. \stoptext ---8<-------------------------------------------------------------------------- To be precise, you don't actually have to refer to the label, having it inside a footnote causes the error. Thanks for any suggestions, Philipp

6 7

math error
by Wolfgang Werners-Lucchini 18 Mar '10

18 Mar '10

Sorry, I found it! \starttext \startformula[] [29;2,2,1]=\frac{206}{7} \stopformula \stoptext Wolfgang

1 0

math error
by Wolfgang Werners-Lucchini 18 Mar '10

18 Mar '10

Hallo, the following example compiles ok \starttext \startformula \frac{206}{7}=[29;2,2,1] \stopformula \stoptext while this compiles not \starttext \startformula [29;2,2,1]=\frac{206}{7} \stopformula \stoptext Bug or user error? Wolfgang

3 2

typescripts
by Michael Saunders 18 Mar '10

18 Mar '10

Wolfgang Schuster: > do you need all of your fonts at the same time in your document? Most of the time, one serif and one sans. I'd be happy to get these installed. Of course, High quality fonts often come in large sets. The varying weights turn up most often in the variations between different kinds of heads, occasionally in other things. Variations in optical size occur more frequently, besides in heads, in things like quotations, footnotes, and captions. Smallcaps (and sometimes, all-caps environments) often turn up in headers. It's nice to be able to switch easily between roman/italic and other things within environments like that---it's very nice if things like shape, weight and so on can be switched independently. It's also very nice if optical design sizes switch automatically with the current size. Consider, for example, something like this: a book on film with a header: "Fellini's Roma and 8 1/2". I'm used to setting something like this in this way: Fellini's \it{Roma} and \it{\cvfrac{8}{1}{2}} (where \cvfrac{}{}{} is a macro that gives me a compound vulgar fraction). The header is itself in smallcaps, so what comes out is: Fellini's <small caps> Roma <italic small caps> and <small caps> 8 <italic proportional lining> (italic and lining (i.e., uppercase) because it's a title) 1/2 <italic numerator><italic><italic denominator> all with minimal effort on the part of the writer. It seems natural that way. > Do you plan to switch between oldstyle and lining figures each sentence? I've certainly done that before, with lining for quantities and oldstyle for everything else (mostly chapter and page numbers). Of course, other sorts of numerals turn up a lot too---the numerator and denominator variants for fractions, the superiors for footnotemarks and ordinals, and occasionally inferiors as well. > Do you need condensed and regular width together in the running text > or do you want one in the text and the other in the header? The different widths of my sans is one thing I hadn't counted on using much (I spend more time in serif) but, since I have the fonts, I thought it would be nice to be able to use them. More than the specific uses I've mentioned above, I'm used to the freedom of being able to use what I have when the need arises. > ConTeXt is not a DTP program and has a completely different concept. I'm aware of that. I've been using LaTeX for fifteen years now. I keep hearing about Context and the work with Luatex and I want to try it out to see whether I can get higher quality. Loading and switching fonts is just the first hurdle. If it's too difficult to do this in Context, that's okay. I realize that it's a work in progress and these things may be improved someday. I just want to get as much working as I can right now so I can try out more things. I have two fonts to install. I've been at it for two weeks. I realize it might take a few more weeks and a lot of work. I know it's not as easy as dropping them in a folder. That's okay. I'll keep at it. > Before we can give you better answers think about what do want > to achieve and where do you need a certain font feature and style, > when you have a clear picture about this ty to describe it and we > try to help you.

2 2

typescripts
by Michael Saunders 18 Mar '10

18 Mar '10

Wolfgang Schuster: > You can apply only *one* feature to \definefontfeatures. I've seen examples like this: \definefontfeature [fea] [mode=node,language=dflt,script=arab, init=yes,medi=yes,fina=yes,isol=yes, liga=yes,dlig=yes,rlig=yes,tlig=yes, calt=yes,trep=yes,mark=yes,mkmk=yes, kern=yes,curs=yes] so I think you mean to say that I can apply only one feature to \definefontsynonym or to \definetypeface. I tried this and it checks out. Thanks---it's nice to see hz working. Protrusion is only on the right margin? > > 2. As far as I can tell from trying to decode examples, there is some > > hidden connection between the first arguments of the second typescript > > block and the font switches. So, for example, a secret connection > > between SerifBoldItalic and \bi seems to connect Junicode-BoldItalic > > to \bi. Fine, but, in all the examples I've seen, there are no more > > than two weights and no widths. In some cases, I have five weights > > (light, book, medium, semi-bold, bold). How do I set up the > > typescript for this and the switches in the text? Must I learn more > > pairs like (SerifBoldItalic, \bi)? You need more typefaces. One for light, another one for condensed etc. ------------------------------ Mojca Miklavec: >> Must I learn more pairs like (SerifBoldItalic, \bi)? > Yes, but there are not many (tf, it, sl, bf, bi, bs, sc) and I assume > that they are extensible. See also below. > > You need more typefaces. One for light, another one for condensed etc. > Maybe I'm wrong, but shouldn't it be possible (I didn't test) to > modify font-unk.mkiv and add a few extra definitions to the following? > (Maybe not modify font-unk itself, but just adding a couple of more > definitons to the typescript.) > > \definebodyfont [default] [rm] > [tf=Serif sa 1, > bf=SerifBold sa 1, > it=SerifItalic sa 1, > sl=SerifSlanted sa 1, > bi=SerifBoldItalic sa 1, > bs=SerifBoldSlanted sa 1, > sc=SerifCaps sa 1] > > You could add your > in=SerifYourFontVariantName sa 1, > bd=SerifYourOtherFontVariantName sa 1, > > And then > \definefontsynonym[SerifYourFontVariantName][YourFontName] > It's true that most people don't do that, but I see no reason for not > extending the model for your particular needs. Mojca ------------------------------ Wolfgang Schuster: > The last time i did this you needed for MkIV also > > \definefontalternative[in] > \definefontalternative[bd] > > but be carefull with the shortcuts, \in is already used (references). Thank you both. I want to begin experimenting with this, but there's one thing that still confuses me. If I have a font with say, forty different combinations of weight/width/shape (5x4x2), I will need to come up with forty different pairs like: myNewFontSwitch=SerifMyFontVariantName sa 1, a strain on the poetic imagination, but possible. It would be nicer though, if I could change weight/width/shape independently of each other (then I need have only 5+4+2 switches). For example, when I see something like: \rm\tf roman \it italic \bf bold resulting in: <book roman> <book italic> <bold roman>, it's surprising to see that \bf has turned off the italic---you don't expect a switch of the weight to have a hidden switch of the shape in it. Could the typescript be set up with fewer switches, so that: \rm\tf roman \it italic \bf bold would result in: <book roman> <book italic> <bold italic>, or, e.g., \rm\tf (regular book roman) \cd (condensed) \it (italic) \bf (bold) would result in: <regular book roman> <condensed book roman> <condensed book italic> <condensed bold italic>? (Also, I'm hoping that having a dozen different sets of font features won't require twelve times as many switches and feature names as this. I think there is some easier method for switching---Hans mentioned \addff{}, but I can't find anything in the docs. If that works, that would make two kinds of switches, one for some kinds of features and another for other kinds.)

2 2

xml TeX expansion?
by Hans van der Meer 17 Mar '10

17 Mar '10

Typesetting material containing macro's from inside a xml-node does not give TeX-ed results. How can this be accomplished? ==== Minimal example ConTeXt code: \startxmlsetups xml:testsetups \xmlsetsetup{test}{test}{xml:*} \stopxmlsetups \xmlregistersetup{xml:testsetups} \startxmlsetups xml:test \xmlflush{#1}% same with: \xmltext{#1}{} \stopxmlsetups \setuppapersize[A6][A6] \starttext By \type{\xmlprocessfile{test}{test.xml}{}}:\par \xmlprocessfile{test}{test.xml}{} \blank Directly:\par This must be {\bf bold text}. \stoptext ==== Input: <?xml version="1.0" encoding="UTF-8"?> <test> This must be {\bf bold text}. </test> ==== Output: Hans van der Meer

4 10

tlig not active in register
by Piotr Kopszak 17 Mar '10

17 Mar '10

Dear list, I'd love to provide a minimal example but before I figure out how to do that a short question: I'm using the same font in the body text and registers: Jannon Text, tex ligatures via fontfeatures work in the body text but not in registers in page scopes. Any ideas? Piotr -- http://okle.pl

2 3