- ntg-context - Mailing Lists

wider item numbering in toc
by H. van der Meer 07 Dec '13

07 Dec '13

In the table of contents my items are numbers 1, 2, etc. At the number the aligning is wrong, the tens are shifted to the right. I tried to remedy with a setup: \setupitemgroup[itemize][each][5,autointro][…] But changing width, distance, textdistance, itemalign do not have effect on the toc. How to accomplish? Hans van der Meer

2 9

(critical edition) text reducing command
by Pablo Rodriguez 06 Dec '13

06 Dec '13

Hi Thomas, Luigi and Hans, I have a feature suggestion that might be interesting to implement for critical editions. Here is my code sample: \mainlanguage[la] \unexpanded\def\doVariant#1#2#3% {\startlinenote[#1]{#2] #3}#2% \prewordbreak\stoplinenote[#1]} \newcounter\VarCounter \unexpanded\def\Variant {\doglobal\increment\VarCounter \normalexpanded{\doVariant{Varia:\VarCounter}}} \starttext \startlinenumbering Gallia est omnis divisa in partes tres, \Variant{quarum unam incolunt Belgae, aliam Aquitani, tertiam qui ipsorum lingua Celtae, nostra Galli appellantur}{{\em om} X}. \blank Gallia est omnis divisa in partes tres, \startlinenote[firstone]{quarum ... appelantur] {\em om} X}quarum unam incolunt Belgae, aliam Aquitani, tertiam qui ipsorum lingua Celtae, nostra Galli appellantur\stoplinenote[firstone]. \stoplinenumbering \stoptext To automatically get the text reduced to the form that appears in the second paragraph, there should be a command for that. In this text reduction, one should be able to set how many words (no punctuation marks) should contain the text to be reduced, how many words should be printed before the separator, how many words should be printed after the separator and which is the separator. I don’t know whether this could be a good way of coding it: \definetextreduction[caesarcompressed] \setuptextreduction[caesarcompressed][totallength=5, wordsbeforesep=1, wordsaftersep=1, separator={...}] I think this feature may be especially relevant with TEI encoded texts. There is a shortcoming on my proposal: only words have to be counted and added to the output and punctuation signs should be ignored. But this is clearly limited, since exclamation and question marks (Spanish has both opening and closing marks for exclamation and question: ¿? ¡!) should not be counted as words (total, after or before), but they should be included in the reduced version of the text. The same happens with apostrophe. And I wonder whether the same rules should be applied to quotation marks. There is a special case: the semicolon is also used as question mark in Greek. I think it is clear than the semicolon should be removed for the reduced text in other languages than Greek, but it should be included (not counted) in Greek reduced texts. I hope the proposal and the issues it might arise are clear. Please, ask if they aren’t. Many thanks for your excellent work, Pablo -- http://www.ousia.tk

1 0

footer page number on first page of section: doesn't appear
by Lars Huttar 05 Dec '13

05 Dec '13

Hi, Based on our reading of http://wiki.contextgarden.net/FO_Page_Layout#First_Page we have the following MWE, which we want to put a page number in the footer on the first page only: \definetext[footerpagenumber][footer][pagenumber] \setuphead[section][header=empty,footer=footerpagenumber,number=no,align={middle,nothyphenated,verytolerant},style=ssbf] \starttext \section{My Own Section} \dorecurse{15}{ \input knuth \par } \stoptext Unfortunately, no page number shows up. If we add \setuppagenumbering[location=footer] before the \starttext, we get the page numbering we want, but it's on every page, not just the first. Is there something wrong with our setuphead? Thanks, Lars

3 4

a way to implement \testcolumn in mixedcolumns
by Lars Huttar 05 Dec '13

05 Dec '13

Hello, On this list I've been advised that mixedcolumns is the latest and greatest implementation of columns; the one to use. We have switched over from columnsets to mixedcolumns, and have been very pleased with the column balancing (for some reason we couldn't get column balancing to work in columnsets). However one thing we do miss from columnsets is the control over widows & orphans in two ways: \testcolumn, and \setupcolumnsetlines. \testcolumn[n] allowed us to do a conditional column break, so when we were about to start a new subsection heading, we could prevent it being an orphan at the bottom of the column; and when starting a paragraph with a hangaround graphic framed flushright and bottom, we could similarly use \testcolumn to prevent the graphic from hanging down into the footer (which is what sometimes happened otherwise). So I'm wondering, is there some way to achieve the equivalent of \testcolumn in mixedcolumns? Is it theoretically impossible to implement this in mixedcolumns because the required information (how many lines are left in the current column) is not yet known? Or could that information be gleaned from somewhere? I see in page-brk.mkiv the following definition for \testcolumn: \def\testcolumn {\dodoubleempty\page_tests_columns_test} \def\page_tests_columns_test[#1][#2]% {\endgraf \ifdim\pagegoal<\maxdimen \ifdim\pagetotal<\pagegoal \d_page_tests_test\dimexpr \pagegoal -\pagetotal \ifdim\lastskip<\parskip+\parskip\fi \ifsecondargument+#2\fi \relax \getrawnoflines\d_page_tests_test % (raw) \ifnum#1>\noflines \column \fi \else \penalty-\plustenthousand % (untested) \fi \fi} I'm not a low-level TeX programmer, and I don't understand a lot of this, but it looks like \getrawnoflines\d_page_tests_test puts the number of remaining lines into \noflines Any suggestions are appreciated. (And I should have a MWE soon.) Lars

3 11

Re: [NTG-context] [***SPAM***] OT: Generating Command reference from source code
by Wolfgang Schuster 04 Dec '13

04 Dec '13

Am 04.12.2013 um 20:11 schrieb Jan Tosovsky <j.tosovsky(a)email.cz>: > On 2013-12-04 Wolfgang Schuster wrote: >> Am 04.12.2013 um 18:56 schrieb Jan Tosovsky <j.tosovsky(a)email.cz>: >>> On 2013-12-04 Hans Hagen wrote: >>>> >>>> there is a (somewhat incomplete) reference definition in xml format >>>> so your (b) is in principle covered; >>> >>> where is it stored? >> >> The english interface is stored in the file cont-en.xml, the path for >> the file on my system is >> >> /Users/wolf/context/beta/tex/texmf- >> context/tex/context/interface/cont-en.xml >> >> A PDF with all commands from the files is available here: >> http://pragma-ade.com/show-man-10.htm > > Thanks. Interesting to see what can be found on my PC :-) You can produce the PDF yourself with "context --global x-set-12.mkiv“. > Unfortunately there isn't even minimal description what the particular > command does :-( The file shows only the syntax of the command, when you want a description of the command you have to writer this yourself. To show which keys and values are available for each command you can load a single one of them from the big file. > And what is the purpose of those localized versions? ConTeXt has a multilingual interface where you can use dutch, french etc. command names, e.g. \starttext … \stoptext is written as \starttekst … \stoptekst when you use the dutch interface. Wolfgang

1 0

Re: [NTG-context] [***SPAM***] OT: Generating Command reference from source code
by Wolfgang Schuster 04 Dec '13

04 Dec '13

Am 04.12.2013 um 18:56 schrieb Jan Tosovsky <j.tosovsky(a)email.cz>: > On 2013-12-04 Hans Hagen wrote: >> On 12/3/2013 10:59 PM, Jan Tosovsky wrote: >>> >>> Supposing that ... >>> a) every .mkiv file is enhanced by 'package' annotation >>> b) every public command/macro contains a description with the list of >>> all available params (sensible subset of JavaDoc annotations) >>> >>> .... I can imagine to extract this info and: >>> >>> A) build the static command reference website with all the hyperlinks >>> B) eventually generate PDF variant of the same >>> C) export it into the form which can be imported into the WIKI (with >>> read-only mode) >>> >>> If every change of behaviour was reflected immediately in the >>> description, if any newly added parameter was added into the parameter >>> list, the main goal would be achieved. >> >> there is a (somewhat incomplete) reference definition in xml format so >> your (b) is in principle covered; > > where is it stored? The english interface is stored in the file cont-en.xml, the path for the file on my system is /Users/wolf/context/beta/tex/texmf-context/tex/context/interface/cont-en.xml A PDF with all commands from the files is available here: http://pragma-ade.com/show-man-10.htm Wolfgang

2 1

Re: [NTG-context] [***SPAM***] OT: Generating Command reference from source code
by Hans Hagen 04 Dec '13

04 Dec '13

