ntg-context November 2018

ntg-context@ntg.nl

40 participants
63 discussions

improving kannada script
by Ulrike Fischer 04 Nov '18

04 Nov '18

According to the xelatex output in the following example both variants are not correct. What would be needed would be the first two glyphs from variant 1 (knd2 script) and the third from variant 2 (knda script). Pictures comparing the output can be found at https://github.com/u-fischer/luaotfload/issues/20 (Disclaimer: I have no idea if xelatex/harfbuzz is correct here, but https://tex.stackexchange.com/a/457427/2388 says so). \definefontfeature [kannada-testA] [indic-common] [script=knd2, % basic shaping pref=yes, blwf=yes, half=yes, pstf=yes, cjct=yes ] \definefontfeature [kannada-testB] %identical to default kannada-one [indic-common] [script=knda, % basic shaping pref=yes, blwf=yes, half=yes, pstf=yes, cjct=yes ] \definefont [kannadatestA][file:notosanskannada-regular.ttf*kannada-testA] \definefont [kannadatestB][file:notosanskannada-regular.ttf*kannada-testB] \starttext \section{Skript knd2} \kannadatestA ಕಿ ಕ್ರ ರ್ಕ \section{Skript knda (default)} \kannadatestB ಕಿ ಕ್ರ ರ್ಕ \stoptext -- Ulrike Fischer http://www.troubleshooting-tex.de/

4 12

Projects and URLs
by Axel Kielhorn 03 Nov '18

03 Nov '18

Hello! Where is the best way to define URLs in a project? I currently define them when I need them, but wouldn’t it be better to keep them in a project file and have only one location to edit when they change? Greetings Axel

4 4

Font Awesome (again)
by Aditya Mahajan 01 Nov '18

01 Nov '18

Hi, There is a FontAwesome.otf file that is distributed with ConTeXt minimals. Does anyone know what version (4 or 5) of the font it is? I am asking because the names of the symbols used in the font do not match those on the font-awesome website. For example, using \showsymbolset[fontawesome] I get that the symbol for "utensils" (https://fontawesome.com/icons/utensils?style=solid) is actually mapped to "food" in ConTeXt. Since the names of the symbols are now taken from the font, my guess is that the distribution has an old version of the font (also because it is a single font rather than three). Would it make sense to update the fonts in the distribution? If not, then simply remove the old version of the fonts? Also, don't we need to update the symb-imp-fontawesome.mkiv file to work with the new symbols. Font awesome has split the fonts into three (https://fontawesome.com/how-to-use/on-the-desktop/setup/getting-started): Solid, Regular, and Brands. (There are also pro version of the fonts). The simplest way to use them will be to have three symbolsets (fontawesome, fontawesome-solid, and fontawesome-brands), where the names are taken from the fonts. In the meanwhile, Hraban has painstakenly written out the mappings by hand, but the automatic mapping might be simpler (and more future proof). https://github.com/fiee/ConTeXt/blob/master/symbols/symb-awesome5.mkiv Thanks, Aditya

6 10

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

ntg-context November 2018