Re: [NTG-context] Metapost labels
On Wed, 7 Aug 2013 06:50:54 +0200 Lutz Haseloff lutz.hasel...@gmail.com wrote: Hi all, with LuaTeX, Version beta-0.77.0-2013073017 (rev 4639) and ConTeXt ver: 2013.08.06 15:50 MKIV beta fmt: 2013.8.7 int: english/english Context seems not to be able to typeset Labels anymore. Yesterday, before an Update, all worked as expected. Minimal not working example: \starttext \startMPpage draw fullcircle scaled 5cm withcolor red; label(textext(\CONTEXT),origin); \stopMPpage \stoptext Or am I missing something happened in the last four weeks? Something seems wrong with the current beta. It does not find files (cont-yes.mkiv, etc.), does not find fonts, etc. metapost loading 'metafun' fails, format not found Following the mailing list, Hans tried `fixing' something with file loading... Alan ___ 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] kerning with buggy libertine
···date: 2013-08-05, Monday···from: Hans Hagen···
On 8/4/2013 3:43 PM, Philipp Gesang wrote:
Hi Hans,
this is a bug report thanks to Khaled:
http://tex.stackexchange.com/a/126650/14066
In short: the font loader applies the kerning of libertine
version 5.3.0 even though this appears to be broken in the font.
Context translation of the example:
\definefontfeature [kerning] [mode=node,smcp=yes,kern=yes]
\definefont [libertineserifsmallcaps] [file:LinLibertine_R.otf*kerning]
\definefont [libertinesanssmallcaps] [file:LinBiolinum_R.otf*kerning]
\def\demotext{Vacillate Vaccine Vapour Vanish Va...}
\starttext
{\libertineserifsmallcaps \demotext}\par
{\libertinesanssmallcaps \demotext}\par
\stoptext
(Doesn’t occur in base mode.) The technical details are in the
thread Khaled references.
\showotfcomposition{file:LinLibertine_R.otf*kerning}{+1}{Va} \page
\showotfcomposition{file:LinBiolinum_R.otf*kerning} {+1}{Va} \page
You need to be more explicit (which font, where to download the
problematic one, etc ... i downloaded the 5.3 version - i think - of
ll). In what sense is it broken in the font?
It’s that version (5.3.0). To quote Jonathan Kew [1]:
The problem arises because the first subtable includes the
V (and T) glyphs in its coverage (as first glyph of the
pair), but then the a.sc and hyphen.sc glyphs are not
included in the ClassDef2 table, so they map to class 0, for
which the kerning is zero. [...]
The description of ClassDefFormat2 says that Any glyph not
covered by a ClassRangeRecord is assumed to belong to Class
0. If that is the case, then I think this is a font bug: any
first-glyph mentioned in a PairPosFormat2 subtable's coverage
when ClassDef2 uses format 2 will, in effect, shadow all
subsequent subtables, so the same first-glyph cannot be used
again.
And the follow up [2]:
FWIW, testing LinLibertine in IE10 on Win8, I see the same
behavior as in Firefox (using harfbuzz): the V, a.sc and
T, hyphen.sc pairs are NOT kerned.
So I believe this supports the interpretation that this is a
font bug, and we should -not- special-case Class0 as per the
experimental harfbuzz patch.
(In principle, a font could have real kerning values
specified for classN, class0, although it's most likely
that class0 will always be used for the default do-nothing
case.)
Best,
Philipp
[1] http://lists.freedesktop.org/archives/harfbuzz/2013-August/003469.html
[2] http://lists.freedesktop.org/archives/harfbuzz/2013-August/003470.html
pgpskZBCaZqPl.pgp
Description: PGP signature
___
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] problem with Persian feature
Dear All, Hello, I am completely new to ConTeXt and after searching and exploring the ConTeXt Garden wiki pages and other resources thoroughly, I decided to write my first document in Persian which reads: \enableregime [utf-8] \definefontfeature [persian] [mode=node,language=dflt,script=arab, init=yes,medi=yes,fina=yes,isol=yes,liga=yes,dlig=yes,rlig=yes,clig=yes, mark=yes,mkmk=yes,kern=yes,curs=yes] \usemodule[simplefonts] \setmainfont[arial][feature=persian] \mainlanguage[pe] \setupbodyfont[arial,12pt] \starttext \pagedir TRT\bodydir TRT\pardir TRT\textdir TRT این یک آزمایش است. \pagedir TLT\bodydir TLT\pardir TLT\textdir TLT This is a test. \stoptext As there are some UTF-8 characters in the document I have attached the document to this message too. The problem is that on my system the Persian part of the output is a set of Persian Isolated characters, but on http://live.contextgarden.net the Persian part does not appear at all. Could somebody please let me know what am I doing wrong? Thanks, Mingranina my-first-doc.tex Description: TeX document ___ 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] problem with Persian feature
On 8/7/2013 10:50 AM, Mingranina Gingranina wrote: Dear All, Hello, I am completely new to ConTeXt and after searching and exploring the ConTeXt Garden wiki pages and other resources thoroughly, I decided to write my first document in Persian which reads: \enableregime [utf-8] \definefontfeature [persian] [mode=node,language=dflt,script=arab, init=yes,medi=yes,fina=yes,isol=yes,liga=yes,dlig=yes,rlig=yes,clig=yes, mark=yes,mkmk=yes,kern=yes,curs=yes] \usemodule[simplefonts] \setmainfont[arial][feature=persian] \mainlanguage[pe] \setupbodyfont[arial,12pt] \starttext \pagedir TRT\bodydir TRT\pardir TRT\textdir TRT این یک آزمایش است. \pagedir TLT\bodydir TLT\pardir TLT\textdir TLT This is a test. \stoptext As there are some UTF-8 characters in the document I have attached the document to this message too. The problem is that on my system the Persian part of the output is a set of Persian Isolated characters, but on http://live.contextgarden.net the Persian part does not appear at all. Could somebody please let me know what am I doing wrong? Here is a more minimal test: \definefontfeature [persian] [arabic] % [...] \mainlanguage[pe] \starttext \definedfont[arial*persian] \setupalign[r2l] این یک آزمایش است. \setupalign[l2r] This is a test. \stoptext If that works, you can try the simplefonts variant. Keep in mind that you need to end a paragraph with an empty line or \par because otherwise the last settings apply. 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] Metapost labels
On 8/7/2013 6:50 AM, Lutz Haseloff wrote: Hi all, with LuaTeX, Version beta-0.77.0-2013073017 (rev 4639) and ConTeXt ver: 2013.08.06 15:50 MKIV beta fmt: 2013.8.7 int: english/english Context seems not to be able to typeset Labels anymore. Yesterday, before an Update, all worked as expected. Minimal not working example: \starttext \startMPpage draw fullcircle scaled 5cm withcolor red; label(textext(\CONTEXT),origin); \stopMPpage \stoptext Or am I missing something happened in the last four weeks? some playing with transformations and keeping properties at the same time ... new beta uploaded 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] Metapost labels
Hi Hans, Labels work again as expected. Thanks for the quick help! 2013/8/7 Hans Hagen pra...@wxs.nl On 8/7/2013 6:50 AM, Lutz Haseloff wrote: Hi all, with LuaTeX, Version beta-0.77.0-2013073017 (rev 4639) and ConTeXt ver: 2013.08.06 15:50 MKIV beta fmt: 2013.8.7 int: english/english Context seems not to be able to typeset Labels anymore. Yesterday, before an Update, all worked as expected. Minimal not working example: \starttext \startMPpage draw fullcircle scaled 5cm withcolor red; label(textext(\CONTEXT),**origin); \stopMPpage \stoptext Or am I missing something happened in the last four weeks? some playing with transformations and keeping properties at the same time ... new beta uploaded 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 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/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 ___
[NTG-context] How to prevent moving figure on the next page?
Hi list,
I need help to undestand this effect: If setuphead[chapter][page=no] and after
figure start a new chapter, than figure is moved to the page 2, although on
page 1 space is enough. Thanks.
\setuppapersize[A5][A5]
\setupbodyfont[10pt]
\setuphead[chapter][page=no]
\showframe
\starttext
\chapter {One}
\dorecurse{2}{\input{knuth}}
\placefigure[here][figure]{Description}
{\externalfigure[figure][width=5cm,height=2.0cm]}
% if setuphead[chapter][page=no] and this comment transform to text, than
figure moves to page 1. What do I need to figure always placing on page 1?
\chapter {Two}
\stoptext
--
Dmitriy
___
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] problem with Persian feature
Dear Hans, Hello, Thank you very much for your reply. With your code the Persian part disappears on my system unless I insert the following two lines after \definefontfeature: \usemodule[simplefonts] \setmainfont[arial][feature=persian] However the Persian characters still appears as isolated characters. Thanks, Mingranina On 8/7/13, Hans Hagen pra...@wxs.nl wrote: On 8/7/2013 10:50 AM, Mingranina Gingranina wrote: Dear All, Hello, I am completely new to ConTeXt and after searching and exploring the ConTeXt Garden wiki pages and other resources thoroughly, I decided to write my first document in Persian which reads: \enableregime [utf-8] \definefontfeature [persian] [mode=node,language=dflt,script=arab, init=yes,medi=yes,fina=yes,isol=yes,liga=yes,dlig=yes,rlig=yes,clig=yes, mark=yes,mkmk=yes,kern=yes,curs=yes] \usemodule[simplefonts] \setmainfont[arial][feature=persian] \mainlanguage[pe] \setupbodyfont[arial,12pt] \starttext \pagedir TRT\bodydir TRT\pardir TRT\textdir TRT این یک آزمایش است. \pagedir TLT\bodydir TLT\pardir TLT\textdir TLT This is a test. \stoptext As there are some UTF-8 characters in the document I have attached the document to this message too. The problem is that on my system the Persian part of the output is a set of Persian Isolated characters, but on http://live.contextgarden.net the Persian part does not appear at all. Could somebody please let me know what am I doing wrong? Here is a more minimal test: \definefontfeature [persian] [arabic] % [...] \mainlanguage[pe] \starttext \definedfont[arial*persian] \setupalign[r2l] این یک آزمایش است. \setupalign[l2r] This is a test. \stoptext If that works, you can try the simplefonts variant. Keep in mind that you need to end a paragraph with an empty line or \par because otherwise the last settings apply. 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] kerning with buggy libertine
On 8/7/2013 10:08 AM, Philipp Gesang wrote: It’s that version (5.3.0). To quote Jonathan Kew [1]: And the follow up [2]: it all makes me wonder if otf is that clear and clean and good ... font designers nowadays need to be programmers and close-readers-of-specs too (esp because it seem to take years to uncover such aspects) anyhow, new beta ... plus some extra messages (the first concern fixing a luatex table ... not related to the issue but nicer anyway) fontsotf loading fixing kernclass table of lookup 'pp_l_3_k_0' fontsotf loading fixing kernclass table of lookup 'pp_l_3_k_1' fontsotf loading fixing kernclass table of lookup 'pp_l_3_k_2' fontsotf loading fixing kernclass table of lookup 'pp_l_3_k_3' fontsotf loading lookup 'pp_l_3_k_3': ignoring further kerns of A (U+00041) fontsotf loading lookup 'pp_l_3_k_3': ignoring further kerns of À (U+000C0) fontsotf loading lookup 'pp_l_3_k_3': ignoring further kerns of Á (U+000C1) fontsotf loading lookup 'pp_l_3_k_3': ignoring further kerns of  (U+000C2) fontsotf loading lookup 'pp_l_3_k_3': ignoring further kerns of à (U+000C3) fontsotf loading lookup 'pp_l_3_k_3': ignoring further kerns of Ä (U+000C4) fontsotf loading lookup 'pp_l_3_k_3': ignoring further kerns of Å (U+000C5) fontsotf loading lookup 'pp_l_3_k_3': ignoring further kerns of Ă (U+00102) fontsotf loading lookup 'pp_l_3_k_3': ignoring further kerns of V (U+00056) fontsotf loading lookup 'pp_l_3_k_3': ignoring further kerns of W (U+00057) fontsotf loading lookup 'pp_l_3_k_3': ignoring further kerns of Y (U+00059) fontsotf loading lookup 'pp_l_3_k_3': ignoring further kerns of Ÿ (U+00178) fontsotf loading lookup 'pp_l_3_k_3': ignoring further kerns of P (U+00050) fontsotf loading lookup 'pp_l_3_k_3': ignoring further kerns of K (U+0004B) fontsotf loading lookup 'pp_l_3_k_3': ignoring further kerns of X (U+00058) fontsotf loading lookup 'pp_l_3_k_3': ignoring further kerns of T (U+00054) fontsotf loading lookup 'pp_l_3_k_3': ignoring further kerns of Ţ (U+00162) fontsotf loading lookup 'pp_l_3_k_3': ignoring further kerns of Ť (U+00164) fontsotf loading lookup 'pp_l_3_k_3': ignoring further kerns of Ț (U+0021A) the message is a signal for users not to complain too loudly if some expected kern doesn't show up (i didn't test side effects so we might now run into other cases) 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] problem with Persian feature
Dear Hans, Hello again, I just noticed that your code works fine with Dejavusans TrueType font, but not with some other TrueType fonts. Thanks, On 8/7/13, Mingranina Gingranina mingran...@gmail.com wrote: Dear Hans, Hello, Thank you very much for your reply. With your code the Persian part disappears on my system unless I insert the following two lines after \definefontfeature: \usemodule[simplefonts] \setmainfont[arial][feature=persian] However the Persian characters still appears as isolated characters. Thanks, Mingranina On 8/7/13, Hans Hagen pra...@wxs.nl wrote: On 8/7/2013 10:50 AM, Mingranina Gingranina wrote: Dear All, Hello, I am completely new to ConTeXt and after searching and exploring the ConTeXt Garden wiki pages and other resources thoroughly, I decided to write my first document in Persian which reads: \enableregime [utf-8] \definefontfeature [persian] [mode=node,language=dflt,script=arab, init=yes,medi=yes,fina=yes,isol=yes,liga=yes,dlig=yes,rlig=yes,clig=yes, mark=yes,mkmk=yes,kern=yes,curs=yes] \usemodule[simplefonts] \setmainfont[arial][feature=persian] \mainlanguage[pe] \setupbodyfont[arial,12pt] \starttext \pagedir TRT\bodydir TRT\pardir TRT\textdir TRT این یک آزمایش است. \pagedir TLT\bodydir TLT\pardir TLT\textdir TLT This is a test. \stoptext As there are some UTF-8 characters in the document I have attached the document to this message too. The problem is that on my system the Persian part of the output is a set of Persian Isolated characters, but on http://live.contextgarden.net the Persian part does not appear at all. Could somebody please let me know what am I doing wrong? Here is a more minimal test: \definefontfeature [persian] [arabic] % [...] \mainlanguage[pe] \starttext \definedfont[arial*persian] \setupalign[r2l] این یک آزمایش است. \setupalign[l2r] This is a test. \stoptext If that works, you can try the simplefonts variant. Keep in mind that you need to end a paragraph with an empty line or \par because otherwise the last settings apply. 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] problem with Persian feature
On 8/7/2013 2:38 PM, Mingranina Gingranina wrote: Dear Hans, Hello again, I just noticed that your code works fine with Dejavusans TrueType font, but not with some other TrueType fonts. in which case you use fonts that have no arabic shapes 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] problem with Persian feature
Am 07.08.2013 um 12:38 schrieb Mingranina Gingranina mingran...@gmail.com: Dear Hans, Hello, Thank you very much for your reply. With your code the Persian part disappears on my system unless I insert the following two lines after \definefontfeature: \usemodule[simplefonts] \setmainfont[arial][feature=persian] However the Persian characters still appears as isolated characters. The name of the key is “features” and not “feature”. 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 ___
Re: [NTG-context] kerning with buggy libertine
···date: 2013-08-07, Wednesday···from: Hans Hagen··· On 8/7/2013 10:08 AM, Philipp Gesang wrote: It’s that version (5.3.0). To quote Jonathan Kew [1]: And the follow up [2]: it all makes me wonder if otf is that clear and clean and good ... font designers nowadays need to be programmers and close-readers-of-specs too (esp because it seem to take years to uncover such aspects) anyhow, new beta ... plus some extra messages (the first concern fixing a luatex table ... not related to the issue but nicer anyway) Thanks, Libertine is now as broken as it should be ;-) fontsotf loading fixing kernclass table of lookup 'pp_l_3_k_0' fontsotf loading fixing kernclass table of lookup 'pp_l_3_k_1' fontsotf loading fixing kernclass table of lookup 'pp_l_3_k_2' fontsotf loading fixing kernclass table of lookup 'pp_l_3_k_3' fontsotf loading lookup 'pp_l_3_k_3': ignoring further kerns of A (U+00041) fontsotf loading lookup 'pp_l_3_k_3': ignoring further kerns of À (U+000C0) fontsotf loading lookup 'pp_l_3_k_3': ignoring further kerns of Á (U+000C1) fontsotf loading lookup 'pp_l_3_k_3': ignoring further kerns of  (U+000C2) fontsotf loading lookup 'pp_l_3_k_3': ignoring further kerns of à (U+000C3) fontsotf loading lookup 'pp_l_3_k_3': ignoring further kerns of Ä (U+000C4) fontsotf loading lookup 'pp_l_3_k_3': ignoring further kerns of Å (U+000C5) fontsotf loading lookup 'pp_l_3_k_3': ignoring further kerns of Ă (U+00102) fontsotf loading lookup 'pp_l_3_k_3': ignoring further kerns of V (U+00056) fontsotf loading lookup 'pp_l_3_k_3': ignoring further kerns of W (U+00057) fontsotf loading lookup 'pp_l_3_k_3': ignoring further kerns of Y (U+00059) fontsotf loading lookup 'pp_l_3_k_3': ignoring further kerns of Ÿ (U+00178) fontsotf loading lookup 'pp_l_3_k_3': ignoring further kerns of P (U+00050) fontsotf loading lookup 'pp_l_3_k_3': ignoring further kerns of K (U+0004B) fontsotf loading lookup 'pp_l_3_k_3': ignoring further kerns of X (U+00058) fontsotf loading lookup 'pp_l_3_k_3': ignoring further kerns of T (U+00054) fontsotf loading lookup 'pp_l_3_k_3': ignoring further kerns of Ţ (U+00162) fontsotf loading lookup 'pp_l_3_k_3': ignoring further kerns of Ť (U+00164) fontsotf loading lookup 'pp_l_3_k_3': ignoring further kerns of Ț (U+0021A) the message is a signal for users not to complain too loudly if some expected kern doesn't show up As most of those go away once the font is cached it is not a big deal anyways. Best, Philipp pgpa8xdCjR0Mw.pgp Description: PGP signature ___ 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] problem with Persian feature
On 8/7/13, Hans Hagen pra...@wxs.nl wrote: On 8/7/2013 2:38 PM, Mingranina Gingranina wrote: Dear Hans, Hello again, I just noticed that your code works fine with Dejavusans TrueType font, but not with some other TrueType fonts. in which case you use fonts that have no arabic shapes For TrueType fonts which are in the directory '/usr/share/fonts/TTF/' everything works fine, but if the font is in '/usr/local/share/fonts/' then the code fails. Please note that I have already executed the commands: OSFONTDIR=/usr/share/fonts;/usr/local/share/fonts;$HOME/.fonts mtxrun --script fonts --reload mtxrun --script fonts --list --all --pattern=* Thanks, Mingranina ___ 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] problem with Persian feature
Hi Mingranina, As Wolfgang said, if I fix the name of the key in \setmainfont (from « feature » to « features », see below), then your test works fine here (using Mac OS X 10.8.4, and ConTeXt ver: 2013.08.07 14:40 MKIV beta fmt: 2013.8.7). By the way in mkiv you don't need to add \enableregime[utf-8]: by default ConTeXt uses utf-8. \definefontfeature [persian] [mode=node,language=dflt,script=arab, init=yes,medi=yes,fina=yes,isol=yes,liga=yes,dlig=yes,rlig=yes,clig=yes, mark=yes,mkmk=yes,kern=yes,curs=yes] \usemodule[simplefonts] \setmainfont[arial][features=persian] %% ^^ \mainlanguage[pe] \setupbodyfont[arial,12pt] \starttext \pagedir TRT\bodydir TRT\pardir TRT\textdir TRT این یک آزمایش است. \pagedir TLT\bodydir TLT\pardir TLT\textdir TLT This is a test. \stoptext Best regards: OK On 7 août 2013, at 12:38, Mingranina Gingranina mingran...@gmail.com wrote: Dear Hans, Hello, Thank you very much for your reply. With your code the Persian part disappears on my system unless I insert the following two lines after \definefontfeature: \usemodule[simplefonts] \setmainfont[arial][feature=persian] However the Persian characters still appears as isolated characters. Thanks, Mingranina On 8/7/13, Hans Hagen pra...@wxs.nl wrote: On 8/7/2013 10:50 AM, Mingranina Gingranina wrote: Dear All, Hello, I am completely new to ConTeXt and after searching and exploring the ConTeXt Garden wiki pages and other resources thoroughly, I decided to write my first document in Persian which reads: \enableregime [utf-8] \definefontfeature [persian] [mode=node,language=dflt,script=arab, init=yes,medi=yes,fina=yes,isol=yes,liga=yes,dlig=yes,rlig=yes,clig=yes, mark=yes,mkmk=yes,kern=yes,curs=yes] \usemodule[simplefonts] \setmainfont[arial][feature=persian] \mainlanguage[pe] \setupbodyfont[arial,12pt] \starttext \pagedir TRT\bodydir TRT\pardir TRT\textdir TRT این یک آزمایش است. \pagedir TLT\bodydir TLT\pardir TLT\textdir TLT This is a test. \stoptext As there are some UTF-8 characters in the document I have attached the document to this message too. The problem is that on my system the Persian part of the output is a set of Persian Isolated characters, but on http://live.contextgarden.net the Persian part does not appear at all. Could somebody please let me know what am I doing wrong? Here is a more minimal test: \definefontfeature [persian] [arabic] % [...] \mainlanguage[pe] \starttext \definedfont[arial*persian] \setupalign[r2l] این یک آزمایش است. \setupalign[l2r] This is a test. \stoptext If that works, you can try the simplefonts variant. Keep in mind that you need to end a paragraph with an empty line or \par because otherwise the last settings apply. 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 ___ ___ 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] How to prevent moving figure on the next page?
I found a solution that suits me:
\setuphead[chapter][page=]
--
Dmitriy
07.08.2013, 15:51, Dmitriy Tokarev dt...@ya.ru:
Hi list,
I need help to undestand this effect: If setuphead[chapter][page=no] and
after figure start a new chapter, than figure is moved to the page 2,
although on page 1 space is enough. Thanks.
\setuppapersize[A5][A5]
\setupbodyfont[10pt]
\setuphead[chapter][page=no]
\showframe
\starttext
\chapter {One}
\dorecurse{2}{\input{knuth}}
\placefigure[here][figure]{Description}
{\externalfigure[figure][width=5cm,height=2.0cm]}
% if setuphead[chapter][page=no] and this comment transform to text, than
figure moves to page 1. What do I need to figure always placing on page 1?
\chapter {Two}
\stoptext
--
Dmitriy
___
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] Feature-Request: Sort bibliography entries in alphabetical order by the entries' “short” value
Hi,
the publication list can be configured with `\setuppublications` to be sorted
by cite order (`sorttype=cite`) or the order of the publication entries
(`sorttype=bbl`).
With the following setup the short names of the publication entries are used
for cite references:
\setuppublications[
criterium=text,
sorttype=cite, % – short?
refcommand=short,
numbering=short,
...
]
The short names are set using the `s` attribute:
\startpublication[
s={RFC2616},
...
]
...
\stoppublication
A cite with this setup would look like [RFC2616].
In a long bibliography list it is useful if the entries are sorted in
alphabetical order by these short names to allow a faster lookup of
publications.
Currently I'm using the filter module and a Tcl script to sort the
publication entries ( http://tex.stackexchange.com/q/126939/7074 ), but it
might be useful if something like a `sorttype=short` option would be added.
Regards,
Michael
___
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] unwanted extra interline space in typing environment
Dear list, I have a document (http://ediciones-criticas.tk/pdf/criticas-context.pdf), which is shows a weird issue: some typing lines have an extra interline space added. It can be found on the first code samples on pages 11 and 12 from the above-mentioned document (sorry, but I have no other way to recreate the issue). My configuration is the following: \setuptyping[margin=yes,lines=yes,blank=line,space=on] How can avoid the unwanted extra interline space in the typing environment? 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] problem with Persian feature
On 08/07/2013 04:09 PM, Mingranina Gingranina wrote: [...] For TrueType fonts which are in the directory '/usr/share/fonts/TTF/' everything works fine, but if the font is in '/usr/local/share/fonts/' then the code fails. Please note that I have already executed the commands: OSFONTDIR=/usr/share/fonts;/usr/local/share/fonts;$HOME/.fonts mtxrun --script fonts --reload mtxrun --script fonts --list --all --pattern=* Hi Mingranina, are the fonts from /usr/local/share/fonts listed with the last command you mention? If you don’t have other issues, you can always move all fonts from /usr/local/share/fonts to /usr/share/fonts. This is an easy fix. Just in case it helps, 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] unwanted extra interline space in typing environment
Am 07.08.2013 um 19:47 schrieb Pablo Rodríguez oi...@web.de: Dear list, I have a document (http://ediciones-criticas.tk/pdf/criticas-context.pdf), which is shows a weird issue: some typing lines have an extra interline space added. It can be found on the first code samples on pages 11 and 12 from the above-mentioned document (sorry, but I have no other way to recreate the issue). My configuration is the following: \setuptyping[margin=yes,lines=yes,blank=line,space=on] How can avoid the unwanted extra interline space in the typing environment? Can you make a minimal example which shows the wrong spacing, I can see it in your document but without a example it’s not possible to give a answer. 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 ___
Re: [NTG-context] Feature-Request: Sort bibliography entries in alphabetical order by the entries' “short” value
On 8/7/2013 7:40 PM, Michael Scholtz wrote:
Hi,
the publication list can be configured with `\setuppublications` to be sorted
by cite order (`sorttype=cite`) or the order of the publication entries
(`sorttype=bbl`).
With the following setup the short names of the publication entries are used
for cite references:
\setuppublications[
criterium=text,
sorttype=cite, % – short?
refcommand=short,
numbering=short,
...
]
The short names are set using the `s` attribute:
\startpublication[
s={RFC2616},
...
]
...
\stoppublication
A cite with this setup would look like [RFC2616].
In a long bibliography list it is useful if the entries are sorted in
alphabetical order by these short names to allow a faster lookup of
publications.
Currently I'm using the filter module and a Tcl script to sort the
publication entries ( http://tex.stackexchange.com/q/126939/7074 ), but it might be
useful if something like a `sorttype=short` option would be added.
I added 'short' as sorttype .. untested as no example.
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] problem with Persian feature
On 8/7/13, Pablo Rodríguez oi...@web.de wrote: On 08/07/2013 04:09 PM, Mingranina Gingranina wrote: [...] For TrueType fonts which are in the directory '/usr/share/fonts/TTF/' everything works fine, but if the font is in '/usr/local/share/fonts/' then the code fails. Please note that I have already executed the commands: OSFONTDIR=/usr/share/fonts;/usr/local/share/fonts;$HOME/.fonts mtxrun --script fonts --reload mtxrun --script fonts --list --all --pattern=* Hi Mingranina, are the fonts from /usr/local/share/fonts listed with the last command you mention? No, they are not listed. If you don’t have other issues, you can always move all fonts from /usr/local/share/fonts to /usr/share/fonts. This is an easy fix. You are right. I think this is the only way to fix this problem. Thanks, Mingranina ___ 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] problem with Persian feature
On 8/7/13, Wolfgang Schuster schuster.wolfg...@gmail.com wrote: Am 07.08.2013 um 12:38 schrieb Mingranina Gingranina mingran...@gmail.com: Dear Hans, Hello, Thank you very much for your reply. With your code the Persian part disappears on my system unless I insert the following two lines after \definefontfeature: \usemodule[simplefonts] \setmainfont[arial][feature=persian] However the Persian characters still appears as isolated characters. The name of the key is “features” and not “feature”. Thanks for reminding me of this mistake. Regards, Mingranina ___ 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] unwanted extra interline space in typing environment
On 08/07/2013 08:00 PM, Wolfgang Schuster wrote:
Am 07.08.2013 um 19:47 schrieb Pablo Rodríguez oi...@web.de:
[...]
How can avoid the unwanted extra interline space in the typing environment?
Can you make a minimal example which shows the wrong spacing?
I can see it in your document but without a example it’s not possible
to give a answer.
Wolfgang,
this is a sample that shows the issue I mentioned in my previous message:
\setuplayout[setups=*lessstrict]
\startsetups[*lessstrict]
\setup[reset]
\widowpenalty=1
\clubpenalty=1
\stopsetups
\starttext
\dorecurse{38}{line\\}
\starttyping
\setuplayout[setups=*lessstrict]
\startsetups[*lessstrict]
\setup[reset]
\widowpenalty=1
\clubpenalty=1
\brokenpenalty=1
\stopsetups
\stoptyping
\page
\stoptext
I know that the widow line from the typing environment is causing the
extra interline spacing, but there are other occurrences where there is
no widow line and there is extra interline spacing.
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] setupnarrower and startnarrower
On 8/6/2013 6:14 PM, Aditya Mahajan wrote: On Tue, 6 Aug 2013, Wolfgang Schuster wrote: Am 06.08.2013 um 17:53 schrieb Aditya Mahajan adit...@umich.edu: On Tue, 6 Aug 2013, Wolfgang Schuster wrote: Am 06.08.2013 um 16:09 schrieb Alan BRASLAU alan.bras...@cea.fr: Thank you Wolfgang, but I was wondering about the standard \startnarrower. Many (some) commands allow setup assignments, the use of which overides but does not change the default. This is a very useful feature of ConTeXt that suggest could be generalized. \startnarrower is but one example. Changing the command is simple but I would drop the second argument when you want to change the left/right etc. values because you can say “left=4cm” etc. to get the desired margins. startnarrower has a weird interface. Ideally, it should just support keywords: \startnarrower [ leftmargin=..., rightmargin=..., alternative=(left|right|both), spacebefore=, spaceafter=, indenting=, indentnext=, before=, after=, ] That’s more or less what I use for the “narrow” alternative in the annotation module. I would prefer such a parameter driven narrower environment myself (do we even need the left, middle and right option when we can set absolute margins) but keeping the current interface for backwards compatibility make things a little bit ugly. Haven't we broken backward compatibility for other environments as well? \startlinenumbering immediately comes to mind where the MkII interface was \startlinenumbering[continue] and the current interface is \startlinenumbering[continue=yes] I, for one, think that it is OK to break backward compatibility for more elegance and consistency. \startnarrower with its interface is one of the oldest commands which also means that it's used in our styles however, we already have \startnarrow and i extended that one to accept a few more combinations: \showframe \definenarrower[whatever][left=3cm,right=2cm,default=left] \starttext \input ward \startnarrower[2*left] \input ward \stopnarrower \input ward \startnarrow[whatever] \input ward \stopnarrow \input ward \startnarrow[whatever][right] \input ward \stopnarrow \input ward \startnarrow[whatever][default=middle] \input ward \stopnarrow \input ward \startnarrow[whatever][default=middle,middle=-1cm] \input ward \stopnarrow \input ward \startnarrow[default=middle] \input ward \stopnarrow \input ward \stoptext - 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] unwanted extra interline space in typing environment
On 8/7/2013 10:52 PM, Pablo Rodríguez wrote:
On 08/07/2013 08:00 PM, Wolfgang Schuster wrote:
Am 07.08.2013 um 19:47 schrieb Pablo Rodríguez oi...@web.de:
[...]
How can avoid the unwanted extra interline space in the typing environment?
Can you make a minimal example which shows the wrong spacing?
I can see it in your document but without a example it’s not possible
to give a answer.
Wolfgang,
this is a sample that shows the issue I mentioned in my previous message:
\setuplayout[setups=*lessstrict]
\startsetups[*lessstrict]
\setup[reset]
\widowpenalty=1
\clubpenalty=1
\stopsetups
\starttext
\dorecurse{38}{line\\}
\starttyping
\setuplayout[setups=*lessstrict]
\startsetups[*lessstrict]
\setup[reset]
\widowpenalty=1
\clubpenalty=1
\brokenpenalty=1
\stopsetups
\stoptyping
\page
\stoptext
I know that the widow line from the typing environment is causing the
extra interline spacing, but there are other occurrences where there is
no widow line and there is extra interline spacing.
you shouldn't rely on \\ as it also starts a new line with content
\dorecurse{38}{line\par}
-
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] problem with Persian feature
On 8/7/13, Otared Kavian ota...@gmail.com wrote: As Wolfgang said, if I fix the name of the key in \setmainfont (from « feature » to « features », see below), then your test works fine here (using Mac OS X 10.8.4, and ConTeXt ver: 2013.08.07 14:40 MKIV beta fmt: 2013.8.7). Unfortunately, on my system it does not work. By the way in mkiv you don't need to add \enableregime[utf-8]: by default ConTeXt uses utf-8. Thanks for this hint. Regards, Mingranina ___ 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 ___