On 12/3/2013 10:59 PM, Jan Tosovsky wrote: > Dear All, > > in another thread I was dreaming ... to have always the complete and up to > date command/macro reference with basic descriptions and list all of the > parameter/options... > > 'Spoiled' by goodies offered by various Java APIs (based on > http://en.wikipedia.org/wiki/Javadoc ) I am missing this a lot. > > Example of the result: > http://docs.oracle.com/javase/7/docs/api/index.html?overview-summary.html > > In Java there is the following structure (simplified): > 1) 'packages' defining the hierarchy > 2) 'classes' defining objects > 3) 'properties' and 'methods' for every particular 'class' > > I've roughly scanned the ConTeXt source structure and bringing the following > idea: > > 1) There is no 'packages' counterpart in ConTeXt, but it would be handy to > think of any logical structure to group commands to logical groups (even > nested). Maybe the filename title prefix could be taken as a starting point > for this. > 2) 'classes' = all individual .mkiv files > 3) 'methods' = all public \def, \define etc in mkiv files (+maybe other > contructs I am not aware) > > Supposing that ... > a) every .mkiv file is enhanced by 'package' annotation > b) every public command/macro contains a description with the list of all > available params > (sensible subset of JavaDoc annotations) > > .... I can imagine to extract this info and: > > A) build the static command reference website with all the hyperlinks > B) eventually generate PDF variant of the same > C) export it into the form which can be imported into the WIKI (with > read-only mode) > > If every change of behaviour was reflected immediately in the description, > if any newly added parameter was added into the parameter list, the main > goal would be achieved. keep in mind that quite some functionality is the result of user requests and for a while can be in flux and i consider it then the users responsibility to wrap up on the wiki (for completely new mechanisms i often write a dedicated manual or an article for a user group journal) > But I understand there is lot of to do in the beginning... with disputable > effect in the end. > > I can help with some coding, transforming ... > > Jan > > Btw, would it be sufficient to scan texmf-context\tex\context\base\*.mkiv > files or there are other parts somewhere else? There are approx 500 files > now. It is huge number, but finite :-) there is a (somewhat incomplete) reference definition in xml format so your (b) is in principle covered; these definitions used to be in the source (more than a decade ago) but i moved them out because some functionality is stepwise provided (not in one place) and also because many commands are generated (you will not find their names by interpreting the source) the problem with tex (and therefore context) is that we are dealing with quite some interaction between unpredictable user input, macro (expansions), tex-internals, resources like fonts, patterns and whatever, etc. and this is why you often need to play with mechanisms: small test files and see how it looks (tex is a visual tool) it's often not as simple as "you feed it this" end "get back that" for documentation several methods are used: - examples in the test suite - some explanation in the source - explanations on the wiki - dedicated manuals - articles by users (+examples) although i sometimes run into impressive auto-documented documentation for languages or os commands, in practice i find myself looking for examples and/or experimenting and/or going into sources 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 -----------------------------------------------------------------

3 3

[***SPAM***] OT: Generating Command reference from source code
by Jan Tosovsky 03 Dec '13

03 Dec '13

Dear All, in another thread I was dreaming ... to have always the complete and up to date command/macro reference with basic descriptions and list all of the parameter/options... 'Spoiled' by goodies offered by various Java APIs (based on http://en.wikipedia.org/wiki/Javadoc ) I am missing this a lot. Example of the result: http://docs.oracle.com/javase/7/docs/api/index.html?overview-summary.html In Java there is the following structure (simplified): 1) 'packages' defining the hierarchy 2) 'classes' defining objects 3) 'properties' and 'methods' for every particular 'class' I've roughly scanned the ConTeXt source structure and bringing the following idea: 1) There is no 'packages' counterpart in ConTeXt, but it would be handy to think of any logical structure to group commands to logical groups (even nested). Maybe the filename title prefix could be taken as a starting point for this. 2) 'classes' = all individual .mkiv files 3) 'methods' = all public \def, \define etc in mkiv files (+maybe other contructs I am not aware) Supposing that ... a) every .mkiv file is enhanced by 'package' annotation b) every public command/macro contains a description with the list of all available params (sensible subset of JavaDoc annotations) ... I can imagine to extract this info and: A) build the static command reference website with all the hyperlinks B) eventually generate PDF variant of the same C) export it into the form which can be imported into the WIKI (with read-only mode) If every change of behaviour was reflected immediately in the description, if any newly added parameter was added into the parameter list, the main goal would be achieved. But I understand there is lot of to do in the beginning... with disputable effect in the end. I can help with some coding, transforming ... Jan Btw, would it be sufficient to scan texmf-context\tex\context\base\*.mkiv files or there are other parts somewhere else? There are approx 500 files now. It is huge number, but finite :-)

1 0

(critical edition) Examples of bib files
by luigi scarso 03 Dec '13

03 Dec '13

We are currently seeing the part of bibliography and we are looking for real examples in utf. You can post the examples on this ml, or send me privately. -- luigi

1 0

vertical square root upstroke (instead of having a slant)
by Sanjoy Mahajan 03 Dec '13

03 Dec '13

With the following minimal file on MkIV (2013.05.28 00:36 MKIV current), the upstroke of the square root is vertical instead of having the usual slant toward the right. With MkII it has the usual slant. I see this problem only with certain arrangements of variables (that recur often in my book chapter on springs and piano strings). For example, it goes away after changing the "\rho" to a "b". \starttext \startformula \sqrt{Tb^2\over \rho}. \stopformula \stoptext I know that the big math symbols are constructed differently in MkIV and MkII. Does the example above show an intended difference? -- -Sanjoy

2 2

Re: [NTG-context] Keeping titles together with the following text when grid is on
by Hans Hagen 03 Dec '13

03 Dec '13

On 12/2/2013 9:02 PM, Jan Tosovsky wrote: > On 2013-12-02 "H. Özoguz" wrote: >> On 2013-12-01 Jan Tosovsky wrote: >>> >>> when grid is on, orphan and widows have to be eliminated using > additional >>> penalty settings. Whereas it works fine for body text, section titles > are >>> still sometimes left at the bottom of the page. >> >> this is not the same question as handling orphan and widows - because >> you surely do not want some titles with only 2-3 lines of body text >> after them. >> >> I always use "\testpage[x]" to handle those issues, see your example >> with testpage: >> >> \setuphead[section][before={\testpage[8]\blank}] \blank[samepage,big] > Thanks, it works! Another magic command not documented anywhere in the > ConTeXt Guide or Wiki... > > I was looking for any alternative for XSL-FO's keep-with-next="always". This > is a different approach, but it doesn't matter. > > Btw, I still don't understand why keeping the title and text behaves > differently when grid is on... > > Jan > > ___________________________________________________________________________________ > If your question is of interest to others as well, please add an entry to the Wiki! > > maillist : ntg-context(a)ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context > webpage : http://www.pragma-ade.nl / http://tex.aanhet.net > archive : http://foundry.supelec.fr/projects/contextrev/ > wiki : http://contextgarden.net > ___________________________________________________________________________________ > -- ----------------------------------------------------------------- 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 -----------------------------------------------------------------

2 1

Command for the caption location inside \startplacefigure
by Géry Ogam 03 Dec '13

03 Dec '13

Hello, What is the option to specify the CAPTION location in \startplacefigure (I already now that you can do it from \setupcaption)? I thought the first argument of 'location' was for the FIGURE location, and the second one for the CAPTION location, but the second one has no effect: \startplacefigure[location={left, top}, title=A cow] \externalfigure[cow] \stopplacefigure Best regards.

1 0

xml selection on attribute expressions
by H. van der Meer 03 Dec '13

03 Dec '13

Following an example in the chapter on Expressions and filters for xml-processing one can select on an attribute ‘name’ in the node <file name=“whatever”/> file[@name=="whatever”]/command(todo) However, I would like to select on a combination of alternatives, so that equivalent are <file name=“whatever”/> and <file src=“whatever”/> I tried several variations but none of them work. \xmlfilter{#1}{file([@name=="whatever”] or [@src=="whatever”])/command(todo) \xmlfilter{#1}{file[@name=="whatever”] or [@src=="whatever”]/command(todo) \xmlfilter{#1}{file[@name=="whatever”] or file[@src=="whatever”]/command(todo) \xmlfilter{#1}{(file[@name=="whatever”]|file[@src=="whatever”])/command(todo) How to? Or is this impossible? Hans van der Meer

1 1

line notes compress
by Hans Hagen 03 Dec '13

03 Dec '13

Hi, The linenote compression options (and control) has been upgraded: \definepapersize [mine] [width=8cm, height=6cm] \setuplayout [location=middle, width=middle, height=middle, headerdistance=5mm] \setuppapersize [mine] [oversized] \definelinenote [MyNote] \setupnote [MyNote] [paragraph=yes] \setupnotation [MyNote] [alternative=serried, distance=.5em, width=broad] \setupalign [verytolerant] \showframe \startbuffer \setupfootertexts[\ttxx compress=\namednoteparameter{MyNote}{compress}\quad compressmethod=\namednoteparameter{MyNote}{compressmethod}] \startlinenumbering This\MyNote{That} context\MyNote{document} is\MyNote{was} a sample\MyNote{an example} that I\MyNote{she} want\MyNote{didn’t want} to show\MyNote{publish} \stoplinenumbering \page \stopbuffer \starttext \setupnote[MyNote][compress=yes,compressmethod=stopper] \getbuffer \setupnote[MyNote][compress=yes,compressmethod=separator] \getbuffer \setupnote[MyNote][compress=yes,compressmethod=space] \getbuffer \setupnote[MyNote][compress=yes,compressmethod=] \getbuffer \setupnote[MyNote][compress=no,compressmethod=stopper] \getbuffer \setupnote[MyNote][compress=no,compressmethod=separator] \getbuffer \setupnote[MyNote][compress=no,compressmethod=space] \getbuffer \setupnote[MyNote][compress=no,compressmethod=] \getbuffer \stoptext Keep in mind that paragraph notes are somewhat special so some tolerance in alignment helps. 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 -----------------------------------------------------------------

2 2

Re: [NTG-context] Keeping titles together with the following text when grid is on
by Alan Braslau 02 Dec '13

02 Dec '13

On Mon, 2 Dec 2013 21:40:55 +0100 Jan Tosovsky <j.tosovsky(a)email.cz> wrote: > Nowadays most of API/command references are generated automatically > directly from the source code comments. It ensures up to date data, > but it helps also to programmers. Descriptive comments in the source > helps to understand the given code when editing older parts. I do not > know to what extent it could be implemented here, but the respective > person could give it a try Sometimes/often the answers to many questions can be found in the source code, indeed. Also, most names are intended to be quite descriptive, and ConTeXt does not error in the use of terse, cryptic labels. In fact, descriptive comments in the source then become redundant when the code is written in such an explicit style. This does not mean that there is no need for good documentation and tutorials. Alan

1 0

Re: [NTG-context] Keeping titles together with the following text when grid is on
by Thomas A. Schmitz 02 Dec '13

02 Dec '13

On 12/02/2013 09:02 PM, Jan Tosovsky wrote: > Thanks, it works! Another magic command not documented anywhere in the > ConTeXt Guide or Wiki... So have you added it yet? Thomas

2 1

Re: [NTG-context] Keeping titles together with the following text when grid is on
by Aditya Mahajan 02 Dec '13

02 Dec '13

On Mon, 2 Dec 2013, Jan Tosovsky wrote: >> \setuphead[section][before={\testpage[8]\blank}] > > Thanks, it works! Another magic command not documented anywhere in the > ConTeXt Guide or Wiki... In that case, please add it to the wiki. Aditya

1 0

Re: [NTG-context] Keeping titles together with the following text when grid is on
by "H. Özoguz" 02 Dec '13

02 Dec '13

Hello, this is not the same question as handling orphan and widows - because you surely do not want some titles with only 2-3 lines of body text after them. I always use "\testpage[x]" to handle those issues, see your example with testpage: \setuppapersize[B5] \startsetups[grid][mypenalties] \setdefaultpenalties \setpenalties\widowpenalties{2}{10000} \setpenalties\clubpenalties {2}{10000} \stopsetups \setuphead[section] [before={\testpage[8]\blank}] %comment the following line to see the difference \setuplayout[grid=yes, setups=mypenalties] \showgrid \starttext \blank[force, 9.5cm] \input tufte \section{Tufte} \input tufte \stoptext Huseyin

2 1

\attachment
by Aditya Mahajan 02 Dec '13

02 Dec '13

It seems that there is a mixup in the backend code for including an attachment. For example, when I use: \setupinteraction[state=start] \starttext The current file is \attachment[tag][file=\jobname.tex, name=test.tex, title={Whatever}] \stoptext I was expecting that the current file will be attached as "test.tex" and title "Whatever. However, the title of the attached file is "tag". See the attached screenshot from Adobe Reader. It seems that in the back end, tag is written to the PDF file where title should have been written. Aditya

2 1

[***SPAM***] RE: Footnote line position
by Jan Tosovsky 01 Dec '13

01 Dec '13

On 2013-11-22 Jan Tosovsky wrote: > > when a single line footnote is used, the footnote divider is > rendered in larger distance than for footnotes with two or > more lines (I mean a gap between the line and the footnote text). > > It can be tested easily: > > \chapter{Chapter}Foo\footnote{Bar}. > \chapter{Chapter}Foo\footnote{Bar > > Bar}. > This behaviour seems to be driven by this code in strc-not.mkvi: \unexpanded\def\normalnoterule {\ifvmode \dontleavehmode \blackrule [\c!color=\noteparameter\c!rulecolor, \c!width=.2\hsize, \c!height=\noteparameter\c!rulethickness, \c!depth=\zeropoint]% \endgraf \kern\strutdepth \fi} When e.g. \endgraf or \kern\strutdepth lines are commented, the gap is smaller, but still different. Changing the depth from \zeropoint to a bigger value (1cm) makes the gap same, but it leads to extreme thick rule. What else could be tweaked here? Thnaks, Jan

1 0

Re: [NTG-context] Palatino patch for the current ConTeXt version
by Jan Tosovsky 01 Dec '13

01 Dec '13

On 2013-11-17 Jan Tosovsky wrote: > > I am trying to fix a Palatino small caps issue using the procedure > explained here: > http://wiki.contextgarden.net/Palatino_Linotype_under_MKIV > > That fix seems to be obsolete nowadays and returning errors. > almost fixed now using this procedure: 1) Create a new LFG file local fix_pala = { comment = "Switching i.sc glyphs indexes", fixes = function(data) local descriptions = data.descriptions descriptions[983201].index = 1170 descriptions[983261].index = 1110 end } return { name = "pala", comment = "Switching the small capped 'i' to a dotless variant in Palatino Linotype.", treatments = { ["pala.ttf"] = fix_pala, ["palai.ttf"] = fix_pala, ["palab.ttf"] = fix_pala, ["palabi.ttf"] = fix_pala, }, } 2) Place it into the folder where other LFG files are stored (tex\texmf-context\tex\context\fonts) 3) Execute 'mtxrun --generate' command to include newly added LFG file into a file database 4) Specify a new font feature referencing to this goodie in the source file: \definefontfeature[dotlessi][mode=base,goodies=pala] \definefontfamily[palatino][rm][Palatino Linotype][features={default,quality,dotlessi}] \setupbodyfont[palatino] \starttext {Athenians \smallcaps{Athenians}}\par {Athenians \sc{Athenians}}\par {\it Athenians \smallcaps{Athenians}}\par {\bf Athenians \smallcaps{Athenians}}\par {\bi Athenians \smallcaps{Athenians}}\par \stoptext 5) Trigger the generating It works except the regular font style. In this case \smallcaps option behaves differently than for e.g. \it or \bf styles. I am quite confused. Moreover, when faked caps are switched on using \sc, it works. Can anybody explain what is happening here? Thanks, Jan

1 0

Re: [NTG-context] Placefigure without Caption-Numbering
by Alan Braslau 01 Dec '13

01 Dec '13

On Sat, 30 Nov 2013 21:06:20 +0100 Jan Tosovsky <j.tosovsky(a)email.cz> wrote: > Indeed much cleaner. But that numbering option seems to be ignored ;-) > Does it work for you? Sorry, it is "number=no". Alan

1 0

Re: [NTG-context] Placefigure without Caption-Numbering
by Alan Braslau 30 Nov '13

30 Nov '13

On Sat, 30 Nov 2013 19:42:54 +0100 Jan Tosovsky <j.tosovsky(a)email.cz> wrote: > On 2013-04-16 Wolfgang Schuster wrote: > > Am 16.04.2013 um 18:56 schrieb "H. Özoguz" <h.oezoguz at mmnetz.de>: > > > > > > How to deactive the Caption-Numbering: > > > > > > \starttext > > > > > > \placefigure[here]{Blub}{\externalfigure[image][width=6cm]} > > > > > > \stoptext > > > > > > I want the caption "Blub", but not the "Figure 1" label. > > > > \placefigure[here,nonumber]{.}{.} > > It helped me now. > > Btw, there is no such an option mentioned in the WIKI or user guide... > > http://wiki.contextgarden.net/Command/placefigure > > But I'd like to add: > (1) caption=none renders 'none' instead of nothing... > (2) when key=none is combined, e.g. [none, page], the numbering is > suppressed, but the second option is ignored. But [page, none] works > fine. The order matters. It is same for [page, nonumber]. > > It would be nice to fix those examples in Wiki or if MkIV behaves > differently, add an appropriate alternative there. > > Thanks, Jan I find that the \startplacefigure \stopplacefigure interface is much cleaner: \startplacefigure [location=here,numbering=no,title=Blub] \externalfigure [image] [width=6cm] \stopplacefigure Alan

2 1

Re: [NTG-context] Placefigure without Caption-Numbering
by Jan Tosovsky 30 Nov '13

30 Nov '13

On 2013-04-16 Wolfgang Schuster wrote: > Am 16.04.2013 um 18:56 schrieb "H. Özoguz" <h.oezoguz at mmnetz.de>: > > > > How to deactive the Caption-Numbering: > > > > \starttext > > > > \placefigure[here]{Blub}{\externalfigure[image][width=6cm]} > > > > \stoptext > > > > I want the caption "Blub", but not the "Figure 1" label. > > \placefigure[here,nonumber]{.}{.} It helped me now. Btw, there is no such an option mentioned in the WIKI or user guide... http://wiki.contextgarden.net/Command/placefigure But I'd like to add: (1) caption=none renders 'none' instead of nothing... (2) when key=none is combined, e.g. [none, page], the numbering is suppressed, but the second option is ignored. But [page, none] works fine. The order matters. It is same for [page, nonumber]. It would be nice to fix those examples in Wiki or if MkIV behaves differently, add an appropriate alternative there. Thanks, Jan

1 0

Keeping titles together with the following text when grid is on
by Jan Tosovsky 30 Nov '13

30 Nov '13

Dear All, when grid is on, orphan and widows have to be eliminated using additional penalty settings. Whereas it works fine for body text, section titles are still sometimes left at the bottom of the page. It can be reproduced using this example: \setuppapersize[B5] \startsetups[grid][mypenalties] \setdefaultpenalties \setpenalties\widowpenalties{2}{10000} \setpenalties\clubpenalties {2}{10000} \stopsetups %comment the following line to see the difference \setuplayout[grid=yes, setups=mypenalties] \showgrid \starttext \blank[force, 9.5cm] \input tufte \section{Tufte} \input tufte \stoptext Is there any extra option for handling this? Thanks, Jan

1 0

Duplexing a single-sided layout?
by Adam Khan 30 Nov '13

30 Nov '13

I have a document in which left and right cannot be equated with inner and outer respectively (outside the header texts). So I use \setuppagenumbering[alternative={singlesided,doublesided}]. But I still need a gutter along (what would be) the inner margin. So, how would I go about duplexing a single-sided layout? For example: \definepapersize[custom][width=335mm,height=500mm] \setuppapersize[custom][B3] \setuplayout[% width=middle,% height=middle,% backspace=90mm,% topspace=25mm,% leftmargin=30mm,% rightmargin=15mm,% leftmargindistance=5mm,% rightmargindistance=20mm,% location={doublesided,duplex},% bottomspace=25mm,% cutspace=90mm] \setuppagenumbering[alternative={singlesided,doublesided}] Sincerely yours, Adam Khan

1 0

Re: [NTG-context] [***SPAM***] Provide showgrid as a PDF layer
by Hans Hagen 30 Nov '13

30 Nov '13

On 11/30/2013 12:04 AM, Jan Tosovsky wrote: > Dear All, > > it would be nice to have a possibility to interactively disable/enable a > grid rendered via \showgrid command. Whereas this grid is helpful for > debugging, it disturbs when the page is evaluated as the whole. Using layers > could make this process more efficient (not requiring to generate both > variants). > > I've noticed something like this is already implemented for the body area > (visualizer vbox layer). > > Or is there any option for this already? \setupinteraction[state=start] \showgrid \showframe \showmakeup \showlayoutcomponents \starttext \input tufte \placefigure{}{} \stoptext but you need a viewer that supports layers (can turn them on and off) 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 -----------------------------------------------------------------

2 1

[***SPAM***] Provide showgrid as a PDF layer
by Jan Tosovsky 30 Nov '13

30 Nov '13

Dear All, it would be nice to have a possibility to interactively disable/enable a grid rendered via \showgrid command. Whereas this grid is helpful for debugging, it disturbs when the page is evaluated as the whole. Using layers could make this process more efficient (not requiring to generate both variants). I've noticed something like this is already implemented for the body area (visualizer vbox layer). Or is there any option for this already? Thanks, Jan

1 0

Re: [NTG-context] Eliminating orpans in the Index
by Hans Hagen 29 Nov '13

29 Nov '13

On 11/26/2013 10:09 PM, Jan Tosovsky wrote: > On 2013-11-23 Jan Tosovsky wrote: >> >> in my two-column index there are several cases when the last >> entry in the given letter group overflows to the next column/page. >> In the extreme case it is just the last page reference. >> ... >> Additionaly, columns are not balanced properly in all cases. When the >> first is longer, it is not a big problem. But the opposite case >> looks weird. > > As the registers are rendered programatically, I cannot intervene into this > process. But can I influence it e.g. using 'processors' applied to > problematic index entries? > > Processors can be used for setting the font-weight or color of particular > entry. Can the same method used for manual setting of > 'keep-with-previous/next' ? I can think of a hack but it will always be for last minute work. 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 -----------------------------------------------------------------

2 1

bibliography - maybeyear
by Alan Braslau 29 Nov '13

29 Nov '13

Hello, Using \setuppublications [alternative=num] for example, should not append letters to the publication years when encountering multiple publications by the same author(s) per year. So, in the use of bibliographies, I have not understood how to control \maybeyear. In the bibl-xxx.tex files, it is defined as \def\maybeyear#1{#1} or \def\maybeyear#1{} as needed. Perhaps this is for mkii. In bibl-bib.mkiv, one has \appendtoks \doifelse{\bibtexpublicationsparameter\c!maybeyear}\v!off {\let\maybeyear\gobbleoneargument} {\let\maybeyear\firstofoneargument}% \to \everysetupbibtexlistplacement which seems to then use the keyword maybeyear. I guess that \setupbibtexpublications [maybeyear=off] in my source would turn off the appended letters, but this is not correct. I have tried many variants (\setuppublications, \setupbibtex). What am I misunderstanding? Or is this a bug? Alan

3 5

Re: [NTG-context] Palatino patch for the current ConTeXt version
by Hans Hagen 29 Nov '13

29 Nov '13

On 11/27/2013 9:16 PM, Jan Tosovsky wrote: > On 2013-11-27 Hans Hagen wrote: >> On 11/27/2013 12:40 AM, Jan Tosovsky wrote: >>> On 2013-11-17 Hans Hagen wrote: >>>> On 11/17/2013 12:23 PM, honyk wrote: >>>>> Hello Everyone, >>>>> >>>>> I am trying to fix a Palatino small caps issue using the procedure >>>>> explained here: >>>>> http://wiki.contextgarden.net/Palatino_Linotype_under_MKIV >>>>> >>>>> That fix seems to be obsolete nowadays and returning errors. >>>>> >>>> >>>> there are several ways to apply patches runtime, see *.lfg files >>>> (and also fonts-mkiv.pdf) >>> >>> 1) I've created a sample LFG file >>> 2) placed it into the folder where other LFG files are stored >>> 3) removed pala.tma and pala.tmc files from the cache >>> 4) triggered the generating >>> >>> My pala.lfg file seems to be ignored: >>> >>> return { >>> name = "pala", >>> comment = "Switching the small capped 'i' to a dotless variant >>> in Palatino Linotype.", >>> remapping = { >>> tounicode = true, >>> unicodes = { >>> ["i.sc"] = 983201, >>> }, >>> }, >>> } >> >> you have to load them ... see fonts-mkiv.pdf > > Thanks, I got it. Two next steps are required and one turned out as > redundant. > > 1) Create a sample LFG file > 2) Place it into the folder where other LFG files are stored > 3) NEW! Execute 'mtxrun --generate' command to include newly added LFG file > into a file database > 4) NEW! Specify a new font feature referencing to this goodie: > \definefontfeature[dotlessi][mode=base,goodies=pala,unicoding=yes] > \definefontfamily[mainface][rm][Palatino > Linotype][features={default,quality,dotlessi}] > 5) Trigger the generating > > It does something, but not what I need :-) > > My MWE: > \definefontfeature[dotlessi][mode=base,goodies=pala,unicoding=yes] > \definefontfamily[palatino][rm][Palatino > Linotype][features={default,quality,dotlessi}] > \setupbodyfont[palatino] > \starttext > Athenians \sc{Athenians} > \stoptext > > This LFG core settings: > unicodes = { > ["a.sc"] = 97, (1) > ["b.sc"] = 983261, (2) > }, > > (1) replaces all small 'a' into small caps variants - just for testing > purposes > (2) doesn't replace small caps 'i' to small caps 'b', but when small caps > text is selected, b is copied into the clipboard - so some replacement is > performed, but incomplete. > > Maybe other tables need to be tweaked as well... > Has anybody any experience with this? this mechanism assumes that the shapes match the one that unicode expects so the (default) tounicode is used ... originally this features was meant for fonts with a faulty mapping (some dingbat fonts have that) 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 -----------------------------------------------------------------

2 1

sagemath in context (like sagetex)
by Xan 29 Nov '13

29 Nov '13

Hi, Is there any kind of package for embedded sagemath in ConTeXt (like sagetex in latex). I found the same question previosly asked (http://www.ntg.nl/pipermail/ntg-context/2009/040483.html) but more things are changed until 2009... so perhaps there is now a solution By the other hand, I see lua lunatic code: http://wiki.contextgarden.net/User:Luigi.scarso/luatex_lunatic#SageMath but this is very programmer centric code, in my opinion. Is there any easy way to do that? I use MKIV Thanks, Xan.

1 0

Unexpected behaviour of enumeration in mkiv
by Thomas Möbius 28 Nov '13

28 Nov '13

Hi, please have a look at the minimal example at the bottom. I am typesetting theorems and lemmata which are numbered consecutively within chapters in a book. I used the same code for a document written in mkii, and I thought I could just reuse it in mkiv. Obviously, there is something I am missing. Question: How do I get the same output when compiling the following code with 'context' as when compiled with 'texexec'. When compiled with 'context', the chapter number is missing in the numbering of theorems. Lemmas are not numbered at all. ~~~snip~~~ \setupenumerations [title=yes, style=normal, list=all, before={\blank[big]}, after={\blank[big]}, location=serried, width=broad, distance=0.5em, headstyle=bold, titlestyle=bold, way=bychapter, conversion=numbers] \defineenumeration [theorem] [text=Theorem, listtext={Theorem }] \defineenumeration [lemma] [text=Lemma, listtext={Lemma }, number=theorem] \starttext \chapter{First chapter} \theorem Hello \theorem Hello \lemma Hello \theorem Hello \stoptext ~~~snip~~~

2 3

Line numbers and tabulate cells in Mark IV
by Adam Khan 28 Nov '13

28 Nov '13

The lines of a tabulate cell may be numbered with code like the following under Mark II, but not under Mark IV. \starttabulate[|p|p|] \NC \input knuth \NC \startlinenumbering \input knuth \stoplinenumbering \NC\NR \stoptabulate How may the lines of a tabulate cell be numbered under Mark IV? Sincerely yours, Adam Khan

2 2

Re: [NTG-context] [***SPAM***] Incorrect internal font processing
by Hans Hagen 28 Nov '13

28 Nov '13

On 11/27/2013 11:35 PM, Jan Tosovsky wrote: > On 2013-11-27 Jan Tosovsky wrote: >> On 2013-11-27 Hans Hagen wrote: >>> On 11/27/2013 10:20 PM, Jan Tosovsky wrote: >>>> On 2013-11-27 Hans Hagen wrote: >>>>> On 11/27/2013 9:53 PM, Jan Tosovsky wrote: >>>>>> On 2013-11-27 Hans Hagen wrote: >>>>>>> On 11/27/2013 8:44 PM, Jan Tosovsky wrote: >>>>>>>> >>>>>>>> during my attempts to patch the Palatino's dotless 'i' I found >>>>>>>> that this font is parsed incorrectly by ConTeXt. >>>>>>>> >>>>>>>> Comparing index/name info of individual glyphs in the font >>>>>>>> software and resulting pala.tma file there is the following >>>>>>>> difference: >>>>>>>> >>>>>>>> Index | Name - font | Name - tma >>>>>>>> 1110 | dotlessi.smcp | i.sc (1) >>>>>>>> 1170 | i.smcp | i.sc (2) >>>>>>>> >>>>>>>> The first one should have IMHO a different name. >>>>>>>> The same name for two glyphs might be dangerous. >>>>>>> >>> >>> the fact that there are two i.sc in the font is suspicious ... best >>> check the font in fontforge ... one never know what kind of things >>> other programs do >> >> Hmm, FontForge glyphs naming corresponds to what we can observe in the >> ConTeXt (doubled i.sc). My previous analysis was based on FontLab. I am >> confused now... > > Actually, there are no names of these glyphs available in the font so they > are calculated(!) > Each of two programs uses a different method. FontLab method is based on > layout tables - GPOS, GSUB, GDEF (it somehow detects that both glyps that is okay to make names unique, although there can still be multiple variants so in fact i.smcp and i.ss01.4 are valid names then, but .smcp and .onum are not understood by name parsers (for adobe glyph names) > differs). The FontForge method is unclear and seems to be buggy. But we some kind of numbering would make more sense i.1 or so > should blame rather the font itself as it is the primary cause of these > problems (= missing glyph names). indeed 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

Multi-letter variables in math mode
by Thaddäus Töppen 28 Nov '13

28 Nov '13

Hi. Sometimes I use variables (really rather abbreviations) in math formulas. It seems to me that the letterspacing is a bit too wide then. Maybe math mode thinks I want to multiply the letters as if they were variables for themselves. Is there a way to preserve normal letterspacing locally in a formula? Kind regards.

2 1

Re: [NTG-context] [***SPAM***] Incorrect internal font processing
by Jan Tosovsky 27 Nov '13

27 Nov '13

On 2013-11-27 Jan Tosovsky wrote: > On 2013-11-27 Hans Hagen wrote: > > On 11/27/2013 10:20 PM, Jan Tosovsky wrote: > > > On 2013-11-27 Hans Hagen wrote: > > >> On 11/27/2013 9:53 PM, Jan Tosovsky wrote: > > >>> On 2013-11-27 Hans Hagen wrote: > > >>>> On 11/27/2013 8:44 PM, Jan Tosovsky wrote: > > >>>>> > > >>>>> during my attempts to patch the Palatino's dotless 'i' I found > > >>>>> that this font is parsed incorrectly by ConTeXt. > > >>>>> > > >>>>> Comparing index/name info of individual glyphs in the font > > >>>>> software and resulting pala.tma file there is the following > > >>>>> difference: > > >>>>> > > >>>>> Index | Name - font | Name - tma > > >>>>> 1110 | dotlessi.smcp | i.sc (1) > > >>>>> 1170 | i.smcp | i.sc (2) > > >>>>> > > >>>>> The first one should have IMHO a different name. > > >>>>> The same name for two glyphs might be dangerous. > > >>>> > > > > the fact that there are two i.sc in the font is suspicious ... best > > check the font in fontforge ... one never know what kind of things > > other programs do > > Hmm, FontForge glyphs naming corresponds to what we can observe in the > ConTeXt (doubled i.sc). My previous analysis was based on FontLab. I am > confused now... Actually, there are no names of these glyphs available in the font so they are calculated(!) Each of two programs uses a different method. FontLab method is based on layout tables - GPOS, GSUB, GDEF (it somehow detects that both glyps differs). The FontForge method is unclear and seems to be buggy. But we should blame rather the font itself as it is the primary cause of these problems (= missing glyph names). Jan

1 0

Re: [NTG-context] [***SPAM***] Incorrect internal font processing
by Hans Hagen 27 Nov '13

27 Nov '13

On 11/27/2013 10:20 PM, Jan Tosovsky wrote: > On 2013-11-27 Hans Hagen wrote: >> On 11/27/2013 9:53 PM, Jan Tosovsky wrote: >>> On 2013-11-27 Hans Hagen wrote: >>>> On 11/27/2013 8:44 PM, Jan Tosovsky wrote: >>>>> >>>>> during my attempts to patch the Palatino's dotless 'i' I found that >>>>> this font is parsed incorrectly by ConTeXt. >>>>> >>>>> Comparing index/name info of individual glyphs in the font software >>>>> and resulting pala.tma file there is the following difference: >>>>> >>>>> Index | Name - font | Name - tma >>>>> 1110 | dotlessi.smcp | i.sc (1) >>>>> 1170 | i.smcp | i.sc (2) >>>>> >>>>> The first one should have IMHO a different name, e.g. dotlessi.sc >>>>> (to keep conventions). The same name for two glyphs >>>>> might be dangerous. >>>> >>>> the font pala.ttf has two entries i.sc and i see no reference to >>>> *.smcp >>> >>> There is no 'i.sc' glyph available according to the font software, >>> only those .smcp, listed in the smcp6 table. >>> >>> As there are only .sc names in the TMA file, I suppose there is some >>> kind of name normalization. But not very precise... >> >> mtxrun --script font --save pala.ttf > > I can confirm your observations. In this lua export there is no .smcp, but > doubled i.sc records. Strange. There must be really some kind of > normalization there... the fact that there are two i.sc in the font is suspicious ... best check the font in fontforge ... one never know what kind of things other programs do > It would be nice to review the corresponding part of the code as it is IMHO > potentially dangerous. afaik no magic there 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 -----------------------------------------------------------------

2 1

Re: [NTG-context] [***SPAM***] Incorrect internal font processing
by Hans Hagen 27 Nov '13

27 Nov '13

On 11/27/2013 9:53 PM, Jan Tosovsky wrote: > On 2013-11-27 Hans Hagen wrote: >> On 11/27/2013 8:44 PM, Jan Tosovsky wrote: >>> >>> during my attempts to patch the Palatino's dotless 'i' I found that >>> this font is parsed incorrectly by ConTeXt. >>> >>> Comparing index/name info of individual glyphs in the font software >>> and resulting pala.tma file there is the following difference: >>> >>> Index | Name - font | Name - tma >>> 1110 | dotlessi.smcp | i.sc (1) >>> 1170 | i.smcp | i.sc (2) >>> >>> (2) - this is a composite character which consist of dotlessi.smcp >>> and dot. >>> >>> The first one should have IMHO a different name, e.g. dotlessi.sc (to >>> keep conventions). The same name for two glyphs might be dangerous. >> >> the font pala.ttf has two entries i.sc and i see no reference to *.smcp > > The version of my Palatino is 5.0 (I run on Win7) > It is located at c:/windows/fonts/pala.ttf i checked on windows 8 > There is no 'i.sc' glyph available according to the font software, only > those .smcp, listed in the smcp6 table. > > As there are only .sc names in the TMA file, I suppose there is some kind of > name normalization. But not very precise... > >> (mtxrun --script --save pala.ttf) mtxrun --script font --save pala.ttf > This returns an error: > c:/windows/fonts/pala.ttf:1: unexpected symbol > > Jan > > ___________________________________________________________________________________ > If your question is of interest to others as well, please add an entry to the Wiki! > > maillist : ntg-context(a)ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context > webpage : http://www.pragma-ade.nl / http://tex.aanhet.net > archive : http://foundry.supelec.fr/projects/contextrev/ > wiki : http://contextgarden.net > ___________________________________________________________________________________ > -- ----------------------------------------------------------------- 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 -----------------------------------------------------------------

2 1

Re: [NTG-context] [
by Lars Huttar 27 Nov '13

27 Nov '13

In a thread from July (http://context.markmail.org/thread/6tgzusw45whaqghi) Marco Patzer raised some questions that we have too. They were somewhat answered, but I'm still not clear on what the meanings of the keywords are. On Jul 8, 2013 4:08:33 pm Hans wrote: > On 7/9/2013 12:30 AM, Marco Patzer wrote: > >/ On 2013–07–08 Hans Hagen wrote: > />/ > />>>/ I expect the markings on the left and right to be the same and show > />>>/ A–C on the first page and D–E on the second one. Looks like a bug to > />>>/ me. > />>/ > />>/ use top and bottom > />/ > />/ This works. Thanks. > />/ > />>/ -- previous : last before sync > />>/ -- next : first after sync > />>/ > />>/ -- top : first in sync > />>/ -- bottom : last in sync > />>/ > />>/ -- first : first not top in sync > />>/ -- last : last not bottom in sync > />/ > />/ That is exactly what's in the wiki (Command/getmarking). To my > />/ defence: The manual (chapter 12.4) is outdated, it lists: > />/ > />/ previous - the last of the previous page > />/ first - the first of the actual page > />/ last - the last of the actual page > />/ both - first — last > />/ all - previous — first — last > />/ > />/ I have no idea what “first not top in sync” means, in contrast to > />/ “first of the actual page”, which is quite clear but wrong on a > />/ current MkIV. > / > old tex terminology ... in mkiv i don't use the build-in-tex marks at > all (too much juggling needed to get things right) So I'm wondering ... Hans, since the descriptions you posted are old tex terminology, what do previous/next/top/bottom/first/last/etc. mean in current terminology? I agree with Marco that the descriptions in the ref manual are much easier to understand, but appear to be wrong; and do not include top/bottom. I'll be happy to update the ref manual and the wiki if I can get clear and accurate information. We have run many examples here, including the ones on the getmarking wiki page, trying to understand what these keywords mean. top/bottom do appear to do what we need in an MWE, but are not working for us in the real document, and knowing the meaning of these keywords would be very helpful in troubleshooting the problem. Thanks, Lars

2 8

Re: [NTG-context] [***SPAM***] Incorrect internal font processing
by Hans Hagen 27 Nov '13

27 Nov '13

On 11/27/2013 8:44 PM, Jan Tosovsky wrote: > Dear All, > > during my attempts to patch the Palatino's dotless 'i' I found that this > font is parsed incorrectly by ConTeXt. > > Comparing index/name info of individual glyphs in the font software and > resulting pala.tma file there is the following difference: > > Index | Name - font | Name - tma > 1110 | dotlessi.smcp | i.sc (1) > 1170 | i.smcp | i.sc (2) > > (2) - this is a composite character which consist of dotlessi.smcp and dot. > > The first one should have IMHO a different name, e.g. dotlessi.sc (to keep > conventions). The same name for two glyphs might be dangerous. the font pala.ttf has two entries i.sc and i see no reference to *.smcp (mtxrun --script --save pala.ttf) naming of glyphs is somewhat fuzzy and not always consistentent in fonts but i fear there is not much we can do here (apart from using palatino nova instead) 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 -----------------------------------------------------------------

2 1

Re: [NTG-context] Palatino patch for the current ConTeXt version
by Hans Hagen 27 Nov '13

27 Nov '13

On 11/27/2013 12:40 AM, Jan Tosovsky wrote: > On 2013-11-17 Hans Hagen wrote: >> On 11/17/2013 12:23 PM, honyk wrote: >>> Hello Everyone, >>> >>> I am trying to fix a Palatino small caps issue using the procedure >>> explained here: >>> http://wiki.contextgarden.net/Palatino_Linotype_under_MKIV >>> >>> That fix seems to be obsolete nowadays and returning errors. >>> >> >> there are several ways to apply patches runtime, see *.lfg files (and >> also fonts-mkiv.pdf) > > 1) I've created a sample LFG file > 2) placed it into the folder where other LFG files are stored > 3) removed pala.tma and pala.tmc files from the cache > 4) triggered the generating > > My pala.lfg file seems to be ignored: > > return { > name = "pala", > comment = "Switching the small capped 'i' to a dotless variant in > Palatino Linotype.", > remapping = { > tounicode = true, > unicodes = { > ["i.sc"] = 983201, > }, > }, > } > > 1) How the LFG file is matched with the font? Is it via the 'name' > parameter, "pala" in my case? Does that name equals to the file title > without an extension or something else? > > 2) Should I see that comment in the log or is it just a remark for editors? > > 3) Can I emulate this patch via direct editing of pala.tma file? When I > change the 'unicodes' value there, it has no impact on generating (nothing > changes in the output). you have to load them ... see fonts-mkiv.pdf ----------------------------------------------------------------- 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 -----------------------------------------------------------------

2 1

[***SPAM***] Incorrect internal font processing
by Jan Tosovsky 27 Nov '13

27 Nov '13

Dear All, during my attempts to patch the Palatino's dotless 'i' I found that this font is parsed incorrectly by ConTeXt. Comparing index/name info of individual glyphs in the font software and resulting pala.tma file there is the following difference: Index | Name - font | Name - tma 1110 | dotlessi.smcp | i.sc (1) 1170 | i.smcp | i.sc (2) (2) - this is a composite character which consist of dotlessi.smcp and dot. The first one should have IMHO a different name, e.g. dotlessi.sc (to keep conventions). The same name for two glyphs might be dangerous. Regards, Jan

1 0

ctxluacode inside bTABLE
by DesdeChaves 27 Nov '13

27 Nov '13

I try make a table with some random numbers but I found a problem with this code: \starttext \ctxluacode{v=math.random(400,600)/10;context("%0.1f",v) ;} \bTABLE \bTR\bTD Distance (cm) \eTD\bTD $\Delta t$ (s) \eTD\eTR \bTR\bTD[nr=3] \ctxluacode{v=math.random(400,600)/10;context("%0.1f",v) ;} \eTD\bTD t1 \eTD\eTR \bTR\bTD t2 \eTD\eTR \bTR\bTD t3 \eTD\eTR \eTABLE \stoptext \ctxluacode{v=math.random(400,600)/10;context("%0.1f",v) ;} don't work inside the bTABLE environment. Thanks in advance. Jorge

2 4

Re: [NTG-context] Palatino patch for the current ConTeXt version
by Hans Hagen 27 Nov '13

27 Nov '13

On 11/17/2013 12:23 PM, honyk wrote: > Hello Everyone, > > I am trying to fix a Palatino small caps issue using the procedure explained > here: > http://wiki.contextgarden.net/Palatino_Linotype_under_MKIV > > That fix seems to be obsolete nowadays and returning errors. > > I've changed > fonts.otf.enhancers.patches["^pala"] > to > fonts.handlers.otf.enhancers.patches["^pala"] > which compiles, but it does nothing. > > I've also tried this variant, but that 'patch' function is never called even > though I clear my font cache every run: > > \startluacode > local fonts = fonts > local otf = fonts.handlers.otf > local patches = otf.enhancers.patches > local register = patches.register > local report = patches.report > > function patch (data,filename) > report("I am here") > report("processing data %s", table.serialize(data)) > end > > register("after","prepare glyphs","^pala", patch) > \stopluacode > > > Any idea? patches are applied when a font is cached so you need to wipe the cache after defining such a patch there are several ways to apply patches runtime, see *.lfg files (and also fonts-mkiv.pdf) 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 -----------------------------------------------------------------

2 1

Re: [NTG-context] PDF bookmarks - incorrect titles for registers
by Hans Hagen 26 Nov '13

26 Nov '13

On 11/26/2013 8:03 PM, Jan Tosovsky wrote: > On 2013-11-18 Jan Tosovsky wrote: >> >> when I specify custom titles for my registers, they are ignored in >> bookmarks: >> >> \setupinteraction[state=start] >> \placebookmarks[chapter] >> \setupinteractionscreen[option=bookmark] >> >> \defineregister[indexname][indexnames] >> \defineregister[indexsubject][indexsubjects] >> \setupheadtext[indexname=Name Index] >> \setupheadtext[indexsubject=Subject Index] >> >> \starttext >> \completecontent >> \chapter{Chapter}text\indexname{primary}\indexsubject{primary} >> \startbackmatter >> \completeindexname >> \completeindexsubject >> \stopbackmatter >> \stoptext >> >> Is it necessary to switch something else on? > > According to the proposed solution at > http://tracker.luatex.org/view.php?id=865 > > it can be switched on using this magic formula > \enabledirectives[references.bookmarks.preroll] > > What is the correct usage of this? And are there any details why it is > required and what exactly it does? by default the title is set to a label which is not expandable the directive will convert the typeset title into a bookmark > When it is added to the beginning of my example, it returns an error: > attempt to call field 'boxtostring' (a nil value) ah, only in my experimental tree, i'll add it to the beta > But to be honest, I'd expect setting this flag internally by default as I > cannot imagine any use case where the index ID should be preferred in favor > of the title... as titles can be anything and bookmarks are limited, we need to have some protection in place ... unexpandable macros are simply dropped so \labeltext{index} becomes index 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 -----------------------------------------------------------------

2 2

Re: [NTG-context] PDF bookmarks - incorrect titles for registers
by Hans Hagen 26 Nov '13

26 Nov '13

On 11/26/2013 8:30 PM, Jan Tosovsky wrote: > Thanks for this detailed explanation. If I understand correctly, this switch > is intentional and won't be applied automatically even for registers or > other peculiar cases where title is specified differently/unexpectedly. the bookmark setting defaults to the title itself but you can always set a bookmark title explicitly with bookmark= >>> When it is added to the beginning of my example, it returns an error: >>> attempt to call field 'boxtostring' (a nil value) >> >> ah, only in my experimental tree, i'll add it to the beta > > Thanks, but this one is not so urgent. 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

Re: [NTG-context] Eliminating orpans in the Index
by Jan Tosovsky 26 Nov '13

26 Nov '13

On 2013-11-23 Jan Tosovsky wrote: > > in my two-column index there are several cases when the last > entry in the given letter group overflows to the next column/page. > In the extreme case it is just the last page reference. > ... > Additionaly, columns are not balanced properly in all cases. When the > first is longer, it is not a big problem. But the opposite case > looks weird. As the registers are rendered programatically, I cannot intervene into this process. But can I influence it e.g. using 'processors' applied to problematic index entries? Processors can be used for setting the font-weight or color of particular entry. Can the same method used for manual setting of 'keep-with-previous/next' ? Thanks, Jan

1 0

Re: [NTG-context] PDF bookmarks - incorrect titles for registers
by Jan Tosovsky 26 Nov '13

26 Nov '13

On 2013-11-18 Jan Tosovsky wrote: > > when I specify custom titles for my registers, they are ignored in > bookmarks: > > \setupinteraction[state=start] > \placebookmarks[chapter] > \setupinteractionscreen[option=bookmark] > > \defineregister[indexname][indexnames] > \defineregister[indexsubject][indexsubjects] > \setupheadtext[indexname=Name Index] > \setupheadtext[indexsubject=Subject Index] > > \starttext > \completecontent > \chapter{Chapter}text\indexname{primary}\indexsubject{primary} > \startbackmatter > \completeindexname > \completeindexsubject > \stopbackmatter > \stoptext > > Is it necessary to switch something else on? According to the proposed solution at http://tracker.luatex.org/view.php?id=865 it can be switched on using this magic formula \enabledirectives[references.bookmarks.preroll] What is the correct usage of this? And are there any details why it is required and what exactly it does? When it is added to the beginning of my example, it returns an error: attempt to call field 'boxtostring' (a nil value) But to be honest, I'd expect setting this flag internally by default as I cannot imagine any use case where the index ID should be preferred in favor of the title... Jan

1 0

Automatic adjusting the font size to fill the text-area
by "H. Özoguz" 26 Nov '13

26 Nov '13

Hello there, in my actual book there is one special condition: It is already clear which paragraphs of the text have to be set on page 1, which on page 2 etc.pp. (a nearly 700 pages-project). So there are no page-breaks within a paragraph, no overruns are allowed. But now the question: The text for each page has not always the same length. So on some pages there might be many empty space at the buttom, while on others the textarea is completely filled. At the beginning I have to set an font-size - so I have to set it, such that the longest text fits into the text area on its page. But of course, many other pages maye filled only 60%. (That is the spectrum of the text-lengths in this project). So one direct solution is clear (if one wants to have filled or nearly-filled pages, and I want this): I can change the font-size for every single page. But which size? It is a experiment, so I have to try 10pt, then compile, then 10.8pt .... ok, was too much, got an page-overrun .... lets try 10.4pt ..... and this for every single of the 700 pages. That is possible of course, and if there is no other way, this will be my approach. So: Is there some trick or way for automatically find the best (biggest) font-size (up to some precision, maybe one digit after decimal point in pt), s.t. the text produces no overrun (no page-brake)? I guess no, because ConTeXt had to run the compiling several times or so ... but better to ask and then to begin with the exhausting work. Thanks. Huseyin

1 0

Re: [NTG-context] Calculating with variables
by "H. Özoguz" 26 Nov '13

26 Nov '13

> which is why the next is better: > > \definemeasure[fontsize:big] [17pt] > \definemeasure[fontsize:small][0.7\measured{fontsize:big}] > > \definefont[big] [name:arial at \measure{fontsize:big}] > \definefont[small][name:arial at \measure{fontsize:small}] > > \starttext > \big Dies ist ein großer Text. \blank > \small Dies ist ein kleiner Text. > \stoptext > > Best wikify this! > > Alternatively you can set up symbolic sizes (like we already have a b c > d), so that > > \definefont[big] [name:arial sa a] > > etc can be used > > Hans Thank you! I will wikify it, hopefully in the next days. Huseyin

1 0

Calculating with variables
by "H. Özoguz" 26 Nov '13

26 Nov '13

Hello there, I am new in variables in ConTeXt, so I tried the the following example of two font-sizes wich should have a ratio of 0.7: \setvariables[fontsize][bigsize=17pt] \setvariables[fontsize][smallsize=0.7\getvariable{fontsize}{size}] \definefont[big][name:arial at \getvariable{fontsize}{bigsize}] \definefont[small][name:arial at \getvariable{fontsize}{smallsize}] \starttext \big Dies ist ein großer Text.\blank \small Dies ist ein kleiner Text. \stoptext That does not work, what is the correct syntax? [Second question about this will be much more involving I think ... :), but I will give it his own thread]. Thanks. Huseyin

2 1

Re: [NTG-context] Converting normal font into bold
by "H. Özoguz" 26 Nov '13

26 Nov '13

> > >>/ May be ConTeXt experts would have better suggestions, till then you > />>/ may want to look at the fake bold option in simplefonts - > />>/ http://wiki.contextgarden.net/Simplefonts#Faking_italics_and_bold_fonts > />/ > />/ Thanks for your advice. > />/ Unfortunately I did not manish to work with this font by simplefonts. I use the following simple setup: > />/ > />/ > />/ \definefont[arabic][file:bliblablup_0.ttf*arabic at 15pt] > / > \definefontfeature[fakebold][extend=1.1] > > \definefont[arabic][file:<fontname>*arabic,fakebold at 15pt] > > >/ \starttext > />/ \arabic\setupalign[r2l] ??????? ??? ???????? ?????? ???? ???????? ??????????? > />/ \stoptext > />/ > />/ How can I get these "fake bolds" with this setup? Or is it absolutely necessary to use Simplefont for these fake-bolds? > / > The feature is unrelated to simplefonts. > > Wolfgang Thanks Wolfgang, but that does not seem to work with this font. See attachment, the font is wider, but not bold. See the difference to the intended result, achieved with Corel Draw (with the same font), see attachment. In ConTeXt I had the following code (see attachment for the compiled pdf): ++++++++++++++++ \definefont[arabic][file:bliblablup_0.ttf*arabic at 15pt] \definefont[arabics][file:bliblablup_0.ttf*arabic at 15pt] \definefontfeature[fakebold][extend=1.2] \definefont[arabic][file:bliblablup_0.ttf*arabic,fakebold at 15pt] \starttext \arabic\setupalign[r2l] ??????? ??? ???????? ?????? ???? ???????? ??????????? \blank\arabics\setupalign[r2l] ??????? ??? ???????? ?????? ???? ???????? ??????????? \stoptext ++++++++++++++++ Huseyin

2 1

pstrics module again
by DesdeChaves 26 Nov '13

26 Nov '13

Dear sirs The pstrics module don't work anymore. I tried to run this simple code but I found a lot of errors. \usemodule[pstric] \starttext \startPSTRICKS \pspicture(0,0)(20,20) \psline(0,0)(20,20) \psline(1,1)(10,10) \endpspicture \stopPSTRICKS \stoptext This module is no longer supported? There is still any hope of being able to use pstric and some of its extensions (pst-spectra, for example)? Thanks a lot Sorry for my persistence about pstrics module. Thanks a lot Jorge

3 9

Re: [NTG-context] ToC - right-alignment of roman numerals
by Hans Hagen 25 Nov '13

25 Nov '13

On 11/24/2013 10:49 PM, Jan Tosovsky wrote: > On 2013-11-18 Jan Tosovsky wrote: >>> On 2013–06–03 Jan Tosovsky wrote: >>> in fresh MkIV I use the following commands for building ToC, but I >>> have no idea how to align the label (roman numeral) to the right. >> >> I am almost there, but things get complicated when chapters are >> combined with preface/index titles without numbering and thus aligned >> improperly: >> >> \setupcombinedlist[content][list=chapter, alternative=c] >> \setupcombinedlist[chapter][ >> distance=1em, >> width=1cm, >> >> numbercommand={\simplealignedbox{\listparameter{width}}{flushright}}, >> ] >> >> \starttext >> \completecontent >> >> \startfrontmatter >> \chapter{Preface}text >> \stopfrontmatter >> >> \startbodymatter >> \chapter{Chapter}text\index{primary} >> \stopbodymatter >> >> \startbackmatter >> \completeindex >> \stopbackmatter >> >> \stoptext >> >> Is there any way how to indent these non-numbered titles so that they >> start where the chapter title starts? > > I've fixed it by applying a margin to everything and setting a negative width to the numbers (distance = -width): > > \setupcombinedlist[chapter][ > distance=0.5cm, > width=-0.5cm, > margin=2cm, > numbercommand={\simplealignedbox{\listparameter{width}}{flushright}}, > ] > > I don't know exactly why it works, but it works :-) > \setupcombinedlist [content] [list=chapter, alternative=c] \setuplist [chapter] [aligntitle=yes, distance=1em, width=1cm] ----------------------------------------------------------------- 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 -----------------------------------------------------------------

2 1

Re: [NTG-context] Intermediate format
by Aditya Mahajan 25 Nov '13

25 Nov '13

On Mon, 25 Nov 2013, Jan Tosovsky wrote: > On 2013-11-25 Aditya Mahajan wrote: >>>> On 11/24/2013 8:32 PM, Jan Tosovsky wrote: >>>>> >>>>> is it possible to get the complete representation of the layout >>>>> that is processed in the luatex PDF generator? >>>>> >>>>> I mean coordinations of individual text boxes, their dimensions >>>>> etc. >>>>> >>>>> Actually, I'd like to retrieve the page number and vertical >>>>> position of my object with a specific id (reference) to be able >>>>> to perform PDF post-processing. >>>> >> >> \setposition{id} >> \message{id:\MPp{id};\MPy{id};\MPx{id}} >> >> should work (untested). Then you can parse the log file. > > This is coool! > > Is there any documentation to all this stuff? I cannot find anything in Wiki > or User Guide... Not really. See http://tex.stackexchange.com/a/125486/323 (and its edit history) to see a usage of some more of these features. Aditya

1 0

Re: [NTG-context] Intermediate format
by Hans Hagen 25 Nov '13

25 Nov '13

On 11/25/2013 9:54 PM, Jan Tosovsky wrote: > On 2013-11-25 Aditya Mahajan wrote: >>>> On 11/24/2013 8:32 PM, Jan Tosovsky wrote: >>>>> >>>>> is it possible to get the complete representation of the layout >>>>> that is processed in the luatex PDF generator? >>>>> >>>>> I mean coordinations of individual text boxes, their dimensions >>>>> etc. >>>>> >>>>> Actually, I'd like to retrieve the page number and vertical >>>>> position of my object with a specific id (reference) to be able >>>>> to perform PDF post-processing. >>>> >> >> \setposition{id} >> \message{id:\MPp{id};\MPy{id};\MPx{id}} >> >> should work (untested). Then you can parse the log file. > > This is coool! > > Is there any documentation to all this stuff? I cannot find anything in Wiki > or User Guide... probably all over the place, but the metafun manual is one of them ----------------------------------------------------------------- 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

large delimiters for equation
by Roger Mason 25 Nov '13

25 Nov '13

Hello, I'd like to have delimiters that match the height of the fraction in an expression like this: \startformula c\Delta T = t\big{(} \frac{c}{v_s} - \frac{c}{v_f} \big{)}. \stopformula I looked in the docs and tried a few likely solutions without luck. Please accept my apologies if this is documented eleswhere. Thanks, Roger

2 2

Re: [NTG-context] Converting (a not so) normal font into bold
by "H. Özoguz" 25 Nov '13

25 Nov '13

> test code: > > \starttext > > \showotfcomposition{file:uthmanichafs1ver09.ttf*arabic}{r2l}{١} \page > \showotfcomposition{file:uthmanichafs1ver09.ttf*arabic}{r2l}{١ ١} \page > \showotfcomposition{file:uthmanichafs1ver09.ttf*arabic}{r2l}{١١} \page > > % \usemodule[fonts-coverage] > % \showfontcomparison[list=file:uthmanichafs1ver09.ttf] > > \stoptext Thank you very much, Hans! Now all issues with this font are solved (new issues within my actual project will surely follow, but no font-issues, I hope). I have to say once more, that I never had experienced before a such fast and competent software-support, that is at least as valuable as the software itself is! To your comments: Ok, yes, it is not a really normal font. It is specially designed for typesetting the holy quran (which is really no easy work). And there is so absolutely no problem that ALL numbers are mapped to ligatures -> there are no digits in the text of the holy quran :) (all numbers are written out at that time). Thanks again! Huseyin

1 0

Re: [NTG-context] Intermediate format
by Aditya Mahajan 25 Nov '13

25 Nov '13

On Mon, 25 Nov 2013, Jan Tosovsky wrote: > On 2013-11-25 Hans Hagen wrote: >> On 11/24/2013 8:32 PM, Jan Tosovsky wrote: >>> >>> is it possible to get the complete representation of the layout that >>> is processed in the luatex PDF generator? >>> >>> I mean coordinations of individual text boxes, their dimensions etc. >>> >>> Actually, I'd like to retrieve the page number and vertical position >>> of my object with a specific id (reference) to be able to perform PDF >>> post-processing. >> >> \starttext >> >> we are here: \setposition{crap}(\MPx{crap},\MPy{crap}) >> >> \stoptext > > Thanks! Looks promising, Actually I'd like to print it into a log or > somewhere else, not into the document itself. But I need also the page > number. Every record should be ideally in the form: ID;page-number;Y-coord. \setposition{id} \message{id:\MPp{id};\MPy{id};\MPx{id}} should work (untested). Then you can parse the log file. Aditya

2 1

Re: [NTG-context] Intermediate format
by Hans Hagen 25 Nov '13

25 Nov '13

On 11/25/2013 9:07 PM, Jan Tosovsky wrote: > On 2013-11-25 Hans Hagen wrote: >> On 11/24/2013 8:32 PM, Jan Tosovsky wrote: >>> >>> is it possible to get the complete representation of the layout that >>> is processed in the luatex PDF generator? >>> >>> I mean coordinations of individual text boxes, their dimensions etc. >>> >>> Actually, I'd like to retrieve the page number and vertical position >>> of my object with a specific id (reference) to be able to perform PDF >>> post-processing. >> >> \starttext >> >> we are here: \setposition{crap}(\MPx{crap},\MPy{crap}) >> >> \stoptext > > Thanks! Looks promising, Actually I'd like to print it into a log or > somewhere else, not into the document itself. But I need also the page > number. Every record should be ideally in the form: ID;page-number;Y-coord. > >>> Is DVI way to go? How can I get it in MkIV? > > I've found that luatex can optionally output DVI [1], but I cannot find any > ConTeXt commandline switch to change the output format from PDF to something > else... indeed, no dvi ... it doesn't pay off to spend time on making all backend functionality multi-mode 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

Re: [NTG-context] Intermediate format
by Hans Hagen 25 Nov '13

25 Nov '13

On 11/24/2013 8:32 PM, Jan Tosovsky wrote: > Dear All, > > is it possible to get the complete representation of the layout that is > processed in the luatex PDF generator? > > I mean coordinations of individual text boxes, their dimensions etc. > > In e.g. XSL-FO processors it is provided in the XML based formats: > > http://www.renderx.com/reference.html#IntermediateFormatSpecification > http://xmlgraphics.apache.org/fop/1.1/intermediate.html > > Actually, I'd like to retrieve the page number and vertical position of my > object with a specific id (reference) to be able to perform PDF > post-processing. > > Is DVI way to go? How can I get it in MkIV? old feature ... \starttext we are here: \setposition{crap}(\MPx{crap},\MPy{crap}) \stoptext ----------------------------------------------------------------- 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 -----------------------------------------------------------------

2 1

Re: [NTG-context] Converting normal font into bold
by "H. Özoguz" 25 Nov '13

25 Nov '13

> i tried to reproduce your issue but gave up because of the fact that > it's unclear what (version) of the font is used ... you switched from 10 > to 09 and in 09 i see no 'big circular thing' so your version is > different from the one i donwload ... so, i cannot even be certain that > the font is okay ... so if you want to test: > > - make sure that you use fonts consistently > - make sure we know where to get that version of the font > - make sure that corel draw (or whatever) is using the same font You are right, sorry to annoy you here, some chaos in my place ... So, to clear all questions: for this min-example (which is at the moment my last unsolved problem with this font) I used this font: http://fonts.qurancomplex.gov.sa/download/UthmanicHafs1Ver09Font.zip And yes, Corel Draw uses this font, too. BUT: There might me some issue with this font relating this end-of-aya-symbol, independent from ConTeXt. See the attached JPG, which is the output of CorelDraw, if I input exactly the same arabic code, like in my example. You see in the picture a different behaviour between the one-digit and two-digit numbers aswell. But it is a different behaviour from ConText, the symbol is used, but the brackets are not replaced. Can you reproduce it now? Thanks! Huseyin

2 2

Re: [NTG-context] Converting normal font into bold
by "H. Özoguz" 25 Nov '13

25 Nov '13

> It is my believe that Unicode has the wrong properties for Arabic > standalone Hamza; in short you should just type a regular Hamza in the > middle of the word and it will get positioned correctly. Placing a > combining Hamza over a Tatweel to “fake” it is wrong IMO. So in Amiri > you just type “بِءَايَٰتِ” and voilà, every thing is rendered correctly (the > same is true for the small Alef). Yes, that works. But the direct way works with Uhtmanic1HafsVer9: \definefont[arabicamiri][file:amiri-regular.ttf*arabic at 15pt] \definefont[arabicuth][file:UthmanicHafs1Ver09.ttf*arabic at 17pt] \starttext \setupalign[r2l] \arabicamiri بِـَٔايَـٰتِ \blank \arabicuth بِـَٔايَـٰتِ \stoptext To be honest, in Corel Draw UthmanicHafs is the perfect font for my purpose - at least in CorelDraw - e.g.: The ayat-numbers are printed as a unicode-symbol, not as numbers (perfect, because ConTeXt has problems with the direction with arabic numbers, they are mirrored in ConTeXt). But it is only perfect in CorelDraw, in ConTeXt some things are not recognized correctly, as I mentioned. E.g. this one: \definefont[arabicamiri][file:amiri-regular.ttf*arabic at 15pt] \definefont[arabicuth][file:UthmanicHafs1Ver09.ttf*arabic at 17pt] \starttext \setupalign[r2l] \arabicuth لِّلْمُتَّقِينَ ﴿٢﴾ \stoptext If I put the same arabic into CorelDraw, it prints a nice Unicode-Symbol for the number - see the JPG I have attached here, screenshot from CorelDraw, but ConTeXt ignores the brackets and prints just a verys small number. There are some problems like this. Are they easy to fix, or is this problem deeply involved? Huseyin

3 2

Re: [NTG-context] Converting normal font into bold
by "H. Özoguz" 25 Nov '13

25 Nov '13

Hi Ondra, thanks for your help. > Apparently, replacing a number enclosed in ornate parentheses (U+FD3E > and U+FD3F) with a number in the "end of ayah" ornament is a specialty > of the UthmanicHafs font. If I input the digit (e.g. U+0662) and then > the special non-printable "end of ayah" character (U+06DD), ConTeXt > and Amiri successfully output the digit inside the ornament. Hmm, ok. But if it is a speciality of UthmanicHafs, why CorelDraw understands it natively? > Of course, since U+06DD is a non-printable character, it might be a > pain to work with in a text editor; you might want to define a custom > command for this purpose: > > \def\eoa#1{#1\char"06DD} Thanks, that works fine: \definefont[arabicamiri][file:amiri-regular.ttf*arabic at 15pt] \definefont[arabicuth][file:UthmanicHafs1Ver09.ttf*arabic at 17pt] \def\eoa#1{#1\char"06DD} \starttext \setupalign[r2l] \arabicuth لأَفَبِهَـٰذَا ٱلْحَدِيثِ أَنتُم مُّدْهِنُونَ ﴿٨١﴾\eoa \stoptext But now another question arises: How to input this command into my unicode of quran automatically? (I am using notepad++). Not the best way to do this manually for all 286 Ayas (and then search and replace for all ayas of all suras). And still: There must be some tricks in CorelDraw handling fonts, which would be great to have in ConText :) Thank you! Huseyin PS: Sorry for these annoyong thread-breaking all the time - I really do not know, what I make wrong here. I am using Thunderbird. If anybody knows how to use thunderbird for email lists correctly, I would be thankful.

2 1

Re: [NTG-context] Converting normal font into bold
by "H. Özoguz" 25 Nov '13

25 Nov '13

> Thanks, that works fine: > > \definefont[arabicamiri][file:amiri-regular.ttf*arabic at 15pt] > \definefont[arabicuth][file:UthmanicHafs1Ver09.ttf*arabic at 17pt] > \def\eoa#1{#1\char"06DD} > \starttext > \setupalign[r2l] > \arabicuth لأَفَبِهَـٰذَا ٱلْحَدِيثِ أَنتُم مُّدْهِنُونَ ﴿٨١﴾\eoa > \stoptext Now I could locate the error in ConText better, see this code and the mistake, which occurs: \definefont[arabicuth][file:UthmanicHafs1Ver09.ttf*arabic at 17pt] \define[1]\eoa{#1\char"06DD} \starttext \setupalign[r2l] \arabicuth إِنَّ ٱلَّذِينَ كَفَرُوا سَوَآءٌ عَلَيْهِمْ ءَأَنذَرْتَهُمْ أَمْ لَمْ تُنذِرْهُمْ لَا يُؤْمِنُونَ ﴿٦﴾\blank إِنَّ ٱلَّذِينَ كَفَرُوا سَوَآءٌ عَلَيْهِمْ ءَأَنذَرْتَهُمْ أَمْ لَمْ تُنذِرْهُمْ لَا يُؤْمِنُونَ ﴿٦٦﴾ \stoptext (I have attached the compiled PDF). The first aya, with a single one-digit number is not regonized correctly, but the second is (with a two-digit-number). Why? Huseyin

2 1

Re: [NTG-context] ToC - right-alignment of roman numerals
by Jan Tosovsky 24 Nov '13

24 Nov '13

On 2013-11-18 Jan Tosovsky wrote: > > On 2013–06–03 Jan Tosovsky wrote: > > in fresh MkIV I use the following commands for building ToC, but I > > have no idea how to align the label (roman numeral) to the right. > > I am almost there, but things get complicated when chapters are > combined with preface/index titles without numbering and thus aligned > improperly: > > \setupcombinedlist[content][list=chapter, alternative=c] > \setupcombinedlist[chapter][ > distance=1em, > width=1cm, > > numbercommand={\simplealignedbox{\listparameter{width}}{flushright}}, > ] > > \starttext > \completecontent > > \startfrontmatter > \chapter{Preface}text > \stopfrontmatter > > \startbodymatter > \chapter{Chapter}text\index{primary} > \stopbodymatter > > \startbackmatter > \completeindex > \stopbackmatter > > \stoptext > > Is there any way how to indent these non-numbered titles so that they > start where the chapter title starts? I've fixed it by applying a margin to everything and setting a negative width to the numbers (distance = -width): \setupcombinedlist[chapter][ distance=0.5cm, width=-0.5cm, margin=2cm, numbercommand={\simplealignedbox{\listparameter{width}}{flushright}}, ] I don't know exactly why it works, but it works :-) Jan

1 0

Re: [NTG-context] Converting normal font into bold
by "H. Özoguz" 24 Nov '13

24 Nov '13

Again, because arabic seems to be vanished in my first posting, I dont know why. Thanks Khaled, the Naskh-Style is not an absolute requirement, but it is very well known and very common (at least for muslims in germany) - and it is very nice, of course, this is an question of flavor. I know your font, of course, but I had always problems with it in typesetting quran. Maybe you can help? See the following code: \definefont[arabicamiri][file:amiri-regular.ttf*arabic at 15pt] \definefont[arabicb][file:uthmantn1ver10.ttf*arabic at 17pt] \starttext \setupalign[r2l] \arabicamiri مِن قَبْلُ هُدًى لِّلنَّاسِ وَأَنزَلَ ٱلْفُرْقَانَ ۗ إِنَّ ٱلَّذِينَ كَفَرُوا۟ بِـَٔايَـٰتِ ٱللَّهِ لَهُمْ عَذَابٌ شَدِيدٌ ۗ وَٱللَّهُ عَزِيزٌ ذُو ٱنتِقَامٍ \blank\blank \arabicb مِن قَبْلُ هُدًى لِّلنَّاسِ وَأَنزَلَ ٱلْفُرْقَانَ ۗ إِنَّ ٱلَّذِينَ كَفَرُوا۟ بِـَٔايَـٰتِ ٱللَّهِ لَهُمْ عَذَابٌ شَدِيدٌ ۗ وَٱللَّهُ عَزِيزٌ ذُو ٱنتِقَامٍ\par \stoptext There are some issues within this example: - overlapping letters (see "Aziyz") - "bi ayaatillah" (overlapping of fatha and hamza) And besides from that: It is not so harmonic like the other font, seems more like a not-caligraphic hand-font (no offense of course :)) But possibly I am making something very wrong, can you help me? Thank you very much. My project is to typesetting quran completely, and that is not easy without an perfect font. If you have a commercial variant with license, please inform me, our company would surely buy it. Thanks and wassalam

