- ntg-context - NTG Mailing Lists

How to switch single font?
by Henri Menke 05 Aug '16

05 Aug '16

Dear list, how can I switch to another typeface for the, say, roman font only? When I use \definefontfamily to do so it switches *all* the fonts, including math, to the one loaded (example below). This leads to very undesirable effects, such as math is no longer set in italics. Cheers, Henri --- \definefontfamily[main][rm][Linux Libertine O] \setupbodyfont[main] \starttext foo $bar$ \stoptext

2 1

Question about a link in a footnote to cite
by Ursula Hermann 05 Aug '16

05 Aug '16

Hello list! I would like to know: If I have this in a footnote \footnote\cite Truman, Harry: Inaugural Address. 1949. Letzter Zugriff: 10.07.2013, http:// <http://www.presidency.ucsb.edu/ws/?pid=13282> www.presidency.ucsb.edu/ws/?pid=13282. [Hervorhebung I.G.] whats the right way? \startbuffer[biblio] @url and I have an author and a year, do I have to write it here? } \stopbuffer \mainlanguage[en] \usebtxdataset[biblio.buffer] \starttext \startbodymatter \startchapter[title={Me}] That's me \footnote{\cite[url, author, year]? \stopchapter \stopbodymatter \startbackmatter \startchapter[title={Bibliography}] \placelistofpublications \stopchapter \stopbackmatter \stoptext

2 1

Question about links
by Ursula Hermann 05 Aug '16

05 Aug '16

