March 2010 - ntg-context - NTG Mailing Lists

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

Numbered enumerations in MK-IV (howto) ?
by gummybears 16 Mar '10

16 Mar '10

Hi, In MK-II the following enumeration worked, sadly in MK-IV they don't. I browsed the internet, tried the proclaim "solution" and searched the mailing list for an solution, found that several people experiencing the same problem with different numbering schemes. Tried several of the proposed solution but no success. I hope someone can help to fix this. Test file \defineenumeration[artikel][location=left,text=Artikel,headstyle=bold,stopper=.,distance=5pt,width=broad,before=\blank,after=\blank] \setupenumerations[subartikel][text=,location=left,stopper=.,width=broad,distance=5pt,before=,after=] \setupenumerations[subsubartikel][text=,location=left,stopper=.,width=broad,distance=5pt,before=,after=] \starttext %\startcolumns[n=2] \startartikel Number should be 1. \stopartikel \startsubartikel Number should be 1.1. \stopsubartikel \startsubartikel Number should be 1.2. \stopsubartikel \startsubsubartikel Number should be 1.2.1. \stopsubsubartikel \startsubsubartikel Number should be 1.2.2. \stopsubsubartikel \startartikel Number should be 2. \stopartikel \startsubartikel Number should be 2.1. \stopsubartikel \startsubartikel Number should be 2.2. \stopsubartikel \startsubsubartikel Number should be 2.2.1. \stopsubsubartikel \startsubsubartikel Number should be 2.2.2. \stopsubsubartikel \startartikel Number should be 3. \stopartikel \startsubartikel Number should be 3.1. \stopsubartikel \startsubartikel Number should be 3.2. \stopsubartikel \startsubsubartikel Number should be 3.2.1. \stopsubsubartikel \startsubsubartikel Number should be 3.2.2. \stopsubsubartikel %\stopcolumns \stoptext

3 2

Re: [NTG-context] version differences
by Hans Hagen 16 Mar '10

16 Mar '10

On 16-3-2010 14:56, Steffen Wolfrum wrote: > Hi Hans, hi Taco, > > > I just updated my minimal from 02. March to 12. March ... and everything looks totally messed up ;o) > Bodytext and footnotes both have surprising horizontal and vertical spaces everywhere! > > Is there a place where you list up what changes took place with each new version? there is indeed a problem that in some situations can show up ... has to to with some glue spec settings in luatex; yesterday taco and i spent quite some time on it and there will be a luatex/mkiv release this week that catches it Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

1 0

xml with interaction fails in footnotes
by Philipp Gesang 16 Mar '10

16 Mar '10

Good evening all, I'm experiencing a weird behaviour when using my module to transliterate stuff in a footnote. ConTeXt fails with an undefined control sequence if an only if I switch on interaction. The issue vanishes when I removing either the footnote environment or the interaction or the transliteration or the tag with the text to be transliterated. In the following minimal example I specified the lines that will make context process the file when commented out. Please note that everything works fine outside xml as the transliteration immediately after “\starttext” demonstrates. Thanks for any help, Philipp ---8<-------------------------------------------------------------------------- \enabletrackers[xml.entities] \enabletrackers[xml.parse] \enabletrackers[xml.path] \enabletrackers[xml.profile] \enabletrackers[xml.remap] \enabletrackers[lxml.access] \enabletrackers[lxml.comments] \enabletrackers[lxml.loading] \enabletrackers[lxml.manipulations] \enabletrackers[lxml.setups] \setupinteraction[state=start] %this one \usemodule[transliterator] \startxmlsetups xml:testsetups \xmlsetsetup{\xmldocument}{*}{-} \xmlsetsetup{\xmldocument}{ body| content| trru| %this one fn| }{xml:*} \stopxmlsetups \xmlregistersetup{xml:testsetups} \startxmlsetups xml:body \xmlflush{#1} \stopxmlsetups \startxmlsetups xml:content \xmlflush{#1} \stopxmlsetups \startxmlsetups xml:fn \startfootnote %this together with … \xmlflush{#1} \stopfootnote %… this one \stopxmlsetups \startxmlsetups xml:trru \starttransliterate %this together with … \xmlflush{#1} \stoptransliterate %… this one \stopxmlsetups \starttext \transliterate{раз, два, три} \startbuffer <body> <content> Content to include with a footnote <fn> <trru>раз, два, три</trru> %this one </fn> </content> </body> \stopbuffer \xmlprocessbuffer{test}{}{} \stoptext ---8<-------------------------------------------------------------------------- -- () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments

4 12

blank line and signals
by Andreas Harder 16 Mar '10

16 Mar '10

Hi all, please have a look at the following example: \newsignal\SectionSignal \def\TestSpace% {\relax\ifdim\lastskip=\SectionSignal \blank[nowhite] \else \blank \fi} \setuphead[section] [after=\blank\vskip\SectionSignal] \setuphead[subsection][before=\TestSpace] \starttext \startcolumns \section{Section} \subsection{Subsection} \dorecurse{50}{some text, } \stopcolumns \stoptext If one removes the blank line after \section{Section} the output is correct, otherwise \TestSpace is ignored … I'm quite sure it worked a couple of weeks before. Best regards Andreas

4 8