2 1

[***SPAM***] Re: Converting normal font into bold
by "H. Özoguz" 24 Nov '13

24 Nov '13

> http://amirifont.org/ > > >/ - and more hard to find such a find in this style (Uthmanic). > / > There is no such a style, it is just a simplified (dumbed down) Naskh > style used only in one single Mushaf. Why is that a requirement? Thanks Khaled, the Naskh-Style is not an absolute requirement, but it is very well known and very common (at least for muslims in germany) - and it is very nice, of course, this is an question of flavor. I know your font, of course, but I had always problems with it in typesetting quran. Maybe you can help? See the following code: \definefont[arabicamiri][file:amiri-quran.ttf*arabic at 15pt] \definefont[arabicb][file:uthmantn1ver10.ttf*arabic at 17pt] \starttext \setupalign[r2l] \arabicamiri ??? ?????? ????? ?????????? ????????? ???????????? ? ????? ????????? ????????? ???????????? ??????? ?????? ??????? ??????? ? ????????? ??????? ??? ????????? \blank\blank \arabicb ??? ?????? ????? ?????????? ????????? ???????????? ? ????? ????????? ????????? ???????????? ??????? ?????? ??????? ??????? ? ????????? ??????? ??? ?????????\par \stoptext There are some issues within this example: - overlapping letters (see "Aziyz") - "bi ayaatillah" (overlapping of fatha and hamza) And besides from that: It is not so harmonic like the other font, seems more like a not-caligraphic hand-font (no offense of course :)) But possibly I am making something very wrong, can you help me? Thank you very much. My project is to typesetting quran completely, and that is not easy without an perfect font. If you have a commercial variant with license, please inform me, our company would surely buy it. Thanks and wassalam

