[NTG-context] Re: PDF/UA-2, WTPDF
Am Sun, 7 Apr 2024 11:57:33 +0200 schrieb Henning Hraban Ramm: >>> Oh, as usual with PDF association… >> >> Sorry that pdf/UA-2 costs something is due to ISO not to the PDF >> association. The PDF association made the WTPDF document which is >> for free (and is very similar to pdf/UA-2). And imho they are also >> trying to get sponsors for PDF/UA-2 (something they already did for >> the PDF 2.0 spec which you now can buy for 0€). > > Ok, sorry for barking at the wrong tree! > > And I guess DANTE as a member of PDF association has access to the > documents anyway? No, members have access to drafts during the time such a standard is developed and discussed in the Working Groups but once it is released there is no longer a free access. BTW: The LaTeX Project is a member too https://pdfa.org/member/ -- Ulrike Fischer http://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: PDF/UA-2, WTPDF
Am Sun, 7 Apr 2024 09:31:30 +0200 schrieb Henning Hraban Ramm: > Am 07.04.24 um 08:06 schrieb Hans Hagen: >> On 4/6/2024 5:34 PM, Henning Hraban Ramm wrote: >> >>> 1. PDF/UA-2 >>> https://pdfa.org/iso-14289-2-pdfua-2/ >> >> looks likes one has to pay for it > > Oh, as usual with PDF association… Sorry that pdf/UA-2 costs something is due to ISO not to the PDF association. The PDF association made the WTPDF document which is for free (and is very similar to pdf/UA-2). And imho they are also trying to get sponsors for PDF/UA-2 (something they already did for the PDF 2.0 spec which you now can buy for 0€). -- Ulrike Fischer http://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: How to make words searchable without diacritics
Am Mon, 7 Aug 2023 09:17:19 -0300 schrieb Marcus Vinicius Mesquita: > Thank you for the answers, Bruce, Pablo and Hraban. I was not aware of > ActualText. > > But \pdfbackendactualtext is actually just what I needed since it can > be used also for other things like: I don't think that it would be a good idea to use ActualText for this. You are effectivly changing the content and meaning of your text, not only for search, but also for copy, screen reader, html export etc. If you think it is okay to claim that the text is filia and then the accents are irrelevant, then why don't you print filia directly? -- Ulrike Fischer http://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] tikz + lmtx
Am Fri, 28 Apr 2023 01:01:23 -0400 (EDT) schrieb Aditya Mahajan via ntg-context: > Circuitikz still doesn't work. Even loading the module fails. It works for me on texlive 2023 with your new module file. -- Ulrike Fischer http://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] PDF 2.0 standard documents now free
Am Thu, 6 Apr 2023 09:02:10 +0200 schrieb Hans Hagen via ntg-context: >> You can put in arbitrary data and then download. >> I don’t think it will become any more free. >> >> indeed, but then: why don't we put them on the wiki site / another >> free site ? > >> Any legal restrictions ? Yes, the copy I got has in the footer Sold by the PDF Association to Ulrike Fischer | April 5, 2023 | Single user only, copying and networking prohibited. I wouldn't distribute it for the same reason I wouldn't distribute pdf copies of the TeXbook. > What happens when the sponsors withdraw? What should happen? I bought a copy at a very good price (0€) and now own it. If the sponsorship ends and the price goes up to 200 CHF again nothing changes for me. > What is there are updates (unlikely anyway). Amendments to ISO document typically have to be buyed too, e.g. amendment 1 (which is part of the bundled offered by pdfa) normally costs 17 CHF. Personally I think that the PDF Association made a very good job here (they worked hard on it), I'm quite grateful for it and I hope that there will more of these offers (personally I would like to get pdf/A-4 and the upcomming pdf/UA-2). -- Ulrike Fischer http://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] tikz error upgrading to texlive version (artix)
Am Fri, 31 Mar 2023 10:10:43 +0200 schrieb Hans Hagen via
ntg-context:
> \usemodule[tikz]
>
> \starttext
>Hello World.
> \stoptext
> works ok here
It fails for me in texlive 2023.
I don't know who changed what here, but it looks like a catcode
problem. context loads tikz files in m-tikz.mkxl with
\tikzinputfiles, and that calls \setcatcodetable\texcatcodes. After
that ~ has catcode 12 and that breaks the \let~\pdfmath@char@quote
in the pgfmathparser.code.tex file
\begingroup
\lccode`\~=`\"
\lowercase{\endgroup
\def\pgfmath@catcodes{%
\catcode`\==12 %
\catcode`\,=12 %
\catcode`\|=12 %
\catcode`\&=12 %
\let~\pgfmath@char@quote
}}%
--
Ulrike Fischer
http://www.troubleshooting-tex.de/
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
Re: [NTG-context] Subject: Leading spaces verbatim
Am Sat, 28 Jan 2023 03:01:24 +0100 schrieb Kalouguine Andre via ntg-context: > I'm trying to make a verbatim block of text with copiable leading spaces > so that students can just copy my Python code snippets into their IDE. This basically doesn't work (quite unrelated to the tex code). The PDF viewers have all their own mind here and none of them is really "code friendly". See e.g. https://tex.stackexchange.com/a/472112/2388 It works sometimes a bit better if the PDF is tagged, but there too you can't currently rely on four spaces staying four spaces (and not all PDF reader understand tagging). Better attach files with code. -- Ulrike Fischer http://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] TUG 2023
Am Wed, 4 Jan 2023 17:50:52 +0100 schrieb Thomas A. Schmitz via ntg-context: > But to my topic: the official announcement for TUG 2023 is out. It will > be in Bonn, Germany, in a building literally (literally!) just across > the street from my university office. Interesting how near people can be ;-) I will have to go over the bridge ... > I guess I just what to get a feeling what to expect at a TUG conference. You could look at previous TUG videos to get a feeling https://www.youtube.com/@TeXUsersGroup/playlists but imho you shouldn't worry. -- Ulrike Fischer http://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] LMTX generates PDFs with non-working fonts on real printers
Am Tue, 4 Oct 2022 18:09:28 +0200 schrieb Hans Hagen via ntg-context: >> Hans, is it possible that LMTX uses some technique that is “too modern” >> for some built-in PDF interpreter? > we basically use the old pre 1.6 embedding, same as luatex I saw that the new code renumbers the glyphs, so it uses 0001, 0002 etc instead of the mix of various slot numbers in luatex. Perhaps the printers don't like that. -- Ulrike Fischer http://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] LMTX: different output if dots are used in the file name
Am Wed, 7 Jul 2021 12:25:29 -0600 schrieb Alan Braslau: > Windows, I believe, does not take kindly to filenames containing > multiple dots. > > Therefore, Hans never uses such filenames and does not expect them, > either, so I am not surprised that this yields unpredictable results. > > An unfortunate side-effect of dealing with Windows. Sorry but this is nonsense. I have seen many files with lots of dots in windows and it works fine. I wouldn't do it in tex, but not because of the OS but because until a few years you could run into problems with some tex applications or macros which didn't expect many dots. -- Ulrike Fischer https://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] A not so short introduction to ConTeXt Mark IV
Am Mon, 4 Jan 2021 15:30:43 +0100 schrieb Hans Hagen: >> Well we discourage the use of plain commands to avoid that new users >> trip over bewildering errors from stuff like "abc \hskip 2cm plus >> cde", but it is not forbidden to use them. > Hm, \hskip is not a plain command but a language primitive. Yes, sorry. I lost the "TeX" from the "(plain) TeX commands" from Henning. > One of those 'persistent' wrong ideas about context is that it somehow > is kind of plain Really? I wouldn't see it this way. I wondered a bit about the number of primitives shown in the document of Joaquín, but that they are used certainly doesn't make context like plaintex. -- Ulrike Fischer http://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] A not so short introduction to ConTeXt Mark IV
Am Sun, 3 Jan 2021 23:59:14 +0100 schrieb Henning Hraban Ramm: > In LaTeX most problems are solved with “use this or that package”, You only need to follow a few days the questions e.g. on tex.sx to see that this is not true: Answers about LaTeX are much more varied than a simple "use this package" and often include new definitions or background explanations. > without the need to understand the commands and settings > involved, The fact that there are so many packages extending LaTeX actually means that there is *more* need to understand commands and settings than in a system like context where "most problems are solved with \setupsomething[somekey=somevalue]". (But it also means that there are many people, who understand enough of the innards to write, to document and to explain packages, commands and settings.) > Of course it helps to understand basic TeX stuff – but you’re not > supposed to use (plain) TeX commands in LaTeX, while it is or was > much more usual in ConTeXt. Well we discourage the use of plain commands to avoid that new users trip over bewildering errors from stuff like "abc \hskip 2cm plus cde", but it is not forbidden to use them. -- Ulrike Fischer http://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
[NTG-context] conflict between colored emoji and save/restore
When using a colored emoji font directly after a save/restore pair
in context mkiv following text gets lost:
\pdfvariable compresslevel=0
\font\fontB={file:seguiemj.ttf:mode=node;+colr;}
\starttext
\pdfextension save\relax
\pdfextension restore\relax
{\fontB \char"2603} % is not there
\stoptext
The problem is that the coordinate transformation from the restore
ends inside the emoji code:
/Span << /ActualText >> BDC
q
0.000 g
1 0 0 1 -70.867 -714.33967 cm %<
BT
(Such an save/restore part is e.g. inserted with a scaled graphics:
\externalfigure[tinypicture.pdf][width=1cm])
--
Ulrike Fischer
http://www.troubleshooting-tex.de/
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] Using ConTeXt with LuaTeX variants
Am Wed, 4 Dec 2019 20:10:13 -0500 schrieb Jairo A. del Rio:
> I want to know if it's possible use HarfTeX/LuaHBTeX with ConTeXt (MKIV),
...
> Although this is pretty easy with LaTeX:
>
> \usepackage{harfload}
> \setmainfont{font}[RawFeature={mode=harf}]
unrelated to your question but this is no longer the recommended way
to use harf mode in latex.
After some discussion the latex team decided to build lualatex next
year over luahbtex. For testing purpose lualatex-dev already now
uses luahbtex. harftex has been archived and its development has
stopped. The harfload code has been integrated into luaotfload.
Also fontspec has been updated and offers keys to activate harf
mode.
So your document should look like this:
\documentclass{article}
\usepackage{fontspec}
\setmainfont{font}[Renderer=Harfbuzz]
...
This requires a current luaotfload and you should use lualatex-dev
to compile it.
--
Ulrike Fischer
https://www.troubleshooting-tex.de/
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
[NTG-context] cm unicode font: missing tounicode of oldstyle nums
cmunrm.otf uses "unstandard" names for the glyphs of the old style
numbers, e.g. oneoldstyle.
This means that the glyphs don't get a tounicode mapping:
\starttext
\pdfvariable compresslevel=0
\font\test={file:cmunrm.otf:mode=node;script=latn;language=DFLT;+onum;}\test
abc123
\stoptext
gives
6 beginbfchar
<0042> <0061>
<0043> <0062>
<0044> <0063>
<0874>
<0875>
<0876>
endbfchar
The names are in glyphtounicode.tex, which contains e.g.
\pdfglyphtounicode{oneoldstyle}{0031}
So it doesn't looks as if they were completly unusual. Would it be
possible to add tounicode mappings for these name?
And how can one declare mappings for really unusual names?
--
Ulrike Fischer
https://www.troubleshooting-tex.de/
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
[NTG-context] variable fonts
In https://mailman.ntg.nl/pipermail/ntg-context/2017/088343.html is some code to use variable fonts. I don't have the fonts but tried it (in a current context mkiv) with "bahnschrift" instead which as far as I could find out should be a variable font too, but can't see any effect. Is the code still meant to work? -- Ulrike Fischer https://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] Pb with tikz, \pdfsavepos and friends
Am Tue, 10 Sep 2019 20:04:58 +0200 schrieb Hans Hagen: >> I checked the pgf versions in my ConTeXt installations from 20180913 and >> 20190909, they are the same : 3.0.1. So I suppose that the change comes from >> ConTeXt itself, that’s why I report the problem here. > ok, for now i'll add these as aliases but savepos is not really related > to pdf (in luatex) tikz/pgf knows about \savepos and does it correctly with lualatex. So I would suggest a bug report at https://github.com/pgf-tikz/pgf. -- Ulrike Fischer https://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] tikz problem with fontsize
Am Sun, 1 Sep 2019 13:05:10 +0200 schrieb Hans Hagen: > what is \coordinate supposed to do: it stores a coordinate under a name. And it works fine for me (I would have been quite surprised if not): \usemodule[tikz] \starttext \starttikzpicture \coordinate (a) at (1,1); \coordinate (b) at (2,2); \draw[red,<->](a)--(b); \stoptikzpicture \stoptext -- Ulrike Fischer https://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] some mac fonts do not work correctly
Am Wed, 24 Jul 2019 12:03:07 +0200 schrieb Hans Hagen:
>> Big Caslon Medium [BigCaslon.ttf] ABCDEFGHIJKLM
> I don't have that file.
After number of test rounds we managed to get all fonts (with one
odd exception) working with these values:
BigCaslon.ttf needs {0, 1, 12}, the W*dings*.ttf fonts need {3, 0,
4} and the affected CJK fonts require {0, 3, 12}.
--
Ulrike Fischer
https://www.troubleshooting-tex.de/
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] some mac fonts do not work correctly
Am Wed, 24 Jul 2019 11:04:17 +0200 schrieb Hans Hagen: >> we got a bug report that some (proprietary) mac fonts don't work >> correctly. The reason seem to be that the OpenType cmap format used >> by these fonts isn't supported by the fontloader. >> >> The necessary cmap formats are "platform 0 (Unicode), encoding 1 >> (Unicode 1.1(?)), format 12" and maybe as a fallback "platform 1 >> (Mac), encoding 0 (Roman), format 0". >> >> A test would be >> >> \starttext >> \font\oddfont="Big Caslon Medium" \oddfont A >> \stoptext > what filename ... when i copy ACaslonPro-Regular from a (by now obsolete > and old) mac it seems to work The bug report mentions these filenames: Heiti TC Light [STHeiti Light.ttc](0) 壹貳參肆伍陸柒捌玖拾 Heiti SC Light [STHeiti Light.ttc](1) 汉体书写信息技术标准相容 Heiti TC Medium[STHeiti Medium.ttc](0) 壹貳參肆伍陸柒捌玖拾 Heiti SC Medium[STHeiti Medium.ttc](1) 汉体书写信息技术标准相容 Big Caslon Medium [BigCaslon.ttf] ABCDEFGHIJKLM GB18030 Bitmap [NISC18030.ttf] 汉体书写信息技术标准相容 Webdings [Webdings.ttf] Wingdings [Wingdings.ttf] Wingdings 2[Wingdings 2.ttf] Wingdings 3[Wingdings 3.ttf] LiHei Pro [LiHeiPro.ttf] 壹貳參肆伍陸柒捌玖拾 LiSong Pro [LiSongPro.ttf] 壹貳參肆伍陸柒捌玖拾 STFangsong [STFANGSO.ttf] 汉体书写信息技术标准相容 STXihei[STXIHEI.ttf]汉体书写信息技术标准相容 STHeiti[STHEITI.ttf]汉体书写信息技术标准相容 Yuanti SC Light[Yuanti.ttc](4) 汉体书写信息技术标准相容 Yuanti SC [Yuanti.ttc](0) 汉体书写信息技术标准相容 Yuanti SC Bold [Yuanti.ttc](2) Imho Marcel only checked the lua and the cmap for Big Caslon. https://github.com/u-fischer/luaotfload/files/3423044/ttx-BigCaslon.txt https://github.com/u-fischer/luaotfload/files/3422873/bigcaslon.lua.zip -- Ulrike Fischer http://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
[NTG-context] some mac fonts do not work correctly
Hello Hans, we got a bug report that some (proprietary) mac fonts don't work correctly. The reason seem to be that the OpenType cmap format used by these fonts isn't supported by the fontloader. The necessary cmap formats are "platform 0 (Unicode), encoding 1 (Unicode 1.1(?)), format 12" and maybe as a fallback "platform 1 (Mac), encoding 0 (Roman), format 0". A test would be \starttext \font\oddfont="Big Caslon Medium" \oddfont A \stoptext (I don't have a mac and so couldn't check) The bug report we got is here https://github.com/u-fischer/luaotfload/issues/73 -- Ulrike Fischer https://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
[NTG-context] luatex-fonts-merged.lua broken?
Hans, we think that luatex-fonts-merged.lua is broken: It contains in line 8594 return characters.indicgroups (from luatex-basics-chr.lua) and such a return statement is a problem in a merged file. -- Ulrike Fischer https://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] Fontloader
Am Sat, 25 May 2019 21:46:46 +0200 schrieb Herbert Voss: > The font LibertinusKeyboard-Regular.otf > https://ctan.org/tex-archive/fonts/libertinus-fonts/ > uses ligatures especially for the keys above 0x > However, I cannot get it run with latest mkiv. as was noticed by Zauguin in https://github.com/u-fischer/luaotfload/issues/60 a work-around it to suppress hyphenation: \font\keyboard=LibertinusKeyboard-Regular.otf:mode=node;+liga \hyphenchar\keyboard=-1 \starttext \keyboard Tab Entf Enter Capslock Windows \stoptext -- Ulrike Fischer https://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
[NTG-context] error in generic fontloader (upvalue 'getglyphdata')
Hans, we think that line 206 and 207 in luatex-basics-nod.lua are faulty and lead to the error attempt to call a nil value (upvalue 'getglyphdata') nuts.getglyphdata= direct.getattr nuts.setglyphdata= direct.setattr should be nuts.getglyphdata= direct.get_attribute nuts.setglyphdata= direct.set_attribute or nuts.getglyphdata= nuts.getattr nuts.setglyphdata= nuts.setattr -- Ulrike Fischer https://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] index "compress" option / collapsing of page numbers
Am Wed, 3 Apr 2019 10:56:21 +0200 schrieb Henning Hraban Ramm: > or is there a need to collapse pages in bibliographies? there can be such page ranges with ff both in the bibliography and the citation. But normally you input them hard coded as you know it in advance (in biblatex as 1\psq or 1\psqq). But biblatex has options to recreate them on-the-fly for backref lists in the bib (and could use the code in more places if needed). -- Ulrike Fischer http://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] follow up
Am Tue, 2 Apr 2019 15:58:18 +0200 schrieb Floris van Manen: >> indeed on preview no x shows up but it does in other viewers >> > > Not just the x. > In the second example the s will disappear, be shows up if you add some extra > digits, and then dropping the 2 I don't have a mac and can't reproduce the problem. But the missing char seems to be always the last one in the beginbfchar/endbfchar list. > The OSX preview is flaky but i’d assume the output of both context version > would be similar (enough) The new context adds new lines inside the beginbfchar/endbfchar block. Perhaps this confuses preview and it drops the last entry. -- Ulrike Fischer http://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] em-dash ligature is converted to en-dash in the generic fontloader
Am Fri, 1 Mar 2019 11:17:56 +0100 schrieb Hans Hagen: > it looks ok in context You need to set automatichyphenmode=0 to see the problem in context: the handling of the --- ligature is clearly broken in some cases: \starttext \automatichyphenmode=0 A---B A --- B \stoptext > Hm, I don't see those lines here I see local tail = getprev(stop) in line 844 of font-ots.lua in a just updated context minimals. If I change this to local tail = stop as suggested by Marcel and rebuild the formats, the ligature behaves again. > (and definitely not in the tex live code freeze window) TeXLive is frozen and pretest has begun, so I don't see a danger to apply patches now. -- Ulrike Fischer http://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] em-dash ligature is converted to en-dash in the generic fontloader
Am Sat, 23 Feb 2019 17:11:12 +0100 schrieb Hans Hagen: > because followed by -- is pretty obscure ... a replace could be > seen as --- and when hyphenated as - -- and such ... it's about time > that texies start using the proper unicode symbols instead of these > funny ligatures well the problem with the proper unicode symbols is that at first they are not so easy to input (that could be handled by the editor) and that they are not so visible. - - — look quite the same in my editor, even more if the screen is not so large and when my eyes tire. If -- wouldn't work I would resort to a command like \ndash instead only to get a better visual clue what's in the document. But regardless from the input method. How can one enable a line break after an em-dash when \automichyphenmode is 1? The only way I found is to explicitly insert a penalty: \starttext \hsize=2pt dash---\penalty1 dash dash—\penalty1 dash \stoptext -- Ulrike Fischer http://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] em-dash ligature is converted to en-dash in the generic fontloader
Am Sat, 23 Feb 2019 15:55:53 +0100 schrieb Hans Hagen: >> As reported on the dev-luatex list --- is converted to an en-dash >> (instead of em-dash) if there are no spaces around the ---. > in context we set: > \automatichyphenmode=1 This solves the problem and after some pondering over the documentation it also looks like a sensible default. But why does \automatichyphenmode=0 suddenly eat a hyphen? -- Ulrike Fischer https://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
[NTG-context] em-dash ligature is converted to en-dash in the generic fontloader
As reported on the dev-luatex list --- is converted to an en-dash
(instead of em-dash) if there are no spaces around the ---.
We could now reproduce the problem also with the generic fontloader:
it appears only with mode=node. I'm using the files from 2019-02-14,
but the problem appeared first in the files from 2018-11-18):
\font\test={file:texgyreheros-regular.otf:+tlig;mode=node;}\test
dashes-these % gives dash
dashes--these % gives en-dash
dashes---these % gives en-dash WRONG
dashes --- these % gives em-dash
em-dashes---these % gives em-dash
\bye
context is not affected, there the code works fine.
--
Ulrike Fischer
https://www.troubleshooting-tex.de/
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] CID set missing with plain fontloader
Am Mon, 11 Feb 2019 12:45:42 +0100 schrieb Hans Hagen: > \pdfvariable omitcidset 1 ouch, how obvious. I should have checked the documentation better. Thanks. -- Ulrike Fischer https://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
[NTG-context] CID set missing with plain fontloader
When I run
\font\test={name:Georgia}
\test
abcx
\bye
with the plain fontloader (similar with luaotfload), and then check
in preflight against the pdf/A-2b or pdf/A-3b I get (beside other
not relevant complaints)
CIDset in subset font is incomplete (font contains glyphs that are
not listed)
The details say additionally (translated): "CID stream contains
*all* CID sets of the embedded font: not true"
If I run with context
\starttext
\font\test={name:Georgia}
\test
abcx
\stoptext
I don't get the complain. What is context doing additionally here? I
don't think that it is a engine problem, I tried also with luatex
1.09.0 and 1.09.2.
--
Ulrike Fischer
http://www.troubleshooting-tex.de/
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
[NTG-context] regression in fontloader?
The following example gave with the generic fontloader from
2018-12-19 and luatex 1.07 two identical lines. With a fontloader
from 2019-01-07 and luatex 1.09 the first line is wrong at the left
side, the "j" is squashed into the next glyph:
\font\test =
{name:FreeSerif:mode=node;script=arab;language=DFLT;+tlig;+ccmp;+locl;+isol;
+fina;
+fin2;+fin3;+medi;+med2;+init;+rlig;+calt;+liga;+cswh;+mset;+curs;+kern;+mark;+mkmk;}
\test
\textdir TRT \pardir TRT \bodydir TRT \pagedir TRT
الإشارات برهن
\hbox{الإشارات برهن}
\bye
--
Ulrike Fischer
https://www.troubleshooting-tex.de/
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] fontloader error in latex: attempt to call upvalue 'getdirection' (a nil value)
Am Fri, 11 Jan 2019 22:51:30 +0100 schrieb Hans Hagen: > afaiks it's ok for luatex 1.09+ Oh, good tipp. You are right with luatex 1.09 it compiles fine. That means that I don't need to debug but should stick to the state of 2018-12-19 until texlive 2019 comes out. -- Ulrike Fischer https://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] fontloader error in latex: attempt to call upvalue 'getdirection' (a nil value)
Am Thu, 10 Jan 2019 17:13:26 +0100 schrieb Pablo Rodriguez: > On 1/7/19 12:40 AM, Ulrike Fischer wrote: >> I just tried to import the fontloader from 2019-01-03 into latex, >> and get on a simple document the error >> >> (./test-utf8.aux)error: >> ...ad/texmf/tex/luatex/luaotfload/fontloader-2019-01-03.lua:23868: >> attempt to call upvalue 'getdirection' (a nil value) >> [...] >> I have no idea (yet) if this is latex specific or if it could affect >> context too but thought I better mention it. The line refers to this >> part of the code: >> >> pardirstate=function(start) >> local nxt=getnext(start) >> local dir=getdirection(start) --<-- >> if dir==lefttoright then >> return nxt,1,1 > > Many thanks for your report, Ulrike. > > This was the same problem that prevented the compilation of the > following code: > > \setupdirections[bidi=on, method=two] > \starttext > \input zapf > \stoptext > > After your report, Hans fixed the issue Well not for generic. I tried yesterday the context state from 2019-01-07 and still have the problem that getdirection is called somewhere but actually nil. But I don't have the time to investigate or to try to create a generic example currently. -- Ulrike Fischer https://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
[NTG-context] fontloader error in latex: attempt to call upvalue 'getdirection' (a nil value)
I just tried to import the fontloader from 2019-01-03 into latex,
and get on a simple document the error
(./test-utf8.aux)error:
...ad/texmf/tex/luatex/luaotfload/fontloader-2019-01-03.lua:23868:
attempt to call upvalue 'getdirection' (a nil value)
.
\newpage ...k \@nobreakfalse \everypar {}\fi \par
\ifdim \prevdepth
>\z@ \vs...
l.51 \end{document}
I have no idea (yet) if this is latex specific or if it could affect
context too but thought I better mention it. The line refers to this
part of the code:
pardirstate=function(start)
local nxt=getnext(start)
local dir=getdirection(start) --<--
if dir==lefttoright then
return nxt,1,1
--
Ulrike Fischer
https://www.troubleshooting-tex.de/
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
[NTG-context] unicode table in the fontloader
Since 29.11 l-unicode.lua disables the slnunicode library with unicode = nil Functions from unicode.utf8 are used in various packages (latex and plain). They are documented in the luatex manual. Simply disabling them is not really an option for us. As we import l-unicode.lua through the lualibs package, this means that I currently have to revert the change manually. Would it be possible to disable the table only in context? Side question: are there any plans to remove the library from the binary? -- Ulrike Fischer https://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] font-ocl.lua:76: attempt to call a nil value (field 'register')
Am Thu, 22 Nov 2018 14:46:57 +0100 schrieb luigi scarso: >> >> A palette entry index value of 0x is a special case indicating >> that the text foreground color (defined by a higher-level client) >> should be used and shall not be treated as actual index into CPAL >> ColorRecord array. >> >> > " the text foreground color (defined by a higher-level client) > should be used" doesn't mean "you MUST take the current color > text" or even "you MUST use black" In fact "defined by a > higher-level client" means that I could define a palette such > that each glyph marked with 0x has its own color based on my > palette --- not necessarily the *same* color. Sounds as if there is some room for interpretation ;-). But assume that I want in my example the 0x to be interpretated as "the current text color", so the currently blue glyphs should be black, and if I add \color[red] before the text they should be red. Can and if yes how this be setup? (Both in context and in generic) -- Ulrike Fischer http://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] font-ocl.lua:76: attempt to call a nil value (field 'register')
Am Thu, 22 Nov 2018 13:50:08 +0100 schrieb Hans Hagen: >> When I use this definitions I still get partly blue glyphs with this >> preamble. Don't you get them? > well, i don't know what to expect Khaled mentioned this link which shows how (harfbuzz-based) browsers like firefox interpret the font https://www.amirifont.org/fatiha-colored.html Also the spec https://docs.microsoft.com/en-us/typography/opentype/spec/colr#layer-record says A palette entry index value of 0x is a special case indicating that the text foreground color (defined by a higher-level client) should be used and shall not be treated as actual index into CPAL ColorRecord array. ==== -- Ulrike Fischer http://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] font-ocl.lua:76: attempt to call a nil value (field 'register')
Am Wed, 21 Nov 2018 20:37:29 +0100 schrieb luigi scarso: > \definefontfeature[quran][mode=node,language=dflt,script=arab, > init=yes,medi=yes,fina=yes,isol=yes, >ccmp=yes,locl=yes,calt=yes, >liga=yes,clig=yes,dlig=yes,rlig=yes, >mark=yes,mkmk=yes,kern=yes,curs=yes, > colr=yes] > \definefont[quran][AmiriQuranColored*quran @ 18pt] > > I have just copied-and- pasted an example around, but > at least the "black-and-white" typography match. When I use this definitions I still get partly blue glyphs with this preamble. Don't you get them? -- Ulrike Fischer https://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] font-ocl.lua:76: attempt to call a nil value (field 'register')
Am Wed, 21 Nov 2018 18:46:44 +0100 schrieb Hans Hagen:
> I'm not sure what yoy mwan with 0x as that's intercepted
With this example (font from
https://github.com/alif-type/amiri/blob/master/AmiriQuranColored.ttf)
a part of the glyphs are in blue. Khaled claims that this is wrong,
that the blue should be black, and the output look like this
https://i.stack.imgur.com/gpoO7.jpg
(sorry about the ^^, it is a translation from a plain example):
\starttext
\definefontfeature[quran][script=arab,colr=yes]
\definefont[quran][AmiriQuranColored*quran @ 20pt]
\catcode`\^=7
\pardir TRT\textdir TRT
\quran
\baselineskip=2.6em
\parindent=0pt
\leftskip=0pt plus 1fil
\rightskip=0pt plus -1fil
\parfillskip=0pt plus 2fil
\def\aya#1{{\textdir TLT 06dd#1}}
fdfd~\aya{١}\par
ٱلۡحَمۡدُ لِلَّهِ رَبِّ ٱلۡعَٰلَمِینَ~\aya{٢} ٱلرَّحۡمَٰنِ
ٱلرَّحِیمِ~\aya{٣} مَٰلِكِ یَوۡمِ ٱلدِّینِ~\aya{٤} إِیَّاكَ نَعۡبُدُ
وَإِیَّاكَ نَسۡتَعِینُ~\aya{٥} ٱهۡدِنَا ٱلصِّرَٰطَ
ٱلۡمُسۡتَقِیمَ~\aya{٦} صِرَٰطَ ٱلَّذِینَ أَنۡعَمۡتَ عَلَیۡهِمۡ
غَیۡرِ ٱلۡمَغۡضُوبِ عَلَیۡهِمۡ وَلَا ٱلضَّاۤلِّینَ~\aya{٧}\par
\stoptext
--
Ulrike Fischer
http://www.troubleshooting-tex.de/
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] font-ocl.lua:76: attempt to call a nil value (field 'register')
Am Wed, 21 Nov 2018 13:01:47 +0100 schrieb Ulrike Fischer: > Khaled wrote that "is that [the code] uses the last palette color A bit too much deleted. It should say "it is a bug that ..." -- Ulrike Fischer http://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
[NTG-context] font-ocl.lua:76: attempt to call a nil value (field 'register')
I tried to register a demo colorpalette:
\starttext
\directlua{fonts.handlers.otf.registerpalette("demo", {
{ g=1 }, %accents
{ b=1 }, %06dd
{ r=0.5, g=0.5, b=0.5 }, %unused?
{ g = 0.5, b=0, r=1 },
}
)}
blub
\stoptext
and got the error
font-ocl.lua:76: attempt to call a nil value (field 'register')
(I wanted to test the coloring of
https://github.com/alif-type/amiri/blob/master/AmiriQuranColored.ttf,
Khaled wrote that "is that [the code] uses the last palette color
for layers using paletteIndex 0x (special value that means use
text color)." and that
local default = colorvalues[#colorvalues]
font-ocl.lua is faulty)
--
Ulrike Fischer
http://www.troubleshooting-tex.de/
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] improving kannada script
Am Fri, 2 Nov 2018 12:53:02 +0100 schrieb luigi scarso: >> You could try https://github.com/khaledhosny/luahbtex. Khaled is >> trying to marry luatex + harfbuzz there > sure, it's hardcoded , the final binary is quite heavy ... > Anyway, I am talking of dll/so plugin and tool, > it's more on the track of > https://www.guitex.org/home/images/ArsTeXnica/AT023/luaffi-article.pdf Well we (some of the latex team) tried to test this as we have quite an interest to have an option to use harfbuzz for some fonts but not every code needed seems to be available publicitly. Also if I remember correctly this requires --shell-escape and this is not really sensible for a user interface. -- Ulrike Fischer http://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] improving kannada script
Am Fri, 2 Nov 2018 11:56:52 +0100 schrieb luigi scarso: > I am planning to play with a harfbuzz plugin to check them (sort of tool) You could try https://github.com/khaledhosny/luahbtex. Khaled is trying to marry luatex + harfbuzz there (I couldn't try it yet due to missing windows binaries). -- Ulrike Fischer http://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] improving kannada script
Am Wed, 31 Oct 2018 16:01:37 +0100 schrieb Hans Hagen: > fyi, there will be an update for some set set of indic script later this > year (most is done but it all relates to available time of those involved) That's good news. I got quite a list of probably broken scripts: https://tex.stackexchange.com/a/457459/2388 (But I couldn't check yet for most of them, if it is a fontloader or a luaotfload problem and if the newest version solves some of the problems, deva e.g. should be already better). -- Ulrike Fischer http://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
[NTG-context] improving kannada script
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/
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] devanagari is missing an accent in newest beta
Am Fri, 19 Oct 2018 11:36:48 +0200 schrieb Arthur Reutenauer: >> Screenshots and code that show the difference and the missing accent >> in the xelatex and context output are in this comment >> https://github.com/u-fischer/luaotfload/issues/9#issuecomment-431288932 >> the older (perfect) output is in a comment above >> https://github.com/u-fischer/luaotfload/issues/9#issuecomment-426978522 > > The missing “accent” is a repha, a form of the consonant ra. It seems > to have been replaced by a middle dot, to the right of the base > consonant. I can’t be completely sure because it’s protruding into the > next consonant so it’s almost indistinguishable from it, but I think > that’s what happened. Yes, good catch. there is a dot. But I'm wondering if I saw ghosts when thinking that it worked before. I can't find no commit which changes to the "right" output and also in a older context it is wrong. -- Ulrike Fischer http://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
[NTG-context] devanagari is missing an accent in newest beta
Disclaimer: I know nothing about devanagari, I can only describe changes visually ... I installed yesterday the newest context, and one of my examples of devanagari is now missing an "accent". I'm rather confident that the output was different before the update as I made screenshots when testing this with luaotfload. The affected font siddhanta can be found here http://svayambhava.blogspot.com/p/siddhanta-devanagariunicode-open-type.html Screenshots and code that show the difference and the missing accent in the xelatex and context output are in this comment https://github.com/u-fischer/luaotfload/issues/9#issuecomment-431288932 the older (perfect) output is in a comment above https://github.com/u-fischer/luaotfload/issues/9#issuecomment-426978522 -- Ulrike Fischer https://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] what defines the font size?
Am Tue, 16 Oct 2018 09:07:38 +0200 schrieb Arthur Reutenauer: > I quite liked the idea of the font itself deciding on its size, of its > own free will ;-) ;-) That's an application of Gödel's incompleteness theorems: with some level of complexity and lookups strange loops und true but unproveable statements about the font appear and then it clearly has its how free will. Or shorter: you no longer can really understand what it is doing ... -- Ulrike Fischer http://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] what defines the font size?
Am Mon, 15 Oct 2018 21:21:32 +0200 schrieb Pablo Rodriguez: > Dear list, > > sorry for this basic question, but what defines the size in a font? > > I mean, we can take TeX Gyre Bonum and TeX Gyre Adventor at twelve > points. x-height is different, M-width is slightly different. > > I thought it was the same A-height, but it isn’t. > > If two fonts have the same size, I think there may be a dimension which > has the same length in both. Which one is this? None. The font decides about its size. -- Ulrike Fischer https://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] Font Awesome (again)
Am Sun, 7 Oct 2018 09:26:11 -0400 (EDT) schrieb Aditya Mahajan: > Would it make sense to update the fonts in the distribution? I didn't quite follow the discussion and the suggested code, but from a similar discussion for latex I know that the symbols in fontawesome 4 and 5 looks different (that's why there is an explicit fontawesome5 package in latex). -- Ulrike Fischer https://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
[NTG-context] \enabletrackers[*] gives lua error.
I tried to look at a font and enabled the trackers like this \enabletrackers[*] \definefont [test][name:texgyreheros] \starttext abcäöü \stoptext The context compilations fails then with ...ext/tex/texmf-context/tex/context/base/mkiv/font-oup.lua:718: attempt to call a nil value (global 'report_unicode') Imho around a week ago (when I asked about the source han font) this worked. -- Ulrike Fischer https://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] accessing glyphs in the private area
Am Tue, 2 Oct 2018 11:29:46 +0200 schrieb Hans Hagen: >> Can't you check for a free range instead? > sure, but then i also loose some functionality in context (unless i gho > for ugly solutions) ... as all glyphs are supposed to have a name access > by name is a pretty good alternative Well in my view name and code point are both valid and useful accesses (and I wouldn't trust names too much). Beside this: xetex has (for non-legacy fonts) primitives for all accesses: by char (unicode), slot and name. luatex hasn't, here the only (primitive) access are commands like \char which expect a number; the name field of a character is marked as "unused" in the manual. Neither has the generic fontloader imho some suitable primitive command for name access. All the examples in the generic folder uses numbers or direct input: e.g. \Uchar"1D49D or \Uradical "0 "221A So it is imho quite natural that people who write code and packages expect the access by \char + code point to work. Why should I bother with a (perhaps font specific) glyph name if I can simply look up a clear code point number in a table? And if I got it right you are reserving a specific space to have stable numbers internally, so you are caring about numbers too ;-) > the main issue is that there are fonts that use private > 0x space I don't know. Wikipedia says that code2000 uses plane 15 but I didn't check. -- Ulrike Fischer http://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] accessing glyphs in the private area
Am Tue, 2 Oct 2018 06:55:02 +0200 schrieb luigi scarso: >> For what do you reserve the space in the PUA? > http://www.pragma-ade.nl/general/manuals/fonts-mkiv.pdf > page 32 of the document : > As we already mentioned in a previous chapter, in ConTeXt we use > Unicode internally. This also means that fonts are organized this > way. By default the glyph representation of a Unicode character > sits in the same slot in the glyph table. All additional glyphs, > like ligatures or alternates are pushed in the private unicode > space. This is why in the lists shown in the figures the > ligatures have a private Unicode number. Hm. To clarify. In xetex there is clear distinction between the slot and unicode. \XeTeXglyph (slot) and \char (unicode) give different output and \char actively uses the tounicode mapping of the font. \font\test="[lmroman10-regular.otf]" \test \XeTeXglyph"7A \char"7A \bye In luatex \char and \Uchar don't really care about unicode, even if the font has tounicode=1 and tounicode entries, they access the char by the hashed integer number. So to get "unicode" the font loader has to sort the glyphs, index unicode glyphs by their unicode code point, and assign "non-unicode" glyphs numbers that don't interfere. Did I got right? Then I do understand that you need some free numbers to push glyphes. But I do not understand why to achieve this you remove glyphs from their unicode points. The PUA is not some non-unicode wilderness. The code points there are as valid as in the other code blocks. You wouldn't move away the greek block to get the place, so why do you think it is okay to throw out of the PUA block what SIL and other font designers encoded there? Can't you check for a free range instead? -- Ulrike Fischer http://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] accessing glyphs in the private area
Am Mon, 1 Oct 2018 19:29:40 +0200 schrieb Hans Hagen:
>> \DeclareTextGlyphY{LinBiolinum_K}{uniE18C}{57740}
>A funny definition ... is that access by name or number?
By number, it uses \char at the end to get the glyph.
> Anyway, for generic (so not for context) I can keep these glyphs in the
> 0xE000-0xEFFF range for now
That would be great. Thanks.
What about the rest and the other PUA's?
U+F000–U+F8FF, U+F–U+D, U+10–U+10FFFD
And when will the change be available? I will have to update
luaotfload.
> (also the names so larger files ... actually
> a mess as that font has Uni and uni so who's to know).
It is not only that font. Actually the libertine package broke,
fontawesome broke, and Coelacanth was only used by Thérèse in the
example as it is free, her real problem was with using Goudy
fleurons.
The private use area is there for every font to use. And quite often
they document this code points and tools like fontforge show them.
I don't think that it is a good idea if an application comes along
and pushes the glyphs from the seats because it wants the space for
itself.
> I have no clue if it clashes with some features at some point so
> that you can use numbers but probably those features are context
> specific anyway.
For what do you reserve the space in the PUA?
--
Ulrike Fischer
http://www.troubleshooting-tex.de/
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] accessing glyphs in the private area
Am Mon, 1 Oct 2018 10:20:07 +0200 schrieb Hans Hagen:
> anyway, the problem, with these private areas is that they are also used
> by the loader (and context) so in order to avoid clashes we move all
> private chars in the font to a dedicated private range
This basically means that for every document and package which uses
the generic fontloader the access to chars in the private area with
\char is now broken in luatex (in xetex it still works fine).
I just got from Claudio Beccari (which seem to have complained to
Luigi) a bug report that the libertine fonts no longer show some of
the keyboard key glyphs due to the same problem.
Can you tell me when this change happend? Perhaps I can build an
older fontloader as a fall back.
> in your case the glyphs have no real useful names so basically i wonder
> what their use it (are they meant for direct access?)
The question on tex.sx claimed that it has the name uniF58C.
I never used the font and don't know how Therese accessed the glyphs
before, but the libertine package has long lists of mappings like
this:
\DeclareTextGlyphY{LinBiolinum_K}{uniE18C}{57740}
How do context users access such glyphs? Why is there no problem?
> you can define
>
> \def\byindex#1{\ctxlua{
> for k, v in pairs(fonts.hashes.identifiers[true].characters) do
> if v.index == #1 then
> tex.print(utf.char(k))
> break
> end
> end
> }}
>
> {\definedfont[Coelacanth] test \byindex{\number"00A33}}
I don't see a use of accessing this glyphs by index - index
positions can change if the font is updated. This can only be a last
resort for glyphs without unicode position.
The only sensible access is by unicode number (which works).
> I can remap those privates to a normalized private name, like P0F581 but
> it depends on how bloated fonts become that have lots of privates.
>
> In that case you can have:
>
> \def\byname#1{\ctxlua{
> for k, v in
> pairs(fonts.hashes.identifiers[true].shared.rawdata.descriptions) do
> if v.name == "#1" then
> tex.print(utf.char(k))
> break
> end
> end
> }}
>
> {\definedfont[Coelacanth] test \byname {P0F581}}
It would at least mean that not the whole characters list must be
searched. And we could create a documented and stable access
command.
--
Ulrike Fischer
http://www.troubleshooting-tex.de/
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
[NTG-context] accessing glyphs in the private area
The font Coelacanth (on CTAN) has glyphs in the private area.
Between 2/2017 (luaotfload in texlive 2017) and now the storing and
accessing of this glyphs has changed.
In the lua of the font of 2017 I find e.g.
[62860]={
["boundingbox"]=165,
["index"]=2622,
["unicode"]=62860,
["width"]=523,
and the glyph can be accessed with \Uchar62860
In the current lua I now find
[983910]={
["boundingbox"]=195,
["index"]=2622,
["unicode"]=62860,
["width"]=523,
},
and \Uchar62860 not longer works, one has to use \Uchar983910.
Is this change intentional? How is one supposed to access such
chars? The manual says about \Uchar that it "expands to the
associated Unicode character." but this seems no longer to be true.
A context example to test is
\starttext
\font\test={name:Coelacanth:mode=node;script=latn;language=DFLT;+tlig;}
\test
1.: \Uchar62860
2.: \Uchar983910
\stoptext
The question was triggered by this tex.sx question
https://tex.stackexchange.com/questions/453224/using-glyphs-in-the-corporate-use-or-microsoft-symbol-areas
https://github.com/u-fischer/luaotfload/issues/7
--
Ulrike Fischer
https://www.troubleshooting-tex.de/
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] remapper change in luatex-basics-gen.lua
Am Sun, 30 Sep 2018 01:20:48 +0200 schrieb Hans Hagen: >> This is new compared to the state in 2/2017 > which is quite a while ago ... Yes. But I'm currently the maintainer of luaotfload and plan to sync more regularly. > hm, isn't latex using kpse ? in generic this resolver is just for fonts Yes, latex is using kpse and the resolver in generic is using it too. But the pgf code is doing something like if resolver then resolver.findfile ... else kpse ... end Imho (and after a night's sleep) I think that they meant something like if context then resolver.findfile ... else kpse ... end and I will suggest them to change their code accordingly. -- Ulrike Fischer https://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
[NTG-context] remapper change in luatex-basics-gen.lua
in luatex-basics-gen.lua
the remapper maps lua to "tex":
local remapper = {
otf= "opentype fonts",
ttf= "truetype fonts",
ttc= "truetype fonts",
cid= "cid maps",
cidmap = "cid maps",
-- fea= "font feature files", -- no longer supported
pfb= "type1 fonts",-- needed for vector loading
afm= "afm",
enc= "enc files",
lua= "tex", --<<<<<<http://minimals.contextgarden.net/current/modules/t-tikz/tex/generic/pgf/graphdrawing/tex/pgflibrarygraphdrawing.code.tex)
Due to the mapping of lua to the tex type
resolvers.findfile("layered","lua") no longer finds layered.lua.
Apart from telling the pgf people not to use resolvers.findfile like
this when latex is used, is there anything one could do in the
generic fontloader?
--
Ulrike Fischer
https://www.troubleshooting-tex.de/
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
[NTG-context] open type feature "frac"
Due to a question on tex.sx
(https://tex.stackexchange.com/questions/452969/luatex-fontfeaturefractions-on-turns-first-digits-into-superscripts)
I looked again (see
https://www.mail-archive.com/ntg-context@ntg.nl/msg84822.html) at
the frac feature.
The output is still not really satisfactory. With mode=node numbers
with slash looks okay, but single numbers are rather odd: only the
last digit has the correct size:
\starttext
\font\test={file:linlibertine_r.otf:mode=node;script=latn;language=DFLT;+frac}
\test
787347 125
1/7 1/2 3/4 5/6 7/8 9/10 11/12 31415/27182 1000/100
\font\test={file:linlibertine_r.otf:mode=base;script=latn;language=DFLT;+frac}
\test
787347 125
1/7 1/2 3/4 5/6 7/8 9/10 11/12 31415/27182 1000/100
\stoptext
(It could be a font bug, the output with xetex isn't good either).
--
Ulrike Fischer
https://www.troubleshooting-tex.de/
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] tounicode mapping missing for locl-variants
Am Thu, 27 Sep 2018 10:25:51 +0200 schrieb Hans Hagen: > these glyphs have no names Side remark: if you think that the font is wrong here I could add a comment on the github site. -- Ulrike Fischer http://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] tounicode mapping missing for locl-variants
Am Thu, 27 Sep 2018 10:25:51 +0200 schrieb Hans Hagen: >> What can one do to get a mapping also for the other glyphs? > > wait till i update ... Thanks. Will it be also in the generic fontloader? -- Ulrike Fischer http://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] tounicode mapping missing for locl-variants
Am Thu, 27 Sep 2018 09:55:02 +0200 schrieb luigi scarso: > ok, then you can see the font as seen by context > mtxrun --script fonts --convert SourceHanSans-Regular.otf > (keep track also of its output ) That is the output of the mtxrun call: https://www.dropbox.com/s/xszihzv21snxdiv/contextmtx.log?dl=0 -- Ulrike Fischer http://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] tounicode mapping missing for locl-variants
Am Thu, 27 Sep 2018 09:14:01 +0200 schrieb luigi scarso:
> On Wed, Sep 26, 2018 at 11:14 PM Ulrike Fischer wrote:
>
>>
>> When I compile the following document I see in the output localized
>> variants for the various glyphs. But copy & paste works only for the
>> last line. The first two gives notdef chars.
>>
>> In the pdf e.g. the first glyph has the numbers 2D0E, 2D0F, 2D0D in
>> the three lines but only for the last there is a unicode mapping:
>> <2D0D> <5203>.
>>
>> What can one do to get a mapping also for the other glyphs?
>>
>> The font can be downloaded here
>>
>> https://github.com/adobe-fonts/source-han-sans/blob/release/OTF/SourceHanSansJ.zip
>> A related bug report is
>> https://github.com/adobe-fonts/source-han-sans/issues/200
>>
>>
>> \pdfvariable compresslevel 0
>> \pdfvariable objcompresslevel 0
>> \setupheader[state=stop]
>>
>
>
>
>> \starttext
>>
>> \font\zhs=
>> {file:SourceHanSans-Regular.otf:mode=node;script=hani;language=ZHS;+locl}
>> \zhs 刃令毒骨縣誤
>>
>> \font\zht=
>> {file:SourceHanSans-Regular.otf:mode=node;script=hani;language=ZHT;+locl}
>> \zht 刃令毒骨縣誤
>>
>> \font\test=
>> {file:SourceHanSans-Regular.otf:mode=node;script=hani;language=DFLT;}
>> \test 刃令毒骨縣誤
>>
>> \stoptext
>>
>>
>>
> what does the trackers say at your end ?
> \enabletrackers[*]
> \nopdfcompression
> [...]
a lot ;-)
https://www.dropbox.com/s/jgwvytl7hi2doi5/test-utf8.log?dl=0
One can see how the glyphs are replaced under locl:
fonts > otf direct > feature 'locl', type 'gsub_single',
lookup 's_s_42': replacing U+5203 by single U+F0608
but I can find nothing about tounicode/cmap or something like that.
--
Ulrike Fischer
http://www.troubleshooting-tex.de/
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
[NTG-context] tounicode mapping missing for locl-variants
When I compile the following document I see in the output localized
variants for the various glyphs. But copy & paste works only for the
last line. The first two gives notdef chars.
In the pdf e.g. the first glyph has the numbers 2D0E, 2D0F, 2D0D in
the three lines but only for the last there is a unicode mapping:
<2D0D> <5203>.
What can one do to get a mapping also for the other glyphs?
The font can be downloaded here
https://github.com/adobe-fonts/source-han-sans/blob/release/OTF/SourceHanSansJ.zip
A related bug report is
https://github.com/adobe-fonts/source-han-sans/issues/200
\pdfvariable compresslevel 0
\pdfvariable objcompresslevel 0
\setupheader[state=stop]
\starttext
\font\zhs=
{file:SourceHanSans-Regular.otf:mode=node;script=hani;language=ZHS;+locl}
\zhs 刃令毒骨縣誤
\font\zht=
{file:SourceHanSans-Regular.otf:mode=node;script=hani;language=ZHT;+locl}
\zht 刃令毒骨縣誤
\font\test=
{file:SourceHanSans-Regular.otf:mode=node;script=hani;language=DFLT;}
\test 刃令毒骨縣誤
\stoptext
--
Ulrike Fischer
https://www.troubleshooting-tex.de/
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] Using the source han sans fonts fails
Am Wed, 19 Sep 2018 13:50:37 +0200 schrieb Ulrike Fischer: > I guess I should reinstall context here, probably it is too old and > never got the 64bit binaries. I did reinstall context and now a 64bit luatex is used on my pc too and the problem is gone. I also installed a 64bit luatex for texlive and now the font can also be used with latex. The first time for me that a 64bit application makes really a difference ;-). -- Ulrike Fischer http://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] Using the source han sans fonts fails
Am Wed, 19 Sep 2018 13:22:40 +0200 schrieb Hans Hagen: >> Is there one for context minimals? And if yes, how could I install >> and activate it? > when you install the context distribution from the garden it should load 64 It doesn't on my PC, there is only a texmf-mswin, but I checked on another and there I have a texmf-mswin64, and my example compiles. I guess I should reinstall context here, probably it is too old and never got the 64bit binaries. -- Ulrike Fischer http://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] Using the source han sans fonts fails
Am Wed, 19 Sep 2018 11:36:40 +0200 schrieb Taco Hoekwater: > Note, however, that the luatex process tops out at nearly 3GB RAM > use while generating the cached version, which could be a problem > on 32-bit operating systems. I have a 64bit OS and 8GB RAM. According to the task manager luatex itself is 32bit. Are you using a 64bit luatex? Is there one for context minimals? And if yes, how could I install and activate it? -- Ulrike Fischer http://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] Using the source han sans fonts fails
Am Wed, 19 Sep 2018 10:54:08 +0200 schrieb Hans Hagen:
> On 9/19/2018 10:24 AM, Ulrike Fischer wrote:
>>
>> Because of a question on tex.sx I tried to use the source han sans
>> fonts. I installed (in windows 10) the fonts from this zip-file:
>>
>> https://github.com/adobe-fonts/source-han-sans/blob/release/OTF/SourceHanSansJ.zip
>>
>> Trying to use them with latex/luaotfload failed with a memory
>> exhausted error while trying to write the lua-file. In context
>>
>> \starttext
>> \font\test={name:sourcehansans}
>> \test abc
>> \stoptext
>>
>> gave the error:
>>
>> fonts > otf loading > loading
>> 'c:/windows/fonts/SourceHanSans-Regular.otf', hash
>> 'sourcehansans-regular'
>> otf reader > loading of table 'vorg' skipped
>> otf reader > invalid index in single format 1: 65353 -> 67212
>> (max 65535)
>> otf reader > rule 1 in gsub lookup 's_s_5' has empty lookups
>> fonts > otf loading > loading failed due to read error
>> fonts > defining > forced type 'otf' of
>> 'c:/windows/fonts/SourceHanSans-Regular' not found
>> fonts > defining > font with asked name
>> 'c:/windows/fonts/SourceHanSans-Regular' is not found using lookup
>> 'name'
>> fonts > defining > unknown font
>> 'c:/windows/fonts/SourceHanSans-Regular', loading aborted
>>
>>
>> xelatex had no problems to use the font.
>>
>> Is this an error in the font or in the fontloader?
> it works ok here with luatex
>
> but ... do you use luajittex?
No (neither with lualatex).
The context log says at the end:
mkiv lua stats > used platform: mswin, type: windows, binary
subtree: texmf-mswin
mkiv lua stats > used engine: luatex version 1.09 with
functionality level 6930, banner: this is luatex, version 1.09.0
(tex live 2018/w32tex)
mkiv lua stats > control sequences: 45351 of 65536 + 10
mkiv lua stats > lua properties: engine: lua 5.3, used memory: 1519
MB (ctx: 1460 MB), hash type: lua, hash chars: min(32,40), symbol
mask: utf (τεχ)
mkiv lua stats > runtime: 39.711 seconds
The fonts *are* large, and my computer is quite old, so it could be
a hardware problem, but I'm wondering a bit about the message
> otf reader > invalid index in single format 1: 65353 -> 67212
--
Ulrike Fischer
http://www.troubleshooting-tex.de/
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
[NTG-context] Using the source han sans fonts fails
Because of a question on tex.sx I tried to use the source han sans
fonts. I installed (in windows 10) the fonts from this zip-file:
https://github.com/adobe-fonts/source-han-sans/blob/release/OTF/SourceHanSansJ.zip
Trying to use them with latex/luaotfload failed with a memory
exhausted error while trying to write the lua-file. In context
\starttext
\font\test={name:sourcehansans}
\test abc
\stoptext
gave the error:
fonts > otf loading > loading
'c:/windows/fonts/SourceHanSans-Regular.otf', hash
'sourcehansans-regular'
otf reader > loading of table 'vorg' skipped
otf reader > invalid index in single format 1: 65353 -> 67212
(max 65535)
otf reader > rule 1 in gsub lookup 's_s_5' has empty lookups
fonts > otf loading > loading failed due to read error
fonts > defining > forced type 'otf' of
'c:/windows/fonts/SourceHanSans-Regular' not found
fonts > defining > font with asked name
'c:/windows/fonts/SourceHanSans-Regular' is not found using lookup
'name'
fonts > defining > unknown font
'c:/windows/fonts/SourceHanSans-Regular', loading aborted
xelatex had no problems to use the font.
Is this an error in the font or in the fontloader?
--
Ulrike Fischer
http://www.troubleshooting-tex.de/
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] question about German hyphenation
Am Sun, 26 Aug 2018 17:26:45 +0200 schrieb Pablo Rodriguez:
> Dear list,
>
> I have the following sample:
>
> \starttext
> \de\hyphenatedword{Rindfleisch}
> \de\hyphenatedword{Rindfleischetikettierung}
> \stoptext
>
> I’m not a native speaker, but I think that "Rindfleisch-etikettierung"
> is right in German. (And I think that "Rindflei-schetikettierung" is wrong.)
>
Yes it is wrong. Correct hyphenation points are
Rind-fleisch-e-ti-ket-tie-rung
> Are the hyphenation patterns wrong in the cases above, or am I missing
> something?
That's difficult to do right with patterns, in latex it is isn't
correct either. The problem is that two words have been combined.
(Rindfleisch and Etikettierung).
--
Ulrike Fischer
https://www.troubleshooting-tex.de/
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] fontloader fails with "bad argument #1 to 'for iterator"
Am Sat, 18 Aug 2018 13:47:32 +0200 schrieb Hans Hagen: >> On the luaotfload tracker was a bug report that the loading of a >> font failed if too many character variant were requested >> >> https://github.com/lualatex/luaotfload/issues/424 >> >> I wanted to check if the problem still exist with a current >> fontloader. Here (both context and latex) the loading of this fonts >> fails even if no character variants at all are requested: > What are character variants? Anyway, if it's "features" there is no > relation between choosing features and loading a font. As far as I got it they are open type features to select variants of characters and are used as any other open type feature: ;+cv01=0;+cv02=0;+cv03=0;+cv04=0;+cv05=0;+cv06=0;... In the bug report the problem seemed to be that the user used so many of this features that some string got too long. But due to the other error I couldn't look at it yet. >> it is in the 07-iosevka-type-slab-2.0.0.zip. > Hm, another of these N x M instance fonts generated from a common > source? I can catch the bad coverage table but it will never render okay. Thanks. And I will forwared the warning ;-). -- Ulrike Fischer https://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
[NTG-context] fontloader fails with "bad argument #1 to 'for iterator"
On the luaotfload tracker was a bug report that the loading of a
font failed if too many character variant were requested
https://github.com/lualatex/luaotfload/issues/424
I wanted to check if the problem still exist with a current
fontloader. Here (both context and latex) the loading of this fonts
fails even if no character variants at all are requested:
\starttext
\font\x={file:iosevka-type-slab-regular.ttf}
\x
ablub
\stoptext
gives
...ext/tex/texmf-context/tex/context/base/mkiv/font-oup.lua:2137:
bad argument #1 to 'for iterator' (table expected, got nil)
The font can be get from
https://github.com/be5invis/Iosevka/releases
it is in the 07-iosevka-type-slab-2.0.0.zip.
--
Ulrike Fischer
https://www.troubleshooting-tex.de/
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] faulty to unicode mapping of chars encoded with surrogate pairs?
Am Wed, 8 Aug 2018 14:15:41 +0200 schrieb Hans Hagen: > line 228 in font-map should be: > > k = k - 0x1 > > (not v = ...) Thanks, that corrects the problem. -- Ulrike Fischer http://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
[NTG-context] faulty to unicode mapping of chars encoded with surrogate pairs?
when I compile the following with context \pdfvariable compresslevel=0 \starttext $f$ \stoptext I get in the pdf 1 beginbfchar <0515> endbfchar D875DC53 is according to http://www.russellcottrell.com/greek/utilities/surrogatepaircalculator.htm the codepoint 2D453 and this is not a valid unicode point. As a result copy& paste doesn't work correctly. A similar example with xelatex writes D835DC53 (remark the 3 instead of the 7) instead in the pdf which gives the correct code point 1D453 and copies fine. lualatex gives the faulty value too. -- Ulrike Fischer http://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] newest beta: luatex-fonts-merged.lua missing
Am Thu, 12 Jul 2018 11:23:48 +0200 schrieb Hans Hagen: >> ...xt/tex/texmf-context/scripts/context/lua/mtx-package.lua:80: >> attempt to perform arithmetic on global 'striped' (a nil value) > > striped -> stripped So you stripped a p too much ;-). I corrected this locally and it worked fine. -- Ulrike Fischer http://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
[NTG-context] newest beta: luatex-fonts-merged.lua missing
In the newest beta from 10. july luatex-fonts-merged.lua is missing in the generic fontloader folder. I tried to create it with the command mentioned in luatex-fonts-lua mtxrun --script package --merge --stripcontext luatex-fonts.lua But I got an error: ...xt/tex/texmf-context/scripts/context/lua/mtx-package.lua:80: attempt to perform arithmetic on global 'striped' (a nil value) Removing the -stripcontext worked: mtxrun --script package --merge luatex-fonts.lua -- Ulrike Fischer http://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] beta
Am Sat, 23 Jun 2018 12:12:05 +0200 schrieb Hans Hagen:
> don't use register split in luaotfload ... look in luatex-fonts.lua etc
> to soo how to analyze the name .. splitters are something context specific
It looks as if we managed to get it working in luaotfload.
We are trying to setup test files. But normalization of the
log-files are complicate as the fontloader uses in various places
texio.write. E.g texio.write(format("(load luc: %s)",lucname))
Would it be possible to change this to some log-function which could
be adapted for the tests (so that e.g. newlines could be inserted
and the path stripped from file names)?
--
Ulrike Fischer
http://www.troubleshooting-tex.de/
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] beta
Am Fri, 22 Jun 2018 17:30:46 +0200 schrieb Wolfgang Schuster: >> ...est/tex/texmf-context/tex/context/base/mkiv/grph-inc.lua:1398: >> image.ownerpassword can not be set >> stack traceback: > Do you get the same error message with the following minimal example: I get the same error after the update with \starttext \externalfigure[A] \stoptext where A.pdf is in the current folder. I'm on windows 10. -- Ulrike Fischer http://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] beta
Am Fri, 22 Jun 2018 16:09:26 +0200 schrieb Hans Hagen: > I uploaded a beta (with an seeindex fix). I still get an error about a missing function registersplit when using the new generic loader together with luaotfload. Looking at the code I can see that there is an "if context" switch around the relevant part (around line 34058): definers.makespecification=makespecification if context then --<<<<<<<<< local splitter,splitspecifiers=nil,"" ... Removing this (and the "end" naturally) then it worked fine. -- Ulrike Fischer http://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] font pathes with colons
Am Sun, 10 Jun 2018 13:24:40 +0200 schrieb Hans Hagen: > i changed the parser for generic a bit so you need to check careful next > beta as i'm only testing some basic plain loading I found something else that changed: The otf-handler registerpalette is gone, and so coloring of fonts like in the following answer no longer works: https://tex.stackexchange.com/a/387069/2388 (I don't have the time now to test it in the plain-tex version.) -- Ulrike Fischer http://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] font pathes with colons
Am Sun, 10 Jun 2018 13:24:40 +0200 schrieb Hans Hagen:
> i changed the parser for generic a bit so you need to check careful next
> beta as i'm only testing some basic plain loading
It broke ;-(
luaotfload complained about a missing registersplit,
then about a missing addspecifier, so I reinserted from the previous
version (from UF to /UF) (around line 32865)
local resolvefile=fontgoodies and fontgoodies.filenames and
fontgoodies.filenames.resolve or function(s) return s end
-- UF
local splitter,splitspecifiers=nil,""
local P,C,S,Cc,Cs=lpeg.P,lpeg.C,lpeg.S,lpeg.Cc,lpeg.Cs
local left=P("(")
local right=P(")")
local colon=P(":")
local space=P(" ")
local lbrace=P("{")
local rbrace=P("}")
definers.defaultlookup="file"
local prefixpattern=P(false)
local function addspecifier(symbol)
splitspecifiers=splitspecifiers..symbol
local method=S(splitspecifiers)
local lookup=C(prefixpattern)*colon
local sub=left*C(P(1-left-right-method)^1)*right
local specification=C(method)*C(P(1)^1)
local
name=Cs((lbrace/"")*(1-rbrace)^1*(rbrace/"")+(1-sub-specification)^1)
splitter=P((lookup+Cc(""))*name*(sub+Cc(""))*(specification+Cc("")))
end
local function addlookup(str,default)
prefixpattern=prefixpattern+P(str)
end
definers.addlookup=addlookup
addlookup("file")
addlookup("name")
addlookup("spec")
local function getspecification(str)
return lpegmatch(splitter,str or "")
end
definers.getspecification=getspecification
function definers.registersplit(symbol,action,verbosename)
addspecifier(symbol)
variants[symbol]=action
if verbosename then
variants[verbosename]=action
end
end
-- /UF
Then it complained about a missing upvalue getthreshold so I
reinserted:
local getthreshold
--UF
injections.threshold=0
getthreshold=function(font)
local p=fontdata[font].parameters
local f=p.factor
local s=p.spacing
local t=injections.threshold*(s and s.width or p.space or 0)-2
return t>0 and t or 0,f
end
--/UF
Now it works again and also the "unknown option" warning is gone.
> i have no clue how otfload locates files but maybe you need to add an
> entry to
>
> local remapper = {
> otf= "opentype fonts",
> ttf= "truetype fonts",
> ttc= "truetype fonts",
> cid= "cid maps",
> cidmap = "cid maps",
> -- fea= "font feature files", -- no longer supported
> pfb= "type1 fonts",-- needed for vector loading
> afm= "afm",
> enc= "enc files",
> lua= "tex", -- LIKE THIS
> }
lua= "misc fonts",
would be better (then one can put the fonts in fonts/misc.
But it doesn't help with the main problem that luaotfload calls
resolvers.findfile first for "basename + otf, tfm, ofm", then
triggers a rebuild of the database and only then calls
resolvers.findfile again with the fullname.
Also I really want to avoid to patch the merged code. I'm regularly
getting the newest version from context and try out if it still
works and prefer if I can use them unchanged.
--
Ulrike Fischer
http://www.troubleshooting-tex.de/
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] font pathes with colons
Am Sun, 10 Jun 2018 12:42:25 +0200 schrieb Hans Hagen:
>> Thanks. But if protection is possible, why doesn't [...] already
>> does it? I thought that in the brackets is always only a path
>> anyway.
> because we share soem code with context and i don't want to support this
> [] syntax there (conflicts too much)
Ah ok. I'm not really bound to a specific syntax as long as
luaotfload at the end gets the correct data.
The problem is that luaotfload is not really maintained currently,
so it is difficult to improve its handling of lua-fonts. The current
setup has some problems with them:
I tried at first the {file:luafont.lua} syntax, but luaotfload
doesn't look in fonts/misc in this case (which imho is a more
logical place then tex/luatex), and also it constantly triggered the
rebuilding of the database. Absolute pathes found with kpathsea
looked like the way out -- apart from the problem with the colon.
--
Ulrike Fischer
http://www.troubleshooting-tex.de/
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] font pathes with colons
Am Sat, 9 Jun 2018 11:52:43 +0200 schrieb Hans Hagen:
>> As far as I can see the code which does the splitting is in
>> font-def.lua and so part of the generic code. Is there anything that
>> can be done to correct his? Or can one somehow protect the colon
>> after c: to be interpretated as file-detail separator?
> i can support {weird name} but need to check first if it will not
> interfere with context (or luatex-plain)
Thanks. But if protection is possible, why doesn't [...] already
does it? I thought that in the brackets is always only a path
anyway.
--
Ulrike Fischer
http://www.troubleshooting-tex.de/
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
[NTG-context] font pathes with colons
I have been playing around with lua fonts and investigating where to
store and how to load them.
The best with luaotfload and latex seems to be currently to get
(with a kpse call) the absolute path and then load with the "xetex"
syntax:
\font\duckchessfont =
[\directlua{tex.sprint(kpse.find_file("luafont-duckchess.lua",
"misc fonts"))}]:mode=node;+liga;+tlig;original=latinmodernsans
This worked but I also saw in the log curious messages
luaotfload | load : font option
"/Users//Documents/Git/lua-font-
pond/texmf/fonts/misc/luafont/luafont-duckchess.lua]:mode=node"
unknown.
I investigated a bit. I'm on windows and imho this looks as if the
syntax parser is splitting after the C: of the drive and putting the
rest in the specification.detail field.
As far as I can see the code which does the splitting is in
font-def.lua and so part of the generic code. Is there anything that
can be done to correct his? Or can one somehow protect the colon
after c: to be interpretated as file-detail separator?
--
Ulrike Fischer
http://www.troubleshooting-tex.de/
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] Fonts and equations
Am Sat, 19 May 2018 10:06:01 +1200 schrieb Henri Menke: >> I can't search for e.g. the a or z if I compile > > You probably have to search for 푎 (U+1D44E) and 푧 (U+1D467). Well yes, but I have some doubts that Lance meant this. -- Ulrike Fischer http://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] Fonts and equations
Am Thu, 17 May 2018 05:19:05 -0600 schrieb Lance Larsen: > One really nice feature with equations is that by default you can > search for variable names in equation in a PDF reader like > acrobat. I can't search for e.g. the a or z if I compile \starttext $z_1 = x_1 + y_1$ $a = b + c$ \stoptext -- Ulrike Fischer http://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] Files on a server
Am Thu, 17 May 2018 09:54:25 +0200 schrieb Taco Hoekwater: >> Works ok for me. Did you test? > > Oh, sorry. It seems it is sneakily rewriting the https:// to http://, > and so does not _actually_ work. Ah. This explains why it seemed to work for https://httpbin.org/html, http://httpbin.org/html exists and why I get a lot of redirection answers. -- Ulrike Fischer http://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] Files on a server
Am Thu, 17 May 2018 09:39:47 +0200 schrieb Taco Hoekwater: >>> Or use luasocket, which is included in the luatex binary: >> But I'm right that this works only with http and not with https? > Works ok for me. Did you test? I tried a few links and always got 301 back regardless if they exist or not and thought due to the discussion two month ago on the luatex list about https content that it doesn't work at all. I know found https://httpbin.org/ and with it the tests worked: https://httpbin.org/html gave 200 and https://httpbin.org/html gave 404. But the answers from "real" websites are so varied and so often don't say the truth that I would't describe it as "works ok" ;-). -- Ulrike Fischer http://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] Files on a server
Am Wed, 16 May 2018 14:23:42 +0200 schrieb Taco Hoekwater: > Or use luasocket, which is included in the luatex binary: But I'm right that this works only with http and not with https? -- Ulrike Fischer http://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] using lua fonts
Am Wed, 9 May 2018 09:56:50 +0200 schrieb Hans Hagen: > watch how i replaced the * by : because only context has the * syntax Thank you very much for this explanation. I was wondering about the same thing and replacing this made the code going. Perhaps a general remark: I and certainly Henry too are quite aware that some of the code is context specific. But it is often quite difficult to see the boundaries -- which part of the examples are generic and which rely on context (and on how much in context). It is also not easy to decide which (lua) functions are "public" and won't break at the next update of the font handler. Henri: As you are interested in these things too, do you think it would be a good idea to setup a github repository where we collect such (plain and latex and context) examples? -- Ulrike Fischer http://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] using lua fonts
Am Thu, 3 May 2018 20:26:20 +0200 schrieb Ulrike Fischer: > I'm trying to run one of the examples of fonts-mkiv.pdf > > I copied the code from 4.5 Lua fonts to a file > "fonts-demo-rule.lua". This lua file is in the same directory as my > test file. > ... > > but I get in the log > > fonts > defining > forced type 'lua' of 'fonts-demo-rule' not found For the record: It was a silly error. As the lua file is not in the sources I had to copy & paste from the fonts-mkiv.pdf and overlooked that the code has a last "end" on the next page. After adding it to the lua everything worked as expected. -- Ulrike Fischer http://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] using lua fonts
Am Tue, 8 May 2018 10:43:00 +0200 schrieb Hans Hagen: > i have no clue as it works ok here ;-(. Where is the fonts-demo-rule.lua on your system? I don't think that it is actually loaded in my test file. I can write nonsense in it and get no error. -- Ulrike Fischer http://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
[NTG-context] using lua fonts
I'm trying to run one of the examples of fonts-mkiv.pdf
I copied the code from 4.5 Lua fonts to a file
"fonts-demo-rule.lua". This lua file is in the same directory as my
test file.
Then I tried
\definefont
[MyRuleFont]
[file:fonts-demo-rule.lua*default sa 1]
\starttext
{\MyRuleFont So when we use it we get text }
\stoptext
but I get in the log
fonts > defining > forced type 'lua' of 'fonts-demo-rule' not found
fonts > defining > font with asked name 'fonts-demo-rule' is not
found using lookup 'file'
fonts > defining > unknown font 'fonts-demo-rule', loading aborted
fonts > defining > unable to define 'fonts-demo-rule.lua' as
'MyRuleFont--0'
The file itself is found (I can see its path later on). What is
going on here?
--
Ulrike Fischer
http://www.troubleshooting-tex.de/
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] two nested \mathbin command changes spacing
Am Tue, 1 May 2018 10:12:42 +0200 schrieb Hans Hagen:
> On 4/30/2018 6:50 PM, Ulrike Fischer wrote:
>> In the following document the second a is much nearer placed to the
>> V:
>>
>> \starttext
>> $V \mathbin{a} W \qquad V \mathbin{\mathbin{a}} W $
>> \stoptext
>>
>> (in the second case an italic kern seems to be missing)
>>
>> Can one avoid this side effect of nested \math-command? When
>> building symbols it is not always easy to avoid such nestings.
> it becomes a chicken-egg issue because one can argue that a wrapped
> mathbin is no longer a pure bin and so ... it's again an indication that
> a wrong boundingbox (width) relying on always some kind of italic to fix
> it is a bad approach
Well yes, I already suspected this when I saw "italic" in the log.
What would be a better approach?
The question who started the investigation wanted to get a binary
symbol "\hat{\otimes}". How does one define it so the spacing is
correct? It doesn't need be the fontloader that catches all the
case. It would be quite okay to insert some code that says "hey
handle me like \otimes". And it would also okay to assume a "good
font".
But even with cambria it doesn't work correctly in context
currently. The displacement is slight (only 0.3pt) but at large zoom
one can see it:
%\setupbodyfont[cambria] %without it the spacing is more pronounced
\starttext
$ V \otimes W $
$ V \mathbin{\hat{\otimes}} W $
$ V \Umathchar 2 0 "2297 W $
$ V \mathbin{\Umathchar 0 0 "2297} W $
$ V \mathbin{\Umathchar 2 0 "2297} W $
$ V \mathbin{\Umathaccent 0 0 "302 \Umathchar 0 0 "2297} W $
\stoptext
--
Ulrike Fischer
http://www.troubleshooting-tex.de/
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
[NTG-context] two nested \mathbin command changes spacing
In the following document the second a is much nearer placed to the
V:
\starttext
$V \mathbin{a} W \qquad V \mathbin{\mathbin{a}} W $
\stoptext
(in the second case an italic kern seems to be missing)
Can one avoid this side effect of nested \math-command? When
building symbols it is not always easy to avoid such nestings.
--
Ulrike Fischer
http://www.troubleshooting-tex.de/
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] ! error: (nodes): attempt to double-free math_char node 100300, ignored
Am Mon, 30 Apr 2018 17:45:28 +0200 schrieb Hans Hagen: > if one needs text in math then using a boxed approach calling some real > text fonts makes more sense Yes, I agree. -- Ulrike Fischer http://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] ! error: (nodes): attempt to double-free math_char node 100300, ignored
Am Mon, 30 Apr 2018 15:49:11 +0200 schrieb Hans Hagen:
>> While discussion the issue with the unicode-math maintainer the
>> question came up if mathalphabets like \mathrm etc should better use
>> mode=node or mode=base. Do you have recommendation?
> not really as i have no clue how he implements math alphabets
Imho like in traditional tex as new math family with \newfam etc.
From the output there is a clear difference, only with base mode one
gets ligatures and kerning.
$\mathtestnode{VA fin}$ (node mode: without ligature and kerning)
$\mathtestbase{VA fin}$ (base mode: with ligature and kerning)
But I'm not sure which output is the typographically sounder one.
--
Ulrike Fischer
http://www.troubleshooting-tex.de/
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] ! error: (nodes): attempt to double-free math_char node 100300, ignored
Am Sat, 28 Apr 2018 21:41:31 +0200 schrieb Hans Hagen: > On 4/28/2018 5:57 PM, Ulrike Fischer wrote: >> Libertinus Serif > > ok, after some debugging luigi and i found a possible issue with the lig > builder part Ah. Good. Is this an engine or a fontloader issue? While discussion the issue with the unicode-math maintainer the question came up if mathalphabets like \mathrm etc should better use mode=node or mode=base. Do you have recommendation? -- Ulrike Fischer http://www.troubleshooting-tex.de/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
