January 2014 - ntg-context - NTG Mailing Lists

Multipage xtables starts at the wrong page
by Marco Pallante 10 Jan '14

10 Jan '14

Hello everyone, I'm using ConTeXt to write a technical manual and I'm facing with some strange behavior I don't know how to overcome. I need a multipage table and I'm using the xtables. This is a (stripped down) version of a part of my document: \mainlanguage [en] \setupxtable [externaldocs] [split=repeat, header=repeat, bodyfont=8pt, foregroundstyle=\ss, option=stretch, align=middle, frame=off, bottomframe=on, framecolor=elitalblue] \setupxtable [externaldocsheader] [background=color, backgroundcolor=black, foregroundcolor=white, foregroundstyle=\ss\bf] \starttext \chapter{Introduction} \startxtable [externaldocs] \startxtablehead \startxrow [externaldocsheader] \startxcell AD No. \stopxcell \startxcell Title \stopxcell \startxcell Doc No. \stopxcell \startxcell Issue \stopxcell \startxcell Date \stopxcell \startxcell Applicability \stopxcell \stopxrow \stopxtablehead \startxtablebody \dorecurse{60}{ \startxrow \startxcell AD No. \stopxcell \startxcell Title \stopxcell \startxcell Doc No. \stopxcell \startxcell Issue \stopxcell \startxcell Date \stopxcell \startxcell Applicability \stopxcell \stopxrow } \stopxtablebody \stopxtable \stoptext What I get, however, is a table that starts at page 2 and not just after the chapter head. If the number of rows is smaller and the table fit the first page, then it starts at the right place. What I'm doing wrong? Thank you very much, Marco

4 9

Macro expansion inside \type
by Devendra Ghate 09 Jan '14

09 Jan '14

Hello Everyone, Consider the following MWE: \define\author{Devendra Ghate} \starttext \type{\author} \stoptext As mentioned on the wiki, this doesn't expand `\author` but rather prints it as it is. However, I would like `\author` to be expanded before it is typeset. Is this possible? Regards, Devendra Ghate

2 1

Mixing math and text font
by Joshua Krämer 09 Jan '14

09 Jan '14

Dear list, in my math, I would like one font (the text font) to be used for letters and digits and another font (the math font) to be used for mathematical symbols. I have tried it like that: % Example 1 \usemodule[simplefonts][size=40pt] \setmathfont[termes] \setmainfont[latinmodernroman] \starttext 123\\$ 123 \coprod \leftrightarrow $ \stoptext % Example 2 \definetypeface [fonttest] [rm] [serif] [modern] \definetypeface [fonttest] [mm] [math] [termes] \setupbodyfont[fonttest, 40pt] \starttext 123\\$ 123 \coprod \leftrightarrow $ \stoptext In both examples, the math font is used for the whole formula. How can I mix the fonts? Kind regards and best wishes for 2014, Joshua Krämer

3 14

Fallback for mathematical lowercase h and hyphen
by Joshua Krämer 09 Jan '14

09 Jan '14

Dear list! (1) With the following example, only manually inserted hyphens are replaced. How can I replace the hyphen automatically inserted at linebreaks? \definefontfeature[extended][default][extend=3] \definefallbackfamily[mainface][serif][TeX Gyre Termes] [range={0x0002d}, features=extended] \definefontfamily[mainface][serif][Latin Modern Roman] \setupbodyfont[mainface, 30pt] \starttext line-break \dorecurse{100}{linebreak } \stoptext I have added the feature "extended" only for better distinction. (2) In the following example, the lowercase h is not replaced. I think this may be because it is separately encoded as "Planck constant" (U+210E) in math fonts. \definefontfamily[mainface][serif][Latin Modern Roman] \definefallbackfamily[mainface][math][Latin Modern Roman] [preset=math:lowercaseitalic] \definefontfamily[mainface][math][TeX Gyre Termes Math] \setupbodyfont[mainface, 30pt] \starttext $ abch $ \stoptext Kind regards, Joshua Krämer