2 1

Intermediate format
by Jan Tosovsky 24 Nov '13

24 Nov '13

Dear All, is it possible to get the complete representation of the layout that is processed in the luatex PDF generator? I mean coordinations of individual text boxes, their dimensions etc. In e.g. XSL-FO processors it is provided in the XML based formats: http://www.renderx.com/reference.html#IntermediateFormatSpecification http://xmlgraphics.apache.org/fop/1.1/intermediate.html Actually, I'd like to retrieve the page number and vertical position of my object with a specific id (reference) to be able to perform PDF post-processing. Is DVI way to go? How can I get it in MkIV? Thanks, Jan

1 0

[***SPAM***] Re: No full Unicode-Support in ConTeXt?
by "H. Özoguz" 24 Nov '13

24 Nov '13

> not at all, as you show way more input here as in the jpeg ... so first > make a minimal example I did gave a min-example, didn't I? The JPG was only to make clear, what I mean with "little signs". Is that clear now? Dont know how to say it better way (sorry my english) :), > also "another font" is not revealing either Of course it is not, yes, sorry. But sometimes I have problems with different fonts (e.g. the letters are not connected), and these problems do not occur in CorelDraw or some other programs. That is, what I meant. (Besides from that, it should be clear that I am a very big fan of ConTeXt and all the way I am talking about it to friends and collegues, so: no attacks at all :)). > the only issue i see is that this otf font has 2048 units and gets > scaled wrong (in luatex's backend probably) The problem is not the scaling (may be too, but not my problem here). Don't you get the following problem in this (your) code? \definefont[arabica][file:uthmantn1ver10.ttf*arabic at 45pt] \definefont[arabicb][file:arabtype.ttf*arabic at 45pt] \starttext \setupalign[r2l] \arabica شَدِيدٌۗ\blank\blank \arabicb شَدِيدٌۗ\par \stoptext Maybe its an issue of my context-version, so see the attachment. With the font "arabtype" everything is fine, with the font "uthmantnver10" the sign is missing. Huseyin

