- ntg-context - Mailing Lists

Devanagari in Siddhanta font with Context m-iv
by Shree Devi Kumar 09 Dec '13

09 Dec '13

I am converting some ITRANS documents with vedic accents to devanagari pdf files using Context. I tried both Chandas and Siddhanta fonts with it, I would prefer to use Siddhanta but in some cases the display is not coming correctly. eg. स॒र्वार्थ॑ in स॒र्व॒म॒ङ्ग॒लमा॒ङ्गल्ये॑ शि॒वे स॒र्वार्थ॑ साधिके। शर॑ण्ये त्र्यम्ब॑के दे॒वि॒ ना॒राय॑णि न॒मोऽस्तु॑ ते॥ does not display correctly when using Siddhanta font but it display correctly in Chandas. Please let me know if you need more details. Thanks, Shree

2 1

Re: [NTG-context] interaction strangeness
by Martin Moncrieffe 08 Dec '13

08 Dec '13

Nope..was sleeping. Just woke… __martin On 8 Dec 2013, at 19:55, Jan Tosovsky <j.tosovsky(a)email.cz> wrote: > On 2013-12-06 H. van der Meer wrote: >> Some further experimentation: interchanging two chapters makes the >> problem go away. >> >> It is reproducible, because putting the chapters back als brings the >> problem back. Even stranger, sitting at chapter 5 it kills the >> interaction for chapter 6 and 8, leaving the interactivity for the >> intervening and later chapters intact. >> >> Addition of content to the start of chapter 5 helped for chapter 6 but >> not for chapter 8, which seems strange. >> Addition of content to the end of chapter 5 also helped for chapter 6 >> >> Addition of content to the start of chapter 7 did help to solve for >> chapter 8. >> >> So I fear it has in some way to do with the moment the output routine >> is >> called in relation to the reference processing in >> \startchapter[title=,reference=]. > > This topic was discussed few weeks ago without clear conclusion: > http://www.ntg.nl/pipermail/ntg-context/2013/075988.html > > In my case most of cases were resolved when I changed > \placebookmarks[chapter, section] just to \placebookmarks[chapter] > Although few cases still remain, it is much better now. > > When the particular item doesn't react via bookmark, it doesn't react also > via ToC. > > I plan to prepare an example for this, but for me it is not so urgent issue. > > 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 > ___________________________________________________________________________________

1 0

Re: [NTG-context] [***SPAM***] Incorrect internal font processing
by Khaled Hosny 08 Dec '13

08 Dec '13

On Sun, Dec 08, 2013 at 09:19:26PM +0100, Jan Tosovsky wrote: > On 2013-12-01 Khaled Hosny wrote: > > On Sun, Dec 01, 2013 at 11:21:30AM +0200, Khaled Hosny wrote: > > > > Interestingly, after I patched Sorts Mill (a FontForge fork) to avoid > > duplicates[1] I ended up with a ‘dotlessi.sc’ glyph, as it turns out > > the font has a <dotlessi> → <regular smallcap i> later on, so that is > > where FontLab gets the glyph name, too. > > > > I’ll try to port this patch to LuaTeX later. > > Thanks for handling this! > > When can I expect this fix in luatex.dll updated on my local machine > using the first-setup script? I pushed the patch to LuaTeX trunk, so it should be in the next release, but no idea about which or when. Regards, Khaled

1 0

Re: [NTG-context] [***SPAM***] Incorrect internal font processing
by Khaled Hosny 08 Dec '13

08 Dec '13

On Wed, Nov 27, 2013 at 11:35:01PM +0100, 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(!) Right, the font (like many MS fonts) uses version 3 ‘post’ table which includes no glyph names at all, software that needs glyph names (e.g. LuaTeX, since you can’t embed a font is PDF without glyph names else printers would go nuts) have to generate it. Some software will use dump names; glyph1 etc. using glyph id, others will try to guess more sensible names from the OpenType layout tables. > 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. FontForge uses the layout tables, too, but this font has a catch, it has two <i> → <some glyph> substitutions in the ‘smcp’ feature, one to a dotted small cap for Turkish (under TRK tag) and a regular one, and FontForge just names the resultant glyph ‘i.sc’ in both cases since it does not seem to check for duplicates, thinking that only one such a substitution can happen per feature. LuaTeX uses a (subset of) FontForge internally, so you get the same bug. It is not clear to me how FontLab arrived to the dotlessi name from the GSUB table, but I need to look into the font a bit more closer. Regards, Khaled

2 2

interaction strangeness
by H. van der Meer 08 Dec '13

08 Dec '13

Something strange happened here with the interaction in a pdf produced. There are chapters reacting when clicked in the table of contents but some are not. Moreover, this behaviour changes with the version of context used. I tried 3 versions of the beta: ConTeXt ver: 2013.10.15 13:52 MKIV beta ConTeXt ver: 2013.11.10 12:23 MKIV beta One specific chapter does not jump to the starting page when clicked. ConTeXt ver: 2013.12.04 11:34 MKIV beta Nothing changed in the source but now another chapter link also becomes inactive! There is no ready explanation I can think of. Because the document in question is about 500 pages I do not yet have a minimal example at hand. And as I suspect the problem can have its origin in the complexity and/or size of the document, I fear the construction of a minimal example will be difficult. Therefore I am first asking if this problem is known already. Afterwards I will try to find a small example, of course. Hans van der Meer

3 3

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