1 0

Malayalam shaping with mkiv/LuaTeX
by Rajeesh K Nambiar 09 Jan '14

09 Jan '14

Hello, especially Hans and Kai, I have succeeded to an extent in adding Malayalam shaping to the existing Devanagari shaping. Being a complete novice in Lua and mkiv, I'm at a point where your expertise is needed to proceed further. Please find the attached patch, test case listed below and expected rendering for comparison. Additionally needed to support: 1. Decomposing 2 part Matras (dependent vowels) - 0D4A, 0D4B, 0D4C for Malayalam [Test cases 2 & 4]. This is needed (at least) for Tamil also. I guess it is as simple as replacing one code point with 2 others - example: replace 0D4A with 0D46, 0D3E. See page 3 of this Unicode standard: http://www.unicode.org/charts/PDF/U0D00.pdf 2. Handling "pref" opentype feature for v2 opentype spec (script tag "mlm2"). This is required for Malayalam Ra ligature, the glyph is formed correctly but it needs to be reordered as pre-base to the base syllable [Test case 1]. (Note that the old spec "mlym" handles "Ra form" as "pstf" and no reordering required). You can observe the difference in Test case 5 - Ra form should be attached to first consonant instead of second one ("mlm2" needs glyph formed by Virama+Ra to be reordered as pre-base to first consonant, while "mlym" doesn't need to). 3. Handling "pstf" opentype feature. It works mostly [Test case 8], except when a post-base Matra follows [Test case 9]. 4. Test cases 6 & 7 shows an example where glyph formation fails when a "pstf" Ya follows. This works correctly with some other conjuncts, though. 4. font-odv.lua hard coded Devanagari Virama (094D) and Ra (0930) in certain places, which needs to use table values to handle other scripts. 5. I had to change "methods.deva" to "methods.mlym" and "methods.dev2" to "methods.mlm2" to get this working, not sure how best to handle multiple scripts. 6. There are other cases like Dot-reph (0D4E) which uses GPOS table and requires reordering as post-base to the syllable follows it, but I haven't looked into them yet. i) The font used is Rachana, which supports both "mlm2" and "mlym" specs, can be downloaded from here: http://download.savannah.gnu.org/releases/smc/fonts/malayalam-fonts-6.0/Rac… You can switch to "mlm2" and "mlym" in test case. ii) Expected rendering of this test case: http://rajeeshknambiar.fedorapeople.org/ConTeXt/context-test.png iii) Test case: ----------- 8< --------- \usemodule[font-odv] \definefontfeature[malayalam][mode=node,language=dflt,script=mlm2,akhn=yes,blwf=yes,half=yes,pres=yes,blws=yes,psts=yes,haln=no] %\definefontfeature[malayalam][mode=node,language=dflt,script=mlym,akhn=yes,blwf=yes,half=yes,pres=yes,blws=yes,psts=yes,haln=no] \starttypescript [serif] [rachana] [name] \definefontsynonym[Serif] [file:rachana][features={malayalam}] \stoptypescript \starttypescript [rachana] \definetypeface[rachana][rm][serif][rachana][default] \definetypeface[rachana][mm][math] [modern][default] \stoptypescript \setupbodyfont[rachana] \starttext 1. \char"0D15 \char"0D4D \char"0D24 \char"0D4D \char"0D30 \\ % ക്ത്ര 2. \char"0D15 \char"0D4D \char"0D24 \char"0D4D \char"0D30 \char"0D4B \\ % ക്ത്രോ 3. \char"0D38 \char"0D4D \char"0D2A \char"0D4D \char"0D30 \\ % സ്പ്ര 4. \char"0D38 \char"0D4D \char"0D2A \char"0D4D \char"0D30 \char"0D4C \\ % സ്പ്രൌ 5. \char"0D24 \char"0D4D \char"0D30 \char"0D2A \\ % ത്രപ 6. \char"0D24 \char"0D4D \char"0D38 \\ % ത്സ 7. \char"0D24 \char"0D4D \char"0D38 \char"0D4D \char"0D2F \\ % ത്സ്യ 8. \char"0D15 \char"0D4D \char"0D2F \\ % ക്യ 9. \char"0D15 \char"0D4D \char"0D2F \char"0D42 \\ % ക്യൂ \stoptext ----------- >8 --------- Let me know if you need additional information or clarifications on test cases. [Patch, test case, expected output image etc are also available here: http://rajeeshknambiar.fedorapeople.org/ConTeXt/] -- Cheers, Rajeesh http://rajeeshknambiar.wordpress.com