1 0

No full Unicode-Support in ConTeXt?
by "H. Özoguz" 24 Nov '13

24 Nov '13

Hello there, I wonder why working with fonts is soo hard in ConText (much easier in Word or CorelDraw). See this following font (free, opensource): http://fonts.qurancomplex.gov.sa/wp-content/uploads/2012/06/UthmanTN1-Ver10… And try now this Context-Code: \definefont[arabic][file:UthmanTN1Ver10.ttf*arabic at 15pt] \starttext \arabic\setupalign[r2l] مِن قَبْلُ هُدًى لِّلنَّاسِ وَأَنزَلَ ٱلْفُرْقَانَۗ إِنَّ ٱلَّذِينَ كَفَرُوا بِـَٔايَـٰتِ ٱللَّهِ لَهُمْ عَذَابٌ شَدِيدٌۗ وَٱللَّهُ عَزِيزٌ ذُو ٱنتِقَامٍ \stoptext You see, this little signs above the letters are vanished in the PDF. But they are set in CoreDraw (for example). Why, what is the problem? Similar problems you can see with another font, no problem in CorelDraw, but problems in ConText. Hope for help. Thank you very much. Huseyin

3 6

Re: [NTG-context] Converting normal font into bold
by "H. Özoguz" 24 Nov '13

