Re: [NTG-context] beta
Hi Hans, with the new beta following mwe produces a bug. Perhaps I'm doing something wrong. MWE: \definefontfamily[mainface][sans][DejaVu Sans] %or \definefontfamily[mainface][sans][gosmicksans] with the same result \setupbodyfont[mainface] \starttext \input tufte \stoptext Error log: Typesetting /home/ubuntu/workspace/mwe.tex mtx-context | run 1: luatex --fmt=/home/ubuntu/workspace/context/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luatex/cont-en --jobname=mwe --lua=/home/ubuntu/workspace/context/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luatex/cont-en.lui --no-parse-first-line --c:currentrun=1 --c:fulljobname=./mwe.tex --c:input=./mwe.tex --c:kindofrun=1 --c:maxnofruns=8 cont-yes.mkiv This is LuaTeX, Version beta-0.80.0 (TeX Live 2015/dev) (rev 5195) \write18 enabled. interfaces implementor warning: 'commands.writestatus' is redefined interfaces implementor error: no actions for 'btxresolvelistreference' open source 1 1 /home/ubuntu/workspace/context/tex/texmf-context/tex/context/base/cont-yes.mkiv ConTeXt ver: 2015.03.26 19:19 MKIV beta fmt: 2015.3.26 int: english/english system 'cont-new.mkiv' loaded open source 2 2 /home/ubuntu/workspace/context/tex/texmf-context/tex/context/base/cont-new.mkiv close source 2 2 /home/ubuntu/workspace/context/tex/texmf-context/tex/context/base/cont-new.mkiv system files jobname 'mwe', input './mwe', result 'mwe' fontslatin modern fonts are not preloaded languageslanguage 'en' is active open source 2 3 /home/ubuntu/workspace/documents/snippets/bug/mwe.tex tex errorerror on line 179 in file /home/ubuntu/workspace/documents/snippets/bug/mwe.tex: ! Argument of \splitoffbase has an extra } inserted text \par to be read again } \rawdoifinsetelse ...def \m_syst_sub_string {,#1,} \ifx \m_syst_sub_string \m... \addtocommalist #1#2-\rawdoifinsetelse {#1} #2\resetglobal {\dodoglobal \ede... \font_typefaces_define_a ...usetypescriptfile [#4] \font_typescripts_use_one ... l.179 ] ... l.2 \setupbodyfont [mainface] Thanks for your help. Christian 2015-03-26 19:24 GMT+01:00 Hans Hagen pra...@wxs.nl: Hi, I uploaded a beta (for luatex 0.80) that has some changes in low level interfaces. Hopefully there are no side effects but there are they can be sorted out fast. I tested the code on projects and manuals so it should not be too bad. Depending on how complex your setup up is, there can be a speed gain of some 5% compared to previous versions. Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ 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://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___ ___ 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://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] beta
On 03/26/2015 07:24 PM, Hans Hagen wrote: Hi, I uploaded a beta (for luatex 0.80) that has some changes in low level interfaces. Hopefully there are no side effects but there are they can be sorted out fast. I tested the code on projects and manuals so it should not be too bad. Depending on how complex your setup up is, there can be a speed gain of some 5% compared to previous versions. Hans, many thanks for the new beta. I’m afraid that the three documents I tested (rather complex ones) cannot be compiled and the error message is the same. \definefontfamily seems to be the offending command The minimal sample: \definefontfamily[mainface][rm][TeX Gyre Pagella] \setupbodyfont[mainface] \starttext \input zapf \stoptext Many thanks for your help, Pablo -- http://www.ousia.tk ___ 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://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] beta
Am 26.03.2015 um 20:14 schrieb Pablo Rodriguez oi...@gmx.es: On 03/26/2015 07:24 PM, Hans Hagen wrote: Hi, I uploaded a beta (for luatex 0.80) that has some changes in low level interfaces. Hopefully there are no side effects but there are they can be sorted out fast. I tested the code on projects and manuals so it should not be too bad. Depending on how complex your setup up is, there can be a speed gain of some 5% compared to previous versions. Hans, many thanks for the new beta. I’m afraid that the three documents I tested (rather complex ones) cannot be compiled and the error message is the same. \definefontfamily seems to be the offending command The minimal sample: \definefontfamily[mainface][rm][TeX Gyre Pagella] \setupbodyfont[mainface] \starttext \input zapf \stoptext Many thanks for your help, The bug happens further down in the \usetypescriptfile command and is triggered when a empty argument is given. The cause can be reproduced with the following example when you pass an empty string to \splitfilename. \starttext \letempty\CommaList \splitfilename{}% fails %\splitfilename{text}% works \addtocommalist\splitoffbase\CommaList \stoptext Wolfgang ___ 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://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
[NTG-context] beta
Hi, I uploaded a beta (for luatex 0.80) that has some changes in low level interfaces. Hopefully there are no side effects but there are they can be sorted out fast. I tested the code on projects and manuals so it should not be too bad. Depending on how complex your setup up is, there can be a speed gain of some 5% compared to previous versions. Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ 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://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] Bug with ligatures (EBGaramond) and \mainlanguage[es]
On 3/26/2015 7:10 AM, Pablo Rodriguez wrote: On 03/26/2015 06:23 AM, Andrés Conrado wrote: Hello, list. When I try to use the EBGaramond font (http://www.georgduffner.at/ebgaramond/) in spanish (using \mainlanguage[es]), ligatures disappear. But they only disappear when they belong to a word (when alone, they look fine). See MWE, if you remove the comment in the \mainlanguage command, ligatures get screwed up: Hi Andrés, I’m afraid this is a proper bug. It isn’t related to Spanish as language. The bug is triggered when a the ligature has a hyphenation point at the end. Here is another mininmal example with German as main language: \mainlanguage[de] \loadtypescriptfile[ebgaramond] \setupbodyfont[ebgaramond,24pt] \starttext \hsize\zeropoint figura afigura \es figura afigura \en figura afigura \stoptext German only inserts a hyphenation point after three characters (and before other three characters). This is why the first word has the ligature and the second word doesn’t have it. English doesn’t show the bug, because it doesn’t find any hyphenation point in the words. Until this is fixed, you may use the new hyphenator. You need a fairly new beta. Add the following lines at the top of your preamble: \setuphyphenation[method=traditional] \sethyphenationfeatures[strict] I hope it helps, It's not a bug actually but a side effect. The way fonts implement ligatures is rather diverse (and even not always recognizable as ligature). This can interact with hyphenation especially because we not only have to take replacements into account but also relative positioning, because 1-1 replacement, many-1 replacements and positioning are all used in combination. Because it makes no sense to expand a node list into all possible permutations of (combinations) of hyphenation points, the current mechanism has some assumptions. One problem with that is that in traditional tex a discretionary comes in several disguises and at some point it doesn't even have specific hyphenation characters it its sublists which in turn interacts with whatever-hyphen replacements and kerning. So, the context reality is that there are a few strategies uses and the results depends on the combination of these strategies. Currently the defaults result in a limited analysis. Then we can have this: \setuphyphenation[method=expanded] which indeed in this example gives the results as expected. Because that method is also used in the alternative hyphenator that one also works. In a future version I will change some defaults or maybe even switch to the alternative hyphenator as it offers some advantages. Pablo has been testing it for a while and it seems to work ok. The only drawback is that I need to keep the old methods as benchmark. When multiple side-by-side hyphenation points are used the font builder can discard some but this is normally no big issue for tex. Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ 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://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] beta
On 3/26/2015 8:35 PM, Wolfgang Schuster wrote: Am 26.03.2015 um 20:14 schrieb Pablo Rodriguez oi...@gmx.es: On 03/26/2015 07:24 PM, Hans Hagen wrote: Hi, I uploaded a beta (for luatex 0.80) that has some changes in low level interfaces. Hopefully there are no side effects but there are they can be sorted out fast. I tested the code on projects and manuals so it should not be too bad. Depending on how complex your setup up is, there can be a speed gain of some 5% compared to previous versions. Hans, many thanks for the new beta. I’m afraid that the three documents I tested (rather complex ones) cannot be compiled and the error message is the same. \definefontfamily seems to be the offending command The minimal sample: \definefontfamily[mainface][rm][TeX Gyre Pagella] \setupbodyfont[mainface] \starttext \input zapf \stoptext Many thanks for your help, The bug happens further down in the \usetypescriptfile command and is triggered when a empty argument is given. The cause can be reproduced with the following example when you pass an empty string to \splitfilename. \starttext \letempty\CommaList \splitfilename{}% fails %\splitfilename{text}% works \addtocommalist\splitoffbase\CommaList \stoptext ok, fix in engine needed ... i uploaded a temp fix Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ 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://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] Bug with ligatures (EBGaramond) and \mainlanguage[es]
On 03/26/2015 06:23 AM, Andrés Conrado wrote: Hello, list. When I try to use the EBGaramond font (http://www.georgduffner.at/ebgaramond/) in spanish (using \mainlanguage[es]), ligatures disappear. But they only disappear when they belong to a word (when alone, they look fine). See MWE, if you remove the comment in the \mainlanguage command, ligatures get screwed up: Hi Andrés, I’m afraid this is a proper bug. It isn’t related to Spanish as language. The bug is triggered when a the ligature has a hyphenation point at the end. Here is another mininmal example with German as main language: \mainlanguage[de] \loadtypescriptfile[ebgaramond] \setupbodyfont[ebgaramond,24pt] \starttext \hsize\zeropoint figura afigura \es figura afigura \en figura afigura \stoptext German only inserts a hyphenation point after three characters (and before other three characters). This is why the first word has the ligature and the second word doesn’t have it. English doesn’t show the bug, because it doesn’t find any hyphenation point in the words. Until this is fixed, you may use the new hyphenator. You need a fairly new beta. Add the following lines at the top of your preamble: \setuphyphenation[method=traditional] \sethyphenationfeatures[strict] I hope it helps, Pablo %% % remove the comment below to see the effect on ligatures. %\mainlanguage[es] \loadtypescriptfile[ebgaramond] \setupbodyfont[ebgaramond,48pt] \starttext flagrantemente y figurativamente ff fl fi ffi ffl ffii figura ffla fflego \stoptext %% Thanks for any ideas you may have, I'm clueless, and really need to use those ligatures. I can edit whatever needs to be edited, but I can't find any ideas in the source, nor the mailing list. ___ 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://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___ -- http://www.ousia.tk ___ 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://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] slanting an intermezzo.
Hi John, Maybe playing with something like what follows will help: begin tilted-framed.tex \starttext \placeintermezzo[right,none]{} \rotate[rotation=-10]{\startframedtext[width=3in] \midaligned{\bf RECIPE FOR SUCCESS} \par \noindent \input knuth.tex \stopframedtext} \input knuth.tex \input knuth.tex \input knuth.tex \stoptext end tilted-framed.tex Best regards: OK On 25 Mar 2015, at 22:36, John Culleton j...@wexfordpress.com wrote: \starttext \setupframed[background=screen,framecorner=rectangular,backgroundscreen=0.70] \placeintermezzo[right,none]{} \startframedtext[width=3in] \centerline {\bf RECIPE FOR SUCCESS} \noindent \input knuth.tex \stopframedtext \input knuth.tex \input knuth.tex \input knuth.tex \stoptext -- I know I am supposed to use \rotate but I can't figure out how to rotate an intermezzo. Please help! John Culleton ___ 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://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] component not included
Am 13.03.2015 um 09:01 schrieb Wolfgang Werners-Lucchini w...@musensturm.de: According toll my observations, you need to reference the needed parts inside of the \start... and \stop..., so your product would become: ``` \startproduct pd-medizin \project pj-medizin \component test \stopproduct ``` You also have to restructure the other files, so that \start... is the first and \stop... the last command in the files. Yes! That is the cause. Thank you! The wiki examples should be corrected to prevent others from this error. With the new beta you can now load project files at the begin of your products and components. Wolfgang ___ 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://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___