3 11

betas
by Hans Hagen 09 Jan '14

09 Jan '14

Hi, As some of you might have noticed, we're in transition to luatex 0.80 (currently 0.78.1). This binary is somewhat faster with respect to nodes without modification of Lua code, but it also provides an additional node field access mechanism. Luigi and I spent quite some time on getting that done and in the process some 70 context files were adapted (as we needed to test). However, it's likely that I have missed some needed changes. As both access mechanisms cannot be mixed, one has to be consistent in usage. Also, the somewhat faster (new) usage is more sensitive for errors so it has to be used with robust (proven) code (read: pluggable code can best use the traditional node field accessors which also have been sped up). And of course it only makes sense for very demanding cases (as stock luatex is already rather efficient now), think of devanagari (where we can get 50% faster) and complex arabic (some 25%). As ConTeXt spends > 50% of its time in Lua it might make a difference in other places too. Anyway, for instance the 175 fonts-mkiv manual processes 10% faster due to this and sometimes more can be achieved (it really depends on how much Lua enhanced mechanisms are used). Roughly I get on my win 8.1 64 bit laptop for the font manual: 10 sec luatex 0.77 with previous context code base 10.25 sec luatex 0.77 with current context code base 9.00 sec luatex 0.78 with current context code base 7.50 sec luajittex 0.78 with current context code base (This manual loads quite some fonts in the process.) In case you wonder why speed is an issue: it really matters when tex is used as a service, and I like fast edit-test cycles too. The target is to get 20 pps or more even for complex documents. It's not that hard to get 550 pps for simple 1000 page one-word-per page documents but when much more kicks in we quickly drop to 15-20 pps. Also, Luigi and I also want to reach reasonable speeds on android phones (triggered by Harald's experiments at the context meeting) but that's another topic. 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 -----------------------------------------------------------------

1 0

\setcharactercasing misbehaviour
by Marco Patzer 09 Jan '14

09 Jan '14

Hi, \setcharactercasing requires a new paragraph to work. Seems like a bug to me. \starttext \setcharactercasing[Word]foo %% Uppercase \setcharactercasing[Word]bar %% lowercase \setcharactercasing[Word]bar %% Uppercase \stoptext Marco

2 2

Language “deo” causes “TeX capacity exceeded” when units are used
by Marco Patzer 09 Jan '14

09 Jan '14

Hi, the following example exceeds TeX's capacity: \mainlanguage [deo] \starttext \unit{10 square metre} \stoptext Marco

2 1

latest beta and luajittex in Linux 32-bit
by Pablo Rodriguez 09 Jan '14

09 Jan '14

Dear list, could anyone using the latest beta from ConTeXt Suite in Linux 32-bit confirm whether compilation with the option --engine=luajittex works? Many thanks for your help, Pablo -- http://www.ousia.tk

3 3

Re: [NTG-context] setuphead for in-paragraph head ?
by Jean-Guillaume 09 Jan '14

09 Jan '14

Thanks for your reply, Marco. Here is a full example: \starttext \definehead[Exercise][subsection] \setuphead [Exercise] [after=] \startExercise[]{(this is the exercise's title)} The exercise's content. \stopExercise \stoptext After contexting it, it looks like: 1 (this is the exercise's title) The exercise's content. Actually, I would like to have the head's number and the head's title on the same line. That is, whith no new line. Jean-Guillaume

2 1