24 Nov '13

> The extend feature stretches the glyphs to get narrow or wide font but it doesn’t embolden it. > > The best solution is to get a font with a real bold style, money shouldn’t be a problem because fonts are cheap nowadays. > > Wolfgang Thanks, I hoped the it could really embold ist (like I did it in CorelDraw). Of course, money is not the problem at all - I am using it commercially, so the company should by any arabic font I would suggest. But it is very hard to find an modern font, which is capable of typsetting Quran, with full supprt and all special symbols (wich are not a part of standard modern arabic) - and more hard to find such a find in this style (Uthmanic). Huseyin

2 1

Re: [NTG-context] Converting normal font into bold
by "H. Özoguz" 24 Nov '13

24 Nov '13

> > > >> May be ConTeXt experts would have better suggestions, till then you > >> may want to look at the fake bold option in simplefonts - > >> http://wiki.contextgarden.net/Simplefonts#Faking_italics_and_bold_fonts > > > > Thanks for your advice. > > Unfortunately I did not manish to work with this font by simplefonts. I use the following simple setup: > > > > > > \definefont[arabic][file:bliblablup_0.ttf*arabic at 15pt] > > \definefontfeature[fakebold][extend=1.1] > > \definefont[arabic][file:<fontname>*arabic,fakebold at 15pt] > > > \starttext > > \arabic\setupalign[r2l] ٱللَّهُ لَآ إِلَـٰهَ إِلَّا هُوَ ٱلْحَىُّ ٱلْقَيُّومُ > > \stoptext > > > > How can I get these "fake bolds" with this setup? Or is it absolutely necessary to use Simplefont for these fake-bolds? > > The feature is unrelated to simplefonts. > > Wolfgang Thanks Wolfgang, but that does not seem to work with this font. See attachment, the font is wider, but not bold. ++++++++++++++++ \definefont[arabic][file:bliblablup_0.ttf*arabic at 15pt] \definefont[arabics][file:bliblablup_0.ttf*arabic at 15pt] \definefontfeature[fakebold][extend=1.2] \definefont[arabic][file:bliblablup_0.ttf*arabic,fakebold at 15pt] \starttext \arabic\setupalign[r2l] ٱللَّهُ لَآ إِلَـٰهَ إِلَّا هُوَ ٱلْحَىُّ ٱلْقَيُّومُ \blank\arabics\setupalign[r2l] ٱللَّهُ لَآ إِلَـٰهَ إِلَّا هُوَ ٱلْحَىُّ ٱلْقَيُّومُ \stoptext ++++++++++++++++ Huseyin

2 1

[***SPAM***] Re: No full Unicode-Support in ConTeXt?
by "H. Özoguz" 24 Nov '13

24 Nov '13

To be more concrete, I added an jpeg from CorelDraw, which shows, what I mean with these "little signs" above the letters. They are vanished in ConText, but are correctly set in CorelDraw with the very same font. Huseyin

1 0

Re: [NTG-context] Converting normal font into bold
by "H. Özoguz" 24 Nov '13

24 Nov '13

> May be ConTeXt experts would have better suggestions, till then you > may want to look at the fake bold option in simplefonts - > http://wiki.contextgarden.net/Simplefonts#Faking_italics_and_bold_fonts Thanks for your advice. Unfortunately I did not manish to work with this font by simplefonts. I use the following simple setup: \definefont[arabic][file:bliblablup_0.ttf*arabic at 15pt] \starttext \arabic\setupalign[r2l] ٱللَّهُ لَآ إِلَـٰهَ إِلَّا هُوَ ٱلْحَىُّ ٱلْقَيُّومُ \stoptext How can I get these "fake bolds" with this setup? Or is it absolutely necessary to use Simplefont for these fake-bolds? Thanks. Huseyin

2 1

[OT] − RobotoSlab Italics… or not
by Renaud Aubin 24 Nov '13

24 Nov '13

