- ntg-context - Mailing Lists

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

12 Dec '13

Thanks for your reply. I am using a goodies file for coloring the accents. I am attaching that as well as a MWE tex file and resulting pdf. Chandas is not fully unicode compliant for some of the accents which are encoded in PUA, hence I would like to use Siddhanta which I understand is a completely redesigned version of Chandas fully compartible with Vedic Unicode Fonts are available from: Siddhanta: http://svayambhava.org/index.php/en/fonts Chandas: http://www.sanskritweb.net/cakram/ Thanks, Shree Devi Am 07.12.2013 um 15:21 schrieb Shree Devi Kumar <shreeshrii at gmail.com <http://www.ntg.nl/mailman/listinfo/ntg-context>>: >* 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. * Make a minimal example and provide links for the fonts (if possible). Wolfgang

2 2

Understanding the basics of \define
by Pavel Stupin 11 Dec '13

11 Dec '13

Hello: I'm struggling with understanding the way \define is supposed to work. I would like to have a macros to generate tables and populate them with some specific data submitted as arguments. I apologize for my lack of understanding of the very basics, but e.g. the following code just doesn't compile: \define[1]\mytable{ \startxtable \startxrow \startxcell #1 \stopxcell \stopxrow \stopxtable} \mytable{abc} I would appreciate your help and maybe some references to read (if any) in order to educate myself. Kind regards, Pavel.

4 10

incrementing counters in tables
by Jannik Voges 10 Dec '13

10 Dec '13

Dear ConTeXt-Users, I want to use counters in tables. But incrementing counters in tables doesn’t work as expected. For example, when I typeset the following example, I get numbers between 80 and 119, I would expect numbers between 0 and 39. How can I get the desired numbers? \definenumber[test] \starttext \bTABLE \dorecurse{8}{ \bTR \dorecurse{5}{\bTD \rawcountervalue[test]\incrementnumber[test] \eTD} \eTR } \eTABLE \stoptext Thanks Jannik Voges

2 2

[OT] Type:Rider
by Flavien Lambert 10 Dec '13

10 Dec '13

Dear all, I am pretty sure that some of you are fond of typography so I dared to make you aware of a really beautiful game running on phones and tablets dedicated to typography. Called Type:Rider, it is composed of several chapters, each dealing with a period of time illustrating the main techniques, fonts and design ideas. The game is really well done in terms of picture and music, the character being two dots evolving on letters from the main font of the time with background extracted from well-known art scenes. Best regards, Flavien.

1 0

Adding a space between multiple years from same authors
by Steffen Kram 10 Dec '13

10 Dec '13

Hi, I’m using the apa-de style. When my citation includes publications from the same authors, then using \cite[authorFirstRef,authorSecondRef] or \cite[authoryear][authorFirstRef,authorSecondRef] will not include Spaces between the years, e.g. \cite[Dyer:2012ts,Dyer:2012hy,Dyer:2013te] => … (Dyer et al., 2012a,2012b,2013a) \cite[authoryear][Dyer:2012ts,Dyer:2012hy,Dyer:2013te] => … Dyer et al. (2012a,2012b,2013a) How can I accomplish that the years are separated by comma and space: => … Dyer et al. (2012a, 2012b, 2013a) I already played with the setupcite command and peeked at the source code but could not find the right place or an idea how to change this. Seems like setupcite has not option and this is somewhere buried deep in the compact-layout code. Any ideas? Cheers, Steffen

2 2

Russian language support in ConTeXt
by Pavel Stupin 10 Dec '13

10 Dec '13

Hello: I would like to use ConTeXt for typesetting the documents in Russian. I used it about 10 years ago and it worked just fine. Much has been changed since then, however, and it doesn't work out-of-box while the only howto I've been able to find (http://wiki.contextgarden.net/Russian) seems to be outdated as none of the examples works with the latest ConTeXt. Could someone please explain me what I need to set up the program accordingly. I would appreciate your help a lot. Kind regards, Pavel.

2 3

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