Hello Henry and Alan and Wolfgang! If I have this example, wich works really fine , I would like to know , how the same sample works if i have a link in a footnote and want to write \cite ,with an autor and a year ? . \startbuffer[biblio] @url? , what is next to write, the autor, the year? Or only the link? } \stopbuffer \mainlanguage[en] \usebtxdataset[biblio.buffer] \starttext \startbodymatter \startchapter[title={Me}] Your attachment actively impedes the aim that brought you to it initially \footnote{\cite[url] [www.contextgarden.net]? \stopchapter \stopbodymatter \startbackmatter \startchapter[title={Bibliography}] \placelistofpublications \stopchapter \stopbackmatter \stoptext Thanks for your help. Uschi

1 0

OTF feature for a math font
by Mohammad Hossein Bateni 05 Aug '16

05 Aug '16

Dear Hans & Wolfgang, I resolved some of the minor issues. But the main question still stands. Is it possible to add an OTF feature to the math font? In the very simple case, I want to change any sequence like "1.2" to "1/2". My feature (see below) works for text fonts but not in math mode. Thanks, MHB On Tue, Aug 2, 2016 at 3:54 PM, Mohammad Hossein Bateni <bateni(a)gmail.com> wrote: > Could the problem be because math fonts use mode=base instead of > mode=node? Or is it because in math fonts, the digits and/or full-stop > have different codes? > —MHB > > On Mon, Aug 1, 2016 at 9:46 AM, Mohammad Hossein Bateni <bateni(a)gmail.com> > wrote: > >> Dear list, >> >> I want to add a customized font feature to the math font, to >> automatically change the decimal point (unicode 0x2E) to the Arabic/Farsi >> version (unicode 0x66B). This will go well with the mapping from Latin >> digits to Farsi digits (done in a sample with mathdigits fallback). >> >> For instance, I want to code in $123.45$ and get a result like ۱۲۳٫۴۵. >> However, I do not want to simply map 0x2E to 0x66B, because then "full >> stop" outside a number will also change. In particular, I'd like to have >> the mapping only when full-stop is preceded and succeeded by a digit. This >> will, among other things, leave the end-of-equation periods unchanged. >> >> Here is how I tried to achieve it. >> >> >> \startluacode >> digits = { 0x30, 0x31, 0x32, 0x33, 0x34, 0x35, 0x36, 0x37, 0x38, 0x39 } >> -- 0x66B instead of 0x2F gives an error! >> replacements = { [0x002E] = { 0x2F } } >> fonts.handlers.otf.addfeature { >> name = "mpf", >> type = "chainsubstitution", >> lookups = { { >> type = "multiple", >> data = replacements, >> } }, >> data = { >> rules = { >> { >> current = { { 0x002E } }, >> after = { digits }, >> before = { digits }, >> lookups = { 1 }, >> } >> } >> } >> } >> \stopluacode >> >> \definefontfeature[mathperiod][mpf=yes] >> >> \resetfontfallback [mathdigits] >> %\definefontfallback[mathdigits][dejavusansmono][ >> digitsextendedarabicindic][check=yes,force=yes,offset=digitsnormal] >> >> \definefontsynonym [MathRoman][name:modern][ >> features={math\mathsizesuffix,mathperiod},goodies=lm-math, >> fallbacks=mathdigits] >> >> \starttext >> $123.45.$ >> >> 123.45. >> >> \addff{mathperiod} >> 123.45. >> \stoptext >> >

1 0

\typescriptthree within the optional argument of \definefontsynonym
by Mohammad Hossein Bateni 04 Aug '16

04 Aug '16

Hello Hans, Suppose you have a typescript as follows. \starttypescript [first] [MyFont] [GoodieOne,GoodieTwo] \definefontsynonym [Serif] [\typescripttwo] [goodies=\typescriptthree] \stoptypescript Using macros \typescriptX (for X=one, two, and three) works in the first and second arguments in \definefontsynonym but not in the optional argument. This seems to be because the optional argument is not expanded. Is this a bug or a feature? What I want to do was have a set of "fixes" (correcting kern issues, etc.) for a collection of fonts. I can either put these in separate goodie files or feature sets (the latter being what I was trying but not in the sample above), and write generic typescripts that would load any of the fonts with its associated fixes. While I can use sans/serif/mono in the first argument, and name of the font in the second argument (to be mapped appropriately using \typescriptprefix to nmemonic name and real font name), the third (optional) argument of \definefontsynonym does not expand immediately, hence I'll end up with "undefined" \typescriptthree when it will be used. Best, Hossein

2 2

Re: [NTG-context] How to typeset a line as if it had zero height
by Wolfgang Schuster 03 Aug '16

03 Aug '16

> Joseph Canedo <mailto:josephcanedo@gmail.com> > 3. August 2016 um 21:48 > > Thanks Wolfgang, out of curiosity what does \GotoPar macro ? Is this > similar to \ignorespaces ? > The \GotoPar removes the following \par or empty line to ensure the previous and the following text stay on the same line. %%%% begin example \define\RuleOne{\dontleavehmode\blackrule[width=4cm,color=orange]} \define\RuleTwo{\dontleavehmode\blackrule[width=4cm,color=yellow]\GotoPar} \starttext \RuleOne \input ward \RuleTwo \input ward \stoptext %%%% end example Wolfgang

1 0

How to typeset a line as if it had zero height
by Joseph Canedo 03 Aug '16

03 Aug '16

Dear all, I have this simple MWE : \starttext \startsection[title=Section] \startalignment[flushright]Line.\stopalignment %% how to make this « 0 height » ? \input knuth \stopsection \stoptext How can I, with ConTeXt or plain TeX, modify this simple example to typeset the text above as if the right aligned line (‘Line’ just below the section) had 0 height (ie the main paragraph with knuth quot is just after the section without blank line) ? By « 0 height » I mean it takes no vertical space but it is still typeset. I hope my question makes sense. Thanks a lot for any insiight. Best regards Joseph Canedo

3 2

Re: [NTG-context] Hyphenation errors (again or still) in recent mkiv
by Robert Blackstone 02 Aug '16

02 Aug '16

On 31 Jul 2016, at 21:06 , Hans Hagen <pragma(a)wxs.nl> > > On 7/31/2016 12:57 PM, Robert Blackstone wrote: >> Dear all, >> >> In the setupfile of my project I have \mainlanguage[en]. The font used is Verdana. >> With mkiv versions till october 2015 the hyphenation of English words was always correct. >> >> The same files compiled with mkiv of july 2016 (version 2016.07.18 16;26) give hyphenations that are definitely wrong. >> Some examples: begi-nning, pr-ocedure, adequ-ately, st-yle >> >> I made some tests with Linux Libertine sans and here also the earlier mkiv's gave correct hyphenations, the july version wrong ones. >> >> So it seems that ref. hyphenation something is wrong with this mkiv-version. Or do I now have to use something other than \mainlanguage[en] ? > > no example so no solution > > Hans Hi Hans, Here is an example: %%%%%%%%%%%%%%%%% \mainlanguage[en] \usemodule[simplefonts] \setmainfont[Verdana] \setupbodyfont[10pt] \contextversion \showgrid \starttext \input knuth \medskip \input tufte \stoptext %%%%%%%%%%%%%%%%% With mkiv version 2015.10.09 21:28 there are no hyphenation errors. With mkiv version 2016.07.18 16:46 the following errors occur: wo-uld (line 6), synth-esize (line 13), enum-erate (line 18) I mentioned some more errors in my original mail, see above. Best regards, Robert Blackstone

6 7

Custom exporters
by Henri Menke 02 Aug '16

02 Aug '16

Dear list, inspired by the question »Convert ConTeXt to LaTeX« on TeX.SX [1] I wondered whether the export backend of ConTeXt allows to write custom exporters. I imagine that the XML backend simply translates ConTeXt markup to XML markup. Such a translation appears to me to also be feasible for other markup languages such as LaTeX or even Markdown. If it is possible to write custom exporters, could someone give me a starting point by pointing out the relevant files? Cheers, Henri [1] https://tex.stackexchange.com/questions/321610

1 0

Re: [NTG-context] Hyphenation errors (again or still) in recent mkiv
by Robert Blackstone 02 Aug '16

02 Aug '16

On 1 Aug 2016, at 14:40 , Hans Hagen <pragma(a)wxs.nl> > To: ntg-context(a)ntg.nl > Subject: Re: [NTG-context] Hyphenation errors (again or still) in > recent mkiv > Message-ID: <d887e5a3-1195-b141-623f-897f7540f457(a)wxs.nl> > Content-Type: text/plain; charset=utf-8; format=flowed > > On 8/1/2016 11:52 AM, Wolfgang Schuster wrote: >>> Robert Blackstone <mailto:blackstone.robert@gmail.com> >>> 1. August 2016 um 11:02 >>> On 31 Jul 2016, at 21:06 , Hans Hagen <pragma(a)wxs.nl> >>> >>> >>> Hi Hans, >>> >>> Here is an example: >>> >>> %%%%%%%%%%%%%%%%% >>> >>> \mainlanguage[en] >>> \usemodule[simplefonts] >>> \setmainfont[Verdana] >>> \setupbodyfont[10pt] >>> \contextversion >>> \showgrid >>> >>> \starttext >>> \input knuth >>> \medskip >>> \input tufte >>> \stoptext >> The wrong hyphenation happens also with the default font. >> >> %\startexceptions[en] >> % would syn-the-size enu-mer-ate >> %\stopexceptions >> >> \starttext \hsize=1mm >> would synthesize enumerate >> \stoptext > > just wondering, as on my machine and luigi's things run ok .. can this > be a osx binary issue? > > Hans My apologies for not answering this particular question, other than by saying that indeed I work on a Mac, two in fact, one with OSX 10.9.5 Mavericks, the other on OS X 10.11.5 El Capitan. No difference in this respect: they produce the same hyphenation errors in an English text. To complicate (perhaps) matters a bit: I did some tests with German, French and Italian texts. Compilation with different mkiv - versions produced no differences and no hyphenation errors. So far I found hyhpenation errors only in English texts compiled with recent mkiv's on a Mac. I hope this helps to find a remedy. Best regards, Robert Blackstone

1 0