Hi folks, I'm working on a Roboto typescript and starting from the work done by Zen Lima back in last July, I would like to push things further. Since I work on some Android projects and use Google Keep mostly on a daily basis, I was surprised to not find italics for the RobotoSlab (either on the web or by extracting the assets of the Keep package). Why am I surprised: Keep do have serif title placeholders for the new note EditText and I see it everyday! $ mtxrun --script font --list --all --pattern=robotoslab robotoslab robotoslabbold RobotoSlab-Bold.ttf robotoslabbold robotoslabbold RobotoSlab-Bold.ttf robotoslablight robotoslablight RobotoSlab-Light.ttf robotoslabregular robotoslabregular RobotoSlab-Regular.ttf robotoslabthin robotoslabthin RobotoSlab-Thin.ttf OK, RobotoSlab fonts are accessible and I have a working typescript to use RobotoSlab with ConTeXt MkIV (I'll made the git repo public soon). At first, my thoughts are: nevermind the Slab italics but now, I'm curious since Inkscape, LibreOffice, … propose the italic and bolditalic features of the RobotoSlab (check out the attached font-manager screenshot). I've worked with different kind of fonts'family (more or less complete) and used and modified many typescripts in my ConTeXter's life but there I should be missing something obvious. Where are the RobotoSlab Italics??? My experience is that italic and bolditalic should correspond to files… First guess: no files so the RobotoSlab Italic and BoldItalic features are just faked ones composed by my GNU/Linux Debian system. No, I must be wrong here too… Any thoughts on "The Quest of the Hidden Italics of the RobotoSlab fonts!"? Best Regards, Renaud

3 5

Converting normal font into bold
by "H. Özoguz" 24 Nov '13

24 Nov '13

Hello together, I have an arabic font, which is quite perfect, but only a little bit too thin, so that it seems to "vanish" into the white of the paper. Unfortunately this font does not come with an bold-variant. Now I tried to manipulate it with CorelDraw, just converted into curves and added an contour (verys small 0.13pt, while font was 11pt) - and it worked! This "aritificial bold-font" works very well, better then I hoped, no problems - although it is no hand-tundes bold, but only countour-adding. Now the question: I obviously cant set the entire book (more than 600 pages) with Corel-Draw, and want too use ConText, of course. So is there a way to produce this boldness out of this too thin font within ConText, too? Thank your very much. Best regards, Huseyin

2 1

Simplefonts (new) fallback issue with Linux Libertine O
by Rik 24 Nov '13

24 Nov '13

Fallbacks (at least the range I tested) do not work with the roman face of Linux Libertine O in the new (core) simplefonts implementation. I first thought that this might be a Libertine issue, but further testing makes me suspect it may be a simplefonts issue. Or perhaps I have used the wrong syntax with the new implementation. Below are two MWEs, one based on the current standalone (current version: 2013.11.16 12:43), running on Windows 8.1 with the win64 bins, and the second based on an up-to-date TL13 (ConTeXt ver: 2013.05.28 00:36 MKIV) on the same system. Linux Libertine O is version When I run the standalone version, the fallback characters do not appear between the first angles, but do appear between the bf and it angles. They appear between angles in all cases with the TL13 MWE. I do not see the problem with my home-grown typescript for Libertine under either TL13 or the current standalone. I do not see the problem with Junicode, Gentium Book Basic, or Gentium Basic. I have not yet tried other fonts. Standalone MWE: \definefallbackfamily [libertine] [serif] [Gentium Plus] [range={0x02052-0x02058},force=yes] \definefontfamily [libertine] [serif] [Linux Libertine O] \setupbodyfont [libertine] \def\SDQP{⁓⁗}% Swung Dash Quad Prime U02053U02057 \starttext >\SDQP< >{\bf \SDQP}< >{\it \SDQP}< >{\bf{\it \SDQP}}< \stoptext TL13 MWE: \setupbodyfontenvironment [default][em=italic] \usemodule [simplefonts] \setmainfontfallback [Gentium Plus] [range={0x02052-0x02058},force=yes] \setmainfont [Linux Libertine O] \def\SDQP{⁓⁗}% Swung Dash Quad Prime U02053U02057 \starttext >\SDQP< >{\bf \SDQP}< >{\it \SDQP}< >{\bf{\it \SDQP}}< \stoptext -- Rik Kabel

2 2

Re: [NTG-context] Numberconversion problem in caption prefixes
by Géry Ogam 23 Nov '13

23 Nov '13

Thanks again Wolfgang, with this setup everything is fine. But I wanted to bring to the attention of Hans the inconsistency of the prefix conversions by defaut, so that he can correct them: I A chapter [a figure] Figure I.1 % <-- Here the conversion of the prefix to Romannumerals is done AUTOMATICALLY. 1.1 A section [a figure] Figure 1.2 % <-- Here the conversion of the prefix to Romannumerals is NOT done AUTOMATICALLY (the presence of a section before seems to DISCARD THE AUTOMATIC CONVERSION). Nor in the prefix of the section. Code: \setuphead[chapter][conversion=Romannumerals] \starttext \chapter{A chapter} \placefigure{}{\externalfigure} \section{A section} \placefigure{}{\externalfigure} \stoptext Every prefix should be AUTOMATICALLY converted, not half of them. Hans, could you please correct that in the next betas? Best regards.

1 0

[***SPAM***] Eliminating orpans in the Index
by Jan Tosovsky 23 Nov '13

23 Nov '13

Hello Everyone, in my two-column index there are several cases when the last entry in the given letter group overflows to the next column/page. In the extreme case it is just the last page reference. Can I somehow prevent this? E.g. keep at least two/three index entries together when the overflowing is triggered? And always keep all the page references together? Additionaly, columns are not balanced properly in all cases. When the first is longer, it is not a big problem. But the opposite case looks weird. Can I influence this behaviour? Thanks, Jan PS: Grid is not activated.

1 0

Re: [NTG-context] Index entries - custom font size
by Jan Tosovsky 23 Nov '13

23 Nov '13

On 2013-11-16 Jan Tosovsky wrote: > there are lot of index entries in my document and with the standard > body font size they occupy too much space. I've tried to decrease > the size by the textstyle parameter. It works, but it is applied > recursively to every nested level: secondary items are smaller twice > and tertiary items three times... > > \setupregister[index][command=\Word, textstyle=small] > \starttext > \index{primary}\index{primary+secondary}\index{primary+secondary+tertia > ry}Text > \completeindex > \stoptext > The following code switches the font size for all the index content. Even for group titles (letters), but it is beneficial here. The index title is split to keep the original size. \startbackmatter \chapter{Index} \start \switchtobodyfont[8pt] \placeindex \stop \stopbackmatter Jan

1 0

Re: [NTG-context] Paragraph - the last line handling
by Hans Hagen 23 Nov '13

23 Nov '13

On 11/22/2013 11:07 PM, Jan Tosovsky wrote: > Hello Everyone, > > in my document there are lot of cases when the last line in the paragraph > has a very narrow gap on the right (case 1 below). I understand it is > sometimes difficult to squeeze characters to the desired lenght (case 2) > without any impact to the final quality, but this looks very unnatural now > (besides all other lines, which are nicely typeset keeping the optical edge > on the right). > > Is it possible to somehow define that under a certain limit the line will be > expanded to the end (case 3)? > > xxxxxxxxxxxx (1) > xxxxxxxxxxxxxx > xxxxxxxxxxxxx > xxxxxxxxxxxx (2) > xxxxxxxxxxxxxx > xxxxxxxxxxxx > xxxxxxxxxxxx (3) > xxxxxxxxxxxxxx > xxxxxxxxxxxxxx > > I use the following setup now: > > \setupalign[hz, hanging] > \setuptolerance[verystrict] % even 'strict' doesn't help here > \setupindenting[medium, yes] > > Any idea? \hsize 15.4cm \input tufte \parfillskip30pt plus 1 fill \input tufte ----------------------------------------------------------------- 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 -----------------------------------------------------------------

2 1

Re: [NTG-context] Linespacing in TOC
by Hans Hagen 23 Nov '13

23 Nov '13

On 11/23/2013 1:44 PM, Jan Tosovsky wrote: > On 2013-11-23 Hans Hagen wrote: >> On 11/23/2013 12:16 PM, Jan Tosovsky wrote: >>> On 2013-11-23 Jan Tosovsky wrote: >>>> On 2013-11-22 Hans Hagen wrote: >>>>> On 11/22/2013 9:44 PM, Jan Tosovsky wrote: >>>>>> On 2013-11-20 Hans Hagen wrote: >>>>>>> On 11/19/2013 11:48 PM, Jan Tosovsky wrote: >>>>>>>> >>>>>>>> I'd like to tweak a default TOC linespacing... >>>>>>>> >>>>>>> \title{Table of Contents} >>>>>>> >>>>>>> \start >>>>>>> \setupinterlinespace[line=0.8ex] >>>>>>> \placecontent >>>>>>> \stop >>>>>> >>>>>> But as I found, any value below 2.8ex causes interline >>>>>> inconsistencies when >>>>>> special cases appears, see the extreme below: >>>>>> >>>>>> \starttext >>>>>> \start >>>>>> \setupinterlinespace[line=1.0ex] >>>>>> \placecontent >>>>>> \stop >>>>>> \chapter{aaaaaaaa}. % line without descenders >>>>>> \chapter{pppppppp}. % line with descenders >>>>>> \chapter{ŠŠŠŠŠŠŠŠ}. % the result is an inconsistent baseline >>>>>> \stoptext >>>>>> >>>>>> Is there any remedy for this? Can I fix the baseline distance >>>>>> somehow? >>>>>> >>>>> >>>>> \definegridsnapping[crap] [fit,0.2] >>>>> \setuplayout[grid=crap] >>>> >>>> This helps! But... it breaks something else :-( >>> >>> I've finally found an acceptable solution. >>> >>> During my tests I found a crucial difference between: >>> >>> \setupinterlinespace[line=2.0ex] >>> >>> and >>> >>> \setupinterlinespace[0.25] >>> >>> The latter sets the baseline distance correctly even without that >>> problematic snapping to the grid! >>> >>>> All lines in my book have a certain (default) linespacing. >>>> TOC entries are rendered (by default) using bigger linespacing. >>> >>> Btw, is there any option to override a default (huge) TOC >> linespacing? I >>> still consider my solution rather a hack. >> >> just set 'before' and 'after' > > Ok. I haven't realize that. > >> normally linespacing in the toc is the same as in the rest of the >> document unless one has assigned to before/after > > This example shows different behaviour: > > \showgrid > \starttext > \start > \placecontent > \stop > \chapter{aaaaaaaa}Foo > > Bar > \chapter{pppppppp}. > \chapter{ŠŠŠŠŠŠŠŠ}. > \stoptext > > On my computer the TOC linespacing is almost twice as big as that in the > paragraph. if the grid is on that can indeed be the case but only if there are lines with > lineheight so that's why you can use less strict options (older mails) 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 -----------------------------------------------------------------

2 1

Re: [NTG-context] Eliminating orphans/widows when grid is on
by Hans Hagen 23 Nov '13

23 Nov '13

On 11/23/2013 1:49 PM, Jan Tosovsky wrote: > Dear All, > > when the grid is switched on in my document, there are lots of orphan and > widows in the output. > > \setuplayout[grid=yes] % grid=tolerant doesn't help > > According to the manual the grid typesetting is a solely ConTeXt feature not > available in the core TEX. Is it production ready? Are there any options to > handle o/w correctly? indeed no core tex but context specific ... and work in progress but the fundamentals will not change, only more options / control / better heuristics might show up (also as side effect of opening up tex more) (usually i spend time on such things when i need it myself or in projects) 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

Eliminating orphans/widows when grid is on
by Jan Tosovsky 23 Nov '13

23 Nov '13

Dear All, when the grid is switched on in my document, there are lots of orphan and widows in the output. \setuplayout[grid=yes] % grid=tolerant doesn't help According to the manual the grid typesetting is a solely ConTeXt feature not available in the core TEX. Is it production ready? Are there any options to handle o/w correctly? Thanks, Jan

1 0

Re: [NTG-context] Linespacing in TOC
by Hans Hagen 23 Nov '13

23 Nov '13

On 11/23/2013 12:16 PM, Jan Tosovsky wrote: > On 2013-11-23 Jan Tosovsky wrote: >> On 2013-11-22 Hans Hagen wrote: >>> On 11/22/2013 9:44 PM, Jan Tosovsky wrote: >>>> On 2013-11-20 Hans Hagen wrote: >>>>> On 11/19/2013 11:48 PM, Jan Tosovsky wrote: >>>>>> >>>>>> I'd like to tweak a default TOC linespacing... >>>>>> >>>>> \title{Table of Contents} >>>>> >>>>> \start >>>>> \setupinterlinespace[line=0.8ex] >>>>> \placecontent >>>>> \stop >>>> >>>> But as I found, any value below 2.8ex causes interline >>>> inconsistencies when >>>> special cases appears, see the extreme below: >>>> >>>> \starttext >>>> \start >>>> \setupinterlinespace[line=1.0ex] >>>> \placecontent >>>> \stop >>>> \chapter{aaaaaaaa}. % line without descenders >>>> \chapter{pppppppp}. % line with descenders >>>> \chapter{ŠŠŠŠŠŠŠŠ}. % the result is an inconsistent baseline >>>> \stoptext >>>> >>>> Is there any remedy for this? Can I fix the baseline distance >>>> somehow? >>>> >>> >>> \definegridsnapping[crap] [fit,0.2] >>> \setuplayout[grid=crap] >> >> This helps! But... it breaks something else :-( > > I've finally found an acceptable solution. > > During my tests I found a crucial difference between: > > \setupinterlinespace[line=2.0ex] > > and > > \setupinterlinespace[0.25] > > The latter sets the baseline distance correctly even without that > problematic snapping to the grid! > >> All lines in my book have a certain (default) linespacing. >> TOC entries are rendered (by default) using bigger linespacing. > > Btw, is there any option to override a default (huge) TOC linespacing? I > still consider my solution rather a hack. just set 'before' and 'after' normally linespacing in the toc is the same as in the rest of the document unless one has assigned to before/after -- ----------------------------------------------------------------- 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 -----------------------------------------------------------------

2 1

Re: [NTG-context] Linespacing in TOC
by Jan Tosovsky 23 Nov '13

23 Nov '13

