- ntg-context - NTG Mailing Lists

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

typescripts
by Michael Saunders 17 Mar '10

17 Mar '10

I have been earnestly trying to understand how they work by attempting a slightly more complex one. So far, I have: ------------------------------------------------------- \definefontfeature[default][mode=node,language=dflt,script=latn,kern=yes,liga=yes,tlig=yes,trep=yes] \definefontfeature[body][onum=yes,pnum=yes,protrusion=quality,expansion=quality]%turn hz on %plus some I hope to use later \definefontfeature[tabular][sans=yes,tnum=yes,onum=yes]%turn hz off \definefontfeature[allcaps][cpsp=yes,case=yes,lnum=yes] \definefontfeature[smallcaps][smcp, onum=yes] \definefontfeature[swashes][swsh=yes] \definefontfeature[inferior][sinf=yes] \definefontfeature[superior][sups, ordn=yes] \definefontfeature[numerator][numr=yes] \definefontfeature[denominator][dnom=yes] \definefontfeature[prop-os][pnum=yes,onum=yes] \definefontfeature[prop-lin][pnum=yes,lnum=yes] \definefontfeature[tab-os][tnum=yes,onum=yes] \definefontfeature[tab-lin][tnum=yes,lnum=yes] \definefontfeature[ornaments][ornm=yes] \definefontfeature[lgc][script=latn,script=grek,script=cyrl] \starttypescript [serif] [junicode] \definefontsynonym[Junicode][name:junicode][features=default,features=body,features=lgc] \definefontsynonym[Junicode-Bold][name:junicodebold][features=default,features=body,features=lgc] \definefontsynonym[Junicode-Italic][name:junicodeitalic][features=default,features=body,features=lgc] \definefontsynonym[Junicode-BoldItalic][name:junicodebolditalic][features=default,features=body,features=lgc] \stoptypescript \starttypescript [serif] [junicode] \definefontsynonym[Serif][Junicode][features=default,features=body,features=lgc] \definefontsynonym[SerifBold][Junicode-Bold][features=default,features=body,features=lgc] \definefontsynonym[SerifItalic][Junicode-Italic][features=default,features=body,features=lgc] \definefontsynonym[SerifBoldItalic][Junicode-BoldItalic][features=default,features=body,features=lgc] \stoptypescript \starttypescript [junicode] \definetypeface [junicode] [rm] [serif] [junicode] [default] [features=default,features=body,features=lgc,features=hanging,features=hz] \stoptypescript \setupalign[hanging,hz] \setupbodyfont[junicode,12pt] ------------------------------------------------------------------------- but, 1. tlig and trep aren't working, so evidently, features=default isn't getting through. No hanging or hz is happening either---probably the same problem. 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)?

3 5

context beta not found
by Hans van der Meer 17 Mar '10

17 Mar '10

Did I miss some change in the ConTeXt beta location? Or a server blackout? On refreshing my ConTeXt beta I get from: curl -o first-setup.sh http://minimals.contextgarden.net/setup/first-setup.sh the error message: curl: (6) Couldn't resolve host 'minimals.contextgarden.net' Hans van der Meer

3 3

After rotation, interaction does no longer work
by berend＠pobox.com 16 Mar '10

16 Mar '10

Hi All, I've a document that is typeset in A5, and then arranged with 2SIDE. Interaction is enabled. Everything works, I can click on registers and table of contents to jump to the particular piece. However, if I add "rotated": \setuparranging [2SIDE,rotated] interaction appears to be disabled. Can this be enabled again? The following test document demonstrates the effect. The links in the table of content are still blue, not no longer clickable. Remove rotated, and it works: -------------------------------------------------- % interface=en \setuppapersize [A5][A4] \setuparranging [2SIDE,rotated] \setupinteraction [state=start, color=blue] \setupcolors [state=start] \starttext \subject{Table of contents} \placecontent[1] \chapter{Hello} World. \chapter{More} Text. \stoptext -------------------------------------------------- Process with "texexec --arrange" -- Thanks, Berend de Boer

2 3

\goto{}[] fails to find the document
by Willi Egger 16 Mar '10

16 Mar '10

Hi, I should give a presentation tomorrow. - It appears that Mr. Murphy is looking into this him self... Seriously, when issuing \goto{start here}[somefile::] results in no message that there is something amiss. However Acrobat Reader tells, that the file is not found. Please refer to the attached minimal file. Kind regards Willi

2 2

Re: [NTG-context] mkiv and unicode
by Wolfgang Werners-Lucchini 16 Mar '10

16 Mar '10

Hallo, > > I work all the time with good old mkii-context, but I have had a lot > > of problems last time, which could be solved easely if I switch to > > mkiv. So I wonder if I should change. The main argument for me to > > stay with mkii is the following: > > > > I have a lot of lua scripts withhin scite which are preprocessing my > > textfiles (string.gsub etc.) These scripts depent on ansi-code and do > > not work with unicode too. > > > > An other problem I have, is to teach scite to use utf-8 per default. > > (code.page=65001) does not work for me. I have tried this with a > > lot of versions of scite. > > code.page=65001 > output.code.page=65001 I have tried this very often. I have tried this in a fresh scite installation uncommenting this in the global propertie file. But it doesn't work. File->Encoding is Code Page Property. And my files are saved in Ansi. I do not want look every time if I have saved with the proper encoding. I do not want files with ansi and files in utf mixed. I have considered to change the editor, but I very like the lua ability. > > Has anybody experiences with scite-lua-scripts and unicode? > > it depends on what you do but normally lua does not care about funny > characters in strings > > an option is to run the script outside scite and pipe data back Yes, this should allow one to use special librarys. I have heard of 'slnunicode' but haven't tested it yet. Wolfgang

2 1

Re: [NTG-context] Numbered enumerations in MK-IV (howto) ?
by gummybears 16 Mar '10

16 Mar '10

@Bernard , thanks for your help, it works.

1 0