On 7/24/2018 14:43, Hans Hagen wrote:
Hi,
Around the upcoming context meeting we expect to release luatex 1.09
(or 1.10 ... yet undecided) which is the prelude to the next year tex
live version. It's another step towards a stable version in terms of
functionality as we don't expect much more
Dear all,
I found some warning message in the log file which concerns about the font.
I didn’t see this kind of error before. (I might missed this error.)
However, it produced an output.
fonts > defining > font with asked name 'texgyreheros-regular' is not
found using lookup 'file'
On 7/24/2018 11:02 PM, Idris Samawi Hamid ادريس سماوي حامد wrote:
Hi Hans, all,
One needed feature that would be of general use is better support for
synctex. Thinking especially of structural elements such as headings,
footnotes, etc. which mostly do not work with synctex - i.e., clicking
Hi Hans, all,
On Tue, 24 Jul 2018 12:43:51 -0600, Hans Hagen wrote:
Hi,
Around the upcoming context meeting we expect to release luatex 1.09 (or
1.10 ... yet undecided) which is the prelude to the next year tex live
version. It's another step towards a stable version in terms of
On 07/24/2018 09:52 PM, Hans Hagen wrote:
> On 7/24/2018 9:24 PM, Pablo Rodriguez wrote:
>> [...]
>> The new font instance is what I was missing in many of the issues I had
>> with features.
> > hm, only with those that affect the glyph shapes in some way, not with
> normal otf kind of features i
On 07/24/2018 09:07 PM, Hans van der Meer wrote:
> I am using XML a lot for structured data and typesetting them with
> hopefully not too much attention to detail — although I must confess
> often being a hopeless perfectionist.
But is it possible to use ConTeXt without paying attention to the
On 07/24/2018 08:43 PM, Hans Hagen wrote:
> [...]
> It's not my intention to implement each possible feature as core feature
> (no one would document it anyway). Also, as development is basically a
> spare time effort, don't expect complex commercially interesting niches
> to come for free
On 7/24/2018 9:24 PM, Pablo Rodriguez wrote:
On 07/24/2018 07:02 PM, Hans Hagen wrote:
On 7/24/2018 6:20 PM, Pablo Rodriguez wrote:
[...]
\starttext
{\feature[+][effect]1234567890}
1234567890 {\feature[+][oldle]1234567890}
\stoptext
I wonder why the first font feature
On 07/24/2018 07:02 PM, Hans Hagen wrote:
> On 7/24/2018 6:20 PM, Pablo Rodriguez wrote:
>> [...]
>> \starttext
>> {\feature[+][effect]1234567890}
>> 1234567890 {\feature[+][oldle]1234567890}
>> \stoptext
>>
>> I wonder why the first font feature ("effect") doesn’t work. What
I am using XML a lot for structured data and typesetting them with hopefully
not too much attention to detail — although I must confess often being a
hopeless perfectionist.
If there are general improvements that can be made in that direction, I would
welcome them. Although I apologise not
Hi,
Around the upcoming context meeting we expect to release luatex 1.09 (or
1.10 ... yet undecided) which is the prelude to the next year tex live
version. It's another step towards a stable version in terms of
functionality as we don't expect much more to be added (in fact, I'm
wondering
On 7/24/2018 6:20 PM, Pablo Rodriguez wrote:
Dear list,
I have the following sample:
\definefontfeature[effect]%[effect=.2]
[effect={width=.3,delta=0.4,factor=0.3}]
\definefontfeature[oldle][onum=yes]
\setupbodyfont[palatino]
\starttext
On 7/24/2018 4:41 PM, Stanislav Sokolenko wrote:
I went with the following little extension to match and make bold
multiple names:
ok.
(this document.CompareNames makes a good candidate for a 'how to improve
your lua code' tutorial ... maybe something for the ctx meeting)
I didn't check
Dear list,
I have the following sample:
\definefontfeature[effect]%[effect=.2]
[effect={width=.3,delta=0.4,factor=0.3}]
\definefontfeature[oldle][onum=yes]
\setupbodyfont[palatino]
\starttext
{\feature[+][effect]1234567890}
1234567890
On 07/24/2018 11:04 AM, Fabrice Couvreur wrote:
> Hi Pablo,
> Thank you Pablo for your answer that corresponds to what I seek to do.
> Small question: how to have a point at the end of the numbering that is
> to say :
>
> Property 1.1.
> Property 1.2.
Hi Fabrice,
the option seems to be:
That's perfect, thank you!
On 2018-07-23 06:32 PM, Hans Hagen wrote:
\startsetups btx:list:author:normalshort
\fastsetup{btx:list:author:concat}
\begingroup
\ctxluacode{document.CheckMeB("\currentbtxdataset","\currentbtxtag",\number\currentbtxauthorindex)}
Hi Pablo,
Thank you Pablo for your answer that corresponds to what I seek to do.
Small question: how to have a point at the end of the numbering that is to
say :
Property 1.1.
Property 1.2.
.
Thanks
Fabrice
2018-07-23 17:39 GMT+02:00 Pablo Rodriguez :
> On 07/23/2018 05:11 PM, Fabrice
17 matches
Mail list logo