On 2013-11-23 Jan Tosovsky wrote: > On 2013-11-22 Hans Hagen wrote: > > On 11/22/2013 9:44 PM, Jan Tosovsky wrote: > > > On 2013-11-20 Hans Hagen wrote: > > >> On 11/19/2013 11:48 PM, Jan Tosovsky wrote: > > >>> > > >>> I'd like to tweak a default TOC linespacing... > > >>> > > >> \title{Table of Contents} > > >> > > >> \start > > >> \setupinterlinespace[line=0.8ex] > > >> \placecontent > > >> \stop > > > > > > But as I found, any value below 2.8ex causes interline > > > inconsistencies when > > > special cases appears, see the extreme below: > > > > > > \starttext > > > \start > > > \setupinterlinespace[line=1.0ex] > > > \placecontent > > > \stop > > > \chapter{aaaaaaaa}. % line without descenders > > > \chapter{pppppppp}. % line with descenders > > > \chapter{ŠŠŠŠŠŠŠŠ}. % the result is an inconsistent baseline > > > \stoptext > > > > > > Is there any remedy for this? Can I fix the baseline distance > > > somehow? > > > > > > > \definegridsnapping[crap] [fit,0.2] > > \setuplayout[grid=crap] > > This helps! But... it breaks something else :-( I've finally found an acceptable solution. During my tests I found a crucial difference between: \setupinterlinespace[line=2.0ex] and \setupinterlinespace[0.25] The latter sets the baseline distance correctly even without that problematic snapping to the grid! > All lines in my book have a certain (default) linespacing. > TOC entries are rendered (by default) using bigger linespacing. Btw, is there any option to override a default (huge) TOC linespacing? I still consider my solution rather a hack. Regards, Jan

1 0

Re: [NTG-context] Linespacing in TOC
by Hans Hagen 23 Nov '13

23 Nov '13

On 11/22/2013 9:44 PM, Jan Tosovsky wrote: > On 2013-11-20 Hans Hagen wrote: >> On 11/19/2013 11:48 PM, Jan Tosovsky wrote: >>> >>> I'd like to tweak a default TOC linespacing... >>> >>> I've 'invented' this: >>> >>> \setupcombinedlist[content][list=chapter, alternative=c] >>> >>> \starttext >>> >>> \title{Table of Contents} >>> \setupinterlinespace[line=0.8ex] % too small, just for testing >>> \placecontent >>> \setupinterlinespace[line=2.75ex] >>> %\setupinterlinespace[reset] >>> >>> \startfrontmatter >>> \chapter{Intro}text >>> >>> text >>> >>> text >>> \startfrontmatter >>> \startbodymatter >>> \chapter{Chapter}text >>> \stopbodymatter >>> \startbackmatter >>> \chapter{Appendix}text >>> \stopbackmatter >>> \stoptext >>> >>> I cannot use simply the \completecontent command as the linespacing >>> is effective already between the title and the first entry line... >>> so I am splitting the title and the rest and set the linespacing >>> just before list rendering. Finally I am resetting the value manually. >>> >>> Are there better ways to tweak linespacing in TOC ? >> >> \title{Table of Contents} >> >> \start >> \setupinterlinespace[line=0.8ex] % too small, just for testing >> \placecontent >> \stop > > Thanks for the hint. > > But as I found, any value below 2.8ex causes interline inconsistencies when > special cases appears, see the extreme below: > > \starttext > \start > \setupinterlinespace[line=1.0ex] > \placecontent > \stop > \chapter{aaaaaaaa}. % line without descenders precedes a line without > ascenders > \chapter{pppppppp}. % line with descenders is followed with a line with > ascenders > \chapter{ŠŠŠŠŠŠŠŠ}. % the result is an inconsistent baseline distance > \stoptext > > Is there any remedy for this? Can I fix the baseline distance somehow? > > I have such cases in my TOC :-( > (but not so extreme as here) \definegridsnapping[crap] [fit,0.2] \setuplayout[grid=crap] but if you really need that kind of tweaks you might consider using a better font: if interlinespace is too small you will never get nice results you can try to play with the h/d ratio: \setupinterlinespace[line=2.8ex,height=0.8,depth=0.2] \showstruts \strut x \setupinterlinespace[line=2.8ex,height=0.7,depth=0.3] \showstruts \strut x or you can plug in a command (in the toc handler) that puts each line in a box with manipulated dimensions 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 -----------------------------------------------------------------

2 1

Paragraph - the last line handling
by Jan Tosovsky 22 Nov '13

22 Nov '13

Hello Everyone, in my document there are lot of cases when the last line in the paragraph has a very narrow gap on the right (case 1 below). I understand it is sometimes difficult to squeeze characters to the desired lenght (case 2) without any impact to the final quality, but this looks very unnatural now (besides all other lines, which are nicely typeset keeping the optical edge on the right). Is it possible to somehow define that under a certain limit the line will be expanded to the end (case 3)? xxxxxxxxxxxx (1) xxxxxxxxxxxxxx xxxxxxxxxxxxx xxxxxxxxxxxx (2) xxxxxxxxxxxxxx xxxxxxxxxxxx xxxxxxxxxxxx (3) xxxxxxxxxxxxxx xxxxxxxxxxxxxx I use the following setup now: \setupalign[hz, hanging] \setuptolerance[verystrict] % even 'strict' doesn't help here \setupindenting[medium, yes] Any idea? Thanks, Jan

1 0

Re: [NTG-context] Linespacing in TOC
by Hans Hagen 22 Nov '13

22 Nov '13

On 11/19/2013 11:48 PM, Jan Tosovsky wrote: > Dear All, > > I'd like to tweak a default TOC linespacing... > > I've 'invented' this: > > \setupcombinedlist[content][list=chapter, alternative=c] > > \starttext > > \title{Table of Contents} > \setupinterlinespace[line=0.8ex] % too small, just for testing > \placecontent > \setupinterlinespace[line=2.75ex] > %\setupinterlinespace[reset] > > \startfrontmatter > \chapter{Intro}text > > text > > text > \startfrontmatter > \startbodymatter > \chapter{Chapter}text > \stopbodymatter > \startbackmatter > \chapter{Appendix}text > \stopbackmatter > \stoptext > > I cannot use simply the \completecontent command as the linespacing is > effective already between the title and the first entry line... so I am > splitting the title and the rest and set the linespacing just before list > rendering. Finally I am resetting the value manually. The 'reset' keyword > seems to be somehow ignored... > > Are there better ways to tweak linespacing in TOC ? \title{Table of Contents} \start \setupinterlinespace[line=0.8ex] % too small, just for testing \placecontent \stop ----------------------------------------------------------------- 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 -----------------------------------------------------------------

2 1

Footnote line position
by Jan Tosovsky 22 Nov '13

22 Nov '13

Dear All, when a single line footnote is used, the footnote divider is rendered in larger distance than for footnotes with two or more lines (I mean a gap between the line and the footnote text). Initially I though there must be an 'empty' paragraph in my footnote but looking into the source it turned out to be a false alarm as it seems to be consistent. It can be tested easily: \chapter{Chapter}Foo\footnote{Bar}. \chapter{Chapter}Foo\footnote{Bar Bar}. Is this behaviour deliberate? Thanks, Jan ConTeXt 2013.11.14 & Win 7

1 0

Re: [NTG-context] Numberconversion problem in caption prefixes
by Géry Ogam 22 Nov '13

22 Nov '13

Thank you Wolfgang, it does what I want. However, I realised after trying the following code inside environments (frontmatter, bodymatter, backmatter and appendices) that the default behaviour is WRONG because the conversions of prefixes are not always automatic. For instance, in the appendix environment, by default chapter numbers are Characters and every prefix representing a chapter number is also a Character (section prefixes, caption prefixes and so on). Now if you decide to switch chapter numbers to Romannumerals, you will get something totally inconsistent if you don’t do many conversions manually: *\startsectionblockenvironment[appendix]* * \defineconversionset[romannumeralsconversionset][][R]* * \setuphead[chapter][sectionconversionset=romannumeralsconversionset]* *\stopsectionblockenvironment* *\starttext* *\startappendices* *\chapter{Cool}* *\placefigure{A cow}{\externalfigure[cow]}* *\chapter{Cat}* *\section{Mouse}* *\section{Dog}* *\placefigure{A cow}{\externalfigure[cow]}* *\stopappendices* *\stoptext* which gives: *I Cool* *[figure] Figure I.I Cow % <-- Here the prefix conversion from 'A' to 'I' works.* *II Cat* *B.1 Mouse % <-- Here the prefix conversion from 'B' to 'II' does NOT work.* *B.2 Dog % <-- Here the prefix conversion from 'B' to 'II' does NOT work.* *[figure] Figure B.II Cow % <-- Here the prefix conversion from 'B' to 'II' does NOT work (because of the presence of the 2 sections B.1 and B.2 where the prefix conversion already did not work I think, so here is the BUG).* Extra: is it normal that caption NUMBERS (not prefixes) are converted to Romannumerals by default INSIDE the appendix environment (outside they are usual numbers)? ('Figure I.I Cow' and 'Figure B.II Cow' instead of 'Figure A.1 Cow' and 'Figure B.2 Cow'.)

2 1

Re: [NTG-context] Problem with urls.
by Robert Blackstone 22 Nov '13

22 Nov '13

On 21 Nov 2013, at 19:53 , Wolfgang Schuster <schuster.wolfgang(a)gmail.com> wrotr >> > > I can process your example without problems. > > ConTeXt ver: 2013.11.16 12:43 MKIV beta fmt: 2013.11.21 int: english/english > > Wolfgang Thank you for your reaction. This is odd. Here this EM does not work with CONTEXT version 2013.11.14 23:22, (which uses LuaTeX version 0.76.0 as engine.) (to get this information I had of course to outcomment the "\from[apurl]") Still stranger: when I plugged the url into some other TeX-file it did work with the same ConTeXt version. So it seems that there is some essential difference between these files (apart from their content) Do you have any idea what that could be? Could it be a matter of text encoding? (I use TeXShop as the front end.) Best regards, Robert Blackstone

2 1

Drawing chemical structures
by DesdeChaves 21 Nov '13

21 Nov '13

Dear Sirs, I'm trying to run some code from the ppchtex manual, however, the chemical structures are not correctly drawn. See the example: https://www.dropbox.com/s/w7v8kouc4glndf0/chemicerror.pdf. I found this problem en Minimals (last version) and on TexLive 2013. \setupbodyfont[11pt] \usemodule[chemic] \starttext \startchemical[width=fit,scale=small,size=big] \bottext{α-Glycerophosphate} \chemical[ONE,SB1357,Z0357][\TL{α}{C},\SL{OPO\lohi{3}{2-}},H,H] \chemical[MOV1,SB137,Z037][C,\SL{OH},H] \chemical[MOV1,SB137,Z0137][C,H,\SL{OH},H] \stopchemical \definechemical[desoxyribose] {\chemical[FIVE,FRONT,BB125,+SB3,-SB4,Z4][O] \chemical[FIVE,FRONT,+R1235,+RZ1235][H,H,\SR{HOH_2C},OH] \chemical[FIVE,FRONT,-R1235,-RZ1235][H,OH,H,H]} \startchemical[height=6500,top=2000,bottom=2500,width=4500] \chemical[desoxyribose] \bottext{Desoxiribosa (dR)} \stopchemical \startchemical[height=4500,bottom=2500] \bottext{$\alpha$-D-Fructofuranose} \chemical [FIVE,FRONT,BB125,+SB3,-SB4,Z4][O] \chemical [FIVE,FRONT,+R1235,+RZ1235][\SR{HO},H,\SR{HOH_2C},CH_2OH] \chemical [FIVE,FRONT,-R1235,-RZ1235][OH,H,\SR{HO},H,CH_2OH] \stopchemical \startchemical[height=4500,bottom=2500] \chemical [FIVE,FRONT,B,R] \chemical [+RZ1..5] [1,2,3,4,5] \chemical [-RZ1..5] [a,b,c,d,e] \stopchemical \stoptext

3 4

Extra blank page after title page.
by john Culleton 21 Nov '13

21 Nov '13

Here is the code. first the file title.tex: ----------------- \startstandardmakeup[doublesided=no] (title stuff) \stopstandardmakeup ------------------- and next the file copy.tex: -------------------------------------- \startstandardmakeup[page=no] (contents) \stopstandardmakeup ------------------------ MY master file contains: \input title.tex \input copy.tex ---------------------- An extra blank page is inserted between the title page and the title verso. If I combine the two files into a new file combine.tex, eliminate the two input lines above and say \input combine.tex instead I still get the unwanted blank page in between. Using MKIV and TexLive 2013 on Linux. -- John Culleton Wexford Press Free list of books for self-publishers: http://wexfordpress.net/shortlist.html PDF e-book: "Create Book Covers with Scribus" available at http://www.booklocker.com/books/4055.html

2 2

Re: [NTG-context] Space problem after formulas inside itemize environments
by Géry Ogam 21 Nov '13

21 Nov '13

> What’s wrong with the second formula, both have the same space before and after the content? Then maybe Hans has corrected it recently. I am using ConTeXt version 2013.04.20, and you?

2 1

Problem with urls.
by Robert Blackstone 21 Nov '13

21 Nov '13

Dear all, Presently I'm experiencing a problem with urls that, hopefully, the ME will demonstrate. It seems to me that something must have changed in the source since the end of september. The example works with mkiv of 24 sept, but not with that of 3 november and later. --------------------------------------------------- \useURL[apurl][http://wiki.contextgarden.net/Category:Commands] \starttext \from[apurl] \url[apurl] \stoptext -------------------------------------------- I use TeXshop. The console gives me the following cryptic message about a LuaTeX error: \ctxcommand #1^^@-\directlua {commands.#1} \font_helpers_low_level_define ...caledfontmode )} \edef \somefontspec {at \n... \font_helpers_trigger_define ..._identifier_class \csname \v_font_identifier… \applyfontclassstrategies ...\fontface \endcsname \else \expandafter \font_h... \font_helpers_synchronize_font ...classstrategies \fi \setfalse \c_font_auto... \tt f-\ifmode \mathtt \else \normaltt \fi … l.5 \from[apurl] ? Thanks in advance for any help. Best regards, Robert Blackstone

2 1

Re: [NTG-context] Space problem after formulas inside itemize environments
by Géry Ogam 21 Nov '13

21 Nov '13

Could you correct this space problem Hans? \startitemize \item Eeny, meeny, miny, moe \placeformula \startformula \text{Numbered formula: the space after is correct.} \stopformula \item Eeny, meeny, miny, moe \placeformula[-] \startformula \text{Unumbered formula: the space after is too big.} \stopformula \item Eeny, meeny, miny, moe \stopitemize

2 1

Numberconversion problem in caption prefixes
by Géry Ogam 21 Nov '13

21 Nov '13

Hello, There is a numberconversion problem in caption prefixes. For instance, if chapter numbers are set to Romannumerals, the conversion of the caption prefixes depends on the presence of a section Minimal example: \setuphead[chapter][conversion=Romannumerals] \setupcaption[way=bychapter, prefixsegments=chapter] \starttext \chapter{Cool} \placefigure{A cow}{\externalfigure[cow]} \chapter{Cat} \section{Mouse} \section{Dog} \placefigure{A cow}{\externalfigure[cow]} \stoptext The previous code displays an inconsistent caption prefix (first time a Romannumeral, second time a number): I Cool [figure] Figure I.1 A cow II Cat 2.1 Mouse 2.2 Dog [figure] Figure 2.1 A cow

2 2